Page 1 of 38
`
`Unified Patents Exhibit 1006
`
`

`
`US 8,594,298 B2
`Page 2
`
`(55)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`6,631,186 B1 "‘
`6,768,792 B2 "‘
`6,845,155 B2‘
`7,330,721 132"‘
`2002/0172347 Al "‘
`2003/0161459 Al *
`2004/0028208 A1 "‘
`
`10/2003
`7/2004
`1/2005
`2/2008
`l l/2002
`8/2003
`2/2004
`
`Adamsetal.
`.......... .. 379/201.12
`Brown et al.
`. 379/207.14
`
`Elsey ..................... .. 379/266.04
`Bhatia et a1.
`............. .. 455/422.1
`Elsey ......... ..
`. 379/221.01
`McBlain et al.
`. 379/220.01
`
`Camazza et al.
`379/221.01
`
`OTHER PUBLICATIONS
`
`Hyam, Kristy, “CA Application No. 2,5 56,892 Oflice Action Dec. 7,
`2010", , Publisher: CIPO, Published in: CA.
`Nash, Michael, “EP Application No. 057233322 Supplementary
`Search Report Apr. 12, 2011", , Publisher: EPO, Published in: EP.
`Canadian Patent Application No. 2,556,892, “Call Management,”
`Avaya Integrated Cabinet Solutions, Inc., Office Action dated Sep.
`21, 2011, 4 pages.
`
`* cited by examiner
`
`Page 2 of 38
`
`Page 2 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 1 of 20
`
`US 8,594,298 B2
`
`
`
`.Eo_=m_n___mE8_o>
`
`
`
`mo_.m8_>mo
`
`
`
`.¢.m>__88_§___$oX:$.25
`
`Ease
`
`mmcoqmmm
`
`Ego
`
`awcoqmmm
`
`Page 3 of 38
`
`
`
`m_...2n_.8:
`
`
`
`Emsommcazb_>__o<._$3
`
`m_=cos_um=a=__mE$xm_
`
`gmEo=8o._.3:$3
`
`as
`
`bmzcbo>__mn___aE-mom.m.mw_._mo—.
`B.‘.
`
`
`
`
`
`
`
`Page 3 of 38
`
`
`
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 2 of 20
`
`US 8,594,298 B2
`
`
`
`
`
`
`
`
`
`
`
`:o__8m>_mmmc_m:n.2o=__u=§_E83.2.238E0\)_H_H_H_3...:Qs__._§..aD36659.
`
`
`
`
`
`Eoo.ucon=m:©c_o_._Ecozwoczoc=8.832395__uEm
`
`mom/.\...a2.2.3...n=>
`
`
`
`meccaEauoci:.mEm.>u=mu._wEm_o335:3S22.u.3gain:8m....=>
`
`SN
`
`an
`
`
`
`EN./.3....__>aso_£._mE/o.2.3sea;3.8..8_mD
`
`
`
`
`
`.c£m_ME.on:8aoahumane.m_._n__>oz.5E353:
`
`
`
`
`
`E8.u=oa=w:©:_uv_.._._mE__wE8_O>mc_>_ao2.2mm2uu<__wEm
`
`
`
`
`
`
`
`SNSN .6232m=o_>2n_.6do9659u:c_Eooxu__o
`
`N.0_u_»\8~
`
`
`
`231/E@E2......see
`
`
`
`
`
`m_.oN1/xmB«.«K.o$aces.23¢:
`
`
`3.35.8.5§___§_85>gee222.8as3:S_.S_..E>.n3w
`
`§.aeam.§xS__§83>2.23mHED...
`
`
`
`
`
`
`
`>5::o>46»3..xon__uEuu_o>_mcow._mamou3oc_Eufiomucafi__uo
`
`
`
`
`
`
`
`
`
`
`
`
`
`mx_..._mo._._<0>w<mFzms_mo<z<s_._._<0
`
`
`
`
`
`uoumcmsan2.8:2on835::22.;95mucosaSoȤ=m3:9:
`
`Q3«mmm:ocn_._=o>.5«ow;..35
`
`.5__Em2Bo:
`
`=uo<SN\(HEE§§_._23:asam25.559.5amNqua
`
`32¢:
`
`Page 4 of 38
`
`Page 4 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 3 of 20
`
`US 8,594,298 B2
`
`
`
`
`
`__aE8_o>9.3.82zoesco=3E.u=__mEwvcomU/\:
`
`
`
`
`
`
`
`
`
`mmsfimz_%<.§232.._&<Eu
`
`8m(_Ia:Luwl|_
`
`8m8“mE
`
`\8m
`
`mom
`
`EHEa:5
`
`QEs.
`
`o__%zas2_a__8_=§_:3Bums__>_§25E_U.\;mom
`
`
`
`__uEuo_o>mc_>_$E5:3u.c9E
`
`
`
`b_>=o<u_£.2o__a2_ow«Zn...»22»:.20El.
`
`
`
`
`
`
`
`Neweéoo>2as»:a_%<
`
`<8»Eago:228
`
`
`
`mmomDo._..os_Em"mac:..:__5
`
`omomD850msm"85022.8
`
`gzéuo>5.umamcmi__mo32
`
`
`.8».5amNnew
`
`=o_.3Eo>annew
`
`.325:=5
`
`
`
`...9__=$mcofiEwEomm:ms___wo50>«mooseucumu_=>=o<sum8uu<»o:2_..._
`
`
`
`
`
`.mmmcms___mo50>.5Em
`
`59.5Em:.n2m
`
`.5._Em2‘$01
`
`
`
`mx:._mn_4._<U>m<mu.zms_mw<z<s_4._<0
`
`
`
`
`
`Page 5 of 38
`
`Page 5 of 38
`
`

