# AVL and Monitoring for Massive Traffic Control System over DDS

Authors: Basem Almadani; Shehryar Khan; Muhammad Naseer Bajwa; Tarek R. Sheltami; Elhadi Shakshuki
Journal: Mobile Information Systems
 (2015)

---

## Abstract

This paper proposes a real-time Automatic Vehicle Location (AVL) and monitoring system for traffic control of pilgrims coming towards the city of Makkah in Saudi Arabia based on Data Distribution Service (DDS) specified by the Object Management Group (OMG). DDS based middleware employs Real-Time Publish/Subscribe (RTPS) protocol that implements many-to-many communication paradigm suitable in massive traffic control applications. Using this middleware approach, we are able to locate and track huge number of mobile vehicles and identify all passengers in real-time who are coming to perform annual Hajj. For validation of our proposed framework, various performance matrices are examined over WLAN using DDS. Results show that DDS based middleware can meet real-time requirements in large-scale AVL environment.


---

## Body

## 1. Introduction

Applications of distributed mobile networks exist in everyday life in the form of transportation systems, healthcare systems, weather and environment monitoring systems, and so forth. Such systems require their mobile nodes to communicate and share data among them in real-time. Mobile nodes in these scenarios may be hand held devices, vehicles [1, 2], or robots [3, 4]. With the advancement in embedded systems, it is now possible to allow thousands of mobile nodes to communicate and share huge amount of data. It is also possible to collect the data at the sensor level and forward it to the application level for processing and analysis, all in real-time. These nodes need to share their context updates regularly. In AVL applications, vehicles assume the role of distributed mobile nodes and they require sharing their information such as their locations, vehicles identification, and passenger status. The passengers’ information can be extracted using Radio Frequency Identification (RFID) system.The city of Makkah in Kingdom of Saudi Arabia hosts millions of Hajj pilgrims every year. Hajj consists of number of rituals, spanning over five designated days that are to be performed in specific locations in and around the city of Makkah. The number of pilgrims is increasing each year and about 3.1 million pilgrims performed Hajj in 2012 [5]. Some of these people get lost in huge crowd and, therefore, there is dire need to identify them, trace their position, and inform their families. There are many models that have been proposed to facilitate the organizers such as in [6] three security requirements are detailed and lattice model is proposed for flow of information. In [7] a bus transportation system within the city of Makkah is proposed and validity of this system is tested using simulation and experiments.Addressing this challenge necessitates formulation of a framework that identifies and monitors the pilgrims as well as their road transport. Such a large-scale system calls for a vast and scalable infrastructure that supports reliable and instant context updates for sharing among the mobile nodes [8] and, at the same time, is able to dynamically adjust to the load demand. In distributed mobile communication environments, the nodes are limited in power and resources. The network connections for these mobile nodes are also fluctuating and may suffer from frequent disconnections.The publish/subscribe (PS) model is by far the most suitable for mobile distribution environment. Although many researchers have attempted to develop publish/subscribe model [9–13], yet only a few of them are able to support mobile networks. The publish/subscribe model has two distinct characteristics. First, it efficiently distributes large amount of data to large number of users. Secondly, the publisher and the subscriber are not required to connect simultaneously in order to distribute data. In PS model, both communicating participants do not know about each other’s existence. Nowadays, industrial automation, aerospace, and defense applications use Data Distribution Service (DDS) based middleware [14, 15]. The work presented in this paper also uses DDS based middleware for our application of Automatic Vehicle Location.DDS is specification for real-time scalable middleware. Its architecture is decentralized and it realized an asynchronous communication model. It specifies many Quality of Service (QoS) policies such as reliability, data flow prioritization, data persistence, and other optimization schemes that are used to control various aspects of data transmission. The unique property of DDS based middleware is that the efficiency of network resources and latency can be controlled by fine tuning some of the QoS policies like latency budget, deadline, and transport priority. In our application, we chose DDS based middleware because of the following characteristics that support mobile distributed environments.(A) Asynchronous Interaction. Network connections in distributed mobile environment have high error rate, high disconnection frequency, and bandwidth limit due to the limited power or lack of spectrum availability. Therefore, asynchronous communication is better than synchronous communication in this type of applications.(B) Data Sharing. The data to mobile devices must be available at all times even when disconnected from the main server. This capability of data sharing and disconnected operation is significant feature in DDS based middleware. It should be noted that consistent, reliable, and efficient accessibility to the database should be provided by the mobile distributed information system. This implies that global distributed database should also be synchronized among all nodes even after disconnection.(C) Reflection and Dynamic Reconfiguration. A heterogeneous environment of dynamic context is encountered by the devices in mobile communication scenarios. In many heterogeneous systems, devices may exhibit different behaviors due to diversity in their network protocols, I/O interfaces, and OS. Thus, mobile nodes/devices should be adaptive to the available resources, which require techniques to optimize the behavior of nodes. Therefore, the middleware should detect the changes in the availability of resources to support dynamic reconfiguration. It also has to notify the application for the reallocation of resources to different nodes.


