Traffic and Travel Information (TTI) - TTI messages via cellular networks - Part 5: Internal services

Migrated from Progress Sheet (TC Comment) (2000-07-10): WIs 129-136 are the result of the splitting of WI 025 (TC Res C 1/2000) (CC/000607).
!!! Resolution BT 19/2002: Finalization of prENV ISO 14821-5 as CEN/TS 14821-5 by CMC under CA7 in English only and submission to the new translation procedure (NT/021014) !!!

Verkehrs- und Reiseinformationen (TTI)-TTI-Nachrichten über mobile - Teil 5: Interne Dienste

Prometne in potovalne informacije (TTI) – Sporočila TTI prek celičnih omrežij – 5. del: Notranje storitve/službe

General Information

Status
Withdrawn
Publication Date
30-Sep-2003
Withdrawal Date
19-Jan-2015
Technical Committee
Current Stage
9900 - Withdrawal (Adopted Project)
Start Date
11-Nov-2014
Due Date
04-Dec-2014
Completion Date
20-Jan-2015

Buy Standard

Technical specification
SIST-TS CEN/TS 14821-5:2003
English language
104 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

SLOVENSKI STANDARD
SIST-TS CEN/TS 14821-5:2003
01-oktober-2003

3URPHWQHLQSRWRYDOQHLQIRUPDFLMH 77, ±6SRURþLOD77,SUHNFHOLþQLKRPUHåLM±

GHO1RWUDQMHVWRULWYHVOXåEH

Traffic and Travel Information (TTI) - TTI messages via cellular networks - Part 5:

Internal services

Verkehrs- und Reiseinformationen (TTI)-TTI-Nachrichten über mobile - Teil 5: Interne

Dienste
Ta slovenski standard je istoveten z: CEN/TS 14821-5:2003
ICS:
35.240.60 Uporabniške rešitve IT v IT applications in transport
transportu in trgovini and trade
SIST-TS CEN/TS 14821-5:2003 en

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 14821-5:2003
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 14821-5:2003
TECHNICAL SPECIFICATION
CEN/TS 14821-5
SPÉCIFICATION TECHNIQUE
TECHNISCHE SPEZIFIKATION
May 2003
ICS 35.240.60
English version
Traffic and Travel Information (TTI) - TTI messages via cellular
networks - Part 5: Internal services

This Technical Specification (CEN/TS) was approved by CEN on 10 May 2001 for provisional application.

The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their

comments, particularly on the question whether the CEN/TS can be converted into a European Standard.

CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available. It

is permissible to keep conflicting national standards in force (in parallel to the CEN/TS) until the final decision about the possible

conversion of the CEN/TS into an EN is reached.

CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,

Hungary, Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands, Norway, Portugal, Slovakia, Spain, Sweden, Switzerland and United

Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36 B-1050 Brussels

© 2003 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 14821-5:2003 E

worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
Table of contents
PAGE
TABLE OF CONTENTS 2
FOREWORD 3
INTRODUCTION 4
1. SCOPE 5
2. NORMATIVE REFERENCES 6
3. DEFINITIONS AND ABBREVIATIONS 7
3.1 Definitions 7
3.2 Abbreviations 9
4. SPECIFICATION OF INTERNAL SERVICES – CONFIGURATION AND MASTER DATA UPDATE14
4.1 Goal of the Service 14
4.2 Access Management 14
4.3 Master Data Management 14
4.4 Key Management 14
4.5 Function Contents and Handling of Access Management 15
4.6 General 16
4.7 Configuration Request initiated by the Onboard Equipment 16
4.8 Configuration Update sent by the Service Center 17
4.9 Handling Sequence of Access Management 26
4.10 Requirements for the Onboard Equipment 33
4.11 Function Contents and Handling of Master Data Management 34
5. SPECIFICATION OF KEY MANAGEMENT AND SECURITY 36
5.1 Descriptions for Operators 36
5.2 Roles in Key Management 36
5.3 Encryption of User Data 43
5.4 Key Exchange Procedures 48
5.5 Cryptographic Function in the Onboard Equipment 61
6. ADP FOR CAS FUNCTIONALITY -CONFIGURATION AND KEY MANAGEMENT 65
6.1 General Definitions and Information Elements 65
6.2 Configuration Management 67
6.3 Key Management 73

6.4 ADP for CAS Functionality -Configuration and Key Management - Specification in ASN.1 82

7. SPECIFICATION OF DIAGNOSTIC SERVICES 94
7.1 Goal of the Service 94
7.2 Function Contents and Handling of Diagnosis Functions 94
7.3 Communications Flow between On-Board Equipment and TT Call Office 95
7.4 Requirements for the Onboard Equipment 96
8. ADP FOR DIAGNOSTIC SERVICES - GENERAL DEFINITIONS AND INFORMATION
ELEMENTS 97
8.1 General 97
8.2 Diagnostic Request Message 97
8.3 Diagnostic Message 99
8.4 ADP for Diagnostic Services - Specification in ASN.1 101
BIBLIOGRAPHY 104
---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
Foreword

This document (CEN/TS 14821-5:2003) has been prepared by Technical Committee CEN/TC 278

"Road transport and traffic telematics", the secretariat of which is held by NEN, in collaboration with

Technical Committee ISO/TC 204 "Transport information and control systems".

This technical specification was prepared by Working Group 7 of CEN TC278. In the field of Traffic and

Traveller Information, the innovative rate is high, with many research and development projects under

way in many countries, and there is a need to establish prospective standards which allow

manufacturers to introduce competitive products to the market in the knowledge that they can

accommodate the future issues of the standard(s) without fundamental change to equipment.

In accordance with the CEN/CENELEC “Internal Regulations Part 2: Common Rules for standards work,

04-1996“ the original copyright holders on the complete set of documents are Mannesmann Autocom

GmbH and TEGARON Telematics GmbH. The original copyright holders hereby grant CEN all

necessary rights with regard to said original copyrights to execute the standardisation process as

described below.

No known national technical specifications (identical or conflicting) exist on this subject.

CEN/TS 14821 consists of eight parts; one part describing the framework and seven parts providing

detailed specifications of all components, protocols and services that are within the scope of CEN/TS

14821.

According to the CEN/CENELEC Internal Regulations, the national standards organizations of the

following countries are bound to announce this CEN Technical Specification: Austria, Belgium, Czech

Republic, Denmark, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Luxembourg,

Malta, Netherlands, Norway, Portugal, Slovakia, Spain, Sweden, Switzerland and the United Kingdom.

---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
Introduction

Traffic and Traveller Information (TTI) may be disseminated through a number of services or means of

communication, covering static displays, portable terminals and in-vehicle equipment.

For all such services, the data to be disseminated, and the message structure involved in the various

interfaces, require clear definition and standards formats in order to allow competitive products to

operate with any received data.

This technical specification focuses on an application data specification whereby data is produced at a

central location and is disseminated via a cellular radio network. It addresses the data specifications for

both downlink and uplink existing between a central location and randomly located vehicles. It enables

messages to be exchanged between different systems and service providers adopting a variety of

applications specifications.

Other techncial specifications are being produced by the CEN TC278 Working Group 4 to cover TTI

dissemination via other means or services. This set of specifications is named GATS (Global Automotive

Telematics Standard). GATS provides the modular framework for implementing such traffic telematics

services on an open technology platform and is network - independent. In many details definitions are

necessary to ensure interoperability. Therefore, those detailed definitions are given in a network-specific

part (CEN/TS 14821-8). With the development of future mobile communication systems towards UMTS /

IMT2000 the bottleneck of narrow-band data communication might fade. Due to its modular structure,

the GATS framework and applications are prepared for that due to its network-independence. The same

holds for emerging technologies for positioning which today is almost exclusively based on GPS.

Other relevant standard developments are, independent from telematics, the application-independent

Wireless Application Protocol (WAP), enabling mobile access to the Internet. It is understood that these

emerging technologies might fit into the framework of telematics applications in future WAP-versions.

For the time being, GATS already today independently from WAP enables access to telematics services.

Utilisation of GATS on a WAP protocol stack and identifying necessary adaptation of WAP specifications

(if any) is currently under investigation of the appropriate groups within WAP-Forum and GATS-Forum.

---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
1. Scope

This CEN/TS defines the specific interfaces and functionality of traffic telematics (TT) services based on

the use of cellular networks. Device manufacturers are enabled to develop terminal equipment

