Network management system and method of management control in a communication system

Abstract

A telecommunications network system (10), formed of multiple interconnected nodes (16-22, 26-34, 50-58), is shown in FIG. 1. At least some of the nodes are provided with application spaces (DPASs, 70-94) into which specific programs can be downloaded and run. The application space (DPASs, 70-94), realized by control logic and memory, takes control of managing specific programs and reporting results arising from execution of the specific programs. The application spaces support specific functionality dependent upon the functionality of the node, and support real-time downloading and running of code. Resultant data acquired from running the specific programs is correlated between nodes to produce highly pertinent management data that is communicated to a management device, such as an OMC (48), for analysis and fault identification/performance optimization. Execution of code at specific nodes, followed by shuffling of the code to interconnected nodes, allows operational assessment of successive nodes and interconnecting paths, with correlation of results limiting management data communicated to the management device. Another embodiment provides for the shuffling of test code between nodes, with any inability either to execute code or to generate a predetermined response considered to be indicative of a fault at either that node or at a connection path coupled thereto.

Description

BACKGROUND TO THE INVENTION

[0001] This invention relates, in general, to a telecommunication network management system and is particularly, but not exclusively, applicable to cellular-type systems supporting a distributed control arrangement, such as that provided by interconnected base site controllers (BSCs) and operations and management centres (OMCs).

SUMMARY OF THE PRIOR ART

[0002] Generally, in distributed telecommunication networks, particularly telecommunication networks used for providing wireless telecommunications (such as the Global System for Mobile communication, GSM), the identification of faults within the network becomes increasingly difficult. In such networks, an end-to-end route for a call is not known at call set-up and the call, in any event, may traverse networks owned or managed by several independent operators. Moreover, with the rapidly growing deployment of infrastructure, and with modern systems operating greater flexibility and dynamism, it is becoming increasingly difficult to manage fault tracking. In particular, it is difficult to verify the accuracy and authenticity of fault information and to determine from fault information where the problem actually lies. Anyway, remote identification of faults seldom provides an indication of the underlying cause of such faults and so identification and implementation of appropriate remedial actions is, to say the least, presently difficult.

[0003] There is thus a need for improved fault tracking and identification in network environments, with this particularly so in distributed telecommunication networks. Operations and management centres (OMCS) may be provided to administer certain elements of the network or, alternatively, a single centre may manage the entire network. Generally speaking, such management centres receive information only in relation to high level statistics and alarms, but not on specific problems. Usually, therefore, additional data is required in order to make a more detailed analysis of the system, to diagnose faults or to optimise sections of network performance. In a rapidly expanding distributed system, possibly spread across a large geographical region, collecting additional data may require access, either physically or logically, to different network elements or nodes in order to download the extra data required and this is time-consuming and potentially difficult.

[0004] In, for example, a distributed wireless telecommunications network, system performance/operation can be impacted by numerous changes in topology and functionality. Usually, the extent of such change cannot be accurately modelled (e.g. in advance of roll-out of additional equipment), with detailed analysis required to at least identify possible solutions. Indeed, elements that are key to performance of a cellular system often require analysis of extensive historically compiled data, which elements impact or relate to: performance optimisation; hot spot detection; handover problems and areas of interference; frequency planning; firmware, software or hardware problems associated with any network element or node; and radio coverage testing.

[0005] Indeed, during operation of a cellular system (in particular), many problems associated with the cellular system are difficult to identify and rectify due to lack of specific diagnostic information. These problems may arise from specific aspects of the particular system configuration, usage or congestion patterns, software load or other factors. Moreover, data available to the OMC to monitor specific network parameters may be insufficient or impossible to relate to user-specific problems or conditions. Other telecommunication networks typically require infrastructure-specific information when assessment of network operation is required.

[0006] Prior art systems have employed intelligent optimisation or expert adviser systems to provide the necessary performance analyses. Such systems are centralised and require considerable amounts of additional data to be gathered centrally before the analysis can be conducted. In the alternative, sufficient data can be accumulated at the network nodes during operation and forwarded to the OMC in case such analysis is required. However, increasing bandwidth constraints and the increasing quantities of data generated by a rapidly expanding network means that such approaches are unsuitable in large distributed telecommunications systems. In other words, management overhead is becoming of increasing concern in view of limited spectral resources and the desire to maximise revenue by supporting as many users as possible within the allocated spectrum.

[0007] Generally, individual nodes have acted to compress node-specific management data that is then individually communicated to a central management agent, e.g. an OMC, for decompression, processing and assessment.

[0008] The present invention is related to co-pending UK patent application XXXXXXX.X [attorney docket number CE30357UM-Lucas et al], filed on even date herewith and similarly assigned to Motorola Limited.

SUMMARY OF THE INVENTION

[0009] According to a first aspect of the invention there is provided a telecommunication network comprising: a plurality of interconnected nodes, at least some of the nodes provided with executable program code measuring at least one predetermined parameter associated with the node to produce data; a correlating node arranged to contrast data from at least two nodes to generate a composite parameter; and a network management device, responsive to the composite parameter, arranged to interpret the composite parameter to identify at least one of a network fault and performance of the telecommunication network.

[0010] The composite parameter is preferably further compressed. The data may be low-level operational performance data. The data may also be at least one of event-driven, time-driven or channel associated data, and the data is time referenced.

[0011] Preferably, the executable program code has a function dependent upon the function of the node into which the executable program code is downloaded.

[0012] In a preferred embodiment, the network management device generates the executable program code to be downloaded.

[0013] Generally, the correlating node is configured either to select data that is to be correlated or the correlating node is responsive to an instruction that targets data to be correlated.

[0014] According to a second aspect of the invention there is provided a telecommunication network comprising: a plurality of interconnected nodes, at least some of the nodes provided with executable program code; means to identify the execution, if any, of the executable program code at a node; means for identifying a fault associated with one of the node and a connection path thereto in response to the program code failing to generate a predetermined response; and means, responsive to legitimate execution of the code and generation of the predetermined response, to shuffle the executable program code to a second node for execution of a further test associated with one of the second node and a connection path coupled to the second node.

[0015] The telecommunication preferably includes means for correlating data generated by the executable program code in parallel paths, thereby to identify faults.

[0016] In one particular embodiment, correlated data of parallel paths is communicated to a central management point arranged to interpret the correlation data to identify at least one of a network fault and performance of the telecommunication network.

[0017] In a further aspect of the present invention there is provided a node for a telecommunication network, the node interconnected, in use, to at least a second node, the node comprising: executable program code measuring at least one predetermined parameter associated with the node to produce data; means to contrast data from the node with data from the second node to generate a composite parameter indicative of at least one of a network fault and performance of the telecommunication network; and means to communicate the composite parameter to a management agent arranged to interpret the composite parameter.

[0018] In yet another aspect of the present invention there is provided a method of managing a telecommunication system, formed of a plurality of interconnected nodes, the method comprising: executing program code at a node to measure at least one predetermined parameter associated with the node to produce data; correlating data from at least two nodes to generate a composite parameter; communicating the composite parameter to a network management device; and interpreting the composite parameter at the network manager to identify at least one of a network fault and performance of the telecommunication network.

[0019] In a further aspect of the present invention there is provided a method of managing a telecommunications network system, formed of a plurality of interconnected nodes, the method comprising: attempting to cause execution of program code at a first node; identifying the execution, if any, of the program code at the first node; identifying a fault associated with one of the first node and a connection path thereto in response to the program code failing to generate a predetermined response at the first node; and responsive to legitimate execution of the code and generation of the predetermined response, shuffling the executable program code to a second node.

[0020] In a particular embodiment, the method further includes attempting to cause execution of program code at the second node;

[0021] In another complementary or alternative embodiment, the method correlates data generated by the executable program code in parallel paths; and then identifies at least one of a fault and a condition of operational performance of at least one of the node and a connection path thereto from data correlation.

[0022] In a further embodiment, correlated data is communicated to a central management point; and then interpretation of the correlated data identifies at least one of a network fault and performance of the telecommunication network.

[0023] Each node of the telecommunications network thus includes an application space into which specific programs, such as program elements, applets or primitives, may be downloaded. These application spaces will support programs of specific functionality, dependent upon the functionality of the node, for example a base station will need to run different applications from a mobile switching centre or a home location register, and will allow real-time downloading and running of code. Selected data, either event-driven or time-driven or channel associated, is communicated between DPASs (such as in BSCs and BTSs) running test program applets.

