NOAATACTAAAA
`
`US 20030101343A1
`
`as) United States
`a2) Patent Application Publication 0) Pub. No.: US 2003/0101343 Al
`Eatonet al.
`(43) Pub. Date:
`May 29, 2003
`
`
`(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 Jeffery Hayes, Lake
`Worth, FL (US); Von Alan Mock,
`Boynton Beach, FL (US)
`
`Tint, C07 ciccceccccccccceccccccccscsessesecsessessesesseaneeees HO4L 9/00
`(51)
`
`eee
`(52) U.S. C0.
`eceecssecesesseesnsssnessnceasesssenesneeeneeeneees 713/170
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`MOTOROLA, INC
`INTELLECTUAL PROPERTY SECTION
`LAW DEPT
`8000 WEST SUNRISE BLVD
`FT LAUDERDAL, FL 33322 (US)
`
`(21) Appl. No.:
`
`09/995,338
`
`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 messagingclient
`(20) establishes a second communication connection (22)
`operating using the plurality of client data (25).
`
`PLURALITY OF CLIENT DATA
`
`25
`
`
`
`SECOND ACCOUNT INFORMATION
`
`SECOND ACCOUNT IDENTIFIER
`
`SECOND ACCOUNT CONTACT INFORMATION
`
`nth ACCOUNT INFORMATION
`wth ACCOUNT IDENTIFIER
`wth accouNT CONTACT INFORMATION
`
`38
`59-|
`
`PLURALITY OF USER PREFERENCES
`
`FILTERS
`
`ALERTS
`
`FONTS
`
`a
`
`PLURALITY OF SESSION DATA
`
`1
`
`APPLE 1009
`
`APPLE 1009
`
`1
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 1 of 24
`
`US 2003/0101343 Al
`
`
`
`
`
`
`
`MATATINSGLINSTI1SaT3
`
`LTOLAa
`
`SINSIT)ONIOVSSIN40ALTWaMd
`
`
`
`NOTLOSNNODNOILVOINANNODISHT3
`
`
`INIT)ONTOVSSINLSUT4
`
`
`
`
`
`VIVdINSTT1SuT
`
`
`
`NOISSSONTOVSS3N
`
`NOTLOINNOD
`
`
`
`SNOISS3SWIVINAITOGNODaS
`
`ONTIOVSSAN40ALTWaNId
`
`NOTLVOINNWNODNODS
`
`
`INSTT)SNIOVSSINONODSS
`
`NOISS3S
`
`
`
`
`
`
`
`
`
`QNIDYSSINS280TILTONYSTJLINGOLINSITOQNOISS
`
`8 NOTLO3NNOD
`
`NOLLVOINANNO)
`
`
`
`{NAT1)ONISVSSIN
`
`VVINSTT)
`
`
`
`YITSTINSGTLNATT)
`
`2
`
`
`
`
`
`
`
`

