Method for allocating network resources

Abstract

Network resources for a call between a calling party and a called party are allocated. The network resources for the call are reserved based on a reservation request. The network resources are reserved before any one network resource from the reserved network resources is committed. The reserved network resources for the call are committed when a called party indicates acceptance for the call.

Description

BACKGROUND OF THE INVENTION

[0002] The present invention generally relates to allocating network resources. More specifically, the present invention relates to reserving and committing network resources based on an authorized quality of service.

[0003] The known signaling architecture H.323 is an International Telecommunications Union (ITU) defined standard that describes how multimedia communications occur between terminals, network equipment and services on local area networks (LANs) and wide area networks (WANs) that do not provide a guaranteed quality of service (such as Internet Protocol (IP) networks). Quality of service is a measure of communication service quality during a call, and can include, for example, the bandwidth, delay and latency associated with the call. In networks using connectionless “best effort” delivery models, the quality of service typically is not guaranteed; the H.323 is a signaling architecture for such a network.

[0004] The H.323 provides a range of implementation options including gatekeeper-routed signaling. In the H.323 standard, gatekeepers map LAN address aliases to IP addresses and provide address lookups when needed. Gatekeepers also exercise call-control functions to limit the number of H.323 connections and the total bandwidth used by these connections in an H.323 “zone.” Although the gatekeeper is not necessary within the H.323 standard, when a gatekeeper is present in a network, network terminals must make use of its services. In other words, gatekeepers maintain state information for each individual call and all call signaling must pass through the gatekeepers.

[0005] The gatekeeper implementation of the H.323 standard, however, suffers several shortcomings. First, the equipment associated with gatekeepers needs to be extremely reliable so that the gatekeeper is available throughout the course of the call. If the gatekeeper-related equipment fails during a call, the call fails because the state information for the call maintained solely at the gatekeeper is lost. Second, the gatekeeper-related equipment likely cannot scale in a cost effective manner because maintaining the state information and performing the messaging associated with H.323 is complex and processor intensive. Finally, theft of service is possible by bypassing the gatekeepers to place unauthorized and unmonitored calls.

SUMMARY OF THE INVENTION

[0006] Network resources for a call between a calling party and a called party are allocated. The network resources for the call are reserved based on a reservation request. The network resources are reserved before any one network resource from the reserved network resources is committed. The reserved network resources for the call are committed when a called party indicates acceptance for the call.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] FIG. 1 illustrates a network, according to an embodiment of the present invention.

[0008] FIG. 2 illustrates a flow chart to reserve network resources for a call, according to an embodiment of the present invention.

[0009] FIG. 3 illustrates a flow chart for performing two-phase signaling in call connection, according to an embodiment of the present invention.

[0010] FIG. 4 illustrates a flow chart for disconnecting a call, according to an embodiment of the present invention.

[0011] FIG. 5 illustrates a flow chart for translating a network address, according to an embodiment of the present invention.

[0012] FIG. 6 shows the call flow for a normal call setup, according to an embodiment of the present invention.

[0013] FIG. 7 shows an example signaling call flow for reservation of resources in the segment of the network between the edge routers for a voice call, according to an embodiment of the present invention.

[0014] FIG. 8 shows the call flow for a normal call termination, according to an embodiment of the present invention.

[0015] FIG. 9 shows the call flow for a call originating from a BTI but terminating in the PSTN, according to an embodiment of the present invention.

[0016] FIG. 10 shows the call flow for a call originating in the PSTN, but terminating in the IP telephony network, according to an embodiment of the present invention.

[0017] FIG. 11 shows the call flow for a normal release to the PSTN, according to an embodiment of the present invention.

[0018] FIG. 12 shows the call flow for a call released from the PSTN, according to an embodiment of the present invention.

[0019] FIG. 13 shows a call flowwhere the BTI connects to a terminating announcement server, according to an embodiment of the present invention.

[0020] FIG. 14 shows the call flow for Call Trace, according to an embodiment of the present invention.

[0021] FIG. 15 shows the call flow for changing the established call parameters, according to an embodiment of the present invention.

[0022] FIG. 16 shows the call flow for activating a per-use Call Forwarding service, according to an embodiment of the present invention.

[0023] FIG. 17 shows the call flow for Call Forwarding—All Calls when the BTI is available, according to an embodiment of the present invention.

[0024] FIG. 18 shows the call flow for Call Forwarding—All Calls when the Terminating BTI is not available, according to an embodiment of the present invention.

[0025] FIG. 19 shows the call flow for Call Forwarding—Busy when BTIT is available, according to an embodiment of the present invention.

[0026] FIG. 20 shows the call flow for Call Forwarding—Busy when the BTI is unavailable, according to an embodiment of the present invention.

[0027] FIG. 21 shows the call flow for Call Forwarding—No Answer when BTIT is available, according to an embodiment of the present invention.

[0028] FIG. 22 shows the call flow for Call Forwarding—No Answer when the BTI is unavailable, according to an embodiment of the present invention.

[0029] FIG. 23 shows the call flow for Caller ID/Calling Name Delivery Call Flow, according to an embodiment of the present invention.

[0030] FIG. 24 shows a call flow for Call Waiting, according to an embodiment of the present invention.

[0031] FIG. 25 shows the call flow for the simple Three-Way Calling alternative with bridging in BTIO, according to an embodiment of the present invention.

[0032] FIG. 26 illustrates the first steps of a three-way call, according to an embodiment of the present invention.

[0033] FIG. 27 shows the sequence of signaling messages exchanged in the conversion of two separate calls into one three-way call, according to an embodiment of the present invention.

[0034] FIG. 28 shows the call flow for Three-way Calling Bridge in Network Call Flow—Hangup of Host, according to an embodiment of the present invention.

[0035] FIG. 29 shows the call flow for Three-way Calling Bridge in Network Call Flow—Hangup of Participant, according to an embodiment of the present invention.

[0036] FIG. 30 shows the call flow for Call Transfer With Consultation service when the host disconnects, according to an embodiment of the present invenion.

[0037] FIG. 31 shows the call flow for Call Transfer Without Consultation service, according to an embodiment of the present invention.

[0038] FIG. 32 shows the call flow for Return Call, according to an embodiment of the present invention.

DETAILED DESCRIPTION

[0039] Embodiments of the present invention relate to a communications system having a combination of different types of networks, such as a data network(s) (based on, for example, packet switching), a telephone network(s) (such as the Plain Old Telephone Network (PSTN)), and/or a cable network(s). Such a communications system can include intelligent end-terminals that allow a service provider to provide various types of services involving the different types of networks and to exploit the capabilities of the end-terminals. For example, packet telephony can be implemented in embodiments of the present invention where voice can be received and transmitted by a telephone or a communication device (such as a personal computer) connected to the data network via a cable network.

[0040] Embodiments of the present invention relate to call authorization, call signaling, network resource management and end-to-end signaling between communication devices (e.g., telephones, personal computers, etc.). Existing telephone services with a service quality consistent with current standards can be supported while a broader range of packet-enabled communications services can also be supported. Embodiments of the present invention allow pricing and billing of communications services to differ based on the differences in service quality (e.g., bandwidth, delay and/or latency) for the various calls.

[0041] Embodiments of the present invention also allow the intelligent end-points to participate in supporting features of the provided services. These intelligent end-points can be, for example, telephony-capable computers and gateways that interface conventional telephones to the data network. By exploiting the intelligence of these end-points in supporting the features of provided services, functionality (e.g., tasks associated with signaling) historically maintained solely by the network can be efficiently divided among the communication network entities and the intelligent end-points connected to the communication network.

[0042] In addition, embodiments of the present invention protect against theft of service, and minimize the cost and complexity associated with providing reliable service. Unlike known telephone networks, embodiments of the present invention do not require high-availability network servers that maintain the state of each individual call. Rather, embodiments of the present invention can maintain state information only in the edge routers and the end-points that are directly involved in a particular call.

[0043] The following discussion is separated into sections for clarity. First, a system overview of a communication network, according to an embodiment of the present invention, is discussed in Section 1 entitled “Sysstem Overview”. Then, separate aspects of embodiments of the present invention are considered: Section 2 entitled “Two-Phase Resource Reservation”, Section 3 entitled “Two-Phase Signaling”, Section 4 “Gate Coordination on a Per-Call Basis”, Section 5 entitled “Network Address Translation”, Section 6 entitled “Simulating Destination Ring Back”. Finally, Section 7 entitled “Protocol Description” details the protocols for the signaling messages and Section 8 entitled “Signaling Architecture Call Flows” describes the call flows for the signaling architecture both of which are applicable to the various aspects of embodiments of the present invention.

[0044] 1. System Overview

[0045] FIG. 1 illustrates a network according to an embodiment of the present invention. Network 10 includes communication network 100 which is connected to gate controller 110 and gate controller 111, network edge devices 120 and 121, and telephone network gateway 130. Gate controllers 110 and 111 are connected to database storage 140 and 141, respectively. Network edge devices 120 and 121 are connected to access networks 150 and 151, respectively. Access networks 150 and 151 are connected to network interface units 160 and 161, respectively. Network interface units 160 and 161 are connected to telephone interface units (TIUs) 170 and 171, respectively, and communication devices 180 and 181, respectively. TIUs 170 and 171 are connected to telephones 190 and 191, respectively. Telephone network gateway 130 is connected to telephone network 135 which, in turn, is connected to telephone 192.

[0046] Communication network 100 can be a network that supports, for example, Internet Protocol (IP) signaling, IP media transport, and/or asynchronous transfer mode (ATM) media transport. Access networks 150 and 151 can be networks of wires or fibers capable of carrying voice and/or data transmissions. The telephone network 135 can be, for example, the Plain Old Telephone System (PSTN).

[0047] Network interface units 160 and 161 can be, for example, cable modems designed for use on a television coaxial cable circuit. Network interface units 160 and 161 allow communication devices 180 and 181, respectively, to connect to access networks 150 and 151, respectively. Network interface units 160 and 161 also allow TIUs 170 and 171, respectively (and in turn telephones 190 and 191, respectively), to connect to access networks 150 and 151, respectively.

[0048] Network edge devices (NEDs) 120 and 121 are devices located at the edge of the communication network 100 that connects the communication network 100 to the access networks 120 and 121, respectively. The network edge devices can be, for example, routers or bridges or similar equipment that can connect communication network 100 to access networks 150 and 151. Because NEDs 120 and 121 can be specifically implemented as, for example, routers at the network edge, these units are also referred to herein as edge routers (ERs).

[0049] Network edge devices 120 and 121 can implement resource management and admission control mechanisms that allow the communication network 100 to provide assurances of bounded per-packet loss and delay required to assure an authorized quality of service for a call. In other words, network edge devices (e.g., network edge devices 120 or 121) can obtain authorization from an associated gate controller (e.g., gate controller 110 or 111, respectively) on a call-by-call basis before providing access to, for example, enhanced quality of service across the communication network. Said another way, the network edge devices can ensure that enhanced quality of service for a call of a particular party has been authorized and for which usage accounting is being done. Network edge devices can generate accounting records for calls because these devices track the resource usage within the communication network 100 for the calls. Network edge devices can also implement Network Address Translation to support address privacy for called paries and/or calling parties, as described more fully below.

[0050] TIUs 170 and 171 are gateways between telephones and packet-carrying networks, such as access networks 150 and 151 and communication network 100. TIUs 170 and 171 can digitize, compress and packetize voice signals from telephone 190 and 191, respectively, to convert analog voice into data packets for transport over the communication network 100, and vice versa. TIUs 170 and 171 can be, for example, a simple stand-alone telephony device that incorporates the broadband interface, a high-speed data cable modem that incorporates the interface unit (i.e., TIUs and their associated network interface units can be combined into a single device), or an advanced digital set-top box that incorporates the broadband interface. TIUs 170 and 171 can be for example broadband interfaces for telephones; consequently, these units are also referred to herein as broadband telephony interfaces (BTIs).

[0051] TIUs contain sufficient processing and memory to perform signaling and call control functions. More specifically, TIUs 170 and 171 each include a processor and is capable of detecting changes in state information (e.g., hook state detection), collecting dialed digits (e.g., dual-tone multifrequency (DTMF) signals), and participating in the implementation of telephone features for telephones 190 and 191, respectively. TIUs 170 and 171 can also participate in end-to-end capability negotiation as described below.

[0052] Note that the term “end-to-end” refers the association between two end points for a call. For example, where a call involves a calling party and a called party using telephones, the end-to-end association for the call can be between the two telephony interface units. Thus, end-to-end messages for example would include messages originating at one telephone interface unit and terminating at the other telephony interface unit where the messages are opaque to other network entities that merely forward the messages (possibly after performing network address translation as described below). For example, end-to-end messages can be routed between telephone interface units with messages being forwarded by the network edge devices and without the message being routed through the gate controllers. Alternatively, for example, where a call involves a calling party using a telephone and a called party using a communication device (such as a personal computer), the end-to-end association for the call can be between the calling party telephony interface unit and the called party network interface unit.

[0053] TIUs can maintain information for calls while in progress, thereby implementing certain service features locally. For example, call waiting can be implemented locally, by detecting hook flash and controlling the active call. Similarly, return call can be implemented locally by retaining state information in the TIUs about the most recent calls.

[0054] Note that TIUs 170 and 171 are considered to be “untrusted” devices in the sense that the TIUs can operate locally-stored software and are not necessarily under the direct control of the service provider (e.g., the entity operating the communication network 100). Because the TIUs are untrusted devices, information passed to the TIUs can be first encrypted before it is given to the TIUs to guarantee privacy. For example, state information can be passed from the gate controllers 110 and/or 111 to the TIUs which store the state information for their later use (thereby avoiding the need to maintain state information for a call at the gate controllers) by first encrypting the state information; the state information retrieved from the TIUs can be verified subsequently via known encryption techniques.

[0055] In addition to encrypting the state information for the TIUs to maintain, a cryptographic hash function can be applied to the state information to detect the integrity of the state information (i.e., detect whether the state information has been altered by an untrusted entity). By applying a cryptographic hash value to the state information, a hash value is produced which can be sent to and maintained by the TIUs. As a result, when the state information is retrieved from a TIU, the cryptographic hash function can be applied to this retrieved state information; if the same hash value is produced, then the retrieved state information has not been altered at, for example, the TIU. The cryptographic hash functions can be, for example, a modification detect codes (MDCs) or message authentication codes (MACs).

[0056] Gate controllers 110 and 111 are adjunct platforms that have access to authentication databases and customer profile information on database storage 140 and 141, respectively. Gate controllers 110 and 111 implement a set of service-specific control functions to support communication services, such as authentication and authorization, number translation and call routing, service-specific admission control, and signaling and service feature support.

[0057] The gate controllers can authenticate signaling messages and authorize requests for service so that communication services and certain service features are only provided to authorized subscribers. In other words, upon receiving a setup request message from a calling party, the gate controller can authenticate the identity of the calling party and authorize the service sought by the calling party.

[0058] The gate controllers can translate dialed telephone numbers to communication network addresses (such as, for example, IP addresses) based on call routing logic. For example, an originating gate controller (e.g., gate controller 110) can translate a dialed telephone number to a communication network address associated with the terminating gate controller (e.g., gate controller 111). The terminating gate controller can subsequently translate the communication network address to the terminating end-point (e.g., BTI 171) to which the call should be routed. In an alternative embodiment, a single dial telephone number can be mapped to multiple communication network addresses, for example, to allow the signaling and media end-points associated with a call to be distinct.

[0059] The gate controllers can implement a broad range of service-specific admission control policies for the communication services. For example, the gate controllers can provide precedence for particular call (e.g., 911 emergency calls). The gate controllers can perform admission control to implement overload control mechanisms similar to those used in the convention telephone network (e.g., telephone network 135), for example, to restrict the number of calls to a particular location or to restrict the frequency of call setup to avoid signaling overload. These mechanisms can be invoked either dynamically or under administrative control.

[0060] The gate controllers can perform signaling and service feature support where the service features cannot be supported solely by the TIUs. For example, certain service features such as call transfer require changing the end-points participating the calls; in such a case, the gate controllers change the gate parameters because call transfer requires reauthorization by the gate controllers. Service features that depend on the privacy of the calling information, such as caller-ID blocking, are implemented by the gate controllers. In addition, service features that require users to receive a consistent view of feature operation even when a TIU is inoperative are implemented by the gate controllers. For example, the gate controllers can control call forwarding when a TIU for a call is inoperative.

[0061] Gate controllers can be organized in domains where each gate controller is associated with a set of TIUs and the network edge devices that serve those TIUs. Although the TIUs are not trusted entities, a trust relationship exists between an network edge device and its associated gate controller because the gate controller acts as a policy server controlling when the network edge device can provide enhanced quality of service. A trust relationship can also exist between gate controllers.

[0062] A gate controller can act as a simple transaction server so that a failure of a gate controller does not affect associated calls that are in process. In one embodiment, a gate controller domain can include a primary and a secondary gate controller. If the primary gate controller fails, only calls in a transient state are affected (i.e., calls that are being established including, for example, where network resources are being allocated). The TIUs associated with those affected calls in a transient state will try to be established on the secondary gate controller after a time-out period has elapsed. All active calls (i.e., calls in progress) are unaffected by the failure of a primary gate controller because the gate controller does not retain state information for these stable, active calls. As a result, gate controllers easily and efficiently scale as more gate controllers for the communication network are required.

[0063] Telephone network gateway 130 can include a combination of a trunking gateway (not shown) and a signaling gateway (not shown). The trunking gateway can convert between a data format used on the data network 100 and the pulse code modulation (PCM) format typically used for transmission over the telephone network 135. The signaling gateway can provide signaling internetworking between signaling protocols of embodiments of present invention described below and conventional telephony signaling protocols such as ISUP/SS7 (i.e., Integrated Services Digital Network User Part/Signaling System 7). In an alternative embodiment, a media gateway control protocol can be used to control the operation of a media gateway separate from a signaling gateway.

[0064] Although not shown in FIG. 1, additional network entities (not shown) can be included in the network 10. For example, the gate controllers can use other servers to implement the authorization or the translation functions. Similarly, three way calling can be supported using audio bridges in the network 10.

[0065] Note that although a limited number of network entities are shown in FIG. 1 for simplicity of presentation, other network entities can be included in network 10. For example, although only a sole network interface unit (e.g., a cable modem) is shown connected to a sole network interface unit, multiple network interface units are likely connected to each access network. Similarly, although only a few network edge devices, a few gate controllers and a sole telephone network gateway are shown connected to the communication network 100, many such devices can be connected to the communication network 100. Many other variations to the network 10 shown in FIG. 1 are possible.

[0066] 2. Two-phase Network Resource Reservation

[0067] In embodiments of the present invention, network resources for a call between a calling party and a called party are allocated. The network resources for the call are reserved based on a reservation request. The network resources are reserved before any one network resource from the reserved network resources is committed. The reserved network resources for the call are committed when a called party indicates acceptance for the call.

[0068] The term “network resources” is used herein as the facilities of a communications network required for a call and any auxiliary services associated with that call. Network resources can include, for example, the capabilities or capacities of equipment within the communications network needed to establish and maintain a call at an appropriate quality of service. The equipment within the communications network can include, for example, routers, bridges and gateways within the communications network.

[0069] The called party “indicates acceptance” for the call in a number of ways. For example, where the called party is using a telephone 190, the called party can indicate acceptance for the call by picking up the telephone hand set thereby causing an off-hook condition. Where the called party is using a communication device 181 (e.g., a personal computer), the called party can indicate acceptance by making an appropriate selection with the communication device 181 that initiates handshake signaling (i.e., a personal computer equivalent for an off-hook condition). Where the called party has an answering machine, the answering machine timer can expire to connect the call.

[0070] Network resources are “reserved” in the sense that the network resources required for a particular call can be identified before the called party is actually connected to the calling party. These network resources can be reserved through the appropriate signal messages collectively referred to herein as a “reservation request”. After the appropriate network resources have been reserved based on the reservation request, these network resources are committed when the called party indicates acceptance for the call. By committing the network resources only when the called party indicates acceptance for the call, the accounting for the call can, for example, accurately track the time of the actual call while excluding the time of the call setup.

[0071] Network resources are “committed” in the sense that an available network resource operates such that the voice information between the calling party and the called party is transported. Before the network resources are committed, the network resources are allocated for the call but are not configured to actually carry the voice information for the call. By committing the reserved network resources once the called party indicates acceptance for the call, the network resources are not wastefully configured before they are actually needed. This can be particularly relevant for portions of the communication network where resources are limited, such as, for example, the upstream resources within the cable network.

[0072] The term “quality of service” is used herein to include, but not limited to, the measure of telecommunication service quality provided during a call. The quality of service can be specified by a calling party, a called party or the service provider of the communications network, or any combination thereof. In other words, the quality of service is “authorized” in the sense that the calling party and/or the called party specify a quality of service for the call and the service provider can verify the specified quality of service for the call. For example, a calling party transferring data (e.g., rather than transferring solely voice) may subscribe for a service with a quality of service having a large bandwidth and small latency; in such an example, a service provider can verify the service subscription for the particular quality of service associated with the call for that particular calling party.

