System and method for controlling terminal application usage through subscriber-application association

• US 20020188736A1
• Filed: 06/11/2001
• Published: 12/12/2002
• Est. Priority Date: 06/11/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Jarvensivu, Hannu
• Application Number:
  US09/878,629
• Publication Number:
  US 20020188736A1
• Time in Patent Office: Days
• US Class Current: 709/229
• 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: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04W 12/08 Access security

Abstract

A system and method for authorizing operation of an application on a terminal in a network. An application is initiated on the terminal by a requesting user. A user data segment locally available at the terminal includes data that is unique to the requesting user, and is searched for an application identifier corresponding to the application initiated by the user. If the application identifier is found not to be associated with the local user data segment, a remotely stored user data segment available on the network is searched to determine if it includes the application identifier. If the application identifier is located in the remotely stored user data segment, the local user data segment on the terminal is updated with the application identifier, and execution of the application is enabled for use by the requesting user. Otherwise, execution of the application is prohibited until the user complies with access rules, such as providing payment for permission to execute the application.

Claims

1. A method for authorizing operation of an application on a terminal in a network, comprising:

initiating the application on the terminal of a requesting user;

searching a local user data segment for an application identifier of the initiated application, wherein the local user data segment is unique to a requesting user and locally available at the terminal;

searching for the application identifier on a remotely stored user data segment available on the network external to the terminal, if the application identifier is not located in the local user data segment; and

if the application identifier is located in the remotely stored user data segment, updating the local user data segment on the terminal with the application identifier, and enabling execution of the application by the requesting user.

2. The method as in claim 1, further comprising prohibiting execution of the application by the requesting user on the terminal where the application identifier is not located in the remotely stored user data segment.

3. The method as in claim 1, further comprising presenting the requesting user with an option to acquire the application, if the application identifier is not located in the remotely stored user data segment.

4. The method as in claim 3, further comprising accepting payment from the requesting user to acquire the application.

5. The method as in claim 4, further comprising updating the remotely stored user data segment to include the application identifier in response to accepting payment.

6. The method as in claim 4, further comprising updating the local user data segment to include the application identifier in response to accepting payment.

7. The method as in claim 4, further comprising enabling execution of the application by the requesting user in response to accepting payment.

8. The method as in claim 1, further comprising transmitting the application to the terminal, prior to initiating the application on the terminal.

9. The method as in claim 8, wherein transmitting the application to the terminal comprises transmitting the application from an authorized source of the application via the network.

10. The method as in claim 9, further comprising updating the remotely stored user data segment to include the application identifier, updating the local user data segment to include the application identifier, and enabling execution of the application by the requesting user, in response to the transmitting of the application from the authorized source of the application.

11. The method as in claim 8, wherein transmitting the application to the terminal comprises downloading the application onto the terminal from an unauthorized source of the application, wherein such transmission fails to cause updating of the remotely stored user data segment to include the application identifier, updating of the local user data segment to include the application identifier, and enabling execution of the application by the requesting user.

12. The method as in claim 1, wherein searching a local user data segment comprises searching a Subscriber Identity Module (SIM) database.

13. The method as in claim 12, wherein the SIM database is transferable to a plurality of different terminals.

14. The method as in claim 1, further comprising enabling execution of the application by the requesting user without searching the remotely stored user data segment stored on the network, if the application identifier is located in the local user data segment.

15. The method as in claim 1, wherein searching the remotely stored user data segment stored on the network for the presence of the application identifier comprises searching a profile directory stored on a server available on the network.

16. The method as in claim 1, further comprising synchronizing the local user data segment and the remotely stored user data segment at one or more predetermined occurrences such that at least the application identifier is replicated in both the local user data segment and the remotely stored user data segment.

17. The method as in claim 1, wherein searching the local user data segment comprises searching a portable storage module for the presence of an application identifier of the initiated application.

18. The method as in claim 17, wherein searching a portable storage module comprises searching a memory associated with a Subscriber Identity Module (SIM).

20. The method as in claim 19, wherein examining a locally stored user data segment for an application identifier of the application comprises searching a portable access database unique to the user for the application identifier.

21. The method as in claim 19, further comprising periodically synchronizing the locally stored user data segment and the remotely stored user data segment.

19. A method for charging for an application operable on a terminal within a network, where the application was not obtained from the application supplier where application charging generally occurs, comprising:

attempting to execute the application by a user on the terminal;

examining a locally stored user data segment for an application identifier of the application, and enabling execution of the application if the application identifier is found in the locally stored user data segment;

examining a remotely stored user data segment for the application identifier if the application identifier is not found in the locally stored user data segment, and enabling execution of the application if the application identifier is found in the remotely stored user data segment;

prohibiting the user from executing the application if the application identifier is not found in either the locally or remotely stored user data segment, and requiring payment for the application as a condition for thereafter enabling execution of the application.

22. A system for allowing a network service provider to control use of an application having an associated application identifier, comprising:

a transferable user data module including local user profile information unique to a user requesting access to the application;

a profile directory maintained on a network, wherein the profile directory includes remote user profile information for at least one user;

a user terminal having the application available therein, wherein the user terminal is coupled to the transferable user data module, the user terminal comprising;

(a) a compare module coupled to receive the application identifier of the application to determine whether the application identifier matches any authorized application identifiers associated with the local user profile information; and

(b) an application execution module to permit user execution of the application if the application identifier matches one of the authorized application identifiers associated with the local user profile information, and to request permission to execute the application from the service provider by searching the remote user profile information for the application identifier if the application identifier fails to match one of the authorized application identifiers associated with the local user profile information.

23. The system of claim 22, wherein the transferable user data module comprises a Subscriber Identity Module (SIM).

24. The system of claim 22, wherein the user terminal comprises a wireless terminal.

25. The system of claim 24, wherein the wireless terminal comprises a wireless telephone operable in a wireless network environment.

27. The method of claim 26, wherein linking an application identifier with user profile information comprises storing the application identifier in a network profile directory segment remote to the terminal.

28. The method of claim 27, wherein determining whether the application identifier has been linked with the user profile information comprises searching a portion of the network profile directory uniquely corresponding to the requesting user for the application identifier.

29. The method of claim 28, wherein linking an application identifier with user profile information further comprising replicating the application identifier in a portable access module, if the application identifier is located in the network profile directory.

30. The method of claim 26, wherein linking an application identifier with user profile information comprises storing the application identifier in a portable access module.

31. The method of claim 30, wherein determining whether the application identifier has been linked with the user profile information comprises searching the portable access module for the application identifier.

26. A method for enabling operation of an application on a terminal in a network, comprising:

linking an application identifier with user profile information unique to each user authorized to execute the application;

determining whether the application identifier has been linked with the user profile information of a requesting user attempting to execute the application from the terminal;

denying execution of the application to the requesting user if the application identifier has not been linked with the user profile information; and

enabling execution of the application to the requesting user if the application identifier has been linked with the user profile information.

32. A method for charging for an application operable on a terminal within a network, where the application was not obtained from the application supplier where application charging generally occurs, comprising:

attempting to execute the application by a user on the terminal;

examining a locally stored user data segment for an application identifier of the application, and enabling execution of the application if the application identifier is found in the locally stored user data segment;

examining a remotely stored user data segment for the application identifier if the application identifier is not found in the locally stored user data segment, and enabling execution of the application if the application identifier is found in the remotely stored user data segment; and

prohibiting the user from executing the application if the application identifier is not found in either the locally or remotely stored user data segment.

33. A method for authorizing execution of an application available on a terminal in a network, comprising:

storing an application identifier as at least a portion of a user data segment unique to each user authorized to execute the application, wherein the user data segments corresponding to each user are remotely stored on the network external to the terminal;

initiating the application on the terminal of a requesting user;

transmitting a request to the network to ascertain whether the requesting user is authorized to execute the application;

determining whether the application identifier is remotely stored in the requesting user'"'"'s user data segment on the network, thereby determining whether the requesting user is authorized to execute the application;

prohibiting execution of the application to the requesting user if not authorized to execute the application; and

enabling execution of the application to the requesting user if authorized to execute the application.

34. The method as in claim 33, further comprising:

searching a locally stored user data segment for the application identifier upon initiating the application on the terminal of the requesting user; and

if the application identifier is stored in the locally stored user data segment, enabling execution of the application to the requesting user without requiring transmission of the request to the network and determining whether the application identifier is remotely stored on the network.

35. The method as in claim 33, further comprising providing the requesting user an option to pay for the application if the requesting user is not authorized to execute the application.

36. The method as in claim 35, further comprising enabling execution of the application to the requesting user upon providing payment for the application.

37. The method as in claim 33, further comprising:

searching a locally stored user data segment for the application identifier upon initiating the application on the terminal of the requesting user;

if the application identifier is stored in the locally stored user data segment, enabling execution of the application to the requesting user without requiring transmission of the request to the network and determining whether the application identifier is remotely stored on the network;

if the application identifier is not stored in the locally stored user data segment, providing the requesting user an option to pay for the application if the requesting user is not authorized to execute the application;

enabling execution of the application to the requesting user upon providing payment for the application; and

updating the locally stored user data segment with the application identifier.

38. A computer-readable medium having computer-executable instructions for authorizing execution of an application operable on a terminal within a network, the computer-executable instructions performing steps comprising:

attempting to execute the application by a user on the terminal;

examining a locally stored user data segment for an application identifier of the application, and enabling execution of the application if the application identifier is found in the locally stored user data segment;

examining a remotely stored user data segment for the application identifier if the application identifier is not found in the locally stored user data segment, and enabling execution of the application if the application identifier is found in the remotely stored user data segment; and

prohibiting the user from executing the application if the application identifier is not found in either the locally or remotely stored user data segment.

39. A system for enabling operation of an application on a terminal in a network, comprising:

means for linking an application identifier with user profile information unique to each user authorized to execute the application;

means for determining whether the application identifier has been linked with the user profile information of a requesting user attempting to execute the application from the terminal;

means for denying execution of the application to the requesting user if the application identifier has not been linked with the user profile information; and

means for enabling execution of the application to the requesting user if the application identifier has been linked with the user profile information.