throbber

`
`
`(19) United States
`
`
`
`
`
`
`
`(12) Patent Application Publication (10) Pub. No.: US 2004/0128356 A1
`
`
`
`
`
`
`
`Bernstein et al.
`(43) Pub. Date:
`Jul. 1, 2004
`
`
`
`
`US 20040128356A1
`
`
`
`
`
`
`(54) EMAIL INTEGRATED INSTANT
`MESSAGING
`
`
`
`
`(76)
`
`
`
`
`
`
`
`
`Inventors: Keith Bernstein, San Francisco, CA
`
`
`
`
`
`(US); Alan Chung, San Francisco, CA
`
`(US)
`
`
`
`
`Correspondence Address;
`
`
`
`Glenn Patent Group
`Suite L
`
`
`
`
`3475 Edison Way
`
`
`
`Menlo Park, CA 94025 (US)
`
`
`
`
`
`(21) Appl. No.2
`
`
`(22) PCT Filed:
`
`
`
`
`10/311,259
`
`
`
`
`
`Jun. 25, 2001
`
`
`
`
`
`(86) PCT No.2
`
`
`
`PCT/US01/20381
`
`
`
`
`
`
`Related US. Application Data
`
`
`
`
`
`
`
`
`(60) Provisional application No. 60/214,157, filed on Jun.
`
`
`26, 2000.
`
`
`
`
`Publication Classification
`
`
`
`(51)
`(52)
`
`
`
`
`
`
`
`
`
`Int. Cl.7 ..................................................... G06F 15/16
`
`
`709/206; 709/203
`
`
`
`
`(57)
`
`
`
`ABSTRACT
`
`
`
`
`
`
`
`
`
`
`
`A system and method supporting instant messaging which
`
`
`
`
`
`
`
`
`
`removes many of the problems and barriers to the use of
`
`
`
`
`
`
`
`
`instant messaging through the use of universally unique
`
`
`
`
`
`
`
`identifiers to web pages for instant messaging sessions, with
`
`
`
`
`
`
`
`
`recipients invited to the instant messaging session via email.
`
`
`$3561
`
`
`
`Client
`
`Computer
`
`210
`
`
`
`212
`
`
`
`
`Memory
`
`
`220 Program
`
`SyStem
`
`222
`
`
`
`
`
`224
`
`
`
`
`Server
`Computer
`
`110
`
`
`
`Database
`
`
`
`
`
`104
`I
`
`.
`
`
`
`152
`
`
`
`
`
`
`
`
`
`
`320 PSrogram
`tem
`20500
`
`322
`
`
`
`
`
`
`
`User?
`300
`
`
`Users
`400
`
`
`
`
`312
`
`
`
`Client
`
`
`Computer
`310
`
`
`
`
`
`Client
`
`Com uter
`
`p
`
`410
`
`412
`
`
`
`422
`
`
`
`
`
`420 Program
`
`523%?
`
`
`102
`
`324
`
`
`
`W
`
`
`
`Server Memo
`
`120
`
`Program
`
`System
`
`1000
`
`
`424
`
`
`
`Server 100
`
`
`
`
`
`
`
`
`Universaily Unique
`
`ldentifert_5_8_
`
`
`Audience List
`
`162
`
`
`
`
`160
`
`
`
`
`
`
`
`164
`
`
`
`166
`
`
`
`
`
`
`
`
`Communication
`
`
`
`
`Record 168
`
`
`» Communication History
`Communication 14_6
`
`
`
`instant
`
`Messaging
`
`Session
`130
`
`
`
`
`-
`
`
`
`.
`.
`
`Universally Unique
`
`ldentifeileg
`,
`
`
`
`”5‘ use“ m
`Recipients 1§§
`
`
`Audience Collection
`
`138
`
`
`
`
`_
`
`
`
`Web Page wuth
`
`ldentifer Jfl
`Received Comm from
`
`
`
`
`
`tst Member &
`Processed
`
`Communication m
`
`
`Transferred
`
`
`
`
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 1
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 1
`
`

