PDR.04 Interface Requirements - ASTRONbroekema/papers/SDP-PDR/PDR04... · 2015. 7. 27. · Interface Requirements 2.1 External Interfaces SDP Interface requirements and associated

Document No: SKA-TEL-SDP-0000039 Unrestricted

Revision: 01 Author: F. Graser

Release Date: 2015-02-09 Page 1 of 40

PDR.04 Interface Requirements

Document number……………………………………………………………SKA-TEL-SDP-0000039

Context………………………………………………………………………………………...….……SE

Revision…………………………………………………………………………………………………01

Author………………………………………………………………….………F. Graser, B. Opperman

Release Date…………………………………………………………………………..…….2015-02-09

Document Classification…………………………………………………………….……. Unrestricted

Status………………………………………………………………………………….……………. Draft

Name Designation Affiliation

Signature & Date:

Signature:

Email:Ferdl Graser (Feb 9, 2015)Ferdl Graser

SDP Systems Engineer

[email protected]

SKA-Science Data ProcessorFerdl Graser

https://secure.echosign.com/verifier?tx=XJEHDWA5R48XN63




Name Designation Affiliation

Signature & Date:

Version Date of Issue Prepared by Comments

0.1

ORGANISATION DETAILS

Name Science Data Processor Consortium

Signature:

Email:Paul Alexander (Feb 9, 2015)Paul Alexander

SDP Lead

[email protected]

University of CambridgePaul Alexander

https://secure.echosign.com/verifier?tx=XJEHDWA5R48XN63




Table of Contents Table of Contents ........................................................................ Error! Bookmark not defined.

List of Figures ............................................................................................................................ 4

List of Tables ............................................................................................................................. 4

Introduction ................................................................................................................................ 5

References ................................................................................................................................ 6

Applicable Documents ............................................................................................................ 6

Reference Documents ............................................................................................................ 6

1 Interface Register .......................................................................................................... 7

1.1 External Interfaces ..................................................................................................... 7

1.2 Internal Interfaces .....................................................................................................10

2 Interface Requirements ...............................................................................................13

2.1 External Interfaces ....................................................................................................13




List of Figures

Figure 1. Diagram illustrating the context of SDP with regard to other Elements (sub-

systems). .................................................................................................................................. 7

Figure 2: Diagram illustrating L4 Internal faces of Top Level SDP components. ................10

List of Tables

Table 1. External SDP interfaces. ............................................................................................ 8

Table 2. SDP L4 internal interfaces. ......................................................................................11




Introduction

In Systems Engineering an interface can be identified as any point where a system and

something, or someone, meet. The interface point may include other systems, internal

hardware, circuitry, external peripherals, networks, system users, etc. These interfaces are

described in an Interface Control Document (ICD) which defines and controls the interfaces of

the system and thereby bound its requirements.

In the context of the SKA1’s Science Data Processor (SDP) this ICD describes all possible and

potential external and internal inputs and outputs to and from the SDP and (other) relevant

subsystems and elements. The external Level 3 (L3) interfaces between SDP and other sub-

systems, i.e., SaDT, CSP, TM, INFRA, are illustrated in Figure 1. This ICD also describes the

internal SDP Level 4 (L4) interfaces between the Hardware, Software, Data Layer, Data

Delivery, Monitor and Control, Pipeline elements (Figure 2) which comprise the SDP. These

interfaces are described in more detail in the following paragraphs.




References

Applicable Documents

The following documents are applicable to the extent stated herein. In the event of conflict

between the contents of the applicable documents and this document, the applicable

documents shall take precedence.

Reference Number Reference

AD[01] SKA-TEL.SDP.SE-TEL.CSP.SE-ICD-001

AD[02] SKA-TEL.SDP.SE-TEL.TM.SE-ICD-001

AD[03] SKA-TEL.SDP.SE-TEL.INFRA.SE-ICD-001

AD[04] SKA-TEL.SDP.SE-TEL.INFRA.SE-ICD-001

AD[05] SKA-TEL.SADT.SE-TEL.SDP.SE-ICD-001

Reference Documents

The following documents are referenced in this document. In the event of conflict between the

contents of the referenced documents and this document, this document shall take

precedence.

There are no reference documents for this document.




1 Interface Register

1.1 External Interfaces

The SDP’s L3 external interfaces are summarised in Figure 1 and detailed in Table 1. These

interfaces are owned by SKAO.

Figure 1. Diagram illustrating the context of SDP with regard to other Elements (sub-systems).




Table 1. External SDP interfaces.

Connection connects to

I.S1L.SDP_CSP.001 SKA1-Low SDP_CSP Visibility Data Interface

C Science Data Processor CSP Central Signal Processor

I.S1M.SDP_CSP.002 SKA1-Mid SDP_CSP Pulsar Search Data

Interface


I.S1M.SDP_CSP.003 SKA1-Mid SDP_CSP Pulsar Timing Data

Interface


I.S1S.SDP_CSP.001 SKA1-Survey SDP_CSP Visibility Data Interface


I.S1L.SDP_INFRA-AUS.001 SKA1-Low SDP_INFRA-AUS Local

Infrastructure Interface

C Science Data Processor LINFA-AUS Local Infrastructure Australia

I.S1S.SDP_INFRA-AUS.001 SKA1-Survey SDP_INFRA-AUS Local

Infrastructure Interface

C Science Data Processor LINFA-AUS Local Infrastructure Australia

I.S1S.SDP_INFRA-SA.001 SKA1-Mid SDP_INFRA-SA Local Infrastructure

Interface

C Science Data Processor LINFA-SA Local Infrastructure South Africa

I.S1L.SADT_SDP.001.VIS CSP-SDP_VIS to SDP_SKA1_LOW

C Science Data Processor SaDT Signal and Data Transport

I.S1L.SADT_SDP.004 SDP to SADT.To_External_SKA1_LOW


I.S1L.SADT_SDP.010 TM_NETWORK to SDP_SKA1_LOW


I.S1M.SADT_SDP.003.PSS (CSP-SDP_PSS to SDP_SKA1_MID) Pulsar

Survey Search


I.S1M.SADT_SDP.003.PST (CSP-SDP_PST to SDP_SKA1_MID ) Pulsar

timing


I.S1M.SADT_SDP.003.VIS CSP- C Science Data Processor




SDP_VIS to SDP_SKA1_MID SaDT Signal and Data Transport

I.S1M.SADT_SDP.009 SAT to SDP_SKA1_MID


I.S1M.SADT_SDP.012 TM_NETWORK to SDP_SKA1_MID


I.S1S.SADT_S5 SDP to SADT to _External_SKA1_SURVEY


I.S1S.SADT_SDP.002.VIS CSP-SDP_VIS to SDP_SKA1_SURVEY


I.S1S.SADT_SDP.011 TM_NETWORK to SDP_SKA1_SURVEY


I.S1L.SDP_TM.001 SKA1-Low SDP_TM Control and Monitoring

Interface

C Science Data Processor TM Telescope Manager

I.S1L.SDP_TM.002 SKA1-Low SDP_TM Telescope State Information

Interface


I.S1M.SDP_TM.002 SKA1-Mid SDP_TM Telescope State Information

Interface


