(15)
`
`!f.ffm¥6-62020
`
`[~9]
`
`[iZJ g J
`
`1:~~-J'\
`
`name=adm.Ol
`ap-name=adm.Ol.dir
`ap-name=adm.Ol.addr
`IJ:rt-v;t.m¥fll,~
`Jr.tv9""1JftHtt 1
`~~~-
`905
`
`j
`
`I
`
`:r. :/ t- r; £ l{!i
`J~H1 »llrt'v.A
`AP7t'J.t;!.
`jjff£
`
`ap-name=adm.02.mail
`addr=l3. 7.16
`ap-addr=5
`alias=
`
`:r.::;.t}'-1);:&~
`
`··11 atllEYFv:A
`A P7 Fv:A
`!iJU£
`
`ap-name=adm.03.file
`addr=l3.7.17
`ap-addr=6
`alias:
`
`906a
`907a
`908a
`909a
`
`906b
`907b
`9D8b
`909b
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1500
`
`

`
`[[3Jl0]
`
`r~-·--------------------------------~-------------------------------------~
`:Oi-{ ~A ~~~.Jf ,, ·~
`~~; 1 )\r.Jf-1\
`I name=adm.03
`narne=ad~.Ol
`ladd r•:::l3. 7.17
`addr=l3. 7.15
`ap-na111e=adm. 03 .• fi I e
`ap-nalle"'adm. 01. addr
`ap-na11e=adm.Ol.dir
`I
`---
`
`I
`
`I
`
`I
`
`-
`
`[
`
`1
`
`I
`
`I
`
`I
`
`• • •
`
`ij'-1'\
`
`1""'"1
`~
`......
`0 .......
`
`I
`I
`
`I
`
`l
`
`[
`
`I
`
`I
`!{ )1.· 1 :/' B
`1001
`
`I
`ll~lll!i7-J~
`
`1006a
`I
`J:~Jm~fl
`-in~ 1 :r::; "
`iafa~ :r::; t-
`• • •
`~-----------------------------------~--------~~------------------ 1om-----~
`r----------------------------------- ---------------------------- --------,
`rl003a ~ ~lp03b
`1006b
`!
`q ""' y ;; 1- I
`I ~.I . . .
`.PIIIllill
`I I
`----
`:
`I
`~
`)1.-Jl.rl)·-)'\
`name•bdm.sx
`I
`addr=13.8.6
`I
`ap-name=bdr~.sx.mail
`
`name=bdm. ax
`addr=13.8.3
`ap-na~te=bdlll.ax.addr
`ap-name=bdm.ax.dir
`'-1004
`1002
`l005-··
`·-----------------------------------~--------------------------------------
`
`I
`
`1
`
`I
`
`(~ 1 1]
`
`~9!f1Ufl 1108
`
`A
`
`;-r:t:ro:
`18tl!1iUU
`'J11
`.--------1--------------- ----------- ----- _ ................ --...---- -----------
`ada.02
`bdm.sx
`UPDATE
`1106
`1105
`
`L I
`
`~$Iii-If- J1~lfli
`
`adm. 01. addr
`
`1101 1102
`
`1103
`
`i!{ifji,:jj--J~£l'
`bdm.ax.addr
`1104
`
`____________ ..
`Ulfl1Y~v.A
`13.8.6
`1107
`
`,.......
`~
`
`.......
`
`(J)
`I
`(J)
`N
`0
`N
`0
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1501
`
`

`
`!f.!flm-¥6-62020
`
`(17)
`
`[~ 1 2]
`
`[~ 1 2]
`
`-1---------,
`
`1002-1------~
`
`Y l''v.A'if-J~
`
`ap-name~adm.Cl.addr
`
`7 }!' v:A 'tf"-J\
`ap-name=bdm.ax.addr
`
`17 ~LI.A·ti~ I
`
`\
`
`i
`I
`I
`I
`I
`I
`I
`
`' I
`' I
`
`I
`
`\
`\
`\
`\
`\
`
`'
`\ 1201
`' ' \
`
`~7~LI7-1Ji~~
`... ,
`i
`I
`I
`I
`I
`I
`j
`I
`I
`I
`J
`
`' " ' ' '
`
`-... , 1211
`' '
`
`name=
`%al.!J!Y F 1./ .A addr=
`~ ~) 1ft:bM!fiJ
`time=
`- - - - - - - - - : - ---:--
`
`- -
`
`1202a
`
`1203a
`
`1204a
`
`.l-F~~ name=bdm. sx 1202b
`~ll!!YFLI.A addr=l3.8.6 1203b
`~ tl ;fi~:IJ~rsl time=9999
`1204b
`:
`:
`
`[~ 1 4]
`
`[~ 1 4]
`
`I 1401
`
`r-------------------------
`
`adm 1402
`
`1 • • I !
`il404~
`
`I I
`
`OL
`
`02
`
`03
`
`'""'
`
`addr
`
`dir
`
`mail
`
`file
`
`1406
`
`l
`I
`I
`:
`I
`I
`I
`I
`
`L-----------------------------------....J
`
`I
`
`bdm 1403
`
`ax
`
`sx
`
`HOSA
`1\
`
`------~--~----·-----------------t
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`I
`J
`I
`
`addr
`
`dir
`1407
`
`mail
`
`I
`
`I
`
`'
`L--------------------------------1
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1502
`
`

`
`!flflm¥6-62020
`
`(18)
`
`[~ 1 3)
`
`[i@ 1 3 J
`
`r02-2
`r-1 vt~ f-.lJ-Jt-r<
`
`ap-name~adm.Ol.dir
`
`11002-2
`-'T-1 vD" t-IJ-lJ--;'\
`
`ap-nane~bdm.ax.dir
`
`171 v? ~ 1J-tf¥i!
`
`i
`I
`
`I ' I
`
`I
`l
`I
`I
`I
`I
`1
`i
`I
`I
`I
`I
`I
`I
`l
`
`1-r-r v!l ~ 1J 'liM! I
`
`..........
`
`I
`
`l
`I
`I
`I
`
`I ' ' I
`
`I
`!
`
`:r:. ~ ~ 1) ~ ;ro;
`,.'11
`titlJ!Y J-:1./:::;t.
`
`nallle ... adm,02.ma.il
`
`addr=
`
`ap-addr-
`A PY ~v;;\
`---- ~----- ---------------- --- ----- ------11Z~G.tr¥-.----------a-1 ias-lx:!m. sx. m"' 7 1
`
`l306a
`
`1307a
`
`1308a
`l':!na.,
`
`/
`
`I
`/
`
`;
`/
`
`1311
`
`I ,
`
`I
`I
`I
`
`I • ' I
`I ._______
`
`\
`l
`1
`I
`I
`I
`!
`I
`I
`I
`I
`I
`\
`I
`
`.:r:.:;.; ~ I) !l!J.l\
`•·11: ~1:!1!7 J"v;;\
`AP7 ~!.-;:\
`
`jJij£
`
`name=bdm.sx.nail
`
`addr~13.B.6
`
`ap-addr--5
`alias=
`
`1306b
`
`1307b
`
`l308b
`
`1309b
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1503
`
`

`
`Electronic Acknowledgement Receipt
`
`EFSID:
`
`Application Number:
`
`6626107
`
`90010416
`
`International Application Number:
`
`Confirmation Number:
`
`1061
`
`Title of Invention:
`
`Point-to-Point Internet Protocol
`
`First Named Inventor/Applicant Name:
`
`6108704
`
`Customer Number:
`
`42624
`
`Filer:
`
`Michael R. Casey
`
`Filer Authorized By:
`
`Attorney Docket Number:
`
`2655-0188
`
`Receipt Date:
`
`Filing Date:
`
`TimeStamp:
`
`14-DEC-2009
`
`17 -FEB-2009
`
`11:22:44
`
`Application Type:
`
`Reexam (Third Party)
`
`Payment information:
`
`Submitted with Payment
`
`I no
`
`File Listing:
`
`Document
`Number
`
`Document Description
`
`File Name
`
`File Size( Bytes)/
`Message Digest
`
`Multi
`Part /.zip
`
`Pages
`(ifappl.)
`
`396157
`
`1
`
`NPL Documents
`
`F0057 _ISR_US9615504.pdf
`
`no
`
`10
`
`e27 eccddcd4afd0e46c54 74618b0320ce80
`4ee73
`
`Warnings:
`
`Information:
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1504
`
`

`
`2
`
`NPL Documents
`
`F0058_gitman_ economic_anal
`ysis.pdf
`
`1874599
`
`ee5313be03ddc6271 d488165e869732cba
`dd8df5
`
`no
`
`22
`
`Warnings:
`
`Information:
`
`3
`
`NPL Documents
`
`F0059_huelamo_end _user_pre
`mises.pdf
`
`712273
`
`6bafdfc025 cd 5 fl a9069bd c6873 0628aae 79
`dc6a
`
`no
`
`11
`
`Warnings:
`
`Information:
`
`4
`
`NPL Documents
`
`F0060_RFC978.pdf
`
`no
`
`5
`
`102320
`
`Warnings:
`
`Information:
`
`21230c20d 1270e7 c861516a43079c6e0e80
`ff401
`
`202556
`
`5
`
`NPL Documents
`
`F0061_RFC1 055.pdf
`
`no
`
`6
`
`4200eae0048397a08bb 15b27455eee7761
`a1a37
`
`Warnings:
`
`Information:
`
`6
`
`NPL Documents
`
`F0062james_mills_data_voice
`.pdf
`
`223076
`
`99ef23fe5bf7c3074fe2a3c50b94bc2a9f6dc
`87c
`
`no
`
`6
`
`Warnings:
`
`Information:
`
`7
`
`NPL Documents
`
`F0063james_forgie_speech.
`pdf
`
`527034
`
`d a96c67 c7 ace 4ba3 88869f0654b9 727f9 73 3
`Ocb3
`
`no
`
`8
`
`Warnings:
`
`Information:
`
`8
`
`NPL Documents
`
`F0064james_forgie_ voice_ co
`nferencing.pdf
`
`500690
`
`a64174568406c29dfe7866ab66ec3a5fa4ba
`6cda
`
`no
`
`8
`
`Warnings:
`
`Information:
`
`9
`
`NPL Documents
`
`F0065_Janes_1979_80.pdf
`
`no
`
`3
`
`154076
`
`Warnings:
`
`Information:
`
`9aed6ddfad82f64d8ec6a9194a 15c938e7b
`bfe7f
`
`421297
`
`10
`
`NPL Documents
`
`F0066_Janes_1985.pdf
`
`no
`
`5
`
`e446be3eb5d4585d956eb7002280badf40
`7b9504
`
`Warnings:
`
`Information:
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1505
`
`

`
`11
`
`NPL Documents
`
`F0067 _Janes_1989.pdf
`
`no
`
`5
`
`617418
`
`Warnings:
`
`Information:
`
`b 15 7 dff 490 70abed aS 7 d 8c608f714d 66886
`8297
`
`2431238
`
`12
`
`NPL Documents
`
`F0068_Janes_1990_91.pdf
`
`no
`
`17
`
`Warnings:
`
`Information:
`
`42a92bed 6d 3 24612d 639 3 dcb84cb 7722 Od
`ScSfec
`
`628193
`
`13
`
`NPL Documents
`
`F0069_Janes_1992_93.pdf
`
`no
`
`6
`
`21 d4e5 f3 ed af3 a02e9efb3aca 1 c85 06 7 d d cb
`ac48
`
`Warnings:
`
`Information:
`
`14
`
`NPL Documents
`
`F0070_Jim_stevens_Much_mo
`re.pdf
`l - - - - - - - - - - -1
`SOb 7 e 1 f91 ccb 1 05 e4c051 099e6 73 685 fa 77
`489b
`
`262071
`
`no
`
`9
`
`Warnings:
`
`Information:
`
`15
`
`NPL Documents
`
`F0071_John_bellamy _Digital_ T
`elephony.pdf
`I - - - - - - - - - ;
`d4118e2dd0b29ce876e901 d342c4920257
`12356f
`
`428289
`
`no
`
`7
`
`Warnings:
`
`Information:
`
`16
`
`Foreign Reference
`
`F0072_JP-63-131637.pdf
`
`no
`
`6
`
`183914
`
`Warnings:
`
`Information:
`
`c3613862827a91 f19076ae80574921 c36bc
`e9cee
`
`2765194
`
`17
`
`Foreign Reference
`
`F0073_JP _6-62020.pdf
`
`no
`
`20
`
`414e1 cc6f9741 c12c8db57735f1 d3be644d
`83841
`
`Warnings:
`
`Information:
`
`18
`
`NPL Documents
`
`487599
`F007 4_J P2008163825 _ Office_A
`1-----------1
`ction_ Translation.pdf
`ed bec99254efe8b8f883d 9 33 acl 3 ebd 3 6e6
`c0010
`
`no
`
`3
`
`Warnings:
`
`Information:
`
`19
`
`NPL Documents
`
`F0075_JP-59-44140.pdf
`
`no
`
`36
`
`1272933
`
`cb52899aaa212045567f925588a887a5511
`a54ba
`
`Warnings:
`
`Information:
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1506
`
`

