WO2007045189A1 - A method and system for service trace and service trace terminal, network element - Google Patents

A method and system for service trace and service trace terminal, network element Download PDF

Info

Publication number
WO2007045189A1
WO2007045189A1 PCT/CN2006/002808 CN2006002808W WO2007045189A1 WO 2007045189 A1 WO2007045189 A1 WO 2007045189A1 CN 2006002808 W CN2006002808 W CN 2006002808W WO 2007045189 A1 WO2007045189 A1 WO 2007045189A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
tracking
entity
tracking identifier
network element
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2006/002808
Other languages
English (en)
French (fr)
Inventor
Jianfeng Liu
Qifeng Ma
Yan Li
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
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 EP06805017A priority Critical patent/EP1947806A4/en
Publication of WO2007045189A1 publication Critical patent/WO2007045189A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/091—Measuring contribution of individual network components to actual service level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities

Definitions

  • the present invention relates to a communication system including a service tracking function, and more particularly to a method, system, service tracking terminal, and network element for service tracking.
  • system service tracking and fault location capability affects the resolution of faults.
  • Automatic service tracking and fast fault location play an important role in communication networks with specialized network tracking systems such as the O&M system (operation and maintenance system). Schematic diagram of the existing O&M system networking.
  • the O&M system is composed of the O&M server and the network side device (network element 1, network element 2, and network element n).
  • the O&M system stores basic information about the NE, such as the IP address, operating system type, name, location, and other descriptions.
  • the terminal is connected to the network side device and the connection mode is wired or wireless.
  • the O&M client requests the O&M server to initiate maintenance tasks, such as alarm monitoring and service signaling tracking, to start the service tracking process as shown in Figure 2.
  • the maintenance personnel pre-sets the tracking conditions, and the O&M client instructs the O&M server to send tracking conditions to each network element to set a service tracking task.
  • Tracking conditions such as terminal phone number, mobile station IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity), etc., can also be tracked not only for users, such as for servers, one or several SS7 links.
  • the NE records the tracking conditions and sets the service tracking task. At the end of this step, the NE is ready for business tracking.
  • the network element that initiates the service request and receives the first request information is assumed to be the network element.
  • NE 1 compare the key information in the message, such as MSISDN (Mobile Station International ISDN Number), with the tracking conditions set on the network element. If the conditions match, NE 1 will track the current business process and send the corresponding tracking information to the O&M system.
  • MSISDN Mobile Station International ISDN Number
  • the network element 1 needs to interact with the network element 2 during the service processing, and then sends The service message is sent to the network element 2, and the network element 2 checks whether the service message matches the tracking condition. If it matches, the service tracking is started, and the tracking information generated during the processing is reported to the O&M system. When the processing of the network element 2 needs to interact with the network element n, the calling process between the foregoing network elements is repeated.
  • the order of the tracking conditions set for the network element group (network element 1, network element 2 network element n) involved in the service need not be fixed, and the content of the setting tracking condition does not necessarily have to be the same, such as
  • the tracking condition is set to the MSISDN for the network element 1, and the tracking condition is set to the IMSI for the network element n.
  • the network element interacts with the NE.
  • the NE interacts with the terminal.
  • the service process is tracked from the beginning.
  • the tracking information is reported to the O&M server.
  • the O&M server sends the O&M server to the O&M client.
  • the maintenance personnel analyze the service process, especially Analysis when an abnormal processing condition occurs.
  • the maintenance personnel decides to stop tracking according to the amount of information obtained, so the O&M client instructs the O&M server to request each network element to disassemble the service tracking task.
  • the O&M server sends the command to the NE. After the NE deletes the tracking task, the service request initiated by the terminal will not be tracked.
  • the technical problem to be solved by the present invention is to provide a service tracking method and system, and an embodiment of a service tracking terminal and a network element, so that both the service terminal and the network element can initiate and participate in service tracking, and can record their participation in service tracking.
  • the obtained tracking information is further passed to the O&M system.
  • the operation and maintenance system sets a service tracking identifier on the business entity
  • one service entity transmits the service tracking identifier to another service entity, and the service entity that receives the service tracking identifier and the service entity that sends the service tracking identifier identify the service tracking identifier and perform the service. track.
  • An embodiment of the service tracking system provided by the present invention includes an operation and maintenance system and a plurality of service entities, where the operation and maintenance system includes a tracking identifier setting unit for setting a service tracking identifier on a service entity; A service entity passes the service tracking identifier to another service entity, and the service entity that receives the service tracking identifier and the service entity that sends the service tracking identifier identify the service tracking identifier to perform service tracking.
  • An embodiment of the terminal for service tracking includes a storage unit for storing a service tracking identifier, and a service tracking unit, configured to send a service tracking identifier, receive a service tracking identifier sent by another terminal or a network element, and Forwarding service tracking identifiers sent by other terminals or network elements; and identifying service tracking identifiers that need to track services, and performing service tracking.
  • the network element embodiment for the service tracking provided by the present invention also includes a storage unit for storing the service tracking identifier, and a service tracking unit, configured to send the service tracking identifier, receive the service tracking sent by other terminals or the network element. Identifying and forwarding the service tracking identifier sent by other terminals or network elements; and identifying the service tracking identifier that needs to track the service, and performing service tracking.
  • the embodiment of the method and system provided by the present invention and the terminal and the network element embodiment for the service tracking, enable the terminal to carry the service tracking identifier of the service in the message for initiating the service request, and the service involved
  • the network element identifies the service tracking identifier in the message, automatically starts the service tracking, records the service log, and delivers the service tracking identifier when interacting with the next entity.
  • the O&M system sets the service tracking identifier on any network element, so that the terminal that sends the service request to the network element and other network elements that have information interaction with the network element receive the service tracking identifier, the terminal, and other networks transmitted by the network element.
  • the meta-identity identifies the service tracking identity, thereby initiating service tracking.
  • the service tracking identifier is automatically transmitted between the terminal and the network element, and between the network element and the network element, so as to prevent the maintenance personnel from manually issuing the tracking command to each network element.
  • Both the terminal and the network element can initiate and participate in service tracking, providing more comprehensive business information for understanding and testing business processes and solving business problems. Provides an enhanced business tracking capability.
  • Figure 1 is a schematic diagram of networking of an existing O&M system
  • FIG. 3 is a block diagram of an embodiment of a service tracking system of the present invention.
  • FIG. 4 is a flowchart of Embodiment 2 of a service tracking method according to the present invention
  • 5 is a flowchart of Embodiment 3 or 4 of a service tracking method according to the present invention
  • FIG. 6 is a block diagram of an embodiment of a terminal for service tracking according to the present invention
  • FIG. 7 is a block diagram of an embodiment of a network element for service tracking according to the present invention.
  • FIG. 3 is a block diagram of an embodiment of a traffic tracking system.
  • FIG. 3 includes an O&M system and a plurality of service entities, where the O&M system includes a tracking identifier setting unit that sets a service tracking identifier on a service entity; the service entity includes a service tracking identifier, and in a process of service interaction between different service entities, The service entity passes the service tracking identifier to another service entity, and the service entity that receives the service tracking identifier identifies the service tracking identifier, starts and performs service tracking. After the service entity that receives the service tracking identifier identifies the service tracking identifier, it requests the O&M system to request the service tracking identifier authentication, and after the authentication is passed, starts the service tracking.
  • the O&M system includes a tracking identifier setting unit that sets a service tracking identifier on a service entity; the service entity includes a service tracking identifier, and in a process of service interaction between different service entities, The service entity passes the service tracking
  • the service entity that receives the service tracking identifier If the service entity that receives the service tracking identifier is in a different trust domain than the service entity that sends the service tracking identifier, the service entity that receives the service tracking identifier passes the O&M system of the trust domain in which it resides and the service entity that sends the service tracking identifier The O&M system of the trust domain obtains an authentication message.
  • the service entity includes a terminal and a network element.
  • the connection between the terminal and the network side may be wireless or wired according to the type of the terminal.
  • the terminal is a terminal for service tracking, and its structure can be referred to FIG. 6.
  • the terminal 1 is a specific embodiment, and includes a terminal function unit 11 and a storage unit 12 for storing a service tracking identifier.
  • the service tracking unit 13 is configured to send a service tracking identifier, receive a service tracking identifier sent by another terminal or a network element, and forward a service tracking identifier sent by another terminal or a network element; and identify that the service needs to be tracked.
  • Business tracking identification tracking of business.
  • the terminal functional unit 11 represents all other functional units of the terminal.
  • the method further includes an authentication processing unit, configured to: after the service tracking unit identifies the service tracking identifier that needs to be tracked, request the service tracking and maintenance system to authenticate the service tracking identifier, and After the authentication is passed, start the business tracking.
  • an authentication processing unit configured to: after the service tracking unit identifies the service tracking identifier that needs to be tracked, request the service tracking and maintenance system to authenticate the service tracking identifier, and After the authentication is passed, start the business tracking.
  • the network element is a network element used for service tracking, and its structure can be referred to FIG. 7, FIG.
  • the network element 2 is a specific embodiment, including a network element function unit 21 and a storage unit 22 for storing a service tracking identifier, and a service tracking unit 23, where the belonging service tracking unit 23 is configured to send its own service tracking identifier and receive The service tracking identifier sent by the other terminal or the network element and the service tracking identifier sent by the other terminal or the network element; and the service tracking identifier that needs to track the service, and the service tracking.
  • the network element function unit 21 represents all other functional units of the network element.
  • the authentication processing unit is further configured to: after the service tracking unit identifies the service tracking identifier that needs to be tracked, request the service tracking and maintenance system to perform service tracking identifier authentication, And, after the authentication is passed, start the business tracking.
  • the terminal in the system is an intelligent terminal with certain processing and storage capabilities such as computing, storage, networking, etc., and the terminal with networking capability can establish a network connection with the O&M server of the system; the terminal with computing capability can identify the service carried by the network element. Tracking identifier; A terminal with storage capability can record service logs, generate and save service tracking information.
  • the network connection established between the intelligent terminal and the O&M server can be a TCP/IP connection or other protocol mode.
  • the physical connection mode is wireless, such as GPRS, or wired, for example, the terminal has a network port connected to the O&M server.
  • the network side O&M server generates a service tracking identifier for a service (such as a download service), which is delivered and set to the terminal.
  • the delivery mode may be through a short message, or a direct TCP/IP network connection, etc.
  • the service tracking identifier may be directly set to the terminal through a TCP/IP network connection manually by the user or by the O&M server. Assume that the processing of a certain service requires the participation of network element 1 and network element 2:
  • the terminal initiates a service request to the network element 1, and carries the service tracking identifier in the service request message.
  • the network element 1 identifies the service tracking identifier, starts the service tracking, records the service processing log in the process of further service processing, generates the tracking information required for the service analysis, and carries the service tracking identifier. If the tracking information generated here is reported to the O&M server immediately, the process is followed by step (3). If the business process is to be performed for a period of time, or after the business process ends, the O&M server checks. If you ask for it, only the tracking information will be saved here.
  • the O&M server checks the service tracking identifier, and checks the service tracking information reported by the NE 1 to the O&M client for processing, such as displaying and analyzing the service process.
  • the network element 2 identifies the service tracking identifier, directly starts the service tracking, records the service processing log, generates the tracking information required for the service analysis, and reports the tracking information to the O&M server to carry the service tracking identifier.
  • the O&M server checks the service tracking identifier, and checks the service information reported by the NE 2 to the O&M client for processing.
  • the terminal can initiate the service tracking and report the tracking information to the O&M system.
  • step (2) the following steps may be added:
  • the network element 1 that receives the service request information from the terminal authenticates the service tracking identifier carried by the terminal, and the authentication is passed, and the network element 1 Start business tracking.
  • FIG. 4 is a signaling diagram of a terminal initiating and participating in tracking a service flow. It is a preferred embodiment of the function extension of the terminal to participate in and report the service tracking information and the network authentication of the service tracking identifier on the basis of the first embodiment:
  • the terminal initiates a service request to the network element 1, and carries a service tracking identifier in the service request message.
  • the terminal starts the service tracking, records the service log, and reports the service tracking information to the O&M server, carrying the service tracking identifier.
  • the O&M server checks the service tracking identifier, and after checking the service tracking identifier that is initially set to the terminal, the service tracking information is transmitted to the O&M client for processing, such as display processing.
  • the network element 1 that receives the terminal service request message detects that the service request message carries the service tracking identifier, and initiates the authentication of the service tracking identifier, that is, sends an authentication message to the O&M server, and carries the service tracking identifier.
  • the O&M server compares the service tracking identifier with the initially set service tracking identifier, and feeds back the authentication response of the service tracking identifier to the network element. If the service tracking identifier is the same, the authentication is passed.
  • the network element 1 starts the service tracking, records the service processing log in the process of further service processing, generates the tracking information required for the service analysis, and reports the tracking information to the O&M server, carrying the service tracking identifier.
  • the O&M server checks the service tracking identifier, and the service tracking information reported by the network element 1 is transmitted to the O&M client for processing, such as displaying and analyzing the business process, after the initial tracking is matched with the service tracking identifier on the terminal.
  • the network element 2 identifies the service tracking identifier, directly starts the service tracking, records the service processing log, generates the tracking information required for the service analysis, and reports the tracking information to the O&M server to carry the service tracking identifier.
  • the O&M server checks the service tracking identifier, and checks the service information reported by the network element 2 to the O&M client for processing.
  • the terminal and each network element continue to interact according to the service process.
  • the terminal and the network element continuously generate tracking information and report it to the O&M server.
  • the O&M server reports the tracking information to the O&M client for display until the end of the business process.
  • the service tracking identifier is canceled, and can be canceled manually by the user, or cancelled by the maintenance personnel through the O&M client operation, or deleted due to the automatic expiration of the lifetime of the service tracking identifier set by the O&M server. This prevents the client from overruning the service tracking identity and affecting network performance.
  • Business tracking After the identification is canceled, the next time the terminal initiates a service request, it will no longer carry the service tracking identifier. The NE will process the service request according to the normal process.
  • the terminal may initiate service tracking actively.
  • the service carries the service tracking identifier, the service tracking identifier in the network element identification message involved in the service, automatically starts service tracking, records the service log, and generates And report the tracking information required for the business analysis, and deliver the service tracking identifier when interacting with the next entity.
  • the tracking flag is automatically transmitted between the terminal and the network element along with the interaction information, so that the maintenance personnel can manually issue the tracking command to each network element manually, and the terminal can participate in the service tracking, which provides a solution for understanding and testing the business process and solving the business failure. More comprehensive business information.
  • the O&M server sets the service tracking identifier on NE1.
  • the O&M server maintains a TCP/IP connection between the server and the NE.
  • the service tracking identifier can be set to NE1 through the TCP/IP network connection. .
  • the terminal sends a service request to the network element 1, the tracking identifier is transmitted to the terminal, and the service tracking is started. Specific steps are as follows:
  • the terminal sends a service request to the network element 1.
  • the network element 1 After receiving the service request, the network element 1 sends the service tracking identifier to the terminal.
  • the terminal identifies the service tracking identifier, starts service tracking, generates a service tracking log, generates tracking information required for service analysis, and reports the tracking message to the O&M server.
  • the O&M server checks the service tracking identifier, and checks the tracking information reported by the terminal to the O&M client for processing after the initial setting is matched with the service tracking identifier on the network element 1.
  • the network element 1 In the service in which the network element 1 needs to invoke the network element n, the network element 1 carries the service information to the network element n while carrying the service tracking identifier.
  • step (6) and the subsequent steps are the same as the step (9) and the subsequent steps in the embodiment 2 shown in FIG. 4, and are not described herein again.
  • the O&M server sets a service tracking identifier for a service on any network element:
  • a network element sends a service to the network element that has set the service tracking identifier for the needs of the service. Interaction information.
  • the network element that has set the service tracking identifier After receiving the service interaction information, the network element that has set the service tracking identifier sends the service tracking identifier to a network element.
  • a network element identifies the service tracking identifier, starts service tracking, generates a service tracking log, generates tracking information required for service analysis, and reports the tracking message to the O&M server.
  • the O&M server After the processing, for example, the O&M server checks the service tracking identifier, and after checking the service tracking identifier that is initially set, the step of transmitting the reported tracking information to the O&M client for processing, and the steps (4) of the third embodiment and thereafter The steps are the same and will not be described again.
  • the service tracking can be initiated by the terminal sending a service request to the network element that has set the service tracking identifier. It can also be initiated by the network element sending service interaction information to the network element that has set the service tracking identifier.
  • the O&M system can set the service tracking identifier on any network element, so that the terminal that sends the service request to the network element and other network elements that have information interaction with the network element receive the service tracking identifier, the terminal, and other network elements transmitted by the network element. Identify the business tracking identifier to initiate business tracking and upload tracking information.
  • the tracking identifier is automatically transmitted between the terminal and the network element, the network element, and the network element along with the interaction information, so that the maintenance personnel can manually issue the tracking command to each network element manually, and the terminal can participate in the service tracking, and report the richer to the O&M system. Business information.
  • the two network elements are mutually trusted devices.
  • the network element that tracks the identifier does not need to authenticate the service tracking identifier, but directly identifies the service tracking identifier and then directly starts the service tracking.
  • the service tracking identifier is carried.
  • the network element sends an authentication message including the service tracking identifier to the O&M system in the same trust domain, and the O&M system of the carrier system where the other network element is located exchanges the authentication information according to the protocol between the operators, and then feeds back to the O&M.
  • the system is in the same trust domain as the network element to implement cross-domain authentication.
  • the network element 1 can further authenticate the service tracking identifier from the terminal. .
  • the timing of the service tracking information from the network element and the terminal to the O&M system does not have to be transmitted in real time, that is, it can be selected at other times as needed, as described in step 2 of Embodiment 1, in the service.
  • the client After a period of time, or after the end of the entire business process, by O&M Based on the service tracking identifier, the client initiates an inquiry to the intelligent terminal and the network element, and the network element records the service log.
  • the intelligent terminal can record the service tracking information because it has a certain storage function.
  • the O&M system can query the service information of different services and different time points by using the timestamp and the service tracking identifier of any service.
  • the method provided by the present invention can make the tracking flag follow the interaction information in the terminal and the network element.
  • the automatic transmission between the NE and the NE prevents the maintenance personnel from manually issuing the tracking commands to each NE.
  • Both the terminal and the network element can initiate and participate in service tracking, providing more comprehensive business information for understanding and testing business processes and solving business problems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

一种业务跟踪方法、 系统和业务跟踪终端、 网元 技术领域
本发明涉及含有业务跟踪功能的通信系统， 尤其涉及一种业务跟踪的 方法、 系统和业务跟踪终端、 网元。
背景技术
通信领域中， 系统业务跟踪与故障定位能力影响故障的解决， 自动业 务跟踪和快捷故障定位在含有专门网絡跟踪系统如 0&M系统（操作与维 护系统）的通信网络中起着重要作用，图 1为现有 0&M系统组网示意图。
由图 1可见， 0&M系统由 0&M服务器和 0&M客户端组成， O&M 系统通过 O&M ^I 务器与网络侧设备 (网元 1、 网元 2 、 网元 n )相 连。 0&M系统保存着网元的基本信息， 如 IP地址、操作系统类型，名称， 位置， 及其他描述信息等。 终端与网絡侧设备相连， 连接方式为有线或无 线。 维护人员通过 O&M客户端向 0&M服务器请求启动维护工作任务， 如告警监测、 业务信令跟踪等， 开始如图 2所示的业务跟踪过程。
假设某业务涉及的设备包括终端、 网元 1、 网元 2和网元 n, 启动并跟踪 该业务的处理过程由图 2示意， 具体如下：
1 )人工下发业务跟踪任务。
维护人员预先设定好跟踪条件， 在 O&M客户端指示 O&M服务器向各个 网元下发跟踪条件， 设定业务跟踪任务。 跟踪条件如终端电话号码、 移动 台 IMSI (国际移动用户标识）、 IMEI (国际移动设备标识）等， 也可不只 针对用户进行跟踪， 如针对服务器、 一条或几条七号信令链路等。 网元记 录跟踪条件， 设置业务跟踪任务。 本步骤结束时， 网元做好了业务跟踪的 准备。
2 )业务跟踪及信息上报。
终端发起业务请求， 接收到第一条请求信息的网元， 在此假设为网元
1 ,将消息中的关键信息，如 MSISDN (移动台国际 ISDN号码)，与网元上设 置的跟踪条件进行对比。如果条件匹配，网元 1将跟踪本次业务处理过程， 并将相应的跟踪信息向 O&M系统上艮。
假设在业务处理过程中网元 1需要与网元 2进行信息交互， 于是发送 业务消息给网元 2， 网元 2检查业务消息与跟踪条件是否匹配，如果匹配， 启动业务跟踪， 并将处理过程中产生的跟踪信息上报 O&M系统。 网元 2 的处理过程还需与网元 n交互时， 重复上述网元间的调用过程。
在此需要说明的是， 对涉及该业务的网元组（网元 1、 网元 2 网元 n )设定的跟踪条件的顺序无需固定， 设定跟踪条件的内容也不一定 必须相同， 如对网元 1设定跟踪条件为 MSISDN, 对网元 n设定跟踪条件 为 IMSI, 只要能够使业务信息与跟踪条件进行匹配， 达到跟踪目的即可。 网元与网元交互， 网元与终端交互， 业务的过程从起始即得到跟踪， 其跟 踪信息上报到 O&M服务器， 0&M服务器再发送给 O&M客户端， 由维 护人员分析业务处理流程， 特別是当异常的处理状况出现时的分析。
3 )停止业务跟踪
维护人员根据得到的信息量的情况， 决定停止跟踪， 于是在 O&M客 户端指示 O&M服务器要求各个网元拆销业务跟踪任务。 O&M服务器将 命令下发给网元， 网元删除跟踪任务之后， 终端发起的业务请求将不会被 跟踪。
由以上流程可以看出， 现有的业务跟踪过程中， 终端不能主动发起业 务跟踪， 完全由维护人员用人工方式通过 O&M系统向各个网元分别下达 跟踪命令， 自动化程度低， 且终端不能产生跟踪信息， 不便于业务故障原 因的分析和解决。
发明内容
本发明要解决的技术问题是提供一种业务跟踪方法、 系统以及一种业 务跟踪终端和网元的实施例， 使业务终端和网元皆可发起和参与业务跟 踪， 并且能够记录其参与业务跟踪取得的跟踪信息， 进一步向 O&M系统 传递上述信息。
本发明提供的业务跟踪方法实施例， 包括：
操作与维护系统在业务实体上设置业务跟踪标识；
在不同业务实体业务交互的过程中， 一个业务实体将所述业务跟踪标 识传递到另一个业务实体， 由接收到业务跟踪标识的业务实体和发送业务 跟踪标识的业务实体识别业务跟踪标识， 进行业务跟踪。 本发明提供的业务跟踪系统实施例， 包括操作与维护系统和多个业务 实体， 所述操作与维护系统包括在业务实体上设置业务跟踪标识的跟踪标 识设置单元； 在不同业务实体业务交互的过程中， 一个业务实体将所述业 务跟踪标识传递到另一个业务实体， 由接收到业务跟踪标识的业务实体和 发送业务跟踪标识的业务实体识别业务跟踪标识， 进行业务跟踪。
本发明提供的用于业务跟踪的终端实施例， 包括用于存储业务跟踪标 识的存储单元， 还包括业务跟踪单元， 用于发送自身业务跟踪标识、 接收 其它终端或网元发送的业务跟踪标识和转发其它终端或网元发送的业务 跟踪标识； 以及， 识别需要跟踪业务的业务跟踪标识， 进行业务跟踪。
本发明提供的用于业务跟踪的网元实施例， 也包括用于存储业务跟踪 标识的存储单元， 还包括业务跟踪单元， 用于发送自身业务跟踪标识、 接 收其它终端或网元发送的业务跟踪标识和转发其它终端或网元发送的业 务跟踪标识； 以及， 识别需要跟踪业务的业务跟踪标识， 进行业务跟踪。
因此， 本发明所提供的方法和系统的实施例， 以及用于业务跟踪的终 端和网元实施例， 能使终端在发起业务请求的消息中， 携带该业务的业务 跟踪标识， 业务所涉及的网元识别消息中的业务跟踪标识， 自动启动业务 跟踪， 记录业务日志， 并且在与下一实体交互时传递业务跟踪标识。 或者 由 0&M系统在任一网元上设置业务跟踪标识， 使向该网元发送业务请求 的终端和与该网元有信息交互的其它网元接收该网元传递的业务跟踪标 识， 终端和其它网元识别业务跟踪标识， 从而启动业务跟踪。 业务跟踪标 识随交互信息自动地在终端和网元， 以及网元和网元间传递， 避免由维护 人员向各个网元人工地分别下达跟踪命令。 终端和网元皆能发起和参与业 务跟踪，为了解和测试业务流程、解决业务故障提供了更全面的业务信息。 提供了一种增强的业务跟踪功能。
附图说明
图 1为现有 O&M系统組网示意图；
图 2为现有业务跟踪流程信令图；
图 3为本发明的业务跟踪系统实施例框图；
图 4为本发明的业务跟踪方法实施例 2的流程图； 图 5为本发明的业务跟踪方法实施例 3或 4的流程图； 图 6为本发明的用于业务跟踪的终端实施例框图；
图 7为本发明的用于业务跟踪的网元实施例框图。
具体实施方式
下面结合附图及具体实施例对本发明作进一步详细说明。
图 3是的业务跟踪系统的实施例框图。 图 3包括 0&M系统和多个业 务实体， 所述 O&M系统包括在业务实体上设置业务跟踪标识的跟踪标识 设置单元； 所述业务实体包括业务跟踪标识， 在不同业务实体业务交互的 过程中， 一个业务实体将所述业务跟踪标识传递到另一个业务实体， 由接 收到业务跟踪标识的业务实体识别业务跟踪标识， 启动并进行业务跟踪。 其中， 接收到业务跟踪标识的业务实体识别业务跟踪标识后， 向 O&M系 统请求业务跟踪标识鉴权， 以及， 在鉴权通过后， 启动业务跟踪。 若接收 到业务跟踪标识的业务实体与发送业务跟踪标识的业务实体处于不同的 信任域， 则接收到业务跟踪标识的业务实体通过其所在的信任域的 O&M 系统和发送业务跟踪标识的业务实体所在的信任域的 O&M系统取得鉴权 消息。
在图 3所示系统中， 所述业务实体包括终端和网元。 其中， 终端与网 络侧的连接根据终端类型可为无线或有线方式。
这里所述终端为用于业务跟踪的终端， 其结构可以参考图 6, 图 6所 述终端 1是一个具体的实施例， 包括终端功能单元 11和用于存储业务跟 踪标识的存储单元 12, 还包括业务跟踪单元 13, 所属业务跟踪单元 13用 于发送自身业务跟踪标识、接收其它终端或网元发送的业务跟踪标识和转 发其它终端或网元发送的业务跟踪标识； 以及， 识别需要跟踪业务的业务 跟踪标识， 进行业务跟踪。 其中， 所述终端功能单元 11 代表了终端的其 他所有的功能单元。
在所述终端的另一个具体的实施例中， 还包括鉴权处理单元， 用于在 所述业务跟踪单元识别需要跟踪的业务跟踪标识后， 向操作与维护系统请 求业务跟踪标识鉴权， 以及， 在鉴权通过后， 启动业务跟踪。
这里所述网元为用于业务跟踪的网元， 其结构可以参考图 7, 图 7所 述网元 2是一个具体的实施例， 包括网元功能单元 21和用于存储业务跟 踪标识的存储单元 22, 还包括业务跟踪单元 23 , 所属业务跟踪单元 23用 于发送自身业务跟踪标识、接收其它终端或网元发送的业务跟踪标识和转 发其它终端或网元发送的业务跟踪标识； 以及， 识别需要跟踪业务的业务 跟踪标识， 进行业务跟踪。 其中， 所述网元功能单元 21代表了网元的其 他所有的功能单元。
在所述网元的另一个具体的实施例中， 还包括鉴权处理单元， 用于在 所述业务跟踪单元识别需要跟踪的业务跟踪标识后， 向操作与维护系统请 求业务跟踪标识鉴权， 以及， 在鉴权通过后， 启动业务跟踪。
该系统中的终端为具备计算、 存储、 联网等一定处理和存储能力的智 能型终端， 具有联网能力的终端可与系统的 O&M服务器建立网络连接； 具有计算能力的终端可以识别网元携带的业务跟踪标识； 具有存储能力的 终端可以记录业务日志， 生成并保存业务跟踪信息。
智能型终端与 0&M服务器建立的网络连接， 可为 TCP/IP连接， 或 为其它协议方式。 物理连接方式为无线方式， 如 GPRS, 或为有线方式， 如终端有网口接 O&M服务器。
实施例 1 :
以下步骤是本发明的业务跟踪方法通过在终端上设置跟踪标识来启 动并进行业务跟踪的一个较简单的实施例。 网络侧 O&M服务器产生针对 一种业务（如： 下载业务） 的业务跟踪标识， 传递并设置到终端上。 传递 方式具体可以通过短消息、 或直接的 TCP/IP 网络连接等； 相应地， 业务 跟踪标识可以通过用户手动或由 O&M服务器通过 TCP/IP网络连接直接 设置到终端。 假设某一业务的处理需要网元 1、 网元 2的参与：
( 1 )终端向网元 1发起业务清求， 在业务请求消息中携带业务跟踪 标识。
( 2 ) 网元 1 识别业务跟踪标识， 启动业务跟踪， 在进一步业务处理 的过程中记录业务处理日志， 生成业务分析需要的跟踪信息， 携带业务跟 踪标识。 此处产生的跟踪信息若即时上报 O&M服务器， 则接步骤（3 ), 若待业务流程进行一段时间后， 或是在业务流程结束后由 O&M服务器查 询取得， 则此处只保存跟踪信息。
( 3 ) 0&M服务器检查业务跟踪标识， 核对与初始设置到终端上的业 务跟踪标识相符后， 将网元 1上报的业务跟踪信息传递至 0&M客户端进 行处理， 如显示、 分析业务流程等。
( 4 )假设该业务中， 网元 1需要与网元 2交互业务信息， 网元 1将 携带业务跟踪标识的业务信息传递给网元 2。
( 5 ) 网元 2识别业务跟踪标识， 直接启动业务跟踪， 记录业务处理 日志， 生成业务分析需要的跟踪信息， 将跟踪信息上报 O&M服务器， 携 带业务跟踪标识。
( 6 ) 0&M服务器检查业务跟踪标识， 核对与初始设置到终端上的业 务跟踪标识相符后， 将网元 2上报的业务信息传递到 O&M客户端进行处 理。
可以理解， 在步骤（1 ) 中， 终端向网元发起业务请求之前， 或者同 时， 或者发送请 之后， 终端可以自行启动业务跟踪并将跟踪信息上报 O&M系统。
出于网络安全的考虑， 在步骤（2 )之前， 还可以增加如下步骤： 接收来自终端的业务请求信息的网元 1对终端携带的业务跟踪标识进 行鉴权， 待鉴权通过， 网元 1启动业务跟踪。
实施例 2:
图 4是终端发起并参与跟踪业务流程的信令示意图。 是在实施例 1基 础上对终端参与并上报业务跟踪信息， 以及对业务跟踪标识进行网络鉴权 的功能扩展的较佳实施例：
( 1 )终端向网元 1发起业务请求， 在业务请求消息中携带业务跟踪 标识。
( 2 )终端启动业务跟踪， 记录业务日志， 将业务跟踪信息上报 O&M 服务器， 携带业务跟踪标识。
( 3 ) O&M服务器检查业务跟踪标识， 核对与初始设置到终端上的业 务跟踪标识相符后， 将业务跟踪信息传递到 0&M客户端进行处理， 如显 示处理等。 ( 4 )接收终端业务请求消息的网元 1检测出业务请求消息中带有业 务跟踪标识， 启动对该业务跟踪标识的鉴权， 即向 0&M服务器发送鉴权 消息， 携带业务跟踪标识。
( 5 ) 0&M服务器将业务跟踪标识和初始设置的业务跟踪标识进行对 比， 向网元反馈业务跟踪标识的鉴权呼应。 若业务跟踪标识相同， 鉴权通 过。
( 6 ) 网元 1 启动业务跟踪， 在进一步业务处理的过程中记录业务处 理日志， 生成业务分析需要的跟踪信息， 将跟踪信息上报 O&M服务器， 携带业务跟踪标识。
( 7 ) O&M服务器检查业务跟踪标识， 核对与初始设置到终端上的业 务跟踪标识相符后， 将网元 1上报的业务跟踪信息传递到 O&M客户端进 行处理， 如显示、 分析业务流程等。
( 8 )假设该业务中， 网元 1需要与网元 交互业务信息， 网元 1将 携带业务 3艮踪标识的业务消息传递给网元 2。
( 9 ) 网元 2识别业务跟踪标识， 直接启动业务跟踪， 记录业务处理 日志， 生成业务分析需要的跟踪信息， 将跟踪信息上报 O&M服务器， 携 带业务跟踪标识。
( 10 ) O&M服务器检查业务跟踪标识， 核对与初始设置到终端上的 业务跟踪标识相符后， 将网元 2上报的业务信息传递到 O&M客户端进行 处理。
步驟（11 )至（13 ) 为还需要网元 n参与该业务时， 网元 2将业务跟 踪标识传递给网元 n, 使网元 n启动业务跟踪并产生跟踪信息的情况， 具 体过程同步骤（8 )到 （10 )。
终端和各个网元按业务流程继续交互， 终端和网元不断产生跟踪信息 并上报 O&M服务器， O&M服务器再将跟踪信息上报给 O&M客户端显 示， 直至业务流程结束。 流程进行中或者流程结束后， 业务跟踪标识被取 消， 可以通过用户手动取消， 或者由维护人员通过 O&M客户端操作来取 消，或者因 O&M服务器设定的业务跟踪标识生命期结束自动过期而删除。 这样可以防止客户端超期使用业务跟踪标识而影响网络性能。 业务跟踪标 识被取消后， 终端下次发起业务请求时将不再带有业务跟踪标识， 网元将 按正常流程处理业务请求。
由上述实施例可见， 终端可以主动发起业务跟踪， 在发起业务请求的 消息中， 携带业务跟踪标识， 业务所涉及的网元识别消息中的业务跟踪标 识， 自动启动业务跟踪， 记录业务日志， 生成并上报业务分析需要的跟踪 信息， 并且在与下一实体交互时传递业务跟踪标识。 跟踪标志随交互信息 自动地在终端和网元间传递， 避免由维护人员向各个网元人工地分別下达 跟踪命令， 而且使终端能参与业务跟踪， 为了解和测试业务流程、 解决业 务故障提供了更全面的业务信息。
实施例 3:
如图 5所示， 0&M服务器在网元 1上设置业务跟踪标识，養于 0&M 服务器与网元间一般保持着 TCP/IP连接， 业务跟踪标识可以通过 TCP/IP 网络连接设置到网元 1上。 终端向网元 1发送业务请求时， 跟踪标识被传 递至终端上， 业务跟踪启动。 具体步骤如下：
( 1 )终端向网元 1发送业务请求。
( 2 ) 网元 1收到业务请求后， 将业务跟踪标识发送给终端。
( 3 )终端识别该业务跟踪标识， 启动业务跟踪， 生成业务跟踪日志 , 生成业务分析需要的跟踪信息， 并将跟踪消息上报 0&M服务器。
( 4 ) O&M服务器检查业务跟踪标识， 核对与初始设置到网元 1上的 业务跟踪标识相符后， 将终端上报的跟踪信息传递到 O&M客户端进行处 理，
( 5 )在网元 1还需要调用网元 n参与的业务中， 网元 1将业务信息 交互给网元 n的同时携带业务跟踪标识。
步骤（6 )及其后步骤即与图 4所示的实施例 2中步骤（9 )及后续步 骤相同， 此处不再赘述。
实施例 4:
如图 5所示， O&M服务器在任一网元上设置一种业务的业务跟踪标 识：
( 1 ) 某网元因该种业务需要， 向设置了业务跟踪标识的网元发送业 务交互信息。
( 2 )设置了业务跟踪标识的网元收到业务交互信息后， 将业务跟踪 标识发送给某网元。
( 3 ) 某网元识别该业务跟踪标识， 启动业务跟踪， 生成业务跟踪日 志， 生成业务分析需要的跟踪信息， 并将跟踪消息上报 O&M服务器。
此后的处理过程， 如 0&M服务器检查业务跟踪标识， 核对与初始设 置的业务跟踪标识相符后， 将上报的跟踪信息传递到 0&M客户端进行处 理等步骤与实施例 3的步骤（4 ) 以及其后的步骤相同， 不再赘述，
由上述实施例可见， 业务跟踪可由终端向设置了业务跟踪标识的网元 发送业务请求而发起。 也可由网元向设置了业务跟踪标识的网元发送业务 交互信息而发起。 O&M 系统可在任一网元上设置业务跟踪标识， 使向该 网元发送业务请求的终端和与该网元有信息交互的其它网元接收该网元 传递的业务跟踪标识， 终端和其它网元识别业务跟踪标识， 从而启动业务 跟踪并上艮跟踪信息。 跟踪标识随交互信息自动地在终端和网元、 网元和 网元间传递， 避免由维护人员向各个网元人工地分别下达跟踪命令， 而且 使终端能参与业务跟踪， 向 O&M系统上报更丰富的业务信息。
需要说明的是， 一些业务常常需要不同的运营商系统共同支持， 当进 行交互业务两个网元同处一个运营商系统即同一信任域中时， 两个网元是 相互信任的设备， 接收业务跟踪标识的网元不需要对业务跟踪标识再进行 鉴权， 而是识别业务跟踪标识后直接启动业务跟踪； 当两个网元处于不同 运营商系统即不同的信任域时， 携带业务跟踪标识的网元向同一信任域的 O&M 系统发送包含业务跟踪标识的鉴权消息， 另一网元所处的运营商系 统的 O&M系统凭运营商之间的协议交互鉴权信息，然后反馈给与该 O&M 系统处于同一信任域中的网元来实现跨域鉴权。 同理， 在图 4所示的实施 例 2中， 由于终端不在任何一个运营商系统的信任域中， 所以出于安全考 虑， 进一步地， 网元 1可对来自终端的业务跟踪标识进行鉴权。
另需说明的是，业务跟踪信息从网元和终端上报到 O&M系统的时机， 不一定要进行实时传递， 即也可根据需要选择在其它时间， 如实施例 1的 步骤 2所述，在业务进行一段时间后，或在整个业务流程结束后， 由 O&M 客户端以业务跟踪标识为条件， 向智能型终端和网元发起查询， 网元记录 业务日志， 智能型终端因具有一定的存储功能， 故能记录业务跟踪信息，
0&M 系统可凭时间戳和任一业务的业务跟踪标识查询不同业务和不同时 点的业务信息。
综上所述， 本发明所提供的方法可以使跟踪标志随交互信息在终端和 网元。 网元和网元间自动传递， 避免由维护人员向各个网元人工地分别下 达跟踪命令。 终端和网元皆能发起和参与业务跟踪， 为了解和测试业务流 程、 解决业务故障提供了更全面的业务信息。
以上所述仅为本发明的较佳实施例而已， 并非用于限定本发明的保护 范围。凡在本发明的精神和原则之内所作的任何修改、等同替换、改进等， 均包含在本发明的包含范围内。