`
`SU.
`
`M
`
`B
`
`M4
`
`US 8,594,298 B2
`
`
`
`
`
`Pmx_.:mn_._._<o>m<mwzm_2mo<z<s_fi<o
`
`
`
`
`
`ocean.Ngas:E25__8E§.:2E8.as_um«.5.8._U.\.mom
`
`__sE$_o>m:_>_600._cog;
`
`
`
`
`
`h.sEaEa..__&
`manQis.
`
`
`
`
`
`a_>_s<25.eu_=86msea.»222.is8/vow
`
`NOmomD350msm“$502m__wo
`
`99|%mmomD8509.2a__8_222.335.8%D__aE8_o>22%“Eco:82.8
`3.13
`
`Ll$5329....:oEomm=m_2=mo.=_o>wmocgovanuo_._>=o<gumEuu<%._ummcms_
`
`
`
`
`__mo50>.5wow
`
`N83,2E.:._%< x._o>>.<ucomcafi=322
`
`Page 6 of 38
`
`
`
`
`
`__uE8_c>mc_>_oow._cogs=o=wu==o_.___uEuucawUI\:
`
`
`
`
`
`
`
`
`
`
`
`mmssuw>._>=o<50>o>38»_.a<xo__o
`
`mom8NV.mw¥\.com
`
`Page 6 of 38
`
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 5 of 20
`
`US 8,594,298 B2
`
`
`
`
`
`=uE8_o>m:_>_oo2cos:E_.8c_§___uEuucowHT.\:
`
`
`
`
`
`
`
`
`
`nmszowz_>_.o<:3»«>38>_.E<xo__o
`
`
`
`
`
`EE
`
`
`
`._>_s<223Exlmom
`
`mommomm.my_n_\.oom
`
`
`
`2505.>E8.._o_.8_._=o::8.ucow.>._>_.oaa.=.Co.._H_.\J
`
`
`
`
`
`
`
`
`
`__uE8_e>m:_>_8o..:2?0:23
`
`
`
`>._%<253.o_%o._umcameo29.9.._...__oU/vow
`
`
`
`
`
`@©®E5%EE
`
`mmomu a__€s_2m__8
`
`as(gas9.,__s
`
`
`
`$8. 5:3:22.8S_.3__E>a.35
`
`
`
`/ _uEm:>=>=u<:53..:_>=o<>2Banzai=ao
`
`
`
`
`
`m:=:EEoo$3.52=uo>2
`
`50>Q3aw“N.55
`
`
`
`...9__.§mcofiEmeoancmz=mo50>3020new.o.mz_>_fi<sum3E2mucosa.
`
`
`
`
`
`
`
`.wmmcw_2__mo50>.5flow5o>.5amanew
`
`as._.82Bo:
`
`
`
`
`
`mxsda._._<O>w<m_#zm_2mw<z<s_..._<U
`
`
`
`
`
`Page 7 of 38
`
`Page 7 of 38
`
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 6 of 20
`
`US 8,594,298 B2
`
`8m
`
`ms
`
`wowu
`
`
`
`.m_nm__m>mc32mm:_=om22...o__nos_s8_>>m:o>__:2“3Bo:man2o_nm._:o>
`
`
`
`
`
`
`
`
`
`«Ema_Em.Emo-~mm-8¢now8m-8~.omou_._maoo
`
`223EHm8¢.$m-2~no88-8m-2~HzE22
`
`so
`
`amwe ”mEmz
`
`£8
`
`EE5EH5:
`
`$8
`
`m.0_u_
`
`%%
`
`Soas
`
`
`
`
`
`on.0:___3m.m__mon__>$5.onEmEmm.m.omEoo>o:om._oEw8>__E£9___50>2$2:9:
`
`
`
`
`
`
`
`
`
`
`
`53:.E5282.Bmn__>ozmmom.mo_oco9mEw.o38c_:9».o22.m.3can...:m__mon=>
`
`
`
`
`
`Page 8 of 38
`
`Page 8 of 38
`
`

`
`U.S. Patent
`
`Nov. 26,2013
`
`Sheet 7 of 20
`
`US 8,594,298 B2
`
`NE
`
`am
`
`
`
`mx3ma._._<0>m<mFzm_2mo<z<s_._._<U
`
`
`
`
`
`
`
`
`
`
`
`Eoo.ucon:wc@=_o_x.€uE”__mEoo_o>m:_>_oo2.8mu2uu<__mEm_
`
`
`
`
`
`8E0nos.
`
`
`
`85095.u__.§2Em ._.§822©O=GEO:
`
`
`
`
`
`u__..§95.0.5229.:s_>a__%_2om
`
`
`
`.>_&<v_u__oEab_>ao<82am59333£59__...=mm=_>=om3:2"..32:o>
`
`
`
`
`
`
`
`
`
`
`
`=:£oo22E0.8>_Eo._._=o222...o__nos_.5o>”mm_=>_.o<.
`
`
`
`
`
`
`
`
`
`
`
`s8.Eo..=2@=_o_._sao_.8=_§___m.83225__mEm
`
`$3n=>>E«swam
`
`
`
`D.._o=wo«:05?22.3._8_m
`
`
`
`
`
`
`
`FOR.l\I:scoeamoa
`
`
`
`_m:u_>=E_5.3.00=50Rum
`
`
`
`mmsuouE250So>EuEa:
`
`
`
`
`
`asuocmfi>__ammooo:mo>m;=o>
`
`
`
`
`
`£.m~+E.o8acofio__..os_
`
`
`
`
`
`§.~.B~.w8acofi850
`
`an
`
`o§-o8.ono
`
`HOCOSQ@EOIQCOSQ
`=o_.8_.=o>5new
`
`%._.82so:
`
`.5o>.5Emn_.%.m
`
`mucosa
`
`=5».5EmNqflm
`
`
`
`Eoacmz__mo
`
`Page 9 of 38
`
`Page 9 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 8 of 20
`
`US 8,594,298 B2
`
`On Vacation
`Substitute...
`
`Page 10 of 38
`
`Page 10 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`SheetN9 of 20
`
`US 8,594,298 B2
`
`/ 300
`
`CALL MANAGEMENT: EASY CALL DELUXE
`
`Set Up Your Call Manager
`
`Add or Edit Activities and choose your call Management phone settings
`My Call Manager: At Work
`
`A-my name: Atwork
`Calls to Home: SendtoVoioerna’| H
`
`302
`303A
`
`Calls to Mobile:5 303B
`
`Calls to Office: Rin Office
`
`E
`
`303C
`
`Mygjyg
`LVM
`Commuting
`
`New Activity...
`
`304 \1z| Click here to enable Schedule for this Activity
`
`Pm
`
`Repeat
`
`305
`
`_/E For this activity. Send text notification to my Mobile
`Phone when receiving voicemail
`
`-/‘El Send email notification when receiving voicemail
`
`Click Apply to save your Activity Settings
`
`308
`
`Apply
`
`FIG. 9
`
`208
`
`209
`
`Page 11 of 38
`
`Page 11 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 10 of 20
`
`US 8,594,298 B2
`
`CALL MANAGEMENT: EASY CALL DELUXE
`
`Set Up Your Call Manager
`
`/ 300
`
`Add or Edit Activities and choose your Call Management phone settings
`My Call Manager. High Priority
`Amy Hngnpnon-ty
`Callsto Home: Sendtovoioenafl fl
`
`M'.y‘E:%u“_
`
`FIQTILX
`
`fllg
`
`Calls to Mobile: Ring Mobile
`
`302
`303A
`
`303B
`
`Calls to Office:fl 303C
`
`304 \-{'_'I Click here to enable Schedule for this Activity
`
`Repeat
`
`}305
`
`_/-E] For this activity, Send text notification to my Mobile
`Phone when receiving voicemail
`
`“E Send email notification when receiving voicemail
`
`Click Apply to save your Activity Settings
`
`308
`
`FIG. 10
`
`Commuting
`
`New Activig...
`
`Page 12 of 38
`
`Page 12 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 11 of 20
`
`US 8,594,298 B2
`
`lvull {'1
`Call Mana er
`
`0
`
`Page 13 of 38
`
`Page 13 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 12 of 20
`
`US 8,594,298 B2
`
`
`
`m8_>moam>__oo
`
`
`
`!
`
`msssm§_aEoo
`
`co_.8_§EEoo88>
`
`co:8__&<
`
`SE
`
`\.
`
`o=o._n_
`
`<2:
`
`Krl
`
`§:oE_
`
`wfl
`
`NP.®_u_
`
`=8
`
`EmEmmm:m_>_
`
`gm_=uos_
`
`
`
`week..3:
`
`mmmnsma
`
`<8.
`
`=8
`
`Eoeommcmg
`
`ago
`
`_I_l\.
`
`
`
`m:_E_=m.2358
`
`
`
`=o_.8_§EEoo8_o>
`
`:o_.8__&<
`
`Sm.
`
`Page 14 of 38
`
`Page 14 of 38
`
`
`
`
`
`