[0024] These specific programs may be generated by the node or by the OMC and distributed to specific network nodes. Alternatively or additionally, certain specific programs may be included into the functionality of the node during construction or installation.

[0025] The specific programs can thus determine the information required by the OMC so that only relevant information needs to be sent over the network. Since much of the analysis may be conducted at the node, or nodes, in question, the information sent to the OMC may be limited to the results of the analysis.

[0026] The source of errors and faults in a distributed network can thus be determined without resorting to centralised OMC functions, since any node within the network can initiate a test sequence, either locally or across the entire network.

[0027] The nodes may contain a local clock, referenced to a central time reference. Parameters recorded or measured by the program element may be time stamped by the local clock. Consequently, when this information is exchanged between one node and another, or between a node and a centralised OMC, the information may be correlated and identified by the time stamped. It may thus be possible to recognise events as a result of this correlation and identification process, in order to determine network performance. The determined network performance may be further used to determine the need for a change in the network.

[0028] One advantage of the invention is that the reliability of the network is monitored by other elements of the network and is not reliant on locally defined and held self-test routines or centralised test procedures. Another advantage is that testing of the network is not limited to the testing of physical links, service or content provision, Quality of Service (QoS), and that other diverse parameters can be tested. Such an approach may be especially useful in network systems where several operators and service or content providers provide separate elements or collaborate to provide and manage the network.

[0029] Another advantage of the invention is that control of the various downloaded specific programs is delegated to the node or network element initiating the application. Delegated control is passed from node to node as the test applications, in particular, are spread through the network. Where the program element is downloaded to a specific network node for, in particular data collection and analysis, the node may interact with other nodes to obtain and verify the information but delegated control is maintained at the delegated node.

[0030] Yet another advantage of the invention is that by providing end user devices (and in particular mobile devices) with an application space enables new and problem specific software to be downloaded into the device, thereby enabling specific conditions to be tracked and monitored. The diagnostic applications can preprocess data or initiate fault locating procedures on behalf of the OMC.

[0031] Yet another advantage of the invention is that diagnostic applications may operate in a pre-emptive mode and actually force a particular failure or condition in the network to assist in identifying the cause of the problems.

[0032] One aspect of the present invention is particularly applicable to fixed networks having variable quality of service (QoS), and in which fixed networks there is a partial loss of communication capabilities resulting in a reduction in functionality.

BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Exemplary embodiments of the present invention will now be described with reference to the following drawings, in which:

[0034] FIG. 1 shows in outline a telecommunications network providing wireless communications to a variety of different users, the telecommunications network adaptable to support the concepts of the present invention; and

[0035] FIGS. 2 and 3 are flow diagrams of preferred operating methodologies by which management data is accumulated, routed and analysed by management control elements of FIG. 1.

DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT

[0036] FIG. 1 shows, in outline, a telecommunication system 10. A mobile station (MS) 12 (of which there are many within each cell of the system) communicates over an air interface 14 with at least one base transceiver station (BTS) 16-22 support a coverage area. Each BTS 16-22 is connected to a telephone network 24 via a base station controller (BSC) 26-30 and a mobile switching centre (MSC) 32-34. BTS are therefore interconnected through MSCs. Each BSC 26-30 is therefore responsible for providing service to at least one cell 36-42 through control of one or more BTSs 16-22, with each cell containing one or more BTSs. The system may support and overlay-underlay environment of cells, as is well known, with a plurality of micro-cells 44-46 controlled by a single BSC. Each MSC may also be connected to an operations and maintenance centre (OMC) 48. The OMC may contain a central time reference, with which clocks in the various other nodes of the network may be synchronised.

[0037] In combination, a BSC and BTS is generally referred to as a base station subsystem (BSS).

[0038] Along with the OMC 48, the mobile stations 14 and BSSs (and other network devices) are all nodes of the telecommunication system 10.

[0039] Connected in the telephone network 24 are a plurality of interconnected multi-architecture telecommunications networks 50-58, including networks supporting broadband and narrowband domains (e.g. broadband asynchronous transmission mode (ATM) networks, narrowband public-switched telephone networks (PSTNs) and integrated service digital networks (ISDNs, etc). Also connected to the telephone network are corporate voice and data networks 60 (e.g. intranets) and internets 62.

[0040] Each node of the network contains a downloadable programmable application space (DPAS) 70-98 which supports one or more primitives that can be programmably configured to perform a number of different tasks upon receipt of a specific downloaded program (sent, for example, in the form of an applet or the like). The mobile stations within the network may also contain a DPAS to receive, store and initiate specific program applications; the DPAS shown in the form of a microprocessor 100 and associated memory 102.

[0041] One embodiment of the invention has a file server 106 connected to the telephone network 24, the file server accessible by a MS through a service provider. A router 108, providing routing and interface capabilities to the telephone network 24, is disposed between the telephone network 24 and the file server 106. Of course, rather than being subject to a permanent connection, the file server 106 may be connected periodically to the telephone network 24 via a modem (not shown).

[0042] By way of operational overview (as shown in FIG. 2), the present invention looks to acquire relatively low-level system data from a number of locations, i.e. nodes. The low-level system data, such as quality of service metrics from subscribers, is then communicated to at least one of the nodes tasked to obtain the low-level system data at which point correlation of this low-level system data from the various other (similarly tasked) nodes is undertaken at a correlation node. Should the correlation reveal a particular anomaly (in terms of operational parameters or in time), then a compressed summary (i.e. selective information in a predetermined report format) of this anomaly is communicated to a central management point, such as an OMC or the like. In contrast with prior art systems that send large volumes of semi-compressed data to a central management point, the present invention instead limits fault reporting (and hence bandwidth utilisation) to highly compressed pertinent data that is directly relevant to the performance or optimisation of the system (or portion thereof) under test.

[0043] Generally, either in response to an alarm trigger or independently on a management (housekeeping) basis (step 200 of FIG. 2)), management programs or applets are communicated to identified system nodes, such as BTSs, BSCs or MSs, where such programs and applets are loaded 202 to the respective DPAS 70-96. Local control processor functionality implements 204 the program or applet which tasks the local (“test”) node to acquire information pertaining to certain identified operational parameters or connection paths/routes. Such operational parameters may be measures of quality of service (e.g. Eb/No and/or frame erasure rate (ER) in the case of a CDMA system, or bit error rate (BER) or signal strength (RSSI) in the context of GSMtype systems) or serving cell identities, etc. The identified operational parameters or connection paths/routes are then monitored, typically over a predetermined period. The program or applet also generally includes a reference to other nodes similarly instructed to undertake the acquisition of information/data pertaining to certain identified operational parameters or connection paths/routes. Once information/data is being/has been accumulated at the node, then the program or applet causes communication of the information/data to a designated node for correlation/contrast (206 of FIG. 2), such as a BSC, which designated node may be in the same hierarchical system layer. Communication of the information may be subject to a suitable form of security coding since the information is potentially system/user sensitive.

[0044] As an alternative implementation, an interrogation mechanism of the node by either a higher-level system entity or designated node could equally be applied to the collection of information/data at an intermediate point.

[0045] Now, with the information/data from several test nodes available to at least one correlation node, the correlation node looks to identify patterns (206 of FIG. 2) in the information/data that could be representative of component faults or system operation. Any correlation is then, preferably, formatted 208 into a highly compressed report containing only pertinent data (reflecting event/parameter correlation between different test nodes), which report is sent 210 (typically in a coded form) to the central management point for assimilation. Should the report indicate a particular system fault or condition, then the central management point either: i) generates 212 an alarm (in a responsive fashion); or proactively ii) issues instructions to correct the fault or condition (through issuing software instructions); or iii) proactively addresses 214 the fault or condition be re-routing paths and/or re-assigning infrastructure equipment to accommodate the prevailing system condition. The system of the present invention therefore distributes management overhead across (generally) lower level system entities, with the central management point only having to assess highly compressed and pertinent report data. In this way, the present invention allows the central management point to review low-level system data that it would not have had access to in prior art system arrangements. In other words, the present invention is able to draw on a finer level of granularity in assessing system faults and operational conditions, whilst limiting information overhead to the central management point. Moreover, the finer level of granularity increases system diagnostic capabilities, whilst the highly compressed and pertinent report format eases demands on management processing (i.e. MiPS) capabilities.

