HRG MCS – BMS Interface Control Document

HURGHADA INTERNATIONAL AIRPORT

Interface Control Document

MCS – BMS

AVIT – Aviation Information Technology Company Page 1

 HRG MCS – BMS Interface Control Document
Table of Contents

1.0 DOCUMENT REVISION ............................................................ 4

2.0 OVERVIEW ................................................................................. 5
2.1 DOCUMENT OBJECTIVES............................................................................................................................................... 6
2.2 FUNCTIONAL OBJECTIVES ............................................................................................................................................ 6
2.3 STANDARD AND REFERENCED DOCUMENTS ............................................................................................................. 7
2.4 INTERFACE IDENTIFICATION ....................................................................................................................................... 8

3.0 INTERFACE LAYERS ................................................................ 9

3.1 PHYSICAL LAYER ......................................................................................................................................................... 10
3.2 DATA LINK LAYER....................................................................................................................................................... 11
3.3 NETWORK LAYER ........................................................................................................................................................ 12
3.4 TRANSPORT LAYER...................................................................................................................................................... 13
3.5 SESSION LAYER ............................................................................................................................................................ 14
3.6 PRESENTATION LAYERS ............................................................................................................................................. 14
3.7 APPLICATION LAYER................................................................................................................................................... 15

4.0 INTERFACE PROFILE............................................................. 16

4.1 NETWORK TIME PROTOCOL (NTP) ........................................................................................................................ 16
4.2 AVIT\TECO RESPONSIBILITY ................................................................................................................................. 17
4.3 AVIT\TECO RESPONSIBILITY ON BMS SERVERS ................................................................................................ 18

5.0 CLOSING .................................................................................... 19

AWARENESS ................................................................................................................................................................................. 19

6.0 REQUIREMENTS SPECIFICATION SIGN-OFF .................. 20

AVIT – Aviation Information Technology Company Page 2

 HRG MCS – BMS Interface Control Document

List of Figures
FIGURE 1 BMS AND MCS RESPONSIBILITY DIAGRAM............................................................................................................ 8
FIGURE 2 STRATUM LEVELS - YELLOW ARROWS INDICATE A DIRECT CONNECTION; RED ARROWS INDICATE A
NETWORK CONNECTION ........................................................................................................................................................ 16
FIGURE 3 BMS AND MCS SERVERS CONNECTION................................................................................................................. 17
FIGURE 4 CLIENT SOFTWARE .................................................................................................................................................... 18

List of Tables
TABLE 1 STANDARD AND REFERNCES ....................................................................................................................................... 7
TABLE 2 OSI LAYERS FOR BMS AND MCS INTERFACE.......................................................................................................... 9
TABLE 3 BMS AND MCS IP ADDRESS AND HOST NAME...................................................................................................... 13
TABLE 4 BMS AND MCS SEVER UDP PORT .......................................................................................................................... 14
TABLE 5 SIGN OFF TABLE............................................................................................................................................................. 20

AVIT – Aviation Information Technology Company Page 3

 HRG MCS – BMS Interface Control Document
1.0 Document Revision

Rev Date Change Department Name

1.0 19 June 2014 Initial Draft AVIT Ahmed Samir

AVIT – Aviation Information Technology Company Page 4

 HRG MCS – BMS Interface Control Document
2.0 OVERVIEW

A system is an aggregation of subsystems cooperating so that the system is

able to deliver the overarching functionality. System integration involves
integrating existing often disparate systems.

System integration is also about adding value to the system, capabilities that are
possible because of interactions between subsystems.

Hurghada International Airport (HRG) has a requirement where system Time

of BMS server needs to be updated from Master Clock System server (MCS
server). Some of information/data would be required to be transferred in different
formats based on the requirements of the target system in relation to the sources
system.

In order to deliver the data efficiently based on business requirements, NTP has
been chosen as the preferred transportation platform. BMS will update the time
from MCS Server via Network Time Protocol. The agreement and signoff of this
document will be the agreed specification against which testing will be performed.

An Interface Control Document (ICD) describes the relationship between two

components for BMS and MCS in terms of data items and messages passed,
protocols observed.

This document should be used as a baseline for any solution proposal, or detailed
functional or technical design of an automated interfacing solution.

AVIT – Aviation Information Technology Company Page 5

 HRG MCS – BMS Interface Control Document
2.1 Document Objectives

The objective of this Specification document is to identify, document and

map the functional, system and customer requirements.

2.2 Functional Objectives

Hurghada International Airport HRG requires BMS server time

parameter to be updated from Master Clock System (MCS) so that MCS can
provide time parameter to BMS server. The following was agreed with the
customer as to the requirements for this interface:

a) This document will serve as the standard MCS interface specification for
platform development and customer expectation.
b) BMS will receive NTP packet from MCS.
c) All functionality and requirements outside of this specification are to be
analyzed and with a new Cost as change requests.

