Method and corresponding equipment enabling billing for use of applications hosted by a wireless terminal

• US 20040267645A1
• Filed: 06/24/2003
• Published: 12/30/2004
• Est. Priority Date: 06/24/2003
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Pollari, Pekka
• Application Number:
  US10/606,271
• Publication Number:
  US 20040267645A1
• Time in Patent Office: Days
• US Class Current: 705/34
• 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 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: G06Q 20/123 Shopping for digital content
• CPC Class Codes: G06Q 20/1235 with control of digital rights management [DRM]
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/145 Payments according to the detected use or quantity
• CPC Class Codes: G06Q 20/16 Payments settled via telecommunication systems
• CPC Class Codes: G06Q 30/04 Billing or invoicing

Abstract

A wireless terminal (10) and an operator network (18) adapted to enable billing a user of the wireless terminal (10) for use of an application (11) hosted by the wireless terminal (10). The application (11) is implemented so as to interface with a business relationship manager (BRM) (12) module also hosted by the terminal (10) via a BRM application programming interface (API) included in the BRM (12), and the BRM (12) ensures that the application (11) is not used by the user unless it is registered with the operator network (18) so that the user is billed for use of the application according to one or another lease/buy plan elected by the user. The BRM (12) also enables registration, de-registration, and even charging for use of network resources by the application (11).

Claims

1. A method enabling billing a user for use of an application (11) hosted by a wireless terminal (10) subscribed to an operator network (18), characterized by:

a step (25b 25c) in which, in response to an indication by the user that the application (11) is to be executed, a business relationship manager (BRM) (12) also hosted by the wireless terminal (10) refers to one or more data stores (12a 13a) hosting information on user registration of applications to determine whether the user has registered the application (11); and

a step (27) in which, if the BRM (12) determines that the user has registered the application (11), the BRM (12) then signals to the application (11) that the user has registered the application (11).

18. A computer program product comprising:

a computer readable storage structure embodying computer program code thereon for execution by a computer processor in a wireless terminal (10), said computer program product for enabling billing a user for use of an application (11) hosted by the wireless terminal (10) subscribed to an operator network (18), said computer program code characterized in that it includes instructions for performing the steps of the method of claim 1.

2. A method as in 1, further characterized by:

a step (26) in which, before a first use of the application (11), the user registers the application (11) with a user information server (13) via the BRM (12).

3. A method as in 2, wherein signalling between the BRM and the user information server is according to SIP (session initiation protocol) or XML (extensible markup language) over HTTP (hypertext transfer protocol) or over HTTPS (secure HTTP).

4. A method as in 2, further characterized by:

a step (25f) in which, before registering for use of the application (11), the user elects in a dialogue with the BRM (12) a lease/buy plan by which the user is billed for use of the application (11).

5. A method as in 1, wherein to determine whether the user has registered the application (11), the BRM (12) refers to a data store (12a) hosted by the wireless terminal (10).

6. A method as in 1, wherein to determine whether the user has registered the application (11), the BRM (12) refers to a data store (13a) maintained by a user information server (13) of the operator network (18).

7. A method as in 1, further characterized by:

a step (33) in which, in response to a prompt by the user to de-register the application (11), the BRM (12) signals a de-register message to a user information server (13) that the application is to be de-registered for the user; and

a step (34) in which the user information server (13) acknowledges the de-register message and de-registers the application (11) for the user.

8. A method as in 1, wherein the application (11) is assigned an identifier common to all copies of the application (11) and used as an identifier for the application (11) in the data stores (12a 13a) indicating whether the user has registered the application (11).

9. A method as in 1, wherein the user is able to elect various plans for paying for use of the application.

10. A method as in 9, wherein the various plans include a plan in which the user is billed monthly for use of the application.

11. A method as in 1, wherein the application consumes network resources and the method is further characterized by:

a step (53) in which with each request for a network service, the BRM (12) appends to the request an identifier indicating the user and an identifier indicating the application (11); and

a step (57) in which a support node (15) of the operator network (18) counts packets bearing the identifier indicating the user and the identifier indicating the application.

12. A method as in 11, wherein the support node (15) is a gateway GPRS (general packet radio service) support node (GGSN).

13. A method as in 1, wherein the application (11) is provided to the operator network (18) by an application provider, and operator network (18) bills the user for use of the application (11) and compensates the application provider in a way predetermined to be commensurate with the use of the application (11) by the user.

14. A wireless terminal (10) including a business relationship manager (BRM) (12) component for enabling billing a user for use of an application (11) hosted by the wireless terminal (10) subscribed to an operator network (18), the wireless terminal (10) characterized in that the BRM (12) comprises:

means (25b 25c), responsive to an indication by the user that the application (11) is to be executed, for referring to at least either a local data store (12a) or a data store (13a) hosted by the operator network (18) to determine whether the user has registered the application (11); and

means (27) for signaling to the application (11) that the user has registered the application (11) in case the BRM (12) determines that the user has registered the application (11).

15. A wireless terminal (10) for use by a user, characterized by:

an application (11), responsive to a signal to begin execution, for providing a signal to confirm registration, and further responsive to a signal indicating registration is in place;

a business relationship manager (BRM) (12) having a BRM application programming interface (API), responsive to the signal to confirm registration, for referring to at least one data store (12a 13a) to determine whether the user has registered the application (11); and

, if the BRM (12) determines that the user has registered the application (11), for signalling to the application (11) that registration is in place.

16. A system enabling billing a user of a wireless terminal (10) for use of an application (11) hosted by the terminal (10), comprising the wireless terminal (10) and an operator network (18) to which the user of the wireless terminal (10) is subscribed, the operator network (18) including a user information server (13), characterized in that:

a BRM (12) included in the wireless terminal (10) is responsive to a signal from the application (11) to confirm registration and signals a request to the operator network (18) to determine whether the user is registered to use the application (11); and

the user information server (13), in response to the request to determine whether the user is registered to use the application (11), refers to a data store (13a) hosted by the operator network (18) to determine whether the user is registered to use the application (11).

17. A system as in claim 16, further comprising a gateway GPRS (general packet radio service) support node (GGSN) (15), and the system is further characterized in that:

in case of an application using network resources, for each request for a network service, the BRM (12) appends to the request a user identifier and an application identifier, and the GGSN, by monitoring packets received from users, counts packets bearing the user identifier and application identifier.