WO2018205850A1 - 一种基站运维方法和装置 - Google Patents

一种基站运维方法和装置 Download PDF

Info

Publication number
WO2018205850A1
WO2018205850A1 PCT/CN2018/084745 CN2018084745W WO2018205850A1 WO 2018205850 A1 WO2018205850 A1 WO 2018205850A1 CN 2018084745 W CN2018084745 W CN 2018084745W WO 2018205850 A1 WO2018205850 A1 WO 2018205850A1
Authority
WO
WIPO (PCT)
Prior art keywords
log
base station
fault
collection task
maintenance
Prior art date
Application number
PCT/CN2018/084745
Other languages
English (en)
French (fr)
Inventor
黄政
王玉龙
徐芳
智亚丹
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018205850A1 publication Critical patent/WO2018205850A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • 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/04—Network management architectures or arrangements
    • 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
    • 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
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • 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
    • H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications

Definitions

  • the present disclosure relates to the field of wireless network management, and in particular, to a base station operation and maintenance method and apparatus.
  • the base station operation and maintenance method and apparatus are provided in the embodiments of the present disclosure.
  • the disclosure is directed to the base station operation and maintenance method and apparatus.
  • An embodiment of the present disclosure provides a base station operation and maintenance method, including:
  • the fault of the base station is processed according to the analysis result of the fault log.
  • an embodiment of the present disclosure further provides a base station operation and maintenance device, including:
  • the collection module is configured to collect a fault log according to relevant parameters in the log collection task
  • the processing module is configured to process the fault of the base station according to the analysis result of the fault log.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the methods described above.
  • the present disclosure provides a base station operation and maintenance method and apparatus.
  • the method includes: determining a log collection task sent by a network management server to a base station, collecting a fault log according to relevant parameters in the log collection task, and analyzing the fault log according to the fault log. , handling the failure of the base station.
  • the fault log of the base station is automatically collected in real time during the operation and maintenance of the base station, and the fault is not used to recover the fault, thereby reducing the occupation and loss of system resources and improving the security of the base station operation. And stability.
  • FIG. 1 is a flowchart of a base station operation and maintenance method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic structural diagram of a base station operation and maintenance device according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of another base station operation and maintenance method according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of still another method for operating a base station according to an embodiment of the present disclosure.
  • the idea of the present disclosure is that in the process of normal communication interaction of the base station, the fault log at the time of failure is collected in real time, thereby providing time for analyzing the content of the fault log, and all processes have high automation characteristics and improve the base station. Operational safety and stability.
  • FIG. 1 is a flowchart of a base station operation and maintenance method according to an embodiment of the present disclosure, including:
  • the network management server is a unified management platform for wireless access network elements. It mainly has configuration management, fault, performance, topology, software, security, and measurement functions. Among them, the quality measurement tools mainly use signaling tracking and data collection.
  • the operation and maintenance of the base station is completed, and the stability of the base station can be effectively improved through the maintenance test tool, and the operation and maintenance efficiency is improved.
  • a base station that is, a public mobile communication base station, is a form of a radio station, and refers to a radio transceiver station that transmits information between a mobile communication switching center and a mobile telephone terminal in a certain radio coverage area.
  • the construction of mobile communication base stations is an important part of the investment of mobile communication operators.
  • the network management server needs to manage the operation and maintenance of the base station. First, a communication connection is established between the network management server and the base station, that is, the network management server and the base station have successfully handshaked, and the subsequent management process can be performed. After the network management server and the base station are successfully handshaked, the network management server automatically sends a log collection task to the base station.
  • a log collection task that is sent by the network management server to the base station is determined.
  • the log collection task is mainly related to the parameters of the log collection task.
  • the related parameters of the log collection task may include: 1. Observing an object, that is, which events are tracked by the log collection task, and which abnormal events are regarded as involved in the log collection task, for example, a specific abnormality Events may include: RNLU (Radio Network User Plane Subsystem) voice anomaly, CMAC (Control Mobile Attenuation Code) voice anomaly, DCM (Data Communication Module) related access anomaly, ERAB (Evolved Radio Access Bearer) setup failure, ERAB One or more of the dropped calls, handover failures, and the like, or other anomalous events that are applicable in this embodiment.
  • RNLU Radio Network User Plane Subsystem
  • CMAC Control Mobile Attenuation Code
  • DCM Data Communication Module
  • ERAB Evolved Radio Access Bearer
  • the task tracking time indicates when the fault log collection involved in the log collection task starts from, and at what time.
  • the time setting may be set according to the natural time, or may be based on the time when the log collection task is sent, the task starts after the preset duration, and the task ends after the preset duration, or, in particular, according to the type of the abnormal event.
  • To determine the start time and end time when an abnormal event occurs, the fault log is collected; when an abnormal event occurs, the fault log is collected again.
  • the advantage of this setting is that it can locate the fault more accurately and save system resources to a certain extent.
  • the reporting mode includes the normal mode and the CMAC only reporting mode.
  • the normal module UE (user equipment) is selected by the TOOL (tool) module.
  • the base station reports the signaling, RNLU and CMAC log files of the UE.
  • the CMAC reporting mode the UE selects to be processed by the CMAC.
  • the CMAC module reports the data. If only the abnormal data reported by the CMAC is required, the CMAC abnormal data is more comprehensive and accurate.
  • Log server information that is, FTP (File Transfer Protocol) information when the fault log is reported.
  • Table 1 shows the types of various abnormal events, the names of abnormal events, the corresponding trigger modules and corresponding acquisition data modules.
  • the method may further include: determining a relevant parameter of the log collection task to be delivered, and generating a log collection task according to the relevant parameter;
  • the task is sent to the base station.
  • the operation and maintenance personnel can define the log collection task.
  • the operation and maintenance personnel can determine the relevant parameters in the log collection task to be delivered, including the above observations.
  • the object, the task tracking time, the reporting mode, and the log server information are generated, and then the corresponding log collection task is generated according to the relevant parameters, and the generated log collection task is sent to the base station, and the base station can perform the fault log according to the log collection task. Collection process.
  • the fault log is collected according to relevant parameters in the log collection task.
  • the base station can collect the fault log according to the relevant parameters. For example, the task tracking time is determined, and the fault log is collected at the start time of the log collection task; the observation object is determined, and the fault log is automatically collected when the abnormality corresponding to the observed object occurs; the process of automatically collecting the fault log is generally In the case of some abnormal events, some abnormal events will affect the normal operation of the base station, resulting in the base station being out of service. At this time, the maintenance is directly sought, and the tasks of the base station can be temporarily taken over by other base stations; The abnormal event does not affect the normal operation of the base station.
  • the log collection task continues to take effect, and the base station continues to automatically collect the fault log.
  • the collection process of the log collection task is ended.
  • the collection process of the fault log for the log collection task is continuous. In the long-term process, during the collection process, the acquisition can be stopped at any time according to the instructions input by the network management server.
  • collecting the fault log may include: detecting an interaction log generated by the base station during the interaction process; and when an abnormal event occurs in the interaction log, collecting an interaction log within a preset scope of the abnormal event context as the fault log.
  • the abnormal event is the abnormal event shown in the foregoing Table 1, and the corresponding abnormal event may be determined according to the type information of the abnormal event; the interaction log in the process of the base station interaction generally refers to an interaction log between the base station and the UE. It may also include an interaction log generated during the self-operation and maintenance of the base station, and may even include an interaction log generated by data interaction between the base station and the network management server, etc.; in these logs, the type corresponding to the abnormal event is detected.
  • the code collects the interaction log within the preset scope of the exception event context as a fault log.
  • the interactive log in the preset range refers to the log in the preset field range.
  • Different preset ranges can be set for different abnormal events according to different types of abnormal events. For some abnormal events, it may be more complicated.
  • the preset range is set to be wider; for some abnormal events, the preset range can be set narrower.
  • the preset range setting can significantly improve the positioning accuracy of the fault, and can also help to troubleshoot the specific cause of the fault.
  • the base station operation and maintenance method may further include: reporting the fault log to the log server.
  • the fault log can also be used for: the log server generates notification information according to the fault log and sends the notification information.
  • the fault log is collected to facilitate the troubleshooting of the O&M personnel and solve the operation and maintenance of the base station to ensure the normal operation of the base station.
  • an exemplary notification manner is: First, the fault log is uploaded to the log server. The log server detects the report of the fault log and generates notification information based on the fault log and sends it to the O&M personnel.
  • the notification information can be generated and sent to the operation and maintenance personnel by means of short messages, telephone calls, voice messages, emails, etc., and the operation and maintenance personnel can perform fault diagnosis of the base station according to this, find out the cause of the base station failure and repair it, thereby ensuring the normal operation of the base station.
  • the reporting of the fault log to the log server may include: compressing the fault log and reporting the fault log to the log server by using a file transfer protocol.
  • the fault of the base station is processed according to the analysis result of the fault log.
  • the operation and maintenance personnel will give the possible causes of the fault according to the information contained in the fault log and the information about the distribution of different signaling, and under the action of the signaling analysis system.
  • the fault of the base station is checked, and the cause of the fault is finally locked, and the fault is repaired according to the reason.
  • the process of repairing the fault is uncertain. At this stage, it is usually done by manpower.
  • This embodiment provides a base station operation and maintenance method, which determines a log collection task that is sent by the network management server to the base station, collects a fault log according to relevant parameters in the log collection task, and processes the fault of the base station according to the analysis result of the fault log.
  • the fault log of the base station is automatically collected in real time during the operation and maintenance of the base station, and the fault is not used to recover the fault, thereby reducing the occupation and loss of system resources and improving the security of the base station. Sex and stability.
  • FIG. 2 is a schematic structural diagram of a base station operation and maintenance device according to an embodiment of the present disclosure, including:
  • the determining module 201 is configured to determine a log collection task that is sent by the network management server to the base station;
  • the collecting module 202 is configured to collect a fault log according to relevant parameters in the log collection task.
  • the processing module 203 is configured to process the failure of the base station according to the analysis result of the fault log.
  • the network management server is a unified management platform for wireless access network elements. It mainly has configuration management, fault, performance, topology, software, security, and measurement functions. Among them, the quality measurement tools mainly use signaling tracking and data collection.
  • the operation and maintenance of the base station is completed, and the stability of the base station can be effectively improved through the maintenance test tool, and the operation and maintenance efficiency is improved.
  • a base station that is, a public mobile communication base station, is a form of a radio station, and refers to a radio transceiver station that transmits information between a mobile communication switching center and a mobile telephone terminal in a certain radio coverage area.
  • the construction of mobile communication base stations is an important part of the investment of mobile communication operators.
  • the network management server needs to manage the operation and maintenance of the base station. First, a communication connection is established between the network management server and the base station, that is, the network management server and the base station have successfully handshaked, and the subsequent management process can be performed. After the network management server and the base station are successfully handshaked, the network management server automatically sends a log collection task to the base station.
  • the determining module 201 is configured to determine a log collection task that is sent by the network management server to the base station.
  • the log collection task is mainly related to the parameters of the log collection task.
  • the related parameters of the log collection task may include: 1. Observing an object, that is, which events are tracked by the log collection task, and which abnormal events are regarded as involved in the log collection task, for example, a specific abnormality
  • the event may include: one or more of RNLU voice anomaly, CMAC voice anomaly, DCM related access exception, ERAB establishment failure, ERAB drop call, handover failure, etc., or other applicable in this embodiment.
  • Anomalous event may include: one or more of RNLU voice anomaly, CMAC voice anomaly, DCM related access exception, ERAB establishment failure, ERAB drop call, handover failure, etc., or other applicable in this embodiment. Anomalous event. 2.
  • the task tracking time indicates when the fault log collection involved in the log collection task starts from, and at what time.
  • the time setting may be set according to the natural time, or may be based on the time when the log collection task is sent, the task starts after the preset duration, and the task ends after the preset duration, or, in particular, according to the type of the abnormal event.
  • To determine the start time and end time when an abnormal event occurs, the fault log is collected; when an abnormal event occurs, the fault log is collected again.
  • the advantage of this setting is that it can locate the fault more accurately and save system resources to a certain extent. 3.
  • the reporting mode includes the normal mode and the CMAC only reporting mode.
  • the normal module UE is selected to be processed by the TOOL module. After the abnormal triggering, the base station reports the signaling of the UE, the log files of the RNLU and the CMAC, and the like, and only the CMAC reporting mode. The UE selects to be processed by the CMAC. When the exception is triggered, only the CMAC module reports the data. If only the abnormal data reported by the CMAC is required, the CMAC abnormal data is more comprehensive and accurate. 4. Log server information, that is, FTP information when the fault log is reported.
  • the base station operation and maintenance apparatus may further include: a generating module 206, configured to determine a relevant parameter of the log collection task to be delivered, and generate a log collection task according to the relevant parameter; Set to send the log collection task to the base station.
  • the operation and maintenance personnel can define the log collection task. The operation and maintenance personnel can determine the relevant parameters in the log collection task to be delivered, including the above observations. The object, the task tracking time, the reporting mode, and the log server information are generated, and then the corresponding log collection task is generated according to the relevant parameters, and the generated log collection task is sent to the base station, and the base station can perform the fault log according to the log collection task. Collection process.
  • the collection module 202 is configured to collect a fault log according to relevant parameters in the log collection task.
  • the base station can collect the fault log according to the relevant parameters. For example, the task tracking time is determined, and the fault log is collected at the start time of the log collection task; the observation object is determined, and the fault log is automatically collected when the abnormality corresponding to the observed object occurs; the process of automatically collecting the fault log is generally In the case of some abnormal events, some abnormal events will affect the normal operation of the base station, resulting in the base station being out of service. At this time, the maintenance is directly sought, and the tasks of the base station can be temporarily taken over by other base stations; The abnormal event does not affect the normal operation of the base station.
  • the log collection task continues to take effect, and the base station continues to automatically collect the fault log.
  • the collection process of the log collection task is ended.
  • the collection process of the fault log for the log collection task is continuous. In the long-term process, during the collection process, the acquisition can be stopped at any time according to the instructions input by the network management server.
  • the collection module 202 may be specifically configured to: detect an interaction log generated by the base station during the interaction process; and when an abnormal event occurs in the interaction log, collect an interaction log within a preset scope of the abnormal event context as the fault log. .
  • the abnormal event is the abnormal event shown in the foregoing Table 1, and the corresponding abnormal event may be determined according to the type information of the abnormal event; the interaction log in the process of the base station interaction generally refers to an interaction log between the base station and the UE. It may also include an interaction log generated during the self-operation and maintenance of the base station, and may even include an interaction log generated by data interaction between the base station and the network management server, etc.; in these logs, the type corresponding to the abnormal event is detected.
  • the code collects the interaction log within the preset scope of the exception event context as a fault log.
  • the interactive log in the preset range refers to the log in the preset field range.
  • Different preset ranges can be set for different abnormal events according to different types of abnormal events. For some abnormal events, it may be more complicated.
  • the preset range is set to be wider; for some abnormal events, the preset range can be set narrower.
  • the preset range setting can significantly improve the positioning accuracy of the fault, and can also help to troubleshoot the specific cause of the fault.
  • the base station operation and maintenance apparatus may further include: a reporting module 204, configured to report the fault log to the log server.
  • the log server generates notification information based on the fault log and sends it out.
  • the fault log is collected to facilitate the troubleshooting of the O&M personnel and solve the operation and maintenance of the base station to ensure the normal operation of the base station.
  • an exemplary notification manner is: First, the fault log is uploaded to the log server. The log server detects the report of the fault log and generates notification information based on the fault log and sends it to the O&M personnel.
  • the notification information can be generated and sent to the operation and maintenance personnel by means of short messages, telephone calls, voice messages, emails, etc., and the operation and maintenance personnel can perform fault diagnosis of the base station according to this, find out the cause of the base station failure and repair it, thereby ensuring the normal operation of the base station.
  • the reporting of the fault log to the log server may include: compressing the fault log and reporting the fault log to the log server by using a file transfer protocol.
  • the processing module 203 is configured to process the failure of the base station according to the analysis result of the fault log. After the base station collects the fault log, the operation and maintenance personnel will give the possible causes of the fault according to the information contained in the fault log and the information about the distribution of different signaling, and under the action of the signaling analysis system. The fault of the base station is checked, and the cause of the fault is finally locked, and the fault is repaired according to the reason. The process of repairing the fault is uncertain. At this stage, it is usually done by manpower. Some simple faults can also be solved by the base station.
  • the embodiment of the present invention provides a base station operation and maintenance device, which determines a log collection task that is sent by the network management server to the base station, collects a fault log according to relevant parameters in the log collection task, and processes the fault of the base station according to the analysis result of the fault log.
  • the fault log of the base station is automatically collected in real time during the operation and maintenance of the base station, and the fault is not used to recover the fault, thereby reducing the occupation and loss of system resources and improving the security of the base station. Sex and stability.
  • FIG. 3 is a flowchart of another base station operation and maintenance method according to an embodiment of the present disclosure, including:
  • S302 The network management server sends the log collection task to the base station.
  • the network management server needs to manage the operation and maintenance of the base station. First, a communication connection is established between the network management server and the base station, that is, the network management server and the base station have successfully handshaked, and the subsequent management process can be performed. After the network management server and the base station are successfully handshaked, the network management server automatically sends a log collection task to the base station.
  • the log server generates notification information according to the fault log and sends the notification information.
  • the log server detects the report of the fault log and generates the notification information based on the fault log.
  • the notification information can be generated and sent to the operation and maintenance personnel by means of SMS, telephone, voice message, or email.
  • FIG. 4 is a flowchart of still another method for operating a base station according to an embodiment of the present disclosure, including:
  • S401 Determine, according to actual operation and maintenance requirements, relevant parameters of the log collection task to be delivered;
  • the network management server sends the log collection task to the base station.
  • the network management server needs to manage the operation and maintenance of the base station. First, a communication connection is established between the network management server and the base station, that is, the network management server and the base station have successfully handshaked, and the subsequent management process can be performed. After the network management server and the base station are successfully handshaked, the network management server sends a log collection task to the base station.
  • the log server generates notification information according to the fault log and sends the notification information.
  • the log server detects the report of the fault log and generates the notification information based on the fault log.
  • the notification information can be generated and sent to the operation and maintenance personnel by means of SMS, telephone, voice message, or email.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement the methods described above.
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .
  • the present disclosure provides a base station operation and maintenance method and apparatus.
  • the method includes: determining a log collection task sent by a network management server to a base station, collecting a fault log according to relevant parameters in the log collection task, and analyzing the fault log according to the fault log. , handling the failure of the base station.
  • the fault log of the base station is automatically collected in real time during the operation and maintenance of the base station, and the fault is not used to recover the fault, thereby reducing the occupation and loss of system resources and improving the security of the base station operation. And stability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本公开提供了一种基站运维方法和装置，所述方法包括：确定网管服务器下发到基站的日志采集任务，根据日志采集任务中的相关参数，收集故障日志，根据对故障日志的分析结果，处理基站的故障。