Claims

权 利 要 求
1、 一种业务 3艮踪方法， 其特征在于， 包括以下步骤：
操作与维护系统在业务实体上设置业务跟踪标识；
在不同业务实体业务交互的过程中， 一个业务实体将所述业务跟踪标 识传递到另一个业务实体， 由接收到业务跟踪标识的业务实体和发送业务 跟踪标识的业务实体识别所述业务跟踪标识， 进行业务跟踪。
2、 根据权利要求 1 所述的方法， 其特征在于： 接收到业务跟踪标识 的业务实体识别业务跟踪标识后， 向操作与维护系统请求业务跟踪标识鉴 权， 以及， 在鉴权通过后， 启动业务跟踪。
3、 根据权利要求 2所述的方法， 其特征在于， 若接收到业务跟踪标 识的业务实体与发送业务跟踪标识的业务实体处于不同的信任域， 则接收 到业务跟踪标识的业务实体通过其所在的信任域的操作与维护系统和发 送业务跟踪标识的业务实体所在的信任域的操作与维护系统取得鉴权消
4、 根据权利要求 1、 2或 3所述的方法， 其特征在于， 第一业务实体 向第二业务实体发送业务请求时， 将所设置的业务跟踪标识传递到第二业 务实体。
5、 根据权利要求 1、 2或 3所述的方法， 其特征在于， 第一业务实体 向第二业务实体发送业务请求时， 第二业务实体将所设置的业务跟踪标识 随业务流传递到第一业务实体。
6、 根据权利要求 4所述的方法， 其特征在于， 所述第一业务实体为 终端， 所述第二业务实体为网元。
7、 根据权利要求 5所述的方法， 其特征在于， 所述第一业务实体为 终端， 所述第二业务实体为网元。
8、 根据权利要求 1、 2或 3所述的方法， 其特征在于， 设置了业务跟 踪标识的业务实体将所设置的业务跟踪标识附加标识本次跟踪的参数后 传递到另一个业务实体。
9、 根据权利要求 1所述的方法， 其特征在于， 业务跟踪启动后， 各 业务实体记录业务日志， 生成业务分析需要的跟踪信息， 上报操作与维护 系统服务器， 操作与维护系统服务器检查业务跟踪标识， 核对与初始设置 的业务跟踪标识相符后， 将上报的跟踪信息传递到操作与维护系统客户端 进行处理。
10、 根据权利要求 9所述的方法， 其特征在于， 所述生成的跟踪信息 实时上报操作与维护系统， 或者由业务实体保存， 在业务流程结束后由操 作与维护系统查询取得。
11、 根据权利要求 1所述的方法， 其特征在于进一步包括： 业务流程进行中或结束后， 业务跟踪标识通过用户手动取消， 或者由 操作与维护系统客户端取消， 或者因设定的业务跟踪标识生命期结束而自 动过期而取消。
12、 一种业务 3艮踪系统， 包括操作与维护系统和多个业务实体， 其特 征在于， 所述操作与维护系统包括在业务实体上设置业务跟踪标识的跟踪 标识设置单元； 在不同业务实体业务交互的过程中， 一个业务实体将所述 业务跟踪标识传递到另一个业务实体， 由接收到业务跟踪标识的业务实体 和发送业务跟踪标识的业务实体识别业务跟踪标识， 进行业务跟踪。
13、 根据权利要求 12所述的系统， 其特征在于： 接收到业务跟踪标 识的业务实体识别业务跟踪标识后， 向操作与维护系统请求业务跟踪标识 鉴权， 以及， 在鉴权通过后， 启动业务跟踪。
14、 根据权利要求 13所述的系统， 其特征在于， 若接收到业务跟踪 标识的业务实体与发送业务跟踪标识的业务实体处于不同的信任域， 则接 收到业务跟踪标识的业务实体通过其所在的信任域的操作与维护系统和 发送业务跟踪标识的业务实体所在的信任域的操作与维护系统取得鉴权 消息。
15、 一种用于业务跟踪的终端， 包括用于存储业务跟踪标识的存储单 元， 其特征在于还包括：
业务跟踪单元， 用于发送自身业务跟踪标识、 接收其它终端或网元发 送的业务跟踪标识和转发其它终端或网元发送的业务跟踪标识； 以及， 识 别需要跟踪业务的业务跟踪标识， 进行业务跟踪。
16、 根据权利要求 15所述的用于业务跟踪的终端， 其特征在于还包 括： 鉴权处理单元， 用于在所述业务跟踪单元识别需要跟踪的业务跟踪标 识后， 向操作与维护系统请求业务跟踪标识鉴权， 以及， 在鉴权通过后， 启动业务跟踪。
17、 一种用于业务跟踪的网元， 包括用于存储业务跟踪标识的存储单 元， 其特征在于还包括：
业务跟踪单元， 用于发送自身业务跟踪标识、 接收其它终端或网元发 送的业务跟踪标识和转发其它终端或网元发送的业务跟踪标识； 以及， 识 别需要跟踪业务的业务跟踪标识 , 进行业务跟踪。
18、 根据权利要求 17所述的用于业务跟踪的网元， 其特征在于还包 括： 鉴权处理单元， 用于在所述业务跟踪单元识别需要跟踪的业务跟踪标 识后， 向操作与维护系统请求业务跟踪标识鉴权， 以及， 在鉴权通过后， 启动业务跟踪。
PCT/CN2006/002808 2005-10-22 2006-10-20 A method and system for service trace and service trace terminal, network element Ceased WO2007045189A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP06805017A EP1947806A4 (en) 2005-10-22 2006-10-20 METHOD, SYSTEM AND SERVICE TRACE TERMINAL, NETWORK ELEMENT

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510100662.7 2005-10-22
CNB2005101006627A CN100454836C (zh) 2005-10-22 2005-10-22 一种业务跟踪的方法和系统