Interface will be delivered as specified in this document, according to this

specification. If HURGHADA International Airport at any stage has a different
requirement than that which is agreed to in this specification, this will imply new
requirement analysis and an update to this specification as necessary.

AVIT – Aviation Information Technology Company Page 6

 HRG MCS – BMS Interface Control Document
2.3 Standard and referenced Documents

Index Reference Title

Internet Architecture Board, Official Protocol
[01] RFC 791 (IP) Standard – Internet Protocol, September 1981, Status:
Required/Standard
Internet Architecture Board , Official Protocol
[02] RFC 792 (ICMP) Standard – Internet Control Message Protocol,
September 1981, Status: Required/Standard
[03] RFC 768 (UDP) USER DATAGRAM PROTOCOL
Internet Architecture Board , Official Protocol
[04] RFC 826 (ARP) Standard – Address Resolution Protocol, November
1982, Status: Elective/Standard
Address allocation for Private Internets, February
[05] RFC 1918
1996, Status: Best Current practice.
Information Technology – Local and metropolitan
area Networks – Part3 carrier sense multiple access
[06] ISO/IEC 8802-3 (MAC)
with collision detection (CSMA / CD) access method
and physical layer specifications.
Supplement to carrier sense Multiple Access with
collision Detection (CSMA / CD) Access Method and
physical layer specification: Media Access Control
[07] ISO/IEC 8802-3u (Fast Ethernet) (MAC) parameters, Physical Layer, Medium
attachment and repeater for 100 Ms/s operation, Type
100 Base T
Product type: standard – 26 OCT 1995
1992 Information Technology – Telecommunication
Information exchange between systems – Interface
[08] ISO/IEC 8877 (RJ45)
connector and contact assignments for ISDN Basic
Access Interface located at reference points S and T
[09] RFC 958 Network Time Protocol (NTP)

Table 1 Standard and Refernces

AVIT – Aviation Information Technology Company Page 7

 HRG MCS – BMS Interface Control Document

2.4 Interface identification

The BMS to MCS Interface is a unidirectional interface.

The following diagram a high level connection between BMS and MCS and
Communication direction from BMS to MCS.

BMS

Responsibility

BMS MCS
AVIT\TECO

Responsibility

Figure 1 BMS and MCS Responsibility Diagram

AVIT – Aviation Information Technology Company Page 8

 HRG MCS – BMS Interface Control Document
3.0 INTERFACE LAYERS

This interface will be as far as possible described in relation to the Open

System Interconnection (OSI) seven layer reference model, The following
section provide detailed information, where necessary, about individual layer,
defining applicable option and parameter values.

Therefore specific option and parameter values for the various protocols that
are used will only be specified when an ambiguity has to be fixed or in the case
of a deviation from a standard.

The BMS to MCS interface profile can be described in term of layers, each
with a mapping to the seven layer OSI reference model described by table
below:

OSI Layer Protocol Standard application

Layers 7 Application Layer RFC 958
Layers 6 Presentation Layer
Layers 5 Session Layer
Layers 4 Transport Layer RFC 768 (UDP)
RFC 791 (IP) [01]
RFC 792 (ICMP) [02]
Layers 3 Network Layer
RFC 826 (ARP) [04]
CISCO HSRP [09]
Layers 2 Data Link Layer ISO/IEC 8802-3 (MAC) [06]
ISO/IEC 8802-3u (Fast Ethernet) [07]
Layers 1 Physical Layer
ISO/IEC 8877-3 (RJ45) [08]

Table 2 OSI Layers for BMS and MCS Interface

AVIT – Aviation Information Technology Company Page 9

 HRG MCS – BMS Interface Control Document
3.1 Physical Layer

In the seven-layer OSI model of computer networking, the physical layer or

layer 1 is the first (lowest) layer. The implementation of this layer is often termed
PHY.

The physical layer consists of the basic networking hardware transmission

technologies of a network. It is a fundamental layer underlying the logical data
structures of the higher level functions in a network. Due to the plethora of
available hardware technologies with widely varying characteristics, this is
perhaps the most complex layer in the OSI architecture.

The physical layer defines the means of transmitting raw bits rather than logical
data packets over a physical link connecting network nodes. The bit stream may be
grouped into code words or symbols and converted to a physical signal that is
transmitted over a hardware transmission medium. The physical layer provides an
electrical, mechanical, and procedural interface to the transmission medium.

Within the semantics of the OSI network architecture, the physical layer translates
logical communications requests from the data link layer into hardware-specific
operations to affect transmission or reception of electronic signals.

The physical layer confirms to the standard Fast Ethernet (ISO/IEC 8802-3u (Fast
Ethernet) [07]) forced to full duplex.

