WO2007076668A1 - Système, dispositif, et procédé pour effectuer une maintenance de fonctionnement sur un dispositif de réseau - Google Patents

Système, dispositif, et procédé pour effectuer une maintenance de fonctionnement sur un dispositif de réseau Download PDF

Info

Publication number
WO2007076668A1
WO2007076668A1 PCT/CN2006/002741 CN2006002741W WO2007076668A1 WO 2007076668 A1 WO2007076668 A1 WO 2007076668A1 CN 2006002741 W CN2006002741 W CN 2006002741W WO 2007076668 A1 WO2007076668 A1 WO 2007076668A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
network device
record
layer
detailed
Prior art date
Application number
PCT/CN2006/002741
Other languages
English (en)
French (fr)
Inventor
Dongjun Wu
Hui Wang
Yujie Chen
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to CNA2006800122248A priority Critical patent/CN101160803A/zh
Publication of WO2007076668A1 publication Critical patent/WO2007076668A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/53—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP using mediation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/59—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/2218—Call detail recording
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/24—Arrangements for supervision, monitoring or testing with provision for checking the normal operation
    • H04M3/241—Arrangements for supervision, monitoring or testing with provision for checking the normal operation for stored program controlled exchanges
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0062—Provisions for network management
    • H04Q3/0087—Network testing or monitoring arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/12—Counting circuits
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/36—Memories
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0164—Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0172—Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0188—Network monitoring; statistics on usage on called/calling number
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/22—Arrangements for supervision, monitoring or testing
    • H04M3/24—Arrangements for supervision, monitoring or testing with provision for checking the normal operation
    • H04M3/247—Knowledge-based maintenance systems

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a system, device and method for implementing network device operation and maintenance. Background of the invention
  • the methods for implementing network equipment operation and maintenance mainly include the following steps:
  • Step 1 The operator creates measurement tasks in the GUI (graphics user interface), such as setting the granularity period, measuring objects, measuring indicators, time, and so on.
  • the created task is directly sent to the network device, and the network device performs the calculation of the performance index of the measurement according to the measurement task it receives.
  • Step 2 Each relevant data collection point reports the data that meets the requirements to the NE OM (network element operation and maintenance) or EM (element management) according to the measurement task. The data that does not meet the requirements is not reported.
  • Step 3 The NE OM or the EM generates a measurement result for each measurement task according to the data received by the NE, or the performance measurement result, and saves the measurement result in a file or a database, or reports the measurement result to the GUI network management system, or The NMS queries the NE OM/EM for the measurement result of the specified task.
  • Step 4 When the end time of the measurement task is reached, or the operator deletes the measurement task, Each relevant data collection point stops reporting data to NE OM or EM.
  • the present invention provides a system, device, and method for implementing network equipment operation and maintenance, so that the operation and maintenance process can be flexibly realized, and the operation and maintenance management is more comprehensive.
  • a method for implementing operation and maintenance of a network device is applied to a network including a device layer and a preprocessing layer, where the method includes: • a network device in the device layer acquires a detailed call record during a call, and records the call in detail Transfer to the pre-processing layer;
  • the pre-processing layer performs operation and maintenance management on the network device according to the detailed record of the call it receives.
  • a network device which acquires a detailed record of a call during a call, and transmits the detailed record of the call to the pre-processing device, including:
  • Obtaining a call detail record module configured to acquire the call detail record, and send the call detail record to the transmission module;
  • a pretreatment device comprising:
  • the statistics module is configured to perform performance measurement index statistics on the detailed call records sent by the network device.
  • a system for implementing operation and maintenance of a network device comprising a device layer and a pre-processing layer, wherein the device layer is composed of at least one network device, the pre-processing layer is composed of a pre-processing device; and the network device acquires a detailed call record during a call And transmitting the detailed call record to the pre-processing device, and the pre-processing device filters the detailed record of the call to implement centralized operation and maintenance management of the network device.
  • the network device further outputs the original call information of the call, and the special pre-processing layer performs operation and maintenance management on the network device according to the call information, such as performing performance measurement index statistics, failure log analysis, etc., thereby
  • the operation and maintenance management processes such as call and performance measurement statistics are separated from each other, so that the functions of the network device are simplified, so that the operation of the network device is more stable; the preprocessing layer in the present invention can obtain the detailed record data of the original call, so that the performance The operation and maintenance management process such as measurement index statistics can be flexibly implemented and more comprehensive.
  • the pre-processing layer performs operation and maintenance management such as new performance measurement index statistics.
  • the code running in the network device is not required to be modified, so that the present invention can quickly respond to the operation and maintenance management such as new performance measurement indicators; the preprocessing layer in the present invention filters by using object filtering, service attribute filtering, and performance measurement indicators. Over The preprocessing layer can support more measurement objects, ensuring the collection integrity of the call information, and further ensuring that the preprocessing layer can perform comprehensive performance measurement and maintenance statistics and other operation and maintenance management; the preprocessing layer in the present invention can be based on The call information transmitted by the network device is used to perform performance measurement metrics for a single call of a single user, so that the pre-processing layer can provide the specific status of each call, thereby quickly and accurately solving the problem of single-call failure; The detailed record data of the call is generated for each call and transmitted to the pre-processing layer, so that when new resources are used When calling, the information of the newly added resources is automatically reflected in the CDR to achieve adaptive measurement. Therefore, the technical solution provided by the present invention improves the monitorability of the entire network and the operational maintain
  • FIG. 1 is a schematic diagram of a network device operation and maintenance system according to an embodiment of the present invention
  • FIG. 2 is a flowchart 1 for implementing a network device operation and maintenance method according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram of a network device operation and maintenance method according to an embodiment of the present invention
  • FIG. 4 is a flowchart 3 of a method for implementing operation and maintenance of a network device according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method for implementing operation and maintenance of a network device according to an embodiment of the present invention
  • FIG. FIG. 5 is a flowchart of a method for implementing operation and maintenance of a network device according to an embodiment of the present invention.
  • each network device in the device layer of the network acquires a detailed record of the call in the call, and transmits the call detail record to a pre-processing layer independent of the existence of the network device, and the pre-processing layer according to the call details received by the pre-processing layer Records the operation and maintenance management of each network device in a centralized manner to obtain performance measurement indicators of network devices.
  • the system for implementing operation and maintenance of a network device of the present invention is as shown in FIG.
  • the system for implementing network device operation and maintenance provided by the embodiment of the present invention is mainly completed by two parts, one part is a device layer, and the other part is a pre-processing layer.
  • the device layer is composed of at least one network device, where the network device can be various host devices, network element devices, etc.; in particular, in the Internet Protocol (IP) multimedia subsystem In the (IP Multimedia Subsystem, IMS) product, the network device may be a Proxy Call Session Control Function (P-CSCF) entity, a Serving CSCF (S-CSCF) entity, and a media gateway control function (Media). Gateway Control Function (MGCF) entity, Exit Out Gateway Control Function (BGCF) entity, etc.
  • the pre-processing layer may be a Performance Data Server (PDS) or other dedicated pre-processing device. As is apparent from Fig. 1, the device layer and the pretreatment layer are independent.
  • PDS Performance Data Server
  • Each network device in the device layer records the call detail record data of the call.
  • the original call detail record data can be referred to as a Call Detail Record (CDR).
  • CDR Call Detail Record
  • Each network device transmits the CDR information to the PDS, and the PDS collects statistics on the CDRs received by the PDS to obtain performance measurement indicators that need to be measured.
  • the system of the present invention may further comprise: a post-analysis layer and a presentation presentation layer comprising at least one client.
  • the post-analysis layer re-analyzes the operation and maintenance management information such as the performance measurement indicators output by the pre-processing layer, and the processing result of the post-analysis layer is output or displayed by the client that presents the presentation layer.
  • the present invention does not limit the post-analytical processing in the post-analytical layer, i.e., the post-analytical layer in the present invention can be implemented using the existing post-analytical processing method.
  • Post-analysis layers include, but are not limited to, element management system (EMS), grid management system
  • NMS network management system
  • network optimization system etc.
  • the network device needs to output CDR information for each call.
  • the CDR information includes detailed information during a call.
  • the information in the CDR includes but is not limited to the following: 1.
  • the calling side here refers to the one of the internal processing of the switch and the signaling message related to the calling party.
  • the called side refers to the side of the switch that processes the signaling messages related to the called party.
  • the related data of the signaling message sending and receiving bit table of the calling/called party in the call includes: the sending and receiving of the standard signaling message in a call, such as whether a standard signaling message in the call has been received or has been sent.
  • the standard signaling message here includes: a transceiving signaling message in the softswitch, a transceiving signaling message in the IMS, and the like.
  • Signaling and receiving signaling messages in the softswitch such as SETUP, Initial Address Message IAM, ALERTING, CONNECT, CONNECT ACK, and RELEASE messages Messages; Transceiver signaling messages in CSCF such as request (INVITE), 183, PRACK, 180, 200 and other signaling messages.
  • Each standard signaling message in the call is sent and received with a corresponding time value, and the network device records the time of receipt and/or the time of issuance of these standard signaling messages.
  • the network device can record: the time when the calling service is requested, that is, the time when the calling side receives the SET UP signaling message, and the time when the called service requests the called side sends the SET UP signaling message, and the called ringing time is When the called side receives the ALERTING message, the called response time is the time when the called side receives the CONECT signaling message and the call end time.
  • the object information corresponding to the call is the object information in the call that can perform performance measurement index statistics.
  • the object information corresponding to the call includes but is not limited to one or more of the following: a calling/called user number of the call, a calling/called port number, an incoming relay, and an outgoing relay.
  • the service attribute information corresponding to the call includes but is not limited to one or more of the following contents: The main/called side access type of the call, the call type of the call, such as an incoming call, an outgoing call or a tandem call, etc., the connection type of the call, such as domestic long distance, international long distance, local call, etc., the intelligent service logo of the call, the supplementary of the call Service sign, the type of service carried by the call, such as voice, video, data, fax, etc., the reason for the failure of the call, the audio and video coding method of the call, and so on.
  • the types of CDRs generated by the network device include, but are not limited to, one or more of the following: a traffic termination CDR, a traffic failure CDR, a traffic synchronization CDR, and a supplementary service CDR.
  • the CDR recorded and generated by the network device is the traffic termination CDR; if the call fails before the response, the CDR recorded and generated by the network device is the traffic failure CDR; If related supplementary services occur, it is necessary to generate supplementary service CDRs to perform statistics related to various supplementary services, such as statistics of performance measurement indicators for forward destinations; to ensure performance measurement indicators in a statistical period
  • the data is absolutely correct.
  • the network device needs to periodically generate the traffic synchronization CDR, and transmit the detailed call record with the active end of the cycle to the pre-processing layer, so that the PDS can accurately calculate the traffic volume and various times in one cycle. Performance measures such as number of calls.
  • the network device can record the call detail record during the call. Recording the call detail record can be achieved through the set process, that is, setting the corresponding field in the CDR.
  • the acquiring call detailed record module may include a traffic abort sub-module, a traffic failure sub-module, a supplementary service sub-module, and a traffic synchronization sub-module, respectively, for recording and generating the foregoing CDR.
  • the above functions of transmitting the CDR, the traffic failure CDR, the supplementary service CDR, and the traffic synchronization CDR to the pre-processing layer are performed by the transmission module.
  • the network device can also periodically generate a timestamp CDR, where the timestamp CDR includes the current time of the network device, that is, the network device periodically writes the current time of the system, so that the pre-processing layer can accurately calculate the performance measurement index.
  • the CDR and transmitted to the PDS, W If the network device transmits the timestamp CDR to the PDS every minute, so that the pre-processing layer can accurately distinguish the CDR information generated by the network device at different times.
  • the function of generating the timestamp CDR is performed by the timestamp module in the network device. At this time, the transmission module also needs to transmit the timestamp CDR generated by the timestamp module to the preprocessing layer.
  • the network device can transmit the CDR information generated by the network device to the PDS by means of active reporting, that is, the network device can report the CDR information immediately after the CDR information is generated.
  • the network device can also transmit the CDR information generated by the network device to the PDS by means of passive reporting, that is, the network device.
  • the storage generates CDR information, and when the PDS requests the CDR information from the network device, the network device transmits the stored CDR information to the PDS.
  • the information contained in the CDRs generated by the network device can be flexibly set according to actual needs, that is, the degree of detail of the information in the CDR can be flexibly changed.
  • the traffic measurement of some links, the performance measurement of some circuit groups can be left in the host for the management, and then the data in one cycle is transmitted to the PDS by means of timing generation of non-traffic CDRs.
  • some field information may also be added to the traffic class CDR, such as adding some link object information, adding a message traffic field for these link objects, etc., so that the link traffic and the like are included in the traffic class CDR transmission.
  • the PDS can obtain information about how many control messages, how many control messages, and so on are received by the link object during the call through the traffic class CDR.
  • the PDS performs centralized analysis and calculation on the CDRs transmitted by the network device, and can also obtain operation and maintenance management information such as performance measurement index values of the link object and the like in one cycle.
  • both call 1 and call 2 are cross-cycle calls.
  • the network device needs to generate a traffic synchronization CDR for call 2 at the end of cycle 0 (10:05), at the end of cycle 1 (10:10).
  • the two cross-cycle calls generate a traffic synchronization CDR, and each traffic synchronization CDR reflects the state of a call at the end of the cycle. If call 1 and call If the call 2 is a normal end, the network device also needs to generate a call termination CDR for the two cross-cycle calls when the call 1 and the call 2 are normally ended.
  • the CDR generated by the network device includes: The traffic synchronization CDR generated for call 2 at 10:05, at 10 : 10 times for the traffic synchronization CDR generated by call 1 and call 2 respectively, generating a traffic termination CDR or traffic failure CDR for call 2 at 10:11, and generating a traffic termination CDR or traffic for call 1 at 10:12 Failure CDR.
  • the network device can generate and transmit CDR information to the PDS in real time according to the failure, termination, and supplementary service generation of each call.
  • the network device can also generate and transmit CDR information to the PDS according to a predetermined periodic timing. . That is, if the call ends within the period, the network device needs to generate and transmit a traffic termination CDR, or a traffic failure CDR, or a supplementary service CDR in real time; if the call is a cross-cycle call, the network device needs to The periodic point reports the call details of the call at the cycle point.
  • the network device can ensure that the CDR information is generated and transmitted for each call in a period, so that the PDS performs the integrity of the basic data of operation and maintenance management such as performance measurement index statistics, thereby It ensures the accuracy of operation and maintenance management information such as PDS statistical performance measurement indicators.
  • the PDS focuses on the operation and maintenance management process.
  • the PDS needs to perform performance measurement metrics on the CDR information transmitted by the network device.
  • the performance measurement indicators are different according to the requirements.
  • the PDS may not filter the CDR information transmitted by the network device, and directly perform performance measurement index statistics.
  • the preset filtering criteria filter the CDR information transmitted by the network device. For example, when counting the calling number of a call, there is no need to filter the CDR information transmitted by the network device. In the process of performing most performance measurement statistics, the PDS needs to be transmitted to the network device.
  • the CDR information is filtered, and then the performance measurement index statistics are performed according to the CDR information that meets the filtering condition, and finally the performance measurement index information is calculated.
  • the performance measurement statistic process performed by the PDS mainly includes a filtering process and a performance measurement index calculation process, wherein the filter condition is stored in the filter condition storage module in the PDS.
  • the filtering process may include: any one of the object information filtering process corresponding to the call, the service attribute information filtering process corresponding to the call, and the filtering process of the performance measurement indicator, or any two or three are included at the same time.
  • the present invention does not limit the order of filtering, for example, the object information filtering process corresponding to the call may be performed first, and then the service attribute information filtering process corresponding to the call may be performed; or the service attribute information filtering process corresponding to the call may be performed first, and then the call is performed.
  • Corresponding object information filtering processing When the filtering process includes the above three filtering processes, the order of the three filtering processes can be adjusted any.
  • the CDR reported by the network device contains the object information corresponding to the call.
  • the object information corresponding to the call includes the calling/called number of the call, the calling/called port number, the incoming and outgoing trunks, the incoming office direction, the outgoing office direction, and the master/called CENTREX group.
  • the object information of the entire measurement system that needs to be calculated by the performance measurement index is stored.
  • the object information can be stored in the object filter storage sub-module in the filter condition storage module, and the object information stored on the PDS side can be sent by the network management system. It can also be the default object information it supports.
  • the object filter includes the object filtering storage sub-module and the filtering module in the present invention, and the object filter determines whether the object information in the CDR transmitted by the network device can match the object that the PDS needs to perform performance measurement index statistics.
  • the match is successful, it indicates that the call corresponding to the CDR is a call that is of interest to the PDS, and the performance measurement indicator of the object that matches the success is calculated for the CDR; if the match is unsuccessful, the call corresponding to the CDR is not filtered by the object, and the call is not a PDS. For a call of interest, there is no need to calculate a performance metric object indicator for the corresponding object for the CDR.
  • the setting of the PDS needs to calculate the outgoing traffic of the office route 2, the office route 3, and the office route 4, and the call corresponding to the CDR reported by the network device is the office route 2, so that the object filtering process determines the
  • the call corresponding to the CDR is a call that is concerned by the PDS, and the PDS needs to calculate the relevant performance measurement indicator of the office route 2 according to the call detail record in the CDR; if the call corresponding to a certain CDR reported by the network device is the office route 5, because The PDS only needs to calculate the outgoing call traffic of office route 2, office route 3, and office route 4.
  • the call corresponding to the CDR is not a call that is of interest to the PDS, and the PDS does not need to be based on the call in the CDR.
  • Detailed records calculate the relevant performance measures for the corresponding object.
  • the CDR information reported by the network device includes service attribute information corresponding to a call.
  • the service attribute information includes the primary/called side access type of the call, the intelligent service indicator of the call, the supplementary service indicator, the type of the bearer service of the call, and the type of the bearer service of the call, such as voice or video.
  • the PDS side stores the service attribute information that the entire measurement system needs to perform the performance measurement index calculation.
  • the service attribute information may be stored in the service attribute filter storage sub-module in the filter condition storage module, and the service attribute information stored on the PDS side may be It is delivered by the NMS, or it can be the default service attribute information it supports.
  • the filtering conditions in the present invention include object filtering and service attribute filtering, after filtering by the object in FIG. 3, a set of objects that need to participate in the performance measurement index statistics is obtained, and each object that needs to participate in the performance measurement index statistics corresponds to A set of ontology with the business attributes of the call.
  • the ontology with the same call service attribute can be organized into a performance measurement unit.
  • the call service attribute can be "calling is 2G access", and the subject whose caller is 2G access is organized into a performance measurement unit.
  • the measurement unit may include the number of trial calls for which the calling party is 2G access, the occupied call traffic for which the calling party is 2G access, and the response traffic volume for which the calling party is 2G access; the call service attribute may be " The calling party is 3G access, and the calling party is organized into another performance measuring unit.
  • the performance measuring unit may include the number of trial calls for the 3G access, and the calling party is the 3G access terminal. Call traffic, the caller is the body of the 3G access response traffic. But no matter how it is organized, the office's ontology collection of this object reflects a variety of call service attributes.
  • the ontology of the object in the PDS performance measurement system may reflect various service attributes.
  • the service attribute may be that the calling party is 2G access, or the calling party may be 3G. Access.
  • the service attribute is fixed.
  • the access type service attribute in the above example is either 2G, 3G, or other forms in the CDR corresponding to a call.
  • the PDS needs to filter the service attribute information of the call detailed record.
  • the business attribute filtering process is as shown in FIG.
  • the service attribute filter includes the service attribute filtering storage sub-module and the filtering module in the present invention, and the service attribute filter determines whether the service attribute information in the CDR filtered by the object can be compared with the service attribute in the performance measuring unit. If the match is successful, it indicates that the call corresponding to the CDR is a call that is of interest to the PDS. The performance measurement indicator of the object and the service attribute of the match is calculated for the CDR. If the match is unsuccessful, the CDR pair is displayed. The incoming call is not filtered by the service attribute. The call is not a call that is of interest to the PDS. The performance measurement indicator object indicator of the corresponding object and service attribute is not required to be calculated for the CDR.
  • the indicators that need to be measured include: The number of call attempts, the number of times of the call, the number of times of the call, the number of times of the call, the number of times of the call, the number of calls, the number of calls, the number of calls Call traffic and answer traffic; these 7 ontology constitute a 2G call traffic measurement unit.
  • the indicators that need to perform performance measurement may also include: the number of trial calls, the number of occupations, the number of times of connection, the number of responses, the amount of occupied traffic, the amount of received traffic, and the amount of answered traffic for the 3G access;
  • the ontology constitutes a 3G call traffic measurement unit.
  • the access type of the calling side is 2G, so that the number of trial calls, the number of occupations, the number of times of connection, the number of responses, the amount of traffic occupied by the calling party for 3G access,
  • the service attributes of the QoS and response traffic are unsuccessful, and the 3G utterance measurement unit does not need to be updated, that is, the information in the CDR does not need to participate in the performance measurement of the 3G utterance measurement unit. statistics.
  • the caller is the number of trial calls, the number of occupations, the number of connections, the number of responses, the amount of traffic, the amount of incoming calls, and the amount of response traffic, and the call service attributes in the CDR information match.
  • the 2G outgoing traffic measurement unit needs to be updated, that is, the information in the CDR needs to participate in the statistics of the performance measurement indicators of the 2G outgoing traffic measurement unit.
  • the CDR information reported by the network device includes the receiving and receiving of the signaling messages corresponding to the call and the time points corresponding to the signaling messages.
  • the information in the CDR may include: the calling side receives the SET UP message, and the corresponding calling side service request time; the called side receives the ACM message, the corresponding called ringing time; the called side receives To the CONNECT message, the corresponding called response time, and so on.
  • the signaling message in the CDR information transmitted by the network device is the call flow.
  • Some key signaling messages in the process can determine the current state of the call, which determines the performance measurement indicators that need to be updated, and also determines the current state of the call.
  • Statistical performance metrics are required. This process is a performance measurement metric filtering process. For example, if the calling side receives the SET UP message, the metric to be updated is the number of trial calls. If the called party receives the ACM message, the metric to be updated is the number of times to be connected. Call traffic; If the called party receives the CONNECT message, the indicator that needs to be updated is the number of responses, the performance measurement indicators that need to be counted are the response traffic, and so on.
  • the filtering module determines, according to the corresponding relationship between the performance measurement index and the call detail record that affects the indicator, each performance measurement indicator that needs to be stored in the storage attribute of the service attribute filtering sub-module, and determines a signaling message that affects the indicator. Then, the performance measurement index is updated according to the sending and receiving of the signaling message in the CDR. The correspondence between the performance measurement indicator and the call detail record affecting the indicator is stored in the performance measurement indicator filter ⁇ "store module.
  • the performance measurement index filtering process will be described below with reference to FIG. 6 through a specific example.
  • the CDR information includes the setting information of the SET UP message received by the calling side, and the PDS updates the number of trial calls in the performance measurement indicator according to the CDR; If the side receives the ACM message, the CDR information includes the set information of the ACM message received by the called side, and the PDS updates the number of times of the connection in the performance measurement indicator according to the CDR, and calculates the received traffic amount; Upon receiving the CONNECT message, the CDR information includes the set information of the CONNECT message received by the called side, and the PDS updates the number of responses in the performance measurement indicator according to the CDR, and calculates the response traffic.
  • the entity in the performance measurement unit obtained after the object information filtering and the service attribute filtering is called the 2G access, and the call of the office direction is 2 Can measure indicators: number of trial calls, number of occupations, number of connections, number of responses, traffic usage, call volume, and response traffic.
  • the ontology obtained by object information filtering and service attribute filtering is not the ontology that needs to update the performance measurement index.
  • the PDS also needs to send and receive signaling messages according to the CDR, that is, the signaling message in the call flow. Judging by the situation.
  • the primary/called side signaling message in the CDR information transmitted by the network device is set as follows: The calling side receives the SET UP message, the called side sends the IAM message, and the called side receives the ACM.
  • the main body that the PDS needs to update is: the number of trial calls, the number of occupations, the amount of traffic occupied, the number of connections, and the amount of incoming calls. Since the CDR information of the call indicates that the called side does not receive the CONNECT, the PDS does not need to update the response number and the response traffic.
  • performance measurement indicators that ultimately need to be updated are obtained, and the PDS updates the performance measurement indicators according to the number of times or by using a calculation formula.
  • the caller is the number of trial calls, the number of occupations, the number of times of connection, and the number of responses for 2G access.
  • the update of performance indicators of these ontology is achieved by direct accumulation of numbers.
  • the occupational traffic measurement, the incoming call traffic, and the response traffic volume are updated by the standard calculation formula.
  • the response traffic volume can be calculated by the formula (the called response time) - Call start time) The cycle is obtained.
  • the performance measurement indicator when updated, it is necessary to determine the time. For example, when updating the occupancy count, it is necessary to determine whether the relay occupation time is within the current period. As shown in FIG. 7, the relay occupation time of the inter-cycle call 1 is in the cycle 1, since the PDS has accumulated statistics on the number of relay occupations according to the information in the traffic synchronization CDR generated by the network device at the cycle point 10:10. Therefore, for the traffic termination CDR generated by the call 1 in the period 2, the PDS cannot re-accumulate the number of relay occupations according to the information in the termination CDR of the traffic.
  • the inter-cycle call 2 relay occupancy time is in cycle 0, since the PDS has The statistics of the number of relay occupations are accumulated according to the information in the traffic synchronization CDR generated by the network device at the cycle point 10:05, so, for the call 2, the traffic synchronization CDR and the period 2 in the 10:10 minute If the CDR is terminated, the PDS can no longer count the number of times the relay is occupied.
  • the PDS needs to make the same judgment when updating the performance measurement indicators such as the number of trial calls, the number of connections, the number of responses, the amount of traffic, the amount of incoming calls, and the amount of response traffic.
  • the description of the pre-processing layer in the above embodiment is described by taking the performance measurement index statistics as an example to describe the processing of the failure log.
  • the processing of the call failure log is implemented by the log module and the log analysis module, and the detection module is mainly used to utilize the network.
  • the detailed record of the call transmitted by the device establishes and stores the log information of the call failure.
  • the log processing module is mainly used for performing log analysis processing of the call failure of the log information stored by the log module. Since the content of the operation and maintenance management of the network device is very rich, it will not be enumerated in this embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Monitoring And Testing Of Exchanges (AREA)
  • Telephonic Communication Services (AREA)

