GB2339313A - Advertisement display system - Google Patents

Advertisement display system Download PDF

Info

Publication number
GB2339313A
GB2339313A GB9923656A GB9923656A GB2339313A GB 2339313 A GB2339313 A GB 2339313A GB 9923656 A GB9923656 A GB 9923656A GB 9923656 A GB9923656 A GB 9923656A GB 2339313 A GB2339313 A GB 2339313A
Authority
GB
Grant status
Application
Patent type
Prior art keywords
terminal
means
message
user
operation information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
GB9923656A
Other versions
GB9923656D0 (en )
GB2339313B (en )
Inventor
Yuichiro Itakura
Yuichiro Tsutsui
Nobuyuki Fujita
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aim Corp
Original Assignee
AIM CORP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30011Document retrieval systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/107Computer aided management of electronic mail
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce, e.g. shopping or e-commerce
    • G06Q30/02Marketing, e.g. market research and analysis, surveying, promotions, advertising, buyer profiling, customer management or rewards; Price estimation or determination
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • H04L12/1432Metric aspects
    • H04L12/1439Metric aspects time-based
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Metering, charging or billing arrangements specially adapted for data wireline or wireless communications
    • H04L12/1453Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1471Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network splitting of costs
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/12Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with filtering and selective blocking capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages
    • H04L51/34Arrangements for user-to-user messaging in packet-switching networks, e.g. e-mail or instant messages with provisions for tracking the progress of a message

Description

1 2339313 MESSAGE SEARCHING SYSTEM AND TERMINAL

BACKGROUND OF THE INVENTION

Field of Invention

The present invention relates to a message searching system and a terminal, which displays information obtained from a computer communications network, such as the Internet.

Description of Related Art

Various kinds of information are available to users through communications networks such as the Internet and other personal computer networks such as Bulletin Board Services (BBS), 6tc. Typically, a te=inal, such as a personal computer, is connected via a modem and a telephone line, local area network, or wide area network, etc., to a computer, such as a 'server', operated by an information provider. A user, using his own terminal, can access whatever data the information provider makes available. A user can also access other information providers through the communications network to which the first information provider is connected. Thus, a user can receive information from various information providers.

An information provider or some enterprise connected to the information provider identifies a user based on a unique user ID and a password to determine whether to provide access to the information to the user and may charge a fee for providing information.

Information supplied to the user is typically displayed in a single window on the user's computer or terminal 2 display. The user can scroll displayed information or switch to a submenu screen. An information provider may provide designated information selected by the user together with additional information such as an advertisement. The additional information is displayed in the same window as the designated information sought by the user.

In a typical arrangement, when a user scrolls his display the additional information, being in the same window, disappears. This prevents the additional information (such as an advertisement) from being efficiently provided to the user. This is a problem for the advertiser.. To overcome this problem, Japanese Patent Application H8-67278, which is commonly owned with this application, proposes an arrangement for displaying two separate and distinct windows on a userl.s display. one of the two windows displays the designated information requested by the user. The other of the two windows is for the additional information, such as an advertisement. Advertisements displayed in the second window can be selected, based on a user characteristic profile, so as to be appropriate for a particular user. Such a profile might include characteristics such as, but not limited to, age, gender, marital status, a previously expressed interest, etc.

As a user's characteristics change over time, the advertisements presented in the second window can be changed based on the users changed profile. For example, some advertisements may target a particular age range.

Information available via communications networks, such as the Internet, change significantly over time. Therefore, it is desirable to be able to supply selected information related to newly available content and for a computer or 3 terminal to be able to keep track of a user's characteristic profile. It is also desirable to be able to keep track of a plurality of user characteristic profiles even when a plurality of users have copied and use the same program to access information. It is also desirable to provide a message searching system and a terminal, which can meet such objectives.

SUMMARY OF THE INVENTION

According to one embodiment of the invention, there is provided a message delivery system for providing messages to users interacting therewith via a terminal and a communication line. The system comprises: a message user database for storing user records constituting a characteristics profile of each user; a transmittal condition database for storing message records containing identification (ID) information related to messages that can be transmitted to the terminal, together with transmittal conditions for each message; a detector for determining a necessity to revise the user records based on information received from the terminal; revising means for revising the user records stored in the message user database when the detector detects the necessity to do so; reading means for reading the user records to obtain a characteristics profile from the message user database in response to a request from the terminal; means for searching the transmittal condition database using characteristics from user records read by the reading means to locate message records whose transmittal conditions are consistent with the read characteristic profile and obtaining ID information for located message records; and means for transmitting the ID information for located message records to the terminal.

4 As one example, the characteristics profile might include each user's birth date and the last communication date associated with that user. The detector dete=ines that the characteristics profile needs to be revised when the date obtained by adding a predetermined value to the user's birth date has already. passed at the time of user's connection to the message searching system and is after the last revision.

means are provided for adding a new item (data field) to the message user database, and means for storing an indicator, such as an item revision time, when the new item was added to the message user database. The detector determines that the user's characteristics profile needs to be revised when the last communication date is before the item revision time. As an alternative, the detector might determine that the characteristics profile needs to be revised when the date obtained by adding a predetermined value to the user's birth date has already passed at the time of the user's connection to the message searching system and that connection has occurred after the latest item revision time of the transmittal condition database. As another alternative, the detector might simply determine that the characteristics profile needs to be revised when the last revision time is before the item revision time.

Means are provided for comparing the characteristics profile revision time of a particular user who is using the terminal, the revision time being stored in the te=inal, with the characteristics revision time stored in the message user database when the terminal is connected to the message searching system. This is particularly helpful when a plurality of users use the same terminal. Means are provided for transmitting the characteristics profile in the message user database to the terminal when the characteristics revision time in the message user database is after the characteristics revision time in the terminal.

Means are provided for comparing the characteristics revision time of the user who is using the terminal, which is stored in the terminal, with the characteristics revision time in the message user database. When the data in the message user database is lagging that which is stored in the terminal, the message user database is updated.

There is provided a database for storing ID information for identifying each of a plurality of user items, as well as attributes, and range and size of each item. The message user database includes an ID for each user, which corresponds to his characteristics.

According to another embodiment of the invention, there is provided a terminal for communicating with the massage delivery system, the terminal comprising: a storage for string characteristics of a terminal user; a second detector for detecting a necessity to revise the characteristics based on information received from the message system; means for requesting through the communication line a dialog for revising the characteristics when the second detector detects the necessity; input means for inputting new characteristics of the user using the dialog; and means for revising the characteristics stored in the storage using the new characteristics input by the input means.

According to one embodiment of the invention, the terminal stores the user's birth date and date of last communication with the message searching system. The characteristic profile is revised based on whether the date obtained by adding a predetermined period to the user's birth 6 date has already passed at the time of the communication with the message searching system and is after the last communication date.

