This repository has been archived by the owner on Nov 16, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 38
/
rfp-0002-Device_Access.html
281 lines (208 loc) · 6.4 KB
/
rfp-0002-Device_Access.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Mozilla/4.6 [en] (WinNT; I) [Netscape]">
<title>RF-0002 - Device Access RFP</title>
</head>
<body bgcolor="#FFFFFF">
<center><table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="90%" >
<tr>
<td ALIGN=LEFT WIDTH="30%"> </td>
<td ALIGN=LEFT WIDTH="50%"> </td>
<td ALIGN=LEFT> </td>
</tr>
<tr>
<td>Java Expert Group </td>
<td> </td>
<td>Mathis</td>
</tr>
<tr>
<td ALIGN=LEFT>Request for Proposal: 0002</td>
<td ALIGN=LEFT> </td>
<td ALIGN=LEFT>Motorola </td>
</tr>
<tr>
<td ALIGN=LEFT>Expires 20 days after: (tbd)</td>
<td ALIGN=LEFT> </td>
<td ALIGN=LEFT>16 Sept 1999 </td>
</tr>
<tr>
<td ALIGN=LEFT>rfp-0002.html</td>
<td ALIGN=LEFT> </td>
<td ALIGN=LEFT> </td>
</tr>
<tr>
<td ALIGN=LEFT> </td>
<td ALIGN=LEFT> </td>
<td ALIGN=LEFT> </td>
</tr>
</table></center>
<center>
<h2>
Device Access RFP</h2></center>
<center><table BORDER=0 CELLSPACING=0 CELLPADDING=0 WIDTH="90%" >
<tr>
<td ALIGN=LEFT WIDTH="100%">
<dl>
<dt>
Status of this Memo </dt>
<dd>
This document suggests the following improvement to the OSGi specification
for the Open Services Gateway Initiative, and requests discussion. Distribution
of this document is unlimited. </dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Abstract </dt>
<dd>
A key component of the Open Services Gateway initiative is an open framework
that defines how services access devices attached to the gateway, either
directly or via a local network.. This RFP provides some general
goals and guidelines and solicits technical submissions that will lead
to defining a Java-based device access API.</dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Acknowledgment </dt>
<dd>
The author wants to acknowledge the contributions of the members of the
Connected Alliance. </dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Introduction </dt>
<dd>
The device framework Java API defines a basic set of capabilities needed
for on-demand dynamically loaded services for devices, appliances and network
hardware attached to an open service gateway. Examples of such devices
include security systems, sensors, coffee makers, remotely controlled appliances,
TV set top boxes, and personal computers. The API must support both
devices attached directly to the gateway and devices accessed from the
gateway via a local communications network. The API must not require
any specific network architecture and must work with a diverse set of wired
and wireless local network technologies. The device APIs must
work in resource constrained devices and should leverage as best
possible existing Java APIs, tools, and techniques.</dd>
<dt>
</dt>
<dd>
While device access APIs for other languages and runtime environments may
be useful in the future, this RFP is focused explicitly only on a Java
language API running in conjunction with a services framework API [1].</dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Technical Discussion </dt>
<dd>
The device framework Java API must provide, at a minimum, the following
capabilities and features:</dd>
<ul>
<li>
On-demand loading of device and network services using the services framework
Java API.</li>
<li>
Independence from any specific network architecture.</li>
<li>
Compatible with any of the emerging local networking standards, including
HomeRF and Bluetooth.</li>
<li>
Independence from any specific device characteristics.</li>
<li>
Automatic addition and deletion of devices when supported by the underlying
communication mechanisms.</li>
<li>
Manual configuration of legacy local networks and their attached devices.</li>
</ul>
<dd>
Additional feature and capability requirements may be found in the Market
Requirements document currently being developed. Other attributes
and capabilities of the device access API may be defined during the course
of the development of the API specification.</dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Security Considerations </dt>
<dd>
As a request for technical proposals, this document has no direct security
considerations. However, the resulting device access API may significantly
impact the security of services running within a gateway and a security
review is needed before approval of the API.</dd>
<dt>
</dt>
<dd>
</dd>
<dt>
References </dt>
<dd>
[1] Mathis, J., "Services Framework RFP", RFP-0001, September 16, 1999. </dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Author's Address </dt>
<dd>
First Name: Jim</dd>
<dd>
Last Name: Mathis</dd>
<dd>
Company Name: Motorola</dd>
<dd>
Company Division: Personal Networking Group</dd>
<dd>
Street Address: 50 E. Commerce Drive</dd>
<dd>
City, State, Country, Postal Code: Schaumburg IL, USA 60173</dd>
<dd>
</dd>
<dd>
voice: + 1-847-576-0674</dd>
<dd>
fax: + 1-847-538-4253</dd>
<dd>
email: <a href="mailto:[email protected]">[email protected]</a></dd>
<dt>
</dt>
<dd>
</dd>
<dt>
Full Copyright Statement </dt>
<dd>
Copyright (C) The Open Services Gateway Initiative (1999).</dd>
<br>All Rights Reserved.
<p>This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it may
be prepared, copied, published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice and this
paragraph are included on all such copies and derivative works. However,
this document itself may not be modified in any way, such as by removing
the copyright notice or references to the Open Services Gateway Initiative.
<p>The limited permissions granted above are perpetual and will not be
revoked by the Open Services Gateway Initiative or its successors or assigns.
<p>This document and the information contained herein is provided on an
"AS IS" basis and THE OPEN SERVICES GATEWAY INITIATIVE DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE
USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
<dt>
</dt>
<dd>
</dd>
</dl>
</td>
</tr>
</table></center>
<hr><!-- hhmts start -->
<br>Expires 20 days after: (tbd)<!-- hhmts end -->