Support for 187 and 188 Information Element Types on S2b Interface

Feature Summary and Revision History

Summary Data

Applicable Product(s) or Functional Area

P-GW

Applicable Platform(s)

  • ASR 5500

  • VPC-DI

  • VPC-SI

Feature Default

Enabled - Always On

Related Changes in This Release

Not Applicable

Related Documentation

P-GW Administration Guide

Revision History

Revision Details

Release

Support for inclusion of 187 and 188 Information Element types on S2b Interface.

21.26.17

Feature Description

During detection and handling of late arriving requests, a GTP-C entity initiates a Create Session Request (ePDG) with the Origination Time Stamp message. This indicates the absolute time at which the request is initiated and the Maximum Wait Time indicating the maximum time to complete the processing of the request. The Maximum Wait Time, together with the Origination Time Stamp, indicates the absolute time at which the request times out at the originating entity. The receiving node utilizes the same time stamp and maximum wait time to identify if it is still a valid message and if it should process it. If the message is processed, the intermediate nodes replicate the time stamp and maximum wait time in messages that are generated by the node toward other peers. Each network element compares the Time Stamp and its own synced Network Time Protocol (NTP) time to ensure that stale messages are not processed.

If any session-related information is created and before the network element responds, the maximum wait time has passed, the network element ensures to clear or release stale session information.

In ePDG, according to the 3GPP 29.274 version, the Origination Time Stamp (188) and Maximum Wait Time (187) Information Element types (IE) are supported into the messages instead of 255 IE type. The feature is only supported for s2b, and s5/s8 interface. P-GW supports receiving and sending the Origination Time Stamp and Max Wait Time IEs / AVPs in these interfaces such a S2b, Gx, and S6b.

How it Works

This section describes the call flow procedures that are related to messages and nodes carrying Origination Time Stamp and Maximum Wait Time (MWT):

The IEs obtained from ePDG send messages toward P-GW, PCRF, and AAA nodes without any modification.

Call Flow

Figure 1. Displays IEs Accross nodes
Table 1. Call Flow Procedures for Origination Time Stamp and Maximum Wait Time (MWT)

Step

Message Type

Description

1

Create Session Request

The ePDG includes Origination Time Stamp and Maximum Wait time on S2b interface.

When present, the Origination Time Stamp contains the Universal Time Code (UTC) time when the originating entity initiated the request, and the Maximum Wait Time contains the duration (number of milliseconds since the Origination Time Stamp) during which the originator of the request waits for a response.

2

Credit Control Request-Initial Request

The IEs received in P-GW will be sending to PCRF through Gx interface. This gets included only in the initial request of CCR.

3

Authentication Authorization Request

The IEs received in P-GW sends messages to AAA through S6b interface.

Supported RAT Types

The Origination Time Stamp and Maximum Wait Time IEs are supported for WLAN RAT type. The received IEs in P-GW sends messages on Gx and S6b interfaces.

Handling Handover

Handover (HO) from LTE to WLAN and vice versa is supported to include Origination Time Stamp and Maximum Wait Time IEs. During the Handoff from LTE to Wi-Fi or vice versa, the Origination Time Stamp and Maximum Wait Time IEs sends messages on S5 and S2b interfaces and not on Gx and S6b interfaces.

In case of LTE to WLAN HO, if a new create session request comes from ePDG, then that request is considered as a new CSR and the handover process is same as the initial attach for new IEs.