Description

一种基站运维方法和装置 技术领域
本公开涉及无线网络管理领域，尤其涉及一种基站运维方法和装置。
背景技术
传统的无线基站运维方式，大部分是基于一种复现式的、后知后觉的定位手段。确定主要有：1、定位一些难以复现的、复杂的系统性问题成本太高，尤其是在复杂特殊场景下才会出现的问题。2、复现问题的过程中，抓取的海量日志文件(log)也及其影响后续的log分析效率，占用大量的人力和时间。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
针对基站故障难以复现、传统的基站运维方式采集日志数据冗余、自动化程度差的问题，本公开实施例提供了一种基站运维方法和装置。
本公开实施例提供了一种基站运维方法，包括：
确定网管服务器下发到基站的日志采集任务；
根据所述日志采集任务中的相关参数，收集故障日志；
根据对所述故障日志的分析结果，处理所述基站的故障。
此外，本公开实施例还提供一种基站运维装置，包括：
确定模块，设置为确定网管服务器所下发的日志采集任务；
采集模块，设置为根据所述日志采集任务中的相关参数，收集故障日志；
处理模块，设置为根据对所述故障日志的分析结果，处理所述基站的故障。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现以上描述的方法。
本公开的有益效果是：
本公开提供了一种基站运维方法和装置，所述方法包括，确定网管服务器下发到基站的日志采集任务，根据日志采集任务中的相关参数，收集故障日志，根据对故障日志的分析结果，处理基站的故障。通过本公开的实施，实现了在基站运维过程中就实时自动的采集基站的故障日志，不用通过复现的形式来排查故障，减少了系统资源的占用和损耗，提高了基站运行的安全性和稳定性。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图说明
图1为本公开实施例提供的一种基站运维方法流程图；
图2为本公开实施例提供的一种基站运维装置组成示意图；
图3为本公开实施例提供的另一种基站运维方法流程图；
图4为本公开实施例提供的又一种基站运维方法流程图。
具体实施方式
本公开的构思点在于，在基站正常通信交互的过程中，就实时的采集出现故障时的故障日志，从而为分析故障日志的内容提供了时间，所有的过程具有高度的自动化特点，提高了基站运行的安全度和稳定性。
下面结合附图对本公开的具体实施方式作进一步说明。
第一示例
请参考图1，图1是本公开实施例提供的一种基站运维方法流程图，包括：
S101、确定网管服务器下发到基站的日志采集任务；
S102、根据日志采集任务中的相关参数，收集故障日志；
S103、根据对故障日志的分析结果，处理基站的故障。
网管服务器是无线接入网网元统一管理的管理平台，主要具有配置管 理、故障、性能、拓扑、软件、安全、维测等功能，其中，维测工具主要通过信令跟踪、数据采集等方式完成基站运维工作，通过维测工具可以有效地提升基站的稳定性，提高运维效率。基站即公用移动通信基站，是无线电台站的一种形式，是指在一定的无线电覆盖区内，通过移动通信交换中心，与移动电话终端之间进行信息传递的无线电收发信电台。移动通信基站的建设是移动通信运营商投资的重要组成部分。
网管服务器要对基站的运维进行管理，首先，网管服务器和基站之间要建立通信连接，即网管服务器和基站握手成功，方能进行后续的管理流程。在网管服务器和基站握手成功后，网管服务器自动的向基站下发日志采集任务。
S101中，确定网管服务器下发到基站的日志采集任务。其中，确定日志采集任务主要是指，日志采集任务的相关参数。在本实施例中，日志采集任务的相关参数可以包括：1、观察对象，即该日志采集任务跟踪哪些事件，哪些异常事件被视为是本次日志采集任务所涉及的，比如，具体的异常事件可以包括：RNLU(无线网络用户面子系统)语音异常，CMAC(控制移动衰减码)语音异常，DCM(数据通信模块)相关的接入异常，ERAB(演进的无线接入承载)建立失败，ERAB掉话、切换失败等等事件中的一个或多个，或者其他在本实施例中可适用的其他异常事件。2、任务跟踪时间，包括本次日志采集任务的开始时间和结束时间，表示该日志采集任务所涉及的故障日志采集是从什么时刻开始，并以什么时刻结束。其中，时间的设置可以根据自然时间设置，也可以以下发日志采集任务的时间为基准，预设时长后任务开始，并在预设时长后任务结束，或者，特别的，可以根据异常事件的类型来确定开始时间和结束时间，当某个异常事件出现的时候，开始进行故障日志的采集；当某个异常事件出现的时候，再结束故障日志的采集。这样设置的好处在于，可以更为精确的定位故障所在，并在一定程度上节约系统资源。3、上报模式，上报模式包括普通模式和仅CMAC上报模式，普通模块UE(用户设备)选择由TOOL(工具)模块处理，异常触发后，基站会上报UE的信令、RNLU和CMAC的日志文件等；而仅CMAC上报模式，UE选择由CMAC处理，异常触发时，仅CMAC模块上报数据。如果仅仅 需要CMAC上报的异常数据，使用仅CMAC上报方式，跟踪的CMAC异常数据更为全面和精确。4、日志服务器信息，即上报故障日志时的FTP(文件传输协议)信息。关于本实施例中的异常事件，请参考表1，表1示出了各种异常事件的类型、异常事件的名称、相应的触发模块和对应的采集数据模块。
表1
Figure PCTCN2018084745-appb-000001
Figure PCTCN2018084745-appb-000002
此外，在本实施例中，在确定网管服务器下发到基站的日志采集任务之前，还可以包括：确定待下发的日志采集任务的相关参数，并根据相关参数生成日志采集任务；将日志采集任务下发到基站。除了可以网管服务器自动下发日志采集任务之外，还可以由运维人员自行定义日志采集任务，运维人员可以根据实际需求，确定待下发的日志采集任务中的相关参数，包括上述的观察对象、任务跟踪时间、上报模式和日志服务器信息等等，然后根据这些相关参数，生成相应的日志采集任务，将生成的日志采集任务下发给基站，基站就可以根据这个日志采集任务进行故障日志的采集流程。
S102中，根据日志采集任务中的相关参数，收集故障日志。基站在接收到日志采集任务，并确定其中的相关参数后，就可以根据这些相关参数，来相应的进行故障日志的采集。比如，确定任务跟踪时间，并在日志采集任务的开始时间开始对故障日志的采集；确定观察对象，在观察对象所对应的异常出现的情况下，自动采集故障日志；自动采集故障日志的过程一般而言会持续一段时间，在出现一些异常事件时，有的异常事件会影响基站的正常运行，从而导致基站停运，此时则直接寻求维护，该基站的任务则暂时可由其他基站接管；有的异常事件则不会影响基站的正常运行，那么，日志采集任务继续生效，基站则继续自动采集故障日志。根据上报模式的不同选择相应的模式，比如普通模式，或者仅CMAC上报模式等等；在日志采集任务的结束时间，结束本次日志采集任务的采集过程。针对日志采集任务进行的故障日志的采集过程是持续的，长期的，在采集的过程中，也可以根据网管服务器输入的指令随时中止采集、继续采集等等。
在本实施例中，收集故障日志具体可以包括：检测基站在交互过程中所产生的交互日志；当交互日志中出现异常事件时，采集异常事件上下文预设 范围内的交互日志，作为故障日志。其中，异常事件就是前述表1中所示的那些异常事件，可以根据异常事件的类型信息确定相应的异常事件；基站交互过程中的交互日志，一般是指基站和UE之间交互的交互日志，还可以包括基站自行运维过程中所产生的交互日志，甚至还可以包括，基站和网管服务器之间数据交互所产生的交互日志等等；当在这些日志中，检测到了异常事件所对应的类型代码，那么，就采集这个异常事件上下文预设范围内的交互日志，作为故障日志。预设范围内的交互日志指的是预设字段范围内的日志，可以根据不同的异常事件的类型，对不同的异常事件设置不同的预设范围，对于某些异常事件比较复杂的，可以将预设范围设置得较宽；对于某些异常事件比较简单的，可以将预设范围设置得较窄。预设范围的设置可以显著提升故障的定位精度，还可以帮助排查故障的具体原因。
在本实施例中，在收集故障日志之后，所述基站运维方法还可以包括：将故障日志上报到日志服务器。其中，故障日志还可以用于：日志服务器根据故障日志生成通知信息并外发。故障日志的采集，是为了便于后期运维人员进行故障排查，解决基站的运维问题，从而保证基站的正常运行。在本实施例中，一种示例性的通知方式是：首先，将故障日志上传给日志服务器。日志服务器检测到有故障日志的上报，根据故障日志，生成通知信息并发送给运维人员。通知信息可以以短信、电话、语音留言、邮件等方式生成并发送给运维人员，运维人员则据此进行基站的故障排查，找出基站故障的原因并修复，从而保证基站的正常运行。
其中，将故障日志上报到日志服务器可以包括：将故障日志进行压缩，并以文件传输协议上报到日志服务器。
S103中，根据对故障日志的分析结果，处理基站的故障。在基站采集故障日志之后，运维人员就根据故障日志中所包含的信息，根据其中不同信令的分布情况等等信息，给出出现故障的可能的原因，并在信令分析系统的作用下，对基站的故障进行排查，最终锁定故障的原因，并根据该原因对故障进行修复。修复故障的过程则是不定的，在现阶段一般要借助人力才能完成，一些简单的故障也可以由基站自行解决。
本实施例提供了一种基站运维方法，确定网管服务器下发到基站的日志 采集任务，根据日志采集任务中的相关参数，收集故障日志，根据对故障日志的分析结果，处理基站的故障。通过本实施例的实施，实现了在基站运维过程中就实时自动的采集基站的故障日志，不用通过复现的形式来排查故障，减少了系统资源的占用和损耗，提高了基站运行的安全性和稳定性。
第二示例
请参考图2，图2是本公开实施例提供的一种基站运维装置组成示意图，包括：
确定模块201，设置为确定网管服务器下发到基站的日志采集任务；
采集模块202，设置为根据日志采集任务中的相关参数，收集故障日志；
处理模块203，设置为根据对故障日志的分析结果，处理基站的故障。
网管服务器是无线接入网网元统一管理的管理平台，主要具有配置管理、故障、性能、拓扑、软件、安全、维测等功能，其中，维测工具主要通过信令跟踪、数据采集等方式完成基站运维工作，通过维测工具可以有效地提升基站的稳定性，提高运维效率。基站即公用移动通信基站，是无线电台站的一种形式，是指在一定的无线电覆盖区内，通过移动通信交换中心，与移动电话终端之间进行信息传递的无线电收发信电台。移动通信基站的建设是移动通信运营商投资的重要组成部分。
网管服务器要对基站的运维进行管理，首先，网管服务器和基站之间要建立通信连接，即网管服务器和基站握手成功，方能进行后续的管理流程。在网管服务器和基站握手成功后，网管服务器自动的向基站下发日志采集任务。
在本实施例中，确定模块201设置为确定网管服务器下发到基站的日志采集任务。其中，确定日志采集任务主要是指，日志采集任务的相关参数。在本实施例中，日志采集任务的相关参数可以包括：1、观察对象，即该日志采集任务跟踪哪些事件，哪些异常事件被视为是本次日志采集任务所涉及的，比如，具体的异常事件可以包括：RNLU语音异常，CMAC语音异常，DCM相关的接入异常，ERAB建立失败，ERAB掉话、切换失败等等事件中的一个或多个，或者其他在本实施例中可适用的其他异常事件。2、任务 跟踪时间，包括本次日志采集任务的开始时间和结束时间，表示该日志采集任务所涉及的故障日志采集是从什么时刻开始，并以什么时刻结束。其中，时间的设置可以根据自然时间设置，也可以以下发日志采集任务的时间为基准，预设时长后任务开始，并在预设时长后任务结束，或者，特别的，可以根据异常事件的类型来确定开始时间和结束时间，当某个异常事件出现的时候，开始进行故障日志的采集；当某个异常事件出现的时候，再结束故障日志的采集。这样设置的好处在于，可以更为精确的定位故障所在，并在一定程度上节约系统资源。3、上报模式，上报模式包括普通模式和仅CMAC上报模式，普通模块UE选择由TOOL模块处理，异常触发后，基站会上报UE的信令、RNLU和CMAC的日志文件等；而仅CMAC上报模式，UE选择由CMAC处理，异常触发时，仅CMAC模块上报数据。如果仅仅需要CMAC上报的异常数据，使用仅CMAC上报方式，跟踪的CMAC异常数据更为全面和精确。4、日志服务器信息，即上报故障日志时的FTP信息。
此外，在本实施例中，所述基站运维装置还可以包括：生成模块206，设置为确定待下发的日志采集任务的相关参数，并根据相关参数生成日志采集任务；下发模块207，设置为将日志采集任务下发到基站。除了可以网管服务器自动下发日志采集任务之外，还可以由运维人员自行定义日志采集任务，运维人员可以根据实际需求，确定待下发的日志采集任务中的相关参数，包括上述的观察对象、任务跟踪时间、上报模式和日志服务器信息等等，然后根据这些相关参数，生成相应的日志采集任务，将生成的日志采集任务下发给基站，基站就可以根据这个日志采集任务进行故障日志的采集流程。
在本实施例中，采集模块202设置为根据日志采集任务中的相关参数，收集故障日志。基站在接收到日志采集任务，并确定其中的相关参数后，就可以根据这些相关参数，来相应的进行故障日志的采集。比如，确定任务跟踪时间，并在日志采集任务的开始时间开始对故障日志的采集；确定观察对象，在观察对象所对应的异常出现的情况下，自动采集故障日志；自动采集故障日志的过程一般而言会持续一段时间，在出现一些异常事件时，有的异常事件会影响基站的正常运行，从而导致基站停运，此时则直接寻求维护，该基站的任务则暂时可由其他基站接管；有的异常事件则不会影响基站的正 常运行，那么，日志采集任务继续生效，基站则继续自动采集故障日志。根据上报模式的不同选择相应的模式，比如普通模式，或者仅CMAC上报模式等等；在日志采集任务的结束时间，结束本次日志采集任务的采集过程。针对日志采集任务进行的故障日志的采集过程是持续的，长期的，在采集的过程中，也可以根据网管服务器输入的指令随时中止采集、继续采集等等。
在本实施例中，采集模块202具体可以设置为：检测基站在交互过程中所产生的交互日志；当交互日志中出现异常事件时，采集异常事件上下文预设范围内的交互日志，作为故障日志。其中，异常事件就是前述表1中所示的那些异常事件，可以根据异常事件的类型信息确定相应的异常事件；基站交互过程中的交互日志，一般是指基站和UE之间交互的交互日志，还可以包括基站自行运维过程中所产生的交互日志，甚至还可以包括，基站和网管服务器之间数据交互所产生的交互日志等等；当在这些日志中，检测到了异常事件所对应的类型代码，那么，就采集这个异常事件上下文预设范围内的交互日志，作为故障日志。预设范围内的交互日志指的是预设字段范围内的日志，可以根据不同的异常事件的类型，对不同的异常事件设置不同的预设范围，对于某些异常事件比较复杂的，可以将预设范围设置得较宽；对于某些异常事件比较简单的，可以将预设范围设置得较窄。预设范围的设置可以显著提升故障的定位精度，还可以帮助排查故障的具体原因。
在本实施例中，所述基站运维装置还可以包括：上报模块204，设置为将故障日志上报到日志服务器。日志服务器则根据故障日志生成通知信息并外发。故障日志的采集，是为了便于后期运维人员进行故障排查，解决基站的运维问题，从而保证基站的正常运行。在本实施例中，一种示例性的通知方式是：首先，将故障日志上传给日志服务器。日志服务器检测到有故障日志的上报，根据故障日志，生成通知信息并发送给运维人员。通知信息可以以短信、电话、语音留言、邮件等方式生成并发送给运维人员，运维人员则据此进行基站的故障排查，找出基站故障的原因并修复，从而保证基站的正常运行。
其中，将故障日志上报到日志服务器可以包括：将故障日志进行压缩，并以文件传输协议上报到日志服务器。
在本实施例中，处理模块203设置为根据对故障日志的分析结果，处理基站的故障。在基站采集故障日志之后，运维人员就根据故障日志中所包含的信息，根据其中不同信令的分布情况等等信息，给出出现故障的可能的原因，并在信令分析系统的作用下，对基站的故障进行排查，最终锁定故障的原因，并根据该原因对故障进行修复。修复故障的过程则是不定的，在现阶段一般要借助人力才能完成，一些简单的故障也可以由基站自行解决。
本实施例提供了一种基站运维装置，确定网管服务器下发到基站的日志采集任务，根据日志采集任务中的相关参数，收集故障日志，根据对故障日志的分析结果，处理基站的故障。通过本实施例的实施，实现了在基站运维过程中就实时自动的采集基站的故障日志，不用通过复现的形式来排查故障，减少了系统资源的占用和损耗，提高了基站运行的安全性和稳定性。
第三示例
请参考图3，图3为本公开实施例提供的另一种基站运维方法流程图，包括：
S301、网管服务器自动生成日志采集任务；
S302、网管服务器将日志采集任务下发给基站；
网管服务器要对基站的运维进行管理，首先，网管服务器和基站之间要建立通信连接，即网管服务器和基站握手成功，方能进行后续的管理流程。在网管服务器和基站握手成功后，网管服务器自动的向基站下发日志采集任务。
S303、根据日志采集任务中的相关参数，收集故障日志；
确定日志采集任务中的相关参数，包括观察对象、任务跟踪时间、上报模式和日志服务器信息等等，并根据这些相关参数进行故障日志的采集。
S304、将故障日志上报给日志服务器；
S305、日志服务器根据故障日志生成通知信息并外发；
日志服务器检测到有故障日志的上报，根据故障日志，生成通知信息并外发；通知信息可以以短信、电话、语音留言、邮件等方式生成并发送给运维人员。
S306、根据通知信息，对基站的故障进行定位并尝试修复。
第四示例
请参考图4，图4为本公开实施例提供的又一种基站运维方法流程图，包括：
S401、根据实际运维需求，确定待下发的日志采集任务的相关参数；
确定日志采集任务中的相关参数，包括观察对象、任务跟踪时间、上报模式和日志服务器信息等等。
S402、根据相关参数生成对应的日志采集任务；
S403、网管服务器将日志采集任务下发给基站；
网管服务器要对基站的运维进行管理，首先，网管服务器和基站之间要建立通信连接，即网管服务器和基站握手成功，方能进行后续的管理流程。在网管服务器和基站握手成功后，网管服务器向基站下发日志采集任务。
S404、根据日志采集任务中的相关参数，收集故障日志；
确定日志采集任务中的相关参数，包括观察对象、任务跟踪时间、上报模式和日志服务器信息等等，并根据这些相关参数进行故障日志的采集。
S405、将故障日志上报给日志服务器；
S406、日志服务器根据故障日志生成通知信息并外发；
日志服务器检测到有故障日志的上报，根据故障日志，生成通知信息并外发；通知信息可以以短信、电话、语音留言、邮件等方式生成并发送给运维人员。
S407、根据通知信息，对基站的故障进行定位并尝试修复。
本公开实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现以上描述的方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能， 或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上内容是结合具体的实施方式对本公开所作的进一步详细说明，不能认定本公开的具体实施只局限于这些说明。对于本公开所属技术领域的普通技术人员来说，在不脱离本公开构思的前提下，还可以做出若干简单推演或替换，都被视为属于本公开的保护范围。
工业实用性
本公开提供了一种基站运维方法和装置，所述方法包括，确定网管服务器下发到基站的日志采集任务，根据日志采集任务中的相关参数，收集故障日志，根据对故障日志的分析结果，处理基站的故障。通过本公开的实施，实现了在基站运维过程中就实时自动的采集基站的故障日志，不用通过复现的形式来排查故障，减少了系统资源的占用和损耗，提高了基站运行的安全性和稳定性。

Claims (11)

  1. 一种基站运维方法，包括：
    确定网管服务器下发到基站的日志采集任务；
    根据所述日志采集任务中的相关参数，收集故障日志；
    根据对所述故障日志的分析结果，处理所述基站的故障。
  2. 如权利要求1所述的基站运维方法，其中，在所述收集故障日志之后，还包括：
    将所述故障日志上报到日志服务器。
  3. 如权利要求2所述的基站运维方法，其中，所述将所述故障日志上报到日志服务器包括：
    将所述故障日志进行压缩，并以文件传输协议上报到所述日志服务器。
  4. 如权利要求1-3任一项所述的基站运维方法，其中，在所述确定网管服务器下发到基站的日志采集任务之前，还包括：
    确定待下发的所述日志采集任务的相关参数，并根据所述相关参数生成所述日志采集任务；
    将所述日志采集任务下发到所述基站。
  5. 如权利要求1-3任一项所述的基站运维方法，其中，所述收集故障日志包括：
    检测所述基站在交互过程中所产生的交互日志；
    当所述交互日志中出现异常事件时，采集所述异常事件上下文预设范围内的交互日志，作为所述故障日志。
  6. 一种基站运维装置，包括：
    确定模块，设置为确定网管服务器所下发的日志采集任务；
    采集模块，设置为根据所述日志采集任务中的相关参数，收集故障日志；
    处理模块，设置为根据对所述故障日志的分析结果，处理所述基站的故障。
  7. 如权利要求6所述的基站运维装置，其中，还包括：
    上报模块，设置为将所述故障日志上报到日志服务器。
  8. 如权利要求7所述的基站运维装置，其中，所述上报模块还设置为：
    将所述故障日志进行压缩，并以文件传输协议上报到所述日志服务器。
  9. 如权利要求6-8任一项所述的基站运维装置，其中，还包括：
    生成模块，设置为确定待下发的日志采集任务的相关参数，并根据所述相关参数生成所述日志采集任务；
    下发模块，设置为将所述日志采集任务下发到基站。
  10. 如权利要求6-8任一项所述的基站运维装置，其中，所述采集模块还设置为：
    检测所述基站在交互过程中所产生的交互日志；
    当所述交互日志中出现异常事件时，采集所述异常事件上下文预设范围内的交互日志，作为所述故障日志。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现权利要求1-5中任一项所述的方法。
