MXPA98000830A

MXPA98000830A - Personal information administrator to update a telecommunication subscriber profile

Info

Publication number: MXPA98000830A
Application number: MXPA/A/1998/000830A
Authority: MX
Inventors: Buhrmann Michael; Elizabeth Montemayor Jane
Original assignee: At&T Wireless Services Inc
Priority date: 1996-06-04
Filing date: 1998-01-29
Publication date: 1998-04-01

Abstract

The present invention relates to a subscriber entering personal information data into a personal information manager (PIM). The PIM, either automatically, or based on additional profile requests entered by the subscriber, generates profile update data associated with the personal information data. The PIM transmits the update data of the profile to a database of a telecommunication system which stores the subscriber profile data. The transmission is via a wired communication link, a wireless communication link, or a wired and wireless communication link combination. After the reception of the profile update data by the database, the subscriber profile data stored therein is updated according to the profile update data of the subscriber. Subsequently, telecommunication services, including call termination services and message reminder services, are provided to the subscriber based on the updated subscriber profile data.

Description

PERSONAL INFORMATION ADMINISTRATOR TO UPDATE A TELECOMMUNICATIONS SUBSCRIBER PROFILE FIELD OF THE INVENTION This invention relates in a general manner to personal information administrators. In particular, this invention relates to a personal information manager for updating a telecommunication subscriber profile based on information entered in the personal information manager.

BACKGROUND OF THE INVENTION In an increasingly mobile society, telecommunication service providers offer many different types of telecommunication services to their subscribers. With the increasing popularity of wireless communication systems (ie, wireless cellular telephone systems, wireless cellular personal communication systems (PCS), or paging systems), such services allow users of wireless communication devices (e.g., telephones) mobile devices REF .: 26568 mobile data, or pagers receivers) to manage their availability for communication. Such services are generally provided to subscription-based users, and therefore, those users are often known as subscribers or subscribers. One category of telecommunication services are the so-called call termination services. The call termination refers to the manner in which a call to a subscriber is processed to the telecommunication system. Call termination services are particularly important in a wireless communication system. Subscribers, while assessing the ability to be reached by a mobile phone, recognize that there may be certain times (for example, during meetings) when they do not want to be interrupted by a phone call. One type of call termination service is call forwarding, in which telephone calls for a subscriber are transmitted to an alternate destination at certain times. Such alternative destination may be, for example, a secretary, voice mail, or other telephone. In this way, if a calling subscriber makes a call to the mobile telephone of a subscriber who has activated the transmission of calls, the call will be automatically routed to the alternative destination.

Another type of call termination service is selective call acceptance, in which only calls from certain telephone numbers are routed to a subscriber telephone during certain times. For example, if a subscriber is in a meeting, he / she can activate the selective call acceptance to route all calls, except those of his secretary, to voice mail. Another category of telecommunication services is the paging alert reminder service. This service provides subscribers with paging alert messages to remind the subscriber of a scheduled event. For example, U.S. Patent No. 5,122,795 describes a national paging system which interconnects existing local paging services. The system includes an automatic page generator, which maintains a list of events that cause pages to be generated for a particular subscriber. A type of automatic page is a page initiated by time, which is issued at a specific time (for example, wake-up calls, notification of birthdays, reminders to take medication, etc.). When the scheduled event occurs, the page generator sends a page for distribution to the appropriate local paging service for issuance.

Also related to the paging messages is U.S. Patent No. 5,416,473, which is addressed to a calendar activated message system. This describes an electronic information processing device (e.g., pocket paging assistant, a personal computer, an electronic pocket organizer, a desktop computer or the like) which communicates with a paging terminal via a conventional modem to automatically send pre-stored messages to a paging subscriber as reminders for meetings, appointments or the like. A user enters a message, a time at which the message should be transmitted, and an identification of a paging subscriber, in the electronic training processing device. The information is stored in a memory of the electronic information processing device until the indicated time occurs. At the indicated time, the electronic information processing device communicates the message to a paging terminal to release it to the pager associated with the identified subscriber. In this way, the electronic information processing device can be used as a notification system to notify paging subscribers of scheduled events. The electronic information processing device is external to the paging system, and communicates with the paging system via a modem. Since the electronic information processing device is not part of the telecommunications network, and does not send messages to the telecommunications network until the time of the alert has arrived, the electronic information processing device must be continuously dedicated to the task of looking for messages that need to be sent. In addition, as a result of being external to the paging system, the electronic information processing device must have continuous access to a telephone line to communicate a message to the paging system. For a telecommunication service provider to provide individualized telecommunication service (eg, call termination services and paging alert reminder service) to the subscribers, individual subscriber profiles must be stored in a database in the network of telecommunication: Such subscriber profiles describe, for each subscriber, the characteristics of the telecommunication service that the subscriber subscribes to, and the current state of the characteristic (for example, active or inactive). In addition, the subscriber profile describes characteristic descriptions that may be unique to each subscriber to allow each subscriber to have a set of customizable telecommunication service features. The problem arises as to how to enter the information in a subscriber profile and how to maintain an updated subscriber profile to reflect a changing program of the subscriber. A method for entering and updating a subscriber profile is for a subscriber to place a telephone call to a processing system which updates the subscriber's profile. The processing system can be automated, so that the subscriber updates his profile based on orders entered via a telephone numeric keypad. Alternatively, the processing system can be verified by an assistant, whereby the subscriber provides his profile request to the assistant and the assistant updates the profile of the subscriber in the database. One of the disadvantages of such a system is that the subscriber must remember to call the processing system when the profile update is done. In addition, the possibility that the subscriber who makes an error in the data entry when using the automated system is another disadvantage of the system. An automated technique for updating a database containing subscriber information is described in U.S. Patent No. 5,243,645, which describes an automatic system for transmitting calls. In that system, a subscriber's call transmission profile is updated based on transactions or activities indicating the subscriber's location. From the point of view of the subscriber, those activities are those discussed with reasons not related to the transmission of calls (for example, the use of a credit card or placement of a long-distance credit card call). An advantage of such a system is that the subscriber's call transmission profile is updated without any extra effort by the subscriber. A disadvantage of this system is that call transmission information is updated only after a subscriber performs an appropriate activity while in a location. If the user does not perform such activity, then the user's transmission profile is not updated. U.S. Patent No. 5,434,908 discloses a system for automatically managing greetings for a subscriber's voice message system based on the information contained in the subscriber's electronic program database (e.g., the program database of the subscriber). administration of the calendar stored in a computer). According to this system, a computer connected to a voice mail system and having access to the database of the electronic program executes a special process. The process periodically verifies the subscriber's electronic program database and determines whether the subscriber's voice mail message needs to be updated. If the voicemail message needs to be updated, the process generates a new message and sends the message to the voicemail system. One shortcoming of such a system is that, since the computer is not an integral part of the voice message system, and does not generate and send the new message to the voice message system until it encounters a program time event, the computer should be continually dedicated to the task of looking for events of scheduled times that require the generation of a message. In addition, as a result of not being an integral part of the voice message system, the computer must have continuous access to the voice mail system to communicate a voice message generated to the voice message system. In addition, the system does not affect the processing of the call (for example, call routing) based on the entries in the electronic program database. The routing of the call to the voice message system is not based on the information contained in the subscriber's electronic program database. The information contained in the subscriber's electronic program database only affects the voice mail message heard by a calling party after the call is routed to the voice mail system.

BRIEF DESCRIPTION OF THE INVENTION A personal information manager (PIM) for updating a telecommunication subscriber profile based on subscriber's personal information data entered into the PI-M. A subscriber enters personal information data into a PIM. Such personal information data comprises program data describing scheduled events (eg, meeting hours, appointments, etc.) and contact data describing the user's contacts (eg, name, address, telephone number, etc.) . Based on the personal information data, the PIM generates updated profile data which is transmitted to a node of the telecommunications network in which the subscriber profile data is stored. In one mode, the user is presented with the user interface to enter profile requests in conjunction with each of the scheduled or scheduled events. In this way, for each of the scheduled events, the subscriber can request that the subscriber's profile be updated in a particular way. Such profile requests include call termination requests, in which a subscriber requests that calls placed for a communication device associated with the subscriber be routed in a particular way, and alert requests, in which a subscriber requests a call. Reminder message is programmed to be sent to a communication device associated with the subscriber in conjunction with a scheduled or scheduled event. After the introduction of the subscriber profile requests, the PIM transmits the profile update data, based on the request or profile request data, to a telecommunication network node in which the profile data of the subscriber They are stored. The profile update data includes call termination update data, corresponding to call termination requests, and alert update data, corresponding to alert requests. In an alternative mode, instead of the subscriber entering profile requests in the PIM, the PIM automatically generates the profile update data based on the program information describing scheduled events entered by the subscriber. In such modality, the subscriber can enter default information that indicates the type of profile update data that should be generated for different types of program information. For example, the default information may indicate that all calls to the subscriber during scheduled meetings should be sent to voicemail. In such an example, the PIM will automatically generate call termination update data for scheduled meetings. Similarly, the default information may indicate that a reminder message should be sent to the subscriber as a reminder for all meetings. In such an example, the PIM will automatically generate alert update data for scheduled meetings. According to another aspect of the invention, the call termination update data is generated based on the contact data representing user contacts. The user enters a call termination request associated with a subscriber contact. The PIM generates profile update data, including call termination update data, based on the call termination request and transmits the profile update data to a telecommunications network node in which the profile data of the subscriber are stored in a database. The transmission of the update data of the PIM profile to the database in the telecommunication system can be via the wireless communication link, a wired communication link, or a combination of wired and wireless communication links. After receiving the update data of the profile of the database, the subscriber profile data is updated accordingly. Thus, in accordance with the present invention, the subscriber's PIM updates the profile of the subscriber in the telecommunication network based on personal information data of the subscriber. In this way, the telecommunication profile of the subscriber closely corresponds to the actual program of the subscriber and the updating of the subscriber's telecommunication profile is closely integrated with the subscriber's PIM programming and the contact management mechanism. Those and other advantages of the invention will be apparent to those skilled in the art with reference to the following detailed description and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 shows a system for updating a telecommunication subscriber profile via a wired communication link and for providing telecommunication services based on the updated subscriber profile. Figure 2 shows the structure of a subscriber profile record.

