MXPA06008659A - A method and apparatuses for sending message to a mobile station by addressing the hardware part - Google Patents

Abstract

A message, typically a SMS message, intended for a specific hardware item is provided from an application node (70) to a message controller (40) together with hardware identification data, e.g. IMSI or IMEISV. The message controller (40) and a location updated subscriber database, e.g. a HLR (50), having stored information about the intended terminating hardware, interacts (78, 80) and a further handling of the message is decided based on the provided hardware identification data and on data stored in the location updated subscriber database (50).

Description

A METHOD AND APPARATUS FOR SENDING MESSAGE TO A MOBILE STATION THROUGH THE ADDRESSING OF THE HARDWARE PART The present invention relates, in general terms, to the handling of messages, particularly short message service (SMS) messages in mobile communications networks, and in particular the present invention relates to finding the address Appropriate completion of an SMS message. BACKGROUND OF THE INVENTION The Short Message Service (SMS) has been used in mobile communication networks to allow different subscribers to send short text messages between them. The Mobile Subscriber ISDN Number (MSISDN), i.e. the mobile subscriber's telephone number is used as the address and identification information, since the SMS content is contemplated for a particular user. The SMS message and the MSISDN are provided to an SMS controller that temporarily stores the SMS and searches for the intended terminating mobile subscriber. When searching for the terminating mobile subscriber, the SMS controller interacts with a Home Location Register (HLR) for identity data, International Mobile Subscriber Identity (IMSI), a Subscriber Identity Module (SIM) associated with the terminating mobile subscriber. The HLR also offers an address of a Mobile Switching Center (MSC) through which the SIM can be reached. By using this data, the message can be routed to the appropriate terminating mobile subscriber. The SMS concept is also used today for several network-based applications, where SMS is used to send data directly to a customer over the phone. Examples of these applications are SMS by Air (OTA), notifications of Multimedia Message Services (MMS) and SIM Toolkit updates. To suit the basic SMS concept, these applications also use MSISDN as the address to reach either the SIM card or the mobile terminal. To the extent that there is a one-to-one correspondence between the MSISDN, the IMSI and the identity of the mobile terminal, for example in accordance with that defined by the International Mobile Equipment Identity (IMEI), or the extended IMEI with the Software version (IMEISV), any of these quantities can be used for addressing purposes with the same termination terminal, SIM and subscriber. However, by introducing more flexible solutions that allow for example a subscriber to move the SIM card between different terminals, or allowing a single mobile subscriber to have more than one SIM card addressed with the same MSISDN, problems of addressing. A part of the work within 3GPP is focused on standardizing a function to automatically detect when using a SIM card identified by IMSI in a terminal identified by IMEISV for the first time. This function is known as Automatic Device Detection (ADD). Information comprising at least MSISDN, IMSI and IMEISV is stored on a server with terminal capability. The server with terminal capability also has the ability to send the relevant information to external applications, such as Device Management Systems (DMS). These applications can use the information part as triggers for different events. Examples are that SMS with new GPRS arrangements can be sent to terminals that require these settings before they can be used for MMS, Wireless Application Protocol (WAP) or other data services. The server with terminal capability therefore allows connected applications to solve the problems of moving the SIM card to different terminals. However, the problems continue in the case of applications not connected to any updated terminal database or in the case of the use of dual SIM cards. COMPENDIUM OF THE INVENTION A general problem with the SMS systems of the prior art is that there is a lack of definition in the addressing of hardware parts, for example, SIM cards or mobile terminals, of a mobile subscriber in a mobile communication network. A further problem with the prior art solutions is that the simultaneous use of more than one SIM card for the same mobile subscriber makes it impossible to ensure that an SMS message reaches the intended hardware. A general object of the present invention is therefore to provide methods, devices and systems in which identifications associated with hardware can also be used as routing data when sending messages. A further object of the present invention is to offer such methods, devices and systems that require the smallest possible changes in current standardized systems. The objects mentioned above are achieved through methods, devices and systems in accordance with the appended patent claims. In other words, a message, typically an SMS message, contemplated for a specific hardware element is provided from an application node to a message controller together with hardware identification data, for example, IMSI or IMEISV, specifying the Termination hardware contemplated. The message controller and a location updated subscriber database, for example HLR, which has information stored on the contemplated termination hardware, interacts and an additional handling of the message is decided based on the hardware identification data provided and based on data stored in the updated location database.

Preferably, the additional handling is based on a comparison between the hardware identification data stored in the updated location subscriber database and the hardware identification data provided. In one embodiment, the hardware identification data is provided to the updated subscriber database of location where a comparison is made with the stored data, resulting in IMSI recovery and a support or switching node address Relevant hardware In another embodiment, the application node also provides the identity of the subscriber, e.g., MSISDN, to the message handler. The message controller interacts with the updated location subscriber database to obtain hardware identification data (e.g., IMSI and / or IMEISV) from the updated location subscriber database. If the hardware identification data provided by the application node, in a comparison made in the message controller corresponds to the hardware data obtained from the updated location subscriber database, the message is transmitted to the address of support or switching node that was also obtained from the location updated subscriber database. Otherwise, error functionalities are applied.

An advantage with the present invention is that any indefiniteness in the hardware addressing contemplated as terminating element of a message is removed. Another advantage of the present invention is that a very limited number of changes have to be made to the current standards. BRIEF DESCRIPTION OF THE DRAWINGS The invention, together with additional objects and advantages thereof, will be better understood with reference to the following description in combination with the accompanying drawings, in which: Figure 1 is a schematic block diagram of a system of mobile communication that supports SMS; Figures 2A and 2B are schematic illustrations of stored data of typical HLR units; Figure 3 is a schematic block diagram of a mode of a message controller in accordance with the present invention and its surrounding units; Figure 4 is a schematic block diagram of modalities of a message controller and an HLR in accordance with the present invention; Figure 5 is a schematic block diagram of other modes of a message controller and an HLR in accordance with the present invention; Figure 6 is a flowchart of the main steps of one embodiment of a method according to the present invention; and Figure 7 is a flow chart of the main steps of another embodiment of a method in accordance with the present invention. DETAILED DESCRIPTION OF THE INVENTION In the present disclosure, the term "hardware identification data" comprises identification data associated with all types of hardware, including, for example, SIM cards, mobile terminals, etc. The hardware identification data may then comprise, for example, IMSI, IMEI, IMEISV as well as combinations thereof. In order to better understand the present invention, a brief overview of a prior art communication system supporting SMS is provided first. Figure 1 illustrates a mobile communication system 1 of this type. Several users of mobile subscribers 10: 0, 10: 1 have access to one or more mobile terminals 14: 0, 14: 1, 14: 2. Each 10: 0, 10: 1 subscriber is characterized by a unique identification number with MSISDN. There is typically a proper relationship 12 between the subscribers 10: 0, 10: 1 and the mobile terminals 14: 0, 14: 1, 14: 2 that the subscriber uses. Terminals 14: 0, 14: 1, 14: 2 also have a unique identity, defined by the IMEISV. In order to associate the subscriber and the mobile terminal 14: 0, 14: 1, 14: 2, a 16: 0 SIM card is inserted., 16: 1, 16: 2 at the mobile terminal 14: 0, 14: 1, 14: 2. The position of the SIM card 16: 0, 16: 1, 16: 2 constitutes the connection to the mobile terminal 14: 0, 14: 1 14: 2 while the connection between the SIM card 16: 0, 16: 1, 16: 2 and the subscriber 10: 0, 10: 1, is carried out through an agreement registered in the database. The SIM card 16: 0, 16: 1, 16: 2 also has an identity, defined by the IMSI. In summary, the subscriber is identified by the MSISDN, the SIM card and the IMSI and the mobile terminal by IMEISV. Each mobile terminal 14: 0, 14: 1, 14: 2 is connected through wireless communication links 18 to a respective base station 22.0, 22: 1. Base stations 22: 0, 22: 1 are typically arranged to service several mobile terminals simultaneously. The base stations 22: 0, 22: 1 are connected to mobile switching centers 20: 0, 20: 1. The communication system 1 tracks which mobile switching center (MSC) 20: 0, 20: 1 is connected to terminal 14: 0, 14: 1, 14: 2, by updating address fields of a HLR 50. When a normal SMS is sent, a 10: 0 subscriber can capture a message on his originating mobile terminal 14: 0 and request that the SMS be sent to a certain 10: 1 receiving subscriber, identified by an MSISDN. The message and its associated MSISDN are transmitted through a connection 26 to the central network 30 of the communication system. In the system illustrated now, the SMS is transmitted in a single SS7 packet via the core network 30 to an SMS controller 40. The communication on the connection 74 between the core network 30 and the SMS controller is governed by an interface 52 defined by the 3GPP standards protocols, and comprises the MSISDN message and data. The SMS message is received by an SMC 42 and interconnected by SMS and the SMS is at least temporarily stored in a controller storage 44. An MSC gateway SMS 46 is connected to the controller storage 44 and interacts with the HLR 50 in an interface 54 for obtaining address data associated with the final subscriber contemplated. The MSISDN is provided 78 in the HLR 50, which uses its databases to return 80 corresponding IMSI data and the address of the MSC currently serving the subscriber. The communication between the "SMS 40 controller and the HLR 50 is carried out in this mode according to a Mobile Application Part standard.

