Method and apparatus for retrieving calling party information in a mobile communications system

Abstract

A method and system for providing calling party identification information to a called party in a mobile communications network. Servers external to the mobile communications network are used to generate and provide calling party information in the form of a service page or phone page without relying on calling line interface information.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority from PCT/SE00/01689 which in turn claims priority from U.S. applications Ser. No. 60/176,806 and 09/644,307.

BACKGROUND OF THE INVENTION

[0002] The present invention generally relates to mobile communications systems. More particularly, the present invention relates to providing calling party identification information to a called party in a mobile communication system.

[0003] In the field of mobile communications, it is known to provide calling party information, which may be in the form of a “service page” or “phone page”, to a called party's terminal. For example, European Patent Application EP 0869688A2 discloses a method and means for transmitting a service page in a communication system. The service page information is provided to, and displayed on, a terminal associated with a telecommunications network using Calling Line Identification Presentation (CLIP) or Connected Line Identification Presentation (COLP). According to the method, a first subscriber sends a call request to a second subscriber, and CLIP information is transmitted to the second subscriber. The second subscriber contacts an Internet Address Server and transmits the CLIP information. The Internet Address Server locates an Internet address corresponding to the CLIP, if available, and transmits the located Internet address to the second subscriber. The second subscriber's terminal then contacts the Internet address and downloads a service page, which is then displayed on the second subscriber's terminal. The service page includes information characteristic of the first subscriber.

[0004] An example of such a system is shown in FIG. 1. A mobile terminal MT1 (associated with network PLMN1) initiates a call to mobile terminal MT(associated with network PLMN2) in step 1 by transmitting a dialed number (corresponding to MT2) to network PLMN1. This step is typically performed when a subscriber (not shown) associated with MT1 inputs the dialed number and pushes a SEND or transmission button on the terminal MT1. After step 1 is performed, the first network PLMN1 sends a message in step 2 to second network PLMN2 requesting that a call be set up with mobile terminal MT2. After step 2 is performed, the second network PLMN2 in step 3 sends a message to second mobile terminal MT2, activating a voice channel to establish the call. The message sent in step 3 also provides an indication of the identity of mobile terminal MT1 in the form of CLI information. Finally, in step 4, the mobile terminal MT2 sends a message to an associated external server PNS2, requesting a service page associated with the calling party based on the CLI information received in step 3.

[0005] There are several drawbacks associated with relying on Connected Line Identification (CLI) to effect service page retrieval. A first problem is that the communication network service provider will typically charge an additional fee for CLI distribution. A second problem is that not every service provider is able or willing to exchange numbers or other identification data when subscribers call between different networks; this potentially makes CLI useless for a large number of subscribers. A third problem is that subscribers cannot control individually whether or not their number or service page is to be shown. For example, some subscribers maintain their number in secrecy; since this number is not transmitted when a call is placed, a corresponding service page cannot be retrieved by other parties. Thus, using the CLI technique, it is not useful for a subscriber having an unlisted or secret identification to have a service page.

[0006] A further problem with conventional calling party identification techniques is that some technologies or systems do not support CLI techniques or may require additional hardware, such as a fixed telephone line. A still further problem with CLI techniques is that if the CLI information is diverted to another number, the CLI information can be lost in some cases.

[0007] It would be desirable to identify a calling party to a called party while avoiding the use of CLI techniques, or in such a way so as to complement or enhance CLI techniques. It would also be desirable to identify a calling party without relying on service providers or the mobile communication networks of the calling and or called parties. It would further be desirable to avoid the problems identified above and to provide additional advantages over conventional CLI-based calling party identification techniques.

SUMMARY OF THE INVENTION

[0008] The present invention overcomes the above-noted problems, and achieves additional advantages, by providing for a method, apparatus, and/or system for providing calling party identification information in the form of a phone page to a called terminal, which either avoids or enhances the use of CLI techniques. According to the embodiments disclosed herein, a first mobile terminal transmits a message to a first external server in conjunction with a triggering event such as the transmission of the dialed number to a first communication network. The first external server determines the identity of both the calling party (first terminal) and the called party (second terminal), and transmits this information to a second external server associated with a second communication network and the second terminal. The transmission of the calling party identification information from the first external server to the second external server allows the called party (second terminal) to retrieve the information without relying on the second network to provide CLI information. In another embodiment, the first and second servers are the same, and the first and second networks are the same.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The present invention can be more fully understood by referring to the following Detailed Description of presently-preferred embodiments in conjunction with the accompanying drawings, in which like reference indicators are used to designate like elements, and in which:

[0010] FIG. 1 is a functional diagram of a conventional call connection process using CLI information;

[0011] FIG. 2 is a functional diagram of a call connection process according to one embodiment of the present invention;

[0012] FIG. 3 is a flow chart describing an exemplary method for handling a call set up in a calling party's terminal, according to one aspect of the present invention;

[0013] FIG. 4 is a flow chart describing an exemplary method for handling a call set up in a first external server according to another aspect of the present invention;

[0014] FIG. 5 is a flow chart describing an exemplary method for handling a call set up in a second external server according to another aspect of the present invention; and

[0015] FIG. 6 is a flow chart describing an exemplary method for handling a call set up in a called terminal according to an additional aspect of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0016] Referring now to FIG. 2, a functional diagram of a call connection process consistent with a first embodiment of the present invention is shown. In FIG. 2, the first, or calling, mobile terminal MT1 transmits (in response to appropriate subscriber input) a called party telephone number (in this example, the telephone number corresponding to second mobile terminal MT2) to a first public land mobile network PLMN1 in step 1. The first network PLMN1 transmits a message to the second network PLMN2, instructing PLMN2 to establish a voice channel for communication with second terminal MT2 in step 2. In step 3, the second network PLMN2 sends a message to second mobile terminal MT2 to activate a voice channel and, optionally, provide supplemental information such as CLI information. In step 4, the second mobile terminal MT2 transmits a message to a second phone page number service (e.g., a server external to the PLMN communication network) PNS2 to retrieve a service page or phone page containing information about the calling party. It will be appreciate that the foregoing steps 1-4 are substantially the same as in FIG. 1.

[0017] According to one implementation of the present invention, substantially simultaneously with the transmission of the calling information to PLMN1, the first mobile terminal MT1 also transmits a data object request signal to a first external server PNS1 in order to retrieve a data object such as a phone page containing information about the called party associated with the second mobile terminal MT2 in step A. Note that this transmission in step A can be performed by first terminal MT1 at the same time as the transmission of the calling information, or can be performed just prior or just after the transmission of the calling information (for example, to avoid using too much of the mobile terminal's limited available power at one time). As a result of step A, the first external server PNS1 now knows or can derive (e.g., by using a procedure such as is described in the copending, commonly-assigned application entitled “Method and Apparatus for Location Event Based Information”, having Ser. No. 09/660,055, the entirety of which is incorporated by reference) the public identity of both the first and second mobile terminals MT1 and MT2. The first external server PNS1 retrieves, derives, or otherwise obtains the identity information and transmits this information to the second external server PNS2 over a second communication link independent of the link or channel used to transmit information between the first and second external servers in step 2. Preferably, the timing of transmissions in steps A and B is such that the information containing the identity and/or phone page information for the calling party is provided in step B to the second external server PNS2 before steps 2, 3, and 4 are completed, so as to allow the second external server PNS2 to provide requested phone page information to the second mobile terminal MT2 substantially immediately, or at least sooner than having to derive the phone page information based on CLI information transmitted to the second network PLMN2 in step 4.

[0018] Note that the requested phone page information can include a pointer or address of a phone page, or the actual phone page itself.

[0019] In an alternative embodiment, the second network PLMN2 can be set up (e.g., by appropriate software programming) to provide the phone page information requested in step 4 by either using the CLI information (if this has been provided to the second mobile terminal MT2 in step 3 and provided to the second external server PNS2 in step 4), or using the phone page information provided by the first external server in step B, whichever occurs first or which results in the requested phone page information being provided to the second mobile terminal MT2 in the shortest period of time.

[0020] Referring now to FIG. 3, a flow chart describing a method performed by the first mobile terminal MT1 in the embodiment of FIG. 2. Such a method can be implemented using a suitably programmed processor resident in the mobile terminal MT1. In step 30, the mobile terminal receives an input (e.g., via a keypad) of a telephone number to be called. In step 32, the mobile terminal receives a SEND or similar command to initiate a call to the called telephone number. In step 34, the mobile terminal transmits an appropriately-formatted signal, including the called telephone number, to the first network PLMN1. Substantially simultaneously with step 34, the mobile terminal in step 36 transmits a data object request (e.g., for a phone page corresponding to the called mobile terminal) to the first external server PNS1. It will be appreciated that step 36 can be performed just prior to, simultaneously with, or just after step 34, with the goal being to ensure that the first external server PNS1 can provide phone page information for the calling terminal MT1 to the second external server PNS2 before the second external server receives the phone page request from the second terminal MT2. In step 38, after a voice channel has been established with mobile terminal MT2, the mobile terminal MT1 receives communication from mobile terminal MT2.

[0021] Referring now to FIG. 4, a flow chart describing a method performed by the first external server PNS1 in the embodiment of FIG. 2. Such a method can be implemented using a suitably programmed processor resident in the first external server PNS1. In step 40, the first external server receives a phone page request, including a called number for which a phone page or other data object is desired, from mobile terminal MT1. In step 42, the first external server determines, from the phone page request, identification information for both the calling terminal MT1 and the called terminal MT2. In step 44, the first external server transmits the identification information for the calling terminal MT1 to the second external server PNS2 which is associated with the called terminal MT2. In step 46, the first external server returns requested phone page information for the called terminal MT2 to the requesting terminal MT1. It will be appreciated that sequence of steps 40-46 can be revised as necessary, preferably keeping in mind the goal of providing the identification information for MT1 to the second external server prior to the second external server's receipt of a phone page request from the second terminal MT2.

[0022] Referring now to FIG. 5, a flow chart describing a method performed by the second external server PNS2 in the embodiment of FIG. 2. Such a method can be implemented using a suitably programmed processor resident in the second external server PNS2. In step 50, the second external server PNS2 receives identification information for the calling terminal MT1 from the first external server PNS1. The identification information can be the phone page information for terminal MT2 or can be information which allows the second external server PNS2 to derive the phone page information for the terminal MT2. In step 52, the second external server PNS2 receives a phone page request from called terminal MT2. In step 54, the second external server PNS2 determines whether the phone page request includes CLI information. If CLI information is included, the second external server responsively generates and provides the requested phone page information using: 1) the calling information received in step 50, or 2) the CLI information provided in step 54, whichever provides the fastest result. If the CLI information is not included in the phone page request from the second terminal MT2, the second external server PNS2 responsively provides, in step 56, the requested phone page information based on the information received in step 50. It will be appreciated that step 54 can be omitted, and the second external server can automatically provide the requested phone page information based solely on the information received in step 50.

[0023] Referring now to FIG. 6, a flow chart describing a method performed by the second, called mobile terminal MT2 in the example of FIG. 2. Such a method can be implemented using a suitably programmed processor resident in the second mobile terminal MT2. In step 60, the second mobile terminal MT2 receives a channel set up request signal (which may or may not include CLI information) from the second network PLMN2, which is the current service provider for the terminal MT2. In step 62, the mobile terminal MT2 completes the communication link with mobile terminal MT1 via networks PLMN1 and PLMN2. In step 64, the second mobile terminal transmits a phone page request to the second external server PNS2, requesting the phone page corresponding to the calling party. As indicated above, the phone page request may or may not include CLI information, depending upon whether or not the channel set up request includes the CLI information. In step 66, the second mobile terminal MT2 receives the requested phone page information.

[0024] The foregoing description has focused on a call as a triggering event to initiate the processes in the foregoing embodiments. It should also be appreciated that other triggering events can trigger the processes above. Such triggering events can include, by way of example, the following:

[0025] An outgoing call is or is about to be initiated.

[0026] An addressed B-party answers a call.

[0027] An incoming call is imminent or has just started.

[0028] A conference call is or is about to be initiated.

[0029] A call is disconnected

[0030] A call is conducted (under which several triggering events can be generated).

[0031] A subscriber is put on hold.

[0032] A new cell in the PLMN has been selected.

[0033] The location of a subscriber has changed.

[0034] A new Public Land Mobile Network (PLMN) operator is selected.

[0035] A new country of registration is made.

[0036] A UE is about to be switched off.

[0037] A UE has been switched on.

[0038] When a designated button on a UE is pressed.

[0039] In response to a talk spurt received by a UE.

[0040] A voice mail has been left to a subscriber.

[0041] An SMS has been sent or received by a subscriber.

[0042] Further, information indicative of which “triggering event” initiated the phone page process can be transferred to MT2 (via suitably-programmed software instructions).

[0043] While the foregoing description includes numerous details, it will be understood that these are provided solely for purposes of explaining the presently-preferred embodiments of the present invention. Such details should not be deemed to constitute limitations of the invention, as the embodiments described above can be varied in many ways by those skilled in the art without departing from the spirit and scope of the invention, as defined by the following claims and their legal equivalents.

Claims

1. A method for communicating between first and second communication devices, comprising:

receiving, at a server associated with the first communication device, a first signal from the first mobile communication device, the first signal including at least an identity of the second device;

identifying a server associated with the second mobile communication device;

rendering a data object from the first signal; and

forwarding the data object to the server associated with the second device.

2. The method of claim 1, wherein the first signal includes a dialed number corresponding to the second mobile communication device and an identification of the first mobile communication device.

3. The method of claim 1, wherein the data object is rendered without using calling line interface (CLI) information.

4. A method for communicating between a first communication device and a second communication device, comprising the steps of:

identifying, at the second communication device, the occurrence of a triggering event;

transmitting to a first server associated with the second communication device a request for a data object associated with the first communication device;

generating the requested data object in the first server based on calling information provided by a second server associated with the first communication device; and

receiving the requested data object from the first server.

5. The method of claim 4, wherein the triggering event does not include calling line identification information.

6. The method of claim 4, wherein the triggering event includes a calling line identification information, but wherein the requested data object is not derived on the basis of the calling line identification information.

7. A method for communicating between a first and a second mobile communication device, comprising the steps of:

identifying the occurrence of a triggering event;

transmitting a data object request including calling line interface (CLI) information, to a server associated with the second mobile communication device;

determining whether the requested data object can be generated based on the CLI information or the calling party information faster, and generating the requested data object using the faster technique; and

receiving the requested data object from the server.

8. The method of claim 7, wherein the data object includes a pointer to the phone page associated with the second device.

9. The method of claim 7, wherein the data object includes a phone page associated with the second device.

10. The method of claim 7, wherein the data object comprises the public identify of the second device.