WO2000018053A2

WO2000018053A2 - Communication method and system utilizing a specific communication code

Info

Publication number: WO2000018053A2
Application number: PCT/IL1999/000503
Authority: WO
Inventors: Neriel Paglin
Original assignee: Neriel Paglin
Priority date: 1998-09-18
Filing date: 1999-09-16
Publication date: 2000-03-30
Also published as: WO2000018053B1; AU5881699A; WO2000018053A3

Abstract

A communication system and method are presented for enabling keep in touch technique between an owner (4A) of at least one communication code and a receiver (4B) of the at least one communication code utilizing a manager utility (6). The code owner (4A), or any authorized person, creates a data record containing information belonging to the code owner, and feeds this data record to the manager utility (6). The manager utility (6), upon receiving the data record, stores it in a database (7) and assigns the at least one communication code associated with at least said predetermined part of the stored information to the data record owner (4A). Upon receiving the at least one communication code from the code receiver (4B), the manager utility (6) provides him with at least said predetermined part of the stored information of the code owner (4A). Upon detecting that changes have been made to the data record of the code owner (4a), the manager utility (6) operates toupdate the code receiver(4B).

Description

Communication Method and System Utilizing a Specific Communication Code

FIELD OF THE INVENTION

The present invention is in the field of communication techniques and relates to a communication method and system utilizing a specific communication code.

BACKGROUND OF THE INVENTION

When people meet for business purposes, it is commonly practiced to exchange business cards containing relevant information for future contacts. A business card usually contains data pertaining to the following: name, occupation, company, position and addresses relative to communication systems such as mail, phone, fax, e-mail and the like.

Business cards gathered from other parties are usually kept for the purpose of exchanging information or in the expectation of performing various transactions. The assumption is that the parties involved will use the addresses for establishing future relations that may result in business dealings. Since the information held in the business cards is of importance, they are carefully filed and ordered. Usually, the data of the cards is painstakingly typed, or scanned, to create computer files that are easier to maintain. It is needless to say that the handling and filing of business cards is cumbersome and time-consuming. As time passes, it is usual for changes to occur in at least some of the data contained in a business card. Although names tend to remain the same, positions, occupations and many kinds of addresses are modified quite often. For example, a person may be promoted to a higher position in another division, may leave for another company or, as frequently occurs, a phone, facsimile or e-mail address is modified. These are all "dynamic" changes that take place in everyday life.

Thus, data printed on the business card remains valid only until changes take place in any one of the many data it displays. Therefore, as a result of these changes, it often becomes difficult to communicate with other parties. Such changes compel the owner of the business card to print a new version of the card, and then to distribute it to his contacts. It would therefore be advantageous to all sides to provide the receiver of a business card with the latest edited version of the card, whenever such editing occurs. However, such an endeavour would require the card owner to send a new card to all his previous contacts each time modifications are made, assuming that it were possible to recall to whom they were distributed originally, and further assuming that the addresses of these receivers have not undergone any change themselves. In practice, both assumptions make such a task only partly achievable, at best. Even if so, the data receiver would still be left with the burden of filing the edited versions of the cards as they arrive.

Quite frequently, names and addresses are published in listings or in public, such as in telephone books and in various advertisements, without any knowledge regarding those who had initially been receivers of the data. In such instances, it is completely impossible to even try to approach the receivers, and there are no easy ways to notify those receivers of the fact that changes have occurred.

Various personal communication techniques have been developed. U.S. Patent 5,717,863 discloses a communication technique aimed at timesaving in retrieving personal information for real-time processes such as a conference call. The technique utilizes a business card in the form of a data structure comprising information commonly found in business cards, and the particular user's PC conference connection address. To contact a certain person, a user must search for the addressed person's name in the list and, upon finding him, the user will receive a "card image" on his display. It is evident that this technique suffers from the following drawbacks. On the one hand, it obliges the user to establish an on-line connection with a server containing the data structure for searching. On the other hand, it provides no privacy for a card owner, since once he has designed and stored his "business card image" in the data structure, his name appears in the list, and anyone can have access to unload his personal data.

Another communication technique is proposed by the Internet site "PlanetAll", and is based on managing a personal address book. PlanetAll acts as an Internet Service Provider owning a central database for maintaining a personal address book. Each subscriber to PlanetAll is allowed to create his personal address book in the central database. Upon mutual consent of a first subscriber and a second subscriber to PlanetAll, the contact particulars of the first subscriber are transmitted from his address book to the address book of the second subscriber. Additionally, the address book of the second subscriber is automatically updated with the relevant changes whenever they occur in the address book of the first subscriber. All these address books reside within the central database belonging to PlanetAll. Thus, each PlanetAll subscriber has his personal address book maintained at the Service Provider's side. Consequently, to gain access to his personal address book, the subscriber needs to establish an on-line connection with the Service Provider. Moreover, to obtain permission of one of the subscribers for the automatic transmission of his contact particulars to another subscriber, the Service Provider has to invoke a specific procedure. With the Internet, the User Resource Locator (URL) is typically utilized to present up to date information to receivers. This technique suffers from numerous drawbacks, as it always requires the active intervention of the user, the time consuming process of getting on-line, accessing addresses and waiting for the results.

The Internet site "ICQ" proposes a communication technique developed by Mirabilis Ltd. This technique utilizes a Client Program and a central database, and is aimed at facilitating on-line communication (e.g., Internet Chats, messaging, etc.) between subscribers to ICQ. Once a "first subscriber" to the Internet downloads the ICQ Client Program to his personal computer and thereby becomes a subscriber to ICQ, each time he goes on-line, he will be provided with an indication that a "second subscriber" is also on-line at that time. This "second subscriber" (or more than one subscriber) is previously selected (chosen) by the "first subscriber" and recorded as associated with the "first subscriber" for further indications to the "first subscriber". Additionally, ICQ allows any subscriber thereto to create and operate his own personal address book. This address book includes personal data of other subscribers to ICQ, per the choice of the owner of the address book. The address book is created at the subscriber side (i.e., in his personal computer), and can be updated with any changes in the personal data of those subscribers who are recorded in the address book.

However, to perform this updating, the address book owner needs to go on-line for accessing the ICQ central database. In other words, the updating procedure is carried out in response to a specific request from the address book owner. This technique does not allow for managing the personal address books of ICQ subscribers by the central database. As a result, any subscriber, before using personal data recorded in his address book for contacting a corresponding subscriber, has to check the actuality of data stored in the address book by establishing an on-line connection with the central database through the Internet.

SUMMARY OF THE INVENTION

There is accordingly a need in the art to improve communication techniques, in particular, so-called "keeping in touch" techniques, by providing a novel communication and updating method and system utilizing a communication code.

It is a major object of the present invention to provide such a method that allows any receiver of a communication code to obtain corresponding information belonging to the owner of this communication, and successfully contact the code owner in a very simple and convenient way, whenever the code receiver desires, even if a significant amount of time has passed from the date he received the code.

It is a further object of the present invention to provide such a system which in most cases frees both the code owner and the code receiver from the need to purchase any equipment in addition to that usually provided at an individual's home or office.

It is a still further object of the present invention to allow the code owner to select what information he wishes to deliver and to whom, and keep the information receivers up to date of all changes introduced by the code owner to the information.

The present invention takes advantage of the fact that the world is undergoing a so-called "communication revolution". More people worldwide are provided with personal Digital Communication Devices (phone device, computers, pagers, PDAs) connected to one or more networks. Accordingly, an individual typically has several personal communication addresses that have to be maintained. Furthermore, each individual has to manage a growing list of addresses of persons with whom contacts have to be maintained. Each record of individual's personal data, typically presented on his business card contains increasing amount of information, such as his telephone number, mobile phone number, fax number, E-mail and mailing addresses, etc. All this information has to be stored, manually entered into the individual's personal address book, and manually updated later on in each of his personal digital communication devices. With this technique, information in the personal address book is definitely rarely up to date, because the details of this information is dynamically changing. Keeping the information stored in personal address books up to date in an automatic and transparent manner to the user, is a very important component of the entire communication process.

