EP1214859A1 - Systeme, methode et article fabrique pour reseau de communication grande vitesse a plusieurs niveaux et a efficacite accrue - Google Patents

Systeme, methode et article fabrique pour reseau de communication grande vitesse a plusieurs niveaux et a efficacite accrue

Info

Publication number
EP1214859A1
EP1214859A1 EP00959799A EP00959799A EP1214859A1 EP 1214859 A1 EP1214859 A1 EP 1214859A1 EP 00959799 A EP00959799 A EP 00959799A EP 00959799 A EP00959799 A EP 00959799A EP 1214859 A1 EP1214859 A1 EP 1214859A1
Authority
EP
European Patent Office
Prior art keywords
network
call
service
data
switch
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.)
Withdrawn
Application number
EP00959799A
Other languages
German (de)
English (en)
Inventor
Michel K. Bowman-Amuah
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Accenture LLP
Original Assignee
Accenture LLP
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Accenture LLP filed Critical Accenture LLP
Publication of EP1214859A1 publication Critical patent/EP1214859A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
    • H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
    • H04Q11/0478—Provisions for broadband connections
    • 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/5619—Network Node Interface, e.g. tandem connections, transit switching
    • H04L2012/5621—Virtual private network [VPN]; Private-network - network-interface (P-NNI)
    • 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/5619—Network Node Interface, e.g. tandem connections, transit switching
    • H04L2012/5623—Network design, dimensioning, topology or optimisation
    • 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/5638—Services, e.g. multimedia, GOS, QOS
    • 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/5638—Services, e.g. multimedia, GOS, QOS
    • H04L2012/5645—Connectionless
    • 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/5638—Services, e.g. multimedia, GOS, QOS
    • H04L2012/5671—Support of voice

Definitions

  • the present invention relates to communications networks and more particularly to an efficient, high speed communication network.
  • PSTN Public Switched Telephone Network
  • the current telecommunication service providers' networks reflect the architecture of the Public Switched Telephone Network (PSTN) network as it has evolved over the last 100 years. This is largely based on circuit switched technologies. Initially, all telecommunication services were offered via a wired infrastructure. As the user-base increased and requirements changed over the last few decades, new types of services were created e.g. wireless PSTN, cable video, multiservice (PSTN, video, satellite). The networks that supported these services were created as parallel networks, along-side the existing PSTN network. As technologies matured, there was some convergence (e.g. they shared the same SONET backbone) in the network architecture.
  • Core network is a set of parallel networks; PSTN, wireless, satellite, cable, ATM, frame relay, IP. There is some interoperability between the services on these parallel network (e.g. PSTN, and wireless), but generally these networks are vertically integrated to provide distinct set of non- interoperable services.
  • a system, method and article of manufacture are provided for providing a high speed network.
  • One component is a customer network which is accessed by a plurality of customers.
  • An edge network interfaces with the customer network.
  • the edge network provides services to the customers.
  • a core network interfaces with the edge network.
  • the core network performs a plurality of tasks including consolidating low-speed traffic streams from the edge network into high-speed trunks, simplifying topologies of the networks, and realizing bandwidth efficiencies across the high speed network.
  • the edge network supports frame relay, SNA migration, virtual private networks, voice service, and/or data service.
  • value added service enhancements may be provided by the edge network.
  • the core network aggregates traffic over the edge network.
  • the core network may interface more than one edge network. In such case, the core network would provide resilient transport to the edge networks.
  • Figure IA is a block diagram of an exemplary telecommunications system in accordance with a preferred embodiment of the present invention.
  • Figure IB shows a block diagram of the Network Data Management in accordance with a preferred embodiment of the present invention
  • Figure 1B-1 is a flowchart illustrating a Network Data Management process in accordance with a preferred embodiment of the present invention
  • Figure IC shows a block diagram of the Customer Interface Management Process in accordance with a preferred embodiment of the present invention
  • Figure lC-1 is a flowchart illustrating a Customer Interface Management Process in accordance with a preferred embodiment of the present invention
  • Figure ID shows a block diagram of the Customer Quality of Service Management Process in accordance with a preferred embodiment of the present invention
  • Figure 1D-1 is a flowchart illustrating a Customer Quality of Service Management Process in accordance with a preferred embodiment of the present invention
  • Figure IE shows a block diagram of the Service Quality Management in accordance with a preferred embodiment of the present invention
  • Figure 1E-1 is a flowchart illustrating a Service Quality Management Process in accordance with a preferred embodiment of the present invention
  • Figure IF shows a block diagram of the Problem Handling Process in accordance with a preferred embodiment of the present invention
  • Figure 1F-1 is a flowchart illustrating a Problem Handling Management Process in accordance with a preferred embodiment of the present invention
  • Figure IG shows a block diagram of the Rating and Discounting Process in accordance with a preferred embodiment of the present invention
  • Figure 1G-1 is a flowchart illustrating Rating and Discounting Process in accordance with a preferred embodiment of the present invention
  • Figure IH shows a block diagram of the Invoice and Collections Process in accordance with a preferred embodiment of the present invention
  • Figure 1H-1 is a flowchart illustrating an Invoice and Collections Process in accordance with a preferred embodiment of the present invention
  • Figure 2A is a flowchart showing illustrating media communication over a hybrid network in accordance with a preferred embodiment of the present invention
  • FIG. 2B is a block diagram of an exemplary computer system in accordance with a preferred embodiment of the present invention.
  • FIG. 3 illustrates the call detail record (CDR) and private network record (PNR) call record formats in accordance with a preferred embodiment of the present invention
  • FIGS. 4A and 4B collectively illustrate the Expanded Call Detail Record (ECDR) and Expanded Private Network Record (EPNR) call record formats in accordance with a preferred embodiment of the present invention
  • FIG. 5 illustrates the Operator Service Record (OSR) and Private Operator Service Record (POSR) call record formats in accordance with a preferred embodiment of the present invention
  • Figures 6A and 6B collectively illustrate the Expanded Operator Service Record (EOSR) and Expanded Private Operator Service Record (EPOSR) call record formats in accordance with a preferred embodiment of the present invention
  • EOSR Expanded Operator Service Record
  • EPOSR Expanded Private Operator Service Record
  • FIG. 7 illustrates the Switch Event Record (SER) call record format in accordance with a preferred embodiment of the present invention
  • FIGS. 8A and 8B are control flow diagrams illustrating the conditions under which a switch uses the expanded record format in accordance with a preferred embodiment of the present invention
  • Figure 9 is a control flow diagram illustrating the Change Time command in accordance with a preferred embodiment of the present invention.
  • Figure 10 is a control flow diagram illustrating the Change Daylight Savings Time command in accordance with a preferred embodiment of the present invention
  • FIG 11 is a control flow diagram illustrating the Network Call Identifier (NCID) switch call processing in accordance with a preferred embodiment of the present invention
  • Figure 12 is a control flow diagram illustrating the processing of a received Network Call Identifier in accordance with a preferred embodiment of the present invention
  • Figure 13A is a control flow diagram illustrating the generation of a Network Call Identifier in accordance with a preferred embodiment of the present invention
  • Figure 13B is a control flow diagram illustrating the addition of a Network Call Identifier to a call record in accordance with a preferred embodiment of the present invention
  • Figure 14 is a control flow diagram illustrating the transport of a call in accordance with a preferred embodiment of the present invention
  • Figure 15A is a flowchart showing a Fault Management Process in accordance with a preferred embodiment of the present invention
  • Figure 15B is a block diagram showing a Fault Management component in accordance with a preferred embodiment of the present invention.
  • Figure 16A is a flowchart showing a Proactive Threshold Management Process in accordance with a preferred embodiment of the present invention
  • Figure 16B is a flowchart showing a Network Sensing Process in accordance with one embodiment of the present invention.
  • FIG. 17 is a flowchart showing an Element Management Process in accordance with a preferred embodiment of the present invention.
  • Figure 18 is a flowchart showing a three tiered customer support process in accordance with a preferred embodiment of the present invention.
  • Figure 19 is a flowchart showing an integrated IP telephony process in accordance with a preferred embodiment of the present invention.
  • Figure 20 is a flowchart showing a Data Mining Process in accordance with a preferred embodiment of the present invention.
  • Figure 21 is a diagram that illustrates the principal points of contact between service providers, their customers and suppliers in accordance with a preferred embodiment of the present invention
  • Figure 22 is a simplified view of processes used by Service and Network Providers in accordance with a preferred embodiment of the present invention.
  • Figure 23 shows the relationship between Processes, Functions and Data in a system in accordance with a preferred embodiment of the present invention
  • Figure 24 illustrates the high-level structure of Network Management processes, the supporting Function Set Groups, and the Data Areas on which these depend in accordance with a preferred embodiment of the present invention
  • FIG. 25 depicts the positioning of the Network Management processes within a Telecommunications Management Network (TMN) in accordance with a preferred embodiment of the present invention
  • Figure 26 shows a Network Planning &Development process of the present invention, including input and output triggers in accordance with a preferred embodiment of the present invention
  • Figure 27 illustrates the Functional Groups and Data Areas for the Network Planning & Development process in accordance with a preferred embodiment of the present invention
  • Figure 28 shows the Network Provisioning process of the present invention, including input and output triggers in accordance with a preferred embodiment of the present invention
  • Figure 29 depicts Functional Groups and Data Areas for the Network Provisioning process in accordance with a preferred embodiment of the present invention
  • Figure 30 illustrates the Network Inventory Management process of the present invention, including input and output triggers in accordance with a preferred embodiment of the present invention
  • Figure 31 shows the Functional Groups and Data Areas for the Network Inventory Management process in accordance with a preferred embodiment of the present invention
  • Figure 32 illustrates the Network Maintenance & Restoration process of the present invention, including input and output triggers
  • Figure 33 is depicts the Functional Groups and Data Areas for the Network Maintenance & Restoration process;
  • Figure 34 shows the Network Data Management process of the present invention, including input and output triggers;
  • Figure 35 illustrates Functional Groups and Data Areas for the Network Data Management process
  • Figure 36 shows the Structuring of the Network Management Layer of the present invention
  • Figure 37 depicts a TMN Layered Management Architecture in accordance with one embodiment of the present invention.
  • Figure 38 illustrates the Customer Care Lifecycle of the present invention
  • Figure 39 shows a Typical Service Management Lifecycle of the present invention
  • Figure 40 depicts the Network Management Lifecycle of the present invention
  • Figure 41 shows how the Customer Care, Service Management and Network Management Lifecycles interact
  • Figure 42 illustrates the five high level network management business processes and thirteen sub-processes
  • Figure 43 is a diagram that illustrates the position of the processes and sub-processes in relation to the processes, function set groups, and data areas of Figure 22;
  • Figure 44 shows how two examples of the linked workflows might be used in accordance with one embodiment of the present invention.
  • Figure 45 illustrates a process flow for the Network Provisioning process of Figure 28
  • Figure 46 illustrates a Process flow for the Network Data Management process of Figure 34;
  • Figure 47 shows the Network Performance Monitoring sub-process of Figure 42;
  • Figure 48 illustrates the Network Test Management sub-process of Figure 42
  • Figure 49 illustrates the Network Configuration and Routing subprocess of Figure 42
  • Figure 50 is a flowchart illustrating a method of implementing a hybrid network in accordance with one embodiment of the present invention.
  • Figure 51 illustrates an exemplary configuration of the Next Generation Network (NGN) Prototype
  • Figure 52 illustrates another exemplary configuration of the NGN Prototype in accordance with a preferred embodiment of the present invention
  • Figure 53 depicts another exemplary configuration of the NGN Prototype in accordance with a preferred embodiment of the present invention.
  • Figure 54 shows another exemplary configuration of the NGN Prototype in accordance with a preferred embodiment of the present invention.
  • Figure 55 depicts another exemplary configuration of the NGN Prototype in accordance with a preferred embodiment of the present invention.
  • Figure 56 shows another exemplary configuration of the NGN Prototype in accordance with a preferred embodiment of the present invention.
  • Figure 57 illustrates another exemplary configuration of the NGN Prototype in accordance with a preferred embodiment of the present invention.
  • Figure 58 is a flowchart illustrating a method for predictive fault management over a network in accordance with a preferred embodiment of the present invention
  • Figure 59 is a diagram which illustrates some exemplary services that may be integrated into the NGN Business Simulator of the present invention
  • Figure 60 illustrates four strategic platforms that can be integrated into the NGN Business
  • Figure 61 illustrates how the NGN Business Simulator utilizes the entire Business Integration Framework by integrating Network Transformation assets with assets from other market offerings
  • Figure 62 is an exemplary Operations Map that may be used to define and implement the NGN Business Simulator processes
  • Figure 63 is an illustration of a utility network that is the underlying supporting infrastructure that provides intelligent connectivity between the various NGN components;
  • Figure 64 is a flowchart illustrating a network creation process in accordance with one embodiment of the present invention.
  • Figure 65 illustrates a network and service provisioning scenario in accordance with one embodiment of the present invention
  • Figure 66 is a flow diagram illustrating a method for demonstrating business capabilities in an eCommerce environment
  • Figure 67 is a flowchart depicting how eCommerce capabilities on the NGN prototype (or other) network can be demonstrated via a simulation
  • Figure 68 is a flow diagram illustrating a method to simulate operation of a service provider network
  • Figure 69 is a chart illustrating components of the NGN Business Simulator of the present invention
  • Figure 70 depicts an exemplary release plan for the NGN Business Simulator of the present invention.
  • Figure 71 illustrates exemplary locations between which the Network Fabric of the present invention may provide connectivity in the manner illustrated in Figure 70;
  • Figure 72 is a table containing an alternative solution evaluation matrix used to evaluate the pro's and con's of various alternatives at a high level by assigning comparative ratings to each area;
  • Figure 73 is an illustration of a high speed network in accordance with one embodiment of the present invention.
  • Figure 74 illustrates the interrelation of the components of the network of Figure 73
  • Figure 75a is a table that illustrates network services based on client requirements
  • Figure 75b is a table that lists features of the network services
  • Figure 75c is a table that illustrates exemplary performance requirements for the services as well as listing exemplary service interfaces
  • Figure 76 is a table that discusses the network implications of selecting the carrier grade edge network option
  • Figure 77 is a table that examines the network implications of selecting the simple connectivity network option
  • Figure 78 is a table that illustrates options for various components of the network
  • Figure 79 illustrates a first example of a network architecture of the present invention, which provides basic IP connectivity between the sites;
  • Figure 80 illustrates a second example of a network architecture of the present invention, which is designed to form an edge network to which the "Simple Connectivity Network" already described can be connected;
  • Figures 81a through 81(1 are tables summarizing the extent to which various objectives are achieved by each of the listed solutions.
  • a prototype network system for demonstrating capabilities of a high speed broadband network.
  • a description of the high speed broadband network is provided below, followed by a description of the prototype network, including a hardware implementation.
  • a description of a business simulator especially adapted to illustrate business capabilities of the prototype and/or high speed broadband network.
  • Communications service providers can reconcile these seemingly conflicting requirements by transforming their networks into a new broadband, next generation network infrastructure.
  • This intelligent, hybrid architecture which efficiently supports both circuit-switched (voice) and packet-switched (data) traffic enables service providers to launch many new broadband data services.
  • Communications service providers can migrate services off their legacy network and consolidate and optimize these services and network resources onto one single packet-based network, thus lowering their costs and increasing the manageability of their overall network transformation. Network transformation may take on many faces.
  • Figure 1 depicts how service providers and businesses can transform to meet these emerging trends in the telecommunications industry.
  • the Network Transformation Implementing IP market offering has been created to aid service providers with the transformation of their network. Through use of the network, communications service providers will be to respond decisively to the new demands of the marketplace.
  • forward-looking communications service providers are already in the midst of seeking the network architecture of tomorrow.
  • Traditional network architectures have served them well in the past, but to compete for the customer today ⁇ and even more so in the future - communications service providers will need to transform their current network to an intelligent, broadband Next Generation Network infrastructure.
  • next generation networks should also have the ability to dynamically reconfigure the network so that it can guarantee a predetermined amount of bandwidth for the requested quality of service (QOS).
  • QOS quality of service
  • the concept is to provide network managers with complete “command and control” over the entire network's infrastructure—not just tell them when a failure has occurred.
  • ATM asynchronous transfer mode
  • Text files and images can be sent over existing packet-based networks because the delivery of this information is not time critical.
  • the new traffic (voice and video) is delivery time sensitive- variable or excessive latency will degrade the quality of service and can render this information worthless.
  • Such networks are generally point- to-point in nature in that a packet from a single source is directed to a single destination by an address attached to the packet. The network responds to the packet address by connecting the packet to the appropriate destination.
  • Packet switching networks are also used which combine burst type data with the more continuous types of information such as voice, high quality audio, and motion video.
  • Commercialization of voice, video and audio transmission makes it desirable to be able to connect packets to multiple destinations, called packet broadcasting.
  • a broadcast video service such as pay-per-view television involves a single source of video packets, each of which is directed to multiple video receivers.
  • conferencing capabilities for voice communication also require single source to multiple destination transmission.
  • One prior packet broadcast arrangement comprises a network consisting of a packet duplication arrangement followed by a packet routing arrangement. As a broadcast packet enters this network, packet copies are made in the packet duplicating arrangement until as many copies exist as there are destinations for the packet. A translation table look up is then performed at the duplication arrangement outputs for each of the packet copies to provide a different, single destination address for each copy. All of the packet copies with their new packet addresses are then applied to the packet routing arrangement, which connects them to the appropriate network output ports.
  • packets in the form of units of data are transmitted from a source- such as a user terminal, computer, application program within a computer, or other data handling or data communication device— to a destination, which may be simply another data handling or data communication device of the same character.
  • the devices themselves typically are referred to as users, in the context of the network.
  • Blocks or frames of data are transmitted over a link along a path between nodes of the network.
  • Each block consists of a packet together with control information in the form of a header and a trailer which are added to the packet as it exits the respective node.
  • the header typically contains, in addition to the destination address field, a number of subfields such as operation code, source address, sequence number, and length code.
  • the trailer is typically a technique for generating redundancy checks, such as a cyclic redundancy code for detecting errors.
  • the receiving node strips off the control information, performs the required synchronization and error detection, and reinserts the control information onto the departing packet.
  • Packet switching arose, in part, to fulfill the need for low cost data communications in networks developed to allow access to host computers.
  • Special purpose computers designated as communication processors have been developed to offload the communication handling tasks which were formerly required of the host.
  • the communication processor is adapted to interface with the host and to route packets along the network; consequently, such a processor is often simply called a packet switch.
  • Data concentrators have also been developed to interface with hosts and to route packets along the network. In essence, data concentrators serve to switch a number of lightly used links onto a smaller number of more heavily used links. They are often used in conjunction with, and ahead of, the packet switch.
  • packet-switched data transmission is accomplished via predetermined end-to-end paths through the network, in which user packets associated with a great number of users share link and switch facilities as the packets travel over the network.
  • the packets may require storage at nodes between transmission links of the network until they may be forwarded along the respective outgoing link for the overall path.
  • connectionless transmission another mode of packet-switched data transmission, no initial connection is required for a data path through the network. In this mode, individual datagrams carrying a destination address are routed through the network from source to destination via intermediate nodes, and do not necessarily arrive in the order in which they were transmitted.
  • the widely-used Telenet public packet switching network routes data using a two-level hierarchy.
  • the hierarchy comprises a long distance-spanning backbone network with a multiplicity of nodes or hubs, each of which utilizes a cluster of backbone switches; and smaller geographic area networks with backbone trunks, access lines and clustered lower level switches connected to each hub.
  • Packet-switched data is transmitted through the network via VCs, using CCITT (International Consultative Committee of the International Telecommunications Union) X.75 protocol, which is a compatible enhancement of X.25 protocol.
  • CCITT International Telegraph and Telephone Consultative Committee of the International Telecommunications Union
  • X.25 is an interface organized as a three-layered architecture for connecting data terminals, computers, and other user systems or devices, generally refereed to as data terminal equipment (DTE), to a packet-switched network through data circuit terminating equipment (DCE) utilized to control the DTE's access to the network.
  • DTE data terminal equipment
  • DCE data circuit terminating equipment
  • DCEs of the network is routinely handled by the network operator typically using techniques other than X.25, communication between the individual user system and the respective DCE with which it interfaces to the network is governed by the X.25 or similar protocol.
  • X.25 establishes procedures for congestion control among users, as well as call setup (or connect) and call clearing (or disconnect) for individual users, handling of errors, and various other packet transmission services within the DTE-DCE interface.
  • X.25 is employed for virtual circuit (VC) connections, including the call setup, data transfer, and call clearing phases.
  • Call setup between DTEs connected to the network is established by one DTE issuing an X.25 call-request packet to the related DCE, the packet containing the channel number for the logical connections, the calling and called DTE addresses, parameters specifying the call characteristics, and the data.
  • the destination DCE issues an incoming call packet, which is of the same general format as the call-request packet, to the destination DTE, the latter replying with a call-accepted packet.
  • the calling DCE issues a call-connected packet to its related DTE.
  • the data transfer phase may begin by delivery of data packets.
  • Prospective routing paths in the network are initially determined by a network control center, which then transmits these predetermined paths to the backbone switches as routing tables consisting of primary and secondary choices of available links from each hub.
  • the secondary choices are viable only in the event of primary link failures, and the specific secondary link selection is a local decision at the respective hub based principally on current or recent traffic congestion patterns.
  • the unavailability of an outgoing link from a hub at the time of the call setup effects a clearing back of the VC for the sought call to the preceding hub.
  • An alternative link is then selected by that hub, or, if none is available there, the VC circuit is again cleared back to the next preceding hub, and so forth, until an available path is uncovered from the routing tables.
  • Messages concerning link and/or hub failures are communicated immediately to the network control center, and that information is dispatched to the rest of the network by the center.
  • the data processing devices reside in a plurality of cards or boards containing printed circuits or integrated circuits for performing the various functions of the respective device in combination with the system software.
  • the cards are inserted into designated slots in cages within a console, with backplane access to a data bus for communication with one another or to other devices in the network.
  • the VME bus is presently the most popular 16/32-bit backplane bus. References from time to time herein to cards or boards will be understood to mean the various devices embodied in such cards or boards.
  • PDNs public data networks
  • Many public data networks offer little or no security for communications between users and hosts or other data processing devices within the network, in keeping with the "public purpose" of the network and the desire for accessibility by a large number of actual and prospective users. Where restrictions on access are necessary or desirable, it is customary to assign each authorized user an identification (ID) number or a password, or both, which must be used to gain access to the host. More elaborate security measures are necessary where access may be had to highly confidential data.
  • ID identification
  • Some data communication networks involve a variety of different customers each of whom makes available a host and one or more databases to its users, and may place a level of security on its database which differs from the level placed by other customers on their respective hosts and databases. In those instances, it is customary to make the host responsible for security and access to itself and its associated database. Thus, a user might have access to certain destinations in the network without restriction, but no access to other destinations.
  • MNS Managed Networked Services
  • the present invention's overall approach to implementing the NM/MNS market offering is two fold.
  • the current opportunity that presents itself is MNS. While this market opportunity for clients is large, they need assistance in understanding data network management - for years they have been solely focused on voice. Additionally, they need to move into this market quickly in order to maintain and grow revenue.
  • the present invention includes a set of assets consisting primarily of job aids and software that can greatly reduce the clients' lead time for service implementation.
  • the present invention assists service providers by providing them the tools to better manage their carrier data networks - the packet switched networks of the future.
  • the present invention significantly enhances and scales MNS assets to address carrier network management in a data networking world. This solution template enables the convergence of circuit and packet switching network control centers and workforces.
  • the present invention's market offering suggests companies take a graduated approach to delivering MNS.
  • One end of the continuum consists of MNS for current network services, including leased lines, frame relay, and X.25.
  • MNS for current network services, including leased lines, frame relay, and X.25.
  • On the far end is outsourced MNS characterized by long-term contracts, involving hundreds of millions of dollars.
  • the NM/MNS market offering is proposing that the companies go beyond the management of the router and the WAN, and into the world of the local area network (LAN), even as far as the desktop and business applications. Service providers have been intimidated by these propositions in the past, since management of the LAN and its equipment and applications has clearly not been their forte.
  • Business Strategy - Companies may look to the present invention for assistance in creating a business strategy for entering the MNS market.
  • this type of engagement will defines a company's target market for MNS (small, mid-market, large) and defines the service offerings that are best suited for the company to offer.
  • Design and Implementation - Companies may be ready to move to the design and implementation phases of creating an MNS capability.
  • the present invention will confirm that their network meets the requirements to provide the service, then assist the client in the designing and implementing an appropriate solution suite.
  • an online catalog of services has been created.
  • the present invention's solution is a continuous cycle that begins with the four major processes associated with NM/MNS. These processes drive the technology and the people components of the solution. Within each of these processes are a number of core functions and sub-functions.
  • the MNS Online Catalog contains all of this information, including the supporting process, technology and organizational solutions for each function.
  • MNSIS Managed Networked Services Integrated Solution
  • each process should be performed in order to provide a complete NM/MNS solution.
  • each process has a number of associated functions and sub-functions that provide the complete picture of the process.
  • the major functions associated with each process are as follows.
  • the main goal of the technology solution is to provide access to network information to make informed decisions.
  • the present invention includes three layers of management: element management, information services management and presentation management. Every action starts with an incident. Processing is tailored to handling the incident with technology that responds to the unique characteristics of each incident. Element Manager
  • the element manager communicates with the network elements to receive alarms and alerts through trapping and polling techniques.
  • the element manager is the layer where the primary data reduction functions reside. At this layer, events received at the element manager will be filtered, aggregated and correlated to further isolate problems within the network. Information that is deemed critical to monitor and manage the network is translated into a standard object format and forwarded to the Information Services Manager.
  • An element manager can be, but is not necessarily, software which adheres to open standards such as the Simple Network Management Protocol (SNMP) and the
  • OMG Object Management Group's
  • CORBA Common Object Request Broker Architecture
  • the information services manager provides the data management and data communications between element managers and presentation managers. All information forwarded from the element managers is utilized by the information services manager to provide information to the network operators.
  • the information services manager adheres to CORBA standards to provide ubiquitous information access via an Object Request
  • ORB ORB
  • the ORB allows the information services manager to share management information stored in distributed databases.
  • the information services manager stores critical management information into operational (real-time) and analytical (historical) distributed databases. These databases provide common data storage so that new products can be easily inserted into the management environment. For example, if an event is received at an element manager that is deemed critical to display to a network user, the information services manager will store a copy of the alarm in the operational database and then forward the alarm to the appropriate network operator.
  • the databases includes online manuals for administrative purposes, as well as for the maintenance specialists to access element specific information.
  • the databases also provide procedures, policies and computer based training to network users.
  • the information services manager provides requested information (real-time and historical) to the network users via the presentation manager.
  • the presentation manager performs the function its name implies: the presentation of the information to an end user. Because different locations and job functions require access to different types of information, there are at least two types of display methods. The first is for graphic intensive presentations and the second is for nomadic use, such as field technicians. The first environment requires a graphic intensive display, such as those provided by X-Windows/MOTIF. The second environment is potentially bandwidth poor where dial-up or wireless access may be used along with more traditional LAN access.
  • the people vision for the NM/MNS include an organization model for customer service support, the corresponding roles and responsibilities for this organization model and a conceptual design for workforce transformation to packet switching.
  • Customer service support provides a single point of contact that is customer focused. This single point of contact provides technical expertise in resolving customer incidents, troubles and requests. Generally a three tiered support structure is optimal for satisfying customer service needs. Each tier, or level, possesses an increasing level of skill, with tasks and responsibilities distributed accordingly. Such a structure is as follows: Tier 1 - typically has a broad set of technical skills and is the first level of support to the customer. Typically this group is responsible for resolving 60-70 percent of the opened problems.
  • Tier 2 - are technical experts and field support personnel who may specialize in specific areas. Typically this group is responsible for resolving 30-40 percent of the opened problems.
  • Tier 3 - are considered solution experts and often consist of hardware vendors, software vendors or custom application development / maintenance teams (in- depth skills needed to investigate and resolve difficult problems within their area of expertise). They are the last resort for solving the most difficult problems. Typically this group is responsible for resolving 5 percent or fewer of the opened problems.
  • the above model is generally referred to as the Skilled Model because personnel at all three tiers are highly skilled. This model generally creates a high percentage of calls resolved on the first call.
  • Other approaches include:
  • Tier 1 only logs calls, they do not resolve calls.
  • One advantage of this model is that skilled resources don't have to waste time logging calls.
  • the integrated network management solution template consists of a suite of best of breed third party software products that automate problem diagnosis, notification, custom-developed reporting, and IP services monitoring.
  • Web-Based SLA Reporting Tool - is a browser based tool that provides the personalized SLA reports to customers in both a template and ad-hoc format.
  • Data Mining Demonstration Provides the capability to analyze network management data looking for patterns and correlations across multiple dimensions. Build models of the behavior of the data in order to predict future growth or problems and facilitate managing the network in a proactive, yet cost-effective manner.
  • Customer to Event Mapping Module Add-on module to the Managed Networked Services Integrated Solution which maps network element events, to service offerings, to customers. This tool allows the Customer Service Representative to proactively address network outages with customers.
  • Service Planning includes both the strategic and tactical planning required to manage distributed environments effectively. Although most planning typically occurs during rollout of the system, certain planning activities must otherwise take place. Service Planning ensures that change can be successfully controlled and implemented. • Service Management Planning
  • Systems Management consists of the day-to-day operational functions required to maintain the system (e.g. fault detection / correction, security management and performance management). • Production Control
  • Service Management controls the overall service to the users of the system. It isolates users from how the system is managed, and ensures that users receive the quality support services they need to carry out their daily business activities. • SLA/OLA Management
  • the present invention includes a system, method, and article of manufacture for providing a hybrid circuit switched/packet switched network.
  • This hybrid network is used as a transitioning network to transition from old "Core” network architectures to "New Core” networks.
  • the details of the NGN transitioning network will first be set forth after which details relating to specific billing aspects of the present invention will be described.
  • PSTN, wireless, and cable networks have continued to grow at their organic rates determined by the growth of the vertical services they were providing.
  • the data networks used a small portion of the backbone SONET bandwidth, while PSTN was still the dominant bandwidth user.
  • IP traffic Due to the exponential growth in IP traffic, the IP based data networks are soon slated to utilize more bandwidth than the PSTN.
  • huge technical advances in packet technologies have made it possible to carry traditional voice over IP networks. This has started a move towards the "Next Generation Network (NGN)" where there will be more sharing of common network infrastructure to provide services, and these services will start to become more interoperable.
  • NTN Next Generation Network
  • the "NGN” is a transition network which will exist during the transformation from the current "Core” to the "New Core".
  • the present invention maps a course for the network evolution from circuit to packet switched technology using a migratory approach in which the network becomes a hybrid circuit and packet topology over a 3 to 7 year period.
  • the current wire-line "Core” network consists of parallel PSTN, SMDS, ATM, Frame-Relay, B/PRI and IP networks.
  • the PSTN network has been evolving over the last century and is a mix of old and new circuit switched technologies.
  • the PSTN network mainly provides point-to-point interactive two-way voice communication services.
  • the service set has evolved to include many intelligent network (LN) service features.
  • LN intelligent network
  • AIN Advanced Intelligent Networks
  • the major IN requirements include session establishment, advanced call processing, call routing and call treatment (network messages and call termination).
  • Examples of applications and features are the CLASS family of services (Call waiting, Call forwarding, Conference calling, Call rejection), enhanced call routing, Number Portability, Calling Card Services, and Audio delivered Information Services (e.g. travel, stocks and weather).
  • SCE Service Creation Environment
  • Data networks in the "Core” While the PSTN was growing in feature functionality as well as traffic demand, new data networks have been created to support the inter-networking of computing devices. These data networks provide interconnection to geographically dispersed computing devices at varying levels of transmission bandwidth (e.g. 56/64K, T-l/E-1, T-3/E-3, OC-3/STM-1).
  • the data networks consist of many technologies e.g. SMDS, ATM, frame-relay and IP. In some cases, these data networks themselves are parallel networks, in other cases, they share a common technology in the backbone (e.g. ATM can be the backbone for frame relay and IP data networks). These data networks share the same SONET based backbone with the PSTN network.
  • the services on the PSTN and the data networks are very distinct and non- interoperable (example: voice versus web access).
  • IP based services that will combine applications such as electronic commerce (procurement, warehousing, distribution and fulfillment) as well as online banking to present the consumer with an integrated boundless shopping experience.
  • the NGN also employs the use of new wire-line broadband access technologies, notably xDSL.
  • Traditional wire-line access technologies will continue to be deployed at higher and higher speeds; wire-line access will move from predominantly T-l speeds to T-3 and OC-n speeds.
  • These new broadband access technologies will increase the need for higher bandwidth in "NGN" core.
  • the "NGN” core continues to use a SONET backbone, but will gradually move to using (D)WDM technologies to provide the bandwidth required to support broadband access.
  • New and emerging technologies such as Giga-Bit Ethernet and Wire Speed IP may find their way to the network backbone, but not until Giga-bit Ethernet technology matures to handle a wide array of network services such as connection oriented circuit emulation.
  • the use of Wire Speed IP technology is suitable for an enterprise network but lacks the robustness and scalability needed for carrier grade backbones. For this reason, there will always be a need for ATM in the backbone.
  • the architecture in the "NGN” provides seamless interoperability of services between the packet based network and the traditional PSTN.
  • New “NGN” packet based capabilities will be developed to support AIN type features, while inter-operating with legacy PSTN/SS7/ATN.
  • Large scale innovation in the IP based IN type capabilities e.g. global number transparency, utilization of web based information, rich media communications
  • Innovations on the PSTN will occur slowly, and may be restricted to maintaining interoperability of legacy PSTN with "NGN”. In many cases, legacy
  • PSTN components e.g. SSP, SCP
  • IP IP based packet switching technologies
  • TCP Transmission Control Protocol
  • UDP circuit switched technologies
  • NTN Next Generation Network
  • NGN Network-to-Network Interface
  • IP/PSTN Gateways IP/PSTN address translators
  • IP/SS7 Gateways IP enabled SSP's
  • IP based Intelligent Peripherals IP based Intelligent Peripherals.
  • new components as will be describe later
  • features like directories, policies, user authentication, registration, session encryption, etc. will also be developed to enhance the IN capabilities.
  • the NGN- IN enablers will provide the next level of intelligence in order to address communication over mixed media types, control of multiple session characteristics, collaborative communications needs, ubiquitous network access, "any to any” communications, and multimedia delivered information services.
  • the Intelligent IP (I 2 P) Network enablers are categorized as follows:
  • the components for the "NGN” are described as individual functional units but may be combined for practicality on individual network devices as the requirements dictate. These components have been designed to operate in a distributed network environment to increase the flexibility of the NGN and New Core.
  • the architecture provides a robust, secure and isolated messaging infrastructure for delivering control plane information to these devices.
  • This infrastructure includes a well defined message set for accessing the functions that are provided by these components and data that resides in the rules database.
  • the control plane architecture is efficient and has a unique mechanism for sharing service, user and control data without duplication. This permits mobile NGN service users to maintain the same experience and have access to the same information regardless of where or how they access the network.
  • a user's profile may be physically stored in a Rules database in the United States, the user may access the network from Europe and be automatically granted access to the specific services and features that normally would be available during his US service experience.
  • the remote session controller in Europe would communicate with the cross network location register and rules database server to identify the subscriber's "home" rules database in order to collect the policies and profile of the subscriber for use in Europe; this is done by using the inter device message sets (command and control ) over the control plane sub network. Unlike other mechanisms often employed, this mechanism does not replicate this information onto the local (European) rules database, making long term control data management predictable.
  • the design is CORBA compliant and therefore can be interconnected with other standards based networks.
  • Session requirements such as Bandwidth, Quality Of Service, Class Of Service
  • Session Manager / Event Logger (Session Control)
  • This process or application is critical since it is the "glue" between the end user application and the communications network. It is responsible for collection and distribution of end-user session preferences, application requirements, access device capability and accounting policy information to the required "IN enabling" components. In summary its main functions are to:
  • This functional component Similar to the Home location register in the wireless / cellular telephony world. This functional component provides the required policies governing users who access third party networks and cross geographical boundaries. It keeps in constant contact with other cross network location registers of the geographically dispersed but inter-connected networks, exchanging accounting, service feature profile and control data for local and roaming subscribers.
  • IP based access methods As the PSTN based access methods go away, entirely IP based access methods will emerge in the "New Core", where all end devices connected to the "New Core" are IP enabled. All existing methods of wire-line based access (xDSL, T-l, T-3, fiber) will continue to provide access to IP based services over the "New Core”. New access technologies (e.g. power-line) will emerge, but will still use the same packet based capabilities in the "New Core".
  • wire-line based access xDSL, T-l, T-3, fiber
  • the current wireless "Core” network consists of wireless based access and roaming capabilities that inter-operate with wire-line PSTN "Core” infrastructure to provide interoperable PSTN services.
  • the wireless PSTN access infrastructure will also migrate to connect to "NGN” and “New Core” to provide wireless PSTN access services while utilizing new capabilities in the "NGN” and the “New Core”.
  • There will also be innovations in the wireless end-devices such that they will become IP enabled, and will thus allow a broad range of innovations by allowing mobility to the wire-line IP based service capabilities (e.g. web browsing, e-mail etc.).
  • LMDS is an emerging technology in the local high speed wire-less access, which utilizes the 25- 35 GHz microwave spectrum for point to point and point to multi-point communications.
  • the end users either share an antenna connected to a digital receiver which is connected to a channel bank .
  • the application server be it voice (PBX), video (CODEC), or Data (Router or Switch) interfaces with the NGN via the channel bank.
  • PBX voice
  • CDEC video
  • Router or Switch Data
  • a session originates from the application which interacts with the server to request authentication (AAA), then a session is established between originator and destination application by routing the call through the NGN components such as Gateways and Switches.
  • LEO low earth orbiting satellites
  • Cable networks were developed for mainly broadband broadcast of analog video entertainment services.
  • the current "Core” cable infrastructure is suitable to serve one way video broadcast. Cable service providers are now upgrading their cable infrastructure to support high speed internet access.
  • cable will provide a new access mechanism for IP services, while simultaneously transport video content using the current video broadcast technology.
  • the IP enabled devices attached to the "NGN” cable infrastructure can take advantage of all the new components and capabilities described in the wire-line “NGN”. This will enable seam-less services between devices that are accessing the "NGN' via a wire-line or cable infrastructures.
  • This "NGN” cable infrastructure can provide IP based telephony services using the same components of the wire-line "NGN” that provide IP telephony to wire- line IP devices.
  • the digital network segment that interfaces with the "NGN” comprises of a coaxial cable local loop which is connected to a cable data modulator running QAM/DPSK protocols.
  • the coaxial loop is terminated at the customer premise by an Ethernet cable modem which delivers the IP Tone to the applications (Voice, Video, Data) that may reside on a PC or application server.
  • the cable modems used provide users and applications with a wide range of bandwidth options from 2 to lOMbits per second depending on configuration and choice of equipment vendor.
  • the cable With the evolution of the "New Core” in the wire- line, the cable will continue to provide another broadband access mechanism for IP based services.
  • the "New Core” matures and enhances in capabilities (probably 10 years away), such that it can provide high speed real-time video content (to provide same quality as cable), it can be envisaged that the cable will becomes an entirely IP access mechanism (just like all wire-line access becomes an IP access mechanism).
  • the broadcast video content will be delivered to IP enabled cable attached devices just like any other rich media will be delivered over the IP network.
  • video encoding technologies such as MPEG2 and motion JPEG will be further improved to deliver higher resolution digital media over the cable infrastructure using NGN and CORE delivery mechanisms.
  • the network becomes transparent and the applications and content drive the creativity of the service creation process.
  • the PSTN like services will be delivered to devices connected via cable access just like they are delivered to other wire-line connected devices on the "New Core".
  • the network transformation plan comprises of the following phases Strategy - Market Trial
  • Service Launch Develop, plan and manage the detailed network, systems, process and program management aspects of the launch of a "New Core” that is applicable for the network based on the strategy developed above. This ensures that the network systems planned and developed will be future- ready.
  • the OSS and back-office systems are be able to support the processes required for service creation and management in the "New Core".
  • the network creation processes provides the program management tools to ensure that the launch is successfully executed. These include entry and exit criteria for network creation, KPIs for quality management, program planning and management tool-kits.
  • the network creation process provides tools to assist the client into improving efficiencies of these parallel journeys. These optimization efforts will include organizational, process and technology driven changes to create efficiency based on consolidation of processes, as well as measurement tools to determine the success of such consolidation.
  • the network architecture roadmap and business blueprint will act as the foundation to ensure that during the consolidation phase the "NGN" maintains the required architecture framework to sustain it for the long term.
  • a typical telecommunication network comprises multiple telecommunication switches located throughout a geographical area. When a user makes a call, the call may be routed through one or more switches before reaching its destination.
  • Figure IA illustrates an exemplary telecommunications system 102 across the United States.
  • a caller 104 places a call from Los Angeles, California to a party 112 located in New York City, New York.
  • Such a call is typically transmitted across three (3) switches: the Los Angeles, California switch 106; the Chicago, Illinois switch 108; and the New York City, New York switch 110.
  • the originating switch is the Los Angeles, California switch 106
  • the terminating switch is the New York City, New York switch 110.
  • Each of the switches, 106-110 is connected to two (2) or more Data Access Points (DAP) 116- 120, for instance a primary DAP 116-120 and a backup DAP 116-120.
  • DAP Data Access Points
  • a DAP 116-120 is a facility that receives requests for information from the switches 106-110, processes the requests, and returns the requested information back to the requesting switch 106-110.
  • the switches 106- 110 use information from the DAPs 116-120 to process calls through the network.
  • each switch 106-110 When a call passes through one of the switches, 106-110, that switch creates a call record.
  • the call record contains information on the call, including but not limited to: routing, billing, call features, and trouble shooting information.
  • each switch 106-110 that processed the call completes the associated call record.
  • the switches 106-110 combine multiple call records into a billing block.
  • the switch 106-110 When a switch 106-110 fills the billing block, the switch 106-110 sends the billing block to a billing center 114.
  • the billing center 114 receives one billing block from each switch 106- 110 that handled the call, which in this case would be three billing blocks.
  • the billing center 114 searches each billing block and retrieves the call record associated with the call, thereby retrieving one call record per switch 106-110 that handled the call.
  • the billing center 114 then uses one or more of the retrieved call records to generate a billing entry.
  • the billing center 114 is also connected to each DAP 116-120 to retrieve information regarding a switch 106-110 or call record.
  • billing in the present invention is increased because the hybrid network also contains proxy intelligence.
  • FIG. IB shows a block diagram of the Network Data Management 130 in accordance with a preferred embodiment of the present invention.
  • Network Data Management 130 encompasses the collection of usage data and events for the purpose of network performance and traffic analysis. This data may also be an input to Billing (Rating and Discounting) processes at the Service Management Layer, depending on the service and its architecture.
  • the process provides sufficient and relevant information to verify compliance/ non-compliance to Service Level Agreements (SLA).
  • SLA Service Level Agreements
  • This process ensures that the Network Performance goals are tracked, and that notification is provided when they are not met (threshold exceeded, performance degradation). This also includes thresholds and specific requirements for billing. This includes information on capacity, utilization, traffic and usage collection. In some cases, changes in traffic conditions may trigger changes to the network for the purpose of traffic control. Reduced levels of network capacity can result in requests to Network Planning for more resources.
  • FIG. 1B-1 is a flowchart illustrating a network data management process in accordance with a preferred embodiment.
  • step 150 data is collected relating to usage and events occurring over a hybrid network.
  • step 152 the data is analyzed to determine a status of the hybrid network which in turn, in step 154, is utilized during management of the hybrid network.
  • step 156 billing rates and discounts are determined based on the status of the hybrid network.
  • the present invention also uses a Customer Interface Management process 132, as shown in Figure IC, to directly interact with customers and translate customer requests and inquiries into appropriate "events" such as, the creation of an order or trouble ticket or the adjustment of a bill.
  • This process logs customer contacts, directs inquiries to the appropriate party, and tracks the status to completion. In those cases where customers are given direct access to service management systems, this process assures consistency of image across systems, and security to prevent a customer from harming their network or those of other customers. The aim is to provide meaningful and timely customer contact experiences as frequently as the customer requires.
  • Figure lC-1 is a flowchart illustrating a Customer Interface Management Process in accordance with a preferred embodiment.
  • step 158 a service level agreement is received for a hybrid network customer.
  • step 160 the service level agreement is stored after which, in step 162, inquiries are received from network customers reflecting occurrences related to the hybrid network. Thereafter, in step 164, events are generated based on the customer inquiries and the service level agreement.
  • the Network Data Management 130 and Customer Interface Management process 132 are used to give information to the Customer Quality of Service Management Process 134, as shown in
  • the Customer Quality of Service Management Process 134 encompasses monitoring, managing and reporting of quality of service as defined in Service Descriptions, Service Level Agreements (SLA), and other service-related documents. It includes network performance, but also performance across all of service parameters, e.g., Orders Completed On Time. Outputs of this process are standard (predefined) and exception reports, including; dashboards, performance of a service against an SLA, reports of any developing capacity problems, reports of customer usage patterns, etc. In addition, this process responds to performance inquiries from the customer. For SLA violations, the process supports notifying Problem Handling and for QoS violations, notifying Service Quality Management 136. The aim is to provide effective monitoring. Monitoring and reporting must provide SP management and customers meaningful and timely performance information across the parameters of the services provided. The aim is also to manage service levels that meet specific SLA commitments and standard service commitments.
  • FIG. 1D-1 is a flowchart illustrating a Customer Quality of Service Management Process in accordance with a preferred embodiment.
  • a hybrid network event is received which may include customer inquiries, required reports, completion notification, quality of service terms, service level agreement terms, service problem data, quality data, network performance data, and/or network configuration data.
  • the system determines customer reports to be generated and, in step 170, generates the customer reports accordingly based on the event received.
  • Figure IE shows a block diagram of the Service Quality Management 136 in accordance with a preferred embodiment of the present invention.
  • the Service Quality Management Process 136 supports monitoring service or product quality on a service class basis in order to determine
  • This process also encompasses taking appropriate action to keep service levels within agreed targets for each service class and to either keep ahead of demand or alert the sales process to slow sales.
  • the aim is to provide effective service specific monitoring, management and customers meaningful and timely performance information across the parameters of the specific service.
  • the aim is also to manage service levels to meet SLA commitments and standard commitments for the specific service.
  • FIG. 1E-1 is a flowchart illustrating a Service Quality Management Process in accordance with a preferred embodiment.
  • a hybrid network event is received that may include forecasts, quality objectives, available capacity, service problem data, quality of service violations, performance trends, usage trends, problem trends, maintenance activity, maintenance progress, and/or credit violations.
  • quality management network data is determined and, in step 176, the quality management network data is generated.
  • Such quality management network data may include constraint data, capacity data, service class quality data, service modification recommendations, additional capacity requirements, performance requests, and/or usage requests.
  • a network process to which to send the generated data is identified.
  • Figure IF shows a block diagram of the Problem Handling Process 138.
  • the Problem Handling Process receives information from the Customer Interface Management Process 132 and the Customer Quality of service Management Process 134. It is responsible for receiving service complaints from customers, resolve them to the customer's satisfaction and provide meaningful status on repair or restoration activity. This process is also responsible for any service-affecting problems, including
  • This proactive management also includes planned maintenance outages.
  • the aim is to have the largest percentage of problems proactively identified and communicated to the customer, to provide meaningful status and to resolve in the shortest timeframe.
  • FIG. 1F-1 is a flowchart illustrating a Problem Handling Management Process in accordance with a preferred embodiment.
  • a notification of a problem within a hybrid network is received by the system.
  • a resolution for the problem within the hybrid network is determined.
  • the resolution may include a status report, resolution notification, problem reports, service reconfiguration, trouble notification, service level agreement violations, and/or outage notification.
  • the progress of the implementation of the resolution is tracked.
  • the Problem Handling Process 138 and the Network Data Management 130 feed information to the Rating and Discounting Process 140, as shown in Figure IG.
  • This process applies the correct rating rules to usage data on a customer-by-customer basis, as required. It also applies any discounts agreed to as part of the Ordering Process, for promotional discounts and charges, and for outages. In addition, the Rating and Discounting Process 140 applies any rebates due because service level agreements were not met. The aim is to correctly rate usage and to correctly apply discounts, promotions and credits.
  • Figure lG-1 is a flowchart illustrating Rating and Discounting Process in accordance with a preferred embodiment.
  • step 185 hybrid network customer usage information is received.
  • step 186 network service level agreement violations are collected, and, in step 187, network quality of service violations are received by the Rating and Discounting system.
  • step 188 rating rules are applied to the network customer usage information.
  • step 189 negotiated discounts are determined based on the network quality of service violations and, in step 190, rebates are determined based on the network service level agreement violations.
  • billing data reflecting the usage information, the negotiated discounts, and the rebates is provided to generate a customer invoice.
  • the Invoice and Collections Process 142 creates correct billing information.
  • This process encompasses sending invoices to customers, processing their payments and performing payment collections.
  • this process handles customer inquiries about bills, and is responsible to resolve billing problems to the customer's satisfaction.
  • the aim is to provide a co ⁇ ect bill and, if there is a billing problem, resolve it quickly with appropriate status to the customer.
  • An additional aim is to collect money due the service provider in a professional and customer supportive manner.
  • FIG. 1H-1 is a flowchart illustrating an Invoice and Collections Process in accordance with a preferred embodiment.
  • customer account inquiries and customer payment information is received by the system.
  • billing data including discounts due to quality of service violations and rebates due to service level agreement violations, is collected and processed.
  • customer account invoices are created for distribution based on the customer payment information and the billing data.
  • Mediation and activity tracking are provided by the event logger and event manager.
  • the event logger and event manager feed the rating and billing information for degraded service using the personally customized rules database.
  • the event driver, collector and manager Utilizing an expert system for the tailored capabilities of each customer, the event driver, collector and manager analyze notification events generated by the system. When a notification event is received the system analyzes the event and uses it to identify the customer. The notification event is also used to credit the customer if they experience a non-impacting event that breaches the customer's contract. In addition to the system itself generating the notification event, the customer is also able to notify the provider directly should such an event occur.
  • Figure 2 A is a flowchart illustrating media communication over the hybrid network of the present invention.
  • the hybrid network transfers the media over the network using IP information to route it to the appropriate destination.
  • the media transfe ⁇ ed over the network may be telephony data, image data, or any other data capable of packet switched transmission.
  • events are generated based on the quality of service of the media transfer. As discussed above with reference to Figure ID and Figure IE, these events include performance notifications due to SLA violations, and customer generated events from the
  • a third step 224 the events generated in step 222 are utilized to generate a bill for the customer.
  • the bill is modified based on events generated during the media transfer. For example, events representing
  • the Problem Handling Process 138 is responsible for receiving service complaints and other service-affecting problems. Together with the Network Data Management 130, the Problem Handling Process feeds data to the Discounting Process 140.
  • the Discounting Process 140 applies the correct rating rules on a customer-by-customer basis, and applies discounts for events, such as outages and other SLA violations.
  • the Invoice and Collections Process 142 utilizes the information from the Discounting Process 140 to create customer billing information.
  • a telephone call comes into a switch on a transmission line referred to as the originating port, or trunk.
  • the originating port is one of many transmission lines coming into the switch from the same location of origin. This group of ports is the originating trunk group.
  • the switch After processing an incoming call, the switch transmits the call to a destination location, which may be another switch, a local exchange carrier, or a private branch exchange.
  • the call is transmitted over a transmission line referred to as the terminating port, or trunk. Similar to the originating port, the terminating port is one of a group of ports going from the switch to the same destination. This group of ports is the terminating trunk group.
  • Contemporary telecommunication networks provide customers with the capability of using the general public network as well as the capability of defining a custom virtual network (VNet).
  • VNet virtual network
  • a VNet customer defines a private dialing plan, including plan telephone numbers.
  • a VNet customer is not limited to the default telephone numbers allocated to a public telecommunication system dedicated to a specific geographic region, but can define custom telephone numbers.
  • a switch Upon processing a telephone call, a switch must generate a call record large enough to contain all of the needed information on a call.
  • the call record must not be so large that the typical call results in the majority of the record fields in the call record to be unused. In such a case, storing such call records results in large amounts of wasted storage, and transmitting such a call record causes unnecessary transmissions.
  • a fixed length call record format such as a 32-word call record.
  • a word is two (2) bytes, or sixteen (16) bits.
  • a fixed length record format cannot expand when new call features are implemented. More importantly, fixed call record formats cannot handle expanded data fields as the telecommunications network becomes more complex with new features and telephone numbers.
  • Contemporary fixed length record formats include time point fields recording local time in three (3) second increments where local switch time represents the time of day at a switch.
  • the timepoint fields are used by the network switches, billing center, and other network subsystems.
  • Each subsystem may require the time period for a different use and in a different format, such as in an epoch time format.
  • Epoch time is the number of one (1) second increments since a particular date and time in history. For example, the billing center requires epoch time for its billing records whereas switch reports and error logs require local switch time.
  • each subsystem may require a finer granularity of precision than the current three (3) second increments.
  • the switches have passed the burden of translating the time into a usable format to the network subsystems.
  • the fixed record format cannot accommodate the various time period requirements because it only contains the time periods in local switch time at a low level of precision. Because of its fixed nature, the fixed record format cannot expand to include different time formats, nor to include a finer granularity of precision, such as a one (1) second increment.
  • An embodiment solves the problem of providing a flexible and expandable call record format by implementing both a small and a large call record format.
  • the embodiment implements a default 32-word call record format, plus an expanded 64-word call record format.
  • An embodiment uses a 32-word call record format for the typical telephone call, which comprises the majority of all telephone calls, and uses a 64-word call record format when additional information is needed regarding the call.
  • This implementation provides the flexibility needed to efficiently manage varying data requirements of a given call record. New call features can be developed and easily inco ⁇ orated into the variable call record format of the present invention.
  • This embodiment also records timepoints in the epoch time format.
  • the embodiment records the origination time of a call in epoch time format, and the remaining timepoints are offsets, or the number of seconds, from that origination time.
  • This embodiment solves the problems associated with converting to and from daylight savings time because daylight savings time is a local time offset and does not affect the epoch time.
  • the timepoints in epoch time format require less space in the call record than they do in local switch time format.
  • the epoch time format may represent coordinated universal time (UTC), as determined at Greenwich, England, which has a time zone of zero (0) local switch time, or any other time.
  • UTC coordinated universal time
  • Epoch time is only a format and does not dictate that UTC must be used.
  • the billing time and the local switch time may be in UTC or local time, and the local switch time may not necessarily be the same time that is used for billing. Therefore, the switch must keep billing time and local switch time separate in order to prevent the problems that occur during daylight savings time changes.
  • This embodiment solves the problem of uniquely identifying each telephone call and all of the call records associated with a specific telephone call by providing a unique identifier to each call record. It generates a network call identifier (NCID) that is assigned to each call record at the point of call origination, that is, the originating switch generates an NCID for each telephone call.
  • NCID accompanies the associated telephone call through the telecommunications network to the termination point at the terminating switch. Therefore, at any point of a telephone call in the network, the associated NCID identifies the point and time of origin of the telephone call.
  • Each switch through which the telephone call passes records the NCID in the call record associated with the call.
  • the NCID is small enough to fit in a 32-word call record, thereby reducing the data throughput and storage.
  • the NCID provides the billing center and other network subsystems with the ability to match originating and terminating call records for a specific telephone call.
  • This embodiment also provides the switch capability of discarding a received NCID and generating a new NCID.
  • a switch discards a received NCID if the NCID format is invalid or unreliable, thereby ensuring a valid unique identifier to be associated with each call going through the network. For instance, an NCID may be unreliable if generated by third party switches in the telecommunications network.
  • This embodiment relates to switches of a telecommunication network that generate call records using a flexible and expandable record format.
  • the call record formats include a small (preferably 32-word) and a large (preferably 64-word) expanded format. It would be readily apparent to one skilled in the relevant art to implement a small and large record format of different sizes.
  • the embodiment also relates to switches of a telecommunication network that generate a unique NCID for each telephone call traversing the network.
  • the NCID provides a mechanism for matching all of the call records associated with a specific telephone call. It would be readily apparent to one skilled in the relevant art to implement a call record identifier of a different format.
  • the chosen embodiment is computer software executing within a computer system.
  • Figure 2B shows an exemplary computer system.
  • the computer system 202 includes one or more processors, such as a processor 204.
  • the processor 204 is connected to a communication bus 206.
  • the computer system 202 also includes a main memory 208, preferably random access memory (RAM), and a secondary memory 210.
  • the secondary memory 210 includes, for example, a hard disk drive 212 and/or a removable storage drive 214, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, etc.
  • the removable storage drive 214 reads from and/or writes to a removable storage unit 216 in a well known manner.
  • Removable storage unit 216 also called a program storage device or a computer program product, represents a floppy disk, magnetic tape, compact disk, etc.
  • the removable storage unit 216 includes a computer usable storage medium having therein stored computer software and/or data.
  • Computer programs are stored in main memory 208 and/or the secondary memory 210. Such computer programs, when executed, enable the computer system 202 to perform the functions of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 204 to perform the functions of the present invention. Accordingly, such computer programs represent controllers of the computer system 202.
  • Another embodiment is directed to a computer program product comprising a computer readable medium having control logic (computer software) stored therein.
  • the control logic when executed by the processor 204, causes the processor 204 to perform the functions as described herein.
  • Another embodiment is implemented primarily in hardware using, for example, a hardware state machine.
  • Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant arts.
  • This embodiment provides the switches of a telecommunication network with nine (9) different record formats. These records include : Call Detail Record (CDR), Expanded Call Detail Record (ECDR), Private Network Record (PNR), Expanded Private Network Record (EPNR), Operator
  • CDR Call Detail Record
  • ECDR Expanded Call Detail Record
  • PNR Private Network Record
  • EPNR Expanded Private Network Record
  • Example embodiments of the nine (9) call record formats discussed herein are further described in Figures 1-5.
  • the embodiments of the call records of the present invention comprise both 32- word and 64-word call record formats. It would be apparent to one skilled in the relevant art to develop alternative embodiments for call records comprising a different number of words and different field definitions.
  • Figure 3 shows a graphical representation of the CDR and PNR call record formats.
  • Figures 4A and 4B show a graphical representation of the ECDR and EPNR call record formats.
  • Figure 5 shows a graphical representation of the OSR and POSR call record format.
  • Figures 6A and 6B show a graphical representation of the EOSR and EPOSR call record formats.
  • Figure 7 shows a graphical representation of the SER record format.
  • the CDR and PNR and thereby the ECDR and EPNR, are standard call record formats and contain information regarding a typical telephone call as it passes through a switch.
  • the CDR is used for a non- VNET customer
  • the PNR is used for a VNET customer and is generated at switches that originate VNET calls.
  • the fields of these two records are identical except for some field-specific information described below.
  • the OSR and POSR contain information regarding a telephone call requiring operator assistance and are generated at switches or systems actually equipped with operator positions.
  • a switch completes an OSR for a non- VNET customer and completes a POSR for a private VNET customer.
  • These records are only generated at switches or systems that have the capability of performing operator services or network audio response system (NARS) functions.
  • NARS network audio response system
  • a SER is reserved for special events such as the passage of each hour mark, time changes, system recoveries, and at the end of a billing block.
  • the SER record format is also described in more detail below.
  • FIGS 8(A) and 8(B) collectively illustrate the logic that a switch uses to determine when to use an expanded version of a record format.
  • a call 202 comes into a switch 106-110 (called the current switch for reference pu ⁇ oses; the current switch is the switch that is currently processing the call), at which time that switch 106-110 determines what call record and what call record format (small/default or large/expanded) to use for the call's 802 call record.
  • the switch 106-110 makes nine (9) checks for each call 802 that it receives.
  • the switch 106-110 uses an expanded record for a call 802 that passes any check as well as for a call 802 that passes any combination of checks.
  • the first check 804 determines if the call is involved in a direct termination overflow (DTO) at the current switch 106-110.
  • DTO direct termination overflow
  • the switch 802 to an 800 number and the original destination of the 800 number is busy. If the original destination is busy, the switch overflows the telephone call 802 to a new destination. In this case, the switch must record the originally attempted destination, the final destination of the telephone call 802, and the number of times of overflow. Therefore, if the call 802 is involved in a DTO, the switch 106-110 must complete an expanded record (ECDR, EPNR, EOSR, EPOSR) 816.
  • ECDR expanded record
  • the second check 806 made on a call 802 by a switch 106-110 determines if the calling location of the call 802 is greater than ten (10) digits.
  • the calling location is the telephone number of the location from where the call 802 originated. Such an example is an international call which comprises at least eleven (11) digits. If the calling location is greater than ten (10) digits, the switch records the telephone number of the calling location in an expanded record (ECDR, EPNR, EOSR, EPOSR) 816.
  • a switch 106-110 makes a third check 808 on a call 802 to determine if the destination address is greater than seventeen (17) digits.
  • the destination address is the number of the called location and may be a telephone number or trunk group. If the destination is greater than seventeen (17) digits, the switch records the destination in an expanded record (ECDR, EPNR, EOSR, EPOSR)
  • a switch 106-110 makes a fourth check 810 on a call 802 to determine if the pre-translated digits field is used with an operated assisted service call.
  • the pre-translated digits are the numbers of the call 802 as dialed by a caller if the call 202 must be translated to another number within the network. Therefore, when a caller uses an operator service, the switch 106-110 records the dialed numbers in expanded record (EOSR, EPOSR) 816.
  • EOSR expanded record
  • a switch 106-110 determines if the pre-translated digits of a call 802 as dialed by a caller without operator assistance has more than ten (10) digits. If there are more than ten (10) pre-translated digits, the switch 106-110 records the dialed numbers in expanded record (ECDR, EPNR) 816.
  • a switch 106-110 determines if more than twenty-two (22) digits, including supplemental data, are recorded in the Authorization Code field of the call record.
  • the Authorization Code field indicates a party who gets billed for the call, such as the calling location or a credit card call. If the data entry requires more than twenty-two (22) digits, the switch 106-110 records the billing information in an expanded record (ECDR, EPNR, EOSR, EPOSR) 816.
  • a switch 106-110 determines if the call 802 is a wideband call.
  • a wideband call is one that requires multiple transmission lines, or channels. For example, a typical video call requires six (6) transmission channels : one (1) for voice and five (5) for the video transmission. The more transmission channels used during a wideband call results in a better quality of reception. Contemporary telecommunication systems currently provide up to twenty- four (24) channels. Therefore, to indicate which, and how many, of the twenty-four channels is used during a wideband call, the switch records the channel information in an expanded record (ECDR, EPNR) 828.
  • ECDR expanded record
  • a switch 106-110 determines if the time and charges feature was used by an operator.
  • the time and charges feature is typically used in a hotel scenario when a hotel guest makes a telephone call using the operator's assistance and charges the call 802 to her room. After the call 802 has completed, the operator informs the hotel guest of the charge, or cost, of the call 802. If the time and charges feature was used with a call 802, the switch 106- 110 records the hotel guest's name and room number in an expanded record (EOSR, EPOSR) 832.
  • EOSR expanded record
  • the ninth, and final, check 824 made on a call 802 by a switch 106-110 determines if the call
  • EVS/NARS enhanced voice service/network audio response system
  • An EVS/NARS is an audio menu system in which a customer makes selections in response to an automated menu via her telephone key pad.
  • Such a system includes a NARS switch on which the audio menu system resides. Therefore, during an EVS/NARS call 802, the NARS switch 106-110 records the customer's menu selections in an expanded record (EOSR, EPOSR) 832.
  • EOSR expanded record
  • the switch 106-110 uses the default record format (OSR, POSR) 830.
  • TBCD Telephone Binary Coded Decimal
  • All TBCD digit fields must be filled with TBCD-Null, or zero, prior to data being recorded.
  • dialed digit formats conform to these conventions :
  • N digits 2-9
  • the valid field values are the digits 2-9.
  • Each call record except SER, contains call specific timepoint fields.
  • the timepoint fields are recorded in epoch time format.
  • Epoch time is the number of one second increments from a particular date/time in history.
  • the embodiment of the present invention uses a date/time of midnight (00:00 am UTC) on January 1, 1976, but this serves as an example and is not a limitation. It would be readily apparent to one skilled in the relevant art to implement an epoch time based on another date/time.
  • Timepoint 1 represents the epoch time that is the origination time of the call 802.
  • the other timepoint stored in the records are the number of seconds after Timepoint 1, that is, they are offsets from Timepoint 1 that a particular timepoint occurred.
  • timepoint fields must be filled in with "O's" prior to any data being recorded. Therefore, if a timepoint occurs, its count is one (1) or greater. Additionally, timepoint counters, not including Timepoint 1, do not rollover their counts, but stay at the maximum count if the time exceeds the limits.
  • the switch clock reflects local switch time and is used for all times except billing. Billing information is recorded in epoch time, which in this embodiment is UTC.
  • the Time offset is a number reflecting the switch time relative to the UTC, that is, the offset due to time zones and, if appropriate, daylight savings time changes. There are three factors to consider when evaluating time change relative to UTC. First, there are time zones on both sides of UTC, and therefore there may be both negative and positive offsets. Second, the time zone offsets count down from zero (in Greenwich, England) in an Eastward direction until the International Dateline is reached. At the Dateline, the date changes to the next day, such that the offset becomes positive and starts counting down until the zero offset is reached again at Greenwich.
  • FIG 9 illustrates the control flow of the Change Time command 900, which changes the Local Switch Time and the Time Offset.
  • the switch enters step 902 and prompts the switch operator for the Local Switch Time and Time Offset from UTC.
  • step 902 the switch operator enters a new Local Switch Time and Time Offset.
  • the new time and Time Offset are displayed back to the switch operator.
  • the switch operator must verify the entered time and Time Offset before the actual time and offset are changed on the switch.
  • step 906 the switch operator verifies the changes, the switch proceeds to step 908 and generates a SER with an Event Qualifier equal to two which identifies that the change was made to the Local Switch Time and Time Offset of the switch.
  • the billing center uses the SER for its bill processing.
  • the switch proceeds to step 910 and exits the command.
  • step 910 exits the command without updating the Local Switch Time and
  • FIG 10 illustrates the control flow for the Change Daylight Savings Time command 1000 which is the second command for changing time.
  • the switch enters step 1002 and prompts the switch operator to select either a Forward or Backward time change.
  • the switch operator makes a selection.
  • step 1004 if the switch operator selects the Forward option, the switch enters step 1006.
  • step 1006 the switch sets the Local Switch Time forward one hour and adds one hour (count of 60) to the Time Offset.
  • the switch then proceeds to step 1010.
  • the switch sets the Local Switch Time back one hour and subtract one hour (count of 60) from the Time Offset.
  • step 1010 the switch operator must verify the forward or backward option and the new Local Switch Time and Time Offset before the actual time change takes place. If in step 1010, the switch operator verifies the new time and Time Offset, the switch proceeds to step 1012 and generates a SER with an Event Qualifier equal to nine which changes the Local Switch Time and Time Offset of the switch. The switch proceeds to step 1014 and exits the command. Referring back to step 1010, if the switch operator does not verify the changes, the switch proceeds to step 1014 and exits the command without updating the Local Switch Time and Time Offset.
  • the billing records are affected by the new Time Offset.
  • This embodiment allows the epoch time, used as the billing time, to increment normally through the daylight savings time change procedure, and not to be affected by the change of Local Switch Time and Time Offset.
  • An embodiment provides a unique NCID that is assigned to each telephone call that traverses through the telecommunications network.
  • the NCID is a discrete identifier among all network calls.
  • the NCID is transported and recorded at each switch that is involved with the telephone call.
  • the originating switch of a telephone call generates the NCID.
  • the chosen embodiment of the NCID of the present invention is an eighty-two (82) bit identifier that is comprised of the following subfields:
  • Originating Switch ID 14 bits
  • This field represents the NCS Switch ID as defined in the Office Engineering table at each switch.
  • the SER call record contains an alpha numeric representation of the Switch ID.
  • a switch uses the alphanumeric Switch ID as an index into a database for retrieving the corresponding NCS Switch ID.
  • Originating Trunk Group 14 bits: This field represents the originating trunk group as defined in the 32/64-word call record format described above.
  • Originating Port Number (19 bits) This field represents the originating port number as defined in the 32/64-word call record format described above.
  • Timepoint 1 (32 bits) : This field represents the Timepoint 1 value as defined in the 32/64-word call record format described above.
  • NCID of a different format.
  • Each switch records the NCID in either the 32 or 64-word call record format.
  • the 32-word call record format intermediate and terminating switches can be used to record the
  • NCID in the AuthCode field of the 32-word call record if the AuthCode filed is not used to record other information.
  • the Originating Switch ID is the NCS Switch ID, not the alphanumeric Switch ID as recorded in the SER call record. If the AuthCode is used for other information, the intermediate and terminating switches record the NCID in the 64-word call record format. In contrast, originating switches do not use the AuthCode field when storing an
  • NCID in a 32-word call record Originating switches record the subfields of the NCID in the corresponding separate fields of the 32-word call record. That is, the Originating Switch ID is stored as an alphanumeric Switch ID in the Switch ID field of the SER call record; the Originating Trunk Group is stored in the Originating Trunk Group field of the 32-word call record; the Originating Port Number is stored in the Originating Port field of the 32-word call record; the Timepoint 1 is stored in the Timepoint 1 field of the 32-word call record; the Sequence Number is stored in the NCID Sequence Number field of the 32-word call record.
  • the 32-word call record also includes an NCID Location (NCIDLOC) field to identify when the NCID is recorded in the AuthCode field of the call record.
  • NCIDLOC NCID Location
  • the NCID Location field contains a '1,' then the AuthCode field contains the NCID. If the NCID Location field contains a '0,' then the NCID is stored in its separate sub-fields in the call record. Only intermediate and terminating switches set the NCID Location field to a T because originating switches store the NCID in the separate fields of the 32-word call record.
  • the expanded call record includes a separate field, call the NCID field, to store the 82 bits of the NCID. This call record is handled the same regardless of whether an originating, intermediate, or terminating switch stores the NCID.
  • the Originating Switch ID is the NCS Switch ID, not the alphanumeric Switch
  • FIG 11 illustrates the control flow of the Network Call Identifier switch call processing.
  • a call 202 comes into a switch 106-110 (called the current switch for reference pu ⁇ oses; the current switch is the switch that is currently processing the call) at step 1104.
  • the current switch receives the call 202 and proceeds to step 1106.
  • the current switch accesses a local database and gets the trunk group parameters associated with the originating trunk group of the call 202. After getting the parameters, the current switch proceeds to step 1108.
  • the current switch determines if it received an NCID with the call 202. If the current switch did not receive an NCID with the call 202, the switch continues to step 1112.
  • step 1112 the switch analyzes the originating trunk group parameters to determine the originating trunk group type. If the originating trunk group type is an InterMachine Trunk (IMT) or a release link trunk (RLT), then the switch proceeds to step 1116.
  • IMT InterMachine Trunk
  • RLT release link trunk
  • An IMT is a trunk connecting two normal telecommunication switches
  • a RLT is a trunk connecting an intelligent services network (ISN) platform to a normal telecommunication switch.
  • the current switch reaches step 1116, the current switch knows that it is not an originating switch and that it has not received an NCID.
  • the current switch analyzes the originating trunk group parameters to determine whether it is authorized to create an NCID for the call 202.
  • step 1116 if the current switch is not authorized to create an NCID for the call 202, the current switch proceeds to step 1118.
  • the current switch knows that it is not an originating switch, it did not receive an NCID for the call 202, but is not authorized to generate an NCID. Therefore, in step 1118, the current switch writes the call record associated with the call 202 to the local switch database and proceeds to step 1120.
  • the current switch transports the call 202 out through the network with its associated NCID. Step 1120 is described below in more detail.
  • step 1116 if the current switch is authorized to create an NCID for the call 202, the current switch proceeds to step 1114.
  • step 1114 the current switch generates a new NCID for the call 202 before continuing to step 1136.
  • step 1136 the current switch writes the call record, including the NCID, associated with the call 202 to the local switch database and proceeds to step 1120.
  • step 1120 the current switch transports the call 202 out through the network with its associated NCID. Step 1120 is described below in more detail.
  • step 1114 the current switch knows that it is an originating switch and, therefore, must generate a NCID for the call 202. Step 1114 is described below in more detail. After generating a NCID in step
  • step 1114 the current switch proceeds to step 1136 to write the call record, including the NCID, associated with the call 202 to the local database. After writing the call record, the current switch proceeds to step 1120 to transport the call out through the network with its associated NCID. Step 1120 is also described below in more detail.
  • step 1110 the current switch processes the received NCID.
  • the current switch may decide not to keep the received NCID thereby proceeding from step 1110 to step 1114 to generate a new NCID. Step 1110 is described below in more detail.
  • step 1114 the current switch may generate a new NCID for the call 202 before continuing to step 1136. Step 1114 is also described below in more detail.
  • step 1136 the current switch writes the call record associated with the call 202 to the local database. The current switch then proceeds to step 1120 and transports the call 202 out through the network with its associated NCID. Step 1120 is also described below in more detail.
  • the current switch may decide to keep the received NCID thereby proceeding from step 1110 to step 1115.
  • the current switch adds the received NCID to the call record associated with the call 202. Steps 1110 and 1115 are described below in more detail.
  • the current switch continues to step 1136 where it writes the call record associated with the call 202 to the local database.
  • the current switch then proceeds to step 1120 and transports the call 202 out through the network with its associated NCID. Step 1120 is also described below in more detail.
  • Figure 12 illustrates the control logic for step 1110 which processes a received NCID.
  • the current switch enters step 1202 of step 1110 when it determines that an NCID was received with the call 202.
  • the current switch analyzes the originating trunk group parameters to determine the originating trunk group type. If the originating trunk group type is an IMT or
  • step 1212 the current switch knows that it is not an originating switch and that it received an NCID for the call 202. Therefore, in step 1212, the current switch keeps the received NCID and exits step 1110, thereby continuing to step 1115 in Figure 11, after which the current switch stores the received NCID in the call record and transports the call.
  • the current switch determines if the originating trunk group type is an IMT or RLT.
  • the current switch determines if the originating trunk group type is an Integrated Services User Parts Direct Access Line (ISUP DAL) or an Integrated Services Digital Network Primary Rate Interface (ISDN PRI).
  • ISUP is a signaling protocol which allows information to be sent from switch to switch as information parameters.
  • An ISUP DAL is a trunk group that primarily is shared by multiple customers of the network, but can also be dedicated to a single network customer.
  • an ISDN PRI is a trunk group that primarily is dedicated to a single network customer, but can also be shared by multiple network customers.
  • a network customer is an entity that leases network resources.
  • step 1204 if the current switch determines that the trunk group type is not an ISUP DAL or ISDN PRI, the current switch proceeds to step 1206.
  • the current switch knows that it received an NCID that was not generated by a switch that is part of the telecommunication network or by a switch that is a customer of the network. Therefore, in step 1206, the current switch discards the received NCID because it is an unreliable NCID. From step 1206, the current switch exits step 1110, thereby continuing to step 1114 in Figure 11 where the current switch creates a new NCID and transports that NCID with the call 202.
  • step 1204 if the current switch determines that the originating trunk group type is an ISUP DAL or ISDN PRI, the current switch continues to step 1208.
  • the current switch determines that the originating trunk group type is an ISUP DAL or ISDN PRI.
  • the current switch knows that it received an NCID from a customer trunk group. Therefore, the current switch analyzes the originating trunk group parameters to determine whether it is authorized to create a new NCID for the call 202. The cu ⁇ ent switch may be authorized to create a new NCID and overwrite the NCID provided by the customer to ensure that a valid NCID corresponds to the call 202 and is sent through the network. In step 1208, if the current switch is not authorized to create a new NCID for the call 202, the cu ⁇ ent switch proceeds to step 1210. In step 1210, the cu ⁇ ent switch checks the validity of the received NCID, for example, the NCID length. If the received NCID is invalid, the current switch proceeds to step 1206. In step 1206, the current switch discards the invalid NCID. From step 1206, the cu ⁇ ent switch exits step 1110, thereby continuing to step 1114 in Figure 11 where the cu ⁇ ent switch creates a new NCID and transports that NCID with the call 202.
  • step 1212 the current switch keeps the received NCID and exits step 1110, thereby continuing to step 1115 in Figure 11 where the cu ⁇ ent switch stores the received NCID in the call record and transports the call.
  • Figure 13A illustrates the control logic for step 1114 which generates an NCID.
  • the cu ⁇ ent switch enters step 1302 when an NCID must be created.
  • the current switch calculates a sequence number.
  • the sequence number represents the number of calls which have occu ⁇ ed on the same port number with the same Timepoint 1 value.
  • the first call has a sequence number value of '0,' after which the sequence number increases incrementally for each successive call that originates on the same port number with the same Timepoint 1 value.
  • the cu ⁇ ent switch proceeds to step 1304.
  • the current switch creates a call record for the call 202, including in it the call's 202 newly created NCID.
  • the current switch exits step 1114 and proceeds to step 1136 in Figure 11 where the current switch writes the call record to the local switch database.
  • Figure 13B illustrates the control logic for step 1115 which adds a received NCID to the call record associated with the call 202.
  • the current switch Upon entering step 1115, the current switch enters step 1306.
  • the current switch knows that it has received a valid NCID from an intermediate or terminating switch, or from a customer switch.
  • the cu ⁇ ent switch determines if the AuthCode field of the 32-word call record is available for storing the NCID. If the AuthCode field is available, the cu ⁇ ent switch proceeds to step 1310. In step 1310, the cu ⁇ ent switch stores the NCID in the AuthCode field of the 32-word call record.
  • the current switch must also set the NCID Location field to the value ' 1' which indicates that the NCID is stored in the AuthCode field.
  • step 1306 if the AuthCode field is not available in the 32-word call record, the cu ⁇ ent switch proceeds to step 1308.
  • step 1308 the cu ⁇ ent switch stores the NCID in the NCID field of the 64-word call record.
  • step 1308 the cu ⁇ ent switch exits step 1115 and continues to step 1136 in Figure 11 where the current switch writes the call record to the local switch database.
  • Figure 14 illustrates the control logic for step 1120 which transports the call from the cu ⁇ ent switch.
  • steps 1402 and 1412. Upon entering step 1402 from step 1136 of Figure 11, the cu ⁇ ent switch knows that it has created an NCID or has received a valid NCID.
  • the cu ⁇ ent switch accesses a local database and gets the trunk group parameters associated with the terminating trunk group for transporting the call 202. After getting the parameters, the current switch proceeds to step 1404.
  • the cu ⁇ ent switch determines the terminating trunk group type. If the terminating trunk is an ISUP trunk, the current switch proceeds to step 1408.
  • step 1408 the current switch analyzes the parameters associated with the ISUP trunk type to determine whether or not to deliver the NCID to the next switch. If the current switch is authorized to deliver the NCID, the current switch proceeds to step 1416.
  • step 1416 the cu ⁇ ent switch transports the call to the next switch along with a SS7 initial address message (IAM).
  • the NCID is transported as part of the generic digits parameter of the IAM.
  • the IAM contains setup information for the next switch which prepares the next switch to accept and complete the call 202.
  • the format of the generic digits parameter is shown below in Table 306 :
  • step 1412 the current switch transports the call 202 to the next switch under normal procedures which consists of sending an IAM message to the next switch without the NCID recorded as part of the generic digits parameter. After transporting the call 202, the cu ⁇ ent switch proceeds to step 1418, thereby exiting the switch processing.
  • step 1404 if the cu ⁇ ent switch determines that the terminating trunk is not an
  • the cu ⁇ ent switch proceeds to step 1406.
  • the cu ⁇ ent switch determines if the terminating trunk group is an ISDN trunk (the terminating trunk group is dedicated to one network customer). If the terminating trunk group is an ISDN, the current switch proceeds to step 1410.
  • the current switch analyzes the parameters associated with the ISDN trunk group type to determine whether or not to deliver the NCID to the next switch. If the cu ⁇ ent switch is authorized to deliver the NCID, the cu ⁇ ent switch proceeds to step 1414.
  • the current switch transports the call to the next switch along with a setup message.
  • the setup message contains setup information for the next switch which prepares the next switch to accept and complete the call 202.
  • the NCID is transported as part of the locking shift codeset 6 parameter of the setup message.
  • Table 307 The format of the locking shift codeset 6 parameter is shown below in Table 307 :
  • the current switch After transporting the call 202 and the setup message, the current switch proceeds to step 1418, thereby exiting the switch processing.
  • step 1412 the current switch transports the call 202 to the next switch under normal procedures which consists of sending a setup message to the next switch without the NCID recorded as part of the locking shift codeset 6 parameter. After transporting the call 202, the cu ⁇ ent switch proceeds to step 1418, thereby exiting the switch processing.
  • step 1412 this step is also entered from step 1118 on Figure 11 when the cu ⁇ ent switch did not receive an NCID, is an intermediate or terminating switch, and is not authorized to create an NCID.
  • the current switch also transports the call 202 to the next switch under normal procedures which consists of sending an IAM or setup message to the next switch without the NCID recorded as part of the parameter. After transporting the call 202, the current switch proceeds to step 1418, thereby exiting the switch processing.
  • a system and method for the switches of a telecommunications network to generate call records for telephone calls using a flexible and expandable record format Upon receipt of a telephone call, a switch in the network analyzes the telephone call to determine whether the default call record is sufficiently large to store call record information pertaining to the telephone call, or whether the expanded call record must be used to store the call information pertaining to the telephone call. After determining which call record to use, the switch generates the default or expanded call record. The switch sends a billing block, comprised of completed call records, to a billing center upon filling an entire billing block.
  • a caller In today's telephony environment, a caller must contact an operator to initiate a conference call and/or have all parties dial a common number to connect into a conference call. This requires the cost of a human operator and the inconvenience of dialing a predefined number to be carried as overhead of each conference call. It also makes it very inefficient to schedule a conference call and assure that all parties are available to participate. It also requires a dedicated number for all the parties to access to facilitate the call.
  • a callback system is facilitated by a caller accessing a display from a computer and filling out information describing the parameters of a call.
  • Information such as the date and time the call should be initiated, billing information, and telephone numbers of parties to participate in the call could be captured.
  • a central o distributed computing facility with access to the hybrid network transmits e-mail in a note to each part required for the call copying the other parties to verify participation and calendar the event.
  • the e-ma would include any particulars, such as the password associated with the call and time the call would b commenced.
  • the necessary network facilities would also be reserved to assure the appropriate Qualit of Service (QOS) would be available, and when the date and time requested arrived, the call is initiate by contacting each of the participants whether they be utilizing a telephone attached to a PSTN or a voice capable apparatus (such as a computer or intelligent television) attached to the hybrid network. Any time during scheduling, initiation or duration of the call, any party could request operator assistan by selecting that service from the display associated with the call.
  • QOS Qualit of Service
  • a custom profile is provided as an extensi to the users existing profile information.
  • the custom profile allows a user to store frequent conferenc call participants information.
  • the profile contains participant's telephone numbers (which could be
  • DDD Downlink Data Network
  • IDDD IDDD
  • E-mail address E-mail address
  • paging service fax number
  • secretary phone number fax number
  • location time zone
  • working hours working hours
  • other pertinent information that may useful for initiating a call.
  • Default profiles based on company or organization needs are also enabled and can be tailored to meet the needs of a particular user based on more global information.
  • Billing information would also be provided online.
  • a user could enter a pre-arranged billing number the ability to bill to a credit card or telephone number. If billing to a telephone number, the system treats the call like a collect or third party call to verify billing.
  • profile information were predefined for a particular call scenario, then another option would allow a immediate connection of a conference call or single call at the press of a button, much as speed dialing performed today except that more than one caller could be joined without intervention of the calling party, Internet callers are supported and an operator can be joined as required.
  • the Internet is a method of interconnecting physical networks and a set of conventions for using networks that allow the computers they reach to interact. Physically, the Internet is a huge, global network spanning over 92 countries and comprising 59,000 academic, commercial, government, and military networks, according to the Government Accounting Office (GAO), with these numbers expected to double each year. Furthermore, there are about 10 million host computers, 50 million users, and 76,000 World-Wide Web servers connected to the Internet.
  • the backbone of the Internet consists of a series of high-speed communication links between major supercomputer sites and educational and research institutions within the U.S. and throughout the world.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • RRCs Requests for Comments
  • T has established numerous standards governing protocols and line encoding for telecommunication devices. Because many of these standards are referenced throughout this document, summaries of the relevant standards are listed below for reference.
  • ITU H.223 Multiplexing Protocols for Low Bitrate Multimedia Terminals
  • ITU H.225 ITU Recommendation for Media Stream Packetization and Synchronization on non-guaranteed quality of service LANs.
  • ITU H.263 Recommendation for Video Coder-Decoder for audiovisual services supporting video resolutions of 128296 pixels, 176344 pixels, 352488 pixels, 7042576 pixels and 14083152 pixels.
  • ITU H.322 Visual Telephone Terminals over Guaranteed Quality of Service LANs
  • ITU H.323 ITU Recommendation for Visual Telephone Systems and Equipment for
  • ISDN Integrated Services Digital Network the digital communication standard for transmission of voice, video and data on a single communications link.
  • RTP Real-Time Transport Protocol an Internet Standard Protocol for transmission of real-time data like voice and video over unicast and multicast networks.
  • IP Internet Protocol an Internet Standard Protocol for transmission and delivery of data packets on a packet switched network of interconnected computer systems.
  • TCP/IP Open protocol standards, freely available and developed independently of any hardware or operating system.
  • TCP/IP is capable of being used with different hardware and software, even if Internet communication is not required.
  • TCP/IP can be used over an Ethernet, a token ring, a dial-up line, or virtually any other kinds of physical transmission media.
  • the traditional type of communication network is circuit switched.
  • the U.S. telephone system uses such circuit switching techniques.
  • the switching equipment within the telephone system seeks out a physical path from the originating telephone to the receiver's telephone.
  • a circuit-switched network attempts to form a dedicated connection, or circuit, between these two points by first establishing a circuit from the originating phone through the local switching office, then across trunk lines, to a remote switching office, and finally to the destination telephone. This dedicated connection exists until the call terminates.
  • the establishment of a completed path is a prerequisite to the transmission of data for circuit switched networks.
  • the microphone captures analog signals, and the signals are transmitted to the Local Exchange Carrier (LEC) Central Office (CO) in analog form over an analog loop.
  • LEC Local Exchange Carrier
  • CO Central Office
  • the analog signal is not converted to digital form until it reaches the LEC Co, and even then only if the equipment is modem enough to support digital information.
  • the analog signals are converted to digital at the device and transmitted to the LEC as digital information.
  • the circuit guarantees that the samples can be delivered and reproduced by maintaining a data path of 64 Kbps (thousand bits per second). This rate is not the rate required to send digitized voice per se. Rather, 64Kbps is the rate required to send voice digitized with the Pulse Code Modulated (PCM) technique. Many other methods for digitizing voice exist, including ADPCM (32Kbps), GSM (13 Kbps), TrueSpeech 8.5 (8.5 Kbps), G.723 (6.4 Kbps or 5.3 Kbps) and Voxware RT29HQ (2.9 Kbps). Furthermore, the 64 Kbps path is maintained from LEC Central Office (CO) Switch to LEC CO, but not from end to end. The analog local loop transmits an analog signal, not 64 Kbps digitized audio. One of these analog local loops typically exists as the "last mile" of each of the telephone network circuits to attach the local telephone of the calling party.
  • PCM Pulse Code Modulated
  • circuit switching has two significant drawbacks.
  • circuit switching infrastructure is built around 64 Kbps circuits.
  • the infrastructure assumes the use of PCM encoding techniques for voice.
  • very high quality codecs are available that can encode voice using less than one-tenth of the bandwidth of PCM.
  • the circuit switched network blindly allocates 64 Kbps of bandwidth for a call, end-to-end, even if only one-tenth of the bandwidth is utilized.
  • each circuit generally only connects two parties. Without the assistance of conference bridging equipment, an entire circuit to a phone is occupied in connecting one party to another party. Circuit switching has no multicast or multipoint communication capabilities, except when used in combination with conference bridging equipment.
  • connection-oriented virtual or physical circuit setup such as circuit switching, requires more time at connection setup time than comparable connectionless techniques due to the end-to-end handshaking required between the conversing parties.
  • Message switching is another switching strategy that has been considered. With this form of switching, no physical path is established in advance between the sender and receiver; instead, whenever the sender has a block of data to be sent, it is stored at the first switching office and retransmitted to the next switching point after e ⁇ or inspection. Message switching places no limit on block size, thus requiring that switching stations must have disks to buffer long blocks of data; also, a single block may tie up a line for many minutes, rendering message switching useless for interactive traffic.
  • Packet switched networks which predominate the computer network industry, divide data into small pieces called packets that are multiplexed onto high capacity intermachine connections.
  • a packet is a block of data with a strict upper limit on block size that carries with it sufficient identification necessary for delivery to its destination.
  • Such packets usually contain several hundred bytes of data and occupy a given transmission line for only a few tens of milliseconds. Delivery of a larger file via packet switching requires that it be broken into many small packets and sent one at a time from one machine to the other.
  • the network hardware delivers these packets to the specified destination, where the software reassembles them into a single file.
  • Packet switching is used by virtually all computer interconnections because of its efficiency in data transmissions. Packet switched networks use bandwidth on a circuit as needed, allowing other transmissions to pass through the lines in the interim. Furthermore, throughput is increased by the fact that a router or switching office can quickly forward to the next stop any given packet, or portion of a large file, that it receives, long before the other packets of the file have arrived. In message switching, the intermediate router would have to wait until the entire block was delivered before forwarding. Today, message switching is no longer used in computer networks because of the superiority of packet switching.
  • the Internet is composed of a great number of individual networks, together forming a global connection of thousands of computer systems. After understanding that machines are connected to the individual networks, one can investigate how the networks are connected together to form an internetwork, or an internet. At this point, internet gateways and internet routers come into play.
  • gateways and routers provide those links necessary to send packets between networks and thus make connections possible. Without these links, data communication through the Internet would not be possible, as the information either would not reach its destination or would be incomprehensible upon arrival.
  • a gateway may be thought of as an entrance to a communications network that performs code and protocol conversion between two otherwise incompatible networks. For instance, gateways transfer electronic mail and data files between networks over the internet.
  • IP Routers are also computers that connect networks and is a newer term prefe ⁇ ed by vendors. These routers must make decisions as to how to send the data packets it receives to its destination through the use of continually updated routing tables.
  • routers By analyzing the destination network address of the packets, routers make these decisions. Importantly, a router does not generally need to decide which host or end user will receive a packet; instead, a router seeks only the destination network and thus keeps track of information sufficient to get to the appropriate network, not necessarily the appropriate end user. Therefore, routers do not need to be huge supercomputing systems and are often just machines with small main memories and little disk storage.
  • the distinction between gateways and routers is slight, and cu ⁇ ent usage blurs the line to the extent that the two terms are often used interchangeably. In cu ⁇ ent terminology, a gateway moves data between different protocols and a router moves data between different networks. So a system that moves mail between TCP/IP and OSI is a gateway, but a traditional IP gateway (that connects different networks) is a router.
  • the telephone system is organized as a highly redundant, multilevel hierarchy. Each telephone has two copper wires coming out of it that go directly to the telephone company's nearest end office, also called a local central office. The distance is typically less than 10 km; in the U.S. alone, there are approximately 20,000 end offices.
  • the concatenation of the area code and the first three digits of the telephone number uniquely specify an end office and help dictate the rate and billing structure.
  • the two-wire connections between each subscriber's telephone and the end office are called local loops. If a subscriber attached to a given end office calls another subscriber attached to the same end office, the switching mechanism within the office sets up a direct electrical connection between the two local loops. This connection remains intact for the duration of the call, due to the circuit switching techniques discussed earlier.
  • each end office has a number of outgoing lines to one or more nearby switching centers, called toll offices. These lines are called toll connecting trunks. If both the caller's and the receiver's end offices happen to have a toll connecting trunk to the same toll office, the connection may be established within the toll office. If the caller and the recipient of the call do not share a toll office, then the path will have to be established somewhere higher up in the hierarchy.
  • TCP/IP In addition to the data transfer functionality of the Internet, TCP/IP also seeks to convince users that the Internet is a solitary, virtual network. TCP/IP accomplishes this by providing a universal interconnection among machines, independent of the specific networks to which hosts and end users attach. Besides router interconnection of physical networks, software is required on each host to allow application programs to use the Internet as if it were a single, real physical network.
  • IP Internet Protocol/IP
  • datagrams The basis of Internet service is an underlying, connectionless packet delivery system run by routers, with the basic unit of transfer being the packet.
  • TCP/IP such as the Internet backbone
  • these packets are called datagrams. This section will briefly discuss how these datagrams are routed through the Internet.
  • routing is the process of choosing a path over which to send packets.
  • routers are the computers that make such choices. For the routing of information from one host within a network to another host on the same network, the datagrams that are sent do not actually reach the Internet backbone. This is an example of internal routing, which is completely self-contained within the network. The machines outside of the network do not participate in these internal routing decisions.
  • Direct delivery is the transmission of a datagram from one machine across a single physical network to another machine on the same physical network. Such deliveries do not involve routers. Instead, the sender encapsulates the datagram in a physical frame, addresses it, and then sends the frame directly to the destination machine. Indirect delivery is necessary when more than one physical network is involved, in particular when a machine on one network wishes to communicate with a machine on another network. This type of communication is what one may think of when speaking of routing information across the Internet backbone. In indirect delivery, routers are required. To send a datagram, the sender must identify a router to which the datagram can be sent, and the router then forwards the datagram towards the destination network.
  • routers in the Internet form a cooperative, interconnected structure, and datagrams pass from router to router across the backbone until they reach a router that can deliver the datagram directly.
  • ATM Asynchronous Transfer Mode
  • ATM networks require mode hardware including:
  • ATM inco ⁇ orates features of both packet switching and circuit switching, as it is designed to carry voice, video, and television signals in addition to data. Pure packet switching technology is not conducive to carrying voice transmissions because such transfers demand more stable bandwidth.
  • Frame relay systems use packet switching techniques, but are more efficient than traditional systems. This efficiency is partly due to the fact that they perform less error checking than traditional X.25 packet-switching services. In fact, many intermediate nodes do little or no error checking at all and only deal with routing, leaving the e ⁇ or checking to the higher layers of the system. With the greater reliability of today's transmissions, much of the e ⁇ or checking previously performed has become unnecessary. Thus, frame relay offers increased performance compared to traditional systems.
  • An Integrated Services Digital Network is an "international telecommunications standard for transmitting voice, video, and data over digital lines," most commonly running at 64 kilobits per second. The traditional phone network runs voice at only 4 kilobits per second.
  • an end user or company must upgrade to ISDN terminal equipment, central office hardware, and central office software. The ostensible goals of ISDN include the following:
  • An ISP is composed of several disparate systems. As ISP integration proceeds, formerly independent systems now become part of one larger whole with concomitant increases in the level of analysis, testing, scheduling, and training in all disciplines of the ISP.
  • the callback call flow commences when a caller calls into a local internet service provider.
  • the caller addresses the callback server to access the callback home page through the internet.
  • IP Internet Protocol
  • the caller enters, sees and/or updates default information such as: callback Internet Protocol (IP) address, call-to phone number (or multiple phone numbers to initiate a conference call) and charge-to method at a minimum.
  • IP Internet Protocol
  • Other information such as one or more numbers comprising entry of a Direct Distance Dialing (DDD), International Direct Distance Dialing (IDDD) or an IP address.
  • DDD Direct Distance Dialing
  • IDDD International Direct Distance Dialing
  • IP address can be utilized to specify a phone number or internet computer with voice capability.
  • a date and time can be prearranged for staging the callback operation. Additional information that can be captured at the callback server home page is detailed below in specific examples designed to elaborate and clarify in accordance with a prefe ⁇ ed embodiment.
  • the callback server sends a message to the callback switch with the appropriate calling information, and the callback switch initiates the callback leg of the call through the Public
  • PSTN Service Telephony Network
  • the callback switch initiates call-to call leg(s) which connect the call through path through PSTN to a telephone set.
  • an exception condition is indicated on the display if it is an IP call, or an audio indicia of the condition is transmitted to the callers if they are utilizing a standard telephony device.
  • a change in status could be a caller hanging up or a glitch occurring in the transmission.
  • the exception conditions are also captured for quality of service analysis.
  • a separate temporary webpage is created which is accessible to all members of the callback via a password selected by the initiator of the callback session. While all of the callers are being connected and throughout the duration of the telephony experience, the status of the call leg changes, and exception conditions, are indicated on the temporary created status webpage, or an audio indicia, where appropriate, of the condition is transmitted to the callers if they are utilizing a standard telephony device. Then, as callers are connected, removed, or change status, the display is updated to reflect the status of each participant's connection.
  • participant can drag and drop files, video clips or any other information which would be utilized as collaborative material during the call.
  • Each participant would be required to move information to their personal computer before the call terminated, since the webpage is temporary and is deleted upon termination of the call.
  • the temporary webpage is password protected to avoid unauthorized access to the information contained in the webpage.
  • the callback service includes support for one-to-one calling, one-to-many calling (conference calling, fax broadcast, text-to-speech message delivery, voice-to-voice message delivery, conference call reservation whereby the server sends E-mails to call-to participants with the conference call details, the server sends fax to call-to participants, or the server sends a text-to- speech message to call-to participants.
  • Real-time view of the status of each conference call participant, ANI and an alphanumeric representation to identify each participant entered by the initiator when a call is "reserved" can be displayed on screen as participants connect to conference. This information is captured as part of the call record set forth earlier.
  • a conference call without callback leg is enabled.
  • a callback customer participates through a Voice Over Network (VON) application utilizing a computer with voice capability, and can initiate a video screen popup on the computer display for manual operator assistance as detailed above in the description of a video operator.
  • VON Voice Over Network
  • the callback caller dials into a local internet service provider. Then, the caller addresses the host server containing the callback home page. At the callback server home page, the caller enters the information described earlier including a callback Internet Protocol (IP) address, call-to phone number (or multiple phone numbers to initiate a conference call) and charge-to method at a minimum. Then, for the callback call flow to initiate the call, the callback server, where the callback server home page is located, transmits a message to the callback switch with the necessary calling information generated from the callback home page. Finally, the callback switch establishes an internet voice session with the callback caller utilizing the internet service provider to establish a voice IP session with the initiating client. The callback switch then initiates the call-to call leg(s) routing the call out over the public service telephony network to a telephone set.
  • IP Internet Protocol
  • the system monitors each call in accordance with a preferred embodiment.
  • the system include rules that define what logic to execute when an exception occurs.
  • the rules include specialized processing based on whether the call is routed via a PSTN or the internet.
  • the system includes a default connection to a manual operator if no other correction of the connection is available. For example, if a caller hangs up during a teleconference and other callers are still connected, an exception message is sent to each of the still connected callers informing them of the status change.
  • Another aspect of the expert system is to ensure quality of service (QOS) and produce reports indicati both integrity and exceptions.
  • QOS quality of service
  • Scheduling of resources is tied to this expert system, which regulates whether calls can be scheduled based on available or projected resources at the time of the proposed c For example, since all calls used by this system are initiated by the callback switch, if there are insufficient outgoing trunk ports during the period of time that a callback subscriber requests, then the callback subscriber is prompted to select another time or denied access to the resources for that time. This is utilized to predict when additional ports and/or resources are required.
  • the NGN operations architecture specifies the points of insertion and collections for network wide events that feed the Fault Management systems. Since the components of the packet portion of the hybrid NGN infrastructure are in most cases manageable by SNMP or some other standard management protocol the major challenges are the following:
  • the network management components of the NGN provide comprehensive solutions to address these challenges. Correlation is provided by the use of rules based inference engines. Event gathering and inte ⁇ retation is typically performed by custom development of software interfaces which communicate directly with the network elements, process raw events and sort them by context prior to storing them. For example, alarms versus command responses. The mediation and standardization challenge is addressed by using a comprehensive library of all possible message types and network events categorize the numerous messages that the NGN generates.
  • FIG. 15 A is a flowchart showing a Fault Management Process 1550 in accordance with a prefe ⁇ ed embodiment of the present invention.
  • the Fault Management Process 1550 begins with a transmitting step 1552.
  • step 1552 data is transmitted over the hybrid network, including video and mixed audio information.
  • the data transmission generally makes full use of the hybrid networks mixed circuit-switched an packet-switched components.
  • the hybrid network includes approximately all the advantages of a packet based network while still making use of the older circuit-switched components already in place. The system is able to do this by co ⁇ elating events raised by both the circuit-switched and packet-switch network elements, as discussed later in relation to event and correlating steps 1554 and 1556.
  • a circuit-switched event gathering step 1554 an event is obtained from a circuit-switched based network element.
  • event gathering and inte ⁇ retation is typically performed by custom developed software interfaces which communicate directly with the network elements, process raw network events, and sort the events by context prior to storing them.
  • the events are co ⁇ elated in a co ⁇ elation step 1556.
  • a conelation step 1556 the event gathered in step 1554 is conelated with a second event obtained from a packet-switched network element.
  • packet-switched event gathering and inte ⁇ retation is typically performed by custom developed software interfaces which communicate directly with the network elements, process raw network events, and sort the events by context prior to storing them.
  • the co ⁇ elation is preferably provided by a rules based inference engine.
  • a fault message is created based on the correlated first and second events obtained in steps 1554 and 1556.
  • the fault message is created utilizing a comprehensive library of all possible message types and network events which categorizes the numerous messages that the hybrid network generates.
  • Figure 15B is a block diagram showing a Fault Management component 1500 in accordance with a prefe ⁇ ed embodiment of the present invention.
  • the Fault Management component 1500 records failures and exceptions in network devices (e.g. network routers or UNIX servers) and performs the following operations:
  • the Fault Management component 1500 includes the following elements:
  • NT Servers 1504 Any NT Server with BMC Patrol clients loaded.
  • HP OV Network Node Manager (Collector Component) 1508 - HP OpenView Network Node Manager is one product which performs several functions. In this context it is it is responsible for receiving performance information from BMC Patrol clients via BMC Patrol View.
  • Seagate NerveCenter 1510 - In a fault management context, Seagate NerveCenter performs root- cause co ⁇ elation of faults and events across the network.
  • HP OV Network Node Manager Network Map 1512 - HP OpenView Network Node Manager is one product which performs several functions. In this context it is responsible for maintaining and displaying the node level network map of the network the MNSIS architecture monitors.
  • HP OV Network Node Manager 1514 - HP OpenView Network Node Manager is one product which performs several functions. In this context it is it is responsible for receiving and displaying all events, regardless of their source.
  • Netcool HP OV NNM Probe 1516 An Omnibus Netcool probe which is installed on the same system as HP OV Network Node Manager and forwards events to the Omnibus Netcool Object Server.
  • RADIUS Remote Authentication Dial Determination
  • the Omnibus Netcool Object Server 1520 - is a real-time memory resident database which stores all cu ⁇ ent events (alerts). The events are viewable by operations personnel using a number of event lists and views, all of which are highly customizable by each operator.
  • Notification Spooler 1522 - A custom provided sub-component which spools job-files that specify which events have occurred for possible notifications.
  • Each spooled job represents a specific event that was received by the Netcool Object Server and may need to result in one or more notification actions.
  • Each job is stored as a file in a special notification spool directory.
  • Notification Actor 1526 A custom provided sub-component which determines the alert time, source node, and alert type from the loaded spooled job and initiates notification actions based as specified in the configuration file.
  • Notification actions include alphanumeric pages, trouble tickets, email, and resolution scripts. Multiple notification actions can be specified in the configuration files such that different actions are taken for different alert times, source nodes, and/or alert types. Default actions are also supported.
  • Alphanumeric Page 1528 An alphanumeric page sent using Telamon TelAlert via modem dialing the relevant paging provider. The alphanumeric page message provides contextual notification of actions to be performed. Context can include any information but frequently contains information such as the device name, problem description, and priority.
  • Electronic Mail Message 1530 An internet mail message send using the UNIX mail utility.
  • the mail message is frequently used to provide non-urgent notification of situations or actions automatically performed by the MNSIS architecture along with detailed context.
  • Local Script Execution 1532 Initiates any local script on the machine, which may initiate scripts or applications on other machines.
  • the Omnibus Netcool Remedy Gateway automatically reads alerts in the Netcool Object Server and opens tickets within Remedy as customized by the user.
  • the Remedy trouble ticket ID is returned to the Omnibus and can be viewed as further reference.
  • Oracle 1540 - Oracle is a relational database management system.
  • New Time Records 1544 -Time records co ⁇ esponding to new alerts in Netcool Object Server which need to be added to the Oracle time tables.
  • SOL Loader Script 1546 - A custom script which automatically loads records into Oracle via
  • the Proactive Threshold Manager is an automated network manager that forewarns service providers of a chance that a service level agreement to maintain a certain level of service is in danger of being breached.
  • the Proactive Threshold Manager provides real-time threshold analysis (that is, it continuously monitors for plan thresholds that have been exceeded) using algorithms. It receives call detail records from the Server and returns alarms which may be retrieved and examined using an NGN workstation.
  • the threshold manager resides on an NGN hybrid network computer.
  • a threshold generally is a number which, when exceeded, generates an alarm in the Proactive Threshold Manager indicating possible breach of a service level agreement. Thresholds may be specified for the time of day and/or the day of the week. Furthermore, a threshold may be applied to each category for which the Proactive threshold manager keeps counts, including the number of short-duration calls, long-duration calls, and cumulative minutes.
  • the priority is a multiple of the number of times a threshold has been exceeded. For example, if the threshold was 10 and the relevant count has reached 50, then the priority of the alarm is 5
  • Each alarm is available to an NGN hybrid network analyst via an NGN Workstation.
  • the workstation is a PC with access to a Server and retrieves the next available alarm of the highest priority.
  • the analyst investigates the alarm data and, if a service level agreement breach is suspected, notifies the provider and suggests appropriate actions to stop the breach.
  • FIG. 16A is a flowchart showing a Proactive Threshold Management Process 1600 in accordance with a prefe ⁇ ed embodiment of the present invention.
  • the process begins with a monitoring step 1602.
  • the Proactive Threshold Manager monitors the NGN hybrid network.
  • the Proactive Threshold Manager generally monitors the network at all times to ensure proper service is provided to subscribers of the network, by assisting service providers in maintaining a proper level of service.
  • the Proactive Threshold Manager determines the minimum level of service needed to avoid breaching subscriber service level agreements. Service level agreement information is generally provided to the Proactive Threshold Manager by the rules database which contains most pertinent subscriber information.
  • the Proactive Threshold Manager senses the cu ⁇ ent level of service which is being provided to customers.
  • Protocol converters assist the Proactive Threshold Manager in communicating with various components of the system. Protocol converters are able to translate information between the packet-switched an circuit-switched system components, thus allowing the Proactive Threshold Manager to communicate with all the components of the hybrid system.
  • the Proactive Threshold Manager compares the current level of service, sensed in step 1606, with the minimum level of service, determined in step 1604, to determine where the current level of service is in relation to the minimum level service which needs to be provided to subscribers.
  • the Proactive Threshold Manager provides an indication or alarm to the service provider if the cu ⁇ ent level of service is within a predetermined range with respect to the minimum level of service.
  • the threshold is preferably chosen such that the service provider is allowed enough time to cure the service level problem before the minimum service level is reached and the subscriber's service level agreement breached.
  • FIG. 16B is a flowchart showing a Network Sensing Process 1620 in accordance with one embodiment of the present invention.
  • the Network Sensing Process 1620 begins with an element monitoring step 1622.
  • custom developed element software monitors the individual network elements and generates events based on hardware occurrences, such as switch failures.
  • hardware occurrences such as switch failures.
  • switch failures typically, the various elements that make up the hybrid network are very different from one another.
  • custom software is generally needed for each network element or group of related network elements.
  • the custom developed software communicates directly with the hardware and generates events when various occu ⁇ ences related to the individual hardware happens. For example, when a hardware element fails, the related element software senses the failure and generates an event indicating the hardware failure and the general nature of the failure. The events are then routed to an element manger to processed.
  • events generated in step 1622 are filtered, aggregated, and correlated by an element manager.
  • the element manager is where the primary data reduction functions reside.
  • the element manager filters, aggregates, and co ⁇ elates the events to further isolate problems within the network. Any information that is deemed critical to monitor and manage the network is translated into standard object format in a translation step 1626.
  • a translation step 1626 information from step 1624 that is deemed critical to monitor and manage the network is translated into a standard object format. Generally, typical operational events are only logged and not translated into standard object format. However, critical information, such as hardware failure, is translated and forwarded to the Information Services Manager in an information provisioning step 1628.
  • step 1628 information from step 1626 is received by the Information Services Manager and forwarded to the Proactive Threshold Manager.
  • the Information Services Manager provides the data management and data communications between the element manager and other system components.
  • the Information Services Manager adheres to CORBA standards to provide universal information access by an object request broker.
  • the object request broker allows the Information Services Manager to share management information stored in distributed databases.
  • the Proactive Threshold Manager uses the information provided by the Information Services Manger to determine a cu ⁇ ent level of service and compare the current level of services with the minimum level of service that the service provider can provide without violating SLAs.
  • the element manager works with the Information Services Manager and the Presentation Manager to assist in the management of the hybrid network system.
  • the three components are briefly described below to provide context for the detailed discussion of the element manager that follows.
  • the element manager communicates with the network elements to receive alarms and alerts through trapping and polling techniques.
  • the element manager is the layer where the primary data reduction functions reside. At this layer, events received at the element manager can be filtered, aggregated and co ⁇ elated to further isolate problems within the network. Information that is deemed critical to monitor and manage the network is translated into a standard object format and forwarded to the Information Services Manager.
  • An element manager can be, but is not necessarily, software which adheres to open standards such as the Simple Network Management Protocol (SNMP) and the Object Management Group's (OMG) Common Object
  • CORBA Request Broker Architecture
  • the information services manager provides the data management and data communications between element managers and presentation managers. All information forwarded from the element managers is utilized by the information services manager to provide information to the network operators.
  • the information services manager adheres to CORBA standards to provide ubiquitous information access via an object request broker (ORB).
  • ORB object request broker
  • the ORB allows the information services manager to share management information stored in distributed databases.
  • the information services manager stores critical management information into operational (realtime) and analytical (historical) distributed databases. These databases provide common data storage so that new products can be easily inserted into the management environment. For example, if an event is received at an element manager that is deemed critical to display to a network user, the information services manager may store a copy of the alarm in the operational database and then forward the alarm to the appropriate network operator.
  • the databases includes online manuals for administrative pu ⁇ oses, as well as for the maintenance specialists to access element specific information.
  • the databases also provide procedures, policies and computer based training to network users.
  • the information services manager provides requested information (real-time and historical) to the network users via the presentation manager.
  • the presentation manager performs the function its name implies: the presentation of the information to an end user. Because different locations and job functions require access to different types of information, there are at least two types of display methods. The first is for graphic intensive presentations and the second is for nomadic use, such as field technicians. The first environment requires a graphic intensive display, such as those provided by X-
  • the second environment is potentially bandwidth poor where dial-up or wireless access may be used along with more traditional LAN access. This is also where browser technology is employed.
  • the Element Management Aspect of the present invention works in conjunction with other components of the system, such as Fault Management, to provide communication between the various network elements of the system.
  • FIG. 17 is a flowchart showing an Element Management Process 1700 in accordance with a preferred embodiment of the present invention.
  • the Element Management Process 1700 begins with a monitoring step 1702.
  • the Element Manager monitors the system for events generated by network elements. Generally, the Element Manager continuously monitors the system to translate events for other system components, such as the Fault Management Component.
  • the Element Manager receives events from various network elements. Preferably the events are provided by custom software interfaces which communicate directly with network elements. The software interfaces preferably process the raw network events and sort them by context prior to providing the events to the Element Manager.
  • a filtering and correlating step 1706 the Element Manager filters and co ⁇ elates the events received in step 1704. Preferably the co ⁇ elation is provided by a rules based inference engine. After collecting and correlating the events, the Element Manager performs a translation step
  • step 1708 the events co ⁇ elated in step 1706 are translated into standard object format.
  • a comprehensive library of all message types generated by the hybrid system is utilized to translate the correlated events into standard object format. Once the events are translated, they are ready for use by other system components, such as Fault Management or Billing.
  • the organization model for customer service support in the NGN network provides a single point of contact that is customer focused. This single point of contact provides technical expertise in resolving customer incidents, troubles and requests. Generally a three tiered support structure is greatly increases customer satisfaction in service needs. Each tier, or level, possesses an increased level of skill, with tasks and responsibilities distributed accordingly.
  • FIG 18 is a flowchart showing a Three Tiered Customer Support Process 1800 in accordance with a preferred embodiment of the present invention.
  • the Three Tiered Customer Support Process 1800 begins with a First Tier step 1802.
  • step 1802 a customer with a hybrid network problem is provided access to customer support personnel having a broad set of technical skills.
  • the customer is provided access to technical experts and field support personnel who may specialize in specific areas. The greater specialized nature of this group allows it to solve many problems the group in step 1802 could not solve. This group is generally responsible for solving 30-40% of all hybrid network problems. If the customers network problem is solved at this stage, the process ends. However, if the customers network problem is not solved at this stage, the process continues to a Third Tier step 1806.
  • the customer is provided access to solution experts who are often hardware vendors, software vendors, or customer application development and maintenance teems.
  • Customer network problems that get this far in the customer support process 1800 need individuals possessing in-depth skills to investigate and resolve the difficult problems with there area of expertise.
  • Solution experts are the last resort for solving the most difficult problems.
  • this group solves about 5% of all hybrid network problems.
  • the above model is generally refe ⁇ ed to as the Skilled Model because personnel at all three tiers are highly skilled. This model generally creates a high percentage of calls resolved on the first call.
  • Other approaches include a Functional Model, and a Bypass Model. In the Functional Model users are requested to contact different areas depending on the nature of the incident.
  • a customer calling a customer support center in accordance with one embodiment of the present invention is first asked a series of questions by an interactive voice response (IVR) system or an live operator.
  • the customer uses Touch-Tone keys on the telephone to respond to these queries from the IVR, or responds normally to a live operator.
  • IVR interactive voice response
  • the previously gathered information (both from the IVR query responses and the diagnostic information solicited from the system problem handlers and element managers) is available to the product support engineer.
  • the product support engineer can query the customer's computer via support agents for additional information, if necessary.
  • the customer spends less time interacting with a product support engineer, and is relieved of many of the responsibilities in diagnosing and resolving problems. Automated diagnoses and shorter customer interactions save the product support center time, resources, and money. At the same time, the customer receives a better diagnosis and resolution of the problem than could usually be achieved with prior art product support techniques.
  • one embodiment of the present invention makes the Internet a viable alternative to telephone calls as a tool for providing consumer product support.
  • Many on-line computer services such as Prodigy and America On-Line, provide, for a fee as a part of their on-line service, software for connecting to and accessing the Internet.
  • the Internet access software accesses and "handshakes" with an "Intemet Entry Server", which verifies the PIN number, provides the access and times the user's access time.
  • the Internet Entry Server is programmed to recognize the PIN number as entitling the user to a limited prepaid or "free" Internet access time for on-line help services.
  • Such a time period could be for a total time period such as 1 hour or more, or access to on-line help services can be unlimited for 90 days, 6 months, etc., for example, with the access time paid for by the sponsor/vendor.
  • the first time a customer uses the on-line help service the Internet Entry Server performs a registration process which includes a number of personal questions and custom data gathering in the form of queries provided by the sponsor/vendor for response by the user. The pertinent answers are then immediately provided to the sponsor/vendor.
  • the Internet Entry Server performs a registration process which includes a number of personal questions and custom data gathering in the form of queries provided by the sponsor/vendor for response by the user. The pertinent answers are then immediately provided to the sponsor/vendor.
  • the Internet Entry Server then "hot-links" the customer to the sponsor/vendor's Internet domain or Home Page for a mandatory "guided tour" where the user is exposed to any cu ⁇ ent product promotion by the sponsor/vendor and can download promotional coupons, product information, etc. After this mandatory guided tour is completed, the customer is allowed to enter queries for help in installing or using the sponsor/vendor's product. As an optional promotional service, upon termination of the on-line help session, access to other information on the Internet can be provided. Once the "free" on-line help service time or time period is up, the Internet Entry Server prompts the user with one or more of a plurality of options for extending the availability of online help.
  • the user can be prompted to enter a credit card number to which on-line help charges can be charged; he or she can be given the opportunity to answer additional survey information in return for additional "free" on-line help; or a 900 subscriber paid telephone access number can be provided through which additional on-line help could be billed via the normal telephone company 900 billing cycles.
  • FIG. 19 is a flowchart showing an integrated IP telephony process 1900 in accordance with a prefe ⁇ ed embodiment of the present invention.
  • the IP telephony process 1900 begins with a • transmitting step 1902.
  • step 1902 data is transmitted over the hybrid network during a data session.
  • This data session is typically a normal Internet browsing session, and is generally initiated by a web browser.
  • users begin the data session by performing actions such as searching for web sites or downloading data from Internet sites.
  • the present invention allows users the option to initiate phone calls without the need to use another telephone.
  • a telephony step 1904 the present invention allows users to initiate and continue telephonic communication.
  • the telephonic is routed by a user action in step 1906, when a user selects a phone number to call.
  • Telephone numbers are typically included in a telephone directory accessible on screen by the user.
  • the directory may include icons which provide a highly recognizable visual mnemonic to allow users to easily recall the information included in a particular directory entry.
  • the present invention utilizes the routing information to direct the call. Since both the original data from the data session and the new IP telephony data use Internet protocol, the present invention can provide a seamless integration of the two, to provide virtually simultaneous telephonic and non-telephonic data communication. The availability of packet switching elements in the hybrid network facilitate this process.
  • packets in the form of units of data are transmitted from a source- such as a user terminal, computer, application program within a computer, or other data handling or data communication device— to a destination, which may be simply another data handling or data communication device of the same character.
  • the devices themselves typically are refe ⁇ ed to as users, in the context of the network.
  • Blocks or frames of data are transmitted over a link along a path between nodes of the network.
  • Each block consists of a packet together with control information in the form of a header and a trailer which are added to the packet as it exits the respective node.
  • the header typically contains, in addition to the destination address field, a number of subfields such as operation code, source address, sequence number, and length code.
  • the trailer is typically a technique for generating redundancy checks, such as a cyclic redundancy code for detecting errors.
  • the receiving node strips off the control information, performs the required synchronization and error detection, and reinserts the control information onto the departing packet.
  • Packet switching arose, in part, to fulfill the need for low cost data communications in networks developed to allow access to host computers.
  • Special pu ⁇ ose computers designated as communication processors have been developed to offload the communication handling tasks which were formerly required of the host.
  • the communication processor is adapted to interface with the host and to route packets along the network; consequently, such a processor is often simply called a packet switch.
  • Data concentrators have also been developed to interface with hosts and to route packets along the network. In essence, data concentrators serve to switch a number of lightly used links onto a smaller number of more heavily used links. They are often used in conjunction with, and ahead of, the packet switch.
  • packet-switched data transmission is accomplished via predetermined end-to-end paths through the network, in which user packets associated with a great number of users share link and switch facilities as the packets travel over the network.
  • the packets may require storage at nodes between transmission links of the network until they may be forwarded along the respective outgoing link for the overall path.
  • connectionless transmission another mode of packet-switched data transmission, no initial connection is required for a data path through the network. In this mode, individual datagrams carrying a destination address are routed through the network from source to destination via intermediate nodes, and do not necessarily arrive in the order in which they were transmitted.
  • the telephonic communication over the hybrid network is limited bases on a user profile.
  • the user profile is included in a mles database.
  • the mles database can provide seamless cross-location registration without the need for duplicate databases located on different networks.
  • the computer used to interface with the Internet includes multimedia equipment such as speakers and a microphone. Utilizing a multimedia equipped computer allows a user to use telephonic communication with little or no dismption while interfacing with the Internet. Multimedia computer speakers are used to receive the telephony audio from the network and the microphone is used to transmit the telephony data to the network.
  • the present invention includes data mining capability that provides the capability to analyze network management data looking for patterns and correlations across multiple dimensions.
  • the system also constructs models of the behavior of the data in order to predict future growth or problems and facilitate managing the network in a proactive, yet cost-effective manner.
  • a technique called data mining allows a user to search large databases and to discover hidden patterns in that data.
  • Data mining is thus the efficient discovery of valuable, non-obvious information from a large collection of data and centers on the automated discovery of new facts and underlying relationships in the data.
  • the term "data mining” comes from the idea that the raw material is the business data, and the data mining algorithm is the excavator, shifting through the vast quantities of raw data looking for the valuable nuggets of business information.
  • Accurate forecasting relies heavily upon the ability to analyze large amounts of data. This task is extremely difficult because of the sheer quantity of data involved and the complexity of the analyses that must be performed. The problem is exacerbated by the fact that the data often resides in multiple databases, each database having different internal file stmctures.
  • FIG 20 is a flowchart showing a Data Mining Process 2000 in accordance with a prefe ⁇ ed embodiment of the present invention.
  • the Data Mining Process 2000 begins with an identifying step 2002.
  • the system identifies patterns and correlations in the system data over the hybrid communication system.
  • the system data is analyzed across multiple dimensions to provide better future system behavior prediction.
  • a model building step 2004 the system builds a model of the network behavior based on the patterns and co ⁇ elations identified in step 2002.
  • Data mining is a process that uses specific techniques to find patterns in data, allowing a user to conduct a relatively broad search of large databases for relevant information that may not be explicitly stored in the databases.
  • a user initially specifies a search phrase or strategy and the system then extracts patterns and relations co ⁇ esponding to that strategy from the stored data.
  • Such a search system permits searching across multiple databases.
  • the extracted patterns and relations can be: (1) used by the user, or data analyst, to form a prediction model; (2) used to refine an existing model; and/or (3) organized into a summary of the target database, as in predicting step 2006.
  • a predicting step 2006 the system predicts future behavior of the network based on the model generated in step 2004.
  • data mining There are two existing forms of data mining: top-down; and bottom-up. Both forms are separately available on existing systems. Top-down systems are also refe ⁇ ed to as “pattern validation,” “verification-driven data mining” and “confirmatory analysis.” This is a type of analysis that allows an analyst to express a piece of knowledge, validate or validate that knowledge, and obtain the reasons for the validation or invalidation. The validation step in a top- down analysis requires that data refuting the knowledge as well as data supporting the knowledge be considered.
  • Bottom-up systems are also referred to as "data exploration.” Bottom- up systems discover knowledge, generally in the form of pattems, in data.
  • the network is managed based on the future behavior of the network.
  • Data mining involves the development of tools that analyze large databases to extract useful information from them.
  • customer purchasing patterns may be derived from a large customer transaction database by analyzing its transaction records.
  • Such purchasing habits can provide invaluable marketing information. For example, retailers can create more effective store displays and more effective control inventory than otherwise would be possible if they know consumer purchase patterns.
  • catalog companies can conduct more effective mass mailings if they know that, given that a consumer has purchased a first item, the same consumer can be expected, with some degree of probability, to purchase a particular second item within a defined time period after the first purchase.
  • Classification of the data records to extract useful information is an essential part of data mining. Of importance to the present invention is the construction of a classifier, from records of known classes, for use in classifying other records whose classes are unknown.
  • a classifier is generated from input data, also called a training set, which consist of multiple records. Each record is identified with a class label. The input data is analyzed to develop an accurate description, or model, for each class of the records. Based on the class descriptions, the classifier can then classify future records, refe ⁇ ed to as test data, for which the class labels are unknown.
  • a credit card company which has a large database on its card holders and wants to develop a profile for each customer class that can be used for accepting or rejecting future credit applicants. Assuming that the card holders have been divided into two classes, good and bad customers, based on their credit history. The problem can be solved using classification.
  • a training set consisting of customer data with the assigned classes are provided to a classifier as input.
  • the output from the classifier is a description of each class, i.e., good and bad, which then can be used to process future credit card applicants.
  • Similar applications of classification are also found in other fields such as target marketing, medical diagnosis, treatment effectiveness, and store location search.
  • Another desirable characteristic for a data mining classifier is its short training time, i.e., the ability to construct the class descriptions from the training set quickly.
  • the methods of the invention are based on a decision-tree classifier.
  • Decision trees are highly developed techniques for partitioning data samples into a set of covering decision mles. They are compact and have the additional advantage that they can be converted into simple classification mles. In addition, they can be easily converted into Stmctured Query language (SQL) statements used for accessing databases, and achieve comparable or better classification accuracy than other classification methods.
  • SQL Stmctured Query language
  • Another data mining classifier technique solves the memory constraint problem and simultaneously improve execution time by partitioning the data into subsets that fit in the memory and developing classifiers for the subsets in parallel. The output of the classifiers are then combined using various algorithms to obtain the final classification. This approach reduces running time significantly. Another method classifies data in batches.
  • Service Providers may face very different regulatory pressures, and the approaches each one takes to competitive threats may be quite distinct. However, in general, Service Providers share three characteristics. They are all:
  • the Reference Model shown in Figure 21 illustrates the principal points of contact between service providers 2100, their customers 2102 and suppliers 2104.
  • the processes that drive Network Management are part of the 'management value chain' from the Customer 2102, through the Service Management to Network Management and subsequently to the externally sourced equipment, which supplies the communications service.
  • This chain may also include other participating Service Providers (or Network Operators) 2106 in delivering the end-to-end service.
  • the interfaces to Suppliers 2104 and other Provider/Operators 2106 are external. These are initially 'procurement' interfaces, but post deployment, become very much operational interfaces.
  • the suppliers of these products or services need to ensure that their management systems directly support the Service Provider's 2100 internal business processes to ensure the most efficient service delivery. There are therefore potential benefits to all by agreeing upon an open, core set of processes, and information flows. To the Service Provider 2100 it enlarges the source of potential suppliers; to the Supplier 2104 it creates a larger potential customer base for their products, while still allowing room for competitive innovation.
  • Service Providers e.g. a co ⁇ orate entity which could also be another Service Provider.
  • a SP may or may not operate a network.
  • a SP may or may not be a Customer of another SP or Network Operator.
  • Network Operator an organization that operates a telecommunications infrastructure.
  • Network Operator may also be a SP.
  • Supplier an individual or organization that provide networking products or services (e.g., maintenance or facilities management) to a Service Provider or Network Operator. These products could include telecommunications equipment, computing platforms or management applications software.
  • Service Management is responsible for managing the customers' perspective for each individual service provided, normally against some type of contractual agreement. Thus its pu ⁇ ose is to 'act on behalf of the customer' for interactions with Network Management.
  • Figure 22 is a simplified view of processes used by Service and Network Providers. As shown in Figure 22, a number of operations management processes are shown to be provided covering Customer Care 2200, Service Management 2202 and Network Management 2204.
  • Network Management processes 2204 will now be identified, and each process is mapped onto its component functions.
  • the modeling of the Network Management processes 2204 and functions is based on the following considerations:
  • Network Management processes 2204 and the process flows that link these, have been derived from discussions and interviews with business planning and operational staff in a number of Service Providers and represent a business-oriented (top-down) view of the stmcture of the Network Management Layer.
  • the Function Set Groups are drawn from standards and reflect a stmcture and terminology which may also be familiar to operational and planning staff.
  • Processes describe the flow of activities to solve a particular problem, or part of it.
  • the means of availability and how the data flows is not significant, i.e. whether or not data is handed over or accessed in a central database is not addressed.
  • processes are concerned with the triggers that set them into action.
  • a function is a unit of processing (either initiated by humans or through an automated action) with specific, well-defined inputs and outputs.
  • the data is essential because the function is described as a unit of processing together with its associated data inputs and outputs. Functions tend to be dedicated to a single pu ⁇ ose and highly granular.
  • a process typically makes use of a number of functions, and a given function may be employed by one, or more, processes. Thus, there is in principle a many-to-many mapping between process and function.
  • Figure 23 shows the relationship between Processes 2300, Functions 2302 and Data 2304.
  • a function 2302 can be considered as a mechanistic reaction to specific inputs (and is thus relatively straightforward to automate), whereas a process 2300 is a reaction to one or more triggers with the application of business mles (and can therefore be more complex to automate).
  • Actors are the external parties providing triggers to the business area to be modeled. What is considered to be external will, of course, depend on what is to be modeled. Furthermore, external parties not providing triggers are not called actors.
  • Each actor in a certain role can provide and receive several triggers. Start with the triggers provided by the actors and model the triggers received by the actors after modeling the process flow-through.
  • Processes 2300 are distinguished within a management layer (such as Network Management) because they represent a major area of operational responsibility, and provide a clean separation of concerns between individual processes.
  • TMN management layers process flows occur vertically, from the Network Management Layer up to the Service, or down to Network Element Management Layers, as well as within the Network Management Layer itself. Indeed, the process flows to support the Service Management Layer are one of the primary drivers in this top-down approach to delivering business benefit. Another issue to recognize is that the dynamics of the lifecycle of each of these Layers is likely to be very different and the implications need to be well understood.
  • FIG. 24 shows the high-level stmcture of Network Management processes 2400, the supporting Function Set Groups 2402, and the data areas 2404 on which these depend.
  • the processes are those already identified in the lower layer of Figure 22.
  • Network Provisioning might make use of a number of the Function Set Groups 2402, say Provisioning for the actual choice and set-up of network paths, and Testing to validate that these are usable.
  • Data 2404 concerning Topologies and Network Configurations may then be involved in supporting those functions.
  • Figure 25 shows the positioning of the network management telcomms operations map within TMN.
  • Provisioning process might be used several times in different ways to achieve the necessary Network Management in support of the service concerned.
  • the processes described here should be recognized as potentially layered in the same way that telecommunications networks and services can be layered.
  • the process flow diagrams consist of a process box in which the process tasks or responsibilities are listed, together with a set of input and output information flows to identify significant interactions between the process area concerned and other parts of the operation.
  • the flow a ⁇ ows are labeled with the nature of the interaction, and the process or entity, with which they interact, is shown as a smaller process box at their termination. In the diagrams, only triggers
  • Triggers which interact outside of the Network Management Layer are explicitly indicated. Triggers may be initiated from:
  • Service Management where these NM processes provide support for the Service Management flows (e.g. Service Problem Resolution triggering Network
  • Network Management in response to needs (triggers) concerned specifically with Network Management (e.g. Network Planning detects the need to re-deploy network resources to deal with, say, a local network overload) 3) Externally supplied (but owned, leased or otherwise contracted) equipment or networks (i.e. from the underlying Element/Sub-Network Management)
  • Figure 26 shows a Network Planning &Development process, including input and output triggers. This process is responsible for the definition of mles for network planning, installation and maintenance, application of new technology and supplier strategy, development and acceptance of new network types, description of standard network configurations for operational use.
  • this process is responsible for designing the network capability to meet a specified service need at the desired cost and for ensuring that the network can be properly installed, monitored, controlled and billed.
  • the process is also responsible for ensuring that enough network capacity will be available to meet the forecasted demand. Based on the required network capacity, orders are issued to suppliers or other network operators (ONO's) and site preparation and installation orders are issued to the Network Inventory Management or a third party Network
  • Constmctor (work orders). A design of the logical network configuration is provided to Network Provisioning. Input triggers
  • Output data (i.e. data generated within this process)
  • Figure 27 illustrates the Functional Groups and Data Areas for the Network Planning & Development process.
  • Figure 28 illustrates the Network Provisioning process, including input and output triggers.
  • This process is responsible for the configuration of the network, to ensure that network capacity is ready for provisioning of services. It carries out network provisioning, as required, to fulfill specific service requests, and configuration changes to address network problems. The process must assign and administer identifiers for provisioned resources, and make them available to other processes.
  • routine provisioning of specific instances of a customer service may not normally involve Network Provisioning but may be handled directly by Service Provisioning from a pre-configured set (see later).
  • Output data (i.e. data generated within this process)
  • Figure 29 illustrates Functional Groups and Data Areas for the Network Provisioning process.
  • Figure 30 illustrates the Network Inventory Management process, including input and output triggers. This process is responsible for anything to do with physical equipment and the administration of this equipment. The process is involved in the installation and acceptance of equipment, with the physical configuration of the network, but also with handling of spare parts and the repair process. Software and hardware upgrades are also the responsibility of this process.
  • Output data (i.e. data generated within this process)
  • Figure 31 shows the Functional Groups and Data Areas for the Network Inventory Management process.
  • Figure 32 illustrates the Network Maintenance & Restoration process, including input and output triggers.
  • This process is responsible for maintaining the operational quality of the network, in accordance with the required network performance goals.
  • Network maintenance activities can be preventative (such as scheduled routine maintenance) or co ⁇ ective.
  • Conective maintenance can be in response to faults or to indications that problems may be developing (proactive). This process initiates tests, does analysis to determine the cause and impact of problems, and notifies Service Management of possible effects on quality.
  • the process can issue requests for conective actions.
  • Output data (i.e. data generated within this process)
  • Figure 34 shows the Network Data Management process, including input and output triggers. This process is responsible for the collection of usage data and events primarily for the pu ⁇ ose of network performance and traffic analysis and optimization. This data may also be an input to Billing (Rating and Discounting) processes at the Service Management Layer.
  • the process must provide sufficient and relevant information to verify compliance/non- compliance to Service Level Agreements.
  • the Service Level Agreements are not known at the NML. This process must ensure that the Network Performance goals are tracked, and that notification is provided when they are not met (threshold exceeded, performance degradation). This includes information on capacity, utilization and traffic.
  • changes in traffic conditions may trigger changes to the network (via Network Provisioning) for the pu ⁇ ose of traffic control e.g. call gapping in case of network congestion. Reduced levels of network capacity can result in requests to Network Planning for more resources.
  • Figure 35 illustrates Functional Groups and Data Areas for the Network Data Management process.
  • Figure 36 illustrates the Structuring of the Network Management Layer.
  • the functional blocks shown in Figure 36 have been chosen, on this basis, to distinguish Network Management capabilities associated with Element Managers (at the node level) and Sub-Network Manager(s) (say, for some managed network area or domain). Note that this is only one possible structuring.
  • Procurement by Service Providers of managed network technology is often based on a combination of Element Management and some aspects of Network Management packaged into this type of Sub-Network Management. This allows the managed Sub-Network domain to be accessed as a network area, rather than just a series of individual network nodes.
  • the Sub- Network might be defined:
  • Sub-Network Manager functionality and Element Manager functionality.
  • the balance between these aspects will be determined by the deployment constraints imposed by the procurer administration and the internal design constraints of the technology.
  • the distribution of functionality may vary significantly from one implementation to another. The factors influencing distribution of functionality are illustrated by the following examples:
  • Mapping of network-oriented to node-oriented resource choices may be optimally handled in different ways for each type of technology and for each separate implementation of the same technology. This can lead to different distributions of functionality within each technology domain to support similar capabilities presented at the boundary to higher-level management.
  • This process is the entry point for the Service Management lifecycle.
  • This process takes capacity plans and capacity requests to generate the specific orders for the provision, configuration and constmction of equipment.
  • These ordering interfaces can be automated to improve effectiveness of the processes. Internal works orders are likely to be automated by some local proprietary interfaces such as a work scheduler or project planning tool.
  • This process supports the Service and Network Management lifecycles.
  • This process takes configuration requests from Customer Care and Service Management
  • Provisioning is to provide the data for the logical configuration of the Network Element through the EML, or for a request to the Network Inventory for physical configurations.
  • automation based upon industry agreements is essential, for the latter the automation of the interface may be a local issue.
  • the Network Inventory is n by a separate organization then automation based upon industry agreements will be desirable.
  • This Process is an essential support component of the Customer Care Ordering Process and the Service Management Service Configuration Process.
  • Network Inventory Management Process This process supports a number of Network Level Processes and needs to be automatically updated to track the physical state of the network inventory across an EML interface.
  • the execution of the physical work is carried out by Workforce Management that may need an automated interface which may not be based upon industry agreements.
  • This process is an essential part of the Network Management lifecycle and supports those Service Management and Customer Care lifecycles that require physical changes to the network.
  • the Maintenance and Restoration Process strongly impacts a customer's perception of service quality.
  • the rapid and accurate handling of problem reports and alarms, their subsequent diagnosis, and restoration require the accurate processing of large numbers of events. This process is essential to support the Network Management, Service Management, and Customer Care lifecycles.
  • the Data Management Process has two distinct aspects:
  • the need is to collect, collate and co ⁇ elate large volumes of data and move them efficiently to systems that can carry out rating and billing.
  • the data transfer needs high level of integrity and auditability.
  • This aspect is cmcial as network degradation usually precedes network failure. Detection and raising of problems at this stage can improve customer perception of service quality. It is also essential to the Network Planning and Development processes as it gives early warning of exhaustion of network capacity. This process is essential to support the Network Management, Service Management, and Customer Care lifecycles.
  • TMN Telecommunications Management Network
  • ITU-T the international body responsible for specifying telecommunications standards.
  • a TMN provides management functions for telecommunication networks and services and offers communications between itself and the telecommunication networks, services and other TMNs.
  • a telecommunication network is assumed to consist of both digital and analogue telecommunications equipment and associated support equipment.
  • a telecommunication service in this context consists of a range of capabilities provided to customers.
  • the Network Management Layer is a key integration layer between the Element Management Layer and the Service Management Layer.
  • Figure 37 illustrates a TMN Layered Management Architecture. Its basic function is to bring together information from the Element Management systems 3700 which support it, and then integrate, correlate and in many cases summarize that information, in order to pass on the relevant information to Service Management Systems 3704. That information may generally relate to the characteristics of the network technologies involved, but should describe an end to end view which is consistent across the (multiple) technologies which may support a customer service. In the reverse direction the Network Management Layer 3702 receives information from the Service Management Layer 3704, process it and then pass on relevant commands and data to the appropriate Element Management System(s) 3700.
  • the Network Management Layer 3702 is more than just a mediator between the EML and SML.
  • the Network Management Layer 3702 has its own responsibilities; for example, network provisioning and network fault management.
  • the key issue is that management responsibility will be placed at a level where adequate information is present, instead of shifting all responsibilities to the SML 3704. For example if a non service-affecting network failure occurs, i.e., breakdown of one leg of an SDH ring, the Network Management Layer 3702 may handle the failure without notifying the SML.
  • the knowledge gained from this activity can be applied in determining which activities, at the NML, need to be progressed first to document requirements, detailed information flows and subsequently specifications, that support Service Management. These information flows may be between SML and NML, NML and EML or wholly within the NML.
  • Figure 38 illustrates the Customer Care Lifecycle.
  • the key lifecycle is the Service Management lifecycle, from initial identification and definition of a service, through planning and development, deployment, ongoing operation and finally phasing out that service, as this will drive the other lifecycles. While there can be many combinations in how a particular company will segment and name their particular processes and methods, the overall lifecycle will generally contain many of the same steps.
  • TBN management
  • the customer care processes in the top row of Figure 22 forms a lifecycle driven by the provision of a specific instance of a customer service. Because there are likely to be many customers, many different services, and a fairly dynamic need to add, delete, or change services, this implies the need to support high transaction rates in the Service Providers Customer Care systems (but not necessarily in each individual customers management system), relatively low data volumes per transaction, high transactional integrity, and low levels of manual intervention to save costs.
  • the Service Management processes in the middle row of the overall process model of Figure 22 form a longer periodicity lifecycle driven by the introduction, modification, and withdrawal of different service products (or 'classes' of service).
  • This lifecycle involves creating the specific policies, mles, process, and data templates used to configure and select service products the Customer Care process can utilize.
  • Figure 39 shows a Typical Service Management Lifecycle.
  • Figure 40 shows the Network Management Lifecycle.
  • the Network Management processes form the lower layer of processes in the overall Service Management Telecomms Operations Map and have to respond to and support both the Customer Care process lifecycle and the
  • Network Management systems Integration of Network Management systems into the Providers' environment is one of the main issues the industry needs to address.
  • real-time operational management was limited to the Element Management Layer, i.e. more or less stand-alone alarm and configuration boxes, with much proprietary internal development within the Network Operator to 'glue' important aspects (e.g. alarm monitoring) together.
  • Network Management systems Moving to the NML, Network Management systems have to support the business processes of the network operator. Interoperability problems arise because the network management processes are complex, since all of these lifecycles have to be resolved, integrated, and supported.
  • Interfacing and/or support problems arise in the following areas: • Deficiencies in life cycle support. Network management systems cunently tend to only support the operational phase of network management.
  • Figure 41 shows how the foregoing three lifecycles interact.
  • These sub-processes support the high level processes and represent the way providers describe daily tasks they perform, or would ideally like to perform, in managing integrated networks to support automated management of services, delivered to their customers.
  • Figure 42 shows the five high level network management business processes 4200 and thirteen sub-processes 4202. Note that additional sub-processes may be added as knowledge increases through analysis of this area. This is a slightly different view from that described in cunent standards, but it should be noted that neither view is wholly right or wrong. Both views are necessary if the objective is to be achieved. The difficult task is to map the process view onto the wealth of available standards that can be used, and to deliver the business benefits through tangible products that can be deployed. In doing that, further requirements will be identified that will influence future standards. As a first step, the need to understand the relationship of processes and sub-processes with Function Set Groups and Function Sets is useful. Figure 43 helps to position the processes and sub-processes 4202 in relation to Figure 24.
  • Each process or subprocess may be composed of all or part of the different Function Set Groups or Function Sets, perhaps as a linked workflow, to achieve its objectives.
  • Figure 44 shows how two examples of the linked workflows might be used.
  • Figure 45 illustrates process flow for network provisioning.
  • the numbers in Figure 45 show the sequence of operations starting with a network provisioning request [1] from the Service Configuration process within the Service Management Layer 3704 (see Figure 37) and finishing with the configuration result [13] and start monitoring [14] messages sent to the Service Configuration and Network Data Management processes respectively.
  • Network Data Management Process Example Figure 46 illustrates a Process flow for Network Data Management. This example assumes that a new service has been provisioned and has triggered Network Data Management to start its function. Further, it shows that Network Data Management has discovered an out-of-spec condition and has notified the Service Problem Resolution process.
  • each sub-process has many triggers and data flows, in the previous examples, only those triggers and data flows pertinent to the high level process are shown. A more detailed view of inputs, outputs and responsibilities of three of the sub-processes will now be set forth.
  • Figure 47 shows the Network Performance Monitoring sub-process. (Managing/Servicing individual NLA's with the Service Management Layer) This sub-process is responsible for managing, processing and analyzing network and NE statistical information, to determine and track network performance, providing Network Performance Assessment. It is also responsible for the gathering of network performance data needed by the Service Management Layer to track Service Level Agreements. Mapping of the SLA to the network level has been called a Network Level Agreement (NLA).
  • NLA Network Level Agreement
  • Figure 48 illustrates the Network Test Management sub-process. This sub-process is responsible for verifying the operational usability of individual or connected network components, which may be supporting a service, and determining causes of faults. It manages all aspects of the testing process, determining the appropriate tests which will be mn, depending on path and equipment characteristics, controlling the tests and collating and comparing the results against predetermined limits or norms. It provides traceability and auditability against all actions. Inputs:
  • Figure 49 illustrates the Network Configuration and Routing subprocess.
  • This sub-process installs the initial logical configuration of the network after network constmction. Furthermore, this process designs and installs network re-configurations in the operational network. In the design process, business mles for the utilization of the network are applied. In the design, the reconfiguration requests from different sources (high level processes an sub-processes) are coordinated. This sub-process is also responsible for the alignment of the configuration as stored in the network management and administrative systems with the real network configuration.
  • a hybrid network in accordance with the discussion above may be implemented in the manner shown in Figure 50.
  • Orders for network capacity are issued in operation 5000 based on a forecasted demand in order to develop a hybrid network.
  • Note Figure 26 the hybrid network is analyzed to identify network problems.
  • the hybrid network is provisioned, as set forth in Figure 28, in accordance with the network problems and service requests. Usage of the hybrid network is determined and network usage control functions are initiated based on the determined usage in operation 5006.
  • Note Figure 34 Note Figure 34.
  • provisioned portions of the hybrid network are assigned identifiers.
  • Hardware of the hybrid network may be managed by performing duties selected from the group of duties consisting of installing the hardware of the hybrid network, performing work on the hardware of the hybrid network, and repairing the hardware of the hybrid network. Further, historic data of the network problems may be maintained, such as in a log. A notification of the usage of the hybrid network may be provided if the usage is above a predetermined amount.
  • sub-processes are used.
  • Such sub-processes include network capacity/trunk planning, software and data building management, scheduling management, logistics management, workforce management, security management, problem analysis and resolution, network performance monitoring and analysis, network traffic monitoring and analysis, network configuration and routing, network test management, network alarm and event conelation, and network usage data collection and consolidation.
  • a prototype of the NGN Network can be created as a selling tool for services of the network.
  • the prototype network may include only a portion of the features of the network described above, the prototype should be a feature rich service delivery platform that can launch applications which are usable in communications and non-communications industry hence stressing the cross industry applicability of this solution.
  • this platform shows them how to effectively use communication services to their advantage.
  • the simulator shows what technology capabilities are needed in the network, what communications business capabilities this can enable, and what new services communications companies may want to provide to their clients.
  • the objective of the prototype is two-fold:
  • the prototype is a tool to show businesses how they can exploit the new network, and to show communications providers why they need to offer these new networking and systems services, and how they can provide them.
  • the assets developed may include business scenarios, white papers, technology assessments, and value propositions for communications clients as well as other industries' clients.
  • the assets developed for the prototype may include methodology, solution constmction kits, workplans, budgets, and a number of skilled resources ready for jump-starting client engagements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Cette invention a trait à un système, à une méthode ainsi qu'à un article fabriqué aux fins d'un réseau grande vitesse. L'un des composants est un réseau client auquel ont accès plusieurs clients. Un réseau bordurier, qui interface avec le réseau client, fournit des services aux clients. Un réseau central, qui interface avec le réseau bordurier, exécute plusieurs tâches dont la consolidation de courants de trafic faible vitesse émanant du réseau bordurier en circuits grande vitesse, la simplification des topologies des réseaux et la constitution de largeurs de bande efficaces dans le réseau grande vitesse.
EP00959799A 1999-08-31 2000-08-31 Systeme, methode et article fabrique pour reseau de communication grande vitesse a plusieurs niveaux et a efficacite accrue Withdrawn EP1214859A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US38661799A 1999-08-31 1999-08-31
PCT/US2000/024155 WO2001017313A1 (fr) 1999-08-31 2000-08-31 Systeme, methode et article fabrique pour reseau de communication grande vitesse a plusieurs niveaux et a efficacite accrue
US386617 2003-03-12

Publications (1)

Publication Number Publication Date
EP1214859A1 true EP1214859A1 (fr) 2002-06-19

Family

ID=23526346

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00959799A Withdrawn EP1214859A1 (fr) 1999-08-31 2000-08-31 Systeme, methode et article fabrique pour reseau de communication grande vitesse a plusieurs niveaux et a efficacite accrue

Country Status (3)

Country Link
EP (1) EP1214859A1 (fr)
AU (1) AU7106000A (fr)
WO (1) WO2001017313A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9363204B2 (en) 2013-04-22 2016-06-07 Nant Holdings Ip, Llc Harmonized control planes, systems and methods
US9384028B1 (en) 2013-12-19 2016-07-05 Amdocs Software Systems Limited System, method, and computer program for preserving service continuity in a network function virtualization (NFV) based communication network
US9760428B1 (en) 2013-12-19 2017-09-12 Amdocs Software Systems Limited System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network
US9430262B1 (en) 2013-12-19 2016-08-30 Amdocs Software Systems Limited System, method, and computer program for managing hierarchy and optimization in a network function virtualization (NFV) based communication network
US9460286B1 (en) 2013-12-19 2016-10-04 Amdocs Software Systems Limited System, method, and computer program for managing security in a network function virtualization (NFV) based communication network
US10606718B1 (en) 2013-12-19 2020-03-31 Amdocs Development Limited System, method, and computer program for managing fault recovery in network function virtualization (Nfv) based networks
US9806979B1 (en) 2013-12-19 2017-10-31 Amdocs Software Systems Limited System, method, and computer program for optimizing a chain of virtual network functions in a network based on network function virtualization (NFV)
KR102168047B1 (ko) 2016-09-26 2020-10-20 난트 홀딩스 아이피, 엘엘씨 클라우드 네트워크들에서의 가상 회로들
US20230084573A1 (en) * 2021-09-02 2023-03-16 At&T Intellectual Property I, L.P. Reliability reference model for topology configuration

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5274643A (en) * 1992-12-11 1993-12-28 Stratacom, Inc. Method for optimizing a network having virtual circuit routing over virtual paths
DE69736340T2 (de) * 1996-03-19 2007-07-12 Lucent Technologies Inc. Verfahren und Vorrichtung in einem integrierten Telekommunikationsnetzwerk zur Umsetzung von synchronen Schmallband-Signalen in nach dem asynchronen Übertragungsmodus arbeitende Signale

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0117313A1 *

Also Published As

Publication number Publication date
WO2001017313A1 (fr) 2001-03-08
AU7106000A (en) 2001-03-26

Similar Documents

Publication Publication Date Title
US6345239B1 (en) Remote demonstration of business capabilities in an e-commerce environment
US6427132B1 (en) System, method and article of manufacture for demonstrating E-commerce capabilities via a simulation on a network
US6611867B1 (en) System, method and article of manufacture for implementing a hybrid network
WO2001017169A9 (fr) Systeme, procede et article pour systeme de gestion previsionnelle des anomalies sur reseau
US6704303B1 (en) IP/telephony user interface for a hybrid communication system
US6449588B1 (en) Customer-driven QOS in hybrid communication system
US6542593B1 (en) Rules database server in a hybrid communication system architecture
US6195697B1 (en) System, method and article of manufacture for providing a customer interface in a hybrid network
US6442547B1 (en) System, method and article of manufacture for information service management in a hybrid communication system
US6556659B1 (en) Service level management in a hybrid network architecture
US6081518A (en) System, method and article of manufacture for cross-location registration in a communication system architecture
US6707812B1 (en) System, method and article of manufacture for element management in a hybrid communication system
US6426948B1 (en) Video conferencing fault management in a hybrid network
US6147975A (en) System, method and article of manufacture of a proactive threhold manager in a hybrid communication system architecture
US7350138B1 (en) System, method and article of manufacture for a knowledge management tool proposal wizard
US8938435B2 (en) Knowledge management tool
US6564209B1 (en) Knowledge management tool for providing abstracts of information
US6900807B1 (en) System for generating charts in a knowledge management tool
US6727927B1 (en) System, method and article of manufacture for a user interface for a knowledge management tool
EP1214859A1 (fr) Systeme, methode et article fabrique pour reseau de communication grande vitesse a plusieurs niveaux et a efficacite accrue
AU2001240010B2 (en) Method of manufacture for a knowledge management tool
AU2001240010A1 (en) Method of manufacture for a knowledge management tool
WO2000074337A2 (fr) Systeme, procede et article manufacture destines a un serveur de base de donnees de regles dans une architecture de systeme de communication hybride
WO2000074336A2 (fr) Systeme, procede et article de fabrication destines a une facturation dynamique au moyen d'une qualite de service dans une architecture de communication hybride
WO2000074324A1 (fr) Systeme, procede et article de fabrication pour la gestion de donnees de reseau dans une architecture de reseau hybride

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020402

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20020813

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20060404