`
`20
`
`NPL Documents
`
`F0076_k_sohraby _ISDN_Primar
`y.pdf
`I - - - - - - - - ;
`5 5 f33 3f3 Od b6a 34d 6cb4023d Oe 1 Of62a9 72
`ladO
`
`507873
`
`no
`
`9
`
`Warnings:
`
`Information:
`
`21
`
`NPL Documents
`
`F0077 _ken_sherman_data_co
`mmunications.pdf
`1-----------1
`a08045a 19608085c077e9ce8d9e66888398
`1b751
`
`752769
`
`no
`
`19
`
`Warnings:
`
`Information:
`
`22
`
`NPL Documents
`
`F0078_kevinjefay_kernel_sup
`port.pdf
`I - - - - - - - - - ;
`7 cd 5cc4ac2 7 48ca3 7fe3 c4c3 703 96d a3 82f6
`abbe
`
`803713
`
`no
`
`13
`
`Warnings:
`
`Information:
`
`23
`
`NPL Documents
`
`F0079 _kyuta_saito_ voice_pack
`et_comm.pdf
`l------------1
`d249d6607b52412523bbb 1 d75c95d3d 19f
`9f8485
`
`300668
`
`no
`
`6
`
`Warnings:
`
`Information:
`
`24
`
`NPL Documents
`
`F0080_Iawrence_roberts_evolu
`tion_of_packet.pdf
`I - - - - - - - - - - ;
`5322ac1 07dc3164a74af2da29ce 1 b 1 b9461
`10e21
`
`543758
`
`no
`
`7
`
`Warnings:
`
`Information:
`
`25
`
`NPL Documents
`
`837781
`lin hwa-
`F0081
`chun_dynamic_load_balancingl------------1
`, pdf
`75b8198609e325fc913a2fc40059c640dd33
`3ad7
`
`no
`
`11
`
`Warnings:
`
`Information:
`
`26
`
`NPL Documents
`
`F0082_m_e_ulug_Statisticai_M
`ultiplexing.pdf
`I - - - - - - - - - ;
`7877637c3d09815a3c55b75fc187620d82b
`31af5
`
`378989
`
`no
`
`8
`
`Warnings:
`
`Information:
`
`27
`
`NPL Documents
`
`F0083_m_gopalakrishnan_inte
`grating_voice_and_data.pdf l------------1
`ae2a 1 d3b0f16a57ff409cd4b6e9a3e58384
`dOd
`
`748795
`
`no
`
`11
`
`Warnings:
`
`Information:
`
`28
`
`NPL Documents
`
`F0084_mj_ross_alternatives_f
`or_integrating.pdf
`I - - - - - - - - - - ;
`77 a8d7 3 e3 d ecc 48d 75 85 3a92 ccfcf4eee 1 Oe
`e3a8
`
`504497
`
`no
`
`9
`
`Warnings:
`
`Information:
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1507
`
`

`
`29
`
`NPL Documents
`
`F0085_natesajanakiraman_ov
`erview_of_recent.pdf
`
`1075971
`
`d414c99a51 bdee8c7 e6535564b720d53db
`79d492
`
`no
`
`15
`
`Warnings:
`
`Information:
`
`30
`
`NPL Documents
`
`F0086_p_borgnis-desbordes.
`pdf
`
`75088
`
`no
`
`2
`
`611 bdOe 174 7e84778c4d 1934932595fa064
`844c0
`
`Warnings:
`
`Information:
`
`31
`
`NPL Documents
`
`F0087 _p_venkat_rangan_softw
`are_a rchitecture.pdf
`
`817899
`
`0777202a3b6656b761727a4b6648b51 bdf
`9d43b1
`
`no
`
`11
`
`Warnings:
`
`Information:
`
`32
`
`NPL Documents
`
`F0088_francis94inet.pdf
`
`no
`
`10
`
`2166322
`
`e0eebbd5ade457f82f85be64dff45d634ded
`a645
`
`Warnings:
`
`Information:
`
`33
`
`NPL Documents
`
`F0089 _I nternet_Navigator _wit
`h_SOR.pdf
`
`1454997
`
`204996c81 acf7d62216ff7dabeebb8f6bb6b
`964c
`
`no
`
`13
`
`Warnings:
`
`Information:
`
`34
`
`NPL Documents
`
`F0090_Extending_the_IP _Inter
`net_ Th roug h_Add ress_Reuse.
`pdf
`
`80075
`
`dea6f7364cb74432a61 b08c7a74983fba46
`a846
`
`no
`
`18
`
`Warnings:
`
`Information:
`
`35
`
`NPL Documents
`
`F0091_ph i lip_h_regan_is_it_th
`e_PBX.pdf
`
`468795
`
`8387f33bd1 f687164c86903828f9c2e364eb
`ccea
`
`no
`
`6
`
`Warnings:
`
`Information:
`
`36
`
`NPL Documents
`
`F0092_polle_t_zellweger_An_
`overview_of_the_etherphone.
`pdf
`
`972784
`
`efda62ad5ca7 c8d 116fcd9d7 c22bfe879e0d
`1387
`
`no
`
`12
`
`Warnings:
`
`Information:
`
`37
`
`NPL Documents
`
`F0093_r_braudes_Requirement
`s_for _Multicast.pdf
`
`904401
`
`7 5 a9dfd4 92a 7 6d6 718ef808d7 efd4 5 814a 7
`Oclf
`
`no
`
`18
`
`Warnings:
`
`Information:
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1508
`
`