[0046] In essence, a management-defined parameter derived from a specific test program executed at a first node is combined with a management-defined parameter derived from a specific test program (which may be the same test program or a different test program) at at least one other node. The combination of parameters is used to produce a composite parameter reflecting operational performance or fault conditions, the composite parameter generally reflecting performance correlation between the nodes under test, if any.

[0047] The present invention is therefore able to look to information that has joint properties between nodes. By directly extracting joint properties of data from a plurality of nodes (through the communication and comparison of selected uncompressed or partially compressed data) enables a greater compression of data than is possible by undifferentiated compression of the data at separate nodes followed by processing at an OMC.

[0048] Parameters that may be measured may include: quality of service (QoS) levels or requests; traffic levels; link quality measures (for the serving cell, neighbour cell); alternate air-interfaces; energy per modulating bit (Eb/No) target; link delay; user equipment (UE) transmission levels); network routing; the soft handover active set; and UE observed neighbours. Network events that may be monitored/assessed may include: mobile faults; radio coverage issues for a given service; identification and mapping of alternative (air-interface) technology locations; identification and mapping of boundary for handover to alternative technology; collection and/or correlation of data from users on alternative technology; and optimum QoS settings. Changes to a network that may be monitored include: determining handover (either with or without system consent); changes to QoS targets; changes to Eb/No targets; the recall of certain mobiles; the need to install new nodes, e.g. BTS equipment; the need to replace or repair a BTS; the need to modify or adapt network routing; and theneed to modify neighbour relationships.

[0049] In one particular embodiment, the OMC 48 downloads program code to determine, for example, coverage from a group of adjacent cells. The MS 12 is currently camped onto its serving cell, i.e. BTS 18, although MS12 monitors other BTSs in the area for handover requirements. In this embodiment, several BTSs are all running applications to determine cell coverage and to determine whether handover is occurring effectively. The DPAS (such as reference numeral 72) associated with BTS 18 analyses the measurement reports sent by MS 12 over a period of time. Other DPASs also analyse measurement reports from MS 12 and forward this information to DPAS 72 (which has been selected as the correlation node when the program code is downloaded). The forwarding of information can be automatic on upon request from DPAS 72. From the incident information/data, DPAS 72 can extrapolate information regarding coverage within the required cells. The applications running DPAS adjoined to the correlation node may be initiated either by correlation node itself or, for example, directly from the OMC 48.

[0050] In yet another embodiment of the invention, MS 12 may be traversing cell or sector boundaries such that the MS is subject to a handover routine. In the event that a BSC (involved in the process) determines that the handover process between BTSs is not occurring as expected, the BSC reports the problem/fault to an interconnected management site, e.g. OMC 48. The OMC 48 downloads a specific application into at least one of the DPAS related to the nodes involved with the handover process, which nodes then interact to determine if there is no spare traffic channel or whether another kind of fault exists. Preferably, one of the DPAS then pre-processes the data and filters out relevant data for return to the OMC.

[0051] In another embodiment, multiple MSs active in a particular cell are downloaded with a particular application that causes a mass calling load on the cell at a specific off-peak time. A related DPAS (associated with the BSS) is loaded with particular application software that monitors the nodes with which the BSS has contact during the mass load operation. Both the MS devices and the DPAS report relevant data to the OMC.

[0052] MS may also be downloaded with software that monitors when connection to the network is lost, with the software then configured to report loss to the OMC when the connection has been re-established.

[0053] In one embodiment (see FIG. 3), the MS 12 connects to the file server 106 via the telephone network 24 described above using an appropriate connection route. If the MS 12 determines that fault conditions exists with the connection, it initiates 300 a procedure to assess operational capabilities of the network through identification of a cause and a point of system failure. More specifically, the MS 12 asks the network node to which it is connected, which in this instance is its serving BTS 18, to set up a test mode and to send a test mode acknowledgement. If the test mode is to be set up by the BTS (in response to MS request), the BSC 28 causes the BTS 18 to download and store (302) the test code to be run by the BTS 18 and an acknowledgement is preferably sent to the MS 12. The procedure can, of course, be implemented from a higher base point within the system (other than the MS 12) such that the mechanism is infrastructure-based.

[0054] One example of the test code might be:

[0055] start

