(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2005/0286466 A1
`
`
` Tagg et al. (43) Pub. Date: Dec. 29, 2005
`
`US 20050286466A1
`
`(54) SYSTEM FOR PROVIDING MOBILE VOIP
`
`Related US. Application Data
`
`(76)
`
`Inventors: James Peter Tagg, Edenbridge (GB);
`Andrew Donald McEwan, Hanwell
`(GB)
`
`(63) Continuation-in-part of application No. 09/706,406,
`filed on N0V~ 3> 2000
`Publication Classification
`
`Correspondence Address:
`,
`REED SMITH LLP
`ATTN: PATENT RECORDS DEPARTMENT
`599 LEXINGTON AVENUE, 29TH FLOOR
`NEW YORK, NY 10022-7650 (US)
`
`(21) Appl. No.:
`
`11/129,184
`
`(22)
`
`Filed:
`
`May 12, 2005
`
`.
`Int. Cl.7 ....................................................... H04Q 7/00
`(51)
`(52) US. Cl.
`............................................ 370/329, 370/401
`(57)
`ABSTRACT
`A system for providing handoif for a mobile devices com-
`prising a mobile phone programmed to automatically han-
`dover between differing data bearers and to optimally detect
`those bearers in a roaming environment keeping power
`consumption to a minimum. Repeating means for these
`mobile devices to extend the range of coverage and the
`protocol for that coverage.
`
`
`
`Bose Exhibit 1031
`
`Bose v. Koss
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 1 0f 32
`
`US 2005/0286466 A1
`
`
`
`Fig. I
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 2 0f 32
`
`US 2005/0286466 A1
`
`
`
`Obtain Access
`
`Repeat until
`connection found
`
`Find network host
`
`node
`
`Establish Physical Link
`
`Establish Logical Link
`
`Send Client Info to Host
`
`
`
`Can local Match
`No Send Client & Host
`Information to Server
`be made?
`
`
`
`206
`
`
`
`
`
`
`
`
`
`
`209
`
`Done (Success)
`
`Can Server
`
`
`Match be made?
`
`
`
`207 No
`
`208
`
`Done (Fail)
`
`Fig. 2
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 3 of 32
`
`US 2005/0286466 A1
`
`General Member Information
`
`301
`
`Member ID
`
`Customer Record
`
`#
`
`Name, Address etc.
`
`Tunnel Provider
`
`302
`
`Allow data link
`
`Allow voice link
`
`Bandwidth share
`
`YES/NO
`
`YES/NO
`
`S°/o-ALL
`
`Number of simultaneous users
`
`1-16
`
`n n n
`
`.$/hour
`
`Sper connect
`
`Number of provided minutes
`
`Number of discrete connection events
`
`Total bits provided.
`
`Charge for uplink
`
`Cost to establish connection
`
`Tunnel user
`
`303
`
`Encryption level (data)
`
`Encryption level (voice)
`
`Pay for up—link
`
`Number of used minutes (budget)
`
`Link budget
`
`Polling Frequency
`
`Cell
`
`phone record
`
`Synchronize or buy
`
`low-high
`
`low-high
`
`max $/hour
`
`I]
`
`max $/day
`
`per hour
`
`Carrier, number etc...
`
`Table of desired content
`
`Fis. 3
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 4 of 32
`
`US 2005/0286466 A1
`
`Enable Cooperative Networking
`
`Log onto Web site
`
`401
`
`
`
` Software download to member
`
`device
`
`Configuration of Member Device
`
`Set tunnel provision preferences
`
`
`
`
`
`Set Access provision preferences
`
`Return Summary & Confirmation
`
`
`
`Fig. 4-
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 5 0f 32
`
`US 2005/0286466 A1
`
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 6 of 32
`
`US 2005/0286466 A1
`
`603
`
`601
`IP Sta k
`
`Pages
`
`612
`Server
`611
`Host
`Client 601
`602
`
`
`
`Browser
`Browser &
`613
`
`Application
`ww'|l m;
`
`
`
`
`
`
`
`606
`607
`608
`
`
`[p
`k
`
`
`
`
`
`617 Drivers
`
` Drivers
`Drivers
`
`4 Server Engine
`
`
`Configuration
`Sofiware
`
`Matching
`Rules
`
`Fig. 6
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 7 0f 32
`
`US 2005/0286466 A1
`
`SooxwM$6356
`o$M1coc3
`WWWx808:5
`
`rum-EEO2£85
`
`-mmcozfimmmo
`
`m-mi
`
`“m“9:me5
`
`MW“850c.
`1mfil
`
`701 702 703
`
`704 705
`
`707 708 709 710
`
`711 712
`
`713
`
`lg.
`
`7
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 8 0f 32
`
`US 2005/0286466 A1
`
`Matching Algorithm
`
` Matching Process
` Obtain Client ID
`
`
`
`Obtain Host FD
`
` Look up records on
`database.
`
` Match permissions with
`desired access
`
`
`
`
` Ask Client to change
`
`D0 permission
`desired access.
`and desire
`match?
`
`
`
`809
`Does Client
`
`
`have alternative
`
`
`preferences
`
`
`
`Fig. 8
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 9 0f 32
`
`US 2005/0286466 A1
`
`Server
`
`908
`
`VOIP
`
`Server
`
`
`
`
`
`
`903
`
`
`
`Internet
`
`901
`
`— "
`
`Cellular
`
`Infrastructure
`
`
`
`904
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 10 0f 32
`
`US 2005/0286466 A1
`
`$35.23:amas.“
`
`82{9&2
`
`$.qu8.3
`
`“32.533
`
`
`
`_¢mhwm......,.,.czmmv
`
`
`
`~_o_awee—
`
`floo—
`
`S$sz
`
`
`
`£23;"3%
`
`SE.acaca
`
`
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 11 0f 32
`
`US 2005/0286466 A1
`
`Audio Rec. 1102
`
`CODEC 1104
`
`CODEC 1105
`
`
`
`
`
`SIPI?S|P 1108
`
`
`
`I RFCOMM1111
`LZCAP 1112
`
`MAC 1114
`
`HCI 1115
`
`Phone
`1100
`
`
`
` Mobile: User Interface
`
`:
`
`
`
`Audio Play 1103
`
`
`
`
`
`
`Authenticate 1126
`SmAuth 1136
`
`
`
`
`RAW/RTP 1109
`
`
`
`
`
`
`
`
`
`
`
`MAC 113
`MAC 1134
`
`
`
`
`
`
`'
`PHY 1117
`PHY 113
`HW 1118
`
`
`
`
`
`
`
`
`75w <-> SIP 1124
`
`316 01137
`
`IP Bridge 1125
`
`Socket 1123
`
`-
`,
`RFCOMM
`1122
`LZCAP 1121
`
`HCI 1120
`
`PHY 1135
`
`Figure 11
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 12 0f 32
`
`US 2005/0286466 A1
`
`1214
`
`1215
`
`Vé/WAhlzl
`
`\éVLAhl/T
`
`Mobile
`
`lfggne
`
`Point
`
`SIP
`Server
`
`Phone
`1204
`
`[REUBEN]
`
`
`
`UMEIIDEJIIEIIIEIID
`
`DEL—[1111:1111
`
`Callibroken 1206
`
`Call held 1207
`
`UMT:S: Invite 1208
`
`UMTgs: Ringin_ 120
`
`UMT'S: 200 OK 121
`
`
`
`I
`
`Re-establishedmediastream 1213
`
`Join Conference 1212
`
`Figure 12
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 13 0f 32
`
`US 2005/0286466 A1
`
`1300
`SMLC
`
`
`
`Lb
`
`Inn’s—ocuuu-uu...u.-
`Cure v IHPLMN 1301!
`....--.....
`I
`
`fun-III...-
`.
`€1303
`5
`f
`1304
`.
`
`I—-.-----J
`
`1305
`MSG
`i;
`fi—H SS7
`II
`
`rung-nuuooooo
`:,..........= 3 GMSC :
`...........
`‘307
`1...........HI—>1 1306 g
`'
`
`6'3”}? SGSN :
`E- s”:
`a
`'
`
`
`..
`
`" 1312 "
`VLRI
`HLR
`
`
`
` {”116".
`HLR
`
`
`~-.------J
`HPLMN
`3
`AAA
`'
`Dunn-"ml
`
`
`
`
`
`
`1318
`Server (SIP)
`
`
`
`Radius
`
`Figure 13b @roposed invention).
`
`1335
`
`1336
`
`1337
`
`
`
`
`
`
`f"""""."
`:
`1338
`:
`1
`
`1334
`
`Lu-o-u-u-uu
`
`..-..“
`
`
`Po-IOOIOIOO-.‘
`=
`1339
`'
`POTS—DE PSTN
`F—POTS/ISD
`
`.-------
`r I ;
`
`
`
`
`
`Figure 13c (Bluetooth CTP).
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 14 0f 32
`
`US 2005/0286466 A1
`
`
`
`WLAN off
`WWAN ~Audio
`Voice Call WWAN -A
`1452
`
` DismverWLAN & Autheticate
`Authenticate .
`Discover Case 1
`
`Handon WWAN -A->WWAN -IP
`1453
`Case 4
`1454
`
`WLAN Connection
`
`WWAN Connection
`Votce Camswm .A
`
`
`
`1463
`
`146
`
` Handover WLAN ->WLAN
`
`
`
`
`
`WLAN off
`WWAN ~Audio lData
`1456
`VolP Call WWAN 4P
`
`Handoff WWAN -lP->WWAN -A
`Case 5
`1457
`
`
`
`Handoff wage EWWAN .A
`1458
`
`
`
`Handoff WLAN ->WWAN -IP
`Case 1
`1 460
`
`Handofl Voice ->WLAN
`Case 2
`
`1
`9
`
`
`
`WLAN Connection
`
`
`WWAN Conneaion
`VoIP Call WLAN
`
`
`1461
`
`45
`
`KEY
`WLAN Status
`WWAN Status
`Voice Call Path
`
`
`
`Active Call States Only
`
`
`
`Handoff WWAN 4P->WLAN
`Case 6
`
`1464
`
`
`
`
`1462
`
`Handover WLAN ->WLAN
`1463
`
`Figure 14
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 15 0f 32
`
`US 2005/0286466 A1
`
`IaCI.
`0.tI‘000|V
`
`xmmxzhwm
`
`:2
`
`“
`
`
`
`
`
`....=WUDEF—3.5coau=zmz§<.
`
`.2:.
`
`22:5
`
`..mm:...
`
`
`
`
`
`waazaofiu.
`
`
`
`..$2...
`
`35.2.3058
`
`€330.50»:
`
`.32...
`
`..22.,
`.regain—S52...
`
`
`
`_Nm_Stema.”
`
`Qa\u0on32.we:a33:.am._quE15
`
`
`\III‘IIO‘OO.......V—m—...
`
`
`
`.,,=5.Saom.:wu....,main—£05..
`,Sm.gw2:3.:2aaa_...
`
`:25.5.2.3a5
`
`1h..
`
`
`
`.(«d
`
`82,
`
`53¢
`
`....
`
`
`
`.8333ieqfiam
`
`
`
`Lflgzwz28was:..
`
`
`
`8.2..
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 16 0f 32
`
`US 2005/0286466 A1
`
`1 i i l I l 3 ! F
`
`igure 16
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 17 0f 32
`
`US 2005/0286466 A1
`
`Figure 1 7
`
`
`
`
`Rear View
`
`Side view
`
`From view
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 18 0f 32
`
`US 2005/0286466 A1
`
`Figure19
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 19 0f 32
`
`US 2005/0286466 A1
`
` 32>.mom
`
`
`
`
`
`
`25.;2:360:20xonaome
`
` ESQ
`
`32>«com32>2.5
`
`gmSEE
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 20 0f 32
`
`US 2005/0286466 A1
`
`Figure 21 a
`
`
`bam.9clF
`
`

`

`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 22 0f 32
`
`US 2005/0286466 A1
`
`as
`
`a:a.m.a.
`
`Eg;.mNomNg
`
`gmma
`
`26
`
`255m
`
`mu«.mmu
`
`mzeapemaa
`
`«NMNaanEa2:
`“mm“a:
`
`.ecwmadm
`
`mmEEG
`
`(3::«swaau»
`
`thN
`
`
`
`
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 23 0f 32
`
`US 2005/0286466 A1
`
`E255
`
` gggé
`
`:35:g“£83
`
`m:—_——_====m=======a
`
`%%Eisgmo:EH3%23952
`
`égafi
`
`m======u=m====
`
`----2
`
`E
`
`
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 24 0f 32
`
`US 2005/0286466 A1
`
`
`
` Basic Product 2501
`
`
`
`
`
`
`(M umnlouin'
`
`d’thstsB
`
`
`
`
`
`came 2503
`
`’ Software ‘
`
`
`
`
`
`Internet
`2508
`
`
`
`Figure 25
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`HIIIIIIIIIIIIIEEIIIIIIIIIIIIIIIH
`“m mum
`lawman m WORM
`arEIgI
`Scum-0m
`Gamma-2m:
`0:032:
`
`a I
`
`fillIII“Illllllfilllllllllllllllfl
`Dmmm PM!
`
`E?
`
`-
`
`_ l l -
`- - . I - - - - - -I I — - El:
`IIIIISI
`§ é’
`E- 5
`Mwmm
`(mums-small!)
`
`
`
`
`
`
`
`
`Figure 26
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 25 0f 32
`
`US 2005/0286466 A1
`
`Teloo Network 2702
`
`Authenticate
`
`04"
`
`
`
`Plus AP Info
`
`Figure 2 7
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 26 0f 32
`
`US 2005/0286466 A1
`
`
`
`
`
`2802
`
`
`2801
`User enters phone
`User selects from
`number
`
`
`
`phone book
`
`
`2804
`
`
`Search for APs in
`
`
`
`2803
`the area and display
`
`User chooses AP
`list to user
`
`
`
`
`
`
`2806
`
`Connect to AP via
`
`WLAN
`
`2807
`
`Send phone
`number to AP
`
`
`
`
`2808
`
`Wait for call
`connection
`
`
`
`
`
`
`
`
`
`
`:1. .
`
`CALL IN
`
`PROGRESS
`
`
`
`
`2811
`
`281 2
`Receive PCM
`
`Receive PCM
`
`2810
`
`
`samples from
`
`samples from AP
`
`Audio In stream
`User hangs up call
`
`
`
`2813
`
`
`Receive hangup
`
`
`from AP
`2814
`
`2816
`2815
`Send PCM
`
`
`Send PCM
`Send hangup to
`
`
`samples to Audio
`AP
`
`samples to AP
`
`Out stream
`
`2817
`
`Stop Streaming
`
`
`
`
`
`2818
`
`
`Disconnect from
`AP
`
`2819
`END
`
`
`(back to start)
`
`
`
`Figure 28a
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 27 0f 32
`
`US 2005/0286466 A1
`
`
`
`
`2821
`Wait for incoming
`connection from
`handset
`
`
`
`
`
`2822
`
`
`Receive phone
`number from
`handset
`
`
`
`2823
`
`
`Pedonn
`
`
`registration with
`SIP server
`
`
`
`2824
`
`
`Negotiate SIP
`INVITE with SIP
`sewer
`
`
`2825
`
`Connect to RTP
`
`endpoint
`
`
`2826
`
`
`CALL IN
`
`PROGRESS
`
`
`
`
`2827
`2828
`
`
`
`Receive PCM
`Receive RTP
`
`
`
`samples from
`packet from RTP
`
`
`
`
`
`handset
`_ 2830
`endpoint
`2829
`
`
`
`Receive hangflp
`Receive SIP BYE
`from RTP or SIP
`from handset
`
`
`endpoints
`
`2831
`2832
`
`
`
`Convert to RTP
`Convert to PCM
`
`
`
`packets
`samples
`
`
`
`2833
`2834
`
`
`
`Send SIP BYE to
`Send hang-up to
`
`
`handset
`RTP endpoint
`
`
`2835
`
`2836
`
`Send PCM
`
`
`
`Send RTP packets
`
`
`samples to
`to Proxy server
`handset
`
`
`
`
`2837
`
`Disconnect from
`
`_ handset
`
`
`
`
`2838
`END
`
`
`(Back to Stan)
`
`Figure 28b
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 28 0f 32
`
`US 2005/0286466 A1
`
`
`
`
`
`2841
`
`
`User enters phone
`User 5:18:35 from
`number
`
`
`
`
`phone book
`
`
`2843
`
`
`Search for APs in
`
`
`
`2342
`the area and display
`User choos
`list to user
`
`
`
`
`
`2845
`
`
`Connect to AP via
`
`
`VVLAN
`
`
`
`
`2846
`
`Perfo'rm
`registration with
`IP server via AP
`
`
`
`
`
`2847
`Negotiate SIP
`INVITE with SIP
`
`
`
`
`server via AP
`
`
`
`
`
`
`2848
`Connect to RTP
`endpoint via AP
`
`
`
`
`
`
`2849
`
`CALL IN
`
`PROGRESS
`
`
`
`
`
`2851
`
`2852
`
`Receive PCM
`Receive RTP
`2850
`
`
`
`samples from
`
`packets from AP
`Audio In stream
`User hangs up call
`
`
`
`
`2853
`
`
`Receive SIP BYE
`
`from AP
`2854
`2855
`
`
`
`
`Convert to RTP
`Convert to PCM
`
`
`
`2856
`packets
`samples
`
`
`
`Send SIP BYE to
`
`AP
`
`2857
`2858
`
`
`
`Send RTP packets
`Send PCM
`
`
`
`to RTP endpoint
`samples to Audio
`
`
`
`via AP
`Out stream
`
`
`
`
`2859
`
`Stop Streaming
`
`
`
`2861
`
`END
`
`
`(back to start)
`
`
`
`Figure 280
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 29 0f 32
`
`US 2005/0286466 A1
`
` 2863
`Wait for incoming
`connection from
`
`
`
`
`handset
`
` 2864
`
`
`
`IP address fix-up and
`fonNarding between
`
`
`handset and SIPIRTP
`
`endpoints, via Proxy if
`necessary
`
`
`
`
`
`
`2865
`Handset shuts
`
`
`down connection
`
`2866
`
`
`
`(Back to Start)
`
`
`END
`
`Figure 28d
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 30 0f 32
`
`US 2005/0286466 A1
`
`2868
`
`Peer-to-peer
`radio layer
`Discovery
`and Routing
`
`2869
`
`LAN Segment
`Discovery
`and Routing
`nclude PC Bridge
`
`Terminate to PSTN
`
`2870
`
`SIP Proxy
`Discovery
`arid Routing
`
`2871
`
`Figure 28c
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 31 0f 32
`
`US 2005/0286466 A1
`
`39-»Gym-ray
`Phone2900
`WLAN 2901
`R03?"2902 _903y n904
`“A
`
`G.a:eway
`2905
`
`
`Pam
`2906
`
`WF‘ISuNdP291O
`
`’I—‘ll
`
`
`WW
`mum:
`px Smart
`maul
`mu
`‘MM wry
`
`53:5": Emma N‘
` my
`Bmwtnd
`
`min-MN
`
`Figure 29
`
`3002
`
`Power Output
`
`3001
`
`
`
`3003
`
`dB Sensitivity
`
`
`
`3008
`3009
`'
`
`Power Output
`dB Sensitivity
`+20dBM
`~88dBm
`
`
`Figure 30
`
`

`

`Patent Application Publication Dec. 29, 2005 Sheet 32 0f 32
`
`US 2005/0286466 A1
`
`3100
`Bridge& Forward
`3101
`IP La er
`3102
`
`Hardware Control layer
`3103
`Driver
`
`
`
`
`
`
`
`
`
`
`
`b1 Active
`
`
`
`
`
`3104
`Interface
`
`3106
`Co-Existence
`
`3107
`80211 Subsystem
`
`3105
`Interface
`
`3108
`Bluetooth Subsystem
`
`3109
`RFCOMM
`3110
`chump
`3111
`HCI
`
`3115
`Beacon Wake Slot
`
`31 16
`Beacon Wake Slot
`
`311?
`Beacon TX Slot
`
`
`
`-<:’nn
`
`
`Time
`
`‘WTX—"W—In1eNal—><W>4———TX_->‘S->
`
`IGgure31
`
`

`

`US 2005/0286466 A1
`
`Dec. 29, 2005
`
`SYSTEM FOR PROVIDING MOBILE VOIP
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This patent application is a continuation in part of
`patent application Ser. No. 09/706,406 filed Nov. 3, 2000,
`the entire disclosure of which is hereby incorporated by
`reference.
`
`FIELD OF THE INVENTION
`
`invention relates to a system that
`[0002] The present
`provides VoIP over wireless LAN and WAN networks.
`
`BACKGROUND OF THE INVENTION
`
`[0003] The Internet came into being in its current form in
`1983 when all the computers connected to ARPANET—a
`military network—began using the same communication
`protocol. In 1986 ARPANET became NSFNET in a bid to
`link the USA’s supercomputers. E-mail began to be com-
`mercially available in 1990 at much the same time that
`Mosaic—the first worldwide web browser—became a use-
`
`ful product. The Internet, comprising mainly the WWW
`(world wide web) and e-mail is now an extremely important
`business tool.
`
`[0004] The world is now networked, much of this pro-
`vided by TCP/IP (Transmission Control Protocol/Internet
`Protocol) but ATM (Asynchronous Transfer Mode) is still
`dominant in telecommunications. Most major companies
`have access to the Internet and the Internet backbone runs
`thru much of our environment. This infrastructure is made
`
`up from largely fixed, rigid connections; wires, routers,
`switches and similar.
`
`[0005] Human beings tend to move around when engaged
`in work and leisure. An easy way to connect to the fixed
`network is needed for these mobile users. Mobile users are
`
`commonly envisaged as people using a cell phone or other
`radio device, but for our purposes a ‘mobile user’ is anyone
`away from their fixed home base.
`
`1. Wireless connections are inherently expen-
`[0006]
`sive as they use a rare resource—radio frequency
`spectrum—and require large infrastructure invest-
`ments.
`
`2. There are practical difficulties when away
`[0007]
`from home base, such as determining IP addresses,
`proxy server settings, negotiating billing and pay-
`ment and security and privacy concerns.
`
`[0008] Even the simple task of moving from one office to
`another within the same company can be fraught with
`complications and more often than not people fail to make
`connection when traveling away from home base. With so
`many companies relying on e-mail and the World Wide Web
`as a critical business tool, an inability to connect can prove
`costly to companies. In the last three years the ability to
`access the Internet has begun to migrate to mobile devices.
`Small mobile devices have tended to use a variety of
`specialist
`Internet access methodologies with varying
`degrees of commercial success. They all suffer from the
`limitation of low bandwidth and high cost.
`
`[0009] There are a number of methods by which users can
`get access to data from mobile wireless devices: SMS,
`
`HDML, WAP and I-Mode being the main standards. All of
`these standards suffer to some extent from problems such as
`limited bandwidth and complex authoring environments.
`
`In SMS (short message service) users can send and
`[0010]
`receive simple, short text messages from their phone. A
`server at the mobile phone service either routes them to other
`mobile phone users or provides a gateway that translates the
`messages and sends them as e-mail
`to Internet e-mail
`services. The gateway will also translate incoming email and
`send it to the user in SMS format. Although rudimentary,
`large successful businesses have been founded from sending
`these short messages demonstrating that people need data on
`the move and are prepared to pay for it.
`
`In HDML (Handheld Device Markup Language) a
`[0011]
`web site is composed using specially modified tags. A
`wireless gateway translates these tags so that the mobile
`device may view them. A mobile device equipped with a
`micro browser capable of interpreting HDML can display
`this information on a small LCD.
`
`In WAP (wireless application protocol) a web site
`[0012]
`is composed using WML (wireless markup language) and
`this information sent to a WAP gateway. The user gains
`access to this gateway either by dialing a RAS (remote
`access server) or by using a packet based system, commonly
`referred to as ‘always on’.
`
`In I-Mode specialist tags are again used to create
`[0013]
`pages formatted in compact-HTML. These are served over
`a gateway to users on a packet-based system.
`
`In the above systems a specialist gateway is used to
`[0014]
`provide output formatted for mobile devices. An alternative
`method of accessing the Internet from a mobile device is
`provided by fixed wireless systems such as Bluetooth and
`the IEEE 802.11 wireless LAN standard.
`
`In the 802.11 and Bluetooth standard two wireless
`[0015]
`devices establish a point to point or point to multi-point link
`using spread spectrum radio technology. The two wireless
`devices can be any type of electronic appliance—PC, PDA,
`Cell phone, microwave oven, home security system. This
`link replaces wires and does nothing to reformat the content
`of data.
`
`[0016] Another wireless standard that has reached ubiq-
`uity in availability but has very little usage is IrDA (Infrared
`Data Association). In the IrDA standard two devices with
`IrDA capability positioned near one other can communicate
`using infra-red beams. The standard suffers from two prob-
`lems. Firstly that the link is optical and therefore requires a
`clear line of sight. The devices must be positioned so that
`their ports are visible to each other or at
`least so that
`sufficient reflected light reaches the, ports. Secondly the two
`computers need to have their IrDA ports configured and
`switched on. This is a non-trivial task: The hardware must be
`
`enabled—commonly powersaving and compatibility issues
`mean that computers are shipped with the port disabled. A
`device driver must be installed. Once the physical link is
`available a logical link is needed to allow file transfer or
`access to the hard disk of the companion computer. Security
`and privacy must be ensured.
`
`

`

`US 2005/0286466 A1
`
`Dec. 29, 2005
`
`[0017] Looking at problems of getting Internet access
`when mobile a number of steps are required.
`
`1. Some form of driver software is needed to
`[0018]
`configure the user’s hardware to allow a link to be
`made.
`
`2. The physical link needs to be made. This
`[0019]
`may be by pointing the two computers at each other
`or connecting a back-to-back USB cable, which has
`been provided by, for example, the hotel at which the
`user is staying.
`
`3. The host user needs to enable and share
`[0020]
`certain services, such as printers and hard disks and
`network connections.
`
`4. The host user needs, itself, to log onto the
`[0021]
`Internet.
`
`5. The host user needs to act as a gateway for
`[0022]
`the connecting user,
`translating and forwarding
`packets onto the Internet.
`
`6. The IP address of the host’s interface needs
`[0023]
`to be configured to a non conflicting address with
`that of its Internet link.
`
`7. The IP address of the connecting user needs
`[0024]
`to point to the host user.
`
`8. The ports and proxy servers need to be set
`[0025]
`up. Even if no special set up is required a user who
`normally works in a corporate network with special
`settings will need to write these down and then delete
`them from the system, remembering to type them
`back in when returning to the corporate environment.
`
`to it a financial
`9. If the link has a cost
`[0026]
`transaction needs to be entered into with metering
`and billing.
`
`10. No simple solution is available to ensure
`[0027]
`a secure link.
`
`11. E-mail may or may not require yet more
`[0028]
`steps to enable.
`
`[0029] This multi-step process is fraught with difficulties
`and there are numerous potential points of failure. Most
`connections fail because either one of the steps cannot be
`completed, or each step is so time consuming that the user
`gives up before completing the task. Since mobile users are
`usually short of time, have limited resources (such as driver
`disks, spare cables) and have to configure multiple times as
`they travel thru different environments, the effort is very
`frustrating. Typically the above exercise is completed
`around 30% of the time with a mean time of effort of two and
`
`a half hours. Although many operating systems (such as
`Windows 2000““) allow connection sharing the implemen-
`tation of these makes the task very complex.
`
`[0030] An additional further complexity has been gener-
`ated by the lack of interoperability between IEEE 802.11 and
`Bluetooth. Since both standards operate in the same fre-
`quency spectrum the two systems will tend to interference
`with each other.
`
`is
`[0031] Additional difficulties occur when a firewall
`present. If a shared connection is obtained in the home or
`office, access to the Internet may be blocked or restricted by
`
`the activities of a firewall. The same technology that pro-
`vides the firewall capability may also track usage and web
`sites visited providing a risk to privacy. Additionally infor-
`mation that
`is sent or received may be logged causing
`considerable security risk.
`
`[0032] Although the cellular system provides some degree
`of roaming it provides no solution to inter-system roaming
`and uses expensive infrastructure, which results in high call
`cost. In addition the process of connecting a PC or PDA to
`a cell phone is complex and requires considerable recon-
`figuration of the device. The current mode of access to the
`Internet is predominantly through a one-to-one commercial
`negotiation. Each person has a connection to the Internet via
`their own ISP. When visiting someone else’s home obtaining
`access to the Internet is difficult. Calling the ISP requires
`another phone line. In the case of ADSL or cable systems the
`MAC address of the network adaptor is registered to the ISP
`so that a second user can’t use the connection. You can
`
`install a network and enable connection sharing in your
`OS—for example Windows 2000TM but
`this involves a
`number of complex steps. In addition there is a significant
`security implications to this. Generally home and commer-
`cial networks are not set up with the anticipation that
`roaming users will be physically connected to the network
`inside the Firewall. Thus many network services are not
`secured against internal access. (It is not uncommon for a
`corporate network running WindowsTM 2000 to have numer-
`ous hard disks shared without passwords.) Although the
`firewall blocks this from external access, a local connection
`would be inside the firewall.
`
`[0033] Although these problems have existed for some
`time,
`the emergence of Bluetooth and IEEE 802.11 are
`encouraging people to connect more often. While the above
`discussion is centered on the difficulty of human beings
`obtaining connection to the Internet it should be bourn in
`mind that autonomous machines have similar difficulties.
`Much talk is made of microwave ovens, video recorders and
`refrigerators talking together using home networks. It is also
`envisaged that automobiles will be similarly equipped.
`These systems are likely to become ubiquitous over the next
`five years as networking capabilities are built into appli-
`ances. These devices need to obtain services from some-
`where and need to obtain a connection to the Internet. It will
`
`be prohibitively expensive to give each device it’s own
`dedicated connection. The devices will also need services
`
`tailored to them. One can consider that an appliance once
`manufactured an shipped becomes a roaming device in need
`of connection to the Internet.
`
`[0034] As described above, there are two main types of
`wireless network present in the world today—wide area
`networks (WWAN) exemplified by cellular systems and
`local area networks (WLAN) provided typically by 802.11
`(also referred to generically as “Wi-Fi”) and Bluetooth
`technologies. Some examples are named in
`
`WWAN
`
`GSM
`UMTS
`W—CDMA
`CDMAZOOO
`
`TABLE 1
`
`WLAN
`
`Wi—Fi (802.11 a/b/g)
`Bluetooth
`DECT
`ZigBee (80215.4)
`
`

`

`US 2005/0286466 A1
`
`Dec. 29, 2005
`
`TABLE 1-continued
`
`WLAN
`
`WiMAX
`HomeRF
`HyperLAN
`
`WWAN
`
`FOMA
`TETRA
`GPRS
`HSCSD
`HSDPA
`EDGE
`
`[0035] Some technologies defy this simple classification.
`Bluetooth, when used in its low power mode, is often called
`a personal area network (PAN) and WiMAX technology can
`have extended range that rivals cellular macro-cell coverage.
`The distinctions can often be based on heritage and infra-
`structure ownership, but nevertheless today there is general
`agreement on the two classifications and the distinction
`between them—a WWAN connects to the core cellular
`
`network first, while a WLAN connects to a computer
`network first.
`
`[0036] A complication of WWANs in particular, but all
`networks in general, is that they distinguish between voice
`bearers and data bearers. Thus in GSM there are GSM audio
`channels and GSM data channels such as EDGE. For the
`
`purposes of this patent, WWAN-audio and WWAN-IP (-In-
`ternet Protocol) will refer to these distinctions respectively.
`Additionally, WWAN-VoIP (-Voice over IP).will refer to the
`situation of carrying voice over WWAN-IP.
`
`[0037] A number of methods have been proposed for
`implementing mobile voice and data systems so that they
`operate on both WWAN and WLAN based infrastructure. In
`implementing such mobile voice and data systems, these
`systems will have to deal with the problems of roaming and
`handoff between them. Roaming is the feature where a
`mobile phone can acquire a radio connection and signal to
`an authentication method to request a connection to services,
`while handoff is the feature where a mobile phone moves
`from one radio connection to the next maintaining a voice
`call or data connection with as little interruption as possible.
`When this interruption is not noticeable to the user the
`handoff is deemed “seamless.” Seamless handoff is not
`
`always an advantage. For example, when the user moves
`from a low cost connection to a high cost connection they
`generally want the transition to be made clear. The ability to
`do seamless handoff is an important feature of these systems
`even if, on occasion, it is deliberately switched off or the
`handoff made non-seamless through the use of notifications.
`When a mobile phone moves from one radio connection to
`another and the bearer technologies are the same we will
`hereafter refer to this as handover to differentiate it from
`
`handoff—for example when moving from one Wi-Fi access
`point to another.
`
`[0038] Two types of systems that have implemented
`mobile voice and data systems that operate on both WAN
`and WLAN based infrastructure are; (1) UMA-based sys-
`tems and (2) Bluetooth CTP-based systems.
`
`[0039] UMA-Based Systems
`
`[0040] The most prominent standard for WWLAN to
`WWAN interoperability is the Unlicensed Mobile Access
`(UMA) system, whose specifications can be obtained from
`www.umatechnology.org. UMA technology provides
`a
`
`method for using the cellular network infrastructure and
`specially modified handsets with WLAN Access Points
`(APs) to implement micro-cells in the network. UMA is
`described in relation to the GSM system but can be gener-
`alized to WWAN-Audio systems including 3G. We shall
`refer to the GSM case for this discussion. In the UMA
`
`system a handset is modified to send voice and data via a
`WLAN connection (such as 802.11 alb/g or Bluetooth).
`When using the WLAN connection,
`the GSM protocols
`(speech encoding and mobility management et. al.) are
`encapsulated and sent over WLAN via an access point which
`routes traffic to a UMA Network Controller (UNC) that
`de-encapsulates the protocol and sends it on to the cellular
`infrastructure. The primary object of the UMA specification
`is to make connection to the core cellular network as quickly
`as possible and then make all
`further communication
`through that core cellular network.
`
`[0041] Roaming is possible on UMA because the protocol
`encapsulation and emulation of a GSM base station allows
`the handset-AP combination to appear as a GSM cellular
`phone and GSM base-station even though the wireless
`protocol being used is WLAN. Handoff
`is supported
`between cells where the initial cell is a WLAN-AP and the
`handoff is made to a GSM cell or vice versa. In these cases
`
`the handset must simultaneously switch radio layer proto-
`cols while maintaining the GSM signaling and audio chan-
`nel connectivity.
`
`[0042] Because of this requirement to emulate the GSM
`cellular protocols (signaling and voice) in complex handoff
`scenarios these systems suffer from a number of practical
`problems: The GSM specification was not written with the
`assumption that
`the radio layer could change mid way
`through a transaction and it therefore organizes the signaling
`channel with precise time slot assignments, interleaved with
`the voice channels.
`Implementation of UMA therefore
`requires complex integration with the GSM software stack at
`a low level in the phone such that the phone can perform
`these handoff tasks.
`
`In particular the phone may signal a handoff ‘start’
`[0043]
`while using one radio layer and then signal the handoff
`‘completion’ using another radio layer. Because of these
`timing, slotting, encapsulation and signaling elements, the
`system design is complex with many points of integration
`between the WLAN signaling elements and the GSM ele-
`ments at low levels in the stack. Presently, such low level
`integration requires considerable engineering time to imple-
`ment as the software elements are real-time and time criti-
`
`cal—often upwards of 18 months for software work, manu-
`facturing and test prior to launch in the network.
`
`[0044] While these time scales are appropriate for prod-
`ucts in the mobile domain the convergence of fixed and
`mobile networks brings Internet development
`timescales
`into play with the problem that by the time deeply embed-
`ded, real-time software stacks have been implemented for a
`phone it is often the case that the Internet protocols have
`moved forward or the handset is obsolete before launch.
`
`Even with considerable design effort system performance
`can still be limited with handoff failures and interoperability
`restrictions.
`
`In addition, although the specification calls for the
`[0045]
`use of standard access points, in practice the access points
`have to be specially designed to cope with the timing
`
`

`

`US 2005/0286466 A1
`
`Dec. 29, 2005
`
`requirement inherent in the protocol management and this
`means the systems can not work with general purpose access
`points such as those deployed in the market already in
`hotspots, homes and offices. This need to specifically design
`each AP dramatically increases the total cost to deploy a
`system as every Access Point must be visited where the older
`units need to be swapped out and the newer unit installed.
`
`In addition UMA handsets require a full cellular
`[0046]
`infrastructure to operate, consisting of a Mobile Switching
`Centre (MSC) within the HPLMN (Home Public Land
`Mobile Network)
`interworking with location databases
`including HLR (Home Location Register) and VLR (V1sitor
`Location Register) or SGSN (Serving GSM Support Nodes).
`This requirement is disadvantageous because it is architec-
`turally complex—data packets must
`transit
`through the
`cellular system even when they originated from WLAN
`Access Points as Internet Protocol (IP) and are often des-
`tined to terminate via IP, say as a VoIP call, thus putting
`unnecessary stress on these systems and causing numerous
`unnecessary protocol translations that introduce latency and
`potential for failure. A call which might have been routed
`locally perhaps over only a few hundred yards of IP cabling
`will have to transit through the entire cellular core network.
`So a UMA protocol based system is essentially incompatible
`with peer-to-peer routing and SIP based RTP stream direct
`connection paths. Also, many companies that want to utilize
`voice and data services over wireless do not possess core
`cellular