WO2009026967A1

WO2009026967A1 - Improvements in or relating to calling and called name presentation

Info

Publication number: WO2009026967A1
Application number: PCT/EP2007/059109
Authority: WO
Inventors: Joerg Kottig; Aqueel Ahmed Siddiqui
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2007-08-31
Filing date: 2007-08-31
Publication date: 2009-03-05

Abstract

A method of controlling presentation of user information, from a first user to a second user, wherein the first and second users are connected to a wireless network having at least one network node for each user, the method comprising the steps of: - retrieving the user information from a database during a location update (LU) process for the first user, - storing the user information at an Visitor Location Register to which the first user is connected, - transmitting the stored user information from the Visitor Location Register to a terminating node to which the second user is connected for presentation of the user information to the second user

Description

Title of the Invention: Improvements in or relating to calling and called name presentation.

Technical Field

The present invention relates to improvements in or relating to calling and called name presentation.

Background

In the telecoms environment a service exists that is called calling name presentation (CNAP). This service deals with the retrieval, storage and delivery of a calling subscriber's name or other information during a call setup. Typically this information is retrieved from a name database (NADB) which is external to the network. The CNAP service is relevant to at least GSM, WCDMA, circuit switched (CS) and packet switched (PS) networks.

Figure 1 shows an example of how calling name is retrieved from an external name database 100 during a communication between the calling mobile 102 and a called mobile 104 so that the calling name of the calling mobile can be displayed to the called mobile. The calling name information is retrieved during the call setup by the originating node 106, a transiting node 108 or the terminating node 110. Wherever the request for the name information originates is an extra signalling load in order to request and deliver the name information from the database 100.

For the wireline networks in North America there are two main retrieval methods for obtaining calling name information. These are generally referred to as the ANSI TCAP method and the ISUP method. ANSI TCAP stands for American standards Institute, Transactions Capability Applications Part, whilst ISUP stands for ISDN (Integrated Systems Digital Network) user part. In the ISUP method the calling party name is included in the ISUP IAM message in the generic name parameter, by the originating exchange. In the TCAP method the calling party name is not included in the ISUP IAM message and the terminating exchange obtains the name from an external database. For wireless networks, such as the 3GPP specification the retrieval method is not specifically specified in the standard, however the service is a required service and needs to be addressed.

The above described methods of name retrieval during the call setup stage have a number of disadvantages. This can include a delay in the call setup phase when the originating or transit node retrieves the name string from an external node during call setup. It is particularly disadvantageous for emergency calls. In addition there is significant increase in signalling traffic during the call setup phase when requesting and answering each name query made to or from the external node.

Summary

Accordingly one object of the present invention is to provide a solution to at least some of the problems associated with the prior art in respect of mobile networks.

According to one aspect of the present invention, there is provided a method of controlling presentation of user information, from a first user to a second user, wherein the first and second users are connected to a wireless network having at least one network node for each user, the method comprising the steps of:

- retrieving the user information from a database during a location update (LU) process for the first user,

- storing the user information at a Visitor Location Register (VLR) to which the first user is connected,

- transmitting the stored user information from the VLR to a node to which the second user is connected for presentation of the user information to the second user.

An advantage of this invention is that calling or connected name or other relevant information is made available with the minimum amount of processing requirements and signalling effort. Not only can calling name string be retrieved but also connected name, pictures, text, sounds, and other data. By storing personal information at the Visitor Location Register (VLR) where the user is located enables considerably more flexibility than would have been the case with the prior art. In addition as long as the subscriber is located at a specific VLR there is no need to retrieve further name information except for on a periodic refresh basis or the like. The name string (or other information) stored in the VLR would be available for additional future services such as intelligent networks and IMS services that may make to use of this information.

According to a second aspect of the present invention there is provided an apparatus for controlling the presentation of user information from a first user to a second user, wherein the first and second users are connected to a wireless network having at least one network node for each user, the apparatus comprising at a network node to which a first user is connected:

- an access unit for retrieving and storing user information from a database during a location update (LU) process for the first user,

- a processing unit for transmitting the stored user information to a second node to which the second user is connected for presentation of the user information to the second user.