I.S1S.SDP_TM.001 SKA1-Survey SDP_TM Control and Monitoring

Interface


I.S1S.SDP_TM.002 SKA1-Survey SDP_TM Telescope State Information

Interface





1.2 Internal Interfaces

All the SDP L4 internal interfaces are summarised in Figure 2 and detailed in Table 2. These

interfaces are owned by SDP.

Figure 2: Diagram illustrating L4 Internal faces of Top Level SDP components.




Table 2. SDP L4 internal interfaces.

Connection connects to

SDP.C1_C2.001 OS to hardware C.1 Hardware Compute Platform C.2 Software Compute Platform

SDP.C1_C2.002 Hardware sensors C.1 Hardware Compute Platform C.2 Software Compute Platform

SDP.C1_C2.003 Out of Band Management to OS. (indirect support to

LMC)

C.1 Hardware Compute Platform C.2 Software Compute Platform

SDP.C2_C3.001 Container interface (OS packages required etc...)

C.2 Software Compute Platform C.3 Data Layer

SDP.C2_C3.002 Storage Interface C.2 Software Compute Platform C.3 Data Layer

SDP.C2_C3.003 Middleware interface (messaging, notifications, etc...)

C.2 Software Compute Platform C.3 Data Layer

SDP.C3_C4.001 Additional services provided by Pipeline wrapper supplied by

Data Layer (essentially through Data Objects like visibilities, weights, flags

etc.).

C.3 Data Layer C.4 Pipeline Components

SDP.C3_C4.002 Interface at the level of a Data Object.

C.3 Data Layer C.4 Pipeline Components

SDP.C3_C5.001 Interface at the level of a Data Product (collection of DOs)

C.3 Data Layer C.5 Data Delivery Platform

SDP.C3_C5.002 Make replication request on DP


SDP.C3_C5.003 Meta information on DP (locality, size, creation date, owner, SB,

etc...)


SDP.C3_C5.004 Notification on availability of new DP


SDP.C3_C5.005 Open question on resource availability (does it come from

LMC / Data Layer)





SDP.C3_C5.006 Replicate catalogue to DDL


SDP.C6_C1.001 LMC hardware control C.1 Hardware Compute Platform C.6 Local Monitoring and Control

SDP.C6_C2.001 Out of Band Management to LMC

C.2 Software Compute Platform C.6 Local Monitoring and Control

SDP.C6_C2.002 Monitor OS to LMC C.2 Software Compute Platform C.6 Local Monitoring and Control

SDP.C6_C2.003 Control OS to LMC C.2 Software Compute Platform C.6 Local Monitoring and Control

SDP.C6_C3.001 Monitor metrics, power etc to LMC

C.3 Data Layer C.6 Local Monitoring and Control

SDP.C6_C3.002 Control metrics, power etc to LMC


SDP.C6_C3.003 Data Flow Manager to Data Layer Interface


SDP.C6_C4.001 Pipeline metrics to LMC C.4 Pipeline Components C.6 Local Monitoring and Control

SDP.C6_C4.002 Pipeline to Local Telescope Model interfacePL open

question

C.4 Pipeline Components C.6 Local Monitoring and Control

SDP.C6_C5.001 General specification of LMC guidelines - monitoring, power

control etc..

C.5 Data Delivery Platform C.6 Local Monitoring and Control

SDP.C6_C5.002 Single document with specialisation where appropriate (e.g.

DFM to DL and Pipeline metrics)


SDP.C6_C5.003 Authentication Interface (to be finalised)





2 Interface Requirements

2.1 External Interfaces

SDP Interface requirements and associated Verification methods are presented in Table 3. Note

that verification methods for interface requirements from the SaDT element are not shown here

as the requirements are led by SaDT and are not available to SDP at this time.

Table 3. SDP interface requirements and verification methods.

Requirement Description verified by

SDP_REQ_INT-1 Interface Management Self-

description- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP shall provide a self-description on request from the TM. Through self-

description the SDP provides information that describes the content of the interface,

including a set of valid commands, parameters, monitoring points, alarms and

events.

VR-1 Verification by Test

SDP_REQ_INT-2 Interface Management Structure of

Reporting- SDP SKA1 Low Survey Mid. Monitor and

Control

SDP shall report information in a hierarchical structure, including a product breakdown

structure and a capability structure.

VR-3 Verification by Demonstration

SDP_REQ_INT-3 Interface Management Configure

interface- SDP SKA1 Low Survey Mid. Monitor and

Control

The TM shall be able to request the SDP to configure the level of reporting of monitoring

points, alarms, events and logs.


SDP_REQ_INT-4 Interface Management Alarm and

event filtering- SDP SKA1 Low Survey Mid. Monitor

and Control

The SDP shall filter alarms and events to prevent the reporting of alarms for items that are not fitted or that are under maintenance.


SDP_REQ_INT-5 Control Configure SDP parameters-

SDP SKA1 Low Survey Mid. Monitor and Control

The TM shall configure the SDP parameters as required for the observation.


SDP_REQ_INT-6 Safety Locally failsafe- SDP SKA1 Low Survey Mid. Monitor

and Control

The SDP shall be designed to be locally fail-safe and not be dependent on any external

inputs from TM for safety.





SDP_REQ_INT-7 Monitoring. Report external

state model- SDP SKA1 Low Survey Mid. Monitor

and Control

The SDP shall report the SDP element external state to TM.


SDP_REQ_INT-8 Monitoring.. Report internal

states- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP shall report the internal states of sub-elements to TM.


SDP_REQ_INT-9 Monitoring. Report alarms-


The SDP shall report alarms for conditions and failures that: a) pose hazards to

equipment, data or personnel b) reduce the effectiveness of SDP to perform its prime

functions or provide capabilities.


SDP_REQ_INT-10 Monitoring. Report specific

alarm information- SDP SKA1 Low Survey Mid.

Monitor and Control

The SDP shall provide the following alarm-related data to the TM: a) Time of detection:

Accuracy of TBD milliseconds with a resolution of TBD milliseconds b) Severity of the Event: Categorised by at least 3 levels of comparison c) Description of the event that

caused the alarm


SDP_REQ_INT-11 Monitoring. Log reporting- SDP SKA1 Low Survey

Mid. Monitor and Control

The SDP shall report log messages to TM. VR-3 Verification by Demonstration

SDP_REQ_INT-12 Monitoring. Log level- SDP

SKA1 Low Survey Mid. Monitor and Control

The TM shall control the level at which log messages are reported.


SDP_REQ_INT-13 Monitoring. Drill-down

capability- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP shall make provision for an extensive set of "drill-down" monitoring

points in the SDP to enable a capability for fault diagnostics.


SDP_REQ_INT-14 Monitoring. Drill-down

activation- SDP SKA1 Low Survey Mid. Monitor and

Control

The activation of the drill-down capability is TBD.


SDP_REQ_INT-15 Monitoring. Report failures-


The SDP shall report detected failures, and identification of the source of the failure in

the SDP product breakdown structure, based on the FMECA analysis. Where

applicable, faulty Line Replaceable Units (LRUs) shall be identified.





SDP_REQ_INT-16 Monitoring. Failure

prediction- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP shall report monitoring points that are required for preventive maintenance, as

