{ "@context": { "@vocab": "https://schema.org/", "dcat": "http://www.w3.org/ns/dcat#", "dc": "http://purl.org/dc/elements/1.1/", "dct": "http://purl.org/dc/terms/", "ecrro": "http://cor.esipfed.org/ont/earthcube/", "ecrr": "https://n2t.net/ark:/23942/g2" }, "@id": "http://n2t.net/ark:/23942/g2800020", "@type": ["CreativeWork"], "name": "SeedLink Protocol specification", "subjectOf": [ { "@type": "CreativeWork", "name": "linked web page", "url": "https://www.seiscomp3.org/doc/applications/seedlink.html" } ], "description": "SeedLink is a real-time data acquisition protocol. The SeedLink protocol is based on TCP. All connections are initiated by the client. During handshaking phase the client can subscribe to specific stations and streams using simple commands in ASCII coding. When handshaking is completed, a stream of SeedLink 'packets' consisting of a 8-byte SeedLink header (containing the sequence number) followed by a 512-byte Mini-SEED record, is sent to the client. The packets of each individual station are always transferred in timely (FIFO) order. The SeedLink implementation used in SeisComP is the oldest and most widely used, however, other implementations exist. Another well-known implementation is deployed in IRIS DMC and some manufacturers have implemented SeedLink in their digitizer firmware. All implementations are generally compatible, but not all of them support the full SeedLink protocol. On the other hand IRIS DMC implements some extensions which are not supported by other servers. 'SeedLink' denotes the SeedLink implementation used in SeisComP. The data source of a SeedLink server can be anything which is supported by a SeedLink plug-in - a small program that sends data to the SeedLink server. Plug-ins are controlled by the SeedLink server, e.g., a plug-in is automatically restarted if it crashes or a timeout occurs. Data supplied by a plug-in can be a form of Mini-SEED packets or just raw integer samples with accompanying timing information. In the latter case, the SeedLink server uses an integrated 'Stream Processor' to create the desired data streams and assemble Mini-SEED packets.", "keywords": "", "license": [ { "@type": "CreativeWork", "name": "not provided" } ], "about": [ { "@type": "DefinedTerm", "name": "Seismology", "identifier": "http://cor.esipfed.org/ont/earthcube/ADO_0000099" } ], "mainEntity": [ { "@type": "CreativeWork", "url": "http://cor.esipfed.org/ont/earthcube/ECRRO_0000204", "name": "Specification" }, { "@type": "CreativeWork", "url": "http://cor.esipfed.org/ont/earthcube/SPKT_0000012", "name": "API" } ], "supportingData": [ { "@type": "DataFeed", "name": "Input Data Type specification", "position": "output", "encodingFormat": [ "miniSEED", "application/vnd.fdsn.mseed" ] } ], "additionalProperty": [ { "@type": "PropertyValue", "propertyID": "ecrro:ECRRO_0000138", "name": "has maturity state", "value": { "@type": "DefinedTerm", "name": "Used in multiple places", "identifier": "http://cor.esipfed.org/ont/earthcube/MTU_0000001" } }, { "@type": "PropertyValue", "propertyID": "ecrro:ECRRO_0000219", "name": "expected lifetime", "value": { "@type": "DefinedTerm", "name": "More than 5 years", "identifier": "http://cor.esipfed.org/ont/earthcube/ELT_0000002" } }, { "@type": "PropertyValue", "propertyID": "ecrro:ECRRO_0000017", "name": "Usage", "value": { "@type": "DefinedTerm", "name": "Wide usage (>50 adopters)", "identifier": "http://cor.esipfed.org/ont/earthcube/UBA_0000001" } }, { "@type": "PropertyValue", "propertyID": "ecrro:ECRRO_0000502", "name": "Communication protocol", "value": { "@type": "DefinedTerm", "name": "TCP/IP", "identifier": "http://cor.esipfed.org/ont/earthcube/CMPR_0000003" } }, { "@type": "PropertyValue", "propertyID": "ecrro:ECRRO_0001301", "name": "registration metadata", "value": { "@type": "StructuredValue", "additionalType": "ecrro:ECRRO_0000156", "contributor": { "@type": "Person", "name": "Stephen M. Richard", "identifier": " https://orcid.org/0000-0001-6041-5302" }, "datePublished": "2021-11-04T17:06:00Z" } } ] }