[0056] write test encryption code ETY23561 L to memory run decryption on memory using public 3-key code respond with decrypted message

[0057] accept the next 1000 bytes and store in memory encrypt code using public key and return code indicate measured round trip delay in ms

[0058] end

[0059] If the tested node refuses/is unable to download and run the code 304-308, a conclusion can be inferred that the test node is either having difficulties in operational performance or is acting illegally. Hence, the network manager may be indirectly appraised on a fault and further analysis/work 309 (such as the dispatch of an engineer) may be required. Furthermore, in operation, if the node under test does not return expected code 310-314 then, again, a conclusion that the node is at fault may be drawn. If the node under test returns incomplete or corrupted data 310-314, the node can be identified as the source of the problem.

[0060] If the test algorithm proves the integrity 316 of the link and the node under test, the node can be instructed to shuffle 320, i.e. pass, the test routine onto the next node in the connection (should a further node exist 322 within a communication chain to the network manager or the like). The test regime is then continued (steps 304 onwards of FIG. 3) until a problem link/node is identified or the system is found to be fully operational.

[0061] In the exemplary manner of FIG. 3, a mechanism is provided that tracks the source of errors within a system without the need for centralised management and testing. The number of test instructions and the amount of test data and results crossing the network to the centralised network management centres can thus be considerably reduced. In a particular embodiment of the invention, the test procedure can be simultaneously applied to multiple parallel data paths employing independent nodes, e.g. an internet type environment. Periodic correlation of the various parallel paths may be applied to identify faults and to limit uplink management data transfer to a central management point, e.g. a file server 106, an OMC 48 or a portable PC-based management tool. Such correlation may therefore also follow and reflect the process and methodology set out in the flow diagram of FIG. 2. For example, the flow of FIG. 3 could be enhanced to include steps 206 to 214 of FIG. 2, as will now be understood.

[0062] The test code can perform a number of different functions and may be comprised of one or primitives which the test environment is designed to assess. It is also worthy to note that the tested node (in this instance BTS 18) is not generally in control of the test, unlike self-test routines. Clearly, the system/operational mechanism of this particular aspect of the present invention is also applicable to solely wireline based systems, including the internet where multiple paths between nodes exist.

[0063] It is preferred that both upstream and downstream communication is encrypted for security, but other methods, such as connecting to a known time synchronised data source, may be employed

[0064] Of course, in an air-interface environment, the absence of a radio link may be entirely endemic of the underlying fault and no detailed problem analysis or identification may be required. In slightly different language, with the air-interface inoperative, even analysis software that is resident at a particular node cannot talk directly to the base station. However, provided that the node has access to additional/supplementary links (such as the world-wide web, a wide area network (WAN) or bluetooth), downloadable test software can be used to explore system operation or faults through the use of such alternative links.

[0065] Alternative embodiments of the invention may be implemented as computer program code encoded on a computer program product for use with a computer system. It is expected that such a computer program product may be distributed as a removable medium with accompanying printed or electronic documentation (e.g. shrink-wrapped software), preloaded with a computer system or distributed from a server or electronic bulletin board over a network (e.g. the Internet or World Wide Web). A series of computer instructions can therefore either be fixed on a tangible medium or fixed in a computer data signal embodied in a carrier wave that is transmittable to a computer system using wireline or wireless transmission techniques. The removable (i.e. tangible) medium may be a computer readable media, such as a diskette, CD-ROM, DVD-ROM or RAM, fixed disk, magneto-optical disks, ROMs, flash memory or magnetic or optical cards. The series of computer instructions embodies all or part of the functionality previously described herein with respect to the system.

[0066] Software embodiments of the invention may be implemented in any conventional computer programming language. For example, preferred embodiments may be implemented in a procedural programming language (e.g. “C”) or an object oriented programming language (e.g. “C++”).

[0067] Although the preferred operating method is realised by general or specific-purpose processor or logic circuits programmed with suitable machine-executable instructions, hardware components may possibly be used to implement certain features of the present invention. Of course, the present invention may be performed by a combination of hardware and software.

[0068] It will, of course, be appreciated that the above description has been given by way of example only and that modifications in detail may be made within the scope of the present invention. Whilst the present invention will be described in relation to the extensive system topography outlined above, the present invention can find application in particular facets of the topography. For example, the present invention can be employed solely in relation to the cellular system or, indeed, within a portion of the cellular system (such as within a BSC and lower system entities, e.g. BTS and MSs, associated therewith).

