{
	"informationService": {
		"descriptionInformation": {
			"serviceDescriptionIdentification": {
				"serviceDescriptionTitle": "DSNA Arrival Sequence Service",
				"serviceDescriptionEdition": "v1.1",
				"serviceDescriptionReferenceDate": "01/06/2021"
			},
			"abbreviations": [
				{
					"name": "A-CDM",
					"description": "Airport CDM (Collaborative Decision Making)"
				},
				{
					"name": "ADES",
					"description": "Aerodrome of Destination"
				},
				{
					"name": "AIRM",
					"description": "ATM Information Reference Model"
				},
				{
					"name": "AMAN",
					"description": "Arrival management"
				},
				{
					"name": "AMQP",
					"description": "Advanced Message Queuing Protocol"
				},
				{
					"name": "ANSP",
					"description": "Air Navigation Service Provider"
				},
				{
					"name": "AOR",
					"description": "Area Of Responsibility"
				},
				{
					"name": "APTO",
					"description": "AMAN Planned Time Over"
				},
				{
					"name": "APTT",
					"description": "AMAN Planned Threshold Time"
				},
				{
					"name": "ATCO",
					"description": "Air Traffic Controller"
				},
				{
					"name": "ATLDT",
					"description": "AMAN Target Landing Time"
				},
				{
					"name": "ATM",
					"description": "Air Traffic Management"
				},
				{
					"name": "ATS",
					"description": "Air Traffic Service"
				},
				{
					"name": "ATSU",
					"description": "Air Traffic Service Unit"
				},
				{
					"name": "CDM",
					"description": "Collaborative Decision Making"
				},
				{
					"name": "DSNA",
					"description": "Direction des Services de la Navigation Aérienne"
				},
				{
					"name": "EH",
					"description": "Extended Horizon"
				},
				{
					"name": "EUROCAE",
					"description": "European Organisation for Civil Aviation Equipment"
				},
				{
					"name": "HTTP",
					"description": "Hypertext Transfer Protocol"
				},
				{
					"name": "IAF",
					"description": "Initial Approach Fix"
				},
				{
					"name": "ICAO",
					"description": "International Civil Aviation Organisation"
				},
				{
					"name": "IFPS",
					"description": "Integrated Initial Flight Plan Processing System"
				},
				{
					"name": "IP",
					"description": "Internet Protocol"
				},
				{
					"name": "MP",
					"description": "Metering Point"
				},
				{
					"name": "OSED",
					"description": "Operational Services & Environment Description"
				},
				{
					"name": "REQ",
					"description": "Requirement"
				},
				{
					"name": "RWY",
					"description": "Runway"
				},
				{
					"name": "SLA",
					"description": "Service Level Agreement"
				},
				{
					"name": "SOAP",
					"description": "Service Oriented Architecture Protocol"
				},
				{
					"name": "STA",
					"description": "Scheduled Time of Arrival"
				},
				{
					"name": "SWIM",
					"description": "System Wide Information Management"
				},
				{
					"name": "SWIM TI",
					"description": "SWIM Technical Infrastructure"
				},
				{
					"name": "TCP",
					"description": "Transmission Control Protocol"
				},
				{
					"name": "TMA",
					"description": "Terminal Manoeuvring Area"
				},
				{
					"name": "TOD",
					"description": "Top Of Descent"
				},
				{
					"name": "TTG",
					"description": "Time To Gain"
				},
				{
					"name": "TTL",
					"description": "Time To Lose"
				},
				{
					"name": "URL",
					"description": "Uniform Resource Locator"
				},
				{
					"name": "WSDL",
					"description": "Web Services Description Language"
				},
				{
					"name": "XML",
					"description": "Extensible Markup Language"
				},
				{
					"name": "XSD",
					"description": "SML Schema Definition"
				},
				{
					"name": "YP",
					"description": "Yellow Profile"
				}
			]
		},
		"name": "ArrivalSequenceDistribution Service",
		"version": "v1.1",
		"serviceAbstract": "This Service is part of DSNA services. It supports the distribution of arrival sequences related to major hub airports.",
		"serviceCategorisation": {
			"serviceType": "SWIM_CANDIDATE",
			"lifeCycleStage": "PROSPECTIVE",
			"businessActivityType": [
				"TRAFFIC_SYNCHRONISATION"
			],
			"informationCategory": [
				"FLIGHT_INFORMATION_EXCHANGE"
			],
			"intendedConsumer": [
				"AIRPORT_OPERATOR",
				"AIR_TRAFFIC_SERVICE_PROVIDER",
				"CIVIL_AIRSPACE_USER"
			],
			"applicationMessageExchangePattern": [
				"PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM"
			],
			"geospatialCategorisation": {
				"aerodromeICAOLocationIndicator": [
					"LFPG",
					"LFPB",
					"LFPO",
					"LFPN",
					"LFPV"
				]
			}
		},
		"serviceProvision": {
			"dateInOperation": "2021-06-30",
			"provider": "DSNA",
			"providerDescription": "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER",
			"providerType": [
				"CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
			],
			"serviceSupport": "",
			"pointOfContact": [
				{
					"name": "DSNA SWIM service team",
					"description": "To request access to the service",
					"email": "dsna_registry_access_manager@eei.cena.fr"
				}
			]
		},
		"serviceGeneralDescription": {
			"operationalNeed": [
				{
					"name": "COMMISSION IMPLEMENTING REGULATION (EU) No 716/2014",
					"description": "the service is defined to satisfy the requirement Arrival Management extended to en-route Airspace. \r The Implementing Regulation requires the upgrade of existing AMAN to provide connection with cooperative En-Route Air Traffic Service Units (ATSU) to coordinate the actions to be taken by the cooperative ATSUs to make the correct time adjustment to flights under their control, in order to get the best and most efficient arriving flight sequence at the relevant airports based on AMAN arriving planning tool."
				},
				{
					"name": "Operational and Business context",
					"description": "The purpose of the AMAN RP SWIM service is to make available to external partners (ADP or Airline Companies) the sequence data provided by the AMAN APPs (CDG and ORY), in the format defined by ED-254 and without any transformation of the information."
				}
			],
			"functionality": [
				{
					"name": "Publish arrival sequence",
					"description": "Publication of current arrival sequence information",
					"realWorldEffect": "All subscribers are informed of any change about the arrival sequence of one or more airports, according to their subscription parameters."
				}
			],
			"accessAndUseCondition": [
				{
					"name": "Business and operational policies",
					"description": "Business and operational policies are defined in the Service Agreement.",
					"type": "SERVICE_POLICY"
				},
				{
					"name": "Versioning Policy",
					"description": "Service update: This service will be updated when new operational needs are identified. Please get in touch with the Service Provider/Consumer Point of Contact for any evolution request regarding this Service. Backwards compatibility is guaranteed between minor versions but not for major. Given a version number MAJOR.MINOR.PATCH, DSNA will increment: the MAJOR version number when incompatible API changes occur, the MINOR version number when functionality evolve in a backwards compatible manner, the PATCH version number when backwards compatible bug fixes occur.",
					"type": "SERVICE_POLICY"
				},
				{
					"name": "Lifecycle Policy",
					"description": "DSNA will manage 3 versions of the service: \r Versions N (i.e. nominal version of the service) and N-1 (if existing) provided by the operational system, Version N-1 will be removed when all consumers have migrated to the nominal version of the service or when the version N+1 is commissioned (Constraint of evolutivity). \r Version N or N+1 (if existing) provided by a pre-operational (preops) system. \r Please get in touch with the Service Provider / Consumer Point of Contact for any evolution request regarding this Service.",
					"type": "SERVICE_POLICY"
				},
				{
					"name": "Access to the service",
					"description": "The access to the service is subject to the signature of a Service Agreement between DSNA and the Recipient. Please contact DSNA SWIM Services Responsible (§1.2) for more information.",
					"type": "LEGAL_CONSTRAINT"
				},
				{
					"name": "Service consumption constraints",
					"description": "Two access points are provided for access to the service from Internet: \r One operational access point associated with the operational system (standard WSDL and amqps endpoint). \r One pre-operational access point associated with the pre-operational system (PREOPS WSDL and amqps endpoint). \r The certificate provided by DSNA is specific to the service and the endpoint (operational or pre-operational). Consumer must not use an operational certificate to invoke the pre-operational system. \r One subscription per certificate (and as a consequence, one AMQP connection).",
					"type": "LEGAL_CONSTRAINT"
				},
				{
					"name": "Confidentiality",
					"description": "Communications are secured by TLS protocol. Communications (HTTPS and AMQPS) are secured by the TLS v1.2 protocol. SSL, TLS  v1 to v1.1 versions are not supported. Suites using the AES -256 or ChaCha20 block cipher algorithm are preferred. The AES-128 algorithm is an acceptable alternative. Suites using the SHA2 and later hash functions are the only ones supported. Communications (HTTPS and AMQPS) require mutual authentication of the correspondents based on X-509 certificates (see § Authentication):\r The consumer must provide its full certificate during the connection phase. This certificate must not have been corrupted or revoked.\r The consumer's certificate also allows identification and secure access to the only distribution channel linked to its subscription.\r The server also transmits its full certificate during the connection phase.",
					"type": "SECURITY_CONSTRAINT"
				},
				{
					"name": "Integrity",
					"description": "Communication integrity is guaranteed by TLS encryption.",
					"type": "SECURITY_CONSTRAINT"
				},
				{
					"name": "Authentification",
					"description": "X.509 certificate \r All communications are secured by mutual authentication of correspondents using X.509 certificates. A consumer is entitled to one subscription per X.509 certificate and therefore one AMQP connection. The lifetime of a subscription and therefore of an AMQP connection is limited by the expiry date of the certificate. Upon service restart, active subscriptions are not lost. The certificates are issued to the consumer by the DSNA during the service contractualisation phase. Certificates have an expiry date and their renewal must therefore be managed in advance by both parties. Transport authentication: TLS with mutual authentication and SASL ANONYMOUS.",
					"type": "SECURITY_CONSTRAINT"
				},
				{
					"name": "Authorisation",
					"description": "The consumer is authorized to access any Arrival Sequence information using a valid X.509 certificate associated with the Arrival Sequence Distribution Service (see Authentication).",
					"type": "SECURITY_CONSTRAINT"
				}
			],
			"qualityOfService": [
				{
					"name": "Avaibility",
					"description": "The contractual service availability is defined in the Service Agreement (see §1.7.1). Target values: Availability of 99% over a rolling period of 1 calendar month \r Maximum Time to Recover: 24 hours."
				},
				{
					"name": "Response time",
					"description": "For subscription management interface: Mean Response Time to a typical request on a single runway should be < 1 sec (Internet latency excluded, calculated over a rolling period of 1 calendar month) Mean Response Time to a subscription request should be < 1.5 sec (Internet latency excluded, calculated over a rolling period of 1 calendar month)"
				},
				{
					"name": "Throughput",
					"description": "At this time no traffic limitation is applied to the service. The consumer shall make a reasonable use of the subscribe interface and there is no reason to require a new subscription each second."
				}
			],
			"validation": [
				{
					"type": "COLLABORATIVE_VALIDATION",
					"description": "Collaborative validation: the Provider together with service users jointly carries out the service validation."
				}
			]
		},
		"serviceInformationDescription": {
			"informationDefinition": [
				{
					"name": "Service Information Definition",
					"description": "The information definition is described in a separate document. This includes the semantic correspondence. See References.",
					"airmConformant": true,
					"airmVersion": "1.0.0"
				}
			],
			"exchangeSchema": [
				{
					"name": "ArrivalSequenceInformationPublisher.wsdl",
					"schemaLanguage": "WSDL",
					"reference": "https://api.dsna.fr/media/document/181"
				},
				{
					"name": "ArrivalSequenceServiceInformationPublisher_msg.xsd",
					"schemaLanguage": "XML",
					"reference": "https://api.dsna.fr/media/document/196"
				},
				{
					"name": "SharedTypes.xsd",
					"schemaLanguage": "XML",
					"reference": "https://api.dsna.fr/media/document/191"
				},
				{
					"name": "ArrivalSequenceInformation_msg.xsd",
					"schemaLanguage": "XML",
					"reference": "https://api.dsna.fr/media/document/176"
				}
			]
		},
		"serviceTechnicalDescription": {
			"serviceMonitoring": {
				"monitoringDescription": "In the event of a problem on the DSNA side: \r The “back-end” server can stop the message service completely. It then issues a ProviderException message with the status AMAN_UNAVAILABLE (see ED-254-REQ 0575). \r The problem may also be partial: \r The server sends a providerException message for one or more ADES (specified in the impactedAdesList elements of the message) while continuing to serve the other arrivalSequence messages (see Figure 4 'alt on LFPO source error'):\r If the consumer is not logged on when a providerException message is sent, the consumer will have to wait for a full message transmission cycle to identify the problem. \r The maximum duration of a complete cycle for an aerodrome is given by the duration of the transmission cycle (@calculationPeriod) plus the maximum processing time ({MAX_DELIVERY_TIME}). \r Message distribution resumes as soon as the cause of the problem is corrected (see ED-254-REQ 0590). \r In the event of a one-off problem on the consumer side, a SOAP communicateProblem operation is available. \r Information will be logged on DSNA side."
			},
			"securityMechanism": [
				{
					"name": "TLS 1.2",
					"description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer. (see Access and use conditions for more information)",
					"type": [
						"CONFIDENTIALITY"
					]
				},
				{
					"name": "X.509v3 Server Certificate",
					"description": "The service utilizes X.509v3 public certificate to authenticate the provider. (see Access and use conditions for more information)",
					"type": [
						"AUTHENTICATION"
					]
				},
				{
					"name": "X.509v3 Client Certificate",
					"description": "The service utilizes X.509v3 public certificate to authenticate the consumer. (see Access and use conditions for more information)",
					"type": [
						"AUTHENTICATION"
					]
				}
			],
			"technicalConstraint": [
				{
					"name": "List of available arrival sequences",
					"description": "Find below the list of available arrival sequences or ADES codes that can be used in subscription requests or that can be present in received messages. \r CDG : LFPG, LFPB; \r Orly : LFPO, LFPN, LFPV."
				},
				{
					"name": "Sizing and performance",
					"description": "For each selected ADES, a consumer must be able to receive one message every 15 sec. (standard sequence calculation period) without generating congestion in its queue. Unprocessed messages will be automatically suppressed after expiration of time to live (TTL) delay. This behavior is not critical due to the cyclical nature of the arrival sequence calculation (see ED-254-REQ 0870). The use of a message listener with deferred processing is recommended in this case.\r The consumer infrastructure must be able to handle the resulting flow rate from their subscription. The filter capability of the subscription request can be used to reduce the resulting flow rate (remove uninteresting ADES or flights). Find below some orders of magnitude for arrival sequence message size and associated flow rate (calculation period 15 sec.).\r  Flights in the sequence Sequence size (bytes) Flow rate (with protocol overhead) (kb/s) \r\n Average ADES situation 40 44550 24 \r Loaded ADES situation 20 220550 118 \r The following values are given as a guide: \r\n Constant Indicative Value \r\n MAX_DELIVERY_TIME (cf. ED-254-REQ 0800, 0805) 10 sec \r\n MAX_CONSUMER_NUMBER (cf. ED-254-REQ 0885) 100 (no clear value identified at this stage)"
				}
			]
		},
		"serviceInterface": [
			{
				"name": "ArrivalSequenceInformationPublisher",
				"description": "Subscription management interface.The service consumer is able to subscribe and unsubscribe to the arrival sequence information and by using the same interface, the consumer is able to send problem reports.",
				"interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
				"interfaceBindingDescription": "SOAP over HTTPS: SOAP 1.1 / HTTP 1.1 / TLS 1.2 / TCP / IPv4",
				"networkInterfaceBinding": "IPV4_SECURE_UNICAST",
				"serviceInterfaceBinding": "SWIM_TI_YP_1_0_WS_SOAP",
				"tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE",
				"operation": [
					{
						"name": "subscribeToArrivalSequenceInformation",
						"description": "SOAP subscription Operation",
						"idempotency": "NON_IDEMPOTENT",
						"synchronicity": "SYNCHRONOUS",
						"precondition": "To have a valid certificate",
						"tiProtocolMethod": [
							"SOAP over HTTPS: SOAP 1.1 / HTTP 1.1 / TLS 1.2 / TCP / IPv4"
						],
						"processingConsideration": [
							{
								"name": "Filters management",
								"description": "All criteria of a subscriptionFilter element are processed with a logical AND operator (see ED-254-REQ 0070(Filter conditions 1)). For a given filter criterion in the same subscriptionFilter element, the logical OR operator is used (see ED-254-REQ 0080)."
							}
						],
						"operationMessage": [
							{
								"name": "subscribeToArrivalSequenceInformationRequest",
								"description": "The message to request a subscription to arrival sequence information, and allowing to define some subscription filters",
								"direction": "IN",
								"isFault": false,
								"headers": "application/XML",
								"body": ""
							},
							{
								"name": "subscribeToArrivalSequenceInformationResponse",
								"description": "The message containing the response to the subscription",
								"direction": "OUT",
								"isFault": false,
								"headers": "application/XML",
								"body": ""
							}
						]
					},
					{
						"name": "unsubscribeToArrivalSequenceInformation",
						"description": "SOAP unsubscription Operation",
						"idempotency": "NON_IDEMPOTENT",
						"synchronicity": "SYNCHRONOUS",
						"precondition": "To have a valid subscription reference",
						"tiProtocolMethod": [
							"SOAP over HTTPS: SOAP 1.1 / HTTP 1.1 / TLS 1.2 / TCP / IPv4"
						],
						"processingConsideration": [
							{
								"name": "n.a",
								"description": "n.a"
							}
						],
						"operationMessage": [
							{
								"name": "unsubscribeToArrivalSequenceInformationRequest",
								"description": "The message to request to stop the subscription to arrival sequence information, and allowing to define some subscription filters",
								"direction": "IN",
								"isFault": false,
								"headers": "application/XML",
								"body": ""
							},
							{
								"name": "unsubscribeToArrivalSequenceInformationtResponse",
								"description": "The message containing the response to the unsubscription",
								"direction": "OUT",
								"isFault": false,
								"headers": "application/XML",
								"body": ""
							},
							{
								"name": "unsubscribeToArrivalSequenceInformationtResponse",
								"description": "The message containing the response to the unsubscription",
								"direction": "OUT",
								"isFault": true,
								"headers": "",
								"body": ""
							}
						]
					},
					{
						"name": "communicateProblem",
						"description": "Operation to log a problem in the DSNA monitoring system",
						"idempotency": "IDEMPOTENT",
						"synchronicity": "SYNCHRONOUS",
						"precondition": "To have a valid certificate",
						"tiProtocolMethod": [
							"SOAP over HTTPS: SOAP 1.1 / HTTP 1.1 / TLS 1.2 / TCP / IPv4"
						],
						"processingConsideration": [
							{
								"name": "n.a",
								"description": "n.a"
							}
						],
						"operationMessage": [
							{
								"name": "communicateProblemRequest",
								"description": "The message to log a problem in the DSNA monitoring system",
								"direction": "OUT",
								"isFault": false,
								"headers": "application/XML",
								"body": ""
							}
						]
					}
				],
				"behaviour": [
					{
						"name": "Nominal and unexpected behaviour",
						"description": "The following diagram illustrates the interaction between the service consumer and the service:"
					}
				],
				"endPoint": [
					{
						"name": "OPERATIONAL",
						"description": "operational network address",
						"address": "https://eaman.swim.dsna.fr:443/aman/arrivalsequence/1.1.0/subscription"
					},
					{
						"name": "PRE-OPERATIONAL",
						"description": "pre-operational network address",
						"address": "https://eaman.preops.swim.dsna.fr:443/aman/arrivalsequence/1.1.0/subscription"
					}
				]
			},
			{
				"name": "ArrivalSequenceInformationSubscriber",
				"description": "DSNA Arrival Sequence Service - Data distribution interface",
				"interfaceProvisionSide": "CONSUMER_SIDE_INTERFACE",
				"interfaceBindingDescription": "AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4",
				"networkInterfaceBinding": "IPV4_SECURE_UNICAST",
				"serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
				"operation": [
					{
						"name": "publishArrivalSequence",
						"description": "Operation to transmit the ArrivalSequence message to the service consumer",
						"idempotency": "NON_IDEMPOTENT",
						"synchronicity": "ASYNCHRONOUS",
						"precondition": "To have a valid certificate and a valid subscription reference",
						"tiProtocolMethod": [
							"AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4"
						],
						"processingConsideration": [
							{
								"name": "n.a",
								"description": "n.a"
							}
						],
						"operationMessage": [
							{
								"name": "ArrivalSequence",
								"description": "An Arrival Sequence is a set of sequence entries, with message related attributes."
							}
						]
					},
					{
						"name": "communicateException",
						"description": "Operation to inform the service consumer about problems occurring, at service run-time, on provider side.",
						"idempotency": "NON_IDEMPOTENT",
						"synchronicity": "ASYNCHRONOUS",
						"precondition": "To have a valid certificate and a valid subscription reference",
						"tiProtocolMethod": [
							"AMQPS: AMQP 1.0 / TLS 1.2 / TCP / IPv4"
						],
						"processingConsideration": [
							{
								"name": "n.a",
								"description": "n.a"
							}
						],
						"operationMessage": [
							{
								"name": "ProviderException",
								"description": "A providerException message is sent in case of a arrival sequencing service degradation or interruption."
							}
						]
					}
				],
				"behaviour": [
					{
						"name": "Nominal and unexpected behaviour",
						"description": "The following diagram illustrates the interaction between the service consumer and the service:"
					}
				],
				"endPoint": [
					{
						"name": "Operational",
						"description": "operational network address",
						"address": "amqps://eaman.swim.dsna.fr:5671"
					},
					{
						"name": "Pre-Operational",
						"description": "pre-operational network address",
						"address": "amqps://eaman.preops.swim.dsna.fr:5671"
					}
				]
			}
		],
		"serviceDescriptionReferences": {
			"implementedStandard": [
				{
					"title": "Arrival Sequence Service Performance Standard",
					"version": "June 2018 edition 1",
					"reference": "EUROCAE ED-254",
					"standardType": "SERVICE_STANDARD",
					"description": "Specifies the information service design of an Arrival Sequence Service in the context of extended arrival management (AMAN)",
					"conformanceStatement": "Additional data and associated activation mechanisms are not supported by DSNA's Sequence Arrival SWIM service, so the following optional requirements (see ED-254-REQ 0710) are not covered. \r Identifier requirement name \r ED-254-REQ 0710 Extensions \r ED-254-REQ 0040 AmanStrategyParameter data entity \r ED-254-REQ 0045 FlightAmanStrategy data entity \r ED-254-REQ 0050 FlightAmanStrategy data entity 2 \r ED-254-REQ 0060 ProposedProcedure data entity \r ED-254-REQ 0070 DepartureManagement data entity \r ED-254-REQ 0090 SupplementaryDataSelection data entity \r ED-254-REQ 0085 SupplementaryData data entity \r ED-254-REQ 0086 Supplementary data switch interpretation \r ED-254-REQ 0405 Supplementary data selection \r ED-254-REQ 0430 Supplementary data selection validity checks \r ED-254-REQ 0435 Supplementary data selection validity \r ED-254-REQ 0470 No supplementary data selection \r ED-254-REQ 0475 Supplementary data selection. \r The following requirement is only partially covered: Identifier Requirement name \r ED-254-REQ 0140 Subscription request (no extension support)"
				}
			],
			"serviceDocument": [
				{
					"description": "DSNA Service description Document.",
					"documentType": "SERVICE_SPECIFICATION",
					"reference": "https://api.dsna.fr/media/document/186",
					"title": "DSD Arrival Sequence Distribution",
					"version": "V1R0"
				}
			]
		}
	}
}