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.
Normally, 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.
The CWP will receive a reply when the service request has been completed, indicating the status of the request. If the request is successful, the SSR code assigned to the segment is updated.
Please note that the use of the DSNA SSRCodeManagement service implies the use of FlightDataDistribution Service to get the output SSR code information in the updated Flight Plan.
Categorisation
SERVICE_DESCRIPTION
PROSPECTIVE
- INFORMATION_MANAGEMENT
- AIR_TRAFFIC_SERVICE_PROVIDER
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
- CIVIL_AIRSPACE_USER
- PROVIDER_OF_DATA_SERVICES
- FLIGHT_INFORMATION_EXCHANGE
- SYNCHRONOUS_REQUEST_REPLY
Provider
DSNA
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.
Paris ACC : At the crossroads of the biggest European platforms, Paris ACC manage one of the densest 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.
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"
- PROVIDER_OF_DATA_SERVICES
DSNA
Restricted
Restricted
SSR Code management
The SSRCodeManagement Service addresses the assignment of SSR codes to eligible flights and release of SSR codes assigned to flights. It addresses operations related to:
- SSR code assignment request,
- SSR code release.
Request SSR Code
To request an assigned SSRCode for a flight
To manually assign a SSRCode given in the input, or to request an automatic SSRCode assignment.
Release SSR Code
To release an SSRCode assigned to a flight
To manually release an assigned SSRCode that is not used for correlation purpose, in order to make this code available again.
-
Services level objectivesThe 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).These 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.
-
Network performanceThe minimum Bandwidth required to consume DSNA services (hypothesis for the technical integration service of 300 simultaneous flight managed by the system) is 10MB/s.
-
Rate limitationCustomer 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.
-
RecoverabilityThe 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).These 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.
-
AvailabilityThe 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).These 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.
-
ConfidentialityTLS 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
-
IntegrityTLS 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
-
SubscriptionConsumers needs to contact DSNA to register administratively to this service.
-
Aviation usersOnly service consumers within the aviation domain can use this service.
-
Non aviation usersThe service consumers cannot pass the information obtained from the service to non-aviation users without prior authorisation from DSNA.
-
Dependencies with DSNA ServicesIf 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.
-
Dependency with FDD DSNA ServiceThe use of this SSRCodeManagement service implies the use of the FlightDataDistribution DSNA Service to get the output Flight Plan Data.
-
Service versioningAt 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.
-
Service reviewsServices 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.
-
Internet AccessibilityThe 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.
-
Mutual authentication with X509 certificatesAuthentication 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.
-
ConfidentialityThe service relies on TLS 1.2 to provide integrity and confidentiality.
-
IntegrityThe service relies on TLS 1.2 to provide integrity and confidentiality.
-
Customer Service SupportCustomer Support for more information on the service [Business Hours]
-
+33169577209
-
+33699513411
-
DSNA/DO Batiment 1611 9, rue de Champagne Boite postale 91205 91200 ATHIS-MONS - France
COLLABORATIVE_VALIDATION
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. DSNA 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.
-
ADSPATM Data Service Provider
-
AMQPAdvanced Message Queuing Protocol
-
ANSPAir Navigation Service Provider
-
ATCAir Traffic Control
-
ATMAir Traffic Management
-
ATSAir Traffic Services
-
ATSEPAir Traffic Safety Electronics Personnel
-
ATSUAir Traffic Service Unit
-
CWPController Working Position
-
DODirection des Operations
-
DSNADirection des Services de la Navigation Aerienne (French ANSP)
-
FDDFlight Data Distribution
-
HTTPHypertext Transfer Protocol
-
IPInternet Protocol
-
IPV4Internet Protocol version 4
-
KPIKey Performance Indicator
-
NTPNetwork Time Protocol
-
SDDService Definition Document
-
SESARSingle European Sky Air Traffic Management Research
-
SLAService Level Agreement
-
SSDSWIM Service Description
-
SSRMSSR code Management
-
SWIMSystem Wide Information Management
-
TCPTransfer Control Protocol
-
TITechnical Infrastructure
-
TLSTransport Level Security
-
URLUniform Resource Locator
-
UTCUniversal Time Coordinated
-
XMLExtensible Markup Language
SSRCodeManagement Service Information Definition
see SESAR PJ32-WP3 SDD SSRCodeManagement
see SESAR SDD SSRCodeManagementT - 4.1.0 AIRM Conformance Declaration
-
Time synchronizationNTP 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.
-
Technical behaviourEach service interface of the DSNA business services relies on the concept of AMQP queues and topics. -The customer shall use an implementation of the AMQP 1.0 specification to connect to the DSNA provider endpoint. -The DSNA provider endpoint is an AMQP 1.0 broker managing queue and topics. The message payloads are encoded following a protobuf format. The customer acts as requester and subscriber. The DSNA provider acts as responder and publisher.Concerning 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.The 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).The subscribers can filter the messages they want to receive by using the filter parameters defined for each subscription operation.N.B:-If the DSNA platform restarts while the Customer is connected to the AMQP Broker, the current repository of messages is published again.-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.-More generally, since the distribution events from different services are asynchronous (independent topics), they may be received in a few ms before reaching consistency.Concerning 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.
-
ReconnectionThe 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.
-
Permission on TopicThe AMQP broker creates the physical resources associated with a destination (queue, topic) on demand when messages are actually sent to them.Permissions on queues and topics (read/write access) are granted based on intended usage. The DSNA customer will have: -Write access on the request queue-Read access on the reply queue -Read access on the topic for distribution service
-
Typical Data Management BehaviourThe detailed behaviour of the service is provided in each operation dedicated section
-
DSNA services are supervised in real time by trained and licensed ATSEPs.
-
SSRCodeManagementProvider
This Service Interface exposes the set of basic operations needed for SSR Code Management. It addresses operations such as:
- releaseSSRCode,
- requestSSRCode.
PROVIDER_SIDESYNCHRONOUS_REQUEST_RESPONSE-
requestSSRCodeAllows the operator to manually assign an SSR code given in the input, or to request an automatic SSR code assignment.gitMessages
-
SSRCodeAssignmentRequestIN
-
SSRCMResponseOUT
-
-
releaseSSRCodeAllows the operator to manually release an assigned SSR code if it is not used for correlation purpose.gitMessages
-
SSRCodeReleaseRequestIN
-
SSRCMResponseOUT
-
EndpointsRestricted
-
SWIM_TI_YP_1_0_AMQP_MESSAGINGInformation is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.
-
IPV4_SECURE_UNICAST
-
-
SESAR PJ32-WP3 SDD SSRCodeManagementSERVICE_STANDARDV1.0Reference
-
https://www.sesarju.eu/sites/default/files/documents/solution/SolPJ.10-W2-93%20TS-IRS%20V3.pdfSSRCodeManagement Service Information Definition
-
-
SWIFT Services SSR Code Management ServiceSWIM Service Description document (SSD) from 4-FLIGHT SWIFT on which the DSNA SSRM Service is basedSERVICE_SPECIFICATIONV1.4
-
SWIM INTERFACE CONTROL DOCUMENT FOR 4-FLIGHTComplete service specificationSERVICE_SPECIFICATION02 SW30
-
CCS_ssrCodeManagement.protoProtobuf file describing the exchanged informationMACHINE_READABLE_SERVICE_DESCRIPTION1.2
-
CCS_common.protoProtobuf file describing the exchanged information common to two or more DSNA ServicesMACHINE_READABLE_SERVICE_DESCRIPTION1.4.3
-
metadata.protoProtobuf file describing the metadata used by the DSNA ServicesMACHINE_READABLE_SERVICE_DESCRIPTIONv1.2
EUROCONTROL Specification for SWIM - Service Description
EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION
Is compliant
2.0
Description of Service according to EUROCONTROL specifications
EUROCONTROL Specification for SWIM - Information Definition
EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION
Is compliant
1.0
EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile
EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE
Is compliant
1.0