Brief description of the drawings

Reference will now be made, by way of example, to the accompanying drawings, in which:

Figure 1 is a block diagram showing a call name presentation process in accordance with the prior art.

Figure 2 is a block diagram of a call name retrieving system according to one embodiment of the present invention.

Figure 3 is a diagram of a first node in the system of figure 2 according to one embodiment of the present invention.

Figure 4 is a diagram of a second node in the system of figure 2 according to one embodiment of the present invention. Figure 5 is a flow diagram of the methods steps according to one embodiment of the present invention.

Figure 6 is a signalling diagram to demonstrate a method of signalling according to one embodiment of the present invention.

Detailed description

The calling name presentation (CNAP) feature enables the called party who has subscribed to the CNAP supplementary service to see the calling party's name on the terminal display. The calling name is fetched during call setup from a database and then delivered to the called terminal. It is a purpose of this invention to enhance the existing CNAP feature to retrieve the name of the calling subscriber in a manner that reduces the signalling effort. By making the calling subscriber name available in the mobile originating mobile switching centre (MSC) and visitor location register (VLR), the name can be deployed to other network nodes without extra signalling effort. It will be appreciated that this principle need not be limited to storage and retrieval of the calling name string only, but could be also used for pictures, text, sounds and other data. Furthermore the method supports the delivery of the connected name (possibly including pictures text etc) to the originating terminal as well.

Referring to figure 2, a system for providing calling name retrieval during location update is illustrated. A subscriber (A) is using a calling mobile 200 to call a called mobile 202 of the subscriber (B.). The A subscriber is connected to a mobile switching centre (MSC) 204 which is in contact with a visitor location register (VLR) 206. The visitor location register is connected by any appropriate means to the home location register (HLR) 208 of subscriber A and the name database (NADB) 210. The call from subscriber A to subscriber B is made via the gateway mobile switching centre (GMSC) 212. The GMSC is in contact with the MSCA/LR of subscriber B 214 and the home location register (HLR) of subscriber B 216. The HLR is also in contact with the MSCA/LR and the MSCA/LR is in contact with the name database.

The calling name is retrieved and located in the visitor location register (VLR) 206 during the location update process. Other information or subscriber data may also be retrieved at the same time, for example pictures, text, sounds, video, etc. the name string that is retrieved, could be received from either the external name database 210 or from the home location register serving the calling subscriber 208. This first case would require a new interface between the VLR 206 and the external name database 210. This second case would require changes to the mobile application parts (MAP) procedure "insert subscriber data (ISD)", in order to support the delivery of the name string to the VLR during location update. The second case, where the name information is stored in their home location register is the preferred of the two options, as it has additional benefits in providing name information to the GMSC, as will be described in greater detail below. Accordingly the name string is stored in the serving VLR as long as the calling subscriber is connected to that VLR. The name string can be refreshed periodically as defined by either the VLR or the subscriber. As will be appreciated, when the subscriber moved to a different visitor location register, it will be necessary for the new visitor location register to fetch the name data or other information as may be the case. This can be carried out during the first location update after the handover procedure has been carried out between the old and new visitor location register.

The mobile switching centre which is connected to a particular visitor location register can convert the name string into an ISUP parameter, which is called "Generic Name" (GN). If this generic name information is not required by certain nodes or networks, it can be screened out by the mobile switching centre or one of the nodes en route to the final destination during the call setup process.

There will be times when the calling name (or other) information will not be readily available, for example when a call enters a public land mobile network (PLMN) from a PSTN or the information is somehow lost in transit. In this case the GMSC or the terminating MSC will be required to execute an information query to determine the calling name information. The query from the GMSC will be carried out as follows:

• the GMSC sends the calling party number while sending "send routing info" to the HLR; • if the calling subscriber belongs to the same HLR, and the HLR has calling party name, the HLR will send the name in the "send routing info Ack" message.

In this way the GMSC will be able to retrieve calling name information without requiring any additional query, thereby reducing signalling. In certain cases the GMSC will not get the name from the HLR and in these situations it will be the terminating MSC that will carry out the query. The amount of signalling that this will require is considerably less than in current procedures.

