{ "informationService": { "serviceAbstract": "This SWIM Service addresses the manual interactions between the 4-Flight ATM Data Service Provider (ADSP) and the CWP in the context of Virtual Centre, for managing SSR code assignment.\r\nNormally, to reduce controller workload, the assignment and release processes are triggered automatically by a timer or event. However, if the automatic process fails, operations are provided for controllers and other authorised users, to manually request the assignment or release of a code to eligible flights\r\nThe CWP will receive a reply when the service request has been completed, indicating the status of the request.\r\nIf the request is successful, the SSR code assigned to the segment is updated.\r\nPlease note that the use of theDSNA SSRCodeManagement service implies the use of FlightDataDistribution Service to get the output SSR code information in the updated Flight Plan.\r\n", "serviceProvider": { "provider": "Direction des Services de la Navigation Aerienne", "abbreviation": "DSNA", "providerDescription": "DSNA is the national air navigation services provider of France.\r\nDSNA 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\nCore 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": [ "PROVIDER_OF_DATA_SERVICES" ], "pointOfContact": [ { "name": "DSNA FlightData Services Customer Relations", "contactInformation": [ { "type": "EMAIL", "address": "bertrand.morvan@aviation-civile.gouv.fr" } ], "role": "To request information about this service" } ] }, "serviceCategorisation": { "serviceType": "SWIM_COMPLIANT", "lifeCycle": [ { "lifeCycleStage": "PROSPECTIVE", "from": "2026-06-01", "to": "2027-02-09" }, { "lifeCycleStage": "OPERATIONAL", "from": "2027-02-09" } ], "businessActivityType": ["INFORMATION_MANAGEMENT"], "intendedConsumer": [ "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER", "AIR_TRAFFIC_SERVICE_PROVIDER", "CIVIL_AIRSPACE_USER", "PROVIDER_OF_DATA_SERVICES" ], "informationCategory": [ "FLIGHT_INFORMATION_EXCHANGE" ], "applicationMessageExchangePattern": [ { "name": "SYNCHRONOUS_REQUEST_REPLY"} ], "geospatialCategorisation": { "countryCode": [ "LF" ] }, "other": [ { "name": "Service Type: FLIGHT_INFORMATION_FEATURE_MANAGEMENT_SERVICE", "value": "FLIGHT_FEATURE_MANAGEMENT_SERVICE" } ] }, "generalDescription": { "operationalEnvironment": { "operationalNeeds": [ { "name": "SSR Code management", "description": "he SSRCodeManagement Service addresses the assignment of SSR codes to eligible flights and release of SSR codes assigned to flights.\r\nIt addresses operations related to:\r\n- SSR code assignment request,\r\n- SSR code release.\r\n" } ] }, "functionality": [ { "name": "Request SSR Code", "description": "To request an assigned SSRCode for a flight", "realWorldEffect": "To manually assign a SSRCode given in the input, or to request an automatic SSRCode assignment." }, { "name": "Release SSR Code", "description": "To release an SSRCode assigned to a flight", "realWorldEffect": "To manually release an assigned SSRCode that is not used for correlation purpose, in order to make this code available again." } ], "accessAndUseConditions": [ { "name": "Subscription", "description": "Consumers needs to contact DSNA to register administratively to this service.", "type": "SERVICE_CONSUMPTION_CONSTRAINT" }, { "name": "Aviation users", "description": "Only service consumers within the aviation domain can use this service.", "type": "SERVICE_POLICY" }, { "name": "Non aviation users", "description": "The service consumers cannot pass the information obtained from the service to non-aviation users without prior authorisation from DSNA.", "type": "SERVICE_POLICY" }, { "name": "Dependencies with DSNA Services", "description": "If the service consumer also consumes other DSNA services, this Service shall be consumed simultaneously with the other DSNA SWIM Services that are part of the contractual agreement between the service consumer and DSNA service provider.", "type": "SERVICE_CONSUMPTION_CONSTRAINT" }, { "name": "Dependency with FDD DSNA Service", "description": "The use of this SSRCodeManagement service implies the use of the FlightDataDistribution DSNA Service to get the output Flight Plan Data.", "type": "SERVICE_CONSUMPTION_CONSTRAINT" }, { "name": "Service versioning", "description": "At least 2 versions of this swim service could be maintained in the same time, taking benefit the capacities of technologies used in DSNA such as protobuf.", "type": "SERVICE_POLICY" }, { "name": "Service reviews", "description": "Services management review are regularly organized with customers to monitor the usability of the services and the KPI related to the quality of service described in the SLA.", "type": "SERVICE_POLICY" }, { "name": "Internet Accessibility", "description": "The interface of DSNA business services is accessible from outside DSNA premises through Internet using IPV4. An IPSEC link (IKE v1 or IKE v2) is used between DSNA provider and customer terminal network equipment.", "type": "SECURITY_CONSTRAINT" }, { "name": "Mutual authentication with X509 certificates", "description": "Authentication is required - Mutual authentication with X509 certificates is used between the AMQPS broker and its client established within a TLS session. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer.", "type": "SECURITY_CONSTRAINT" }, { "name": "Confidentiality", "description": "The service relies on TLS 1.2 to provide integrity and confidentiality.", "type": "SECURITY_CONSTRAINT" }, { "name": "Integrity", "description": "The service relies on TLS 1.2 to provide integrity and confidentiality.", "type": "SECURITY_CONSTRAINT" } ], "dateInOperation": "2027-02-09", "qualitiesOfService": { "performance": [ { "name": "Services level objectives", "description": "The service level objectives regarding the availability, response time, throughput and recoverability of DSNA Services depend on the purpose (mission) for which the Customer intend to use them (e.g. 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 DSNA Customer." }, { "name": "Network performance", "description": "The minimum Bandwidth required to consume DSNA services (hypothesis for the technical integration service of 300 simultaneous flight managed by the system) is 10MB/s." }, { "name": "Rate limitation", "description": "Customer 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." } ], "reliability": [ { "name": "Recoverability", "description": "The service level objectives regarding the recoverability of the Service depend on the purpose (mission) for which the Customer intend to use it (e.g. test, training or 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 Customer." }, { "name": "Availability", "description": "The service level objectives regarding the availability of the Service depend on the purpose (mission) for which the Customer intend to use it (e.g. test, training or 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 Customer." } ], "security": [ { "name": "Confidentiality", "description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer" }, { "name": "Integrity", "description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer" } ] }, "serviceSupport": [ { "name": "Customer Service Support", "role": "Customer Support for more information on the service [Business Hours]", "contactInformation": [ { "type": "PHONE", "address": "+33169577209" }, { "type": "PHONE", "address": "+33699513411" }, { "type": "EMAIL", "address": "bertrand.morvan@aviation-civile.gouv.fr" }, { "type": "POSTAL", "address": "DSNA/DO Batiment 1611 9, rue de Champagne Boite postale 91205 91200 ATHIS-MONS - France" }] }], "validation": [ { "description": { "evidence": "Prior to any Service publication in the European Swim Registry, this service has been prototyped and validated in the context of SESAR Virtual Centres activities and through the operational 4-FLIGHT program.\r\nDSNA and THALES shall ensure that the interfaces comply with the specifications stated in the ICDs and that the interfaces are adequately tested by both parties as defined in the Interface Responsibility Definition sections of these ICDs." }, "type": "COLLABORATIVE_VALIDATION" }] }, "informationDescription": { "informationDefinition": [ { "name": "SSRCodeManagement Service Information Definition", "definition": "see SESAR PJ32-WP3 SDD SSRCodeManagement", "airmCorrespondence": "see SESAR SDD SSRCodeManagementT - 4.1.0 AIRM Conformance Declaration" } ] }, "technicalDescription": { "technicalConstraint": [ { "name": "Time synchronization", "description": "NTP is the standard solution for accurately synchronizing systems to UTC time. So, DSNA Provider and DSNA 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": "Technical behaviour", "description": "Each service interface of the DSNA business services relies on the concept of AMQP queues and topics. \r\n-\tThe customer shall use an implementation of the AMQP 1.0 specification to connect to the DSNA provider endpoint. \r\n-\tThe DSNA provider endpoint is an AMQP 1.0 broker managing queue and topics. \r\nThe message payloads are encoded following a protobuf format. \r\n The customer acts as requester and subscriber. The DSNA provider acts as responder and publisher.\r\nConcerning publish-subscribe, the customer subscribes to a DSNA distribution service by directly listening to an appropriate AMQP topic, which name follows the DSNA derivation rules.\r\nThe customer requests on the Subscription management queue the creation of a new subscription. The DSNA provider returns on the Reply queue, the address of the Publication queue(s) to receive data (one queue per type of subscribed data).\r\nThe subscribers can filter the messages they want to receive by using the filter parameters defined for each subscription operation.\r\nN.B:\r\n-\tIf the DSNA platform restarts while the Customer is connected to the AMQP Broker, the current repository of messages is published again.\r\n-\tThe 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-\tMore generally, since the distribution events from different services are asynchronous (independent topics), they may be received in a few ms before reaching consistency.\r\n\r\nConcerning request-reply (used for subscription technical operations or management operations) the DSNA customer sends a request by sending a message to an appropriate AMQP queue, which name follows the DSNA derivation rules, to make a request. The request message contains the name of the queue into the DSNA customer listens and in which the reply from the DSNA provider is expected.\r\n" }, { "name": "Reconnection", "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 DSNA customer to try to reconnect regularly." }, { "name": "Permission on Topic", "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 DSNA 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" } ], "serviceMonitoring": { "monitoringDescription": "DSNA services are supervised in real time by trained and licensed ATSEPs." }, "behaviour": [ { "name": "Typical Data Management Behaviour", "description": "The detailed behaviour of the service is provided in each operation dedicated section" }] }, "references": { "implementedStandard": [ { "conformanceStatement": "Is compliant", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION", "title": "EUROCONTROL Specification for SWIM - Service Description", "version": "2.0", "description": "Description of Service according to EUROCONTROL specifications" }, { "conformanceStatement": "Is compliant", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION", "title": "EUROCONTROL Specification for SWIM - Information Definition", "version": "1.0" }, { "conformanceStatement": "Is compliant", "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE", "title": "EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile", "version": "1.0" } ], "serviceDocument": [ { "documentType": "SERVICE_STANDARD", "title": "SESAR PJ32-WP3 SDD SSRCodeManagement", "version": "V1.0", "reference": { "description": "SSRCodeManagement Service Information Definition", "url": "https://www.sesarju.eu/sites/default/files/documents/solution/SolPJ.10-W2-93%20TS-IRS%20V3.pdf" } }, { "description": "SWIM Service Description document (SSD) from 4-FLIGHT SWIFT on which the DSNA SSRM Service is based", "documentType": "SERVICE_SPECIFICATION", "title": "SWIFT Services SSR Code Management Service", "version": "V1.4" }, { "description": "Complete service specification", "documentType": "SERVICE_SPECIFICATION", "title": "SWIM INTERFACE CONTROL DOCUMENT FOR 4-FLIGHT", "version": "02 SW30" }, { "description": "Protobuf file describing the exchanged information", "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "CCS_ssrCodeManagement.proto", "version": "1.2" }, { "description": "Protobuf file describing the exchanged information common to two or more DSNA Services", "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "CCS_common.proto", "version": "1.4.3" }, { "description": "Protobuf file describing the metadata used by the DSNA Services", "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION", "title": "metadata.proto", "version": "v1.2" } ] }, "serviceInterface": [ { "name": "SSRCodeManagementProvider", "description": "This Service Interface exposes the set of basic operations needed for SSR Code Management.\r\nIt addresses operations such as:\r\n- releaseSSRCode,\r\n- requestSSRCode.", "provisionSide": "PROVIDER_SIDE", "endPoints": [ { "name": "Endpoint", "description": "For security reasons, the addresses will be communicated only to Customers", "url": "amqps://"} ], "serviceInterfaceBinding": { "name": "SWIM_TI_YP_1_0_AMQP_MESSAGING", "description": "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." }, "networkInterfaceBinding": { "name": "IPV4_SECURE_UNICAST" }, "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE", "operations": [ { "name": "requestSSRCode", "description": "Allows the operator to manually assign an SSR code given in the input, or to request an automatic SSR code assignment.", "idempotency": "NON_IDEMPOTENT", "messages": [ { "name": "SSRCodeAssignmentRequest", "direction": "IN" }, { "name": "SSRCMResponse", "direction": "OUT" }] }, { "name": "releaseSSRCode", "description": "Allows the operator to manually release an assigned SSR code if it is not used for correlation purpose.", "idempotency": "NON_IDEMPOTENT", "messages": [ { "name": "SSRCodeReleaseRequest", "direction": "IN" }, { "name": "SSRCMResponse", "direction": "OUT" }] }] } ], "descriptionInformation": { "descriptionIdentification": { "title": "SSRCodeManagement Service description", "edition": "1.0.0", "referenceDate": "2026-06-01" }, "abbreviations": [ { "name": "ADSP", "description": "ATM Data Service Provider" }, { "name": "AMQP", "description": "Advanced Message Queuing Protocol" }, { "name": "ANSP", "description": "Air Navigation Service Provider" }, { "name": "ATC", "description": "Air Traffic Control" }, { "name": "ATM", "description": "Air Traffic Management" }, { "name": "ATS", "description": "Air Traffic Services" }, { "name": "ATSEP", "description": "Air Traffic Safety Electronics Personnel" }, { "name": "ATSU", "description": "Air Traffic Service Unit" }, { "name": "CWP", "description": "Controller Working Position" }, { "name": "DO", "description": "Direction des Operations" }, { "name": "DSNA", "description": "Direction des Services de la Navigation Aerienne (French ANSP)" }, { "name": "FDD", "description": "Flight Data Distribution" }, { "name": "HTTP", "description": "Hypertext Transfer Protocol" }, { "name": "IP", "description": "Internet Protocol" }, { "name": "IPV4", "description": "Internet Protocol version 4" }, { "name": "KPI", "description": "Key Performance Indicator" }, { "name": "NTP", "description": "Network Time Protocol" }, { "name": "SDD", "description": "Service Definition Document" }, { "name": "SESAR", "description": "Single European Sky Air Traffic Management Research" }, { "name": "SLA", "description": "Service Level Agreement" }, { "name": "SSD", "description": "SWIM Service Description" }, { "name": "SSRM", "description": "SSR code Management" }, { "name": "SWIM", "description": "System Wide Information Management" }, { "name": "TCP", "description": "Transfer Control Protocol" }, { "name": "TI", "description": "Technical Infrastructure" }, { "name": "TLS", "description": "Transport Level Security" }, { "name": "URL", "description": " Uniform Resource Locator " }, { "name": "UTC", "description": "Universal Time Coordinated" }, { "name": "XML", "description": "Extensible Markup Language" } ] }, "serviceIdentification": { "name": "SSRCodeManagement Service", "version": "1.4.3" } } }