Download - ERTICO.com

Global System for
Telematics
! "
#$%$&%'$$( #$%$&%'$$(
! "
) * +#' ' ,$$ $- ,'
. * / " 0 " / / "
1)234.2) 14
) * +#' ' ,$$ $- #5
. * 6/ 6 0 " / / "
) # 7 ) 46
8 " 7.6 /
! " 46 8 " 7.6 9 2 6 /
#
#
$
$
1 6
% #

%
0
%
) 46 8 " 9 2 6
$/< $'/$&/'$$( ! " 2 " 78
39
$/& $>/$&/'$$( ! " 6
" 8
8 "

#
) 46 8 " 9 2 6
6 ! " ''%$#%'$$5
1 ! 3 " ''%$#%'$$5
9 ? ! " ''%$#%'$$5
6 ''%$#%'$$5
6 3 "" ''%$#%'$$5
0
'#%$#%'$$5 222

) 46 8 " 9 2 6
0
PART 1 - INTRODUCTION AND ENTERPRISE VIEW.................................11
Chapter 1 - Introduction ........................................................................................12
1.1 Intended Audience ....................................................................................12
1.2 Organisation .............................................................................................12
1.3 Typographic Conventions .........................................................................13
1.4 Objectives.................................................................................................13
Chapter 2 - Executive Summary............................................................................14
Chapter 3 - Methodology for the Deliverable........................................................15
3.1 Introduction ..............................................................................................15
3.2 Architecture Documents............................................................................15
3.2.1 Content of the IP-level Deliverables ..................................................15
3.2.2 Content of the SP-level Deliverables .................................................16
3.3 The Viewpoint Approach of RM-ODP [1] ................................................16
3.4 The Unified Modelling Language (UML) [2]............................................16
3.5 Structure of this Document........................................................................17
3.6 Conventions..............................................................................................18
3.7 Consistency with IP-level Deliverables .....................................................18
Chapter 4 - System Overview ................................................................................20
4.1 Introduction ..............................................................................................20
4.2 The Open Systems architecture and design................................................20
4.3 Architecture Elements...............................................................................21
4.4 Short Description per Element ..................................................................22
PART 2 - LOGICAL VIEW.............................................................................27
Chapter 5 - Protocol Definition..............................................................................28
5.1 The OSI 7 Layer protocol model and the GST derived model....................28
5.2 Identified Protocols...................................................................................29
5.3 The Vehicle to PSAP protocol Stack.........................................................30
5.3.1 Payload Layer ...................................................................................30
5.3.2 Transport Layer.................................................................................31
5.4 The Vehicle To Vehicle protocol Stack.....................................................31
5.4.1 Payload Layer ...................................................................................31
5.4.2 Transport Layer.................................................................................31
5.5 Bi-directional Client System to Service Centre Communication................31
5.5.1 Payload Layer ...................................................................................31
5.5.2 Transport protocols ...........................................................................31
5.6 Client System to Control Centre Protocol Stack ........................................31
5.6.1 Payload layer.....................................................................................31
5.6.2 Transport Layer.................................................................................32
'#%$#%'$$5 ,

) 46 8 " 9 2 6
5.7 Business to Business Protocols..................................................................33
5.8 Service Centre to Client System Broadcasting...........................................33
5.9 Nomadic Device to Client System Protocols .............................................33
5.9.1 Payload Layer ...................................................................................33
5.9.2 Transport Layer.................................................................................34
Chapter 6 - Application Runtime Environment....................................................37
6.1 Introduction ..............................................................................................37
6.2 Use Case Diagram ....................................................................................37
6.3 Basic OSGi functionality ..........................................................................39
6.3.1 Core OSGi framework.......................................................................39
6.3.2 What is an OSGi service....................................................................39
6.3.3 What is a bundle................................................................................39
6.3.4 Importing and exporting packages.....................................................41
6.3.5 Log Service.......................................................................................41
6.3.6 Configuration Service and Metatype..................................................42
6.4 Connection Manager.................................................................................44
6.4.1 Introduction.......................................................................................44
6.4.2 Interfaces ..........................................................................................44
6.4.2.1 Domain Model ..................................................................................44
6.4.2.2 Communication Management from the application point of view ......46
6.4.2.3 Connection manager from the Scheme Handler point of view............47
6.4.2.4 SOAP Connection Factory ................................................................48
6.4.3 API Specifications.............................................................................50
6.5 Positioning................................................................................................59
6.5.1 Introduction.......................................................................................59
6.5.2 Interfaces ..........................................................................................59
6.5.3 API Specification ..............................................................................60
6.6 Event mechanisms ....................................................................................62
6.6.1 Introduction.......................................................................................62
6.6.2 Events coming from the vehicle environment ....................................62
6.6.3 Events coming from the Control Centre.............................................63
6.6.4 Events coming from a Service Centre................................................63
6.6.5 Events exchanged between service applications in the Client System 63
Chapter 7 - Interface To Vehicle Sensors..............................................................64
7.1 Introduction ..............................................................................................64
7.2 Problem Description .................................................................................64
7.3 High-Level requirements...........................................................................65
7.4 Use Case Diagram ....................................................................................66
7.4.1 Actors ...............................................................................................66
7.4.2 Use Cases..........................................................................................67
7.5 Entities......................................................................................................69
1.5.1 Vehicle Admin components .....................................................................70
7.5.1 Data providers ...............................................................................71
7.6 Class View................................................................................................73
7.6.1 Vehicle Admin layer class diagram ...................................................73
7.6.2 Data providers class diagram.............................................................76
7.6.3 Cells Class Diagram (part of data providers layer).............................78
'#%$#%'$$5 (

) 46 8 " 9 2 6
7.7 Sequence View .........................................................................................80
7.7.1 Get Status Element Value..................................................................80
7.7.2 Request Status Element Value Change Notification...........................82
7.7.3 Execute Status Command..................................................................82
7.7.4 Manage Status Elements....................................................................84
7.8 Considered Solution alternatives ...............................................................85
7.9 Vehicle Tree .............................................................................................86
7.9.1 UNITS ..............................................................................................87
7.9.2 Vehicle Tree Description...................................................................88
Chapter 8 - Nomadic Device Integration.............................................................111
8.1 Disclaimer ..............................................................................................111
8.2 Introduction ............................................................................................111
8.3 Terminology Used ..................................................................................111
8.4 Services and Service Repository Synchronization ...................................112
8.5 Use Cases and Collaborations .................................................................112
8.5.1 Initial Connect.................................................................................113
8.5.2 Authentication and Authorization....................................................121
8.5.3 End Point Tree Synchronization ......................................................129
8.5.4 Vehicle Status Service Discovery and Initialization.........................132
8.5.5 eCall discovery and initialization.....................................................137
8.5.6 Service Consumption ......................................................................137
8.5.7 Service Provisioning .......................................................................138
8.6 Protocols.................................................................................................140
8.6.1 Protocol Stack .................................................................................140
Chapter 9 - Deployment And Provisioning .........................................................141
9.1 Introduction ............................................................................................141
9.1.1 Protocol-oriented.............................................................................141
9.1.2 Domain Model ................................................................................141
9.2 Use Case Diagram ..................................................................................142
9.3 Deployment ............................................................................................143
9.3.1 Scope ..............................................................................................143
9.3.2 Solution...........................................................................................144
9.3.3 The gst-deployment.xml file............................................................144
9.3.4 Physical Structure............................................................................150
9.3.5 Example gst-deployment.xml ..........................................................151
9.4 Provisioning Protocol..............................................................................152
9.4.1 OMA Device Management Bootstrap..............................................152
9.4.2 OMA DM Device Description Framework DTD .............................152
9.4.3 OMA Device Management Notification Initiated Session................152
9.4.4 OMA Device Management Protocol................................................153
9.4.5 General ...........................................................................................153
9.4.6 Large Object Handling ....................................................................153
9.4.7 Generic Alerts .................................................................................154
9.4.8 User Interaction commands .............................................................154
9.4.9 OMA Device Management Representation Protocol........................155
9.4.10 OMA Device Management Security................................................155
9.4.11 OMA Device Management Standardized Objects............................155
9.4.12 OMA Device Management Tree and Description ............................155
'#%$#%'$$5 5

) 46 8 " 9 2 6
9.4.13 OMA Device Management Tree and Description Serialization........156
9.5 GST Provisioning Device Management Tree (DMT) ..............................156
9.5.1 Node Name Conventions.................................................................157
9.5.2 Components Management Object....................................................157
9.5.3 Services Management Object ..........................................................160
9.5.4 Users Management Object...............................................................163
9.6 Behaviour Associated with the Management Objects ..............................167
9.6.1 User Display Interactions ................................................................167
9.6.2 Components Management Object....................................................167
9.6.3 Services Management Object ..........................................................170
9.6.4 Users Management Object...............................................................170
9.7 Use Case Realizations.............................................................................171
9.7.1 Subscribe to service from client.......................................................171
9.7.2 Subscribe to service from Control Center with user intervention......171
9.7.3 Subscribe to service from Control Center without user intervention.172
9.7.4 Upgrade of a service without user intervention ................................174
9.7.5 Activate new component .................................................................175
9.7.6 Upgrade component ........................................................................175
9.7.7 Remove component.........................................................................175
Chapter 10 - Identity, Authentication, Authorization ........................................177
10.1 Introduction ............................................................................................177
10.2 Use Case Diagram ..................................................................................179
10.3 Interfaces ................................................................................................179
10.4 Protocol Stack and Specification.............................................................179
10.5 Message Structure...................................................................................179
10.6 API Specification....................................................................................179
10.7 Interactions .............................................................................................180
PART 3 - IMPLEMENTATION VIEW AND CONCLUSIONS.......................181
Chapter 11 - Reference Model .............................................................................182
11.1 Components............................................................................................182
11.2 Nodes .....................................................................................................185
Chapter 12 - Architectural Issues and Decisions.................................................188
12.1 ARE: considered alternatives for positioning...........................................188
12.2 Protocols: Using SIP as a Transport/Routing Protocol.............................188
12.3 Vehicle Interface: considered solution alternatives..................................188
Chapter 13 - Conclusions and Next Steps............................................................191
13.1 Compliancy matrix indicating how each requirement is covered by the
design 191
PART 4 - APPENDIX SECTION..................................................................199
Appendix A - Terms and abbreviations ..............................................................200
Appendix B - References ......................................................................................204
'#%$#%'$$5 -

) 46 8 " 9 2 6
Appendix C - Overview of the UML terminology used in this document ..........208
13.2 Collaborations.........................................................................................208
13.3 Work Item...............................................................................................208
13.4 Components............................................................................................208
13.5 Diagrams ................................................................................................208
13.5.1 Class Diagram.................................................................................208
13.5.2 Sequence Diagram ..........................................................................208
13.5.3 Activity Diagram.............................................................................208
13.5.4 Component Diagram .......................................................................208
13.5.5 Deployment Diagram ......................................................................208
13.6 Views .....................................................................................................208
13.6.1 The Enterprise View........................................................................209
13.6.2 Logical View...................................................................................209
13.6.3 Implementation View......................................................................209
Appendix D - Index ..............................................................................................210
'#%$#%'$$5 >

) 46 8 " 9 2 6
Figure 1 - Sub-project Components ..........................................................................14
Figure 2 Workpackage 3 Deliverables ......................................................................18
Figure 3 High Level Overview of Open Systems ......................................................20
Figure 4 System Overview, Reference Points and Collaborations for the Open
SystemsSub-Project ..........................................................................................21
Figure 5 GST and OSI Protocol Layers comparison..................................................28
Figure 6 Authorizing service access with SAML assertions......................................33
Figure 7 Main Protocol Stacks..................................................................................36
Figure 8 Application Runtime Environment .............................................................38
Figure 9 Class Diagram for Connection Manager .....................................................45
Figure 10 An application getting a connection..........................................................47
Figure 11 Registering new transport protocols..........................................................48
Figure 12 A SOAP extension of the ConnectionFactory ...........................................49
Figure 13 Sending a SOAP message.........................................................................50
Figure 14 Class Diagram for Positioning ..................................................................59
Figure 15 – Example vehicle hardware system architecture ................................64
Figure 16 – Use Case Diagramm ..............................................................................66
Figure 17 System Overview ...................................................................................111
Figure 18 TCU FEP Activation ..............................................................................114
Figure 19 TCU FEP Activation ..............................................................................114
Figure 20 Nomadic Device FEP Activation ............................................................115
Figure 21 Nomadic Device FEP Activation ............................................................115
Figure 22 Initial Connect Sequence Diagram..........................................................116
Figure 23 Nomadic Device FEP discovery .............................................................118
Figure 24 Initial Connect Nomadic Device Classes.................................................119
Figure 25 Initial Connect TCU Class Diagram........................................................120
Figure 26 Setup and Management Phase.................................................................121
Figure 27 ND Class Diagram..................................................................................124
Figure 28 Tcu Verify ND Credentials.....................................................................125
Figure 29 Service Info Object.................................................................................129
Figure 30 Service Synchronization .........................................................................130
Figure 31 Two Way Synchronization .....................................................................131
Figure 32 Vehicle Status Discovery........................................................................134
Figure 33 Vehicle Status Discovery........................................................................135
Figure 34 NDIService.............................................................................................138
Figure 35 Use Case Overview ................................................................................139
Figure 36: Provisioning and Deployment domain model.........................................142
Figure 37 Use cases for Provisioning and Deployment ...........................................143
Figure 38 Top-level structure of gst-deployment.xml..............................................144
Figure 39 Structure of the system type definition element......................................145
Figure 40 Structure of the service definition element ..............................................146
Figure 41 Structure of service application element..................................................147
Figure 42 Structure of the supported system types element.....................................149
Figure 43 Structure of the supported locales element ..............................................150
Figure 44 GST Provisioning Management Objects .................................................157
'#%$#%'$$5 &

) 46 8 " 9 2 6
Figure 45 Components Management Object. ..........................................................158
Figure 46 Services Management Object..................................................................160
Figure 47 Users Management Object......................................................................164
Figure 48 Data upload via OMA DM. ....................................................................168
Figure 49 Data upload though OMA DL.................................................................168
Figure 50 Component diagram ...............................................................................182
Figure 51 Deployment Diagram .............................................................................185
'#%$#%'$$5

) 46 8 " 9 2 6
91) < . 2=)14 3)24= 9=
=) 1 12 2
'#%$#%'$$5

Chapter 1 - INTRODUCTION
1.1 Intended Audience
) 46 8 " 9 2 6
) " 6 " 8! " "7 7.
"6 " ) 46 8 " " ! / " " !
7 2 # ) 3) 39 2 . . 6 6 / )
! 7 9/
1.2 Organisation
) " ! *
• 2 6 !
o 2 A 6
o B "" 8A 6 ! "
6 78 " / 1 6 8 8 7
6 " 78
7 /
o 8 7 A 2 6 "
46 8 " 66 78 7
" 8/ ) " 6 78 6 ! 6
8 6 ! 6
7 7 " " /
o 8 " 4 ! A ) 6
B "6 78! 6 # 6 " 78
46 8 " '/< 7 C#D/
• : ! A ! 6 / )
6 " 87 8 ! " 6 * "
6 B"6 %4 7 6 / )
B"6 7 " 6 !
" 78 6 " 7 /
o A 9 " 6
"" " 6 /
6 6 ! 7 " )
" /
o 966 1 " " A ) 46 8 " " !
7 " 6 3 8 "/
o 2 A ) 6 6 ) 8 " !
66 " .6 6 8! 8/ )
78 6 " .
" 8 "/
o = " 2 A ) 6 6
"6 "" 7 ! "
9E 3 6 ! "7 . 3
8 " /
'#%$#%'$$5

) 46 8 " 9 2 6
o 6 8" A 6 / ) 6
6 8" 66 "
6 3 3 6 8 6
966 " 3 3 3 8 "/
o 2 8 9 9 ? A ) 46
8 " 6 " 6 8
? 7 66 /
• 2"6 " ! 3 A ) 6 6 #/'
7 6 8 ) 46 8 " "6 " /
o 1 A "6 6 8" " !
1 2"6 " /
o 3 = B 6 A 1 6 "
6 6 ! ! 7 78 )
/
1.3 Typographic Conventions
) ! 86 6 " *
9 ! ! 6 2 6 " B6 78
66 B) " 77
Code Examples 3 B"6 6
C:\Project\MyCode.c " 6 /
1 6 " 6
7
C

Chapter 2 - EXECUTIVE SUMMARY
) 46 8 " 9 2 6
) " 6 " # G9
2 6 H 46 8 " 7.6 /
Figure 1 - Sub-project Components
9 6 " 8 6 7
8 " ! 7.6 / ) 8 " ! 7 8 7.
8 " 6 " 7.6
B " 6 /
) ! 6 8 8 46 8 " 7.6
6 6 7.6 / 6
6 " . I! F "
" " 'J ! 8
6 /
#
Use cases &
system requirements
! " # !
"$ !
" #
&' # # "
WP1
Architecture &
interface specifications
Project management
Dissemination and
exploitation
To and from all WPs
WP2 WP3 WP4 WP5 WP6
WP7
Prototype
development
To and from all WPs
Field trials
Validation
WP Manager
WP Participants
% # !
'#%$#%'$$5

) 46 8 " 9 2 6
Chapter 3 - METHODOLOGY FOR THE DELIVERABLE
3.1 Introduction
) " 8 7 7 1 .4 I !6 66 J C

• 9 " 8
• ).!
) 46 8 " 9 2 6
• ) 7 . 2 . . " /
) 2 . " 8 ! "
) ! B ! 7.6 7
" 8 7 /
) " 6 2 . 7 . $
" 6 ! 8 "
" ! 8/
3.2.2 Content of the SP-level Deliverables
) " *
• 7.6 I " J
• 6 " I 6 J
• ) 7 . 2 . . " /
3.3 The Viewpoint Approach of RM-ODP [1]
1 "6 ! "6 B 8 7 8 " 1 .
4 8 " " $ " 6 !
/ !6 6
7 7 8 " ! "
7 /
) ! !6 *
% "
6 6 8 "
: 2 " "6 " 7
8 7 ! 7
2"6 " 9 "6 " 8 "
Table 2 - GST Viewpoints
3.4 The Unified Modelling Language (UML) [2]
) ) 6 7 !6 78"
: I :J " / ) : 6 7 ""
B6 ) 6 "6 "
"6 " I 7 ! J 6 86 "6 " /
) ! : " *
'#%$#%'$$5

% " 2 1
6 3 " + 7
) 46 8 " 9 2 6
: 3 " I " 6 J
2"6 " 3 "6 "
F " I " 7 6 J
. " I " 7 6 J
6 8" "
Table 3 - Principal UML Diagrams used in GST
= 7 B " 66 "
"" 8 " 6 : " "
7 " " 6 I 7 !
) 8 " ! " 9K 4 : ) J/
3.5 Structure of this Document
) B 6 6 8 " ! 7.6 8 7
" 7. 8 " 6 I J 7
7.6 /
) " " ! *
I J
2 "
2 3 "
6
2 6
L 82 F "
L 8: 8 3
2 6
: 8 6
1 3 "6 3 "6 "
3 "6 6
= 6 8" "
= 6
Table 4 - Structure of this Document
'#%$#%'$$5

3.6 Conventions
) 46 8 " 9 2 6
) 8! G )H G ) =4)H G1 M 21 H G 9::H G 9:: =4)H
G 4 : H G 4 : =4)H G1 34 = H G 9KH G4 )24=9:H
" 7 6 7 C,'D/
) 6 " ! " 86 " *
• 9 6 A " " 6 ! ) 7 66 /
• 9 7 A 6 " 7 7 6
4 I46 8 " ! 82 J " / ) 7
! 6 6 *
o 2 6 3 6 78"
! . 8 B/ 8
6" ! ! ! 8 6
! 7 "7 7 6" /
o 2 8 6 " " 4
" ! / ) " B"6
7 46 ) " " ! 7 4 )24=9:/
Reference Implementation Development Tools
Reference Implementation
Protocol Binding
Protocol and State Specification
Hardware Requirements
Additional APIs
(e.g. vehicle)
Figure 2 Workpackage 3 Deliverables
3.7 Consistency with IP-level Deliverables
9 8 " 2 . 7 7 8 6 78
2 . 7 G) 3 % 3 H " / 2
7 " . 7 7 " 7 8
! 2 . 7 ! /
GST Protocols
Architecture
GST In-vehicle Software
Execution Environment
'#%$#%'$$5

) 46 8 " 9 2 6
) 2 . 7 7 *
• :; );4 ;39 ;#;

Chapter 4 - SYSTEM OVERVIEW
4.1 Introduction
) 46 8 " 9 2 6
46 8 " 6 8 6 7 8 " ) "
I )J/ ) 7.6 ? "6 ! ""
! 7 ) " G " H78
) 7.6 /
) ! 6 ! "6 !
7 46 8 " /
Payment and
Billing
Develop, Offer and Operate Services
Service
Deployment
Service Centres
Subscribe Authentication Client System
Management
Control Centre
Service
Usage
Service
Provisioning
Figure 3 High Level Overview of Open Systems
4.2 The Open Systems architecture and design
End Users
2 "6 B 2 ! 8 7 ""
6 7 / 2 " 8 " .
"6 6 ! 7 ! 7 7
66 / ) 8E "6 6 " 78 6
7 ! 6 " 7 "6 /
) ) 46 8 " 7.6 6
! 66 6 6 " 7
"6 8 " / ) 8 " 7 "7 . ! !
6 " 7 8 " 9 I 9J
" 7 6 / 2 B 7 8 " ) " 46 8 "
6 7 8 ! ! ) 7.6
1 3 83 6 7 /
9 46 8 " " 7 7 7 6 " 7
6 " / ) " " 46 8 " 7.6 ! 7 * )
6 ! 6 6 / 2 ! 6
"6 " 78 .
) " 7 "6 " ) 3 "6 8 " /
'#%$#%'$$5 '$

) 46 8 " 9 2 6
) . 78 6
" / ) 7
" 8 " 8 "/
9 6 6 46
8 " 3 3 / 2 ! 8 3 3 " 7
! )/ 2 " 6 6 7 966
. /
) 66 966 ! "6 "
6 8" 6 / 6 8" 966
? 6 ! 8 6 86 8
) 3 "6 3 3 / ! 8 7
87 6 6 6 86 7 66 " /
2 8 6 ! 6 8"
966 " ) "6 3 3 /
) " 78 " 966
7 . / 4 " 7 7 3 3
6 . 3 8 " ! 966 /
9 3 3 6 8 8 "
7 7 66 /
3 " 78 3 "
78 . . " 8 //
4.3 Architecture Elements
, ! ! 8 " 6 A
6 A 8 7 46 8 " 7.6 /
Figure 4 System Overview, Reference Points and Collaborations for the Open SystemsSub-
Project
'#%$#%'$$5 '<

) 46 8 " 9 2 6
1 6 8 7 ! 7 "
6 8 )/ 2 6 " 78"
! 9K ) 7 "6 " 78 ) < /
4.4 Short Description per Element
) 46 8 " 7.6 78 , 6 6
! ! 3 8 " "" ! ) "
" 3 3 / ) 6 6
! 3 8 " " 8 7 78 966
6 "6 " /
$ 0 ! ! ! % #
! "$ ! ! # $ "
# % ! # # !
# "
) 6 6 7
! " 6 7 /
9 B6 " 7 6 ) 7 (/
8= " 8" 7 " !
" " I $J
'#%$#%'$$5 ''

) 46 8 " 9 2 6
" " /
2 " 6 ) 6 " " 7
2 "/
Table 5 - Definition of Terms Used when Presenting the System Overview
'#%$#%'$$5 '#

) 46 8 " 9 2 6
3 # 5 3 ) $ 5
3 I3J = ) 3 7 .
6 8 6 8
966 / 2 F 8 "6 " IJ 66
66 "" ! 966
3 8 "/
) " 3 3 8 " ) ) " 3 " "
"6 6 78 46 8 " 966 1 "
" /
3 8 "
"
9
9 ?
3 3 ) 6 3 3 !
" " 3 8 " !
66 " " 6 /
3 8 " 2 " 8 6 " /
2 B ) 3
8 " 7 ! B ! /
3 3 ) "6 3 3 6 7
? / 2 @ !
/
Table 6 - Entities for the Open SystemsSub-Project
''%$#%'$$5 ',

#
6 8"
2 I .2J
8 " "
2 I .2J
I .2J
2
2 I .2J
= "
2
) 46 8 " 9 2 6
6 7 # 0
• Provisioning and Deployment
• Protocol Definition
• Provisioning and Deployment
• Protocol Definition
'#%$#%'$$5 '(

) 46 8 " 9 2 6
2 6 2 ! 966
4 : ) 3 "6 ! "
6 8" 6 1 M 21 6 8" 6
6 6
2 8 9
9 ?
) ! " 6 6 6 78
8 7. 8 "/
= " 2 6 1 34 = ""
7 ! = " )3 /
Table 8 - Descriptions of the Work Items for the Open Systems Sub-project
'#%$#%'$$5 '5

) 46 8 " 9 2 6
91) ' . :4 239: 2
''%$#%'$$5 '-

Chapter 5 - PROTOCOL DEFINITION
) 46 8 " 9 2 6
5.1 The OSI 7 Layer protocol model and the GST derived model
"" 6 4 2 - : 8 " 6 "
" ? 8 6 / 6
8 / " 7 " 6 6 6
78 / 6 6 7 "6
F " .6 6 78 " /
6 6 ) -. 8 " "6 ! 7 8 8 *
6 8 6 8 / ) 6 8 8 6 !
8 6 7 8
8 66 8 " 86 / ) 6 8 6
" /
) ! 6 ! 7 ! ! /
Figure 5 GST and OSI Protocol Layers comparison
) ) 46 8 " 6 - 6 *
• % . 6 78 2
7 "6 " 78 ) 1 "6 966 !
" " " I J 7 89 ! I 9 J C,#D/
• % % A 6 78 2 7 "6 "
78 966 ! 66 ""
3 C,#D@ C,#D "" C,,D/
• $ 0 0 ) A
6 78 2 7 "6 " 78 966
! "" 7 ! 3 3 8 " 7.
/
'#%$#%'$$5 '>

) 46 8 " 9 2 6
• % 0 0 A 6 78 2 7
"6 " 78 3 8 " 66 ! "68 6
6 " /
• 8 8 A 6 78 2 7 "6 "
78 3 3 3 . "6 ""
C,#DC,,DC,(D/
• $ 0 % 2 ) A 6 78
2 7 ! "6 " ) 83 6 C,(D/
• # $ 3 . 6 78
7 = " 2 6 "
2 7 "6 " 78 966 "68 6 /
) ! 6 6 6 6 6 *
5.2 Identified Protocols
) ! 7 6
/ " 7 " 6/
7 9 :
% C(

0
8
8
$ 0
% 2 )
# $
3
) 46 8 " 9 2 6
7 9 :
2 I5JCD 1 F
)3 23 C(#DC(,DC((D 1 F
)) C,>D 1 F I ))
2 J
9 C'#D 1 F
9 :CDC''D 1 F
9 :C

5.3.2 Transport Layer
) 46 8 " 9 2 6
66 " 8 I2 3$'/

) 46 8 " 9 2 6
) "6 " 6 2 "68 ! 46
7 9 I4 9J

5.7 Business to Business Protocols
) 46 8 " 9 2 6
) @ . .@ 8 6 ) B 6
8 6 /
) ) 3 " 3

) 46 8 " 9 2 6
9 ) "6 = " 2 "6 2 "6 "
! 6 *
4 9 8 : 1 6 C

) 46 8 " 9 2 6
'#%$#%'$$5 #(

) 46 8 " 9 2 6
Figure 7 Main Protocol Stacks
''%$#%'$$5 #5

) 46 8 " 9 2 6
Chapter 6 - APPLICATION RUNTIME ENVIRONMENT
6.1 Introduction
2 3 8 " 7 6 66 6 78
6 8 " 8
66 B /
) ! " "6 9 2 3 8 "
66 "" 8 3 8 " *
•
• 6 I " J
• " "
• "" " "
•
" B 7
Q ! 7 / 6 7 ) .
B "6 ! "
. 8" 7 /
6.2 Use Case Diagram
> ! 7 " 66 "/
''%$#%'$$5 #-

ud Use Cases and collaborations
UC-OS-0001
Check Client
System Status
ClientSystemStatus
RQ-OS-0066
automatically
choosing the
connection
depend
UC-OS-0024
Application
«realize»
Download(from WI
deployment and
prov isioning)
depend
ConnectionManager
This interface will
allow the dynamic
registration of new
protocol handlers.
Interface
for registering
new transport
protocols
«extend»
Connection
interface to
applications
«realize»
«extend»
This module will take
care of choosing which
connection is to be
used if there are
several available.
) 46 8 " 9 2 6
depend
«include»
depend
UC-EFCD-0005
Message and
Communication
Handling
UC-OS-0023
Serv ice
Consumption
UC-OS-0057
Monitoring
Monitoring_and_testing
UC-OS-0058
Testing
Logging
Positioning
'#%$#%'$$5 #>

6.3 Basic OSGi functionality
6.3.1 Core OSGi framework
) 46 8 " 9 2 6
2 6 )
4 7 / ) 7 7 6 7 8 66
3 8 " . 78 "" 6 "" 4
"" " ! ) 9 2 8 ! 7
7 ! 66 ) 3 8 "/
) 4 6 6 " !
! 66 8 " " 8 "
7 ! 66 6 8 " "
8 " " ! 8/
2 " ! ! 66 8 " 8 6
"" 6 7 ! 8! / ) " !
6 6" 6 " "6 .7 !
R 7 8 ! " ! /
6.3.2 What is an OSGi service
9 4 . "6 7 /
" 87 " " ! / 9 !
6 *
•
• "6 " IJ
) 6 8 I/ / ! J/ 4
6 7
6 "6 " /
9 " 6 "6 " 6 78 /
B"6 " 8 " 8/
9 6 7 "6 / 2
6 6 6 " !
1 8! 7 7
6 6 /
) 8 " 6 8 " /
6.3.3 What is a bundle
) 7 7 " ! "6 " " 7 6 /
"6 " 6 7 / @ " 87 "
" ! / 9 7 91 *
'#%$#%'$$5 #&

) 46 8 " 9 2 6
• "6 " ? " / )
" 87 ! ) : 6
I J /
• " 7 91 6
" 7 7 / ) 6 86 "
" ! 8 7 /
• 6 7 7 / )
B 6 7 / 2 ! " 6
! 78 " ! 7 /
• 6 " 4 2.4 ) 8 91
7 / ) " 7 7 /
8 7 6 5 *
• 2= )9:: ///////// 7 7 8 /
• 1 4: //////// % 7
7 / ) 7 8 7
66 /
• )91)2= ////////// 7 7 @ 9 /
" 7 8 /
• )4 2= ////////// 7 7 66 @ 9 / 6
" 7 8 /
• 93)2 /////////////// 7 8 /
• =2= )9:: //// 7 7 / 2 "
/
'#%$#%'$$5 ,$

6.3.4 Importing and exporting packages
) 46 8 " 9 2 6
@ 4 " ! 6 / 7 B6 8
6 /
9 7 6 7 B6 .
" 2"6 .
" /
) 2"6 . " ! 7 F 6
7 B6 78 7 4 " /
) 8 F 6 " " 7 7 E 2"6 .
" 6 7 B 6 6 " 7 ! *
/S
7 "6 6 " 7
6 87 ! ! 7 / 9 6 8 7 78
" ! I/ / 7 B6 6 7 7 J 7
6 7 7 /
6.3.5 Log Service
96 " 7 " ! 8 4 6
7 8 ! " 4 66 /
4 : /
) : 8 " ! / 2
6 6 " 4 " / 2 8
! 6 I J A / / / /:
/ / / /: 1 /
9 8 " " 6 " "
6 " " /
) : 6 7 8 ! " / :
6 F ! . 6 8/ " 8
" " F 7 /
: " F ! F 6
" " 6 /
2 4 " ! "6 7 6 "" 8
: 8 7 / ) 8 6 78: 1 /
) : ! 6 *
T 6 8 " % B 6 7 /
T 668 6 8 " 7 /
) 7 : /
T 6 8 ! F /
'#%$#%'$$5 ,<

) 46 8 " 9 2 6
@8 7 : 7 " " ! 8 66
" : 7 78 :
" / 9 : 7 8" 7 6 " 8
6 /
; ; $ ; ;1 $
Type: public abstract «interface» Interface
Package: Logging
org.osgi.service.log.LogService Interfaces
Method Type Notes
log (int,
String)
log (int,
String,
Throwabl
e)
log
(ServiceR
eference,
int,
String)
log
(ServiceR
eference,
int,
String,
Throwabl
e)
public: void param: level [ int - in ]
param: message [ String - in ]
public: void param: level [ int - in ]
param: message [ String - in ]
param: exc [ Throwable - in ]
public: void param: service [ ServiceReference - in ]
param: level [ int - in ]
param: message [ String - in ]
public: void param: service [ ServiceReference - in ]
param: level [ int - in ]
param: message [ String - in ]
param: exc [ Throwable - in ]
6.3.6 Configuration Service and Metatype
3 6 7
7 ! 8 4 " /
) 3 9 " 6 " *
US9 ! /6 6 6 8
S2"6 " 8 /
) 8 7 3 ) /
'#%$#%'$$5 ,'

) 46 8 " 9 2 6
3 9 " " !
6/ 3 8 7 8% 6 / L 8
! 8 7 86 *
86 V W 2 W : W W 7 W @8 W W @ 2 W
@ " W3 W@ W W 8
6 " V W W W W78 W7 W 7 W
8 V 6 " XCDEW 86 XCDE
V 86
) 6 8I2 J 3 ) 8
6 / 9 2 F 6
" 6 " ! / 2 7 66
" 2 7 /
) 3 9 " " 1 8 ! !
3 ) 2 /
/
3 9 " "
6 6 IJ " 6
@8 3 8 G !H 8
! 6 8 6 " 7 6
B6 86 / ) 6 "
6 . " 86 /
) 86 6 ! 7 6 7
7 86 "6 7 " . " /
"7 ! 3 86 6 " 7
8 " 7 ? " 6
86 8/
9 " *
" ) 4 3
) 2 ) ) 7 F 8 6
3 8 "/ ) " 6 )
4 : 6 " 6 B 2 /
'#%$#%'$$5 ,#

6.4 Connection Manager
6.4.1 Introduction
) 46 8 " 9 2 6
) " " "6 B F " " "
"" 3 8 "/ ) 8"
7 7 " 7 ! ! 6 "
M 6
8 ! 6 / " " " 6 7
6 M 7 ! ! 7 Q " " 8
" 7 ! 7 8 " ! "6 7
/
9 " " 66 7 " "6 B7
" 6 7 /
) F " 3 7 "
*

cd ConnectionManager
«interface»
org.osgi.service.io.ConnectorService
+ open(String) : javax.microedition.io.Connection
+ open(int, String) : javax.microedition.io.Connection
+ open(boolean, int, String) : javax.microedition.io.Connection
+ openDataInputStream(String) : java.io.DataInputStream
+ openDataOutputStream(String) : java.io.DataOutputStream
+ openInputStream(String) : java.io.InputStream
+ openOutputStream(String) : java.io.OutputStream
1
uses
1..*
«interface»
org.osgi.service.io.ConnectionFactory
+ close() : void
+ getScheme() : String
+ createConnection(string, int, boolean, Dictionary) : javax.microedition.io.Connection
+ open() : void
) 46 8 " 9 2 6
1
«interface»
javax.microedition.io.Connection
+ close() : void
OSGi
Framework
Application
'#%$#%'$$5 ,(

) 46 8 " 9 2 6
# ) $ 5
B/" / /3 9 B /
2 B 78
63
"3
2 6 3
4 6 3
/ / / /3 8 9 B
' 3 4
1 # 3 8
/ / / /3 B " 4 1#
' 3 4
1 # 3 8
Table 10 - Descriptions of Interfaces for Connection Manager
6.4.2.2 Communication Management from the application point of view
) ! F " ! 6 ! 66 6
*
''%$#%'$$5 ,5

sd An application geting a connection
) 46 8 " 9 2 6
Application OSGi Framework «interface»
ConnectionFactory
org.osgi.service.io.ConnectorService
Application
getService(Connector service)
Connector service object
open(String)
searches for a suitable
ConnectionFactory in
the service registry
returns the
ConnectionFactory
returns a Connection object
createConnection(String uri,
int mode, boolean timeout)
Figure 10 An application getting a connection
Application
implementing an
org.osgi.service.io.ConnectionFactory
e.g. for handling the
"HTTP" scheme
As you can see, the getting of the Connection is done in two steps: first the application
acquires the Connector Service from the Service Registry, and then asks the
Connector Service for a Connection object. Once a Connection object is obtained, its
methods will be used for sending messages during the lifecycle of the application.
6.4.2.3 Connection manager from the Scheme Handler point of view
) ! F " ! ! 3 8 66
6 ! " I6 J 7 8 " 8 3
8 " ! /
'#%$#%'$$5 ,-

sd Registering new transport protocols
ConnectionFactory
Application
register the
ConnectionFactory in the
Application
Service Registry
implementing an
org.osgi.service.io.ConnectionFactory
e.g. for handling the
"HTTP" scheme
6.4.2.4 SOAP Connection Factory
) 46 8 " 9 2 6
OSGi Framework
Figure 11 Registering new transport protocols
'#%$#%'$$5 ,>

cd ConnectionManager
«interface»
org.osgi.service.io.ConnectorService
+ open(String) : Connection
+ open(int, String) : Connection
+ open(boolean, int, String) : Connection
+ openDataInputStream(String) : java.io.DataInputStream
+ openDataOutputStream(String) : java.io.DataOutputStream
+ openInputStream(String) : java.io.InputStream
+ openOutputStream(String) : java.io.OutputStream
«interface»
org.osgi.service.io.ConnectionFactory
+ close() : void
+ getScheme() : String
+ createConnection(string, int, boolean, Dictionary) : Connection
+ open() : void
«interface»
SOAPConnectionFactory
1
1
«interface»
AdapterManager
ConnectionPolicy
«realize»
1
1
uses
1..*
«interface»
SOAPConnection
+ close() : void
0..*
GPRS Adapter
IEEE 802.11
Adapter
) 46 8 " 9 2 6
«interface»
javax.microedition.io.Connection
+ close() : void
OSGi
Framework
Application
'#%$#%'$$5 ,&

) 46 8 " 9 2 6
send messages, block low-priority messages if a high-priority message has to be sent,
and request connecting over a fixed network adapter as opposed to the automatic
connecting that the Operating system does when you simply open a socket.
The process of sending a SOAP message is shown on the following diagram:
sd SendingSOAPMessage
Application OSGi Framework «interface»
«interface»
«interface» «interface»
open(URL with soap header)
ConnectorService
searches for a suitable ConnectionFactory in the service registry
returns the SOAPConnectionFactory
return the SOAPConnection object
SOAPConnectionFactory SOAPConnection
createConnection("soap://priority=2")
create
createRequestObject(String targetObjectURI, String methodName, Vector
params,Properties headerAttributes, String encodingStyle, int priority)
return SOAP request object
invoke(URL soapServerURL, String SOAPActionURI)
return SOAPResponse
6.4.3 API Specifications
create
SOAPRequest
'#%$#%'$$5 ($

&$ 4; ; ;0
Type: public abstract «interface» Interface
Package: ConnectionManager
) 46 8 " 9 2 6
An existing standard interface.
It is extended by HttpConnection, DatagramConnection, InputConnection,
OutputConnection etc.
javax.microedition.io.Connection Interfaces
Method Type Notes
close () public: void
; ; $ ; ;0 '
Type: public abstract «interface» Interface
Package: ConnectionManager
An existing interface
See J2ME Connector and OSGi Release 3 ConnectionFactory
org.osgi.service.io.ConnectionFactory Interfaces
Method Type Notes
close () public: void
getScheme () public: String
createConnection
(string, int, boolean,
Dictionary)
public:
javax.microedition.io
.Connection
param: uri [ string - in ]
param: mode [ int - in ]
param: timeouts [ boolean - in ]
param: options [ Dictionary - in ]
open () public: void MUST be called by the implementation of the
Connector service before any create-
Connection method is called. It MAY be used
to create resources that are
need for the correct operation of this package.
; ; $ ; ;0 $
Type: public abstract «interface» Interface
Package: ConnectionManager
Existing interface from OSGi R3
'#%$#%'$$5 (<

org.osgi.service.io.ConnectorService Interfaces
Method Type Notes
open (String) public:
javax.microed
ition.io.Conne
ction
open (int, String) public:
javax.microed
ition.io.Conne
ction
open (boolean, int,
String)
openDataInputStrea
m (String)
openDataOutputStre
am (String)
openInputStream
(String)
openOutputStream
(String)
0 '
public:
javax.microed
ition.io.Conne
ction
public:
java.io.DataI
nputStream
public:
java.io.DataO
utputStream
public:
java.io.InputS
tream
public:
java.io.Output
Stream
Type: public abstract «interface» Interface
Implements: ConnectionFactory.
Package: soap
) 46 8 " 9 2 6
param: address [ String - in ]
param: mode [ int - in ]
READ, WRITE, READ_WRITE
param: address [ String - in ]
The address of the destination, in URI format
param: timeout [ boolean - in ]
param: mode [ int - in ]
READ, WRITE, READ_WRITE
param: address [ String - in ]
The address of the connection, in URI format
param: address [ String - in ]
The address of the destination, in URI format.
param: address [ String - in ]
The address of the destination, in URI format.
param: address [ String - in ]
The address of the destination, in URI format.
param: address [ String - in ]
The address of the destination, in URI format.
'#%$#%'$$5 ('

) 46 8 " 9 2 6
Attribute Type Notes
public static : The name of the priority property in the
PRIORITY_PROP_NA String SOAPRequest headers.
ME
Initial Value: "priority";
HIGH_PRIORITY public static :
int
Initial Value: 3;
public static : Initial Value: 2;
NORMAL_PRIORITY int
LOW_PRIORITY public static :
int
Initial Value: 1;
SOAP_SCHEME public static : The value of the service property IO_SCHEME It
String provides the scheme for which the
SOAPConnectionFactory is able to create
Connection objects.
Initial Value: "soap";
An extension of the Connection Factory defined in OSGi R3 for getting connections
over the SOAP protocol. The SOAP Connection Factory adds prioritization and
connection management on top of a SOAP stack.
SOAPConnectionFactory Attributes
0
Type: public abstract «interface» Interface
Extends: Connection.
Package: soap
This interface provides methods for creating the objects needed for a communication
over the SOAP protocol.
SOAPConnection Interfaces
Method Type Notes
createRequestObject
()
public:
SOAPRequest
Creates an empty request object that can later be filled
in by using its set methods
'#%$#%'$$5 (#

Method Type Notes
createRequestObject
(String, String,
Vector, Properties,
String)
createParameterObje
ct ()
createParameterObje
ct (String, Class,
Object, String)
9
public:
SOAPRequest
public:
SOAPParame
ter
public:
SOAPParame
ter
) 46 8 " 9 2 6
param: targetObjectURI [ String - in ]
The object ID of the service being invoked
param: methodName [ String - in ]
The name of the method to invoke on the service
param: params [ Vector - in ]
The parameters of the method as a Vector of
SOAPParameter objects
param: headerAttributes [ Properties - in ]
The attributes that are part of the SOAP header (e.g.
authentication headers)
param: encodingStyleURI [ String - in ]
The encoding of the parameters
Creates a request object that can be used to send a
request over SOAP.
@return A SOAP request object that is used to invoke
the request
Type: public abstract «interface» Interface
Package: soap
Creates an empty parameter object that can later be
filled in by using its set methods
param: name [ String - in ]
The key of the parameter
param: type [ Class - in ]
The Java type of the parameter
param: value [ Object - in ]
The value of the parameter
param: encodingStyleURI [ String - in ]
The encoding of the value
A request interface that can be used to send a request over SOAP.
Creates a parameter object that can be provided in the
createRequestObject method
SOAPRequest Interfaces
Method Type Notes
getTargetObjectURI
()
public: String
setTargetObjectURI
(String)
public: void param: targetObjectURI [ String - in ]
getMethodName () public: String
setMethodName
(String)
public: void param: methodName [ String - in ]
'#%$#%'$$5 (,

) 46 8 " 9 2 6
Method Type Notes
getParams () public: Vector
setParams (Vector) public: void param: params [ Vector - in ]
getHeaderAttributes public:
()
Properties
setHeaderAttributes
(Properties)
public: void param: attr [ Properties - in ]
getEncodingStyle () public: String
setEncodingStyle
(String)
public: void param: encodingStyle [ String - in ]
invoke (URL, String) public: param: url [ URL - in ]
SOAPRespons The URL of the remote server
e
param: SOAPActionURI [ String - in ]
The action to be called at the specified URL
Type: public abstract «interface» Interface
Package: soap
Invokes the request. If there were problems
connecting to the remote server or if the
ConnectionManager decided to abort the request due
to low priority this method will throw a
SOAPException. If there was a problem while
invoking the method on the remote server this method
will return a fault encapsulated in a SOAPResponse
object.
@return A response object that encapsulates either the
return value of the remote method or a fault
representing a remote error
throws = 'SOAPException'
An interface representing a parameter for a method invocation.
SOAPParameter Interfaces
Method Type Notes
setName (String) public: void param: name [ String - in ]
getName () public: String
setType (Class) public: void param: type [ Class - in ]
getType () public: Class
setValue (Object) public: void param: value [ Object - in ]
getValue () public: Object
'#%$#%'$$5 ((

) 46 8 " 9 2 6
Method Type Notes
setEncodingStyleURI
(String)
public: void param: encodingStyleURI [ String - in ]
public: String
getEncodingStyleUR
I ()
34
Type: public Class
Implements: Exception.
Package: soap
An exception thrown by the invoke method of the SOAPRequest to indicate a
connection error.
SOAPException Attributes
Attribute Type Notes
embeddedThr private :
Throwable
SOAPException Methods
Method Type Notes
SOAPException () public:
SOAPException public: param: reason [ String - in ]
(String)
SOAPException
(String, Throwable)
public: param: reason [ String - in ]
param: cause [ Throwable - in ]
SOAPException
(Throwable)
public: param: cause [ Throwable - in ]
getCause () public:
Throwable
getMessage () public: String
34
Type: public Class
Extends: SOAPException.
Status: Proposed. Version 1.0. Phase 1.0.
Package: soap
9 B 6 ! 78 " 49 1 F
" F I ! 6 8
7 .6 8" /J/
'#%$#%'$$5 (5

'
Type: public abstract «interface» Interface
Package: soap
) 46 8 " 9 2 6
A fault object represents an error in the remote invocation of the Web service method.
SOAPFaultMessage Interfaces
Method Type Notes
getFaultCode () public: String Returns the fault code of the fault (the possible fault
codes are defined in the SOAP specification).
getFaultString () public: String A user-friendly readable string describing the fault.
Type: public abstract «interface» Interface
Package: soap
An interface representing the remote answer of a request invocation. It contains either
the return value of the remote method or a fault indicating an error during the remote
invocation.
SOAPResponse Interfaces
Method Type Notes
getReturnValue () public: The return value of the remote method or null if the
SOAPParamet
er
response encapsulates a fault.
faultReturned () public:
boolean
True if the response encapsulates a fault.
getFault () public: Returns a fault object if the response encapsulates a fault
SOAPFaultMe
ssage
or null if not.
Type: public abstract «interface» Interface
Package: adapter
Represents a management interface for the native network adapters. MAY be used by
the ConnectionManager to check the connectivity and to connect to the network using
a specific network adapter as opposed to automatically using the default one by the
Operating System when a socket is opened by the JVM.
AdapterManager Interfaces
Method Type Notes
'#%$#%'$$5 (-

) 46 8 " 9 2 6
Method Type Notes
connect (String) public: void param: adapterType [ String - in ]
connect () public: void
disconnect () public: void
isConnected () public:
boolean
listAdapterTypes () public:
Enumeration
connectedAdapterTy
pe ()
0 $ 3$
public: String
throws Exception
throws Exception
throws Exception
Type: public abstract «interface» Interface
Package: adapter
An event indicating the presence or absence of connectivity.
ConnectivityEvent Attributes
Attribute Type Notes
CONNECTED public static :
int
Initial Value: 0;
DISCONNECTED public static :
int
Initial Value: 1;
ConnectivityEvent Interfaces
Method Type Notes
getEventType () public: int
getAdapterType () public: String
0 $ 1
Type: public abstract «interface» Interface
Package: adapter
A listener for connectivity.
ConnectivityListener Interfaces
'#%$#%'$$5 (>

) 46 8 " 9 2 6
Method Type Notes
connected
(ConnectivityEvent)
public: void param: event [ ConnectivityEvent - in ]
6.5 Positioning
6.5.1 Introduction
9 "" 6 6
"" 7 ! 66 6 78 6
/ ) ! "" A
B"6 7 ! 3 66 Q7 !
8 " Y 7 G 66 Q7 ! 3 66 !
! 8 ! 83 66 /
) 8 6 6 ! ! 8
6 6 66 /
) 7 "6 7 ! 7
8 " I J 7 6 6 " /
6.5.2 Interfaces
) 7 / 9 66 9K
F 6 9K
78 "6 " : 4
1 8/
cd Positioning
«interface»
org.gstproject.os.position.PositionService
+ getPosition() : org.osgi.util.position.Position
provides
«interface»
org.osgi.util.position.Position
provides
Figure 14 Class Diagram for Positioning
«interface»
org.gstproject.os.position.PositionListener
+ positionChanged(org.osgi.position.Position) : void
9 B6 " 7 ) 7

) 46 8 " 9 2 6
2 = " " 7 " !
" " /
2 6 ) 6 " " 7
/
2 . O ) INJ " 6 "
G H I "" 7.6 J 2 .
I C#D . . C,DJ/
3 "" B6 8 ! ! 7
7 /
'#%$#%'$$5 5$ , 8 " I 8 "
,J/
! 4 2 6 !
7 7 7 / ) 4 6 4
7 / " 87 8 ) !
7 ) ! 66 /
= E " 8
/ 2 7 7
8
4

) 46 8 " 9 2 6
76 ) ! A / / 6 83 3
/
) 86 " 7 "6 /
) ! " 7 7 6 I " "6
J ! ! 8 7
8 "6 /
: 6 / 1 7
! ! " ! *
V I % 2J S$
3 8 ! !
8 "/ ) 66 "6 B 8 6 7 6
8 ? F 8! 8/ 9
2 8 " / / 8 /
@ ; & ; ; ; 1
Type: public abstract «interface» Interface
Package: Positioning
Listener for position change events.
The listener MUST use the whiteboard model for registration - it MUST be registered
as a service in the OSGi service registry
Positioning::org.gstproject.os.position.PositionListener Interfaces
Method Type Notes
positionChanged
(org.osgi.position.P
osition)
public: void param: newPosition [ org.osgi.position.Position - in ]
@ ; & ; ; ; $
Type: public abstract «interface» Interface
Package: Positioning
Position service interface registered in the OSGi service registry.
Positioning::org.gstproject.os.position.PositionService Interfaces
Method Type Notes
getPosition () public:
org.osgi.util.p
osition.Positi
on
'#%$#%'$$5 5<

@ ; ; ; ;
Type: public abstract «interface» Interface
Package: Positioning
Existing OSGi interface - see OSGi R3
) 46 8 " 9 2 6
It MUST hold an exact, unique location, based on the WGS84 System (World
Geodetic System 1984).
Positioning::org.gstproject.os.position.Position Interfaces
Method Type Notes
getAltitude() public:
org.osgi.util.
Measurement
Returns the altitude of this position in meters.
getLatitude () public:
org.osgi.util.
Measurement
Returns the latitude of this position in radians.
getLongitude () public:
org.osgi.util.
Measurement
Returns the longitude of this position in radians.
getSpeed () public: Returns the ground speed of this position in meters
org.osgi.util.
Measurement
per second.
getTrack () public: Returns the track of this position in radians as a
org.osgi.util.
Measurement
compass heading.
6.6 Event mechanisms
6.6.1 Introduction
2 8 " " 8 " " 8 6 7
78 I 66 7 //J/ ) 7
7 8 " " ) 8 "/
) " 86 " " ) 78 *
• " " " A 2%4 /
• " " 3 3
• " " 3
• B 7 ! 66 3 8 "
6.6.2 Events coming from the vehicle environment
2 " " 6 %
" 6 I 2%4 " J /
'#%$#%'$$5 5'

6.6.3 Events coming from the Control Centre
) 46 8 " 9 2 6
8 : 4 9 ! 7 " " 3 8 " 78
3 3 " " 6 4 9 6
4 " ) 6 /
6.6.4 Events coming from a Service Centre
) " " 8 6 966
"" 6 "" ! 3 /
6 7 " 66 "
"" 66 4 ! 7 "
7 B 6 6 /
6.6.5 Events exchanged between service applications in the Client System
2 "" B 7 ! 66 1 8
! 4 ! 7 " 7 7 !/
) ! 7 6 4 " ! E 8
"6 " 6 8 F 78 6 / 2
" !
! 7 6 " ! 4
" ! / 7
) 8/
1 " 78 ! " ! / )
" 7 ! 7 6 8 "
"6 " / ) .7 6 87 !
78 " ! F "
7 /
'#%$#%'$$5 5#

) 46 8 " 9 2 6
Chapter 7 - INTERFACE TO VEHICLE SENSORS
7.1 Introduction
) 6 " 8 7 ! " 6 8
66 ! ! " 2=
6 "6 6 / ) 9 2 !
7 ! 66 66 6 F 8 6 7
! 66 3 .3 /
2 6 ! !*

) 46 8 " 9 2 6
4 ).7 " 8 7 39=.7 "
! " " 39= 4 ) 3
4 ).39= ! 8/ ) B"6 6 8
/
9 " " ! 78 * 2Z 6 6 8/
6 7 " ? " 6 7
"" " ! " 86
6 8 66 7 6
66 / " 7
7 " "" " 7 8 !
F 8" " 7 66 ! 7
66 6 7 " /
9 " 66 66 8 " 8 / / .
7 6 6 " 3 8 "/ )
6 " " 8 " 7 /
8 " 7 7 " 8 / / " 7
78 4 9 6 ! ! 7 ) /
) ! ! ) 3 3 I33J I J
" " 7 33 " "
/ / 78 " / ) " !
6 4 9 8 ! "
) 66 3 1 F 8 "/
7.3 High-Level requirements
) ! F " " 7 *
3

) 46 8 " 9 2 6
3

) 46 8 " 9 2 6
• 1 % $ @ ! "6
" 7 " 7
" 66
7.4.2 Use Cases
• 3 @2 6 7 6 7 8
" " .
! /
@
1 " : 3
8 3$ ' "@
) F " 6 12/ 2
" 6 /
$ 3$ "
) F " 6 12/ )
B / 9 " /
)
) " 6 " 66 6
/ ) " 7 7 9 " /
• 3 % @ " / 6
" " !
! ! 86 ! 7 6 .7 6
"6 /
@
1 " : 3
8 3$ ' "@
) F " 6 12/ 2
6 /
$ 3$ "
) F " 6 12/ )
B / 9 " /
)
) " 6 " 66 6
/
• 9 3 % # @ ) "
: 3
@
8 3$ ' "@
'#%$#%'$$5 5-

) 46 8 " 9 2 6
) F " 6 12/ 2
/
$ 3$ "
) F " 6 12/ )
B / 9 " /
)
) " 6 " 66 6
/ ) " 7 7 9 " /
• 34 0 @3 G6 " H
/ B"6 ) "6 93 @ 3 "6 /
: 3
@
8 3$ ' "@
) F " 6 12/ 2
"" 7 B "" 66 6 /
$ 3$ ",
) F " 6 12/ )
B / 9 " /
$ 3$ "*
) F " 6 12/ )
B 7 "" B 8 7
! 6 " / 9 " /
)
) " 6 " 66 6
/ ) " ! 66 "" 6 " /
• 3 @9 . "6 / / 6
8 "/ 9 ! "6 ) !
" " 7
66 " / ) ! "6 7
! 78 ) 6 6 /
@
: 2 " /
8 3$ ' "@
: " 6 7 8 " 7
6 12/ ) 9 " 6 7 6 !
" / ) 6 " 7 I ! " 6 G !
H /J
$ 3$ "
'#%$#%'$$5 5>

) 46 8 " 9 2 6
) ! " / ) 6 8
78 " 6 "6 / 8 " !
" 7 /
=
)
7.5 Entities
) ! ! " 7 7 / ) 6 #
7 8 / ) 8 G H 6 "
6 7 6 " ""
! 6 7 / G 9 " H ? "
6 66 6 " / ) G4
" ) H 7 ! 4 1, 6 C4 D !
6 ! 8 ? 4 9 "6 7
/ 2"6 " 6 . 9 " " "
7 4 ) / @ ) 66
4 9 "6 " /
'#%$#%'$$5 5&

