Patent Grant
8681781
The invention relates to video, voice, data communications and application services. More particularly, the invention relates to a system and method for securely authorizing VoIP interconnection access control between anonymous peers of VoIP networks.
In the traditional telephone carrier operating model, calls between Local Exchange Carriers (LECs), or Retail Service Providers (RSPs) are transported by an Inter-Exchange Carrier (IXC). The RSP provides retail telephone services to its end user subscribers on its network. When a RSP end user subscriber calls a telephone number which is not in the RSP's network, the RSP will switch that call to an IXC that will transport the call to the RSP serving the called number to complete the telephone call to the receiving party. The business model for this call scenario starts with the source RSP that switches the call to the IXC. The RSP pays the IXC a fee to transport the call to the destination RSP. The DCC transports the call to the destination RSP which completes the call to the receiving party.
The DCC pays the destination RSP a fee to complete the telephone call. An important operating value added by the DCC is route discovery. The IXC manages a central routing table that enables routing among a multitude of RSPs to any telephone number on the global Public Switched Network (PSTN). This action simplifies operations for the RSP operator whom needs to route to only one IXC to obtain termination to any telephone number in the PSTN. In this document, the operating model described above is referred to as the IXC operating model.
This common telephony business model for the operating model described above is referred to as the Calling Party Pays model. The end user of the source RSP pays a retail service fee to the source RSP. The source RSP pays the IXC a fee to locate and transmit the call to the destination RSP. The IXC pays the destination RSP a termination fee to complete the call. An important aspect of this business model is the role of the IXC as the central routing and billing intermediary among many RSPs. Source and destination RSPs do not have commercial interconnect agreements with one another.
An important commercial value added by the IXC is the clearing of calls (routing and access control) between RSPs, accounting of interconnected calls and settlement of interconnect fees to ensure the destination RSP receives a share of the revenue compensation as expected in the Calling Party Pays business model. Each RSP has a single bilateral interconnect agreement with the IXC which eliminates the costly need for commercial bilateral agreements with every other RSP.
Relative to the conventional IXCs, a new communications model has evolved: The increasing use of Voice over IP (VoIP) communications has made possible a new operating model referred to as the Peer To Peer operating model. The Peer To Peer operating model differs from the IXC operating model because end to end routing and signaling for telephone calls is achieved directly from the source RSP (peer) to the destination RSP (peer) without the need for a central intermediary such as an IXC. Two examples of the Peer To Peer operating model are DUNDi and ENUM. DUNDi (Distributed Universal Number Discovery, www.dundi.com) enables source networks (peers) to discover routes to destination networks (peers) without the need for a central routing directory or intermediary signaling point.
ENUM is the Internet Engineering Task Force (www.itef.org) protocol (RFC 2916) which defines how a source peer may resolve telephone numbers into IP addresses in order to route and signal a VoIP call directly to the destination network (peer). In other words, ENUM is a standard adopted by the Internet Engineering Task Force (IETF) that uses the domain name system (DNS) to map telephone numbers to Web addresses or uniform resource locators (URL). The goal of the ENUM standard is to provide a single number to replace the multiple numbers and addresses for an individual's home phone, business phone, fax, cell phone, and e-mail.
However, while IP technology has enabled the Peer To Peer operating model, there is no scalable mechanism to implement the Calling Party Pays business model with a Peer To Peer operating model. With the Peer To Peer operating model, the Calling Party Pays business model can only be implemented if every RSP (peer) has a bilateral commercial interconnect agreement with every other RSP (peer). Bilateral agreements among RSPs is not practical because the number of commercial peering agreements for all RSPs increases by the square of the number of RSPs (peers) [n*(n−1)/2 where n=number of peers], making large scale peer to peer networks using the Calling Party Pays business model virtually impossible.
Referring now to
a represents a call scenario where the calling party 120 calls a receiving party 130. The call from the calling party 120 is initiated with a call setup message 400, such as a SIP Invite message to the Call Control Point 110. The Call Control Point determines if, and how, the call should be routed to the receiving party 130. To complete the call to the receiving party 130, the Call Control Point 110, sends a message 410 to the receiving party 130 to complete the call between the calling and called parties. When the RSP provides service to both the calling and called parties, the call can be completed within the RSP's network 100 without the use of facilities provided by another VoIP service provider. In
Referring now to
Completion of the call scenario in
The second function required for peering is access permission. The source network 100 must be permitted to access the destination network 200 to complete the call. Access permission between two IP networks is commonly controlled by the use of an access list at the destination network. The destination network 200 will only accept IP communications from IP addresses in its access control list. Other access control techniques are based on the inclusion of a password or digital signature in the call setup message 420 between the source and destination networks. If the destination network 200 can validate that the password or digital signature can only be from a trusted source, the call or peering transaction can be accepted without the source IP address being included in an access control list.
There are several limitations with this conventional technology used for VoIP interconnection or peering. First, the technique of bilateral peering agreements is difficult to implement when a large number of bilateral peering agreements must be maintained. Real time route discovery techniques such as ENUM or DUNDi provide scalable solutions for inter-peer routing but do not provide scalable mechanisms for inter-peer access control or accounting. Accordingly, there is a need in the art for a scalable technique for inter-peer access control and accounting that is independent of the route discovery mechanism. A further need exists for a reliable scalable mechanism for implementing the Calling Party Pays business model with a Peer to Peer operating model:
A need exists in the art to solve this scalability problem for the Calling Party Pays business model in a Peer To Peer operating model. A need also exists in the art for eliminating or substantially reducing the number of bilateral agreements among RSPs.
According to one exemplary aspect of the technology, RSPs using VoIP may establish a single bilateral commercial agreement with a trusted third party or clearinghouse that can authorize interconnection, on a call by call basis, among source and destination RSPs. These source and destination RSPs will typically not have bilateral commercial interconnect agreements. The invention can comprise a trusted settlement clearinghouse that ensures interconnect data such as calling number, caller ID, interconnect rates and other critical data are valid and then executes any resulting financial transactions between the source and destination RSPs.
Exemplary aspects of the invention will refer to interconnections among RSPs providing VoIP telephony services. However, one of ordinary skill in the art will recognize that this invention can be used for peering access control and accounting between IP networks on a session by session basis for many applications in addition to VoIP, such as video sessions, data transfers with a guaranteed quality of service, bandwidth reservation, conferencing of three or more telephony or video sessions, content brokering, short message services, gaming and instant messaging.
A settlement clearinghouse, according to one exemplary aspect of the invention, can be referred to more generally as a Peering Authority, and may be used for peering access control and accounting of other IP applications in addition to VoIP. A settlement clearinghouse or peering authority can comprise a common trusted third party for all peers. The settlement clearinghouse can exchange digital certificates with each peer and use asymmetric key cryptography to establish and manage a trusted, bilateral relationship with each peer. These trusted bilateral relationships between each peer and the settlement clearinghouse can enable the settlement clearinghouse to securely authorize VoIP interconnection access control between anonymous peers on a call by call basis. In addition, the settlement clearinghouse can also securely collect accounting information for each call interconnected between VoIP networks. This accounting information may then be used for the tracking or billing of interconnected VoIP calls and execution of inter-network financial settlements.
According to another exemplary aspect of the invention, a source IP network may specify routing and all terms of an individual peering session with the destination network of its choice. According to other exemplary aspects of the technology, the inventive system and method describes how a trusted third party clearinghouse, or peering authority, can provide a centralized and scalable for solution for authorizing and accounting for inter-network peering sessions among known and anonymous peers. Exemplary aspects of the inventive system also include the discrete elements that form each of the individual peering authorization request messages, peering authorization response messages, and the peering authorization tokens. The discrete elements of the messages and authorization tokens are described in further detail below.
According to a further exemplary aspect, the inventive system comprises a technique that can decouple IP peering access control and accounting from routing. The inventive system illustrates how a source IP peer can submit a peering request to a trusted Peering Authority for access authorization to a known destination peer. Unlike conventional routing requests that are used by source networks to find the route to a destination, the peering request can comprise routing and all commercial terms (price, type of service, quality of service) for the proposed peering session. The role of the Peering Authority is to authorize and account for the peering transaction between the source and destination peers which have no trusted or commercial relationship.
a is a functional block diagram that illustrates a conventional VoIP call within a RSP's network.
b is a functional block diagram illustrating a conventional VoIP call that requires inter-IP network peering.
a is a functional block diagram illustrating an exemplary call scenario according to one exemplary embodiment of the invention.
b is a functional block diagram illustrating how call detail records are collected by a settlement clearinghouse for interconnect accounting and settlement billing according to one exemplary embodiment of the invention.
a-3d are logic flow diagrams illustrating a process of how a clearinghouse or peering authority authorizes and tracks accounting information for a VoIP call interconnected between two IP networks according to one exemplary embodiment of the invention.
a is a functional block diagram illustrating an inter-IP network peering scenario that includes a peering authorization request according to an exemplary embodiment of the invention.
b is a functional block diagram illustrating an exemplary peering authorization response message according to one exemplary embodiment of the invention.
c is a functional block diagram illustrating an exemplary call setup message, with peering authorization token, between peers according to one exemplary embodiment of the invention.
d is a functional block diagram illustrating exemplary peering accounting messages according to one exemplary embodiment of the invention.
A settlement clearinghouse or peering authority can comprise a common trusted third party for all peers of VoIP networks. The settlement clearinghouse can exchange digital certificates with each peer and use asymmetric key cryptography to establish and manage a trusted, bilateral relationship with each peer. These trusted bilateral relationships between each peer and the settlement clearinghouse can enable the settlement clearinghouse to securely authorize VoIP interconnection access control between anonymous peers of VoIP networks on a call by call basis. In addition, the settlement clearinghouse can also securely collect accounting information for each call interconnected between VoIP networks. This accounting information may then be used for the tracking or billing of interconnected VoIP calls and execution of inter-network financial settlements.
Referring now to the drawings, in which like numerals represent like elements throughout the several Figures, aspects of the invention and the illustrative operating environment will be described.
An exemplary call scenario can begin with a calling party 120 who calls a telephone number 17036054283 as illustrated in
This interconnect routing and rate information may have been pre-configured based on a bilateral agreement between the source 100 and destination networks 200 or may have been discovered in real time using some other mechanism. However, before sending call setup message 440, the source Call Control Point 110 sends an interconnect authorization request message 310 to the Settlement Clearinghouse 300. One of ordinary skill in the art of IP communications recognizes that messages to and from the Settlement Clearinghouse 300 may be encrypted to ensure the message contents are secure.
The Clearinghouse 300 may operate in a networked environment using logical connections to one or more other remote computers. The Clearinghouse 300 and Call Control Points 110, 210 can comprise computers such as a personal computer, a server, a router, a network PC, a peer device, or a common network node. The logical connections depicted in
The Clearinghouse 300 and Call Control Points 110, 210 illustrated in
Moreover, those skilled in the art will appreciate that the present invention may be implemented in other computer system configurations, including other hand-held devices besides hand-held computers, multiprocessor systems, microprocessor based or programmable consumer electronics, networked personal computers, minicomputers, mainframe computers, and the like.
The invention may be practiced in a distributed computing environment as illustrated in
The illustrated telephones 120, 130, 220, and 230 can comprise any general purpose computer capable of running software applications. The telephones 120, 130, 220, and 230 can be portable for mobile applications and they may be coupled to the respective networks 100, 200 though wired or wireless links. Typical wireless links include a radio frequency type in which the telephones 120, 130, 220, and 230 can communicate to the respective networks 100, 200 using radio frequency (RF) electromagnetic waves. Other wireless links that are not beyond the scope of the invention can include, but are not limited to, magnetic, optical, acoustic, and other similar wireless types of links.
Referring again to
To implement the Calling Party Pays business model, a positive interconnect rate indicates that the Source RSP Network 100 will pay the Destination RSP Network 200 to complete the call to the receiving party. The Settlement Clearinghouse 300, acting as the trusted third party between the Source RSP Network 100 and the Destination RSP Network 200 will approve or reject the interconnect authorization request message 310, based on the interconnect policies enforced by the Settlement Clearinghouse 300.
The Settlement Clearinghouse 300 responds to an interconnect authorization request message 310 by sending an authorization response message 315 back to the source Call Control Point 110 indicating that the authorization request was approved or rejected. The interconnect authorization response message 315 may also be referred to more generally as the peering authorization response and may be used for other IP applications in addition to VoIP. If the interconnect authorization request message 310 is approved by the Settlement Clearinghouse 300, the interconnect authorization response message 315 will comprise an interconnect authorization token that is returned to the Source RSP Network 100. The interconnect authorization token will also be referred to more generally as the peering authorization token and may be used for other applications in addition to VoIP.
The Settlement Clearinghouse 300 will typically sign the interconnect authorization token with its digital signature to ensure non-repudiation of the authorization token and to guarantee that the Settlement Clearinghouse 300 is party to the interconnection or peering transaction between the Source RSP Network 100 and the Destination RSP Network 200.
Another valuable service which may be provided by the Settlement Clearinghouse 300 is authentication and verification of the name and identification of either, or both, of the calling party 120 and the Source RSP Network 100. This function is especially useful for the Destination RSP Network 200 and receiving party 230 when a call is received from an unknown source network or anonymous peer. If the name and identification of either, or both, of the calling party 120 and source network 100 have been verified by the Settlement Clearinghouse 300 and are included in the signed authorization token conveyed in the interconnect call setup message 440, the destination network 200 and receiving party 230 may have some assurance that the name and identification information is legitimate.
When the source Call Control Point 110 receives interconnect authorization approval in the response 315 from the Settlement Clearinghouse 300, it can extract the interconnect authorization token from the response 315 and insert the authorization token in the call setup message 440 to the Call Control Point 210 of the Destination RSP Network 200. The destination Call Control Point 210 reviews the interconnect authorization token contained in the call setup message 440 to determine if it is valid.
Determining if the interconnect authorization token valid can be accomplished by the Call Control Point 210 validating the digital signature of the signed authorization token. If the interconnect authorization token has been signed by a trusted third party, such as by the Settlement Clearinghouse 300 who may have a bilateral commercial interconnect agreement with Call Control Point 210, then the token is valid and the call will be accepted, even if the call originates from an unknown IP address or anonymous peer. The token is deemed valid because of the relationship between the Settlement Clearinghouse 300 and Call Control Point 210.
To implement the Calling Party Pays business model, the signed authorization token in the call setup message 440 will include the interconnect rate required by the Destination RSP Network 200. The signed token with the interconnect rate, provides the Destination RSP Network 200 with a document that cannot be repudiated or rejected by the Settlement Clearinghouse 300. The interconnect authorization token contained in the setup message 440 is evidence that the Settlement Clearinghouse approved the interconnection between the source and destination networks at the specified rate.
b illustrates how call detail records are collected by the Settlement Clearinghouse 300 for interconnect settlement billing. When the call between the calling party 120 and receiving party 230 ends, the source Call Control Point 110 sends a call detail record 320 to the Settlement Clearinghouse 300 and the destination Call Control Point 210 also sends a call detail record 330 to the Settlement Clearinghouse 300. The call detail records 320 and 330 may include the interconnect rate approved by the Settlement Clearinghouse 300 in the interconnect authorization token.
One of ordinary skill in the art of IP communications will recognize that the technique described above for inter-IP network access control and accounting for VoIP applications can also be applied generally for many other IP applications that require the use or facilities of multiple networks. For example, exchanging video programs over the IP network using the described inter-IP network access control is not beyond the scope of the invention.
Exemplary Process for Securely Authorizing VoIP Interconnections Between Anonymous Peers
The processes and operations of the inventive system described below with respect to all of the logic flow diagrams may include the manipulation of signals by a processor and the maintenance of these signals within data structures resident in one or more memory storage devices. For the purposes of this discussion, a process can be generally conceived to be a sequence of computer-executed steps leading to a desired result.
These steps usually require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, or otherwise manipulated. It is convention for those skilled in the art to refer to representations of these signals as bits, bytes, words, information, elements, symbols, characters, numbers, points, data, entries, objects, images, files, or the like. It should be kept in mind, however, that these and similar terms are associated with appropriate physical quantities for computer operations, and that these terms are merely conventional labels applied to physical quantities that exist within and during operation of the computer.
It should also be understood that manipulations within the computer are often referred to in terms such as listing, creating, adding, calculating, comparing, moving, receiving, determining, configuring, identifying, populating, loading, performing, executing, storing etc. that are often associated with manual operations performed by a human operator. The operations described herein can be machine operations performed in conjunction with various input provided by a human operator or user that interacts with the computer.
In addition, it should be understood that the programs, processes, methods, etc. described herein are not related or limited to any particular computer or apparatus. Rather, various types of general purpose machines may be used with the following process in accordance with the teachings described herein.
The present invention may comprise a computer program or hardware or a combination thereof which embodies the functions described herein and illustrated in the appended flow charts. However, it should be apparent that there could be many different ways of implementing the invention in computer programming or hardware design, and the invention should not be construed as limited to any one set of computer program instructions.
Further, a skilled programmer would be able to write such a computer program or identify the appropriate hardware circuits to implement the disclosed invention without difficulty based on the flow charts and associated description in the application text, for example. Therefore, disclosure of a particular set of program code instructions or detailed hardware devices is not considered necessary for an adequate understanding of how to make and use the invention. The inventive functionality of the claimed computer implemented processes will be explained in more detail in the following description in conjunction with the remaining Figures illustrating other process flows.
Further, certain steps in the processes or process flow described in all of the logic flow diagrams below must naturally precede others for the present invention to function as described. However, the present invention is not limited to the order of the steps described if such order or sequence does not alter the functionality of the present invention. That is, it is recognized that some steps may be performed before, after, or in parallel other steps without departing from the scope and spirit of the present invention.
Referring now to
Step 006 can comprise two sub-steps: In the first sub-step, the source network 100 usually must determine which external network(s) serve(s) the receiving party 230 (sometimes through using route discovery) and determine the terms of interconnecting with the external network (peering criteria). There are many established ways the source network 100 can determine the how the call can be routed to the destination network 200 serving the receiving party 230.
Routes to the external called number of the receiving party 230 could be pre-programmed in the routing table of the call control point 110 of the source network 100 based on negotiated interconnect agreements with destination networks 230. Alternatively, the routes can be discovered in real time using protocols such as ENUM or DUNDi. Once the call control point 110 of the source network 100 has determined the possible routes to the receiving party 230, the second sub-step of Step 006 is for the call control point 110 of the source network 100 to determine additional peering criteria such as bandwidth, network quality of service, and the price the calling party 120 must pay the destination network 200 to complete the call.
The peering criteria information can be based on interconnect agreements negotiated with destination networks 200 or advertising. In the future, the peering criteria may be obtained from IP protocols that advertise peering prices and service levels over the network. When the route and peering criteria are determined, this information is then sent in Step 008 as a peering authorization request 310 to the Clearinghouse 300 as illustrated in
After the Clearinghouse 300 receives the peering authorization request from the call control point 110 of the source network 100, in Step 010 the Clearinghouse 300 authenticates the source of the information and the calling party. Specifically, in step 012, the Clearinghouse 300 authenticates the source device (call control point 110) which sent the peering request. Step 012 can be completed in various ways such as checking the IP address of the source device or more securely using Secure Sockets Layer (SSL) client authentication. If the source device cannot be authenticated, the peering request may be denied in Step 014. Identifying the source device will reveal the operator of the source network that has established a trusted relationship with the Clearinghouse.
Next, in step 016, the Clearinghouse 300 checks the status of the source network operator to determine if it may originate calls or be granted access to another network. If access to another network is not allowed, the peering request may be denied in Step 018. As part of this process, the Clearinghouse 300 may determine details about the source network identification, such as the organization name and address. One important element in the source network identification is information which indicates how the source network identification was verified.
This information about the source network 100 that is verified by the Clearinghouse 300 can be a value added service for the receiving party 200. In Step 020, the Clearinghouse 300 may check the status of the calling party to determine if it may access external networks. The Clearinghouse 300 may also take actions to identify the calling party. Step 020 can be similar to a Caller Name (CNAM) look-up in the traditional Public Switched Telephone Network (PSTN) or some other mechanism which more securely identifies and verifies the calling party identification. If the calling party is not allowed to access networks external to the source network, the peering request may be denied in Step 022.
Referring now to
Next, in Step 030, the Clearinghouse 300 can check the pricing terms of the peering request. The pricing terms of the peering request can be compared to pricing tables stored in the Clearinghouse 300. If the pricing terms of the request do not match any entries of the table(s), or if the pricing terms are incomplete or ambiguous, the peering request may be denied in Step 032. For example, if the currency specified is Japanese Yen (JPY) and the clearinghouse only performs settlement in US Dollars (USD) then the peering request would be denied in Step 032.
In Step 034, the Clearinghouse 300 checks if the quality of service (QoS) terms of the peering request. The Clearinghouse 300 can check the QoS terms of the peering request against stored values in tables that the Clearinghouse may have for the destination networks 200. If the service level is not supported, then the peering request will be denied by the Clearinghouse in Step 036. For example, if a peering request specifies 64 kb/sec bandwidth for a VoIP call and the Clearinghouse 300 recognizes that 64 kb/sec bandwidth cannot be provided by the destination network 200, then the peering request will be denied in Step 036.
In Step 038, the Clearinghouse 300 compares historical quality of service of the destination device or network 200 to the quality of service requested in the peering request. If the historical quality of service is less than the requested quality of service, the peering request may be denied in Step 040. For example, if the Answer Seizure Ratio specified in the peering request is 50%, but Clearinghouse historical records indicate that the destination device or network 200 has a historical Answer Seizure Ratio of 40% then the peering request would be denied in Step 040.
If all authentication and peering criteria checks are successful, the Clearinghouse 300 creates a peering authorization token for each destination network 200 in Step 042. The token is usually digitally signed using a private key of the Clearinghouse 300 to ensure data integrity and non-repudiation of the token. The tokens are then returned to the call control point 110 of source network 100 in a peering authorization response 315 in Step 044.
Referring now to
When the destination network 200 receives the call setup message, in Step 050 the call control point 210 will validate the peering token contained in the setup message before accepting the call. A common practice for securely validating tokens is validating the digital signature of the token using the public key of the clearinghouse 300. In Step 052, the token can be validated using the public key. If the digital signature is valid; then the destination network 200 can be certain that the token was signed using the Clearinghouse private key. If the token is not valid, the call control point 210 of the destination network 200 will block the call in Step 054. The process then continues in Step 068 in which the call control point 110 of the source network selects the next available destination network 200. If the inquiry to decision Step 052 is positive, then the process proceeds to decision Step 056.
If the token is valid, the call control point 210 of the destination network 200 may choose to check the peering criteria present in the token. The peering criteria can comprise service type, pricing terms, quality of service, just to name a few. Other peering criteria is not beyond the scope of the invention. In decision Step 056, the call control point 210 can determine if the service type present in the token is acceptable for its network configuration. If the inquiry to decision Step 056 is negative, then the call is blocked in Step 058. The process then continues in Step 068 in which the call control point 110 of the source network selects the next available destination network 200. If the inquiry to decision Step 056 is positive, then the process proceeds to decision Step 060.
In decision Step 060, the call control point 210 can determine if the pricing terms found in the token are acceptable for its network terms. If the inquiry to decision Step 060 is negative, then the call is blocked in Step 062. The process then continues in Step 068 in which the call control point 110 of the source network selects the next available destination network 200. If the inquiry to decision Step 060 is positive, then the process proceeds to decision Step 064.
In decision Step 064, the call control point 210 can determine if the quality of service terms found in the token are acceptable for its quality of service parameters. If the inquiry to decision Step 064 is negative, then the call is blocked in Step 066. The process then continues in Step 068 in which the call control point 110 of the source network selects the next available destination network 200.
Referring now to
Peering Authorization Request 310
The Peering Authorization Request 310 from the source IP network 100 to the Peering Authority (Clearinghouse 300) may include the following information listed in Table 1 below.
Peering Authorization Request 310—XML Mapping
Table 2 below maps peering authorization request message information elements to eXtensible Markup Language (XML) tags.
Peering Authorization Response 315
The Peering Authorization Response 315 from the Peering Authority (Clearinghouse 300) to the Source IP Network 100 may include the following information listed in Table 3 below:
Peering Authorization Token
For non-repudiation of peering authorization and settlement services, the peering authorization token usually must be digitally signed with the private key of the Peering Authority (Clearinghouse 300). The peering authorization token may be encoded, encrypted or plain text. The token defines what type of service, quantity of service, quality of service and pricing has been authorized by the Peering Authority.
The peering authorization token returned from a Peering Authority (Clearinghouse 300) may include the information elements in Table 4 below.
Peering Authorization Token—XML Mapping
Table 5 below maps peering authorization token information elements to eXtensible Markup Language (XML) tags and ASCII tags.
Accounting
After a VoIP call, or a peering session, is completed it must be accounted. The call or peering session details must be reported to the settlement clearing or peering authority (Clearinghouse 300). Table 5 below lists Information Elements which should be included in a call or session detail record. The XML format is provided for information elements which have not been defined previously in this document.
Referring now to
The call begins with the calling party 510, John Doe in the Accounts Payable department of National Bank Corp. The calling party has a traditional circuit switched telephone with telephone number 4045266060. The telephone is connected via Circuit 1 of Trunk Group S 520 to a SIP gateway 530 having an IP address 1.1.1.1. SIP, or Session Initiation Protocol, is an IP protocol used transmitting voice, video and other communications over IP networks as is known to one of ordinary skill in the art. The SIP gateway 530 is registered with the SIP Proxy 540 with IP address 1.1.1.2. The SIP Proxy 540 performs the roll of the Call Control Point 110 that is illustrated in
When the calling party 510 calls the telephone number 2564286000, a call setup message is sent from SIP Gateway 530 to the SIP Proxy 540. The SIP Proxy determines to call either Destination Network 1600 or Destination Network 2605. Table 7 below summarizes the routing data and peering criteria for completing the call from the SIP Proxy 540 to a destination network which can complete the call to the receiving party 610.
Table 7 above includes routing information, such as the IP addresses of SIP Gateways 630 and 635 and trunk group—circuit details 620 and 625 connecting to the receiving party telephone 610. Table 7 also includes peering rate information which can be used to bill for the peering session. The peering rate for 64 kbs of bandwidth to terminate a voice call on Network 1-600 is $0.10 USD per 60 seconds. For Network 2-605 the peering rate for the same service is 10 JPY per 60 seconds. Table 7 also includes minimum acceptable quality of service in terms of Answer Seizure Ratio, Mean Hold Time and Post Dial Delay.
Before sending a call setup to either Destination Network 1-600 or Destination Network 2-605, the SIP Proxy 540 sends a peering authorization request 710 to the Peering Authority, ACME Settlement Clearinghouse 700. Below is the peering authorization request message 710. It is an eXtensible Markup Language (XML) message transmitted via Hyper Text Transport Protocol (HTTP).
In the peering authorization request 710 above, separate pricing, bandwidth and quality of service criteria is specified for each destination within each set of <Destination> tags. A global set of peering criteria may be applied to all destinations by including the criteria information within the request message, but outside of the <destination> tags.
When the ACME Settlement Clearinghouse 700 receives the peering authorization request 710, it may perform the following functions:
Below is the peering authorization response message 720 illustrated in
At least one important information element in the peering authorization response message 720 is the peering authorization token. The source network Call Control Point 110 (see
Example of Peering Authorization Token in Text Format
Peering authorization tokens may be in any format, not just an XML format. Below is the peering authorization reformatted in American Standard Code for Information Interchange (ASCII) text format:
When the source SIP Proxy 540 receives the peering authorization request 720 from the Clearinghouse 700, it extracts the peering authorization token and includes the token in the call setup message 730 to the destination network as illustrated in
The SIP Gateway 630 of the Destination Network 1-600 performs the steps below to validate that the call has been authorized by the ACME Settlement Clearinghouse and that the interconnect, or peering, terms are acceptable:
If the price information is not acceptable, the call should not be accepted.
At the end of an interconnect VoIP call, or peering session, both the source and destination networks 600, 605 should report accounting records to the peering authority 700. As illustrated in
Settlement
When the call, or peering session, accounting records 740 are collected, the ACME Settlement Clearinghouse 700 may then perform additional services for the source and destination peers such as interconnect billing, determination of net settlement 40, payments among the peering, execution of any settlement payment transaction, analysis and reporting of inter-peer traffic statistics.
Other Applications of Peering in IP Communications
One of ordinary skill in the art of IP communications recognizes that the peering technique described above for VoIP applications could also be used in other IP applications that require peering between two networks, access control and accounting. A video call, which is a straight-forward extension of the VoIP call scenario described in detail, is an application which could benefit from the techniques described. Other peering applications include data file downloads, interactive gaming, application services or content brokering.
The following example illustrates how the invention can be used for applications other than VoIP. Assume the source network is a service provider offering on-line movie services to its end user subscribers. If the source network does not have the movie content requested by a subscriber (calling party), the source network can send a peering request to a content broker (clearinghouse) to request access to the network distributor of the requested movie. In this example, the network distributor is analogous to the destination network in the VoIP call scenario. The requested movie, or application, is analogous to the receiving party. The content broker would approve the peering request and create a peering token specifying the movie and requested bandwidth for the movie media stream.
The source network would then forward the peering token to the network distributor. The network distributor would then validate the peering token, identify the movie (application) requested and then provide the movie media stream to the source network. The source network would then redirect the movie stream to its end user. At the end of the movie media stream, the source network and network distributor would send their accounting records to the content broker who would facilitate billing and payment from the source network to the network distributor.
It should be understood that the foregoing relates only to illustrate the embodiments of the invention, and that numerous changes may be made therein without departing from the scope and spirit of the invention as defined by the following claims.
This application is a continuation of and claims priority to application Ser. No. 12/288,442 filed Oct. 20, 2008 now U.S. Pat. No. 8,238,329 entitled “Method and System for Securely Authorized VoIP Interconnections Between Anonymous Peers of VoIP Networks,” the entire contents of which are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4726056 | An et al. | Feb 1988 | A |
| 4979118 | Kheradpir | Dec 1990 | A |
| 5155763 | Bigus et al. | Oct 1992 | A |
| 5185780 | Leggett | Feb 1993 | A |
| 5251152 | Notess | Oct 1993 | A |
| 5325290 | Cauffman et al. | Jun 1994 | A |
| 5404516 | Georgiades et al. | Apr 1995 | A |
| 5408465 | Gusella et al. | Apr 1995 | A |
| 5434848 | Chimento, Jr. et al. | Jul 1995 | A |
| 5473630 | Penzias et al. | Dec 1995 | A |
| 5563939 | La Porta et al. | Oct 1996 | A |
| 5570417 | Byers et al. | Oct 1996 | A |
| 5581544 | Hamada et al. | Dec 1996 | A |
| 5600794 | Callon | Feb 1997 | A |
| 5606602 | Johnson et al. | Feb 1997 | A |
| 5633919 | Hogan et al. | May 1997 | A |
| 5638433 | Bubien, Jr. et al. | Jun 1997 | A |
| 5668955 | deCiutiis et al. | Sep 1997 | A |
| 5675636 | Gray | Oct 1997 | A |
| 5712907 | Wegner et al. | Jan 1998 | A |
| 5740361 | Brown | Apr 1998 | A |
| 5790642 | Taylor et al. | Aug 1998 | A |
| 5799072 | Vulcan et al. | Aug 1998 | A |
| 5867495 | Elliott et al. | Feb 1999 | A |
| 5892753 | Badt et al. | Apr 1999 | A |
| 5896445 | Kay et al. | Apr 1999 | A |
| 5898668 | Shaffer | Apr 1999 | A |
| 5898673 | Riggan et al. | Apr 1999 | A |
| 5917891 | Will | Jun 1999 | A |
| 5917897 | Johnson et al. | Jun 1999 | A |
| 5917902 | Saucier | Jun 1999 | A |
| 5943657 | Freestone et al. | Aug 1999 | A |
| 5966427 | Shaffer et al. | Oct 1999 | A |
| 5991373 | Pattison et al. | Nov 1999 | A |
| 5995554 | Lang | Nov 1999 | A |
| 6005925 | Johnson et al. | Dec 1999 | A |
| 6005926 | Mashinsky | Dec 1999 | A |
| 6049531 | Roy | Apr 2000 | A |
| 6067287 | Chung-Ju et al. | May 2000 | A |
| 6084953 | Bardenheuer et al. | Jul 2000 | A |
| 6085238 | Yuasa et al. | Jul 2000 | A |
| 6128280 | Jamoussi et al. | Oct 2000 | A |
| 6128304 | Gardell et al. | Oct 2000 | A |
| 6137869 | Voit et al. | Oct 2000 | A |
| 6157648 | Voit et al. | Dec 2000 | A |
| 6178510 | O'Connor et al. | Jan 2001 | B1 |
| 6205211 | Thomas et al. | Mar 2001 | B1 |
| 6229804 | Mortsolf et al. | May 2001 | B1 |
| 6233234 | Curry et al. | May 2001 | B1 |
| 6240449 | Nadeau | May 2001 | B1 |
| 6259691 | Naudus | Jul 2001 | B1 |
| 6263051 | Saylor et al. | Jul 2001 | B1 |
| 6275490 | Mattaway et al. | Aug 2001 | B1 |
| 6304551 | Ramamurthy et al. | Oct 2001 | B1 |
| 6310873 | Rainis et al. | Oct 2001 | B1 |
| 6317490 | Cameron et al. | Nov 2001 | B1 |
| 6330311 | Mijares, Jr. et al. | Dec 2001 | B1 |
| 6339595 | Rekhter et al. | Jan 2002 | B1 |
| 6345090 | Walker et al. | Feb 2002 | B1 |
| 6366577 | Donovan | Apr 2002 | B1 |
| 6404746 | Cave et al. | Jun 2002 | B1 |
| 6426955 | Gossett, Jr. et al. | Jul 2002 | B1 |
| 6430282 | Bannister et al. | Aug 2002 | B1 |
| 6459708 | Cox et al. | Oct 2002 | B1 |
| 6477164 | Vargo et al. | Nov 2002 | B1 |
| 6487283 | Thomas et al. | Nov 2002 | B2 |
| 6526131 | Zimmerman et al. | Feb 2003 | B1 |
| 6570870 | Berstis | May 2003 | B1 |
| 6611519 | Howe | Aug 2003 | B1 |
| 6614781 | Elliott et al. | Sep 2003 | B1 |
| 6615349 | Hair | Sep 2003 | B1 |
| 6636504 | Albers et al. | Oct 2003 | B1 |
| 6658568 | Ginter et al. | Dec 2003 | B1 |
| 6665271 | Thomas et al. | Dec 2003 | B1 |
| 6680948 | Majd et al. | Jan 2004 | B1 |
| 6707812 | Bowman-Amuah | Mar 2004 | B1 |
| 6735177 | Suzuki | May 2004 | B1 |
| 6751652 | Thomas | Jun 2004 | B1 |
| 6754181 | Elliott et al. | Jun 2004 | B1 |
| 6757823 | Rao et al. | Jun 2004 | B1 |
| 6765896 | Ahmed et al. | Jul 2004 | B1 |
| 6795867 | Ma et al. | Sep 2004 | B1 |
| 6829243 | Sundhar | Dec 2004 | B1 |
| 6996093 | Dalton, Jr. et al. | Feb 2006 | B2 |
| 7017050 | Dalton, Jr. et al. | Mar 2006 | B2 |
| 7099301 | Sheu | Aug 2006 | B1 |
| 20020101967 | Eng et al. | Aug 2002 | A1 |
| 20030012178 | Mussman et al. | Jan 2003 | A1 |
| 20030095541 | Chang et al. | May 2003 | A1 |
| 20030193933 | Jonas et al. | Oct 2003 | A1 |
| 20040042606 | Zino et al. | Mar 2004 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 781 015 | Jun 1997 | EP |
| 0 824 295 | Feb 1998 | EP |
| 0 984 164 | Oct 1999 | EP |
| 2 301 264 | Nov 1996 | GB |
| WO 9714236 | Apr 1997 | WO |
| WO 9723078 | Jun 1997 | WO |
| WO 9818237 | Apr 1998 | WO |
| WO 9836543 | Aug 1998 | WO |
| WO 9837665 | Aug 1998 | WO |
| WO 9848542 | Oct 1998 | WO |
| WO 9911051 | Mar 1999 | WO |
| WO 9914931 | Mar 1999 | WO |
| WO 9914932 | Mar 1999 | WO |
| WO 9926153 | May 1999 | WO |
| WO 0048102 | Aug 2000 | WO |
| WO 0049551 | Aug 2000 | WO |
| WO 0052905 | Sep 2000 | WO |
| WO 0147232 | Jun 2001 | WO |
| WO 0147235 | Jun 2001 | WO |
| WO 0152476 | Jul 2001 | WO |
| WO 0163820 | Aug 2001 | WO |
| WO 0223854 | Mar 2002 | WO |
| WO 2005089141 | Sep 2005 | WO |
| WO 2006065789 | Jun 2006 | WO |
| Entry |
|---|
| International Search Report; PCT/US05/45013; Feb. 20, 2007. |
| AT&T Communications, Adm. Rates and Tariffs, Tariff FCC No. 1, 3rd Revised p. 178.69.1. |
| ETSI, “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Open Settlement Protocol (OSP) for Inter-Domain pricing, authorization and usage exchange,” ETSI TS 101 321, V4.1.1 (Nov. 2003) Technical Specification, pp. 49. |
| Hansson, Allan et al., “Phone Doubler—A step towards integrated Internet and telephone communities,” Ericsson Review No. 4, 1997, Abstract, XP-000725693, pp. 142-151. |
| Johannesson, Nils Olof, “The ETSI Computation Model: A Tool for Transmission Planning of Telephone Networks,” IEEE Communications Magazine, Jan. 1997, pp. 70-79. |
| Netscape Communications Corporation, “Introduction to SSL,” Oct. 9, 1998, [Retrieved from Internet May 19, 2004], http://developer.netscape.com/docs/manuals/security/sslin/contents.htm, pp. 12. |
| RSA Security Press Release, “TransNexus Integrates Industry Leader RSA Security' BSAFE Encryption Software Into Its ClearIPSM Clearinghouse Solution,” Oct. 21, 1999, Abstract XP-002193409, www.rsasecurity.com. |
| Rudkin, S. et al., “Real-time applications on the Internet,” BT Technology Journal, vol. 15, No. 2, Apr. 1997, pp. 209-225. |
| Sin, Sam-Kit et al., “A New Design Methodology for Optimal Interpolative Neural Networks with Application to the Localization and Classification of Acoustic Transients,” IEEE Conference on Neural Networks for Ocean Engineering, 1991, pp. 329-340. |
| The Ascend MaxVoice Gateway, “The asnet pipeline,” Abstract XP-002096239, www.asnet.co.nz/pipeline/sum97/tamvg.html, Mar. 11, 1999. |
| Thom, Gary A., “H.323: The Multimedia Communications Standard for Local Area Networks,” IEEE Communications Magazine, Abstract, XP 000636454, Dec. 1996, pp. 52-56. |
| TransNexus Home Page, Printed May 17, 2005, www.transnexus.com, 2 pp. |
| TransNexus Press Release, “Agis and Popstar introduce Profit-Generating Internet Fax Services to ISP Partners and Customers Worldwide,” Abstract XP-002193408, Jun. 24, 1999, www.transnexus.com, 3 pp. |
| Chaniotakis et at., “Parlay and Mobile Agents in a Homogenized Service Provision Architecture, ” IEEE; Universal Multiservice Networks; ECUMN 2002; 2nd European Conference on Apr. 8-10, 2002; pp. 150-154. |
| Liao, Wanjiun; “Mobile Internet Telephony Protocol: An application layer protocol for mobile Internet telephony services,” Communications, 1999; ICC '99; 1999 IEEE International Conference; vol. 1; Jun. 6-10, 1999; pp. 339-343. |
| Maresca et al.; “Internet Protocol Support for Telephony,” Proceedings of the IEEE, vol. 92, No. 9; Sep. 2004; pp. 1463-1477. |
| Number | Date | Country | |
|---|---|---|---|
| 20130054696 A1 | Feb 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12288442 | Oct 2008 | US |
| Child | 13543855 | US |
