|
1. Purpose
Fixed and mobile devices (such as mobile phones, desktop and pocket PCs) equipped with communication facilities such as Infrared, Bluetooth and Wireless LAN and technologies like Jini and UPnP, make the establishment of ad hoc networks of several devices both possible and increasingly commonplace. TC Ad Hoc’s interest lies in ‘ad hoc FIPA’, that is, ad hoc networks which consist of devices running either complete FIPA-compliant agent platforms, fragments of FIPA-compliant platforms or a combination of the two. TC Ad Hoc will either modify relevant existing FIPA Specifications, or create a new specification to ensure that interoperability between FIPA-compliant agent platforms and/or platform fragments can be maintained in ad hoc networks.
2. Organisation and Contacts
|
Chair
|
Michael Berger (Siemens)
|
|
Co-Chair
|
Michael Pirker (Profactor)
|
|
Chair Email
|
adhoc-chair(at)fipa.org
|
|
Editor
|
Michael Berger (Siemens)
|
|
Credits
|
Anil Kumar Gunesh, Juan Jim Tan, Constantinos Neophytou, Leonid Titkov, Stefan Posland, Marius Walliser, Steve Quirolgico, Yugi Wada, Wei Lin, Kari Koivuniemi, Heimo Laamanen, Jamie Lawrence, Michael Watzke, John Shepherdson, Tadashi Araragi, Celeste Campo, Heikki Helin, Mikko Laukkanen, Santtu Toivonen, Fabio Bellifemine, Keven Keven Keaney, Renato Levy, Margaret Lyell, Michael Pirker, David Cabanillas, Monique Calisti, Giancarlo Fortino, Xuan Huang, Ben Mankin, Rainer Umland, Juan Jim Tan, Yanmin Xi and Michael Berger
|
|
Mailing List
|
adhoc(at)fipa.org
|
3. Documents (latest versions)
|
Specifications
|
FIPA00023K FIPA Agent Management Specification
PC00095A FIPA Agent Discovery Service Specification
SC00023XX FIPA Agent Management Specification - up for discussion
|
|
Work Plans
|
[f-wp-00020] Agents in Ad Hoc Environments Work Plan
(Version A 2003/08/23)
|
|
Responses to 1st
AdHoc CfT
|
[f-in-00061] Response from UMBC
[f-in-00062] Response from Media Lab Europe
[f-in-00063] Response from Universidad Carlos III de Madrid
[f-in-00064] Response from Siemens
|
|
Input for
FIPA 26
|
[f-in-00069] FIPA Adhoc Architecture Possibilites from Siemens
[f-in-00070] Contribution from Universidad Carlos III de Madrid
[f-in-00071] Contribution from BTexact Technologies
|
|
Input for
FIPA 28
|
[f-in-00091] Towards a FIPA Approach from Mobile Ad-hoc
Environments by Siemens and Sonera
|
|
Whitepaper
|
[f-in-00068A] Current Ad-Hoc Whitepaper
|
|
Input for
FIPA 30
|
[PC00095A] FIPA Agent Discovery Service Specification
[PC00096A] FIPA JXTA Discovery Middleware Specification
|
4. Milestones
|
Date
|
TC Milestones
|
|
2002/02
|
Publish workplan [f-wp-00020] and get acceptance from FAB
|
|
2002/02
|
Establish TC, open call for technical technology (CFT) [f-out-00105]
|
|
2002/04
|
Deadline for technical contributions
|
|
2002/05
|
Presentation of technical contributions, structuring, discussion
|
|
2002/10
|
Deliver first draft of preliminary specification
|
|
FIPA29
|
Making specification as experimental
|
|
FIPA 30
|
Deliver first draft of preliminary specification
|
|
FIPA 31
|
Marking specification as experimental, deliver white paper
|
5. Remit
FIPA has already addressed some of the problems related to wireless communication in the FIPA nomadic Application Support Specification [FIPA00014], FIPA Device Ontology Specification [FIPA00091], FIPA Message Buffering Service Specification [FIPA00092], and FIPA Messaging Interoperability Services Specification [FIPA00093]. However, further specifications are required to address a number of issues in order to facilitate interoperability between agents operating on different platforms in ad hoc environments.
6. Status
The following Adhoc meeting resolutions were made at the 32nd FIPA meeting in Rockville, MD:
The Ad-Hoc TC did not meet.
Status updates from this and prior meetings can be found in the respective resolutions. This information is available at FIPA Past Meetings.
7. How to Contribute
Communication to the working group is via the email mailing list adhoc(at)fipa.org.
|
