(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2003/0101343 A1
`
`Eaton et al.
`(43) Pub. Date:
`May 29, 2003
`
`US 20030101343A1
`
`(54) SYSTEM FOR PROVIDING CONTINUITY
`BETWEEN MESSAGING CLIENTS AND
`METHOD THEREFOR
`
`(22)
`
`Filed:
`
`Nov. 27, 2001
`
`Publication Classification
`
`(76)
`
`Inventors; Eric Thomas Eaton, Lake Worth, FL
`(US); David Jefl'ery Hayes, Lake
`Worth, FL (US); Von Alan Mock,
`Boynton Beach, FL (US)
`
`Correspondence Address:
`MOTOROLA, INC
`INTELLECTUAL PROPERTY SECTION
`LAW DEPT
`8000 WEST SUNRISE BLVD
`FT LAUDERDAL, FL 33322 (US)
`
`(21) Appl. No.:
`
`09/995,338
`
`Int. Cl.7 ....................................................... H04L 9/00
`(51)
`
`..
`(52) US. Cl.
`............. 713/170
`
`(57)
`
`ABSTRACT
`
`A messaging communication system (10) includes a plural-
`ity of messaging clients (12). A first messaging client (14)
`establishes a first communication connection (16) operating
`using a plurality of client data (25). The first messaging
`client (14) transfers the plurality of client data (25) to a
`second messaging client (20). The second messaging client
`(20) establishes a second communication connection (22)
`operating using the plurality of client data (25).
`
`PLURALITY OF CLIENT DATA
`
`31
`
`ACCOUNT IDENTIFIER
`
`gg
`
`32
`
`SERVER IDENTIFIER
`
`PLURALITY OF CONTACT DATA
`
`FIRST ACCOUNT INFORMATION
`
`FIRST ACCOUNT IDENTIFIER
`
`FIRST ACCOUNT CONTACT INFORMATION
`
`SECOND ACCOUNT INFORMATION
`
`SECOND ACCOUNT IDENTIFIER
`
`SECOND ACCOUNT CONTACT INFORMATION
`
`Nth ACCOUNT INFORMATION
`
`Nth ACCOUNT IDENTIFIER
`
`Nth ACCOUNT comm INFORMATION
`
`PLURALITY OF USER PREFERENCES
`
`FILTERS
`
`ALERTS
`
`FONTS
`
`
`
`36d
`
`PLURALITY OF SESSION DATA
`
`|
`
`1
`
`APPLE 1009
`
`APPLE 1009
`
`1
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 1 0f 24
`
`US 2003/0101343 A1
`
`
`
`EHHEHHEH6BEE
`
`
`
`zofiomzzoo2828232285E
`
`EH6652mm:51:
`
`<29EH65m:
`
`N.AUNBNa
`
`mEH6652mm:“65555:
`
`
`
`5666652mm:
`
`6285mm:.6:5556
`
`mzsmmm:3:95928mm
`
`
`
`282822228ozoomw
`
`285%on
`
`
`
`EH662558:928mm
`
`zommm
`
`
`
`2.55:am::55:52:52:952%
`
`
`
`
`
`E58228282822228
`
`
`
`EH6653mm:
`
`<22EH6
`
`MHHEHHEH6
`
`2
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication May 29, 2003 Sheet 2 0f 24
`
`US 2003/0101343 A1
`
`gg
`
`
`PLURALITY OF CLIENT DATA
`
`
`
`
`
`.31
`
`32
`
`ACCOUNT IDENTIFIER
`
`SERVER IDENTIFIER
`
`
`
`PLURALITY OF CONTACT DATA
`
`FIRST ACCOUNT INFORMATION
`
`
`
`
`FIRST ACCOUNT CONTACT INFORMATION
`
`FIRST ACCOUNT IDENTIFIER
`
`SECOND ACCOUNT INFORMATION
`
`SECOND ACCOUNT IDENTIFIER
`
`SECOND ACCOUNT CONTACT INFORMATION
`
`Nth ACCOUNT INFORMATION
`
`
`
`
`Nth ACCOUNT IOFNTIFIFR
`
`Nth ACCOUNT CONTACT INFORMATION
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`PLURALITY OF SESSION DATA
`
`FILTERS
`
`ALERTS
`
`FONTS
`
`FIG.2
`
`36
`
`3
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 3 0f 24
`
`US 2003/0101343 A1
`
`
`NVHCESE283mm52
`
`
`
`W+n_/\mmozufibzmEmma.22
`
`“VxMHmezmoHonmmmmzyz
`
`
`
`mhz<¢Hqum<monmmmmgyz
`
`<2oHszoou<
`
`<2Hz<mHlom<m
`
`m:2HHz=o°o<
`
`
`
`m:Hz<mHlom<m
`
`z:oHhzzooo<
`
`z:~z<mHloz<m
`
`
`
`>monH=onmmwm5H2
`
`
`
`
`
`onmmmmeZHu<mmm=;#z
`
`ZOHmmmmgo>HH4<m=4m
`
`/.\.Q.V
`
`
`
`
`
`onmmmmoZHo<mmuzozoomm
`
`
`
`
`
`zmHmHHZWQHonmmmmazoomm
`
`
`
`
`
`onwmmmoZHo<mmm=pmmH;
`
`
`
`
`
`mMHmHHzmaHonmmmmhmme
`
`<~<o
`
`mN~z<mHosz<mé<~pz<mHlom<¢
`
`mmQHHz=ouu<
`
`2NoHhzsooo<
`
`zNHz<mHoHHm<m
`
`
`
`
`
`.mhz<¢Hlom<monwmmmozoomm
`
`
`
`
`
`mmozmmmuummonmmmmazoomw
`
`
`
`
`
`>thonmonmmmmazoomm
`
`
`
`
`
`>mo~mH=onmmmmazoomm
`
`
`
`m.-nUNRN
`
`
`
`
`
`>thonmonmmmmHmzHg
`
`
`
`
`
`mmozmmmmmmmonwmmmHmmHm
`
`<_9Hszouu<
`
`<PH2<¢HOHpm<m
`
`m_9HHzaooo<
`
`
`
`m.~z<mHoHHm<m
`
`2_OHHz=ooo<
`
`z_pz<mHoHHm<m
`
`
`
`>mohmH:onwmmmHmsz
`
`
`
`
`
`mpz<mHlom<monmmmmHmZHm
`
`4
`
`

`

`Patent Application Publication May 29, 2003 Sheet 4 0f 24
`
`US 2003/0101343 A1
`
`onmmmm
`zm2<pmm=Hp22HHz=ooo<
`_.Nmz<hmm=HH“Nmo<mmm=N9Hszooo<
`__m=<hmm=HH"_mo<mmm=_QHpzpooo<
`vv
`
`>onmH:
`
`5
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 5 0f 24
`
`US 2003/0101343 A1
`
`
`
`598o.—m._m<o
`
`ozo
`3%:
`
`8%,EEawom
`
`ozma<mzEco:Ezmmzpm
`
`ga
`
`kmEozmz
`SuzzoommPZH
`
`II...E.I
`
`E1lllll4mm5:9:
`
`
` _zowqw‘wdnc._5de_mmmE5i”:5:22mm:4
`
`mmVm
`
`
`
`
`Em:
`
`”SEW—”:5
`
`Eon
`
`mm
`
`we
`
`
`
`$26;”mm:
`
`mm
`
`Eon(Zn1'382
`
`5:050:55
`
`aman
`
`85;
`
`o28<mmmz
`
`E55
`
`mm<2wk
`
`
`”8555mo<msmEozmz
`Emiomagmamm.
`
`
`<53
`
`<P<o
`
`:95mm
`
`ananR_|
`
`
`mum:_
`
`mmQR.8
`Flllllllllll
`
`
`1-|[III-Ili
`
`
`:154.2965:359%
`
`“so:V;m.AUNRN
`
`
`
`6
`
`
`
`
`
`
`

`

`h
`
`42f06t
`
`US 2003/0101343 A1
`
`992
`
`W5%M$8
`
`w3
`
`S1IIpIII3_ZOE§E<_m_”952$:
`
`2_rIIfiIéIIL.
`
`Patent Application Publication
`
`mm
`
`>mo=mz
`
`mo<mohm
`
`moH>mo
`
`
`
`>mozmzuoH>mo
`
`Pamzzoommsz
`
`no.
`
`NE
`
`:3
`
`5demm
`thozHo8.5.2”SE
`
`mommmoomm
`
`w:5302
`
`
`ozfiwwmmz
`
`m0H>mo
`
`><4mmHa
`
`
`
`Mum:moH>mo
`
`mo<mmmHzH
`
`hzmHJQ
`
`mgHmomm
`
`
`
`mo<mmm2 mm
`
`
`
`
`
`>mozm2<H<oHZMHJQ
`
`mmmmoo<
`
`
`
`<H<oFZMHJQ
`
`HOAm>mozm2
`
`
`
`onmmmmmo<mmmz
`
`>zozm:
`
`mmo<mmm2
`
`>mozm2
`
`
`
`>mozmzm0H>mo
`
`12::ng
`
`V9
`
`vm
`
`(.8
`
`x858.
`E385%
`E38$8
`ESEEmm
`mm’
` 8>L/
`I'—I
`.0ACNE.
`
`7
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 7 0f 24
`
`US 2003/0101343 A1
`
`m9
`
`0Hos<
`
`mm>Hmo
`
`onwH>u4mpans
`
`UQH>mo
`
`oZHo<mmm=
`
`
`mo<mOHmHZMHAQPHDOKHQHzmzH
`
`
`>mozm2HZHHJQ“use;1mm:
`
`mAHmomm
`
`—I|||
`
`IIIIL
`
`_mummz<mp__<29.8mmmm“
`
`emoH>\mm
`
`mm>Hmo
`
`
`
`<H<oHzmHAQ
`
`
`
`>mozm:m4m<o
`
`mmAJOMHzoo
`
`zgoo\m=
`
`mmpmm>zoo
`
`mgm<oob
`
`ozmo<mz
`
`xomMAm<o
`
`>zozm2
`
`FQMZZOQMMPZH
`
`xomu4m<o
`
`_*O\H
`
`IIIIIxomm4m<o
`
`N*o\H
`
`XOm~4m<o
`
`mo<mmmp2Hmum:
`
`
`
`Aozhzoowhozum
`
`mm>Hmomz<mh
`
`pmeH
`
`k.AVNRN
`
`8
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 8 0f 24
`
`US 2003/0101343 A1
`
`928.33:
`
`monmmmm
`
`<23
`
`052%:
`
`
`
`:85:55mm
`
`E>Em“5&3:
`
`
`
`zommmuoE528228
`{I
`
`figEH55m:
`
`”952%:EH65.:
`
`
`
`E>EmzofifimwfizsooEEOozmzmmmz5m:
`
`NR.E$330255%:gohiéam
`
`238228
`
`928mm
`
`Ea23222228EEO2.5%:28%A.mpzmfio
`
`<53
`
`E>Em
`
`EHEES
`
`E>Em
`
`Manama.
`
`282822228
`
`zofiszzoo
`
`gum5::ngE525%d1
`
`:5:9528%mm
`
`9
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 9 0f 24
`
`US 2003/0101343 A1
`
`ozoomm928mm
`
`
`952%”:
`
`$553
`
`2de_
`
`xZHJm:
`
`mo<mmu2
`
`ozBfimz
`
`EH6
`
`xZHAZBOQ
`
`mo<mmm2
`
`mm>mmm
`
`mu<mmm2.
`
`mm>mmm
`
`mwmmoo<
`
`mm
`
`zmpszmz<mH
`
`mwmgmmHz
`
`zmhm>m
`
`muggompzoo
`
`mmmHmommzw
`
`mm<m<p<o
`
`10
`
`10
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 10 0f 24
`
`US 2003/0101343 A1
`
`mp<>HmE
`
`25>
`
`
`
`xzospmz<mm<moH;
`
`02Ho<mmm2
`
`52mm
`
`
`
`
`
`xzo;_mz<mm<A<QO4
`
`mowmagma
`xmoEm—zGEL
`
`oZHo<mmmzEm:
`pzmflo.1.
`
`
`523::I
`
`mm>mmmI2:8mNew
`
`
`
`
`
`
`xmoEm—zozoomm
`
`
`
`03%.;mmN02Ho<mmm2ozoomm
`
`newmagma
`
`vmw
`
`
`
`mainxmozfimz95.:
`
`92553215583533295:
`EH6EH8
`
`
`
`HzmfloON
`
`11
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication May 29, 2003 Sheet 11 0f 24
`
`US 2003/0101343 A1
`
`ozE<mmmzIEDEozHo<mwwz9E:
`HzmfloEH6
`
`
`
`0mm
`
`NN.AUNBN
`
`
`
`025<mmw2azoomm
`
`Emflo
`
`ow
`
`NE
`
`mo<wmm2
`
`E>mmm
`
`.3SN
`
`cum
`
`éosmzwas0285mm:5:
`25¢023:::
`
`8N
`
`:26
`
`8mV25932:
`
`.VQNNmN
`
`xom5mg95:
`
`
`
`QQNxomm4m<oozoomm
`
`12
`
`12
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 12 0f 24
`
`US 2003/0101343 A1
`
`928mm
`
`0255me
`
`can
`
`I--Eganp23-I
`
`mpzmflouZHo<mmu2
`
`ozHo<mmmz
`
`
`
`259wosz<mmm2azoom
`
`mEN
`
`mo<mwm2
`
`mm>mmm
`
`
`
`mpzmfloozHo<mmm2
`
`-IIMOLEEEu.--
`
`oz5<mwmz
`
`55%052mm:2:«mm
`
`oz5<mmm=
`
`@2558:
`
`ozHe<mmm2
`
`EH5
`
`13
`
`13
`
`

`

`Patent Application Publication May 29, 2003 Sheet 13 0f 24
`
`US 2003/0101343 A1
`
`296
`
`ESTABLISH FIRST
`COMMUNICATION CONNECTION
`
`293
`
`AUTHENTICATION
`REQUIRED
`
`?
`
`YES
`
`NO
`
`300
`
`FIRST
`AUTHENTICATION
`
`302
`
`YES
`
`316
`
`
`TRANSFER
`AUTHENTICATION
`
`KEY
`
`TRANSFER
`
`FIRST MESSAGING
`CLIENT ACCUNULATES
`SESSION DATA
`
`DCJA
`
`NO
`
`308
`
`VERIFY SECOND
`MESSAGING CLIENT
`
`YES
`
`YES
`
`306
`
`VERIFY
`
`SECOND NESSACINC
`
`
`CLIENT
`
`?
`NO
`
`3’0
`
`TRANSFER
`CLIENT DATA
`
`314
`
`312
`
`SECOND
`
`
`COMMUNICATION
`AUTHENTICATION
`KEY
`CONNEQCTION
`
`?
`
`.318
`
`
` OPERATE SECOND
`COMMUNICATION CONNECTION
`
`
`WITH CLIENT DATA
`
`
`AUTHENTICATION
`REQUIRED
`
`’?
`
`YES
`
`324
`
`ESTABLISH SECOND
`SESSION CONNECTION
`
`320
`
`322
`
`SECOND
`
`AUTHENTICATION
`
`FIG. 13
`
`14
`
`14
`
`

`

`Patent Application Publication May 29, 2003 Sheet 14 0f 24
`
`US 2003/0101343 A1
`
`.3CM?
`
`
`
`FIRST MESSAGING
`
`CLIENT ACCUMULATES
`SESSION DATA
`
`
`
`
`
`USER INPUT
`YES
`
`FIRST MESSAGING
`
`DEVICE
`?
`
`
`
`
`USER INPUT
`SECOND MESSAGING
`DEVICE
`9
`
`
`?
`
`
`
`
`ACTIVATE
`SECOND MESSAGING
`CLIENT
`
`
`SECOND
`MESSAGING CLIENT
`
`CONNECTION
`?
`
`
`
`
`333
`
`TRANSFER OF
`DATA AFFIRMATIVE
`
`FIG.14
`
`15
`
`15
`
`

`

`Patent Application Publication May 29, 2003 Sheet 15 0f 24
`
`US 2003/0101343 A1
`
`.302
`
`
`FIRST MESSAGING
`
`
`CLIENT ACCUMULATES
`SESSION DATA
`
`
`
`
`FIRST MESSAGING
`
`
`DISCONNECT
`
`?
`
`NO
`
`TRANSFER
`CLIENT DATA
`
`3’0
`
`.136
`
`YES
`
`DISCONNECT FIRST
`
`
`
`.138
`
`CLIENT - MESSAGING CLIENT
`
`
`
`
`
`
`
`
`DISCONNECT FIRST
`MESSAGING CLIENT
`
`
`
`
`DISCONNECT
`
`
`FIRST MESSAGING
`
`
`
`CLIENT
`CLIENT DATA
`
`
`9
`
`
`CONTINUE FIRST
`COMMUNICATION
`CONNECTION WITH
`
`YES
`
`340
`
`
`
`.124
`
`
`
`OPERATE SECOND
`
`COMMUNICATION CONNECTION
`
`
`WITH CLIENT DATA
`
`
`FIG.15
`
`16
`
`16
`
`

`

`Patent Application Publication May 29, 2003 Sheet 16 0f 24
`
`US 2003/0101343 A1
`
`
`
`FIRST MESSAGING
`
`
`CLIENT ACCUMULATES
`
`
`SESSION DATA
`
`.3IE?
`
`
`
`
`DATA PORTION
`
`;346
`
`TRANSFER
`CLIENT DATA
`
`
`?
` CLIENT
`
`
` CLIENT
`
`
`
`
`CLIENT DATA
`
`PORTION =
`
`PREDETERMINED
`
`
`
`CLIENT DATA
`PORTION =
`REQUIREMENT
`
`(548
`
`DATA REQUIREMENT
`?
`
`.3Ei2
`
`PREDETERMINED
`PORTION
`?
`
`
`
`
`.356
`
`.3553
`
`N0
`
`IDENTIFY CLIENT
`DATA PORTION
`
`
`
`TRANSFER CLIENT
`DATA PORTION
`
`FIG-16
`
`17
`
`17
`
`

`

`Patent Application Publication May 29, 2003 Sheet 17 0f 24
`
`US 2003/0101343 A1
`
`359
`
`
`FIRST COMMUNICATION
`CONNECTION
`
`
`
`
`
`
`
`PARTICIPATE
`Nth MESSAGING
`SESSION ?
`
`NOTIFY OF
`TRANSFER
`
`YES
`
`NOTIFICATION
`?
`
`
`
`N0
`
`ESTABLISH SECONO
`COMMUNICATION CONNECTION
`
`FIRST COMMUNICATION
`CONNECTION INCLUDES
`
`Nth MESSAGING SESSION
`
`
`thTRANSFER
`
`MESSAGING
`SESSION
`
`?
`
` CLIENT DATA
`37D
`
`
`TRANSFER
`CLIENT OATA
`
`
`318
`
`
`
`?
`IIIIIIIIIIIIIIIIIIIIIIIIIII
`
`
`
`N
`
`INCLUOES Nth
`MESSAGING SESSION
`
`3'0
`
`312
`
`SECOND
`COMMUNICATION
`CONNECTION
`
`YES
`
`372
`
`Nth MESSAGING SESSION
`mxmm
`COMMUNICATION CONNECTION
`
`
`18
`
`18
`
`

`

`Patent Application Publication May 29, 2003 Sheet 18 0f 24
`
`US 2003/0101343 A1
`
`378
`
`FIRST
`
`
`
`MESSAGING CLIENT
`PARTICIPATION
`
`?
`
`
`FIRST COMMUNICATION
`CONNECTION INCLUDES MULTIPLE
`
`USER MESSAGING SESSION
`
`
`MULTIPLE USER
`MESSAGING SESSION
`
`
`
`
`
`
`
`?
`
`TRANSFER
`DATA
`
`
`
`YES
`
`310
`
`TRANSFER
`
`CLIENT DATA
`
`JEN?
`
`SESSION
`
`TRANSFER MESSAGE
`
`
`
`
`383
`
`SECOND MESSAGING
`CLIENT PARTICIPATION
`
`
`FIG-18
`
`19
`
`19
`
`

`

`Patent Application Publication May 29, 2003 Sheet 19 0f 24
`
`US 2003/0101343 A1
`
`.me
`
`0&1th
`
`onmmmm “v
`ZOEEQ:95Egg
`
`
`zammmseamE:
`nmn_Nm.
`
`“5:5252:52
`
`mMHmezmoH
`
`20
`
`20
`
`

`

`Patent Application Publication
`
`M
`
`02a
`
`4
`
`US 2003/0101343 A1
`
`Swe»m5.8...m.$225
`m$3$25:
`.22.$3:82.52.52..92mm9,.....22..was:32m..3321;QE...
`
`
`
`n5.585352
`02w$.23:
`
`
`QNAVE”Emma:26255$...
`
`
`
`mo<mmm2>5;choz<02min?..;h_m_._>o<mm._<
`
`
`mo<mmmz><._n_wHooz<ozmmnzozSo2.?ozmm
`238%@2858:313.262asE:530F
`92:82;ago8wvmmN”mm“.mMFIhauzmmwéaN.5.8.3531;
`
`szmmmmo.EEEE:.052mm:52
`
`3%.a..oooFommzno»:92mm
`59:32aNmum:A £5352:
`
`.932:92mm..m.F.._m._>o<m5<.mmoz:ozmmON?
`
`
`
`
`
`
`mamBF$1..92mm
`.302.5E:vs:82.8“.5..9%mm»
`
`1.8o...Buz20?.ozmmmfivoz<azmmnz
`
`9.8%8:20:was:.82.18:2083FES
`882.0FEm:
`
`
`
`
`
`Fzmflo0285mm:0mm.
`
`.053mm:52
`
`._.<_._FNmum:C502
`
`m._m_<._H<><SFEm:
`
`:5.FEm:#592
`
`
`
`Fzmflo02Ho<wwm2szE
`
`mmm
`
`0F20moo.FEm:
`
`
`
`5de”.2858...“cam:
`
`mmNRN
`
`
`
`55...228mm
`
`5deo2H0<wmm2
`
`ON
`
`”828&de
`
`
`
`.52..52..9mm
`
`:82;szoFmmm:
`
`mc<mmm2mum:oz<
`
`Nmum:E.ozum2.
`
`OFmagma:92
`
`
`
`
`
`52..”SF.”2.539
`
`
`
`onmmmmoZHo<wmm=0F
`
`9%
`
`
`
`m¢<mmm2><._n_mHo
`
`@2858:OF
`
`onmmmw
`
`
`
`Fzmzmooflsozxg>18.sz
`
`
`
`onmmmmbingo
`
`5.25:<29
`
`5de22mm...
`
`21
`
`21
`
`

`

`pm
`
`0..
`
`b
`
`a
`
`US 2003/0101343 A1
`
`
`2NW“AVEm235:2::9523:82
`
`9,e:2,82;3%‘NES2fl8m332:;.335;.2%
`nEg.m5mEomNmum:Nmum:owm5582<9%
`2Ev
`
`M35$::52Ammv
`
`
`3=-m=52;.3:$1...20:was:.82mg”$0.:9%.Easy.
`M0mm152:52a.5852E:3NEm:
`$>EmE52mmmm.80%.“:meaflwmmfifiomoE5525382083_$8Wmmm
`
`
`
`
`nE:NES55%E:F$2:22
`
`2”82"Emma:8282..2mm0%
`
`.mEH602858::Ed“2853:5“:
`:552:25:m=33“V2563:5&3:E:2.8%
`
`wmmNbom
`
`4oz<QZMn—nz.__mmIoz=<4
`f2328:“;m«$25:
`
`
`S5:5822028228928%S
`
`
`288mm255$:8mafia:Emma9&0?wawe“fiflm.252.5E:5H".82:85..2mm
`
`
` zawmmmvfimmw?2__fi_,wzzo<zmmw<mawwwwPmmv__._moe:99%m?3:5as;“.52..92mmmufiwwmzozyfiama
`
`.asSamz8?.9mmm.58E.328?.9%$83:
`E25:962:93am:
`..mmumzépzomoo;FEm:
`
`233%><._n_mHo
`
`22
`
`22
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 22 0f 24
`
`US 2003/0101343 A1
`
`28mg358:S302asE:52
`
`
`
`$288”.Examm
`
`
`
`$2525Examm
`
`358:5a:azoomm.rk.v.K55%:Ed255$::25@2553:NWLN:26o25<m$=
`
`
` 288%MES:S.33%
`
`szgeozhwémmz:EmjzzmoENEozsfimmzE:
`
`
`__n_:m._.<:;.83SI:..gut—$25:moo._—mum:
`
`
`
`
`553:EmmaE5as?at“:SE:$02..9mmmafia:8e:as?mm»$02..ozmwN938:zams
`$53::530:?2:85..92mm.252asE:Va:22:83..9mm5.83:
`
`
`
`
`
`
`.ouz.><._n_mHo.azozmic:82.102:._.oz__ozmmhmmscmmva
`83NE8”9szE52mE4552:382083_mum:mmExamE52mmm
`
`.....320292.0:82.
`
`
`
`92as;.mv5:28$52”:88:55.22onmeEmma
`m2ȣ88amz8?.9mm:89amz8?.2mm2225%
`mmNRa0m.
`
`8wm?\Esomz2028228:9528am:
`
`
`
`
`
`
`
`mamIN$88332:;.835;.9mm
`
`
`
`2.mmm::8:
`
`mo<mmm2E83
`
`
`0mm‘Emjzi&N5853::mN38
`E:N58E822:_$3:52
`
`$532Emoo<N$8mmmNE82Noam:<9mm
`
`
`
`oz<382;zmmo.102282..02mm
`
`E558”.
`
`e:E:
`
`235:3“;N9»
`
`szsmgsgozéEN
`
`Exmm<n_mmmwzép
`
`ozoomwE.zo
`
`23
`
`
`
`
`
`
`
`2382285&2?5%onzwwwwfi?
`
`23
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 23 0f 24
`
`US 2003/0101343 A1
`
`onmwmmozHo<mmm2Smo<mwm2
`
`rimmHo
`
`NNNWWNENWNNSNm3
`
`aE8:9:
`
`
`
`5&8::32
`
`
`
`E55E52mmm
`
`
`
`
`
`WWAVEmmmmON
`_.N%m::;SN51..:8252..2%8w
`.
`
`:9602558...$53:mm:95on
`
`52"EmmaN$8292382;5%.1322;3$1..9mm
`
`285%2:58:2$02..ozmm_e:29%
`
`
`
`5&8:Emma:808BNZ8r.9%.asE8%8r.ozmm
`
`ENEezmzmm:E:NEB:52E:N$8552820555523.8E5355$:EN:
`929mg:EBas?m?._
`
`
`
`83Nmum:”EmmaEH52mmmEdm<d<><.._o92088Nmum:
`e:95%252asE:5:N958:$sz
`
`mmvNEEOE:mN:95E:N58E52_mm:E52$523:
`
`8mEa...$01.826%»3%:NEW
`Nma:88m5582<2%
`Evom2:85..saw.252N:am:5222:8E:9%
`
`$52:a_mm:593::aNEm
`593::a£52:288%3&5
`mamm?E23:
`
`NEEEEO235$::95oz§m$2
`E5523NoNEE£52zoEoEnz
`
`E”::55$02..saw
`
`E83:
`
`
`
`ozHc<mmu2955mm:><.EmHo
`
`onmmmm
`
`24
`
`24
`
`

`

`Patent Application Publication
`
`May 29, 2003 Sheet 24 0f 24
`
`US 2003/0101343 A1
`
`mega...5E95on.mvRN”ExamEEO$55.3::95052mgwmN1:95355$:
`
`
`
`
`onmmmm@2553:__....oo89.52so»:92mm2353:
`E202>83N$8E552:no:252?me5E
`e:as;.252as$15:asmm:vs:22:85..2mm55m:WEE
`
`
`
`mmmN20:925:.a:.18282..92mm
`0%NEm:N382mafia:<azmm
`
`£5CNNMafia9%‘
`mmmmHON
`
`...20:9%:.82
`E058E:ozwm$83.
`
`
`E>mwmEH820mmmm>mmmC302mmm
`
`__;.._m_._>o<m5<..mo<mmm2Oh
`>:._Hm<._H<><.5ohzo83_mum:
`
`
`
`>pH._Hm<..H<><.._omm>~fimCur—.02mummz<5
`
`game
`
`ow>.
`
`:80E9.5220?.Qme
`
`oz<ozmmm<
`
`
`
`mo<mmmzEmoo<
`
`N;Em:20E
`
`353:E52
`
`mmmIN58S.3531;E5;.GEN
`
`52..52..9sz8w
`
`mmv
`
`mm>
`
`m..m<._H<><mHm._m<._H<><
`
`233%5‘de
`
`zofi<oflna<
`
`25
`
`25
`
`

`

`US 2003/0101343 A1
`
`May 29, 2003
`
`SYSTEM FOR PROVIDING CONTINUITY
`BETWEEN MESSAGING CLIENTS AND METHOD
`THEREFOR
`
`BACKGROUND OF THE INVENTION
`
`[0001]
`
`1. Field of the Invention
`
`[0002] This invention relates in general to communication
`systems and in particular to communication systems incor-
`porating capabilities to provide continuity between messag-
`ing clients.
`
`[0003]
`
`2. Description of the Related Art
`
`the way
`[0004] With the proliferation of the Internet,
`people communicate is changing. Electronic communication
`such as electronic mail (email), and real time electronic
`messaging (e.g. instant messaging and chat messaging) is
`quickly replacing traditional telephonic communication and
`handwritten letters. Real time electronic messaging allows
`the simultaneous access to a message or a plurality of
`messages by multiple account users, with each account user
`capable of inputting a message or a plurality of messages to
`a messaging session. Each inputted message is relayed to
`messaging clients operating on messaging devices (such as
`computers) of the other account users who have chosen to
`participate in that messaging session. The other session
`participants can respond with their own messages, which are
`likewise relayed to all
`the participating devices. These
`messages are typically text messages that are delivered to
`the intended recipient(s) of the message in a real
`time
`manner. However, these messages may be in a variety of
`different media formats or combinations thereof such as
`
`audio, animation, video, images, etc. A session history of the
`messages received and transmitted by all participants
`involved in the messaging session is typically maintained on
`the individual participants’ devices and typically presented
`on the screen of the respective device in the form of a
`scrolling dialog. This text history constitutes one of the
`attributes of the look and feel of the real time electronic
`
`messaging experience.
`
`[0005] There are currently several standard methods avail-
`able for account users to participate in messaging commu-
`nications. For example, personal instant messaging typically
`occurs between two individuals. An individual can establish
`
`a private chat room so that multiple users can participate in
`a common on-line conversation. Participants gain access to
`the private chat room by accepting an invitation from the
`creator of the private chat room. Non-restricted public chat
`rooms are available to anyone interested in the topic being
`discussed by simply selecting the desired chat room descrip-
`tor on the account user’s device. In addition to the non-
`
`restricted public chat rooms there are limited access public
`chat rooms. An example of one such restriction is the
`limiting of the number of account users allowed to partici-
`pate in the chat room. Electronic gaming is available to
`participants who register and login to join at least one other
`participant in playing one or more games. Communication
`of participants’ “moves” are made through electronic mes-
`sage communications in messaging sessions.
`
`[0006] Each messaging session can have various types of
`session attributes such as session type, session connection
`info, participants, filter settings, colors, relative font sizes,
`etc. The account user can also have various types of pref-
`
`erences such as colors, relative font sizes, buddy lists,
`nicknames, and parental control settings. These are only a
`few examples of the attributes and preferences that can effect
`a messaging session.
`
`[0007] Several different devices, such as personal com-
`puters, interactive broadcast receivers and mobile commu-
`nication devices, can be utilized to participate in messaging
`communications. Although these different devices can be
`utilized to participate in a messaging communication they all
`do not have the same set of features and capabilities. For
`example, display size, support for different media types, and
`cost of sending messages can all be different for different
`devices. Some messaging service providers maintain the
`same user preference settings such as screen names, buddy
`list groups, electronic mailboxes, and parental control set-
`tings regardless of which device is used to access the
`service. By having this capability the service providers are
`providing continuity of user preferences from device to
`device, which simplifies the use of multiple devices in the
`messaging system.
`
`In order to utilize real time electronic messaging, a
`[0008]
`device is pre-configured with, or the user installs, applica-
`tion client software distributed by a particular service pro-
`vider. The client software connects to a message server for
`communication. To access the message server, via a logon
`procedure, the client sends the routing information (e.g. IP
`address and number of the port assigned to the client, mobile
`phone number) of the device being used, the account user’s
`username,
`the account user’s password, and the account
`user’s current availability setting to the message server. The
`message server temporarily stores the routing and availabil-
`ity information for the account user’s device. In response to
`the account user’s login information (username and pass-
`word),
`the message server provides the messaging client
`with the account user’s contact list. The message server then
`determines the presence and availability of the account users
`in that contact list. If the message server finds any of the
`contacts logged in (i.e. presence setting is online), it sends
`a message back to the messaging client on the account user’s
`device with the presence and availability information for
`that account user. The message server also sends the account
`user’s presence and availability information to the people
`that have the account user in their contact list. The account
`
`user can click on the name of a person in his/her contact list
`who is online, and a window is created in which the account
`user can enter a message. The account user enters a message
`and clicks “send” to communicate with that person. The
`other person gets the message and can respond. Messages
`between account users may be addressed directly to the
`account user’s device or may be addressed to the username
`and sent via the message server.
`
`[0009] The window that the session participants see on
`their respective messaging devices typically includes a
`scrolling dialog of the session history. Each participant’s
`messages appear in this window on all participating devices.
`Messages can have different attributes such as message
`formatting, sender identification, timestamps and others. For
`example, messages related to a particular electronic game
`could contain graphics enhancing the “look and feel” of the
`electronic game for the participants.
`
`the
`[0010] When the messaging session is complete,
`account users close the message window for that messaging
`26
`
`26
`
`

`

`US 2003/0101343 A1
`
`May 29, 2003
`
`session. When the account user signs off, his/her messaging
`client sends a message to the message server to terminate the
`account user’s participation in the plurality of messaging
`sessions. The message server then sends an update of the
`account user’s presence and availability information to the
`people that have the account user in their contact list to
`indicate the account user has signed off. Finally, the message
`server discards the routing and availability information for
`the account user’s device.
`
`[0011] Some messaging services support access of a single
`account from multiple devices. Further, some messaging
`services also support simultaneous login of devices on the
`same account. Still further, some messaging services utilize
`a resource extension to describe the device that is being
`utilized to communicate. For example an account user
`logging in with a mobile device can choose to use “mobile
`device” as their resource extension while logging into the
`same account from the home personal computer may utilize
`a resource extension of “home computer”.
`
`[0012] When using messaging services that allow access
`from multiple devices, an account user can log on with a first
`messaging device and engage in conversations with other
`account users and later log on with a second messaging
`device. For example, users of mobile devices would typi-
`cally benefit if a messaging session in progress on a fixed
`network device could be continued on a mobile device. This
`
`would allow the account user to continue the messaging
`session when the account user is no longer in proximity to
`the fixed network device. In addition the account user would
`
`benefit if a messaging session that was in progress on a
`mobile device could be continued on a fixed network device
`
`that may have a superior user interface.
`[0013]
`In order to switch to a different device with existing
`technology, the account user may have to cause the currently
`connected device to disconnect from the message server.
`The account user would then have to cause the second
`
`device to connect to the message server and login. Finally,
`the account user would have to re-initiate each messaging
`session (one-to-one, public chat, private chat, electronic
`game) that was in progress on the first device. The disad-
`vantage of this method is the numerous manual operations
`required of the account user to change devices. A further
`disadvantage is the lack of messaging session continuity. For
`example, the second device will not have the session history
`that was available on the first device, and the second device
`may not be able to re-connect to chat rooms that restrict the
`number of active account users since another account user
`
`may have connected to the chat room after the account user’s
`first device disconnected.
`
`[0014] What is needed is a system and method for main-
`taining continuity between messaging clients.
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0015] The present invention will be described by way of
`exemplary embodiments, but not limitations, illustrated in
`the accompanying drawings in which like references denote
`similar elements, and in which:
`
`[0016] FIG. 1 is an electronic block diagram of a mes-
`saging communication system, in accordance with the pre-
`ferred embodiment of the present invention;
`[0017] FIG. 2 illustrates client data for use within the
`messaging communication system of FIG. 1, in accordance
`with the preferred embodiment of the present invention;
`
`[0018] FIGS. 3 and 4 illustrate more detail of the client
`data of FIG. 2, in accordance with the preferred embodi-
`ment of the present invention;
`
`[0019] FIGS. 5, 6, and 7 are electronic block diagrams of
`various embodiments of a messaging device in which a
`messaging client of FIG. 1 operates;
`
`[0020] FIG. 8 is an electronic block diagram of an alter-
`nate embodiment of a messaging communication system, in
`accordance with the preferred embodiment of the present
`invention;
`
`[0021] FIGS. 9 to 12 are electronic block diagrams of
`various embodiments of the messaging communication sys-
`tem of FIGS. 1 and 8, in accordance with the preferred
`embodiment of the present invention;
`
`[0022] FIGS. 13 to 18 are flowcharts illustrating the opera-
`tion of the messaging communication system of FIGS. 1
`and 8, in accordance with the preferred embodiment of the
`present invention;
`
`[0023] FIG. 19 illustrates a message for use within the
`messaging communication system of FIGS. 1 and 8,
`in
`accordance with the preferred embodiment of the present
`invention; and
`
`[0024] FIGS. 20 to 24 are signaling flow diagrams illus-
`trating the interaction between the elements of the messag-
`ing communication system of FIGS. 1 and 8, in accordance
`with the preferred embodiment of the present invention.
`
`DETAILED DESCRIPTION OF THE
`
`PREFERRED EMBODIMENT(S)
`
`[0025] As required, detailed embodiments of the present
`invention are disclosed herein; however, it is to be under-
`stood that the disclosed embodiments are merely exemplary
`of the invention, which may be embodied in various forms.
`Therefore, specific structural and functional details dis-
`closed herein are not to be interpreted as limiting, but merely
`as a basis for the claims and as a representative basis for
`teaching one skilled in the art
`to variously employ the
`present
`invention in virtually any appropriately detailed
`structure. Further, the terms and phrases used herein are not
`intended to be limiting; but rather, to provide an understand-
`able description of the invention.
`
`[0026] Referring to FIG. 1, an electronic block diagram of
`a messaging communication system 10 in accordance with
`the present invention is shown. As illustrated, the messaging
`communication system 10 preferably includes a plurality of
`messaging clients 12 for participation within a plurality of
`messaging sessions 24. As illustrated, the plurality of mes-
`saging sessions 24 can include a messaging session 40
`and/or a multiple user messaging session 19. The plurality of
`messaging sessions 24, for example, can include the com-
`munication of a plurality of electronic messages such as chat
`sessions,
`instant message sessions, and electronic mail,
`facilitating substantially real time communication among
`the plurality of messaging clients 12. Similarly, the plurality
`of messaging sessions 24 can include communication of
`gaming messages for one or more gaming sessions (e.g.
`battleship, checkers, chess, tic tac toe and doom). It will be
`appreciated by one of ordinary skill
`in the art
`that
`the
`plurality of messaging sessions 24 can include any of the
`messaging sessions mentioned herein or an equivalent. Each
`27
`
`27
`
`

`