`
`38
`
`NPL Documents
`
`F0094_r_w_meba_Experiments
`_in_Wideband.pdf
`
`233947
`
`d37bd24c9482b32dd1 ac11 cl e925b45a56
`301c9d
`
`no
`
`7
`
`Warnings:
`
`Information:
`
`39
`
`NPL Documents
`
`F0095_r_p_mcNamara_some_
`considerations.pdf
`
`292918
`
`5a0807f23 5 f0a2a9d 5 b56 7 d d877 4603 d d a 7
`914c2
`
`no
`
`5
`
`Warnings:
`
`Information:
`
`40
`
`NPL Documents
`
`F0096_randy_cole_packet_voic
`e_when.pdf
`
`662089
`
`2ef3af38d393b013e58d9dbb 1 aa29715601
`a7a07
`
`no
`
`10
`
`Warnings:
`
`Information:
`
`41
`
`NPL Documents
`
`F0097 _scott_flinn_coordinatin
`g_heterogeneous.pdf
`
`1104908
`
`160e963fe6320d 124 7d97276dfd8c255129
`7bfb8
`
`no
`
`16
`
`Warnings:
`
`Information:
`
`42
`
`NPL Documents
`
`F0098_shimmi_hattori_integra
`ted_digital_switching.pdf
`
`656025
`
`5701 ee25e31 d8c6361 c49a8e318ed6fbf46
`7494
`
`no
`
`7
`
`Warnings:
`
`Information:
`
`Total Files Size (in bytes)
`
`30535989
`
`This Acknowledgement Receipt evidences receipt on the noted date by the USPTO of the indicated documents,
`characterized by the applicant, and including page counts, where applicable. It serves as evidence of receipt similar to a
`Post Card, as described in MPEP 503.
`
`New A~~lications Under 35 U.S.C. 111
`If a new application is being filed and the application includes the necessary components for a filing date (see 37 CFR
`1.53(b)-(d) and MPEP 506), a Filing Receipt (37 CFR 1.54) will be issued in due course and the date shown on this
`Acknowledgement Receipt will establish the filing date of the application.
`
`National Stage of an International A~~lication under 35 U.S.C. 371
`If a timely submission to enter the national stage of an international application is compliant with the conditions of 35
`U.S.C. 371 and other applicable requirements a Form PCT/DO/E0/903 indicating acceptance of the application as a
`national stage submission under 35 U.S.C. 371 will be issued in addition to the Filing Receipt, in due course.
`
`New International A~~lication Filed with the USPTO as a Receiving Office
`If a new international application is being filed and the international application includes the necessary components for
`an international filing date (see PCT Article 11 and MPEP 181 0), a Notification of the International Application Number
`and of the International Filing Date (Form PCT/R0/1 OS) will be issued in due course, subject to prescriptions concerning
`national security, and the date shown on this Acknowledgement Receipt will establish the international filing date of
`the application.
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1509
`
`

`
`PCT
`WORLD IN'll!Lil!C1UAL PROPERTY OROANJZA UON
`Iutemational BW'C811
`INTERNATIONAL APPUCATION PUBLISHED UNDER THE PATENf COOPERATION TREATY {PCI)
`wo 94122087
`(51) IDteroatiolllll Patent Classification 5 :
`G06F 13100
`(43) IDteruatiolllll Publkatioa Date: 29 September 1994 (29.09.94)
`
`(11) IDterDatiolllll Publication Number:
`
`Al
`
`(21) IDternatioDBI Application Number.
`
`(22) IDternational FiliDg Date:
`
`PCI'IUS94~ (81) Designated States: AU, CA, JP, KR, European patent (AT,
`BE, 01, DB, DK, ES, FR., GB, GR, IE, IT, LU, MC, NL,
`PT, SE).
`
`3 January 1994 (03.01.94)
`
`i
`
`(30) Priority Data:
`08/033,914
`
`19 Man:h 1993 (19.03.93)
`
`Publiihed
`With international search report.
`
`US
`
`(71) Applicant: 3COM CORPORATION [US/US]; S400 Bayfront
`Plaza, P.O. Box 58145, Santa Clara, CA 95052-8145 (US).
`
`(72) IDventors: NILAKANTAN, Cbandrasekharan; 3774 Woodbart.:
`Court, San Jose, CA 95117 (US). LOI, Ly; 34852 Winches(cid:173)
`ter Placa, Fremont, CA 94555 (US). ARUNKUMAR, Na(cid:173)
`garaj; 3041 Cedar Ridge Court, San Jose, CA 95148 (US).
`SEAMAN, Michael, John; 350 Elan Village Lane, 11206,
`San Jose, CA 95134 (US).
`
`(74) Agent: HAYNES, Mluk, A; Haynes & Davis, Suite 170,2180
`Sand Hill Road, Menlo Park, CA 94025-6935 (US).
`
`(54) Title: SYSTEM FOR REVERSE ADDRESS RESOLUTION FOR REMOTE NEIWORK DEVICE
`
`lZ1
`
`PACKET EXCHANGE OVER 'JAil HI:Dll\
`
`(57) Abstract
`
`A rcvene address resolution protocol for usc in a commWiicalion network which allows ruolutioo logic to rrovide a higher level
`protocol information (such as an IP address) to a somt:C of a mquest (127) for such infonnation (122), indepeodent of the physical network
`address of such SOUICC. The protocol is used in a processor having a pliiiiility of ports, at least onc of such ports conoccted by a point-ti>
`point chaone1 to a mnote network device. Reverse address resolution protocol is responsive (129) to a resolution n:qucst from the remote
`octwork device across the point-to-point c:halmc1 to supply the higher level protocol infmmatioo based upon the port through which the
`resolution n:qucst is n=ivc:d (125), rather than the physical network address of the n:questing device. Thus, a remote device may be
`coupled to a network, aod c:oonected to a c:entral maoaganent site across a point-to-point communication link, in a "plug and play" mode.
`The person c:oonecting the device to the JaDOte network docs not need to determine the physical network address of the device or coofigurc
`the devic:e with a higher level address protocoL
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1510
`
`

`
`FOR THE PURPOSES OF INFORMAnON ONLY
`
`Codes used to identify Slates party to the PCT on the front pages of pamphleiS publishing intcmational
`applications under the PCT.
`
`AT
`AU
`BB
`BB
`ar
`BG
`BJ
`BR
`BY
`CA
`CF
`CG
`CD
`Cl
`CM
`CN
`cs
`cz
`DB
`DK
`I!S
`n
`fR
`GA
`
`AUSiria
`Allllnlla
`llolllodoe
`Bdakm
`BurtiDa Puo
`Balprla
`l!eoiD
`BnzjJ
`Bellruo
`Canada
`QalnJ Aflkan Ropubllc
`<:oaso
`Swilmlml
`ale d'lvoile
`Clmaooa
`OIIDa
`Olocbodovotla
`Czcdl Ropubllc
`<lcrmaDy
`Deaawlt
`SpaiD
`fiDiml
`ITIIIIlO
`Glbco
`
`GB
`Uoltod JQaadom
`GE
`Gelqla
`GN
`GuiDca
`GR
`Gleccc
`BU
`Ruopry
`IB
`lrclaDd
`rr
`llaly
`JP
`Japoa
`KE
`Jtcaya
`KG K~
`KP
`Domlx:nllc ~··· kp~~Jllc
`orKrRa
`D
`~lie of Komi
`KZ
`JW.atbllall
`u
`LiccbcmtdD
`Sri LaiD
`Lit
`w
`l..oaCIIiJCUIJ
`LV
`LIMa
`MClCIIOO
`MC
`~Jic or Moldova
`MD
`Madapoclr
`MG
`ML
`MaB
`MN MqoBa
`
`MR
`M.omiiiDII
`MW Malawi
`NE
`If,....
`NL
`NetbcrlaDdl
`Norway
`NO
`NZ
`NcwZcalaDd
`PL
`Polml
`PT
`Podupl
`RO
`RDmmia
`RU
`RuSm Pedaadoa
`SD
`SudiD
`SE
`Swcdal
`Slowala
`Sl
`SK
`Slowtla
`SN
`Scllqal
`TD
`Clad
`TG
`Toco
`Tl
`TajiklstaD
`Tlllllda411111 Tobap
`TT
`UA
`UbiiDc
`Uollod s- or Amcril:a
`us
`uz
`Uzbcklllaa
`VlotNam
`VN
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1511
`
`

