{"id":440777,"date":"2024-10-20T08:17:26","date_gmt":"2024-10-20T08:17:26","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-cen-iso-ts-194682022-tc\/"},"modified":"2024-10-26T15:28:52","modified_gmt":"2024-10-26T15:28:52","slug":"bsi-pd-cen-iso-ts-194682022-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-cen-iso-ts-194682022-tc\/","title":{"rendered":"BSI PD CEN ISO\/TS 19468:2022 – TC"},"content":{"rendered":"
This document defines and specifies component facets supporting the exchange and shared usage of data and information in the field of traffic and travel. The component facets include the framework and context for exchanges, the data content, structure and relationships necessary and the communications specifications, in such a way that they are independent from any defined technical platform. This document establishes specifications for data exchange between any two instances of the following actors: \u2014 Traffic information centres (TICs); \u2014 Traffic control centres\/Traffic management centres (TCCs\/TMCs); \u2014 Service providers (SPs). This document can also be applied for use by other actors, e.g. car park operators. This document includes the following types of information: \u2014 use cases and associated requirements, and features relative to different exchange situations; \u2014 different functional exchange profiles; \u2014 abstract elements for protocols; \u2014 data model for exchange (informational structures, relationships, roles, attributes and associated data types required). In order to set up a new technical exchange framework, it is necessary to associate one functional exchange profile with a technical platform providing an interoperability domain where plug-and-play interoperability at a technical level can be expected. The definition of such interoperability domains is out of scope of this document but can be found in other International Standards or Technical Specifications (e.g. the ISO 14827 series). This document is restricted to data exchange. Definition of payload content models is out of the scope of this document.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
1<\/td>\n | 30479842 <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | A-30420949 <\/td>\n<\/tr>\n | ||||||
194<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
196<\/td>\n | European foreword Endorsement notice <\/td>\n<\/tr>\n | ||||||
200<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
202<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
205<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
208<\/td>\n | 4 Symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
209<\/td>\n | 5 Exchange modeling framework 5.1 Overview 5.2 Business scenarios and functional exchange profiles <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | 5.3 Requirements, features and exchange patterns <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | 5.4 Business scenario: information delivery 5.4.1 Overview <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | 5.4.2 Requirements 5.4.3 Data delivery exchange pattern 5.4.4 Specific exchange pattern specification PIMs included in this document 5.5 Business scenario: collaborative ITS services 5.5.1 Overview <\/td>\n<\/tr>\n | ||||||
214<\/td>\n | 5.5.2 Data exchange-enabling service request and feedback paradigm <\/td>\n<\/tr>\n | ||||||
215<\/td>\n | 5.5.3 Requirements 5.6 Exchange data model 5.7 Data exchange features 5.7.1 Context diagram <\/td>\n<\/tr>\n | ||||||
216<\/td>\n | 5.7.2 Features <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | 5.8 Exchange pattern modeling using UML <\/td>\n<\/tr>\n | ||||||
224<\/td>\n | 6 Snapshot pull 6.1 Overview <\/td>\n<\/tr>\n | ||||||
225<\/td>\n | 6.2 Exchange pattern messages definition 6.2.1 Overall presentation <\/td>\n<\/tr>\n | ||||||
226<\/td>\n | 6.2.2 Exchange pattern definition <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 6.2.3 Relevant exchange information in exchange data model 6.2.4 Exchange messages 6.3 State diagrams 6.4 Features implementation description 6.4.1 Overview <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | 6.4.2 Subscription contract 6.4.3 Session 6.4.4 Information management <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | 6.4.5 Data delivery <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | 6.4.6 Self-description 6.4.7 Communication 6.4.8 General optimization issues 7 Snapshot push 7.1 Overview <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | 7.2 Exchange pattern messages definition 7.2.1 Overall presentation 7.2.2 Basic exchange pattern <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | 7.2.3 Relevant exchange information in exchange data model <\/td>\n<\/tr>\n | ||||||
234<\/td>\n | 7.2.4 Exchanged messages 7.3 State diagrams 7.4 Features implementation description <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | 7.4.1 Subscription contract 7.4.2 Session 7.4.3 Information management 7.4.4 Data delivery <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | 7.4.5 Self-description 7.4.6 Communication\/protocol 7.4.7 General optimization issues 8 Simple push 8.1 Overview <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | 8.2 Exchange pattern messages definition 8.2.1 Overall presentation <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | 8.2.2 Basic exchange pattern <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | 8.2.3 Relevant exchange information from exchange data model <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | 8.2.4 List of exchanged messages <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | 8.3 State diagrams <\/td>\n<\/tr>\n | ||||||
244<\/td>\n | 8.4 Features implementation description 8.4.1 Overview 8.4.2 Subscription contract 8.4.3 Session <\/td>\n<\/tr>\n | ||||||
246<\/td>\n | 8.4.4 Information management 8.4.5 Data delivery <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | 8.4.6 Self-description 8.4.7 Communication\/protocol 8.4.8 General optimization issues 9 Stateful push 9.1 Overview <\/td>\n<\/tr>\n | ||||||
248<\/td>\n | 9.2 Exchange pattern messages definition 9.2.1 Overall presentation <\/td>\n<\/tr>\n | ||||||
249<\/td>\n | 9.2.2 Basic exchange pattern <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | 9.2.3 Relevant exchange information from exchange data model <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | 9.2.4 List of exchanged messages 9.3 State Diagrams <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | 9.4 Features implementation description 9.4.1 Overview <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | 9.4.2 Subscription contract 9.4.3 Session <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | 9.4.4 Information management 9.4.5 Data delivery <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | 9.4.6 Self-description 9.4.7 Communication 9.4.8 General optimization issues <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | 10 Simple CIS 10.1 Overview 10.2 Exchange pattern and messages definition 10.2.1 Overall presentation <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | 10.2.2 Basic exchange pattern <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | 10.2.3 Relevant exchange information from exchange data model <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | 10.2.4 Exchanged messages <\/td>\n<\/tr>\n | ||||||
264<\/td>\n | 10.3 State diagrams <\/td>\n<\/tr>\n | ||||||
265<\/td>\n | 10.4 Features implementation description 10.4.1 Overview 10.4.2 Subscription contract 10.4.3 Session 10.4.4 Information management <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | 10.4.5 Self-description 10.4.6 Communication\/protocol 11 Stateful CIS 11.1 Overview <\/td>\n<\/tr>\n | ||||||
271<\/td>\n | 11.2 Exchange pattern and messages definition 11.2.1 Overall presentation <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | 11.2.2 Basic exchange pattern <\/td>\n<\/tr>\n | ||||||
274<\/td>\n | 11.2.3 Relevant exchange information from exchange data model <\/td>\n<\/tr>\n | ||||||
275<\/td>\n | 11.2.4 Exchanged messages <\/td>\n<\/tr>\n | ||||||
277<\/td>\n | 11.3 State diagrams <\/td>\n<\/tr>\n | ||||||
278<\/td>\n | 11.4 Features implementation description 11.4.1 Overview <\/td>\n<\/tr>\n | ||||||
279<\/td>\n | 11.4.2 Subscription contract 11.4.3 Session 11.4.4 Information management <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | 11.4.5 Self-description 11.4.6 Communication 12 Other PIM definitions <\/td>\n<\/tr>\n | ||||||
281<\/td>\n | Annex A (informative) Methodology presentation <\/td>\n<\/tr>\n | ||||||
283<\/td>\n | Annex B (normative) Definition of requirements <\/td>\n<\/tr>\n | ||||||
288<\/td>\n | Annex C (normative) Basic exchange data model and data dictionary <\/td>\n<\/tr>\n | ||||||
321<\/td>\n | Annex D (informative) Introduction to communications and protocols <\/td>\n<\/tr>\n | ||||||
326<\/td>\n | Annex E (informative) Major functional exchange profile and exchange patterns for information delivery <\/td>\n<\/tr>\n | ||||||
328<\/td>\n | Annex F (informative) Data delivery background: stateless and stateful information with information life cycle management <\/td>\n<\/tr>\n | ||||||
330<\/td>\n | Annex G (informative) Collaborative ITS services (CIS) background <\/td>\n<\/tr>\n | ||||||
343<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Intelligent transport systems. Data interfaces between centres for transport information and control systems. Platform-independent model specifications for data exchange protocols for transport information and control systems<\/b><\/p>\n |