Tech-
invite
3GPP
space
IETF
space
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
4‑5x
Content for
TS 29.573
Word version: 18.7.0
1…
4…
A…
4
General Description
4.1
Introduction
4.2
N32 Interface
4.3
Protocol Stack
5
N32 Procedures
5.1
Introduction
5.2
N32 Handshake Procedures (N32-c)
5.3
Message Forwarding Procedure on N32 (N32-f)
5.4
Nsepp_Telescopic_FQDN_Mapping Service
5.5
Support of Roaming Intermediaries
6
API Definitions
6.1
N32 Handshake API
6.2
JOSE Protected Message Forwarding API on N32
6.3
Nsepp_Telescopic_FQDN_Mapping API
7
Usage of HTTP CONNECT for N32-c connection establishment via Roaming Intermediaries
7.1
General
7.2
HTTP standards headers
7.3
HTTP custom headers
7.4
Error Handling
4
General Description
p. 11
4.1
Introduction
p. 11
4.2
N32 Interface
p. 11
4.2.1
General
p. 11
4.2.2
N32-c Interface
p. 11
4.2.3
N32-f Interface
p. 12
4.3
Protocol Stack
p. 13
4.3.1
General
p. 13
4.3.2
HTTP/2 Protocol
p. 13
4.3.2.1
General
p. 13
4.3.2.2
HTTP standard headers
p. 13
4.3.2.3
HTTP custom headers
p. 14
4.3.2.4
HTTP/2 connection management
p. 14
4.3.3
Transport Protocol
p. 15
4.3.4
Serialization Protocol
p. 15
5
N32 Procedures
p. 15
5.1
Introduction
p. 15
5.2
N32 Handshake Procedures (N32-c)
p. 16
5.2.1
General
p. 16
5.2.2
Security Capability Negotiation Procedure
p. 16
5.2.3
Parameter Exchange Procedure
p. 18
5.2.3.1
General
p. 18
5.2.3.2
Parameter Exchange Procedure for Cipher Suite Negotiation
p. 18
5.2.3.3
Parameter Exchange Procedure for Protection Policy Exchange
p. 20
5.2.3.4
Parameter Exchange Procedure for Security Information list Exchange
|R16|
p. 22
5.2.4
N32-f Context Termination Procedure
p. 23
5.2.5
N32-f Error Reporting Procedure
p. 24
5.3
Message Forwarding Procedure on N32 (N32-f)
p. 25
5.3.1
Introduction
p. 25
5.3.2
Use of Application Layer Security
p. 25
5.3.2.1
General
p. 25
5.3.2.2
Protection Policy Lookup
p. 26
5.3.2.3
Message Reformatting
p. 27
5.3.2.4
Message Forwarding to Peer SEPP
p. 29
5.3.2.5
JOSE Protected Forwarding Options
|R18|
p. 30
5.3.3
Message Forwarding to Peer SEPP when TLS is used
p. 30
5.3.3.1
General
|R18|
p. 30
5.3.3.2
Correlation of N32-c context and N32-f Connection for TLS Security
|R18|
p. 30
5.3.3.3
3gpp-Sbi-N32-Handshake-Id
|R18|
p. 31
5.3.3.4
Error Handling
|R18|
p. 31
5.3.4
Void
5.4
Nsepp_Telescopic_FQDN_Mapping Service
|R16|
p. 31
5.4.1
General
p. 31
5.4.2
Foreign FQDN to Telescopic FQDN Mapping Procedure
p. 32
5.4.3
Telescopic FQDN to Foreign FQDN Mapping Procedure
p. 32
5.5
Support of Roaming Intermediaries
|R18|
p. 33
5.5.1
General
p. 33
5.5.2
N32-c connection establishment via RIs
p. 33
5.5.2.1
N32-c connection establishment using HTTP CONNECT
p. 33
5.5.2.1.1
General
p. 33
5.5.2.1.2
Successful N32-c connection establishment via one RI
p. 33
5.5.2.1.3
Successful N32-c connection establishment via two RIs
p. 35
5.5.2.2
Error messages originated by RIs over the N32-c interface
p. 36
5.5.2.2.1
General
p. 36
5.5.2.2.2
N32-c connection establishment rejection by RI A
p. 36
5.5.2.2.3
N32-c connection establishment rejection by RI B
p. 37
5.5.3
N32-f messages forwarding or origination via RIs
p. 37
5.5.3.1
Error messages originated by (or related to) RIs over the N32-f interface
p. 37
5.5.3.1.1
General
p. 37
5.5.3.2
N32-f related error determined upon receipt of an N32-f request
p. 38
5.5.3.2.1
Error message originated by RI via N32-f
p. 38
5.5.3.2.2
Error message originated by pSEPP on N32-f (and optionally N32-c)
p. 39
5.5.3.3
N32-f related error determined upon receipt of an N32-f response
p. 40
5.5.3.3.1
Error message originated by RI via N32-f interface
p. 40
5.5.3.3.2
Error message formatting by the RI
p. 42
5.5.3.4
Applicative (i.e. SBI related) error determined upon receipt of an N32-f request
p. 43
5.5.3.4.1
Applicative error originated by RI via N32-f
p. 43
5.5.3.4.2
Error message formatting by the RI
p. 43
5.5.3.5
Handling of applicative events trigger determined by RI
p. 44
5.5.3.5.1
Applicative request message originated by RI via N32-f
p. 44
5.5.3.5.2
Originated request message formatting by the RI
p. 44
5.5.4
N32-f Context and/or N32-f Connection termination initiated by the RI
p. 45
5.5.4.1
General
p. 45
5.5.4.2
N32-f error reporting request encapsulated in a N32-f request
p. 45
5.5.4.3
Using N32-f error response
p. 46
6
API Definitions
p. 47
6.1
N32 Handshake API
p. 47
6.1.1
API URI
p. 47
6.1.2
Usage of HTTP
p. 48
6.1.2.1
General
p. 48
6.1.2.2
HTTP standard headers
p. 48
6.1.2.2.1
General
p. 48
6.1.2.2.2
Content type
p. 48
6.1.2.3
HTTP custom headers
p. 48
6.1.2.3.1
General
p. 48
6.1.3
Resources
p. 48
6.1.3.1
Overview
p. 48
6.1.4
Custom Operations without Associated Resources
p. 49
6.1.4.1
Overview
p. 49
6.1.4.2
Operation: Security Capability Negotiation
p. 49
6.1.4.2.1
Description
p. 49
6.1.4.2.2
Operation Definition
p. 49
6.1.4.3
Operation: Parameter Exchange
p. 50
6.1.4.3.1
Description
p. 50
6.1.4.3.2
Operation Definition
p. 50
6.1.4.4
Operation: N32-f Context Terminate
p. 51
6.1.4.4.1
Description
p. 51
6.1.4.4.2
Operation Definition
p. 51
6.1.4.5
Operation: N32-f Error Reporting
p. 52
6.1.4.5.1
Description
p. 52
6.1.4.5.2
Operation Definition
p. 52
6.1.5
Data Model
p. 52
6.1.5.1
General
p. 52
6.1.5.2
Structured data types
p. 53
6.1.5.2.1
Introduction
p. 53
6.1.5.2.2
Type: SecNegotiateReqData
p. 54
6.1.5.2.3
Type: SecNegotiateRspData
p. 56
6.1.5.2.4
Type: SecParamExchReqData
p. 58
6.1.5.2.5
Type: SecParamExchRspData
p. 60
6.1.5.2.6
Type: ProtectionPolicy
p. 61
6.1.5.2.7
Type: ApiIeMapping
p. 61
6.1.5.2.8
Type: IeInfo
p. 62
6.1.5.2.9
Type: ApiSignature
p. 63
6.1.5.2.10
Type: N32fContextInfo
p. 64
6.1.5.2.11
Type: N32fErrorInfo
p. 65
6.1.5.2.12
Type: FailedModificationInfo
p. 66
6.1.5.2.13
Type: N32fErrorDetail
p. 66
6.1.5.2.14
Type: CallbackName
p. 66
6.1.5.2.15
Type: IpxProviderSecInfo
|R16|
p. 66
6.1.5.2.16
Type: IntendedN32Purpose
|R17|
p. 67
6.1.5.2.17
Type: RiErrorInformation
|R18|
p. 67
6.1.5.3
Simple data types and enumerations
p. 67
6.1.5.3.1
Introduction
p. 67
6.1.5.3.2
Simple data types
p. 67
6.1.5.3.3
Enumeration: SecurityCapability
p. 68
6.1.5.3.4
Enumeration: HttpMethod
p. 68
6.1.5.3.5
Enumeration: IeType
p. 68
6.1.5.3.6
Enumeration: IeLocation
p. 69
6.1.5.3.7
Enumeration: N32fErrorType
p. 69
6.1.5.3.8
Enumeration: FailureReason
p. 70
6.1.5.3.9
Enumeration: N32Purpose
|R17|
p. 70
6.1.5.3.10
Enumeration: N32ReleaseIndication
|R18|
p. 70
6.1.5.4
Binary data
p. 71
6.1.6
Error Handling
p. 71
6.1.6.1
General
p. 71
6.1.6.2
Protocol Errors
p. 71
6.1.6.3
Application Errors
p. 71
6.1.7
Feature Negotiation
|R17|
p. 71
6.1.8
HTTP redirection
|R18|
p. 72
6.2
JOSE Protected Message Forwarding API on N32
p. 73
6.2.1
API URI
p. 73
6.2.2
Usage of HTTP
p. 73
6.2.2.1
General
p. 73
6.2.2.2
HTTP standard headers
p. 73
6.2.2.2.1
General
p. 73
6.2.2.2.2
Content type
p. 73
6.2.2.2.3
Accept-Encoding
|R16|
p. 73
6.2.2.3
HTTP custom headers
p. 74
6.2.2.3.1
General
p. 74
6.2.3
Resources
p. 74
6.2.3.1
Overview
p. 74
6.2.4
Custom Operations without associated resources
p. 74
6.2.4.1
Overview
p. 74
6.2.4.2
Operation: JOSE Protected Forwarding
p. 74
6.2.4.2.1
Description
p. 74
6.2.4.2.2
Operation Definition
p. 74
6.2.4.3
Operation: JOSE Protected Forwarding Options
|R16|
p. 77
6.2.4.3.1
Description
p. 77
6.2.4.3.2
Operation Definition
p. 77
6.2.5
Data Model
p. 78
6.2.5.1
General
p. 78
6.2.5.2
Structured data types
p. 79
6.2.5.2.1
Introduction
p. 79
6.2.5.2.2
Type: N32fReformattedReqMsg
p. 79
6.2.5.2.3
Type: N32fReformattedRspMsg
p. 80
6.2.5.2.4
Type: DataToIntegrityProtectAndCipherBlock
p. 80
6.2.5.2.5
Type: DataToIntegrityProtectBlock
p. 81
6.2.5.2.6
Type: RequestLine
p. 82
6.2.5.2.7
Type: HttpHeader
p. 82
6.2.5.2.8
Type: HttpPayload
p. 83
6.2.5.2.9
Type: MetaData
p. 84
6.2.5.2.10
Type: Modifications
p. 85
6.2.5.2.11
Type: FlatJweJson
p. 86
6.2.5.2.12
Type: FlatJwsJson
p. 87
6.2.5.2.13
Type: IndexToEncryptedValue
p. 87
6.2.5.2.14
Type: EncodedHttpHeaderValue
p. 87
6.2.5.2.15
Type: ProblemDetailsMsgForwarding
|R18|
p. 87
6.2.5.2.16
Type: AdditionInfoMsgForwarding
|R18|
p. 88
6.2.5.3
Simple data types and enumerations
p. 88
6.2.5.3.1
Introduction
p. 88
6.2.5.3.2
Simple data types
p. 88
6.2.5.3.3
Void
6.2.5.3.4
Void
6.2.6
Error Handling
p. 88
6.2.6.1
General
p. 88
6.2.6.2
Protocol Errors
p. 88
6.2.6.3
Application Errors
p. 88
6.3
Nsepp_Telescopic_FQDN_Mapping API
|R16|
p. 89
6.3.1
API URI
p. 89
6.3.2
Usage of HTTP
p. 90
6.3.2.1
General
p. 90
6.3.2.2
HTTP standard headers
p. 90
6.3.2.2.1
General
p. 90
6.3.2.2.2
Content type
p. 90
6.3.2.3
HTTP custom headers
p. 90
6.3.2.3.1
General
p. 90
6.3.3
Resources
p. 90
6.3.3.1
Overview
p. 90
6.3.3.2
Resource: Mapping
p. 91
6.3.3.2.1
Description
p. 91
6.3.3.2.2
Resource Definition
p. 91
6.3.3.2.3
Resource Standard Methods
p. 91
6.3.4
Data Model
p. 92
6.3.4.1
General
p. 92
6.3.4.2
Structured data types
p. 92
6.3.4.2.1
Introduction
p. 92
6.3.4.2.2
Type: TelescopicMapping
p. 93
6.3.4.3
Simple data types and enumerations
p. 93
6.3.4.3.1
Introduction
p. 93
6.3.4.3.2
Simple data types
p. 93
6.3.5
Error Handling
p. 93
6.3.5.1
General
p. 93
6.3.5.2
Protocol Errors
p. 93
6.3.5.3
Application Errors
p. 93
6.3.6
Feature Negotiation
p. 94
6.3.7
Security
p. 94
6.3.7.1
General
p. 94
7
Usage of HTTP CONNECT for N32-c connection establishment via Roaming Intermediaries
|R18|
p. 94
7.1
General
p. 94
7.2
HTTP standards headers
p. 94
7.3
HTTP custom headers
p. 95
7.3.1
3gpp-Connect-Req-Info
p. 95
7.3.2
3gpp-Connect-Resp-Info
p. 96
7.4
Error Handling
p. 96
7.4.1
General
p. 96
7.4.2
Application Errors
p. 96