GPS Architecture - Revision history

Gema.Cueto: Updated reference ICD/SDD links

2026-04-17T12:45:18Z

Updated reference ICD/SDD links

← Older revision		Revision as of 12:45, 17 April 2026
Line 31:		Line 31:
	[[File:GPS_architecture.png\|GPS segments\|right\|thumb\|300px]]		[[File:GPS_architecture.png\|GPS segments\|right\|thumb\|300px]]

	The communication boundaries between these three segments are documented in the Interface Control Documents (ICDs):<ref>[~~http~~://~~www~~.gps.gov/technical/icwg/ GPS Interface Control Documents ICDs]</ref>		The communication boundaries between these three segments are documented in the Interface Control Documents (ICDs):<ref>[https://archive.gps.gov/technical/icwg/ GPS Interface Control Documents ICDs]</ref>
	# IS-GPS-200:<ref name=" IS-GPS-200-E ">[https://~~www~~.gps.gov/technical/icwg/IS-GPS-~~200L~~.pdf Interface Specification IS-GPS-200~~, Revision L~~]</ref> defines the requirements related to the interface between the GPS space and user segments of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2).		# IS-GPS-200:<ref name=" IS-GPS-200-E ">[https://archive.gps.gov/technical/icwg/IS-GPS-200N.pdf Interface Specification IS-GPS-200]</ref> defines the requirements related to the interface between the GPS space and user segments of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2).
	# IS-GPS-705):<ref name=" IS-GPS-705A ">[https://~~www~~.gps.gov/technical/icwg/IS-GPS-~~705G~~.pdf Interface Specification IS-GPS-705~~, Revision G~~]</ref> defines the requirements related to the interface between the GPS space and user segments of the GPS for radio frequency (RF) link 5 (L5).		# IS-GPS-705):<ref name=" IS-GPS-705A ">[https://archive.gps.gov/technical/icwg/IS-GPS-705J.pdf Interface Specification IS-GPS-705]</ref> defines the requirements related to the interface between the GPS space and user segments of the GPS for radio frequency (RF) link 5 (L5).
	# IS-GPS-800:<ref name"IS-GPS-800">[https://~~www~~.gps.gov/technical/icwg/IS-GPS-~~800G~~.pdf Interface Specification IS-GPS-800~~, Revision G~~]</ref> Defines the characteristics of the L1 Civil (L1C) signal transmitted from GPS satellites to navigation receivers on radio frequency link 1 (L1).		# IS-GPS-800:<ref name"IS-GPS-800">[https://archive.gps.gov/technical/icwg/IS-GPS-800J.pdf Interface Specification IS-GPS-800]</ref> Defines the characteristics of the L1 Civil (L1C) signal transmitted from GPS satellites to navigation receivers on radio frequency link 1 (L1).
	# IS-GPS-240::<ref name"IS-GPS-240">[https://~~www~~.gps.gov/technical/icwg/ICD-GPS-~~240C~~.pdf Interface Specification IS-GPS-240~~, Revision C~~]</ref> Defines the functional data transfer interface between the GPS Control Segment (CS) and the GPS user and user-support communities during the Operational Control System (OCS) / Architecture Evolution Plan (AEP) system era.		# IS-GPS-240::<ref name"IS-GPS-240">[https://archive.gps.gov/technical/icwg/ICD-GPS-240D.pdf Interface Specification IS-GPS-240]</ref> Defines the functional data transfer interface between the GPS Control Segment (CS) and the GPS user and user-support communities during the Operational Control System (OCS) / Architecture Evolution Plan (AEP) system era.
	# ICD-GPS-870:<ref name=" ICD-GPS-870 ">[https://~~www~~.gps.gov/technical/icwg/ICD-GPS-870E.pdf Interface Specification ICD-GPS-870~~, Revision E~~]</ref> This ICD defines the functional data transfer interface between the GPS Next Operational Control System (OCX) and the GPS user and user-support communities; captures the same interface as ICD-GPS-240, but for the OCX era.		# ICD-GPS-870:<ref name=" ICD-GPS-870 ">[https://archive.gps.gov/technical/icwg/ICD-GPS-870E.pdf Interface Specification ICD-GPS-870]</ref> This ICD defines the functional data transfer interface between the GPS Next Operational Control System (OCX) and the GPS user and user-support communities; captures the same interface as ICD-GPS-240, but for the OCX era.

	== Civil GPS Service Interface Committee ==		== Civil GPS Service Interface Committee ==

Gema.Cueto: /* Civil GPS Service Interface Committee */

2020-11-30T07:48:05Z

Civil GPS Service Interface Committee

@@ Line 38: / Line 38: @@
 # ICD-GPS-870:<ref name=" ICD-GPS-870 ">[https://www.gps.gov/technical/icwg/ICD-GPS-870E.pdf Interface Specification ICD-GPS-870, Revision E]</ref> This ICD defines the functional data transfer interface between the GPS Next Operational Control System (OCX) and the GPS user and user-support communities; captures the same interface as ICD-GPS-240, but for the OCX era.
-=== Civil GPS Service Interface Committee ===
+== Civil GPS Service Interface Committee ==
-The Civil GPS Service Interface Committee (CGSIC) is the recognized worldwide forum for effective interaction between all civil GPS users and the U.S. GPS authorities.
+The Civil GPS Service Interface Committee (CGSIC) is the recognized worldwide forum for effective interaction between all civil GPS users and the U.S. GPS authorities. The U.S. Coast Guard Navigation Center (NAVCEN) coordinates and manages CGSIC in cooperation with the Department of Transportation. The Department of Transportation established CGSIC to exchange information about GPS with the civil user community, respond to the needs of civil GPS users, and integrate GPS into civil sector applications. Information from CGSIC members and meetings is provided to United States GPS authorities for consideration in GPS policy development and GPS service operation.<ref name = "CGIC">[https://www.gps.gov/cgsic/ Civil GPS Service Interface Committee in GPS official website]</ref>
 ==Notes==

Gema.Cueto: /* Boundaries Among Segments */

2020-11-24T07:38:57Z

Boundaries Among Segments

@@ Line 37: / Line 37: @@
 # IS-GPS-240::<ref name"IS-GPS-240">[https://www.gps.gov/technical/icwg/ICD-GPS-240C.pdf Interface Specification IS-GPS-240, Revision C]</ref> Defines the functional data transfer interface between the GPS Control Segment (CS) and the GPS user and user-support communities during the Operational Control System (OCS) / Architecture Evolution Plan (AEP) system era.
 # ICD-GPS-870:<ref name=" ICD-GPS-870 ">[https://www.gps.gov/technical/icwg/ICD-GPS-870E.pdf Interface Specification ICD-GPS-870, Revision E]</ref> This ICD defines the functional data transfer interface between the GPS Next Operational Control System (OCX) and the GPS user and user-support communities; captures the same interface as ICD-GPS-240, but for the OCX era.
 [[File:GPS_triad.png|right|thumb|300px]]
-Besides these interface documents, the following three centers (privately referred as the Big Three or the GPS triad) provide a interface between GPS and any user, civilian or military:<ref>[http://www.gps.gov/news/2008/2008-04-idm-public-summary.pdf U. S. Positioning, Navigation, and Timing Interference Detection and Mitigation Plan Summary]</ref>
+Besides the interface documents, the following three centers (privately referred as the Big Three or the GPS triad) provide a interface between GPS and any user, civilian or military:<ref>[http://www.gps.gov/news/2008/2008-04-idm-public-summary.pdf U. S. Positioning, Navigation, and Timing Interference Detection and Mitigation Plan Summary]</ref>
 # '''U.S. Strategic Command GPS Operations Center (GPSOC)''': is  the Department of Defense (DoD) primary point of contact for information regarding status of GPS Precise Positioning Service (PPS) and GPS Standard Positioning Service (SPS). The GPSOC is in charge of responding to inquiries and providing information regarding the GPS constellation and the existence of space segment anomalies or issues that could result in GPS outages worldwide.
 # '''U.S. Coast Guard (USCG) Navigation Center (NAVCEN)''': is the primary interface to all civil non-aviation users of GPS. It provides capabilities for question or issue resolution regarding GPS anomalies and interference reporting, to support maritime and land users with prioritized approach for safety-of-life applications.

Gema.Cueto: /* Boundaries Among Segments */

2020-11-24T07:14:46Z

Boundaries Among Segments

← Older revision		Revision as of 07:14, 24 November 2020
Line 32:		Line 32:

	The communication boundaries between these three segments are documented in the Interface Control Documents (ICDs):<ref>[http://www.gps.gov/technical/icwg/ GPS Interface Control Documents ICDs]</ref>		The communication boundaries between these three segments are documented in the Interface Control Documents (ICDs):<ref>[http://www.gps.gov/technical/icwg/ GPS Interface Control Documents ICDs]</ref>
	# IS-GPS-200:<ref name=" IS-GPS-200-E ">[~~http~~://www.gps.gov/technical/icwg/IS-GPS-~~200E~~.pdf Interface Specification IS-GPS-200, Revision E]</ref> defines the requirements related to the interface between the ~~Space Segment (SS) of the Global Positioning System (~~GPS) and ~~the navigation User Segment (US)~~ of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2).		# IS-GPS-200:<ref name=" IS-GPS-200-E ">[https://www.gps.gov/technical/icwg/IS-GPS-200L.pdf Interface Specification IS-GPS-200, Revision L]</ref> defines the requirements related to the interface between the GPS space and user segments of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2).
	# IS-GPS-705):<ref name=" IS-GPS-705A ">[~~http~~://www.gps.gov/technical/icwg/IS-GPS-~~705A~~.pdf Interface Specification IS-GPS-~~705A~~]</ref> defines the requirements related to the interface between the ~~Space Segment~~ (SS) of the ~~Global Positioning System~~ (GPS) ~~and~~ the ~~navigation User~~ Segment (US) of the GPS ~~for radio frequency~~ (RF) ~~link 5~~ (L5).		# IS-GPS-705):<ref name=" IS-GPS-705A ">[https://www.gps.gov/technical/icwg/IS-GPS-705G.pdf Interface Specification IS-GPS-705, Revision G]</ref> defines the requirements related to the interface between the GPS space and user segments of the GPS for radio frequency (RF) link 5 (L5).
	# ICD-GPS-870:<ref name=" ICD-GPS-870 ">[~~http~~://www.gps.gov/technical/icwg~~/meetings/2011/04/28~~/ICD-GPS-~~870-IRN001~~.pdf Interface Specification ICD-GPS-870 ~~(Draft)~~]</ref> This ICD defines the ~~interfaces~~ between the Operational Control ~~Segment~~ and the GPS ~~users. The files provided by~~ the ~~Control Segment to the users are the Almanacs, Operational Advisories (OAs), Anti~~-~~Spoofing (A/S) status~~, ~~and~~ the ~~Notice Advisory to Navstar Users (NANUs)~~.		# IS-GPS-800:<ref name"IS-GPS-800">[https://www.gps.gov/technical/icwg/IS-GPS-800G.pdf Interface Specification IS-GPS-800, Revision G]</ref> Defines the characteristics of the L1 Civil (L1C) signal transmitted from GPS satellites to navigation receivers on radio frequency link 1 (L1).
			# IS-GPS-240::<ref name"IS-GPS-240">[https://www.gps.gov/technical/icwg/ICD-GPS-240C.pdf Interface Specification IS-GPS-240, Revision C]</ref> Defines the functional data transfer interface between the GPS Control Segment (CS) and the GPS user and user-support communities during the Operational Control System (OCS) / Architecture Evolution Plan (AEP) system era.
			# ICD-GPS-870:<ref name=" ICD-GPS-870 ">[https://www.gps.gov/technical/icwg/ICD-GPS-870E.pdf Interface Specification ICD-GPS-870, Revision E]</ref> This ICD defines the functional data transfer interface between the GPS Next Operational Control System (OCX) and the GPS user and user-support communities; captures the same interface as ICD-GPS-240, but for the OCX era.

	[[File:GPS_triad.png\|right\|thumb\|300px]]		[[File:GPS_triad.png\|right\|thumb\|300px]]

Gema.Cueto: /* The Ground Segment */

2020-11-24T07:06:01Z

The Ground Segment

← Older revision		Revision as of 07:06, 24 November 2020
Line 17:		Line 17:
	The [[GPS Ground Segment]] (also referred to as Control Segment) is the responsible for the proper operation of the GPS system.		The [[GPS Ground Segment]] (also referred to as Control Segment) is the responsible for the proper operation of the GPS system.

	The Ground Segment is comprised of four major subsystems: <ref name="Ground">[https://www.gps.gov/systems/gps/control/ GPS Ground Segment in ]</ref>		The Ground Segment is comprised of four major subsystems: <ref name="Ground">[https://www.gps.gov/systems/gps/control/ GPS Ground Segment in GPS official website]</ref>
	* Master Control Station (MCS)		* Master Control Station (MCS)
	* Alternate Master Control Station		* Alternate Master Control Station

Gema.Cueto: /* The Ground Segment */

2020-11-24T07:05:40Z

The Ground Segment

← Older revision		Revision as of 07:05, 24 November 2020
Line 17:		Line 17:
	The [[GPS Ground Segment]] (also referred to as Control Segment) is the responsible for the proper operation of the GPS system.		The [[GPS Ground Segment]] (also referred to as Control Segment) is the responsible for the proper operation of the GPS system.

	The ~~GPS Control~~ Segment is ~~composed by a network~~ of ~~Monitor Stations~~ (MS)~~, a~~ Master Control Station (~~MCS~~) ~~and the Ground Antennas~~ (GA).		The Ground Segment is comprised of four major subsystems: <ref name="Ground">[https://www.gps.gov/systems/gps/control/ GPS Ground Segment in ]</ref>
			* Master Control Station (MCS)
			* Alternate Master Control Station
			* Network of ground antennas (GAs),
			* Network of globally-distributed monitor stations (MSs).

	The Master Control Station (MCS) processes the measurements received by the Monitor Stations (MS) to estimate satellite orbits (ephemerides) and clock errors, among other parameters, and to generate the navigation message. These corrections and the navigation message are uploaded to the satellites through the Ground Antennas, which are co-located in four of the Monitor stations (Ascension Island, Cape Canaveral, Diego Garcia, and Kwajalein).		The Master Control Station (MCS) processes the measurements received by the Monitor Stations (MS) to estimate satellite orbits (ephemerides) and clock errors, among other parameters, and to generate the navigation message. These corrections and the navigation message are uploaded to the satellites through the Ground Antennas, which are co-located in four of the Monitor stations (Ascension Island, Cape Canaveral, Diego Garcia, and Kwajalein).

Gema.Cueto: /* The Space Segment */

2020-11-24T07:02:47Z

The Space Segment

← Older revision		Revision as of 07:02, 24 November 2020
Line 12:		Line 12:
	The main functions of the [[GPS Space Segment]] are to transmit radio-navigation signals with a specific signal structure, and to store and retransmit the navigation message sent by the Control Segment. These transmissions are controlled by highly stable atomic clocks on board the satellites.		The main functions of the [[GPS Space Segment]] are to transmit radio-navigation signals with a specific signal structure, and to store and retransmit the navigation message sent by the Control Segment. These transmissions are controlled by highly stable atomic clocks on board the satellites.

	The ~~GPS Space Segment~~ is ~~formed by a satellite constellation with enough satellites~~ to ~~ensure that~~ the ~~users will have,~~ at least, ~~4 simultaneous~~ satellites ~~in view from any point at~~ the ~~Earth surface at any time~~.		The United States is committed to maintaining the availability of at least 24 operational GPS satellites, 95% of the time. To ensure this commitment, the Air Force has been flying 31 operational GPS satellites for the past few years.<ref name="Space">[https://www.gps.gov/systems/gps/space/ GPS Space Segment information in GPS official website]</ref>

	==The Ground Segment==		==The Ground Segment==

Filipe.Pelica: Included editor logo.

2014-09-18T15:21:43Z

Included editor logo.

← Older revision		Revision as of 15:21, 18 September 2014
Line 4:		Line 4:
	\|Level=Basic		\|Level=Basic
	\|YearOfPublication=2011		\|YearOfPublication=2011
			\|Logo=GMV
	\|Title={{PAGENAME}}		\|Title={{PAGENAME}}
	}}		}}

Filipe.Pelica: fixed broken link

2014-05-29T13:44:18Z

fixed broken link

← Older revision		Revision as of 13:44, 29 May 2014
Line 33:		Line 33:
	[[File:GPS_triad.png\|right\|thumb\|300px]]		[[File:GPS_triad.png\|right\|thumb\|300px]]

	Besides these interface documents, the following three centers (privately referred as the Big Three or the GPS triad) provide a interface between GPS and any user, civilian or military:<ref>[http://www.~~pnt~~.gov/~~public~~/~~docs~~/2008~~/idmpublicsummary~~.pdf U. S. Positioning, Navigation, and Timing Interference Detection and Mitigation Plan Summary]</ref>		Besides these interface documents, the following three centers (privately referred as the Big Three or the GPS triad) provide a interface between GPS and any user, civilian or military:<ref>[http://www.gps.gov/news/2008/2008-04-idm-public-summary.pdf U. S. Positioning, Navigation, and Timing Interference Detection and Mitigation Plan Summary]</ref>
	# '''U.S. Strategic Command GPS Operations Center (GPSOC)''': is the Department of Defense (DoD) primary point of contact for information regarding status of GPS Precise Positioning Service (PPS) and GPS Standard Positioning Service (SPS). The GPSOC is in charge of responding to inquiries and providing information regarding the GPS constellation and the existence of space segment anomalies or issues that could result in GPS outages worldwide.		# '''U.S. Strategic Command GPS Operations Center (GPSOC)''': is the Department of Defense (DoD) primary point of contact for information regarding status of GPS Precise Positioning Service (PPS) and GPS Standard Positioning Service (SPS). The GPSOC is in charge of responding to inquiries and providing information regarding the GPS constellation and the existence of space segment anomalies or issues that could result in GPS outages worldwide.
	# '''U.S. Coast Guard (USCG) Navigation Center (NAVCEN)''': is the primary interface to all civil non-aviation users of GPS. It provides capabilities for question or issue resolution regarding GPS anomalies and interference reporting, to support maritime and land users with prioritized approach for safety-of-life applications.		# '''U.S. Coast Guard (USCG) Navigation Center (NAVCEN)''': is the primary interface to all civil non-aviation users of GPS. It provides capabilities for question or issue resolution regarding GPS anomalies and interference reporting, to support maritime and land users with prioritized approach for safety-of-life applications.

Timo.Kouwenhoven: /* Boundaries Among Segments */

2012-03-18T12:33:55Z

Boundaries Among Segments

← Older revision		Revision as of 12:33, 18 March 2012
Line 29:		Line 29:
	# IS-GPS-200:<ref name=" IS-GPS-200-E ">[http://www.gps.gov/technical/icwg/IS-GPS-200E.pdf Interface Specification IS-GPS-200, Revision E]</ref> defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the navigation User Segment (US) of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2).		# IS-GPS-200:<ref name=" IS-GPS-200-E ">[http://www.gps.gov/technical/icwg/IS-GPS-200E.pdf Interface Specification IS-GPS-200, Revision E]</ref> defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the navigation User Segment (US) of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2).
	# IS-GPS-705):<ref name=" IS-GPS-705A ">[http://www.gps.gov/technical/icwg/IS-GPS-705A.pdf Interface Specification IS-GPS-705A]</ref> defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the navigation User Segment (US) of the GPS for radio frequency (RF) link 5 (L5).		# IS-GPS-705):<ref name=" IS-GPS-705A ">[http://www.gps.gov/technical/icwg/IS-GPS-705A.pdf Interface Specification IS-GPS-705A]</ref> defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the navigation User Segment (US) of the GPS for radio frequency (RF) link 5 (L5).
	# ICD-GPS-870:<ref name=" ICD-GPS-870 ">[http://www.gps.gov/technical/icwg/meetings/2011/04/28/ICD-GPS-870-IRN001.pdf Interface Specification ICD-GPS-870 (Draft)]</ref> This ICD defines the interfaces between the Operational Control Segment and the GPS users. The files provided by the Control Segment to the users are the Almanacs, Operational Advisories (OAs), Anti-Spoofing (A-S) status, and the Notice Advisory to Navstar Users (NANUs).		# ICD-GPS-870:<ref name=" ICD-GPS-870 ">[http://www.gps.gov/technical/icwg/meetings/2011/04/28/ICD-GPS-870-IRN001.pdf Interface Specification ICD-GPS-870 (Draft)]</ref> This ICD defines the interfaces between the Operational Control Segment and the GPS users. The files provided by the Control Segment to the users are the Almanacs, Operational Advisories (OAs), Anti-Spoofing (A/S) status, and the Notice Advisory to Navstar Users (NANUs).

	[[File:GPS_triad.png\|right\|thumb\|300px]]		[[File:GPS_triad.png\|right\|thumb\|300px]]