Policy control and billing support for call transfer in a session initiation protocol (SIP) network

• US 7,739,196 B2
• Filed: 06/19/2006
• Issued: 06/15/2010
• Est. Priority Date: 03/12/2002
• Status: Active Grant

• Current Assignee: OL Security LLC (Intellectual Ventures LLC)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Gallant, John Kenneth, Gregorat, Mariafranca, McMurry, Kathleen A.
• Primary Examiner(s): Hewitt, II; Calvin L
• Assistant Examiner(s): Nigh; James D
• Application Number:
  US11/425,050
• Publication Number:
  US 20060239253A1
• Time in Patent Office: 1,457 Days
• Field of Search: 705 50- 52
• US Class Current: 705/52
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/47 Fraud detection or prevention means
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/63 based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/67 Transmitting arrangements for sending billing related information
• CPC Class Codes: H04M 15/70 Administration or customization aspects; Counter-checking correct charges
• CPC Class Codes: H04M 15/73 Validating charges
• CPC Class Codes: H04M 15/8292 Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2215/0148 Fraud detection or prevention means
• CPC Class Codes: H04M 2215/202 VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/48 Sending information over a non-traffic network channel or another connection than the one actually used, e.g. signalling, D-channel, data and voice
• CPC Class Codes: H04M 2215/70 Administration aspects, modify settings or limits or counter-check correct charges
• CPC Class Codes: H04M 2215/7072 Validate charges
• CPC Class Codes: H04M 3/2281 Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
• CPC Class Codes: H04M 3/54 Arrangements for diverting calls for one subscriber to another predetermined subscriber based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; to voice mail H04M3/53308

Abstract

A system includes a database configured to store account information relating to users of a telecommunications network. Additionally, a session initiation protocol (SIP) server receives first messages initiating call transfers. The server appends billing information and a digital signature to the first message based on account information of one of the users stored in the database. The digital signature provides for authentication of the call transfers.

Claims

1. A method comprising:

receiving, by a first session initiation protocol (SIP) server, a first SIP message based on a first party device initiating a call transfer relating to a second party and a third party;

retrieving first party call policy information and third party call policy information from a call policy information database;

verifying, by the first SIP server using the first party call policy information and the third party call policy information, that the first party is authorized to initiate the call transfer to the third party;

creating, by the first SIP server and based on the verifying, a digital signature identifying the first SIP server;

generating, by the first SIP server and using account information in the stored profile for the first party, billing information related to the call transfer;

appending, by the first SIP server, the billing information and the digital signature to the first SIP message;

authenticating, by a processor, the first SIP server based on the digital signature appended to the first SIP message; and

completing, by the processor, the call transfer based on the authenticating the first SIP server, and determining whether to bill the first party, with respect to the completed call transfer, based on the billing information appended to the first SIP message.

2. The method of claim 1, where authenticating the first SIP server includes:

receiving a second SIP message, including the digital signature, at a second SIP server; and

authenticating the first SIP server at the second SIP server.

3. The method of claim 2, where the first and second SIP servers are a portion of a same computing system.

4. The method of claim 1, where the first SIP message is a SIP REFER message.

5. The method of claim 1, further comprising:

appending a timestamp to the first SIP message.

6. A method for effecting a call transfer in accordance with session initiation protocol (SIP), the method comprising:

receiving a first SIP message at a SIP server, the first SIP message being generated by a first party and indicating that the first party is requesting a call be initiated between a second party and a third party;

accessing, by the SIP server, first call policy information and account information in a stored profile for the first party and second call policy information in a stored profile for the third party, associated with the call;

determining, by the SIP server and based on the first call policy information and the second call policy information, that the first party is allowed to initiate the call transfer, where, when a conflict exists between the first call policy and the second call policy, the first call policy overrides the second call policy; and

determining, by the SIP server and based on the account information, whether to bill the first party for the call between the second and third party.

7. The method of claim 6, where accessing the account information includes:

accessing account information that indicates how the first party is to be billed for the call.

