US20080049783A1 - Network controller and method to support format negotiation between interfaces of a network - Google Patents
Network controller and method to support format negotiation between interfaces of a network Download PDFInfo
- Publication number
- US20080049783A1 US20080049783A1 US11/932,601 US93260107A US2008049783A1 US 20080049783 A1 US20080049783 A1 US 20080049783A1 US 93260107 A US93260107 A US 93260107A US 2008049783 A1 US2008049783 A1 US 2008049783A1
- Authority
- US
- United States
- Prior art keywords
- network
- protocol
- bearer
- gateway
- format
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
- H04L2012/5614—User Network Interface
- H04L2012/5618—Bridges, gateways [GW] or interworking units [IWU]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A controller of a communications network enables endpoints or multiple networks to intercommunicate using multiple types of bearer format (IP, TDM, ATM, Frame Relay, etc.), and enables a bearer format conversion when necessary to carry bearer channel information across an interface of the network. The network may be packet-based or circuit-based and may include gateways and associated controllers which work in tandem to transfer format conversion parameters between endpoints or networks. The format control parameters are exchanged between various controllers, i.e., call control elements, to determine the appropriate format to forward the bearer channel information across the interface and to instruct the associated gateway of the required format conversion. The determination of the necessary format conversions may occur on a call-by-call basis, or by periodically detecting and storing format conversions associated with the various endpoints and intercommunicating networks. A corresponding method is also disclosed.
Description
- This application is a continuation of co-pending U.S. patent application Ser. No. 10/140,518 filed May 7, 2002 entitled NETWORK CONTROLLER AND METHOD TO SUPPORT FORMAT NEGOTIATION BETWEEN INTERFACES OF A NETWORK, which is incorporated herein by reference.
- This invention relates to communication networks, but more specifically to a network controller and method that enables bearer format negotiation between interfaces of the network in order to facilitate communications between endpoints that support different transmission protocols.
- Data transfers occur over channels of communication networks under various transmission protocols, either circuit-based or packet-based. An example of a circuit-based transmission protocol is Time Division Multiplex (TDM). In a TDM protocol, a data stream is conveyed over a physical carrier at a constant bit rate with appropriate framing bits to enable synchronized detection of data. Packet-based transmission protocols, on the other hand, include Internet Protocol (IP) and Asynchronous Transfer Mode (ATM). ATM provides connection-oriented transport of data in fixed-length 53-byte cells while IP provides connectionless transport of data in variable length packets. Either protocol may be used to transport a bearer channel for multimedia, voice, video, or other real-time traffic.
- A problem occurs when the bearer channel is passed between networks, or between endpoints and networks, that use different transmission protocols. If an originating endpoint or node connects to a network via an IP interface, and the network uses ATM in its backbone, and the terminating endpoint or node connects to the network via a TDM interface, then conversions must take place between the different transmission protocol types in order for the endpoints to communicate with one another. Further, when one network using one bearer format connects to another network using another bearer format, any communication channel passing between the networks must encounter a conversion between bearer formats.
- There are numerous ways to handle this situation. One way involves providing parallel backbone networks for each type of transmission protocol, as well as gateways between the parallel networks to allow endpoints on different networks to intercommunicate. Each parallel network need only have a compatible interface to the other networks and endpoints that use the same bearer format. For example, multiple IP networks can easily interface to other networks and endpoints using IP as their bearer format. A gateway, on the other hand, may be required to interconnect, for example, an ATM-based network and a TDM-based network. Interconnecting incompatible networks via a gateway, while workable, has serious disadvantages. First, it is capital intensive, since multiple network types are deployed. Second, it is operationally complex since each network must be administered independently from one another.
- In view of the foregoing, an objective of the present invention is to provide a network controller and method thereof that permit network access via multiple bearer formats.
- It is another objective to enable a single-protocol network, such as ATM, that interconnects with networks or nodes that use other transmission protocols.
- Another objective of the present invention is to provide a method of format conversion that enables end-users to choose a format that is most appropriate for their needs and equipment capabilities.
- It is yet a further objective of the present invention to enable a network to lessen loads on network resources (e.g., reduced processing power, terminations, operations processes, etc.) while performing the required functions.
- In accordance with a first aspect of the invention, a communication network using one type of network transmission protocol transports data between and/or among respective nodes that may implement different packet-based or circuit-based transmission protocols, such as ATM, IP, or TDM. In combination with a network that includes plural intercommunicating nodes capable of transferring information according to one of several bearer formats, the first aspect of the invention comprises a controller that exchanges information with an associated node to determine, based on an exchange of control information with at least one other controller, a conversion required between the network transmission protocol and a bearer format of the associated node so that a gateway connected to the associated node may be instructed to perform the determined format conversion.
- In another aspect of the invention, a method of providing format conversion between an originating and a terminating node of a network comprises transferring between controllers associated with the originating and terminating nodes signaling information indicative of first and second format control parameters respectively associated with the originating and terminating nodes; in response to the first format control parameter, converting when necessary the first bearer format to a format compatible with the network to enable the originating node to communicate with the network; and, in response to the second format control parameter, converting when necessary the network protocol to a protocol compatible with the second bearer format to enable the terminating node to communicate with the network.
- Other features and aspects of the invention will become apparent upon review of the following description taken in connection with the accompanying drawing. The invention, though, is pointed out with particularity by the appended claims.
-
FIG. 1 shows a functional diagram of a multiprotocol network that includes a controller according to an aspect of the present invention. -
FIG. 1 shows amulti-protocol backbone network 10 that interfaces with multiple network types orendpoints 12, 14 (hereafternodes 12, 14) to efficiently transport bearer traffic over a communication channel between nodes. A packet-basedbackbone network 16, such as an IP or ATM network, is illustrated for purposes of this disclosure. For maximum efficiency and performance,network 16 is optimized for a dominant network protocol of ingress and egress traffic conveyed withnodes backbone network 16 via anATM Adaptation Layer 1 interface, thennetwork 16 is optimized for ATM transport. - To efficiently determine which, if any, bearer format conversion must occur for a particular communication channel over
paths gateway controllers originating node 12 uses an IP protocol and terminatingnode 14 uses a TDM protocol, then a conversion is performed between IP and TDM somewhere along the communication path. If the originating and terminating nodes use the same bearer format as that used by thebackbone network 16, then no conversion is required or performed. - In order for the gateway controllers to determine whether a conversion is to be performed, bearer format signaling procedures are performed at
gateway controllers controllers controllers respective nodes respective controller controller network 16 in conjunction with determined knowledge of the user's equipment linked with anode network 16, or via call setup signaling messages received from the user's equipment at call setup time. -
FIG. 1 also illustrates an architecture to support bearer format negotiation. The architecture includes aningress gateway 22, an egressgateway 24, and one ormore gateway controllers - Signaling interfaces are provided between
ingress gateway controller 26 and originatingnode 12; betweenegress gateway controller 28 and terminatingnode 14; and between ingress andegress gateway controllers Paths gateway controllers respective gateways path 18 supports a bearer channel interface betweeningress gateway 22 and originatingnode 12;path 20 supports a bearer channel betweenegress gateway 24 and terminatingnode 14;path 34 supports a bearer channel between ingress andegress gateways path 36 supports a signaling channel betweencontrollers ingress gateway 22 and originatingnode 12 comprisesbearer format 1; the format of the bearer traffic between ingress andegress gateways bearer format 2; and the format of the bearer channel betweenegress gateway 24 and terminatingnode 14 comprisesbearer format 3. - To provide efficiency in transport of ATM traffic, for example, there may be provided four types of gateways for each of the
gateways gateway -
- a. AAL1/ATM gateway—a gateway that enables an ATM AAL1-based originating or terminating node to interface with an ATM-based backbone network;
- b. AAL2/ATM gateway—a gateway that enables an ATM AAL2-based originating or terminating node to interface with an ATM-based backbone network;
- c. IP/ATM gateway—a gateway that enables an IP-based originating or terminating node to interface with an ATM-based backbone network; and
- d. TDM/ATM gateway—a gateway that enables a TDM-based originating or terminating node to interface with an ATM-based backbone network.
- Although four conversion functions are described, the gateways may perform any number of conversions, e.g. two or more. Further, the arrangement depicted in
FIG. 1 may be physical or logical. If it is logical, then the functionality of multiple elements may be combined together and performed in a single physical element. For example, a gateway controller and gateway may be combined into a single unit. Similarly, a single gateway controller may have the combined functionality of an originating and terminating gateway controller for a particular call. It is also important to note that a gateway controller and a gateway may perform “ingress functions” for some calls concurrently with “egress functions” for other calls. - To assist in determining how to adapt bearer traffic of potentially different formats, bearer format information is propagated throughout
network 16, bygateway controllers respective nodes controller 26, to another originating or terminating gateway controller, such ascontroller 28, by way of a parameter in, for example, a call setup message. The parameter is referred to as the bearer format parameter, which identifies the type of interface used between thenetwork 16 and each of the originating and terminatingnodes Controllers nodes nodes controllers - The illustrated embodiment uses an ATM backbone network and messages associated with a Bearer Independent Call Control (BICC) signaling protocol. However, different backbone transmission protocols (e.g., IP) with their associated signaling protocols (e.g., SIP) may also be used. The basic premise of passing bearer format information between the ingress and egress sides of a connection or interface on a backbone network in order to determine the appropriate format of data transport remains the same.
- Exemplary bearer formats carried over an ATM backbone are shown in Table 1 below.
TABLE 1 Ingress Format AAL1 IP TDM AAL2 Egress AAL1 AAL1 AAL1 AAL1 AAL1 format IP AAL1 IP over AAL5 IP over AAL5 AAL2 TDM AAL1 IP over AAL5 AAL1 AAL1 AAL2 AAL1 IP over AAL5 AAL2 AAL2 - Table 1 sets forth four basic rules, as follows:
-
- a) If a call enters
network 16 using AAL1 over an ATM interface atnode 12, the call is carried acrossnetwork 16 in the same format as it arrives. Any required format conversion is performed at theegress gateway 24. - b) If a call enters
network 16 over an IP interface ofnode 12, the bearer format is converted at theingress gateway 22 and carried acrossnetwork 16 as AAL1 if theegress gateway 24 is an AAL1/ATM gateway. The bearer format will be converted at the ingress gateway and carried across thenetwork 16 as IP over AAL5 if theegress gateway 24 is an IP/ATM, TDM/TM, or AAL2/ATM gateway, and any required subsequent format conversion will be performed at the egress gateway. - c) If a call enters
network 16 using AAL2 over an ATM interface atnode 12, the call will be carried acrossnetwork 16 as AAL2 if the egress gateway is either an IP/ATM or AAL2/ATM gateway, and any required format conversion is performed at theegress gateway 24. Ifegress gateway 24 is either an AAL1/ATM or TDM/ATM gateway, the bearer format will be converted at theingress gateway 22 and carried acrossnetwork 16 as AAL1. - d) If a call enters
network 16 over a TDM interface atnode 12, it is carried acrossnetwork 16 as AAL1 if the egress gateway is either an AAL1/ATM or TDM/ATM gateway, and the TDM to AAL1 format conversion will be performed at the ingress gateway, 22. Ifegress gateway 24 is an AAL2/ATM gateway, it will be carried acrossnetwork 16 as AAL2 and the TDM to AAL2 format conversion will be performed at theingress gateway 22. Ifegress gateway 24 is an IP gateway, it will be carried acrossnetwork 16 as IP over AAL5, and the TDM to IP over AAL5 format conversion will be performed a the ingress gateway, 22.
- a) If a call enters
- Table 2 identifies bearer format conversion rules to be followed in a network to support these procedures.
TABLE 2 Condition Operation If (ingress AND (egress interface = AAL1) then carry the call as AAL1 to the egress gateway; interface = AAL1) pass the call unchanged to the terminating node or network AND (egress interface = IP) then carry the call as AAL1 to the egress gateway; convert to IP at the egress gateway AND (egress interface = AAL2) then carry the call as AAL1 to the egress gateway; convert to AAL2 at the egress gateway AND (egress interface = TDM) then carry the call as AAL1 to the egress gateway; convert to TDM at the egress gateway If (ingress AND (egress interface = AAL1) then convert the call to AAL1 at the ingress interface = IP) gateway; carry the call as AAL1 to the egress gateway; pass the call unchanged to the terminating node or network AND (egress interface = IP) then convert the call to IP over AAL5 at the ingress gateway; carry the call as IP over AAL5 to the egress gateway; pass the call unchanged to the terminating node or network AND (egress interface = AAL2) then convert the call to IP over AAL5 at the ingress gateway; carry the call as IP over AAL5 to the egress gateway; convert to AAL2 at the egress gateway AND (egress interface = TDM) then convert the call to IP over AAL5 at the ingress gateway; carry the call as IP over AAL5 to the egress gateway; convert to TDM at the egress gateway If (ingress AND (egress interface = AAL1) then convert the call to AAL1 at the ingress interface = AAL2) gateway; carry the call as AAL1 to the egress gateway AND (egress interface = IP) then carry the call as AAL2 to the egress gateway; convert to IP at the egress gateway AND (egress interface = AAL2) then carry the call as AAL2 to the egress gateway; pass the call unchanged to the terminating node or network AND (egress interface = TDM) then convert the call to AAL1 at the ingress gateway; carry the call as AAL1 to the egress gateway; convert to TDM at the egress gateway If (ingress AND (egress interface = AAL1) then convert the call to AAL1 at the ingress interface = TDM) gateway; carry the call as AAL1 to the egress gateway AND (egress interface = IP) then convert the call to IP over AAL5 at the ingress gateway; carry the call as IP over AAL5 to the egress gateway AND (egress interface = AAL2) then convert the call to AAL2 at the ingress gateway; carry the call as AAL2 to the egress gateway AND (egress interface = TDM) then convert the call to AAL1 at the ingress gateway; carry the call as AAL1 to the egress gateway; convert to TDM at the egress gateway - In order for
controllers gateway controllers gateways gateway controllers nodes bearer format 2 ofFIG. 1 ) is ATM. Similar procedures may also be developed based on different backbone bearer formats, such as IP, TDM, or Frame Relay. - The operation may be described, starting with an exemplary routine executed at an originating
node 12. At originatingnode 12, a call setup message (e.g., an Initial Address Message (IAM)) is sent togateway controller 26 for the connection betweennode 12 andingress gateway 22, similar to the way call setup is initiated for a switch or other conventional call control element. This call setup message may contain a bearer format parameter that provides an indication ofbearer format 1. Upon receipt of the call setup message from originatingnode 12, and based on information contained in said message,controller 26 determines thatingress gateway 22 ofnetwork 16 will receive the bearer channel of the call, and thategress gateway controller 28 will control the egress gateway for the call.Controller 26 next attempts to determine thepreferred bearer format 2 for transporting the bearer channel acrossnetwork 16. This may be accomplished according to the following routine: -
- If (ingress interface=AAL1), then
- send the call setup message to the egress gateway controller, indicating that ATM AAL1 will be used as the bearer format in the backbone network; instruct the ingress gateway to pass the bearer unchanged, as AAL1
- If (ingress interface=IP) then
- send the call setup message to the egress gateway controller, indicating that IP is used as the bearer format on the ingress interface
- If (ingress interface=AAL2) then
- send the call setup message to the egress gateway controller, indicating that AAL2 is used as the bearer format on the ingress interface
- If (ingress interface=TDM) then
- send the call setup message to the egress gateway controller, indicating that TDM is used as the bearer format on the ingress interface
- Upon receipt of the call setup acknowledgement message [e.g., Address Complete Message (ACM)] from the egress gateway controller,
- If (ingress interface=AAL2) then
- If (egress interface=AAL1) then
- instruct the ingress gateway to convert the bearer to AAL1
- If (egress interface=IP) then
- instruct the ingress gateway to keep the bearer as AAL2
- If (egress interface=AAL2) then
- instruct the ingress gateway to keep the bearer as AAL2
- If (egress interface=TDM) then
- instruct the ingress gateway to convert the bearer to AAL1;
- If (egress interface=AAL1) then
- Else if (ingress interface=TDM) then
- If (egress interface=AAL1) then
- instruct the ingress gateway to convert the bearer to AAL1
- If (egress interface=IP) then
- instruct the ingress gateway to convert the bearer to IP over AAL5
- If (egress interface=AAL2) then
- instruct the ingress gateway to convert the bearer to AAL2
- If (egress interface=TDM) then
- instruct the ingress gateway to convert the bearer to AAL1
- If (egress interface=AAL1) then
- Else if (ingress interface=IP) then
- If (egress interface=AAL1) then
- instruct the ingress gateway to convert the bearer to AAL1
- If (egress interface=IP) then
- instruct the ingress gateway to convert the bearer to IP over AAL5
- If (egress interface=AAL2) then
- instruct the ingress gateway to convert the bearer to IP over AAL5
- If (egress interface=TDM) then
- instruct the ingress gateway to convert the bearer to IP over AAL5
- If (egress interface=AAL1) then
- Else if (ingress interface=AAL1) then
- Do nothing
- If (ingress interface=AAL2) then
- Pass the call setup acknowledgment to the originating node or network.
- If (ingress interface=AAL1), then
- Upon receipt of a call setup message from
ingress gateway controller 26,egress gateway controller 28 determines which egress gateway will receive the bearer channel of the call based on the standard information contained in the call setup message. Thereafter, the call setup message is sent to the terminating node or network, in this case,node 14. - In response to an incoming call setup message from the gateway controller for the egress gateway, terminating
node 14 sends an address complete (ACM) message to the gateway controller for the egress gateway, which may include a bearer format parameter indicatingbearer format 3. - Upon receipt of the call setup acknowledgment message from the terminating node or network, an operation is performed, which is described in connection with an exemplary routine executed at
egress gateway controller 28, as follows: -
- If (egress interface=AAL1), then
- If (ingress interface=AAL1) then
- instruct the egress gateway to pass the bearer unchanged, as AAL1 on the egress interface
- If (ingress interface=IP) then
- instruct the egress gateway to convert the bearer channel from AAL1 to IP on the egress interface
- If (ingress interface=AAL2) then
- instruct the egress gateway to convert the bearer channel from AAL1 to AAL2 on the egress interface
- If (ingress interface=TDM) then
- instruct the egress gateway to convert the bearer channel from AAL1 to TDM on the egress interface;
- If (ingress interface=AAL1) then
- Else if (egress interface=IP) then
- If (ingress interface=AAL1) then
- instruct the egress gateway to convert the bearer channel from AAL1 to IP on the egress interface
- If (ingress interface=IP) then
- instruct the egress gateway to convert the bearer channel from IP over AAL5 to IP on the egress interface
- If (ingress interface=AAL2) then
- instruct the egress gateway to convert the bearer channel from AAL2 to IP on the egress interface
- If (ingress interface=TDM) then
- instruct the egress gateway to convert the bearer channel from IP over AAL5 to IP on the egress interface;
- If (ingress interface=AAL1) then
- Else if (egress interface=AAL2) then
- If (ingress interface=AAL1) then
- instruct the egress gateway to convert the bearer channel from AAL1 to AAL2 on the egress interface
- If (ingress interface=IP) then
- instruct the egress gateway to convert the bearer channel from IP over AAL5 to AAL2 on the egress interface
- If (ingress interface=AAL2) then
- instruct the egress gateway to pass the bearer unchanged, as AAL2 on the egress interface
- If (ingress interface=TDM) then
- instruct the egress gateway to pass the bearer unchanged, as AAL2 on the egress interface;
- If (ingress interface=AAL1) then
- Else if (egress interface=TDM) then
- If (ingress interface=AAL1) then
- instruct the egress gateway to convert the bearer channel from AAL1 to TDM on the egress interface
- If (ingress interface=IP) then
- instruct the egress gateway to convert the bearer channel from IP over AAL5 to TDM on the egress interface
- If (ingress interface=AAL2) then
- instruct the egress gateway to convert the bearer channel from AAL1 to TDM on the egress interface
- If (ingress interface=TDM) then
- instruct the egress gateway to convert the bearer channel from AAL1 to TDM on the egress interface.
- If (ingress interface=AAL1) then
- If (egress interface=AAL1), then
- After the above operation is completed,
egress gateway controller 28 sends the call setup acknowledgment message toingress gateway controller 26, with an indication (in the bearer format parameter) of the type of egress interface used ongateway 24. - Based on the above teachings, the illustrated embodiment described herein may be modified or altered by persons skilled in the art without departing from the scope of the invention, as defined by the appended claims. Thus, it is the intent to include within the scope of the invention all such modifications as may come to the skilled artisan.
Claims (19)
1. A communication network wherein the network comprises a plurality of intercommunicating nodes capable of transferring information according to at least one bearer format, comprising:
a controller that exchanges information with an associated node to determine, based on an exchanged of control information with at least one other controller, a conversion required between a network transmission protocol and a bearer format of the associated node so that a gateway connected to the associated node is instructed to perform the conversion.
2. The network of claim 1 , wherein the exchanged information includes voice signals.
3. The network of claim 1 , wherein the bearer formats of the nodes comprise at least two different bearer formats.
4. The network of claim 1 , wherein exchanged control information is carried in a bearer format parameter that identifies the bearer formats at the associated nodes.
5. The network of claim 1 , wherein the network transmission protocol and the bearer formats are packet-based.
6. The network of claim 5 , wherein said packet-based network transmission protocol and bearer formats include at least one of: ATM, IP, or Frame Relay.
7. The network of claim 1 , wherein the network transmission protocol and the bearer formats are circuit-based.
8. The network of claim 7 , wherein the circuit-based network transmission protocol and the bearer formats include Time Division Multiplex (TDM).
9. The network of claim 4 , wherein the controller determines format conversion on a call-by-call basis.
10. The network of claim 4 , wherein the controller receives from a node a bearer format parameter indicating a bearer format used by the associated node and, in response, instructs a gateway to perform a conversion to render the node compatible with the network.
11. The network of claim 10 , wherein the bearer format parameter is carried in a signaling protocol between multiple controllers.
12. The network of claim 11 , wherein the signaling protocol comprises at least one of: a Bearer Independent Call Control (BICC) protocol, a Session Initiation Protocol (SIP), a SIP-T protocol, an ISDN User Part (ISUP) protocol, a Broadband ISUP (B-ISUP) protocol, or an H.323 protocol.
13. The network of claim 4 , wherein the bearer format parameter is carried in a signaling protocol between controllers and gateways.
14. The network of claim 13 , wherein the signaling protocol comprises at least one of: a Media Gateway Control Protocol (MGCP), an H.248 protocol, or a Trunking Gateway Control Protocol (TGCP).
15. The network of claim 4 , wherein the bearer format parameter is carried in a signaling protocol between controllers and nodes.
16. The network of claim 15 , wherein the signaling protocol comprises at least one of: a Q.931 protocol, a Q.2931 protocol, a Media Gateway Control Protocol (MGCP), an H.248 protocol, an H.323 protocol, and a Network-based Call Signaling (NCS) protocol.
17. A network capable of transferring data between originating and destination nodes according to respective transmission protocols, the network including an originating gateway associated with the originating node and responsive to a first controller to effect conversion of a first bearer format to a protocol compatible with the network and a destination gateway associated with the destination node and responsive to a second controller to effect conversion of the protocol of the network to a bearer format of the destination node, the improvement comprising:
a signaling protocol to transfer control information between the first and second controllers to effect an exchange of bearer format information related to the originating and destination nodes, said signaling protocol providing a basis for format conversion at the respective gateways.
18. The network of claim 17 , wherein said signaling protocol includes a bearer format parameter that identifies a format used by the originating and destination nodes.
19. The network of claim 18 , wherein the network comprises multiple nodes having associated gateways and controllers, and said bearer format parameter is propagated within the network to multiple controllers of multiple gateways.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/932,601 US20080049783A1 (en) | 2002-05-07 | 2007-10-31 | Network controller and method to support format negotiation between interfaces of a network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/140,518 US7346076B1 (en) | 2002-05-07 | 2002-05-07 | Network controller and method to support format negotiation between interfaces of a network |
US11/932,601 US20080049783A1 (en) | 2002-05-07 | 2007-10-31 | Network controller and method to support format negotiation between interfaces of a network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/140,518 Continuation US7346076B1 (en) | 2002-05-07 | 2002-05-07 | Network controller and method to support format negotiation between interfaces of a network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080049783A1 true US20080049783A1 (en) | 2008-02-28 |
Family
ID=39113391
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/140,518 Expired - Fee Related US7346076B1 (en) | 2002-05-07 | 2002-05-07 | Network controller and method to support format negotiation between interfaces of a network |
US11/932,601 Abandoned US20080049783A1 (en) | 2002-05-07 | 2007-10-31 | Network controller and method to support format negotiation between interfaces of a network |
US12/030,151 Expired - Fee Related US7746893B2 (en) | 2002-05-07 | 2008-02-12 | Network controller and method to support format negotiation between interfaces of a network |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/140,518 Expired - Fee Related US7346076B1 (en) | 2002-05-07 | 2002-05-07 | Network controller and method to support format negotiation between interfaces of a network |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/030,151 Expired - Fee Related US7746893B2 (en) | 2002-05-07 | 2008-02-12 | Network controller and method to support format negotiation between interfaces of a network |
Country Status (1)
Country | Link |
---|---|
US (3) | US7346076B1 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040120498A1 (en) * | 2002-12-20 | 2004-06-24 | Nortel Networks Limited | Interworking of multimedia and telephony equipment |
US20080056243A1 (en) * | 2003-02-11 | 2008-03-06 | Roy Radhika R | Access independent common architecture for real-time communications services for networking environments |
US20080144659A1 (en) * | 2002-05-07 | 2008-06-19 | Habiby Samer A | Network controller and method to support format negotiation between interfaces of a network |
US7496192B1 (en) * | 2002-12-20 | 2009-02-24 | Nortel Networks Limited | Interworking of multimedia and telephony equipment |
US20090238195A1 (en) * | 2008-03-20 | 2009-09-24 | Jarkko Pyykkonen | Different ip interfaces in a communication network system |
GB2463006B (en) * | 2008-08-26 | 2011-03-16 | Cvon Innovations Ltd | Conversion management system, method and computer program |
US8705518B1 (en) | 2003-02-24 | 2014-04-22 | At&T Intellectual Property Ii, L.P. | Apparatus and method for controlling services and operations in converged communications networks |
US9165292B2 (en) | 2011-12-23 | 2015-10-20 | Mastercard International Incorporated | Systems and methods for a network-to-network interface |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7633929B1 (en) * | 2003-04-09 | 2009-12-15 | Cisco Technology, Inc. | Arrangement for providing ISUP transparency across voice over packet networks based on determined exchange type |
US7773588B2 (en) * | 2006-04-13 | 2010-08-10 | Directpacket Research, Inc. | System and method for cross protocol communication |
US8555371B1 (en) | 2009-07-17 | 2013-10-08 | Directpacket Research, Inc. | Systems and methods for management of nodes across disparate networks |
US7710978B2 (en) * | 2006-04-13 | 2010-05-04 | Directpacket Research, Inc. | System and method for traversing a firewall with multimedia communication |
US8605730B2 (en) * | 2006-04-13 | 2013-12-10 | Directpacket Research, Inc. | System and method for multimedia communication across disparate networks |
US8560828B2 (en) * | 2006-04-13 | 2013-10-15 | Directpacket Research, Inc. | System and method for a communication system |
FI20075575L (en) | 2007-08-16 | 2009-02-17 | Teliasonera Ab | Conversion system and method in a multi-operator environment |
CN103269289B (en) * | 2013-04-17 | 2016-03-16 | 中国人民解放军空军装备研究院雷达与电子对抗研究所 | Air traffic control radar information test method and equipment |
CN105704069B (en) * | 2014-11-26 | 2020-02-14 | 中兴通讯股份有限公司 | Method and device for saving processing resources in network element |
CN107302528A (en) * | 2017-06-12 | 2017-10-27 | 深圳市诺龙技术股份有限公司 | A kind of transmission method of multi-protocol data and a kind of gateway apparatus |
Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6018521A (en) * | 1996-12-27 | 2000-01-25 | Motorola, Inc. | Network interface subsystem for use in an ATM communications system |
US6034950A (en) * | 1996-12-27 | 2000-03-07 | Motorola Inc. | System packet-based centralized base station controller |
US6049543A (en) * | 1996-12-27 | 2000-04-11 | Motorola, Inc. | Transcoder for use in an ATM-based communications system |
US6185198B1 (en) * | 1996-03-20 | 2001-02-06 | Aeris Communications, Inc. | Time division multiple access downlink personal communications system voice and data debit billing method |
US20020036983A1 (en) * | 2000-05-22 | 2002-03-28 | Ina Widegren | Application influenced policy |
US20020154646A1 (en) * | 2001-03-21 | 2002-10-24 | Dubois Jean F. | Programmable network services node |
US20020176404A1 (en) * | 2001-04-13 | 2002-11-28 | Girard Gregory D. | Distributed edge switching system for voice-over-packet multiservice network |
US6490451B1 (en) * | 1999-12-17 | 2002-12-03 | Nortel Networks Limited | System and method for providing packet-switched telephony |
US20030227908A1 (en) * | 2000-05-04 | 2003-12-11 | Scoggins Shwu-Yan Chang | Method and apparatus for negotiating bearer control parameters using property sets |
US20040017773A1 (en) * | 2002-07-23 | 2004-01-29 | Eyeball Networks Inc. | Method and system for controlling the rate of transmission for data packets over a computer network |
US6707812B1 (en) * | 1999-06-02 | 2004-03-16 | Accenture Llp | System, method and article of manufacture for element management in a hybrid communication system |
US20040066783A1 (en) * | 2002-09-26 | 2004-04-08 | Deepak Ayyagari | Connection management in a centralized communication system |
US6721565B1 (en) * | 2000-08-07 | 2004-04-13 | Lucent Technologies Inc. | Handover of wireless calls between systems supporting circuit and packet call models |
US6775232B1 (en) * | 2000-05-11 | 2004-08-10 | Cisco Technology, Inc. | Method for scheduling data for communication on a digital subscriber line |
US20040196826A1 (en) * | 2003-04-02 | 2004-10-07 | Cellco Partnership As Verizon Wireless | Implementation methodology for client initiated parameter negotiation for PTT/VoIP type services |
US20040240469A1 (en) * | 2001-05-18 | 2004-12-02 | Martin Stumpert | Method and devices for the interworking of nodes |
US6862622B2 (en) * | 1998-07-10 | 2005-03-01 | Van Drebbel Mariner Llc | Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture |
US20050232296A1 (en) * | 2004-03-24 | 2005-10-20 | Stephan Schultze | Method for data transmission |
US20050232284A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Providing automatic format conversion via an access gateway in a home |
US20060002325A1 (en) * | 2003-07-12 | 2006-01-05 | Samsung Electronics Co., Ltd. | Method for controlling conversion of vocoder mode in a mobile communication system |
US20060078000A1 (en) * | 1999-02-10 | 2006-04-13 | Mika Rinne | Method for informing layers of a protocol stack about the protocol in use |
US7092378B1 (en) * | 2001-12-10 | 2006-08-15 | At & T Corp. | System for utilizing a genetic algorithm to provide constraint-based routing of packets in a communication network |
US7200387B1 (en) * | 2004-09-01 | 2007-04-03 | Cellco Partnership | Application invocation on a mobile station using messaging service |
US7346076B1 (en) * | 2002-05-07 | 2008-03-18 | At&T Corp. | Network controller and method to support format negotiation between interfaces of a network |
-
2002
- 2002-05-07 US US10/140,518 patent/US7346076B1/en not_active Expired - Fee Related
-
2007
- 2007-10-31 US US11/932,601 patent/US20080049783A1/en not_active Abandoned
-
2008
- 2008-02-12 US US12/030,151 patent/US7746893B2/en not_active Expired - Fee Related
Patent Citations (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6185198B1 (en) * | 1996-03-20 | 2001-02-06 | Aeris Communications, Inc. | Time division multiple access downlink personal communications system voice and data debit billing method |
US6018521A (en) * | 1996-12-27 | 2000-01-25 | Motorola, Inc. | Network interface subsystem for use in an ATM communications system |
US6049543A (en) * | 1996-12-27 | 2000-04-11 | Motorola, Inc. | Transcoder for use in an ATM-based communications system |
US6034950A (en) * | 1996-12-27 | 2000-03-07 | Motorola Inc. | System packet-based centralized base station controller |
US6862622B2 (en) * | 1998-07-10 | 2005-03-01 | Van Drebbel Mariner Llc | Transmission control protocol/internet protocol (TCP/IP) packet-centric wireless point to multi-point (PTMP) transmission system architecture |
US20060078000A1 (en) * | 1999-02-10 | 2006-04-13 | Mika Rinne | Method for informing layers of a protocol stack about the protocol in use |
US6707812B1 (en) * | 1999-06-02 | 2004-03-16 | Accenture Llp | System, method and article of manufacture for element management in a hybrid communication system |
US6490451B1 (en) * | 1999-12-17 | 2002-12-03 | Nortel Networks Limited | System and method for providing packet-switched telephony |
US20030227908A1 (en) * | 2000-05-04 | 2003-12-11 | Scoggins Shwu-Yan Chang | Method and apparatus for negotiating bearer control parameters using property sets |
US6775232B1 (en) * | 2000-05-11 | 2004-08-10 | Cisco Technology, Inc. | Method for scheduling data for communication on a digital subscriber line |
US20020036983A1 (en) * | 2000-05-22 | 2002-03-28 | Ina Widegren | Application influenced policy |
US6721565B1 (en) * | 2000-08-07 | 2004-04-13 | Lucent Technologies Inc. | Handover of wireless calls between systems supporting circuit and packet call models |
US20020154646A1 (en) * | 2001-03-21 | 2002-10-24 | Dubois Jean F. | Programmable network services node |
US20020176404A1 (en) * | 2001-04-13 | 2002-11-28 | Girard Gregory D. | Distributed edge switching system for voice-over-packet multiservice network |
US20040240469A1 (en) * | 2001-05-18 | 2004-12-02 | Martin Stumpert | Method and devices for the interworking of nodes |
US7092378B1 (en) * | 2001-12-10 | 2006-08-15 | At & T Corp. | System for utilizing a genetic algorithm to provide constraint-based routing of packets in a communication network |
US7346076B1 (en) * | 2002-05-07 | 2008-03-18 | At&T Corp. | Network controller and method to support format negotiation between interfaces of a network |
US20080144659A1 (en) * | 2002-05-07 | 2008-06-19 | Habiby Samer A | Network controller and method to support format negotiation between interfaces of a network |
US20040017773A1 (en) * | 2002-07-23 | 2004-01-29 | Eyeball Networks Inc. | Method and system for controlling the rate of transmission for data packets over a computer network |
US20040066783A1 (en) * | 2002-09-26 | 2004-04-08 | Deepak Ayyagari | Connection management in a centralized communication system |
US20040196826A1 (en) * | 2003-04-02 | 2004-10-07 | Cellco Partnership As Verizon Wireless | Implementation methodology for client initiated parameter negotiation for PTT/VoIP type services |
US20060002325A1 (en) * | 2003-07-12 | 2006-01-05 | Samsung Electronics Co., Ltd. | Method for controlling conversion of vocoder mode in a mobile communication system |
US20050232296A1 (en) * | 2004-03-24 | 2005-10-20 | Stephan Schultze | Method for data transmission |
US20050232284A1 (en) * | 2004-04-16 | 2005-10-20 | Jeyhan Karaoguz | Providing automatic format conversion via an access gateway in a home |
US7200387B1 (en) * | 2004-09-01 | 2007-04-03 | Cellco Partnership | Application invocation on a mobile station using messaging service |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080144659A1 (en) * | 2002-05-07 | 2008-06-19 | Habiby Samer A | Network controller and method to support format negotiation between interfaces of a network |
US7746893B2 (en) | 2002-05-07 | 2010-06-29 | At&T Intellectual Property Ii, L.P. | Network controller and method to support format negotiation between interfaces of a network |
US7496192B1 (en) * | 2002-12-20 | 2009-02-24 | Nortel Networks Limited | Interworking of multimedia and telephony equipment |
US20040120498A1 (en) * | 2002-12-20 | 2004-06-24 | Nortel Networks Limited | Interworking of multimedia and telephony equipment |
US7920690B2 (en) | 2002-12-20 | 2011-04-05 | Nortel Networks Limited | Interworking of multimedia and telephony equipment |
US20080056243A1 (en) * | 2003-02-11 | 2008-03-06 | Roy Radhika R | Access independent common architecture for real-time communications services for networking environments |
US8625578B2 (en) * | 2003-02-11 | 2014-01-07 | At&T Intellectual Property Ii, L.P. | Access independent common architecture for real-time communications services for networking environments |
US8705518B1 (en) | 2003-02-24 | 2014-04-22 | At&T Intellectual Property Ii, L.P. | Apparatus and method for controlling services and operations in converged communications networks |
US20090238195A1 (en) * | 2008-03-20 | 2009-09-24 | Jarkko Pyykkonen | Different ip interfaces in a communication network system |
WO2009115126A1 (en) * | 2008-03-20 | 2009-09-24 | Nokia Siemens Networks Oy | Different ip interfaces in a communication network system |
GB2463006B (en) * | 2008-08-26 | 2011-03-16 | Cvon Innovations Ltd | Conversion management system, method and computer program |
US9043432B2 (en) | 2008-08-26 | 2015-05-26 | Apple Inc. | Converting content prior to delivery |
US9165292B2 (en) | 2011-12-23 | 2015-10-20 | Mastercard International Incorporated | Systems and methods for a network-to-network interface |
US9306770B2 (en) | 2011-12-23 | 2016-04-05 | Mastercard International Incorporated | Systems and methods for extending an existing network |
Also Published As
Publication number | Publication date |
---|---|
US20080144659A1 (en) | 2008-06-19 |
US7346076B1 (en) | 2008-03-18 |
US7746893B2 (en) | 2010-06-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7746893B2 (en) | Network controller and method to support format negotiation between interfaces of a network | |
US6683877B1 (en) | Carrying voice traffic over broad band networks | |
EP1247420B1 (en) | Method and apparatus for providing efficient application-level switching for multiplexed internet protocol media streams | |
EP0841831B1 (en) | Wan-based voice gateway | |
US6396840B1 (en) | Method, interface and system for connecting communication traffic across an intermediate network | |
US7088723B2 (en) | System and method for enhancing a voice channel in voice over internet protocol | |
US6765912B1 (en) | Network resource usage in call sessions | |
US20060133359A1 (en) | Multiprotocol convergence switch (MPCS) and method for use thereof | |
US6714544B1 (en) | Method and apparatus for proxied signalling of an end to end connection across a connection oriented network | |
JPH10341242A (en) | Logic link connection server | |
US6021136A (en) | Telecommunication network that reduces tandeming of compressed voice packets | |
JP3923533B2 (en) | ATM partial cut-through | |
KR100277134B1 (en) | Apparatus and method for connecting frame relay device through AMT network using frame relay proxy signal agent | |
WO2003096648A1 (en) | Dynamic call control | |
EP1021890B1 (en) | Virtual path merging in a multipoint-to-point network tunneling protocol | |
US7085264B2 (en) | System and method for controlling media gateways that interconnect disparate networks | |
US6937598B1 (en) | Method and apparatus for transporting ATM cell traffic over IP networks | |
US7283533B1 (en) | Interworking of packet-based voice technologies using virtual TDM trunks | |
US7477638B1 (en) | Interworking of IP voice with ATM voice using server-based control | |
JP2002204270A (en) | Method and device for backhauling call signalling for multiple protocol | |
Cisco | VISM Functional Description | |
CA2379437A1 (en) | Communications using hybrid circuit-switched and packet-switched networks | |
KR100674338B1 (en) | An Interworking unit transmitting internet phone packets using ATM AAL2 function and method thereof | |
KR100397470B1 (en) | Voice over IP and voice over ATM interworking system | |
Sreetharan et al. | ATM Interworking in Broadband Wireless Applications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |