Application data flow management in an IP network
First Claim
1. A two-level, network-based application control architecture for monitoring services provided via a packet-based network, comprising:
- a first computing device at a network level and a second computing device at a control level,wherein the first computing device at the network level;
analyzes data flows relating to services to be monitored,detects occurrence of configurable events, including a request for connection to a first service of the services to be monitored,generates and sends event reports to the second computing device, wherein at least one event report sent to the second computing device identifies the request for connection to the first service and includes corresponding data related to a connection setup and a generated traffic; and
wherein the second computing device at the control level;
configures the first computing device to detect occurrence of events of interest in the analyzed data flows,receives and processes the event reports from the first computing device to monitor the services,in response to receiving the corresponding data related to the connection setup and the generated traffic from the first computing device, generates and stores a Finite State Automaton in memory, the Finite State Automaton having states associated with phases of the connection to the first service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the first service,associate a second monitored service of the services to be monitored with a second Finite State Automaton stored in memory, the second Finite State Automaton having states associated with phases of the connection to the second service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the second service; and
cause the second Finite State Automaton to evolve based on the received event reports, to monitor the second service,wherein the Finite State Automaton further has a callback function which is associated with an entry into or an exit from a state of the Finite State Automaton, or with a state-to-state transition of the Finite State Automaton, and takes actions at both an application level and the control level.
1 Assignment
0 Petitions
Accused Products
Abstract
Disclosed herein is a two-level, network-based application control (NBAC) architecture for monitoring services provided via a packet-based network. The NBAC architecture includes a Network Trigger System provided at a network level to analyze data flows relating to services to be monitored to detect occurrence of configurable events, and to generate and send event reports; and a Usage Status Engine provided at a control level to configure the Network Trigger System to detect occurrence of events of interest, and to receive and process the event reports from the Network Trigger System to monitor the services.
-
Citations
16 Claims
-
1. A two-level, network-based application control architecture for monitoring services provided via a packet-based network, comprising:
-
a first computing device at a network level and a second computing device at a control level, wherein the first computing device at the network level; analyzes data flows relating to services to be monitored, detects occurrence of configurable events, including a request for connection to a first service of the services to be monitored, generates and sends event reports to the second computing device, wherein at least one event report sent to the second computing device identifies the request for connection to the first service and includes corresponding data related to a connection setup and a generated traffic; and wherein the second computing device at the control level; configures the first computing device to detect occurrence of events of interest in the analyzed data flows, receives and processes the event reports from the first computing device to monitor the services, in response to receiving the corresponding data related to the connection setup and the generated traffic from the first computing device, generates and stores a Finite State Automaton in memory, the Finite State Automaton having states associated with phases of the connection to the first service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the first service, associate a second monitored service of the services to be monitored with a second Finite State Automaton stored in memory, the second Finite State Automaton having states associated with phases of the connection to the second service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the second service; and cause the second Finite State Automaton to evolve based on the received event reports, to monitor the second service, wherein the Finite State Automaton further has a callback function which is associated with an entry into or an exit from a state of the Finite State Automaton, or with a state-to-state transition of the Finite State Automaton, and takes actions at both an application level and the control level. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. A method for monitoring services provided via a packet-based network, comprising:
-
providing a two-level, network-based application control architecture including; a first computing device provided at a network level and a second computing device provided at a control level, performing steps by the first computing device provided at the network level to; analyze data flows relating to services to be monitored, detect occurrence of configurable events, including a request for connection to a first service of the services to be monitored, generate and send event reports to the second computing device, wherein at least one event report sent to the second computing device identifies the request for connection to the first service and includes corresponding data related to the connection setup and the generated traffic; and performing steps by the second computing device provided at the control level to; configure the first computing device to detect occurrence of events of interest in the analyzed data flows, receive and process the event reports from the first computing device to monitor the services, in response to receiving the corresponding data related to the connection setup and the generated traffic from the first computing device, generate and store a Finite State Automaton in memory, the Finite State Automaton having states associated with phases of the connection to the first service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the first service, associate a second monitored service of the services to be monitored with a second Finite State Automaton stored in memory, the second Finite State Automaton having states associated with phases of the connection to the second service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the second service; and cause the second Finite State Automaton to evolve based on the received event reports, to monitor the second service, wherein the Finite State Automaton further has a callback function which is associated with an entry into or an exit from a state of the Finite State Automaton, or with a state-to-state transition of the Finite State Automaton, and which takes actions at both an application level and the control level.
-
-
16. Non-transitory computer readable media having software modules stored thereon that, when executed by a processing system, implement a system comprising:
-
a first computing device at a network level and a second computing device at a control level, wherein the first computing device at the network level; analyzes data flows relating to services to be monitored, detects occurrence of configurable events, including a request for connection to a first service of the services to be monitored, generates and sends event reports to the second computing device, wherein at least one event report sent to the second computing device identifies the request for connection to the first service and includes corresponding data related to a connection setup and a generated traffic; and wherein the second computing device at the control level; configures the first computing device to detect occurrence of events of interest in the analyzed data flows, receives and processes the event reports from the first computing device to monitor the services, in response to receiving the corresponding data related to the connection setup and the generated traffic from the first computing device, generate and store a Finite State Automaton in memory, the Finite State Automaton having states associated with phases of the connection to the first service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the first service, associate a second monitored service of the services to be monitored with a second Finite State Automaton stored in memory, the second Finite State Automaton having states associated with phases of the connection to the second service, and state-to-state transitions associated with events the occurrence of which is detected in the analyzed data flows, to provide a representation of possible phases of connection to the second service; and cause the second Finite State Automaton to evolve based on the received event reports, to monitor the second service, wherein the Finite State Automaton further has a callback function which is associated with an entry into or an exit from a state of the Finite State Automaton, or with a state-to-state transition of the Finite State Automaton, and which takes actions at both an application level and the control level.
-
Specification