convert to OAS 3.1.0 (6863589e) · Commits · MEC - Multi-access Edge Computing / V2X Information Service API

MEC030_V2XInformationService.json

0 → 100644

+1781 −0

File added.

Preview size limit exceeded, changes collapsed.

MEC030_V2XInformationService.yaml

+661 −666

Original line number	Diff line number	Diff line
		openapi: 3.1.0
		info:
		title: "ETSI GS MEC 030 V2X Information Service API"
		title: 'ETSI GS MEC 030 V2X Information Service API'
		version: 2.1.1
		description: "ETSI GS MEC 030 V2X Information Service API described using OpenAPI."
		description: 'ETSI GS MEC 030 V2X Information Service API described using OpenAPI.'
		contact:
		name: ETSI Forge
		email: cti_support@etsi.org
		@@ -10,9 +11,8 @@ info:
		name: BSD-3-Clause
		url: 'https://forge.etsi.org/legal-matters'
		externalDocs:
		description: "ETSI GS MEC 030 V2X Information Service API, v2.1.1"
		description: 'ETSI GS MEC 030 V2X Information Service API, v2.1.1'
		url: 'https://www.etsi.org/deliver/etsi_gs/MEC/001_099/030/02.01.01_60/gs_mec030v020101p.pdf'
		openapi: 3.0.0
		servers:
		- url: 'https://localhost/vis/v1'
		tags:
		@@ -292,7 +292,6 @@ paths:
		type: string
		required: true


		get:
		tags:
		- 'subscription'
		@@ -522,7 +521,6 @@ components:
		type: object
		x-etsi-ref: 6.5.12


		Pc5ProvisioningInfo.proInfoPc5:
		description: The provisioning information per location as defined below.

		@@ -630,7 +628,6 @@ components:
		type: object
		x-etsi-mec-cardinality: 0..1


		ProvChgPc5Notification:
		properties:
		dstLayer2Id:
		@@ -1228,7 +1225,6 @@ components:
		type: object
		x-etsi-ref: 6.5.8


		msgType:
		description: '− denm(1): Decentralized Environmental Notification Message (DENM) as specified in ETSI EN 302 637-3 [i.3], − cam(2): Cooperative Awareness Message (CAM) as specified in ETSI EN 302 637-2 [i.2], − poi(3): Point of Interest message as specified in ETSI TS 101 556-1 [i.11], − spat(4): Signal Phase And Timing (SPAT) message as specified in SAE J2735 [i.12], − map(5): MAP message as specified in SAE J2735 [i.12], − ivi(6): In Vehicle Information (IVI) message as defined in ISO TS 19321 [i.13], − ev-rsr(7): Electric vehicle recharging spot reservation message, as defined in ETSI TS 101 556-3 [i.14], '
		enum:
		@@ -1271,7 +1267,7 @@ components:
		- msgEncodeFormat
		- msgContent
		type: object
		x-etsi-notes: "NOTE 1: Other standardization organizations could be added as needed.NOTE 2:The V2X message types of ETSI shall be used as specified in ETSI TS 102 894-2 [6], clause A.114."
		x-etsi-notes: 'NOTE 1: Other standardization organizations could be added as needed.NOTE 2:The V2X message types of ETSI shall be used as specified in ETSI TS 102 894-2 [6], clause A.114.'
		x-etsi-ref: 6.2.6

		V2xMsgSubscription.links:
		@@ -1340,7 +1336,6 @@ components:
		x-etsi-notes: "NOTE 1:\tOther standardization organizations could be added as needed.\nNOTE 2:\tThe V2X message types of ETSI shall be used as specified in ETSI TS 102 894-2 [6], clause A.114."
		x-etsi-ref: 6.3.5


		V2xMsgNotification.links:
		description: 'Links to resources related to this notification.'
		properties:
		@@ -1369,7 +1364,7 @@ components:
		stdOrganization:
		description: 'Standardization organization which defines the published V2X message type ETSI: European Telecommunications Standards Institute. See note 1.'
		enum:
		- "ETSI"
		- 'ETSI'
		type: string
		msgType:
		$ref: '#/components/schemas/msgType'
		@@ -1390,7 +1385,7 @@ components:
		- msgContent
		- _links
		type: object
		x-etsi-notes: "NOTE 1: Other standardization organizations could be added as needed. NOTE 2: The V2X message types of ETSI shall be used as specified in ETSI TS 102 894-2 [6], clause A.114"
		x-etsi-notes: 'NOTE 1: Other standardization organizations could be added as needed. NOTE 2: The V2X message types of ETSI shall be used as specified in ETSI TS 102 894-2 [6], clause A.114'

		V2xServerUsd.sdpInfo:
		description: SDP with IP multicast address and port number used for V2X communication via MBMS.
		@@ -1502,65 +1497,65 @@ components:
		x-etsi-mec-origin-type: URI
		type: object
		responses:
		204:
		'204':
		description: No Content
		206:
		'206':
		description: Partial content
		400:
		'400':
		description: 'Bad Request : used to indicate that incorrect parameters were passed to the request.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		401:
		'401':
		description: 'Unauthorized : used when the client did not submit credentials.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		403:
		'403':
		description: 'Forbidden : operation is not allowed given the current status of the resource.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		404:
		'404':
		description: 'Not Found : used when a client provided a URI that cannot be mapped to a valid resource URI.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		406:
		'406':
		description: 'Not Acceptable : used to indicate that the server cannot provide the any of the content formats supported by the client.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		409:
		'409':
		description: 'Conflict : The operation cannot be executed currently, due to a conflict with the state of the resource'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		412:
		'412':
		description: 'Precondition failed : used when a condition has failed during conditional requests, e.g. when using ETags to avoid write conflicts when using PUT'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		415:
		'415':
		description: 'Unsupported Media Type : used to indicate that the server or the client does not support the content type of the entity body.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		422:
		'422':
		description: 'Unprocessable Entity : used to indicate that the server understands the content type of the request entity and that the syntax of the request entity is correct but that the server is unable to process the contained instructions. This error condition can occur if an JSON request body is syntactically correct but semantically incorrect, for example if the target area for the request is considered too large. This error condition can also occur if the capabilities required by the request are not supported.'
		content:
		application/json:
		schema:
		$ref: '#/components/schemas/ProblemDetails'
		429:
		'429':
		description: 'Too Many Requests : used when a rate limiter has triggered.'
		content:
		application/json: