Customized data delivery and network configuration via aggregation of device attributes
Claim Score by NHIP
Abstract
Aspects of a method and system for customized data delivery and network configuration via aggregation of device attributes are provided. In this regard, a first network device may receive device attributes from a plurality of devices that are communicatively coupled to the first network device. The first network device may aggregate the received device attributes and communicate the aggregate attributes to a source network device. The first network device may receive customized content from the source network device, wherein the customization is based on the aggregate device attributes. The first network device may communicate the customized content to the plurality of devices. The first network device may comprise, for example, a set-top box, a wired access point, and/or wireless access point. The device attributes of a device may comprise settings, capabilities, and/or user preferences of the device.

Term
5.4 yearsto projected expiry
Projected expiry 19 February 2032, counted from filing; an application has no term until it is granted.
- Priority
- Filed
- Published
- Today
- Projected expiry
24 claims: 2 independent, 22 dependent
- 1Broadest claimClaim Score 74, broad(NHIP)A method for communication, the method comprising:performing by one or more circuits in a first network device: receiving device attributes from a plurality of second network devices that are communicatively coupled to said access point device;aggregating said received device attributes;communicating said aggregate device attributes to a source network device;and receiving customized content from said source network device, wherein said content is customized based on said aggregate device attributes;and communicating said customized content from said access point device to said one or more devices.
- 13A system for communication, the system comprising:one or more circuits and/or processors for use in a first network device, wherein said one or more circuits and/or processors are operable to: receive device attributes from a plurality of second network devices that are communicatively coupled to said access point device;aggregate said received device attributes;communicate said aggregate device attributes to a source network device;and receive customized content from said source network device, wherein said content is customized based on said aggregate device attributes;and communicate said customized content from said access point device to said one or more devices.
Independent claims2
54 paragraphs in 6 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE
0001This patent application makes reference to, claims priority to and claims benefit from U.S. Provisional Patent Application Ser. No. 61/228,385 filed on Jul. 24, 2009.
0002The above stated application is hereby incorporated herein by reference in its entirety.
FIELD OF THE INVENTION
0003Certain embodiments of the invention relate to networking. More specifically, certain embodiments of the invention relate to a method and system for customized data delivery and network configuration via aggregation of device attributes.
BACKGROUND OF THE INVENTION
0004Electronic communication networks are becoming an increasingly popular means of exchanging data of various types, sizes for a variety of applications and business and consumers alike want network access on more and more devices. Moreover, consumers and business continually want faster network access and/or greater bandwidth on all of their communication devices. Consequently, as more and more devices are being equipped to access communication networks, network administrators and service providers are presented with the challenge of effectively serving an increasing number of devices having and increasingly diverse set of capabilities utilizing an increasing diverse collection of protocols, software, and/or other networking and computing resources.
0005Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
BRIEF SUMMARY OF THE INVENTION
0006A system and/or method is provided for customized data delivery and network configuration via aggregation of device attributes, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.
0007These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.
BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS
0008<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrating customized data delivery based on aggregated device attributes, in accordance with an embodiment of the invention.
0009<figref idref="DRAWINGS">FIG. 2</figref> is a diagram illustrating aggregation and communication of device attributes, in accordance with an embodiment of the invention.
0010<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating multiple levels of aggregation of device attributes, in accordance with an embodiment of the invention.
0011<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart illustrating exemplary steps for aggregating and communicating device attributes, in accordance with an embodiment of the invention.
0012<figref idref="DRAWINGS">FIG. 5</figref> is a flow chart illustrating delivery of customized data based on aggregated device attributes, in accordance with an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
0013Certain embodiments of the invention may be found in a method and system for customized data delivery and network configuration via aggregation of device attributes. In various embodiments of the invention, first network device may receive device attributes from a plurality of devices that are communicatively coupled to the first network device. The first network device may aggregate the device attributes and communicate the aggregate device attributes to a source network device. The first network device may receive customized from the source network device, wherein the customization is based on the aggregate device attributes. The first network device may communicate the customized content to the plurality of devices. The first network device may comprise one or more of a set-top box, a wired access point, and/or wireless access point. The device attributes of each of the plurality of network devices may comprise settings, capabilities, and/or user preferences. Additionally or alternatively, the device attributes of each of the plurality of network devices may comprise one or more of: a serial number or unique identifier, a manufacturer identifier, a model identifier, a hardware configuration, a software configuration, an operating system identifier, available and/or total memory, available and/or total processing cycles, security information, battery level, and/or power settings.
0014The communication of the aggregate device attributes may be secured utilizing IPSec and/or MACsec protocols. The device attributes may be received by the first network device via an out-of-band channel. The device attributes may be received by the first network device via an optical communication link. The content may be customized by one or more of: compressing, decompressing, down-sampling, and/or up-sampling. The customized content may be delivered from the first network device to the plurality of devices based on the aggregate device attributes. The first network device may be configured based on the aggregate device attributes. The source network device may be configured based on the aggregate device attributes. One or more network devices along a network path between the first network device and the source network device may be configured based on the aggregate device attributes.
0015<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrating customized data delivery based on aggregated device attributes, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 1</figref>, there is shown a network <b>100</b> comprising a server <b>106</b> and a subnetwork <b>112</b>. The subnetwork <b>112</b> may be, for example, a local area network (LAN) and may comprise network devices <b>114</b><i>a</i>, <b>114</b><i>b</i>, and <b>114</b> (collectively or individually referenced herein as network devices <b>114</b>) and <b>116</b>.
0016The server <b>106</b> may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to provide services and/or applications to one or more remote device(s) and to customize the services and/or applications provided to one or more remote device(s) based on attributes of the one or more remote device(s). Exemplary services and/or applications provided by the server <b>106</b> may comprise web hosting, general purpose file hosting and/or storage, multimedia streaming, e-mail, online gaming, and VoIP. Additionally, the server <b>106</b> may comprise a memory <b>108</b> that may be operable to store device attributes for network devices that communicate with the server <b>206</b>.
0017The network devices <b>114</b> may comprise various devices such as home entertainment equipment, computing devices, and portable devices. Exemplary entertainment equipment may comprise set-top boxes, optical drives, digital video recorders, televisions, and/or stereo systems. Exemplary computing devices may comprise desktop computers, laptop computers, and servers. Exemplary portable devices may comprise cell phones, smartphones, laptop computers, and/or portable media players.
0018Each of the network devices <b>114</b> may comprise suitable logic, circuitry, interfaces and/or code that may be operable to process electronic information and communicate with the network device <b>116</b>. For example, each of the network devices <b>114</b> may be operable to send requests for data and/or content, receive, process, and present content, and/or to run a web browser or other applications for providing network services and/or applications to a user. Additionally, as part of communicating with the network device <b>116</b>, each of the network devices <b>114</b> may be operable to communicate its attributes to the network device <b>116</b>. In various embodiments of the invention, attributes of the devices <b>114</b><i>a</i>, <b>114</b><i>b</i>, and <b>114</b><i>c </i>may be associated with or indicated by a user profile of the cellular enabled communication devices <b>114</b><i>a</i>, <b>114</b><i>b</i>, and <b>114</b><i>c</i>, respectively.
0019The network device <b>116</b> may be an access point device which may comprise, for example, a router, a server, a wired access point, a wireless access point, or a set-top box. The network device <b>116</b> may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to communicate with the network devices <b>114</b> and with the server <b>116</b>. In communicating with the network devices <b>114</b>, the network device <b>116</b> may receive device attributes from one or more of the network devices <b>114</b> and communicate the aggregate device attributes from the network devices <b>114</b> to the server <b>106</b>.
0020Protocols and/or network links utilized for communication between the network devices <b>114</b> and the network device <b>116</b> may vary from device to device and may comprise wired, wireless, and/or optical links. Exemplary protocols which may be utilized for communication between the network devices <b>114</b> and the network device <b>116</b> may comprise Ethernet, Wi-Fi, Bluetooth, Zigbee, USB, IEEE 1394, HDMI, and DisplayPort.
0021Protocols and/or network links utilized for communication between the network device <b>116</b> and the server <b>106</b> may comprise wired, wireless, and/or optical links. Exemplary protocols which may be utilized for communication between the network device <b>116</b> and the server <b>106</b> may comprise Ethernet, Wi-Fi, Bluetooth, Zigbee, USB, IEEE 1394, HDMI, and DisplayPort. Additionally, in some embodiments of the invention, the server <b>106</b> may be part of a service provider network and the server <b>106</b> may communicate with the network device <b>116</b> via a DSL or cable television head-end (not shown). In such embodiments of the invention, the network device <b>116</b> may comprise a DSL or CATV modem.
0022In operation, device attributes may be communicated from each of the network devices <b>114</b> to the network device <b>116</b>. The network device <b>116</b> may generate one or more messages comprising the aggregate of the device attributes received from the network devices <b>114</b> and may communicate the message(s) to the server <b>106</b>. In this regard, device attributes from a plurality of network devices <b>114</b> may be consolidated for communication to the server <b>206</b>. In some instances, device attributes for the network device <b>116</b> may additionally be communicated with the attributes associated with the network devices <b>114</b>. In addition to consolidating and forwarding the device attributes, the network device <b>116</b> may store the attributes in a table or other data structure. Furthermore, in various embodiments of the invention, the network device <b>116</b> may be configured based on attributes of the devices <b>114</b>. That is, in addition to aggregating the attributes, the network device <b>116</b> may inspect or determine the attributes and may be configured based on the attributes. Also, in instances that there are additional network devices along the path from the network device <b>116</b> to the server <b>106</b>, one or more of those devices may also be configured based on the communicated aggregate attributes. In some embodiments of the invention, the message(s) may be encrypted and/or otherwise secured for communication to the server <b>206</b>.
0023A device's attributes may comprise, for example, its capabilities, preferences, and/or settings. A device's attributes may comprise, for example, one or more of its: serial number or unique identifier, make, model, hardware configuration, software configuration, operating system, available and/or total memory, available and/or total processing cycles or capabilities, security information and/or settings, battery strength, power settings, and user preferences.
0024In some embodiments of the invention, the device attributes from the devices <b>114</b> may be communicated to the network device <b>116</b> in-band with content delivered from the network device <b>116</b>. For example, the network device <b>114</b><i>c </i>may be communicatively coupled to the network device <b>116</b> via a bi-directional link utilizing a protocol such as Ethernet, and thus content may be communicated to the device <b>114</b><i>c </i>via a downlink channel and device attributes may be communicated to the device <b>116</b> via an upstream channel.
0025In some embodiments of the invention, the device attributes from the devices <b>114</b> may be communicated to the network device <b>116</b> out-of-band with content delivered from the network device <b>116</b>. For example, the network devices <b>114</b><i>a </i>may communicate its device attributes to the network device <b>116</b> via Bluetooth and the network device <b>116</b> may communicate content to the network devices <b>114</b><i>a </i>via an HDMI connection. Notwithstanding, some of the device attributes may be communicated in-band while some of the device attributes may be communicated out-of-band (OOB).
0026The server <b>106</b> may receive the aggregate device attributes and may store the attributes to a database or other data structure. The device attributes may then be utilized to determine services and/or applications to make available to the subnetwork <b>112</b>. Additionally or alternatively, the device attributes may be utilized to determine how to format, encode, or otherwise process content such that the content may be suitable for conveyance to the devices <b>114</b> via the device <b>116</b>. For example, device attributes associated with the network device <b>114</b><i>a </i>may indicate that it is suited for low resolution video and thus the server <b>106</b> may transcode higher resolution video to a lower resolution prior to transmitting the video destined for the device <b>114</b><i>a</i>. For another example, the device attributes may indicate coding and/or decoding hardware and/or software utilized by a device <b>114</b> and the server <b>106</b> may encode content accordingly.
0027In an exemplary embodiment of the invention, the networking devices <b>114</b> may each request, for example, a multimedia stream from the server <b>106</b> but each of the network devices <b>114</b>, as indicated by the received device attributes, may have different multimedia processing capabilities. Accordingly, the server <b>106</b> may be operable to generate a scalable coded datastream comprising a plurality of subset datastreams. In this regard, a subset datastream may be generated by dropping portions of a datastream. For example, packets may be dropped from an MPEG datastream to generate a subset datastream. The subset datastream may have lower temporal resolution, spatial resolution, and/or quality compared to the original MPEG datastream. Which of the plurality of subset datastreams are delivered to each of the devices <b>114</b><i>a</i>, <b>114</b><i>b</i>, and <b>114</b><i>c </i>may be determined based on the device attributes associated with network device <b>114</b><i>a</i>, <b>114</b><i>b</i>, and <b>114</b><i>c</i>, respectively. In some embodiments of the invention, the network device <b>116</b> may further process data for delivery to one or more of the network devices <b>114</b>.
0028In another exemplary embodiment of the invention, it may be determined that one or more attributes are common among two or more of the devices <b>114</b>. Consequently, the content to be delivered to the subnetwork <b>112</b> may be customized based on the shared attributes. Additionally, the server <b>106</b>, the network device <b>116</b>, and/or any other network devices along the path between the server <b>106</b> and the network device <b>116</b>, may be configured based on the shared attributes. That is to say, if the network devices <b>114</b> have widely differing attributes, it may be difficult to optimize the content and/or network path for delivery of content to the devices. However, when the devices <b>114</b> share attributes, it may be possible to customize the data and/or the network configuration to optimize delivery of content based on the shared attributes.
0029Although a single server <b>206</b> is utilized for illustrative purposes in <figref idref="DRAWINGS">FIG. 1</figref>, one or more other network devices may receive the aggregate device attributes and utilized it to manage the delivery of content to the devices <b>114</b>.
0030<figref idref="DRAWINGS">FIG. 2</figref> is a diagram illustrating aggregation and communication of device attributes, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 2</figref>, there is shown the network devices <b>114</b> and the network device <b>116</b> described with respect to <figref idref="DRAWINGS">FIG. 1</figref>. Also shown in <figref idref="DRAWINGS">FIG. 2</figref> are exemplary messages <b>202</b> and <b>208</b> for exchanging device attributes.
0031Each of the messages <b>202</b><i>a </i>may comprise a field <b>204</b> identifying a device associated with the message <b>202</b> and a field <b>206</b> comprising other device attributes. The field <b>204</b> may comprise, for example, a serial number or other information identifying the specific device <b>114</b>, and/or may comprise make, model, or other information that generally identifies the device <b>114</b>. In this regard, the general information may identify, for example, a category or class of devices to which the device <b>114</b> belongs. The field <b>206</b> may comprise, for example, hardware configuration, software configuration, power settings, operating system, and/or other attributes of the device, or device class/category, identified by the corresponding field <b>204</b>. The messages <b>202</b><i>a </i>may be exchanged utilizing a dedicated protocol, or may be encapsulated in packets utilized natively on the link over which they are communicated. For example, the messages <b>202</b> may be inserted in the payload of Ethernet packets. In another example, the attributes may be conveyed in a header or a reserved field of a packet.
0032The message <b>208</b> may comprise fields <b>210</b> and <b>212</b>. The field <b>210</b> may identify the network devices <b>114</b> which provided device attributes to the network device <b>116</b>. The field <b>210</b> may comprise, for example, a serial number or other information identifying the specific devices <b>114</b>, and/or may comprise make, model, or other information that generally identifies the devices <b>114</b>. In this regard, the general information may identify, for example, a category or class of devices to which the devices <b>114</b> belong. The field <b>212</b> may comprise, for example, hardware configuration, software configuration, power settings, operating system, and/or other attributes of the device, or device class/category, identified by the corresponding field <b>210</b>.
0033In operation, the network devices <b>114</b><i>a</i>, <b>114</b><i>b</i>, and <b>114</b><i>c </i>may send the messages <b>202</b><i>a</i>, <b>202</b><i>b</i>, and <b>202</b><i>c</i>, respectively, to the network device <b>116</b>. The network device <b>116</b> may extract the device attributes from the messages <b>202</b> and generate a message <b>208</b> comprising the attributes extracted from the messages <b>202</b>. In various embodiments of the invention, the message <b>208</b> may be secured, encoded, scrambled or otherwise processed such that only a designated destination device can decipher the contents of the message. In regards to security the message <b>208</b> may be encrypted, scrambled, and/or securely communicated utilizing protocols such as MACSec and IPSec.
0034The server <b>206</b> may receive the message <b>208</b> and extract the identification information and/or the other device attributes associated with the network devices <b>114</b>. The device attributes may then be stored in a database or other data structure. The attributes stored in the data structure may be utilized to determine which services and/or content to send or make available to a particular network and/or network device. The attributes stored in the data structure may be utilized to configure the server <b>106</b>, the network device <b>116</b>, and/or other network devices along a path from server <b>106</b> to the network devices <b>114</b>. Additionally or alternatively, in instances when there is content to be transmitted to a particular network device <b>114</b>, the server <b>106</b> may check the database to determine how to format, encode, secure, or otherwise process the content prior to transmitting the content.
0035The embodiment in <figref idref="DRAWINGS">FIG. 2</figref> is merely an example for illustration and is not exhaustive. For example, in other embodiments of the invention, device attributes may be communicate in a single field or in more than two fields. Similarly, device attributes may be transmitted in multiple messages. For example, the devices <b>114</b> may not communicate any identification field and thus the attributes of the devices may be limited
0036<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating multiple levels of aggregation of device attributes, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 3</figref>, there is shown networks <b>310</b><sub>1</sub>, <b>310</b><sub>2</sub>, <b>310</b><sub>3</sub>, and <b>310</b><sub>3</sub>.
0037Each of the networks <b>310</b><sub>2</sub>, <b>310</b><sub>3</sub>, and <b>310</b><sub>3 </sub>may comprise one or more network devices such as the network devices <b>14</b> and/or the network device <b>116</b> described with respect to <figref idref="DRAWINGS">FIGS. 1 and 2</figref>. In this regard, the network devices <b>302</b> may be similar to or the same as the network devices <b>114</b> and/or <b>116</b> described with respect to <figref idref="DRAWINGS">FIGS. 1 and 2</figref>. The service provider <b>310</b><sub>1 </sub>may comprise one or more network devices such as the server <b>106</b>, head-ends, or other network devices operable to provide internet connectivity and/or content to network devices <b>302</b>.
0038In operation, the network device <b>302</b><i>a </i>may communicate its device attributes, A, to the network device <b>302</b><i>c </i>and the network device <b>302</b><i>b </i>may communicate its device attributes, B, to the network device <b>302</b><i>c</i>. The network device <b>302</b><i>c </i>may comprise an access point device. The network device <b>302</b><i>c </i>may generate a message comprising the attributes ‘A’, the attributes B, and its own device attributes, C. In some embodiments of the invention, the device <b>302</b><i>b </i>may also store the attributes B and C locally. In some embodiments of the invention, the device <b>302</b><i>b </i>may be configured based on the attributes B and C. The network device <b>302</b><i>c </i>may encrypt or otherwise process the message for communication to the network device <b>302</b><i>g </i>and then send the attributes to the network device <b>302</b><i>g</i>, which may comprise an access point device. In some embodiments of the invention, the network device <b>302</b><i>g </i>may store a copy of the attributes A, B, and C locally.
0039Similarly, the network device <b>302</b><i>d </i>may communicate its device attributes, D, to the network device <b>302</b><i>f </i>and the network device <b>302</b><i>e </i>may communicate its device attributes, E, to the network device <b>302</b><i>f</i>. The network device <b>302</b><i>f </i>may comprise an access point device. The network device <b>302</b><i>f </i>may generate a message comprising the attributes D, the attributes E, and its own device attributes, depicted as F. In some embodiments of the invention, the device <b>302</b><i>b </i>may also store the attributes D and E locally. In some embodiments of the invention, the device <b>302</b><i>f </i>may be configured based on the attributes D and E. The network device <b>302</b><i>f </i>may encrypt or otherwise process the message for communication to the network device <b>302</b><i>g </i>and then send the attributes to the network device <b>302</b><i>g. </i>
0040The network device <b>302</b><i>g </i>may process the received messages to extract the attributes A, B, C, D, E, F and may generate a message comprising A, B, C, D, E, F, and its own device attributes G. The generated message may be formatted, encoded, and/or secured for communication to one or more devices in the service provider <b>310</b><sub>1 </sub>and may be communicated to the network <b>310</b><sub>1</sub>. Exemplary formatting and/or encoding of content may comprise, for example, up-sampling, down-sampling, scrambling, unscrambling, compressing, decompressing, and/or transcoding. In some embodiments of the invention, the device <b>302</b><i>g </i>may also store the attributes A, B, C, D, E, F locally. In some embodiments of the invention, the device <b>302</b><i>g </i>may be configured based on the attributes A, B, C, D, E, and F.
0041Subsequent to aggregation of the device attributes, one or more of the service provider <b>310</b><sub>1</sub>, the device <b>302</b><i>g</i>, the device <b>302</b><i>c</i>, and the devices <b>302</b><i>f </i>may utilize the aggregated attributes to customize delivery of data to the other devices <b>302</b>. For example, the format, resolution, compression, encoding, and/or other characteristics of a multimedia stream transmitted by the service provider <b>310</b><sub>1</sub>, the device <b>302</b><i>g</i>, the device <b>302</b><i>c</i>, and/or the devices <b>302</b><i>f </i>may be formatted based on the aggregated attributes.
0042<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart illustrating exemplary steps for aggregating and communicating device attributes, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 4</figref>, subsequent to step <b>404</b>, the exemplary steps may advance to step <b>404</b>. In step <b>404</b>, a first network device may receive device attributes one or more second devices, if any, that are further, in terms of number of network hops, from a service provider than the first network device. The service provider may comprise, for example, the server <b>106</b> and/or other devices such as the network <b>114</b> and/or <b>116</b>. Subsequent to step <b>404</b>, the exemplary steps may advance to step <b>406</b>.
0043In step <b>406</b>, the first network device may generate a message comprising the received device attributes as well as its own device attributes. The message may be encoded, encrypted, and/or otherwise processed for communication. Additionally, in some embodiments of the invention, the first network device may be configured based on the received device attributes. Subsequent to step <b>406</b>, the exemplary steps may advance to step <b>408</b>.
0044In step <b>408</b>, the message generated in step <b>406</b> may be communicated to one or more third network devices, where the third network device(s) either reside in the service provider or are closer, in terms of number of network hops, to the service provider. In this regard, the message may be communicated securely utilizing, for example, IPSec or MACsec. Subsequent to step <b>408</b>, the exemplary steps may advance to step <b>410</b>.
0045In step <b>410</b>, in instances that the third network devices do not reside within the domain of the service provider's <b>310</b><sub>1</sub>—the ultimate destination of the device attributes—then the exemplary steps may return to step <b>404</b>. In instances that the third network device(s) do reside in the domain of the service provider <b>310</b><sub>1 </sub>the exemplary steps may advance to step <b>412</b>.
0046In step <b>412</b>, the one or more third network devices within the domain of the service provider <b>310</b><sub>1 </sub>may decode, decrypt, descramble, and/or otherwise process the received message(s) comprising the device attributes to extract the device attributes. The third network device(s) may store the device attributes to memory. Subsequently, the service provider <b>310</b><sub>1 </sub>may utilize the device attributes to determine which content, applications, and/or services to make available to a particular network device. In this regard, the service provider <b>3101</b> may be configured based on the attributes. Additionally and/or alternatively, the third network device may encode, format, or otherwise process content prior to transmission such that the content is customized for the device to which it is transmitted.
0047<figref idref="DRAWINGS">FIG. 5</figref> is a flow chart illustrating delivery of customized data based on aggregated device attributes, in accordance with an embodiment of the invention. Referring to <figref idref="DRAWINGS">FIG. 5</figref>, the exemplary steps may begin with step <b>502</b>. In step <b>502</b>, a service provider <b>310</b><sub>1 </sub>may receive one or more messages comprising device attributes. Subsequent to step <b>502</b>, the exemplary steps may advance to step <b>504</b>. In step <b>504</b>, the service provider <b>310</b><sub>1 </sub>may decode, decrypt, and/or otherwise process the received message(s) comprising the device attributes to extract the device attributes. The service provider <b>310</b><sub>1 </sub>may store the device attributes to memory. In this regard, the service provider <b>310</b><sub>1 </sub>may comprise a database which may be updated upon received the device attributes. Subsequent to step <b>504</b>, the exemplary steps may advance to step <b>506</b>.
0048In step <b>506</b>, the service provider <b>310</b><sub>1 </sub>may receive a request for content from a remote networking device and the service provider <b>310</b><sub>1 </sub>may prepare to transmit the content to the requesting device. In this regard, the service provider <b>310</b><sub>1 </sub>may look up the requesting device's attributes in the database and determine how to process the data such that the data may be customized based on exemplary factors comprising, the capabilities, attributes, and/or configuration of the requesting device. Subsequent to step <b>506</b>, the exemplary steps may advance to step <b>508</b> and transmit the customized data.
0049Various aspects of a method and system for customized data delivery via device attributes aggregation are provided. In an exemplary embodiment of the invention, a first network device <b>116</b> may receive device attributes from a plurality of devices <b>114</b> that are communicatively coupled to the first network device <b>116</b>. The first network device <b>116</b> may communicate the aggregate device attributes to a source network device, such as server <b>106</b> (<figref idref="DRAWINGS">FIG. 1</figref>) and/or a device of a service provider <b>310</b><sub>1</sub>. The first network device <b>116</b> customized from the source network device <b>106</b>, wherein the customization is based on the aggregate device attributes. The first network device <b>116</b> may communicate the customized content to the plurality of devices <b>114</b>. The first network device <b>116</b> may comprise one or more of a set-top box, a wired access point, and/or wireless access point. The device attributes of each of the plurality of network devices may comprise settings, capabilities, and/or user preferences. The device attributes of each of the plurality of network devices may comprise one or more of: a serial number or unique identifier, a manufacturer identifier, a model identifier, a hardware configuration, a software configuration, an operating system identifier, available and/or total memory, available and/or total processing cycles, security information, battery level, and/or power settings.
0050The communication of the aggregate device attributes may be secured utilizing IPSec and/or MACsec protocols. The device attributes may be received by the first network device <b>116</b> via an out-of-band channel. The device attributes may be received by the first network device <b>116</b> device via an optical communication link. The content may be customized by one or more of: compressing, decompressing, down-sampling, and/or up-sampling. The customized content may be delivered from the first network device <b>116</b> to the plurality of devices based on the aggregate device attributes. The first network device <b>116</b> may be configured based on the aggregate device attributes. The source network device <b>106</b> may be configured based on the aggregate device attributes. One or more network devices along a network path between the first network device <b>116</b> and the source network device <b>106</b> may be configured based on the aggregate device attributes.
0051Another embodiment of the invention may provide a machine and/or computer readable storage and/or medium, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform the steps as described herein for customized data delivery via device attributes aggregation.
0052Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
0053The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
0054While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.
Contents6
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8671099B2 | Cited by | United States of America | Applicant |
| US9672273B2 | Cited by | United States of America | Applicant |
| US11363679B2 | Cited by | United States of America | Applicant |
| US2012233239A1 | Cited by | United States of America | Pre-grant |
| US12082311B2 | Cited by | United States of America | Applicant |
| US2017013062A1 | Cited by | United States of America | Search report |
| US11019149B2 | Cited by | United States of America | Search report |
| WO2013102927A2 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| US2012198020A1 | Cited by | United States of America | Pre-grant |
| US9692794B2 | Cited by | United States of America | Search report |
| US2016285952A1 | Cited by | United States of America | Pre-grant |
| US2020081995A1 | Cited by | United States of America | Search report |
| CN103858409A | Cited by | China | Search report |
| US10838915B2 | Cited by | United States of America | Search report |
| US2014250234A1 | Cited by | United States of America | Pre-grant |
| US9684708B2 | Cited by | United States of America | Applicant |
| US2017292638A1 | Cited by | United States of America | Search report |
| US10548185B2 | Cited by | United States of America | Search report |
| US10303526B2 | Cited by | United States of America | Search report |
| US9584570B2 | Cited by | United States of America | Search report |
| US2015281301A1 | Cited by | United States of America | Pre-grant |
| US2004139233A1 | Cites | United States of America | Pre-grant |
| US2005231641A1 | Cites | United States of America | Pre-grant |
| US2006218480A1 | Cites | United States of America | Pre-grant |
| US2006224525A1 | Cites | United States of America | Pre-grant |
| US2006230309A1 | Cites | United States of America | Pre-grant |
| US2007109935A1 | Cites | United States of America | Pre-grant |
| US2007192486A1 | Cites | United States of America | Pre-grant |
| US2008208607A1 | Cites | United States of America | Pre-grant |
| US5519438A | Cites | United States of America | Pre-grant |
| US7590750B2 | Cites | United States of America | Pre-grant |
18 members in 6 offices
Priority claims1
| Document | Office | Kind | Date |
|---|---|---|---|
| 22838509 | United States of America | P |
Members18
| Document | Office | Kind | |
|---|---|---|---|
| CA2739445A1 | Canada | A1 | |
| WO2010040147A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2010099649A1 | United States of America | A1 | |
| WO2010040147A9 | World Intellectual Property Organization (WIPO) | A9 | |
| WO2010040147A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2278774A2 | European Patent Office (EPO) | A2 | |
| US2011022733A1 | United States of America | A1 | |
| CN101964722A | China | A | |
| EP2350112A2 | European Patent Office (EPO) | A2 | |
| TW201136263A | Taiwan Province of China | A | |
| EP2278774A3 | European Patent Office (EPO) | A3 | |
| EP2350112A4 | European Patent Office (EPO) | A4 | |
| US8431521B2 | United States of America | B2 | |
| US2013216479A1 | United States of America | A1 | |
| TWI455545B | Taiwan Province of China | B | |
| US8862766B2 | United States of America | B2 | |
| EP2278774B1 | European Patent Office (EPO) | B1 | |
| CN106331087A | China | A |
59 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Response to Reasons for AllowanceREAS | REAS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail PUB Notice of non-compliant IDSMM327-B | MM327-B | |
| PUB Notice of non-compliant IDSM327-B | M327-B | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Interview Summary - Examiner InitiatedEXIE | EXIE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
13 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20110022733
- Application
- 12616607
Titles
- English
- CUSTOMIZED DATA DELIVERY AND NETWORK CONFIGURATION VIA AGGREGATION OF DEVICE ATTRIBUTES
Patent term adjustment
- A delay
- +804 daysthe office missed an examination deadline
- B delay
- +175 dayspendency past three years
- Applicant delay
- −149 days
- Net adjustment
- 830 days
Classification
- CPC, 3
- H04L67/303
- H04L67/2833
- H04L67/306
- IPC, 1
- G06F15 16
- USPC, 1
- 709247000