`(12) Patent Application Publication (10) Pub. No.: US 2004/0128356A1
`Bernstein et al.
`(43) Pub. Date:
`Jul. 1, 2004
`
`US 2004.0128356A1
`
`(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.:
`10/311,259
`(22) PCT Filed:
`Jun. 25, 2001
`
`(86) PCT No.:
`
`PCT/US01/20381
`
`Related U.S. Application Data
`(60) Provisional application No. 60/214,157, filed on Jun.
`26, 2000.
`Publication Classification
`
`(51) Int. Cl. ................................................ G06F 15/16
`(52)
`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.
`
`ye
`
`User2
`3OO
`
`User3
`400
`
`Client
`Computer
`210
`
`Client
`Cogger
`
`Client
`Compute
`p 410
`
`
`
`
`
`212
`
`312
`
`42
`
`Memory
`220 Program
`System
`
`224
`
`222
`
`
`
`Server
`Computer
`10
`
`Database
`
`104
`
`History
`154
`
`152
`
`56
`
`324
`
`322
`
`
`
`420 Program
`System
`2OOO
`
`422
`
`424
`
`Server Memory
`120
`Program
`System
`OOO
`
`Server 100
`
`102
`
`Universaily Unique
`identifer 58
`Audience List
`62
`
`164
`
`16O
`Communication History
`166
`Communication
`Record 188
`
`
`
`stant
`Messaging
`Session
`130
`
`Universally Unique
`identifer 32
`
`First User 134.
`
`Recipients 136
`
`Audience Collection
`138
`
`Web Page with
`Identifer 4
`Received Comm from
`1st Member 142
`Processed
`Communication 44
`Transferred
`Communication 146
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 1
`
`
`
`Patent Application Publication
`
`Jul. 1, 2004 Sheet 1 of 13
`
`US 2004/O128356A1
`
`
`
`
`
`ÁJoulew JeAJ?S
`
`uueuôOJd | Ozz
`
`uuelfiodd | OZ7
`
`ZZ$7
`
`
`
`
`
`
`
`
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 2
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 2 of 13
`
`US 2004/0128356 A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`1OOO
`
`1012
`
`Creating instant messaging Session with
`universally unique identifier initiated by first
`user for recipients designated as at least one
`of remaining of users
`
`Providing instant messaging session identified
`by universally unique identifier as formatted
`web page to each designated recipients and to
`first user
`1024
`
`
`
`
`
`1014
`
`Fig. 2A
`
`1012
`
`Receiving instant messaging session request
`from first user for recipients designated by
`asSociated email address for at least one
`remaining user
`
`1052
`
`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. 2B
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 3
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 3 of 13
`
`US 2004/O128356A1
`
`
`
`Creating web page referenced based upon
`universally unique identifier
`
`Providing web page with area associated with
`first user for participation
`
`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
`asSociated with first member
`
`Fig. 3
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 4
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 4 of 13
`
`US 2004/0128356 A1
`
`1122
`
`
`
`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
`
`
`
`
`
`
`
`
`
`
`
`Maintaining database referencing history of instant messaging session
`with universally unique identifier
`
`Fig. 4B
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 5
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 5 of 13
`
`US 2004/0128356A1
`
`1.192
`
`Maintaining history of instant messaging session with universally unique
`identifier for audience collection
`
`Sending processed communication from first member as content in area
`associated with first member to history of instant messaging session with
`universally unique identifier
`
`1232
`
`
`
`
`
`
`
`
`
`
`
`Receiving transferred communication from first member at history to create
`history-received communication from first member
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 6
`
`
`
`Patent Application Publication
`
`Jul. 1, 2004
`
`Sheet 6 of 13
`
`US 2004/0128356A1
`
`
`
`ZZ$7
`
`Z
`
`9:61
`
`000 ||
`
`uuelfioud | OZ9
`
`zze
`
`;
`Z
`Z
`
`uJeuôOJd | OZZ
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 7
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 7 of 13
`
`US 2004/O128356A1
`
`1262
`
`
`
`1272
`
`Creating new communication record Containing
`first member history-received communication
`as communication from first member
`
`
`
`
`
`Adding new communication record to
`communication history
`
`Fig. 7A
`
`1274
`
`Sending database initiating request for instant messaging Session with
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 8
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 8 of 13
`
`US 2004/0128356 A1
`
`
`
`
`
`
`
`
`
`1192
`
`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
`
`1336
`
`Fig. 8A
`
`1342
`
`1372
`
`Creating audience list containing references to
`each member of audience collection
`
`
`
`
`
`
`
`Creating a first communication record in
`communication history based upon initiating
`request
`
`
`
`1374
`
`Fig. 8B
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 9
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 9 of 13
`
`US 2004/O128356A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`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, IPR2017-1800
`Uniloc's Exhibit 2006, page 10
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 10 of 13
`
`US 2004/0128356 A1
`
`2OOO
`
`Providing support for email communication & Web browser Compliant
`communication used by user with communicatively Coupled Server based
`upon at least one member of tactile input and acoustic input from user
`
`
`
`
`
`
`
`2012
`
`2O32
`
`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
`
`
`
`
`
`
`
`Receiving transferred communication from first member to create
`received-transferred communication from first member
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 11
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 11 of 13
`
`US 2004/O128356A1
`
`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
`
`
`
`
`
`
`
`
`
`
`
`
`
`Presenting received-transferred communication from first member as content in
`area associated with first member
`
`Fig. 11B
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 12
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 12 of 13
`
`US 2004/O128356A1
`
`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
`
`2114
`
`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
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Database
`15O
`
`Universally Unique identifer158
`
`Audience List 162
`
`Communication History
`166
`
`Communication Record 168
`
`Fig. 12B
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 13
`
`
`
`Patent Application Publication Jul. 1, 2004 Sheet 13 of 13
`
`US 2004/O128356A1
`
`
`
`
`
`USer1 200
`
`Language1230
`
`User2 300
`
`Language2320
`
`
`
`USer3 400
`
`
`
`Language3430
`
`Received Comm from
`1st Member 142
`
`Language1230
`
`
`
`
`
`PrOCeSSed
`Communication 144
`
`
`
`
`
`Transferred
`Communication 146
`
`
`
`
`
`
`
`
`
`
`
`Language2320
`
`Language3430
`
`Language1230
`
`Language2320
`
`Language3430
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 14
`
`
`
`US 2004/O128356 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
`CSS.
`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, IPR2017-1800
`Uniloc's Exhibit 2006, page 15
`
`
`
`US 2004/O128356 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.
`0.015 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.
`0.017. The present invention also details the process
`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.
`0.018. 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.
`0.019
`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, IPR2017-1800
`Uniloc's Exhibit 2006, page 16
`
`
`
`US 2004/O128356 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 least one processed
`communication from the first member;
`0034 FIG. 5C depicts a detail flowchart of operation
`1212 of FIG. 5A for maintaining the history;
`0035 FIG. 6 is a refinement of FIG. 1 showing server
`100 coupled 102 to instant messaging session 130 and
`further coupled 104 to database 150;
`0036 FIG. 7A depicts a detail flowchart of operation
`1262 of FIG. 5C for maintaining the communication his
`tory;
`0037 FIG. 7B depicts a detail flowchart of operation
`1272 of FIG. 7A for creating the instant messaging session
`with the universally unique identifier;
`0038 FIG. 7C depicts a detail flowchart of operation
`1192 of FIG. 4B for maintaining the database;
`0039 FIG. 8B depicts a detail flowchart of operation
`1342 of FIG. 8A for creating the history;
`0040 FIG.9 depicts a detail flowchart of operation 1172
`of FIG. 4A for Sending the instant messaging invitation
`email message to the associated email address designated for
`each of the recipients,
`0041 FIG. 10A depicts a detail flowchart of client pro
`gram system 2000 of FIGS. 1 and 6 for controlling the
`asSociated client computer based upon the use by the user
`and the communicatively coupled server 100;
`0042 FIG. 10B depicts a detail flowchart of operation
`2012 of FIG. 10A for support of email and web browser
`compliant communication;
`0043 FIG. 10C depicts a detail flowchart of operation
`2012 of FIG. 10A for providing Support for email commu
`nication and for web browser compliant communication;
`0044 FIG. 11A depicts a detail flowchart of operation
`2042 of FIG. 10B for receiving the instant messaging
`invitation email message;
`004.5 FIG. 11B depicts a detail flowchart of operation
`2052 of FIG. 10C for receiving the transferred communi
`cation;
`FIG. 12A depicts a detail flowchart of operation
`0.046
`2072 of FIG. 11A for using the received instant messaging
`invitation email message by the recipient;
`
`0047 FIG. 12B shows a refinement of the relationships
`involved with database 150 of FIG. 6 regarding references
`involved with it and its components, and
`0048 FIG. 13 depicts an application of the instant mes
`Saging System in a Situation where different users prefer
`multiple languages.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`0049 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.
`0050. The server computer 110 delivers formatted web
`pages to the client computer providing an area for the user
`of the client computer to participate in an Instant Messaging
`Session. Each Instant Messaging Session has a universally
`unique identifier, which the Server computer uses to identify
`and Store individual Instant Messages.
`0051) Server 100 communicatively couples 224 to client
`computer 210 used by user 200 supporting email commu
`nications and web browser compliant communications.
`Similarly, server 100 communicatively couples 324 and 424
`to client computers 310 and 410 user by users 300 and 400,
`respectively.
`0.052 Server 100 includes server computer 110 accessi
`bly coupled 122 to server memory 120. Server program
`system 1000 operates server 100 and is comprised of pro
`gram Steps residing in Server memory 120.
`0053. Each client computer 210, 310, and 410, is acces
`sibly coupled 222,322 and 422 to a respective memory 220,
`320, and 420. In certain embodiments of the invention,
`program System 2000 operates the associated client com
`puter based upon the interaction of the user and communi
`cations with server 100.
`0054 Each user may employ at least one of acoustic and
`tactile input to the associated client computer in its use. The
`usage may vary. By way of example, user 200 may use 212
`tactile input Such as a keyboard and pointing device. User
`300 may use 312 acoustic input exclusively. User 400 may
`user 412 a combination of acoustic and tactile input.
`0055. User presentation of instant messaging communi
`cation as well as alerts regarding instant messaging invita
`tions may be presented in at least one of the following ways:
`Visually, acoustically, and tactilely.
`0056 By way of example, the visual alert may include an
`icon presented on a view Screen, or by turning on a light. The
`acoustic alert may emit at least one of the following: an alert
`Sound or an alert audio message. A tactile alert may include
`raising or lowering a tactile output member, Such as found
`on a Braille keyboard. Any of these alerts may include a
`representation of the first user, the time of receipt of the
`invitation, as well as other information which may be part of
`the invitation, Such as the intended topic or agenda of the
`instant messaging Session.
`0057 By way of example, the areas of a web page may
`be associated with distinct voices by which contented pre
`Sented in an area may be acoustically presented to the user.
`
`Samsung v. Uniloc, IPR2017-1800
`Uniloc's Exhibit 2006, page 17
`
`
`
`US 2004/O128356 A1
`
`Jul. 1, 2004
`
`The acoustic presentation may follow the order of receipt of
`the transferred communication, or the user may specify that
`a priority Scheme by which various transferring communi
`cations received within a period of time are ordered for
`presentation. The user may further specify that differing
`Voices may be presented louder or Softer. The user may
`Silence a Voice.
`0.058 Note that the server 100 communicatively coupled
`to the associated client computer used by the user may
`further support a version of TCP-IP compliant protocols in
`communication with the user, for at least one of the users.
`0059) Server 100 communicatively coupled to the asso
`ciated client computer used by the user may further Support
`at least one of the following:
`0060 a version of Wireless Application Protocol
`(WAP) compliant protocols in communication with
`the user;
`0061 a version of Bluetooth compliant protocols in
`communication with the user;
`0062) a version of HTTP compliant protocols in
`communication with the user; and
`0063) a version of XML compliant protocols in
`communication with the user.
`Instant messaging session 130 involves a univer
`0064.
`Sally unique identifier 132 and web page 140 based upon that
`universally unique identifier, initiated by a first user 134
`involving at least one recipient 136 contacted by email
`through their email address. Each recipient 136 is Sent an
`instant messaging invitation email message.
`0065. The first user 134 is a member of the audience
`collection 138. When and if a recipient 136 responds to the
`instant messaging invitation email message, it becomes a
`member of the audience collection 138.
`0.066 When a communication 142 is received from a first
`member of the audience collection 138, a transferred com
`munication 144 from the first member is sent to all audience
`collection members.
`0067. Upon receipt of communication 142, it may be
`processed to create the processed communication 142 from
`the first member, which is then Sent to all audience collection
`members as the transferred communication 144.
`0068 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.
`0069 Arrow 1010 directs the flow of execution from
`starting operation 1000 to operation 1012. Operation 1012
`performs creating an instant messaging Session with a uni
`versally unique identifier initiated by a first of the users for
`recipients designated as at least one of the remaining of the
`users. Arrow 1014 directs execution from operation 1012 to
`operation 1016. Operation 1016 terminates the operations of
`this flowchart.
`0070 Arrow 101010 directs the flow of execution from
`starting operation 1000 to operation 101012. Operation
`101012 performs providing the instant messaging Session
`identified by the universally unique identifier as a formatted
`web page to each of the designated recipients and to the first
`
`user. Arrow 101014 directs execution from operation
`101012 to operation 1016. Operation 1016 terminates the
`operations of this flowchart.
`0071 FIG. 2B depicts a de