`
`&U
`
`tH..w
`
`02.m3
`
`US 8,594,298 B2
`
`
`
`
`
`1£5m._.._.M|..madmm<§eeo____m__m.§ .§,%w—%§s§s._o>
`
`a8m_§=_P__<
`
`3.__o>aEzésam22&as2,Ego%an$3mE
`
`32%_.
`
`=m_2a<:m
`
`nE.:..M
`
`Page 15 of 38
`
`
`
`§:_.§m_,_£35QécassV__§¢z
`
`.215.2..m\s_§__&<
`.3<32,»:Q“Gn_ow.28m8e.__
`
`Page 15 of 38
`
`

`
`U.S. Patent
`
`Nov. 26,2013
`
`Sheet 14 of 20
`
`US 8,594,298 B2
`
`3.0_..._
`
`85>IIIIn=Eo»
`
`
`
`
`
`.oEmoomcmfixm_m8._
`
`
`
`
`
`
`E22555.__mo-=o__8__&<Emvcofimz
`
`§>m=<
`
`page__8VI.
`IQNE.
`
`ozsmamd6:3
`
`
`
`_m_:mo.o.mm_9_>>
`
`
`
`_oEmommo_m.__>>
`
`Page 16 of 38
`
`Page 16 of 38
`
`
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 15 of 20
`
`Us 8,594,298 B2
`
`8:8E>__8
`
`
`
`.€mn_$o_>mo
`
`we<zm
`
`uoEmEon_
`
`25;as
`
`25;as_§§§_
`
`o_nm_.m>8<zm-s_on_38__e___83co_§=m_.Eoo
`m:_EmEon_
`m=_EmEon_
`
`_e___255,n_
`
`mass;
`
`._m§<o\z_>>
`
`amas
`
`ms88¢#sci
`
`
`
`:o_§:m=__ooam;
`
`
`
`822:5§_==...asEoov
`
`o2€o_.8__228n_
`
`
`:o_§=a_Eooco_§=m__Eoo
`
`8mtmE_m>__§__u_.082
`
`
`.=aE2.<
`
`Q
`
`fig
`
`
`
` 3o_mo._625mm
`
`
`
`_eEooQ=o_§=u_.Eoo>.¢%._w=%mm.w_..,_
`
`o=o_._n_
`
`Emeoomcmz=3
`
`mags.
`
`mla
`
`Eon.
`
`gO0
`
`ow:
`
`.
`
`ma
`
`_m_z%_$m
`
`.€8Eoo.§:_
`
`LI
`
`mm¢_o__3.a_:mo..§=_
`
`<2:
`
`Page 17 of 38
`
`_m_.:8.m._E_
`
`mmm_2_>>
`
`.€8Eoo.S=__mmH.%Se
`
`£8
`
`0::
`
`9.0_n_
`
`Page 17 of 38
`
`
`
`
`
`
`
`
`
`
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 16 of 20
`
`US 8,594,298 B2
`
`3.8E_,__8sn_I_....l.a__8
`
`
`
`E8$wm,.ooEmE%m._flm._m,k,..m_o_.E
`
`
`>__8Wm._m_§.._$~_
`=mn_Eou.eE_I['\\\\\\\V..
`Emz:o.._III8.
`
`
`om:
`
`>.§_Eoo.§=_
`
`m8_9_;._o_=$_§=_
`
`<S_.
`
`
`a3-_2m_932am_H.a___$e..__
`we83m=%___%ommmm_es>
`
`
`
`__mo>=8Eoo.9E_wasoi8:mac:cemcmwe$__moBEoofimmz-=_oEmm_mo:mm<_V_,_
`
`
`83|0::
`mmHw|ms.
`
`I
`
`2.22L
`
`.
`
`
`
`
`=o_.8_om=o_§=m==oo£3.o=o_E.%...>>s_on_:8
`
`
`
`
`
`8__$9n_$m_o__\s_oB=So.=Eoov:o_§=m==ooco_§=m_.Eoo.E%:m=<§__u_ones.
`
`
`
`5:83e§8__3.25n.mmnfl&%¢_.,__gasom832_8m
`m2Ill88
`
`I.3.0_u_
`
`Page 18 of 38
`
`Page 18 of 38
`
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 17 of20
`
`US 8,594,298 B2
`
`”°!1d0SWS"J!1°N||9° >->->>->->—>->->->->->->->-zzzz
`”°“d0'59”‘3"4"°N"e° zz>->->-zz>—>->->->->->-zzzz
`
`zcuaogAaqMaAg|aa
`
`‘_?‘—-F‘—
`
`.
`[.C]|80!I\3C|KJ8A!|6G
`Cnepoado <rl.D-r-¢‘O1—¢.\l(\l(\l1—¢\l(")1—\—¢\l¢'\lC\l(VC\l
`
`92.
`
`$2.
`
`93
`
`99
`
`22.
`
`92.
`
`NS:
`
`E5E832
`was:82
`
`M255882
`
`
`
`mm<o.E882.mm<o.Eog32
`
`$_<o.Eoo82
`
`mm<o.Eon_as
`m_m<ow_,_on_82
`
`
`
`8:/at
`
`E,GE
`
`
`
` 8“.3.zo_B<..~m_EoH$_mm:3SN5%zozowmoEo.Emm:38“5%zo_5<m._._mo_2:.&m_m:3SN3%zo_5<mzox2%:as
`
`
`
`
`
`(]|dnOJ9.l8||B3
`
`
`m|.__mo_2..m._m<.__<><z:3m_m<oE8828N5zo_Sw.mzozmm<oI._.zoo82SN8%zO_._.o<..m.__mo_2|m._m<.__<><Ims_oIammm<o.:,_oo828m«.3zo:.o<mm_u_o:m._m|<.__<><mzoz3m_m<o.:,_889SNmm?zo_S<
`
`zmmmom3mm<o._.z.Oo_.8O3EE_5m_:m9...m._mK.__<><z=Ewm:.__u__.25%zo_._.o<..n__>EE:.a,m:m.zH_mow3mm<o.E8_.85%m_5Ewm:w
`
`
`m_m<oE8Fl82P::<uma3mammmmmm.Wm9WMwWM...WW
`£0oz_.3—mm_m._.mxm_<_2m_._m_._.as
`
`
`
`
`
`
`mm<om:,_on_82SN3%zo_B<.mzo.z.zmmmommmzoIQB
`
`mw
`
`Page 19 of 38
`
`
`
`
`
` com2%---23SN8%zo_5<ms_o=m:ms_<><m.__mos_E83%---z3SN5%zo_5<Baas.zmmmomms.o_._3...
`
`
`
`
`
`Cl|9|"8J9'-‘Tn
`
`mm~._
`
`~m~.v
`
`mm~._
`
`mm~._
`
`oo~__
`
`r¢N._
`
`Nm~__
`
`mo~__
`
`mm~__
`
`mm~__
`
`c-__
`
`FNNFF
`
`m~N__
`
`-N_r
`
`mow_r
`
`c.m_F
`
`__w__
`
`N.w__
`
`Page 19 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 18 one
`
`US 8,594,298 B2
`
`
`
`mass:._§
`
`
`
`
`
`$52.9__2..._m.%_§2.__ssz
`
`
`s§..__:mms§_,_:$§E__:as§..__am=5%e::L:,..u..._m..._
`
`
`
`w_,_:§:._EIIIIIasasam52as52“.8asawfigsa_%_s§.
`
`
`$.22,Q3§_§.=¢%.%_Qa2§___22$3§§.e_.__
`
`
`
`.____._.<.____._.<,___.:.<
`¢_§.:_a__2eXEM1_§§x
`n_Ess_xox:E3|:
`
`asasaama.5EE
`
`
`
`v_5.<se§a§.awa<o7.awa<2lawfie$5EOE.$¢»e=%._¢E$_m.=_''.8:5E832.
`
`_~_.__%_§_
`
`
`
`
`
`$fi._m.Mm_z“$332223......22.ass§__=._2e_§__2a__s
`
`
`
`IIII—82as%82.
`
`
`
`m_g_%§_.§s__%§:__:_so_uwe>__§_w__§.__.._<m.w_s__n_2‘GE
`I._29__~:$_o:§=ea.
`
`
`..“.Jn
`
`
`
`TmztsizoT.
`
`In>.§s8.§=_
`
`E202aw
`
`§_>.m___a_.o25
`Es.2
`
`Page 20 of 38
`
`Page 20 of 38
`
`
`
`

