SOL005: Fix in notification interfaces (621d868a) · Commits · Miguel Angel Reina Ortega / SOL005

src/SOL005/NSDManagementNotification/NSDManagementNotification.yaml

+927 −4

File changed.

Preview size limit exceeded, changes collapsed.

src/SOL005/NSPerformanceManagementNotification/NSPerformanceManagementNotification.yaml

+137 −5

Original line number	Diff line number	Diff line
		@@ -31,9 +31,9 @@ produces:

		paths:
		##################################################################################
		# Notification endpoint NS Performance Management #
		# Notification endpoint PerformanceInformationAvailableNotification #
		##################################################################################
		'/URI_is_provided_by_the_client_when_creating_the_subscription-PerformanceInformationAvailableNotification':
		'/URI_is_provided_by_the_client_when_creating_the_subscription_PerformanceInformationAvailableNotificatio':
		parameters:
		- name: Authorization
		description: >
		@@ -55,20 +55,152 @@ paths:
		The POST method delivers a notification regarding a performance management event from the server to the client.
		This method shall follow the provisions specified in the
		Tables 7.4.9.3.1-1 and 7.4.9.3.1-2 for URI query parameters,

		parameters:
		- name: PerformanceInformationAvailableNotification
		description: >
		Notification about performance information availability.
		in: body
		required: false
		required: true
		schema:
		$ref: "definitions/SOL005NSPerformanceManagementNotification_def.yaml#/definitions/PerformanceInformationAvailableNotification"
		- name: Accept
		description: >
		Content-Types that are acceptable for the response.
		Reference: IETF RFC 7231
		in: header
		required: true
		type: string
		- name: Content-Type
		description: >
		The MIME type of the body of the request.
		Reference: IETF RFC 7231
		in: header
		required: true
		type: string
		responses:
		204:
		description: >
		204 NO CONTENT

		The notification was delivered successfully.
		headers:
		WWW-Authenticate:
		type: string
		description: >
		Challenge if the corresponding HTTP request has not provided
		authorization, or error details if the corresponding HTTP request
		has provided an invalid authorization token.
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1
		400:
		$ref: "../responses/SOL005_resp.yaml#/responses/400"
		401:
		$ref: "../responses/SOL005_resp.yaml#/responses/401"
		403:
		$ref: "../responses/SOL005_resp.yaml#/responses/403"
		404:
		$ref: "../responses/SOL005_resp.yaml#/responses/404"
		405:
		$ref: "../responses/SOL005_resp.yaml#/responses/405"
		406:
		$ref: "../responses/SOL005_resp.yaml#/responses/406"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		$ref: "../responses/SOL005_resp.yaml#/responses/503"

		get:
		summary: Test the notification endpoint
		description: >
		The GET method allows the server to test the notification endpoint that is provided by the client, e.g. during
		subscription.
		This method shall follow the provisions specified in the
		Tables 7.4.9.3.2-1 and 7.4.9.3.2-2 for URI query parameters,
		request and response data structures, and response codes.
		parameters:
		- name: Accept
		description: >
		Content-Types that are acceptable for the response.
		Reference: IETF RFC 7231.
		in: header
		required: true
		type: string
		responses:
		204:
		description: >
		204 NO CONTENT

		The notification endpoint was tested successfully.
		The response body shall be empty.
		headers:
		WWW-Authenticate:
		type: string
		description: >
		Challenge if the corresponding HTTP request has not provided
		authorization, or error details if the corresponding HTTP request
		has provided an invalid authorization token.
		maximum: 1
		minimum: 0
		Version:
		description: >
		Version of the API used in the response.
		type: string
		maximum: 1
		minimum: 1
		400:
		$ref: "../responses/SOL005_resp.yaml#/responses/400"
		401:
		$ref: "../responses/SOL005_resp.yaml#/responses/401"
		403:
		$ref: "../responses/SOL005_resp.yaml#/responses/403"
		404:
		$ref: "../responses/SOL005_resp.yaml#/responses/404"
		405:
		$ref: "../responses/SOL005_resp.yaml#/responses/405"
		406:
		$ref: "../responses/SOL005_resp.yaml#/responses/406"
		500:
		$ref: "../responses/SOL005_resp.yaml#/responses/500"
		503:
		$ref: "../responses/SOL005_resp.yaml#/responses/503"

		##################################################################################
		# Notification endpoint ThresholdCrossedNotification #
		##################################################################################
		'/URI_is_provided_by_the_client_when_creating_the_subscription_ThresholdCrossedNotification':
		parameters:
		- name: Authorization
		description: >
		The authorization token for the request.
		Reference: IETF RFC 7235
		in: header
		required: false
		type: string
		- name: Version
		description: >
		Version of the API requested to use when responding to this request.
		in: header
		required: true
		type: string

		post:
		summary: Notify about PM related events
		description: >
		The POST method delivers a notification regarding a performance management event from the server to the client.
		This method shall follow the provisions specified in the
		Tables 7.4.9.3.1-1 and 7.4.9.3.1-2 for URI query parameters,
		parameters:
		- name: ThresholdCrossedNotification
		description: >
		Notification about threshold crossing.
		in: body
		required: false
		required: true
		schema:
		$ref: "definitions/SOL005NSPerformanceManagementNotification_def.yaml#/definitions/ThresholdCrossedNotification"
		- name: Accept