compatible to services based on this technical specification. This will allow for interoperability of different

terminal equipment and service providers which allows competition between service providers and

terminal manufacturers. Furthermore it sets the scene for international availability of these services.

This technical specification specifies

• TT-specific interfaces between terminal and service centre. This especially incorporates the

message sets of the application data protocols and the service-independent communication handling

(including conditional access and transport protocols).

• Functionality, procedures and requirements of basic terminal components as well as their interaction

with the service centre. This especially comprises conditional access and security mechanisms.

• Service Specifications, which are essential to ensure consistent behaviour of terminal and service

centre.
The services incorporated within this issue comprise:
• breakdown and emergency services
• interactive traffic information services
• broadcast traffic information services
• navigation services (route assistance, route advice, homing)
• operator services
• general information services
• floating car data collection

It is envisaged that future research and development will lead to improvements on the services listed

above as well as to the creation of new services. Nevertheless this technical specification provides the

framework for seamless integration of new features and services into the existing architecture.

---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
2. Normative references

This Technical Specification incorporates by dated or undated reference, provisions from other

publications. These normative references are cited at the appropriate places in the text and the

publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of

these publications apply to this Technical Specification only when incorporated in it by amendment or

revision. For undated references the latest edition of the publication referred to applies (including

amendments).

ISO/IEC 9797-1 Information technology -- Security techniques -- Message Authentication

Codes (MACs) -- Part 1: Mechanisms using a block cipher

ISO/IEC 9797-2:2002 Information technology -- Security techniques -- Message Authentication

Codes (MACs) -- Part 2: Mechanisms using a dedicated hash-function

ISO/IEC 10116 Information technology – Security techniques - Modes of operation for an n-

bit block cipher

ISO/IEC 10118-1:2000 Information technology - Security techniques – Hash-functions – Part 1:

General

ISO/IEC 10118-2 Information technology – Security techniques – Hash-functions – Part 2:

Hash-functions using an n-bit block cipher

ISO 11568-3: Banking - Key management (retail) - Part 3: Key life cycle for symmetric

ciphers

PKCS#1: RSA Encryption Standard, RSA Labs Technical Notes, Version 1.5, Nov. 1993

CCITT, Annex A to CCITT Blue Book Rec. E212
---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3. Definitions and abbreviations
3.1 Definitions
For the purposes of this CEN/TS, the following terms and definitions apply:
3.1.1 Attribute (of a Traffic Information Message)

A Traffic Information Message is made up of separate parts that can be called attributes. This includes,

for example, an item of information and a length of validity.
3.1.2 Authorisation

Reciprocal proof that the identity provided by the communications partner is valid

3.1.3 Broadcast Service

Data service within a cellular wireless network that allows for mono-directional dissemination of data

from a service centre to multiple users in the area of signal reception
3.1.4 Bypass Description
Representation of a Bypass, consisting of a Bypass Hint and/or a Bypass Route.
3.1.5 Bypass Hint
Representation of a hint for a Bypass
3.1.6 Bypass Link
Prominent waypoints on a Bypass Route
3.1.7 Bypass Route
Representation of the route for a Bypass
3.1.8 Cell Broadcast
Broadcast service of the GSM network
3.1.9 Data telegram
Digital message exchanged between two systems
3.1.10 Delivery Notification

Network acknowledgement for successful/ unsuccessful delivery of a message to the mobile device

3.1.11 Functional Road Class

A classification based on the importance of the road element in the connectivity of the total road network

3.1.12 Functional Road Class 0
Motorways
3.1.13 Functional Road Class 1

All non-Motorways that are part of a connection used for nation wide traffic and transport

3.1.14 Geocode

Geocodes are unique identifiers unmistakably defining important points on road networks. Geocodes

can be derived from / converted into WGS84 co-ordinates by the algorithm described in CEN/TS 14821-

---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3.1.15 Hardware service agents

Partner companies of the traffic telematics service providers who are authorised to install onboard

equipment into vehicles and to maintain it
3.1.16 Homing
Simple form of guidance to destination, in which the direction and
straight-line distance of the destination are indicated
3.1.17 Information Element
Information unit of a message
3.1.18 Intersection
Junction of two or more roads
3.1.19 Length of a Speech Report
Length of a Speech Report, including pauses, in tenths of a second
3.1.20 Mobile Originated
Data telegram sent from the onboard equipment to the Service Centre.
3.1.21 Mobile Terminated
Data telegram sent by the Service Centre to the onboard equipment.
3.1.22 Onboard equipment