`

`Patent Application Publication May 29, 2003 Sheet 2 of 24
`
`US 2003/0101343 Al
`
`[>
`
`PLURALITY OF CLIENT DATA
`
`
`Jt
`
`ACCOUNT IDENTIFIER
`
`
`
`
`
`
`
`52
`
`J3
`
`SERVER IDENTIFIER
`
`AUTHENTICATION KEY
`
`
`
`PLURALITY OF CONTACT DATA
`
`
`FIRST ACCOUNT INFORMATION
`
`
`
`
`
`
`
`
`
`
`
` FILTERS
`
`
`PLURALITY OF SESSION DATA
`
`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 CONTACT INFORMATION
`
`36
`
`ALERTS
`
`FONTS
`
`BIG.2Z
`
`3
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 3 of 24
`
`£7SJONIVIITNdNOISSISYIN
`
`
`creeALTYOTYdNOISSISYN
`
`lyYITATINIGINOISSIS4IN
`
`
`SIONSYIIFNdNOTSSISGNOIIS
`
`
`MSLITINIGINOISSISGNOOIS
`
`
`ALTYOTYdNOISSISQNOIIS
`
`SIONIYIIFYdNOISSISSUI
`
`
`YILATINIGTNOISSISLSYT4
`
`
`ALTHOIYdNOISSIS1SYT4
`
`
`
`NOISSISSNTOVSSINYIN
`
`NOISSISONTOVSSINQNOD3S
`
`
`
`
`NOISSISONIOVSSINLSYT4
`
`
`SINVdIOTLYYdNOISS3SYN
`
`
`SINYIOILYVdNOISSISQN0I3S
`
`SINVdTOILYVdNOISSISLSU
`
`WLVG
`
`WoQILNNOQOV
`
`VoINVdIOILUYd
`
`d@dLINN0IOV
`
`G2INVdTOLLYVd
`
`YiGLINNOJOV
`
`VLINVdIOTLYVd
`
`QlQIINNO0V
`
`
`
`GtINVdIOTLY¥d
`
`N@QIINNODOV
`
`N@INVdIOILVd
`
`NLG1INNOJOV
`
`NIINVdIOTLYVd
`
`
`
`
`
`AMOLSIHNOISSISJSUTJ
`
`US 2003/0101343 Al
`
`EOL
`
`WAQILNNOQOV
`
`VAIN¥dIOTLUVd
`
`GWGILNNOJOV
`
`GWLNVdTOTLaVd
`
`NWQTLNNOJOY
`
`NAINVdIQTLUVd
`
`
`
`AMOLSIHNOISS3S43N
`
`
`
`
`
`ANOLSIHNOISSISCNOIIS
`
`NOISSHS40ALTWaNTd
`
`4
`
`

`

`Patent Application Publication May 29, 2003 Sheet 4 of 24
`
`US 2003/0101343 A1
`
`)NdANVISINTL
`
`NOTSSIS
`
`¢dAVISIAIL
`
`GJOVSSIN
`
`@QILNNOJOV
`
`NQTINNOJOV
`
`|dAVISSIWIL
`
`|JOVSSIN
`
`|QIINNOIOV
`
`AMOLSIH
`
`5
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 5 of 24
`
`US 2003/0101343 Al
`
`68
`
`GauIM
`
`ONIOVSSIN
`
`WALSAS
`
`08
`
`sd
`
`71av9OL
`
`QN3QV3H
`
`J18Vo
`
`WAC0N
`
`WL
`
`£8
`
`cs
`
`c8
`
`LANYSHL3
`
`|
`
`uAMOd¥asn
`
`LINDUTDANdNT
`
`0968
`
`
`
`
`
`
`
`88
`
`
`
`rT—_77a~~astTeOOoesTTTUT|7w3ZINO0034|-enes49I0ATWEyOVEL(UYOSAIMASNON+gSHIT
`9g|ZZOL99ag!
`
`
`1WOK—————|_avidsta—AddONIWIL
`986SgS
`arocco1G9FW40Nd
`os-|1viva|INSTwasn
`boeeeee_—
`
`
`
`|Ma4SNVUL3OVANGINI
`|NOLLVOTTdd¥|INATT0140d
`LoosQNIDYSSIN29__XIz9
`YSATHOyooro
`
`TORLNAI)So
`
`J9VYOLSJOvHOLSAYONIA
`
`wre
`
`£g
`
`SSYN#
`
`INST10
`
`vlvd
`
`viva
`
`JOIAIC96
`
`LNOdvVlvdK—t»WAGON
`
`QauIM
`
`ONTOVSSIN
`
`WALSAS
`
`6
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 6 of 24
`
`US 2003/0101343 Al
`
`wasn
`
`LndNI
`
`WaSNFOTAAC
`
`FOVANSLNI
`
`gol
`
`Oll
`
`SOIAIO
`
`AW1dSTO
`
`Loos>Oy
`r--+--11NOLLVOD
`Idd|MAJSNVSLiviva
`
`FITEON
`
`ONIOVSSIN
`
`LNAT19
`
`ANST10
`
`31110ud
`
`Se
`
`86f™
`
`LINOULDLAdNI
`
`rel
`
`¥6
`
`
`8S
`
`‘AMONG
`
`JOVUOLS
`
`JIA
`
`
`
`ANONANJOTASC
`
`LOANNOOUSINI
`
`SOL
`
`col
`
`Viva90!
`aro[TS
`LydJOIAAd
`
`LTNOYLO
`
`YOSSI00Ud
`
`26.On|
`
`VLV¥ONATO ¢e
`
`AMOWSN
`
`vivaLNaIT
`
`
`
`LOISAYONAN
`
`
`
`NOISS3SJOVSS3IN
`
`JOVSSAN
`
`AMONIN
`
`SJ0VSS3N
`
`SSaudgv
`
`AMOWAN
`
`
`
`AMOWINFOIAIC
`
`
`
`06
`
`.OPI
`
`7
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 7 of 24
`
`US 2003/0101343 Al
`
`991
`
`Orany
`
`USAT
`
`NOISIAITALOf
`
`VLVGWow,yIN3T10xodJ19v9yasL¢9861
`[oe~—XodFEVOXogF189
`
`FM140Yd
`LLaeoe—_o4
`
`AXOWAN
`
`JOVYOLS
`
`JOIAI
`
`VL¥OLNAI10
`
`AYOWSIN
`
`q1aV9
`
`ONTOVSSSN
`
`LNIT10
`
`LNATVO
`
`u3aMOd
`
`LINQUTO
`
`OS0IA/18
`
`
`
`YAATYCYATIONLNOD
`
`NMOO/dN
`
`YALYSANOD
`
`31avdOL
`
`QN30V3H
`
`x08JIGVO
`
`AMOWSN
`
`LOANNOOUSINT
`
`X0dJIaVO
`
`lfO/I
`
`ZOLA
`
`
`
`JONLNOD3LOWSY
`
`YAATSOSNVUL
`
`LfdNI
`
`z#O/TJOVANSINISSN
`
`8
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 8 of 24
`
`US 2003/0101343 Al
`
`YIAYIS
`
`YALTNICL
`
`HaAUIS
`
`71140Ud
`
`NOTLVOINWKOD
`
`NOTLOINNOD
`
`
`
`INI)ONTOVSSIN
`
`
`
`ViVG
`
`asWSLSTINGOLINSTTNODS—
`
`
`
`
`
`VvINAITO(NO03S62
`
`(NODS
`
`ONTOYSSAN
`
`SNOISSIS
`
`YLVO
`
`ONTOVSS3N
`
`
`
`AMONINY3ANIS
`
`
`
`MGANISJOVSSIN
`
`
`
`ZAlélSINSITOONTOVSSIN40ALTWANTd
`
`
`
`
`
`
`
`
`
`YIANNISNomvanNnooIN3ITOONTOYSS3INLSUTS
`
`
`
`4OSSI00UdNOTLOANNOD
`
`MC
`
`
`Vi¥dINSTTLSHTd
`
`
`
`NSTITINIGLINITIOLUT
`
`NOTLONNOD
`
`
`
`
`
`
`
`vivNOLLVOINNINOOINSITOSNTOWSS3AGNODISjhSING)
`
`9
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 9 of 24
`
`US 2003/0101343 Al
`
`INIT|SSR||ontoyssan
`
`SSN0Y
`Asad
`ONIOVSSIN
`
`INSTV
`
`GNOOaS
`
`aNooas
`
`A9VSSIN-
`YaANAS
`
`USAYIS
`
`SSauddy
`
`MSATSOIN4d
`
`YALLIWSNVYL
`
`SSATSYIN
`
`WALSAS
`
`YATIONLNOD
`
`uaaTHOSENS
`
`asvav1vd
`
`10
`
`10
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 10 of 24
`
`US 2003/0101343 Al
`
`ONIDVSSIN
`
`MaANaS
`
`ALVATUd
`
`
`
`
`QNIOVSSINLSUT4
`NVMvk
`
`INIT)
`
`LANNE||
`
`
`
`
`
`ohh697QNIDVSSINGNODSS
`
`IN3T19Oz
`
`y9C
`
`YYOMLINV3¥JOIM
`
`QNTOYSSINHLYNOS||ONIOVSSINCYIHL
`
`JNAT19IN3T10
`
`||Cw992ad
`
`
`
`FOIAIGYYOMLINCYTHL
`YYOMIINV38VW201
`G9oJOTAI
`G9CJOIAAG
`WYOMLINGNODIS
`WOMLANLSUT4
`
`11
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication May 29, 2003 Sheet 11 of 24
`
`US 2003/0101343 A1
`
`
`
`X08318VOGYIHL
`
`ITOLA
`v8292
`
`NISdONSOV3HONTOVSSINLsutaPT7
`
`YYOMLNFava
`
`ONTDVSSINHLunds||ONIOVSSSNCYIHL
`9/297
`LN3T19LN3I19
`
`
`98¢X08318V9GNOOSS
`98¢X08aav)LSU
`
`98d
`
`cZt
`
`AOVSSIN
`
`YSAYaS
`
`iNav
`
`4
`
`12
`
`12
`
`
`
`
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 12 of 24
`
`US 2003/0101343 Al
`
`
`
`
`
`WALSASONIDYSSINONOWALSASONTOVSSANLSUT
`
`
`
`
`
`SINSITOONIOVSS3N
`
`
`
`___0_AlTHvantdQNOO3S__5¥6z
`
`06¢
`
`L
`
`___sOALTIVaAdSTS
`
`SINAIT)ONIOVSSAN
`
`5262
`
`GIOLA
`
`ONTOVSSIN
`
`INATVO
`
`JOVSSIN
`
`YaANaS
`
`QNIOVSSAN
`
`IN3T10
`
`ANAT
`
`
`ONIOVSSINOSZ-~ONTOVSS3N
`HLYNosGuTHL
`
`INST10
`
`QNOO3S
`
`QNIOVSSIN
`
`LN3119
`
`QNIOVSSIN
`
`ANAT10
`
`13
`
`13
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication May 29, 2003 Sheet 13 of 24
`
`US 2003/0101343 Al
`
`296
`
`ESTABLISH FIRST
`COMMUNICATION CONNECTION
`
`300
`
`YES
`
`FIRST
`AUTHENTICATION
`
`? N
`
`AUTHENTICATION
`REQUIRED
`
`O
`
`298
`
`302-)
`
`FIRST MESSAGING
`CLIENT ACCUMULATES
`SESSION DATA
`
`NO
`
`
`
`TRANSFER
`DATA
`2
`
`YES
`
`308
`VERIFY SECOND
`MESSAGING CLIENT
`
`YES
`
`506
`
`
`VERIFY
`
`SECOND MESSAGING
`
`
`
`NO
`
`TRANSFER
`310|CLIENT DATA
`
`314
`
`YES
`
`316
`
`
`
`
`TRANSFER
`AUTHENTICATION
`KEY
`
`312
`
`
`SECOND
`
`AUTHENTICATION
`COMMUNICATION
`CONNECTION
`KEY
`?
`
`
`
`524
`
`
`
`
` OPERATE SECOND
`COMMUNICATION CONNECTION
`
`WITH CLIENT DATA
`
`
`309
`SECOND
`
`320
`
`AUTHENTICATION
`REQUIRED
`
`AUTHENTICATION
`
`FIG.13
`
`14
`
`

