PCAP Header Encoding for Network Element Identification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data packet capturing methods, such as PCAP, lack the necessary information to identify network elements (NEs) and technology types in telecommunications networks, making it difficult for network operators to troubleshoot and manage mobile communications effectively.

Innovation Solution

A method that extracts and encodes NE identification, type, and technology type information into a standardized packet-capture file header, using a 16-byte packet header in IPV6 format, allowing for easy identification and troubleshooting by encoding NE-identity, NE-type, and technology-type information in specific fields.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If standard PCAP file format is used for packet capture, then compatibility and ease of processing are improved, but the ability to identify network elements and technology types is lost

Engineering Contradiction:
Improveease of processingVSAvoidnetwork element identification information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The packet header is segmented into specific fields: a first field for NE identification, a second field for NE type, and a third field for technology type. This segmentation allows the header to contain multiple types of information in an organized manner, maintaining compatibility while adding identification capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent embeds multiple identification fields within the existing PCAP header structure. The NE identification, NE type, and technology type are nested within the header fields, allowing the standard PCAP format to accommodate extended information without requiring a completely new file format.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Measurement precision

If detailed NE identification information is added to packet headers, then network element identification capability is improved, but header structure complexity increases

Engineering Contradiction:
Improvenetwork element identification capabilityVSAvoidheader structure complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

Different fields within the header are assigned specific purposes: the first field handles NE identification, the second field handles NE type, and the third field handles technology type. This local specialization allows each field to be optimized for its specific function while maintaining overall header structure clarity.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent uses hexadecimal encoding for the NE type and technology type fields, converting these parameters into a compact representation. This parameter transformation reduces the visual complexity of the header while preserving the identification information, making it more manageable for network operators.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240348543A1Encoding Device-Type Identifiers with Captured Mobile Data Packets
Publication Date: 2024.10.17 TC FRANCE SAS
  • US20240348543A1 patent drawing
  • US20240348543A1 patent drawing
  • US20240348543A1 patent drawing

AI summary

Systems and methods for monitoring data packets captured from a network are provided. A method, according to one implementation, includes the step of receiving raw data from a network, where the raw data pertains to mobile communications involving a Network Element (NE). The method also includes the step of extracting information from the raw data to obtain NE information defining a device type, such as network element type, and other information that characterizes the NE. Also, the method includes the step of encoding the NE information in a header of a Packet Capture (PCAP) file.