ETSI TS 129 328 V12.15.0 (2020-01)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents (3GPP TS 29.328 version 12.15.0 Release 12)

RTS/TSGC-0429328vcf0

General Information

• Status: Published
• Publication Date: 14-Jan-2020
• Technical Committee: 3GPP CT 4 - MAP/CAMEL/GTP/BCH/SS/TrFO/IMS/GUP/WLAN (formely CN4)
• Current Stage: 12 - Completion
• Completion Date: 15-Jan-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
IP Multimedia (IM) Subsystem Sh interface;
Signalling flows and message contents
(3GPP TS 29.328 version 12.15.0 Release 12)


3GPP TS 29.328 version 12.15.0 Release 12 1 ETSI TS 129 328 V12.15.0 (2020-01)

Reference
RTS/TSGC-0429328vcf0
Keywords
5G,GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 2 ETSI TS 129 328 V12.15.0 (2020-01)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 3 ETSI TS 129 328 V12.15.0 (2020-01)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions, symbols and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 9
4 Main Concept . 9
5 General Architecture . 9
5.1 Functional requirements of network entities . 9
5.1.1 Functional Requirements of the Application Server . 9
5.1.2 Functional requirements of HSS . 9
5.1.3 Functional Requirements of the Presence Network Agent . 9
5.2 Functional classification of Sh interface procedures . 10
6 Procedure Descriptions. 10
6.1 User data handling procedures . 11
6.1.1 Data read (Sh-Pull) . 11
6.1.1.1 Detailed behaviour . 15
6.1.2 Data Update (Sh-Update) . 17
6.1.2.1 Detailed behaviour . 19
6.1.3 Subscription to notifications (Sh-Subs-Notif) . 22
6.1.3.1 Detailed behaviour . 24
6.1.4 Notifications (Sh-Notif) . 26
6.1.4.1 Detailed behaviour . 26
6.2 AS permissions list . 27
6.3 Void . 28
6.4 Void . 28
6.5 User identity to HSS resolution . 28
7 Information element contents . 29
7.1 User Identity . 29
7.1.1 IMS Public User Identity / Public Service Identity . 29
7.1.2 MSISDN . 29
7.1A Wildcarded PSI . 29
7.1B Wildcarded Public User Identity . 29
7.2 Requested Domain . 29
7.2A Requested Nodes . 29
7.2B Serving Node Indication . 30
7.3 Requested Data . 30
7.4 Service Indication . 30
7.5 Result . 30
7.6 Data . 30
7.6.1 Repository Data . 33
7.6.2 IMSPublicIdentity . 33
7.6.3 IMS User State . 33
7.6.4 S-CSCF Name . 34
7.6.5 Initial Filter Criteria . 34
7.6.6 Location Information . 34
7.6.6.1 Location information for CS . 35
7.6.6.2 Location information for GPRS . 35
7.6.6.3 Location information for EPS . 36
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 4 ETSI TS 129 328 V12.15.0 (2020-01)
7.6.6.4 Location Information for TWAN . 36
7.6.7 User state . 37
7.6.8 Charging information . 37
7.6.9 MSISDN . 37
7.6.9A Extended MSISDN . 37
7.6.10 PSIActivation . 38
7.6.11 DSAI . 38
7.6.12 Void . 38
7.6.13 Void . 38
7.6.14 IP address secure binding information . 38
7.6.15 Service Priority Level . 38
7.6.15A Extended Priority . 39
7.6.16 SMSRegistrationInfo . 39
7.6.17 UE reachability for IP . 39
7.6.18 T-ADS Information. 39
7.6.19 Private Identity . 39
7.6.20 STN-SR . 39
7.6.21 UE SRVCC Capability . 40
7.6.22 CSRN . 40
7.6.23 Reference Location Information . 40
7.6.24 IMSI . 40
7.6.25 IMSPrivateUserIdentity . 40
7.7 Subscription request type . 40
7.8 Current Location . 40
7.9 Application Server Identity . 40
7.10 Application Server Name . 40
7.11 Requested Identity Set . 41
7.12 Expiry Time. 41
7.13 Send Data Indication . 41
7.14 DSAI Tag . 41
7.15 Session-Priority . 41
7.16 One Time Notification . 41
7.17 Repository Data ID . 41
7.18 Pre-paging Supported . 41
7.19 Local Time Zone Indication . 41
7.20 UDR Flags . 42
7.21 Call Reference Info . 42
7.22 Call Reference Number . 42
7.23 AS-Number . 42
8 Protocol version identification . 42
9 Operational Aspects . 42
Annex A (normative):  Mapping of Sh operations and terminology to Diameter . 43
A.1 Introduction . 43
A.2 Sh message to Diameter command mapping. 43
A.3 Void . 43
Annex B (informative):  Message flow . 44
B.1 Message flows . 44
B.1.1 Data Update, Registration, Notification Subscription. . 44
Annex C (informative):  UML model of the data downloaded over Sh interface . 46
C.1 General description. 46
C.2 PublicIdentifiers . 48
C.3 Sh-IMS-Data . 49
Annex D (normative): XML schema for the Sh interface user profile . 51
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 5 ETSI TS 129 328 V12.15.0 (2020-01)
Annex E (informative): T-ADS request handling in the HSS. 61
Annex F (normative): Diameter overload control mechanism . 68
F.1 General . 68
F.2 HSS behaviour . 68
F.3 AS behaviour . 68
Annex G (Informative): Diameter overload node behaviour . 69
G.1 Message prioritization . 69
Annex H (informative): Change history . 70
History . 75