identified in the FMECA analysis.


SDP_REQ_INT-17 Monitoring. Capability

reporting- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP, when requested by the TM to commit/engage a capability, shall report the availability of that capability as either: a) Not

available b) Available, with degraded performance c) Available with full

performance


SDP_REQ_INT-18 Monitoring. Resource

Overview- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP shall present a high-level overview of SDP resource availability.


SDP_REQ_INT-19 Monitoring. Current

Capability availability- SDP SKA1 Low Survey Mid.

Monitor and Control

The SDP shall report on all capabilities available to the telescope.


SDP_REQ_INT-20 Monitoring. Event reporting - SDP SKA1 Low Survey Mid. Monitor and Control

The SDP shall report the following events to TM: a) Processing progress: SDP shall

report on "Processing Started", "Processing Completed" and "Processing Success/Fail" events to TM to indicate the progress of a

capability. b) Mode/Frequency change: SDP shall report on the successful/failed mode or

observational frequency band change requested by the TM. c) VO event: SDP

shall report on the creation of a VO event.


SDP_REQ_INT-21 Engineering Interface- SDP


The TM shall provide a "tunnelling" capability to access engineering interfaces

of sub-elements remotely.

SDP_REQ_INT-22 Life-cycle Management. Remote

updates- SDP SKA1 Low Survey Mid. Monitor and

Control

The SDP shall enable patching and upgrade of software and firmware remotely.


SDP_REQ_INT-23 Life-cycle Management.

Facilitate remote updates- SDP SKA1 Low Survey

Mid. Monitor and Control

The TM shall provide "tunnelling" capability to facilitate remote software and firmware

upgrades.





SDP_REQ_INT-24 Life-cycle Management. Report version information - SDP


The SDP shall report version information of all software and firmware.


SDP_REQ_INT-25 Data Transport. Maximum data

rate- SDP SKA1 Low Survey Mid. Monitor and

Control

The maximum data rate for the transfer of control and monitoring data to facilitate the

SDP_TM interface is TBD.


SDP_REQ_INT-26 Protocol. Communications protocol- SDP SKA1 Low Survey Mid. Monitor and

Control

The communications protocol for this interface is defined in Section 5 of this

document.

SDP_REQ_INT-27 Data Identification. Exclusions- SDP SKA1 Low Survey Mid. Telescope State

Information

The TM shall ensure that all Telescope State Information contained in the Telescope

Model will be available for transmission to the SDP in one of the categories defined

below.

SDP_REQ_INT-28 Data Identification. Critical

information- SDP SKA1 Low Survey Mid. Telescope

State Information

The TM shall send and the SDP shall receive Telescope State Information as

detailed in Appendix X within TBD seconds of the TM receiving such state information. These information points are classified as critical for the purposes of this document.


SDP_REQ_INT-29 Data Identification. Non-critical information- SDP SKA1

Low Survey Mid. Telescope State Information

The TM shall send and the SDP shall receive Telescope State Information other

than that detailed in Appendix X within TBD seconds of the TM receiving such state

information. These information points are classified as non-critical for the purposes of

this document.


SDP_REQ_INT-30 Data Transport. Maximum data

rate- SDP SKA1 Low Survey Mid. Telescope

State Information

The maximum data rate for the transfer of control and monitoring data to facilitate the

SDP_TM interface is TBD.


SDP_REQ_INT-31 Protocol. Communications protocol- SDP SKA1 Low Survey Mid. Telescope

State Information

The communications protocol for this interface is defined in Section 5 of this

document.

SDP_REQ_INT-32 Visibility Organisation- SDP SKA1

Low, Survey and Mid. Visibility Data

See 2.1.3 for information on data organisation.




SDP_REQ_INT-33 Visibility Coverage- SDP SKA1 Low, Survey and Mid. Visibility

Data

For a given set of frequency channels the CSP shall produce all possible cross-

correlations and auto-correlations.


SDP_REQ_INT-34 Visibility Transport- SDP SKA1 Low, Survey and Mid. Visibility

Data

The CSP shall produce visibility data using UDP/IP on IEEE 802.3 Ethernet frames.


SDP_REQ_INT-35 Visibility MTU- SDP SKA1 Low,

Survey and Mid. Visibility Data

The UDP MTU shall be as large as possible, whilst still maintaining transmission compatibility with COTS networking

equipment.

VR-2 Verification by Analysis

SDP_REQ_INT-36 Visibility Format- SDP SKA1 Low, Survey and Mid. Visibility

Data

See 2.1.3 for information on data format.

SDP_REQ_INT-37 Visibility Communications protocol- SDP SKA1 Low, Survey and Mid. Visibility Data

SPEAD [AD1] with visibility specific payload format. The communications protocol for this

interface is further defined in Section 5 of this document.

SDP_REQ_INT-38 Visibility Routing- SDP SKA1 Low, Survey and Mid. Visibility

Data

Subsets of the visibility data hierarchy shall be routable to specific IP and port

combinations. Subsets are still TBD.


SDP_REQ_INT-39 Visibility Multiple streams- SDP

SKA1 Low, Survey and Mid. Visibility Data

The CSP, when producing multiple streams of visibility data, will provide sufficient control

and meta-data to allow each stream to be independently received by the SDP.


SDP_REQ_INT-40 Visibility SKA-1 Low Data Rate- SDP SKA1 Low, Survey and Mid.

Visibility Data

The CSP-Low shall send and the SDP-Low shall receive visibility data at a maximum

rate of 72.64 Tbps (TBC).


SDP_REQ_INT-41 Visibility SKA-1 Survey Data Rate- SDP SKA1 Low, Survey and Mid. Visibility Data

The CSP-Survey shall send and the SDP-Survey shall receive visibility data at a maximum rate of 45.54 Tbps (TBC).


SDP_REQ_INT-42 Visibility SKA-1 Mid Data Rate- SDP SKA1 Low, Survey and Mid.

Visibility Data

The CSP-Mid shall send and the SDP-Mid shall receive visibility data at a maximum

rate of 33.45 Tbps (TBC).


SDP_REQ_INT-43 Visibility Meta-data- SDP SKA1 Low,

Survey and Mid. Visibility Data

The CSP shall provide sufficient meta-data with the visibility data to allow the receiver to

fully decode any encapsulation without additional information. Specifically this will

include the ability to convert timestamp information into an absolute time standard

(UTC, TBD).





SDP_REQ_INT-44 Visibility Antenna Labelling- SDP


Metadata included with visibility data will include labels of antennas forming the

visibility in the format as used by TM. The order of antenna labels forming the visibility shall be according to the sign convention of

the SKA telescope.


SDP_REQ_INT-45 Visibility Timestamps- SDP SKA1


64-bit integer UTC timestamp epoch of the last sample that was integrated (i.e. whether flagged/not correlated, or not). 32 bits is 1 second count since UTC epoch; 32 bits is fraction of a 1 second, providing ~0.25 ns timestamp resolution. As a minimum each

integration time (60ms) needs to be uniquely identified. Nanosecond timestamp resolution

is needed for pulsar phase binning use cases.


SDP_REQ_INT-46 Visibility Channel / Baseline ID- SDP SKA1 Low, Survey and Mid.

