Passer au contenu
Français
Portail client
Contact
  • Il n'y a aucune suggestion car le champ de recherche est vide.

1. INTRODUCTION

Emplacement : Documentation ICS2 > Interface Control Document

DOCUMENT PURPOSE

The purpose of this document is to describe the overall technical Common System Specifications of the ICS2 System-to-System (S2S) Trader Interfaces. In particular, this document provides specifications and lays out applicable guidelines to support the technical implementation of IT system-to-system interfaces between the ICS2 Trader Interfaces (ICS2 TI) and the connectivity access points used by Economic Operators in the context of the ICS2 system.

Each Member State has the option to develop a National Trader Interface (NTI) or use the Shared Trader Interface (STI) implementation. These implementations must be compliant to the Harmonised Trader Interface specifications (HTI) which are the subject of this document.

TARGET AUDIENCE

The main target audience for this document is the Economic Operators and/or the IT service providers who are responsible for the implementation and maintenance of interfaces between the EO system and the ICS2 TI, as well as national administrations implementing a NTI or participating in the STI.

Readers are assumed to have a good understanding of general IT architectural concepts and may belong to the following categories:

  • Economic Operators;
  • EO IT system providers;
  • DG TAXUD units responsible for ICS2 TI implementation;
  • Member States responsible for ICS2 TI implementation;
  • External Contractors involved in ICS2 development or operational activities.

SCOPE

The scope of this document is to define:

  • The technical and operational aspects of the ICS2 system-to-system Trader Interface with a link to the functional specifications;
  • The interfaces and services to be implemented at ICS2 TI with a view to be consumed by the access point used by an Economic Operator (EO);
  • The interfaces and services to be implemented by the access point used by an EO with a view to be consumed by the ICS2 TI;
  • The message exchange protocol between the ICS2 TI and the access point used by an EO, including the technical specificities of its implementation for ICS2;
  • The operational aspects of the interface to be applied, e.g. the necessary actions to be taken in order to enroll and register an access point as an ICS2 system actor, the testing, connection and message exchange actions with the ICS2 TI, etc.

In addition, it is in the scope of this document to describe supporting and operational elements of the interfaces, such as security aspects, certain Operational Service Level and Change Management aspects.

The ICS2 system is implemented in an incremental way: a series of blocks define the roadmap for its implementation along three releases. The scope of this document was originally release 1 and has been updated to include the impact of release 2 and release 3. The document is applicable to all releases.

STRUCTURE

The present document contains the following chapters:

  • Chapter 1: Introduction describes the scope and the objectives of the document;
  • Chapter 2: Overview provides an overview of the functional, technical and operational aspects of the ICS2 system-to-system Trader Interface, as well as the context of this interface in the ICS2 environment;
  • Chapter 3: Functional Information Exchange Specifications describes the functional specification of the services, the information exchange messages and the orchestration of information exchange between the access point used by an EO and the ICS2 TI, including the rules and conditions;
  • Chapter 4: Technical Information Exchange Specifications describes the technical specification of the selected message exchange protocol between the ICS2 TI and the access point used by an EO, including the technical specificities of its implementation;
  • Chapter 5: Operational describes the operational aspects of enrolling, registering, testing and successfully setting-up an interface between the access point used by an EO and the ICS2 TI;
  • Annex 1: Service operations provides a list of service operations and their payloads;
  • Annex 2: P-Modes Summary provides a summary of the P-modes;
  • Annex 3: Sample Message Scenario provides an example scenario of an information exchange with the help of messages;
  • Annex 4: ebMS Errors lists the errors returned during problematic message exchanges;
  • Annex 5: Message Layer Security Controls describes how message level security controls are applied.
  • Annex 6: Example describes an AS4 message.

REFERENCE DOCUMENTS

Table 1: Reference documents

APPLICABLE DOCUMENTS

  • A01 — Title : SOFT-DEV Framework Contract ; Reference : TAXUD/2021/CC/162 ; Version : N/A ; Date : 24/06/2021
  • A02 — Title : Specific Contract 01 ; Reference : TAXUD/2021/DE/173 ; Version : N/A ; Date : 07/09/2021
  • A03 — Title : CD3-FQP-Framework Quality Plan ; Reference : DG TAXUD ; Version : 1.30 ; Date : 14/05/2020

Table 2: Applicable documents

ABBREVIATIONS & ACRONYMS

For a better understanding of the present document, the following table provides a list of the principal abbreviations and acronyms used.

See also the ‘list of acronyms’ on TEMPO.

  • AEO — Definition : Authorised Economic Operator
  • AEOS — Definition : Authorised Economic Operator – Safety and Security
  • AS4 — Definition : Applicability Statement 4
  • CA — Definition : Certificate Authority
  • CR or ICS2 CR — Definition : ICS2 Common Repository
  • DG TAXUD — Definition : Directorate-General Taxation and Customs Union
  • ebMS — Definition : ebXML Messaging Services
  • eIDAS — Definition : Electronic Identification Authentication and trust Services
  • ENS — Definition : Entry Summary Declaration
  • EO — Definition : Economic Operator
  • EORI — Definition : Economic Operator Registration and Identification
  • EUCTP — Definition : EU Customs Trader Portal
  • ERDS — Definition : Electronic Registered Delivery Service
  • HRCM — Definition : High Risk Cargo and Mail
  • HTI — Definition : Harmonised Trader Interface
  • ICS2 — Definition : Import Control System 2
  • ITSP — Definition : IT Service Provider
  • LOTL — Definition : List of Trusted Lists
  • LRN — Definition : Local reference number
  • MEP — Definition : Message Exchange Pattern
  • MIME — Definition : Multipurpose Internet Mail Extensions
  • MS — Definition : Member State
  • MSH — Definition : Message Service Handler
  • MRN — Definition : Movement Reference Number
  • NES — Definition : National Entry System
  • NTI — Definition : National Trader Interface
  • NVOCC — Definition : Non-Vessel Operating Common Carrier
  • RMS — Definition : Responsible Member State
  • S2S — Definition : System-to-System
  • SOA — Definition : Service Oriented Architecture
  • SOAP — Definition : Simple Object Access Protocol
  • SOFTDEV — Definition : Development, Maintenance and Support of Customs and Taxation Information Systems
  • STI — Definition : Shared Trader Interface
  • TAPAS — Definition : DG TAXUD AS4 Access Point
  • TI or ICS2 TI — Definition : ICS2 Trader Interface
  • TES — Definition : Trans-European System
  • U2S — Definition : User to System
  • UI — Definition : User Interface
  • UUID — Definition : Universal Unique Identifier
  • UUM&DS — Definition : Uniform User Management and Digital Signatures
  • XML — Definition : Extensible Markup Language
  • XPath — Definition : XML Path Language

Table 3: Abbreviations and acronyms

DEFINITIONS

For a better understanding of the present document, the following table provides a list of the principal terms used.