`

`
`
`m82JEmym>m
`
`Emaoi
`
`
`
`.momvEmmaoEoE.623
`
`
`
`%NowM«NVm.09‘
`52mm
`
`S.IIIIUN353822EI
`IIMummmmooiwvwucmafimm8302008563.4l3commoEsercoo %@flcozonzEEoo.mm?m8:95.th
`
`
`
`
`3a59552@5552H£5,mamanm>>mags:25952::
`
`
`
`:5:.550328mm.3:9:mi
`
`
`memP
`
`
`
`CmuPn.mm
`
`
`
`
`
`1,
`
`
`
`01w
`
`
`
`
`
`
`1Aw
`
`
`
`C0—.rWESQEoovmmMrLoamm
`
`
`
`Smack.CNN
`
`
`
`NNN
`
`
`
`ooow
`
`
`
`Emcmoiomm
`
`,
`
`E295
`
`
`
`Emaen.omv
`
`
`
`@5332
`
`86me
`
`Emma.
`
`09
`
`
`
`
`
`
`
`Em=0
`
`$5an0
`
`05
`
`E25
`
`LquEoo
`
`9m
`
`N5
`
`NNm
`
`N5
`
`Emzo
`
`$5950
`
`05»
`
`NNV
`
`
`
`N3
`
`_‘
`
`0,:
`
`Emma
`
`cow
`
`mam:
`
`08
`
`9mm:
`
`00v
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 2
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 2
`
`
`
`
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 2 of 13
`
`
`
`US 2004/0128356 A1
`
`
`
`
`
`1 000
`
`
`
`1012
`
`
`
`
`
`
`
`
`
`
`Creating instant messaging session with
`
`
`
`
`
`universally unique identifier initiated by first
`
`
`
`
`
`
`user for recipients designated as at least one
`
`
`
`of remaining of users
`
`
`
`
`
`
`
`
`
`1 024
`
`
`
`1014
`
`
`
`
`
`
`
`Providing instant messaging session identified
`
`
`
`
`
`by universally unique identifier as formatted
`
`
`
`
`
`
`web page to each designated recipients and to
`first user
`
`
`
`
`
`
`
`Fig. 2A
`
`1 052
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`1012
`
`
`
`
`
`
`
`Receiving instant messaging session request
`
`
`
`
`
`from first user for recipients designated by
`
`
`
`
`
`associated em ail address for at least one
`
`
`remaining user
`
`
`
`
`
`
`
`Assigning universally unique identifier based
`
`
`
`
`
`upon instant messaging session request
`
`
`
`
`
`
`Sending instant meSSaging invitation email
`
`
`
`
`message to associated email address
`
`
`
`
`designated for each recipient
`
`
`
`
`
`
`Fig. ZB
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 3
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 3
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 3 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`
`
`
`
`
`
`
`Creating web page referenced based upon
`
`
`
`universally unique identifier
`
`
`
`
`
`
`
`
`
`Providing web page with area associated with
`
`
`
`
`first user for participation
`
`
`
`associated with first member
`
`
`
`
`
`
`
`Providing web page with another area
`
`
`
`
`
`
`associated with recipient for participation upon
`
`
`
`
`
`response to instant messaging invitation email
`
`
`
`message, for each recipient
`
`
`
`
`
`Transferring received communication from
`
`
`
`
`
`client computer operated by first member of
`
`
`
`
`
`audience to all members of audience to create
`
`
`
`
`transferred communication as content in area
`
`
`
`
`
`
`Fig. 3
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 4
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 4
`
`

`