[0073] FIG. 2 illustrates a flow chart to reserve network resources for a call, according to an embodiment of the present invention. FIG. 2 is a simplified view of the connection process to better illustrate the two-phase allocation of network resources. This process is in two phases in the sense that network resources are first reserved and then committed in separate and distinct phases. In other words, network resources are reserved first; once the reservation process is complete, then the reserved network resources can be committed. Other aspects of the overall process will be described in further detail in other sections below.

[0074] Note that components of the communications networks shown in FIG. 1 are referred to in FIG. 2 for convenience with the shorthand notation: originating TIU 170 (TIUO), originating network edge device 120 (NEDO), originating gate controller 110 (GCO), terminating gate controller 111 (GCT), terminating network edge device 121 (NEDT), and terminating TIU 171 (TIUT).

[0075] At step 210, a setup message for a call between a calling party and a called party is sent from the originating TIU 170 to the originating gate controller 110 and the terminating gate controller 111. For example, upon receiving the setup message at the originating gate controller 110, the setup message (possibly modified with additional information) can be forwarded to the terminating gate controller 111 through communication network 100. In one embodiment, the setup message can be, for example, in the form of the SETUP message described below in Section 7 entitled “Protocol Description”.

[0076] At step 220, a gate for the call is established at the terminating network edge device 121 upon receiving the setup message from terminating gate controller 111. A “gate” is a call-admission control mechanism that uses, for example, known packet filters at the edge routers. At step 230, another gate for the call is established at the originating network edge device 120. In one embodiment, the gates can have associated time limits on the gate duration; such a features can allow the calls to be limited where, for example, the calls are established with a pre-paid calling card that has a limited amount of calling time that is pre-paid.

[0077] Note that by establishing the gates at the originating and terminating network edge devices rather than at the corresponding gate controllers, the state information for the call is maintained at a network entity through which the call is routed. In other words, state information for a call can be maintained without maintaining the state information at a gate controller. Consequently, if a gate controller fails after the gates have been established for a call, the call can be maintained. The establishment of gates for a call are discussed more fully below in the Section 4 entitled “Gate Coordination on a Per-Call Basis”.

[0078] At step 240, a reserve message is sent from the originating TIU 170 to the originating NED 120. At step 250, a reserve message is sent from the terminating TIU 171 to the terminating NED 121. The reserve messages sent by the originating TIU 170 and terminating TIU 171 are a part of the reservation process where an allocation of network resources is requested but the network resource need not yet be assigned or committed. Allocating the network resources includes the verifying that the quality of service desired by a TIU is no greater than the quality of service authorized by the corresponding gate controller; the gate controller authorizes a quality of service for a call using the authentication databases and customer profile information on the associated database storage (e.g., database storage 140 and 141).

[0079] To provide telephone-grade service over network 10, the network 10 can provide bounded per-packet loss and delay for the voice packets of a call by performing active resource management both in the access network 150 and 151, and communication network 100. Because the network edge devices (e.g., NEDs 120 and 121) within the connection path for a call may have capacity constrained links, reservation requests for a call (and any associated messages) are forwarded end to end, thereby ensuring that network resources are available end to end. In one embodiment, because the access networks 150 and 151 may be capacity constrained (at least in the upstream direction), resource management is performed on a per-call basis for the access networks 150 and 151.

[0080] Resource management in the communication network 100, however, can be performed on a per-call basis or on a coarse-grained resource basis (i.e., resources within the communication network 100 can be reserved for multiple calls at a given time). Resource management within portions of the communication network 100 may be performed on a per-call basis because some network edge devices with the communications network 100 may not have sufficient processing capacity to process a large number of reservation messages typical for high volume call traffic. Alternatively, resource management within portions of the communication network 100 may be performed on a multiple-call basis if these portions of the communication network 100 are adequately provisioned (i.e., sufficient capacity has been reserved by a multiple-call reservation); in such cases, network edge devices within these portions of communication network 100 need not perform per-call admission control. Consequently, in an embodiment of the present invention, some network edge devices do per-flow admission control to interpret reservation requests while other network edge devices that are in capacity-rich regions of the data network 100 are provisioned to simply forward these messages without interpretation.

[0081] Embodiments of the present invention can perform resource reservation in the communication network 100 in a uni-directional manner which thereby compensates for routing asymmetries. Thus, when the originating TIU 170 sends a reservation request to the originating NED 120 and when the originating TIU 170 receives back an acknowledgment for the reservation request, two aspects are of the connection are confirmed. First, adequate bandwidth for the call is available in both directions over the access networks 150 and 151. Second, adequate bandwidth for the call is available over the communication network 100.

[0082] Steps 210 through 240 describe the process of reserving the network resources. At this point, the network resources to be used for the call are reserved, but none of these network resources are yet committed.

[0083] At step 250, end-to-end messages are exchanged between the originating TIU 170 and the terminating TIU 171. As previously discussed above, the term “end-to-end” refers the associated between two end points associated with a call. So, where a call involves a calling party and a called party using telephones, the end-to-end association for the call can be between the two telephony interface units; thus, end-to-end messages would include messages originating at one telephone interface unit and terminating at the other telephony interface unit.

[0084] The end-to-end messages can include, for example, a ring message from the originating TIU 170 to the terminating TIU 171, a ring back message from the terminating TIU 171 to the originating TIU 170, and a connect message from the terminating TIU 171 to the originating TIU 170. The ring message can signal the terminating telephone 191 to ring thereby indicating an incoming call. The ring back message can signal the originating TIU 170 that the terminating telephone 190 is ringing. The connect message can signal to the originating TIU 170 that the called party has indicated acceptance for the call by, for example, going off-hook. Note that these end-to-end messages can be routed between the originating TIU 170 and the terminating TIU 171 without being routed through the originating gate controller 110 or terminating gate controller 111.

[0085] At step 270, upon the calling party and the called party being connected (e.g., upon an off-hook condition by the called party and a connect message being sent), a commit message is sent from the originating TIU 170 to the originating NED 120 and from the terminating TIU 171 to the terminating NED 121.

[0086] At step 280, upon receiving the commit message at the originating NED 120, the gate established at the originating NED 120 in step 230 is opened. Similarly, at step 290, upon receiving the commit message at the terminating NED 121, the gate established at the terminating NED 120 in step 220 is opened. At this point when the gates are opened at the originating NED 120 and the terminating NED 121, the reserved network resources are committed. The commit process can include a verification by the NED that the actual quality of service sought by the associated TIU is no greater than the quality of service reserved during the reservation process.

[0087] The gate at the originating edge router and the gate at the terminating edge router for each call are opened almost simultaneously (e.g., within a few hundred milliseconds of each other) because, under normal operating conditions, the calling party and the called party send respective Commit message to their respective network edge devices substantially simultaneously. Similarly, under normal operating conditions, the calling party and the called party end the call and send respective release messages to their respective network edge devices substantially simultaneously. Gate coordination prevents billing for incomplete calls and prevents theft of service by two colluding BTIs.

[0088] By separating the reservation process from the commit process, embodiments of the present invention advantageously ensure that network resources are available before actually ringing the far-end telephone (e.g., the telephone of the called party). This, of course, advantageously ensures that usage recording is not initiated until the far-end telephone goes off hook. Consequently, call billing excludes calls that are not completed (e.g., where the called party does not answer) and excludes the portion of calls that occur before the called party answers.

[0089] Although FIG. 2 describes an embodiment for reserving network resources where the calling party and the called party were using telephones 190 and 191, respectively, through TIUs 170 and 171, respectively, the process can be analogized for a calling party and/or called party using a communication device 180 and/or 181, respectively.

[0090] Note that the state information for a call can be maintained without maintaining the state information at a gate controller. From the perspective of the originating gate controller, a gate setup message for a call (e.g., a GATESETUP message described in Section 7 below) is received through a network edge device connecting a trusted network to an untrusted network. The state information for the call (e.g., contained within a GATEALLOC message described in Section 7 below) is formatted at the gate controllers based on the setup message for the call. The state information for the call is sent to the originating network edge device without maintaining the state information at the originating gate controller and at the terminating network edge device without maintaining the state information at the terminating gate controller.

[0091] Note that the term “maintained” as used herein in reference to the state information is intended to include storing and using the state information while the call is being establishing, the call is in progress and the is being released. Although the state information may be temporarily stored at the gate controllers, the state information is not maintained at the gate controller because the gate controllers do not do not use the state information (e.g., for call processing) while the call is being establishing, the call is in progress and the call is being released. In fact, the gate controllers need not stored the state information after the state information has been provided to the network edge routers because the state information for the call is accessed at the gate controllers, not the gate controllers.

[0092] 3. Two-Phase Signaling

[0093] In embodiments of the present invention, signaling messages are exchanged for a call between a calling party to a called party in two phases. The signaling messages are exchanged in two phases in the sense that the messages for setting up the call are exchanged in one phase and the messages for connecting the call are exchanged in a separate and distinct second phase. By separating the messages for setting up the call from the messages for connecting the call, the later messages can be exchanged end to end without being routed through the gate controllers that set up the call.

[0094] Note this concept of two-phase signaling is distinct from the concept of two-phase network resource reservation in the sense that the two-phase signaling can be performed in combination with or independent of the two-phase network resource reservation. In other words, when done in combination, the messaging for the two-phase signaling can be interleaved with the messaging for the two-phase network resource reservation; when done independently, the messages for each can be distinct. The two-phase network resource reservation relates to reserving network resources without committing them, then committing those reserved resources. The two-phase signaling relates to performing signaling to set up the call, then once the call is setup (e.g., thereby confirming the authoried quality of service), exchanging end-to-end messaging.

[0095] A setup message having a destination address is forwarded from the calling party to the called party. A setup acknowledgment message is received at, for example, a gate controller from the called party if the destination address corresponds to the called party. The received setup acknowledgment message is sent to the calling party. The calling party and the called party exchange end-to-end messages if the calling party received the forwarded setup acknowledgment message and if at least one from the group of the called party and the calling party sent a reserve message to an associated network edge device.

[0096] FIG. 3 illustrates a flow chart for performing two-phase signaling in call connection, according to an embodiment of the present invention. At step 310, the calling party goes off-hook and dials a telephone number of the called party. For convenience, FIG. 3 will be discussed where the calling party is using telephone 190 and the called party is using telephone 191. Of course, any number of arrangements are possible, such as the calling party using communication device 180. At step 320, the originating TIU 170 collects the dialed digits.

[0097] At step 330, the originating TIU 170 sends a setup message to the originating gate controller 110. The setup message can be sent through network interface unit 160, access network 150, NED 120 and communication network 100. In one embodiment, the setup message can be, for example, in the form of the SETUP message described below in Section 7 entitled “Protocol Description”.

[0098] At step 340, the setup message is forwarded from the originating gate controller 110 to the terminating gate controller 111. At step 350, the setup message is forwarded from the terminating gate controller 111 to the terminating TIU 171. (After receiving the setup message, the originating gate controller 110 and the terminating gate controller 111, can establishe a gate at the originating NED 120 and a gate at the terminating NED 121 as described in Section 2 above.) At step 360, if the destination address of setup message corresponds to the terminating TIU 171, a setup acknowledgment message is sent to the TIU 170. The setup acknowledgment message can be sent, for example, through terminating gate controller 111 and originating gate controller 110. In one embodiment, the setup acknowledgment message can be, for example, in the form of the SETUPACK message described below in Section 7 entitled “Protocol Description”.

[0099] At step 370, the network resources for the call are reserved. As described above in Section 2 entitled Two-Phase Network Resource Reservation, a reserve message is sent from the originating TIU 170 to the originating NED 120 and from the terminating TIU 170 to the terminating NED 121 when an allocation of network resources is requested but the network resource need not yet be assigned or committed.

[0100] At steps 380 through 395, end-to-end messages are exchanged between the originating TIU 170 and the terminating TIU 171 if the calling party received the setup acknowledgment message sent to the originating TIU 170 in step 360 and if the calling party or the called party sent a reserve message to its NED. In other words, end-to-end messages relating to the connection of the call are exchanged only after the reservation messages have been exchanged and the reservation process is complete. This ensures that service is only provided to calling and called parties that have been authorized and authenticated for the call. This also ensures that the call is established for a specifically authorized quality of service and that the call is billed appropriately.

[0101] At step 380, a ring message is sent from the originating TIU 170 to the terminating TIU 171. The ring message can signal the terminating telephone 191 to ring thereby indicating an incoming call.

[0102] At step 390, a ring back message is sent from the terminating TIU 171 to the originating TIU 170. The ring back message can signal the originating TIU 170 that the terminating telephone 190 is ringing.

[0103] At step 395, a connect message is sent from the terminating TIU 171 to the originating TIU 170. The connect message can signal to the originating TIU 170 that the called party has indicated acceptance for the call by, for example, going off-hook.

[0104] These end-to-end messages can be routed between the originating TIU 170 and the terminating TIU 171 without being routed through the originating gate controller 110 or terminating gate controller 111 because state information for the call can be maintained without maintaining it at the gate controllers 110 and 111. In addition, these end-to-end message can be routed through NEDs 120 and 121 opaquely.

[0105] Note that by separating the signaling for a call relating the reservation process and relating to connect process, the concept of the traditional dedicated phone line for a telephone user can be replaced with a process that authenticates the calling party and called party, and authorizes a desired quality of service on a per-call basis. In other words, only authenticated users reserved network resources for an authorized quality of service before these network resources are connected. Consequently, calls having varying qualities of service can be provided and appropriately billed on a call-by-call basis.

[0106] Furthermore, by separating the signaling for a call into signals relating to the reservation process and signals relating to the connect process, the gate controllers are involved in the signaling process where only needed: during the reservation process. After the reservation process is complete, the originating and terminating gate controllers pass the state information for the call to, for example, the originating and terminating TIUs without maintaining the state information at the gate controllers. The gate controllers no longer need be involved in the call and messaging related to the connection process can be sent end-to-end without being routed through the gate controllers. In other words, the gate controllers are involved only during the initial start of the call but not during the call duration. This results in a reduction of the message load by, for example, approximately a factor of three. Consequently, the amount of memory need in the gate controllers is greatly reduced. Moreover, the gate controllers can be constructed without the typically stringent requirements for reliability.

[0107] 4. Gate Coordination on a Per-Call Basis

[0108] As discussed in the preceding section, reserved network resources can be committed upon the originating and terminating network edge devices receiving commit messages indicating that the call has been connected. At this point, gates associated with a call between a calling party and a called party can be opened in a coordinated fashion. A timer associated with a first gate opened at an originating network edge device is initiated. A first gate open message is sent from the originating network edge device to the terminating network edge device. The first gate at the originating network edge device is released if the timer expires before at least one from the group of: (1) an acknowledgment based on the sent first gate open message is received from the terminating network edge device, and (2) a second gate open message is received at the originating network edge device from the terminating network edge device after the terminating network edge device has opened a second gate associated with the called party.

[0109] At step 400, a timer associated with a gate at the originating NED 120 is initiated upon receiving a commit message from the originating TIU 170. At step 410, a timer associated with a gate at the terminating NED 121 is initiated upon receiving a commit message from the terminating TIU 171. As described above in Section 2 entitled “Two-Phase Network Resource Reservation”, the commit message is sent from a TIU to the associated NED upon the called party indicating an acceptance for the call (e.g., by a connect message being sent from the terminating TIU to the originating TIU). The order steps 400 and 410 depends on the order in which the NEDs receive the commit messages from their associated TIUs.

[0110] At step 420, a gate open message is sent from the originating NED 120 to the terminating NED 121. At step 430, a gate open message is sent from the terminating NED 121 to the originating NED 120. In one embodiment, the setup acknowledgment message can be, for example, in the form of the GATEOPEN message described below in Section 7 entitled “Protocol Description”. The order in which steps 420 and 430 are performed depends on the order in which steps 400 and 410 are performed. A gate open message is sent from one NED to the other NED to notify that other NED when a gate for the call has been opened.

[0111] At step 440, a gate open acknowledgment message is sent from originating NED 120 to terminating NED 121 upon the originating NED 121 receiving the gate open message sent during step 430 by terminating NED 120. At step 450, a gate open acknowledgment message is sent from terminating NED 121 to originating NED 120 upon the terminating NED 120 receiving the gate open message sent during step 420 by originating NED 120. In one embodiment, the setup acknowledgment message can be, for example, in the form of the GATEOPENACK message described below in Section 7 entitled “Protocol Description”. The order in which steps 440 and 450 are performed depends on the order in which the gate open acknowledgment message are received.

[0112] At conditional step 470, a determination is made as to whether the timer for the gate at the originating NED 120 expired before (1) the originating NED 120 received the gate open acknowledgment message from the terminating NED 121, or (2) the originating NED 120 received the gate open message from the terminating NED 121. If the timer expired before either condition is satisfied, then the process proceeds to step 475 where the gate at the originating NED 120 is closed and released. If the timer did not expire before either condition is satisfied, then the process proceeds to step 477 where the gate at the originating NED 120 is allowed to remained open.

[0113] At conditional step 480, a determination is made as to whether the timer for the gate at the terminating NED 121 expired before (1) the terminating NED 121 received the gate open acknowledgment message from the originating NED 120, or (2) the terminating NED 121 received the gate open message from the originating NED 120. If the timer expired before either condition is satisfied, then the process proceeds to step 485 where the gate at the terminating NED 121 is closed and released. If the timer did not expire before either condition is satisfied, then the process proceeds to step 487 where the gate at the terminating NED 121 is allowed to remained open.

[0114] A gate is “closed” in the sense that the call is no longer active although the gate for the call remains established for possible later use. For example, in a call having a call waiting feature, a first party can be connected to two other parties and two gates (one per call) will be established at the network edge device associated with the first party. In such a case, as the first party switches between the calls the temporarily inactive call will have an associated gate that is closed; this closed gate can be reopened upon the call being reactivated.

[0115] A gate is “released” in the sense that the call is no longer active and the gate for the call is deleted from the associated network edge device. In such a case, for a call to be started, the entire network resource reservation process and commit process (see, e.g., the discussed relating to FIG. 2) have to be repeated.

[0116] The timer at a gate ensures that the other gate related to the call is also opened within the timer period so that billing for the call is accurate and so that theft of service can be prevented. Without such gate coordination, either a service provider could bill a party for a call where only one gate was opened (even if the calling party was not connected to the called party) or a service provider could be susceptible to theft of service for a call where only one gate was opened. Considering the latter, theft of service could occur without gate coordination, for example, by two colluding TIUs: where the originating TIU can initiate a call and only the terminating TIU sends a local commit message, the single gate would not be released for up to several minutes because the far-end telephone could be ringing; the originating BTI could then steal service during this time. By sending the gate open message from the network edge device with an open gate to the network edge device without a corresponding peer gate, the second gate for the call is sure to be established even if a commit message is not received from the associated TIU (as could be the case if a theft of service was attempted).

[0117] Gate coordination can also be performed at the end of a call. Just as a gate open message and a gate open acknowledgment message is sent to the network edge device where the peer gate is established, a gate close message and a gate close acknowledgment message can be sent upon a gate closing to the network edge device where the peer gate is open. In other words, when a call is ended by either the calling party or the called party, the party ending the call has its gate closed and the peer gate is informed of the closure so that the peer gate is also closed. An example of the message exchange for a gate closing is shown in FIG. 8 and the associated discussion in Section 8 entitled “Signaling Architecture Call Flows”.

[0118] By coordinating the gate closings, again theft of service by a malfunctioning or malicious TIU can be prevented. Consider the case where the originating TIU 170 calls terminating TIU 171 and pays for the call. If either the calling party or the called party end the call, the gates at both the originating NED 120 and the terminating NED 121 need to be closed. Because the originating TIU 170 is being billed for the call, the calling party has an incentive to issue a release message to close the gate at the originating NED 120. The terminating TIU 171, however, cannot be trusted to send the release message to close the gate at the terminating NED 121. A gate close message sent from the originating NED 120 can close the gate at the terminating NED 121 to prevent the terminating TIU 171 from placing another call and having that call billed to the party associated with TIU 170.

[0119] 5. Network Address Translation

[0120] Because the TIUs are untrusted entities, any information that a calling party or a called party desires to keep private, such as caller ID information or address information, should be accessible to the network 10 but not to other untrusted entities. This section describes the use of network address translations and encryption techniques that allow gate controllers to send state information to TIUs where it is maintained in a form that renders the private information opaque.

[0121] In one embodiment, a call between a calling party and a called party is connected. Information associated with the call is sent from the calling party to the called party without the called party receiving a source address that indicates at least one from the group of a logical identity of the calling party and a geographical identity of the calling party.

[0122] The term “logical identity” is used to herein to include, for example, any aspect of the source address or destination address that indicates the specific identity of a calling party or the called party. The term “geographic identity” is used to herein to include, for example, an aspect of the source address or destination address that indicates the particular geographic location of a calling party or called party. Even where a network address has been modified or altered to protect the logical identity of a calling party or called party, the remaining aspects of the network address can reveal the general geographic location of the party. In an embodiment of the present invention, information is sent from one party to another party without revealing either the logical identity nor the geographic identity of a party.