`
`3PS.U
`
`H
`
`0
`
`2
`
`02f091
`
`US 8,594,298 B2
`
`
`
`
`
`WSE0222:2,.268»_E9==o50>
`
`
`
`
`
`
`f.2m__moo.m__moo.m__mo8502m__mo.u£ooEo:2m=~oso:95:2...__mo8:sues55>$__._en_so>
`cozmuczocm...o_o._s>SEO90oz95:905s,use:A%=wEvsoc,a,
`
`
`
`
`v..2._a=D23.2m22
`
`sEHEEEEHEEEIEEE
`gggggéénuaug5£5
`
`\a
`
`sec...Em
`
`Page 21 of 38
`
`2.o_u_
`
`
`
`wcozawmm_o.._305E9:uo.um_omOnom_mcmomoEo._n_
`
`
`
`
`
`Page 21 of 38
`
`

`
`U.S. Patent
`
`Nov. 26, 2013
`
`Sheet 20 of 20
`
`US 8,594,298 B2
`
`82$¢__§,_mm?
`m=E._mo
`
`§_%
`
`osé
`
`.2
`
`H22§_<.
`
`
`
`9m__§._<w_$__mo
`
`om.o_“_
`
`25:a<9:
`
`Ilm<§
`
`9:Egg
`
`§_.5w_$__8S8
`
`
`
`
`
`.m_m.=_w__2_3m.§so_mw
`
`$__8
`
`
`
`2:QEma;2_;wm._o__mo
`
`Page 22 of 38
`
`Page 22 of 38
`
`
`
`
`
`
`
`

`
`US 8,594,298 B2
`
`1
`CALL MANAGEMENT
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`This application claims priority fiom U.S. Provisional
`Application No. 60/546,409 entitled “Personal Call Manage-
`ment System,” filed Feb. 20, 2004, the disclosure ofwhich is
`incorporated herein by reference.
`This application is related to U.S. patent application Ser.
`No. 11/060,642 entitled “Dynamically Routing Telephone
`Calls,” filed on the same date herewith, the disclosure of
`which is incorporated herein by reference,
`This application is related to U.S. patent application Ser.
`No. 1 1/060,085 entitled “Informing Caller of Callee Activity 15
`Mode,” filed on the same date herewith, the disclosure of
`which is incorporated herein by reference.
`
`10
`
`BACKGROUND OF THE INVENTION
`
`l. Field of the Invention
`This invention relates generally to management ofcommu-
`nications such as telephone calls, and more specifically to
`techniques for handling, routing, and configuring incoming
`telephone calls.
`2. Background of the Invention
`Many people (callees) have a multitude of telephone num-
`bers (TNs) that they give out to potential callers. Typically
`this set ofTNs includes home, office, and cell phone numbers.
`Ifthe caller knows more than one TN for the callee, the caller
`selects the most likely number to reach the callee and often
`leaves a voicemail message before trying another number.
`The caller is burdened with determining the most likely
`sequence of calls to reach the callee. This often results in one
`or more voicemail messages (home, office, cell) even if the
`caller ultimately reaches the callee. This situation slows the
`process of establishing a connection, increases costs, and
`reduces the probability ofmaking a live connection, due to the
`effort and time required of the caller. In addition, multiple
`voicemail messages are a burden for the callee.
`What is needed is a system and method that automatically
`handles, routes, and manages telephone calls so that callers
`do not have to guess whichnumber to call to reach a particular
`individual. What is further needed is a system andmethod that
`allows a callee to specify how incoming calls are handled, and
`that responds dynamically to real-time conditions at the time
`a call is placed. What is further needed is additional function-
`ality that improves the process of configuring, routing, and
`processing incoming telephone calls.
`
`SUIVIMARY OF THE INVENTION
`
`The callee is ofien in a much better position to know how
`they can be reached than the caller, since the callee often
`knows in advance where they will be physically located
`(home, office, or car), and how reachable they will be. The
`present invention provides techniques for allowing the callee
`to specify how incoming calls will be handled. The user can
`specify call management parameters according to various
`factors, including time of day, day ofweek, manual override,
`caller identity, caller input (for example specifying whether
`the call is urgent), called number, location of callee (for
`example using GPS, cell phone tower location, tower trian-
`gulation, lnstant Messaging presence, Smart Tags, or other
`locating technology), location of caller, recent phone use,
`explicit selection (using web page, cell phone application,
`dial-in Interactive Voice Response (IVR), or other method),
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`implicit system-learned (adaptive) understanding of the
`callee’s call -receipt desires, or the like. In addition, any com-
`bination of the above factors may be used.
`Calls may also be sent to voicemail without ringing the
`user’s phone, based upon filtering or explicit selection.
`Callees may configure their routing and filtering by behaviorl
`location/activity mode. Example modes are: At Home, At
`Work, At Work in a Meeting, Commuting, and on Vacation.
`The selection ofactive mode can be made explicitly or implic-
`itly. Explicit mode selection can include any combination of
`time-of-day and user input using cell phone, web, and/or
`phone IVR. For example, a cell phone may have a physical
`“mode” button or a mechanism for accessing an on-screen
`menu from which the user can select among a number of
`modes. Implicit mode selection can include location informa-
`tion (including velocity calculated from sequential position
`samples), computer calendaring information, past behavior
`of the user, and the location of other users (“suppress calls
`while I’m in the presence of the CE ”). Global Positioning
`System (GPS) technology may be used to route calls (based
`on mode); the destination telephone need not be equipped
`with GPS detection technology. For example, if the user is
`carrying a cell phone (or other location-aware device) and
`walks into his or her office, the mode may change to “At
`Office” and calls will be routed to the office phone.
`Difierent ring types may be used based upon any combi-
`nation of dialed TN, calling party, mode, caller location,
`callee location, and/or the like. For example, the specific ring
`ofa user’s home, oflice, or cell phone may be selected by the
`system based on whether the caller is a family member or
`business associate (filter based) or whether the caller origi-
`nally called the home TN or office TN (dialed TN based).
`The callee configures the system with mode and filter pref-
`erences,
`in order to define how various calls should be
`handled. Configuration can take place via any type of user
`interface, including a web interface, phone-based IVR, or cell
`phone application. Configuration includes characterizing
`potential callers into groups and setting up filters for each
`group. Filters specify eitherto which phone to send the call, to
`send it to voicemail, or to give the caller a choice. The filter
`configuration for a group can change based on time of day,
`explicit command from the user, and/or location of the user.
`Configuration also includes defining various activity modes
`during which different call management rules should be
`applied.
`the system can learn (adapt and
`In one embodiment,
`extrapolate from past user behavior) in order to select current
`mode or to place calling TN into filters. This configuration
`can take place automatically by the system or the system can
`present suggestions to the user for approval. The system can,
`for example, learn not to take calls from party A when the
`callee is in the presence of party B.
`In one embodiment, a call to any one of a callee’s existing
`phone numbers is automatically routed to the callee at his or
`her designated phone. At the callee’s discretion, certain call-
`ers will ring through and others will automatically go to a
`single voicemail box (or otherwise handled).
`In another embodiment, location information from a cell
`phone carried by the callee can automatically change the
`user’s filtering and/or activity mode throughout the day. For
`example, if the callee is within 20 feet of his or her office
`phone, the oflice phone is the phone that will ring for any, or
`some selected subset, of people calling the callee.
`The system of the present invention provides any or all of
`the following features, alone or in any combination:
`multiple TNs for a single callee: the callee can specify
`different handling procedures for each TN;
`
`Page 23 of 38
`
`Page 23 of 38
`
`

`
`US 8,594,298 B2
`
`3
`
`a mechanism, such as a web-based user interface, for speci-
`fying and implementing call handling procedures that
`depend on any or all of a number of factors;
`callee (and/or caller) location detection, for example using
`GPS or other techniques, for determining which call-
`handling mode to use;
`time of day detection for determining which call-handling
`mode to use;
`caller identification, for determining which call-handling
`mode to use;
`adaptive techniques for learning callee preferences for call
`handling;
`call forwarding to other phones or to voicemail or email;
`call screening;
`default modes for call-handling (for example, At Home, At
`Work, At Work in a Meeting, Commuting, OnVacation);
`user interface for modifying and configuring call-handling
`modes;
`automatic switching fi'om one mode to another, for
`example when conditions, time period, location, or envi-
`ronmental factors change;
`user-initiating switching from one mode to another, for
`example using cell phone commands, web-based inter-
`face, telephone IVR, or the like;
`a user interface for specifying call handling settings and for
`changing modes.
`Further features of the invention, its nature and various
`advantages will be more apparent from the accompanying
`drawings and the following detailed description.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The accompanying drawings illustrate several embodi-
`ments of the invention and, together with the description,
`serve to explain the principles of the invention.
`FIG. 1 is a block diagram depicting an architecture for
`implementing the present invention according to one embodi-
`ment.
`
`FIG. 2 is a screen shot depicting a telephone setup screen
`according to one embodiment.
`FIGS. 3, 4, and 5 are screen shots depicting call manager
`setup screens according to one embodiment.
`FIG. 6 is a screen shot depicting a VIP list management
`screen according to one embodiment.
`FIG. 7 is a screen shot depicting an example of a call
`management summary screen according to one embodiment.
`FIG. 8 is a screen shot depicting an example of a user
`interface for selecting among modes via a mobile phone
`handset.
`
`FIG. 9 is a screen shot depicting a call manager setup
`screen wherein some calls are converted to voicemails,
`according to one embodiment.
`FIG. 10 is a screen shot depicting a call manager setup
`screen wherein calls to different phone numbers are handled
`differently.
`FIG. 11 a screen shot depicting an example wherein a
`current activity mode for a callee is displayed on a ca1ler’s
`device.
`FIG. 12 is a block diagram depicting an architecture for
`implementing callee identification by means other than
`NANP telephone numbers, according to one embodiment.
`FIG. 13 is a block diagram depicting an example of a
`detailed architecture for implementing the present invention
`according to one embodiment.
`FIG. 14 is a block diagram depicting one architecture for
`implementing call management functionality according to
`the techniques of the present invention.
`
`4
`FIG. 15 is a block diagram depicting an architecture for
`implementing the present invention by integrating with a
`wireless carrier using WIN or CAMEL.
`FIG. 16 is a block diagram depicting an architecture for
`implementing the present invention using DNP.
`FIG. 17 is a table containing an example set of rules for a
`callee, including a set of op-codes.
`FIG. 18 is a block diagram depicting an architecture for
`implementing a disaster-resi1ientDNP architecture according
`to one embodiment of the present invention.
`FIG. 19 is an example ofa call routing matrix according to
`one embodiment.
`FIG. 20 is a block diagram depicting an architecture for
`in-network and out-of-network call routing using an imple-
`mentation of the present invention.
`
`DETAILED DESCRIPTION OF THE
`EMBODIMENTS
`
`Terminology
`For purposes ofthe description herein, the term “callee” is
`used to refer to an individual or entity that is being called or
`that may be called at some point in the future. The term “user”
`is used interchangeably with “callee.”
`A “caller” is a personwho places a call to a user, or attempts
`to place a call, or potentially could place a call.
`A “dialed telephone number (dialed TN)” is a number
`dialed by a caller. It may or may not be associated with an
`actual telephone device.
`A “delivery telephone device” is a device that can be used
`to receive calls.
`A “user profile” is a set of user configuration information
`specifying call management parameters.
`A “mode” is a callee’s operational mode, such as “At
`Home,” “At Work,” etc. As described below, a mode can be
`selected explicitly by a user or implicitly according to the
`user’s profile.
`A “filter" is a defined scheme for identifying a subset of a
`user’s potential callers and to treat calls from them in a dis-
`tinctive way.
`Additional terminology is defined herein within the con-
`text of the following description.
`The present invention is now described more fully with
`reference to the accompanying Figures, in which several
`embodiments of the invention are shown. The present inven-
`tion may be embodied in many difierent forms and should not
`be construed as limited to the embodiments set forth herein.
`Rather these embodiments are provided so that this disclosure
`will be complete and will fully convey the invention to those
`skilled in the art.
`For illustrative purposes, the following description sets
`forth the invention in terms ofhandling a call that is placed by
`dialing a telephone number (TN) such as a North American
`Numbering Plan (NANP) number. However, one skilled in
`the art will recognize that the techniques set forth herein can
`be used for handling communications that are initiated in
`other ways. In particular, a caller can specify a callee using
`any type ofcaller identifier, whether a dialed TN, a text string,
`a non-NANP digit sequence, or the like. The term User
`Address (UA) is used herein to denote any such mechanism
`for identifying a callee.
`In the following description the term Delivery Telephone
`Number (Delivery TN) refers to the telephone number (or
`UA) ofthe device or system that terminates a call for, or to, a
`user. Delivery TN5 connect to delivery devices such as a
`telephone, a voicemail platform (traditional or e-mail deliv-
`ery only), attendant Interactive Voice Response (IVR) sys-
`
`10
`
`20
`
`25
`
`30
`
`35
`
`45
`
`50
`
`55
`
`60
`
`65
`
`Page 24 of 38
`
`Page 24 of 38
`
`

`
`US 8,594,298 B2
`
`5
`tem, or the like. A Dialed TN (the TN that the caller dialed)
`may or may not have the same number as one of the callee’s
`Delivery TNs; a call to the Dialed TN may or may not be
`connected to the device addressed by the identical Delivery
`TN. Thus, in some cases, a Dialed TN is virtual and is not the
`address of a physical delivery device.
`As will be described in more detail below, in one embodi-
`ment the present invention manages a callee’s set ofUAs and
`the real-time mapping ofthose UAs to delivery devices. Calls
`placed to a UA may be routed to one (or more) ofthe delivery
`devices corresponding to Delivery TNs. The system uses a
`combination of modes, filters, caller selection (attendant),
`busy state, and no-answer state to detennine whether and how
`a call should be routed to an appropriate delivery TN.
`The present invention can be implemented in symmetric or
`asymmetric fashion. A symmetric implementation is one in
`which all delivery TNs are in the set ofdialed TNs; otherwise
`the implementation is asymmetric.
`Referring now to FIG. 1, there is shown a block diagram
`depicting an architecture for implementing the present inven-
`tion according to one embodiment.
`Caller 101 places a call via a local phone switch 102 such
`as Central Ofiice (CO), Mobile Switching Center (MSC), or
`Private Branch Exchange (PBX). The call goes through pub-
`lic switched telephone network (PSTN) 103 to destination
`switch 104 such as CO 104A, MSC 104B, or PBX 104C. The
`present invention may be implemented regardless of the par-
`ticular type of switches 102, 104 being used at the origin or
`destination. Destination switch 104 queries call management
`module 105 to determine where to route the call. Module 105
`checks user profile database 105A to obtain call management
`settings for users. In one embodiment, external input 120
`(such as callee location, caller identifiers, and the like) is also
`used by module 105 to determine where to route the call.
`Module 105 sends a response to switch 104 indicating the
`desired routing for the call. The appropriate delivery device
`108 (including for example home telephone 108A, wireless
`telephone 108B, olfice telephone 108C, voicemail platform
`106, and/or the like), is given the call, and the device handles
`the call as though it were received directly. Callee 109 then
`receives the call via the selected delivery device 108.
`In one embodiment, when voicemail platform 106 handles
`a call, it can query module 105 to determine whether a voice-
`mail message should be delivered as an email attachment 110
`to email reader 111 for receipt by callee 109. In another
`embodiment, when voicemail platform 106 handles a call, it
`can activate an alert (e.g. a flashing light, a tone, or an indi-
`cator on a display) on any or all of delivery devices 108,
`according to callee preferences as indicated in module 105.
`In one embodiment, each query from destination switch
`104 includes, for example, the dialed TN and the cal1erTN (if
`known). One skilled in the art will recognize that other infor-
`mation may also be included inthe query. In one embodiment,
`in response to receiving a query, module 105 returns a desti-
`nation TN which may represent a delivery device 108 corre-
`sponding to the dialed number, or another device 108, or
`voicemail platform 106. Voicemail platform 106 canbe in the
`same network as destination switch 104, or it can be acces-
`sible over PSTN 103.
`
`In one embodiment, voicemail platform e-mail delivery
`query 107 includes the dialed TN and the caller TN (if
`known). In response, module 1 05 provides a delivery flag (yes
`or no), and an e-mail address.
`The present invention can be implemented in connection
`with any type of telephone system, including home tele-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`S0
`
`55
`
`60
`
`65
`
`6
`phones, olfice telephones, and wireless telephones, regard-
`less of telephone equipment and regardless of telephone ser-
`vice provider.
`Referring now to FIG. 14, there is shown a block diagram
`depicting one architecture for implementing call manage-
`ment functionality according to the techniques ofthe present
`invention. When caller 101 places a call to callee 109, the call
`is routed to callee 109 based on rules stored in service data-
`base 105A.
`'
`Caller 202 may call a landline TN or wireless TN ofcallee
`109. In the landline case, FIG. 14 illustrates “post-ring” man-
`agement of the call. Landline phone 1420 is rung by con-
`nected CO switch 102A1 in LEC 1401. When phone 1420
`goes unanswered, the call is forwarded (using a prc-provi-
`sioned “Call Forward Busy/No Answer” switch feature) over
`Public Switched Telephone Network (PSTN) 103 to Wireless
`Cam'er’s Mobile Switch 104B where it is then managed.
`Mobile Switch (MSC) 104B sends a query over SS7 network
`1403 through one or more Signaling Transfer Points (STP)
`1404 through signaling gateway 1407 to Application Proces-
`sor 105B.
`
`Application Processor 105B queries database 105A and
`returns a reply containing routing information that will be
`used by Mobile Switch 104B to route the call. Possible rout-
`ing destinations include callee’s 109 wireless phone and car-
`rier’s voicemail platform 106.
`In some implementations, queries from Mobile Switch
`104B may pass through the Home Location Register (HLR)
`1402. In a similar fashion, when caller 101 places a call to the
`callee’s 109 wireless phone, rather than callee’s wireline
`phone 1420, the call is routed from originating switch 102A.2,
`through PSTN 103 to MSC 104B. MSC 104B manages these
`calls “pre-ring,” before the mobile phone is rung. In some
`cases, caller 101 is connected to an automated attendant (In-
`teractive Voice Response, or IVR; not shown in FIG. 14).
`For example, if callee 109 shares landline 1420 with a
`family member, MSC 104B can be instructed to temporarily
`connect caller 101 to voicemail platform 106 in a way that
`causes voicemail platform 106 to play prompts under the
`direction of an Application Processor (not shown) by way of
`Messaging gateway 1408. Calls may also be managed in an
`Enterprise 1413. In this case, PBX 1411 queries the service
`for routing information and voicemail 1412 may be used in
`the enterprise.
`In one embodiment, signaling gateway 1407, database
`105A, application processor 105B, and messaging gateway
`1408 communicate with one another via Local Area Network
`(LAN) 1406. Similarly, components ofenterprise 1413 com-
`municate with one another via Local Area Network (LAN)
`1409. LANs 1406 and 1409 communicate with one another
`using Internet Protocol (IP) 1202, and LAN 1406 communi-
`cates with VM 106 using IP 1202. Gateway 1410 connects
`LAN 1409 to PSTN 103. STP 1404 communicates with sig-
`naling gateway l407 via SS7 1405.
`In one embodiment, user profile database 105A stores the
`following information in order to specify a callee’s call man-
`agement settings:
`Set of dialed TNs (logical or physical)
`Set of delivery TNs (addresses to delivery devices)
`Set of modes (At work, At home, etc.)
`Mapping of dialed TN to delivery TN for each dialed TN
`and mode combination. This mapping may include the
`creation and application of filters, which are sets of
`calling party TNs that control the mapping. Further
`description appears below.
`
`Page 25 of 38
`
`Page 25 of 38
`
`

`
`US 8,594,298 B2
`
`7
`Authentication of dialed TNS and delivery TNs to confirm
`they are under the control ofthe callee. Further descrip-
`tion appears below.
`Call Management Configuration Interface
`According to one embodiment ofthe present invention, call
`management settings described above are specified by the
`user via a user interface such as a website, via a cell phone or
`PDA, or by default initi