`Patent Application Publication
`
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 4 0f 13
`
`
`
`
`
`
`
`US 2004/0128356 A1
`
`
`
`
`
`
`
`1122
`
`
`
`
`
`
`
`1152
`
`
`
`
`
`
`
`
`
`Receiving communication from 1st member of
`
`
`
`
`audience to create at least 1 received
`communication
`
`
` Processing at least 1 received communication
`
`
`
`
`
`
`
`
`
`
`
`from 1st member to create at least 1
`
`
`
`
`
`processed communication from 1st member
`
` Sending at least 1 proCessed communication
`
`
`
`
`
`
`
`
`
`
`from 1st member to create transferred
`
`
`
`
`
`communication as content in area associated
`
`
`
`
`
`With 1st member to all members of audience
`
`
`
`
`
`
`
`
`
`
`
`
`
`with universally unique identifier
`
`
`
`
`
`
`
`Maintaining database referencing history of instant messaging session
`
`
`
`
`
`
`
`
`Fig. 48
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 5
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 5
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 5 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`1192
`
`
`
`
`
`
`
`
`
`
`Maintaining history of instant messaging session with universally unique
`
`
`
`
`
`
`
`
`
`1282
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Sending processed communication from first member as content in area
`
`
`
`
`
`
`
`
`
`
`
`associated with first member to history of instant messaging session with'
`
`
`
`universally unique identifier
`
`
`
`identifier for audience collection
`history-received communication from first member
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Receiving transferred communication from first member at history to create
`
`
`
`
`
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 6
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 6
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 6 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`LmEom
`
`mm?om?
`
`mmmnmfio
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`_E95
`
`.mSano
`
`:3:
`
`8m
`
`
`
`
`
`
`
`
`
`
`
`
`
`mm?EBEI.a:mumN_.N.
`
`
`
`
`
`
`NEmmwNE
`
`
`
`
`
`EEEIcozmoEzEEoo
`
`Door
`
`
`
`co=m2§EEoo$5:50
`
`mm;28%Evw;,8v
`
`mm:0253%E959%:
`
`
`
`
`02‘E296
`
`.N2v9EmboimmmN5
`
`
`
`
`
`Hm:mu:m_v:<ourvmmEwan...
`
`03%:2.3525E26
`n.owno5MmlthcmEE0822Loamw55an0«WWW.
`
`
`
`
`
`
`mlvacozmgcssgom2
`
`
`
`
`
`3.63:9...552608562
`
`UOmmmoen—
`
`
`
`VrcosmoEzEEooIndmEmaGmm
`
`fl.LmsEmEum_.I
`
`EatE508283.mvEm:if02.
`
`
`
`
`
`III205%o:@282mmtgwcmu.993mm
`
`
`
`$3.25>$52:.£30m?“no>>.3__.3Emma.0Or—
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 7
`
`E:.2358.me89950mm2m
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 7
`
`
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 7 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`1 262
`
`
`
`
`
`
`
`
`
`
`
`
`Creating new communication record containing
`
`
`
`
`first member history-received communication
`
`
`
`
`
`as communication from first member
`
`1272
`
`
`
`
`
`
`
`Adding new communication record to
`
`
`communication history
`
`
`
`
`Fig. 7A
`
`
`
`1274
`
`
`
`
`
`
`
`
`
`Sending database initiating request for instant messaging session with
`
`
`
`
`
`
`
`
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 8
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 8
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 8 0f 13
`
`
`
`US 2004/0128356 A1
`
`1192
`
`
`
`
`
`
`
`
`1332
`
`
`
`
`
`
`
`Receiving initiating request for instant
`
`
`
`
`
`
`
`
`messaging session with universally unique
`
`
`
`
`
`
`identifier by first user for recipients at database
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Creating history of instant messaging session
`
`
`
`
`
`
`
`
`
`with universally unique identifier from initiating
`
`
`
`
`
`
`request for instant messaging session with
`
`
`
`
`
`
`
`
`universally unique identifier by first user for
`
`recipients
`
`1 336
`
`
`
`
`
`Fig. 8A
`
`1 342
`
`
`
`1 372
`
`
`
`
`
`
`
`
`
`
`
`
`
`Creating audience list containing references to
`
`
`
`
`each member of audience collection
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Creating a first communication record in
`
`
`
`
`
`
`communication history based upon initiating
`
`
`request
`
`
`
`Fig. 88
`
`1 374
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 9
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 9
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 9 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`1412
`
`
`
`
`
`
`
`
`
`
`Sending instant messaging invitation email message
`
`
`
`
`
`
`
`containing body including web page actively embedded
`
`
`
`
`
`
`
`
`
`to associated email address designated for at. least one
`
`
`recipient
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Sending instant messaging invitation email message
`
`
`
`
`
`
`
`
`containing body including link to web page URL based
`
`
`
`
`
`
`
`
`upon universally unique identifier to associated email
`
`
`
`
`
`address designated for at least one recipient
`
`
`
`
`
`
`
`
`
`
`Sending instant messaging invitation email message
`
`
`
`
`
`
`containing body including icon referenced by universally
`
`
`
`
`
`
`unique identifier to associated email address designated
`
`
`
`
`for at least one recipient
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`1414
`
`
`
`
`Fig. 9
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 10
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 10
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 10 0f 13
`
`
`
`US 2004/0128356 A1
`
`2000
`
`
`
`upon at least one member of tactile input and acoustic input from user
`
`
`
`
`
`
`
`
`
`Providing support for email communication & web browser compliant
`
`
`
`
`
`
`
`communication used by user with communicatively coupled server based
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2012
`2032
`
`
`
`
`
`
`
`
`Sending instant messaging session request
`
`
`
`
`
`
`initiated by first user for designated recipients
`
`
`
`
`to communicatively coupled server
`
`
`
`
`
`
`
`
`
`
`
`
`
`Receiving instant messaging invitation email
`
`
`
`
`message for user as recipient from
`
`
`
`
`communicatively coupled server to create
`
`
`
`
`
`received instant messaging invitation email
`
`message
`
`
`
`
`
`
`
`receivestransferred communication from first member
`
`
`
`
`
`
`
`Receiving transferred communication from first member to create
`
`
`
`
`
`
`
`
`2056
`
`2054
`
`0 Fig. 100
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 11
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 11
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 11 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`
`
`
`
`
`
`
`2042
`
`
`
`
`
`
`
`Using received instant messaging invitation
`
`
`
`
`
`email message by recipient to create instant
`
`
`
`
`
`
`messaging response sent to communicatively
`
`
`coupled server
`
`
`
`
`
`
`
`
`
`
`Alerting recipient of received instant messaging
`
`
`
`
`
`invitation email message employing at least
`
`
`
`
`
`
`
`
`one of visual output, acoustic output and tactile
`
`output
`
`
`
`
`
`2080
`
`
`
`
`
`2074
`
`
`
`area associated with first member
`
`
`
`
`
`
`
`
`Presenting received-transferred communication from first member as content in
`
`
`
`
`
`
`
`Fig. 118
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 12
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 12
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 12 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`
`
`2114
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`2112
`
`
`
`
`
`
`
`Activating embedded web page referenced by
`
`
`
`
`
`
`
`
`universally unique identifier in received instant
`
`
`
`
`messaging invitation email message by
`
`
`
`
`
`recipient to create instant messaging response
`
`
`
`
`
`
`sent to communicatively coupled server
`
`
`
`
`
`
`
`
`
`
`Activating link to web page by URL based upon
`
`
`
`
`
`universally unique identifier in received instant
`
`
`
`
`messaging invitation email message by
`
`
`
`
`
`
`
`recipient to create instant messaging response
`
`
`
`
`
`
`sent to communicatively coupled server
`
`
`
`
`
`
`
`Activating icon referenced by universally
`
`
`
`
`
`
`unique identifier in received instant messaging
`
`
`
`
`
`
`
`invitation email message by recipient to create
`
`
`
`
`
`instant messaging response sent to
`
`
`
`communicatively coupled server
`
`
`
`
`
`
`
`
`
`2130
`
`2116
`
`Fig. 12A
`
`Database
`
`
`150
`
`
`
`
`
`
`Universally Unique ldentiferfli
`
`
`
`
`Audience List 162
`
`
`Communication History
`
`166
`
`
`
`
`
`
`
`
`
`Communication Record 168
`
`
`Fig. 123
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 13
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 13
`
`

`