The invention thus provides a system and a method by which calling name (or other information objects) could be stored in the VLR after the location update has occurred. The information could be used for several purposes, including the calling name presentation feature or other features like intelligent network or IP multimedia services. By utilising the above described method delays associated with additional call setup time for calls originating from a mobile network will be minimised. As long as the subscriber is located at a specific VLR there is no need to retrieve further name information, except for periodic refresh or the like.

The calling name would be available with considerably reduced signalling effort. In addition if the calling name or other information is stored in the HLR the only requirement is an additional parameter to be sent from the HLR to the VLR during the location update interface (MAP, ISD procedure). The information may be stored in a database on the VLR node.

The names string stored in the VLR would be available for additional future services such as intelligent network services and IP Multimedia Subsystem (IMS) services that make use of the name information. Additional information may also be stored in the VLR as previously indicated, such as pictures, sounds, Logos, text etc so that they are available if required.

Figure 3, shows the node of the network corresponding to the VLR 206 in figure 2. The calling mobile 300 makes a wireless connection with the VLR 302. The VLR may contact the HLR of the calling mobile and/or the name database (NADB) during the location update process in order to retrieve calling name information. This information relating to calling name is then transmitted via, for example, the GMSC to the called mobile at a visitor location register or a home location register as the case may be.

Similarly, figure 4 shows the node of the network of the called mobile that corresponds to the B-MSCA/LR 214 in figure 2. In figure 4 so-called mobile 400 is connected to an MSCA/LR 402 in the vicinity of the called mobile. This node receives calling name information via any appropriate node in the network, for example the GMSC. Similarly this node can retrieve name information subsequently becoming connected name information from either the home location register of the called mobile or the name database as the case may be and as will be described in greater detail below with reference to figure 6.

Referring now to figure 5, the method steps of how a calling mobile makes a call with calling name information is now described. The mobile performs a location update at step 5001. In response to the location update, the VLR then proceeds to retrieve a name associated with the mobile from any appropriate location, including for example the HLR of the calling mobile or the name database of the network. This is shown in step 504. The VLR then stores the name at an appropriate location; step 506. This name is stored at this location until the mobile moves out of range of that particular VLR. It may be necessary to periodically update or reacquire the data of the name if it is lost for any reason; step 508. If the mobile moves out of the range of the particular VLR the name information may be transferred during the transfer processes as described elsewhere.

Subsequently the mobile initiates a first call at step 500. Upon initiation of the first call the previously retrieved name associated with the calling mobile station is now to be considered the calling name. The VLR in the vicinity of the calling mobile receives the call request from the calling mobile; step 502. The VLR then proceeds to send the call to the terminating node via any appropriate route through the network including the calling name with the call; step 510. At a certain point in time the call ends; step 512. The calling mobile may make a subsequent call at step 514, however in this situation it may not be necessary for the VLR to retrieve the calling name information as this is already there from the first call. In this case the process proceeds immediately to step 510, where the call is sent to the terminating node of the new call and the call includes the calling name information which is already stored. If for any reason the calling name information is not available a subsequent call may proceed with the retrieval of the calling name corresponding to step 504.

In addition to the calling name information that is provided to the called party, the called name, ie the name of the subscriber that is being called, and may be of interest to the calling subscriber. This feature could be referred to as "connected name presentation (CONP)" and work in a similar manner to CNAP. Further details of the CONP will now be described.

