Flexibly model processing steps in your dataflows with Routes | Leanspace

Table of Contents

Flexibly model processing steps in your dataflows with Routes

Flexibly model processing steps in your dataflows with Routes

In our previous article, we demonstrated how you can use Leanspace Routes to perform on-premise encryption and decryption while still enjoying the benefits of the cloud. The Routes tool solves some of the major problems that impact the ability of satellite operators to scale their operations. If you’re not familiar with the Routes tool by Leanspace, learn more about it via this introductory blog article here.

In this article, we explore how you can build a Routes yaml file which models the processing steps of your incoming and outgoing data flows. We’ll also show how you can take advantage of the built-in connectors and processors provided by Leanspace. 

Modeling a telemetry flow within a Route

In the below image, there is a visual display of the flow of telemetry, from the satellite, to the cloud based mission control, where time series data is mapped and stored.

There are two main types of steps, connectors and processors:

The connectors manage the incoming and outgoing data flows, in this case, it pulls telemetry from the gSaaS connector, which is KSAT in this case, and the outgoing flow is the Leanspace Stream connector, which takes the processed telemetry and sends it to the Leanspace Stream tool, which sits within the cloud-based mission control.

The processors are the steps in between, such as decryption, CCSDS frame splitting, that transforms the telemetry, we’ll cover those later in this article.

All of these steps have been modeled In the below code block, which contains the Route file.

- route:
  id: tm
  from:
    uri: ksat:1.1.1.1:11111
          steps:
            - log:
                message: Processing ${body}
                loggingLevel: DEBUG
            - process:
                ref: '#class:io.leanspace.routes.processors.DecryptionProcessor'
            - split:
                method: 'ccsdsFrameSplitter'
                parallelProcessing: true
            - process:
                ref: '#class:io.leanspace.routes.processors.CcsdsFrameProcessor'
            - to:
                uri: leanspace-stream:####
                parameters:
                  env: ####
                  tenant: ####
                  clientId: ####
                  clientSecret: ####

KSAT Connector (line 4) is a built-in connector provided by Leanspace. Its role is to pull incoming telemetry from KSAT, who supplies you with the host and port. Once it arrives it will be in an encrypted state.

Decryption Processor (line 10) takes the encrypted state and then performs decryption processing. Routes comes with built-in processors for both Cysec and AWS KMS, the tool also supports the creation of custom processors as well.

CCSDS Frame Splitter (line 12) and the CCSDS Frame Processor (line 15), which are built-in processors provided by Leanspace. The Frame Splitter will take the decrypted telemetry and split it. After that, the Frame Processor will perform error detection and correction techniques to ensure the integrity of the data.

Leanspace Streams Connector (line 16), contains the authentication steps required to send telemetry to Leanspace’s secure environment. This is a built-in connector that takes the decrypted and processed telemetry and sends it to Leanspace via SSL. This is a built-in connector that takes the decrypted and processed telemetry, and sends it to Leanspace via SSL, where it is stored.

Complete flexibility in how you model your data flows

While all of the example’s steps have been modeled in the above code block, which contains the Route file, you have complete flexibility in how you model your data flows with Routes; both the order and the type of steps and processing that takes place.  

For instance, you can set up error handling to capture transmission interruptions, with multiple inputs and outputs, all within the same Route file. If you’re curious to learn more about other use cases, check out our previous article on on-premise encryption and decryption with Routes.

Conclusion

As you can see above, you always stay in control over the creation and management of your data flows, with as much flexibility as you need. With Leanspace Routes you can be up and running in no time at all. 

If you are interested in learning more about how to create your own solutions for your satellite operations, including creating your own processors with specific requirements, reach out to one of our engineers.

DISCOVER MORE BLOG ARTICLES

Get Leanspace Insights

Sign up for the latest product releases and updates, delivered straight to your inbox each month.

JOIN OUR TEAM

Discover our exciting job vacancies.
We are constantly hiring.
Come and join the Leanspace adventure!

CONNECT WITH US

MEDIA

Introducing ITAR compatible Deployment Options! The freedom to deploy on your terms is here!

X