System Architecture: Satellite-Based Navigation
Development of Satellite Navigation System (SNS) architecture involves dividing the
required functionality into manageable parts.
Current major systems:
o GPS (USA)
o GLONASS (Russia)
o Galileo (EU – under development)
Satellite Navigation System (SNS) Architecture
1. Inception Phase
The first steps in the development of the system architecture
Define boundary of the problem.
Determine mission use cases.
Analyze use cases to develop:
o Functional requirements
o Nonfunctional requirements
o Constraints
Vision
Provide effective and affordable Satellite Navigation System services for our
customers.
Requirements for the Satellite Navigation System
Functional Requirements
1. Provide SNS services
2. Operate SNS
3. Maintain SNS
Nonfunctional Requirements
High reliability for service guarantee.
High accuracy for current & future needs.
Functional redundancy for critical capabilities.
Extensive automation to reduce operational costs.
Easy maintenance to lower costs.
Extensible for future upgrades.
Long service life (especially for space-based parts).
Constraints
Must comply with international standards.
Use commercial-off-the-shelf (COTS) hardware & software.
Introduction to GPS (Global Positioning System)
Definition
GPS allows a user with a GPS receiver to know their position anywhere on Earth, at
any time, in any weather.
History
First GPS satellite launched: 1978.
Full system completed with 24 satellites: 1994.
Navigation evolved from:
o Landmarks
o Maps of earth/stars
o Compass, sextant, chronometer
o Ground-based radio navigation (e.g., LORAN)
Architecture Segments
1. Control Segment
o 6 ground stations.
o Master control station: Schriever Air Force Base, Colorado.
2. User Segment
o GPS receivers used for navigation.
3. Space Segment
o 24 satellites in orbit (11,000 nautical miles above Earth).
Working Principle (Trilateration)
Distance from satellites is calculated using time & position data.
1 satellite → user is on surface of an imaginary sphere.
2 satellites → location is on the intersection line of spheres.
3-4 satellites → exact position is determined.
Applications
Military:
Navigation (land, sea, air).
Weapon systems (e.g., cruise missiles).
Civilian:
Emergency services.
Engineering (e.g., Channel Tunnel construction).
Personal activities (driving, geocaching, hiking).
Defining the Boundaries of the Problem – SNS
Purpose: First step in designing the SNS architecture is to define its context.
Context diagram: Shows environment where SNS operates.
Actors (external entities interacting with SNS):
o People (users, operators)
o Other systems (provide services)
o Physical environment (space, ground)
Satellite Navigation System – Context Diagram
Purpose:
Shows external entities (actors) interacting with the Satellite Navigation System
(SNS).
Arrows indicate dependency direction.
Actors & Interactions
1. User → SNS
o Users depend on SNS for navigation services.
2. Operator → SNS
o Operators control and monitor SNS operations.
3. Maintainer → SNS
o Maintainers ensure the system is repaired and updated.
4. SNS → External Power
o SNS depends on external power sources to function.
5. SNS → External Communications
o SNS relies on communication systems for data exchange.
6. SNS → Atmosphere/Space
o SNS depends on space/atmospheric conditions for satellite operations.
Dependency Arrows
Arrow pointing to SNS: Actor depends on SNS.
Arrow from SNS to actor: SNS depends on that external entity.
Mission Use Case
A mission use case is a high-level description of how a system interacts with its actors to
achieve its primary mission objectives, focusing on end-to-end services rather than detailed
functions.
Example (SNS):
User → Navigation Services
Operator → Mission Operations
Maintainer → Maintenance Operations
Packages for the SNS Mission Use Cases – shows mission-related tasks for different actors
(User, Operator, Maintainer).
Figure → The SNS Logical Architecture – shows high-level system components (Launch
Segment, Satellite Segment, Ground Segment, User Segment) and how they connect.
Conceptual Model
The system is divided into four main segments to represent the highest-level logical
architecture:
1. Ground Segment
o Controls, monitors, and maintains the satellites.
o Includes mission control centers, ground antennas, and data processing
facilities.
2. Launch Segment
o Responsible for delivering satellites into orbit.
o Includes launch vehicles and supporting infrastructure.
3. Satellite Segment
o The space-based components that perform navigation functions.
o Includes GPS satellites, communication links, and onboard systems.
4. User Segment
o The receivers and devices that use navigation data.
o Includes mobile phones, aircraft navigation systems, ships, etc.
OperateSNS Mission Use Case Package
Goal: Define the main mission use cases for operating the Satellite Navigation System (SNS)
based on overall system operation.
Identified Mission Use Cases
1. Initialize Operations – Start up the system and prepare it for functioning.
2. Provide Normal Operations – Handle day-to-day navigation services.
3. Provide Special Operations – Handle special or unique mission needs.
4. Terminate Operations – Shut down the system safely.
Black-Box Activity Diagram for Initialize Operations.
Left swimlane (Operator): actions like ordering launch preparations, launch, activation,
checkout, etc.
Right swimlane (SNS): system responses like preparing for launch, launching, activating
satellite, preparing for operations, etc.
Figure System Use Cases for Initialize Operations
System Use Cases for Initialize Operations
System Use Case Description
Prepare the launcher and its satellite payload for launch, and perform the
Launch Satellite
launch.
Fly the launcher to the point at which the satellite payload will be
Fly to Separation
separated. This involves the use and separation of multiple launcher
Point
stages.
Perform the activation of the satellite in preparation for its deployment
Activate Satellite
from the launcher.
Separate Satellite Deploy the satellite from the launcher.
Move Satellite Use the satellite bus propulsion capability to position the satellite into the
into Orbit correct orbital plane.
Elaboration
System Architecture – Elaboration Phase
Developing a Good Architecture
Well-defined layers of abstraction – each layer = coherent part of the system.
Clear separation of concerns – interface vs. implementation.
Implementation changes possible without breaking client assumptions.
Common behavior achieved through abstractions & common mechanisms.
Architectural Development Activities
1. Identify elements at the right level of abstraction.
2. Define semantics & attributes of elements.
3. Specify relationships between elements (boundaries, collaborations).
4. Refine elements iteratively for further analysis.
Validating Proposed Architecture
Allow experimentation with alternative approaches before final decisions.
Use modeling, simulation, prototyping (various scales).
Perform macro-level analysis of SNS architecture.
Validate assumptions & decisions early to find problems sooner.
Early detection → cheaper changes for requirements & architecture.
Allocating Nonfunctional Requirements
Nonfunctional requirements (e.g., performance, reliability, standards compliance) are
assigned at segment level.
Then distributed to subsystem use cases, using similar allocation methods.
Recursive application – applied from system → segments → subsystems.
Example constraints:
Compatibility with international standards.
Maximum use of COTS (Commercial Off-The-Shelf) hardware/softwar
Stipulating the System Architecture & Deployment
UML 2.0 Component Diagram used for hierarchical decomposition of the system.
Shows highest-level abstraction of the Satellite Navigation System (SNS):
o Segments (main system parts).
o Relationships & interfaces between them.
The Component Diagram for the Satellite Navigation System
Figure – Component Diagram
Ball-and-socket notation → LaunchSupport interface (physical connection).
Dashed dependency line → PositionInformation interfaces (data exchange).
Components:
o LaunchSegment – handles launch support.
o SatelliteSegment – satellite in space.
o GroundSegment – control, communication, maintenance.
System Architecture & Deployment
The Deployment of SNS Segments
The Deployment of SNS Segments
3) Construction Phase
After the Elaboration Phase, a stable system architecture is ready.
Changes in this phase are usually small and affect only lower-level
components, not the main system segments.
Major segments (like Launch, Satellite, Ground, and User) remain
unchanged.
4) Post-Transition Phase
The system is designed with two important goals:
Extensibility – easy to add new functions in the future.
Long Service Life – should work reliably for many years.
