description:Information about the serializers in this transport binding, as defined in the SerializerTypes type in ETSI GS MEC 011 [i.4]. Support for at least one of the entries is required in conjunction with the transport.
transport:
$ref:'#/definitions/TransportDescriptor'
TransportDescriptor:
title:TransportDescriptor
required:
@@ -118,6 +121,7 @@
implSpecificInfo:
type:object
description:Additional implementation specific details of the transport.
description:Describes the destination interface information, . Some applications (e.g. inline/tap) _DECAPSULATED, FORWARD_ENCAPSULATED or PASSTHROUGH, one value
shall be provided. If the action is onDUPLICATE_DECAPSULATED or DUPLICATE_ENCAPSULATED, two values shall be provided. See note 2.
filterType:
$ref:'#/definitions/FilterType'
priority:
type:integer
description:Priority of this traffic rule within the range 0 to 255. If traffic rule conflicts, the one with higher priority take precedence. Value indicates the priority in descending order, i.e. with 0 as the highest priority and 255 as the lowest priority.
description:Priority of this traffic rule within the range 0 to 255. If traffic rule conflicts, the one with higher priority take precedence. See note 1.
contentEncoding:int32
trafficFilter:
minItems:1
@@ -200,19 +208,24 @@
trafficRuleId:
type:string
description:Identifies the traffic rule.
description:|
NOTE 1: Value indicates the priority in descending order, i.e. with 0 as the highest priority and 255 as the lowest priority.
NOTE 2: Some applications (like inline/tap) require two interfaces. The first interface in the case of inline/tap is on the
client (e.g. UE) side and the second on the core network (e.g. EPC) side
description:If it is per FLOW, the filter matches upstream (e.g. UE->EPC) packets and the downstream (e.g. EPC->UE) packets are handled by the same context.