Publications (1)

Publication Number Publication Date
WO2007045189A1 true WO2007045189A1 (en) 2007-04-26

Family

ID=37298032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/002808 Ceased WO2007045189A1 (en) 2005-10-22 2006-10-20 A method and system for service trace and service trace terminal, network element

Country Status (3)

Country Link
EP (1) EP1947806A4 (zh)
CN (1) CN100454836C (zh)
WO (1) WO2007045189A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2109251A4 (en) * 2007-05-31 2010-10-06 Huawei Tech Co Ltd SERVICE PROCEDURE, NETWORK DEVICE, OPERATING AND MANAGEMENT CONTROL DEVICE, SERVICE REQUIREMENT

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101193393B (zh) * 2006-11-24 2010-09-08 大唐移动通信设备有限公司 消息跟踪的方法及系统
CN101232691B (zh) * 2007-01-24 2011-03-16 中兴通讯股份有限公司 信令跟踪方法及装置
CN100484037C (zh) 2007-03-14 2009-04-29 华为技术有限公司 设备跟踪系统、装置及方法
CN101287257B (zh) * 2007-04-09 2012-10-17 华为技术有限公司 一种业务跟踪方法、系统及服务器
CN101183980A (zh) * 2007-12-12 2008-05-21 上海华为技术有限公司 一种设备跟踪方法、装置及系统
CN101404696B (zh) * 2008-11-03 2012-10-10 中兴通讯股份有限公司 可视化业务流程跟踪方法和系统、业务流程处理系统
TWI420387B (zh) * 2009-07-30 2013-12-21 Woei Jia Hwang 網頁即時語音錄製方法及其應用
CN102480383B (zh) * 2010-11-23 2015-12-16 腾讯科技（深圳）有限公司 一种日志消息报文处理方法及装置
CN102739465A (zh) * 2011-04-12 2012-10-17 中兴通讯股份有限公司 一种实现信令跟踪的方法、装置及系统
CN102427411B (zh) * 2011-12-06 2014-10-22 中兴通讯股份有限公司 一种全网信令跟踪方法及系统
CN111526068B (zh) * 2020-04-29 2023-07-11 华为技术有限公司 故障上报方法及终端
CN115499807A (zh) * 2021-06-18 2022-12-20 中兴通讯股份有限公司 网元配置方法、业务配置方法、网元、存储介质
CN115988438B (zh) * 2022-12-14 2024-07-30 中国联合网络通信集团有限公司 呼叫业务数据处理方法、装置、设备及存储介质
CN120223508B (zh) * 2025-05-27 2025-07-29 广东开普勒通讯科技有限公司 云数据中心的监控运维管理方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000056029A1 (en) 1999-03-12 2000-09-21 Nokia Networks Oy Interception system and method
CN1284232A (zh) * 1997-12-04 2001-02-14 艾利森公司 网络呼叫跟踪
CN1494349A (zh) * 2002-10-28 2004-05-05 深圳市中兴通讯股份有限公司 一种移动通讯系统中实现用户呼叫信令跟踪的方法
CN1555163A (zh) * 2003-12-29 2004-12-15 中兴通讯股份有限公司 一种光传输环形网错连业务的恢复方法
CN1596001A (zh) * 2003-09-13 2005-03-16 华为技术有限公司 无线网络控制器面向用户的故障检测方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7200848B1 (en) * 2000-05-09 2007-04-03 Sun Microsystems, Inc. Migrating processes using data representation language representations of the processes in a distributed computing environment
US20020072358A1 (en) * 2000-12-13 2002-06-13 Telefonaktiebolaget Lm Ericsson Methods and apparatus for real-time performance monitoring in a wireless communication network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1284232A (zh) * 1997-12-04 2001-02-14 艾利森公司 网络呼叫跟踪
WO2000056029A1 (en) 1999-03-12 2000-09-21 Nokia Networks Oy Interception system and method
CN1494349A (zh) * 2002-10-28 2004-05-05 深圳市中兴通讯股份有限公司 一种移动通讯系统中实现用户呼叫信令跟踪的方法
CN1596001A (zh) * 2003-09-13 2005-03-16 华为技术有限公司 无线网络控制器面向用户的故障检测方法
CN1555163A (zh) * 2003-12-29 2004-12-15 中兴通讯股份有限公司 一种光传输环形网错连业务的恢复方法

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2109251A4 (en) * 2007-05-31 2010-10-06 Huawei Tech Co Ltd SERVICE PROCEDURE, NETWORK DEVICE, OPERATING AND MANAGEMENT CONTROL DEVICE, SERVICE REQUIREMENT