Figure 3 is a flow chart of the steps for generating the updated profile data to be used in updating the subscriber profile database. Figure 4 shows an example of the PIM program display. Figure 5 shows an example of the PIM program display with an aggregate profile request field. Figure 6 shows an example of subscriber profile registration. Figure 7 is a flow diagram of the steps performed to process a call according to an updated subscriber profile. Figure 8 is a flow diagram of the steps performed for message alert processing according to an updated subscriber profile. Figure 9 shows a system for updating a telecommunication subscriber profile via a wireless communication link to provide telecommunication services based on the updated subscriber profile. Figure 10 shows a system for updating a telecommunication subscriber profile via a wireless telecommunication link using a packet data protocol and for providing telecommunication services based on the updated subscriber profile.

Figure 11 shows a visualization example of the PIM contact manager.

DETAILED DESCRIPTION OF THE INVENTION A system for updating a telecommunication subscriber profile and for providing telecommunication services based on the updated subscriber profile is shown in Figure 1. A wireless cellular communication network 102 includes a mobile switching center (MSC) 104, a station radio base (RBS) 106, a service control point (SCP) 108, a voice mail processor 146, a message center 150, and a message alert processor 148. A mobile station 110 is shown in communication with the RBS 106 via a radio communication link 112. The mobile station 110 is shown here as a mobile telephone. A suitable mobile station 110 can be a telephone capable of operating in accordance with TIA / EIA Interim -Standard IS-137, '800 MHz TDMA Cellular - Radio Interface -Minimum Performance Standards for Mobile Stations, December 1994, Telecommunications Industry Association , which is incorporated here as a reference, so that in addition to receiving and transmitting voice, the telephone is capable of receiving messages from the short message service. Of course, other types of telephones can also be used (for example, code division multiple access (CDMA) or Group Special Mobile (GSM)). The SMS messages are short text messages, which are transmitted to the telephone via the wireless cellular communication network 102. Upon receipt by the telephone, the SMS message is displayed in the visual display area 111 of the telephone. Such message system via SMS is well known and is described in more detail in TIA / EIA Interim Standard IS-136. 1, 800 MHz TDMA Cellular - Radio Interface - Mobile Station - Base Station Compatibili ty - Digi tal Control Channel, Rev. 0, May 17, 1995, Telecommunications Industry Association, which is incorporated herein by reference. It should be noted that although the mobile station 110 is defined here as a mobile telephone, the mobile station 110. may be another type of wireless communication device. As is well known in the wireless communications art, a wireless cellular communication network 102 comprises a plurality of radio base stations, such as the RBS 106, each of which serves a geographic area, or cell. Only one RBS 106 is shown in Figure 1 for clarity. The RBS 106 is connected to the MSC 104 which controls the operation of the RBS 106. The MSC 104 is also connected to the public switched telephone network (PSTN) 114, which allows the mobile station 110 to communicate with landline stations, such as a telephone 116. The MSC 104 is also connected to the SCP 108, the voice mail processor 146, and the message center 150. The SCP 108 contains a database 118 which contains subscriber profiles. The operation of the SCP is controlled by the SCP logic 120. The SCP logic 120 may be a computer processor that executes stored program instructions in a manner that is well known in the art. Alternatively, the SCP logic 102 can be a circuit for carrying out the functions of the SCP logic 120. The operation of the SCP logic 120 will be discussed in more detail later. The configuration of a wireless cellular communication network 102 is well known, and the details of such a network will not be discussed here. For more information on wireless cellular communication networks see Neil L. Boucher, Cellular Radi or Handbook, 3rd Edition, Quantum Publishing, Mili Valley, CA, 1995, which is incorporated herein by reference. As discussed above, telecommunication service providers offer many different types of telecommunication to subscribers to help subscribers manage their mobile communications. The services to which each subscriber subscribes, and the installation details of each of these services are stored in a subscriber profile database 118. The subscriber profile database 118 contains a database record for each subscriber that describes the profile of the subscriber. The structure of a subscriber profile record is shown as 200 in Figure 2. The first entry 202 in the record contains the mobile station identification number (MIN) of the subscriber's mobile station. Where the mobile station is a mobile phone, the MIN is the telephone number of the telephone. The second entry 204 in the register contains the unique electronic serial numbers (ESN) of the mobile station. The combination of the MIN and the ESN provides an index in the database 118 and identifies a unique subscriber profile record for a particular subscriber and the associated mobile station. The subscriber profile record also contains characteristic entries 206, which specify the characteristics of the service for the subscriber and the associated mobile station identified by MIN and ESN. Each characteristic input 206 specifies a characteristic and the block of time during which the characteristic is active. The time entries shown in characteristic entries 206 specify a start date / time and a final date / time. These time entries can be specific, so the feature will be active from a certain date / start time to a certain date / end time. Alternatively, the end date / time can specify an indefinite date / time, so the feature will be active until the subscriber profile record is updated. The structure and elements of a subscriber profile record may vary depending on the particular implementation. The structure shown in Figure 2 is exemplary of the structure of such a record. The subscriber profile record of a particular subscriber is updated in the database 118 via the personal information manager (PIM), such as the PIM 122 (Figure 1). As used herein, a PIM is any type of electronic personal information device. For example, and without limitation, a PIM can be a program that runs on a personal computer (for example, No Up-To-Date available from Now Software, Inc., Portland Oregon), and a hands-free personal information device (for example, a Casio Digital Diary), or a personal digital assistant (for example, Apple Newton). In general, and as shown in Figure 1, an appropriate PIM 122 includes a central processing unit (CPU) 124 connected to a memory 126, a user interface 136, and a modem 138. The memory 126 contains storage areas for storing personal information data 127, a PIM program 130, a subscriber profile update application program (API) interface 132, and other data 134. Personal information data 127 comprises program data 128 and contact data 129.

The memory unit 126 can be any type of storage device that can be read by a machine. For example, and without limitation, the memory unit 126 may be a random access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), a programmable read-only memory, erasable (EPROM), a programmable read-only, electronically erasable memory (EEPROM), magnetic storage media (i.e., a magnetic disk), or optical storage media (i.e., a CD-ROM). In addition, the PIM 122 may contain several combinations of machine readable storage devices, which are accessible by the CPU 124, and which are capable of storing a combination of computer program code and data. The CPU 124 executes the computer program instructions of the PIM program 130, to carry out the personal information management functions of the PIM 122. Such functions include personal programming functions and contact management functions. Such personal information management functions are well known in the art. The program data 128 contains information about the user program. Contact data 129 contains contact information such as name, address, telephone numbers, fax numbers, etc. about the user's contacts. The API that updates the profile of the subscriber 132 in a computer program that allows the PIM 122 to be interconnected with the subscriber profile database 118 of the wireless cellular communication network 102. Additional details of the API that updates the profile of the subscriber 132 will be described later. The CPU 124 is also connected to a user interface 136, which allows the subscriber to interact with the PIM. Such a user interface 136 may be, for example, a display monitor, printer, mouse, keyboard, light pen, touch pad, or the like. In addition, the user interface 136 may include a combination of such devices. The user interface 136 allows the subscriber using the PIM 122 to view, enter and update personal information data 127 and in other circumstances interact with the PIM 122. The modem 138 is used to send information from the PIM 122 to the SCP 108 through of PSTN 114. The use of a modem to communicate with external devices is well known and will not be described in detail here. The steps for generating updated profile data, based on program data, for use in updating the subscriber profile database 118 will be described in conjunction with the flow chart of Figure 3. For purposes of the described example further on, it is assumed that the PIM user 122 is the subscriber associated with the mobile station 110. In this way, updates of the subscriber profile initiated by the user using the PIM 122 will affect the processing of calls and alert messages of the subscriber. the mobile station 110. In step 302, the subscriber updates the program data 128 via the user interface 136. Such an update step can be effected in various ways, depending on the particular PIM implementation. In general, the subscriber is provided with a program display for a day chosen via the user interface 136. An example of program display 400 is shown in Figure 4. Assume for this example that the program is displayed for March 1, 1996. The subscriber enters program data in the description field 404 to indicate that the scheduled events occur at the times indicated in the time field 402. For example, as shown in Figure 4, the subscriber has entered data indicating a meeting with John in room 4A from 9:00 AM to 10:30 AM; Lunch 12:00 a Half Day at 1:00 PM; and room 2B from 3:30 PM to 5:30 PM. After entering the data via the user interface 136, the entered data is stored as program data 128 in the memory 126 of the PIM 122. Of course, there are many different ways for the PIM 122 to handle the input of the program data 128 in the memory 126 by the subscriber via an interface of user 136, and the method will depend on the particular programming program 130 that controls the PIM 122. The data entry mechanism described herein in conjunction with Figure 4 is for example purposes only. In one embodiment, after the introduction of the program data 128 by the subscriber in step 302, the PIM 122 asks the subscriber whether the subscriber wishes to update his telecommunication subscriber profile based on the PIM entries. This question is represented in the flow diagram of Figure 3 as step 304. If the subscriber answers "NO" to this question, then the subscriber profile is not updated and the procedure ends in step 312. If the subscriber responds " YES "to this question, then in step 306 the subscriber enters profile requests in the PIM 122. The entry of profile requests is controlled by the subscriber profile update (API) 132. Alternatively, the introduction of requests can be controlled by the programming program 130. The update of the subscriber profile (API) 132 is the program code that works in conjunction with the programming program 130 of the PIM 122 to provide the functions of updating the subscriber profile according to the invention. The subscriber is presented, via the user interface 136, with a display 500 (Figure 5) that allows the insertion of profile requests in a profile request field 502. The profile request field 502 is added to the conventional programming display 400 presented by the PIM 122 in step 302. A type of profile request is a call termination request in which the subscriber requests or requests a call termination service (eg, call forwarding) be activated. Another type of profile request is a user alert request, in which the subscriber requests that an alert message service be activated. Assume that the subscriber enters profile requests in the profile request field 502 as follows. Input 504 is a call termination request indicating that from 9:00 AM to 10:30 AM, during the meeting with John in room 4A, all calls to subscriber's mobile station 110 must be transmitted to the mail of subscriber's voice. Entry 506 is a call termination request that indicates that during lunch, from 12:00 a.m.