## 2. Related Work

For large-scale mobile system, a middleware called Scalable Context-Aware Middleware for Mobile Environments (SALES) is developed in [16]. It is a tree based classified model of nodes for performance evaluation, load balancing, and calculating communication cost among the following four types of nodes: (1) central node, (2) base node, (3) coordinator user node, and (4) simple user. SALES does not take advantage of real-time DDS and uses UDP. Two main terminologies are used: Quality of Context (QoC) and Context Data Distribution Level Agreement (CDDLA). QoC is associated with context information distributive service whereas CDDLA is quality agreement between consumer and producer imposed by the middleware. This SALES architecture lacks the functionality of fault tolerance, QoS support, and context updates by mobile nodes.For ubiquitous computing, a middleware named Solar is developed in [17]. It uses two protocols: TCP for interplanetary communication and Distributed Hash Table (DHT) for routing and discovery. It is built on the basis of self-organizing peer-to-peer network and is designed for scalability among the set of communicating nodes. It employs filter and pipe programming model. Each filter has group of entry and exit points as well as sources and sinks. Each node in the solar architecture is viewed as planet and each planet has a number of satellite nodes. Solar has the reliability of TCP that may not be suitable for some real-time applications. It also lacks the functionality of fault tolerance. A limited research is done in the implementation of mobile distributed applications using DDS based middleware. Among few of them is [4]. Its architecture supports mobile nodes and provides reliable data delivery. It also supports handover by switching the wireless access points. The mobile nodes in the proposed middleware execute light version of DDS, whereas the fixed nodes execute full version and are responsible for routing and data delivery among all nodes. Due to the architecture of this middleware, mobile nodes have to run in a single domain and stable wireless connectivity is necessary. This proposed middleware, too, lacks the functionality of fault tolerance.REliable and VErsatile News delivery support for aGEncies (Revenge) is a DDS based middleware, which serves as news dispatching service among mobile nodes [18]. It efficiently disseminates the data among the mobile nodes in DDS domain. It is also based on self-organizing peer-to-peer network and is fault tolerant. Revenge efficiently detects the crashed nodes and reroutes the paths from any source to any sink. This architecture, however, lacks the functionality of handover. Another DDS based middleware is proposed in [19] for real-time communication between mobile nodes using proxy approach. A proxy DDS client is used for managing, coordinating, and forwarding all the data to mobile nodes. This architecture provides both reliable and unreliable data delivery. Due to the Firewall/NAT restrictions, mobile nodes have to run within a single domain with continuous connectivity.A DDS based middleware called Scalable Data Distribution Layer (SDDL) [20, 21] is proposed for real-time tracking of mobile nodes. This middleware connects the stationery DDS nodes in a wired network to the mobiles nodes with IP based wireless connection. Two protocols are used in this middleware: RTPS wire protocol for communication among the stationery nodes and mobile reliable UDP protocol for communication among the mobile nodes. In wired core network, there are three types of stationery nodes with unique roles: (1) gateway that is responsible for maintaining separate connections with mobile nodes through Mobile Reliable- (MR-) UDP connections; it is also responsible for notifying other core network nodes when a mobile node is connected or disconnected; (2) Point of Attachments (PoA) Manager that distributes the list of points of attachment/gateways to mobile nodes and it may later switch to different gateway; mobile nodes may also switch the gateway when they detect weak connection with the current gateway; and (3) group definers, which are responsible for evaluation of group-membership of mobile nodes. They subscribe to a specific DDS topic and map each node to one or more groups corresponding to application specific group membership logic. When a new message is sent to a group, a gateway asks for group-to-mobile-node mapping to know which mobile node is ready to send messages.An RFID system based on publish/subscribe middleware is introduced in [22]. Since different applications require different data, middleware has to adapt to all applications. When more applications need to be incorporated, it is necessary to adjust middleware functionalities to satisfy them. This, however, costs time and effort. Using publish/subscribe mechanism applications can subscribe to events from the RFID reader dynamically. In this model filtering of messages can be topic based or content based. In topic based filtering, the subscriber receives messages published to a specific topic. All subscribers will receive the same messages for a particular topic. In content based filtering, subscribers will receive messages if the content of the messages match the constraints set by the subscribers. Four components are proposed for publish/subscribe model in this RFID middleware: (1) list of publications maintained by the message manager, (2) list of subscriptions maintained by the message manager, (3) message manager that acts as a controller and responds to the requests of the reader manager for maintenance; it also responds to the client queries for the list of publication and maintains the list of subscribers, and (4) an API with a set of routines and protocols to allow the clients to subscribe and unsubscribe.