The 100 Base-T interface points between BMS to MCS through HURGADA
INTERNATIONAL AIRPORT - DATA NETWORK CABLE (DNE)

Cables are defined at the straight RJ45 (DCE) female socket (refer to ISO/IEC
8877 (RJ45) [08]) on its Switch inside the cabinet.

AVIT – Aviation Information Technology Company Page 10

 HRG MCS – BMS Interface Control Document
3.2 Data Link Layer

In the seven-layer OSI model of computer networking, the data link layer is layer 2.

The data link layer is the protocol layer that transfers data between adjacent network
nodes in a wide area network or between nodes on the same local area network segment.
The data link layer provides the functional and procedural means to transfer data between
network entities and might provide the means to detect and possibly correct errors that
may occur in the physical layer.

The data link layer is concerned with local delivery of frames between devices on the
same LAN. Data-link frames, as these protocol data units are called, do not cross the
boundaries of a local network. Inter-network routing and global addressing are higher
layer functions, allowing data-link protocols to focus on local delivery, addressing, and
media arbitration.

When devices attempt to use a medium simultaneously, frame collisions occur. Data-link
protocols specify how devices detect and recover from such collisions, and may provide
mechanisms to reduce or prevent them.

Delivery of frames by layer-2 devices is affected through the use of unambiguous

hardware addresses. A frame's header contains source and destination addresses that
indicate which device originated the frame and which device is expected to receive and
process it. In contrast to the hierarchical and routable addresses of the network layer,
layer-2 addresses are flat, meaning that no part of the address can be used to identify the
logical or physical group to which the address belongs.

The data link thus provides data transfer across the physical link. That transfer can be
reliable or unreliable; many data-link protocols do not have acknowledgments of
successful frame reception and acceptance, and some data-link protocols might not even
have any form of checksum to check for transmission errors. In those cases, higher-level
protocols must provide flow control, error checking, and acknowledgments and
retransmission.

Within the semantics of the OSI network architecture, the data-link-layer protocols
respond to service requests from the network layer and they perform their function by
issuing service requests to the physical layer.

This layer conforms to the ISO/IEC 8802-3 (MAC) standard (refer to [06]) with
untagged frame format.

AVIT – Aviation Information Technology Company Page 11

 HRG MCS – BMS Interface Control Document
3.3 Network Layer

In the seven-layer OSI model of computer networking, the network layer is layer 3.
The network layer is responsible for packet forwarding including routing through
intermediate routers, whereas the data link layer is responsible for media access control,
flow control and error checking.

The network layer provides the functional and procedural means of transferring variable
length data sequences from a source to a destination host via one or more networks, while
maintaining the quality of service functions.

Functions of the network layer include:

 Connection model: connectionless communication

 Host addressing

 Message forwarding

Within the service layering semantics of the OSI network architecture, the network layer
responds to service requests from the transport layer and issues service requests to the
data link layer.

This layer conforms on the “RFC 791 (IP) [01], RFC 792 (ICMP) [02], and RFC
826 (ARP) [04].
There is an IP address will be defined in the following format: W.X.Y.Z/AA
where W, X, Y and Z represent 8 bits of the address in decimal values and AA the
Sub-net mask value which gives in decimal the number of bits set to “1” inside the
mask.
The network layer used is the IP version 4 (Internet protocol version 4), the
following internet protocols shall be supported by the interface:

 IP RFC 791 – Internet Protocol (refer to [01])

 ARP RFC 826 – Address Resolution Protocol (refer to [04])

Both of BMS and MCS will have a unique IP address for communication that will
occurred between them, all unicast address definition shall respect private
addressing of RFC 1918 (refer to [05]).

AVIT – Aviation Information Technology Company Page 12

 HRG MCS – BMS Interface Control Document
The following table will show the IP address and Host Name for MCS and BMS
that will be defined later.

System Host Name IP Address

BMS TBD TBD
BMS TBD TBD
MCS MCSSERVER1 192.168.50.101
MCS MCSSERVER2 192.168.50.102

Table 3 BMS and MCS IP address and Host Name

3.4 Transport layer

In computer networking, the transport layer or layer 4 provides end-to-end

communication services for applications within a layered architecture of network
components and protocols. The transport layer provides convenient services such
as connection-oriented data stream support, reliability, flow control, and
multiplexing.
Transport layers are contained in both the TCP/IP model (RFC 1122), which are
the foundation of the Internet and the Open Systems Interconnection (OSI) model
of general networking. The definitions of the transport layer are slightly different
in these two models.
The most well-known transport protocol is the Transmission Control Protocol
(TCP). It lent its name to the title of the entire Internet Protocol Suite, TCP/IP. It is
used for connection-oriented transmissions, whereas the connectionless User
Datagram Protocol (UDP) is used for simpler messaging transmissions. TCP is the
more complex protocol, due to its state full design incorporating reliable
transmission.
The transport layer used between BMS and MCS is UDP Packets (User Datagram
Protocol – refer to RFC 768 (UDP)), and the following table show the UDP port
on both BMS and MCS server that will be used.

