{
  "informationService": {
    "descriptionInformation": {
      "abbreviations": [
        {
          "name": "ABI",
          "description": "Advanced Boundary Message"
        },
        {
          "name": "AC",
          "description": "Airspace Configuration"
        },
        {
          "name": "ACC",
          "description": "Area Control Centre"
        },
        {
          "name": "ACH",
          "description": "ATC Change Message (ICAO format, CFMU special)"
        },
        {
          "name": "ACP",
          "description": "Accept Message"
        },
        {
          "name": "ACT",
          "description": "Activate Message"
        },
        {
          "name": "ADEP",
          "description": "Airport of Departure"
        },
        {
          "name": "ADES",
          "description": "Airport of Destination"
        },
        {
          "name": "ADEXP",
          "description": "ATS Data Exchange Presentation"
        },
        {
          "name": "ADS",
          "description": "Automatic dependent surveillance"
        },
        {
          "name": "ADSP",
          "description": "ATM Data Service Provider"
        },
        {
          "name": "AFPL",
          "description": "Abbreviated Flight Plan"
        },
        {
          "name": "AFTN",
          "description": "Aeronautical Fixed Telecommunication Network"
        },
        {
          "name": "AIRM",
          "description": "ATM Information Reference Model"
        },
        {
          "name": "ALRS",
          "description": "Alerting Service"
        },
        {
          "name": "AMQP",
          "description": "Advanced Message Queuing Protocol"
        },
        {
          "name": "ANSP",
          "description": "Air Navigation Service Provider"
        },
        {
          "name": "AOI",
          "description": "Area Of Interest"
        },
        {
          "name": "APCH",
          "description": "Approach"
        },
        {
          "name": "APL",
          "description": "ATC Flight Plan Message (ICAO)"
        },
        {
          "name": "APOC",
          "description": "Airport Operator"
        },
        {
          "name": "APP",
          "description": "Approach"
        },
        {
          "name": "AR",
          "description": "Authorisation Required"
        },
        {
          "name": "ARR",
          "description": "Arrival"
        },
        {
          "name": "ATC",
          "description": "Air Traffic Control"
        },
        {
          "name": "ATCO",
          "description": "Air Traffic Control Officer"
        },
        {
          "name": "ATCS",
          "description": "Air Traffic Control Services"
        },
        {
          "name": "ATD",
          "description": "Actual Time of Departure"
        },
        {
          "name": "ATFCM",
          "description": "Air Traffic Flow and Capacity Management"
        },
        {
          "name": "ATI",
          "description": "Automatic Tracking Initiation "
        },
        {
          "name": "ATM",
          "description": "Air Traffic Management"
        },
        {
          "name": "ATN",
          "description": "Aeronautical Telecommunication(s) Network"
        },
        {
          "name": "ATO",
          "description": "Actual Time Over"
        },
        {
          "name": "ATOT",
          "description": "Actual Take-Off Time "
        },
        {
          "name": "ATS",
          "description": "Air Traffic Services"
        },
        {
          "name": "ATSU",
          "description": "Air Traffic Service Unit"
        },
        {
          "name": "CCS",
          "description": "Coflight Cloud Services"
        },
        {
          "name": "CDN",
          "description": "Coordination Message"
        },
        {
          "name": "CDR",
          "description": "Conditional Route"
        },
        {
          "name": "CFL",
          "description": "Cleared Flight Level"
        },
        {
          "name": "CHG",
          "description": "ICAO ATS Change Message"
        },
        {
          "name": "CLDM",
          "description": "Consolidated Logical Data Model"
        },
        {
          "name": "CNL",
          "description": "ICAO ATS Cancel Message"
        },
        {
          "name": "COF",
          "description": "Change of Frequency Message"
        },
        {
          "name": "COP",
          "description": "Coordination Point"
        },
        {
          "name": "CORRD",
          "description": "Correlation Distribution"
        },
        {
          "name": "CPDLC",
          "description": "Controller Pilot Datalink Communications"
        },
        {
          "name": "CWP",
          "description": "Controller Working Position"
        },
        {
          "name": "DAD",
          "description": "Dialogue and Distribution"
        },
        {
          "name": "DCB",
          "description": "Demand and Capacity Balancing"
        },
        {
          "name": "DCT",
          "description": "Direct Routing"
        },
        {
          "name": "DEP",
          "description": "Departure"
        },
        {
          "name": "DLA",
          "description": "ICAO ATS Delay Message"
        },
        {
          "name": "DOF",
          "description": "Date of Flight"
        },
        {
          "name": "DSNA",
          "description": "Direction des Services de la Navigation A0xC3 0xA9rienne (French ANSP)"
        },
        {
          "name": "EAP",
          "description": "Extended ATC Planner"
        },
        {
          "name": "EATMA",
          "description": "European ATM Architecture"
        },
        {
          "name": "ECL",
          "description": "En-Route Cruise Level"
        },
        {
          "name": "EET",
          "description": "Estimated Elapsed Time"
        },
        {
          "name": "EFL",
          "description": "Entry Flight Level"
        },
        {
          "name": "ENAV",
          "description": "Ente Nazionale Assistenza al Volo (Italian ANSP)"
        },
        {
          "name": "ENV",
          "description": "Environment"
        },
        {
          "name": "EOBD",
          "description": "Estimated Off-Block Date"
        },
        {
          "name": "EOBT",
          "description": "Estimated Off-Block Time"
        },
        {
          "name": "EQPT",
          "description": "Equipment"
        },
        {
          "name": "ETA",
          "description": "Estimated Time of Arrival"
        },
        {
          "name": "ETN",
          "description": "Estimated Time of Entry"
        },
        {
          "name": "ETX",
          "description": "Estimated Time of Exit"
        },
        {
          "name": "FABEC",
          "description": "Functional Airspace Block"
        },
        {
          "name": "FANS",
          "description": "Future Air Navigation Systems"
        },
        {
          "name": "FDD",
          "description": "Flight Data Distribution"
        },
        {
          "name": "FDM",
          "description": "Flight Data Management"
        },
        {
          "name": "FDO",
          "description": "Flight Data Operator"
        },
        {
          "name": "FDPS",
          "description": "Flight Data Processing System"
        },
        {
          "name": "FL",
          "description": "Flight Level"
        },
        {
          "name": "FNM",
          "description": "Flight Notification Message"
        },
        {
          "name": "FP",
          "description": "Flight Plan"
        },
        {
          "name": "FPL",
          "description": "Flight Plan Message (ICAO)"
        },
        {
          "name": "GAT",
          "description": "General Air Traffic"
        },
        {
          "name": "GGDC",
          "description": "Ground Ground Data Communications"
        },
        {
          "name": "HMI",
          "description": "human machine Interface"
        },
        {
          "name": "HOP",
          "description": "Hand Over Proposal message"
        },
        {
          "name": "IACH",
          "description": "Individual ATC Modification Message"
        },
        {
          "name": "IAP",
          "description": "Instrument Approach Procedure"
        },
        {
          "name": "IAPL",
          "description": "Individual ATC Flight Plan Message"
        },
        {
          "name": "IARR",
          "description": "Individual Arrival Message"
        },
        {
          "name": "IAS",
          "description": "Indicated Airspeed"
        },
        {
          "name": "ICAO",
          "description": "International Civil Aviation Organization"
        },
        {
          "name": "ICD",
          "description": "Interface Control Document"
        },
        {
          "name": "ICHG",
          "description": "Individual Modification Message"
        },
        {
          "name": "ICNL",
          "description": "Individual Cancellation Message"
        },
        {
          "name": "ID",
          "description": "Identifier"
        },
        {
          "name": "IDEP",
          "description": "Individual Departure Message"
        },
        {
          "name": "IDLA",
          "description": "Individual Delay Message"
        },
        {
          "name": "IER",
          "description": "Interface Exchange Requirement"
        },
        {
          "name": "IFPL",
          "description": "Individual Flight Plan Message"
        },
        {
          "name": "IFPS",
          "description": "Integrated initial flight plan processing system"
        },
        {
          "name": "IFR",
          "description": "Instrument Flight Rules"
        },
        {
          "name": "IKE",
          "description": "Internet Key Exchange"
        },
        {
          "name": "INAP",
          "description": "Integrated Network Management and ATC planning"
        },
        {
          "name": "IOP",
          "description": "Interoperability"
        },
        {
          "name": "IP",
          "description": "Internet Protocol"
        },
        {
          "name": "IPSEC",
          "description": "Internet Protocol Security protocol"
        },
        {
          "name": "IPV4",
          "description": "Internet Protocol version 4"
        },
        {
          "name": "JU",
          "description": "Joint Undertaking"
        },
        {
          "name": "KPI",
          "description": "Key Performance Indicator"
        },
        {
          "name": "LAM",
          "description": "Logical Acknowledgment Message"
        },
        {
          "name": "LOA",
          "description": "Letter of Agreement"
        },
        {
          "name": "LOF",
          "description": "Logon Forward"
        },
        {
          "name": "LP",
          "description": "Logical Position"
        },
        {
          "name": "LTM",
          "description": "Local Traffic Manager"
        },
        {
          "name": "MAS",
          "description": "Manual Assumption of Communications Message"
        },
        {
          "name": "MB",
          "description": "Mega byte"
        },
        {
          "name": "MEP",
          "description": "Message Exchange Pattern"
        },
        {
          "name": "MSA",
          "description": "Multi-sector area"
        },
        {
          "name": "MTCD",
          "description": "Medium Term Conflict Detection"
        },
        {
          "name": "NDA",
          "description": "Next Data Authority"
        },
        {
          "name": "NM",
          "description": "Network Manager"
        },
        {
          "name": "NOP",
          "description": "Network Operation Plan"
        },
        {
          "name": "NTP",
          "description": "Network Time Protocol"
        },
        {
          "name": "OAT",
          "description": "Operational Air Traffic"
        },
        {
          "name": "OCA",
          "description": "Oceanic Control Area"
        },
        {
          "name": "OCL",
          "description": "Oceanic Clearance"
        },
        {
          "name": "OCM",
          "description": "Oceanic Clearance Message"
        },
        {
          "name": "OCSP",
          "description": "Online Certificate Status Protocol"
        },
        {
          "name": "OE",
          "description": "Operational Entity"
        },
        {
          "name": "OLDI",
          "description": "On-line Data Interchange"
        },
        {
          "name": "PAC",
          "description": "Preliminary Activate Message"
        },
        {
          "name": "PBN",
          "description": "Performance Based Navigation"
        },
        {
          "name": "PKCS",
          "description": "Public-Key Cryptography Standards"
        },
        {
          "name": "PRO",
          "description": "Profile"
        },
        {
          "name": "PTA",
          "description": "Planned time of Arrival"
        },
        {
          "name": "RFL",
          "description": "Requested Flight Level"
        },
        {
          "name": "RJC",
          "description": "Reject Message"
        },
        {
          "name": "RNAV",
          "description": "Area Navigation"
        },
        {
          "name": "ROC",
          "description": "Rate of Climb"
        },
        {
          "name": "ROCD",
          "description": "Rate of Climb Descend"
        },
        {
          "name": "ROF",
          "description": "Request on Frequency"
        },
        {
          "name": "RPL",
          "description": "Repetitive Flight Plans"
        },
        {
          "name": "RTI",
          "description": "Request Tactical Instructions message "
        },
        {
          "name": "RVSM",
          "description": "Reduced Vertical Separation Minima"
        },
        {
          "name": "SAC",
          "description": "System Area Code"
        },
        {
          "name": "SDD",
          "description": "Service Definition Document"
        },
        {
          "name": "SDM",
          "description": "Supplementary Data Message"
        },
        {
          "name": "SESAR",
          "description": "Single European Sky Air Traffic Management Research"
        },
        {
          "name": "SFPL",
          "description": "System Flight Plan"
        },
        {
          "name": "SIC",
          "description": "System Identification Code"
        },
        {
          "name": "SID",
          "description": "Standard Instrumental Departure"
        },
        {
          "name": "SLA",
          "description": "Service Level Agreement"
        },
        {
          "name": "SSD",
          "description": "SWIM Service Description"
        },
        {
          "name": "SSI",
          "description": "Synchronous Serial Interface"
        },
        {
          "name": "SSR",
          "description": "Secondary Surveillance Radar"
        },
        {
          "name": "SSRM",
          "description": "Secondary Surveillance Radar Management"
        },
        {
          "name": "STAR",
          "description": "Standard Arrival Route"
        },
        {
          "name": "SWIM",
          "description": "System Wide Information Management"
        },
        {
          "name": "TBC",
          "description": "To Be Confirmed"
        },
        {
          "name": "TBD",
          "description": "To Be Defined"
        },
        {
          "name": "TCP",
          "description": "Transfer Control Protocol"
        },
        {
          "name": "TI",
          "description": "Technical Infrastructure"
        },
        {
          "name": "TIM",
          "description": "Transfer Initiation Message"
        },
        {
          "name": "TIP",
          "description": "Tactical Instructions Proposal message"
        },
        {
          "name": "TLS",
          "description": "transport level security"
        },
        {
          "name": "TP",
          "description": "Trajectory Prediction"
        },
        {
          "name": "UHF",
          "description": "Ultra High Frequency"
        },
        {
          "name": "UTC",
          "description": "Coordinated Universal Time"
        },
        {
          "name": "VC",
          "description": "Virtual Centre"
        },
        {
          "name": "VFR",
          "description": "Visual Flight Rules"
        },
        {
          "name": "VRCD",
          "description": "Vertical Rate Climb Descent"
        },
        {
          "name": "XFL",
          "description": "Exit Flight Level"
        }
      ],
      "serviceDescriptionIdentification": {
        "serviceDescriptionTitle": "CCS Flight Data Distribution Service Description",
        "serviceDescriptionEdition": "5.5.0.3",
        "serviceDescriptionReferenceDate": "14/06/2022"
      }
    },
    "name": "CCS FlightDataDistribution",
    "serviceAbstract": "This Service is part of Coflight Cloud Services (CCS), which are primarily designed to support the Virtual Centre concept. As such, these CCS Services support the interactions between the CCS ATM Data Service Provider (ADSP) and Virtual Centre Air Traffic Service Units (ATSUs). \r\nThe CCS FlightDataDistribution service is consistent with the other CCS services.\r\nIt supports:\r\n-\tthe distribution of Flight Plan information every time an update of a relevant Flight Plan is processed by the ADSP. The modifications of the Flight Plans can be triggered from several sources (other CWPs or functionality of the ADSP).\r\n-\tThe distribution of Erroneous AFTN messages information referred to FDO for manual correction, every time an AFTN message reception fails Coflight checks.\r\n\r\nNote: Only civil flights are handled by CCS services.\r\n \r\nThis version of the service is intended to be used in \u0027test mission\u0027, which aims at providing services and support to the Customer(s) to enable them to test any version of their ATM system during development.\r\n",
    "serviceCategorisation": {
      "serviceType": "SWIM_COMPLIANT",
      "lifeCycleStage": "OPERATIONAL",
      "businessActivityType": [
        "INFORMATION_MANAGEMENT"
      ],
      "informationCategory": [
        "FLIGHT_INFORMATION_EXCHANGE"
      ],
      "intendedConsumer": [
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
      ],
      "applicationMessageExchangePattern": [
        "BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM",
        "SYNCHRONOUS_REQUEST_REPLY"
      ]
    },
    "serviceDescriptionReferences": {
      "implementedStandard": [
        {
          "conformanceStatement": "Description of Service according to EUROCONTROL specifications",
          "description": "This specification contains requirements for describing information services in the context ofInitial System Wide Information Management (iSWIM). The requirements prescribe the minimum set of elements a service descriptionhas to contain",
          "isConformant": true,
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+documents\r\n\r\nNote: to request access to Confluence, please refer to the point of contact section.",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION",
          "title": "EUROCONTROL Specification for SWIM - Service Description ",
          "version": "2.0"
        },
        {
          "conformanceStatement": "Information definition according to EUROCONTROL specifications",
          "description": "This specification contains requirements forinformation definitions, meaning the formal descriptions of exchanged information, in the context of Initial System Wide Information Management (iSWIM). This contributes to semantic interoperability of information. ",
          "isConformant": true,
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+documents\r\n\r\nNote: to request access to Confluence, please refer to the point of contact section.",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION",
          "title": "EUROCONTROL Specification for SWIM - Information Definition",
          "version": "1.0"
        },
        {
          "conformanceStatement": "Implementation of service and network bindings",
          "description": "This specification contains requirements for system interfaces (e.g. protocols) and for IT infrastructure capabilities required to enable a reliable, secure and efficient exchange of information in the context of Initial System Wide Information Management (iSWIM).This contributes to technical interoperability",
          "isConformant": true,
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+documents\r\n\r\nNote: to request access to Confluence, please refer to the point of contact section.",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE",
          "title": "EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile",
          "version": "1.0"
        }
      ],
      "serviceDocument": [
        {
          "description": "AIRM traceability for CCS Flight Data Distribution service payload",
          "documentType": "AIRM_TRACE",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Distribution+Service \nNote: to request access to Confluence, please refer to the point of contact section",
          "title": "CCS AIRM mapping FDD service",
          "version": "1.0"
        },
        {
          "description": "Validation evidence for CCS Flight Data Distribution service",
          "documentType": "SERVICE_VALIDATION_REPORT",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Distribution+Service \nNote: to request access to Confluence, please refer to the point of contact section",
          "title": "CCS Validation evidence document - FlightDataDistribution",
          "version": "1.0"
        },
        {
          "description": "Protobuf files describing the exchanged information",
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Distribution+Service",
          "title": "CCS_flightDataDistribution.proto",
          "version": "5.2.0.2"
        },
        {
          "description": "Protobuf file describing the exchanged information common to two or more CCS Services",
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Distribution+Service",
          "title": "CCS_common.proto",
          "version": "5.5.1.2"
        },
        {
          "description": "Protobuf file describing the metadata used by the CCS Services",
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Distribution+Service",
          "title": "metadata.proto",
          "version": "v1.2.0.0"
        },
        {
          "description": "Complete service specification",
          "documentType": "SERVICE_SPECIFICATION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Distribution+Service",
          "title": "CCS Flight Data Distribution Service Description",
          "version": "5.5.0.3"
        },
        {
          "description": "Document that includes the list of all applicable error messages for CCS services",
          "documentType": "SERVICE_SPECIFICATION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+Documents",
          "title": "CCS Errors Management Document",
          "version": "2.0"
        }
      ]
    },
    "serviceProvision": {
      "dateInOperation": "2020-07-01",
      "provider": "DSNA\u0026ENAV",
      "providerDescription": "DSNA (Direction des Services de la Navigation Aerienne) is the national air navigation services provider of France. DSNA is entrusted with the provision of air traffic services, associated communication, navigation and surveillance services and aeronautical information services in all airspace under French responsibility and at designated airports. DSNA is member of A6, FABEC and SESAR JU.\r\nParis ACC : At the crossroads of the biggest European platforms, Paris ACC manage one of the most dense airspace in Europe. Paris ACC act to develop Paris airports capacity. The traffic handled by Paris ACC consists of 72% of flights departing or arriving at Parisian airports. With its 1.3 million controlled flights in 2018, Paris ACC is one the most important ACC in Europe.\r\n\r\nENAV S.p.A. (ENAV) is the Italian AIR Navigation Service Provider \r\nENAV\u0027s core business is to manage the regulated Air Traffic Control Services (ATCS), for which it is entrusted, allowing aircraft to fly within the assigned airspace with constantly enhanced levels of safety, optimizing the effectiveness of the service provided and the efficiency of the company",
      "providerType": [
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
      ],
      "pointOfContact": [
        {
          "name": "Andrea Quaresima",
          "description": "CCS Collaborative tools administrator - To request access to the CCS documentation",
          "email": "andrea.quaresima@enav.it",
          "phoneNumber": ""
        },
        {
          "name": "Guillaume Ramonet",
          "description": "Coflight Cloud Services Program Director - To request access to the CCS service",
          "email": "Guillaume.Ramonet@aviation-civile.gouv.fr",
          "phoneNumber": ""
        },
        {
          "name": "Service Desk",
          "description": "For Incidents on services in operation, contact the Service desk [working hours/opening days] as described in the related support service (incident management) supplied by CCS provider to CCS customer during the procurement phase\r\n",
          "email": "",
          "phoneNumber": ""
        }
      ]
    },
    "serviceGeneralDescription": {
      "operationalNeed": [
        {
          "name": " 1 General operational need",
          "description": "CCS FlightDataDistribution Service supports:\r\n- the distribution of Flight Plan information every time an update of a relevant Flight Plan is processed by the ADSP,\r\n- the distribution of Erroneous AFTN messages information every time an AFTN message reception fails Coflight checks.\r\n"
        }
      ],
      "functionality": [
        {
          "name": "Publish flight data",
          "description": "Publish flight data",
          "realWorldEffect": "All subscribers are informed of any change on the flight plan information of a flight when this flight is updated"
        },
        {
          "name": "Publish erroneous AFTN messages",
          "description": "Publish erroneous AFTN messages",
          "realWorldEffect": "All subscribers receive the AFTN messages information concerning the erroneous AFTN messages that need to be referred to FDO for manual correction."
        },
        {
          "name": "Get erroneous AFTN messages",
          "description": "Get erroneous AFTN messages",
          "realWorldEffect": "On request, a subscriber gets the AFTN messages information concerning the erroneous AFTN messages that need to be referred to FDO for manual correction."
        },
        {
          "name": "Get flight data",
          "description": "Get flight data",
          "realWorldEffect": "On request, a subscriber gets the flight plan information."
        }
      ],
      "accessAndUseCondition": [
        {
          "description": "\u003cbold\u003eIPR\u003c/bold\u003e\r\nIn accordance with their internal contractual rules on IPRs, DSNA, ENAV and skyguide retain exclusive ownership of the information contained in this document, which is to be deemed as foreground of the Coflight Cloud Services project (aiming at delivering remote flight data processing).\r\n\r\n\u003cbold\u003eAccess to the Service\u003c/bold\u003e\r\nThis service is provided to Service Consumers under a contractual basis signed between the CCS Service Provider and the Service Consumer.",
          "name": "Information ownership",
          "type": "LEGAL_CONSTRAINT"
        },
        {
          "description": "If the service consumer also consumes other CCS services, this Service shall be consumed simultaneously with the other CCS SWIM Services that are part of the contractual agreement between the service consumer and CCS service provider.",
          "name": "Dependencies with other CCS Services",
          "type": "SERVICE_CONSUMPTION_CONSTRAINT"
        },
        {
          "description": "This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities",
          "name": "Alignment to SESAR Virtual Centre activity",
          "type": "SERVICE_POLICY"
        },
        {
          "description": "Both the SWIM Service Description documents / Protobuf files and the CCS Services are versioned.\r\nThe version assigned to SSDs and to Protobuf files is composed by four digits in the form x.y.z.w.\r\nNew releases are numbered according to the following rule (compared to the previous version): \r\n-\tw increased by one: means that some content that could be ignored by the developers changed and the changes do not affect the protobuf files generation. For example, changes in the comments or in the descriptions of services, fields and data structures.\r\n-\tz increased by one: means that some content is changed by adding (but not changing or removing) some messages and/or data types. The generated protobuf files are expected to be an extension of the previous one and as result they are backward compatible.\r\n-\ty increased by one: means that the file is changed by changing or removing some operations. The generated protobuf files are not expected to be compatible with the previous one.\r\n-\tx increased by one: means that the file contains a new baseline. Major changes are expected to be present.\r\n\r\nThe service version is composed by 3 digits a.b.c assigned according to the following rule:\r\n- a could be 0,1,2 depending on the status of the service with respect to the SWIM registration phase:\r\n0: before the service application (as candidate)\r\n1: if candidate\r\n2: if compliant\r\n- b Increments if major changes have been done with respect to the previous version (modify/remove). No backward compatibility.\r\n- c Increments if minor changes have been done with respect to the previous version (addition/description modified). Full backward compatibility.\r\n",
          "name": "Service versioning",
          "type": "SERVICE_POLICY"
        },
        {
          "description": "Services management review are regularly organized with CCS customers to monitor the usability of the services and the KPI related to the quality of service described in the SLA.",
          "name": "KPIs monitoring",
          "type": "SERVICE_POLICY"
        },
        {
          "description": "The interface of CCS business services is accessible from outside DSNA premises through Internet using IPV4. An IPSEC link (IKE v1 or IKE v2) is used between CCS provider and CCS customer terminal network equipment.",
          "name": "Confidentiality and integrity",
          "type": "SECURITY_CONSTRAINT"
        },
        {
          "description": "The CCS provider acts as a certificate authority to provide and validate X.509 certificates. Before service operation, a package including X509 certificate and private key, will be delivered to the customer using the PKCS#12 archive file format. \r\nMutual authentication with X509 certificates is used between the AMQP broker and its client. Prior to any exchanges of AMQP Messages, the CCS customer shall establish with CCS Provider a TLS session using TLS 1.2 version. \r\n-\tCCS customer shall provide its certificates when establishing the connection. The certificates shall be valid (nor corrupted, nor revoked). The certificates of the CCS customer allow its identification for the use of the different CCS services (CCS business services at lower level).\r\n-\tThe CCS provider transmit its complete certificate during the connection phase and allow OCSP stapling to allow the CCS customer to check if it is valid or not.\r\n-\tFor the cryptographic algorithms, the authorized cipher suites must be agreed between the CCS provider and the customer based on the standards.\r\nAs an ATSU, the CCS business services customer, once identified, has access to all CCS services.\r\nIn the case of a Customer that would fail to authenticate 3 times in less than 3 minutes, the IP address would be ban and has to trigger the incident management procedure.\r\n",
          "name": "Authentication and authorisation",
          "type": "SECURITY_CONSTRAINT"
        }
      ],
      "concepts": [
        {
          "name": "Subscription filter for FlightDataSubscriber interface",
          "description": " [Name: OE; Type: ControllerDesignatorType; Cardinality: 0..*]  "
        },
        {
          "name": "Subscription filter for ErroneousFlightDataSubscriber interface",
          "description": " "
        }
      ],
      "qualityOfService": [
        {
          "name": "Services level objectives",
          "description": "The service level objectives regarding the availability, response time, throughput and recoverability of CCS Services depend on the purpose (mission) for which the Customer intend to use them (e.g. integration, test, training, operational purpose).\r\nThese service level objectives are therefore negotiated with the Customers, based on their safety analysis, and are detailed in the specific Service Level Agreement established with each CCS Customer."
        },
        {
          "name": "Network performance",
          "description": "The minimum Bandwidth required to consume CCS services (hypothesis for the technical integration service of 300 simultaneous flight managed by the system) is 10MB/s."
        },
        {
          "name": "Rate limitation",
          "description": "Customer ATSU shall restrict the overall rate of requests to a maximum of 720 request/minutes. The detailed rate limitation per services is detailed in the associated swim service description of each service."
        }
      ],
      "validation": [
        {
          "description": "Prior to any Service publication in the European SWIM Registry, CCS partners organise a joint validation that involve both CCS Providers and the first CCS Customer. \r\nTest Cases dealing with several test topics are run using a happy flow of few flights to check that the services are consistent, compliant with the actual service description and meet the acceptance criteria formulated by the first CCS Customer.\r\nAny anomaly raised by the test case execution is conveyed into the CCS bug management process. For each anomaly, a criticality level is assigned:\r\n-\tCritical: blocking issue that prevents the usage of a service functionality\r\n-\tMajor: issue that prevents the usage of a service functionality for which a workaround has been identified\r\n-\tMinor: other anomalies neither Critical nor Major \r\nDepending on the impacts, the issue is addressed to the specific team(s) in charge of the resolution (specification team, software team, dataset team...).\r\nOnce fixed, the issue is verified during one of the next validation sessions and closed if the resolution is confirmed by the validation team.\r\n\r\nIn addition to the functional validation, CCS partners also organise performance validations. The objectives of such sessions are:\r\n-\tto measure the CCS system response times according to several Key Performance Indicators (KPI) and Non-Functional Requirements (NFR) agreed among parties\r\n-\tto indicate if the KPI target values are reached or not\r\nThe following KPI are evaluated:\r\n-\tMaximum Provider response time for receiving the related to a short process request triggered from the CCS Client\r\n-\tMaximum Provider response time for receiving the result related to a long process request triggered from the CCS Client\r\n-\tMaximum Provider response time for receiving the result Provider related to a SFPL external event processing\r\nWhile the following KPI is just monitored for information:\r\n-\tMaximum Provider response time for receiving an Acknowledge (or Reject) related to a request triggered from the CCS Client.\r\nIt is worth noting that the performance test cases involve only the operations from a subset of CCS services.\r\nThe response times from end to end are computed by costumer equipments. CCS reference platform internal traversal times are measured on provider side.\r\nThe details about executed test cases and related results are provided in the CCS Validation evidence document of this service.\r\n",
          "type": "COLLABORATIVE_VALIDATION"
        }
      ]
    },
    "serviceInformationDescription": {
      "exchangeSchema": [
        {
          "name": "publishFlightDataDistribution Exchange schema",
          "reference": "CCS_flightDataDistribution.proto 5.2.0.2",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "publishErroneousAFTNMessageData Exchange schema",
          "reference": "CCS_flightDataDistribution.proto 5.2.0.2",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "flightDataRepositoryRequest Exchange schema",
          "reference": "CCS_flightDataDistribution.proto 5.2.0.2",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "getErroneousAFTNMessage Exchange schema",
          "reference": "CCS_flightDataDistribution.proto 5.2.0.2",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "getErroneousAFTNMessageSummary Exchange schema",
          "reference": "CCS_flightDataDistribution.proto 5.2.0.2",
          "schemaLanguage": "Protocol buffer"
        }
      ],
      "informationDefinition": [
        {
          "airmConformant": true,
          "airmVersion": "1.0.0",
          "description": "For the exchanged data model, please refer to the SWIM Service Description document (sections 2.1 and 2.2)",
          "name": "Service Information Definition"
        }
      ]
    },
    "serviceTechnicalDescription": {
      "securityMechanism": [
        {
          "description": "Mutual authentication with X509 certificates is used between the AMQP broker and its client established within a TLS session",
          "name": "Mutual authentication with X509 certificates",
          "type": [
            "AUTHENTICATION"
          ]
        },
        {
          "description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer.",
          "name": "TLS 1.2",
          "type": [
            "CONFIDENTIALITY",
            "INTEGRITY"
          ]
        },
        {
          "description": "IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer",
          "name": "IPsec v4",
          "type": [
            "CONFIDENTIALITY",
            "INTEGRITY",
            "AUTHENTICATION"
          ]
        }
      ],
      "serviceMonitoring": {
        "monitoringDescription": "CCS services and the servers, interfaces and infrastructure supporting them are supervised in real time by trained and licensed ATSEPS during CCS operational use.\r\nA dedicated service to obtain supervision information for the complete CCS swim services portfolio and the technical means supporting these services is available to the customer. For more information, please refer to the swim service description of the CCS technical supervision distribution service."
      },
      "technicalConstraint": [
        {
          "name": "Time synchronisation",
          "description": "CCS provider and CCS customer use the date and time for the operation of each service, and they must be able to date the traces and the information passed to the SSI log collector.\r\nNTP is the standard solution to synchronize time accurately. So, CCS Provider and CCS Customer shall use, each of them, at least one NTP server (stratum N), integrated in a NTP network containing a stratum 0 reference time clock. CCS customer may use a CCS provider server as a NTP server, however this usage is restricted to time synchronization test or monitoring purpose.\r\n"
        },
        {
          "name": "Provider-Customer interface-Exchange patterns",
          "description": "Each services interface of the CCS business services relies on the concept of AMQP queues and topics. \r\n-\tThe CCS customer shall use an implementation of the AMQP 1.0 specification to connect to the CCS provider AMQP 1.0 endpoint. \r\n-\tThe CCS provider endpoint is an AMQP 1.0 broker managing queue and topics. \r\nThe message payloads are encoded following a protobuf format. \r\nThe message exchange patterns used by the CCS services are request/reply and publish/subscribe. The CCS customer acts as requester and subscriber. The CCS provider acts as responder and publisher.\r\nConcerning publish-subscribe, the CCS customer subscribes to a CCS distribution service by directly listening to an appropriate AMQP topic, which name follows the CCS derivation rules.\r\nThe subscription to CCS Distribution Services is not performed via subscription operations, but by connecting to the appropriate AMQP Topic described in the .protobuf files as topic://\u003cNameSpaceName\u003e.\u003cServiceInterfaceName\u003e.\u003cLogicalOperation\u003e\r\nThe subscribers can filter the messages they want to receive by using the filter parameters, if any, defined for the subscription operation.\r\nPlease note that, after subscribing to a CCS Distribution Service, the current repository of messages needs to be obtained from CCS via the get\u003cMessageRepository\u003e operation defined for each CCS Distribution Service (see \"Subscription\" section of the distribution operation of the service).\r\nN.B:\r\n- If the CCS platform restarts while the Customer is connected to the AMQP Broker, the current repository of messages is published again.\r\n- The acknowledgement that a Customer receives to his request (\"RequestReport\") may be received after the data distribution that this request has triggered, as these two messages are managed asynchronously by AMQP Queues and Topics\r\n\r\nConcerning request-reply the CCS customer sends a request by sending a message to an appropriate AMQP queue, which name follows the CCS derivation rules, to make a request. The request message contains the name of the queue into the CCS customer listens and in which the reply from the CCS provider is expected.\r\n"
        },
        {
          "name": "Provider-Customer interface-Connection management",
          "description": "The Customer is the one that initiates the TCP connection and in case of a Network / Connection failure, it is the responsibility of the CCS customer to try to reconnect regularly."
        },
        {
          "name": "Provider-Customer interface-Queue management",
          "description": "The AMQP broker creates the physical resources associated with a destination (queue, topic) on demand when messages are actually sent to them.\r\nPermissions on queues and topics (read/write access) are granted based on intended usage. The CCS customer will have: \r\n-\tWrite access on the request queue\r\n-\tRead access on the reply queue \r\n-\tRead access on the topic for distribution service\r\n"
        }
      ]
    },
    "serviceInterface": [
      {
        "behaviour": [
          {
            "name": "Service behaviour",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "This Service Interface exposes one operation for publishing updates of flight plan data on a specific flight immediately when updated. ",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the topic",
                "name": "topic://ccs.protobuf.flightDataDistribution.FlightDataSubscriber.publishFlightDataDistribution",
                "type": "TOPIC"
              }
            ],
            "name": "FlightDataSubscriber"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "FlightDataSubscriber",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "This operation sends the flight plan data of a flight when it is updated.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "publishFlightDataDistribution",
            "operationMessage": [
              {
                "description": "Message definition for Flight Data",
                "direction": "IN",
                "isFault": false,
                "name": "FlightDataMessage"
              },
              {
                "description": "Predefined void",
                "direction": "OUT",
                "isFault": false,
                "name": "void"
              }
            ],
            "synchronicity": "ASYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "FIRE_AND_FORGET"
      },
      {
        "behaviour": [
          {
            "name": "Service behaviour ",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "This Service Interface exposes one operation for publishing the erroneous AFTN message information for FDO correction.",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the topic",
                "name": "topic://ccs.protobuf.flightDataDistribution.ErroneousFlightDataSubscriber.publishErroneousAFTNMessageData",
                "type": "TOPIC"
              }
            ],
            "name": "ErroneousFlightDataSubscriber"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "ErroneousFlightDataSubscriber",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "This operation sends the erroneous AFTN messages information for FDO correction.\r\n\r\nUpon reception of an AFTN erroneous message associated to a given SFPL, this message is referred to FDO.\r\n\r\nOnly the following AFTN messages are referred to FDO by CCS (the other are not yet within the scope of PJ16): ACH, APL, ARR, CHG, CNL, DEP, DLA, FPL, IACH, IAPL, IARR, ICHG, ICNL, IDEP, IDLA, IFPL.\r\nThe consumer can receive two other kinds of referred message: blocked and not checked.\r\nThe information referralType is used to differentiate an erroneous message referred for correction from a message \"blocked\" by FDM since an erroneous message for the same SFPL was already referred to FDO. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "publishErroneousAFTNMessageData",
            "operationMessage": [
              {
                "description": "Erroneous AFTN message.",
                "direction": "IN",
                "isFault": false,
                "name": "ErroneousAFTNMessage"
              },
              {
                "description": "Predefined void",
                "direction": "OUT",
                "isFault": false,
                "name": "void "
              }
            ],
            "precondition": "The consumer has to define off-line the priority for each kind of external message: \r\n-\t1: the message is referred.\r\n-\t0: the message is not referred.\r\n",
            "processingConsideration": [
              {
                "name": "message kind restriction",
                "description": "This publication concerns only AFTN messages: neither erroneous OLDI, nor erroneous manual input."
              },
              {
                "name": "each FDO message refers only to one error",
                "description": "Each FDO message refers only to one error of the AFTN message.\r\nIf an AFTN message contains several errors, the system sends a first referred message related to the first error. Then when this error is corrected by the FDO, the system sends, if any, a referred message for the next error.\r\n"
              },
              {
                "name": "external message priority",
                "description": "The consumer has to define off-line the priority for each kind of external message:\r\n   -\t1: the message is referred.\r\n   -\t0: the message is not referred.\r\n"
              },
              {
                "name": "erroneous message not associated to SFPL",
                "description": "According to the offline definition of FDO environment data, when an erroneous message cannot be associated to an existing SFPL, the referral to FDO may be replaced by the creation of an abbreviated flight plan, if at least the callsign is available (the resulting APL contains all data of the AFTN message except route and wake turbulence category)."
              },
              {
                "name": "ICAO field F22",
                "description": "The ICAO field F22 is not defined in PJ16, so it is not sent by CCS in the flightPlanInfo: the operator has to use the raw message for the CHG messages."
              },
              {
                "name": "ADESOLD field",
                "description": "The ADEXP field ADESOLD is applicable only to IACH, IAFP and IAPL messages."
              },
              {
                "name": "ADEXP fields with equivalent in ICAO F18",
                "description": "The ADEXP fields that have an equivalent field in ICAO F18 are sent via the field otherInformation."
              },
              {
                "name": "specificADEXPField parameter",
                "description": "CCS sends a technical parameter specificADEXPField containing ADEXP fields which have no equivalent in PJ16 and are not equivalent to other ICAO field."
              }
            ],
            "synchronicity": "ASYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "FIRE_AND_FORGET"
      },
      {
        "behaviour": [
          {
            "name": "Service behaviour  ",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "This Service Interface exposes the technical operation that allows the consumer to get the current flight plan data of all flights on request. It is typically used when starting the Service, for initialisation.",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataDistribution.FlightDataProvider.flightDataRepositoryRequest",
                "type": "QUEUE"
              }
            ],
            "name": "FlightDataProvider"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "FlightDataProvider",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "Allows a consumer to get the applicable flight plan data related to all relevant flights concerning this consumer.\r\nIn the request, the parameter oe allows to filter the flights to be received in  return (the criteria is fulfilled if oe is part of the list of  servedController.controller.identifier for the flight). If no oe is filled, no fliter is applied to the response (all flights known by the system are expected). The parameter wpId is ignored by CCS.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "flightDataRepositoryRequest",
            "operationMessage": [
              {
                "description": "Class supporting the request of the publication of the flight plan messages. It triggers their publication.",
                "direction": "IN",
                "isFault": false,
                "name": "FlightDataRepositoryRequest"
              },
              {
                "description": "Report returned by the service provider following a repository request.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataRequestReport"
              }
            ],
            "processingConsideration": [
              {
                "name": "FlightDataMessage sending",
                "description": "A FlightData message is sent for each flight, with the same content as if the operation publishFlightDataDistribution was triggered for all the flights, except that it is done through the FlightDataProvider interface. The whole set of messages (as many messages as flights) is sent within certain time tuned on provider’s platform (the time is constant whatever the number of flights).\r\nAmong the flights fulfilling the filter criteria of the request, the flights received are the ones existing at the time the request is performed. Following the sending of the request and before all the FlightData messages are received:\r\n-\tif a flight is deleted, no FlightData message is received (if not yet received before deletion of the flight)\r\n-\tif a flight is created, no FlightData message is received (the customer shall use the publishFlightDataDistribution message to be notified of this creation)\r\n-\tif a flight is updated, the FlightData message received includes this update\r\n\r\nThe FlightDataRequestReport is received after the last FlightData message has been received.                  \r\n\r\nIn case no data fulfills the criteria of a getxxx request, a OK_BUT response will be sent to the customer, with an error description message.       \r\n\r\nIn get/publish operations of other services regarding flights (operations of CORRD and MONAD services), no filtering is applied to flights. It is assumed that the Customer relies on publishFlightDataDistribution/flightDataRepositoryRequest filtering to determine if a flight is of interest for him or not.\r\nAs a consequence, a flight can be considered as relevant if a FlightData message has been received for this flight. Data received with the other services for any other flight could be ignored by the Customer.\r\nFollowing this principle, when a flightDataRepositoryRequest is performed, it is advisable for the Customer to wait for a complete response from it before sending any request for the other services regarding flights.\r\n"
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "behaviour": [
          {
            "name": "Service behaviour   ",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "This Service Interface exposes two technical operations that allows the consumer to get the erroneous AFTN message information for FDO correction, on request. It is typically used when starting the Service, for initialisation.",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataDistribution.ErroneousFlightDataProvider.getErroneousAFTNMessage",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataDistribution.ErroneousFlightDataProvider.getErroneousAFTNMessageSummary",
                "type": "QUEUE"
              }
            ],
            "name": "ErroneousFlightDataProvider"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "ErroneousFlightDataProvider",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "Allows a consumer to get the erroneous AFTN messages referred to FDO for manual correction, either for a specific erroneous message by filling the messageId, or all the erroneous messages if the messageId attribute is empty.\r\n\r\nRefer to publishErroneousAFTNMessageData description for more details about the list of errors that can be enc. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "getErroneousAFTNMessage",
            "operationMessage": [
              {
                "description": "Request for the publication of erroneous AFTN messages \r\nIt allows to obtain either a specific erroneous message by filling the messageId or the whole ErroneousAFTNMessages if the messageId attribute is empty.",
                "direction": "IN",
                "isFault": false,
                "name": "GetErroneousAFTNMessage"
              },
              {
                "description": "Publish erroneousAFTNMessages as a response of the operation requestErroneousAFTNMessage.",
                "direction": "OUT",
                "isFault": false,
                "name": "GetErroneousAFTNMessageReport"
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Allows a consumer to get the summary of erroneous AFTN messages referred to FDO for manual correction.\r\n\r\nRefer to publishErroneousAFTNMessageData description for more details about the list of errors that can be encountered\r\n. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "getErroneousAFTNMessageSummary",
            "operationMessage": [
              {
                "description": "Request for the publication of the erroneous AFTN messages summary.",
                "direction": "IN",
                "isFault": false,
                "name": "GetErroneousAFTNMessageSummary"
              },
              {
                "description": "Publish ErroneousAFTNMessagesSummary list as a response of the operation getErroneousAFTNMessageSummary",
                "direction": "OUT",
                "isFault": false,
                "name": "GetErroneousAFTNMessageSummaryReport"
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      }
    ],
    "version": "2.0.0"
  }
}