Prepaid access to internet protocol (IP) networks

• US 20020116338A1
• Filed: 02/22/2001
• Published: 08/22/2002
• Est. Priority Date: 02/22/2001
• Status: Abandoned Application

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Cobo, Miguel, Barna, John, Gonthier, Jean-Charles
• Application Number:
  US09/789,562
• Publication Number:
  US 20020116338A1
• Time in Patent Office: Days
• US Class Current: 705/52
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1467 involving prepayment
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/854 Available credit
• CPC Class Codes: H04M 15/88 Provision for limiting connection, or expenditure
• CPC Class Codes: H04M 17/00 Prepayment of wireline communication systems, wireless communication systems or telephone systems using a coded card to authorise calls from a telephone set H04M1/675
• CPC Class Codes: H04M 17/10 Account details or usage
• CPC Class Codes: H04M 2215/0116 Provision for limiting expenditure, e.g. limit on call expenses or account
• CPC Class Codes: H04M 2215/0152 General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/202 VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/204 UMTS; GPRS
• CPC Class Codes: H04M 2215/22 Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/8166 Available credit
• CPC Class Codes: H04M 7/0078 Security; Fraud detection; Fraud prevention
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

The invention relates to a solution for prepaid access to an Internet Protocol (IP) network, and particularly a third generation (3G) network. A user has a prepaid account configured in his terminal and in a Prepaid Server (PPS). When the user wants to access the network, an access server requests that the PPS authenticates the terminal and, if accepted, responds with a message informing the access server of how much the terminal can utilise network resources before a re-authentication is necessary. When this limit is met, the access server re-requests authentication until the user disconnects or the account is exhausted, in which case the user is denied further access.

Claims

1. A system for providing prepaid access for a terminal using a prepaid account to an Internet protocol (IP) network, the system comprising an access server, a prepaid server (PPS), and at least one connection to the IP network, wherein the PPS stores account information associated with the terminal, and wherein:

the PPS is for;

receiving an access request from the access server;

authenticating the account; and

if the account was successfully authenticated

sending to the access server an access accept message comprising at least one limit to the account'"'"'s allowed resource usage; and

the access server is for;

receiving an access accept message from the PPS;

allowing the terminal to access to the IP network; and

counting the account'"'"'s resource usage, and when the usage reaches the limit;

interrupting the terminal'"'"'s network access; and

sending an access request to the PPS.

2. The system according to claim 1, wherein the access server further is for, previous to receiving an access accept message from the PPS, sending a first access request to the PPS, the first access request comprising the account identity of the prepaid account used by the terminal.

3. The system according to claim 2, wherein the access server further is for receiving a connection request from the terminal.

4. The system according to claim 3, wherein the connection request comprises the account identity of the prepaid account used by the terminal.

5. The system according to claim 1, wherein the access server comprises a protocol client and the PPS comprises a corresponding protocol server.

6. The system according to claim 5, wherein the messages between the access server and the PPS are sent between the protocol client and the protocol server.

7. The system according to claim 5, wherein the protocol used by the protocol client and the protocol server adheres to a client-server model.

8. The system according to claim 7, wherein the protocol is Remote Authentication Dial In User Service (RADIUS).

9. The system according to claim 1, wherein the PPS sends an access reject message to the access server in case the account was not authenticated.

10. The system according to claim 9, wherein the access server disconnects the terminal upon reception of the access reject message.

11. The system according to claim 1 further comprising an Authentication, Authorisation and Accounting (AAA) framework through which the PPS and the access server communicate.

12. The system according to claim 1, wherein the access server sends a start accounting message to the PPS upon reception of a first access accept message for a certain session for a certain account.

13. The system according to claim 1, wherein the access server sends at least one accounting interim message to the PPS after having received an access accept message and before sending an access request message.

14. The system according to claim 1, wherein the PPS is further for verifying that the access server supports the prepaid solution provided by the system.

16. The method according to claim 15, wherein step of sending an access accept message is preceded by the step of authenticating the account and the step of sending an access accept message is performed only if the account is successfully authenticated.

17. The method according to claim 16, wherein the step of authenticating the account is preceded by the step of sending a first access request from the access server to the PPS, the first access request comprising the account identity of the prepaid account used by the terminal.

18. The method according to claim 17, wherein the step of sending a first access request from the access server to the PPS is preceded by the steps of:

sending a connection request from the terminal; and

receiving the connection request at the access server.

19. The method according to claim 18, wherein the connection request comprises the account identity of the prepaid account used by the terminal.

20. The method according to claim 15, wherein the access server comprises a protocol client and the PPS comprises a corresponding protocol server.

21. The method according to claim 20, wherein the protocol used by the protocol server and the protocol client adheres to a client-server model.

22. The method according to claim 21, wherein the protocol is Remote Authentication Dial In User Service (RADIUS).

23. The method according to claim 16, wherein the PPS sends an access reject message to the access server in case the account did not pass the authentication.

24. The method according to claim 23, wherein the access server disconnects the terminal upon reception of the access reject message.

25. The method according to claim 15, wherein the network further comprises an Authentication, Authorisation and Accounting (AAA) framework through which the PPS and the access server communicate.

26. The method according to claim 15, wherein the access server sends a start accounting message to the PPS upon reception of a first access accept message for a certain session for a certain account.

27. The method according to claim 15, wherein the access server sends at least one accounting interim message to the PPS after having received an access accept message and before sending an access request message.

28. The method according to claim 16, wherein the step of authenticating the account further comprises the step of verifying that the access server supports the prepaid solution provided by the method.

30. The access server according to claim 29, wherein the first communication unit further is for, previous to receiving an access accept message from the PPS, sending a first access request to the PPS, the first access request comprising the account identity of the prepaid account used by the terminal.

31. The access server according to claim 29, further comprising a second communication unit for receiving a connection request from the terminal.

32. The access server according to claim 31, wherein the connection request comprises the account identity of the prepaid account used by the terminal.

33. The access server according to claim 29, wherein the first communication unit is a protocol client corresponding to a protocol server in the PPS.

34. The access server according to claim 33, wherein the protocol used by the protocol client and the protocol server adheres to a client-server model.

35. The access server according to claim 34, wherein the protocol is Remote Authentication Dial In User Service (RADIUS).

36. The access server according to claim 29, wherein the network further comprises an Authentication, Authorisation and Accounting (AAA) framework and wherein the messages sent between the first communication unit and the PPS are sent through the AAA framework.

37. The access server according to claim 29, wherein the first communication unit further is for sending a start accounting message to the PPS upon reception of a first access accept message for a certain session for a certain account.

38. The access server according to claim 29, wherein the first communication unit further is for sending at least one accounting interim message to the PPS after having received an access accept message and before sending an access request message.

40. The prepaid server (PPS) according to claim 39, wherein a first access request message associated with a terminal comprises the account identity of the prepaid account used by the terminal.

41. The prepaid server (PPS) according to claim 39, wherein the communication unit is a protocol server corresponding to a protocol client in the access server.

42. The prepaid server (PPS) according to claim 41, wherein the protocol used by the protocol client and the protocol server adheres to a client-server model.

43. The prepaid server (PPS) according to claim 42, wherein the protocol is Remote Authentication Dial In User Service (RADIUS).

44. The prepaid server (PPS) according to claim 39, wherein the communication unit further is for sending an access reject message to the access server in case the account was not successfully authenticated.

45. The prepaid server (PPS) according to claim 39, wherein the memory further is for storing a list of access servers that support the prepaid solution offered by the PPS, and the authentication unit further is for verifying that the access server that sent the access request is on the list of access servers.

46. The prepaid server (PPS) according to claim 39, wherein the communication unit further is for receiving from the access server information about the account'"'"'s resource usage.

47. The prepaid server (PPS) according to claim 40, wherein the authentication unit further is for updating account information stored in the memory upon reception of the information about the account'"'"'s resource usage.

15. In a network, a method for providing prepaid access for a terminal using a prepaid account to an Internet protocol (IP) network, the network comprising an access server, a prepaid server (PPS), and at least one connection to the IP network, the PPS storing account information associated with the terminal, the method comprising the steps of:

sending from the PPS to the access server an access accept message comprising at least one limit to the account'"'"'s allowed resource usage; and

upon reception of the access accept message by the access server;

allowing the terminal to access the IP network; and

counting the account'"'"'s resource usage; and

when the usage reaches the limit;

interrupting the terminal'"'"'s network access; and

sending an access request to the PPS.

29. An access server in a network for providing prepaid access for a terminal using a prepaid account to an Internet protocol (IP) network, the network further comprising a prepaid server (PPS), and at least one connection to the IP network, wherein the PPS stores account information associated with the terminal, and wherein the access server comprises:

a first communication unit for;

receiving from the PPS an access accept message comprising at least one limit to the account'"'"'s allowed resource usage; and

sending an access request to the PPS; and

a network access control unit for;

allowing the terminal to access to the IP network;

counting the account'"'"'s resource usage; and

when the usage reaches the at least one limit;

interrupting the terminal'"'"'s network access.

39. A prepaid server (PPS) in a network for providing prepaid access to an Internet protocol (IP) network for a terminal using a prepaid account, the network further comprising an access server, and at least one connection to the IP network, and wherein the PPS comprises:

a memory for storing account information associated with the terminal;

an authentication unit for authenticating the account; and

a communication unit for;

receiving an access request from the access server; and

if the account was successfully authenticated, sending to the access server an access accept message comprising at least one limit to the account'"'"'s allowed resource usage.