{ "informationService": { "descriptionInformation": { "abbreviations": [ { "name": "AC", "description": "Airspace Configuration" }, { "name": "ACC", "description": "Area Control Centre" }, { "name": "ADES", "description": "Aerodrome of Destination" }, { "name": "ADSP", "description": "ATM Data Service Provider" }, { "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": "AOR", "description": "Area Of Responsibility" }, { "name": "APL", "description": "Abbreviated Flight Plan" }, { "name": "APOC", "description": "Airport Operator" }, { "name": "ARES", "description": "Airspace Reservations" }, { "name": "ASD", "description": "Airspace Status Distribution" }, { "name": "ASM", "description": "Airspace Status Management" }, { "name": "ATC", "description": "Air Traffic Control" }, { "name": "ATCO", "description": "Air Traffic Control Officer" }, { "name": "ATCS", "description": "Air Traffic Control Services" }, { "name": "ATFCM", "description": "Air Traffic Flow and Capacity Management" }, { "name": "ATM", "description": "Air Traffic Management" }, { "name": "ATS", "description": "Air Traffic Services" }, { "name": "ATSU", "description": "Air Traffic Service Unit" }, { "name": "CCS", "description": "Coflight Cloud Services" }, { "name": "CDM", "description": "Collaborative Decision Making" }, { "name": "CDR", "description": "Conditional Route" }, { "name": "CFMU", "description": "Central Flow Management Unit" }, { "name": "CWP", "description": "Controller Working Position" }, { "name": "DCB", "description": "Demand and Capacity Balancing" }, { "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": "ENAV", "description": "Ente Nazionale Assistenza al Volo (Italian ANSP)" }, { "name": "FAB", "description": "Functional Airspace Block" }, { "name": "FABEC", "description": "Functional Airspace Block Europe Central" }, { "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": "GAT", "description": "General Air Traffic" }, { "name": "HMI", "description": "human machine Interface" }, { "name": "ICAO", "description": "International Civil Aviation Organization" }, { "name": "ID", "description": "Identifier" }, { "name": "IFR", "description": "Instrument Flight Rules" }, { "name": "IKE", "description": "Internet Key Exchange" }, { "name": "INAP", "description": "Integrated Network Management and ATC planning" }, { "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": "LTM", "description": "Local Traffic Manager" }, { "name": "MB", "description": "Mega byte" }, { "name": "MSA", "description": "Multi-sector area" }, { "name": "NOP", "description": "Network Operation Plan" }, { "name": "NTP", "description": "Network Time Protocol" }, { "name": "OCSP", "description": "Online Certificate Status Protocol" }, { "name": "OE", "description": "Operational Entity" }, { "name": "OPSUP", "description": "Operational Supervision" }, { "name": "PKCS", "description": "Public-Key Cryptography Standards" }, { "name": "SDD", "description": "Service Definition Document" }, { "name": "SESAR", "description": "Single European Sky Air Traffic Management Research" }, { "name": "SFPL", "description": "System Flight Plan" }, { "name": "SLA", "description": "Service Level Agreement" }, { "name": "SSD", "description": "SWIM Service Description" }, { "name": "SSI", "description": "Synchronous Serial Interface" }, { "name": "SWIM", "description": "System Wide Information Management" }, { "name": "TAD", "description": "Technical Architecture Description" }, { "name": "TBC", "description": "To Be Confirmed" }, { "name": "TBD", "description": "To Be Defined" }, { "name": "TCP", "description": "Transfer Control Protocol" }, { "name": "TDA", "description": "Temporary Danger Area" }, { "name": "TI", "description": "Technical Infrastructure" }, { "name": "TLS", "description": "transport level security" }, { "name": "TSA", "description": "Temporary Segregated Area" }, { "name": "UTC", "description": "Coordinated Universal Time" } ], "serviceDescriptionIdentification": { "serviceDescriptionTitle": "CCS Operational Configuration Management Service Description", "serviceDescriptionEdition": "5.2.2.5", "serviceDescriptionReferenceDate": "14/06/2022" } }, "name": "CCS OperationalConfigurationManagement", "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 OperationalConfigurationManagement service is consistent with the other CCS services.\r\nIt allows the ACC/Approach operational supervisor to manage the operational configuration in the ATSU by processing his input on the following on-line data:\r\n-\tthe mapping of control roles and responsibilities (control volume, ADES, set of runways,...) to Control Working Positions\r\n-\tAirspace status management (ARES/CDR activation...) \r\n-\tAirspace planning management (ARES/CDR timesheets) \r\n- \tAerodrome configuration management \r\n-\tRadioFrequency allocation plan management\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\nPlease note that the use of CCS OperationalConfigurationManagement Service implies the use of CCS OperationalConfigurationDistribution Service for sector mappings, aerodrome configuration and radio frequency allocation and of CCS AirspaceStatusDistribution Service for ARES/CDR.\r\n", "serviceCategorisation": { "serviceType": "SWIM_COMPLIANT", "lifeCycleStage": "OPERATIONAL", "businessActivityType": [ "INFORMATION_MANAGEMENT" ], "informationCategory": [ "FLIGHT_INFORMATION_EXCHANGE" ], "intendedConsumer": [ "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER" ], "applicationMessageExchangePattern": [ "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 Operational Configuration Management service payload", "documentType": "AIRM_TRACE", "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Operational+Configuration+Management+Service \nNote: to request access to Confluence, please refer to the point of contact section", "title": "CCS AIRM mapping OPSUPM service", "version": "1.0" }, { "description": "Validation evidence for CCS Operational Configuration Management service", "documentType": "SERVICE_VALIDATION_REPORT", "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Operational+Configuration+Management+Service \nNote: to request access to Confluence, please refer to the point of contact section", "title": "CCS Validation evidence document - OperationalConfigurationManagement", "version": "1.0" }, { "description": "Protobuf files describing the exchanged information", "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Operational+Configuration+Management+Service", "title": "CCS_operationalConfigurationManagement.proto", "version": "4.2.2.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+Operational+Configuration+Management+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+Operational+Configuration+Management+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+Operational+Configuration+Management+Service", "title": "CCS Operational Configuration Management Service Description", "version": "5.2.2.5" }, { "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 OperationalConfigurationManagement Service allows the ACC/Approach operational supervisor to manage the operational configuration in the ATSU by processing his input on the following on-line data:\r\n-\tthe mapping of control roles and responsibilities (control volume, ADES, set of runways,...) to Control Working Positions\r\n-\tAirspace status management (ARES/CDR activation...)\r\n-\tAirspace planning management (ARES/CDR timesheets)\r\n-\tAerodrome configuration management\r\n-\tRadioFrequency allocation plan management\r\n\r\n\r\n" } ], "functionality": [ { "name": "Update sector mapping", "description": "Update sector mapping", "realWorldEffect": "Change the operational configuration of the ATSU" }, { "name": "Activate sector mapping", "description": "Activate sector mapping", "realWorldEffect": "Change the current operational configuration of the ATSU (using a next or an off-line pre-defined sector mapping)" }, { "name": "Update ARES activation status", "description": "Update ARES activation status", "realWorldEffect": "Change and lock the activation status of the ARES" }, { "name": "Unlock ARES activation status", "description": "Unlock ARES activation status", "realWorldEffect": "Unlock a previous manual ARES activation status: the activation status of the ARES is unlocked and automatically updated by the system from ARES timesheets, information off-line defined and information issued from the CFMU." }, { "name": "Update CDR activation status", "description": "Update CDR activation status", "realWorldEffect": "Change and lock the status of the CDR to open or closed." }, { "name": "Unlock CDR activation status", "description": "Unlock CDR activation status", "realWorldEffect": "Unlock a previous manual CDR status: the status of the CDR is unlocked and automatically updated by the system from CDR timesheets, information off-line defined and information issued from the CFMU." }, { "name": "Delete next sector mapping", "description": "Delete next sector mapping", "realWorldEffect": "Delete the next operational configuration of the ATSU, if any" }, { "name": "Load next sector mapping", "description": "Load next sector mapping", "realWorldEffect": "Change the next operational configuration of the ATSU (using an off-line pre-defined sector mapping)" }, { "name": "Create CDR timesheet", "description": "Create CDR timesheet", "realWorldEffect": "Add a timesheet to a CDR" }, { "name": "Delete ARES timesheet", "description": "Delete ARES timesheet", "realWorldEffect": "Remove an existing activation periods timesheet from an ARES timetable" }, { "name": "Delete CDR timesheet", "description": "Delete CDR timesheet", "realWorldEffect": "Remove an existing timesheet from a CDR" }, { "name": "Update ARES timesheet", "description": "Update ARES timesheet", "realWorldEffect": "Update an existing activation periods timesheet for an ARES" }, { "name": "Update CDR timesheet", "description": "Update CDR timesheet", "realWorldEffect": "Update an existing CDR timesheet" }, { "name": "Add a comment for an ARES", "description": "Add a comment for an ARES", "realWorldEffect": "Define a comment for an ARES" }, { "name": "Modify aerodrome runway configuration", "description": "Modify aerodrome runway configuration", "realWorldEffect": "Modify the current configuration of the runways for an aerodrome of a given Aerodrome Group" }, { "name": "Update radio frequency allocation for a responsibility", "description": "Update radio frequency allocation for a responsibility", "realWorldEffect": "Modify the radio frequency assigned to control responsibility(ies), either by selecting a new radio frequency, or by reverting back to the predefined value" }, { "name": "Planify the next aerodrome group configuration", "description": "Planify the next aerodrome group configuration", "realWorldEffect": "For a given aerodrome group, save a predefined configuration as the next one, together with a planned activation time " }, { "name": "Modify aerodrome configuration", "description": "Modify aerodrome configuration", "realWorldEffect": "For a given aerodrome, modify the configuration parameters" }, { "name": "Delete a next aerodrome group configuration", "description": "Delete a next aerodrome group configuration", "realWorldEffect": "For a given aerodrome group, remove the next configuration" }, { "name": "Activate a new aerodrome group configuration", "description": "Activate a new aerodrome group configuration", "realWorldEffect": "For a given aerodrome group, make as the current configuration, either the one identified as the next one, or another predefined one" }, { "name": "Update radio frequency allocation for all the responsibilities of the ATSU", "description": "Update radio frequency allocation for all the responsibilities of the ATSU", "realWorldEffect": "Change the current radio frequency allocation, either by selecting a new radio frequency allocation plan, or by reverting back to the predefined default radio frequency configuration" }, { "name": "Create ARES timesheet", "description": "Create ARES timesheet", "realWorldEffect": "Add a timesheet into an ARES timetable to define new activation periods" } ], "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" } ], "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": "modifyRunwayConfiguration Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "activateAerodromeGroupConfiguration Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "deleteNextAerodromeGroupConfiguration Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "modifyAerodromeConfiguration Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "planifyNextAerodromeGroupConfiguration Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "createARESTimesheet Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "createCDRTimesheet Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "deleteARESTimesheet Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "deleteCDRTimesheet Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateARESTimesheet Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateCDRTimesheet Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "unlockARESActivationStatus Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateARESActivationStatus Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "unlockCDRStatus Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateCDRStatus Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "addARESComment Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateFrequency Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateFrequencyPlan Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "activateSectorMapping Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "updateSectorMapping Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "loadNextSectorMapping Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.2", "schemaLanguage": "Protocol buffer" }, { "name": "deleteSectorMapping Exchange schema", "reference": "CCS_operationalConfigurationManagement.proto 4.2.2.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 are supervised in real time by trained and licensed ATSEPS. \r\n\r\nA dedicated service to supervise the complete CCS swim services portfolio is available to the customer.\r\nFor more information, please refer to the swim service description of the CCS technical supervision distribution service\r\n" }, "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 should use, each of them, at least one NTP server (stratum N), integrated in a NTP network containing a stratum 0 reference time clock.\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 defined for each 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 operations used by the Operational Supervisor to modify the Aerodrome Configuration Data.", "endPoint": [ { "address": "For security reasons, the addresses will be communicated only to Customers", "addressableResource": [ { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AerodromeConfigurationManagementProvider.modifyRunwayConfiguration", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AerodromeConfigurationManagementProvider.activateAerodromeGroupConfiguration", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AerodromeConfigurationManagementProvider.deleteNextAerodromeGroupConfiguration", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AerodromeConfigurationManagementProvider.modifyAerodromeConfiguration", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AerodromeConfigurationManagementProvider.planifyNextAerodromeGroupConfiguration", "type": "QUEUE" } ], "name": "AerodromeConfigurationManagementProvider" } ], "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": "AerodromeConfigurationManagementProvider", "networkInterfaceBinding": "IPV4_SECURE_UNICAST", "operation": [ { "description": "Allows to modify the current configuration of the runways for an aerodrome of a given Aerodrome Group.\r\nThis operation enables an eligible user (normally a supervisor) to modify the following data of a given runway or of the runway(s) of an aerodrome: landing and/or take-off rates, IAP in operation and operating mode (open or closed).\r\nIt is also possible to revert to default rate values of runway(s) if no rate value is provided in the operation.. ", "idempotency": "NON_IDEMPOTENT", "name": "modifyRunwayConfiguration", "operationMessage": [ { "description": "Message definition for the operation of the same name.", "direction": "IN", "isFault": false, "name": "ModifyRunwayConfiguration" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse" } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful:\r\n- the current configuration of the aerodrome group concerned by these runway(s) modifications is updated and published using the Operational Configuration Distribution Service for display in the Controller and Operational Supervisor HMIs if required.\r\n- the updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." }, { "name": "runwayName parameter", "description": "When the aim of this operation is to :\r\n-\tmodify data for all the runways of the aerodrome group, runwayName should not be filled\r\n-\tmodify data for one specific runway, runwayName should be filled with the name of the runway involved\r\n" }, { "name": "inOperationIAP and iaf parameters", "description": "When modifying data for a specific runway, parameters inOperationIAP and iaf could be filled to update the IAP in operation. In this case, both should be filled.\r\nWhen modifying data for all the runways, neither inOperationIAP nor iaf should be filled.\r\n" } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows replacing the current Aerodrome Group Configuration with another given aerodrome group configuration.\r\nThe user may activate an offline predefined aerodrome group configuration, activate the one previously defined as the Next one or revert back to the default one.\r\n\r\nWhen the aim of this operation is to :\r\n-\tactivate an offline predefined aerodrome group configuration, aerodromeGroupConfigName should be filled with the name of the configuration,\r\n-\tactivate the next aerodrome group configuration, aerodromeGroupConfigName should not be filled,\r\n-\trevert back to the default aerodrome group configuration, aerodromeGroupConfigName should not be filled and aerodromeConfigurationOrigin should be DEFAULT.\r\n. ", "idempotency": "NON_IDEMPOTENT", "name": "activateAerodromeGroupConfiguration", "operationMessage": [ { "description": "Message definition for the operation of the same name.", "direction": "IN", "isFault": false, "name": "ActivateAerodromeGroupConfiguration" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful:\r\n- the updated aerodrome configuration is published using the Operational Configuration Distribution Service for display in the Controller and Operational Supervisor HMIs if required. In the last 2 cases (activation of the next aerodrome group configuration or revert back to the default one), the next configuration and its planned activation time if any are resetted.\r\n- the updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows removing the fact that an aerodrome group configuration is identified as the next one.. ", "idempotency": "NON_IDEMPOTENT", "name": "deleteNextAerodromeGroupConfiguration", "operationMessage": [ { "description": "Message definition for the operation of the same name.", "direction": "IN", "isFault": false, "name": "DeleteNextAerodromeGroupConfiguration" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the updated aerodrome configuration is published using the Operational Configuration Distribution Service for display in the Controller and Operational Supervisor HMIs if required." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows modifying the configuration parameters of an aerodrome.\r\n\r\nThe 3 possibilities given by this operation are :\r\n-\trevert to default the aerodrome Altitude Correction\r\n-\trevert to default the aerodrome Transition Level. In this case, defaultAltitudeCorrection should be set to FALSE\r\n-\tmodify one or several of the following parameters : transitionLevel, altitudeCorrection, modeSCapabilityState. In this case, revertToDefault should not be filled\r\n\r\naerodromeGroup is ignored by CCS.. ", "idempotency": "NON_IDEMPOTENT", "name": "modifyAerodromeConfiguration", "operationMessage": [ { "description": "Message definition for the operation of the same name.\r\nIf revertToDefault is filled, transitionLevel, altitudeCorrection and modeSCapabilityState are ignored by CCS.", "direction": "IN", "isFault": false, "name": "ModifyAerodromeConfiguration" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful:\r\n-\tthe updated aerodrome configuration is published using the Operational Configuration Distribution Service for display in the Controller and Operational Supervisor HMIs if required.\r\n-\tthe updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs.\r\n" } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows changing the next configuration to be applied for an aerodrome group by selecting another aerodrome configuration from a predefined configuration list, and/or to change the date and time that the configuration is planned to be activated.\r\n. ", "idempotency": "NON_IDEMPOTENT", "name": "planifyNextAerodromeGroupConfiguration", "operationMessage": [ { "description": "Message definition for the operation of the same name.", "direction": "IN", "isFault": false, "name": "PlanifyNextAerodromeGroupConfiguration" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the updated aerodrome configuration is published using the Operational Configuration Distribution Service for display in the Controller and Operational Supervisor HMIs if required.\r\n\r\n" }, { "name": "No automatic processing for the activation of this next configuration", "description": "no automatic processing is applied for the activation of this next configuration." } ], "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 operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Planning data.", "endPoint": [ { "address": "For security reasons, the addresses will be communicated only to Customers", "addressableResource": [ { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspacePlanningManagementProvider.createARESTimesheet", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspacePlanningManagementProvider.createCDRTimesheet", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspacePlanningManagementProvider.deleteARESTimesheet", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspacePlanningManagementProvider.deleteCDRTimesheet", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspacePlanningManagementProvider.updateARESTimesheet", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspacePlanningManagementProvider.updateCDRTimesheet", "type": "QUEUE" } ], "name": "AirspacePlanningManagementProvider" } ], "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": "AirspacePlanningManagementProvider", "networkInterfaceBinding": "IPV4_SECURE_UNICAST", "operation": [ { "description": "Allows to add a timesheet into an ARES timetable to define new activation periods.\r\nThe input parameters shall be the originator, the ARES name and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity.. ", "idempotency": "NON_IDEMPOTENT", "name": "createARESTimesheet", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "CreateARESTimesheet" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "CFMU timesheets", "description": "Manually created ARES timesheets are not updated by the reception of ARES timesheets from CFMU (the reception of ARES timesheets in an e-AMI message leads to the replacement of all the automatic ARES timesheets of the timetable with the received ARES timesheets)." }, { "name": "Successful request", "description": "If the request is successful and if or as soon as the ARES activation status is unlocked, the ARES activation status is automatically updated by the system from the ARES timetable.\r\nThe ARES modifications are published using the AirspacePlanningSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs." }, { "name": "Unsuccessful request", "description": "The operation is rejected if:\r\n-\tthe operation would result in the intersection of the new timesheet with existing one(s)\r\n-\tthe operation is performed while 5 timesheets already exist (a maximum of 5 timesheets is allowed by the system for an ARES)" }, { "name": "end of activation period in the past", "description": "If the end of the activation period given in the input is in the past, the input is accepted but no timesheet is created." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows to add a timesheet to a CDR.\r\nThe input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the timesheet data containing an activation time period, and optionally the activation levels and/or a periodicity.. ", "idempotency": "NON_IDEMPOTENT", "name": "createCDRTimesheet", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "CreateCDRTimesheet" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "precondition": "The consumer has pre-defined (off-line) all his CDRs as portion of airways.", "processingConsideration": [ { "name": "CFMU timesheets", "description": "Manually created CDR timesheets are not updated by the reception of CDR timesheets from CFMU (the reception of CDR timesheets in an e-AMI message leads to the replacement of all the automatic CDR timesheets of the timetable with the received CDR timesheets)." }, { "name": "Unsuccessful request", "description": "Note: the operation is rejected if:\r\n-\tthe operation is performed while 5 non-predefined timesheets already exist (a maximum of 5 non-predefined timesheets is allowed by the system for an CDR)\r\n" }, { "name": "Successful request", "description": "If the request is successful and if or as soon as the CDR activation status is unlocked, the CDR activation status is automatically updated by the system from the CDR timetable.\r\nThe CDR modifications are published using the AirspacePlanningSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs. \r\nFollowing these modifications of CDR environment data, the expanded route of the concerned SFPL can be modified if an alternative route is eligible for automatic insertion (depending on dataset). If several alternative routes are eligible, the shorter one is inserted. The updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." }, { "name": "end of activation period in the past", "description": "If the end of the activation period given in the input is in the past, the input is accepted but no timesheet is created." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows to remove an existing activation periods timesheet from an ARES timetable.\r\nThe input parameters shall be the originator, the ARES name and the identifier of the timesheet to remove.. ", "idempotency": "NON_IDEMPOTENT", "name": "deleteARESTimesheet", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "DeleteARESTimesheet" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the ARES timesheet is removed, but no publication is made. The OK response to the request has to be taken account by the customer to know that the timesheet has been actually removed." }, { "name": "End time for timesheets without periodicity", "description": "Iin case the end time of a timesheet is reached, and it doesn\u0027t include a periodicity, it is automatically removed, and no publication is sent. In this case, the customer should rely on the end time parameter to determine when the timesheet is actually removed." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows to remove an existing activation periods timesheet from a CDR timetable.\r\nThe input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the identifier of the timesheet to remove.. ", "idempotency": "NON_IDEMPOTENT", "name": "deleteCDRTimesheet", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "DeleteCDRTimesheet" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "precondition": "The consumer has pre-defined (off-line) all his CDRs as portion of airways.", "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the CDR timesheet is removed, but no publication is made. The OK response to the request has to be taken account by the customer to know that the timesheet has been actually removed. \r\nFollowing these modifications of CDR environment data, the expanded route of the concerned SFPL can be modified if an alternative route is eligible for automatic insertion (depending on dataset). If several alternative routes are eligible, the shorter one is inserted. The updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." }, { "name": "End time for timesheets without periodicity", "description": "In case the end time of a timesheet is reached, and it doesn\u0027t include a periodicity, it is automatically removed, and no publication is sent. In this case, the customer should rely on the end time parameter to determine when the timesheet is actually removed." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows to update an existing activation periods timesheet for an ARES.\r\nThe input parameters shall be the originator, the ARES name, the identifier of the timesheet to update and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity.. ", "idempotency": "NON_IDEMPOTENT", "name": "updateARESTimesheet", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "UpdateARESTimesheet" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "CFMU timesheets", "description": "Manually created ARES timesheets are not updated by the reception of ARES timesheets from CFMU (the reception of ARES timesheets in an e-AMI message leads to the replacement of all the automatic ARES timesheets of the timetable with the received ARES timesheets)." }, { "name": "Unsuccessful request", "description": "The operation is rejected if:\r\n-\tthe operation would result in the intersection of the new timesheet with existing one(s)\r\n" }, { "name": "Successful request", "description": "If the request is successful and if or as soon as the ARES activation status is unlocked, the ARES activation status is automatically updated by the system from the ARES timetable.\r\nThe ARES modifications are published using the AirspacePlanningSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows to update an existing CDR timesheet.\r\nThe input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR), the identifier of the timesheet to update and the timesheet data containing an activation time period, and optionally the activation levels and/or periodicity.. ", "idempotency": "NON_IDEMPOTENT", "name": "updateCDRTimesheet", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "UpdateCDRTimesheet" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "precondition": "The consumer has pre-defined (off-line) all his CDRs as portion of airways.", "processingConsideration": [ { "name": "Predefined timesheet modification", "description": "Predefined timesheet are not modifiable on line." }, { "name": "CFMU timesheets", "description": "Manually created CDR timesheets are not updated by the reception of CDR timesheets from CFMU (the reception of CDR timesheets in an e-AMI message leads to the replacement of all the automatic CDR timesheets of the timetable with the received CDR timesheets)." }, { "name": "Successful request", "description": "If the request is successful and if or as soon as the CDR activation status is unlocked, the CDR activation status is automatically updated by the system from the CDR timetable.\r\nThe CDR modifications are published using the AirspacePlanningSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs. \r\n\r\nFollowing these modifications of CDR environment data, the expanded route of the concerned SFPL can be modified if an alternative route is eligible for automatic insertion (depending on dataset). If several alternative routes are eligible, the shorter one is inserted. The updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs.\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 operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Status data.", "endPoint": [ { "address": "For security reasons, the addresses will be communicated only to Customers", "addressableResource": [ { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspaceStatusManagementProvider.unlockARESActivationStatus", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspaceStatusManagementProvider.updateARESActivationStatus", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspaceStatusManagementProvider.unlockCDRStatus", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspaceStatusManagementProvider.updateCDRStatus", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.AirspaceStatusManagementProvider.addARESComment", "type": "QUEUE" } ], "name": "AirspaceStatusManagementProvider" } ], "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": "AirspaceStatusManagementProvider", "networkInterfaceBinding": "IPV4_SECURE_UNICAST", "operation": [ { "description": "Enables to unlock a previous manual ARES activation status.\r\nThe input parameters shall be the originator and the ARES name. . ", "idempotency": "NON_IDEMPOTENT", "name": "unlockARESActivationStatus", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "UnlockARESActivationStatus" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the ARES activation status is unlocked and automatically updated by the system from information off-line defined (ARES timesheets...) and issued from the CFMU.\r\nThe ARES modifications are published using the AirspaceStatusSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs. \r\nIf SFPL are meant to be updated by ARES activation (choice to be made in dataset), the updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs.\r\n" } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Enables to update the following ARES data:\r\n- the status (activated or deactivated),\r\n- the comment associated to the ARES.\r\n\r\nThe input parameters shall be the originator, the ARES name and the ARES status.. ", "idempotency": "NON_IDEMPOTENT", "name": "updateARESActivationStatus", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "UpdateARESActivationStatus" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the ARES status is updated (activated or deactivated) and locked. It is no longer automatically updated by the system until the supervisor releases it. \r\n\r\nThe ARES modifications are published using the AirspaceStatusSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs.\r\n" }, { "name": "CCS limitation", "description": "For information, following these modifications of ARES environment data Coflight computes the intersection between flight trajectories and ARES volumes in order to propose a TSA avoidance route for the concerned SFPLs. Then this avoidance route can be inserted manually in the route by the operator. However this behaviour (SFPL update) and this FDM operation are not implemented in CCS (according to PJ16 FDM and FDD definitions)." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Enables to unlock a previous manual CDR status.\r\nThe input parameters shall be the originator and the CDR identifier (airway name and names of the start and last points of the CDR).. ", "idempotency": "NON_IDEMPOTENT", "name": "unlockCDRStatus", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "UnlockCDRStatus" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "precondition": "The consumer has pre-defined (off-line) all his CDRs as portion of airways.", "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the CDR status is unlocked and it is defined in the CDR timetable (the system computes CDR data from manual CDR timesheets, information off-line defined and information issued from the CFMU).\r\nThe CDR modifications are published using the AirspaceStatusSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs. \r\n\r\nIf SFPL are meant to be updated by CDR activation (choice to be made in dataset), the updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Enables to lock the CDR status to open or closed.\r\nThe input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the CDR status.. ", "idempotency": "NON_IDEMPOTENT", "name": "updateCDRStatus", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "UpdateCDRStatus" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "precondition": "The consumer has pre-defined (off-line) all his CDRs as portion of airways.", "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the CDR status is updated (open or closed) and it is locked until the supervisor releases it. When the CDR status is unlocked, it is defined in the CDR timetable.\r\nThe CDR modifications are published using the AirspaceStatusSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs.\r\nFollowing these modifications of CDR environment data, the expanded route of the concerned SFPL can be modified if an alternative route is eligible for automatic insertion (depending on dataset). If several alternative routes are eligible, the shorter one is inserted. The updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows to define, update or remove a comment to a given ARES.. ", "idempotency": "NON_IDEMPOTENT", "name": "addARESComment", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "AddARESComment" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "comment parameter", "description": "If the comment attribute is :\r\n-\tfilled but empty, the current ARES comment will be removed\r\n-\tfilled with at least 1 character, this new comment will be applied to the ARES." }, { "name": "Successful request", "description": "If the request is successful, the ARES modifications are published using the AirspaceStatusDistribution Service in order to be displayed in the Controller and Operational Supervisor HMIs." } ], "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 operations used by the Operational Supervisor to modify the Radio Frequency Allocation.", "endPoint": [ { "address": "For security reasons, the addresses will be communicated only to Customers", "addressableResource": [ { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.RadioFrequencyAllocationManagementProvider.updateFrequency", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.RadioFrequencyAllocationManagementProvider.updateFrequencyPlan", "type": "QUEUE" } ], "name": "RadioFrequencyAllocationManagementProvider" } ], "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": "RadioFrequencyAllocationManagementProvider", "networkInterfaceBinding": "IPV4_SECURE_UNICAST", "operation": [ { "description": "Allows a consumer to modify the radio frequency assigned to control responsibility(ies):\r\n-\teither by selecting a new radio frequency,\r\n-\tor by reverting back to the predefined value (off-line defined) of the radio frequency assigned to the given control responsibility (if it has been on-line updated before).\r\n\r\nThe input parameters shall be:\r\n-\tthe value of the new radio frequency and the controlResponsibility(ies) where the indicated frequency shall be assigned,\r\n-\tor the controlResponsibility(ies) where the default frequency shall be assigned.\r\n\r\nWhen the aim of this operation is to :\r\n-\tapply a new frequency to one or several Responsibilities, frequency should be filled\r\n-\trevert to default frequency for one or several Responsibilities, revertToDefaultFreq should be set to TRUE and frequency shouldn\u0027t be filled\r\n. ", "idempotency": "NON_IDEMPOTENT", "name": "updateFrequency", "operationMessage": [ { "description": "Message definition for the operation of the same name.\r\nIf revertToDefaultFreq is set to FALSE or not filled, frequency should be filled", "direction": "IN", "isFault": false, "name": "UpdateFrequency" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "system checks", "description": "When modifying data for a specific runway, parameters inOperationIAP and iaf could be filled to update the IAP in operation. In this case, both should be filled.\r\nWhen modifying data for all the runways, neither inOperationIAP nor iaf should be filled.\r\n" }, { "name": "Successful request", "description": "For each modification request, the system shall check that: \r\n-\tevery radio frequency belongs to the predefined list of radio frequencies available for the allocation,\r\n-\tevery responsibility belongs to the predefined list of responsibilities requiring radio frequency allocation,\r\n-\tevery responsibility defined in the current radio frequencies allocation plan has one and only one associated radio frequency.\r\n" } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Allows a consumer to change the current radio frequency allocation:\r\n-\teither by selecting a new radio frequency allocation plan among the predefined radio frequency configurations,\r\n-\tor by reverting back to the predefined default radio frequency configuration (offline defined). \r\n\r\nThe input parameters shall be:\r\n-\tthe name of the requested ATSUSectorConfiguration,\r\n-\tand the name of the radio frequency configuration to load in place of the current one (except on the operation of reverting back to the default one: in this case this is the default radio frequency configuration which will be loaded).\r\n\r\nWhen the aim of this operation is to :\r\n-\tapply a new plan to an ASTUSectorConfiguration, radioFrequencyAllocationName should be filled\r\n-\trevert to default frequency plan an ASTUSectorConfiguration, revertToDefaultPlan should be set to TRUE and radioFrequencyAllocationName shouldn\u0027t be filled\r\n. ", "idempotency": "NON_IDEMPOTENT", "name": "updateFrequencyPlan", "operationMessage": [ { "description": "Message definition for the operation of the same name.\r\n\r\nIf revertToDefaultPlan is set to FALSE or not filled, radioFrequencyAllocation should be filled", "direction": "IN", "isFault": false, "name": "UpdateFrequencyPlan" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "system checks", "description": "For each modification request, the system shall check that : \r\n-\tevery radio frequency belongs to the predefined list of radio frequencies available for the allocation,\r\n-\tevery responsibility belongs to the predefined list of responsibilities requiring radio frequency allocation,\r\n-\tevery responsibility defined in the current radio frequencies allocation plan has one and only one associated radio frequency.\r\n" }, { "name": "Successful request", "description": "If the request is successful, the new radio frequency configuration plan is published using the OperationalConfigurationDistribution Service in order to be displayed in the Controller and Operational Supervisor HMIs." } ], "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 operations used by the Operational Supervisor to modify the Sector Configuration Data.", "endPoint": [ { "address": "For security reasons, the addresses will be communicated only to Customers", "addressableResource": [ { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.SectorConfigurationManagementProvider.activateSectorMapping", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.SectorConfigurationManagementProvider.updateSectorMapping", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.SectorConfigurationManagementProvider.loadNextSectorMapping", "type": "QUEUE" }, { "description": "Name of the queue", "name": "queue://ccs.protobuf.operationalConfigurationManagement.SectorConfigurationManagementProvider.deleteSectorMapping", "type": "QUEUE" } ], "name": "SectorConfigurationManagementProvider" } ], "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": "SectorConfigurationManagementProvider", "networkInterfaceBinding": "IPV4_SECURE_UNICAST", "operation": [ { "description": "Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.\r\nThe supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping. \r\nAs a consequence, the parameter sectorMappingId is MANDATORY when the parameter revertToDefaultMapping is not filled or set to FALSE (but if revertToDefaultMapping is set to YES, sectorMappingId is not needed).. ", "idempotency": "NON_IDEMPOTENT", "name": "activateSectorMapping", "operationMessage": [ { "description": "Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.\r\nThe supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping.\r\nIf the request is successful, the new current mapping is published using the SectorConfigurationSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs.\r\nWhen applying a new current mapping, loaded from the next mapping, then the next mapping becomes current and the former \"current\" mapping is deleted.\r\n\r\nNote:The cardinality of the parameter sectorMappingId is optional, because the operation \"ActivateSectorMapping\" covers also the case of reverting back to default mapping. Indeed, when the parameter revertToDefaultMapping is not filled or set to FALSE, then sectorMappingId is mandatory. If the supervisor chooses to revert back to the default mapping, this field is unused.", "direction": "IN", "isFault": false, "name": "ActivateSectorMapping" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the new current mapping is published using the SectorConfigurationSubscriber Service Interface in order to be displayed in the Controller and Operational Supervisor HMIs. \r\nThe updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs." }, { "name": "current mapping loaded from next mapping", "description": "When applying a new current mapping, loaded from the next mapping, the next mapping is then deleted." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration.. ", "idempotency": "NON_IDEMPOTENT", "name": "updateSectorMapping", "operationMessage": [ { "description": "Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration.\r\nThe input parameters shall be at least the identifier of the ATSUSectorConfiguration, the name and the state of the sectorMapping and the sectorMapping content. \r\nIf the request is successful, the new mapping is published using the Operational Configuration Distribution Service in order to be displayed in the Controller and Operational Supervisor HMIs.\r\nWhen the supervisor updates a sector mapping and fixes its defaultCommunicationResponsibility:\r\n-some mapping checks and restriction when entering the fields prevent from possible inconsistencies,\r\n-the CCS system allocate dynamically the frequencies to each logical CWP according to the Role/Responsibilites (e.g. Sectors for Tactical ATCO) mapped on it.\r\nthe radio frequency allocation plan is unchanged.\r\n\r\nNote:The cardinality of the parameter sectorMappingId for the UpdateSectorMapping operation is mandatory. Cfr ActivateSectorMapping operation description", "direction": "IN", "isFault": false, "name": "UpdateSectorMapping" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "sectorMappingId parameter", "description": "The parameter sectorMappingId is operationally MANDATORY for this operation (the reason that it is defined as optional in the parameters table is because it is common with the operation ActiveSectorMapping (cf. ActivateSectorMapping operation description))." }, { "name": "allocatedRole and allocatedResponsibility parameters", "description": "allocatedRole and allocatedResponsibility must be provided together. If one of these fields is provided, the consumer must also provide the other field. If not, the system will not be able to determine the corresponding operational entity." }, { "name": "Successful request", "description": "If the request is successful, the new mapping is published using the Operational Configuration Distribution Service in order to be displayed in the Controller and Operational Supervisor HMIs. \r\n\r\nThe updated SFPL taking into account the modification are published using the Flight Data Distribution Service in order to be displayed in the Controller HMIs" }, { "name": "sector mapping update with defaultCommunicationResponsibility", "description": "When the supervisor updates a sector mapping and fixes its defaultCommunicationResponsibility:\r\n-\tsome mapping checks and restriction when entering the fields prevent from possible inconsistencies,\r\n-\tthe CCS system allocates dynamically the frequencies to each logical CWP according to the Role/Responsibilites (e.g. Sectors for Tactical ATCO) mapped on it.\r\n- the radio frequency allocation plan is unchanged." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Enables to load a pre-defined mapping as being the next mapping of a given ASTUSectorConfiguration.\r\n\r\nThe input parameters shall be:\r\n-\tthe ATSUSectorConfigurationIdentifier,\r\n-\tthe identifier of the sectorMapping.\r\n. ", "idempotency": "NON_IDEMPOTENT", "name": "loadNextSectorMapping", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "LoadNextSectorMapping" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the new next SectorMapping is published using the OperationalConfigurationDistribution Service in order to be displayed in the Controller and Operational Supervisor HMIs." }, { "name": "next and predefined mapping update", "description": "The previous \"next\" mapping is deleted and the predefined mapping loaded as the next one, is duplicated (not deleted)." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] }, { "description": "Enables to delete a given sector mapping. Only the next sector mapping can be deleted.\r\nThe input parameter is the identifier of the concerned ATSUSectorConfiguration (sufficient to delete a next mapping knowing that only one next sector mapping per ATSUSectorConfiguration).\r\n. ", "idempotency": "NON_IDEMPOTENT", "name": "deleteSectorMapping", "operationMessage": [ { "description": "Message definition for the operation of the same name", "direction": "IN", "isFault": false, "name": "DeleteSectorMapping" }, { "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.", "direction": "OUT", "isFault": false, "name": "OperationalConfigurationResponse " } ], "processingConsideration": [ { "name": "Successful request", "description": "If the request is successful, the given SectorMapping is deleted from the ATSUSectorConfiguration, but no publication is made. The OK response to the request has to be taken account by the customer to know that the sector mapping has been actually removed. No publication is made since the updated mapping (the next sector mapping) does not exist anymore." } ], "synchronicity": "SYNCHRONOUS", "tiProtocolMethod": [ "transfer" ] } ], "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING", "tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE" } ], "version": "2.0.0" } }