`

`Patent Application Publication May 29, 2003 Sheet 14 of 24
`
`US 2003/0101343 A1
`
`
`
`FIRST MESSAGING
`
`CLIENT ACCUMULATES
`SESSION DATA
`
`
`
`502
`
`
`
`
`
`USER INPUT
`
`FIRST MESSAGING
`DEVICE
`?
`
`
`
`
`
`USER INPUT
`SECOND MESSAGING
`DEVICE
`?
`
`NO
`
`
`
`ACTIVATE
`
`SECOND MESSAGING
`CLIENT
`
`
`
`?
`
`
`SECOND
`MESSAGING CLIENT
`CONNECTION
`?
`
`
`
`S33)
`
`
`
`TRANSFER OF
`ata AFFIRMATIVE
`
`15
`
`

`

`Patent Application Publication May 29,2003 Sheet 15 of 24
`
`US 2003/0101343 Al
`
`302
`
`FIRST MESSAGING
`CLIENT ACCUMULATES
`SESSION DATA
`
`
`
`
`DISCONNECT YES_|DISCONNECT FIRST
`FIRST MESSAGING
`
`
`
`
`310
`
`?
`
`YES
`
`
`
`
`CLIENT c MESSAGING CLIENT
`
`
`NO
`
`
`TRANSFER
`CLIENT DATA
`
`
`ISB
`
`
`
`CONTINUE FIRST
`
`DISCONNECT
`COMMUNICATION
`
`FIRST ete
`
`
`CONNECTION WITH
`
`CLIENT DATA
`
`
`
`
`
`DISCONNECT FIRST
`
`MESSAGING CLIENT
`
`
`
`524
`
`
`
`OPERATE SECOND
`
`COMMUNICATION CONNECTION
`
`
`WITH CLIENT DATA
`
`
`FIG.15
`
`16
`
`