[0123] FIG. 5 illustrates a flow chart for translating a network address, according to an embodiment of the present invention. At step 500, packets having the source address and the destination are sent from the originating TIU 170 through the originating network interface unit 160 towards the originating NED 120. The source address and the destination address locally identify the calling party and the called party, respectively. These addresses are “local” in the sense that they are associated with particular portions of networks (also referred to herein as “address domains”), such as portions of the access network 150 and/or communication network 100 and/or other access networks (not shown in FIG. 1). These local addresses are not sent outside of their resepective address domains. To send packets outisde of the address domain, the destination needs to be identified by a global address, as described below. Table 1 illustrates an example of the source address (SA) and the destination address (DA) at this point.

TABLE 1
SA 10.10.1.5
DA 10.10.1.27

[0124] At step 510, the packets received at NED 120 are translated from local addresses for the address domain within access network 150 to global addresses. Not only can the destination address be translated into a global address, but the source address can also be translated into a global address. Table 2 illustrates a translation table for the call used at NED 120. Note that the global addresses used for the call can be assigned dynamically, for example, on a call-by-call basis so that when a call has ended, the global address can be reused for another, unrelated call.

	TABLE 2
	Local Address	Global Address
SA	10.10.1.5	135.4.1.7
DA	10.10.1.27	135.4.2.15

[0125] At step 520, the packets are forwarded from the originating NED 120 to the terminating NED 121. At this point, the packets have the global address shown in Table 2.

[0126] At step 530, the packets received at the terminating NED 121 are translated from global addresses to addresses that are local to the address domain for which the terminating access network 151 is included. Table 3 illustrates a translation table for the call used at NED 121 for translating the global addresses to local addresses.

TABLE 3
Global Address	Local Address
135.4.1.7	10.10.100.19	SA
135.4.2.15	10.10.100.7	DA

[0127] At step 540, the packets translated by the terminating NED 121 are sent through access network 151 to the terminating TIU 171. Table 4 illustrates the source address and the destination address for the packets for the call as the packets are transmitted across terminating access network 151, through terminating network interface unit 161 to the terminating TIU 171.

TABLE 4
SA 10.10.100.19
DA 10.10.100.7

[0128] The translated packets are received at the terminating TIU 171 without revealing the logical identity and the geographic identity of calling party. Note that the called party only has access to the global source address and the global destination address which themselves are translations. Because the source address of calling party has been translated twice, once at the originating NED 120 and once at the terminating NED 121, address information about the calling party has been altered beyond recognition to the calling party.

[0129] Once the call is completed, the translation tables at the originating NED 120 and the terminating NED 121 can be deleted, and the global addresses can be released for reuse in another call. For example, if the network address translation is incorporated into the funcitonality of the respective gates, the global addresses can be released when the gates are released. In another embodiment, the global addresses can be released after a time period of inactivity.

[0130] FIG. 5 illustrates the process by which packets are sent from the originating TIU 170 to the terminating TIU 171. Similarly, packets sent from the terminating TIU 171 to the originating TIU 170 can be translated at the terminating NED 121 (reverse of the translation shown in Table 3) and again at the originating NED 120 (reverse of the translation shown in Table 2). Thus, the source address and the destination address of the packets can be sent from the terminating TIU 171 to the originating TIU 170 without revealing the logical identity and the geographic identity of called party.

[0131] The double translation of network addresses can be provided as a service to a subscriber by a service provider. In other words, a call can be connected where the calling party and/or the called party subscribe to the double translation service. FIG. 5 illustrates the case where the privacy of both the calling party and the called party address information is maintained: both the source address and the destination address of packets for the call are translated as the packets are sent from the calling party to the called party and as packets for the call are sent from the called party to the calling party.

[0132] The double translation service can be provided to one party (i.e., only the calling party or the called party) without providing the service to the other party. In such a case, for example where only the calling party has subscribed to the double translation service, the first source address for packets sent from the originating TIU 170 are translated at the originating NED 120 into a global source address, and the global address for these packets are translated at the terminating NED 121 into a second local source address. As packets are sent from the terminating TIU 171, the second local source address is translated at the terminating NED 121 into the global source address, and the global source address is translated into the first source address at the originating NED 120.

[0133] In other words, where only one party has subscribed to the double translation service, the address associated with that party is translated twice. Consequently, the logical identity and the geographic identity of that party is maintained in privacy from the other party for the call.

[0134] The translation tables at the originating NED 120 and the terminating NED 121 can be set up for a specific call and then can be deleted at the end of the call. This further ensures the privacy of the calling party and/or called party because the global addresses are not repeated. Furthermore, by releasing the global addresses at the end of a call, the global addresses can be reused for another call having a different calling party and/or called party. Consequently, any potential shortage in the number of global addresses can be alleviated because the number of active calls at one time is much less than the number of total calling parties and called parties.

[0135] 6. Simulated Destination Ring Back

[0136] In another embodiment of the present invention, a ringback for a call between a calling party and a called party can be simulated. A connection acknowledgment associated with the call is received where the calling party is located within a first network and the called party is located within a second network. A prestored ring back signal from a set of prestored ringback signals is selected where the selected prestored ring back signal is associated with the second network. The selected prestored ring back signal is sent to the calling party.

[0137] The prestored ringback signal can be, for example, a signal that is indicative of the network associated with the called party rather than a signal originated by that network. For example, a signal indicative of a foreign network (i.e., a network located in a foreign country) can be stored at a terminating TIU and provided within a ring back message sent to the origianting TIU. In such a case, the ring back signal can simulate the ring back signal for that foreign country rather than relying on the actual foreign-network-originated ring back signal.

[0138] 7. Protocol Description

[0139] This section contains details of the various protocols associated with embodiments of the present invention. These include the communication between BTI and Gate Controller, between the BTI and Edge Router, between the BTI and other BTIs, between the Gate Controller and Edge Router, between Edge Router and Edge Router, and between Gate Controller and Gate Controller.

[0140] All messages are given here in a text-based format, using a type/value structure. This is particularly easy for prototype implementations, and for describing the interactions between network elements. However, if any system components exist where memory is a serious limitation, it is possible that a binary format could be used to conserve buffer space requirements.

[0141] A sample message is:

[0142] SETUP 0S55072 v1.0; DEST E164 8766; CALLER 8718 Bill Marshall; AUTHID 3312120; CRV 21; CODING 53B,6 ms G.711

[0143] Messages consist of a sequence of type/value pairs. Each element of the sequence is separated by a semicolon; a semicolon at the end of the message is optional. The type and value are ascii character strings, separated by white space (e.g. spaces or tabs). Generally every element contains at least two items, the type name and the parameter value, but may contain several white-space separated parameter values.

[0144] The first element of every message is in a standard format. The type of the first element is the message name, the first parameter is the transaction identifier, and the second parameter is the version number (v1.0 here).

[0145] Embodiments of the present invention can use an application-layer retransmission scheme to achieve reliable transport of messages. This is done independent of any lower layer reliable transmission protocol, since the signaling system must also recover from component failures and restart transactions when a component has failed. This often happens after the component has received, acknowledged receipt, and has started working on a request; it is up to the application layer to realize that no response is coming and to re-initiate the transaction.

[0146] We therefore specify the behavior of the network elements as if the underlying transport is merely UDP/IP, and provides no buffering, flow control, nor error recovery.

[0147] All basic message exchanges are transaction-based. All start with a request message issued by a client, and sent to a server. The client must provide a unique transaction identifier for each separate request, and provide that transaction identifier in the standard place in all messages. The client must insure that the transaction identifier is not reused for any subsequent messages for a period of at least some specified interval. (approximately 30 seconds, exact value TBD).

[0148] A sample exchange begins with a client forming a request message and sending it to the server:

[0149] SETUP 1X64193 v1.0; <other stuff>

[0150] The message type is SETUP, the transaction identifier is 1X64193, and the message is using version 1.0. When the server has completed the work requested by this transaction, it sends one of two possible responses:

[0151] SETUPACK 1X64193 v1.0; <other stuff>or

[0152] SETUPNAK 1X64193 v1.0; <other stuff>.

[0153] The server must store all requests it receives for some period of time (30 seconds). The server must also store its responses for some period of time (30 seconds) in case they were lost in transmission and need to be resent.

[0154] If a client sends a request but does not receive a response within a reasonable time (which may vary based on message type), it resends the original request, without any modification.

[0155] If a server receives a request message that it recognizes as a duplicate (same source, same transaction identifier, same message type, not necessary to compare message content), it either resends its response, if the response has been completed, or sends a pseudo-response:

[0156] WORKING 1X64193 v1.0;

[0157] The receipt of a WORKING message at the client indicates that the server has received the message, and the response has not yet been sent. It is reasonable for the client to use a longer timer before resending the request again.

[0158] In some situations, e.g. the SETUP message, it is possible that the normal processing time may exceed the timeout period of the client. In that case the server can immediately send the WORKING pseudo-response upon receipt of a request.

[0159] Typical timeouts that seem reasonable to use are:

[0160] BTI to Edge Router: 0.5 seconds initially, 1 second after WORKING response

[0161] BTI to Gate Controller: 1 second, 2 seconds after WORKING response

[0162] Gate Controller to GC: 1 second, 2 seconds after WORKING response

[0163] 7.1 BTI to Gate Controller

[0164] The BTI initiates transactions with the Gate Controller to request a new connection to a remote named endpoint, or to request some enhanced service to be performed on an existing connection. In addition to basic connections, this protocol enables all the custom calling features to be implemented, and provides conference control capability.

[0165] This protocol is designed to utilize significant intelligence in the BTI, allowing it to completely handle the user interface and to implement new custom services that build on the primitives that exist in the signaling system of embodiments of the present invention.

[0166] Messages initiated by the BTI include SETUP, REDIRECT, SPLICE, TRACE, and PROFILE. SETUP is used to initiate a new connection. REDIRECT takes an existing connection and sends it to some other destination. SPLICE takes two existing connections and connects them together. TRACE generates a law-enforcement report of an abusive or harassing call. PROFILE enables the BTI to specify custom call handling services for times when the BTI cannot be contacted (e.g. power failure).

[0167] 7.1.1 SETUP

[0168] SETUP is the basic message sent by a BTI to initiate a connection to another endpoint; an example message is:

[0169] SETUP 0S55072 v1.0; DEST E164 8766; CALLER 8718; AUTHID 3312120; CRV 21; SIGADDR wtm-bti:7685; DATAADDR wtm-bti:7000 2 2; CODING 53B,6 ms,G.711

[0170] DEST specifies the destination of this call. The first parameter in this field gives an address space name to search; valid address spaces are E164 (standard telephone numbers), CINFO (source string from a previous call), and SERVICE (generic network service by name). The second parameter gives the actual telephone number/source string/service name. Further parameters, if given, are passed through and given to the receiving endpoint. Examples of various usages of the DEST element are:

[0171] DEST E164 8766 places a new call to a phone number. Second parameter is the number in the customer's dialing plan (e.g. centrex, nanp, etc.)

[0172] DEST CINFO <string>places a return call to a previous caller, for example, *69 return call. Second parameter is the string given in a SETUP, SETUPACK, or TRANSFER.

[0173] DEST SERVICE bridge 3 places a call to a network service, in this example a bridge service for 3 parties. The second parameter is the name of the network service (e.g. bridge, announcement, etc.) and further parameters are given to that service for further interpretation.

[0174] CALLER gives the caller-id value for the line that is originating this call. The Gate Controller must verify that this caller-id is valid based on the AUTHID. Since the BTI is outside out control, we cannot be sure that the call is really coming from the line it claims; however we can ensure that the caller-id specified is one of the possible ones from this BTI.

[0175] AUTHID is the authorization code given to this particular BTI from the OAMP system. It is changed periodically, e.g. every ten minutes.

[0176] CRV is the Call Reference Value assigned for the BTI's end of this new call. The CRV appears in all messages sent to the BTI, enabling the BTI to correctly assign the message to the proper call, and to properly ignore messages that refer to previous call attempts. Note that multiple race conditions exist if a customer partially completes a call, hangs up, then places another call. The BTI needs some mechanism to ignore stale messages without the need to synchronize with all possible parties prior to processing a new customer request (e.g. give the customer another dialtone).

[0177] SIGADDR is the IP system name and port number that the called endpoint should use as a destination for all BTI-BTI messages. This may be the same address and port as is used by the Gate Controller to signal an incoming call, or it may be a separate port for the current call only. If it is the same port, then it is necessary to structure the messages such that the BTI can distinguish GC-BTI messages from BTI-BTI messages, which this v1.0 design does.

[0178] DATAADDR is the IP system name and port specification that the called endpoint should use as a destination for all voice data packets. The first parameter is a system-name:port-number, where the port number is the lowest port number in a set of consecutive ports. The second parameter gives the size of the set of consecutive ports. The third parameter, if present, gives any alignment requirements of the port numbers if it is necessary to translate them in a PAT server. A typical voice-only telephone call will use two ports, the first for RTP and the second for RTCP, and will require that the first port be even.

[0179] CODING specifies a list of possible encapsulations and coding methods that the originator will perform. Each parameter is at least three items separated by commas, where the first item specifies a message size, the second item gives the interval between packets, the third item gives the coding algorithm, and fourth and later items (optional) give additional parameters specific to the coder.

[0180] 7.1.1.1 SETUP Acknowledgment

[0181] The response to a SETUP message is SETUPACK or SETUPNAK. A sample SETUPACK message is:

[0182] SETUPACK 0S55072 v1.0; CRV 3712;

[0183] SIGADDR 10.0.0.1:5134; DATAADDR 10.0.0.1:5136 2;

[0184] CODING 53B,6 ms,G.71 1; GATEIP 135.207.31.1:7682; GATEID 17S63224; CINFO <string>

[0185] CRV gives the Call Reference Value assigned by the remote endpoint to identify all messages associated with the conversation. It must be included in all BTI-BTI messages.

[0186] SIGADDR gives the address and port to use as a destination for all BTI-BTI signaling messages.

[0187] DATAADDR gives the address and ports to use as a destination for all voice data packets. The second parameter gives the number of consecutive ports allocated for this purpose.

[0188] CODING gives the single encapsulation and coding method, of the choices presented in the

[0189] SETUP message, that is acceptable to the destination BTI. Format of the parameter is identical to that given above.

[0190] GATEIP gives the IP address and port number of the Edge Router that contains the gate controlling access service for this connection. This is the destination address to use for all BTI-ER messages.

[0191] GATEID gives the identification and authorization token assigned by the Edge Router for the gate allocated for this connection.

[0192] CINFO is an encrypted string of information from the Gate Controller, containing a number of items of state information needed by the Gate Controller to properly handle any future requests for advanced features for this call, e.g. 3-way calling, return call, transfer, etc. It must be stored unaltered by the BTI and returned to the Gate Controller unaltered for any of these features.

[0193] 7.1.1.2 SETUP Error

[0194] If the SETUP fails, the Gate Controller will return an error indication to the BTI. A sample SETUPNAK message is:

[0195] SETUPNAK 0S55072 v1.0; ERROR Authorization failed

[0196] ERROR gives an error message string, which could be displayed if the BTI has some method to do so. Otherwise it provides some useful debugging information.

[0197] Other elements in the SETUPNAK message are TBD.

[0198] 7.1.2 REDIRECT

[0199] The BTI sends a REDIRECT message to its Gate Controller when it wants a current call to be directed to some other destination. A sample REDIRECT message is:

[0200] REDIRECT 0S42115 v1.0; DEST E164 8720; CALLER 8766; AUTHID 6929022;

[0201] CINFO

[0202] 135.207.31.2:7650/135.207.31.1:7682/17S63224/10.0.12.221:7685/10.0.12.221:7000-2-2/9733608718/21/10.0.12.221:7685

[0203] DEST gives the new desired destination of this call. It may be either an E164 number, a service name, or a CINFO string, just as in the SETUP message.

[0204] CALLER gives the caller-id value for the line that is making the request. The Gate Controller must verify that this caller-id is valid based on the AUTHID. Since the BTI is outside our control, we cannot be sure that the call is really coming from the line it claims; however we can ensure that the caller-id specified is one of the possible ones from this BTI.

[0205] AUTHID is the authorization code given to this particular BTI from the OAMP system. It is changed periodically, e.g. every ten minutes.

[0206] CINFO is the encrypted string previously supplied by the Gate Controller, which tells the Gate Controller various pieces of information about the current call.

[0207] 7.1.2.1 REDIRECT Acknowledgment

[0208] If the Gate Controller is successful in directing the call to the new destination, it will respond with a REDIRECTACK message. A sample is:

[0209] REDIRECTACK 0S42115 v1.0;

[0210] 7.1.2.2 REDIRECT Error

[0211] If the REDIRECT fails, the Gate Controller will return an error indication to the BTI. A sample REDIRECTNAK message is:

[0212] REDIRECTNAK 0S55072 v1.0; ERROR Authorization failed

[0213] ERROR gives an error message string, which could be displayed if the BTI has some method to do so. Otherwise it provides some useful debugging information.

[0214] Other elements in the REDIRECTNAK message are TBD.

[0215] 7.1.3 SPLICE

[0216] The BTI sends a SPLICE message to its Gate Controller when it wants two current calls to be connected together. A sample SPLICE message is:

[0217] SPLICE 0S42161 v1.0; CALLER 8766; AUTHID 6929022;

[0218] CINFO1

[0219] 135.207.31.2:7650/135.207.31.1:7682/17S63224/10.0.12.221:7685/10.0.12.221:7000-2-2/9733608718/21/10.0.12.221:7685;

[0220] CINF02

[0221] 135.207.31.2:7650/135.207.22.1:7682/5S71731/10.3.7.150:7685/10.3.7.150:7000-2-2/9733608720/8839/10.3.7.150:7685

[0222] CALLER gives the caller-id value for the line that is making the request. The Gate Controller must verify that this caller-id is valid based on the AUTHID. Since the BTI is outside our control, we cannot be sure that the call is really coming from the line it claims; however we can ensure that the caller-id specified is one of the possible ones from this BTI.

[0223] AUTHID is the authorization code given to this particular BTI from the OAMP system. It is changed periodically, e.g. every ten minutes.

[0224] CINFO1 is the encrypted string previously supplied by the Gate Controller, which tells the Gate Controller various pieces of information about the first call.

[0225] CINFO2 is the encrypted string previously supplied by the Gate Controller, which tells the Gate Controller various pieces of information about the second call.

[0226] 7.1.3.1 SPLICE Acknowledgment

[0227] If the Gate Controller is successful in directing the two calls to each other, it will respond with a SPLICEACK message. A sample is:

[0228] SPLICEACK 0S42161 v1.0;

[0229] 7 .1.3.2 SPLICE Error

[0230] If the SPLICE fails, the Gate Controller will return an error indication to the BTI. A sample SPLICENAK message is:

[0231] SPLICENAK 0S55072 v1.0; ERROR Authorization failed

[0232] ERROR gives an error message string, which could be displayed if the BTI has some method to do so. Otherwise it provides some useful debugging information.

[0233] Other elements in the SPLICENAK message are TBD.

[0234] 7.1.4 TRACE

[0235] The BTI sends a TRACE message to its Gate Controller when it to report an abusive or harassing phone call to law enforcement. A sample TRACE message is:

[0236] TRACE 0S42115 v1.0; CALLER 8766; AUTHID 6929022;

[0237] CINFO

[0238] 135.207.31.2:7650/135.207.31.1:7682/17S63224/10.0.12.221:7685/10.0.12.221:7000-2-2/9733608718/21/10.0.12.221:7685

[0239] CALLER gives the caller-id value for the line that is making the request. The Gate Controller must verify that this caller-id is valid based on the AUTHID. Since the BTI is outside our control, we cannot be sure that the call is really coming from the line it claims; however we can ensure that the caller-id specified is one of the possible ones from this BTI.

[0240] AUTHID is the authorization code given to this particular BTI from the OAMP system. It is changed periodically, e.g. every ten minutes.

[0241] CINFO is the encrypted string previously supplied by the Gate Controller, which tells the Gate Controller various pieces of information about the call.

[0242] 7.1.4.1 TRACE Acknowledgment

[0243] If the information in the TRACE message is valid, the Gate Controller will respond with a TRACEACK message. A sample message is:

[0244] TRACEACK 0S42115 v1.0;

[0245] 7.1.4.2 TRACE Error

[0246] If the TRACE fails, the Gate Controller will return an error indication to the BTI. A sample TRACENAK message is:

[0247] TRACENAK 0S55072 v1.0; ERROR Authorization failed

[0248] ERROR gives an error message string, which could be displayed if the BTI has some method to do so. Otherwise it provides some useful debugging information.

[0249] Other elements in the TRACENAK message are TBD.

[0250] 7.1.5 PROFILE

[0251] To be provided.

[0252] 7.1.5.1 PROFILE Acknowledgment

[0253] To be provided.

[0254] 7.1.5.2 PROFILE Error

[0255] If the PROFILE fails, the Gate Controller will return an error indication to the BTI. A sample PROFILENAK message is:

[0256] PROFILENAK 0S55072 v1.0; ERROR Authorization failed

[0257] ERROR gives an error message string, which could be displayed if the BTI has some method to do so. Otherwise it provides some useful debugging information.

[0258] Other elements in the PROFILENAK message are TBD.

[0259] 7.2 Gate Controller to BTI

[0260] The Gate Controller initiates messages to the BTI to inform it of incoming calls, or to inform it of a change in the status of an existing call.

[0261] Messages initiated by the Gate Controller include SETUP, TRANSFER, and CALLHOLD. SETUP is used to inform the BTI of an incoming call, and to ask the BTI the proper handling of this new call request. TRANSFER informs the BTI that a current call has been redirected to a new destination. CALLHOLD informs the BTI that the call has been placed on hold and to temporarily release the resources used by this call.

[0262] 7.2.1 SETUP

[0263] The Gate Controller informs a BTI of an incoming call request with a SETUP message. A sample message is:

[0264] SETUP 4T93182 v1.0; DEST 9733608766; CALLER 9733608718; CRV 21; SIGADDR 10.0.0.1:4722; DATAADDR 10.0.0.1:4724 2 2; CODING 53B,6 ms,G.7 11; GATEIP 135.207.22.1:7682; GATEID 21S11018; CINFO <string>

[0265] DEST is the destination E1 64 address, as given by the originator and expanded to a global addressing plan by the Gate Controller.

[0266] CALLER (optional) is the caller-id information. This element is only present if the customer has subscribed to some variant of caller-id service. If the customer has subscribed to calling name service as well, the second parameter will contain the name of the caller. If the originator of the call has specified caller-id blocking, the first parameter will contain “anonymous.”

[0267] CRV is the Call Reference Value assigned by the destination for this call. It must be included in all BTI-BTI messages to properly identify the call.

[0268] SIGADDR gives the address and port number for the destination of all BTI-BTI signaling messages.

[0269] DATAADDR gives the address and port number for the destination of voice data packets. The second parameter (optional) gives the number of consecutive ports allocated. The third parameter (optional) gives the alignment information for the port numbers.

[0270] CODING specifies a list of possible encapsulations and coding methods that the originator will perform. Each parameter is at least three items separated by commas, where the first item specifies a message size, the second item gives the interval between packets, the third item gives the coding algorithm, and fourth and later items (optional) give additional parameters specific to the coder.

[0271] GATEIP gives the IP address and port number of the Edge Router that contains the gate controlling access service for this connection. This is the destination address to use for all BTI-ER messages.

[0272] GATEID gives the identification and authorization token assigned by the Edge Router for the gate allocated for this connection.

[0273] CINFO is an encrypted string containing internal state information of the Gate Controller, which is to be stored in the BTI and returned with any future enhanced service request related to this call, e.g. 3-way calling, call transfer, etc.

[0274] 7.2.1.1 SETUP Acknowledgment

[0275] If the BTI is willing to accept the incoming call specified in the SETUP message, it responds with SETUPACK. A sample SETUPACK message is:

[0276] SETUPACK 4T93182 v1.0; CRV 2712; SIGADDR kkrama-bti:7685; DATAADDR kkrama-bti:7000 2 2; CODING 53B,6 ms,G.711

[0277] CRV is the Call Reference Value assigned by the BTI for this call. It is the value that will appear in all BTI-BTI messages to identify the specific call instance.

[0278] SIGADDR is the address and port number where the BTI will listen for BTI-BTI signaling messages.

[0279] DATAADDR is the address and port numbers where the BTI will accept voice data packets. The second parameter indicates the number of consecutive ports, and the third parameter gives the alignment necessary if the part numbers are translated by a PAT server.

[0280] CODING is the encapsulation style and coding method chosen from those offered.

[0281] 7.2.1.2 SETUP Error

[0282] If the BTI is not willing to accept the incoming call, it responds with SETUPNAK. A sample SETUPNAK message is:

[0283] SETUPNAK 4T93182 v1.0; ERROR Busy; FORWARD E164 8800

[0284] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the originating BTI in a SETUPNAK message.

[0285] FORWARD gives the new destination that the call should be directed to, as a result of the call forwarding algorithm implemented within the BTI. The structure of this element is identical to that of the DEST element of the BTI-GC SETUP message.

[0286] Other elements in the message are TBD.

[0287] 7.2.2 TRANSFER

[0288] The TRANSFER messages is used by the Gate Controller to inform the BTI of a change in destination of an existing call. The BTI must alter some destination parameters to communicate with this new destination. A sample TRANSFER message is:

[0289] TRANSFER OT5087 v1.0; CRV 21; REMCRV 1025; SIGADDR 135.207.31.3:6026; DATAADDR 135.207.31.3:6028 2; CODING 53B,6 ms,G.711; ROLE orig;

[0290] CINFO <string>

[0291] CRV gives the Call Reference Value of the call that has been transferred. This parameter is intended to help the BTI determine the proper adjustments.

[0292] REMCRV is the Call Reference Value assigned by the party at the other end of the call. This value must be used in all BTI-BTI communication.

[0293] SIGADDR is the IP address and port for BTI-BTI signaling messages to the other endpoint.

[0294] DATAADDR is the IP address and UDP port specification for voice data packets. The second parameter, if present, gives the number of consecutive port numbers assigned for this connection. The third parameter, if present, tells any alignment necessary for the port numbers.

[0295] CODING tells the encapsulation scheme and coding method to use for this connection.

[0296] ROLE tells whether the BTI should consider itself the originator or terminator of this conversation.

[0297] CINFO is an encrypted string of information about the other end of the conversation, to be stored in the BTI, for use for future enhanced services that may be requested.

[0298] 7.2.2.1 TRANSFER Acknowledgment

[0299] If the BTI is able to identify the call given in the TRANSFER message, adjust its internal state, and allocate resources to the new destination, it responds with TRANSFERACK. A sample TRANSFERACK message is:

[0300] TRANSFERACK 0T5087 v1.0;

[0301] 7.2.2.2 TRANSFER Error

[0302] If the BTI is not willing to accept the transferred call, it responds with TRANSFERNAK. A sample TRANSFERNAK message is:

[0303] TRANSFERNAK 0T5087 v1.0; ERROR Resource reservation to new destination failed

[0304] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the originating system in a NAK message.

[0305] Other elements in the message are TBD.

[0306] 7.2.3 CALLHOLD

[0307] The BTI must be placed on hold while gate adjustments are performed. In most cases this is handled by the BTI-BTI HOLD message. In some situations, it must be done by the Gate Controller, and is performed by issuing the CALLHOLD message. A sample CALLHOLD message is:

[0308] CALLHOLD 2T10477 v1.0; CRV 21

[0309] CRV is the Call Reference Value assigned by the BTI for this conversation.

[0310] 7.2.3.1 CALLHOLD Acknowledgment

[0311] After the BTI has placed itself in a hold status, it responds with CALLHOLDACK. A sample CALLHOLDACK message is:

[0312] CALLHOLDACK 2T10477 v1.0;

[0313] 7.2.3.2 CALLHOLD Error

[0314] If the BTI is not able to process the HOLD request, it responds with CALLHOLDNAK. A sample CALLHOLDNAK message is:

[0315] CALLHOLDNAK 2T10477 v1.0; ERROR Illegal Call Reference Value ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the originating system in a NAK message.

[0316] 7.3 BTI to Edge Router

[0317] Resource allocation messages are exchanged between the BTI and the Edge Router for reservation and release of network resources. These messages all have a reference to a “Gate,” which must have been initialized by a Gate Controller prior to the BTI's resource reservation request.

[0318] Messages initiated by the BTI include RESERVE, COMMIT, RERESERVE, RECOMMIT, RELEASE, HOLD, and KEEPALIVE. RESERVE is the normal first step in the reservation protocol, where it requests an allocation of resources but does not require them to be assigned. COMMIT requests the actual assignment of resources to this conversation. RERESERVE is used in cases where the BTI already has some resources either reserved or committed to it and is willing to use them to satisfy this new request. RECOMMIT serves a similar function when the resources are to be committed to this new connection. RELEASE is the indication from the BTI that a connection should be terminated. HOLD indicates to the Edge Router that the voice data stream is temporarily stopping, and to stop monitoring the data stream, but to maintain the resources as reserved. KEEPALIVE is sent periodically (interval TBD) in the held state to the Edge Router to maintain the resource reservation; a lack of keepalives indicates a (probably undesirable) call termination.

[0319] 7.3.1 RESERVE

[0320] The RESERVE message is sent by the BTI in the first stage of resource allocation. A sample RESERVE message is:

[0321] RESERVE 0S55073 v1.0; GATEID 17S63224; BANDWIDTH 53B,6 ms

[0322] GATEID is the identification of the gate, as assigned by the Edge Router. Included in this string is the security authorization that indicates the sender is allowed to perform operations on this gate.

[0323] BANDWIDTH is the specification of the actual bandwidth desired at this time. It is specified as packet size, in bytes, and inter-packet interval. The details of the algorithm for comparing this to the specification given by the Gate Controller in the GATESETUP message is TBD.

[0324] 7.3.1.1 RESERVE Acknowledgment

[0325] If the resource reservation is successful, meaning bandwidth is available both upstream and downstream in the access network, and bandwidth is available in the forward direction in the backbone network, the Edge Router responds with a RESERVACK message. A sample message is:

[0326] RESERVEACK 0S55073 v1.0;

[0327] 7.3.1.2 RESERVE Error

[0328] If the resource reservation fails, the Edge Router responds with a RESERVENAK message. A sample message is:

[0329] RESERVENAK 0S55073 v1.0; ERROR No upstream capacity available ERROR gives an error message string, which could be displayed if the BTI has some method to do so, or can simply result in a fast busy signal.

[0330] Other elements in the message are TBD.

[0331] 7.3.2 COMMIT

[0332] The COMMIT message is sent by the BTI in the second stage of resource allocation. On receipt of a COMMIT message, the Edge Router resets the gate timer to a smaller interval (approximately 2 seconds, exact value TBD). If that timer expires before the COMMITACK is sent, the gate is terminated. A sample COMMIT message is:

[0333] COMMIT 0S55074 v1.0; GATEID 17S63224; BANDWIDTH 53B,6 ms

[0334] GATEID is the identification of the gate, as assigned by the Edge Router. Included in this string is the security authorization that indicates the sender is allowed to perform operations on this gate.

[0335] BANDWIDTH is the specification of the actual bandwidth desired at this time. It is specified as packet size, in bytes, and inter-packet interval. The details of the algorithm for comparing this to the specification given by the Gate Controller in the GATESETUP message is TBD. The value given in the COMMIT can be no greater than that from the RESERVE message; again the comparison method is TBD.

[0336] 7.3.2.1 COMMIT Acknowledgment

[0337] If the resource allocation is successful, meaning bandwidth has been allocated in the access network (e.g. via unsolicited grants), and the Edge Router has successfully coordinated with its remote Edge Router at the other end of the call, the Edge Router responds with a COMMITACK message. A sample message is:

[0338] COMMITACK 0S55074 v1.0;

[0339] 7.3.2.2 COMMIT Error

[0340] If the resource allocation fails, or the coordination with the remote gate does not complete within the allotted interval, the Edge Router responds with a COMMITNAK message. It is intended that this be a very infrequent event, since it results in the caller hearing first a ringback tone, then turning into a failure tone. Such call defects are limited by the service description to only a few per million completed calls, although deliberate cases of fraud causing this error are not counted. A sample message is:

[0341] COMMITNAK 0S55074 v1.0; ERROR Gate coordination failure

[0342] ERROR gives an error message string, which could be displayed if the BTI has some method to do so, or can simply result in a fast busy signal.

[0343] Other elements in the message are TBD.

[0344] 7.3.3 RERESERVE

[0345] The RERESERVE message is sent by the BTI in the first stage of resource allocation when the BTI has a current allocation that the new connection will be re-using. See Section xx.xx for information about the two stage resource allocation scheme. A sample RERESERVE message is:

[0346] RERESERVE 0S42110 v1.0; GATEID 5S71731; PREVGATEID 21S11018; BANDWIDTH 53B,6 ms

[0347] GATEID is the identification of the gate, as assigned by the Edge Router. Included in this string is the security authorization that indicates the sender is allowed to perform operations on this gate.

[0348] PREVGATEID is the identification of an existing, committed gate, whose resources will be re-used in the current connection.

[0349] BANDWIDTH is the specification of the actual bandwidth desired at this time. It is specified as packet size, in bytes, and inter-packet interval. The details of the algorithm for comparing this to the specification given by the Gate Controller in the GATESETUP message is TBD.

[0350] 7.3.3.1 RERESERVE Acknowledgment

[0351] If the resource re-reservation is successful, meaning bandwidth is available both upstream and downstream in the access network, and bandwidth is available in the forward direction in the backbone network, the Edge Router responds with a RERESERVACK message. A sample message is:

[0352] RESERVEACK 0S42110 v1.0;

[0353] 7.3.3.2 RERESERVE Error

[0354] If the resource re-reservation fails, the Edge Router responds with a RERESERVENAK message. A sample message is:

[0355] RERESERVENAK 0S42110 v1.0; ERROR Illegal previous gate identifier

[0356] ERROR gives an error message string, which could be displayed if the BTI has some method to do so, or can simply result in a fast busy signal.

[0357] Other elements in the message are TBD.

[0358] 7.3.4 RECOMMIT

[0359] The RECOMMIT message is sent by the BTI in the second stage of resource allocation when a previous allocation is to be re-used. See Section xx.xx for information about the two stage resource allocation scheme. On receipt of a RECOMMIT message, the Edge Router resets the gate timer to a smaller interval (approximately 2 seconds, exact value TBD). If that timer expires before the RECOMMITACK is sent, the gate is terminated. A sample RECOMMIT message is:

[0360] RECOMMIT 0S42111 v1.0; GATEID 5S71731; PREVGATEID 21S11018; BANDWIDTH 53B,6 ms

[0361] GATEID is the identification of the gate, as assigned by the Edge Router. Included in this string is the security authorization that indicates the sender is allowed to perform operations on this gate.

[0362] PREVGATEID is the identification of an existing, committed gate, whose resources may be re-used in the current connection.

[0363] BANDWIDTH is the specification of the actual bandwidth desired at this time. It is specified as packet size, in bytes, and inter-packet interval. The details of the algorithm for comparing this to the specification given by the Gate Controller in the GATESETUP message is TBD. The value given in the COMMIT can be no greater than that from the RESERVE message; again the comparison method is TBD.

[0364] 7.3.4.1 RECOMMIT Acknowledgment

[0365] If the resource allocation is successful, meaning bandwidth has been allocated in the access network (e.g. via unsolicited grants), and the Edge Router has successfully coordinated with its remote Edge Router at the other end of the call, the Edge Router responds with a RECOMMITACK message. A sample message is:

[0366] RECOMMITACK 0S42111 v1.0;

[0367] 7.3.4.2 RECOMMIT Error

[0368] If the resource allocation fails, or the coordination with the remote gate does not complete within the allotted interval, the Edge Router responds with a RECOMMITNAK message. It is intended that this be a very infrequent event, since it results in the caller hearing first a ringback tone, then turning into a failure tone. Such call defects are limited by the service description to only a few per million completed calls, although deliberate cases of fraud causing this error are not counted. A sample message is:

[0369] RECOMMITNAK 0S42111 v1.0; ERROR Gate coordination failure

[0370] ERROR gives an error message string, which could be displayed if the BTI has some method to do so, or can simply result in a fast busy signal.

[0371] Other elements in the message are TBD.

[0372] 7.3.5 RELEASE

[0373] The BTI sends the RELEASE message to the Edge Router when the call has completed, and the resources are to be released and billing is to stop. A sample message is:

[0374] RELEASE 0S55075 v1.0; GATEID 17S63224

[0375] GATEID is the identification of the gate that was assigned for this conversation, and which is now to be released.

[0376] 7.3.5.1 RELEASE Acknowledgment

[0377] The Edge Router always responds to a RELEASE message with RELEASEACK. If a gate existed with the indicated identification, then it is closed, its resources released, a billing event is generated, and a GATECLOSE message is sent to the corresponding Edge Router at the other end of the connection.

[0378] A sample message is:

[0379] RELEASEACK 0S55075 v1.0;

[0380] 7.3.5.2 RELEASE Error

[0381] The Edge Router always responds to a RELEASE with a RELEASEACK. There are no error indications generated. If the gate identification does not exist, the Edge Router assumes the gate has already been closed by the remote end.

[0382] 7.3.6 HOLD

[0383] If the BTI wants to place a current call on hold, it must inform the Edge Router that its upstream data stream will stop. Otherwise, the Edge Router will interpret the lack of data as a hangup indication and terminate the call. This is done by a HOLD message. A sample message is:

[0384] HOLD 0S55090 v1.0; GATEID 17S63224

[0385] GATEID is the identification of the gate, as assigned by the Edge Router. Included in this string is the security authorization that indicates the sender is allowed to perform operations on this gate.

[0386] 7.3.6.1 HOLD Acknowledgment

[0387] If the hold operation is successful, meaning bandwidth has been placed back in the pool of reserved but not yet committed, the Edge Router responds with a HOLDACK message. A sample message is:

[0388] HOLDACK 0S55090 v1.0;

[0389] 7.3.6.2 HOLD Error

[0390] If the hold operation fails the Edge Router responds with a HOLDNAK message. A sample message is:

[0391] HOLDNAK 0S55090 v1.0; ERROR Gate not yet committed

[0392] ERROR gives an error message string, which could be displayed if the BTI has some method to do so, or can simply result in a fast busy signal.

[0393] Other elements in the message are TBD.

[0394] 7.3.7 KEEPALIVE

[0395] While having a connection on hold, it is necessary for the BTI to periodically inform the Edge Router that it is still alive and healthy, and that the reservation should be maintained. Lack of any traffic from the BTI is taken as evidence that the BTI has failed, or that some access component has failed and that the BTI is unable to request a call termination. The safe strategy is to terminate the call, rather than possibly charge the customer for a length service outage. A sample KEEPALIVE message is:

[0396] KEEPALIVE 21C3972 v1.0; GATEID 17S63224

[0397] GATEID is the identification of the gate, as assigned by the Edge Router. Included in this string is the security authorization that indicates the sender is allowed to perform operations on this gate.

[0398] There is no error control or retransmission of KEEPALIVE messages. The interval between them is engineered to minimize the chances of false error detection.

[0399] 7.4 Edge Router to BTI

[0400] No messages are initiated by the Edge Router.

[0401] 7.5 BTI to BTI

[0402] There are various end-to-end messages that are exchanged in any signaling system, which are used to coordinate the state of the two endpoints in providing consistent service. In embodiments of the present invention these are implemented as BTI-BTI signaling messages, are sent directly between the two BTIs involved in the conversation. These are formatted such that they can be processed by the same subroutines as the other messages. Messages exchanged between BTIs include RING, RINGBACK, CONNECT, HANGUP, HOLD, and RINGTIMEOUT. RING is sent from the originator to the destination to indicate that all appears ready and that the destination should ring the phone. RINGBACK is sent from the destination to the originator to indicate that the phone is ringing. CONNECT is sent from the destination to the originator when the called party answers the phone, or immediately after receipt of RING is the called party is ready. HOLD is sent from either BTI to the other to indicate the call will be placed on hold and to release any real-time resources currently held. HANGUP and RINGTIMEOUT are informational messages to indicate state information that the BTI will receive by other mechanisms as well.

[0403] 7.5.1 RING

[0404] The RING message is sent by the originating BTI when it has received the acknowledgment from its Edge Router that resources are available for the call, and therefore it is time to alert the destination user. A sample message is:

[0405] RING 3712 v1.0; CRV 3712

[0406] CRV (optional) is the Call Reference Value assigned by the destination BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0407] The acknowledgment of RING is either RINGBACK or CONNECT, not a separate RINGACK message.

[0408] 7.5.2 RINGBACK

[0409] When a terminating BTI has completed the resource reservation sequence, and has received a RING message from the originating BTI, its proper response is either RINGBACK or CONNECT. RINGBACK is sent if the destination is not yet ready to receive the call, and that the BTI is ringing the phone. CONNECT means the destination is ready now, and that no ringing is needed (e.g. a voice response system). A sample message is:

[0410] RINGBACK 21 v1.0; CRV 21; SOURCE local; TYPE callwaiting

[0411] CRV (optional) is the Call Reference Value assigned by the originating BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0412] SOURCE (optional) specifies whether the audible ringback tone is to be generated locally by the originating BTI, or whether the destination will generate the tone utilizing the data stream. Due to the resource reservation scheme, SOURCE specified as “remote” can only occur when the destination is a trusted network element that does not need a gate to control access to the network. If not specified, ringback tone is generated locally by the BTI.

[0413] TYPE (optional) specifies one of several possible ringback audio sequences. Parameter value “callwaiting” means the special tone sequence indicating the callwaiting alert signal has been given. If the parameter is not given, or not understood, it defaults to “normal”.

[0414] There is no explicit acknowledgment to RINGBACK. However, if the originating BTI does not receive either RINGBACK or CONNECT in response to its RING message, it will retransmit the RING until a response is received.

[0415] 7.5.3 CONNECT

[0416] The CONNECT message is sent by the terminating BTI when the user has answered and the connection should be established. A sample message is:

[0417] CONNECT 21 v1.0; CRV 21

[0418] CRV (optional) is the Call Reference Value assigned by the originating BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0419] Acknowledgment of the CONNECT message occurs via the COMMIT/COMMITACK exchange with the Edge Router.

[0420] 7.5.4 HANGUP

[0421] This is an information message that is sent by either BTI to the other one to indicate the user is terminating the connection. A sample message is:

[0422] HANGUP 3712 v1.0; CRV 3712

[0423] CRV (optional) is the Call Reference Value assigned by the originating BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0424] There is no acknowledgment of the HANGUP message. There are multiple independent mechanisms that determine that a call has completed and will terminate the billing; since the system must recover from access link failures, BTI hardware/software failures, and power failures, each of which may prevent the BTI from sending the HANGUP message. Therefore its use is not critical.

[0425] 7.5.5 HOLD

[0426] If the BTI wants to place a current call on hold, it must inform the other endpoint that its incoming data stream will stop. Otherwise, the other endpoint will interpret the lack of data as a hangup indication and terminate the call. This is done by a HOLD message. A sample message is:

[0427] HOLD 21 v1.0; CRV 21

[0428] CRV (optional) is the Call Reference Value assigned by the originating BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0429] Note that before stopping the data stream, the BTI must also inform its Edge Router that the data stream will stop, else the Edge Router will terminate the call. This is done via a BTI-ER HOLD message.

[0430] 7.5.5.1 HOLD Acknowledgment

[0431] When a BTI has received a HOLD message from the other endpoint, it adjusts its threshold for considering the connection dead, and responds with the acknowledgment. This message is:

[0432] HOLDACK 3712 v1.0; CRV 3712

[0433] CRV (optional) is the Call Reference Value assigned by the originating BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0434] 7.5.6 RING TIMEOUT

[0435] This is an information message that is sent by the terminating BTI to the originator to indicate the user has not answered within the interval they configured, and that the call will be forwarded. A sample message is:

[0436] RINGTIMEOUT 3712 v1.0; CRV 3712

[0437] CRV (optional) is the Call Reference Value assigned by the originating BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0438] There is no error recovery for this message. It is informational only, and serves to tell the originating BTI to stop the ringback tone, and that a transfer is imminent. Without this message the originating BTI will still receive a TRANSFER message from the Gate Controller and handle the call in the same way.

[0439] 7 .5.7 RESOURCECHANGE

[0440] TBD

[0441] 7.5.8 KEEPALIVE

[0442] While having a connection on hold, it is necessary for the BTI to periodically inform its peer BTI that it is still alive and healthy, and that the connection should be maintained. Lack of any traffic from the BTI is taken as evidence that the BTI has failed, or that some access component has failed and that the BTI is unable to request a call termination. The safe strategy is to terminate the call, rather than possibly charge the customer for a length service outage. A sample KEEPALIVE message is:

[0443] KEEPALIVE 3712 v1.0; CRV 3712

[0444] CRV (optional) is the Call Reference Value assigned by the other BTI. It must appear in the message, but may appear either as the transaction identifier, or as a separate element.

[0445] There is no error control or retransmission of KEEPALIVE messages. The interval between them is engineered to minimize the chances of false error detection.

[0446] 7.6 Gate Controller to Edge Router

[0447] The protocol between the Gate Controller and Edge Router is for purposes of resource control and resource allocation policy. The Gate Controller implements all the allocation policies, and uses that information to manage the set of gates implemented in the Edge Routers. The Gate Controller initializes the gates with specific source, destination, and bandwidth restrictions; once initialized the BTI is able to request resource allocations within the limits imposed by the Gate Controller.

[0448] Messages initiated by the Gate Controller include GATEALLOC, GATESETUP, GATEMODIFY, GATERELEASE, and GATEINFO. GATEALLOC allocates a new gate identifier. GATESETUP initializes all the policy and traffic parameters for the gate, and sets the billing information. GATEMODIFY is used to change any or all of the parameters of an existing gate. GATERELEASE signals the end of the connection, and that the gate and all its resources can be made available to any other requester. GATEINFO is a mechanism by which the Gate Controller can find out all the current state and parameter settings of an existing gate.

[0449] 7.6.1 GATEALLOC

[0450] A GATEALLOC message is sent by the Gate Controller to allocate a new gate, and establish a GateID, but without setting any of the specific parameters needed for gate operation. A GATESETUP must come later with the operation parameters. On receipt of a GATEALLOC, the Edge Router starts a timer (approximately 120 seconds, exact value TBD), and if the gate has not entered the “commit” state in that time it is released. A sample GATEALLOC message is:

[0451] GATEALLOC 4T93176 v1.0; OWNER wtm-bti:7685

[0452] OWNER specifies the name of the customer this gate will serve.

[0453] 7.6.1.1 GA TEALLOC Acknowledgment

[0454] A sample GATEALLOC message is:

[0455] GATEALLOCACK4T93176 v1.0; GATEID 17S63224; CUSTUSAGE 3

[0456] GATEID is the string that identifies the gate that was allocated. It consists of at least two parts, with some (edge-router-specified) separator between them: the identity of the gate that was allocated, and a security code that must be given to the Edge Router in order to affect any change in the gate parameters.

[0457] CUSTUSAGE tells the Gate Controller the number of simultaneous gates the customer has currently. This is calculated by a scan of all current gates, comparing the OWNER parameter. If the number of gates assigned to a customer is inconsistent with the service subscribed, the Gate Controller can take appropriate action.

[0458] 7.6.1.2 GATEALLOC Error

[0459] Errors in allocating gates are reported by a GATEALLOCNAK message. A sample is:

[0460] GATEALLOCNAK 4T93176 v1.0; ERROR No gates available

[0461] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message.

[0462] Other elements in the message are TBD.

[0463] 7.6.2 GATESETUP

[0464] The GATESETUP message is sent by the Gate Controller to the Edge Router to initialize the operational parameters of the gate. A sample GATESETUP message is:

[0465] GATESETUP 4T93181 v1.0; OWNER kkrama-bti:7685;

[0466] SRCIP 10.3.7.151; DESTIP 10.0.0.1:4724; BANDWIDTH 53B,6 ms,G.711;

[0467] ROLE term; REMGATEIP 135.207.31.1:7682; REMGATEID 17S63224;

[0468] REFID 135.207.31.2:36123E5C:93178;

[0469] BILLDATA 5123-0123-4567-8900/9733608718/9733608766

[0470] OWNER (optional) gives the name of the customer this gate will serve. If this parameter is not given, then GATEID is mandatory.

[0471] GATEID (optional) gives the string that identifies the gate, with security code. If this parameter is not given, then OWNER is mandatory, and a new gate will be allocated.

[0472] SRCIP identifies the source IP address that will appear in all the data packets that go through the gate. Note that the source port number is not specified, and is generally not known or always constant.

[0473] DESTIP is the destination IP address that will appear in the IP header, and the destination UDP port number that will appear in the UDP header. Only packets that match the SourceIP/DestinationIP/DestinationPort will obtain the higher Quality of Service provided by the gate.

[0474] BANDWIDTH specifies the maximum bandwidth that maybe requested through this gate. Although the parameter includes the coding style, it is not used by the gate.

[0475] ROLE specifies whether the Edge Router is the originator or terminating side of this conversation. This has importance only if the backbone reservation is bi-directional, and only one of the Edge Routers need do the reservation.

[0476] REMGATEIP is the address of the Edge Router at the other end of this connection. All ER-ER gate coordination messages are to be sent to this address and port.

[0477] REMGATEID is the identity of the gate at the other end of the connection.

[0478] REFID is the unique string that is to appear in billing records for this conversation.

[0479] BILLDATA is the charging information that is to appear in billing records for this conversation.

[0480] 7.6.2.1 GATESETUP Acknowledgment

[0481] A sample GATESETUPACK message is:

[0482] GATESETUPACK4T93181 v1.0; GATEID 21S11018; CUSTUSAGE 1

[0483] GATEID is the string that identifies the gate that was allocated. It consists of at least two parts, with some (edge-router-specified) separator between them: the identity of the gate that was allocated, and a security code that must be given to the Edge Router in order to affect any change in the gate parameters.

[0484] CUSTUSAGE tells the Gate Controller the number of simultaneous gates the customer has currently. This is calculated by a scan of all current gates, comparing the OWNER parameter. If the number of gates assigned to a customer is inconsistent with the service subscribed, the Gate Controller can take appropriate action.

[0485] 7.6.2.2 GATESETUP Error

[0486] Errors in establishing gates are reported by a GATESETUPNAK message. A sample is:

[0487] GATESETUPNAK 4T93181 v1.0; ERROR No gates available

[0488] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message.

[0489] Other elements in the message are TBD.

[0490] 7.6.3 GATEMODIFY

[0491] The GATEMODIFY message is sent by the Gate Controller to the Edge Router to modify the operational parameters of an existing gate. A sample GATEMODIFY message is:

[0492] GATEMODIFY 2T10486 v1.0; GATEID 17S63224; SRCIP 10.3.7.151; DESTIP 10.0.0.1:4724; BANDWIDTH 53B,6 ms,G.711; ROLE term; REMGATEIP 135.207.31.1:7682; REMGATEID 17S63224; REFID 135.207.31.2:36123E5C:93178; BILLDATA 5123-0123-4567-8900/9733608718/9733608766q

[0493] GATEID gives the string that identifies the gate, with security code.

[0494] SRCIP identifies the source IP address that will appear in all the data packets that go through the gate. Note that the source port number is not specified, and is generally not known or always constant.

[0495] DESTIP is the destination IP address that will appear in the IP header, and the destination UDP port number that will appear in the UDP header. Only packets that match the SourceIP/DestinationIP/DestinationPort will obtain the higher Quality of Service provided by the gate.

[0496] BANDWIDTH specifies the maximum bandwidth that may be requested through this gate. Although the parameter includes the coding style, it is not used by the gate.

[0497] ROLE specifies whether the Edge Router is the originator or terminating side of this conversation. This has importance only if the backbone reservation is bi-directional, and only one of the Edge Routers need do the reservation.

[0498] REMGATEIP is the address of the Edge Router at the other end of this connection. All ER-ER gate coordination messages are to be sent to this address and port.

[0499] REMGATEID is the identity of the gate at the other end of the connection.

[0500] REFID is the unique string that is to appear in billing records for this conversation.

[0501] BILLDATA is the charging information that is to appear in billing records for this conversation.

[0502] 7.6.3.1 GATEMODIFY Acknowledgment

[0503] A sample GATEMODIFYACK message is:

[0504] GATEMODIFYACK 2T10486 v1.0; GATEID 17S63224; CUSTUSAGE 1

[0505] GATEID is the string that identifies the gate that was allocated. It consists of at least two parts, with some (edge-router-specified) separator between them: the identity of the gate that was allocated, and a security code that must be given to the Edge Router in order to affect any change in the gate parameters.

[0506] CUSTUSAGE tells the Gate Controller the number of simultaneous gates the customer has currently. This is calculated by a scan of all current gates, comparing the OWNER parameter. If the number of gates assigned to a customer is inconsistent with the service subscribed, the Gate Controller can take appropriate action.

[0507] 7.6.3.2 GATEMODIFY Error

[0508] Errors in modifying gates are reported by a GATEMODIFYNAK message. A sample is:

[0509] GATEMODIFYNAK 4T93181 v1.0; ERROR Illegal Gate Identification

[0510] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message.

[0511] Other elements in the message are TBD. 7.6.4 GATERELEASE

[0512] When a Gate Controller has transferred a connection, it sends a GATERELEASE message to the Edge Router to release any resources held by the endpoint that is now not part of the call. While the behavior is similar to a RELEASE message from the BTI, it results in a different event recorded in the billing system, and it avoids the normal gate coordination (as the corresponding gate at the other end of the original connection has been redirected to another destination). A sample is:

[0513] GATERELEASE 4T93181 v1.0; GATEID 17S63224

[0514] GATEID is the string that identifies the gate that was allocated. It consists of at least two parts, with some (edge-router-specified) separator between them: the identity of the gate that was allocated, and a security code that must be given to the Edge Router in order to affect any change in the gate parameters.

[0515] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message. Other elements in the message are TBD.

[0516] 7.6.4.1 GATERELEASE Acknowledgment

[0517] A GATERELEASE message always gives a response of GATERELEASEACK. A sample is:

[0518] GATERELEASEACK 4T93181 v1.0;

[0519] 7.6.4.2 GA TERELEASE Error

[0520] A GATERELEASE message always results in a response of GATERELEASEACK. If the GATEID parameter specifies an invalid gate, the Edge Router assumes the gate has already been closed.

[0521] 7.6.5 GATEINFO

[0522] When a Gate Controller wishes to find out the current parameter settings, or current state, of a gate, it sends to the Edge Router a GATEINFO message. A sample is:

[0523] GATEINFO OT5082 v1.0; GATEID 17S63224

[0524] GATEID is the string that identifies the gate that was allocated. It consists of at least two parts, with some (edge-router-specified) separator between them: the identity of the gate that was allocated, and a security code that must be given to the Edge Router in order to affect any change in the gate parameters.

[0525] 7.6.5.1 GATEINFO Acknowledgment

[0526] The message is sent by the Gate Controller to the Edge Router to modify the operational parameters of an existing gate. A sample GATEINFOACK message is:

[0527] GATEINFOACK OT5082 v1.0; GATEID 17S63224; STATE commit; SRCIP 10.3.7.151; DESTIP 10.0.0.1:4724; BANDWIDTH 53B,6 ms,G.711;

[0528] ROLE term; REMGATEIP 135.207.31.1:7682; REMGATEID 17S63224;

[0529] REFID 135.207.31.2:36123E5C:93178;

[0530] BILLDATA 5123-0123-4567-8900/9733608718/9733608766

[0531] GATEID gives the string that identifies the gate, with security code.

[0532] STATE gives the internal state of the gate, one of the following: setup, reserved, commit, or hold.

[0533] SRCIP identifies the source IP address that will appear in all the data packets that go through the gate. Note that the source port number is not specified, and is generally not known or always constant.

[0534] DESTIP is the destination IP address that will appear in the IP header, and the destination UDP port number that will appear in the UDP header. Only packets that match the SourceIP/DestinationIP/DestinationPort will obtain the higher Quality of Service provided by the gate.

[0535] BANDWIDTH specifies the maximum bandwidth that maybe requested through this gate. Although the parameter includes the coding style, it is not used by the gate.

[0536] ROLE specifies whether the Edge Router is the originator or terminating side of this conversation. This has importance only if the backbone reservation is bi-directional, and only one of the Edge Routers need do the reservation.

[0537] REMGATEIP is the address of the Edge Router at the other end of this connection. All ER-ER gate coordination messages are to be sent to this address and port.

[0538] REMGATEID is the identity of the gate at the other end of the connection.

[0539] REFID is the unique string that is to appear in billing records for this conversation.

[0540] BILLDATA is the charging information that is to appear in billing records for this conversation.

[0541] 7.6.5.2 GATEINFO Error

[0542] Errors in fetching gate information are reported by a GATEINFONAK message. A sample is:

[0543] GATEINFONAK 0T5082 v1.0; ERROR Illegal Gate Identification

[0544] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message.

[0545] Other elements in the message are TBD.

[0546] 7.7 Edge Router to Gate Controller

[0547] No messages are initiated by the Edge Router.

[0548] 7.8 Edge Router to Edge Router

[0549] In order to prevent some types of theft of service fraud, it is necessary for the Edge Routers to synchronize the gates at opposite ends of a connection. In particular, a gate that is “committed” at one end of a connection, but not at the other, can be used as a high quality data connection, or can be used to fraudulently charge an unsuspecting customer for a lengthy connection.

[0550] Messages exchanged between the Edge Routers include GATEOPEN, and GATECLOSE. GATEOPEN is exchanged with the gate has resources committed to it, and GATECLOSE is exchanged when those resources are released. Timers within the gate implementation impose strict controls on the length of time these exchanges may occupy.

[0551] 7.8.1 GATEOPEN

[0552] The GATEOPEN message is sent by the Edge Router to its corresponding Edge Router at the other end of a connection on receipt of the COMMIT message from the BTI. A sample message is:

[0553] GATEOPEN 21T6572; GATEID 17S63224; BANDWIDTH 53B,6 ms

[0554] GATEID is the identification string for the remote gate, including the security code required.

[0555] BANDWIDTH is the bandwidth request received in the COMMIT message.

[0556] 7.8.1.1 GATEOPEN Acknowledgment

[0557] On receipt of a GATEOPEN message, the Edge Router responds with a GATEOPENACK. A sample message is:

[0558] GATEOPENACK 21T6572 v1.0;

[0559] 7.8.1.2 GATEOPEN Error

[0560] If some error occurs in the processing of a GATEOPEN, the Edge Router responds with GATEOPENNAK. Such a situation can occur when the remote gate times out and releases the gate before the commit sequence completes. A sample message is:

[0561] GATEOPENNAK 21T6572 v1.0; ERROR Invalid gate identifier

[0562] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message.

[0563] Other elements in the message are TBD.

[0564] 7.8.2 GATECLOSE

[0565] The GATECLOSE message is sent by the Edge Router to its corresponding Edge Router at the other end of a connection on receipt of the RELEASE message from the BTI. The Edge Router releases any resources held by that gate, stops any unsolicited grants offered on the upstream channel, and frees the gate. A sample message is:

[0566] GATECLOSE 21T6583; GATEID 17S63224;

[0567] GATEID is the identification string for the remote gate, including the security code required.

[0568] 7.8.2.1 GATECLOSE Acknowledgment

[0569] On receipt of a GATECLOSE message, the Edge Router responds with a GATECLOSEACK. A sample message is: GATECLOSEACK 21T6583 v1.0;

[0570] 7.8.2.2 GATECLOSE Error

[0571] A GATECLOSE message always results in a response of GATECLOSEACK. If the GATEID parameter specifies an invalid gate, the Edge Router assumes the gate has already been closed.

[0572] 7.9 Gate Controller to Gate Controller

[0573] Messages exchanged between the Gate Controllers include GCSETUP, GCREDIRECT, and GCSPLICE. All occur in situations where the Gate Controller realizes that it cannot complete a request due to the destination being served by a different Gate Controller. These messages package up all the internal state, ask the remote Gate Controller to complete the desired function, then respond with the updated state information. In an implementation of the Gate Controller it is likely that these messages will exist in some internal form in order to share the implementation of call termination services.

[0574] 7.9.1 GCSETUP

[0575] The GCSETUP message is exchanged between Gate Controllers when different Gate Controllers serve the originating and terminating endpoints of a call. It is basically formed by packaging all the partial state information the originating Gate Controller has assembled, and requesting the terminating Gate Controller to complete the work necessary to initiate the connection.

[0576] A sample GCSETUP message is:

[0577] GCSETUP 4T93177 v1.0; DEST E164 9733608766; CALLER 9733608718 Bill Marshall;

[0578] CRV 21; SIGADDR 135.207.31.1:6000; DATAADDR 135.207.31.1:6002 2 2; REMGATEIP 135.207.31.1:7682; REMGATEID 17S63224;

[0579] CODING 53B,6 ms,G.71 1; REFID 135.207.31.2:36123E5C:93178; BILLDATA 5123-0123-4567-8900/9733608718/9733608766;

[0580] CINFO

[0581] 135.207.31.2:7650/135.207.31.1:7682/17S63224/10.0.12.221:7685/10.0.12.221:7000-2-2/9733608718/21/10.0.12.221:7685

[0582] DEST is the destination address for this connection. Its format is the same as in the SETUP message received from the BTI, except that the E164 number, if present, is expanded from the local numbering plan of the customer to the global numbering plan.

[0583] CALLER is the caller-id and calling name of the originator of the connection. From the SETUP message received from the BTI, the originating Gate Controller expanded the E 164 number to a global numbering plan, and looked up the calling name.

[0584] CRV is the Call Reference Value assigned by the originating BTI. Copied from the SETUP message.

[0585] SIGADDR is the IP address and port number the destination should use for BTI-BTI signaling messages. This is a global version of the address given in the SETUP message from the BTI, with name to ip-address translation done, and with any NAT/PAT server translation included.

[0586] DATAADDR is the IP address and port number the destination should use for data packets. This is a global version of the address given in the SETUP message from the BTI, with name and ip-address translation done, and with any NAT/PAT server translation included. The second and third parameters (optional) in this element give the number of consecutive ports used, and the alignment information needed for the starting port number.

[0587] REMGATEIP is the IP address and port number of the Edge Router that contains the gate to be used for this conversation. This is the destination address for all ER-ER communication.

[0588] REMGATEID is the gate identifier and security code for the gate within that Edge Router.

[0589] CODING is the offered encapsulation methods and coding styles offered by the call originator.

[0590] REFID is a unique identifier assigned by the originating Gate Controller, which will appear in all the Billing Records. The REFID is intended to be unique within a period of several months.

[0591] BILLDATA is the billing/accounting data indicating the charging arrangement for this conversation.

[0592] CINFO is a string generated by the originating Gate Controller that contains all the information needed for future enhanced services that may involve the call originator. This will be encrypted and given to the destination BTI to store. The format is a list of many items separated by slashes, or which the first is the ip address and port of the Gate Controller that built the string. Subsequent items in this string include the address/port of the Edge Router, gate identifier, signaling endpoint address, data endpoint address, the originator's call reference value, and the originator's address for initial call signaling.

[0593] 7.9.1.1 GCSETUP Acknowledgment

[0594] When the terminating Gate Controller has completed the call, it packages up all its assembled state information and passes it back to the originating Gate Controller in the GCSETUPACK message. A sample GCSETUPACK message is:

[0595] GCSETUPACK 4T93177 v1.0; CRV 3712;

