Chapter 1 - ERTICO.com

More documents

Recommendations

Info

3.6 Consistency with IP-level Deliverables DEL_RSQ_3_1 Architecture and Interface Specifications Any information that refers to an IP-level deliverable but that is not yet incorporated by this IP-level deliverable is indicated in “Track Changes/Highlight Changes” format. In the absence of this format, this SP-level deliverable can be assumed to be fully consistent with the IP-level deliverable to which it refers. This is the version of the IP-level deliverable that this deliverable refers to: • DEL_GST_3_1_v4.2.doc. or (at a later stage) • DEL_GST_3_2_v1.2.doc. All the diagrams included within this deliverable refers to: • MOD_GST_RSQ_v2.0.EAP 3/23/2006 26 Version 2.0
<strong>Chapter</strong> 4 - SYSTEM OVERVIEW 4.1 Introduction The RESCUE project goals [8] are listed below; DEL_RSQ_3_1 Architecture and Interface Specifications ° identify requirements of users, manufacturers, operators and emergency services for RESCUE application, information exchanges and services; ° achieve a Europe-wide consensus on a single harmonised RESCUE system based on adaptation of existing and new technology and systems; ° define operational procedures and arrangements for all stages of the RESCUE functionalities; ° develop prototypes at the UK stakeholders and closely follow the developments in the GST Open Systems and GST test sites relevant for RESCUE; ° trial the system in a dedicated UK RESCUE test site and in addition trial the system in different scenarios at currently two GST test sites in Europe (Italy and Germany); ° validate the system via simulated tests and real life testing in the UK site and gather information from the GST test sites relevant to RESCUE; ° work towards ensuring the take-up of the RESCUE solution in non-participating countries via a project Forum. It is the visionary goal of the consortia that all public and <strong>com</strong>mercial organisations providing RESCUE services adapt to the RESCUE related specifications. GST allows the construction of the totally integrated incident response chain, which will ensures the fastest and most effective response to a incident – including availability of incident data at all levels in the emergency chain, ensuring a fast and safe route to the incident and ensuring the interaction between emergency vehicles and other road users and the exchange of information between rescue units and control rooms for e.g. medical intervention. 3/23/2006 27 Version 2.0
Page 1 and 2: Global System for Telematics Releas
Page 3 and 4: DEL_RSQ_3_1 Architecture and Interf
Page 19 and 20: Chapter 1 - INTRODUCTION 1.1 Intend
Page 25: GST has selected the following UML
Page 29 and 30: 4.2 PSAP1, PSAP2 and Telco Roles DE
Page 43 and 44: Emergency Service Vehicle (ESV) DEL
Page 45 and 46: Reference Point Name RP-RSQ-002 Veh
Page 47 and 48: Reference Point Name RP-RSQ-005 Ser
Page 65 and 66: PSAP2 - Emergency Data Retrieving f
Page 69 and 70: ESV - Reset Transmission ESV - Cust
Page 77 and 78:
DEL_RSQ_3_1 Architecture and Interf
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Collaboration DEL_RSQ_3_1 Architect
Page 85 and 86:
6.1.3 Interfaces DEL_RSQ_3_1 Archit
Page 87 and 88:
activated. DEL_RSQ_3_1 Architecture
Page 89 and 90:
Page 91 and 92:
6.2.4 API Specification Class Diagr
Page 93 and 94:
tatus Unit (TCU-PV) Device 4 Connec
Page 95 and 96:
Page 97 and 98:
6.3.5 Interactions DEL_RSQ_3_1 Arch
Page 99 and 100:
Page 101 and 102:
6.4.3 Interfaces cd UC RSQ 001 - PV
Page 103 and 104:
3. reduces the time-to-market; 4. r
Page 105 and 106:
Page 107 and 108:
Field Name Description Value OrigTr
Page 109 and 110:
TR-End Request - Indication Close t
Page 111 and 112:
Information Element Description CCI
Page 113 and 114:
Information Element Description Tim
Page 115 and 116:
MSD component part of the sendMSD i
Page 117 and 118:
SendData () public: void Disconnect
Page 119 and 120:
Chapter 7 - PSAP ECALL DEL_RSQ_3_1
Page 121 and 122:
Page 123 and 124:
7.1.6 Lifecycles DEL_RSQ_3_1 Archit
Page 125 and 126:
7.2.3 Interfaces DEL_RSQ_3_1 Archit
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
finishIncident (int, int) public: v
Page 137 and 138:
7.4 UC RSQ 002 - PSAP1 - EOS DEL_RS
Page 139 and 140:
Page 141 and 142:
7.4.7 Interactions sd EOS Public Se
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
8.1.7 Interactions sd UC RSQ 003 -
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
8.2.6 API Specification Class Diagr
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
9.1.7 Interactions DEL_RSQ_3_1 Arch
Page 169 and 170:
9.1.8 Lifecycles DEL_RSQ_3_1 Archit
Page 171 and 172:
10.1.3 Interfaces DEL_RSQ_3_1 Archi
Page 173 and 174:
Page 175 and 176:
10.1.6 Lifecycles DEL_RSQ_3_1 Archi
Page 177 and 178:
Page 179 and 180:
The AcceptanceStatus element will c
Page 181 and 182:
Page 183 and 184:
Chapter 11 - ESV DRIVER SUPPORT DEL
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Railways Stations DEL_RSQ_3_1 Archi
Page 191 and 192:
Page 193 and 194:
Meteo conditions Traffic Worksites
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
11.1.7 Interactions DEL_RSQ_3_1 Arc
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
() DataFormatNegotiationR esult (In
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
ud UC RSQ 006 - ESV - Reset Transmi
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
TransmitWarning (WarningMsg) 12.3.7
Page 237 and 238:
12.3.8 Lifecycles ad UC RSQ 006 - E
Page 239 and 240:
12.4.3 Interfaces cd UC RSQ 006 - P
Page 241 and 242:
Page 243 and 244:
12.4.6 Lifecycles ad UC RSQ 006 - P
Page 245 and 246:
Page 247 and 248:
12.5.6 Lifecycles ad UC RSQ 006 - P
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
GetAvailableVAD () public: void Set
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
14.2.4 API Specification Class Diag
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
SetDestination () public: void GetC
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Chapter 15 - SECURITY 15.1 Check Se
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
CheckIfDataHasBeenSent () public: v
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
E-Call Handler [CP-RSQ-15.0, CP- RS
Page 311 and 312:
Page 313 and 314:
18.3.2 Nodes dd Deployment Diagrams
Page 315 and 316:
EmergencyDataReceiv er [CP-RSQ-6.0]
Page 317 and 318:
Handler “Accept Deployment” Mes
Page 319 and 320:
18.6 ESV Driver Support 18.6.1 Comp
Page 321 and 322:
HMIDriver User interface for the ES
Page 323 and 324:
Page 325 and 326:
Component Name Component Descriptio
Page 327 and 328:
Page 329 and 330:
Component Name Component Descriptio
Page 331 and 332:
18.9 Vehicle to Centre Communicatio
Page 333 and 334:
at ESV side. Third Party This node
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
The system consists of the followin
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
S->C: RTSP/1.0 200 OK CSeq: 892 Req
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
19.11.2 Legal Issues Data protectio
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
ID (short) Definition Additional ex
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
RTSP Real Time Streaming Protocol S
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Stations DEL_RSQ_3_1 Architectur
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435:
show all

Chapter 1 - ERTICO.com

Create successful ePaper yourself

Delete template?

Save as template?