Project

ZigBee Alliance

Title<Spec 0.92
Philips Disclosure of Necessary Claims>

Date
Submitted

26 October 2004

SourceBob Kraus
Philips IP&S
345 Scarborough Road
P.O. Box 3001
Briarcliff Manor, NY 10510-8001

Re:[Form for Necessary Claims Declaration.]

Abstract[Use this form to disclose and state position regarding licensing of necessary
claims. If your company intends to declare intellectual property contributions
necessary to implement ZigBee specifications, complete this form according to the
instructions.]

Purpose[.]NoticeThis document has been prepared to assist the ZigBee Alliance. It is offered as abasis for discussion and is not binding on the contributing individual(s) ororganization(s). The material in this document is subject to change in form andcontent after further study. The contributor(s) reserve(s) the right to add, amend orwithdraw material contained herein.

ReleaseThe contributor acknowledges and accepts that this contribution will be posted in
the member area of the ZigBee web site AS PHILIPS CONFIDENTIAL
INFORMATION.

Form Approved by ZigBee Alliance – __Feb_, 2004

Voice:
Fax:
E-mail:[914-333-9634][ 914-332-0615][Bob.Kraus @Philips.com]

Version 1.0

30390093

LegalNoticeCopyright © ZigBee Alliance, Inc. (2003). All rights Reserved
Elements of ZigBee Alliance specifications may be subject to third party intellectual property
rights, including without limitation, patent, copyright or trademark rights (such a third party may
or may not be a member of ZigBee). ZigBee is not responsible and shall not be held responsible inany manner for identifying or failing to identify any or all such third party intellectual property
rights.
This document and the information contained herein are provided on an “AS IS” basis and ZigBee
DISCLAIMS ALL WARRANTIES EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO (A) ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
WILL NOT INFRINGE ANY RIGHTS OF THIRD PARTIES (INCLUDING WITHOUT
LIMITATION ANY INTELLECTUAL PROPERTY RIGHTS INCLUDING PATENT,COPYRIGHT OR TRADEMARK RIGHTS) OR (B) ANY IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NONINFRINGEMENT. IN NO EVENT WILL ZIGBEE BE LIABLE FOR ANY LOSS OF PROFITS,
LOSS OF BUSINESS, LOSS OF USE OF DATA, INTERRUPTION OF BUSINESS, OR FOR
ANY OTHER DIRECT, INDIRECT, SPECIAL OR EXEMPLARY, INCIDENTIAL, PUNITIVE
OR CONSEQUENTIAL DAMAGES OF ANY KIND, IN CONTRACT OR IN TORT, IN
CONNECTION WITH THIS DOCUMENT OR THE INFORMATION CONTAINED HEREIN,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. All Company,
brand and product names may be trademarks that are the sole property of their respective owners.
The above notice and this paragraph must be included on all copies of this document that are
made.
ZigBee Alliance, Inc.
2694 Bishop Drive, Suite 275
San Ramon, CA 94583

Form Approved by ZigBee Alliance – __Feb_, 2004

Version 1.0

30390093

NECESSARY CLAIMS DECLARATION(APPLIES TO BOTH PROMOTER MEMBERS AND PARTICIPANTS)
Please return or FAX to:

Executive Director, ZigBee Alliance
c/o Global Inventures
2400 Camino Ramon, Suite 375
San Ramon, CA 94583 USA
PHONE (+1 925-275-6607) FAX (+1 925-275-6691)

Disclosure Period:_____ to 27 OCT. 2004

This Declaration is made in accordance with and subject to the ZigBee Alliance Intellectual Property Rights Policy
A. ZIGBEE ADOPTED SPECIFICATION or ZIGBEE PROPOSED SPECIFICATION:
Number: ______0.92________________
Title: ______________________________
B. MEMBER ORGANIZATION:
Legal Name of Member Organization: __________Philips Electronics North America Corporation_______________
If the Member is completing this Declaration to disclose Necessary Claims of an Affiliate or Non-Member, the Member
must provide the following information:
Legal Name of Affiliate:

Koninklijke Philips Electronics N.V.