`

`
`
`
`
`
`
`CLIENT
`DATA PORTION
`
`
`9
`
`TRANSFER
`CLIENT DATA
`
`Patent Application Publication May 29, 2003 Sheet 16 of 24
`
`US 2003/0101343 Al
`
`
`
`FIRST MESSAGING
`
`CLIENT ACCUMULATES
`
`
`SESSION DATA
`
`502
`
`
`548
`
`
`
`CLIENT
`
`DATA REQUIREMENT
`
`?
`
`CLIENT DATA
`PORTION =
`REQUIREMENT
`
`352
`
`CLIENT DATA
`PORTION =
`PREDE TERMINED
`
`
` PREDETERMINED
`
`PORTION
`?
`
`
`556)
`
`IDENTIFY CLIENT
`“DATA PORTION
`
`558)
`
`
`
`TRANSFER CLIENT
`“DATA PORTION
`
`FIG.16
`
`17
`
`

`

`Patent Application Publication May 29,2003 Sheet 17 of 24
`
`US 2003/0101343 Al
`
`
`
`359
`
`FIRST COMMUNICATION
`CONNECTION
`
`
`
`nth WessAcING
`
`SESSION ?
`
` FIRST COMMUNICATION
`nth MESSAGING SESSION
`
` tp!RANSFER
`
` NOTIFY OF
` 370
`NOTIFICATION 310
`
`
`
`
`
`CONNECTION INCLUDES
`
`NO"
`
`MESSAGING
`SESSION
`?
`
`
`
`CLIENT DATA
`INCLUDES Nth
`MESSAGING SESSION
`
`TRANSFER
`CLIENT DATA
`
`TRANSFER
`
`
`
`
`318
`
`NO
`
`ESTABLISH SECOND
`COMMUNICATION CONNECTION
`
`
`512
`
`SECOND
`
`COMMUNICATION
`
`CONNECTION
`
`?
`
`
`YES
`
`nth MESSAGING SESSION
`IN. SECOND
` 372
`COMMUNICATION CONNECTION
`
`18
`
`