In the same manner as with CNAP, the name information is stored during location update in the VLR. When the call is established from subscriber A to subscriber B the name information thus becoming connected name information is forwarded to the originating MSC in the opposite direction to the call. The MSC may then relay the information relating to connected name to the calling user terminal. This is illustrated with respect to figure 6. The vertical lines represent a node in the network and the horizontal lines represent messages between respective nodes. The three nodes are the mobile subscriber 600, the originating MSC (O-MSC) 602, and the terminating MSC (T-MSC) 604. The steps carried out in order to implement connected name presentation start with a Connection Management (CM) service request from the mobile subscriber to the originating MSC. The originating MSC replies with a CM service accept message and in turn the mobile subscriber sends a call setup message to the originating MSC. The originating MSC confirms that the call is proceeding to the mobile subscriber and sends an ISUP IAM message to the terminating MSC. The connected name information (or any other appropriate information) is then sent with one of the ISUP return messages, for example in the Address Complete Message (ACM), Answer Message (ANM) or Connect Message (CON). The connected name presentation is then transferred to the user with the Direct Transfer Application Path (DTAP) facility information elements included in an alerting or connect message or a similar message. The connected name presentation could be restricted by the subscriber using a connected name presentation restriction (CONR). For implementation of some of the messages described above it will be necessary for the ISUP messages to be converted to support delivery of generic text. It will be appreciated that there may be many variations and modifications to the method and apparatus described above.

Claims

1. A method of controlling presentation of user information, from a first user to a second user, wherein the first and second users are connected to a wireless network having at least one network node for each user, the method comprising the steps of:

- retrieving the user information from a database during a location update process for the first user,

- storing the user information at a Visitor Location Register to which the first user is connected,

- transmitting the stored user information from the Visitor Location Register to a node to which the second user is connected for presentation of the user information to the second user.

2. The method of claim 1 , wherein the transmitting comprises a transmitting from an originating Visitor Location Register as the Visitor Location Register to a terminating node as the node to which the second user is connected.

3. Method according to claim 2, wherein the user information comprises name information subsequently becoming calling name information.

4. The method according to claim 1 , wherein the transmitting comprises a transmitting from a terminating Visitor Location Register as the Visitor Location Register to an originating node as the node to which the second user is connected.

5. Method according to claim 4, wherein the user information comprises name information subsequently becoming connected name information.

6. The method of any preceding claim, further comprising providing at least a Home Location Register or a Visitor Location Register as the network node.

7. The method of claim 6, wherein the step of retrieving user information comprises retrieving the user information from a Home Location Register associated with the first user.

8. The method of any preceding claim, wherein the step of retrieving the user information comprises retrieving the user information from an external dedicated database.

9. The method of any preceding claim, further comprising updating the user information on a periodic basis.

10. The method of any preceding claim, further comprising re-acquiring the user information if the user moves from the originating Visitor Location Register to a new originating Visitor Location Register.

11. The method of any preceding claim , wherein the step of re-acquiring the user information comprises retrieving the user information a first location update process for the new originating Visitor Location Register after completion of a handover process from the originating Visitor Location Register.

12. The method of any preceding claim, further comprising reacquiring the user information by means of a query to the database from any node in the network if the user information is not received from the originating Visitor Location Register.

13. The method according to any of the preceding claims, wherein the user information comprises one or more of user data, multimedia data, picture data, computer data and text data.

14. Apparatus for a network node for controlling the presentation of user information from a first user to a second user, wherein the first and second users are connected to a wireless network having at least one network node for each user, wherein the first user is connected to the network node, the apparatus comprising: - an access unit for retrieving and storing user information from a database during a location update process for the first user,

15. The apparatus of claim 14, wherein one node is an originating node and one node is a terminating node.

16. The apparatus of claim 14 or claim 15, wherein the network node comprises a Home Location Register or a Visitor Location Register.

17. The apparatus of claim 16, wherein the user information is retrieved from an Home Location Register associated with the first user.

18. The apparatus of any of the claims 14 to claim 17, wherein the user information is retrieved from an external dedicated database.

19. The apparatus of any of claims 14 to 18, wherein the user information is updated on a periodic basis.

20. The apparatus of any of claims 14 to 18, wherein if the user moves from the originating Visitor Location Register to a new originating Visitor Location Register the user information is reacquired by the new originating Visitor Location Register.

21. The apparatus of claim 20, wherein the new originating Visitor Location Register reacquires the user information at a first location update process for the new originating Visitor Location Register after completion of a handover process from the originating Visitor Location Register.

22. The apparatus of any of claims 14 to 21 , wherein the user information comprises one or more of calling name information, called name information, user data, multimedia data, picture data, computer data and text data.

3. A computer program comprising instructions for carrying out the steps of the method according to any one of claims 1 to 13 when said computer program is executed on a computer.