There are unsaved changes.

Space Assigned Number Authority(SANA) Registry

CCSDS Terms

XML version of this registry
Created
2012-01-13
Last Updated
2017-05-19
Registration Policy
TBD
Registration Form
A new registration can be requested by completing this form.
Review authority
SEA
Signature
md5
I have reviewed all my changes.
Terms References
abstract syntax
Representation that identifies all the components of a data unit and describes their conceptual structure.
[610.0‑G‑5]
abstract syntax
The specification of Application Layer data or application-protocol-control-information by using notation rules which are independent of the encoding techniques used to represent them.
[910.2‑G‑1]
abstract-association
The relationship that exists between two abstract-ports that are bound to each other.
[910.2‑G‑1]
abstract-bind-operation
A task whose successful performance binds one or more pairs of abstract-ports.
[910.2‑G‑1]
abstract-error
A predefined condition that, upon occurrence during an attempted invocation of an abstract-operation, causes that abstract-operation to fail.
[910.2‑G‑1]
abstract-model
The macroscopic level of ASDC, composed of abstract-objects, abstract-ports, and abstract-services.
[910.2‑G‑1]
abstract-object
A functional entity (e.g., a system) that interacts with one or more other abstract-objects to provide abstract-services to, and/or use the abstract-services of, those abstract-objects.
[910.2‑G‑1]
abstract-operation
A task whose performance provides all or part of an abstract-service. An abstract-operation is invoked by an abstract-object and performed by another abstract-object via the abstract-association that exists between them.
[910.2‑G‑1]
abstract-port
A point at which an abstract-object interacts with another abstract-object, via an abstract-port of the same type on the other abstract-object.
[910.2‑G‑1]
abstract-port-type
The common identifier for a collection of abstract-ports that perform the same set of abstract-operations. There are two varieties of abstract-port-types, symmetric and asymmetric.
[910.2‑G‑1]
abstract-refinement
The process of modeling a system as one or a few high-level abstract-objects and successively decomposing each of those abstract-objects into lower-level component-abstract-objects.
[910.2‑G‑1]
abstract-service
A set of capabilities that one abstract-object offers to another by means of one or more of its abstract-ports.
[910.2‑G‑1]
abstract-service-provider
An abstract-object that offers an abstract-service to another abstract-object.
[910.2‑G‑1]
abstract-service-user
An abstract-object that uses an abstract-service of another abstract-object.
[910.2‑G‑1]
abstract-unbind-operation
A task whose performance unbinds two abstract-objects.
[910.2‑G‑1]
AC coefficient
Any wavelet coefficient from any subband except LL3.
[122.0‑B‑1]
accept
Within the Transfer layer, recognition by the receiving end that a TC Frame has passed the validation and acceptance test criteria as programmed into the Frame Acceptance and Reporting Mechanism.
[200.0‑G‑6]
acceptor
In a particular instance of OSI-service-procedure, an OSI-service-user that receives a deliver primitive and as a result may issue one or more submit primitives.
[910.2‑G‑1]
access
The OAIS entity that contains the services and functions which make the archival information holdings and related services visible to Consumers.
[651.0‑M‑1]
access aid
A software program or document that allows Consumers to locate, analyze, order or retrieve Archival Information Packages of interest.
[650.0‑M‑2]
access collection
A collection of AIPs that is defined by a Collection Description but for which there is no Packaging Information for the collection in Archival Storage.
[650.0‑M‑2]
access control
The process of granting access to information technology (IT) system resources only to authorized users, programs, processes, or other systems.
[350.4‑G‑1]
access control
The process of granting access to the resources of a system only to authorized users, programs, processes, or other systems.
[350.1‑G‑1]
[350.7‑G‑1]
access control mechanism
Hardware or software features, operating procedures, management procedures, and various combinations of these designed to detect and prevent unauthorized access and to permit authorized access in an automated system.
[350.1‑G‑1]
access functional entity
The OAIS functional entity that contains the services and functions which make the archival information holdings and related services visible to Consumers.
[650.0‑M‑2]
access policy
Written statement, authorized by the repository management, that describes the approach to be taken by the repository for providing access to objects accessioned into the repository. The Access Policy may distinguish between different types of access rights, for example between system administrators, Designated Communities, and general users.
[652.0‑M‑1]
access rights information
The information that identifies the access restrictions pertaining to the Content Information, including the legal framework, licensing terms, and access control. It contains the access and distribution conditions stated within the Submission Agreement, related to both preservation (by the OAIS) and final usage (by the Consumer). It also includes the specifications for the application of rights enforcement measures.
[650.0‑M‑2]
access software
A type of software that presents part of or all of the information content of an Information Object in forms understandable to humans or systems.
[650.0‑M‑2]
accuracy
Closeness of the agreement between the result of a measurement and a true value of the measurand. Accuracy is generally characterized by the overall uncertainty of a measured value. (See also ‘uncertainty’.)
[301.0‑B‑4]
accuracy
Closeness of the agreement between the times reported by a local time source and the master onboard time source of the spacecraft.
[872.0‑M‑1]
acknowledged (Space Packet)
Reported to have been received in its entirety. A Space Packet is said to be acknowledged when evaluation of the CLCWs returned by the space element shows that all TC frames containing parts of the Space Packet reported have been acknowledged by the space element.
[912.3‑B‑2]
acquisition sequence
A specific high transition density bit pattern transmitted to permit the receiving end to acquire symbol synchronization.
[231.0‑B‑2]
acquisition sequence
A specific high transition density bit pattern, to enable the receiver to acquire bit synchronization.
[230.0‑G‑1]
action
An atomic (non-interruptible) control directive of mission operations (equivalent to a telecommand or ground-segment directive) that can be initiated by manual or automatic control sources, via the M&C service. An action may have arguments and its evolving status can be observed. An action can typically apply pre- and post-execution checks.
[520.0‑G‑3]
active tag
A type of RFID tag that contains an internal power source, and in some cases also a radio transceiver. These additional component(s) are used to enhance the effective read/write range and rate of data transfer characteristics of the RFID tag. This type of integrated tag circuit is usually of a complex design with many components. Active tags can transmit over the greatest distances (100+ feet).
[880.0‑G‑1]
activity
An automated mission operations function; typically an operations procedure, batch task or other software process. An activity can be individually scheduled or initiated. In principle, an activity is non-atomic, has duration, and can be controlled once initiated. An activity may have arguments and its evolving status can be observed. An activity may generate multiple actions, and its behaviour can be dependent on status observed at run-time.
[520.0‑G‑3]
ad hoc
A network typically created in a spontaneous manner. An ad hoc network requires no formal infrastructure and is limited in temporal and spatial extent.
[880.0‑G‑1]
adapter
In an SOA context, a software component that implements a higher-level service in terms of a lower-level service or specific technology. In this way different adapters can map a high-level service onto different underlying technologies, transparently to all higher layers including the application. Adapters can also wrap non–service-oriented applications so that they can be used as Service Providers in Service Oriented Architecture.
[520.0‑G‑3]
adhoc order
A request that is generated by a Consumer for information the OAIS has indicated is currently available.
[650.0‑M‑2]
administration functional entity
The OAIS functional entity that contains the services and functions needed to control the operation of the other OAIS functional entities on a day-to-day basis.
[650.0‑M‑2]
AE-invocation
A specific utilization of part or all of the capabilities of a given application-entity in support of the communications requirements of an application-process-invocation.
[910.2‑G‑1]
agency center
Facility used for executing commands to spacecraft, as well as monitoring telemetry, tracking, flight dynamics, and other engineering parameters.
[500.0‑G‑2]
Aggregation Block
A named collection of Assignment Statements and/or other Aggregation Blocks.
[641.0‑B‑1]
[641.0‑G‑2]
agile reader
A reader that can read different types of RFID tags, either made by different manufacturers or operating on different frequencies.
[880.0‑G‑1]
AIP edition
An AIP whose Content Information or Preservation Description Information has been upgraded or improved with the intent not to preserve information, but to increase or improve it. An AIP edition is not considered to be the result of a Migration.
[650.0‑M‑2]
AIP version
An AIP whose Content Information or Preservation Description Information has undergone a Transformation on a source AIP and is a candidate to replace the source AIP. An AIP version is considered to be the result of a Digital Migration.
[650.0‑M‑2]
alert
An asynchronous notification, such as a non-nominal event, of significance to mission operations. Alerts may be used to notify such events to operators, initiate an automatic response, or synchronise asynchronous functions. Alerts may have arguments.
[520.0‑G‑3]
alphanumeric character set
The set of characters comprised of the digits 0 through 9 and the letters a-z or A‑Z.
[641.0‑B‑1]
[641.0‑G‑2]
ambiguity period
The interval between successive recurrences of the same time code.
[301.0‑B‑4]
ancillary information
A data type used to interpret measurements and properties.
[500.0‑G‑2]
annotation
The process of adding information to the Space Link data.
[910.3‑G‑3]
announce
To cause a message to be sent to one or more implicitly specified modules, namely, all those modules that are located within a specified continuum (or all continua), that are members of a specified unit (possibly the root unit), and that perform a specified role in the application (possibly ‘any role’).
[735.1‑B‑1]
antenna
A device for sending or receiving electromagnetic waves.
[880.0‑G‑1]
anti-collision
A feature of RFID systems that enables a batch of tags to be read in one reader field by preventing the radio waves from interfering with one another. It also prevents individual tags from being read more than once.
[880.0‑G‑1]
aperiodic
Not periodic.
[132.0‑B‑1]
[732.0‑B‑2]
apocenter
The point in an orbit at the greatest distance from the central body (i.e., at this point the geometric distance between the central body and the orbiting body is at a maximum).
[500.0‑G‑2]
application
A data system implementation, typically taking the form of a set of source code text files, that relies on AMS procedures to accomplish its purposes. Each application is identified by an application name.
[735.1‑B‑1]
application
A software entity in an SLE user system or an SLE provider system that makes use of the ISP1 protocol, as distinguished from the software implementing the protocol layers defined in this Recommended Standard. The application is considered to implement the ‘higher layers’ defined in the architectural model in section 2.
[913.1‑B‑1]
application
Component of the onboard software that makes use of the Time Access Service.
[872.0‑M‑1]
application data
The array of zero or more octets embedded in a message containing the specific information that the message conveys.
[735.1‑B‑1]
application identifier
The authority identifier of the application by which the application is identified in the BIND invocation and the BIND return.
[913.1‑B‑1]
Application Process Layer
The upper layer of the Telecommand Data Management Service.
[200.0‑G‑6]
application programmers’ interface
The definition of the exposed or ‘public’ interface to a software component that can be used by another software component. In an SOA context, an API corresponds to a language- or technology-specific implementation of an abstract service specification. This constitutes the code classes, types and functions utilised by a programmer when implementing the service provider and service consumer.
[520.0‑G‑3]
application-association, association
A cooperative relationship between two ASO-invocations which governs their bilateral use of the Presentation Service for communication of information and coordination of their joint operation.
[910.2‑G‑1]
application-entity
An application element, within an application process, embodying a set of capabilities which is pertinent to OSI and which is defined for the Application Layer, that corresponds to a specific application-entity-type (without any extra capabilities being used).
[910.2‑G‑1]
application-process
An element within a real open system which performs the information processing for a particular application.
[910.2‑G‑1]
application-process-invocation
A specific utilization of part or all of the capabilities of a given application process in support of a specific occasion of information processing.
[910.2‑G‑1]
application-service-element
A set of application-functions that provides a capability for the interworking of application entity-invocations for a specific purpose; application-service-elements are a component of application-service-objects.
[910.2‑G‑1]
application-service-object
An active element within (or equivalent to the whole of) the application entity embodying a set of capabilities defined for the Application Layer that corresponds to a specific ASO-type (without any extra capabilities being used).
[910.2‑G‑1]
Archival Information Collection
An Archival Information Package whose Content Information is an aggregation of other Archival Information Packages.
[650.0‑M‑2]
Archival Information Package
An Information Package, consisting of the Content Information and the associated Preservation Description Information (PDI), which is preserved within an OAIS.
[650.0‑M‑2]
[651.0‑M‑1]
[661.0‑B‑1]
Archival Information Unit
An Archival Information Package where the archive chooses not to break down the Content Information into other Archival Information Packages. An AIU can consist of multiple digital objects (e.g., multiple files).
[650.0‑M‑2]
archival storage functional entity
The OAIS functional entity that contains the services and functions used for the storage and retrieval of Archival Information Packages.
[650.0‑M‑2]
archive
A place in which data are preserved. Typically, an archive will provide services for storing and cataloging collected data, and for retrieving selected data upon request. Data delivered to and received from space-related data archives should be in the form of SFDUs, although the data may be stored internally in some other form.
[610.0‑G‑5]
archive
An organization that intends to preserve information for access and use by a Designated Community.
[650.0‑M‑2]
[651.0‑M‑1]
[651.1‑B‑1]
argument
A run-time parameter provided to various control items on invocation, e.g., telecommand arguments. Arguments apply to actions, activities and alerts among other items.
[520.0‑G‑3]
argument
A value that is part of a telecommand packet. This value is in general set by a human actor, usually a spacecraft controller. Arguments are only used in the context of commanding, never for telemetry purposes.
[660.0‑G‑1]
array type
A composite type whose components are all of the same type. Components are selected by indexing.
[644.0‑B‑3]
[645.0‑G‑1]
ASCII
A coded set of alphanumeric and control characters used for information interchange.
[301.0‑B‑4]
ASO-association
A cooperative relationship among two or more ASO-invocations for the purpose of communication of information and the coordination of their joint operation.
[910.2‑G‑1]
ASO-invocation
A specific utilization of part or all of the capabilities of a given ASO (without extra capabilities being used).
[910.2‑G‑1]
ASO-type
A description of a class of ASOs in terms of a set of capabilities defined for the Application Layer.
[910.2‑G‑1]
associated description
The information describing the content of an Information Package from the point of view of a particular Access Aid.
[650.0‑M‑2]
association
A cooperative relationship between an SLE service-providing application entity and an SLE service-using application entity. An association is formed by the exchange of SLE protocol data units through the use of an underlying communications service.
[911.1‑B‑3]
[911.2‑B‑2]
[911.5‑B‑2]
[912.1‑B‑3]
[912.3‑B‑2]
association control service element
An ASE that provides the exclusive means for establishing and terminating all application-associations.
[910.2‑G‑1]
asymmetric
A variety of abstract-port-type that indicates that the two abstract-ports of the port pair invoke and perform different and complementary sets of abstract-operations. One asymmetric abstract-port is designated the consumer, and the other, the supplier. The consumer performs the set of operations invoked by the supplier, and the supplier performs the operations invoked by the consumer.
[910.2‑G‑1]
asymmetric ports
Two ports (of two objects) involved in the provision of a service offering all of the operations associated with the service
[910.4‑B‑2]
asymmetrical service
An OSI-service for which the definitions of all OSI-local views are not all the same (i.e. there are several types of OSI-local view).
[910.2‑G‑1]
asynchronous
Not synchronous (see synchronous).
[132.0‑B‑1]
[133.0‑B‑1]
[133.1‑B‑2]
[231.0‑B‑2]
[232.0‑B‑2]
[732.0‑B‑2]
asynchronous channel
A data channel where the symbol data are modulated onto the channel only for the period of the message. The message must be preceded by an acquisition sequence to achieve symbol synchronization. Bit synchronization must be reacquired on every message. A hailing channel is an example of an asynchronous channel.
[210.0‑G‑1]
[211.0‑B‑4]
[211.1‑B‑3]
[211.2‑B‑1]
asynchronous data link
A data link consisting of a sequence of variable-length Proximity Link Transmission Units (PLTUs), which are not necessarily concatenated. Two types of asynchronous data links are 1) Asynchronous Data Link over an Asynchronous Channel: Hailing provides an example of an asynchronous data link over an asynchronous channel. An important issue is resynchronization between successive hails. Idle is provided for the reacquisition process. 2) Asynchronous Data Link over a Synchronous Channel: Data service provides an example of an asynchronous data link over a synchronous channel. Once the link is established via hailing, communication transitions to a synchronous channel and maintains the link in this configuration until the session is interrupted or ends. If the Physical layer does not receive data from the Data Link layer, it provides idle to maintain a synchronous channel.
[210.0‑G‑1]
[211.1‑B‑3]
[211.2‑B‑1]
atomic time scale
A time scale based on atomic or molecular resonance phenomena. Elapsed time is measured by counting cycles of a frequency locked to an atomic or molecular transition.
[301.0‑B‑4]
attenuation
The reduction in amplitude or strength of a signal as a function of distance.
[880.0‑G‑1]
attitude
Orientation of the body reference frame with respect to a defined reference frame.
[500.0‑G‑2]
attitude equipment
Equipment onboard a spacecraft that is used to take measurements of the spacecraft attitude.
[500.0‑G‑2]
attribute
A piece of information that describes a Data Entity or Dictionary Entity. This information characterizes or enhances the understanding of the data that is described. Attributes are used to define the semantics of data entities.
[647.3‑B‑1]
[647.1‑B‑1]
[647.2‑B‑1]
attribute descriptor
A piece of information that describes an attribute. This document specifies a set of descriptors for attribute description.
[647.2‑B‑1]
[647.1‑B‑1]
[647.3‑B‑1]
attribute value
A value associated with an attribute instance.
[647.1‑B‑1]
[647.2‑B‑1]
[647.3‑B‑1]
audit trail
A record showing who has accessed an IT system and what operations the user has performed during a given period.
[350.4‑G‑1]
Audio
Sonic information capable of being recorded or transmitted (typically 20 Hz–20 kHz). In addition to human voice, audio may contain experiments’ noises, sounds, or music, all of which need more quality and more BandWidth (BW) than voice to be transmitted.
[766.2‑R‑0]
authenticate
To verify the identity of a user, device, or other entity in a computer system, often as a prerequisite to allowing access to resources in a system. Also, to verify the integrity of data that have been stored, transmitted, or otherwise exposed to possible unauthorized modification.
[350.4‑G‑1]
authentication
(1) Verification of the identity of a user, device, or other entity in a computer system, often as a prerequisite to allowing access to resources in a system. (2) Verification of the integrity of data that have been stored, transmitted, or otherwise exposed to possible unauthorized modification.
[350.1‑G‑1]
[350.7‑G‑1]
authentication
The process of verifying the authorization of a user, process, or device, usually as a prerequisite for granting access to resources in an IT system.
[350.4‑G‑1]
authenticity
The degree to which a person (or system) regards an object as what it is purported to be. Authenticity is judged on the basis of evidence.
[650.0‑M‑2]
authority
An administrative entity or persona that may have responsibility for the configuration and operation of an instance of an application. Each authority is identified by an authority name.
[735.1‑B‑1]
Authority and Description Identifier
In the context of EAST, an identifier of the EAST Recommendation within the CCSDS organization.
[644.0‑B‑3]
[645.0‑G‑1]
Authority and Description Identifier
The concatenation of the Control Authority Identifier (CAID) and the Data Description Identifier (DDID).
[622.0‑B‑1]
Authority and Description Identifier
The concatenation of the Control Authority Identifier (CAID) and the Data Description Identifier (DDID).
[631.0‑G‑2]
[632.0‑B‑1]
authorization
The granting of access rights to a user, program, or process.
[350.1‑G‑1]
[350.7‑G‑1]
Authorization Validation
The validation of an SM Message Set to ensure that the Sender of the message set is authorized to send messages in the context of the Service Agreement and that the Service Agreement is supported by the Receiver.
[910.11‑B‑1]
[910.14‑G‑1]
Auto-Id Center
A group of potential RFID end users, technology companies, and academia. The Auto-ID Center began at the Massachusetts Institute of Technology (MIT) and is now a global entity. It is focused on driving the commercialization of ultra-low cost RFID solutions that use Internet-like infrastructure for tracking goods throughout the global supply chain. The Auto-ID Center organization is now called EPCglobal.
[880.0‑G‑1]
automatic data capture
Method of collecting data and entering it directly into a computer system without human intervention. Automatic Identification (Auto-ID) Refers to any technologies for capturing and processing data into a computer system without using a keyboard and includes bar coding, RFID, and voice recognition.
[880.0‑G‑1]
autotrack
A system which causes Earth station’s antenna to automatically follow (track) a moving spacecraft.
[410.0‑B‑21]
AOS transfer frame
See (AOS) transfer frame.