Member is authorized to act on behalf of Affiliate in filing this Disclosure.
C. CONTACT FOR LICENSE TERMS AND CONDITIONS:Name of Organization: _________Philips Electronics North America Corporation
Name of Individual & Department: ___Robert J. Kraus, Intellectual Property & Standards
Address: ___345 Scarborough Road; P.O. Box 3001; Briarcliff Manor, NY 10510-8001
Telephone: 914-333-9634 Fax: 914-332-0615 E-mail: Bob.Kraus@Philips.com
D. POSITION REGARDING LICENSING OF NECESSARY CLAIMS:
If the Member owns, has a right to, or is aware of any Necessary Claims, please specify the patent number, patentapplication number and/or relevant claims.
(SEE ATTACHMENT A)
With respect to licensing such Necessary Claims, Member declares as follows (check one box only):1.

The parent of Member is prepared to grant a Royalty Free License to the Alliance, Promoter Members and Participantsin respect of claims identified on Attachment A as “Mandatory”.
E. The parent of Member is willing to grant a fee-based license, under the claims identified on Attachment A as
Optional (and variations of such claims) and under reasonable and non-discriminatory terms and conditions, to the
Alliance, Promoter Members and Participants in order to fully comply with the ZigBee Proposed Specification
0.92 or Adopted Specification.
E. SIGNATURE:

Print name of authorized person:___________________Robert J. Kraus________________________
Title of authorized person: ________________Principal Counsel, Intellectual Property________
Signature of authorized person: __________________________________ Date: ___________________________

Form Approved by ZigBee Alliance – __Feb_, 2004

Version 1.0

30390093

February, 2004

ZigBee-<doc#>
ATTACHMENT A

Spec 0.92 documents referenced are:
• 02130r9 Network Specification• 03525r5 ZigBee Application Framework Specification• 03529r6 ZigBee Device Profile
PHGB 010073
Section of
Mandatory/Optional Proposed Spec.
0.92

Relevant Claims
3. A method of operating a master-slave distributed
network comprising a master node and a plurality ofslave nodes, the master node and the slave nodes
being operatively interconnected, wherein a slave
node wishing to send a data packet to the masternode includes in the data a prestored address of thenext node in a route to the master node andtransmits the data packet.

Mandatory

02130r9
10.3.2, 10.3.3

4. A method as claimed in claim 3, characterised inthat a slave node receiving a data packet includes inthe data packet the stored address of the next nodein the route to the master node before transmitting
the data packet.

Mandatory

02130r9
10.3.3

5. A method as claimed in claim 3 or 4,
characterised by the master node including
addresses of the slave nodes on a route to a
destination slave node in a data packet to betransmitted.

Mandatory

02130r9
10.2.1 (limited: 1 or
2 hops only)

6. A method as claimed in claim 5, characterised bya slave node receiving a data packet removing its
own address from the data packet and transmitting
the altered data packet.

Mandatory

02130r9
10.3.3

Mandatory

02130r9
10.3.4

Optional

02130r9
10.3.5

7. A method as claimed in any one of claims 3 to 6,
characterised by a new slave node transmitting an
invitation message requesting routing informationfrom in-range slave nodes, the new slave node
receiving routing information and determining whichof the in-range slave nodes is the preferred node in
its route to the master node and storing its address.
8. A method as claimed in any one of claims 3 to 7,
characterised by, after an alteration in the network,
slave nodes re-examining their routes to the masternode and in response to a slave node finding that its
route does not comply with predetermined routing
criteria, that slave node setting-up a new route bystoring the address of the next node in its route.

Page 4

Philips Confidential

February, 2004

ZigBee-<doc#>

PH GB030052
Section of
Mandatory/Optional Proposed Spec.
0.92

Relevant Claims
1. A method of operation of a networked device in a
network having at least one other device, the method
including:sending (104) a simple device description query
message to at least one other device requesting asimple device description;
receiving (106) from the other device a simple device
description message of defined length including adevice type value representing the type of the otherdevice;sending (108) an extended device description query
message to the other device requesting an extended
device description from the other device; andreceiving (110) from the other device an extended
device description of variable length.
2. A method according to claim 1 further including
establishing (102) the network address of anotherdevice or other devices before the step of sending(104) a simple device description to at least one otherdevice.
8. A method of operation of a networked device,including:receiving (104) a simple device description query
message from one of the other devices requesting asimple device description;
sending (106) to the other device a simple device
description message of defined length including adevice type value representing the type of the
networked device;receiving (108) an extended device description query
message from the other device requesting an
extended device description from the networked
device; andsending (110) to the other device an extended device
description of variable length.

