MOBILE APPLICATION REGISTRATION

• US 20090328144A1
• Filed: 08/08/2007
• Published: 12/31/2009
• Est. Priority Date: 09/14/2006
• Status: Active Grant

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Sherlock, Gerard, Pilkington, John D.R.
• Granted Patent: US 9,047,444 B2
• Time in Patent Office: Days
• US Class Current: 726/2
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/123 by using dedicated hardware, e.g. dongles, smart cards, cryptographic processors, global positioning systems [GPS] devices
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography postage metering system using cryptography G06Q2250/05
• CPC Class Codes: G06Q 2220/10 Usage protection of distributed data files
• CPC Class Codes: G06Q 2220/18 Licensing
• CPC Class Codes: G11B 20/00086 Circuits for prevention of unauthorised reproduction or copying, e.g. piracy indicating unauthorised use of record carriers in general G11B23/28; scrambling for television signal recording H04N5/913; network architectures or network protocols for network security H04L63/00; cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
• CPC Class Codes: H04L 63/0853 using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04W 12/065 Continuous authentication
• CPC Class Codes: H04W 12/48 using secure binding, e.g. securely binding identity modules to devices, services or applications
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor

Abstract

A method of registering an application on a mobile terminal in a mobile network with an application server, said mobile terminal comprising an identity module, said method comprising the steps of: receiving at the application server a first message for registering the application, said first message comprising a telephone number associated with the identity module; generating by the application server a unique identifier and associating the unique identifier with the telephone number; sending a second message from the application server to the mobile terminal, said second message comprising the unique identifier; and generating and storing at the mobile terminal a data block comprising the unique identifier, a subscriber identity associated with the identity module and a terminal identifier associated with the mobile terminal.

Claims

1. A method of registering an application on a mobile terminal (102) in a mobile network (112) with an application server (120), said mobile terminal (102) comprising an identity module (106), said method comprising the steps of

a) receiving at the application server (120) a first message for registering the application, said first message comprising a telephone number associated with the identity module (106);

b) generating by the application server (120) a unique identifier and associating the unique identifier with the telephone number;

c) sending a second message from the application server (120) to the mobile terminal (102), said second message comprising the unique identifier; and

d) generating and storing at the mobile terminal (102) a data block comprising the unique identifier, a subscriber identity associated with the identity module (106) and a terminal identifier associated with the mobile terminal (102).

2. A method according to claim 1 comprising a further authentication step of:

e) checking if the subscriber identity stored in the data block is the same as the subscriber identity obtained from the identity module (196) and checking the terminal identifier stored in the data block against the terminal identifier obtained from the mobile terminal (102).

3. A method according to claim 2, wherein steps a) to d) are repeated if either of the checks in step e) fail.

4. A method according to claim 2, wherein the application is terminated if either of the checks in step e) fail.

6. A method according to claim 1, wherein the first and second messages are sent over the mobile network (112).

8. A method according to claim 1, wherein the telephone number is used by the mobile network (112) to route the second message to the mobile terminal (102), and the telephone number in the first message is provided by the mobile network (112).

9. A method according to claim 1, wherein the first and second communications methods are secure communications methods.

10. A method according to claim 1, wherein the first message originates from the mobile terminal (102).

5. A method according to claim 5, wherein the application uses the unique identifier to identify the mobile terminal (112) and the identity module (106) to the application server (120).

7. A method according to claim 5, wherein the first and second messages are short message service messages.

11. A system for registering an application on a mobile terminal (102) in a mobile network (112), said system comprising an application server (120), said mobile terminal (102) comprising an identity module (106), and wherein the application server (120) is adapted for receiving a first message for registering the application, said first message comprising a telephone number associated with the identity module (106), for generating a unique identifier and associating the unique identifier with the telephone number, and for sending a second message to the mobile terminal (102), said second message comprising the unique identifier;

the mobile device (102) is adapted for generating and storing a data block comprising the unique identifier, a subscriber identity associated with the identity module (106) and a terminal identifier associated with the mobile terminal (102).