Packet domain event notification +CGEV

For reference, see 3GPP 27.007 Ch. 10.1.19.

These notifications are subscribed using the +CGEREP command.

Syntax descriptions are as follows:

Network detach. All active contexts are deactivated. The deactivation of individual contexts is not reported separately:

+CGEV: NW DETACH

Mobile Equipment (ME) detach:

+CGEV: ME DETACH

ME is overheated and flight mode is enabled:

+CGEV: ME OVERHEATED

Battery voltage is low:

+CGEV: ME BATTERY LOW

The ME has activated a default bearer:

+CGEV: ME PDN ACT <cid>[,<reason>]

The network has activated a dedicated bearer:

+CGEV: NW ACT <p_cid>,<cid>,<event_type>

The network has deactivated a default bearer:

+CGEV: NW PDN DEACT <cid>

The User Equipment (UE) has deactivated a default bearer:

+CGEV: ME PDN DEACT <cid>

The network has deactivated a dedicated bearer:

+CGEV: NW DEACT <p_cid>,<cid>,<event_type>

The UE has deactivated a dedicated bearer:

+CGEV: ME DEACT <p_cid>,<cid>,<event_type>

The network has modified a bearer:

+CGEV: NW MODIFY <cid>,<change_reason>,<event_type>

The UE has modified a bearer:

+CGEV: ME MODIFY <cid>,<change_reason>,<event_type>

IPv6 link is up for the default bearer:

+CGEV: IPV6 <cid>

IPv6 address resolution or refresh failure:

+CGEV: IPV6 FAIL <cid>

Requested procedure is restricted:v2.0.x≥1

+CGEV: RESTR <cause>,<validity>

Requested procedure is restricted:v2.0.x≥2

+CGEV: RESTR <cause>,<validity>,<cid>,<remaining_time_regular>,<remaining_time_exceptional>

Configuration of Access Point Name (APN) rate control:

+CGEV: APNRATECTRL CFG <cid>,<rate>,<time_window>,<exceptional_data_allowed>,<additional_rc_rate>,
<additional_rc_time_window>

Status of APN rate control:

+CGEV: APNRATECTRL STAT <cid>,<status>,<remaining_time>,<exceptional_data_allowed>,<additional_rc_status>,
<additional_rc_remaining_time>

Status indicating if exceptional data is allowed. Only changes in allowance are notified:

+CGEV: EXCE STATUS <exce_status>

<cid>

Integer, 0–10. Context identifier for an associated context.

255 – RESTR is valid for all context identifiers.v2.0.x≥2

<reason>

0 – Only IPv4 allowed

1 – Only IPv6 allowed

2 – Only single access bearers allowed

3 – Only single access bearers allowed and context activation for a second address type bearer was not successful.

<change_reason>

Integer. A bitmap that indicates what kind of change has occurred. The <change_reason> value is determined by adding together all the applicable bits.

Bit 1 – TFT changed

Bit 2 – Quality of Service (QoS) changed

Bit 3 – WLAN offload changed

<cid_other>

Integer, 0–10. Indicates the context identifier allocated for an Mobile Termination (MT)-initiated context of a second address type. This parameter is included only if the <reason> parameter indicates that only single address bearers are allowed.

<p_cid>

Integer, 0–10. Context identifier for an associated default context.

<event_type>

0 – Informational event

1 – Information request. Acknowledgement is required, and it can be either accept or reject.

<cause>

Restriction cause

1 – Radio Policy Manager (RPM). Procedure restricted by RPM.

2 – Throttling. Procedure restricted by 3GPP or operator-specific throttling.

3 – Invalid configuration. Procedure restricted by invalid context configuration.

<validity>

Validity of restriction

1 – Permanent restriction. Enabling requires a power-off, Universal Integrated Circuit Card (UICC) change, or a configuration change.

2 – Temporary restriction. Enabling requires, for example, back-off timer expiry.

<number_of_packets>

0–16 777 215 – Number of data packets that the UE is allowed to send during the time period indicated in <time_window>.

Values 0,0 of <number_of_packets>,<time_window> indicate that APN rate control is not configured.

<time_window>

60–604 800 – Time window in seconds (1 minute to 1 week).

<remaining_time_regular>v2.0.x≥2

Integer. Remaining time for regular data restriction in seconds. Range 0-4294967295.

The maximum value is reported when the restriction is active, but the duration is unknown. The minimum value is reported when regular data usage is permitted.

<remaining_time_exceptional>v2.0.x≥2

Integer. Remaining time for exceptional data restrictions in seconds. Range 0-4294967295.

The maximum value is reported when the restriction is active, but the duration is unknown. The minimum value is reported when exceptional data usage is permitted.

<exceptional_data_allowed>

Indicates if exceptional data is allowed when APN rate control blocks the sending of data. Valid only if additional APN rate control is not configured (<additional_rc_status> is 2).

0 – Not allowed.

1 – Allowed.

<additional_rc_rate>

0–65535 – Additional configured exceptional data rate. Number of additional exceptional data packets that the UE is allowed to send when <rate> is exceeded during the time period indicated in <additional_rc_time_window>.

Values 0,0 of <additional_rc_rate>,<additional_rc_time_window> indicate that additional APN rate control is not configured.

If additional APN rate control is configured, it controls the sending of exceptional data, and the value of<exceptional_data_allowed> is 0.

<additional_rc_time_window>

60–604 800 – Additional time window in seconds (1 minute to 1 week).

The time window is used to calculate exceptional data packets configured at <additional_rc_rate>.

<status>

0 – OFF. APN rate control does not block uplink data.

1 – ON. APN rate control blocks uplink data.

2 – APN rate control is not configured for this CID.

<remaining_time>

0–604 800 – Remaining uplink data blocking time in seconds when status is 1. Can be 0 if less than a full second remains.

<additional_rc_status>

0 – APN rate control is configured for exceptional data and currently not blocking exceptional uplink data.

1 – APN rate control is configured for exceptional data and currently blocking exceptional uplink data.

2 – APN rate control is not configured for exceptional data for this CID.

<additional_rc_remaining_time>

0–604 800 – Remaining exceptional uplink data blocking time in seconds when <additional_rc_status> is 1.

Can be 0 if less than a full second remains, but rate control blocks exceptional data if <additional_status> is 1. 0 when <additional_rc_status> is 0.

<exce_status>

0 – Exceptional data not allowed.

1 – Exceptional data allowed.

The following notification example shows that an initial Packet Data Network (PDN) connection is activated:

+CGEV: ME PDN ACT 0

The following notification example shows that the device is detached from network:

+CGEV: ME DETACH

The following notification example shows a restriction caused by throttling with temporary validity.

+CGEV: RESTR 2,2