WO2013086996A1 - 故障处理方法、设备和系统 - Google Patents

故障处理方法、设备和系统 Download PDF

Info

Publication number
WO2013086996A1
WO2013086996A1 PCT/CN2012/086553 CN2012086553W WO2013086996A1 WO 2013086996 A1 WO2013086996 A1 WO 2013086996A1 CN 2012086553 W CN2012086553 W CN 2012086553W WO 2013086996 A1 WO2013086996 A1 WO 2013086996A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
base station
service
virtual base
reporting
Prior art date
Application number
PCT/CN2012/086553
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 WO2013086996A1 publication Critical patent/WO2013086996A1/zh

Links

Classifications

    • 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/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • 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
    • 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/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the base station network element is viewed from the base station controller side.
  • One base station is a logical network element, and the fault processing center is deployed on the single-station main control unit to perform correlation processing on all faults of the local station.
  • the embodiments of the present invention provide a fault processing method, device, and system, which can identify, report, and process service faults, thereby simplifying fault maintenance operations and reducing system load.
  • an embodiment of the present invention provides a fault reporting method, including:
  • the service fault monitoring module monitors whether a service fault occurs.
  • the service fault monitoring module fills the virtual base station ID value corresponding to the service fault in the virtual base station identifier attribute field included in the fault object of the service fault, and the virtual base station ID value corresponds to a virtual base station;
  • the service fault monitoring module reports the fault object filled with the virtual base station ID value.
  • a fault reporting device including:
  • a first monitoring unit configured to monitor whether a service failure occurs
  • An evaluation unit configured to: when the first monitoring unit monitors that a service failure occurs, in the virtual base station identifier attribute field included in the fault object of the service fault, fill the virtual base station ID value corresponding to the service fault, and the virtual base station ID value corresponds to one Virtual base station
  • the first reporting unit is configured to report a fault object that is filled with the virtual base station ID value.
  • an embodiment of the present invention provides a fault processing method, including:
  • the fault object includes a virtual base station identifier attribute field; determining whether the fault is a service fault according to whether the virtual base station identifier attribute field included in the fault object is valid;
  • the faulty object of the service fault is reported to the base station service fault processing center corresponding to the virtual base station identifier attribute field.
  • the embodiment of the invention provides a fault processing device, including:
  • a receiving unit configured to receive the reported fault object, where the fault object includes a virtual base station identifier attribute field;
  • the determining unit is configured to determine whether the fault is a service fault according to whether the virtual base station identifier attribute field included in the fault object is valid, and if the fault object attribute field is valid, determine that the fault is a service fault; if the fault object attribute field is determined to be invalid, The fault is determined as a fault of the device.
  • the third reporting unit is configured to report the fault of the service fault to the service fault processing center corresponding to the virtual base station identifier attribute field.
  • the embodiment of the present invention provides a fault processing system, including a fault reporting device and a fault processing device, where
  • the fault reporting device is the aforementioned fault reporting device
  • the fault handling device is the aforementioned fault handling device.
  • Fault reporting and processing method device and system provided by embodiments of the present invention, through service Faults are identified, reported, and processed to simplify fault maintenance operations and reduce system load.
  • FIG. 1 is a schematic flow chart of an embodiment of a fault reporting method according to the present invention.
  • FIG. 2 is a schematic flow chart of another embodiment of a fault reporting method according to the present invention.
  • FIG. 3 is a schematic structural diagram of an embodiment of a fault reporting device according to the present invention.
  • FIG. 4 is a schematic structural diagram of another embodiment of a fault reporting device according to the present invention.
  • FIG. 5 is a schematic flowchart diagram of another embodiment of a fault processing method according to the present invention.
  • FIG. 6 is a schematic structural diagram of another embodiment of a fault processing device according to the present invention.
  • FIG. 7 is a schematic structural diagram of another embodiment of a fault processing device according to the present invention.
  • FIG. 8 is a schematic flow chart of another embodiment of a fault processing method according to the present invention.
  • FIG. 9 is a schematic diagram of an embodiment of a fault handling system of the present invention.
  • FIG. 10 is a schematic diagram of another embodiment of a fault handling system of the present invention.
  • FIG. 1 is a schematic flowchart of a method for processing a fault according to an embodiment of the present invention, including: Step 11: The service monitoring module monitors whether a service fault occurs.
  • the fault can be classified into a service fault and a device fault.
  • the fault monitoring module can be divided into a service fault monitoring module and a device fault monitoring module.
  • the business fault monitoring module can be responsible for monitoring business faults, while the equipment fault monitoring module is responsible for monitoring equipment faults.
  • the service monitoring module can determine whether a service fault occurs according to the status of the service running. If a service fault occurs, go to step 12.
  • Step 12 The service fault monitoring module fills the virtual base station ID value corresponding to the service fault to the virtual base station identifier of the service fault object.
  • the fault object may include one or a combination of the following: fault ID, fault type, fault object location parameter length, fault actual parameter length, fault class ID, fault class instance ID, fault location parameter, fault detailed parameter, ticket list Board six-tuple, detection veneer six-tuple, etc.
  • the virtual base station identifier attribute that is, the virtual base station identifier, may be added to the fault object.
  • the specific implementation manner may be that a field is added to the data structure that expresses the fault object, and the initial value of the field may be an invalid value.
  • This attribute is an attribute added when the fault management mechanism defines the fault object.
  • Step 13 The service monitoring module reports the service fault object.
  • the service fault monitoring module may report the service fault object that is filled with the virtual base station ID value to the fault processing center by using the local fault reporting interface.
  • the type of the faulty service can be distinguished, and the subsequent fault reporting and processing is simplified.
  • the fault maintenance operation steps save system resources.
  • Step 21 The equipment fault monitoring module monitors whether a device fault occurs
  • the device fault monitoring module determines that the device is based on the operating state of the device monitored by the device. If the fault occurs, if the device fault monitoring module detects that the device is faulty, go to step 22. Further, when the fault object is initially defined, the virtual base station identifier can be added to all faulty objects. The initial default is invalid. When a service fault occurs, the corresponding service fault monitoring module fills the virtual base station ID value corresponding to the service to the virtual base station identifier, and the virtual base station identifier of the device fault does not add any content, and the value is always an invalid value.
  • Step 22 The device monitoring module reports the device fault object.
  • the device fault monitoring module can call the local fault reporting interface to report the device fault object to the fault handling center.
  • FIG. 3 is a schematic structural diagram of an embodiment of a fault processing apparatus according to the present invention, including a first monitoring unit 31, an evaluation unit 32, and a first upper unit 33:
  • a first monitoring unit 31 configured to monitor whether a service fault occurs
  • the value unit 32 is configured to: when the monitoring unit 31 monitors that a service failure occurs, in the virtual base station identifier attribute field included in the fault object of the service fault, the virtual base station ID value corresponding to the service fault is filled, and the virtual base station ID value corresponds to a virtual base station;
  • the first reporting unit 33 is configured to report a fault object filled with the virtual base station ID value.
  • the fault processing apparatus provided in this embodiment further includes the second monitoring unit 41 and the second upper unit 42 shown in FIG. 4:
  • a second monitoring unit 41 configured to monitor whether a device failure occurs
  • the second reporting unit 42 is configured to report the device fault object monitored by the second monitoring unit 41.
  • FIG. 5 is a schematic flowchart of another embodiment of a fault processing method according to the present invention, including:
  • Step 51 The fault processing center receives the reported fault object.
  • the fault processing center receives the fault object reported by the service fault monitoring module and the device fault monitoring module, and the reported fault object includes a virtual base station identifier attribute field.
  • Step 52 The fault diagnosis center determines whether the reported fault is a service fault.
  • the fault processing center is valid according to the virtual base station identifier value of the reported fault object. To determine whether the fault object is a service fault, and if the fault object virtual base station identifier value is valid, determine that the fault corresponding to the fault object is a service fault.
  • Step 53 The fault processing center reports the service fault object to the base station service fault processing center.
  • the fault processing center reports the service fault object to the service fault processing center corresponding to the virtual base station identifier attribute field of the service fault object.
  • the fault processing method of the embodiment further includes the step 54: if it is determined that the faulty object virtual base station identifier value is invalid, determining that the fault object is a device fault, reporting the device fault object to the base station equipment fault processing center.
  • the method provided by the embodiment of the present invention is to determine whether the fault corresponding to the fault object is a service fault according to the fault value of the virtual base station identifier of the fault object, and if the fault is a service, report the fault object to the base station service according to the faulty virtual base station identifier value.
  • the fault handling center distinguishes different types of faults and reports them to different base station processing centers for processing, which simplifies the fault maintenance operation steps and saves system resources.
  • FIG. 6 is a schematic structural diagram of another embodiment of a fault processing apparatus according to the present invention, including a receiving unit 61, a judging unit 62, and a third upper>3 ⁇ 4 unit 63:
  • the receiving unit 61 is configured to receive the reported fault object, where the fault object includes a virtual base station identifier attribute field;
  • the determining unit 62 is configured to determine whether the fault is a service fault according to whether the virtual base station identifier attribute field included in the fault object is valid, and if the fault object attribute field is valid, determine that the fault is a service fault; If the object attribute field is invalid, it is determined that the fault is a device fault;
  • the third reporting unit 63 is configured to report the faulty object of the service fault to the service fault processing center corresponding to the virtual base station identifier attribute field.
  • the fault processing device provided in this embodiment further includes a fourth reporting unit 71, which is included in FIG. 7, and is configured to report the fault object of the device fault to the base station equipment fault processing center.
  • FIG. 8 is a schematic flowchart of another embodiment of a fault processing method according to the present invention, where the method shown in the figure is a complete fault reporting process:
  • the service fault monitoring module monitors whether a service fault occurs. If a service fault occurs in the monitoring, the service fault monitoring module fills the virtual base station ID value corresponding to the service fault in the virtual base station identifier attribute field included in the fault object of the service fault, and the service fault occurs. The monitoring module reports the fault object filled with the virtual base station ID value. The device fault monitoring module monitors whether a device fault occurs. If the device fault occurs during the monitoring, the device fault monitoring module reports the device fault object.
  • the fault processing center receives the reported fault object, and the fault processing center determines whether the fault is a service fault according to whether the virtual base station identifier attribute field included in the fault object is valid, and if the fault object attribute field is determined to be valid, determining the fault as a service If the faulty object is invalid, the fault is determined to be a fault of the fault, and the fault is faulty.
  • the object is reported to the base station equipment fault processing center for processing.
  • the service processing implementation scenario in the embodiment of the present invention is a large-scale base station interconnection scenario.
  • the processing capability of the original single-station hardware devices is divided into various processing resources, such as main control resources, baseband resources, signaling resources, and transmission resources, and further abstracted into main control services and basebands.
  • the service, the signaling service, and the transmission service, and the plurality of base station hardware devices can form a resource pool to be uniformly scheduled through the interconnection architecture. Therefore, in the embodiment of the present invention, the virtual base station may be composed of services in different physical base station resources.
  • the method provided by the embodiment of the present invention can ensure that the service fault is flexibly followed.
  • the dynamically deployed virtual base station performs central fault handling. Therefore, each physical base station main control board does not need to statically deploy a large and complete system that supports various types of service fault handling.
  • the master resource of the base station 1, the baseband resource of the base station 2, and the transmission resource of the base station 3 constitute the virtual base station 1, and the ID of the virtual base station 1 is 001, wherein the base station 1 is composed of an indoor baseband processing unit (BBU).
  • the BBU1 is composed of a radio remote unit (RRU) RRU1
  • the base station 2 is composed of BBU2+RRU2
  • the base station 3 is composed of BBU3+RRU3.
  • the BBU1 is designated as the main control board of the virtual base station 1, and all the service faults of the cells covered by the base stations BBU1+RRU1, BBU2+RRU2, and BBU3+RRU3 are processed.
  • the service fault monitoring module 1 is used to monitor all service faults of the BBU1+RRU1 cell of the base station
  • the service fault monitoring module 2 is used to monitor all service faults of the BBU2+RRU2 cell of the base station
  • the device fault monitoring module 1 is used to monitor the BBU1+RRU1 of the base station. All equipment failures, equipment failure monitoring module 2 is used to monitor all equipment failures of the base station BBU2+RRU2.
  • the service monitoring module 2 detects that the base station BBU2+RRU2 cell service fault A and the equipment fault monitoring module 2 monitor the base station BBU2+RRU2 device fault B as an example, and details the fault handling in this scenario provided by the embodiment of the present invention.
  • Step 81 The service fault monitoring module identifies a padding value for the service fault virtual base station; where the virtual base station identifier is an attribute added when the fault handling mechanism initially defines the fault object, and the initial value of the attribute is an invalid value, that is, the fault object corresponding to A
  • the fault object corresponding to B includes the virtual base station identifier attribute, and the initial value of the attribute in the fault object corresponding to A and the fault object corresponding to B is an invalid value.
  • the fault object may also include one or a combination of the following: fault ID, fault type, fault object location parameter length, fault actual parameter length, fault class ID, fault class instance ID, fault location parameter, fault detailed parameter, fault board Six-tuple, detection veneer six-tuple, etc.
  • the service fault monitoring module 2 when the service fault monitoring module 2 detects that A occurs, the service fault monitoring module 2 adds the ID 001 of the virtual base station 1 to the virtual base station identity attribute of the fault object corresponding to A.
  • Step 82 The monitoring module reports the fault object.
  • the service fault monitoring module 2 reports the fault object corresponding to A to the fault processing center by calling a local fault processing interface; the device fault monitoring module 2 calls the local fault processing interface to respond to the fault corresponding to B.
  • the object is reported to the fault handling center.
  • the fault processing center can be located on the RRU2 board or on the board of the BBU2.
  • the fault handling center can be located on the BBU2 board.
  • Step 83 The fault processing center determines whether the fault corresponding to the reported fault object is a service fault.
  • the fault processing center determines the fault type of A and B according to the virtual base station identifier value.
  • the fault processing center determines that the virtual base station value in the fault object corresponding to A is 001, it determines that A is a service fault;
  • the virtual base station value in the fault object corresponding to B is an invalid value, it is determined that B is a device fault.
  • the fault processing center may perform preliminary processing on the fault object.
  • the preliminary processing of the fault object may include one or more of the following processes: processing, filtering, and correlation analysis of the fault. If the faulty object is on the BBU of the base station, the fault handling center can handle faults inside the boards of the BBU. For example, fault reporting, jitter, and intra-board correlation analysis are performed on the board.
  • Step 84 The equipment in the fault handling center is faulty
  • the fault processing center calls the center reporting interface, that is, a function is called to report the fault object corresponding to the fault B to the base station equipment fault processing center for processing.
  • the fault handling center can be located on the RRU2 board or the board of the BBU2.
  • the fault processing center can be located on the BBU2 board.
  • the base station equipment fault handling center may map B to the alarm information. Further, before performing the mapping process, the base station device fault processing center may further perform one or more processing of filtering, jitter, correlation analysis, and the like on the fault object corresponding to B, and after performing mapping processing, the base station device The fault handling center can report the fault object corresponding to the processed B to the NMS.
  • Step 86 The fault processing center reports a service fault object.
  • the fault processing center calls the interface on the center, and reports the fault object corresponding to A to the base station service fault processing center according to the virtual base station identifier 001 of the fault object corresponding to the A. Reason.
  • the base station service fault processing center is located on the BBU1 board.
  • the method further includes the step 87: the base station service fault processing center maps the fault object corresponding to the A to the alarm information. Further, before performing the mapping process, the base station service fault processing center may further process one or more items of filtering, jitter, or correlation analysis on the fault object corresponding to the reported A. Further, after performing the mapping process, the base station service fault object processing center may report the fault object corresponding to the processed A to the network management.
  • the technical solution provided by the embodiment of the present invention can distinguish between a device fault related to a hardware device and a service fault related to a virtual base station network element, where the service fault is dynamically deployed by the virtual base station, and the virtual base station central fault system is Processing, and equipment failure is still handled by the physical base station equipment fault processing center. Therefore, the problem that the service failure caused by the single centralized aggregation of the traditional fault reporting processing is not handled and maintained by the corresponding virtual base station, but is distributed to the respective physical base station for processing and reporting, and the system deployment is complicated and the system resources are wasted. It also solves the problem that the network management side is troublesome in fault maintenance and the user perception is poor.
  • FIG. 9 is a schematic diagram of an embodiment of a fault handling system of the present invention.
  • the fault handling system can include a fault reporting device 91 and a fault handling device 92.
  • the fault reporting device 91 may be the fault reporting device described in the foregoing embodiment, and the fault handling device may be the fault handling device described in the foregoing embodiment.
  • FIG. 10 is a schematic diagram of an embodiment of a fault processing system according to the present invention.
  • the system may further include: a base station service fault processing center 93, configured to receive a service fault object reported by the fault processing device, and The service fault object is mapped to the alarm information, and the alarm information is reported to the network management device.
  • the technical solution provided by the embodiment of the present invention is: when a service fault occurs, the service fault monitoring module fills the virtual base station ID corresponding to the service fault to the virtual base station identification attribute of the service fault object, and the virtual base station identification attribute is an initial fault processing mechanism. The attribute added when the fault object is defined, and then the fault object is reported to the fault handling center. The fault handling center is based on the fault object. Whether the virtual base station identification value is a valid value to determine whether the fault is a service fault, and then reporting the service fault object to the base station service fault processing center according to the virtual base station identifier value.
  • the technical solution provided by the embodiment of the present invention distinguishes between processing service faults and equipment faults, simplifies fault maintenance operations, and reduces system burden.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本发明实施例提供一种故障报告方法，监控模块监控是否发生业务故障，如果发生业务故障，监控模块在该业务故障的故障对象中填充业务故障对应的虚拟基站ID值，上报业务故障对象。本发明实施例同时还提供一种故障处理方法，故障处理中心判断上报是否为业务故障，若为业务故障，则将业务故障对象上报到该业务对应的虚拟基站。本发明实施例还提供故障报告设备、故障处理设备和故障处理系统。通过对业务故障进行判断、上报和处理，从而简化故障维护操作，减轻系统负担。

