<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>system infrastructure/technology Archives - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</title>
	<atom:link href="https://insidegnss.com/category/main-categories/system-infrastructure-technology/feed/" rel="self" type="application/rss+xml" />
	<link>https://insidegnss.com/category/main-categories/system-infrastructure-technology/</link>
	<description>Global Navigation Satellite Systems Engineering, Policy, and Design</description>
	<lastBuildDate>Thu, 09 Jul 2020 17:53:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>

<image>
	<url>https://insidegnss.com/wp-content/uploads/2017/12/site-icon.png</url>
	<title>system infrastructure/technology Archives - Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</title>
	<link>https://insidegnss.com/category/main-categories/system-infrastructure-technology/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Ensuring PNT for All</title>
		<link>https://insidegnss.com/ensuring-pnt-for-all/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Tue, 26 Sep 2017 08:59:27 +0000</pubDate>
				<category><![CDATA[201708 September/October 2017]]></category>
		<category><![CDATA[civil]]></category>
		<category><![CDATA[Column]]></category>
		<category><![CDATA[GNSS (all systems)]]></category>
		<category><![CDATA[Military - Defense]]></category>
		<category><![CDATA[PNT]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[receiver]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[Thinking Aloud]]></category>
		<guid isPermaLink="false">http://insidegnss.com/2017/09/26/ensuring-pnt-for-all/</guid>

					<description><![CDATA[<p>Today’s headlines frame my thoughts about securing GNSS assets, which one expert has characterized as our “least visible and most vulnerable infrastructure.” Today’s...</p>
<p>The post <a href="https://insidegnss.com/ensuring-pnt-for-all/">Ensuring PNT for All</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>
Today’s headlines frame my thoughts about securing GNSS assets, which one expert has characterized as our “least visible and most vulnerable infrastructure.”
</p>
<p><span id="more-22945"></span></p>
<p>
Today’s headlines frame my thoughts about securing GNSS assets, which one expert has characterized as our “least visible and most vulnerable infrastructure.”
</p>
<p>
In the Columbia River Gorge, a National Scenic Area spanning the Washington-Oregon border, a 15-year-old boy has been accused of intentionally tossing fireworks into tinder-dry grass thereby starting a (thus far) 33,000-acre forest fire that has devastated a natural treasure. Meanwhile, in the latest incident of large-scale identity theft, credit-rating agency Equifax has belatedly acknowledged a months-long breach of its database in which 143 million personal records were reportedly accessed.
</p>
<p>
In one case, an individual — obliviously or purposefully — creates outsized havoc, in the other, a skilled team of professional thieves disrupt a global enterprise and endanger the financial well-being of millions.
</p>
<p>
Of course, we have headlines closer to the point, such as <a href="http://insidegnss.com/news/reports-of-mass-gps-spoofing-attack-in-the-black-sea-strengthen-calls-for-pnt-backup/">“Reports of Mass GPS Spoofing Attack in the Black Sea,”</a> or <a href="http://insidegnss.com/news/south-korea-developing-an-eloran-network-to-protect-ships-from-cyber-attacks/">“South Korea developing eLoran Network to Protect Ships”</a> from North Korean GPS jamming.
</p>
<p>
These latter incidents, of course, arise from state-sponsored or –enabled actions. But, as with the Columbia gorge fire, personal behaviors — often harder to detect and prevent — can similarly afflict GNSS capabilities. In recent years, considerable attention has focused on the use of small GNSS jammers, also known as “personal privacy devices.” Perhaps the best-known case is that of a trucker trying to jam his vehicle’s own receiver who interrupted GPS-aided landing operations at Newark International Airport.
</p>
<p>
As the articles on jamming and spoofing mitigation in this issue of <em>Inside GNSS</em> reflect, the motives and methods of perpetrators vary. But, given the natural progression of information-sharing and widening expertise in GNSS — along with our cultural soft spot for making heroes out of rebels and outlaws — we can probably assume that the trend toward disruption will only get worse.
</p>
<p>
Some GNSS user groups have struck out on their own to ensure the security of their constituencies and their particular needs. Military users benefit from a variety of alternative PNT technologies such as geomagnetic mapping, vision- and image-based navigation, and chip-scale atomic clocks and inertial measurement units. The U.S. Federal Aviation Administration has decided to retain, for the time being, a minimum operational network of VHF omnidirectional range (VOR) facilities originally planned to be phased out with the introduction of GNSS.
</p>
<p>
Over time, some of these alternatives may migrate into the commercial and professional space — then again, they may not. And the vast majority of individual GNSS consumers have no organizations to advocate for their needs.
</p>
<p>
So, what is to be done? How can we ensure that the positioning, navigation, and timing (PNT) utility is available to all users, and not just those sectors with the resources to develop solutions for themselves? The future of location-based applications and enterprise — and the associated economic benefits — depend on a satisfactory answer to that question.
</p>
<p>
Multi-level threats clearly require multi-tiered responses that fit the corresponding scope and scale of different domains. At the system level, GNSS providers are exploring such measures as encryption, signal authentication, stronger signal power, and advanced signal designs.
</p>
<p>
National and international legal/initiatives include such efforts as regulating the sale and use of GNSS jammers and spoofers. Alternative PNT systems — for example, enhanced Loran (eLoran) — represent a potential multinational approach to the problem.
</p>
<p>
At the level of user equipment, several GNSS manufacturers are incorporating interference detection and mitigation (IDM) and antispoofing capabilities into proprietary products.
</p>
<p>
The variety of these initiatives and their advocates illustrates the breadth of concern about assured PNT, but also reflect the fractured nature of responses to the threats to GNSS. The situation calls for leadership with the expertise and stature to bring comprehensive solutions before the wider GNSS community.
</p>
<p>
The International Committee on GNSS has the membership and forum, if not yet the clear mandate, to impose such solutions globally. At the national level, the U.S. Space-Based PNT Executive Committee assisted by its expert advisory panel seems the most likely candidate for this role.
</p>
<div class='pdfclass'><a target='_blank' class='specialpdf' href='http://insidegnss.com/wp-content/uploads/2018/01/sepoct17-THINKING.pdf'>Download this article (PDF)</a></div>
<p>The post <a href="https://insidegnss.com/ensuring-pnt-for-all/">Ensuring PNT for All</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Turn NextGen into ThisGen</title>
		<link>https://insidegnss.com/turn-nextgen-into-thisgen/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Sun, 06 Aug 2017 19:56:41 +0000</pubDate>
				<category><![CDATA[201706 July/August 2017]]></category>
		<category><![CDATA[Aviation]]></category>
		<category><![CDATA[Column]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[military]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[Thinking Aloud]]></category>
		<guid isPermaLink="false">http://insidegnss.com/2017/08/06/turn-nextgen-into-thisgen/</guid>

					<description><![CDATA[<p>The Next Generation Air Transportation System (NextGen) is setting no records in government efficiency or speed. So, it’s time for the Federal Aviation...</p>
<p>The post <a href="https://insidegnss.com/turn-nextgen-into-thisgen/">Turn NextGen into ThisGen</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The Next Generation Air Transportation System (NextGen) is setting no records in government efficiency or speed. So, it’s time for the Federal Aviation Administration (FAA), Congress, and partner agencies to change the verb tense and transform NextGen into an operational ThisGen.</p>
<p><span id="more-22926"></span></p>
<p>Like many massive infrastructure projects, the NextGen program has suffered numerous setbacks, many self-inflicted. An August 2016 report from the Office of the Inspector General (OIG) of FAA’s parent, the Department of Transportation, noted, “FAA’s plans have proven to be unrealistic, lacking stable investment priorities and requirements for NextGen systems.”</p>
<p>With more than $7 billion in modernization funds already expended, the FAA is currently projecting costs of $14.8 billion from Fiscal Year (FY) 2015 to 2030, according to the OIG report. Despite the characterization of NextGen as being wildly over budget, however, total cost estimates for the program “have evolved, but not increased markedly since FY 2004,” the OIG says. The president’s proposed FY18 budget requests $988 million for continued NextGen development, down from $1.055 billion in FY17.</p>
<p>As other infrastructure modernization efforts involving GNSS have shown, getting the technology right is the easy part. The Global Positioning System has a 22-year operational history to bolster expectations about its performance, which has continued to improve steadily. The arrival of other GNSS systems has only strengthened this technological resource.</p>
<p>Instead, the sticking points arise from such issues as enterprise architecture, systems integration with other technologies such as data communications and weather forecasting, interagency cooperation, human factors, cybersecurity, operational procedures, and regulatory updates to accommodate modernization.</p>
<p>Like America’s healthcare insurance system, modernization of the National Air Space is more complicated than casual observers might think.</p>
<p>NextGen needs to happen, first, because it will pay off in improved aviation operations, greater capacity, and better use of the crowded National Air Space (NAS). FAA modernization has already provided $2.7 billion in savings from such things as less usage of fuel and is expected to provide another $160 billion in benefits through NextGen’s targeted 2025 completion date.</p>
<p>Efforts so far have barely scratched the surface of what GNSS and other NextGen technologies can provide.</p>
<p>However, the need to get NextGen back on track has gained heightened urgency with the renewed push to privatize U.S. air traffic control (ATC). On June 27, the House Transportation and Infrastructure Committee approved a measure that would turn the nation’s taxpayer-funded ATC infrastructure and operations (carried out by 30,000 public employees) over to a nonprofit organization controlled by aviation industry representatives.</p>
<p>The measure, previously backed unsuccessfully by House Transportation Committee chairman Bill Shuster, has gained important support from President Donald Trump.</p>
<p>NAS modernization is a perhaps uniquely complicated undertaking with many elements subject to inevitable changes as technologies and operational environments (including the political and economic context) evolve. NextGen is a moving target being shot at from a moving platform.</p>
<p>Attempting to privatize air traffic control at this point in the process would throw a very large monkey wrench into some very delicate works in progress. As Senate Appropriations Committee Chairman Thad Cochran (R-Miss.) and committee Vice Chairman Sen. Patrick Leahy (D-Vt.) said in a February 28 letter to Senate Commerce, Science and Transportation Committee Chairman Sen. John Thune, “If air traffic control were separated during this critical period of technological advancement, the progress already being made to synchronize investment from government and industry related to safety, equipage, training, operational changes, and overall integration would be lost.”</p>
<p>And the FAA, not some newly convened group dominated by stakeholders with their own interests in mind, should continue to lead this project. As a special National Research Council committee concluded in a congressionally mandated analysis of NextGen in 2015, “Replacing or upgrading systems while continuously and safely operating the whole system is an intricate undertaking, a process that the FAA seems to have mastered.”</p>
<div class="pdfclass"><a class="specialpdf" href="http://insidegnss.com/wp-content/uploads/2018/01/julyaug17-THINKING.pdf" target="_blank" rel="noopener">Download this article (PDF)</a></div>
<p>The post <a href="https://insidegnss.com/turn-nextgen-into-thisgen/">Turn NextGen into ThisGen</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Positioning Technology in Australia Gets a $12 Million Boost</title>
		<link>https://insidegnss.com/positioning-technology-in-australia-gets-a-12-million-boost/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Mon, 23 Jan 2017 21:52:20 +0000</pubDate>
				<category><![CDATA[agriculture]]></category>
		<category><![CDATA[civil]]></category>
		<category><![CDATA[commercial]]></category>
		<category><![CDATA[GNSS (all systems)]]></category>
		<category><![CDATA[high precision positioning]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[legacy-application]]></category>
		<category><![CDATA[location based services]]></category>
		<category><![CDATA[Marine]]></category>
		<category><![CDATA[Survey and Mapping]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/positioning-technology-in-australia-gets-a-12-million-boost/</guid>

					<description><![CDATA[<p>SBAS illustration with the GNSS satellites (upper left) and the communications satellite (upper right). With the Australian government’s announcement earlier this month that...</p>
<p>The post <a href="https://insidegnss.com/positioning-technology-in-australia-gets-a-12-million-boost/">Positioning Technology in Australia Gets a $12 Million Boost</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class='special_post_image'><img class='specialimageclass img-thumbnail' src='https://insidegnss.com/wp-content/uploads/2018/01/web SBAS.png' ><span class='specialcaption'>SBAS illustration with the GNSS satellites (upper left) and the communications satellite (upper right).</span></div>
<p>
With the Australian government’s announcement earlier this month that it would invest $12 million in a two-year program looking into the future of positioning technology in Australia, comes plans for testing of satellite based augmentation systems (SBAS) to be undertaken, and for future applications for all four major modes of transport in Australia, as well as for potential safety, productivity, efficiency and environmental benefits.</p>
<p><span id="more-24732"></span></p>
<p>
With the Australian government’s announcement earlier this month that it would invest $12 million in a two-year program looking into the future of positioning technology in Australia, comes plans for testing of satellite based augmentation systems (SBAS) to be undertaken, and for future applications for all four major modes of transport in Australia, as well as for potential safety, productivity, efficiency and environmental benefits.</p>
<p>The SBAS test-bed is Australia’s first step toward developing the positioning technology and expertise needed to be competitive globally and could impact the country’s place as an industry leader in the Asia Pacific region. An SBAS would overcome current gaps Australia has in mobile and radio communications and, when combined with on-ground operational infrastructure and services, could ensure that accurate positioning information can be received anytime and anywhere within Australia.</p>
<p>The two-year project will test two new satellite positioning technologies including next generation SBAS and Precise Point Positioning, which will provide positioning accuracies of several decimeters and five centimeters, respectively. Currently, positioning in Australia is usually accurate to five to 10 meters.
</p>
<p>
“SBAS utilizes space-based and ground-based infrastructure to improve and augment the accuracy, integrity and availability of basic Global Navigation Satellite System (GNSS) signals, such as those currently provided by the USA Global Positioning System (GPS),” stated Federal Minister for Infrastructure and Transport Darren Chester, who added the program could test the potential of SBAS technology in the four transport sectors—aviation, maritime, rail and road.</p>
<p>“The future use of SBAS technology was strongly supported by the aviation industry to assist in high accuracy GPS-dependent aircraft navigation. Positioning data can also be used in a range of other transport applications including maritime navigation, automated train management systems and in the future, driverless and connected cars.”</p>
<p>From using Google Maps on smartphone to emergency management and farming, many people use and benefit from positioning technology every day without even realizing it.</p>
<p>The funding will be used to test instant, accurate and reliable positioning technology that could provide future safety, productivity, efficiency and environmental benefits across many industries in Australia, including transport, agriculture, construction, and resources.<br />
According to the Australian Government, research has shown that the wide-spread adoption of improved positioning technology has the potential to generate upwards of $73 billion of value to Australia by 2030.</p>
<p>The benefits to this improved technology can be widespread. Minister for Resources and Northern Australia Matt Canavan said access to more accurate data about the Australian landscape would also help unlock the potential of the North.</p>
<p>“This technology has potential uses in a range of sectors, including agriculture and mining, which have always played an important role in our economy, and will also be at the heart of future growth in Northern Australia,” Senator Canavan said.<br />
“Access to this type of technology can help industry and Government make informed decisions about future investments.”</p>
<p>The SBAS test-bed is Australia&#8217;s first step towards joining countries such as the United States, Russia, India, Japan and many across Europe in investing in SBAS technology and capitalizing on the link between precise positioning, productivity and innovation.</p>
<p>Early this year, Geoscience Australia with the Collaborative Research Centre for Spatial Information (CRCSI) will call for organizations from numerous industries including agriculture, aviation, construction, mining, maritime, rail, road, spatial, and utilities to participate in the test-bed.</p>
<p><strong>GNSS Infrastructure </strong><br />
The SBAS test-bed will utilize existing national GNSS infrastructure developed by AuScope as part of the National Collaborative Research Infrastructure Strategy.</p>
<p>It will test two new satellite positioning technologies — next generation SBAS and Precise Point Positioning, which provide positioning accuracies of several decimeters and five centimeters, respectively.</p>
<p>Highly accurate positioning technologies are already available in Australia, but they can be cost-prohibitive and not readily available in many areas.</p>
<p>Geoscience Australia is working with the CRCSI on the project, which is designed to evaluate the effectiveness of an SBAS for Australia, and build expertise within government and industry on its transformative benefits. The project is funded through the Department of Industry, Innovation and Science, and Department of Infrastructure and Regional Development.</p>
<p>Positioning data has become fundamental to a range of applications and businesses worldwide. It increases productivity, secures safety and propels innovation; enables GPS on smartphones, provides safety-of-life navigation on aircraft, increases water efficiency on farms, helps to locate vessels in distress at sea, and supports intelligent navigation tools and advanced transport management systems that connect cities and regions.</p>
<p></p>
<p>The post <a href="https://insidegnss.com/positioning-technology-in-australia-gets-a-12-million-boost/">Positioning Technology in Australia Gets a $12 Million Boost</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Siemens Convergence Creators Launch Satellite Interference Geolocation Service</title>
		<link>https://insidegnss.com/siemens-convergence-creators-launch-satellite-interference-geolocation-service/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Fri, 20 Jan 2017 16:55:43 +0000</pubDate>
				<category><![CDATA[GNSS (all systems)]]></category>
		<category><![CDATA[receiver]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[Ventures]]></category>
		<guid isPermaLink="false">http://insidegnss.com/industryview/siemens-convergence-creators-launch-satellite-interference-geolocation-service/</guid>

					<description><![CDATA[<p>As described in the November-December issue of Inside GNSS, “Interference Localization from Space,” radio frequency interference causes the satellite industry to lose millions...</p>
<p>The post <a href="https://insidegnss.com/siemens-convergence-creators-launch-satellite-interference-geolocation-service/">Siemens Convergence Creators Launch Satellite Interference Geolocation Service</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class='special_post_image'><img class='specialimageclass img-thumbnail' src='https://insidegnss.com/wp-content/uploads/2018/01/SIECAMS ILS ONE illustration.jpg' ><span class='specialcaption'></span></div>
<p>As described in the November-December issue of <em>Inside GNSS</em>, <a href="http://insidegnss.com/interference-localization-from-space/" target="_blank">“Interference Localization from Space,” </a>radio frequency interference causes the satellite industry to lose millions of dollars per year due to detrimental effects, ranging from a degradation in the quality of service to the complete loss of service.</p>
<p><span id="more-26620"></span><br />
As described in the November-December issue of <em>Inside GNSS</em>, <a href="http://insidegnss.com/interference-localization-from-space/" target="_blank">“Interference Localization from Space,” </a>radio frequency interference causes the satellite industry to lose millions of dollars per year due to detrimental effects, ranging from a degradation in the quality of service to the complete loss of service.</p>
<p>In an effort to combat this, Vienna, Austria-based Siemens Convergence Creators has announced its new <a href="http://www.convergence-creators.siemens.com/satellite-geolocation-service-roll-out.html" target="_blank">Satellite Geolocation Service</a>, designed to enable satellite and service operators to localize satellite signal interference worldwide.</p>
<p>For satellite operators and users, including the GNSS community, the ability to rapidly identify and mitigate interference — intentional or not — is crucial to protecting the core functionality of their assets and service operations.</p>
<p>According to a statement by the European Space Agency (ESA), which supported the development of the geolocation system, SIECAMS ILS ONE works by analyzing the signal distortions primarily caused by satellite movement, atmospheric, or weather influences and other environmental factors. By comparing such signal distortions of the interference signal with known signals, ILS ONE is able to identify the precise location of the interference source.  </p>
<p>Up to now, interference geolocation systems required having two geostationary satellites in close proximity to each other in order to obtain sufficient crosstalk for reliable geolocation signal processing. According Siemans Convergence Creators, SIECAMS results in a significant improvement in the resolution of interference issues compared with traditional satellite-interference localization systems.</p>
<p>“The SIECAMS single-satellite solution is a real game-changer for the satellite industry,” says Stephane Pirio, ESA Technical Officer for the activity. “It is much cheaper than traditional geolocation systems and this makes it particularly attractive for small- and medium-size satellite operators.”</p>
<p>SIECAMS ILS ONE has been very successfully used by Eutelsat since early 2016.</p>
<p>Siemens Convergence Creators has made substantial investments towards the development of tools for satellite interference mitigation in the last decade within the framework of its SIECAMS product line. SIECAMS currently comprises the carrier-monitoring and interference-detection tool SIECAMS CMS, the carrier-ID detection tool SIECAMS CID, the geolocation system SIECAMS ILS, and the single-satellite geolocation system, SIECAMS ILS ONE.</p>
<p>Until now, the company says, satellite operators had to invest in high-quality geolocation tools and personnel training to enable their own staff to identify, locate, and reduce or eliminate sources of interference in order to avoid potential damage claims and the risk of losing customers. Even so, locating the origin of interference may take days, weeks, or even months. </p>
<p>The localization of satellite interference works worldwide because Siemens Convergence Creators&#8217; Satellite Geolocation Service offers coverage of practically the entire inhabited landmass on Earth.</p>
<p>The Satellite Geolocation Service went into operation on January 9 and can be ordered on demand for individual interference events, or via yearly subscription that includes a contingent of interference localization instances. </p>
<p>Part 2 of the Working Papers on satellite-based geolocation of interference can be found in the January-February issue of <em>Inside GNSS</em>. </p>
<p>The post <a href="https://insidegnss.com/siemens-convergence-creators-launch-satellite-interference-geolocation-service/">Siemens Convergence Creators Launch Satellite Interference Geolocation Service</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Air Force Approves Lockheed Martin&#8217;s GPS Ground Control Design</title>
		<link>https://insidegnss.com/air-force-approves-lockheed-martins-gps-ground-control-design/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Tue, 13 Dec 2016 23:09:01 +0000</pubDate>
				<category><![CDATA[Aerospace and Defense]]></category>
		<category><![CDATA[components]]></category>
		<category><![CDATA[Environment]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[location based services]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/industryview/air-force-approves-lockheed-martins-gps-ground-control-design/</guid>

					<description><![CDATA[<p>GPS III satellites in production. Image Source: Lockheed Martin. The U.S. Air Force has approved Lockheed Martin&#8217;s current GPS satellite ground control system...</p>
<p>The post <a href="https://insidegnss.com/air-force-approves-lockheed-martins-gps-ground-control-design/">Air Force Approves Lockheed Martin&#8217;s GPS Ground Control Design</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class='special_post_image'><img class='specialimageclass img-thumbnail' src='https://insidegnss.com/wp-content/uploads/2018/01/GPSIII.jpg' ><span class='specialcaption'>GPS III satellites in production. Image Source: Lockheed Martin.</span></div>
<p>
The U.S. Air Force has approved Lockheed Martin&#8217;s current GPS satellite ground control system upgrade to enable it to operate with more powerful and accurate GPS III satellites, the company said.
</p>
<p>
The Air Force&#8217;s Critical Design Review (CDR) for the Contingency Operations (COps) contract, completed on November 17, allows Lockheed Martin to proceed with the modification of the existing Architecture Evolution Plan (AEP) Operational Control Segment. The AEP, maintained by Lockheed Martin, controls the 31 GPS IIR, IIR-M and IIF satellites in orbit.
</p>
<p><span id="more-26610"></span></p>
<p>
The U.S. Air Force has approved Lockheed Martin&#8217;s current GPS satellite ground control system upgrade to enable it to operate with more powerful and accurate GPS III satellites, the company said.
</p>
<p>
The Air Force&#8217;s Critical Design Review (CDR) for the Contingency Operations (COps) contract, completed on November 17, allows Lockheed Martin to proceed with the modification of the existing Architecture Evolution Plan (AEP) Operational Control Segment. The AEP, maintained by Lockheed Martin, controls the 31 GPS IIR, IIR-M and IIF satellites in orbit.
</p>
<p>
Lockheed Martin said that the COps modifications allow the AEP to support the new GPS Block III satellites by enabling them to perform their positioning, navigation and timing mission, once they are launched. COps is envisioned as a temporary gap filler prior to the GPS constellation&#8217;s transition to the next generation Operational Control System (OCX) Block 1, the company said.
</p>
<p>
&quot;The GPS constellation is a valuable asset to our warfighters, our nation and the world. This risk-reduction effort ensures the Air Force has the ability to maintain the constellation at full strength,&quot; said Mark Stewart, vice president of Lockheed Martin&#8217;s Navigation Systems mission area. &quot;We are here to support the Air Force and the GPS III program any way we can.&quot;
</p>
<p>
In February, the Air Force awarded Lockheed Martin the $96 million COps services and supplies contract. The government approved the company&#8217;s proposed ground system modification during a Preliminary Design Review on May 11, the company said.
</p>
<p>
As <em>Inside GNSS</em> reported, <a href="http://insidegnss.com/industryview/lockheed-martin-advances-gps-ground-control-system-for-u-s-air-force/">under a separate contract in October, Lockheed Martin completed the Commercial Off-the-Shelf (COTS) Upgrade no. 2</a> (CUP2) project, which is part of a multi-year plan to refresh the AEP&#8217;s technology and enhance the system&#8217;s ability to protect data and infrastructure, the company said. Lockheed Martin said CUP2 is now fully operational and managing the current GPS constellation.
</p>
<p>
In September,<a href="http://insidegnss.com/news/lockheed-martin-awarded-395-million-gps-iii-contract-option/"> Lockheed Martin received a $395 million U.S. Air Force Space and Missile Systems Center contract option </a>to build two additional GPS III satellites. The contract option calls for long-lead and production hardware to manufacture GPS III space vehicles (SVs) 9 and 10.
</p>
<p>
The government plans to compete future purchases of GPS III satellites beginning with the GPS III SV 11. This future competition will maintain the current technical GPS III baseline, and will add additional hosted payloads to increase system accuracy, search and rescue capability, and universal S-Band compatibility, the Air Force said.</p>
<p>The post <a href="https://insidegnss.com/air-force-approves-lockheed-martins-gps-ground-control-design/">Air Force Approves Lockheed Martin&#8217;s GPS Ground Control Design</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Lockheed Martin Advances GPS Ground Control System for U.S. Air Force</title>
		<link>https://insidegnss.com/lockheed-martin-advances-gps-ground-control-system-for-u-s-air-force/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Thu, 01 Dec 2016 22:59:03 +0000</pubDate>
				<category><![CDATA[Aerospace and Defense]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[infrastructure]]></category>
		<category><![CDATA[military]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/industryview/lockheed-martin-advances-gps-ground-control-system-for-u-s-air-force/</guid>

					<description><![CDATA[<p>The Air Force&#8217;s Global Positioning Systems Directorate contracted the CUP2 upgrade. Lockheed Martin has announced a major upgrade to modernize the GPS ground...</p>
<p>The post <a href="https://insidegnss.com/lockheed-martin-advances-gps-ground-control-system-for-u-s-air-force/">Lockheed Martin Advances GPS Ground Control System for U.S. Air Force</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class='special_post_image'><img class='specialimageclass img-thumbnail' src='https://insidegnss.com/wp-content/uploads/2018/01/GPS Directorate.jpg' ><span class='specialcaption'>The Air Force&#8217;s Global Positioning Systems Directorate contracted the CUP2 upgrade.</span></div>
<p>
Lockheed Martin has announced a major upgrade to modernize the GPS ground control system, the company said. The commercial-off-the-shelf (COTS) upgrade no. 2 (CUP2) project, which became operational in mid-October to manage the 31 GPS satellites, is the latest step in the U.S. Air Force&#8217;s plan to refresh technology and transform the legacy operational control segment, also known as the Architecture Evolution Plan (AEP), the company said.
</p>
<p><span id="more-26607"></span></p>
<p>
Lockheed Martin has announced a major upgrade to modernize the GPS ground control system, the company said. The commercial-off-the-shelf (COTS) upgrade no. 2 (CUP2) project, which became operational in mid-October to manage the 31 GPS satellites, is the latest step in the U.S. Air Force&#8217;s plan to refresh technology and transform the legacy operational control segment, also known as the Architecture Evolution Plan (AEP), the company said.
</p>
<p>
&quot;Under CUP2, Lockheed Martin and the Air Force installed modern commercial hardware and a major software upgrade that enhances the system&#8217;s ability to protect data and infrastructure from cyber threats, as well as improves its overall sustainability and operability,&quot; said Vinny Sica, Lockheed Martin vice president and general manager of mission solutions. &quot;Continued modernization and cyber-hardening of the GPS control system is vitally important to the sustainment of navigation services for our military and all global GPS users.&quot;
</p>
<p>
The Air Force awarded Lockheed Martin the CUP2 project in November 2013 through its GPS Control Segment contract. The system, a part of a GPS Control Segment contract, is deployed into the AEP&#8217;s GPS Master Control Station and the Alternate Master Control Station.
</p>
<p>
This is the third major technology upgrade of the GPS command and control system since the GCS contract began in January 2013, the company said.
</p>
<p>
In May, as part of Contingency Operations (COps) through the GPS III contract, Lockheed Martin demonstrated a preliminary design to build off CUP2 and further upgrade the AEP, the company said. This supports the next generation GPS III satellites to perform their positioning, navigation and timing mission.
</p>
<p>
Lockheed Martin said COps is a temporary gap filler prior to the entire GPS constellation&#8217;s transition to the next-generation Operational Control System (OCX) Block 1, which is currently in development.
</p>
<p>
The Air Force&#8217;s Space and Missile Systems Center, Global Positioning Systems Directorate, contracted the CUP2 upgrade. The Air Force Space Command&#8217;s 2nd Space Operations Squadron (2SOPS), based at Schriever Air Force Base, Colorado, manages and operates the GPS constellation.</p>
<p>The post <a href="https://insidegnss.com/lockheed-martin-advances-gps-ground-control-system-for-u-s-air-force/">Lockheed Martin Advances GPS Ground Control System for U.S. Air Force</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>NOAA Expands GNSS Data Sources for Weather Prediction</title>
		<link>https://insidegnss.com/noaa-expands-gnss-data-sources-for-weather-prediction/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Wed, 16 Nov 2016 22:29:00 +0000</pubDate>
				<category><![CDATA[201611 November/December 2016]]></category>
		<category><![CDATA[Environment]]></category>
		<category><![CDATA[GNSS (all systems)]]></category>
		<category><![CDATA[satellites/space segment]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[NOAA]]></category>
		<category><![CDATA[weather data]]></category>
		<category><![CDATA[weather prediction]]></category>
		<guid isPermaLink="false">http://insidegnss.com/news/noaa-expands-gnss-data-sources-for-weather-prediction/</guid>

					<description><![CDATA[<p>The National Oceanic and Atmospheric Administration (NOAA) will purchase data from small commercial satellites to expand its GNSS radio occultation (RO) efforts to...</p>
<p>The post <a href="https://insidegnss.com/noaa-expands-gnss-data-sources-for-weather-prediction/">NOAA Expands GNSS Data Sources for Weather Prediction</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>
The National Oceanic and Atmospheric Administration (NOAA) will purchase data from small commercial satellites to expand its GNSS radio occultation (RO) efforts to better predict weather.
</p>
<p>
In September NOAA, through the government&#8217;s Commercial Weather Data Pilot program, awarded contracts to San Francisco, California-based Spire Global ($370,000) and GeoOptics ($695,000), of Pasadena, California, to provide RO data. This data will be used to assess whether commercially provided information can be incorporated into the agency&#8217;s weather models.
</p>
<p><span id="more-24709"></span></p>
<p>
The National Oceanic and Atmospheric Administration (NOAA) will purchase data from small commercial satellites to expand its GNSS radio occultation (RO) efforts to better predict weather.
</p>
<p>
In September NOAA, through the government&#8217;s Commercial Weather Data Pilot program, awarded contracts to San Francisco, California-based Spire Global ($370,000) and GeoOptics ($695,000), of Pasadena, California, to provide RO data. This data will be used to assess whether commercially provided information can be incorporated into the agency&#8217;s weather models.
</p>
<p>
The RO technique has been around for a long time, taking advantage of the effects of electrical energy and moisture in the atmosphere on GNSS signal propagation. The GPS signals bend a bit as they skim through the atmosphere; a deflection that is a function of the density of the atmosphere. The time it takes for the signal to travel the now-longer path around the curve of the planet can be used to calculate atmospheric properties, such as temperature, pressure, humidity and electron density.
</p>
<p>
With its Stratos product, Spire gathers RO data from 10 low Earth orbit (LEO) small, or microsatellites with multiple sensors, tracking GPS signals providing 3.65 atmospheric profiles per year, according to the company. GeoOptics will begin launching its LEO cubesat constellation, CICERO, in early 2017. When RO data is combined with that from polar-orbiting weather satellites, NOAA believes it can make better weather forecasts.
</p>
<p>
Both Spire and GeoOptics will begin providing GNSS RO data to NOAA by April 30, 2017, the agency said. NOAA&#8217;s National Environmental Satellite, Data, and Information Service (NESDIS) will analyze the data and issue a report in early 2018.
</p>
<p>
&quot;[NOAA&#8217;s] models take data from a number of sources including radiosondes, land-based stations, and satellites,&quot; said Sandy MacDonald, Spire&#8217;s director for numerical weather prediction. &quot;GPS RO data delivers a very accurate and detailed sounding of temperature and moisture from the upper atmosphere into the lower atmosphere. About 40 percent of the soundings make it to the lowest layer of the atmosphere, the boundary layer. GPS RO data is exceptionally useful for making bias corrections in the full atmosphere.&quot;
</p>
<p>
NOAA already uses GNSS RO data through the six-satellite COSMIC constellation, which is a joint satellite program with Taiwan. The agency has requested more federal funding for COSMIC-2 follow-on satellites.
</p>
<p>
Currently, Spire&#8217;s satellites collect RO data in a pre-production capacity, said MacDonald, a 40-year NOAA veteran who leads Spire&#8217;s RO efforts in Boulder, Colorado. &quot;Unlike some forms of data, GPS-RO requires processing for it to be useful in forecasting. This September, at the International Radio Occultation Working Group, we revealed the first commercially collected and processed GPS-RO profiles,&quot; he said. &quot;The biggest hurdles to getting the data is access to on-time rocket launches. We have the single most aggressive launch schedule in the industry with over 70 satellites manifested over the next year but delays on the launch pad affect how quickly we get access to this data.&quot;
</p>
<p>
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:RelyOnVML/>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]-->
</p>
<p>
<!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:DoNotShowRevisions/>
<w:DoNotPrintRevisions/>
<w:DoNotShowMarkup/>
<w:DoNotShowComments/>
<w:DoNotShowInsertionsAndDeletions/>
<w:DoNotShowPropertyChanges/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="&#45;-"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"
DefSemiHidden="false" DefQFormat="false" DefPriority="99"
LatentStyleCount="371">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true"
UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true"
Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true"
Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true"
Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true"
Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true"
Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true"
Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true"
UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 6"/>
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>


<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>


<![endif]-->
</p>
<p>
<strong>Congressional Push for Commercial Data</strong><br />
While Congress approved $3 million for Commercial Weather Data Pilot program, the effort was initiated through the<a href="http://insidegnss.com/news/vote-nears-for-weather-forecasting-bill-that-could-boost-gps-radio-occultation-firms/"> Weather Research and Forecasting Innovation Act</a>. The measure, sponsored by two Oklahoma representatives, Frank Lucas and Jim Bridenstine, both Republicans, calls for commercial data for weather monitoring purposes.
</p>
<p>
U.S. Representative Lamar Smith, R-Texas, who is chairman of the House Committee on Science, Space, and Technology, said it was a good thing that NOAA is acquiring private sector weather data. &quot;In the face of looming data gaps and continual delays with our governmental satellite systems, the private sector can provide data to better predict weather and protect American lives and property,&quot; he said. &quot;In the face of real threats, NOAA needs to address its shortfalls and think beyond government weather systems by making further awards under the [Commercial Weather Data Pilot program].
</p>
<p>
&quot;We see a future with small satellites delivering data of the same quality that required large satellites and much greater cost in the past,&quot; MacDonald said. &quot;We&#8217;ve already demonstrated that small satellites are most effective when collecting large amounts of data through Spire&#8217;s ship tracking product. Similar to ship tracking where frequent updates are important, spatial density is an important factor in the usefulness of GPS RO data. By launching many small satellites, they&#8217;re able to capture an exceptional number of occultations in comparison to smaller number of traditional satellites.&quot;
</p>
<p>
Small satellites have the attention of the White House Office of Science and Technology Policy (OSTP). A new OSTP initiative, &quot;Harnessing the Small Satellite Revolution,&quot; calls for NASA, the Defense Department (DoD), Commerce Department, and other agencies to promote government and private small satellite use.
</p>
<p>
In addition to NOAA&#8217;s weather efforts, small satellites will be used for remote sensing, communications, science, and space exploration, the White House said. NASA will fund as much as $30 million in small satellite data purchases, including $25 million for nongovernment spacecraft constellations. NASA also intends to purchase such Earth science observation data as moderate-resolution land imaging and RO data.</p>
<p>The post <a href="https://insidegnss.com/noaa-expands-gnss-data-sources-for-weather-prediction/">NOAA Expands GNSS Data Sources for Weather Prediction</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Intelligent Transportation Systems: 22nd ITS World Congress</title>
		<link>https://insidegnss.com/intelligent-transportation-systems-22nd-its-world-congress/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Tue, 02 Dec 2014 05:24:37 +0000</pubDate>
				<category><![CDATA[Compass/Beidou]]></category>
		<category><![CDATA[Galileo]]></category>
		<category><![CDATA[GLONASS]]></category>
		<category><![CDATA[GNSS (all systems)]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[legacy-application]]></category>
		<category><![CDATA[SBAS and RNSS]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<guid isPermaLink="false">http://insidegnss.com/event/intelligent-transportation-systems-22nd-its-world-congress/</guid>

					<description><![CDATA[<p>The Convention Centre Bordeaux The 22nd World Congress and Exhibition on Intelligent Transport Systems and Services will be held at the Convention Centre...</p>
<p>The post <a href="https://insidegnss.com/intelligent-transportation-systems-22nd-its-world-congress/">Intelligent Transportation Systems: 22nd ITS World Congress</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class='special_post_image'><img class='specialimageclass img-thumbnail' src='https://insidegnss.com/wp-content/uploads/2018/01/images_Facade-Lac.jpg' ><span class='specialcaption'>The Convention Centre Bordeaux</span></div>
<p>
The 22nd World Congress and Exhibition on Intelligent Transport Systems and Services will be held at the Convention Centre Bordeaux and Exhibition Centre Bordeaux in Bordeaux, France on October 5 &#8211; 9, 2015. It will focus on how achieving intelligent mobility will change our lives, and the benefits space can bring to ITS applications.
</p>
<p>
The theme for this year’s event is “Towards Intelligent Mobility – Better Use of Space”, and will offer Plenary, Executive, Technical/Scientific, Special Interest and Interactive Sessions.
</p>
<p><span id="more-23496"></span></p>
<p>
The 22nd World Congress and Exhibition on Intelligent Transport Systems and Services will be held at the Convention Centre Bordeaux and Exhibition Centre Bordeaux in Bordeaux, France on October 5 &#8211; 9, 2015. It will focus on how achieving intelligent mobility will change our lives, and the benefits space can bring to ITS applications.
</p>
<p>
The theme for this year’s event is “Towards Intelligent Mobility – Better Use of Space”, and will offer Plenary, Executive, Technical/Scientific, Special Interest and Interactive Sessions.
</p>
<p>
A Congress topic of note for the GNSS community is &quot;Space Technologies and Services For ITS&quot;, and will include discussion of GNSS positioning and timing services used by all modes of transport, and how, when combined with vehicle sensors and with vehicle-to-infrastructure (V2X) communication, future multi-constellation and multi-frequency receivers will dramatically improve positioning performance and contribute to the development of a wide range of innovative ITS applications, including:
</p>
<ul>
<li>Hybridization of GNSS receivers with other sensors (eg video, lidar).</li>
<li>Collaborative cloud-based mapping.</li>
<li>Reliable positioning for critical ITS services.</li>
<li>Solutions for regulated services (eg eCall, digital tachograph, dangerous goods)</li>
<li>New services from multi-constellation receivers.</li>
<li>Monitoring transport infrastructures using Earth observation satellites.</li>
<li>Traffic monitoring with infra-red cameras from satellites.</li>
</ul>
<p>
This year’s event will also include a special session on &quot;GNSS Services<br />
and Performance Standardization Workshop&quot; with discussion of GNSS<br />
positioning and timing services used by all modes of intelligent<br />
transport. The workshop is organized by ERTICO and the Satellite<br />
Positioning Performance Assessment for Road Transport (SaPPART) European<br />
Cooperation in Science and Technology (COST) Action.
</p>
<p>
Other congress topics include:
</p>
<ul>
<li>Cooperative ITS Deployment Challenges</li>
<li>Multimodal Transport for People and Goods</li>
<li>Urban Trends Driving ITS Changes</li>
<li>Solutions for Sustainable Mobility</li>
<li>Automated Roads, Automated Management, Automated Driving</li>
<li>Are Big Data and Open Data Transport’s “Silver Bullets”?</li>
</ul>
<p>
The ITS World Congress in Bordeaux is organized by ERTICO &#8211; ITS Europe in close cooperation with the European Commission, ITS America and ITS Asia-Pacific, and is hosted by TOPOS.
</p>
<p>
Congress organizers will also offer a social program for attendees to enjoy all areas of interest in and around Bordeaux, its region, products and services. The official language of the Congress is English. A selected number of sessions will be conducted in French.</p>
<p>The post <a href="https://insidegnss.com/intelligent-transportation-systems-22nd-its-world-congress/">Intelligent Transportation Systems: 22nd ITS World Congress</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Won’t Get Fooled Again</title>
		<link>https://insidegnss.com/wont-get-fooled-again-2/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Wed, 22 Jan 2014 06:54:26 +0000</pubDate>
				<category><![CDATA[201401 January/February 2014]]></category>
		<category><![CDATA[Column]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[policy]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[Thinking Aloud]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://insidegnss.com/2014/01/22/wont-get-fooled-again-2/</guid>

					<description><![CDATA[<p>How many times, as some once-promising politician stumbles up against his pull date, have we heard that irreverent anthem of The Who invoked?...</p>
<p>The post <a href="https://insidegnss.com/wont-get-fooled-again-2/">Won’t Get Fooled Again</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>How many times, as some once-promising politician stumbles up against his pull date, have we heard that irreverent anthem of The Who invoked?</p>
<p>Thousands? Millions?</p>
<p>Yes, back in the wreckage of the second George Bush’s second term, Barack Obama looked pretty good by comparison. Even then, though, raising the banner of “Hope” before the eyes of a desperate nation was a risky thing to do.</p>
<p><span id="more-22504"></span></p>
<p>But now — much as I hate it — I’d have to answer Sarah Palin’s snide query, “How’s That Hopey-Changey Stuff Working Out For Ya?’’ Not so well, Mrs. Palin, really not so well.</p>
<p>And back in 2009, Obama’s resistance to being separated from his Blackberry by security-minded officials seemed amusing — a generational indication that smartphones might be competing for the affections of Americans toward their automobiles. Instead, it actually foreshadowed U.S. eavesdropping on the phones of world leaders.</p>
<p>What seemed wonkish but well-informed inclination toward new technology turned out to be mere fancy for the hipness of social media. Hence, the near-catastrophe of LightSquared driven by an impulsive search for 500 megahertz of RF spectrum to reallocate as wireless broadband.</p>
<p>No, once in the White House, the execution of plans fell far short of the rhetoric. Thus, the early promise to close our gulag for terrorists at Guantanamo — filled with innocent and guilty alike — appears no more likely to happen in 2014 than in 2009.</p>
<p>Any more than Obama’s teaching courses in constitutional law seems to have engendered a respect for the protections of the U.S. Constitution.</p>
<p>Or that the good intentions of universal health insurance coverage could survive its poor design and disastrous rollout. “Let it be written, let it be done,” did not work any better for the president’s health care mandate than the same mantra did for Yul Brynner as Pharaoh in “The Ten Commandments.”</p>
<p>What would I like to see this administration achieve in the way of space-based positioning, navigation, and timing (PNT) before last call at the polls in 2016? Well, for a starter, here’s a short list:</p>
<ul>
<li>Admit that the Global Positioning System — or more broadly, PNT — really is a part of the national critical infrastructure that deserves at least as much consideration and protection as the other 16 sectors identified in the National Infrastructure Protection Plan. After all, GPS has a very tangible, physical presence in its satellites and ground control segment.</li>
<li>Support an international GNSS monitoring and assessment service that would benefit all system providers and users. Isn’t that a natural corollary to the administration’s 2010 amendment to National Space Policy authorizing use of foreign GNSS services to strengthen GPS?</li>
<li>Acknowledge that Americans’ personal location should be considered private unless willingly made public by individuals, granting it the Fourth Amendment protections envisioned in the Supreme Court’s <em>Katz v. United States</em> decision. And enforce those protections against wholesale National Security Agency surveillance as well as the FBI and local police. And while we’re at it, let’s admit that Edward Snowden is closer to being a patriot in the tradition of Daniel Ellsberg with his Pentagon Papers than the traitorous spy that embarrassed officials are trying to portray him as.</li>
<li>Get the unmanned aerial systems (UAS) initiative off the ground and into the air. Is it possible that we could learn from the experience of many other nations, including those in Europe, that are well ahead of the United States in this area. This may seem at odds with the previous suggestion, but with adequate legal guidelines personal privacy can remain secure while the civil benefits of UAS are revealed. The FAA’s responsibility for ensuring aviation safety are not incompatible with advancing the UAS project vigorously.</li>
<li>Actually design and approve plans for — if not the completion of — a system to detect and mitigate GNSS interference as well as ensure a backup for GPS. More than nine years after a presidential directive to do so, we should either invest the resources and leadership to get it done or admit that it’s beyond our abilities.</li>
</ul>
<p>The post <a href="https://insidegnss.com/wont-get-fooled-again-2/">Won’t Get Fooled Again</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Ionospheric Scintillation</title>
		<link>https://insidegnss.com/ionospheric-scintillation/</link>
		
		<dc:creator><![CDATA[Inside GNSS]]></dc:creator>
		<pubDate>Sun, 19 Jan 2014 23:47:41 +0000</pubDate>
				<category><![CDATA[201401 January/February 2014]]></category>
		<category><![CDATA[Column]]></category>
		<category><![CDATA[Compass/Beidou]]></category>
		<category><![CDATA[engineering]]></category>
		<category><![CDATA[Galileo]]></category>
		<category><![CDATA[GLONASS]]></category>
		<category><![CDATA[GNSS (all systems)]]></category>
		<category><![CDATA[GNSS Solutions]]></category>
		<category><![CDATA[GPS]]></category>
		<category><![CDATA[signal]]></category>
		<category><![CDATA[system infrastructure/technology]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://insidegnss.com/2014/01/19/ionospheric-scintillation/</guid>

					<description><![CDATA[<p>Ionospheric scintillations are rapid temporal fluctuations in both amplitude and phase of trans-ionospheric GNSS signals caused by the scattering of irregularities in the...</p>
<p>The post <a href="https://insidegnss.com/ionospheric-scintillation/">Ionospheric Scintillation</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="special_post_image"><img decoding="async" class="specialimageclass img-thumbnail" src="https://insidegnss.com/wp-content/uploads/2018/01/SolFigs_0.jpg" /></div>
<p>Ionospheric scintillations are rapid temporal fluctuations in both amplitude and phase of trans-ionospheric GNSS signals caused by the scattering of irregularities in the distribution of electrons encountered along the radio propagation path. The occurrence of scintillation has large day-to-day variability. The most severe scintillations are observed near the poles (at auroral latitudes) and near the equator (within ± 20 degrees of geomagnetic equator).</p>
<p><span id="more-22481"></span></p>
<p>Ionospheric scintillations are rapid temporal fluctuations in both amplitude and phase of trans-ionospheric GNSS signals caused by the scattering of irregularities in the distribution of electrons encountered along the radio propagation path. The occurrence of scintillation has large day-to-day variability. The most severe scintillations are observed near the poles (at auroral latitudes) and near the equator (within ± 20 degrees of geomagnetic equator).</p>
<p>Equatorial amplitude scintillation affects both code and carrier tracking and degrades pseudorange and carrier phase measurements. Deep amplitude fades over sufficient duration can cause loss of lock in both code and carrier tracking within a GNSS receiver. Equatorial phase scintillation adversely affects the operation of a receiver’s phase lock loop (PLL) and leads to carrier cycle slips, navigation data bit errors, and complete loss of carrier lock.</p>
<p>Usually the level of scintillation can be characterized by the S<sub>4</sub> amplitude scintillation index; the higher the S<sub>4</sub> index, the more severe the scintillation. Details for computing the S<sub>4</sub> index can be found in the Additional Resources section at the end of this article. Carrier phase tracking is very sensitive to scintillation due to a PLL’s stringent tracking threshold. Therefore, one solution for the scintillation problem is to employ a frequency lock loop (FLL) to replace a PLL for carrier tracking, due to its better robustness to signal attenuation and signal dynamics. However, many GNSS applications require (multi-frequency) carrier phase measurements, which a FLL cannot provide.</p>
<p>Despite the challenge of phase tracking under strong equatorial scintillation, several signal processing techniques can be used to improve the carrier tracking robustness. The common ones are FLL-assisted-PLL, adaptive-bandwidth PLL, and data stripping/aiding.</p>
<p>Given its robustness, using a FLL to aid a PLL seems like a wise approach. This combined carrier-tracking loop is called <em>FLL-assisted-PLL</em>. In a typical implementation, a FLL and a PLL operate in parallel to jointly control the carrier numerical controlled oscillator (NCO). The overall performance of such a FLL-assisted-PLL falls between that of a standalone FLL and a standalone PLL, depending on the loop noise bandwidths.</p>
<p>An <em>adaptive-bandwidth PLL</em> is another popular option for carrier tracking under scintillation. The use of a wide PLL bandwidth can help maintain phase tracking during periods of phase scintillation by tracking a rapidly changing phase. On the other hand, a narrow PLL bandwidth is desirable to tolerate amplitude scintillation with the ability to track at low carrier-to-noise–density (C/N<sub>0</sub>) ratios. The adaptive-bandwidth PLL is typically implemented by a Kalman filter with a time-varying Kalman gain based on the C/N<sub>0</sub> conditions, because the Kalman filter explicitly models the receiver clock and optimally adapts its band-width based on C/N<sub>0</sub>.</p>
<p>It is well-known that a pure PLL discriminator provides an improved signal tracking threshold by up to six decibels compared to a Costas discriminator. Modernized GNSS signals provide a pilot (data-less) component and a data component. Although tracking only the pilot component can bring a three-decibel loss due to the power sharing between the data and pilot components, a net gain of three decibels still is achieved due to the pure PLL. Therefore, tracking the pilot component of modernized GNSS signals (e.g., GPS L2C and L5) is recommended in scintillation environments.</p>
<p>For GNSS signals that do not have a pilot component, one can still use a pure PLL discriminator with <em>data stripping</em>. For example, for the GPS L1 C/A signal, after storing the data bits for the entire navigation message, or with external aiding, it is possible to predict the navigation data bits until the navigation message changes. This is so-called data stripping. With the help of data stripping, one can use a pure PLL discriminator instead of a Costas discriminator in the short term for better carrier tracking under scintillation.</p>
<p><strong>Multi-Satellite, Multi-Frequency Solutions</strong><br />
The techniques that we have discussed thus far focus on improving the carrier tracking in a single-frequency scalar-based receiver. Carrier tracking under scintillation can be improved by using multi-satellite and multi-frequency aiding. This is because scintillation rarely occurs on all visible satellites simultaneously on account of the isolated nature of electron irregularities mentioned in the introduction.</p>
<p>Furthermore, scintillation is carrier frequency–dependent. Both amplitude and phase scintillation levels has an inverse relation with the signal carrier frequency. The lower the carrier frequency, the stronger the scintillation is. In other words, if the same GPS signal was broadcast on L1, L2, and L5 frequencies at the same power, scintillation will most likely affect the L2 and L5 signals more than the L1 signal.</p>
<p>For the benefits of both frequency diversity and satellite diversity, it is important to implement the multi-satellite and multi-frequency aiding in a multi-frequency GNSS receiver. A typical implementation of such a processing architecture — herein referred to Shared-Architecture A — is shown in <strong>Figure 1 </strong><em>(see inset photo, above right, for all figures)</em>.</p>
<p>For the purpose of a better illustration, only the processing for GPS L1 C/A and L2C signals is shown in the figure. Each satellite has multiple channels for tracking signals on different frequencies. Each channel has a Doppler removal and correlation (DRC) unit, a local signal generator unit, and a PLL.</p>
<p>In this architecture, the key component is the multi-frequency vector delay and frequency lock loop (VDFLL). It receives the correlation from all channels and tracks the code and frequency of all signals from all satellites jointly. Regardless of the implementation variations, a VDFLL should include a local PVT (position, velocity, and time) engine that accepts multi-frequency code and Doppler measurements. The most common choice of this local PVT engine is an extended Kalman filter.</p>
<p>The VDFLL provides two feedback signals for each channel. One is the code phase error or the code Doppler to control the code NCO in the local signal generator, and the other is the carrier Doppler to aid the PLL in each channel. These code phase errors and the carrier Doppler values are derived from the local PVT engine.</p>
<p>With the carrier Doppler aiding from the VDFLL, the PLL in each channel only needs to track the residual Doppler (i.e., that induced by scintillation). The main implementation challenge for Shared-Architecture A is incorporating a reliable multi-constellation, multi-frequency PVT engine, as implementation of multi-frequency aiding and multi-satellite aiding depend upon it.</p>
<p><strong>Figure 2</strong> presents an alternative processing architecture, named Shared-Architecture B. Compared to Shared-Architecture A, this architecture employs a delay lock loop (DLL) for code tracking in each channel, and the multi-frequency VDFLL is replaced by a single-frequency VFLL and a code phase estimator.</p>
<p>In this architecture, DLLs are carrier-aided by PLLs to provide low-noise pseudorange measurements. As the carrier aiding from PLLs are fused by a VFLL, the multi-satellite aiding still propagates to DLLs indirectly from the PLLs in L1 C/A channels, even though a vector delay lock loop (VDLL) is not used in this case. Instead of being used to control the code NCOs, the code phase estimates derived from the single-frequency PVT engine are applied to detect loss of code lock on L1 C/A signals and to steer the DLLs when loss of code lock does occur.</p>
<p>In Shared-Architecture B, because the L1 C/A signal is more resistant to equatorial scintillation than the L2C signal, the L2C PLLs are aided by the L1 C/A PLLs. Since the carrier Doppler from the L1 C/A channels is already fused by the VFLL, the L2C PLLs benefit from the satellite diversity as well. In the L2C channels, similar to the L1 C/A channels, the carrier-aided DLLs are used for code tracking. The estimated L2C code phases based on the L1 C/A timing information are only used for detecting the loss of code locks and for code steering after loss of locks.</p>
<p>Shared-Architecture B also has the advantage of implementing multi-satellite aiding and multi-frequency aiding separately. For example, if only the multi-frequency aiding mode is needed, the receiver can simply disable the VFLL aiding and keep the L1-to-L2 aiding, which Shared-Architecture A cannot.</p>
<p>For signal acquisition, both architectures only acquire the signal on a single frequency (referred to here as the master frequency signal), because the carrier Doppler and timing information of the master frequency signal can directly estimate the code phase and carrier Doppler parameters of other frequency signals. In order words, the timing information and carrier Doppler from the master frequency signal can be used to directly initialize the code and carrier tracking loops of other frequency signals. The typical choice of the master frequency signal is the GPS L1 C/A signal, due to its shorter ranging code and stronger scintillation resistance compared to others.</p>
<p>We implemented Shared-Architecture A and Shared-Architecture B in a multi-constellation, multi-frequency GNSS software receiver. We will only present here the results of the Shared-Architecture B with the intermediate frequency (IF) data affected by equatorial ionospheric scintillation, but results with Shared-Architecture A were similar.</p>
<p>Data was collected in Rio de Janeiro during a research project established between the Brazilian Institute of Geography and Statistics (IBGE), the University of the State of Rio de Janeiro (UERJ), and the Position, Location And Navigation (PLAN) Group at the University of Calgary, to investigate the effects of equatorial ionospheric scintillation on GNSS signals during the current solar maximum.</p>
<p><strong>Figure 3</strong> shows the percentile of valid L1 C/A and L2C phase observations with the Shared-Architecture B and a standard architecture (without using multi-frequency and multi-satellite aiding). Valid phase observations are defined as those where the carrier phase observations have a phase lock indicator (PLI) value larger than 0.6 (see Additional Resources) and no cycle slips are detected. The results are based on eight hours of data using two-hertz measurements.</p>
<p>As reflected in the figure, due to the benefits of multi-frequency/multi-satellite aiding, Shared-Architecture B provides significantly more valid measurements than a standard architecture over the entire S<sub>4</sub> range, especially for the L2C carrier phase. This demonstrates the importance of the multi-frequency/multi-satellite aiding for a multi-frequency GNSS receiver.</p>
<p>In conclusion, despite the challenge of carrier tracking under strong equatorial scintillation, the performance of carrier tracking can be improved via modern signal processing techniques. Due to the natural characteristics of scintillation, multi-frequency/multi-satellite aiding benefits multi-frequency carrier tracking under equatorial ionospheric scintillation. The improved performance of the proposed multi-frequency/multi-satellite aiding was shown with IF data collected in Brazil.</p>
<p><span style="color: #993300;"><strong>Additional Resources</strong></span><em><strong><br />
For equatorial scintillation </strong></em><br />
Doherty, P. H., and S. H. Delay, C. E. Valladares, and J. A. Klobuchar, “Ionospheric Scintillation Effects in the Equatorial and Auroral Regions,” <em>Proceeding of ION GPS-2000</em>, Salt Lake City, Utah, USA, September 2000</p>
<p><em><strong>For S<sub>4</sub> index calculation and PLI calculation</strong></em><br />
Van Dierendonck A.J., and J. Klobuchar and Q. Hua, “Ionospheric Scintillation Monitoring Using Commercial Single Frequency C/A Code Receivers,” <em>Proceedings of the 6th International Technical Meeting of Satellite Division of the Institute of Navigation (ION GPS 1993)</em>, pp. 1333-1342, September 1993</p>
<p>Van Dierendonck, A. J., “GPS Receivers,” in <em>Global Positioning System: Theory and Applications, Vol. 1</em>, AIAA, Washington, DC, pp. 330–433, 1996</p>
<p><em><strong>For FLL-assisted-PLL and adaptive-bandwidth PLL</strong></em><br />
Ward, P. W., “Performance Comparison between FLL, PLL and a Novel FLL-Assisted-PLL Carrier Tracking Loop Under RF Interference Conditions,” <em>Proceedings of ION GNSS 1998</em>, pp. 783-795, September 1998</p>
<p>Humphreys, T. E., and M. L. Psiaki, B. M. Ledvina, and P. M. Kintner, Jr., “GPS Carrier Tracking Loop Performance in the Presence of Ionospheric Scintillations,” <em>Proceedings of ION GNSS 2005</em>, Long Beach, California, USA, September 2005</p>
<p><strong><em>For vector tracking</em></strong><br />
Lashley, M., and D. Bevly ,<a href="http://insidegnss.com/vector-delay-lock-loops/"><strong> “GNSS Solutions: How do vector delay lock loops predict the satellite signals?”</strong></a> <em>Inside GNSS</em>, September/October 2012</p>
<p><strong><em>For GSNRx</em></strong><br />
<strong>http://plan.geomatics.ucalgary.ca/project_info.php?pid=27</strong>, including the following available on that website:</p>
<p>Petovello, M. G., and C. O’Driscoll, G. Lachapelle, D. Borio, and H. Murtaza, “Architecture and Benefits of an Advanced GNSS Software Receiver,” <em>Journal of Global Positioning Systems</em>, vol. 7, no. 2, pp. 156–168, 2008</p>
<div class="pdfclass"><a class="specialpdf" href="http://insidegnss.com/wp-content/uploads/2018/01/janfeb14-SOLUTIONS.pdf" target="_blank" rel="noopener noreferrer">Download this article (PDF)</a></div>
<p>The post <a href="https://insidegnss.com/ionospheric-scintillation/">Ionospheric Scintillation</a> appeared first on <a href="https://insidegnss.com">Inside GNSS - Global Navigation Satellite Systems Engineering, Policy, and Design</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