Thus, the main idea of the present invention consists of the following. Most people today have business cards, especially those performing specific functions in companies. People exchange their business cards whilst meeting each other and wishing to communicate in the future. A card owner desires a card receiver to whom he has delivered his business card to have a simple way of "keeping in touch". To this end, an individual or any other authorized person creates the individual's own data record containing his personal information or any other information he wishes to deliver to others, for example, that typically contained in a business card: name, position, mail address, fax and telephone numbers, Email, etc. This data record may comprise an attachment, for example a file containing a text and/or picture. The data record, or the address where this data record is maintained, is stored in the database of a manager utility. The individual receives a unique communication code generated by the manager utility, thereby becoming the "code owner". The code owner applies his own communication code to his business card, letter-head, or the like, and delivers it to people with whom he wishes to "keep in touch". An individual who was given the unique communication code (for example, issued on the business card of the code owner) becomes the "code receiver". The communication code serves as the address of the specific data record maintained in the database of the manager utility. Hence, the code receiver may use this address to obtain the code owner's information entered in the corresponding data record. Obviously, an individual may be the owner of several communication codes corresponding to different data records belonging to him.

The code owner, as well as the code receiver, typically has at least one personal communication unit at his disposal, for example, a personal computer or a phone device. Such a personal communication unit is typically a node of at least one popular network. Indeed, every phone device is associated with a Telephone Company, while almost every computer is connectable to the Internet by means of an Internet Service Provider (ISP). The telephone network may be "Public Switched Telephone Network" (PSTN), or the "Integrated Service Digital Network" (ISDN). The main principles of these types of telephone networks are known per se, and therefore need not be described in detail, except to note the following. PSTN is a communication common carrier network that provides voice and data communication services over switched lines. ISDN is a type of digital end-to-end telecommunication network, that supports multiple services, including voice and data. ISDN lines can transmit digital data as well as voice without a modem. ISDN is used in public and private network architectures.

The term "manager utility " used herein signifies software and or hardware installed at remote communication devices connectable to each other through a communication link. This utility is capable of utilizing hardware and software typically installed in the corresponding communication device for creating and/or managing a database in a memory of this device. These communication devices may be either personal communication devices, or personal communication devices and server utilities of corresponding networks. The system allows each code owner to be aware of all his associated code receivers. Additionally, the system, on the one hand, allows the code owner to keep his data record up to date, and, on the other hand, automatically updates the registered receivers associated with this specific code with all the changes made. The system enables the code receiver, as well as the code owner, to create their own private databases. Each private database may be stored in the memory of the personal communication unit of the respective user, in the central database or in both.

To enjoy all the advantageous features of the present invention, the code owner, as well as the code receiver, should have a predetermined software package ("User Program") installed in his personal communication unit, for example by downloading this software package from the network (e.g. the Internet). If a phone device serves as a communication unit, it should be of the so-called "smart type" equipped with a certain programming/interface utility, for example in the form of a chip with an embedded application, such as a known Single In-line Memory Module (SIMM). Such a smart-type phone device can be used as both a phone and portable computer capable of running a suitable application, which is the predetermined "User Program" for the purposes of the present invention.

The manager utility may be a central database manager associated with the network's server. In this case, in order to store the data record in the central database and to receive the communication code assigned to him by the central database manager, the code owner connects to the central database manager via the network. The code receiver, in order to obtain the information presented on the received business card, in the most convenient and available manner, accesses the central database manager from his personal communication unit through the network. The manager transmits the information included in the requested data record to the code receiver, and registers the code receiver in the central database as a receiver associated with this specific code owner.

The private database may be maintained only at the corresponding user's side (i.e., in his personal communication unit). In this case, the User Programs, installed in the communication units, by themselves may serve as the manager utility.

In a case that some of the users prefer to have their private databases maintained in their personal communication units only, and others prefer to utilize the central database for this purpose, the User Programs, together with the central database manager, serve as the manager utility.

There is thus provided according to one aspect of the present invention, a communication method between an owner of at least one communication code and a receiver of said at least one communication code utilizing a manager utility, the method comprising the steps of: at the code owner side:

(a) creating a data record containing information belonging to the code owner, and feeding said data record to the manager utility,

(b) receiving the at least one communication code associated with at least a predetermined part of the information included in said data record; at the code receiver side, upon receiving said at least one communication code:

(c) feeding said at least one communication code to the manager utility;

(d) receiving data representative of said at least predetermined part of the information contained in the data record of the code owner; at the manager utility: (e) upon the receipt of said data record, storing it and assigning said at least one communication code to the data record owner;

(f) upon the receipt of said at least one communication code from the code receiver, transmitting at least said predetermined part of the stored information of the code owner to said code receiver.

Preferably, the code receiver and the code owner have their personal communication devices, which are nodes of a network. According to one embodiment of the invention, the manager utility is a central database manager associated with a server utility of this network. The central database manager belongs to either the network's server or to an additional Service Provider (SP) coupled to the network's server. According to another embodiment of the invention, User Programs installed in the personal communication devices constitute the manager utility.

According to another aspect of the present invention, there is provided a communication system utilizing a network having a server utility and communication units associated with different network subscribers, the system comprising a central database manager associated with said server utility, wherein the central database contains data representative of a plurality of data records, each data record containing information belonging to the corresponding subscriber and being associated with at least one communication code assigned to at least a predetermined part of the information of the corresponding subscriber who is the owner of said at least one code; the central database manager comprises: a communication utility that receives data addressed to the central database and transmitted through said network, and transmits data from said central database to a corresponding one of said communication units through the network; an identification utility coupled to said communication utility for identifying said data addressed to the manager as a certain request to the central database; and a central processor utility that is coupled to the communication utility and to the identification utility, and is associated with said central database, the central processor utility being responsive to the request data for generating data representative of said at least predetermined part of the information included in the corresponding data record, when the request data is representative of said at least one communication code, and, when the request data is representative of the data record, for storing the information included in the data record in the central database and assigning said at least one communication code to the corresponding subscriber. The network may be either a computer or a telephone network, or a combination of both. The subscriber's communication unit may be a personal computer, a phone device or the like.

The data record may have more then one corresponding communication code. For example, the code owner designs his data record having several information parts, and decides to deliver different parts to different persons. This is implemented by assigning to each information part its own communication code. More than one communication code could be applied to the same business card. For example, one such communication code may be a so-called "business code", associated with the position of the code owner in a company he works, and the other communication code may be a so-called "personal code", associated with the personal data of the code owner, irrespectively of his position in the company.

According to yet another aspect of the present invention, there is provided a communication system for providing communication between first and second subscribers to a network, the system comprising: a personal communication unit of the first subscriber and a personal communication unit of the second subscriber, the first and second units being connectable to each other through the network; and a manager utility including a first software package installed in the first personal communication unit and a similar, second software package installed in the second personal communication unit, wherein - l i ¬

the first software package is responsive to data coming from the network and addressed to the first communication unit, so as to selectively generate corresponding notification messages to the first subscriber, to manage a private data base of the first subscriber, and to transmit predetermined data from the private database of the first subscriber to the second subscriber, and is responsive to data entered into the personal communication unit of the first subscriber to assign at least one communication code to the first subscriber; the second software package is responsive to data coming from the network and addressed to the second communication unit, so as to selectively generate corresponding notification messages to the second subscriber, to manage a private data base of the second subscriber, and to transmit predetermined data from the private database of the second subscriber to the first subscriber, and is responsive to data entered into the personal communication unit of the second subscriber to assign at least one communication code to the second subscriber.