`
`
`Patent Application Publication
`
`
`
`
`
`
`Jul. 1, 2004 Sheet 13 0f 13
`
`
`US 2004/0128356 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`User3 400
`
`
`
`
`
`User1 200- Language1 230
`User2 300- Language2 320
`
`
`Language3 430
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Received Comm from
`
`
`1st Member 142
`
`
`
`
`
`Language1 230
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Processed
`
`
`
`
`
`
`
`
`
`Transferred
`
`
`Communication 1%
`
`
`Communication m - Languagez 320
`
`
`
`
`I LanguageZ 320
`
`
`
`
`
`
`
`.
`
`Language3 430
`
`
`
`
`
`
`
`
`
`
`
`Language1 230
`
`
`
`
`
`
`
`Language3 430
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 14
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 14
`
`

`

`
`
`US 2004/0128356 A1
`
`
`Jul. 1, 2004
`
`
`
`EMAIL INTEGRATED INSTANT MESSAGING
`
`
`
`
`
`TECHNICAL FIELD
`
`
`
`
`
`
`
`
`
`
`
`
`[0001] This invention relates to initiation of an Instant
`
`
`
`
`
`
`
`
`Messaging (IM) session between two or more parties and
`communication using a “standard/standalone” Instant Mes-
`
`
`
`
`
`
`
`
`
`
`
`saging paradigm with or without email integration.
`BACKGROUND ART
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`[0002] There are at least four major problems that are
`
`
`
`
`
`
`common in today’s Instant Messaging (IM) systems includ-
`
`
`
`
`
`
`ing: “screen name” namespace problems, privacy problems,
`
`
`
`
`
`
`lack of acceptable and automated Instant Messaging mes-
`
`
`
`
`
`sage archiving, and service provider compatibility/software
`
`
`deliverability problems.
`
`
`
`
`
`
`
`[0003] The namespace problem can be broken down into
`
`
`
`three sub-problems, as follows:
`
`
`
`
`
`
`
`
`[0004]
`“Screen names” are not unique across IM provid-
`
`
`
`
`
`
`
`
`ers. In today’s Instant Messaging software, each Instant
`
`
`
`
`
`
`
`Messaging service provider maintains a separate and pro-
`
`
`
`
`
`
`
`prietary “screen name” namespace. This leads to users of
`
`
`
`
`
`
`
`
`
`one Instant Messaging service not being able to freely
`
`
`
`
`
`
`
`communicate with the users of a different Instant Messaging
`
`
`
`
`
`
`
`
`service provider because names in each namespace are not
`
`
`
`
`
`
`
`
`universal, so, for example, the user “Johril” in AOL’s Instant
`
`
`
`
`
`
`
`
`Messenger (AIM) might refer to John Smith, while “John P
`
`
`
`
`
`
`
`in Yahoo’s Messenger might refer to John Jones.
`
`
`
`
`
`
`
`
`[0005] Obtaining a desired name is difficult, and will only
`
`
`
`
`
`
`
`
`get more difficult. The namespaces available within each
`
`
`
`
`
`
`
`Instant Messaging provider are extremely crowded. For
`
`
`
`
`
`
`
`
`
`example, when signing up with the largest of the Instant
`
`
`
`
`
`
`
`Messaging providers, AOL’s Instant Messenger (AIM) ser-
`
`
`
`
`
`
`
`
`
`vice, a typical user would rarely succeed with their first
`choice for a screen name because there are over 90 million
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`names already in use. In the case of AOL, this problem will
`
`
`
`
`
`
`
`
`
`only get worse as over 3 million new users sign up for AIM
`each month.
`
`
`
`
`
`
`
`
`
`
`[0006]
`“Screen names” frequently have little or no con-
`
`
`
`
`
`
`
`nection to a person’s “real” name. Most Instant Messaging
`screen names are names like “doglover3”, “corvette33”, etc.,
`
`
`
`
`
`
`
`since, as described above, names like “John Smith” have all
`
`
`
`
`
`
`
`
`been taken. Therefore users end up with screen names which
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`are hard for others to remember. This problem is of particu-
`lar concern in the business world where universal and
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`recognizable user names are essential for conducting busi-
`ness.
`
`
`
`
`
`
`
`
`
`
`
`[0007] The privacy problem can be seen as follows. In the
`Instant Messaging environments available by current Instant
`
`
`
`
`
`
`
`
`
`
`
`
`
`Messaging providers a particular user’s presence online can
`
`
`
`
`
`
`easily, or even automatically, be detected by others. When a
`
`
`
`
`
`
`
`
`user begins an Instant Messaging session using one of these
`
`
`
`
`
`
`
`
`Instant Messaging providers, all other users who are inter-
`ested in this user are notified that the he just went “online”.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Some Instant Messaging providers do provide some protec-
`
`
`
`
`
`
`
`
`
`tion against this “presence detection”. They may allow users
`to set an option to either let “no one” know that they are
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`online, or to block certain people from knowing they are
`
`
`
`
`
`
`
`
`online. Unfortunately, these type of features are cumber-
`some to use since they are not automatic and force users to
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`constantly manage who can “see” them and who can’t.
`
`
`
`
`
`
`
`
`[0008] The Instant Messaging messaging archiving prob-
`
`
`
`
`
`
`
`
`lem can be seen as follows. Some currently available Instant
`
`
`
`
`
`
`
`Messaging client software allows users to save transcripts of
`
`
`
`
`
`
`
`
`an Instant Messaging session as a file on their computer disk.
`But the client software does not allow them to file these
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`sessions away, title them, etc., as they would with email, and
`
`
`
`
`
`
`
`
`
`the feature is cumbersome enough that most users either
`
`
`
`
`
`
`
`
`
`
`don’t know it exists, or simply don’t use it. This gives
`
`
`
`
`
`
`Instant Messaging a disadvantage when compared to email
`because it does not allow the user to maintain an automatic
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`archive of what was discussed in the Instant Messaging
`session.
`
`
`
`
`
`
`
`
`
`[0009] There are several problems associated with Instant
`
`
`
`
`
`
`Messaging service provider compatibility and software
`
`
`
`
`
`
`
`delivery. Today, Instant Messaging service providers require
`
`
`
`
`
`
`users download a particular piece of software to execute on
`
`
`
`
`
`
`
`
`their computer. This type of Instant Messaging software
`
`
`
`
`
`causes at least three major problems.
`
`
`
`
`
`
`[0010] Lack of interoperability causes a significant prob-
`
`
`
`
`
`
`
`
`lem. Each Instant Messaging service provider only supports
`
`
`
`
`
`
`
`
`its own Instant Messaging protocol and client software.
`
`
`
`
`
`
`
`
`Clients from one Instant Messaging service provider, using
`
`
`
`
`
`
`
`
`that service provider’s Instant Messaging software can typi-
`
`
`
`
`
`
`
`
`
`cally only communicate with other people who use the same
`
`
`
`
`
`
`
`service provider and software. A person cannot arbitrarily
`
`
`
`
`
`
`
`
`send an Instant Message to another person, unless that other
`
`
`
`
`
`
`
`
`
`person uses the same Instant Messaging service provider and
`
`
`
`
`
`
`
`
`
`software that
`they do. For example, “Joe” uses AOL’s
`
`
`
`
`
`
`
`Instant Messenger, and “Jane” uses Yahoo’s Messenger.
`Even if Joe and Jane know each other’s screen names, they
`
`
`
`
`
`
`
`
`
`
`cannot communicate with each other since they are using
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`different Instant Messaging service providers.
`
`
`
`
`
`
`[0011] Lack of platform independence is another problem.
`
`
`
`
`
`
`
`Today’s Instant Messaging service providers and software
`typically will only execute on a limited number of hardware
`
`
`
`
`
`
`
`
`
`
`
`
`
`platforms, so users on non-supported platforms will not be
`
`
`
`
`
`
`able to communicate with users on supported platforms.
`
`
`
`
`
`
`
`[0012] The inability to work through network “firewalls ”
`
`
`
`
`
`
`
`causes additional problems. The current Instant Messaging
`
`
`
`
`
`
`
`
`service providers and software offerings will typically not
`
`
`
`
`
`
`
`work through “firewalls”. Since most business enterprises
`
`
`
`
`
`
`
`
`have firewalls in place, these programs preclude users inside
`
`
`
`
`
`
`
`the organization from communicating with users outside of
`
`
`
`
`
`
`the organization. Additionally, as home networks become
`more prevalent,
`the use of firewalls will become more
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`common and the significance of this problem will increase.
`SUMMARY OF THE INVENTION
`
`
`
`
`
`
`
`
`
`[0013] Certain embodiments of the present invention are
`
`
`
`
`
`
`
`directed to a system supporting the initiation of an Instant
`
`
`
`
`
`
`
`
`Messaging (IM) session between two or more parties
`
`
`
`
`
`
`
`
`
`through the use of email programs and standard web brows-
`
`
`
`
`
`
`ers. Additionally, it allows users to communicate using a
`
`
`
`
`
`“standard/standalone” Instant Messaging paradigm (i.e.
`
`
`
`
`
`
`
`
`without email integration) which affords users the features
`
`
`
`
`
`
`
`
`of today’s popular Instant Messaging services, but also
`provides at least the additional benefits listed in the sum-
`
`
`
`
`
`
`
`
`
`mary.
`
`
`
`
`
`
`
`
`
`[0014] Regarding the namespace problem, users are not
`
`
`
`
`
`
`
`
`required to use proprietary “screen names”. Instead,
`the
`
`
`
`
`
`
`
`
`
`inventive system allows the parties to use their email address
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 15
`
`
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 15
`
`

`

`
`
`US 2004/0128356 A1
`
`
`Jul. 1, 2004
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`as their “screen name”. Email addresses have the advantages
`
`
`
`
`
`
`
`
`that they are much more pervasive and established than
`
`
`
`
`
`
`
`typical Instant Messaging “screen names”, and valid email
`
`
`
`
`
`
`addresses are guaranteed to be universally unique names.
`
`
`
`
`
`
`
`[0015] The present invention details a process whereby a
`
`
`
`
`
`
`
`
`computer user may send an “IM Enhanced” or “Live” email
`
`
`
`
`
`
`
`
`to another person, using a standard email program, by
`
`
`
`
`
`
`knowing only the recipient’s email address.
`
`
`
`
`
`
`
`[0016] Regarding the privacy problem, when an Instant
`
`
`
`
`
`
`
`
`Messaging session is initiated via email, strict privacy rules
`are enforced in a non-intrusive manner; one user cannot
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`“blindly” initiate a messaging session with another user,
`
`
`
`
`
`
`
`
`
`unless the second user accepts the Instant Messaging invi-
`
`
`
`
`
`
`
`
`tation. Furthermore, the initial chat request is not delivered
`
`
`
`
`
`
`
`
`via an Instant Message, rather, it is delivered in an email.
`
`
`
`
`
`
`
`
`Upon receipt of the email invitation, the recipient initiates an
`
`
`
`
`
`
`
`Instant Messaging conversation with the sender (who’s
`
`
`
`
`
`
`
`
`acceptance is implicit since the sender initiated the Instant
`
`
`
`
`
`
`Messaging request). When an Instant Messaging session is
`
`
`
`
`
`
`
`
`initiated via the “standalone” Instant Messaging web page,
`
`
`
`
`
`
`
`
`
`the user is able to control presence detection in the same
`
`
`
`
`
`
`
`sorts of ways as most commonly available Instant Messag-
`
`
`
`ing software allows.
`
`
`
`
`
`
`
`
`invention also details the process
`[0017] The present
`
`
`
`
`
`
`
`
`whereby users may indicate that presence detection is
`
`
`
`
`
`
`
`allowed only to certain individuals simply by sending those
`individuals an email/IM invitation. This email becomes the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`implicit “permission” for the recipient to converse with the
`
`
`
`
`
`
`
`
`
`
`
`sender, so no other action is required on the part of the
`
`
`
`
`
`
`
`
`sender. This provides a very dynamic and powerful means of
`
`
`
`
`
`
`granting “permission” to message, and the permissions may
`
`
`
`
`
`
`
`
`
`even be email message specific. This means that if Joe sends
`Jane an IM-enhanced email, Jane would be able to commu-
`
`
`
`
`
`
`
`nicate to Joe through that email, but
`if Jane used the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`standalone Instant Messaging service, she may not by able
`
`
`
`
`
`
`
`
`detect Joe’s presence, assuming Joe has “total privacy”
`selected.
`
`
`[0018] The sender is not able to initiate the Instant Mes-
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`saging conversation in any way other than through an email.
`
`
`
`
`
`
`
`
`This prevents users from getting Instant Messaging “spam”.
`
`
`
`
`
`
`
`
`If the recipient accepts the Instant Messaging invitation
`included in the email, they can begin a conversation with the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`sender (who is assumed to have implicitly accepted IMs
`
`
`
`
`
`
`
`
`from the recipient). Since these Instant Messaging conver-
`
`
`
`
`
`
`
`
`
`sations are initiated via email,
`the spam problem is also
`
`
`
`
`
`
`
`
`addressed by leveraging all of the protections already in
`
`
`
`
`
`
`
`
`
`place for protecting users against email spam, this includes
`
`
`
`
`
`eXisting legislation, filtering software, etc.
`
`
`
`
`
`
`
`[0019] Regarding the problem of Instant Messaging mes-
`
`
`
`
`
`
`
`
`sage archiving, users may choose to permanently save
`
`
`
`
`
`
`
`
`Instant Messaging sessions in much the same way that they
`
`
`
`
`
`
`
`
`save email. The Instant Messaging session might even be
`
`
`
`
`
`
`
`
`
`saved as part of the email. This allows Instant Messaging
`
`
`
`
`
`
`archives to be referred back to in the future. Additionally, if
`there was an Instant Messaging session as a result of an
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`email, that Instant Messaging session will be automatically
`
`
`
`
`
`
`
`
`saved in conjunction with the email, so that anytime in the
`
`
`
`
`
`
`
`
`
`future the user chooses to read that particular piece of email,
`
`
`
`
`
`
`
`they will also see the associated messaging.
`
`
`
`
`
`
`
`
`[0020] Upon receiving such an email, the recipient will be
`
`
`
`
`
`
`
`
`
`
`able to read the email “body” as they always have, and
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`below the email body will be an area in which to participate
`
`
`
`
`
`
`
`
`in an Instant Messaging conversation with the sender.
`
`
`
`
`
`
`[0021] As the Instant Messaging session proceeds, it is
`
`
`
`
`
`
`
`constantly being saved on the server computer, which pro-
`
`
`
`
`
`
`
`
`vides the Instant Messaging support. This allows users to file
`
`
`
`
`
`
`
`
`away emails as always, and at any future time, when they
`
`
`
`
`
`
`
`
`view the email, the full transcript of the Instant Messaging
`
`
`
`
`
`
`
`
`session will also appear. This allows users to both maintain
`
`
`
`
`
`
`
`
`conversations about the email together with the email, as
`well as to maintain an automatic archive of their Instant
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Messaging session (users would, of course, be able to
`
`
`
`disable this feature).
`
`
`
`
`
`
`[0022] Regarding Instant Messaging service provider
`
`
`
`
`
`
`
`compatibility and software delivery problems, no explicit
`
`
`
`
`
`
`
`
`signup or software is needed. Sender and recipient need not
`
`
`
`
`
`
`
`
`be signed up with a common Instant Messaging service
`
`
`
`
`
`
`
`provider, or any service provider at all in order to message
`
`
`
`
`
`
`
`
`
`each other. Users may “message” each other without the
`
`
`
`
`
`
`
`need for explicit client software downloads. Messaging is
`
`
`
`
`
`
`
`performed with standard DHTML within an email window
`
`
`
`
`
`
`
`
`
`[though the Instant Messaging part of this invention can also
`
`
`
`
`
`
`
`
`
`be utilized in an “IM only” mode, without the use of email].
`
`
`
`
`
`
`
`
`
`[0023] This “IM area” is rendered within the email mes-
`
`
`
`
`
`
`
`sage, using only generally available browser technologies,
`
`
`
`
`
`
`
`
`such as DHTML. No other software is required for the user
`
`
`
`
`
`
`
`
`
`to download, and no “plugins” are required. This allows any
`
`
`
`
`
`
`
`user with a popular browser to immediately, and seamlessly,
`
`
`
`
`
`participate in an Instant Messaging session.
`
`
`
`
`
`
`
`
`[0024] The whole Instant Messaging session takes place
`
`
`
`
`
`
`
`using only the publicly-defined internet protocol known as
`
`
`
`
`
`
`HTTP allowing Instant Messaging conversations to take
`place across firewalls. The present invention also details the
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`process whereby a computer user may send or receive
`“standard” Instant Messages,
`from a web-based Instant
`
`
`
`
`
`
`
`
`
`
`
`
`Messaging web page/application. The implementation of
`
`
`
`
`
`
`
`
`
`this “standalone” web page uses the same software “engine”
`as the software described above, which allows users to
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Instant Messaging each other within their emails. Though
`there are many benefits to the email/Im solution, a standa-
`
`
`
`
`
`
`
`
`lone solution is required as well, since the sender needs a
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`way to communicate with the recipient once the recipient
`chooses to initiate an Instant Messaging session. Addition-
`
`
`
`
`
`
`
`ally, users often choose to communicate only via Instant
`
`
`
`
`
`
`
`
`Messages, and not use email. It is in the standalone incan-
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`tation of this software where the privacy and presence-
`
`
`
`
`
`
`
`hiding and http presence-detection features of this software
`shine.
`
`
`
`
`
`
`
`
`[0025] These and other advantages of the present inven-
`
`
`
`
`
`
`
`tion will become apparent upon reading the following
`
`
`
`
`
`
`
`detailed descriptions and studying the various figures of the
`
`drawings.
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`
`
`
`
`
`
`
`
`
`[0026] FIG. 1 depicts a system comprising a server 100
`
`
`
`
`communicatively coupled to associated client computers
`
`
`
`
`
`
`used by users supporting email communications and web
`
`
`
`
`
`browser compliant communications to provide instant mes-
`saging between at least two of the users;
`
`
`
`
`
`
`
`
`
`
`
`
`[0027] FIG. 2A depicts a detail flowchart of server pro-
`
`
`
`
`
`
`
`gram system 1000 of FIG. 1 for supporting instant messag-
`ing between at least two of the users;
`
`
`
`
`
`
`Samsung v. Uniloc, |PR2017-1799
`Uniloc's Exhibit 2002, page 16
`
`
`
`
`
`
`
`
`
`Samsung v. Uniloc, IPR2017-1799
`Uniloc's Exhibit 2002, page 16
`
`

