Table of Contents
Advertisement
X509v3 Extended Key Usage: TLS Web Server Authentication
◊ Example certificate, see Appendix.
Signature algorithm
The signature algorithm must be SHA256 with RSA encryption.
Key length
The key length of the keys must be at least 2048 bit.
3.5 ACL Clearance
The ActiveShuttle constantly communicates to the AMS. While the ActiveShuttles must be operated in a Wi-
Fi network, the server hosting the AMS in most cases is located in a data processing center and therefore in
a separated network. Access Control Lists (ALCs) normally manages the network communication.
To enable the communication between the ActiveShuttle and the AMS, it is therefore necessary to have the
ALCs cleared beforehand.
→ Request clearance from network operator.
In most cases there are two possible categories of ACL requests:
•
IP-based ACL-Clearance: Only specific IPs within the manufacturing network (Wi-Fi) are allowed to
communicate with the server(s).
On the other hand, communication is not bound to specific ports.
→ Request a new ACL-Clearance for every new ActiveShuttle to be placed in the network.
•
Port-based ACL-Clearance: Each Node in the manufacturing network (Wi-Fi) is allowed to
communicate only through specific ports on the server(s). The communication is normally not bound
to specific IPs.
→ It is not necessary to request ACL-Clearance for every new ActiveShuttle to be placed in the network.
IP-based ACL-Clearance is strongly recommended due to the following reasons:
•
Additional Sectors require different sets of ports: If there are additional Sectors for different maps
at different locations, a new set of ports must be cleared to be able to use port-based ACL-
Clearances.
•
Independence from software updates/changes: With the continuous development of the
ActiveShuttle features it might become necessary to establish additional communication channels
between the ActiveShuttle and the AMS.
IP-based ACL-Clearances do not require the corresponding ports to be checked ahead of a planned
update.
•
Debugging/enhanced logging support: Debugging and enhanced logging features may require
additional communication channels to be opened. As ACL requests often have a long processing time,
enhanced debugging and logging might not be possible within a short term.
IP-based ACL-Clearances allow for be easy enhancement, if the enhanced logging is placed on the
same server or a server that is part of the original ACL request.
Prerequisites
•
For IP-based ACL-Clearances the ActiveShuttles must be assigned with a static IP address.
A request can be placed for this.
In most cases this is covered by the DHCP server, which assigns the static IP address to specific
MAC-addresses.
RA91390962 AB-V1.3.3, en
Requirements | ILS, ActiveShuttle | 27
Advertisement
Chapters
Table of Contents
Troubleshooting
