Issue/Feature Description:
When testing HTTP/2 N35 interface message HTTPV2_NUDR_SUBSCRIPTION_DATA_AM_DATA_REQ from UDM1→ UDR1, the request uses the following path (with v2 in URI as defined in 3GPP TS 29.504 and Ts 29.505):
:method = GET
:path = /$({abotprop.UDR1.SecureShell.IPAddress}):$({abotprop.UDR1.N35.Server.Port})/nudr-dr/v2/subscription-data/$({abotprop.SUT.SUPI})/$({abotprop.SUT.MCC})$({abotprop.SUT.MNC})/provisioned-data/am-data
However, on UDR1, the request is received/validated with /v1 support: (V2 support is not validated)
:path = /$({abotprop.UDR1.SecureShell.IPAddress}):$({abotprop.UDR1.N35.Server.Port})/nudr-dr/v1/subscription-data/...
As per spec, it should be strictly V2
Why this issue to fixed / feature is needed(give scenarios or use cases):
To ensure the APIs used are aligned with the Specification.
How to reproduce, in case of a bug:
Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)
Issue/Feature Description:
When testing HTTP/2 N35 interface message HTTPV2_NUDR_SUBSCRIPTION_DATA_AM_DATA_REQ from UDM1→ UDR1, the request uses the following path (with v2 in URI as defined in 3GPP TS 29.504 and Ts 29.505):
:method = GET
:path = /$({abotprop.UDR1.SecureShell.IPAddress}):$({abotprop.UDR1.N35.Server.Port})/nudr-dr/v2/subscription-data/$({abotprop.SUT.SUPI})/$({abotprop.SUT.MCC})$({abotprop.SUT.MNC})/provisioned-data/am-data
However, on UDR1, the request is received/validated with /v1 support: (V2 support is not validated)
:path = /$({abotprop.UDR1.SecureShell.IPAddress}):$({abotprop.UDR1.N35.Server.Port})/nudr-dr/v1/subscription-data/...
As per spec, it should be strictly V2
Why this issue to fixed / feature is needed(give scenarios or use cases):
To ensure the APIs used are aligned with the Specification.
How to reproduce, in case of a bug:
Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)