# US 2005/0097209 A1 · Telecommunications network subscriber experience measurement

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0097209 A1
- Document ID: US20050097209A1
- Status: Published application
- Kind: A1
- Application number: 10/980,248
- Filed: 2004-11-04
- Published: 2005-05-05
- Earliest claimed: 2002-05-08
- Assignees: Aran Communications Limited
- Inventors: Brendan McDonagh; Augustine Collins; Philip Beck; Thomas Morrisroe
- Web page: https://patentgrep.com/patent/US20050097209A1

## CPC

- H04W 24/00: Supervisory, monitoring or testing arrangements
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/5009: Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L 41/5067: Customer-centric QoS measurements
- H04L 43/00: Arrangements for monitoring or testing data switching networks
- H04L 41/0681: Configuration of triggering conditions
- H04L 41/5087: {wherein the managed service relates to voice services (management of VoIP services H04M7/0081)}
- H04L 41/509: {wherein the managed service relates to media content delivery, e.g. audio, video or TV}
- H04L 41/5093: {wherein the managed service relates to messaging or chat services}
- H04L 43/0847: {Transmission error}
- H04L 43/0852: Delays
- H04L 43/106: using time related information in packets, e.g. by adding timestamps
- H04L 43/12: Network monitoring probes
- H04L 43/16: Threshold monitoring
- H04W 24/08: Testing, {supervising or monitoring} using real traffic
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In a mobile network a packet interface (103) is monitored by a tap (160-163) in a non-intrusive manner. Captured transaction data is uploaded to a probe (155-158) linked to one or more taps. The probe acts as a slave to a server (159), activating and terminating data capture. A coordinator (601) of the probe (155) manages data capture and buffering according to the server. The server (150) filters the data according to a subscriber registry (203) and loads data until there are complete protocol descriptions. These provide real time subscriber-centered QoS metrics.

## Claims

### Claim 1

A management system for a telecommunication network, the management system comprising:
a plurality of taps for monitoring in real time activity at network interfaces to provide network transaction data,
a filter for filtering the transaction data on a subscriber identifier basis to provide per-user quality-of-service metrics in real time, and
a server for aggregating the metrics and for storing at least some of the metrics and transaction data.

### Claim 2 (depends on 1)

A management system as claimed in claim 1, wherein the taps each capture network messages and generate a transaction event record for one or more messages, the transaction records being provided as the transaction data.

### Claim 3 (depends on 1)

A management system as claimed in claim 1, wherein at least some of the taps are non-invasive.

### Claim 4 (depends on 1)

A management system as claimed in claim 1, wherein at least one tap is connected to monitor traffic at a network interface between network elements handling messages for multiple subscribers.

### Claim 5 (depends on 1)

A management system as claimed in claim 1, wherein at least one tap is a software agent executing on a subscriber device.

### Claim 6 (depends on 5)

A management system as claimed in claim 5, wherein the software agent executes on a SIM card of a subscriber mobile device or in the device's circuit.

### Claim 7 (depends on 1)

A management system as claimed in claim 1, wherein there are a plurality of probes located remotely from the server and connected to at least one tap.

### Claim 8 (depends on 7)

A management system as claimed in claim 7, wherein each probe comprises a task coordinator, and a registry storing data concerning taps presently linked to the probe and characteristics of the network interfaces where the taps are located.

### Claim 9 (depends on 8)

A management system as claimed in claim 8, wherein the registry holds data concerning mobile terminal configurations.

### Claim 10 (depends on 8)

A management system as claimed in claim 8, wherein the task coordinator manages commands from the server defining monitoring tasks including start times and end times.

### Claim 11 (depends on 10)

A management system as claimed in claim 10, wherein the task coordinator comprises a function for receiving filtering commands from the server for filtering in the probes.

### Claim 12 (depends on 5)

A management system as claimed in claim 5, wherein the probe buffers transaction data for periodic upload to the server.

### Claim 13 (depends on 12)

A management system as claimed in claim 12, wherein the server polls the probes for transaction data uploads.

### Claim 14 (depends on 1)

A management system as claimed in claim 1, wherein the server comprises a collection process associated with each tap or each probe, at least some collection processes performing format conversion or decryption on data received from an associated probe.

### Claim 15 (depends on 1)

A management system as claimed in claim 1, wherein the server comprises a subscriber registry for storing identifiers of subscribers for whom quality-of-service metrics are to be determined and for transferring identifiers to the filter, located either in the server or in a probe.

### Claim 16 (depends on 1)

A management system as claimed in claim 1, wherein the server comprises a data loading function for loading filtered data into memory.

### Claim 17 (depends on 16)

A management system as claimed in claim 16, wherein the data loading function performs transaction data.

### Claim 18 (depends on 16)

A management system as claimed in claim 16, wherein the server comprises a filtering memory structure for incomplete records and the data loading function writes filtered data to said memory structure, and monitors the data to determine when a complete protocol procedure description for a subscriber has been loaded, and transfers the complete descriptors as metrics to a complete records memory structure.

### Claim 19 (depends on 1)

A management system as claimed in claim 1, wherein the server comprises a report generating function for analysing the metrics and generating reports according to operator configurations.

### Claim 20 (depends on 1)

A management system as claimed in claim 1, wherein the server comprises an alarm generating function for analysing the metrics and generating alarms according to operator configurations.

### Claim 21 (depends on 20)

A management system as claimed in claim 20, wherein the configurations comprise service level agreements.

### Claim 22 (depends on 19)

A management system as claimed in claim 19, wherein the server comprises a publish-and-subscribe mechanism to allow remote mechanisms to receive alarm notifications.

### Claim 23 (depends on 19)

A management system as claimed in claim 19, wherein the thresholds are set by Key Performance Indicators.

### Claim 24 (depends on 1)

A system as claimed in claim 1, wherein the metrics include:
attach success rate,
time to complete an Attach procedure,
detach success rate,
time to complete Detach procedure,
abnormal termination rate and cause,
PDP Context Activation success rate,
time to complete PDP Context Activation procedure,
PDP Context De-activation success rate,
time to complete PDP Context De-activation procedure,
PDP Context Abnormal De-activation rate & cause, or
PDP Context Throughput in uplink & downlink.

### Claim 25 (depends on 1)

A system as claimed in claim 1, wherein the metrics include:
service activation success rate,
service completion success rate,
service average bitrate,
service startup and shutdown latencies,
how often the actual bitrate is within x % of maximum bitrate,
how often SDUs are delivered out of order,
number of SDUs lost or detected as erroneous,
residual bit error rates in SDU's subflows,
how often the transfer delay of SDUs is within x % of the maximum allowed, or
how often the actual bitrate is within x % of guaranteed bitrate.

### Claim 26 (depends on 1)

A system as claimed in claim 1, wherein the metrics are classified in one or more of:
a conversation class of telephony speech, VoIP, audio conferencing, or VPN,
a streaming class of one-way video streams (e.g. sports highlights, music videos, security camera feeds), or one-way audio streams (e.g. music or sound broadcasts),
an interactive class of database retrieval, client/server interactions, browsing and Internet access, WAP access, process control, remote sensing, remote control, or file transfer, and
a background class: non-urgent measurement collection, email, or SMS/MMS.
