If you have difficulty in submitting comments on draft standards you can use a commenting template and email it to admin.start@bsigroup.com. The commenting template can be found here.
Standards Development
This document describes the current situation and provides insights into post-processing software (PP-SW) in space with the aim of coordinating standardization efforts. For this purpose, the current state of the art in post-processing software in space/ground, experiences, and best practices are analyzed and the general architecture of PP-SW in space/ground segment is described. Furthermore, functional blocks for PP-SW, information flow and corresponding interfaces for standardization and their hardware components are identified. Mapping HW to SW components for standardization needs. The distillation of secure keys as well as the creation of entanglement will be treated, albeit the last will be more prospective due to the current technological limitations. Finally, a critical review of the components and interfaces is carried out in order to propose a plan and priorities for the standardization of PP-SW in relation to space.
The purpose is to provide a document on the Post-Processing Software (PP-SW) implementation.
The PP-SW is part of a Quantum Key Distribution (QKD) System. From the measurement of the quantum signals, a raw key is obtained, that has to be processed to extract the final, secret key. This process is key for the good performance of the QKD system and can be very heavy in the required resources, both on the communications and computing sides. These are the reasons why is particularly critical in space applications and different configurations can lead to very different performances. Example configurations could be implementing e.g. BB84 protocol, having Alice operating in the space segment (in orbit) and Bob operating in the ground segment, or use other protocol, e.g. BBM92 protocol, has both Alice and Bob operating in ground segment at different locations.
From the point of the standardization, the space segment is critical. The BB84 protocol is a good starting point, as it primarily concerns the space segment, where different issues need to be addressed and standardized to allow international use. Once the standardisation of such a protocol is successfully completed, the standard can further be extended by the BBM92 protocol as a next phase of standardization.
Some examples of the many aspects needed to be described for standardization follow:
1) There are two different operating environment for PP-SW execution. The two computers are:
• an On-board computer (OBC), operating in the space segment
• a ground terminal computer, operating in the ground segment
2) The OBC works in a very demanding environment, and it has to address the following areas: radiation, redundancy, memory protection (scrubbing, error detection/correction), lifespan, multi-core. Space software that is executed on OBC, addresses not only PP-SW algorithms, but also space related issued, which typically represents the following:
• memory scrubbing
• communication interfaces
• orbit determination and control
The purpose of this document is to support development of the post-processing software and enable compatibility between space and ground segments, providing insights on the general architecture of the PP-SW, its functional blocks and information flow, which in turn will define the interfaces for standardization, the mapping of HW components to functional blocks and the mapping of HW to SW components for standardization. The document will end with a prioritization for PP-SW in space standardization.
An indicative Table of Contents follows:
− Current state of the art in post-processing software (PP-SW) in space, experiences, and best practices. This chapter will give the context and starting point of the Roadmap, referencing standardisation efforts for space and ground communication, technology developments for space, ongoing quantum satellite missions and ongoing and operational optical communication satellite missions.
− The general architecture of PP-SW.
This chapter will describe the general architecture of PP-SW, defining its main constituents and functionalities, placing them in the context of a global quantum communications infrastructure, where the terrestrial and space segments cooperate for end-to-end quantum communications potentially anywhere on earth. In principle, either the transport of secure keys or the creation of non-classical correlations will be considered, although the last one, because of current technological limitations is expected to be less detailed than the first one. Satellites in different kind of orbits (LEO, MEO, GEO) and constellations will be discussed. Different types of QKD systems, like prepare and measure or entanglement based will be also treated on a conceptual level.
− Identification of functional blocks for PP-SW, information flow and corresponding interfaces for standardization. For the main architectures identified in the previous chapter, a detailed description of the functional blocks will be given. This means not only a description of what it does, but also the data that is processed in these blocks. − Identification of the HW components in the functional blocks. The HW components and the general requirements of the functional blocks identified in the previous chapter will be given. The HW components shall be agnostic to the actual implementation as much as possible.
− Mapping HW to SW components for standardization needs. The blocks identified previously are potential subjects of standardization, as well as their interfaces and the associated architecture. In this chapter, they will be analysed from the point of view of standardization. This includes an analysis of components and interfaces which are already standardized for different purposes, e.g., on-board computers, memory resources, processing resources.
− Priorities for PP-SW in space standardization.
In this chapter a critical revision of the components and relations (interfaces) discussed in the previous chapter will be performed in order to suggest a plan and priorities for standardization of Post-Processing Software in relation to Space. In particular, the standardization readiness level will be considered. This is particularly relevant for those components that are in the early stages of technological development, where a premature standardization might impose unneeded rigidity. Again, this analysis shall consider existing standards which can be applied for quantum communication in space.
This project is being piloted and implemented in accordance with the new European Agile Specification (EAS) process.
Required form fields are indicated by an asterisk (*) character.
You are now following this standard. Weekly digest emails will be sent to update you on the following activities:
You can manage your follow preferences from your Account. Please check your mailbox junk folder if you don't receive the weekly email.
You have successfully unsubscribed from weekly updates for this standard.
Comment by: