MXPA98005906A - Architecture and method for managing a flexible communications network - Google Patents

Abstract

The present invention discloses an architecture and method for establishing one or more variable bandwidth communications channels that provides telecommunication customers with immediate setup of an arbitrary bandwidth connection upon demand. A centrally disposed access server (40) controls all of the switches (19) that form the traffic-bearing network (15) and forms a single portal through which all connection requests are made. Requests from users (12) and network applications are interpreted, validated, translated, and seamlessly delivered to the DXCs by the access server (40). The access server (40) comprises a packet switched data network (42), a processor (44), and several workstations (46, 48) for performing a plurality of customer and network related functions. The access server (40) functions as an intermediatory between a traffic-bearing network (15) and one or more network subsystems (20, 25) which are responsible for allocating the connection based on the customer's request.

Description

ARCHITECTURE AND METHOD TO MANAGE A FLEXIBLE COMMUNICATIONS NETWORK TECHNICAL FIELD OF THE INVENTION The present invention relates generally to an improved telecommunications system. Specifically, it relates to the architecture and methods to give the client a more efficient system to start an arbitrary capacity of telecommunications connections to the request.

BACKGROUND OF THE INVENTION The Public Switched Telephone System (PSTN) provides telecommunication service to many subscribers. The PSTN is designed for intermittent use for each subscriber because it is not practical or desired to design a system to maintain a constant connection between each possible pair of subscribers. In this way subscribers effectively share the PSTN by using it on different occasions and in limited portions instead of using all the capacity of the system that is available. For typical connections, the resource systems needed to complete a personal call are reserved at the time the call is generated by the person initiating the call. In the telecommunications services industry, a typical subscription connection consists of one or more telephone lines connected to a central office. The central office is connected to a plurality of switch systems. Other types of connections for subscribers are frequently desired. For example, some clients require semi-permanent connections between particular sites. In this case, it is generally more economical to go beyond the central office and connect the sites with each one using the switch system. This type of connection is referred to connection dedicated to the private line. A private line is a permanent connection in the system that links a couple of distant clients. Instead of marking by the central office to require a system channel, a private line is constantly reserved and arranged exclusively for the use of a client. In addition, customers who need to transport high digital data capacity often find it impossible to do so over a conventional telephone line. Because these signals are compatible with high-speed multiplexed telephony signals commonly carried by telephone systems, those customers can use a direct T1 (1,544 bps) digital connection to carry digital data with high capacity, voice or video. In addition, customer requirements generally vary between a single shared access telephone connection and a vast capacity of connections. In general, telecommunications subscribers have a spectrum of needs that lie between these two extremes. For example, in terms of capacity, the needs of subscribers generally vary from a single telephone voice channel (the equivalent of 64 Kbps) to a T1 line (1,544 Mbps), a T3 line (44,736 Mbps), and beyond. With the interest of having an escalation of services to economically satisfy the individual needs of the clients, many options have been developed to distribute capacities in increments. For example, the fractional service T1 refers to capacity offers in increments of 64 Kpbs. In this way, a subscriber does not have to pay to access the entire T1 transmission line when they only require a part of the capacity. The supplier can sell what is left of the capacity to other clients. Variations in time are also possible. For example, some customers consider constant utility as an important need when other customers can tolerate calls placed in delay and from time to time blocked calls in favor of something cheaper. Generally, a single line connected to a central office makes a request to the resource system every time a telephone call is initiated. If the resource system is not available, the call is blocked. In contrast, a dedicated line is always connected and available. A compromise between these two extremes is a schedule of access to shared lines.

A subscriber such as a bank may need a T1 line constantly available for two hours each night at a certain time. In this way the same T1 line could be made available to other customers at other times. The arrangement is cheaper for everyone instead of buying fully dedicated T1 lines that are generally not going to be used. To further improve services, the telecommunications industry is developing techniques known as capacity in demand (Bandwith on Demand BOD). The goal of BOD is to allow subscribers to instantly get the capacity of the system they need most for as long as they need it and to make service providers only charge for the time and capacity that were currently used. Presently there are several techniques to carry out those types of flexible connections. A conventional type of flexible connections is a T 1 line with 24 channels (with 64 Kbps each) each can be configured as an incoming or outgoing channel. Additionally, each channel can be configured for a particular type of service, such as a dedicated private line, 800 service, etc. (depending on the client). While that method gives the client an option in the available capacity, the connection typically requires several days or longer time to be established by the service provider. In these terms an instant or demand connection can not be established. Another method gives the client control over a terminal connected to the provider's equipment and can configure the communication lines according to their needs. Examples of such services include the digital reconfiguration service (DRS), dynamic allocation of capacity (Dynamic Allocation of Bandwith DAB), and a fixed reconfiguration system (Fixed Network Reconfiguration FNR). These services require a considerable amount of manual intervention and advanced plans by the client before connecting. Thus, a naive user can not easily establish and control the chain of communications. The integrated digital system (ISDN) method offers a digital connection to the subscriber with the appropriate capacity to load several voice and data channels simultaneously. The basic ISDN connection consists of two voice channels and one data channel while the primary ISDN connection consists of 23 voice channels and one data channel. These services represent fast call arrangements, moderate capacity (up to the T1 ratio) and a dynamic and flexible arrangement. However, the use of ISDN is limited for many reasons.

ISDN services are not readily available in many areas. Additionally, the equipment needed to facilitate the ISDN connection is typically very expensive for normal applications. The re-emission / ceiular composition technique, most notably the asynchronous transfer mode (ATM), hopes to penetrate the telecommunications market within a few years. These technologies seem promising but to carry them out they need more work on their standards and the hardware system has to be replaced on a large scale, so that method would be very expensive. Providing capacity arbitrarily with demand is problematic using equipment systems in existence in part because the cross-connection of digital connections (Digital Cross Connections DXCs) typically maintains a limited number of synchronous high-speed x.25 control lines, which are preferred by their Speed in response to the command. It is desirable to design a control system that allows the system to be shared among several levels of system and service applications. That type of system would accommodate new applications without the need to make a general inspection of existing applications. In this way, an architectural method that gives clients a wide line of resources to the system each time it is needed by the client and that charges the client only for the resource currently used, would give a great advantage over other connection methods. of flexible capacity.

