| Network controller and method to support format negotiation between interfaces of a network -> Monitor Keywords |
|
|
  Network controller and method to support format negotiation between interfaces of a networkUSPTO Application #: 20080049783Title: Network controller and method to support format negotiation between interfaces of a network 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. (end of abstract) Agent: At&t Corp. - Bedminster, NJ, US Inventors: Samer A. Habiby, Steven M. Michelson USPTO Applicaton #: 20080049783 - Class: 370466000 (USPTO) Related Patent Categories: Multiplex Communications, Communication Techniques For Information Carried In Plural Channels, Adaptive, Converting Between Protocols The Patent Description & Claims data below is from USPTO Patent Application 20080049783. Brief Patent Description - Full Patent Description - Patent Application Claims
[0001] 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. BACKGROUND OF THE INVENTION [0002] 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. [0003] 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. [0004] 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. [0005] 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. [0006] 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. [0007] It is another objective to enable a single-protocol network, such as ATM, that interconnects with networks or nodes that use other transmission protocols. [0008] 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. [0009] 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. SUMMARY OF THE INVENTION [0010] 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. [0011] 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. [0012] 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. BRIEF DESCRIPTION OF THE DRAWINGS [0013] FIG. 1 shows a functional diagram of a multiprotocol network that includes a controller according to an aspect of the present invention. DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS [0014] FIG. 1 shows a multi-protocol backbone network 10 that interfaces with multiple network types or endpoints 12, 14 (hereafter nodes 12, 14) to efficiently transport bearer traffic over a communication channel between nodes. A packet-based backbone 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 with nodes 12, 14. For example, if most of the nodes connect to the backbone network 16 via an ATM Adaptation Layer 1 interface, then network 16 is optimized for ATM transport. [0015] To efficiently determine which, if any, bearer format conversion must occur for a particular communication channel over paths 18, 20, the gateway controllers 26, 28 determine the bearer format used at each of the nodes. If, for example, an originating node 12 uses an IP protocol and terminating node 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 the backbone network 16, then no conversion is required or performed. [0016] In order for the gateway controllers to determine whether a conversion is to be performed, bearer format signaling procedures are performed at gateway controllers 26, 28, and signaling messages, including respective bearer format parameters associated with the endpoints, are exchanged among controllers 26, 28, and between controllers 26, 28 and respective nodes 12,14. The signaling procedures and message exchanges allow internodal transfer of the type of bearer format used along every path in a particular communication channel between nodes, and also enable a microprocessor in the gateway controller to determine whether to activate a conversion function of the gateway which it controls. Each gateway may have the functionality to support multiple, i.e., two or more transmission protocols stored therein. The conversion function of the gateway is ready to be activated in response to commands from a respective controller 26, 28 that include the format conversion parameter. Upon initiation of a call, the controller 26, 28 determines the needed conversion based on a memory map of bearer format requirements for the respective nodes that have previously been propagated throughout the network 16 in conjunction with determined knowledge of the user's equipment linked with a node 12, 14. The knowledge of the user's equipment may be determined either by information previously propagated throughout the network 16, or via call setup signaling messages received from the user's equipment at call setup time. [0017] FIG. 1 also illustrates an architecture to support bearer format negotiation. The architecture includes an ingress gateway 22, an egress gateway 24, and one or more gateway controllers 26, 28. Gateways perform bearer format conversion, enabling a call to pass between networks using different internal bearer formats. In the simplest sense, the gateway may also perform a null format conversion. The gateway further includes an interface that allows a gateway controller to instruct which, if any, conversion is needed on a call-by-call or per-connection basis where routines for the various transmission protocol definitions and manner of conversions are stored in a memory associated with the gateway. A gateway controller is one of many types of call control elements having a signaling interface to communicate with other call control elements, as well as a control interface to communicate with the gateways which it controls. As used herein, a call control element is generally a stored program control device that contains logic used to control the setup, tear down, and services for a call. [0018] Signaling interfaces are provided between ingress gateway controller 26 and originating node 12; between egress gateway controller 28 and terminating node 14; and between ingress and egress gateway controllers 26, 28. Paths 30, 32 support respective control interfaces between gateway controllers 26, 28 and their respective gateways 22, 24. In addition, path 18 supports a bearer channel interface between ingress gateway 22 and originating node 12; path 20 supports a bearer channel between egress gateway 24 and terminating node 14; path 34 supports a bearer channel between ingress and egress gateways 22, 24; path 36 supports a signaling channel between controllers 26, 28. The format of the bearer traffic between ingress gateway 22 and originating node 12 comprises bearer format 1; the format of the bearer traffic between ingress and egress gateways 22, 24 comprises bearer format 2; and the format of the bearer channel between egress gateway 24 and terminating node 14 comprises bearer format 3. [0019] To provide efficiency in transport of ATM traffic, for example, there may be provided four types of gateways for each of the gateways 22, 24. In a preferred embodiment that uses an ATM-based backbone network, each gateway 22, 24 provides a bearer interworking function between ATM and various bearer format types. Other backbone networks could also be used, such as an IP-based backbone network having comparable gateways suitable for that type of network. For purposes of this disclosure, exemplary gateways include: [0020] a. AAL1/ATM gateway--a gateway that enables an ATM AAL1-based originating or terminating node to interface with an ATM-based backbone network; [0021] b. AAL2/ATM gateway--a gateway that enables an ATM AAL2-based originating or terminating node to interface with an ATM-based backbone network; [0022] c. IP/ATM gateway--a gateway that enables an IP-based originating or terminating node to interface with an ATM-based backbone network; and [0023] d. TDM/ATM gateway--a gateway that enables a TDM-based originating or terminating node to interface with an ATM-based backbone network. [0024] 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. Continue reading... Full patent description for Network controller and method to support format negotiation between interfaces of a network Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Network controller and method to support format negotiation between interfaces of a network patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Network controller and method to support format negotiation between interfaces of a network or other areas of interest. ### Previous Patent Application: System and method for integrated service access Next Patent Application: Providing third party content to media devices Industry Class: Multiplex communications ### FreshPatents.com Support Thank you for viewing the Network controller and method to support format negotiation between interfaces of a network patent info. IP-related news and info Results in 3.6274 seconds Other interesting Feshpatents.com categories: Medical: Surgery , Surgery(2) , Surgery(3) , Drug , Drug(2) , Prosthesis , Dentistry |
||
