IP Library Granted Patent US 9,450,768
Granted Patent B2
US 9,450,768 · App. 14/471,149 · Granted Sep 20, 2016

Subscriber-specific tracing in communications

Inventors: Jani Olavi Soderlund (Vantaa, FI); Juha Pekka Hyttinen (Kerava, FI); Jyrki Olavi Nousiainen (Tuusula, FI); Tapio Antero Kiviharju (Riihimäki, FI); Niko Markus Savolainen (Kerava, FI)
Assignee: NOKIA SOLUTIONS AND NETWORKS OY
H04L12/1407H04L67/22H04L67/2804H04W8/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,450,768
App. No.
14/471,149
Granted
Sep 20, 2016
Kind
B2
Abstract

A method for subscriber tracing comprises capturing user plane packets in a network apparatus implementing a 3GPP policy and charging enforcement functionality PCEF. Packet-specific metadata is added to a captured user plane packet. The packet-specific metadata may be used for facilitating subscriber-specific troubleshooting of core network elements.

Claims (44)

1. A method for subscriber tracing in a communications system, said method comprising:

capturing, in a network apparatus, user plane packets, wherein the apparatus implements a 3GPP policy and charging enforcement functionality PCEF; and

adding packet-specific metadata to a captured user plane packet,

wherein the packet-specific metadata is used for facilitating subscriber-specific troubleshooting of core network elements, and

wherein the metadata includes

a public part documented in product-specific customer documentation, and/or

a private part intended for troubleshooting by the product vendor, and including information on an exact code point, licensing information, internal resource situation information, and/or other private information.

2. A method according to claim 1 , wherein the metadata includes service awareness metadata and/or packet drop metadata.

3. A method according to claim 1 , wherein the metadata includes one or more of

a PCC rule name identifying a PCC rule, a PCC rule base name identifying a PCC rule base activated by a local default policy or an external server, a PCC rule action, precedence, a PCC filter, a charging rating group, a charging service id, a policy monitoring key, and an identification and a reasoning of a dropped packet.

4. A method according to claim 3 , wherein the PCC rule name has a PCC rule type that is either dynamic or predefined.

5. A method according to claim 1 , wherein the fields needed for the public parts includes at least one of

a rule activation field,

a Gx/Gxc monitoring field,

a dependency to online charging, wherein a rating group visible in the captured packet is the same that is visible on an OCS interface, and

a dependency to offline charging, wherein the rating group visible in the captured packet is the same that is visible in charging data records CDR on Bp and GTP′ interfaces.

6. A method according to claim 5 , wherein the rule activation field includes at least one of a rating group, a service identification, a monitoring key, and a filter for matching traffic to the rule.

7. A method according to claim 1 , further comprising adding one or multiple metadata fields to the same packet.

8. A method according to claim 1 , wherein the metadata indicates to a network operator what was the treatment like in the network apparatus for a specific packet and packet flow.

9. A method according to claim 1 , wherein the metadata enables a network operator to compare the charging and policy control treatment received by different packet flows in the network apparatus for a specific packet and packet flow.

10. A method according to claim 1 , further comprising adding the metadata in a PCAP next generation PCAP-NG dump file format directly to the packet itself.

11. A method according to claim 1 , further comprising encoding the metadata by using a suitable encoding method, such as a type-length-value TLV structure.

12. A method according to claim 1 , wherein the metadata is added to the packet at the specific capture points located in the ingress and/or egress of packet processing.

13. A method according to claim 12 , wherein

the metadata is collected in memory buffers, and

the collected metadata is inserted to a packet at the capture point for sending the metadata as part of a packet capture file to a product-specific data aggregation service.

14. A method according to claim 13 , wherein the packet capture file is analysable by means of a de-facto standard Wireshark tool family.

15. An apparatus comprising:

at least one processor; and

at least one memory including a computer program code,

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to perform any of the method steps of claim 1 .

16. A computer program product embodied on a non-transitory computer-readable medium, said computer-readable medium comprising program instructions which, when run on a computing apparatus, causes the computing apparatus to perform a method according to claim 1 .

17. A method for subscriber tracing in a communications system, said method comprising:

capturing, in a network apparatus, user plane packets, wherein the apparatus implements a 3GPP policy and charging enforcement functionality PCEF; and

adding packet-specific metadata to a captured user plane packet,

wherein the packet-specific metadata is used for facilitating subscriber-specific troubleshooting of core network elements, and

wherein the metadata enables a network operator to compare the charging and policy control treatment received by different packet flows in the network apparatus for a specific packet and packet flow.

18. A method for subscriber tracing in a communications system, said method comprising:

capturing, in a network apparatus, user plane packets, wherein the apparatus implements a 3GPP policy and charging enforcement functionality PCEF; and

adding packet-specific metadata to a captured user plane packet,

wherein the packet-specific metadata is used for facilitating subscriber-specific troubleshooting of core network elements,

wherein the metadata is added to the packet at the specific capture points located in the ingress and/or egress of packet processing,

wherein the metadata is collected in memory buffers, and

wherein the collected metadata is inserted to a packet at the capture point for sending the metadata as part of a packet capture file to a product-specific data aggregation service.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 26, 2014
From: SODERLUND, JANI OLAVI; HYTTINEN, JUHA PEKKA; NOUSIAINEN, JYRKI OLAVI; KIVIHARJU, TAPIO ANTERO; SAVOLAINEN, NIKO MARKUS
To: NOKIA SOLUTIONS AND NETWORKS OY
Reel/Frame 033829/0288 →
Priority Claims (1)
WO PCT/EP2013/068652 · Sep 10, 2013 · international
Continuity (1)
Related Publication 20150071129A1 · Mar 12, 2015