The terminal is provided with means for receiving from the message user database an item revision time indicating when a new item (data f ield) was added to the message user database. The detector determines that it is necessary to revise the characteristics stored in the storage when the last communication date is before the item revision time.

According to one embodiment of the invention, the terminal stores the user's birth date and the characteristic revision time. The detector detects a necessity to revise the characteristics based on whether the date obtained by adding a predetermined period to the user's birth date has already passed at the time when the user connects to the message searching system and is after the last revision time.

The terminal can further include means for receiving an item revision time indicating when a new item was added to the message user database, from the message user database.

The detector determines that it is necessary to revise the characteristics stored in the storage when the last revision time is before the item revision time.

According to one embodiment of the invention, the message searching system contains characteristics of each user. The terminal includes means for comparing the characteristics revision time about the user of the terminal, which is stored in the storage, with the characteristics revision time stored in the message searching system, when the terminal is connected to the message searching system; and means for transmitting the characteristics stored in the 7 storage to the message searching apparatus when the characteristics revision time stored in the message searching system is before the last revision time of the message information stored in the storage. 5 According to another embodiment of the invention, the terminal includes means for comparing the characteristics revision time of the user of the terminal, which is stored in the terminal, with the characteristics revision time stored in the message searching system. Means are provided for downloading characteristics stored in the message searching system when the characteristics revision time stored in the message searching system is after the characteristics revision time stored in the terminal. Further, means are provided for revising the characteristics stored locally in the terminal.

The terminal has a detector for detecting that the characteristics stored locally have been revised by the user.

means are provided for uploading locally revised characteristics to the message searching system.

The terminal can be provided with a CPU for processing information. The terminal has a storage for storing process information which is to be read and processed by CPU. The terminal also has a memory for storing the location where the process information is stored in the storage. Means are provided for inputting ID information for identifying the user of the terminal. Determination means are provided for determining the location of the process information in the storage when processing the process information. Re-input means are provided for requesting the user of the terminal to input the ID again when the location of the process information stored in the memory is different from the 8 location of the process information determined by the determination means. User determination means are provided for determining that, when the ID inputted through the input means is different from the ID inputted through the re-input means, the user who is using the terminal is different from the user who originally inputted the ID through the input means.

The terminal has input means including means for inputting a user password. A re-input means includes means for requesting the user to input the password again when the location of the process information stored by the memory is different from the location of the process information determined by the determination means. The user determination means includes means for determining that, when the password inputted through the input means is different from the password inputted through the re-input means, a user who is using the terminal is a different person from the user who originally inputted the ID.

According to an embodiment of the invention, there is provided process information to be executed by a CPU. Alternatively, the process information may be data which is read out by the CPU. The terminal further including means for communicating with an information processor through a communication line. It also includes means for inquiring whether the ID and the password which were inputted through the re-input means are registered in the information processor, when the user determination means determines that a user who is using the terminal is a different person from the user who originally inputted the ID through the input meansBRIEF DESCRIPTION OF THE DRAWINGS

9 Fig. 1 is a block diagram showing the overall structure of the display system according to one embodiment of the invention.

Fig. 2 is a block diagram showing the structure of the terminal 10.

Fig. 3 is a block diagram showing the structure of the connection manager 23 and the message distributor 28.

Fig. 4 illustrates the structure of the message user database 34.

Fig. 5 illustrates the structure of the transmittal condition database 36.

Fig. 6 is a block diagram showing a functional structure of the software executed by CPU 40 of the main body 14.

Fig. 7 illustrates a screen display of the display 12.

Fig. 8 is a diagram showing the connection sequence of the terminal 10, message manager 24, etc.

Fig. 9 is a flowchart showing a connection process of the terminal 10.

Fig. 10 is a flowchart showing a message request action of the connection manager 23.

Fig. 11 illustrates a structure of the provider user database 25.

Fig. 12 is a flowchart showing a connection process of the message manager 28.

Fig. 13 is a flowchart showing a connection process of the message distributor 38.

Fig. 14 illustrates a structure of the connection log 28.

Fig. 15 is a diagram showing the characteristics revising sequence in the first embodiment.

Fig. 16 is a flowchart showing the characteristics revising process of the message distributor 28.

Fig. 17 is a flowchart showing details of the communication processing step of Fig. 16.

Fig. 18 is a flowchart showing the characteristics revising process of the message viewer 76.

Fig. 19 is a flowchart showing details of the event processing step of Fig. 18.

Fig. 20 is a diagram showing the characteristics revising sequence of a second embodiment of the invention.

Fig. 21 illustrates the structure of the message user database 34 of a third embodiment of the invention.

Fig. 22 illustrate a list of item types of the third embodiment of the invention.

Fig. 23 is a block diagram showing a hardware structure of overall the communication system of the fourth embodiment of the invention.

DETAIL DESCRIPTION OF THE EMBODIMENTS

Various embodiments will be described with reference to the attached drawings, wherein like reference numerals indicate like or corresponding elements through the drawings.

First Embodiment Fig. 1 is a block diagram showing a system according to a first embodiment of the present invention. Terminals 10 are connected to each information provider 20 through modems such as modems 16 and 18, a public communication network 17, and public network gateways 19. Each information provider 20 is managed by a so-called Internet Provider.

one or more message providers 30 are connected to a message distribution system 39 through a dedicated line.

Message providers 30 supply the message distribution system 39 additional information such as an advertisement (message), transmittal conditions for respective messages, and the web home page address of the message provider 30 on the Internet 32. Messages may include still image, dynamic image, voice sound, and any combinations of these. The message distribution system 39 (message searching system) includes the message distributor 28 (message searcher), message user database 34, transmittal condition database 36, and connection log 38. The transmittal condition database 36 stores transmittal conditions of respective messages. The message user database 34 stores data about message users of terminals 10.

The message distributor 28 is connected to information providers 20 through dedicated lines. The message distributor 28 transmits the message provided from the message provider-30 to each information provider 20. The message contains data indicating an Internet Web page address of the message provider. The message manager 24 in the information provider 20 receives the message from the message distribution system 39, and stores the message in a message database 26 along with an associated message ID (URL).

The terminal 10 can receive information, such as a home page, from the Internet 32 through an Internet gateway 22 of the information provider 20. The terminal 10 receives a message from the message manager 24. The message manager 24 reads out the message from the message database 26 and transmits the message to the terminal 10 based on the request from the terminal 10. The user of a terminal 10 has a provider user ID and a provider password which are used to connect through a public network gateway 19 to the Internet gateway 22, together with a message user ID and a message 12 user password which are used to obtain the message from the message manager 24.

If a plurality of information providers 20 are connected to the public network 17, the user can connect to any of the information providers 20. For this purpose, a user may have many provider IDs for use with respective information providers 20. However, a single message user ID can be used for all information providers 20.

Fig. 2 is a block diagram showing a hardware arrangement of the main body 14 of the terminal 10. CPU 40 executes programs stored in a ROM 42 and a RAM 44. A timer 46 counts predetermined periods. A user inputs data through an input device 48. A hard disk drive 50, as an example of the storage device, stores image data, user information 49, such as a characteristic profile, a last revising date of the characteristic profile, and programs for operating CPU 40.

A battery-backed up calendar IC 51 supplies the current date and time to CPU 40. A floppy disk drive 52 reads data and/or a program from the floppy disk 56 and provides it to CPU 40. A CD-ROM drive 54 reads out data or a program from a CD-ROM 58 to provide it to CPU 40. The main body 14 also has a display interface which is used to connect to the modem 16, and a modem interface which is used to connect to the display 12.

Fig. 3 is a block diagram showing a hardware arrangement of the connection manager 23, message manager 24 and the message distributor 28, shown in Fig. 1. A CPU 90 executes programs stored in a ROM 92 and a RAM 94. Timer 96 counts predetermined periods. The communication interface 98 processes inputs and outputs to and from an outside 13 communication line. The message distributor 28 may include two of the communication interfaces 98 for connecting with the message provider 30 and the information provider 20, respectively. A user inputs data through an input device 100. The database interface 102 is used to connect the system to various databases DB stored on storage devices such as, for example, a hard disk. The floppy disk drive 104 reads data and/or a program from a floppy disk 106, and provides it to CPU 90. A calendar IC 107 supplies date and time information to CPU 90. The display 108 displays the communication state, etc., to the operator.

Fig. 4 is an exemplary data base structure for message user database 34. Other structures can be used. The message user database 34 contains records having fields of data constituting a user characteristic profile of each user. The fields of data correspond to individual user characteristics, such as message user ID, message user password, provider ID for identifying each information provider 20, provider user

ID, information display time, birth date, gender, marital status, occupation, address, name, drinking permitted status, etc. Fields of data can be added and modified as needed. For example, a characteristic "smoking" indicating whether or not a user smokes has been newly added to a field 35. A last communication date when a user last communicated with the message distributor and the item revision time when the new field was last added to the database are recorded in the message user database 34.

Each user inputs his or her characteristics via terminal when using a message viewer 76 (see Fig. 6) for receiving information from the message manager 24 for the first time, or when installing the message viewer program in the terminal 10. Terminal 10 transfers inputted characteristics to the 14 information provider 20, while storing the characteristics locally on hard disk drive 50. The information provider 20 transfers the received information to the message distributor 28 which stores the characteristics in the message user database 34. The characteristics may contain age, occupation category, income, hobby, etc.

Fig. 5 shows one possible arrangement of transmittal condition database 36. The transmittal condition database 36 stores message URLs for identifying each message together with transmittal conditions associated with that message. The transmittal conditions include limitation of display frequency for each user, limitation of display frequency for the overall users, display time, range of the age to be displayed, gender, marital status, occupation, address, whether the user drinks alcoholic beverages or not, etc. New search items can be added to the transmittal condition database 36, as necessary. In this embodiment, a newly added field 37 contains information indicating whether or not. The message distributor 28 searches for the URLs of messages, in response to the request from the terminal 10, based on the user's characteristics, and transmits the URLs of identified messages to terminal 10. After receiving the URLs, messages matching the URLs and which are therefore appropriate for the user can be sent to terminal 10.

Fig. 6 shows the functional structure of software executed by CPU 40 of main body 14. The software is, stored in storage medium, such as a CD-ROM 58 or floppy disk 56, which is provided to each user. The software can be stored in either non- compressed or compressed form. The software is installed into the hard disk drive 50 from the recording medium. At this time, message viewer location information is also stored on the hard disk drive 50. The message viewer location information represents the location of the message viewer 76 on the hard disk drive 50. The software stored in the hard disk drive 50 is read out in the RAM 44 and is executed by CPU 40. 5 The software which is supplied to the user for installation on hard disk drive 50 comprises a communication module 73 having a PPP driver 70 and a TCP/IP driver 72, a browser 74, and a message viewer 76, as a functional structure. The PPP driver 70 creates a data link with public network gateway 19. The browser 74 communicates with the Internet gateway 22 through the TCP/IP driver 72 on the data link created by the PPP driver 70. The message -viewer 76 communicates with the message manager 24 through the TCP/IP driver 72 on the data link created by the PPP driver 70. The message viewer 76 has a connection module 78, a revising module 83 and an event process module 86 for updating (revising) the characteristics, and a queue 84 for storing the URL received from the message distributor 28. The queue 84 is generated in the RAM 44.

Fig. 7 is an example of a screen displayed on display 12. Two windows open on the display 12. One is a browser window Go for displaying images found by browser 74. Browser window 60 displays information received from the Internet 32. Suitable examples of the browser 74 include Netscape (trademark) and Mosaic (trademark). The other window is a message viewer window 62 for displaying messages from message viewer 76.

Message viewer window 62 displays a home page button 64, information request button 66, halt/resume button 68 and quit button 69. The window displays messages received from information providers 20. When the home page button 64 is 16 clicked, the home page which corresponds to the message being displayed in message viewer window 62 is displayed in the browser window 60. When the information request button 66 is selected, material which corresponds to the message being displayed on the message viewer window 62 is transmitted to the user.

The message viewer window 62 displays a new message every predetermined period (e.g., every one minute). When the message can be displayed, the halt/resume button 68 indicates "halt". If the halt/resume button 68 is selected in this situation, message transmission is interrupted. When a message is not being displayed, the halt/resume button 68 indicates "resume". If the halt/resume button 68 is selected in this situation, message transmission begins again. Selecting the quit button 69 causes the message viewer to finish communication with the message manager 24.

Fig. 8 explains the connection sequence among the terminal 10, public network gateway 19, connection manager 23, message manager 24, message distributor 28, the Internet gateway 22 and the Internet 32. When the communication module 73 of the terminal 10 generates a PPP connection request (S102), the connection manager 23 verifies whether the provider user ID and the passwor d of the user who requested connection, are registered, by checking the provider user database 25 (S104).

If the ID and the password are registered, the connection manager 23 transmits a PPP connection permission to the terminal 10 (S106), while sending the provider user ID to the message manager 24 together with the corresponding port number of the PPP connection. The message manager 24 stores the provider user ID and the corresponding port number 17 of the PPP connection in the RAM 94.

Once the PPP connection is allowed, a TCP/IP connection is established between the browser 74 of the terminal 10 to the Internet gateway 22 (Silo), and browser 74 can communicate with the Internet 32 through the Internet gateway 22 (S112). The message viewer 76 of the terminal 10 is TCP/IP connected to the message manager 24 (S114). Then, the message manager 24 requests verification to the message viewer 76 of the terminal 10 (S118).

