7.3 Information Elements

29.2723GPPEvolved Packet System (EPS)Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocolRelease 17TS

7.3.1 General

The following table specifies the Diameter AVPs defined for the S6a/S6d interface protocol, the S7a/S7d interface protocol and the S13/S13′ interface protocol, their AVP Code values, types, possible flag values and whether or not the AVP may be encrypted. The Vendor-ID header of all AVPs defined in this specification shall be set to 3GPP (10415).

For all AVPs which contain bit masks and are of the type Unsigned32, e.g., ULR-Flags, DSR-Flags, PUA-Flags, etc., bit 0 shall be the least significant bit. For example, to get the value of bit 0, a bit mask of 0x0001 should be used.

Table 7.3.1/1: S6a/S6d, S7a/S7d and S13/S13′ specific DiameterAVPs

				AVP Flag rules
Attribute Name	AVP Code	Clause defined	Value Type	Must	May	Should not	Must not	May Encr.
Subscription-Data	1400	7.3.2	Grouped	M, V				No
Terminal-Information	1401	7.3.3	Grouped	M, V				No
IMEI	1402	7.3.4	UTF8String	M, V				No
Software-Version	1403	7.3.5	UTF8String	M, V				No
QoS-Subscribed	1404	7.3.77	OctetString	M, V				No
ULR-Flags	1405	7.3.7	Unsigned32	M, V				No
ULA-Flags	1406	7.3.8	Unsigned32	M, V				No
Visited-PLMN-Id	1407	7.3.9	OctetString	M, V				No
Requested-EUTRAN-Authentication-Info	1408	7.3.11	Grouped	M, V				No
Requested-UTRAN-GERAN-Authentication-Info	1409	7.3.12	Grouped	M, V				No
Number-Of-Requested-Vectors	1410	7.3.14	Unsigned32	M, V				No
Re-Synchronization-Info	1411	7.3.15	OctetString	M, V				No
Immediate-Response-Preferred	1412	7.3.16	Unsigned32	M, V				No
Authentication-Info	1413	7.3.17	Grouped	M, V				No
E-UTRAN-Vector	1414	7.3.18	Grouped	M, V				No
UTRAN-Vector	1415	7.3.19	Grouped	M, V				No
GERAN-Vector	1416	7.3.20	Grouped	M, V				No
Network-Access-Mode	1417	7.3.21	Enumerated	M, V				No
HPLMN-ODB	1418	7.3.22	Unsigned32	M, V				No
Item-Number	1419	7.3.23	Unsigned32	M, V				No
Cancellation-Type	1420	7.3.24	Enumerated	M, V				No
DSR-Flags	1421	7.3.25	Unsigned32	M, V				No
DSA-Flags	1422	7.3.26	Unsigned32	M, V				No
Context-Identifier	1423	7.3.27	Unsigned32	M, V				No
Subscriber-Status	1424	7.3.29	Enumerated	M, V				No
Operator-Determined-Barring	1425	7.3.30	Unsigned32	M, V				No
Access-Restriction-Data	1426	7.3.31	Unsigned32	M, V				No
APN-OI-Replacement	1427	7.3.32	UTF8String	M, V				No
All-APN-Configurations-Included-Indicator	1428	7.3.33	Enumerated	M, V				No
APN-Configuration-Profile	1429	7.3.34	Grouped	M, V				No
APN-Configuration	1430	7.3.35	Grouped	M, V				No
EPS-Subscribed-QoS-Profile	1431	7.3.37	Grouped	M, V				No
VPLMN-Dynamic-Address-Allowed	1432	7.3.38	Enumerated	M, V				No
STN-SR	1433	7.3.39	OctetString	M, V				No
Alert-Reason	1434	7.3.83	Enumerate	M, V				No
AMBR	1435	7.3.41	Grouped	M, V				No
CSG-Subscription-Data	1436	7.3.78	Grouped	M. V				No
CSG-Id	1437	7.3.79	Unsigned32	M, V				No
PDN-GW-Allocation-Type	1438	7.3.44	Enumerated	M, V				No
Expiration-Date	1439	7.3.80	Time	M, V				No
RAT-Frequency-Selection-Priority-ID	1440	7.3.46	Unsigned32	M, V				No
IDA-Flags	1441	7.3.47	Unsigned32	M, V				No
PUA-Flags	1442	7.3.48	Unsigned32	M, V				No
NOR-Flags	1443	7.3.49	Unsigned32	M, V				No
User-Id	1444	7.3.50	UTF8String	V			M	No
Equipment-Status	1445	7.3.51	Enumerated	M, V				No
Regional-Subscription-Zone-Code	1446	7.3.52	OctetString	M, V				No
RAND	1447	7.3.53	OctetString	M, V				No
XRES	1448	7.3.54	OctetString	M, V				No
AUTN	1449	7.3.55	OctetString	M, V				No
KASME	1450	7.3.56	OctetString	M, V				No
Trace-Collection-Entity	1452	7.3.98	Address	M, V				No
Kc	1453	7.3.59	OctetString	M, V				No
SRES	1454	7.3.60	OctetString	M, V				No
PDN-Type	1456	7.3.62	Enumerated	M, V				No
Roaming-Restricted-Due-To-Unsupported-Feature	1457	7.3.81	Enumerated	M, V				No
Trace-Data	1458	7.3.63	Grouped	M, V				No
Trace-Reference	1459	7.3.64	OctetString	M, V				No
Trace-Depth	1462	7.3.67	Enumerated	M, V				No
Trace-NE-Type-List	1463	7.3.68	OctetString	M, V				No
Trace-Interface-List	1464	7.3.69	OctetString	M, V				No
Trace-Event-List	1465	7.3.70	OctetString	M, V				No
OMC-Id	1466	7.3.71	OctetString	M, V				No
GPRS-Subscription-Data	1467	7.3.72	Grouped	M, V				No
Complete-Data-List-Included-Indicator	1468	7.3.73	Enumerated	M, V				No
PDP-Context	1469	7.3.74	Grouped	M, V				No
PDP-Type	1470	7.3.75	OctetString	M, V				No
3GPP2-MEID	1471	7.3.6	OctetString	M, V				No
Specific-APN-Info	1472	7.3.82	Grouped	M, V				No
LCS-Info	1473	7.3.84	Grouped	M, V				No
GMLC-Number	1474	7.3.85	OctetString	M, V				No
LCS-PrivacyException	1475	7.3.86	Grouped	M, V				No
SS-Code	1476	7.3.87	OctetString	M, V				No
SS-Status	1477	7.3.88	OctetString	M, V				No
Notification-To-UE-User	1478	7.3.89	Enumerated	M, V				No
External-Client	1479	7.3.90	Grouped	M, V				No
Client-Identity	1480	7.3.91	OctetString	M, V				No
GMLC-Restriction	1481	7.3.92	Enumerated	M, V				No
PLMN-Client	1482	7.3.93	Enumerated	M, V				No
Service-Type	1483	7.3.94	Grouped	M, V				No
ServiceTypeIdentity	1484	7.3.95	Unsigned32	M, V				No
MO-LR	1485	7.3.96	Grouped	M, V				No
Teleservice-List	1486	7.3.99	Grouped	M, V				No
TS-Code	1487	7.3.100	OctetString	M, V				No
Call-Barring-Info	1488	7.3.101	Grouped	M, V				No
SGSN-Number	1489	7.3.102	OctetString	M, V				No
IDR-Flags	1490	7.3.103	Unsigned32	M, V				No
ICS-Indicator	1491	7.3.104	Enumerated	V			M	No
IMS-Voice-Over-PS-Sessions-Supported	1492	7.3.106	Enumerated	V			M	No
Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions	1493	7.3.107	Enumerated	V			M	No
Last-UE-Activity-Time	1494	7.3.108	Time	V			M	No
EPS-User-State	1495	7.3.110	Grouped	V			M	No
EPS-Location-Information	1496	7.3.111	Grouped	V			M	No
MME-User-State	1497	7.3.112	Grouped	V			M	No
SGSN-User-State	1498	7.3.113	Grouped	V			M	No
User-State	1499	7.3.114	Enumerated	V			M	No
MME-Location Information	1600	7.3.115	Grouped	V			M	No
SGSN-Location-Information	1601	7.3.116	Grouped	V			M	No
E-UTRAN-Cell-Global-Identity	1602	7.3.117	OctetString	V			M	No
Tracking-Area-Identity	1603	7.3.118	OctetString	V			M	No
Cell-Global-Identity	1604	7.3.119	OctetString	V			M	No
Routing-Area-Identity	1605	7.3.120	OctetString	V			M	No
Location-Area-Identity	1606	7.3.121	OctetString	V			M	No
Service-Area-Identity	1607	7.3.122	OctetString	V			M	No
Geographical-Information	1608	7.3.123	OctetString	V			M	No
Geodetic-Information	1609	7.3.124	OctetString	V			M	No
Current-Location-Retrieved	1610	7.3.125	Enumerated	V			M	No
Age-Of-Location-Information	1611	7.3.126	Unsigned32	V			M	No
Active-APN	1612	7.3.127	Grouped	V			M	No
Error-Diagnostic	1614	7.3.128	Enumerated	V			M	No
Ext-PDP-Address	1621	7.3.129	Address	V			M	No
UE-SRVCC-Capability	1615	7.3.130	Enumerated	V			M	No
MPS-Priority	1616	7.3.131	Unsigned32	V			M	No
VPLMN-LIPA-Allowed	1617	7.3.132	Enumerated	V			M	No
LIPA-Permission	1618	7.3.133	Enumerated	V			M	No
Subscribed-Periodic-RAU-TAU-Timer	1619	7.3.134	Unsigned32	V			M	No
Ext-PDP-Type	1620	7.3.75A	OctetString	V			M	No
SIPTO-Permission	1613	7.3.135	Enumerated	V			M	No
MDT-Configuration	1622	7.3.136	Grouped	V			M	No
Job-Type	1623	7.3.137	Enumerated	V			M	No
Area-Scope	1624	7.3.138	Grouped	V			M	No
List-Of-Measurements	1625	7.3.139	Unsigned32	V			M	No
Reporting-Trigger	1626	7.3.140	Unsigned32	V			M	No
Report-Interval	1627	7.3.141	Enumerated	V			M	No
Report-Amount	1628	7.3.142	Enumerated	V			M	No
Event-Threshold-RSRP	1629	7.3.143	Unsigned32	V			M	No
Event-Threshold-RSRQ	1630	7.3.144	Unsigned32	v			M	No
Logging-Interval	1631	7.3.145	Enumerated	V			M	No
Logging-Duration	1632	7.3.146	Enumerated	V			M	No
Relay-Node-Indicator	1633	7.3.147	Enumerated	V			M	No
MDT-User-Consent	1634	7.3.148	Enumerated	V			M	No
PUR-Flags	1635	7.3.149	Unsigned32	V			M	No
Subscribed-VSRVCC	1636	7.3.150	Enumerated	V			M	No
Equivalent-PLMN-List	1637	7.3.151	Grouped	V			M	No
CLR-Flags	1638	7.3.152	Unsigned32	V			M	No
UVR-Flags	1639	7.3.153	Unsigned32	M, V				No
UVA-Flags	1640	7.3.154	Unsigned32	M, V				No
VPLMN-CSG-Subscription-Data	1641	7.3.155	Grouped	M, V				No
Time-Zone	1642	7.3.163	UTF8String	V			M	No
A-MSISDN	1643	7.3.157	OctetString	V			M	No
MME-Number-for-MT-SMS	1645	7.3.159	OctetString	V			M	No
SMS-Register-Request	1648	7.3.162	Enumerated	V			M	No
Local-Time-Zone	1649	7.3.156	Grouped	V			M	No
Daylight-Saving-Time	1650	7.3.164	Enumerated	V			M	No
Subscription-Data-Flags	1654	7.3.165	Unsigned32	V			M	No
Measurement-Period-LTE	1655	7.3.166	Enumerated	V			M	No
Measurement-Period-UMTS	1656	7.3.167	Enumerated	V			M	No
Collection-Period-RRM-LTE	1657	7.3.168	Enumerated	V			M	No
Collection-Period-RRM-UMTS	1658	7.3.169	Enumerated	V			M	No
Positioning-Method	1659	7.3.170	OctetString	V			M	No
Measurement-Quantity	1660	7.3.171	OctetString	V			M	No
Event-Threshold-Event-1F	1661	7.3.172	Integer32	V			M	No
Event-Threshold-Event-1I	1662	7.3.173	Integer32	V			M	No
Restoration-Priority	1663	7.3.174	Unsigned32	V			M	No
SGs-MME-Identity	1664	7.3.175	UTF8String	V			M	No
SIPTO-Local-Network-Permission	1665	7.3.176	Unsigned32	V			M	No
Coupled-Node-Diameter-ID	1666	7.3.177	DiameterIdentity	V			M	No
WLAN-offloadability	1667	7.3.181	Grouped	V			M	No
WLAN-offloadability-EUTRAN	1668	7.3.182	Unsigned32	V			M	No
WLAN-offloadability-UTRAN	1669	7.3.183	Unsigned32	V			M	No
Reset-ID	1670	7.3.184	OctetString	V			M	No
MDT-Allowed-PLMN-Id	1671	7.3.185	OctetString	V			M	No
Adjacent-PLMNs	1672	7.3.186	Grouped	V			M	No
Adjacent-Access-Restriction-Data	1673	7.3.187	Grouped	V			M	No
DL-Buffering-Suggested-Packet-Count	1674	7.3.188	Integer32	V			M	No
IMSI-Group-Id	1675	7.3.189	Grouped	V			M	No
Group-Service-Id	1676	7.3.190	Unsigned32	V			M	No
Group-PLMN-Id	1677	7.3.191	OctetString	V			M	No
Local-Group-Id	1678	7.3.192	OctetString	V			M	No
AIR-Flags	1679	7.3.201	Unsigned32	V			M	No
UE-Usage-Type	1680	7.3.202	Unsigned32	V			M	No
Non-IP-PDN-Type-Indicator	1681	7.3.204	Enumerated	V			M	No
Non-IP-Data-Delivery-Mechanism	1682	7.3.205	Unsigned32	V			M	No
Additional-Context-ID	1683	7.3.206	Unsigned32	V			M	No
SCEF-Realm	1684	7.3.207	DiameterIdentity	V			M	No
Subscription-Data-Deletion	1685	7.3.208	Grouped	V			M	No
Preferred-Data-Mode	1686	7.3.209	Unsigned32	V			M	No
Emergency-Info	1687	7.3.210	Grouped	V			M	No
V2X-Subscription-Data	1688	7.3.212	Grouped	V			M	No
V2X-Permission	1689	7.3.213	Unsigned32	V			M	No
PDN-Connection-Continuity	1690	7.3.214	Unsigned32	V			M	No
eDRX-Cycle-Length	1691	7.3.215	Grouped	V			M	No
eDRX-Cycle-Length-Value	1692	7.3.216	OctetString	V			M	No
UE-PC5-AMBR	1693	7.3.217	Unsigned32	V			M	No
MBSFN-Area	1694	7.3.219	Grouped	V			M	No
MBSFN-Area-ID	1695	7.3.220	Unsigned32	V			M	No
Carrier-Frequency	1696	7.3.221	Unsigned32	V			M	No
RDS-Indicator	1697	7.3.222	Enumerated	V			M	No
Service-Gap-Time	1698	7.3.223	Unsigned32	V			M	No
Aerial-UE-Subscription-Information	1699	7.3.224	Unsigned32	V			M	No
Broadcast-Location-Assistance-Data-Types	1700	7.3.225	Unsigned64	V			M	No
Paging-Time-Window	1701	7.3.226	Grouped	V			M	No
Operation-Mode	1702	7.3.227	Unsigned32	V			M	No
Paging-Time-Window-Length	1703	7.3.228	OctetString	V			M	No
Core-Network-Restrictions	1704	7.3.230	Unsigned32	V			M	No
eDRX-Related-RAT	1705	7.3.229	Grouped	V			M	No
Interworking-5GS-Indicator	1706	7.3.231	Enumerated	V			M	No
Ethernet-PDN-Type-Indicator	1707	7.3.232	Enumerated	V			M	No
Subscribed-ARPI	1708	7.3.233	Unsigned32	V			M	No
IAB-Operation-Permission	1709	7.3.234	Enumerated	V			M	No
V2X-Subscription-Data-Nr	1710	7.3.235	Grouped	V			M	No
UE-PC5-QoS	1711	7.3.236	Grouped	V			M	No
PC5-QoS-Flow	1712	7.3.237	Grouped	V			M	No
5QI	1713	7.3.238	Integer32	V			M	No
PC5-Flow-Bitrates	1714	7.3.239	Grouped	V			M	No
Guaranteed-Flow-Bitrates	1715	7.3.240	Integer32	V			M	No
Maximum-Flow-Bitrates	1716	7.3.241	Integer32	V			M	No
PC5-Range	1717	7.3.242	Integer32	V			M	No
PC5-Link-AMBR	1718	7.3.243	Integer32	V			M	No
Third-Context-Identifier	1719	7.3.244	Unsigned32	V			M	No
NOTE 1: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. For further details, see IETF RFC 6733 [61]. NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.

The following table specifies the Diameter AVPs re-used by the S6a/S6d interface protocol from existing Diameter Applications, including a reference to their respective specifications and when needed, a short description of their use within S6a and S6d.

Any other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol specified in IETF RFC 6733 [61], do not need to be supported. The AVPs from the Diameter base protocol specified in IETF RFC 6733 [61] are not included in table 7.3.1/2, but they may be re-used for the S6a/S6d protocol, the S7a/S7protocol and the S13/S13′ protocol.

Table 7.3.1/2: S6a/S6d, S7a/S7d and S13/S13′ re-used Diameter AVPs

