Secondary RAT Usage Report in CDR Records
Feature Summary and Revision History
Feature Description
Configuring Secondary RAT Usage Report through GTPP
Monitoring and Troubleshooting
- Show Commands and Outputs

Secondary RAT Usage Report in CDR Records

Feature Summary and Revision History

Summary Data


Applicable Product(s) or Functional Area	P-GW SAEGW S-GW
Applicable Platform(s)	ASR 5500 VPC-DI
Feature Default	Disabled - Configuration Required
Related Changes in This Release	Not Applicable
Related Documentation	Command Line Interface Reference GTPP Interface Administration and Reference P-GW Administration Guide SAEGW Administration Guide S-GW Administration Guide Statistics and Counters Reference

Revision History


Revision Details	Release
P-GW and S-GW supports secondary RAT usage reports and CDRs processing through GTPP Group Configuration CLIs.	21.20.31

Feature Description

Reporting issues pertaining to 5G RANSecondaryRATUsageReport occur due to lack of:

Control in identifying whether the RANSecondaryRATUsageReport must be processed in CDRs or not. This allows the S-GW, P-GW, and SAEGW to either include these reports in the SGW-CDR or PGW- CDR or to simply ignore them.
Number of available reports inside a CDR, if the control is active.
Control in identifying whether Zero-volume reports must make it inside the CDR or not.

This results in billing loss of data. To overcome these reporting issues, you can trigger CLI controls using GTPP group configuration to:

Allow the S-GW, P-GW, and SAEGW to either include the RANSecondary RAT Usage reports in the SGW-CDR or PGW-CDR or to simply ignore them.

Identify the number of secondary RAT usage reports available inside the SGW-CDR or the PGW- CDR.

Note

This limit must be in accordance with the system capability and ensure to consider the File-Format of the CDRs. If the configured limit exceeds, the system closes the SGW-CDR or PGW-CDR with the appropriate change-condition. For example, max-change-condition CDR is reused for further reports.

Add or ignore Zero-volume reports inside the CDR.
The CLI gtpp limit-secondary-rat-usage or hardcoded limit will be removed and the CLI gtpp limit-secondary-rat-usage is reused to control the number of records within the range 1-100.
Provides logging when the CDR size reaches the maximum size. Through PGW-CDR counter, you can monitor the number of occurrences when the CDR exceeds its size limit.

Behavior Matrix

The following table explains the new behavior of P-GW and S-GW for this feature.

CLI

P-GW New Behavior

S-GW New Behavior

gtpp attribute secondary-rat-usage

By default, this CLI command is enabled in gtpp group.

P-GW sends secondary RAT usage records in CDR including zero volume records.

S-GW sends secondary RAT usage records in CDR including zero volume records.

[ no ] gtpp attribute secondary-rat-usage

P-GW does not send secondary RAT usage records in CDR.

S-GW does not send secondary RAT usage records in CDR.

gtpp suppress-secondary-rat-usage zero-volume

By default, this CLI command is disabled in gtpp group.

P-GW does not include and send zero volume secondary RAT records in CDR. P-GW sends only secondary RAT records with non-zero volumes.

S-GW does not include and send zero volume secondary RAT records in CDR. S-GW sends only secondary RAT records with non-zero volumes.

[ no ] gtpp suppress-secondary-rat-usage zero-volume

P-GW sends secondary RAT usage records including zero volume records in CDR.

S-GW sends secondary RAT usage records including zero volume records in CDR.

gtpp limit-secondary-rat-usage range_1–100 . If not configured, the default value is 32. By default, this CLI command is enabled in gtpp group.

Example: gtpp limit-secondary-rat-usage 32

Note

This CLI is the modification of the existing CLI command gtpp limit-secondary-rat-usage with range between 1– 100.

P-GW generates CDR immediately when total received secondary RAT records exceeds 32 and reported cause value is maximum change condition .

P-GW generates multiple CDRs if total received secondary RAT records are multiples of 32.

Example: If P-GW receives 100 RAT records between two triggers, P-GW generates 3 CDRs and keeps the remaining 4 RAT records for the next CDR trigger.

S-GW generates CDR immediately when total received secondary RAT records exceeds 32 and the reported cause value is maximum change condition .

S-GW generates multiple CDRs if the total received secondary RAT records are multiples of 32.

Example: If S-GW receives 100 RAT records between two triggers, S-GW generates 3 CDRs and keeps the remaining 4 RAT records for the next CDR trigger.

Example:gtpp limit-secondary-rat-usage 40

P-GW generates CDR immediately when total received secondary RAT records exceeds 40 and cause value is maximum change condition .