`

`Patent Application Publication May 29,2003 Sheet 18 of 24
`
`US 2003/0101343 Al
`
`MULTIPLE USER
`MESSAGING SESSION
`
`MESSAGING CLIENT
`PARTICIPATION
`?
`
`
`
`
`
`
`
`
`FIRST COMMUNICATION
`CONNECTION INCLUDES MULTIPLE
`USER MESSAGING SESSION
`
`TRANSFER
`DATA
`
`
`
`19
`
`

`

`Patent Application Publication May 29, 2003 Sheet 19 of 24
`
`US 2003/0101343 A1
`
`vee
`
`Gee
`
`leGl
`
`NOISSAS ly
`
`NOISSAS
`
`NOTLVAYIS34
`
`
`
`QNOOAS{$uT4
`
`
`
`INIT)INIT)
`
`
`
`YSTSTINACTYATATINIGT
`
`YITATINAGI
`
`20
`
`6LQOL
`
`20
`
`

`

`May29, 2003 Sheet 20 of 24
`
`US 2003/0101343 Al
`
`
`
`JOH3ANISASLLON
`
`OlrYAASNVYL
`
`
`
`LNSNI90TMONHOV
`
`Patent Application Publication
`
`
`
`
`
`OGQLDWIANISINST10ONTOVSS3NINSTI)ONTOVSS3N
`
`
`
`FOVSSINAV1dSIGONYON3dd¥wild31AQVSNTYNOTSS3S
`
`NOTSS3SONIOVSSINOL“}uMONdfU3HNOIdOLdiGHWoldOLONIODWinONESZTp
`
`
`FOVSSINAVIdSIGONYONJdd¥ONIOSWeluGNIS
`
`wecASLVHM“OatA3H.|wGNOWSAMOH“CaNTNStHAGSOLJOVSSINGav
`ONVMOUNIKNAdOroeZuasNOLONaSOL©YASNOdwe
`
`
`
`
`narONIDYSSINieINaI1OONTOWSSAA1SUTd
`
`NOTSS3SSINTOVSSINOL
`OlNOS901ALTIISVTIVAYOLNOS907|YSN
`:03N‘AV14S10HONLONGNIS|he
`
`ZuashMITTIVTIVAY40MGAMISAJILON
`
`
`
`INATTOONTOWSSNJ0vSS3NISHGNOO3S
`
`pip|od00OLGEN110A,ONESwé09OLQHINNDAnGNISBIh(NYONAddY
`SNISVSSIN isandayS3SOOHO|YaSNIN3I10
`
`9Ip:JOVSSANAYTASIO
`92a02
`
`SVHK)YZYGSNOLweMSLVHN|JOVSSINSAdALCNY
`
`3d0Ns.ON3S“d31AQVUW“SGN,ONISOcONTOVSSANOL
`
`
`
`0ONo6e‘ahAgHeONSWOQNIMSN3dO|4aSn
`mGLEn|We=oN|Nldal
`
`
`VivaMasSNVULNOISSSSAV1dSIG
`
`
`YaISNVULwaHONSiHOH‘GN,HonNOS901|¥asn
`
`
`
`
`
`INAN390SIMONMOVAYOLSTH
`
`vor
`
`YadSNVULVIVO
`
`
`
`LON2030:AV1dS
`
`QNOOASOL
`
`21
`
`21
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 21 of 24
`
`US 2003/0101343 Al
`
`
`
`
`JOVSSINAVIdSIOwMONdfYaHHOTdAONdfUGHWoldOLONIODWelwONGSNOISSASAVIdSIC
`JOVSSINAVIdSTOvitANNOISES
`
`
`
`
`
`(NYONadd¥cov'ob“elda)AQVANY“3dON,GNSSIO¥SSANAY1dSIA
`(NYONadd¥SaHONNYT
`
`
`
`
`vANSLVHM‘O30ASH.|u@WOWS.MOH“ENON“O3NSOHOIsano3d
`
`
`
`
`INSTT,SNTOYSS3NOHI0INaITOONTOWSS3ALSUTS
`
`"CGN‘AVTdSI0HOMLON.GNSSOf
` NOISS3S
`
`S901ZuasnMAASAITIONKITMAVTIVAY40O1NOSd01|UaSN
`
`
`
`INSTT)ONIOWSSINOvSSIN1SuT4(NOD3S
`oe[7TIBVIIVAYST|438TIeVILVAYSI@wasn
`
`309OLGHINNOAwGNSSwé09OLRNNOAwGNSSpOISTH
`9Z/1Oz
`
`{VHLZaSNASTLONLVHL|aMASLLON
`
`blyNOLIVOTIdd
`
`
`
`EINESINGOONTOVSS3NINaITOONTSYSS3N
`--MA4SNVULNOS901|4asn
`
`
`
`
` JOVSSINIdgo0V\IgzPaJOVSSAN1439ZwasnZuasnOL
`
`JOVSSIN¥GNIS
`
`
`
`98EMIANSSASLLONSSE
`
`ONIOVSSINOL
`
`
`
`NOISS3SONTOVSSINOL
`
`OLONTOSWiluONGS
`
`MGISNVUL
`
`(NYCNadd¥
`
`CNVMOCNIMNadO_|}ZwasnOl
`
`
`96E-TdNSLVHM‘O30AZHnGNSS
`
`
`
`/ANAAODSIGNOLLO3NNODGNOd3SO01
`
`22
`
`
`
`
`
`NOLLVOLSINSAINaTTO.ONTOVSS3N
`
`22
`
`

`

`Patent Application Publication
`
`May29, 2003 Sheet 22 of 24
`
`US 2003/0101343 Al
`
`JOVSSIN
`
`
`
`FOVSSAN1dI00VawasnWOU
`
`SAUAS88°
`
`96¢/ZwasnOL
`ANLYHM‘030ASHON3S
`
`
`
`
`
`INaT1)ONIOVSSINJOvSS3NISMIdCNODSSYOTAYaANASONTOVSSANCSLiINaITOONTOVSSININaI1O
`
`
`
`
`
` onytdfgg)AYRENOTSS3S
`
`
`NOTLOINNODaeiawdNSLVHM‘CatAZHu;;YSISNVYLS901|YasnoorSer|/ANGAOISIC
`
`JOVSSINAVTdSICceaeteONSANOLSIH
`
`
`(NYMOGNIMNad0‘HONWLON,ON3S"Of
`
`
`
`INaTTOONTOWSS3N|__LVHL@¥aSN_AATLONWWHL|3SASTON|arayonroyssanLSMEd
`
`ISSNAVATHON.ONSS1da1ONESm30VSSHOLAUVIETY“SdON.
`
`
`
`
`
`:O3N‘AVIdSIOENONS.MOH“CBNnBHONSANOHENisano3y:
`
`CNYGN3dd¥idNOISSISAVIdSIG
`sooc'sasn|MANESMILONgae[|ARZMBYTIVAYJoJ]OLNOSoo7|3sn
`
`NOISS3ISOVSSINOLMONan3HOT
`9ThP95OLGaNNA.NGSGNYONadd¥
`
`oeJOVSSIN¥GNIS
`6E7TayTIVAYSI|uasnTIaVIVAYSI@4asn
`92Z/1OZ
`sl.7
`1d300V@¥asnZoe7%asnOL
`
`
`Aa1SandaeNOLLVOLdTUaAcer
`
`
`aNyV1¥a
`
`‘aySS¥dUaSSNVAL
`
`NOILVOTIdd¥
`
`SHONAVT
`
`rer
`
`23
`
`23
`
`

`

`Patent Application Publication
`
`ECDIA9%ZZIOZ
`.
`INSTT)ONTOWSSAJOVSSINSeQNO03S
`
`
`
`NOTSS3SONIOVSSINOL3dONw_ON3SQNY GNAddW
`ONYONSddVHONdnUHWOTdJOVSSININ
`
`FOVSSINAVIdSIO|ud09OLGA3NNOAnGNAS1009OLO35NNOAnCNIS
`
`
`s9012Y3snYAANESAATLONggeAITIIEVTIVAY4001NOS9011Yasn
`
`
`
`
`IN3I10SNIOVSSINIWHLZNaSNAJILONLVHL|Y3SNAATLON
`‘O30AZHnHONLON«GNSSoor966.aNOWS.MOHG2NHtNONSNOWisvedNSLVHM
`
`
`
`
`
`
`
`QNVONadd¥iLaT]AQVINWofp;widwildd1AGWSNTY“SdONaGNSS
`
`CNYMOONIMN3dO|wdASLVHM‘OatASH.ONS
`
`
`
`O1NOTITTEBVILVAY40IN3IT0ONIDYSSINLSUT4
`“03N‘AV1dSIGZwasnOL
`bibGIONTOSWauGNSSWMONdnUSHOldOLONTOSWelwON3S
`
`
`LVHLZUaSNASTLON|yaSNASTLON9S¢ZIN3IIOLVHISIZIN3ITOSTHONNV
`
`O6EJOVSSIN¥GNIS
`
`TIGVIIVAYSITIGVIIVAYNOISSASAVIdSIO
`FIVIIVAYSI|yasnTIGVIIVAYSIZ43S
`
`968ZorUaISNVYL
`
`
`
`
`EINESIN3IT)SNISYSS3NIN3IN)ONIDVSS3N
`
`ALITIGVTIIVAY40SAMSAJILONNOTLVOTIdd¥
`
`
`
`
`
`YIAYISASTLONpoe
`
`May29, 2003 Sheet 23 of 24
`
`US 2003/0101343 Al
`
`
`
`3OWSSINLd300¥
`
`wasn
`
`ZwasnOL
`
`FOVSSINAVIdSIG
`
`
`
`NOISSSSSNIOVSSINOL
`
`AMOLSIH
`
`
`
`JOVSSINAVIdSId
`
`ONIOVSSINOL
`
`NOISSIS
`
`élwasnNOUS
`
`
`
`FOVSSIN1dJOOV
`
`24
`
`24
`
`

`

`Patent Application Publication
`
`
`INSTT)JOvSSINISUGNOD3SONTOVSS3NYIAwaAuaSONTOVSSINBGLiTNdI1OONTOVSSININdI1)
`
`
`
`
`
`
`
`(NVON3dd¥OLONIODWanONSWMONdQ43HNOIdOlONIODWInONASANOISTH
`
`
`
`S901ZwasnLITMAVILVAY40IN3ITOONIDVSSINLSUT4
`NOISSASONIDVSSIN|w209OLCINNOAnGNAS
`
`{N3I10QNTOVSSINTIAVIIVAYSI}uasn|aI@VIIVAVSI2uasn\|
`
`
`olx;
`aES
`OLNOIVHLZ@WSNAJTLON{VHL|MSNASTLON“PPZOE
`
`
`
`86EweNOWS.MOH,‘HOMINLONyCN3S“C3N
`
`O6E@4asnZwasnOL
`
`96647sz-yaSNOL
`wAONdf43HTdFOVSSINULNA
`
`wild37AQVINW77AOVSSINOL
`
`
`LVHLSIZ@INILVHLZMasASTLONLwasnASLLONSSHONNYT
`ndASLVHM“3%ASHGNSS
`TIGVILVAYSITGVILVAYZINSTI
`
`
`.“UNONS.MOH‘ON
`
`
`
`YAANIS99EMAANISAATLON995AATLON
`
`
`HONLON,oop‘ON3S
`
`ALTIIGVILVAY40O1NOS907|Yas
`
`
`AMITTISVTIVAY40YSANISAJILONMIISNVYL
`n209OL33NNOAnGNAS
`
`
`
`JOYSSIN1da00V
`
`alwasnNOUS
`
`
`
`FOVSSAN1d300V
`
`FOVSSIN¥NAS
`
`9¢
`
`Of
`
`May29, 2003 Sheet 24 of 24
`
`US 2003/0101343 Al
`
`OLF9VSSINAV1dSIO
`
`9S
`
`aN
`
`NOISSSSAVIdSIO
`
`NOLLVITIdd¥
`
`25
`
`25
`
`

`