(M? P) of a 3GPP specification. The SMS gate MSC 46 initiates a transmission of the SMS message when the IMSI associated with the MSC address through the connection 76 and the SS7 network 30. The IMSI is used by the MSC during the paging operation of the mobile terminal . The MSC to which the 20: 1 communication is directed receives the IMSI message and data through the connection 24 and sends it to the mobile terminal 14: 1, which has the SIM card 16.1 associated with the IMSI data. In this way, the SMS reaches the termination subscriber contemplated 10: 1. An important part to be able to provide this service is the HLR 50. Figure 2a schematically illustrates part of the content of an HLR in a typical SMS case. The HLR comprises several entries illustrated as rows of data. Each input comprises an MSISDN number 101, an IMSI number 102, a current MSC address 104 and in this mode also an IMEISV number 103. The entries thus define the present relationships between the hardware identification data, i.e. IMSI and IMEISV, and MSISDN. In addition, the current location in the communication network is provided through the MSC address. This HLR 50 is continuously updated. This means that if a subscriber places their SIM card in a new mobile terminal, the IMEISV number of the corresponding entry is updated to reflect the new hardware. Other applications have been developed, using SMS concepts to transmit data to the subscriber; terminal or SIM card. Non-exclusive examples are email notification, multimedia message service message (MSM) notification, voice mail, WAP push, SMS toolkit SMS or OTA configuration SMS. Such application nodes are illustrated through 70: 1, 70: 2, 70: 3 in Figure 1. The SMS messages generated by these applications 70: 1, 70: 2, 70: 3 are provided, typically through from an Internet network 60, to an interrelated unit of application node 48 the SMS controller 40. Other types of networks or connections can also be used to connect the SMS controller 40 and the applications 70: 1, 70: 2, 70: 3. The message, together with an MSISDN identifying the terminating subscriber, is transmitted through a connection 58 using, for example, a Short Point-to-Point Message (SMPP). The SMS message is then sent in the same way as in the case of SMS messages that come from the subscriber. There is, however, a main difference between certain application SMS messages and normal SMS messages from the subscriber. The SMS messages from the subscriber are in all the actual situations contemplated for the final subscriber. However, application SMS messages may be contemplated to reach the SIM card or the mobile terminal instead of the actual subscriber. If a subscriber moves the SIM card to a new terminal, the application that generates the termination SMS messages in the mobile terminal must be informed. In addition, if MSISDN is moved, using for example Dual SIM procedures, from one SIM card to another SIM card, SMS messages with SIM termination will not reach the intended SIM card. The concept of double S1M can also be extended to more than two SIM cards. The principles for an OTA configuration SMS can be described with reference to Figure 1 employing a particular implementation of ADD. When a subscriber is detected with the new terminal, a possible procedure may be as follows. The MSC 20: 1 node in either a public land mobile home network (HPLMN) or the visited public land mobile network (VPLMN) looks for IMEISV for all users in Location Update, IMSI Connection type or Normal. The MSC 20: 1 sends the IMEISV received in the Location Update operation to the HLR 50 node of HPLMN. The HLR 50 stores IMEISV together with other subscriber data, in accordance with what is described above. The HLR 50 sends a message to a server with terminal capability 72. In the system currently illustrated, the server with terminal capability 72 reviews the received information against a configuration data file stored internally. The server with terminal capability 72 sends a new configuration command to a DMS, as illustrated in the application node 70: 1. Any appropriate data can be attached. DMS 70: 1 processes configuration commands at regular intervals and for appropriate configuration methods based on received device data and access point name (APN) to identified subscribers. The DMS 70: 1 sends an OTA SMS, addressed with the MSISDN, to an SMS 40 controller for further delivery in accordance with the procedures described further above. The server with terminal capability 72, provides here the identity information necessary to be able to perform the OTA configuration. An additional complication arises when the concept of double (or multiple) SIM is introduced. Many operators today have solutions with more than one SIM card associated with the same MSISDN number. These solutions are often referred to as GSM Dual Cards, Dual SIM Cards or the like. With these solutions, a subscriber does not have to change the SIM card between the terminals if the subscriber has more than one terminal. Several terminals can be used simultaneously for calls that leave a mobile, but only one can be used for calls ending in a mobile, and SMS messages ending in a mobile. A typical case is a user with a manual terminal and a terminal mounted on a car. Another typical case is a user with a large advanced smartphone and a small mobile phone. It is then up to the subscriber to specify to the network which of these terminals should be marked in HLR as currently active for mobile terminated calls and SMS messages. Figure 2b schematically illustrates parts of the contents of an HLR in a case of Dual SIM. Each SIM card, i.e. each IMSI, corresponds to an input of the HLR 50. However, since several IMSIs may be associated with the same MSISDN, only the selected IMSI for incoming call termination has the defined MSISDN number. In this particular example, the subscriber MSISDN-1 has Dual SIMs with IMSI numbers IMSI-1 and IMSI-2. IMSI-1 is selected as the number that should receive incoming calls. In the same way, subscriber MSISDN-3 has marked IMSI-4 as the "active" SIM card and has "passive" IMSI-3. However, if an application node has the purpose of sending an SMS message to a given SIM card or mobile terminal, the corresponding MSISDN may be associated with another IMSI or IMEISV. This results in the application node not guaranteeing that the SMS actually arrives at the intended hardware. For example, with reference to Figure 2b, if IMSI-2 is the contemplated goal, the associated MSISDN, i.e. MSISDN-1, is not active and in addition MSISDN-1 is actively associated with another IMSI, specifically IMSI-1. The information used in the described modalities consists mainly of IMSI, IMEI or IMEISV and MSISDN. However, other types of identification data for mobile terminals, subscriber identity modules and mobile subscribers can be used in an equivalent manner. The general solution of the present invention comprises the addition of parameters of interface protocol 56 that controls communication between the application node 70: 1, 70: 2, 70: 3 and the SMS controller 40. These parameters comprise identification data. of hardware, typically at least one of the identification data of subscriber identification module (IMSI) and mobile equipment identification data (IMEI or IMEISV). Figure 3 illustrates an embodiment of an SMS controller 40 in accordance with the present invention together with parts of the neighboring communication system. An SMS message and an associated MSISDN number MSISDNx are sent from an application node 70 to the SMS controller via connection 58. According to this embodiment of the present invention, in addition to these data, IMSI associated IMSIx are also attached. When the SMS GMSC 46 interrogates the HLR 50 with a message requesting routing information for the SMS, the MSISDNx data is used as identification. The IMSI data returned IMSIy (and also MSC address data) correspond to the SIM card which is the "active" receiver of calls and SMS's in accordance with the databases of the HLR 50. The SMS GMSC 46 compares in a comparator 45 the IMSI data from the HLR 50 and the IMSIx data received by the connection 43 in order to verify that they are the same. If they are really the same, implicitly, the MSC address is also the MSC address associated with IMSIx and provided by connection 47 to reach the SMS message provided by 41. The SMS sending procedure then proceeds normally, initiating a SMS transmission. The data provided in connection 76 then comprises the SMS message, the MSC address and the IMSIx data. If the IMSI received from the HLR 50 is not the same as the IMSI received from the application node, alternative error handling procedures are possible. In one embodiment, an error message 49 is provided to the application node, indicating that the contemplated termination hardware can not be reached through the use of the MSISDN number as the only address. In an alternative mode, the SMS message could be stored for a period of time, and a new HLR interrogation could take place after a lapse of time, to check if there is any change in the choice of active SIM cards. Here, an error message could be returned, for example, after a certain number of attempts or after a certain period of time. In accordance with the embodiment of Figure 3, with a simple update of the SMPP protocol, or another protocol that controls the communication between the application node and the SMS controller, that is, the interface 56, the information coming from the HLR can be used to verify that you are going to the correct terminal or the correct SIM card. No changes need to be made to the current standardized protocols for the interface 54 between the SMS controller 40 and the HLR 50. However, if additional changes are made also on the interface 54, additional advantages can be achieved. Figure 4 illustrates another embodiment of an SMS controller in accordance with the present invention. An SMS message is sent from an application node 70 to the SMS controller via connection 58. The MSISDN number can also be optionally provided. In accordance with this embodiment of the present invention, in addition to these data, IMSI associated IMSIx data are also attached. According to this embodiment, the SMS GMSC 46 interrogates the HLR 50 with a message in accordance with a modified standard. Here routing information for the SMS is required based on the IMSIx 81 data used as identification. In the return, MNSC address data MSCx 79 corresponding to the SIM card having the identity of IMSIx is provided regardless of whether the SIM card is marked as active or not. This is provided in accordance with the information stored in the HLR 50 databases. The SMS 46 GMSC adds the MSCx address to the IMSIx message and data. The SMS sending procedure then proceeds normally, initiating a transmission of the SMS. The data provided in connection 76 then comprises the SMS message, the MSCx address and the IMSIx data. If the MAP 54 interface is updated in order to also transfer IMSi as identification information, the correct terminal can be reached regardless of which SIM card is marked as active for the mobile terminated SMS in the case of Dual SIM solutions. In such a case, the need for error signaling is not as vital as in the case of the embodiment of Figure 4. Figure 5 illustrates another embodiment of an SMS controller in accordance with the present invention. An SMS message is sent from an application node 70 to the SMS controller through the connection 58, along with the MSISDN number, MSISDNx. According to this embodiment of the present invention, in addition to these data, associated IMEI data, IMEIx, is also attached. According to this embodiment, the SMS GMSC 46 interrogates the HLR 50 with a message comprising the MSISDNx 80. In the return, MSC address data MSCy 79 correspond to the associated terminal as active relative to MSISDNx. Likewise, the IMSIy and IMEIy corresponding to SMS GMSC 46 are provided. The GMSC 46 of SMS compares in a comparator 45 the IMEI data from the HLR 50 and the IMEIx data received by the connection 43 to verify that they are the same. If they really are the same, the address of MSC MSCy is the same as MSCx, the IMSIy is the same as IMSIx, and they are equipped with a connection 47 to connect the SMS message provided by 41. The SMS sending procedure continues then normally, initiating a transmission of the SMS. The data provided in connection 76 then comprises the SMS message, the MSCx address and the IMSIx data. If the IMEI received from the HLR 50 is not the same as that received from the application node, alternative error handling procedures are possible analogously to the embodiment of Figure 3. An error message 49 can be provided to the application node, indicating that the termination hardware contemplated, in this case a given mobile terminal, can not be reached by using the MSISDN number as the only address. In an alternative mode, the SMS message could be stored for a period of time, a new HLR interrogation can be performed after a lapse of time, to check whether there are changes in the choice of active terminal equipment. Here, an error message could be returned, for example, after a certain number of attempts or after a certain period of time. Note that the modality of Figure 5, HLR 50 is considered as including IMEISV data record (or IMEI). In previous modalities it does not matter whether or not the HLR 50 comprises IMEI or IMEISV registers, since this data is not used.

