On line notification in mobile communication system

BACKGROUND

The present invention relates to mobile Communications Systems, more 5 particularly to Services that are provided to users of a mobile Communications System, and even more particularly to techniques for informing a mobile Communications System user of the Status of other users in the System. As the user base of wireless (mobile) Communications Systems continues to grow, so do the number and types of Services that such Systems can offer. No longer are mobile communication devices limited to providing just the traditional voice communication Services. Instead, Services such as paging, e-mail, general data transmission, chat-programs and even general purpose browsers are becoming more commonplace as devices such as Personal Digital Assistants (PDAs) and other types of intelligent mobile terminals are introduced into the marketplace.

One problem that currently exists in the mobile communication environment is the inability of a calling party to know whether an intended recipient of a phone call has his or her telephone "on-line" (i.e., switched on or within ränge), thereby enabling that intended recipient to answer/receive the call. SLmilar problems exist with respect to other types of Communications as well, such as with a Short Message Service (SMS) message. In the case of an SMS-message, the calling party presently has no way of knowing whether the intended recipient is presently on-line, thereby increasing the probability that he will actually read the transmitted message now, or whether the intended recipient is presently off-line, thereby increasing the likelihood that the message will be read at some time in the (possibly) distant future.

The problem with this lack of information is that, whenever a person makes a call, it takes some seconds to dial the number, some more seconds for the System to call the B-party, and then still more seconds either for the B-party to answer or for the system to notify the calling party (the "A-party") that the user cannot be reached at the moment because, for example, the phone is not switched on. While the amount of time involved in making an uncompleted call might, at first, seem trivial, it can add up to a substantial number of minutes when one considers how many uncompleted calls are attempted in any given day. If the calling party were to know, ahead of time, that a call could not presently be completed, then the attempt would not be made and the time involved could be saved for more productive activities.

There are a number of Solutions to this problem in the wireline Internet world. For example, a product called ICQ is a known Internet tool that provides information about who is on-line at any given time, and enables a user to contact these individuals. However, because of fundamental differences between the wireline Internet infrastructure and that which is found in the mobile Communications world (e.g., cellular telephone environments), the known wireline-based Solutions are not functional in the wireless world. Techniques where a caller is able to determine the status of a wireless terminal from a data terminal before attempring to communicate with that terminal are described in WO 9713382.

Therefore, it is desired to provide a mechanism for a calling party in a mobile communication System to know, ahead of time, whether an intended recipient of a call or other transmission is presently capable of receiving an anticipated call or other transmission.

SUMMARY

It is therefore an object of the present invention to provide nodes and techniques for notifying mobile users of various Status conditions associated with other mobile users. The claimed invention is descibed by independent method and apparatus claims 1, 2, 5 and 6.

The foregoing and other objects are achieved in nodes and methods for notifying a first user of a mobile communication device about Status of other users in a mobile Communications system. In one aspect of the invention, such nodes and methods include receiving a signal from the mobile communication device to a Service node. At the Service node, a list is determined that indicates other users that the first user wants to know the Status of. The Status of each of the other users on the list is then determined, and the Status is transmitted from the service node to the mobile communication device.

In another aspect of the invention a method and node includes receiving a signal from the mobile device, wherin the signal indicates the status of a first user, and determining in response to the signal, lists of users in which the first user is listed. Determining, for each of the lists of users, a corresponding other user to which the list belongs; and sending a notification to each of the corresponding other users indicating the status of the first user.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the invention will be understood by reading the following detailed description in conjunction with the drawings in which: <ul id="ul0001" list-style="none" compact="compact"><li>FIGS. 1a, 1b and 1c illustrate an exemplary wireless on-line notification service from a user's point of view, in accordance with one aspect of the invention;</li><li>FIGS. 2a, 2b and 2c are block diagrams of exemplary embodiments of a System for effecting a wireless on-line notification service in accordance with several aspects of the invention;</li><li>and FIGS. 3a, 3b, 3c, 3d and 3e illustrate wireless on-line notification-related signaling between a mobile Station and a service node in accordance with several aspects of the invention.</li></ul>

DETAILED DESCRIPTION

The various features of the invention will now be described with respect to the figures, in which like parts are identified with the same reference characters.

Exemplary Wireless On-Line Notification (WOLN) techniques and apparatuses will now be described. Referring first to FIGS. 1a, 1b and 1c, these illustrate an exemplary WOLN service as it might be seen from a user's point of view. In accordance with one aspect of the invention, the user has established a list ofindividuals whose Status is of interest to him. This type of list will be referred to in this disclosure as a "Notify Me" list. The listed individuals may be potential recipients of a call, a data transmission, or virtually any other type of communication from the user. Merely for the sake of example, this "Notify Me" list will be assumed to includethe names of three individuals: Peter, Anna and Sarah. Of course, the user could have predefined more or fewer individuals in the list. In Operation, the user's wireless device, such as the mobile Station (MS) 101 depicted in FIG. 1a, obtains information from a remote Server (not depicted in FIG. la) that checks through the predefined "Notify Me" list and determines, for each of the listed individuals, whether they are presently capable of responding to an anticipated call or other transmission from the user. If so, this Status is reflected on a display portion 103 of the MS 101.

FIGS. 1b and 1c are enlarged views of the display portion 103 of the MS 101, as seen at different stages of the WOLN service. In the example of FIG. 1b, the display portion 103 of the MS 101 indicates the names Peter, Anna and Sarah. Next to each name is a blank box, which is defined to indicate that the corresponding named individual is presently incapable of responding to any call (or other transmission) from the user. Armed with this knowledge, the user can save himself wasted efforts at trying to reach any of these individuals.

FIG. 1c depicts a Situation in which the individual named Peter has just gone on-line (e.g., by turning on the power to his mobile device). In response to this Situation, the remote Server transmits this Information to our user's MS 101, which responds by filling in the box associated with Peter's name in the display portion 103. 5 The user now knows that Peter is capable of responding to any call or other transmission that the user may initiate. Of course, the use of blank or filled-in boxes to represent this information is merely an example, and other techniques for representing this information (such as including complete text) could easily be used instead.

Taking a high-level look at the WOLN application (which resides both in the user's device and in the remote Server), it should perform the following tasks (not necessarily in the Order indicated) : <ul id="ul0002" list-style="none" compact="compact"><li>1) When the user (whose identity will henceforth be represented by the all-uppercase term "USER") turns on his wireless device, the wireless device notifies the server that USER has gone on-line.</li><li>2) The Server then obtains the current Status (e.g., "on-line", "not on-line") for each of the individuals defined in USER's "Notify Me" list (which is a list of other users that USER has previousiy defined and which is kept in a WOLN database). This information is transferred to USER's mobile device.</li><li>3) The server may also examine its WOLN database to identify which other lists include the names of this USER. Each of these other lists belongs to a corresponding other user. The server, therefore. notifies each of the other users who are presently on-line that "USER has gone on-line." The process of identifying which other lists include the names of this USER may be performed dynamically by examining each of the "Notify Me" lists in the system, and determining which of these    include the USER's identity. The owners of these identified lists are then notified of USER's change in Status. In an alternative embodiment, the processing involved in dynamically determining who to notify in the event of a user's change in Status may be substantially reduced by creating and maintaining a second type of list, herein referred to as a "Notify Others" list. In such an embodiment, each user has his own "Notify    Others" list in addition to the "Notify Me" list described above. The contents of the    "Notify Others" list is a list of users who should be notified whenever a particular user's Status changes. In the above example, USER's "Notify Others" list includes the identity of those other users whose own "Notify Me" lists include the identity of USER.</li><li>4) When USER turns his mobile device off, a notification of this event is sent to the Server. The Server responds by examining its WOLN database to identify which other "Notify Me" lists include the names of this USER. (In one embodiment, this task is greatly simplified by using the Contents of USER's "Notify Others" list described above.) As mentioned above, each of these other "Notify Me" lists belongs to a corresponding other user. The server, therefore, notifies each of the other users who are presently on-line that "USER has gone off-line." Of course, when USER is on-line and one of the individuals on his predefmed list goes off-line, this information may be similarly forwarded to USER's mobile terminal, so that USER can be kept apprised of the most recent Status of the named associates.</li></ul>

FIGS. 2a, 2b and 2c are block diagrams of exemplary embodiments of asystem for effecting a WOLN service. The user's wireless device in these examples is a mobile Station 201 (designated MS-A in the figures), but could easily be any other type of wireless device (e.g., a PDA) that includes appropriate hardware and Software (WOLN Subsystem 203) for working with the WOLN application. Referring first to an    embodiment illustrated in FIG. 2a, the MS-A 201 includes a radio frequency (RF) part 205 for communicating with a base Station (BS) 207 via an air interface 209 in accordance with known techniques that need not be described here in detail. The BS 207 is, in turn, coupied to a Mobile Switching Center (MSC) 213 by means of a pulse code modulation (PCM) link 211, which may be a Standard EI/TI link. The MSC 213 is coupied to a second PCM link 215 for communication with a service node that, in this embodiment, is a combination Home Location Register (HLR) / WOLN database 217. (The indications of HLR's throughout this description is merely for illustrative purposes. Those having ordinary skill in the art will recognize that any equivalent equipment could be substituted for the indicated HLR's.) The BS 207, PCM links 211,    215 and MSC 213 are well-known in the art (e.g., in the Global System for Mobile communication (GSM)), and need not be described here in detail. Considering only the HLR functions of the combination HLR/WOLN database 217, these are also well-known, and need not be described here in detail.

The WOLN application is primarily supported by the WOLN Subsystem 5 203 in the MS-A 201, and by the WOLN database portion of the service node (in this embodiment, the combined HLR/WOLN database 217). The WOLN Subsystem 203 controls the MS-A's display portion 103, and sends and receives appropriate signaling (described in further detail below) to/from the WOLN database portion of the combined HLR/WOLN database 217. The intermediate elements in the System (e.g., the BS 207 and MSC 213) also support the WOLN application to the extent that they forward WOLN-related information between the MS-A 201 and the combined HLR/WOLN database 217. However, this function would be readily apparent to one having ordinary skill in the art, and will not be described here in detail.

The system illustrated in FIG. 2a permits an HLR to be used to provide all of the information needed to implement a WOLN service (i.e., the WOLN service node is within the HLR itself). The service provided by this embodiment is limited, however, in that it works only for terminals within the same HLR, which most commonly means users of the same Operator. In order to provide the service among different Operators, alternative embodiments are used. In one alternative, illustrated in FIG. 2b, a service node 219 is separate from the HLR 217'. The service node 219 includes all of the data and service node control Software associated with the WOLN service, and is accessible to HLR's from many different Systems. As a result, the WOLN service can inform users of the status of other users across System boundaries. The HLR 217' in this embodiment Stores information pertaining to whether a given subscriber has the WOLN service in much the same way that it retains information about whether the subscriber has other Services, such as call forwarding. However, the actual Status information for a user (e.g., whether a user is on-line or not) as well as the various lists ("Notify Me" and possibly "Notify Others") are stored in the service node.

The embodiment of FIG. 2b has a drawback in that the service node 219 may become a huge database. This problem is addressed in another alternative embodiment, illustrated in FIG. 2c. Here, a plurality of combined HLR/WOLN databases 217"-1 . 217"-n operate as described above with respect to the combined 5 HLR/WOLN database 217 of FIG. 2a, but in addition, are each connected to a superior service node 221, which passes on questions and information from one HLR/WOLN database to those of different Operators. In this way, knowledge of the Status of all users can be distributed throughout a number of separate Systems. Logically, this looks very much like a global HLR, but requires much less equipment, and doesn't include the drawback of requiring a giant database, although some storage Space is needed. The WOLN-related signaling between the MS-A 201 and the service node (e.g., the combined HLR/WOLN database 217 of FIG. 2a, the service node 219 of FIG. 2b, or the combined HLR/WOLN database 217" of FIG. 2c) will now be described by way of several examples. In each of these, the "HLR" and "ServiceNode/WOLN Database" represent logical functions, and as such, are depicted as separate entities. However, as has been explained, these two logical functions may or may not physically reside in a common node.

Referring first to FIG. 3a, a power-on sequence will be described. In response to the MS-A powering on (step 301), it sends a message communicating this fact to the HLR (step 303). The HLR then passes this information along to the service node (step 305), which responds by reporting this change in Status to those other users who are designated in MS-A's "Notify Others" list 306. As explained earlier, the HLR Stores an indication of whether or not a user subscribes to the WOLN service. If the user is a WOLN subscriber, the HLR sends a query to the service node regarding who of MS-A's associates ("friends") are presently on-line (step 307). In this example, the System node examines MS-A's "Notify Me" list 308, and consequently determines that friends B, C and D are on-line, and passes this information back to the HLR (step 309). The HLR, in turn, Signals this information to the MS-A (step 311). The WOLN Subsystem 203 in MS-A then causes the display portion 103 to indicate that friends B, C and D are on-line (step 313).

A user who is on-line may be informed of another user's change in Status, such as that other user's Coming on-line. The signaling associated with this example is depicted in FIG. 3b. Here it is assumed that MS-A is already on-line, and that another telephone (designated MS-E) turns on (step 315), belonging to a user "E" who is also on MS-A's "Notify Me" list. Because each of the MS's in this example follows the same principles, the Service node is notified of MS-E's Coming on-line (step 317) in much the same way that the Service node was informed when MS-A was turned on. In addition to its further communication with MS-E (not shown), the Service node recognizes that user E is on MS-A's list (e.g., by detecting that MS-A is listed on MS-E's "Notify Others" list (not shown)), and consequently sends a message to the HLR indicating that the MS-E has turned on and that MS-A wants to know this information (step 319). The HLR responds by sending a message to MS-A, telling it that MS-E has turned on (step 321). In response to receipt of this message, the WOLN Subsystem causes the display portion 103 to indicate that user E is on-line (step 323).

Another Status change that may warrant notification is going off-line. The signaling associated with this notification is illustrated in FIG. 3c. Here, one of the mobile devices (MS-C) that user A is interested in goes off-line (step 325). This information is passed along to the Service node (step 327), which recognizes that user C is on MS-A's list (e.g., by detecting that MS-A is listed on MS-C's "Notify Others" list (not shown)), and consequently sends a message to the HLR indicating that the MS-C has turned off and that MS-A wants to know this information (step 329). The HLR responds by sending a message to MS-A, telling it that MS-C has turned off (step 331). In response to receipt of this message, the WOLN Subsystem causes the display portion 103 to indicate that user C is off-line (step 333).

In addition to signaling associated with notifications, such as thoseillustrated above, there is also signaling associated with setting up and maintaining a list. In the signaling example of FIG. 3d, the user of MS-A 201 wants to build up his list of other users (i.e., his "Notify Me" list). He may indicate this by, for example, pressing an associated key or key combination on his telephone (step 335). Of course, other types of user input selection techniques, such as menu selection techniques, may be used as an alternative. His telephone (MS-A 201) allows him to enter the identities of the other users he wants to have in his initial list, or alternatively, to add to an existing list. In this example, the other users are designated G, H, I and J. The MS-A 201 sends a message to the HLR indicating that he wants to set up a list with MS- G, H, I and J in it (step 337). The HLR forwards this Information to the Service node (step 339). The Service node responds by establishing a new "Notify Me" list designating MS-G, H, 1 and J, or alternatively, adding MS-G, H, I and J to an existing "Notify Me" list (step 341). In those embodiments employing a "Notify Others" list, the Service node may further respond by locating the "Notify Others" lists respectively belonging to MS-G, H, I and J, and adding MS-A to each of these lists.

In a final signaling example, the user of MS-A wants to remove another user from his "Notify Me" list. He may indicate this by, for example, pressing an associated key or key combination on his telephone (step 343). Of course, other types of user input selection techniques, such as menu selection techniques, may be used as an alternative. In this example, the other user to be removed is designated K. The MS-A 201 sends a message to the HLR indicating that he wants to remove MS-K from the list (step 345). The HLR forwards this information to the Service node (step 347). The service node responds by removing MS-K from MS-A's "Notify Me" list (step 349). In those embodiments employing a "Notify Others" list, the service node may further respond by locating the "Notify Others" list belonging to MS-K, and removing MS-A from this list.

The techniques and apparatus described above may be applied to implement a number of different variations of WOLN Services. In a simple case, the WOLN service gives a user information about who is presently available to accept a call (or other transmission), thereby eliminating wasted efforts at reaching people who will not respond.

In another application, the WOLN service not only informs the user about who eise is presently available to accept a call, but also indicates whether any of these individuals subscribe to, for example, a voicemail service. Armed with this knowledge, the user might call a person who is known to be off-line because the user knows that it is not a wasted effort - he can always leave a message. This additional service is relatively simple to implement because Information about whether or not a person has voicemail already resides in the HLR in most cellular Communications Systems.

In yet another application, the WOLN service can provide Information indicating whether a person has an e-mail service connected to his telephone, voicemail or SMS. With this knowledge, the user can decide to transmit a written message rather than attempting to establish a voice call.

Many other applications of the WOLN service are possible. For example, mobile Communications Systems are shortly expected to maintain information about the location of mobile subscribers. If a PDA with a large enough memory to störe displayable maps were utilized, the WOLN service could supply information about a person's present whereabouts, and this information could be indicated graphically on a user's PDA.

In each of the above-described (and other) applications of the WOLNservice, the System can provide security/confidentiality by giving each mobile subscriber the choice of being on another user's "Notify Me" list or not. The default can be set to "not permitting listing on another user's list", and each subscriber can override this default. It is also possible to provide an authorization function. If user A wants to have user B on his "Notify Me" list, then, before any lists are updated, a message is passed to user B asking whether this is acceptable. If user B accepts being named on user A's "Notify Me" list, then this permission is transmitted back to the service node which Updates user A's "Notify Me" list accordingly. Otherwise, the service node will not permit user A to add user B to user A's "Notify Me" list.

Another consideration with respect to the. WOLN service is how toimplement the necessary signaling. Existing mobile phones can do this in several ways. One way is to utilize the control Channel. However, this approach would probably get overloaded very soon. As an alternative, the SMS service could be used, because it does not require that many bytes be sent over the air interface. In future Systems, the proposed schemes for packet data can advantageously be used because they are more efficient than present signaling methods, and can handle the capacity requirements.

Yet another consideration with respect to the WOLN Service is that it can add a lot of signaling to the mobile Communications System. Of course, one technique for addressing this concern is to build up the infrastnicture capacity to cope with the increased load. Another approach is to modify the way the WOLN Service operates from the user's point of view, so that the user Orders a snapshot of his list of people. For example, the user might press a button or activate the "snapshot" function via a menu system in the phone (or PDA). When activated, the system returns data about the people on the list only once, instead of every time someone's Status changes.

Another consideration, which is unique to the mobile environment, is how to handle the Situation when someone who is on-line temporarily moves into a location having bad radio coverage (e.g., a road tunnel or an elevator). To the mobile Communications System, it appears that this person has become unavailable. With the WOLN system as described above, this information would then be signaled to every other user whose "Notify Me" list includes this particular user. However, the mobile user soon becomes "available" again because his Situation was just temporary (e.g, he leaves the tunnel or elevator). This subsequent change in Status would again initiate a signaling activity to all those having this subscriber on their "Notify Me" list. It isapparent that the benefits of having instantaneous information about the user may not outweigh the bürden that this extra signaling imposes on the system. As one solution to this problem, a reporting delay may be introduced to filter out transient changes in Status. For example, when a mobile subscriber suddenly goes off-line, the system might wait, say, two minutes, after which time it checks to see whether the subscriber is still off-line. If he is, then his off-line Status may be considered permanent enough to report to others. However, if he is back on-line, then no signaling is performed. The "Notify others" list has beeen described as a list that is associated with a particular user. However, alternative embodiments may be devised in which a master "Notify Others" list resides at a central cite, such as the service node 219. In such embodiment, each list entry might be addressed by specifying a user of interest, and entry itself would be the list of other users who should be notified of changes in status of the user of interest.