The document describes a proposed smart trash system using Internet of Things technologies. It begins with an introduction to IoT and its applications in waste management. It then reviews existing smart trash solutions and their limitations. Next, it defines the requirements and specifications for the proposed system, including functional and non-functional requirements. It presents conceptual models of the system including class, activity, and sequence diagrams. Finally, it proposes an architecture and proof of concept for the system including sensors, servers, networking, and scenarios for data collection and routing trucks.

1. Elaborated by: supervised by:
KBOUBI Sidki M. ZENDAH Mohamed Khalil
AYED Mohamed
JOUINI Aroua
KSOURI Slim
Internet Of Things
Smart Trash
System
2014 / 2015

2. Summary
General Introduction.................................................................................... 1
State of art.................................................................................................... 3
I. Existing solution..................................................................................................................4
1. BRE SmartWaste............................................................................................................4
2. ENEVO...........................................................................................................................4
II. Critics.................................................................................................................................5
Conclusion..............................................................................................................................5
Requirement definition................................................................................. 6
I. Requirements analysis.........................................................................................................7
1. Functional requirements .................................................................................................7
2. No-Functional requirements...........................................................................................7
II. Requirements specification................................................................................................8
1. Actors identification.......................................................................................................8
2. Use case diagrams ..........................................................................................................8
2.1. General use case ......................................................................................................8
2.2. Detailed use case .....................................................................................................8
Conclusion..............................................................................................................................9
Conception.................................................................................................. 10
Introduction ..........................................................................................................................11
I. Class diagram....................................................................................................................11
II. Activity diagram ..............................................................................................................12
III. Sequence diagram...........................................................................................................12
Conclusion............................................................................................................................13

3. Proof of concept.......................................................................................... 14
Introduction ..........................................................................................................................15
I. Architecture.......................................................................................................................15
1. Hardware architecture ..................................................................................................15
1.1. Weight Sensor .......................................................................................................15
1.2. Level sensor:..........................................................................................................15
1.3. Server:....................................................................................................................15
1.4. Global Positioning System GPS:...........................................................................16
1.5. Arduino:.................................................................................................................16
2. Software architecture....................................................................................................16
2.1. Apache:..................................................................................................................16
2.2. MySql: ...................................................................................................................17
2.3. php:........................................................................................................................17
2.4. C++:.......................................................................................................................17
II. Scenarios:.........................................................................................................................17
Conclusion............................................................................................................................19
General conclusion..................................................................................... 20

4. List of Figures
Figure 1: BRE SmartWaste ........................................................................................................4
Figure 2: Enevo ONe..................................................................................................................5
Figure 3: General use case..........................................................................................................8
Figure 4: Retrieve trucks list use case ........................................................................................9
Figure 5: Class diagram............................................................................................................11
Figure 6: Activity diagram .......................................................................................................12
Figure 7: Sequence diagram.....................................................................................................13
Figure 8: Weight sensor............................................................................................................15
Figure 9: Level sensor ..............................................................................................................15
Figure 10: Server ......................................................................................................................15
Figure 11: GPS .........................................................................................................................16
Figure 12: Arduino ...................................................................................................................16
Figure 13: Apache ....................................................................................................................16
Figure 14: MySql......................................................................................................................17
Figure 15: PHP .........................................................................................................................17
Figure 16: C++ .........................................................................................................................17
Figure 17: Can concept.............................................................................................................18
Figure 18: Sending Data to server............................................................................................18
Figure 19: Sending Data to trucks............................................................................................19
Figure 20: GPS Tracking..........................................................................................................19

5. General Introduction
1
General Introduction
The Internet of Things (IoT) is a computing concept that describes a future where
everyday physical objects will be connected to the Internet and be able to identify themselves
to other devices. The term is closely identified with RFID as the method of communication,
although it also may include other sensor technologies, wireless technologies or QR codes.
The IoT is significant because an object that can represent itself digitally becomes
something greater than the object by itself. No longer does the object relate just to you, but is
now connected to surrounding objects and database data. When many objects act in unison,
they are known as having "ambient intelligence."
The Internet of Things may be a hot topic in the industry but it’s not a new concept. In
the early 2000’s, Kevin Ashton was laying the groundwork for what would become the
Internet of Things (IoT) at MIT’s AutoID lab. Ashton was one of the pioneers who conceived
this notion as he searched for ways that Proctor & Gamble could improve its business by
linking RFID information to the Internet. The concept was simple but powerful. If all objects
in daily life were equipped with identifiers and wireless connectivity, these objects could be
communicate with each other and be managed by computers.
At the time, this vision required major technology improvements. After all, how would
we connect everything on the planet? What type of wireless communications could be built
into devices? What changes would need to be made to the existing Internet infrastructure to
support billions of new devices communicating? What would power these devices? What
must be developed to make the solutions cost effective? There were more questions than
answers to the IoT concepts in 1999.
Today, many of these obstacles have been solved. The size and cost of wireless radios has
dropped tremendously. IPv6 allows us to assign a communications address to billions of
devices. Electronics companies are building Wi-Fi and cellular wireless connectivity into a
wide range of devices. ABI Research estimates over five billion wireless chips will ship in
2013. Mobile data coverage has improved significantly with many networks offering
broadband speeds. While not perfect, battery technology has improved and solar recharging