AVIT – Aviation Information Technology Company Page 13

 HRG MCS – BMS Interface Control Document

System Host Name UDP Port

BMS TBD Random free Port
BMS TBD Random free Port
MCS MCSSERVER1 123
MCS MCSSERVER2 123
Table 4 BMS and MCS Sever UDP Port

Using UDP protocol will help BMS and MCS to communicate with each other
using NTP between them that will be defined later in this document in Section
(05): Interface Profile

3.5 Session Layer

In the seven-layer OSI model of computer networking, the session layer is

layer 5.
The session layer provides the mechanism for opening, closing and managing a
session between end-user application processes.

3.6 Presentation Layers

In the seven-layer OSI model of computer networking, the presentation layer is

layer 6 and serves as the data translator for the network. It is sometimes called the
syntax layer.
The presentation layer is responsible for the delivery and formatting of
information to the application layer for further processing or display. It relieves
the application layer of concern regarding syntactical differences in data
representation within the end-user systems

AVIT – Aviation Information Technology Company Page 14

 HRG MCS – BMS Interface Control Document
3.7 Application Layer

In computer network programming, the application layer is an abstraction layer

reserved for communications protocols and methods designed for process-to-
process communications across an Internet Protocol (IP) computer network.
Application layer protocols use the underlying transport layer protocols to
establish host-to-host connections.
In the OSI model, the definition of its application layer is narrower in scope. The
OSI model defines the application layer as being the user interface. The OSI
application layer is responsible for displaying data and images to the user in a
human-recognizable format and to interface with the presentation layer below it.

Application layer will define the communication between BMS and MCS through
the interface using Network Time Protocol.
We will state how NTP will work through the interface and responsibilities for
both systems BMS and MCS in next Section (04): Interface Profile

AVIT – Aviation Information Technology Company Page 15

 HRG MCS – BMS Interface Control Document
4.0 INTERFACE PROFILE

In this section we will talk about Network Time Protocol of the interface and the
responsibility of both companies MCS (AVIT\TECO) and BMS, to update BMS server
with time parameter from MCS server.

4.1 Network Time Protocol (NTP)

Network Time Protocol (NTP) is a networking protocol for clock

synchronization between computer systems over packet-switched, variable-latency
data networks.

NTP uses a hierarchical, semi-layered system of time sources. Each level of this
hierarchy is termed a "stratum" and is assigned a number starting with zero at the
top. The number represents the distance from the reference clock and is used to
prevent cyclical dependencies in the hierarchy. Stratum is not always an indication
of quality or reliability; it is common to find stratum 3 time sources that are higher
quality than other stratum 2 time sources.
.

Figure 2 Stratum Levels - Yellow arrows indicate a direct connection; red arrows indicate a network
connection

AVIT – Aviation Information Technology Company Page 16

 HRG MCS – BMS Interface Control Document
4.2 AVIT\TECO Responsibility

AVIT \TECO will responsible on for Master Clock system ready and install
services required on that server to serve the function of that interface to deliver
time parameter to BMS servers by AVIT\TECO.

And Figure below will show the connection between MCS servers and BMS
Server.

Figure 3 BMS and MCS servers connection

AVIT – Aviation Information Technology Company Page 17

 HRG MCS – BMS Interface Control Document
4.3 AVIT\TECO responsibility on BMS Servers

AVIT \ TECO will responsible to install client software CDG021and configuration

required to make it up and running for receiving time parameter for NTP servers

BMS Servers working on windows server 2008, and Figure below show the screen
shot of software after installation.

Figure 4 Client software

AVIT – Aviation Information Technology Company Page 18

 HRG MCS – BMS Interface Control Document

5.0 Closing

Awareness

This document has been prepared with the intention of defining

Interface Control Specifications. Any functions that will arise after this
document is signed-off will result in change request process to be
followed.

AVIT – Aviation Information Technology Company Page 19

 HRG MCS – BMS Interface Control Document

6.0 Requirements Specification Sign-Off

Name Role and Representing Signature Date

Project Director
Ayman Dessouky
AVIT

Light Current System Engineer

Shaymaa Nabil
AVIT

Integration Manager
Ahmed Samir
AVIT

Project Manager (MCS)

Emad Shenouda
TECO

Senior Engineer (MCS)

Bahaa Ismael
TECO

Project Manager (BMS)

Wael Nada
Johnson Controls

System Project Engineer

Salah El Din (BMS)
Johnson Controls

Table 5 Sign off table

AVIT – Aviation Information Technology Company Page 20