[0596] SIGADDR 135.207.22.1:6142; DATAADDR 135.207.22.1:6146 2 2; REMGATEIP 135.207.22.1:7682; REMGATEID 21S11018;

[0597] CODING 53B,6 ms,G.711;

[0598] CINFO

[0599] 135.207.31.2:7650/135.207.22.1:7682/21 S11018/10.3.7.151:7685/10.3.7.151:7000-2-2/9733608766/3712/10.3.7.151:7685

[0600] CRV is the Call Reference Value assigned by the destination BTI for this conversation. It is passed transparently from the SETUPACK message from the destination BTI.

[0601] SIGADDR is the IP address and port number the originator should use for BTI-BTI signaling messages. This is a global version of the address given in the SETUPACK message from the terminating BTI, with name to ip-address translation done, and with any NAT/PAT server translation included.

[0602] DATAADDR is the IP address and port number the originator should use for data packets. This is a global version of the address given in the SETUPACK message from the terminating BTI, with name and ip-address translation done, and with any NAT/PAT server translation included. The second and third parameters (optional) in this element give the number of consecutive ports used, and the alignment information needed for the starting port number.

[0603] REMGATEIP is the IP address and port number of the Edge Router that contains the gate to be used at the terminating end for this conversation. This is the destination address for all ER-ER communication.

[0604] REMGATEID is the gate identifier and security code for the gate within that Edge Router.

[0605] CODING is the encapsulation method and coding style accepted by the call destination.

[0606] REFID (optional) is a unique identifier assigned by the Gate Controller, which will appear in all the Billing Records. The REFID is intended to be unique within a period of several months. If this parameter appears, it will override the REFID assigned by the originating Gate Controller

[0607] BILLDATA (optional) is the billing/accounting data indicating the charging arrangement for this conversation. If this parameter appears, it will override the BILLDATA assigned by the originating Gate Controller.

[0608] CINFO is a string generated by the terminating Gate Controller that contains all the information needed for future enhanced services that may involve the terminating BTI. This will be encrypted and given to the originating BTI to store. The format is a list of many items separated by slashes, or which the first is the ip address and port of the Gate Controller that built the string. Subsequent items in this string include the address/port of the Edge Router, gate identifier, signaling endpoint address, data endpoint address, the destination's call reference value, and the destination's address for initial call signaling.

[0609] 7.9.1.2 GCSETUP Error

[0610] If the terminating Gate Controller encounters an error while completing a connection request, it responds to the originating Gate Controller with a GCSETUPNAK message. A sample message is:

[0611] GCSETUPNAK 4T93177 v1.0; ERROR No gates available

[0612] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a SETUPNAK message.

[0613] Other elements in the message are TBD.

[0614] 7.9.2 GCREDIRECT

[0615] The GCREDIRECT message is exchanged between Gate Controllers when different Gate Controllers serve the originating and terminating endpoints of a call. It is basically formed by packaging all the partial state information the first Gate Controller has assembled in its processing of a REDIRECT message, and requesting the terminating Gate Controller to complete the work necessary to redirect the connection.

[0616] A sample GCREDIRECT message is:

[0617] GCREDIRECT OT5081 v1.0; DEST E164 9733608800;

[0618] BILLDATA 5123-0123-4567-8900/9733608718/9733608800;

[0619] CINFO

[0620] 135.207.31.2:7650/135.207.31.1:7682/17S63224/10.0.12.221:7685/10.0.12.221:7000-2-2/9733608718/21/10.0.12.221:7685

[0621] DEST is the destination address for this new connection. Its format is the same as in the SETUP message received from the BTI, except that the E164 number, if present, is expanded from the local numbering plan of the customer to the global numbering plan.

[0622] BILLDATA is the billing/accounting data indicating the charging arrangement for the additional segment of this connection.

[0623] CINFO is a string generated by the originating Gate Controller that contains all the information needed for future enhanced services that may involve the call originator. This will be encrypted and given to the destination BTI to store. The format is a list of many items separated by slashes, or which the first is the ip address and port of the Gate Controller that built the string. Subsequent items in this string include the address/port of the Edge Router, gate identifier, signaling endpoint address, data endpoint address, the originator's call reference value, and the originator's address for initial call signaling.

[0624] 7.9.2.1 GCREDIRECT Acknowledgment

[0625] If the terminating Gate Controller is able to successfully process a GCREDIRECT request, it responds with a GCREDIRECTACK message. A sample message is:

[0626] GCREDIRECTACK 0T5081 v1.0; REMGATEIP 135.207.22.1:7682; REMGATEID 21 S 11018

[0627] REMGATEIP is the IP address and port number of the Edge Router that is holding a gate for the previous connection that has now been redirected.

[0628] REMGATEID is the identification string for the gate at that Edge Router for the previous connection.

[0629] 7.9.2.2 GCREDIRECT Error

[0630] If the terminating Gate Controller encounters an error while completing a redirect request, it responds to the originating Gate Controller with a GCREDIRECTNAK message. A sample message is:

[0631] GCREDIRECTNAK OT5081 v1.0; ERROR No gates available

[0632] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a NAK message.

[0633] Other elements in the message are TBD.

[0634] 7.9.3 GCSPLICE

[0635] If the Gate Controller receiving a SPLICE request from a BTI is not the one that generated the CINFO1 string, it sends to that Gate Controller a GCSPLICE message. A sample message of this type is:

[0636] GCSPLICE 7T1019 v1.0;

[0637] CINFO1

[0638] 135.207.31.2:7650/135.207.22.1:7682/9S1077/10.3.7.151:7685/10.3.7.151:7006-2-2/9733608766/3746/10.3.7.151:7685;

[0639] CINFO2

[0640] 135.207.31.2:7650/135.207.22.1:7682/5S71731/10.3.7.150:7685/10.3.7.150:7000-2-2/9733608720/8839/10.3.7.150:7685

[0641] If the Gate Controller receiving the above GCSPLICE request is not the one that generated the CINFO2 string, it sends to that third Gate Controller another GCSPLICE message. A sample message of this second type is:

[0642] GCSPLICE 7T1021 v1.0;

[0643] CINFO2

[0644] 135.207.31.2:7650/135.207.22.1:7682/5S71731/10.3.7.150:7685/10.3.7.150:7000-2-2/9733608720/8839/10.3.7.150:7685; SIGADDR 135.207.22.1:6162; DATAADDR 135.207.22.1:6164 2 2; CRV 3746; REMGATEIP 135.207.22.1:7682; REMGATEID 9S1077; CODING 53B,6 ms,G.71 1; REFID 135.207.31.2:26124C90:7224; BILLDATA 6010-0203-0456-7890/9733608766/BRIDGE;

[0645] CINFO 135.207.31.2:7650/135.207.22.1:7682/9S 1077/10.3.7.151:7685/10.3.7.151:7006-2-2/9733608766/3746/10.3.7.151:7685

[0646] CINFO1 is the string previously supplied by a Gate Controller, which tells that Gate Controller various pieces of information about the first endpoint. This string was stored encrypted by the BTI that originated the SPLICE request. Either CINFO 1 must be present in the message, or the set of fields that are determined from the Gate Controller unpacking CINFO1: SIGADDR, DATAADDR, CRV, REMGATEIP, REMGATEID, CODING, REFID, and BILLDATA. With these fields present, the CINFO1 string is attached as CINFO.

[0647] CINFO2 is the string previously supplied by a Gate Controller, which tells that Gate Controller various pieces of information about the second endpoint. This string was stored encrypted by the BTI that originated the SPLICE request.

[0648] SIGADDR is the IP address and port number the second endpoint should use for BTI-BTI signaling messages. This is a global version of the address given in the SETUP/SETUPACK message from the first endpoint BTI, with name to ip-address translation done, and with any NAT/PAT server translation included.

[0649] DATAADDR is the IP address and port number the second endpoint should use for data packets. This is a global version of the address given in the SETUP/SETUPACK message from the first endpoint BTI, with name and ip-address translation done, and with any NAT/PAT server translation included. The second and third parameters (optional) in this element give the number of consecutive ports used, and the alignment information needed for the starting port number.

[0650] REMGATEIP is the IP address and port number of the Edge Router that contains the gate to be used at the first BTI's end for this conversation. This is the destination address for all ER-ER communication.

[0651] REMGATEID is the gate identifier and security code for the gate within that Edge Router.

[0652] CODING is the encapsulation method and coding style accepted by the first BTI.

[0653] REFID is a unique identifier assigned by the Gate Controller, which will appear in all the Billing Records. The REFID is intended to be unique within a period of several months.

[0654] BILLDATA is the billing/accounting data indicating the charging arrangement for this conversation.

[0655] CINFO is a string generated by a Gate Controller that contains all the information needed for future enhanced services that may involve that BTI. This will be encrypted and given to the other BTI to store. The format is a list of many items separated by slashes, or which the first is the ip address and port of the Gate Controller that built the string. Subsequent items in this string include the address/port of the Edge Router, gate identifier, signaling endpoint address, data endpoint address, the destination's call reference value, and the destination's address for initial call signaling.

[0656] 7.9.3.1 GCSPLICE Acknowledgment

[0657] If the terminating Gate Controller is able to successfully process a GCSPLICE request, it responds with a GCSPLICEACK message. If the GCSPLICE request was of the first type above, a sample acknowledgement message is:

[0658] GCSPLICEACK 7T1019 v1.0;

[0659] If the GCSPLICE request was of the second type above, a sample acknowledgment message is:

[0660] GCSPLICEACK 7T1021 v1.0;

[0661] SIGADDR 135.207.22.1:6166; DATAADDR 135.207.22.1:6168 2 2; CODING 53B,6 ms,G.711;

[0662] REMGATEIP 135.207.22.1:7682; REMGATEID 5S71731; CRV 8839; REFID 135.207.31.2:26124C90:7224;

[0663] BILLDATA 6010-0203-0456-7890/9733608720/9733608766;

[0664] CINFO

[0665] 135.207.31.2:7650/135.207.22.1:7682/5S71731/10.3.7.150:7685/10.3.7.150:7000-2-2/9733608720/8839/10.3.7.150:7685

[0666] SIGADDR is the IP address and port number the first endpoint should use for BTI-BTI signaling messages. This is a global version of the address given in the SETUP/SETUPACK message from the second endpoint BTI, with name to ip-address translation done, and with any NAT/PAT server translation included.

[0667] DATAADDR is the IP address and port number the first endpoint should use for data packets. This is a global version of the address given in the SETUP/SETUPACK message from the second endpoint BTI, with name and ip-address translation done, and with any NAT/PAT server translation included. The second and third parameters (optional) in this element give the number of consecutive ports used, and the alignment information needed for the starting port number.

[0668] REMGATEIP is the IP address and port number of the Edge Router that contains the gate to be used at the second BTI's end for this conversation. This is the destination address for all ER-ER communication.

[0669] REMGATEID is the gate identifier and security code for the gate within that Edge Router.

[0670] CODING is the encapsulation method and coding style accepted by the second BTI.

[0671] REFID (optional) is a unique identifier assigned by the Gate Controller, which will appear in all the Billing Records. The REFID is intended to be unique within a period of several months. If this parameter appears, it will override the REFID assigned by the originating Gate Controller

[0672] BILLDATA (optional) is the billing/accounting data indicating the charging arrangement for this conversation. If this parameter appears, it will override the BILLDATA assigned by the originating Gate Controller.

[0673] CINFO is a string generated by a Gate Controller that contains all the information needed for future enhanced services that may involve that BTI. This will be encrypted and given to the other BTI to store. The format is a list of many items separated by slashes, or which the first is the ip address and port of the Gate Controller that built the string. Subsequent items in this string include the address/port of the Edge Router, gate identifier, signaling endpoint address, data endpoint address, the destination's call reference value, and the destination's address for initial call signaling.

[0674] 7.9.3.2 GCSPLICE Error

[0675] If the terminating Gate Controller encounters an error while completing a splice request, it responds to the originating Gate Controller with a GCSPLICENAK message. A sample message is:

[0676] GCSPLICENAK 4T93177 v1.0; ERROR No gates available

[0677] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so, and can be passed back to the BTI in a NAK message.

[0678] Other elements in the message are TBD.

[0679] 7.10 Edge Router to Billing Event Collector

[0680] Messages sent by the Edge Router include CALLSTART, CALLEND, and CALLPARTIALEND. These messages are sent over a reliable transport mechanism, such as TCP/IP, which performs all of the flow control and error control needed to ensure the reliable receipt of the messages at the Billing Event Collector. The format of the messages is slightly different than other messages, since they are not transaction based.

[0681] These messages must also include a timestamp. It is assumed here that the timestamp will be added by the Billing Event Collector, who will perform its function in real-time. If, however, the Edge Routers are expected to accumulate event records for some longer period of time and send them in a burst, then the Edge Router will need to record the time of each event and the messages must include that information as well.

[0682] 7.10.1 CALLSTART

[0683] Whenever an Edge Router allocates resources for a gate, it issues a CALLSTART event record to the Billing Event Recorder. A sample message is:

[0684] CALLSTART 135.207.31.2:36123E5C:93178 5123-4567-8900/9733608718/8733608766 53B,6 ms

[0685] The parameters to this message are:

[0686] 1) The unique reference ID for this call, which will be common in all billing records related to the call

[0687] 2) The billing data for this call, which consists of multiple sets of three items:

[0688] a) the account number to be charged for the call

[0689] b) the source E. 164 number for the call

[0690] c) the termination E. 164 number for the call

[0691] d) the above three fields repeated as needed for multiple call segment

[0692] 3) The bandwidth resources used by this call.

[0693] 7.10.2 CALLEND

[0694] Whenever an Edge Router releases resources for a gate, it issues a CALLEND event record to the Billing Event Recorder. Note that this does not occur when a call is placed on HOLD, since the resources are still reserved for future use. A sample message is:

[0695] CALLEND 135.207.31.2:36123E5C:93178 5123-4567-8900/9733608718/8733608766 53B,6 ms

[0696] The parameters to this message are:

[0697] 1) The unique reference ID for this call, which will be common in all billing records related to the call

[0698] 2) The billing data for this call, which consists of multiple sets of three items:

[0699] a) the account number to be charged for the call

[0700] b) the source E.164 number for the call

[0701] c) the termination E. 164 number for the call

[0702] d) the above three fields repeated as needed for multiple call segment

[0703] 3) The bandwidth resources used by this call.

[0704] 7.10.3 CALLPARTIALEND

[0705] Whenever an Edge Router is instructed by a Gate Controller to releases resources at one end of a conversation, but told not to coordinate with the remote gate and release all the resources at both ends, it issues a CALLPARTIALEND event record to the Billing Event Recorder. A sample message is:

[0706] CALLPARTIALEND 135.207.31.2:36123 E5C:93178 5123-4567-8900/9733608718/8733608766 53B,6 ms

[0707] The parameters to this message are:

[0708] 1) The unique reference ID for this call, which will be common in all billing records related to the call

[0709] 2) The billing data for this call, which consists of multiple sets of three items:

[0710] a) the account number to be charged for the call

[0711] b) the source E.164 number for the call

[0712] c) the termination E.164 number for the call

[0713] d) the above three fields repeated as needed for multiple call segment

[0714] 3) The bandwidth resources used by this call.

[0715] 7.11 Gate Controller to NAT/PAT Server

[0716] Messages sent by the Gate Controller include NATENQ, and NATSETUP.

[0717] Inquiry messages to the NAT/PAT server have a common structure for message element names. The first letter of the type name is either “L” or “G”, indicating a request about a local or global address. The last portion of the type name is a number, which is used by the sender to match up responses with the requests. For example, a request message with a parameter GADDR3 will give a response with a parameter LADDR3, and a request message with a parameter LADDR7 will give a response with a parameter GADDR7. There is no requirement that the digit sequences in parameter names by consecutive, but they must be unique within the message.

[0718] 7.11.1 NATENQ

[0719] A NATENQ message is sent by the Gate Controller to the NAT server to inquire about a possible entry in the translation tables, but without creating an entry if none currently exists.

[0720] A sample message is:

[0721] NATENQ 4T93174 v1.0; LADDR1 10.0.12.221:7685

[0722] LADDRx/GADDRx is the locauglobal address and port number that the Gate Controller is asking about.

[0723] 7.11.1.1 NATENQ Acknowledgment

[0724] The response to a NATENQ message gives the translations found in the tables for the specified addresses. If no entry was found, its element is not present in the response message. A sample NATENQACK message is:

[0725] NATENQACK 4T93174 v1.0; GADDR1 135.207.31.1:6000

[0726] GADDRx/GADDRx is the global/local address and port number that the Gate Controller is asking about.

[0727] 7.11.1.2 NATENQ Error

[0728] The only anticipated error that can occur in a NATENQ message is that the server does not perform a NAT/PAT function, and therefore does not recognize the request. A sample error response is:

[0729] NATENQNAK 4T93174 v1.0; ERROR Unrecognized request

[0730] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so. Otherwise it provides some useful debugging information. It can also be passed back as part of the error indication from the Gate Controller request.

[0731] Other elements in the NATENQNAK message are TBD.

[0732] 7.11.2 NATSETUP

[0733] A NATSETUP message is sent by the Gate Controller to the NAT server to create entries in the translation tables. A sample message is:

[0734] NATSETUP 4T93175 v1.0; LADDR1 10.0.12.221:7685; LADDR2 10.0.12.221:7000 2 2

[0735] LADDRx/GADDRx is the local/global address and port number that the Gate Controller desires entries to be established in the translation table. The second parameter, if present, gives the number of consecutive ports requested. The third parameter, if present, gives any alignment restrictions on the port number assigned.

[0736] 7.11.2.1 NATSETUP Acknowledgment

[0737] The response to a NATSETUP message gives the translation entries either found or established in the translation tables. A sample NATSETUPACK message is:

[0738] NATSETUPACK 4T93175 v1.0; GADDR1 135.207.31.1:6000; GADDR2 135.207.31.1:6002 2

[0739] GADDRx/GADDRx is the global/local address and port number that the Gate Controller asked to be established. The second parameter (if present) indicates the number of consecutive ports assigned.

[0740] 7.11.2.2 NATSETUP Error

[0741] Any error encountered while creating NAT/PAT entries will result in a NATSETUPNAK message. A sample error response is:

[0742] NATSETUPNAK 4T93175 v1.0; ERROR Translation table full

[0743] ERROR gives an error message string, which could be displayed if the Gate Controller has some method to do so. Otherwise it provides some useful debugging information. It can also be passed back as part of the error indication from the Gate Controller request.

[0744] Other elements in the NATSETUPNAK message are TBD.

[0745] 7.12 NAT/PAT Server to Gate Controller

[0746] No messages are initiated by the NAT/PAT server.

[0747] 8 Signaling Architecture Call Flows

[0748] In this section call flows are presented to show the signaling exchange for both basic telephony services as well as many CLASS and Custom Calling features.

[0749] 8.1 Call Flow Terminology

[0750] The following terminology describes signaling call flows that can be used by embodiments of the present invention. Symbols are used to represent parties involved in the call flow (e.g. Gate Controllers) and information that is exchanged (e.g. Call Parameters). Each of these is often followed by a subscript indicating which one specifically is being referenced. Common subscripts are O for originating, T for terminating, F for forwarding, B for bridging, and TR for transferring. For example, in a simple telephone conversation, BTIO refers to the originating BTI, and BTIT to the terminating BTI, and similarly for E.164T, ERO, ERT, GCO, GCT, etc.

[0751] All the messages and parameters are described in detail in the next section.

[0752] Call Flow Symbols:

[0753] BTI—Broadband Telephony Interface—or a telephony-equipped cable modem

[0754] ER—Edge Router: Cable modem termination system that serves the BTI

[0755] GID—Gate ID: Identification of the “gate” within the edge router assigned to this call.

[0756] GC—Gate Controller that serves the BTI

[0757] CI—Call Information: Information about the call through the network. This information includes the E. 164 address, the IP address of the BTI, the IP address of the serving Gate Controller, the IP address of the serving ER, and the GID of the gate in the ER.

[0758] [CI](GC)—Encrypted information about the BTI that is given to others outside the network to store. It is signed and encrypted by the Gate Controller indicated.

[0759] BID—Billing ID: Identifier of the call for billing purposes; intended to be unique not only within the entire network, but to not be reused for a significant period of time. Both Edge routers involved in a call report this identifier in the call detail records.

[0760] TID—Transaction ID: Identifier of a message; indended to only be locally unique for the duration of a message/response transaction.

[0761] E.164—Telephone number

[0762] CN—Directory name of caller

[0763] LA—local IP address (set when BTI powers on)

[0764] GA—global IP address (set via NAT when BTI begins a session)

[0765] PN—Port number used by BTIs for a particular connection

[0766] Al—Authentication Information, single string per subscriber, common across all lines served by one BTI. This string is signed and encrypted by a network server, and is verified by Gate Controllers for every transaction.

[0767] $—call accounting information, such as customer account number, to be included in billing information for the current call. Given to ER as part of the permission to open gate. In some cases, e.g. call forwarding, two separate account numbers will be included to indicate a split charging arrangement for the call. In addition to charging information, accounting information includes parameters that place bounds on the call that is to be established. Some parameters may include maximum call duration and transmission priority.