ETSI
3GPP TS 29.328 version 12.15.0 Release 12 6 ETSI TS 129 328 V12.15.0 (2020-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.

ETSI
3GPP TS 29.328 version 12.15.0 Release 12 7 ETSI TS 129 328 V12.15.0 (2020-01)
1 Scope
This 3GPP Technical Specification (TS) specifies:
1. The interactions between the HSS (Home Subscriber Server) and the SIP AS (Application Server) and between
the HSS and the OSA SCS (Service Capability Server). This interface is referred to as the Sh reference point.
2. The interactions between the SIP AS and the SLF (Subscription Locator Function) and between the OSA SCS
and the SLF. This interface is referred to as the Dh reference point.
The IP Multimedia (IM) Core Network Subsystem stage 2 is specified in 3GPP TS 23.228 [1] and the signalling flows
for the IP multimedia call control based on SIP and SDP are specified in 3GPP TS 24.228 [2].
The IP Multimedia (IM) Session Handling with the IP Multimedia (IM) call model is specified in 3GPP TS 23.218 [4].
This document addresses the signalling flows and message contents for the protocol at the Sh and Dh interface.
This document also addresses how the functionality of Ph interface is accomplished.
The Presence Service Stage 2 description (architecture and functional solution) is specified in 3GPP TS 23.141 [18].
2 References
[1] 3GPP TS 23.228: "IP Multimedia (IM) Subsystem – Stage 2".
[2] 3GPP TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP
(Release 5)".
[3] 3GPP TS 23.002: "Network architecture".
[4] 3GPP TS 23.218: "IP Multimedia (IM) Session Handling; IP Multimedia (IM) call model".
[5] 3GPP TS 29.329: "Sh Interface based on Diameter – Protocol details".
[6] 3GPP TS 29.228: "IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Message
Elements".
[7] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol ; Protocol details".
[8] IETF RFC 3588: "Diameter Base Protocol".
[9] ITU-T recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[10] 3GPP TS 23.018: "Basic Call Handling; Technical realization".
[11] 3GPP TS 23.003: "Numbering, Addressing and Identification".
[12] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[13] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[14] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase
3 - Stage 2".
[15] IETF RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
[16] IETF RFC 3261: "SIP: Session Initiation Protocol".
[17] IETF RFC 3966: "The tel URI for Telephone Numbers".
[18] 3GPP TS 23.141: "Presence Service; Architecture and Functional Description".
[19] 3GPP TS 23.012: "Location Management Procedures".
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 8 ETSI TS 129 328 V12.15.0 (2020-01)
[20] ANSI X3.4: "Coded Character Set - 7-bit American Standard Code for Information Interchange"
[21] Void
[22] 3GPP TS 33.203: "Access Security for IP-based services".
[23] IETF RFC 791: "Internet Protocol".
[24] IETF RFC 4291: "IP Version 6 Addressing Architecture".
[25] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[26] 3GPP TS 29.272: "MME and SGSN Related Interfaces Based on Diameter Protocol ".
[27] 3GPP TS 23.008: "Organization of subscriber data".
[28] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[29] 3GPP TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services
and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2".
[30] 3GPP TS 29.118: "SGs interface specification".
[31] 3GPP TS 29.272: "Evolved Packet System; MME and SGSN Related Interfaces Based on
Diameter Protocol".
[32]           3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[33] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) centralized services; Stage 2".
[34] 3GPP TS 29.273: "3GPP EPS AAA interfaces".
[35] IETF RFC 4776: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for
Civic Addresses Configuration Information".
[36] IETF RFC 7683: "Diameter Overload Indication Conveyance".
[37] ETSI ES 283 034: "e4 interface based on the DIAMETER protocol".
[38] 3GPP TS 22.153: "Multimedia Priority Service".
[39] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP" – stage 3.
[40] Void.
[41] IETF RFC 5952: "A Recommendation for IPv6 Address Text Representation".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply.
IP Multimedia session: IP Multimedia session and IP Multimedia call are treated as equivalent in this specification.
Transparent data: Data that is understood syntactically but not semantically by the HSS. It is data that an AS may
store in the HSS to support its service logic. One example is data that an AS stores in the HSS, using it as a repository.
Non-transparent data: Data that is understood both syntactically and semantically by the HSS.
AS (Application Server): a term used to denote either of a SIP Application Server or an OSA Service Capability
Server.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 9 ETSI TS 129 328 V12.15.0 (2020-01)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AS Application Server
C Conditional
CSCF Call Session Control Function
CSG Closed Subscriber Group
GIBA GPRS-IMS-Bundled-Authentication
C Conditional
HSS Home Subscriber Server
IE Information Element
IP Internet Protocol
IM IP Multimedia
IMS IP Multimedia Subsystem
M Mandatory
O Optional
SIP Session Initiation Protocol
SLF Subscription Locator Function
S-CSCF Serving CSCF
4 Main Concept
This document presents the Sh interface related functional requirements of the communicating entities.
It gives a functional classification of the procedures and describes the procedures and message parameters.
Error handling flows, protocol version identification, etc. procedures are also included.
5 General Architecture
This clause further specifies the architectural assumptions associated with the Sh reference point, building on 3GPP
TS 23.228 [1], 3GPP TS 23.218 [4] and also the Ph reference point building upon 3GPP TS 23.141 [18].
5.1 Functional requirements of network entities
5.1.1 Functional Requirements of the Application Server
The Application Server may communicate with the HSS over the Sh interface.
For functionality of the Application Server refer to 3GPP TS 23.002 [3], 3GPP TS 23.228 [1] and 3GPP TS 23.218 [4].
5.1.2 Functional requirements of HSS
The HSS may communicate with the Application Server over the Sh interface and with the Presence Network Agent
over the Ph interface. The functionality of the Ph interface shall be the same as the functionality of the Sh interface.
For functionality of the HSS refer to 3GPP TS 23.002 [3], 3GPP TS 23.228 [1] and 3GPP TS 23.218 [4].
5.1.3 Functional Requirements of the Presence Network Agent
The Presence Network Agent may communicate with the HSS over the Ph interface. In this case, all references to an
Application Server in this specification apply also to a Presence Network Agent.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 10 ETSI TS 129 328 V12.15.0 (2020-01)
5.2 Functional classification of Sh interface procedures
Operations on the Sh interface are classified in functional groups:
1. Data handling procedures
- The download of data from the HSS to an AS.
- The update of data in the HSS.
2. Subscription/notification procedures
- An AS can subscribe to receive notifications from the HSS of changes in data.
- The HSS can notify an AS of changes in data for which the AS previously had subscribed.
6 Procedure Descriptions
In the tables that describe the Information Elements transported by each command, each Information Element is marked
as (M) Mandatory, (C) Conditional or (O) Optional.
- A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this
Information Element is absent, an application error occurs at the receiver and an answer message shall be sent
back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message
shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding
Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element.
- A conditional Information Element (marked as (C) in the table) shall be present in the command if certain
conditions are fulfilled.
- If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application
error occurs and an answer message shall be sent back to the originator of the request with the Result-Code
set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the
missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other
fields set as expected for this Information Element.
- If those conditions are not fulfilled, the Information Element shall be absent. If however this Information
Element appears in the message, it shall not cause an application error and it may be ignored by the receiver
if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an
answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall be sent back to the
originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be
included in this message.
- An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the
discretion of the application at the sending entity. Absence or presence of this Information Element shall not
cause an application error and may be ignored by the receiver.
When a procedure is required to determine the Public Identity used for an identity lookup in HSS and SLF, the HSS and
SLF shall derive the Public Identity from the SIP URI or Tel URI contained in the Public-Identity AVP, if not already
in canonical form as per 3GPP TS 23.003 [11], as described below:
- If the Public-Identity AVP contains a SIP URI, the HSS and SLF shall follow rules for conversion of SIP URI
into canonical form as specified in IETF RFC 3261 [16] chapter 10.3.
- If the Public-Identity AVP contains a Tel URI in E.164 format, the HSS and SLF shall remove visual separators
and remove all URI parameters.
When a command contains a ServiceData XML element with or without content (i.e. ),
the Service Data element is defined as present in the clauses 6.1 to 6.4.
Unknown permanent failure error codes shall be treated in the same way as DIAMETER_UNABLE_TO_COMPLY.
For unknown transient failure error codes the request may be repeated, or handled in the same way as
DIAMETER_UNABLE_TO_COMPLY.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 11 ETSI TS 129 328 V12.15.0 (2020-01)
6.1 User data handling procedures
6.1.1 Data read (Sh-Pull)
This procedure is used between the AS and the HSS. The procedure is invoked by the AS and is used:
- To read transparent and/or non-transparent data for a specified user from the HSS.
This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in 3GPP
TS 29.329 [5]. Tables 6.1.1.1 and 6.1.1.2 detail the involved information elements.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 12 ETSI TS 129 328 V12.15.0 (2020-01)
Table 6.1.1.1: Sh-Pull
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 13 ETSI TS 129 328 V12.15.0 (2020-01)
Information Mapping to Cat. Description
element name Diameter
AVP
User Identity User-Identity M IMS Public User Identity, Public Service Identity, or MSISDN of the user for
(See 7.1) whom the data is required.
See clause 7.1 for the content of this AVP.
Wildcarded PSI Wildcarded- O If the request refers to a Wildcarded PSI, the AS may include the
(See 7.1A) Public- corresponding Wildcarded PSI in this information element.
Identity
If this element is present, it should be used by the HSS to identify the
identity affected by the request. If that is the case, the terms User Identity
or Public Service Identity in the detailed behaviour refer to the Wildcarded
PSI.
Wildcarded Wildcarded- O If the request refers to a Wildcarded Public User Identity, the AS may
Public User IMPU include the corresponding Wildcarded Public User Identity in this
Identity (See information element.
7.1B)
If this element is present, it should be used by the HSS to identify the
identity affected by the request. If that is the case, the terms User Identity
or Public User Identity in the detailed behaviour refer to the Wildcarded
Public User Identity.
Requested data Data- M This information element indicates the reference to the requested
(See 7.3) Reference information. The set of valid reference values are defined in 7.6.
Requested Identity-Set O If Data-Reference indicates that IMS Public Identities is the requested data
Identity set set to be downloaded, this information element should be included.
(See 7.11)
When this information element takes the value IMPLICIT_IDENTITIES, the
HSS shall provide all non-barred IMS Public Identities that belong to the
same implicit registration set as the IMS Public Identity included in the
message in the User-Identity AVP. The MSISDN user identity is not
applicable for this value. If the User Identity is a Public Service Identity, the
HSS shall return only the User Identity in the request.