A system, generally mobile, interacting with the service centre to handle traffic telematics services

3.1.23 Road Junction
Intersection of two or more roads
3.1.24 Route description

Description of a route showing the geometry of street intersections, manoeuvre instructions, street and

place names, and geographical co-ordinates
3.1.25 Service centre

System produced by the traffic telematics operators / service providers to handle traffic telematics

services
3.1.26 Short Message Service
Packet-based form of data transfer within the GSM network
3.1.27 Speech connection

Communications channel between two systems for the bi-directional transmission of speech

3.1.28 Speech Report
Traffic Information Report transmitted by a speech system
3.1.29 Terminal Device

Generally mobile system interacting with the service centre for implementation of telematics services

3.1.30 TINFO
Traffic Information Report
---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3.1.31 TINFO Version

Unique identification of a Traffic Message, consisting of a number and a time stamp

3.1.32 Traffic Data
Data for qualification of Traffic Events. This includes:
• Values: speed, traffic flow, traffic density
• Places: position, place designation
• Facts: description of situation
3.1.33 Traffic Event

An occurrence on a road or in an area that is worthy of reporting, such as a traffic jam, wrong-way driver,

or fog.
3.1.34 Traffic Information

Technical representation of a Traffic Situation within the onboard equipment, accomplished by a number

of Traffic Information Reports.

This Traffic Information can be displayed to the customer via suitable terminals.

3.1.35 Traffic Information Report
Technical representation of a Traffic Event produced by processing traffic data.

Each Traffic Reports uniquely identified by a number, the TINFO ID, a time stamp, the TINFO version.

Note: If the Traffic Event changes, the time stamp changes, but the TINFO ID number does not.

3.1.36 Traffic Situation

The total number of all Traffic Events taking place that deserve reporting within an area. The Traffic

Situation is always linked to an area. Thus, for example, an areas could be a conurbation or a

geometrically demarcated area; an example is the radius around a point.
3.1.37 Voice connection

Circuit-switched channel between two systems for bi-directional voice transmission

3.1.38 Waypoint
Significant points on the route
3.2 Abbreviations
For the purposes of this CEN/TS, the following abbreviations apply:
3.2.1 % ott
percent of the time
3.2.2 ADP
Application Data Protocol, i.e. a message set for a telematics service
3.2.3 AM
Acknowledge Message
3.2.4 ASN.1
Abstract Syntax Notation
---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3.2.5 BC
Broadcast
3.2.6 BCS
Broadcast Service
3.2.7 CA
Conditional Access
3.2.8 CAS
Conditional Access and Security
3.2.9 CB
Cellular Broadcast
3.2.10 CBC
Cipher Block Chaining
3.2.11 CLI
Calling Line Identification
3.2.12 CRM
Calling Request Message
3.2.13 CSD
Circuit Switched Data
3.2.14 DES
Data Encryption Standard: symmetrical encryption procedure
3.2.15 DRM
Digital Road Map
3.2.16 DSC
Data Service Centre: depending on the mobile communication network
3.2.17 ELB
Extended Location Block
3.2.18 FCD
Floating Car Data
3.2.19 FCDGM
FCD General Message
3.2.20 FCDPM
FCD Parameter Message
3.2.21 FCDNSM
FCD Notification Set-up Message
---------------------- Page: 12 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3.2.22 FCDRM
FCD Revoke Message
3.2.23 FCDVDSUM
FCD Virtual Detection Site Update Message
3.2.24 GATS
Global Automotive Telematics Standard
3.2.25 GEM
General Error Message
3.2.26 GPS
Global Positioning System NAVSTAR GPS
3.2.27 GSM
Global System for Mobile Communication
3.2.28 IE
Information Element
3.2.29 ICV
Initial Chaining Value
3.2.30 L_max
one
Max. length of transferable data in data transaction
3.2.31 MAC
Message Authentication Code
3.2.32 MNA
Mobile Network Address
3.2.33 MF
Mandatory Fixed format
3.2.34 MO
Mobile Originated Message
3.2.35 MT
Mobile Terminated Message
3.2.36 MV
Mandatory Variable format
3.2.37 N_min
Minimum number of ELB waypoints
3.2.38 OBU
Onboard Unit, synonymously used telematics device, telematics terminal
---------------------- Page: 13 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3.2.39 OF
Optional Fixed format
3.2.40 OV
Optional Variable format
3.2.41 PDU
Protocol Data Unit
3.2.42 PFA
Probability of false alarm (i.e. estimated error is too large)
3.2.43 PMD
Probability of missed detection (i.e. estimated error is too small)
3.2.44 RSA
Asymmetrical encryption procedure by Rivest, Shamir and Adleman
3.2.45 SAE
Society of Automotive Engineers, Inc.
3.2.46 SMS
Short Message Service
3.2.47 SMSC
SMS Centre
3.2.48 SV
Space Vehicle
3.2.49 TEG
Telematics Expert Group – Group within the WAP-Forum Ltd.
3.2.50 TINFO
Traffic Information Report
3.2.51 TOC
Telematics Operator Code
3.2.52 TRP
Transport Protocol
3.2.53 TT
Traffic telematics
3.2.54 TTI
Traffic and Traveller Information
3.2.55 TTFF
Time to First Fix
---------------------- Page: 14 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
3.2.56 UTC
Universal Time Co-ordinated
3.2.57 VDS
Virtual Detection Site
3.2.58 vel, V
Velocity
3.2.59 VIN
Vehicle Identification Number
3.2.60 WAP
Wireless Application Protocol
3.2.61 WGS84
World Geodetic System
---------------------- Page: 15 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
4. Specification of internal services – configuration and master
data update
4.1 Goal of the Service
The task of the internal services is
• the administration and diagnosis of functions and parameters for all services,
• the administration of parameters specific to a particular service, and also
• to check onboard equipment basic functionality.