P-GW generates multiple CDRs if total received secondary RAT records are multiples of 40.

Example: If P-GW receives 100 RAT records between two triggers, it will generate 2 CDRs and will keep remaining 20 RAT records for the next CDR trigger.

If the configured value is greater than 32 and sends 32 secondary RAT records in every CDR, Ignores gtpp limit-secondary-rat-usage 40 CLI command.

Example:gtpp limit-secondary-rat-usage 20

P-GW generates CDR immediately when total received secondary RAT records exceed 20 and cause value is maximum change condition .

P-GW generates multiple CDRs if total received secondary RAT records are multiples of 20.

Example: If P-GW receives 100 RAT records between two triggers, P-GW generates 2 CDRs and will store the remaining 20 RAT records for the next CDR trigger.

S-GW generates CDR immediately when the total received secondary RAT records exceeds 20 and cause value is maximum change condition .

S-GW generates multiple CDRs if total received secondary RAT records are in multiples of 20.

Example: If S-GW receives 100 RAT records between two triggers, it will generate 5 CDRs.

[ no ] gtpp limit-secondary-rat-usage

Generates CDR immediately when the total received secondary RAT records exceed 255 and cause value is maximum change condition .

Generates multiple CDRs if the total received secondary RAT records are multiples of 255.

Example: If 1000 RAT records between two triggers are received, then 3 CDRs are generated. The remaining 235 RAT records are stored for the next CDR trigger.

Ignores the [ no ] gtpp limit-secondary-rat-usage CLI and sends 32 secondary RAT records in every CDR.

Behavior is similar to the gtpp limit-secondary-rat-usage 32 CLI implementation.

Counter and debug logs are not required as it will never exceed the CDR size of 64k.

Service-specific unit limit is sent in the serviceConditionChange file.

Record Closure

Relationship to Other Features

Sessmgr Restart While Processing Secondary RAT Usage CDR Records in the P-GW Administration Guide.
Secondary RAT Usage IE during GnGp handover, S-GW, and P-GW support of Secondary RAT Data Usage Report in Gz CDRs, see the 5G Non-Standalone chapter in the P-GW Administration Guide.
P-GW support of Secondary RAT Data Usage Report in Rf CDRs, see the 5G Non-Standalone chapter in the P-GW Administration Guide.

Limitations

This feature has the following limitations:

S-GW allows a maximum number of 16 secondary RAT records per bearer during session recovery and checkpointing.
P-GW allows a maximum number of 142 secondary RAT records across all bearers during session recovery and checkpointing.
Anything beyond these numbers gets lost during session recovery.

Configuring Secondary RAT Usage Report through GTPP

Use the following GTPP configurations to close Secondary RAT Usage CDR records before exceeding a buffer size.

Enabling or Disabling the Secondary RAT Usage Report

Use the following configuration to enable or disable secondary RAT Usage report.

configure 
   context context_name 
      gtpp group group_name 
         gtpp attribute secondary-rat-usage 
         default gtpp attribute secondary-rat-usage 
         no gtpp attribute secondary-rat-usage 
         end

NOTES:

gtpp attribute secondary-rat-usage : Sends an optional attribute Secondary RAT usage records.
default gtpp attribute secondary-rat-usage : Sends an optional attribute Secondary RAT usage records by default.
no gtpp attribute secondary-rat-usage : Does not send the optional attribute Secondary RAT usage records.

Controlling the Maximum Number of Entries

When the Secondary RAT usage record reaches the maximum configured value within a CDR, the CDR closure cause occurs and uses maxChangeCond . The gtpp limit-secondary-RAT-usage CLI command controls the maximum number of Secondary RAT usage record entries in the P-GW and S-GW CDRs. If the limit is configured with a value more than 32, the partial CDRs get generated with a maximum of 32 for S-GW CDR.

Note

The existing behaviour of S-GW has a limit of 32 Secondary RAT Usage records.

The following table explains the behavior of Secondary RAT records and CDR, and the maximum limit.


Sl. Number	CDR Type	Configured limit- secondary-rat-usage	Effective Maximum Limit	No. of Secondary RAT records Sent by UE	Behavior of Secondary RAT Records and CDR
1	P-GW	Less than 32 Example: 20	20	35	Partial CDR is generated with 20 secondary RAT records.
	P-GW	Less than 32 Example: 20	20	35	Remaining 15 secondary RAT records sent in the next trigger.
	S-GW	Less than 32 Example: 20	20	35	Partial CDR is generated with 20 Secondary RAT records.
	S-GW	Less than 32 Example: 20	20	35	Remaining 15 Secondary RAT records sent in the next trigger.
2	P-GW	32	32	35	Partial CDR is generated with 32 Secondary RAT records.
	P-GW	32	32	35	Remaining 3 secondary RAT records sent in the next trigger.
	S-GW	32	32	35	Partial CDR is generated with 32 secondary RAT records.
	S-GW	32	32	35	Remaining 3 secondary RAT records sent in the next trigger.
3	P-GW	Greater than 32 Example: 100	100	100	Partial CDR is generated with 100 secondary RAT records.
	P-GW	Greater than 32 Example: 100	100	100
	S-GW	Greater than 32 Example: 100	32	100	Three partial CDRs are generated with 32 secondary RAT records each.
	S-GW	Greater than 32 Example: 100	32	100	Remaining 4 secondary RAT records sent in the next trigger.
4	P-GW	Not configured	255	1000	Three partial CDRs are generated with 255 secondary RAT records each.
	P-GW	Not configured	255	1000	Remaining reported Secondary RAT records become a part of CDR in the next trigger.
	S-GW	Not configured	32	1000	No partial CDR is generated.
	S-GW	Not configured	32	1000	32 Secondary RAT records become part of the CDR in the next trigger.

Use the following configuration to control the maximum number of entries.

configure 
   context context_name 
      gtpp group group_name 
         gtpp limit-secondary-rat-usage usage_limit 
         default gtpp limit-secondary-rat-usage 
         no gtpp limit-secondary-rat-usage 
         end

NOTES:

gtpp limit-secondary-rat-usage usage_limit : Enter a maximum number of secondary RAT reports. usage_limit must be an integer in the range of 1-100. The recommended value for S-GW CDR is 32.

For example, if the limit is set to 10, then the CDR is generated once the configured value is reached.
default gtpp limit-secondary-rat-usage : Specifies a default value of 32.
no gtpp limit-secondary-rat-usage : Disables the CDR generation with limited number of secondary RAT usage information.

Suppressing Zero-Volume Secondary RAT Usage Report

Use the following configuration to suppress zero-volume Secondary RAT Usage report.

configure 
   context context_name 
      gtpp group group_name 
         gtpp suppress-secondary-rat-usage zero-volume 
         default gtpp suppress-secondary-rat-usage zero-volume 
         no gtpp suppress-secondary-rat-usage zero-volume 
         end

NOTES:

gtpp suppress-secondary-rat-usage zero-volume : Suppresses either Secondary RAT records or zero volume Secondary RAT records.
default gtpp suppress-secondary-rat-usage zero-volume : Does not suppress the zero volume secondary RAT usage records.
no gtpp suppress-secondary-rat-usage zero-volume : Does not suppress the zero volume Secondary RAT usage records.

Monitoring and Troubleshooting

This section provides information on how to monitor and troubleshoot using show commands available in support of this feature.

Show Commands and Outputs

This section provides information regarding show commands and their outputs for this feature.

show config

The output of this CLI command displays the following parameters.


Field	Description
gtpp attribute secondary-rat-usage	Specify this option to include the Secondary RAT reports field in the CDR.
gtpp suppress-secondary-rat-usage zero-volume	Enables the exclusion of the zero volume Secondary RAT reports in the CDR.
gtpp limit-secondary-rat-usage	Enables limiting the number of Secondary RAT Usage reports in CDR with the configured value.

show config verbose

The output of this CLI command displays the following parameters.


Field	Description
gtpp attribute secondary-rat-usage	Displays the Secondary RAT usage records.
gtpp suppress-secondary-rat-usage zero-volume	Displays only Secondary RAT records that is having non-zero volumes from P-GW and S-GW.
gtpp limit-secondary-rat-usage	If total received Secondary RAT records are multiples of 10, displays multiple CDR generated by P-GW and S-GW. The reported cause value will be the maximum change condition.
no gtpp limit-secondary-rat-usage	Displays Secondary RAT records for unconfigured cause.

show gtpp group

The output of this CLI command displays the following parameters.


Field	Description
Secondary RAT records present	Specifies whether the Secondary RAT record is present or not. The available options are: no yes
Limit-secondary-rat-usage	Specifies a limit for Secondary RAT usage report.

show gtpp statistics group

The output of this CLI command displays the following parameter.


Field	Description
Total PGW-CDR exceed size limit	Displays the total number of CDRs that exceeded size limit in P-GW.

Release Change Reference, StarOS Release 21.20/Ultra Services Platform Release 6.14

Bias-Free Language

Book Title

Release Change Reference, StarOS Release 21.20/Ultra Services Platform Release 6.14

Chapter Title