In principle, it would also be possible to use IMEI in an arrangement similar to the modality of Figure 4. However, the search for an MSC address based exclusively on an IMEI number could be difficult to implement in reality. In another embodiment, the data received by the SMS controller 40 on the interface 56 comprises both IMSI and IMEISV. The GMSC 46 of SMS offers the IMSI to the HLR 50 through the interface 54, but receives the IMEISV back. The IMEISV is then used to compare the termination hardware originally contemplated with that which is stored in the HLR 50. This could be used to ensure that the SIM card is placed in the correct telephone. This could be a complement to the use of a server with terminal capability 72. In the present disclosure, SMS is used as an example message system. The present invention, however, can also be applied to other message systems, for example, Unstructured Supplemental Service Data (USSD). In the same way, an SMS controller is used as a model for a general message controller. In the described embodiments, an updated localization subscription database is exemplified through an HRL. However, other subscriber databases having updated location data such as, for example, Home Subscriber Servers (HSS) can also be used. The address received from the updated location subscription database refers to a switching or support node which, in the described embodiment, is exemplified by an MSC. However, other types of switching or support nodes, for example, an SGSN in GPRS or 3G systems can also be used. In addition, in the above modalities, IMEISV has been used to refer to the hardware identity of the mobile terminal. Since IMEISV comprises the IMEI and an extension that defines the current software version, any message addressed to the mobile terminal that is independent of the software version can also be addressed only by the IMEI. In other words, both the IMEI and IMEISV can serve as a reference to the mobile terminal hardware. Figure 6 illustrates a flow diagram of the main steps of one embodiment of a method according to the present invention. The procedure begins in step 20. In step 210, a hardware identification data message is transferred from an application node to a message handler. An interaction step 212 between the message controller and the updated location terminal database, typically an HLR, comprises in the present embodiment steps 214, 216 and 218. In step 214, the hardware identification data is sent to the HLR as part of an interrogation for a support or switching node address. In step 216, the HLR retrieves the address corresponding to the hardware identification data, and in step 218, this address data is returned to the message handler. A step 220 of further administration of the message comprises in this mode the step 224 of initiating the transmission of the message in accordance with the address received from the HLR. The procedure ends in step 299. Figure 7 illustrates a flow chart of the main steps of another embodiment of a method in accordance with the present invention. The procedure begins in step 200. In step 210, a message and (first) hardware identification data is transferred from an application node to a message handler. The termination subscriber identification number is transferred in step 211, together with the message or separately. An interaction step 212 between the message controller and an updated location terminal database, typically an HLR, comprises in the present embodiment three steps 213, 215 and 217. In step 213, the subscriber identification number is sent to the HLR as part of an interrogation for a switching or support node address. In step 215, the HLR retrieves the address corresponding to the subscriber identification number and also a (second) corresponding hardware identification data. In step 217, this address data and hardware identification data are returned to the message handler. A step 220 of further administration of the message comprises in this embodiment steps 221 to 224. In step 221, the hardware identification data received from the HLR and the application node, respectively, are compared. If the hardware identification data, as decided in step 222, is corresponding data, the procedure proceeds to step 224, where the transmission of the message in accordance with the address received from the HLR is carried out. If in step 222 it is concluded that the hardware data does not correspond, the procedure proceeds to step 223, where an error handling procedure is carried out. The procedure ends in step 299. The embodiments described above are to be understood as some illustrative examples of the present invention. It will be understood by those skilled in the art that various modifications, combinations and changes can be made to the modalities without departing from the scope of the present invention. In particular, different partial solutions can be combined in different modalities in other configurations, when technically possible. The scope of the present invention, however, is defined by the appended claims.

