eMPS and WPS Support

Feature Summary and Revision History

Summary Data

Table 1. Summary Data

Applicable Product(s) or Functional Area

cnSGW-C

Applicable Platform(s)

SMI

Feature Default Setting

Disabled – Configuration required to enable

Related Documentation

Not Applicable

Revision History

Table 2. Revision History

Revision Details

Release

First introduced.

2021.02.0

Feature Description

This feature supports the following:

  • Enhanced Multimedia Priority Service (eMPS) or Wireless Priority Service (WPS)

  • eMPS GTPv2 Load/Overload Self Protection Exclusion

  • Message Priority Profiles to define priority either at global level or at each interface level (PFCP, GTP).

eMPS/WPS Support

Feature Description

This feature supports identifying the eMPS subscriber. The feature sets the message priority bit for:

  • PFCP interface towards the UP.

  • GTPC interface towards the MME and PGW.

This feature includes DSCP marking for request messages in control messages as per the configured value in the profile for eMPS subscriber.

eMPS GTPv2 Load/Overload Self Protection Exclusion Support

Feature Description

cnSGW-C supports interaction of eMPS with GTPv2 load or overload feature. It supports excluding eARPs, APNs, Emergency, or WPS calls during self-protection mode in GTPv2 load or overload feature.

By default, cnSGWc throttles the incoming GTPC messages in the self-protection mode. If cnSGWc is in self-protection mode and the overload exclude profile is configured, then the cnSGWc compares the parameters of the incoming message with the configured DNN, ARP, QCI, and message priority values.

In case of a match or the session is identified as a WPS or an emergency session, cnSGWc processes the incoming message, otherwise rejects it.

cnSGW-C can exclude the dnn-list, arp-list, and qci-list, message-priority from the rejection for incoming request messages in self-protection mode. cnSGW-C excludes this rejection in the following manner:

  • Excludes the dnn-list from rejection for any call level procedure when the subscriber APN name (NI+OI) matches with overload-exclude-profile.

  • Excludes bearer modification or creation from rejection for any new or existing ARP (Priority-Level) value.

  • Excludes bearer modification or creation from rejection for any new or existing QCI value.

  • Excludes the deleted bearer or the session operations, such as, Delete Bearer Request, Delete Session Request, Delete Bearer command from rejection irrespective of the overload-exclude-profile configuration.

To exclude the incoming GTPC traffic from a specific north-bound interface, see the Configure Overload Exclude Profile section.


Note

cnSGW-C does not support message throttling.

Feature Configuration

Configuring this feature involves the following steps:

Configuring WPS Profile

To configure this feature, use the following configuration:

config 
   profile wps wps_name 
      arp arp_value message-priority-profile msg_priority_profile_name 
      dscp dscp_value 
      message-priority [ pfcp | gtpc ]  
      end

NOTES:

  • wps wps_name —Specify the WPS service name. Must be a string.

  • arp arp_value —Specify the range of ARP levels (separated by , or -). Must be an integer or a string. WPS session is decided based on ARP.

  • message-priority-profile msg_priority_profile_name — Specifies that a message-priority profile is added in ARP list within WPS profile. WPS session is decided based on the configured ARP and the associated message priority profile inside the WPS profile.

  • dscp dscp_value —Specify the DSCP marking value in the decimal range 0-63 or hex range 0x0-0x3F. Must be a string.

Configuration Example

The following is an example configuration.


config
   profile wps wp1
     arp 2 message-priority-profile message_priority_name
   end

Configuration Verification

To verify the configuration:

show full-configuration profile wps wps1
profile wps wps1
arp 2 message-priority-profile mp1
exit

Configuring WPS-Profile and SGW-Profile Association

To configure WPS-Profile and SGW-Profile association, use the following configuration:

config 
 profile sgw sgw_name 
  wps-profile wps_name 
  end

NOTES:

  • wps-profile wps_name —Specify the Wireless Priority Service (WPS) name. Must be a string.

Configuration Example

The following is an example configuration.

config
   profile sgw sgw1
     wps-profile wp1
     end

Configuration Verification

To verify the configuration:

show running-config profile sgw
profile sgw sgw1
wps-profile wp1

Configuring WPS-Profile and DNN-Profile Association

This section describes how to configure WPS-Profile and DNN-Profile association.


Note

If WPS profile is associated with SGW profile and DNN profile, DNN profile takes the priority.

To configure WPS-Profile and DNN-Profile association, use the following configuration:

config 
 profile dnn dnn_name 
   wps-profile wps_name 
   end

Configuration Example

The following is an example configuration.

 config
   profile dnn dnn1
   wps-profile wps1
   end

Configuration Verification

To verify the configuration:

show running-config profile dnn 
profile dnn dnn1
wps-profile wps1

OAM Support

This section describes operations, administration, and maintenance information for this feature

Bulk Statistics Support

The following are the examples for eMPS messages:

sgw_pdn_emps_counters{app_name="smf",cluster="cn",data_center="cn",instance_id="0",
service_name="sgw-service",status="active"} 1
sgw_pdn_emps_stats{app_name="smf",cluster="cn",data_center="cn",instance_id="0",
service_name="sgw-service",status="release"} 7
sgw_pdn_emps_stats{app_name="smf",cluster="cn",data_center="cn",instance_id="0",
service_name="sgw-service",status="setup"} 8
gtpc_app_priority_events{app_name="smf",cluster="smf",data_center="smf",event_type=
"NumRxModifyBearerResFrmSerSuccess",instance_id="0",
interface_type="S11",priority_msg="true",service_name="gtpc-ep"} 3
gtpc_app_priority_events{app_name="smf",cluster="smf",data_center="smf",event_type=
"RxCreateSessionRes",instance_id="0",interface_type="S5E",
priority_msg="true",service_name="gtpc-ep"} 2
proto_pfcp_msg_total{app_name="smf",cluster="smf",data_center="smf",instance_id="0",
interface_type="SXA",message_direction="outbound",
message_name="N4_MSG_SESSION_ESTABLISHMENT_REQUEST",msgpriority="True",service_name=
"protocol",status="accepted",transport_type="origin"} 2
proto_pfcp_msg_total{app_name="smf",cluster="smf",data_center="smf",instance_id="0",
interface_type="SXA",message_direction="outbound",
message_name="N4_MSG_SESSION_MODIFICATION_REQUEST",msgpriority="True",service_name="protocol",
status="accepted",transport_type="origin"} 6