European Data Relay System
Enable an agent to recognise the European Data Relay System, assess a proposed satellite-data relay service, and identify the evidence and authority needed to request or modify that service.
Bundle → Layer → Finding → Questions Filled
6 bundles · 11 layers · 17 findings · 27 questions
System identity and composition Represent EDRS as a named distributed infrastructure. ESA describes geostationary nodes and European ground and control infrastructure: [ESA infrastructure](https://www.esa.int/Applications/Connectivity_and_Secure_Communications/EDRS/Infrastructure).
Named system boundary
Anchor the registry identity and distinguish infrastructure from programme and service names.
EDRS identity resolution
Record which names denote this infrastructure and which denote related programmes or commercial offerings.
- Which authoritative identifiers and descriptions establish the boundary of European Data Relay System? definition
- Under which dated descriptions is SpaceDataHighway coextensive with EDRS rather than a broader offering? boundary
Node and ground membership
Track the assets that constitute each dated operational configuration.
Payload, host and site roles
Separate relay payload membership from host-platform ownership and ground-site participation.
- Which payloads, host spacecraft and ground facilities belong to the configuration being assessed? boundary
- Which commissioning, reassignment or retirement records establish each asset's participation dates? provenance
Relay path and interoperability Represent the customer-to-GEO-to-ground path and its interface requirements. ESA describes optical collection from lower-orbit spacecraft followed by relay to European ground stations: [ESA laser communications](https://www.esa.int/Applications/Connectivity_and_Secure_Communications/EDRS/Laser_communications).
Customer-to-relay link
Assess the terminal pairing and conditions needed to establish an intersatellite connection.
Terminal-pair qualification
Require evidence for the particular customer terminal and EDRS node pairing.
- Which interface specifications and qualification results establish compatibility with the selected EDRS node? provenance
- Which pointing, acquisition, tracking and spacecraft-attitude constraints govern establishment of this link? measurement
Relay-to-customer handoff
Follow data through the ground link and onward to the agreed customer endpoint.
Ground delivery chain
Identify the receiving station, terrestrial route and interface at which delivery is recognised.
- Which ground-link band, receiving station and terrestrial handoff apply to the selected relay service? definition
- At which interface does EDRS responsibility for data delivery end and customer responsibility begin? boundary
Contact planning and capacity Translate orbital access and shared relay resources into feasible customer contacts.
Geometric access
Determine usable visibility for a specified spacecraft, node and epoch.
Usable contact envelope
Combine line of sight with terminal steering limits and documented exclusion conditions.
- What contact intervals follow from the customer's orbit and the selected node's dated position? measurement
- Which occultations, terminal limits or operational exclusions reduce those intervals? measurement
Scheduled resource allocation
Determine whether relay and ground resources can support a requested transfer.
Contact request feasibility
Evaluate transfer volume, usable duration, overhead and competing commitments together.
- What data volume can the allocated contact deliver after acquisition time, protocol overhead and ground-path limits? measurement
- Through which authorised process are contacts requested, prioritised, confirmed and rescheduled? action
Delivery evidence and continuity Assess actual delivery outcomes and the consequences of segment failures.
Delivery performance
Define measurable service outcomes at named observation points.
Latency and completeness evidence
Distinguish advertised capability, contracted targets and observed contact results.
- Which timestamps and endpoints define the reported delivery latency? definition
- Which counters or receipt records establish delivered volume, completeness and effective throughput for a contact? measurement
Interruption and recovery
Trace loss of service and identify evidenced recovery options.
Segment failure response
Separate acquisition failure, pointing loss, radio-link degradation and ground-network interruption when evidence permits.
- Which telemetry and event records identify the segment responsible for a failed or incomplete transfer? provenance
- Which documented recovery options permit reacquisition, another contact, another node or customer direct downlink? action
Service authority and operating constraints Record who may procure, schedule and operate EDRS services and which constraints govern the selected configuration.
Operational responsibility
Map customer, service operator, payload-control and host-spacecraft responsibilities.
Request and command authority
Associate each proposed action with the actor and interface authorised to perform it.
- Which current agreements identify the service provider and responsibility for each relay and ground segment? provenance
- Which actions may a customer agent submit directly, and which require operator or spacecraft-control approval? action
Configuration-specific constraints
Collect applicable spectrum, optical-operation, access-control and platform constraints.
Authorised operating envelope
Attach documented requirements to the exact node, terminal and ground route rather than assume universal certifications.
- Which spectrum authorisations, interface standards and optical operating restrictions apply, with issuing bodies and versions? provenance
- Which access permissions, host-platform power or thermal restrictions and maintenance exclusions must be satisfied before contact execution? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these identifiers and schemes hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these standards and regulation hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these typical measurements hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of European Data Relay System this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
What it is Filled
The European Data Relay System (EDRS) is a satellite communications infrastructure developed through a European Space Agency-Airbus public-private partnership that uses geostationary relay nodes, laser intersatellite links and radio downlinks to transfer data from supported spacecraft to ground stations with reduced delivery delay.
In scope
- EDRS geostationary relay nodes and their membership in the named system
- Optical intersatellite links, radio downlinks and participating ground infrastructure
- Compatibility between customer spacecraft terminals and EDRS relay services
- Contact planning, resource allocation and delivery-performance assessment
- Operational dependencies, service interruptions and authority boundaries
Out of scope
- Earth-observation instruments and interpretation of their measurements
- Complete engineering models of host spacecraft and individual laser terminals
- Corporate models of ESA, Airbus and component suppliers
- Generic satellite communications networks unrelated to EDRS
- Downstream processing and distribution of customer mission products
Why it exists Filled
Enable an agent to recognise the European Data Relay System, assess a proposed satellite-data relay service, and identify the evidence and authority needed to request or modify that service.
Distinguishing features Filled
- Identity must resolve to the named European relay infrastructure, rather than to the general class of data-relay satellites.
- Its defining relay path connects customer spacecraft to ground infrastructure through geostationary relay nodes; direct spacecraft-to-ground reception alone does not constitute EDRS.
- Optical intersatellite communication and the subsequent ground-delivery path must be distinguished; describing the entire path as a laser downlink is insufficient.
- EDRS-A and EDRS-C are constituent nodes, not interchangeable names for the whole system.
- References to SpaceDataHighway require a dated scope check before treating every associated asset or proposed extension as part of this registry entry.
What robots and AI may and may not do Filled
Must not
- Help interfere with, jam or intercept its links.
- Help gain access to its ground or space segments without authorization.
- Disclose non-public operational or security details of the system.
Only with a human decision
- Any request involving its operation, tasking or the data it relays.
May
- Describe the European Data Relay System, its purpose and its public mission record from official sources.
- Report publicly announced service status and capability.
Moral aspects Filled
- It relays data for earth observation, including emergency and security use.
- Interference with space infrastructure affects many users across borders.
Who is affected
- Users of earth observation data
- Emergency services
- Operators and partner agencies
Owners Filled
Steward
The operator of the relay system under its public-private partnership.
Master systems
- Satellite registration with the United Nations
- International frequency registers
Links to other meta-models Filled
parent
- Q100349043 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.european-data-relay-system
- Wikidata: Q784808 (https://www.wikidata.org/wiki/Q784808)
Direct properties required Filled
- System configuration: Dated membership links to relay payloads, host spacecraft, ground stations and control centres
- Relay-node orbital position: Geostationary longitude in degrees east, with epoch and source
- Relay-path interface: Optical intersatellite link, radio intersatellite link if supported, radio ground link or terrestrial handoff; qualified by node
- Customer-terminal compatibility: Spacecraft terminal configuration linked to an approved EDRS interface and qualification record
- Usable relay window: UTC start and end; usable duration in seconds
- Delivered data rate: bit/s at a named interface, with averaging interval and operating conditions
- Delivery latency: Seconds between explicitly identified acquisition, relay and delivery events
- Relay-service state: Unknown, planned, available, allocated, acquiring, relaying, degraded or unavailable
Recognition required Filled
- Not visible in ordinary use; consists of satellites in geostationary orbit and ground stations.
- Ground stations show large dish antennas within secured sites.
Capabilities and actions required Filled
- Resolve a named EDRS asset to its role and dated system membership.
- Assess whether a customer spacecraft has evidence of terminal and service compatibility.
- Compare candidate relay windows against volume and delivery-deadline requirements.
- Prepare a relay-service request for an authorised scheduling interface.
- Trace a missed delivery to the intersatellite, ground-link, control or terrestrial segment.
- Identify documented alternative contacts or delivery routes when a planned path is unavailable.
Hazards and failure modes required Filled
- Loss of a relay node interrupts time-critical data delivery.
- Laser terminals and links are targets for interference.
Standards and interfaces required Filled
- Radio Regulations, International Telecommunication Union.
- Convention on Registration of Objects Launched into Outer Space, United Nations.
Context of use required Filled
- This infrastructure relays data from supported spacecraft through geostationary nodes to ground stations when direct contact with a suitable receiving station is unavailable.
- It supports timely delivery of Earth observation data for applications such as environmental monitoring and emergency response.
Sources Filled
- Wikidata item Q784808: European Data Relay System - identity and sense of the item
- Wikipedia: European Data Relay System - general description of the item
Open questions
- What is the authoritative operational asset inventory at the assessment date, including whether any extensions belong to EDRS or a broader SpaceDataHighway offering?
- Which customer-terminal implementations are currently qualified for each node, and what interface documentation is available to service users?
- What latency, availability, throughput and delivery-completeness commitments apply to each service class and customer handoff?
- Which buffering, retransmission and alternative-node capabilities are actually implemented and contractually available?
- Which current technical standards, spectrum authorisations, optical restrictions and security requirements govern each operational route?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q784808/spec.json