When the message viewer 76 receives the verification request, the message viewer 76 transmits the message user ID and the password to the message manager 24 (S120). The message manager 24 reads from the RAM 44 the provider user ID which has been associated with the port number of the PPP connection used by the user, and transmits the provider user ID to the message distributor 28, together with the provider ID for identifying the provider, the message user ID and the password (S121).

The message distributor 28 checks the message user DB 34 to verify whether the received message user ID and the message user password are registered in the message user DB 34 (S122). If they are registered, the message distributor 28 transmits a connection permission to the message viewer 76 (S124). Then, message distributor 28 notifies the connection manager 23 to stop charging the user who has a provider user ID, which has been received at S121 (S130).

The details of operations generally shown in Fig. 8 will be explained in greater detail with reference to Figs. 9 through 13. Fig. 9 shows anoperation flow of the connection module 78 of the message viewer 76. The connection module 78 18 starts the communication module 73 (S210). This causes the communication module 73 to connect using PPP with the public network gateway 19 using the provider user ID and the provider user password. Having confirmed a PPP connection (S212), the connection module 78 starts the browser 74 (S214) to cause a TCP/IP connection between the browser 74 and the Internet gateway 22. Then, the connection module 78 is TCP/IP connected with the message manager 24 using a unique TCP/IP port number of the message viewer 76 (S216) Since independent communication links are formed between the browser 74 and the Internet gateway 22, and between the message viewer 76 and the message manager 24 based on the two different TCP/IP port numbers, communication via these two separate paths occurs independently of each other. This allows the messacre viewer 76 to display a message without losing any essential browser functionality.

Next, the message viewer 76 compares the message viewer position information with the position of the message viewer 76 (S218). If these two agree with each other, the message viewer 76 waits for a verification request from the message manager 24 (S222). Verification, that is, the message user ID and the password are given to the message viewer 76 by the message distributor 28 at the first communication with message distributor 28, and are stored in hard disk drive 50.

When message viewer 76 receives the verification request from the message manager 24, the message viewer 76 reads out the message user'ID and the password from the hard disk drive 50 and transmits them to the message distributor 28 (S224) If, at S218, the message viewer position information does not agree with the actual position where the message viewer 76 is stored, there is a high possibility that the message viewer 76 has been copied to the other computer. Therefore, the user is requested to input the message user ID and the password again (S220). The newly inputted message user ID and the password are stored in the hard disk drive 50, together with the new message viewer position information which indicates the new position of the message viewer.

Then, the message viewer 76 waits for a request from the message manager 24 (S222), and transmits the message user ID and the password stored in the hard disk drive 50 (S224).

This ensures that the message user ID of the genuine user can be transmitted to the message manager 24 even if the message viewer 76 is copied to the other computer. Once. the message viewer 76 receives permission from the message manager 24 (S226), the message viewer 76 starts the timer 46 (S228) and starts to carry out a characteristics revising process (Fig, 18).

Fig. 10 shows an operation flow of the connection manager 23 in the connection sequence shown in Fig. 8. when a PPP connection is requested through the public network gateway 19 from the terminal 10 (S310), the connection manager 23 requests the provider user ID and the password to the terminal 10 (S312). Upon receiving the provider user ID and the password, the connection manager 23 checks the provider user database 25 to verify whether the provider user ID and the password are registered (S314).

As shown in Fig. 11, the provider user database 25 stores provider user ID, provider user password, the total amount of chargeable time so far, and chargeable amount for each provider user. If the received provider user ID and the provider user password are not registered in the provider user database 25, the connection manager 23 disconnects the line (Fig. 10, S318) and the process concludes (S320). If the provider user ID and the password are registered in the provider user database 25, the connection manager 23 permits the terminal 10 a PPP connection (S322) and transmits a connection notice to the message manager 24 (S324). Then, the connection manager 23 waits for a charge stop notice from the message distributor 28 (S326). Upon receiving the notice, the connection manager 23 stops charging the provider user (S328).

Fig. 12 shows a operation flow of the message manager 24 in the connection sequence shown in Fig. 8. Upon receiving the connection notice from the connection manager 23 (S810), the message manager 24 records the received provider user ID in the RAM 94 (S812). The message manager 24 starts the timer 96 (S814) to determine whether the timer 96 has been TCP/IP connected with the message manager 24 (S816). If.the TCP/IP connection is not established, the message manager 24 waits (S816, S818). If the timer 96 is up (S818), the process concludes (S820).

If, at S816, it is determined that the TCP/IP connection has been completed, the message manager 24 requests verification to the message viewer 76 (S822). The message manager 24 resets the timer 96 to start counting again (S824). If the timer 96 is up before the message manager 24 receives the verification (S828), the process concludes (S830). If the message manager 24 receives the verification (S826), the message manager 24 reads out the provider user ID from the RAM 94 (S832) and transmits it to the message distributor 28 together with the provider ID for identifying this provider, the message user ID and the message user password which were received from the message viewer 76 (S834). Then, the communication starts between the message 21 viewer 76 and the message distributor 28 through the message manager 24 (S836).

Fig. 13 shows an operation flow of the message distributor 28 in the connection sequence shown in Fig. 8.

Upon receiving the message user ID and the password from the message manager 24 (S410), the message distributor 28 checks the message user database 34 (Fig. 4) to determine if they are registered (S412). If the user is not registered, the message distributor 28 sends an inquiry to the message viewer 76 asking whether the user is registering as a new user (S414). If new user registration is requested, the message distributor 28 receives a characteristics form the message viewer 76 and stores the information in the message user database 34. The message distributor 28 also gives the user the message user ID and the message user password (S418)...

If registration is not requested (S414), the message distributor 28 requests verification to the message viewer 76 (S420) and waits until receiving the verification (S422) Then operation returns to S412. Upon receiving the verificaticin, the process returns to S412 and proceeds to S424. At S424, connection permission is generated, and a log on, is recorded in the connection log 38 (S426) The message distributor 28 reads the provider ID and the provider user ID which have been received form the message manager 24 (S428) and instructs the provider defined by the provider ID to stop charging the user who is defined by the provider user ID (S430). This event is recorded in the connection log 38 (S432). Since message user ID and provider user ID are independently provided, charging can be stopped only on the provider ID that is in use, even if a single message user has a plurality of providers (or provider user 22 IDs) The connection manager 23 stops charging the user who is defined by the provider user ID. In other words, the connection manager 23 maintains access to the Internet 32 without charge. 5 Fig. 14 shows an example of a connection log 38. Provider ID, event (log on, charge stop, etc.), event occurrence time are recorded in the connection log for each provider user ID. The connection fee to the provider during the charge stop period is paid by the owner of the message distribution system 39. Therefore, the provider user can access the Internet only on condition that the user watches the message.

The example shown in Fig. 14 indicates that charge on the provider user XXX was stopped after log'on. The message distributor 28 detects the charge stop period based on the connection log 38 to pay the fee which corresponds to the detected period to the provider. The message distributor 28 charges the message provider 30 for the service of displaying the message on the message viewer 76.

Fig. 15 explains the communication sequence of terminal 10, the message manager 24 and the message distributor 28 after the message distributor 28 permits the connection of terminal 10. The message distributor 28 checks the terminal 10 to inquire the last revision date and time (hereinafter, referred to simply as revision time) of the characteristics 49 of the terminal 10 (S140). When the message distributor 28 receives the last revision time and time of the characteristics from the terminal 10 (S142), the message distributor 28 determines if it is necessary to revise the characteristics, based on the last revision time and on the data stored in the message user database 34 (S144) - 23 If it is determined that the characteristics 49 of the terminal 10 needs to be revised, the message distributor 28 requests the terminal 10 to transmit the characteristics (S14G), and the terminal 10 transmits the characteristics in response to the request. If it is necessary to revise both the characteristics 49 and characteristics stored in the message user database 34, the message distributor 28 requests the terminal 10 to input the characteristics (S150) 10 Terminal 10 requests the dialog for revising the characteristics from the connection manager 23 (S152), downloads the dialog (S154), and displays on the display 12. Characteristics input by the user (S156) are transmitted to 15 the message distributor 28 (S158). Then, the message distributor 28 registers the characteristics in the message user database 34, and send it back to the terminal 10 (S160). once the characteristics of the message distributor 28 and the terminal 10 have been revised, communication starts 20 (S162, S164).

Fig. 16 shows the detailed operation of the message distributor 28 in the communication sequence shown in Fig. 15. The message distributor 28 inquires and receives the revision time of the characteristics of the terminal 10 (S450). Then, the message distributor 28 compares the received revision information with the last communication date between the message user database 34 and the user (S452). If the characteristics revision time of the terminal 10 is later than the last communication date, the characteristics 49 of the terminal 10 have been revised. Then, the message distributor 28 requests the characteristics 49 (S454). The message distributor 28 revise the message user database 34 based on the received characteristics 24 (S456) The last communication date with the message user is further compared with the item revision time of the message user database 34. For example, if an additional field, such as f ield 35 (see Fig. 4) has been added to the message user database 34, all users are required to input data to the new field 35. If the database item revision time is later than the last communication date, the characteristics have not been revised. Then, the message distributor 28 requests through the terminal 10 new characteristics from the message user in connection with the newly added item (S460). When new information is input by the user, the message user database 34 is revised (S462).

Then, comparison is made among the current date, the date which is obtained by adding a predetermined value to the birth date, and the last communication date (S464). If the birth date plus predetermined value is before the current date and after the last communication date, the message distributor 28 requests the user to input information about a certain item which is associated with the predetermined value (S466). Predetermined value is, for example, 20 years, which means that the user reaches his majority. The associated item may an indicator of whether or not the user smokes. In this case, if the user became twenty years old between the current date and the last communication date, the message distributor 28 requests the user to input information as to whether the user smokes at S466. When the characteristics have been received from the terminal 10, the message user database 34 is revised (S468).

The message distributor 28 compares the revision time of the characteristics 49 with the last communication date with the user of the message user database 34 (S470) If the revision time of the characteristics of the terminal 10 is before the last communication date, there is a possibility that the message user database 34 has been revised by accessing from a different terminal other than the user's terminal. In order to revise the characteristics of the terminal 10, the message characteristics stored in the message user database 34 are transmitted to the terminal 10 (S472). Thus, the revision of the characteristics is completed, and the communication process starts (S474) Fig. 17 shows details of the communication process of the message distributor 28 (S474) Upon receiving a message request (URL request) from the terminal 10 (S710), the message distributor 28 searches and reads out the provider ID and the provider user ID from the connection log 38 using the TCP/IP number which is now URL-requested (S712).

Then, the message distributor 28 searches and reads out the characteristics from the message user database 34 using the provider ID and the provider user ID (S714). The message distributor 28 further searches a message, which is to be transmitted from transmittal condition database 36 in the message user database 34 and reads out the URL using the characteristics (S716) Then, the message distributor 28 transmits the URL read out from the message user database 34 to the terminal 10 and the process returns to Fig. 16 (S720) Fig. 18 shows in greater detail the operations of the message viewer 76 in the communication sequence of Fig. 15.

When the message viewer 76 receives a request for characteristics (S240), it reads the characteristics 49 from the hard disk drive 50 and transmits them (S242) When the message viewer 76 receives an input request of 26 characteristics (S246), the message viewer 76 requests the message manager 24 to transmit a dialog screen for enabling the user to input the characteristics (S248). The message manager 24 transmits the dialog screen in response to the request. The message viewer 76 downloads the dialog (S248) to display on the display 12 (S250).

When the user inputs the characteristics (S252), the message viewer 76 transmits the characteristics to the message distributor 28 (S254). When the message distributor 28 receives the characteristics (S256), the message distributor 28 revises the characteristics 49 stored in the hard disk drive 50 (S258). If neither the characteristics request, characteristics input request, nor characteristics is received, or if S242, S254, or S258 is finished, event processing is executed (S244) and the process returns to S240.

Fig. 19 shows details of the event processing (S244) of Fig. 18. This operation is executed by the event process module 86 of the message viewer 76. If there is a predetermined number or more of empty places in the queue 84 (S514), the event process module 86 transmits a URL request (S516). This allows the terminal 10 to receive URLs of the message that the message distributor found during a search.

Upon receiving URL O(S518), the terminal 10 transmits a receipt response (S520) and loads the URL in the queue 84 (S522) When the timer 46 counts up (S524), the image stored in the image buffer is displayed (S526). This allows the URL message searched by the message distributor to be displayed. Next, the timer 46 is reset (S528), and a new image is requested to the message manager 24 using the URL loaded at the head of the queue 84 (S530). When the image is received from the message manager (S532), the received image is stored 27 in the image buffer (S534). Storing the image in the image buffer in advance can reduce the time taken for revising the image.

Second Embodiment Fig. 20 shows the characteristics revision sequence in accordance with the second embodiment. In the first embodiment, the message distributor 28 determines the necessity to revise the characteristics. In the second embodiment, the message viewer 76 of the terminal 10 determines the necessity to revise the characteristics. The other structure is the same as that in the first. embodiment.

When the message viewer 76 receives a connection permission from the message distributor 28 at S124 of Fig. 8, the message viewer 76 inquires the message distributor 28 about the last communication date with the user and the item revision time in the message user database 34 (S710). The message distributor 28 reads out the provider ID and the provider user ID from the connection log 38 using the TCP/IP port number. The message distributor 28 also reads out the last communication date from the message user database 34 using the provider ID and the provider user ID, and transmits it together with the item revision time to the terminal 10 (S172).

The message viewer 76 of the terminal 10 compares the received last communication date with the last revising date 47 of the characteristics 49. If the last communication date is after the last revising date 47, there is a possibility that the message user database 34 has been revised by accessing from the other terminal. Then, the message viewer 76 requests the message distributor 28 to transmit the 28 characteristics (S174). Then, the message distributor 28 reads out the characteristics in the same manner as reading of the last communication date, and transmits the characteristics to the terminal 10 (S176). Upon receiving the characteristics, the message viewer 76 of the terminal 10 revises the characteristics 49 stored in the hard disk drive 50.

Then, the message viewer 76 compares the item revision time received from the message distributor 28 with the last communication date. If the item revision time is after the last communication date, that means the message user database 34 does not contain the new item which has been newly added. The terminal 10 requests a dialog for revising the items to the message manager 24 (S178). Upon receiving the dialog from the message manager 24, the terminal 10 displays the dialog on the display 12 (S180) When the user inputs characteristics of the new item (S182), the characteristics 49 in the hard disk drive 50 is revised and the characteristics is transmitted to the message distributor 28 (S184).

If the date obtained by adding a predetermined value to the user's birth date is before the present time and before the last communication date, the terminal 10 request the message manager 24 to send a dialog for adding the new item as characteristics (S178) Upon receiving the dialog from the message manager 24, the terminal 10 displays it on the display 12. For example, if the date obtained by adding 20 years to the user's birth date is between the last communication date and the present time, a dialog for inquiring whether the user smokes is immediately added.

If the last revising date 47 in the characteristics 49 29 is after the last communication date received from the message distributor 28, that means the characteristics 49 has been revised without communicating with the message distributor 28. In this case, the characteristics 49 is transmitted to the message distributor 28 even though the items in the message user database 34 have not revised yet (S186). Then, the message distributor 28 revises the characteristics of the message user database 34. The message viewer 76 starts communication with the message distributor 28 (S188, S190) According to the embodiment, characteristics can be easily revised similarly to the first embodiment. The lead of the message distributor 28 is reduced compared with the first embodiment.

Third Embodiment Fig. 21 shows a structure of the message user database 34 in accordance with the third embodiment. In this embodiment, item type field is provided before each user item. The other structure is the same as that of the first embodiment.

As shown in Fig. 22, each type of the items corresponds to each item. Each item type is provided with an attribute, such as date, numeral, character, etc., data range, and the data size (Byte number). The message provider 30 selects an item as message searching condition. The message distributor 28 stores the searching condition of each item following the each item type. A plurality of item types and the associated conditions may be stored while corresponding them to each message.

This embodiment allows a searching condition of a new item to be set merely by revising the characteristics. A new item type can be added without changing the structure of the message user database 34. Searching conditions can be flexibly added or modified in response to various requests from the message provider 30.

Fourth Embodiment Fig. 23 shows a hardware structure of the fourth embodiment. In this embodiment, the information provider 20 functions as computer communication (BBS) provider, such as PC-VAN TM or COMPUSERVE TM, instead of the Internet provider.

Compared with Fig. 1, the Internet gateway 22 and the Internet 32 are not connected, instead, the BBS database is connected to the connection manager. The provider user database 25 is substituted by the BBS user database 251.

Since the structures shown in Figs. 2 through 5 and 8 are common with this embodiment, explanation will be omitted.

In Fig. 6, the browser 74 is substituted by a character-based or image-based communication software which communicates with the BBS. In this embodiment, the browser 74 communicates with the connection manager 23.

In this embodiment, the browser 74 is TCP/IP connected to the message manager 24 at S110 of Fig. 8, and transmits and receives data to and from the message manager 24 (S112) The other connection operations in Fig. 8 and structures shown in Figs. 9-11 and 13-22 are the common with this embodiment, and explanation will be omitted. The structure of the BBS user database 251 is the same as that of the provider user database shown in Fig. 12. However, in this embodiment, BBS ID, BBS user ID and BBS user password are used, instead of provider ID, provider user ID and provider user password.

31 Two independent links are generated for the BBS database 21 and the message database 26, respectively. Therefore, information which is independent from the BBS can be displayed on the message viewer window 62, even when information from the BBS is being received. Furthermore, charging from the BBS can be controlled based on the display state on the message viewer window 62. For example, when an advertisement is displayed on the message viewer window 62, BBS usage fee is not charged on the user, but is charged on the message provider 30.

Although, in the embodiment, two logical links are connected using TCP/IP, non-logical link may be connected to the connection manager 23 and a different data link may be formed from the message viewer 76 to the message manager 24.

Some Alternatives Browser 74 displays home page information of the Internet 32 in the specific embodiments described. However, browser 74 can have an alternative arrangement to provide an Internet telephone or the Internet TV phone which allows voice communication through the Internet. Even when the browser 74 does not display specific information on the display, the message distributor 28 can control the charging operation on the connection to the Internet in a similar way to that described above with respect to the specifically described embodiments, thereby providing an Internet telephone function to the user with a less expense.

The browser 74 can also be configured and arranged to display on-demand video information. In such case, a video providing system is substituted for the Internet gateway 22, 32 and charging for the on-demand video service may be stopped during display of additional information. This can provide less expensive on- demand video information to the user.

Although the message user database 34, the transmittal condition database 36 and. the connection log 38 are shown as independent disc devices, the information from all of them can be stored in a single storage device such as a disk, tape, or other storage device. The mutual relationship among the data of the respective fields can be realized by various file structures. For example, the message user database 34, the transmittal condition database 36 and the connection log 38 may be arranged in different areas of a single file.

Timer functions can be carried out either by hardware or software, or both. A single time can be used for various timing functions, or multiple timers could be used. Also, count times can be software set.

The Internet browser window and the message display module window may be arranged in the vertical direction on the display 12. The browser 74 and the message viewer 76 may be incorporated in a single unit, and the window may be divided into two areas. If this is a case, information received from the Internet 32 and information received from the message manager 24 are separately displayed in the respective areas in a signal window.

Most or all of the functions carried out can be software controlled. Thus programs can be provided on such media as floppy disk 56 and CD-ROM 58. The floppy disk 106 can store all or part of the software for controlling operations. These programs may be read from the medium on which they are stored directly into RAM for implementation (execution). The 33 recording media may include, but are not limited to, optical recording medium, such as a DVD, magnetic recording medium, such as an MD, opto- magnetic recording medium, such as a PD, tape medium, and semiconduqtor memory, such as an IC card and 5 a miniature card, other than floppy disk and CD-ROM. Especially, the following recording media can be provided:

