Shopping Cart

No products in the cart.

BSI PD CEN/TS 15448:2014

$215.11

Postal services. Open standard interface between image controller and enrichment devices (OCRs, video coding systems, voting systems)

Published By Publication Date Number of Pages
BSI 2014 242
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

The purpose of this Technical Specification is to define the requirements of the OCR/VCS Standard interface and to convey these requirements in context to the reader.

This document is arranged under 4 main clauses as described in Figure 1:

  • UCM (Use Case Model) describes the use cases for the IC/ED Interface using sequence diagrams with messages.

  • IDD (Interface Design Description) defines the data model for the IC/ED interface.

  • SDD (System Design Description) defines the mandatory specification of the IC/ED interface in terms of architecture, services and behavioural models. In the Common Part of this clause no middleware or transport layer is specified. The common part of this clause is intended to be middleware-independent.

  • SDD-TCP/IP, SDD-CORBA, in these specialized clauses. The specifications for 2 compatible transport solutions TCP/IP, CORBA are provided. Further middleware solutions (such as SOAP) can be added when available, provided that they are fully compatible with the Common Part.

As shown on Figure 2, there are many interfaces from an Enrichment Device to the rest of the system. This document is only concerned with the Mailpiece Processing part of the complete Standard Interface.

The mailpiece processing is concerned with the passing of a mailpiece to an Enrichment Device for processing.

Figure 3 depicts the system model of an Enrichment Device. As visible on the figure, an Enrichment Device is one of:

a single or a pool of automatic recognition and interpretation engines, which are capable of retrieving information from an image of a mailpiece without human intervention;

a single or a pool of video coding desks, which produce results from images of mailpieces; all tasks related to the management of the coders and the coding desks are encapsulated within the VCS system, or are accessible via interfaces which are outside the scope of the interface described within this document;

a system which can determine the most appropriate result for a mailpiece using data and/or an image of a mailpiece; typically, a voter determines the most appropriate result from two or more results.

This document therefore covers the Mailpiece Processing interface between the Image Controller and the Enrichment Devices.

The document describes the requirements in the case of real-time enrichment: operational mode of an Enrichment Device, where the ED replies within the specified expiration time to the IC; the IC has to keep track of all mailpieces waiting for a reply from an ED. The ED does not keep persistence of mailpieces outside a channel connection with the IC. The ED has to have the processing power available to enrich a mailpiece. There is one and only one response for a mailpiece.

A later version of the document shall describe the case of deferred enrichment: operational mode of an Enrichment Device, where the ED may pre-request mailpieces from the IC. The ED has to keep persistence of the mailpiece to enrich it later and keep the result available for a result request from the IC. There is no response expected by IC from the ED.

The interface between Image Controller and Image Controller is NOT part of this document.

Furthermore, there may be many IC connected to many ED’s, as shown in the following object model:

The submission strategy in case of one IC connected to many ED’s is not part of the interface. It is for optimizing the mail flow in case of identical ED’s, or for defining the order in which different ED’s are activated (cascaded versus parallel submission).

The submission strategy of the IC shall be part of the specification and certification of the IC, which is not part of this document.

PDF Catalog

