Method and apparatus for verification of a telephone number

'b G

O

<img file="SE535546C2_D0001.tif" />

(12) Patent Specification (10) SE 535 546 C2

<img file="SE535546C2_D0002.tif" />

<img file="SE535546C2_D0003.tif" />

Sweden (21) Patent application number: 1150765-4 (45) Patent granted: 2012-09-18 (41) Application generally available: 2012-02-14 (22) Patent application submitted: 2009-07-14 (24) Maturity date: 2009- 07-14

Completed international patent application with number: PCT / SE2009 / 050897 (86) International filing date: 2009-07-14 (83) Deposit of microorganism: - (30) Priority information: - (51) International class:

H04W12 / 06 (2009.01)

H04L 29/06 (2006.01)

<td>(73) Patent holders:</td><td>Telefonaktiebolaget LM Ericsson (publ), 164 83 Stockholm SE</td>

<td>(72) Inventor:</td><td>Niklas AGEV1K, Stockholm SE Björn IDRÉN, Hässelby SE</td>

<td>(74) Agents:</td><td>Ericsson AB Klas Norin, Torshamnsgatan 23, 164 80 Stockholm SE</td>

<td>(54) Name:</td><td>Method and apparatus for verifying a telephone number</td>

<td>(56) Publications cited:</td><td> ___</td>

(47) Summary:

The invention relates to a method and apparatus for verifying a mobile number. The method comprises: storing a mobile number and a corresponding mobile subscriber identity number; receiving a request for verification of the mobile phone number; sending, in response to the request, an IMSI query requesting a mobile subscriber identity number registered in conjunction with the mobile subscriber identity number in a CPR; receiving in response to the IMSI question the mobile subscriber identity number associated with the mobile phone number in the CPR; comparing the stored mobile subscriber identity number and the received mobile subscriber identity number, and, if the comparison shows that the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number, initiating the execution of the message or positioning service regarding the mobile phone number.

<img file="SE535546C2_D0004.tif" />

535 546

Summary

The invention relates to a method and apparatus for verifying a mobile number. The method comprises: storing a mobile number and a corresponding mobile subscriber identity number; receiving a request for verification of the mobile phone number; sending, in response to the request, an IMSI query requesting a mobile subscriber identity number registered in conjunction with the mobile subscriber identity number in a CPR; receiving in response to the IMSI query the mobile subscriber identity number associated with the mobile phone number in the CPR; comparing the stored mobile subscriber identity number and the received mobile subscriber identity number, and, if the comparison shows that the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number, initiating the execution of the message or positioning service regarding the mobile phone number.

535 546

METHOD AND APPARATUS FOR VERIFYING A PHONE NUMBER

technology Area

The invention relates to the field of mobile radio communication, and in particular to security enhancements for services utilizing such communication.

Background

The large market penetration of mobile communication devices in most parts of the world has attracted many industries to provide services using mobile radio communication systems. One example is the banking industry, where some banks offer their customers the opportunity to receive information via Short Message Service (SMS). In the banking industry as well as in other industries that handle information that can be sensitive, integrity and information security are often of high concern. Although very convenient, the transmission of information via SMS is generally not entirely secure. Many adherents to SMS-based services argue that although SMS banking services are not as secure as other conventional banking channels, SMS banking services are not intended to be used for transactions with very high risk. However, there is still a desire to increase the security of delivery on SMS banking services and other services utilizing mobile radio communication systems.

Summary

One problem to which the invention relates is how to improve security for third-party services that utilize messaging or positioning services through a mobile radio communications network.

The invention relates to a method for verifying a mobile phone number to determine whether a message or positioning service in a mobile radio communication system should be performed with respect to the mobile telephone number. The method comprises: storing a mobile number and a corresponding mobile subscriber identity number in a database of a verification device; receiving in the verification apparatus a request for verification of the mobile telephone number; transmitting, from the verifier in response to the verification request, an IMSI query requesting a mobile subscriber identity number registered in conjunction with the mobile phone number in a home location register; reception in the verifier of

535 The 546 mobile subscriber identity number associated with the mobile phone number in the home location register; comparing in the authentication apparatus of the stored mobile subscriber identity number and the received mobile subscriber identity number; and, if the comparison shows that the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number: initiate the performance of the message or positioning service regarding the mobile phone number.

It is thus achieved that it can be discovered if the mobile subscription to which the mobile phone number is associated has changed between the time for storing the mobile phone number and the time for initiating a message or positioning service regarding the mobile phone number. The performance of a message or positioning service can be made conditional on the result of verification of the mobile phone number.

The home location registry mentioned in this application should not only be interpreted as being a home location register as specified in the Global System for Mobile Communications (GSM), but a server that includes the functionality corresponding to the home location register as specified in the detailed description regardless of how it is referred to in a specific telecommunications network. An example of an alternative term is HSS (Home Subscriber Server) as specified in IMS (Internet Protocol Multimedia Subsystem).

The storage may include: receiving in the verification apparatus a request for registration of a mobile number; sending from the authentication apparatus in response to the request for registration of the mobile phone number, a first IMSI query requesting a mobile subscriber identity number registered in connection with the mobile phone number in a home location register; receiving in the authentication device in response to the first IMSI query mobile subscriber identity number associated with the mobile phone number in the home location register; and wherein the storage includes storage as the corresponding mobile subscriber identity number, the mobile subscriber identity number received in response to the first IMSI query. By this aspect, it is achieved that the registration of the mobile phone number in a verification device can be conveniently carried out.