Also Published As

Publication number Publication date
EP1947806A4 (en) 2008-10-29
CN1859165A (zh) 2006-11-08
EP1947806A1 (en) 2008-07-23
CN100454836C (zh) 2009-01-21

Similar Documents

Publication Publication Date Title
WO2007045189A1 (en) A method and system for service trace and service trace terminal, network element
CN106534289B (zh) 自动化测试方法、装置及系统
CN107395767A (zh) 基于长连接的消息推送系统及方法
US20100100582A1 (en) System and method for server initiation beacon
CN108833172B (zh) 一种网络故障报警的处理方法、装置和网络系统
CN108990062B (zh) 智能安全Wi-Fi管理方法和系统
CN109525620B (zh) 一种消息推送系统、方法及装置
CN102647295B (zh) 一种设备管理的方法及装置
US20160301580A1 (en) Service Testing Method, Device, and System, Network Node, and Quality Processing Node
CN101227339B (zh) 一种基于内容和/或ip地址的数据业务监控方法
CN101325781A (zh) 一种合法监听方法、系统和网络设备
CN101026506B (zh) 一种接入网监听系统及其实现方法
CN108112015B (zh) 一种语音业务的切换方法、装置及移动终端
CN100466541C (zh) 业务网络跟踪系统及跟踪方法
JP2006279636A (ja) クライアント間通信ログの整合性保証管理システム
WO2008138198A1 (en) Keepalive monitoring method, system and apparatus of a subscriber session
CN101076196B (zh) 合法监听系统和方法
WO2014015525A1 (zh) 一种用户在线状态的查询方法和装置
CN100583090C (zh) 数据库的侦听
WO2022041827A1 (zh) 移动网络侦测信息的传输方法和装置、存储介质
CN116866473A (zh) 基于可信通信的身份展示方法、终端及服务器
CN106506495B (zh) 一种终端上线控制方法及装置
CN101296113B (zh) 网元设备、网管系统及网元设备注册接入网管系统的方法
CN107566473A (zh) 一种电力二次系统设备核查方法
WO2012068792A1 (zh) 手机及实现手机设备管理的注册方法、系统及装置

Legal Events

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

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2006805017

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2006805017

Country of ref document: EP