PDF Pages PDF Title
4 Contents Page
8 1 Scope
11 2 Normative references
3 Terms and definitions
13 4 Symbols and abbreviations
5 The Use Case Model (UCM)
5.1 General
14 5.2 Overall Description
5.2.1 General
5.2.2 Use-Case Model Survey
5.2.2.1 General
5.2.2.2 Connection Use Case Model
15 5.2.2.3 Channel Use Case Model
17 5.2.3 Assumptions and Dependencies
5.2.3.1 Image supply
5.2.3.2 Control
5.2.3.3 Output
5.2.3.4 Enrichment
5.2.3.5 Data Representation
18 5.2.3.6 Image Representation
5.2.3.7 Channel Concept
20 5.2.3.8 Client/server model
21 5.2.3.9 Server Selection Service
5.2.3.10 Connection Sequence
5.2.3.11 Flow Control Model
24 5.3 Specific Requirements
5.3.1 Use-Case Reports
5.3.1.1 UC001 – Publish Presence
25 5.3.1.2 UC002 – Connect
32 5.3.1.3 UC003 – Disconnect
34 5.3.1.4 UC004 – Open Channel
36 5.3.1.5 UC006 – Get Enrichment Device Status
37 5.3.1.6 UC101 – Close Channel
40 5.3.1.7 UC102 – Control Flow
42 5.3.1.8 UC103 – Request Channel Status
44 5.3.1.9 UC104 – Submit Mailpiece
45 5.3.1.10 UC105 – Transmit Result
47 5.3.2 Supplementary Requirements
5.3.3 Rejections
5.3.3.1 General
5.3.3.2 Discarded Use Cases
48 6 Interface Design Description IDD
6.1 Purpose
49 6.2 Scope of IDD
6.3 Prerequisites
6.4 Overview
50 6.5 Section A – TIFF Definition
6.5.1 Tiff Usage
6.5.1.1 General
51 6.5.1.2 General Baseline TIFF Tags
6.5.1.3 Image Type Related Baseline TIFF Tags
52 6.5.1.4 Additional Baseline TIFF Tags
53 6.5.1.5 TIFF Extensions Tags
55 6.6 Section B – Mailpiece Data Definition
6.6.1 Requirements
6.6.1.1 General
6.6.1.2 Use Cases
57 6.6.1.3 Non-Functional Requirements
59 6.6.2 Model Commitments
6.6.2.1 Namespaces
60 6.6.3 Domain Data Model & Types
6.6.3.1 General
63 6.6.3.2 Domain Instance Types
85 6.6.3.3 Domain Generic Types
96 6.6.3.4 Customer Specific Domain Types
101 6.6.3.5 Domain Base Types
124 6.6.3.6 Domain Primitives
126 6.6.3.7 Region Location
134 7 System Design Description (SDD) – Common Part
7.1 Purpose
135 7.2 Overview
7.3 Architectural Goals and Constraints
7.3.1 General
136 7.3.2 Client Server Model
7.3.3 Client / Servant Relationships
138 7.3.4 Server Selection
139 7.4 Service Model
7.4.1 Overview
141 7.4.2 Exception Handling
7.4.3 Logical link between IC and ED services
7.4.4 Interface: IEnrichmentDevice
7.4.4.1 General
142 7.4.4.2 Service: connect()
7.4.4.3 Service: getCapabilities()
143 7.4.4.4 Service: openChannel()
7.4.4.5 Service: getEDState()
144 7.4.4.6 Method: requestChannelState()
7.4.4.7 Method: closeChannel()
7.4.4.8 Method: submitMailpiece()
145 7.4.4.9 Service: disconnect()
7.4.5 Interface: IImageController
7.4.5.1 General
7.4.5.2 Service: connectAck ()
146 7.4.5.3 Service: capabilitySets
147 7.4.5.4 Service: putEDState()
7.4.5.5 Service: channelAck
148 7.4.5.6 Service: putChannelState()
7.4.5.7 Service: mailpieceAck
149 7.4.5.8 Service: transmitResult()
7.4.6 Data definition
7.5 Behavioural Model
150 8 System Design Description (SDD) – Middleware dependent parts
8.1 SDD TCP/IP Implementation
8.1.1 Communication layer
151 8.1.2 Server selection
8.1.3 Message definition
153 8.1.4 Behavioural Model
8.1.4.1 Connection
160 8.1.4.2 Open Channel
162 8.1.4.3 Close Channel
163 8.1.4.4 Flow Control
166 8.1.4.5 Disconnection
169 8.2 SDD CORBA Implementation
8.2.1 General
8.2.2 Server Selection
171 8.2.3 Exception Handling
8.2.4 ORB Implementation
8.2.5 Interface Definition
8.2.5.1 General
8.2.5.2 Interface: IEnrichmentDevice
172 8.2.5.3 Interface: IImageController
173 8.2.5.4 Data Types
174 8.2.6 Behavioural Model
8.2.6.1 Connect
184 8.2.6.2 Disconnect
191 8.2.6.3 Open Channel
194 8.2.6.4 Close Channel
196 8.2.6.5 Control Flow
201 8.3 SDD SOAP Implementation
202 Annex A (informative)Introduction to XML
A.1 Introduction to XML
A.1.1 General
A.1.2 XML Document Structure
A.1.2.1 General
A.1.2.2 Prolog
203 A.1.2.3 Body
A.1.2.4 Epilog
A.1.3 Introduction to XML Schema
A.1.3.1 General
A.1.3.2 XML schema components
205 A.2 XML Schemas
A.2.1 Domain Instance Types
A.2.1.1 XML messages
210 A.2.1.2 Enrichment Device Request (IC Output, ED Input)
A.2.1.3 Enrichment Device Response (ED Output , IC Input)
211 A.2.1.4 Enrichment Capability Set (ED Output , IC Request)
A.2.2 Base Types
219 A.2.3 Generic Types
221 A.2.4 Primitives
225 A.2.5 Example of a Customer specific Schema Definition
227 A.3 The XML Instance Document
A.3.1 Type Assignment in the Instance Document
228 A.3.2 Examples
A.3.2.1 General
A.3.2.2 Enrichment Device Request
232 A.3.2.3 Enrichment Device Response
236 A.3.2.4 Enrichment Device Capability Set
BSI PD CEN/TS 15448:2014
$215.11