appropriate formats (text, draw, VoIP) and to send
the complex requests to the experts and/or web
services which should be resolved by them. Client
applications are implemented on Pocket PCs.
There is only one helpdesk operator and many
experts in one consultation session.
The network communication is realized in a way
that clients send UDP datagrams to the server, and
the server resends the UDP datagrams, according to
the contents of the received message.
The communication protocol between the agents
and the information flow rely on fuzzy logic. In this
case, the fuzzy logic is used for enabling or
disabling (adaptation) some controls depending on
the quality of the service (QoS), i.e. the signal
strength. So, if the signal strength is good, the
features of chat, draw and VoIP will be enabled.
However, for medium signal the VoIP feature will
be disabled. For bad signal, beside the VoIP, the
draw feature should be also disabled, and the only
active communication feature will be chat.
Streams are used for the voice transfer. Desktop
based clients (for both helpdesk operator and
experts) can be also connected to the server.
The Web services are used to find the solution of
the problem using the wireless Internet access. If the
Web services are unable to find the solution, the
Experts are activated. Some types of Web services
are used for the responses. These Web services
support and convert various types of media data.
The experts interface has controls for chat, draw,
VoIP, file upload/download, authority control (VoIP
channel).
The helpdesk operator can give the control over
the interface (or by giving the speaking possibility)
and reclaim the control later. Helpdesk operator has
the role of a moderator in the consultation process.
Figure 1 shows the architecture of the MBEA.
Client applications reside on pocket PCs and they
have three main parts: Helpdesk agent, which
manages operator interaction within the application
and communicates with interoperability agent. VoIP
client serves for the voice transfer, and the client
application represents all the features mentioned
above (chat, draw, voice, file up/download,
communication among clients). Expert Agent
receives and sends the resolved requests using
various file types (like text, image, and voice).
Collaboration Agent calculates the cost of the
corresponding expert’s service. The communication
is realized through wireless area networks
connected to the Internet.
The server contains Interoperability Agent
which redirects the complex request to the Experts
and/or Web services and exchanges reformatted
media types; Passive helpdesk Agent calculates the
helpdesk interface; Media Agent monitors the
media contents (text, image or voice); Experts and
helpdesk preferences are stored in XML data
storage; VoIP Server is responsible for voice
transfer and UDP server application manages the
login, chat, draw and control. For the purpose of
saving the memory and processing power of the
clients handheld devices, Passive Helpdesk Agents
and Media Agent reside on the server side. The
agents are XML based.
4 MBEA DESIGN
In this paper, we describe our approach in
development of a MBEA by using multi XML
agents and fuzzy logic. Helpdesk agent resides on
the client side, and monitors the helpdesk operator’s
interaction by using the features of the application
and communicates with interoperability agent (e.g.
sends the request to the available competent experts
and/or web services, receives the response in
corresponding format and regulates the customers
billing). The triggers that demand helpdesk agent’s
actions are: drawing, sending chat messages, and
communicating using VoIP. This agent is named
Helpdesk because it helps the customers to simply
resolve their requests. At the start of the
communication session, helpdesk agent
communicates with the Passive helpdesk agent and
interoperability agent that reside on the server. The
Passive agent demands the information from the
Media agent about the type of the files to be used for
the particular communication session. This agent is
named passive helpdesk since it waits to be invoked;
it recalculates the interface structure and sends the
data to the helpdesk agent which finally draws the
interface. The Expert Agent receive the requests in
some format (text, file, voice) from the
interoperability agent, concerns about the solution of
the requests, sends the solutions to interoperability
agent, modifies the expert’s profile, checks the QoS
and billing status.
The main tasks of the interoperability agent are:
receiving the requests from helpdesk agent and
forwarding them to the expert agents and/or web
services. Also it exchanges reformatted data files
with helpdesk agent. Media agent monitors the
folder with the data files for the communication
session, and sends this information to the Passive
helpdesk agent. The Passive helpdesk agent
recalculates the helpdesk interface according to the
MOBILE BUSINESS EXPERT ADVISOR
205