Description

一种实现网络设备运行维护的系统、 设备及方法
技术领域
本发明涉及网络通讯技术领域， 具体涉及一种实现网络设备运行维 护的系统、 设备及方法。 发明背景
随着网络的演进以及网络功能的完善， 网络设备的竟争重点已逐渐 转向了运行维护功能方面。 运营商需要了解网络的性能状况， 需要实现 性能监控、性能问题隔离和定位、性能趋势预测、分析 VIP用户的行为， 以及针对用户投诉分析失败原因等功能。
目前， 实现网络设备运行维护的方法主要包括如下步驟：
步驟 1、 操作员在 GUI ( graphics user interface, 图形用户界面） 中 创建测量任务， 如设置粒度周期， 测量对象， 测量指标， 时间等。 创建 的任务直接下发到网络设备中， 网络设备根据其接收的测量任务进行测 量性能指标的打点计算。
步驟 2、 各个相关数据采集点根据测量任务向 NE OM ( network element operation and maintenance , 网元运行维护) 或 EM ( element management, 网元管理）上报符合要求的数据， 不符合要求的数据不上 报。
步骤 3、 NE OM或 EM根据其接收到的数据为每一个测量任务分别 生成测量结果， 即性能测量结果，并将测量结果保存在文件或数据库中， 或者将测量结果上报到 GUI网管， 或者由网管向 NE OM/EM查询指定 任务的测量结果。
步驟 4、 当达到测量任务的结束时间， 或操作员删除了测量任务后， 各个相关数据采集点停止向 NE OM或 EM上报数据。
通过上述描述可知， 在目前的实现网络设备运行维护的方法中， 如 果在网络设备执行测量任务过程中新增了资源， 即使该新增的资源符合 某个测量任务指定的条件， 也不能自动包含在该测量任务中， 不能做到 自适应测量； 由于该方法需要先建立测量任务， 所以， 测量任务中没有 的指标， 就收集不到相应的指标数据， 使该方法难以支持事后分析； 由 于性能测量指标在网络设备内统计， 所以， 系统不能提供针对单次呼叫 的性能测量指标统计。 发明内容
有鉴于此， 本发明提供一种了实现网络设备运行维护的系统、 设备 及方法， 从而使运行维护过程能够灵活实现， 运行维护管理更加全面。
本发明提供的具体技术方案是：
一种实现网络设备运行维护的方法， 应用于包括设备层和预处理层 的网絡中， 该方法包括： . 设备层中的网络设备获取呼叫过程中的呼叫详细记录， 并将所述呼 叫详细记录传输至预处理层；
预处理层根据其接收到的呼叫详细记录对网络设备进行运行维护管 理。
一种网络设备， 获取呼叫过程中的呼叫详细记录， 并将所述呼叫详 细记录传输至预处理设备， 包括：
获取呼叫详细记录模块， 用于获取所述呼叫详细记录， 并且将所述 呼叫详细记录发送给传输模块；
传输模块， 用于将获取呼叫详细记录模块获取的呼叫详细记录传输 至所述预处理设备。 一种预处理设备， 包括：
统计模块， 用于对网络设备发来的呼叫详细记录进行性能测量指标 统计。
一种实现网络设备运行维护的系统， 包括设备层和预处理层， 其中 设备层由至少一台网络设备构成， 所述预处理层由预处理设备构成； 网絡设备获取呼叫过程中的呼叫详细记录， 并将呼叫详细记录传输 至预处理设备， 预处理设备对所述呼叫详细记录进行过滤处理， 实现对 网络设备的集中运行维护管理。
采用本发明提供的技术方案，网络设 ^又输出呼叫的原始呼叫信息， 由专门的预处理层根据呼叫信息对网络设备进行运行维护管理， 如进行 性能测量指标统计、 失败日志分析等， 从而使呼叫与性能测量指标统计 等运行维护管理过程相互分离， 使网络设备的功能单一化， 从而使网絡 设备的运行更加稳定； 本发明中的预处理层能够获取到原始呼叫的详细 记录数据， 使性能测量指标统计等运行维护管理过程能够灵活实现， 并 且更加全面等； 而且， 当网络设备传输的呼叫信息包含呼叫过程详细信 息时， 预处理层即使进行新的性能测量指标统计等运行维护管理， 也不 需要对网络设备中运行的代码进行修改， 使本发明能够对新的性能测量 指标等运行维护管理进行快速响应； 本发明中的预处理层通过采用对象 过滤、 业务属性过滤、 性能测量指标过滤过程， 使预处理层能够支持更 多的测量对象， 保证了呼叫信息的收集完整性， 进一步保证了预处理层 能够进行全面的性能测量指标统计等运行维护管理； 本发明中的预处理 层能够根据网络设备传输来的呼叫信息， 针对单个用户的单次呼叫进行 性能测量指标统计， 使预处理层能够提供每次呼叫的具体状况， 从而能 够快速准确的解决单次呼叫的故障问题； 由于网絡设备会针对每个呼叫 产生并向预处理层传输呼叫的详细记录数据， 这样， 当新增资源被用于 呼叫时， 新增资源的信息会自动体现在 CDR中， 从而实现自适应测量。 因此， 通过本发明提供的技术方案， 提高了整个网络的可监控性以及网 络设备的可运行维护性。 附图简要说明
图 1是本发明实施例的实现网络设备运行维护系统的示意图； 图 2是本发明实施例的实现网络设备运行维护方法的流程图一； 图 3是本发明实施例的实现网络设备运行维护方法的流程图二； 图 4是本发明实施例的实现网络设备运行维护方法的流程图三； 图 5是本发明实施例的实现网络设备运行维护方法的流程图四； 图 6是本发明实施例的实现网絡设备运行维护方法的流程图五； 图 Ί是本发明实施例的实现网络设备运行维护方法的流程图六。 实施本发明的方式
本发明的核心思想是： 网络的设备层中的各网络设备获取呼叫中的 呼叫详细记录， 并将呼叫详细记录传输至独立于网络设备存在的预处理 层， 预处理层根据其接收的呼叫详细记录对各网络设备集中进行运行维 护管理， 以获得网络设备的性能测量指标等。
下面基于本发明的核心思想、 结合附图对本发明提供的实现网络设 备运行维护的系统、 设备及方法做进一步的描述。
本发明的实现网络设备运行维护的系统如附图 1所示。
图 1中， 本发明实施例提供的实现网络设备运行维护的系统主要由 两部分协作完成， 一部分是设备层， 另一部分是预处理层。 所述设备层 由至少一个网络设备组成， 这里的网絡设备可以为各种主机设备， 网元 设备等； 特别的， 在互联网协议（Internet Protocol, IP ) 多媒体子系统 ( IP Multimedia Subsystem, IMS )产品中， 网络设备可以是代理呼叫会 话控制功能（Proxy Call Session Control Function, P-CSCF ) 实体， 服务 CSCF( Serving CSCF, S-CSCF )实体，媒体网关控制功能（ Media Gateway Control Function, MGCF )实体， 出口网关控制功能（ Breakout Gateway Control Function, BGCF ) 实体等。 所述预处理层可以为性能数据服务 器（Performance Data Server, PDS )或其他专用预处理设备。 从图 1中 可以明显看出， 设备层与预处理层是独立存在的。
设备层中的各网络设备记录呼叫原始的呼叫详细记录数据， 在本实 施例中可以将原始的呼叫详细记录数据称之为呼叫详细记录（ Call Detail Record, CDR )。 各网絡设备将 CDR信息传输至 PDS, 由 PDS对其接收 的各个 CDR集中进行统计， 以获得其需要测量的性能测量指标。
本发明的系统还可以进一步包括： 后分析层和包括至少一个客户端 的呈现表示层。 后分析层对预处理层输出的性能测量指标等运行维护管 理信息进行再次分析处理， 后分析层的处理结果由呈现表示层的客户端 输出或显示。 本发明不限制后分析层中的后分析处理过程， 即本发明中 的后分析层可以采用现有的后分析处理方法来实现。 后分析层包括但不 限于网元管理系统（ element management system , EMS )， 网格管理系统
( network management system , NMS ) , 网络优化系统等。 分别进行说明。
―、 网络设备输出 CDR信息的过程。
网络设备需要针对每个呼叫均输出 CDR信息。 CDR信息中包括了 一个呼叫过程中的详细信息。 CDR中的信息包括但不限于如下内容： 1、 呼叫中主 /被叫侧的信令消息收发位表的相关数据。
这里的主叫侧是指交换机内部处理和主叫相关的信令消息的那一 侧 , 被叫侧是指交换机内部处理和被叫相关的信令消息的那一侧。 呼叫中主 /被叫侧的信令消息收发位表的相关数据包括：一个呼叫中 的标准信令消息的收发情况， 如呼叫中的某个标准信令消息是否已经收 到了或者是否已经发出了。 这里的标准信令消息包括： 软交换中的收发 信令消息、 IMS中的收发信令消息等。 软交换中的收发信令消息如建立 ( SETUP ) , 初始地址消息 （Initial Address Message IAM ) , 振铃 ( ALERTING ), 连接（CONNECT ), 连接应答（CONNECT ACK )和 释放（RELEASE ) 消息等信令消息； CSCF 中的收发信令消息如请求 ( INVITE ), 183 , PRACK, 180, 200等信令消息。
2、 呼叫中的标准信令消息的收到 /发出时刻信息。
呼叫中每个标准信令消息的收发都会有一个对应的时间值， 网络设 备记录这些标准信令消息的收到时刻和 /或发出时刻。 例如， 网络设备可 以记录： 主叫业务请求时刻即主叫侧收到 SET UP信令消息的时刻， 被 叫业务请求时刻即被叫侧发出 SET UP信令消息的时刻， 被叫振铃时刻 即被叫侧收到 ALERTING 消息的时刻， 被叫应答时刻即被叫侧收到 CONECT信令消息的时刻以及通话结束时刻等。
3、 呼叫对应的对象信息。
呼叫对应的对象信息即呼叫中能够进行性能测量指标统计的对象信 息。 例如在软交换中， 呼叫对应的对象信息包括但不限于下述内容中的 一种或多种： 呼叫的主 /被叫用户号码、 主 /被叫端口号、 入中继和出中 继的电路号、入中继和出中继的类型、 入局与出局局向号、 主 /被叫的虚 拟用户交换机 ( CENTREX )群号、 主 /被叫的专用分组交换机 ( PBX ) 群号等等。
4、 呼叫对应的业务属性信息。
呼叫对应的业务属性信息包括但不限于下述内容中的一种或多种： 呼叫的主 /被叫侧接入类型， 呼叫的呼叫类型如入局呼叫、 出局呼叫或汇 接呼叫等， 呼叫的接续类型如国内长途、 国际长途、 市话等， 呼叫的智 能业务标志， 呼叫的补充业务标志，呼叫的承载业务类型如语音、视频、 数据、 传真等， 呼叫的失败原因， 呼叫的音频视频编码方式等等。
网络设备产生的 CDR种类包括但不限于下述内容的一种或多种：话 务终止 CDR, 话务失败 CDR, 话务同步 CDR以及补充业务 CDR。
如果该呼叫正常结束或者在通话过程中异常结束， 则网络设备记录 并生成的 CDR为话务终止 CDR; 如果该呼叫在应答之前失败， 则网络 设备记录并生成的 CDR为话务失败 CDR; 如果有相关补充业务发生， 则需要生成补充业务 CDR, 以便进行各种补充业务相关的统计， 如针对 前转目的地的性能测量指标的统计等; 为了保证在一个统计周期内统计 的性能测量指标的数据绝对正确 , 网络设备需要周期性的产生话务同步 CDR, 将周期结束时刻处于活动状态的呼叫详细记录传输至预处理层， 以便使 PDS 可以准确地计算一个周期内的话务量和各种呼叫次数等性 能测量指标。 网络设备可以在呼叫过程中记录呼叫详细记录， 记录呼叫 详细记录可以通过置位过程来实现， 即对 CDR中的相应字段进行设置。
上述记录并生成话务终止 CDR、 话务失败 CDR、 补充业务 CDR以 及话务同步 CDR的功能由网络设备中的获取呼叫详细记录模块来完成。 对应的， 所述获取呼叫详细记录模块可以包括话务中止子模块， 话务失 败子模块， 补充业务子模块以及话务同步子模块， 分别用于记录并生成 上述 CDR。 上述将话务终止 CDR、 话务失败 CDR、 补充业务 CDR、 话 务同步 CDR传输至预处理层的功能由传输模块来完成。
为了使预处理层便于对性能测量指标进行准确统计， 网络设备还可 以周期性的产生时间戳 CDR， 时间戳 CDR中包含有网络设备的当前时 间， 即网络设备周期性的将系统当前时间写入 CDR中， 并传输至 PDS, W 如网络设备每分钟向 PDS传输一次时间戳 CDR, 以使预处理层能够准 确区分网络设备在不同时刻产生的 CDR信息。 生成时间戳 CDR的功能 由网絡设备中的时间戳模块来完成， 此时， 传输模块还需要将时间戳模 块生成的时间戳 CDR传输至预处理层。
网络设备可以采用主动上报的方式将其产生的 CDR信息传输至 PDS, 即网络设备产生 CDR信息后立即上报； 网络设备也可以采用被动 上报的方式将其产生的 CDR信息传输至 PDS, 即网絡设备存储其产生 CDR信息， 在 PDS向网絡设备请求 CDR信息时， 网絡设备才将其存储 的 CDR信息传输至 PDS。
网络设备产生的 CDR中包含的信息可根据实际需要进行灵活设置， 即 CDR 中的信息详细程度是可以灵活变化的。 例如， 可以把一些链路 的流量测量， 一些电路群的性能测量继续留在主机进行打点， 然后， 采 用定时产生非话务类 CDR的方式将一个周期内的数据传输至 PDS。 当 然， 也可以在话务类 CDR中增加一些字段信息， 如增加一些链路对象 信息、 增加针对这些链路对象的消息流量字段等， 使链路的流量等信息 包含在话务类 CDR中传输至 PDS, 从而使 PDS能够通过话务类 CDR 获得一个呼叫过程中， 此链路对象发送了多少控制消息， 收到了多少控 制消息等信息。 PDS通过对网络设备传输来的 CDR进行集中分析计算， 也能够获得链路对象等在一个周期内的性能测量指标值等运行维护管 理信息。
下面结合附图 2对网络设备产生不同种类的 CDR的过程进行说明。 图 2中， 呼叫 1和呼叫 2均为跨周期呼叫， 网络设备需要在周期 0 的结束时刻 （ 10 :05 ) 为呼叫 2生成话务同步 CDR, 在周期 1的结束时 刻 （10 :10 ) 为这两个跨周期呼叫分别生成话务同步 CDR, 每个话务同 步 CDR反映某呼叫在该周期的结束时刻所处的状态。 如果呼叫 1和呼 叫 2均为正常结束， 则网络设备还需要在呼叫 1和呼叫 2正常结束时， 为这两个跨周期呼叫分别生成呼叫终止 CDR。
假设呼叫 1的结束或失败时刻为 10 :12, 呼叫 2的结束或失败时刻 为 10 :11 , 则网络设备生成的 CDR包括： 在 10 :05时刻为呼叫 2生成的 话务同步 CDR, 在 10 :10时刻为呼叫 1和呼叫 2分别生成的话务同步 CDR,在 10 :11为呼叫 2生成话务终止 CDR或话务失败 CDR,在 10 :12 为呼叫 1生成话务终止 CDR或话务失败 CDR。
从上述描述可以看出， 网络设备可以根据每个呼叫的失败、 终止及 补充业务的产生情况实时产生并向 PDS传输 CDR信息， 同时， 网络设 备还可以根据预定周期定时产生并向 PDS传输 CDR信息。 也就是说， 如果呼叫在周期内就结束了， 则网络设备需要实时产生并传输话务终止 CDR、 或者话务失败 CDR、 或者补充业务 CDR; 如果呼叫是跨周期的 呼叫， 则网络设备需要在周期点上报这个呼叫在该周期点的呼叫详细信 息。 通过各种 CDR信息的生成和传输， 可以保证网络设备为一个周期 内的每个呼叫都生成并传输了 CDR信息， 使 PDS进行性能测量指标统 计等运行维护管理的基础数据的完整性高，从而保证了 PDS统计性能测 量指标等运行维护管理信息的准确性。
二、 PDS集中进行运行维护管理过程。
下面以性能测量指标统计过程为例进行说明。
PDS需要对网络设备传输来的 CDR信息进行性能测量指标统计， 才艮据需要进行性能测量指标的不同， PDS 可以不对网絡设备传输来的 CDR信息进行过滤， 直接进行性能测量指标统计， 也可以按照预先设定 的过滤准则对网络设备传输来的 CDR信息进行过滤。 例如在统计呼叫 的主叫号码时， 就不需要对网络设备传输来的 CDR信息过滤。 而在进 行大多数的性能测量指标统计过程中， PDS 需要对网络设备传输来的 CDR信息进行过滤， 然后， 根据符合过滤条件的 CDR信息进行性能测 量指标统计， 最终计算出性能测量指标信息。 当需要进行过滤处理时， PDS进行的性能测量指标统计过程主要包括过滤处理过程和性能测量指 标计算过程， 其中过滤条件存储于 PDS中的过滤条件存储模块中。
过滤处理过程可以包括： 呼叫对应的对象信息过滤处理、 呼叫对应 的业务属性信息过滤处理和性能测量指标的过滤处理过程中的任意一 种、 或者任意两种、 或者三种同时都包括。 而且， 本发明不限制过滤的 先后顺序， 如可以先进行呼叫对应的对象信息过滤处理， 再进行呼叫对 应的业务属性信息过滤处理； 也可以先进行呼叫对应的业务属性信息过 滤处理， 再进行呼叫对应的对象信息过滤处理。 当过滤处理过程同时包 括上述三种过滤处理过程时， 这三种过滤处理过程的先后顺序可以任何 调整。
下面对这三种过滤处理过程分别进行描述。
1、 呼叫对应的对象信息过滤处理。
网络设备上报的 CDR中包含呼叫对应的对象信息。呼叫对应的对象 信息包括该呼叫的主 /被叫号码、 主 /被叫端口号、 入中继和出中继、 入 局局向、 出局局向、 主 /被叫 CENTREX群等。
PDS 侧存储有整个测量系统需要进行性能测量指标计算的对象信 息 , 这里的对象信息可以存储于过滤条件存储模块中的对象过滤存储子 模块中， 而且， PDS侧存储的对象信息可以是网管下发的， 也可以是其 支持的默认对象信息。
由于 PDS侧存有整个测量系统需要进行性能测量指标统计的所有对 象信息， 而网络设备传输来的每张 CDR 中仅包含与这个呼叫相关的一 些对象信息， 因此， 需要对 CDR进行对象过滤， 对象过滤过程如附图 3 所示。 图 3中， 对象过滤器中包含有本发明中的对象过滤存储子模块和过 滤模块， 对象过滤器判断网络设备传输来的 CDR中的对象信息是否能 够和 PDS需要进行性能测量指标统计的对象匹配， 如果匹配成功，表明 CDR对应的呼叫是 PDS关心的呼叫 ,需要针对该 CDR计算匹配成功的 对象的性能测量指标； 如果匹配不成功， 则表明 CDR对应的呼叫没有 通过对象过滤， 该呼叫不是 PDS关心的呼叫， 不需要针对该 CDR计算 相应对象的性能测量指标对象指标。
下面通过一个具体的例子例一进行说明。
设定 PDS需要计算局向 2, 局向 3 , 局向 4的发话出局话务量， 而 网络设备上报的一张 CDR对应的呼叫是局向 2的发话， 这样， 通过对 象过滤过程， 确定该 CDR对应的呼叫是 PDS关心的呼叫， PDS需要根 据该 CDR中的呼叫详细记录计算局向 2的相关的性能测量指标； 如果 网络设备上报的某张 CDR对应的呼叫是局向 5的发话， 由于 PDS只需 要计算局向 2， 局向 3, 局向 4的发话出局话务量， 所以， 通过对象过 滤过程， 确定该 CDR对应的呼叫不是 PDS关心的呼叫， PDS不需要根 据该 CDR中的呼叫详细记录计算相应对象的相关的性能测量指标。
2、 呼叫对应的业务属性过滤处理。
网络设备上报的 CDR信息中包含一个呼叫对应的业务属性信息。业 务属性信息包括呼叫的主 /被叫侧接入类型， 呼叫的智能业务标志， 补充 业务标志， 呼叫的承载业务类型等， 以及呼叫的承载业务类型如语音或 视频等。
PDS侧存储有整个测量系统需要进行性能测量指标计算的业务属性 信息， 这里的业务属性信息可以存储于过滤条件存储模块中的业务属性 过滤存储子模块中， 而且， PDS侧存储的业务属性信息可以是网管下发 的， 也可以是其支持的默认业务属性信息。 如果本发明中的过滤条件包括对象过滤和业务属性过滤， 则通过上 述图 3的对象过滤后， 会得到一个需要参加性能测量指标统计的对象集 合， 每个需要参加性能测量指标统计的对象会对应一组本体， 这些本体 中带有呼叫的业务属性。 带有相同呼叫业务属性的本体可以组织成性能 测量单元的形式， 如呼叫业务属性可以是 "主叫为 2G接入"， 则主叫为 2G接入的本体组织成一个性能测量单元， 这个性能测量单元中可以包 括主叫为 2G接入的试呼叫次数、主叫为 2G接入的占用接通话务量以及 主叫为 2G接入的应答话务量等本体； 呼叫业务属性可以是 "主叫为 3G 接入"， 则主叫为 3G接入的本体组织成另一个性能测量单元， 这个性能 测量单元可以包括主叫为 3G接入的试呼次数，主叫为 3G接入的接通话 务量， 主叫为 3G接入的应答话务量等本体。 但是不管以什么方式组织， 局向这个对象的本体集合反映出了多种呼叫业务属性。
可见， PDS性能测量系统中的对象需要测量的本体可能体现出多种 业务属性， 例如， 同样是试呼叫次数这个本体， 其业务属性可能是主叫 为 2G接入， 也可能是主叫为 3G接入。 而对于主机上报的一个呼叫的 CDR来说， 其业务属性是固定的， 如上述例子中的接入类型业务属性， 在一个呼叫对应的 CDR中要么是 2G, 要么是 3G, 或者是其他形式， 但是， 绝对不会出现又是 2G接入， 又是 3G接入的现象。 这样 PDS就 需要对呼叫详细记录进行业务属性信息的过滤。 业务属性过滤过程如附 图 4所示。
图 4中， 业务属性过滤器中包含有本发明中的业务属性过滤存储子 模块和过滤模块， 业务属性过滤器判断对象过滤后的 CDR中的业务属 性信息是否能够和性能测量单元中的业务属性匹配， 如果匹配成功， 表 明 CDR对应的呼叫是 PDS关心的呼叫，需要针对该 CDR计算匹配成功 的对象、 业务属性的性能测量指标； 如果匹配不成功， 则表明 CDR对 应的呼叫没有通过业务属性过滤，该呼叫不是 PDS关心的呼叫， 不需要 针对该 CDR计算相应对象、 业务属性的性能测量指标对象指标。
下面通过一个具体的例子例二进行说明。
设定针对软交换中的局向对象， 需要进行性能测量的指标包括： 该 局向的主叫为 2G接入的试呼次数、 占用次数、 接通次数、 应答次数、 占用话务量、 接通话务量和应答话务量； 这 7个本体组成 2G发话话务 测量单元。 需要进行性能测量的指标还可以包括： 主叫为 3G接入的试 呼次数、 占用次数、 接通次数、 应答次数、 占用话务量、 接通话务量和 应答话务量； 这 7个本体组成 3G发话话务测量单元。 而网络设备上报 的一个呼叫的 CDR信息中， 主叫侧接入类型为 2G, 这样， 对于主叫为 3G接入的试呼次数、 占用次数、 接通次数、 应答次数、 占用话务量、 接通话务量和应答话务量这几个指标业务属性匹配不成功， 3G发话话 务测量单元不需要进行更新，即 CDR中的信息不需要参加 3G发话话务 测量单元的性能测量指标的统计。 而主叫为 2G接入的试呼次数、 占用 次数、 接通次数、 应答次数、 占用话务量、 接通话务量和应答话务量这 几个指标和 CDR信息中的呼叫业务属性匹配成功 , 2G发话话务测量单 元需要进行更新，即 CDR中的信息需要参加 2G发话话务测量单元的性 能测量指标的统计。
3、 性能测量指标的过滤
网络设备上报的 CDR信息中包含有一个呼叫对应的信令消息的收 发情况和这些信令消息收发对应的时刻点。针对某个呼叫， CDR中的信 息可以包括： 主叫侧收到了 SET UP消息，对应的主叫侧业务请求时刻； 被叫侧收到了 ACM消息，对应的被叫振铃时刻；被叫侧收到 CONNECT 消息， 对应的被叫应答时刻等等。
由于网络设备传输来的 CDR信息中的信令消息收发情况是呼叫流 程中的一些关键信令消息， 根据这些信令消息的收发情况， 可以判断出 当前呼叫所处的状态， 也就决定了需要更新的性能测量指标， 同时也决 定了呼叫所处的当前状态下需要进行统计的性能测量指标， 这个过程就 是性能测量指标过滤过程。 例如， 如果主叫侧收到了 SET UP消息， 则 需要更新的指标为试呼次数； 如果被叫侧收到了 ACM消息， 则需要更 新的指标为接通次数， 需要进行统计的性能测量指标为接通话务量； 如 果被叫侧收到 CONNECT消息， 则需要更新的指标为应答次数， 需要进 行统计的性能测量指标为和应答话务量， 等等。
性能测量指标的过滤过程如附图 5所示。 图 5中， 过滤模块根据性 能测量指标与影响该指标的呼叫详细记录的对应关系， 针对业务属性过 滤存储子模块中存储的需要进行统计的每一个性能测量指标， 确定影响 该指标的信令消息， 然后根据 CDR 中的信令消息的收发情况进行性能 测量指标的更新。 所述性能测量指标与影响该指标的呼叫详细记录之间 的对应关系存储在性能测量指标过滤^ "储子模块中。
下面结合附图 6、 通过具体的例子对性能测量指标过滤过程进行说 明。
图 6中， 如果主叫侧收到了 SET UP消息， 则 CDR信息中会包括主 叫侧收到 SET UP消息的置位信息 , PDS根据该 CDR更新性能测量指标 中的试呼次数； 如果被叫侧收到了 ACM消息， 则 CDR信息中会包括被 叫侧收到了 ACM消息的置位信息， PDS根据该 CDR更新性能测量指标 中的接通次数， 并计算接通话务量； 如果被叫侧收到 CONNECT消息， 则 CDR信息中会包括被叫侧收到 CONNECT消息的置位信息， PDS根 据该 CDR更新性能测量指标中的应答次数， 并计算应答话务量。
结合例一和例二的情况， 经过对象信息过滤和业务属性过滤后得到 的性能测量单元中的本体为主叫为 2G接入， 局向为 2的呼叫的以下性 能测量指标： 试呼次数、 占用次数、接通次数、 应答次数、 占用话务量、 接通话务量和应答话务量。 但是， 通过了对象信息过滤和业务属性过滤 得到的本体， 并不是最终需要进行性能测量指标更新的本体， PDS还需 要根据 CDR 中的信令消息的收发情况， 即呼叫流程中的信令消息置位 情况来判断。 假设网络设备传输来的 CDR信息中的主 /被叫侧信令消息 置位情况为： 主叫侧收到了 SET UP消息， 被叫侧发出了 IAM消息， 被 叫侧收到了 ACM。 这样， PDS需要更新的本体为： 试呼次数、 占用次 数、 占用话务量、 接通次数和接通话务量。 由于该呼叫的 CDR信息中 表明，被叫侧没有收到 CONNECT, 因此 PDS不需要更新应答次数和应 答话务量。
通过上述各个过滤过程后， 得到了最终需要更新计算的性能测量指 标， PDS根据次数累加或利用计算公式等方法对性能测量指标进行更新。 例如在上述针对软交换的一个局向对象的例子中， 主叫为 2G接入的试 呼次数、 占用次数、 接通次数和应答次数， 这些本体的性能测量指标的 更新是通过直接次数累加实现的； 而占用话务量、 接通话务量和应答话 务量， 这些本体的性能测量指标的更新是通过标准的计算公式计算获得 的， 例如应答话务量可以通过公式（被叫应答时刻 -呼叫起始时刻） ÷周期获得。
需要说明的是， 在上述性能测量指标进行更新时， 需要判断一下时 间， 例如在更新占用次数时， 需要判断中继占用时刻是否在本周期内。 如图 7中，跨周期呼叫 1的中继占用时刻在周期 1内， 由于 PDS已经根 据网络设备在周期点 10 :10产生的话务同步 CDR中的信息对中继占用 次数进行了累加统计，所以，针对呼叫 1在周期 2产生的话务终止 CDR, PDS就不能根据该话务终止 CDR中的信息对中继占用次数进行再次累 加统计。 同理， 跨周期呼叫 2的中继占用时刻在周期 0内， 由于 PDS已 经根据网络设备在周期点 10 :05产生的话务同步 CDR中的信息对中继 占用次数进行了累加统计，所以，针对呼叫 2在 10 :10分的话务同步 CDR 和周期 2内的话务终止 CDR, PDS均不能再对中继占用次数进行累加统 计。
同样的道理， PDS在对试呼次数、 接通次数、 应答次数、 占用话务 量、 接通话务量和应答话务量等性能测量指标进行更新时， 也需要进行 同样的判断。
上述实施例对预处理层的描述是以性能测量指标统计为例进行描述 叫失败日志的处理等， 对呼叫失败日志的处理由日志模块和日志分析模 块来实现， 曰志模块主要用于利用网络设备传输来的呼叫详细记录建立 并存储呼叫失败的日志信息， 日志处理模块主要用于对日志模块存储的 日志信息进行呼叫失败的日志分析处理。 由于对网络设备进行运行维护 管理包含的内容非常丰富， 在本实施例中不再一一列举。
总之， 以上所述仅为本发明的较佳实施例而已 , 并非用于限定本发 明的保护范围。 凡在本发明的精神和原则之内， 所作的任何修改、 等同 替换、 改进等， 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、一种实现网络设备运行维护的方法， 其特征在于， 网絡中包括设 备层和预处理层， 该方法包括：
设备层中的网络设备获取呼叫过程中的呼叫详细记录， 并将所述呼 叫详细记录传输至预处理层；
预处理层根据其接收到的呼叫详细记录对网络设备进行运行维护管 理。
2、根据权利要求 1所述的方法， 其特征在于， 所述呼叫中的呼叫详 细记录包括下述内容的至少一个：
表示呼叫中的标准信令消息收发情况的主 /被叫侧的消息收发位表 相关数据； 和
呼叫中的标准信令消息的收到 /发出时刻信息； 和
呼叫对应的对象信息； 和
呼叫对应的业务属性信息。
3、根据权利要求 1所述的方法， 其特征在于， 所述设备层中的网络 设备获取呼叫过程中的呼叫详细记录为：
网络设备获取正常结束的呼叫中的呼叫详细记录； 或
网络设备获取异常结束的呼叫中的呼叫详细记录； 或
网絡设备获取在应答之前失败的呼叫中的呼叫详细记录； 或 网络设备获取发生的补充业务的呼叫详细记录； 或
网络设备定时获取处于活动状态的呼叫中的呼叫详细记录。
4、根据权利要求 2或 3所述的方法， 其特征在于， 所述设备层中的 网络设备获取呼叫过程中的呼叫详细记录， 并将所述呼叫详细记录传输 至预处理层进一步包括： 网絡设备定时获取网络设备当前的时刻信息 , 并传输至预处理层。
5、根据权利要求 1所述的方法， 其特征在于， 所述预处理层根据其 接收到的呼叫详细记录对网络设备进行运行维护管理为：
预处理层艮据呼叫详细记录进行性能测量指标统计。
6、根据权利要求 1所述的方法， 其特征在于， 所述预处理层根据呼 叫详细记录进行性能测量指标统计之前进一步包括：
预处理层根据其存储的过滤条件对其接收的'呼叫详细记录进行过 滤， 获得影响性能测量指标统计结果的呼叫详细记录；
所述才艮据呼叫详细记录进行性能测量指标统计为：
才艮据影响性能测量指标统计结果的呼叫详细记录进行性能测量指标 统计。
7、根据权利要求 6所述的方法， 其特征在于， 所述过滤条件包括下 列过滤条件中的至少一个：
呼叫对象过滤条件， 和业务属性过滤条件， 和性能测量指标过滤条 件；
所述性能测量指标过滤条件为：
需要进行统计的性能测量指标与呼叫详细记录之间的对应关系， 所 述呼叫详细记录为影响该需要进行统计的性能测量指标的统计结果的 呼叫详细记录。
8、根据权利要求 1所述的方法， 其特征在于， 所述预处理层根据其 接收到的呼叫详细记录对网络设备进行运行维护管理为：
预处理层根据其接收的呼叫详细记录建立呼叫失败的日志信息， 并 根据日志信息进行呼叫失败的曰志分析处理。
9、根据权利要求 1或 2所述的方法， 其特征在于， 所述网络中进一 步包括连接到预处理层的后分析层， 该方法进一步包括： 预处理层将预处理结果数据传输至后分析层；
后分析层对其接收的预处理结果数据进行后分析处理。
10、 根据权利要求 9所述的方法， 其特征在于， 所述网络中进一步 包括连接到后分析层的呈现表示层， 该方法进一步包括：
后分析层的处理结果由呈现表示层输出或显示。
11、 一种网络设备， 其特征在于， 所述网絡设备获取呼叫过程中的 呼叫详细记录， 并将所述呼叫详细记录传输至预处理设备， 包括： 获取呼叫详细记录模块， 用于获取所述呼叫详细记录， 并且将所述 呼叫详细记录发送给传输模块；
传输模块， 用于将获取呼叫详细记录模块获取的呼叫详细记录传输 至所述预处理设备。
12、根据权利要求 11所述的网絡设备， 其特征在于， 所述获取呼叫 详细记录模块包括以下子模块中的至少一个：
话务中止子模块， 用于获取正常 /异常结束的呼叫中的呼叫详细记 录， 并且将所述呼叫详细记录发送给传输模块； 和
话务失败子模块， 用于获取在应答之前失败的呼叫中的呼叫详细记 录， 并且将所述呼叫详细记录发送给传输模块； 和
补充业务子模块， 用于获取发生的补充业务的呼叫详细记录， 并且 将所述呼叫详细记录发送给传输模块； 和
话务同步子模块， 用于定时获取处于活动状态的呼叫中的呼叫详细 记录， 并且将所述呼叫详细记录发送给传输模块。
13、根据权利要求 12所述的网络设备， 其特征在于， 所述网络设备 中进一步包括：
时间戳模块， 用于定时获取网络设备当前的时刻信息， 并传输至预 处理设备。
14、 一种预处理设备， 其特征在于， 所述预处理设备包括： 统计模块， 用于对网络设备发来的呼叫详细记录进行性能测量指标 统计。
15、根据权利要求 14所述的预处理设备， 其特征在于， 所述预处理 设备进一步包括：
过滤条件存储模块，用于存储对呼叫详细记录进行过滤的过滤条件； 过滤模块， 用于根据过滤条件存储模块中存储的过滤条件对预处理 设备接收到的呼叫详细记录进行过滤， 获得影响性能测量指标统计结果 的呼叫详细记录， 并将影响性能测量指标统计结果的呼叫详细记录传输 至统计模块。
16、根据权利要求 15所述的预处理设备， 其特征在于， 所述过滤条 件存储模块包括下列子模块中的至少一个：
对象过滤存储子模块， 用于存储需要进行性能测量指标统计的呼叫 对象信息； 和
业务属性过滤存储子模块， 用于存储需要进行性能测量指标统计的 呼叫业务属性信息； 和
性能测量指标过滤存储子模块， 用于存储需要进行统计的性能测量 指标与影响其统计结果的呼叫详细记录的对应关系。
17、 根据权利要求 14、 15或 16所述的预处理设备， 其特征在于， 所述预处理设备进一步包括：
曰志模块， 用于根据预处理设备接收的呼叫详细记录建立呼叫失败 的日志信息；
日志分析模块， 用于对日志模块中存储的日志信息进行呼叫失败的 日志分析处理。
18、 一种实现网络设备运行维护的系统， 其特征在于， 该系统包括 设备层和预处理层， 其中设备层由至少一台网络设备构成， 所述预处理 层由预处理设备构成；
网络设备获取呼叫过程中的呼叫详细记录， 并将呼叫详细记录传输 至预处理设备， 预处理设备对所述呼叫详细记录进行过滤处理， 实现对 网络设备的集中运行维护管理。
19、根据权利要求 18所述的系统， 其特征在于， 所述系统进一步包 括：
后分析层， 对预处理层输出的预处理结果数据进行后分析处理。
20、 根据权利要求 19所述的系统， 其特征在于， 所述后分析层为： 网元管理系统 EMS， 或网络管理系统 NMS, 或网给优化系统。
PCT/CN2006/002741 2005-12-30 2006-10-17 Système, dispositif, et procédé pour effectuer une maintenance de fonctionnement sur un dispositif de réseau WO2007076668A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNA2006800122248A CN101160803A (zh) 2005-12-30 2006-10-17 一种实现网络设备运行维护的系统、设备及方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA2005101374671A CN1992752A (zh) 2005-12-30 2005-12-30 一种实现网络设备运行维护的系统、方法及网络设备
CN200510137467.1 2005-12-30

