STF644 - Milestone D - Merge stf644 to Master branch

README.md

models/addresses.proto

models/device_info.proto

models/device_specific_message_formats.proto

models/downlink_info.proto

models/end_point_info.proto

models/event_msg.proto

models/impl_specific_info.proto

models/interface_descriptor.proto

models/iot_platform_info.proto

models/key_value_pair.proto

models/mb_transport_info.proto

models/o_auth2_info.proto

models/problem_details.proto

models/registereddevices_get200_response.proto

models/registereddevices_post_request.proto

models/registerediotplatforms_by_id_get200_response.proto

models/registerediotplatforms_post_request.proto

models/security_info.proto

models/serializer_type.proto

models/traffic_filter.proto

models/traffic_rule_descriptor.proto

models/transport_info.proto

models/transport_type.proto

models/tunnel_info.proto

models/uplink_msg.proto

services/reg_dev_service.proto

services/reg_iot_plat_service.proto

6.6.0

 No newline at end of file

/*

  ETSI GS MEC 033 IoT API

  ETSI GS MEC 033 IoT API described using OpenAPI.

  The version of the OpenAPI document: 3.1.1

  Contact: cti_support@etsi.org

  Generated by OpenAPI Generator: https://openapi-generator.tech

*/

syntax = "proto3";

package mec033;

message Addresses {

  // Host portion of the address.

  string host = 3208616;

  // Port portion of the address.

  int32 port = 3446913;

}

/*

  ETSI GS MEC 033 IoT API

  ETSI GS MEC 033 IoT API described using OpenAPI.

  The version of the OpenAPI document: 3.1.1

  Contact: cti_support@etsi.org

  Generated by OpenAPI Generator: https://openapi-generator.tech

*/

syntax = "proto3";

package mec033;

import public "models/device_specific_message_formats.proto";

import public "models/downlink_info.proto";

import public "models/key_value_pair.proto";

import public "models/traffic_rule_descriptor.proto";

message DeviceInfo {

  // Information needed for secondary authentication of the IoT device to the data network - see ETSI TS 129 561 [i.4] and ETSI TS 129 061 [i.5] for 5G and LTE procedures, respectively. This attribute is implementation dependent and should be logically linked to the identifiers of the IoT device listed hereafter.

  string deviceAuthenticationInfo = 231010367;

  // Additional information about the IoT device. This attribute is implementation dependent and may be expressed as an array of keyvalue pairs. 

  repeated KeyValuePair deviceMetadata = 227391580;

  // GPSI of the IoT device if 5G-enabled (see note 1).

  string gpsi = 3179775;

  // PEI of the IoT device if 5G-enabled (see note 1).

  string pei = 110868;

  // SUPI of the IoT device if 5G-enabled (see note 1).

  string supi = 3541979;

  // MSISDN of the IoT device if LTE-enabled (see note 1).

  string msisdn = 528072231;

  // IMEI of the IoT device if LTE-enabled (see note 1).

  string imei = 3236040;

  // IMSI of the IoT device if LTE-enabled (see note 1).

  string imsi = 3236474;

  // ICCID of the IoT device (see note 1).

  string iccid = 100017508;

  // Human-readable identifier of the IoT device.

  string deviceId = 35449363;

  // MEC traffic rules the IoT device is requested to be associated to (see note 2). The data type definition is as per ETSI GS MEC 010-2 [i.6].

  repeated TrafficRuleDescriptor requestedMecTrafficRule = 447629606;

  // IoT platform to which the IoT device is requested to be associated to (see note 2).

  string requestedIotPlatformId = 382142773;

  // User transport to which the IoT device is requested to be associated to (see note 2).

  string requestedUserTransportId = 440692748;

  DeviceSpecificMessageFormats deviceSpecificMessageFormats = 503076127;

  DownlinkInfo downlinkInfo = 457334378;

  // Client-side SSL/TLS certificate to be used by the MEC IoTS to interact with the user transport provided by the associated IoT platform in case the MEC IoTS acts on behalf of the IoT device.

  string clientCertificate = 55457997;

  // Indication whether the IoT device has a valid associated traffic rule (TRUE) or not (FALSE). See note 3.

  bool enabled = 535852225;

}

/*

  ETSI GS MEC 033 IoT API

  ETSI GS MEC 033 IoT API described using OpenAPI.

  The version of the OpenAPI document: 3.1.1

  Contact: cti_support@etsi.org

  Generated by OpenAPI Generator: https://openapi-generator.tech

*/

syntax = "proto3";

package mec033;

import public "models/event_msg.proto";

import public "models/uplink_msg.proto";

message DeviceSpecificMessageFormats {

  EventMsg eventMsgFormat = 357883555;

  UplinkMsg uplinkMsgFormat = 410143422;

}