When this information element takes the value ALIAS_IDENTITIES, the
HSS shall provide all non-barred IMS Public User Identities that are in the
same Alias Public User Identity Set as the IMS Public User Identity
included in the message in the User-Identity AVP (see 3GPP TS 23.008
[27] for the definition of Alias Public User Identity Set). The MSISDN user
identity and the Public Service Identity are not applicable for this value.

When this information element takes the value
REGISTERED_IDENTITIES, the HSS shall provide all non-barred IMS
Public Identities whose state is registered, belonging to all Private Identities
that the IMS Public Identity or MSISDN in the User-Identity AVP is
associated with. If the User Identity is a Public Service Identity, the HSS
shall return no identities in the response.

When this information element takes the value ALL_IDENTITIES, the HSS
shall provide all non-barred IMS Public Identities, belonging to all Private
Identities that the User Identity is associated with.

If Data-Reference indicates that IMS Public Identities is the requested data
set to be downloaded and this information element is not included, the HSS
shall download the set of IMS Public Identities that would be downloaded if
the value of this information element had been ALL_IDENTITIES.
Requested Requested- C This information element indicates the domain to which the operation is
domain Domain applicable. Check table 7.6.1 to see when it is applicable.
(See 7.2)
Requested Requested- O This information element indicates the Node Types to which the operation
nodes Nodes is applicable. Check table 7.6.1 to see when it is applicable.
(See 7.2A)
Current Current- C This information element indicates whether an active location retrieval has
Location Location to be initiated or not. It shall be present if Location Information is requested.
(See 7.8) If this information element takes the value InitiateActiveLocationRetrieval
(1) the HSS shall indicate to the MSC/VLR and/or SGSN and/or MME the
need to initiate an active location retrieval.
Check table 7.6.1 to see when it is applicable.
ETSI
3GPP TS 29.328 version 12.15.0 Release 12 14 ETSI TS 129 328 V12.15.0 (2020-01)
Service Service- C IE that identifies, together with the User Identity included in the User-
Indication Indication Identity AVP and Data-Reference, the set of service related transparent
(See 7. 4) data that is being requested.
Check table 7.6.1 to see when it is applicable.
Application Origin-Host M IE that identifies the AS originator of the request and that is used to check
Server Identity the AS permission list.
(See 7.9)
Application Server-Name C IE that is used, together with the User Identity included in the User-Identity
Server Name AVP and Data-Reference, as key to identify the filter criteria.
(See 7.10) Check table 7.6.1 to see when it is applicable.
DSAI Tag (See DSAI-Tag C IE that is used, together with the User Identity included in the User-Identity
7.14) AVP and Data-Reference, as key to identify the instance of Dynamic
Service Activation Info (DSAI) requested.
Check table 7.6.1 to see when it is applicable.
Session Priority Session- O This information element shall indicate the session's priority to the HSS. If it
(see 7.15) Priority is not included, the request shall be treated as normal.
Private Identity User-Name C Private Identity of the user for whom the data is required.
(see 7.6.19)
Check table 7.6.1 to see when it is applicable.
Serving Node Serving- O This information element shall indicate that only the serving node
Indication Node- address/identity associated to the location data is required.
(See 7.2B) Indication
Check table 7.6.1 to see when it is applicable.
Pre-paging Pre-paging- O This information element shall indicate whether the AS supports pre-paging
Supported Supported or not.
(See 7.18) It indicates by its absence that the AS does not support pre-paging. For
details see 3GPP TS 23.018 [10].
Local Time Local-Time- O This information element shall indicate that the Local Time Zone is
Zone Indication Zone- requested and shall indicate whether only the Local Time Zone is required
(See 7.19) Indication or the Local Time Zone is required together with other location data.

