charging architecture

MobileNext Broadband Gateway

Charging for GGSN/PDN Gateway

Published: 2013-02-25

Copyright © 2013, Juniper Networks, Inc.

Juniper Networks, Inc.1194 North Mathilda AvenueSunnyvale, California 94089USA408-745-2000www.juniper.net

Copyright © 2013, Juniper Networks, Inc. All rights reserved.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the UnitedStates and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All othertrademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,transfer, or otherwise revise this publication without notice.

Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that areowned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

MobileNext Broadband Gateway Charging for GGSN/PDN GatewayCopyright © 2013, Juniper Networks, Inc.All rights reserved.

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through theyear 2038. However, the NTP application is known to have some difficulty in the year 2036.

ENDUSER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networkssoftware. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at

http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditionsof that EULA.

Copyright © 2013, Juniper Networks, Inc.ii

http://www.juniper.net/support/eula.html

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

Part 1 Overview

Chapter 1 Charging Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Advice of Charge Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Advice of Charge on the Broadband Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Charging Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Charging in Mobile Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Charging with Data Records (Offline Charging) . . . . . . . . . . . . . . . . . . . . . . . . . 7

Charging in Real Time (Online Charging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Offline Charging Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Online Charging Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Charging Data Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Information Collection and CDR Generation . . . . . . . . . . . . . . . . . . . . . . . . . . 12

CDR Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Charging Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Charging Profile Selection Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Service Sets and Service Filters for Advice of Charge Overview . . . . . . . . . . . . . . . 16

Part 2 Configuration

Chapter 2 Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configuring Offline Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configuring Online Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3 Configuration Tasks for Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring GTP Prime for Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring GTP Prime for Transferring CDRs . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring GTP Prime Peers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring Persistent Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configuring Local Persistent Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Tracing Persistent Storage Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

iiiCopyright © 2013, Juniper Networks, Inc.

Configuring the Solid State Disk for Persistent Storage . . . . . . . . . . . . . . . . . . . . . 27

Initializing the Solid State Disk for Persistent Storage . . . . . . . . . . . . . . . . . . . 28

Ejecting the Solid State Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Installing the Solid State Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring Transport Profiles for Offline Charging . . . . . . . . . . . . . . . . . . . . . . . . 29

Configuring Charging Trigger Events for Offline Charging . . . . . . . . . . . . . . . . . . . . 32

Configuring CDR Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Configuring Charging Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Configuring Charging Profiles for APNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configuring Transport Profiles for Online Charging . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring Charging Trigger Events for Online Charging . . . . . . . . . . . . . . . . . . . . 43

Configuring Credit Control Failure Handling Parameters . . . . . . . . . . . . . . . . 44

Configuring Miscellaneous Online Charging Trigger Events . . . . . . . . . . . . . . 47

Configuring Service Sets and Service Filters for Advice of Charge . . . . . . . . . . . . . 52

Chapter 4 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Example: Configuring Online Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 5 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

[edit unified-edge gateways ggsn-pgw <gateway-name>] Hierarchy Level . . . . 65

all-rgs-on-termination (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . 78

always-include (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

authorization-rejected (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . 80

blacklist (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

block-traffic-pending-reauth-no-quota (Credit Control Failure Handling) . . . . . 82

cc-failure-handling (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

cc-octet-both (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

cc-octet-downlink (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

cc-octet-uplink (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

cc-time (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

cdr-aggregation-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

cdr-profile (Charging Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

cdr-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

cdr-release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

cdrs-per-file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

charging (GGSN or P-GW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

charging-function-name (Transport Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

charging-gateways (Transport Profiles—Offline) . . . . . . . . . . . . . . . . . . . . . . . . . 104

charging-method (Trigger Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

charging-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

container-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

convert-to-offline (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . 108

credit-control-not-applicable (Credit Control Failure Handling) . . . . . . . . . . . . . 110

credit-limit-reached (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . 111

default-rating-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

default-service-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

description (Charging-Related Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

destination-ipv4-address (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

destination-port (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

diameter-profile (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Copyright © 2013, Juniper Networks, Inc.iv


direction (Trigger Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

disable-online-charging (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . 119

disable-replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

disk-space-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

down-detect-time (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

echo-interval (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

end-user-service-denied (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . 124

enable-reduced-partial-cdrs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

exclude (Trigger Profiles—Offline) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

exclude-attributes (CDR Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

file-age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

file-creation-policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

file-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

file-name-private-extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

file-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

gtpp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

grant-grace-quota (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . 143

grant-quota (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

header-type (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

include-quota-holding-time (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . 146

initial-request (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . . . . . 147

local-persistent-storage-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

local-storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

measurement-method (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . 150

mtu (Transport Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

n3-requests (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

node-id (CDR Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

no-mscc-in-ccrt (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

no-path-management (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

offline (Transport Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

offline (Trigger Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

online (Transport Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

online (Trigger Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

override (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

peer (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

peer (Peer Order) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

peer-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

pending-queue-size (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

persistent-storage-order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

profile-id (Charging Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

quota-holding-time (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

quota-request-on-first-packet (Transport Profiles—Online) . . . . . . . . . . . . . . . . 169

quota-threshold (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

quota-validity-time (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

rating-group (Trigger Profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

redirect-reason (Service Filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

reconnect-time (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

reporting-level (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

report-requested-apn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

vCopyright © 2013, Juniper Networks, Inc.

Table of Contents

requested-service-unit (Trigger Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . 177

result-code-based-action (Credit Control Failure Handling) . . . . . . . . . . . . . . . . 178

send-ccri-on-first-packet (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . 179

service (Service Filter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

service-context-id (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . 181

service-mode (Charging Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

service-mode (Transport Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

session-failover-not-supported (Transport Profiles—Online) . . . . . . . . . . . . . . . 186

sgsn-sgw-change-limit (GGSN or P-GW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

single-mscc (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

source-interface (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

switch-back-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

t3-response (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

tariff-time-list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

time-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

traceoptions (Charging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

traceoptions (Local Persistent Storage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

transport-profile (Charging Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

transport-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

transport-protocol (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

trigger-profile (Charging Profiles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

trigger-profiles (GGSN or P-GW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

tx-timeout (Transport Profiles—Online) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

update-request (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . . . 210

user-name (Local Persistent Storage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

user-unknown (Credit Control Failure Handling) . . . . . . . . . . . . . . . . . . . . . . . . . . 212

version (GTP Prime) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

volume-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

watermark-level-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

watermark-level-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

watermark-level-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

world-readable (Local Persistent Storage) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Part 3 Administration

Chapter 6 Monitoring the Charging Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Verifying and Managing the Charging Configuration . . . . . . . . . . . . . . . . . . . . . . . 221

Chapter 7 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

clear unified-edge ggsn-pgw charging cdr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

clear unified-edge ggsn-pgw charging cdr wfa . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

clear unified-edge ggsn-pgw charging local-persistent-storage statistics . . . . . 226

clear unified-edge ggsn-pgw charging path statistics . . . . . . . . . . . . . . . . . . . . . 227

clear unified-edge ggsn-pgw charging transfer statistics . . . . . . . . . . . . . . . . . . 228

request system storage unified-edge charging media start . . . . . . . . . . . . . . . . . 229

request system storage unified-edge charging media stop . . . . . . . . . . . . . . . . . 230

request system storage unified-edge media eject . . . . . . . . . . . . . . . . . . . . . . . . . 231

request system storage unified-edge media prepare . . . . . . . . . . . . . . . . . . . . . . 232

show unified-edge ggsn-pgw charging global statistics . . . . . . . . . . . . . . . . . . . 233

show unified-edge ggsn-pgw charging local-persistent-storage statistics . . . . 236

Copyright © 2013, Juniper Networks, Inc.vi


show unified-edge ggsn-pgw charging path statistics . . . . . . . . . . . . . . . . . . . . . 242

show unified-edge ggsn-pgw charging path status . . . . . . . . . . . . . . . . . . . . . . . 247

show unified-edge ggsn-pgw charging service-mode . . . . . . . . . . . . . . . . . . . . . 250

show unified-edge ggsn-pgw charging transfer statistics . . . . . . . . . . . . . . . . . . 253

show unified-edge ggsn-pgw charging transfer status . . . . . . . . . . . . . . . . . . . . 256

Part 4 Troubleshooting

Chapter 8 Acquiring Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Tracing Charging Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Configuring the Trace Log Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Configuring the Tracing Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Part 5 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

viiCopyright © 2013, Juniper Networks, Inc.

Table of Contents

List of Figures

Part 1 Overview

Chapter 1 Charging Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 1: System Architecture for Advice of Charge and Top-Up . . . . . . . . . . . . . . . 4

Figure 2: Simple Charging Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Figure 3: General Architecture for Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10


Chapter 4 Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Figure 4: Architecture for Online Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

ixCopyright © 2013, Juniper Networks, Inc.

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv


Chapter 3 Configuration Tasks for Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Table 3: Bearer Information Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table 4: Attribute Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 5 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table 5: Charging Behavior Based on convert-to-offline Configuration . . . . . . . . 109

Table 6: Charging Behavior Based on disable-online-charging Configuration . . . 119

Part 3 Administration

Chapter 7 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Table 7: show unified-edge sgw charging global statistics Output Fields . . . . . . 233

Table 8: show unified-edge ggsn-pgw charging local-persistent-storage statistics

Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

Table 9: show unified-edge ggsn-pgw charging path statistics Output Fields . . 243

Table 10: show unified-edge ggsn-pgw charging path status Output Fields . . . 248

Table 11: show unified-edge ggsn-pgw charging service-mode Output Fields . . 250

Table 12: show unified-edge ggsn-pgw charging transfer statistics Output

Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Table 13: show unified-edge ggsn-pgw charging transfer status Output

Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Part 4 Troubleshooting

Chapter 8 Acquiring Troubleshooting Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Table 14: Charging Tracing Flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

xiCopyright © 2013, Juniper Networks, Inc.

About the Documentation

• Documentation and Release Notes on page xiii

• Supported Platforms on page xiii

• Documentation Conventions on page xiii

• Documentation Feedback on page xv

• Requesting Technical Support on page xv

Documentation and Release Notes

To obtain the most current version of all Juniper Networks®

technical documentation,

see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/.

If the information in the latest release notes differs from the information in the

documentation, follow the product Release Notes.

Juniper Networks Books publishes books by Juniper Networks engineers and subject

matter experts. These books go beyond the technical documentation to explore the

nuances of network architecture, deployment, and administration. The current list can

be viewed at http://www.juniper.net/books.

Supported Platforms

For the features described in this document, the following platforms are supported:

• MX240 Routers

• MX960 Routers

• MX480 Routers

Documentation Conventions

Table 1 on page xiv defines notice icons used in this guide.

xiiiCopyright © 2013, Juniper Networks, Inc.

http://www.juniper.net/techpubs/

http://www.juniper.net/books

http://www.juniper.net/techpubs/en_US/release-independent/junos/information-products/pathway-pages/mx-series/mx240/index.html



Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Table 2 on page xiv defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

ExamplesDescriptionConvention

To enter configuration mode, typetheconfigure command:

user@host> configure

Represents text that you type.Bold text like this

user@host> show chassis alarms

No alarms currently active

Represents output that appears on theterminal screen.

Fixed-width text like this

• A policy term is a named structurethat defines match conditions andactions.

• JunosOSSystemBasicsConfigurationGuide

• RFC 1997,BGPCommunities Attribute

• Introduces or emphasizes importantnew terms.

• Identifies book names.

• Identifies RFC and Internet draft titles.

Italic text like this

Configure the machine’s domain name:

[edit]root@# set system domain-namedomain-name

Represents variables (options for whichyou substitute a value) in commands orconfiguration statements.

Italic text like this

• To configure a stub area, include thestub statement at the[edit protocolsospf area area-id] hierarchy level.

• The console port is labeledCONSOLE.

Represents names of configurationstatements, commands, files, anddirectories; configuration hierarchy levels;or labels on routing platformcomponents.

Text like this

stub <default-metricmetric>;Enclose optional keywords or variables.< > (angle brackets)

Copyright © 2013, Juniper Networks, Inc.xiv


Table 2: Text and Syntax Conventions (continued)

ExamplesDescriptionConvention

broadcast | multicast

(string1 | string2 | string3)

Indicates a choice between the mutuallyexclusive keywords or variables on eitherside of the symbol. The set of choices isoften enclosed in parentheses for clarity.

| (pipe symbol)

rsvp { # Required for dynamicMPLS onlyIndicates a comment specified on thesame line as the configuration statementto which it applies.

# (pound sign)

community namemembers [community-ids ]

Enclose a variable for which you cansubstitute one or more values.

[ ] (square brackets)

[edit]routing-options {static {route default {nexthop address;retain;

}}

}

Identify a level in the configurationhierarchy.

Indention and braces ( { } )

Identifies a leaf statement at aconfiguration hierarchy level.

; (semicolon)

J-Web GUI Conventions

• In the Logical Interfaces box, selectAll Interfaces.

• To cancel the configuration, clickCancel.

Represents J-Web graphical userinterface (GUI) items you click or select.

Bold text like this

In the configuration editor hierarchy,select Protocols>Ospf.

Separates levels in a hierarchy of J-Webselections.

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can

improve the documentation. You can send your comments to

[email protected], or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/ . If you are using e-mail, be sure to include

the following information with your comments:

• Document or topic name

• URL or page number

• Software release version (if applicable)

Requesting Technical Support

Technical product support is available through the Juniper Networks Technical Assistance

Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,

xvCopyright © 2013, Juniper Networks, Inc.

About the Documentation

mailto:[email protected]

https://www.juniper.net/cgi-bin/docbugreport/

or are covered under warranty, and need post-sales technical support, you can access

our tools and resources online or open a case with JTAC.

• JTAC policies—For a complete understanding of our JTAC procedures and policies,

review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

• Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/.

• JTAC hours of operation—The JTAC centers have resources available 24 hours a day,

7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online

self-service portal called the Customer Support Center (CSC) that provides you with the

following features:

• Find CSC offerings: http://www.juniper.net/customers/support/

• Search for known bugs: http://www2.juniper.net/kb/

• Find product documentation: http://www.juniper.net/techpubs/

• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

• Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

• Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

• Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

• Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verify service entitlement by product serial number, use our Serial Number Entitlement

(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Casewith JTAC

You can open a case with JTAC on the Web or by telephone.

• Use the Case Management tool in the CSC at http://www.juniper.net/cm/.

• Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.

Copyright © 2013, Juniper Networks, Inc.xvi


http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf

http://www.juniper.net/support/warranty/

http://www.juniper.net/customers/support/

http://www2.juniper.net/kb/

http://www.juniper.net/techpubs/

http://kb.juniper.net/

http://www.juniper.net/customers/csc/software/

https://www.juniper.net/alerts/

http://www.juniper.net/company/communities/

http://www.juniper.net/cm/

https://tools.juniper.net/SerialNumberEntitlementSearch/

http://www.juniper.net/cm/

http://www.juniper.net/support/requesting-support.html

PART 1

Overview

• Charging Overview on page 3

1Copyright © 2013, Juniper Networks, Inc.

CHAPTER 1

Charging Overview

• Advice of Charge Overview on page 4


• Offline Charging Overview on page 8

• Online Charging Overview on page 9

• Charging Data Records on page 11

• Charging Profiles on page 14

• Service Sets and Service Filters for Advice of Charge Overview on page 16


Advice of Charge Overview

The Advice of Charge (AoC) feature provides a subscriber with information about any

applicable charges when the subscriber uses a service. AoC information is providedbefore

the subscriber uses the service, and the subscriber must accept the charges in order to

use the service. This is in contrast with typical charging scenarios where subscribers who

use a service are provided information about any charges only after they have used the

service.

For prepaid subscribers, the charges are applied in real time until the subscriber’s quota

is exhausted. The subscriber is then given the opportunity to recharge; this is called

Top-Up.

The MobileNext Broadband Gateway configured as a Gateway GPRS Support Node

(GGSN) or Packet Data Network Gateway (P-GW) can be configured to provide AoC

information to subscribers. Currently, AoC and Top-Up are provided for prepaid

subscribers. Figure 1 on page 4 displays the overall architecture for the gateway

components and the functional groupings for AoC and Top-Up.

Figure 1: SystemArchitecture for Advice of Charge and Top-Up

PCRFPolicy and chargingrules function

OFCSOffline ChargingSystem

OCSOnline ChargingSystem

AoCAdvice of ChargeServer

AFApplication Function

SPRSubscriber ProfileRepository

Ga GyGx

Ga

Gx

Gy

PDN Gateway(PCEF and charging entity)

g040

808

This topic includes the following sections:

• Advice of Charge on the Broadband Gateway on page 4

Advice of Charge on the Broadband Gateway

The broadband gateway provides AoC and Top-Up features using HTTP redirection. The

subscriber HTTP traffic is redirected to an AoC or Top-Up server based on triggers provided

by the Online Charging System (OCS). HTTP traffic is redirected for one of the following

reasons:

• The OCS must notify subscribers who request a new service about the charges.



• The OCS must notify subscribers of tariff changes when they roam in a foreign public

land mobile network (PLMN).

• The OCS has sent the final unit indication with the action set to redirect and the

subscriber runs out of quota.

The following is a high-level overview of the AoC process:

1. The subscriber who is using online charging connects to or roams into a new PLMN.

2. The broadband gateway sends a Credit Control Request (CCR) message to the OCS.

3. The OCS analyzes the information in the CCR message and determines that the

subscriber must be redirected.

4. The OCS requests redirection by sending the appropriate information in the Credit

Control Answer (CCA) message.

5. The broadband gateway sends the redirect URL (constructed from the information

in the CCA message) to the subscriber’s user equipment (UE).

6. The user equipment connects to the redirect URL and the broadband gateway forwards

the request to the AoC or Top-Up server.

7. The AoC or Top-Up server sends a response to user equipment and provides

information about new tariff plans and recharge options.

8. The subscriber tops up (recharges) or agrees to the tariff.

9. The AoC or Top-Up server informs the OCS about the acceptance charges or the

top-up.

10. The subscriber continues the browsing session, with the broadband gateway forwarding

the requests.

RelatedDocumentation

Configuring Service Sets and Service Filters for Advice of Charge on page 52•


Charging Overview

Charging is an umbrella term that often covers not only charging, but also the rating and

billing of services. Together, charging, rating and billing combine to assure that service

providers are compensated by their customers or subscribers for the delivery of services.

More specifically, charging is used to describe the metering of services that are not free

or are bundled in other ways with basic service features (such as handoffs). The opposite

of a charge is a credit. Together, in the process called rating, charges and credits are

applied to a subscriber’s account to determine the periodic amount due to the service

provider. If charges exceed credits, the subscriber’s account is billed for a certain amount.

Monthly telephony billing statements used to have a section called “other charges and

credits” where these items were detailed, usually by date.


Chapter 1: Charging Overview

Charges can be determined by a number of different criteria, alone or in combination:

• Time (duration), often variable by time of day or distance between endpoints

• Pre-paid credits, which are consumed by users and often have a quota that can be

exhausted

• Artificial units, which have no basis in reality, such as the old “message units” for

telephony services

Charging rates can be set by contract or by public documents (called “tariffs”) approved

by a regulating entity. Tariffs and contract terms can vary by time of day, day of the week,

or other intervals.

Service charges can be flat-rate or metered based on the various criteria outlined above.

Flat-rate services are popular with customers (especially those on tight budgets),

predictable, simple to maintain from an accounting perspective (few disputes arise over

flat-rate services), and easy to bill. On the other hand, flat-rate services can deprive the

service provider of additional revenues during periods of high usage and can result in

forced expenses on the part of the subscriber during periods of low usage.

Metered services are popular with customers when services are inexpensive compared

to other items in a budget, unpredictable, difficult to maintain from an accounting

perspective (many disputes arise over metered services), and more complex to bill.

However, in contrast to flat-rate services, metered services provide additional revenues

when resource use is high (due to a suddenly popular service), spreading the financial

burden among customers based on actual usage.

The accrued amount of subscriber charges can be conveyed to the subscriber in real time

as they occur, periodically (monthly bills were a common feature in telephony), or on

request. The use of one main method need not preclude the others.

Charging in Mobile Networks

In the mobile network, it is important to have detailed and accurate monitoring of service

usage on the MobileNext Broadband Gateway so that proper charging information can

be generated for millions of customers. In the Third-Generation Partnership Project

(3GPP), there are three distinct aspects to the process that translates service use into

a bill for services. These aspects are charging, rating, and billing. Charging gathers statistics

about service usage for each customer. Rating is the process of determining how much

each service costs each particular customer, based on the services contracted or tariffed.

Billing is the process of actually generating the customer’s invoice for services.

The MobileNext Broadband Gateway is the anchor of the data call and contains most

of the subscriber context information. The broadband gateway is responsible for collecting

charging information related to the external data network usage and to network resource

usage on the Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway

(P-GW), including the amount of data categorized by quality of service (QoS), the user

protocols, and the usage of the packet data protocol address. Packet data volume in

both the uplink (from the Gn-to-Gi interface) and downlink (from the Gi-to-Gn interface)

directions is counted separately.



Long Term Evolution (LTE) mobile networks define two different types of charging

systems: Offline Charging Systems (OFCS) and Online Charging Systems (OCS). Offline

charging is usually used for post-paid services for which the subscriber receives a bill

(typically monthly). Online charging is well suited for pre-paid services. Online charging

can affect a session in real time. For example, a session can be terminated if the subscriber

runs out of credit. Offline charging cannot affect subscribers in real time. Typically, a

service provider will provision both offline and online charging for subscribers.

Charging with Data Records (Offline Charging)

In offline charging, a charging trigger monitors the subscriber’s use of services and

resources and generates charging events that describe the system charge activities. A

charging data function, which can be integrated with the gateway device, processes

charging events and collects these as Charging Data Records (CDRs). The CDRs are

written to files or transferred to the OFCS charging gateway over the Ga interface using

the GPRS Tunnleing Protocol (GTP) prime (GTPP) protocol. The billing domain

determines the cost of the resources used and invoices the subscriber.

If the user is roaming, the billing domain and charging gateway are in the subscriber’s

home network, while the charging data function is in the same network as the Serving

Gateway (S-GW) and Packet Data Network Gateway (P-GW). The visited network also

uses the roaming CDRs to invoice the home network for the roaming subscriber’s use of

visited resources (a process called settlement).

Charging in Real Time (Online Charging)

In online charging, a charging trigger in the P-GW sends a credit request to the online

charging function over the Gy interface to see if a session can begin. A rating function

determines the subscriber’s balance and replies with a credit authorization (which usually

also specifies how long the session can last or how much data can be transferred). The

charging trigger monitors the session and use of resources. If the allocation nears its limit,

another credit request is sent for additional resources. When the session is over, the

charging trigger notifies the OCS with regard to any remaining credit to return to the

subscriber.

If the user is roaming, the OCS is always in the subscriber’s home network. As in offline

charging, the visited network uses the roaming CDRs to invoice the home network for the

roaming subscriber’s use of visited resources (settlement).


Offline Charging Overview on page 8•


• Configuring GTP Prime for Charging on page 23

• Configuring Persistent Storage on page 25



• Example: Configuring Online Charging on page 55



Offline Charging Overview

The MobileNext Broadband Gateway supports offline charging, which is commonly used

in a postpaid environment. The broadband gateway provides mobile operators with an

intelligent charging service that has flexible provisioning and accurate resource usage

record collection for their mobile subscribers. The broadband gateway gathers Charging

Data Records (CDRs) and delivers them to the charging gateway function (CGF) over

the Ga interface using the GTP Prime protocol. The billing function is distributed across

all modules of the broadband gateway, which performs these tasks for billing:

• Accurate CDR creation and closure

• Partial record generation

• ASN.1 or 3GPP formatting of CDRs prior to transfer to CGF or local storage

• Support of GTP Prime protocol stack to transfer CDRs to the CGF

• Support of primary, secondary, and tertiary CGF for redundancy of each charging profile

Charging information collection does not affect real-time operations and is transferred

over the Ga interface using the GTP Prime protocol. The network element generates the

CDR for each subscriber and reports it periodically to the charging gateway. The charging

gateway then optionally reformats and transfers the collected CDRs to the operator’s

billing system for billing purposes.

Figure 2 on page 8 shows the components in a sample charging topology.

Figure 2: Simple Charging Topology



The provisioning of the charging services follows this process:

1. Configure the CGF or local storage.

2. Create the transport profile and associate the primary, secondary, and tertiary CGF.

3. (Optional) Configure the CDR and trigger profiles.

4. Create a charging profile with a profile ID and the associated transport, CDR, and

trigger profiles. The profile ID is used to match against the charging characteristic

information element sent in the GTP create request or the RADIUS profile ID

attribute-value pairs (AVPs) from the RADIUS authentication response.

5. In the access point name (APN) configuration, configure the charging profile selection

order as static to select locally configured charging profiles.

The binding of the charging services, as well as the charging information collection,

follows this process:

1. The broadband gateway starts to establish a bearer when the broadband gateway

receives the request from the mobile subscriber to create a packet data protocol

(PDP) context.

2. For each new bearer created in the broadband gateway, the configured charging

profile selection order algorithm is applied and a charging profile is associated with

the bearer.

3. The broadband gateway generates a container or CDR for every trigger or signaling

event that the operator wants reported for this subscriber.

4. When the mobile subscriber terminates the session, the final network usage is reported

to the CGF by the broadband gateway.


Charging Overview on page 5•







Online Charging Overview

Online charging is part of a complete MobileNext Broadband Gateway configuration,

including policy and charging rules, quality-of-service (QOS) determination, and overall

charging considerations. The Gy interface connects the Packet Data Network Gateway

(P-GW) and Online Charging System (OCS).

The unique aspect of online charging is that charging information can affect the

subscriber’s access to service in real time. The OCS delivers information to the P-GW



that is used to control credits. Events that are of interest to online charging include bearer

resource usage, especially data services. Data usage information is converted to charging

events which are sent to the OCS, where available credit and rating is used to determine

service access parameters. The OCS can deny use of the resource when credits are low,

often by terminating the call. Figure 3 on page 10 shows the overall architecture for the

gateway components and the functional groupings for policy and charging.

Figure 3: General Architecture for Charging


OCSOnline ChargingServer


AFApplication function

Subscription ProfileRepository (SPR)

PDN Gateway(PCEF andcharging entity)

Serving Gateway(S-GW) g0

4079

4

Ga

GyGx

S5/S8

S5/S8

Ga

Gy

Gx

The Gy interface between P-GW and OCS uses the Diameter protocol.











Charging Data Records

The MobileNext Broadband Gateway gathers charging information in Charging Data

Records (CDRs). The broadband gateway supports different charging format versions.

The broadband gateway generates CDRs that contain the following types of information

to charge a mobile station user or subscriber for accessing data from access point name

(APN) networks:

• Data volume—Amount of data sent to and received from the APN networks.

• Duration of packet data protocol (PDP) context—Length of PDP context or call.

• Quality-of-service (QoS) classes—Priority at which requested data is transported.

• Roaming—Charges imposed for subscriber roaming among SGSNs belonging to a

mobile operator or between different mobile operators.

• Tariff—Charges imposed based on the time of day.

CDRs can be delivered by the following methods:

• CDRs are transferred directly to a charging gateway server using the GTP Prime protocol.

The GTP Prime protocol supports UDP or TCP as the transport protocol, and IPv4

addresses. You must configure the charging gateways as GTP Prime peers. The peers

can be configured for use by transport profiles as primary, secondary, or tertiary servers.

The broadband gateway supports sending the following messages:

• Node Alive Response—Response to a Node Alive Request received from the charging

gateway function (CGF). The Node Alive Request message is used to indicate that

a node in the network has started its service.

• Echo Request and Echo Response—The Echo Request message detects the path

status between the CGF and the broadband gateway and should not be sent more

than once every 60 seconds using UDP as the transport protocol.

• Redirect Request—CGF can send Redirect Request messages to the broadband

gateway to advise that received CDR traffic is to be redirected to another CGF or

that the next node in the chain (such as a mediation device or billing computer) has

lost its connection to the CGF. When the request is to redirect to another CGF, the

transport profile switches to the recommended CGF only if it is configured as a peer

in the transport profile; otherwise, it switches to the next highest-priority peer in the

transport profile.

• CDRs are logged to the local persistent storage and eventually retrieved by a charging

gateway using the File Transfer Protocol (FTP). In broadband gateways configured

with a backup Routing Engine, a mirror directory of CDRs is available.

Local persistent storage stores the CDRs in the form of files on the Routing Engine.

When the transport profile is configured to use local persistent storage for CDRs, the

session DPC sends the CDRs to the Routing Engine as temporary log files. When the

triggers (such as file age, file size, or CDR count) acting on the temporary log files are



reached, the temporary log file is closed and moved to the final log directory where it

is available for transfer by the operator. By default, the configured user or root user is

authorized to access the files. However, you can configure the log files to be readable

by all users.

The final CDR log files are stored in the /opt/mobility/charging/ggsn/final_log directory

in the filename format NodeID_-_PIC_-_transport-profile-id_-_RC.date_-_time[.PI].cdr,

where:

• NodeID—Name of the host that generated the file.

• PIC—The PIC number generating the CDR.

• transport-profile-id—The number of the transport profile generating the CDR.

• RC—Running count or sequence number, starting with the value of 1.

• date—Date when the CDR file was closed in the format YYYYMMDD, where YYYY is

the year, MM is the month (01-12), and DD is the day (01-31).

• time—Time when the CDR file was closed in the format HHMMshhmm, where HH is

the local time hour of day (00-23), MM is the local time minute of the hour (00-59),

s is the sign of local time differential from UTC (+ or -),hh is the local time differential

hour (00-23), and mm is the local time differential minute (00-59).

• PI—(Optional) Private information that is explicitly configured.

• cdr—File extension is always cdr.

For example, a final CDR log file could be named

magnet-PGW-1-3_-_155970.20120612_-_0950-0700.asn.cdr.

The charging gateway consolidates charges for a particular PDP context from the

broadband gateway. Each CDR is marked with a charging ID that identifies the mobile

station user and the particular PDP session. This charging ID correlates information

generated by the broadband gateway. Each CDR also includes a Local Record Sequence

Number (LRSN) that is allocated sequentially and is unique for each CDR on the same

session DPC. The LRSN is the IP address of the broadband gateway and the node ID. The

charging gateway uses the LRSN to identify missing records. The billing gateway uses

the charging ID and the LRSN to identify CDRs. The billing gateway server generates the

information used in the bill that is sent to the subscriber.

Information Collection and CDRGeneration

Upon establishment of a PDP context, the broadband gateway opens a first partial CDR

if it is configured to generate CDRs for the PDP context. The broadband gateway generates

this CDR in Abstract Syntax Notation 1 (ASN.1) format. This format provides a common

syntax for data transmitted between different communication systems.

This partial CDR contains static and dynamic information. The static information includes

details such as the type of record (in this case, a CDR) and the international mobile station

identifier (IMSI) of the subscriber. Additional information included in the CDR is based

on the dynamic usage of an APN network by the subscriber. To collect dynamic usage



information, the broadband gateway monitors the uplink and downlink bearer traffic

associated with a PDP context.

A container holds the incremental statistics for the bearer. Each CDR has the containers

that belong to the same bearer. Depending on the event, a container can be added to

the CDR. You can configure the maximum number of containers for the CDR. Upon

reaching this limit, the CDR is closed and sent to the CGF. The broadband gateway adds

a container to the partial CDR each time one of the following chargeable events occurs:

• The QoS changes.

• The tariff changes.

• Other charging conditions are satisfied.

For example, if the QoS changes, a container is added. If the tariff changes, another

container is added. If the QoS changes again, another container is added and so on until

the maximum number of containers is reached.

The broadband gateway adds a container to the partial CDR and closes the CDR when

one of the following chargeable events occurs:

• The PDP context terminates.

• The time limits are exceeded.

• The volume limits are exceeded.

The broadband gateway closes a partial CDR and opens a subsequent partial CDR if one

of the following occurs:

• The configured number of containers for the container limit attribute is reached.

• A configurable data volume limit for the first partial CDR is reached. Each container

has a data volume count associated with the chargeable event. Initially, the first partial

CDR contains one container with 0 bytes of data volume.

• A configurable time limit for the first partial CDR is reached.

• The maximum of five SGSN or S-GW changes is reached. A container can include a

list of up to five changes.

A very active broadband gateway has to generate a large number of CDRs. Many CDRs

contain a lot of information that is not necessary for a given PDP context or is known to

the charging gateway by other means. To minimize the size of the generated CDR packets,

the charging configuration contains a variety of CDR attributes that can be excluded from

CDRs if the information is not necessary.

After a PDP context terminates, a broadband gateway adds a container to the current

partial CDR, closes it, and delivers it to a charging gateway using the configured CDR

delivery method.



CDRDelivery

CDR delivery to a charging gateway is based on the transport profile configuration. You

can configure primary, secondary, and tertiary external charging gateways or local

persistent storage in the transport profile. You must configure either the external charging

gateways or local persistent storage, or both.

To support high throughput, the distributed control plane modules on the broadband

gateway independently send CDRs to the charging gateway through their own UDP/TCP

communication path. However, connectivity to the charging gateway is fate-shared.

Thus, when one control plane reports loss of connectivity, all control planes switch to

the next charging gateway in the peer order. This behavior also applies to GTP Prime

echo failure, node alive, and redirect messages. The redirect message can contain the

recommended charging gateway to switch to, but the transport profile switches to this

charging gateway only if it is configured in the transport profile. Otherwise, it is redirected

to the next higher-priority charging gateway in the peer order.

If the broadband gateway loses connectivity to all the charging gateways or the charging

gateway is too slow, each control plane has a staging area to temporarily prevent the

loss of CDRs. To prevent CDR and charging container record loss, all records are backed

up to the backup control plane if redundancy is configured.





• Configuring Offline Charging on page 21

• Configuring Transport Profiles for Offline Charging on page 29


Charging Profiles

The broadband gateway associates a charging profile with a mobile subscriber when a

bearer is established. The charging profile specifies the charging behavior to apply based

on the subscriber’s charging characteristics. The charging behavior includes the charging

mechanism, charging information sets, and charging transport behavior. The charging

behavior depends on the charging type (for example, charging gateway or RADIUS server)

and the associated charging profile.

Charging profiles can reference these profiles, which define the charging behavior:

• CDR profile—Defines the attributes in each CDR transmitted to the charging gateway.

You can enable the generation of reduced partial CDRs and configure the exclusion of

information elements from the CDR.

• Transport profile—Defines how to transfer the CDR to the charging gateway.



You can specify information about the CDRs, including CDR format and aggregation

limit, being transferred to the charging gateways. You can specify the order of the

charging gateways.

• Trigger profile—Defines the effective charging events that trigger CDR creation and

container addition or closure.

You can specify triggers, including:

• Time limits—Maximum age of collected charging data before a subsequent CDR is

generated.

• Volume limits—Maximum amount of collected charging data before a subsequent

CDR is generated.

• Tariff activation times—Time windows in which tariffs change for charging purposes.

If the services provided by an APN network have different time windows and tariffs,

you can configure the broadband gateway to update CDRs when the tariffs change.

• Container limits—Maximum number of containers in each CDR before a subsequent

CDR is generated.

• Bearer changes—Bearer information changes to ignore for charging data updates.

Charging updates are not triggered by changes to this information.

Charging Profile Selection Process

The MobileNext Broadband Gateway has a highly flexible charging profile selection

algorithm that enables the operator to choose the appropriate charging configuration

for each subscriber. Provisioning is done for each APN, where the operator can specify

the profile selection order for the charging profile.

You can specify that the charging profile be selected from the following sources in the

preferred order:

• Subscriber type (static)—Use the configured charging profile for the type of subscriber

(home, roamer, or visitor). If the charging profile for the type of subscriber is not

configured for the APN, then the default profile is used if configured.

• SGSN or Serving Gateway (serving)—Use the charging profile sent by the SGSN or

Serving Gateway.

• RADIUS server (radius)—Use the charging profile provided by the RADIUS server.

If the charging profile cannot be selected from the first source in the profile selection

order, then the algorithm will try the next source. If no charging profile can be selected

from any source, then charging is disabled for the subscriber.




• Configuring Charging Profiles on page 38




• Configuring Charging Trigger Events for Offline Charging on page 32

• Configuring CDR Attributes on page 35

• Configuring Charging Profiles for APNs on page 40


Service Sets and Service Filters for Advice of Charge Overview


applicable charges before the subscriber uses a service, or when the subscriber’s quota

is exhausted. This intervention is provided by “filtering” or sifting the packet traffic to find

those requiring AoC treatment. The AoC feature parameters are configured in several

places that all come together in a firewall filter and a service set attached to the mobile

interface (mif) of an access point name (APN) for input and output traffic. For AoC

purposes, you apply the AoC service set and filter to input and output traffic. The service

set and service filter names are variables, but must conform to usual Junos OS naming

rules.

The broadband gateway finds traffic packets that require AoC notification and sends

the packets to a services interface (usually an aggregated multiservices [ams-] interface).

The services PIC forwards the information to the AoC server and then relays the reply to

the user device.

In addition to the service set, firewall service filter, and mobile interface configuration,

the AoC feature requires the configuration of a zero-rated or unlimited rating group (RG)

to redirect traffic towards the AOC and Top-up server for recharge when the subscriber

quota is exhausted.

Therefore, several individual configurations all come together when the AoC feature is

applied to the mobile interface:

• The PCEF profile configured at the [edit servicespcefprofile]hierarchy level. This profile

must be referenced in the AoC service set configured at the [edit services service-set]

hierarchy level.

• The AoC service filter configured at the [edit firewall family inet service-filter

aoc-filter-name] hierarchy level. This filter sifts through the packet flow to detect those

needing AoC.

• The service set and service filters applied to the mobile interface (mif) configured at

the [edit interfacesmif] hierarchy level. The service sets and service filters are applied

to input and output traffic.

• The Policy and Charging Control (PCC) action profile configuration to create a

zero-rated rating group, and the PCC rule configuration to create a zero-rated flow

that references the configured PCC action profile.

All four must be configured properly in order for AoC to function as intended.





• Configuring Service Sets and Service Filters for Advice of Charge on page 52

• Configuring Policy and Charging Control Action Profiles

• Configuring Application-Aware Policy and Charging Control Rules



PART 2

Configuration

• Configuration Overview on page 21

• Configuration Tasks for Charging on page 23

• Configuration Examples on page 55

• Configuration Statements on page 65


CHAPTER 2

Configuration Overview


• Configuring Online Charging on page 22

Configuring Offline Charging

You can configure the charging function on the MobileNext Broadband Gateway. The

broadband gateway supports the configuration of offline charging. Offline charging can

be configured to send Charging Data Records (CDRs) to charging gateways, to store

CDRs on local physical storage, or both.

To configure the broadband gateway for offline charging:

• Configure the GPRS tunneling protocol (GTP) Prime properties for transmitting the

CDR to the external charging gateway.

You must perform this task if you are using an external charging gateway. You can also

configure the local persistent storage options to store CDRs on the Routing Engine.

• Configure the local persistent storage options on the Routing Engine for the CDRs.

You must perform this task if you want to configure offline charging and do not configure

an external charging gateway.

• Configure the transport profile, which specifies information about the CDRs being

transferred to the specified charging gateways, including the CDR format and

aggregation limit.

• (Optional) Configure the trigger profile, which specifies the charging events that trigger

the creation of the CDR or the addition or closure of the container.

• (Optional) Configure the CDR profile, which specifies the attributes in each transmitted

CDR.

• Configure the charging profile, which specifies the charging behavior to apply based

on profiles included in the charging profile. The included profiles must be defined.

• Configure the charging profiles for the access point names (APNs).

• Configure tracing for charging operations.



Configuring GTP Prime for Transferring CDRs on page 23•







• Tracing Charging Operations on page 263


Configuring Online Charging

You can configure the charging function on the MobileNext Broadband Gateway. The

broadband gateway supports the configuration of online charging, which enables real-time

charging of subscribers. The online charging configuration determines how online

messages are transported between the broadband gateway and the Online Charging

System (OCS), what the gateway does during credit control failure, and other

miscellaneous attributes. The Gy interface connects the Gateway GPRS Support Node

(GGSN) or Packet Data Network Gateway (P-GW) and the OCS.

To configure the broadband gateway for online charging:

• Configure the transport profile, which specifies how online charging messages between

the GGSN or P-GW and the OCS are transported.

• (Optional) Configure the trigger profile, which specifies the credit control failure handling

parameters and other miscellaneous online charging attributes.

• Configure the charging profile, which specifies the charging behavior to apply based

on profiles included in the charging profile. The included profiles must be previously

configured on the broadband gateway.

• Configure tracing for charging operations.



• Configuring Charging Trigger Events for Online Charging on page 43

• Configuring Transport Profiles for Online Charging on page 41






CHAPTER 3

Configuration Tasks for Charging



• Configuring the Solid State Disk for Persistent Storage on page 27









Configuring GTP Prime for Charging

To configure GPRS tunneling protocol (GTP) Prime to transfer Charging Data Records

(CDRs), perform these tasks:

• Configuring GTP Prime for Transferring CDRs on page 23

• Configuring GTP Prime Peers on page 24

Configuring GTP Prime for Transferring CDRs

CDRs are transferred to a charging gateway using GTP Prime or logged to a Routing

Engine hard disk and eventually retrieved by a charging gateway using FTP.

To configure global GTP Prime options to transfer CDRs:

1. Specify that you want to configure GTP Prime properties for the gateway called MBG1.

[edit]user@host# edit unified-edge gateways ggsn-pgwMBG1 charging gtpp

2. Specify the destination port number of the charging gateway function (CGF) server.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set destination-port port-number


3. Specify the source interface from which GTP Prime packets will be sent.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set source-interface interface-name <ipv4-address>

4. Specify the transport protocol.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set transport-protocol (udp | tcp)

5. Specify the GTP Prime version.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set version (v0 | v1 | v2)

6. Specify the GTP Prime header type.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set header-type (long | short)

7. Specify that path management is disabled. This option cannot be used with the echo

request interval.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set no-path-management

8. Specify the GTP Prime echo request interval for path management.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set echo-interval seconds

9. Specify the number of retries of GTP Prime messages upon timeout.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set n3-requests requests

10. Specify the response timeout value for the GTP Prime request message.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set t3-response response-interval

11. Specify the time to wait before declaring a CGF as down.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set down-detect-time seconds

12. Specify the time after which to retry the connection to the CGF server.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set reconnect-time seconds

13. Specify the maximum number of Data Record Transfer (DRT) messages awaiting an

acknowledgment.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# set pending-queue-size queue-size

Configuring GTP Prime Peers

CDRs are transferred to a charging gateway using GTP Prime. The charging gateway is

the GTP Prime peer. The charging gateway peer inherits the global GTP Prime values.

You configure the GTP Prime peer only if you want to override any of the global GTP

Prime values.



To configure the GTP Prime peer to transfer CDRs:

1. Specify the name of the CGF peer for which you are configuring GTP Prime properties.

Use this peer name to configure the peer order in the transport profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp]user@host# edit peer peer-name

2. Specify the destination IPv4 address of the CGF peer.

[edit unified-edge gateways ggsn-pgwMBG1 charging gtpp peer peer-name]user@host# set destination-ipv4-address ip-address

3. (Optional) Specify any of the global GTP Prime options that you want to override for

this charging gateway.


Configuring Offline Charging on page 21•



Configuring Persistent Storage

You can store Charging Data Records (CDRs) locally on the Routing Engine hard disk.

You must configure the persistent storage order in the transport profile before CDRs can

be stored locally on the Routing Engine.

To configure local persistent storage for the CDRs, perform these tasks:

• Configuring Local Persistent Storage on page 25

• Tracing Persistent Storage Operations on page 26

Configuring Local Persistent Storage

To configure local persistent storage of the file containing the CDRs:

1. Specify that you want to configure local persistent storage.

[edit]user@host# edit unified-edge gateways ggsn-pgwMBG1 charginglocal-persistent-storage-options

2. Specify the file age, in minutes.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set file-age value

3. Specify the file size, in MB.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set file-size value

4. Specify the number of CDRs for each file.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set cdrs-per-file value


Chapter 3: Configuration Tasks for Charging

5. Specify that CDR log files are not replicated to the standby Routing Engine.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set disable-replication

6. Specify the user authorized to access the files.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set user-name username

7. Specify that CDR log files can be accessed for reading by all users.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set world-readable

8. Specify the private extension for the filename.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set file-name-private-extension string

9. Specify whether the CDR file is shared across all nodes for a charging group or is unique

to a charging group in each node.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set file-creation-policy (unique-file | shared-file)

10. Configure the CDR file format as 3GPP 32 297 format or raw ASN.1 format.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set file-format (3gpp | raw-asn)

11. Configure the disk policy for when the disk runs out of space. Specify the percentage

and notification for the watermark levels. Notification can be to generate an SNMP

alarm, a syslog, or both.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# set disk-space-policy watermark-level-1 (percentage) (syslog | snmp |alarm)

user@host# set disk-space-policy watermark-level-2 (percentage) (syslog | snmp |alarm)

user@host# set disk-space-policy watermark-level-3 (percentage) (syslog | snmp |alarm)

Tracing Persistent Storage Operations

To configure tracing operations for local persistent storage:

1. Specify that you want to configure tracing options for charging operations.

[editunified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-options]user@host# edit traceoptions

2. (Optional) Configure the name for the file used for the trace output.

[edit unified-edgegatewaysggsn-pgwMBG1charging local-persistent-storage-optionstraceoptions]

user@host# set file filename

3. (Optional) Configure flags to filter the operations to be logged.




user@host# set flag flag

By default, only important events are logged. You can specify which trace operations

are logged by including specific tracing flags. The following table describes the flags

that you can include.

DescriptionFlag

Trace all operationsall

Trace connection establishment between the RoutingEngine and all session DPCs for CDR file backup

connection

Trace file operations (open, write, close)file-operations

Trace miscellaneous operationsgeneral

Trace file journaling operationsjournaling

Trace mirroring operationsmirror

4. (Optional) Configure the level of tracing.


user@host# set level (all | critical | error | info | notice | verbose | warning)


Configuring the Solid State Disk for Persistent Storage on page 27•




• Configuring S-GW-Specific Charging Parameters

• Configuring S-GW Global Charging Profiles and Selection Order

• Configuring S-GW Charging Traceoptions


Configuring the Solid State Disk for Persistent Storage

You can use the Solid State Disk (SSD) on the Routing Engine for local persistent storage.

You must configure the SSD (part number SSD-CDR-S) before Charging Data Records

(CDRs) can be stored locally on the Routing Engine.



NOTE: If you do not want to format the existing content on the SSD, youmust specify the no-format option when preparing the SSD.

To use the SSD for local persistent storage of CDRs, perform these tasks:

• Initializing the Solid State Disk for Persistent Storage on page 28

• Ejecting the Solid State Disk on page 28

• Installing the Solid State Disk on page 29

Initializing the Solid State Disk for Persistent Storage

If the SSD on the Routing Engine is not plugged in before you start storing CDRs locally

on the Routing Engine, you must initialize the SSD.

To initialize the SSD for local persistent storage when it has not been installed in the

Routing Engine:

1. Power down the Routing Engine by pressing the Online/Offline button or entering the

shutdown -h now command.

2. Install the SSD. For information about installing the SSD, see “Replacing an SSD Drive

on an RE-A-1800 or RE-S-1800” in the Hardware Guide for your MX Series router.

3. Boot the Routing Engine.

4. Prepare the SSD to store CDRs.

user@host> request system storage unified-edgemedia prepare

NOTE: If you do not want to format the existing content on the SSD, youmust specify the no-format option.

5. Enable the SSD to start storing CDRs.

user@host> request system storage unified-edge chargingmedia start

Ejecting the Solid State Disk

To eject the SSD from the Routing Engine:

1. Disable the SSD to close all open files and stop storing CDRs.

user@host> request system storage unified-edge chargingmedia stop

2. Prepare the SSD for removal from the Routing Engine.

user@host> request system storage unified-edgemedia eject

3. Remove the SSD from the Routing Engine. For information about removing the SSD,

see “Replacing an SSD Drive on an RE-A-1800 or RE-S-1800” in the Hardware Guide

for your MX Series router.



Installing the Solid State Disk

If the SSD on the Routing Engine is reinstalled on the Routing Engine after it was initialized,

you must prepare the SSD to store CDRs.

To prepare the SSD for local persistent storage when it has been reinstalled on the

Routing Engine:

1. Install the SSD. For information about installing the SSD, see “Replacing an SSD Drive

on an RE-A-1800 or RE-S-1800” in the Hardware Guide for your MX Series router.

2. Prepare the SSD to store CDRs.

user@host> request system storage unified-edgemedia prepare


3. Enable the SSD to start storing CDRs.


4. Reboot the Routing Engine.


Configuring Persistent Storage on page 25•

• request system storage unified-edge chargingmedia start on page 229

• request system storage unified-edge chargingmedia stop on page 230

• request system storage unified-edgemedia eject on page 231

• request system storage unified-edgemedia prepare on page 232

Configuring Transport Profiles for Offline Charging

A transport profile provides information for transporting offline Charging Data Records

(CDRs) and online messages. Offline CDRs are transported from the charging data

function (CDF) to the charging gateways or to local persistent storage, and online

messages are transported between the Gateway GPRS Support Node (GGSN) Packet

Data Network Gateway (P-GW) and the Online Charging System (OCS). A transport

profile can be associated with one or more charging profiles. You can configure a maximum

of eight transport profiles.



NOTE: The following configuration steps are applicable at both the [edit

unified-edge gateways ggsn-pgw gateway-name charging] and the [edit

unified-edgegatewayssgwgateway-namecharging]hierarchy levels.However,

for clarity, theyarepresentedonlyat the [editunified-edgegatewaysggsn-pgw

gateway-name charging] hierarchy level. Unless explicitly stated otherwise,

the configuration steps canbeusedwith exactly the samesyntax under bothhierarchy levels.

To configure transport profiles for offline charging:

1. Specify the name of the transport profile that you are configuring for the gateway

called MBG1.

[edit unified-edge gateways ggsn-pgwMBG1 charging]user@host# edit transport-profiles profile-name

The transport profile name can contain letters, numbers, and hyphens (-) and can be

up to 128 characters long.

2. Specify a description for the transport profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profiles profile-name]user@host# set description string

3. Specify that you want to configure offline charging in the transport profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profiles profile-name]user@host# edit offline

4. Configure the charging function name for offline charging, which is used to select the

transport profile for offline charging.

If either the primary or secondary charging functions obtained from the policy and

charging rules function (PCRF) match the one configured here, then the transport

profile is selected. If the names provided by the PCRF do not match, then the transport

profile is not selected and the default transport profile is used.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profilestransport-profile1 offline]

user@host# set charging-function-name function-name

5. Configure the transport parameters for offline CDRs.


user@host# edit charging-gateways

a. Configure the order in which the charging gateways are selected. The charging

gateway must be defined as a GTP Prime peer. The highest-priority peer is selected

first as the active charging gateway. When the active charging gateway goes down,

the next higher-priority peer is selected. If all the charging gateways are down and

you have configured local persistent storage, then the CDRs are stored on the

Routing Engine.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profilestransport-profile1 offline charging-gateways]



user@host# set peer-order peer charging-gateway-peer-name

b. Specify the time that the CDF must wait before switching back to a higher-priority

peer from a lower-priority peer that has become the active charging gateway.


user@host# set switch-back-time seconds

The range for the time that the CDF must wait before switching to a higher-priority

peer is 0 through 300 seconds.

c. Specify that the persistent storage order is local (on the Routing Engine). You must

configure the persistent storage order before CDRs can be stored locally on the

Routing Engine.


user@host# set persistent-storage-order local-storage

d. Configure the CDR format version. The charging format implemented in the 3GPP

Release 8 specifications (r8) is the default format version.


user@host# set cdr-release (r7 | r8 | r9 | r99)

NOTE: 3GPP release versions 7, 9, and 99 are only applicable to theGGSN and P-GW (not to the S-GW), while 3GPP release version 8 isapplicable to the GGSN, P-GW, and S-GW.

e. Specify the maximum number of CDRs that can be added to a Data Record Transfer

(DRT) message before it is transmitted. A DRT message containing the CDRs is

transmitted from the CDF to the charging gateway function (CGF) server, when

the cdr-aggregation-limit or the mtu size is reached (whichever comes first).


user@host# set cdr-aggregation-limit value

The range for the CDR aggregation limit is 1 through 16.

f. Configure the maximum transmission unit (MTU), in bytes, of the DRT message.


user@host# setmtu value

The range for the MTU is 300 through 8000 bytes.

6. Specify the maximum number of containers to limit for each CDR.


user@host# set container-limit value

The range for the maximum number of containers for a CDR is 1 through 15.



7. Specify the number of SGSN or S-GW changes that can occur before the CDR is

updated and closed.


user@host# set sgsn-sgw-change-limit value

The range for the maximum number of SGSN or S-GW changes that can occur is 1

through 5.

NOTE: This statement is not applicable to the Serving Gateway (S-GW).


Charging Profiles on page 14•








• offline (Transport Profiles) on page 156

• transport-profiles on page 201

Configuring Charging Trigger Events for Offline Charging

A trigger profile defines the charging events that cause offline Charging Data Record

(CDR) changes and attributes for online charging. For offline CDRs, a trigger profile

determines the events that trigger the creation of a Charging Data Record (CDR), the

addition of a container to a CDR, and the closure of a CDR. You can configure up to a

maximum of 16 trigger profiles.









To configure trigger profiles for offline charging:

1. Specify the name of the trigger profile that you are configuring for the gateway called

MBG1.

[edit unified-edge gateways ggsn-pgwMBG1 charging]user@host# edit trigger-profiles profile-name

The trigger profile name can contain letters, numbers, and hyphens (-) and can be up

to 128 characters long.

2. Specify a description for the trigger profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# set description string

3. Configure the default charging method to be used for subscribers attached to the

trigger profile. The broadband gateway uses the configured default charging method

only when the policy and charging rules function (PCRF) or the static policy and

charging enforcement function (PCEF) policy do not provide a charging method.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# set charging-method (both | none | offline | online)

If you do not configure this statement, then offline charging is enabled by default.

4. Configure offline charging in the trigger profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# edit offline

5. Specify a time limit for closing the CDR. A value of zero (0) disables this trigger.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-nameoffline]

user@host# set time-limit seconds

The range for the activation of the time limit is 600 through 65,535 seconds.

6. Specify the PDP context or bearer information changes that do not trigger charging

data updates. All of these changes trigger a container or CDR closure by default.


user@host# set exclude [bearer-information-change]

You can specify more than one trigger to exclude in a single line. For example, to

exclude the PLMN change and QoS change (in a trigger profile called trigger-profile-1)

from the CCR messages:

[edit unified-edge gateways ggsn-pgwMBG-PGW1 charging trigger-profilestrigger-profile-1 offline]

user@host# set exclude plmn-change qos-change

Table 3 on page 34 describes the bearer information changes that can be ignored for

charging data updates.



Table 3: Bearer Information Changes

DescriptionBearer Information Change

Diameter Credit Control Application (DCCA) events

NOTE: This trigger is applicable only to the GatewayGPRS Support Node (GGSN) or Packet Data NetworkGateway (P-GW).

dcca-events

Mobile Station (MS) time zone changems-timezone-change

Public land mobile network (PLMN) changeplmn-change

Quality-of-service (QoS) changeqos-change

Radio Access Technology (RAT) changerat-change

Serving GPRS Support Node (SGSN) or MobilityManagement Entity (MME) change

NOTE: This trigger is applicable only to the S-GW.

sgsn-mme-change

SGSN or S-GW limit change

NOTE: This trigger is applicable only to the GGSN orP-GW.

sgsn-sgw-change

User location information changeuser-location-change

7. Specify a volume limit trigger for bandwidth, in bytes.


user@host# set volume-limit value

The range for the volume limit is 1 through 4,294,967,295 bytes.

8. Specify the direction for the volume limit trigger. If you specify both, the volume limit

applies to the combined amount of uplink and downlink traffic.


user@host# set volume-limit direction (both | uplink)

9. Configure the list of times to update CDRs when the tariffs change within a day. These

times can be specified in a minimum of 15-minute increments. Specify the tariff time

changes in the format hh:mm, where hh is 00 through 23 (00 is midnight) and mm is

00 through 59. The specified time is local time. You can configure up to a maximum

of 24 tariff time changes.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# set tariff-time-list hh:mm

For example:



[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-nametariff-time-list]

user@host# set tariff-time-list 21:00user@host# set tariff-time-list 07:00


Charging Profiles on page 14•






• offline (Trigger Profiles) on page 157

• trigger-profiles (GGSN or P-GW) on page 206

• trigger-profiles (Serving Gateway)

Configuring CDR Attributes

A Charging Data Record (CDR) profile defines the attributes in each CDR.

To configure CDR profiles:







1. Specify the name of the CDR profile that you are configuring for the gateway called

MBG1.

[edit unified-edge gateways ggsn-pgwMBG1 charging]user@host# edit cdr-profiles profile-name

The CDR profile name can contain letters, numbers, and hyphens (-) and can be up


2. Specify a description for the profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging cdr-profiles profile-name]user@host# set description string

3. Enable reduced partial CDR (RPC) generation.

[edit unified-edge gateways ggsn-pgwMBG1 charging cdr-profiles profile-name]user@host# set enable-reduced-partial-cdrs



4. Set optional attributes to exclude from the CDR. You can specify the excluded

attributes so that you can manage the size of the CDR. By default, all attributes are

included in the CDR.

[edit unified-edge gateways ggsn-pgwMBG1 charging cdr-profiles profile-name]user@host# set exclude-attributes [attribute]

Table 4 on page 36 describes the attributes that can be excluded from CDRs.

Table 4: Attribute Exclusions

Information in CDRsAttribute

Access point name (APN) network identifierapn-ni

APN selection modeapn-selection-mode

Charging characteristic selection modecc-selection-mode

Dynamic Packet Data Protocol (PDP) address indicationdynamic-address

List of service datalist-of-service-data

List of traffic volumeslist-of-traffic-volumes

Local record sequence numberlrsn

Mobile station (MS) time zonems-time-zone

Network initiation flagnetwork-initiation

Node identifiernode-id

Packet data network (PDN) connection IDpdn-connection-id

PDP or PDN typepdppdn-type

P-GW public land mobile network (PLMN) identifier fieldpgw-plmn-identifier

PS Furnish Info (where PS stands for packet switched)ps-furnish-info

Radio Access Technology (RAT) typerat-type

Record sequence numberrecord-sequence-number

Served International Mobile Equipment Identity andSoftware Version Number (IMEISV)

served-imeisv

Served mobile station ISDN (MSISDN)served-msisdn

Served PDP context or IP-CAN bearer addressserved-pdppdn-address



Table 4: Attribute Exclusions (continued)

Information in CDRsAttribute

Served PDP context or IP-CAN bearer address extensionserved-pdp-address-extension

Serving node PLMN identifier fieldserving-node-plmn-identifier

Time when session established; added to first CDRstart-time

Time when session terminated; added to last CDRstop-time

User location informationuser-location-information

5. Specify the format of the node identifier (ID) in the CDR. The node identifier indicates

the node that generated the CDR.

[edit unified-edge gateways ggsn-pgwMBG1 charging cdr-profiles profile-name]user@host# set node-id hostname

NOTE:• The node identifier can be configured as one of the following:

• hostname—Hostname of the node that generated the CDR.

• hostname-spic—Hostname of the node that generated the CDR andthe ID of the services PIC on which the CDRwas triggered, delimitedby a colon (:).

• ipaddress-spic—IP address of the node that generated the CDR andthe ID of the services PIC on which the CDRwas triggered, delimitedby a colon (:).

• If you do not include the node-id statement, then the IP address of the

node generating the CDR and the ID of the services PIC on which theCDRwas triggered, with a colon (:) as a delimiter, are used as the nodeidentifier.

6. Specify that the broadband gateway includes the requested access point name (APN)

in the CDRs of subscribers attached to the CDR profile. Therefore, when the APN type

is virtual, the broadband gateway includes the requested or virtual APN in the CDRs.

[edit unified-edge gateways ggsn-pgwMBG1 charging cdr-profiles profile-name]user@host# set report-requested-apn

NOTE: If you do not include the report-requested-apn statement, then, by

default, the broadband gateway includes only the real APN in the CDR.(For virtual APNs, the real APN to which the virtual APN is mapped isincluded in the CDR.)




cdr-profiles on page 92•








Configuring Charging Profiles

A charging profile defines the charging behavior applied to a mobile subscriber. The

charging profile includes a transport profile, a Charging Data Record (CDR) profile, one

or more trigger profiles, and other default service-aware charging information.







To configure charging profiles:

1. Specify the name of the charging profile that you are configuring for the gateway

called MBG1.

[edit unified-edge gateways ggsn-pgwMBG1 charging]user@host# edit charging-profiles profile-name

The charging profile name can contain letters, numbers, and hyphens (-) and can be


2. Specify a profile identifier that is matched against the GPRS tunneling protocol (GTP)

charging characteristic or authentication, authorization, and accounting (AAA) charging

profile number. The profile identifier must be specified and it must be a unique value

across all charging profiles defined for a gateway.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set profile-id profile-id

3. Specify the transport profile referenced by this charging profile. The transport profile

must be specified and must be previously configured on the broadband gateway.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set transport-profile profile-name



4. (Optional) Specify a description for the profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set description string

5. (Optional) Specify the default rating group, which is used for charging service data

containers. This configuration is not applicable for the S-GW.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set default-rating-group integer

If no default rating group is specified, then RG0 is sent in the Credit Control Request

(CCR) message.

6. (Optional) Specify the default service identifier for the service or the service

component, which is used for charging service data containers. This configuration is

not applicable for the S-GW.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set default-service-id integer

If no default service identifier is specified, thenService ID0 is sent in the Credit Control

Request (CCR) message.

7. (Optional) Specify the CDR profile referenced by this charging profile. The CDR profile

must be previously configured on the gateway.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set cdr-profile profile-name

8. (Optional) Specify one or more trigger profiles to be referenced by this charging profile.

The trigger profiles must be previously configured on the gateway.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-name]user@host# set trigger-profile profile-name

9. (Optional) Specify one or more rating group identifiers that should be associated with

a trigger profile. The rating group is used to select the trigger profile to be associated

with a charging profile. If the rating group identifier received by the broadband gateway

matches the rating group identifier configured here, then the trigger profile with which

the rating group identifier is associated is linked to the charging profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging charging-profiles profile-nametrigger-profile profile-name]

user@host# set rating-group [value]







• charging-profiles on page 106




Configuring Charging Profiles for APNs

You can configure charging profiles that apply to access point names (APNs) that are

used for the default profile, home subscribers, roaming subscribers, and visiting

subscribers.

To configure charging profiles for APNs:

1. Specify that you want to configure charging profiles for a particular APN.

[edit]user@host#editunified-edgegatewaysggsn-pgwMBG1apn-servicesapnsapn-namecharging

2. Specify the name of the default charging profile. The charging profile must be defined.

[edit unified-edge gateways ggsn-pgwMBG1 apn-services apns apn-name charging]user@host# set default-profile profile-name

3. Specify the name of the charging profile for home subscribers roaming in other public

land mobile networks (PLMNs). The charging profile must be defined.

[edit unified-edge gateways ggsn-pgwMBG1 apn-services apns apn-name charging]user@host# set home-profile profile-name

4. Specify the name of the charging profile for roaming subscribers between PLMNs.

The charging profile must be defined.

[edit unified-edge gateways ggsn-pgwMBG1 apn-services apns apn-name charging]user@host# set roamer-profile profile-name

5. Specify the name of the charging profile for visiting subscribers from other PLMNs.

The charging profile must be defined.

[edit unified-edge gateways ggsn-pgwMBG1 apn-services apns apn-name charging]user@host# set visitor-profile profile-name

6. Specify the profile selection order. You can order the selections by the charging profile

sent by the RADIUS server (radius), the charging profile sent by the SGSN or Serving

Gateway (serving), or the locally configured charging profile (static).

[edit unified-edge gateways ggsn-pgwMBG1 apn-services apns apn-name charging]user@host# set profile-selection-order [(serving | radius | static)]










Configuring Transport Profiles for Online Charging

A transport profile provides information for transporting offline Charging Data Records

(CDRs) and online messages. Offline CDRs are transported from the charging data

function (CDF) to the charging gateways or to local persistent storage, and online

messages are transported between the Gateway GPRS Support Node (GGSN) Packet

Data Network Gateway (P-GW) and the Online Charging System (OCS). A transport

profile can be associated with one or more charging profiles. You can configure a maximum

of eight transport profiles.

To configure transport profiles for online charging:

1. Specify the name of the transport profile that you are configuring for the gateway

called MBG1.

[edit unified-edge gateways ggsn-pgwMBG1 charging]user@host# edit transport-profiles profile-name

The transport profile name can contain letters, numbers, and hyphens (-) and can be


2. Specify a description for the transport profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profiles profile-name]user@host# set description string

3. Specify that you want to configure online charging in the transport profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profiles profile-name]user@host# edit online

4. (Optional) Specify that the broadband gateway reports both active and inactive rating

groups to the OCS on bearer termination.

[edit unified-edge gateways ggsn-pgwMBG1 charging transport-profilestransport-profile1 online]

user@host# set all-rgs-on-termination

If you do not include the all-rgs-on-termination statement, then, by default, the

broadband gateway reports only the active rating groups to the OCS on bearer

termination.

5. (Optional) Configure the charging function names for online charging, which are used

to select the transport profile for online charging.

If either the primary or secondary charging functions obtained from the policy and

charging rules function (PCRF) match the one configured here, then the transport

profile is selected. If the names provided by the PCRF do not match, then the transport

profile is not selected and the default transport profile is used.


user@host# set charging-function-name function-name

6. Associate a previously configured Diameter Gy profile with the transport profile. The

Diameter Gy profile configuration associated with the transport profile determines

the OCS with which the GGSN or P-GW interacts.



The Diameter Gy profile must be specified and must be previously configured at the

[edit unified-edge diameter-profiles gy-profile] hierarchy level.


user@host# set diameter-profile diameter-gy-profile-name

7. (Optional) Specify that no Multiple Services Credit Control (MSCC) attribute-value

pairs (AVPs) are included in the Credit Control Request-Terminate (CCR-T) messages

sent from the broadband gateway to the OCS.


user@host# set no-mscc-in-ccrt

If you include the no-mscc-in-ccrt statement, the broadband gateway first sends the

MSCC AVPs in the CCR-Update (CCR-U) message (to report usage), and then sends

the CCR-T message to the OCS. If you do not include this statement, then the

broadband gateway sends the MSCC AVPs in the CCR-T messages (to report usage).

8. (Optional) Specify that the broadband gateway requests quota (for a rating group)

from the OCS only on receipt of the first packet matching that rating group.


user@host# set quota-request-on-first-packet

If you do not include the quota-request-on-first-packet statement, then, by default,

broadband gateway requests quota from the OCS when the rating group is created.

9. (Optional) Specify that the broadband gateway sends CCR-Initial (CCR-I) messages

to the OCS only on receipt of the first packet for any rating group of the bearer.


user@host# set send-ccri-on-first-packet

If you do not include the send-ccri-on-first-packet statement, then the broadband

gateway sends the CCR-I messages to the OCS to authorize the bearer during bearer

establishment. In addition, if thequota-request-on-first-packetstatement is configured,

the broadband gateway sends the CCR-I messages without any MSCC AVPs included.

10. (Optional) Configure the service context identifier (ID) attribute-value pair (AVP).

The broadband gateway sends this AVP in all Credit Control Request (CCR) messages

to the OCS.


user@host# set service-context-id service-context-id-avp

The service context ID can be a maximum of 100 characters. If you do not configure

the service context ID, then the default service context ID ([email protected]) is sent

in CCR messages.

11. (Optional) Configure whether online charging sessions should fail over to an alternate

server or not, when failure occurs during an ongoing credit control session. The alternate

server is selected based on the configuration in the Diameter profile that is associated

with the transport profile.




user@host# set session-failover-not-supported

If you do not include the session-failover-not-supported statement, the failover of

online charging sessions to an alternative server is enabled by default.

12. (Optional) Specify that only one MSCC AVP is included in the CCR messages sent

from the broadband gateway to the OCS.


user@host# set single-mscc

If you do not include the single-mscc statement, then, by default, the broadband

gateway includes one or more MSCC AVPs in CCR messages.

13. (Optional) Specify the time (in seconds) that the broadband gateway waits for a

response from the OCS before timing out.


user@host# set tx-timeout timeout

The range for the time that the broadband gateway waits for a response is 0 through

300 seconds.


Configuring Online Charging on page 22•



• online (Transport Profiles) on page 158


Configuring Charging Trigger Events for Online Charging

A trigger profile defines the charging events that cause offline Charging Data Record

(CDR) changes, and the attributes for online charging. You can configure up to a maximum

of 16 trigger profiles.

NOTE: The configuration of the trigger profile for online charging is optional.

You must perform the following procedure before you can configure online charging

trigger attributes.

To configure the trigger profile for online charging:

1. Specify the name of the trigger profile that you are configuring for the gateway called

MBG1.

[edit unified-edge gateways ggsn-pgwMBG1 charging]user@host# edit trigger-profiles profile-name



The trigger profile name can contain letters, numbers, and hyphens (-) and can be up


2. (Optional) Specify a description for the trigger profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# set description string

3. (Optional) Configure the default charging method to be used for subscribers attached

to the trigger profile. The broadband gateway uses the configured default charging

method only when the policy and charging rules function (PCRF) or the static policy

and charging enforcement function (PCEF) policy does not provide a charging method.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# set charging-method (both | none | offline | online)

If you do not configure this statement, then offline charging is enabled by default.

4. Configure online charging in the trigger profile.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-name]user@host# edit online

To configure trigger attributes for online charging, you configure the credit control failure

handling parameters and miscellaneous attributes such as the measurement method,

quota threshold, reporting level, and so on. This topic includes the following tasks:

• Configuring Credit Control Failure Handling Parameters on page 44

• Configuring Miscellaneous Online Charging Trigger Events on page 47

Configuring Credit Control Failure Handling Parameters

Credit control failure handling parameters determine what the broadband gateway does

during credit control failure. If the Online Charging System (OCS) responds with a result

code that is not successful, then actions configured for specific result codes are performed.

If the OCS does not respond to Credit Control Request (CCR) messages, then other

configured actions are performed.

To configure credit control failure handling parameters:

1. Specify that the broadband gateway blocks traffic for a rating group pending

reauthorization when the quota is exhausted.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-nameonline cc-failure-handling]

user@host# set block-traffic-pending-reauth-no-quota

2. Configure the actions to be carried out by the broadband gateway when the initial

Credit Control Request fails.

NOTE: You can configure only one of the following actions.

a. Specify that offline charging is used to charge subscribers. In this case, online

charging is disabled for the subscriber. Optionally, you can also specify that the

subscriber session is extended until the grace quota elapses. After the grace quota



elapses, the session is terminated and the subscriber is charged using offline

charging.


user@host# set initial-request convert-to-offlineuser@host# set initial-request convert-to-offline grant-grace-quota

b. Optionally, specify that online charging is disabled, and that offline charging, if

enabled, is used to charge subscribers. If offline charging is not enabled, then no

charging is applied to the subscriber.


user@host# set initial-request disable-online-charging

c. Optionally, specify that the subscriber session is extended until the grace quota

elapses. After the grace quota elapses, the session is terminated and the subscriber

is charged using offline charging.


user@host# set initial-request grant-grace-quota

3. Specify that the broadband gateway overrides the credit control failure handling

parameters received from the OCS and uses the parameters configured locally on

the gateway.


user@host# set override

4. Configure the actions to be performed based on the Diameter Result-Code

attribute-value pair (AVP) received from the OCS:

a. Specify that the rating group is blacklisted when the OCS sends a Diameter

Authorization Rejected message to the gateway. Optionally, you can also specify

that the gateway retries with the OCS after the configured time elapses.


user@host# set result-code-based-action authorization-rejected blacklistuser@host#set result-code-based-actioncredit-limit-reachedblacklist retry-timer

For example, to configure the gateway to blacklist the rating group and retry with

the OCS after 300 seconds (5 minutes):


user@host# set result-code-based-action credit-limit-reached blacklist 300

b. Specify that, if the result code is Diameter Credit Control Not Applicable, the

gateway disables online charging and enables offline charging. Optionally, you can

also specify that the subscriber session is extended until the grace quota elapses.

After the grace quota elapses, the session is terminated and the subscriber is

charged using offline charging.




user@host# set result-code-based-action credit-control-not-applicableconvert-to-offline

user@host# set result-code-based-action credit-control-not-applicableconvert-to-offline grant-grace-quota

c. Specify that the rating group is blacklisted when the OCS sends a Diameter Credit

Limit Reached message to the gateway. Optionally, you can also specify that the

gateway retries with the OCS after the configured time elapses.


user@host# set result-code-based-action credit-limit-reached blacklistuser@host#set result-code-based-actioncredit-limit-reachedblacklist retry-timer

d. Specify the actions to be carried by the gateway when the OCS sends a Diameter

End User Service Denied message.




subscriber session is extended until the grace quota elapses. After the grace

quota elapses, the session is terminated and the subscriber is charged using

offline charging.

[editunified-edgegatewaysggsn-pgwMBG1chargingtrigger-profilesprofile-nameonline cc-failure-handling]

user@host# set end-user-service-denied convert-to-offlineuser@host# set end-user-service-denied convert-to-offline grant-grace-quota


enabled, is used to charge subscribers. If offline charging is not enabled, then

no charging is applied to the subscriber.


user@host# set end-user-service-denied disable-online-charging

e. Specify the actions to be carried out by the gateway when the OCS sends a

Diameter User Unknown message.




subscriber session is extended until the grace quota elapses. After the grace

quota elapses, the session is terminated and the subscriber is charged using

offline charging.


user@host# set user-unknown convert-to-offlineuser@host# set user-unknown convert-to-offline grant-grace-quota




enabled, is used to charge subscribers. If offline charging is not enabled, then

no charging is applied to the subscriber.


user@host# set user-unknown disable-online-charging

5. Configure the actions to be carried out by the broadband gateway when the Credit

Control Request-Update fails.




subscriber session is extended until the grace quota elapses. After the grace quota

elapses, the session is terminated and the subscriber is charged using offline

charging.


user@host# set update-request convert-to-offlineuser@host# set update-request convert-to-offline grant-grace-quota


enabled, is used to charge subscribers. If offline charging is not enabled, then no

charging is applied to the subscriber.


user@host# set update-request disable-online-charging

c. Optionally, specify that the subscriber session is extended until the grace quota

elapses. After the grace quota elapses, the session is terminated and the subscriber

is charged using offline charging.


user@host# set update-request grant-grace-quota

ConfiguringMiscellaneous Online Charging Trigger Events

As a part of the online trigger profile configuration, you can configure the following

miscellaneous attributes:

• Grace quota to be granted in case of credit control failure

• Default measurement method to be used

• Quota holding time

• Quota threshold

• Quota validity time



• Reporting level

• Attributes (including quotas) for the requested service unit

To configure the miscellaneous attributes:

1. Configure the grace quota. The broadband gateway allocates the grace quota in case

of credit control failure; for example, if there is no reply from the OCS to the CCR

message.

a. Configure the volume quota (in bytes) for both uplink and downlink directions.

[edit unified-edge gateways ggsn-pgwMBG1 charging trigger-profiles profile-nameonline]

user@host# set grant-quota cc-octet-both volume-quota-both

The range for the volume quota for both the uplink and downlink directions is

1,048,576 through 9,223,372,036,854,775,807 bytes.

b. Configure the volume quota (in bytes) for the downlink direction.


user@host# set grant-quota cc-octet-downlink volume-quota-dl

The range for the volume quota for in the downlink direction is 1,048,576 through

9,223,372,036,854,775,807 bytes.

c. Configure the volume quota (in bytes) for the uplink direction.


user@host# set grant-quota cc-octet-uplink volume-quota-ul


9,223,372,036,854,775,807 bytes.

d. Configure the time quota (in seconds).


user@host# set grant-quota cc-time time-quota

The range for the time quota is 300 through 4,294,967,294 seconds.

2. Specify the default measurement method to be used. This specified measurement

method is used by the gateway to include the Requested-Service-Unit (RSU) AVP in

the CCR message if the policy and charging enforcement function (PCEF) does not

include the RSU AVP in the CCR message.


user@host# setmeasurement-method (none | time | volume | volume-and-time)

If you specify time as the default measurement method, then the gateway includes

the CC Time AVP in the RSU based on configured time (cc-time statement). If you

specify volume as the default measurement method, the gateway includes the CC

Octet Both, CC Octet Downlink, and CC Octet Uplink AVPs in the RSU based on

configured values (cc-octet-both, cc-octet-downlink, and cc-octet-uplink statements,



respectively). If you specify volume-and-time, then the gateway includes both time

and volume AVPs in the RSU. If you specify none, then the gateway sends an empty

RSU.

3. Configure the quota holding time, in seconds. The configured quota holding time is

used if the OCS does not provide quota validity time in the Quota-Holding-Time AVP

in the Credit Control Answer (CCA) message.


user@host# set quota-holding-time time-in-seconds

The range for the quota holding time is 300 through 864,000 seconds.

NOTE: The quota holding time provided by the OCS takes precedenceover the one configured (locally) on the broadband gateway. A quotaholding time of zero indicates that the quota holdingmechanism shouldnot be used.

If you do not include the quota-holding-time statement, the quota holding

time provided by the OCS is used. If no quota holding time is provided bythe OCS, then the quota holdingmechanism is not used.

4. Configure the threshold for the quota received from the OCS:

a. Specify the quota threshold as a percentage of the total quota allocated. The

broadband gateway uses the quota threshold to determine when to report the

used quota to and request more quota from the OCS. For example, if the OCS

provides 100 KB of quota and if the quota threshold is 80 percent, then the gateway

sends the OCS a Credit Control Request-Update message with the used quota,

when the quota used is 80 KB.


user@host# set quota-threshold threshold

The range for the quota threshold is 5 through 95 percent.

b. Optionally, specify that the configured quota threshold overrides the one provided

by the OCS.


user@host# set quota-threshold override

5. Configure the quota validity time, in seconds. The configured quota validity time is

used if the OCS does not provide quota validity time in the Validity-Time AVP in the

Credit Control Answer (CCA) message.


user@host# set quota-validity-time time-in-seconds

The range for the quota validity time is 30 through 864,000 seconds.



6. Configure the default reporting level for the reports from the gateway to the offline

charging gateway and the OCS:

a. Specify the reporting level. You can specify whether the gateway reports at the

rating group level or at the service identifier level (within a rating group).


user@host# set reporting-level (rating-group | service-identifier)

b. Optionally, specify that the configured reporting level overrides the one provided

by the PCRF.


user@host# set reporting-level override

7. Configure the attributes for the requested service unit. (The broadband gateway uses

the configured quotas in the RSU AVP in the CCR message to the OCS.)

a. Specify that the broadband gateway always includes the RSU AVP in CCR messages

to the OCS.


user@host# set requested-service-unit always-include

NOTE: By default, the broadband gateway includes the RSU AVP inCCRmessages sent to the OCS requesting for quota, except in thefollowing cases:

• If thequotaholding timehaselapsed, thebroadbandgateway returnsthe quota to the OCS and does not request for more quota.

• If the send-ccri-on-first-packet statementhasnotbeen included, and

if the quota-request-on-first-packet statement is configured, the

broadbandgatewaysendsaCCR-Imessage to theOCS, toauthorizethe bearer, without the RSU AVP included.

b. Specify that the broadband gateway includes the RSU AVP in the CCR messages

to the OCS, when the usage is reported for the reason of quota holding time.


user@host# set requested-service-unit include-quota-holding-time

NOTE:• By default, the gateway does not include the RSU AVP in CCRmessages to the OCS, when the reporting reason is quota holdingtime.

• If you configure both the always-include and

include-quota-validity-timestatements, thealways-includestatement

takes precedence.



c. Configure the volume quota (in bytes) for both uplink and downlink directions.


user@host# set requested-service-unit cc-octet-both volume-quota-both

The range for the volume quota for both the uplink and downlink directions is

1,048,576 through 9,223,372,036,854,775,807 bytes.

d. Configure the volume quota (in bytes) for the downlink direction.


user@host# set requested-service-unit cc-octet-downlink volume-quota-dl


9,223,372,036,854,775,807 bytes.

e. Configure the volume quota (in bytes) for the uplink direction.


user@host# set requested-service-unit cc-octet-uplink volume-quota-ul


9,223,372,036,854,775,807 bytes.

f. Configure the time quota (in seconds).


user@host# set requested-service-unit cc-time time-quota

The range for the time quota is 300 through 4,294,967,294 seconds.

g. Specify that the broadband gateway includes the Requested-Service-Unit AVP in

the CCR messages to the OCS, when the usage is reported for the reason of quota

holding time.


user@host# set requested-service-unit include-quota-holding-time

NOTE: By default, the gateway does not include theRequested-Service-Unit AVP in CCRmessages to the OCS, when thereporting reason is quota holding time.


Configuring Charging Profiles on page 38•


• online (Trigger Profiles) on page 159






Configuring Service Sets and Service Filters for Advice of Charge


applicable charges before the subscriber uses a service, or when the subscriber’s quota

is exhausted. The service set and services filter names are variables, but must conform

to usual Junos OS naming rules.

Before you begin configuring a service set and service filter for AoC and Top-Up on a

broadband gateway, you should have done the following:

• Configured the chassis of the broadband gateway

• Configured the interfaces of the broadband gateway

• Configured a zero-rated or unlimited rating group to allow the “redirect-URL” traffic

towards the AoC or Top-up server.

To configure the AoC service set and service filter and apply them to the mobile interface

of the APN:

1. Configure a policy and charging enforcement function (PCEF) profile. (The name

aoc_pcef is a variable.)

[edit services]user@mbg# set pcef profile aoc_pcef

2. Configure the service set for AoC. (The name aoc_service_set is a variable.)

[edit services service-set aoc_service_set]user@mbg# set tcp-mss 1300user@mbg# set service-set-options subscriber-awareness

3. Reference the configured PCEF profile in a service set. (The nameprofile1 is a variable.)

[edit services service-set aoc_service_set]user@mbg# set application-identification-profile profile1user@mbg# set pcef-profile aoc_pcefuser@mbg# set interface-service service-interface ams0.1user@mbg#set interface-service load-balancingoptionshask-keys resource-triggered

NOTE: The PCEF profile referenced is the PCEF profile configured at the[edit services pcef] hierarchy level.

4. Configure the AoC service filter. There is only one term in this filter that selects packets

for AoC and Top-Up servicing. (The term aoc_filter is a variable.)

[edit firewalls family inet service-filter aoc_filter term t1]user@mbg# set from redirect-reason [ dpi aoc ]user@mbg# set then service

NOTE: Youmust include deep packet inspection (DPI) as well as AoC asthe redirect reason for this feature to function properly.



5. Apply the previously configured AoC service set and service filter for input and output

on the mobile interface (mif.0) of the APN.

[edit interfacesmif unit 0 family inet]user@mbg# set service input service-set aoc_service_set service-filter aoc_filteruser@mbg# set service output service-set aoc_service_set service-filter aoc_filter

NOTE: The service set referencedmust be configured at the [edit services

service-set] hierarchy level and the service filter referencedmust be

configured at the [edit firewall family inet service-filter] hierarchy level.




• Configuring Policy and Charging Control Action Profiles

• Configuring Application-Aware Policy and Charging Control Rules

• Example: Configuring Policy and Charging Enforcement Function with

Application-Aware Policy and Charging Control Rules



CHAPTER 4

Configuration Examples


Example: Configuring Online Charging

This example shows how to configure the MobileNext Broadband Gateway so that

charging is carried out online in real time. By default, the broadband gateway records no

charging information. The broadband gateway conveys online charging information to

the Online Charging Server (OCS) over the Gy interface using the Diameter protocol.

• Requirements on page 55

• Overview on page 55

• Configuration on page 56

• Verification on page 60

• Troubleshooting on page 61

Requirements

This example uses the following hardware and software components:

• A supported MX Series chassis configured with supported line cards and a services

PIC.

• A supported and properly installed version of 64-bit Junos OS and the jmobile software

package.

• Correct configuration as a Packet Data Network Gateway (P-GW) with corresponding

interfaces.

Before you configure online charging, be sure you have:

• Configured the broadband gateway correctly.

• Configured GTP and Diameter correctly.

Overview

Online charging is part of a complete broadband gateway configuration, including policy

and charging rules, quality-of-service (QOS) determination, and overall charging

considerations. Figure 4 on page 56 shows the overall architecture for the gateway


components and the functional groupings for policy and charging. The Gy interface

connects the P-GW and OCS.

Figure 4: Architecture for Online Charging


OCSOnline ChargingServer


AFApplication function

Subscription ProfileRepository (SPR)

PDN Gateway(PCEF andcharging entity)

Serving Gateway(S-GW) g0

4079

4

Ga

GyGx

S5/S8

S5/S8

Ga

Gy

Gx

You can configure both online and offline charging. This example configures only online

charging, including the Gy interface.

Topology

The topology for this online charging example consists of mobile network nodes and the

interfaces connecting them to each other. The key device is the P-GW, which incorporates

the charging entity to handle charging information, and the policy and charging

enforcement functions (PCEF) to determine how the charging and policy information is

handled. The P-GW communicates with the OCS over the Gy interface, which is the main

interface configured for online charging.

Configuration

To configure online charging, perform these tasks:


• Results on page 59



CLI QuickConfiguration

set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profiles trigger-profile-1tariff-time-list 17:00:00




set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profiles trigger-profile-1online quota-threshold 80

set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profiles trigger-profile-1online grant-quota cc-octet-both 5000000

set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profiles trigger-profile-1online requested-service-unit cc-time 1800

set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profiles trigger-profile-1online requested-service-unit cc-octet-both 1048576

set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profiles trigger-profile-1online cc-failure-handling update-request convert-to-offline

setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profiles transport-profile-1online tx-timeout 5

setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profiles transport-profile-1online session-failover-not-supported

setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profiles transport-profile-1online diameter-profile gy-profile-1

setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profiles transport-profile-1online send-ccri-on-first-packet

setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profiles transport-profile-1online set-quota-request-on-first-packet

set unified-edge gateways ggsn-pgwmbg-1 charging charging-profilesdefault-charging-profile profile-id 232

set unified-edge gateways ggsn-pgwmbg-1 charging charging-profilesdefault-charging-profile transport-profile transport-profile-1

set unified-edge gateways ggsn-pgwmbg-1 charging charging-profilesdefault-charging-profile trigger-profile trigger-profile-1 rating-group 1000

Configuring Online Charging

Step-by-StepProcedure

To configure online charging on the broadband gateway:

NOTE: You can configure both offline and online charging parameters andprofiles.Thisexampleonlyconfiguresonlinechargingparametersandprofiles.

1. Enable online charging at the PCEF level if using static policies.

[edit]user@mbg# set unified-edge gateways ggsn-pgwmbg-1 pcef static-policiespcc-rules pcc-rule-1 charging charging-method online


Chapter 4: Configuration Examples

NOTE: You can also set the charging-method to online-offline to enable

online charging. If you do not include this statement in the rule, thedefault is to apply the bearer-level chargingmethod, which could benone (no charge).

2. Enable online charging at the bearer (trigger profile) level if not using charging in a

static policy.

[edit]user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 charging-method online

NOTE: This establishes the default chargingmethod if the PCEF staticpolicy does not provide amethod.

3. Configure trigger profiles for online charging parameters.

[edit]user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 tariff-time-list 17:00:00

user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 tariff-time-list 18:00:00



user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 online quote-threshold 80

user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 online grant-quota cc-octet-both 5000000

user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 online quote-threshold 80

user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 online requested-service-unit cc-time 1800

user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 online requested-service-unit cc-octet-both 1048576

user@mbg# set unified-edge gateways ggsn-pgwmbg-1 charging trigger-profilestrigger-profile-1 online cc-failure-handling update-request convert-to-offline

NOTE: You configure a list of local tariff times (in hh, hh:mm, orhh:mm:ss format)atwhichthetariff changesandChargingDataRecords(CDRs)aregenerated to reflect thechange in tariff.Makesure that thereis a difference of at least 15minutes betweenmultiple values. Theseconds values are ignored. You can configure amaximumof 24 values.The local time zone’s Universal Metric Time (UMT) offset is added tothe time configured.



4. Configure transport profiles for online charging parameters.

[edit]user@mbg#setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profilestransport-profile-1 online tx-timeout 5

user@mbg#setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profilestransport-profile-1 online session-failure-not-supported

user@mbg#setunified-edgegatewaysggsn-pgwmbg-1chargingtransport-profilestransport-profile-1 online diameter-profile gy-profile-1

set unified-edge gateways ggsn-pgwmbg-1 charging transport-profilestransport-profile-1 online send-ccri-on-first-packet

set unified-edge gateways ggsn-pgwmbg-1 charging transport-profilestransport-profile-1 online set-quota-request-on-first-packet

NOTE: The Diameter profile must be properly configured under theDiameter configuration.

5. Configure charging profiles for online charging parameters.

[edit]user@mbg# setunified-edgegatewaysggsn-pgwmbg-1 chargingcharging-profilesdefault-charging-profile profile-id 232

user@mbg# setunified-edgegatewaysggsn-pgwmbg-1 chargingcharging-profilesdefault-charging-profile transport-profile transport-profile-1

user@mbg# setunified-edgegatewaysggsn-pgwmbg-1 chargingcharging-profilesdefault-charging-profile trigger-profile trigger-profile-1 rating-groups 1000

Results

From configuration mode, confirm your configuration by entering the show command at

the correct hierarchy level. If the output does not display the intended configuration,

repeat the configuration instructions in this example to correct it.

For brevity, this show command output includes only the configuration that is relevant

to this example.

[edit unified-edge gateways ggsn-pgwmbg-1 charging]trigger-profiles {trigger-profile-1 {tariff-time-list {"17:00:00 -0700";"18:00:00 -0700";"20:05:00 -0700";"22:05:00 -0700";

}online {quota-threshold 80;grant-quota {cc-octet-both 5000000;

}requested-service-unit {cc-time 1800;cc-octet-both 1048576;



}cc-failure-handling {update-request {convert-to-offline;

}}

}}

}transport-profiles {transport-profile-1 {online {tx-timeout 5;session-failover-not-supported;diameter-profile gy-profile-1;quota-request-on-first-packet;send-ccri-on-first-packet;

}}

}charging-profiles {default-cp {profile-id 232;transport-profile transport-profile-1;trigger-profile trigger-profile-1 {rating-group 1000;

}}

}

Verification

Verifying Online Charging Peer Status Configuration

Purpose Verify that the online charging peer is successfully communicating with the broadband

gateway.

Action From operational mode, enter the showunified-edgeggsn-pgwdiameterpeerstatusdetail

command.

user@mgb-1# show unified-edge ggsn-pgw diameter peer statusDiameter Peer Status Name : p1 FPC/PIC : 3/0 State : I-Open State Duration : 00:01:31 Watchdog State : okay Origin Host : mydomain.net Origin Realm : mydomain.net Peer Address : 10.6.1.2 Peer port : 3868 Source Address : 10.6.88.1 Source Port : 30736



Meaning If the output shows that the state of the peer is “I-Open,” then the connection to the OCS

is established.

Verifying Online Charging Peer Statistics

Purpose Verify that the online charging peer is successfully sending to and receiving from the

broadband gateway.

Action From operational mode, enter the showunified-edgeggsn-pgwdiameterdcca-gystatistics

detail command.

user@mgb-1# show unified-edge ggsn-pgw diameter dcca-gy statistics detail

Gateway: PGW FPC/PIC: 3/0 Total Sessions: 1 Total Sessions Terminated: 0 Internal Errors: 0

Credit Control Initial Update Terminate Total

-----------------------------------------------------------------------------

Requests Transmitted 1 0 1 2 Request Timeouts 0 0 0 0 Request Tx Timeouts 0 0 0 0 Request Discarded 0 0 0 0 Answers Received 1 0 1 2

Answers Dropped 0 0 0 0 Answers Parse Errors 0 0 0 0 Answers with Invalid AVP(s) 0 0 0 0

Server Requests Re-Auth Abort Session Total ------------------------------------------------------------------------ Requests Received 0 1 1 Requests Dropped 0 0 0 Requests Parse Errors 0 0 0 Requests with Invalid AVP(s) 0 0 0 Answers Transmitted 0 1 1

Meaning If the output shows that the number of requests transmitted and answers received is

non-zero, then the connection to the OCS is functioning properly.

Troubleshooting

To troubleshoot online charging configuration, perform these tasks:

• Troubleshooting Rating Group and Volume Quota on page 61

Troubleshooting Rating Group and VolumeQuota

Problem The rating group and quota granted by the OCS is not as expected for the subscriber.



Solution To display the rating group for online charging and the quota for the subscriber, perform

the following:

1. From operational mode, enter the show unified-edge ggsn-pgw subscribers extensive

command.

user@mgb-1# show unified-edge ggsn-pgw subscribers extensiveGateway: PGW

Subscriber Information: UE: IMSI: 223456789012369 IMEI: 3568710407092001 MSISDN: 62818881442 Time Zone: GMT DST: None RAT Type: UTRAN User Location Information: MCC: None MNC: None LAC: 0x0 CI: 0x0 SAC: 0x0 RAC: 0x0 TAC: 0x0 ECI: 0x0 PDN Session: APN name: jnpr-gxgy

IPv4 Address: 30.30.0.1 IPv6 Address: None GTP Version: 1 Address Assignment: Local

Local Control IP: 200.6.88.1 Remote Control IP: 70.70.70.4 Local Control TEID: 0x12000000 Remote Control TEID: 0x1 Selection mode: MS or network provided APN, subscription verified

Session PIC: 0 /0 (FPC/PIC) PFE: 2 /0 (FPC/PIC) Service PIC: None/None (FPC/PIC) Session State: Established Session Duration: 8 Roaming Status: Visitor Serving network: MCC: 123 MNC: 456 Direct Tunnel: Disabled HW Rule set Identifier: 0 Rule Map: 1 PCRF Event Triggers: QoS |TIMEOUT

PCRF Origin Host: diameter1

PCRF Origin Realm: hitachi.com

Usage Monitoring Information: Monitoring Key: 0

Status: 2000 Total: Active

Bearer: NSAPI/EBI: 5 Local Data IP: 200.6.88.1 Remote Data IP: 70.70.70.4 Local Data TEID: 0x14120000 Remote Data TEID: 0x1001 Bearer State: Established Idle Timeout: 0 min AAA Interim Interval: 0 min QoS Parameters: Traffic Class: Interactive ARP: 3 Traffic Handling Priority: 1 Transfer Delay: 0 MBR Uplink: 1664 kbps MBR Downlink: 1664 kbps Signaling Indicator: 0 Forwarding Class: None Loss Priority: None Mapped V2 Parameters: QCI: 6 ARP: 11/1 /1 (PL/PVI/PCI) Charging information: Charging ID: 0x12000000 Transport Profile Name: tp1 Charging Characteristics: 0x8



Profile ID: 1 Charging Profile name: cp1 State: Ready Previous State: None

Profile selection criteria: Static default Details: Offline, Online Statistics information (PFE cleared and non-cleared): None collected Offline charging information: Current service data container sequence number: None Current partial record sequence number: 1 Number of CDRs closed: 0 Number of containers closed: 0 Online charging information: Number of online rating groups: 1 Next CC request number: 1 CC Failure Handling: Retry-and-Terminate Last CCR result code: 2001 Rating group information: Rating group: 100 Service id: 2 State: Ready RG Action ID: 0x2020000 Trigger profile: trp1 Details: Offline RG, Online RG Reporting Level: Rating Group Volume Quota: Total: 3000 Uplink: 1500 Downlink: 1500 Holding time: 600 Collection time: Fri Feb 8 06:56:56 2013 Uplink packets: 0 Downlink packets : 0 Uplink bytes: 0 Downlink bytes : 0 PCC Rule Information: Rule Name: gx-rule-2 Type: Static Associated Rule Base: None Precedence: 100 Status: Active QoS Attributes: QCI: 6 ARP: 11/0 /0 (PL/PVI/PCI) Charging Attributes: Rating Group: 100 Service ID: 2 Gating Status: enable-both AF Charging Id: None Charging Method: Online-Offline Metering Method: None Usage Monitoring Key : NULL Filter Attributes: Remote IP/Mask: 200.6.1.2/32 Protocol: any Direction: Both Local Ports: any Remote Ports: any Send to UE: Yes

2. The rating group reporting level for online charging for the subscriber is displayed

under Rating group information in the output. Make sure that the reporting level is

correct.

3. The volume quota uplink and downlink and total is displayed under Rating group

information in the output. Make sure that the quotas are correct.










CHAPTER 5

Configuration Statements

• [edit unified-edge gateways ggsn-pgw <gateway-name>] Hierarchy Level on page 65

[edit unified-edge gateways ggsn-pgw <gateway-name>] Hierarchy Level

ggsn-pgw gateway-name {anchor-pfe-ipv4-nbm-prefixesmaximum-ipv4-prefixes;anchor-pfe-ipv6-nbm-prefixesmaximum-ipv6-prefixes;apn-services {apns {[name] {aaa-profile aaa-profile;address-assignment {aaa;allow-static-ip-address {no-aaa-verify;

}dhcp-proxy-client {aaa-override;

}dhcpv4-proxy-client-profile {logical-system logical-system;pool-name pool-name;profile-name profile-name;routing-instance routing-instance;

}dhcpv6-proxy-client-profile{logical-system logical-system;pool-name pool-name;profile-name profile-name;routing-instance routing-instance;

}inet-pool {exclude-pools [value];group group;pool pool;

}inet6-pool {exclude-v6pools [value];group group;pool pool;

}


local {aaa-override;

}}allow-network-behind-mobile;apn-data-type (ipv4 | ipv4v6 | ipv6);apn-type (real | virtual | virtual-pre-authenticate);block-visitors;charging {default-profile default-profile;home-profile home-profile;profile-selection-order [profile-selection-method];roamer-profile roamer-profile;visitor-profile visited-profile;

}description description;dns-server {primary-v4 primary-v4;primary-v6 primary-v6;secondary-v4 secondary-v4;secondary-v6 secondary-v6;

}idle-timeout idle-timeout;idle-timeout-direction (both | uplink);inter-mobile-traffic {(deny | redirect redirect);

}local-policy-profile local-policy-profile;maximum-bearersmaximum-bearers;mobile-interfacemobile-interface;nbns-server {primary-v4 primary-v4;secondary-v4 secondary-v4;

}network-behind-mobile {imsi imsi {prefix-v4 [ipv4-prefix];prefix-v6 [ipv6-prefix];

}}p-cscf{[address];

}restriction-value restriction-value;selection-mode {(from-ms | from-sgsn | no-subscribed);

}service-mode service-mode-options;service-selection-profile service-selection-profile;session-timeout session-timeout;user-options {override-pco;password password;(use-apnname | use-imsi | use-msisdn | user-name username);

}verify-source-address {



disable;}wait-accounting;

}}

}call-rate-statistics {history history;interval interval;

}charging {cdr-profiles profile-name {description string;enable-reduced-partial-cdrs;exclude-attributes {apn-ni;apn-selection-mode;cc-selection-mode;dynamic-address;list-of-service-data;list-of-traffic-volumes;lrsn;ms-time-zone;network-initiation;node-id;pdn-connection-id;pdppdn-type;pgw-plmn-identifier;ps-furnish-info;rat-type;record-sequence-number;served-imeisv;served-msisdn;served-pdppdn-address;served-pdp-address-extension;serving-node-plmn-identifier;start-time;stop-time;user-location-information;

}node-id (hostname | hostname-spic | ipaddress-spic);report-requested-apn;

}charging-profiles profile-name {cdr-profile profile-name;default-rating-group rg-num;default-service-id id-num;description string;profile-id id-num;service-modemaintenance;transport-profile profile-name;trigger-profile profile-name {rating-group [value];

}}gtpp {


Chapter 5: Configuration Statements

destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;pending-queue-size value;peer peer-name {destination-ipv4-address address;destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;pending-queue-size value;reconnect-time duration;source-interface interface-name [ipv4-address address];t3-response response-interval;transport-protocol (tcp | udp);version (v0 | v1 | v2);

}reconnect-time duration;source-interface {interface-name;ipv4-address address;

}t3-response response-interval;transport-protocol (tcp | udp);version (v0 | v1 | v2);

}local-persistent-storage-options {cdrs-per-file value;disable-replication;disk-space-policy {watermark-level-1 {notification-level (both | snmp-alarm | syslog);percentage value;

}watermark-level-2 {notification-level (both | snmp-alarm | syslog);percentage value;


}}file-age {age;disable;

}file-creation-policy (shared-file | unique-file);file-format (3gpp | raw-asn);file-name-private-extension string;file-size {



size;disable;

}traceoptions {file file-name <files number> <match regular-expression> <no-world-readable |world-readable> <size size>;

flag flag;level (all | critical | error | info | notice | verbose | warning);no-remote-trace;

}user-name string;world-readable;

}traceoptions {file {file-name;files number;size size(no-world-readable | world-readable);

}flag flag;level (all | critical | error | info | notice | verbose | warning);no-remote-trace;

}transport-profiles profile-name {description string;offline {charging-function-name function-name;{charging-gateways {cdr-aggregation-limit value;cdr-release (r7 | r8 | r9 | r99);mtu value;peer-order {[peer charging-gateway-peer-name];

}persistent-storage-order {local-storage;

}switch-back-time seconds;

}container-limit value;sgsn-sgw-change-limit value;

}online {all-rgs-on-termination;charging-function-name function-name;diameter-profile profile-name;no-mscc-in-ccrt;quota-request-on-first-packetsend-ccri-on-first-packetservice-context-id service-context-id;session-failover-not-supported;single-mscc;tx-timeout timeout;

}service-modemaintenance;



}trigger-profiles profile-name {charging-method (both | none | offline | online);description string;offline {exclude {dcca-events;ms-timezone-change;plmn-change;qos-change;rat-change;sgsn-sgw-change;user-location-change;

}time-limit value;volume-limit {value;direction (both | uplink);

}}online {cc-failure-handling {block-traffic-pending-reauth-no-quota;initial-request {convert-to-offline {grant-grace-quota;

}disable-online-charging;grant-grace-quota;

}override;result-code-based-action {authorization-rejected {blacklist {retry-timer;

}}credit-control-not-applicable {convert-to-offline {grant-grace-quota;

}}credit-limit-reached {blacklist {retry-timer;

}}end-user-service-denied {convert-to-offline {grant-grace-quota;

}disable-online-charging;

}user-unknown {convert-to-offline {grant-grace-quota;




}}update-request {convert-to-offline {grant-grace-quota;


}}grant-quota {cc-octet-both volume-quota-both;cc-octet-downlink volume-quota-dl;cc-octet-uplink volume-quota-ul;cc-time time-quota;

}measurement-method (none | time | volume | volume-and-time);quota-threshold {threshold;override;

}quota-holding-time time-in-seconds;quota-validity-time time-in-seconds;reporting-level {override;(rating-group | service-identifier);

}requested-service-unit {always-include;cc-octet-both volume-quota-both;cc-octet-downlink volume-quota-dl;cc-octet-uplink volume-quota-ul;cc-time time-quota;include-quota-holding-time;

}}tariff-time-list {tariff-time;

}}

}gtp {control {dscp-code-point value;echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;forwarding-classclass-name;interface {interface-name;v4-address v4-address;

}n3-requests requests;no-response-cache;



path-management (disable | enable);response-cache-timeoutt interval-in-seconds;t3-response response-interval;

}data {echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;error-indication-interval seconds;interface {interface-name;v4-address v4-address;

}path-management (disable | enable);

}echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;gn {control {dscp-code-point value;echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;forwarding-classclass-name;interface {interface-name;v4-address v4-address;

}n3-requests requests;path-management (disable | enable);t3-response response-interval;

}data {echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;interface {interface-name;v4-address v4-address;


}echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;interface {interface-name;v4-address v4-address;


}



gp {control {dscp-code-point value;echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;forwarding-classclass-name;interface {interface-name;v4-address v4-address;






}interface {interface-name;v4-address v4-address;

}n3-requests requests;path-management (disable | enable);peer-group name {control {support-16-bit-sequence;

}echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;n3-requests requests;path-management (disable | enable);peer {[ip-addr-prefix];

}



routing-instance routing-identifier;t3-response response-interval;

}peer-history number;s5 {control {dscp-code-point value;echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;forwarding-classclass-name;interface {interface-name;v4-address v4-address;

}n3-requests requests;path-management (disable | enable);support-16-bit-sequence;t3-response response-interval;





}s8 {control {dscp-code-point value;echo-interval interval;echo-n3-requests requests;echo-t3-response response-interval;forwarding-classclass-name;interface {interface-name;v4-address v4-address;

}n3-requests requests;path-management (disable | enable);



support-16-bit-sequence;t3-response response-interval;





}t3-response response-interval;traceoptions {file filename {files files;(no-world-readable | world-readable);size size;

}flag {flag;

}level level;no-remote-trace;

}}home-plmn {[mccmccmncmnc];

}inline-services {ip-reassembly {service-set {service-set-name;

}}

}ip-reassembly-profile {profile-name;

}ipv6-router-advertisement {current-hop-limit current-hop-limit;disable;



maximum-advertisement-intervalmaximum-advertisement-interval;maximum-initial-advertisement-intervalmaximum-initial-advertisement-interval;maximum-initial-advertisementsmaximum-initial-advertisements;minimum-advertisement-intervalminimum-advertisement-interval;reachable-time reachable-time;retransmission-timer retransmission-timer;router-lifetime router-lifetime;

}local-policy-profile local-policy-profile;maximum-bearersmaximum-bearers;preemption {enable;gtpv1-pci-disable;gtpv1-pvi-disable;

}service-modemaintenance;service-selection-profiles {profile-name {term name {from {anonymous-user;domain-name domain-name;charging-characteristics charging-characteristics;imei imei;imsi imsi;maximum-bearersmaximum-bearers;msisdnmsisdn;pdn-type (ipv4 | ipv4v6 | ipv6);peer peer;peer-routing-instance peer-routing-instance;plmn {except;mccmccmncmnc;

}rat-type (eutran | geran | hspa | utran | wlan);roaming-status (home | roamer | visitor);

}then {accept;apn-name apn-name;charging-profile charging-profile;pcef-profile pcef-profile;redirect-peer redirect-peer;reject;

}}

}}software-datapath {traceoptions {file filename {files files;matchmatch;size size;(no-world-readable | world-readable);

}



flag {flag;


}}system {pfes {[interface interface-name];

}service-pics {[interface interface-name];

}session-pics {[interface interface-name];

}}traceoptions {file filename {files files;matchmatch;(no-world-readable | world-readable);size size;

}flag {flag;


}}


[edit unified-edge gateways] Hierarchy Level•

• Notational Conventions Used in Junos OS Configuration Hierarchies



http://www.juniper.net/techpubs/en_US/junos/topics/reference/general/junos-software-notational-conventions-configuration-hierarchy.html

all-rgs-on-termination (Transport Profiles—Online)

Syntax all-rgs-on-termination;

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameonline]

Release Information Statement introduced in Junos OS Mobility Release 12.1W.

Description Specify that the broadband gateway reports both active and inactive rating groups to

the Online Charging System (OCS) on bearer termination.

An inactive rating group refers to a rating group for which the broadband gateway has

received quota preemptively from the OCS, but for which the associated rule is not yet

installed by the policy and charging enforcement function (PCEF). If you include the

all-rgs-on-termination statement, the preemptive quota is returned on bearer termination.

NOTE: If you do not include the all-rgs-on-termination statement, then, by

default, the broadband gateway reports only the active rating groups to theOCS on bearer termination.

Required PrivilegeLevel

unified-edge—To view this statement in the configuration.

unified-edge-control—To add this statement to the configuration.







always-include (Trigger Profiles—Online)

Syntax always-include;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline requested-service-unit]


Description Specify that the broadband gateway always includes the Requested-Service-Unit (RSU)

attribute-value pair (AVP) in the Credit Control Request (CCR) messages to the Online

Charging System (OCS). By default, the broadband gateway includes the RSU AVP in

CCR messages sent to the OCS requesting for quota, except in the following cases:

• If the quota holding time has elapsed, the broadband gateway returns the quota to

the OCS and does not request for more quota.

• If the send-ccri-on-first-packet statement has not been included, and if the

quota-request-on-first-packet statement is configured, the broadband gateway sends

a CCR-I message to the OCS, to authorize the bearer, without the RSU AVP included.

NOTE: If youconfigureboththealways-includeand include-quota-validity-time

statements, the always-include statement takes precedence.








• requested-service-unit (Trigger Profiles—Online) on page 177



authorization-rejected (Credit Control Failure Handling)

Syntax authorization-rejected {blacklist {retry-timer;

}}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action]


Description Configure the action to be performed when the Online Charging System (OCS) sends a

Diameter Authorization Rejected message to the broadband gateway. You can also

specify that the rating group is blacklisted and that the gateway retries with the OCS

after a configured time elapses.

The remaining statements are explained separately.

Default If you do not include this statement, then the session is terminated by default if the

gateway receives a Diameter Authorization Rejected message from the OCS.








• result-code-based-action (Credit Control Failure Handling) on page 178



blacklist (Credit Control Failure Handling)

Syntax blacklist {retry-timer;

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action authorization-rejected],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action credit-limit-reached]


Description Specify that the rating group is blacklisted based on the result code (authorization rejected

or credit limit reached) received from the Online Charging System (OCS).

You can also specify a time after the rating group is blacklisted after which the gateway

retries with the OCS for authorization.

Options retry-timer—Time, in seconds, after which the gateway retries with the OCS.

Range: 120 through 3,866,040 seconds





• authorization-rejected (Credit Control Failure Handling) on page 80



• credit-limit-reached (Credit Control Failure Handling) on page 111




block-traffic-pending-reauth-no-quota (Credit Control Failure Handling)

Syntax block-traffic-pending-reauth-no-quota;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling]

Description Specify that the broadband gateway blocks traffic for a rating group (category) pending

reauthorization, when the quota is exhausted.

Default If you do not include this statement, then the gateway allows traffic by default, when

the quota is exhausted.





• cc-failure-handling (Trigger Profiles—Online) on page 83






cc-failure-handling (Trigger Profiles—Online)

Syntax cc-failure-handling {block-traffic-pending-reauth-no-quota;initial-request {convert-to-offline {grant-grace-quota;











}}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline]




Description Configure the options that determine what the broadband gateway does during credit

control failure.

If the Online Charging System (OCS) responds with a result code that is not successful,

then the actions configured for the result-code-based-action statement are performed.

If the OCS does not respond to the Credit Control Request (CCR) messages, then the

other actions configured in the cc-failure-handling statement are performed.












cc-octet-both (Trigger Profiles—Online)

Syntax cc-octet-both volume-quota-both;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline grant-quota],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline requested-service-unit]


Description Configure the volume quota (in bytes) for both uplink and downlink directions.

If the volume quota is configured for grant-quota and if the grant-grace-quota statement

is configured, then the gateway uses the configured value to grant grace quota. If the

volume quota is configured for requested-service-unit, the broadband gateway uses the

configured value to request quota from the Online Charging System (OCS).

Options volume-quota-both—Volume quota for both the uplink and downlink directions.

Range: 1,048,576 through 9,223,372,036,854,775,807 bytes







• grant-quota (Trigger Profiles—Online) on page 144





cc-octet-downlink (Trigger Profiles—Online)

Syntax cc-octet-downlink volume-quota-dl;




Description Configure the volume quota (in bytes) for the downlink direction.





Options volume-quota-dl—Volume quota for the downlink direction.













cc-octet-uplink (Trigger Profiles—Online)

Syntax cc-octet-uplink volume-quota-ul;




Description Configure the volume quota (in bytes) for the uplink direction.





Options volume-quota-ul—Volume quota for the uplink direction.













cc-time (Trigger Profiles—Online)

Syntax cc-time time-quota;




Description Configure the time quota (in seconds) that can be used for granting grace quota or for

requesting service units.

If the time quota is configured for grant-quota and if the grant-grace-quota statement is

configured, then the gateway uses the configured value to grant grace quota. If the time

quota is configured for requested-service-unit, the broadband gateway uses the configured

value to request quota from the Online Charging System (OCS).

Options time-quota—Time quota.

Range: 300 through 4,294,967,294 seconds












cdr-aggregation-limit

Syntax cdr-aggregation-limit value;

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameoffline charging-gateways],

[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-nameoffline charging-gateways]


Support at the [edit unified-edgegatewayssgwgateway-namecharging transport-profiles

profile-name offline charging-gateways] hierarchy level introduced in Junos OS Mobility

Release 11.4W.

Description Configure the maximum number of Charging Data Records (CDRs) that can be added

to a Data Record Transfer (DRT) message before it is transmitted.

A DRT message containing the CDRs is transmitted from the charging data function

(CDF) to the charging gateway function (CGF) server, when the cdr-aggregation-limit or

the mtu size is reached (whichever comes first). For efficient transmissions of DRT

messages, you may want to set the cdr-aggregation-limit to the maximum value of 16.

Options value—Number of CDRs that can be added to a DRT message.

Range: 1 through 16

Default: 5





• charging-gateways (Transport Profiles—Offline) on page 104





cdr-profile (Charging Profiles)

Syntax cdr-profile profile-name;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging charging-profilesprofile-name],

[edit unified-edge gateways sgw gateway-name charging charging-profiles profile-name]


Support at the [edit unified-edge gateways sgw gateway-name charging charging-profiles

profile-name] hierarchy level introduced in Junos OS Mobility Release 11.4W.

Description Associate a previously configured Charging Data Record (CDR) profile with a charging

profile.

When a subscriber session is created, the subscriber is bound to a charging profile and

the CDR profile configuration associated with this profile determines the information

(fields) that is included in the CDRs, which are used for billing.

Any modification to the existing configuration of this attribute must be done only when

the charging profile with which it is associated is under active maintenance mode. Use

one of the following commands, as applicable, to bring the charging profile under

maintenance mode:

• For the Gateway GPRS Support Node (GGSN) or Packet Data Network Gateway

(P-GW)—setunified-edgegatewaysggsn-pgwgateway-namechargingcharging-profiles

profile-name service-modemaintenance

• For the Serving Gateway (S-GW)—set unified-edge gateways sgw gateway-name

charging charging-profiles profile-name service-modemaintenance

TIP: If the profile is not already defined, use the one of the followingcommands, as applicable, to define a new CDR profile:

• GGSNorP-GW—setunified-edgegatewaysggsn-pgwgateway-namecharging

cdr-profiles profile-name

• S-GW—set unified-edge gateways sgw gateway-name charging cdr-profiles

profile-name

Options profile-name—Name of the CDR profile to be associated with the charging profile.





cdr-profiles on page 92•




cdr-profiles

Syntax cdr-profiles profile-name {description string;enable-reduced-partial-cdrs;exclude-attributes {apn-ni;apn-selection-mode;cc-selection-mode;dynamic-address;list-of-service-data;list-of-traffic-volumes;lrsn;ms-time-zone;network-initiation;node-id;pdn-connection-id;pdppdn-type;pgw-address-used; # S-GW onlypgw-plmn-identifier;ps-furnish-info;rat-type;record-sequence-number;served-imeisv;served-msisdn;served-pdppdn-address;served-pdp-address-extension;serving-node-plmn-identifier;sgw-change; # S-GW onlystart-time;stop-time;user-location-information;


}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging],[edit unified-edge gateways sgw gateway-name charging]


Support at the [edit unified-edge gateways sgw gateway-name charging] hierarchy level

introduced in Junos OS Mobility Release 11.4W.

Description Configure a Charging Data Record (CDR) profile. The configuration in the CDR profile

determines the content or the information that is included in a CDR, which are used for

billing.

By default, the Juniper Charging Service (J-CS) module adds all the required fields

mandated by the Third-Generation Partnership Project (3GPP) standards to the CDR.

However, you can exclude the provisional fields information from the CDR by configuring

a CDR profile.



The broadband gateway supports a maximum of 255 CDR profiles.

Options profile-name—Name of the CDR profile.

Range: 1 through 128 bytes






• charging (GGSN or P-GW) on page 96

• charging (Serving Gateway)





cdr-release

Syntax cdr-release (r7 | r8 | r9 | r99);






Release 11.4W.

r9 attribute introduced in Junos OS Mobility Release 12.1W.

Description The encoding of the Charging Data Record (CDR) is compliant with the 3GPP technical

specification release version that is configured using the statement. The supported

versions are 3GPP release versions 7, 8, and 99.

NOTE: 3GPP release versions 7, 9 and 99 are only applicable to the GGSNand P-GW (not to the S-GW), while 3GPP release version 8 is applicable tothe GGSN, P-GW, and S-GW.

For 3GPP releaseversion 7CDRs, thedecisiononwhether theCDRgeneratedis aGGSNCDR(G-CDR)or an evolvedG-CDR (eG-CDR) is basedonwhethera policy and charging enforcement function (PCEF) profile is configured forthe access point name (APN) or the chargingmethod for the trigger profileis configured as online.

Options r7—3GPP release version, 7.

r8—3GPP release version, 8.



Default: r8










cdrs-per-file

Syntax cdrs-per-file value;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charginglocal-persistent-storage-options],

[edit unified-edge gateways sgw gateway-name charging local-persistent-storage-options]


Support at the [edit unified-edge gateways sgw gateway-name charging

local-persistent-storage-options] hierarchy level introduced in Junos OS Mobility Release

11.4W.

Description Configure the maximum number of Charging Data Records (CDRs) that can be added

to a file after which the temporary CDR log file is closed and moved to a final location

within the same disk (/opt/mobility/charging/ggsn/final_log), from where it can be

transferred using SSH FTP (SFTP). Files transferred from the final location should be

deleted from the local Routing Engine disk after the transfer. Only authorized users can

transfer and delete the files (after the transfer).

However, any one of the following conditions must be met (whichever comes first) before

the files are moved from the temporary location to the final location:

• Number of CDRs per file reaches the configured or default limit.

• Size of the file reaches the configured or default limit.

• Age of the file reaches the configured or default limit.

NOTE: The default limit is applicable only if you have not configured anyvalue.

Options value—Maximum number of CDRs that can be added to a file after which it is closed and

moved to a location within the Routing Engine disk, from where it can be transferred

using SFTP.

Range: 5000 through 1,000,000

Default: 0, which indicates that there is no trigger for the CDR count per file.





• local-persistent-storage-options on page 148





charging (GGSN or P-GW)

Syntax charging {cdr-profiles profile-name {description string;enable-reduced-partial-cdrs;exclude-attributes {apn-ni;apn-selection-mode;cc-selection-mode;dynamic-address;list-of-service-data;list-of-traffic-volumes;lrsn;ms-time-zone;network-initiation;node-id;pdn-connection-id;pdppdn-type;pgw-plmn-identifier;ps-furnish-info;rat-type;record-sequence-number;served-imeisv;served-msisdn;served-pdppdn-address;served-pdp-address-extension;serving-node-plmn-identifier;start-time;stop-time;user-location-information;


}charging-profiles profile-name {cdr-profile profile-name;default-rating-group rg-num;default-service-id id-num;description string;profile-id id-num;service-modemaintenance;transport-profile profile-name;trigger-profile profile-name {rating-group [value];

}}gtpp {destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;



pending-queue-size value;peer peer-name {destination-ipv4-address address;destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;pending-queue-size value;reconnect-time duration;source-interface interface-name [ipv4-address address];t3-response response-interval;transport-protocol (tcp | udp);version (v0 | v1 | v2);

}reconnect-time duration;source-interface {interface-name;ipv4-address address;


}local-persistent-storage-options {cdrs-per-file value;disable-replication;disk-space-policy {watermark-level-1 {notification-level (both | snmp-alarm | syslog);percentage value;




}file-creation-policy (shared-file | unique-file);file-format (3gpp | raw-asn);file-name-private-extension string;file-size {size;disable;

}traceoptions {file file-name <files number> <match regular-expression> <no-world-readable |world-readable> <size size>;





}traceoptions {file {file-name;files number;size size(no-world-readable | world-readable);


}transport-profiles profile-name {description string;offline {charging-function-name function-name;{charging-gateways {cdr-aggregation-limit value;cdr-release (r7 | r8 | r9 | r99);mtu value;peer-order {[peer charging-gateway-peer-name];



}container-limit value;sgsn-sgw-change-limit value;

}online {all-rgs-on-termination;charging-function-name function-name;diameter-profile profile-name;no-mscc-in-ccrt;quota-request-on-first-packetsend-ccri-on-first-packetservice-context-id service-context-id;session-failover-not-supported;single-mscc;tx-timeout timeout;


}trigger-profiles profile-name {charging-method (both | none | offline | online);description string;offline {exclude {



dcca-events;ms-timezone-change;plmn-change;qos-change;rat-change;sgsn-sgw-change;user-location-change;











}}update-request {convert-to-offline {



grant-grace-quota;}disable-online-charging;grant-grace-quota;



}quota-holding-time time-in-seconds;quota-validity-time time-in-seconds;reporting-level {override;(rating-group | service-identifier);



}}

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name]


Description Configure the charging parameters for subscribers on the Gateway GPRS Support Node

(GGSN) or Packet Data Network Gateway (P-GW).















• [edit unified-edge gateways ggsn-pgw <gateway-name>] Hierarchy Level on page 65



charging-function-name (Transport Profiles)

Syntax charging-function-name function-name;

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameoffline],

[editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameonline]

[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-nameoffline]


Description Configure the charging function name, which is used to select the transport profile for

offline and online charging. If either the primary or secondary charging functions obtained

from the policy and charging rules function (PCRF) match the one configured here, then

the transport profile is selected.

The following conditions are applicable to the charging-function-name statement:

• The charging function name is a strings configured by the operator and is used as a

matching criteria.

• Configuring the charging function name is not mandatory for offline or online transport

profiles.

• The charging function names provided by the PCRF must match the one configured

for the transport profile. If the names provided by the PCRF do not match, then the

transport profile is not selected and the default transport profile is used.

For example, assume that you configure the charging function names for both offline

and online, that is, you configure two charging function names. The transport profile

is selected only if both names configured on the gateway match the corresponding

ones provided by the PCRF.

The charging function name is referred by the PCRF in the Credit Control Request (CCR)

and Credit Control Acknowledgment (CCA) messages exchanged over the Gx interface.

Offline Charging Data Records (CDRs) are transported from the charging data function

(CDF) to the offline charging gateway based on the transport profile selected. Online

charging messages are transported between the Packet Data Network Gateway (P-GW)

and the Online Charging System (OCS) based on the transport profile selected.


Default If you do not include this statement, then the gateway uses the default transport profile.

Options function-name—Name of the charging function name.

Range: Up to 256 characters



charging-gateways (Transport Profiles—Offline)

Syntax charging-gateways {cdr-aggregation-limit value;cdr-release (r7 | r8 | r9 | r99);mtu value;peer-order {[peer charging-gateway-peer-name];



}





profile-name offline] hierarchy level introduced in Junos OS Mobility Release 11.4W.

Description Configure a group of GTP Prime peers, the local Routing Engine disk, or both for Charging

Data Record (CDR) file storage. In addition, you can configure the following:

• The maximum number of CDRs that can be added to a Data Record Transfer (DRT)

message.

• The maximum transmission unit of a DRT message.

• The generated CDRs to be compliant with a specific 3GPP release.

• The duration that the charging data function (CDF) waits before transmitting the CDRs

to a peer that has recently come up and that has the highest priority among all the

peers, which are alive.











charging-method (Trigger Profiles)

Syntax charging-method (both | none | offline | online);

Hierarchy Level [edit unified-edgegatewaysggsn-pgwgateway-namecharging trigger-profilesprofile-name]


Description Specify the default charging method to be used for rating groups attached to the trigger

profile. The broadband gateway uses the configured default charging method only when

the policy and charging rules function (PCRF) or the static policy and charging

enforcement function (PCEF) policy do not provide a charging method.

Default If you do not include this statement, then the default charging method is set to offline

charging (offline).

Options both—Use both offline and online charging methods.

none—Charging is disabled for the subscriber.

offline—Use only the offline charging method.

online—Use only the online charging method.










charging-profiles

Syntax charging-profiles profile-name {cdr-profile profile-name;default-rating-group rg-num;default-service-id id-num;description string;profile-id id-num;service-modemaintenance;transport-profile profile-name;trigger-profile profile-name {rating-group [value];

}}





Description Configure a charging profile. The charging profile determines the overall charging

configuration for a subscriber, such as the data collected in a Charging Data Record

(CDR), the events that generate the CDR, where the CDR is stored, and so on for that

subscriber.

You can configure up to a maximum of 255 charging profiles.

Options profile-name—Name of the charging profile.













container-limit

Syntax container-limit value;




Description Configure the maximum number of containers that can be added to a Charging Data

Record (CDR). When the limit is reached, the CDR is closed.

Options value—Maximum number of containers.

Range: 1 through 15

Default: 5










convert-to-offline (Credit Control Failure Handling)

Syntax convert-to-offline {grant-grace-quota;

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling initial-request],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action credit-control-not-applicable],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action end-user-service-denied],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action user-unknown],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling update-request]

Description Specify that offline charging is used to charge rating groups in case of credit control

failure. In this case, online charging is disabled for the rating group.

NOTE: If you include this statement, you cannot configure thedisable-online-charging statement or grant-grace-quota statement at the

same hierarchy level. However, you can still configure the grant-grace-quota

statement in the convert-to-offline stanza.

Table 5 on page 109 displays how the configuration of the convert-to-offline statement

and override statement, at the [edit unified-edge gateways ggsn-pgw gateway-name

chargingtrigger-profilesprofile-nameonlinecc-failure-handling]hierarchy level, determines

the charging behavior in case of credit control failure.



Table 5: Charging Behavior Based on convert-to-offline Configuration

Only OnlineChargingEnabled;override notConfigured

Only Online ChargingEnabled; override notConfigured

Both Offline andOnline ChargingEnabled; overrideConfigured

Both Offline and OnlineChargingEnabled;overrideNotConfigured

The rating groupis charged usingoffline charging.

If the CCFH AVP receivedfrom the OCS is Continue,then the rating group ischarged using offlinecharging; if not, the sessionis terminated.

The rating group ischarged usingoffline charging.

If theCredit-Control-Failure-Handling(CCFH) attribute-value pair(AVP) received from the OnlineCharging System (OCS) isContinue, then the rating groupis charged using offline charging;if not, the session is terminated.

convert-to-offlineconfigured

The session isterminated.

If the CCFH AVP receivedfrom the OCS is Continue,then online charging isdisabled and the rating groupis not charged; if not, thesession is terminated.

The rating group ischarged usingoffline charging.

If the CCFH AVP received fromthe OCS is Continue, then therating group is charged usingoffline charging; if not, thesession is terminated.

convert-to-offlinenot configured

The remaining statement is explained separately.







• credit-control-not-applicable (Credit Control Failure Handling) on page 110

• disable-online-charging (Credit Control Failure Handling) on page 119

• end-user-service-denied (Credit Control Failure Handling) on page 124

• grant-grace-quota (Credit Control Failure Handling) on page 143

• initial-request (Credit Control Failure Handling) on page 147


• override (Credit Control Failure Handling) on page 161

• update-request (Credit Control Failure Handling) on page 210

• user-unknown (Credit Control Failure Handling) on page 212



credit-control-not-applicable (Credit Control Failure Handling)

Syntax credit-control-not-applicable {convert-to-offline {grant-grace-quota;

}}



Description Specify that in case of credit control failure, if the result code is Diameter Credit Control

Not Applicable, then the gateway will disable online charging. If offline charging is enabled,

then offline charging will continue to be applied to the rating groups.

If offline charging is disabled, then the convert-to-offline statement can be used to enable

offline charging for the rating groups, and the usage quota can be limited using the

grant-grace-quota statement.












credit-limit-reached (Credit Control Failure Handling)

Syntax credit-limit-reached {blacklist {retry-timer;

}}



Description Specify that in case of credit control failure, if the result code is Diameter Credit Limit

Reached, then the gateway will terminate the session. You can also specify that the

rating group is blacklisted and that the gateway retries with the Online Charging System

(OCS) after a certain configured time elapses.












default-rating-group

Syntax default-rating-group rg-num;






Description Specify a default rating group to be used for charging service data containers. The rating

group represents a collection of services.

NOTE: This configuration is not applicable for the Serving Gateway (S-GW).

Options rg-num—Default rating group to be used for charging.










default-service-id

Syntax default-service-id id-num;






Description Specify the default service identifier to be used for charging service data containers. This

ID is used to identify the service or the service component.

NOTE: This configuration is not applicable for the Serving Gateway (S-GW).

Options id-num—Default service identifier to be used for charging.










description (Charging-Related Profiles)

Syntax description string;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging cdr-profiles profile-name],[edit unified-edge gateways ggsn-pgw gateway-name charging charging-profilesprofile-name],

[edit unified-edge gateways ggsn-pgw gateway-name charging transport-profilesprofile-name],

[editunified-edgegatewaysggsn-pgwgateway-namecharging trigger-profilesprofile-name],[edit unified-edge gateways sgw gateway-name charging cdr-profiles profile-name],[edit unified-edge gateways sgw gateway-name charging charging-profiles profile-name],[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-name],[edit unified-edge gateways sgw gateway-name charging trigger-profiles profile-name]


Support at the [edit unified-edge gateways sgw gateway-name charging cdr-profiles

profile-name], [edit unified-edge gateways sgw gateway-name charging charging-profiles

profile-name], [edit unified-edge gateways sgw gateway-name charging transport-profiles

profile-name], and [editunified-edgegatewayssgwgateway-namecharging trigger-profiles

profile-name] hierarchy levels introduced in Junos OS Mobility Release 11.4W.

Description Enter a description for the Charging Data Record (CDR) profile, charging profile, transport

profile, or trigger profile. The description can be used to indicate the purpose of the profile.

For example, you might have a description to differentiate the default profile from other

profiles, as follows: This is the default profile to be used when a subscriber cannot be

categorized into any other profile.

Options string—Description of the profile.

Range: Up to 255 characters





• cdr-profiles on page 92







destination-ipv4-address (GTP Prime)

Syntax destination-ipv4-address address;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging gtpp peer peer-name],[edit unified-edge gateways sgw gateway-name charging gtpp peer peer-name]


Support at the [edit unified-edge gateways sgw gateway-name charging gtpp peer

peer-name] hierarchy level introduced in Junos OS Mobility Release 11.4W.

Description Configure the charging gateway function (CGF) server’s (GTP Prime peer’s) IPv4 address,

to which the Charging Data Records (CDRs) are sent as GTP Prime messages from the

charging gateway function (CGF). This is a mandatory configuration.

Options address—IPv4 address of the CGF server.





• peer (GTP Prime) on page 162





destination-port (GTP Prime)

Syntax destination-port port-number;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging gtpp],[edit unified-edge gateways ggsn-pgw gateway-name charging gtpp peer peer-name],[edit unified-edge gateways sgw gateway-name charging gtpp],[edit unified-edge gateways sgw gateway-name charging gtpp peer peer-name]


Support at the [edit unified-edge gateways sgw gateway-name charging gtpp] and [edit

unified-edge gateways sgw gateway-name charging gtpppeerpeer-name] hierarchy levels


Description Configure the TCP or UDP port on which the charging gateway function (CGF) server

listens to the GTP Prime messages sent from the charging data function (CDF).

When there are global-level and peer-level configurations, the peer-level configuration

takes precedence.

Options port-number—TCP or UDP port on which the CGF server listens to the GTP Prime messages

sent from the CDF.

Range: 1 through 65535

Default: 3386





• gtpp on page 141






diameter-profile (Transport Profiles—Online)

Syntax diameter-profile profile-name;



Description Associate a previously configured Diameter Gy profile with the transport profile.

NOTE: Youmust configure a Diameter Gy profile to be associated with atransport profile.

When a subscriber session is created, the subscriber is bound to a transport profile and

the Diameter Gy profile configuration associated with this profile determines the Online

Charging System (OCS) with which the Gateway GPRS Support Node (GGSN) or Packet

Data Network Gateway (P-GW) interacts.

TIP: If theprofile isnotalreadydefined,use the followingcommandtodefinea new Diameter Gy profile: set unified-edge diameter-profiles gy-profiles

profile-name.

Options profile-name—Name of the previously configured Diameter Gy profile to be associated

with the transport profile.










direction (Trigger Profiles)

Syntax direction (both | uplink);

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameoffline volume-limit],

[edit unified-edgegatewayssgwgateway-namecharging trigger-profilesprofile-nameofflinevolume-limit]


Support at the [edit unified-edge gateways sgw gateway-name charging trigger-profiles

profile-nameoffline volume-limit]hierarchy level introduced in Junos OS Mobility Release

11.4W.

Description Specify whether the maximum volume of data transmitted includes the data transmitted

in both the uplink and downlink directions, or only in the uplink direction.

When the configured volume limit is reached, the CDR is updated with the transmitted

uplink and downlink bytes and is closed.

Any change to the existing configuration does not affect a previously established session.

The updated configuration applies only to new sessions.

Default If you do not configure thedirection statement, then the configured volume limit includes

the total volume of data transmitted in both uplink and downlink directions.

Options both—The configured volume limit must include the total volume of data transmitted in

both uplink and downlink directions.

uplink—The configured volume limit must include the volume of data transmitted only

in the uplink direction.





• volume-limit on page 214





disable-online-charging (Credit Control Failure Handling)

Syntax disable-online-charging;


[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action end-user-service-denied],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action user-unknown],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling update-request]

Description Specify that online charging is disabled in case of credit control failure, and that offline

charging, if enabled, is used to charge rating groups. If offline charging is not enabled,

then no charging is applied to the rating group.

NOTE: If you include this statement, you cannot configure theconvert-to-offline or grant-grace-quota statements at the same hierarchy

level.

Table 6 on page 119 displays how the configuration of the disable-online-charging

statement and override statement, at the [edit unified-edge gateways ggsn-pgw

gateway-name charging trigger-profiles profile-name online cc-failure-handling] hierarchy

level, determines the charging behavior in case of credit control failure.

Table 6: Charging Behavior Based on disable-online-charging Configuration

Only OnlineChargingEnabled;override notConfigured

Only Online ChargingEnabled; override notConfigured

Both Offlineand OnlineChargingEnabled;override

Configured

Both Offline and OnlineCharging Enabled; override notConfigured

Online chargingis disabled and

If the CCFH AVP receivedfrom the OCS is Continue,


If theCredit-Control-Failure-Handling(CCFH) attribute-value pair(AVP) received from the Online

disable-online-chargingconfigured

the rating groupis not charged.

then online charging isdisabled and the ratinggroup is not charged; ifCharging System (OCS) isnot, the session isterminated.

Continue, then the rating groupis charged using offline charging;if not, the session is terminated.

The session isterminated.

If the CCFH AVP receivedfrom the OCS is Continue,then online charging is


If the CCFH AVP received fromthe OCS is Continue, then therating group is charged usingoffline charging; if not, thesession is terminated.

disable-online-chargingnot configured

disabled and the ratinggroup is not charged; ifnot, the session isterminated.









• convert-to-offline (Credit Control Failure Handling) on page 108

• end-user-service-denied (Credit Control Failure Handling) on page 124

• grant-grace-quota (Credit Control Failure Handling) on page 143



• override (Credit Control Failure Handling) on page 161


• user-unknown (Credit Control Failure Handling) on page 212

disable-replication

Syntax disable-replication;






11.4W.

Description Specify that Charging Data Records (CDRs) stored on the Routing Engine disk should

not be replicated to the standby Routing Engine. Typically, the CDRs stored on Routing

Engine disk are replicated to the standby Routing Engine, as a backup.

By default, replication is enabled.










disk-space-policy

Syntax disk-space-policy {watermark-level-1 {notification-level (both | snmp-alarm | syslog);percentage value;



}}






11.4W.

Description When you use the Routing Engine disk to store Charging Data Records (CDRs), you may

want to monitor and raise alerts if the disk space falls below a configured threshold level,

which enables you to take appropriate measures to prevent the loss of CDR data.

Use the statements within this hierarchy to configure the percentage of disk space you

want to allocate for storage, and raise alerts when the limit is reached.

You can configure up to a maximum of three threshold levels.











down-detect-time (GTP Prime)

Syntax down-detect-time duration;






Description Configure the duration for which the charging data function (CDF) must wait for a

response from the charging gateway function (CGF) server after the expiry of an n3 * t3

cycle, after which the server’s status is marked Down. The CDF then sends the GTP Prime

messages to the next configured CGF server in the corresponding transport profile.


takes precedence.

Options duration—Duration the CDF waits after the n3 * t3 cycle expiry before declaring a GTP

Prime peer as Down. The CDF then sends the GTP Prime messages to the next

configured GTP Prime peer in the corresponding transport profile.

Range: 0 through 255 seconds

Default: 10 seconds












echo-interval (GTP Prime)

Syntax echo-interval duration;






Description Configure the number of seconds that the charging data function (CDF) must wait before

sending an echo request message to the charging gateway function (CGF) server.

Echo messages are:

• Sent only for UDP connections.

• Not sent more than once in a minute.


takes precedence.

Options duration—Number of seconds that the CDF waits before sending an echo request message

to the CGF server.


Default: 60 seconds












end-user-service-denied (Credit Control Failure Handling)

Syntax end-user-service-denied {convert-to-offline {grant-grace-quota;


}



Description Specify that in case of credit control failure, if the result code is Diameter End User Service

Denied, then the gateway will terminate the session.

If offline charging is enabled, then offline charging will continue to be applied to rating

groups. If offline charging is disabled, then the convert-to-offline statement can be used

to enable offline charging for rating groups, and the usage quota can be limited using the

grant-grace-quota statement.

Alternatively, online charging can be disabled using thedisable-online-charging statement.

If offline charging is also disabled, then no charging is applied to the rating group.












enable-reduced-partial-cdrs

Syntax enable-reduced-partial-cdrs;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging cdr-profiles profile-name],[edit unified-edge gateways sgw gateway-name charging cdr-profiles profile-name]


Support at the [edit unified-edge gateways sgw gateway-name charging cdr-profiles


Description Enable the generation of reduced partial Charging Data Records (CDRs). Reduced Partial

CDRs (RPCs) contain mandatory fields as well as information regarding changes in the

session parameters relative to the previous CDR. For example, if the user equipment

location has not changed, then this information is excluded from the RPC because this

information has not changed from the previous CDR.

Default If this statement is not configured, the generation of fully qualified partial CDRs (FQPCs)

is supported. FQPCs contains all the mandatory and conditional fields, as well as those

fields that the public land mobile network (PLMN) operator has provisioned to be included

in the CDR.










exclude (Trigger Profiles—Offline)

Syntax exclude {dcca-events; # P-GW onlyms-timezone-change;plmn-change;qos-change;rat-change;sgsn-mme-change; #S-GW onlysgsn-sgw-change; #P-GW onlyuser-location-change;

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameoffline],

[editunified-edgegatewayssgwgateway-namecharging trigger-profilesprofile-nameoffline]



profile-nameoffline]hierarchy level and the sgsn-mme-changeoption introduced in Junos

OS Mobility Release 11.4W.

dcca-events option introduced in Junos OS Mobility Release 12.1W.

Description Certain signal message updates to the packet data protocol (PDP) context or bearer

trigger charging updates. However, using the statements in this hierarchy, you can choose

not to record these updates in the Charging Data Record (CDR).

For example, a quality-of-service (QoS) change results in a container being added to the

CDR. However, the container is not added if you configure to ignore this change, using

one of the following commands, as applicable:

• setunified-edgegatewaysggsn-pgwgateway-namechargingtrigger-profilesprofile-name

exclude qos-change for the Gateway GPRS Support Node (GGSN) or Packet Data

Network Gateway (P-GW).

• set unified-edge gateways sgw gateway-name charging trigger-profiles profile-name

exclude qos-change for the Serving Gateway (S-GW).

Options NOTE: The following options are applicable to both GGSN or P-GW andS-GWCDRs unless otherwise specified.

• dcca-events—(GGSN or P-GW only) If configured, excludes the generation of the offline

container when Diameter Credit Control Application (DCCA) events occur. Examples

of DCCA events include quota exhaustion, threshold being reached, and so on.

• ms-timezone-change—If configured, excludes charging data updates to the CDR when

there is a change in the MS time zone. Otherwise, when an MS time zone change occurs,

the CDR is updated with the charging information and is closed.



• plmn-change—If configured, excludes charging data updates to the CDR when there

is a PLMN change. Otherwise, when a public land mobile network (PLMN) change

occurs, the CDR is updated with the charging information and is closed.

• qos-change—If configured, excludes charging data updates to the CDR when there is

a QoS change. Otherwise, a container is added to the CDR when there is a QoS change.

• rat-change—If configured, excludes charging data updates to the CDR when there is a

Radio Access Technology (RAT) change. Otherwise, when a RAT change occurs, the

CDR is updated with the charging information and is closed.

• sgsn-mme-change—(S-GW only) If configured, excludes charging data updates to the

CDR when the SGSN or Mobility Management Entity (MME) changes reach the

maximum configured limit (determined by the value set for the sgsn-mme-change-limit

parameter). Otherwise, when the SGSN or MME changes reach the maximum configured

limit, the CDR is updated and closed.

• sgsn-sgw-change—(GGSN or P-GW only) If configured, excludes charging data updates

to the CDR when the SGSN or S-GW changes reach the maximum configuration limit

(determined by the value set for the sgsn-sgw-change-limit parameter). Otherwise,

when the SGSN or S-GW changes reach the maximum configured limit, the CDR is

updated and closed.

• user-location-change—If configured, excludes charging data updates to the CDR when

there is a change in user location. Otherwise, when a change in the user location

information (such as E-UTRAN cell global identifier [ECGI], Tracking Area Identity

[TAI], Routing Area Identity [RAI], Service Area Identity [SAI], Location Area Identity

[LAI], or Cell Global Identity [CGI]) occurs, the open containers are closed and added

to the CDR.










exclude-attributes (CDR Profiles)

Syntax exclude-attributes {apn-ni;apn-selection-mode;cc-selection-mode;dynamic-address;list-of-service-data;list-of-traffic-volumes;lrsn;ms-time-zone;network-initiation;node-id;pdn-connection-id;pdppdn-type;pgw-address-used; # S-GW onlypgw-plmn-identifier;ps-furnish-info;rat-type;record-sequence-number;served-imeisv;served-msisdn;served-pdppdn-address;served-pdp-address-extension;serving-node-plmn-identifier;sgw-change; # S-GW onlystart-time;stop-time;user-location-information;

}



pgw-address-usedand sgw-changeoptions and support for them at the [editunified-edge

gatewayssgwgateway-namechargingcdr-profilesprofile-name]hierarchy level introduced

in Junos OS Mobility Release 11.4W.

ps-furnish-infoand served-pdp-address-extensionoptions introduced in Junos OS Mobility

Release 12.1W.

Description Configure the optional attributes to be excluded from the Charging Data Record (CDR).

By default, all informational elements are included in the CDR.

CAUTION: Some of the attributes are added to the CDR irrespective ofwhetherornotyouhaveconfigured themtobeexcluded, if thecorrespondingtriggeringeventsareenabled.Thems-time-zone,serving-node-plmn-identifier,

rat-type, anduser-location-informationattributesareaddedto theCDR,unless

the correspondingms-timezone-change, plmn-change, rat-change, and

user-location-change triggering events are explicitly disabled using the

statements under the following hierarchy levels:



• [editunified-edgegatewaysggsn-pgwgateway-namechargingtrigger-profiles

profile-nameoffline exclude]hierarchy level for theGatewayGPRSSupport

Node (GGSN) or Packet Data Network Gateway (P-GW).

• [edit unified-edge gateways sgw gateway-name charging trigger-profiles

profile-nameofflineexclude]hierarchy level for theServingGateway(S-GW).



Options NOTE: The following options are applicable to both the GGSN or P-GW andthe S-GWCDRs unless otherwise specified.

• apn-ni—Exclude the Access Point Name Network Identifier (APN-NI) from the CDR.

The APN-NI defines the external network to which the user wants to connect through

the GGSN.

• apn-selection-mode—Exclude the APN selection mode from the CDR. The APN selection

mode indicates the origin of the APN and whether the Home Location Register (HLR)

or Home Subscriber Server (HSS) has verified the user’s subscription. The possible

values for this mode are:

• Mobile Station—MS-provided APN, subscription not verified, which indicates that

the mobile station (MS) provided the APN and that the HLR or HSS did not verify

the user’s subscription to the network.

• Network—Network-provided APN, subscription not verified, which indicates that the

network provided a default APN because the mobile station did not provide an APN,

and that the HLR or HSS did not verify the user’s subscription to the network.

• Verified—MS or network-provided APN, subscription verified, which indicates that

the mobile station or the network provided the APN and that the HLR or HSS verified

the user’s subscription to the network.

• cc-selection-mode—Exclude (from the CDR) the type of charging characteristic that

the GGSN or P-GW applies to the CDR: Home, Visiting, Roaming, or SGSN/S-GW

supplied.

• dynamic-address—Exclude from the CDR the packet data protocol (PDP) address that

has been dynamically allocated for the specific PDP context.

• list-of-service-data—Exclude the list of service data from the CDR. This list includes

one or more containers and each of the container includes a list of fields which records

information about the volume of data transmitted in bytes in the uplink and downlink

directions, quality-of-service (QoS) changes, and so on. For the complete list, refer to

the 3GPP 32.298 v 8.7.0 technical specification.

• list-of-traffic-volumes—Exclude the list of traffic volumes from the CDR. This list

includes one or more containers and each container includes a list of fields which

records information about the volume of data transmitted, in bytes, in the uplink and

downlink directions, the reason for closing the container, when the container is closed,

and the location of the user equipment when this data transmission occurs.

This attribute is applicable for CDRs that are compliant with the 3GPP R7 and R99

release specifications, only.

• lrsn—Exclude the Local Record Sequence Number (LRSN) from the CDR. LSRN is a

unique and sequential number generated by the network node (GGSN or P-GW) and

is assigned to the CDRs for tracking any missing billing records.

• ms-time-zone—Exclude the mobile station time zone from the CDR.



NOTE:

• This attribute is added to the CDR, irrespective of whether or not youhave configured it to be excluded, if theMS Timezone Change triggeringevent is enabled. You can disable this triggering event by including thems-timezone-change statement at the [edit unified-edge gateways

ggsn-pgw gateway-name charging trigger-profiles profile-name offline

exclude]hierarchy level (for theGGSNorP-GW), or the [edit unified-edge

gateways sgw gateway-name charging trigger-profiles profile-name offline

exclude] hierarchy level (for the S-GW).

• This attribute is applicable only to CDRs that are compliant with the3GPP R7, R8, and R9 release specifications.

• network-initiation—Exclude (from the CDR) the indication that the PDP context is

network initiated.

This attribute is applicable only to CDRs that are compliant with the 3GPP R7 and R99

release specifications.

• node-id—Exclude (from the CDR) the ID of the network element node that generates

the CDR.

On the MX Series router, the format of the node ID isggsn/pgw-ip-address:virtual-spic-id.

• pdn-connection-id—Exclude the Packet Data Network (PDN) connection from the

CDR. This ID uniquely identifies different records belonging to the same PDN connection.

This field includes the charging ID of the first IP-CAN bearer activated within the PDN

connection. Together with the P-GW address, it uniquely identifies the PDN connection.

This attribute is applicable only for CDRs that are compliant with the 3GPP R8 and R9

release specification.

• pdppdn-type—Exclude the PDP Type and PDN Type attributes from the CDR. Both

PDP Type and PDN Type define the end-user protocol used between the external PDN

and the mobile station.



• pgw-address-used—Exclude the P-GW address-used attribute from the CDR. This

option is applicable only to the S-GW.

• pgw-plmn-identifier—Exclude the P-GW public land mobile network (PLMN) identifier

(mobile country code and mobile network code) from the CDR.

This attribute is applicable only to CDRs that are compliant with the 3GPP R8, R9, and

R99 release specifications.

• ps-furnish-info—Exclude the PS Furnish Info attribute (where PS stands for Packet

Switched) from the CDR. This information is provided by the online charging system

(OCS) in the PS Furnish Charging Information attribute-value pair (AVP).



• rat-type—Exclude the Radio Access Technology (RAT) type used by the mobile station

(eUTRAN, GERAN, WLAN, GAN, HSPA Evolution, or evolved High Rate Packet Data

[eHRPD]) from the CDR.

NOTE:

• This attribute is added to the CDR, irrespective of whether or not youhave configured it to be excluded, if the RAT Change triggering event isenabled.Youcandisable this triggeringeventby including the rat-change

statement at the [edit unified-edge gateways ggsn-pgw gateway-name

charging trigger-profiles profile-name offline exclude] hierarchy level (for

theGGSNorP-GW),or the [editunified-edgegatewayssgwgateway-name

charging trigger-profiles profile-name offline exclude] hierarchy level (for

the S-GW).

• This information is applicable only for CDRs that are compliant with the3GPP R7, R8, and R9 release specifications.

• record-sequence-number—Exclude the record sequence number from the CDR. The

record sequence number is a sequential number assigned to each partial CDR of a

particular PDP context or IP-CAN bearer. This number is not assigned if there is only

one CDR generated during the lifetime of a subscriber.

• served-imeisv—Exclude the International Mobile Station Equipment Identity and

Software Version Number (IMEISV) attribute of the served mobile equipment (ME)

from the CDR.

• served-msisdn—Exclude the mobile station ISDN (MSISDN) number of the served

equipment from the CDR.

• served-pdp-address-extension—Exclude the served PDP context or IP-CAN bearer

address extension attribute from the CDR. This attribute is used when the PDP Type

is IPv4v6; it carries the IPv4 address.

• served-pdppdn-address—Exclude the served PDP context or IP-CAN bearer address

attribute from the CDR.



• serving-node-plmn-identifier—Exclude the serving node (SGSN or S-GW) PLMN identifier

(mobile country code and mobile network code) from the CDR.

NOTE:

• This attribute is added to the CDR, irrespective of whether or not youhave configured it to be excluded, if the PLMN Change triggering eventis enabled. You can disable this triggering event by including theplmn-change statement at the [edit unified-edge gateways ggsn-pgw

gateway-name charging trigger-profiles profile-name offline exclude]

hierarchy level (for theGGSNorP-GW),or the [editunified-edgegateways

sgw gateway-name charging trigger-profiles profile-name offline exclude]

hierarchy level (for the S-GW).

• This information is applicable only for CDRs that are compliant with the3GPP R8 and R9 release specifications.

• sgw-change—Exclude the S-GW change attribute from the CDR. This option is

applicable only to the S-GW.

• start-time—Exclude (from the CDR) the time when the IP-CAN session is established

at the P-GW for the first bearer in this session.



• stop-time—Exclude (from the CDR) the time when the user IP-CAN session is terminated

for the last bearer in this session.



• user-location-information—Exclude (from the container) the location of the user

equipment during the service data container recording interval. If this attribute is

excluded from the container, then it is also excluded from the CDR.

NOTE:

• This attribute is added to the CDR, irrespective of whether or not youhave configured it to be excluded, if the User Location Change triggeringevent is enabled. You can disable this triggering event by including theuser-location-change statement at the [edit unified-edge gateways

ggsn-pgw gateway-name charging trigger-profiles profile-name offline

exclude]hierarchy level (for theGGSNorP-GW), or the [edit unified-edge

gateways sgw gateway-name charging trigger-profiles profile-name offline

exclude] hierarchy level (for the S-GW).

• This information is applicable only for CDRs that are compliant with the3GPP R7, R8, and R9 release specifications.



file-age

Syntax file-age {age;disable;

}




disable statement and support at the [edit unified-edge gateways sgw gateway-name

charging local-persistent-storage-options]hierarchy level introduced in Junos OS Mobility

Release 11.4W.

Description Configure the duration, in minutes, after which the temporary Charging Data Record

(CDR) log file is closed and moved to a final location within the same disk

(/opt/mobility/charging/ggsn/final_log), from where it can be transferred using SSH FTP

(SFTP).

Files transferred from the final location should be deleted from the local Routing Engine

disk after the transfer. Only authorized users can transfer and delete the files (after the

transfer). However, any one of the following conditions (whichever comes first) must be

met before the files are moved from the temporary location to the final location:

• The age of the file reaches the configured or default limit.

• The size of the file reaches the configured or default limit.

• The number of CDRs per file reaches the configured or default limit.


Default If you do not configure this statement, then the trigger based on file age is enabled by

default.

Options age—Duration, in minutes, after which a CDR file is closed and moved to a final location

within the Routing Engine disk, from where it can be transferred using SFTP.

Range: 20 through 7200 minutes

Default: 120 minutes

disable—Disable the file age trigger.










file-creation-policy

Syntax file-creation-policy (shared-file | unique-file);






11.4W.

Description Configure whether Charging Data Records (CDRs) generated for a specific transport

profile from all the services PICs should be routed to a single temporary file (shared-file

option) or to multiple files, with each file storing CDRs generated from a single services

PIC (unique-file configuration).

Default If you do not include the file-creation-policy statement, CDRs from all the services PICs

are routed to a single temporary file (shared-file option)

Options shared-file—CDRs are routed to the files based on the file-routing criteria of the transport

profile. In this configuration, all the CDRs generated for a specific transport profile

from all the services PICs are routed to a single CDR temporary file. When a file

trigger, such as file size, file age, or CDR count, triggers temporary file closure, the

files are moved to the final CDR location (/opt/mobility/charging/ggsn/final_log).

This is the default.

unique-file—CDRs are routed to the files based on the file routing criteria of the transport

profile. In this configuration, all the CDRs generated for a specific transport profile

from each services PIC are routed to a separate CDR temporary file. When a file

trigger, such as file size, file age, or CDR count, triggers temporary file closure, the

files are moved to a final CDR location (/opt/mobility/charging/ggsn/final_log).










file-format

Syntax file-format (3gpp | raw-asn);






11.4W.

Description Specify the file format for Charging Data Records (CDRs) stored in the CDR log files.

Default If you do not include the file-format statement, the CDRs are stored in a format compliant

with the 3GPP 32297 technical specification release (3gpp option).

Options 3gpp—CDRs are stored in a format that is compliant with the 3GPP 32297 technical

specification release.

raw-asn—CDRs are stored in raw Abstract Syntax Notation One (ASN.1) format.










file-name-private-extension

Syntax file-name-private-extension string;






11.4W.

Description Specify a private extension (string) that is appended to the filenames.

NOTE: The final CDR log files are stored in the/opt/mobility/charging/ggsn/final_log directory in the filename format

NodeID_-_PIC_-_transport-profile-id_-_RC.date_-_time[.PI].cdr, where:

• NodeID—Name of the host that generated the file.

• PIC—Number of the PIC that is generating the CDR.

• transport-profile-id—Number of the transport profile generating the CDR.

• RC—Running count or sequence number, starting with the value of 1.

• date—Datewhen theCDR filewasclosed in the formatYYYYMMDD, whereYYYY is the year,MM is themonth (01-12), and DD is the day (01-31).

• time—Timewhen the CDR file was closed in the formatHHMMshhmm,whereHH is the local timehourofday (00-23),MM is the local timeminuteof the hour (00-59), s is the sign of local time differential fromUTC (+ or-), hh is the local time differential hour (00-23), andmm is the local timedifferential minute (00-59).

• PI—(Optional) Private information that is explicitly configured.

• cdr—File extension is always cdr.

Options string—Private extension.

Values: 1 through 16 bytes










file-size

Syntax file-size {size;disable;

}




disable statement and support at the [edit unified-edge gateways sgw gateway-name

charging local-persistent-storage-options]hierarchy level introduced in Junos OS Mobility

Release 11.4W.

Description Configure maximum size that the file can reach, in MB, after which the temporary Charging

Data Record (CDR) log file is closed and moved to a final location within the same disk

(/opt/mobility/charging/ggsn/final_log), from where it can be transferred using SSH FTP

(SFTP).

Files transferred from the final location should be deleted from the local Routing Engine

disk after the transfer. Only authorized users can transfer and delete the files (after the

transfer). However, any one of the following conditions (whichever comes first) must be

met before the files are moved from the temporary location to the final location:

• Size of the file reaches the configured or default limit.

• Age of the file reaches the configured or default limit.

• Number of CDRs per file reaches the configured or default limit.


Default If you do not configure this statement, then the trigger based on file size is enabled by

default.

Options value—Maximum size that the CDR file can reach, in MB, after which it is closed and

moved to a final location within the Routing Engine disk, from where it can be

transferred using SFTP.

Range: 1 MB to 1024 MB

Default: 10 MB

disable—Disable the file size trigger.






gtpp

Syntax gtpp {destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;pending-queue-size value;peer peer-name {destination-ipv4-address address;destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;pending-queue-size value;reconnect-time duration;source-interface interface-name [ipv4-address address];t3-response response-interval;transport-protocol (tcp | udp);version (v0 | v1 | v2);

}reconnect-time duration;source-interface {interface-name;[ipv4-address address;


}





Description The statements in this hierarchy enable you to set global as well as unique configurations

for the general packet radio service (GPRS) tunneling protocol Prime (GTP Prime) peers

(Charging Gateway Function [CGF] servers). If no separate configuration is defined for

a peer, then the global configurations apply for that peer.

The charging data function (CDF) sends the Charging Data Records (CDRs) as GTP Prime

messages to the GTP Prime peer, based on this configuration.




grant-grace-quota (Credit Control Failure Handling)

Syntax grant-grace-quota;


[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling initial-request convert-to-offline],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action credit-control-not-applicableconvert-to-offline],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action end-user-service-deniedconvert-to-offline],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling result-code-based-action user-unknown convert-to-offline],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling update-request],

[edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline cc-failure-handling update-request convert-to-offline]

Description Specify that, in case of credit control failure, the subscriber session is extended until the

grace quota elapses.

NOTE: The grace quota can be configured using the grant-quota statement

at the [edit unified-edge gateways ggsn-pgw gateway-name charging

trigger-profiles profile-name online] hierarchy level.

If you include this statement, you cannot configure the convert-to-offline or

disable-online-charging statements at the same hierarchy level.







• convert-to-offline (Credit Control Failure Handling) on page 108

• disable-online-charging (Credit Control Failure Handling) on page 119






grant-quota (Trigger Profiles—Online)

Syntax grant-quota {cc-octet-both volume-quota-both;cc-octet-downlink volume-quota-dl;cc-octet-uplink volume-quota-ul;cc-time time-quota;

}



Description Configure the grace quota to be allocated in case the quota is exhausted.

The broadband gateway allocates the grace quota when the quota for the rating group

(category) has been exhausted.












header-type (GTP Prime)

Syntax header-type (long | short);






Description Configure the charging data function (CDF) GTP Prime message header length to match

the version supported on the charging gateway function (CGF) server, which can be set

to either short (6 bytes) or long (20 bytes). The long format is supported only in GTP

Prime version 0. GTP Prime versions 1 and 2 support the short header length only.


takes precedence.

Options long—CDF GTP Prime message header length is set to 20 bytes.

short—CDF GTP Prime message header length is set to 6 bytes.












include-quota-holding-time (Trigger Profiles—Online)

Syntax include-quota-holding-time;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline requested-service-unit]


Description Specify that the broadband gateway includes the Requested-Service-Unit attribute-value

pair (AVP) in the Credit Control Request (CCR) messages to the Online Charging System

(OCS), when the usage is reported for the reason of quota holding time. By default, the

gateway does not include the Requested-Service-Unit AVP in CCR messages to the OCS,

when the reporting reason is quota holding time.

NOTE: If youconfigureboththealways-includeand include-quota-validity-time

statements, the always-include statement takes precedence.











initial-request (Credit Control Failure Handling)

Syntax initial-request {convert-to-offline {grant-grace-quota;


}



Description Configure the actions to be carried out by the broadband gateway when the initial Credit

Control Request fails.


Default If you do not include this statement, and if the secondary Online Charging System (OCS)

is configured, then the gateway tries to establish a session with the secondary OCS. If

that is not configured, then the subscriber’s session is terminated by default.











local-persistent-storage-options

Syntax local-persistent-storage-options {cdrs-per-file value;disable-replication;disk-space-policy {watermark-level-1 {notification-level (both | snmp-alarm | syslog);percentage value;




}file-creation-policy (shared-file | unique-file);file-format (3gpp | raw-asn);file-name-private-extension string;file-size {size;disable;

}traceoptions {file file-name <files number> <match regular-expression> <no-world-readable |world-readable> <size size> ;



}





Description Configure the Charging Data Record (CDR) file storage options, which are measures to

prevent loss of the CDR data.

You typically store the CDRs on the local Routing Engine disk when you do not have any

external charging gateway function (CGF) servers configured to store them or when all

the CGF servers are down.



When you choose to store the CDRs locally, the CDRs generated by the services PICs are

routed to a file on the Routing Engine disk. Some of the options that can be configured

include the following:

• Action to be taken when the disk space falls below the configured watermark level.

• Restricting access to the files to a specific user.

• File routing criteria—CDRs are routed to the files based on the file-routing criteria of

the transport profile. Therefore, all CDRs generated for a given transport profile are

saved in a specific CDR log file.










local-storage

Syntax local-storage;

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameoffline charging-gateways persistent-storage-order],

[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-nameoffline charging-gateways persistent-storage-order]



profile-nameofflinecharging-gatewayspersistent-storage-order]hierarchy level introduced

in Junos OS Mobility Release 11.4W.

Description Configure the Routing Engine disk as backup storage for the Charging Data Records

(CDRs) when the external storage resources (charging gateway function [CGF] servers)

are down or if no external servers are configured.

Default If you do not include the local-storage statement, the backup storage is disabled.





• persistent-storage-order on page 166





measurement-method (Trigger Profiles—Online)

Syntax measurement-method (none | time | volume | volume-and-time);



Description Specify the default measurement method. This specified measurement method is used

by the gateway to include the Requested Service Unit (RSU) attribute-value pair (AVP)

in the Credit Control Request (CCR) message if the policy and charging enforcement

function (PCEF) does not include the Requested Service Unit (RSU) attribute-value pair

(AVP) in the CCR message.

Options none—Send an empty RSU.

time—Include the CC Time AVP in the RSU based on configured time (cc-time).

volume—Include the CC Octet Both, CC Octet Downlink, and CC Octet Uplink AVPs in

the RSU based on configured values (cc-octet-both, cc-octet-downlink, and

cc-octet-uplink, respectively).

time-and-volume—Include both time and volume AVPs in the RSU based on the configured

values.











mtu (Transport Profiles)

Syntax mtu value;






Release 11.4W.

Description Configure the maximum transmission unit (MTU) for a Data Record Transfer (DRT)

message, which represents the maximum size in bytes that a DRT message can reach

before it is transmitted.

A DRT message containing the Charging Data Records (CDRs) is transmitted from the

charging data function (CDF) to the charging gateway function (CGF) server, when the

cdr-aggregation-limit or the mtu size is reached (whichever comes first).

Options value—Maximum size, in bytes, for a DRT message.


Default: 1500 bytes










n3-requests (GTP Prime)

Syntax n3-requests requests;






Description Configure the maximum number of times the charging data function (CDF) attempts to

send echo request messages to the charging gateway function (CGF) server, after which

the CDF waits for a configured duration (seedown-detect-time) for any response before

declaring the server as Down.

The broadband gateway retransmits the requests to the UDP peers. However, for the

TCP peers, the requests are retransmitted to a newer peer (when there is a switchover)

or to the same peer (when it becomes alive after being Down).


takes precedence.

Options requests—Number of times that the CDF attempts to send a request to a CGF server after

which the CDF waits for a configured duration (see down-detect-time) before

declaring the server as Down.

Range: 1 through 5

Default: 3












node-id (CDR Profiles)

Syntax node-id (hostname | hostname-spic | ipaddress-spic);



Description Specify the format of the node identifier (ID) in the Charging Data Record (CDR). The

node identifier indicates the node that generated the CDR.

NOTE:

• If you do not include this statement, then the IP address of the nodegenerating the CDR and the ID of the services PIC on which the CDRwastriggered, with a colon (:) as a delimiter, are used as the node identifier inthe CDR.

• When you include the node-id statement and commit the configuration,

the new node ID format comes into effect immediately; that is, allsubsequent CDRs use the new node ID format.

Options hostname—Specify that the hostname of the node generating the CDR is used as the

node identifier.

hostname-spic—Specify that the hostname of the node generating the CDR and the ID

of the services PIC on which the CDR was triggered, delimited by a colon (:), are used

as the node identifier. For example, if the hostname of the node is jnprcg and the ID

of the services PIC is 2, the node ID is jnprcg:2.

ipaddress-spic—Specify that the IP address of the node generating the CDR and the ID

of the services PIC on which the CDR was triggered, delimited by a colon (:), are used

as the node identifier. For example, if the IP address of the node is 192.168.1.19 and

the ID of services PIC is 3, the node ID is 192.168.1.19:3.

This is the default.










no-mscc-in-ccrt (Transport Profiles—Online)

Syntax no-mscc-in-ccrt;



Description Specify that no Multiple Services Credit Control (MSCC) attribute-value pairs (AVPs)

are included in the Credit Control Request Terminate (CCR-T) messages sent from the

broadband gateway to the Online Charging System (OCS).

This configuration is useful in cases where the OCS does not support the MSCC AVP in

CCR-T messages. If you include this statement, then the broadband gateway first sends

the MSCC AVPs in the CCR-Update (CCR-U) message (to report usage), and then sends

the CCR-T message to the OCS.

NOTE: If you do not include the no-mscc-in-ccrt statement, then the

broadband gateway sends the MSCC AVPs in CCR-Tmessages (to reportusage).










no-path-management (GTP Prime)

Syntax no-path-management;






Description Use this statement to disable path management messages. If this statement is configured,

no echo messages are sent. However, the router responds to any echo messages that

are received.

NOTE:

• Pathmanagement refers to the exchange of echomessages betweenchargingdata function (CDF)andcharginggateway function (CGF)servers(GTP Prime peers) to find out whether a CGF server is alive to process theGTP Primemessages sent from the CDF.

• Echomessages are sent only for UDP connections.


takes precedence.












offline (Transport Profiles)

Syntax offline {charging-function-name function-name;{charging-gateways {cdr-aggregation-limit value;cdr-release (r7 | r8 |r9 | r99);mtu value;peer-order {[peer charging-gateway-peer-name];



}container-limit value;sgsn-sgw-change-limit value; #P-GW only

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging transport-profilesprofile-name],

[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-name]




Description Configure the transport parameters for offline charging records, such as:

• The charging gateway peers that store the Charging Data Records (CDRs).

• The maximum number of CDRs that can be added to a Data Record Transfer (DRT)

message.

• The maximum transmission unit of a DRT message.

• The generated CDRs to be compliant with a specific 3GPP release.

• The duration that the charging data function (CDF) waits before transmitting the CDRs

to a peer that has recently come up and that has the highest priority among all the

peers, which are alive.

• Whether to use the local Routing Engine disk for CDR storage.

• The charging function name that is used to select the offline charging gateway.











offline (Trigger Profiles)

Syntax offline {exclude {dcca-events; #P-GW onlyms-timezone-change;plmn-change;qos-change;rat-change;sgsn-mme-change; #S-GW onlysgsn-sgw-change; #P-GW onlyuser-location-change;

}sgsn-mme-change-limit value; #S-GW onlytime-limit value;volume-limit {value;direction (both | uplink);

}}

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namecharging trigger-profilesprofile-name],[edit unified-edge gateways sgw gateway-name charging trigger-profiles profile-name]




Description Configure the attributes that trigger charging updates for offline charging records.

For example, you can set the maximum duration that the Charging Data Record (CDR)

can remain open (time-limit), maximum volume of data that can be transmitted before

closing a CDR (volume-limit), maximum number of containers that can be added to a

CDR, or maximum number of Serving Gateway (S-GW) or serving GPRS support node

(SGSN) changes that can occur before the CDR is updated and closed.












online (Transport Profiles)

Syntax online {all-rgs-on-termination;charging-function-name function-name;diameter-profile profile-name;no-mscc-in-ccrt;quota-request-on-first-packetsend-ccri-on-first-packetservice-context-id service-context-id;session-failover-not-supported;single-mscc;tx-timeout timeout;

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging transport-profilesprofile-name]


Description Configure the parameters for transporting online charging messages between the Gateway

GPRS Support Node (GGSN) or Packet Data Network Gateway (P-GW) and the online

charging system (OCS).











online (Trigger Profiles)

Syntax online {cc-failure-handling {block-traffic-pending-reauth-no-quota;initial-request {convert-to-offline {grant-grace-quota;











}}grant-quota {cc-octet-both volume-quota-both;cc-octet-downlink volume-quota-dl;cc-octet-uplink volume-quota-ul;



cc-time time-quota;}measurement-method (none | time | volume | volume-and-time);quota-holding-time time-in-seconds;quota-threshold {threshold;override;

}quota-validity-time time-in-seconds;reporting-level {override;(rating-group | service-identifier);


}}

Hierarchy Level [edit unified-edgegatewaysggsn-pgwgateway-namecharging trigger-profilesprofile-name]


Description Configure the trigger attributes for online charging.











override (Credit Control Failure Handling)

Syntax override;


Description Specify that the broadband gateway overrides the credit control failure handling

parameters received from the Online Charging System (OCS) and uses the parameters

configured locally on the gateway.

Default If you do not include this statement, then the gateway uses the parameters provided by

the OCS. If the OCS does not provide the parameters, then the parameters configured

locally on gateway are used.










peer (GTP Prime)

Syntax peer peer-name {destination-ipv4-address address;destination-port port-number;down-detect-time duration;echo-interval duration;header-type (long | short);n3-requests requests;no-path-management;pending-queue-size value;reconnect-time duration;source-interface {interface-name;ipv4-address address;


}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging gtpp],[edit unified-edge gateways sgw gateway-name charging gtpp]


Support at the [edit unified-edge gateways sgw gateway-name charging gtpp] hierarchy

level introduced in Junos OS Mobility Release 11.4W.

Description Configure GTP Prime peers (charging gateway function [CGF] servers). You can configure

up to a maximum of 24 peers. The charging data function (CDF) sends the Charging Data

Records (CDRs) as GTP Prime messages to the GTP Prime peer, based on this

configuration.


takes precedence.












peer (Peer Order)

Syntax [peer charging-gateway-peer-name];

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameoffline charging-gateways peer-order],

[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-nameoffline charging-gateways peer-order]



profile-name offline charging-gateways peer-order] hierarchy level introduced in Junos


Description Configure the name of the charging gateway peer. However, make sure the peer that you

specify here is previously configured for its IP address, name, and so on, using one of the

following statements, as applicable. Otherwise, you will encounter a configuration error.

• set unified-edge gateways ggsn-pgw gateway-name charging gtpp peer for the gateway

GPRS support node (GGSN) or Packet Data Network Gateway (P-GW).

• setunified-edgegatewayssgwgateway-namecharginggtpppeer for the Serving Gateway

(S-GW).

Options charging-gateway-peer-name—Name of the charging gateway server.





• peer-order on page 164






peer-order

Syntax peer-order {[peer charging-gateway-peer-name];

}






Release 11.4W.

Description Configure the charging gateway function (CGF) servers. You can configure up to a

maximum of three servers for a transport profile.

When more than one CGF servers are available for storing Charging Data Records (CDRs),

the charging data function (CDF) must identify the server to which to route the CDRs to

first. The peer order determines this hierarchy, using which the CDF tries to send the CDRs

to the server that comes first in this order. The peer that comes first in the order is treated

as the highest-priority peer. At any given time, CDRs are sent to only one of the peers. If,

for any reason, the first server goes down, the CDF tries to send the CDRs to the server

that comes next in the order. However, if a higher-priority peer comes up, the CDRs are

sent to this peer after a waiting period determined by the switch-back-time configuration.

When required, the priority of any peer can be changed by using the configuration option

to insert before or insert after the existing peers.

NOTE: If all thepeersareDownand if youhaveconfigured theRoutingEngine

disk as the backup storage option, then the CDRs are routed to the RoutingEngine disk. However, if one ormore peers comealive, thenCDFwaits for theconfigured switch-back-time duration and routes the CDRs to the highest

priority peer that is alive after this duration. The CDRs that were previouslystored on the Routing Engine disk are not routed to the charging gateway(peer) and remain on the disk. You need to transfer the CDRs using SSH FTP(SFTP) from the following location on the disk:/opt/mobility/charging/ggsn/final_log.






charging-gateways (Transport Profiles—Offline) on page 104•






pending-queue-size (GTP Prime)

Syntax pending-queue-size value;






Description Configure the maximum number of Data Record Transfer (DRT) messages that can be

sent by the charging data function (CDF) without an acknowledgement from the charging

gateway function (CGF) server. When the limit is reached, CDF stops sending the

messages to that CGF server.


takes precedence.

Options value—Maximum number of DRT messages that can be queued without an

acknowledgement from the CGF server.

Range: 1 through 4096

Default: 1024












persistent-storage-order

Syntax persistent-storage-order {local-storage;

}






Release 11.4W.

Description Configure the local storage of Charging Data Records (CDRs). You may want to store

the CDRs on the local Routing Engine disk for one of the following reasons:

• When there are no charging gateway peers configured for a transport profile

• When none of the primary, secondary, or tertiary charging gateway peers can be reached

(that is, when they are down)











profile-id (Charging Profiles)

Syntax profile-id id-num;






Description Configure a unique identifier to be associated with a charging profile. You must configure

a profile ID for a charging profile.

Based on the user’s subscription, the Serving Gateway (S-GW), serving GPRS support

node (SGSN), or RADIUS server returns the charging profile (identified by the profile ID)

that must be used for charging the mobile subscriber. If more than one node returns a

profile ID, then the profile selection order configuration determines which server’s profile

ID must be given higher priority. This profile ID is then matched with the configured profile

ID to choose the correct charging profile for that subscriber. However, if a server returns

an incorrect or unconfigured charging profile ID, the profile ID returned by the server that

is next in priority is taken into consideration. If none of the profile IDs match, then charging

is disabled for the subscriber.

NOTE: The RADIUS server returns the profile ID as a four-byte hexadecimalvalue in the Access Accept message.

Options id-num—Unique number to be associated with the charging profile.

Range: 1 through 65,534








• profile-selection-order (APN)

• profile-selection-order (Serving Gateway)



quota-holding-time (Trigger Profiles—Online)

Syntax quota-holding-time time-in-seconds;



Description Configure the quota holding time, in seconds. The configured quota holding time is used

if the Online Charging System (OCS) does not provide quota holding time in the

Quota-Holding-Time attribute-value pair (AVP) in the Credit Control Answer (CCA)

message. The quota holding time provided by the OCS takes precedence over the one

configured (locally) on the broadband gateway. A quota holding time of zero indicates

that the quota holding mechanism should not be used.

The quota holding time indicates the number of seconds for which the quota granted by

the OCS is held by the gateway when no traffic is received for that rating group. If traffic

is received before the quota holding time elapses, the quota holding time is reset. If no

traffic is received before the quota holding time elapses, the broadband gateway sends

a Credit Control Request Update (CCR-U) message to the OCS indicating that the quota

holding time has elapsed.

NOTE: If you do not include the quota-holding-time statement, the quota

holding timeprovidedby theOCS is used. If noquotaholding time isprovidedby the OCS, then the quota holdingmechanism is not used.

Options time-in-seconds—Quota holding time, in seconds.

Range: 300 through 864,000 seconds








• quota-validity-time (Trigger Profiles—Online) on page 171



quota-request-on-first-packet (Transport Profiles—Online)

Syntax quota-request-on-first-packet;



Description Specify that the broadband gateway requests quota (for a rating group) from the Online

Charging System (OCS) only on receipt of the first packet matching that rating group.

If you do not include the quota-request-on-first-packet statement, then, by default,

broadband gateway requests quota from the OCS when the rating group is created.

NOTE:

• If the send-ccri-on-first-packetstatement (at the [editunified-edgegateways

ggsn-pgw gateway-name charging transport-profiles profile-name online]

hierarchy level) isnot included, thenthebroadbandgatewaysendsaCreditControlRequest-Initial (CCR-I)message to theOCS,duringbearer creation,without anyMultiple Services Credit Control (MSCC) attribute-value pairs(AVPs); this isdone forbearerauthorization.When thebroadbandgatewayreceives the first packet for the rating group, it requests for quota for thatrating group by sending the CCR-Update (CCR-U)message to the OCS.

• The quota-request-on-first-packet statement is applicable at the rating

group level, whereas the send-ccri-on-first-packet statement is applicable

at the bearer level.








• send-ccri-on-first-packet (Transport Profiles—Online) on page 179



quota-threshold (Trigger Profiles—Online)

Syntax quota-threshold {threshold;override;

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging trigger-profiles profile-nameonline],

[editunified-edgegatewayssgwgateway-namecharging trigger-profilesprofile-nameonline]


Description Configure the quota threshold for the quota received from the Online Charging System

(OCS). The quota threshold can be specified as a percentage of the total quota allocated.

You can also specify that the configured quota threshold overrides the one provided by

the OCS.

The broadband gateway uses the quota threshold to determine when to report the used

quota to and request more quota from the OCS. For example, if the OCS provides 100

KB of quota and if the quota threshold is 70 percent, then the gateway sends the OCS a

Credit Control Request-Update message with the used quota, when the quota used is

70 KB.

Options threshold—Quota threshold, specified as a percentage of the total quota allocated.

Range: 5 through 95 percent

override—Override the quota threshold provided by the OCS and use the configured

threshold.










quota-validity-time (Trigger Profiles—Online)

Syntax quota-validity-time time-in-seconds;



Description Configure the quota validity time, in seconds. The configured quota validity time is used

if the Online Charging System (OCS) does not provide quota validity time in the

Validity-Time attribute-value pair (AVP) in the Credit Control Answer (CCA) message.

The quota validity time indicates the number of seconds for which the quota granted by

the OCS is valid for a session (across all rating groups). When the validity time elapses,

the broadband gateway reauthorizes the quota using a Credit Control Request (CCR)

Update Request message.

Options time-in-seconds—Quota validity time, in seconds.









• quota-holding-time (Trigger Profiles—Online) on page 168



rating-group (Trigger Profile)

Syntax rating-group [value];

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingcharging-profilesprofile-nametrigger-profile profile-name],

[edit unified-edge gateways sgw gateway-name charging charging-profiles profile-nametrigger-profile profile-name]


Description Specify one or more rating group identifiers that should be associated with the trigger

profile. A rating group represents a collection of services.

The rating group is used to select the trigger profile to be associated with a charging

profile. If the rating group identifier received by the broadband gateway matches the

rating group identifier configured here, then the trigger profile with which the rating group

identifier is associated is linked to the charging profile.

NOTE: If youdonot configure a rating group identifier, then thegatewayusesthe default trigger profile.

Options [value]—One or more rating group identifiers. To enter more than one value, enclose the

values in square brackets ([]).

Range: 0 through 4,294,967,294







• trigger-profile (Charging Profiles) on page 204



redirect-reason (Service Filter)

Syntax redirect-reason [ aoc dpi ];

Hierarchy Level [edit firewalls family inet service-filter filter-name term term-name from]

Release Information Statement introduced in Junos OS Mobility Release 12.1W2.

Description Configure the service filter fromcondition to trigger service (when coupled with the service

action) for a subscriber requiring Advice of Charge (AoC) notification or when the

subscriber’s quota is exhausted (Top-Up).

NOTE: For the AoC feature, youmust configure both the deep packetinspection (dpi) and aoc options.

Options aoc—Match the packets requiring AoC treatment.

dpi—Match the packets requiring DPI treatment.


interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.


• service on page 180





reconnect-time (GTP Prime)

Syntax reconnect-time duration;






Description Configure the duration (in seconds) that the charging data function (CDF) must wait

before trying to reconnect to a charging gateway function (CGF) server that was marked

Down earlier.


takes precedence.

Options duration—Duration after which the CDF tries to reconnect to a CGF server that was

previously down.

Range: 60 through 255 seconds. Enter 0 if you do not want to attempt to reconnect to

a peer.

Default: 60 seconds












reporting-level (Trigger Profiles—Online)

Syntax reporting-level {override;(rating-group | service-identifier);

}



Description Configure the default reporting level for the reports from the gateway to the offline

charging gateway and the Online Charging System (OCS). The reporting can be done at

the rating group level or the service identifier level (within a rating group).

Default If you do not include this statement, then the default reporting level is set to rating-group.

Options overrride—Override the reporting level provided by the policy and charging rules function

(PCRF) with the one configured locally.

rating-group—Specify that the gateway reports at the rating group level.

service-identifier—Specify that the gateway reports at the service identifier level.










report-requested-apn

Syntax report-requested-apn;



Description Specify that the broadband gateway includes the requested access point name (APN)

in the Charging Data Records (CDRs) of subscribers attached to the CDR profile. Therefore,

when the APN type is virtual, the broadband gateway includes the requested or virtual

APN in the CDRs.

NOTE: If you do not include the report-requested-apn statement, then, by

default, the broadband gateway includes only the real APN in the CDR. (Forvirtual APNs, the real APN to which the virtual APN is mapped is included inthe CDR.)










requested-service-unit (Trigger Profiles—Online)

Syntax requested-service-unit {always-include;cc-octet-both volume-quota-both;cc-octet-downlink volume-quota-dl;cc-octet-uplink volume-quota-ul;cc-time time-quota;include-quota-holding-time;

}



Description Configure the quotas for the requested service unit. The broadband gateway uses the

configured quotas to do the following:

• Request quota from the Online Charging System (OCS) as a part of the Credit Control

Request-Initial (CCR-Initial) message.

• Report the quota to and request additional quota from the OCS as a part of the

CCR-Update message.

• Report the quota to the OCS as a part of the CCR-Terminate message.











result-code-based-action (Credit Control Failure Handling)

Syntax result-code-based-action {authorization-rejected {blacklist {retry-timer;







}}



Description Configure the actions to be performed based on the Diameter Result-Code attribute-value

pair (AVP) received from the online charging system (OCS), in case of credit control

failure.












send-ccri-on-first-packet (Transport Profiles—Online)

Syntax send-ccri-on-first-packet;



Description Specify that the broadband gateway sends a Credit Control Request-Initial (CCR-I)

message to the Online Charging System (OCS) only on receipt of the first packet for any

rating group of the bearer.

NOTE: If youdonot include the send-ccri-on-first-packet statement, then the

broadband gateway sends the CCR-I message to the OCS to authorize thebearer during bearer establishment. In addition, if thequota-request-on-first-packetstatement isconfigured, thebroadbandgateway

sends the CCR-I message without any Multiple Services Credit Control(MSCC) attribute-value pairs (AVPs) included. MSCC AVPs are used torequest quota for a rating group.

The send-ccri-on-first-packet statement is applicable at the bearer level,

whereas the quota-request-on-first-packet statement is applicable at the

rating group level.








• quota-request-on-first-packet (Transport Profiles—Online) on page 169



service (Service Filter)

Syntax service;

Hierarchy Level [edit firewalls family inet service-filter filter-name term term-name then]

Release Information Statement introduced in Junos OS Mobility Release 12.1W2.

Description Configure the service filter thenaction to trigger service when the match condition is met.

NOTE: For the AoC feature, youmust configure both the deep packetinspection (dpi) and aoc options in the redirect-reasonmatch condition.


interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.


• redirect-reason on page 173





service-context-id (Transport Profiles—Online)

Syntax service-context-id service-context-id;



Description Specify the service context identifier (ID) attribute-value pair (AVP). The broadband

gateway sends this AVP in all Credit Control Request (CCR) messages to the Online

Charging System (OCS).

NOTE: If you do not include this statement, then the default service contextID ([email protected]) is sent in CCRmessages.

Options service-context-id—Service context ID.

Range: 1 through 100 characters










service-mode (Charging Profiles)

Syntax service-mode service-mode-options;






Description Place the charging profile under maintenance mode.

You must put the charging profile in maintenance mode when you have to make any of

the following changes to the existing charging profile configuration:

• Change the CDR profile, transport profile, or the trigger profile associated with this

charging profile

• Change the profile ID configuration

• Delete the charging profile

When a charging profile is in maintenance mode, no new subscribers are accepted for

that charging profile. However, maintenance mode does not become active until no

existing subscriber sessions are using that charging profile and all the corresponding

CDRs have been flushed out. Unless the maintenance mode becomes active, you cannot

modify the charging profile attributes or delete the charging profile.

Use the following commands to help you with maintenance mode tasks:

• To verify that the charging profile has entered active maintenance mode, use one of

the following commands, as applicable:


(P-GW)—showunified-edgeggsn-pgwchargingservice-modegatewaygateway-name

charging-profile profile-name

• For the Serving Gateway (S-GW)—show unified-edge sgw charging service-mode

gateway gateway-name charging-profile profile-name

• To verify that the subscriber count has reached zero, use one of the following

commands, as applicable:

• For the GGSN or P-GW—show unified-edge ggsn-pgw subscribers charging

charging-profile profile-name gateway gateway-name

• For the S-GW—show unified-edge sgw subscribers charging charging-profile

profile-name gateway gateway-name

• To verify that all CDRs for the transport profile referred to by this charging profile have

been flushed out, use one of the following commands, as applicable:



• For the GGSN or P-GW—show unified-edge ggsn-pgw charging transfer status

transport-profile-name profile-name

• For the S-GW—showunified-edgesgwchargingtransferstatustransport-profile-name

profile-name

• To explicitly end any subscriber sessions, use one of the following commands, as

applicable:

• For the GGSN or P-GW—clear unified-edge ggsn-pgw subscribers charging

charging-profile profile-name gateway gateway-name

• For the S-GW—clear unified-edge sgw subscribers charging charging-profile


• To explicitly flush all the CDRs for the transport profile referred to by this charging

profile, use the one of the following commands, as applicable:

• For the GGSN or P-GW—clear unified-edge ggsn-pgw charging cdr

transport-profile-name profile-name gateway name

• For the S-GW—clearunified-edgesgwchargingcdrtransport-profile-nameprofile-name

gateway name

Options service-mode-options—Specify the service mode. Currently, maintenance mode is the

only option supported.






• Changing a Charging Profile

• Mobility Maintenance Mode Overview



service-mode (Transport Profiles)

Syntax service-modemaintenance;

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging transport-profilesprofile-name],

[edit unified-edge gateways sgw gateway-name charging transport-profiles profile-name]




Description Place the respective transport profile under maintenance mode.

To make the following changes to the existing transport profile configuration, you must

put that transport profile in maintenance mode:

• Change the CDR encoding format to comply with a different 3GPP technical

specification release (that is, changing the cdr-release configuration)

• Delete the transport profile

In maintenance mode, no new subscribers are accepted for that transport profile. However,

the maintenance mode does not become active until no existing subscriber sessions are

using that transport profile and all corresponding CDRs have been flushed out. Unless

the maintenance mode becomes active, you cannot modify the above-mentioned

transport profile attributes or delete the transport profile. Use the following commands

to help you with the maintenance mode tasks:

• To verify that the transport profile has entered active maintenance mode, use one of

the following commands, as applicable:

• For the gateway GPRS support node (GGSN) or Packet Data Network Gateway

(P-GW)—showunified-edgeggsn-pgwchargingservice-modegatewaygateway-name

transport-profile profile-name

• For the Serving Gateway (S-GW)—show unified-edge sgw charging service-mode

gateway gateway-name transport-profile profile-name

• To verify that the subscriber count has reached zero, use one of the following


• For the GGSN or P-GW—show unified-edge ggsn-pgw subscribers charging

transport-profile profile-name gateway gateway-name

• For the S-GW—show unified-edge sgw subscribers charging transport-profile


• To verify that all CDRs for the transport profile have been flushed out, use one of the

following commands, as applicable:

• For the GGSN or P-GW—show unified-edge ggsn-pgw charging transfer status




• For the S-GW—showunified-edgesgwchargingtransferstatustransport-profile-name

profile-name

• To explicitly end any subscriber sessions, use one of the following commands, as

applicable:

• For the GGSN or P-GW—clear unified-edge ggsn-pgw subscribers charging

transport-profile profile-name gateway gateway-name

• For the S-GW—clear unified-edge sgw subscribers charging transport-profile


• To explicitly flush all the CDRs for the transport profile, use one of the following


• For the GGSN or P-GW—clear unified-edge ggsn-pgw charging cdr


• For the S-GW—clearunified-edgesgwchargingcdrtransport-profile-nameprofile-name






• Changing a Transport Profile

• Mobility Maintenance Mode Overview



session-failover-not-supported (Transport Profiles—Online)

Syntax session-failover-not-supported;



Description Specify whether online charging sessions should failover to an alternate server or not,

when failure occurs during an ongoing credit control session. The alternate server is

selected based on the configuration in the Diameter profile that is associated with the

transport profile.

The CC-Session-Failover (CCSF) AVP, which is defined in 3GPP specification 32.299,

takes precedence over the session-failover-not-supportedconfiguration on the broadband

gateway. If the Online Charging System (OCS) does not send the CCSF AVP in response

to the CCR-Initial message, then the failover of the online charging session is determined

by the session-failover-not-supported configuration.

By default, the gateway always fails over new online charging sessions to the secondary

OCS. Therefore, the session-failover-not-supported configuration is applicable only in

the case of CCR-Update and CCR-Final messages.

NOTE: If youdonot includethis statement, thenthe failoverofonlinechargingsessions to an alternate server is enabled by default.










sgsn-sgw-change-limit (GGSN or P-GW)

Syntax sgsn-sgw-change-limit value;

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profilesprofile-nameoffline]


Description Configure the maximum number of Serving GPRS Support Node (SGSN) or Serving

Gateway (S-GW) changes that can occur before the CDR is updated and closed.

Options value—Maximum number of SGSN or S-GW changes.

Range: 1 through 5.

Default: 4










single-mscc (Transport Profiles—Online)

Syntax single-mscc;



Description Specify that only one Multiple Services Credit Control (MSCC) attribute-value pair (AVP)

is included in the Credit Control Request (CCR) messages sent from the broadband

gateway to the Online Charging System (OCS).

This configuration is useful in cases where the OCS supports only one MSCC AVP in CCR

messages.

NOTE: If you do not include the single-mscc statement, then, by default, the

broadband gateway includes one or more MSCC AVPs in CCRmessages.










source-interface (GTP Prime)

Syntax source-interface {interface-name;ipv4-address address;

}






Description Configure the name of the local loopback interface and its IPv4 address as the source

interface from which the GTP Prime packets are sent to the charging gateway function

(CGF) servers. This is a mandatory configuration. However, before specifying this

configuration, make sure that the interface has been previously defined.

The following is a sample configuration:

gtpp { source-interface { lo0.0; ipv4-address 10.10.10.10; }}


takes precedence.

Options address—IPv4 address of the local loopback interface from which the GTP Prime packets

are sent. This is a mandatory configuration.

interface-name—Name of the local loopback interface from which the GTP Prime packets

are sent.












switch-back-time

Syntax switch-back-time seconds;






Release 11.4W.

Description The charging data function (CDF) transmits Charging Data Records (CDRs) to the

highest-priority peer. The priority is determined by the peer-order configuration. If for any

reason the highest-priority peer goes down, the CDF transmits the CDRs to the next

high-priority peer and so on. If none of the peers are up, then the CDRs are transmitted

to the local Routing Engine disk, if it is configured. During this transmission, it is possible

that a peer or a peer that is higher in priority might come up. Instead of immediately

switching over the transmission of the CDRs to the peer that recently came up, you can

configure the duration that the CDF must wait to transmit the CDRs to the highest-priority

peer that becomes available after this duration.

NOTE: If all the peers are down, in order not to lose any CDR data, youmightwant to configure the local storage on the Routing Engine disk using thefollowing statement:

• setunified-edgegatewaysggsn-pgwgateway-namechargingtransport-profiles

profile-nameofflinecharging-gatewayspersistent-storage-order local-storage

for the gateway GPRS support node (GGSN) or Packet Data NetworkGateway (P-GW).

• set unified-edge gateways sgw gateway-name charging transport-profiles

profile-nameofflinecharging-gatewayspersistent-storage-order local-storage

for the Serving Gateway (S-GW).

However, even if the Routing Engine disk is not configured for storage, theCDR data is not lost because it gets buffered in the services PICs. ServicesPICscanbufferup toamaximumof2GBofdata, afterwhichacall admissioncontrol (CAC) is triggered.

In themeantime, if one or multiple peers come alive, then CDFwaits for theconfigured switch-back-time duration and routes the CDRs to the

highest-priority peer that is alive after this duration. The CDRs that werestored previously on the Routing Engine disk are not routed to the charginggateway (peer) and remain on the disk. You need to transfer the CDRs usingSSH FTP (SFTP) from the following location on the disk:/opt/mobility/charging/ggsn/final_log.



Options seconds—Time, in seconds, CDF waits before transmitting the CDRs to the highest-priority

peer.


Default: 30 seconds








t3-response (GTP Prime)

Syntax t3-response response-interval;






Description Configure the duration (in seconds) that the charging data function (CDF) must wait

before resending a GTP Prime message when the response to a request has not been

received.


takes precedence.

Options response-interval—Time that the CDF waits before resending a GTP Prime message when

the response to a request has not been received.


Default: 5 seconds












tariff-time-list

Syntax tariff-time-list {[tariff-time];

}

Hierarchy Level [editunified-edgegatewaysggsn-pgwgateway-namecharging trigger-profilesprofile-name],[edit unified-edge gateways sgw gateway-name charging trigger-profiles profile-name]




Description Configure a list of local times (in hh:mm format) at which the tariff changes and Charging

Data Records (CDRs) are generated to reflect the change in tariff. Because you can

configure multiple values, make sure that there is a difference of at least 15 minutes

between these values. You can configure up to a maximum of 24 values.

Any change to the existing configuration applies to both existing and new subscriber

sessions.

Options tariff-time—Local time at which to generate a CDR, in hh:mm format, when the tariff

changes.











time-limit

Syntax time-limit value;






Description Configure the duration, in seconds, (since the previous trigger) after which the Charging

Data Record (CDR) is updated with the uplink and downlink bytes transmitted in this

duration and is closed. For example, if the duration is set to 3600 seconds, then the total

resource utilization for the past hour is added to the CDR and the CDR is closed.



Options value—Duration in seconds.


Default: 0, indicates that no time limit is set.










traceoptions (Charging)

Syntax traceoptions {file {file-name;files number;size size(no-world-readable | world-readable);


}





online and tpm options introduced in Junos OS Mobility Release 12.1W.

Description Specify tracing options for charging.

Options file file-name—Name of the file to receive the output of the tracing operation. The router

appends -msfpc#pic# to the filename and places the file in the /var/log directory.

For example, if you configured the filename as smd, then the actual log filename on

the router is smd-ms50, where ms stands for multiservices card, and 5 and 0 are the

FPC and PIC slot numbers.


files number—(Optional) Maximum number of trace files. When a trace file named

trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and

so on, until the maximum number of trace files is reached. Then the oldest trace file

is overwritten.

Range: 2 through 1000 files

Default: 3 files

flag flag—Specify which operations are to be traced. To specify more than one operation,

include multiple flag statements.

CAUTION: Youmight want to enable traceoptions only when you want todebug specific charging operations. Enabling the traceoptions flagsmighthave an impact on the system performance.

• all—Trace all operations of all charging submodules.

• cdr-encoding—Trace ASN1 encoding of the CDRs.



• client-fsm—Trace the charging-specific finite state machine (FSM) in the application

framework (mobile-smd).

• config—Trace configuration events on both daemons (chargemand and mobile-smd).

• fsm—Trace FSM.

• general—Trace general events that do not fit in any specific traces, such as errors in

chargemand.

• group-fsm—Trace the transport-profile FSM in chargemand.

• init—Trace initialization events.

• ipc—Trace the interprocess communication (IPC) messages betweenmobile-smd and

chargemand.

• online—Trace the Gy module.

• path-management—Trace path management operations within the path manager

module within chargemand.

• resource—Trace resources, such as memory, counters, and so on.

• timers—Trace resources associated with timer processing.

• tpm—Trace the online processing module.

• transport—Trace transport-profile-level operations in chargemand.

• triggers—Trace trigger-profile-related operations used by the mobile-smd charging

module.

level—Level of tracing to perform. You can specify any of the following levels:

• all—Match all levels.

• critical—Match error conditions.

• error—Match error conditions.

• info—Match informational messages.

• notice—Match conditions that must be handled specially.

• verbose—Match verbose messages.

• warning—Match warning messages.

no-remote-trace—(Optional) Disable remote tracing.

no-world-readable—(Optional) Disable unrestricted file access.



size size—(Optional) Maximum size of each trace file, in kilobytes (KB) or megabytes

(MB). When a trace file named trace-file reaches this size, it is renamed trace-file.0.

When the trace-file again reaches its maximum size, trace-file.0 is renamed trace-file.1

and trace-file is renamed trace-file.0. This renaming scheme continues until the

maximum number of trace files is reached. Then, the oldest trace file is overwritten.

If you specify a maximum number of files, you must also specify a maximum file size

with the size option.

Syntax: xk to specify KB, xm to specify MB, or xg to specify GB.

Range: 10,240 through 1,073,741,824 bytes

Default: 128 KB

world-readable—(Optional) Enable unrestricted file access.


trace and unified-edge—To view this statement in the configuration.

trace-control and unified-edge-control—To add this statement to the configuration.







traceoptions (Local Persistent Storage)

Syntax traceoptions {file file-name <files number> <match regular-expression> <no-world-readable |world-readable> <size size>;


}






11.4W.

Description Specify tracing options related to the storage of Charging Data Records (CDRs) on the

local Routing Engine disk.

Options file filename—Name of the file to receive the output of the tracing operation.


files number—(Optional) Maximum number of trace files. When a trace file named

trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and

so on, until the maximum number of trace files is reached. Then the oldest trace file

is overwritten.

Range: 2 through 1000 files

Default: 3 files

flag flag—Specify which operations are to be traced. To specify more than one operation,

include multiple flag statements.

CAUTION: Youmay want to enable traceoptions only when you want todebug specific charging operations. Enabling the traceoption flagsmighthave an impact on the system performance.

• all—Trace all operations.

• connection—Trace the connection establishment between Routing Engine and all

services PICs for CDR file backup.

• file-operations—Trace all file open, write, and close operations.

• general—Trace general operations.



• journaling—Trace journaling operations. Journaling creates a log for each file-write

operation, which helps to sanitize the CDR data in temporary log files after a reboot.

• mirror—Trace mirroring operations. Mirroring enables you to synchronize the CDR file

information onto backup.

level—Level of tracing to perform. You can specify any of the following levels:

• all—Match all levels.

• critical—Match critical conditions.

• error—Match error conditions.

• info—Match informational messages.

• notice—Match conditions that must be handled specially.

• verbose—Match verbose messages.

• warning—Match warning messages.

match regex—(Optional) Refine the output to include lines that contain the regular

expression (regex).

no-remote-trace—(Optional) Disable remote tracing.

no-world-readable—(Optional) Disable unrestricted file access.

size size—(Optional) Maximum size of each trace file, in kilobytes (KB) or megabytes

(MB). When a trace file named trace-file reaches this size, it is renamed trace-file.0.

When the trace-file again reaches its maximum size, trace-file.0 is renamed trace-file.1

and trace-file is renamed trace-file.0. This renaming scheme continues until the

maximum number of trace files is reached. Then, the oldest trace file is overwritten.

If you specify a maximum number of files, you must also specify a maximum file size

with the size option.

Syntax: xk to specify KB, xm to specify MB, or xg to specify GB.

Range: 10,240 through 1,073,741,824 bytes

Default: 128 KB

world-readable—(Optional) Enable unrestricted file access.


trace and unified-edge—To view this statement in the configuration.

trace-control and unified-edge-control—To add this statement to the configuration.






transport-profile (Charging Profiles)

Syntax transport-profile profile-name;






Description Associate a previously configured transport profile with a charging profile. You must

associate a transport profile with a charging profile.

When a subscriber session is created, the subscriber is bound to a charging profile. The

transport profile configuration associated with this charging profile determines the

transport of the CDRs generated for this subscriber from the charging data function (CDF)

to the external charging gateway function (CGF) servers, the local Routing Engine disk,

or both the CGF servers and local Routing Engine disk.

Any modification to the existing configuration of this attribute must be done only when

the charging profile with which it is associated is under active maintenance mode. Use

one of the following commands, as applicable, to bring the charging profile under

maintenance mode:


(P-GW)—setunified-edgegatewaysggsn-pgwgateway-namechargingcharging-profiles

profile-name service-modemaintenance

• For the Serving Gateway (S-GW)—set unified-edge gateways sgw gateway-name

charging charging-profiles profile-name service-modemaintenance

TIP: If the profile is not already defined, use one of the following commands,as applicable, to define a new transport profile:

• GGSNorP-GW—setunified-edgegatewaysggsn-pgwgateway-namecharging

transport-profiles profile-name

• S-GW—set unified-edge gateways sgw gateway-name charging

transport-profiles profile-name

Options profile-name—Name of the previously configured transport profile to be associated with

the charging profile.






transport-profiles

Syntax transport-profiles profile-name {description string;offline {charging-function-name function-name;{charging-gateways {cdr-aggregation-limit value;cdr-release (r7 | r8 | r9 | r99);mtu value;peer-order {[peer charging-gateway-peer-name];



}container-limit value;sgsn-sgw-change-limit value; #P-GW only

}online { #P-GW onlyall-rgs-on-termination;charging-function-name function-name;diameter-profile profile-name;no-mscc-in-ccrt;quota-request-on-first-packetsend-ccri-on-first-packetservice-context-id service-context-id;session-failover-not-supported;single-mscc;tx-timeout timeout;


}





Description Configure a transport profile, which determines how the offline Charging Data Records

(CDRs) and online messages are transported. You must configure a transport profile for

the broadband gateway.

NOTE: You can configure up to amaximum of eight transport profiles.

For offline charging, the following are applicable:



• CDRs are transported from the charging data function (CDF) to a storage resource,

which can be external charging gateway function (CGF) servers or the local Routing

Engine disk, or both.

• Transport parameters for offline CDRs can be configured using the charging-gateways

statement.

• The configured charging-function-name is used to select the transport profile.

For online charging, the following are applicable:

• Online messages are transported to the online charging system (OCS).

• Transport parameters for online messages can be configured using theonlinestatement.

• The configured charging-collection-function is used to select the transport profile.

Options profile-name—Name of the transport profile.















transport-protocol (GTP Prime)

Syntax transport-protocol (tcp | udp);






Description Configure the transport protocol for transmitting the GTP Prime packets from the charging

data function (CDF) to the charging gateway function (CGF) server, which can be either

GTP Prime over UDP or GTP Prime over TCP.


takes precedence.

Options tcp—Transport protocol used is TCP.

udp—Transport protocol used is UDP.












trigger-profile (Charging Profiles)

Syntax trigger-profile profile-name {rating-group [value];

}






Description Associate a previously configured trigger profile with a charging profile.

You can associate more than one trigger profile with a charging profile. For each trigger

profile that you configure, you can specify one or more rating groups to be associated

with that trigger profile. When more than one trigger profile is configured, the broadband

gateway uses the rating group identifier to select the trigger profile to be associated with

the charging profile.

NOTE: If you do not configure a trigger profile, then the gateway uses thedefault trigger profile.

When a subscriber session is created, the subscriber is bound to a charging profile and

the trigger profile configuration associated with this profile determines the events that

result in the creation of a CDR, the addition of a container to a CDR, and the closure of a

CDR.

TIP: If the profile is not already defined, use one of the following commands,as applicable, to define a new trigger profile:

• For the Gateway GPRS Support Node (GGSN) or Packet Data NetworkGateway (P-GW)—set unified-edge gateways ggsn-pgw gateway-name

charging trigger-profiles profile-name

• For the Serving Gateway (S-GW)—set unified-edge gateways sgw

gateway-name charging trigger-profiles profile-name

Options profile-name—Name of the previously configured trigger profile to be associated with the

charging profile.






trigger-profiles (GGSN or P-GW)

Syntax trigger-profiles profile-name {charging-method (both | none | offline | online);description string;offline {exclude {dcca-events;ms-timezone-change;plmn-change;qos-change;rat-change;sgsn-sgw-change;user-location-change;









}



user-unknown {convert-to-offline {grant-grace-quota;






}quota-validity-time time-in-seconds;reporting-level {override;(rating-group | service-identifier);

}requested-service-unit {always-include;cc-octet-both volume-quota-both;cc-octet-downlink volume-quota-dl;cc-octet-uplink volume-quota-ul;cc-time time-quota;


}}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charging]




Description Configure a trigger profile, which determines the events that trigger the creation of a

Charging Data Record (CDR), the addition of a container to a CDR, and the closure of a

CDR.

You can configure up to a maximum of 16 trigger profiles.

NOTE: If you do not configure a trigger profile, then the broadband gatewayuses the default trigger profile.

Options profile-name—Name of the trigger profile.














tx-timeout (Transport Profiles—Online)

Syntax tx-timeout timeout;



Description Specify the time (in seconds) that the broadband gateway waits for a response from

the online charging system (OCS) before timing out.

The Tx timer is started when the Credit Control Request (CCR) is sent and stopped when

the Credit Control Acknowledgement (CCA) is received. When the Tx timer expires for

CCR-Update messages, the Credit-Control-Failure-Handling (CCFH) attribute-value pair

(AVP) is applied, if it was received in the CCR-Initial message.

If the CCFH AVP is not received in the CCR-Initial message, or if the Tx timer expires for

the CCR-Initial message, then thecc-failure-handlingconfiguration at the [editunified-edge

gateways ggsn-pgw gateway-name charging trigger-profiles profile-name online] is

applicable.

Options timeout—Timeout, in seconds.

Default: 5 seconds











update-request (Credit Control Failure Handling)

Syntax update-request {convert-to-offline {grant-grace-quota;


}



Description Configure the actions to be carried out by the broadband gateway when the Credit Control

Request-Update fails.

The gateway uses the credit control failure parameters provided by the Online Charging

System (OCS) to determine the actions to be performed in case of credit control failure.

If OCS does not provide the parameters, then the gateway uses the parameters configured

using the update-request statement. If this statement has not been included, then the

session is terminated by default.











user-name (Local Persistent Storage)

Syntax user-name string;






11.4W.

Description Restrict access to the Charging Data Record (CDR) files to a specific user.

In addition to the non-root user who is authorized using this statement, the root user

always has access permissions.

Options string—Username.











user-unknown (Credit Control Failure Handling)

Syntax user-unknown {convert-to-offline {grant-grace-quota;


}



Description Specify that in case of credit control failure, if the result code is Diameter User Unknown,

then the gateway will terminate the session.

If offline charging is enabled, then offline charging will continue to be applied to

subscribers. If offline charging is disabled, then the convert-to-offline statement can be

used to enable offline charging for subscribers, and the usage quota can be limited using

the grant-grace-quota statement.

Alternatively, online charging can be disabled using thedisable-online-charging statement.

If offline charging is also disabled, then no charging is applied to the subscriber.











version (GTP Prime)

Syntax version (v0 | v1 | v2);






Description Configure the latest GTP Prime version that is supported on the configured local loopback

source interface’s IP address from which the GTP Prime packets are sent to the charging

gateway function (CGF) server. The possible values are: v0, v1, or v2.


takes precedence.

Options v0—GTP Prime version supported is v0.

v1—GTP Prime version supported is v1.

v2—GTP Prime version supported is v2.












volume-limit

Syntax volume-limit {value;direction (both | uplink);

}






Description Configure the volume of data, in bytes, that is transmitted (since the previous trigger)

before the Charging Data Record (CDR) is updated with the transmitted bytes and is

closed. In addition, you can specify whether the maximum volume of data transmitted

includes the data transmitted in both the uplink and downlink directions, or only in the

uplink direction.



Default If you do not include the volume-limit statement, the volume limit trigger is disabled.

Options value—Maximum volume of data transmitted, in bytes, after which the CDR is updated

and closed.

Range: 1 byte through 4 GB











watermark-level-1

Syntax watermark-level-1 {notification-level (both | snmp-alarm | syslog);percentage value;

}

Hierarchy Level [edit unified-edge gateways ggsn-pgw gateway-name charginglocal-persistent-storage-options disk-space-policy],

[edit unified-edge gateways sgw gateway-name charging local-persistent-storage-optionsdisk-space-policy]



local-persistent-storage-options disk-space-policy] hierarchy level introduced in Junos


Description Configure the percentage of Routing Engine disk space to be used for storage and the

action to be taken when this limit is reached, such as raise SNMP alarms, record the alert

information in the system logs, or both. You can then take appropriate measures to

prevent any loss of Charging Data Record (CDR) data.

Options notification-level (both | snmp-alarm | syslog)—Specify whether you want to raise SNMP

alarms, log information on the system logs, or both, when the watermark level is

reached.

• both—Log the alert information on system log files and also raise an SNMP alarm.

• snmp-alarm—Raise an SNMP alarm.

• syslog—Log the alert information on system log files.

Default: syslog

percentage value—Percentage of Routing Engine disk space to be used for storage after

which you get an alert (if it is configured). Entering 0 disables the checking for the

watermark level.

Default: 70 percent of the Routing Engine disk space





• disk-space-policy on page 121





watermark-level-2


}







Description Configure the percentage of Routing Engine disk space to be used for storage and also

the action to be taken when this limit is reached, such as raise SNMP alarms, record the

alert information in the system logs, or both. You can then take appropriate measures

to prevent any loss of Charging Data Record (CDR) data.


alarms, log information on the system logs, or both when the watermark level is

reached.

• both—Log the alert information on system log files and raise an SNMP alarm.



Default: syslog



watermark level.











watermark-level-3


}







Description Configure the percentage of Routing Engine disk space to be used for storage and also

the action to be taken when this limit is reached, such as raise SNMP alarms, record the

alert information in the system logs, or both.

When this watermark level is reached, the charging daemon stops writing the Charging

Data Records (CDRs) to the local Routing Engine disk till the CDR storage space is restored

by transferring the files using SSH FTP (SFTP) and deleting the files from the CDR log

directory. However, the data is not immediately lost because the services PICs buffer up

to 2 GB of data.


alarms, log information on the system logs, or both when the watermark level is

reached.

• both—Log the alert information on system log files and also raise an SNMP alarm.



Default: syslog



watermark level.











world-readable (Local Persistent Storage)

Syntax world-readable;






11.4W.

Description Allow all users to have read permissions on the Charging Data Record (CDR) files. By

default, this is disabled.










PART 3

Administration

• Monitoring the Charging Configuration on page 221

• Operational Commands on page 223


CHAPTER 6

Monitoring the Charging Configuration

• Verifying and Managing the Charging Configuration on page 221

Verifying andManaging the Charging Configuration

Purpose Display or clear information about the charging configuration.

NOTE: This topic lists commands that are applicable only to the GatewayGPRS Support Node (GGSN) or Packet Data Network Gateway (P-GW).However, you can display or clear information about the chargingconfigurationfor theServingGateway(S-GW).Replacetheggsn-pgwkeyword

in the commands belowwith sgw to run the corresponding commands for

theS-GW; forexample,showunified-edgesgwcharging local-persistent-storage

statistics displays information about the local persistent storage statistics

on the S-GW.

Action To display information about the local persistent storage statistics:•

user@host> show unified-edge ggsn-pgw charging local-persistent-storage statistics

• To display information about the path management message statistics:

user@host> show unified-edge ggsn-pgw charging path statistics

• To display information about the status of the configured peers:

user@host> show unified-edge ggsn-pgw charging path status

• To display information about the transfer statistics for configured transport profiles:

user@host> show unified-edge ggsn-pgw charging transfer statistics

• To display information about the transfer status for configured transport profiles:

user@host> show unified-edge ggsn-pgw charging transfer status

• To clear the locally-stored CDRs:

user@host> clear unified-edge ggsn-pgw charging cdr

• To clear the local persistent storage statistics:

user@host> clear unified-edge ggsn-pgw charging local-persistent-storage statistics


• To clear the path management message statistics:

user@host> clear unified-edge ggsn-pgw charging path statistics

• To clear the transfer statistics:

user@host> clear unified-edge ggsn-pgw charging transfer statistics











CHAPTER 7

Operational Commands


clear unified-edge ggsn-pgw charging cdr

Syntax clear unified-edge ggsn-pgw charging cdr gateway name<transport-profile-name profile-name>

Release Information Command introduced in Junos OS Mobility Release 11.2W.

Description Clear the Charging Data Records (CDRs) from the services PICs for the configured

transport profiles on the specified gateway GPRS support node (GGSN) or Packet Data


Options gateway gateway-name—Clear CDRs from the services PICs for the specified GGSN or

P-GW.

transport-profile-name profile-name—(Optional) Clear CDRs from the services PICs only

for the specified transport profile.


clear, unified-edge


show unified-edge ggsn-pgw charging transfer status on page 256•

List of Sample Output clear unified-edge ggsn-pgw charging cdr gateway name on page 224

Output Fields No message is displayed on successful execution of this command; otherwise an error

message is displayed.

Sample Output

clear unified-edgeggsn-pgwchargingcdrgateway name

user@host> clear unified-edge ggsn-pgw charging cdr gateway PGW



clear unified-edge ggsn-pgw charging cdr wfa

Syntax clear unified-edge ggsn-pgw charging cdr wfa gatway-name name<transport-profile-name profile-name>


Description Clear from the services PICs the Charging Data Records (CDRs) that have not received

an acknowledgement from the charging gateway function (CGF), the Routing Engine, or

both.

Options gateway gateway-name—Clear the unacknowledged CDRs from the services PICs for the

specified GGSN or P-GW.

transport-profile-name profile-name—(Optional) Clear the unacknowledged CDRs from

the services PICs only for the specified transport profile.


clear, unified-edge


show unified-edge ggsn-pgw charging transfer status on page 256•

List of Sample Output clear unified-edge ggsn-pgw charging cdr wfa gateway name on page 225

Output Fields No message is displayed on successful execution of this command; otherwise an error

message is displayed.

Sample Output

clear unified-edgeggsn-pgwchargingcdrwfa gateway name

user@host> clear unified-edge ggsn-pgw charging cdr wfa gateway PGW


Chapter 7: Operational Commands

clear unified-edge ggsn-pgw charging local-persistent-storage statistics

Syntax clear unified-edge ggsn-pgw charging local-persistent-storage statistics gatewaygateway-name


Description Clear the storage statistics of the Charging Data Record (CDR) files on the local Routing

Engine disk on the specified Gateway GPRS Support Node (GGSN) or Packet Data


Options gateway gateway-name—Clear the storage statistics for the specified gateway.


clear, unified-edge


showunified-edgeggsn-pgwcharging local-persistent-storagestatisticsonpage236•

List of Sample Output clear unified-edge ggsn-pgw charging local-persistent-storage statistics gatewayname on page 226

Output Fields When you enter this command, you are provided feedback on the status of your request.

Sample Output

clear unified-edgeggsn-pgw charging

user@host> clear unified-edge ggsn-pgw charging local-persistent-storage statistics gatewayPGWCleared charging local persistent storage statisticslocal-persistent-storage

statistics gatewayname



clear unified-edge ggsn-pgw charging path statistics

Syntax clear unified-edge ggsn-pgw charging path statistics gateway gateway-name<fpc-slot slot-number pic-slot slot-number><gtpp-peer-addr ipv4-address><gtpp-peer-name peer-name>


Description Clear the path management message statistics between the charging data function

(CDF) and the charging gateway function (CGF) servers for the specified gateway GPRS

support node (GGSN) or Packet Data Network Gateway (P-GW).

Options gatewaygateway-name—Clear the path management message statistics for the specified

GGSN or P-GW.

fpc-slot slot-number pic-slot slot-number—(Optional) Clear the path management

message statistics only for the specified FPC slot number and PIC slot number.

gtpp-peer-addr ipv4-address—(Optional) Clear the path management message statistics

only for the GTP Prime peer with the specified IPv4 address.

gtpp-peer-namepeer-name—(Optional) Clear the path management message statistics

only for the GTP Prime peer with the specified name.


clear, unified-edge


show unified-edge ggsn-pgw charging path statistics on page 242•

List of Sample Output clear unified-edge ggsn-pgw charging path statistics gateway name on page 227


Sample Output


user@host> clear unified-edge ggsn-pgw charging path statistics gateway PGWCleared charging path statistics

path statisticsgateway name



clear unified-edge ggsn-pgw charging transfer statistics

Syntax clear unified-edge ggsn-pgw charging transfer statistics gateway gateway-name<fpc-slot slot-number pic-slot slot-number><transport-profile-name profile-name>


Description Clear the charging transfer statistics on one or more gateway GPRS support nodes

(GGSNs) or Packet Data Network Gateways (P-GWs). If a GGSN or P-GW is not specified,

then charging transfer statistics for all GGSNs or P-GWs are cleared.

Options gateway gateway-name—Clear the transfer statistics for the specified GGSN or P-GW.

fpc-slot slot-number pic-slot slot-number—(Optional) Clear the transfer statistics for the

configured transport profiles for the specified FPC slot number and PIC slot number.

transport-profile-name profile-name—(Optional) Clear the transfer statistics only for the

specified transport profile.


clear, unified-edge


show unified-edge ggsn-pgw charging transfer statistics on page 253•

List of Sample Output clear unified-edge ggsn-pgw charging transfer statistics gateway name on page 228


Sample Output


user@host> clear unified-edge ggsn-pgw charging transfer statistics gateway PGWCleared charging transfer statistics

transfer statisticsgateway name



request system storage unified-edge chargingmedia start

Syntax request system storage unified-edge chargingmedia start<re0 | re1>


Description Enable use of local persistent storage for Charging Data Records (CDRs).

Options re0 | re1—(Optional) On routers that support dual or redundant Routing Engines, use the

disk on the Routing Engine in slot 0 (re0) or Routing Engine in slot 1 (re1).


maintenance


request system storage unified-edgemedia prepare on page 232•

• request system storage unified-edge chargingmedia stop on page 230

• showunified-edgeggsn-pgwcharging local-persistent-storagestatisticsonpage236

List of Sample Output request system storage unified-edge chargingmedia start on page 229

Output Fields When you enter this command, there is no output for success but an error displays if the

command fails to complete.

Sample Output

request systemstorage unified-edgechargingmedia start




request system storage unified-edge chargingmedia stop

Syntax request system storage unified-edge chargingmedia stop<re0 | re1>


Description Disable use of local persistent storage for Charging Data Records (CDRs).

Options re0 | re1—(Optional) On routers that support dual or redundant Routing Engines, use the

disk on the Routing Engine in slot 0 (re0) or Routing Engine in slot 1 (re1).


maintenance


request system storage unified-edgemedia eject on page 231•

• request system storage unified-edge chargingmedia start on page 229

List of Sample Output request system storage unified-edge chargingmedia stop on page 230

Output Fields When you enter this command, there is no output for success but an error displays if the

command fails to complete.

Sample Output

request systemstorage unified-edgechargingmedia stop

user@host> request system storage unified-edge chargingmedia stop



request system storage unified-edgemedia eject

Syntax request system storage unified-edgemedia eject<re0 | re1>


Description Prepare the Solid State Disk (SSD) for removal from the Routing Engine. This command

unmounts the SSD from /opt/mobility.

Options re0 | re1—(Optional) On routers that support dual or redundant Routing Engines, prepare

the disk on the Routing Engine in slot 0 (re0) or Routing Engine in slot 1 (re1).


maintenance


request system storage unified-edge chargingmedia stop on page 230•

List of Sample Output request system storage unified-edgemedia eject on page 231


Sample Output

request systemstorage unified-edgemedia eject

user@host> request system storage unified-edgemedia ejectMedia successfully ejected



request system storage unified-edgemedia prepare

Syntax request system storage unified-edgemedia prepare<no-format><re0 | re1>


Description Prepare the Solid State Disk (SSD) on the Routing Engine for local persistent storage of

Charging Data Records (CDRs). This command formats the SSD and mounts it to

/opt/mobility.


Options no-format—(Optional) Do not format the existing content on the SSD when preparing

the disk on the Routing Engine.

re0 | re1—(Optional) On routers that support dual or redundant Routing Engines, prepare

the disk on the Routing Engine in slot 0 (re0) or Routing Engine in slot 1 (re1).


maintenance


request system storage unified-edge chargingmedia start on page 229•

• showunified-edgeggsn-pgwcharging local-persistent-storagestatisticsonpage236

List of Sample Output request system storage unified-edgemedia prepare on page 232


Sample Output

request systemstorage unified-edgemedia prepare

user@host> request system storage unified-edgemedia prepareCreating filesystemMounting mediaMedia successfully prepared



show unified-edge ggsn-pgw charging global statistics

Syntax show unified-edge ggsn-pgw charging global statistics<brief | detail><fpc-slot slot-number pic-slot slot-number><gateway gateway-name>


Description Display the global statistics for charging for one or more Gateway GPRS Support Nodes

(GGSNs) or Packet Data Network Gateways (P-GWs). If a GGSN or P-GW is not specified,

then the statistics for all GGSNs and P-GWs are displayed.

Options none—(Same as brief) Display the global statistics for charging, in brief.

brief | detail—(Optional) Display the specified level of output.

The brief option displays the statistics per GGSN or P-GW for all services PICs. The

detail option displays the statistics per GGSN or P-GW for each services PIC.

fpc-slot slot-number pic-slot slot-number—(Optional) Display the global statistics for

charging only for the specified FPC slot number and PIC slot number.

gateway gateway-name—(Optional) Display the global statistics for charging for the



view


showunified-edgeggsn-pgwcharging local-persistent-storagestatisticsonpage236•

• show unified-edge ggsn-pgw charging path statistics on page 242

• show unified-edge ggsn-pgw charging transfer statistics on page 253

List of Sample Output show unified-edge ggsn-pgw charging global statistics brief on page 235show unified-edge ggsn-pgw charging global statistics detail on page 235

Output Fields Table 7 on page 233 lists the output fields for the show unified-edge ggsn-pgw charging

global statistics command. Output fields are listed in the approximate order in which

they appear.

Table 7: show unified-edge sgw charging global statistics Output Fields

Level of OutputField DescriptionField Name

All levels

none

Name of the GGSN or P-GW.Gateway

detailFPC slot number and PIC slot number for which the statisticsare displayed.

FPC/PIC



Table 7: show unified-edge sgw charging global statistics Output Fields (continued)


All levels

none

Number of CDR send errors. This counter indicates an internalerror while closing the CDR.

CDR Send Errors

All levels

none

Number of CDR encoding failures. For example, if the buffer isinsufficient then the CDR encoding does not take place.

CDR Encode Errors

All levels

none

Number of CDR allocation failures. For example, if there isinsufficient memory then the CDR allocation can fail.

CDRAlloc Failures

All levels

none

Number of internal failures pertaining to charging containers.Container Failures

All levels

none

Number of bearers for which charging is enabled.Charging Bearers Created

All levels

none

Number of charging bearers destroyed.Charging Bearers Destroyed



Sample Output

show unified-edgeggsn-pgw chargingglobal statistics brief

user@host> show unified-edge ggsn-pgw charging global statistics briefGateway: PGW Charging Global Statistics

CDR Send Errors : 8 CDR Encode Errors : 0 CDR Alloc Failures : 0 Container Failures : 0 Charging Bearers Created : 100 Charging Bearers Destroyed : 4

show unified-edgeggsn-pgw chargingglobal statistics detail

user@host> show unified-edge ggsn-pgw charging global statistics detailGateway: PGW Charging Global Statistics FPC/PIC: 1/0 CDR Send Errors : 4 CDR Encode Errors : 0 CDR Alloc Failures : 0 Container Failures : 0 Charging Bearers Created : 50 Charging Bearers Destroyed : 2

FPC/PIC: 3/0 CDR Send Errors : 4 CDR Encode Errors : 0 CDR Alloc Failures : 0 Container Failures : 0 Charging Bearers Created : 50 Charging Bearers Destroyed : 2



show unified-edge ggsn-pgw charging local-persistent-storage statistics

Syntax show unified-edge ggsn-pgw charging local-persistent-storage statistics<gateway gateway-name>


gateway option introduced in Junos OS Mobility Release 11.4W.

Description Display the storage statistics of the Charging Data Record (CDR) files on the local Routing

Engine disk for one or more Gateway GPRS Support Nodes (GGSNs) or Packet Data

Network Gateways (P-GWs). If a GGSN or P-GW is not specified, then the status for all

GGSNs and P-GWs is displayed.

Options gatewaygateway-name—(Optional) Display the storage statistics for the specified GGSN

or P-GW.


view


clearunified-edgeggsn-pgwcharging local-persistent-storagestatisticsonpage226•

List of Sample Output showunified-edgeggsn-pgwcharging local-persistent-storagestatisticsonpage240


local-persistent-storage statistics command. Output fields are listed in the approximate

order in which they appear.

Table8: showunified-edgeggsn-pgwcharging local-persistent-storagestatisticsOutputFields

Field DescriptionField Name

Total number of batch messages sent from services PICs to the Routing Engine disk.The CDRs generated in services PICs are sent to the local Routing Engine disk as batchmessages.

BatchMessages received

Total number of responses sent for the received batch messages.Batch Responses sent

Total number of invalid batch messages sent from services PICs to the Routing Enginedisk.

Invalid Messages received

Total number of temporary CDR files opened on the Routing Engine disk.

These files are closed and copied from the temporary location to a final location(/opt/mobility/charging/ggsn/final_log) within the same Routing Engine disk, fromwhere they can be transferred using SSH FTP (SFTP). A file is closed when the filesize, file age, or the maximum number of CDRs added to the file reaches the configuredlimit (or the default limit, when no limit is configured).

Number of temp log files opened



Table 8: show unified-edge ggsn-pgw charging local-persistent-storage statistics OutputFields (continued)


Total number of open journal files. Journal files are used to remove any unfinished filewrites from the temporary log files if a daemon or router crash interrupts the kernelfile write. When the daemon or router come back up, the journal log files are read toensure that the contents of the temporary log file are sane. If there is any unfinishedCDR data, the temporary log file is truncated to the last-known successful file write.For each temporary log CDR file, a separate journal file is opened.

Number of journal files opened

Total number of journal files closed.Number of journal files closed

Total number of temporary CDR log files closed.

Authorized users can use SFTP to transfer these files from the/opt/mobility/charging/ggsn/final_log location.

Number of CDR log files closed

Total number of temporary CDR log files closed because the age of the files reachedthe configured limit (or the default limit, when no limit is configured).

The default value for the file age is 120 minutes.

Number of CDR files closed due tofile-age

Total number of number of temporary CDR log files closed because the size of thefiles reached the configured limit (or the default limit, when no limit is configured).

The default file size is 10 MB.

Number of CDR files closed due tofile-size

Total number of temporary CDR log files closed because the maximum number ofCDRs added to the files reached the configured limit.

There is no default limit.

Number of CDR files closed due tocdr-count

Total number of abnormal temporary CDR log file closures. This counter is incrementedwhen the charging daemon comes up after a system reboot or crash and temporaryCDR log file closures are triggered.

Abnormal file closures

Total number of normal temporary CDR log file closures. This counter is incrementedwhen changes in the configuration, such as a file format change, trigger temporaryCDR log file closures.

Normal file closures

Total number of closed temporary CDR log files that are compliant with the formatspecified in the 32297 technical specification release.

Number of CDR log files closed inTS_32_297 format

Total number of closed temporary CDR log files that are in the raw ASN.1 format.Number of CDR log files closed in rawasn1 format

Total number of CDRs backed up to the standby Routing Engine.Total number of CDRs backed up





Total number of messages sent by the Routing Engine to the services PICs to indicatethat its disk is full and unable to accept any more charging data.

You can use SFTP to transfer the files from the /opt/mobility/charging/ggsn/final_loglocation to free disk space, or remove the disk and copy the files.

You can remove the disk by issuing the following commands in this order:

• request system storage unified-edge chargingmedia stop

• request system storage unified-edgemedia eject

Disk Full messages sent

Total number of disk full resolve messages sent. When the disk space is freed, theRouting Engine sends messages to the services PICs indicating that it can receivecharging data.

Disk Full resolvemessages sent

Number of asynchronous I/O requests written. This counter is incremented once forevery write operation into the temporary log CDR file.

Number of async IO reqs written

Indicates whether disk space is available for storage. The possible values are:

• DISK_AVAILABLE

• DISK_AT_WATERMARK_LEVEL1



• DISK_OFFLINE—Indicates that a disk is not present or the request system storageunified-edge chargingmedia stop command has been issued.

• DISK_OFFLINE_PENDING—Indicates whether any CDRs are being written or mirroredon the backup Routing Engine. This interim status message is displayed after therequest systemstorageunified-edgechargingmedia stop command has been issuedbut before the disk goes offline.

Disk space status

Indicates the percentage of the total Routing Engine disk space configured for storage.By default, watermark level 1 is set to 70 percent of the total disk space.

When this limit is reached, an alert (if configured) is sent and you can take correctivemeasures to free the disk space.

Watermark level1 at (MB)


When this limit is reached, an alert (if configured) is sent and you can take correctivemeasures to free the disk space.



When this limit is reached, an alert (if configured) is sent and you can take correctivemeasures to free the disk space. If an alert is not configured, the services PICs stopsending the charging data to the Routing Engine disk and you must transfer the filesusing SFTP to free the disk space. However, this data is not lost because it is bufferedin the services PICs. The services PICs can buffer up to a maximum of 2 GB of data,after which a Call Admission Control (CAC) is triggered.






Temporary CDR log file Statistics

NOTE: The information about temporary CDR log files is displayed only if temporary CDR log files are currently open.

Name of the temporary CDR log file.File Name

Name of the journal file.Journal file name

Total number of CDRs that have been currently added to the temporary CDR log file.Current number of CDRs

Current size, in bytes, of the temporary CDR log file.Current file size (bytes)

Configured duration, in minutes, after which the temporary CDR log file is closed. Ifthis parameter is not configured, then the default value is displayed.

File age trigger (mins)

Configured size, in bytes, that the temporary CDR log file can reach after which it isclosed. If this parameter is not configured, then the default value is displayed.

File size trigger (bytes)

Configured maximum number of CDRs that can be added to the temporary CDR logfile, after which it is closed. If this parameter is not configured, then the default valueis displayed.

CDR count trigger

Global Statistics

Total number of messages sent by the Routing Engine to the services PICs to indicatethat its disk is offline or is not mounted, and that it is unable to accept any morecharging data.

You can configure the disk (storage media) to store charging data by issuing thesecommands:

• request system storage unified-edgemedia prepare

• request system storage unified-edge chargingmedia start

Disk Offlinemessages sent

When the disk is prepared and mounted, the Routing Engine sends messages to theservices PICs to indicate that it can now receive charging data. This field indicates thetotal number of these messages sent.

Disk Availablemessages sent

Total number of CDR files stored on the local Routing Engine disk.Number of CDR storage files on disk

Storage space, in MB, that is currently being used.Current storage space in use (MB)

Total free space, in MB, available for storage on the disk.Available storage space on disk (MB)

Total storage space, in MB, on the disk.Total storage space on disk (MB)

Mirroring Connection Information





State of the mirroring connection. The following states are possible:

• Active—Indicates that the mirroring status on Routing Engine is active.

• Standalone—Indicates that the backup Routing Engine is down, or that gracefulRouting Engine switchover (GRES) is not configured.

• Standby—Indicates that the backup Routing Engine is on standby.

Connection state

Indicates whether the mirroring connection is established with the other RoutingEngine or not

Other REmirroring connection present

Indicates whether GRES is configured or not.GRES configured

Sample Output

show unified-edgeggsn-pgw charging

user@host> show unified-edge ggsn-pgw charging local-persistent-storage statisticsGateway: PGW Charging local-persistent-storage Statistics



Batch Messages received : 46 Batch Responses sent : 46

local-persistent-storagestatistics

Invalid Messages received : 0 Number of temp log files opened : 1 Number of journal files opened : 1 Number of journal files closed : 0 Number of CDR log files closed : 0 Number of CDR files closed due to file-age : 0 Number of CDR files closed due to file-size : 0 Number of CDR files closed due to cdr-count : 0 Abnormal file closures : 0 Normal file closures : 0 Number of CDR log files closed in TS_32_297 format : 0 Number of CDR log files closed in raw asn1 format : 0 Total number of CDRs backed up : 949 Disk Full messages sent : 0 Disk Full resolve messages sent : 0 Number of async IO reqs written : 46 Disk space status : DISK_AVAILABLE Watermark level1 at(MB) : 618(70%) Watermark level2 at(MB) : 706(80%) Watermark level3 at(MB) : 794(90%)

Temporary CDR log file StatisticsFile Name: /opt/mobility/charging/ggsn/temp_log/templog_file_1.log Journal file name : /opt/mobility/charging/ggsn/jrnl/jrnl_1.log Current number of CDRs : 949 Current file size(bytes) : 288642 File age trigger(mins) : 60 File size trigger(bytes) : 10485760 CDR count trigger : 0

Global Statistics Disk Offline messages sent : 0 Disk Available messages sent : 0 Number of CDR storage files on disk : 0 Current storage space in use(MB) : 301 Available storage space on disk(MB) : 582 Total storage space on disk(MB) : 883

Mirroring Connection Information Connection state : STANDALONE Other RE mirroring connection present : NO GRES configured : NO



show unified-edge ggsn-pgw charging path statistics

Syntax show unified-edge ggsn-pgw charging path statistics<brief | detail><fpc-slot slot-number pic-slot slot-number><gateway gateway-name><gtpp-peer-addr ipv4-address><gtpp-peer-name peer-name>



Description Display the path management message statistics (between the Charging Data Function

(CDF) and the Charging Gateway Function (CGF) servers) for one or more gateway GPRS

support nodes (GGSNs) or Packet Data Network Gateways (P-GWs). If a GGSN or P-GW

is not specified, then the statistics for all GGSNs and P-GWs is displayed.

Options none—(Same as brief) Display the path management message statistics.


The brief option displays the statistics per GGSN or P-GW for all services PICs. The

detail option displays the statistics per GGSN or P-GW for each services PIC.

fpc-slot slot-number pic-slot slot-number—(Optional) Display the path management

message statistics only for the specified Flexible PIC Concentrator (FPC) slot number

and PIC slot number.

gateway gateway-name—(Optional) Display the path management statistics for the


gtpp-peer-addr ipv4-address—(Optional) Display the path management message statistics

only for the GPRS tunneling protocol Prime (GTP Prime) peer with the specified IPv4

address.

gtpp-peer-namepeer-name—(Optional) Display the path management message statistics

only for the GTP Prime peer with the specified name.


view


clear unified-edge ggsn-pgw charging path statistics on page 227•

List of Sample Output show unified-edge ggsn-pgw charging path statistics brief on page 246show unified-edge ggsn-pgw charging path statistics detail on page 246


path statistics command. Output fields are listed in the approximate order in which they

appear.



Table 9: show unified-edge ggsn-pgw charging path statistics Output Fields


All levels

none


detailFPC slot number and PIC slot number for which the statistics are displayed.FPC/PIC

All levels

none

Address of the CGF server (GTP Prime peer).CGF Address

All levels

none

Name of the CGF server (GTP Prime peer).CGF Server Name

All levels

none

Total number of echo requests received by the CDF from the CGF sever.Echo Requests Rx

All levels

none

Total number of echo responses transmitted by the CDF to the CGF sever.Echo Responses Tx

All levels

none

Total number of echo responses received by the CDF from the CGF server.EchoResponses Rx

All levels

none

Total number of echo requests transmitted by the CDF to the CGF server.Echo Requests Tx

All levels

none

Total number of node alive requests received by the CDF from the CGF server.Node-AliveRequests Rx

All levels

none

Total number of responses transmitted by the CDF to the node alive requestsreceived from the CGF server.

Node-AliveResponses Tx

All levels

none

Total number of Version Not Supported messages received by the CDF fromthe CGF server. The CGF server sends these messages to the CDF to indicatethat the GTP Prime messages sent by the CDF are incompatible with the GTPPrime version supported by the CGF server.

Version NotSupported Rx

All levels

none

Total number of Version Not Supported messages transmitted by the CDF tothe CGF server. The CDF sends these messages to indicate that the GTP Primemessages sent by the CGF server are incompatible with the GTP Prime versionsupported by the CDF.

Version NotSupported Tx

All levels

none

Total number of echo requests sent by the CDF for which there were noresponses from the CGF server and that have timed out.

Echo Requeststimed out



Table 9: show unified-edge ggsn-pgw charging path statistics Output Fields (continued)


All levels

none

Configured echo interval, in seconds. If the echo interval is not configured, thenthe default value is displayed.

Echo Interval

All levels

none

Configured down detect time, in seconds. If the down detect time is notconfigured, then the default value is displayed.

Down DetectionInterval

All levels

none

Configured reconnect time, in seconds. If the reconnect time is not configured,then the default value is displayed.

Reconnect TimeInterval

All levels

none

Configured destination port. If the destination port is not configured, then thedefault port (3386) is displayed.

Destination Port

All levels

none

Configured pending queue size. If the pending queue size is not configured, thenthe default value (1024) is displayed.

PendingQueueSize

All levels

none

FPC slot that manages the path management messages.PathManager FPCSlot

All levels

none

PIC slot that manages the path management messages.PathManager PICSlot

All levels

none

Port used for path management messages.PathManager Port

All levels

none

Configured T3 response time interval, in seconds. If the T3 response time is notconfigured, then the default value (5 seconds) is displayed.

T3 Response TimeInterval

All levels

none

Indicates whether the source interface is valid or not.Source InterfaceValid

All levels

none

Configured header type for the GTP Prime messages.GTPPHeader Type

All levels

none

Configured value forN3 requests. If theN3 requests value is not configured, thenthe default value (3) is displayed.

N3 Requests

All levels

none

Address of the local loopback source interface from which the GTP Primepackets are sent to the CGF server.

Local Address



Table 9: show unified-edge ggsn-pgw charging path statistics Output Fields (continued)


All levels

none

Configured version that is supported on the configured local loopback sourceinterface’s IP address, from which the GTP Prime packets are sent to the CGFserver.

GTPP Version

All levels

none

Configured transport protocol for sending the GTP Prime packets from CDF tothe CGF server.

Transport Protocol

All levels

none

Start of the range of source ports from which the TCP connection from eachservices PIC to the CGF server can originate. The GGSN or P-GW assigns a rangeof source ports internally.

TCP Port RangeStart

All levels

none

End of the range of source ports from which the TCP connection from eachservices PIC to the CGF server can originate. The GGSN or P-GW assigns a rangeof source ports internally.

TCP Port RangeEnd

detailIndicates whether the TCP connection state on the services PIC has beenestablished or not.

TCP ConnectionState



Sample Output

show unified-edgeggsn-pgw chargingpath statistics brief

user@host> show unified-edge ggsn-pgw charging path statistics briefGateway: PGWCharging Path Statistics

CGF Address : 2.2.2.2 CGF Server Name : p_cgf Echo Requests Rx: 0 Echo Responses Tx: 0 Echo Responses Rx: 0 Echo Requests Tx: 0 Node-Alive Requests Rx: 0 Node-Alive Responses Tx: 0 Version Not Supported Rx: 0 Version Not Supported Tx: 0 Echo Requests timed out : 0 Echo Interval : 0 Down Detection Interval : 10 Reconnect Time Interval : 60 Destination Port : 3386 Pending Queue Size : 1000 Path Manager FPC Slot : 5 Path Manager PIC Slot : 0 T3 Response Time Interval : 5 Path Manager Port : 30275 Source Interface Valid : Yes GTPP Header Type : long N3 Requests : 1 Local Address : 12.4.1.1

GTPP Version : V0 Transport Protocol : TCP TCP Port Range Start : 30277 TCP Port Range End : 30308

show unified-edgeggsn-pgw chargingpath statistics detail

user@host> show unified-edge ggsn-pgw charging path statistics detailGateway: PGWCharging Path StatisticsFPC/PIC: 5/0

CGF Address : 2.2.2.2 CGF Server Name : p_cgf Echo Requests Rx: 0 Echo Responses Tx: 0 Echo Responses Rx: 0 Echo Requests Tx: 0 Node-Alive Requests Rx: 0 Node-Alive Responses Tx: 0 Version Not Supported Rx: 0 Version Not Supported Tx: 0 Echo Requests timed out : 0 Echo Interval : 0 Down Detection Interval : 10 Reconnect Time Interval : 60 Destination Port : 3386 Pending Queue Size : 1000 Path Manager FPC Slot : 5 Path Manager PIC Slot : 0 T3 Response Time Interval : 5 Path Manager Port : 30275 Source Interface Valid : Yes GTPP Header Type : long N3 Requests : 1 Local Address : 12.4.1.1

GTPP Version : V0 Transport Protocol : TCP TCP Port Range Start : 30277 TCP Port Range End : 30308 TCP Connection State : Established



show unified-edge ggsn-pgw charging path status

Syntax show unified-edge ggsn-pgw charging path status<brief | detail><fpc-slot slot-number pic-slot slot-number><gateway gateway-name><gtpp-peer-addr ipv4-address><gtpp-peer-name peer-name>



Description Display the status of the configured GPRS tunneling protocol (GTP) Prime peers for one

or more gateway GPRS support nodes (GGSNs) or Packet Data Network Gateways

(P-GWs). If a GGSN or P-GW is not specified, then the status for all GGSNs and P-GWs

is displayed.

The status includes information about whether the GTP Prime peers are connected,

down, or still in the process of establishing a connection, and whether the echo messages

are enabled or disabled.

NOTE: Incharging, the termsGTPPrimepeersandcharginggatewayfunction(CGF) server are used interchangeably.

Options none—(Same as brief) Display the status of the configured peers.


fpc-slotslot-numberpic-slotslot-number—(Optional) Display the status of the configured

peers only for the specified FPC slot number and PIC slot number.

gateway gateway-name—(Optional) Display the path management statistics for the


gtpp-peer-addr ipv4-address—(Optional) Display the status of the configured peers only

for the GTP Prime peer with the specified IPv4 address.

gtpp-peer-name peer-name—(Optional) Display the status of the configured peers only

for the GTP Prime peer with the specified name.


view


show unified-edge ggsn-pgw charging path statistics on page 242•

List of Sample Output show unified-edge ggsn-pgw charging path status on page 249show unified-edge ggsn-pgw charging path status detail on page 249



Output Fields Table 10 on page 248 lists the output fields for the showunified-edge ggsn-pgw charging

path status command. Output fields are listed in the approximate order in which they

appear.

Table 10: show unified-edge ggsn-pgw charging path status Output Fields


All levels

none


All levels

none

Address of the CGF server (GTP Prime peer).Peer-Address

All levels

none

Name of the CGF server (GTP Prime peer).Peer-Name

All levels

none

IPv4 address of the local loopback source interface from where the GTP Primepackets are sent to the CGF server (GTP Prime peer).

Local-Address

All levels

none

Status of the CGF server:

• Connected

• Down

• In-Progress

Status

All levels

none

Indicates whether echo messages are enabled or disabled. The possible valuesare:

• Enabled or Disabled for UDP connections

• N/A (Not Applicable) for TCP connections

Echo

detailProbable cause for the current status of the CGF peer. This field is displayedonly when the CGF server is down or the connection has not been established.

Cause

detailFPC and PIC slot numbers.FPC/PIC



Sample Output

show unified-edgeggsn-pgw chargingpath status

user@host> show unified-edge ggsn-pgw charging path statusGateway: PGWCharging Path StatusPeer-Address Peer-Name Local-Address Status Echo2.2.2.2 p_cgf 12.4.1.1 Connected N/A

show unified-edgeggsn-pgw chargingpath status detail

user@host> show unified-edge ggsn-pgw charging path status detailGateway: PGWCharging Path Status

FPC/PIC 5/0 Peer-Address 2.2.2.2 Peer-Name p_cgf Local-Address 12.4.1.1 Status Connected Echo N/A



show unified-edge ggsn-pgw charging service-mode

Syntax show unified-edge ggsn-pgw charging service-mode gateway gateway<brief | detail><charging-profile profile-name><transport-profile profile-name>


Description Display the charging service mode information for the specified Gateway GPRS Support

Node (GGSN) or Packet Data Network Gateway (P-GW).

Options gateway gateway-name—Display the charging service mode information for the specified

GGSN or P-GW.


charging-profile profile-name—(Optional) Display the service mode information for the

specified charging profile.

transport-profile profile-name—(Optional) Display the service mode information for the

specified transport profile.


view


service-mode (Charging Profiles) on page 182•

• service-mode (Transport Profiles) on page 184

List of Sample Output show unified-edge ggsn-pgw charging service-mode gateway PGWbrief on page 251showunified-edgeggsn-pgwchargingservice-modegatewayPGWdetailonpage252


service-mode command. Output fields are listed in the approximate order in which they

appear.

Table 11: show unified-edge ggsn-pgw charging service-mode Output Fields


All levelsName of the GGSN or P-GW.Gateway Name



Table 11: show unified-edge ggsn-pgw charging service-mode Output Fields (continued)


All levelsService mode for the gateway. The following service modes are possible:

• Maintenance—Gateway is in maintenance mode.

• MMActive Phase—In this mode, you can make changes to any of theconfiguration options under the [edit unified-edge gateways ggsn-pgwgateway-name charging charging-profiles] or the [edit unified-edge gatewaysggsn-pgw gateway-name charging transport-profiles] hierarchy levels.

• MMIn/OutPhase—In this mode, you cannot make changes to the configurationoptions under the [edit unified-edge gateways ggsn-pgw gateway-namecharging charging-profiles] or the [edit unified-edge gateways ggsn-pgwgateway-name charging transport-profiles] hierarchy levels.

• Operational—Gateway is still in operational mode and not in maintenancemode. You can use the following commands to put the charging profile ortransport profile in maintenance mode:

• setunified-edgegatewaysggsn-pgwgateway-namechargingcharging-profilesprofile-name service-modemaintenance

• set unified-edge gateways ggsn-pgw gateway-name chargingtransport-profiles profile-name service-modemaintenance

Service Mode

All levelsName of the charging profile.Charging Profile(s)or Charging Profile

All levelsService mode for the charging profile.Service Mode

All levelsName of the transport profile.TransportProfile(s)or Transport Profile

All levelsService mode for the transport profile.Service Mode

detailLists the components or modules that are not yet ready to accept theconfiguration changes. Maintenance mode becomes active only after all thecomponents or modules are ready to accept these changes.

PendingMaintenanceModeReady Ack

Sample Output


user@host> show unified-edge ggsn-pgw charging service-mode gateway PGWbriefMaintenance Mode MM Active Phase - System is ready to accept configuration changes for all



attributes of this object and its sub-hierarchies. MM In/Out Phase - System is ready to accept configuration changes only for

service-modegatewayPGWbrief

non-maintenance mode attributes of this object and its sub-hierarchies..Gateway Name : PGWService Mode : Operational

Charging Profile(s) Service Modep_juniper OperationalTransport Profile(s) Service Modep_tsp Operational


user@host> show unified-edge ggsn-pgw charging service-mode gateway PGWdetailGateway Name : PGWService Mode : Operationalservice-modegateway

PGWdetailCharging Profile: p_juniperService Mode : OperationalTransport Profile: p_tspService Mode : Operational



show unified-edge ggsn-pgw charging transfer statistics

Syntax show unified-edge ggsn-pgw charging transfer statistics<brief | detail><fpc-slot slot-number pic-slot slot-number><gateway gateway-name><transport-profile-name profile-name>



Description Display the transfer statistics for the configured transport profiles on one or more Gateway

GPRS Support Nodes (GGSNs) or Packet Data Network Gateways (P-GWs). If a GGSN

or P-GW is not specified, then statistics for all GGSNs and P-GWs are displayed.

Options none—(Same as brief) Display the transfer statistics for the configured transport profiles

for all GGSNs or P-GWs.


fpc-slot slot-number pic-slot slot-number—(Optional) Display the transfer statistics only

for the specified FPC slot number and PIC slot number.

gatewaygateway-name—(Optional) Display the transfer statistics for the specified GGSN

or P-GW.

transport-profile-name profile-name—(Optional) Display the transfer statistics only for

the specified transport profile.


view


clear unified-edge ggsn-pgw charging transfer statistics on page 228•

List of Sample Output show unified-edge ggsn-pgw charging transfer statistics brief on page 255show unified-edge ggsn-pgw charging transfer statistics detail on page 255


transfer statistics command. Output fields are listed in the approximate order in which

they appear.

Table 12: show unified-edge ggsn-pgw charging transfer statistics Output Fields


All levels

none


All levels

none

Name of the transport profile.Transport-Profile



Table 12: show unified-edge ggsn-pgw charging transfer statistics Output Fields (continued)


All levels

none

Total number of redirection request messages received by the charging datafunction (CDF) from the charging gateway function (CGF) server.

The CGF server can send these messages to inform CDF about the following:

• The CGF server is about to stop service (possibly due to an error condition orfor maintenance).

• The next node in the chain (such as a billing server) has lost its connectionto the CGF server.

RedirectionRequests Rx

All levels

none

Total number of redirection response messages transmitted as responses tothe redirection requests received. Redirection response messages indicatewhether a redirection request message was successful or not.

RedirectionResponses Tx

All levels

none

Total number of DRT response messages received for the Data Record Transfer(DRT) request messages sent. DRT response messages indicate whether a DRTrequest was successful or not.

DRT Responses Rx

All levels

none

Total number of DRT request messages transmitted to the CGF server. Thesemessages are used to transfer CDRs from the CDF to the CGF server.

DRT Requests Tx

All levels

none

Total number of successful DRT response messages received for the DRTrequest messages sent.

DRT successfulResponses Rx

All levels

none

Total number of DRT error response messages received for the DRT requestmessages sent.

DRT ErrorResponses Rx

All levels

none

Total number of DRT requests sent that timed out before receiving any responsesfrom the CGF server.

DRT Requeststimed out

All levels

none

Total number of times the CGF servers were switched, which indicates thenumber of times that the CGF servers were either offline or down formaintenance.

CGF Switch BackTimes

All levels

none

Total number of batch requests transmitted (from services PICs) for a transportprofile.

Batch Requests Tx

All levels

none

Total number of error responses sent by the Routing Engine to the services PICsfor the batch requests messages received.

Batch ResponseErrors Rx

All levels

none

Total number of CDRs transmitted from services PICs to the Routing Engine.Batch CDR's Tx

All levels

none

Total number of CDRs transmitted to the CGF server.CDR Count



Table 12: show unified-edge ggsn-pgw charging transfer statistics Output Fields (continued)


All levels

none

Total number of request messages awaiting acknowledgements from eitherthe Routing Engine or the CGF server.

TotalWFA

All levels

none

Number of open batch requests timed out.

Batch message requests are sent to write CDRs into local storage. This counterindicates that no response was received and that the request was timed out.

Open BatchRequestsTimedout


Sample Output

show unified-edgeggsn-pgw chargingtransfer statistics brief

user@host> show unified-edge ggsn-pgw charging transfer statistics briefGateway: PGWCharging Transfer StatisticsTransport-Profile : p_tsp Redirection Requests Rx: 0 Redirection Responses Tx: 0 DRT Responses Rx: 0 DRT Requests Tx: 0 DRT successful Responses Rx: 0 DRT Error Responses Rx: 0 DRT Requests timed out : 0 CGF Switch Back Times : 0 Batch Requests Tx: 0 Batch Response Errors Rx: 0 Batch CDR's Tx: 0 CDR Count : 0 Total WFA : 0 Open Batch Requests Timed out : 0


user@host> show unified-edge ggsn-pgw charging transfer statistics detailGateway: PGWCharging Transfer Statisticstransfer statistics

detail FPC/PIC: 3/0 Transport-profile : p_tsp Redirection Requests Rx: 0 Redirection Responses Tx: 0 DRT Responses Rx: 0 DRT Requests Tx: 0 DRT successful Responses Rx: 0 DRT Error Responses Rx: 0 DRT Requests timed out : 0 CGF Switch Back Times : 0 Batch Requests Tx: 0 Batch Response Errors Rx: 0 Batch CDR's Tx: 0 CDR Count : 0 Total WFA : 0 Open Batch Requests Timed out : 0



show unified-edge ggsn-pgw charging transfer status

Syntax show unified-edge ggsn-pgw charging transfer status<brief | detail><fpc-slot slot-number pic-slot slot-number><gateway gateway-name><transport-profile-name profile-name>



Description Display the Charging Data Record (CDR) transfer status for the configured transport

profiles for one or more gateway GPRS support nodes (GGSNs) or Packet Data Network

Gateways (P-GWs). If a GGSN or P-GW is not specified, then the status for all GGSNs

and P-GWs is displayed.

Options none—(Same as brief) Display the total number of unacknowledged and buffered CDRs

for the configured transport profiles for all GGSNs or P-GWs.


fpc-slot slot-number pic-slot slot-number—(Optional) Display the total number of

unacknowledged and buffered CDRs only for the specified FPC slot number and PIC

slot number.

gateway gateway-name—(Optional) Display the total number of unacknowledged and

buffered CDRs for the configured transport profiles for the specified GGSN or P-GW.

transport-profile-name profile-name—(Optional) Display the total number of

unacknowledged and buffered CDRs only for the specified transport profile.


view


show unified-edge ggsn-pgw charging transfer statistics on page 253•

List of Sample Output show unified-edge ggsn-pgw charging transfer status on page 258show unified-edge ggsn-pgw charging transfer status detail on page 258


transfer status command. Output fields are listed in the approximate order in which they

appear.

Table 13: show unified-edge ggsn-pgw charging transfer status Output Fields


All levels

none

The call admission control (CAC) status of the transport profile.CAC Status



Table 13: show unified-edge ggsn-pgw charging transfer status Output Fields (continued)


All levels

none

Name of the GGSN or P-GWGateway


All levels

none

Name of the transport profile.Transport-Profile

detailID of the transport profile.Transport-profile Id

All levels

none

Total number of CDRs (for the transport profile) sent to the charging gatewayfunction (CGF) servers for which no acknowledgements were received.

Total UnAck CDR's

All levels

none

Total number of buffered CDRs (for the transport profile) in the services PICs.Total BufferedCDR's



Sample Output

show unified-edgeggsn-pgw chargingtransfer status

user@host> show unified-edge ggsn-pgw charging transfer statusGateway: PGW Charging Transfer StatusTransport-Profile : p_tsp Total UnAck CDR's : 2 Total Buffered CDR's : 0 CAC Status : Operational

Transport-Profile : 2 Total UnAck CDR's : 0 Total Buffered CDR's : 0 CAC Status : Operational

Gateway: PGW2 Charging Transfer StatusTransport-Profile : p_tsp Total UnAck CDR's : 5 Total Buffered CDR's : 0 CAC Status : Operational

Transport-Profile : 2 Total UnAck CDR's : 0 Total Buffered CDR's : 0 CAC Status : Operational

show unified-edgeggsn-pgw chargingtransfer status detail

user@host> show unified-edge ggsn-pgw charging transfer status detailGateway: PGW Charging Transfer Status FPC/PIC: 2/0 Transport-profile : p_tsp Transport-profile Id : 3 Total UnAck CDR's : 2 Total Buffered CDR's : 0 CAC Status : Operational

Transport-profile : 2 Transport-profile Id : 1 Total UnAck CDR's : 0 Total Buffered CDR's : 0 CAC Status : Operational

Gateway: PGW2 Charging Transfer Status FPC/PIC: 2/1 Transport-profile : p_tsp Transport-profile Id : 6 Total UnAck CDR's : 5 Total Buffered CDR's : 0 CAC Status : Operational

Transport-profile : 2 Transport-profile Id : 4 Total UnAck CDR's : 0 Total Buffered CDR's : 0 CAC Status : Operational



PART 4

Troubleshooting

• Acquiring Troubleshooting Information on page 263


CHAPTER 8

Acquiring Troubleshooting Information


Tracing Charging Operations

Charging tracing operations track mobile charging operations and record them in a log

file. The error descriptions captured in the log file provide detailed information to help

you solve problems.

All log files are located in the /var/log directory. You cannot change the directory in which

trace files are located. When the trace file reaches its maximum size, a .0 is appended

to the filename, then a new file is created with a .1, and finally a .2. When the maximum

number of trace files is reached, the oldest trace file is overwritten.

NOTE: You should use carewhen tracing charging operations because it canhave a performance impact.

To configure charging tracing operations:

1. Specify that you want to configure tracing options for charging operations.

[edit]user@host# edit unified-edge gateways ggsn-pgwMBG1 charging traceoptions

2. (Optional) Configure the name for the file used for the trace output.

3. (Optional) Configure flags to filter the operations to be logged.

The mobile charging traceoptions configuration tasks are described in the following

topics:

• Configuring the Trace Log Filename on page 264

• Configuring the Tracing Flags on page 264


Configuring the Trace Log Filename

By default, the name of the file that records trace output for mobile charging is

mobile-smd. You can specify a different name with the file option to distinguish trace

output for different session Dense Port Concentrators (DPCs). For example, you can

specify the filename in the format filename-msnumberfpcnumberpicnumber.

To configure the filename for mobile charging tracing operations:

• Specify the name of the file used for the trace output.

[edit unified-edge gateways ggsn-pgwMBG1 charging traceoptions]user@host# set file filename

Configuring the Tracing Flags

To configure the flags for the events to be logged:

• Configure the flags.

[edit unified-edge gateways ggsn-pgwMBG1 charging traceoptions]user@host# set flag flag

By default, only important events are logged. You can specify which trace operations are

logged by including specific tracing flags. Table 14 on page 264 describes the flags that

you can include.

Table 14: Charging Tracing Flags

DescriptionFlag

Trace all operationsall

Trace CDR encodingcdr-encoding

Trace client finite state machine (FSM)client-fsm

Trace configuration eventsconfig

Trace FSMfsm

Trace general flowgeneral

Trace group FSMgroup-fsm

Trace initialization eventsinit

Trace IPCipc

Trace Gy active session management (ASM) moduleonline

Trace path management modulepath-management



Table 14: Charging Tracing Flags (continued)

DescriptionFlag

Trace resourcesresource

Trace timerstimers

Trace online processing moduletpm

Trace transport grouptransport

Trace trigger informationtriggers








Chapter 8: Acquiring Troubleshooting Information

PART 5

Index

• Index on page 269


Index

Symbols#, comments in configuration statements....................xv

( ), in syntax descriptions.....................................................xv

< >, in syntax descriptions...................................................xiv

[ ], in configuration statements.........................................xv

{ }, in configuration statements.........................................xv

| (pipe), in syntax descriptions...........................................xv

AAdvice of Charge

overview...............................................................................4

service filter configuration..........................................52

service set and filter overview....................................16

all-rgs-on-termination statement

transport profiles

online.........................................................................78

always-include statement

trigger profiles

online.........................................................................79

authorization-rejected statement

trigger profiles

online.........................................................................80

Bblacklist statement

trigger profiles

online..........................................................................81

block-traffic-pending-reauth-no-quota statement

trigger profiles

online.........................................................................82

braces, in configuration statements.................................xv

brackets

angle, in syntax descriptions.....................................xiv

square, in configuration statements........................xv

broadband gateway

charging................................................................................5

configuring online charging........................................55

offline charging.................................................................8

online charging overview...............................................9

Ccc-failure-handling statement

trigger profiles

online.........................................................................83

cc-octet-both statement

trigger profiles

online.........................................................................85

cc-octet-downlink statement

trigger profiles

online.........................................................................86

cc-octet-uplink statement

trigger profiles

online.........................................................................87

cc-time statement

trigger profiles

online.........................................................................88

CDR profiles

configuring........................................................................35

cdr-aggregation-limit statement

charging gateways

transport profiles..................................................89

cdr-profile statement

charging profiles............................................................90

cdr-profiles statement..........................................................92

cdr-release statement

charging gateways

transport profiles..................................................94

CDRs

GTP Prime properties...................................................23

cdrs-per-file statement........................................................95

charging

configuring..................................................................21, 22

configuring on broadband gateway........................55

disabling persistent storage....................................230

enabling persistent storage.....................................229

offline....................................................................................8

on broadband gateway..................................................5

online.....................................................................................9

charging configurations

managing.........................................................................221

monitoring.......................................................................221

charging profiles

APN

configuring...............................................................40

CDR profiles.....................................................................35

configuring........................................................................38

transport profiles...........................................................29

trigger profiles..................................................................32

charging statement...............................................................96


charging-function-name statement

transport profiles..........................................................102

charging-gateways statement

transport profiles

offline.......................................................................104

charging-method statement

trigger profiles...............................................................105

charging-profiles statement............................................106

clear unified-edge ggsn-pgw charging cdr

command............................................................................224

clear unified-edge ggsn-pgw charging cdr wfa

command............................................................................225

clear unified-edge ggsn-pgw charging

local-persistent-storage statistics

command...........................................................................226

clear unified-edge ggsn-pgw charging path

statistics command.........................................................227

clear unified-edge ggsn-pgw charging transfer

statistics command........................................................228

comments, in configuration statements........................xv

container-limit statement


conventions

text and syntax...............................................................xiv

convert-to-offline statement

trigger profiles

online.......................................................................108

credit-control-not-applicable statement

trigger profiles

online........................................................................110

credit-limit-reached statement

trigger profiles

online..........................................................................111

curly braces, in configuration statements......................xv

customer support....................................................................xv

contacting JTAC...............................................................xv

Ddefault-rating-group statement

charging profiles.............................................................112

default-service-id statement


description statement

CDR profiles.....................................................................114

charging profiles............................................................114


trigger profiles.................................................................114

destination-ipv4-address statement

GTP Prime........................................................................115

destination-port statement

GTP Prime........................................................................116

diameter-profile statement

transport profiles

online.........................................................................117

direction statement

trigger profiles

offline........................................................................118

disable-online-charging statement

trigger profiles

online.........................................................................119

disable-replication statement.........................................120

disk-space-policy statement.............................................121

documentation

comments on...................................................................xv

down-detect-time statement

GTP Prime........................................................................122

Eecho-interval statement

GTP Prime.......................................................................123

edit unified-edge gateways ggsn-pgw statement

hierarchy................................................................................65

enable-reduced-partial-cdrs statement

CDR profiles....................................................................125

end-user-service-denied statement

trigger profiles

online........................................................................124

examples

configuring online charging........................................55

exclude statement

trigger profiles

offline.......................................................................126

exclude-attributes statement

CDR profiles....................................................................128

Ffile-age statement................................................................135

file-creation-policy statement.........................................136

file-format statement..........................................................137

file-name-private-extension statement......................138

file-size statement................................................................139

font conventions.....................................................................xiv

Ggrant-grace-quota statement

trigger profiles

online........................................................................143



grant-quota statement

trigger profiles

online.......................................................................144

GTP Prime peers

GTP Prime properties...................................................24

GTP Prime properties

configuring.................................................................23, 24

gtpp statement.......................................................................141

Hheader-type statement

GTP Prime.......................................................................145

Iinclude-quota-holding-time statement

trigger profiles

online.......................................................................146

initial-request statement

trigger profiles

online........................................................................147

Llocal-persistent-storage-options statement.............148

local-storage statement

charging gateways.......................................................149

Mmanuals

comments on...................................................................xv

measurement-method statement

trigger profiles

online.......................................................................150

mobile charging

flags for tracing operations.....................................264

log filenames for tracing operations....................264

tracing operations.......................................................263

mobile subscribers

CDR profiles.....................................................................35


APN............................................................................40

monitoring.......................................................................221

persistent storage of CDR...........................................25

tracing operations.......................................................263


trigger profiles..................................................................32

mtu statement

charging gateways........................................................151


Nn3-requests statement

GTP Prime.......................................................................152

no-mscc-in-ccrt statement

transport profiles

online........................................................................154

no-path-management statement

GTP Prime.......................................................................155

node-id

CDR profiles....................................................................153

Ooffline charging

configuring.........................................................................21

offline statement


trigger profiles................................................................157

online charging

configuring........................................................................22

configuring on broadband gateway........................55

on broadband gateway..................................................9

online statement



override statement

trigger profiles

online.........................................................................161

Pparentheses, in syntax descriptions.................................xv

peer statement

GTP Prime.......................................................................162

peer order

charging gateways..............................................163

peer-order statement


pending-queue-size statement

GTP Prime.......................................................................165

persistent storage

configuring........................................................................25

configuring the SSD................................................27, 29

disabling for charging................................................230

ejecting the SSD.............................................................28

enabling for charging.................................................229

formatting SSD.............................................................232

initializing the SSD.........................................................28

preparing SSD......................................................231, 232

removing SSD................................................................231

tracing operations..........................................................26


Index

persistent-storage-order statement


profile-id statement.............................................................167

Qquota-holding-time statement

trigger profiles

online.......................................................................168

quota-request-on-first-packet statement

transport profiles

online.......................................................................169

quota-threshold statement

trigger profiles

online........................................................................170

quota-validity-time statement

trigger profiles

online.........................................................................171

Rrating-group statement

trigger-profile

charging-profiles..................................................172

reconnect-time statement

GTP Prime........................................................................174

redirect-reason statement

Advice of Charge...........................................................173

report-requested-apn statement

CDR profiles....................................................................176

reporting-level statement


request system storage unified-edge charging

media start command...................................................229

request system storage unified-edge charging

media stop command...................................................230

request system storage unified-edge media eject

command.............................................................................231

request system storage unified-edge media prepare

command............................................................................232

requested-service-unit statement

trigger profiles

online.........................................................................177

result-code-based-action statement

trigger profiles

online........................................................................178

Ssend-ccri-on-first-packet statement

transport profiles

online........................................................................179

service filters

Advice of Charge.............................................................16

Advice of Charge configuration.................................52

service sets

Advice of Charge.............................................................16

service statement

Service Filter..................................................................180

service-context-id statement

transport profiles

online.........................................................................181

service-mode statement

charging profiles...........................................................182


session-failover-not-supported statement

transport profiles

online.......................................................................186

sgsn-sgw-change-limit statement

transport-profiles.........................................................187

show unified-edge ggsn-pgw charging global


show unified-edge ggsn-pgw charging

local-persistent-storage statistics

command...........................................................................236

show unified-edge ggsn-pgw charging path


show unified-edge ggsn-pgw charging path status

command............................................................................247

show unified-edge ggsn-pgw charging service-mode

command...........................................................................250

show unified-edge ggsn-pgw charging transfer


show unified-edge ggsn-pgw charging transfer

status command..............................................................256

single-mscc statement

transport profiles

online.......................................................................188

source-interface statement

GTP Prime.......................................................................189

peer...........................................................................189

support, technical See technical support

switch-back-time statement


syntax conventions................................................................xiv

Tt3-response statement

GTP Prime........................................................................191

tariff-time-list statement

trigger-profiles...............................................................192



technical support

contacting JTAC...............................................................xv

time-limit statement...........................................................193

Top-Up

Advice of Charge...............................................................4

traceoptions statement

charging...........................................................................194

local persistent storage.....................................197

tracing operations

for persistent storage...................................................26

mobile charging...........................................................263

mobile subscribers......................................................263

transport profiles

configuring

offline charging......................................................29

online..........................................................................41

transport-profile statement

charging profiles...........................................................199

transport-profiles statement...........................................201

transport-protocol statement

GTP Prime......................................................................203

trigger profiles

configuring........................................................................32

online charging.......................................................43

trigger-profile statement..................................................204

trigger-profiles statement................................................206

tx-timeout statement

transport profiles

online......................................................................209

Uupdate-request statement

trigger profiles

online.......................................................................210

user-name statement

local persistent storage...............................................211

user-unknown statement

trigger profiles

online........................................................................212

Vversion statement

GTP Prime.......................................................................213

volume-limit statement


Wwatermark-level-1 statement...........................................215

watermark-level-2 statement..........................................216

watermark-level-3 statement..........................................217

world-readable statement

local persistent storage..............................................218


Index

charging architecture

Documents