In MTS1 MTS 1 you can find specifications information regarding:
EC (primary) and RSA (fallback) algorithm for issuer and device signature of mobile ticket bundles (MTB). Issuer signature ensures that the requests comes from a trusted participant. Device signatures are used to provide a binding between the mobile ticket and the device (e.g. a mobile phone).
The structure of the mobile ticket bundle.
Schemas of security headers of the mobile ticket bundle.
In MTS2 MTS 2 you can find specifications information regarding:
How a device key, used for device signatures, can be calculated. Device keys are used to provide a binding between the mobile ticket bundle and the device (e.g. a mobile phone). To read about the keys and algorithms see MTS1
In MTS3 MTS 3 you can find specifications information regarding:
Coordinated Ticket Name Space, which defines a common set of variables and data structures to be used within the MTB. For example version handling and metadata. To read about MTBs see MTS1MTS 1.
Schemas for version handling, metadata et.c.
In MTS4 MTS 4 you can find specifications information regarding:
Coordination and key management between participants and the administrative body (Samtrafiken).
Participant metadata set, containing current keys and related metadata, is distributed by Samtrafiken to participants and all participants needs to retrieve this list regularyregular.
Mandatory fields of the JSON Web Signature (JWS) protected header.
Schema for the participant metadata set.
In MTS5 MTS 5 you can find specifications information regarding:
How to generate and validate a proof-of-possession (of private keys) token. Private keys are used to sign critical parts of requests and responses.
How to validated proof-of-possession tokens.
Specification of Primary and fallback algorithms.
Hash calculation and how to verify it.
In MTS6 MTS 6 you can find specifications information regarding:
The generic language Tickle how to write and evaluate conditions for the journey.
The language is use to define time and spatial geographical conditions including macros (complex conditions saved in the client for less data in messages).
In MTS7 MTS 7 you can find specifications information regarding:
Methods to store a MTB on a chip embedded in a smart card, a wearable or similar.
Requrements Requirements and compliance levels that has to be fulfilled to use this.
Specific commands to use.
Complete data structures that is needed.
Security issues that needs to be considered.
In MTS8 MTS 8 you can find specifications information regarding:
Date and time formats used within the mobile ticket specifications and related APIs.
ISO standards regaring regarding time duration and intervall interval formats.