throbber
a2) United States Patent
`US 6,754,665 Bl
`(10) Patent No.:
`Futagamiet al.
`(45) Date of Patent:
`Jun, 22, 2004
`
`
`US006754665B1
`
`(54)
`
`(75)
`
`INFORMATION PROCESSING APPARATUS,
`INFORMATION PROCESSING METHOD,
`AND STORAGE MEDIUM
`Inventors: Motomasa Futagami, Kanagawa (IP);
`Youji Kawamoto, Tokyo (JP);
`Hirofumi Kawamura, Kanagawa(JP),
`Motohiko Nagano, Tokyo (JP)
`
`.
`
`(73) Assignee: Sony Corporation, Tokyo (JP)
`
`6,138,149 A * 10/2000 Ohmura oo... eee 705/26
`
`..
`6,195,651 Bl *
`2/2001 Handel et al.
`3/2001 Ferrel et al. we. 707/515
`6,199,082 B1 *
`6,199,099 B1 *
`3/2001 Gershmanet al.
`.......... 345/966
`Eo
`0905-478 Bi “ S00 Steametal oe t00093
`
`6,269,369 Bl *
`7/2001 Robertson.......
`707/10
`6,317,718 BL * 11/2001 Fano vescccsssssssseesssseeeeee 705/1
`6/2002 Van Det Meer oo... 715/513
`6,405,224 B1 *
`
`6,477,563 B1 * 11/2002 Kawamuraetal.
`......... 709/202
`.. 707/102
`6,487,557 B1 * 11/2002 Nagatomo.........
`
`8/2001 Herz et al. we 705/14
`2001/0014868 Al *
`
`(*) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`US.C. 154(b) by 254 days.
`
`* cited by examiner
`
`(21) Appl. No.: 09/592,977
`
`(22)
`
`Filed:
`
`Jun. 13, 2000
`
`(30)
`Foreign Application Priority Data
`Jun. 24, 1999
`(IP) eee eeecccceeseeeseseeecnseeenees P11-177819
`Jun. 24, 1999
`(IP) eee eee ccc ceeseeeseseeecnseeenees P11-177820
`
`Tint, C07 eee ceccececeeeececeeeeeneeanens GO06F 17/30
`(SV)
`UWS. Ch.
`cocceccccecceccssccessstessstessnsessseiesneesseees 707/102
`(52)
`(58) Field of Search oo... ecteeeeeeereees 707/102
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`5191611 A *
`3/1993 Lang veces 705/53
`
`4/1996 Colgan vecccsscessseesseeeeee 705/12
`5,510,978 A *
`
`5/1998 Bisbee et al... 713/176
`5,748,738 A *
`9/1998 Felger oe. eee 379/114.14
`5,802,156 A *
`5,867,821 A *
`2/1999 Ballantyne et al.
`...... 345/970.1
`5,930,801 A *
`7/1999 Falkenhainer et al.
`.. 707/103 R
`6,006,227 A * 12/1999 Freemanetal. ............ 707/02
`
`4/2000 Sutcliffe et al. 345/751
`6,052,122 A *
`5/2000 Willner et al... 370/352
`6,064,666 A *
`....
`. 713/200
`6,119,229 A *
`9/2000 Martinez et al.
`
`............. 705/26
`6,134,548 A * 10/2000 Gottsmanet al.
`
`Primary Examiner—Wayne Amsbury
`(74) Attorney, Agent, or Firm—Sonnenschein, Nath &
`Rosenthal LLP
`
`(57)
`
`ABSTRACT
`
`A technique is disclosed which makesit possible to easily
`control access to personal information of a user. A manage-
`.
`:
`,
`ment server stores personal information such as a name,
`telephone number, address, and electronic mail address of
`each user. For example,if a user of a computer transmits a
`request command to the management server to transmit
`personal
`information of a user of a portable telephone
`device, the management server determines, in accordance
`with accessrestriction information, whetheror not providing
`of the personal
`information of the user of the portable
`telephone is restricted. If the providing of the personal
`information requested by the user of the computer is
`restricted, the managementserver inquires of the user of the
`portable telephone device, who is the ownerof the personal
`information, whether to give permission to provide the
`personal information. If permission is given, the manage-
`mentserver provides the personal informationto the user of
`the computer.
`
`23 Claims, 25 Drawing Sheets
`
` RETRIEVAL
`
`
`44
`
`
`
`LOG
`DATABASE
`
`COMMUNICATION
`CONTROLLER
`
`
`
`
`UPDATED INFORMATION
`
`SERVER UNIT
`NOTIFICATION UNIT
`
`
`
`
`
`PERSONAL
`
` INFORMATION
`
`
`DATABASE
`
`33
`
`
`
`
`
`TO NETWORK
`
`Google Exhibit 1030
`Google Exhibit 1030
`Google v. Mullen
`Google v. Mullen
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 1 of 25
`
`US 6,754,665 B1
`
`q1aVL
`
`ssayaqvssduddv
`
`181
`
`\——
`
`bgC|
`
`
`
`
`
`—a1aVLvik
`
`|“Old
`
`sSaHaav
`
`SSATAYIM
`
`MYOMLANct
`
`(Oe
`
`
`
` WHOMLANa71avLFEVLaANOHASTALoosueay\ssquacyONENd
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 2 of 25
`
`US 6,754,665 B1
`
`Ssaydqdqv
`
`(e41avl
`
`Sssaydqdqv
`
`YY
`
`
`ohanaJaviJleviGVgssayaav\ssayaav
`ElsNoHassl
`
`
`€2|
`=LL
`=r|/foC4oo
`
`SSI1SHIM
`
`ssayaay
`
`319V1vk
`
`YHOMLINcl
`
`¢Dl
`
`ang
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 3 of 25
`
`US 6,754,665 B1
`
`FIG. 3
`
`21
`
`TERMINAL UNIT
`
`COMMUNICATION
`CONTROLLER
`
`1
`
`TO NETWORK
`
`ADDRESS TABLE
`
`MEMORY
`
`23
`
`NY
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 4 of 25
`
`US 6,754,665 B1
`
`FIG. 4
`
`PERSONAL INFORMATION
`REGISTRATION PROCESS
`
`ACCESS A SERVER
`
`o1
`
`DISPLAY A PERSONAL INFORMA-|S2
`TION INPUT SCREEN
`
`IS A TRANSMISSION
`COMMNAD INPUT?
`
`WM oo
`
`TRANSMIT PERSONAL|S4
`INFORMATION
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 5 of 25
`
`US 6,754,665 B1
`
`FIG. 5
`
`PERSONAL INFORMATION
`ACQUISITION PROCESS
`
`TRANSMIT A KEYWORD|911
`TO A SERV
`mi D
`
`i
`
`IS PERSONAL
`
`INFORMATION RECEIVED?
`
`S12
`
`UPDATE AN ADDRESS
`es m
`TAB
`
`|913
`
`END
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 6 of 25
`
`US 6,754,665 B1
`
`FIG. 6
`
`32
`
`31
`
`SERVER UNIT
`
`COMMUNICATION
`|}<—> CONTROLLER
`
`TO NETWORK
`
`
`
`PERSONAL
`INFORMATION
`DATABASE
`
`
`
`33
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 7 of 25
`
`US 6,754,665 B1
`
`FIG. 7
`
`DATABASE REGISTRATION
`PROCESS
`
`
`
`
`
`TRANSMIT A PERSONAL INFORMA-
`TION INPUT SCREEN DATA
`
`IS PERSONAL
`
`INFORMATION RECEIVED?
`
`Y
`
`$22
`
`
`
`
`
`Ay,
`
`
`INPUT THE PERSONAL INFORMA-
`TION INTO THE DATABASE
`
`
`
`FIG. 8
`
`S21
`
`523
`
`
`
`
`
`PERSONAL INFORMATION
`
`PROVIDING PROCESS RETRIEVE PERSONAL INFORMA-
`TION USING A KEYWORD
`
`
`931
`
`TRANSMIT PERSONAL INFORMATION|932
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 8 of 25
`
`US 6,754,665 B1
`
`ee
`
`NOILLVWHOSNI
`
`IWNOS&Ad
`
`ASVavLVd
`
`MYOMLANOL
`NOLLVOINNNWOO
`YATIOULNOO
`<—>LINNYsdAuss
`
`NOILVWHOANIGAaLlVvddA
`INANOILVOISILON
`
`| €
`
`6Sls
`
`LV
`
`IWAdIdLad
`
`ASVaVLVd
`
`501
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 9 of 25
`
`US 6,754,665 B1
`
`FIG. 10
`
`UPDATED INFORMATION
`
`NOTIFICATION PROCESS
`
`
`RETRIEVE A USER WHO HAS
`RETRIEVED UPDATED PERSONAL
`INFORMATION
`
`
`
`TRANSMIT THE UPDATED PERSONAL
`INFORMATION TO THE USER
`
`
`
`
`
`S41
`
`$42
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 10 of 25
`
`US 6,754,665 B1
`
`COMPUTER 1
`(USER A)
`
`MANAGEMENT
`SERVER 6
`
`COMPUTER 4
`(USER B)
`
`(P1) REQUEST FOR RETRIEVAL
`
`THE USER
`
`(P3) PRODUCE A RETRIEVAL
`
`
`LOG IN TERMS OF THEC)
`(P4) TRANSMIT PERSONAL
`
`RETRIEVAL OF USER A
`
`
`INFORMATION
`
`
`OF PERSONAL INFORMATION (P2) AUTHENTICATE ()
`
` (P5)REQUEST FOR UPDATING
` (P6) UPDATE THE PERSONAL (C)
`
`
`
`
`
`
`PERSONAL INFORMATION
`
`INFORMATION
`
`(P7) CHECK THE
`RETRIEVAL LOG ©
`
`
`(IN TERMS OF
`(P8) TRANSMIT PERSONAL
`USER A)
`
`
`INFORMATION
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 11 of 25
`
`US 6,754,665 B1
`
`clOld
`
`LS
`
`Le
`
`|501
`
`TWASIML3Y
`
`3ASVavLvd
`
`MHOMLANOLNOLLVIINNWNOD
`
`YATIOWLNOO
`
`<—>LINNIWNIWYSAL
`LINNSNIMOSHO
`
`dlvddn
`
`
`
`AYOWAWJ1avl
`
`sSayddaqv
`
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 12 of 25
`
`US 6,754,665 B1
`
`UPDATE CHECKING
`PROCESS
`
`ACCESS A SERVER
`
`|S91
`
`ISSUE A REQUEST FOR CHECKING|S52
`WHETHER PERSONAL INFORMA-
`TION HAS BEEN UPDATED
`
`
`
`N/IS UPDATED PERSONAL S58
`
`INFORMATION RECEIVED?
`
`
`UPDATE PERSONAL INFORMATION|904
`IN THE ADDRESS TABLE
`
`
`END
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 13 of 25
`
`US 6,754,665 B1
`
`COMPUTER 1
`(USER A)
`
`MANAGEMENT
`SERVER 6
`
`COMPUTER 4
`(USER B)
`
`(P11) ISSUE A REQUEST FOR
`RETRIEVING INFORMATION
`
`(P12) AUTHENTICATE()
`THE USER
`
`(P13) TRANSMIT PERSONAL
`INFORMATION
`
`(P14) PRODUCE A RETRIEVAL OC
`LOG ASSOCIATED WITH
`
`(P15)PERFORM POLLING IN
`ACCORDANCE WITH THE
`RETRIEVAL LOG
`
`(P22) POLLING RESPONSE: YES
`
`(P16) CHECK PERSONAL 7)
`INFORMATION
`
`(P18)
`ISSUE A REQUEST FOR
`UPDATING THE PERSONAL
`INFORMATION ASSOCIATED
`WITH USER A
`(P19) UPDATE THE
`PERSONAL INFOR- ©
`MATION ASSOCIATED]
`WITH USER A
`
`(P21) CHECK PERSONAL ()
`INFORMATION
`
`(P17) POLLING RESPONSE: NO
`
`(P20) PERFORM POLLING IN
`ACCORDANCE WITH
`THE RETRIEVAL LOG
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 14 of 25
`
`US 6,754,665 B1
`
`FIG. 15
`
`DATA B-
`
`DATA C
`
`USER C
`
`OWNER
`INFORMATION :
`USER A
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`ALL
`
`INFORMATION :
`USER A
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`USER A
`
`INFORMATION :
`USER B
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`USER A
`USER B
`
`OWNER
`INFORMATION :
`USER C
`USER D
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`USER A
`USER C
`USER D
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 15 of 25
`
`US 6,754,665 B1
`
`FIG.
`
`16
`
`USER A
`
`USER B
`
`USER ©
`
`USER D
`
`OWNER
`INFORMATION :
`DATA C
`
`OWNER
`INFORMATION :
`DATA D
`
`OWNER
`INFORMATION :
`DATA D
`
`DATA D
`
`OWNER
`INFORMATION :
`DATA A
`DATA B
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`DATA A
`DATA B
`DATA C
`DATA D
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`DATA A
`DATA C
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`DATA C
`
`ACCESS
`ALLOWANCE
`INFORMATION :
`DATA D
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 16 of 25
`
`US 6,754,665 B1
`
`FIG. 17
`
`PERSONAL INFORMATION
`PROVIDING PROCESS
`
`
`
`
`
`
`
`RETRIEVE PERSONAL INFORMATION|961
`
`USING A KEYWORD
`
`
`
`
`
`
`
` S66
`
`
`Y
`S68
`
`
`
`
`
`CHANGE THE ACCESS RESTRIC-
`TRANSMIT A MESSAGE
`TO TELL THAT THE
`
`TION INFORMATION
`
`REQUEST IS REFUSED
`
`TRANSMIT PERSONAL INFORMATION
`
`IS ACCESS ALLOWED?
`
` 563
`TRANSMIT A MESSAGE TO TELL
`THAT ACCESS TO THE PERSONAL
`INFORMATION IS NOT ALLOWED
`
`$64
`
`IS THERE A REQUEST FOR CHANG
`ING THE ACCESS RESTRICTION?
`
`Y
`
`
`TRANSMIT A REQUEST TO THE
`
`OWNER TO CHANGE THE ACCESS
`
`RESTRICTION INFORMATION
`
`
`IS THE REQUEST ACCEPTED?
`
`N
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 17 of 25
`
`US 6,754,665 B1
`
`USER
`REQUESTING
`S
`
`MANAGEMENT
`SERVER 6
`
`OWNER OF
`PERSONAL
`INFORMATION
`
`(P33) AUTHENTICATION
`
`(P32)
`C) PERFORM USER
`
`PROCESS
`
`(P31)REQUEST THE SERVER
`TO AUTHENTICATE THE
`USER
`
`AUTHENTICATION
`
`
`suepeouesr|EAGT ETRE
`PERSONAL
`C)
`WITH A KEYWORD
`INFORMATION
`
`(P36) TRANSMITPERSONAL
`
`(P35)
`(>) DETERMINATION AS
`TO ALLOWANCE OF
`ACCESS: ALLOWED
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 18 of 25
`
`US 6,754,665 B1
`
`USER
`REQUESTING
`ACCESS
`
`MANAGEMENT
`SERVER 6
`
`OWNER OF
`PERSONAL
`INFORMATION
`
`(P41)REQUEST THE SERVER
`TO AUTHENTICATE THE
`USER
`
`(P43) AUTHENTICATION
`
`AUTHENTICATION
`PROCESS
`
`(INPUT BY THE USER) (P42) PERFORM USER
`
`DETERMINATION AS TO
`WHETHER TO ISSUE A
`REQUEST FOR CHANGING
`THE ACCESS RESTRIC-
`TION : NO
`
`(P44) TRANSMIT A RETRIEVAL
`REQUEST TOGETHER
`WITH A KEYWORD
`
`(P46) TRANSMIT THE RESULT
`OF DETERMINATION AS
`TO ALLOWANCE OF
`ACCESS
`
`(P45) DETERMINATION
`AS TO ALLOWANCE OF
`ACCESS : NOT ALLOWED
`
`

`