[0069] The present invention finds application in telecommunication systems in general, including (but not limited to) internet, dual band (radio frequency) systems, combined GSM/CDMA systems, and third generation multimedia applications.

Claims

1. A telecommunication network comprising: a plurality of interconnect ed nodes, at least some of the nodes provided with executable program code measuring at least one predetermined parameter associated with the node to produce data; a correlating node arranged to contrast data from at least two nodes to generate a composite parameter; and a network management device, responsive to the composite parameter, arranged to interpret the composite parameter to identify at least one of a network fault and performance of the telecommunication network.

2. The telecommunications network of claim 1, wherein the composite parameter is compressed.

3. The telecommunications network of claim 1, wherein the data is low-level operational performance data.

4. The telecommunications network of claim 1, wherein the executable program code has a function dependent upon the function of the node into which the executable program code is downloaded.

5. The telecommunications network of claim 1, wherein the network management device generates the executable program code to be downloaded.

6. The telecommunications network of claim 1, wherein data is at least one of event-driven, time-driven or channel associated data, and said data is time referenced.

7. The telecommunications network of claim 1, wherein the correlating node is configured to select data that is to be correlated.

8. The telecommunications network of claim 1, wherein the correlating node is responsive to an instruction that targets data to be correlated.

9. A telecommunication network comprising: a plurality of interconnected nodes, at least some of the nodes provided with executable program code; means to identify the execution, if any, of the executable program code at a node; means for identifying a fault associated with one of the node and a connection path thereto in response to the program code failing to generate a predetermined response; and means, responsive to legitimate execution of the code and generation of the predetermined response, to shuffle the executable program code to a second node for execution of a further test associated with one of the second node and a connection path coupled to the second node.

10. The telecommunication network of claim 9, further comprising: means for correlating data generated by the executable program code in parallel paths, thereby to identify faults.

11. The telecommunication network of claim 10, wherein correlated data of parallel paths is communicated to a central management point arranged to interpret the correlation data to identify at least one of a network fault and performance of the telecommunication network.

12. A node for a telecommunication network, the node interconnected, in use, to at least a second node, the node comprising: executable program code measuring at least one predetermined parameter associated with the node to produce data; means to contrast data from the node with data from the second node to generate a composite parameter indicative of at least one of a network fault and performance of the telecommunication network; and means to communicate the composite parameter to a management agent arranged to interpret the composite parameter.

13. A method of managing a telecommunication system, formed of a plurality of interconnected nodes, the method comprising: executing program code at a node to measure at least one predetermined parameter associated with the node to produce data; correlating data from at least two nodes to generate a composite parameter; communicating the composite parameter to a network management device; and interpreting the composite parameter at the network manager to identify at least one of a network fault and performance of the telecommunication network.

14. The method of claim 13, wherein the composite parameter is compressed.

15. The method of claim 13, wherein the data is low-level operational performance data.

16. The method of claim 13, further comprising downloading the program code to the node on at least one of a periodic basis and in response to a management request.

17. The method of claim 13, wherein data is at least one of event-driven, time-driven or channel associated data, and said data is time referenced.

18. A method of managing a telecommunications network system, formed of a plurality of interconnected nodes, the method comprising: attempting to cause execution of program code at a first node; identifying the execution, if any, of the program code at the first node; identifying a fault associated with one of the first node and a connection path thereto in response to the program code failing to generate a predetermined response at the first node; and responsive to legitimate execution of the code and generation of the predetermined response, shuffling the executable program code to a second node.

19. The method of claim 18, further comprising: attempting to cause execution of program code at the second node;

20. The method of claim 18, further comprising: correlating data generated by the executable program code in parallel paths; and identify at least one of a fault and a condition of operational performance of at least one of the node and a connection path thereto from data correlation.

21. The method of claim 18, further comprising: communicating correlated data to a central management point; and interpreting the correlated data to identify at least one of a network fault and performance of the telecommunication network.

22. A computer program element comprising computer program code means arranged to make a controller execute procedure to perform the method steps of claim 13.

23. The computer program element of claim 22, embodied on a computer readable medium.