(1) A recording medium which stores program code to be executed by a CPU of a terminal. The terminal is connected with a communication line. The program comprises (a) means for allowing communication through the communication line between CPU and the message searching system which contains user characteristic information of each user of plural terminals, (b) means for causing CPU to store the user characteristic information. in the storage of the terminal, (c) means for causing CPU to detect a necessity to revise the characteristics during 'the communication with the message searching system, (d) means for causing CPU to request, through the communication line, a dialog which is used to revise the characteristics of the user of the terminal, when it is detected that the revision is necessary, and (e) means for causing CPU to revise the characteristics stored in the storage based on the dialog received from the communication line.

(2) The recording medium of above item (1), wherein the program further comprises means for causing CPU to store the user's birth date and the last communication date between the massage search system in the storage, and means for causing CPU to detect a necessity to revise the characteristics with the detection means, based on the determination whether the date which is obtained by adding a predetermined period to the user's birth date has passed at the time of the communication between the terminal and the message searching 34 system and after the last communication date.

(3) The recording medium of above item (2), wherein the program further comprises means for causing CPU to receive from the message user database the database revision time when a new item is added to the message user database, and means for causing CPU to determine with the detector that it is necessary to revise the characteristics stored in the storage when the last communication date is before the database item revision time.

(4) The recording medium of above item (3), wherein the program further comprises means for causing CPU to store the user's birth date and the characteristics revision time in the storage, and means for causing CPU to detect a necessity to revise the characteristics with the detection means, based on the determination whether the date which is obtained by adding apredetermined period to the user's birth date has passed at the time of the user's connection to the message searching system and after the last revision time.

(5) The recording medium of above item (4), wherein the program further comprises means for causing CPU to receive from the message user database the database revision time when a new item is added to the message user database, and means for causing CPU to determine with the detector that it is necessary to revise the characteristics stored in the storage when the last revision time is before the database item revision time.

(6) The recording medium of any one of above items (1) through (5), wherein the program further comprises means for causing CPU to compare the characteristics revision time about the terminal user, which is stored in the storage, with the characteristics revision time stored in the message searching system, when the terminal connects to the message searching system, and means for causing CPU to transmit the characteristics stored in the storage to the message searching system when the characteristics revision time in the message searching system is before the characteristics revision time stored in the storage.

(7) The recording medium of any one of above item (1) through (6), wherein the program further comprises means for causing CPU to compare the characteristics revision time about the terminal user, which is stored in the storage, with the characteristics revision time stored in the message searching system, when the terminal connects to the message searching system, means for causing CPU to receive the characteristics stored in the message searching system when the characteristics revision time in the message searching system is after the characteristics revision time stored in the storage, and means for causing CPU to revise the characteristics stored in the storage.

(8) The recording medium of any one of above item (1) through (7), wherein the program further comprises revision detector for causing CPU to detect the fact that the user has revised the characteristics stored in the storage, and means causing CPU to transmit the characteristics stored in the storage to the message searching system, when the revision detector detects the fact that the characteristics has been revised.

(9) A recording medium which stores a program to be executed by CPU, the program comprises (a) storage for causing CPU to store process information that is read and processed by CPU, (b) memory for causing CPU to store the 36 position where the process information is stored in the storage, (c) input means for causing CPU to request the user to input the ID to identify the user of the terminal, (d) determination means for causing CPU to determine the position of the process information in the storage when processing the process information, (e) re-input means for causing CPU to request the user to input the ID of the user of the terminal again when the position of the process information stored in the memory is different from the position determined by the determination means, and (f) user determination means for causing CPU to determine that, when the ID inputted through the re-input means is different from the ID which was inputted through the input means, different user is using the terminal from the original user who inputted the ID through the input means.

(10) The recording medium of above item (9), wherein the program fdrther comprises means for causing CPU to request the user to input the user password through the input means, means for causing CPU to request the user to input the user password again through the re-input means when the position of the process information stored by the memory is different from the position determined by the determination means, and means for causing CPU to determine that the different user is using the terminal from the original user who inputted the ID through the input means through the user determination means, when the password inputted from the reinput means is different from the password which was inputted from the input means.

(11) The recording medium of above item (9) or (10), wherein the program to be executed by CPU is the process information.

37 (12) The recording medium of any one of above items (9) to (11), wherein the program further comprises means for allowing the communication between CPU and the information processor through the communication line, and means for causing CPU to inquire if the ID and the password which were inputted through the re-input means has been registered in the information processor, when it is determined by the user determination means that the different user is using the terminal from the user who originally inputted the ID.

Recording medium which stores the program for implementing the function of the message viewer 76, recording medium which stores the program for implementing- the function of the message manager 24 and recording medium which stores the program for implementing the message distributor 28 are used exclusively to manufacture the terminal 10, the message manager 24 and the message distributor 28, respectively.

According to the embodiments of the invention, appropriate display information which is suitable to the updated user characteristics can be selected and displayed on the terminal, even if the user characteristics change as time passes. Even when a plurality of users copy and use the same program, information can be displayed on the terminal, which suits to each user.

It should be noted that the present invention is not limited to the embodiments as described above. It is envisaged that various modifications and variations to the above described embodiments could be made without falling out of the scope of the present invention as defined from the claims.

38

Claims (8)