## 3. DDS Architecture

DDS specifies a communication model that is data centric publish/subscribe for various computing and distributed environments. This data centric publish/subscribe (DCPS) uses a Global Data Space (GDS) where publishers post and the DCPS model disseminates this information to all the interested subscribers.Figure1 illustrates all the basic constructs in a simple DCPS model. A domain is a virtual network area and all the publishers and subscribers can send and receive messages within a domain. A publisher is an object that, according to the publisher’s QoS policies, distributes data and publishes different types of data objects. Data writers are used by the publishers to write data to the GDS. A subscriber receives the publishing data using data readers and, according to subscriber’s QoS policies, makes them available to the receiving application. It reads the topics from GDS for which there exists a matching subscription and data readers are informed that data is received.Figure 1
DDS architecture [19].The DDS has two types of discovery protocols: the Participant Discovery Protocol (PDP) and the Endpoint Discovery Protocol (EDP). Through these protocols participants can dynamically discover the existence of other participants and also inform other participants about the end points such as data readers and data writers and so forth. The basic architecture of DDS is described as the unidirectional data communication in a fixed network. In this network a publisher pushes the data to the subscriber which is saved in its history caches. Topic is the data type that links the publishers and subscribers. Implementation requires this discovery protocol to identify the existence, presence, and absence of the endpoints when the network is joined or left by them. Another key distinguishing feature of DDS as compared to another publish/subscribe middleware is that it has rich QoS support. The behavior and performance of the DDS service and how it performs the various coordination tasks depend upon how its QoS policies are configured. For mobile environment the useful QoS policies are durability, history, and reliability. Below is a brief description of each of them.(i)
For mobility support, RELIABILTY QoS policy is used indicating the reliability level between publisher and subscriber. If RELIABILTY is set to BEST_EFFORT then the publisher will push the samples without retransmissions or expecting acknowledgements. If RELIABILITY is set to RELIABLE then publisher will guarantee the delivery of samples to the subscriber. If the subscriber is disconnected or unavailable and samples are unacknowledged then the publisher can retransmit the samples using the DURABILITY QoS policies.
(ii)
DURABILITY QoS indicates whether previous data samples will be made available to late joining subscriber by the publisher or not. By setting the DURABILITY policy to PERSISTENCE, the past data samples are stored in the permanent memory such as FLASH, HARD DISK. Due to this the subscriber can have this data when it reconnects to the system at any time. The DURABILITY policy depends upon the HISTORY QoS policy and RESOURCE_LIMITS QoS policy.
(iii)
HISTORY QoS specifies the maximum number of data samples that are stored in the History Cache of publisher for reconnecting or late joining subscribers.
(iv)
RESOURCE LIMIT specifies maximum number of samples and instances which publisher or subscriber can manage.


## 4. Proposed Solution

In this section we propose a framework for location and monitoring system based on DDS based middleware especially for pilgrims of Hajj. To provide control and location services of this huge crowd, each pilgrim can be provided with a GPS transmitter; however, implementing this solution is too expensive. Similarly, another possibility is that each person can be provided with a radio transmitter with unique identifier and the transmitter can update pilgrim’s location by sending update to the database via base station. Although it may be useful, signal coverage can be a problem. Our solution addresses these challenges during journey of pilgrims and offers crowd management and prevention of accidents using the architecture depicted in Figure2.Figure 2
AVL and monitoring system architecture.Proposed approach can manage a huge system consisting of about 50,000 buses as mobile nodes as well as the passengers inside these vehicles. This system is especially useful for ensuring that all pilgrims have valid Hajj permits. Assume there are various entry points to the city of Makkah and on each entry point there is check posts almost 10 Km from the city. Three layers of security are implemented on each check post. These include RFID readers to read electronic license plates, distributed database server, and automatic gates access based upon previous two security layers. The detailed layout of the framework is given below.


### 4.1. Bus or Mobile Node

(i)
GPS and 3G Device.Every bus has a 3G device that periodically updates its current locations using GPS.
(ii)
Thermal Camera. These cameras count number of passengers in the bus and send this information to local database in the bus.
(iii)
RFID Readers.Each passenger has RFID wrist bands with their personal information. This information is collected using RFID readers inside the bus and sent to local database.
(iv)
WiFi Device. Local database is synchronized with DDS cloud using WiFi.The message format for RFID passenger data is shown in Figure 3.Figure 3
Message format in RFID message.


### 4.2. The Check Post

The check posts are established at different entry points of the city. Each check post has various parallel lines. They have distributed servers and databases which are part of the DDS cloud. Also, multiple RFID readers are installed for vehicle’s identification through passive RFID license plates.


### 4.3. The Automatic Gate

At the end of each check post there is an automatic gate that will only open after a positive decision is made inside the cloud for a particular vehicle based on different factors such as vehicle identification, passenger counting through thermal cameras, and passenger identification and status through RFID data. When a bus arrives at a check post it has to pass through all three stages before it is finally allowed to enter the city.In the first part of this clearance, there are RFID readers for the verification and authentication of license plates and a decision is made whether this bus is allowed to operate for Hajj pilgrims or not. At this stage it is also verified whether this mobile node is physically present at the checkpoint or not using its GPS location update. This cross checking can deal with identity theft of vehicles. In second part the stored RFID data of passenger identification and status inside the bus is passed to the cloud via WiFi for authentication and decision making. If a mobile node/bus has more than a certain number of unauthorized passengers then the whole bus is rejected; otherwise manual checking is done. In third stage the thermal cameras installed on the bus will do the head counting and will convey this data to the DDS cloud over WiFi. At this point the passenger count data from RFID readers and the thermal cameras are cross checked for further verification in case there are multiple readings for RFID tags.At the end when a mobile node reaches the automatic gate, a decision is made based on the data provided to the cloud during the previous stages. In our case the number of publishers is in thousands whereas subscriber is one. There are four topics for which publishers are publishing as shown in Figure4. These topics are vehicle location update, vehicle registration information, passenger head count, and RFID passenger’s data.Figure 4
DDS domain.


## 4.1. Bus or Mobile Node

(i)
GPS and 3G Device.Every bus has a 3G device that periodically updates its current locations using GPS.
(ii)
Thermal Camera. These cameras count number of passengers in the bus and send this information to local database in the bus.
(iii)
RFID Readers.Each passenger has RFID wrist bands with their personal information. This information is collected using RFID readers inside the bus and sent to local database.
(iv)
WiFi Device. Local database is synchronized with DDS cloud using WiFi.The message format for RFID passenger data is shown in Figure 3.Figure 3
Message format in RFID message.


## 4.2. The Check Post

The check posts are established at different entry points of the city. Each check post has various parallel lines. They have distributed servers and databases which are part of the DDS cloud. Also, multiple RFID readers are installed for vehicle’s identification through passive RFID license plates.


## 4.3. The Automatic Gate

At the end of each check post there is an automatic gate that will only open after a positive decision is made inside the cloud for a particular vehicle based on different factors such as vehicle identification, passenger counting through thermal cameras, and passenger identification and status through RFID data. When a bus arrives at a check post it has to pass through all three stages before it is finally allowed to enter the city.In the first part of this clearance, there are RFID readers for the verification and authentication of license plates and a decision is made whether this bus is allowed to operate for Hajj pilgrims or not. At this stage it is also verified whether this mobile node is physically present at the checkpoint or not using its GPS location update. This cross checking can deal with identity theft of vehicles. In second part the stored RFID data of passenger identification and status inside the bus is passed to the cloud via WiFi for authentication and decision making. If a mobile node/bus has more than a certain number of unauthorized passengers then the whole bus is rejected; otherwise manual checking is done. In third stage the thermal cameras installed on the bus will do the head counting and will convey this data to the DDS cloud over WiFi. At this point the passenger count data from RFID readers and the thermal cameras are cross checked for further verification in case there are multiple readings for RFID tags.At the end when a mobile node reaches the automatic gate, a decision is made based on the data provided to the cloud during the previous stages. In our case the number of publishers is in thousands whereas subscriber is one. There are four topics for which publishers are publishing as shown in Figure4. These topics are vehicle location update, vehicle registration information, passenger head count, and RFID passenger’s data.Figure 4
DDS domain.


## 5. Experimentation Setup

Before going to experimentation and results, some performance parameters are defined below to validate the timeliness of our proposed solution.(i)
The time taken by a data packet to reach the receiver side is known as the latency. This includes both the propagation delay as well as the queuing delay and can be calculated by dividing Round Trip Time (RTT) by 2:(1)
Latency
=
RTT
2
.
(ii)
Variation in latency is known as the jitter. The smaller the value of the jitter, the smaller the variation in the delay of packets. It means that with small values of jitter we can be sure that delay of the packets will be same for most of the time during their journey from sender to receiver. Jitter can be calculated as given in(2)
Jitter
=
1
N
∑
i
=
1
N
x
i
-
x
-
2
,
where the total number of delay samples is represented byN and mean value of N delay samples is represented by x
¯.
(iii)
The average rate of successful data transmission is known as the throughput. This includes the payload as well as the protocol overhead. Following equation is used to calculate the throughput:(3)
Throughput
=
Packet  Size
×
Number  of  Packets
Total  Time
.We  provide hardware platform used in our experiment as well as software tools needed in Tables 1 and 2, respectively.Table 1
Platform specifications for WLAN.
Host Apublisher
Host Bsubscriber
CPU
Intel(R), Core (TM)2 Duo CPU P8800 @ 2.66 GHz
Intel(R), Core (TM)2 Duo CPU P8800 @ 2.66 GHz
OS
Windows 7 64 bitoperating system
Windows 7 64 bitoperating system
Memory
4 GB
4 GB
Networkconnection
WLANIEEE 802.11, 54 Mbps
WLANIEEE 802.11, 54 MbpsTable 2
Software specifications for WLAN.
Tool
Version
Purpose
RTI Connext-RTI DDS Latency Test
5.0.0
Measure latency(one way delay)
Wire-shark
1.2.3
Measure throughputTo support mobility and ensure real-time behavior of the system, QoS policies used in our experimentation are shown in Table3.Table 3
QoS policies for mobility.
QoS policy
Publisher
Subscriber
DURABILITY
PERSISTENCE
PERSISTENCE
RELIABILITY
RELIABLE
RELIABLE
HISTORY
KEEP_ALL
KEEP_LAST
RESOURCE_LIMIT
LENGTH_UNLIMITED
1


## 6. Results and Analysis