`U.S. Patent
`
`Jun. 22, 2004
`
`Sheet 19 of 25
`
`US 6,754,665 Bl
`
`USER
`REQUESTING
`ACCESS
`
`MANAGEMENT
`SERVER 6
`
`OWNER OF
`PERSONAL
`INFORMATION
`
`(P51)REQUEST THE SERVER
`TO AUTHENTICATE THE
`USER
`
`(P53) AUTHENTICATION
`
`(P52)
`e PERFORM USER
`AUTHENTICATION
`PROCESS
`
`(P54) TRANSMIT A RETRIEVAL
`REQUEST TOGETHER
`WITH A KEYWORD
`
`(P56) TOASTAMESSAGE
`
`ACCESS IS REFUSED
`
`PERSONAL INFORMATION
`
`(P55)
`A DETERMINATION AS TO
`ACCESS : NOT ALLOWED
`
`ALLOWANCE OF
`
`DETERMINATION
`AS TO WHETHER TO
`ISSUE A REQUEST
`FOR CHANGING
`THE ACCESS
`(P57) TRANSMIT A REQUEST
`RESTRICTION : YES
`FOR CHANGING THE
`(INPUT BY THE USER)
`ACCESS RESTRICTION|(psa)
`ACQUIRE INFORMATION
`C) AS TO THE OWNER OF
`PERSONAL INFORMATION
`(P59)
`TRANSMIT A REQUEST
`FOR CHANGING THE
`ACCESS RESTRICTION
`
`(P60)
`TRANSMIT A MESSAGE
`TO TELL THAT THE
`REQUEST HAS BEEN
`ACCEPTED
`(P62)
`(P61)
`TRANSMIT THE
`PERSONAL INFORMATION‘ACQUIRE THE
`PERSONAL INFORMATION
`Cy (P63)
`UPDATE INFORMATION
`AS TO RESTRICTION
`OF ACCESS TO THE
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 20 of 25
`
`US 6,754,665 B1
`
`USER
`REQUESTING
`ACCESS
`
`MANAGEMENT
`SERVER 6
`
`OWNER OF
`PERSONAL
`INFORMATION
`
`(P51)REQUEST THE SERVER
`TO AUTHENTICATE THE
`USER
`
`(P53) AUTHENTICATION
`
`(P52)
`(y PERFORM USER
`AUTHENTICATION
`PROCESS
`
`(P54)TRANSMIT A RETRIEVAL
`REQUEST TOGETHER
`WITH A KEYWORD
`
`(P55)
`DETERMINATION AS TO
`() ALLOWANCE OF
`(P56) TRANSMIT A MESSAGEYAccess: NOT ALLOWED
`TO TELL THAT THE
`ACCESS IS REFUSED
`
`PERSONAL INFORMATION (P61)
`
`(P60)
`TRANSMIT A MESSAGE
`TO TELL THAT THE
`REQUEST HAS BEEN
`ACCEPTED
`
`DETERMINATION
`AS TO WHETHER TO
`ISSUE A REQUEST
`FOR CHANGING
`THE ACCESS
`RESTRICTION: YES
`(INPUT BY THE USER)
`
`(P57) TRANSMIT A REQUEST
`FOR CHANGING THE
`ACCESS RESTRICTION
`
`(P58)
`ACQUIRE INFORMATION
`OAS TO THE OWNER OF
`PERSONAL INFORMATION
`
`(P59)
`TRANSMIT A REQUEST
`FOR CHANGING THE
`ACCESS RESTRICTION
`
`(P62)
`TRANSMIT THE
`
`O ACQUIRE THE
`PERSONAL INFORMATION
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 21 of 25
`
`US 6,754,665 B1
`
`AWYNY¥ASNGIAYALSIOAY
`
`
`
`NOIWHILSISSYYASN
`
`
`
`SAWVNLSV1GNVLSdls
`
`NOILVWHOSNI
`
`J1avlSSayddv
`
`co(Old
`
`
`
`ANOHd31SL3A18VLYdOd
`
`YAagWnN
`
`YSaANn
`
`
`
`YAEWANYADVd
`
`
`
`SSSydavIIVW-s
`
`
`
`ATINISOVAAWOH
`
`Y>AagWNAN
`
`4d09diZAWOH
`
`
`
`SSaY¥qdvSWOH
`
`
`
`AWVNANVdNOOd
`
`
`
`ANOHd31dLANVdNOD
`
`YAaWAN
`
`
`
`STINISOVAANVdWOO
`
`Y>AaWNAN
`
`NOILVWHYOSNI
`
`dqalvddn
`XO@ADVSSAW
`
`NOILVOISILON
`NOILVAYOSNI
`NOILVOILNSHLAV
`
`NOILVWHOSNI
`
`¥3asn
`
`ANOHd31dLAWOH
`
`
`NOILOIHLSAYSSAIQOV
`
`NOILVWYOSNI
`
`X08TIVW
`
`
`
`NOILVWHOANITVNINYSL
`
`isi
`
`VIGSW
`
`
`
`SSSYddVANVdNOOD
`
`
`
`NOILVWHOSNISSAOOV
`
`TVNIWYSAL
`
`
`AWVNNOILOAS
`NOILVDINNNWODJOSAdAL
`
`NOILVOINNWNOOD
`
`NOILVAYOSNIJTEVIIWAY
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 22 of 25
`
`US 6,754,665 B1
`
`FIG. 23
`
`
`
`REGISTERED USER NAME: USER A, USER B
`
`ACCESS RESTRICTION
`INFORMATION
`
`
`
`FIRST AND LAST NAMES : USER A, USER B
`
`HOME TELEPHONE
`NUMBER
`: USER A, USER B
`
`PORTABLE TELEPHONE
`NUMBER
`: USER A, USER B
`
`PAGER NUMBER : USER A, USER B
`
`E-MAIL ADDRESS : USER A, USER B
`
`HOME FACSIMILE
`NUMBER
`
`: NOBODY
`
`HOME ZIP CODE : NOBODY
`
`HOME ADDRESS : NOBODY
`
`COMPANY NAME : USER A
`
`COMPANY TELEPHONE
`NUMBER
`: USER A
`
`COMPANY FACSIMILE
`NUMBER
`: USER
`
`SECTION NAME
`
`:USER A
`
`COMPANY ADDRESS : USER A
`
`NOTES
`
`: NOBODY
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`COMMUNICATION TERMINAL
`INFORMATION LIST
`:USER A, USER B
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 23 of 25
`
`US 6,754,665 B1
`
`FIG. 24
`
`REGISTERED USER NAME: USER A, USER B
`
`FIRST AND LAST NAMES
`HOME TELEPHONE
`NUMBER
`: USER A, USER B
`
`: USER A, USER B
`
`PORTABLE TELEPHONE
`NUMBER
`: USER A, USER B
`PAGER NUMBER : USER A, USER B
`
`E-MAIL ADDRESS : USER A, USER B
`
`HOME FACSIMILE
`NUMBER
`
`: NOBODY
`
`HOME ZIP CODE : NOBODY
`
`HOME ADDRESS_: NOBODY
`
`COMPANY NAME : USER A
`
`COMPANY TELEPHONE
`NUMBER
`: USER A
`
`COMPANY FACSIMILE
`NUMBER
`USER A
`
`SECTION NAME
`
`:USER A
`
`COMPANY ADDRESS : USER A
`
`NOTES
`
`: NOBODY
`
`
` UPDATED
`INFORMATION
`
`
`NOTIFICATION
`
`INFORMATION
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`COMMUNICATION TERMINAL
`INFORMATION LIST
`:USER A, USER B
`
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 24 of 25
`
`US 6,754,665 B1
`
`FIG. 25A
`
`
`
`FIG. 25B
`
`111
`
`112
`
`113
`
`114
`
`116
`
`115
`
`FIG. 25C
`
`
`
`

`

`U.S. Patent
`
`Jun.22, 2004
`
`Sheet 25 of 25
`
`US 6,754,665 B1
`
`FIG. 26
`
`142
`
`143
`
`144
`
`102
`
`CPU|ROM|RAM HARD DISK 141
`
`_ |
`|
`|
`
`INPUT / OUTPUT INTERFACE
`
`145
`
`DISPLAY
`
`INPUT
`
`COMMUNICATION
`
`146
`
`147
`
`148
`
`149
`
`,
`
`101
`
`

`

`US 6,754,665 B1
`
`1
`
`INFORMATION PROCESSING APPARATUS,
`INFORMATION PROCESSING METHOD,
`AND STORAGE MEDIUM
`
`BACKGROUND OF THE INVENTION
`
`1. Field of the Invention
`
`The present invention relates to an information processing
`apparatus, an information processing method, and a storage
`medium, and moreparticularly, to an information processing
`apparatus, an information processing method, and a storage
`medium, which allow personal information ofa user, such as
`a name, address,
`telephone number, and electronic mail
`address, to be recorded in an address table or the like and
`which also makeit possible to easily control the access of
`another user to the personal information.
`2. Description of the Related Art
`A recent reduction in cost of information communication
`devices allows many users to record and mange personal
`information on an information communication device such
`
`as a portable telephone device, a computer, or a PDA
`(Personal Digital (Data) Assistant), wherein the personal
`information may include names, addresses,
`telephone
`numbers, and electronic mail addresses of users themselves
`and/or friends or acquaintances.
`FIG. 1 illustrates an example of a communication system
`including such information communication devices.
`In FIG. 1, computers 1 and 2 are connected to an in-house
`LAN (local area network) 12 in a certain company. The LAN
`12 is connected to the Internet 11. Computers 3 and 4 are
`connected to an ISP (Internet service provider) 14 via a
`public telephone network 13 so that they can access the
`Internet 11. A portable telephone device 5 can access the
`Internet 11 via a portable telephone wireless network
`(including base stations and the like) 15.
`The Internet 11 provides various services including an
`electronic mail (E-mail) service, whereby users of the com-
`puters 1 to 4 or the portable telephone device 5 can send an
`electronic mail to each other via the Internet 11.
`
`An application program for sending/receiving electronic
`mails is generally called a mailer. In general, the mailer has
`a table, called an address table, for managing personal
`information. The address table is used by a user to record
`personal
`information such as names and electronic mail
`addresses of other users.
`
`‘The recording of personal information into address tables
`hasto be performed by respective users themselves. This job
`is troublesome for users.
`
`Although the mailer has the capability of extracting the
`electronic mail addressof the senderof a received electronic
`mail and recording the extracted electronic mail address in
`the address table, the other items of personal information
`such as a telephone number or a company namehaveto be
`input by a user.
`Telephone devices such as a portable telephone device 5
`has the capability of recording telephone numbers of other
`users into an address table by using the telephone number
`notification service provided by the ISDN (Integrated Ser-
`vice Digital Network). However, even in this case, other
`items of personal
`information have to be input by the
`respective users of the telephone devices.
`SUMMARYOF THE INVENTION
`
`Thus, the object of the present invention is to solve the
`problems described above.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`According to an aspect of the present invention, there is
`provided an information processing apparatus which
`acquires personal information from an information provid-
`ing apparatus serving to provide personal information of a
`user, by means of transmitting a keyword used to retrieve
`personal information to the information providing appara-
`tus;
`requesting the information providing apparatus to
`retrieve personal information using the keyword; receiving
`personal information correspondingto the keyword from the
`information providing apparatus; and recording the personal
`information received from the information providing appa-
`ratus.
`
`According to another aspect of the present invention,
`there is provided an information processing apparatus which
`provides personal information of a user in response to a
`request issued by a client terminal in such a manner that
`whenpersonal information described in a personal informa-
`tion database is updated, information as to updating of the
`personal information is provided to a client terminal which
`hasissued, in the past, a requestforretrieval of that personal
`information.
`
`Accordingto still another aspect of the present invention,
`there is provided an information processing apparatus which
`provides personal information of a user in response to a
`request issued by a client terminal, by meansof receiving a
`request for personal information from the client terminal;
`determining whether providing of personal
`information
`requested by the client terminal is permitted or restricted, on
`the basis of permission/restriction information representing
`whether providing of the personal information is permitted
`or restricted; when the client terminal issues a request for
`personal information,if the providing of the personal infor-
`mation is not permitted or is restricted, inquiring of the
`ownerof the personal information whether or not to give
`permission as to the providing of the personal information;
`and providing personal information to the client terminal
`when the owner of the personal information gives permis-
`sion to provide the personal information.
`Accordingto still another aspect of the present invention,
`there is provided an information processing apparatus which
`acquires personal information of a user from an information
`providing apparatus serving to provide personal information
`of a user, by means of performing inquiry in such a manner
`that when a request is issued to the information providing
`apparatus to provide the personal information, if the pro-
`viding of the personal information is not permitted or is
`restricted, a request is issued to the information providing
`means to inquire of the owner of the personal information
`whetheror not to give permission as to the providing of said
`personal information.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a schematic diagram illustrating an example of
`a conventional communication system;
`FIG. 2 is a schematic diagram illustrating the configura-
`tion of a communication system according to an embodi-
`ment of the present invention;
`FIG. 3 is a block diagram illustrating an example of a
`functional configuration of a computer;
`FIG. 4 is a flow chart illustrating a personal information
`registration process;
`FIG. 5 is a flow chart illustrating a personal information
`acquisition process;
`FIG. 6 is a block diagram illustrating an example of a
`functional configuration of a managementserver;
`
`

`