Attribute Name	Reference	Comments	M-bit
Service-Selection	IETF RFC 5778 [20]	See clause 7.3.36
3GPP-Charging-Characteristics	3GPP TS 29.061 [21]	See 3GPP TS 32.251 [33] Annex A and 3GPP TS 32.298 [22] clause 5.1.2.2.7 This attribute holds the EPS PDN Connection Charging Characteristics data for an EPS APN Configuration, or the PDP context Charging Characteristics for GPRS PDP context, or the Subscribed Charging Characteristics data for the subscriber level 3GPP Charging Characteristics; refer to 3GPP TS 23.008 [30].
Supported-Features	3GPP TS 29.229 [9]
Feature-List-ID	3GPP TS 29.229 [9]
Feature-List	3GPP TS 29.229 [9]	See clause 7.3.10
Served-Party-IP-Address	3GPP TS 32.299 [8]	holds the PDN IP Address of the user
QoS-Class-Identifier	3GPP TS 29.212 [10]
Allocation-Retention-Priority	3GPP TS 29.212 [10]	See clause 7.3.40
Priority-Level	3GPP TS 29.212 [10]
Pre-emption-Capability	3GPP TS 29.212 [10]
Pre-emption-Vulnerability	3GPP TS 29.212 [10]
Max-Requested-Bandwidth-DL	3GPP TS 29.214 [11]
Max-Requested-Bandwidth-UL	3GPP TS 29.214 [11]
Extended-Max-Requested-BW-DL	3GPP TS 29.214 [11]
Extended-Max-Requested-BW-UL	3GPP TS 29.214 [11]
RAT-Type	3GPP TS 29.212 [10]	See clause 7.3.13	Must set
MSISDN	3GPP TS 29.329 [25]
MIP6-Agent-Info	IETF RFC 5447 [26]
MIP-Home-Agent-Address	IETF RFC 4004 [27]
MIP-Home-Agent-Host	IETF RFC 4004 [27]
PDP-Address	3GPP TS 32.299 [8]
Confidentiality-Key	3GPP TS 29.229 [9]	See clause 7.3.57
Integrity-Key	3GPP TS 29.229 [9]	See clause 7.3.58
Visited-Network-Identifier	3GPP TS 29.229 [9]	See clause 7.3.105	Must not set
GMLC-Address	3GPP TS 29.173 [37]	See clause 7.3.109	Must not set
User-CSG-Information	3GPP TS 32.299 [8]		Must not set
ProSe-Subscription-Data	3GPP TS 29.344 [49]	See clause 7.3.180	Must not set
OC-Supported-Features	IETF RFC 7683 [50]	See clause 7.3.178	Must not set
OC-OLR	IETF RFC 7683 [50]	See clause 7.3.179	Must not set
SCEF-Reference-ID	3GPP TS 29.336 [54]		Must not set
SCEF-ID	3GPP TS 29.336 [54]		Must not set
AESE-Communication-Pattern	3GPP TS 29.336 [54]	see clause 7.3.193	Must not set
Communication-Pattern-set	3GPP TS 29.336 [54]	see clause 7.3.194	Must not set
Monitoring-Event-Configuration	3GPP TS 29.336 [54]	See clause 7.3.195	Must not set
Monitoring-Event-Report	3GPP TS 29.336 [54]	See clause 7.3.196	Must not set
UE-Reachability-Configuration	3GPP TS 29.336 [54]	See clause 7.3.197	Must not set
eNodeB-ID	3GPP TS 29.217 [56]	See clause 7.3.198	Must not set
SCEF-Reference-ID-for-Deletion	3GPP TS 29.336 [54]		Must not set
Monitoring-Type	3GPP TS 29.336 [54]		Must not set
Maximum-Number-of-Reports	3GPP TS 29.336 [54]		Must not set
Monitoring-Duration	3GPP TS 29.336 [54]		Must not set
Charged-Party	3GPP TS 29.336 [54]		Must not set
Location-Information-Configuration	3GPP TS 29.336 [54]		Must not set
Reachability-Type	3GPP TS 29.336 [54]		Must not set
Maximum-Response-Time	3GPP TS 29.336 [54]		Must not set
Reachability-Information	3GPP TS 29.336 [54]		Must not set
Monitoring-Event-Config-Status	3GPP TS 29.336 [54]		Must not set
Supported-Services	3GPP TS 29.336 [54]	See clause 7.3.199	Must not set
Supported-Monitoring-Events	3GPP TS 29.336 [54]	See clause 7.3.200	Must not set
DRMP	IETF RFC 7944 [57]	See clause 7.3.203	Must not set
Reference-ID-Validity-Time	3GPP TS 29.336 [54]		Must not set
Maximum-UE-Availability-Time	3GPP TS 29.338 [48]	See clause 5.3.3.22	Must not set
Emergency-Services	3GPP TS 29.273 [59]
Load	IETF RFC 8583 [60]	See clause 7.3.211	Must not set
Extended-eNodeB-ID	3GPP TS 29.217 [56]	See clause 7.3.218	Must not set
External-Identifier	3GPP TS 29.336 [54]		Must not set
Loss-Of-Connectivity-Reason	3GPP TS 29.336 [54]		Must not set
Active-Time	3GPP TS 29.128 [63]		Must not set
Idle-Status-Indication	3GPP TS 29.128 [63]		Must not set
MTC-Provider-Info	3GPP TS 29.336 [54]		Must not set
Traffic-Profile	3GPP TS 29.336 [54]		Must not set
PDN-Connectivity-Status-Configuration	3GPP TS 29.336 [54]	See clause 7.3.195	Must not set
PDN-Connectivity-Status-Report	3GPP TS 29.336 [54]	See clause 7.3.196	Must not set
Battery-Indicator	3GPP TS 29.336 [54]		Battery-Indicator
SCEF-Reference-ID-Ext	3GPP TS 29.336 [54]		Must not set
SCEF-Reference-ID-for-Deletion-Ext	3GPP TS 29.336 [54]		Must not set
NOTE 1: The M-bit settings for re-used AVPs override those of the defining specifications that are referenced. Values include: "Must set", "Must not set". If the M-bit setting is blank, then the defining specification applies. NOTE 2: If the M-bit is set for an AVP and the receiver does not understand the AVP, it shall return a rejection. If the M-bit is not set for an AVP, the receiver shall not return a rejection, whether or not it understands the AVP. If the receiver understands the AVP but the M-bit value does not match with the definition in this table, the receiver shall ignore the M-bit.

7.3.2 Subscription-Data

The Subscription-Data AVP is of type Grouped. It shall contain the information related to the user profile relevant for EPS and GERAN/UTRAN.

AVP format:

Subscription-Data ::= <AVP header: 1400 10415>

[ Subscriber-Status ]

[ MSISDN ]

[ A-MSISDN ]

[ STN-SR ]

[ ICS-Indicator ]

[ Network-Access-Mode ]

[ Operator-Determined-Barring ]

[ HPLMN-ODB ]

*10[ Regional-Subscription-Zone-Code ]

[ Access-Restriction-Data ]

[ APN-OI-Replacement ]

[ LCS-Info ]

[ Teleservice-List ]

*[ Call-Barring-Info ]

[ 3GPP-Charging-Characteristics ]

[ AMBR ]

[ APN-Configuration-Profile ]

[ RAT-Frequency-Selection-Priority-ID ]

[ Trace-Data]

[ GPRS-Subscription-Data ]

*[ CSG-Subscription-Data ]

[ Roaming-Restricted-Due-To-Unsupported-Feature ]

[ Subscribed-Periodic-RAU-TAU-Timer ]

[ MPS-Priority ]

[ VPLMN-LIPA-Allowed ]

[ Relay-Node-Indicator ]

[ MDT-User-Consent ]

[ Subscribed-VSRVCC ]

[ ProSe-Subscription-Data ]

[ Subscription-Data-Flags ]

*[ Adjacent-Access-Restriction-Data ]

[ DL-Buffering-Suggested-Packet-Count ]

*[ IMSI-Group-Id ]

[ UE-Usage-Type ]

*[ AESE-Communication-Pattern ]

*[ Monitoring-Event-Configuration ]

[ Emergency-Info ]

[ V2X-Subscription-Data ]

[ V2X-Subscription-Data-Nr ]

*[ eDRX-Cycle-Length ]

[ External-Identifier ]

[ Active-Time ]

[ Service-Gap-Time ]

[ Broadcast-Location-Assistance-Data-Types ]

[ Aerial-UE-Subscription-Information ]

[ Core-Network-Restrictions ]

*[ Paging-Time-Window ]

[ Subscribed-ARPI ]

[ IAB-Operation-Permission ]

*[ AVP ]

The AMBR included in this grouped AVP shall include the AMBR associated to the user’s subscription (UE-AMBR); Max-Requested-Bandwidth-UL and Max-Requested-Bandwidth-DL within this AVP shall not both be set to "0".

The APN-OI-Replacement included in this grouped AVP shall include the UE level APN-OI-Replacement associated to the user’s subscription.

When multiple External Identifiers are defined for the same subscription, the External-Identifier in this grouped AVP shall contain a default External Identifier determined by the HSS.

7.3.3 Terminal-Information

The Terminal-Information AVP is of type Grouped. This AVP shall contain the information about the user’s terminal.

AVP format

Terminal-Information ::= <AVP header: 1401 10415>

[ IMEI ]

[ 3GPP2-MEID ]

[ Software-Version ]

*[ AVP ]

7.3.4 IMEI

The IMEI AVP is of type UTF8String. This AVP shall contain the International Mobile Equipment Identity, as specified in 3GPP TS 23.003 [3]. It should consist of 14 digits, including the 8-digit Type Allocation Code (TAC) and the 6-digit Serial Number (SNR). It may also include a 15^th digit.

7.3.5 Software-Version

The Software-Version AVP is of type UTF8String. This AVP shall contain the 2-digit Software Version Number (SVN) of the International Mobile Equipment Identity, as specified in 3GPP TS 23.003 [3].

7.3.6 3GPP2-MEID

This AVP is of type OctetString. This AVP contains the Mobile Equipment Identifier of the user’s terminal. For further details on the encoding of the AVP data, refer to the encoding of the Mobile Identity (MEID) octets 3 to 10 in 3GPP2 A.S0022 [28] Annex A.

7.3.7 ULR-Flags

The ULR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.7/1:

Table 7.3.7/1: ULR-Flags

Bit	Name	Description
0	Single-Registration-Indication	This bit, when set, indicates that the HSS shall send Cancel Location to the SGSN. An SGSN shall not set this bit when sending ULR.
1	S6a/S6d-Indicator	This bit, when set, indicates that the ULR message is sent on the S6a interface, i.e. the source node is an MME (or a combined MME/SGSN to which the UE is attached via E-UTRAN). This bit, when cleared, indicates that the ULR message is sent on the S6d interface, i.e. the source node is an SGSN (or a combined MME/SGSN to which the UE is attached via UTRAN or GERAN).
2	Skip Subscriber Data	This bit, when set, indicates that the HSS may skip subscription data in ULA. If the subscription data has changed in the HSS after the last successful update of the MME/SGSN, the HSS shall ignore this bit and send the updated subscription data. If the HSS effectively skips the sending of subscription data, the GPRS-Subscription-Data-Indicator flag can be ignored.
3	GPRS-Subscription-Data-Indicator	This bit, when set, indicates that the HSS shall include in the ULA command the GPRS subscription data, if available in the HSS; it shall be included in the GPRS-Subscription-Data AVP inside the Subscription-Data AVP (see 7.3.2). Otherwise, the HSS shall not include the GPRS-Subscription-Data AVP in the response, unless the Update Location Request is received over the S6d interface and there is no APN configuration profile stored for the subscriber, or when the subscription data is returned by a Pre-Rel-8 HSS (via an IWF). A standalone MME shall not set this bit when sending a ULR.
4	Node-Type-Indicator	This bit, when set, indicates that the requesting node is a combined MME/SGSN. This bit, when cleared, indicates that the requesting node is a single MME or SGSN; in this case, if the S6a/S6d-Indicator is set, the HSS may skip the check of those supported features only applicable to the SGSN, and if, in addition the MME does not request to be registered for SMS, the HSS may consequently skip the download of the SMS related subscription data to a standalone MME. NOTE2
5	Initial-Attach-Indicator	This bit, when set, indicates that the HSS shall send Cancel Location to the MME or SGSN if there is the MME or SGSN registration.
6	PS-LCS-Not-Supported-By-UE	This bit, when set, indicates to the HSS that the UE does not support neither UE Based nor UE Assisted positioning methods for Packet Switched Location Services. The MME shall set this bit on the basis of the UE capability information. The SGSN shall set this bit on the basis of the UE capability information and the access technology supported by the SGSN.
7	SMS-Only-Indication	This bit, when set, indicates that the UE indicated "SMS only" when requesting a combined IMSI attach or combined RA/LU.
8	Dual-Registration-5G-Indicator	This bit, when set by an MME over S6a interface, indicates that the HSS+UDM shall not send Nudm_UECM_DeregistrationNotification to the registered AMF (if any); when not set by an MME over S6a interface, it indicates that the HSS+UDM shall send Nudm_UECM_DeregistrationNotification to the registered AMF (if any). See 3GPP TS 29.503 [66]. An SGSN shall not set this bit when sending ULR over S6d interface.
9	Inter-PLMN-inter-MME handover	This bit, when set by an MME over S6a interface, indicates that an inter PLMN inter MME (or AMF to MME) handover is ongoing.
10	Intra-PLMN-inter-MME handover	This bit, when set by an MME over S6a interface, indicates that an intra PLMN inter MME (or AMF to MME) handover is ongoing.
NOTE1: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS. NOTE2: If the MME is registered for SMS then the HSS will download the SMS related data also for the standalone MME.

7.3.8 ULA-Flags

The ULA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.8/1:

Table 7.3.8/1: ULA-Flags

Bit	Name	Description
0	Separation Indication	This bit, when set, indicates that the HSS stores SGSN number and MME number in separate memory. A Rel-8 HSS shall set the bit. An IWF interworking with a pre Rel-8 HSS/HLR shall clear the bit.
1	MME Registered for SMS	This bit, when set, indicates that the HSS has registered the MME for SMS.
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

7.3.9 Visited-PLMN-Id

The Visited-PLMN-Id AVP is of type OctetString. This AVP shall contain the concatenation of MCC and MNC. See 3GPP TS 23.003 [3]. The content of this AVP shall be encoded as an octet string according to table 7.3.9-1.

See 3GPP TS 24.008 [31], clause 10.5.1.13, PLMN list, for the coding of MCC and MNC. If MNC is 2 digits long, bits 5 to 8 of octet 2 are coded as "1111".

Table 7.3.9/1: Encoding format for Visited-PLMN-Id AVP

8	7	6	5	4	3	2	1
MCC digit 2				MCC digit 1				octet 1
MNC digit 3				MCC digit 3				octet 2
MNC digit 2				MNC digit 1				octet 3

7.3.10 Feature-List AVP

7.3.10.1 Feature-List AVP for the S6a/S6d application

The syntax of this AVP is defined in 3GPP TS 29.229 [9].

For the S6a/S6d application, the meaning of the bits shall be as defined in table 7.3.10/1 for the Feature-List-ID 1 and in table 7.3.10/2 for the Feature-List-ID 2.

Table 7.3.10/1: Features of Feature-List-ID 1 used in S6a/S6d

Feature bit	Feature	M/O	Description
0	ODB-all-APN	O	Operator Determined Barring of all Packet Oriented Services This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update by sending DIAMETER_ERROR_ROAMING_NOT_ALLOWED and, optionally, including the type of ODB in the Error-Diagnostic AVP. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
1	ODB-HPLMN-APN	O	Operator Determined Barring of Packet Oriented Services from access points that are within the HPLMN whilst the subscriber is roaming in a VPLMN This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update by sending DIAMETER_ERROR_ROAMING_NOT_ALLOWED and, optionally, including the type of ODB in the Error-Diagnostic AVP. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
2	ODB-VPLMN-APN	O	Operator Determined Barring of Packet Oriented Services from access points that are within the roamed to VPLMN This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update by sending DIAMETER_ERROR_ROAMING_NOT_ALLOWED and, optionally, including the type of ODB in the Error-Diagnostic AVP. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
3	ODB-all-OG	O	Operator Determined Barring of all outgoing calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
4	ODB-all- InternationalOG	O	Operator Determined Barring of all outgoing international calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs.If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
5	ODB-all-InternationalOGNotToHPLMN-Country	O	Operator Determined Barring of all outgoing international calls except those directed to the home PLMN country This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
6	ODB-all-InterzonalOG	O	Operator Determined Barring of all outgoing inter-zonal calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
7	ODB-all-InterzonalOGNotToHPLMN-Country	O	Operator Determined Barring of all outgoing inter-zonal calls except those directed to the home PLMN country This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
8	ODB-all-InterzonalOGAndInternationalOGNotToHPLMN-Country	O	Operator Determined Barring of all outgoing international calls except those directed to the home PLMN country and Barring of all outgoing inter-zonal calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send this ODB barring category to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent this ODB category within IDR, the HSS may apply barring of roaming and send CLR.
9	RegSub	O	Regional Subscription This feature is applicable for the ULR/ULA, IDR/IDA and DSR/DSA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send Regional Subscription Zone Codes to the MME or SGSN within ULA. Instead the HSS may reject location update. If the MME or SGSN does not indicate support of this feature in IDA and the HSS has sent Regional Subscription Zone Codes within IDR, the HSS may apply barring of roaming and send CLR.
10	Trace	O	Trace Function This feature is applicable for the ULR/ULA, IDR/IDA and DSR/DSA command pairs. If the MME or SGSN does not indicate support of this feature in ULR, the HSS shall not send Trace Data to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent Trace Data within IDR, the HSS may store this indication, and not send any further Trace Data to that MME or SGSN. If the MME or SGSN does not indicate support of this feature in DSA, and the HSS has sent Trace Data within DSR, the HSS may store this indication, and not send any further Trace Data to that MME or SGSN
11	LCS-all-PrivExcep (NOTE 1)	O	All LCS Privacy Exception Classes This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
12	LCS-Universal (NOTE 1)	O	Allow location by any LCS client This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
13	LCS-CallSessionRelated (NOTE 1)	O	Allow location by any value added LCS client to which a call/session is established from the target UE This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
14	LCS-CallSessionUnrelated (NOTE 1)	O	Allow location by designated external value added LCS clients This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
15	LCS-PLMNOperator (NOTE 1)	O	Allow location by designated PLMN operator LCS clients This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
16	LCS-ServiceType (NOTE 1)	O	Allow location by LCS clients of a designated LCS service type This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports MAP based Lg interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
17	LCS-all-MOLR-SS (NOTE 1)	O	All Mobile Originating Location Request Classes This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
18	LCS- BasicSelfLocation (NOTE 1)	O	Allow an MS to request its own location This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
19	LCS- AutonomousSelfLocation (NOTE 1)	O	Allow an MS to perform self location without interaction with the PLMN This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
20	LCS- TransferToThirdParty	O	Allow an MS to request transfer of its location to another LCS client This feature is applicable for the ULR/ULA and IDR/IDA command pairs. Over S6d interface, this feature is applicable when the SGSN supports MAP based Lg interface. If the MME or SGSN does not support this feature, the HSS shall not send the related LCS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that MME or SGSN.
21	SM-MO-PP (NOTE 1)	O	Short Message MO-PP This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
22	Barring-OutgoingCalls	O	Barring of Outgoing Calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
23	BAOC	O	Barring of all outgoing calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
24	BOIC	O	Barring of outgoing international calls This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
25	BOICExHC	O	Barring of outgoing international calls except those directed to the home PLMN Country This feature is applicable for the ULR/ULA and IDR/IDA command pairs. If the MME or SGSN does not support this feature, the HSS shall not send the related SMS information to the MME or SGSN within ULA. If the MME or SGSN does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME or SGSN.
26	UE-Reachability-Notification	O	UE Reachability Notifcation This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d. If the MME or SGSN indicates in the ULR command that it does not support the UE-Reachability-Notifications, the HSS shall not set the "UE-Reachability-Request" bit in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
27	T-ADS Data Retrieval	O	Terminating Access Domain Selection Data Retrieval This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d. If the MME or SGSN indicates in the ULR command that it does not support the retrieval of T-ADS data via IDR/IDA commands, the HSS shall not set the "T-ADS Data Request" bit in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
28	State/Location-Information-Retrieval	O	State/Location Information Retrieval This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d. If the MME or SGSN indicates in the ULR command that it does not support State/Location Information Retrieval, the HSS shall not set the "EPS User State Request", "EPS Location Information Request" or "Current Location Request" bits in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
29	Partial Purge	O	Partial Purge from a Combined MME/SGSN This feature is applicable for the ULR/ULA and PUR/PUA command pairs, over S6a and S6d. If the HSS indicates in the ULA command that it does not support Partial Purge, the combined MME/SGSN shall not include in the PUR command the indication of the specific serving node where the Purge has been done.
30	Local Time Zone Retrieval	O	UE Time Zone Retrieval This feature is applicable for the ULR/ULA and IDR/IDA command pairs, over S6a and S6d. If the MME or SGSN indicates in the ULR command that it does not support the retrieval of Local Time Zone via IDR/IDA commands, the HSS shall not set the "Local Time Zone Request" bit in IDR-Flags in subsequent IDR commands towards that MME or SGSN.
31	Additional MSISDN	O	Additional MSISDN This feature is applicable for the ULR/ULA, IDR/IDA and DSR/DSA command pairs, over S6a and S6d. If the MME or SGSN indicates in the ULR command that it does not support A-MSISDN, the HSS shall populate the MSISDN AVP either with the subscribed MSISDN or the subscribed additional MSISDN based on operator policy and availability and the HSS shall not send IDR with the A-MSISDN AVP or DSR with the "A-MSISDN Withdrawal" bit to the serving nodes when the subscription data is changed. If the MME or SGSN indicates in the IDA command that it does not support this feature and the HSS has already sent an A-MSISDN value within IDR, the HSS may store this indication and not send any further A-MSISDN updates to that MME or SGSN.
Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1". Feature: A short name that can be used to refer to the bit and to the feature, e.g. "ODB-HPLMN-APN". M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O"). Description: A clear textual description of the feature. NOTE 1: If both bits, corresponding to the feature defined for Lg interface and Lgd interface respectively, are not set, and the HSS supports the feature, the HSS shall not send the related LCS information to the SGSN within ULA and IDR.

Table 7.3.10/2: Features of Feature-List-ID 2 used in S6a/S6d

Feature bit	Feature	M/O	Description
0	SMS in MME	O	SMS in MME This feature is applicable for the ULR/ULA, IDR/IDA, DSR/DSA, NOR/NOA command pairs, over S6a. It is used by the MME to notify the HSS it is capable of SMS transfer without the need of establishing an SGs association with an MSC. If the MME does not support this feature, the HSS shall not send the related SMS information to the MME within ULA. If the MME does not indicate support of this feature in IDA, and the HSS has sent the related SMS information within IDR, the HSS may store this indication, and not send any further SMS information to that MME. If the HSS does not support this feature, the HSS shall ignore any request for a registration for SMS; the MME may store this feature indication, and not send any further request for a registration for SMS to the HSS.
1	SMS in SGSN	O	SMS in SGSN This feature is applicable for the ULR/ULA command pair, over S6d. If the SGSN indicates in the ULR command that it does not support this feature, the HSS shall not indicate "SMS in SGSN Allowed" to the SGSN.
2	Dia-LCS-all-PrivExcep (NOTE 1)	O	All LCS Privacy Exception Classes This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
3	Dia-LCS-Universal (NOTE 1)	O	Allow location by any LCS client This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
4	Dia-LCS-CallSessionRelated (NOTE 1)	O	Allow location by any value added LCS client to which a call/session is established from the target UE This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
5	Dia-LCS-CallSessionUnrelated (NOTE 1)	O	Allow location by designated external value added LCS clients This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
6	Dia-LCS-PLMNOperator (NOTE 1)	O	Allow location by designated PLMN operator LCS clients This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
7	Dia-LCS-ServiceType (NOTE 1)	O	Allow location by LCS clients of a designated LCS service type This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
8	Dia-LCS-all-MOLR-SS (NOTE 1)	O	All Mobile Originating Location Request Classes This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
9	Dia-LCS- BasicSelfLocation (NOTE 1)	O	Allow an MS to request its own location This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
10	Dia-LCS- AutonomousSelfLocation (NOTE 1)	O	Allow an MS to perform self location without interaction with the PLMN This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
11	Dia-LCS- TransferToThirdParty (NOTE 1)	O	Allow an MS to request transfer of its location to another LCS client This feature is applicable for the ULR/ULA and IDR/IDA command pairs over the S6d interface, when the SGSN supports Diameter based Lgd interface. If the SGSN does not support this feature, the HSS shall not send the related LCS information to the SGSN within ULA. If the SGSN does not indicate support of this feature in IDA, and the HSS has sent the related LCS information within IDR, the HSS may store this indication, and not send any further LCS information to that SGSN.
12	Gdd-in-SGSN	O	Support of Diameter based Gdd interface for SMS in SGSN This feature is applicable for the ULR/ULA command pair over S6d, when the SGSN supports the Diameter based Gdd interface for SMS in SGSN.
13	Optimized-LCS-Proc-Support	O	Support for the optimized LCS procedure This feature is applicable for the ULR/ULA command pair over S6a/S6d, when the network supports ISR and when the node is combined MME/SGSN and supports optimized LCS procedure as described in 3GPP TS 29.172 [47] clause 6.2.2.
14	SGSN CAMEL Capability	O	Support of SGSN CAMEL Capability This feature is applicable for the ULR/ULA command pair over S6d, when the SGSN supports the CAMEL capability.
15	ProSe Capability	O	Support of ProSe Capability This feature is applicable for the ULR/ULA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the ProSe capability. If the MME or combined MME/SGSN does not support this feature, the HSS shall not send the related ProSe subscription data to the MME or combined MME/SGSN within ULA. If the MME or combined MME/SGSN does not indicate support of this feature in IDA, and the HSS has sent the related ProSe subscription data within IDR, the HSS may store this indication, and not send any further ProSe subscription data to that MME.
16	P-CSCF Restoration	O	Support of P-CSCF Restoration This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a or S6d interfaces, when the MME or SGSN supports the execution of the P-CSCF restoration procedures. If the MME or the SGSN does not indicate support of this feature in ULR, the HSS shall not send subsequent IDR commands requesting the execution of HSS-based P-CSCF restoration procedures, as described in 3GPP TS 23.380 [51] clause 5.4.
17	Reset-IDs	O	Support of Reset-IDs This feature is applicable to the ULR/ULA and IDR/IDA and DSR/DSA and RSR/RSA command pairs over the S6a and S6d interfaces. If the MME or SGSN indicates in the ULR command that it does not support Reset-IDs, the HSS shall not include Reset-ID AVPs in RSR commands sent to that MME or SGSN. If the MME or SGSN indicates that it does not support this feature in IDA, and the HSS has already sent a Reset-ID value within IDR, the HSS may store this indication and not send any further Reset-ID updates to that MME or SGSN.
18	Communication-Pattern	O	Support of AESE communication patterns This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the AESE communication patterns. If the MME or combined MME/SGSN does not indicate the support for this feature, the HSS shall not send CP parameter sets to the MME or combined MME/SGSN within IDR/ULA command. If the MME or combined MME/SGSN indicates that it does not support this feature in IDA, and the HSS has already sent CP parameter sets within IDR, the HSS may store this indication and not send any further updates related to CP parameter sets to that MME or combined MME/SGSN.
19	Monitoring-Event	O	Support of Monitoring Event This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a or S6d interfaces, when the MME or SGSN supports the Monitoring event feature. If the MME or SGSN does not indicate support of this feature in ULR, the HSS shall not send Monitoring event configuration data to the MME or SGSN within ULA and shall not send subsequent IDR commands requesting the configuration of Monitoring events in the MME or SGSN. If the MME or SGSN indicates that it does not support this feature in IDA, and the HSS has already sent Monitoring event configuration data within IDR, the HSS may store this indication and not send any further updates related to Monitoring events to that MME or SGSN.
20	Dedicated Core Networks	O	Support of Dedicated Core Networks This feature is applicable to the ULR/ULA, IDR/IDA and DSR/DSA command pairs over the S6a and S6d interfaces. If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send DCN-related subscription data (e.g., UE Usage Type) in ULA, and shall not send subsequent IDR or DSR commands when such subscription data are updated. If the MME/SGSN does not indicate support of this feature in the IDA command and the HSS has already sent DCN-related subscription data in IDR, the HSS may store this indication and not send further updates related to DCN subscription data.
21	Non-IP PDN Type APNs	O	Support of Non-IP PDN Type APNs This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a and S6d interfaces. If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send APN configurations with a Non-IP PDN type in the subscription data sent in ULA or in IDR, and shall not send IDR commands with the only purpose to update such subscription data. If the MME or SGSN indicates in the IDA command that it does not support this feature, and the HSS has already sent Non-IP PDN Type APNs within IDR, the HSS may store this indication, and not send any further updates related to Non-IP PDN Type APNs to that MME or SGSN.
22	Non-IP PDP Type APNs	O	Support of Non-IP PDP Type APNs This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a/S6d interface. If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send PDP contexts (as part of the GPRS-Subscription-Data) with a Non-IP PDP type in the subscription data sent in ULA or in IDR, and shall not send IDR commands with the only purpose to update such subscription data. If the MME or SGSN indicates in the IDA command that it does not support this feature, and the HSS has already sent Non-IP PDP Type APNs within IDR, the HSS may store this indication, and not send any further updates related to Non-IP PDP Type APNs to that MME or SGSN.
23	Removal of MSISDN	O	Support of Removal of MSISDN This feature is applicable to the ULR/ULA and DSR/DSA command pairs over the S6a/S6d interface. If the MME/SGSN does not indicate support of this feature in the ULR command, the HSS shall not send DSR with the "MSISDN Withdrawal" bit set, to remove an existing MSISDN value from the subscription profile stored in the MME/SGSN.
24	Emergency Service Continuity	O	Support of Emergency Services Continuity This feature is applicable to the ULR/ULA, NOR/NOA and IDR/IDA command pairs over the S6a interface, when the HSS and the MME support the continuity of emergency services upon mobility between 3GPP and WLAN accesses, as specified in 3GPP TS 23.401 [2], or continuity of emergency services upon mobility between EPS and 5GS without N26 interface, as specified in 3GPP TS 23.502 [67]. If the MME does not indicate support of this feature in a former ULR command, the HSS shall not include the Emergency Info in an ULA command and shall not send an IDR command to update the PGW in use for emergency services. If the HSS does not indicate support of this feature in a former ULA command, the MME shall not send a NOR command to update the PGW in use for emergency services. If the HSS supports this feature on S6a, it shall also support the Emergency Service Continuity feature on SWx, see 3GPP TS 29.273 [59].
25	V2X Capability	O	Support of V2X Service This feature is applicable for the ULR/ULA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the V2X service. If the MME or combined MME/SGSN does not support this feature, the HSS shall not send the related V2X subscription data to the MME or combined MME/SGSN within ULA. If the MME or combined MME/SGSN does not indicate support of this feature in IDA, and the HSS has sent the related V2X subscription data within IDR, the HSS may store this indication, and not send any further V2X subscription data to that MME or that combined MME/SGSN.
26	External-Identifier	O	Support of External-Identifier This feature is applicable for the ULR/ULA, DSR/DSA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the External-Identifier. If the MME or combined MME/SGSN does not support this feature: -The HSS shall not send the External-Identifier subscription data to the MME or combined MME/SGSN within ULA. -The HSS shall not send Monitoring Event configuration for UEs that are part of a group and have no MSISDN as part of its subscription data to the MME/SGSN. -The HSS shall not indicate External-Identifier-Withdrawal in the DSR-Flags AVP of the DSR.
27	NR as Secondary RAT	O	Support of NR as Secondary RAT This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d) when the MME (or combined MME/SGSN) supports NR as Secondary RAT, and over S6d when the SGSN supports the indication related to NR as Secondary RAT (such as, e.g., the related Access Restriction Data, or extended QoS parameters). If the MME, SGSN, or combined MME/SGSN does not support this feature, the HSS shall not send (in ULA) or update (in IDR) subscription data related to NR as Secondary RAT. If the HSS does not support this feature, the MME shall ignore the bit "NR as Secondary RAT Not Allowed" in Access-Restriction-Data.
28	Unlicensed Spectrum as Secondary RAT	O	Support of Unlicensed Spectrum as Secondary RAT This feature is applicable to the ULR/ULA and IDR/IDA command pairs over S6a (and S6d) when the MME (or combined MME/SGSN) supports the use of unlicensed spectrum in the form of LAA or LWA/LWIP as Secondary RAT. If the MME (or combined MME/SGSN) does not support this feature, the HSS shall not send (in ULA) or update (in IDR) subscription data related to the use of unlicensed spectrum in the form of LAA, LWA/LWIP or NR in unlicensed bands as Secondary RAT (such as, e.g., the related Access Restriction Data). If the HSS does not support this feature, the MME shall ignore the bit "Unlicensed Spectrum as Secondary RAT Not Allowed" in Access-Restriction-Data.
29	Ethernet PDN Type APNs	O	Support of Ethernet PDN Type APNs This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a and S6d interfaces. If the MME (or combined MME/SGSN) does not indicate support of this feature in the ULR command, the HSS shall not send APN configurations with an Ethernet PDN type in the subscription data sent in ULA or in IDR, and shall not send IDR commands with the only purpose to update such subscription data. If the MME (or combined MME/SGSN) indicates in the IDA command that it does not support this feature, and the HSS has already sent Ethernet PDN Type APNs within IDR, the HSS may store this indication, and not send any further updates related to Ethernet PDN Type APNs to that MME (or combined MME/SGSN).
30	Extended Reference IDs	O	Extended Reference IDs This feature is applicable to the ULR/ULA and IDR/IDA command pairs over the S6a or S6d interfaces, when the HSS and MME/SGSN support handling 64-bit long Reference IDs. If the MME or SGSN does not indicate support of this feature in ULR, the HSS shall not send ULA or IDR commands containing 64-bit long SCEF Reference IDs or SCEF Reference IDs for Deletion.
Feature bit: The order number of the bit within the Supported-Features AVP, e.g. "1". Feature: A short name that can be used to refer to the bit and to the feature, e.g. "SMS in MME". M/O: Defines if the implementation of the feature is mandatory ("M") or optional ("O"). Description: A clear textual description of the feature. NOTE 1: If both bits, corresponding to the same feature defined for Lg interface and Lgd interface, are not set, and the HSS supports the feature, the HSS shall not send the related LCS information to the SGSN within ULA and IDR.

Features that are not indicated in the Supported-Features AVPs within a given application message shall not be used to construct that message.

7.3.10.2 Feature-List AVP for the S7a/S7d application

For the S7a/S7d application, the feature list does not contain any feature in this release.

7.3.11 Requested-EUTRAN-Authentication-Info

The Requested-EUTRAN-Authentication-Info is of type Grouped. It shall contain the information related to the authentication requests for E-UTRAN.

AVP format

Requested-EUTRAN-Authentication-Info ::= <AVP header: 1408 10415>

[ Number-Of-Requested-Vectors ]

[ Immediate-Response-Preferred ]

[ Re-synchronization-Info ]

*[AVP]

7.3.12 Requested-UTRAN- GERAN-Authentication-Info

The Requested-UTRAN-GERAN-Authentication-Info is of type Grouped. It shall contain the information related to the to authentication requests for UTRAN or GERAN.

AVP format

Requested-UTRAN-GERAN-Authentication-Info ::= <AVP header: 1409 10415>

[ Number-Of-Requested-Vectors]

[ Immediate-Response-Preferred ]

[ Re-synchronization-Info ]

*[AVP]

7.3.13 RAT-Type

The RAT-Type AVP is of type Enumerated and is used to identify the radio access technology that is serving the UE. See 3GPP TS 29.212 [10] for the defined values.

3GPP TS 29.212 [10] defines distinct RAT-Type values for EUTRAN (WB-EUTRAN), EUTRAN-NB-IoT, LTE-M, WB-EUTRAN over satellite access, EUTRAN-NB-IoT over satellite access, LTE-M over satellite access; these values shall be used in the signaling between the serving nodes (MME/SGSN) and the HSS, e.g. to determine the corresponding access restrictions for the UE.

7.3.14 Number-Of-Requested-Vectors

The Number-Of-Requested-Vectors AVP is of type Unsigned32. This AVP shall contain the number of AVs the MME or SGSN is prepared to receive.

7.3.15 Re-Synchronization-Info

The Re-Synchronization-Info AVP is of type OctetString. It shall contain the concatenation of RAND and AUTS.

7.3.16 Immediate-Response-Preferred

The Immediate-Response-Preferred AVP is of type Unsigned32. This optional AVP indicates by its presence that immediate response is preferred, and by its absence that immediate response is not preferred. If present, the value of this AVP is not significant.

When EUTRAN-AVs and UTRAN-AVs or GERAN-AVs are requested, presence of this AVP within the Requested-EUTRAN-Authentication-Info AVP shall indicate that EUTRAN-AVs are requested for immediate use in the MME/SGSN; presence of this AVP within the Requested-UTRAN-GERAN-Authentication-Info AVP shall indicate that UTRAN-AVs or GERAN-AVs are requested for immediate use in the MME/SGSN. It may be used by the HSS to determine the number of vectors to be obtained from the AuC and the number of vectors downloaded to the MME or SGSN.

7.3.17 Authentication-Info

The Authentication-Info AVP is of type Grouped. This AVP contains Authentication Vectors.

AVP format:

Authentication-Info ::= <AVP header: 1413 10415>

*[ E-UTRAN-Vector ]

*[UTRAN-Vector]

*[GERAN-Vector]

*[AVP]

7.3.18 E-UTRAN-Vector

The E-UTRAN-Vector AVP is of type Grouped. This AVP shall contain an E-UTRAN Vector.

AVP format:

E-UTRAN-Vector ::= <AVP header: 1414 10415>

[ Item-Number ]

{ RAND }

{ XRES }

{ AUTN }

{ KASME }

*[AVP]

7.3.19 UTRAN-Vector

The UTRAN-Vector AVP is of type Grouped. This AVP shall contain an UTRAN Vector.

AVP format:

UTRAN-Vector ::= <AVP header: 1415 10415>

[ Item-Number ]

{ RAND }

{ XRES }

{ AUTN }

{ Confidentiality-Key }

{ Integrity-Key }

*[AVP]

7.3.20 GERAN-Vector

The GERAN-Vector AVP is of type Grouped. This AVP shall contain a GERAN Vector.

AVP format:

GERAN-Vector ::= <AVP header: 1416 10415>

[ Item-Number ]

{ RAND }

{ SRES }

{ Kc }

*[AVP]

7.3.21 Network-Access-Mode

The Network-Access-Mode AVP is of type Enumerated. The following values are defined:

PACKET_AND_CIRCUIT (0)

Reserved (1)

ONLY_PACKET (2)

7.3.22 HPLMN-ODB

The HPLMN-ODB AVP is of type Unsigned32 and it shall contain a bit mask indicating the HPLMN specific services of a subscriber that are barred by the operator. The meaning of the bits is HPLMN specific:

Table 7.3.22/1: HPLMN-ODB

Bit	Description
0	HPLMN specific barring type 1
1	HPLMN specific barring type 2
2	HPLMN specific barring type 3
3	HPLMN specific barring type 4

HPLMN-ODB may apply to mobile originated short messages; See 3GPP TS 23.015 [36].

7.3.23 Item-Number

The Item-Number AVP is of type Unsigned32. The Item Number is used to order Vectors received within one request.

7.3.24 Cancellation-Type

The Cancellation-Type AVP is of type Enumerated and indicates the type of cancellation. The following values are defined:

MME_UPDATE_PROCEDURE (0)

This value is used when the Cancel Location is sent to the previous MME due to a received Update Location message from a new MME or due to the HSS+UDM receiving an Nudm_UEContextManagement service request from the AMF or due to the HSS receiving Nhss_UECM_SNDeregistration service operation from UDM (see clause 5.4.2.2 of 3GPP TS 29.563 [70]).

SGSN_UPDATE_PROCEDURE (1)

This value is used when the Cancel Location is sent to the previous SGSN due to a received Update Location message from a new SGSN or due to the HSS+UDM receiving an Nudm_UEContextManagement service request from the AMF or due to the HSS receiving Nhss_UECM_SNDeregistration service operation from UDM (see clause 5.4.2.2 of 3GPP TS 29.563 [70]).

SUBSCRIPTION_WITHDRAWAL (2)

This value is used:

– when the Cancel Location is sent by the HSS to the current MME or SGSN due to withdrawal of the user’s subscription by the HSS operator;

– when the Cancel VCSG Location is sent by the CSS to the current MME or SGSN due to withdrawal of the user’s VPLMN CSG subscription by the CSS operator.

UPDATE_PROCEDURE_IWF (3)

This value is used by an IWF when interworking with a pre-Rel-8 HSS.

INITIAL_ATTACH_PROCEDURE (4)

This value is used when the Cancel Location is sent to the MME or SGSN due to a received Update Location message during initial attach procedure from an SGSN or MME respectively.

7.3.25 DSR-Flags

The DSR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in table 7.3.25/1:

Table 7.3.25/1: DSR-Flags

