`
`WO 2004/049625
`
`PCT/US2003/038 I 35
`
`wireless communication networks. By way of example, data network 102 may
`
`be implemented through a Wide Area Network ("WAN"), Local Area Network
`
`("LAN"), an intra net and/or the Internet. Further, the service center 106 may
`
`be connected to multiple data networks 102, such as, for example, to a
`
`wireless carrier network and to the Internet.
`
`[026] Voice network 104 may provide telephony services to allow a
`
`calling party, such as calling party 120, to place a telephone call to user 110.
`
`In one embodiment, voice network 104 may be implemented using a network,
`
`such as the Public Switched Telephone Network ("PSTN"). Alternatively,
`
`voice network 104 may be implemented on a voice over broadband network,
`
`
`
`such as a network using voice-over Internet Protocol C'VolP'1) technology.
`
`Additionally, in other embodiments, the voice network may be a video over
`
`broadband network, such as, for example, a network for pro~iiding 2-way
`
`video communications. In another example, the voice network may be a
`
`I
`
`wlreless broadband network, such as, for example, a network using WiFi (i.e.,
`
`IEEE 802.11(b) and/or (g)). In yet another example, voice network 104 may
`
`be a wireless voice network{s), such as, for example, a cellular or third(cid:173)
`
`generation cellular network). In addition, voice network 104 may be
`
`implemented using any single or combination of the above-described
`
`technologies consistent with the principles of the present invention. Further,
`
`service center 106 may be connected to multiple voice networks 104, such as
`for example, Verizon's ™ Voice Network, voice networks operated by other
`carriers, and wireless carrier networks.
`
`[027] Service center 106 provides a platform for managing
`
`communications over data network 102 and voice network 104. Service
`
`center 106 also provides gateway functions, such as code and protocol
`
`conversions, to transfer communications between data network 102 and voice
`network 104. Service center 106 may be implemented using a combination of
`hardware, software, and/or firmware. For example, service center 106 may
`
`be implemented using a plurality of general purpose computers or servers
`
`coupled by a network (not shown). Although service center 106 is shown
`
`8
`
`Page 256 of 382
`
`GOOGLE EXHIBIT 1009 (Part 2 of 2)
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 12 of 81
`
`WO 2004/049625
`
`PCT/U S2003/038 l 35
`
`with direct connections to data network 102. and voice network 104, any
`
`number and type of network elements may be interposed between service
`
`center 106, data network 102, and voice network 104.
`[028) User terminal 112 provides user 11 0 an interface to data
`network 102. For example, user terminal 112 may be implemented using any
`
`device capable of accessing the Internet, such as a general purpose
`
`computer or personal computer equipped with a modem. User terminal 112
`
`may also be implemented in other devices, such as the Blackberry™, and
`Ergo Audrey™. Furthermore, user terminal 112 may be implemented in
`
`wireless devices, such as pagers, mobile phones (with data access
`
`functions), and Personal Digital Assistants ("PDAs"} with network
`
`connections.
`[029) User terminal 112 also allows user 11 0 to communicate with
`service center 106. For example, user 110 may use Instant Messaging ("IM'')
`to communicate with service center 106. In addition, user terminal 112 may
`
`use other aspects of TCP/IP including the Hypertext Transfer Protocol
`("HTTP"); the User Datagram Protocol ("UDP"); the File Transfer Protocol
`
`("FTP"); the Hypertext Markup Language ("HTML"); and the eXtensible
`
`Markup Language ("XML").
`[030} Furthermore, user terminal 112 may communicate directly with
`service center 106. For example, a client application may be installed on user
`terminal 112, which directly communicates with service center 106. Also,
`
`user terminal 112 may communicate with service center 106 via a proxy.
`[031] Phones 114, 116, 118, and 122 interface with voice networl<
`104, Phones 114, 116, 118, and 122 may be implemented using known
`devices, including wireline phones and mobile phones. Although phones 114,
`116, 118, and 122 are shown directly connected to voice network 104, any
`number of intervening elements, such as a Private Branch Exchange (''PBX"),
`
`may be interposed between phones 114, 116, 118, and 122 and voice
`
`network 104.
`
`9
`
`Page 257 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 13 of 81
`
`WO 2004/049625
`
`PCT/US2003/038 I 35
`
`[032] Fig. 2 is a block diagram of a user terminal consistent with the
`
`present invention. User terminal 112 may include a Central Processing Unit
`
`("CPU") 200, a memory 202, a storage module 204, a network interface 206,
`
`an input interface 208, an output interface 210, an input device 216, and an
`
`output device 218.
`
`[033] CPU 200 provides control and processing functions for user
`
`terminal 112. Although Fig. 2 illustrates a single CPU, user terminal 112 may
`
`include multiple CPUs. CPU 200 may also include, for example, one or more
`
`of the following: a co-processor, memory, registers, and other processing
`
`devices and systems as appropriate. CPU 200 may be implemented, for
`
`example, using a Pentium™ processor provided from Intel CorporationTM_
`
`[034] Memory 202 provides a primary memory for CPU 200, such as
`
`for program code. Memory 202 may be embodied with a variety of
`
`components of subsystems, including a Random Access Memory ("RAM")
`
`and a Read-Only Memory (''ROM"). When user terminal 112 executes an
`
`application installed in storage module 204, CPU 200 may download at least
`
`a portion of the program code from storage module 204 into memory 202. As
`
`CPU 200 executes the program code, CPU 200 may also retrieve additional
`
`portions of program code from storage module 204.
`
`[035] Storage module 204 may provide mass storage for user terminal
`
`112. Storage module 204 may be implemented with a variety of components
`
`or subsystems including, for example, a hard drive, an optical drive, CD ROM
`
`drive, DVD drive, a general-purpose storage device, a removable storage
`
`device, and/or other devices capable of storing information. Further, although
`
`storage module 204 is shown within user terminal 112, storage module 204
`
`may be implemented external to user terminal 112.
`
`[036] Storage module 204 includes program code and information for
`
`user terminal 112 to communicate with service center 106. Storage module
`
`204 may include, for example, data structures or program code for a calendar
`
`application, such as GroupWise™ provided by Novell Corporation™ or
`
`Outlook provided by Microsoft Corporation™; a client application, such as a
`
`10
`
`Page 258 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 14 of 81
`
`WO 2004/049625
`
`PCT/US2003/038J35
`
`Microsoft Network Messenger Service ("MSNMS") client or America Online
`
`Instant Messenger (AIM) client; and an Operating System ("OS"), such as the
`
`Windows Operation System provided by Microsoft Corporation. In addition,
`
`storage module 204 may include other program code and information, such
`
`as program code for TCP/I P communications; kernel and device drivers;
`
`configuration information, such as a Dynamic Host Configuration Protocol
`
`("DHCP") configuration; a web browser, such as Internet Explorer™ provided
`
`by Microsoft Corporation, or Netscape CommunicatorTM provided by Netscape
`
`Corporation™; and any other software that may be installed on user terminal
`
`112.
`
`[037] Network interface 206 provides a communications interface
`
`between user terminal 112 and data network 102. Network interface 206 may
`
`receive and transmit communications for user terminal 112. For example,
`
`network interface 206 may be a modem, or a LAN port.
`
`[038] Input interface 208 receives input from user 110 via input device
`
`212 and provides the input to CPU 200. Input device 212 may include, for
`
`example, a keyboard, a microphone, and a mouse. Other types of input
`
`devices may also be implemented consistent with the principles of the present
`
`invention.
`
`(039] Output interface 21 O provides information to user 110 via output
`
`device 214. Output device 214 may include, for example, a display, a printer,
`
`and a speaker. Other types of output devices may also be implemented
`
`consistent with the principles of the present invention.
`
`[040) Fig. 3 is a diagram of a voice network, consistent with the
`
`principles of the present invention. As shown, voice network 104 includes an
`
`Intelligent Service Control Point ("ISCP") 302, Service Transfer Points (''STP")
`
`304 and 306, service switching points ("SSP") 308 and 310, a Line
`
`
`
`Information Database (4'LIDB'1} 312, an ISCP Service Provisioning And
`
`Creation Environment ("SPACE") 314, a Recent Change Environment
`
`("RCE") 316, an Intelligent Peripheral ("IP'') 320, and a switch access 322.
`
`Although this embodiment of a voice network 104 is described as a PSTN, as
`
`11
`
`Page 259 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 15 of 81
`
`WO 2004/().t9625
`
`PCT/US2003/0381 J:1i
`
`discussed above in other embodiments, voice network 104 may be, for
`
`example, a voice or video over broadband network a wireless broadband, a
`
`wireless voice network, etc.
`[041J Voice network 104 may be implemented using the PSTN and
`SS7 as a signaling protocol. The SS7 protocol allows voice network 104 to
`
`provide features, such as call forwarding, caller-ID, three-way calling, wireless
`
`services such as roaming and mobile subscriber authentication, local number
`
`portability, and toll-free/toll services. The SS? protocol provides various types
`
`of messages to support the features of voice network 104. For example,
`
`these SS? messages may include Transaction Capabilities Applications Part
`
`("TCAP") messages to support event "triggers,'' and queries and responses
`
`between ISCP 302 and SSPs 308 and 310.
`
`{042] ISCP 302 may also be, for example, a standard service control
`
`point (''SCP") or an Advanced Intelligent Network {"AIN") SCP. ISCP 302
`
`provides translation and routing services of SS7 messages to support the
`
`features of voice network 104, such as call forwarding. In addition, ISCP 302
`
`may exchange information with the service center 106 using TCP/IP or SS7.
`
`ISCP 302 may include service logic used to provide a switch, such as SSP
`
`308 or 310, with specific call processing instructions. ISCP 302 may also
`
`store data related to various features that a user may activate. Such features
`
`may include, for example, call intercept and voice mail. ISCP 302 may be
`
`implemented using a combination of known hardware and software. ISCP
`
`302 is shown with a direct connection to service center 106 and a connection
`
`to ISCP SPACE 314, however, any number of network elements including
`
`routers, switches, hubs, etc., may be used to connect ISCP 302, ISCP
`
`SPACE 314, and service center 106. Further, information exchanged
`
`between the ISCP 302 and service center 106 may use, for example, the SR-
`
`3389 General Data Interface {"GDI") for TCP/IP.
`
`[043] STPs 304 and 306 relay SS7 messages within voice network
`
`104. For example, STP 304 may route SS? messages between SSPs 308
`
`12
`
`Page 260 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 16 of 81
`
`WO 2004/049625
`
`PCT/ US2003/038135
`
`and 310. STP 302 may be implemented using known hardware and software
`
`from manufacturers such as NORTEL TM and LUCENT Technologies™.
`
`[044] SSPs 308 and 310 provide an interface between voice network
`
`104 and phones 114 and 120, respectively, to setup, manage, and refease
`
`telephone calls within voice network 104. SSPs 308 and 310 may be
`
`implemented as a voice switch, an SS7 switch, or a computer connected to a
`
`switch. SSPs 308 and 310 exchange SS7 signal units to support a telephone
`
`call between calling party 120 and user 110. For example, SSPs 308 and
`
`310 may exchange SS7 messages, such as TCAP messages, within
`
`Message Signal Units ("MSU") to control calls, perform database queries to
`
`configuration database 312, and provide maintenance information,
`
`[045) LIDB 312 comprises one or more known databases to support
`
`the features of voice network 104. For example, LIDS 312 may include
`
`subscriber (i.e., a user that is a customer of a business entity providing
`
`services through one or more components of environment 100) information,
`
`such as a service profile, name and address, and credit card validation
`
`information. Although, in this figure, LIDB 312 is illustrated as directly
`
`connected to ISCP 302, LIDS 312 may be connected to ISCP 302 through an
`
`STP (e.g., 304 and 306), Additionally, this communication link may use, for
`
`example, the GR-2838 General Dynamic Interface ("GDI") for SS7.
`
`[046]
`
`ISCP SPACE 314 may be included as part of the ISCP 302 or
`
`be separate from the ISCP 302. For example, the Telcordic;1™ ISCP may
`
`include an environment similar to SPACE 314 as part of the product. Further,
`
`ISCP SPACE 314 may include one or more servers. ISCP SPACE 314 is the
`
`point in the ISCP platform where customer record updates may be made.
`
`[047] In one embodiment, customer records may be stored in ISCP
`
`SPACE 314 such that the records may be updated and sent to ISCP 302.
`
`These records may include information regarding how to handle calls directed
`
`to the customer. For example, these customer records may include
`
`information regarding whether or not calls for the customer are to be
`
`forwarded to a different number, and/or whether or not the call should be
`
`13
`
`Page 261 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 17 of 81
`
`WO 2004/049625
`
`PCT/ US2003/038JJ5
`
`directed to an IP, such as a voice mail system, after a certain number of rings.
`
`Additionally, one ISCP SPACE 314 may provide updates to one or more
`
`ISCPs 302 via an ISCP network (not shown).
`
`[048] Additionally, voice network 104 may include one or more recent
`
`change engines 316 such as, for example, an Enterprise Recent Change
`
`engine ("eRC"); an Assignment, Activation, and Inventory System {°AAIS''); or
`
`a Multi~Services Platform ("MSP"). As an example, {he eRC and AAIS may
`
`be used in voice networks 104 located in the western part of the United
`
`States, while an MSP may be used in networks in the eastern part. The
`
`recent change engines may be used to update switch and ISCP databases.
`
`For example, a recent change engine may deliver database updates to SSPs
`
`and to ISCPs, such that when updating databases, these recent change
`engines emulate human operators. Additionally, if the instructions are to be
`sent to an ISCP 302, the recent change engine may first send the instructions
`
`to ISCP SPACE 314, which then propagates the instructions to ISCP 302 as
`
`discussed above. Further, an MSP or eRC may be used, for example, for
`
`provfding updates to both SSPs 308 or 310 and ISCPs 302. Or, for example,
`
`an eRC may be used for providing updates to SSPs 308 or 310, while an
`
`AAIS is used for providing updates to ISCPs 302.
`
`[049] Updates sent to SSPs 308 or 31 O may be sent from the recent
`
`change engine 316 via a switch access 322 that may, for example, convert
`
`the updates into the appropriate protocol for SSP 308 or 310. For example,
`
`recent change engine 316 may send updates to SSPs 308 or 310 via TCP/IP.
`
`Switch access 322 may then convert the updates from TCP/IP to X.25. This
`
`switch access 322 may be implemented using hardware and/or software.
`
`These connections may include any number of elements, such as, for
`
`example, switches, routers, hubs, etc. and may be, for example, an internal,
`
`data network for voice network 104.
`
`[050] Voice network 104 may also include one or more IPs. For
`
`example, in Figure 3, an IP 320 is illustrated as being connected to SSP 308.
`
`These !Ps may be used for providing functions for interaction between users
`
`14
`
`Page 262 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 18 of 81
`
`WO 2004/049625
`
`PCT/US2003/038 I 35
`
`and the voice network, such as voice mail services, digit collection,
`
`customized announcements, voice recognition, etc. Moreover, the
`
`communications between SSP 308 and IP 320 may use the Primary Rate
`
`interface ((IPRi") (e.g., the 1129 protocol) protocol. Additionally, the IP 320
`
`may be capable of sending and receiving information to/from the Service
`Center 106. These communications may use, for example, the SR-3511
`protocol. Further, although Figure 3 illustrates this connection as a direct
`
`connection, this connection may include any number of elements including
`
`routers, switches, hubs, etc., and may be via, for example, an internal data
`network for voice network 104.
`(051] Fig. 4 is a block dia9ram of a service center, consistent with the
`principles of the present invention. As shown, service center 106 may include
`firewalls 402 and 404, one or more digital companion servers 406, one or
`
`more communication portal servers 408, one or more network access servers
`410, and a voice portal 412. The voice portal 412 may include a voice portal
`application server 414 and a voice recognition server 416. A network 418
`
`may be used to interconnect the firewalls and servers. Additionally, back end
`server( s) 420 may be provided between the service center 106 and the voice
`network 104.
`
`[052] Firewalls 402 and 404 provide security services for
`
`communications between service center 106, data network 102, and voice
`
`network 104, respectively. For example, firewalls 402 and 404 may restrict
`
`communications between user terminal 112 and one or more servers within
`service center 106. Any appropriate security policy may be implemented in
`firewalls 402 and 404 consistent with the principles of the present invention.
`
`Firewalls 402 and 404 may be implemented using a combination of known
`
`hardware and software, such as the Raptor Firewall provided by the Axent
`
`Corporation. Further, firewalls 402 and 404 may be implemented as separate
`machines within service center 106, or implemented on one or more
`machines external to service center 106,
`
`15
`
`Page 263 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 19 of 81
`
`WO 2004/049625
`
`PCT/ US2003/0J8JJ5
`
`[053] Network 418 may be any appropriate type of network, such as
`
`an Ethernet or FDDI network. Additionally, r,etwork 418 may also inch.1de
`
`switches and routers as appropriate without departing from the scope of the
`invention. Further, additional firewalls may be present ·;n network 418, for
`example, to place one or more of servers 406, 408, 410, or voice portal 412
`
`behind additional firewalls.
`[054] Each server (406, 408,410,414,416,420) may be any
`
`appropriate type of server o r compoter1 such as a Unix or DOS-based server
`or computer. The servers may implement various logical functions, such as
`
`those described below. In Figure 4, a different server is illustrated as being
`
`used for each logical function. In other embodiments, the logical functions
`
`may be split across multiple servers, multiple servers may be used to
`
`Implement a single function, all functions may be performed by a single
`
`server, etc.
`
`lh general, a digital companion server 406 may provide the
`[055]
`software and hardware for providing specific services of the service center.
`
`Exemplary services include, for example, permitting a customer to add
`contacts to their address book from a history of calls made or received by the
`
`customer, permitting a customer to make cafls directly 'from their address
`
`book, scheduling a call to be placed at a specific time, or permitting the
`
`customer to look at the name and/or address associated with a phone
`
`number. Additionally, these services may include permitting the customer to
`
`listen to their voice mail on-line, forwarding their calls based on a scheduler
`
`and/or the calling parties number, setting up conference calts on-line, real(cid:173)
`
`time call management, etc. In one embodiment, real-time call management
`
`enables a user to perform several functions as a call is being received, such
`
`as sending a call to voice mail, sending a call received on one device to
`
`another device, manually initiating protection from telemarketers, playing an
`
`announcement for the caller, scheduling a call back, bridging a caller onto a
`
`current call, etc.
`
`16
`
`Page 264 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 20 of 81
`
`WO 2004/049625
`
`PCT/US2003/038JJ5
`
`[056] A communication portal server 408 may provide the hardware
`
`and software for managing a customer'~ account and interfacing with
`
`customer account information stored by the provider of customer's voice
`
`network 104. The network access servers 410 may provide the hardware and
`
`software for sending and receiving information to the voice network 104 in
`
`processing the applications provided by the service center. For example, the
`
`network access servers 410 may be used for transmitting and/or receiving
`
`information from/to an ISCP 302 or an SSP 308 or 310 of the voice network
`
`104.
`
`[057] Voice portal 412 includes software and hardware for receiving
`
`and processing instructions from a customer via voice. For example, a
`
`customer may dial a specific number for voice portal 412. Then the customer
`using speech may instruct the service center 105 to modify the services to
`
`which the customer subscribes. Voice portal 412 may include, for example, a
`
`voice recognition function 416 and an application function 414. Voice
`
`recognition function 416 may receive and interpret dictation, or recognize
`
`spoken commands. Application function 414 may take, for example, the
`
`output from voice recognition function 416, convert it to a format suitable for
`service center 106 and forwarcl the information to one or more servers (406,
`408,410) in service center 106.
`
`[058) Fig. 5 illustrates a logical architecture of an exemplary system,
`
`consistent with the present invention. As illustrated, the logical architecture
`
`may be split into four planes: client side plane 502, application service plane
`
`504, network access plane 506, and voice network plane 508.
`
`[059] Client side plane 502 includes user terminals 112_A and 112_8
`
`that a user may use to send and/or receive information to/from the service
`
`center 106. Additionally, client side plane 502 includes the user's phone(s)
`
`114. As discussed above, user terminals 11 2 may be any type of device a
`
`user may use for communicating with service center 106. For example, user
`terminal 112_A may be a PDA running a program for communicating with
`service center 106, while user terminal 112_8 may be a desktop type
`
`17
`
`Page 265 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 21 of 81
`
`WO 2004/049625
`
`PCT/ US2003/038J35
`
`computer running a web browser for communicating with the service center
`
`106 via the Internet. Additionally, the user may have one or more phones
`
`114, such as, for example, one or more standard landline telephones and/or
`
`wireless phones.
`
`[060] Application service plane 504 includes digital companion
`
`server(s) 406, communication portal server(s) 408, and voice portal 412.
`
`These entities may communicate between one another using, for example,
`
`web services or any other suitable protocols. Web services are a
`
`standardized way of integrating Web-based applications using XML, Simple
`
`Object Access Protocol ("SOAP"), Web Services Description Language
`
`("WSDL") and Universal Description, Discovery and Integration ("UDDI") open
`
`standards over an Internet protocol backbone.
`[061) As illustrated, a digital companion server 406 may provide the
`
`following functions: a client proxy function 512, a web server function 514, an
`
`application server function 516, a calendar server function 518, a notification
`
`server function 520, and a database function 522. Each of these functions
`
`may be performed in hardware, software, and/or firmware. Further, these
`
`functions may each be executed by a separate server, split across multiple
`
`servers, included on the same server functions, or any other manner.
`
`[062) Client proxy function 512 provides a proxy function for the digital
`
`companion that may be used for security purposes. Client proxy function 512
`
`may be included in a separate server such that all communications sent from
`
`the other digital companion functions/servers to a user terminal 112 via data
`
`network 102 go through client proxy 512. Also, if client proxy 512 is included
`
`on a separate server, for example, an additional firewall may be provided
`
`between client proxy 512 and the other digital companion servers to provide
`
`additional security.
`
`[063J Web server function 514 provides functionality for receiving
`
`traffic over data network 102 from a customer. For example, web server
`
`function 514 may be a standard web server that a customer may access
`
`18
`
`Page 266 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 22 of 81
`
`WO 200-1/049625
`
`l'CT/US2003/03H 13:'i
`
`using a web browser program, such as Internet Explorer or Netscape
`
`Communicator.
`
`(064] Application server function 516 encompasses the general
`
`functions performed by digital companion server(s) 406. For example, these
`
`functions may include interfacing with the various other digital companion
`
`functions to perform specific services provided by the service center. These
`
`services may include, for example, interfacing with other function(s), software,
`
`and/or hardware to provide a customer with the capability of managing their
`
`calls online. Such services may include, for example, permitting a customer
`
`to add contacts to their address book from a history of calls made or received
`
`by the customer, permitting a customer to make calls directly from their
`
`address book, scheduling a call to be placed at a specific time, or permitting
`
`the customer to look at the name and/or address associated with a phone
`
`number. Additionally, these services may include permitting the customer to
`
`listen to their voice mail on-line, forwarding their calls based on a scheduler
`
`and/or the calling parties number, setting up conference calls on-line,
`
`enabling call management with user intervention in real-time, etc.
`
`(065] Additionally, application server function 516 may interface with
`
`one or more external devices, such as an external web server, for retrieving
`
`or sending information. For example, application server function 516 may
`
`interface with a voice network's data center 556 (e.g., verizon.com) to
`
`determine the services to which the customer subscribes (e.g., call waiting,
`
`call forwarding, voice mail, etc.).
`
`(066] Calendar server function 518 may provide the capability of
`
`scheduling events, logging when certain events occurred, triggering the
`
`application-functions to perform a function at a particular time, etc. In one
`
`aspect of the invention, calendar server function 518 generates and maintains
`
`a scheduling data structure, such as a user calendar that includes scheduling
`
`events (e.g., meetings, tasks, etc.), that are created by the user through user
`
`terminal 112_A. For example, a user may schedule a conference call event
`
`in a calendar application reflecting a time and date when the user is to
`
`19
`
`Page 267 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 23 of 81
`
`WO 2004/1)-llJ625
`
`PCT/US2003/0J81J:-
`
`participate in a conference call that is be established in accordance with
`
`certain aspects related to the present invention. Calendar server function 518
`
`may operate with, or leverage, application server function 516 to initiate
`
`conference call configuration processes consistent with aspects of the
`
`invention.
`
`[067] Notification server function 520 provides the capability to send
`information from the service center 106 to a user terminal 112. For example,
`the notification server function 520 at the direction of the application server
`
`function 516 may send a notification to the user terminal 112 that the user is
`
`presently receiving a phone call at the user's phone 114. This notification
`
`may be, for example, an instant message pop-up window that provides an
`
`identification of the cafler as well as the number being called. The notification
`
`may also have a number of user-selectable buttons or items associated with it
`
`that enable the user to manage a call in real-time.
`
`[068J Database function 522 provides the storage of information
`
`useable by the various applications executed by the digital companion
`servers. These databases may be included in, for example, one or more
`external storage devices connected to the digital companion servers.
`
`Alternatively, the databases may be included in storage devices within the
`
`digital companion servers themselves. The storage devices providing
`
`database function 522 may be any type of storage device, such as for
`
`example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
`
`[069] As discussed above, communication portal server(s) 408
`
`provide the hardware and software for managing a customer's account and
`
`interfacing with customer account information stored by the provider of
`
`customer's voice network 104. As illustrated in Figure 5, a communication
`
`portal server 408 may provide the following functions: a web server function
`526, an application server function 528, a contacts database function 530,
`
`and/or a customer profile function 532. Each of these functions may be
`performed by a separate server, split across multiple servers, included on the
`
`same server functions, or any other manner.
`
`20
`
`Page 268 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 24 of 81
`
`WO 200~/049625
`
`PCT/US2003/038135
`
`[070] Web server function 526, as with web server function 514 of the
`
`digital companion servers, provides functionality for receiving traffic over data
`
`network 102 from a customer. For example, the web server may be a
`
`standard web server that a customer may access using a web browser, such
`
`as Internet Explorer or Netscape Communicator.
`
`[071] Application server function 528 encompasses the general
`
`functions performed by communication portal servers 408. For example,
`
`these functions may include interfacing with the voice network to retrieve
`
`and/or modify customer profile information, and creating and editing an
`
`address book for the user. Additionally, application server function 528 may
`
`include the functionality of sending and/or receiving information to/from
`
`external servers and/or devices. For example, communication portal servers
`
`408 may be connected to a network, such as, the Internet. Application server
`
`function 528 may then provide connectivity over the Internet to ·external
`
`servers 552 that provide web services, such as the Superpages web page.
`
`Application server function 528 could then contact these external services
`
`552 to retrieve information, such as an address for a person in the user's
`
`address book.
`
`[072]
`
`In another example, application server function 528 of
`
`communication portal 408 may interface a Single Sign On ("SSO") server
`
`554. SSO 554 may be used to allow users to access all services to which the
`
`user subscribes, on the basis of a single authentication that is performed
`
`when they initially access the network.
`
`(073] Moreover, application server function 528, similar to application
`
`server 516, may provide functionality to facilitate services performed by the
`
`service center. These services may include, for example, interfacing with
`
`other function(s), software, and/or hardware to provide a customer with the
`
`capability of managing their calls online. For example, permitting a customer
`
`to add contacts to their address book from a history of calls made or received
`by the customer, permitting a customer to make calls directly from their
`address book, scheduling a call to be placed at a specific time, or permitting
`
`21
`
`Page 269 of 382
`
`
`
`Case 6:21-cv-00642-ADA Document 32-17 Filed 01/07/22 Page 25 of 81
`
`WO 200~/049625
`
`PCT/US2003/0381J5
`
`the customer to look at the name and/or address associated with a phone
`
`number. Additionally, these services may include permitting the customer to
`
`listen to their voice mail on-line, forwarding their calls based on a scheduler
`
`and/or the calling parties number, setting up conference calls on-line,
`
`enabling call