The method may include sending a verification response indicating the result of the comparison. In one embodiment, the verification response includes an indication of whether the stored mobile subscriber identity number and the received mobile subscriber identity number

535 546 has been issued by the same mobile network operator or not. For example, such an indication can only be given in scenarios where the comparison shows that the received mobile subscriber identity number does not correspond to the stored mobile subscriber identity number. The verification apparatus may, for example, be included in an application server arranged to provide a third party service utilizing the messaging or positioning service. In this implementation, the request for verification is advantageously generated by the application server and the initiation advantageously comprises that the application server sends a request for execution of the message or positioning service.

In another embodiment, for example, the authentication apparatus may be included in an application server which operates as a broker node for services in a communication system. In this implementation, the verification request can be received from an application server arranged to provide a third-party service utilizing the messaging or positioning service; wherein the initiation comprises the broker mode executing the message or positioning service, or sending a request for execution of the message or positioning service to a mobile radio communication network in the communication system, or transmitting a verification response indicating the result of the comparison to the application server.

In an embodiment where the message or positioning service is part of a third party service, the method may further comprise sending a message to the mobile phone number through the mobile radio communication system if the comparison shows that the received mobile subscriber identity number does not correspond to the stored mobile subscriber identity number, where the message indicates a delivery service of the third party. telephone number. For example, such a message can be sent from the authentication device, or from the application server that provides the third party service. By sending such a message, it can be ensured that a mobile subscriber who has retained his mobile number, but for which the subscription has been changed, will receive a notification when a third party service is terminated due to the changes made to his subscription. The mobile subscriber can then take appropriate action to reactivate the third party service if desired.

535 546

One embodiment provides a method for requesting a message or positioning service in a mobile radio communication system. This method involves sending, from an application server to a verification device, a request for registration of a mobile number in the verification device, the request including an indication of the mobile telephone number. This method further includes transmitting, from the application server to the verifier, a request for verification of the mobile phone number to determine whether a message or positioning service in a mobile radio communication system should be performed with respect to the mobile phone number.

The invention also relates to a verification apparatus for verifying a mobile phone number to determine whether a message or positioning service in a mobile radio communication system should be performed with respect to the mobile telephone number. In one embodiment, the verification apparatus comprises: a database for storing a mobile number and an associated mobile subscriber identity number; a first input arranged to receive a request for verification of a mobile number; an output arranged to transmit an IMSI query regarding a mobile number, wherein the IMSI query requests a mobile subscriber identity number registered in conjunction with the mobile phone number in a home location register; a second input arranged to receive a mobile subscriber identity number in response to an IMSI query regarding a mobile number; and process means arranged to compare a mobile subscriber identity number stored in the database in conjunction with a mobile number with a mobile subscriber identity number received in response to an IMSI query regarding the mobile phone number, and to initiate the performance of the message or positioning service regarding the mobile phone number if the comparison shows that the received mobile subscriber identity number corresponds to the mobile subscriber identity number.

In addition, the invention also relates to an application server arranged to provide a third party service utilizing a messaging or positioning service. The application server comprises: an output arranged to transmit, to a verification device, a request for registration of a mobile number in the verification device, the request for registration including an indication of the mobile telephone number. The output is further arranged to transmit to the verification apparatus, a request for verification of the mobile telephone number to determine whether the message or positioning service in a

535 546 mobile radio communication systems should be implemented regarding the mobile phone number. In one embodiment, the application server comprises the authentication apparatus.

The application server may include an input arranged to receive a verification response indicating the result of the verification of a mobile number; a customer information register for the third party service; and a process means arranged to store, in the customer information register of the third party service as part of the third party service's subscription information for a telephone number, if a verification response received by the output indicates that the verification result regarding the mobile phone number was negative, information indicating that the verification result is negative.

Furthermore, the invention also relates to a computer program for verifying a mobile phone number to determine whether a message or positioning service in a mobile radio communication system should be performed with respect to the mobile telephone number. The computer program includes computer program code portions which, when run by a verifier, enable the verifier to: store a mobile number and a corresponding mobile subscriber identity number in a database of the verifier; in response to a verification request, send an IMSI query requesting a mobile subscriber identity number registered in conjunction with the mobile phone number in a home location register; retrieve from the database the stored mobile subscriber identity number; comparing the stored mobile subscriber identity number and a mobile subscriber identity number received in response to the IMSI query; and initiating the execution of the message or positioning service regarding the mobile phone number if the comparison shows that the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number.

The invention also relates to a computer program product comprising computer readable means on which the computer program is stored.

Further aspects of the invention are described in the following detailed description and in the appended claims.

535 546

Brief description of the drawings

<td>Fig. 1</td><td>is a schematic illustration of a mobile radio communication system comprising a mobile radio communication network.</td>

<td>Fig. 2</td><td>is a flowchart illustrating one embodiment of a method for verifying a mobile number.</td>

<td>Fig. 3</td><td>illustrates an embodiment where a verification device can communicate with CPRs via a network bridge.</td>

<td>Fig. 4</td><td>is a signal diagram illustrating an embodiment of a method for registering a mobile number with a verification device.</td>

<td>Fig. 5a</td><td>is a signal diagram illustrating a signal scenario in one embodiment of a method for verifying a mobile number.</td>

<td>Fig. 5b</td><td>is a signal diagram illustrating a signal scenario in one embodiment of a method for verifying a mobile number.</td>

<td>Fig. 5c</td><td>is a signal diagram illustrating a signal scenario in one embodiment of a method for verifying a mobile number.</td>

<td>Fig. 5d</td><td>is a signal diagram illustrating a signal scenario in one embodiment of a method for verifying a mobile number.</td>

<td>Fig. 6a Fig. 6b</td><td>is a schematic illustration of an embodiment of a verification apparatus. is a schematic illustration showing another aspect of the embodiment of the verification apparatus shown in Fig. 6a.</td>

<td>Fig. 7</td><td>is a schematic illustration of a third-party application server arranged to request verification of a mobile phone number.</td>

<td>Fig. 8</td><td>is a schematic illustration of a communication system comprising a broker mode comprising a verification apparatus.</td>

Detailed description

An example of a mobile radio communication system 100 is shown schematically in Fig. 1. Mobile radio communication system 100 comprises at least one mobile radio communication network 103, which in the description will sometimes be referred to as network 103 for the sake of brevity. A mobile radio communication network 103 is normally connected to other networks 104, such as, for example, public circuit switched telephone networks (PSTNs), other mobile radio networks, the Internet, etc.

535 546

Network 103 comprises a plurality of radio base stations 105 providing mobile radio communication to mobile stations (MS's) 110 over an air interface. For example, an MS 110 can be a mobile phone, a laptop, a handheld computer or any other radio capable device. A radio base station 105 is connected, often via a base station controlling node, to a Mobile Switching Center (MSC) 115, which can, among other things, provide routing and mobility management for communication sessions to and from MS 110. Normally, a plurality of radio base stations 105 are connected to each MSC 115th

Network 103 in Fig. 1 further includes a Home Location Register (CPR) 120, which includes a central database containing details of the mobile service subscriptions in the network 103. In particular, the CPR 120 for each subscription stores a mobile subscriber identity number, often referred to as International Mobile Subscriber Identity (IMSI), and at least one telephone number assigned to the subscription, where such telephone number is often referred to as an MSISDN for the subscription. The mobile subscriber identity number and mobile phone number are also normally stored on a Subscriber Identity Module (SIM) card (not shown) used in conjunction with an MS 110 to identify the mobile subscription in the MS 110. The terms IMSI and MSISDN are used herein when they are mentioned in the description and figures for reference to mobile subscriber identity numbers and mobile telephone numbers in general, including when reference is made to mobile subscriber identity numbers and mobile numbers in standards for mobile radio communication where a different terminology is used.

Via, for example, the Internet or other networks 104, a service provider that is outside the network 103 may utilize a messaging service and / or a positioning service as part of a service provided to a customer who is also a subscriber to services in a mobile radio communications network. In the following, the term message or positioning service will be used in reference to a service performed using a mobile radio communications network relating to a mobile number, the service being either a messaging service or a positioning service. For example, a messaging or positioning service can be a short message service (SMS) service, multimedia messaging service (MMS), an email service, a data stream service, a push messaging service, a WAP (Wireless Application Protocol) service, a positioning service based on triangulation, a positioning service based on identification of the cell where the mobile subscription to which the mobile phone number is currently associated is active, etc.

535 546

A service provider that is outside the network 103 will hereafter be referred to as a third-party service provider and a service provided by a third-party service provider will be referred to as a third-party service. For example, a third-party service may be a non-portal service, that is, a service that is not provided through a portal run by the operator of the network 103 in which the recipient of the third-party service is registered, but is provided directly from the third-party service provider. For example, a third-party service provider may be a mobile network operator providing services to mobile subscribers in networks 103 operated by other operators, or a service provider that does not operate any mobile radio communications network, but a service provider that utilizes network 103 to communicate with MS 110.

Third-party services where a messaging or positioning service is utilized may be, for example: a service provided by a bank, where an account statement or other information is sent to an account holder via SMS or other messaging service; a security-enhancing service provided by a company operating a website where its customers have accounts, whereby an account PIN can be sent via SMS or other messaging service to a mobile subscription belonging to the account holder; an ATM service where ATM fraud is prevented by checking that the bank account holder's position matches the ATM's by comparing the bank account holder's mobile subscription with a stored ATM (ATM) position before being allowed to withdraw money, etc. There are many other ways such as messaging or positioning services may be used by third party services.

In many third-party services that utilize messaging or positioning services, the integrity of service users, and / or the confidentiality of information provided to or by the service, is important. For example, a company that runs a website may not want to send a pin code via SMS to an account holder, if there is a significant risk that the SMS will end up in the wrong hands; an ATM operator may not want to perform a positioning of a mobile subscription in the ATM example given above, if there is a significant risk that the mobile subscription does not belong to the bank account holder but could belong to a person who has not agreed to be positioned, etc.

535 546

To enjoy a third-party service that utilizes a messaging or positioning service, a customer of the third-party service will often need to provide the third-party service provider with the mobile phone number for their mobile subscription. Because a mobile number is a number unique to a subscription, the mobile phone number can be used as an identifier of a mobile subscription for a customer of a third-party service provider. However, the mobile phone number is often transferred to a new subscription when a mobile subscription ends. Unless the customer to the third party service informs the third party service provider that he / she no longer has access to the mobile phone number, a message or positioning service that is part of the third party service, such as sending an SMS or positioning the mobile subscription, will be performed for the wrong person. It is true that some mobile network operators have guidelines that define a time interval within which a mobile number for a canceled subscription cannot be reused for a new subscription. However, such a time interval, if the third party service provider is never informed of the termination of the mobile subscription, will only temporarily prevent the part of the third party service utilizing the messaging or positioning service from being performed with respect to the wrong person.

As mentioned above, a mobile radio communication network normally uses a mobile subscriber identity number to identify a mobile subscription. The network 103 stores the mobile subscriber identity number and the mobile phone number in HLR 120. According to one aspect of the invention there is provided a verification apparatus, where the mobile subscriber identity number associated with a mobile number can be verified in order to avoid a third party service being delivered with respect to the wrong person. By storing the mobile phone number and corresponding mobile subscriber identity number of a customer to a third party service, and by verifying that the mobile subscriber identity number associated with the mobile phone number has not changed before delivery of the third party service to the customer, all transfers of the mobile phone number to a new subscription number will be made after detected, since the mobile subscriber identity number associated with the mobile phone number when transferring a mobile number to a new subscription will change.

An embodiment of a method performed by a verification apparatus is illustrated schematically in FIG.

2nd By the method of Fig. 2, it can be determined whether a message or positioning service is to be performed with respect to a particular mobile number. In step 200, a database is stored at

535 546 the verification device a mobile number, as well as the mobile subscriber identity number associated with the mobile telephone number in the network 103 where the mobile subscription is held. In step 205, a request for verification of the mobile phone number is received, for example from an application server by the third-party service provider. The verification request is sent by the third-party application server in connection with a messaging or positioning service to be performed regarding a mobile phone number, and the result of the verification shall be used in deciding whether or not the messaging or positioning service should be performed.

In step 210, an IMSI query is sent to CPR 210 in which the subscription associated with the mobile phone number is registered. The IMS I query sent in step 210 includes information on the mobile phone number, and is a request for information on the mobile subscriber identity number associated with the mobile phone number in HLR 210 in which the mobile phone number is registered. As will be discussed more in relation to Fig. 3 below, for example, the IMSI query can be sent via a network bridge of the network 103. For example, if the IMSI query sent by the authentication device is in a format incompatible with the transmission protocol used by HLR 210, the IMSI query sent by the authentication device may trigger such a network bridge, or another node, to send a corresponding IMSI query to a format is compatible with the transmission protocol used by HLR 120.

In step 215, a response to the IMSI question is received from the CPR, where the answer to the IMSI question includes the mobile subscriber identity number or information indicating the mobile subscriber identity number associated with the mobile phone number in the CPR. In step 220, the mobile subscriber identity number received in the answer to the IMSI question is compared with the mobile subscriber identity number stored in conjunction with the mobile phone number in step 200. If the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number, it can be concluded that the mobile phone number is still used by the same subscriber as at the time of performing step 200 (the received mobile subscriber identity number and stored mobile subscriber identity numbers may be expressed in different formats, and therefore an exact identity is not necessarily required agreement between the two).

535 546

If the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number, step 225 occurs where the message or positioning service is started for the mobile phone number. On the other hand, if the verification result obtained in step 220 is negative, that is, if the received mobile subscriber identity number does not match the stored mobile subscriber identity number, the messaging or positioning service is not started. Instead, step 230 occurs where a verification response is sent to the node from which the verification query was received in step 205, where the verification response includes an indication of the negative verification result.

The initiation of the requested service in step 225 can be performed in different ways. For example, the initiation may include sending a verification response to the person requesting the verification, the verification response including an indication indicating that the result of the verification was positive, i.e., the received mobile subscriber identity number was found to correspond to the stored mobile subscriber identity number. Upon receipt of the positive verification response, the requesting requestor may then send a request for execution of the message or positioning service to a network 103. If the verification request received in step 205 is included in a message or positioning service request, the initiation of the requested service may include transmitting, to a mobile radio communication network, a request to perform the message or positioning service regarding the telephone number. If the verifier can perform at least portions of the service, the initiation may include performing these portions of the service.

A request for execution of the message or positioning service sent to a network 103 can be sent in accordance with a proprietary protocol, or a standardized protocol can be used for the transmission of the request for execution. For example, if the message or positioning service is SMS, the Short Message Peer-to-peer Protocol (SMPP) can be used to query the message or positioning service. Alternatively, other protocols can be used. The network 103 to which a request for execution is sent can be any network 103: the network 103 in which the mobile phone number is registered, or another network 103.

As mentioned above, a verification response including information based on the result of the comparison performed in step 220 can also be sent when the verification result is positive to the sender of the request for verification of the mobile phone number. The transmission of

535 The 546 verification response can be omitted, if desired, for example, if a confirmation as to whether the requested messaging or positioning service has been successfully performed or not will be sent to the person requesting the verification.

A result of the verification can be registered in the verification apparatus in connection with the stored mobile phone number and the associated mobile subscriber identity number, if desired. For example, a result of the comparison can be stored, the time of verification can be stored, etc.

A verification response to be sent by the verification device to the person requesting the verification may include information as to whether the mobile subscriber identity number stored by the verification device in connection with the mobile phone number corresponds to the mobile subscriber identity number received from the CPR in which the mobile phone number is registered. Such information may, for example, be indicated by a flag in the verification response message, or by any other means. Depending on the information received by the verification device in the answer to the IMSI question, the verification response message may include additional information. For example, if the answer to the IMSI question includes information about which network 103 the mobile phone number is currently registered, the verification response may include information indicating whether the mobile phone number is registered in the same network 103 as when the mobile phone number was stored in step 200 of the verification device, or in another network. . Such information may be included as a flag in the verification response message or as an indicator which may be more than two values. For example, a 2-bit indicator may be used, which may assume, for example, one of the following values: 1) the mobile subscriber identity number has not changed; 2) the mobile subscriber identity number has changed within the same network; 3) the mobile subscriber identity number has changed and the mobile network has changed; 4) the mobile phone number is not used. Alternatively, the verification response message may include an identity of the network 103 in which the mobile phone number is currently stored. From information related to whether the network 103 with which the mobile phone number is registered has changed, conclusions can be drawn about whether it is likely that the mobile phone number is now used by another subscriber in the same network 103, or whether the owner of the mobile phone number has moved his subscription to a new network. Other information may also be provided in a verification response message, such as, for example, information in which network the mobile subscription is currently active.

