{"id":403570,"date":"2024-10-20T05:06:41","date_gmt":"2024-10-20T05:06:41","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iso-128552022-tc\/"},"modified":"2024-10-26T09:07:26","modified_gmt":"2024-10-26T09:07:26","slug":"bs-en-iso-128552022-tc","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iso-128552022-tc\/","title":{"rendered":"BS EN ISO 12855:2022 – TC"},"content":{"rendered":"
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
264<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | European foreword Endorsement notice <\/td>\n<\/tr>\n | ||||||
273<\/td>\n | Foreword <\/td>\n<\/tr>\n | ||||||
274<\/td>\n | Introduction <\/td>\n<\/tr>\n | ||||||
277<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
278<\/td>\n | 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
279<\/td>\n | 4 Symbols and abbreviated terms <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | 5 Architectural concepts and information exchanges 5.1 Main roles in the toll charging environment <\/td>\n<\/tr>\n | ||||||
281<\/td>\n | 5.2 Information exchange between toll charging and provision 5.2.1 General <\/td>\n<\/tr>\n | ||||||
283<\/td>\n | 5.2.2 Basic protocol mechanisms <\/td>\n<\/tr>\n | ||||||
284<\/td>\n | 5.2.3 Exchange trust objects functionality 5.2.4 Originating and providing EFC context data functionality <\/td>\n<\/tr>\n | ||||||
285<\/td>\n | 5.2.5 Provide contract issuer information functionality 5.2.6 Manage exception list functionality <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | 5.2.7 Report toll declarations functionality 5.2.8 Report billing details functionality <\/td>\n<\/tr>\n | ||||||
287<\/td>\n | 5.2.9 Payment settlement functionality <\/td>\n<\/tr>\n | ||||||
288<\/td>\n | 5.2.10 Exchange enforcement data functionality <\/td>\n<\/tr>\n | ||||||
289<\/td>\n | 5.2.11 Process user complaints functionality 5.2.12 Exchange quality assurance parameters functionality <\/td>\n<\/tr>\n | ||||||
290<\/td>\n | 5.2.13 Provide media settlement data functionality 6 Computational specification 6.1 Overview <\/td>\n<\/tr>\n | ||||||
293<\/td>\n | 6.2 Application protocol data units 6.2.1 General <\/td>\n<\/tr>\n | ||||||
295<\/td>\n | 6.2.2 Application protocol control information (APCI) <\/td>\n<\/tr>\n | ||||||
296<\/td>\n | 6.2.3 Application data units 6.2.4 ADU identification <\/td>\n<\/tr>\n | ||||||
297<\/td>\n | 6.2.5 ADU action code 6.2.6 User identification <\/td>\n<\/tr>\n | ||||||
298<\/td>\n | 6.3 RequestAdu data structure <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | 6.4 AckAdu data structure <\/td>\n<\/tr>\n | ||||||
308<\/td>\n | 6.5 StatusAdu data structure 6.6 TrustObjectAdu data structure <\/td>\n<\/tr>\n | ||||||
315<\/td>\n | 6.7 EfcContextDataAdu data structure 6.7.1 General <\/td>\n<\/tr>\n | ||||||
316<\/td>\n | 6.7.2 GeneralContextData type <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | 6.7.3 MeshedContextData type <\/td>\n<\/tr>\n | ||||||
342<\/td>\n | 6.7.4 Common data structures <\/td>\n<\/tr>\n | ||||||
364<\/td>\n | 6.8 ContractIssuerListAdu data structure <\/td>\n<\/tr>\n | ||||||
366<\/td>\n | 6.9 ExceptionListAdu data structure <\/td>\n<\/tr>\n | ||||||
370<\/td>\n | 6.10 ReportAbnormalObeAdu data structure <\/td>\n<\/tr>\n | ||||||
371<\/td>\n | 6.11 TollDeclarationAdu data structure <\/td>\n<\/tr>\n | ||||||
375<\/td>\n | 6.12 BillingDetailsAdu data structure 6.12.1 General <\/td>\n<\/tr>\n | ||||||
377<\/td>\n | 6.12.2 UsageList data type <\/td>\n<\/tr>\n | ||||||
387<\/td>\n | 6.12.3 AssociatedEventData data type <\/td>\n<\/tr>\n | ||||||
393<\/td>\n | 6.13 PaymentClaimAdu data structure <\/td>\n<\/tr>\n | ||||||
395<\/td>\n | 6.14 PaymentAnnouncement Adu data structure <\/td>\n<\/tr>\n | ||||||
397<\/td>\n | 6.15 ProvideUserDetailsAdu data structure <\/td>\n<\/tr>\n | ||||||
401<\/td>\n | 6.16 ReportCccEventAdu data structure <\/td>\n<\/tr>\n | ||||||
402<\/td>\n | 6.17 ProvideUserIdListAdu data structure <\/td>\n<\/tr>\n | ||||||
403<\/td>\n | 6.18 Report QA data structure <\/td>\n<\/tr>\n | ||||||
404<\/td>\n | 6.19 User complaint data structure <\/td>\n<\/tr>\n | ||||||
405<\/td>\n | 6.20 User complaint response data structure <\/td>\n<\/tr>\n | ||||||
407<\/td>\n | 6.21 Media settlement data structure <\/td>\n<\/tr>\n | ||||||
408<\/td>\n | 7 Transfer mechanisms and supporting functions 7.1 Transfer mechanisms <\/td>\n<\/tr>\n | ||||||
409<\/td>\n | 7.2 Secure communication channel 7.3 Supporting functions 7.3.1 Communication services 7.3.2 Authenticators <\/td>\n<\/tr>\n | ||||||
411<\/td>\n | 7.3.3 Signature and hash algorithms 7.3.4 Keys encryption <\/td>\n<\/tr>\n | ||||||
412<\/td>\n | Annex A (normative) Data type specifications <\/td>\n<\/tr>\n | ||||||
413<\/td>\n | Annex B (informative) Example enforcement process applyingstandardized APDU exchanges <\/td>\n<\/tr>\n | ||||||
418<\/td>\n | Annex C (informative) Example of data flows in a toll domain <\/td>\n<\/tr>\n | ||||||
421<\/td>\n | Annex D (informative) Example of rounding differences <\/td>\n<\/tr>\n | ||||||
425<\/td>\n | Annex E (informative) Example of fee calculation using EFC context data <\/td>\n<\/tr>\n | ||||||
429<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Tracked Changes. Electronic fee collection. Information exchange between service provision and toll charging<\/b><\/p>\n |