What is claimed is:
1. A terminal with a CPU for processing information, comprising:
a storage for storing operation information to be read and operated by said CPU; a memory for storing a location of said operation information in said storage; input means for inputting an ID for identifying a user of said terminal; determination means for determining a current location of said operation information in said storage;' re-input means for requesting said user to input said ID again when said location stored in said memory is different from said current location determined by said determination means; and user determination means for determining that a current user of said terminal is different from whom originally input said ID, when said ID input by said input means is different from said ID input by said reinput means.
2. A terminal according to claim 1, wherein said input means includes means for inputting a user password; said re-input means includes means for requesting said user to input said password again when said location stored in said memory is different from said current location determined by said determination means; and said user determination means includes means for determining that a user of said terminal is different from whom originally input said ID, when said password input by said input means is different from said password input by said re-input means.
39
3. A terminal according to claim 1 or 2, wherein said operation information is a program to be executed by said CPU.
4. A terminal according to any one of said claims 1 to 3, further comprising: means for communicating with a host computer through a communication line; and means for inquiring whether said ID and said password input by said re-input means have been registered in said host computer, when said user determination means determines that a user of said terminal is different from whom originally input said ID by said input means.
5. A host computer which communicates with a terminal through a communication network comprising: a first storage storing operation information to be used by said terminal; a memory storing a first data indicating a version of said operation information; first revising means for revising said operation information stored in said first storage; second revising means for revising said first data when said first revising means revises said operation information; receiving means for receiving a second data indicating a version of said operation information previously stored in said terminal; determination means for determining a necessity to update said operation information stored in said terminal based on said first data and second data; and transmission means for transmitting said operation information and said first data stored in said storage to said terminal when said determination means determines said necessity.
6. A host computer which communicates with a terminal through a communication network comprising: a first storage storing operation information to be used by said terminal; a memory storing a first data indicating a version of said operation information; first revising means for revising said operation information stored in said first storage; second revising means for revising said first data when said first revising means revises said operation information; a first transmission means for transmitting said first data to said terminal; and a second transmission means for transmitting said operation information and said first data stored in said storage to said terminal when said terminal determines that said information stored in said terminal needs to be updated, based on said first data.
7. A recording medium storing a program code to be read by a terminal communicating with a host computer through a communications network, said program code comprising: program code means for causing said terminal to store operation information; program code means for causing said terminal to store a first data indicating a version of said operation information; program code means for causing said terminal to revise said first data when revising said operation information; program code means for causing said terminal to transmit said first data to said host computer; program code receiving means for causing said terminal to receive from said host computer a revision information to revise said operation information, when said host computer 41 determines that said operation information needs to be revised based on said first data; and program code means for causing said terminal to revise said operation information based on said revision information received by said receiving means.
8. A recording medium storing program code to be read by a terminal communicating with a host computer through a communications network, said program code comprising: program code means for causing said terminal to store operation information; program code means for causing said terminal to store a first data indicating a version of said operation information; program code means for causing said terminal to revise said first data when revising said operation information; program code means for causing said terminal to receive a second data indicating a version of a operation information previously stored in said host computer; program code determination means for causing said terminal to determine said necessity to revise said operation information, based on said first and second data; program code receiving means for causing said terminal to receive from said host computer a revision information to revise said operation information, when said determination means determines that said operation information needs to be revised; program code means for causing said terminal to revise said operation information based on said revision information received by said receiving means.
GB9923656A 1996-05-10 1997-05-08 Terminal Expired - Fee Related GB2339313B (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP13969096 1996-05-10
US1945596 true 1996-06-11 1996-06-11
GB9824680A GB2328537B (en) 1996-05-10 1997-05-08 Message searching system and terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB0016318A GB2348308B (en) 1996-05-10 1997-05-08 Message distribution system

Publications (3)

Publication Number Publication Date
GB9923656D0 GB9923656D0 (en) 1999-12-08
GB2339313A true true GB2339313A (en) 2000-01-19
GB2339313B GB2339313B (en) 2000-08-09

Family

ID=27269548

Family Applications (1)

Application Number Title Priority Date Filing Date
GB9923656A Expired - Fee Related GB2339313B (en) 1996-05-10 1997-05-08 Terminal

Country Status (1)

Country Link
GB (1) GB2339313B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2368151A (en) * 2000-10-19 2002-04-24 One Zone Networks Determining access privilege to electronic data
WO2004047465A2 (en) * 2002-11-18 2004-06-03 Jens Hewerer Method and device for the transmission of messages

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0284924A2 (en) * 1987-04-02 1988-10-05 International Business Machines Corporation Data processing network with updating of files
EP0749081A1 (en) * 1995-06-12 1996-12-18 Pointcast Inc. Information and advertising distribution system and method
WO1997021183A1 (en) * 1995-12-08 1997-06-12 Bell Communications Research, Inc. Method and system for placing advertisements in a computer network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0284924A2 (en) * 1987-04-02 1988-10-05 International Business Machines Corporation Data processing network with updating of files
US5019963A (en) * 1987-04-02 1991-05-28 International Business Machines Corporation Data processing network with upgrading of files
EP0749081A1 (en) * 1995-06-12 1996-12-18 Pointcast Inc. Information and advertising distribution system and method
WO1997021183A1 (en) * 1995-12-08 1997-06-12 Bell Communications Research, Inc. Method and system for placing advertisements in a computer network

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2368151A (en) * 2000-10-19 2002-04-24 One Zone Networks Determining access privilege to electronic data
WO2002080084A2 (en) * 2000-10-19 2002-10-10 One Zone Networks Method of managing data
WO2002080084A3 (en) * 2000-10-19 2004-05-13 One Zone Networks Method of managing data
WO2004047465A2 (en) * 2002-11-18 2004-06-03 Jens Hewerer Method and device for the transmission of messages
WO2004047465A3 (en) * 2002-11-18 2004-08-19 Jens Hewerer Method and device for the transmission of messages

Also Published As

Publication number Publication date Type
GB9923656D0 (en) 1999-12-08 grant
GB2339313B (en) 2000-08-09 grant

Similar Documents

Publication Publication Date Title
US7305354B2 (en) Media asset management system
US8065185B2 (en) System and method of providing targeted advertisements from subscribers of directory services
US6651090B1 (en) Information processing apparatus, information processing method, and transmitting medium
US7493655B2 (en) Systems for and methods of placing user identification in the header of data packets usable in user demographic reporting and collecting usage data
US20070242626A1 (en) Methods and Apparatuses to Connect People for Real Time Communications via Voice over Internet Protocol (VoIP)
US20030093315A1 (en) System and method for using e-mail as advertisement medium
US5915093A (en) Computer network debit disk used for prepayment to transfer information from a central computer
US20040148191A1 (en) Digitized intellectual property archive with preferential method of transfer and routing
US20080167992A1 (en) Methods and systems for an accountable media advertising application
US7260837B2 (en) Systems and methods for user identification, user demographic reporting and collecting usage data usage biometrics
US20080177726A1 (en) Methods for delivering task-related digital content based on task-oriented user activity
US20090249359A1 (en) Apparatus and methods for widget intercommunication in a wireless communication environment
US20080040139A1 (en) Systems and methods for generation, registration and mobile phone billing of a music pod system
US20020178255A1 (en) Incentive program for a peer-to-peer network
US20020184096A1 (en) Portable terminal device for providing and obtaining advertisement information, advertisement providing method, advertisement obtaining method, advertisement distributing method and program therefor
US20070294401A1 (en) Providing collected profiles to media properties having specified interests
US20030229549A1 (en) System and method for providing for out-of-home advertising utilizing a satellite network
US20030028614A1 (en) Portable storage media and method of utilizing remote storage unit on network as auxiliary memory of local computer by using the same
US20030004834A1 (en) Online shopping method, online shopping system and computer program product for realizing the same
US20050125289A1 (en) Audience targeting system with segment management
US20040177370A1 (en) Storage and use of viewer preference data in a device remote from a set-top box
US20050246736A1 (en) Audience server
US20050021731A1 (en) Traffic flow analysis method
US20050125290A1 (en) Audience targeting system with profile synchronization
US8751461B2 (en) Systems for and methods of user demographic reporting usable for identifying users and collecting usage data

Legal Events

Date Code Title Description
732E Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)
PCNP Patent ceased through non-payment of renewal fee

Effective date: 20090508