[0768] CP—Call parameters (e.g. compression standard) for this call. CPO are the parameters offered by the call originator, CPT are those accepted by the terminating system.

[0769] o—indicates that network address translation is done in the ER

[0770] ANN-INFO—Announcement Information: Parameter indicating to an announcement server which announcement to play.

[0771] CF—Flag that indicates call forwarding on all calls or busy is active.

[0772] T—Flag that indicates call transfer is active.

[0773] CTOR—Cut Through On Release Flag: Indicates that the Edge Router should cut through the call in the receive direction when the BTI reserves the bandwidth.

[0774] SGCP Parameters:

[0775] S-R—SGCP parameter indicating a connection should be opened in both the send and receive directions.

[0776] S-NR—SGCP parameter indicating a connection should be opened only in the send (upstream) direction.

[0777] NS-R—SGCP parameter indicating a connection should be opened in only the receive (downstream) direction.

[0778] SS7 Symbols:

[0779] IAM—Initial Address Message

[0780] ACM—Address Complete Message

[0781] E-ACM—Early Address Complete Message

[0782] ANM—Answer Message

[0783] REL—Release Message

[0784] RLC—Release Complete Message

[0785] SUS—Suspend Message

[0786] RES—Resume Message

[0787] 8.2 Basic Call Flows

[0788] 8.2.1 Connect

[0789] FIG. 6 shows the call flow for a normal call setup. Call setup involves establishing an IP signaling and bearer channel between BTIs across a packet network. The signaling channel uses “better than best effort” IP transmission across the network. Signaling reliability is ensured within the application. In the access portion of the network (between the edge router [ER] and the BTI), the bearer channel uses an “unsolicited grant” as defined by the MCNS v1.1 to maintain a constant bit rate channel. The ER “colors” the “high QoS” bearer channel packets to give them higher priority than “best-effort QoS” packets over the backbone portion of the network (between the ERs).

[0790] Some of the aspects of the basic Connect call flow are:

[0791] Digit Collection—The BTIo needs to recognize when a complete telephone number is dialed so it can package the number in a SETUP message and send it on to GCo for translation.

[0792] Network Address Translation (NAT) for the Originating BTI—The ER does network address translation between local (Net10) addresses for each of the BTIs and global addresses. Each ER is assigned a set of global addresses. The ER assigns a global address to a BTI when the BTI attempts to communicate outside of its local area, or when a Gate Controller requests that a global address be assigned toaBTI.

[0793] BTI Authentication—GCO authenticates the BTI upon receipt of a SETUP message.

[0794] The Authentication Information (AI) needs to be provisioned in the BTI at BTI registration. GCO also performs service-specific admission control. For instance, if a Gate Controller knew that a specific destination area was overloaded with traffic, it could block a call setup.

[0795] Gate Allocation—GCO requests a gate be allocated in ERO for this call. ERO replies with a Gate ID (GIDO) to be used for the call. GCO adds this information to the Call Information (CIO) record for this call.

[0796] Billing Identifier (BID)—While processing an initial call attempt, the Gate Controller assigns a globally unique Billing Identifier (BID) to the call. Such a unique identifier could be, for example, the IP address of the Gate Controller, followed by a timestamp, followed by a call sequence number. It is intended that this identifier be unique over several billing cycles, and enable the billing system to correctly match all records related to a single call.

[0797] Number Translation—The E.164T address is translated by the Gate Controllers to the local IP address of the terminating BTI and the terminating ER. If GCO cannot translate the E.164T address on its own, it identifies a Gate Controller (GCT) that can do the translation. GCO sends the GCSETUP message, with additional information in it, on to GCT for processing. This simplifies the security of the ER, in that it only accepts commands from a small group of well-known Gate Controllers.

[0798] Accounting Information ($)—In addition to charging information (e.g. account number), accounting information includes parameters that place bounds on the call that is to be established. Some parameters may include maximum call duration and transmission priority. In several situations involving call forwarding, the charging for the call will be split among two or more subscribers. Thus the “$” parameter in messages may contain several account codes with information as to the proper allocation of charges to each.

[0799] “Opening The Gate”—The Gate Controller gives permission for an ER to allow a BTI to set up an “unsolicited grant”. The ER also “colors” the bearer-channel packets so they have “high-QoS” to a specific destination address. If an ER does not receive the permission to “open the gate” for high-priority packets, it does not allow the unsolicited grant or the high-priority packets. This permission is based on a specific source IP address and a specific destination IP address, and bounds on the resources the endpoints can use. The account information ($) in the gate setup message to the ER provides the bounds on these resources.

[0800] Call Information (CIO and CIT)—information about a BTI, including its E.164 address, its Gate Controller's address, its ER's address, and the GID within the ER. Each endpoint of a call receives this information about the other endpoint, signed and encrypted by the local Gate Controller to prevent unauthorized disclosure or tampering by the BTI. This call information is used later for Call Trace (*57), Call Return (*69), and in setting up Three-Way Calling.

[0801] Capability Negotiation—The BTIs have the ability to negotiate Call Parameters (CP) (e.g. encoding) in the SETUP message exchange. If additional negotiation is needed, it can be accomplished before resource commitment is made.

[0802] Access Resource Reservation—An MCNS unsolicited grant protocol is used to reserve a constant bit rate channel in the access portion of the network. The access reservation comes in two parts, which is required for the telephony application. In first step, the “reservation” ensures the bandwidth will be available when needed, but does not actually assign the bandwidth nor does it “open the gate.” The reservation is obtained prior to ringing the destination telephone. Only when the destination user answers does the second step, the “commitment,” allocate the bandwidth and start the billing for the call. To protect resources, only a certain number of outstanding reservations are allowed per BTI.

[0803] Backbone Resource Reservation—DOSA allows for the possibility of a different backbone resource reservation protocol than that used for the access portion of the network. It is the job of the ER to process the access reservation message and translate it into the proper message sequence for backbone resources. When the ER acknowledges the reservation with an ACK message, it means that the access resources are available for the call and whatever backbone resources this CMTS needed to reserve to support the flow has been reserved. At this point it is safe to begin the ring phase. An example of backbone resource reservation is shown in Section 6.2.2.

[0804] Commit—This is the second step of the access reservation sequence. The commitment is made when an actual connection is to be made and billing is started. The ER and the network previously reserved the resources, and held them for this particular conversation. The ER emits a call-detail-record to the billing system at this time.

[0805] Gate Coordination—In order to avoid certain theft of service scenarios, the opening and closing of gates within the network needs to be coordinated between ERs. GATEOPEN is an ER to ER message indicating that the gate has opened on the far end of the call. Far end Call Parameters are passed to the BTI for it to check whether it agrees with the parameters that are in the far end gate.

[0806] 8.2.2 Backbone Reservation

[0807] FIG. 7 shows an example signaling flow for reservation of resources in the segment of the network between the edge routers for a voice call. This is one potential model of backbone reservation; however, different approaches may achieve the same result. One principle that we desire to achieve is to separate the mechanism for access reservation from the backbone reservation. This leaves the BTI interaction with the ER independent of the backbone network between ERs.

[0808] We assume a model in which the resource reservation is initiated by a sender and only reserves resources for packets being generated by that sender i.e. reservations are unidirectional. This matches the forwarding model used in IP networks in which paths can be asymmetric. However, the RESERVE message used over the access network has different semantics: reserve bi -directional capacity over the access network.

[0809] Since, the end to end route between two edge routers may change during the duration of a call, we also assume that RESERVE messages are periodically transmitted from either end to refresh the reservation—this is not shown in the figure. The IP source address in the RESERVE message contains the source address of ERO. The IP destination address in the RESERVE message is that of BTIT. The reservation message identifies: GAO (BTIO's global IP address), PNO (BTIO's port number for this call), GAT (BTIT's global IP address), PNT (BTIO's port number for this call) as the owner of the reservation. After setting up the bidirectional access reservation, the ER sends a BACKBONERESERVE message through intermediate backbone routers towards BTIT. Routers that are incapable of processing the BACKBONERESERVE message forward them without any processing.

[0810] In this example, the receipt of the RESERVEACK to a BTI indicates that resources have been reserved in both the send and receive directions in the access channel, and in the send direction in the backbone.

[0811] 8.2.3 Disconnect

[0812] FIG. 8 shows the call flow for a normal call termination. When a BTI detects on-hook, it sends an end-to-end HANGUP message to the other BTI and a RELEASE message to the ER. In response to the RELEASE command, the ER closes the gate and emits a CALLEND to the billing system that indicates the call has completed and that billing should stop.

[0813] Note that there are a number of error conditions that will cause this disconnect sequence, such as BTI failures, power failures, cable plant failures, and backbone network failures. In all cases, it is desirable to stop the billing at the end of the useful connection, and to not charge the customer for a (possibly lengthy) service outage.

[0814] 8.2.4 Calls Terminating in the PSTN

[0815] FIG. 9 shows the call flow for a call originating from a BTI but terminating in the PSTN. In the call flow, GCT recognizes that E.164T terminates outside of the IP network. GCT identifies the appropriate SGWT and TGWT. GCT initiates a GATESETUP to ERT with the Cut Through On Reserve (CTOR) flag set to indicate that a one-way voice path from the PSTN to BTIO should be established once the reserve is requested. GCT then sends the SETUP to SGWT. SGWT allocates a trunk identified by the IP port number PNT on TGWT for the call. SGWT also looks at CPO to determine the call parameters that will be used for this call (CPT).

[0816] Upon receiving the SETUPACK from SGWT, GCT replies to GCO, including the CTOR flag. GCO sets up the gate on the originating end of the call including the CTOR flag indicating that ERO, should open the voice path toward BTIO on reserve. GCO also includes the CTOR flag on the SETUPACK message to BTIO so BTIO does not generate its own ringback, but uses the ringback from the far end of the network. If additional capability negotiation is needed, it can be done at this point.

[0817] Once the call parameters are known, SGWT uses the SGCP message CREATECONNECTION to inform TGWT about the potential call. Included in this message are all the parameters that TGWT needs to reserve the necessary bandwidth and to translate between the IP packets and the TDM trunk. Also included in this message is an SGCP NOTIFICATIONREQUEST, requesting TGWT to notify SGWT when the reservation is acknowledged by ERT. TGWT sends a reserve message requesting the appropriate QoS in the network for the call. The trunking gateway needs to send this reserve message (versus the SGW) since the reservation needs to be along the path of the bearer channel. Upon a successful reservation, TGWT sends the SGCP NOTIFY to SGWT.

[0818] Once SGWT receives both the RING message from BTIO and the NOTIFY from TGWT, SGWT sends the SS7 Initial Address Message (IAM) into the PSTN to set up the connection between TGWT and the ultimate destination. Upon receipt of the SS7 Address Complete Message (ACM), indicating that the destination phone is available and ringing, SGWT sends BTIO the RINGBACK message and BTIO plays ringback tone it is receiving from the network to the customer.

[0819] When the destination phone goes off-hook, an SS7 Answer Message (ANM) is received by SGWT. SGWT sends the CONNECT back to BTIO and uses the SGCP message MODIFYCONNECTION to indicate to TGWT that it needs to change the connection to a two-way connection, and send the COMMIT into the network to open the gate in both directions.

[0820] There are special cases when SS7 messages are received that cause the call flow to change. Some of these cases are described below:

[0821] Early Address Complete Message (E-ACM)—When an E-ACM message is received from the SS7 network instead of ACM, the voice connection needs to be established in both directions (send and receive). One example of how this is used by the PSTN is to indicate when an 800 call is being routed to an IVR system to determine where the call should be ultimately routed. After the call is routed and the far end answers, SGWO receives an ANM.

[0822] Busy—If either the PSTN network or the called party is busy, the SS7 network returns a busy indication with a cause code in response to the IAM. SGWO needs to send a BUSY message with a cause code in place of RINGBACK to BTIO so BTIO will play fast busy or slow busy to the customer.

[0823] 8.2.5 Calls Originating From The PSTN

[0824] FIG. 10 shows the call flow for a call originating in the PSTN, but terminating in the IP telephony network. The IAM message is the first indication that a call is destined from the PSTN to a BTI. The IAM message is received by SGWO which subsequently sends a SETUP message to GCO. setup proceeds as normal through the IP network. The CTOR flag is not needed since ringback or terminating announcements will not be generated from the IP network.

[0825] The signaling flow is similar to when a call is destined for the PSTN (see previous section). SGCP messages are used between SGWO and TGWO.

[0826] 8.2.6 Call Release To The PSTN

[0827] FIG. 11 shows the call flow for a normal release to the PSTN. This call flow assumes that the BTI originated the call. If the call originated in the PSTN, SGWT would send an SS7 Suspend (SUS) message. This indicates to the PSTN that the phone at the BTI went on-hook, but the call is not released until a timer expires (usually 14 seconds). If the phone goes off-hook before the timer expires, an SS7 Resume (RES) message is sent.

[0828] 8.2.7 Call Release From The PSTN

[0829] FIG. 12 shows the call flow for a call released from the PSTN. The call flow assumes that the call originated in the PSTN.

[0830] 8.2.8 E911 Emergency Service

[0831] To support E911 emergency calls, GCO must route the call to the E911 call center associated with the calling number. The E911 call center may be reached via a gateway or may be an E911 call center that is supported on the packet network. The originating phone number and additional information can be obtained by having the E911 call center send a SETUPNACK message to GCT as in the call flows for caller ID/calling name delivery. Otherwise, the call flows for call setup are unchanged.

[0832] The BTI originating a 911 call must not disconnect the call when the user hangs up. This requires BTIO to detect that the dialed number is 911 and to alter its local hangup processing accordingly.

[0833] A call to an operator for assistance may be transferred by the operator to an E91 1 center. In this case, the gateway or end-system that the operator is connected to must send an end-to-end message to BTIO instructing it to alter its hangup processing. This message must be authenticated by BTIO as being sent by a trusted network entity before BTIO alters its hangup processing. Authentication is required so that an arbitrary endpoint cannot instruct a BTI to alter its hangup processing.

[0834] 8.2.9 Terminating Announcements

[0835] In some cases when a call cannot be completed, the customer hears a terminating announcement. Terminating announcement handling may be invoked when the dialed number has changed or cannot be translated, or as a result of a network resource limitation (e.g., “trunk busy”) or network problem.

[0836] Since the BTI contains processing and storage, common terminating announcements may be handled locally by the BTI in response to an error indication. For example, common messages such as “The number you have dialed is not in service. Please check the number and dial again” or the “trunk busy” signal may be stored locally in the BTI. In the first case, GCO returns an error message to BTIO indicating that the dialed number cannot be translated. In the second case, a router returns an error message to BTIO as a result of an admission control failure during the processing of a COMMIT message. The error messages indicate to BTIO which announcement should be played.

[0837] Some services require the announcement to be customized, perhaps based on the originating number, dialed number, time-of-day, or administrative controls. Thus, in general, announcements are a function of conditions known to the Gate Controller. In this case, there are two options for supporting terminating announcements. The Gate Controller may send the announcement to the BTI as a data message to be played out by the BTI. Alternatively, the BTI may connect to a terminating announcement server. These alternatives may also be used to support the common terminating announcements described above.

[0838] FIG. 13 shows a call flowwhere the BTI connects to a terminating announcement server.

[0839] Terminating announcement handling may be invoked either by GCO or GCT in response to a SETUP message. The Gate Controller routes the call to a terminating announcement server and interacts with the server to control the announcement that it plays. The call accounting information (“$”) that is used for the call indicates that the call is not billed.

[0840] 8.2.10 CALEA Wiretapping

[0841] CALEA requires the ability to intercept (wiretap) calls from a subscriber line and to provide additional information associated with these calls, such as the dialed number, and the time and duration of the call. Given that the BTI is not considered to be a trusted device, support for CALEA wiretapping must be implemented within the network, and must not be detectable by any party participating in the call. Our solution to the problem requires the ER to be able to multicast information flowing from each party in the call to both the other party or parties, and an additional end-system or gateway (a “wiretap server”) that can deliver the bearer channel information to the authorities. This multicast capability requires every packet that matches a filter function to be routed to the wiretap server, in addition to being routed normally. The filter function is discussed below.

[0842] One proposed approach to the problem does not rely on per-connection processing in the ER to wiretap a line. In this approach, when the authorities ask that a line be wiretapped, an administrative system sends a message to the originating ER instructing it to multicast the bearer channel to the wiretap server. The filter specifies the local IP address of the BTI associated with the line that is being tapped, the address of the wiretap server, and it might additionally specify the port number associated with the bearer channel. However, since the port numbers associated with the bearer (voice) channel may be dynamically assigned by the originating and terminating BTI's, the administrative server is unable to specify this information. If the filter function does not contain the port number information, it would cause all packets associated with the BTI to be intercepted, which may not be desirable since these packets may include data packets that cannot legally be intercepted. Thus, this approach is possible in our architecture, but it may be desirable to have an approach that only intercepts the bearer channel without intercepting additional channels.

[0843] The preferred approach is to rely on the Gate Controller to support wiretapping. When the authorities ask that a line be tapped, the database record associated with the line is modified to indicate that the line should be tapped. When a SETUP message arrives at the Gate Controller (it may be either an originating Gate Controller or a terminating Gate Controller), the Gate Controller looks up the database record and notes that the line should be tapped. The Gate Controller sends a message containing the address of the wiretap server to the ER. This information may be included as part of the “gate open” message.

[0844] The Gate Controller also sends a message containing the dialed number to the wiretap server. The ER sends messages at the beginning and the end of the call to the wiretap server. These additional messages provide the additional information required by CALEA. In this solution, only new calls may be wiretapped. Calls that exist before the wiretapping information is provisioned in the GC will not be multicast to the wiretap server.

[0845] 8.2.11 Call Trace

[0846] FIG. 14 shows the call flow for Call Trace. BTIT (the recipient of the call that needs to be traced) sends a single TRACE message to GCT, containing its own authentication information, and the connection information received from GCT for the most recent incoming call. GCT verifies the connection information (CI) by decrypting and checking the signature. If valid, the E.164 number contained within CI is reported to law enforcement, along with the identity of the customer making the report.

[0847] 8.2.12 Operator Break-In

[0848] Operator Break-In is a combination of the CALEA wiretapping described in Section 8.2.10 and Three-Way Calling described in Section 8.3.4. Call flows for operator break-in will be provided in future versions of this document.

[0849] 8.2.13 Operator Services

[0850] Operator services will initially be supported for IP phone customers by going through a PSTN Gateway. In the future, operator services may be on the IP network.

[0851] 8.2.14 Mid-Call Resource Change

[0852] In some cases, a call in progress may need to change the established call parameters. For instance, if a call is set up using a low-bit-rate compression (e.g. 16 kbps G.728) and after the call is answered the BTI detects a modem tone, the BTI needs to change the bearer channel to a non-compressed 64 kbps G.711 channel. FIG. 15 shows the call flow of how this can be accomplished. Gate Controllers do not need to be involved in a mid-call resource change as long as the account information the Gate Controller delivered to the ER during call set up is consistent with the resource change request. For example, if the BTI requests a channel with higher bandwidth or higher priority than the account information allows, the ER would deny the request. As with the normal call set up, there is a two step—Reserve then Commit—process for changing call parameters mid-call.

[0853] 8.3 Feature Call Flows

[0854] 8.3.1 Call Forwarding

[0855] Call Forwarding service allows a call destined for one E.164 address to be redirected to another E.164 address. The redirection may happen on all calls, only on busy, only on no answer, or on a combination of either busy or no-answer. Call Forwarding is a popular service, and is used by other services (e.g. voice mail) to redirect calls. If a BTI is unavailable and call forwarding is active, all calls destined for the BTI should be forwarded.

[0856] At least three parties are involved in all types of Call Forwarding service:

[0857] The Originating Location (BTIO)—the location that places the call to be forwarded.

[0858] The Terminating Location (BTIT)—the location that has Call Forwarding active.

[0859] The Forwarding Location (BTIT)—the location that the calls are being forwarded to.

[0860] Regardless of the type of Call Forwarding (All Calls, Busy, No Answer), the forwarding number may be specified by the customer on a per-use basis, or be pre-provisioned (specified when the customer signs up for Call Forwarding service). If the forwarding number is pre-provisioned, the BTI and the Gate Controller serving that customer stores the forwarding number. If the forwarding number is specified on a per-use basis, the customer dials a code (e.g. *72) and the forwarding number to activate Call Forwarding.

[0861] In all cases, the Originating Location must not receive the forwarding number. In the case of Call Forwarding—No Answer, the Originating Location may know that the call is being forwarded.

[0862] FIG. 16 shows the call flow for activating a per-use Call Forwarding service. The BTI recognizes that the customer dialed the code to active Call Forwarding, and prompts the customer for the forwarding telephone number. This information is sent to the Gate Controller in a PROFILE message. The Gate Controller validates that the forwarding number maps to either a BTI that the Gate Controller knows or to another Gate Controller. The Gate Controller checks to make sure the customer subscribes to Call Forwarding service, and if so activates the service and stores the forwarding number for later use.

[0863] The following sections describe the call flows for each of the types of Call Forwarding service for both when the BTI is available and when the BTI is unavailable.

[0864] 8.3.1.1 Call Forwarding—All Calls