Half a day until 1:00 PM, the subscriber asks to accept selective calls, so that only calls from the telephone number (123) 555-66661 will be released to the mobile station of the subscriber 110. All other calls will be transmitted to the mail of subscriber's voice. Entry 508 is an alert request indicating that the subscriber requests that a reminder message be generated, "meeting in room 2B", at 3:00 PM and sent to the station 1 Telephone numbers used here are for example purposes only. The use of any particular telephone number other than the exemplification of the present invention has no meaning. It is not intended to refer to real telephone numbers. mobile 110. Entry 510 is a call termination request that indicates that from 3:30 PM to 5:30 PM, corresponding to the staff meeting in room 2B, the subscriber requests that all calls to the mobile station 110 are sent to the telephone number (123) 444-5555. After the subscriber enters and confirms the profile requests entered in the profile request field 502, the PIM 122 generates appropriate profile update data to update the subscriber profile database 118 in step 308. The base The generated profile update data is based on the profile requests entered by the subscriber in the profile request field 502. The generation of profile update data controlled by the API that updates the profile of the subscriber 132. This data of Profile update include both call termination update data (from profile requests 504, 506, 510) and alert update data (from profile request 508). In one embodiment, the profile update data is in the form of a Transaction Capability Application Part (TCAP) message. TCAP messages are well known in the telecommunication network technique and are described in more detail in ANSI 1988, Signaling System No. 7 (SS7) - Transaction Capability Application Part (TCAP), ANSI TI.114- 1988, which is incorporated here as a reference. In an alternative embodiment, instead of the subscriber entering profile requests in step 306 and based on the generation of profile update data (step 308) on the profile request entered by the subscriber, the PIM 122 could be configured, through the API that updates the profile of the subscriber 132, to automatically generate profile update data based on the program data 128 entered by the subscriber in step 302. In such mode, the subscriber can store default information as data 134 in the memory 126. For example, the user may store default information indicating that when the meeting is scheduled in the program data 128, the PIM 122 shall automatically generate call termination update data specifying that all the Calls during that time should be transmitted to voice mail. In addition, the default information could indicate that when a meeting is scheduled in the program data 128, the PIM 122 should automatically generate alert update data specifying that an alert message should be sent to the mobile station 110 at a time. default before the scheduled meeting. Of course, various types of information can be stored by default by the subscriber to customize the profile update data generated. In addition, the subscriber could leave out the profile update data automatically generated by any particular programmed case. Thus, according to this embodiment, steps 304 and 306 may not be performed. Instead, in step 308, the profile update data will be generated automatically based on the program data 128 entered by the user in step 302. After determining step 308, the PIM 122 transmits the profile update data to the wireless cellular communication network 102 in step 310. The profile update data, which are in the TCAP message format, are transmitted to the SCP 108 via the modem 13 , link 140, PSTN 114, and link 142. Links 140 and 142 may be standard telephone links. The SCP logic 120 is configured to recognize the received TCAP message as profile update data to update the appropriate subscriber profile record in the database 118. Assuming that no other subscriber profile data was stored in the profile register subscriber for the subscriber associated with the mobile station 110, the subscriber profile record in the database 118 after the step 310 could be the register 600 shown in Figure 6.