Publications (1)

Publication Number Publication Date
WO2007076668A1 true WO2007076668A1 (fr) 2007-07-12

Family

ID=37898521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/002741 WO2007076668A1 (fr) 2005-12-30 2006-10-17 Système, dispositif, et procédé pour effectuer une maintenance de fonctionnement sur un dispositif de réseau

Country Status (4)

Country Link
US (1) US20070201640A1 (zh)
EP (1) EP1804479A1 (zh)
CN (2) CN1992752A (zh)
WO (1) WO2007076668A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101202672A (zh) * 2007-12-26 2008-06-18 华为技术有限公司 一种网络运行指标实现方法、系统及装置
WO2010020246A1 (en) * 2008-08-22 2010-02-25 Neustring Fzco Method of analysing data traffic in a telecommunication network
CN101925084B (zh) * 2009-06-11 2014-07-16 中兴通讯股份有限公司 呼叫日志上报、匹配方法与装置
CN101764703B (zh) * 2009-09-16 2011-12-21 深圳市震有科技有限公司 一种基于虚拟技术的网元管理系统的实现方法
EP2481203B1 (en) 2009-09-23 2013-12-04 Telefonaktiebolaget LM Ericsson (publ) Technique for monitoring a call
KR101379670B1 (ko) * 2009-12-23 2014-04-04 알까뗄 루슨트 호 단위 측정 데이터를 수집하기 위한 방법 및 그것의 이동성 관리 디바이스 및 기지국

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1231809A (zh) * 1996-07-30 1999-10-13 夸尔柯姆股份有限公司 Cdma无线通信系统中的负荷监测和管理
CN1359576A (zh) * 2000-05-02 2002-07-17 三菱电机株式会社 Atm交换机及高可靠性的atm控制方法
CN1400797A (zh) * 2001-08-06 2003-03-05 赵宁 处理电话主叫信息的装置
US20050010659A1 (en) * 2003-07-08 2005-01-13 Alcatel Use of a communications network element management system to manage network policy rules
CN1618243A (zh) * 2001-12-10 2005-05-18 高通股份有限公司 在无线数据通信系统内测试话务和辅助信道的方法和装置
JP2005148966A (ja) * 2003-11-13 2005-06-09 Nippon Telegr & Teleph Corp <Ntt> 通信局内の媒体在庫管理装置および方法、ならびにそのプログラムと記録媒体

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9715497D0 (en) * 1997-07-22 1997-10-01 British Telecomm A telecommunications network
US6359976B1 (en) * 1998-06-08 2002-03-19 Inet Technologies, Inc. System and method for monitoring service quality in a communications network
US6876731B2 (en) * 2002-03-12 2005-04-05 Bellsouth Intellectual Property Corporation System and method for managing CDR information

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1231809A (zh) * 1996-07-30 1999-10-13 夸尔柯姆股份有限公司 Cdma无线通信系统中的负荷监测和管理
CN1359576A (zh) * 2000-05-02 2002-07-17 三菱电机株式会社 Atm交换机及高可靠性的atm控制方法
CN1400797A (zh) * 2001-08-06 2003-03-05 赵宁 处理电话主叫信息的装置
CN1618243A (zh) * 2001-12-10 2005-05-18 高通股份有限公司 在无线数据通信系统内测试话务和辅助信道的方法和装置
US20050010659A1 (en) * 2003-07-08 2005-01-13 Alcatel Use of a communications network element management system to manage network policy rules
JP2005148966A (ja) * 2003-11-13 2005-06-09 Nippon Telegr & Teleph Corp <Ntt> 通信局内の媒体在庫管理装置および方法、ならびにそのプログラムと記録媒体

