Patent application EP19174273A (EP), filed 2019-05-14
Publication number: EP3570494A2
Title: A FRAMEWORK FOR INTELLIGENT AUTOMATED OPERATIONS FOR NETWORK, SERVICE & CUSTOMER EXPERIENCE MANAGEMENT
Abstract: A device may receive an alarm from a network and determine whether to process the alarm using a robotic process automation (RPA) engine or a machine learning automation (MLA) engine. Based on the determination, the device may selectively cause the alarm to be processed by the RPA engine or the MLA engine. The device may receive data associated with a network performance indicator and may provide the data to the MLA engine. The MLA engine may use a machine learning model to assign a score to the data and may determine whether to generate a trouble ticket based on the score.
IPC codes: H04L  12/    24            A I
H04L  12/    26            A I
G06N  20/    00            A I
G06N   5/    04            A I
Claims: number: 1
text: A device, comprising:
number: 2
text: The device of claim 1, wherein the MLA engine, after outputting the recommendation, is further to:
number: 3
text: The device of claim 1 or 2, wherein the RPA engine, when performing the one or more first recovery actions, is to:
number: 4
text: The device of any one of the preceding claims, wherein the MLA engine, when using the machine learning model to assign the score to the alarm, is to:
number: 5
text: The device of any one of the preceding claims, wherein the recommendation is a first recommendation, and the RPA engine is to:
number: 6
text: The device of any one of the preceding claims, wherein the recommendation is a first recommendation, and the RPA engine is to:
number: 7
text: A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors, cause the one or more processors to:
number: 8
text: The non-transitory computer-readable medium of claim 7, wherein the MLA engine, after outputting the second recommendation, is further to:
number: 9
text: The non-transitory computer-readable medium of claim 7 or 8, wherein the one or more instructions, that cause the one or more processors to determine whether to process the alarm using the RPA engine or the MLA engine, cause the one or more processors to:
number: 10
text: The non-transitory computer-readable medium of any one of claims 7 to 9, wherein the historical data associated with the alarm includes a quantity of times a trouble ticket was opened for the alarm over a period of time.
number: 11
text: The non-transitory computer-readable medium of any one of claims 7 to 10, wherein the fault in the network is at least one of a call drop event or a cable modem offline event;
and/or
wherein the RPA engine, when determining whether the RPA engine is capable of performing the one or more first recovery actions, is to:
determine that the RPA is not capable of performing the one or more first recovery actions when the one or more first recovery actions involve using a graphical user interface.
number: 12
text: A method, comprising:
number: 13
text: The method of claim 12, wherein the network performance indicator includes at least one of network latency of a network, bandwidth usage of one or more customer-premises equipments (CPEs) connected to the network, throughput of the network, a quantity of active users using the network, jitter in the network, packet loss in the network, a service indicator associated with a service, or a customer experience indicator associated with a customer experience.
number: 14
text: The method of claim 12 or 13, wherein determining whether to generate the trouble ticket comprises:
number: 15
text: The method of any one of claims 12 to 14, further comprising:
Office action: search_report, dated 2019-11-20
Rejection reasons: inventive_step_epc_56
Prior art cited: ref_id: GB2421656
ref_type: patent
severity: background
ref_id: US2008140817
ref_type: patent
severity: obviousness
ref_id: US7536595
ref_type: patent
severity: obviousness
ref_id: US2011260879
ref_type: patent
severity: obviousness
ref_id: US2014068348
ref_type: patent
severity: background
ref_id: US2017054641
ref_type: patent
severity: background
ref_id: US2018019910
ref_type: patent
severity: obviousness
Final disposition: pending (2019-11-20)