Description

故障处理方法、 设备和系统 本申请要求于 2011 年 12 月 13 日提交中国专利局、 申请号为 201110415217.5、 发明名称为"故障处理方法、 设备和系统，，的中国专利申请 的优先权， 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及通信技术， 具体涉及一种故障处理方法、 设备和系统。
背景技术 传统基站运营状态下， 各类故障会统一调用故障上报接口上报各种故 障到故障处理中心进行故障处理以及告警映射。 在单站运营的情况下， 从 基站控制器侧看基站网元， 一个基站就是一个逻辑网元， 故障处理中心部 署在单站的主控单元上， 对本站的所有故障进行相关性处理。
在新的大规模基站集中互联的架构下， 现有技术中的故障处理方式存 在操作维护复杂、 资源利用率较低等问题。 发明内容 本发明实施例提供一种故障处理方法、 设备和系统， 通过对业务故障 进行识别、 上报和处理， 从而简化故障维护操作， 减轻系统负担。
一方面， 本发明实施例提供了一种故障报告方法， 包括：
业务故障监控模块监控是否发生业务故障；
如果监控发生了业务故障， 业务故障监控模块在业务故障的故障对象 所包括的虚拟基站标识属性字段中，填充业务故障所对应的虚拟基站 ID值， 虚拟基站 ID值对应一个虚拟基站；
业务故障监控模块上报填充了虚拟基站 ID值的故障对象。 另一方面， 本发明实施例提供了一种故障报告设备， 包括：
第一监控单元， 用于监控是否发生业务故障；
赋值单元， 用于当第一监控单元监控发生了业务故障时， 在业务故障 的故障对象所包括的虚拟基站标识属性字段中， 填充业务故障所对应的虚 拟基站 ID值， 虚拟基站 ID值对应一个虚拟基站；
第一上报单元， 用于上报填充了所述虚拟基站 ID值的故障对象。
再一方面， 本发明实施例提供了一种故障处理方法， 包括：
接收上报的故障对象， 故障对象包括虚拟基站标识属性字段； 根据故障对象包括的虚拟基站标识属性字段是否有效， 判断故障是否 为业务故障；
若判断故障对象属性字段为有效， 则确定故障为业务故障；
将业务故障的故障对象， 上报到虚拟基站标识属性字段所对应的基站 业务故障处理中心。
再一方面， 本发明实施例提供了一种故障处理设备， 包括：
接收单元， 用于接收上报的故障对象， 故障对象包括虚拟基站标识属 性字段；
判断单元， 用于根据故障对象包括的虚拟基站标识属性字段是否有效， 判断故障是否为业务故障， 若判断故障对象属性字段为有效， 则确定故障 为业务故障； 若判断故障对象属性字段为无效， 则确定故障为设备故障； 第三上报单元， 用于将业务故障的故障对象， 上报到虚拟基站标识属 性字段所对应的业务故障处理中心。
再一方面， 本发明实施例提供了一种故障处理系统， 包括故障报告设 备和故障处理设备， 其中，
故障报告设备为前述的故障报告设备；
故障处理设备为前述的故障处理设备。
本发明实施例提供的故障报告和处理方法、 设备和系统， 通过对业务 故障进行识别、 上报和处理， 从而简化故障维护操作， 减轻系统负担。
附图说明 为了更清楚地说明本发明实施例中的技术方案， 下面将对实施例描述 中所需要使用的附图作一简单地介绍， 显而易见地， 下面描述中的附图是 本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳 动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明故障报告方法一实施例流程示意图；
图 2为本发明故障报告方法另一实施例流程示意图；
图 3为本发明故障报告设备一实施例结构示意图；
图 4为本发明故障报告设备另一实施例结构示意图；
图 5为本发明故障处理方法另一实施例流程示意图；
图 6为本发明故障处理设备另一实施例结构示意图；
图 7为本发明故障处理设备另一实施例结构示意图；
图 8为本发明故障处理方法另一实施例流程示意图；
图 9为本发明故障处理系统一实施例示意图；
图 10为本发明故障处理系统另一实施例示意图。
具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本 发明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描 述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做出创造性劳动前提 下所获得的所有其他实施例， 都属于本发明保护的范围。
实施例一 图 1为本发明故障处理方法一实施例流程示意图， 包括： 步骤 11 : 业务监控模块监控是否发生了业务故障；
本发明实施例中， 可以将故障区分为业务故障和设备故障。 另外， 故 障监控模块可以区分为业务故障监控模块和设备故障监控模块。 比如， 可 以由业务故障监控模块负责监控业务故障， 而设备故障监控模块负责监控 设备故障。
进一步的， 业务监控模块可以根据业务运行的状态来判断是否发生了 业务故障， 如果发生了业务故障， 则执行步骤 12。
步骤 12:业务故障监控模块将业务故障对应的虚拟基站 ID值填充到该 业务故障对象的虚拟基站标识；
其中， 故障对象可以包括如下内容之一或其组合： 故障 ID、 故障类型、 故障对象定位参数长度、 故障实际参数长度、 故障类 ID, 故障类实例 ID、 故障定位参数、 故障详细参数、 故障单板六元组、 检测单板六元组等。
本步骤中， 可以在故障对象中增加虚拟基站标识属性， 即虚拟基站标 识， 具体实现方式可以是在表达故障对象的数据结构体中增加一个字段， 该字段的初始值可以为一个无效值。 这个属性是故障管理机制定义故障对 象时添加的属性。
步骤 13: 业务监控模块上报业务故障对象；
其中， 业务故障监控模块可以调用本地故障上报接口将填充虚拟基站 ID值的业务故障对象上报到故障处理中心。
本实施例中， 通过对业务故障对象添加虚拟基站标识属性， 并且将该 业务对应的虚拟基站 ID值添加到该属性， 可以区分出故障业务的类型， 在 后续的故障上报和处理中， 简化了故障维护操作步骤， 节省了系统资源。
进一步的， 本实施例提供的故障处理方法还可以包括图 2所示的步骤： 步骤 21 : 设备故障监控模块监控是否发生设备故障；
其中， 设备故障监控模块根据其监控的设备的运行状态判断该设备是 否发生故障， 如果设备故障监控模块监控到设备发生故障， 则执行步骤 22; 进一步的， 在初始定义故障对象时， 可以给所有的故障对象都添加虚 拟基站标识， 初始默认为无效值。 只有产生业务故障时， 相应的业务故障 监控模块才将该业务对应的虚拟基站 ID值填充到该虚拟基站标识， 设备故 障的虚拟基站标识不添加任何内容， 该值始终为无效值。
步骤 22: 设备监控模块上报设备故障对象。
其中， 设备故障监控模块可以调用本地故障上报接口将设备故障对象 上报到故障处理中心。
图 3 为本发明故障处理设备一实施例结构示意图， 包括第一监控单元 31、 赋值单元 32和第一上 ^艮单元 33:
第一监控单元 31 , 用于监控是否发生业务故障；
赋值单元 32, 用于当监控单元 31监控发生了业务故障， 在该业务故障 的故障对象所包括的虚拟基站标识属性字段中， 填充业务故障所对应的虚 拟基站 ID值， 该虚拟基站 ID值对应一个虚拟基站；
第一上报单元 33 , 用于上报填充了虚拟基站 ID值的故障对象。
进一步的， 本实施例提供的故障处理设备还包括图 4所示的第二监控 单元 41和第二上 ^艮单元 42:
第二监控单元 41 , 用于监控是否发生设备故障；
第二上报单元 42, 用于上报第二监控单元 41监控的设备故障对象。 实施例二
图 5为本发明故障处理方法另一实施例流程示意图， 包括：
步骤 51 : 故障处理中心接收上报的故障对象；
其中， 故障处理中心接收业务故障监控模块和设备故障监控模块上报 的故障对象， 上报的故障对象包括虚拟基站标识属性字段。
步骤 52: 故障处理中心判断上报的故障是否为业务故障；
其中， 故障处理中心根据上报的故障对象的虚拟基站标识值是否有效 来判断该故障对象是否为业务故障， 若该故障对象虚拟基站标识值有效， 则确定该故障对象对应的故障为业务故障。
步骤 53:故障处理中心上报该业务故障对象到基站业务故障处理中心； 其中， 故障处理中心将业务故障对象上报到该业务故障对象的虚拟基 站标识属性字段所对应的业务故障处理中心。
进一步的， 本实施例故障处理方法还包括步骤 54: 若判断该故障对象 虚拟基站标识值为无效， 则确定该故障对象为设备故障， 则上报该设备故 障对象到基站设备故障处理中心。
本发明实施例提供的方法， 即根据故障对象虚拟基站标识值是否有效 判断该故障对象对应的故障是否为业务故障， 若是业务故障， 则根据该故 障的虚拟基站标识值上报该故障对象到基站业务故障处理中心， 区分不同 类型的故障， 将其上报到不同的基站处理中心处理， 简化了故障维护操作 步骤， 节省了系统资源。
图 6为本发明故障处理设备另一实施例结构示意图，包括接收单元 61、 判断单元 62和第三上>¾单元 63:
接收单元 61 , 用于接收上报的故障对象， 该故障对象包括虚拟基站标 识属性字段；
判断单元 62, 用于根据该故障对象包括的虚拟基站标识属性字段是否 有效， 判断该故障是否为业务故障， 若判断该故障对象属性字段为有效， 则判断该故障为业务故障； 若判断该故障对象属性字段为无效， 则判断该 故障为设备故障；
第三上报单元 63 , 用于将业务故障的故障对象， 上报到虚拟基站标识 属性字段所对应的业务故障处理中心。
进一步的， 本实施例提供的故障处理设备还包括图 7 所包括的第四上 报单元 71 , 用于将设备故障的故障对象， 上报到基站设备故障处理中心。
实施例三 图 8为本发明故障处理方法另一实施例流程示意图， 本图所示方法为 完整的故障上报处理流程：
业务故障监控模块监控是否发生业务故障， 如果监控发生了业务故障， 业务故障监控模块在业务故障的故障对象所包括的虚拟基站标识属性字段 中， 填充业务故障所对应的虚拟基站 ID值， 业务故障监控模块上报填充了 虚拟基站 ID值的故障对象； 设备故障监控模块监控是否发生设备故障， 如 果监控发生了设备故障， 设备故障监控模块上报设备故障对象。
进一步的， 故障处理中心接收上报的故障对象， 故障处理中心根据故 障对象包括的虚拟基站标识属性字段是否有效， 判断故障是否为业务故障， 若判断故障对象属性字段为有效， 则确定该故障为业务故障， 将业务故障 的故障对象， 上报到虚拟基站标识属性字段所对应的业务故障处理中心处 理； 若判断故障对象属性字段为无效， 则确定该故障为设备故障， 故障处 理中心将设备故障的故障对象， 上报到基站设备故障处理中心处理。
本发明实施例中业务处理实现场景为大规模基站互联场景。 在基站大 规模互联的情形下， 原有单站硬件设备的处理能力被划分成各种处理资源， 比如主控资源、 基带资源、 信令资源、 传输资源， 并进一步抽象成主控服 务、 基带服务、 信令服务、 传输服务， 而多个基站硬件设备可以通过互联 架构形成了资源池被统一调度。 所以， 本发明实施例中， 可以由不同的物 理基站资源中的服务组成虚拟基站， 当虚拟基站与物理基站不是——对应 的情况下， 本发明实施例提供的方法可以保证业务故障灵活地跟随动态部 署的虚拟基站进行中心故障处理， 这样， 每个物理基站主控板上不用静态 部署一个大而全的支持各种制式业务故障处理的系统。
假设由基站 1的主控资源、 基站 2的基带资源和基站 3的传输资源组 成虚拟基站 1 , 该虚拟基站 1的 ID为 001 , 其中， 基站 1由室内基带处理 单元 (Building Baseband Unit, BBU)BBU1和远端射频模块 ( Radio Remote Unit, RRU ) RRU1 组成， 基站 2 由 BBU2+RRU2 组成以及基站 3 由 BBU3+RRU3 组成。 指定 BBU1 为虚拟基站 1 的主控板， 处理基站 BBU1+RRU1、 BBU2+RRU2和 BBU3+RRU3覆盖的小区所有业务故障。 同 时业务故障监控模块 1用来监控基站 BBU1+RRU1小区的所有业务故障， 业务故障监控模块 2用来监控基站 BBU2+RRU2小区的所有业务故障， 设 备故障监控模块 1用来监控基站 BBU1+RRU1的所有设备故障， 设备故障 监控模块 2用来监控基站 BBU2+RRU2的所有设备故障。
以业务监控模块 2检测到基站 BBU2+RRU2小区发生业务故障 A和设 备故障监控模块 2监控到基站 BBU2+RRU2发生设备故障 B为例， 下面详 细说明本发明实施例提供的此场景下的故障处理方法：
步骤 81 : 业务故障监控模块给业务故障虚拟基站标识填充值； 其中， 虚拟基站标识为故障处理机制初始定义故障对象时增加的一个 属性， 该属性初始值为无效值， 即 A所对应的故障对象和 B所对应的故障 对象均包含该虚拟基站标识属性， A所对应的故障对象和 B所对应的故障 对象中的该属性初始值均为无效值。 故障对象还可以包括如下内容之一或 其组合： 故障 ID、 故障类型、 故障对象定位参数长度、 故障实际参数长度、 故障类 ID, 故障类实例 ID、 故障定位参数、 故障详细参数、 故障单板六元 组、 检测单板六元组等。
本步骤中， 当业务故障监控模块 2检测到 A发生， 业务故障监控模块 2将虚拟基站 1的 ID 001添加到 A所对应的故障对象的虚拟基站标识属性。
步骤 82: 监控模块上报故障对象；
其中， 业务故障监控模块 2通过调用本地故障处理接口， 即通过一个 调用函数将 A所对应的故障对象上报到故障处理中心； 设备故障监控模块 2通过调用本地故障处理接口， 将 B所对应的故障对象上报到故障处理中 心。
进一步的， 当故障 A或者 B发生在 RRU2单板上时， 该故障处理中心 可以位于 RRU2单板上， 还可以位于 BBU2的单板， 当故障 A或者 B发生 在 BBU2单板上时， 该故障处理中心可以位于 BBU2单板。
步骤 83: 故障处理中心判断上报的故障对象所对应的故障是否为业务 故障；
其中， 故障处理中心根据虚拟基站标识值判断 A和 B的故障类型， 当 故障处理中心判断 A所对应的故障对象中的虚拟基站值为 001时， 则确定 A为业务故障； 当故障处理中心判断 B所对应的故障对象中的虚拟基站值 为无效值时， 则确定 B为设备故障。
进一步的， 在判断故障类型之前， 故障处理中心可以对故障对象进行 初步处理。 其中， 对故障对象初步处理可以包括如下处理中的一项或多项： 对故障的过滤、抖动和相关性分析等处理。如故障对象在基站设备 BBU上， 故障处理中心可以处理 BBU中各单板内部的故障， 比如， 进行单板内部的 故障上报过滤、 放抖动以及板内相关性分析等。
步骤 84: 故障处理中心上^艮设备故障；
其中， 故障处理中心调用中心上报接口， 即调用一个函数将故障 B所 对应的故障对象上报到基站设备故障处理中心处理。 当故障 B在 RRU2单 板上时， 该故障处理中心可以位于 RRU2单板上， 还可以位于 BBU2的单 板， 当故障 B发生在 BBU2单板上时， 该故障处理中心可以位于 BBU2单 板。
还可以进一步包括步骤 85, 基站设备故障处理中心可以将 B映射为告 警信息。 进一步的， 在进行映射处理之前， 基站设备故障处理中心还可以 对 B所对应的故障对象进行过滤或抖动或相关性分析等中的一项或者数项 处理，以及在进行映射处理之后，基站设备故障处理中心可以将处理后的 B 所对应的故障对象上报到网管。
步骤 86: 故障处理中心上报业务故障对象；
其中， 故障处理中心调用中心上 接口， 根据 A所对应的故障对象的 虚拟基站标识 001将 A所对应的故障对象上报到基站业务故障处理中心处 理。 当故障 A发生在 BBU2或 RRU2, 基站业务故障处理中心位于 BBU1 单板。
还可以进一步包括步骤 87: 基站业务故障处理中心将 A所对应的故障 对象映射为告警信息。 进一步的， 在进行映射处理之前， 基站业务故障处 理中心还可以对上报的 A所对应的故障对象进行过滤或抖动或相关性分析 等中的一项或者数项处理。 更进一步的， 在进行映射处理之后， 基站业务 故障对象处理中心可以将处理后的 A所对应的故障对象上报到网管。
本发明实施例提供的技术方案， 可以把跟硬件设备有关的设备故障和 与虚拟基站网元相关的业务故障进行区分处理， 其中， 业务故障随着虚拟 基站的动态部署， 由虚拟基站中心故障系统处理， 而设备故障还是由本物 理基站设备故障处理中心处理。 因此， 解决了传统故障上报处理单一集中 而带来的业务故障不是由对应的虚拟基站统一处理和维护， 而是分散到各 自物理基站进行处理和上报而导致的系统部署复杂和系统资源浪费问题， 还解决了网管侧对故障维护繁瑣， 用户感知差的问题。
图 9为本发明故障处理系统一实施例示意图。 该故障处理系统可以包 括故障报告设备 91和故障处理设备 92。 其中， 故障报告设备 91可以为前 述实施例所描述的故障报告设备， 故障处理设备可以为前述实施例所描述 的故障处理设备。
进一步可选的， 如图 10所示， 图 10为本发明故障处理系统一实施例 示意图， 该系统还可以包括： 基站业务故障处理中心 93 , 用于接收故障处 理设备上报的业务故障对象， 并映射该业务故障对象为告警信息， 上报该 告警信息到网管设备。
本发明实施例提供的技术方案为： 当业务故障产生， 业务故障监控模 块将该业务故障对应的虚拟基站 ID填充到该业务故障对象的虚拟基站识别 属性， 该虚拟基站识别属性为故障处理机制初始定义故障对象时增加的属 性， 然后将故障对象上报到故障处理中心， 故障处理中心根据故障对象的 虚拟基站识别值是否为有效值来判断该故障是否为业务故障， 然后根据虚 拟基站标识值将业务故障对象上报到基站业务故障处理中心。 本发明实施 例提供的技术方案区分处理业务故障和设备故障， 简化了故障维护操作， 减轻了系统负担。
可以理解的是， 上述方法及设备中的相关特征可以相互参考。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步 骤可以通过程序指令相关的硬件来完成， 前述的程序可以存储于计算机可 读取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而 前述的存储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代 码的介质。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对 其限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通 技术人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修 改， 或者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不 使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

