Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
[Nnrf_NFManagement] POST /subscriptions request serves a 200 response (R15.2.0)
POST /nnrf-nfm/v1/subscriptions HTTP/1.1
Host: 127.0.0.1:8080
Connection: keep-alive
Content-Length: 284
accept: application/json
DNT: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36
Content-Type: application/json
Origin: https://petstore.swagger.io
Sec-Fetch-Site: cross-site
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9
{
"nfStatusNotificationUri":"http://192.168.128.31:8380/nsmf-pdusession/v1/nnrf-nfm/nf-profiles/update",
"subscriptionId":"000000-subs0000000",
"subscrCond":{
"nfInstanceId":"41470254-cc86-44cf-aaa3-b56ac7000000"
},
"reqNotifEvents":[
"NF_REGISTERED",
"NF_PROFILE_CHANGED",
"NF_DEREGISTERED"
]
}
HTTP/1.1 201 Created
Connection: keep-alive
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Content-Type, Authorization, Accept, Accept-Language
Location: http://127.0.0.1:8080/nnrf-nfm/v1/subscriptions/000000-subs0000000
Content-Type: application/json
Content-Length: 396
Access-Control-Allow-Methods: GET, PUT, POST, PATCH, DELETE, OPTIONS
Date: Thu, 14 May 2020 16:02:11 GMT
{
"nfStatusNotificationUri":"http://192.168.128.31:8380/nsmf-pdusession/v1/nnrf-nfm/nf-profiles/update",
"subscrCond":{
"nfInstanceId":"41470254-cc86-44cf-aaa3-b56ac7000000"
},
"subscriptionId":"000000-subs0000000",
"validityTime":"2020-05-14T17:02:11.740Z",
"reqNotifEvents":[
"NF_REGISTERED",
"NF_PROFILE_CHANGED",
"NF_DEREGISTERED"
],
"plmnId":null,
"notifCondition":null,
"reqNfType":null,
"reqNfFqdn":null
}
@tnmtechnologies
Copy link
Author

tnmtechnologies commented May 14, 2020

The consumer subscribes to any notification event about NF instance with id 41470254-cc86-44cf-aaa3-b56ac7000000. Its nfStatusNotificationUri is http://192.168.128.31:8380/nsmf-pdusession/v1/nnrf-nfm/nf-profiles/update. This Uri does not depend on any 3GPP specification. The subscriptionId value is under consumer responsability.
The producer serves a 201 response and can set or change the validityTime attribute value. As always for a 201 response, the Location header is set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment