U.S. patent application number 13/534187 was filed with the patent office on 2012-10-25 for systems and methods for retrieving customer premise equipment data.
This patent application is currently assigned to AT&T Intellectual Property I, L.P.. Invention is credited to Kaiyan Chen, Baofeng Jiang, Michael Yew-Aik Lim.
Application Number | 20120271914 13/534187 |
Document ID | / |
Family ID | 39794189 |
Filed Date | 2012-10-25 |
United States Patent
Application |
20120271914 |
Kind Code |
A1 |
Jiang; Baofeng ; et
al. |
October 25, 2012 |
Systems and Methods for Retrieving Customer Premise Equipment
Data
Abstract
A method includes receiving a trigger event at a customer
premise equipment management system from a service provider system.
The trigger event includes a request for retrieval of customer
premise equipment data from at least one customer premise equipment
device. The method includes issuing, from the customer premise
equipment management system, a customer premise equipment data
request to the at least one customer premise equipment device in
response to receiving the trigger event. Each customer premise
equipment data request includes a customer premise equipment access
certificate to gain access to particular customer premise equipment
data. The method also includes receiving, at the customer premise
equipment management system, the requested customer premise
equipment data.
Inventors: |
Jiang; Baofeng; (Pleasanton,
CA) ; Chen; Kaiyan; (Pleasanton, CA) ; Lim;
Michael Yew-Aik; (Fremont, CA) |
Assignee: |
AT&T Intellectual Property I,
L.P.
Atlanta
GA
|
Family ID: |
39794189 |
Appl. No.: |
13/534187 |
Filed: |
June 27, 2012 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11729682 |
Mar 29, 2007 |
8250190 |
|
|
13534187 |
|
|
|
|
Current U.S.
Class: |
709/217 |
Current CPC
Class: |
H04M 7/0069 20130101;
H04W 76/10 20180201; H04L 65/1023 20130101; H04M 11/062 20130101;
H04L 41/0809 20130101; H04W 4/00 20130101; H04L 41/0806 20130101;
H04L 41/24 20130101; H04L 67/10 20130101; H04L 41/0866 20130101;
H04L 12/2898 20130101; H04L 12/2859 20130101; H04L 41/50
20130101 |
Class at
Publication: |
709/217 |
International
Class: |
G06F 15/16 20060101
G06F015/16 |
Claims
1. A method comprising: receiving a trigger event at a customer
premise equipment management system from a service provider system,
wherein the trigger event comprises a request for retrieval of
customer premise equipment data from at least one customer premise
equipment device; issuing, from the customer premise equipment
management system, a customer premise equipment data request to the
at least one customer premise equipment device in response to
receiving the trigger event, wherein each customer premise
equipment data request includes a customer premise equipment access
certificate to gain access to particular customer premise equipment
data; and receiving, at the customer premise equipment management
system, the customer premise equipment data.
2. The method of claim 1, wherein the customer premise equipment
data comprises one or more of local area network performance
parameters, local area network usage parameters, and local area
network performance statistics.
3. The method of claim 1, wherein the customer premise equipment
data comprises one or more of wide area network performance
parameters, wide area network performance statistics, wide area
network usage parameters, upstream wide area network usage,
downstream wide area network usage, upstream wide area network
usage statistics, and downstream wide area network usage
statistics.
4. The method of claim 1, wherein the customer premise equipment
data comprises a bulk download of customer premise equipment data
from multiple premise equipment devices.
5. The method of claim 1, wherein a particular customer premise
equipment access certificate for a particular customer premise
equipment device is retrieved from a customer premise equipment
access database.
6. The method of claim 1, further comprising storing a portion of
the customer premise equipment data corresponding to a particular
customer premise equipment device in a customer premise equipment
data database as data associated with the particular customer
premise equipment device.
7. The method of claim 1, wherein the at least one customer premise
equipment device comprises two or more customer premise equipment
devices, and wherein issuing the customer premise equipment data
request comprises communications via parallel communication
channels to each of the two or more customer premise equipment
devices.
8. The method of claim 1, wherein a first particular customer
premise equipment device of the at least one customer premise
equipment device comprises at least one of a digital subscriber
line modem, a set-top box device, or a residential gateway.
9. The method of claim 1, wherein the trigger event comprises one
of multiple periodic requests for customer premise equipment
data.
10. A non-transitory computer readable medium comprising
instructions executable by a processor to: receive a trigger event
at a customer premise equipment management system from a service
provider system, wherein the trigger event comprises a request for
retrieval of customer premise equipment data from a first customer
premise equipment device; issue a customer premise equipment data
request to the first customer premise equipment device in response
to receipt of the trigger event, wherein the customer premise data
request includes a customer premise equipment access certificate to
gain access to the customer premise equipment data from the first
customer premise equipment device; and receive the customer premise
equipment data in response to the customer premise equipment data
request.
11. The non-transitory computer readable medium of claim 10,
further comprising instructions executable by the processor to
retrieve the customer premise equipment access certificate from a
customer premise equipment access database.
12. The non-transitory computer readable medium of claim 10,
further comprising instructions executable by the processor to
store the customer premise equipment data in a customer premise
equipment data database.
13. The non-transitory computer readable medium of claim 10,
further comprising instructions executable by the processor to
forward the customer premise equipment data to the service provider
system.
14. The non-transitory computer readable medium of claim 10,
wherein the trigger event relates to activation of the first
customer premise equipment device.
15. A system, comprising: at least one processor; and at least one
memory accessible to the at least one processor, the at least one
memory comprising instructions executable by the at least one
processor to: receive a develop customer specific marketing
strategies, implement customer specific maintenance procedures
and/or implement customer specific trouble shooting procedures data
request from a customer premise equipment management system,
wherein the customer premise equipment request comprises a customer
premise equipment access certificate; and send requested data to
the customer premise equipment management system when the customer
premise equipment access certificate authorizes the processor to
provide data to the customer premise equipment management
system.
16. The system of claim 11, wherein the develop customer specific
marketing strategies, implement customer specific maintenance
procedures and/or implement customer specific trouble shooting
procedures data request comprises a request for a bulk download of
customer premise data.
17. The system of claim 11, wherein the develop customer specific
marketing strategies, implement customer specific maintenance
procedures and/or implement customer specific trouble shooting
procedures data request comprises a request for wide area network
data.
18. The system of claim 11, wherein the develop customer specific
marketing strategies, implement customer specific maintenance
procedures and/or implement customer specific trouble shooting
procedures data request comprises a request for local area network
data.
19. The system of claim 11, wherein the develop customer specific
marketing strategies, implement customer specific maintenance
procedures and/or implement customer specific trouble shooting
procedures data request is received as part of a trouble shooting
procedure.
20. The system of claim 11, wherein the develop customer specific
marketing strategies, implement customer specific maintenance
procedures and/or implement customer specific trouble shooting
procedures data request is received as part of a maintenance
procedure.
Description
PRIORITY CLAIM
[0001] This application is a continuation of, and claims priority
to, U.S. patent application Ser. No. 11/729,682, filed on Mar. 29,
2007, which is hereby incorporated by reference in its
entirety.
FIELD OF THE DISCLOSURE
[0002] The disclosure generally relates to customer premise
equipment and more particularly to systems and methods for
retrieving customer premise equipment data.
BACKGROUND
[0003] Service providers routinely install customer premise
equipment (CPE) devices at individual customer locations to
facilitate the providing of services. Examples of such service
providers include, but are not limited to, Internet service
providers, telephone service providers, and cable service
providers. CPE devices often store CPE device specific data
including, but not limited to, wide area network (WAN) data and
local area network (LAN) data. The WAN data stored in a CPE device
typically relates to WAN level activity between the CPE device and
the service provider. Examples of the types of WAN data that may be
stored in a CPE device include, but are not limited to, CPE WAN
performance statistics and CPE WAN usage parameters. The LAN data
stored in a CPE device typically relates to customer location
specific activity relating to the use of service provider services.
Examples of the types of LAN data that may be stored in a CPE
device include, but are not limited to, LAN performance parameters,
LAN usage parameters, LAN performance statistics, and service
provider service usage statistics. develop customer specific
marketing strategies, implement customer specific maintenance
procedures and/or implement customer specific trouble shooting
procedures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0004] FIG. 1 is a schematic block diagram of an example of a
network system including one embodiment of a CPE data retrieval
system;
[0005] FIG. 2 is a block diagram of one embodiment of a CPE data
retrieval module;
[0006] FIG. 3 is a flow chart of one embodiment of a method of
collecting CPE access data from a CMS;
[0007] FIG. 4 a flow chart of one embodiment of a method of
providing requested CPE access data from a CMS to a CPE data
retrieval system;
[0008] FIG. 5 is a flow chart of one embodiment of a method of
retrieving CPE data;
[0009] FIG. 6 is a flow chart of another embodiment of a method of
retrieving CPE data;
[0010] FIG. 7 is a flow chart of another embodiment of a method of
retrieving CPE data; and
[0011] FIG. 8 is an illustrative embodiment of a general computer
system.
DETAILED DESCRIPTION
[0012] Referring to FIG. 1, a schematic block diagram of a network
system 100 including one embodiment of a customer premise equipment
(CPE) data retrieval system 102 is shown. The network system 100
generally includes a service provider system 104, a CPE data
retrieval system 102, a CPE management system (CMS) 106, one or
more node elements 108, and a plurality of CPE devices 110.
[0013] In one embodiment, the service provider system 104, the CPE
data retrieval system 102, and the CMS 106 are communicatively
coupled via an Intranet network. In one embodiment, the service
provider 104, the CPE data retrieval system 102, and the CMS 106
are communicatively coupled via an Internet network. In one
embodiment, the service provider system 104, the CPE data retrieval
system 102, and the CMS 106 are communicatively coupled via a
combination of an Internet network and an Intranet network. In one
embodiment, the service provider system 104 includes the CMS 106 as
an integrated component of the service provider system 104. In one
embodiment, the service provider system 104 includes the CPE data
retrieval system 102 as an integrated component of the service
provider system 104. In one embodiment, the service provider system
104 includes both the CMS 106 and the CPE data retrieval system 102
as integrated components of the system provider system 104.
[0014] The service provider system 104, the CPE data retrieval
system 102, and the CMS 106 are communicatively coupled to each of
the node elements 108. In one embodiment, each of the service
provider system 104, the CPE data retrieval system 102, and the CMS
106 are communicatively coupled to each of the node elements 108
via an Internet network system. Each of the node elements 108 are
communicatively coupled to one or more CPE devices 110. In one
embodiment, each of the node elements are communicatively coupled
to one or more CPE devices 110 via an Internet network. A node
element 108 generally routes data to and from one or more CPE
devices 110 associated with the node element 108 within the network
system 100. In one embodiment, the node elements 108 route data
exchanges between the CPE devices 110 and one or more of the
service provider system 104, the CPE data retrieval system 102, and
the CMS 106.
[0015] A CPE device 110 is installed at each service provider
customer location. The service provider system 104 provides one or
more services to a service provider customer via the installed CPE
device 110. Examples of services provided by the service provider
system 104 include, but are not limited to, telephone services,
cable services, and Internet services. Examples of CPE devices 110
include, but are not limited to, ADSL modems, set up boxes, and
residential gateways. Each CPE device 110 stores CPE specific data.
The types of CPE specific data stored in the CPE device 110
include, but are not limited to, CPE wide area network (WAN) data
and local area network (LAN) data. The LAN is a customer location
network communicatively coupled to the CPE device 110.
[0016] CPE WAN data includes CPE data parameters relating to WAN
level activity between the CPE device 110 and the network system
100. Examples of CPE WAN data include, but are not limited to, CPE
WAN performance parameters, CPE WAN performance statistics, CPE WAN
usage parameters, CPE downstream Dynamic Spectrum Management (DSM)
statistics, CPE upstream/downstream WAN usage, and CPE
upstream/downstream performance statistics. LAN data includes CPE
data parameters associated with customer location specific activity
relating to the use of services provided by the service provider.
Examples of LAN data parameters include, but are not limited to,
LAN performance parameters, LAN usage parameters, LAN performance
statistics, and service provider service usage statistics.
[0017] The CMS 106 generally manages and stores CPE device specific
CPE access data for each of the CPE devices 110 under the
management of the CMS 106. In one embodiment, the CMS 106 manages
and stores CPE access data for CPE devices 110 associated with a
single service provider. In one embodiment, the CMS 106 manages and
stores CPE access data for CPE devices 110 associated with a number
of different service providers. In one embodiment, the CPE access
data stored by the CMS 106 includes a CPE identification tag and a
CPE access certificate for each of the CPE devices 110. In one
embodiment, the CPE access data stored by the CMS 106 includes a
CPE identification tag, a CPE access certificate, and a CPE type
for each of the CPE devices 110.
[0018] In one embodiment, the CPE data retrieval system 102
coordinates the retrieval of selected CPE data from one or more
selected CPE devices 110. In one embodiment, the CPE data retrieval
system 102 coordinates a bulk download of CPE data from one or more
selected CPE devices 110. In one embodiment, the CPE data retrieval
system 102 coordinates a periodic retrieval of selected CPE data
from one or more selected CPE devices 110. In one embodiment, the
CPE data retrieval system 102 coordinates a periodic bulk download
of CPE data from one or more selected CPE devices 110.
[0019] In one embodiment, the selected CPE devices 110 consist of
the CPE devices 110 under the management of the CPE data retrieval
system 102. In one embodiment, the selected CPE devices 110 consist
of the CPE devices 110 under the management of the CPE data
retrieval system 102 that are associated with a specific service
provider. In one embodiment, the one or more selected CPE devices
110 consist of one or more CPE devices 110 undergoing a trouble
shooting procedure. In one embodiment, the one or more selected CPE
devices 110 consist of one or more CPE devices 110 selected for a
maintenance procedure.
[0020] Referring to FIG. 2, a block diagram of one embodiment of a
CPE data retrieval module 200 is shown. The CPE data retrieval
system 102 includes a CPE data retrieval module 200. The CPE data
retrieval module 200 generally coordinates the retrieval and
storage of CPE data from one or more selected CPE devices 110. One
embodiment of the CPE data retrieval module 200 generally includes
a communication module 201, a CPE access data collection module
202, a CPE data collection module 204, a CPE access data database
206, and a CPE data database 208.
[0021] The communication module 201 generally coordinates
communications between the CPE data retrieval system 102 and one or
more of the service provider system 104, the CMS 106, and one or
more selected CPE devices 110. In one embodiment, the communication
module 201 establishes communication channels between the CPE data
retrieval system 102 and one or more of the service provider system
104, the CMS 106, and one or more selected CPE devices 110
responsive to requests received from the CPE access data collection
module 202 and/or the CPE data collection module 204.
[0022] The CPE access data collection module 202 manages the
collection and storage of CPE access data. As mentioned previously,
the CMS 106 stores CPE access data for each of the CPE devices 110
under the management of the CMS 106. During the initialization of
the CPE data retrieval system 102, the CPE access data collection
module 202 coordinates the collection of the CPE access data for
the CPE devices 110 associated with the CPE data retrieval system
102 from the CMS 106.
[0023] In one embodiment, the set of CPE devices 110 associated
with the CPE data retrieval system 102 are the same set of CPE
devices 110 under the management of the CMS 106. In one embodiment,
the CPE devices 110 associated with the CPE data retrieval system
102 are affiliated with a specific service provider while the CMS
106 manages CPE devices 110 for multiple service providers. In one
embodiment, the CPE devices 110 associated with the CPE data
retrieval system 102 are affiliated with a specific segment of a
service provider network.
[0024] Referring to FIG. 3, a flow chart of one embodiment of a
method 300 of collecting CPE access data is shown. A communication
channel is established with a CMS 106 at step 302. In one
embodiment, the CPE access data collection module 202 issues a
command to the communication module 201 to establish a
communication channel between the CPE data retrieval system 102 and
the CMS 106. The communication module 201 responsively establishes
a communication channel between the CPE data retrieval system 102
and the CMS 106. A request for CPE access data is issued to the CMS
106 via the communication channel at step 304. In one embodiment,
the CPE access data collection module 202 issues a request for CPE
access data to the CMS 106. In one embodiment, the CPE access data
collection module 202 issues a request for CPE access data for the
CPE devices 110 associated with the CPE data retrieval system 102.
In one embodiment, the CPE access data collection module 202 issues
a request for CPE access data for one or more selected CPE devices
110. The requested CPE access data is received from the CMS 106 at
the CPE data retrieval system via the communication channel at step
306. In one embodiment, the CPE access data collection module 202
stores the received CPE access data in the CPE access data database
206. While the steps in the method 300 have been described in a
particular order, the described steps may be performed in a
different order, a subset of the described steps may be performed,
or additional steps may be performed in addition to the described
steps.
[0025] Referring to FIG. 4 a flow chart of one embodiment of a
method 400 of providing requested CPE access data from a CMS 106 to
a CPE data retrieval system 102 is shown. A request for CPE access
data associated with at least one CPE device 110 is received at a
CMS 106 at step 402. In one embodiment, the CMS 106 receives a
request for CPE access data for the CPE devices 110 associated with
the CPE data retrieval system 102. In one embodiment, the CMS 106
receives a request for CPE access data for one or more selected CPE
devices 110. The requested CPE access data is transmitted from the
CMS 106 to the CPE data retrieval system 102 responsive to the
received request at step 402. While the steps in the method 400
have been described in a particular order, the described steps may
be performed in a different order, a subset of the described steps
may be performed, or additional steps may be performed in addition
to the described steps.
[0026] Referring back to FIG. 2, as additional CPE devices 110 are
placed under the management of the CPE data retrieval system 102,
the CPE access data collection module 202 manages the collection
and storage of the CPE access data for the newly added CPE devices
110. In one embodiment, the CPE access data collection module 202
periodically requests the CPE access data for newly added CPE
devices 110 from the CMS 106. In one embodiment, the CPE data
retrieval system 102 automatically receives the CPE access data
from a newly added CPE device 110 during the activation of the new
CPE device 110. Upon receipt of CPE access data, the CPE access
data collection module 202 stores the received CPE access data in
the CPE access data database 206.
[0027] In one embodiment, the CPE access data collection module 202
retrieves CPE access data for one or more selected CPE devices 110
from the CMS 106 on an ad hoc basis. When the CPE data retrieval
system 102 selects one or more CPE devices 110 for CPE data
retrieval, the CPE access data collection module 202 issues a
request for the CPE access data for the one or more selected CPE
devices 110 to the CMS 106. The CPE access data collection module
202 forwards the received CPE access data to the CPE data
collection module 204.
[0028] The CPE data collection module 204 generally coordinates the
retrieval and storage of CPE data from one or more selected CPE
devices 110 responsive to a trigger event. The trigger event
defines the one or more CPE devices 110 selected for CPE data
retrieval. In one embodiment, the trigger event is a request from
the service provider system 104 for one or more selected CPE data
parameters from one or more selected CPE devices 110. In one
embodiment, the trigger event is a request initiated by the CPE
data retrieval system 102 for the retrieval of one or more selected
CPE data parameters from one or more selected CPE devices 110. In
one embodiment, the trigger event is a request initiated by the CPE
data retrieval system 102 for a bulk download of CPE data stored in
one or more selected CPE devices 110. In one embodiment, the
trigger event is a request initiated by the CPE data retrieval
system 102 for a bulk download of CPE data stored in the CPE
devices 110 under the management of the CPE data retrieval system
102. In one embodiment the request for CPE data issued by the CPE
data retrieval system 102 is initiated on a periodic basis. In one
embodiment, the request for CPE data issued by the CPE data
retrieval system 102 is initiated approximately every twenty-four
hours. Responsive to the trigger event, the CPE data collection
module 204 retrieves the CPE access data for the one or more
selected CPE devices 110 from the CPE access data database 206.
[0029] In one embodiment, the retrieved CPE access data includes
the CPE identification tag, the CPE access certificate, and the CPE
type for each of the one or more selected CPE devices 110.
Different types of CPE devices 110 may be supported by different
application program interfaces (API) thereby requiring different
access mechanisms. The CPE data collection module 202 uses the CPE
type for each of the one or more selected CPE devices 110 to
identify the specific API supported by each of the one or more
selected CPE devices 110 and to determine the appropriate access
mechanisms for each of the one or more selected CPE devices 110.
The CPE data retrieval system 102 uses the CPE identification tag
to address the CPE device 110 identified by the CPE identification
tag. The CPE data retrieval system 102 uses the CPE access
certificate to provide the authorization necessary to gain access
to the CPE data stored in the associated CPE device 110.
[0030] When a single CPE device 110 is selected for CPE data
retrieval, the CPE data collection module 204 issues a command to
the communication module 201 to establish a communication channel
between the CPE data retrieval system 102 and the selected CPE
device 110 using the CPE identification tag, CPE specific access
mechanism, and the CPE access certificate for that CPE device 110.
The communication channel is established via the node element 108
associated with the selected CPE device 110 within the Internet
network. The trigger event defines the CPE data parameters selected
for retrieval. The CPE data collection module 204 issues a request
for the selected CPE data parameters to the selected CPE device
110. The selected CPE device 110 responsively retrieves the
requested one or more CPE data parameters from a CPE memory and
transmits the requested one or more CPE data parameters from the
CPE device 110 to the CPE data retrieval system 102. The CPE data
collection module 204 stores the received CPE data in the CPE data
database 206. In cases, where the CPE data is requested by a
service provider, the retrieved CPE data is forwarded to the
service provider system 104.
[0031] In one embodiment, when multiple CPE devices 110 are
selected for CPE data retrieval, the CPE data collection module 204
issues a command to the communication module 201 to establish
individual communication channels with each of the multiple CPE
devices 110 using the CPE identification tags, the CPE access
mechanisms, and the CPE access certificates for each of the
selected CPE devices 110. In one embodiment, the CPE data
collection module 204 issues a command to the communication module
201 to simultaneously establish multiple parallel communication
channels between the CPE data retrieval system 102 and each of the
selected CPE devices 110. Each of the parallel communication
channels are established between the CPE data retrieval system 102
and each one of the selected CPE devices 110 via the node element
associated with each of the selected CPE devices 110 within the
Internet network. In one embodiment, the CPE data retrieval system
102 issues requests for the selected CPE data parameters to each of
the selected CPE devices 110 via the established communication
channels. In one embodiment, the CPE data retrieval system 102
simultaneously issues parallel requests for the selected CPE data
parameters to each of the selected CPE devices 110 via the
established communication channels. Each of the selected CPE
devices 110 responsively retrieves the requested CPE data from CPE
memory and transmits the requested CPE data parameters from the CPE
device 110 to the CPE data retrieval system 102. The CPE data
collection module 204 stores the received CPE data in the CPE data
database 206. In cases, where the CPE data is requested by a
service provider, the retrieved CPE data is forwarded to the
service provider system 104.
[0032] In one embodiment, the trigger event is a request for a bulk
download of CPE data from each of the plurality of CPE devices 110
associated with the CPE data retrieval system 102. In one
embodiment, the request for the bulk download of CPE data from each
of the plurality of CPE devices 110 is initiated by the CPE data
retrieval system 102. In one embodiment, the request for the bulk
download of CPE data from each of the plurality of CPE devices 110
is initiated by the CPE data retrieval system 102 on a periodic
basis. Responsive to the trigger event, the CPE data collection
module 204 issues a command to the communication module 201 to
establish parallel communication channels between the CPE data
retrieval system 102 and each of the plurality of CPE devices 110
in the CPE data retrieval system 102. The CPE data collection
module 204 issues requests for a bulk download of CPE data to each
of the plurality of CPE devices 110 via the parallel communication
channels. Each of the plurality of CPE devices 110 responsively
retrieves the CPE data stored in each of the respective CPE devices
110 and transmits the CPE data to the CPE data retrieval system
102. In one embodiment, the CPE data collection module 204 archives
the CPE data that is collected during the bulk download of CPE data
in the CPE data database 208. In one embodiment, the CPE data
collection module 204 maintains the CPE data retrieved during the
bulk download of CPE data in the CPE data database 208 for a
pre-defined period of time.
[0033] In one embodiment, the number of CPE devices 110 that the
CPE data retrieval system 102 communicates with during a single CPE
data retrieval session is defined by the CPE data retrieval system
hardware, software and/or bandwidth limitations. In one embodiment,
the number of CPE devices 110 that the CPE data retrieval system
102 communicates with during a single CPE data retrieval session
ranges from a single CPE device 110 to as many as a thousand CPE
devices 110. In one embodiment, it takes approximate one minute to
perform a bulk download of the CPE data stored in a single CPE
device 110 to the CPE data retrieval system 102.
[0034] In one embodiment, the CPE devices 110 employ a Digital
Subscriber Line (DSL) forum standard TR69 tree data model to store
CPE data. The DSL forum standard TR69 tree data model supports the
retrieval of CPE data by the CPE data retrieval system 102 as
individual data elements, as an individual data branch, or as a
whole data tree. CPE data is typically retrieved from a CPE device
110 in the form of a whole data tree during a bulk download of CPE
data from the CPE device 110.
[0035] It should be noted that the systems described above may be
implemented using software or firmware executed by hardware, or
exclusively in hardware through the use of one or more custom
circuits, such as for example, application-specific integrated
circuits (ASICs) or any other suitable combination of hardware
and/or software.
[0036] Referring to FIG. 5, a flow chart of one embodiment of a
method 500 of retrieving CPE data is shown. A first communication
channel is established with a first CPE device 110 via a first node
element 108 at step 502. The first node element 108 is operable to
route data to and from the first CPE device 110 in an Internet
network. A request for CPE data is issued to the first CPE device
110 via the first communication channel at step 504. The requested
CPE data is received from the first CPE device 110 via the first
communication channel at step 506. While the steps in the method
500 have been described in a particular order, the steps may be
performed in a different order or additional steps may be performed
in addition to the described steps.
[0037] In one embodiment, a computer readable medium stores a
computer executable program for retrieving customer premise
equipment (CPE) data. The computer readable medium includes
computer readable code for establishing a first communication
channel with a first CPE device 110 via a first node element 108,
the first node element 108 being operable to route data to and from
the first CPE device 110 in an Internet network, computer readable
code for issuing a first request for CPE data to the first CPE
device 110 via the first communication channel, and computer
readable code for receiving the requested CPE data from the first
CPE device 110 via the first communication channel.
[0038] In one embodiment, a system for retrieving customer premise
equipment (CPE) data includes a communication module 201 and a CPE
data collection module 204. The communication module 201 is
operable to establish a first communication channel with a first
CPE device 110 via a first node element 108, the first node element
108 being operable to route data to and from the first CPE device
110 in an Internet network. The CPE data collection module 204 is
communicatively coupled to the communication module 201. The CPE
data collection module 204 is operable to issue a first request for
CPE data to the first CPE device 110 via the first communication
channel and receive the requested CPE data from the first CPE
device 110 via the first communication channel.
[0039] Referring to FIG. 6, a flow chart of another embodiment of
retrieving CPE data is shown. A request for CPE data is received at
a CPE device 110 via a communication channel including a node
element 108 at step 602. The node element 108 is operable to route
data to and from the CPE device 110 in an Internet network. The
requested CPE data is transmitted from the CPE device 110 to the
CPE data retrieval system 102 via the communication channel at step
604. While the steps in the method 600 have been described in a
particular order, the described steps may be performed in a
different order, a subset of the described steps may be performed,
or additional steps may be performed in addition to the described
steps.
[0040] Referring to FIG. 7, a flow chart of another embodiment of a
method 700 of retrieving CPE data using a CPE data retrieval system
102 is shown. The CPE data collection module 204 detects a trigger
event at step 702. The CPE data collection module 204 identifies
the one or more CPE devices 110 that have been selected for CPE
data retrieval based on an analysis of the trigger event at step
704 and retrieves the CPE access data for each of the one or more
selected CPE devices 110 from the CPE access data database 206 at
step 706. The CPE data collection module 204 reviews the CPE type
of each of the selected one or more CPE devices 110 and to identify
the specific API supported by each of the one or more selected CPE
devices 110 at step 708 and to determine the appropriate access
mechanisms for each of the one or more selected CPE devices 110 at
step 710. The CPE data collection module 204 determines the CPE
data targeted for retrieval from the one or more selected CPE
devices 110 based on an analysis of the trigger event at step
712.
[0041] The CPE data collection module 204 issues a command to the
communication module 201 to establish communication channels
between the CPE data retrieval system 102 and each of the one or
more selected CPE devices 110 using the CPE identification tag, the
CPE access mechanism, and the CPE access certificate for each of
the selected one or more CPE devices 110 and the communication
module 201 establishes the requested communication channels at step
714. Each of the communication channels is established between the
CPE data retrieval system 102 and each one of the respective
selected CPE devices 110 via an associated node element 108 within
the Internet network. The CPE data retrieval system 102 issues a
request for the CPE data targeted for retrieval to each of the one
or more selected CPE devices 110 via the respective communication
channel at step 716. Each of the one or more selected CPE devices
110 responsively transmits the requested CPE data to the CPE data
retrieval system 102. The requested CPE data is received from each
of the selected one or more CPE devices 110 at the CPE data
retrieval system 102 at step 718. The CPE data collection module
204 stores the CPE data received from the selected one or more CPE
devices 110 in the CPE data database 208 at step 720.
[0042] While the steps in the method 700 have been described in a
particular order, the described steps may be performed in a
different order, a subset of the described steps may be performed,
or additional steps may be performed in addition to the described
steps.
[0043] Referring to FIG. 8, an illustrative embodiment of a general
computer system is shown and is designated 800. The computer system
800 can include a set of instructions that can be executed to cause
the computer system 800 to perform any one or more of the methods
or computer based functions disclosed herein. The computer system
800 may operate as a standalone device or may be connected, e.g.,
using a network, to other computer systems or peripheral
devices.
[0044] In a networked deployment, the computer system may operate
in the capacity of a server or as a client user computer in a
server-client user network environment, or as a peer computer
system in a peer-to-peer (or distributed) network environment. The
computer system 800 can also be implemented as or incorporated into
various devices, such as a personal computer (PC), a tablet PC, a
set-top box (STB), a personal digital assistant (PDA), a mobile
device, a palmtop computer, a laptop computer, a desktop computer,
a communications device, a wireless telephone, a land-line
telephone, a control system, a camera, a scanner, a facsimile
machine, a printer, a pager, a personal trusted device, a web
appliance, a network router, switch or bridge, a CPE device 110, a
CPE data retrieval system 102, a CMS 106, a service provider system
104, or any other machine capable of executing a set of
instructions (sequential or otherwise) that specify actions to be
taken by that machine. In a particular embodiment, the computer
system 800 can be implemented using electronic devices that provide
voice, video or data communication. Further, while a single
computer system 800 is illustrated, the term "system" shall also be
taken to include any collection of systems or sub-systems that
individually or jointly execute a set, or multiple sets, of
instructions to perform one or more computer functions.
[0045] As illustrated in FIG. 8, the computer system 800 may
include a processor 802, e.g., a central processing unit (CPU), a
graphics processing unit (GPU), or both. Moreover, the computer
system 800 can include a main memory 804 and a static memory 806
that can communicate with each other via a bus 808. As shown, the
computer system 800 may further include a video display unit 810,
such as a liquid crystal display (LCD), an organic light emitting
diode (OLED), a flat panel display, a solid state display, or a
cathode ray tube (CRT). Additionally, the computer system 800 may
include an input device 812, such as a keyboard, and a cursor
control device 814, such as a mouse. The computer system 800 can
also include a disk drive unit 816, a signal generation device 818,
such as a speaker or remote control, and a network interface device
820.
[0046] In a particular embodiment, as depicted in FIG. 8, the disk
drive unit 816 may include a computer-readable medium 822 in which
one or more sets of instructions 824, e.g. software, can be
embedded. Further, the instructions 824 may embody one or more of
the methods or logic as described herein. In a particular
embodiment, the instructions 824 may reside completely, or at least
partially, within the main memory 804, the static memory 806,
and/or within the processor 802 during execution by the computer
system 800. The main memory 804 and the processor 802 also may
include computer-readable media.
[0047] In an alternative embodiment, dedicated hardware
implementations, such as application specific integrated circuits,
programmable logic arrays and other hardware devices, can be
constructed to implement one or more of the methods described
herein. Applications that may include the apparatus and systems of
various embodiments can broadly include a variety of electronic and
computer systems. One or more embodiments described herein may
implement functions using two or more specific interconnected
hardware modules or devices with related control and data signals
that can be communicated between and through the modules, or as
portions of an application-specific integrated circuit.
Accordingly, the present system encompasses software, firmware, and
hardware implementations.
[0048] In accordance with various embodiments of the present
disclosure, the methods described herein may be implemented by
software programs executable by a computer system. Further, in an
exemplary, non-limited embodiment, implementations can include
distributed processing, component/object distributed processing,
and parallel processing. Alternatively, virtual computer system
processing can be constructed to implement one or more of the
methods or functionality as described herein.
[0049] The present disclosure contemplates a computer-readable
medium that includes instructions 824 or receives and executes
instructions 824 responsive to a propagated signal, so that a
device connected to a network 826 can communicate voice, video or
data over the network 826. Further, the instructions 824 may be
transmitted or received over the network 826 via the network
interface device 820.
[0050] While the computer-readable medium is shown to be a single
medium, the term "computer-readable medium" includes a single
medium or multiple media, such as a centralized or distributed
database, and/or associated caches and servers that store one or
more sets of instructions. The term "computer-readable medium"
shall also include any medium that is capable of storing, encoding
or carrying a set of instructions for execution by a processor or
that cause a computer system to perform any one or more of the
methods or operations disclosed herein.
[0051] In a particular non-limiting, exemplary embodiment, the
computer-readable medium can include a solid-state memory such as a
memory card or other package that houses one or more non-volatile
read-only memories. Further, the computer-readable medium can be a
random access memory or other volatile re-writable memory.
Additionally, the computer-readable medium can include a
magneto-optical or optical medium, such as a disk or tapes or other
storage device to capture carrier wave signals such as a signal
communicated over a transmission medium. A digital file attachment
to an e-mail or other self-contained information archive or set of
archives may be considered a distribution medium that is equivalent
to a tangible storage medium. Accordingly, the disclosure is
considered to include any one or more of a computer-readable medium
or a distribution medium and other equivalents and successor media,
in which data or instructions may be stored.
[0052] Although the present specification describes components and
functions that may be implemented in particular embodiments with
reference to particular standards and protocols, the invention is
not limited to such standards and protocols. For example, standards
for Internet and other packet switched network transmission (e.g.,
TCP/IP, UDP/IP, HTML, HTTP) represent examples of the state of the
art. Such standards are periodically superseded by faster or more
efficient equivalents having essentially the same functions.
Accordingly, replacement standards and protocols having the same or
similar functions as those disclosed herein are considered
equivalents thereof.
[0053] The illustrations of the embodiments described herein are
intended to provide a general understanding of the structure of the
various embodiments. The illustrations are not intended to serve as
a complete description of all of the elements and features of
apparatus and systems that utilize the structures or methods
described herein. Many other embodiments may be apparent to those
of skill in the art upon reviewing the disclosure. Other
embodiments may be utilized and derived from the disclosure, such
that structural and logical substitutions and changes may be made
without departing from the scope of the disclosure. Additionally,
the illustrations are merely representational and may not be drawn
to scale. Certain proportions within the illustrations may be
exaggerated, while other proportions may be minimized. Accordingly,
the disclosure and the figures are to be regarded as illustrative
rather than restrictive.
[0054] One or more embodiments of the disclosure may be referred to
herein, individually and/or collectively, by the term "invention"
merely for convenience and without intending to voluntarily limit
the scope of this application to any particular invention or
inventive concept. Moreover, although specific embodiments have
been illustrated and described herein, it should be appreciated
that any subsequent arrangement designed to achieve the same or
similar purpose may be substituted for the specific embodiments
shown. This disclosure is intended to cover any and all subsequent
adaptations or variations of various embodiments. Combinations of
the above embodiments, and other embodiments not specifically
described herein, will be apparent to those of skill in the art
upon reviewing the description.
[0055] The Abstract of the Disclosure is submitted with the
understanding that it will not be used to interpret or limit the
scope or meaning of the claims. In addition, in the foregoing
Detailed Description, various features may be grouped together or
described in a single embodiment for the purpose of streamlining
the disclosure. This disclosure is not to be interpreted as
reflecting an intention that the claimed embodiments require more
features than are expressly recited in each claim. Rather, as the
following claims reflect, inventive subject matter may be directed
to less than all of the features of any of the disclosed
embodiments. Thus, the following claims are incorporated into the
Detailed Description, with each claim standing on its own as
defining separately claimed subject matter.
[0056] The above disclosed subject matter is to be considered
illustrative, and not restrictive, and the appended claims are
intended to cover all such modifications, enhancements, and other
embodiments which fall within the true spirit and scope of the
present invention. Thus, to the maximum extent allowed by law, the
scope of the present invention is to be determined by the broadest
permissible interpretation of the following claims and their
equivalents, and shall not be restricted or limited by the
foregoing detailed description
* * * * *