1.5.1 Vehicle Admin components
) 46 8 " 9 2 6
Figure 3 – Entities for the interface to vehicle sensors
) " 8 ? 6 78 "
6 66 6 " /
) " 66 I !. . J 8
7 7 ! " 8 . ) . / )
6 7 " 66 " 7
/ 2 ! B 6 "
" 66 " 6 4 8/ 9
6 9 " 7 66 6 7
6 / ) 6 ! 8
7 I J ! /
'#%$#%'$$5 -$

) 46 8 " 9 2 6
2 ! " " 6 2 I J
6 / 2 6 7 6 8
6 7 8 9 2 "
7 F /
) " 8/ ) " 7
6 78 ) . 6 7 66 6 7.
/ 9 2 " 8 B 8 " ! 2
/ ) B " " 6 9 2 "6 "
" 8 8 B " " "6 4
9 " /
Vehicle Admin interface
9 " 86 66 /
9 " 66 " 8 F 6 6 /
9 86 . 9 2 7 78
3 = " / " "
6 6

CellProvider
) 46 8 " 9 2 6
) 3 " 6 ! 8
/ "6 " 3 6 7
6 " " 7 7 7
6 " I . G3 HJ . I 3 7 6 7
" J/
'#%$#%'$$5 -'

7.6 Class View
) 46 8 " 9 2 6
) ! 7 ! , " 7 ! 78
66 6 / 2 7 ! 6 .
7 ! (/ 8 "
"6 " "6 " . 6 /
Figure 4 – Class Diagramm Vehicle Admin Layer
7.6.1 Vehicle Admin layer class diagram
) ! 3 " 7 9 " 8 / )
! 8 "6 66 6 /
VehicleTreeNode
) ) = 6 / 2
6 6 I" . J ! Q 6 "
" "2 6 7 !
3 = IJ " /
9 " 6 7 6 9 2 F !
) = / " / 9
6 7 "6 " 6 7 " 66 6 B8
" ) = / ) 6 B8
6 B 6 "
'#%$#%'$$5 -#

) 46 8 " 9 2 6
) = / ) B ! 8 6 B8
86 8 6 9 "
"6 " 7 8 B " " 4
9 " / 2 9 " !
7 ! " 6 " 66 7 !
6 " 86 / ) 6 B8
" 6 " I 9 " B"6 J 7 B "
) = / ) B8. ) = $ "

VehicleAdmin
) 46 8 " 9 2 6
) 9 2 F !
12 /
@ 2 9 " "6 " 6 7 6
! "6 " ) = / / 2 !
" 7 " / 7 "6 "
8 7 ! 6 ) = "6 " !
"6 " 66 ! 66
9 2/
NodeValueListener
9 " " " 7 !
6 ! I 6

7.6.2 Data providers class diagram
CoreHandler
) 46 8 " 9 2 6
Figure 5: Class Diagramm Data Provider Layer
Data providers Entry point interface (OSGi service). Using the interface clients may
register listeners, request and send cells.
CellProvider
" 6 " 3 6
9 " ! B 3 IJ "
) = /The CellProvider module provides the access to the lowest
layers of the vehicle sensors interface. Modules implementing the CellProvider
interface are responsible for translating the specific vehicle data coming from a
vehicle bus into an abstract bus independent format (the “Cells”) and vice-versa (a
Cell object to a specific bus format).
) 6 " 7 2 3 "
F 3 /
'#%$#%'$$5 -5

) 46 8 " 9 2 6
'#%$#%'$$5 --

Cell Listener
) 46 8 " 9 2 6
) 6 / "
G 3 9 = 8H 6 7 8 6 "
! 3 8" 66 6
3 " / ) 6 7
8 8 F 6
8! "6 " 8
" 3 IJ " / )
! F B6 ! " 6 7839=
! 6 / 3 ! 7 6
7 6 " "

Cell
) 46 8 " 9 2 6
9 3 7 7 /
Data Cell
) 6 7 78" 9 2/ 2 6 8
/
Complex Cell
) " ! " / 9 B"6
" 6 / ) 6
/ 9 6 " " I 6 J
6 / 9 6 6 " 7
"6 7 6 6 7 8
/ 2 ! 7 "6 B
" 6 3 "6 B3 /
) "6 B / / " 6
"6 B 6 78 / 3 "6 B 78
" 78 B/
String Descriptor
Represents string status value. Such a status value could be the VIN, or registration
number of the vehicle.
Measurement
6 7 F " " 7 /
" 7 6 1# 4 6 /
9 ¢¡¤£¤¥§¦¤¨©¡¡ 7 " 6 " .
"6/ ) 6 7 " "
" " 8<

StateDataCell
) 46 8 " 9 2 6
! 6 / 2 9 2 !
" B ! "" 7 8 8 /
1 6 / ) 9 2 ! 4 47 7
" 3 /
State
7 7 F 3 / 7 6
7 3 6 " /
RemoteMethodCell
" 8
B " " 8/ @ " " 6
7 "6 7 9 2 F 1 " 3 / 2
" " 6 8
8 " 6 " / F " "
/
7.7 Sequence View
7.7.1 Get Status Element Value
2 9 2 F ) = "
9 " / 2 6 7
7 I J 6 / ) 3 = IJ
" / ) " 7 / 9 7
6 78 " 3 IJ/ 9 6 7 8
6 8 " " I B"6
3 J/
'#%$#%'$$5 >$

) 46 8 " 9 2 6
Figure 7: Sequence “Get Status Element Value”
'#%$#%'$$5 ><

) 46 8 " 9 2 6
7.7.2 Request Status Element Value Change Notification
2 F 9 2 F ) = "
9 " B " = 3 : / 2"6 "
66 6 " 7 6 /
7.7.3 Execute Status Command
Figure 8: Sequence “Status Value Notification”
2 9 2 F ) = "
9 " = "" ? ""
7 ! " "" 47 CD/ 4 ?
"" B " B = 3 "" !
"6 " " " 3 3
? /
'#%$#%'$$5 >'

) 46 8 " 9 2 6
Figure 9: Sequence “Execute Status Command”
'#%$#%'$$5 >#

7.7.4 Manage Status Elements
) 46 8 " 9 2 6
9 2 ! " " /
6 6 " ) 4 / )
9 " ! 8 6
6 / 2 6 B ) =
" ! / 9 " 6 B
9 " 6 6 6 I" @ J/
! 7 " 66
" 6 B " 3 =
7 ! 7 /
Figure 10: Sequence “Manage Status Elements”
'#%$#%'$$5 >,

7.8 Considered Solution alternatives
) 46 8 " 9 2 6
2 % 3 )3 '& ! ! % ! 4 "
2 7 9 " : 8
7 B6 8 4 9 ) 4 / ) 6 6
G H 7 !/
9 8 G 6 H 7 ! " "
7 7 7 / 2 " 6 8
8 6 7 6 / 2 6
" 6 / = ! " F G! ! 6
8H/ 6 8 7 B 7
7 / 9 ! ! 7 ! 8 6 8
8 8! 4 9 )O F "
8 6 " ! 7 " 66 / )
! F 6 4 9 ) 4 ) 6 6 8
/
3 6 8 4 9 4 ) ! 66 B .
" " 9 2 7 4 " !
7 " G H 8 : 6 / 86 9 2
6 . I " " 6 . 6 . /J/
4 9 ) 6 . 6 B87 ! 4 9 ) 4 9 2
66 6 9 2 8
8 " 66 "6 / 2 " 4 4 9 ) 6 6 8
B"6 3 " 4 4 9 ) 6 . " 66
7 ) 6 . " 8" 6
B 7 8 8/
8G H 7 6 /
2 ! ! 6 8 4 9 ) 6 !
6 7 " 6 . " ! !
! ! 6 " " 7
8 " 6 . " 7 6 ! G6 .
6 . H 4 9 ) 6 7 7 8
66 /
6 " 6 6 7 " 6 7 " " 4
) 8 86 66 6 7 " ! ! 9 2
8 4 4 9 )/ @8G! H " 6 "
6 7 6 / 2 6 7
3 7 4 4 9 ) 9 2/ ) 4 9 ) 9 2 "
6 B6 " 6 78 "6 4 " ! 7
6 6 " 6 ! ! ! /
" " G H 9 2 ! 784 4 9
) 7 " 8 : /
" 7 12 " 7 6 / 8
! / @8 ! E" 4 4 9 ) 9 2
7 8 7 " 8 : 6
7 " 6 /) 8 : 4 49 ) !
7 8 4 9 ) 6 /
'#%$#%'$$5 >(

) 46 8 " 9 2 6
3 " 9 " 8 !
! 66 ! 6 " 7 "
! 8 7 8GB6 7 H 7 8 : 78 "6 " "
4 9 ) 6 ! ! 87 6 B87 ! 4 9 )
" ! 8 4 9
) 6 . / ) ! 6 ! ! 8* )
6 78 6 / 4 ? 78
9 " / B6 ! 78 4 9 )
6 /
) !3 % # "
4 5* 3 "" 3 " " " 7 / 4
" 87 " G 8 H "
7 " G 9 " IJ/ IJH/ )
" G 7 H " " 7
6 " F " B 7 / )
7 6 ! !
7 / ) " "" 7 / )
"" " 7 !
6 " ! ! ! / 2"" 7 8
66 6 7 8
! ! 6 " " I
J/ 7 ! 8 ! 6 7 "
8 7 /
7.9 Vehicle Tree
9 66 )3 78
9 " / ) 7 ! 6
/
) ! " 6 *
2 8* /% % 2 8
9 " * /% % 9 "
) 8 7 6 " 7
2= 86 " /
) " 7 6 8 " " 6
7 . G % H 7 /
) 7 6 ! !
6 " 7 B
" /
'#%$#%'$$5 >5

) 46 8 " 9 2 6
Figure 11: Grafical representation of the vehicle subtree
) 7 6 )/ ) 2 8
3 7 ! " 8 )
66 3 1 F /
7.9.1 UNITS
6 8 7 2 I8 \" 2 E ]J 6 /
) 2 - 7 "7 / ) 7 - *
2 #
: "
) "
$
L ""
9"6 9
) "6 L L
9" 7 "
: " 8 3
9 7 " 7 86 /
'#%$#%'$$5 >-

7.9.2 Vehicle Tree Description
) 46 8 " 9 2 6
) 6 " 7 78 66
7 / ! 7 !
6 /
) 6 6 86
7 86 6 8 /
;:% :%
) 6 "
7 / 2 8/
%
Figure 12: VehicleIdentity Subtree
% #
1
0
1
%
8
0
'#%$#%'$$5 >>

;:$ :% :% #
1 6 "7 /
Request:
Cell Type: StringDecsriptor
Acess Type: getString()
Reply:
Data Type: 17 character string value
;:$ :% :
) 6 /
) 46 8 " 9 2 6
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: =(0,9999); =(1,12) =(1,31)
Example: 2005-09-30
;:$ :% :
) 7 " " /
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: 32 character max
;:$ :% : %
6 " " /
Request:
Cell Type: SringDescriptor
Acess Type: getString()
Reply:
Data Type: 32 character max
;:$ :% : 8
) 7 7 8 86 /
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: 32 character max
Occurrence: One
Scope: Static
;:$ :% : 0
'#%$#%'$$5 >&

1 6 8 86 /
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: 32 character max
;:$ :% :1
) 46 8 " 9 2 6
) 7 78 2/ )
7 78 ! . ? 2 4 5#&/
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: 2 char code
en = English it = Italien sv = Swedish
es = Spanish de = German pt = Portuguese
fr = French nl = Netherlands el = Greek
ru = Russian ja = Japanese zh = Chinese
ko = Korean
;:$ :% :0
7 /
Request:
Cell Type: SringDescriptor
Acess Type: getString()
Reply:
Data Type: 16 character max
;:$ :% :1
) 6 /
Request:
Cell Type: SringDescriptor
Acess Type: getString()
Reply:
Data Type: 16 character max
;:$ :% :
) "7 /
Request:
'#%$#%'$$5 &$

Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
;:$ :% :6 "
) "7 6 ! ! ! /
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
;:$ :% :
) 7 "7 6 ! /
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
;:$ :%
) 46 8 " 9 2 6
'#%$#%'$$5 &<

) 6 8 " /
%
Figure 13: VehicleStatus Subtree
;:$ :% :
) 46 8 " 9 2 6
1
6
0
38
00
) 6 6 " /
0
'#%$#%'$$5 &'

;:$ :% : :0
) 46 8 " 9 2 6
7 6 " ! 6 /
Request:
Cell Type: DataCell
Acess Type: getPhysicalValue()
Reply:
Data Type: double
Unit: m/s
;:$ :% : :
1 6 ! 6 " /
Request:
Cell Type: DataCell
Acess Type: getPhysicalValue()
Reply:
Data Type: double
Unit: m/s
;:$ :% :1
This node is the parent of all light sensor data.
'#%$#%'$$5 &#

1
;:$ :% :1 : 7 1
) 7 6
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: all off
1: left side only on
2: right side only on
3: all on
;:$ :% :1 :E
) 7
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
;:$ :% :1 :E 8
) 7 7 "
E
Request:
Cell Type: StateDataCell
Acess Type: getValue()
7 1
E 8
' 1
8 7 1
E = 1
1 0
) 46 8 " 9 2 6
'#%$#%'$$5 &,

Reply:
Data Type: int
Code : 0: off
1: on
;:$ :% :1 :' 1
1 6 :
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: all off
1: only front foglight on
2: only rear fog light on
3: all on
;:$ :% :1 :8 7 1
) 7 7
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
;:$ :% :1 :E = 1
) 7 ?
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
;:$ :% :1 :1 0
) 46 8 " 9 2 6
This node returns information, if the driving light should be
switched on because of the environmental conditions.
Request:
Cell Type: ComplexCell
Acess Type: getValue()
'#%$#%'$$5 &(

Reply:
Data Type: StateDataCell []
StateDataCell [0] = Dawn
Code: 0: no
1: yes
StateDataCell [1] = Darkness
Coede: 0: no
1: yes
StateDataCell [2] = Rainfall
Code: 0: no
1: yes
StateDataCell [3] = Tunnel
Code: 0: no
1: yes
StateDataCell [4] = Underground Parking
Code: 0: no
1: yes
StateDataCell [5] = High Speed
Code: 0: no
1: yes
;:$ :% :6
) 46 8 " 9 2 6
This node is the parent of all wiper sensor data.
6
' 6
;:$ :% :6 :' 6
Returns front wiper status.
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: intervall/automatic (rain sensor activ)
6
' 6
'#%$#%'$$5 &5

2: normal
3: fast
;:$ :% :6 : 6
Returns rear wiper status.
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
2: not equipped
;:$ :% :6 :' 6
Returns the relativ value of front wiper speed.
) 46 8 " 9 2 6
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Value: 0..255;
0 = wipers are not moving
255 = wipers are moving as fast as possible
;:$ :% :
Returns the relativ rain intencity in percent (%).
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0…100
Unit : %
;:$ :% :
'#%$#%'$$5 &-

) 46 8 " 9 2 6
) B "6 L I$ 3 V '-#

0
;:$ :% :0 :0
) 6 /
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: no crash detected
1: front crash
2: side crash left
3: side crash right
4: rear crash
;:$ :% :0 : 9
1 " F 7/
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Range: 0…254
0: no squib triggered
;:$ :% :0 :0 $
) 8 ! ! 7
/
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: no crash detected
0
0 $
$
) 46 8 " 9 2 6
9
'#%$#%'$$5 &&

) 46 8 " 9 2 6
1-4: crash severity (1: easy; 4: serious)
;:$ :% :0 : $
) . 7 /
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: no deploy
1: release roll-over bar
;:$ :% :
) 6 " 7 68 /
;:$ :% : :'
1 6 8 " /
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..1]
StateDataCell [0] = Passenger
Code: 0: no
1: yes
2: not available
StateDataCell [1] = MiddleFront
Code: 0: no
1: yes
2: not available
'
"
' "
' "
"
0 40
0 40
0 40
0 40
0 40
'#%$#%'$$5

;:$ :% : : "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
StateDataCell [0] = SecondRowLeft
Code: 0: no
1: yes
2: not available
StateDataCell [1] = SecondRowMiddle
Code: 0: no
1: yes
2: not available
StateDataCell [2] = SecondRowRight
Code: 0: no
1: yes
2: not available
;:$ :% : : "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
StateDataCell [0] = ThirdRowLeft
Code: 0: no
1: yes
2: not available
StateDataCell [1] = ThirdRowMiddle
Code: 0: no
1: yes
2: not available
StateDataCell [2] = ThirdRowRight
) 46 8 " 9 2 6
'#%$#%'$$5

Code: 0: no
1: yes
2: not available
;:$ :% : :' "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
StateDataCell [0] = ForthRowLeft
Code: 0: no
1: yes
2: not available
StateDataCell [1] = ForthRowMiddle
Code: 0: no
1: yes
2: not available
StateDataCell [2] = ForthRowRight
Code: 0: no
1: yes
2: not available
;:$ :% : :' "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
) 46 8 " 9 2 6
StateDataCell [0] = FifthRowLeft
Coede: 0: no
1: yes
2: not available - wo braucht man das ??
StateDataCell [1] = FifthRowMiddle
Coede: 0: no
1: yes
2: not available
StateDataCell [2] = FifthRowRight
Code: 0: no
1: yes
2: not available
;:$ :% : 8
8
'
"
"
'#%$#%'$$5 ' "

