Adding ECPD Identification and Account Numbers to Pilot Packets

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

  • GGSN

  • P-GW

Applicable Platform(s)

  • ASR 5500

  • VPC-DI

  • VPC-SI

Feature Default

Disabled - Configuration Required

Related Changes in This Release

Not Applicable

Related Documentation

  • Command Line Interface Reference

  • P-GW Administration Guide

  • GGSN Administration Guide

Revision History

Revision Details

Release

First introduced.

21.25

Feature Description

The Pilot Packet feature provides key information about a subscriber session, such as subscriber identity and subscriber IP address, to an external element. When the subscriber allocates or deallocates IP address during an event trigger, a “pilot” packet is generated. Using this information new service such as Subscriber Analytics are enabled and sent in UDP transport.

Pilot Packet consists of the following information in the form of Type Length Values (TLVs):

  • Allocation/De-allocation Flag

  • MSISDN (MDN)

  • IMSI

  • Allocated Address-IPv4

  • Allocated Address-IPv6-Address

  • Allocated NAT IPv4 Address

  • NAT Address Port Chunk Start

  • NAT Address Port Chunk Size

  • Serving Network Identifier

  • Foreign Agent IP Address

  • NAI

  • RAT Type

The operator enables the network element with Pilot packet to gain and report enterprise-level information through the Flexible-Services-Container TLV on SGi interface.

Flexible-Services-Container consists of the following enterprise-level information:

  • Enterprise Customer Profile Database Identification (ECPD ID)

  • Account Number

For example: ECPD ID = 3458312; Account Number = 0442058164-00001

Notes

Following are the important notes:

  • P-GW adds new TLV to the Pilot packet for subscribers, only if configured through CLI and received on S6b in AAA message.

  • P-GW ignores Flexible-Services-Container received in the Re-Auth procedure.

  • The contents and interpretation of the enterprise information (ECPD ID and Account Number) is not required for P-GW or GGSN services. The data is not parsed by P-GW or GGSN and passed transparently in Pilot packet.

Configuring Pilot Packet

To configure Pilot Packets containing key information about a subscriber session to third-party network elements, use the following configuration:

configure 
   context context_name 
      pilot-packet { attribute { foreign-agent-ip-address | nai | rat-type | serving-nw-id | flexible-services-container } | name server_name source-ip-address source_ip_address destination-ip-address destination-ip_address destination-udp-port udp_port_value [ dscp-marking dscp-value ] | trigger rat-change generate { nat-info-only | user-info-and-nat-info | user-info-only } } 
      default pilot-packet { attribute { foreign-agent-ip-address | nai | rat-type | serving-nw-id | flexible-services-container } | trigger rat-change } 
      no pilot-packet { attribute { foreign-agent-ip-address | nai | rat-type | serving-nw-id | flexible-services-container } | name server_name | trigger rat-change } 
      end 

NOTES:

  • pilot-packet { attribute flexible-services-container} : Sends the optional flexible-services-container in Pilot packets.

  • default pilot-packet { attribute flexible-services-container } : Does not send the optional flexible-services -container in Pilot packets.

  • no pilot-packet { attribute flexible-services-container } : Disables flexible services container information in Pilot packets.

Verifying the Configuration

Use the following commands to verify the Pilot packets configuration.

  • show configuration

  • show configuration verbose

show configuration

The output of this command includes the following field.

Table 1. show config Command Output Description
Field Description

flexible-services-container

Indicates that an optional TLV Flexible Services Container is sent in Pilot packets.

The show config verbose command also includes similar field output.