Claims (33)

1. CLAIMS 1. A method for handling messages in a mobile communication system (1), comprising the steps of: transferring a message and first associated hardware identification data of a contemplated termination receiver (16: 1, 16: 2, 14: 1, 14: 2) of the message from the application node (70; 70: 1-3) to a message controller (49); interacting between the message controller (40) and an updated location subscriber database (50); further handling the message based on the first identification data of hardware and data stored in the updated subscriber database of location (50).
2. 2. A method according to claim 1, characterized in that it presents the additional step of: comparing the first hardware identification data and the hardware identification data stored in the updated subscriber database of location (50) , through which the additional handling step is based on the result of the comparison step.
3. 3. A method according to claim 1 or 2, characterized in that the step of interacting in turn comprises the steps of: sending the first hardware identification data from the message controller (40) to the database updated subscriber location (50); whereby the first hardware identification data is used in the updated subscriber database of location (50) to retrieve the address, if any, of a switching or support node (20: 1) that is currently handling the hardware (16: 1, 16: 2, 14: 1, 14: 2) defined by the hardware identification data; and returning the address of the switching or support node (20: 1), if any, from the updated subscriber base of location (50) to the message controller (40); whereby the additional handling step comprises initiating the transmission of the message to the address of the switching or support node (20: 1).
4. 4. A method according to claim 3, characterized in that the additional handling step further comprises, if an address of a switching or support node (20: 1) which currently handles a hardware is not recovered (16: 1). , 16: 2, 14: 1, 14: 2) defined by the hardware identification data in the updated subscriber database of location (50), storage of the message and resumption of the interaction step with the database of updated localization subscriber (50) after a lapse of time.
5. A method according to claim 1 or 2, characterized in that it presents the additional step of transferring mobile subscriber identification data associated with the messages from the application node (70; 70: 1-3) to the controller of message (40).
6. 6. A method according to claim 5, characterized in that the mobile subscriber identification data is a mobile subscriber ISDN number.
7. A method according to claim 5 or 6, characterized in that the step of interacting comprises in turn the steps of: sending the mobile subscriber identification data from the message controller (40) to the database updated subscriber location (50); recover an address, if it exists, from a switching or support node (20: 1) that. currently manages a mobile subscriber (10: 1) defined by the mobile subscriber identification data and second hardware identification data associated therewith; and returning the address of the switching or support node (20: 1) and the second hardware identification data from the updated location subscriber database (50) to the message controller (40).
8. A method according to claim 7, characterized in that a comparison step is carried out in the message controller (40), where the first hardware identification data and the second hardware identification data are compared.; and whereby the additional handling step comprises, if the first hardware identification data and the second hardware identification data are equivalent, the start of a transmission of the message to the address of the switching or support node (20: 1 ).
9. 9. A method according to claim 8, characterized in that the additional handling step comprises, if the first hardware identification data and the second hardware identification data are not equivalent, storing the message and resuming the step of interaction with the updated subscriber database of location (50) after a lapse of time.
10. A method according to claim 8 6 9, characterized in that the additional handling step further comprises, if the first hardware data and the second hardware data are not equivalent, the sending of an error message to the node of application (70; 70: 1-3).
11. 11. A method according to any of claims 1 to 10, characterized in that the first hardware identification data and the second hardware identification data comprise at least one of the identification data of the subscriber identification module and data. of identification of mobile equipment.
12. 12. A method according to claim 11, characterized by the return of at least one identification data of subscriber identification module and identification data of mobile equipment from the updated subscriber database of location (50) to the message handler (40).
13. 13. A method according to any of claims 1 to 12, characterized in that the message is a short message service message - SMS - and the message controller (40) is an SMS controller.
14. 14. A method according to any of claims 1 to 13, characterized in that the location updated subscriber database (50) is a home location register.
15. 15. A method according to any of claims 3 to 7 or any claim dependent on claim 3 or 7, characterized in that the switching or support node (20: 1) is a mobile switching center.
16. 16. A message controller (40), comprising: a first receiver (48) for a message and a first associated hardware identification data of a terminating receiver contemplated by the message; and means (46) for interacting with an updated location subscriber database (50; and means (46) for additionally handling the message based on the first identification data of hardware and data stored in the database subscriber update location (50)
17. 17. A message controller according to claim 16, characterized in that the means (46) for additional handling is arranged to be based on the result of a comparison between the first identification data. of hardware and the hardware identification data stored in the updated subscriber database of location (50)
18. 18. A message controller according to claim 16 or 17, characterized in that the means (46) for interacting it comprises in turn: a sending means for sending the first hardware identification data to the updated subscriber database of location (50); a second receiver for an address, if any, of a switching or support node (20: 1) that currently handles hardware (16: 1, 16: 2, 14: 1, 14: 2) defined by the hardware identification data of the base subscriber data updated location (50); the means (46) for additional handling comprising means for initiating a transmission of the message to the address of the switching or support node (20: 1).
19. 19. A message controller according to claim 18, characterized in that the means (46) for additional handling further comprises, if no address is provided for a switching or support node (20: 1) that is currently handling hardware (16: 1, 16: 2, 14: 1, 14: 2) defined by the hardware identification data by the updated location database of the subscriber (50), storing the message and resuming the step of interacting with the updated subscriber database of location (50) after a period of time.
20. 20. A message controller according to claim 16 or 17, characterized in that the first receiver (48) is arranged to additionally receive a mobile subscriber identification data.
21. 21. A message controller according to claim 20, characterized in that the mobile subscriber identification data is a mobile subscriber ISDN number.
22. 22. A message controller according to claim 20 or 21, characterized in that the means (46) for interacting comprises in turn: a sending means for sending the mobile subscriber identification data to the data base of the subscriber. updated localization subscriber (50); and a second receiver for an address, if any, of a switching or support node (20: 1) currently operated by a mobile subscriber (10: 1) defined by the mobile subscriber identification data and the second hardware identification data. associated with it from the updated location database (50).
23. 23. A message controller according to claim 22, characterized in that it has: means (46) for comparing the first hardware identification data and the second hardware identification data; the means (46) for additional handling comprises a means for initiating a transmission of the message to the address of the switching or support node (20: 1); so that the means to start is arranged to operate if the output of the means for comparison indicates that the first hardware identification data and the second hardware identification data are equivalent.
24. 24. A message controller according to claim 23, characterized in that the means (46) for additional handling further comprises means (44) for storing the message and a means for resuming interaction with the subscriber database. updated location (50) after a lapse of time; so that the means (44) for storing and the means for resuming are arranged to operate if the output of the means for comparison indicates that the first hardware identification data and the second hardware identification data are not equivalent.
25. 25. A message controller according to claim 23 or 24, characterized in that the means (46) for additional handling further comprises a means for sending an error message to a source node (70; 70: 1-3). ) of the message; so that the means for sending an error message is arranged to operate if the output of the means for comparison indicates that the first hardware identification data and the second hardware identification data are not equivalent.
26. 26. A message controller according to any of claims 16 to 25, characterized in that the first hardware identification data and the second hardware identification data comprise at least one of the following: identification data of the module subscriber identification and identification data of mobile equipment.
27. 27. A message controller according to claim 26, characterized in that the second receiver is arranged to receive at least one of the following: subscriber identification module identification data and mobile equipment identification data from the updated subscriber database of location (50).
28. 28. A message handler according to any of claims 16 to 27, characterized in that the message is a short message service message - SMS - and the message handler is an SMS handler.
29. 29. A communication system node having an updated location subscriber database (50), comprising: storage for address and hardware identification data associated with mobile subscribers; and means to update the storage content; characterized in that it has a receiver for hardware identification data associated with a contemplated termination receiver (16: 1, 16: 2, 14: 1, 14: 2) of a message from a message controller (40); means to retrieve an address, if any, from a support or switching node (20: 1) that is currently handling a hardware (16: 1, 16: 2, 14: 1, 14: 2) defined by the identification data of hardware coming from storage; and sending device to send the address of the switching or support node (20: 1) that is currently handling a hardware (16: 1, 16: 2, 14: 1, 14: 2) defined by the hardware identification data to the message handler (40).
30. 30. A communication system node according to claim 29, characterized in that the sending device further comprises a device for sending hardware identification data to the message controller (40).
31. 31. A communication system node according to claim 29 or 30, characterized in that the updated location subscriber database (50) is a home location register.
32. 32. A mobile communication system (1), comprising at least one message controller according to any of claims 16 to 28.
33. 33. A mobile communication system according to claim 32, characterized in that it also comprises at least one communication system node according to any of claims 29 to 31.