`US 2003/0101343 Al
`
`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 messageor 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 methodsavail-
`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 commonon-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 examplesofthe attributes and preferencesthat 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 numberofthe 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 contactlist. 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 messageback 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 contactlist. The account
`user can click on the nameof a person in his/her contactlist
`whois online, and a windowis 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 windowonall participating devices.
`Messages can have different attributes such as message
`formatting, senderidentification, 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 Al
`
`May 29, 2003
`
`session. When the accountuser 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 accountuser has signed off. Finally, the message
`server discards the routing and availability information for
`the account user’s device.
`
`[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;
`
`FIGS.5, 6, and 7 are electronic block diagrams of
`[0019]
`various embodiments of a messaging device in which a
`messaging client of FIG. 1 operates;
`
`FIG.8 is an electronic block diagram of an alter-
`[0020]
`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 embodimentof the
`present invention;
`
`[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
`[0023] FIG. 19 illustrates a message for use within the
`from multiple devices, an accountuser can log on withafirst
`messaging device and engage in conversations with other
`messaging communication system of FIGS. 1 and 8,
`in
`account users and later log on with a second messaging
`accordance with the preferred embodiment of the present
`invention; and
`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]
`Inorder to switch to a different device with existing
`technology, the account user may haveto 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
`disadvantageis 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 notbe able to re-connect to chat roomsthat restrict the
`number of active account users since another account user
`may have connectedto 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 whichlike 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;
`
`[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 and8, 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 embodiedin various forms.
`Therefore, specific structural and functional details dis-
`closed herein are notto 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
`intendedto 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 includesa 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 Al
`
`May 29, 2003
`
`data 23. As illustrated, the plurality of client data 25 pref-
`erably includes a client version identifier (not shown), an
`accountidentifier 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]
`Theclient 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
`
`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
`currently using the messaging client 26. In an embodiment
`client software can also be designed into client hardware of
`of the present invention in which a messageserveris utilized
`a messaging client. Each messagingclient 26 of the plurality
`to managethe plurality of messaging sessions 24, the server
`of messaging clients 12 further includes a client identifier
`identifier 32 identifies the message server. For example, the
`27. For example, the first messaging client 14 includesafirst
`server identifier 32 can be a wireless address, an IP (internet
`client
`identifier 15 and the second messaging client 20
`protocol) address, or an IP address accompanied by a
`includes a secondclientidentifier 21. The clientidentifier 27
`number of the port assigned to the message server. The
`authentication key 33 preferably includes a codethat is used
`to authenticate the account user 30 to the messaging com-
`munication system 10. For example, the authentication key
`33 could be derived from a password known only to the
`account user 30 and the messaging communication system
`10. The plurality of contact data 34 is a listing of information
`relating to the various account users in which the account
`user 30 currently using the messaging client 26 communi-
`cates, plans to communicate, or has communicated with in
`the past. For example, the plurality of contact data 34 can be
`a “buddy list” for the account user 30. The plurality of
`contact data 34 preferably includes a plurality of account
`information 37 for each of a plurality of accounts. For
`example, the plurality of account information 37 for an Nth
`account can include an Nth accountidentifier 38 and further
`can include an Nth account contact information 39 associ-
`ated with the Nth account identifier 38. The Nth account
`
`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 numberof 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 commun