See also the ‘glossary’ on TEMPO.

  • AS4 — Definition : AS4 (Applicability Statement 4) is a Conformance Profile of the OASIS ebMS 3.0 specification and represents an open standard for the secure and payload-agnostic exchange of Business-to-business documents using Web services.
  • AS4 access point — Definition : An AS4 access point is an operational IT component that implements the AS4 specifications for the exchange of information with other AS4 access points, be it a Trader Interface (STI/NTI) or an access point used by an Economic Operator (EO).
  • Carrier — Definition : Carrier means in the context of entry, the person who brings the goods, or who assumes responsibility for the carriage of the goods, into the customs territory of the Union. However, in the case of combined transportation, "carrier" means the person who operates the means of transport which, once brought into the customs territory of the Union, moves by itself as an active means of transport; in the case of maritime or air traffic under a vessel- sharing or contracting arrangement, "carrier" means the person who concludes a contract and issues a bill of lading or air waybill for the actual carriage of the goods into the customs territory of the Union. (Definition is from ICS2 definitions [R03])
  • Certificate Authority — Definition : A Certificate Authority (CA) is an entity that issues digital certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate. This allows others (relying parties) to rely upon signatures or on assertions made about the private key that corresponds to the certified public key. A CA acts as a trusted third party—trusted both by the subject (owner) of the certificate and by the party relying upon the certificate. The format of these certificates is specified by the X.509 standard.
  • Electronic Certificate — Definition : An electronic or digital certificate is an attachment to an electronic message used for security purposes. The most common use of a digital certificate is to verify that a user sending a message is who he or she claims to be, and to provide the receiver with the means to encode a reply. An individual wishing to send an encrypted message applies for a digital certificate from a Certificate Authority (CA). The CA issues an encrypted digital certificate containing the applicant's public key and a variety of other identification information. The CA makes its own public key readily available through print publicity or perhaps on the Internet.
  • Electronic seal3 — Definition : According to the eIDAS regulation, an electronic seal is a piece of data attached to an electronic document or other data, which ensures data origin and integrity. Technically similar to digital signatures, electronic seals serve as evidence that an electronic document was issued by a specific legal entity, not a natural person.
  • High Risk Cargo and Mail Screening (HRCM screening) — Definition : High Risk Cargo and Mail Screening (HRCM screening) is a notification communicated by the customs authority of the RMS to the person filing (and the carrier under certain conditions) that the goods concerned shall need to be screened as a high risk cargo and mail, in accordance with the point 6.7.3 of the Annex to Commission Decision C (2010) 774 of 13 April 2010, before being loaded on board of an aircraft bound to the customs territory of the Union. (Definition is from ICS2 definitions [R03])
  • IT Service Provider — Definition : An IT Service Provider (ITSP) is a legal person contracted by a Person filing for services involving the delivery and reception of messages to and from ICS2 TI. An IT Service Provider must be identified and registered by Customs to be authorised to exchange messages with TI. Any EO can have its own system or make use of services from one or several ITSPs for the delivery of ICS2 messages to Customs (via STI/NTI). The use of these services must be covered by a contractual arrangement where the EO assumes the responsibility of any information sends by the ITSP to Customs.
  • Payload — Definition : The present document refers to the term “payload” as the XML encoded data-set defined for information exchange as defined in the ICS2 Information Exchange Message definition document [R04]. For the technical realisation of an information exchange between two parties (a Sender and a Trader Interface), a payload is embedded in an AS4 message.
  • Person filing — Definition : Person filing means any person that submits to the customs authority ENS filing in its complete or partial content and other notifications in the prescribed form and manner. This person can be any person that issues a bill of lading or air waybill and can be either carrier, NVOCC (i.e. freight forwarder), or any person identified by the legal provisions obliged to submit required particulars of ENS to the customs and can include postal operator, consignee stipulated in the lowest bill of lading. Person filing also includes a representative of any of the persons mentioned above that submits the ENS filing in its complete or partial content to the customs authority on behalf of the person that it is representing. (Definition is from ICS2 definitions [R03])
  • Sender — Definition : The present document refers to the term "sender" as the system sending the technical messages to the TI. This can be a system implemented by the EO lodging the ENS filings or by an IT Service Provider. The sender is understood as a system actor in the ICS2 system context and is the one authenticated and authorised from the system security point of view.
  • Signal Message — Definition : An AS4 Message is a logical unit which consists of User Messages or Signal Messages or both. A Signal Message is an ebMS message that contains a Signal Message unit (an eb:Messaging/eb:SignalMessage XML structure) and allows transmitting data interpreted by an AS4 Message Service Handler as a signal (e.g. a pull signal).
  • Trader Interface — Definition : Trader Interface: The TI represents the IT system that will be used by Economic Operators to communicate with customs authorities in the context of ICS2. It is an abstraction of: The National Trader Interface (NTI), developed, hosted and operated by a particular Member State; The Shared Trader Interface (STI), developed, hosted and operated by DG TAXUD.
  • User Message — Definition : An AS4 Message is a logical unit which consists of User Messages or Signal Messages or both. A User Message is a message that contains a User Message unit (an eb:Messaging/eb:UserMessageXML structure) and allows transmitting data interpreted by a Consumer.

Table 4: Definitions

3 This electronic seal must not be confounded with the physical electronic seals attached to shipping containers.

Source : https://mgi-team.atlassian.net/wiki/spaces/DOCI5/pages/3348037668