COMPENDIUM OF THE INVENTION The present invention discloses an architecture and method for establishing one or more variable capacity communication channels that give the telecommunications client an immediate connection arrangement of arbitrary capacity on demand. Therefore, the primary object of the invention is to provide the client with an architecture system that allows obtaining or programming a connection of almost any capacity including DSO, T1, fractional T1, T3 and other kinds of capabilities. Clients may require connections in different ways and expect comparable time arrangements with voice calls and time arrangements, in a few words, within a few seconds. Another object of the present invention is to provide a system and method to charge the client according to the current use of the resources. Another object of the present invention is to provide an architecture where system characteristics and other services can be added without the need to replace universal applications in a transparent manner to the client. In this aspect, the centralized access system controls the field within the traffic system and functions as a single portal through which all connection requests are made. The requests of the users or the applications for the application of the system (for example, for restoration, capacity, address, provisioning, etc.) are interpreted, validated, translated and delivered to the digital system of cross connections (network digital cross connects DXCs) by the computer acessor of the service. Another object of the present invention is to provide an architecture that is robust and capable of detecting faults throughout the transmission and capable of diverting the call if a fault is detected. The failure has to be transparent to the client. One of the advantages of the present invention is that it allows telecommunications companies to offer services such as ATM long before those services are available. The technology used to implement the present invention is available and implemented using a modified version of the existing equipment and protocols. Another advantage of the present invention is the increase in speed and the ease of integrating new applications because no application monopolizes the cross connection (DXC). The present application also downloads some of the process requirements of the DXCs and moves the application further to the control system network. However, another advantage is that the DXCs of the multiple vendor equipment can be easily supported by the translation of the capabilities into the computer acessor of the service. Another advantage of the system is its redundant distribution design that allows a quick and easy transition from the entire system to an alternate intervening system during failure or maintenance events. For a more complete understanding of the present invention, including methods and advantages, reference is made to the following detailed description taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES 5 In the figures: Figure 1 is a diagram of an architecture to establish a flexible connection capacity according to the symbol of the invention; Figures 2A-2C demonstrate the connections between a digital method of support system (digital network support system DDS), the tf 10 intervening base of MegaHub (the MegaHub Basis Controller MBC), the digital system of cross connections (Digital Cross connects DXCs) and the common access system according to an aspect of the invention; Figure 3 is a high-level diagram of a flexible communications management architecture according to an expression of the invention; Figure 4 demonstrates the communication architecture between DDS and the access system according to the invention; Figure 5 demonstrates the architecture of the redundant path according to one aspect of the configuration of the invention; Figure 6 shows the map of X.25 virtual channels between the access system and other subsystems of the communication network; Figure 7 is a current process diagram of the method used to handle message control systems according to the invention; Figure 8 is a diagram of the establishment of the client and provisioning of the functions according to the invention; Figure 9 is a graphical use interference for a CVNW instrument that can be used to select the city of origin / destination Paris as the connection path. Corresponding numbers refer to corresponding parts in the figures if not indicated otherwise.