1、 一种故障 ^艮告方法， 其特征在于， 包括：
业务故障监控模块监控是否发生业务故障；
如果监控发生了业务故障， 所述业务故障监控模块在所述业务故障的 故障对象所包括的虚拟基站标识属性字段中， 填充所述业务故障所对应的 虚拟基站 ID值， 所述虚拟基站 ID值对应一个虚拟基站；
所述业务故障监控模块上报填充了所述虚拟基站 ID值的故障对象。
2、 根据权利要求 1所述的故障报告方法， 其特征在于， 所述方法还包 括：
设备故障监控模块监控是否发生设备故障；
如果监控发生了设备故障， 所述设备故障监控模块上报所述设备故障 对象。
3、 一种故障报告设备， 其特征在于， 包括：
第一监控单元， 用于监控是否发生业务故障；
赋值单元， 用于当所述第一监控单元监控发生了业务故障时， 在所述 业务故障的故障对象所包括的虚拟基站标识属性字段中， 填充所述业务故 障所对应的虚拟基站 ID值， 所述虚拟基站 ID值对应一个虚拟基站；
第一上报单元， 用于上报填充了所述虚拟基站 ID值的故障对象。
4、 根据权利要求 3所述的故障报告设备， 其特征在于， 所述设备还包 括：
第二监控单元， 用于监控是否发生设备故障；
第二上报单元， 用于当第二监控单元监控发生设备故障时， 上报所述 设备故障对象。
5、 一种故障处理方法， 其特征在于， 包括：
接收上报的故障对象， 所述故障对象包括虚拟基站标识属性字段； 根据所述故障对象包括的虚拟基站标识属性字段是否有效， 判断所述 故障是否为业务故障；
若判断所述故障对象属性字段为有效， 则确定所述故障为业务故障； 将所述业务故障的故障对象， 上报到虚拟基站标识属性字段所对应的 基站业务故障处理中心。
6、 根据权利要求 5所述的故障处理方法， 其特征在于， 所述方法还包 括：
若判断所述故障对象属性字段为无效， 则确定所述故障为设备故障； 将所述设备故障的故障对象， 上报到基站设备故障处理中心。
7、 一种故障处理设备， 其特征在于， 包括：
接收单元， 用于接收上报的故障对象， 所述故障对象包括虚拟基站标 识属性字段；
判断单元， 用于根据所述故障对象包括的虚拟基站标识属性字段是否 有效， 判断所述故障是否为业务故障， 若判断所述故障对象属性字段为有 效， 则确定所述故障为业务故障； 若判断所述故障对象属性字段为无效， 则确定所述故障为设备故障；
第三上报单元， 用于将所述业务故障的故障对象， 上报到虚拟基站标 识属性字段所对应的业务故障处理中心。
8、 根据权利要求 7所述的故障处理设备， 其特征在于， 所述设备还包 括：
第四上报单元， 用于将所述设备故障的故障对象， 上报到基站设备故 障处理中心。
9、 一种故障处理系统， 其特征在于， 包括故障报告设备和故障处理设 备， 其中，
所述故障报告设备为如权利要求 3或 4所述的故障报告设备； 所述故障处理设备为如权利要求 7或 8所述的故障处理设备。
10、 根据权利要求 9所述的故障处理系统， 其特征在于， 还包括： 基站业务故障处理中心， 用于接收所述故障处理设备上报的业务故障 对象， 并映射所述业务故障对象为告警信息， 上报所述告警信息到网管设 备。
PCT/CN2012/086553 2011-12-13 2012-12-13 故障处理方法、设备和系统 WO2013086996A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110415217.5A CN103167539B (zh) 2011-12-13 2011-12-13 故障处理方法、设备和系统
CN201110415217.5 2011-12-13

