Note: Descriptions are shown in the official language in which they were submitted.
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
METHOD OF DISTRIBUTING INFORMATION REGARDING ONE OR MORE
ELECTRICAL DEVICES AND SYSTEM FOR THE SAME
FIELD OF THE INVENTION
[0001] This invention relates generally to systems and method to
provide information,
and relates more particularly to systems configured to provide information
regarding
electrical devices and methods for the same.
DESCRIPTION OF THE BACKGROUND
[0002] In today's widely used IP (intern& protocol) networks, the
Dynamic Host
Configuration Protocol (DHCP) is commonly used to dynamically assign an IP
address to an electrical device coupled to a network. DHCP is a useful and
convenient mechanism that allows new electrical devices to connect to a
network
without manual configuration. Although DHCP allows the assignment of a dynamic
IP address to an electrical device, no convenient method exists for other
electrical
devices or users to determine the new dynamically assigned IP address of the
electrical device. Because the IP address has been dynamically assigned, the
IP
address can change every time the electrical device is plugged into the
network,
removed, and plugged in again so the dynamically assigned IP address of the
electrical device may need to be repeatedly determined.
[0003] Many methods to retrieve the dynamically assigned IP address
involve using
proprietary visual user interfaces of the electrical device or a gateway
device. For
example, if the electrical device has a visual display capability (e.g.,
laptops, mobile
phones, printers with an LCD display, game consoles coupled to a television,
etc.), a
proprietary method of navigating a visual user interface usually exists to
allow the
user to determine the new dynamically assigned IP address.
[0004] In the same or different examples, the router or other gateway
device that hosts
the DHCP server can have a proprietary visual user interface that allows the
user to
navigate a series of screens, menu items, and/or commands to determine the
newly
assigned dynamic IP address for the electrical device. However, in this
method, the
user is required to know the MAC (media access control, or hardware) address
of the
electrical device and then look up the MAC address in a table to find the
associated
dynamically assigned IP address.
1
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0005] Furthermore, standard and widely adopted protocols such as
UPnP (universal
plug and play), DLNA (digital living network alliance), and Bonjour work in
the
application layer above TCP/IP (transmission control protocol/internet
protocol) and
allow for dynamic discovery of new electrical devices provided that those new
electrical devices also participate in and support the proprietary discovery
protocol.
However, these protocols are generally only useful within a local private
network. If
the proprietary discovery protocol works in both private and public networks,
the
proprietary discovery protocol requires the user to enter two different
addresses to
access the electrical device depending on whether the user is inside or
outside of the
local network.
[0006] Accordingly, a need or potential for benefit exists for a
method and/or system
that allow a user to discover easily a dynamically assigned IP address for an
electrical
device and to access and use the electrical device without knowing the DHCP
address.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] To facilitate further description of the embodiments, the
following drawings are
provided in which:
[0008] FIG. 1 illustrates a block diagram of a system configured to
provide information
regarding at least one electrical device, according to a first embodiment;
[0009] FIG. 2 illustrates a block diagram of an exemplary electrical
device of FIG. 1,
according to the first embodiment;
[0010] FIG. 3 illustrates a rear view of an exemplary gateway device
of FIG. 1,
according to the first embodiment;
[0011] FIG. 4 illustrates a representative block diagram of an
example of the elements
included in the circuit boards inside a chassis of the gateway device of FIG.
3;
[0012] FIG. 5 illustrates a front view of an exemplary internal
client computer of FIG.
1, according to the first embodiment;
[0013] FIG. 6 illustrates a representative block diagram of an
example of the elements
included in the circuit boards inside chassis of the internal client computer
of FIG. 5;
[0014] FIG. 7 illustrates a block diagram of an exemplary
registration server of FIG. 1,
according to the first embodiment;
[0015] FIG. 8 illustrates a flow chart for an exemplary embodiment of
a method of
distributing information regarding one or more electrical devices using a
first server,
according to the first embodiment;
2
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0016]
FIG. 9 illustrates a flow chart for an exemplary embodiment of an activity
of
registering the electrical device, according to the first embodiment;
[0017] FIG. 10 illustrates a flow chart for an exemplary embodiment of
an activity of
processing a request for information about the electrical device, according to
the first
embodiment;
[0018] FIG. 11 illustrates a flow chart for an exemplary embodiment of
a procedure of
authenticating a user of the client computer, according to the first
embodiment; and
[0019] FIG. 12 illustrates a flow chart for an exemplary embodiment of
a procedure of
providing the requested information about the electrical device, according to
the first
embodiment.
[0020] For simplicity and clarity of illustration, the drawing figures
illustrate the
general manner of construction, and descriptions and details of well-known
features
and techniques may be omitted to avoid unnecessarily obscuring the invention.
Additionally, elements in the drawing figures are not necessarily drawn to
scale. For
example, the dimensions of some of the elements in the figures may be
exaggerated
relative to other elements to help improve understanding of embodiments of the
present invention. The same reference numerals in different figures denote the
same
elements.
[0021] The terms "first," "second," "third," "fourth," and the like in
the description and
in the claims, if any, are used for distinguishing between similar elements
and not
necessarily for describing a particular sequential or chronological order. It
is to be
understood that the terms so used are interchangeable under appropriate
circumstances such that the embodiments described herein are, for example,
capable
of operation in sequences other than those illustrated or otherwise described
herein.
Furthermore, the terms "include," and "have," and any variations thereof, are
intended
to cover a non-exclusive inclusion, such that a process, method, system,
article,
device, or apparatus that comprises a list of elements is not necessarily
limited to
those elements, but may include other elements not expressly listed or
inherent to
such process, method, system, article, device, or apparatus.
[0022] The terms "left," "right," "front," "back," "top," "bottom,"
"over," "under," and
the like in the description and in the claims, if any, are used for
descriptive purposes
and not necessarily for describing permanent relative positions. It is to be
understood
that the terms so used are interchangeable under appropriate circumstances
such that
3
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
the embodiments of the invention described herein are, for example, capable of
operation in other orientations than those illustrated or otherwise described
herein.
[0023] The terms "couple," "coupled," "couples," "coupling," and the
like should be
broadly understood and refer to connecting two or more elements or signals,
electrically, mechanically and/or otherwise. Two or more electrical elements
may be
electrically coupled but not be mechanically or otherwise coupled; two or more
mechanical elements may be mechanically coupled, but not be electrically or
otherwise coupled; two or more electrical elements may be mechanically
coupled, but
not be electrically or otherwise coupled. Coupling may be for any length of
time, e.g.,
permanent or semi-permanent or only for an instant.
[0024] "Electrical coupling" and the like should be broadly understood
and include
coupling involving any electrical signal, whether a power signal, a data
signal, and/or
other types or combinations of electrical signals. "Mechanical coupling" and
the like
should be broadly understood and include mechanical coupling of all types.
[0025] The absence of the word "removably," "removable," and the like
near the word
"coupled" and the like does not mean that the coupling, etc. in question is or
is not
removable.
DETAILED DESCRIPTION OF EXAMPLES OF EMBODIMENTS
[0026] Some embodiments concern a method of distributing information
regarding one
or more electrical devices using a first server. Each of the one or more
electrical
devices can have unique identification information, an internal IP address,
and an
external IP address. The method can include: receiving in the first server a
first
request to register a first electrical device of the one or more electrical
devices, the
first request to register comprises the unique identification information, the
internal IP
address, and the external IP address of the first electrical device of the one
or more
electrical devices;
storing in the first server the unique identification information,
the internal IP address, and the external IP address of the first electrical
device of the
one or more electrical devices using the first server; receiving in the first
server from
a first client computer a first request for information regarding the first
electrical
device of the one or more electrical devices; using the first server to
determine the
external IP address of the first electrical device of the one or more
electrical devices;
redirecting the first request for the information to a first gateway device if
an external
IP address of the first client computer is identical to the external IP
address of the first
4
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
electrical device of the one or more electrical devices; and returning the
external IP
address of the first electrical device of the one or more electrical devices
if the
external IP address of the first client computer is different from the
external IP
address of the first electrical device of the one or more electrical devices
[0027] Various embodiments can concern a method of disseminating
information
regarding at least one electrical device using a registration server. The at
least one
electrical device has unique identification information, an internal IP
address, and an
external IP address wherein the external IP address is an IP address of a
first gateway
device for a first local network. The method can include: receiving in the
registration
server a first request to register the at least one electrical device, the
first request to
register includes the unique identification information, the internal IP
address, and the
external IP address of the at least one electrical device; storing in the
registration
server the unique identification information, the internal IP address, and the
external
IP address of the at least one electrical device using the registration
server; receiving
in the registration server from a first client computer a first request for
information
regarding the at least one electrical device, the first request includes the
external IP
address of the first client computer and the unique identification information
of the at
least one electrical device; providing to the first client computer the
external IP
address of the at least one electrical device if the external IP address of
the first client
computer is different from the external IP address of the at least one
electrical device;
and providing to the first client computer the internal IP address of the at
least one
electrical device if the external IP address of the first client computer is
identical to
the external IP address of the at least one electrical device. The
registration server is
not part of the first local network. In some examples, the at least one
electrical device
and the first gateway device are part of the first local network.
[0028] Many embodiments can concern a method of determining
information regarding
an electrical device. The electrical device having unique identification
information,
an internal IP address, and an external IP address. The method can include:
requesting the internal IP address of the electrical device; receiving the
internal IP
address of the electrical device; setting-up the electrical device, wherein
setting-up the
electrical device can include communicating to a first server the unique
identification
information, the internal IP address and the external IP address of the
electrical
device; using the client computer to query the first server for at least one
of the
internal IP address or the external IP address of the electrical device; using
the client
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
computer to receive at least one of the internal IP address of the electrical
device or
the external IP address of the electrical device; using the client computer to
access the
electrical device using at least one of the internal IP address of the
electrical device or
the external IP address of the electrical device. The electrical device can be
part of a
different local network than the first server.
[0029] Yet other embodiments can concern a registration server
configured to provide
information regarding two or more electrical devices. Each of the two or more
electrical devices has unique identification information, an internal IP
address, and an
external IP address. The registration server can include: (a) a registration
module
configured to receive at least two requests to register each of the two or
more
electrical devices, each of the at least two requests to register includes the
unique
identification information, the internal IP address, and the external IP
address of the
two or more electrical devices; (b) a storage module configured to store the
unique
identification information, the internal IP address, and the external IP
address of each
of the two or more electrical devices; (c) a request module configured to
receive one
or more requests for information regarding the two or more electrical devices
from
one or more client computers and further configured to determine an external
IP
address of the one or more client computers making the one or more requests
for the
information; and (d) a return module. A first request of the one or more
requests for
the information is a request for the information about a first electrical
device of the
two or more electrical devices is by a first client computer of the one or
more client
computers. The return module can be configured to redirect the first request
of the
one or more requests for the information by the first client computer of the
one or
more client computer to a first gateway device if the external IP address of
the first
client computer of the one or more client computers is identical to the
external IP
address of the first electrical device of the two or more electrical devices.
The return
module can be further configured return the external IP address of the first
electrical
device of the two or more electrical devices if the external IP address of the
first client
computer of the one or more client computers is different from the external IP
address
of the first electrical device of the two or more electrical devices.
[0030] Turning to the drawings, FIG. 1 illustrates a block diagram of
a system 100
configured to provide information regarding at least one electrical device
110,
according to a first embodiment. System 100 is merely exemplary and is not
limited
6
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
to the embodiments presented herein. System 100 can be employed in many
different
embodiments or examples not specifically depicted or described herein.
[0031] In some embodiments, system 100 can include: (a) at least one
electrical device
110; (b) at least one of an internal client computer 130 or an external client
computer
131; (c) at least one gateway device 150; (d) at least one lookup server 170;
and (e) at
least one registration server 190. In some examples, lookup server 170 and
registration server 190 can be combined into a single dual purpose server and
can be
called a lookup server, a registration server, or the like. In various
examples, internal
client computer 130, electrical device 110, and gateway device 150 are part of
a local
network 101. Lookup server 170, registration server 190, and external client
computer 131 are not part of local network 101.
[0032] Not to be taken in a limiting sense, a simple example of a
method of using
system 100 to provide information about electrical device 110 includes
electrical
device 110 being assigned a new dynamically generated internal IP address by
gateway device 150 (or another networking device). Electrical device 110 then
registers unique identification information, the assigned internal IP address,
and the
external IP address of electrical device 110 (e.g., the IP address of gateway
device
150) with registration server 190. In some examples, electrical device 100
registers
the assigned external IP address of electrical device 110 without knowing the
assigned
external IP address. For example, registration sever 190 can obtain the
external IP
address of electrical device 110 using source packet information contained in
the
register request.
[0033] In some examples, registration server 190 can be a trusted
DHCP-DNS server (a
type of domain name system server that allows an electrical device to register
both the
internal and the external IP addresses of the electrical device). In many
examples,
registration server 190 is available and residing in a network (i.e., not
local network
101) that is visible by any client (e.g., internal client computer 130 and
external client
computer 131) that needs to access registration server 190 (e.g., the public
internet).
Electrical device 110, as part of the registration process with registration
server 190,
also can also provide other unique identification information such as
authentication
information (e.g., a username and a password) for electrical device 110,
service or
type of service it provides, model number, MAC address, etc. Electrical device
110
can re-register this information as needed (e.g., when the internal IP address
of
electrical device 110 is updated dynamically).
7
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0034] After the registration process is complete, registration
server 190 can receive a
request for information regarding electrical device 110 from a requesting
client
computer (e.g., internal client computer 130 or external client computer 131).
The
request for information can include the MAC address of electrical device 110
(or any
other unique identification information). Registration server 190 can examine
the
MAC address (or any other unique identification information) and apparent
external
source IP address of a requesting client computer to determine what
information to
provide in response to the request for information. In some examples, the
requesting
client computer is also required to provide authentication information (e.g.,
username/password) for security purposes.
[0035] In some examples, if: (a) the apparent external source IP
address of the
requesting client computer matches the external IP address of electrical
device 110,
and (b) the unique identification information and the authentication
information
provided by the requesting client computer matches with the unique
identification
information and the authentication information of electrical device 110,
registration
server 190 determines that the client computer is requesting access to the
information
about electrical device 110 from within the same network (i.e., local network
101) as
electrical device 110. In this case, registration server 190 returns the most
recently
registered internal IP address for electrical device 110.
[0036] In other examples, registration server 190 does not provide
the most recently
registered internal IP address of electrical device 110. Rather, registration
server 190
redirects the request for information to gateway device 150, and gateway
device 150
can provide the internal IP address of electrical device 110. By providing the
internal
IP address to the requesting client computer, the requesting client computer
(e.g.,
internal client computer 130) is able to directly access the services provided
by
electrical device 110.
[0037] If the apparent external IP address of the requesting client
computer is different
than the external IP address of electrical device 110 but the unique
identification
information and authentication information provide by the client computer
matches
the stored information, registration server 190 can return the most recently
registered
external IP address of electrical device 110 to the requesting client
computer.
[0038] FIG. 2 illustrates a block diagram of electrical device 110,
according to the first
embodiment. Electrical device 110 is merely exemplary and is not limited to
the
8
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
embodiments presented herein. Electrical device 110 can be employed in many
different embodiments or examples not specifically depicted or described
herein.
[0039] In some examples, electrical device 110 can include: (a) a
system bus 211; (b) a
controller 212 coupled to system bus 211; (c) at least one network connector
213; (d)
at least one network adapter 214 coupled to system bus 211 and network
connector
213; (e) storage module 216 coupled to system bus 211; (f) one or more
application
specific devices 217; (g) an operations module 221; (h) a set-up module 222;
and (i) a
registration module 223. In these examples, electrical device 110 does not
have a
visual display or a visual user interface. In the same or different examples,
the
components of electrical device 110 can be coupled together without using
system bus
211. In various embodiments, the architecture of controller 212 can be
compliant
with any of a variety of commercially distributed architectures.
[0040] Network connector 213 can be any type of network connector such
as, for
example, an ethernet connector, a universal serial bus (USB) connector, a
serial port
connector, a parallel port connector, and the like. In other examples, network
connector 213 can include a wireless network adapter and an antenna. In many
examples, electrical device 110 can be coupled to gateway device 150 (FIG. 1)
using
network connector 213.
[0041] Application specific devices 217 can include any other devices
and/or adapters
that are required for electrical device 110 to perform its designed functions.
For
example, electrical device 110 can be a motion detection device, and
application
specific devices 217 can include the sensors needed to detect motion. In many
examples, application specific devices 217 do not include any devices that
have visual
display capabilities (e.g., a monitor or a liquid crystal display (LCD)). In
many
examples, adding a visual display device is too costly or unnecessary for the
primary
function of electrical device 110. Accordingly, when electrical device is
configured
using DHCP or another protocol, no mechanism exists to provide the
configuration
information (e.g., an internal or external IP address of electrical device
110) to a user.
[0042] Storage module 216 can include memory, both read only memory
(ROM) and
random access memory (RAM). Non-volatile portions of storage module 216 or the
ROM can be encoded with a boot code sequence suitable for restoring electrical
device 110 (FIG. 1) to a functional state after a system reset. Storage module
216 can
also include a hard disk and/or other types of storage devices.
9
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0043]
Operations modules 221 can be configured to operate and provide the designed
functionality of electrical device 110. Set-up module 222 can be configured to
handle
the set-up and configuration of electrical device 110. Registration module 223
can be
configured to communicate with lookup server 170 (FIG. 1) and/or registration
server
190 (FIG. 1) to register the internal and external IP addresses and other
information
about electrical device 110.
[0044] In some examples, storage module 216 can store operations module
221, set-
up module 222, and/or registration module 223, and these modules can be
performed
using controller 212. When electrical device 110 of FIGs. 1 and 2 is running,
program instructions stored in storage module 216 can be executed by
controller 212.
A portion of the program instructions stored in storage module 216 can be
suitable for
carrying out at least portions of the methods of transmitting data between
other
elements of system 100 (FIG. 1), as described hereinafter with respect to
FIGs. 8-12.
In same or different examples, at least portions of the methods of
transmitting data
between the other elements, as described hereinafter with respect to FIGs. 8-
12, can
be implemented by circuitry in electrical device 110.
[0045] FIG. 3 illustrates a rear view of gateway device 150 for
broadcasting data,
according to the first embodiment. Gateway device 150 is merely exemplary and
is
not limited to the embodiments presented herein. Gateway device 150 can be
employed in many different embodiments or examples not specifically depicted
or
described herein. In the same or different embodiments, gateway device 150 can
be
considered a computer component for communicating data between a network
(e.g.,
the internet) and internal client computer 130 (FIG. 1) and electrical device
110 (FIG.
1). Gateway device 150 can be an electrical device used to connect a computer
or
electrical device to a network. For example, gateway device 150 can include
one or
more of: a router, a hub, a wireless access point, a modem-router, a VoIP
(voice over
internet protocol) modem-router, a wireless ethernet bridge, and a wireless
network
interface card (WNIC).
[0046] Gateway device 150 can include a chassis 352 containing one or
more circuit
boards (not shown), one or more network connectors 351, an input device 354,
and
one or more antennas 355. Antennas 355 can be used to transfer or transmit
information using electromagnetic waves (i.e., a wireless network). Network
connectors 351 can be any type of network connectors such as, for example,
Ethernet
connectors, universal serial bus (USB) connectors, serial port connectors,
parallel port
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
connectors, and the like. In one example, network connectors 351 include one
ADSL
(Asymmetric Digital Subscriber Line) connector and four Ethernet ports.
[0047] A representative block diagram of an example of the elements
included in the
circuit board(s) inside chassis 352 is shown in FIG. 4. In the embodiment
shown in
FIG. 4, a controller 456 is coupled to a system bus 457. In various
embodiments, the
architecture of controller 456 can be compliant with any of a variety of
commercially
distributed architectures. In other examples, gateway device 150 (FIG. 3) does
not
include system bus 457, and the components of gateway device 150 can
communicate
with system bus 457.
[0048] In the embodiment of FIG. 4, system bus 457 is also coupled to
storage
module 458 that can include read only memory (ROM), random access memory
(RAM), a hard drive and/or other storage devices. Also, various I/0
(input/output)
devices such as one or more network adapters 459 and 460, an input adapter
461, and
other I/0 devices and adapters 462 can be coupled to system bus 457. Network
adapter 459 can be coupled to antenna(s) 355, and network adapter 460 can be
coupled to network connectors 351. Network connectors 351 and antenna(s) 355,
though network adapters 460 and 459, respectively, can be coupled to
controller 212
(FIG. 2) directly or through system bus 457. In other embodiments, a single
network
adapter can be used to control all of these I/0 devices.
[0049] In some examples, network adapter 459 can include transmitter
463 and
receiver 464. Transmitter 463 can be a radio frequency or other wireless
transmitter.
Receiver 464 can be a radio frequency or other wireless receiver. In numerous
embodiments, transmitter 463 and receiver 464 can include or be radios.
[0050] When gateway device 150 in FIGs. 1 and 3-4 is running, program
instructions
stored in storage module 458 are executed by controller 456. A portion of the
program instructions stored in storage module 458 can be suitable for carrying
out at
least portions of the methods of transmitting data between other elements of
system
100 (FIG. 1), as described hereinafter with respect to FIGs. 8-12. In same or
different
examples, at least portions of the methods of transmitting data between the
other
elements, as described hereinafter with respect to FIGs. 8-12, can be
implemented by
circuitry in gateway device 150.
[0051] FIG. 5 illustrates a block diagram of internal client computer
130, according to
the first embodiment. Internal client computer 130 is merely exemplary and is
not
limited to the embodiments presented herein. Internal client computer 130 can
be
11
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
employed in many different embodiments or examples not specifically depicted
or
described herein. Internal client computer 130 includes a chassis 535
containing one
or more circuit boards (not shown), a USB (universal serial bus) port 542, a
Compact
Disc Read-Only Memory (CD-ROM) and/or Digital Video Disc (DVD) drive 532,
and a hard drive 534.
[0052] A representative block diagram of the elements included on the
circuit boards
inside chassis 535 is shown in FIG. 6. A controller 640 in FIG. 6 is coupled
to a
system bus 644 in FIG. 6. In various embodiments, the architecture of
controller 640
can be compliant with any of a variety of commercially distributed
architecture
families.
[0053] System bus 644 also is coupled to memory 638 that includes both
read only
memory (ROM) and random access memory (RAM). Non-volatile portions of
memory 638 or the ROM can be encoded with a boot code sequence suitable for
restoring internal client computer 130 (FIG. 1) to a functional state after a
system
reset. In addition, memory 638 can include microcode such as a Basic Input-
Output
System (BIOS).
[0054] In the depicted embodiment of FIGs. 5-6, various I/0 devices
such as a disk
controller 634, a graphics adapter 649, a video controller 648, a keyboard
adapter 643,
a mouse adapter 647, network adapter 646, and other I/0 devices and adapters
645
can be coupled to system bus 644. Keyboard adapter 643 and mouse adapter 647
are
coupled to keyboard 536 (FIGs. 5 and 6) and mouse 537 (FIGs. 5 and 6),
respectively.
While graphics adapter 649 and video controller 648 are indicated as distinct
units in
FIG. 6, video controller 648 can be integrated into graphics adapter 649, or
vice versa
in other embodiments. Video controller 648 is suitable for refreshing monitor
538
(FIGs. 5 and 6) to display images in monitor 538 (FIG. 5 and 6) of internal
client
computer 130. Disk controller 634 can control hard drive 534 (FIGs. 5 and 6),
CD-
ROM or DVD drive 532 (FIGs. 5 and 6), and USB port 542 (FIGs. 5 and 6). In
other
embodiments, distinct units can be used to control each of these devices
separately.
[0055] Network adapters 646 can be coupled to one or more antennas 631.
In some
embodiments, network adapters 646 are part of a WNIC (wireless network
interface
controller) card 629 plugged or coupled to an expansion port (not shown) in
internal
client computer 130 (FIG. 1). In other embodiments, WNIC card 629 is a
wireless
network card built into internal client computer 130 (FIG. 1). A wireless
network
adapter can be built into internal client computer 130 by having wireless
ethernet
12
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
capabilities integrated into the motherboard chipset (not shown), or
implemented via a
dedicated wireless ethernet chip (not shown), connected through the PCI
(peripheral
component interconnector) or a PCI express bus. In some examples, each of
network
adapters 646 can include a transmitter 633 and receiver 635. Transmitter 633
can be a
radio frequency or other wireless transmitter. Receiver 635 can be a radio
frequency
or other wireless receiver. In numerous embodiments, transmitter 633 and
receiver
635 can include or be radios. In other embodiments, network adapter 646 can be
a
wired network adapter.
[0056] When internal client computer 130 in FIG. 1 and 5-6 is running,
program
instructions stored on a USB drive coupled to USB port 542, on a CD-ROM or DVD
in CD-ROM and/or DVD drive 532, on hard drive 534, or in memory 638 (FIG. 6)
are
executed by controller 640 (FIG. 6). A portion of the program instructions
stored in
these devices can be suitable for carrying out at least portions of the
methods of
transmitting data between a network (e.g., the internet) and internal client
computer
130 and electrical device 110, as described hereinafter with respect to FIGs.
5-8. In
same or different examples, at least portions of the methods of transmitting
data
between a network and internal client computer 130 and electrical device 110,
as
described hereinafter with respect to FIGs. 5-8, can be implemented by
circuitry in
internal client computer 130.
[0057] In various embodiments, external client computer 131 can be
similar to or the
same as internal client computer 130.
[0058] FIG. 7 illustrates a block diagram of an exemplary example of
registration
server 190, according to the first embodiment. Registration server 190 is
merely
exemplary and is not limited to the embodiments presented herein. Registration
server 190 can be employed in many different embodiments or examples not
specifically depicted or described herein.
[0059] Registration server 190 can perform two main functions in some
examples. The
first function is to receive registration information provided by electrical
device 110
(FIG. 1). When this information is received, registration server 190 stores
the
external IP address (or source IP address) of the requesting device (i.e.,
electrical
device 110, where the external IP address of electrical device 110 is the
external IP
address of gateway device 150) provided by electrical device 110 and/or
gateway
device 150, as well as the internal IP address of the same requesting device
provided
by electrical device 110 and/or gateway device 150, and any other uniquely
13
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
identifying information contained within the registration information. In some
examples, electrical device 110 can provide its external IP address. In other
examples, registration server 190 can determine the external IP address of
electrical
device 110 from header information of the TCP/IP packets from electrical
device 110.
[0060] The second function of registration server 190 is to serve as
a type of DNS
server. Traditional DNS servers merely provide a stored external IP address as
a
result of a look-up request with no other input. Registration server 190, on
the other
hand, receives a MAC address (or any other unique identification information)
from
the requesting client computer (e.g., internal client computer 130 and/or
external
client computer 131) and can examine the MAC address (or any other unique
identification information) and the apparent external source IP address of the
requesting client computer. This apparent external source IP address of the
requesting
client computer is used to determine the information about a registered
electrical
device (e.g., electrical device 110) to return to the requesting computer. In
some
examples, the requesting client computer is also required to provide
authentication
information (e.g., a username and a password) for security purposes.
[0061] This approach can use external public DNS server mechanisms
and can add the
additional functionality of being able to register two IP addresses to a
single DNS
hostname entry. Registration server 190 can be configured to determine the
proper IP
address to return in response to a query.
[0062] Other systems and methods to return dynamically assigned IP
addresses can
introduce a second layer DNS server within a local network to allow discovery
of
dynamically assigned IP addresses. Using these other methods, in order to
access a
particular electrical device, the external client (e.g., a device outside the
local
network) needs to look up the local network address first, and then query the
internal
lookup server to determine the internal IP address of the specific electrical
device. In
contrast, the system and device described herein allows each electrical device
within
the local network to register itself (or allows for a third device like a
gateway device
to register the electrical device) to an external lookup server. Accordingly,
the
systems and methods described herein allow a single lookup to find the IP
address(es)
of electrical device 110.
[0063] Furthermore, in these other systems and methods that use a
second layer DNS
server, all of the nodes (i.e., internal client computers, electrical devices,
etc.) inside
the network have to point their primary DNS server records to the internal DNS
server
14
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
of the local network for the systems or methods to work. If that internal DNS
server
disappeared for whatever reason (e.g., crashed, turned off, etc.), all of the
internal
nodes on the local network would also fail because these other devices would
lack the
ability to resolve domain names. In contrast, the systems and methods
described
herein do not require reworking the internal configuration of the local
network or
relying on a public system that is more robust.
[0064] Referring again to FIG. 7, in many examples, registration
server 190 (i.e., a
serving device) can be configured to provide information regarding one or more
electrical devices (e.g., an internal IP address, and/or an external IP
address).
Registration server 190 can include: (a) at least one input device 754; (b) at
least one
input adapter 761; (c) at least one network adapter 760; (d) at least one
network
connector 751; (e) at least one controller 756; (f) other I/0 devices and
adapters 762;
(g) a storage module 758; (h) a security module 771 configured to run on
controller
756; (i) a registration module 772 configured to run on controller 756; (j) a
request
module 773 configured to run on controller 756; and (k) a return module 774
configured to run on controller 756.
[0065] Security module 771 can be configured to determine if
authentication
information is correct. In various embodiments, security module 771 can
determine if
the authentication information provided by the client computer matches the
stored
authentication information for electrical device 110. For example, security
module
771 can authenticate the user based on the username and the password. That is,
security module 771 can authenticate the user if the username and the password
of the
authentication information provided by the client computer is the same as the
username and the password for electrical device 110 as stored by the
registration
server
[0066] Registration module 772 can be configured to receive at least
one request to
register the one or more electrical devices (e.g., electrical device 110). In
some
examples, the request to register an electrical device can include at least
one request
to register the MAC address (or any other unique identification information),
the
internal IP address, and the external IP address of the electrical device.
Storage
module 758 can be configured to store the MAC address (or any other unique
identification information), the internal IP address, and the external IP
address of the
one or more electrical devices. In the same or different examples, the request
to
register can also include authentication information.
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0067] Request module 773 can be configured to receive one or more
requests for
information regarding the one or more electrical devices from one or more
client
computers. Request module 773 can be further configured to determine the
external
IP address of the requesting client computer. For example, request module 773
can
determine the external IP address of the requesting client computer by
examining the
headers of the TCP/IP packets from the requesting client computer.
[0068] Return module 774 can be configured return the external IP
address of electrical
device 110 if the external IP address of the client computer (e.g., external
client
computer 131) is different than the external IP address of electrical device
110.
Furthermore, return module 774 can be configured to redirect a request for
information about electrical device 110 to gateway device 150 if an external
IP
address of the first client computer (i.e., internal client computer 130) is
the same as
the external IP address of electrical device 110. In other examples, return
module 774
can return the information about electrical device 110 regardless of the
external IP
address of the requesting client computer.
[0069] "Server," as used herein, can refer to a single computer, a
single server, or a
cluster or collection of servers. Typically, a cluster or collection of
servers can be
used when the demands by client computers (e.g., electrical device 110,
internal client
computer 130, and/or external client computer 131) are beyond the reasonable
capability of a single server or computer. In many embodiments, the servers in
the
cluster or collection of servers are interchangeable from the perspective of
the client
computers and can be located at the same or different places. Furthermore, the
server
can have internal and/or external memory.
[0070] If registration server 190 is a single server, it can include
registration module
772, request module 773, and return module 774. In other examples, a first
server can
include a first portion of these modules, and one or more second servers can
include a
second, possibly overlapping, portion of these modules. In these examples,
registration server 190 can comprise the combination of the first server and
the one or
more second servers.
[0071] In some examples, storage module 758 can store the information
about the one
or more electrical devices. In some examples, storage module can store a
structured
collection of records or data, for instance. For example, the information
about the one
or more electrical devices can be stored as an XML (Extensible Markup
Language)
database, MySQL database, or an Oracle database. In the same or different
16
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
embodiments, the information about the one or more electrical devices can be
stored
in a searchable group of individual data files.
[0072] Turning to another embodiment, FIG. 8 illustrates a flow chart
for an exemplary
embodiment of a method 800 of distributing information regarding one or more
electrical devices using a first server. Method 800 can also be considered a
method of
determining information regarding at least one electrical device. Method 800
is
merely exemplary and is not limited to the embodiments presented herein.
Method
800 can be employed in many different embodiments or examples not specifically
depicted or described herein. In some embodiments, the activities, the
procedures,
and/or the processes of method 800 can be performed in the order presented. In
other
embodiments, the activities, the procedures, and/or the processes of method
800 can
be performed in any other suitable order. In still other embodiments, one or
more of
the activities, the procedures, and/or the processes in method 800 can be
combined or
skipped.
[0073]
Referring to FIG. 8, method 800 includes an activity 810 of providing
authentication information for an electrical device.
In some examples, the
authentication information is provided to a user of the electrical device. In
some
examples, the electrical device can be similar to or the same as electrical
device 110
of FIG. 1. The authentication information can include at least one of a
username or a
password.
[0074] In some embodiments, a user of an electrical device can receive
the
authentication information with the electrical device. For example, the
authentication
information can be included with the packaging of the electrical device. In
another
example, a user of the electrical device can request the information (e.g.,
request the
information over a website of the manufacturer or distributor of the
electrical device)
and the manufacturer or distributor, for example, can provide the
authentication
information. In still another example, the electrical device can be used to
create at
least one of the username or the password. In yet another example, the
electrical
device can provide the predetermined authentication information to the user.
[0075] Method 800 in FIG. 8 continues with an activity 815 of setting-
up the electrical
device. In various embodiments, setting-up the electrical device can include
coupling
the electrical device to a gateway device and performing any necessary set-up
routines
that are specific to the electrical device. After being coupled to the gateway
device,
the electrical device can request from the gateway device (or another
networking
17
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
device) an assignment of an internal IP address. For example, the assigning of
an
internal IP address can be performed using DHCP. In some examples, a set-up
module (e.g., set-up module 222 (FIG. 2)) can be used to help facilitate the
set-up of
the electrical device.
[0076] After the set-up process is complete, in some examples, the
electrical device will
have been assigned an internal IP address, but a user of the electrical device
will lack
an easy method to determine the new IP address if the electrical device lacks
a visual
user interface. The rest of method 800 provides an easy method for a user to
determine the new IP address of the electrical device without having to
navigate
proprietary menus or screens in a computer, the electrical device, or the
gateway
device.
[0077] Subsequently, method 800 of FIG. 8 includes an activity 820 of
registering the
electrical device. In some example, information about the electrical device
can be
registered with a registration server. For example, the electrical device and
the
registration server can be similar to or the same as electrical device 110 and
registration server 190 of FIG. 1. FIG. 9 illustrates a flow chart for an
exemplary
embodiment of activity 820 of registering the electrical device, according to
the first
embodiment.
[0078] Referring to FIG. 9, activity 820 includes a procedure 905 of
communicating the
request to register the electrical device to a registration server. In many
examples, the
electrical device can communicate the request to register the electrical
device to the
registration server via the Internet or another communications network. In
some
examples, the electrical device can include its MAC address, its internal IP
address,
its external IP address, and/or other unique identification information as
part of the
request for registration. In some examples, the electrical device
automatically
communicates this information to the registration server in real time. In the
same or
different examples, the request for registration can also include the
authentication
information associated with the electrical device.
[0079] Activity 820 in FIG. 9 continues with a procedure 915 of
receiving the request
to register the electrical device. In some examples, the registration server
can receive
the request to register from the electrical device. The received request for
registration
can include the MAC address, the internal IP address, the external IP address,
and/or
other unique identification information of the first electrical device. In
other
examples, the request to register includes the MAC address and the internal IP
18
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
address, but not the external IP address. In these examples, the registration
server can
determine the external IP address by examining the header or other information
transferred as part of the standard TCP/IP packet. In the same or different
examples,
the request for registration can also include the authentication information
associated
with the electrical device. In some examples, a registration module (e.g.,
registration
module 772 of FIG. 7) can handle at least part of procedure 915.
[0080] Subsequently, activity 820 of FIG. 9 includes a procedure 925
of processing the
request to register the electrical device. In some embodiments, procedure 925
can
include storing the MAC address, the internal IP address, the external IP
address,
and/or other unique identification information of the electrical device. In
the same or
different examples, the registration server can also store the authentication
information associated with the electrical device. For example, the
registration server
can store the registration information of the electrical device in a storage
module. In
various examples, the storage module can be similar to or the same as storage
module
758 of FIG. 7. In some examples, a registration module (e.g., registration
module 772
of FIG. 7) can handle at least part of procedure 925. After procedure 925,
activity
820 is complete.
[0081] In various embodiments, activity 820 can repeated to register
different electrical
devices. For example, activity 820 can be performed to register a first
electrical
device and repeated one or more second times to register one or more second
electrical devices.
[0082] Referring again to FIG. 8, method 800 of FIG. 8 continues with
an activity 825
of determining the address of registration server. In some examples, a client
computer (e.g., internal client computer 130 or external client computer 131
of FIG.
1) can desire to request information about an electrical device registered
with the
registration server, but the client computer needs the IP address of the
registration
server. In activity 825, the client computer can determine the IP address of
the
registration server by sending a request to a lookup server for the IP address
of the
registration server. The lookup server can return the IP address of the
registration
server to the client computer. In various examples, the client computer can
send a
DNS (domain name server) lookup request to the lookup server to retrieve the
IP
address of the registration server. In many embodiments, the lookup server can
be
similar or identical to lookup server 170 of FIG. 1.
19
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0083] After determining the IP address of the registration server,
method 800 in FIG. 8
continues with an activity 830 of communicating a request for information
about the
electrical device. In many embodiments, a client computer (e.g., internal
client
computer 130 or external client computer 131 of FIG. 1) can query the
registration
server for at least one of the internal IP address or the external IP address
of the
electrical device. In some examples, the client computer can transmit the
request for
information about the electrical device to the registration server over the
Internet
and/or one or more other networks. In some examples, the request for
information
can include the MAC address or other unique identification information of the
electrical device.
[0084] Subsequently, method 800 of FIG. 8 includes an activity 835 of
processing a
request for information about the electrical device. FIG. 10 illustrates a
flow chart for
an exemplary embodiment of activity 835 of processing a request for
information
about the electrical device, according to the first embodiment.
[0085] Referring to FIG. 10, activity 835 includes a procedure 1060
of determining if
the electrical device is registered. In some examples, the registration server
can
determine whether the electrical device is registered by searching the stored
information about registered electrical devices to determine if the specific
electrical
device is registered with the registration server. In various embodiments, the
request
module of the registration server can determine if any information exists in
the
storage module for the MAC address or other unique identification information
of the
electrical device. In some examples, a request module (e.g., request module
773 of
FIG. 7) can perform at least part of procedure 1060. If the electrical device
is not
registered with the registration server, the next procedure in activity 835 in
FIG. 10 is
a procedure 1061. If the electrical device is registered with the registration
server, the
next procedure in activity 835 in FIG. 10 is a procedure 1062.
[0086] Procedure 1061 communicates to the client computer that no
such electrical
device is registered. If the request module determines that the electrical
device for
which information was requested is not registered with the registration
server, the
return module can communicate to the client computer that no information is
available about the specific electrical device. In some examples, a return
module
(e.g., return module 774 of FIG. 7) can perform at least part of procedure
1061. If no
such electrical device is registered after procedure 1061, activity 835 (FIGs.
8 and 10)
and method 800 (FIG. 8) are complete.
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
[0087] Procedure 1062 authenticates the client computer. In some
examples, to provide
enhanced security, authentication of the client computer can be required
before
information about the electrical device is provided to the user of the client
computer.
FIG. 11 illustrates a flow chart for an exemplary embodiment of procedure 1062
of
authenticating the client computer, according to the first embodiment. In some
examples, a security module (e.g., security module 771 of FIG. 7) can perform
at least
part of procedure 1062.
[0088] Referring to FIG. 11, procedure 1062 includes a process 1171
of requesting
authentication information from the client computer. In some examples, the
requested
authentication information can include at least one of a username or a
password.
[0089] Next, procedure 1062 of FIG. 11 includes a process 1172 of
communicating
authentication information to the first server. In some examples, the client
computer
can provide at least one of a username or a password to the registration
server.
[0090] Procedure 1062 in FIG. 11 continues with a process 1173 of
receiving
authentication information of a user of the client computer. In some examples,
the
requesting module or the return module of the registration server can receive
the
authentication information from the client computer.
[0091] Subsequently, procedure 1062 of FIG. 11 includes a process
1174 of
determining if authentication information is correct. In various embodiments,
the
security module of the registration server can determine if the authentication
information provided by the client computer matches the stored authentication
information for the electrical device. For example, the security module can
authenticate the user based on the username and the password. That is, the
registration server can authenticate the user if the username and the password
of the
authentication information provided by the client computer is the same as the
username and the password for the electrical device as stored by the
registration
server. If the authentication information is correct, procedure 1062 is
complete and
the next procedure is procedure 1063 of FIG. 10. If the authentication
information is
not correct, the next process in procedure 1062 of FIG. 11 is process 1175.
[0092] Process 1175 informs the user that the authentication
information is not correct.
In some examples, the registration server can communicate to the client
computer that
the authentication information is not correct and that the registration server
cannot
process the request for information about the electrical device. In some
embodiments,
the registration server can give the user one or more additional attempts to
submit the
21
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
correct authentication information before rejecting the request. After process
1175,
procedure 1062, activity 835 (FIGs. 8 and 10), and method 800 (FIG. 8) are
complete.
[0093] In other embodiments, the registration server does not require
authentication of
the user of the client computer before providing the information about the
electrical
device. In these examples, procedure 1062 of FIG. 10 can be skipped.
[0094] Referring again to FIG. 10, activity 835 includes a procedure
1063 of providing
the requested information about the electrical device. FIG. 12 illustrates a
flow chart
for an exemplary embodiment of procedure 1063 of providing the requested
information about the electrical device, according to the first embodiment. In
some
examples, a return module (e.g., return module 774 of FIG. 7) can perform at
least
part of procedure 1063.
[0095] Referring to FIG. 12, procedure 1063 includes a process 1271
of determining if
the client computer and the electrical device are in the same local network.
Depending on whether the client computer and the electrical device are in the
same
internal network, different information may be provided to the client computer
and
may be provided by a different entity (e.g., registration server 190 or
gateway device
150). In some examples, the external IP address of the client computer and the
electrical device can be compared to determine if the client computer and the
electrical device are in the same local network. In other embodiments, other
mechanism can be used to determine if the client computer and the electrical
device
are in the same local network.
[0096] If the external IP addresses are the same, the registration
server can conclude
that the client computer and the electrical device are in the same local
network, and
the next process in procedure 1063 of FIG. 12 is process 1273. If the external
IP
addresses of the electrical device and the client computer are different, the
next
process in procedure 1063 of FIG. 12 is process 1272.
[0097] Process 1272 provides the registration information. In some
examples, if the
client computer and the electrical device are not in the same local network,
the
registration server can return the external IP address of the electrical
device (e.g.,
electrical device 110) to the client computer (e.g., external client computer
131).
After providing the registration information in process 1272, procedure 1063
and
activity 835 (FIGs. 8 and 10) are complete.
[0098] Process 1273 redirects the request for the information about
the electrical device
to the gateway device. In many examples, the registration server can redirect
a
22
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
request for the information about the electrical device to a gateway device if
an
external IP address of the client computer is the same as the external IP
address of the
electrical device. The gateway device can then provide the internal IP
address. In
other embodiments, the registration server can provide the information and
process
1273 is unnecessary.
[0099] Subsequently, procedure 1063 of FIG. 12 includes a process
1274 of providing
the registration information. In some examples, if the client computer and the
electrical device are in the same internal network, the gateway device can
return the
internal IP address of the electrical device to the client computer (e.g.,
internal client
computer 130). After process 1274, procedure 1063 and activity 835 (FIGs. 8
and 10)
are complete.
[00100] Referring back to FIG. 8, method 800 continues with an
activity 840 of
accessing the electrical device from a client computer. In some examples, the
client
computer can use at least one of the internal IP address or the external IP
address of
the electrical device to access the electrical device.
[00101] Although the invention has been described with reference to
specific
embodiments, it will be understood by those skilled in the art that various
changes
may be made without departing from the spirit or scope of the invention.
Accordingly, the disclosure of embodiments of the invention is intended to be
illustrative of the scope of the invention and is not intended to be limiting.
It is
intended that the scope of the invention shall be limited only to the extent
required by
the appended claims. For example, activities 810, 815, 820, 825, 830, 835 and
840 of
FIG. 8, procedures 905, 915, and 925 of FIG. 9, procedures 1060, 1061, 1062,
and
1063, processes 1171, 1172, 1173, 1174, and 1175, and processes 1271, 1272,
1273,
and 1274 may be comprised of many different activities and procedures and be
performed by many different modules, in many different orders, that any
element of
FIG. 1 may be modified, and that the foregoing discussion of certain of these
embodiments does not necessarily represent a complete description of all
possible
embodiments.
[00102] All elements claimed in any particular claim are essential to
the embodiment
claimed in that particular claim. Consequently, replacement of one or more
claimed
elements constitutes reconstruction and not repair. Additionally, benefits,
other
advantages, and solutions to problems have been described with regard to
specific
embodiments. The benefits, advantages, solutions to problems, and any element
or
23
CA 02832810 2013-10-09
WO 2012/135376
PCT/US2012/030999
elements that may cause any benefit, advantage, or solution to occur or become
more
pronounced, however, are not to be construed as critical, required, or
essential
features or elements of any or all of the claims, unless such benefits,
advantages,
solutions, or elements are stated in such claim.
[00103] Moreover, embodiments and limitations disclosed herein are not
dedicated to the
public under the doctrine of dedication if the embodiments and/or limitations:
(1) are
not expressly claimed in the claims; and (2) are or are potentially
equivalents of
express elements and/or limitations in the claims under the doctrine of
equivalents.
24
