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

2. OVERVIEW

Emplacement : Documentation ICS2 > Interface Control Document

The Interface Control Document of the ICS2 Trader Interface defines the technical and operational aspects of the ICS2 system-to-system Trader Interface with a link to the functional specifications. It also provides guidelines for the adequate implementation of the interfaces.

It is assumed that the reader is aware of the functional context of the ICS2 system as described in;

  • The ICS2 Business Process Description [R02];
  • The ICS2 Definitions [R03];
  • The ICS2 Information Exchange Message Specifications [R04]. More details on the provided services can be found in:
  • The ICS2 Service Specification Documents [R05];
  • The ICS2 Technical Service Contracts [R06].

Figure 1 defines the context of this interface in the ICS2 environment.

Figure 1: ICS2 overview In the context of the ICS2 programme, an Economic Operator must interact with the various ICS2 components through the ICS2 Trader Interface. 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 with the Harmonised Trader Interface specifications.

‌

A trader must connect to a specific Trader Interface system (National or Shared) according to the Member State of the Customs Office of First Entry (COFE) specified inside the ENS Filing or (if unknown) to the Member State to which the ENS Filing will be addressed.

The ICS2 Trader Interfaces (National or Shared) interact with the ICS2 Common Repository (CR) which is responsible for the ENS lifecycle management (i.e. linking all relevant ENS filings) as well as for orchestrating the risk management process with the relevant NES systems.

The interactions between the ICS2 Common Repository and NES systems occur over the Common Communication Network (CCN2ng). The Uniform User Management and Digital Signatures system (UUM&DS) will support the security measures with registration, identification and authorisation functionality.

The Economic Operator has the choice to interact with a Trader Interface through a web user interface4, or through a system-to-system interface. Only the latter interface is in scope of this document. The interfaces will be implemented according to the Connecting Europe Facility (CEF) eDelivery building block specifications which are aligned with the eIDAS requirements for ERDS (Electronic Registered Delivery Service) as defined in Article 3(36)5.

For the technical realisation of these system-to-system interfaces, AS4 access points have to be used accordingly to the eDelivery building block specifications. From a trade perspective, such an access point can be implemented and operated by an Economic Operator himself or can be delivered by an IT Service Provider (ITSP) as a service to an Economic Operator.

As described in more details in the document, the system-to-system interaction occurs over a secure HTTPS connection on the public internet using the AS4 secure and reliable messaging protocol.

‌

4 Web user interface for trade will only be available from ICS2 Release 2 onwards.

5 The eIDAS regulation (EU regulation № 910/2014 of 23 July 2014 on electronic identification and repeals directive 1999/93/EC with effect from 30 June 2016) oversees electronic identification and trust services for electronic transactions in the European Union's internal market and regulates electronic signatures, electronic transactions, involved bodies and their embedding processes to provide a safe way for users to conduct business online. Article 3(36) reads as follows: “(36) ‘electronic registered delivery service’ means a service that makes it possible to transmit data between third parties by electronic means and provides evidence relating to the handling of the transmitted data, including proof of sending and receiving the data, and that protects transmitted data against the risk of loss, theft, damage or any unauthorized alterations;”.

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