Publications (1)

Publication Number Publication Date
WO2013086996A1 true WO2013086996A1 (zh) 2013-06-20

Family

ID=48590194

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/086553 WO2013086996A1 (zh) 2011-12-13 2012-12-13 故障处理方法、设备和系统

Country Status (2)

Country Link
CN (1) CN103167539B (zh)
WO (1) WO2013086996A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105320585A (zh) * 2014-07-08 2016-02-10 北京启明星辰信息安全技术有限公司 一种实现应用故障诊断的方法及装置
CN112988831A (zh) * 2019-12-13 2021-06-18 深圳云天励飞技术有限公司 故障定位方法及相关装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015035564A1 (zh) * 2013-09-11 2015-03-19 华为技术有限公司 一种告警上报方法及相关设备、系统
CN103674590B (zh) * 2013-11-09 2016-04-20 皖江新兴产业技术发展中心 半导体芯片全自动封装设备自动报警系统实现方法
CN105281928A (zh) * 2014-05-29 2016-01-27 中兴通讯股份有限公司 一种告警上报方法及装置
CN107995016B (zh) * 2016-10-26 2021-03-23 普天信息技术有限公司 一种网络故障处理方法、装置及系统
CN108399723A (zh) * 2018-03-29 2018-08-14 苏州天华信息科技股份有限公司 一种应用于交管监控平台的语音报警系统及方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101593135A (zh) * 2008-05-29 2009-12-02 国际商业机器公司 在分布式集成环境中集中处理业务流程故障的装置和方法
CN101651625A (zh) * 2009-09-03 2010-02-17 中兴通讯股份有限公司 多业务恢复的选路装置及选路方法
CN101800675A (zh) * 2010-02-25 2010-08-11 华为技术有限公司 故障监控方法、监控设备及通信系统
CN102075368A (zh) * 2011-02-22 2011-05-25 华为技术有限公司 一种业务故障诊断方法、装置和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968141B (zh) * 2006-08-09 2010-05-12 华为技术有限公司 一种wdm传输系统的保护方法与装置
CN102143005B (zh) * 2011-04-14 2015-01-28 中兴通讯股份有限公司 一种基于oam协议确定故障消除的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101593135A (zh) * 2008-05-29 2009-12-02 国际商业机器公司 在分布式集成环境中集中处理业务流程故障的装置和方法
CN101651625A (zh) * 2009-09-03 2010-02-17 中兴通讯股份有限公司 多业务恢复的选路装置及选路方法
CN101800675A (zh) * 2010-02-25 2010-08-11 华为技术有限公司 故障监控方法、监控设备及通信系统
CN102075368A (zh) * 2011-02-22 2011-05-25 华为技术有限公司 一种业务故障诊断方法、装置和系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105320585A (zh) * 2014-07-08 2016-02-10 北京启明星辰信息安全技术有限公司 一种实现应用故障诊断的方法及装置
CN105320585B (zh) * 2014-07-08 2019-04-02 北京启明星辰信息安全技术有限公司 一种实现应用故障诊断的方法及装置
CN112988831A (zh) * 2019-12-13 2021-06-18 深圳云天励飞技术有限公司 故障定位方法及相关装置
CN112988831B (zh) * 2019-12-13 2024-06-07 深圳云天励飞技术有限公司 故障定位方法及相关装置