The bottleneck in our proposed framework can be data transmission over WiFi at check posts. Therefore, we conducted experiments to measure various performance matrices for this wireless medium. Latency and jitter can validate if the proposed solution can fulfill real-time requirements in AVL application for Hajj pilgrims. The values of throughput can shed light on whether WiFi can withstand high data-rate demand of such scenario. The obtained results for latency, jitter, and throughput for Wifi over DDS are tabulated in Tables4–7. There is significant improvement in the results compared to [23] because of the introduction of QoS policies as well as controlled environment for experimentation making sure that only DDS applications are running over WiFi.Table 4
Latency and jitter for many-to-one model.
Number of publishers
Minimum(m sec)
Maximum(m sec)
Avg.(m sec)
Avg. [23] (m sec)
Jitter(m sec)
1
1.28
63.51
2.41
12.18
2.35
2
1.38
57.29
2.47
13.17
1.96
4
1.77
112.44
4.00
12.45
4.68
6
2.06
454.14
4.23
12.71
5.16
8
2.22
707.40
5.95
12.93
7.53Table 5
Latency and jitter for many-to-many model.
Number of publishers
Number of subscriber
Minimum(m sec)
Maximum(m sec)
Avg.(m sec)
Jitter(m sec)
2
2
1.42
131.93
2.69
2.95
4
2
1.64
237.24
3.43
3.36
4
4
1.55
106.48
2.40
3.39
8
4
2.43
291.53
6.32
4.28Table 6
Throughput for many-to-one model.
Number of publishers
Total packets(×1000)
Total time(sec)
Throughput(Mbps)
Throughput [23] (Mbps)
1
4585
5536
6.810
0.842
2
2794
3277
6.958
1.598
4
3330
3807
7.168
3.386
6
3780
3986
7.772
3.515
8
5040
5544
7.498
2.91Table 7
Throughput for many-to-many model.
Number of publishers
Number of subscribers
Total packets(×1000)
Total time(sec)
Throughput(Mbps)
2
2
3560
3706
7.87
4
2
4032
4360
7.67
4
4
4032
2767
12.37
8
4
4032
2730
12.59For latency and jitter, 1024-byte payload is used. First, one subscriber and multiple publishers scenario is examined. In each run 20,000 to 50,000 packets are sent and the minimum, maximum, and average values are calculated. Tests are repeated up to 10 times and overall average is taken to account for any random fluctuation in performance measures.Table4 records measurements obtained from experiments. Jitter is calculated using (2). We can see that both latency and jitter increase linearly as the number of publishers grow. Figures 5 and 6 show latency and jitter graphs corresponding to Table 4. In Figure 5 we can observe that there is considerable improvement in latency as compared to results in [23] because specific QoS policies for mobility are introduced in our scenario and Wifi experimentation was carried out in a controlled lab setup to avoid other applications running on the same WiFi.Figure 5
Average latency in many-to-one model.Figure 6
Jitter in many-to-one model.Latency and jitter are also calculated for many-to-many communication scenario. Tests are run to examine the effect of multiple publishers and multiple subscribers on the latency and jitter. As expected, both performance measures have higher values when multiple participants try to transmit the data over a single channel. These results are tabulated in Table5. Figures 7 and 8 show the results graphically.Figure 7
Average latency in many-to-many model.Figure 8
Jitter in many-to-many model.The data packets’ size and the frequency of the transmission affect the throughput. Data size used in our case is up to few hundred bytes except for the local database updates that are synchronized with DDS cloud. These updates are sent in packets up to 1 KB. Hundreds of thousands of samples are sent from publisher side and received on the subscriber side in each iteration. Total time for this communication is observed and throughput is calculated using (3). The tests are repeated at least 10 times to get more accurate results.Similar to the latency results we can see in Table6 and Figure 9 that there is considerable difference in the throughput. The reason is again judicious selection of QoS values in mobile applications. However, we can observe that with the increase in number of participants there is negligible difference in the throughput.Figure 9
Throughput in many-to-one model.Like many-to-many latency and jitter experiments, we also conducted tests to measure average WiFi in many-to-many mode. Various configurations of publishers and subscribers are examined. Table7 summarizes the results obtained. We can observe from Figure 10 that throughput is not significantly affected by the number of participants in many-to-many scenarios as well.Figure 10
Throughput many-to-many model.Here, it is worth pointing out that the maximum numbers of publishers in our experiments are limited to only eight whereas the total numbers of vehicles are in thousands. The reason is that this experimentation shows the data communication over WiFi at checkpoints. If, on each highway, there are four lanes for vehicles then this framework can deal with eight buses simultaneously. And the small values of latency points out that the buses are cleared almost instantaneously within any let or hindrance.


## 7. Conclusion

Monitoring and tracking vehicles during Hajj have been a tough task for Saudi Arabian authorities for a long time. Illegal Hajj pilgrims also pose a challenge in organization of annual event. In this paper, we introduced a framework to solve this problem of vehicle tracking during Hajj by using OMG’s DDS middleware specification. We discussed pilgrims’ difficulties and transport congestion problems faced during this period. An automated solution based on Real-Time Publish/Subscribe middleware is proposed for tracking and monitoring of vehicles as well as pilgrims. The use of DDS based middleware is motivated by its data centric and asynchronous communication paradigm along with rich set of QoS policies. Experiments are performed for WLAN over DDS to validate real-time characteristics of our proposed framework. Obtained results for various performance parameters such as latency, jitter, and throughput show that the proposed approach can withstand stringent real-time requirements in AVL application under consideration. These preliminary results are encouraging enough to serve as bases for further development of the framework, and ultimately the infrastructure.



---

*Source: 187548-2015-10-04.xml*