Visibility Data

Channel ID, baseline ID and beam ID (Survey only) once per integration time. 26-bit baseline polarisation ID (to allow for 10e4 stations in SKA2) and a 22-bit channel ID for Low and Mid. 22-bit baseline ID (to allow for ~3k stations in SKA2), a 20-bit channel ID, and a 6-bit beam ID for Survey. Provides

offset into channel / baseline visibility array for this particular heap.


SDP_REQ_INT-47 Visibility Channel / Baseline Count- SDP SKA1 Low, Survey and Mid. Visibility Data

Provides counts for the two dimensions of the channel / baseline visibility array. When

used in conjunction with the ID, uniquely identifies the portion of the overall array in

this heap. 26 bits for the baseline count and 22 bits for the channel count.


SDP_REQ_INT-48 Visibility Schedule Block ID- SDP


A 64-bit schedule block ID used to uniquely associate correlator data with a particular

observation. This ID will be provided to the CSP by TM. Actual bit length is TBD

pending decision from TM.


SDP_REQ_INT-49 Visibility Hardware ID- SDP SKA1


Hardware source ID, 24-bit. This indicates the hardware source of the data for

testing/troubleshooting/back tracing to a hardware fault.


SDP_REQ_INT-50 Visibility Time Centroid- SDP SKA1


Time centroid index (TCI), as 8-bit integer (TBD). Is the unit-less calculated centroid of

the integration interval.


SDP_REQ_INT-51 Visibility Complex Visibility- SDP


Complex visibility, two 32-bit single-precision floating point numbers already data valid

normalized.





SDP_REQ_INT-52 Visibility Flagging Fraction- SDP


8-bit (TBD) integer indicating the fraction of data (FD) that was correlated. Encode the square root of FD in 8 bits. Reserve 1 bit of

the FD for a hardware fault flag


SDP_REQ_INT-53 Visibility Normalisation- SDP SKA1


The CSP shall not perform Van Vleck, or any other normalization corrections, on the

visibility data.


SDP_REQ_INT-54 Visibility Delay Tracking- SDP SKA1


The CSP shall apply delay tracking and fringe stopping corrections to each channel, as supplied by the TM, to all visibility data

sent to the SDP.


SDP_REQ_INT-55 Visibility Doppler Tracking- SDP


The CSP shall apply Doppler tracking corrections, as supplied by the TM, to all

visibility data sent to the SDP


SDP_REQ_INT-56 Pulsar Search Transport- SDP

SKA1 Mid. Pulsar Search Data

The CSP shall produce pulsar search data using TCP/IP on IEEE 802.3 Ethernet

frames.


SDP_REQ_INT-57 Pulsar Search Format- SDP SKA1

Mid. Pulsar Search Data

The format for pulsar search candidates is TBD.


SDP_REQ_INT-58 Pulsar Search Communications protocol- SDP SKA1 Mid.

Pulsar Search Data

Unidirectional high-level message passing protocol running on TCP/IP.5


SDP_REQ_INT-59 Pulsar Search SKA-1 Mid Data Rate- SDP SKA1 Mid. Pulsar Search Data

The CSP-Mid shall send and the SDP-Mid shall receive pulsar search data at a

maximum rate of 10 Gbps. The CSP-Mid shall send and the SDP-Mid shall receive transient or single pulse search data at a

maximum data rate of 4 Gbps.


SDP_REQ_INT-60 Pulsar Search Meta-data- SDP

SKA1 Mid. Pulsar Search Data

The CSP shall provide sufficient meta-data with the pulsar search data to allow the

receiver to fully decode any encapsulation without additional information.


SDP_REQ_INT-61 Pulsar Search Candidates- SDP SKA1 Mid. Pulsar Search

Data

List of pulsar search candidates in TBD format.


SDP_REQ_INT-62 Pulsar Timing Transport- SDP

SKA1 Mid. Pulsar Timing Data

The CSP shall produce pulsar timing data using TCP/IP on IEEE 802.3 Ethernet

frames.





SDP_REQ_INT-63 Pulsar Timing Format- SDP SKA1

Mid. Pulsar Timing Data

1. The format for the pulsar timing data is defined as PSRFITS file format. Individual

files are 10s dumps Each file is max 68 MB per beam per dump

SDP_REQ_INT-64 Pulsar Timing Communications protocol- SDP SKA1 Mid.

Pulsar Timing Data

File transfer between CSP and SDP using rsync (TBC).


SDP_REQ_INT-65 Pulsar Timing SKA-1 Mid Data Rate- SDP SKA1 Mid.

Pulsar Timing Data

The CSP-Mid shall send and the SDP-Mid shall receive pulsar timing data at a

maximum rate of 9.4 Gbps (this data rate is for the payload data only and does not

include overhead for the file format, protocol, etc.)


SDP_REQ_INT-66 Pulsar Timing Meta-data- SDP


The CSP shall provide sufficient meta-data with the pulsar timing data to allow the


SDP_REQ_INT-67 Pulsar Timing Communications protocol- SDP SKA1 Mid.

Pulsar Timing Data

File transfer between CSP and SDP using rsync (TBC).


SDP_REQ_INT-68 Pulsar Timing SKA-1 Mid Data Rate- SDP SKA1 Mid.

Pulsar Timing Data

The CSP-Mid shall send and the SDP-Mid shall receive pulsar timing data at a

maximum rate of 9.4 Gbps (this data rate is for the payload data only and does not

include overhead for the file format, protocol, etc.)


SDP_REQ_INT-69 Pulsar Timing Meta-data- SDP


The CSP shall provide sufficient meta-data with the pulsar timing data to allow the



SDP_REQ_INT-70 Rack size- SDP Compute SKA1

Common Mechanical

The racks referred to hereafter shall be of size 1200mm D x 600mm W x 2100mm H.

VR-4 Verification by Inspection

SDP_REQ_INT-71 Rack standard- SDP Compute

SKA1 Common Mechanical

The racks of equipment provided by the SDP for installation in the allocated space

provided by INFRA shall meet the IEC 60297-3-100 standard TBC in terms of

mechanical interfaces and size.


SDP_REQ_INT-72 Service area- SDP Compute SKA1

Common Mechanical

Additional aisle space in front of racks of 1200mm will be provided by INFRA for each rack of SDP equipment to allow for doors,

cabling and operator access.





SDP_REQ_INT-73 Floor loading- SDP Compute


Equipment provided by the SDP for installation in the allocated space provided

by INFRA shall have a maximum floor loading of 2000 kg per square metre TBC.


SDP_REQ_INT-74 Connection- SDP Compute SKA1 Common Mechanical

INFRA will provide a fluid interface to each SDP rack that conforms to the TBD

standard.


SDP_REQ_INT-75 Temperature- SDP

Compute SKA1 Common Mechanical

INFRA shall ensure that the temperature of the cooling fluid at the point of ingress to the

SDP rack is no more than 22 degrees Celsius TBC.


SDP_REQ_INT-76 Capacity- SDP Compute


The SDP shall ensure that the SDP rack presents no more than 50 kW TBC of heat

load to the cooling medium.


SDP_REQ_INT-77 Environment- SDP