The header 602 of the register contains MIN ((123) 456-789) and ESN (998877665544) of the mobile station 110 associated with the subscriber. The characteristic entry 604 of register 600 is the subscriber's call termination data specifying that the call transmitted to the voice mail must be invoked from 9:30 AM to 11:00 AM on 3/1/96. This subscriber call termination data corresponds to the entry 504 in the profile request field 502 entered by the subscriber during step 306. The characteristic entry 606 of the register 600 is the subscriber's call termination data specifying that the Acceptance of selective telephone number calls (123) 555-6666) must be invoked from 12:00 a.m. to noon until 1:00 p.m. 3/1/96. Calls from the other telephone numbers are directed to voice mail. This subscriber call termination data corresponds to the entry 506 in the profile request field 502 entered by the subscriber during step 306. The characteristic entry 608 of the record 600 is the subscriber alert data specifying that the message " meeting in room 2B "should be sent to mobile station 110 at 3:00 PM on 3/1/96. In this way the subscriber alert data corresponds to the input 508 in the profile request field 502 entered by the subscriber during step 306. The characteristic input 610 of the register 600 is the subscriber call termination data specifying that the call transmitted to the telephone number (123) 444-5555 must be invoked from 3:30 PM to 5:30 PM on 3/1/96. This subscriber call termination data corresponds to input 510 in the profile request field 502 entered by the subscriber during step 306. The procedure ends in step 312. Thus, in the manner described above in conjunction with Figure 3, the subscriber profile data stored in the database 118 of the wireless cellular communication network 102 are updated as a result of the introductions made by the subscriber in the PIM 122. The registration of the subscriber profile 600 described above it is only an example of how the subscriber profile data (including subscriber call termination data and subscriber alert data) can be stored in the database 118. Other data organization techniques can be used to store the data. Subscriber profile data in data bank 118. As described above, the profile update data can be generated based on the Program data 128 stored in the PIM 122. Additionally, the profile update data can be generated based on contact data 129 as follows. As described above, the contact data 129 contains data such as the name, address and telephone number for user contacts. To view such contact data 129, the user is presented, via the user interface 136, a display 1100 (Figure 11) which lists all, or part, of the contact data 129. As shown " "* in Figure 11, display 1100 contains names with addresses and associated telephone numbers. A subscriber could use such a PIM display to request the update of the subscriber's profile. For example, assume 0 that the subscriber is entering a meeting but is waiting for an important call from Mary Jones. In this way, the subscriber wishes that all calls be transmitted to voice mail, except calls from the Mary Jones telephone number, which must be released to the mobile station 5 of the subscriber 110. The subscriber could select (eg, using a mouse) enter 1102 in the display 1100. The subscriber could then indicate a call termination request (eg, selective call acceptance) for the selected entry 1102, and the subscriber 0 could also indicate the start time and end in which the call termination request must be active. Such an indication can be made, for example, through a PIM order using an operation menu. Of course, there are many variations on how the subscriber can select a name from display 1100 and enter a call termination request, depending on the particular PIM implementation. After the confirmation of the request, the PIM 122, under the control of the program of the PIM 130 and the API that updates the profile of the subscriber 132, generates profile update data, which contain update data of call termination, and sends the profile update data to the wireless cellular communication network 102. The steps of generating the profile update data and sending the profile update data to the wireless cellular communication network 102 are similar to the steps 308 and 310 described previously in conjunction with Figure 3. In this example, upon receipt of the profile update data, the subscriber profile record in database 118 could be updated to contain a feature entry containing the completion data of subscriber calls that specify that the selective call acceptance for the telephone number (465) 493-5835 must be invoked during a particular time, and that calls from other telephone numbers should be directed to voice mail. Such a characteristic input could be similar to the characteristic input 606 of the register 600 described above in conjunction with Figure 6. Thus, in accordance with this aspect of the invention, the contact data 129 that is stored as personal information data. 127 in the memory 126 of the PIM 122 are to allow a user to request that the call termination feature update for the user's subscriber profile in the wireless cellular communication network 102 be made. Call processing will now be described. according to the present invention in conjunction with the flow chart of Figure 7. In step 702 a call is placed from landline telephone 116 to mobile station 110. In step 704, the call is routed through PSTN 114 to MSC 104. It should be noted that the routing of calls from a landline telephone to a wireless cellular communication network Manufacturing is well known in the art. In step 706 the MSC 104 sends a question to the database 118 via the link 144 requesting subscriber profile registration of the subscriber associated with the mobile station 110. The logical SCP 120 is configured to receive the request, retrieve the registration subscriber profile 600 of the database 118, and send the subscriber profile record 600 which contains the subscriber profile data to the MSC 104. As described above, the subscriber profile record 600 includes both subscriber profile data 600. subscriber call termination (entries 604, 606, 610) and subscriber alert data (entry 608). In step 708 it is determined whether the call termination feature is active at the time of the call.

If a call termination feature is active, then in step 712 the call is routed according to the active call termination feature. If a call termination feature is not active, then in step 710, the call is routed to the mobile station 110 via the RBS 106 and the communication link 112. It should be noted that the routing of a call from the MSC to a Mobile station is well known. The process ends in step 714. As an example, consider a call placed from telephone 116 (having a telephone number (123) 888-8888) to mobile station 110 at 12:30 PM on March 1, 1996. After upon reception of the call, the MSC 104 will need a registration of the subscriber profile associated with the mobile station 110 of the database 118. According to the reception, the registration of the subscriber profile 600, the MSC 104 will determine that the FEATURE-2 606 is active. According to CHARACTERISTICS-2, only telephone number calls (123) '555-6666 will be accepted between 12:00 noon and 1:00 PM. All other calls will be routed to the subscriber's voicemail. The telephone number of the calling telephone 110, called ANI, is provided by the MSC 104 by the PSTN 114 during the routing of the call in a manner well known in the art. In this way, the MSC 104 determines that the ANI can not be accepted by the mobile station 110 at that time, the call must be routed to a voice mail processor 146, where the calling party on the telephone 116 can leave a message for the subscriber. Alternatively, if the telephone number of the telephone 116 was (123) 555-6666, then the call could be routed to the mobile station 110. The processing of calls in relation to the remaining call termination feature entries ( 604, 610) in the subscriber profile record 600, could be clear to one skilled in the art given in the above description, and such call processing will be discussed in more detail here. The message alert processing according to the updated subscriber profile will now be described in conjunction with a flowchart of Figure 8. In step 802 the message alert processor 148 scans the call profile records stored in the database 118 to determine if there is any scheduled alert message that should be released 'at that time. If in step 804 it is determined that there is an alert message feature entry in the subscriber profile record for that moment, then in step 806 a short message service (SMS) message is sent to the mobile station 110 To initiate the sending of such a message, the message alert processor 148 sends a request to the message center 150 requesting that the message be sent to the mobile station 110. The message center 150 formats the message and sends it to the MSC. 104 to release it to the mobile station 110 via the RBS 106. After sending a request to the message center 150, the message alert processor 148 returns to step 802 to start the procedure again. If no alert message feature entries are found in any subscriber profile records for that moment, then the message alert processor 148 falls asleep (i.e. waits) for a period of time in step 808 and returns to the step 802 to start the procedure again. As an example, consider subscriber profile 600 (Figure 6). At 3:00 PM on March 1, 1996 the message alert processor 148 will scan subscriber profile records of the database 118 and will recognize that, as a result of the FEATURE-3 608, the message "Meeting in the room 2B "is programmed to be sent to the mobile station 110. The message alert processor 148 will send an instruction to the message center 150 to generate the message. The message center 150 will generate the SMS message and send it to the MSC 104. The MSC 104 will send the message to the mobile station 110 via the RBS 106. As a result, the message "Meeting in room 2B" will be displayed in the visual display area 111 of mobile station 110. It should be noted that the message alert processing as described above involves sending SMS messages to mobile station 110 via a network wireless cellular communication 102. Alternatively, the mobile station could be a conventional paging receiver and the message could be a conventional paging message sent through a paging system instead of a wireless cellular communication network. In such an embodiment, the message alert processor 148 could send the desired message to the paging terminal (not shown) that is associated with a conventional paging system. The paging terminal initiates a page for the unique address of the paging receiver, and upon receipt, the paging receiver will display the message. Conventional paging systems are well known and the details of such systems will not be described in detail here. For more information on paging systems, see, for example, Wireless Basi cs, 2a. Edition, 1996, Telephony Books, Overland Park, KS, ISBN D-87288-633-6, which is incorporated herein by reference. In an alternative embodiment, as shown in Figure 10, the PIM 122 sends the profile update data to the wireless cellular communication network 102 via the wireless communication link in place of the PSTN 114. The modem 138 of the modality shown in Figure 1 is replaced with a wireless modem 902 connected to a mobile station 904, such as a mobile telephone. Returning to step 310 of Figure 3, the PIM 122 transmits the profile update data, which are in the TCAP message format via the modem 902 and the mobile station 904. The modem 902 and the mobile station 904 establish a channel of wireless communication 906 with the RBS 106. The profile update data in the TCAP message format is sent to the RBS 106 over the wireless communication channel 906. The TCAP message is then sent to the SCP 108 via the MSC 104 and the link 144. Processing of the TCAP message by SCP 108 remains as described above. In another alternative embodiment, as shown in Figure 10, the PIM 122 sends the profile update data to the wireless communication network 102 via a wireless communication link using a packet data protocol. The modem 138 of the mode shown in Figure 1 is replaced with a wireless CDPD modem 1002 connected to the CPU 124 via an external interface 1004. Returning to step 310 of Figure 3, the PIM 122 transmits the update data of the profile, which are in the TCAP message format, via the modem 1002. The modem 1002 establishes a CDPD protocol channel of wireless communication 1006 with the RBS 106. The profile update data in the TCAP message format is sent to the RBS 106 on the CDPD wireless communication protocol channel 1006. The TCAP message is then sent to the SCP 108 via the MSC 104 and the link 144. The processing of the TCAP message by the SCP 108 remains as described above. The transmission of data using the CDPD wireless communication protocol channel is well known and is described in more detail in Cellul di Di gi tal Packet Da ta System Specifi ca ti on, Relay 1.1 January 19, 1995, CDPD forum, Inc. , Chicago, III, which is incorporated here as a reference. An advantageous embodiment has been described in which the invention was increased in conjunction with a wireless communications network. However, it should be clear to one skilled in the art that the principles of the present invention could be implemented in conjunction with a terrestrial communication network (eg, a telephone network) as well. In such mode, the landline communication network could include a database of the subscriber profile containing profile information about subscribers to the network. The subscriber profile database can be updated by a personal information manager who is in communication with the subscriber profile database, in a manner similar to that described above. Telephone calls placed within the landline communication network could be processed in accordance with the records contained in the subscriber profile database. With respect to alert messages, the alert message could be communicated to landline telephones within the landline communication network at scheduled time. For example, the message "Meeting in Room 2B" (which is used as an example of text sent to mobile station 1109 in a wireless mode), could be routed to a landline telephone as a voice message using techniques of Well-known text to speech conversion. The above Detailed Description should be understood as being illustrative and exemplary in every aspect, but without restriction, and the scope of the invention described herein is not determined from the detailed description, but from the claims construed according to the scope allowed by the patent laws. It should be understood that the embodiments shown and described herein are only illustrative of the principles of the present invention and that various modifications may be implemented by those skilled in the art without departing from the scope and spirit of the invention. It is noted that in relation to this date, the best method known to the applicant to carry out the aforementioned invention, is that which is clear from the present description of the invention. Having described the invention as above, property is claimed as contained in the following:

Claims

1. A personal information management device, characterized in that it comprises: a memory that stores personal information data; a user interface for receiving a call termination request associated with at least a portion of the personal information data; a modem for transmitting call termination update data based on the call request to a telecommunications network node in which the subscriber's call termination data is stored.

2. The personal information management device according to claim 1, characterized. because the personal information data comprises program data representing scheduled events and 'the call termination request is associated with one of the scheduled events.

3. The personal information management device according to claim 1, characterized in that the personal information data comprise contact data representing at least one user contact and the call termination request is associated with at least one user contact.

4. The personal information management device according to claim 1, characterized in that the modem transmits the call termination update data via a wired communication link.

5. The personal information manager device according to claim 1, characterized in that the modem is a wireless modem for transmitting the call termination update data via a wireless communication link.

6. The personal information management device of. according to claim 5, characterized in that the wireless modem is configured to transmit the call termination update data as packet data via the wireless communication link.

7. A personal information management device, characterized in that it comprises: a memory for storing personal information data; means for generating call termination update data based on personal information data; a modem for transmitting the call termination update data to a telecommunications network node in which the subscriber's call termination data is stored.

