Page 448 - Handbook of Modern Telecommunications

Network Management and Administration 3-239

TABl E 3.9.1 Comparison of Signaling Sensory versus Packet-Flow Sensory Approaches
Signaling Sensory Monitoring Packet-Flow Sensory Monitoring
Viewpoint Call and Session Control: Management of Session Delivery: Monitoring actual delivery
the fixed connection TDM network but of service content and payload. Service
also includes packet services for wireless, quality monitoring during a session and not
e.g., GPRS. Setup and tear-down of fixed at the setup or tear-down of a session.
and mobile sessions, with normal or Intrasession service quality.
abnormal notification/closure.
Orientation Connection-based: Show end-to-end call Connectionless: Tracking of packet flows on
path involving all network elements for a a session-by-session basis regardless of what
service. Topology aware of what network network elements are used. Can show
elements are delivering what from the adjacent devices, but concentrates on the
network. Setup or tear-down of flow of packets across a point of the
connection paths within the network. network. Topology agnostic because there is
not a specific path involved due to rerouting
capabilities in mesh networks.
Service Perception Aggregate Service: Looking at the flow of a All Service Components: Looks at all the
revenue service to the end user. Noting the individual enabling services (i.e., DNS,
path that the revenue service takes from DHCP, AAA, LDAP) as well as all of the
origination to termination (at the end user content components. Service enablers are
point). Usually does not see actual content the essential parts that work together to
of the revenue service. Sees setup, sees allow the secure flow of content to the end
data flow during the session, and session user. Only shows the flow of IP content (not
tear-down. Includes both successful and voice content) whether payload is encrypted
failed access attempts to deliver the or not. Payload is noticed but not decrypted.
revenue service. Tells packet loss, tells delay of packet
transport.
Planning Value Trending traffic volume for call capacity. Trending volume for data capacity.
Fixed per service and per session. Understanding the volume of data/IP traffic
Tracking the number of port assignments as variable per service and per session.
in use at any given point in time. Sizing of Tracking of the volume of data flowing
connection capacity (ports, transmission between two points that may involve a
paths, backhaul need) for fixed capacity variable number of access connections.
content. Monitoring the flow of Assists capacity planning (sizing of IP
connection capacity, rate, trending of delivery infrastructure, routers, links,
number of connections. Good at tracking switches, servers).
call setup and tear-down, not Monitors mixed service types across a
understanding the total volume of portion of a bearer network. Trends around
information flowing across the network. content volume regardless of the number of
sessions.
Not good at understanding total number of
connections needed to get data from
origination to destination points.
Errors Recognized Network Transport Errors: Failure to Network Transport Errors including those
connect, but not failure to properly deliver that happen during process of delivering a
service components. Only errors resulting service. Retransmission, packet loss, packet
in a loss of the service, when the service is errors. Service transport errors seen if
abnormal termination. If loss of packets signaling is over IP.
creates poor customer services, customer Session + Network Errors: Service
may abruptly stop the service. Cannot tell degradation errors. Response time increase
this type of termination (poor-quality to unacceptability for service quality impact.
termination) vs. customer needing to
abort from other reasons.
Session Errors: Focus on service failure
errors (abnormal termination of service)
e.g., service fault.
Continued