Also Published As

Publication number Publication date
US20070201640A1 (en) 2007-08-30
CN101160803A (zh) 2008-04-09
EP1804479A1 (en) 2007-07-04
CN1992752A (zh) 2007-07-04

Similar Documents

Publication Publication Date Title
EP1616420B1 (en) Method for verification of communication path in ip telephony ping
US7551565B2 (en) User semantic overlay for troubleshooting convergent network problems
US6721284B1 (en) Generating service detail records
US8908558B2 (en) Method and apparatus for detecting a network impairment using call detail records
US7630484B2 (en) Service and information management system for a telecommunications network
US20080192920A1 (en) Service and information management system for a telecommunications network
EP1672836A1 (en) Generating service detail records with quality of service data
US8983046B2 (en) Method and apparatus for providing end-to-end call completion status
CN110401965B (zh) VoLTE语音质量拨测分析方法及系统
WO2007076668A1 (fr) Système, dispositif, et procédé pour effectuer une maintenance de fonctionnement sur un dispositif de réseau
US8908557B2 (en) Method and apparatus for monitoring a packet network
CN103269334B (zh) 会话关联方法、装置及系统
US6775375B1 (en) Service and information management system for determining, replicating or correcting failed calls in a telecommunications network
Tortorella Service reliability theory and engineering, II: Models and examples
KR100932900B1 (ko) ＶｏＩＰ 망에서의 실시간 통화품질 측정 및 관리 장치와그 방법
Cisco Release Notes for the BTS 10200 Release 2.0
KR101081097B1 (ko) 식별 정보 수집 장치 및 방법
JP4165335B2 (ja) 遅延時間測定装置、ジッター耐性測定装置及びそれらを用いた通話品質評価装置
CN104184625A (zh) Dss1信令监测方法和系统
JP2008295058A (ja) 遅延時間測定装置、ジッター耐性測定装置及びそれらを用いた通話品質評価装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 200680012224.8

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06804960

Country of ref document: EP

Kind code of ref document: A1