Invoke operation
Response
Ready. Choose an operation and press Send request.
Reference — Section 1 (N33, AF → NEF)

Aligned with shared/docs/CALL_FLOWS_N33_N5.md — resource model, relay note, and example payloads.

1.1 Resource model

  • Collection: POST /{scsAsId}/subscriptions — create subscription (AF session with QoS façade).
  • Individual: GET | PUT | PATCH | DELETE /{scsAsId}/subscriptions/{subscriptionId}.

scsAsId is the SCS/AS identifier path parameter (e.g. my-af-001).

1.2 Typical CRUD (relay: AF → NEF → PCF → NEF → AF)

(1) CREATE — AF POST …/subscriptions + JSON → NEF → PCF POST /app-sessions …
(2) READ   — AF GET …/subscriptions/{id} → NEF may refresh from PCF
(3) UPDATE — AF PUT … + JSON → NEF → PCF PATCH …
(4) PATCH  — AF PATCH … + JSON → NEF → PCF PATCH …
(5) DELETE — AF DELETE … → NEF → PCF DELETE …
Relay mode: the v1 NEF simulator requires ueIpv4Addr on create so the translated N5 ascReqData satisfies the ueIpv4 / ueIpv6 / ueMac oneOf toward the PCF.

1.3 Example A — CREATE

Method / path: POST /nnef-afsessionwithqos/v1/my-af-001/subscriptions
Headers: Content-Type: application/json, optional X-Correlation-ID

Body



          

1.4 Example B — GET

GET /nnef-afsessionwithqos/v1/my-af-001/subscriptions/{subscriptionId}

1.5 Example C — PUT (full replace)

PUT /nnef-afsessionwithqos/v1/my-af-001/subscriptions/{subscriptionId}

Body



          

1.6 Example D — PATCH

PATCH /nnef-afsessionwithqos/v1/my-af-001/subscriptions/{subscriptionId}

Body



          

1.7 Example E — DELETE

DELETE /nnef-afsessionwithqos/v1/my-af-001/subscriptions/{subscriptionId} — typical success: 204 No Content.

1.8 Example F — Mock notification NON-STANDARD

POST /nnef-afsessionwithqos/v1/_sim/{scsAsId}/subscriptions/{subscriptionId}/notify

Requires SIMULATOR_EXTENSIONS_ENABLED=true on the NEF.

Body



          

Correlation & trace

Send X-Correlation-ID on NEF requests in relay mode, then inspect:

GET /nnef-afsessionwithqos/v1/_sim/trace/{X-Correlation-ID}

NON-STANDARD