update MTS API OAS and Json to v2.2.1 (98de6253) · Commits · MEC - Multi-access Edge Computing / Bandwidth Management API

TrafficSteeringApi.json

+29 −9

Original line number	Diff line number	Diff line
		@@ -5,7 +5,7 @@
		"url": "https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api"
		},
		"title": "ETSI GS MEC 015 Multi-access Traffic Steering APIs",
		"version": "2.1.1",
		"version": "2.2.1",
		"description": "The present document focuses on the Multi-access Traffic Steering multi-access edge service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The present document specifies the necessary API with the data model and data format.",
		"license": {
		"name": "BSD-3-Clause",
		@@ -13,8 +13,8 @@
		}
		},
		"externalDocs": {
		"description": "ETSI GS MEC015 V2.1.1 Traffic Management APIs",
		"url": "https://www.etsi.org/deliver/etsi_gs/MEC/001_099/015/02.01.01_60/gs_MEC015v020101p.pdf"
		"description": "ETSI GS MEC015 V2.2.1 Traffic Management APIs",
		"url": "https://www.etsi.org/deliver/etsi_gs/MEC/001_099/015/02.02.01_60/gs_MEC015v020201p.pdf"
		},
		"servers": [
		{
		@@ -301,7 +301,7 @@
		"Query.app_instance_id": {
		"name": "app_instance_id",
		"in": "query",
		"description": "A MEC application instance may use multiple app_instance_ids as an input parameter to query the MTS session of a list of MEC application instances. See note.",
		"description": "A MEC application instance may use multiple app_instance_ids as an input parameter to query the MTS session of a list of MEC application instances. app_instance_id corresponds to appInsId defined in table 7.2.5-1. See note.",
		"required": false,
		"schema": {
		"type": "array",
		@@ -313,7 +313,7 @@
		"Query.app_name": {
		"name": "app_name",
		"in": "query",
		"description": "A MEC application instance may use multiple app_names as an input parameter to query the MTS session of a list of MEC application instances. See note.",
		"description": "A MEC application instance may use multiple app_names as an input parameter to query the MTS session of a list of MEC application instances. app_name corresponds to appName defined in table 7.2.5-1. See note.",
		"required": false,
		"schema": {
		"type": "array",
		@@ -325,7 +325,7 @@
		"Query.session_id": {
		"name": "session_id",
		"in": "query",
		"description": "A MEC application instance may use session_id as an input parameter to query the information of a list of MTS sessions. See note.",
		"description": "A MEC application instance may use session_id as an input parameter to query the information of a list of MTS sessions. session_id corresponds to sessionId defined in table 7.2.5-1. See note.",
		"required": false,
		"schema": {
		"type": "array",
		@@ -337,8 +337,10 @@
		},
		"schemas": {
		"MtsCapabilityInfo": {
		"title": "MtsCapabilityInfo",
		"properties": {
		"mtsAccessInfo": {
		"title": "mtsAccessInfo",
		"description": "The information on access network connection as defined below",
		"items": {
		"type": "object",
		@@ -384,6 +386,7 @@
		"x-etsi-mec-origin-type": "Uint32"
		},
		"timeStamp": {
		"title": "timeStamp",
		"description": "Time stamp to indicate when the corresponding information elements are sent",
		"properties": {
		"nanoSeconds": {
		@@ -413,14 +416,28 @@
		"x-etsi-ref": "7.2.4"
		},
		"MtsSessionInfo": {
		"title": "MtsSessionInfo",
		"properties": {
		"sessionId": {
		"description": "MTS session instance identifier",
		"type": "string",
		"x-etsi-mec-cardinality": "0..1",
		"x-etsi-mec-origin-type": "String"
		},
		"appInsId": {
		"description": "Application instance identifier",
		"type": "string",
		"x-etsi-mec-cardinality": "1",
		"x-etsi-mec-origin-type": "String"
		},
		"appName": {
		"description": "Name of the application",
		"type": "string",
		"x-etsi-mec-cardinality": "0..1",
		"x-etsi-mec-origin-type": "String"
		},
		"flowFilter": {
		"title": "flowFilter",
		"description": "Traffic flow filtering criteria, applicable only if when requestType is set as FLOW_SPECIFIC_MTS_SESSION. Any filtering criteria shall define a single session only. In case multiple sessions match flowFilter the request shall be rejected. If the flowFilter field is included, at least one of its subfields shall be included. Any flowFilter subfield that is not included shall be ignored in traffic flow filtering",
		"items": {
		"type": "object",
		@@ -433,7 +450,7 @@
		"x-etsi-mec-origin-type": "Uint32"
		},
		"dstIp": {
		"description": "Destination address identity of session (including range)",
		"description": "Destination address identity of session. The string for an IPv4 address shall be formatted in the \"dotted decimal\" notation as defined in IETF RFC 1166 [10]. The string for an IPv6 address shall be formatted according to clause 4 of IETF RFC 5952 [11], with in CIDR notation [12] used to provide the routing prefix",
		"type": "string",
		"x-etsi-mec-cardinality": "0..1",
		"x-etsi-mec-origin-type": "String"
		@@ -464,7 +481,7 @@
		"x-etsi-mec-origin-type": "Uint32"
		},
		"sourceIp": {
		"description": "Source address identity of session (including range)",
		"description": "Source address identity of session. The string for an IPv4 address shall be formatted in the \"dotted decimal\" notation as defined in IETF RFC 1166 [10]. The string for an IPv6 address shall be formatted according to clause 4 of IETF RFC 5952 [11], with in CIDR notation [12] used to provide the routing prefix",
		"type": "string",
		"x-etsi-mec-cardinality": "0..1",
		"x-etsi-mec-origin-type": "String"
		@@ -495,6 +512,7 @@
		"x-etsi-mec-origin-type": "Uint32"
		},
		"qosD": {
		"title": "qosD",
		"description": "QoS requirement description of the MTS session, applicable only if mtsMode = 4 (QoS). If the qosD field is included, at least one of its subfields shall be included. Any qosD subfield that is not included shall be ignored in Multi-access Traffic Steering (MTS)",
		"properties": {
		"maxJitter": {
		@@ -545,6 +563,7 @@
		"x-etsi-mec-origin-type": "Enum_inlined"
		},
		"timeStamp": {
		"title": "timeStamp",
		"description": "Time stamp to indicate when the corresponding information elements are sent ",
		"properties": {
		"nanoSeconds": {
		@@ -587,6 +606,7 @@
		"x-etsi-ref": "7.2.5"
		},
		"ProblemDetails": {
		"title": "ProblemDetails",
		"properties": {
		"detail": {
		"description": "A human-readable explanation specific to this occurrence of the problem",

TrafficSteeringApi.yaml

+32 −8

Original line number	Diff line number	Diff line
		@@ -3,15 +3,15 @@ info:
		contact:
		url: https://forge.etsi.org/rep/mec/gs015-bandwith-mgmt-api
		title: 'ETSI GS MEC 015 Multi-access Traffic Steering APIs'
		version: 2.1.1
		version: 2.2.1
		description: The present document focuses on the Multi-access Traffic Steering multi-access edge service. It describes the related application policy information including authorization and access control, information flows, required information and service aggregation patterns. The present document specifies the necessary API with the data model and data format.
		license:
		name: BSD-3-Clause
		url: 'https://forge.etsi.org/legal-matters'

		externalDocs:
		description: ETSI GS MEC015 V2.1.1 Traffic Management APIs
		url: 'https://www.etsi.org/deliver/etsi_gs/MEC/001_099/015/02.01.01_60/gs_MEC015v020101p.pdf'
		description: ETSI GS MEC015 V2.2.1 Traffic Management APIs
		url: 'https://www.etsi.org/deliver/etsi_gs/MEC/001_099/015/02.02.01_60/gs_MEC015v020201p.pdf'

		servers:
		- url: 'https://localhost/mts/v1'
		@@ -201,7 +201,7 @@ components:
		Query.app_instance_id:
		name: app_instance_id
		in: "query"
		description: "A MEC application instance may use multiple app_instance_ids as an input parameter to query the MTS session of a list of MEC application instances. See note."
		description: "A MEC application instance may use multiple app_instance_ids as an input parameter to query the MTS session of a list of MEC application instances. app_instance_id corresponds to appInsId defined in table 7.2.5-1. See note."
		required: false
		schema:
		type: array
		@@ -210,7 +210,7 @@ components:
		Query.app_name:
		name: app_name
		in: "query"
		description: "A MEC application instance may use multiple app_names as an input parameter to query the MTS session of a list of MEC application instances. See note."
		description: "A MEC application instance may use multiple app_names as an input parameter to query the MTS session of a list of MEC application instances. app_name corresponds to appName defined in table 7.2.5-1. See note."
		required: false
		schema:
		type: array
		@@ -219,7 +219,7 @@ components:
		Query.session_id:
		name: session_id
		in: "query"
		description: "A MEC application instance may use session_id as an input parameter to query the information of a list of MTS sessions. See note."
		description: "A MEC application instance may use session_id as an input parameter to query the information of a list of MTS sessions. session_id corresponds to sessionId defined in table 7.2.5-1. See note."
		required: false
		schema:
		type: array
		@@ -227,8 +227,10 @@ components:
		type: string
		schemas:
		MtsCapabilityInfo:
		title: MtsCapabilityInfo
		properties:
		mtsAccessInfo:
		title: mtsAccessInfo
		description: The information on access network connection as defined below
		items:
		type: object
		@@ -289,6 +291,7 @@ components:
		x-etsi-mec-cardinality: 1..N
		x-etsi-mec-origin-type: Uint32
		timeStamp:
		title: timeStamp
		description: Time stamp to indicate when the corresponding information elements are sent
		properties:
		nanoSeconds:
		@@ -318,13 +321,25 @@ components:
		\ The user may get billed extra charges if they go over the allotted amount."
		x-etsi-ref: 7.2.4
		MtsSessionInfo:
		title: MtsSessionInfo
		properties:
		sessionId:
		description: MTS session instance identifier
		type: string
		x-etsi-mec-cardinality: 0..1
		x-etsi-mec-origin-type: String
		appInsId:
		description: Application instance identifier
		type: string
		x-etsi-mec-cardinality: '1'
		x-etsi-mec-origin-type: String
		appName:
		description: Name of the application
		type: string
		x-etsi-mec-cardinality: 0..1
		x-etsi-mec-origin-type: String
		flowFilter:
		title: flowFilter
		description: Traffic flow filtering criteria, applicable only if when requestType is set as FLOW_SPECIFIC_MTS_SESSION. Any filtering criteria shall define a single session only. In case multiple sessions match flowFilter the request shall be rejected. If the flowFilter field is included, at least one of its subfields shall be included. Any flowFilter subfield that is not included shall be ignored in traffic flow filtering
		items:
		type: object
		@@ -336,7 +351,10 @@ components:
		x-etsi-mec-cardinality: 0..1
		x-etsi-mec-origin-type: Uint32
		dstIp:
		description: Destination address identity of session (including range)
		description: Destination address identity of session. The string for an IPv4 address shall
		be formatted in the "dotted decimal" notation as defined in IETF RFC 1166 [10]. The string
		for an IPv6 address shall be formatted according to clause 4 of IETF RFC 5952 [11],
		with in CIDR notation [12] used to provide the routing prefix
		type: string
		x-etsi-mec-cardinality: 0..1
		x-etsi-mec-origin-type: String
		@@ -362,7 +380,10 @@ components:
		x-etsi-mec-cardinality: 0..1
		x-etsi-mec-origin-type: Uint32
		sourceIp:
		description: Source address identity of session (including range)
		description: Source address identity of session. The string for an IPv4 address shall be
		formatted in the "dotted decimal" notation as defined in IETF RFC 1166 [10]. The string
		for an IPv6 address shall be formatted according to clause 4 of IETF RFC 5952 [11],
		with in CIDR notation [12] used to provide the routing prefix
		type: string
		x-etsi-mec-cardinality: 0..1
		x-etsi-mec-origin-type: String
		@@ -391,6 +412,7 @@ components:
		x-etsi-mec-cardinality: '1'
		x-etsi-mec-origin-type: Uint32
		qosD:
		title: qosD
		description: QoS requirement description of the MTS session, applicable only if mtsMode = 4 (QoS). If the qosD field is included, at least one of its subfields shall be included. Any qosD subfield that is not included shall be ignored in Multi-access Traffic Steering (MTS)
		properties:
		maxJitter:
		@@ -437,6 +459,7 @@ components:
		x-etsi-mec-cardinality: '1'
		x-etsi-mec-origin-type: Enum_inlined
		timeStamp:
		title: timeStamp
		description: 'Time stamp to indicate when the corresponding information elements are sent '
		properties:
		nanoSeconds:
		@@ -482,6 +505,7 @@ components:
		\ and port, respectively."
		x-etsi-ref: 7.2.5
		ProblemDetails:
		title: ProblemDetails
		properties:
		detail:
		description: A human-readable explanation specific to this occurrence of the problem