8. The method of claim 6, further comprising:

appending at least one of billing information, a timestamp, or a digital signature to the first SIP message based on the accessed information.

9. The method of claim 8, where the billing information and the timestamp are encrypted.

10. The method of claim 6, further comprising:

generating a second SIP message by the second party and addressed to the third party, the second SIP message inviting the third party to join a call with the second party and including the first and second call policy information.

11. The method of claim 10, further comprising:

authenticating the call transfer based on the first and second call policy information in the second SIP message; and

determining to bill the first party for the call when the authentication is successful.

12. A system comprising:

a computer comprising;

a first processor, and

a first memory, connected to the first processor, including a database comprising profile information relating to a plurality of users of a telecommunications network, where the profile information for each of the plurality of users includes call policy information and account information; and

a session information protocol (SIP) server comprising;

a second processor, and

a second memory, connected to the second processor, storing executable instructions that when executed by the processor, cause the second processor to perform the steps of;

receiving a first SIP message based on a first party device initiating a call transfer relating to a second party and a third party,

retrieving first party call policy information and third party call policy information from the database,

verifying, using the first party call policy information and the third party call policy information, that the first user is authorized to initiate the call transfer to the third user,

creating, based on the verifying, a digital signature identifying the SIP server;

generating, using the account information in the profile for the first user, billing information related to the call transfer,

appending the billing information and the digital signature to the first SIP message, the digital signature providing for authentication of the call transfer,

authenticating the SIP server based on the digital signature appended to the first SIP message, and

completing the call transfer based on the authenticating the SIP server, and determining whether to bill the first party, with respect to the completed call transfer, based on the billing information appended to the first SIP message.

13. The system of claim 12, further comprising:

a location service database configured to store location information relating to the users of the telecommunications network.

14. The system of claim 13, where the SIP server is further to query the location service database for an address of the third user and to forward the first SIP message to the third user at the address retrieved from the location service database.

15. The system of claim 14, further comprising:

a first end-user station associated with the first user to generate the first SIP message.

16. The system of claim 15, further comprising:

a second end-user station associated with the second user to receive the first SIP message from the SIP server and to generate a second SIP message inviting a third end-user station associated with the third user to join a call, the second SIP message including the billing information and the digital signature, and the third end-user station being identified by the first SIP message.

17. The system of claim 16, further comprising:

a second SIP server to receive the second SIP message, authenticate the billing information based on the digital signature, and determine that the first user associated with the first end-user station should be billed for the call when the billing information is successfully authenticated.

18. The system of claim 12, where the SIP server appends the billing information to the first SIP message, indicating how the first user is to billed for the call based on the account information in the profile for the first user.

19. A system comprising:

means for receiving a first session initiation protocol (SIP) message from a first party device initiating a call transfer relating to a second party and a third party;

means for retrieving first party call policy information and third party call policy information from a call policy information database;

means for verifying, using the first call policy information and the third call policy information, that the first party is authorized to initiate the call transfer to the third party;

means for creating, based on the verifying, a digital signature identifying a SIP server;

means for generating, using account information in the stored profile for the first party, billing information related to the call transfer;

means for appending the billing information and a digital signature to the first SIP message;

means for authenticating the SIP server based on the digital signature appended to the first SIP message; and

means for receiving a second SIP message initiating a call related to the call transfer, the second SIP message including the digital signature, the means for receiving the second SIP message additionally generating, based on the billing information appended to the first SIP message, an indication how the first party is to be billed for the call when the digital signature appended to the first SIP message indicates that the second SIP message is authentic.

20. The system of claim 19, where the means for appending further appends a timestamp to the first SIP message, and the means for receiving the second SIP message additionally authenticates the second SIP message based on the timestamp.

21. The system of claim 19, where, when a conflict exists between the policy information in the stored profile for the first party and the policy information in the stored profile for the third party, the means for receiving the second SIP message resolves the conflict in favor of the policy information in the stored profile for the first party.