Check table 7.6.1 to see when it is applicable.
UDR Flags UDR-Flags O This Information Element contains a bit mask. See 7.x for the meaning of
(See 7.20) the bits.
Call-Reference- Call- O This Information Element contains a Call Reference Number and the AS-
Info Reference- Number. May be present when Data Reference is CSRN. It allows a later
(See 7.21) Info retry of the call setup in the context of MTRR. See 3GPP TS 23.292 [33]

Table 6.1.1.2: Sh-Pull Resp
Information Mapping to Diameter Cat. Description
element name AVP
Result Result-Code / M Result of the request.
(See 7.5) Experimental_Result
Result-Code AVP shall be used for errors defined in the Diameter
Base Protocol.
Experimental-Result AVP shall be used for Sh errors. This is a
grouped AVP which contains the 3GPP Vendor ID in the Vendor-
Id AVP, and the error code in the Experimental-Result-Code AVP.
Wildcarded PSI Wildcarded-Public- O If the request refers to a specific PSI matching a Wildcarded PSI
(See 7.1A) Identity and the Wildcarded PSI was not included in the request and is not
included in the User-Data AVP, the HSS may include the
corresponding Wildcarded PSI in this information element. This
information may be used by the AS to identify the affected
Wildcarded PSI.
Wildcarded Wildcarded-IMPU O If the request refers to a Public User Identity matching a
Public User Wildcarded Public User Identity and the Wildcarded-IMPU AVP
Identity (See was not included in the request and is not included in the User-
7.1B) Data AVP, the HSS may include the corresponding Wildcarded
Public User Identity in this information element. This information
may be used by the AS to identify the affected Wildcarded Public
User Identity.
Data User-Data C Requested data. This element shall be present if the requested
(See 7.6) data exists in the HSS and the AS has permissions to read it.

ETSI
...