A SYSTEM FOR MONITORING TELEPHONE NETWORKS AND/OR DATA COMMUNICATION NETWORKS, ESPECIALLY MOBILE TELEPHONE NETWORKS

Abstract: The present invention relates to a system for monitoring telephone networks and/or data communication networks, especially cellular mobile telephone networks (CeN), and for the purpose of providing a system giving good evidence of performance and quality of the services to be delivered by the network, at the same time as the system should be easy to handle and should comprise components which require small space and are effective in use, according to the invention a system (CeNA) is suggested comprising one or more fixed and/or mobile units (FTU, MTU), here designated as field units or test units, which units comprise quality observation means communicating with a network operator or operation center (CU).

Description: A SYSTEM FOR MONITORING TELEPHONE NETWORKS AND/OR DATA COMMUNICATION NETWORKS, ESPECIALLY MOBILE TELEPHONE NETWORKS The Scope of the invention The present invention relates to a system for monitoring telephone networks and/or telecommunication networks, in particular cellular telephone networks. The background to the invention The rapid, world-wide expansion in cellular networks com¬ bined with keener competition among network operators, has meant an ever increasing need for continuous improvement as to quality and accessibility of networks as stated. Where the network operator is concerned, higher quality and better accessibility must be obtained while at the same time prices of calls and other services should be kept as low as possible. Subscribers expect the operator of the cellular network to be able to offer services of a high quality at a price comparable to that of fixed installed networks. To meet these requiremen s, the applicant has developed a system for monitoring cellular networks as stated, namely a system comprising an operator's tool for testing, verifi¬ cation, planning and maintenance, as well as continuous inspection and monitoring of cellular networks With this system, the operator will be able to verify his planning and restructuring of cells for expanding and enhancing the network, to detect problems in existing networks as seen from the subscriber's point of view, and with speed and efficiency take steps to resolve any problem as stated. Because the system comprises' manageable elec- tronic data, it will be possible for the operator to obtain statistical lists to be used in analysing the quality of the network, and also to obtain at desired points in the network and at any time, a clear picture of the immediate and future measures which need to be implemented in order to maintain an optimal network. The aims of the invention One aim of the present invention is to describe a system which may be designed and configured for simple instal¬ lation and operation while at the same time procuring objective observations of the performance in the network concerned and thus information to the network operator concerning the service provided through the network. A further aim of the invention is to provide a system whereby the operator may in a simple manner set the requisite control parameters, and a system which, once the parameters and operating commands have been set, more or less operates without supervision. Another aim of the invention is to describe a system which may be built on a modular basis, thus permitting simple extension of the system when the network(s) concerned grows larger, whether relating to analogous and/or digital standards. Yet a further aim of the invention is to describe a system designed in such a way as to allow the processed data to provide information in relevant and easily readable formats, e.g. for printed reports and suitable statistics. One more aim of the invention is to describe a system where the operator may evaluate the performance statistics relative to random points in the network, or study in detail the network performance as experienced by a user. Siimmary of the invention These aims are achieved according to the invention by a system of the nature described initially, which is characterised in that it comprises one or several fixed and mobile units, referred to here as field units or test units, the said units containing quality observing organs which communicate with an operator of the network, in particular an operator for a cellular mobile network. The most important components which are part of the system according to the invention thus comprise a mobile test unit (MTU) and a fixed test unit (FTU) , the mobile test unit preferably being designed as an autonomous module, capable of receiving orders from and supply results to a fixed unit. The mobile unit may be programmed or ordered to carry out quality observations comprising the radio signal level on one or several defined channels, signalling of decoding , calculations of bit error rate, performing analogous measurings, both "down-link" and "up-link", and log position information. Results observed by the mobile unit will suitably be reported back to the fixed unit for accumulation of stati- sties, and the mobile unit may suitably comprise a micro processor and be placed in a suitable vessel/vehicle. The fixed unit which communicates with the mobile unit may constitute the operator's point of access to the system as to specification of parameters, definition of tasks, presentation of status of service, and ordering of presentations of results. The fixed unit (FTU) receives calls from the mobile unit (MTU) and represents the fixed end of a call. Logging will also take place here. In addition, the system comprises an operations centre (CU) which constitutes a collective concept for a number of units and enables communication between the said field units (FTU, MTU) and the operator or the user of the system. This operations centre allows communication not merely between the said field units in the relevant cellular telephone network but also communication between databases via e.g. one or several open data networks. An operations centre may suitably comprise a frontal unit (FE) which defines the interface for operating and defining the actual system, a database management system (DBMS) , a main server (CeNAS) which takes care of the exchange of data between the database management system and the said field units (FTU/MTU) , a configuration station (CS) which defines the interface for maintenance of data and system resources, and a presentation station (PS) with the task of presenting the relevant data/measurements. Appropriately, a central unit as stated may comprise soft¬ ware to handle operator communication and system operation, generating of digital maps as well as presentation of results. Further advantages and features of the present invention will become evident from the description below taken in conjunction with the attached drawings, and the patent claims attached. Brief description of the figure in the drawings Figure 1 is a block chart showing an example of interaction between a cellular mobile network (CeN) and a permanent network (PSTN) comprising components which may bring the present invention to fulfilment. Figure 2 shows an interaction image for a configuration station being part of the system according to figure 1. Figures 3A and 3B together show another interaction image which may appear on creation of system functions, in particular when the frontal unit (FE) is being used. Figures 4A and 4B together show yet another interaction image which may be used in setting parameters in the system. Figures 5A, 5B and 5C are together a screen image of a geographical area where certain statistically related data have been plotted. Figure 6 is a screen image showing statistical tables of certain logged observations of quality. Figures 7A, 7B and 7C together show a screen image of a routing overview for a mobile conversation, while figure 7D is in larger scale one part of figure 7C. Figures 8A, 8B and 8C are together a screen image similar to figure 5, where is shown in larger scale a statistical map overview of accumulated measurements. Figure 9 is a screen image similar to Figures 7A-7D where a map overview shows the quality of a conversation for a mobile unit along one particular route. Figures 10A and 10B are together a screen image which shows statistics presented as bar charts. Description of embodiments In Figure 1 is shown schematically an outline of the system according to the invention, referred to here as CeNA which could also be described as a cellular network analysis system. The cellular mobile network is referred to in Figure 1 as CeN, and this network communicates with a permanent network, PSTN, which in turn, and via a multitude of fixed test units FTU communicates with an operations centre CU. The system CeNA comprises a set of tools for the cellular operator and is used continually for monitoring the quality of services in the network concerned, in particular the cellular mobile telephone network CeN. In principle, the system aims to represent the subscribers' perception of the quality of the services in the network. To attempt to achieve maximal performance, the system builds on the following criteria: To carry out volume measurements in the network con¬ cerned, the said measurements being made by means of, on the one hand, fixed units, referred to here as fixated test units, FTU, and, on the other hand, mobile units, referred to here as mobile test units, MTU. The fixed test units FTU which may comprise a multitude of such units, may be spread out geographically, while the mobile test units MTU, which may also be arbitrary in number, are preferably fitted into vessels/vehicles with random or determined routes in the specific network CeN to be monitored. User-friendly surroundings for positioning and maintenance, in particular with regard to the operator interface relative to the operations centre CU, from where random fixed test units FTU and mobile test units MTU can be configures and controlled, placing and maintenance being capable of being divided, while at the same time levels of access may be allocated according to the wish of the operator. The operations centre CU with its components thus has user-friendly surroundings which means that the whole system may be governed from just one geographical location, since the stationary and mobile test units do not need to have an operator's interface Unattended operation is aimed for after a system configuration has been defined and system orders received and carried out, because the system components are then capable of making unattended observation measurements of quality, and perform collecting, storing and more or less complete processing of collected data, while at the same time real time communication of the results and pertaining storage ensure immediate access to the measured results. Storage of results based on an open database system allowing easy access to and exchange of information, while at the same time an open database architecture also affords the user the option of using the information in his own application and in connection with other information from the same or from other open database systems. - Standardised communication protocols between system components entail communication via the same open network, e.g. TCP/IP which means flexible configuration and distribution of system components, with exceptions for communication between the fixed test units FTU and the mobile test units MTU which employ a mobile data communication link and the permanent network PSTN. Flexible configuration for easy adaptation to varying and growing demand is achieved by using the data network as a link between system components, adaptation to various configurations, as well as a complete overview of the development potential. Diverse and powerful visualisation of the results focusing both on detailed and statistical presentations, with most of the presentations building on the use of a geographical information system which enables the operator or the user to assess the results relative to their factual surroundings in the geographical position concerned. The presentation of the results may also comprise means for generating statistical reports, and all the presentation tools may be based on industrial, standardised tools com¬ ponents and formats, thus allowing easy export of the information to other applications. In summary, a system as shown in Figure 1 could make it possible for the operator in a straightforward manner to configure and maintain measuring nodes, to carry out and to store field measurings with a minimal number of components and also to utilise the collected data for orderly presen¬ tation and analysis as well as for easy distribution of reports and results to other users in the organisation concerned. A closer inspection of Figure 1 will reveal that the said CeNA system may comprise a multitude of components which constitute the complete system according to the invention, namely for ordering, collecting, storage, administration and presentation of the observations of quality which are made in the cellular mobile telephone network which is to be monitored. According to an appropriate embodiment of the invention, a so-called front end FE is used which could be described as the interface for the operator or the user of the system in managing the components which are part of a CeNA system. The main tasks carried out by the front end FE, include definition of system components, ordering of measurings and monitoring system performance. By means of or from the front end FE, the user may set parameters for any of the previously mentioned fixed test units FTU and mobile test units MTU, and also issue orders concerning measurings for the said and other components which are defined in the system. The said front end FE may be called up from any work station in the connected data network. Access to the various system components may be defined and restricted according to the operator's needs, and password protection may be used. This permits a flexible set-up with regard to definitions of orders for measurings and distributed maintenance of the CeNA system(s) concerned. All definitions in the system and set-up of orders are retained in a so-called database management system DBMS, allowing the user with ease to retrieve and/or modify existing definitions. The said front end FE also provides functions for monitoring activities in the CeNA system, both with regard to immediate situations and collected statistical data concerning such activities. The front end FE may suitably be implemented in a standard Windows configuration and utilise the data network for access to a server CeNAS for the said cellular network monitoring system CeNA, and the said database management system DBMS. The said server CeNAS has as its task to relay measurement orders from the database management system DBMS to the flexible test units FTU, as well as the measuring results from the said flexible test units FTU to the database management system DBMS. The results may comprise data from observations of quality from the fixed test unit FTU concerned, or comprise results received by the latter from relevant mobile test units MTU for storage in the database management system DBMS. Moreover, the server CeNAS has as its task to keep stati¬ stics of the use of the system, comprising statistics of activities for the said mobile test units MTU and fixed test units FTU, and to pre-process the measuring results for statistical information with the emphasis on perfor¬ mance and with subsequent presentation in mind. In other words, the server CeNAS constitutes a central part for the said CeNA system and may for instance be imple¬ mented in a UNIX configuration, the server generally residing in the same computer as the one comprising the server platform for the database management system DBMS. It should be understood that the server communicates with the fixed test units FTU via the network mentioned previously, TCP/IP. As mentioned above, each of the fixed test units FTU is employed in announcing calls via the network PSTN to the individual mobile test units MTU and to answer calls from the said mobile test units MTU in the mobile network CeN. The fixed test units FTU thus have as their task to relay calls to selected mobile test units MTU and thereby communicate measurement orders, to evaluate their own measuring orders with regard to the time for calling mobile test units, to initiate calls to mobile test units MTU in the mobile network CeN, and also to measure selected parameters for originating calls, and, finally, to answer calls from mobile test units MTU and to receive observations of quality from there. The fixed test units FTU may suitably be implemented as free-standing units, and all control of the fixed test units will, in the embodiment shown, be exercised from the front end FE. With a given configuration, one or each of the flexible test units FTU will be able to serve from 1 to 20 PSTN lines, while at the same time each of the fixed test units may be distributed in a suitable geographical pattern, and also communicate with the mobile test units MTU via the said mobile network CeN, as well as with the server CeNAS via the data network TCP/IP. Each of the mobile test units MTU performs all the said observations of field or quality in the relevant mobile network. In other words, it is the task of the mobile test units to: - receive measurement orders from fixed test units FTU, - answer calls from the fixed test units FTU, - evaluate measurement orders and take action accordingly, - make calls to the fixed test units FTU, - take measurements in the mobile network concerned, inclu ding logging of a multitude of parameters, - position relate and time stamp all measurements made, - communicate measurement results to fixed test units FTU The mobile test units MTU mentioned will originate and answer calls in the mobile network concerned in accordance with given measurement orders, and the measurements carried out will be sent back to one or several fixed test units FTU very nearly in real-time. In the event of a dropped call, the mobile test unit MTU concerned will temporarily store the results in its own internal storage device, in order suitably to transfer these at a later time. Each of the mobile test units MTU may suitably be built as an inte¬ grated unit comprising a micro computer, a test mobile, a positioning system, e.g. GPS, as well as communications equipment. By using appropriately so-called PSMClA-based storage, each of the mobile test units can easily be up¬ graded with new software versions without the support of a programmer. The complete mobile test unit MTU may thus suitably be built into a small house, facilitating easy installation in a vessel/vehicle. Also shown in Figure 1 is a configuration station CS whose task it is to maintain the database management system DBMS and the GIS system resources existing in the system. Via a user-friendly interface the operator may define resources for measurement both with regard to the database management system DBMS and the said GIS system. This entails that the operator may determine how data collected from the field units comprising the mobile test units MTU and the fixed test units FTU are to be handled. The main tasks having been given to the configuration station CS are to: administer how measurements are to be grouped relative to time, location and user's identification, administer map information for a geographical informa¬ tion system, the GIS system, - define links between measurement results and geogra¬ phical information, define geographical areas used in ordering presentations of measurements and results, leave out or store as back-up old measurement results in order to release space in a database management system DBMS. The implementation of the configuration station CS may suitably be done in a standard Windows configuration, and may be used in the data network TCP/IP for access to the collectively shared resources in the database management system DBMS. As is the case with the front end FE, various access rights may be granted or refused to specific users. One example of a screen image related to a configuration station CS is shown in Figure 2, the said interaction image being related to the creation of a new map, related to the GIS system concerned. Moreover, shown in Figure 1 is a presentation station PS which constitutes the operator's tool for presentation of the collected measurements. By means of a geographical information system and a spreadsheet system, the user will have the possibility of viewing the results in different formats. The presentation station PS allows visualisation of data collected through the database management station DBMS, presented both as conversation oriented and as stati¬ stically oriented. The main operations allocated to the presentation station PS are: to make it possible for the user to select and present individual conversations (one measurement order carried out from set-up of the call until shut-down) which focuses on each individual measurement and incident during the conversation, - to make it possible for the user to select and present statistical overviews of the collected measurements, enabling one to group measurements according to time, location and size, the statistical overviews giving measurement results as properties of the location and the network parameters, rather than as properties of indivi- dual conversations. - to procure detailed tabulated presentations of data related to route outlines and statistical overviews, enabling the user to emphasise and study details of the GIS presentations, - to enable the user to draw up and to procure reports from the statistical data in the database management system DBMS. By procuring report templates with pre-selected topics, and restrictions based on the resulting data, the user will readily be able to procure reports, all the functionalities of the presentation station PS being suitably integrated in a "Windows" platform, as standard "Windows" applications are used. For geographically oriented presentations, a geographical information system is used at the presentation station PS, which is fully controlled by the presentation station PS. This entails that a presentation is provided of the measurement results related to the geographical position, either as single conversations or statistical data, and then as a fully integrated part of the presenta¬ tion station PS, entailing that it is not required for another sub-system to be started, with its own set of commands and terminology. It should be understood that in the presentation station PS a suitably user-friendly report generator exists, affording the user the possibility of selecting the results which are of interest, and to set the criteria of the basis for a report. The report generator of the presentation station PS may be associated with the use of an integrated "EXCEL" spreadsheet for composing or editing the reports. The said database management system DBMS may be referred to as the focal point for all information in the said CeNA system. The database management system will hold all permanent information in the system, comprising among other things: - definitions of areas which are being used in setting measurement orders and presentation of information, system component parameters for all components, e.g. comprising fixed test units FTU, mobile test units MTU, etc. , - measurement orders which are permanently stored in the database management system DBMS for subsequent repeated use or change, storage of all individual measurement results from fixed test units FTU and mobile test units MTU in the database management system DBMS, results of statistical data from analyses concerning the measurement results. It should be understood that all relevant data are stored in the said database management system DBMS, be it data relating to the configuration of the system components, set-up of measurement data, etc., as well as statistics about all mobile test units MTU and fixed test units FTU and also results from the network and the processed results therefrom, the system handling all data in a consistent manner, utilising the database management system as the preferred storage system which thus eliminates any intermediate formats visible to the user. The database management system is well structured, allowing the user to use pertaining information for applications different from those related to the set of tools associated with the actual network analysis of the cellular network. The open DBMS architecture also offers the user the option of combining the information in the DBMS with other external data sources and to establish links by means of common indices. The DBMS system may be chosen among most standar- dised database systems available in the market, in particu¬ lar by using ODBC based technology. The components mentioned as being part of the CeNA system communicate via standard communication networks based on TCP/IP, making a wide range of configuration solutions possible. The front end FE mentioned, the server CeNAS, fixed test units FTU and the presentation station PS may be geographically distributed and connected via the said network TCP/IP and the database management system DBMS. Because the said TCP/IP is supported by a large variety of base networks it is possible to interconnect components via LAN, WAN, fixed dial-up lines or ISDN. The communication between the mobile test units MTU and fixed test units FTU is implemented via a special modem. Description of functions The main functions in the system described, mentioned in connection with Figure l, may be listed as follows: - measurement preparations comprising definition of components and allocation of system resources, handling of orders with setting-up of measurement order effectuating orders, comprising transmission of measurement orders to FTU and MTU, - measurement phase in which FTU and MTU carry out measurements and logging and also transmission of results back to server CeNAS, handling of results in which results are received, analysed, and stored in DBMS. - presentation of results where the operator may be given an overview of results and generate reports. With reference to Figures 3 and 4 which show different interactive screen images, further details of the prepara¬ tions for measurement will be described in detail. Before a system can be put into operation, all system com¬ ponents must be defined, this work being performed at the time of setting-up the system, or when system components are introduced or re-configured, this work being carried out from the front end FE, see Figure 1. The operator will then define parameters for the fixed test units FTU and the mobile test units MTU concerned, and for the fixed test units FTU that may include the parameters: Name of FTU, comprising a symbolic reference to the FTU concerned, - FTU network address subscriber numbers in the FTU concerned geographical position for the FTU. Where the mobile test units MTU are concerned, parameters will also here be set up at the front end FE, and will suitably comprise: MTU name for identification MTU home area, identifying where the MTU normally operates, - vehicle registration number and specification of the vessel/vehicle where the MTU concerned is installed. MTU number of mounting, entailing a unique identifier for the said MTU within the relevant CeNA system, being associated with the identification of hardware for the particular PS. MTU subscriber number, each MTU being capable of com¬ prising more than one subscriber number, arranged via one or several selectable SIM cards. The CeNA system mentioned will also utilise certain named system resources for setting-up orders and for analysis of the measurement results collected. The definitions of areas is used both where setting up orders is concerned, as well as effectuating of orders and in the presentation, while map sheet are used in analysing and in presentations. With regard to definitions of areas, the CeNA system will typically work with sub-areas within a measurement area where measurings are performed. These are referred to as geographical areas, and this division is used in order that the operator may be able to carry out differentiated measurings within various sub-areas. For instance, certain problem areas may be given priority higher than where the mobile network functions without problems. The geographical areas are created randomly as polygons which will in turn be defined and named by the operator and also stored in the database management system DBMS for sub¬ sequent reference. The geographical areas are defined from the configuration station CS and may either interactively be defined via the GIS system, or be imported from external tables to the DBMS definitions. The geographical areas may also later on be used during presentations in restricting the result areas presented. The CeNA system described offers a multitude of ways in which the collected measurement results may be viewed and analysed. Measurements recently made or conversations between mobile test units MTU and fixed test units FTU and the operator may be retrieved individually and inspected in every minute detail, while the user for instance monitors correspondingly movements of the mobile test unit MTU, the way this is illustrated in Figures 7 and 9, this being presented on the user's screen by means of a supporting GIS application. Selected conversations which have taken place may be forwarded e.g. to a collector being responsible for merging and distributing data from individual MTU sessions to various DBMS tables thus building and maintaining the background material employed in subsequent generating of long-term statistical presentation. This will in actual fact entail a quantisation procedure, since an exact geographical position is being substituted by one or more parcels, comprising small rectangular regions, also referred to as a mesh, comprising the ori- ginal. An exact point in time is substituted by one or several day periods spanning the original. Exact measure¬ ment data will, depending on the topic concerned, be substituted by accumulable quantities, comprising distribu¬ tion, mean value, median value as well as standard deviation. Each parcel will comprise its own set of these accumulators, making it possible to collect results from a multitude of measuring sessions, and then to regard these results as properties of individual locations rather than random arbitrary events taking place during individual con- versations. It is expedient that the parcels are grouped together in what is referred to as map sheets. In principle, a map sheet is a random rectangular region, subdivided into a grid, to form uniformly shaped parcels. In addition to its geographical boundaries and mesh size, a map sheet will also possess some few properties which determine whether or not it will be affected by incoming measurements forwarded to the collector. Among other things, this will include: identification of network operator; separate map sheets must exist for the various network operators to obviate that measurement data originating from completely different sources contribute to the same accumulators, and one map sheet should not be influenced by data procured from measurements in the network of another operator, time constrains; it is appropriate to make it possible to distinguish between measurement results collected during various periods in the day, as it is well known that a network may perform differently under peak load, e.g. at 3.00 p.m., local time, and provided a map sheet has a time constraint, it will only be affected by measurements procured during the said particular period of time, - on/off; it will be possible to disable a map sheet for a certain period of time, or permanently, and if that is the case, the map sheet will not be affected by incoming measurement results, but it will still be possible to view its contents. Map sheets may overlap, partially or completely, in respect of geometry and any time constrains. If the collector receives measurements emerged at a location which is covered by a multitude of sheets, these will all be affec¬ ted, provided they contain a coordinated network operator identification, and that no other limiting constrains exist. Thus one single report from from a mobile test unit MTU will generally cause more than one accumulator to become updated. The placement and the construction of map sheets entail that the operator is able to make decisions which will greatly affect the behaviour in the CeNA system mentioned earlier, at least as far as post-processing, storage and presentation of results are concerned. Implicitly, these decisions will determine the actual layout of the database management system DBMS, and as such they should be con¬ sidered as the task which should only be performed by the administrator of the CeNA system. For this and similar reasons, the configuration station CS for the CeNA system concerned provides a highly user-friendly tool. Moreover, the operator will be given great flexibility with regard to the description of measurement orders. Each order may be sent to a multitude of mobile test units MTU, and each single mobile test unit MTU may comprise a πrul i- tude of orders. When the MTU concerned has received a set of orders, they will be valid until receipt of a new set. The definition of an order may comprise selecting the fixed test units FTU involved, and also the mobile test unit(s) MTU involved, setting of run-parameters, the measurement qualifiers MQ, as well as time parameters. As far as the run-parameters are concerned, these may com¬ prise: idle time Rx measurements of level to be performed keep data for subsequent renewed attempts in the event that transfer to FTU failed reject measurement on insufficient GPS coverage GPS filter, selection between 2D and 3D navigating as a prerequisite for measurements being made. When the "idle time Rx level measurements" is selected, the relevant mobile test unit MTU will log Rx level measure¬ ments also in an idle modus (not in conversation) . These reports will temporarily be stored in the internal memory of the mobile test unit, and the mobile test unit MTU con- cerned will call a designated fixed test unit FTU for the purpose of updating results at regular intervals. Normally, it will be possible to use the "keep data" option, ensuring that the MTU will retain measurement re¬ sults for subsequent renewed transfer in case one updating of results fails. The option "reject measurements .. " will ensure that no measurements are initiated when there is no GPS coverage, and that measurements in progress will be terminated if coverage drops out for an extended period of time. Built into the present system are also so-called measure¬ ment qualifiers which specify the conditions for carrying out the respective measurements. It entails the following option: - at point in time, where measurements are made within intervals of a given duration between starting and stopping time, - within area, where measurements are made when the mobile test unit MTU concerned enters one of the specified areas, these areas being specified from a geographical list of areas, - on being triggered, where measurements commence when the mobile test unit MTU concerned receives from the spe¬ cified base station BTS and/or carrier frequency, - max. sampling within the area, this parameter re¬ stricting the number of samples being performed in an area (for the time period valid for this measurement order) to the defined number. With the options "at point in time", "within area", and "on being triggered", these will suitably be evaluated as an and-operation, entailing that all qualifiers specified for a measurement order must be met for a call to be initiated. In order to ensure the best adaptation of a measurement order, however, the mobile test unit MTU concerned should always evaluate all measurement orders available and perhaps execute the most important orders compatible with relevant conditions. It should be understood that the said time parameters may specify start and stop for a valid order period, intervals which define maximum measurement frequency, as well as the duration of the call. It should be understood that the geographical area list which is being checked when the command "within area" appears, is very important in order for a measurement order to be initiated. It should furthermore be understood that "on being triggered" entails a specification of the serviced cell BSiC concerned, and its pertaining channel frequency ARFCN which is being used as a condition for performing the measurement, which may mean that if the option "on being triggered" is selected, measurements will only be carried out provided the relevant mobile test unit MTU is being held firmly to a given pair of serviced cell and channel frequency, BSiC/ARFCN, at the time of evaluation. It should furthermore be understood that modes for set-up of measurements may comprise commands for defining a new order, as well as definitions for redefining an existing order, and when a set of measurement orders have been com- plemented, they will be ready to be forwarded to the fixed test units FTU and the mobile test units MTU concerned. It should furthermore be understood that setting up of orders for the fixed test units FTU is in many ways similar to that of the mobile test units but to a limited extent. Mainly, the user will specify the relevant FTU, the MTU(s) to be called, and time-related parameters. Overview of measurements performed When one set of measurement order is defined, the operator can select transmission of the orders to the various mobile test units, the said transmission being done via respective fixed test units FTU, and on receiving confirmation from the fixed test units FTU involved that the orders are new or are to be retained, FTU will start connecting up each defined MTU and transmit the correct order for each of these. On receipt of confirmation from the MTU concerned, a successful measurement order will be stated as having been transmitted, while if the transmission fails, the FTU concerned will repeat the transmission at fixed intervals. The measurement phase will constitute a co-operating operation among the mobile test units MTU involved, the fixed test units FTU and the server CeNAS, entailing that if orders are being communicated, measurements will be made at the mobile test units, and the results sent back via the fixed test units to the server CeNAS to be stored in the database management system DBMS. A measurement phase may comprise the following events: - Receipt of order: when the said MTU is called by the said FTU, the former will start receiving the measurement order and possibly replace any previous order, and thereby con¬ stitute the governing parameters for the said MTU until a new set of orders is received. The said MTU will store the measurement order in a local permanent store which allows renewed reading and start-up of execution of order following a system disconnection or an error in the said MTU to be made. - Measurement qualification: when a set of measurement orders has been established in the MTU, the latter will commence checking the orders for a measurement quali¬ fication, which entails that the respective MTU will check its position, its time and certain trigger parameters, e.g. the serviced cell BSiC and/or the frequency ARFCN for the serviced cell, and concerning adapted start of measurements. - Measurements made: when the FTU concerned has detected an order adaptation, it will commence the various measurements which may comprise: i) Measuring response times: The MTU concerned starts by dialling the number of the subscriber in the FTU concerned and measuring time for setting up the conversation, while at the same time the response time is being logged, ii) Measuring Rx level: the MTU concerned will execute and log measuring of the Rx level of the serving cell and the six strongest non-serving cells, and this information will comprise the Rx level, the serving cell concerned BSiC and pertaining carrier frequency for the serving and the six non-serving cells. iii) Measuring the quality of the signal: quality of signal must be measured and logged, the said infor¬ mation comprising the quality of the signal as defined according to the GSM 0.5.08 for the serving cell frequency. iv) Measuring the timing advance: measuring the timing advance for the serving cell frequency will be measured and logged, v) Signalling information: the system will log layer-1 and layer-3 messages from GSM signalling, messages for both "up-link" and "down-link" being stored, but then relative to frame contents which may be found in other measurement results, vi) Disconnected calls: Any disconnection, either while a call is being set up or of an established connec¬ tion will be stored, and if disconnecting takes place while a call is being set up, the type of disconnection will subsequently be evaluated at the server CeNAS which will distinguish between two types of disconnecting while a call is being set up: 1) disconnecting because the CeNA-FTU was. en¬ gaged, or 2) disconnecting because of system blocking (either GSM or PSTN) . vii) Handover information: the system will obtain all handovers taking place during a call or a conversation and the reason for the handover, see table 10.32 in GSM rec. 04.08, will be stored, iix) Signal to Echo Noise Ratio: this ratio, referred to as S2ENR parameter, described unwanted echo, and the combination of this parameter, quality of signal, Rx quality, and Rx level for the serving cell, describe the quality for the call or the conversation experienced by the user, ix) Measuring at idle time: the operator may specify a measurement order entailing that the MTU concerned will perform measurement at idle time, entailing that the said MTU does not claim access to the network. Only measurement of Rx level will then be performed, while e.g. sampling each 10th to 15th second is generated, after which the log will fill up after a while, and a dump call will be made to the fixed test unit FTU concerned. x) Measuring calls: this measurement order will procure many more data compared with the said measurement at idle time, as a measurement is procured each time a new GPS position occurs, which may e.g. be every second. A measurement will always contain Rx level measurement, signal quality measurement, and measurement of timing advance. The said S2ENR will be present in the measurements at less frequent intervals. Layer-l and layer-3 messages, handover information, time for setting up a call, and any disconnecting will exist in the measurements when occurring. Transmission of results The relevant mobile test unit MTU will start transmission of results to the relevant fixed test unit FTU as soon as a conversation has been established via the said MTU modem. This means that the results will be transmitted simultaneously with new results being obtained or acquired. This entails a transmission of the result more or less in real time. The MTU concerned will, however, hold the line until all data from the measurements have been transferred, even if the parameter for duration of call issued by virtue of the measurement order has expired. This extra time in communication mode should only make up a tiny fraction of the duration of the conversation because of the said transmission done in more or less real time. It is expedient that the communication protocol employed is adaptable with regard to speed. It means that the system will optimise the baud-rate. In case of poor conditions for data transmission, the rate will be reduced, while under good conditions, it will be possible to increase the rate. Any unwanted disconnecting either while a call is being set up or during a conversation, will be logged and stored together with the result "not transferred" to the MTU disc for subsequent transfer, something which does not have to require large storage capacity in the said MTU. Handling of results The server CeNAS previously mentioned is in the present embodiment responsible for handling the measurement results mentioned, i.e. those results received from the mobile test units MTU involved via the fixed test units FTU correspondingly involved and stored and being analysed in the said server. The result handling may be summarised as stated below: Communication of results: upon receipt of measurement results from the said MTU and the said FTU, the incoming data will be "unpacked", the said test units then following a protocol set-up comprising a multitude of ACK and a multitude of NACK with incoming packages. In case a communications line should drop out due to a rejected connection, the mobile test unit MTU will keep the result and complement the result transaction at a later stage. - Storage of results: the server CeNAS will allocate transactions related to the database management system DBMS and commence storing of the result in the said DBMS system. On a successfully implemented completion, the server CeNAS will also complete the transaction, marking it as valid. If the transaction is not implemented in a completely successful manner, the fixed test unit/the server FTU/serv will add the missing result(s) when the mobile test unit MTU completes its transfer of the results. - Analysing the results: the operator may forward results from sessions with selected mobile test units MTU to the result collector in the said cellular network analyser CeNA, the collector, as mentioned above, being made up of a sub-device designed for this purpose. It should be understood that for each single MTU report, all affected map sheets must be detected, based on the exact position of the MTU concerned at the time the measurement was made. Furthermore, updating must be done of the corresponding accumulators, the said updating being related to distribution of results, mean value, median value, and standard deviation. New accumulators will need to be created as required. This procedure is necessary in order that measurement results recently acquired may be able to contribute to network statistics procured and stored by the said CeNA system. Presentation of results The presentation station mentioned, PS, see Figure 1, is used in presenting of measurement results and in generating reports, the station extracting data from the database management station DBMS and presenting the data to the operator in various formats. It is expedient to present these data in two main modes: GIS oriented presentation where the measurement data are presented in relation to geographical position, spreadsheet or mesh-oriented presentation where measurement data are shown in a spreadsheet, while shared geographical presentations, e.g. bars, pie charts and distribution curves are available. The results may be studied in the following ways: - map overviews where the measurement results are being visualised on top of a map of the measurement area, grid overviews where the results are shown in a "grid" similar to a spreadsheet, chart overview where the results are shown as bar charts, line charts or pie charts. What all these presentations have in common is that the operator may prepare criteria for the results to be re¬ trieved. The selecting of criteria is done by choosing a topic, a symbol, and by setting the constraints, and whether this is available, type and form of presentation. When the selecting has been prepared, the system will present the data in the given manner. The said map overview is used in viewing the results re¬ lating to a map of the measurement area. Two types of may views may exist, namely the static overview and the route overview. The static map view is being used in viewing the accumulated results from a variety of measurements, while the route map overview is used in viewing the results from one conversation. To specify further, the static overview is selected for presentation of the contents of map sheets. As mentioned above, a map sheet will comprise a background map, a superimposed mesh, and a set of tables from the database management system DBMS. On starting the presentation station, the user will open one or several set(s) of map sheets, and these will constitute the basis for all static overview presentations performed in that session. To view the accumulated measurement results, a static monitoring selection is defined. Selecting a static overview comprises one or several selection layers. One layer is suitably defined as follows: a theme defining the data to be presented, the said themes to be defined further below, a symbol defining how the data should be presented in the map, a constraint, limiting the data selected for presentation, the said limitations comprising the communicating cell BSiC, the relevant channel frequency ARFCN, geographical area, time spent, and identi¬ fication of operator/user. More particularly, the available themes may include: Rx level, Rx quality Signal to Echo Noise Ratio - Handovers Rate of setting up call. Time to establish connection Blocked calls Rejected calls Shown in Figure 5 is an interaction image on a screen where e.g. the theme Rx level as performed by the mobile test unit MTU concerned may be viewed. Such an observation may be made in each grid of the map sheets, as the Rx level can be represented both the way it is viewed from the serving cell, whether BSiC or ARFCN, and the way it is viewed from any combination of BSiC/ARFCN. The other themes will be stored the way they are viewed from any BSiC and/or ARFCN, and viewed from the basis of the given combinations. All measurements are grouped in accordance with pre-defined boundaries, all being subject to bound rules for presen¬ tation. In the screen image shown in Figure 5, the symbols used for definition of the results can comprise various colour scales, but generally speaking, these symbols may comprise: shadowing, where the cells are in shaded colours accor¬ ding to the values of the result, solid lines where the cells are filled-in in colour according to the values of the result, standard symbols where the cells have been given symbols indicating the value of the result. The constraints which set the limit for selecting results for presentation may comprise as stated above BSiC, ARFCN, time, geographical area, and also operator identification, and it is possible for example, by using a constraint in a selection layer for "blocked calls" for a certain period of time, and another constraint in another layer with the same theme, to compare results from one or several periods against each other. The system may usually be designed so that it is possible to obtain an overview of a variety of layers (usually up to two) in a static overview at the same time. When a static overview is created, the operator will be able to identify, by referring to an area of symbols, the measurement values for the meshes within the area concerned. By altering the themes, symbols and constraints, the operator may readily manipulate the static overviews, enabling him to view the collected results from different angles. A selection aimed at a static overview may be named and stored for subsequent renewed use, and such sets of selec¬ ted overviews may be stored in the database management system DBMS. In Figure 6 is shown a screen image where the static over¬ view grid may be studied in further detail, based on the results in the meshes for the static overview. When the user calls the static overview grid, he will be given a tabular presentation of the field in the static overview meshes concerned. Based on this overview, the user may view the contents of each field in the database management system DBMS which is connected with the meshes, and by selection of the mesh configuration menu it will be pos¬ sible to customise the contents and the set-up of the grid in accordance with the user's specifications. It is also possible to use constraints on the grid to limit the visible DBMS rows, or to display results distributed on BSiC and/or ARFCN. To localise fields from the static overview, the user points to and clicks in the static overview map, and the system will then focus on the corresponding records in the grid, entailing a transition from the screen image according to Figure 5, to the screen image according to Figure 6, or alternatively from the screen image shown in Figure 8 to the screen image shown in Figure 6, and vice versa, and by clicking on a record in the grid, the system will highlight the corresponding mesh pattern in the static overview map, see Figure 5 or Figure 8. Shown in Figures 7 and 9 are screen images which the operator will be able to obtain on his computer system when the operator calls up the function "route overview", which entails a visualisation of results of single conversations, from set-up of a call until disconnecting. To create a selecting list for route overview, it will be possible for the operator to use the function "route list builder". The user may set parameters comprising identification of MTU, time of start and stop, original BSiC and ARFCN, and also to specify the events of which an overview is requested. Based on these systems, the system will present a list of "conversations" from which to select. A selected conversation will then be drawn in the route overview according to results measured along the route, see in particular the heavier line entered in Figures 7 and 9, and by choice among a set of available themes, and these may be accompanied by one or several events to be visualised. In connection with a route map overview as shown in the Figures 7 and 9, the themes may suitably comprise: - Rx level - Rx quality - Time Advance and these themes may be drawn in by means of a colour code or a shading code in accordance with relevant values along the said route. The events which may suitably be associated with a route map overview are as follows: Handover, symbolising handover failure or complete Connection, symbolising where connection established Blocked call - Rejected call Signal to Echo Noise Ratio, symbolising a signal to echo NR level By a combination of themes and events for given conversations, the user may visualise one or several routes simultaneously. It is possible to focus on one or several individual conversations, or to adapt the system to focus on the complete set of conversations. In other words, the route overview grid is being used to study the measurement results for each sampling along a route overview conversation in further detail. When the route overview grid has been launched, the user will have a tabular presentation of the representation fields for each measurement sampling. Using the route overview grid as a point of departure, the user may inspect the content of each field in the database management system DBMS for each conversation. By selecting the grid configuration menu, it will be possible to customise the content and the set-up of the grid in accordance with the wish of the user. To localise fields from the static overview it is possible to point to and click into the route overview map, and the system will then focus on corresponding records in the grid. And vice versa by clicking on a record in the grid, the system will highlight the corresponding "sampling" in the route over¬ view map. It should be understood that the system is also able to present the measurement results collected in the form of chart overviews, mainly graphic views of the grid overview. A screen image with one such graphic representation is shown in Figure 10, but it should be understood that the operator may change the type of diagram and proportions of the representation in various ways, depending on the way in which it is most appropriate to present the data from the grid overview. In Figure 10 is shown an example where the grid overview shows measurements of Rx level in a multitude of serving cells BSiC and a multitude of frequencies ARFCN, the screen image of Figure 10 being capable of showing the result in a Z-grouped bar chart with the Rx level along the Y-axis, the BSiC concerned along the X-axis, and frequencies along the X-axis. The chart overview will show the data of the grid overview in a system defined format at normalisation, and make it possible for the operator to change the presentation in accordance with own wishes. Reporting When the user/operator has an interesting set of maps, grids and chart overviews, the user will normally prepare a report. The report may be drawn up in many different ways, possibly using features related to Windows, as well as others by chosing in accordance with the presentation station of the system, PS. One initial alternative is a so-called map report which may be taken out directly on a printing device, exported to the clipboard or to a file to be included in a document created in a standard Windows package. Typical applications where map reports of the monitored cellular network may be included are Designer, Ami-Pro, MS-Word. It is also possible to import data from other Windows-applications into the map overview to produce a better report. Examples of applications may comprise Designer, Coral Draw, or a report termed Excel Spreadsheet, see further details below. It is possible to use a grid overview and/or chart overview to obtain a report. The operator designs the grid overview and the chart overview as desired, and selects the choice wanted with regard to report format. The presentation station PS will then export the grid overview and the program overview into a report of the Excel Spreadsheet type, start up the said Excel Spreadsheet, and display the finished report. The spreadsheet reports may subsequently be stored for later use, or be used in conjunction with any other Excel spreadsheets, even in places where a CeNA system according to the invention is not installed. The said Excel spreadsheet report may also be entered in the map overview prior to print-out in order thus to provide a more informative report. It should be understood that the system according to the present invention may also comprise a report builder which allows drafting of "customised" reports, for instance in Excel. Both the format and the contents of the report may be determined by the user. A set-up menu, based on familiar network concepts, which is easy to use, can be procured in order to help the user make appropriate decisions, and with a tool as stated, advanced Excel reports may be generated, even if the user has no previous knowledge of Excel. The main choices which may be available in a report builder for retrieval of data may comprise: theme (Rx level, Rx quality, rate of setting up calls etc.) how the data are to be inspected (e.g. as mean value, median value, degree of implementability etc.) "first level" constraint, which specifies the main grouping of the data (e.g. according to cell or to geographical area) "second level" constraint (e.g. operator identification, time, BSiC, ARFCN) , as this allows further grouping of data and also provision of a new dimension in the table. The main choices of format of the report may comprise: type of report (a regular spreadsheet table, an interactive "Pivot Table" etc.) type of graph (pie chart, 3D bar chart etc.) format of number values (e.g. % of a total) In addition to providing tables and graphs via existing data, the user may perform various types of statistical analyses on the data selected. A correlation tool may, for instance, be used to examine for a possible relation between measurements concerning Rx level and Rx quality. The report may be stored as a new, independent report, or it may be added as one or more pages to an already existing report. It is also possible to store the report template in order to use it as a shell when procuring new reports. It should be understood that also static reports may be procured, comprising the absolute values of measurements and reflecting the database management system DBMS at the time when the report was created. The report may be exported to any station and need not be associated with the database management system DBMS. It shall furthermore be understood that also a dynamic report may be chosen, and that such a report, rather than holding the relevant DBMS values, places weight on the corresponding DBMS annotations and when loading, extracts the updated values from the said DBMS. This option is being used in creating periodic reports for a certain interesting subject such as e.g. rejected calls within various cells. In other words, according to the invention a description is given for a system for monitoring telephone networks, in particular cellular networks, based on robots being sent out and into the measurements area, e.g. in vessels/vehicles of private or public type. The said robots have been programmed to receive instructions with specific orders for observation of the quality of parameters which reflect the quality of the services performed in the geographical area concerned which may be covered by one or several cells, and one or several associated base stations. It should be understood that the system may be used chiefly for digital networks, but may also be used for analogous networks or a combination of these by sending out a suitable number of robots programmed accordingly. On the basis of the results communicated by the robots back to their associated base stations and associated main centre, in particular to an open database with suitable user access, the owner of the network will quickly be able to obtain real-time based and statistical data of the quality in the network in order then to take steps to improve it. This may e.g. comprise observation of a base station being poorly or wrongly placed, the possible need for placing out more base stations for improved coverage. Alternatively, the observations may comprise good connection to the base station, but lack of channels between the base station and its associated main centre which should entail upgrading the network to several channels in the area concerned. Furthermore it may be observed with the system according to the invention the real number of handovers from base station to base station along a certain route, as well as the number of successfully completed hand-overs etc. The said robots or mobile test units may be designed approximately resembling a mobile telephone, without a particular power supply, enabling the individual units to take up very little space, and naturally being programmable within a variety of possibilities. The appendix enclosed contains an outline of components and component specifications which may be part of an embodiment of the present invention. APPENDI X CeNA Front-End (FE) : System component definitions, measurement ordering and system status surveillance. HW-requirements : 33 MHz 486 or better 8 Mb Of RAM Minimum 20 Mb of free disk space SW-requirements : MS Windows 3.1 or later MS DOS 6.0 or later CeNA Configuration Station (CS) : Map-sheet definitions and handling. Definition of geographical areas. Storage handling, back-up and disposal of old data. HW-require ents : 33 MHz 486 or better 8 Mb of RAM Minimum 20 Mb of free disk space SW-requirements : MS Windows 3.1 or later MS DOS 6.0 or later CeNA Presentation Station (PS) : Result presentation and report building. HW-requirements : 66 MHz 486 or better 12 Mb Of RAM Minimum 20 Mb of free disk space _ SW-requirements: MS Windows 3.1 or later MS DOS 6.0 or later Graphics 1280 x 1024 with 256 colourdrive CeNA Server (CeNAS) : Handle outgoing and incoming DBMS traffic to FTUs. System statistics. HW-requiremen s: HP-700 series workstation, or 800 series Server Sufficient RAM and disk capacity SW - requi re ent s : HP/UX 9 . 0 or later Sybase . . , . . or -other DBMS system may be used upon request CeNA Fixed Test Unit (FTU) : Performing measurement. Make calls to MTUs. Receive calls from MTUs. Hardware configuration: CPU: Intel 486 50 MHz DX2 Memory: 4 MB upgradable to 16MB Storage: 50 MB disk, upgradable to 500 MB PSTN lines: 5 lines, upgradable to 20 Extern comms: Ethernet interface Software configuration: Built self-test and runtime software. Upgradable by download from CeNA Server. CeNA Mobil e Tes t Uni t (MTU) : Performing measurement . Make calls to FTUs . Receive calls from FTUs . Hardware conf iguratio CPU: Intel 386 33 MHz SX Memory: l MB, upgradable Storage: l MB PCMCIA disk, upgradable to 100 MB Test MS: Built in Orbitel 901 Test MS Modem: Built in ... modem Navigation Built in Rockwell .. GPS, Dead reckoning: Optionally connection for ... DR system Extern comms: Serial line for external connection. Software configuration: Built self-test and runtime software. Upgradable by change of PCMCIA card.