`
`wo 94/2.2087
`
`PCT IUS94/00004
`
`SYSTEM FOR REVERSE ADDRESS RESOLUTION
`FOR REMOTE NETWORK DEVICE
`
`FIELD OF THE INVENTION
`
`The present invention relates to start up protocols for devices in
`
`communication networks; and more particularly to systems which allow a
`
`machine without a configured higher level protocol address to obtain such
`
`5
`
`address without a unique machine identifier.
`
`DESCRIPTION OF RELATED ART
`
`A widely accepted series of international standards describing network
`
`architectures is known as the OS! reference model. See, generally,
`
`10
`
`Tannenbaum, Computer Networks, 2nd Ed., 1988, Prentice-Hall. According
`
`to this model, network communications are divided into a plurality of
`
`protocols within layers of the model. Local Area Networks (LANs) operate
`
`using medium access protocols within the lower layers, layers 1 and 2, of the
`
`OSI model, such as the carrier sense multiple access with collision detection
`
`15
`
`CSMAICD, IEEE Standard 802.3, also known as ETHERNET, and the token
`
`ring access ring method of IEEE Standard 802.5. These two lower layers
`
`are typically broken down into the physical layer and the data link layer, with
`
`the data link layer being further broken down into a media access control
`
`(MAC) layer, and a logical link layer.
`
`20
`
`Systems, such as personal computers, workstations, and mainframe
`
`computers, attached to the LANs each have a distinct lower level protocol
`
`identifier known as the physical network address or MAC address. LAN
`
`frames forwarded to a destination system on the network under these lower
`
`level protocols contain the destination system MAC address, or other
`
`25
`
`physical network address, as a destination. LAN frames forwarded from a
`
`source system on the network contain the source system MAC address, or
`
`other physical network address, as a source address.
`
`Systems
`
`. 1 .
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1512
`
`

`
`wo 94/l2087
`
`PCT /US94/00004
`
`communicate by encapsulating additional protocols (OSIIayers 3-7) within
`
`the lower layer LAN frames. These higher level protocols are grouped into
`
`suites such as the TCP/IP protocol suite and the XNS protocol suite. Many
`
`LANs contain groups of end systems that use different higher level protocol
`
`5
`
`suites. These higher level protocol suites also assign unique higher level
`
`protocol identifiers to systems which transmit or receive frames in the
`
`network.
`
`For instance, an internet protocol IP address is assigned to each
`
`system operating within an internet protocol network. The internet protocol
`
`10
`
`address includes a network address portion and a host address portion. The
`
`netWork address portion identifies a network within which the system resides,
`
`and the host address portion uniquely identifies the system In that network.
`
`Processors routing packets in an internet protocol network rely on the
`
`network address portion of the IP address in a frame to find the local area
`
`15
`
`network of the destination machine. Once the local area network of the
`
`destination is located, the frame is forwarded to that network where the host
`
`address portion is relied upon to assign a MAC address for the destination
`
`machine to the packet. Thus, higher level protocol address places the
`
`device In a particular network or subnetwork, so that the higher level protocol
`
`20
`
`can effectively manage the routing of packets among the networks, without
`
`maintaining a table of the unique physical access layer identifiers for all of
`
`the terminals in the network.
`
`In order to communicate in such a network, the machine must first
`
`obtain Its higher level protocol address. This address is typically assigned
`
`25
`
`by a central authority, such as the Internet Activities Board, or by a network
`
`manager. Normally, a particular machine learns its IP address by a
`
`configure operation, in which a technician uses a local terminal to configure
`
`the machine. In a centrally managed network, this could be a cumbersome
`
`task, Involving travel of skilled personnel away from the central management
`
`30
`
`location. However, a reverse address resolution protocol RARP has been
`
`- 2-
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1513
`
`

`
`wo 94/22087
`
`PCT /US94/00004
`
`developed for networks such as TCP/IP or SNMP protocols. The RARP
`
`allows a machine without a configured IP address to obtain an IP address
`
`from a remote server. The machine broadcasts a request and waits until an
`
`RARP server responds. In the request, the requesting machine must provide
`
`5
`
`its physical network address (MAC address) to uniquely identify Itself,
`
`allowing the server to map it into an IP address.
`
`This RARP protocol works fine, so long as the central management
`
`site Is aware of the physical network address of the devices being added to
`
`the network.
`
`In order to find out the physical network address, all of the
`
`1 0
`
`system being added to the network must be passed through the central
`
`management site so that the address can be read from these machines, or
`
`a local technician must read the physical network address from the machine
`
`and telephone the central site. This process makes connecting a new device
`
`to a network difficult. Further, this process of physically reading the physical
`
`15
`
`network address from the box Is prone to human errors. Such addresses
`
`are typically very long (MAC addresses are 48 bits long), and can be
`
`misread or typed in erroneously.
`
`It is desirable to have so-called "plug and play• network devices.
`
`Such devices can be plugged in and turned on by unskilled personnel.
`
`20
`
`However, the need to find out the physical network address of the box
`
`detracts from this ability.
`
`Accordingly, it is desirable to provide a technique for resolving higher
`
`level protocol addresses, without reliance on the lower level protocol
`
`addresses.
`
`25
`
`SUMMARY OF THE INVENTION
`
`The present invention provides a reverse address resolution protocol
`
`for use in a communication network which allows resolution logic to provide
`
`a higher level protocol address, or other information, to a source of a request
`
`30
`
`for such address, Independent of the physical network address of such
`
`. 3-
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1514
`
`

`
`wo 94122087
`
`PCTIUS94/00004
`
`source. The proto~ol according to the present invention is used in a
`
`processor having
`
`
`
`a plurality of ports, at least one of such ports connected by
`
`a point-to-point channel to a remote network device. The reverse address
`
`resolution protocol is responsive to a resolution request from the remote
`
`5
`
`network device across the point-to-point channel to supply the higher level
`
`protocol address based upon the port through which the resolution request
`
`is received, rather than the physical network address of the requesting
`
`device. Thus, a remote device may be coupled to a network, and connected
`
`to a central management site across a point-to-point communication link in
`
`1 0
`
`a "plug and play• mode. The person connecting the device to the remote
`
`network does not need to determine the physical network address of the
`
`device or configure the device with a higher level address protocol. All this
`
`can be handled automatically.
`
`Thus, the present invention can be characterized as an apparatus for
`
`15
`
`resolving higher level protocol addresses in response to resolution requests
`
`from a source of resolution requests in a communication network. The
`
`apparatus comprises a central processor having a plurality of ports for
`
`connection to the communication network, and resolution logic which is
`
`coupled to the communication network and In communication with the central
`
`20
`
`processor. The resolution logic provides a higher level protocol identifier in
`
`response to a particular port in the plurality of ports through which the
`
`resolution request is received by the central processor, independent of the
`
`lower level protocol identifier of the source of the resolution request. The
`
`resolution logic may be a routine executed by the central processor, or a
`
`25
`
`routine executed by a network management processor coupled to the
`
`communication network, and in communication with the central processor.
`
`The resolution logic, according to one aspect, includes a resolution
`
`table that is configurable independent of the lower level protocol identifiers,
`
`which assigns higher level protocol identifiers to particular ports of the central
`
`30
`
`processor through which the resolution requests may be received.
`
`- 4-
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1515
`
`

`
`wo 94/22087
`
`PCTIUS94100004
`
`The higher level protocol identifier may comprise an internet protocol
`
`IP address, which includes a network address for the source of the resolution
`
`request, and a host address for the source of the resolution request.
`
`Further, the higher level protocol may be utilized by a network management
`
`5
`
`system, which communicates network-wide, while the lower level protocol
`
`comprises a medium access protocol.
`
`The resolution logic, according to the present invention, relies on the
`
`source of the resolution request being coupled across a point-to-point
`
`communication channel to the particular port of the processor receiving the
`
`10
`
`request. In this way, the port serves as a virtual identifier for the source of
`
`the request.
`
`Thus, the present invention can also be characterized as an apparatus
`
`for connecting a first network and a second network. This apparatus
`
`includes a communication link, a first processor, and a second processor.
`
`15
`
`The first processor has a first interface coupled to the first network and a
`
`second interface coupled to the communication link. The second processor
`
`has a lower level protocol identifier and is coupled to the second network
`
`and to the communication link. Resolution logic is coupled to the first
`
`network to provide a higher level protocol identifier to the second processor
`
`20
`
`in response to a resolution request through the second interface of the first
`
`processor, independent of the lower level protocol identifier of the second
`
`processor. In this manner, the first processor can configure the higher level
`
`protocol addresses for devices in the system, Independent of the lower level
`
`protocol addresses.
`
`25
`
`According to another aspect of the invention, the first processor
`
`includes resources to provide network services to frames of data in the first
`
`and second networks through the first and second interfaces, and the second
`
`processor includes resources to extend the second interface of the first
`
`processor transparently to the second network.
`
`- 5 -
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1516
`
`

`
`wo 94/22087
`
`PCT /US94/00004
`
`The resolution logic may comprise a routine executed by the first
`
`processor, or a routine executed by a network management processor
`
`located in the first network.
`
`Accordingly, a technique which greatly improves the "plug and play•
`
`5
`
`capability of a network device has been provided. Remote networks may be
`
`set up using this system, without requiring error prone and cumbersome
`
`techniques to acquire the physical network address of each device being
`
`added to the network.
`
`Other aspects and advantages of the present invention can be seen
`
`1 0
`
`upon review of the figures, the detailed description, and the claims which
`
`follow.
`
`BRIEF DESCRIPTION OF THE FIGURES
`
`Fig. 1 is a schematic diagram of a system including the reverse
`
`15
`
`address resolution logic according to the present invention.
`
`Fig. 2 illustrates a prior art packet exchange sequence for reverse
`
`address resolution over LAN media.
`
`Fig. 3 Illustrates a packet exchange sequence over a WAN medium
`
`as extended according to the present invention.
`
`20
`
`Fig. 4 illustrates the resolution request generation process used in the
`
`sequence of Fig. 3.
`
`Fig. 5 illustrates the resolution request response generation process
`
`used in the sequence of Fig. 3.
`
`Fig. 6 illustrates the resolution request response acceptance process
`
`25
`
`used in the sequence of Fig. 3, which results in a request for a subnet mask
`
`in IP networks.
`
`Fig. 7 is a diagram of the subnet mask
`
`
`
`response generation process
`
`used in the sequence of Fig. 3.
`
`Fig. 8 is a diagram of the subnet mask response acceptance process
`
`30
`
`used in the sequence of Fig. 3.
`
`- 6 -
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1517
`
`

`
`W094/ll087
`
`PCTIUS94/00004
`
`Fig. 9 is a schematic diagram illustrating one network environment in
`
`which the present invention may be used.
`
`DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
`
`5
`
`A detailed description of preferred embodiments of the present
`
`invention is provided with respect to Figs. 1-9. Fig. 1 illustrates application
`
`of the present invention in a preferred embodiment. Figs. 2-8 Illustrate the ·
`
`extended protocol for reverse address resolution used In a preferred
`
`embodiment of the present invention. Fig. 9 provides an overview of a
`
`1 0
`
`network in which the present invention may be applied.
`
`Fig. 1 provides a schematic diagram of an apparatus for connecting
`
`a first network 1 0 to a second network 11 using address resolution logic 25
`
`according
`
`
`
`to the present invention. The first network 1 0 includes a first LAN
`
`9 which includes a plurality of end systems and a server, and may be
`
`15
`
`interconnected to other LANs using intermediate systems (not shown) known
`
`in the art. Coupled to the LAN 9 is a boundary router 12. The boundary
`
`router 12 Is an intermediate system in the network which provides network
`
`resources serving higher level protocol suites which, in one unique
`
`embodiment, constitute routing resources. As such, the boundary router 12
`
`20
`
`maintains end system directories 13 for the local LAN 9 and global routing
`
`information 14 to serve the routing functions according to the higher level
`
`protocol suites. Thus, the end system directories will include DEC end
`
`system tables, IPX end system tables, IP end system tables, and others to
`
`serve other protocol suites that are operating in the network 10. The
`
`25
`
`boundary router 12 may also be coupled to other portions of the corporate
`
`data network as schematically illustrated at arrow 15.
`
`The boundary router 12 includes a local interface 16 which serves the
`
`local LAN 9 providing access to the network resources within the boundary
`
`router to end systems on LAN 9. The boundary router could also have
`
`30
`
`interfaces to other local LANs as well. In addition, the boundary router 12
`
`-7-
`
`LG v. Straight Path, IPR2015-00209
`Straight Path - Ex. 2024 - Page 1518
`
`

`
`W094/l2087
`
`l'CT/US94/00004
`
`includes a remote routing interface 17, which provides an interface to the
`
`network resources for end systems in the remote network 11. In support of
`
`the remote interface 17, the boundary router maintains end system
`
`directories 18 serving the higher level protocol suites in the remote network
`
`5
`
`11.
`
`As illustrated schematically by the hatched symbol 19, the remote
`
`network 11 appears to the end systems in the local LAN 9 as if it were a
`
`LAN connected