description:The GET method is used to query information about the MTS information. This method is typically used in the "Get MTS service Info from the MTS Service" procedure as described in clause 6.2.6.
operationId:mtscapabilityinfoGET
operationId:MtscapabilityinfoGET
tags:
-mts
responses:
@@ -33,11 +33,12 @@ paths:
$ref:'#/components/responses/403'
'404':
$ref:'#/components/responses/404'
parameters:[]
/mts_sessions/{sessionId}:
get:
summary:Retrieve information about specific MTS session.
description:This method retrieves information about an individual MTS session. This method is typically used in the "Get configured MTS Session Info from the MTS Service" procedure as described in clause 6.2.10.
operationId:mtssessionsByIdGET
operationId:MtssessionsGETSessionid
tags:
-mts
responses:
@@ -56,10 +57,17 @@ paths:
$ref:'#/components/responses/404'
'403':
$ref:'#/components/responses/403'
parameters:
-name:sessionId
in:path
required:true
description:The unique identifier of the sessionId.
schema:
type:string
put:
summary:Update the information about specific MTS session.
description:The unique identifier of the sessionId.
schema:
type:string
delete:
summary:Remove specific MTS session.
description:DELETE method is typically used in "Unregister from the MTS Service" procedure as described in clause 6.2.8.
operationId:mtssessionsByIdDELETE
operationId:MtssessionsDELETESessionid
tags:
-mts
responses:
@@ -103,11 +118,18 @@ paths:
$ref:'#/components/responses/404'
'403':
$ref:'#/components/responses/403'
parameters:
-name:sessionId
in:path
required:true
description:The unique identifier of the sessionId.
schema:
type:string
/mts_sessions:
get:
summary:Retrieve information about a list of MTS sessions.
description:This method retrieves information about a list of MTS sessions. This method is typically used in the "Get configured MTS Session Info from the MTS Service" procedure as described in clause 6.2.10.
operationId:mtssessionsGET
operationId:MtssessionsGET
tags:
-mts
parameters:
@@ -120,9 +142,6 @@ paths:
content:
application/json:
schema:
type:object
properties:
MtsSessionInfo:
type:array
items:
$ref:'#/components/schemas/MtsSessionInfo'
@@ -135,7 +154,7 @@ paths:
post:
summary:Create a MTS session.
description:This method is used to create a MTS session. This method is typically used in "Register application to the MTS Service" procedure as described in clause 6.2.7.
operationId:mtssessionsPOST
operationId:MtssessionsPOST
tags:
-mts
requestBody:
@@ -164,6 +183,7 @@ paths:
$ref:'#/components/responses/404'
'403':
$ref:'#/components/responses/403'
parameters:[]
components:
schemas:
ProblemDetails:
@@ -173,33 +193,28 @@ components:
type:string
format:uri
description:A URI reference according to IETF RFC 3986 that identifies the problem type
x-etsi-mec-cardinality:0..1
x-etsi-mec-origin-type:URI
title:
type:string
description:A short, human-readable summary of the problem type
x-etsi-mec-cardinality:0..1
x-etsi-mec-origin-type:String
status:
type:integer
format:uint32
description:The HTTP status code for this occurrence of the problem
x-etsi-mec-cardinality:0..1
x-etsi-mec-origin-type:Uint32
detail:
type:string
description:A human-readable explanation specific to this occurrence of the problem
x-etsi-mec-cardinality:0..1
x-etsi-mec-origin-type:String
instance:
type:string
format:uri
description:A URI reference that identifies the specific occurrence of the problem
description:The seconds part of the Time. Time is defined as Unixtime since January 1, 1970, 00:00:00 UTC
x-etsi-mec-origin-type:Uint32
x-etsi-mec-cardinality:'1'
type:integer
format:uint32
nanoSeconds:
description:The nanoseconds part of the Time. Time is defined as Unix-time since January 1, 1970, 00:00:00 UTC
x-etsi-mec-origin-type:Uint32
x-etsi-mec-cardinality:'1'
type:integer
format:uint32
required:
@@ -409,82 +390,59 @@ components:
-nanoSeconds
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
description:DSCP in the IPv4 header or Traffic Class in the IPv6 header
x-etsi-mec-origin-type:Uint32
x-etsi-mec-cardinality:0..1
type:integer
format:uint32
flowlabel:
description:Flow Label in the IPv6 header, applicable only if the flow is IPv6
x-etsi-mec-origin-type:Uint32
x-etsi-mec-cardinality:0..1
type:integer
format:uint32
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)
x-etsi-mec-origin-type:Structure
x-etsi-mec-cardinality:'1'
type:object
properties:
minTpt:
# description': minimal throughput in [kbps]
description:minimal throughput in [kbps]
$ref:'#/components/schemas/Unit32'
# x-etsi-mec-origin-type': Unit32
# x-etsi-mec-cardinality': 0..1
type:object
maxLatency:
# description': tolerable (one-way) delay in [10 nanoseconds]
description:tolerable (one-way) delay in [10 nanoseconds]
$ref:'#/components/schemas/Unit32'
# x-etsi-mec-origin-type': Unit32
# x-etsi-mec-cardinality': 0..1
type:object
maxLoss:
# description': tolerable packet loss rate in [1/10^x]
description:tolerable packet loss rate in [1/10^x]
$ref:'#/components/schemas/Unit32'
# x-etsi-mec-origin-type': Unit32
# x-etsi-mec-cardinality': 0..1
type:object
maxJitter:
# description': tolerable jitter in [10 nanoseconds]
description:tolerable jitter in [10 nanoseconds]
$ref:'#/components/schemas/Unit32'
# x-etsi-mec-origin-type': Unit32
# x-etsi-mec-cardinality': 0..1
type:object
priority:
# description': 'numeric value (0 - 255) corresponding to the traffic priority: 0: low; 1: medium; 2: high; 3: critical'