PCT/CN2018/084745 2017-05-08 2018-04-27 一种基站运维方法和装置 WO2018205850A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710323889.0A CN108882263A (zh) 2017-05-08 2017-05-08 一种基站运维方法和装置
CN201710323889.0 2017-05-08

Publications (1)

Publication Number Publication Date
WO2018205850A1 true WO2018205850A1 (zh) 2018-11-15

Family

ID=64104388

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/084745 WO2018205850A1 (zh) 2017-05-08 2018-04-27 一种基站运维方法和装置

Country Status (2)

Country Link
CN (1) CN108882263A (zh)
WO (1) WO2018205850A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022028017A1 (zh) * 2020-08-04 2022-02-10 浙江三维利普维网络有限公司 基站的数据上报方法、装置、电子装置和存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153664B (zh) * 2019-06-26 2024-05-31 中兴通讯股份有限公司 参数优化方法、装置、基站、服务器及存储介质
CN113839971A (zh) * 2020-06-08 2021-12-24 中兴通讯股份有限公司 采集数据的方法和网元管理器

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101102220A (zh) * 2007-07-24 2008-01-09 中兴通讯股份有限公司 一种在无线通讯系统中获取信息快照的方法
CN103596208A (zh) * 2013-11-15 2014-02-19 大唐移动通信设备有限公司 一种网元故障判断方法及系统
CN106488487A (zh) * 2015-08-27 2017-03-08 中兴通讯股份有限公司 故障检测方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007288579A (ja) * 2006-04-18 2007-11-01 Fujitsu Ltd 基地局ログ収集装置、基地局のログの収集方法、およびコンピュータプログラム
CN100341357C (zh) * 2004-07-07 2007-10-03 华为技术有限公司 基站日志上报系统及方法
CN103053192A (zh) * 2011-06-16 2013-04-17 华为技术有限公司 一种基站的故障检测方法及装置
CN104782162B (zh) * 2012-11-14 2019-04-26 华为技术有限公司 维护基站的方法、设备及系统
CN106507400A (zh) * 2015-09-08 2017-03-15 中兴通讯股份有限公司 一种故障定位方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101102220A (zh) * 2007-07-24 2008-01-09 中兴通讯股份有限公司 一种在无线通讯系统中获取信息快照的方法
CN103596208A (zh) * 2013-11-15 2014-02-19 大唐移动通信设备有限公司 一种网元故障判断方法及系统
CN106488487A (zh) * 2015-08-27 2017-03-08 中兴通讯股份有限公司 故障检测方法及装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022028017A1 (zh) * 2020-08-04 2022-02-10 浙江三维利普维网络有限公司 基站的数据上报方法、装置、电子装置和存储介质

Also Published As

Publication number Publication date
CN108882263A (zh) 2018-11-23

Similar Documents

Publication Publication Date Title
EP3386150B1 (en) Terminal failure processing method, device and system
WO2018205850A1 (zh) 一种基站运维方法和装置
WO2017041406A1 (zh) 一种故障定位方法及装置
CN112422344A (zh) 日志异常的告警方法、装置、存储介质及电子装置
EP1947806A1 (en) A method and system for service trace and service trace terminal, network element
CN101883374B (zh) 一种终端上报信息的方法及终端设备
CN112202635B (zh) 链路的监控方法、装置、存储介质以及电子装置
WO2012000387A1 (zh) 一种优化网络接入性能的方法、装置及系统
CN108199861B (zh) 一种机房管理方法及装置
CN105099791A (zh) 一种基于网络信令监测数据的终端故障定位方法和系统
CN108696376B (zh) 信令切换失败的故障排查方法和装置
Elmokashfi et al. Adding the next nine: An investigation of mobile broadband networks availability
CN111262624B (zh) 光缆故障的监控方法和装置
CN106792842A (zh) 一种短信通道监控方法及系统
CN102595455B (zh) 自动路测系统中测试模块的管理方法及装置
CN107920360B (zh) 一种定位网络问题的方法、装置及系统
US10334461B2 (en) System, device and method for testing app performance
CN106856599B (zh) 终端、检测服务器、短信收发故障检测方法及系统
JP2017521933A (ja) メッセージ処理方法及び装置
CN114710801B (zh) 网络性能的测评参数的处理方法、装置、存储介质及设备
CN112532486B (zh) 网络诊断的方法、电子设备、系统与可读存储介质
CN107371141B (zh) 一种垃圾信息监控方法、装置及通信系统
CN106488480B (zh) 一种工单引擎实现方法及装置
CN116415028A (zh) 录像数据补录方法、云存储服务器、系统及存储介质
WO2023185533A1 (zh) 一种探测处理方法、装置、系统、存储介质及电子装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18798458

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18798458

Country of ref document: EP

Kind code of ref document: A1