Content for TS 29.573 Word version: 18.5.0
A OpenAPI Specification
B Examples of N32-f Encoding
C End to end call flows when SEPP is on path
D Withdrawn API versions
$ Change history
A (Normative) OpenAPI Specification p. 80
A.1 General p. 80
A.2 N32 Handshake API p. 80
A.3 JOSE Protected Message Forwarding API on N32-f p. 88
A.4 SEPP Telescopic FQDN Mapping API |R16| p. 92
B Examples of N32-f Encoding p. 94
B.1 General p. 94
B.2 Input Message Containing No Binary Part p. 94
B.3 Input Message Containing Multipart Binary Part p. 95
C End to end call flows when SEPP is on path p. 98
C.1 General p. 98
C.2 TLS security between SEPPs p. 98
C.2.1 When http URI scheme is used p. 98
C.2.1.1 General |R16| p. 98
C.2.1.2 Without TLS protection between NF and SEPP and with TLS security without the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| p. 98
C.2.1.3 Without TLS protection between NF and SEPP and with TLS security with the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| p. 101
C.2.2 When https URI scheme is used p. 102
C.2.2.1 General |R16| p. 102
C.2.2.2 With TLS protection between NF and SEPP relying on telescopic FQDN, and TLS security without the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| p. 102
C.2.2.3 With TLS protection between NF and SEPP relying on 3gpp-Sbi-Target-apiRoot header, and TLS security without the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| p. 106
C.2.2.4 With TLS protection between NF and SEPP relying on telescopic FQDN, and TLS security with the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| p. 109
C.2.2.5 With TLS protection between NF and SEPP relying on 3gpp-Sbi-Target-apiRoot header, and TLS security with the 3gpp-Sbi-Target-apiRoot header used over N32f |R16| p. 112
C.3 Application Layer Security between SEPPs p. 114
D Withdrawn API versions p. 124
D.1 General p. 124
D.2 N32 Handshake API p. 124
$ Change history p. 126