Page 503525r5
6.4, 6.5
Optional
03529r6
5.1.1.5, 5.1.1.8

02130r9
10.1.3
Optional
03529r6
5.1.1.1, 5.1.1.2

03525r5
6.4, 6.5
Optional

03529r6
5.1.1.5, 5.1.1.8,
5.2.1.5, 5.2.1.8

Philips Confidential

February, 2004

ZigBee-<doc#>

9. A networked device, including:a transceiver (8) for sending and receiving messages:
anda message handler (26, 182) arranged to carry out thesteps of:on receiving (104) a simple device description query
message from one of the other devices, sending (106)to the other device a simple device description
message of defined length including a device typevalue representing the type of the networked device;andon receiving (108) an extended device description
query message from another device sending (110) to
the other device an extended device description ofvariable length.
11. A networked device, including: a transceiver (8)for sending and receiving messages: a message
handler (26, 182) arranged to carry out the steps of:sending a simple device description query message toanother device requesting a simple device
description; receiving from the other device a simple
device description message of fixed length including adevice type value representing the type of the otherdevice and a field indicating whether an extended
device description is available; and further arranged tooptionally carry out the steps of: testing the simple
device description message to determine whether an
extended device description is available; sending an
extended device description query message to theother device requesting an extended device
description from the other device; and receiving fromthe other device an extended device description ofvariable length.

Page 603525r5
6.4, 6.5
Optional

03529r6
5.1.1.5, 5.1.1.8,
5.2.1.5, 5.2.1.8

03525r5
6.4, 6.5
Optional

03529r6
5.1.1.5, 5.1.1.8,
5.2.1.5, 5.2.1.8

Philips Confidential

February, 2004

ZigBee-<doc#>

15. A system, comprisinga plurality of networked devices each having atransceiver for sending and receiving network
messages;at least one networked device arranged to send a
simple device query message to other devices and toreceive and interpret simple device description
messages subsequently received from the otherdevices;
at least one networked device arranged to send an
extended device query message to other devices andto receive and interpret extended device description
messages subsequently received from the otherdevices;each of the networked devices being arranged torespond to an incoming simple device query message
from another of the devices by sending a simple
device description message of defined length
including a device type value representing the type ofthe device; andat least one of the networked devices is arranged torespond to an incoming extended device query
message from another of the devices by sending an
extended device description message.

Optional

18. A computer program for controlling a networked
device, the computer program being arranged tocause the networked device to carry out the steps of amethod according to any of claims 1 or 2.

Optional

As 1 & 2

20. A computer program according to claim 18
recorded on a data carrier (14).

Optional

As 1 & 2

Page 703525r5
6.4, 6.503529r6
5.1.1.5, 5.1.1.8,
5.2.1.5, 5.2.1.8

Philips Confidential

February, 2004

ZigBee-<doc#>

PHGB 030054

Relevant Claims
3. A method of operation of a networked
device, including:transmitting or receiving (104) a simple
device description message (230) of defined
length, the simple device description
message being in the form of a tokencompressed message compressed from ahuman-readable message format, themessage including a device type value
representing the type of the other device; thedevice type value being selected from adevice type hierarchy having predetermined
top level elements including a controller
device type (52) and a basic device type(54), and at least one further level (68) of
subsidiary device types depending from thebasic device type (54) and inheriting
properties of higher level device types on
which the subsidiary device type depends,
but not including any further level ofsubsidiary device types depending from thecontroller device type (52).
4. A method according to claim 3 further
including the steps of:establishing (102) the address of at least
one other device;sending (104) a simple device description
query message to the other device or one ormore of the other devices requesting asimple device description;
receiving (106) from the other device or
devices the simple device description
message.

Mandatory/Optional

Mandatory for transmission
but
optional(ZigBee critical)
for reception

Section of
Proposed Spec.
0.92

03525r5
6.403529r6
5.2.1.502130r9
10.1.3

Optional

03525r5
6.403529r6
5.1.1.1, 5.1.1.2,
5.1.1.5, 5.2.1.5

5. A method according to claim 3 further
comprisingsending (108) an extended device
description query message to the otherdevice or one of the other devices requesting
an extended device description from theother devices; andreceiving (110) from the other device or theone of the other devices an extended device
description of variable length.