BRIEF DESCRD7TION OF THE DRAWINGS

In order to understand the invention and to see how it may be carried out in practice, a preferred embodiment will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:

Fig. 1 is a schematic block diagram of the main components of a conventional communication system;

Fig. 2a is a schematic block diagram of the main components of a system, constructed according to one embodiment of the invention;

Fig. 2b is a schematic block diagram of the main components of a system, constructed according to another embodiment of the invention; Fig. 3 schematically illustrates the main utilities of a subscriber's communication unit and of a central database manager used in the system of either of Figs. 2a and 2b;

Fig. 4 is a schematic illustration of the main operational principles of the system of either of Figs. 2a and 2b; Figs. 5a and 5b illustrate a flow diagram of a part of the operation of the system of either of Figs. 2a and 2b;

Figs. 6a and 6b illustrate a flow diagram of another part of the operation of the system of either of Figs. 2a and 2b; Fig. 7 illustrates yet another part of the operation of the system of either of

Figs. 2a and 2b;

Fig. 8 is a schematic illustration of an example suitable for the design of a central database in the system of either of Figs. 2a and 2b;

Figs. 9a to 9c schematically illustrate the main principles of managing central and private databases in the system of either of Figs. 2a and 2b;

Fig. 10 is a schematic illustration of a communication system, constructed according to yet another embodiment of the invention;

Fig. 11 is a flow diagram of the operation of the system of Fig. 10, initiated by a code owner; Fig. 12 shows a flow diagram of the operation of the system of Fig. 10, initiated by a code receiver

Fig. 13 is a schematic illustration of yet another embodiment of the invention.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT Referring to Fig. 1, there is illustrated a conventional communication system, generally designated 1, representing a network formed by Service Providers (SP) sides 2 and a plurality of subscriber sides 4, each connected to the SP side 2 through a communication link. Such a network may be a computer network, for example the "INTERNET", or a telephone network, the SP side 2 being associated with Internet Service Providers or Telephone Companies, respectively. Each server 3 of the SP side 2 is typically a central computer station representing a local area network (LAN), and is typically connected to a plurality of remote servers (LANs) 3 through the communication link. Each such server 3 is associated with various databases, which can be accessed by each subscriber of either server 3. To receive a specific data record contained in the database, the user at the subscriber side 4 establishes an on-line connection with his local SP side 2, in accordance with a protocol between a so-called "Server Program" and "Client Program" installed at the server and subscriber sides, respectively. The principles of the network's construction and operation are known per se.

Fig. 2a illustrates the main components of a communication system, generally designated 10, constructed and operated according to one embodiment of the invention. Same reference numbers are used for identifying those components, which are identical in the systems 1 and 10, to facilitate understanding. As shown, the system 10 comprises the network 1 as its constructional part, and a manager utility 6. In this specific example, the manager utility 6 functions actually similar to one of the servers 3 being coupled to the SP side 2 through a communication link, and manages a central database 7. Alternatively, although not specifically shown, one of such servers can function as the manager 6 managing the database 7. In the system 10, the subscriber side 4 is composed of so-called "owner" and "receiver" sides 4a and 4b, respectively.

The terms "owner" and "receiver" signify different network's subscribers (users) who are, respectively, the owner and receiver of a specific communication code Cco_m- Practically, each subscriber can be the owner with respect to one specific communication code, and the receiver with respect to another specific code. Such a communication code C_Co_m belongs to the code owner, and is assigned to at least a predetermined part of information belonging to the code owner and included in a data record designed by him or by an authorized person on his behalf. In this specific example, the data record is maintained at the manager side 6 (i.e., in the central database 7), as will be described more specifically further below. The system 10 is aimed at facilitating so-called "keeping in touch" between the code owner and the code receiver by utilizing this specific code C_COm-

The communication code C_COm presents access to the central database manager 6. This access results in the automatic transmission of the information contained in the corresponding data record (or a predetermined part of the data record) from the central database to a private database of that user who has accessed the manager side 6 by means of the communication code C_com, as will also be described more specifically further below.

Fig. 2b illustrates a communication system 100 according to another embodiment of the invention. The system 100 is constructed generally similar to the system 10, but comprises a so-called "distributed database". In other words, each local server 3 owns a part of the central database 7a, for example containing those data records or parts of data records which are associated with its local subscribers. Referring to Fig. 3, the subscriber side 4a (or 4b) comprises a communication device 8 that has inter alia the following utilities: a communication utility 10 (e.g., modem), an input means 12 (e.g., keypad, microphone), a memory 14, an indication means 16 (e.g., display, speaker), and a central processor utility (CPU) 18. The owner and receiver sides 4a and 4b are the subscribers of the network 1 and are associated with either the same server or different remote servers of the SP side 2. The communication device 8 may be a personal computer. In this case the network's "Client Program" is duly installed in the CPU 18, and a specific software package, a so-called "User Program", is either already installed or can be easily installed in the CPU 18, for example by means of downloading the program through the network (e.g., the Internet). This software package operates in accordance with the principles of the present invention, as will be described more specifically further below. If User Program is installed in the communication device 8, the User Program together with the central database manager serve as the manager utility.

Alternatively, the communication device 8 may be a phone device of the so-called "smart type", namely equipped with a programming/interface utility for running the "User Program" (application). The provision of such a programming/interface utility enables the phone device to be used as both the phone and portable computer or personal digital assistance (PDA). If a wireless phone device is considered, such a programming/interface utility may be in the form of a chip with an embedded application to be mounted in the phone device, such as the known "Single In-Line Memory module" (SIMM). In the case of a regular "wired" telephone device, a separate electronic unit may be interconnected between the communication link and the telephone device. The communication utility of the phone device is provided with an identification means, the so-called "Caller ID" function.

When identifying that received signals come from the manager 6, the communication utility, instead of generating a call (i.e., actuating the phone ringer) actuates the CPU 18 for running the "User Program". Alternatively, a separate data link may be provided for transmitting data from the manager 6 to the phone device 8. In other words, the present invention may be used with either the "Public Switched Telephone Network" (PSTN) or the "Integrated Service Digital Network" (ISDN). Thus, the CPU 18 of the communication device 8, which may be a smart-type phone or a personal computer, is preprogrammed with the specific software package ("User Program"). This software package actually presents a "Client Program" associated with a certain Application Program Interface (API) installed in the CPU 22 of the manager side 6. The "User Program" is capable of creating and/or managing a private database in the memory of the device 8, as will be described more specifically further below. It should be noted that if a simple phone device is used having no such programming/interface utility, relevant data may still be transmitted from the server utility to this phone device being presented to the user as text or voice messages.

As further shown in Fig. 3, the manager 6 is typically a server computer station, which comprises inter alia the following utilities: a communication utility 20, a CPU 22 having an appropriate application program interface (API), and a connection utility 24. The communication utility may be of a so-called "MODEM POOL" type, i.e. comprising a large number of modems having a Caller ID detection feature so as to identify the subscriber's communication unit that has initiated the connection. Figs. 4 and 5a-5b illustrate a part of the operation of the system 10 initiated by a user A at the subscriber side 4a of the network 1 in order to become the owner of a communication code C_Com and, optionally, to subscribe to the central database manager 6. User A accesses the manager side 6 either by inputting an address code

5 Co of the central database manager 6 via the network's "Client Program" installed in his personal computer, or by dialing the manager's phone number Co from the user's phone device (step 30). Generally speaking, this code Co is the network's address of the manager 6. The on-line connection between the subscriber side 4a and the manager side 6 is established through the SP side 2 (step 32). The modem

10 20 receives the incoming data and actuates the connection utility 24 (step 36). The received data (e.g., Co) presents requested data to be identified by the connection utility 24 (step 38). The access through the code Co signifies that user A at the side 4a wishes to carry out the following:

- create his own data record (DR)A to be stored in the central database 7, 15 and obtain his communication code C _«; and, optionally,

- subscribe to the manager side 6 for creating and/or managing a private database (PD)A in the memory 14 and for obtaining his own private code (A)

*— priv-

20 Once receiving the private code C⁽ p_rj_v assigned to him, user A will use this private code for accessing the manager 6. In response to the receipt of the code Co, the CPU 22 presents a user's program interface to the communication unit 4a (step 40), thereby enabling user A to create the data record (DR)A (step 42) and to transmit it to the manager side 6 (step 44) to be stored in the central database 7

25 (step 46). This having been accomplished, the CPU 22 assigns a unique communication code C^(A) _com to this specific user A (step 48) who thereby becomes the "code owner". The communication code C ^A) _COm may be associated with the entire information included in the data record (DR)A. Alternatively, the data record may contain several portions of information, each associated with a different communication code, as will be described more specifically further below.

It should be noted that, theoretically, in order to create such a data record in the central database and to receive at least one communication code, the user does not necessarily have to use the on-line means. He may design the data record and transmit to the manager side 6 in any other known manner (e.g., mail, fax), and, accordingly, may receive a notification message containing at least the communication code via mail or facsimile transmission. However, as indicated above, every personal phone device, as well as every personal computer, is typically a node of a network, either a telephone network or a computer network. It is not an exaggeration to say that most people have at their disposal at least one of such nodes.

The user's program interface also presents an option to the user to register as a subscriber to the central database manager 6 (step 50). If the user chooses to subscribe to the manager, he actuates a corresponding key, e.g. he "clicks" the appropriate position on the displayed representation of the program interface. For this purpose, his personal communication device has to be loaded with the "User Program" (step 51). If the communication device 8 is a personal computer and if such a software package has not yet been installed therein, the software package may be downloaded in response to the key actuation (step 52). As indicated above, the "User Program" is capable of creating and managing a private database (PD)A in the memory 14 (step 54), or of managing an existing private database, if any.

Additionally, the choice to subscribe to the central database 7 results in that the CPU 22 generates a unique private code C _p™ and assigns it to this specific user A (step 56). User A becomes the owner of both the communication code C com and the private code C^(A) _pri_V. User A may deliver the communication code C _Com to other parties (code receivers), and may apply the private code C _priv to amend (edit) his data record in the central database 7.

A user B who was given the communication code C^(A _COm is considered as the code receiver. As further shown in Fig. 4 and is illustrated in a flow diagram of Figs. 6a and 6b in a self-explanatory manner, user B, upon receiving the communication code C _com (step 60), could apply this code C^(A) _com to carry out the following:

- access the manager 6 (step 62) to request and obtain information included in the user's A data record (DR)_A or a predetermined part thereof, as the case may be (step 64); and, optionally, upon deciding to subscribe to the manager 6 (step 72)

- create his private database (PD)_B (step 76), and have the requested information included in the data record (DR)_A or in the part thereof stored in the private database (PD)_B; and/or

- create his own data record (DR)_B (step 78) to be stored in the central database 7, and obtain unique communication and private codes C com and C priv assigned to him (step 80).

The manager 6 operates in the following manner. Upon identifying the requested data, i.e. the communication code C _Co_m (step 64), the manager 6 transmits the requested information included in the data record (DR)_A from the central database 7 to the communication unit of user B (step 66). CPU 22 determines whether user B is a registered subscriber to the central database manager 6 (step 70), for example, by allowing user B to enter his subscriber's information (e.g., C_pri_v or any other client's LD) through the user's program interface. If no such data is entered, the user is invited to choose whether or not to subscribe to the manager 6 (step 72). To this end, the user's program interface includes all the necessary keys (icons) to be actuated by the user at his choice.

If user B decides to subscribe to the central database manager 6, then, depending on whether the "User Program" has or has not yet been installed in the personal computer 8 (step 73), the private database (PD)_B is either directly created (step 76) or created after the "User Program" is downloaded (steps 74 and 76), respectively. Step 76 is optional, and necessary in cases when either no private database exists in the memory of the communication unit or the subscriber does not intend to use any existing private database for the purposes of the present invention (i.e. "keeping in touch").

Then, user B creates his data record (DR)B and transmits the same to the manager 6 to be stored in the central database 7 (step 78). Here, a communication code C co_m and a private code C p_ri_V are assigned to user B and transmitted to him through the network (step 79). Thus, user B receives his communication and private codes C com and C pnv

The manager 6 registers the subscriber's information of user B (e.g., C co_m, or any other relevant information per the user's preferences) as the receiver of the information included in the data record (or a predetermined part of this data record) of user A (step 80). Additionally, the CPU 22 of the manager 6 automatically generates a message to user A indicative of that user B has requested specific personal data of user A by means of the communication code C _Com- This message is transmitted to a specific communication unit of user A (per his preferences) for updating a "Mailing List" of user A in his private database (PD)_A (step 81). The "Mailing List" contains information regarding those subscribers who have requested and obtained personal data included in the data record (DR)A or a corresponding part thereof. A manner in which this message may be transmitted to user A will be described more specifically further below. Hence, each data record is associated with its owner, its corresponding "Mailing List" and corresponding communication code C_COm (i.e., the communication code of the owner).

It should be noted that user A could add an item relating to a specific user into his "Mailing List", without having this item received through the processing of the communication code C^(A _COm fed by this specific user. It should also be noted that every subscriber may choose where to have his "Mailing List" stored, namely in his private database, in the central database or in both these databases.

To enable user A to identify user B, the corresponding message contains certain personal information of user B, specified as his preferences for information to be allowed for transmission in such cases (i.e., name, Email, phone number, C c_0m, etc.), as will be described further below with reference to Fig. 8. If user B, for any reason, declines the option to subscribe to the central database 7 or to at least advise any information to be included in the "Mailing List" of user A, the manager side 6 may, upon successfully identifying the network's address of the communication unit of user B, register this address as associated with the receiver of the personal data of user A (step 68).

Turning now to Fig. 7, the private code C _priv of user A enables him to access the manager side 6 from any communication unit, which is the node of the network 1 (step 82). For this purpose, the manager 6 operates in the following manner. Upon receiving the private code C p_ri_V and identifying it as requested data (step 84), the manager 6 provides user A with the appropriate user's program interface and displays the data record (DR)_A in a manner which allows the amendments to be made thereto (step 86). When user A completes the amending procedure (step 88), the CPU 22 operates to register these amendments in the central database 7 (step 90). Hence, the "old" data record of user A duly stored in the central database 7 is replaced by a "new" one. Optionally, the CPU 22 also maintains the old data record, and/or assigns a so-called "Time Stamp" to the changes made. It should be noted that, if the user's data record is maintained in his personal communication device, the user can make all necessary changes to this data record off-line, and then transmit these changes to the central database manager by using the user's private code C_pri_V.

The CPU 22 now operates in a manner to correspondingly update the data records residing with all the receivers of the communication code C _Com, who have requested and obtained the corresponding information and are therefore registered in the central database 7 as associated with the amended data record (i.e. "Mailing List" of user A). The updating procedure may be implemented in the following manner.

A message, which is indicative of the changed data record of the code owner and is addressed to a specific communication unit of the code receiver, is automatically generated and transmitted to the SP side 2 (step 92). There, the message is kept until the appropriate utility detects that an on-line connection between the addressed communication unit and the SP side 2 (its local server) is established for any purposes (steps 94 and 96). Upon detecting the existence of such an on-line connection, the SP side 2 transmits the message to the addressed communication unit (step 98). To this end, CPU of the SP 2 and the CPU 22 of the manager 6 typically operate in accordance with a certain "protocol". The delay of transmission of such messages until the specific user initiates the on-line connection for any purposes, is aimed at preventing him from additional expenses associated with the on-line updating procedures.

According to one of the functions of the software package (i.e., "User Program") duly installed in the subscriber communication unit 8, this software is responsive to messages coming from the manager 6 (through the SP side 2) for replacing the old data record stored in the private database by the amended one or adding the amended data record to the old one (step 100).

It should be noted that time schedule for automatic message generation may be specified by a subscriber himself. For example, a corresponding message may be generated immediately after detecting any changes in or any request for information contained in the data record. Alternatively, such messages may be generated periodically, the time interval being preset by the subscriber. The periodic automatic updating procedure may be initiated by software installed either at the manager side ("Server Program") or at the subscriber side ("User Program"). If User Program initiates the updating procedure, this updating may be selective with respect to subscribers whose information are stored in the user's private database. For example, the User Program may generate a query message to the central database asking whether any changes have been made to data records belonging to one or more selective subscribers.

Fig. 8 illustrates one possible example of the design of the central database 7. According to this specific example, the central database 7 is composed of a plurality of fields (or groups of fields), e.g. ten groups Fi-Fio. The first group F_1? so-called "Subscribers' Information", contains data representative of the registered subscribers Sι-S_m to the manager 6. Group F₂ contains data representative of the subscriber's preferences per choice of each specific subscriber, for example, the network's address of a personal communication unit to which messages should be addressed, or information allowed to be transmitted to other subscribers as an indication that this specific subscriber has requested their personal data. The third group F₃ contains personal data records of the registered subscribers. Each data record may comprise N different information portions. Consequently, N different communication codes may be assigned to each one of m subscribers and included in the field F₅. Group F4 contains private codes of the registered subscribers. Group F₆ contains information about those subscribers who have requested and obtained the personal data (or a specific part thereof) of each specific subscriber, i.e., "Mailing List" of the specific subscriber. As for the requested personal data of various subscribers duly transmitted to a specific subscriber per his request ("Restoring List"), these data are included in the group F .

The maintenance of "Restoring Lists" in the central database is optional, and is performed in accordance with the choice of each specific subscriber. However, it is important to note that, if a specific subscriber selects this function, he will be able to restore his private database when something happens to the original one maintained in the memory of his personal communication unit (i.e., his private database). Groups Ε% and F₉ contain data representative of, respectively, the time of the changes made to the personal data records ("Time Stamp") and the time of the last updating procedure executed with respect to each subscriber. Group F10, a so-called "Dynamic Information", presents data indicative of a "new" address for communication (e.g. phone number, Email, etc.) of a specific subscriber introduced by him (or by authorized person) to be currently relevant.

The entrance of the new address in the dynamic field may be caused by the fact that this specific subscriber is going to be available at this address within a certain period of time, and intends to return to the "main" address indicated in his data record (Groups F₂ and/or F₃) when this period of time expires. Additionally, the subscriber may specify only some of his associated code receivers appearing in his "Mailing List" to be updated with these temporary changes. This may be implemented in the following manner.

When a specific subscriber enters any temporary address for communication into his associated dynamic field, the central database manager (i.e. CPU 22) generates a query like this: "To Update Everybody from Mailing List?". If the subscriber's answer is "NO", he receives his Mailing List displayed and selects (e.g. marks) those code receivers whom he wishes to be updated. If the subscriber answers "YES", the central database manager operates to update all of those subscribers that appear in the Mailing List of this specific subscriber. Consequently, when a registered subscriber Si wishes to communicate with another subscriber S₂ from his "Restoring List", the manager operates to check whether there exists any temporary address in the dynamic field of subscriber S₂. If so, the manager determines whether the area code tariffs of the "new" address, recorded in the dynamic field, and the "main" address, recorded in the "Restoring List" of subscriber Si, are equal or different. If the area code tariffs are different, the manager generates a corresponding notification massage to subscriber Si, and asks him whether to perform the connection (e.g. dialing) or not.

As indicated above, more than one communication code may be assigned to the same subscriber. These codes may be associated with different parts of the same data record or with different data records belonging to the same subscriber. In other words, the receivers of different communication codes of the codes' owner will have access to different parts of the information associated with this code owner. For example, one such communication code may be assigned to relevant data associated with the position of an individual in a company, so-called "business code" C^(bus)com. The other communication code, so-called "personal code" C^(per _om, is representative of the individual's personal information irrespective of his job position.

Reference is now made to Figs. 9a-9c illustrating the main principles of the above-mentioned concept. As shown in Fig. 9a, the central database 7 contains a plurality of different data records, generally at (DR)i, each corresponding to a different communication code. A user ORi is the owner of a personal communication code C _com and a private code C ¹ _pri_V, both associated with his data record (DR);.

The code owner ORi is also an employee of a company and represents a specific position there. The company owns a group (DR)j of data records (DR)i, each data record (DR); being associated with one of the company's employees (i.e. a specific position). Consequently, a business communication code C _com is assigned to each data record within the group (DR)_j, and the company is the owner 0₂ of these business communication codes. The company (i.e. the owner 0₂) also owns a corresponding number of private codes C⁽²⁾ _pri_V (or the single private code) for editing data contained in the data record group (DR)j.

As further shown in Fig. 9a, the code owner ORi may also be a receiver of several communication codes given to him by other parties either through personal or business contacts. According to the present example, such an owner/receiver ORi may has received a business code Cx from party X, a personal code C_Y ^(pers) from party Y and both such codes C_z ^(bus) and C_z ^(pers) from party Z. In a similar manner, the owner/receiver ORi delivers his business code C com, personal code C^(p _Com, and both business and personal codes to code receivers Ri, R₂ and R3, respectively. Figs. 9b and 9c illustrate in a self-explanatory manner a private database

(PD)i of the owner/receiver O/Ri and a private database (PD)j of the owner 0₂ (i.e. company), respectively. When the individual, constituting the owner/receiver O/Ri, leaves his position with the company (owner 0₂), the communication code C _com representative of this specific position in the company remains with the company, and will be assigned to another employee filling this specific position. Additionally, all registered business connections created during the activity of the specific employee O/Ri with the company (particulars received or transmitted to and from the data record associated with the business code C co_m) remain in the ownership of the company. On the other hand, all the contacts of the individual O/Ri may remain in his possession. In other words, each code owner (individual or company) will have the option to keep track of those parties (code receivers) who requested his/its data record or provided him/it with their data records. The owner O/Ri (i.e. individual) and the owner 0₂ (i.e. company) use their different private codes to keep the corresponding data records (DR)i and (DR)ι, respectively, up to date.

As to the parties Ri, R₂ and R₃, who received the business code belonging to a specific position in the company, they will always be able to get in contact with the person currently manning this position in the company, whenever the receiver desired, even if personnel relocations have occurred in between. In parallel, it will always be possible for those parties who received the personal code of a specific individual to reach him. It is a typical case that the private database of the employee is maintained in his personal communication device, while the private database of the employer (company) is maintained in the company's respective utility.

The advantages of the present invention are thus self-evident. The network's subscriber obtains the software package ("User program") installed in his communication unit (PC or phone device), thereby becoming a registered subscriber to the central database manager 6. If a telephone network is considered, the user's phone device has to be equipped with an appropriate programming/interface utility, the provision of which enables the phone device to be used as both the phone and portable computer. The user having such a communication device at his disposal may connect to the manager side 6 to subscribe to the central database 7 and to enjoy appropriate services, as described above.

The codes' owner may apply his communication code(s) to his business card or deliver the code(s) in any other suitable way. The code(s) receiver, in turn, is provided with a very simple and expedient way of recalling and contacting those who provide him with their business cards.

It should also be noted that the users' interface presented at the personal communication device may typically include a connection key, which, whilst being actuated, initiates the on-line connection between the code receiver and code owner. The program may be such that, if the code receiver actuates the connection key, the on-line connection between the code receiver and the code owner is established upon receiving the owner's permission. The provision of the dynamic field (Fio in Fig. 8) facilitates communication between the subscribers and prevents them from unforeseen expenses.

As indicated above, either one of the user's Mailing and Restoring Lists or both of them may be maintained in the private database in the user's personal communication device, rather than in the central database, per the user's choice. In this case, User Program installed in the personal communication device is responsible for creating and maintaining the user's personal data record, assigning a communication code to him and managing the transmission of relevant information.

Fig. 10 illustrates a communication system 200, utilizing the above idea. The system 200 serves for communication between users A and B utilizing their mobile "smart-type" phone devices 8a and 8b, respectively, through the telephone network. Each of the devices 8a and 8b is preprogrammed with User Program, and is connectable to the central database manager 6, per the user's choice, as will be described more specifically further below. Thus, in this specific example, the manager utility is constituted by the User Programs installed at the subscribers' sides and connectable to each other through the network.

The operation of the system 200 will now be described with reference to Fig. 11, showing the main operational steps initiated by user A, and Figs. 12a-12b, showing the main operational steps initiated by user B. Initially, user A enters his personal data into his phone device through the interface of the User Program (step 102). In this specific example, the User Program, in response to the entrance of such data, generates a query asking user A whether he wishes his personal data record to be stored in the central database 7 (step 104).

If user A selects this option, the User Program operates to transmit his personal data to the central database manager 6 through the communication link (step 106). The manager creates the user's personal data record to be stored in the central database 7, and assigns private and communication codes C^(A) _pri_V and C^(A) _Com to user A (step 108). Thus, user A becomes the owner of these two codes, and may deliver the communication code C _Com to people with whom he wishes to keep in touch, e.g., user B, (step 110), and may use the private code C _pri_V for introducing changes in his personal data record, when necessary.

If user A declines this offer, the User Program tries to identify the user's contact address (step 112), namely the network's address of this specific communication device (phone number in this specific example). It should be noted that user A may use his personal computer as the communication device, in which case the user's contact address may be his E-mail address. Upon identifying the user's contact address, the User Program generates a query asking user A whether he agrees to have his contact address maintained at the central database (114).

The case may be such that User Program fails to identify the user's contact address. In this case, the program generates a message to user A inviting him to supply his contact address (step 116). When user A enters his contact address (step 118), he receives the query as to whether to store the contact address in the central database.

If user A disagrees to have his contact address maintained at the central database, User Program creates the personal data record (DR)_A, stores it in the memory of the phone device and assigns a communication code C _Com to user A (step 120), thereby allowing him to deliver the communication code C _Co to other parties (step 110). If user A selects the central database, User Program transmits the contact address to the central database manager (step 122). Consequently, the manager assigns private and communication codes C^(A) _priv and C^(A) _COm to user A (step 108). It should be noted that the entered communication code contains data indicative of a specific communication device, e.g., a preferred communication device of user A in which his personal data record is maintained, of his associated Service Provider, or of the central database manager.

Turning now to Fig. 12, user B to whom the communication code C _Co_m has been delivered, and who thereby is considered as the code receiver, wishes to obtain personal data of user A associated with this communication code C⁽ _c0m, and to have this data stored in his personal communication device (e.g., phone device). To this end, user B enters this communication code through the interface of his User Program (step 126). User Program identifies whether the entered communication code contains data indicative of a specific communication device (i.e., a preferred communication device of user A in which his personal data record is maintained) or of the central database manager 6 (step 128). Accordingly, User Program initiates contact with either the communication device of user A (step 130) or the manager 6 (step 132). In the case that User Program has contacted the central database manager 6, the manager routes the request to the communication device of user A (step 136). To this end, the manager generates a corresponding message to User Program of user A indicative of the relevant data of user B (per his preferences, as described above, e.g., his network's address), who is asking for the personal data of user A. Thus, the communication device of user A is contacted either by User

Program of user B or by the central database manager. If the communication device of user A is in the off-line mode, i.e., is not continuously connected to the telephone (or computer) network, the User Program of user B generates a corresponding message and transmits it to the user's A mailbox (step 138). If the user's A device is in the on-line mode, his User Program becomes actuated (step 140), and operates to identify whether any data from the user's A personal data record can be transmitted in response to any request or upon the permission of user A (step 142).

If no permission is required, User Program of user A transmits the requested personal data, i.e., associated with the communication code C _Com, to the communication device of user B and keeps the user's B personal data (e.g., his network address) in the Mailing List of user A (step 144). If the user's A permission is required, his User Program presents a corresponding message to him (step 146). Then depending on the user's A selection, User Program either transmits his personal data to user B (step 144), or generates and transmits a corresponding message to user B indicative of that the transmission of this personal data is not allowable (step 148).

As indicated above, the manager utility may be constituted by User Programs installed in the personal communication devices of the code owner and the code receiver, without utilizing any central database manager. In this case, as illustrated in Fig. 13, a communication system 300 is actually composed of a plurality of users communication devices - two devices 8 A and 8B being shown in the present example to facilitate understanding, and a communication link through which they are connectable to each other. The term "communication link" in this specific example signifies also a plurality of server utilities (server providers) enabling the connection between these devices. In the present example, the personal communication devices are users' mobile phones, but it should be understood that such devices may also be computers. The User Program is installed in each such communication device. The system 300 operates in the following manner. User A, to become the owner of a communication code C ^A) _com, through his User Program, enters all desired information and creates his personal data record, which is stored in the memory of his communication device. The User Program either creates user A private database or utilizes the existing one, if any (per his choice). Upon creating the personal data record, the User Program generates the communication code C co_m, the network address of user A communication device being a part of this communication code. User A could select specific fields in the data record that contain information to be transmitted with or without his specific permission.

User B, who has received this communication code and who wishes to obtain corresponding personal information of user A stored in his personal communication device in a manner to be kept up to date, uses the interface of his User Program for entering this code C^(A) _COm- The User Program of user B request him to supply information to be transmitted to user A for identifying user B who requests the personal information of user A. Then, the Program generates a request message indicative of that user B requests personal information from the data record of user A corresponding to this communication code, and operates to connect the communication devices of users B and A through the communication link and to transmit this message, provided the network address of user A is identified. Obviously, the User Program of user B, similarly to that of user A, manages the private database of user B (i.e., either an existing one or a new one created by the User Program for the purposes of the present invention).

The User Program of user A identifies this request message and personal information of user B (if any) to be recorded in the "Mailing List" of user A, and operates in accordance with the selection of user A to transmit the requested information. If no personal information of user B is supplied, the User program of user A records the identified network's address of user B, i.e., the address from which the request message has arrived. The User Program of user A will use this address or that indicated by user B, if any, for updating purposes. To this end, the User Program of user A, in response to changes entered in the personal data record of user A, will generate (either automatically or periodically, per choice of user A choice, as described above) a corresponding message and transmit it to the network's address of user B. Obviously, user A has an option to select those to whom he wishes to transmit such a notification (updating) message without his specific permission. It should be noted that the communication code of user A generated by his

User Program includes data indicative of this software package. Consequently, when using phone devices for communication, this data can be identified to realize that the call comes from User Program, and therefore to actuate User Program of user B, without generating an incoming call at user B's side. The User Program of User B, upon receiving the requested information, creates a specific record in the "Restoring List" of user B maintained in his private database. Upon receiving a message indicative of changes in the information contained in this record (coming from the User program of user A), the User Program of user B operates to update the corresponding record. It should be noted that such a private database may be composed of a database maintained in a memory of the server utility of a specific LAN, for example the server of the company's computer network, and a database maintained in the memory of a personal computer of a particular company's employee. For example, the employee's "Mailing" and/or "Restoring" lists are maintained in the company's server, and his personal information (his personal data record) and, possibly, one of the above lists, is stored in his personal computer. As indicated above, each data record is associated with its owner, its corresponding "Mailing List" and corresponding communication code of the code owner. All these information may be maintained at the code owner's side and/or at the central database. As for the case of distributed database, for example, the data record itself is maintained at the code owner's side (his private database), the owner's particulars (e.g., his name) is maintained at the Service Provider's side, and the "mailing List" is maintained in the central database. It is important to note that the case may be such that information contained in the "personal" data record does not necessarily relate to the particulars of the code owner (name, address, etc.), but rather to a specific entity. For example, a card containing such information relates to a product commercially available from a specific company. Thus, with the present invention, this company may record a list of customers who have purchased this product to inform them about new, improved models of the product or other products of the company.

Another example of such an entity-like "subscriber" to which the data contained in the data record actually relates, is a class picture. Thus, young people whilst graduating from high school, may create such a data record to have the opportunity to keep in touch over time.

Thus, the communication code enabling the "keep in touch" technique according to the invention contains data providing access to a corresponding part of the information included in the data record of the code owner. These data depends on the kind of the manager utility. If the central database manager serves as the manager utility, such a communication code is indicative of the network's address of the manager and of an identification code of a corresponding data record stored in the central database. If the manager utility managers a distributed database, the communication code includes the network address of a corresponding Service Provider, the identification code of a corresponding database where the data record is maintained and the identification code of this data record. If User Programs serve as the manager utility, the communication code is indicative of the network address of a corresponding Service Provider, the network address of the code owner (e.g., his phone number or Email) and identification code of a corresponding data record at user's private database.

Thus, the present invention utilizes users' personal communication devices (phone device, computer) connectable to each other through the network, and utilizes the manager utility (central database manager associated with the network's server or User Programs installed in the personal communication devices) to facilitate the keeping in touch" between the users.

Those skilled in the art will readily appreciate that various modifications and changes can be applied to the preferred embodiments of the invention as hereinbefore exemplified without departing from its scope defined in and by the appended claims. For example, the network may be a computer or telephone network or a combination of both. Consequently, the communication device from which the address code (i.e. requested data) is input and to which the relevant information is transmitted, may be a computer or a phone device equipped with all necessarily utilities. The programming means managing the central database (API), and that managing the private database ("User Program"), may be of any known suitable kind. In the method claims, which follow, characters that are used to designate claim steps are provided for convenience only, and do not apply to any particular order of performing the steps.

Claims

CLAIMS:

1. A communication method between an owner of at least one communication code and a receiver of said at least one communication code utilizing a manager utility, the method comprising the steps of: at the code owner side:

(c) feeding said at least one communication code to the manager utility;

(d) receiving data representative of said at least predetermined part of the information belonging to the code owner; at the manager utility :

(e) upon the receipt of said data record, storing it and assigning said at least one communication code to the data record owner;

2. The method according to Claim 1, wherein said manager utility comprises a central database manager.

3. The method according to Claim 2, and also comprising the step of: - subscribing by the code owner to the central database manager.

4. The method according to Claim 3, wherein said subscribing comprises the following steps performed by the central database manager: - assigning a private code to the code owner to be used by him or by another user on his behalf for introducing changes in said at least predetermined part of the information included in said data record; - upon detecting that said changes have been made, storing data indicative of said changes in the central database; and upon transmitting at least said predetermined part of the stored information of the code owner to the code receiver per his request, notifying the code owner about said code receiver.

5. The method according to Claim 2, and also comprising the step of;

- subscribing by the code receiver to the central database manager.

6. The method according to Claim 5, wherein said subscribing comprises the following steps performed by the central database manager:

- upon receiving said at least one communication code from the code receiver, registering said code receiver as the receiver associated with said at least one communication code of said code owner; and

- upon detecting that any changes were made to said at least predetermined part of the information of the code owner stored in the central database, and that the changes were made after the transmission of said information to the code receiver, notifying the code receiver about said changes.

7. The method according to Claim 1, wherein the code owner and the code receiver sides each comprises a personal communication device which is a node of a network.

8. The method according to Claim 7, wherein said manager utility comprises a predetermined software package installed in the personal communication device of the code owner and a similar software package installed in the personal communication device of the code receiver; said storing of the data record, assigning of said at least one communication code to the data record owner and transmitting at least said predetermined part of the stored information of the code owner to said code receiver is carried out by the software package installed in the personal communication device of the code owner.

9. The method according to Claim 8, and also comprising the step of: - managing a private database of the code owner in his personal communication device, wherein said managing is performed by the software package installed in the personal communication device of the code owner.

10. The method according to Claim 8, and also comprising the step of: - managing a private database of the code receiver in his personal communication unit, wherein said managing is performed by the software package installed in the personal communication unit of the code receiver.

11. The method according to Claim 2, wherein the code owner side comprises a personal communication device that is a node of a network, said central database manager being associated with the network's server.

12. The method according to Claim 11, wherein the manager utility also comprises a predetermined software package installed in the personal communication device of the code owner and capable of operating in response to data coming from the central database manager.

13. The method according to Claim 11, wherein said data record is transmitted to the central database manager through said network.

14. The method according to Claim 4, wherein the code owner side comprises a personal communication device that is a node of a network, said central database manager being associated with the network's server.

15. The method according to Claim 14, wherein said private code and said at least one communication code are transmitted to the code owner through the network.

16. The method according to Claim 2, wherein said code receiver side comprises a personal communication unit, which is a node of a network, said central database manager being associated with the network's server.

17. The method according to Claim 16, wherein said at least one communication code is transmitted from the code receiver to the central database manager through said network, and said at least predetermined part of the stored information of the code owner is transmitted to said code receiver through the network.

18. The method according to Claim 11, and also comprising the step of: - managing a private database of the code owner.

19. The method according to Claim 18, wherein said managing comprises the following steps: - upon receiving said at least one communication code from the code receiver, registering said code receiver as the receiver associated with said at least one communication code of said code owner, and automatically generating a message to notify the code owner about said code receiver; transmitting said massage to the personal communication device of the code owner through said network; and in response to said message, updating said private database of the code owner accordingly.

20. The method according to Claim 18, wherein said private database of the code owner is maintained in his personal communication device, a predetermined software package being installed in said personal communication device.

21. The method according to Claim 18, wherein said private database of the code owner is maintained in the central database.

22. The method according to Claim 16, and also comprising the steps of: - managing a private database belonging to said code receiver.

23. The method according to Claim 22, wherein said managing comprises the following steps: upon receiving said at least one communication code from the code receiver, registering said code receiver as the receiver associated with said at least one communication code of said code owner; upon detecting that any changes were introduced to said at least predetermined part of the stored information after the transmission of said information to the code receiver, automatically generating a message to notify the code receiver about the detected changes; transmitting said massage to the personal communication unit of the code receiver through said network; in response to said message, updating said private database of the code receiver accordingly.

24. The method according to Claim 22, wherein said private database of the code receiver is maintained in his personal communication unit, a predetermined software package being installed in said personal communication device.

25. The method according to Claim 22, wherein said private database of the code receiver is maintained in the central database.

26. The method according to Claim 1, and also comprising the step of:

- applying by the code owner his at least one communication code to his business card to be delivered to the code receiver.

27. The method according to Claim 1, and also comprising the step of: - assigning at least one additional communication code to said code owner.

28. The method according to Claim 27, wherein each of the communication codes assigned to the same code owner is associated with a corresponding part of the information contained in his data record.

29. The method according to Claim 27, wherein said additional communication code assigned to the said code owner is associated with an additional data record belonging to the code owner and stored in the central database.

30. The method according to Claim 19, wherein said transmitting of the message from the central database manager to the personal communication device of the code owner comprises the steps of:

- transmitting said massage to the server utility of the network;

- delaying the transmission of the message from the server utility to said personal communication device until the server utility detects that an on-line connection between the personal communication device and the server utility is established.

31. The method according to Claim 23, wherein said transmitting of the message from the central database manager to the personal communication unit of the code receiver comprises the steps of:

- transmitting said massage to the server utility of the network; - delaying the transmission of the message from the server utility to said personal communication unit until the server utility detects that an on-line connection between the personal communication unit and the server utility is established.

32. The method according to Claim 19, wherein said automatic generation of the notification message to the code receiver is performed in response to said changes made by the code owner.

33. The method according to Claim 23, wherein said automatic generation of the notification message to the code receiver is performed in response to the detected changes, wherein an inspection procedure for detecting changes is performed periodically.

34. The method according to Claim 33, wherein the periodic inspection for detecting changes is initiated by the software package installed in the personal communication unit.

35. The method according to Claim 33, wherein the periodic inspection for detecting changes is initiated by the central database manager.

36. A communication method between an owner of at least one communication code and a receiver of the code utilizing a central database manager, the code owner and the code receiver having their personal communication devices, wherein the communication devices are nodes of a common network and said central database manager is associated with a server utility of said network, the method comprising the steps of: at the code owner side:

- creating a data record containing information belonging to the code owner, and transmitting said data record to the manager through said network; - receiving the at least one communication code associated with at least a predetermined part of said information; at the code receiver side, upon receiving said at least one communication code:

- transmitting said at least one communication code to said central database manager through said network;

- receiving data representative of said at least predetermined part of the information of the code owner, and storing said data in the personal communication device of the code receiver, at the central database manager: - upon the receipt of said data record of the code owner, storing said personal information in said central database, and assigning to the data record owner said at least one communication code associated with said at least predetermined part of the stored information;

- in response to said communication code, transmitting said at least predetermined part of the data record to said personal communication device of the code receiver; and

- registering said code receiver as the receiver associated with said code owner, in a manner to provide an indication to the code owner about his associated code receiver, and to notify the code receiver about any changes introduced by the code owner to said at least predetermined part of his information.

37. A communication system utilizing a network having a server utility and communication units associated with different network's subscribers, the system comprising a central database manager associated with said server utility, wherein the central database contains data representative of a plurality of data records, each data record containing information belonging to the corresponding subscriber and being associated with at least one communication code assigned to at least a predetermined part of the information of the corresponding subscriber who is the owner of said at least one code; the central database manager comprises: a communication utility that receives data addressed to the central database and transmitted through said network, and transmits data from said central database to a corresponding one of said communication units through the ₅ network; an identification utility coupled to said communication utility for identifying said data addressed to the manager as a certain request to the central database; and a central processor utility that is coupled to the communication utility and to the identification utility, and is associated with said central database, the central ₁₀ processor utility being responsive to the request data for generating data representative of said at least predetermined part of the information included in the corresponding data record, when the request data is representative of said at least one communication code, and, when the request data is representative of the data record, for storing the information included in the ₁₅ data record in the central database and assigning said at least one communication code to the corresponding subscriber.

38. The system according to Claim 37, wherein said central processor utility comprises a predetermined application program interface for managing said central database. ₂₀

39. The system according to Claim 38, wherein said application program interface creates and manages a plurality of private databases, each belonging to a corresponding one of the network's subscribers.

40. The system according to Claim 37, wherein the network's subscribers are provided with a predetermined programming/interface utility installed in

₂5 their communication units for creating and managing a private database of the corresponding subscriber.

41. The system according to Claim 37, wherein said central processor utility is responsive to the communication code transmitted from the network's subscriber for notifying the code owner.

42. The system according to Claim 37, wherein said central processor utility is responsive to any changes introduced by the code owner to the at least predetermined part of his information stored in the central database for notifying those subscribers who used the corresponding communication code

5 for requesting and obtaining the information of the code owner.

43. The system according to Claim 40, wherein said programming/interface utility is responsive to messages coming from the central database manager for amending data included in the private database accordingly.

44. The system according to Claim 37, wherein said network is a computer 10 network.

45. The system according to Claim 44, wherein said computer network is the INTERNET.

46. The system according to Claim 37, wherein said network is a telephone network, said subscribers' communication units being phone devices.

15 47. The system according to Claim 46, wherein the phone device is equipped with a predetermined programming/interface utility for and managing a private database of the corresponding subscriber, and is associated with an identification utility connected to a phone mechanism and to the programming/interface utility, the identification utility being responsive to data

20 coming from the central database manager for actuating the programming/interface utility.

48. The system according to Claim 37, wherein the network's server is composed of a plurality several remote server utilities connectable to each other through a communication link.

25 49. The system according to Claim 48, wherein said central database manager is a part of one of the plurality of server utilities.

50. The system according to Claim 48, wherein said central database is distributed between the server utilities, different parts of said central database being associated with different server utilities.

51. The system according to Claim 37, wherein the central database also comprises:

- data representative of certain preferences of the network's subscribers;

- data indicative of those network's subscribers who have requested and to 5 whom have been transmitted data representative of said at least predetermined part of the information included in the data record of the code owner; and

- data indicative of those network's subscribers whose information have been requested by and transmitted to the code owner.

₁0

52. The system according to Claim 39, wherein the private database of the specific network's subscriber comprises:

- data indicative of those network's subscribers who have requested and to whom have been transmitted data representative of said at least predetermined part of the information included in the data record of said

₁5 specific subscriber; and

- data indicative of those network's subscribers whose information have been requested by and transmitted to said specific subscriber.

53. The system according to Claim 40, wherein the private database of the specific network's subscriber comprises:

20 - data indicative of those network's subscribers who have requested and to whom have been transmitted data representative of said at least predetermined part of the information included in the data record of said specific subscriber; and

- data indicative of those network's subscribers whose information have been 25 requested by and transmitted to said specific subscriber.

54. A communication system for providing communication between first and second subscribers to a network, the system comprising: a personal communication unit of the first subscriber and a personal communication unit of the second subscriber, the first and second ₃₀ communication units being connectable to each other through the network; and a manager utility including a first software package installed in the first personal communication unit and a similar, second software package installed in the second personal communication unit, wherein the first software package is responsive to data coming from the network and addressed to the first communication unit, so as to selectively generate corresponding notification messages to the first subscriber, to manage a private data base of the first subscriber, and to transmit predetermined data from the private database of the first subscriber to the second subscriber, and is responsive to data entered into the personal communication unit of the first subscriber to assign at least one communication code to the first subscriber; the second software package is responsive to data coming from the network and addressed to the second communication unit, so as to selectively generate corresponding notification messages to the second subscriber, to manage a private data base of the second subscriber, and to transmit predetermined data from the private database of the second subscriber to the first subscriber, and is responsive to data entered into the personal communication unit of the second subscriber to assign at least one communication code to the second subscriber.