;:$ :% : 8 :'
) 46 8 " 9 2 6
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..1]
StateDataCell [0] = Passenger
Code: 0: no
1: yes
2: not available - wo braucht man das ??
StateDataCell [1] = MiddleFront
Code: 0: no
1: yes
2: not available
;:$ :% : 8 : "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
StateDataCell [0] = SecondRowLeft
Code: 0: no
1: yes
2: not available
StateDataCell [1] = SecondRowMiddle
Code: 0: no
1: yes
2: not available
StateDataCell [2] = SecondRowRight
Code: 0: no
1: yes
2: not available
;:$ :% : 8 : "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
StateDataCell [0] = ThirdRowLeft
Code: 0: no
1: yes
2: not available
StateDataCell [1] = ThirdRowMiddle
Code: 0: no
'#%$#%'$$5

1: yes
2: not available
StateDataCell [2] = ThirdRowRight
Code: 0: no
1: yes
2: not available
;:$ :% : 8 :' "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
StateDataCell [0] = ForthRowLeft
Code: 0: no
1: yes
2: not available
StateDataCell [1] = ForthRowMiddle
Code: 0: no
1: yes
2: not available
StateDataCell [2] = ForthRowRight
Code: 0: no
1: yes
2: not available
;:$ :% : 8 :' "
Request:
Cell Type: ComplexCell
Acess Type: getValue()
Reply:
Data Type: StateDataCell [0..2]
) 46 8 " 9 2 6
StateDataCell [0] = FifthRowLeft
Code: 0: no
1: yes
2: not available - wo braucht man das ??
StateDataCell [1] = FifthRowMiddle
Code: 0: no
1: yes
2: not available
StateDataCell [2] = FifthRowRight
Code: 0: no
1: yes
2: not available
;:$ :% :38
This node is the parent of all Electronic Brake Management (EBM)
Systems
'#%$#%'$$5

38
;:$ :% :38 : 8
) 9 . @ 8 " /
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
2: engaged
3: malfunction
;:$ :% :38 : 0
) 6 9 . 3 8 "
3
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
2: engaged
3: malfunction
;:$ :% :38 :3
) 46 8 " 9 2 6
) 6 7 8 8 " I@ * 3 @ *
/J
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
8
0
E8
3
'#%$#%'$$5

Data Type: int
Code : 0: off
1: on
2: engaged
3: malfunction
;:$ :% :38 :E8
) 6 8 @ 8 "
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
2: engaged
3: malfunction
;:$ :% :38 :3
) 46 8 " 9 2 6
) 6 ) F 3 I 1J
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: off
1: on
2: engaged
3: malfunction
;:$ :% : 00
00
%
'#%$#%'$$5

;:$ :% : 00:
) /
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: ACC not operable
1: radar on
2: radar off
;:$ :% : 00:
) 6 9 3 3 "
Request:
Cell Type: StateDataCell
Acess Type: getValue()
Reply:
Data Type: int
Code : 0: passiv
1: stand by
2: normal
3: increased dynamic
4: active brake pressure
5: driver passed over
;:$ :% : 00: %
) 46 8 " 9 2 6
) 6 7 "
Request:
Cell Type: DataCell
Acess Type: getPhysicalValue()
Reply:
Data Type: double
Range: 1…250
Unit: m
;:$ :% :# $
# $
E
E E =
0
0 40
'#%$#%'$$5

) 46 8 " 9 2 6
;:$ :% :# $ :
Die Nachricht enthält die durch GPS übermittelte absolute horizontale
und vertikale Position des Fahrzeugs.
Request:
Cell Type: ComplexCell
Acess Type: getPhysicalValue()
Reply:
Data Type: DataCell [0..2]
DataCell [0] = PositionLongitude
Range: -180 degree to 180 degree
DataCell [1] = PositionLatitude
Range: -90 degree to 90 degree
DataCell [2] = StatusHeight
Range: -32767 m …32767 m
;:$ :% :# $ :E
Returns the height of the vehicle in m.
Request:
Cell Type: DataCell
Acess Type: getPhysicalValue()
Reply:
Data Type: double
Range: 0..360
Unit: degrees
;:$ :% :# $ :E E =
Returns the absolute direction of the vehicle in degrees.
Request:
Cell Type: DataCell
Acess Type: getPhysicalValue()
Reply:
Data Type: double
Range: -32767…32766
Unit: m
;:$ :% :# $ :0
) 8 ! 78
Request:
'#%$#%'$$5

Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: 32 character max
;:$ :% :
) 46 8 " 9 2 6
This node returns the time acording to “Coordinated Universal Time”
UTC. It´s
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: =(0,23); =(0,59); =(0,59)
Example: 23:20:19
;:$ :% :
) 8 78
Request:
Cell Type: StringDescriptor
Acess Type: getString()
Reply:
Data Type: =(0,9999) =(1,12); =(1,31)
Example: 1995-04-02
;:$ :% :
) "6 " "
Request:
Cell Type: DataCell
Acess Type: getPhysicalValue()
Reply:
Data Type: double
Unit: km
C4 2D 4 6 6*%%!!!/ / /
'#%$#%'$$5

) 46 8 " 9 2 6
'#%$#%'$$5

) 46 8 " 9 2 6
Chapter 8 - NOMADIC DEVICE INTEGRATION
8.1 Disclaimer
= " 2 ) 6 7
"6 6 7 7 6" 6 6
7 " / 9 F 46 8 " !
6 "6 " 7 "6 "
6 , ! 6 /
8.2 Introduction
) 6 = " 2
/ = " 2 " "
9 7 6 "7 8 " 8 78
4 F 6" I4 J . 8 "/ 2
B ) "7 8 " 6 ) " 3 )3
78C#D/
) = " 2 ! " 6 / 9 6
= " 7 = " 2 / ) = "
! 8 7 6 )3 / ) = "
! 8 ) "6 ! "/
@ 6 8 . ! 7 6 ! !
" "" ! /

) 46 8 " 9 2 6
8.4 Services and Service Repository Synchronization
@ ! B 8
G H B = " 2 /
2 B = " 2 6 7 8
! 78 )3 " / 9 B"6
7 " # E F 6" /
9 " ! 6 / ) 6 " 6
" / 2 B"6 # 6 8 = "
7 # 6 8 6 " I # "J
)3 6 6 " /
) 7 ! 6 8 "6 "
6 8 "6 / " ! ! ! 6
"6 " = " # 3
#3 6 )3 02 3 3 /
9 = 2 6 ) /
2 " 7 = ) 6 78 2 7 / ) 7
6 " 7 = ) / ) 2
" 6 /
2 7 ! =
) / ! = ) /
• 4 )3 = ! 7
= " /
• 4 = " ) ! 7
)3 /
@ 2 7 8 8 ? ! G !H 7
7 6 78 6 /
9 " 66 7 78 B ! 7
8 " 8 ? = ) 83 ! "
6 / ) G)! . 8 8 H
8 ? 86 7 78 8 : 8 ?

8.5.1 Initial Connect
) 46 8 " 9 2 6
) 3 7 B 78 = "
! 8/ ) "7 8 " I J . 6
6 6 / ) 6 6 " 7 ! = "
7 " 7 = " ) 3 "6 = "
2 7 /
) 3 ? 78 ! 7 * I
3 %3 7 ! 6 78 #(J
0
02 '3 $ ) 7 ? .
6 = " ! 8/ )
B
B6 " 7
" " " 7
" ! 8 = "
2 2 /
# '3 $ 8 6
= " /
# '3 $ " 86 78
)3 9 7 7
= " /
TCU Front End Processor Activation
9 B6 = " ! 8" 7
) 46 8 " B " / 2
= " ! 8 "6 7 ! 8 7 78 ! "
966 1 " " 2 /
) 6 78 ! )3 ! 78
8 6 / 4 )3 7
B " 2 = " 86 /
! B 8 B " "6 "6 "
6 6 /
'#%$#%'$$5

) 46 8 " 9 2 6
Figure 18 TCU FEP Activation
State Diagram
) " ! = " ! 86
! 8 ! / = ! @
? B " / 6 "
B6 6 8" ! "/
Figure 19 TCU FEP Activation
Nomadic Device Front End Processor Activation
" )3 = " 2 =
! ! /
'#%$#%'$$5

) 46 8 " 9 2 6
Figure 20 Nomadic Device FEP Activation
) ! " 6 6 6 = "
7 /
Figure 21 Nomadic Device FEP Activation
Starting the Nomadic Device Front End Processor makes the FEP discoverable by the
Embedded Gateway.
The ND FEP Discovery Collaboration
) 7 8 ! *

) 46 8 " 9 2 6
'/ 9 = " " "7
= " = " 2 /
#/ 2 6 ! = " 66
! "7 8 " = " ! 8
= " /
,/ 8 = " ! 8 = " 2 78"
8 : 6 $ I " J " 7 78 4 9
= 2 C#(D/
) ! F " 6 " 6
/
Figure 22 Initial Connect Sequence Diagram
) "6 ! F " 8
"6 ! ! = " ! 8 = " 2
'#%$#%'$$5

) 46 8 " 9 2 6
/ 9 F = " ! )3 6 2
F /
) "6 ! *
0 '
02 ' 3 ) 7
= " ! 8/ ) "6 !
"" ! = " 7
6 6 = " ! 8 !
= " /
02 0 ) "6 8 6 = "
! 8 7 6 ""
78 = " ! 8/ )
7 @ "6 "
/
# 0 = " 3 " A " 8
" )3 3 " 7
= " /
# ' 3
# '3 J
' @
) = " " )3
6 @ = " / 9
! ! = 7
" 6 78 )3 /
) 2 = " = "
6 / 2 )3 2
6 8/ " !/
) # $*'"
# '3 $
( ) # 32 ! (
4 )3 6 7 G = " H
8 6 2 / 9 F F "
'' ! 6 ! " 6 / )3 2
! 7 8 = " / = B )3 2
! ) "6 "
/ 2 7 " /
2 ! (
) # " # % !
# ! 3'- "
% ( / 21 0
"
) ! " ! 8 /
'#%$#%'$$5

Class View
) 46 8 " 9 2 6
Figure 23 Nomadic Device FEP discovery
) 3 " 8 6 8 ! 2 7
"6 " 78 ) "6 = " 2 "6 " /
02
) 7 " ! 7 7
" 7 ! "6 *
• 9 )3 A ) "6 ! 8*
o 3 7 8 = " /
o 2 8 "
o 3 = "
o 3 $ P
o " = "
• 9 " 6 6
'#%$#%'$$5

) 46 8 " 9 2 6
• 9 9 78 B " 86
? 6
• 9 6 ^$ " "6 6 6 "
" 7 . .7 6 ^$ 8 : " /
• 9 4@ N C''DC'-D "6 ! !
6 ^$ " 4@ N 6 / ) ! "
! = "
7 *
Figure 24 Initial Connect Nomadic Device Classes
) 6 6 ^$ " !
= " ! 7 " )3 / ) 7 6
" " / ) 6 " 78 8
" ! " " ! ^$
" / ) " 8 8 = "
"6 " / ) * = " 9 2 2 "6 " "
7 F "6 " "68/
'#%$#%'$$5

) 46 8 " 9 2 6
" " ^$ " 7
6 6 6 6 /
) " )3 7 ! *
Figure 25 Initial Connect TCU Class Diagram
) 3 " = " 2 3
7 / @ ! ! 8 / 2 )3
3 78 I6 ^$J "
= " / 4 6 " 3 6
"6 " ! "" " /
% 5-67 ' % 89 % # ! : ' '
! " 32 ( 0"&
2 % !( ) # 2 # ! (
) # ! ' %89 % # : ';
'#%$#%'$$5

8.5.2 Authentication and Authorization
) 46 8 " 9 2 6
4 6 "6 8 "" B 7 !
)3 3 = " / ) 6 ^$
" = " 6 /
) ! 6 ^$ "
! )3 /
) 6 2 7 "6 4 9 8 : 8
6 6 '( C'>D/ ) !
! *
sd Authentication message flow.OS
ND Front End
Processor
Setup
Package #0, Alert form TCU FEP
Package #1:Credentials and Device
information
Package #2: Acknowledge message
and Server Credentials including list
of authorized services
Management
Package #3: Client response to server
authentication, contains list of authorized
services
Package #n: Vehicle Status and
eCall services setup
Figure 26 Setup and Management Phase
9 7 78C'>D 66 6 ! 6*
TCU Front End
Processor

) 46 8 " 9 2 6
@ 6 2 "68 ! 7 78 C'>D 6 6 >
9 / ) "68! 6 7 3 2 6
/ " = " 2
/ ) )3 2 6 ! '

sd ND Transmit Credentials ot TCU
) 46 8 " 9 2 6
TCU Nomadic Dev ice TCU
TCU Connection
Manager
(from Initial Connect)
Package #0
ND FEP Serv er ND FEP Client TCU FEP Serv er
Instantantiate
Prepare Package #1 message
Send Package#1
9 6 ^$ " " )3 = " 4 :
3 "6 / ) "6 6 6 ^< "
78" 8 :%4@ N 6 " 66 6
3 )3 /
) " ! 78 ', ! B ! *
'#%$#%'$$5

ud ND Transmit credentials to TCU
SyncML Parser
SyncML
Formatter
«interface»
intf::Authenticator
+ Authenticate(char[]) : int
+ RetrieveAuthorizedServices(int) : ServiceInfo[]
+ CreateCredentials() : char[]
NDI Dev ice
Management Tree
TCU Verify ND Credentials
Use
«interface»
intf::FepServer
+ Accept() : byte[]
1..*
Instantiates
«interface»
intf::FepClient
+ FormatRequestMessage() : byte[]
+ SendMessage(SyncMLMessage) : void
+ ParseResponseMessage() : SyncMLMessage
1
) 46 8 " 9 2 6
1 0..*
«interface»
helpers::SyncMLMessage
«thread»
intf::MessageThread
- fepClient: FepClient
- SyncMLMessage:
+ «property get» getfepClient() : FepClient
+ «property set» setfepClient(FepClient) : void
+ HandleMessage(byte[]) : void
Needs to be
detailed
'#%$#%'$$5
86 7 3 /

id TCU Authentication and Authorization
«interface»
intf::Sessions
- session: Session
+ AddSession(int, String) : long
+ RemoveSession(String) : boolean
+ RetrieveSession(long) : Session
intf::Session
- SessionId: long
- SourceURL: String
- DeviceId: int
+ «property get» getDeviceId() : int
+ «property get» getSourceURL() : String
+ «property set» setDeviceId(int) : void
+ «property set» setSourceURL(String) : void
+ «property get» getSessionId() : long
1
Contains
0..*
1
Uses
) 46 8 " 9 2 6
1
Uses
SyncML Parser
Triggers
FEP Serv er FEP Client
«interface»
intf::Authenticator
NDI Dev ice
Management Tree
SyncML
Formatter
+ Authenticate(char[]) : int
+ CreateCredentials() : char[]
+ RetrieveAuthorizedServices(int) : ServiceInfo[]
Also contains the
Session
information on a
per Nomadic
device basis.
'#%$#%'$$5

) 46 8 " 9 2 6
= " / 2 B 6 = " F #
"6 ^< /
= " 2 ! 6 7 78C'>D 6
> 6 '(/ 9 2 66 7 7 ( I

) 46 8 " 9 2 6
• 2 2 # /
I F " '>J
"68 87 6
/
• ) = " E 11 # ^< " !
/ 2 78 )3 )3
2 6 ! ,$< 6 6 2
#
/
TCU synchronize list of available services with ND
^' " 78 )3 7
? = / ) "
! 7 " 78 " 4 9 8 :
" ) I )J 78 6 8" / )
7 = " 2
F " 7 / 6 8" 6
6 " " 6 /
< % % )3 # ! !
! # ! ! !
% 0 ) ' # %
2 # ! # "
TCU Submit Credentials to Nomadic Device
9 = " )3 2 6 !
6 ^' " ! 8 )3
! = " /
) )3 2 6 @ 5, ( 86
/
4 6 ^' " )3 = " 2 !
! 8 6 " 6 *
• 2 " = " 2 G= 8
3 )3 H 7 /
• 2 " = " 7 ""
78 ,**/" / )
E 21 # 6 " _
ND Verify Credentials of TCU
) 7 8 6 )3 / )3
78 ^' " )3 B6
6 6 6 / ) = 6 6 B
" ) / ) 6
3 The reason for this rigid termination of the setup process if the credentials are not send or not
recognized by the TCU is explained by the specific situation of a driver switching on the engine and
driving the car. The setup process takes place when the driver is probably on the road and he or she
should not be disturbed by this setup phase. In other words, if the setup fails this Nomadic Device
Integration remains inactive. The user could eventually be warned about this situation by means of an
orally warning or a message on the phone.
'#%$#%'$$5

) 46 8 " 9 2 6
)3 / 2 = 2
6 ,$< " / ) " 2 7 6
6 6 7 )3 = " /
2 6 =
? " )/
) 78" = " " ) / 4
= 2 ? )3
" ) " ! 6 '

) 46 8 " 9 2 6
Figure 29 Service Info Object
) N : " 7 "6 " 6 /
8.5.3 End Point Tree Synchronization
9 B6 78 7 6 6 6 6
"6 ! 8 ? = ) !
! ! 78 9 "6 ? / )
8 ? 6 ! 6 6 78 4 9 8 :
8

) 6 *
) 46 8 " 9 2 6
Figure 30 Service Synchronization
• 4@ N 6 6 C'-D
• 4 9 8 : 8 C'>D 8 : 6 6 C

Two-Way Sync
) 46 8 " 9 2 6
= 8 78
7 ! 6 78
= " 3 /
) 86 8 ? 2 9 6
7 8 7 ? / ) 7 )
"6 ! ! 8 8 ? 7 "6 ! C'>D 6

Slow-Sync
) 46 8 " 9 2 6
2 " 8 8 ? / 2 !. 8
"6 7 / 9 !. 8 B
7 46 8 F 7 B
7 ! = " )3 /
8.5.4 Vehicle Status Service Discovery and Initialization
4 7 )3 = )3
8 ? ! 7 / ) 3

0
Trigger Vehicle Status Discovery
) F " ! 6 /
) 46 8 " 9 2 6
" " 8
4 '