[0865] FIG. 17 shows the call flow for Call Forwarding—All Calls when the BTI is available. The first part of the call flow is the same as shown in FIG. 6: Connect Call Flow. When the SETUP message is received by the Terminating BTI, it recognizes that Call Forwarding—All Calls is active. It sends a special SETUPACK to the Terminating Gate Controller indicating that Call Forwarding is active. The Gate Controller recognizes the Call Forwarding response, closes the gate at the ER that it opened for this call (using the GATERELEASE message), and sends the forwarding number on to GCO along with account information so that the forwarded leg of the call can be billed to BTIT. The Originating Gate Controller sets up the call to the forwarding number as normal, except that billing information may be kept for both legs of the call.

[0866] FIG. 18 shows the call flow for Call Forwarding—All Calls when the Terminating BTI is not available. In this case, GCT times out on the BTIT SETUP message. The GCT checks the customer profile and determines that Call Forwarding is active and proceeds as if it got a Call Forwarding response from BTIT.

[0867] 8.3.1.2 Call Forwarding—Busy

[0868] FIG. 19 shows the call flow for Call Forwarding—Busy when BTIT is available. The first part of the call flow is the same as shown in FIG. 6: Connect Call Flow. When the SETUP message is received by BTIT, it recognizes that the designated line is currently off-hook and that Call Forwarding—Busy is active. It sends a special SETUPACK to GCT indicating that Call Forwarding is active. GCT recognizes the Call Forwarding response. The rest of the call flow is identical to FIG. 17: Call Forwarding—All Calls/BTI Available.

[0869] FIG. 20 shows the call flow for Call Forwarding—Busy when the BTI is unavailable. This flow is identical to FIG. 18: Call Forwarding—All Calls/BTI Unavailable Call Flow.

[0870] 8.3.1.3 Call Forwarding—No Answer

[0871] FIG. 21 shows the call flow for Call Forwarding—No Answer when BTIT is available. The first part of the call flow is the same as shown in FIG. 6: Connect Call Flow. BTIT recognizes the Call Forward-No Answer feature is active and times out after the correct number of rings. A RINGTIMEOUT message is sent to the originator to stop the ringback, and a REDIRECT message is sent to the GCT to start the forwarding operation. The REDIRECT message contains the new E.164F address.

[0872] GCT decrypts the call information, and retrieves the billing information for this subscriber. If the call forwarding or transfer feature is subscribed it passes the GCREDIRECT message back to the GCO with the appropriate billing information.

[0873] The REDIRECT messages serves two purposes, this call forwarding function and also a blind transfer function (transfer without consultation). Since the Gate Controller does not know which application is active, it must assume a data transfer is in progress and inform BTIO that it will be interrupted. This is done via the CALLHOLD/CALLHOLDACK exchange. If BTIO was in a talking state, BTIO tells ERO to temporarily suspend its resource reservation; then acknowledges the CALLHOLD command of the GCO. GCT then acknowledges to BTIT that the REDIRECT was successful.

[0874] At this point the GCO treats this call identically to the initial call, by translating E.164F into a Gate Controller address and passing a GCSETUP message to GCF. The actions of GCF, ERF, and BTIF are identical to those shown in FIG. 6 for GCT, ERT, and BTIT.

[0875] When GCO receives the acknowledgement to its GCSETUP message, instead of performing a GATESETUP it modifies the settings of the already allocated gate via a GATEMODIFY command. When complete, the new destination information is passed to the BTIO via a TRANSFER message. GATEMODIFY and TRANSFER are identical to the messages used for 3-way calling and for call transfer. After resources are reserved for this call, BTIO sends a RING command, and the response is either RINGBACK (if the new destination is onhook and now ringing) or CONNECT (if the new destination is ready now). The latter would typically be the case within interactive voice response systems. After the CONNECT message, the resources are committed and the communication path is opened.

[0876] FIG. 22 shows the call flow for Call Forwarding—No Answer when the BTI is unavailable. This flow is identical to FIG. 18: Call Forwarding—All Calls/BTI Unavailable Call Flow.

[0877] 8.3.2 Caller ID/Calling Name Delivery

[0878] The following describes two alternatives for implementing Caller ID/Calling Name Delivery with embodiments of the present invention.

[0879] The first is to have BTIT request caller ID information upon receipt of the SETUP from the GCT. This request is sent to GCT, which recognizes the Caller ID flag and checks if the customer line has subscribed for Caller ID/Calling Name services. GCT returns the phone number (E.164o) and the Calling Name (CNo) of the call originator. Subsequently, BTIT returns a SETUPACK as usual. If the subscriber at BTIT subscribes to services such as Anonymous Call Rejection or Call Screening, then the SETUPACK may not be returned by BTIT. Finally, when BTIT rings the phone (assuming it is a simple “black phone” with the traditional Caller ID box), then the Caller ID and Calling Name are presented to the Caller ID box between the 1st and 2nd ring. If the user's telephone is more intelligent, this information may be presented as a message that is interpreted and displayed. FIG. 23 shows the call flow for this alternative.

[0880] 1. Another alternative for implementing Caller ID/Calling Name Delivery is to have GCT check if BTIT subscribes to the service on receipt of every call. If so, the caller's phone number (E.164o) and the Calling name (CNo) are sent in the SETUP message to BTIT on every incoming call. The BTI can either accept (SETUPACK) or reject (SETUPNACK) the call based upon E.164o and CNo. This alternative does not require additional messaging between GCT and BTIT for achieving Caller ID/Calling Name Delivery services.

[0881] 8.3.3 Call Waiting

[0882] FIG. 24 showsw a call flow for Call Waiting, accordeing to an embodiment of the present invention. Initially, there is a call in progress between the BTIO1, and BTIT. A second call from BTIO2 to BTIT is established up to the point of reserving access and backbone bandwidth. BTIO2 reserves the channel as normal, but BTIT uses a RERESERVE message to indicate that it does not need a new access reservation, but just needs to associate the new gate (GIDT2) in the ER with the existing access reservation for gate (GIDT1). “RING” and “RINGBACK” messages are exchanged between the new BTIO2 and BTIT. BTIT now inserts a “call waiting tone” into the original call in progress to indicate to the user that there is a second incoming call. When the user does a “flash-hook”, then BTIT sends a HOLD message to BTIO1 and receives an acknowledgment for this message. Subsequently, BTIT completes the call to BTIO2 by sending a CONNECT message. Instead of having another allocation of resources for BTIT for this new call, we go through a reallocation of existing resources. The BTIT sends a RECOMMIT message with the Gate IDs of the two calls (GIDT1 and GIDT2) so that ERT may reallocate the resources from the first to the second call. In addition, a new CALLSTART event is sent to the billing server. When BTIO1 gets the HOLD message, it requests ERO1 to suspend allocation of its resources on the MCNS channel using the HOLD message until a future COMMIT message is sent from BTIO1. BTIO1 sends periodic KEEPALIVE message both to ERO1 and BTIT to ensure that the bandwidth is not reallocated to other calls.

[0883] 8.3.4 Three-way Calling

[0884] 8.3.4.1 Three-Way Calling—Bridging In BTI

[0885] FIG. 25 shows the call flow for the simple Three-Way Calling alternative with bridging in BTIO. In the flow, a second call is set up as a totally new call using separate resources in BTIO, the access network, and the backbone network. When the customer wants to complete the three-way call (indicated by the second flash-hook), BTIO bridges the calls together.

[0886] This section describes the use of a bridge located on a server inside the network. FIG. 26 illustrates the first steps of a three-way call. The customer starts with an existing call, either one he or she placed or one that he or she received. By flashing the switchhook, that call is placed on hold. A HOLD message is sent to the destination indicating this change, and HOLDACK is sent in response. Both ends then inform their ERs that the isochronous transmission will be temporarily halted, but to keep the committed resources, via the HOLD message to the ER. Periodic KEEPALIVE messages are sent to each end and the ERs to accomplish this.

[0887] BTIO then plays the originator dialtone, and receives the full E.164 address of the additional party to call. This new call proceeds as shown in FIG. 6 for normal call setup. At the point of the resource reservation exchange, ERO has allocated two gates (the original one with the parameters of the first call, and the new one with parameters for this call), upstream access resources are reserved for one call, and the backbone has reserved resources for both of the calls. When the third party answers, the second call is established using the resources reserved for GIDO2. This state is identical to that of call-waiting, when one call is on hold and the subscriber is talking on a second call. However, since the subscriber initiated the second call, instead of receiving that call, the later hookflash commands a three-way call instead of a switch back to the first conversation.

[0888] FIG. 27 shows the sequence of signaling messages exchanged in the conversion of two separate calls into one three-way call. BTIO allocates a conference bridge by creating a third connection to a special network server. The bridge server will take an arbitrary number of input streams and generate an output stream for each; each output is the sum of all inputs except for the contribution from the corresponding input. When the number of inputs exceeds a small number (e.g. 3), the bridge does silence detection on each input to reduce the accumulated noise.

[0889] Once the host establishes the connection to the bridge, each of the participants of the three-way call need to be informed of the new destination, and need to have their gates modified appropriately. This function is identical to that done for Call Forwarding with No Answer, and involves BTIO sending a REDIRECT message for each existing connection.

[0890] The REDIRECT function involves two steps. First is a GATEMODIFY message to the ER modifying the parameters of the gate. This message includes the new destination address for data packets, as well as new billing information. Second is a TRANSFER message to the BTI, telling it to switch to a new destination for sending and receiving packets. Before acknowledging this message, the BTI performs a resource reservation exchange with the indicated endpoint (in this case, the bridge) to ensure network resources are available.

[0891] The GATEMODIFY message sent to the ER includes charging information ($). Calls from each endpoint to the bridge involve split-charging; the originator of the call pays only for the equivalent call to his/her dialed destination, and the party making the three-way call pays for the extra segment to the bridge. This is similar to that done for Call Forwarding.

[0892] The GATEMODIFY message sent to the ER also includes a Billing Identifier, BID. This unique identifier is given to all of the ERs involved in the three-way call, so that all billing records produced can be matched later. The BID used for the call is the unique ID assigned for the BTIO to Bridge connection.

[0893] The TRANSFER message sent to the BTI includes updated CIB information, encrypted by the local GC. This information replaces the previous CI information. CIB contains sufficient information to allow one of the participants in this 3-way call to add another party and allocate an additional bridge; use of this CIB for a return-call or for call-trace will result in errors.

[0894] It is possible for one of the participants in a 3-way call, who also subscribes to the 3-way calling service, to add another party. The call flow is identical to FIG. 27, except that one of the endpoints is not a BTI but rather the first Bridge. The Bridge handles TRANSFER messages in the same way as the BTI, allowing this service to cascade.

[0895] This sequence assumes the Bridge is located within the network, and does not need global address or gates to be allocated. GCO is identified as the Gate Controller serving the bridge, and there is no ER and no need for upstream scheduling of access lines. If the bridge were instead located outside of the network, then additional exchanges would be required to establish the gates and allocation of upstream bandwidth. These exchanges would be identical to those for normal call establishment.

[0896] There are two separate cases for hangup sequences. If the originator of the 3-way call hangs up, it sends the RELEASE message to its local ER and a HANGUP message to the bridge. The bridge, sends HANGUP messages to the other two legs of the call and also GATECLOSE messages to their ERs. This sequence is shown in FIG. 28.

[0897] If a participant in the 3-way call disconnects, it is desired that the bridge be released and the call revert back to a normal two-party call. FIG. 20 shows the sequence of messages needed to perform this function. The Bridge receives a HANGUP message from a participant BTI, and sends a SPLICE message to its GC, giving the connection information (CI) for the two call legs to be spliced together.

[0898] The GCs inform the ERs, via a GATEMODIFY command, of the new destination of the data packets, and inform the BTIs, via a TRANSFER command, of the new destination. In case of errors, such as when the resource reservation exchange fails to allocate backbone bandwidth for the direct connection, the bridge can stay involved in the call with the two remaining parties.

[0899] 8.3.5 Call Transfer

[0900] There are two different call transfer services. Call Transfer With Consultation is a service very similar to Three-Way Calling except that when the originator of the three-way call disconnects, the remaining two parties can still talk. Call Transfer Without Consultation is similar to Call Forwarding, except the forwarding can be done after a call is established.

[0901] 8.3.5.1 Call Transfer with Consultation

[0902] Call Transfer With Consultation is very similar to Three-Way Calling except that when the customer (or host) hangs up the phone, the call between the two participants can continue. Also billing continues as if both legs of the call are still in place.

[0903] Most of the call flows for setting up a Call Transfer With Consultation are identical to those for Three-Way Calling (FIG. 26, FIG. 27, and FIG. 29). The only call flow that is different is when a host disconnects. FIG. 30 shows the call flow for Call Transfer With Consultation service when the host disconnects. As with Three-Way Calling, the call reverts to a simple two-way call between the two participants. However, the billing for the call continues as if it is a three-way call. For the Call Transfer With Consultation call flow, the following events have proceeded the hangup of the host:

[0904] 1) BTIT1 has originated a call to BTIO and billing records (BIDT1/O) for this leg of the call are being generated by ERT1.

[0905] 2) BTIO has put BTIT1 on hold and set up a new call to BTIT2. The billing records (BIDO/T2) for this leg of the call are being generated by ERO.

[0906] 3) BTIO has joined the two legs of the call into a three-way call using a network bridge.

[0907] At the point when the host hangs up, the gate at the host's edge router (ERO) is closed and billing associated with that gate (BIDO/T2) is terminated. GCO retrieves the information associated with this billing record (including the globally unique BID) from ERO using the GATEINFO request and transfers the billing information to one of the participant's ERs. The participant ER that receives this information (ERT2 in the call flow), generates a new billing record for the leg associated with BIDO/T2. During bill processing, the two billing records for BIDOO/T2 are associated using the unique BID so the call can be billed properly.

[0908] 8.3.5.2 Call Transfer Without Consultation

[0909] As shown in FIG. 31, Call Transfer Without Consultation is very similar to Call Forwarding—No Answer.

[0910] 8.3.6 Return Call

[0911] It is possible for GCO to implement the return call service by storing the number of the most recent incoming call (caller id) in the Gate Controller, and then returning the call on a SETUP request. However, this requires the Gate Controller to retain state associated for every telephone. It would be desirable to allow the end-system (e.g., BTI) to retain this state, simplifying the Gate Controller. Unfortunately, if the incoming call was from a subscriber that has blocked caller id, it is important to keep the caller id information private, hence it cannot be made available to the end-system.

[0912] The solution is for the GC to send the caller id information to the BTI in a digitally signed and encrypted form, with every SETUP request. When a user dials the *69 code to activate the return call service, BTIO includes the encrypted information in the SETUP request to GCO. If GCO successfully decrypts and validates the information, and the customer subscribes to Return Call service, it returns the call as if processing a normal SETUP request to the number associated with the most recent incoming call.

Claims

1. A method for use in a packet-carrying communication network in which calls originating from respective originating interface units are routed through a routing entity of said network, the method comprising responsive to call setup requests originating from the originating interface units, establishing parameters for said calls on a call-by-call basis, and causing at least one of said established parameters to be stored in said routing entity, said routing entity operating to ensure that access to resources of said network is consistent with said at least one of said stored parameters.

2. The invention of claim 1 wherein said routing entity is a network edge device.

3. The invention of claim 2 wherein said network edge device is a router.

4. The invention of claim 2 wherein said network edge device is a bridge.

5. The invention of claim 2 wherein said originating interface units are connected to said network edge device via an access network.

6. The invention of claim 1 wherein the parameters established for at least ones of said calls include at least one of: a source network address and a destination network address.

7. The invention of claim 1 wherein the quality of service for at least ones of said calls is determined by at least one of the parameters established for those calls.

8. The invention of claim 1 wherein at least one of said parameters established for a call controls at least one of: bandwidth, bounded packet loss and latency.

9. The invention of claim 1 wherein the parameters established for a call include at least one of: packet size and inter-packet interval.

10. The invention of claim 1 wherein the parameters established for a call include at least one of: transmission priority and compression bit rate.

11. The invention of claim 1 wherein the parameters established for a call include operation, policy and traffic parameters.

12. The invention of claim 1 wherein said parameters established for a call are established by a gate controller, said gate controller thereupon communicating those parameters to said routing entity, said gate controller being an entity of said network through which calls are not routed.

13. The invention of claim 12 wherein said routing entity is a network edge device.

14. The invention of claim 1 further comprising establishing a gate for said each call at said network edge device, said gate being a call-admission control mechanism for a call defined at least in part by the parameters established for the call.

15. The invention of 14 wherein the parameters established for a call are established by a gate controller that communicates with said originating interface units.

16. A method for use in a packet-carrying communication network in which calls originating from respective originating interface units are routed through a routing entity of said network, the method comprising responsive to call setup requests originating from the originating interface units, establishing parameters for each of said calls on a call-by-call basis, the quality of service for said each call being determined by at least one of the parameters established for that call, causing at least one of said established parameters to be stored in said routing entity, receiving at said routing entity packets for said each call from the respective originating interface unit, said routing entity routing those packets to said network and said routing entity utilizing said at least one of said parameters to control admission of said packets into said network in such a way as to provide a quality of service for said call that is no greater than a quality of service previously authorized for that call.

17. The invention of claim 16 wherein said at least one of the parameters is received by said routing entity from a gate controller through which said calls are not routed.

18. The invention of claim 17 wherein said parameters established for said each call and stored at said routing entity include billing parameters for that call.

19. The invention of claim 18 further comprising tracking resource usage at said routing entity for said each call.

20. The invention of claim 17 wherein said parameters established for said each call and stored at said routing entity include at least one of: a source network address and a destination network address.

21. The invention of claim 16 wherein said routing entity is a network edge device.

22. The invention of claim 21 wherein said network edge device is a router.

23. The invention of claim 17 wherein said network edge device is a bridge.

24. The invention of claim 21 wherein said originating interface units are connected to said network edge device via an access network.

25. The invention of claim 16 wherein at least one of said parameters for said each call controls its bandwidth.

26. The invention of claim 16 wherein the parameters established for said each call that determine its quality of service include packet size and inter-packet interval.

27. The invention of claim 16 wherein the parameters established for said each call that determine its quality of service include at least one of: transmission priority and compression bit rate.

28. The invention of claim 16 wherein the parameters established for said each call include operation, policy and traffic parameters.

29. The invention of claim 16 wherein said parameters for said each call are used in a gate established for said each call at said network edge device, said gate being a call-admission control mechanism for said each call defined at least in part by said parameters established for that call.

30. Apparatus for use in a packet-carrying communication network in which calls originating from respective originating interface units are routed through a routing entity of said network, the apparatus comprising means for establishing parameters for each of said calls on a call-by-call basis in response call setup requests originating from the originating interface units, and means for causing at least one of said established parameters to be stored in said routing entity, whereby said routing entity is able to operate in such a way as to ensure that access to resources of said network during said each call is consistent with said at least one of said stored parameters.

31. The invention of claim 30 wherein said routing entity is a network edge device.

32. The invention of claim 30 wherein the parameters established for at least ones of said calls include at least one of: a source network address and a destination network address.

33. The invention of claim 30 wherein the quality of service for at least ones of said calls is determined by at least one of the parameters established for those calls.

34. The invention of claim 30 wherein at least one of said parameters established for said each call controls at least one of the call's bandwidth, bounded packet loss and latency.

35. The invention of claim 33 wherein said parameters that determine quality of service include packet size and inter-packet interval.

36. The invention of claim 33 wherein said parameters that determine quality include at least one of: transmission priority and compression bit rate.

37. The invention of claim 30 wherein the parameters established for said each call include operation, policy and traffic parameters.

38. The invention of claim 30 wherein said apparatus is a gate controller not adapted to route packets during said calls.

39. The invention of 38 wherein said means for causing at least one of said established parameters to be stored in said routing entity comprises means for establishing a gate for said each call at said routing entity, said gate being a call-admission control mechanism for said each call defined at least in part by said parameters established for the call.

40. A packet routing device for use in a packet-carrying communication network in which calls originating from respective originating interface units are routed through said packet routing device, the packet routing device comprising means for receiving and storing parameters that were established for said calls on a call-by-call basis responsive to call setup requests originating from the originating interface units, and means for routing to said network packets that were received for each call from the respective originating interface unit, said packet routing device being adapted to utilize said at least one of said parameters to control admission of said packets into said network.

41. The invention of claim 40 wherein said parameters established for said each call and stored at said routing entity include billing parameters for that call.

42. The invention of claim 41 further comprising means for tracking resource usage at said routing entity for said each call.

43. The invention of claim 40 wherein said parameters established for said each call and stored at said routing entity include at least one of: a source network address and a destination network address.

44. The invention of claim 40 wherein said packet routing device is a router.

45. The invention of claim 40 wherein said packet routing device is a bridge.

46. The invention of claim 40 wherein at least one of said parameters for said each call controls its bandwidth.

47. The invention of claim 40 wherein the parameters established for said each call include packet size and inter-packet interval.

48. The invention of claim 40 wherein the parameters established for said each call include at least one of: transmission priority and compression bit rate.

49. The invention of claim 40 wherein the parameters established for said each call include operation, policy and traffic parameters.

50. The invention of claim 40 wherein said parameters for said each call are used in a gate established for said each call at said packet routing device, said gate being a call-admission control mechanism for said each call defined at least in part by said parameters established for the call.