INFRA shall ensure that the ambient environment of the SDP equipment is no

more than 25 degrees Celsius TBC.


SDP_REQ_INT-78 Additional load- SDP


The SDP shall ensure that the SDP equipment inserts no more than TBD kW of additional load into the INFRA environment.


SDP_REQ_INT-79 Data centre power efficiency-

SDP Compute SKA1 Common Mechanical

The data centre housing SDP equipment shall have a PUE no greater than 1.25.


SDP_REQ_INT-80 Per rack power consumption- SDP Compute SKA1 Common

Mechanical

The SDP equipment will be limited to a maximum of 50 kW per rack.


SDP_REQ_INT-81 Nominal voltage- SDP Compute


INFRA shall provide a power supply with a nominal voltage of 230V AC.


SDP_REQ_INT-82 Level variation- SDP Compute


INFRA shall provide a power supply with a variation of no more than TBD % from the

steady state level.


SDP_REQ_INT-83 Nominal level- SDP Compute SKA1

Common Mechanical

INFRA shall provide a power supply with a steady state voltage equal to the specified

nominal voltage +10/-6% TBC.


SDP_REQ_INT-84 Harmonic distortion- SDP Compute SKA1 Common

Mechanical

INFRA shall provide a power supply with total harmonic distortion less than TBD %.





SDP_REQ_INT-85 Frequency variation- SDP Compute SKA1 Common

Mechanical

INFRA shall provide a power supply with power supply frequency of 50Hz +/-TBD %.


SDP_REQ_INT-86 Controlled shutdown under UPS- SDP Compute SKA1

Common Mechanical

INFRA shall provide uninterruptable power at a TBD level for a duration of TBD to the SDP in the event of a major power supply

failure.


SDP_REQ_INT-87 Redundancy- SDP


Each rack shall be supplied by two independent power feeds.


SDP_REQ_INT-88 Scope- SDP Compute SKA1 Common Mechanical

An access control system provided by INFRA shall prevent unauthorised access to

all SDP equipment.


SDP_REQ_INT-89 Logging- SDP Compute


The access control system provided by INFRA shall ensure that all access attempts

to the SDP equipment are logged.


SDP_REQ_INT-90 Configuration- SDP


The access control system provided by INFRA shall have the ability to provide temporary access for contractors and maintainers as authorised by the SDP.


SDP_REQ_INT-91 Ease of Use- SDP Compute SKA1

Common Mechanical

The access control system provided by INFRA shall not impact on staff activities

once inside the secure area.

SDP_REQ_INT-92 Authentication- SDP


The access control system provided by INFRA shall use authentication media that is

revocable and replaceable.


SDP_REQ_INT-93 Space allocation- SDP Compute

SKA1 Mid Mechanical

INFRA-SA shall provide sufficient floor space for the installation of 100 racks TBC.


SDP_REQ_INT-94 Cable trays- SDP Compute SKA1

Mid Mechanical

INFRA-SA shall supply and install cable trays sufficient to cover the following requirements [width, mass loading,

above/below are TBD].


SDP_REQ_INT-95 Overall power consumption- SDP

Compute SKA1 Mid Electrical

The SDP equipment will be limited to an overall power limit of 3.2MW.





SDP_REQ_INT-96 Medium- SDP Compute SKA1 Mid Fire Control

The fire control system provided by INFRA-SA shall use a medium that complies to the following South African standards (TBD) in

order to ensure that unnecessary damage is not caused to SDP equipment in the case of

a fire suppression event.


SDP_REQ_INT-97 Warning- SDP Compute SKA1 Mid Fire Control

The fire control system provided by INFRA-SA shall provide visual and audible warnings prior to the activation of the fire suppression

system to allow evacuation of personnel from the environment.


SDP_REQ_INT-98 Space allocation- SDP Compute

SKA1 Low Mechanical

INFRA-AUS shall provide sufficient floor space for the installation of 25 racks TBC.



Low Mechanical