sd Trigger Vehicle Status Discovery
Vehicle Status
Serv er
) 46 8 " 9 2 6
ND Dev ice
Management
Tree
getService(ServiceDescription)
Instantiate Service
Start Service
Service Code
ND FEP Serv er TCU FEP Client TCU Management
Tree
Prepare Vehicle Status Server
Status respons
In case of a failure
at this point the TCU
FEP Client MUST
abort the setup
process and the
system needs to go
back in its initial
polling mode.
Connect
Figure 32 Vehicle Status Discovery
''%$#%'$$5

) 3 " 7 ! *
c d TC U V e h ic le S ta tu s D is c o v e r y
« i n te rfa c e »
in tf::S e r v e r L is te n e r
+ o n D i sc o v e ry E v e n t() : v o i d
A u th e n tic a tio n
a n d A u th o riz a tio n :
:S yn c M L
F o r m a tte r
U se s
A u th e n tic a tio n
a n d A u th o r iz a tio n :
:O b e x P a rs e r
) 46 8 " 9 2 6
U se s
A u th e n tic a tio n
a n d A u th o r iz a tio n :
:S yn c M L P a r s e r
U se s
« i n te rfa c e »
i n tf::F e p C l i e n t
- se rv i c e R e p o si to ry : S e rv i c e R e p o si to ry
- sy n c M L M e ssa g e : S y n c M L M e ssa g e
+ « p ro p e rty g e t» g e ts y n c M L M e s s a g e () : S y n c M L M e s s a g e
+ o n D i s c o v e ry E v e n t() : v o i d
+ « p ro p e rty s e t» s e ts y n c M L M e s s a g e (S y n c M L M e s s a g e ) : v o i d
+ S e n d (b y te []) : v o i d
+ fo rma tO b e x M e s s a g e (b y te []) : S tri n g
+ p a rs e O b e x M e s s a g e (b y te []) : b y te []
+ fo rma tS y n c M L M e s s a g e (S y n c M L M e s s a g e ) : S tri n g
+ p a rs e S y n c M L M e s s a g e () : S y n c M L M e s s a g e
+ c re a te N D T ri g g e r() : v o i d
e x te n d s
« i n te rfa c e »
in tf::S e r v ic e R e p o s ito r y
- se rv i c e In fo L i st: S e rv i c e In fo []
+ a d d S e rv i c e (S e rv i c e In fo ) : v o i d
+ re m o v e S e rv i c e (S e rv i c e In fo ) : v o i d
+ i sS u p p o rte d (S tri n g ) : b o o l e a n
+ re tri e v e S e rv i c e In fo () : S e rv i c e In fo
- S e ssi o n Id : l o n g
- S o u rc e U R L : S tri n g
- D e v i c e Id : i n t
'#%$#%'$$5

) 46 8 " 9 2 6
1 " " )3
1 6 8/ ) 6 8 "6 "
= " ! 8 / : ! ! B 8!
8/ ) 8! 7 /
Respond to Vehicle Status Discovery
9 B6 78 #' 8 = "
8 : B "" 6
/ 4 G 7 H = "
7 6 " " )3 "
/ " 6 ! ""
7 . 6 /
) " = " ! *
cd Nomadic Device Vehicle Status Server initiation
«interface»
RequestHandler
+ StartService (String) : void
+ SendResponse() : void
«interface»
intf::
ServiceRepository
«interface»
intf::ServiceInfo
Nomadic Device TCU
«interface»
intf::FepServer
+ Accept() : byte[]
«interface»
intf::FepClient
- serviceRepository: ServiceRepository
- syncMLMessage: SyncMLMessage
ServerListener
+ «property get» getsyncMLMessage() : SyncMLMessage
+ onDiscoveryEvent() : void
+ «property set» setsyncMLMessage(SyncMLMessage) : void
+ Send(byte[]) : void
+ formatObexMessage(byte[]) : String
+ parseObexMessage(byte[]) : byte[]
+ formatSyncMLMessage(SyncMLMessage) : String
+ parseSyncMLMessage() : SyncMLMessage
+ createNDTrigger() : void
«interface»
intf::ServiceInfo
- ServiceLocator: String
- ShortDescription: String
- LongDescription: String
- MajorVersion: int
- MinorVersion: int
«interface»
intf::ResponseHandler
+ StartService(String) : void
+ «property get» getLongDescription() : String
+ «property get» getMajorVersion() : int
+ «property get» getMinorVersion() : int
+ «property get» getServiceLocator() : String
+ «property get» getShortDescription() : String
+ «property set» setLongDescription(String) : void
+ «property set» setMajorVersion(int) : void
+ «property set» setMinorVersion(int) : void
+ «property set» setServiceLocator(String) : void
+ «property set» setShortDescription(String) : void
+ equals() : boolean
+ toString() : String
= 7 ! "
= " )3 8 / ) = 6
6 ! 1 F / ) ! " / )
" 6 8 B / !
B 8 "6 " 6 8 "6
/ = B " " " 8
66 / 8 1 F 7 6 )3 /
''%$#%'$$5

) 46 8 " 9 2 6
) )3 63 6 6 ! 1 6 / 2
1 6 ! 6 8 B )3
" " 8 /
" . ! 8 "" /
8.5.5 eCall discovery and initialization
9 ! 30 3# 3 / )
3 ! )3 ! " I J "
" 6 ! " 6 " " )
1 6 C,#D 9 < / ) B
6 " / 7 8
" " 6 " 7 7 6 ! )3
! 7 /
) 3 B 8 6
/
) "6 6 6 ! /
3 2 # " . 66 / ) 8 "
" 8 ! F / ) 3
# 1 B 6 /
) ! 7 "6 " *
0
0 $ ) )3 86 78
8 7
= "
0 $ ) = " 6
8 " 78 3
" " 8
/
8.5.6 Service Consumption
3 "6 " 7 ! =
) / ) "" ! 7 ? "6 " 6 6
6 " /
" " " 8 ! " B
"6 / ) 7 6 G 6H" 7 "6 " 78
8) = / 9 ) = "6 " 7
* = 2 / ) !
! " /
'#%$#%'$$5

8.5.7 Service Provisioning
) 46 8 " 9 2 6
cd Serv ice Consumption Interface
«interface»
service::
NDIServ ice
+ start() : boolean
+ stop() : boolean
Figure 34 NDIService
) 4 9 8 ? 6
6 " 8 ? 7 !
= " )3 / ! B 8 8 ? B6
B 786 6 >/(/# . ) 8 ? /
2 2 7 78 "6 7
= ) / 4 2 8 ?
6 2 7 9= 3 6 78 7 /
! B 8 6 " "6 "
6 / " B"6 *
• ! " " 3 3 78" 6
6 78 6 8" 3 6 /
• 2 78" B 3 .14 @ 8
/
) " " ! 6 E 21 "
6 6 8 /
) " ! 2 2 7 !
7 ) = 2"6 " /
8 ? 2 ! ! 6 ! "
6 ! 8 ? 6 *
• 4 " I9 6 J = " 8 ?
) 8! = 8 )3 /
• 4 " I9 6 J )3 8 ? = 8
! ) 8 = " /
) = 1 6 / ) = 8 )3
2 7 "6 " ! = "
" )3 ! ) = "
! )3 " = " /
(*' *' 32 # # =
" ! !
(*' *' % "
'#%$#%'$$5

ud Nomadic Dev ice Gateway Use Case Overv iew
) 46 8 " 9 2 6
Nomadic Gateway
Nomadic Device
Accept
FEP
Activ ation
Embedded
Device
FEP to FEP
connection «realize»
Initial Connect «realize»
Nomadic
Dev ice
Submit
Credentials
Activate
Autorized
Serv ices on
Nomadic Device
Respond
to eCall
discov ery
Create
and Send
MSD to PSAP
Connect
to Serv ice
Model on
Embedded Dev ice
Verify
Remote Serv ice
View av ailability
(Nomadic)
Verify
Credentials of
Embedded
Dev ice
Modify
Nomadic
Dev ice
Operation
Nomadic
Serv ice
Browser
«realize»
«realize»
Respond
to Vehicle
Status
Discovery
«realize»
«realize»
«realize»
«realize»
«realize»
«realize»
«realize»
«realize»
Authenticate and
Authorization
Vehicle Status
Serv ice Discov ery
and initialization
eCall discovery
and initialization
Vehicle Status
Change
On eCall
Serv ice
Consumption
Serv ice
Prov isioning
«realize»
Serv ice
View
Download and
Activ ate
«realize»
«realize»
«realize»
«realize»
«realize»
«realize»
Figure 35 Use Case Overview
«realize»
Verify
Credentials of
Nomadic
Dev ice
«realize»
«realize»
«realize»
«realize»
Trigger
Vehicle
Status
Discovery
Send
Vehicle Status
Change Ev ent to
Service
«realize»
Dispatch
list of
Available
Serv ices
Handle
Nomadic
Dev ice Data
Verify
Remote Serv ice
View av ailability
(Embedded)
Poll
Nomadic
Device
Embedded
Device
Submit
Credentials
Activ ate
Authorized
Serv ices on
Embedded Dev ice
Trigger
eCall
discov ery
Activ ate
eCall listener
Send
eCall vehicle
trigger to
Nomadic
We still need to check this with the Rescue team. It
is not clear what the eCall service will send as event
data to the eCall client. Could be a formatted MSD
message but it could also be an object containing
some basic eCall info. This leaves the Nomadic
device with the task to compile the MSD message
before sending it.
''%$#%'$$5

8.6 Protocols
8.6.1 Protocol Stack
) 46 8 " 9 2 6
= " 2 B6 78 6 "
7 6 ! 6 4 9 8 : 8 ? C

) 46 8 " 9 2 6
Chapter 9 - DEPLOYMENT AND PROVISIONING
9.1 Introduction
) 6 6 8" 6 /
7 6 6 " # 7
/ ) 6 6 66
"6 " 3 3 3 /
$ 7 6 6 7 #
/ ) 6 6 66
"6 66 3 8 "/
6 8" 6 7 " "
" 83 3 /
9.1.1 Protocol-oriented
) ) 6 8" 6 . 66 /
) " 7 7 B ""
! . 6 / ) ! 6
6 7 6 "6 " /
9.1.2 Domain Model
) " " ! #5 7 ! 6
6 6 7 ! "*
''%$#%'$$5

cd Domain Model
Service subscription concepts (optional)
« entity »
LocalizedServiceInfo
- Name: string
- Description: string
- Icon: image
1..*
« entity »
Service
- SymbolicName: string
- Version: version
0..*
« entity »
Subscription
0..1
A subscription is an abstract concept that
can be implemented in a number of ways.
A subscription can be associated with an
end user, a client system, the combination
of the two and/or any number of
parameters available in the backend.
The service is the
concept that is visible
to the end user.
« entity »
SubscriptionConstraints
- BeginDate: date
- EndDate: date
- Renew: boolean
« entity »
Locale
- Language: string
0..1
OsgiBundle
) 46 8 " 9 2 6
« entity »
ServiceApplication
« entity »
Component
« entity »
- SymbolicName:
DynamicComponent
string
- Version:
- ServerTimestamp:
version
timestamp
- MimeType: string
UnixHostsFile
The service application is the
provisioning unit. It groups and orders a
number of components. It also contains
an optional reference to the service it
realizes. This is to enable feedback to
the end user based on lifecycle events.
LinuxBinary
« entity »
ClientSystemType
A given dynamic component is not
necessarily the same over time or for
different client systems. It can be a
configuration 0..* that is derived from a number
of parameters available in the control
center, e.g. end user, client system,
language, time etc. The ServerTimestamp
indicates when the current instance was
created by the control center.
0..* {ordered}
'#%$#%'$$5

ud Use Cases and Collaborations
UC-OS-0025
Deployment
UC-OS-0022b
Control Centre
Initiated
Prov isioning
without the need
for End User
Acceptance
UC-OS-0022a
Control Centre
Initiated
Prov isioning with
End User
Acceptance
UC-OS-0040
Application
Installation by
Operator
«include»
UC-OS-0024
Application
Upload/Download
«include»
UC-OS-0041
Application Update
by Operator
«extend»
«extend»
«include»
UC-OS-0006
Upgrade of a
Serv ice
Application
9.3 Deployment
9.3.1 Scope
«include»
«include»
«realize»
UC-OS-0042
Application
Remov al by
operator
UC-OS-0022
Control Centre
Initiated Serv ice
Prov isioning
«extend»
UC-OS-0020
Serv ice
Prov isioning and
Application
Download
«extend»
UC-OS-0021 End
User initiated
Serv ice
Prov isioning
UC-OS-0007
Automatic
Upgrade of a
Serv ice
Application
) 46 8 " 9 2 6
«realize»
«realize»
«include»
«include»
Deployment
Client System
Management
(CSMgmt)
(from System Overview.OS)
Prov isioning
UC-OS-0053
Serv ice
Fullfilment
«i ncl ude»
UC-OS-0055
Serv ice Discov ery
Service Deployment Interface (SD-I)
System Management Interface (SM-I)
Figure 37 Use cases for Provisioning and Deployment
Serv ice Centre
(SC)
(from System Overview.OS)
Service Consumption Interface (SC-I)
Telematics
Control Unit
(TCU)
(from System Overview.OS)
) 6 6 6 " 6 8 ) 966
? ) 3 3 / 2 6 !
6 " 3 3 / ) "6 "
3 3 Q 86 ! 8 ! 7 78 6 6 ! 7
3 3 /
) 6 6 6 " 6 "
"6 966 3 8 "/
) " 7 " *
• 2
•
• 8 " 1 F "
'#%$#%'$$5

• " 7 6
9.3.2 Solution
) 46 8 " 9 2 6
) ) " ?6 "6 !
B" " . 6 8" /B" " 7 6 8"
"6 / ) 8 B . 6 8" /B" 7 &/#/# ) .
6 8" /B" / ) 6 8 ?6 7 &/#/, 8
/
9.3.3 The gst-deployment.xml file
) . 6 8" /B" 6 8" 6 " / )
" 9K " " 9K 8 " 86
" 9K " )
66 " / " 86 ! 7 7
! 6 /
Figure 38 Top-level structure of gst-deployment.xml
2 6 8" 6 E 8 8 " 86
3 3 6 " "" ! 7 8 " 86
7 /
If the deployment descriptor doesn’t contain any service definitions the Service
Provider and Control Centre Operator either has to agree on the service definitions out
of band or the Service Provider simply provides an application and leaves the
definition of the service to the Control Centre Operator.
'#%$#%'$$5

The Vendor Information Element
) 46 8 " 9 2 6
The purpose of the vendor information element is for the creator of the
deployment package to be able to provide contact information in a textual
non-structured textual format.
The System Type Definition Element
) 6 6 8 " 86 " 8 7 8 "
86 7 66 78 66 /
) 8 " 86 " ) B 8 6 "
9K " /
Figure 39 Structure of the system type definition element
) 8 " 86 " ) ! 7 *
• system-type-id – This attribute contains a string identifier for the system type.
The exact syntax of this identifier is left undefined and can either use existing
standards or can be generated by either the Service Provider or the Control
Centre Operator. E.g. a Control Centre Operator could communicate to its
Service Providers that it supports 2 system types with the identifiers
“com.gstproject.terminal.osgi.r3” and “com.gstproject.terminal.linux”. The
Control Centre Operator is responsible for setting a naming policy that
prevents namespace collisions between system type identifiers when
interacting with Service Providers.
) 6 " ) B 6 8 " 86 / )
" " 3 3 46 !
" 8 " 6 "6 " 66 8 " 86 /
) " " 8 " 6 8 "
86 / ) " " 7 6 B " " 7 78
3 3 7 " " ! 8 "
66 78 66 8 " 86 /
The feature element MUST have the following attribute:
• feature-id – This attribute contains a string identifier for a feature. The exact
syntax of this identifier is left undefined and can be generated by either the
Service Provider or the Control Centre Operator. E.g. a Control Centre
Operator could communicate to Service Providers that it recognizes and can
check for presence of the following features
“com.gstproject.feature.vehicle.sensor.odometer” and
“com.gstproject.feature.gps”. The Control Centre Operator is responsible for
setting a naming policy that prevents namespace collisions between features
when interacting with Service Providers.
'#%$#%'$$5