`US 2003/0101343 A1
`
`May 29, 2003
`
`of the plurality of messaging clients 12 such as a first
`messaging client 14 and a second messaging client 20
`includes client software to interface within the messaging
`communication system 10. The client software, for example,
`can include a software application for communication
`through an Internet service provider. Further,
`the client
`software can include a software application for participation
`in one or more electronic games offered by a gaming
`software provider. It will be appreciated by one of ordinary
`skill in the art that the client software can be any of those
`mentioned herein or an equivalent. Further, it will be appre-
`ciated by one of ordinary skill in the art that in accordance
`with the present invention, the interface capabilities of the
`client software can also be designed into client hardware of
`a messaging client. Each messaging client 26 of the plurality
`of messaging clients 12 further includes a client identifier
`27. For example, the first messaging client 14 includes a first
`client
`identifier 15 and the second messaging client 20
`includes a second client identifier 21. The client identifier 27
`
`of the messaging client 26 is a unique identification within
`the messaging communication system 10 for directing mes-
`sages to a particular messaging client. For example,
`the
`client identifier 27 can be an address of a mobile device or
`
`an IP address and number of the port of a fixed network
`device. To communicate within at least one of the plurality
`of messaging sessions 24 the messaging client 26 establishes
`a communication connection 28. For example,
`the first
`messaging client 14 establishes a first communication con-
`nection 16 for communication within at least one of the
`
`plurality of messaging sessions 24. Similarly, the second
`messaging client 20 establishes a second communication
`connection 22 for communication within at least one of the
`
`plurality of messaging sessions 24. It will be appreciated by
`one of ordinary skill in the art that
`the communication
`connection 28, the first communication connection 16, and
`the second communication connection 22 can be a physical
`connection, or alternatively can be a logical connection
`where the act of connecting and disconnecting is a logical
`one. Each messaging client 26 of the plurality of messaging
`clients 12 is operated by at least one account user 30. The
`account user 30 is an individual who uses one or more
`
`messaging clients to communicate with other account users
`within the plurality of messaging sessions 24. It will be
`appreciated by one of ordinary skill
`in the art
`that
`the
`account user 30 can communicate using one or more mes-
`saging clients. For example, a first account user 29 can
`establish communication within the plurality of messaging
`sessions 24 using the first messaging client 14, and,
`in
`accordance with the present invention, also using the second
`messaging client 20.
`
`[0027] Each messaging client 26 preferably includes a
`plurality of client data 25. The plurality of client data 25
`includes data associated with the messaging client 26 and
`data associated with each messaging session for which the
`messaging client 26 is currently participating, has partici-
`pated in, or plans to participate in. The plurality of client data
`25 can be divided up into one or more client data portions
`18 as illustrated in FIG. 2. The first messaging client 14
`includes a first client data 17 and the second messaging
`client 20 includes a second client data 23. FIG. 2 illustrates
`
`the plurality of client data 25 included within the messaging
`client 26 of FIG. 1. It will be appreciated by one of ordinary
`skill in the art that the plurality of client data 25 as illustrated
`in FIG. 2 can be the first client data 17 or the second client
`
`data 23. As illustrated, the plurality of client data 25 pref-
`erably includes a client version identifier (not shown), an
`account identifier 31, a server identifier 32, an authentication
`key 33, a plurality of contact data 34, a plurality of user
`preferences 35, and a plurality of session data 36. It will be
`appreciated by one of ordinary skill
`in the art
`that
`the
`plurality of client data 25 can include any of the client data
`mentioned herein or an equivalent.
`[0028] The client version identifier is preferably the name
`and version or other similar indication of the messaging
`client being used. The account identifier 31 is preferably a
`user name or other identification of the account user 30
`
`currently using the messaging client 26. In an embodiment
`of the present invention in which a message server is utilized
`to manage the plurality of messaging sessions 24, the server
`identifier 32 identifies the message server. For example, the
`server identifier 32 can be a wireless address, an IP (internet
`protocol) address, or an IP address accompanied by a
`number of the port assigned to the message server. The
`authentication key 33 preferably includes a code that is used
`to authenticate the account user 30 to the messaging com-
`munication system 1