8. The personal information management device according to claim 7, characterized in that the personal information data comprises program data representing scheduled events.

9. The personal information management device according to claim 7, characterized in that the personal information data comprise contact data representing at least one user contact.

10. The personal information management device according to claim 7, characterized in that the modem transmits the call termination update data via a wireless communication link.

11. The personal information management device according to claim 7, characterized in that the modem is a wireless modem for transmitting the call termination update data via a wireless communication link.

12. The personal information management device according to claim 11, characterized in that the wireless modem is configured to transmit the call termination update data as packet data via the wireless communication link.

13. A personal information management device, characterized in that it comprises: a memory that stores program data representing scheduled events; a user interface for receiving an alert request associated with one of the scheduled events; a modem for transmitting alert update data based on the alert request to a telecommunications network node in which the subscriber's alert data is stored.

14. The personal information management device according to claim 13, characterized in that the modem transmits alert update data via a wired communication link.

15. The personal information management device according to claim 13, characterized in that the modem is a wired modem for transmitting alert update data via a wireless communication link.

16. The personal information management device according to claim 15, characterized in that the wireless modem is configured to transmit the alert update data as packet data via the wireless communication link.

17. A personal information management device, characterized in that it comprises: a memory that stores program data representing scheduled events; means for generating alert update data based on scheduled events; a modem for transmitting alert update data to a telecommunications network node in which the subscriber's alert data is stored.

18. The personal information management device according to claim 17, characterized in that the modem transmits alert update data via a wired communication link.

19. The personal information manager device according to claim 17, characterized in that the modem is a wired modem for transmitting alert update data via a wireless communication link.

20. The personal information management device according to claim 19, characterized in that the wireless modem is configured to transmit alert update data as packet data via the wireless communication link.

21. A method for the operation of a personal information management device comprising a memory that stores personal information data, the method is characterized in that it comprises the steps of: receiving a call termination request associated with at least a portion of the data of personal information via a user interface; transmit call termination update data based on the call termination request to a telecommunications network node in which the subscriber's call termination data is stored.

22. The method according to claim 21, characterized in that the personal information data comprises program data representing scheduled events and the call termination request is associated with upo of the scheduled events.

23. The method according to claim 21, characterized in that the personal information data comprise contact data representing at least one user contact and the call termination request is associated with at least one user contact.

24. The method according to claim 21, characterized in that the transmission step further comprises the step of transmitting the call termination update data to the telecommunication network node via a wired communication link.

25. The method according to claim 21, characterized in that the transmission step further comprises the step of transmitting the call termination update data to the telecommunication network node via a wireless communication link.

26. The method according to claim 25, characterized in that the step of transmitting the call termination update data to the telecommunication network node via a wireless communication link further comprises the step of transmitting the call termination update data. as packet data via the wireless communication link.

27. A method for the operation of a personal information management device comprising a memory that stores personal information data, the method is characterized in that it comprises the steps of: generating call termination update data based on the personal information data; transmit the call termination update data to a telecommunications network node in which the subscriber's call termination data is stored.

28. The method according to claim 27, characterized in that the personal information data comprise program data representing scheduled events.

29. The method according to claim 27, characterized in that the personal information data comprise contact data representing at least one user contact.

30. The method according to claim 27, characterized in that the transmission step further comprises the step of transmitting the call termination update data to the telecommunications network node via a wired communication link.

31. The method according to claim 27, characterized in that the transmission step further comprises the step of transmitting the call termination update data to the telecommunication network node via a wireless communication link.

32. The method in accordance with the claim 31, characterized in that the step of transmitting the call termination update data to the telecommunications network node via a wireless communication link further comprises the step of transmitting the call termination update data as packet data via the link of wireless communication.

33. A method for the operation of a personal information management device comprising a memory that stores program data, representing scheduled events, the method is characterized in that it comprises the steps of: receiving an alert request associated with one of the events cale? Data via a user interface transmit the alert update data based on the alert request to a node of the telecommunications network in which the subscriber's alert data is stored.

34. The method according to claim 33, characterized in that the transmission step further comprises the step of transmitting the alert update data to the telecommunication network node via a wired communication link.

35. The method according to claim 33, characterized in that the transmission step further comprises the step of transmitting the alert update data to the telecommunication network node via a wireless communication link.

36. The method according to claim 35, characterized in that the step of transmitting the alert update data to the telecommunications network node via a wireless communication link further comprises the step of transmitting the alert update data as packet data via the wireless communication link.

37. A method for the operation of a personal information management device comprising a memory that stores program data, which represents scheduled events, the method is characterized in that it comprises the steps of: generating alert update data based on scheduled events; transmitting the alert update data to a node of the telecommunications network in which the subscriber alert update data is stored.

38. The method according to claim 37, characterized in that the transmission step further comprises the step of transmitting alert update data to the telecommunications network node via a wired communication link.

39. The method according to claim 37, characterized in that the transmission step further comprises the step of transmitting alert update data to the telecommunication network node via a wireless communication link.

40. The method according to claim 39, characterized in that the step of transmitting the alert update data to the telecommunications network node via a wireless communication link further comprises the step of transmitting the alert update data as packet data via the wireless communication link.