6. General Introduction
2
has been built into numerous devices. There will be billions of objects connecting to the
network with the next several years.
IoT impacts every business. Mobile and the Internet of Things will change the types of
devices that connect into a company’s systems. These newly connected devices will produce
new types of data. The Internet of Things will help a business gain efficiencies, harness
intelligence from a wide range of equipment, improve operations and increase customer
satisfaction. IoT will also have a profound impact on people’s lives. It will improve public
safety, transportation and healthcare with better information and faster communications of
this information. While there are many ways that the Internet of Things could impact society
and business, there are at least three major benefits of IOT that will impact every business,
which include: communication, control and cost savings.

7. State of art

8. State of art
4
Introduction
Internet of Things represents a general concept for the ability of network devices to sense
and collect data from the world around us, and then share that data across the Internet where it
can be processed and utilized for various interesting purposes. In this very purpose we
decided to conduct a project that will allow us to control and automize the waste management
in a smart city. In this chapter we will try to talk about the previous that was held and try to
analyze it as well.
I. Existing solution
1. BRE SmartWaste
SMARTWaste provides a flexible online reporting platform that is suitable to all
company types and sectors. So whether you are a client, or contractor, the building
owner/operator or occupier, SMARTWaste can assist your business to manage and reduce
your waste outputs, impacts and costs.
Our web based tool helps to:
 Save time in tracking and reporting against your company sustainability targets
 Ability to compare your regional and project performance
 Access to all your project information in one place
 Reduce your waste, energy and water costs
 Set and monitor your targets to reduce your site based impacts
 Obtain BREEAM and Code for Sustainable Homes credits
Figure 1: BRE SmartWaste
2. ENEVO
Enevo ONe is a comprehensive logistics solution that saves time, money and the
environment. It uses wireless sensors to measure and forecast the fill-level of waste containers

9. State of art
5
and generates smart collection plans using the most efficient schedules and routes. The
solution provides up to 50% in direct cost savings.
Until now collecting waste has been done using static routes and schedules where
containers are collected every day or every week regardless if they are full or not. Enevo ONe
changes all this by using smart wireless sensors to gather fill-level data from waste
containers.
Figure 2: Enevo ONe
II. Critics
The previous work demonstrates how important waste management systems are
important nowadays. However in an RFID-based garbage collection system, an RFID
collection bin includes a communication module for communicating with a central server, an
RFID tag module for reading the data from an RFID card, automatic garbage entrance, and a
scale function to measure the weight of the food waste. However, the collection bin
communicates only with a server and lacks machine-to-machine communication with the
other collection bins, which may cause a server overload. Furthermore, owing to the delay
incurred from the complex discharge process of an RFID-based garbage collection system,
users have a lengthy wait; in addition, an RFID-based garbage collection system lacks
mobility because of a fixed power supply, causing further user inconvenience.
Conclusion
Owing to the characteristics and merits of IoT services, waste management has also
become a significant issue in academia, industry, and government as major IoT application
fields. An indiscriminate and illegal discharge of waste, an absence of waste disposal and
management systems, and inefficient waste management policies have caused serious
environmental problems and have incurred considerable costs for waste disposal. To handle
these problems, various researches into waste management based on IoT technology have
been conducted, from studies on RFID technology to studies on waste management platforms
and systems.

10. Requirement definition

11. Requirements definition
7
Introduction
After imbibing the general context of the project and presenting the preliminary study
that we have done, we are going to focus in this chapter on define some basic concepts that
will help us to better understand the process of work, then we will analyze similar products to
try to overcome its drawbacks.
I. Requirements analysis
1. Functional requirements
 Trash type
Our trash should detect the type of waste it contains to inform the system if there are
dangerous wastes such as toxic.
 Danger degrees
From the type of the trash already given, our solution will calculate the degrees of danger
contained in the trash and alert the nearest truck to take it off the street.
 Current capacity
One of the features of the smart trash is to send automatically her current capacity in
order to allow the system to verify if it’s already full or not, so that make’s the trucks wait
until they get informed that one of the nearest trash is full.
2. No-Functional requirements
 Powered by solar energy
This no-functional requirement focuses on the cost of energy consumed, that’s why our
solution will be powered by the solar energy given by the generation engines already installed
in the public light poles.
 Real time
It is important that the information given by the sensors be transferred in real time to the
main system.

12. Requirements definition
8
II. Requirements specification
1. Actors identification
The actors that interact with our system are the following:
- Administrator: how is the one working on the main system.
- Agent: the track driver.
2. Use case diagrams
In this section we present the general use case diagram of our solution.
2.1. General use case
The Figure below shows the solution’s general use case. It contains the general
functionalities that the Smart trash offers:
Figure 3: General use case
2.2. Detailed use case
After presenting the general use case diagram of the solution, we detail subsequently the
import use cases.

13. Requirements definition
9
o Retrieve trucks list
The following use case diagram detailed the administrator use case of retrieve trucks list.
Figure 4: Retrieve trucks list use case
Conclusion
In this chapter, we have established the requirements analysis and have defined the
requirements specifications. This has led us to clearly identify the system's actors and the
features it should implement.

14. Conception

15. Conception
11
Introduction
This chapter consist of a logical description how our system going to work, by shaping
the system and append an architecture.
I. Class diagram
For the class diagram we divided the system into three parts
Trash: the censors
System: the server
GPS: the GPS in the trunks
Figure 5: Class diagram

16. Conception
12
II. Activity diagram
The activity diagram is the workflow of step activity and actions of our system.
Figure 6: Activity diagram
III. Sequence diagram
This graph presents the scenario of our system.
Every time the sensors in the trash send their status to the server,
When trash need to be treated the server request from trunk their position then send new
itinerary to the closest trunk to the trash

17. Conception
13
Figure 7: Sequence diagram
Conclusion
In this chapter we described the system using Class, Sequences and activity diagrams.

18. Proof of concept

19. Proof of concept
15
Introduction
I. Architecture
1. Hardware architecture
1.1. Weight Sensor
1.2. Level sensor:
Level sensors detect the level (as in water level) of substances that flow,
including liquids, slurries, granular materials, and powders. The substance to
be measured can be inside a container or can be in its natural form (e.g., a
river or a lake).
It will be implemented on the top level of the can to calculate the level
of trash inside it.
Figure 9: Level
sensor
1.3. Server:
A web server is a computer system that processes requests via HTTP, the
basic network protocol used to distribute information on the World Wide Web.
It will have an entire system to get the data from the cans, make the
necessary calculations and take the decisions to send to the trucks about the
Figure 10:
Server
A load cell is a transducer that is used to create an electrical signal
whose magnitude is directly proportional to the force being measured.
This sensor will be used to measure the trash load inside the can. Figure 8: Weight
sensor

20. Proof of concept
16
state of cans, positions, shortest road and priority.
1.4. Global Positioning System GPS:
The Global Positioning System (GPS) is a space-based satellite
navigation system that provides location and time information in all
weather conditions, anywhere on or near the Earth where there is an
unobstructed line of sight to four or more GPS satellites.
Every truck will be equipped with an interactive GPS system to guide
and show the information retrieved from the server.
Figure 11: GPS
1.5. Arduino:
2. Software architecture
2.1. Apache:
The Apache HTTP Server, colloquially called Apache, is the world's most widely-used
Web server software. In 2009, it became the first Web server software to serve more than 100
million Web sites.
Figure 13: Apache
Arduino is a family of single-board micro controllers, intended to
make it easier to build interactive objects or environments.
With every can, an Arduino card will be connected to every sensor to
gather the data and transfer it to the server via wifi or any wireless
connection available.
Figure 12: Arduino

21. Proof of concept
17
2.2. MySql:
MySQL officially, but also called "My Sequel” is the world's second most widely used
open-source relational database management system (RDBMS). The SQL phrase stands for
Structured Query Language.
Figure 14: MySql
2.3. php:
PHP is a server-side scripting language designed for web development but also used as a
general-purpose programming language. As of January 2013, PHP was installed on more than
240 million websites (39% of those sampled) and 2.1 million web servers.
Figure 15: PHP
2.4. C++:
C++ is a general purpose programming language. It has imperative, object-oriented and
generic programming features, while also providing the facilities for low level memory
manipulation.
Figure 16: C++
II. Scenarios:
Can Concept:
The Can is designed to analyze what’s inside it using the Arduino card that is connected
to a level sensor, the weight sensor.

22. Proof of concept
18
Figure 17: Can concept
Sending data to the server:
The Can is programmed to send regular data about it is status and the data that is gathered
in real time to a remote server in the cloud. The server will analyze the data from all the trash
Cans connect and take decisions based on what it has.
Figure 18: Sending Data to server
Sending data to the trucks:
After analysing the data from the Cans and the truck (state, position) the server will
decide which truck to contact and to send the itinerary to collect the cans.

23. Proof of concept
19
Figure 19: Sending Data to trucks
GPS Tracking:
After the data is sent to the truck, the GPS system will indicate the itinerary to the driver,
and the process is done.
Figure 20: GPS Tracking
Conclusion

24. General conclusion
20
General conclusion