The Service Definition Element
) 46 8 " 9 2 6
) " . / )
" ) " ? " /
Figure 40 Structure of the service definition element
) " ) ! 7 *
• service-id - This attribute contains a string identifier for the service. The exact
syntax of this identifier is left undefined and can be generated by either the
Service Provider or the Control Centre Operator. The Control Centre Operator
is responsible for setting a naming policy that prevents namespace collisions
between services when interacting with Service Providers.
• version – This attribute contains the version of the service in
.. format. E.g. 1.12.0. The micro part is optional.
) " 9K ! 7 *
• default-locale – This attribute contains the default locale of the service
definition. This is the locale that should be used if there is no information
available for a requested locale. Locales are constructed by combining 2-letter
language codes [58] with 2-letter country codes [59] separated by a ‘-‘. If this
attribute is not present the default locale is assumed to be en-US.
) ? " " 6 / 2
) " " 6 " / 2 9K "
"
) ? " 9K ! 7 *
• locale – This attribute contains the locale of the service definition. Locales are
constructed by combining 2-letter language codes [58] with 2-letter country
codes [59] separated by a ‘-‘. If this attribute is not present the locale is
assumed to be en-US.
) " " ) ? " /
) 6 " ) ? 6 /
) " 7 " 87 6 6
/
) " ) ! 7 *
• height – The height in pixels of the icon.
• width – The width in pixels of the icon.
'#%$#%'$$5

) 46 8 " 9 2 6
• mime-type – The mime-type of the file containing the data for the icon.
• path – The path to the icon file relative to the root of the containing zip file.
The Service Application Element
) 6 6 66 " 7 ! "6
"6 " 8 " 86 /
) 66 " 9K 66 8 " 86 "
66 " " " / 2
) " 8 "6 " /
Figure 41 Structure of service application element
2 66 " 66 8 " 86 "
! ! 8 " 86 66 / ) 8 "
86 9K " " 8 " 86 " " . 6 8" /B"
7 "" 7 7 ! 3 3
46 / 2 66 " E 66 8 " 86
" " ! 8 " 86 66 7
"" 7 7 78 3 3 46 /
2 66 " 66 "
66 87 6 8 " ! 8
F 78 8 "/ 2 66 " E
66 " 66 ! 8 7 6
F /
) 66 " ) ! 7 *
• 66 . A ) 7
66 / ) B 8 B
78 9K 7 7 " 3
'#%$#%'$$5

) 46 8 " 9 2 6
3 46 / ) 3 3 46 6 7
" 6 8 6 " 6 7 ! 66
! ! /
• A ) 7 66
`" a/`" a/`" a " / / /

) 46 8 " 9 2 6
) 66 8 " 86 " 9K 66 8 " 86 "
F " B F " " /
Figure 42 Structure of the supported system types element
2 66 8 " 86 66 8 " 86 " 8 " 86
78 " 66 / 9 66 8 " 86 " 9K
F B F " " 6 8 !
7 66 78 8 " / 2 F "
78 " ) 7 6 8 "
7 66 / 2 B F " 3 3 46
4 : " 8 8 F " /
2 66 8 " 86 F "
8 " 86 ) 66 78 " /
2 66 8 " 86 B F " "
3 3 46 4 : " 8 8 F "
8 " 86 /
) 66 8 " 86 " ) ! 7 *
• 8 ". 86 . . ) 7 8 " 86 / )
B 8 B B
7 78 3
3 46 / / / 3 3 46 ""
66 ' 8 " 86 !
G "/ 6 / " / / #H G "/ 6 / " / BH/ )
3 3 46 6 7 " 6 8 6
" 6 7 ! 8 " 86 ! !
/
) F . " ) ! 7 *
• . . ) 7 / ) B
8 B 7 78
3 3 46 / / / 3 3 46
"" ?
6 !
'#%$#%'$$5

) 46 8 " 9 2 6
G "/ 6 / / / / " H
G "/ 6 / / 6H/ ) 3 3 46 6 7
" 6 8 6 " 6 7 !
! ! /
) B F " " B F " 7
78 8 " 7 6 / ) 3 3 46 4 :
" 86 F " /
) 66 " 66 / 2 )
" " /
Figure 43 Structure of the supported locales element
) " " 8 / ) " )
! 7 *
• . ) 7 '. C(>D
) " 9K ! 7 *
• 8A ) 7 '. 8 C(&D/
2 " E 8 7 "
7 " 66 /
) 6 6 " 7 7
6 6 6 " 7
"" /
) " 7 " 86 "
" /
) 6 " " ) 7 *
• " . ) " 6 "
• . ) 6 "
• 6 . 9 6 6 "
9.3.4 Physical Structure
) 6 8 ) 6 8" 6 ?6 C5$D! .
6 8" /B" 8 "6 6 78
/
) 7 "" ! *
` ?6 a% . 6 8" /B"
` ?6 a%` 6 a%` "6 a
` ?6 a%` 6 a%` 6 a
B"6 *
. B"6 . 6 8" /?6
'#%$#%'$$5

% . 6 8" /B"
% . B"6 .7 /
% . B"6 . / 6
9.3.5 Example gst-deployment.xml
@ ! B"6 . 6 8" /B" *
) 46 8 " 9 2 6
Any OSGi R3 implementation running J2ME
CDC/Foundation
GST Demo Service
This Service Demonstrates GST
Must have a minimum of 16 MB ram

) 46 8 " 9 2 6
mime-type="x-application/osgi-bundle">
9.4 Provisioning Protocol
) 6 6 4 9 " I4 9 J/
" 6 784 9 7
7 / 9 6 F "
6 4 9 / ) 6 " 7 ! 4 9
6 6 6 ! )/ B6 8
! 6 6 ! 4 9 6 / @ !
6 6 4 9
6 ! F " ! 8 / )
6 % " 4 9 6 7 4 9 7
1 " C5$D/
9.4.1 OMA Device Management Bootstrap
) 66 7 66 C#'D 6 4 9 7
78 6 / 2 6
7 8 6 6 6 " "
" 7 66 4 9 / ) 7 66 "
7 C#'D "" ! 6
6 ! /
9.4.2 OMA DM Device Description Framework DTD
) 6 6 6
F " 4 9 ) / 2"6 " 6 6
) ) C,$D/
9.4.3 OMA Device Management Notification Initiated Session
) 6 6 F 6 7 78
3 3 ! 78 / ) = 2
" " 4 9 C#(D / 2 ! 3 3
! . " " B"6
9 / ) " ! 6 /
= 6 4 9 7 " 8 6 /
0
9 $
31. .=4)2.3.$$< 46 ) 66
'#%$#%'$$5

) 46 8 " 9 2 6
31. .=4)2.3.$$' 46 ) 3 66
31. .=4)2. .$$< 46 ) 66 .
" "
31. .=4)2. .$$' 46 ) 66
F " . 14. .3.$$< C#5D/
Table 13: Provisioning protocol requirements.
9.4.4 OMA Device Management Protocol
) 6 6 " 6 4 9
C#5D " 66 " 8*
9.4.5 General
0
9 $
. 14. .3.$$< 46 ) 66
. 14. . .$$< 46 ) 66 I J
. 14. .3.$$# 46 ) . " "
. 14. .3.$$, 46 ) 3 . " "
. 14.3.$

9.4.7 Generic Alerts
) 46 8 " 9 2 6
) 6 6 " 6 9 4 9
" " 8/
0 9 $
DM-PRO-GAlert-C-001 46 ) A Generic Alert have a
relation to a MO.
. 14. 9 .3.$$# 46 ) : 12
DM-PRO-GAlert-C-005 46 ) Type info must be
included.
DM-PRO-C-011 46 ) Sending of Generic
Alerts by clients
DM-PRO-C-010
DM-PRO-GAlert-S-002
9.4.8 User Interaction commands
46 ) Client Support for
asynchronous data via
alerts
46 ) Actions are performed
by the server as a result
of a Generic Alert.
Table 16: Provisioning protocol requirements.
2"6 " 6 6 ) 66
6 8 3 " 78C#5D/ 4
9K 7 66 /
DM-PRO-C-007
0 9 $
46 ) Client support for executing
User Interaction Commands
DM-PRO-UI-C-001 46 ) Client support for Display
DM-PRO-UI-C-002 46 ) Client support for
Confirmation
DM-PRO-UI-C-006 46 ) Ordering of user interaction
commands
DM-PRO-S-007
46 ) Server support for sending
User Interaction Commands
DM-PRO-UI-S-001 46 ) Server support for Display
DM-PRO-UI-S-002 46 ) Server support for
Confirmation
DM-PRO-UI-S-006 46 ) Ordering of user interaction
commands
'#%$#%'$$5

) 46 8 " 9 2 6
Table 17: Provisioning protocol requirements.
9.4.9 OMA Device Management Representation Protocol
66 6 Atomic Exec "" C#-D F
6 /
9
0
DMREPPRO-PCE-C-004 ) ) 66 9 "
"" "
DMREPPRO-PCE-C-005 ) ) 66 B
"" "
Table 18: Provisioning protocol requirements.
9.4.10 OMA Device Management Security
) 6 6 8 4 9 C#>D/ 2
7 8 F 4 9 % 6 6
8 6 8 78 8 6
8 / ) 6 6 8 )) / 7
)) 7 4 9 C#$D/
9.4.11 OMA Device Management Standardized Objects
2"6 " 6 6 ) 66 4 9
? 47 78 C#& D/ 2 "6 " )
66 6 2 7 B 12 " " 7 " 6 7
" " 7 7 8/ ) ! 8
" " 7 " 6 6 6 /
0 9 $
31. . ) 4@ .3.$$, 46 ) 3 66 2 7 B
12
31. . ) 4@ . .$$, 46 ) 66 2 7 B
12
Table 19: Provisioning protocol requirements.
9.4.12 OMA Device Management Tree and Description
) 6 6 F I93:J/
) 6 B ! " 8 8
'#%$#%'$$5

) 46 8 " 9 2 6
)/ 2"6 " 9K 66 93: 6 6 8 ) 7
4 : =4) 6 8/
9 6 6 F 66 6
6 6 ! 4 9 F " C,$D/
9 *
0 9 $
)= . 6.3.$$< 8 9K 3 66 93:
6 6 8
)= . 6. .$$< 8 9K 66 93:
6 6 8
)= . 6.3.$$<
)= . 6.3.$$'
)= . 6.3.$$#
)= . 6.3.$$(
)= . 6.3.$$>
)= . 6. .$$

$
) 46 8 " 9 2 6
GST
'#%$#%'$$5

$/GST/components
$
GST
components
) 46 8 " 9 2 6
*
+
Figure 45 Components Management Object.
) 6 "6 3 "/
Access type: Get
Format: node
Occurrence: One
Scope: Permanent
$/GST/components/
'#%$#%'$$5

Scope: Dynamic
) 46 8 " 9 2 6
$/GST/components///State
) "6 8 "/
* % % % # % # ) # %/ )
" " ) 6 = / ) 8 " 9K
" ! " " /
Access type: Get
Format: int
Occurrence: One
Scope: Dynamic
Default value: Staging
$/GST/components///Transition
) "6 /
B " " 3 " ! 8 8 "6
"6 / 2 B "" )
($$ 3 "" 6
) '$$ 4L/ ) "
B "" / * % #/ $
6 "6 / )
6 78 I . J " " !
7 / ) B "" ) G,$#
7 H "6 / ) B
"" " 8 6 8 /
Access type: Exec
Format: null
Occurrence: One
Scope: Dynamic
$/GST/components///Failure
) 8 "6 / B
Transition " 7 6 6 B /
2 6 " /
$/
Access type: Get
Format: int
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/components///Data
) 7 8 ! "6 / ) 2 86
86 "6 / ) ! ! 8
6 "6 786 " Add Replace "" / )
URL / % " /
Access type: Get, Replace
Format: bin
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/components///URL
'#%$#%'$$5

) 46 8 " 9 2 6
) 1: ! ! 6 / )
1: ! " " 6 @ / )
! 7 7 ! 2 86
6 " 1:/ ) ! ! 8 6 "6 /
) Data 8/ $
7 ! " " /
Access type: Add, Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
9.5.3 Services Management Object
) 7. 86 8 7 !
8 "/ 2
" /
$
GST
$/GST/services
services
*
+
CurrentLocale
'#%$#%'$$5

Access type: Get
Format: node
Occurrence: One
Scope: Permanent
$/GST/services/
) 46 8 " 9 2 6
) 6 " 7 / ) "
8"7 " " " / ) 7
! 7. /
Access type: Add, Get, Replace, Delete
Format: node
Occurrence: ZeroOrMore
Scope: Dynamic
$/GST/services//
) 6 / ) "
" " / ) 6
7 7 6 b / / " . " 7 /
Access type: Add, Get, Replace, Delete
Format: node
Occurrence: OneOrMore
Scope: Dynamic
$/GST/services///CurrentLocale
) 6 8 / 2 6
8 7. / 2 86 8 8
/ 2 6 7 8 6
8/ 2 B 7 4 : 7
7. /
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/services///locales
) 6 ? " 7 /
Access type: Add, Get
Format: node
Occurrence: One
Scope: Dynamic
$/GST/services///locales/
) 6 ! ? " 7 /
Access type: Add, Get, Replace, Delete
Format: node
Occurrence: ZeroOrMore
Scope: Dynamic
$/GST/services///locales/
/Name
'#%$#%'$$5

) 46 8 " 9 2 6
) 6 8 " 6 78 6
/
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/services///locales/
/Description
) 6 6 78 6
/
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/services///locales//Icon
) 6 78 6 /
Access type: Get, Replace, Delete
Format: bin
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/services///components
) 6 "6 ? /
Access type: Get
Format: node
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/services///components/
) 6 " "6 ? / ) "
8"7 " "6 " " /
) 7 ! 7. / 2
6 7 8 6 8/
Access type: Add, Get, Delete
Format: node
Occurrence: ZeroOrMore
Scope: Dynamic
$/GST/services///components/
/
) 6 "6 ? / )
"6 c% )% "6 /
B "6 ! " " / ) "
"6 " " / 2 6 7 8
6 8/
Access type: Add, Get, Delete,
'#%$#%'$$5

Format: null
Occurrence: OneOrMore
Scope: Dynamic
) 46 8 " 9 2 6
$/GST/services///settings
) 6 6 6 " /
Access type: Get
Format: node
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/services///settings/
) 6 6 6 " 78
" / ) 6 6 " /
Access type: Add, Get, Replace, Delete
Format: chr
Occurrence: ZeroOrMore
Scope: Dynamic
9.5.4 Users Management Object
) 4 6 " ! 7 6
" " /
'#%$#%'$$5

$/GST/users
$
GST
users
) 46 8 " 9 2 6
*
FirstName ?
LastName ?
'#%$#%'$$5

) 46 8 " 9 2 6
) " / 8 6 ? 6 8
6 6 /
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//LastName
) " / 8 6 ? 6 8
6 6 /
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//Email
) " / 8 6 ? 6 8
6 6 /
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//CreatedDate
) ! ! 8 "/ 8
6 ? 6 86 6 /
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//Locale
) 6 / 2 7 / /
? / 2 ? " 7 66 78 /
Access type: Get, Replace, Delete
Format: chr
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//subscriptions
) 6 7 6 /
Access type: Get
Format: node
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//subscriptions/
) 6 " 7 6 3 "/ ) "
8"7 " 7 6 " " / 2
'#%$#%'$$5

) 46 8 " 9 2 6
7 7 7 7 / 4
6 " State ! %.
Access type: Add, Get, Replace, Delete
Format: node
Occurrence: ZeroOrMore
Scope: Dynamic
$/GST/users//subscriptions//
ServiceID
) 6 ! 7 6 / 2
! ` 8"7 = " a ` a "
7. 6 78 I*J/ 2 6 7 8
6 8/
Access type: Add, Get, Replace, Delete
Format: chr
Occurrence: one
Scope: Dynamic
$/GST/users//subscriptions//State
) 6 7 6 / * %
2 % 2 / $ / "
9K 7 F 3 " 9 C#5D/ 2 6 7 8
"" " 7 6 /
Access type: Get, Replace
Format: int
Occurrence: One
Scope: Dynamic
$/GST/users//subscriptions//
Transition
) 78 F I " J 7 6 / ) 7 6
3 " ! 8 8 "6 7 6
! B / 2 B "" )
G($$ 3 "" H 6 )
G'$$ 4LH/
2 B ! ) 6 78
I . J " " ! 7
/
) " B "" /
* / ) B "" ) G,$#
7 H "6 / ) B ""
" 8 6 8 /
Access type: Exec
Format: null
Occurrence: One
Scope: Dynamic
$/GST/users//settings
) 6 6 6 " /
'#%$#%'$$5

Access type: Get
Format: node
Occurrence: ZeroOrOne
Scope: Dynamic
$/GST/users//settings/
) 46 8 " 9 2 6
) 6 6 6 "
78 8"7 " /
Access type: Add, Get, Replace, Delete
Format: node
Occurrence: ZeroOrMore
Scope: Dynamic
$/GST/users//settings//
) 6 6 6 " 78
" / ) 6 6 " /
Access type: Add, Get, Replace, Delete
Format: chr
Occurrence: ZeroOrMore
Scope: Dynamic
9.6 Behaviour Associated with the Management Objects
9.6.1 User Display Interactions
6 8 B " "
4 9 6 2 3 "" C#5D/ = 6 )
"6 6 8 /
9.6.2 Components Management Object
3 . " 4 "6 4 B 7
6 / ) 2 7 7 / )
8 " 8 ! "6 ?
! 8 F / 9 "6 7 7
" " 1: ! " " .
" 7 7 6 " " 4 ;
Semantics of Transition execution and Download of component
) 4 9 ! 6 6 B7 6 7
! 6 !
6 / ) 3 "6 4 ! 6 !
4 9 I / / 9 %1 6 J 8 7 !
" " I B"6 6 7 ! 6 4 9
!

Upload of Data via OMA DM
) 46 8 " 9 2 6
) ! B"6 ! ! 4 9 8 " "6
6 G1 6 H ""
6 7 86 / ) ) )
B /
Client
OMA DM
“Discovery + Download”
Push Initiation
Device Information Exchange
Replace $/components///Data
Replace …../targetstate
Exec Mgmt Tree Object -> Transition
Figure 48 Data upload via OMA DM.
Upload of Data through an Alternative Download Mechanism
Control Center
(OMA DM
Server)
) ! B"6 ! ! 4 9 B !
" G1 6 H "" 6 8 1: !
6 7 IB ?J 7 86
! " 7 / ) ) )
B ! 1: 7 86 /
Mobile
Device
OMA DM
“Discovery”
Push Initiation
Device Information Exchange
Replace $/components///URL
Replace ……./targetstate
Exec Mgmt Tree Object -> Transition
Request D/L Descriptor
D/L Descriptor
Request Update Package
Update
OMA DL
“Download”
Figure 49 Data upload though OMA DL.
Control Center
(OMA DM
Server
Content
Server
2 "6 "68 B !
F "6 1:
"6 / 2 1: "68 ! G($' A 1:H/
'#%$#%'$$5

4 9 : ! " "/
Use of Generic Alert for Notifications
) 46 8 " 9 2 6
9 ! ! B I
J )
9 " / ) " ! *
* )
G1 2 * ) 12 3 "6 7 6 . 8
/ ) 7 8
* / /
0 * 78 6 6 B "" /
2 6 B "" )
) "
9 /
2 6 B ""
) ) =4)
9 /
9 6 4 : 6 8
2 " " /
Result codes
) ! 7 7 "6
/ 2 "6 " ! /
0 3
$ 0
2
'$$ ) "6 8
,$$ 3 3 6 ". 6 "
6
,$< = 6 .
!
) 6
! "6
,$' = 6 A 2 ) 6
! "6 7
,$, " 7
,$(
9
6 8
,$5 = 9 6 7 3 = 9 6 7
B"6 ! "
'#%$#%'$$5

) 46 8 " 9 2 6
,$- 9 9 ! 1 F 7
9 !
,$> 1 F ) " .4 3 " .
,$& ! ) 6 1:
!
,

7 7 <
7 7 '
7 7 ,
7 7 >
9.7 Use Case Realizations
) 46 8 " 9 2 6
Table 23: Subscription state encoding.
) 7 ! 3 &/' ?
6 / 9 B"6 !
" . 78 B"6 /
9.7.1 Subscribe to service from client
) 7 6 . 3.4 .$$'

) 46 8 " 9 2 6
9 c% )% % % 7 6 % B"6 7 6 %
2
B"6 *

9 "
) 46 8 " 9 2 6
Table 25: Command sequence.
2 7 6 6 ! ! " "
3 3 " 8 7 6 %! 6 "
7 6 6 /
6 B 7 6 %/ 2
7 6 " "
! 3 3 9 ! *
* / /
0 * B ""
:1 2 * c% )% % % 7 6 % B"6 7 6 %
* 7 7 I 'J 7 7 I >J
Upgrade of a service with user intervention
) 6 . 3.4 .$$$5/ 2 B6 6
6 GB"6 H "

) 46 8 " 9 2 6
) ! ! 9 ! 6 "
68 ! ! 7 6 ! 6 /
6 B 7 6 %/ 2
7 6 " "
! 3 3 9 ! *
* / /
0 * B ""
:1 2 * c% )% % % 7 6 % B"6 7 6 %
* 7 7 I 'J 7 7 I >J
9.7.4 Upgrade of a service without user intervention
) 6 . 3.4 .$$$-/ 2 B6 6
6 GB"6 H "

9.7.5 Activate new component
) 46 8 " 9 2 6
) 66 . 3.4 .$$,$/ 2
6 ! ! "6 ? / ) "
B"6 "6 GB"6 H G

0 0 H 0
) 46 8 " 9 2 6
0 # %
@ 9 "
B c% )% "6 % B"6 %

) 46 8 " 9 2 6
Chapter 10 - IDENTITY, AUTHENTICATION,
AUTHORIZATION
10.1 Introduction
9 ' ! 6 3 8 " 1 F "
.4 I 3.4 .$$(&J ! / ) !
! 8 ! 8
" . " "
Z " " "6 /
7 6 " 6 6 6 6 " "
! 8 F " 6 8 ?
6 / I J
.4 6 I6 78 ) J ! " 8
6 8" 6 6 " /
? 6 3 3 !
6 7 % ? /
8 F " ) .4 6 6
! 6 ) 8 76 // :; 3;#/

) 46 8 " 9 2 6
7 8 )) % )) 49 / ) 6
) 6 / 9 6 7
7 7 ! ?
6 6 ? F /
• 2 6 6 8 6
/
• 6 " ?
• ) N : 86 N :
"6 " 8" " 9 : /
) 9 : 6 6 G
H " G H 6 ?
6 ! 8 .4 6 " 8 E6
" ! 6 " "" 8
? " " /
" ? .4 6 ""
" I 8" J 7 78 ) I/ / 3
3 J / @ 8 6 *
• G 7 86 H "" 8
• 78 3 3 I6 ) 9 Z
J
• 8" 66 " " 7 ! 9
2 6 ) 6 ! *
• " 78 9 ! 78
" 0 " I/ / 0 7"!/ "J
9 "6 6 8 _
To address privacy issues identity mapping mechanisms (see illustration below) based
on specific needs of GST between an Aggregator and federated Service Providers and
between GST Aggregators as are required.
'#%$#%'$$5

10.2 Use Case Diagram
10.3 Interfaces
) 46 8 " 9 2 6
Figure 2 – Distributed Authentication in GST Nodes
:; 3;#/< 9 2 6 3 6 5 9 ?
3 7 3 6 - 9 3 7 Q 6 8
2 /
10.4 Protocol Stack and Specification
:; 3;#/< 9 2 6 3 6 5 9 ?
3 7 3 6 - 9 3 7 Q 6 8
2 /
10.5 Message Structure
:; 3;#/< 9 2 6 3 6 5 9 ?
3 7 3 6 - 9 3 7 Q 6 8
2 /
10.6 API Specification
:; 3;#/< 9 2 6 3 6 5 9 ?
3 7 3 6 - 9 3 7 Q 6 8
2 /
'#%$#%'$$5

10.7 Interactions
) 46 8 " 9 2 6
:; 3;#/< 9 2 6 3 6 5 9 ?
3 7 3 6 - 9 3 7 Q 6 8
2 /
'#%$#%'$$5 $

) 46 8 " 9 2 6
91) # . 2 : =)9)24= 2 9=
34=3: 24=
'#%$#%'$$5 <

Chapter 11 - REFERENCE MODEL
) 46 8 " 9 2 6
) 6 7 "6 ! 6
7 78 6 / ) " 7
? "6 " ! 6 7 8
/ ) " "6 ! "
6 "6 " ! 6 8"
"6 ) ) " " ! /
11.1 Components
Figure 50 Component diagram
9 B6 " 7 ) 7 #

) 46 8 " 9 2 6
• $ A ) 6 8 . /
966 "" ! 78" 3
78 46 8 " /
• $ 3 $ A 9 6" " 6
6" 6 8" 8 6 8
966 3 3 / ) 46 8 " " 6
6 8 66 7" /
3 "6 = " "6 " 7 " !
" " /
3 "6
6
'#%$#%'$$5 #

) 46 8 " 9 2 6
0 # 0 ) $ 5
3 9 ! 966
3 78 " ? 3
/ ) 3 6
966 66 6 8" "
7 M /
2
''%$#%'$$5 ,

11.2 Nodes
) 46 8 " 9 2 6
Figure 51 Deployment Diagram
9 B6 " 7 ) 7 ##/
''%$#%'$$5 (

) 46 8 " 9 2 6
= = " " 7 " !
" " /
= 6 ) 6 " " 7
/
2 . O ) INJ " 6 "
G H I "" 7.6 J 2 .
I C#D . . C,DJ/
Table 33 - Definition of Terms Used when Describing Collaborations
'#%$#%'$$5 5

) 46 8 " 9 2 6
# # # 0 ) $ 5
3 8 " = ) G ! H "6 78
966 1 " 2
= " 2 ! " / )
"6 "
3 /
3 1 7 6 / 46
8 " 6 3 "
966 ! )
6 3 8 " 3
""
' 1 6 8" "6 78 4
6 / 9 66
6 3 3 8 78
) : 9
8 , ) 46 "6 "
8 : 7 / ) 6 6
) 6 7
6 "6
9 8 ! 6
7 6 8 " / "
''%$#%'$$5 -

) 46 8 " 9 2 6
Chapter 12 - ARCHITECTURAL ISSUES AND DECISIONS
) 6 7 "
/ ) 6 /
12.1 ARE: considered alternatives for positioning
! " "6 " 7 *
9 2.3 I / " / / 86 / J
1

) 46 8 " 9 2 6
6 . I " " 6 . 6 . /J/
4 9 ) 6 . 6 B87 ! 4 9 ) 4 9 2
66 6 9 2 8
8 " 66 "6 / 2 " 4 4 9 ) 6 6 8
B"6 3 " 4 4 9 ) 6 . " 6
7 ) 6 . " 8" 6
B 7 8 8/ .
8G H 7 6 /
2 ! ! 6 8 4 9 ) 6 . !
6 7 " 6 . " ! !
! ! 6 " " 7
8 " 6 . " 7 6 ! G6 .
6 . H 4 9 ) 6 . 7 7 8
66 /
6 " 6 6 7 " 6 7 " " 4
) 8 86 66 6 7 " ! ! 9 2
8 4 4 9 )/ @8G! H " 6 "
6 7 6 / 2 6 7
3 7 4 4 9 ) 9 2/ ) 4 9 ) 9 2 "
6 B6 " 6 78 "6 4 " ! 7
6 6 " 66 ! ! ! /
" " G H 9 2 ! 784 4 9
) 7 " 8 : /
" 7 12 " 7 6 / 8
! / @8 ! E" 4 4 9 ) 9 2
7 8 7 " 8 : 6
7 " 6 / ) 8 : 4 4 9 ) !
7 8 4 9 ) 6 . /
3 " 9 " 8 !
! 66 ! 6 " 7 "
! 8 7 8GB6 7 H 7 8 : 78 "6 " "
4 9 ) 6 . ! ! 87 6 B87 ! 4 9 )
" ! 8 4 9
) 6 . / ) ! 6 ! ! 8* )
6 78 6 / 4 ? 78
9 " / B6 ! 78 4 9 )
6 . /
) !3 % # "
4 5* 3 " 3 " " " 7 / 4
" 87 " G 8 H "
7 " G 9 " IJ/ IJH/ )
" G 7 H " " 7
6 " F " B 7 / )
7 6 ! !
7 / ) " "" 7 / )
"" " 7 !
6 " ! ! ! / 2"" 7 8
66 6 7 8
'#%$#%'$$5 &

) 46 8 " 9 2 6
! ! 6 " " I
J/ 7 ! 8 ! 6 7 "
8 7 /
'#%$#%'$$5

1M.4 .
$$$<
1M.4 .
$$$,
1M.4 .
$$$(
1M.4 .
$$$-
1M.4 .
$$

1M.4 .
$$'$
1M.4 .
$$'<
1M.4 .
$$''
1M.4 .
$$'#
1M.4 .
$$',
1M.4 .
$$'(
1M.4 .
$$'5
1M.4 .
$$(<
) 8 ) "
7 6 "
8 " " 4 : 7
" 7 7 ! 8
7 /
) 46 8 " 9 2 6
0 $
F " /
) " 7 !
"6 " )/ ) )
6 ! !
6 "
/
) ) 6 7
6 6 7 /
F " 7
8 78 8
86 ) 6
F " 7 78
"6 " /
) 6 " ) F " 78 8
7.6 /
) 3 3 ) 7 7
" " 6
3 " "
$
9 3 9:: 7 7
6 8 66 8
). "6 3 3
6 "
6 8"
9 ) 7
3 3
" 6 8 "
66 "6 " /
) 9:: 7 ! 8
6
66 6 !
6 8 66 E
6 " F "
0
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
1M.4 . 9 8 ). "6 ) 3 783 6 & A 6 8" 3
'#%$#%'$$5

$$#$ 7 7 8 ).
"6 3 3
" /
1M.4 .
$$#<
1M.4 .
$$#'
1M.4 .
$$#(
1M.4 .
$$#5
1M.4 .
$$#-
1M.4 .
$$#>
1M.4 .
$$#&
1M.4 .
$$,<
1M.4 .
$$,'
) ) 7
%6 8
3 8 "
3 3
) 3 3 9K 7 7
" 8
3 8 "
966 8 "
/
) ) 8 " ) 6
! . 8 " "
966 /
) ! 3 8 " !
" IB 6 " 8 !
6 "6 J ) 7
" 8" 7 /
2 9K 7 6 7 !
! "6 "
" " 999
I9 9 ?
9 J . "6
6 8
6 ! 6
7 8 "/
966 8 "
9:: 7 6 . 7 /
6 " "
) " ) 6
" 7
966 8 "
I " 6 J/
) " ) 6
! ! 8 7
) 46 8 " 9 2 6
$ '
0 $
'#%$#%'$$5

1M.4 .
$$,#
1M.4 .
$$,,
1M.4 .
$$,(
1M.4 .
$$,5
1M.4 .
$$,&
1M.4 .
$$($
1M.4 .
$$(-
1M.4 .
$$(>
1M.4 .
$$(&
1M.4 .
$$5$
6 7 !
966 8 " /
) " 9K 7 7
! ! 6
3 8 "
I/ / . .
1 @
@ 3 J
2 ) 7 6 7
7 ! 6
6 ! "6 /
2 9:: 7 6 7 "
B
66 6 !
" 7 7
6 6 /
) ) 7 8
" "
2 9:: 7 6 7 8 " 8
3 8 "E
6 7 /
) 46 8 " 9 2 6
0 $
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 78 3 6 & A 6 8"
/
3 7 ) F " 7 8
8 6 8
I ! J/
) 6 8 8
F " / 2 7
78 "6 " /
6 66 "
8 !
3 783 6 5 A 966 1 "
" /
4 6 8 3 783 6 5 A 966 1 "
" /
966 6 . 6 " ) F "
"6 " )/ )
6 /
966 6 " ) F "
"6 " )/ )
'#%$#%'$$5

1M.4 .
$$5<
1M.4 .
$$5'
1M.4 .
$$5#
1M.4 .
$$5,
1M.4 .
$$5(
1M.4 .
$$55
1M.4 .
$$5-
1M.4 .
) " ) 7 7
8
66 F " 3
3 3 /
) 6 8 "
) 7 6 7 I!
3 3 J/
2 9K 7 6 7
66
! "6 !
3 3 7 /
) ) 8 " 9:: 66
86 ""
7 ! 3 8 "
3 3 * 8
9 8
) " /
) ) 8 " 9:: 6
"" 9 2 6
7 ! 3 8 "
3 3 6
" 7 ""
6 "" " /
2 6
I " J 3
8 " 9K " 8
" ""
" " 6 "
" /
) " 9K 66
1 3 I " 6 J
" /
) 3 8 " 9K 66
B "
0
) 46 8 " 9 2 6
)
"6 " /
0 $
) 78
8 7.6 /
6 /
3 783 6 5 A 966 1 "
" /
'#%$#%'$$5

$$5> I/ /
@ @ 3 J
1M.4 .
$$5&
1M.4 .
$$-$
1M.4 .
$$-<
1M.4 .
$$-#
1M.4 .
$$-,
1M.4 .
$$-(
1M.4 .
$$-5
1M.4 .
$$--
1M.4 .
$$->
) " 9:: 7 7
"" ! 6
/ ) 8
" 7 " " "
" 7 6 /
) 3 8 " 9K 7
@
. . I 7 J
! 78 .
6 3 /
) 46 8 " 9 2 6
0 $
"6 " 6 /
3 783 6 - A 2
/
) E 6 8 8
! 7 ! / 2 ! 7
"6 " 6 /
! 7 ! " ) E 6 8 8
! 7 ! / 2 ! 7
"6 " 6 /
966 " 3 783 6 5 A 966 1 "
" /
) 3 8 " 9:: 6
7
6
/
'#%$#%'$$5

1M.4 .
$$>$
1M.4 .
$$><
1M.4 .
$$>'
1M.4 .
$$>#
1M.4 .
$$>,
1M.4 .
$$>5
1M.4 .
$$>-
1M.4 .
$$>>
1M.4 .
$$>&
1M.4 .
$$&$
3 8 "/
) 46 8 " 9 2 6
0 $
6 6 " ) 7 78 "6 "
6 3 6 & A 6 8"
/
1 " ) 7 78 "6 "
6 3 6 & A 6 8"
78
6 8
1 " " ) 7 78 "6 "
6 3 6 & A 6 8"
78
6 8
8 " ) ) 6 !
"6 " 6 8
? ) 7 78 "6 "
6 3 6 & A 6 8"
78
6 8
)) 9 2 ) 4 6
F " /
9@ 9 2 ) 4 6
F " 9 .3 9= " 6
" //
7 3 8 " ) F " 3 6 > A
= " 2 /
3 "" 7 ! 3
8 " B
) 8 " I" 7 6
9 P J
) F " 3 6 > A
= " 2 /
) " "6 ) F " 7 78
8 6 " ) "6 "
6 /
1M.4 . 3 7 ! ) F " 7 78
8 6 " ) "6 "
'#%$#%'$$5

$$&< 6 /
1M.4 .
$$&'
1M.4 .
$$&#
1M.4 .
$$&(
1M.4 .
$$&5
1M.4 .
$$&-
1M.4 .
$$&>
1M.4 .
$$&&
1M.4 .
$

) 46 8 " 9 2 6
91) , . 9 = 2N 3)24=
'#%$#%'$$5

) 46 8 " 9 2 6
Appendix A - TERMS AND ABBREVIATIONS
9' 9 9 7 I@)J
93: 9 8 3 . I@)J
9 9 8
9 =/< 97 8 B=
9 13 9 1 " 3 I@)J
@'@ @ ) @
@2 @ 2" I@)J
@ ! ""
@ @ I@)J
@) @ @
3'3 3 ) 3
3'2 3 2
32 3 "" 2 = 9 I@)J
341 1 F " 3 6
3 3
3) 3 ) "
3) 3 ) 6 8 I@)J
9@ 9 @
2= 4 . 2 " 8
) " )
= 6= ! 6 I@)J
3 " 83
9 B 7 9
3 6 3 ""
3 3
3 3
B 8 I@)J
B " 1 " " ) 966
B I@)J
5 " ! "" 5
) ) I@)J
) ) I@)J
'#%$#%'$$5 '$$

9 9 "78
9 9 I@)J
) 46 8 " 9 2 6
9 9 7 I@)J
4 47 B I@)J
7 8 " 7 3 ""
) 7 8 " ) "
32 3 2 I@)J
31 683 7 1 6 " I@)J
1 . I@)J
2 " 2 I@)J
6 I@)J
) : 86 B 6:
)) 86 B ) 6
2 2
2 ) 2 )
2 2
2 2 " I@)J
2 2
2 I5J 2 5
2 2 "
2 1 2 6 81
2 2 I 2 # J
2 ) 2 ) "
I 2 # )J
2 9 2 9
:'39 : : 9 6 8 I@)J
:9 : 9 = ! 9 6 I@)J
: : I@)J
93 " 9 3
B
)4 ) " 46 " ? "
= = "
= = "
) )3
= " 7 7 "6 "
= " 2
'#%$#%'$$5 '$<

) 46 8 " 9 2 6
= " ! 8 "7 !
= "
= " 2 " ! = "
8! . )3
49 2 4 ? 9 "
2 "
4@ N 47 B
43) 4 . 3 7 )
4 4 F 6"
4 9 46 7 9
4 47 I@)J
4 46 8 "
4 2 46 8 " 2
9= 9 = ! I@)J
K 8
9 7 9
M M 8
1 3 1 F 3 ""
1 34 " I@)J
1 1 8 8
1 3 1 " 3
9 : 89 6:
9 9 I@)J
3 3 ""
34 8 3 4 I@)J
9 89 I@)J
2 7 7 2 "
2 2
) "6 )
49 4 9
49 "6 47 B 9
7.
8 I@)J
'#%$#%'$$5 '$'

) 46 8 " 9 2 6
8 ? I@)J
I@)J
8 : 8 ? 6:
)3 ) 6 3
)3 ) " 3 "6
) ) 6 B6 6
)19 34 ) 9 3 "7 7 8
) )
@ @
66 " 8
) >%

Appendix B - REFERENCES
) 46 8 " 9 2 6
" ) ! " 7
6 7 / "
! 7 " /
C

) 46 8 " 9 2 6
C'$D 8 :* 4 9. 8 :. 8 .

) 46 8 " 9 2 6
C#>D G4 9 " 8H 46 7 9
4 9.) . . 8.

) 46 8 " 9 2 6
C5

) 46 8 " 9 2 6
Appendix C - OVERVIEW OF THE UML TERMINOLOGY
USED IN THIS DOCUMENT
13.2 Collaborations
G9 7 8 " !
6 " 6 7 E 7 " 6 / 9
7 6 ! " I
"6 J 6 ? 78
6 8 6 6 ! 8HC'D/
3 7 6 7 " ! B6
? 3 78C#D/
13.3 Work Item
) " ! " 7 " : 7 B )
" 7 ! ! 8 "
/ 9 B"6 7 6 966
3 8 " 7 6 8" ! "/
13.4 Components
3 "6 " 7 7 7 B ! 8 6
"6 B ! / 3 "7 "6
7 78 8 " 4 ! 6 / 3 "6 7 "6 "
! 7 8 6 "6 " /
13.5 Diagrams
13.5.1 Class Diagram
9 " ! ? 7 ! I86 J
7 /
13.5.2 Sequence Diagram
? 8 " 7 ! 47 % 3 "6 / 47
! 7 ! 6
66 /
13.5.3 Activity Diagram
2 B 7 9 8 " " ! / 9
6 F " 8 " 6 " 7
8 " 6 7 /
13.5.4 Component Diagram
? "6 ! 6 1 2"6 " /
13.5.5 Deployment Diagram
13.6 Views
" ! 8 "/
1 .4 B6 " !6
! ! 6 ? ! ! 8/
'#%$#%'$$5 '$>

) 46 8 " 9 2 6
2 B ) !6 66 / ) 6 !
: ! 2"6 " !
13.6.1 The Enterprise View
" G H6 8 " 4 !/
" " ! 7 "
7 / ) 6 ! 7 7 " /
13.6.2 Logical View
) ! 6 8 3 3 7
78 '/< 3 1 F " 7 6 !/
) 6 "
" 7 /
13.6.3 Implementation View
) 3 47 78 : ! 7
3 "6 " 6 8" "/
'#%$#%'$$5 '$&

Appendix D - INDEX
C+*;,, *( '>
9
1223, 130
66 .

"6 " .

1 *. '> #$ #<