Claims: P a t e n t C l a i m s 1. A system for monitoring telephone networks and/or data communication networks, especially cellular mobile telephone networks (CeN) , c h a r a c t e r i s e d i n that the system (CeNA) comprises one or several fixed and/or mobile units (MTU, FTU) , referred to here as field units or test units, the said units comprising organs for observation of quality, communicating with an operator of the network (CeN, BTS, PSTN) . 2. A system as stated in claim l, c h a r a c t e r i s e d i n the fixed units (FTU) being placed in a geographical pattern, and the mobile test units (MTU) being mounted into vessels/vehicles which move about in the network concerned (CeN, BST, MSC, PSTN) , especially in selected areas of the network. 3. A system as stated in claim l or 2, c h a r a c t e r i s e d i n that the communication between the field units (MTU, FTU) and the network operator takes place via the network concerned (CeN, MSC, PSTN) and preferably virtually in real-time. 4. A system as stated in one of the claims 1-3, c h a r a c t e r i s e d i n that the said communication takes place through reporting during certain intervals of time or by temporary local logging of analysis data for subsequent communication. 5. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that the system (CeNA) comprises an interface (CU) between the network operator and the field units (FTU, MTU) , the said interface allowing the organs in the individual units which observe quality to be set in accordance with particular requirements from the operator, e.g. basic setting, report interval, maintenance, access level etc. 6. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that the system (CeNA) comprises an open database (DBMS) where the data from observations of quality from the various units (FTU, MTU) are stored and processed, e.g. for analysing and for graphical presentation of the quality of the network in selected geographical areas, statistics, as well as for transport of information to other applications. 7. A system as stated in claim 6, c h a r a c t e r i s e d i n that the open database (DBMS) communicates with other similar open databases, and that the system (CeNA) as such communicates via the same open network (TCP/IP) . 8. A system as stated in claim 7, c h a r a c t e r i s e d i n that the mobile units (MTU) which comprise quality observation organs, communicate with the fixed units (FTU) , and that the said quality observation organs may comprise a built-in micro computer, a test mobile, a positioning system (GPS) and communication equipment etc. 9. A system as stated in claim 8, c h a r a c t e r i s e d i n that the fixed units (FTU) communicate with the mobile units (MTU) preferably via a special modem and via a cellular telephone network, and with the operator/user via a preferably open network (TCP/IP) . 10. A system as stated in claim 9, c h a r a c t e r i s e d i n that the mobile units (MTU) are equipped to receive changes in observation program or measurement ordering, optionally temporary storage of quality observations in their own store, as well as organs for communication of the said observations to an operator via the fixed units (FTU) . 11. A system as stated in claim 9 or 10, c h a r a c t e r i s e d i n that the substantially open network (TCP/IP) enables connection of components via LAN, WAN, fixed, dial-up lines or ISDN. 12. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that the database (DBMS) communicates with data processing organs which can be handled by the operator, for quality observation data received and stored, which allows analysing of larger or smaller geographical areas, so-called measurement areas, as well as smaller sub-areas and regions thereof, a geographical position being definable by smaller mesh- shaped parcels. 13. A system as stated in claim 12, c h a r a c t e r i s e d i n that the parcels are . grouped together as map sheets which are sub- ivided by means of a grid. 14. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that the quality observation organs of the mobile units (MTU) are equipped to carry out one or several of the following measurements: - Rx level Rx level Signal to Echo Noise ratio Handovers Time for establishing connection, rate of call set-up - Blocked calls Failed calls Failed handovers, as well as storing, updating and transmitting the said measurements via the fixed units (FTU) . 15. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that the said quality observation measurements are presented for visualised inspection in the form of: map sheets, either as statistical overviews of accumulated measurements or as a route overview for a mobile conversation, grid overview chart overview. 16. A system as stated in claim 15, c h a r a c t e r i s e d i n that the presentation in the form of a route overview entails building up a route list, for instance comprising: identification of a selected mobile unit (MTU) with associated identification, - time for starting and stopping original cell (BSiC) and cellular network (CeN/ARFCN) available themes, for instance Rx level, Rx quality, time schedule, events which are to be part of the analysis, e.g. completed or non-completed handovers, establishing of connection, blocked call, rejected call, signal to echo noise ratio, the presentation being shown in legible symbols, e.g. colours, lines, shade of grey etc. 17. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that one or several of the mobile units are arranged in a private car, a service car, a bus or coach, a tram or a train, the units (MTU) being arranged for unattended, automatic operation, and the units (MTU) being capable of performing the same functions as a mobile telephone, yet performed with the said additional quality observation organs and without a particular power supply. 18. A system as stated in any one of the preceding claims, c h a r a c t e r i s e d i n that the system may be used for analogous networks, digital networks, and also for networks comprising wholly or in part a combination of these, e.g. NMT network and GSM network, optionally with two different mobile units in the same vessel/vehicle.

Inventors: DAHL ERIK, LUNDE IVAR, DAHL, ERIK, LUNDE, IVAR
Applicants: DAHL ERIK, ERICSSON AS, LUNDE IVAR, DAHL, ERIK, ERICSSON A/S, LUNDE, IVAR
Application year: 1995
Main classification: H04Q7
IPC codes: H04M3, H04W16, H04W24