Bit	Name	Description
0	Regional Subscription Withdrawal	This bit, when set, indicates that Regional Subscription shall be deleted from the subscriber data.
1	Complete APN Configuration Profile Withdrawal	This bit, when set, indicates that all EPS APN configuration data for the subscriber shall be deleted from the subscriber data. This flag only applies to the S6d interface.
2	Subscribed Charging Characteristics Withdrawal	This bit, when set, indicates that the Subscribed Charging Characteristics have been deleted from the subscription data.
3	PDN subscription contexts Withdrawal	This bit, when set, indicates that the PDN subscription contexts whose identifier is included in the Context-Identifier AVP shall be deleted. (Note 1)
4	STN-SR	This bit, when set, indicates that the Session Transfer Number for SRVCC shall be deleted from the subscriber data.
5	Complete PDP context list Withdrawal	This bit, when set, indicates that all PDP contexts for the subscriber shall be deleted from the subscriber data.
6	PDP contexts Withdrawal	This bit, when set, indicates that the PDP contexts whose identifier is included in the Context-Identifier AVP shall be deleted. (Note 2)
7	Roaming Restricted due to unsupported feature	This bit, when set, indicates that the roaming restriction shall be deleted from the subscriber data in the MME or SGSN.
8	Trace Data Withdrawal	This bit, when set, indicates that the Trace Data shall be deleted from the subscriber data.
9	CSG Deleted	This bit, when set, indicates that – the "CSG-Subscription-Data from HSS" shall be deleted in the MME or SGSN when received over the S6a or S6d interface – the "CSG-Subscription-Data from CSS" shall be deleted in the MME or SGSN when received over the S7a or S7d interface.
10	APN-OI-Replacement	This bit, when set, indicates that the UE level APN-OI-Replacement shall be deleted from the subscriber data.
11	GMLC List Withdrawal	This bit, when set, indicates that the subscriber’s LCS GMLC List shall be deleted from the MME or SGSN.
12	LCS Withdrawal	This bit, when set, indicates that the LCS service whose code is included in the SS-Code AVP shall be deleted from the MME or SGSN.
13	SMS Withdrawal	This bit, when set, indicates that the SMS service whose code is included in the SS-Code AVP or TS-Code AVP shall be deleted from the MME or SGSN.
14	Subscribed periodic RAU-TAU Timer Withdrawal	This bit, when set, indicates that the subscribed periodic RAU TAU Timer value shall be deleted from the subscriber data.
15	Subscribed VSRVCC Withdrawal	This bit, when set, indicates that the Subscribed VSRVCC shall be deleted from the subscriber data.
16	A-MSISDN Withdrawal	This bit, when set, indicates that the additional MSISDN, if present, shall be deleted from the subscriber data.
17	ProSe Withdrawal	This bit, when set, indicates that the ProSe subscription data shall be deleted from the MME or combined MME/SGSN.
18	Reset-IDs	This bit, when set, indicates that the set of Reset-IDs shall be deleted from the MME or SGSN.
19	DL-Buffering-Suggested-Packet-Count Withdrawal	This bit, when set, indicates that the DL-Buffering-Suggested-Packet-Count shall be deleted in the MME or SGSN.
20	Subscribed IMSI-Group-Id Withdrawal	This bit, when set, indicates that all subscribed IMSI-Group-Id(s) shall be deleted in the MME or SGSN.
21	Delete monitoring events	This bit when set indicates to the MME or SGSN to delete all the Monitoring events for the subscriber which are associated with the provided SCEF-ID.
22	User Plane Integrity Protection Withdrawal	This bit, when set, indicates to the SGSN that User Plane Integrity Protection may no longer be required when GERAN is used. The MME shall ignore it.
23	MSISDN Withdrawal	This bit, when set, indicates that the MSISDN shall be deleted from the subscriber data. It is also used by the MME/SGSN to delete those monitoring events created using the MSISDN.
24	UE Usage Type Withdrawal	This bit, when set, indicates to the MME or SGSN that the UE Usage Type shall be deleted from the subscription data.
25	V2X Withdrawal	This bit, when set, indicates that the V2X subscription data shall be deleted from the MME or combined MME/SGSN.
26	External-Identifier-Withdrawal	This bit, when set, indicates that the External-Identifier shall be deleted from the subscriber data. It is also used by the MME/SGSN to delete those monitoring events created using the removed External Identifier or all monitoring events created for any External Identifier in case of removing the default External Identifier.
27	Aerial-UE-Subscription Withdrawal	This bit, when set, indicates that the Aerial UE subscription shall be deleted from the subscriber data.
28	Paging Time Window Subscription Withdrawal	This bit, when set, indicates that the Paging Time Window subscription shall be deleted from the subscriber data.
29	Active-Time-Withdrawal	This bit, when set, indicates that the Active Time used for PSM shall be deleted from the subscriber data.
30	eDRX-Cycle-Length -Withdrawal	This bit, when set, indicates that the eDRX-Cycle-Length shall be deleted from the subscriber data. . If the eDRX-Related-RAT is present in the DSR command, only the eDRX Cycle Length for indicated RAT types shall be deleted. Otherwise, the entire eDRX Cycle Length subscription for all RAT types shall be deleted.
31	Service-Gap-Time-Withdrawal	This bit, when set, indicates that the Service Gap Time shall be deleted from the subscriber data.
Note 1: If the Complete APN Configuration Profile Withdrawal bit is set, this bit should not be set. Note 2: If the Complete PDP context list Withdrawal bit is set, this bit should not be set. Note 3: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN. Note 4: Bits 3 and 6 are excluding alternatives and shall not both be set. Note 5: When this AVP is transferred over the S7a/S7d interface, only the bit 9 (CSG Deleted) is meaningful, other bits shall be cleared.

7.3.26 DSA-Flags

The DSA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in table 7.3.26/1:

Table 7.3.26/1: DSA-Flags

Bit	Name	Description
0	Network Node area restricted	This bit, when set, shall indicate that the complete Network Node area (SGSN area) is restricted due to regional subscription.
Note: Bits not defined in this table shall be cleared by the sending SGSN and discarded by the receiving HSS.

7.3.27 Context-Identifier

The Context-Identifier AVP is of type Unsigned32.

7.3.28 Void

7.3.29 Subscriber-Status

The 3GPP Subscriber Status AVP is of type Enumerated. It shall indicate if the service is barred or granted. The following values are defined:

SERVICE_GRANTED (0)

OPERATOR_DETERMINED_BARRING (1)

7.3.30 Operator-Determined-Barring

The Operator-Determined-Barring AVP is of type Unsigned32 and it shall contain a bit mask indicating the services of a subscriber that are barred by the operator. The meaning of the bits is the following:

Table 7.3.30/1: Operator-Determined-Barring

Bit	Description
0	All Packet Oriented Services Barred
1	Roamer Access HPLMN-AP Barred
2	Roamer Access to VPLMN-AP Barred
3	Barring of all outgoing calls
4	Barring of all outgoing international calls
5	Barring of all outgoing international calls except those directed to the home PLMN country
6	Barring of all outgoing inter-zonal calls
7	Barring of all outgoing inter-zonal calls except those directed to the home PLMN country
8	Barring of all outgoing international calls except those directed to the home PLMN country and Barring of all outgoing inter-zonal calls

7.3.31 Access-Restriction-Data

The Access-Restriction-Data AVP is of type Unsigned32 and it shall contain a bit mask where each bit when set to 1 indicates a restriction. The meaning of the bits is the following:

Table 7.3.31/1: Access-Restriction-Data

Bit	Description
0	UTRAN Not Allowed
1	GERAN Not Allowed
2	GAN Not Allowed
3	I-HSPA-Evolution Not Allowed
4	WB-E-UTRAN Not Allowed
5	HO-To-Non-3GPP-Access Not Allowed
6	NB-IoT Not Allowed
7	Enhanced Coverage Not Allowed
8	NR as Secondary RAT in E-UTRAN Not Allowed
9	Unlicensed Spectrum as Secondary RAT Not Allowed
10	NR in 5GS Not Allowed
11	LTE-M Not Allowed
12	WB-E-UTRAN Except LTE-M Not Allowed
13	WB-E-UTRAN(LEO) Not Allowed
14	WB-E-UTRAN(MEO) Not Allowed
15	WB-E-UTRAN(GEO) Not Allowed
16	WB-E-UTRAN(OTHERSAT) Not Allowed
17	NB-IoT(LEO) Not Allowed
18	NB-IoT(MEO) Not Allowed
19	NB-IoT(GEO) Not Allowed
20	NB-IoT(OTHERSAT) Not Allowed
21	LTE-M(LEO) Not Allowed
22	LTE-M(MEO) Not Allowed
23	LTE-M(GEO) Not Allowed
24	LTE-M(OTHERSAT) Not Allowed
NOTE 1: Bits not defined in this table shall be cleared by the HSS and discarded by the receiving MME/SGSN. NOTE 2: Bits 11 and 12 are only used when bit 4 is not set.

The restriction "HO-To-Non-3GPP-Access Not Allowed" shall take a higher precedence than the APN-level parameter "WLAN-Offloadability" (see clause 7.3.181).

7.3.32 APN-OI-Replacement

The APN-OI-Replacement AVP is of type UTF8String. This AVP shall indicate the domain name to replace the APN OI for the non-roaming case and the home routed roaming case when constructing the APN, and the APN-FQDN upon which to perform a DNS resolution. See 3GPP TS 23.003 [3] and 3GPP TS 29.303 [38].

The contents of the APN-OI-Replacement AVP shall be formatted as a character string composed of one or more labels separated by dots (".").

7.3.33 All-APN-Configurations-Included-Indicator

The All-APN-Configurations-Included-Indicator AVP is of type Enumerated. The following values are defined:

All_APN_CONFIGURATIONS_INCLUDED (0)

MODIFIED_ADDED_APN_CONFIGURATIONS_INCLUDED (1)

7.3.34 APN-Configuration-Profile

The APN-Configuration-Profile AVP is of type Grouped. It shall contain the information related to the user’s subscribed APN configurations for EPS.

The AVP format shall conform to:

APN-Configuration-Profile ::= <AVP header: 1429 10415>

{ Context-Identifier }

[ Additional-Context-Identifier ]

[ Third-Context-Identifier ]

{ All-APN-Configurations-Included-Indicator }

1*{APN-Configuration}

*[AVP]

The Subscription-Data AVP associated with an IMSI contains one APN-Configuration-Profile AVP.

Each APN-Configuration-Profile AVP contains one or more APN-Configuration AVPs.

Each APN-Configuration AVP describes the configuration for a single APN.

Therefore, the cardinality of the relationship between IMSI and APN is one-to-many.

The Context-Identifier AVP shall identify the per subscriber’s default APN configuration.

If present, the Additional-Context-Identifier AVP shall identify another default APN configuration, only for those subscriptions containing more than one types of APNs i.e. among APNs with an IP-based PDN type, APNs with a Non-IP PDN type, and APNs with an Ethernet PDN type; in this case, each of those two default APN configurations shall have a different PDN type category (e.g. one default APN with an IP-based PDN type, and another default APN with a Non-IP PDN type).

If present, the Third-Context-Identifier AVP shall identify another default APN configuration, only for those subscriptions containing more than two types of APNs i.e. among APNs with an IP-based PDN type, APNs with a Non-IP PDN type, and APNs with an Ethernet PDN type; in this case, each of those three default APN configurations shall have a different PDN type category (i.e. one default APN with an IP-based PDN type, and another default APN with a Non-IP PDN type and one default APN with an Ethernet PDN type).

7.3.35 APN-Configuration

The APN-Configuration AVP is of type Grouped. It shall contain the information related to the user’s subscribed APN configurations. The Context-Identifier in the APN-Configuration AVP shall identify that APN configuration, and it shall not have a value of zero. Furthermore, the Context-Identifier in the APN-Configuration AVP shall uniquely identify the EPS APN configuration per subscription. For a particular EPS user having multiple APN configurations, the Service-Selection AVP values shall be unique across APN-Configuration AVPs.

The AVP format shall conform to:

APN-Configuration ::= <AVP header: 1430 10415>

{ Context-Identifier }

* 2 [ Served-Party-IP-Address ]

{ PDN-Type }

{ Service-Selection}

[ EPS-Subscribed-QoS-Profile ]

[ VPLMN-Dynamic-Address-Allowed ]

[MIP6-Agent-Info ]

[ Visited-Network-Identifier ]

[ PDN-GW-Allocation-Type ]

[ 3GPP-Charging-Characteristics ]

[ AMBR ]

*[ Specific-APN-Info ]

[ APN-OI-Replacement ]

[ SIPTO-Permission ]

[ LIPA-Permission ]

[ Restoration-Priority ]

[ SIPTO-Local-Network-Permission ]

[ WLAN-offloadability ]

[ Non-IP-PDN-Type-Indicator ]

[ Non-IP-Data-Delivery-Mechanism ]

[ SCEF-ID ]

[ SCEF-Realm ]

[ Preferred-Data-Mode ]

[ PDN-Connection-Continuity ]

[ RDS-Indicator ]

[ Interworking-5GS-Indicator ]

[ Ethernet-PDN-Type-Indicator ]

*[ AVP ]

The AMBR included in this grouped AVP shall include the AMBR associated to this specific APN configuration (APN-AMBR).

The Served-Party-IP-Address AVP may be present 0, 1 or 2 times. These AVPs shall be present if static IP address allocation is used for the UE, and they shall contain either of:

– an IPv4 address, or

– an IPv6 address/prefix, or

– both, an IPv4 address and an IPv6 address/prefix.

For the IPv6 prefix, the lower 64 bits of the address shall be set to zero.

The PDN-GW-Allocation-Type AVP applies to the MIP6-Agent-Info AVP. Therefore, it shall not be present if MIP6-Agent-Info is not present.

The APN-OI-Replacement included in this grouped AVP shall include the APN-OI-Replacement associated with this APN configuration. This APN-OI-Replacement has higher priority than UE level APN-OI-Replacement.

The Visited-Network-Identifier AVP indicates the PLMN where the PGW was allocated, in case of dynamic PGW assignment.

NOTE: If interworking with MAP is needed, the Context-Identifier will be in the range of 1 and 50.

The Non-IP-Data-Delivery-Mechanism shall only be present when Non-IP-PDN-Type-Indicator is set to TRUE (1).

The SCEF-ID AVP and the SCEF-Realm AVP shall only be present when Non-IP-PDN-Type-Indicator is set to TRUE (1), and Non-IP-Data-Delivery-Mechanism is set to SCEF-BASED-DATA-DELIVERY (1).

The RDS-Indicator may be present when Non-IP-PDN-Type-Indicator is set to TRUE (1), and Non-IP-Data-Delivery-Mechanism is set to SCEF-BASED-DATA-DELIVERY (1).

Absence of PDN-Connection-Continuity AVP indicates that the handling is left to local VPLMN policy.

7.3.36 Service-Selection

The Service-Selection AVP is of type of UTF8String. This AVP shall contain either the APN Network Identifier (i.e. an APN without the Operator Identifier) per 3GPP TS 23.003 [3], clauses 9.1 & 9.1.1, or this AVP shall contain the wild card value per 3GPP TS 23.003 [3], clause 9.2.1, and 3GPP TS 23.008 [30], clause 2.13.6).

The contents of the Service-Selection AVP shall be formatted as a character string composed of one or more labels separated by dots ("."), or as the wild card APN, i.e., consisting of only one ASCII label, "*".

This AVP is defined in IETF RFC 5778[20].

7.3.37 EPS-Subscribed-QoS-Profile

The EPS-Subscribed-QoS-Profile AVP is of type Grouped. It shall contain the bearer-level QoS parameters (QoS Class Identifier and Allocation Retention Priority) associated to the default bearer for an APN (see 3GPP TS 23.401 [2], clause 4.7.3).

AVP format

EPS-Subscribed-QoS-Profile ::= <AVP header: 1431 10415>

{ QoS-Class-Identifier }

{ Allocation-Retention-Priority }

*[AVP]

NOTE: QoS-Class-Identifier is defined in 3GPP TS 29.212 [10] as an Enumerated AVP. The values allowed for this AVP over the S6a/S6d interface are only those associated to non-GBR bearers, as indicated in 3GPP TS 23.008 [30]; e.g., values QCI_1, QCI_2, QCI_3 and QCI_4, which are associated to GBR bearers, cannot be sent over S6a/S6d.

7.3.38 VPLMN-Dynamic-Address-Allowed

The VPLMN-Dynamic-Address-Allowed AVP is of type Enumerated. It shall indicate whether for this APN, the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally, the PDN GW in the domain of the VPLMN.. If this AVP is not present, this means that the UE is not allowed to use PDN GWs in the domain of the VPLMN. The following values are defined:

NOTALLOWED (0)

ALLOWED (1)

7.3.39 STN-SR

The STN-SR AVP is of type OctetString and shall contain the Session Transfer Number for SRVCC. See 3GPP TS 23.003 [3] for the definition of STN-SR. This AVP contains an STN-SR, in international number format as described in ITU-T Rec E.164 [41], encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

7.3.40 Allocation-Retention-Priority

The Allocation-Retention-Priorit AVP is of typeGrouped and is defined in 3GPP TS 29.212 [10]. It shall indicate the Priority of Allocation and Retention for the corresponding APN configuration.

AVP format

Allocation-Retention-Priority ::= <AVP header: 1034 10415>

{ Priority-Level }

[ Pre-emption-Capability ]

[ Pre-emption-Vulnerability ]

If the Pre-emption-Capability AVP is not present in the Allocation-Retention-Priority AVP, the default value shall be PRE-EMPTION_CAPABILITY_DISABLED (1).

If the Pre-emption-Vulnerability AVP is not present in the Allocation-Retention-Priority AVP, the default value shall be PRE-EMPTION_VULNERABILITY_ENABLED (0).

7.3.41 AMBR

The AMBR AVP is of type Grouped.

It shall contain the maximum requested bandwidth for Uplink and Downlink traffic. The Max-Requested-Bandwidth-(UL/DL) AVPs shall encode the bandwidth value in bits per second, having an upper limit of 4294967295 bits per second. The Extended-Max-Requested-BW-(UL/DL) AVPs shall encode the bandwidth value in kilobits (1000 bits) per second, having an upper limit of 4294967295 kilobits per second.

When the maximum bandwidth value to be set for UL (or DL, respectively) traffic is lower than 4294967296 bits per second, the Max-Requested-Bandwidth-UL (or -DL, respectively) AVP shall be present, and set to the requested bandwidth value in bits per second, and the Extended-Max-Requested-BW-UL (or -DL, respectively) AVP shall be absent.

When the maximum bandwidth value to be set for UL (or DL, respectively) traffic is higher than 4294967295 bits per second, the Max-Requested-Bandwidth-UL (or DL, respectively) AVP shall be present, and set to its upper limit 4294967295, and the Extended-Max-Requested-BW-UL (or -DL, respectively) shall be present, and set to the requested bandwidth value in kilobits (1000 bits) per second.

NOTE: The value applicable for Max-Requested-Bandwidth-UL (or DL, respectively) is between 1 and 4294967295 bits per second, and the value applicable for Extended-Max-Requested-BW-UL (or -DL, respectively) is between 4294968 and 4294967295 kilobits per second. The AMBR AVP cannot indicate the requested bandwidth between 4294967296 and 4294967999 bits per second, and any larger value that cannot be represented in the granularity of kilobits per second.

AVP format

AMBR ::= <AVP header: 1435 10415>

{ Max-Requested-Bandwidth-UL }

{ Max-Requested-Bandwidth-DL }

[ Extended-Max-Requested-BW-UL ]

[ Extended-Max-Requested-BW-DL ]

*[AVP]

7.3.42 MIP-Home-Agent-Address

The MIP-Home-Agent-Address AVP is of type Address and is defined in IETF RFC 4004 [27]. This AVP shall contain either IPv4 or IPv6 address of the PDN-GW and this IP address shall be used as the PDN-GW IP address.

7.3.43 MIP-Home-Agent-Host

The MIP-Home-Agent-Host is of type Grouped and is defined in IETF RFC 4004 [27]. This AVP shall contain a FQDN of the PDN-GW which shall be used to resolve the PDN-GW IP address using the Domain Name Service function.

MIP-Home-Agent-Host grouped AVP is composed by Destination-Host and Destination-Realm AVPs.

Destination-Host shall contain the hostname of the PDN-GW, formatted as described in 3GPP TS 29.303 [38], clause 4.3.2.

Destination-Realm shall be formatted as:

epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org

where MNC and MCC values indicate the PLMN where the PDN-GW is located.

7.3.44 PDN-GW-Allocation-Type

The PDN-GW-Allocation-Type AVP is of type Enumerated. It shall indicate whether the PDN GW address included in MIP6-Agent-Info has been statically allocated (i.e. provisioned in the HSS by the operator), or dynamically selected by other nodes. The following values are defined:

STATIC (0)

DYNAMIC (1)

7.3.45 MIP6-Agent-Info

The MIP6-Agent-InfoAVP is of type Grouped and is defined in IETF RFC 5447 [26]. This AVP shall contain the identity of the PDN-GW. This AVP is used to convey the identity of the PDN-GW between the MME/SGSN and the HSS regardless of the specific mobility protocol used (GTP or PMIPv6). The identity of PDN-GW is either an IP address transported in MIP-Home-Agent-Address or an FQDN transported in MIP-Home-Agent-Host. FQDN shall be used if known to the MME/SGSN/HSS.

AVP format

MIP6-Agent-Info ::= < AVP Header: 486 >

*2[ MIP-Home-Agent-Address ]

[ MIP-Home-Agent-Host ]

[ MIP6-Home-Link-Prefix ]

*[ AVP ]

Within the MIP6-Agent-Info AVP, if static address allocation is used, there may be either:

– an IPv4 address or an IPv6 address of the PGW contained in one MIP-Home-Agent-Address AVP;

– both IPv4 address and IPv6 address of the PGW contained in two MIP-Home-Agent-Address AVPs.

The AVP MIP6-Home-Link-Prefix is not used in S6a/S6d, but it is included here to reflect the complete IETF definition of the grouped AVP.

7.3.46 RAT-Frequency-Selection-Priority-ID

The RAT-Frequency-Selection-Priority-ID AVP is of type Unsigned32 and shall contain the subscribed value of Subscriber Profile ID for RAT/Frequency Priority. For details, see 3GPP TS 23.401 [2] and 3GPP TS 23.060 [12] . The coding is defined in 3GPP TS 36.413 [19]. Values shall be in the range of 1 to 256.

7.3.47 IDA-Flags

The IDA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meanings of the bits are defined in table 7.3.47/1:

Table 7.3.47/1: IDA-Flags

Bit	Name	Description
0	Network Node area restricted	This bit, when set, shall indicate that the complete Network Node area (SGSN area) is restricted due to regional subscription.
Note: Bits not defined in this table shall be cleared by the sending SGSN and discarded by the receiving HSS.

7.3.48 PUA-Flags

The PUA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meanings of the bits are defined in table 7.3.48/1:

Table 7.3.48/1: PUA-Flags

bit	name	Description
0	Freeze M-TMSI	This bit, when set, shall indicate to the MME that the M-TMSI needs to be frozen, i.e. shall not be immediately re-used.
1	Freeze P-TMSI	This bit, when set, shall indicate to the SGSN that the P-TMSI needs to be frozen, i.e. shall not be immediately re-used.
Note: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

