To configure CF support under the active charging service, use the following configuration:

configure 
   active-charging service service_name 
      content-filtering category policy-id cf_policy_id 
         analyze priority priority { all | category category 
          | x-category xcategory } action { allow | 
          content-insert content_string | discard | redirect-url url | 
          terminate-flow | www-reply-code-and-terminate-flow reply_code  
          } [ edr edr_format] failure-action { allow |  
          content-insert content_string | discard | redirect-url url 
          | terminate-flow | www-reply-code-and-terminate-flow reply_code} 
          [ edr edr_format] 
          end 

To configure CF under the rulebase, use the following configuration:

configure 
   active-charging service service_name 
      content-filtering category policy-id cf_policy_id 
      content-filtering mode category static-only 
      end 

To configure CF under the APN, use the following configuration:

configure 
   context context_name 
      apn apn_name 
         content-filtering category policy-id cf_policy_id 
         end 

The CF categories are configured under the active charging service under specific policy IDs. The rulebase and APN also have an associated policy ID. For any session, one policy ID can be associated with the session at anytime. The categories configured under that CF policy ID are applicable for the session on the UPF.

The PCF can override the CF policy ID by sending this value on the N7 interface. For this purpose, a proprietary IE is available in the YAML definition for the N7 interface. The hierarchy for the CF policy ID is as follows:

smPolicyDecision 
   ciscoAvpSet: 
      cfPolicyId: uint32 value 

When the PCF does not send a CF policy ID, the existing CF policy ID in the rulebase configuration or the policy ID configured in the APN configuration is selected, in the order of precedence. This CF policy ID value is sent to the UPF in PFCP Session Establishment Request message in the "Subscriber Parameters" attribute. During PDU Session Modification, if the PCF changes the CF policy ID, the ID is sent to the UPF in PFCP Session Modification Request message.

The Event Logging feature captures procedure-level information per subscriber. Upon completing a procedure, either successfully or unsuccessfully, the SMF generates a procedure summary or event report logging the event.

The EDR generation per procedure is configurable. For configuration details, see the Configure EDR Files for Generation section in this guide.

The following table lists the supported procedures and the corresponding IDs.

Further, the SMF captures event-level information per procedure. The following table provides details on the subscriber events and the respective event IDs.

The events captured per procedure are configurable. For configuration details, see the Configure EDR Files for Generation section in this guide.

The following tables list the detailed event record for the PDU Session Create and Delete procedures.

For details on the listed attributes, see the table in the EDR Transaction File section.

NOTES:

• Userplane-status is of type number. The number can be one of the following:

  • UpStateNone = 0

  • UpStateEstablishing = 1 // UPF Session is being established or setup

  • UpStateActivating = 2 // UPF Session is being modified to Activate Access Tunnel

  • UpStateActivated = 3 // UPF Session Active for Access & Core Tunnel

  • UpStateDeactivating = 4 // UPF Session is being modified to Deactivate Access Tunnel

  • UpStateDeactivated = 5 // UPF Session Deactivated for Access, valid Core Tunnel Only

  • UpStateModifying = 6 // UPF Session is being modified for QoS/flow parameters

  • UpStateDeleting = 7 // UPF Session is being Released

  • UpStateDeleted = 8 // UPF Session is Released

• PduSessionType is of type number. The number can be one of the following:

  • UnknownSessionType = 0

  • Ipv4PduSession = 1

  • Ipv6PduSession = 2

  • Ipv4V6PduSession = 3

    Unstrutured = 4

    Ethernet = 5

    FutureUsePduSessionType = 7

• SSC mode is of type number. The number can be one of the following:

  • UnknownSscMode = 0

  • SscMode1 = 1

  • SscMode2 = 2

  • SscMode3 = 3

  • DupSscMode1 = 4

  • DupSscMode2 = 5

  • DupSscMode3 = 6

  • FutureUseSscMode = 7

• Eps Iwk (Type: Number)

  • EpsInterworkingIndication_DummyEnum = 0

  • EpsInterworkingIndication_NONE = 1

  • EpsInterworkingIndication_WITH_N26 = 2

  • EpsInterworkingIndication_WITHOUT_N26 = 3

• Roaming status (Type: Number)

  • ROAMING_STATUS_NONE = 0

  • ROAMING_STATUS_HOMER =1 //HOMER

  • ROAMING_STATUS_VISITOR_LBO =2 //LBO

  • ROAMING_STATUS_VISITOR_HR = 3 //IN-HR

  • ROAMING_STATUS_ROMER = 4 //OUT-HR

• PreemptionCapability (type: Number)

  5G:

  • 0: "PreemptionCapability_DummyEnum",

  • 1: "NOT_PREEMPT",

  • 2: "MAY_PREEMPT",

  Others:

  • 0: Disabled

  • 1: Enabled

• PreemptionVulnerability (type: Number)

  5G:

  • 0: "PreemptionVulnerability_DummyEnum",

  • 1: "NOT_PREEMPTABLE",

  • 2: "PREEMPTABLE",

• Disconnect-Reason (type: String)

  Disconnect-Reason contains a self-explanatory string. If it holds a number, then the string interpretation is as follows:

  • PduRelReason_Error = 1

  • PduRelReason_SessIdleTimeout = 2

  • PduRelReason_SessCpIdleTimeout = 3

  • PduRelReason_SessAbsoluteTimeout = 4

Procedure EDR Example:

1,2021/03/18 13:43:40.892,1448,imsi-123456789012345,1287,N11SmContextCreateReq,
.
.
.
3,1313,V1,Success,201,1,,3,1316,V1,Success,200,1,,3,1319,V1,Success,201,1,,3,1287,V1,
imsi-123456789012345,imei-123456786666660,123456789012345,9999988888,msisdn-9999988888,
Success,,1,0,,,193|,,,,,,,NR,3,3329,V1,imsi-123456789012345,imei-123456786666660,msisdn-9999988888,
Success,201,1,3|1;2;7|3000 mbps|4000 mbps|1000 mbps|2000 mbps,20 kbps|20 kbps,,3,3332,V1,Success,
204,1,,3,3585,V1,Success,201,1,,3,524,V1,Success,,1,Request_Accepted,3,1299,V1,Success,200,194|,
77|,,,,1,1,intershat,2|1|0|2|128|1|filters:0;3;1;;|3|1|0|2|192|1|filters:0;3;1;;|1|1|1|1|255|1|
filters:0;3;1;;,5||0 kbps|0 kbps|0 kbps|0 kbps|3||6000 mbps|8000 mbps|2000 mbps|4000 mbps,20 kbps|
20 kbps,N1_N2_TRANSFER_INITIATED,12.0.4.0|,2|Abf123||,0

In the preceding example, the initial entries represent the transaction EDRs and last part provided here represents the procedure-level EDRs.