`

`
`
`US 2004/0128356 A1
`
`
`Jul. 1, 2004
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`[0028] FIG. 2B depicts a detail flowchart of operation
`
`
`
`
`
`
`
`1012 of FIG. 2A for creating the instant messaging session;
`
`
`
`
`
`
`
`[0029] FIG. 3 depicts a detail flowchart of operation 1022
`
`
`
`
`
`
`
`
`of FIG. 1 for providing the instant messaging session;
`
`
`
`
`
`
`[0030] FIG. 4A depicts a detail flowchart of operation
`
`
`
`
`
`
`
`1122 of FIG. 3 for transferring the at least one received
`communication from the first member;
`
`
`
`
`
`
`
`
`
`
`
`[0031] FIG. 4B depicts a detail flowchart of server pro-
`
`
`
`
`
`
`
`gram system 1000 of FIG. 1 for supporting instant messag-
`
`
`
`
`
`ing between at least two users;
`
`
`
`
`
`
`[0032] FIG. 5A depicts a detail flowchart of operation
`
`
`
`
`
`1192 of FIG. 4B for maintaining the database referencing
`
`
`the history;
`
`
`
`
`
`
`[0033] FIG. 5B depicts a detail flowchart of operation
`
`
`
`
`
`
`
`1172 of FIG. 4A for sending the at

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket