Skip to content
TechSpec
  • Foreword
  • 1 Scope
  • 2 References
  • 3 Definitions, symbols and abbreviations
  • 4 Main concept
  • 5 Definition methodology
  • 6 General guidelines
  • 7 GUP bindings
  • 8 Rp interface
  • 9 Rg interface
  • 10 Authentication, authorization and security
  • A.1 HSS IMS GUP Component definition
  • A.2 HSS IMS GUP Component structure
  • A.3 Common Data Types
  • A.4 Data Services Template Checklist tables
  • E.1 Correlation header
  • E.2 Provider header
  • E.3 ProcessingContext header
  • E.4 Consent header
  • E.5 UsageDirective header
  • E.6 ServiceInstanceUpdate header
  • E.7 Timeout header
  • E.8 CredentialsContext header
  • E.9 Security header
  • E.10 UserInteraction header

E.9 Security header

29.2403GPP3GPP Generic User Profile (GUP)NetworkRelease 17Stage 3TS

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

OASIS WS-Security compliant header elements as defined in OASIS SOAP Message Security [24] specification communicate the relevant security information in SOAP.

The construction and decoration of the <wsse:Security> header element in the context of GUP MUST adhere to the rules specified in OASIS SOAP Message Security [24] specification.

Additionally the construction, decoration and usage of the <wsse:Security> header element in the context of GUP MUST also adhere to the mechanisms defined in Liberty Alliance Security Mechanisms [15] specification.

Normative semantics, definitions, schemas and processing rules for the security header block are defined both in OASIS SOAP Message Security [24] and Liberty Alliance ID-WSF Security Mechanisms [15] specifications.