US007 187932B1
`
`(12)
`
`United States Patent
`Barchi
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 7,187,932 B1
`Mar. 6, 2007
`
`(54) AUTOPOPULATION OF ADDRESS BOOK
`ENTRIES
`(75) Inventor: Ron Barchi, Maple Valley, WA (US)
`(73) Assignee: Cingular Wireless II, LLC, Atlanta,
`GA (US)
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 619 days.
`
`(*) Notice:
`
`(21) Appl. No.: 10/346,497
`(22) Filed:
`Jan. 16, 2003
`
`(51) Int. Cl.
`(2006.01)
`H04O 7/20
`(52) U.S. Cl. ................... 455/445; 455/405; 455/414.1;
`455/425; 379/201.01: 379/213.01: 379/218.01
`(58) Field of Classification Search ...........r 455/414.1,
`455/415,445, 466,567, 425,405; 379/201.01,
`379,218.01, 355.04, 356.01, 355.02, 355.09
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`4,734.931 A * 3/1988 Bourg et al. ............. 379,93.01
`4,800,582 A *
`1/1989 D’Agosto et al. ..... 379,216.01
`5,034,976 A
`7, 1991 Sato ........................... 379,111
`5,204.894 A * 4, 1993 Darden ....
`... 379.88.03
`5,483,586 A *
`1/1996 Sussman ..
`... 379,218.01
`5,689,547 A * 11/1997 Molne ........................ 379,379
`5,943,611 A * 8, 1999 Molne ........................ 455,564
`6,005,927 A * 12/1999 Rahrer et al. ...
`379,142.01
`6,163,596 A * 12/2000 Gelfer et al. .............. 379 (67.1
`6,507,866 B1
`1/2003 Barchi
`6,539,238 B1* 3/2003 Brouns et al. .............. 455,558
`6,553,222 B 1 * 4/2003 Weiss ......................... 455,415
`
`6,738,462 B1* 5/2004 Brunson ................ 379,142.06
`6,804.338 B1 * 10/2004 Chen ..................... 379,142.08
`6,870,915 B2 * 3/2005 Stillman et al. ....... 379,201.01
`28393.2 A 358 f heal." 455,414
`aCl ( a.
`2003/01 10371 A1* 6/2003 Yang et al. ................. T13/100
`OTHER PUBLICATIONS
`“vOard: The Electronic Business Card,” http://www.imc.org/pdi/
`vcardwhite.html, 5 pages, visited Nov. 11, 2002.
`(Continued)
`Primary Examiner Binh K. Tieu
`(74) Attorney, Agent, or Firm—Klarduist Sparkman, LLP
`57
`ABSTRACT
`(57)
`that lated his
`t or compares a number of communications directed to a
`selected destination and based on a subscriber profile, deter
`mines if address or contact information associated with the
`destination is to be added to a personal address book or other
`contact database. Contact information can be obtained using
`a reverse phone number lookup in a white pages or yellow
`pages directory, or using an Internet-based search engine or
`database. The tabulator can be configured to access the
`Subscriber profile prior to initiating a communication, during
`a communication, or after completion of the communication.
`In one example, subscriber billing records are delivered to
`the tabulator for identification of destinations for which
`contact information is to be added to the personal address
`book. Additional or revised contact information can be
`stored in the personal address book automatically, or in
`response to a subscriber instruction delivered from a mobile
`station.
`
`23 Claims, 5 Drawing Sheets
`
`
`
`808
`
`ADDRESS BOOK
`UPDATES
`ON/OFF
`DEFAULT
`CUSTOMIZE
`
`806
`
`810
`
`800
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 1 of 12
`
`

`

`US 7,187,932 B1
`Page 2
`
`OTHER PUBLICATIONS
`s
`& 8
`vCard, The Electronic Business Card.” Version 2.1, 51 pages, Sep.
`18, 1996.
`“SyncML Device Information DTD, version 1.1.” 38 pages, Feb.
`15, 2002.
`
`“Building an Industry-Wide Mobile Data Synchronization Proto
`col.” Version 1.0, 14 pages, 2000.
`“SyncML Representation Protocol, Version 1.1.” 51 pages, Feb. 15.
`2002.
`* cited by examiner
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 2 of 12
`
`

`

`U.S. Patent
`
`Mar. 6, 2007
`
`Sheet 1 of 5
`
`US 7,187,932 B1
`
`
`
`
`
`
`
`
`
`
`
`112
`
`MSC
`
`BSC
`
`CONTACT.
`PROC
`
`12
`
`FIG 2
`
`06
`
`204 - 202 o
`
`108
`
`FIG. 1
`
`107
`
`[XXX
`
`228
`
`234
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 3 of 12
`
`

`

`U.S. Patent
`
`Mar. 6, 2007
`
`Sheet 2 of 5
`
`US 7,187,932 B1
`
`FIG. 3
`
`
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 4 of 12
`
`

`

`U.S. Patent
`
`Mar. 6, 2007
`
`Sheet 3 of 5
`
`US 7,187,932 B1
`
`INITIATE
`CALL
`
`602
`
`600
`
`FIG. 6
`
`SEND CALL
`INFO TO
`ANALYZER
`
`604
`
`607 NO
`
`
`
`
`
`STORE
`CONTACT
`DATA2
`
`09 YES
`
`
`
`
`
`YES
`
`608
`
`
`
`STORED
`PREVIOUSLY2
`
`NO
`
`6.13
`
`END
`
`612
`
`ADD DATA TO
`ADDRESS BOOK
`
`LOOKUP
`DATA
`
`610
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 5 of 12
`
`

`

`U.S. Patent
`
`Mar. 6, 2007
`
`Sheet 4 of 5
`
`US 7,187,932 B1
`
`STORE
`CONTACT
`DATA
`
`STORED
`PREVIOUSLY?
`
`ADD DATA TO
`ADDRESS BOOK
`
`
`
`OOO
`
`1021
`
`1022
`1024
`
`100
`
`1008
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 6 of 12
`
`

`

`U.S. Patent
`
`Mar. 6, 2007
`
`Sheet 5 of 5
`
`US 7,187,932 B1
`
`806
`
`810
`
`800
`
`FIG. 8
`
`808
`
`810
`
`807
`
`ADDRESS BOOK
`UPDATES
`ON/OFF
`DEFAULT
`CUSTOMIZE
`LOCAL
`
`
`
`USAGE DATA
`COLLECTOR
`
`902
`
`06
`
`912
`
`914
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 7 of 12
`
`

`

`1.
`AUTOPOPULATION OF ADDRESS BOOK
`ENTRIES
`
`FIELD OF THE INVENTION
`
`The disclosure pertains to methods of revising and popu
`lating address book entries.
`
`BACKGROUND
`
`10
`
`The development of cellular communication networks
`permits network Subscribers to make and receive calls, send
`and receive email messages and short message service
`messages, send and receive faxes, and perform other com
`munication tasks while at a fixed location or while mobile.
`15
`Thus, a Subscriber need not remain at a particular home or
`business address in order to remain accessible for personal
`or business communications. For example, a network Sub
`scriber can configure a mobile office so that the subscriber
`can send and receive typical business and personal commu
`nications, even while mobile. For example, a realtor can
`configure an automobile with a fax machine, a laptop
`computer, a personal digital assistant or handheld computer,
`and a cellular telephone or other mobile station. As a result,
`the realtor need not return to an office regularly, increasing
`her availability for client contact. Other subscribers can take
`advantage of mobile communications to remain in touch
`with friends and family, even while traveling.
`While mobile communication systems offer numerous
`advantages, management of necessary contact information
`can be difficult. Access to a stored customer/contact database
`is typically unavailable, so that obtaining contact data such
`as phone numbers and addresses is difficult. Methods and
`apparatus are needed that permit network Subscriber to
`access and revise contact data while mobile.
`
`25
`
`30
`
`35
`
`SUMMARY OF THE INVENTION
`
`Methods of populating a contact database comprise
`receiving a contact identifier associated with a communica
`tion with a contact. The contact identifier is analyzed and
`contact information associated with the contact identifier is
`selected for inclusion in the contact database based on the
`analysis. In additional examples, methods further comprise
`recording a tally count associated with the contact identifier,
`and analyzing the contact identifier based on the recorded
`tally count. In other examples, a contact data search asso
`ciated with the contact identifier is performed to obtain
`contact data records and the contact database is populated
`using the contact data records. In additional representative
`examples, the contact analysis is based on a predetermined
`set of contact identifiers for which contact data is excluded
`from the contact database. In further examples, the contact
`database is populated with the selected information if con
`tact data associated with the contact identifier is not included
`in the contact database. In other examples, an aging param
`eter is associated with contact data included in the contact
`database, and the contact database is updated with the
`selected information based on the aging parameter. In rep
`resentative examples, the contact identifier is a mobile
`station ISDN number, a phone number, and/or an email
`address.
`Methods of selecting data for a contact database include
`selecting a destination and initiating a communication to the
`selected destination. At least one usage indicator associated
`with the destination is analyzed and, based on the analysis,
`contact data associated with the identifier is selected for
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 7,187,932 B1
`
`2
`inclusion in a contact database. In additional examples,
`contact data associated with the identifier is gathered and
`included in the contact database based on the analysis. In
`other examples, the at least one usage indicator includes a
`tally count of a number of communications associated with
`the selected destination. In specific examples, the usage
`indicator is associated with a number of communications of
`a selected types directed to the selected destination.
`Communication networks comprise a usage analyzer con
`figured to receive usage indicators including a destination
`associated with a communication initiated by a network
`Subscriber and to select destinations based on the usage
`indicators. A contact data acquisition unit is in communica
`tion with the usage analyzer and is configured to obtain
`contact data for destinations selected by the usage analyzer.
`In other examples, a Subscriber profile database is config
`ured to deliver subscriber profile parameters to the usage
`analyzer, wherein the usage analyzer selects destinations
`based on the subscriber profile parameters. In representative
`examples, the Subscriber profile parameters include a tally
`count associated with a number of communications directed
`to a destination. In additional examples, a memory is con
`figured to store personal address book data and the usage
`indicator is configured to receive billing records and select
`destinations based on the billing records.
`Mobile stations comprise a user profile input configured
`to select at least one Subscriber profile parameter associated
`with an address book and a transceiver configured to com
`municate the at least one address book update parameter to
`Subscriber usage analyzer. In additional examples, the at
`least one address book update parameter is a destination
`tally parameter, and a memory is configured to store at least
`one address book update parameter. In other examples, the
`transceiver is configured to receive address book entries and
`store the address book entries a memory. In additional
`representative examples, the user profile input is configured
`to acknowledge population of an address book.
`These and other examples are described below with
`reference to the accompanying drawings.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a schematic diagram of a communication system
`that includes a contact processor and an address book.
`FIG. 2 is a schematic diagram of a communication system
`illustrating a method of updating a personal address book.
`FIG. 3 is a schematic diagram of a communication system
`illustrating a method of updating a personal address book
`based on communication of a short message service (SMS)
`message.
`FIG. 4 is a schematic diagram of a communication system
`illustrating a method of updating a personal address book
`based on communication of an email.
`FIG. 5 is a block diagram illustrating a method of adding
`or updating contact information to an address book or other
`database.
`FIG. 6 is a block diagram illustrating a method of adding
`or updating contact information to an address book or other
`database.
`FIG. 7 is a block diagram illustrating a method of adding
`or updating contact information to an address book or other
`database.
`FIG. 8 is a schematic diagram of a mobile station con
`figured to communicate with a network-based address book.
`FIG. 9 is a schematic block diagram of a contact process
`ing System.
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 8 of 12
`
`

`

`US 7,187,932 B1
`
`3
`FIG. 10 is a schematic diagram of a menu associated with
`a user interface for configuring a subscriber profile database
`associated with an address book.
`
`DETAILED DESCRIPTION
`
`10
`
`15
`
`25
`
`Methods and apparatus for revising, expanding, and
`updating contact information are described with reference to
`contact information stored in one or more address books.
`Address books can be configured to store a variety of user
`information such as contact names, phone numbers (includ
`ing home, business, and cell phone numbers), fax numbers,
`email addresses, home and business addresses, web pages.
`and other personal or business information.
`With reference to FIG. 1, a communication system
`includes a mobile station 102 that communicates with a
`mobile base station 104 and an antenna 105 over an air
`interface 106. The mobile base station 104 is in communi
`cation with a base station controller (BSC) 108 and a mobile
`switching center (MSC) 110. The BSC 108 is configured to
`communicate with additional base stations and antennas
`such as a mobile base station 109 and an antenna 107. A
`home location register (HLR) 112, a visitor location register
`(VLR) 114, and a contact processor 121 are in communi
`cation with the MSC 110. The HLR 112 provides storage for
`subscriber information such as subscriber MSISDNs and
`other permanent and temporary information associated with
`subscribers. The VLR 114 provides data storage for mobile
`stations that are in a service area associated with the MSC
`110, but that are not associated with subscribers to the
`30
`network serviced by the MSC 110. An equipment identity
`register (EIR) 118 and an authentication center (AuC) 120
`are also in communication with the MSC 110. The MSC 110
`is in communication with a public switched telephone
`network (PSTN) 122 that is in communication with one or
`more telephones such as a representative telephone 124 and
`other communication devices such as a fax machine 125.
`The MSC 110 can be configured to communicate directly
`with other remote or local networks or the Internet. Alter
`natively, communication with additional networks can be
`provided via the PSTN 122. The mobile base station 104 is
`shown in FIG. 1 as communicating with the mobile station
`102, but typically the mobile base station 104 is configured
`to communicate with one or more mobile stations such as
`cell phones, laptop computers, personal digital assistants,
`handheld computers, or other communication devices. In
`addition, the mobile station 102 can communicate with
`mobile stations associated with wireless networks that are in
`communication with the PSTN 122 or the MSC 110. The
`PSTN 122 is generally configured for communication with
`landline telephones such as the telephone 124 or other fixed
`devices such as the fax machine 125, desktop computers,
`servers, or other devices. In addition, the PSTN 122 permits
`communication with one or more additional networks such
`as a representative network 126, shown in FIG. 1 as the
`Internet.
`The contact processor 121 is configured to receive origi
`nation information, destination information, and/or message
`characterization information pertaining to a communication.
`For example, for a voice call from the mobile station 102 to
`another mobile station, the contact processor 121 can receive
`one or more identifiers such as originating and destination
`phone numbers or originating and destination equipment
`identifiers. The contact processor 121 can also receive a
`message indicator that identifies the message as a Voice
`message. In other examples, a message indicator can iden
`tify the message as a short message service message, a fax,
`
`50
`
`35
`
`40
`
`45
`
`55
`
`60
`
`65
`
`4
`an email, video, audio, or other message type. The contact
`processor 121 can also be situated at other locations in a
`communication network in association with the PSTN 122.
`the BSC 108, or at a mobile station 102. A contact database
`or address book 127 can be configured to receive identifiers
`from the contact processor 121 and can co-located with the
`contact processor 121, or the address book 127 and the
`contact processor 121 can be situated at different network
`locations. Location of the address book 127 in a wireless
`network facilitates access for mobile subscribers.
`With reference to FIG. 2, a wireless communication
`network includes a mobile switching center (MSC) 202 that
`is in communication with a base station controller (BSC)
`204, a home location register (HLR) 206 and a mobile
`station (MS) 208. The MS 208 originates a message 209 that
`is delivered to the MSC 202. The MSC 202 is configured to
`deliver a message 210 to an address tabulator 212 as well as
`delivering a message to a message destination. The message
`210 can include mobile station integrated services digital
`network numbers (MSISDNs) associated with a call source
`such as the MS 208 or a call destination. The message 210
`can include different or additional identifiers associated with
`a source or destination of a voice call, an email, a fax, or
`other communication.
`The address tabulator 212 directs a subscriber profile
`request 214 to a subscriber profile directory (SPD) 216 that
`is configured to store subscriber profile parameters for one
`or more network subscribers. The subscriber profile request
`214 typically includes a subscriber identity such as an
`originating MSISDN. The SPD 216 returns one or more
`selected subscriber profile parameters to the address tabu
`lator 212 in a profile return message 218. Based on the
`received profile parameters, the address tabulator 212 issues
`a destination lookup request 220 to a personal address book
`(PAB) 222 stored at a server 224. The server 224 returns a
`notification 226 that indicates if the destination MSISDN is
`included in the PAB 222, and in the example of FIG. 2, the
`notification indicates that the MSISDN is not stored in the
`PAB 222. The address tabulator 212 then issues a lookup
`request 228 to lookup system 232 that returns a destination
`data message 234 that includes, for example, one or more
`addresses, user names, and other information associated
`with the destination MSISDN. The information stored in the
`PAB 222 is then updated based on the returned destination
`data message 234.
`The SPD 216 can return one or more subscriber profile
`parameters to the address tabulator 212 in the profile return
`message 218, based on an SPD subscriber configuration that
`can be setup based on default values, or customized by or for
`an individual subscriber, or a subscribergroup. In addition,
`the SPD 216 can be configured so that only selected network
`subscribers are eligible to use the SPD 216. Eligibility can
`be determined by, for example, a user's subscription type or
`other subscriber or network configurations. Processing asso
`ciated with the PAB 222 can be performed prior to call
`completion, after call completion, or after call termination,
`or a combination thereof. Updates to the PAB 222 can be
`entered in the PAB 222 automatically or a request for user
`approval of changes to the PAB 222 can be issued based on,
`for example, subscriber profile parameters stored in the SPD
`216.
`Subscriber profile parameters can be associated with a
`number of calls or other communications to a destination
`associated with a single MSISDN. For example, a threshold
`tally count for a single destination can be set so that once this
`number of calls to the destination is reached, destination
`address information is added to the PAB222. The tally count
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 9 of 12
`
`

`

`US 7,187,932 B1
`
`10
`
`15
`
`5
`can be associated with a tally frequency so that the tally
`count threshold can be reached based on a number of
`contacts to a destination within a selected time period. In
`other examples, the PAB 222 can be updated based on, for
`example, time of call requests, or particular call destinations.
`For example, address or other information for destinations
`associated with a specified country code, area code, or local
`exchange code can be selected for inclusion or addition to
`the PAB 222. As a specific example, calls to phone numbers
`having a particular prefix associated with, for example, a
`selected business or other institution, can be identified so
`that contact and address information for Such numbers can
`be added to the PAB 222 after only one call request, or after
`a selected number of call requests that is less than a tally
`frequency threshold associated with other communication
`requests.
`The SPD 216 can be updated based on address, contact,
`or other information provided by the lookup system 232 that
`can be based on a reverse white pages/yellow pages lookup,
`obtained by a database query, obtained by one or more
`Internet-based searches or other search engines. Additional
`databases can also be selected. For example, industry spe
`cific databases can be queried, and maps, photographs,
`drawings, other information can be retrieved and stored for
`one or more communication destinations.
`With reference to FIG. 3, a communication system
`includes a portable digital assistant 302 or other mobile
`device configured to communicate with a wireless commu
`nication system that includes a mobile switching center 304
`and short message service center (SMSC) 306. A subscriber
`directs a message 308 from the PDA302 to the MSC 304,
`and the MSC 304 directs a request 310 to the SMSC 306 to
`deliver a short message service (SMS) message to a desti
`nation. In addition, the SMSC 306 transmits a message 312
`that includes address or contact databased on billing infor
`mation associated with PDA302, or the subscriber, or both
`to a number/address tabulator 314 at a server or other
`computer or processor. The tabulator 314 issues a request for
`subscriber profile information to a subscriber profile data
`base (SPD) 316 that responds by directing a profile message
`318 to the tabulator 314. Based on subscriber profile param
`eters and the billing information, address or contact data is
`selected for addition to, for example, a master personal
`address book (PAB) 320. The tabulator 314 directs a request
`319 to the server 321 to determine if the PAB 320 already
`contains contact information corresponding to the data
`selected for addition, and the server 321 returns a message
`322 that acknowledges if such data is stored. If such data is
`already stored, the stored data can be updated based on a
`subscriber parameter such as a refresh time. If the server 321
`confirms that data corresponding to the selected data is not
`stored or stored data is to be updated, then the tabulator 314
`sends a lookup request 326 to a server 328 that gathers
`contact data based on telephone or email directories, other
`directories, from the Internet, or otherwise collected. The
`contact data is communicated to the PAB 320 in a message
`330, and the PAB 320 is updated.
`With reference to FIG. 4, a communication system
`includes a personal digital assistant 402 configured to com
`municate with a mobile switching center (MSC) 403 of a
`60
`wireless communication network. The MSC 403 is in com
`munication with a short message service center (SMSC) 405
`and a short message peer-to-peer protocol processor (SMPP)
`406. The SMPP 406 can be configured as a dedicated
`processor or included at the SMSC 405 or other network
`location to permit communication of voice mail and email
`between different networks, particularly between wired net
`
`45
`
`6
`works and wireless networks. The SMPP 406 directs a
`message 413 to an email hub 407 that in turn directs a
`message 414 to an address analyzer 415. Based on the
`message 414, the address analyzer 415 issues a request 417
`to a subscriber profile database (SPD) 416 for parameters
`associated with address or contact updates. The SPD 416
`returns a message 418 and based on the message 418, directs
`a request 419 to a server 421 associated with a contact
`database 420. Depending on a message 422 returned by the
`server 421, a request 426 is delivered to a lookup server 428
`to gather contact information associated with a message
`destination. A return message 430 containing contact infor
`mation is delivered to the server 421 and the contact
`database 420 is updated.
`With reference to FIG. 5, a contact tabulator 514 directs
`a request 507 to an MMS 502 so that a communications
`summary 508 is returned to the contact tabulator 514. The
`communications summary 508 can be based on information
`concerning communication origination, destination, content,
`or other information based on, for example, subscriber
`billing records. The contact tabulator 514 and a subscriber
`profile database (SPD) 516 exchange messages 514, 518.
`and based on the SPD 516, the contact tabulator 514 requests
`data from a contact database 520 and receives requested data
`from the contact database 520 in messages 519, 522, respec
`tively. The contact tabulator 514 issues a request 526 for
`contact data, and the server 521 issues a request 529 for
`additional contact data to lookup server 528 that returns
`contact data in a message 530.
`With reference to FIG. 6, a method of populating an
`address book or other database includes a step 602 of
`initiating a communication such as a voice call, email, fax,
`or other communication to a selected destination. Informa
`tion concerning the communication Such as communication
`type, source, and destination are directed to a contact
`analyzer in step 604 and in a step 606 communication-based
`information Such as destination and type are analyzed to
`determine if contact information associated with the com
`munication or communication destination is to be stored. If
`contact information is not to be stored, the method ends in
`a step 607. Such a determination can be based on, for
`example, a comparison of a number of communications
`directed to the destination with respect to a threshold num
`ber Stored in a Subscriber profile. Using Such an approach,
`destinations that are frequently used can be identified for
`addition to the address book. In some cases, destination
`information is not stored. For example, destinations such as
`phone numbers, can be included in a “do not add” list, so that
`associated information is not retrieved. An “anti-spamming
`detector can also be provided so that such contacts are
`excluded. Contact information that is already included can
`be identified in a step 608, so that such information is not
`retrieved again, and the procedure ends in a step 609.
`Alternatively, such information can be updated based on a
`Subscriber profile parameter associated with contact aging,
`wherein contact data older than a predetermined time is
`selectively updated. Contact information is obtained in a
`step 610 using directories, the Internet, or other date sources,
`and the contact information is added to the address book in
`a step 612, and the method ends in a step 613.
`With reference to FIG. 7, another representative method
`of populating or updating a contact database includes initi
`ating an update request in a step 701. In a step 702,
`communication records such as billing records for a Sub
`scriber are obtained and delivered to a contact analyzer. In
`step 704, the contact analyzer identifies contact data Such as
`phone numbers, email addresses, or other destinations,
`
`25
`
`30
`
`35
`
`40
`
`50
`
`55
`
`65
`
`Google, Exhibit 1008
`IPR2022-00742
`Page 10 of 12
`
`

`

`US 7,187,932 B1
`
`5
`
`7
`groups of destinations, or message types or formats associ
`ated with particular destinations or groups of destinations. In
`a step 706, data storage is selected based on, for example,
`subscriber parameters stored in a subscriber profile database.
`If storage is not selected, the method ends in a step 707. In
`a step 708, selected data is screened to avoid overwriting of
`existing contact data and to eliminate contact data associated
`with “do not call' or “do not email destinations. If no data
`storage or data updates are selected, the method ends in a
`step 709. In a step 710, contact data is retrieved, and in a step
`712, contact data in an address book or other storage is
`updated. The method ends in a step 713.
`With reference to FIG. 8, a personal digital assistant
`(PDA) 802 or other mobile device is configured to commu
`15
`nicate with other mobile or fixed locations using a network
`based or other contact database or address book. The PDA
`802 includes a transceiver 805 and an antenna 806 config
`ured to communicate with a wireless network. A subscriber
`identity module (SIM) 807 includes a processor and memory
`configured to store one or more subscriber identifiers such
`as, for example, an international mobile Subscriber identity
`(IMSI) and/or an MSIDSN. The PDA 802 is configured to
`display an address book control menu 808 on a PDA display
`810. The menu 808 can include a display of menu items
`associated with, for example, autopopulation of contact
`information, manually controlled population of a contact
`database, entry and editing of Subscriber profile parameters
`associated with additions to and revisions of the contact
`database, and disabling address book population. A menu
`entry can also be associated with synchronizing a local copy
`of a personal address book with an address book stored on
`a network. A subscriber profile database can be stored in
`memory 810 at the PDA 802 and synchronized with a
`network copy so that address book entries can be updated
`without access to a particular network. Menu items are
`conveniently selecting using a user input 803 Such as one or
`more programmable or dedicated keys, a keypad, or a stylus
`that can be positioned at a selection region associated with
`a menu item to be selected.
`In some examples, an MSISDN serves as a communica
`tion source or destination identifier. Other identifiers can be
`used such as, for example, an international mobile Sub
`scriber identity (IMSI), an international mobile equipment
`identity (IMEI), email addresses, domain names, web
`addresses, PSTN telephone numbers, or other communica
`tion source or destination identifiers. In additional examples,
`contact data gathering can be executed and gathered data
`stored based on, for example, a common message recipient
`for emails, faxes, and other communications. A tally count
`can be based on communications to a recipient, even if the
`recipient is associated with several subscriber identifiers.
`For mobile users, the PAB and associated processing can
`be conveniently located in a wireless network so that the
`PAB is accessible. In other examples, PAB storage and PAB
`processing can be includes at a mobile station Such as a cell
`phone or a personal digital assistant. A representative con
`tact processing system 900 is illustrated in FIG. 9. A usage
`data collector 902 receives communication identifiers asso
`ciated with one or more communications, and delivers
`identification information to a usage analyzer 906. Based on
`a subscriber profile configuration (SPD) stored in a memory
`908, the analyzer issues a request for additional address
`book data to an address book data collector 912 that per
`forms database searches or other searches, or requests per
`formance of Such searches. Collected data can be screened
`or verified, and accepted address book data is stored in an
`
`25
`
`30
`
`35
`
`40
`
`45
`
`8
`address book memory 914. Components of the system 900
`can be situated at one or more network locations.
`A subscriber profile can be updated based on a menu that
`is used to select subscriber profile parameter fields for
`selecting a tally count, message types to be tallied, and other
`parameters. With reference to FIG. 10, a representative
`menu 1000 is configured for entry of subscriber profile
`parameters and control of selections associated with the
`update and population of a contact database. The menu 1000
`includes an options area 1001 that displays menu entries
`1002, 1003, 1004, 1005 that are associated with address
`book autopopulation, user approval of address book updates,
`downloading of an address book to, for example, a mobile
`station, and spam filtering respectively. Sources from which
`address book data is collected are selected using a source
`area 1008. A menu entry 1010 is associated with searching
`a complete set of address book sources. Alternatively, data
`Sources can be individually selected using menu entries
`1012, 1013, 1014, 1015. The menu 1000 can be displayed
`on, for example, a PDA, cell phone, a laptop computer, or
`other device, and menu entries can be selected using a
`keypad, keyboard, a mouse, a stylus, or other pointing
`device or input device. Menu entries can be accepted or
`rejected using menu areas 1020, 1022, respectively, and
`configuration of additional parameters is