535 546

Where the messaging or positioning service is part of a third party service, a message may be sent to the mobile phone number in response to a negative verification result, if desired, the message informing the subscriber having the mobile phone number that the third party service will terminate with respect to the mobile phone number. This can be useful, as there are situations where the mobile subscriber identity number has changed even if the mobile phone number is still used by the same person. For example, if a user of a mobile number decides to move his mobile subscription to another network 103, or if he has requested a new SIM card to access various services provided by his network 103, the mobile subscriber identity numbers are normally changed. For example, such a message can be sent to the mobile phone number by the third-party application server, or by the authentication device.

The method illustrated in Fig. 2 can be implemented in relation to a mobile subscription in a network 103 operated in accordance with any standard, such as, for example, the Global System for Mobile Communications (GSM) standard, the Universal Mobile Telecommunications System (UMTS) standard, the Long standard Term Evolution (LTE), etc. The flow chart in Fig. 2 refers to a single mobile number. However, a verification device operating according to the method illustrated in Fig. 2 can be used for verification of a plurality of mobile numbers registered in the same or different networks 103, where different networks 103 may be of the same or different standards. Step 200 would normally be performed once per mobile subscription, while steps 205-220 would normally be performed for a mobile number each time a third-party service provider requests verification of the mobile phone number. Thus, a substantial period of time may elapse between the execution of steps 200 and steps 205-230 with respect to the same mobile number.

For example, a message type that already exists in a mobile phone standard can be used for the IMSI query sent in step 210. Examples of already existing message types that can be used are the Mobile Application Part Send Routing Information (MAP SRI) message type specified in ETSI Technical Specification (TS) 129 002 v 8.9.0 or ETSI TS 100 974 v. 7.15.0 (for example, SRI for SMS, or other SRI messages, such as an SRI message for using an MSC 115 for requesting routing information from a HLR 120), the type of send_IMSI message, or any other message type that provides an option for CPR spreads. In a MAP SRI535 546 request, the mobile phone number is included and in a MAP SRI response the associated mobile subscriber identity number is included. MAP signaling is normally performed via the SS7 signal network used for signaling between different nodes in mobile radio communication networks 103 and in other telephone networks. Alternatively, a new message type can be specified for use as the IMSI query.

Often, a verification apparatus for carrying out the method of Fig. 2 need not have direct access to the SS7 signal network, or other means for communicating directly with HLR 120 in the network 103 where a mobile number is registered. In such cases, the authentication apparatus may, for example, be connected to an application server or network bridge 310, which may be, for example, an application server or network bridge 310 of a PLMN or of a mobile radio communication network 103, for example a gateway MSC. This is illustrated in Figure 3, where a verification device 300 is connected to network bridge 310 and to an application server (AS) 305 for a third-party service provider, hereinafter referred to as third-party application server 305 or AS 305 for the sake of brevity. The network bridge 310 is capable of communicating with at least one, and usually a plurality of CPRs 120, where an HLR 120 stores mobile subscriber identity number values ​​associated with mobile numbers currently registered in a network 103.1 in this set, the IMSI query in step 210 of Fig. 2 may be, for example, a proprietary message instructing the network bridge 310 to send a suitable IMSI query message to relevant CPR 120 for the mobile subscriber identity number associated with the mobile phone number included in the IMSI question. The network bridge 310, or another node instructed to do so by the network bridge 310, can then send an appropriate IMSI query message compatible with the relevant CPR 120, for example, a MAP SRI message or other message sent as discussed above, to the relevant CPR: a 120. Alternatively, the IMSI query transmitted by the verifier 300 may be in a format compatible with the relevant CPR 120.1, a network scenario where the verifier uses a CPR 120 in the form of an HSS in an IMS core network, the verifier can contact the HSS via the network bridge 310 in the form by an Interrogating Call Session Control Function (ICSCF), which communicates with the HSS user's DIAMETER protocol.

Fig. 4 is a signal diagram schematically illustrating signaling that can be performed in relation to step 200 of Fig. 2. The signaling in Fig. 4 illustrates a scenario in which AS 305 instructs the verifier 300 to register a mobile number in relation to which

535 546 future verification can be requested by AS 305. A Register MSISDN command 400 is sent from AS 305 to the verifier 300, where the Register MSISDN command 400 includes a mobile number to be registered by the verifier 300. Upon receipt of the Register MSISDN command 400, the authentication device 300 sends an ISMI query 405 to the CPR in which the mobile subscription associated with the mobile phone number is registered, where the IMSI query 405 includes the mobile phone number. IMSI query 405 will be received by CPR 120 for network 103 in which the mobile phone number is registered, possibly via a network bridge 310 as discussed in connection with Fig. 3. An answer 410 to the IMSI question is then received by the verification device 300 from HLR 120, where the answer 410 to the IMSI question includes the mobile subscriber identity number associated with the mobile phone number. As mentioned above, the answer to the IMSI question may include additional information related to the subscription associated with the mobile phone number, such as, for example, information on which network 103 the mobile phone number is registered and in which network the mobile subscription is currently active.

Upon receiving the answer 410 to the IMSI question, the verification device 300 stores the mobile phone number and its associated mobile subscriber identity number in a database. Alternatively, the mobile phone number may be stored upon receipt of the Register MSISDN command 400 and the associated mobile subscriber identity number may be stored upon receipt of the answer 410 to the IMSI query.

If desired, a Register MSISDN ACK 415 can then be sent by AS 305, indicating that the requested registration of the mobile phone number has been completed.

In Fig. 4, the storage of a mobile number and associated mobile subscriber identity number are initiated by the receipt of a Register MSISDN command message 400 from AS 305.1 In this scenario, for example, the mobile phone number may have been registered manually or automatically for a service in AS 305 before AS 305 sends message 400. Alternatively, the storage of the mobile phone number and the associated mobile subscriber identity number in the verifier 300 may be initiated in other ways, such as, for example, by manually inserting a mobile number into a user interface of the verifier 300.

535 546

Figures 5a-5d are signal diagrams illustrating various scenarios and embodiments of the invention, assuming that an input comprising a mobile number and associated mobile subscriber identity number has already been stored in a verification device 300 (compare steps 200 in Figures 2 and 4). In Fig. 5a, a verification device 300 receives a Verify-MSISDN Request message 500 from AS 305, where the Verify-MSISDN Request message 500 includes a mobile number to be verified. Receiving Verify MSISDN Request Message 500 triggers verification device 300 to send an IMSI query 505 which includes the mobile phone number, the IMSI query 505 having been received by HLR120 in the network 103 in which the mobile phone number is registered. Verifier 300 then receives a response 510 to the IMSI question from HLR 120, where the answer 510 to the IMSI question includes the mobile subscriber identity number associated with the mobile phone number in HLR 120.

Upon receiving the response 510 to the IMSI query, the verifier 300 performs step 220 of Fig. 2, where the mobile subscriber identity number received by the response 510 to the IMSI question is compared with the mobile subscriber identity number stored in conjunction with the mobile phone number of the verifier 300 (cf. steps 200 in Figs. 2 and 4). In the scenario illustrated in Fig. 5a, the received mobile subscriber identity number corresponds to the stored mobile subscriber identity number and the mobile phone number is thus verified. Initiation of the message or positioning service is then performed by the verifier by sending a positive verifier response to AS 305, where the positive verifier response 515 includes an indication that the verifier was successful, for example in the form of a flag or other parameter in the verifier response message 515 .

Fig. 5b illustrates a scenario similar to that of Fig. 5a, but where the comparison performed in step 220 shows that the stored mobile subscriber identity number does not correspond to the mobile subscriber identity number received in response 505 to the IMSI question. A verification response 515 is sent by the authentication device 300 to AS 305, where the verification response 515 includes an indication that the stored mobile subscriber identity number does not correspond to that currently associated with the mobile telephone number, i.e. that the verification result is negative. As discussed above, additional information may be included in a verification response 515.

535 546

In the embodiment of the method illustrated in Fig. 5b, AS 305 records in a customer database that a negative verification response has been received regarding the mobile phone number, see event 516. A message 517 is then sent to the mobile phone number and informs the user of the mobile phone number that the third party service has performed in relation to the telephone number verification. terminated for the mobile phone number. Alternatively, such a message 517 may be transmitted by AS 305 and ask a mobile radio communication network 100 to deliver the message 517 using a proprietary or standardized protocol, compare the discussion in connection with step 225 above, or the transmission of such message 517 may be skipped.

As mentioned above, a request for verification of a mobile number may be included in the request for a message or positioning service. Fig. 5c illustrates a scenario where a request for verification of a mobile phone number is included in a question of delivering a special message to a subscriber in a mobile radio communication network 103, for example by SMS, MMS, e-mail, WAP, or any other messaging service. . A Deliver-Message-Request Message 520 is received by a verification device 300 from a service provider 305. Deliver-Message-Request 520 includes information about a mobile number to which the message is to be delivered, as well as information to be included in the message. Upon receipt of Deliver Message Message 520, the verifier 300 sends an IMSI query 505, receives a response 510 to the IMSI query, and performs a comparison 220 of the stored and received mobile subscriber identity number as described in connection with Fig. 5a. In the scenario in Fig. 5c, the comparison shows that the mobile subscriber identity number received in IMSI query 510 corresponds to that stored in the verification device 300 and the mobile phone number can thus be verified. Thus, a message 525, which includes the information received in Deliver Message Message 520, is sent to the mobile station 110 associated with the mobile phone number. For example, the message 525 may be sent by the verifier 300 and ask a mobile radio communication network 103 to deliver the message 517 using a prorated or standard protocol, compare the discussion in connection with step 225 above.

A Delivery Message ACK 530 is then also sent to the verifier 300 to AS 305 in Fig. 5c. Such a Delivery Message ACK 530 may alternatively be sent earlier than the transmission of message 525 to the mobile subscription as a

535 546 verification response message 515, or sent in response to a delivery ACK received in response to the transmission of message 525, or it can be skipped.

Fig. 5d illustrates a scenario where a request for verification of a mobile phone number is included in a request for positioning of the mobile subscription associated with the mobile phone number. A verification device 300 receives a Positioning Request 535, wherein Positioning Request 535 includes information on the telephone number of the mobile subscription to be determined. Upon receiving Positioning Request 520, the verifier 300 sends an IMSI query 505, receives a response 510 to an IMSI query, and performs a comparison 220 of the stored and received mobile subscriber identity number as described in connection with Fig. 5a. In the scenario in Fig. 5d, the comparison shows that the mobile subscriber identity number received in IMSI query 510 corresponds to what is stored in the verification device 300 and the mobile phone number can thus be verified. Accordingly, the verifier 300 initiates a location determination of the mobile subscription associated with the mobile phone number. Such a location determination can be initiated, for example, by the verifier 300, which asks a mobile radio network 100 for performing the triangulation, or by the verifier asking the mobile radio network 100 to transmit a cell ID of the cell where the mobile station associated with the mobile phone number is currently active. , or in any other way appropriate to the resolution requirements of the requested positioning. Since the position of the mobile subscription is known to the verifier 300, a position warning message 545 is sent to AS 305 including an indication of the position of the mobile subscription associated with the mobile phone number. In the example given above where the mobile subscription position is used to avoid ATM fraud, a table listing the identity of the cell (s) covering the location of the ATM operated by the third party service provider, or a table listing the geographical position of all such ATMs for example, held by the verifier 300 or AS 305. A comparison can then be made between the position of the mobile subscription obtained from the positioning and the position of the ATM where a ATM card is used for withdrawing money, where the ATM card is registered at the same ATM customer as the mobile phone number. If such a table listing the ATM position is saved by the verifier 300, a positioning query message 535 in this example may advantageously include an indication of the ATM to which the positioning query 535 relates and

535 For example, the 546 positioning result 517 may include a flag indicating whether or not the mobile station 110 associated with the mobile phone number is currently located near this ATM.

If the comparison 220 performed in the scenario of Fig. 5c or 5d had shown that the received mobile subscriber identity number does not correspond to that stored by the verification device 300 in step 200, the transmission of message 525 (Fig. 5c) or the positioning (Fig. 5d) would not normally have been performed. As discussed above in connection with Fig. 2, an indication that the subscription associated with the mobile phone number has changed since the mobile phone number was registered in the verification device 300 is advantageously sent to AS 305 in a verification response 515, or in a positioning response 545 / delivery message ACK 530.

In an implementation, a particular service request type received by an authentication device from an application server, such as a Positioning Request 535 or a Deliver-Message-Request 520, can call a verification of a mobile number by default. In an alternative implementation, a service request may include a flag, or other indication, indicating to the verifier 300 whether or not a verification of the mobile phone number is requested in relation to the delivery of the requested messaging or positioning service.

The IMSI question 405 and the answer 410 to the IMSI question in Figures 5a-5d may advantageously be of the same message type as the IMSI question 405 and the answer 410 to the IMSI question in Figure 4, although different message types may alternatively be used.

Messages sent between a verification device 300 and a third-party service provider 305, such as a register MSISDN request 400, a verify MSISDN request 500, a verification response 515, a positioning request 535, etc., may be, for example, priority messages. If the authentication device 300 and third-party AS 305 are implemented in the same node, such messages may be intimate messages.

The signal scenarios illustrated in Figures 5a-5d are only examples and the verification method illustrated in Fig. 2 can be implemented in a number of different third-party service scenarios and in relation to a number of message or positioning services.

535 546

In Fig. 6a, an example of the verifier 300 is illustrated schematically. The verifier 300 in Fig. 6a includes a verification management mechanism 600 including a comparison mechanism 605. Verifier 300 further includes a database 615 in which entered information including mobile numbers and associated mobile subscriber identity numbers can be stored. The authentication management mechanism 600 is coupled to the database 615 so that the authentication management mechanism 600 can access data stored in the database 615. The verification management mechanism 600 is additionally connected to an interface 620 for communication with at least one AS 305 and to an interface 625 for communication with HL possibly via a network bridge 310 as shown in Fig. 3). Interfaces 620 and 625 can be the same or different physical interfaces and they can normally serve as both signal inputs and signal outputs.

Verification management mechanism 600 in Fig. 6a is arranged to receive a Register MSISDN command 400 from an application server 305 via interface 620 and to instruct interface 625 to send an IMSI query 405 in response to receiving a RegisterMSISDN command 405. In addition, the verification management mechanism 600 in Fig. 6a is arranged to receive a response 410 to an IMSI query via interface 625 and to instruct the database 615 to store, in the database 615, a mobile number received in a RegisterMSISDN command 400 and an associated mobile subscriber identity number received in a response. 410 on the IMSI issue. Additionally, the authentication management mechanism 600 is arranged to receive a Verify-MSISDN Request 500 for a mobile number from AS 305 via interface 620 and to instruct interface 625 to send an IMSI query 505 in response to receiving a Verify-MSISDN Request 500. The verification management mechanism 600 is further arranged to receive a response 510 to an IMSI query via interface 625; extracting a received mobile subscriber identity number from a received response 510 to IMSI query, retrieving a stored mobile subscriber identity number from database 615; and delivering a received mobile subscriber identity number and a stored mobile subscriber identity number associated with the same mobile number to the comparison mechanism 605. The comparison mechanism 605 is arranged to compare the received mobile subscriber identity number with the stored mobile subscriber identity number and to deliver a comparison result. In addition, the verification management mechanism 600 may be arranged to send a Verification Response 515 to AS 305.

535 546

The verifier 300 in Fig. 6a is given by way of example only and the verifier 300 can be implemented in other ways. For example, instead of, or in addition to, being arranged to receive a request for registration of a mobile number from AS 305 via interface 620, the verification device 300 may include a user interface so that a request for registration of a telephone number can be entered manually. In addition, a verification device 300 may be distributed in another way, for example, such that a verification management mechanism 600 is arranged to perform some of the tasks described above, while another (s) are arranged to perform other of the tasks described above. Further, the verification apparatus 300 may be implemented in a physically distributed manner such that, for example, the database 615 and the verification management mechanism 600, or parts of the verification management mechanism 600, are located at different geographical locations even if they are run as the same logical apparatus.

The verification management mechanism 600 and the database 615 in Fig. 6a may be implemented by suitable software and hardware. For example, database 615 may be a general database, or a database specifically developed for the authentication device 300. Database 615 may be compatible with Structured Query Language (SQL) or any other appropriate language, for insertion and retrieval of information from database 615. For example, the verification management mechanism 600 may be implemented using one or more general processors, or one or more processors specially developed for the verification device 300 in combination with software for performing a mobile number verification (cf. Fig. 2).

Fig. 6b shows an alternative way of schematically illustrating the verifier 300 according to Fig. 6a. Fig. 6b shows the verification apparatus 300 including process means 630 coupled to a computer program product 635 in the form of a memory, as well as to interfaces 620 and 625. The memory comprises computer-readable code means which stores a computer program 636, which when executed by the processing means 630, the verification apparatus 300 perform the verification method as illustrated in Fig. 2. In other words, the verification management mechanism 600 and its comparison mechanism 605 in this embodiment can be implemented by means of corresponding program modules of the computer program 636.1. The embodiment shown also includes the computer program product 635 the database 615, but in other embodiments, the database 615 can be stored in a second memory (not shown). 300. Processor body 630

535 54G may be one or more processors - for example, a processor of the processing means may be arranged to execute code related to database 615, and another processor may be arranged to execute code related to the authentication management mechanism 600, or the same processor may be used to execute the code for the authentication management mechanism and the database code. The computer program product 635 can be any type of non-volatile computer-readable device, such as a hard disk, flash memory, electrically erasable programmable read-only memory (EEPROM), a DVD, a CD, a USB memory, etc.

Figure 7 shows an example of AS 305 arranged to provide at least one third-party service to customers of a third-party service provider. AS 305 includes a verification request processing mechanism 700, a memory with a third-party service customer information register 705, and a communication to / from the verification device 300 interface 7, wherein the verification request processing mechanism 700 is coupled to the interface 70 and the customer information register. The customer information register 705 is contained in a memory, for example in a database, arranged to store information related to customers for a third party service, where such information is, for example, the telephone number of a customer's mobile subscription, an operator code for the network 103 where the customer's mobile subscription is registered, verification result information obtained from the verification device 300 in relation to a customer, information about which services a customer subscribes to, etc. The authentication request handling mechanism 700 is arranged to retrieve information from the customer information register 705, such as a mobile number to be verified; sending a request for registration of a mobile number to a verification device 300 via interface 710 (compare register MSISDN command 400 in Fig. 4); and sending a verification request to the verification apparatus 300 to determine whether a message or positioning service in a mobile radio communication system is to be performed for a mobile number. (compare verify MSISDN request 500 in Fig. 5a; deliver message request 520 in Fig. 5c; 535 in Fig. 5d). In addition, the verification request processing mechanism 700 may be arranged to store information received from a verification device via interface 715 in the customer information register 705, such as information related to whether or not a verification event has been successful. AS 305 can be implemented as a suitable combination of hardware and software. The schematic illustration of a verification apparatus 300 shown in Fig. 6b can also be used as a schematic illustration.

535 546 of an embodiment of AS 305, which includes process means and memory means, wherein the memory means stores computer program code portions which, when executed by the process means, AS 305 sends to a verification device 300 a request for registration of a mobile number as well as computer program code portions which are executed by the process means. AS 305 to send to the verification device 300 a request for verification of the mobile phone number.

The verification device 300, for example, can be implemented as part of an application server. In Figures 3-5, verification apparatus 300 is illustrated as a separate node from AS 305. However, verification apparatus 300 may alternatively be implemented as part of AS 305. If the verifier 300 is part of AS 305, any message sent between the verifier 300 and AS 305 may advantageously be an internal message (e.g., Register MSISDN command 400, Verify MSISDN request 500; Verification response 505, etc.). Interfaces 620 and 710 can then be internal interfaces.

For example, when a verification device 300 is implemented in a node separate from AS 305, the verification device 300 can serve a plurality of different third-party application servers belonging to the same or different service providers. For example, the verification device 300 may be implemented in an application server that is operated as a broker mode for services in a communication system for various service providers. For example, such a switching mode may be arranged to perform messaging or positioning services on various mobile radio networks 103 upon request from various ASs 305. An example of a communication system 800 comprising a brokering mode 805 arranged to provide access to messaging or positioning services provided in a variety of mobile radio communication systems 103j-1, 103j, 103j + 1, to a variety of third-party service providers, 305Ϊ-1,3O5i and 3051 + 1 is schematically illustrated in Fig. 8. The communication system 800 may comprise all or part of the mobile radio communication system 100 shown in Fig. 1.

Although various aspects of the invention are set out in the appended independent claims, other aspects of the invention comprise a combination of any features presented in the description above and / or in the accompanying claims.

535 546 claims, and not only the combinations explicitly stated in the appended claims.

One skilled in the art will appreciate that the technology presented herein is not limited to the embodiments shown in the accompanying drawings and the prior detailed description, which are presented for illustrative purposes only, but may be implemented in a number of different ways and defined by the following claims.

535 546