12 Information Elements

29.2753GPPProxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocolsRelease 17Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

12.1 Additional Proxy Mobile IPv6 Information Elements

12.1.1 3GPP-Specific PMIPv6 Information Elements

12.1.1.0 General

This specification requires the encoding of additional 3GPP-specific Information Elements for PMIPv6 with the 3GPP Mobility Option, as defined by 3GPP TS 29.282 [24]. The 3GPP specific Information Elements defined by this specification are listed in the table 12.1.1.0-1.

Table 12.1.1.0-1: 3GPP Specific PMIPv6 Information Elements

3GPP Specific PMIPv6 Information Element	3GPP Specific PMIPv6 Information Element Description
Protocol Configuration Options	3GPP PCO data, in the format from 3GPP TS 24.008 [16] subclause 10.5.6.3, starting with octet 3.
3GPP Specific PMIPv6 error code	3GPP Vendor-Specific PMIPv6 error code, as specified in subclause 12.1.1.1
PDN GW IP address	PDN GW IP address, as specified in subclause 12.1.1.4
DHCPv4 Address Allocation Procedure Indication	DHCPv4 Address Allocation Procedure Indication, as specified in subclause 12.1.1.5.
Fully Qualified PDN Connection Set Identifier	FQ-CSID as specified in subclause 12.1.1.2
PDN Type Indication	PDN type indication as specified in subclause 12.1.1.3
Charging ID	Charging ID as specified in subclause 12.1.1.6
Selection Mode	Selection Mode as specified in subclause 12.1.1.7
Charging Characteristics	Subclause 12.1.1.8
Serving Network	Subclause 12.1.1.9
Mobile Equipment Identity	Subclause 12.1.1.10
MSISDN	Subclause 12.1.1.11
APN Restriction	Subclause 12.1.1.12
Maximum APN Restriction	Subclause 12.1.1.13
Unauthenticated IMSI	Subclause 12.1.1.14
PDN Connection ID	Subclause 12.1.1.15
PGW Back-Off Time	Subclause 12.1.1.16
Signalling Priority Indication	Subclause 12.1.1.17
Static IP Address Allocation Indication	Subclause 12.1.1.18
Additional Protocol Configuration Options	Subclause 12.1.1.19
MME/SGSN Identifier	Subclause 12.1.1.20
End Marker Notification	Subclause 12.1.1.21
Trusted WLAN Mode Indication	Subclause 12.1.1.22
UE Time Zone	Subclause 12.1.1.23
Access Network Identifier Timestamp	Subclause 12.1.1.24
Logical Access ID	Subclause 12.1.1.25
Origination Time Stamp	Subclause 12.1.1.26
Maximum Wait Time	Subclause 12.1.1.27
TWAN Capabilities	Subclause 12.1.1.28

Depending on the need for 3GPP-specific information content, there several items of this information element may be added to the PBU, PBA, BRI, BRA, UPN or UPA.

The subtype for a 3GPP specific PMIPv6 Information Element is defined in 3GPP TS 29.282 [24]. The data format of the 3GPP specific PMIPv6 Information Element is defined in this specification. If the data format is defined by another specification, that specification shall be referenced in the table above.

12.1.1.1 3GPP Specific PMIPv6 error code

Proxy Binding Acknowledgement (PBA) and Binding Revocation Acknowledgment (BRA) contain a mandatory Status information element and also may contain a 3GPP Specific PMIPv6 Error Code (3GSPEC) information element, which is coded within Mobility Options field.

NOTE: ETF RFC 5213 [4] and IETF RFC 6275 [8] specify PMIPv6 Status values for a PBA message for indicating the acceptance of a message, or for reporting an error. Up-to-date values for the Status field are specified in the IANA registry of assigned numbers [32]. IETF RFC 5846 [6] specifies PMIPv6 Status values for the BRA message. Up-to-date BRA status values are specified in the IANA registry of assigned numbers [33].

Binding Revocation Indication (BRI) may contain a 3GPP Specific PMIPv6 Error Code (3GSPEC) information element, which is coded within Mobility Options field.

The purpose of the 3GSPEC information element, which is depicted in Figure 12.1.1.1-1 is to carry a GTPv2 Cause value within PMIPv6 messages. 3GPP TS 29.274 [22] specifies GTPv2 Cause values.

Bits
Octets	8	7	6	5	4	3	2	1
1	3GPP Specific PMIPv6 Error Code

Figure 12.1.1.1-1: 3GPP Specific PMIPv6 Error Code

If MAG/SGW receives a 3GSPEC IE in Proxy Binding Acknowledgement message from LMA/PGW, which requires that the MAG/SGW shall send a GTPv2 message to MME/SGSN, then the MAG/SGW shall copy 3GSPEC value into GTPv2 Cause IE . If in such case, the MAG/SGW does not receive 3GSPEC IE with PBA, depending on the overall meaning of the PMIPv6 Status IE the MAG/SGW shall send to MME/SGSN one of the following GTPv2 Cause values with CS bit set to 1:

– "Request Accepted" (decimal 16), if the received PMIPv6 Status indicates PBU acceptance.

– "Request rejected for a PMIP reason" (decimal 112), if the received PMIPv6 Status indicates PBU rejection.

If MAG/SGW receives a 3GSPEC IE in Binding Revocation Indication message from LMA/PGW, which requires that the MAG/SGW shall send a GTPv2 message to MME/SGSN, then the MAG/SGW shall copy 3GSPEC value into GTPv2 Cause IE with CS bit set to 1.

If MAG/SGW receives a Cause IE with a GTPv2 message, which requires sending a Binding Revocation Acknowledgement message to LMA/PGW, the MAG/SGW shall copy the GTPv2 Cause value into the 3GSPEC IE.

12.1.1.2 Fully Qualified PDN Connection Set Identifier (FQ-CSID)

A fully qualified PDN Connection Set Identifier (FQ-CSID) identifies a set of PDN connections belonging to an arbitrary number of UEs on a node such as a MME, SGW or PGW. The FQ-CSID is generated by the MAG, the LMA and any other node such as the MME for 3GPP access. It is generated for each new PDN connection, and it is used in case of partial node failure to identify the PDN connections associated with a Connection Set Identifier.

The FQ-CSID is coded as follows:

	Bits
Octets	8	7	6	5	4	3	2	1
1	Node-ID Type				Number of CSIDs= m
2 to p	Node-ID
(p+1) to (p+2)	First PDN Connection Set Identifier (CSID)
(p+3) to (p+4)	Second PDN Connection Set Identifier (CSID)
…	…
(m-1) to m	m"th PDN Connection Set Identifier (CSID)

Figure 12.1.1.2-1: FQ-CSID

The details of each field and value are specified in 3GPP TS 29.274[22].

12.1.1.3 PDN Type Indication

The purpose of the PDN type indication option is to indicate the GW decision to change the PDN type and a cause for the change. This attribute is set by the LMA in the PBA.

The MAG shall set the PDN type accordingly, if this option is present in the PBA.

Bits
Octets	8	7	6	5	4	3	2	1
1	PDN type
2	Cause

Figure 12.1.1.3-1: PMIPv6 PDN type indication

The following defines the value of the PMIPv6 PDN type indication.

PDN type value

#1: IPv4

#2: IPv6

Cause value as defined in 3GPP TS 29.274[13]

#18: New PDN type due to network preference;

12.1.1.4 PDN GW IP address

The purpose of the PDN GW IP address information element is to carry the IP address of the PDN GW to which the receiving Serving GW shall send a PBU on the chained S8 interface. This information element shall be included in a PBU for initial attach or handover sent on S2a or S2b interface for S2a/S2b – PMIP based S8 chaining scenario.

This information element shall be included in an Update Notification message according to the conditions specified in subclause 20.2.7.1 of 3GPP TS 23.007 [13].

The content and encoding of the PDN GW IP address is depicted on Figure 12.1.1.4-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1-4/16	IPv4 or IPv6 Address

Figure 12.1.1.4-1: PDN GW IP Address

12.1.1.5 DHCPv4 Address Allocation Procedure Indication

The purpose of the DHCPv4 Address Allocation option is to indicate that DHCPv4 is to be used in allocating the IPv4 address to the UE if the option is present in the PBA message.

12.1.1.6 Charging ID

The Charging ID is defined in figure 12.1.1.6-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1-4	Charging ID value

Figure 12.1.1.6-1: Charging ID

12.1.1.7 Selection Mode

Selection Mode indicates they way the MME or SGSN selected the APN: whether a subscribed APN was selected, or whether a non-subscribed APN sent by a UE or a non-subscribed APN chosen by the SGSN was selected. The Selection Mode is defined in 3GPP TS 23.060 [23]

The encoding of the Selection Mode is shown in Figure 12.1.1.7-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1	Reserved						Selection Mode

Figure 12.1.1.7-1: Selection mode

The reserved bits shall be set to 1 by the MAG and not processed by the LMA.

The defined Selection Mode values are shown in Table 12.1.1.7-1.

Table 12.1.1.7-1: Selection Mode

Value	Selection mode value
0	MS or network provided APN, subscribed verified
1	MS provided APN, subscription not verified
2	Network provided APN, subscription not verified
3	For future use. Shall not be sent. If received, shall be interpreted as the value ‘2’.

12.1.1.8 Charging Characteristics

The Charging Characteristics information element is defined in 3GPP TS 32.251 [25] and is a way of informing both the SGW and PGW of the rules for producing charging information based on operator configured triggers. For the encoding of this information element see 3GPP TS 32.298 [26].

The Charging Characteristics is defined in figure 12.1.1.8-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1-2	Charging Characteristics value

Figure 12.1.1.8-1: Charging Characteristics

12.1.1.9 Serving Network

Serving Network identifies the serving network the UE is attached to. The format of the Serving Network 3GPP-specific Information Element is defined below.

	Bits
Octets	8	7	6	5	4	3	2	1
1	MCC digit 2				MCC digit 1
2	MNC digit 3				MCC digit 3
3	MNC digit 2				MNC digit 1

Figure 12.1.1.9-1

12.1.1.10 Mobile Equipment Identity

The purpose of the Mobile Equipment Identity (MEI) information element is used to convey the UE’s terminal identity from the Serving GW, TWAN or ePDG to the PDN GW over the S5/S8, S2a or S2b interface.

The encoding of the MEI is depicted in Figure 12.1.1.10-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1 to 8	Mobile Equipment Identity

Figure 12.1.1.10-1: Mobile Equipment Identity (MEI)

The MEI contains either the IMEI or IMEISV in the format defined in subclause 6.2 of 3GPP TS 23.003 [12].

The MEI shall contain the IMEISV if it is available. If only the IMEI is available, then the last semi‑octet of octet 8 of MEI shall be set to "1111". Both IMEI and IMEISV are TBCD encoded, where IMEI is 15 BCD digits and IMEISV is 16 BCD digits. Bits 5 to 8 of octet n encodes digit 2n, bits 1 to 4 of octet n encodes digit 2n-1. Digits are packed contiguously with no internal padding.

NOTE: This encoding follows that of the IMEI(SV) field in the International Mobile Equipment Identity (and Software Version) (IMEI(SV)) information element defined in clause 7.7.53 of 3GPP TS 29.060 [28].

12.1.1.11 MSISDN

The purpose of the MSISDN information element is used to convey the user’s MSISDN from the Serving GW to the PDN GW over the S5/S8 interface, from the trusted non-3GPP access network to the PDN-GW over S2a and from ePDG to the PDN-GW over S2b. MSISDN is defined in 3GPP TS 23.003 [12].

The content and encoding of the MSISDN is depicted on Figure 12.1.1.11-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1	Number digit 2				Number digit 1

n	Number digit m				Number digit m-1

Figure 12.1.1.11-1: MSISDN

Octets 1 to n represent the MSISDN value in international number format as described in ITU-T Rec E.164 [29], encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111".

12.1.1.12 APN Restriction

The APN Restriction is defined in figure 12.1.1.12-1. The APN Restriction value is specified in 3GPP TS 29.274 [22].

	Bits
Octets	8	7	6	5	4	3	2	1
1	APN Restriction value

Figure 12.1.1.12-1: APN Restriction

12.1.1.13 Maximum APN Restriction

The Maximum APN Restriction is defined in figure 12.1.1.13-1. The Maximum APN Restriction value is specified in 3GPP TS 29.274 [22].

	Bits
Octets	8	7	6	5	4	3	2	1
1	Maximum APN Restriction value

Figure 12.1.1.13-1: Maximum APN Restriction

12.1.1.14 Unauthenticated IMSI

The purpose of the Unauthenticated IMSI information element is used to convey the user’s IMSI for the emergency attached UE with an IMSI which is not authenticated by the network. The format of IMSI is defined in 3GPP TS 23.003 [12].

The content and encoding of the Unauthenticated IMSI is depicted on Figure 12.1.1.14-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1	Number digit 2				Number digit 1

n	Number digit m				Number digit m-1

Figure 12.1.1.14-1: Unauthenticated IMSI

Octets 1 to n represent the IMSI value in international number format as described in ITU-T Rec E.164 [29], encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111". The maximum number of digits is 15.

12.1.1.15 PDN Connection ID

The purpose of the PDN Connection ID information element is used to convey the PDN Connection ID.

The content and encoding of the PDN Connection ID is depicted on Figure 12.1.1.15-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1	Spare (all bits set to 0)				PDN Connection ID

Figure 12.1.1.15-1: PDN Connection ID

NOTE: The format of the PDN connection ID is aligned with EPS bearer ID defined for GTPv2 in 3GPP TS 29.274 [22].

12.1.1.16 PGW Back-Off Time

The PGW Back-Off Time information element is coded as shown in figure 12.1.1.16-1. The timer unit and timer value are specified in 3GPP TS 29.274 [22].

Bits
Octets	8	7	6	5	4	3	2	1
1	Timer unit			Timer value

Figure 12.1.1.16-1: PGW Back-Off Time

12.1.1.17 Signalling Priority Indication

The Signalling Priority Indication information element contains signalling priority indications received from the UE for a specific PDN connection.

The Signalling Priority Indication information element is coded as shown in figure 12.1.1.17-1.

Bits
Octets	8	7	6	5	4	3	2	1
1	Spare							LAPI

Figure 12.1.1.17-1: Signalling Priority Indication

The following bits within Octet 1 shall indicate:

– Bit 8 to 2 – Spare, for future use and set to zero.

– Bit 1 – LAPI (Low Access Priority Indication): This bit defines if the UE indicated low access priority when establishing the PDN connection. It shall be encoded as the Low Priority parameter of the Device Properties IE in 3GPP TS 24.008 [16]. The receiver shall assume the value "0" if the Signalling Priority Indication IE is applicable for a message but not included in that message by the sender. The low access priority indication may be included in charging records.

12.1.1.18 Static IP Address Allocation Indication

The Static IP Address Allocation Indication information element contains Static IP Address Allocation Indication for the Handover procedures. These indications are equivalent for the Static IPv4/IPv6 Address Flag defined in 3GPP TS 29.274 [22].

The Static IP Address Allocation Indication information element is coded as shown in figure 12.1.1.18-1.

Bits
Octets	8	7	6	5	4	3	2	1
1	Spare						S6PI	S4AI

Figure 12.1.1.18-1: Static IP Address Allocation Indication

The following bits within Octet 1 shall indicate:

– Bit 8 to 3 – Spare, for future use and set to zero.

– Bit 2 – S6PI (Static IPv6 Home Network Prefix Indication): if this bit is set to 1, it indicates that IPv6 Home Network Prefix is statically allocated.

– Bit 1 – S4AI (Static IPv4 Address Indication): if this bit is set to 1, it indicates that IPv4 address is statically allocated.

12.1.1.19 Additional Protocol Configuration Options

The Additional Protocol Configuration Options IE contains additional 3GPP protocol configuration options information. The IE is in the same format as the PCO IE specified in 3GPP TS 24.008 [16] subclause 10.5.6.3, starting with octet 3.

12.1.1.20 MME/SGSN Identifier

The purpose of the MME/SGSN Identifier information element is to carry the IP address of the MME/SGSN. The content and encoding of the MME/SGSN Identifier is depicted on Figure 12.1.1.20-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1-4/16	IPv4 or IPv6 Address

Figure 12.1.1.20-1: MME/SGSN Identifier

12.1.1.21 End Marker Notification

The purpose of the End Marker Notification information element is used to convey the End Marker Notification.

The content and encoding of the End Marker Notificaton is depicted on Figure 12.1.1.21-1.

Bits
Octets	8	7	6	5	4	3	2	1
1	Spare							EMN

Figure 12.1.1.21-1: End Marker Notification

The following bits within Octet 1 shall indicate:

– Bit 8 to 2 – Spare, for future use and set to zero.

– Bit 1 – EMN (End Marker Notification): This bit shall be set to the value "1".

12.1.1.22 Trusted WLAN Mode Indication

The purpose of the Trusted WLAN Mode Indication information element is to convey the selected trusted WLAN Mode.

The content and encoding of the Trusted WLAN Mode Indication is depicted on Figure 12.1.1.22-1.

Bits
Octets	8	7	6	5	4	3	2	1
1	Spare						MCM	SCM

Figure 12.1.1.22-1: Trusted WLAN Mode Indication

The following bits within Octet 1 shall indicate:

– Bit 8 to 3 – Spare, for future use and set to zero.

– Bit 2 –MCM (Multiple-connection mode Indication): if this bit is set to 1, it indicates that the Multiple-connection mode is used.

– Bit 1 –SCM (Single-connection mode Indication): if this bit is set to 1, it indicates that the Single-connection mode is used.

12.1.1.23 UE Time Zone

UE Time Zone is used to indicate the offset between universal time and local time in steps of 15 minutes of where the UE currently resides. The "Time Zone" field uses the same format as the "Time Zone" IE in 3GPP TS 24.008 [5].

The content and encoding of the UE Time Zone is depicted on Figure 12.1.1.23-1.

Bits
Octets	8	7	6	5	4	3	2		1
1	Time Zone
2	Spare							Daylight Saving Time

Figure 12.1.1.23-1: UE Time Zone

The value of the Time Zone field in octet 1 represents the time zone adjusted for daylight saving time.

The following bits within Octet 2 shall indicate:

– Bit 8 to 3 – Spare, for future use and set to zero.

– Bit 2 to 1 – The value of the Daylight Saving Time field specifies the adjustment that has been made. Possible values for the Daylight Saving Time field are given below in Table 12.1.1.23-2

Table 12.1.1.23-1 Possible values for the "Daylight Saving Time" field and their meanings.

Daylight Saving Time	Value (binary)
Daylight Saving Time	Bit 2	Bit 1
No adjustment for Daylight Saving Time	0	0
+1 hour adjustment for Daylight Saving Time	0	1
+2 hours adjustment for Daylight Saving Time	1	0
Spare	1	1

12.1.1.24 Access Network Identifier Timestamp

The Access Network Identifier Timestamp indicates the UTC time when the Access Network Identifier information was acquired. The content and encoding of the Access Network Identifier Timestamp is depicted on Figure 12.1.1.24-1. Octets 1 to 4 are encoded in the same format as the first four octets of the 64-bit timestamp format as defined in section 6 of IETF RFC 5905 [40].

NOTE: The encoding is defined as the time in seconds relative to 00:00:00 on 1 January 1900

	Bits
Octets	8	7	6	5	4	3	2	1
1-4	Access Network Identifier Timestamp

Figure 12.1.1.24-1: Access Network Identifier Timestamp

12.1.1.25 Logical Access ID

The purpose of the Logical Access ID information element is to convey the Logical Access ID. The Logical Access ID is implemented by providing both the Relay Identity which is either an IP Address or and FQDN along with the allocated Circuit-ID.

The Logical Access ID is depicted on Figure 12.1.1.25-1.

	Bits
Octets	8	7	6	5	4	3	2	1
1	Relay Identity Type
2	Relay Identity Length
3 to k	Relay Identity
(k+1) to (k+2)	Circuit-ID Length
(k+3) to q	Circuit-ID

Figure 12.1.1.25-1: Logical Access ID

The Relay Identity Type is encoded in octet 1. It indicates the type of identity as described in Table 12.1.1.25-1. The Relay Identity Length is encoded in the octet 2. It indicates the length of the relay identity. The octets 3 to K contains the Relay Identity. If the Relay Identity type is set to 1 (i.e. an FQDN), it is encoded as described in section 3.1 of IETF RFC 1035 [31] but excluding the trailing zero byte. The Circuit-ID length in the octet (k+1) to (k+2) indicates the length of the Circuit-ID. The Circuit-ID is as defined in IETF RFC 3046 [42], it is encoded in octets (k+3) to q as an Octetstring and provided by the Relay.

Table 12.1.1.25-1: Relay Identity Type

Relay Identity Type	Values (Decimal)
IPv4 or IPv6 Address	0
FQDN	1

12.1.1.26 Origination Time Stamp

The Origination Time Stamp information element is coded as shown in figure 12.1.1.26-1. The Origination Time Stamp value shall be encoded as specified in 3GPP TS 29.274 [22].

	Bits
Octets	8	7	6	5	4	3	2	1
1-6	Origination Time Stamp value

Figure 12.1.1.26-1: Origination Time Stamp

12.1.1.27 Maximum Wait Time

The Maximum Wait Time information element is coded as shown in figure 12.1.1.27-1. The Maximum Wait Time value shall be encoded as specified in 3GPP TS 29.274 [22].

	Bits
Octets	8	7	6	5	4	3	2	1
1-2	Maximum Wait Time value

Figure 12.1.1.27-1: Maximum Wait Time

12.1.1.28 TWAN Capabilities

The purpose of the TWAN Capabilities information element is to convey the capabilities supported by the TWAN to the PGW.

The content and encoding of the TWAN Capabilities is depicted on Figure 12.1.1.28-1.

Bits
Octets	8	7	6	5	4	3	2	1
1	Spare							WPMSI

Figure 12.1.1.28-1: TWAN Capabilities

The following bits within Octet 1 shall indicate:

– Bit 8 to 2 – Spare, for future use and set to zero.

– Bit 1 – WLCP PDN Connection Modification Support Indication (WPMSI): if this bit is set to 1, it indicates that the TWAN supports the WLCP PDN Connection Modification procedure. This indication is used by the P-CSCF restoration extension procedure for TWAN access (see 3GPP TS 23.380 [36]).