Advice of charge for internet protocol multimedia subsystem services without utilizing an application server

• US 20070053330A1
• Filed: 08/17/2005
• Published: 03/08/2007
• Est. Priority Date: 08/17/2005
• Status: Active Grant

• Current Assignee: Cingular Wireless II LLC (AT&T, Inc.)
• Original Assignee: Cingular Wireless II LLC (AT&T, Inc.)
• Inventors: Tran, Nhan, Stafford, Matthew
• Granted Patent: US 7,711,351 B2
• Time in Patent Office: Days
• US Class Current: 370/338
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1414 in real-time
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

Advice of charge information is provided utilizing the session initiation protocol (SIP) in an Internet protocol multimedia subsystem without utilizing an application server. The advice of charge message is provided to a user via the serving call/session control function and the home subscription server. When a request for a service is received by the serving call/session control function, the state of a binary, Boolean flag associated with the originator of the request is analyzed. Depending upon the state of the flag, either the request is routed to its intended destination, or an advice of charge message is routed to originating user, advising the user of the charge for the requested service. If the user accepts the charge, the serving call/session control function transmits the request for routing to the intended destination, and the flag is toggled. If the user declines the charge, the call is ended.

Claims

1. A method for providing, in an Internet protocol multimedia subsystem (IMS) without utilizing an IMS application server (AS), notification of a charge for a service, said method comprising:

receiving, without utilizing an IMS AS, a request to access a service;

determining, without utilizing an IMS AS, a status in response to receiving said request;

in accordance with said status, without utilizing an IMS AS, performing one of;

providing notification of said charge for service; and

providing said request for routing to an intended destination.

2. A method in accordance with claim 1, said method further comprising:

subsequent said act of providing said notification, receiving acceptance of said charge;

and

providing said request for routing to an intended destination.

3. A method in accordance with claim 1, wherein said status is indicative of one of:

an originator of said request being a subscriber to said service;

prior to said act of receiving, said originator accepted said charge; and

said originator of said request not being a subscriber to said service.

4. A method in accordance with claim 3, further comprising:

performing said act of providing said notification if said status is indicative of said originator not being a subscriber to said service; and

performing said act of providing said request for routing if said status is indicative of one of;

said originator of said request being a subscriber to said service; and

said originator accepting said charge prior to said act of receiving.

5. A method in accordance with claim 1, wherein:

said status is indicative of a flag being set to one of true and false;

said act of providing said notification is performed if said flag is set to one of true and false; and

said act of providing said request for routing is performed if said flag is set to the other one of true and false.

6. A method in accordance with claim 5, further comprising:

subsequent to providing said notification, toggling said flag to an alternate state and performing said act of providing said request for routing, responsive to receipt of an indication that said charge is accepted.

7. A processor for providing, in an Internet protocol multimedia subsystem (IMS) without utilizing an IMS application server (AS), notification of a charge for a service, said processor comprising:

a first processing portion, not being an IMS AS, for;

receiving in a request to access a service;

requesting a status from a second processing portion;

receiving said status from said second processing portion;

in accordance with said status, performing one of;

providing notification of said charge for service; and

providing said request for said service for routing to an intended destination.

said second processing portion, not being an IMS AS, for;

storing said status;

receiving said request for status from said first processing portion; and

providing said status to said first processing portion.

8. A processor in accordance with claim 7, wherein said first processor functions as a session initiation protocol (SIP) proxy for an AS.

9. A processor in accordance with claim 7, wherein said status is indicative of one of:

an originator of said request for said service being a subscriber to said service;

said originator previously accepting said charge; and

said originator of said request for said service not being a subscriber to said service.

10. A processor in accordance with claim 7 wherein:

said first processing portion provides notification of said charge for said service if said status is indicative of an originator of said request for service not being a subscriber of said service.

said first procession portion provides said request for said service for routing if said status is indicative of one of;

said originator being a subscriber to said service; and

said originator accepting said charge.

11. A processor in accordance with claim 7, wherein said first processing portion comprises a serving call session control function (S-CSCF).

12. A processor in accordance with claim 7, wherein said second processing portion comprises a home subscription server (HSS).

13. A processor in accordance with claim 7, wherein said request for service originated from one of mobile telephone, a personal digital assistant (PDA), a hand held processor, an SIP phone, and a lap top computer.

14. A processor in accordance with claim 7, wherein:

said status is indicative of a flag being set to one of true and false;

said act of providing said notification is performed if said flag is set to one of true and false; and

said act of providing said request for routing is performed if said flag is set to the other one of true and false.

15. A processor in accordance with claim 14, wherein:

subsequent to providing said notification and responsive to receipt of an indication that said charge is accepted, said flag is toggled to an alternate state and said request is provided for routing.

16. A computer readable medium encoded with a computer program code for providing, in an Internet protocol multimedia subsystem (IMS) without utilizing an IMS application server (AS), notification of a charge for a service, said program code comprising:

a receive request code segment for receiving, without utilizing an IMS AS, a request to access a service;

a determine status code segment for determining, without utilizing an IMS AS, a status in response to receiving said request;

in accordance with said status, without utilizing an IMS AS, performing one of;

a provide notification code segment for providing notification of said charge for service; and

a routing code segment providing said request for routing to an intended destination.

17. A computer readable medium in accordance with claim 16, said program code further comprising:

a receive acceptance code segment for, subsequent said act of providing said notification, receiving acceptance of said charge; and

said routing code segment for providing said request for routing to an intended destination.

18. A computer readable medium in accordance with claim 16, wherein said status is indicative of one of:

an originator of said request being a subscriber to said service;

prior to said act of receiving, said originator accepted said charge; and

said originator of said request not being a subscriber to said service.

19. A computer readable medium in accordance with claim 18, wherein:

said provide notification code segment performs said act of providing said notification if said status is indicative of said originator not being a subscriber to said service; and

said routing code segment performs said act of providing said request for routing if said status is indicative of one of;

said originator of said request being a subscriber to said service; and

said originator accepting said charge prior to said act of receiving.

20. A computer readable medium in accordance with claim 16, wherein:

said status is indicative of a flag being set to one of true and false;

said act of providing said notification is performed if said flag is set to one of true and false; and

said act of providing said request for routing is performed if said flag is set to the other one of true and false.

21. A computer readable medium in accordance with claim 20, said program code further comprising:

a toggle code segment for, subsequent to providing said notification, toggling said flag to an alternate state and performing said act of providing said request for routing, responsive to receipt of an indication that said charge is accepted.