7.3.49 NOR-Flags

The NOR-Flags AVP is of type Unsigned32 and it contains a bit mask. The meaning of the bits is defined in table 7.3.49/1:

Table 7.3.49/1: NOR-Flags

bit	name	Description
0	Single-Registration-Indication	This bit, when set, indicates that the HSS shall send Cancel Location to the SGSN. An SGSN shall not set this bit when sending NOR.
1	SGSN area restricted	This bit, when set, shall indicate that the complete SGSN area is restricted due to regional subscription.
2	Ready for SM from SGSN	This bit, when set, shall indicate that the UE is present or the UE has memory capacity available to receive one or more short messages via SGSN.
3	UE Reachable from MME	This bit, when set, shall indicate that the UE has become reachable again from MME.
4	Reserved	The use of this bit is deprecated. This bit shall be discarded by the receiving HSS.
5	UE Reachable from SGSN	This bit, when set, shall indicate that the UE has become reachable again from SGSN.
6	Ready for SM from MME	This bit, when set, shall indicate that the UE is present or the UE has memory capacity available to receive one or more short messages via MME.
7	Homogeneous Support of IMS Voice Over PS Sessions	This bit, when set, shall indicate that the Homogeneous Support of IMS Voice Over PS Sessions is updated.
8	S6a/S6d-Indicator	This bit, when set, shall indicate that the NOR message is sent on the S6a interface, i.e. the message is from the MME or the MME part on the combined MME/SGSN. This bit, when cleared, indicates that the NOR message is sent on the S6d interface, i.e. the message is from the SGSN or the SGSN part on the combined MME/SGSN.
9	Removal of MME Registration for SMS	This bit, when set, shall indicate that the MME requests to remove its registration for SMS.
NOTE 1: The S6a/S6d-Indicator flag shall be used together with Homogeneous Support of IMS Voice Over PS Sessions flag, i.e. if the Homogeneous Support of IMS Voice Over PS Sessions bit is set, the S6a/S6d-Indicator bit shall be set if the message is sent from the MME or the MME part on the combined MME/SGSN, and shall be cleared if the message is sent from the SGSN or the SGSN part on the combined MME/SGSN. This S6a/S6d-Indicator bit shall be discarded by the receiving HSS if the Homogeneous Support of IMS Voice Over PS Sessions bit is not set. NOTE 2: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS.

7.3.50 User-Id

The User-Id AVP shall be of type UTF8String. It shall contain the leading digits of an IMSI (i.e. MCC, MNC, leading digits of MSIN, see 3GPP TS 23.003 [3], clause 2.2) formatted as a character string. Within a HSS, a User-Id identifies a set of subscribers, each with identical leading IMSI digits.

7.3.51 Equipment-Status

The Equipment-Status AVP is of type Enumerated, and shall contain the status of the mobile equipment. The following values are defined:

PERMITTEDLISTED (0)

PROHIBITEDLISTED (1)

TRACKINGLISTED (2)

7.3.52 Regional-Subscription-Zone-Code

The Regional-Subscription-Zone-Code AVP is of type OctetString. It shall contain a Zone Code (ZC) as defined in 3GPP TS 23.003 [3], clause 4.4. Up to 10 Zone Codes per VPLMN can be defined as part of the users’s subscription data.

NOTE 1: Each zone code represents a collection of tracking area or routing areas (defined by the operator of the VPLMN) where the user is allowed, or disallowed, to roam. The determination of which areas are actually allowed, and which ones are not allowed, is done by the serving node (MME/SGSN) in an implementation-dependent manner.

NOTE 2: The description of RSZI in 3GPP TS 23.003 [3] is applicable, in the context of this specification, not only to location areas, but also to routing and tracking areas.

7.3.53 RAND

The RAND AVP is of type OctetString. This AVP shall contain the RAND. See 3GPP TS 33.401 [5].

7.3.54 XRES

The XRES AVP is of type OctetString. This AVP shall contain the XRES. See 3GPP TS 33.401 [5].

7.3.55 AUTN

The AUTN AVP is of type OctetString. This AVP shall contain the AUTN. See 3GPP TS 33.401 [5].

7.3.56 KASME

The KASME AVP is of type OctetString. This AVP shall contain the K_ASME. See 3GPP TS 33.401 [5].

7.3.57 Confidentiality-Key AVP

The Confidentiality-Key is of type OctetString, and shall contain the Confidentiality Key (CK).

7.3.58 Integrity-Key AVP

The Integrity-Key is of type OctetString, and shall contain the Integrity Key (IK).

7.3.59 Kc AVP

The Kc AVP is of type OctetString, and shall contain the Ciphering Key (Kc).

7.3.60 SRES

The SRES AVP is of type OctetString. This AVP shall contain the SRES. See 3GPP TS 33.102 [18].

7.3.61 Void

7.3.62 PDN-Type

The PDN-Type AVP is of type Enumerated and indicates the address type of the PDN, when it is IP-based.

NOTE: There are certain PDNs that can be accessed without using IP. These are identified by a specific PDN type indicator in their APN configuration settings (e.g. see clauses 7.3.204 and 7.3.232).

The following values are defined:

IPv4 (0)

This value shall be used to indicate that the PDN can be accessed only in IPv4 mode.

IPv6 (1)

This value shall be used to indicate that the PDN can be accessed only in IPv6 mode.

IPv4v6 (2)

This value shall be used to indicate that the PDN can be accessed both in IPv4 mode, in IPv6 mode, and also from UEs supporting dualstack IPv4v6.

IPv4_OR_IPv6 (3)

This value shall be used to indicate that the PDN can be accessed either in IPv4 mode, or in IPv6 mode, but not from UEs supporting dualstack IPv4v6. It should be noted that this value will never be used as a requested PDN Type from the UE, since UEs will only use one of their supported PDN Types, i.e., IPv4 only, IPv6 only or IPv4v6 (dualstack). This value is only used as part of the APN subscription context, as an authorization mechanism between HSS and MME.

7.3.63 Trace-Data AVP

The Trace-Data AVP is of type Grouped. This AVP shall contain the information related to trace function.

AVP format

Trace-Data ::= <AVP header: 1458 10415>

{Trace-Reference}

{Trace-Depth}

{Trace-NE-Type-List}

[Trace-Interface-List]

{Trace-Event-List}

[OMC-Id]

{Trace-Collection-Entity}

[MDT-Configuration]

*[AVP]

7.3.64 Trace-Reference AVP

The Trace-Reference AVP is of type OctetString. This AVP shall contain the concatenation of MCC, MNC and Trace ID, where the Trace ID is a 3 byte Octet String. See 3GPP TS 32.422 [23].

The content of this AVP shall be encoded as octet strings according to table 7.3.64/1.

See 3GPP TS 24.008 [31], clause 10.5.1.13, PLMN list, for the coding of MCC and MNC. If MNC is 2 digits long, bits 5 to 8 of octet 2 are coded as "1111".

Table 7.3.64/1: Encoding format for Trace-Reference AVP

8	7	6	5	4	3	2	1
MCC digit 2				MCC digit 1				octet 1
MNC digit 3				MCC digit 3				octet 2
MNC digit 2				MNC digit 1				octet 3
Trace ID								octet 4
								octet 5
								octet 6

7.3.65 Void

7.3.66 Void

7.3.67 Trace-Depth AVP

The Trace-Depth AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Trace Depth.

7.3.68 Trace-NE-Type-List AVP

The Trace-NE-Type-List AVP is of type OctetString. Octets are coded according to 3GPP TS 32.422 [23].

7.3.69 Trace-Interface-List AVP

The Trace-Interface-List AVP is of type OctetString. Octets are coded according to 3GPP TS 32.422 [23].

7.3.70 Trace-Event-List AVP

The Trace-Event-List AVP is of type OctetString. Octets are coded according to 3GPP TS 32.422 [23].

7.3.71 OMC-Id AVP

The OMC-Id AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24].

7.3.72 GPRS-Subscription-Data

The GPRS-Subscription-Data AVP is of type Grouped. It shall contain the information related to the user profile relevant for GPRS.

AVP format:

GPRS-Subscription-Data ::= <AVP header: 1467 10415>

{ Complete-Data-List-Included-Indicator }

1*50{PDP-Context}

*[AVP]

NOTE: The max number of PDP-Context AVP aligns with the value of maxNumOfPDP-Contexts as defined in 3GPP TS 29.002 [24].

7.3.73 Complete-Data-List-Included-Indicator

The Complete-Data-List-Included-Indicator AVP is of type Enumerated. The following values are defined:

All_PDP_CONTEXTS_INCLUDED (0)

MODIFIED_ADDED_PDP CONTEXTS_INCLUDED (1)

7.3.74 PDP-Context

The PDP-Context AVP is of type Grouped. For a particular GPRS user having multiple PDP Context configurations, the Service-Selection AVP values may be the same for different PDP-Context AVPs.

AVP format

PDP-Context ::= <AVP header: 1469 10415>

{ Context-Identifier }

{ PDP-Type }

[ PDP-Address ]

{ QoS-Subscribed }

[ VPLMN-Dynamic-Address-Allowed ]

{ Service-Selection }

[3GPP-Charging-Characteristics]

[ Ext-PDP-Type ]

[ Ext-PDP-Address ]

[ AMBR ]

[ APN-OI-Replacement ]

[ SIPTO-Permission ]

[ LIPA-Permission ]

[ Restoration-Priority ]

[ SIPTO-Local-Network-Permission ]

[ Non-IP-Data-Delivery-Mechanism ]

[ SCEF-ID ]

*[AVP]

The Ext-PDP-Address AVP may be present only if the PDP-Address AVP is present. If the Ext-PDP-Address AVP is present, then it shall not contain the same address type (IPv4 or IPv6) as the PDP-Address AVP.

When PDP-Type takes the value Non-IP (HEX 02), the Ext-PDP-Type AVP shall be absent.

The AMBR included in this grouped AVP shall include the AMBR associated to the APN included in the PDP-Context AVP (APN-AMBR).

The APN-OI-Replacement included in this grouped AVP shall include the APN-OI-Replacement associated to the APN included in the PDP-Context. This APN-OI-Replacement has higher priority than UE level APN-OI-Replacement.

The Non-IP-Data-Delivery-Mechanism shall only be present when PDP-Type takes the value Non-IP (HEX 02).

The SCEF-ID shall only be present when Non-IP-Data-Delivery-Mechanism takes the value SCEF-BASED-DATA-DELIVERY (1).

7.3.75 PDP-Type

The PDP-Type AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24]. The allowed values are one of IPv4 encoded as HEX (21) or IPv6 encoded as HEX (57) or Non-IP encoded as HEX (02).

7.3.75A Ext-PDP-Type

The Ext-PDP-Type AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24] and 3GPP TS 29.060 [39] and shall contain the value of IPv4v6.

7.3.76 Void

7.3.77 QoS-Subscribed

The QoS-Subscribed AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24] (octets of QoS-Subscribed, Ext-QoS-Subscribed, Ext2-QoS-Subscribed, Ext3-QoS-Subscribed and Ext4-QoS-Subscribed values are concatenated).

7.3.78 CSG-Subscription-Data

The CSG-Subscription-Data AVP is of type Grouped. This AVP shall contain the CSG-Id, and may contain the associated Visited-PLMN-Id, an associated expiration date and the APNs which are allowed to be accessed via Local IP Access from the CSG.

If the Visited-PLMN-Id is not present, the CSG-Subscription-Data corresponds to the registered PLMN (i.e. the visited PLMN) of the MME or the SGSN.

AVP format

CSG-Subscription-Data ::= <AVP header: 1436 10415>

{ CSG-Id }

[ Expiration-Date ]

*[ Service-Selection ]

[ Visited-PLMN-Id ]

*[AVP]

7.3.79 CSG-Id

The CSG-Id AVP is of type Unsigned32. Values are coded according to 3GPP TS 23.003 [3]. Unused bits (least significant) shall be padded with zeros.

7.3.80 Expiration-Date

The Expiration-Date AVP is of type Time (see IETF RFC 6733 [61]) and contains the point in time when subscription to the CSG-Id expires.

7.3.81 Roaming-Restricted-Due-To-Unsupported-Feature

The Roaming-Restricted-Due-To-Unsupported-Feature AVP is of type Enumerated and indicates that roaming is restricted due to unsupported feature. The following value is defined:

Roaming-Restricted-Due-To-Unsupported-Feature (0)

7.3.82 Specific-APN-Info AVP

The Specific-APN-Info AVP is of type Grouped. It shall only be present in the APN configuration when the APN is a wild card APN. It shall contain the APN which is not present in the subscription context but the UE is authorized to connect to and the identity of the registered PDN-GW.

The AVP format shall conform to:

Specific-APN-Info ::= <AVP header: 1472 10415>

{ Service-Selection }

{ MIP6-Agent-Info }

[ Visited-Network-Identifier ]

*[ AVP ]

7.3.83 Alert-Reason AVP

The Alert-Reason AVP is of type Enumerated. The following values are defined:

UE_PRESENT (0)

UE_MEMORY_AVAILABLE (1)

7.3.84 LCS-Info

The LCS-Info AVP is of type Grouped. This AVP shall contain the following LCS related information for a subscriber:

– list of GMLCs in the HPLMN that are permitted to issue a call/session unrelated or call/session related MT-LR location request for this UE;

– privacy exception list that is applicable only over the S6d interface;

– MO-LR list.

AVP format

LCS-Info ::= <AVP header: 1473 10415>

*[ GMLC-Number]

*[ LCS-PrivacyException ]

*[ MO-LR ]

*[AVP]

7.3.85 GMLC-Number

The GMLC-Number AVP is of type OctetString. This AVP shall contain the ISDN number of the GMLC in international number format as described in ITU-T Rec E.164 [41] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

7.3.86 LCS-PrivacyException

The LCS-PrivacyException AVP is of type Grouped. This AVP shall contain the classes of LCS Client that are allowed to locate any target UE.

AVP format

LCS-PrivacyException ::= <AVP header: 1475 10415>

{ SS-Code }

{ SS-Status }

[ Notification-To-UE-User ]

*[ External-Client ]

*[ PLMN-Client ]

*[ Service-Type ]

*[AVP]

7.3.87 SS-Code

The SS-Code AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24].

7.3.88 SS-Status

The SS-Status AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24]. For details, see 3GPP TS 23.011 [29].

7.3.89 Notification-To-UE-User

The Notification- To-UE-User AVP is of type Enumerated. The following values are defined:

NOTIFY_LOCATION_ALLOWED (0)

NOTIFYANDVERIFY_LOCATION_ALLOWED_IF_NO_RESPONSE (1)

NOTIFYANDVERIFY_LOCATION_NOT_ALLOWED_IF_NO_RESPONSE (2)

LOCATION_NOT_ALLOWED (3)

7.3.90 External-Client

The External-Client AVP is of type Grouped. This AVP shall contain the identities of the external clients that are allowed to locate a target UE for a MT-LR.

AVP format

External-Client ::= <AVP header: 1479 10415>

{ Client-Identity }

[ GMLC-Restriction ]

[ Notification-To-UE-User ]

*[AVP]

7.3.91 Client-Identity

The Client-Identity AVP is of type OctetString and it shall contain the ISDN number of the external client in international number format as described in ITU-T Rec E.164 [41] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

7.3.92 GMLC-Restriction

The GMLC-Restriction AVP is of type Enumerated. The following values are defined:

GMLC_LIST (0)

HOME_COUNTRY (1)

7.3.93 PLMN-Client

The PLMN-Client AVP is of type Enumerated. The following values are defined:

BROADCAST_SERVICE (0)

O_AND_M_HPLMN (1)

O_AND_M_VPLMN (2)

ANONYMOUS_LOCATION (3)

TARGET_UE_SUBSCRIBED_SERVICE (4)

7.3.94 Service-Type

The Service-Type AVP is of type Grouped. This AVP shall contain the identities of the service type of the clients that are allowed to locate a target UE for an MT-LR.

AVP format

Service-Type ::= <AVP header: 1483 10415>

{ ServiceTypeIdentity }

[ GMLC-Restriction ]

[ Notification-To-UE-User ]

*[AVP]

7.3.95 ServiceTypeIdentity

The ServiceTypeIdentity AVP is of type Unsigned32. For details on the values of this AVP, see 3GPP TS 29.002 [24].

7.3.96 MO-LR

The MO-LR AVP is of type Grouped. This AVP shall contain the classes of MO-LR for which a subscription exists for a particular UE.

AVP format

MO-LR ::= <AVP header: 1485 10415>

{ SS-Code }

{ SS-Status }

*[AVP]

7.3.97 Void

7.3.98 Trace-Collection-Entity AVP

The Trace-Collection-Entity AVP is of type Address and contains the IPv4 or IPv6 address of the Trace Collection Entity, as defined in 3GPP TS 32.422 [23], clause 5.9.

7.3.99 Teleservice-List

The Teleservice-List AVP is of type Grouped. This AVP shall contain the service codes for the short message related teleservice for a subscriber:

AVP format

Teleservice-List ::= <AVP header: 1486 10415>

1 * { TS-Code }* [ AVP ]

7.3.100 TS-Code

The TS-Code AVP is of type OctetString. Octets are coded according to 3GPP TS 29.002 [24].

7.3.101 Call-Barring-Info

The Call-Barring-Info AVP is of type Grouped. This AVP shall contain the service codes for the short message related call barring services for a subscriber:

AVP format

Call-Barring-Info ::= <AVP header: 1488 10415>

{ SS-Code }

{ SS-Status }

*[ AVP ]

7.3.102 SGSN-Number

The SGSN-Number AVP is of type OctetString and it shall contain the ISDN number of the SGSN. For further details on the definition of this AVP, see 3GPP TS 23.003 [3]. This AVP contains an SGSN-Number in international number format as described in ITU-T Rec E.164 [41] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

7.3.103 IDR-Flags

The IDR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.103/1:

Table 7.3.103/1: IDR-Flags

bit	name	Description
0	UE Reachability Request	This bit when set shall indicate to the MME or the SGSN that the HSS is awaiting a Notification of UE Reachability.
1	T-ADS Data Request	This bit, when set, shall indicate to the MME or SGSN that the HSS requests the support status of "IMS Voice over PS Sessions", and the RAT Type and timestamp of the last radio contact with the UE.
2	EPS User State Request	This bit, when set, shall indicate to the MME or the SGSN that the HSS requests the MME or the SGSN for the current user state.
3	EPS Location Information Request	This bit, when set, shall indicate to the MME or the SGSN that the HSS requests the MME or SGSN for location information
4	Current Location Request	This bit when set shall indicate to the MME or the SGSN that the HSS requests the MME or SGSN to provide the most current location information by paging the UE if the UE is in idle mode. This bit is used only in combination with the"EPS Location Information Request" bit.
5	Local Time Zone Request	This bit when set shall indicate to the MME or the SGSN that the HSS requests the MME or SGSN to provide information on the time zone of the location in the visited network where the UE is attached.
6	Remove SMS Registration	This bit when set shall indicate to the MME that it shall consider itself unregistered for SMS.
7	RAT-Type Requested	This bit when set shall indicate to the MME or the SGSN that the HSS requests the MME or SGSN to provide the RAT Type that corresponds to the requested EPS Location Information. This bit is used only in combination with the"EPS Location Information Request" bit.
8	P-CSCF Restoration Request	This bit, when set, shall indicate to the MME or SGSN that the HSS requests the execution of the HSS-based P-CSCF restoration procedures, as described in 3GPP TS 23.380 [51] clause 5.4.
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

7.3.104 ICS-Indicator

The ICS-Indicator AVP is of type Enumerated. The meaning of the values is defined in 3GPP TS 23.292 [34] and 3GPP TS 23.216 [35]. The following values are defined:

FALSE (0)

TRUE (1)

7.3.105 Visited-Network-Identifier

The Visited-Network-Identifier AVP contains the identity of the network where the PDN-GW was allocated, in the case of dynamic PDN-GW assignment.

The AVP shall be encoded as:

mnc<MNC>.mcc<MCC>.3gppnetwork.org

7.3.106 IMS-Voice-Over-PS-Sessions-Supported

The IMS-Voice-Over-PS-Sessions-Supported AVP is of type Enumerated. The following values are defined:

NOT_SUPPORTED (0)

This value indicates that "IMS Voice over PS Sessions" is not supported by the UE’s most recently used TA or RA in the serving node.

SUPPORTED (1)

This value indicates that "IMS Voice over PS Sessions" is supported by the UE’s most recently used TA or RA in the serving node.

7.3.107 Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions

The Homogeneous-Support-of-IMS-Voice-Over-PS-Sessions AVP is of type Enumerated. The following values are defined:

NOT_SUPPORTED (0)

This value indicates that "IMS Voice over PS Sessions" is not supported, homogeneously, in any of the TAs or RAs associated to the serving node for the served subscribers including consideration on roaming relationship for IMS Voice over PS.

SUPPORTED (1)

This value indicates that "IMS Voice over PS Sessions" is supported, homogeneously, in all of the TAs or RAs associated to the serving node for the served subscriber including consideration on roaming relationship for IMS Voice over PS.

If this AVP is not present in the command, it indicates that there is no homogeneous support of IMS Voice Over PS Sessions on all the TA/RAs of the serving node, or that the homogeneity of this support is unknown to the serving node.

NOTE: In order to ensure the T-ADS by HPLMN, MME or SGSN is expected to either set "Homogenous Support of IMS Voice over PS Sessions" AVP to "NOT_SUPPORTED (0)", or not to set this AVP for inbound roaming subscribers if there is no IMS Voice over PS roaming relationship with the HPLMN.

7.3.108 Last-UE-Activity-Time

The Last-UE-Activity-Time AVP is of type Time (see IETF RFC 6733 [61]), and contains the point of time of the last radio contact of the serving node (MME or SGSN) with the UE.

7.3.109 GMLC-Address

The GMLC-Address AVP is of type Address and shall contain the IPv4 or IPv6 address of the V-GMLC associated with the serving node.

7.3.110 EPS-User-State

The EPS-User-State AVP is of type Grouped. It shall contain the information related to the user state in the MME and/or the SGSN.

AVP format

EPS-User-State ::= <AVP header:1495 10415>

[MME-User-State]

[SGSN-User-State]

*[AVP]

7.3.111 EPS-Location-Information

The EPS-Location Information AVP is of type Grouped. It shall contain the information related to the user location relevant for EPS.

AVP format

EPS-Location-Information ::= <AVP header: 1496 10415>

[MME-Location-Information]

[SGSN-Location-Information]

*[AVP]

7.3.112 MME-User-State

The MME-User-State AVP is of type Grouped. It shall contain the information related to the user state in the MME.

AVP format

MME-User-State ::= <AVP header: 1497 10415>

[User-State]

*[AVP]

7.3.113 SGSN-User-State

The SGSN-User-State AVP is of type Grouped. It shall contain the information related to the user state in the SGSN.

AVP format

SGSN-User-State ::= <AVP header: 1498 10415>

[User-State]

*[AVP]

7.3.114 User-State

The User-State AVP is of type Enumerated and indicates the user state in EPS. The following values are defined:

DETACHED (0)

The UE is in EMM_DEREGISTERED state.

ATTACHED_NOT_REACHABLE_FOR_PAGING (1)

The SGSN has determined from its internal data that the UE is attached to the network, but there is no EPS bearer active, and the UE is not reachable for paging. This value is only applicable to S4-SGSN.

ATTACHED_REACHABLE_FOR_PAGING (2)

The SGSN has determined from its internal data that the UE is attached to the network, but there is no EPS bearer active; the SGSN has not determined from its internal data that the UE is not reachable for paging. This value is only applicable to S4-SGSN.

CONNECTED_NOT_REACHABLE_FOR_PAGING (3)

The SGSN or MME has determined from its internal data that the UE is attached to the network, there is at least one EPS bearer active, and the UE is not reachable for paging.

CONNECTED_REACHABLE_FOR_PAGING (4)

The SGSN or MME has determined from its internal data that the UE is attached to the network, there is at least one EPS bearer active, and the SGSN or MME has not determined from its internal data that the UE is not reachable for paging.

RESERVED (5)

This value should not be used by MME or SGSN over S6a/S6d. If this value is received by the HSS from pre-rel-12 MME/SGSNs, the HSS shall consider that the UE is not reachable and use the "Network determined not reachable" state when reporting the User State to other network entities, e.g. over Sh.

NOTE: The state associated to a "Network determined not reachable" condition should also be used by HSS when reporting to the requesting entity, e.g. over Sh, that the user was found to be not reachable (for instance, if the HSS receives no answer from the MME/SGSN to the user state query).

7.3.115 MME-Location-Information

The MME-Location-Information AVP is of type Grouped. It shall contain the information related to the user location relevant for the MME.

AVP format

MME-Location-Information ::= <AVP header: 1600 10415>

[E-UTRAN-Cell-Global-Identity]

[Tracking-Area-Identity]

[Geographical-Information]

[Geodetic-Information]

[Current-Location-Retrieved]

[Age-Of-Location-Information]

[User-CSG-Information]

[ eNodeB-ID ]

[ Extended-eNodeB-ID ]

*[AVP]

An eNodeB-ID AVP may be present for Monitoring event reporting.

7.3.116 SGSN-Location-Information

The SGSN-Location-Information AVP is of type Grouped. It shall contain the information related to the user location relevant for the SGSN.

AVP format

SGSN-Location-Information ::= <AVP header: 1601 10415>

[Cell-Global-Identity]

[Location-Area-Identity]

[Service-Area-Identity]

[Routing-Area-Identity]

[Geographical-Information]

[Geodetic-Information]

[Current-Location-Retrieved]

[Age-Of-Location-Information]

[ User-CSG-Information]

*[AVP]

7.3.117 E-UTRAN-Cell-Global-Identity

The E-UTRAN-Cell-Global-Identity AVP is of type OctetString and shall contain the E-UTRAN Cell Global Identification of the user which identifies the cell the user equipment is registered, as specified in 3GPP TS 23.003 [3]. Octets are coded as described in 3GPP TS 29.002 [24].

7.3.118 Tracking-Area-Identity

The Tracking-Area-Identity AVP is of type OctetString and shall contain the Tracking Area Identity of the user which identifies the tracking area where the user is located, as specified in 3GPP TS 23.003 [3]. Octets are coded as described in 3GPP TS 29.002 [24].

7.3.119 Cell-Global-Identity

The Cell-Global-Identity AVP is of type OctetString and shall contain the Cell Global Identification of the user which identifies the cell the user equipment is registered, as specified in 3GPP TS 23.003 [3]. Octets are coded as described in 3GPP TS 29.002 [24].

7.3.120 Routing-Area-Identity

The Routing-Area-Identity AVP is of type OctetString and shall contain the Routing Area Identity of the user which identifies the routing area where the user is located, as specified in 3GPP TS 23.003 [3]. Octets are coded as described in 3GPP TS 29.002 [24].

7.3.121 Location-Area-Identity

The Location-Area-Identity AVP is of type OctetString and shall contain the Location Area Identification of the user which identifies the Location area where the user is located, as specified in 3GPP TS 23.003 [3]. Octets are coded as described in 3GPP TS 29.002 [24].

7.3.122 Service-Area-Identity

The Service-Area-Identity AVP is of type OctetString and shall contain the Service Area Identifier of the user where the user is located, as specified in 3GPP TS 23.003 [3]. Octets are coded as described in 3GPP TS 29.002 [24].

7.3.123 Geographical-Information

The Geographical-Information AVP is of type OctetString and shall contain the geographical Information of the user. For details and octet encoding, see 3GPP TS 29.002 [24].

7.3.124 Geodetic-Information

The Geodetic-Information AVP is of type OctetString and shall contain the Geodetic Location of the user. For details and octet encoding, see 3GPP TS 29.002 [24].

7.3.125 Current-Location-Retrieved

The Current-Location-Retrieved AVP is of type Enumerated. The following values are defined:

ACTIVE-LOCATION-RETRIEVAL (0)

This value is used when location information was obtained after a successful paging procedure for Active Location Retrieval when the UE is in idle mode or after retrieving the most up-to-date location information from the eNB when the UE is in connected mode.

7.3.126 Age-Of-Location-Information

The Age-Of-Location-Information AVP is of type Unsigned32 and shall contain the the elapsed time in minutes since the last network contact of the user equipment. For details, see 3GPP TS 29.002 [24].

7.3.127 Active-APN

The Active-APNs AVP is of type Grouped. It shall contain information about a dynamically established APN on a serving node, so the HSS can restore it, if it is eventually lost after a node restart.

The AVP format shall conform to:

Active-APN ::= <AVP header: 1612 10415>

{ Context-Identifier }

[ Service-Selection ]

[ MIP6-Agent-Info ]

[ Visited-Network-Identifier ]

*[ Specific-APN-Info ]

*[ AVP ]

7.3.128 Error-Diagnostic

The Error-Diagnostic AVP is of type Enumerated. The following values are defined:

– GPRS_DATA_SUBSCRIBED (0)

This value shall be used when Experimental-Error is DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION and there is GPRS Subscription Data for the user.

– NO_GPRS_DATA_SUBSCRIBED (1)

This value shall be used when Experimental-Error is DIAMETER_ERROR_UNKNOWN_EPS_SUBSCRIPTION and there is not GPRS Subscription Data for the user.

– ODB_ALL_APN (2)

This value shall be used when Experimental-Error is DIAMETER_ERROR_ROAMING_NOT_ALLOWED and the Operator Determined Barring indicates "All Packet Oriented Services Barred" (see clause 7.3.30).

– ODB_HPLMN_APN (3)

This value shall be used when Experimental-Error is DIAMETER_ERROR_ROAMING_NOT_ALLOWED and the Operator Determined Barring indicates "Roamer Access HPLMN-AP Barred" (see clause 7.3.30).

– ODB_VPLMN_APN (4)

This value shall be used when Experimental-Error is DIAMETER_ERROR_ROAMING_NOT_ALLOWED and the Operator Determined Barring indicates "Roamer Access to VPLMN-AP Barred" (see clause 7.3.30).

7.3.129 Ext-PDP-Address AVP

The Ext-PDP-Address AVP is of type Address and indicates an additional address of the data protocol, and it may be included when the PDP supports dual-stack (IPv4v6).

7.3.130 UE-SRVCC-Capability

The UE-SRVCC-Capability AVP is of type Enumerated. It shall indicate if the UE supports or does not support the SRVCC capability. The following values are defined:

UE-SRVCC-NOT-SUPPORTED (0)

UE-SRVCC-SUPPORTED (1)

7.3.131 MPS-Priority

The MPS-Priority AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.131/1:

Table 7.3.131/1: MPS-Priority

Bit	Name	Description
0	MPS-CS-Priority	This bit, when set, indicates that the UE is subscribed to the eMLPP or 1x RTT priority service in the CS domain.
1	MPS-EPS-Priority	This bit, when set, indicates that the UE is subscribed to the MPS in the EPS domain.
Note: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

NOTE: The HSS derives the information for MPS-CS-Priority from the eMLPP Subscription Data as defined in the 3GPP TS 29.002 [24] or 1x RTT priority service which is out of the scope of 3GPP.

7.3.132 VPLMN-LIPA-Allowed

The VPLMN-LIPA-Allowed AVP is of type Enumerated. It shall indicate whether the UE is allowed to use LIPA in the VPLMN where the UE is roaming. The following values are defined:

LIPA_NOTALLOWED (0)

This value indicates that the UE is not allowed to use LIPA in the VPLMN where the UE is roaming.

LIPA_ALLOWED (1)

This value indicates that the UE is allowed to use LIPA in the VPLMN where the UE is roaming.

7.3.133 LIPA-Permission

The LIPA-Permission AVP is of type Enumerated. It shall indicate whether the APN can be accessed via Local IP Access. The following values are defined:

LIPA_PROHIBITED (0)

This value indicates that this APN is prohibited to be accessed via LIPA.

LIPA_ONLY (1)

This value indicates that this APN can be accessed only via LIPA.

LIPA_CONDITIONAL (2)

This value indicates that this APN can be accessed via both non LIPA and LIPA.

7.3.134 Subscribed-Periodic-RAU-TAU-Timer

The Subscribed-Periodic-RAU-TAU-Timer AVP is of type Unsigned32 and it shall contain the subscribed periodic RAU/TAU timer value in seconds as specified in 3GPP TS 24.008 [31].

7.3.135 SIPTO-Permission

The SIPTO-Permission AVP is of type Enumerated. It shall indicate whether the traffic associated with this particular APN is allowed or not for SIPTO above RAN.

The following values are defined:

SIPTO_above_RAN _ALLOWED (0)

SIPTO_above_RAN _NOTALLOWED (1)

7.3.136 MDT-Configuration

The MDT-Configuration AVP is of type Grouped. It shall contain MDT related information as specified in 3GPP TS 32.422 [23].

The AVP format shall conform to:

MDT-Configuration ::= <AVP header: 1622 10415>

{ Job-Type }

[ Area-Scope ]

[ List-Of-Measurements ]

[ Reporting-Trigger ]

[ Report-Interval ]

[ Report-Amount ]

[ Event-Threshold-RSRP ]

[ Event-Threshold-RSRQ ]

[ Logging-Interval ]

[ Logging-Duration ]

[ Measurement-Period-LTE ]

[ Measurement-Period-UMTS ]

[ Collection-Period- RRM-LTE ]

[ Collection-Period-RRM-UMTS ]

[ Positioning-Method ]

[ Measurement-Quantity]

[ Event-Threshold-Event-1F ]

[ Event-Threshold-Event-1I ]

*[ MDT-Allowed-PLMN-Id ]

*[ MBSFN-Area ]

*[ AVP ]

7.3.137 Job-Type

The Job-Type AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Job-Type.

7.3.138 Area-Scope

The Area-Scope AVP is of type Grouped. See 3GPP TS 32.422 [23].

The AVP format shall conform to:

Area-Scope ::= <AVP header: 1623 10415>

*[ Cell-Global-Identity ]

*[ E-UTRAN-Cell-Global-Identity ]

*[ Routing-Area-Identity ]

*[ Location-Area-Identity ]

*[ Tracking-Area-Identity ]

*[ AVP ]

7.3.139 List-Of-Measurements

The List-Of-Measurements AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in 3GPP TS 32.422 [23]. The most significant bit is bit 8 of the first octet.

7.3.140 Reporting-Trigger

The Reporting-Trigger AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits is defined in 3GPP TS 32.422 [23]. The most significant bit is bit 8 of the first octet.

7.3.141 Report-Interval

The Report-Interval AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Report Interval

7.3.142 Report-Amount

The Report-Amount AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Report Amount.

7.3.143 Event-Threshold-RSRP

The Event-Threshold-RSRP AVP is of type Unsigned32. See 3GPP TS 32.422 [23] for allowed values

7.3.144 Event-Threshold-RSRQ

The Event-Threshold-RSRQ AVP is of type Unsigned32. See 3GPP TS 32.422 [23] for allowed values

7.3.145 Logging-Interval

The Logging-Interval AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Logging Interval

7.3.146 Logging-Duration

The Logging-Duration AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Logging Duration

7.3.147 Relay-Node-Indicator

The Relay-Node-Indicator AVP is of type Enumerated. It shall indicate whether the subscription data belongs to a Relay Node or not (see 3GPP TS 36.300 [40]). The following values are defined:

NOT_RELAY_NODE (0)

This value indicates that the subscription data does not belong to a Relay Node.

RELAY_NODE (1)

This value indicates that the subscription data belongs to a Relay Node.

The default value when this AVP is not present is NOT_RELAY_NODE (0).

7.3.148 MDT-User-Consent

The MDT-User-Consent AVP is of type Enumerated. It shall indicate whether the user has given his consent for MDT activation or not (see 3GPP TS 32.422 [23]). The following values are defined:

CONSENT_NOT_GIVEN (0)

CONSENT_GIVEN (1)

The default value when this AVP is not present in ULA is CONSENT_NOT_GIVEN (0). Absence of this AVP in IDR shall be interpreted as the MDT-User-Consent has not been modified.

The presence of this subscription parameter in ULA or IDR shall be independent of the support of the Trace Function by the MME/SGSN (see clause 7.3.10).

7.3.149 PUR-Flags

The PUR-Flags AVP is of type Unsigned32 and it shall contain a bitmask. The meaning of the bits is defined in table 7.3.149/1:

Table 7.3.149/1: PUR-Flags

bit	name	Description
0	UE Purged in MME	This bit, when set, indicates that the combined MME/SGSN has purged the UE in the MME part of the node. This bit shall not be set by a standalone SGSN.
1	UE Purged in SGSN	This bit, when set, shall indicate that the combined MME/SGSN has purged the UE in the SGSN part of the node. This bit shall not be set by a standalone MME.
NOTE: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS.

7.3.150 Subscribed-VSRVCC

The Subscribed-VSRVCC AVP is of type Enumerated. It shall indicate that the user is subscribed to the vSRVCC. The following value is defined:

VSRVCC_SUBSCRIBED (0)

Absence of this AVP in IDR shall be interpreted as the Subscribed-VSRVCC has not been modified.

Absence of this AVP in ULA shall be interpreted as the user is not subscribed to the vSRVCC.

7.3.151 Equivalent-PLMN-List

The Equivalent-PLMN-List AVP is of type Grouped. This AVP shall contain the equivalent PLMN IDs of the registered PLMN (i.e. the visited PLMN) of the MME or the SGSN.

AVP format

Equivalent-PLMN-List ::= <AVP header: 1637 10415>

1*{ Visited-PLMN-Id }

*[AVP]

7.3.152 CLR-Flags

The CLR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.152/1:

Table 7.3.152/1: CLR-Flags

Bit	Name	Description
0	S6a/S6d-Indicator (Note 1)	This bit, when set, indicates that the CLR message is sent on the S6a interface, i.e. the message is to the MME or the MME part on the combined MME/SGSN. This bit, when cleared, indicates that the CLR message is sent on the S6d interface, i.e. the message is to the SGSN or the SGSN part on the combined MME/SGSN.
1	Reattach-Required	This bit, when set, indicates that the MME or SGSN shall request the UE to initiate an immediate re-attach procedure as described in 3GPP TS 23.401 [2] and in 3GPP TS 23.060 [12].
NOTE 1: The S6a/S6d-Indicator flag shall be used during initial attach procedure for a combined MME/SGSN. The S6a/S6d-Indicator flag may also be sent to a standalone node. NOTE 2: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN. NOTE 3: For the purpose of withdrawing "Aerial UE Subscription", HSS may send CLR with CLR-Flag set to Reattach-Required.

7.3.153 UVR-Flags

The UVR-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.154/1:

Table 7.3.154/1: UVR-Flags

Bit	Name	Description
0	Skip Subscriber Data	This bit, when set, indicates that the CSS may skip subscription data in UVA. If the CSG subscription data has changed in the CSS after the last successful update of the MME/SGSN, the CSS shall ignore this bit and send the updated CSG subscription data.
Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving CSS.

7.3.154 UVA-Flags

The UVA-Flags AVP is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.156/1:

Table 7.3.156/1: UVA-Flags

Bit	Name	Description
0	Temporary Empty VPLMN CSG Subscription Data	This bit, when set, indicates that the CSS has currently no VPLMN CSG subscription data for this user but has registered the MME or SGSN, so to inform them if later changes in VPLMN CSG subscription data occur.
Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving CSS.

7.3.155 VPLMN-CSG-Subscription-Data

The VPLMN-CSG-Subscription-Data AVP is of type Grouped. This AVP shall contain the CSG-Id, and optionally an associated expiration date.

AVP format

VPLMN-CSG-Subscription-Data ::= <AVP header: 1641 10415>

{ CSG-Id }

[ Expiration-Date ]

*[AVP]

7.3.156 Local-Time-Zone

The Local-Time-Zone AVP is of type Grouped and shall contain the Time Zone and the Daylight Saving Time (DST) adjustment of the location in the visited network where the UE is attached.

The AVP format shall conform to:

Local-Time-Zone ::= <AVP header: 1649 10415>

{ Time-Zone }

{ Daylight-Saving-Time }

* [ AVP ]

7.3.157 A-MSISDN

The A-MSISDN AVP is of type OctetString. See 3GPP TS 23.003 [3] for the definition of the Additional MSISDN. This AVP contains an A-MSISDN, in international number format as described in ITU-T Rec E.164 [41], encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

This AVP may be present in the Subscription-Data AVP when sent within ULA.

It may also be present in the Subscription-Data AVP, sent within an IDR, if the current value in the MME or SGSN needs to be changed.

7.3.158 Void

7.3.159 MME-Number-for-MT-SMS

The MME-Number-for-MT-SMS AVP is of type OctetString and it shall contain the ISDN number corresponding to the MME for MT SMS. For further details on the definition of this AVP, see 3GPP TS 23.003 [3]. This AVP contains an international number with the format as described in ITU-T Rec E.164 [41] and shall be encoded as a TBCD-string. See 3GPP TS 29.002 [24] for encoding of TBCD-strings. This AVP shall not include leading indicators for the nature of address and the numbering plan; it shall contain only the TBCD-encoded digits of the address.

7.3.160 Void

7.3.161 Void

7.3.162 SMS-Register-Request

The SMS-Register-Request AVP is of type Enumerated and it shall indicate whether the MME or the SGSN requires to be registered for SMS (e.g. SGs interface not supported) or if the MME or the SGSN prefers not to be registered for SMS or if the MME or the SGSN has no preference.

The following values are defined:

SMS_REGISTRATION_REQUIRED (0)

SMS_REGISTRATION_NOT_PREFERRED (1)

NO_PREFERENCE (2)

The criteria for setting these values are defined in 3GPP TS 23.272 [44] and 3GPP TS 23.060 [12].

7.3.163 Time-Zone

The Time-Zone AVP is of type UTF8String and shall contain the time zone of the location in the visited network where the UE is attached.

It contains the offset from UTC (Coordinated Universal Time) in units of 15 minutes, as defined in 3GPP TS 22.042 [42]. It shall be expressed as positive (i.e. with the leading plus sign [+]) if the local time is ahead of or equal to UTC of day and as negative (i.e. with the leading minus sign [-]) if it is behind UTC of day.

The value contained in the Time-Zone AVP shall take into account daylight saving time, such that when the sending entity changes from regular (winter) time to daylight saving (summer) time, there is a change to the value in the Time-Zone AVP.

The contents of the Time-Zone AVP shall be formatted as a character string with the following format:

Basic format: ±n, with "n" being the number of units of 15 minutes from UTC.

For example, if the offset is +2h=+8x15mn, the value of the Time-Zone AVP will be: "+8".

7.3.164 Daylight-Saving-Time

The Daylight-Saving-Time AVP is of type Enumerated and shall contain the Daylight Saving Time (in steps of 1 hour) used to adjust for summertime the time zone of the location where the UE is attached in the visited network.

The following values are defined:

NO_ADJUSTMENT (0)

PLUS_ONE_HOUR_ADJUSTMENT (1)

PLUS_TWO_HOURS_ADJUSTMENT (2)

7.3.165 Subscription-Data-Flags

The Subscription-Data-Flags is of type Unsigned32 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.165/1:

Table 7.3.165/1: Subscription-Data-Flags

Bit	Name	Description
0	PS-And-SMS-Only-Service-Provision-Indication	This bit, when set, indicates that the subscription is for PS Only and permits CS service access only for SMS.
1	SMS-In-SGSN-Allowed-Indication	This bit, when set, indicates that SMS in SGSN for the user is allowed.
2	User Plane Integrity Protection	This bit, when set, indicates that the SGSN may decide to activate integrity protection of the user plane when GERAN is used (see 3GPP TS 43.020 [58]). The MME shall ignore it.
3	PDN-Connection-Restricted	This bit, when set, indicates to the MME that it shall not establish any non-emergency PDN connection for this user if the MME and the UE supports Attach without PDN connection. The SGSN shall ignore it.
4	Acknowledgement-Of-Downlink-NAS-Data PDUs disabled	This bit, when set, indicates to the MME that acknowledgement of downlink NAS data PDUs for Control Plane CIoT Optimization is disabled for this UE (even for APN configurations with RDS Indicator set to ENABLED (1)). When not set it indicated to the MME that acknowledgement of downlink NAS data PDUs for Control Plane CIoT Optimization is enabled (for APN configurations with RDS Indicator set to ENABLED (1)) for this UE, which is the default (see 3GPP TS 23.401 [2]). The SGSN shall ignore it.
NOTE: Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command.

7.3.166 Measurement-Period-LTE

The Measurement-Period-LTE AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Measurement period LTE.

7.3.167 Measurement-Period-UMTS

The Measurement-Period-UMTS AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Measurement period UMTS.

7.3.168 Collection-Period-RRM-LTE

The Collection-Period-RRM-LTE AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Collection period for RRM measurements LTE.

7.3.169 Collection-Period-RRM-UMTS

The Collection-Period-RRM-UMTS AVP is of type Enumerated. The possible values are those defined in 3GPP TS 32.422 [23] for Collection period for RRM measurements UMTS.

7.3.170 Positioning-Method

The Positioning-Method AVP is of type OctetString. It contains one octet carrying a bit map of 8 bits. The possible values are those defined in 3GPP TS 32.422 [23] for Positioning Method.

7.3.171 Measurement-Quantity

The Measurement-Quantity AVP is of type OctetString. It contains one octet carrying a bit map of 8 bits. The possible values are those defined in 3GPP TS 32.422 [23] for Measurement quantity.

7.3.172 Event-Threshold-Event-1F

The Event-Threshold-Event-1F AVP is of type Integer32. See 3GPP TS 32.422 [23] for allowed values.

7.3.173 Event-Threshold-Event-1I

The Event-Threshold-Event-1I AVP is of type Integer32. See 3GPP TS 32.422 [23] for allowed values

7.3.174 Restoration-Priority

The Restoration-Priority AVP is of type Unsigned32. It shall indicate the relative priority of a user’s PDN connection among PDN connections to the same APN when restoring PDN connections affected by an SGW or PGW failure/restart (see 3GPP TS 23.007 [43]).

Values 1 to 16 are defined, with value 1 as the highest level of priority.

7.3.175 SGs-MME-Identity

The SGs-MME-Identity AVP is of type UTF8String. This AVP shall contain the MME identity used over the SGs interface and specified in 3GPP TS 23.003 [3] clause 19.4.2.4.

7.3.176 SIPTO-Local-Network-Permission

The SIPTO-Local-Network-Permission AVP is of type Unsigned32. It shall indicate whether the traffic associated with this particular APN is allowed or not for SIPTO at the local network.

The following values are defined:

"SIPTO at Local Network ALLOWED" 0

"SIPTO at Local Network NOTALLOWED" 1

7.3.177 Coupled-Node-Diameter-ID

The Coupled-Node-Diameter-ID AVP is of type DiameterIdentity. This AVP shall contain the S6a or S6d Diameter identity of the coupled node as specified in 3GPP TS 23.003 [3] clause 19.4.2.4 and clause 19.4.2.6.

7.3.178 OC-Supported-Features

The OC-Supported-Features AVP is of type Grouped and it is defined in IETF RFC 7683 [50]. This AVP is used to support Diameter overload control mechanism, see Annex C for more information.

7.3.179 OC-OLR

The OC-OLR AVP is of type Grouped and it is defined in IETF RFC 7683 [50]. This AVP is used to support Diameter overload control mechanism, see Annex C for more information.

7.3.180 ProSe-Subscription-Data

The ProSe-Subscription-Data AVP is of type Grouped. It shall contain the ProSe related subscription data. It was originally defined in 3GPP TS 29.344 [49].

AVP format

ProSe-Subscription-Data ::= <AVP header: 3701 10415>

{ ProSe-Permission }

*[AVP]

7.3.181 WLAN-offloadability

The WLAN-offloadability AVP is of type Grouped. This AVP contains WLAN offloadability for E-UTRAN or UTRAN.

AVP format:

WLAN-offloadability ::= <AVP header: 1667>

[ WLAN-offloadability-EUTRAN ]

[ WLAN-offloadability-UTRAN ]

*[ AVP ]

7.3.182 WLAN-offloadability-EUTRAN

The WLAN-offloadability-EUTRAN AVP is of type Unsigned32 and it shall contain a bitmask. The meaning of the bits is defined in table 7.3.182/1:

Table 7.3.182/1: WLAN-offloadability-EUTRAN

bit	name	Description
0	WLAN offloadability for E-UTRAN	This bit, when set, shall indicate that the traffic associated with the APN is allowed to be offloaded to WLAN from E-UTRAN using the WLAN/3GPP Radio Interworking feature. If not set, it means the traffic associated with the APN is not allowed to be offloaded to WLAN from E-UTRAN.
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

7.3.183 WLAN-offloadability-UTRAN

The WLAN-offloadability-UTRAN AVP is of type Unsigned32 and it shall contain a bitmask. The meaning of the bits is defined in table 7.3.183/1:

Table 7.3.183/1: WLAN-offloadability-UTRAN

bit	name	Description
0	WLAN offloadability for UTRAN	This bit, when set, shall indicate that the traffic associated with the APN is allowed to be offloaded to WLAN from UTRAN using the WLAN/3GPP Radio Interworking feature. If not set, it means the traffic associated with the APN is not allowed to be offloaded to WLAN from UTRAN.
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN..

7.3.184 Reset-ID

The Reset-ID is of type OctetString. The value shall uniquely (within the HSS’s realm) identify a resource in the HSS that may fail or has restarted.

In the Reset procedure, when used to add/modify/delete subscription data shared by multiple subscribers, the Reset-ID is used to identify the set of affected subscribers.

7.3.185 MDT-Allowed-PLMN-Id

The MDT-Allowed-PLMN-Id AVP is of type OctetString. This AVP shall contain the concatenation of MCC and MNC. See 3GPP TS 23.003 [3]. The content of this AVP shall be encoded as an octet string according to table 7.3.185/1.

This AVP identifies the PLMN in which the MDT data collection shall take place.

See 3GPP TS 24.008 [31], clause 10.5.1.13, PLMN list, for the coding of MCC and MNC. If MNC is 2 digits long, bits 5 to 8 of octet 2 are coded as "1111".

Table 7.3.185/1: Encoding format for MDT-Allowed-PLMN-Id AVP

8	7	6	5	4	3	2	1
MCC digit 2				MCC digit 1				octet 1
MNC digit 3				MCC digit 3				octet 2
MNC digit 2				MNC digit 1				octet 3

7.3.186 Adjacent-PLMNs

The Adjacent-PLMNs AVP is of type Grouped. This AVP shall contain a list of PLMN IDs where an UE served by the MME/SGSN is likely to make a handover from the PLMN where the MME/SGSN is located.

AVP format:

Adjacent-PLMNs ::= <AVP header: 1672 10415>

1*{ Visited-PLMN-Id }

*[AVP]

7.3.187 Adjacent-Access-Restriction-Data

The Adjacent-Access-Restriction-Data AVP is of type Grouped. This AVP shall contain a pair of PLMN ID and the associated Access Restriction Data for that PLMN.

AVP format:

Adjacent-Access-Restriction-Data ::= <AVP header: 1673 10415>

{ Visited-PLMN-Id }

{ Access-Restriction-Data }

*[AVP]

7.3.188 DL-Buffering-Suggested-Packet-Count

The DL-Buffering-Suggested-Packet-Count AVP is of type Integer32. It shall indicate whether extended buffering of downlink packets at the SGW, for High Latency Communication, is requested or not. When requested, it may also suggest the number of downlink packets to buffer at the SGW for this user.

The following values are defined:

"Extended DL Data Buffering NOT REQUESTED" 0

"Extended DL Data Buffering REQUESTED, without a suggested number of packets" -1

"Extended DL Data Buffering REQUESTED, with a suggested number of packets" > 0

"Extended DL Data Buffering REQUESTED", with or without a suggested number of packets to be buffered for this user, indicates that extended buffering of downlink packets at the SGW is applicable to this user.

"Extended DL Data Buffering NOT REQUESTED" indicates that extended buffering of downlink packets at the SGW is not applicable to this user.

7.3.189 IMSI-Group-Id

The IMSI-Group-Id AVP shall be of type Grouped. This AVP shall contain the information about the IMSI-Group-Id.

AVP format

IMSI-Group-Id ::= <AVP header: 1675 10415>

{ Group-Service-Id }

{ Group-PLMN-Id }

{ Local-Group-Id }

*[AVP]

For details see 3GPP TS 23.003 [3], clause 19.9).

7.3.190 Group-Service-Id

The Group-Service-Id AVP is of type Unsigned32 and it shall identify the specific service for which the IMSI-Group-Id is used. The following values are defined:

Table 7.3.190-1: Group-Service-Id

Value	Description
1	Group specific NAS level congestion control
2	Group specific Monitoring of Number of UEs present in a geographical area

Values greater than 1000 are reserved for home operator specific use. IMSI-Group-IDs with a Group-Service-Id in this range shall not be sent outside the HPLMN unless roaming agreements allow so.

7.3.191 Group-PLMN-Id

The Group-PLMN-Id AVP is of type OctetString. This AVP shall contain the concatenation of MCC and MNC. See 3GPP TS 23.003 [3]. The content of this AVP shall be encoded as an octet string according to table 7.3.191-1.

See 3GPP TS 24.008 [31], clause 10.5.1.13, PLMN list, for the coding of MCC and MNC. If MNC is 2 digits long, bits 5 to 8 of octet 2 are coded as "1111".

Table 7.3.191-1: Encoding format for Group-PLMN-Id AVP

8	7	6	5	4	3	2	1
MCC digit 2				MCC digit 1				octet 1
MNC digit 3				MCC digit 3				octet 2
MNC digit 2				MNC digit 1				octet 3

7.3.192 Local-Group-Id

The Local-Group-Id AVP is of type OctetString. It shall contain an operator defined value, representing a group.

7.3.193 AESE-Communication-Pattern

AESE-Communication-Pattern AVP is of type Grouped and is defined in 3GPP TS 29.336 [54].

AVP format

AESE-Communication-Pattern ::= <AVP header: 3113 10415>

[ SCEF-Reference-ID ]

[ SCEF-Reference-ID-Ext ]

{ SCEF-ID }

*[ SCEF-Reference-ID-for-Deletion ]

*[ SCEF-Reference-ID-for-Deletion-Ext ]

*[ Communication-Pattern-Set ]

[ MTC-Provider-Info ]

*[AVP]

At least one reference ID (either in SCEF-Reference-ID or in SCEF-Reference-ID-Ext) or a reference ID for deletion (either in SCEF-Reference-ID-for-Deletion or in SCEF-Reference-ID-for-Deletion-Ext) shall be present.

When the "Extended Reference IDs" feature is supported by the HSS and MME/SGSN, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used insted of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively.

7.3.194 Communication-Pattern-Set

Communication-Pattern-Set AVP is of type Grouped and is defined in 3GPP TS 29.336 [54].

AVP format

Communication-Pattern-Set ::= <AVP header: 3114 10415>

[ Periodic-Communication-Indicator ]

[ Communication-Duration-Time ]

[ Periodic-Time ]

*[ Scheduled-Communication-Time ]

[ Stationary-Indication ]

[ Reference-ID-Validity-Time ]

[ Traffic-Profile ]

[ Battery-Indicator ]

*[AVP]

If the Reference-ID-Validity-Time AVP is absent, it indicates that there is no expiration time defined for the Communication-Pattern-Set.

7.3.195 Monitoring-Event-Configuration

The Monitoring-Event-Configuration AVP is of type Grouped. It shall contain the Monitoring event configuration related subscription data. It is originally defined in 3GPP TS 29.336 [54].

For S6a/S6d interface, the Monitoring-Event-Configuration AVP format is specified as following:

AVP format:

Monitoring-Event-Configuration ::= <AVP header: 3122 10415>

[ SCEF-Reference-ID ]

[ SCEF-Reference-ID-Ext ]

{ SCEF-ID }

{ Monitoring-Type }

*[ SCEF-Reference-ID-for-Deletion ]

*[ SCEF-Reference-ID-for-Deletion-Ext ]

[ Maximum-Number-of-Reports ]

[ Monitoring-Duration ]

[ Charged-Party ]

[ UE-Reachability-Configuration ]

[ Location-Information-Configuration ]

[ SCEF-Realm ]

[ External-Identifier ]

[ MTC-Provider-Info ]

[ PDN-Connectivity-Status-Configuration ]

*[ AVP ]

When the Monitoring-Event-Configuration AVP is used over the S6a/S6d interfaces, the SCEF-Realm AVP shall be present and its value shall be obtained by the HSS from the Origin-Realm AVP of the Configuration-Information-Request command conveying the corresponding monitoring event configuration over the S6t interface from the SCEF to the HSS.

The Monitoring-Type AVP shall only be taken into account in combination with SCEF-Reference-ID/SCEF-Reference-ID-Ext AVP; Monitoring-Type AVP shall be ignored for deletion of an event (i.e. when SCEF-Reference-ID-for-Deletion/SCEF-Reference-ID-for-Deletion-Ext AVP is present).

Maximum-Number-of-Reports shall not be present over S6a/S6d interfaces if Monitoring-Type is AVAILABILITY_AFTER_DDN_FAILURE (6).

Maximum-Number-of-Reports shall not be greater than one over S6a/S6d interfaces if Monitoring-Type is LOCATION_REPORTING (2) and MONTE-Location-Type is LAST_KNOWN_LOCATION (1).

When multiple External Identifiers are defined for the same subscription, the External-Identifier in this grouped AVP, if present, shall contain the specific External Identifier to be associated with this monitoring event; if it is not present, the External Identifier associated with this monitoring event shall be the default External Identifier defined in the subscription (see clause 7.3.2).

When the "Extended Reference IDs" feature is supported by the HSS and MME/SGSN, the SCEF-Reference-ID-Ext and SCEF-Reference-ID-for-Deletion-Ext AVPs shall be used insted of SCEF-Reference-ID and SCEF-Reference-ID-for-Deletion respectively.

7.3.196 Monitoring-Event-Report

The Monitoring-Event-Report AVP is of type Grouped. It shall contain the Monitoring event report data. It is originally defined in 3GPP TS 29.336 [54].

For S6a/S6d interface, the Monitoring-Event-Report AVP format is specified as following:

AVP format:

Monitoring Event Report::= <AVP header: 3123 10415>

{ SCEF-Reference-ID }

[ SCEF-Reference-ID-Ext ]

[ SCEF-ID ]

[ Reachability-Information ]

[ EPS-Location-Information ]

[ Monitoring-Type ]

[ Loss-Of-Connectivity-Reason ]

[ Idle-Status-Indication ]

[ Maximum-UE-Availability-Time ]

*[ PDN-Connectivity-Status-Report ]

*[ AVP ]

For S6a/S6d interface, when the Monitoring-Type AVP takes the value UE_REACHABILITY (1), the Reachability-Information AVP shall take the value REACHABLE_FOR_DATA (1).

For S6a/S6d interface, when the Monitoring-Type AVP takes the value PDN_CONNECTIVITY_STATUS (10), the PDN-Connectivity-Status-Report AVP(s) shall contain the list of active PDNs, for the given APN provided in the monitoring event configuration, or for all APNs if no APN was provided; each PDN-Connectivity-Status-Report shall have the PDN-Connectivity-Status-Type set to value "CREATED (0)".

When the "Extended Reference IDs" feature is supported by the HSS and MME/SGSN, the SCEF-Reference-ID-Ext AVP shall be used insted of SCEF-Reference-ID; in such case, the required AVP "SCEF-Reference-ID" shall be included in the grouped AVP by the sender, but its content shall be discarded by the receiver.

7.3.197 UE-Reachability-Configuration

The UE-Reachability-Configuration AVP is of type Grouped, and it shall contain the details for configuration for UE reachability. It is originally defined in 3GPP TS 29.336 [54].

For S6a/S6d interface, the UE-Reachability-Configuration AVP format is specified as following:

AVP format:

UE-Reachability-Configuration::= <AVP header: 3129 10415>

[ Reachability-Type ]

[ Maximum-Response-Time ]

*[ AVP ]

NOTE: When a Maximum-Response-Time value is not received from the SCEF, the HSS can send an O&M configured desired active time value within the Maximum-Response-Time AVP.

For S6a/S6d interface, the Reachability-Type AVP shall have bit 0 ("Reachability for SMS") cleared, and it shall have bit 1 ("Reachability for Data") set.

7.3.198 eNodeB-ID

The eNodeB-ID AVP is of type OctetString, and indicates the eNodeB in which the UE is currently located. It is originally defined in 3GPP TS 29.217 [56].

7.3.199 Supported-Services

The Supported-Services AVP is of type Grouped and it shall contain the different bit masks representing the services supported by the MME/SGSN:

AVP format

Supported-Services::= <AVP header: 3143 10415>

[ Supported-Monitoring-Events ]

*[AVP]

7.3.200 Supported-Monitoring-Events

The Supported-Monitoring-Events AVP is of type Unsigned64 and it shall contain a bit mask. The meaning of the bits shall be as defined in table 7.3.200-1:

Table 7.3.200 -1: Supported-Monitoring-Events

Bit	Name	Description
0	UE and UICC and/or new IMSI-IMEI-SV association	only used on S6t interface
1	UE-reachability	This bit shall be set if UE reachability Monitoring event is supported in the MME/SGSN
2	Location-of-the-UE	This bit shall be set if Location of the UE and change in location of the UE Monitoring event is supported in the MME/SGSN
3	Loss-of-connectivity	This bit shall be set if Loss of connectivity Monitoring event is supported in the MME/SGSN
4	Communication-failure	This bit shall be set if Communication failure Monitoring event is supported in the MME/SGSN
5	Roaming-status	only used on S6t interface
6	Availability after DDN failure	This bit shall be set if Availability after DDN failure Monitoring event is supported in the MME/SGSN
7	Idle Status Indication	This bit shall be set if Idle Status Indication reporting is supported in the MME/SGSN
8	PDN Connectivity Status	This bit shall be set if PDN Connectivity Status monitoring event is supported in the MME/SGSN
NOTE: Bits not defined in this table shall be cleared by the sender and discarded by the receiver of the command.

7.3.201 AIR-Flags

The AIR-Flags AVP is of type Unsigned32 and it shall contain a bitmask. The meaning of the bits is defined in table 7.3.201/1:

Table 7.3.201/1: AIR-Flags

bit	name	Description
0	Send UE Usage Type	This bit, when set, indicates that the MME or SGSN requests the HSS to send the subscription parameter "UE Usage Type".
NOTE: Bits not defined in this table shall be cleared by the sending MME or SGSN and discarded by the receiving HSS.

7.3.202 UE-Usage-Type

The UE-Usage-Type AVP is of type Unsigned32. This value shall indicate the usage characteristics of the UE that enables the selection of a specific Dedicated Core Network (DCN). See clause 4.3.25 of 3GPP TS 23.401 [2].

The allowed values of UE-Usage-Type shall be in the range of 0 to 255.

Values in the range of 0 to 127 are standardized and defined as follows:

0: Spare, for future use

…

127: Spare, for future use

Values in the range of 128 to 255 are operator-specific.

7.3.203 DRMP

The DRMP AVP is of type Enumerated and it is defined in IETF RFC 7944 [57]. This AVP allows the HSS, the CSS, the EIR and the MME/SGSN to indicate the relative priority of Diameter messages. The DRMP AVP may be used to set the DSCP marking for transport of the associated Diameter message.

7.3.204 Non-IP-PDN-Type-Indicator

The Non-IP-PDN-Type-Indicator AVP is of type Enumerated and indicates whether the APN has a Non-IP PDN type.

The following values are defined:

FALSE (0)

This value indicates that the APN does not have a Non-IP PDN type.

TRUE (1)

This value indicates that the APN has a Non-IP PDN type and, in this case, the value indicated by the PDN-Type AVP inside APN-Configuration AVP shall be ignored.

The default value when this AVP is not present is FALSE (0).

7.3.205 Non-IP-Data-Delivery-Mechanism

The Non-IP-Data-Delivery-Mechanism AVP is of type Unsigned32 and indicates the mechanism to be used for Non-IP data delivery for a given APN. The following values are defined:

SGi-BASED-DATA-DELIVERY (0)

This value indicates that the Non-IP data is delivered via Point-To-Point tunnelling over the SGi interface.

SCEF-BASED-DATA-DELIVERY (1)

This value indicates that the Non-IP data is delivered via the SCEF.

The default value when this AVP is not present is SGi-BASED-DATA-DELIVERY (0).

7.3.206 Additional-Context-Identifier

The Additional-Context-Identifier AVP is of type Unsigned32 and indicates the identity of another default APN to be used when the subscription profile of the user contains APNs with more than one PDN type among IP-based PDN types, non-IP PDN types and Ethernet PDN types.

7.3.207 SCEF-Realm

The SCEF-Realm AVP is of type DiameterIdentity and it shall contain the Diameter realm of the SCEF. For further details on the encoding of this AVP, see IETF RFC 6733 [61].

7.3.208 Subscription-Data-Deletion

The Subscription-Data-Deletion AVP is of type Grouped and indicates the shared subscription data that need to be deleted from the subscription profiles of the impacted subscribers.

AVP format

Subscription-Data-Deletion ::= <AVP header: 1685 10415>

{ DSR-Flags }

[ SCEF-ID ]

*[ Context-Identifier ]

[ Trace-Reference ]

*[ TS-Code ]

*[ SS-Code ]

*[ AVP ]

7.3.209 Preferred-Data-Mode

The Preferred-Data-Mode AVP is of type Unsigned32 and it shall contain a bitmask. The meaning of the bits is defined in table 7.3.209/1:

Table 7.3.209/1: Preferred-Data-Mode

bit	name	Description
0	Data over User Plane Preferred	This bit, when set, shall indicate that the User Plane is preferred for transmitting the traffic associated with the APN. If not set, it means that the User Plane is not preferred for transmitting the traffic associated with the APN.
1	Data over Control Plane Preferred	This bit, when set, shall indicate that the Control Plane is preferred for transmitting the traffic associated with the APN. If not set, it means that the Control Plane is not preferred for transmitting the traffic associated with the APN.
NOTE 1: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME. NOTE 2: At least one of the bits 0 and 1 shall be set to 1. Both bits 0 and 1 may be set to 1 to indicate that both User Plane and Control Plane are preferred for transmitting the traffic associated with the APN. NOTE 3: This parameter only applies to E-UTRAN and SGi PDN connections. Data over User Plane refers to PDN data transported over S1-U and Data Radio Bearer. Data over Control Plane refers to PDN data transported over NAS and Signalling Radio Bearer.

7.3.210 Emergency-Info

The Emergency-Info AVP is of type Grouped. It shall contain the identity of the PDN-GW used for the establishment of emergency PDN connections.

The AVP format shall conform to:

Emergency-Info ::= <AVP header: 1687 10415>

[ MIP6-Agent-Info ]

*[ AVP ]

7.3.211 Load

The Load AVP is of type Grouped and it is defined in IETF RFC 8583 [60]. This AVP is used to support Diameter load control mechanism, see Annex F for more information.

7.3.212 V2X-Subscription-Data

The V2X-Subscription-Data AVP is of type Grouped. It shall contain the V2X related subscription data for the network scheduled LTE sidelink communication..

AVP format:

V2X-Subscription-Data ::= <AVP header: 1688 10415>

[ V2X-Permission ]

[ UE-PC5-AMBR ]

*[AVP]

The UE-PC5-AMBR AVP within the V2X-Subscription-Data AVP indicates the UE AMBR used for LTE PC5 interface.

7.3.213 V2X-Permission

The V2X-Permission AVP is of type Unsigned32 and it shall contain a bit mask that indicates the permissions for V2X service subscribed by the user. The meaning of the bits shall be as defined in table 7.3.x2-1:

Table 7.3.x2-1: V2X-Permission

Bit	Name	Description
0	Allow V2X communication over PC5 as Vehicle UE	This bit, when set, indicates that the user is allowed to use V2X communication over PC5 as Vehicle UE in the serving PLMN.
1	Allow V2X communication over PC5 as Pedestrian UE	This bit, when set, indicates that the user is allowed to use V2X communication over PC5 as Pedestrian UE in the serving PLMN.
NOTE: Bits not defined in this table shall be cleared by the HSS and discarded by the MME.

7.3.214 PDN-Connection-Continuity

The PDN-Connection-Continuity AVP is of type Unsigned32 and indicates how to handle the PDN connection when the UE moves between "broadband" (WB-E-UTRAN, UTRAN) and "narrowband" (NB-IoT, GPRS, EC-GSM-IoT). The following values are defined:

MAINTAIN-PDN-CONNECTION (0)

DISCONNECT-PDN-CONNECTION-WITH-REACTIVATION-REQUEST (1)

DISCONNECT-PDN-CONNECTION-WITHOUT-REACTIVATION-REQUEST (2)

This AVP corresponds to the "PDN continuity at inter RAT mobility" field as defined in 3GPP TS 23.401 [2] table 5.7.1-1.

7.3.215 eDRX-Cycle-Length

The eDRX-Cycle-Length AVP is of type Grouped. This AVP shall contain an eDRX cycle length, along with the RAT type for which this cycle length is applicable to (e.g. E-UTRAN and NB-IOT).

AVP format:

eDRX-Cycle-Length ::= <AVP header: 1691 10415>

{ RAT-Type }

{ eDRX-Cycle-Length-Value }

*[ AVP ]

7.3.216 eDRX-Cycle-Length-Value

The eDRX-Cycle-Length-Value AVP is of type OctetString. This AVP shall contain the extended DRX cycle value subscribed for this user for a given RAT type. The contents of eDRX-Cycle-Length-Value shall consist of 1 octet.

The encoding shall be as defined in 3GPP TS 24.008 [31], clause 10.5.5.32, and it shall only contain the value of the field "eDRX value" for a given RAT type, i.e., the 4 least significant bits of the octet in this AVP shall contain bits 1-4 of octet 3 in the "Extended DRX parameter" IE (see Figure 10.5.5.32 of 3GPP TS 24.008 [31]), and the 4 most significant bits of the octet in this AVP shall be set to 0.

7.3.217 UE-PC5-AMBR

The UE-PC5-AMBR AVP is of type Unsigned32. It indicates the maximum bits delivered by UE over the PC5 interface within a period of time. The unit of UE-PC5-AMBR is bits/s.

7.3.218 Extended eNodeB-ID

The Extended eNodeB-ID AVP is of type OctetString, and indicates the eNodeB in which the UE is currently located. It is originally defined in 3GPP TS 29.217 [56].

7.3.219 MBSFN-Area

The MBSFN-Area AVP is of type Grouped. It contains a MBSFN Area ID and a Carrier Frequency (see 3GPP TS 32.422 [23]).

The AVP format shall conform to:

MBSFN-Area ::= <AVP header: 1694 10415>

[ MBSFN-Area-ID ]

[ Carrier-Frequency ]

*[ AVP ]

If both MBSFN-Area-ID and Carrier-Frequency values are present, a specific MBSFN area is indicated. If Carrier-Frequency value is present, but MBSFN-Area-ID is absent, all MBSFN areas on that carrier frequency are indicated. If both MBSFN-Area-ID and Carrier-Frequency are absent, any MBSFN area is indicated.

7.3.220 MBSFN-Area-ID

The MBSFN-Area-ID AVP is of type Unsigned32 and it shall contain the MBSFN Area ID value, in the range of 0..255 (see 3GPP TS 36.331 [62]).

7.3.221 Carrier-Frequency

The Carrier-Frequency AVP is of type Unsigned32 and it shall contain the Carrier Frequency value, in the range of 0..262143 (see 3GPP TS 36.331 [62]).

7.3.222 RDS-Indicator

The RDS-Indicator AVP is of type Enumerated and indicates whether the Reliable Data Service (RDS) is enabled or disabled for the APN. See 3GPP TS 23.682 [55].

The following values are defined:

DISABLED (0)

ENABLED (1)

The default value when this AVP is not present is DISABLED (0).

7.3.223 Service-Gap-Time

The Service-Gap-Time AVP is of type Unsigned32 and indicates the minimum number of seconds during which the UE shall stay in ECM-IDLE mode, after leaving the ECM-CONNECTED mode, before being allowed to send a subsequent connection request to enter ECM-CONNECTED mode again. See description of the Service Gap Control feature in 3GPP TS 23.401 [2].

7.3.224 Aerial-UE-Subscription-Information

The Aerial-UE-Subscription-Information AVP is of type Unsigned32 and indicates the subscription of Aerial UE function. The following values are defined:

AERIAL_UE_ALLOWED (0)

AERIAL_UE_NOT_ALLOWED (1)

This AVP corresponds to the "Aerial UE subscription information" information element as defined in 3GPP TS 36.413[19] and TS 36.423 [65].

7.3.225 Broadcast-Location-Assistance-Data-Types

The Broadcast-Location-Assistance-Data-Types AVP is of type Unsigned64. The content of this AVP is a bit mask which indicates the broadcast location assistance data types for which the UE is subscribed to receive ciphering keys used to decipher broadcast assistance data.

The meaning of the bits is defined in table 7.3.225-1:

Table 7.3.225-1: Broadcast-Location-Assistance-Data-Types

bit	name	Description
0	Positioning SIB Type 1-1	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-1.
1	Positioning SIB Type 1-2	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-2.
2	Positioning SIB Type 1-3	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-3.
3	Positioning SIB Type 1-4	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-4.
4	Positioning SIB Type 1-5	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-5.
5	Positioning SIB Type 1-6	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-6.
6	Positioning SIB Type 1-7	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-7.
7	Positioning SIB Type 2-1	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-1.
8	Positioning SIB Type 2-2	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-2.
9	Positioning SIB Type 2-3	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-3.
10	Positioning SIB Type 2-4	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-4.
11	Positioning SIB Type 2-5	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-5.
12	Positioning SIB Type 2-6	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-6.
13	Positioning SIB Type 2-7	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-7.
14	Positioning SIB Type 2-8	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-8.
15	Positioning SIB Type 2-9	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-9.
16	Positioning SIB Type 2-10	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-10.
17	Positioning SIB Type 2-11	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-11.
18	Positioning SIB Type 2-12	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-12.
19	Positioning SIB Type 2-13	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-13.
20	Positioning SIB Type 2-14	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-14.
21	Positioning SIB Type 2-15	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-15.
22	Positioning SIB Type 2-16	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-16.
23	Positioning SIB Type 2-17	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-17.
24	Positioning SIB Type 2-18	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-18.
25	Positioning SIB Type 2-19	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-19.
26	Positioning SIB Type 3-1	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 3-1.
27	Positioning SIB Type 1-8	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 1-8.
28	Positioning SIB Type 2-20	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-20.
29	Positioning SIB Type 2-21	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-21.
30	Positioning SIB Type 2-22	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-22.
31	Positioning SIB Type 2-23	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-23.
32	Positioning SIB Type 2-24	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-24.
33	Positioning SIB Type 2-25	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 2-25.
34	Positioning SIB Type 4-1	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 4-1.
35	Positioning SIB Type 5-1	This bit, when set, indicates that the UE is subscribed to receive ciphering keys applicable to positioning SIB Type 5-1.
NOTE: Bits not defined in this table shall be cleared by the sending HSS and discarded by the receiving MME or SGSN.

7.3.226 Paging-Time-Window

The Paging-Time-Window AVP is of type Grouped. This AVP shall contain the Paging Time Window length, along with the Operation Mode (see clause 7.3.227) for which this time window length is applicable to.

AVP format:

Paging-Time-Window ::= <AVP header: 1701 10415>

{ Operation-Mode }

{ Paging-Time-Window-Length }

*[ AVP ]

7.3.227 Operation-Mode

The Operation-Mode AVP is of type Unsigned32. This value shall indicate the operation mode for which the Paging-Time-Window-Length applies. See clause 3GPP TS 24.008 [31], clause 10.5.5.32.

The allowed values of Operation-Mode shall be in the range of 0 to 255.

Values are defined as follows:

0: Spare, for future use

1: Iu mode

2: WB-S1 mode

3: NB-S1 mode

4 to 255: Spare, for future use

7.3.228 Paging-Time-Window-Length

The Paging-Time-Window-Length AVP is of type OctetString. This AVP shall contain the Paging time window length subscribed for this user for a given operation mode. The contents of Paging-Time-Window-Length shall consist of 1 octet.

The encoding shall be as defined in 3GPP TS 24.008 [31], clause 10.5.5.32, and it shall only contain the value of the field "Paging Time Window length" for a given RAT type, i.e., the 4 most significant bits of the octet in this AVP shall contain bits 5-8 of octet 3 in the "Extended DRX parameter" IE (see Figure 10.5.5.32 of 3GPP TS 24.008 [31]), and the 4 least significant bits of the octet in this AVP shall be set to 0.

7.3.229 eDRX-Related-RAT

The eDRX-Related-RAT AVP is of type Grouped. This AVP shall contain the RAT type to which the eDRX Cycle Length is related:

AVP format

eDRX-Related-RAT ::= <AVP header: 1705 10415>

1 * { RAT-Type }

*[AVP]

7.3.230 Core-Network-Restrictions

The Core-Network-Restrictions AVP is of type Unsigned32 and shall contain a bitmask indicating the types of Core Network that are disallowed for a given user. The meaning of the bits shall be as defined in table 7.3.230-1:

Table 7.3.230-1: Core-Network-Restrictions

Bit	Name	Description
0	Reserved	The use of this bit is deprecated. This bit shall be discarded by the receiving MME.
1	5GC not allowed	Access to 5GC not allowed.
NOTE: Bits not defined in this table shall be cleared by the HSS and discarded by the MME.

7.3.231 Interworking-5GS-Indicator

The Interworking-5GS-Indicator AVP is of type Enumerated and indicates whether the interworking between 5GS and EPS is subscribed or not subscribed for the APN. See 3GPP TS 23.502 [67].

The following values are defined:

NOT-SUBSCRIBED (0)

SUBSCRIBED (1)

The default value when this AVP is not present is NOT-SUBSCRIBED (0).

7.3.232 Ethernet-PDN-Type-Indicator

The Ethernet-PDN-Type-Indicator AVP is of type Enumerated and indicates whether the APN has an Ethernet PDN type.

The following values are defined:

FALSE (0)

This value indicates that the APN does not have an Ethernet PDN type.

TRUE (1)

This value indicates that the APN has an Ethernet PDN type and in this case the value indicated by the PDN-Type AVP inside APN-Configuration AVP shall be ignored.

The default value when this AVP is not present is FALSE (0).

7.3.233 Subscribed-ARPI

The Subscribed-ARPI AVP is of type Unsigned32 and shall contain the subscribed value of the Additional RRM Policy Index. For details, see 3GPP TS 23.401 [2].

7.3.234 IAB-Operation-Permission

The IAB-Operation-Permission AVP is of type Enumerated. It shall indicate to the MME or SGSN whether the UE is allowed for IAB operation. See 3GPP TS 23.401 [2].

The following values are defined:

IAB_OPERATION_ALLOWED (0)

IAB_OPERATION_NOTALLOWED (1)

7.3.235 V2X-Subscription-Data-Nr

The V2X-Subscription-Data-Nr AVP is of type Grouped. It shall contain the V2X related subscription data for the network scheduled NR sidelink communication.

AVP format:

V2X-Subscription-Data-Nr ::= <AVP header: 1710 10415>

[ V2X-Permission ]

[ UE-PC5-AMBR ]

[ UE-PC5-QoS ]

*[AVP]

The UE-PC5-AMBR AVP within the V2X-Subscription-Data AVP indicates the UE AMBR used for NR PC5 interface.

7.3.236 UE-PC5-QoS

The UE-PC5-QoS AVP is of type Grouped. It shall contain the PC5 QoS parameters for V2X communication over NR PC5 reference point.

AVP format:

UE-PC5-QoS ::= <AVP header: 1711 10415>

1*{ PC5-QoS-Flow }

[ PC5-Link-AMBR ]

*[AVP]

7.3.237 PC5-QoS-Flow

The PC5-QoS-Flow AVP is of type Grouped. It shall contain the QoS parameters for a PC5 flow.

AVP format:

PC5-QoS-Flow ::= <AVP header: 1712 10415>

{ 5QI }

[ PC5-Flow-Bitrates ]

[ PC5-Range ]

*[AVP]

7.3.238 5QI

The 5QI AVP is of type Integer32. It shall contain the 5QI. See 3GPP TS 23.501 [69] for allowed values.If the 5QI is used in PC5 QoS parameter, it shall contain PQI, PQI is a special 5QI (see clause 5.4.2.1 of 3GPP TS 23.287 [68]).

7.3.239 PC5-Flow-Bitrates

The PC5-Flow-Bitrates AVP is of type Grouped. It shall contain the PC5 Flow Bit Rates, it’s for GBR QoS Flows only.

AVP format:

PC5-Flow-Bitrates ::= <AVP header: 1714 10415>

[ Guaranteed-Flow-Bitrates ]

[ Maximum-Flow-Bitrates ]

7.3.240 Guaranteed-Flow-Bitrates

The Guaranteed-Flow-Bitrates AVP is of type Integer32. It indicates the guaranteed bits delivered for the PC5 QoS flow by UE over the PC5 interface within a period of time. The unit of Guaranteed-Flow-Bitrates is bits/s.

7.3.241 Maximum-Flow-Bitrates

The Maximum-Flow-Bitrates AVP is of type Integer32. It indicates the maximum bits delivered for the PC5 QoS flow by UE over the PC5 interface within a period of time. The unit of Maximum-Flow-Bitrates is bits/s.

7.3.242 PC5-Range

The PC5-Range AVP is of type Integer32. It indicates the Range in the unit of meters. See clause 5.4.2.4 of 3GPP TS 23.287 [68].

7.3.243 PC5-Link-AMBR

The PC5-Link-AMBR AVP is of type Integer32. It indicates t the PC5 Link Aggregated Bit Rates for all the Non-GBR QoS Flows. The unit of PC5-Link-AMBR is bits/s.

7.3.244 Third-Context-Identifier

The Third-Context-Identifier AVP is of type Unsigned32 and indicates the identity of another default APN to be used when the subscription profile of the user contains APNs with three PDN types, i.e. IP-based PDN types, non-IP PDN types and Ethernet PDN types.