DETAILED DESCRIPTION OF THE INVENTION In part, the present invention is an improved telecommunications system and an architecture that provides customers according to their demands with an immediate connection of arbitrary capacity. A centrally placed service access controls all the changes that make up the system that holds the traffic. The service access is the only portal through which all connection requests are made. The requests made by those who use the system and by the application system are interpreted and validated, translated, and delivered to the DXCs by the service accessor. Referring now to Figure 1 is a diagram of the telecommunication system for flexible capacity handling according to the preferred expression of the invention and is shown and indicated generally as 10. As illustrated, system 1 0 includes an access service 40 which is centrally configured between the traffic system 15 and the network of the support system (Network Support System NSS) 20, the cross-connection controller (the Cross Connect Controller CXC) 25 and other functionally related systems 30. 5 The traffic support system 1 5 can encompass any of the known and existing changed data systems and is capable of loading signals of various capacities and densities. Examples include public and private data systems (Public and Private Data Networks PDNs), local exchange systems, and others as is appreciated by experts. System 15 is designed to encompass many changes of connected nodes 19 each having a control link 17 connected to the access server 40 which, in turn, coordinates the distribution of change commands between the entire communication system of the traffic holder 1 5. Likewise, the system 15 of the client 12 has access to the exchange system 1 5 via junction 14. The access server kernel 40 covers the 4fc data exchange system 42, a processor system 44, and several work stations 46 and 48 and corresponding inferences 50 and 52. In practice, system 42 may be a system packet of x.25 change implemented using, for example, commercial recorders such as the DynaStar 200 manufactured by the Dynatech corporation. In one embodiment, the processor system 44 encompasses one or more Alpha processors made by the Digital Equipment Corporation (Digital Equipment Corporation) and has at least one communication ion 43 together with the system 42. The processor system 44 also has access to a database 54 to store a variety of information related to the system to support the different functions. Examples include control information links, DXC node type, change, router and configuration channel information among other things appreciated by experts in that field. Several systems that normally exercise direct control over the traffic system holder 15 are represented by the blocks 20, 25, and 30. According to the present invention, the blocks 20, 25, and 30 are COTS systems that have been modified as described. later. With this consideration, Figures 2A-2C demonstrate the arrangement of the control progression used to describe the modifications of the systems 20, 25 and 30 according to the preference expressed by the invention. In figure 2A, the provisioning of the system 20, preferably having a graphic user (graphical user interface GUI) in front, demonstrated directly connected to a traffic support system 15 of changes, as represented by the DXCs 70. The provisioning of the system 20 can be a Digital Support System made by Prism systems which is generally used as a method of system management to see the condition of the system 15. According to the present invention, the NSS 20 is adapted to perform two functions. First, the modified NSS 20 provides a visual workstation where the end-to-end connection is established and administers privileges to the clients according to the present invention. The second function performed by the modified NSS 20 is to provide the real time, and the perspective of the current traffic path in response to connection requests. Also, the NSS 20 performs enhanced system management functions to establish calls. Figure 2A also demonstrates CXC 25 in one mode is a modified version of a MegaHub DEX 600E (MegaHub) change made by the Digital Switch Corporation. The CXC 25 is used to perform user-based accounts, alarm filters, centralized connections located among other similar systems of controlled functions. According to the present invention, a MegaHub 25 is modified by replacing the internal factory change with x.25 control links to the DXCs 70 system. In this way, the modified MegaHub 25 manages the entire system 130 as if it were a single change of matrix. The modified MegaHub 25 is called the MegaHub Control Base (megaHub Basis Controller MBC). Several methods can be used to modify internal factory changes of the CXC 25. Specific implementations of those modifications will be apparent to people with experience in the art. The M BC 25 provides a wide variety of methods to establish a connection. For example, connections can be established using Dual Tone Multifrequency (DTMF), dialing lines, dedicated lines, or signaling methods • in band. Other ways contemplated for the establishment of connection signals include: SS7 internet and others that are apparent to the experts in the area. In whatever way the CXC is implemented, systems 20 and 25 are conventionally applied separately. Thus, prior to the present invention, there was neither the motivation nor the way to integrate the operation of these two systems, such as the systems and 25. • Additionally, a general technical barrier to such integration has existed in that each DXC 70 generally supports a limited number of control joints. In addition, it is common to use redundant connections from a given supervisory control system to improve system security and increase robustness. Thus, conventionally, it has been problematic to have multiple systems controlling a common group of systems of changes 1. In any case, for many reasons, it is desirable to have two or more systems, such as 20, 25, or 30 to control a common group of systems. of changes 15. For example, the integration of the operation of systems 20 and 25 serves to solve a conventional problem associated with the field of control systems that relates to the addition of new functionality 30 to the system. To add functionality 30 it is generally required to modify and add software to the DXCs 70 and to the control elements such as 20 and 25, which is already handling existing applications. Thus, to add new functionality 30, different applications are forced to coexist within a single system, such as system 20, because DXCs 70 is typically for a single supervisor subsystem. However, as will be apparent, by sharing the control system between multiple subsystems 20 and 25, new functionality 30 can be adapted without prior inspection of the software. For example, the software application for a new function can reside in any other system 30 that has shared access to the DXCs 70. Thus, the integration of the two systems 20 and 25 is particularly advantageous. Figure 2B demonstrates an example of how systems 20 and 25 can be modified and applied to operate in a common system 15 according to the present invention. As it is demonstrated systems 20 and 25 are modified to be able to communicate with each one. Within each system 20 and 25, a communication process is added (20a and 25a respectively). Additionally, two communication channels 72 and 74 are used to join the two systems 20 and 25. In a preferred embodiment, these communication channels 72, 74 take the form of an Application Part Transaction Capability SS7 (SS7 Transaction Capability Application Part TCAP) the format of the message to conform to the prevailing norm although other formats may be used. In this way, the NSS 20 can send information pertinent to the establishment of the call to the MBC 25. The MBC 25, in turn, causes a connection to be formed between the system 15. Likewise, the MBC 25 can send change of trajectory information. not requested to the NSS 20 so that the latter can maintain an up-to-date representation of what is connected between the traffic support system 15 and carry out true-time alarm and function control. Various methods can be used to implement the communication process 20a and 20b and specific implementations of those modifications as described above, and which are apparent to experts in that field. Another modification of the subsystems 20 and 25 is illuminated in Figure 2C where the connection system pack 76 and 78 of the systems 20 and 25, respectively, which are conventionally connected directly to the DXC 70 control junctions, are instead, connected to a common access server 40 according to the present invention. In this way, the two systems 20 and 25 can act on a common group of changes in the traffic support system 15. An obvious advantage of the present invention is that many subsystems, as subsystems 20 and 25 and / or applications within those subsystems, each can act within the system 1 5 without resorting to knowledge or consideration of one another. This feature is useful for providing fast, efficient, and simple integration of applications within a common system 1 5. Note that the connection of the two subsystems 20 and 25 as described above, via direct connections 76 and 78 are terminated via the common access server 40 as demonstrated by the PVC / SVC channel 80. If subsystems 76 and 78 were directly connected, as shown in Figure 2B, the first aspect of operation as described above can be practiced in the system. 1 5 independently of the access server 40. There is a practical additional benefit in using the access server 40 as an intermediary between subsystems 20 and 25. The NSS 20 generally operates in its exchange junction package in a virtual change call ( switched virtual cali SVC). This means that a connection or session is established for each message that passes through the union. This is suitable for intermittent or low volume use where the response time is not critical. On the other hand, MBC 25 operates some of the packet switch connections in a permanent virtual circuit (PVC) mode. In a PVC mode, a session is established once and then used to all subsequent communication messages. PVC mode is preferable for continuous high-volume use when a session established for each message could incur a lot of delay. So for practical reasons, the common access server 40 is also conveniently used as a platform to adapt between the mix of SVC and PVC junctions that are prevalent in telecommunications hardware and applications.

Referring to Figure 1, the NSS 20 and the MBC 25 are shown connected to the capacity system packet 42 between the common access server 40 via junctions 22 and 27 respectively.

Other subsystems, represented by block 30, can be similarly connected to act on the traffic support system 15. In this way, new subsystems discovered in the future, as well as the legacy systems used by clients to exercise limited configuration and control, can be easily accommodated by the method of control system of the present invention. As described, it is possible that the subsystem 20 can be implemented using the Prism's Digital Support System (PDSS) that can be configured to perform various system management functions. While the setting of functions and configurations of DSS 20 may vary, as understood by those experts in the field, the following description highlights several features of a DSS by one embodiment of the invention: DSS Specification 20. Characteristics v Functions according to a Modality The DSS 20 can be implemented through a separate and still operationally integrated software group characteristic. The DSS 20 controls and correlates functions among the characteristic groups. A common application phase ensures all parts of the DSS function as a single entity although individual modules are installed in physically separate locations. With unified visibility in DSS 20, an operator can respond quickly without the need for boring operations in duplicate hardware that might otherwise be required. DSS-II applications.

Operator workstation (OWS operator) Using a standard OSF / Motif compatible x-terminal or a workstation with a TCP / IP phase, an operator can enter the system anywhere and simultaneously can access different applications of DSS 20 or any other x-window to OSS compatible through point-and-click interactions.

System Entry Event (Event Loqging ELS DSS 20 allows the customer's order to be adapted to the specific event display system according to the operator's instructions) Users can obtain fast and accurate real-time isolation and historical information. operated r can categorize events by equipment and transmission facilities along with severity alarms.New alarms are highlighted for quick review until they are recognized.This way, an operator can easily identify potential problems in the system or can also identify personnel They try to enter the system without authorization.

Management of the Service Inventory Management (SIS) A relational intelligent management system database entry is used in DSS 20 to improve user questions related to system inventory. The key information of the inventory, such as circuits, equipment and customer information are synchronized with other characteristic DSS groups, thus allowing better management of the system with consistent and updated information. In addition, the inventory of the database correlates capacity and path objects with the client's data to provide virtual system management.

Application Management (Application Management APM) DSS 20 operates on a LAN architecture scale. DSS 20 can verify characteristic groups that are distributed across multiple guest systems and, if equipped, to prevent a total failure. DSS 20 can maintain available copies of each software module in an optional redundant guest hardware store, such that an application can be quickly restored on a primary failure or during a hardware / software upgrade. Information from the database can be maintained simultaneously multiple hardware systems to ensure the integrity of the configuration.

Connectivity Management (Connectivity Management (1 MS) DSS 20 employs connectivity management software that supports the creation, removal, distribution of unresolved capacity and restoration of pre-plan end-to-end DSO, nxDSO and DS1 circuits A central and unique figure is the Virtual Client Management System (Client Virtual Network Management CVNM) that provides a fine capacity partition based on customer identification.

Customer Position Status Display System DSS 20 correlates with the inventiveness of the database and the event entry system to support the graphical display of the status of a customer's virtual system at an industrial level PC This feature is used in the provisioning of customer service.

External System Phase (ESI External System Interface) Integrated access to DSS 20 of an interlocked incoming order and provisioning systems can be developed based on a phase of an external system. The integration of the DSS 20 with the existing or future operational support system eliminates duplicate system and hardware limits to provide more efficient operation.

DS1 Administration In one modality, a total of six (6) Sun SPARC 10 servers are used where four (4) of these are SPARC 10 model s 51 's that are configured for guest applications. The two leftovers are SPARC 10 40's that are configured to process communications. Two (2) of the four (4) applications (type A1) are configured for database applications, each equipped with 256 MB memory and also with 6.3 GB disk. The other two (2) (type A2) are configured for other applications, each equipped with 256 MB memory and 4.2 disk. A resistant operation will be provided, with an active and willing copy of the RDBMS entry and each system application deployed between the four servers. The communication server supports elements of the communication system. Each system is equipped with 224 MB memory and with disk 2. 1 GB. The guest system communicates with the element system in x.25. This is achieved by a synchronous port RS-449 in the servers. Also, in one modality, five (5) Sun SPARC LX workstations provide the phase of use for the management of the database, the administration system and other uses where the response of the system is important. All servers and workstations can be connected by the Ethernet LAN system, with TCP / IP communications. An NSD / PC terminal allows a CVNM client to control the dedicated system through its personal computer and at the customer's location. Each of the applications has eight (8) asynchronous ports per text terminal, printer, NSD / PC and other peripherals.

DS 1 Provisioning path (DS 1 Path Provisioning) DSS 20 supports the definition of DS 1 speed path in the DS 1 system. With this consideration, the trajectories of DS 1 are transported by the system in any hardware compatible 1/0 DCS with exchange facilities. DSS 20 supports the definition of DSO and n * DSO speed paths in the DS1 system. DSO trajectories are transported by the system in any 1/0 DCS with change facilities. The DSS manages signals for voice and data trajectories.

DSS Provisioning path DSS supports the definition of 2400, 4800, 9600 and 56000 bps DSS trajectory in the DS1 system. These trajectories can be transported by the system at any 1/0 DCS in exchange facilities. Additionally, DCC 20 supports substrate multiplexing of these circuits at every 1/0 DCS suitably equipped for operation.

Multipoint provisioning path DSS 20 supports the definition of DDS MJ U and the DMB data voting path in the DS1 system. DSO trajectories can be transported by the system on any 1/0 DCS change facility. Internal multipoint circuit cascades will only be supported by MJU circuits. Other types of multipoint circuits are not supported, including side-by-side symmetric bridge.

Partitioning capacity DSS partition 20 DSO capability based on customer identification. Capacities associated with the specific identification of the client can only be used in paths defined for that client. The allocation of capabilities in this way is typically carried out by telco users. Specific users can be assigned the privilege of using Pre-Assigned Capacity (Bandwith On Demand BOD) groups during trajectory definitions. The privileged user of telco is responsible for the allocation of capacity. This includes groups of Demand on Demand (Bandwidth on Demand BOD pools).

Partitioning of the Client Ei DSS 20 supports partition information in operations Specific DSS based on the definition of the client's virtual system. For example, question operations may be limited based on customer identification.

Security Partition DSS enforces virtual system partitions and prevents unauthorized users from viewing through the partition boundary within 1 MS, ALS, and ELS applications. The DSS 20 provides a specific user profile, controlled by the administrator system, which specifies valid IDs for the user and assigns privileges to carry out DSS operations by command bases.

Demand Capacity The DSS allows the DSO capability to be associated with groups of specific capacity in demand (Bandwidth on Demand). Specific users have access to specific BOD groups for path identification. The BOD capacity is returned to the BOD group when the user discontinues the use. (for example, full scales and trajectories are removed from the service). Typically, BOD groups are established by telco users and users of CVNM DOD scale use of specific amounts of capacity.

Alarm Partition Display The DSS provides the customer with an exhibition by dividing the facilities of the alarm events that affect the customer's virtual system.

Platform The DSS software runs under the operating system U N IX. In one mode, on a SUN 4 platform using SUNOS (Solaris 1) it is used although another window-x workstation for complaints can be used. A database system, such as the INGRESS RDBMS, can be installed on the DSS platform. The DSS 20 may require that VI Corpis DataViews be installed on the DSS platform. The DSS can be installed on a SUN 4 multiple computer platform co-resident on an Ethernet LAN.

Resistant Sites DSS applications provide secure distributed operations on a multiple-fault-tolerant multi-processor platform. Each DSS application can be built with a common remote call procedure (RPC Common Remote Procedure) based on a communication within the API process that allows an architectural application of the client. The components of the client application locate (transparently to the user) the corresponding active components at the start and behave gracefully on the face of non-client exits (for example: LAN, server platform, server application) DSS. Eligible applications of the server components have at least one active instant and a wait time in different computers on the platform. Changing the instant wait of any server is controlled by the application's handler. The time for each DSS application to switch to the instant wait is specific to the application. Typically, an application can change in less than 15 minutes. Components of a DSS application can be used on any platform computer to achieve improved performance and confidence.

DBMS In a modality, DBMS relational entry is used to save the inventory information management system. The ANSY SQL level is used by DSS software to access these inventories. Also, in another mode, the DSS 20 uses the Raima DBMS product (formerly known as DBVista) to store DSS internal events and events guaranteed by the system.

Data Communications In one modality, the DSS 20 is configured with two Sun SPARC 10 communication engines to withstand initial efforts to control approximately 86 DSC CSX DEX knots as well as connecting the DSS and MBC-2 systems. The DSS is communicated by the access server designed to act on each of the native systems of x.25 junctions and x.25 path virtual channels serving the different applications. Each DSS communication system runs the SunLink x.25 communication software and supports 2 HIS four-port cards that are plugged into the SBUS system. Each bearing supports a physical phase RS-449.

Each DSS communications server supports a minimum of two (2) HIS cards supporting four ports each. At least one can be added to each server as needed. Depending on the number of SBUS slots available, more HSI cards can be added to each server. Each DSS communication supports a minimum of four (4) 56 kbps x.25 junctions. This allows the DSS 200 to use a group of 8 physical joins with 256 channels per join to establish any virtual channel. The DSS 20 automatically establishes virtual circuit changes (Switch Virtual Circuits SVCS) to any defined DXC and MBC channels. If an SVC fails, the server will try to reset it.

If the 56 kbps physical union fails, all sessions in that union will be started in other physical unions. In one modality, each DSS communication supports a minimum of 256 virtual circuit changes (Switched Virtual Circuits SVCS) per x.25 physical junctions allowing up to 1024 SVCs per communications server. Additionally communication servers can be easily added to support higher capacity joints and faster requirements. In this way, the DSS communication system is scalable and can grow as required to support additional knots, faster speed and performance.

Method of Operation In the preferred embodiment of the invention, the DSS 20 supports remotely routed circuits that are tracked and found within the database as previously described. A CVNM instrument will take out the name of a node from the SOT; the knot has to be multiple. Also, if the node type is valid, the DSS will prepare a list of 10-digit MBC port numbers defined in that node. This list will only show those postings that are allowed by the user's profile (for example, shipments of other clients are not going to be shown). The CVNM instrument will allow the user to select a single port per 10-digit node. It is required that two knots be chosen - one to originate and one to finish the circuit. The user can select a knot in many ways. Using the ALS, the user could press on the knot. Nodes are not displayed on the user's ALS screen if the circuits for their profile have not been defined. Users can also select knots by the SOT look-up method or by the SIS. When the two knots have been selected and their ports selected the user will be presented with the option to put the circuit into service or remove it from service immediately. If the circuit is put into service then the circuit record is automatically generated by the software generating the path described above within a short time. The list of 10-digit ports available in the node will be chosen by the database each time the user selects a node. Thus, the user does not need to keep his own copy of the 10-digit postings that are available to the user. The access server 40 also handles a number of different phases to the systems 20, 25 and 30 and the traffic support system jf 15. In particular, as shown in figure 1, a workstation configuration 46 is shown connected to a processor 44 for the purpose of allowing system personnel to view or declare information that systems 20, 25 and 30 and other system elements connected to access server 40. This information is stored in database 54 and can include the appropriate capabilities and protocols for each entity set by the change system package 42. The status / history of the workstation 48 is also demonstrated together with the processor 44 for the purpose of teaching the operational status of the change system package 42 and all connections connected. This state / alarm control can include all software applications, hardware devices, and t scrollwheels in the realm of the service accessor 40. The application block 56 in FIG. 1, represents an operation, as a software process or something similar, that can to act directly by the access server 40. One of the uses contemplated for such application 56 is loading and unloading operation software, content of the database, controls, and status indicators, to or from the system of change support holder. traffic 15. The remote interface block 58 represents a connection allowing remote processing to access many of the same functions within the service accessor 40 as provided by work stations 46, 48 or application 56. In this way, the control remote control of the control system could be carried out. The experts in the field will immediately appreciate that several implementations of the access server 40 can be performed. The following description of the access server 40 forms a contemplated and highlighted modality, without limitations, many aspects of the access server according to a modality: Description of the Access Server and Functional Specifications according to a Modality.

The goal of the access server 40 is to send messages over virtual channels using x.25 concentrator devices and low level routing equipment without introducing any delay at the end to end the message path. In this way, most of the virtual channels (see figure 1) are traversed by the access server 40 point to point and does not require another process only the route. This path can be completely directed by the X.25 communication server and does not require another CPU utilization system. Limiting message delay is more critical in the path and process of the DXC binary message. In this way, in the preferred embodiment, the access server 40 introduces almost zero delay in any path of the virtual message from end to end that does not require additional processing of the application. Similarly, the access server 40, does not introduce more than 100 milliseconds (millisecond) of delay at the end when the path of the message required by the application process, such as updating the database and inscribing the message, ends. This requirement applies specifically to the binary and the connection and disconnection of ASCII control channels. The access server 40 supports a minimum of 120 DXC nodes and can be extended to add additional DXC nodes as needed. The access server 40 continuously controls all the X.25 physical junctions and virtual channels and reports alarms to a management system (Network Management System NMS) when a failure occurs. A major alarm can be reported when the failure of a union is detected and critical is reported when the failure of the two (redundant) junctions is detected. Losing alarm messages are reported when the connectivity of the union is restored. The access server 40 periodically tries to start any virtual channel that failed. The interval to try again periodically can be configured by the administrator assuring that since a physical failure has been corrected the future manual intervention is not necessary to restore the communication channels.

Operational Regimes The access service software system 40 consists of operating service systems that provide the background for the other layers of software applications. These services include the following: 5 - Security system service, system management service. The access server 40 provides a way to ensure protection of the access system without authorization or interference. - Backup system and restoration facilities: For disk and magnetic tape operations, software 10 of the operating system provides for the control of the mechanism for • disk, tape and printing device for the format and assembly. - Disk space management, purging, size and process quotas. -Equipment to analyze disk errors and magnetic tape. 15 -Batch operations and printing of queue handling process queues and jobs. -Maintaining file entry systems and providing • file dump analysis. -Generation of the system and initialization process- Installing 20 device drivers, compartment of memory segments and processes. -Control and management of the system's performance. -Application of programming and control software The access server 40 maintains statistical information (for example, number of failures, number of starts) for each phase of external unions allowing users to control the work of the union and to see the state of the Union.

System Interface Interfaces The access server 40 adapts to the native physical interface of each external system that is connected to it. Each of the external systems with which the server communicates are existing systems and have their own specific physical requirements. The access server 40 accommodates each native interface and does not require the development of any of the external systems to be able to communicate by the access server. Access server 40 supports the following physical communication data connecting to specific systems ^ X. 25 -SVC -DSS-il X.25 -PVCs -MBC-2 (DXC and TCAP junctions) X.25 -SVC -DRS X.25 CVCS - DSC DEX CSLL DXCs TCP / IP - Ethernet account system - Ethernet NMS - Access server The access server supports the following communication protocols: DSC binary DXC protocol PDS snyder ASCI I protocol. TCP / IP Decnet X.25 The access server 40 provides the path of the message traffic needed to support the integration of component systems allowing the following data flow: System Message type DSS-I I r-- M BC-2 Binary SS7 TCAP message DSS-I I < r-- > DSC 1/0 DXCs ASCI I PDS messages DRS < - DSC 1/0 DXCs messages ASCI I PDS MBC-2 - -í > DSC 1/0 DXCs Binary Message DXC Server < --- > NMS Alarm message system Server --- > Accounts Call for Detailed Records Regiments of the DSS 20 interface The DSS 20 system is configured with two SUN PARC 10 communication machines to support DSC DEX CSI L nodes as well as interconnecting DSS 20 and MBC-2 systems. DSS 20 will be communicated by the access server 40 designed to compare each native x.25 junction system. Because the natural duplication of the components of the platform, the DSS 20 is directly connected to each access server (see figures 3 and 5), one placed and one distant. The access server 40 provides a redundant physical union (see figure 5) and rotation of the virtual channels (see figure 6) to the DXCs and MBC-2 systems. The DSS 20 will control the failures of the unions and will report the loss of communications. Each access server 40 supports a minimum of four (4) 56 Kbps x.25 DSS- 1 1 control junctions. This allows the DSS 20 to use a group of 8 physical unions with 256 channels per link to establish any virtual control channel to the DXC systems and MBC-2 Each access server 40 supports a minimum of 256 virtual circuit changes (Swiched Virtual Circuits SVC) by DSS-I I x.25 physical union allowing up to 1024 SVCs per DSS-I I communication server. The access server 40 supports a CCITT x.25 communications heap and serves as a standard packet of data exchange system (Standard Packet Switching Data Network PSDN). It is not required that a lot of proprietary Q-bit manipulation sessions confront the communications subsystem DSS-I I. In one embodiment, the access server 40 allows 4 SVCs per DXC node from the DSS-I I to be directed to 4 DXC ASCI I SVCs controlled by the access server 40 and allows a minimum of 2 SVCs to be directed from the DSS- I I to the MBC-2 TCAP face entrance PVCs. Returning to figure 3, a high-level diagram of an integrated capacity allocation system according to the intervention is demonstrated and denoted generally as 1 00. In particular, double and redundant systems 1 02, 104, are provided and allow operation of crossing of each system by the entire system.

With respect to the left side 102, FIG. 3 illustrates which customer premise equipment (CPE) 105 is used to gain access to the Digital Reconfiguration Service (DRS) processor 109 by the access terminal 107. As is known In the art, DRS is an application system management network that is designed to reconfigure the connection portion of a client and to configure temporary capacity when the client needs additional capacity. As shown by FIG. 3, the left side 102 has a DRS processor 109 that is communicably linked to an access server 1 13 which provides many channels by concentrating and directing functions described herein. In one embodiment, the access server 113 and its redundant counterpart 115 comprise the x.25 recorder equipment and the DEC Alpha processor that provides shared access to the system 1 1 1. Redundant access servers 113 and 1 15 are communicably hooked to each other by the links 114 and 1 15. Likewise, the access servers 1 13 and 1 15 are linked to the customer management service (Customer Management Service CMS) processor 1 17 by control connections 1 19. The platform 1 17 CMS is a entry to various features and functions related to the client, such as customer orders, partitions, message routing and other similar operations related to the client. Returning to Figure 4, the architectural phase between the digital support system (Digital Network Suport System) (equivalent to DSS in Figure 1) 155 and access servers 159, 161 is demonstrated. Figure 4 demonstrates that the plurality of server application 155, which collectively of an operable DSS, are provided where the extensive applications of the various systems are executed. Server operations include end-to-end circuit provisioning, static or dynamic router selection, circuit reconfiguration schedule, system function control, system resource partitioning, multi-level security access, disaster recovery, and management of alarms, management of the virtual system of the client, graphic display of the state of the system and interactive or batch of the process of command files among others.

As is demonstrated, the application of the server 155 is communicatively linked by LAN union 1 57 to communication servers 159 and 161 which in turn, provide the control and command of paths to access servers 163 and 165. In this way, servers 163 and 165 are functionally equivalent to access server 40 of Figure 1 as previously described. In one embodiment, each access server 163 and 165 supports a minimum of four (4) control links. In this way, each access server 163 and 165 can traverse x.25 virtual channel concentrating and traversing functions to the server application 1 55. The communication path is provided by communication servers 1 59, 161 and link 157 which in one mode is a TCP / I P channel. Each access server 163, 165 supports a CCITT heap of communications x.25 and develops the function of a standard packet of data system changes. In this manner, the access servers 163 and 165 may allow several SVCs by DXC of the server application 155 to be routed to DXC ASCII SVCs controlled by the access servers. In sum, the access servers 163 and 165 form a transmitting control path without interruption between the data traffic holder system 15 and the support system method in place. Returning to Figure 5, a communications architecture 200 demonstrating the redundant characteristic according to an embodiment of the invention as demonstrated. The goal of architecture 200 is to provide high security to redundant paths between the various applications and DXCs in the system. As shown in figure 5, 2 MBC processors 205 and 207 communicatively linked to each other by signal junction 209. This provides dual and independent system controls that can each operate separately and control the entire load of the entire system if one side of the control system method has a catastrophic failure on your computer. As shown, remote changes 21 1 and 213 provide physical unions to opposite sides of the control system method and give each side the ability to change if a fault occurs. The change layer 215 associates the MBC processors 205 and 207 to the access server layer 217 which encompasses a plurality of data exchange component packets including hubs 230 and access servers 233. A wide area system 219 is scattered among the respective sides of the architectural system 200 giving a communication path at the server level 21 7. Finally, the digital connection crossing layer 250 provides the connection to the corresponding data traffic system. As has been indicated, one purpose of the access server 40 is to scroll through the extensive system through virtual channels using x.25 concentrator devices and low level x.25 router equipment (layer 217) without introducing any delay in the message path. end to end. In this way, according to one modality, most of the virtual channels traversed by the access server are from point to point and do not require another process only to be traversed. This route can be carried out completely by the x.25 communications server (159 and 161 of figure 1), without requiring additional use of the access server. The access server layer 217 has to intercept cross-connection digital messages from layer 250 and determine the connection status, deliver responses and queue formed to update the process. In sum, figure 5 presents a high degree of redundancy between several processors of a connection ion. In particular, a primary redundancy level is given by the junctions T1 between the division 40 on the right and the left of FIG. 5. A secondary protection level between the access server processors of the layer 217 is provided by the WAN 219. Finally, the X.25 230 trackers are extensively cross-connected so that the failure of a track or a joint is easily exceeded. This design ensures a high robust architecture for the distribution of control information to the DXC layer 280. In reality, the system is designed to allow two (or more) MBCs 205 and 207 to control the system. As an important advantage of the present invention, these MBCs 205 and 207 can be geographically separated so that, in the event of a geographic lack of an MBC, control of the entire system can be immediately carried out by the other MBC without any interruption of service. In Figure 5, SS7 signal junctions 209 are demonstrated by connecting the two MBCs 205 and 207. This is done to maintain an accurate database on the state of the system at the two locations. Returning to figure 6, the map of the various virtual channels X.25 between each access server 159 and 161 and other systems in the network is demonstrated and generally denoted as 275. Figure 6 shows the virtual channel devices 280 that are routed to the access server side 285 on a point-to-point basis eliminating unnecessary delays. In one embodiment, the access server side 285 introduces no more than 100 millisecond delay of the end-to-end message path that the application transformation requires such as updating the database and message entries. This requirement applies specifically to the binary and to the ASCCll connection and disconnection of control channels.

In another modality, the side access server 285 is designed to support a minimum of 120 DXC nodes and can be extended to add other nodes as necessary. In this aspect, it is to be understood that the access server 285 side of FIG. 6 demonstrates the signal of the traffic input and output path of the physical access server 40 of FIG. 1 also as the redundant access server 113 and 115 of Figure 3. Other virtual channels between DSS 290, DRS 295, DXC 300, DXC handler 305 and TCAP input 310 are illustrated demonstrating virtual channel path and joint designations according to the modality contemplated. The access server side 285 provides the traffic of messages needed to support the integration of several system components according to a fixed process that is denoted figure 7 as 300. Process 300 with step 305 when the access server initiates the various unions to determine if the unions are active and operational. The next one, in step 310 the access server examines the connection status of the various virtual channels and reports the status to the network of the support system. At this point, the access server waits to receive the message along the junction, step 315, and verifies the validity of any message to ensure an appropriate command or which control is being sent, step 320. As shown, always and when a message has not been received, the process is directed to step 317 to examine the state of the various unions throughout the system. When a valid message is received, the process flow is directed to step 330 where the access server collects the message source and the installed designation capacity and searches for any translation of instructions specific to the received message, step 330. Then, in step 335 the message is interpreted and transformed as necessary and a path is selected to determine the best way to send the message to the determined destination, step 340. The message is sent and when it is sent successfully the flow of the process is directed to the step 317 where the access server reevaluates the state of all unions waiting for the message. On the other hand, when a message is not sent successfully and all possible routes have been exhausted, step 350, a rejection message is sent, step 335, to the message source and the command or change of message is aborted. If other routes are available, in step 355 the access server looks for other connections and selects the best route for the intended designation, step 340. This evaluation may involve exams for protocol adhesion, privilege access, valid designations of references and other requirements as appreciated by those trained in the art. Returning to Figure 8, the method of selecting a flexible capacity resource is demonstrated and generally denoted as 375. Process 375 begins when a customer or service provider places an order for a 380 capacity resource that, in turn, is traversed by a circuit provisioning process 385. In the preferred embodiment, the command is instantaneously transformed to the circuit provisioning process 385 allowing selection on demand to be made. After, the customer order is directed towards a provisioning system 390 that receives the order in real time and updates the appropriate service bases of the customer data to ensure that the customer has the authority and access to the requested capacity resource. If so, the process flow is directed to step 395 where the call and the account files are established by the system using the appropriate control links. Also, maintenance system may be required 400 to ensure correct point-to-point connection signals as well as the quality of the joint. Finally, process 375 is directed to establish the call 405 that establishes the connection and gives the client exclusive use of end-to-end channel transmission to the time and capacity required. Returning now to Figure 9, a screen 425 of front geographic use interface to establish a connection utility is demonstrated. The 425 screen can be used by telecommunication clients or other users to establish point-to-point communications channels that allow a connection at any two points in the system. For example, the client could use the 425 screen to establish a communication connection at a specific time and date and for a specific duration taking into account that the client has authority to use the service. In this way, the client can configure a rapid change of data in any two of the system, such as video conference, remote database search or other data transfer of similar capacity but not programmed. As shown, screen 425 is divided into a left side 430 and a right side 435 which in a modality corresponds to origination and points ending in the connection. On the 430 origination side, the client has the option of several sites to establish the call. A unique ten-digit identifier and description field 434 is provided corresponding to each available source site. Similarly, a menu 437 of designation points available on the right side 435 of the screen 425 which allows the user to select from a plurality of available termination points for the call. As shown, each termination point has a four-digit identifier and a description 439 corresponding to endpoints in the connection path of the call. A confirmation box 440 is provided allowing the client to configure the end-to-end path for the connection used using the specific service and at a specific time and / or date. It should be understood that the screen 425 is illustrative of one of many possible personifications and that the illustrated features monopolize one of many possible solutions to the same problem.

While this invention has been described in reference to illustrative embodiments, it is not intended that the description be interpreted in a limited manner. Various modifications and combinations of the illustrative embodiment as well as other embodiments of the invention will be apparent to persons skilled in the art with reference or description. It is, then, desired that the included claims encompass any of the modifications or modalities.

Claims (12)

1. CLAIMS 1. An architecture system to establish communication channels of variable capacity in demand that architecture includes: a traffic support system having a plurality of knots linked one or the other by a plurality of transmission paths, said knots forming a local center connecting a plurality of users; an access server connected to said traffic support system by a first plurality of communications link to receive messages by said user; and a support of the network of the system communicatively linked to said access server by a second plurality of communication connections, said network of the support system configured to carry out a plurality of system management functions. The architecture according to claim 1, wherein said access server also includes: a system packet data changes connected to said first plurality communications link to receive messages by said users; a process system communicatively linked to said data system; a database connected to said processor and keeping a plurality of information related to the user and information related to the system; and a group of work stations configured to provide a plurality of system configuration functions and status / history functions, said work stations communicatively linked to said processor. The architecture according to claim 1, wherein said system support network also encompasses an application for initiating calls and managing the privileges of the client. 4. The architecture according to claim 3, wherein said network supports the system also encompasses an application to obtain an almost real-time view of the traffic routing system in response to the connection request. The architecture according to claim 1, wherein it also includes a cross-connection controller com unicably linked to said access server by a second plurality of communication junctions. 6. The architecture according to claim 5, further comprising communication channels joining said cross-connection controller and said network of the support system. The architecture according to claim 5, further including a plurality of X.25 virtual circuit changes formed a signal path between said access server and other systems of said system architecture. The architecture according to claim 2, wherein said data exchange packet system includes a plurality of X.25 hubs and low X.25 level traversers to transmit formatted X.25 messages created along said architecture. of the system. 9. The architecture according to claim 7, wherein the access controller introduces a delay of almost zero in the X. message path of virtual circuits. 10. Central access server to establish a point-point communication channel in a telecommunications system said system having at least one traffic support system, a provisioning system of available resources and a cross-connection controller, said server access comprising: A change packet of the data system communicably linked to both said telecommunications system and said network system by a plurality of virtual change circuits; A processor system linked to said data system exchange packet by a first communications link supporting a data exchange protocol for receiving said messages originated by said communication system; A group of work stations linked to said processor system and containing a plurality of applications related to the system to perform functions related to the system; and a database structure attached to said processor to store a plurality of information related to the system. 1 1. The central access server of the claim 10 also includes: An application program to upload and download operation software, database content, commands, and indicators of | state to and of said traffic support change system; and A remote phase that provides access to functions within said access server, said functions provided by any said work station or said application program. 12. In a telecommunications system having an access server configured centrally between the traffic support system and a plurality of system methods that control the provisioning and change of available resources of the system, a • Capacity distribution method available in the system covering the steps of: sending a user request for a telecommunications service: 15 intercepting the request at the level of the access server; interpreting the request to determine the type of service requested by the user; formulating the request according to a predetermined format compatible with said supply system; 20 transmitting the request made to said supply system; determining if the user has authority to access the service; and distributing enough capacity in the system to fill the request.