`US 6,754,665 B1
`
`3
`FIG. 7 is a flow chart illustrating a database registration
`process;
`FIG. 8 is a flow chart illustrating a personal information
`providing process;
`FIG. 9 is a block diagram illustrating another example of
`a functional configuration of a managementserver;
`FIG. 10 is a flow chart illustrating an update notification
`process;
`FIG. 11 is a schematic diagram illustrating a communi-
`cation process between the management server and com-
`puters;
`FIG. 12 is a block diagram illustrating another example of
`a functional configuration of a computer;
`FIG. 13 is a flow chart illustrating an update checking
`process;
`FIG. 14 is a schematic diagram illustrating a communi-
`cation process between the management server and com-
`puters;
`FIG. 15 is a schematic diagram illustrating access restric-
`tion information;
`FIG. 16 is a schematic diagram illustrating access restric-
`tion information;
`FIG. 17 is a flow chart illustrating a personal information
`providing process;
`FIG. 18 is a schematic diagram illustrating a communi-
`cation process between the management server and an
`access requester and an owner of personal information;
`FIG. 19 is a schematic diagram illustrating a communi-
`cation process between the management server and an
`access requester and an ownerof personal information;
`FIG. 20 is a schematic diagram illustrating a communi-
`cation process between the management server and an
`access requester and an owner of personal information;
`FIG. 21 is a schematic diagram illustrating a communi-
`cation process between the management server and an
`access requester and an ownerof personal information;
`FIG. 22A is a schematic diagram illustrating the format of
`personal information described in a personal information
`database stored in the management server, FIG. 22B illus-
`trates the contents of personal information, FIG. 22C illus-
`trates the contents of an address table, FIG. 22D illustrates
`the contents of user registration information, and FIG. 22E
`illustrates the contents of a communication terminal infor-
`mationlist;
`FIG. 23 is a schematic diagram illustrating the details of
`access restriction information;
`FIG, 24 is a schematic diagram illustrating the details of
`update notification information;
`FIG. 25A is a schematic diagram illustrating the appear-
`ance of a computer in which a program for executing a
`process according to the present inventionis installed, FIG.
`25B is a schematic diagram illustrating various storage
`media for storing a program used to execute a process
`according to the present
`invention, and FIG. 25C is a
`schematic diagram illustrating a process for supplying a
`program used to execute a process according to the present
`invention; and
`FIG. 26 is a block diagram illustrating an example of a
`configuration of a computer for executing a process accord-
`ing to the present invention.
`DESCRIPTION OF THE PREFERRED
`EMBODIMENTS
`
`FIG. 2 illustrates the configuration of a communication
`system according to an embodimentof the present inven-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`tion. In FIG. 2, similar parts to those in FIG. 1 are denoted
`by similar reference numerals and they are not described in
`further detail, unless required. The communication system
`shownin FIG. 2 is basically similar to that shown in FIG. 1
`except
`that
`it further includes a management server 6
`connected to the Internet 11.
`
`The management server 6 (information providing
`apparatus) manages personal information of all users of
`computers 1-4, portable telephone device 5, and other client
`terminals which are not shown in FIG. 2, in termsof, for
`example, names,
`telephone numbers, addresses, dates of
`birth, and electronic mail addresses.
`If the managementserver 6 receives personal information
`from any user of the computers 1-4 orthe portable telephone
`device 5,
`the management server 6 enters the received
`personal information into a database. On the other hand,if
`personal information of a certain user is requested by any of
`the computers 1-4 or the portable telephone device 5, the
`managementserver 6 provides the requested personal infor-
`mation to the device which has issued the request.
`In the communication system constructed in the above-
`described manner, users of the computers 1 and 2 register
`their personal information into the managementserver 6 by
`accessing the managementserver6 on the Internet 11 via the
`in-house LAN 12. Similarly, users of the computers 3 and 4
`register their personal information by accessing the man-
`agement server 6 via the public telephone network 14 and
`the ISP 13, and the user of the portable telephone device 5
`registers his/her personal information by accessing the man-
`agement server 6 via the wireless network 15.
`When, thereafter, the user of the computer 1 wants to
`register the personal information of the user of the personal
`telephone device 5 into the address table on the computer1,
`the user of the computer 1 sends the nameorthelike of the
`user of the portable telephone device 5, as a keyword for
`retrieval of personal information, to the management server
`6 from the computer 1. In response, the managementserver
`6 retrieves personal
`information (for example, personal
`information containing the keyword) which matches the
`keyword received from the computer 1, and sends the
`retrieved personal information to the computer 1. If the
`computer 1 receives the personal information sent from the
`managementserver 6, the computer 1 records the received
`personal information into the address table.
`Thus, the user of the computer 1 can have the personal
`information of the user of the portable telephone device 5
`recorded in the address table without having to input the
`personal information via the keyboard orthe like.
`FIG. 3 illustrates an example of a functional configuration
`of the computer 1 shown in FIG. 2.
`The computer 1 comprises a communication controller
`21, a terminal unit 22, and an address table memory 23.
`The communication controller 21 serves as an interface
`
`for communicating with the management server 6 on the
`Internet 11 via a network such as an in-house LAN 12, a
`public telephone network 14 and an ISP 13, or a wireless
`network 15. The terminal unit 22 serves to perform various
`processes required for the computer 1 to behave as a client
`of the management server 6. The address table memory 23
`stores an address table in which personal information is
`recorded.
`
`The computers 2-4 and the portable telephone device 5
`shownin FIG. 2 are similar to the computer 1 shownin FIG.
`3, and thus they are not described in further detail herein.
`The computers 1-4 and the portable telephone device 5
`(hereinafter,
`these devices are generically represented as
`
`

`

`US 6,754,665 B1
`
`5
`terminals) perform various processes including a
`client
`personal
`information registration process for registering
`personal information into the management server 6 and a
`personal information acquisition process for acquiring per-
`sonal information from the managementserver 6.
`Referring to the flow chart shown in FIG. 4, the personal
`information registration process is described below.
`When a user wants to register his/her personal informa-
`tion into the management server 6,
`the user operates a
`keyboard or the like (not shown) to input a registration
`command to the terminal unit 22. Thus,
`in step S1,
`the
`terminal unit 22 sends a personal information registration
`request to the management server 6 on the Internet 12 by
`accessing the managementserver 6 via the communication
`controller 21.
`
`Uponreception of the request for registration of personal
`information, the managementserver6 transmitsto the client
`terminal an HTML (Hyper Text Markup Language) file or
`the like representing a personal information input screen
`used to input personal information, as described in further
`detail later. If the communication controller 21 of the client
`terminal receives the HTMLfile, the communication con-
`troller 21 transfers it to the terminal unit 22 In step S2, the
`terminal unit 22 displays the personal information input
`screen in accordance with the received HTMLfile.
`
`The user inputs desired items of personal information via
`the personal information input screen. After completion of
`inputting the personal information, the user enters a personal
`information transmission command. In step S3, the terminal
`unit 22 determines whether a transmission command has
`
`been issued If it is determined in step S3 that the personal
`information transmission commandhasnot been issued, the
`process returns to step S3.
`If it is determined in step S3 that the personal information
`transmission command has been issued, the process goes to
`step S4.
`In step S4,
`the terminal unit 22 controls the
`communication controller 21 so as to transmit the personal
`information, which has been input via the personal infor-
`mation input screen, to the managementserver 6. Thus, the
`personal information registration process is completed.
`Referring now to the flow chart shown in FIG. 5, the
`process of acquiring personal
`information is described
`below.
`
`When a user wants to acquire personal information of
`another user from the managementserver6, the user inputs
`a personal information request commandto the terminal unit
`22. In response, in step S11, the terminal unit 22 controls the
`communication controller 21 so as to transmit a personal
`information retrieval request command together with a key-
`word to the managementserver 6 on the Internet 11.
`Herein, when the personal information request command
`is input to the terminal unit 22, the keyword may be given
`by the user by meansof inputting the nameorthe electronic
`mail address of the user whose personal informationis to be
`acquired.
`The keyword may also be given from information locally
`owned by a client terminal. For example, when personal
`information of a certain user described in the address table
`stored in the address table memory 23 includes only the
`electronic mail address of that user,
`if another item of
`personal information of that user is required, the keyword
`may be obtained by invoking the address table and pointing
`to the electronic mail address. Alternatively, when an elec-
`tronic mail from a certain user is displayed in a window on
`the display screen of the client terminal, if the user of the
`client
`terminal
`inputs a personal
`information request
`
`10
`
`15
`
`25
`
`30
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`command, the terminal unit 22 detects the electronic mail
`address of the sender of the electronic mail displayed in the
`window and employsthe detected electronic mail address as
`the keyword.
`If the management server 6 receives the personal infor-
`mation retrieval request command together with the key-
`word from the client terminal,
`the management server 6
`retrieves the personal information which matches the key-
`word as will be described in further detail later, and trans-
`mits (returns) the retrieved personal informationto the client
`terminal. In step $12, the client terminal determines whether
`the personal information has been received from the man-
`agement server 6. If it is determined in step S12 that the
`personal information has not been received from the man-
`agement server 6, the process returns to step $12.
`If it is determined in step S12 that the personal informa-
`tion has been received from the managementserver6, that
`is,
`if the communication controller 21 has received the
`personal information from the management server 6, the
`process goes to step $13. In step $13, the terminal unit 22
`receives the personal information from the communication
`controller 21 and registers it into the address table in the
`address table memory 23. Thus, the personal information
`acquisition process is completed.
`As described above, the user of the client terminal can
`register personal
`information of a desired user into the
`address table by performing a simple operation upon the
`keyboard to generate a keyword without having

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


Or .

Accessing this document will incur an additional charge of $.

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

Accept $ Charge
throbber

Still Working On It

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

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

throbber

A few More Minutes ... Still Working

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

Thank you for your continued patience.

This document could not be displayed.

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

Your account does not support viewing this document.

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

Your account does not support viewing this document.

Set your membership status to view this document.

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

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

Become a Member

One Moment Please

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

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

Your document is on its way!

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

Sealed Document

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

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


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket