|Publication number||US5930334 A|
|Application number||US 08/828,936|
|Publication date||Jul 27, 1999|
|Filing date||Mar 28, 1997|
|Priority date||Mar 28, 1997|
|Also published as||CA2284697A1, EP0972395A1, WO1998044704A1|
|Publication number||08828936, 828936, US 5930334 A, US 5930334A, US-A-5930334, US5930334 A, US5930334A|
|Inventors||Richard Lundberg, Håkan Omnell, Tomas Kostenius, Gunnar Hallgren|
|Original Assignee||Telefonaktiebolaget Lm Ericsson|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (14), Non-Patent Citations (2), Referenced by (6), Classifications (16), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates to monitoring the operation of telecommunications equipment, and more particularly, to monitoring the average amount of time a subscriber is out of service as the result of some fault or failure in the telecommunications equipment.
It is important to be able to measure and evaluate the performance of a telecommunications system both generally from the overall system perspective and in more detail from the perspective of specific telecommunications equipment. The present invention is particularly directed to the issue of determining how often a telecommunications path, used by a subscriber to request and receive a telecommunications service from a telecommunications system, is "down" as a result of some type of fault or failure in the subscriber path or in the communications system itself. One example of a subscriber path is a wireline which connects a subscriber device such as a telephone to a local telephone exchange. Since a subscriber wireline is perhaps the simplest and most common example of a subscriber path, it is used in the subsequent description for purposes of illustration but not limitation.
One way to address this issue might be to manually sample the status of the subscriber lines, collect and correlate the manually obtained data, and then calculate various statistical parameters based on those collected figures. But a manual approach is tedious, time consuming, expensive, and not altogether effective because of these limitations. Another approach might be simply to measure the amount of time that a telecommunications center such as a local exchange, is down or "out-of-order" and use that as a general measure of how often subscriber lines are down. However, this latter approach is too general and does not account for fault or other blocking events that effect the operational status of the subscriber lines independent of the telecommunications center operation/operability.
It is therefore an object of the present invention to provide a technique that automatically monitors the operational status of individual subscriber lines to determine how often a subscriber line on average and/or individually is blocked or down so that it cannot be used by a subscriber device to receive or request communication services.
It is a further object of the present invention to provide a subscriber line down time monitoring and calculation technique that accounts for causes in subscriber line down time attributable to multiple sources including subscriber line hardware, software specifically controlling the subscriber line hardware, and other external sources including any widespread system down time of the telecommunications center to which the subscriber line is connected.
It is a further object of the present invention to provide such measurement and calculation parameters simply, inexpensively, and with little data processing overhead using existing resources in conventional telecommunications systems.
The method of the present invention monitors the operation of communications equipment including plural subscriber communications paths used by corresponding subscriber devices to receive information from or transmit information to a telecommunications center such as a local telephone exchange. One or more data records is maintained in computer memory for each subscriber path connected to the communications center. Each data record is updated using recently determined data relating to the operational status of each subscriber path. A computer then determines from the updated records a subscriber path blocking parameter. A blocked subscriber path means that the subscriber path cannot be used as intended as a communications path.
The subscriber path blocking parameter may represent the amount of time that a subscriber path is blocked, such as an average amount of time each subscriber path is blocked, or an amount of time that an individual one of the subscriber paths is blocked. The average amount of blocked time per subscriber line for a particular time period is sometimes referred to as line down time (LDT) if the blocking fulfills certain "line down" criteria. It should be understood, however, that the "line down" time calculation also applies to more sophisticated subscriber paths that might also include for example a time division multiplexed time slot. Even if a subscriber path is blocked, it may not be treated as "down" or "operational" unless it satisfies one or more predetermined "line down" criteria. One example criterion is an amount of time that a subscriber path must be blocked (faulty) or unblocked (in operation), e.g., 30 seconds, before that subscriber path will be treated as "down" or "operational," respectively.
Another advantageous feature of the present invention is that the communications center itself, such as the local telephone exchange, is monitored to determine the amount of time (if any) that it is not providing service to the subscriber devices. The system's operational status is monitored in addition to the operational status of the subscriber paths which connect the subscriber devices to the communications system. The amount of time that the subscriber paths are detected as "down" for any reason is calculated based both on the detected operational status of each individual subscriber path and on the determined amount of time that the communications system is not operational.
In a particular embodiment of the present invention that includes a telecommunications center including a switching node, telecommunications subscriber devices, and subscriber lines used by corresponding ones of the subscriber devices to obtain a communications service from the telecommunications center, electronic circuitry detects and reports faults related to each subscriber line. Reported faults are used to determine if the subscriber line should be blocked. The subscriber line blocking state (operational status) is used to determine if the subscriber line is "down" or "operational" according to the line down criteria. A data processor evaluates whether any subscriber line has recently been blocked and whether any subscriber line has recently become unblocked. Subscriber line records stored in memory are updated based on the detected operational status for each subscriber line.
A line interface circuit is connected between a corresponding subscriber line and the telecommunications center. Each line interface circuit includes circuitry that monitors faults of the corresponding subscriber line which could affect whether the corresponding line is blocked. Such line interface circuits may be located at the telecommunications center or at an intervening access node.
In a preferred example embodiment, a plurality of counters may be used in performing line down time calculations. A first counter counts a number of subscriber lines currently detected as down based on the detected operational (blocking) status of the subscriber lines. A second counter accumulates an accumulated number of lines down using periodically obtained values from the first counter. The data processor calculates an average amount of time each subscriber line is down using a value obtained from the second counter and a total number of fully-connected subscriber lines. A fully-connected subscriber line is a line which has been assigned to provide service to a particular subscriber device and has been connected and/or activated so that it is capable of providing that service. The fact that a subscriber line is fully-connected or otherwise activated does not mean that it is necessarily operational or non-operational. A third counter counts a number of currently fully-connected subscriber lines. A fourth counter maintains an accumulated number of fully-connected subscriber lines using periodically obtained values from the third counter.
By using software variables and counters, the preferred example embodiment of the present invention provides a comprehensive and detailed measurement of subscriber line down time useful in evaluating performance. The features and advantages of the present invention will be described in further detail below in conjunction with the drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a function block diagram showing one example application of the present invention using one or more PSTN line connections to a local exchange;
FIG. 2 is a function block diagram showing another example application of the present invention using one or more PSTN connections to a local exchange via a PCM (Pulse Code Modulation) connected Access Node (AN);
FIG. 3 is a flowchart diagram illustrating a method in accordance with the present invention;
FIG. 4 is a function block diagram showing hardware and software data structures used in implementing the preferred example embodiment of the present invention; and
FIGS. 5-7 are flowchart diagrams that illustrate procedures employed in implementing the preferred example embodiment of the present invention.
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular circuit components, interfaces, techniques, etc. in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well known methods, devices, and circuits are omitted so as not to obscure the description of the present invention with unnecessary detail.
FIG. 1 illustrates one example application of the present invention. More specifically, a local telephone exchange 10 is shown connected to two subscriber devices 12 and 14 over corresponding subscriber path 18. One example subscriber device is a telephone 12 connected directly by a subscriber wireline to a corresponding line interface circuit (LIC) 20 shown in this example in local telephone exchange 10. Another example type of subscriber device is personal computer 14 connected via modem 16 over subscriber line 18 to corresponding line interface circuit 20 in the local telephone exchange 10. Of course, other types of subscriber wirelines could be used including for example an integrated services digital network (ISDN). While the detailed description is couched in terms of dedicated subscriber wirelines, the present invention is equally applicable to other subscriber paths including shared wirelines, time division multiplexed timeslots, wireless communications channels, etc.
Substantive information from the subscriber devices 12 and 14 such as voice information is communicated via exchange lines 24. Each line interface circuit (LIC) 20 detects faults and reports detected faults to one or more regional processors 28 via connections 25. Each LIC 20 may optionally include a device processor. Regional processors 28 operate in accordance with regional software 32 stored in regional processor memory. Faults reported from the LIC 20 or from software test programs are used by the regional and/or central software 32 and 34 to determine if the subscriber line should be blocked. The blocking state (operational status) is used to determine if the subscriber line is "down" or "operational" according to the line down criteria. In addition, regional processors 28 communicate with one or more central processors 30 operating in accordance with central software 34 stored in central processor memory. In addition to monitoring and controlling information from the respective line interface circuits 20, the processors 28 and 30 also operate and control conventional switching equipment 26 which is typically connected by telephone trunks to other telephone exchanges. While regional and central processors have been shown, those skilled in the art will appreciate that other data processing architectures including a single data processor architecture may also be employed.
Each line interface circuit 20 connected to a corresponding subscriber device performs a number of functions such as conversion of any analog signal on the subscriber line into digital form for further processing in switching equipment which in the preferred embodiment is a digital switch such as the AXE-10 manufactured and sold by Ericsson. The line interface circuit 20 also performs a number of other functions including feeding current to the subscriber line, receiving dialed digits in both pulse and tone formats from the subscriber device, sending ring and tone signals to the subscriber device, and carrying out various measurements on the subscriber line and LIC hardware. In particular, hardware/software self-test and self-checking functions are performed. Information including detected faults in the subscriber line and associated subscriber line hardware and software is reported from the line interface circuits (LIC) 20 via regional processor(s) 28 to central processor(s) 30. Faults may also be reported from test programs located in the central processor software 34. The regional and central processor software programs use the fault information to block or unblock subscriber lines. Knowing the operational status of each subscriber line, the processors also know if the subscriber device is prevented from communication with the local exchange 10.
Another example application to which the present invention may be applied is illustrated in FIG. 2 where like reference numerals refer to like elements from FIG. 1. An access node 40 is positioned between the subscriber devices 12 and 14 and the local exchange 10. The subscriber wirelines 18 are connected to corresponding line interface circuits 20 in the access node 40. The substantive information (e.g., voice) from the line access node's interface circuits 20 and control-related information from the access node (AN) are multiplexed onto time division multiplex lines 44 by a multiplexer/demultiplexer (MUX/DEMUX) 42 connected to a corresponding interface 46 in switching equipment 26. The blocking information obtained from the access node (AN) is processed by regional and central processing hardware and software 48 as described further below.
In this example application, the subscriber line includes not only the wireline 18 and corresponding line interface circuit 20 but also the multiplexer/demultiplexer (MUX/DEMUX) 42 and an assigned TDM timeslot(s) on TDM line 44. Thus, depending upon whether individual time slots are assigned to subscriber lines in a static or dynamic fashion, the actual subscriber path corresponding to a subscriber line may vary.
FIG. 3 illustrates a general method in accordance with the present invention executed by one or more data processors already present in the local telephone exchange 10. Subscriber lines are continuously (or periodically) monitored to detect the blocking/unblocking states for each subscriber line. A subscriber line may be blocked for a variety of reasons including a defective subscriber wire, a faulty connection of subscriber wire to either the subscriber device or the line interface, an excessive voltage on the subscriber line 18, a fault in the line interface circuit hardware (e.g., a blown fuse), a fault or other failure in line 24 connecting line interface circuit 20 to switching equipment 26, etc. Other types of software-related blockings are also detected by the telecommunications switch software. Self-test programs may detect faults in hardware and software, and faults may also be detected by the software operating system itself.
The detected and reported fault information of monitored subscriber lines (block 50) is used to update the subscriber line blocking status (operational status) information. For example, blocking status is monitored using individual subscriber line database records (block 52). A determination is made which of the subscriber lines having recently become blocked or unblocked satisfy prescribed line blocking and unblocking parameter(s) including in the preferred embodiment the "line down" criteria (block 54). An example of such a line blocking parameter is the requirement that a line be blocked or unblocked for at least 30 seconds before its operational status ("down" or "operational") is changed.
In block 56, the amount of time that the system (in this example the local telephone exchange 10) is down is determined. The average subscriber line down time, i.e., the time during which the line is blocked and cannot be used for its intended purpose, is then calculated using the system down time and blocking status parameters previously determined (block 58). The average line down time produces an average line down time value attributable to each one of the subscriber lines connected to the telephone exchange as a general performance parameter to evaluate efficiency, reliability, effectiveness, etc. In addition or alternatively, other line blocking parameters may be calculated using the collected subscriber line information including, for example, the amount of time a specific subscriber line (as opposed to an "average" subscriber line) has been blocked.
FIG. 4 is a function block diagram of a particular data processing configuration for implementing a preferred example embodiment of the present invention. Specifically, one (or more) central processor(s) 74 is shown connected to a database 70, a system down timer 78, a memory 76 for storing data and program information, a user interface 80 including for example a display, keyboard, printer, etc., and a plurality of counters 82-96. While much of the information obtained by the central processor 74 for calculating line down time is obtained at an application software level, the system down time monitored to in block 56 in FIG. 3 is obtained from the operating system software underlying application software.
Database 70 includes a plurality of subscriber line data records 72. Each record preferably corresponds to one subscriber line. Each subscriber line record 72 includes a line identification field, a subscriber telephone number field, a status of line field, a status time supervision field, an external blocking field, and possibly additional other fields. The central processor 74 creates these database records initially when a new subscriber line is fully-connected or otherwise activated and updates them when a fault or no-fault event is detected on a subscriber line. A subscriber line may be fully-connected or otherwise activated, in the sense that the hardware connections have been made and the central processor has software-activated the line for operation, but nevertheless be blocked operationally as a result of software commands or hardware faults associated with the subscriber line. In an ideal system, all fully-connected/activated lines permit communications between the subscriber devices and the local exchange, and no subscriber lines are down or blocked.
A subscriber line is deemed "fully-connected" when the subscriber line is connected to the subscriber device and the central processor has activated the line by, for example, assigning the subscriber line ID to a subscriber device telephone number or by other software command.
The status of line field stores whether the fully-connected subscriber line is currently blocked or unblocked controlled by subscriber line controlling software. The status time supervision field is in effect a dedicated timer which tracks the amount of time that particular subscriber line has recently been detected as having a blocked or unblocked which fulfills the "line down" criteria. In a preferred example embodiment of the present invention, a software timer is used to detect when a subscriber line has been in a changed blocking/unblocking status for 30 seconds or more.
The external blocking field is an example of other possible fields that may be provided. The external blocking field specifies the cause or source underlying the fault that has caused blocking of a specific subscriber line. In this example, external blocking field permits the central processor 74 to monitor the number of subscriber lines which are blocked for solely reasons which are external or independent of the telephone exchange, e.g., the wire 18 is broken (cut off).
In the example embodiment, the central processor 74 employs counters 82-96 to keep track of the current number of blocked subscriber lines, fully-connected subscriber lines, as well as accumulation total count values. In particular, counter 82 counts the number of lines currently detected as blocked fulfilling the "line down" criteria and having been "down" longer than minimum valid down time, e.g., 30 seconds. Counter 82 is incremented by the central processor 74 when a fully-connected subscriber line is detected as "down" for more than the prescribed blocking time, e.g., 30 seconds. Conversely, the central processor 74 decrements counter 82 each time a fully-connected blocked line is detected as unblocked for more the prescribed time period. Counter 84 keeps track of the number of lines currently externally blocked and fulfilling the "line down" criteria, and therefore monitors a subset of the total number of currently blocked lines maintained in counter 82. The count value in counter 84 is based not only on the status of line and status time fields of the individual subscriber line records but also upon the external blocking field. Counter 86 counts the number of fully-connected subscriber lines.
An accumulation counter 88 is updated on a regular basis, e.g., every 30 seconds, with the current value in counter 82. Similarly, accumulation counter 90 keeps an accumulated count of externally blocked lines based on regular scannings of counter 84. Accumulation counter 92 keeps an accumulated count of fully-connected lines based on regular scannings of counter 86.
The central processor 74 determines line down time (LDT) and other subscriber line performance parameters by scanning the counter values at the end of a performance measurement in accordance with the following equation: ##EQU1## The line down time caused by any system down time (SDT), e.g., time during which the local exchange is not operational, is calculated using values from 94 and 96 in accordance with the following equation: ##EQU2## In both equation (1) and (2), k is a constant associated with a measurement time period. The total line down time value then is simply calculated in accordance with the following equation:
LDT(total)=LDT(line down)+LDT(SDT) (3)
In addition, the line down time due to blockings of a specific type such as externally blocked timings, may also be calculated using values from 90 and 92 in accordance with the following: ##EQU3##
The following is a simplified example that illustrates this LDT calculation:
______________________________________ No. of Accumulated No. of Fully- AccumulatedScanning Lines No. Connected No. of Fully-Period Down of Lines Down Lines Connected Lines______________________________________1 10 10 10000 100002 10 20 10000 200003 10 30 10000 300004 10 40 10000 400005 10 50 10000 500006 20 70 10000 600007 20 90 10000 700008 20 110 10000 800009 20 130 10000 9000010 20 150 10000 100000______________________________________ ##STR1##
In the above example, there are ten scanning periods. The measurement period constant k corresponds in this example to 525,600 minutes which is the number of minutes in a single year. In scanning periods 1-5, the number of lines down is constant at 10, and therefore, 10 lines are added to the accumulated number of lines down in column 2. Similarly, column 3 shows that the number of fully-connected lines in all scanning periods 1-10 is constant at 10,000 so that the accumulated number of fully-connected lines increments each scanning period by 10,000. However, in scanning period 6, the number of lines down increases from 10 to 20 so that the accumulated number of lines down at the end of each scanning period 6-10 increases by 20 rather than 10.
To calculate the line down time for this example, the accumulated number of lines down at the end of scanning period 10, (i.e., 150), is divided by the accumulated number of fully-connected lines at the end of the tenth scanning period, (i.e., 100,000). Multiplying that quotient by the measurement time constant of 525,600 minutes results in an average LDT of 788 minutes during which the average subscriber line was down for one year.
A method for implementing the preferred example embodiment is described in conjunction with the flowcharts shown in FIGS. 5-7. In block 100, any subscriber lines recently reported faulty and therefore blocked as a result of a software command, processor fault, hardware fault, line fault, external voltage, etc. is detected, and preferably, the cause of that blocking is detected as well. Similarly, in block 102, any subscriber lines recently reported free from faults and therefore unblocked are also detected. Subscriber line data records are updated with the most recent status of blocking information in accordance to the last reported fault status change "fault"/"no fault" (block 104).
For subscriber lines whose operational status (down/operational) has changed, a status timer corresponding to that subscriber line is initiated. Moreover, if the cause of the subscriber line blocking was detected as an external cause, a flag in the externally blocked field of the subscriber line data record is set (block 104). The status timers are monitored, and if the detected subscriber line status persists for 30 seconds, the number of subscriber lines currently blocked, and fulfilling the "line down" criteria, stored in counter 82 is incremented for lines which have just become blocked or decremented for lines which have just become unblocked (block 106).
Any new, fully-connected or activated lines, as indicated for example by a software connection command, are detected and used to update the value of the fully-connected lines counter 86 (block 108). From the system down timer 78, the amount of any system down time which corresponds to any amount of time that the local telephone exchange is down, (e.g., not performing services to subscribers), is measured and added to the accumulation counter 94 after each system down event (block 110). The system downtimer 78 is located externally from the central processor and measures the time duration of any outage of the central processor. System downtime may be either reported to or fetched by the central processor at a successful start, restart, or reload of the central processor.
The values of counters 82, 84, and 86 are periodically scanned and added to corresponding accumulation counters 88, 90, and 92 (block 112). Using the accumulation counter values, average line down time and other related parameters are calculated (block 114). This process continues as long as performance of the system is to be monitored.
FIG. 6 shows a flowchart diagram outlining procedures for calculating the average line down time (LDT). The blocked lines accumulation counter 88 value is divided by the fully connected lines accumulation counter 92 value and multiplied by constant k, e.g., 525,600, to generate the parameter LDT (blockings) value as indicated above in conjunction with equation (1) (block 120). The externally blocked lines accumulation counter 90 value is divided by the fully-connected lines accumulation counter value and then multiplied by a constant k to generate the LDT (external blocking) value noted above in accordance with equation (4) (block 122). The accumulated system down time 94 is divided by the corresponding measurement time period 96 and multiplied by the constant to generate to LDT(SDT) as indicated above in equation (2) (block 124). The total average line down time is then calculated in accordance with equation (3), i.e., LDT (total)=LDT (line down)+LDT(SDT), (block 126).
FIG. 7 illustrates in flowchart format procedures for calculating individual line down time. The status of an individual subscriber line is monitored (block 130), and any reported status changes ("fault"/"no fault") that leads to blocked or unblocked changes and fulfillment of the "line down" criteria for that individual subscriber line are detected (block 132). A flag is activated whenever the line is down, and deactivated whenever the subscriber line is operational again (block 134). The flag is regularly scanned and the time for which the individual subscriber line is down is accumulated (block 135). At the end of a desired measurement, the accumulated value counter value may be stored and/or displayed as desired (block 136).
There are several commercial advantages of this invention. Both the operators and developers need an automatic and accurate way of measuring the "in service performance" of the exchange or other communication center. Operators are also able to compare exchanges from different suppliers based on this in service performance. The average line down time is also useful to developers in evaluating the quality of their own telecommunications products.
The foregoing detailed description shows and describes only certain particular embodiments of the present invention. However, those skilled in the art will recognize that many modifications and variations may be made without departing substantially from the spirit and scope of the present invention. Accordingly, it should be clearly understood that the form of the invention herein is exemplary only and is not intended to limit the scope of the invention as defined in the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4197427 *||Nov 11, 1977||Apr 8, 1980||Lynch Communication Systems, Inc.||Dual-processor line concentrator switching system|
|US4306295 *||Sep 14, 1979||Dec 15, 1981||Telefonaktiebolaget L M Ericsson||Arrangement for measuring the ratio between a number of events occurring after each other in a first and a second series of events|
|US4330688 *||Jan 24, 1980||May 18, 1982||Cselt - Centro Studi E Laboratori Telecomunicazioni S.P.A.||System for statistical supervision of trunk-dialed long-distance telephone calls|
|US4464543 *||Dec 1, 1982||Aug 7, 1984||Gte Business Communication Systems Inc.||Network control center call trace|
|US5042027 *||Sep 8, 1989||Aug 20, 1991||Hitachi, Ltd.||Communication network system and method of controlling a communication network|
|US5425087 *||Aug 8, 1994||Jun 13, 1995||At&T Corp.||Telephone usage monitoring arrangement|
|US5471526 *||Feb 28, 1994||Nov 28, 1995||Telefonaktiebolaget L M Ericsson (Publ.)||Tracing with keys and locks on a telecommunication network|
|US5479473 *||Jun 25, 1993||Dec 26, 1995||Mci Communications Corporation||Method and apparatus for testing call paths over long distance carrier networks|
|US5488655 *||Jul 6, 1994||Jan 30, 1996||U S West Technologies, Inc.||Method and system for controlling traffic in PSTN links through the use of variable price incentives|
|US5553127 *||Apr 11, 1995||Sep 3, 1996||Telefonaktiebolaget L M Ericsson||System and method for processing and analyzing telephone calls in a telephone exchange|
|US5583928 *||Aug 17, 1993||Dec 10, 1996||British Telecommunications Public Limited Company||Detecting local exchange failure and resultant control of a communications network|
|US5699402 *||Sep 26, 1994||Dec 16, 1997||Teradyne, Inc.||Method and apparatus for fault segmentation in a telephone network|
|DE2743235A1 *||Sep 26, 1977||Apr 5, 1979||Siemens Ag||Quality meter for frequency of telephone exchange faults - with quotient of events occurring put into counter used for correction of permissible number of faults|
|FR2348612A1 *||Title not available|
|1||*||GR 512 CORE, Issue 1, Jan. 1995, SSGR: Reliability, Section 12, Outage Reporting and Analysis, pp. 7 1 through 9 6.|
|2||GR-512-CORE, Issue 1, Jan. 1995, SSGR: Reliability, Section 12, Outage Reporting and Analysis, pp. 7-1 through 9-6.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6487173 *||Mar 16, 1998||Nov 26, 2002||Fujitsu Limited||Network system and communication device|
|US6643262 *||Aug 29, 1997||Nov 4, 2003||Telefonaktiebolaget Lm Ericsson (Publ)||System and method for dynamic sharing of connection resources|
|US7508752 *||May 30, 2003||Mar 24, 2009||Cisco Technology, Inc.||Hardware facility switching in cross-connect systems|
|US8699681 *||Dec 26, 2009||Apr 15, 2014||At&T Intellectual Property Ii, L.P.||Method and apparatus for monitoring blocked calls in a communication network|
|US20080175588 *||Apr 6, 2007||Jul 24, 2008||Tellabs Vienna, Inc.||Method and apparatus for analyzing a network or a network element fault|
|US20100104079 *||Dec 26, 2009||Apr 29, 2010||Marian Croak||Method and apparatus for monitoring blocked calls in a communication network|
|U.S. Classification||379/27.06, 379/12, 379/22.03, 370/251, 379/8, 379/16, 370/248|
|International Classification||H04M3/36, H04M3/30, H04M3/22|
|Cooperative Classification||H04M3/30, H04M3/36, H04M3/22|
|European Classification||H04M3/36, H04M3/30, H04M3/22|
|Mar 28, 1997||AS||Assignment|
Owner name: TELEFONAKTIEBOLAGET LM ERICSSON, SWEDEN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LUNDBERG, RICHARD;KOSTENIUS, TOMAS;HALLGREN, GUNNAR;AND OTHERS;REEL/FRAME:008487/0751;SIGNING DATES FROM 19970321 TO 19970324
|Jan 24, 2003||FPAY||Fee payment|
Year of fee payment: 4
|Jan 29, 2007||FPAY||Fee payment|
Year of fee payment: 8
|Jan 27, 2011||FPAY||Fee payment|
Year of fee payment: 12