EGNOS Data Access Service (EDAS) - Revision history

Gema.Cueto: Updated reference ICD/SDD links

2026-04-19T21:13:31Z

Updated reference ICD/SDD links

Gema.Cueto: /* EDAS Architecture */

2020-06-05T07:07:04Z

EDAS Architecture

← Older revision		Revision as of 07:07, 5 June 2020
Line 64:		Line 64:
	==EDAS Architecture ==		==EDAS Architecture ==
	[[File:EDAS_Architecture.png \| EDAS high level architecture<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]		[[File:EDAS_Architecture.png \| EDAS high level architecture<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]


	The EDAS architecture is composed of the following elements:		The EDAS architecture is composed of the following elements:

Gema.Cueto: /* EDAS Architecture */

2020-06-05T07:06:29Z

EDAS Architecture

← Older revision		Revision as of 07:06, 5 June 2020
Line 71:		Line 71:
	The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:		The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:

	* EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).		-EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).

	* The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.		-The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.

	[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]		[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]

Gema.Cueto: /* EDAS Architecture */

2020-06-05T06:57:53Z

EDAS Architecture

← Older revision		Revision as of 06:57, 5 June 2020
Line 71:		Line 71:
	The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:		The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:

	* EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).		* EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).

	* The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.		* The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.

Gema.Cueto: /* EDAS Architecture */

2020-06-05T06:54:07Z

EDAS Architecture

← Older revision		Revision as of 06:54, 5 June 2020
Line 68:		Line 68:
	EDAS Client Software (CS): represents the functional interface between the EGNOS Data Server (EDS) and the Service Provider (SP) and it provides authentication, data communication and quota and integrity management		EDAS Client Software (CS): represents the functional interface between the EGNOS Data Server (EDS) and the Service Provider (SP) and it provides authentication, data communication and quota and integrity management
	EGNOS Data Server: transforms data received from INSPIRE (a dedicated interface to access to EGNOS data) from the EGNOS proprietary format to ASN.1 (SL0) and RTCM (SL1). For each message received EDS creates one or more RTCM messages and one ASN.1 message. In addition it delivers information to the CS about the status of the messages quota contracted by the SP.		EGNOS Data Server: transforms data received from INSPIRE (a dedicated interface to access to EGNOS data) from the EGNOS proprietary format to ASN.1 (SL0) and RTCM (SL1). For each message received EDS creates one or more RTCM messages and one ASN.1 message. In addition it delivers information to the CS about the status of the messages quota contracted by the SP.


	The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:		The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:

Gema.Cueto: /* EDAS Architecture */

2020-06-05T06:53:29Z

EDAS Architecture

← Older revision		Revision as of 06:53, 5 June 2020
Line 72:		Line 72:
	The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:		The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:

	# EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).		* EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).

	# The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.		* The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.

	[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]		[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]

Gema.Cueto: /* EDAS Architecture */

2020-06-05T06:52:58Z

EDAS Architecture

← Older revision		Revision as of 06:52, 5 June 2020
Line 70:		Line 70:


			The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:

			# EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).







	The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>:
	# EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).
	# The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.		# The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.

Gema.Cueto: /* EDAS Based Applications */

2020-06-05T06:52:14Z

EDAS Based Applications

← Older revision		Revision as of 06:52, 5 June 2020
Line 172:		Line 172:

	EDAS has proved to play a role within the identified market segments considered in the [[EGNOS Commercial Data Distribution Service\| EGNOS CDDS]]. There is a continuously growing EDAS user community and there are a wide range of applications that provide EDAS-based services that comprise the [[EGNOS Commercial Data Distribution Service\| CDDS]].		EDAS has proved to play a role within the identified market segments considered in the [[EGNOS Commercial Data Distribution Service\| EGNOS CDDS]]. There is a continuously growing EDAS user community and there are a wide range of applications that provide EDAS-based services that comprise the [[EGNOS Commercial Data Distribution Service\| CDDS]].
	Furthermore, the EDAS-N project ~~has been approved. This project is going to examine~~ how the current EGNOS Data Access Service (EDAS) should evolve to meet user needs between 2020 and 2030. On the basis of its analysis, it proposes 8 new EDAS services.		Furthermore, the EDAS-N project examined how the current EGNOS Data Access Service (EDAS) should evolve to meet user needs between 2020 and 2030. On the basis of its analysis, it proposes 8 new EDAS services.
	As EDAS is expected to disseminate EGNOS V3 data over this period, the analysis focuses on what additional features could help generate new EDAS services for users and service providers.		As EDAS is expected to disseminate EGNOS V3 data over this period, the analysis focuses on what additional features could help generate new EDAS services for users and service providers.
	The EDAS-N project defined how the current EGNOS EDAS should evolve to meet more demanding user needs between 2020 and 2030. The analysis looked at potential new EDAS services and their market uptake. It also estimated their capital expenditure and operating expense. The project proposed a final set of 8 new EDAS-based services, and defined their implementation schedule.		The EDAS-N project defined how the current EGNOS EDAS should evolve to meet more demanding user needs between 2020 and 2030. The analysis looked at potential new EDAS services and their market uptake. It also estimated their capital expenditure and operating expense. The project proposed a final set of 8 new EDAS-based services, and defined their implementation schedule.
	The uptake of the next generation of EDAS is estimated at 178 direct users (mainly service providers) and 350,000 indirect users by 2030. <ref name=" EGNOS data access service">[https://www.gsa.europa.eu/egnos-data-access-service EGNOS Data Access Service]</ref>		The uptake of the next generation of EDAS is estimated at 178 direct users (mainly service providers) and 350,000 indirect users by 2030. <ref name=" EGNOS data access service">[https://www.gsa.europa.eu/egnos-data-access-service EGNOS Data Access Service]</ref>


	==Notes==		==Notes==

Gema.Cueto at 06:50, 5 June 2020

2020-06-05T06:50:11Z

← Older revision		Revision as of 06:50, 5 June 2020
Line 14:		Line 14:

	In fact, EDAS to users the possibility to access the EGNOS data even when the Signal In Space (SIS) is not available due to lack of visibility of the satellites (Urban Canyon, Indoor, ...).		In fact, EDAS to users the possibility to access the EGNOS data even when the Signal In Space (SIS) is not available due to lack of visibility of the satellites (Urban Canyon, Indoor, ...).
	EDAS was officialy declared available on July 2012. The last release of the Service Definition Document (SDD) is available [https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf here]~~since July 2012~~.		EDAS was officialy declared available on July 2012. The last release of the Service Definition Document (SDD) is available [https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf here].

	Since April 2013, four new EDAS Services have been introduced: Data Filtering, FTP, SISNET and NTRIP.<ref name=" EDAS Services">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/ EDAS Services]</ref>		Since April 2013, four new EDAS Services have been introduced: Data Filtering, FTP, SISNET and NTRIP.<ref name=" EDAS Services">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/ EDAS Services]</ref>

Gema.Cueto: /* EDAS Architecture */

2020-06-05T06:04:32Z

EDAS Architecture

← Older revision		Revision as of 06:04, 5 June 2020
Line 63:		Line 63:

	==EDAS Architecture ==		==EDAS Architecture ==
	[[File:EDAS_Architecture.png \| EDAS high level architecture.\|380px\|thumb\|left]]		[[File:EDAS_Architecture.png \| EDAS high level architecture<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]

	The EDAS architecture is composed of the following elements:		The EDAS architecture is composed of the following elements:
Line 82:		Line 82:
	# The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.		# The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.

	[[File:EDAS_diagram.png\| EDAS Services Diagram.\|380px\|thumb\|left]]		[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>\|380px\|thumb\|left]]

	The EDAS Client SW is a platform-independent interface element allowing the connection of Users to EDAS system for reception of Main Data Streams. This tool is only available after registration and users make use of it to obtain the EGNOS products in real-time from the EDAS system, then perform the necessary processing and finally provide services to end users via non-GEO means.		The EDAS Client SW is a platform-independent interface element allowing the connection of Users to EDAS system for reception of Main Data Streams. This tool is only available after registration and users make use of it to obtain the EGNOS products in real-time from the EDAS system, then perform the necessary processing and finally provide services to end users via non-GEO means.

← Older revision		Revision as of 21:13, 19 April 2026
Line 11:		Line 11:
	In 2006, the European Commission through the GJU (now superseded by the European GNSS Agency, the [http://www.gsa.europa.eu GSA]) commissioned the EDAS system. EDAS allows any registered entity to plug into EGNOS to receive the internal data collected, generated and delivered by EGNOS for free. Although the idea of providing GNSS data streams in real time is far from being new, EDAS has some key differentiators, the most important one is probably the service reliability. Other benefits that EDAS brings are the high data rate (1Hz), the dissemination of the EGNOS message broadcast by each GEO satellite and the provision of GLONASS raw measurements. Additionally EDAS provides the raw data of the Ranging and Integrity Monitoring Stations (RIMS) and Navigation Land Earth Stations (NLES).<ref name=" EDAS Beta test findings"/>		In 2006, the European Commission through the GJU (now superseded by the European GNSS Agency, the [http://www.gsa.europa.eu GSA]) commissioned the EDAS system. EDAS allows any registered entity to plug into EGNOS to receive the internal data collected, generated and delivered by EGNOS for free. Although the idea of providing GNSS data streams in real time is far from being new, EDAS has some key differentiators, the most important one is probably the service reliability. Other benefits that EDAS brings are the high data rate (1Hz), the dissemination of the EGNOS message broadcast by each GEO satellite and the provision of GLONASS raw measurements. Additionally EDAS provides the raw data of the Ranging and Integrity Monitoring Stations (RIMS) and Navigation Land Earth Stations (NLES).<ref name=" EDAS Beta test findings"/>

	EDAS provides ground-based access to EGNOS data, through a collection of services, which are accessible to registered users through the Internet and are oriented to users in different domains of application such as Location Based Services (LBS), a broad range of services in professional GNSS markets, Assisted-GNSS (A-GNSS) concepts, and related R&D activities.<ref name="EGNOS EDAS SDD">[https://egnos~~-user-support~~.~~essp~~-~~sas~~.eu~~/new_egnos_ops~~/sites/default/files/~~library/official_docs~~/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref>		EDAS provides ground-based access to EGNOS data, through a collection of services, which are accessible to registered users through the Internet and are oriented to users in different domains of application such as Location Based Services (LBS), a broad range of services in professional GNSS markets, Assisted-GNSS (A-GNSS) concepts, and related R&D activities.<ref name="EGNOS EDAS SDD">[https://egnos.gsc-europa.eu/sites/default/files/documents/egnos_edas_sdd_in_force.pdf?v=1734519406 EGNOS EDAS SDD]</ref>

	In fact, EDAS to users the possibility to access the EGNOS data even when the Signal In Space (SIS) is not available due to lack of visibility of the satellites (Urban Canyon, Indoor, ...).		In fact, EDAS to users the possibility to access the EGNOS data even when the Signal In Space (SIS) is not available due to lack of visibility of the satellites (Urban Canyon, Indoor, ...).
	EDAS was officialy declared available on July 2012. The last release of the Service Definition Document (SDD) is available [https://egnos~~-user-support~~.~~essp~~-~~sas~~.eu~~/new_egnos_ops~~/sites/default/files/~~library/official_docs~~/egnos_edas_sdd_in_force.pdf here].		EDAS was officialy declared available on July 2012. The last release of the Service Definition Document (SDD) is available [https://egnos.gsc-europa.eu/sites/default/files/documents/egnos_edas_sdd_in_force.pdf?v=1734519406 here].

	Since April 2013, four new EDAS Services have been introduced: Data Filtering, FTP, SISNET and NTRIP.<ref name=" EDAS Services">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/ EDAS Services]</ref>		Since April 2013, four new EDAS Services have been introduced: Data Filtering, FTP, SISNET and NTRIP.<ref name=" EDAS Services">[https://egnos-user-support.essp-sas.eu/new_egnos_ops/ EDAS Services]</ref>
Line 29:		Line 29:
	EDAS is not an end-user product. The data streams can be used by Service Providers to generate added value to the final customers by improving the availability and accuracy of the positioning. For instance, one may think of a Service Provider that takes the EGNOS message from EDAS and disseminates it to its customers through the Internet or GPRS.		EDAS is not an end-user product. The data streams can be used by Service Providers to generate added value to the final customers by improving the availability and accuracy of the positioning. For instance, one may think of a Service Provider that takes the EGNOS message from EDAS and disseminates it to its customers through the Internet or GPRS.

	The EDAS services are classified as Main Data Stream services (Service Level 0, Service Level 1, and Service Level 2) and Added Value Services (Data Filtering, FTP, SISNet and Ntrip).<ref name="EGNOS EDAS SDD"~~>[https:~~/~~/egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>		The EDAS services are classified as Main Data Stream services (Service Level 0, Service Level 1, and Service Level 2) and Added Value Services (Data Filtering, FTP, SISNet and Ntrip).<ref name="EGNOS EDAS SDD"/>

	The main types of data provided by the main data stream Services are:<ref name=" EDAS Services"/>		The main types of data provided by the main data stream Services are:<ref name=" EDAS Services"/>
Line 47:		Line 47:
	Specific guidelines for the access and usage of the EDAS FTP service, including naming conventions and folder structure (EDAS FTP-User Information Package), are available at the EDAS specific section of the [http://egnos-user-support.essp-sas.eu/ EGNOS User Support Website].		Specific guidelines for the access and usage of the EDAS FTP service, including naming conventions and folder structure (EDAS FTP-User Information Package), are available at the EDAS specific section of the [http://egnos-user-support.essp-sas.eu/ EGNOS User Support Website].

	[[File:EDAS_FTP.png \| EDAS FTP service<ref name="EGNOS EDAS SDD"~~>[https:~~/~~/egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>\|380px\|thumb\|centre]]		[[File:EDAS_FTP.png \| EDAS FTP service<ref name="EGNOS EDAS SDD"/>\|380px\|thumb\|centre]]

	*EDAS NTRIP Service:		*EDAS NTRIP Service:
Line 54:		Line 54:
	NTRIP is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.(EDAS Ntrip – User Information Package) are available at the EDAS specific section of the [http://egnos-user-support.essp-sas.eu/ EGNOS User Support Website].		NTRIP is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.(EDAS Ntrip – User Information Package) are available at the EDAS specific section of the [http://egnos-user-support.essp-sas.eu/ EGNOS User Support Website].

	[[File:EDAS Ntrip.png \| EDAS Ntrip Message Types <ref name="EGNOS EDAS SDD"~~>[https:~~/~~/egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>\|380px\|thumb\|centre]]		[[File:EDAS Ntrip.png \| EDAS Ntrip Message Types <ref name="EGNOS EDAS SDD"/>\|380px\|thumb\|centre]]

	*EDAS Data Filtering Service:		*EDAS Data Filtering Service:
Line 63:		Line 63:

	==EDAS Architecture ==		==EDAS Architecture ==
	[[File:EDAS_Architecture.png \| EDAS high level architecture<ref name="EGNOS EDAS SDD"~~>[https:~~/~~/egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>\|380px\|thumb\|left]]		[[File:EDAS_Architecture.png \| EDAS high level architecture<ref name="EGNOS EDAS SDD"/>\|380px\|thumb\|left]]


Line 70:		Line 70:
	EGNOS Data Server: transforms data received from INSPIRE (a dedicated interface to access to EGNOS data) from the EGNOS proprietary format to ASN.1 (SL0) and RTCM (SL1). For each message received EDS creates one or more RTCM messages and one ASN.1 message. In addition it delivers information to the CS about the status of the messages quota contracted by the SP.		EGNOS Data Server: transforms data received from INSPIRE (a dedicated interface to access to EGNOS data) from the EGNOS proprietary format to ASN.1 (SL0) and RTCM (SL1). For each message received EDS creates one or more RTCM messages and one ASN.1 message. In addition it delivers information to the CS about the status of the messages quota contracted by the SP.

	The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD"~~>[https:~~/~~/egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>:		The EDAS architecture is decomposed into two separate elements<ref name="EGNOS EDAS SDD"/>:

	-EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).		-EDAS system, implementing the interface with the EGNOS infrastructure and performing the necessary data processing to provide the different EDAS Services through Internet. Users can connect directly to EDAS system for some of the services which are based on standard protocols (FTP, SISNET and NTRIP).
Line 76:		Line 76:
	-The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.		-The EDAS Client SW, resident at user level, implementing the external interface of some of the EDAS services (EDAS Service Level 0, Service Level 2 and EDAS Data Filtering Service). The EDAS Client SW is responsible for basic security functions and for the interface with the EDAS system through the appropriate communication means.

	[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD"~~>[https:~~/~~/egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs/egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>\|380px\|thumb\|left]]		[[File:EDAS_diagram.png\| EDAS Services Diagram<ref name="EGNOS EDAS SDD"/>\|380px\|thumb\|left]]

	The EDAS Client SW is a platform-independent interface element allowing the connection of Users to EDAS system for reception of Main Data Streams. This tool is only available after registration and users make use of it to obtain the EGNOS products in real-time from the EDAS system, then perform the necessary processing and finally provide services to end users via non-GEO means.		The EDAS Client SW is a platform-independent interface element allowing the connection of Users to EDAS system for reception of Main Data Streams. This tool is only available after registration and users make use of it to obtain the EGNOS products in real-time from the EDAS system, then perform the necessary processing and finally provide services to end users via non-GEO means.
Line 87:		Line 87:
	==EDAS Performance==		==EDAS Performance==
	This section presents the EDAS Services performance in terms of availability and latency:		This section presents the EDAS Services performance in terms of availability and latency:
	* Availability: percentage of the time in which an EDAS service is delivering data according to specifications. The availability of EDAS services is measured at the EDAS system output (excluding external network performance).<ref name="EGNOS EDAS SDD"~~>[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs~~/~~egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>		* Availability: percentage of the time in which an EDAS service is delivering data according to specifications. The availability of EDAS services is measured at the EDAS system output (excluding external network performance).<ref name="EGNOS EDAS SDD"/>
	* Latency: time elapsed since the transmission of the last bit of the navigation message from the space segment (EGNOS and GPS/GLONASS satellites) until data leave the EDAS system (formatted according to the corresponding service level specification). EDAS latency is a one way parameter defined for real-time services.<ref name="EGNOS EDAS SDD"~~>[https://egnos-user-support.essp-sas.eu/new_egnos_ops/sites/default/files/library/official_docs~~/~~egnos_edas_sdd_in_force.pdf EGNOS EDAS SDD]</ref~~>		* Latency: time elapsed since the transmission of the last bit of the navigation message from the space segment (EGNOS and GPS/GLONASS satellites) until data leave the EDAS system (formatted according to the corresponding service level specification). EDAS latency is a one way parameter defined for real-time services.<ref name="EGNOS EDAS SDD"/>

	===EDAS Services Availability===		===EDAS Services Availability===