INFRA-AUS shall supply and install cable trays sufficient to cover the following requirements [width, mass loading,




Compute SKA1 Low Electrical

The SDP equipment will be limited to an overall power limit of 0.75 MW TBC.


SDP_REQ_INT-101 Medium- SDP Compute SKA1 Low Fire Control

The fire control system provided by INFRA-AUS shall use a medium that complies to

the following Australian standards (TBD) in order to ensure that unnecessary damage is not caused to SDP equipment in the case of



SDP_REQ_INT-102 Warning- SDP Compute SKA1 Low Fire Control

The fire control system provided by INFRA-AUS shall provide visual and audible

warnings prior to the activation of the fire suppression system to allow evacuation of

personnel from the environment.


SDP_REQ_INT-103 Space allocation- SDP Compute SKA1 Survey Mechanical

INFRA-AUS shall provide sufficient floor space for the installation of 75 racks TBC.



Survey Mechanical




SDP_REQ_INT-105 Overall power consumption- SDP Compute SKA1 Survey

Electrical

The SDP equipment will be limited to an overall power limit of 2.0 MW TBC.


SDP_REQ_INT-106 Medium- SDP Compute

SKA1 Survey Fire Control


the following Australian standards (TBD) in





order to ensure that unnecessary damage is not caused to SDP equipment in the case of


SDP_REQ_INT-107 Warning- SDP Compute






SDP_REQ_INT-108 Rack size- SDP Archive SKA1

Common Mechanical

The racks referred to hereafter shall be of size 1200mm D x 600mm W x 2100mm H.


SDP_REQ_INT-109 Rack standard- SDP Archive


The racks of archive equipment provided by the SDP for installation in the allocated

space provided by INFRA shall meet the IEC 60297-3-100 standard TBC in terms of

mechanical interfaces and size.


SDP_REQ_INT-110 Service area- SDP Archive SKA1 Common Mechanical

Additional aisle space in front of racks of 1200mm will be provided by INFRA for each rack of SDP archive equipment to allow for

doors, cabling and operator access.


SDP_REQ_INT-111 Floor loading- SDP Archive SKA1

Common Mechanical

Equipment provided by the SDP for installation in the allocated space provided

by INFRA shall have a maximum floor loading of 2000 kg per square metre TBC.


SDP_REQ_INT-112 Environment- SDP Archive SKA1 Common Thermal

INFRA shall ensure that the ambient environment of the SDP equipment is no

more than 25 degrees Celsius TBC.


SDP_REQ_INT-113 Humidity- SDP Archive

SKA1 Common Thermal

INFRA shall ensure that the ambient environment of the SDP equipment is in the range 20% to 80% humidity non-concensing.


SDP_REQ_INT-114 Data centre power efficiency-

SDP Archive SKA1 Common Electrical

The data centre housing SDP equipment shall have a PUE no greater than 1.25.


SDP_REQ_INT-115 Per rack power consumption-

SDP Archive SKA1 Common Electrical

The SDP equipment will be limited to a maximum of 20 kW per rack.


SDP_REQ_INT-116 Nominal voltage- SDP

Archive SKA1 Common Electrical

INFRA shall provide a power supply with a nominal voltage of 230V AC.


SDP_REQ_INT-117 Level variation- SDP Archive

SKA1 Common Electrical


steady state level.





SDP_REQ_INT-118 Nominal level- SDP Archive SKA1 Common Electrical


steady state level.


SDP_REQ_INT-119 Harmonic distortion- SDP Archive SKA1 Common

Electrical

INFRA shall provide a power supply with total harmonic distortion less than TBD %.


SDP_REQ_INT-120 Frequency variation- SDP Archive SKA1 Common

Electrical

INFRA shall provide a power supply with power supply frequency of 50Hz +/I TBD %.


SDP_REQ_INT-121 Controlled shutdown under UPS- SDP Archive SKA1

Common Electrical

INFRA shall provide uninterruptable power at a TBD level for a duration of TBD to the SDP in the event of a major power supply

failure.


SDP_REQ_INT-122 Redundancy- SDP Archive SKA1 Common Electrical

Each rack shall be supplied by two independent power feeds.


SDP_REQ_INT-123 Logging- SDP Archive

SKA1 Common Access Control

The access control system provided by INFRA shall ensure that all access attempts

to the SDP equipment are logged.


SDP_REQ_INT-124 Configuration- SDP Archive

SKA1 Common Access Control

The access control system provided by INFRA shall have the ability to provide temporary access for contractors and maintainers as authorised by the SDP.


SDP_REQ_INT-125 Ease of Use- SDP Archive SKA1 Common Access Control

The access control system provided by INFRA shall not impact on staff activities

once inside the secure area.


SDP_REQ_INT-126 Authentication- SDP

Archive SKA1 Common Access Control

The access control system provided by INFRA shall use authentication media that is

revocable and replaceable.


SDP_REQ_INT-127 Space allocation- SDP Archive SKA1 Mid Mechanical

INFRA-SA shall provide sufficient floor space for the installation of TBD archive

racks.

SDP_REQ_INT-128 Cable trays- SDP Archive SKA1

Mid Mechanical

INFRA-SA shall supply and install cable trays sufficient to cover the following requirements [width, mass loading,



SDP_REQ_INT-129 Total heat load- SDP Archive

SKA1 Mid Thermal

The SDP shall ensure that the SDP archive equipment inserts no more than TBD kW of

total load into the INFRA environment.






Archive SKA1 Mid Electrical

The SDP archive equipment will be limited to an overall power limit of TBD kW.


SDP_REQ_INT-131 Medium- SDP Archive SKA1 Mid Fire Control

The fire control system provided by INFRA-SA shall use a medium that complies to the following South African standards (TBD) in

order to ensure that unnecessary damage is not caused to SDP archive equipment in the

case of a fire suppression event.


SDP_REQ_INT-132 Warning- SDP Archive SKA1 Mid Fire Control

The fire control system provided by INFRA-SA shall provide visual and audible warnings prior to the activation of the fire suppression

system to allow evacuation of personnel from the environment.


SDP_REQ_INT-133 Space allocation- SDP Archive SKA1 Low Mechanical

INFRA-AUS shall provide sufficient floor space for the installation of TBD archive

racks.



Low Mechanical




SDP_REQ_INT-135 Total heat load- SDP Archive

SKA1 Low Thermal




Archive SKA1 Low Electrical

The SDP equipment will be limited to an overall power limit of TBD kW.


SDP_REQ_INT-137 Medium- SDP Archive SKA1 Low Fire Control





SDP_REQ_INT-138 Warning- SDP Archive SKA1 Low Fire Control





SDP_REQ_INT-139 Space allocation- SDP Archive

SKA1 Survey Mechanical

INFRA-AUS shall provide sufficient floor space for the installation of TBD archive

racks.



Survey Mechanical







SDP_REQ_INT-141 Total heat load- SDP Archive SKA1 Survey Thermal





Archive SKA1 Survey Electrical

The SDP archive equipment will be limited to an overall power limit of TBD kW.


SDP_REQ_INT-143 Medium- SDP Archive





SDP_REQ_INT-144 Warning- SDP Archive






SDP_REQ_INT-145 Visibility Wire data rate-SDP SKA1 Low Data

Exchange

59.15bit/s (64 bits/visibility) [RD8] (TBC)

SDP_REQ_INT-146 Visibility Data Link and

Framing-SDP SKA1 Low Data Exchange

Ethernet supporting Jumbo frames

SDP_REQ_INT-147 Visibility SADT-SDP end

point -SDP SKA1 Low Data Exchange

Demarcation at SDP switch

SDP_REQ_INT-148 Visibility Individual link

capacity-SDP SKA1 Low Data Exchange

100Gbit/s

SDP_REQ_INT-149 Visibility Data traffic profile-

SDP SKA1 Low Data Exchange

Continuous unidirectional data flow from CSP to SDP

SDP_REQ_INT-150 Visibility Flow control -SDP SKA1 Low Data Exchange

No flow control to be provided by SADT.

SDP_REQ_INT-151 Visibility Data buffering-SDP SKA1 Low Data

Exchange

None required




SDP_REQ_INT-152 Visibility Transport latency-


No special requirements

SDP_REQ_INT-153 Visibility Packet loss-SDP SKA1 Low Data Exchange

Minimal better than 10-6 suggested

SDP_REQ_INT-154 Visibility Packet out of

order-SDP SKA1 Low Data Exchange

None

SDP_REQ_INT-155 Visibility Protocol support-


Ethernet/IP/UDP/ Application Header /science data

SDP_REQ_INT-156 Visibility Pluggable

Modules-SDP SKA1 Low Data Exchange

The pluggable modules shall meet 4x25G electrical I/O CAUI-4 IEEE P802.3bm

SDP_REQ_INT-157 Visibility Type of connection between SADT and SDP-SDP SKA1 Low Electro-

optical

100 Gigabit Ethernet pluggable modules see document �CSP-SDP Data Transmission,

Concept Design, Equipment and Architecture� [RD6]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible

for the Ethernet switching required to deliver the flows to the SDP receiving equipment.

SDP_REQ_INT-158 Visibility Number of

connections-SDP SKA1 Low Electro-optical

Number of 100GE connections 592 TBC

SDP_REQ_INT-159 Visibility Power for

pluggable module-SDP SKA1 Low Electrical

DC power for the pluggable units taken from the Ethernet switch.CAUI-4 IEEE P802.3bm

Power Watts (TBD)

SDP_REQ_INT-160 Visibility Power Source-

SDP SKA1 Low Electrical

Mains or 48v DC power for the transponder units. TBD

SDP_REQ_INT-161 Visibility Optical modules-

SDP SKA1 Low Mechanical

Receptor housings on the SDP equipment shall fit with pluggable modulesCFP4..

SDP_REQ_INT-162 Visibility Cabling -SDP SKA1 Low Mechanical

Physical space shall be available for the cables or fibres required for client and line

side connections.




SDP_REQ_INT-163 Visibility Rack space-SDP

SKA1 Low Mechanical

Standard 19 inch rack space conforming to IEC 60297 or ETS 300119 will be required

from SDP for SADT transponder equipment. The amount of rack space per SADT

transponder unit is 10 U TBC.


transponder units-SDP SKA1 Low Mechanical

Expected number of rack SADT transponder units TBC.

SDP_REQ_INT-165 Visibility Transponder

management-SDP SKA1 Low Monitor and Control

The SADT transponders shall have a Network Management System capable of

controlling and monitoring the line and client side interfaces.

SDP_REQ_INT-166 Visibility Traffic

management user interface-SDP SKA1 Low Monitor

and Control

All traffic management functionality provided by SADT equipment shall have an end user controllable terminal interface provided by SADT e.g. Network manager/craft terminal

PC

SDP_REQ_INT-167 Visibility Physical layer

monitoring across interface-SDP SKA1 Low Monitor

and Control

SADT shall provide method to monitor OSI layer 1 statistics inside its interface boundary

and collect statistics from end element packetisers and transceiver modules (DOM)

via TM and the SADT network manager

SDP_REQ_INT-168 Visibility Built in self-test

data integrity and performance margin-SDP SKA1 Low Monitor and

Control

In non-observation mode the SADT equipment shall self-generate and receive

PRBS data streams, or interface to external test equipment, for the purpose of performance margin testing and

maintenance of SADT links

SDP_REQ_INT-169 Visibility Interoperability

between elements following upgrade-SDP SKA1 Low

Operational

Interoperability between end element equipment and internal interfaces shall be maintained during system build upgrades

using strict version control


between elements following upgrade-SDP SKA1 Low

Operational



SDP_REQ_INT-171 Visibility System integration plan compliance-SDP SKA1

Low Operational

SADT equipment shall operate according to a system-wide (multi-element) integration

test plan owned by the SKAO � TBD

SDP_REQ_INT-172 Visibility Precursor

constraints-SDP SKA1 Low Operational

SADT equipment interfaces and constraints due to the precursor telescopes on site shall be provided system-wide by the SKAO and

AIV consortium - TBD




SDP_REQ_INT-173 Visibility Wire data rate-SDP SKA1 Survey Data

Exchange

37.07 Tbps (64 bits/visibility) [RD8] (TBC)


Framing-SDP SKA1 Survey Data Exchange


SDP_REQ_INT-175 Visibility SADT-SDP end point -SDP SKA1 Survey

Data Exchange



capacity-SDP SKA1 Survey Data Exchange

100Gbit/s


SDP SKA1 Survey Data Exchange


SDP_REQ_INT-178 Visibility Flow control -SDP

SKA1 Survey Data Exchange


SDP_REQ_INT-179 Visibility Data buffering-SDP SKA1 Survey Data

Exchange

None required


SDP SKA1 Survey Data Exchange


SDP_REQ_INT-181 Visibility Packet loss-SDP

SKA1 Survey Data Exchange



order-SDP SKA1 Survey Data Exchange

None

SDP_REQ_INT-183 Visibility Protocol support-SDP SKA1 Survey Data

Exchange







Modules-SDP SKA1 Survey Electro-optical

SDP_REQ_INT-185 Visibility Type of connection between SADT and SDP-

SDP SKA1 Survey Electro-optical

100 Gigabit Ethernet using CFP4 modules see document CSP-SDP Data

Transmission, Concept Design, Equipment and Architecture [RD06]. Note: The packet

flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible for the Ethernet switching required to deliver the flows to the SDP receiving equipment.


connections-SDP SKA1 Survey Electro-optical

Number of 100GE connections 371


pluggable module-SDP SKA1 Survey Electrical


Power Watts (TBD)


SDP SKA1 Survey Electrical



SDP SKA1 Survey Mechanical

Receptor housings on the SDP equipment shall fit with pluggable modulesCFP4.

SDP_REQ_INT-190 Visibility Cabling -SDP

SKA1 Survey Mechanical


side connections.

SDP_REQ_INT-191 Visibility Rack space-SDP SKA1 Survey Mechanical





transponder units-SDP SKA1 Survey Mechanical

Expected number of rack SADT transponder units ~ TBC.


management-SDP SKA1 Survey Monitor and Control




management user interface-SDP SKA1 Survey Monitor

and Control


PC





monitoring across interface-SDP SKA1 Survey Monitor

and Control





data integrity and performance margin-SDP SKA1 Survey Monitor and

Control





between elements following upgrade-SDP SKA1 Survey

Operational




between elements following upgrade-SDP SKA1 Survey

Operational




Survey Operational


test plan owned by the SKAO � TBD


constraints-SDP SKA1 Survey Operational



SDP_REQ_INT-201 Visibility Wire data rate-

SDP SKA1 Mid Data Exchange

27.21 Tbps (64 bits/visibility) [RD8] (TBC)


Framing-SDP SKA1 Mid Data Exchange


SDP_REQ_INT-203 Visibility SADT-SDP end

point -SDP SKA1 Mid Data Exchange



capacity-SDP SKA1 Mid Data Exchange

100Gbit/s







SDP_REQ_INT-206 Visibility Flow control -SDP SKA1 Mid Data Exchange


SDP_REQ_INT-207 Visibility Data buffering-


None required




SDP_REQ_INT-209 Visibility Packet loss-SDP SKA1 Mid Data Exchange



order-SDP SKA1 Mid Data Exchange

None

SDP_REQ_INT-211 Visibility Protocol support-




Modules-SDP SKA1 Mid Data Exchange


SDP_REQ_INT-213 Visibility Type of connection between SADT and SDP-SDP SKA1 Mid Electro-

optical

100 Gigabit Ethernet pluggable modules see document �CSP-SDP Data Transmission,

Concept Design, Equipment and Architecture� [RD6]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible



connections-SDP SKA1 Mid Electro-optical

Number of 100GE connections 273


pluggable module-SDP SKA1 Mid Electrical


Power Watts (TBD)





SDP SKA1 Mid Electrical



SDP SKA1 Mid Mechanical

Receptor housings on the SDP equipment shall fit with pluggable modulesCFP4..

SDP_REQ_INT-218 Visibility Cabling -SDP SKA1 Mid Mechanical


side connections.

SDP_REQ_INT-219 Visibility Rack space-SDP

SKA1 Mid Mechanical





transponder units-SDP SKA1 Mid Mechanical

Expected number of rack SADT transponder units TBC.


management-SDP SKA1 Mid Monitor and Control




management user interface-SDP SKA1 Mid Monitor and

Control


PC


monitoring across interface-SDP SKA1 Mid Monitor and

Control





data integrity and performance margin-SDP

SKA1 Mid Monitor and Control





between elements following upgrade-SDP SKA1 Mid

Operational








Operational




Mid Operational


test plan owned by the SKAO -TBD


constraints-SDP SKA1 Mid Operational



SDP_REQ_INT-229 Pulsar Search Wire data rate-SDP SKA1 Mid Data Exchange

0.222 Tbit/s TBC [RD10]

SDP_REQ_INT-230 Pulsar Search Data Link and



SDP_REQ_INT-231 Pulsar Search SADT-SDP end



SDP_REQ_INT-232 Pulsar Search Individual link


10 Gbit/s

SDP_REQ_INT-233 Pulsar Search Data traffic profile-


Continuous unidirectional data flow from CSP to SDP. Note the TCP transport uses bidirectional traffic but any feedback for the

Pulsar computation goes via TM.

SDP_REQ_INT-234 Pulsar Search Flow control -SDP SKA1 Mid Data Exchange


SDP_REQ_INT-235 Pulsar Search Data buffering-SDP SKA1 Mid Data Exchange

None required

SDP_REQ_INT-236 Pulsar Search Transport latency-



SDP_REQ_INT-237 Pulsar Search Packet loss-SDP

SKA1 Mid Data Exchange





SDP_REQ_INT-238 Pulsar Search Packet out of order-


None

SDP_REQ_INT-239 Pulsar Search Protocol support-


Ethernet/IP/TCP/ Application Header /science data

SDP_REQ_INT-240 Pulsar Search Pluggable Modules-

SDP SKA1 Mid Electro-optical


SDP_REQ_INT-241 Pulsar Search Type of connection between SADT and SDP-SDP SKA1 Mid Electro-

optical

10 Gigabit Ethernet pluggable modules see document CSP-SDP Data Transmission,

Concept Design, Equipment and Architecture [RD06]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible


SDP_REQ_INT-242 Pulsar Search Number of


Number of 10 GE connections 23

SDP_REQ_INT-243 Pulsar Search Power for pluggable

module-SDP SKA1 Mid Electrical


Power Watts (TBD)

SDP_REQ_INT-244 Pulsar Search Power Source-SDP

SKA1 Mid Electrical


SDP_REQ_INT-245 Pulsar Search Optical modules-



SDP_REQ_INT-246 Pulsar Search Cabling -SDP SKA1

Mid Mechanical


side connections.

SDP_REQ_INT-247 Pulsar Search Rack space-SDP

SKA1 Mid Mechanical




SDP_REQ_INT-248 Pulsar Search Number of


Expected number of rack SADT transponder units 1 shared with PST. TBC.




SDP_REQ_INT-249 Pulsar Search Transponder




SDP_REQ_INT-250 Pulsar Search Traffic management user interface-SDP SKA1 Mid Monitor and Control


PC

SDP_REQ_INT-251 Pulsar Search Physical layer


Control




SDP_REQ_INT-252 Pulsar Search Built in self-test data integrity and performance

margin-SDP SKA1 Mid Monitor and Control




SDP_REQ_INT-253 Pulsar Search Interoperability


Operational



SDP_REQ_INT-254 Pulsar Search Interoperability


Operational



SDP_REQ_INT-255 Pulsar Search System integration

plan compliance-SDP SKA1 Mid Operational


test plan owned by the SKAO -TBD

SDP_REQ_INT-256 Pulsar Search Precursor




SDP_REQ_INT-257 Pulsar Timing Wire data rate-SDP SKA1 Mid Data Exchange

0.002 Tbit/s TBC

SDP_REQ_INT-258 Pulsar Timing Data Link and



SDP_REQ_INT-259 Pulsar Timing SADT-SDP end






SDP_REQ_INT-260 Pulsar Timing Individual link


10 Gbit/s

SDP_REQ_INT-261 Pulsar Timing Data traffic profile-


Continuous unidirectional data flow from CSP to SDP. Note the TCP transport uses bidirectional traffic but any feedback for the

Pulsar computation goes via TM

SDP_REQ_INT-262 Pulsar Timing Flow control -SDP SKA1 Mid Data Exchange


SDP_REQ_INT-263 Pulsar Timing Data buffering-SDP SKA1 Mid Data Exchange

None required

SDP_REQ_INT-264 Pulsar Timing Transport latency-



SDP_REQ_INT-265 Pulsar Timing Packet loss-SDP

SKA1 Mid Data Exchange


SDP_REQ_INT-266 Pulsar Timing Packet out of order-


None

SDP_REQ_INT-267 Pulsar Timing Protocol support-


Ethernet/IP/TCP/ Application Header /science data

SDP_REQ_INT-268 Pulsar Timing Pluggable Modules-SDP SKA1 Mid Electrical


SDP_REQ_INT-269 Pulsar Timing Type of connection between SADT and SDP-SDP SKA1 Mid Electro-

optical

10 Gigabit Ethernet pluggable modules see document CSP-SDP Data Transmission,

Concept Design, Equipment and Architecture [RD06]. Note: The packet flow is presented as a 100Gigabit stream out of the pluggable module. SDP is responsible


SDP_REQ_INT-270 Pulsar Timing Number of


Number of 10 GE connections 1




SDP_REQ_INT-271 Pulsar Timing Power for pluggable

module-SDP SKA1 Mid Electrical


Power Watts (TBD)

SDP_REQ_INT-272 Pulsar Timing Power Source-SDP

SKA1 Mid Electrical


SDP_REQ_INT-273 Pulsar Timing Optical modules-



SDP_REQ_INT-274 Pulsar Timing Cabling -SDP SKA1

Mid Mechanical


side connections.

SDP_REQ_INT-275 Pulsar Timing Rack space-SDP SKA1 Mid Mechanical




SDP_REQ_INT-276 Pulsar Timing Number of


Expected number of rack SADT transponder units 1 shared with PSS TBC.

SDP_REQ_INT-277 Pulsar Timing Transponder



controlling and monitoring the line and client side interfaces

SDP_REQ_INT-278 Pulsar Timing Traffic management user interface-SDP SKA1 Mid Monitor and Control


PC

SDP_REQ_INT-279 Pulsar Timing Physical layer


Control




SDP_REQ_INT-280 Pulsar Timing Built in self-test data integrity and performance

margin-SDP SKA1 Mid Monitor and Control


PRBS data streams, or interface to external test equipment, for the purpose of

SDP_REQ_INT-281 Pulsar Timing Interoperability


Operational






SDP_REQ_INT-282 Pulsar Timing Interoperability


Operational



SDP_REQ_INT-283 Pulsar Timing System integration

plan compliance-SDP SKA1 Mid Operational


test plan owned by the SKAO - TBD.

SDP_REQ_INT-284 Pulsar Timing Precursor




PDR04InterfaceRequirements(4)EchoSign Document History February 09, 2015

Created: February 09, 2015

By: Verity Allan ([email protected])

Status: SIGNED

Transaction ID: XJEHDWA5R48XN63

“PDR04InterfaceRequirements (4)” HistoryDocument created by Verity Allan ([email protected])February 09, 2015 - 3:17 PM GMT - IP address: 131.111.185.15

Document emailed to Ferdl Graser ([email protected]) for signatureFebruary 09, 2015 - 3:18 PM GMT

Document viewed by Ferdl Graser ([email protected])February 09, 2015 - 3:20 PM GMT - IP address: 105.184.40.35

Document e-signed by Ferdl Graser ([email protected])Signature Date: February 09, 2015 - 3:21 PM GMT - Time Source: server - IP address: 105.184.40.35

Document emailed to Paul Alexander ([email protected]) for signatureFebruary 09, 2015 - 3:21 PM GMT

Document viewed by Paul Alexander ([email protected])February 09, 2015 - 6:46 PM GMT - IP address: 131.111.185.15

Document e-signed by Paul Alexander ([email protected])Signature Date: February 09, 2015 - 6:47 PM GMT - Time Source: server - IP address: 131.111.185.15

Signed document emailed to Ferdl Graser ([email protected]), Paul Alexander ([email protected]) andVerity Allan ([email protected])February 09, 2015 - 6:47 PM GMT