The separate internal services can be summarised in the areas of access management (4.2), in master

data management (4.3), and diagnosis (see 8) for onboard equipment basic functionality. The

description of the cryptographic procedures required to meet the security requirements and the

associated management of cryptographic keys is done within the framework of the Service „Specification

of Key Management and Security“ (see 5), a short overview over this topic and its interaction with the

internal services is given in 4.4.
4.2 Access Management

The following belong to the functions and parameters covering all services within the framework of

access management:
• Management of communication addresses (Short Message and call addresses),
• Conditional Access management

The concept of Conditional Access (CA) means access control management for telematics services.

It primarily includes activation/deactivation of individual services or service groups and the

assignment of cryptographic methods and keys to the services.
• Service-specific parameter management,
• Management of service language,
• Management of service availability in the case of roaming.
4.3 Master Data Management

This internal service includes the updating of vehicle-related master data for items that were not known

at the time of production of the onboard equipment, or which can change during the lifetime of the

onboard equipment.
4.4 Key Management

The „Specification of Key Management and Security“ (see 5) covers the security mechanisms for the

traffic telematics services between the onboard equipment and the service center. This therefore

touches on the application-independent aspects of the use of cryptographic procedures in carrying out

the services at the transport level and CAS layer, the associated key allocation is described within the

application Key Management (description and ADP). The application-specific parameterization of key

use and the management of service-specific authorization profiles can be found in this specification for

Internal Services.
---------------------- Page: 16 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)

The following function areas are looked at in the „Specification of Key Management and Security“:

• Application of cryptographic methods to provide the security of messages, particularly with respect to:

• Message confidentiality
• Message integrity
• Sender identity / authenticity
• Retaining sender anonymity
• Non-Repudiation

For the individual services, differentiated encryption of the application-dependent data for the individual

services is used for the various interactive point-to-point and broadcast data messages services.

The security concept is based on the following properties of the onboard equipment:

The keys required to encode or decode the ADP contents are made accessible to the onboard

equipment via point to point data message requests within the framework of the „Specifications of Key

Management and Security“ (Key Update) in encrypted form.

The keys are stored in a secured environment in the onboard equipment (1st generation without chip

card), or in an encryption module (2nd generation with chip card).

Each key can be allocated to one or more applications for use so that each operator can decide

independently if he wishes to secure various services with a single unified key or multiple different keys.

4.5 Function Contents and Handling of Access Management

Access management makes available to the onboard equipment all the necessary information within the

onboard equipment to process the services properly.

As a rule access management is initiated by the onboard equipment by an request (Configuration

Request Message) and acknowledged by an update message (Configuration Update Message) from the

service center.

In addition the service center may send Configuration Update Messages without any initiation from the

onboard equipment. These messages may be transmitted individually via point-to-point messages or

non-individually via broadcast messages.

The internal service access management (Configuration Update) includes the address-related,

authorization-related and also parameter-related updates (Address Update, Access Update and

Parameter Update respectively) by the onboard equipment via the data communications media.

Additional information transmitted refer to the service availability in case of roaming (using telematics

services within other countries and/or networks). Figure 1 gives an overview over the configuration

information sent by the service center to the onboard equipment. The individual elements and the

context of their application are given in the following sections.

The configuration elements shall be stored in the onboard equipment (with equipment of the first

generation without chip card) or in the encryption module (in the case of equipment of the second

generation with chip card), so that they can be changed only by the traffic telematics service operator.

Individual situations and the data contents that are consequently transmitted are explained in 4.9.2 to

4.9.7. The following describes the contents of the messages.

The access management specified in this and the following parts of CEN/TS 14821 enable telematics

service roaming and interoperability, however, it is not within the scope of this GATS-specifications to

define the link between the service operators itself.
---------------------- Page: 17 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
4.6 General
The service described below is based on the interface specification
ADP-Version = 2
and shall be signaled at the transport layer as:
Application ID = „Configuration Update“

The following parameter timers are relevant for the proceess control of Access Management Services

itself. The depositing and updating of the timers in the terminal device will be handled according to the

following specification as well as the initialization process defined in this CEN/TS. The usage of the

different timers is explained within the context of the communication procedures.

Table 4-1 : Parameters
Para-
Identifier Description Unit Range Scale Default
meter ID
1 KM_Ctrl Control parameter for Key - 0-65535 1 0
Management, not used in this
version of GATS
2 IS_Ctrl Control parameter for Access-1 0
Management, not used in this
version of GATS
3 IS_Twait Timer between a configuration s 3600 1 240
request message and the
configuration update message

All parameter will be transmitted from the service center to the onboard unit as absolute values, without

any scaling or offset. In the table the given scaling factors, min. and max. values might be used in the

onboard unit for compressed data storage, since the parameter update will be carried out with fixed IE-

lengths for each parameter.
4.7 Configuration Request initiated by the Onboard Equipment

The onboard equipment’s request for parameters is typically made through the Configuration Request

Message. The following information shall be included:

• Identification of the country and mobile network the Configuration Update is requested for.

• The desired type of information (addresses and/or CA information and/or parameters).

• Identification of all applications supported by the terminal, including the ADP Version and the most

recent address and parameter update states of the onboard equipment, marked on the basis of the

update version number. If currently no address / parameter updates are stored in the terminal the

corresponding version number shall be set to zero.

Note: In the case of signaling parameter version number 0 for any application the terminal shall apply the

default parameter settings defined by the services specification of consideration.

If, in case of a manually triggered Configuration Request, the terminal does not receive a Configuration

Update within the waiting period IS_TWait, the request has to be cancelled. The parameter IS_TWait

itself can be set by a Configuration Update.
---------------------- Page: 18 ----------------------
SIST-TS CEN/TS 14821-5:2003
CEN/TS 14821-5:2003 (E)
4.8 Configuration Update sent by the Service Center
4.8.1 General

The general structure of the Configuration Update Message sent by the service center via point-to-point

or broadcast data messages is given in figure 1. It contains the following information elements:

• a variable number of Configuration Blocks (0...255) and

• Each Configuration Block may contain any combination of the following information elements, which

can be used by the service center according to the situation:

• Application Flag: to flag the application-related validity of the following information, optionally

service-related or not service-specific.

• Address Flag: address information included / not included. Transmitted addresses are always

related to applications, i.e. the address flag can only be set in combination with the application

flag.
• Access Flag: authorization information included / not included

• Parameter Flag: parameters included / not included. Transmitted parameters are always related

to applications, i.e. the parameter flag can only be set in combination with the application flag.

The information containers hold the following according to the setting of the above-mentioned f

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.