Also Published As

Publication number Publication date
CN103167539B (zh) 2015-12-02
CN103167539A (zh) 2013-06-19

Similar Documents

Publication Publication Date Title
WO2013086996A1 (zh) 故障处理方法、设备和系统
CN109560955B (zh) 网络的部署信息确定方法及设备
US20200382362A1 (en) Alarm information processing method, related device, and system
CN108039964B (zh) 基于网络功能虚拟化的故障处理方法及装置、系统
CN107544839B (zh) 虚拟机迁移系统、方法及装置
US9532359B2 (en) Resource allocation method and device
WO2017092640A1 (zh) 一种虚拟网络性能的监控系统及方法、相关设备
WO2019141089A1 (zh) 网络告警方法、装置、系统及终端
US10700921B2 (en) Automatic symptom data collection in cloud deployment
EP3644646A1 (en) Load-balancing method and apparatus
CN112423331A (zh) 一种故障诊断方法及装置
CN105071968A (zh) 一种通信设备的业务面和控制面的隐性故障修复方法和装置
CN106375102A (zh) 一种服务注册方法、使用方法及相关装置
CN108604996A (zh) 一种nfv系统中的策略传输方法和装置
CN115426274B (zh) 资源预警方法、装置、电子设备及存储介质
CN116074178A (zh) 网络的数字孪生架构、网络会话处理方法及装置
KR20240071399A (ko) O-ran에 있어서의 o-ru의 인터넷 프로토콜의 버전 설정 및/또는 검지
CN114221882A (zh) 故障链路检测方法、装置、设备和存储介质
CN105659530A (zh) 一种告警处理的方法和设备
CN104602287B (zh) 一种以太通路切换的方法和装置
WO2017177762A1 (zh) 一种资产管理方法及系统
CN116723111B (zh) 业务请求的处理方法、系统及电子设备
EP4443933A1 (en) Virtualization base and wireless access network control by wireless access network node
CN109089278B (zh) 一种接口测试方法及装置
CN109951748B (zh) 一种基于sdn的otn中的业务超发方法及系统

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: 12857254

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: 12857254

Country of ref document: EP

Kind code of ref document: A1