03525r5
6.5
Optional
03529r6
5.1.1.8, 5.2.1.8

Page 8

Philips Confidential

February, 2004
14. A networked device, including: atransceiver (8) for sending and receiving
messages; and: a message handler (26, 182)
arranged to send or receive simple device
description message of defined length, thesimple device description message being in
the form of a token-compressed message
compressed from a human-readable
message format, the message including adevice type value representing the type ofthe other device; the device type value being
selected from a device type hierarchy having
predetermined top level elements including acontroller device type (52) and a basic device
type (54), and at least one further level (68)of subsidiary device types depending fromthe basic device type (54) and inheriting
properties of higher level device types on
which the subsidiary device type depends,
but not including any further level ofsubsidiary device types depending from thecontroller device type (52).
15. A networked device according to claim
14,
wherein the message handler is arranged tocarry out the steps of:establishing (102) the address of at least
one other device;sending (104) a simple device description
query message to another device requestinga simple device description;
receiving (106) from the other device thesimple device description message of fixed
length including a device type value
representing the type of the other device anda field indicating whether an extended device
description is available;
and further arranged to optionally carry out
the steps of:testing the simple device description
message to determine whether an extended
device description is available;sending (108) an extended device
description query message to the otherdevice requesting an extended device
description from the other device; andreceiving (110) from the other device anextended device description of variable
length.

ZigBee-<doc#>

03525r5
6.4
Mandatory
03529r6
5.2.1.502130r9
10.1.3

Optional

03525r5
6.4, 6.503529r6
5.1.1.1, 5.1.1.2,
5.1.1.5, 5.1.1.8,
5.2.1.5, 5.2.1.8

Page 9

Philips Confidential

February, 2004

ZigBee-<doc#>

20. A computer program defining a device
type hierarchy having predetermined top
level elements including a controller device
type (52) and a basic device type (54), andat least one further level (68) of subsidiarydevice types depending from the basic
device type (54) and inheriting properties of03525r5
Mandatory for
6.4
higher level device types on which thetransmissionbutoptional(ZigBe
subsidiary device type depends, but note critical)for reception
including any further level of subsidiary03529r6
device types depending from the controller
5.2.1.5
device type (52), the computer program
being arranged to cause a networked device(2,4) to send and/or receive simple device
description messages (230) including thedevice type selected from the device typehierarchy.

Page 10

Philips Confidential

February, 2004

ZigBee-<doc#>

21. A computer program according to claim
20 for controlling a controller-type networked
device, the networked device having atransport stack and an application, thecomputer program comprising:code implementing a transport adaption layer(180) for interfacing with the transport stack;code implementing an application
programming interface (186) for interfacingwith the application; andcode implementing a messaging layer (182)including the capabilities of sending andreceiving messages in a token-encoded
human readable messaging format, the code
being arranged to cause the networked
device:to recognise incoming device query
messages requiring a simple device
description response and to provide a simple
device description response including adevice type of controller device type;to respond to an incoming controller query
message querying whether the networked
device can control a predetermined device
type by responding with the lowest level ofdevice type in the list of device types that canbe controlled by the networked device thateither is the predetermined device type or isa higher level device type from which thepredetermined device type depends; andto carry out the steps of:sending a device query message to anotherdevice;receiving a response from the other device
indicating the device type of the other device,
the device type being selected from a device
type hierarchy having predetermined top
level elements including a controller device
type and a basic device type, and at least
one further level of subsidiary device types
depending from the basic device type andinheriting properties of higher level device
types on which the subsidiary device type
depends, but not including any further levelof subsidiary device types depending fromthe controller device type;determining the extent to which the
networked device can control the otherdevice by determining the lowest level ofdevice type that either is the device type ofthe other device or is a higher level device
type from which the device type of the otherdevice depends, in the list of device types

03525r5
6.4
Optional
03529r6
5.1.1.5, 5.2.1.5

Page 11

Philips Confidential

February, 2004

ZigBee-<doc#>that can be controlled by the networked
device; andcontrolling the other device with thefunctionality of the determined lowest level ofdevice type by sending control signals
selected from a list of control signals
appertaining to the determined lowest level ofdevice type.

Page 12

Philips Confidential