Patent Grant
12047659
Embodiments of the invention generally relate to the field of networking and secure data transfer over ad-hoc networks.
The digital data transferred over the Internet is growing rapidly, driven primarily by video. Downloaded video, Video on Demand (VOD), live video (both broadcast video and consumer video), interactive video (e.g. video conferencing, video telephony, and video gaming) are all growing in popularity.
Networking companies, such as cellular and cable companies are investing heavily in everything from optical fiber to next generation millimeter wave cellular (e.g. 5G) technology. However, there are often diminishing returns on such investments for these companies as the “price per bit” has fallen rapidly due to heavy competition. The so called “last mile” problem—the data transfer between the network data center (e.g., Internet Service Provider (ISP), cellar network) and customer's device or local area network (LAN)—is by far the most expensive and difficult of the networking challenges.
For video specifically, there are three challenging metrics for data transfer performance directly related to Quality of Service (QoS) and Quality of Experience (QoE). First, especially for interactive video and live video, reducing the latency (time from source to destination) is critical for a pleasant user experience. With high latency, people in a video conference, for example, often talk over each other creating awkward and unnatural communication.
Second, the continuity of transfer is critical, especially for VOD, live and interactive video. Pauses and the dreaded buffering symbol are annoying to the viewer. Since a large amount of data needs to be transferred at a relatively constant rate for the duration of the video, any interruption or diminution in bandwidth will cause problems. Most approaches to mitigating the effects of changing bandwidth involve adapting the size and quality of the video data dynamically to match fluctuations in bandwidth. Quality selective protocols (e.g., Dynamic Adaptive Streaming over HTTP or MPEG-DASH) are used. This reduces the bandwidth needed to transfer the video at the cost of video quality. However, it does not solve network drop out when there is no data stream at all.
Third, simply put, video data is very large. This requires a lot of bandwidth and computation at the source, at strategic nodes throughout the networks, and, worst of all, at the “last mile”. In many places and/or at popular times for streaming such bandwidth is limited. And improving bandwidth for all places, and for peak time, is hugely expensive. Witness the extremely slow roll out of the new 5G cellular technology.
One increasingly common technique to help mitigate these problems is Content Delivery Networks that are sometimes called Content Distribution Networks (CDN). CDNs are geographically distributed networks of proxy servers and data centers at the edge of the network. Rather than video data being served from a single server or data center at one location in the world, the video is distributed (copied) from the source server to a number of CDN edge nodes strategically placed around the globe. The data copies are either preloaded into the CDN cache as desired or transferred when a CDN edge node receives the first request.
Requests for data from client devices are redirected to the physically most appropriate CDN edge node. If the CDN edge node has the data cached the response is quick with relatively low latency. If not, the CDN edge node requests the data from either another CDN edge node or the source server. The data is delivered to the client device and cached at the CDN edge node.
For a content provider with a central repository of content, there are two advantages. First, since the content provider's source server or data center only has to serve a few (maybe hundreds) CDN edge nodes, rather than potentially millions of client requests, the burden on the source server and store are less. Second, in many cases the transfer between the source server and the CDN edge nodes is achieved with high bandwidth, predictable, even dedicated, network connections, reducing the latency from the source server to the edge nodes. For example, Amazon Web Services, AWS, uses dedicated high bandwidth connections between its regional data centers and the AWS CloudFront CDN service. (Note that the CDN service can be independent of the content server and store service. And high bandwidth connections between a source server and CDN edge data centers are not always available. In fact, using multiple CDN services, e.g. AWS CloudFront and Akamai, for better coverage is an increasing popular approach.)
Optimizing CDN technology requires a large number of parameters and strategies to achieve high performance. The caching strategy (what should be saved at the edge and for how long) is crucial and dependent on context. Artificial Intelligence methods can be used to decide what and where to pre-position data or to let the data be cached at the node only after the first client request. The proxy mapping by location may be modified to include bandwidth, edge node utilization, and data availability. CDN technologies are a rapidly evolving field with an ever increasing number companies (e.g. Akamai, Amazon Web Services CloudFront) expanding their edge networks.
CDNs are good for reducing traffic and latency from the content source server. But they are still limited with respect to regional latency and bandwidth. Some companies that value low latency above all else are placing dedicated edge servers right in the Point of Presence (PoP) of the Internet Service Provider (ISP) that connects the clients to the Internet. This might work with large ISPs such as Comcast Xfinity and ATT. However, there are hundreds, maybe thousands, of smaller ISPs so full coverage with dedicated edge servers does not scale well.
A special network device and method for using the same are described. In one embodiment, the device is for use in a network arrangement comprising a plurality of access points that are part of one or more existing networks and operable to individually address and communicate with each other to form a local area network (LAN) to transfer data between two or more of the plurality of access points using point-to-point links independent of their function in the one or more first existing networks, and the client device comprises: a first communication interface; a second wireless communication interface; a cache to store content; and connection logic coupled to the first and second communication interfaces, and the cache, to initiate a wireless connection with one or more access points in the plurality of access points by itself using the second wireless communication interface to transfer desired content cached by individual access points of the plurality of access points, the wireless connection used to request at least one of the one or more of the plurality of access points to transfer the desired content via one or more direct point-to-point transfers with one or more access points in the plurality of access points.
The present invention will be understood more fully from the detailed description given below and from the accompanying drawings of various embodiments of the invention, which, however, should not be taken to limit the invention to the specific embodiments, but are for explanation and understanding only.
In the following description, numerous details are set forth to provide a more thorough explanation of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention.
Some portions of the detailed descriptions which follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or “networking” or the like, refer to the action and processes of a computer system(s), or similar electronic computing device(s), that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The present invention also relates to apparatus for performing the operations herein. This apparatus may be specifically constructed for the required purposes, or it may be comprised of a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Similarly, general purpose networking equipment may be employed including, but not limited to, modems, routers, Wi-Fi access points, Bluetooth, and other wired and wireless networking hardware systems.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.
Embodiments of the present invention are predicated on a number of existing Special Network Devices (SND) Wi-Fi access points physically close enough with each other to communicate directly (e.g., within about 50 meters). These are the nodes in a Special Local Area Network (SLAN).
These SNDs (via the embodiments described below) connect to one another, forming a SLAN independent of any connection to the Internet or other private network. These SNDs intelligently cache data that passes through (or is proactively requested by the SND). Additionally, in some embodiments, the SND has access to data on connected client devices.
Simultaneously, these SNDs also serve the traditional function of connecting wireless clients to the Internet or other private networks. However, now the wireless client can also benefit from the collective caching of the SLAN. If a data request from a wireless client can be served from the data cached in the SLAN, that access is generally faster and has no impact on (and does not suffer from) Internet traffic.
Embodiments of the present invention have one or more advantages. First, embodiments of the invention help to improve network performance, especially within the so called “last mile”—the connection between the ISP or private network (a conventional network independent of the Internet) and the local device—in certain situations. Embodiments of the invention have the potential to reduce bandwidth problems enabling better performance for video and other large data transfers and perhaps also improve continuity and reduce latency.
Second, embodiments of the invention create an entirely new layer in this data caching approach—creating a Special Local Area Networks (SLAN) and caching right at the Wi-Fi access point physically located in a home or business. While many or all of these nodes are also connected to a central network, or networks (e.g. the Internet via an ISP), the network is able to transfer data between the networked nodes independently of that central network.
In highly populated areas, such as business districts and urban and suburban neighborhoods, there is often multiple Wi-Fi access points (or hotspots or IEEE 802.11x “Wi-Fi” networks) that are within range and broadcasting their name (Service Set Identifier, SSID). Most of these Wi-Fi access points require a password to authenticate that the client is allowed access. In one embodiment, the client device sees these Wi-Fi access points and the Wi-Fi access points themselves are close enough to connect to each other.
In one embodiment, all the Wi-Fi access points that are capable of the functionality described below and that are physically located close enough to connect to each other, do so forming a SLAN.
In one embodiment, these Wi-Fi access point devices are called Special Network Devices (SNDs), and the functionality of a SND includes caching hardware and software for handling data; discovering other SNDs; networking with other SNDs forming a SLAN; message passing and responding within a SLAN; data transfer within a SLAN; as well as functioning as a traditional Wi-Fi access point for client devices and communicating with the ISP or private network. In some embodiments, this functionality is achieved with conventional computer running custom software connected to a traditional Wi-Fi access point device. In other embodiments, integrated SND hardware with these specific capabilities is employed.
In one embodiment, the networking between SNDs is embodied in a sideband signal (a dedicated separate Wi-Fi signal for this purpose). For security, in one embodiment, this sideband signal is limited to SNDs by hardware and/or software authentication. In other embodiments, the SND connects via switching between Wi-Fi signals or other wireless and/or wired communication functionality.
In one embodiment, one SND may be connected to multiple other SNDs forming a SLAN. However, these are not closed mesh networks (e.g. not a private network) since the SNDs, in one embodiment can self-join and self-organize into a network. In one embodiment, one SND is capable of connecting directly to N other SNDs. Those N SNDs are not necessarily all connected to each other. This first SND acts as a bridge node, or repeater, or more specifically a Wi-Fi repeater, between the other SNDs that are not directly connected. Likewise, some of the N other SNDs might be connected to SNDs that the first SND is not. Thus, those SNDs act as bridges, or Wi-Fi repeaters, between these SNDs. Messaging and data is transmitted by hopping between these nodes. Theoretically, this network could extend to the physically furthest SND that can be connected to at least one of the others, though the costs for multiple hops between nodes in a network may degrade performance.
In one embodiment, the SNDs cache large files or objects locally, especially multimedia content, based on heuristic and learned algorithms. In one embodiment, these algorithms are initially derived from those employed with CDN and other caching strategies, and are expected to evolve for the characteristics of a given SLAN. A common example of a caching strategy is the “least accessed” principle. As data is accessed, timestamps are updated. When memory is needed for new data the least accessed data is deleted first.
With an arrangement of SNDs, when a client requests large data, the SLAN is queried to see if that data is available locally, and if so, the client request is served locally. Caching files or objects at the Wi-Fi access point level of the network has many of the same bandwidth and latency reduction advantages as CDNs and PoPs. It would certainly help with popular live broadcasts and on-demand binging, especially during the network congested evening hours. (Note that the advantage of embodiments of the invention for interactive video which requires low latency is not well known.)
Embodiments of the invention also facilitate streaming video. One SND can receive streaming data and transfer that data throughout the SLAN for several clients, reducing the burden on the ISP, Internet, and/or private network. There are practical limitations in performance, however. For example, SLAN nodes (SNDs) connected via Wi-Fi repeaters would require retransmission of packets, creating some amount of congestion in the local spectrum. Nevertheless, embodiments of the invention improve the performance of streaming popular content.
The description and figures below describe the steps to create such a network and deliver data, especially large data such as video, across it. In one embodiment, these steps include:
The description of embodiments of the invention characterizes a SLAN created by replacing existing, or adding new, Wi-Fi access points with SND capable hardware and software. It assumes deriving the benefits from the existing topology of these points, e.g. at homes, at coffee shops, at work, at airports. However, one skilled in the art could imagine placing these devices in strategic locations to “complete” the SLAN and provide just this type of “last foot” networking benefit. In other words, embodiments of the invention include both ad-hoc creation and designed creation of this SLAN.
Also, embodiments of the invention are not limited to the ad-hoc creation of these networks to (relatively) physically fixed Wi-Fi access points. One skilled in the art in view of the present disclosure can imagine these networks being spontaneously created with mobile devices that may also have the required functionality.
Description of CDN, Pop, and LANs with Wi-Fi Access Points
Traditional networking partitions the data into packets. Each packet is sent to an Internet Node 102 and is repeated to another node and so on along a Data Packet Path 106 until the packet is received by an Internet Service Provider (ISP) 103 and then the Client Device 105. The path of the data packet could require multiple hops (i.e. passing through several Internet Nodes 102). The Internet Nodes 102 can be all over, including all over the globe. Furthermore, each packet in a data transfer might take a different path. In one embodiment, the path depends on sophisticated algorithms, known to those skilled in the art, that depend on factors such as, but not limited to, bandwidth, availability, and connectivity at the nodes. While these algorithms attempt to reduce, and potentially minimize, the packet path, the Source Server 101 cannot predict, or demand, low latency or sufficient bandwidth. Also in this model, the Source Sever 101 itself could be a bottleneck if there is a great demand for its content.
The main advantage to using CDNs is the data propagation to the geographical edge of the network. The content is closer and therefore faster, to get to the client. Data propagation of static content takes time though. In many cases, data is propagated (proactively pre-loaded or updated) before the first access.
With effective caching and prediction strategies, CDNs significantly reduce bandwidth stress on the source servers and latency to the client. Now the Data Packet Path 108 is significantly shorter and, perhaps, more predictable. This is the most common method that large video content providers use today.
Yet high latency and bandwidth demands persist even with CDNs. So a few companies like Twitch, Amazon's video game streaming service, have moved servers even closer to the edge by installing them in some ISP's Point of Presence (usually last node before the client).
Embodiments of the invention have two additive advantages that can supplement any of these networking approaches. First, it creates a local area network with data caching even closer to the client device. Second, serving requests for data that are cached locally can be executed without involving the Internet, or even the ISP.
Note that this disclosure will use the present state-of-the-art method of wirelessly connecting popularly called Wi-Fi (a trademarked phrase representing the family of IEEE 802.11x standards). While Wi-Fi is one method for wireless networking, one skilled in the art can imagine successor technologies (wired, wireless, or contact) being used for the purposes of embodiments of the invention. Furthermore, there are other contemporary wireless technologies (e.g., Bluetooth, Near Field Communication, etc.) that could be used. Finally, embodiments of the invention could also work with a mixture of technologies for networking, both wired and wireless.
For descriptive purposes, the term “Wi-Fi access point” is used to refer to a device that is connected on one side to the Internet (e.g. via an ISP) and on the other side to client devices via Wi-Fi. However, the term “access point” is a more general description that implies network access regardless of the wireless or wired protocol. In one embodiment, an access point is any last point on the edge of a network that enables client devices to connect directly. Note that a single physical device can offer several Wi-Fi signals. Also note that a single physical device can have multiple Wi-Fi signals each with a different Service Set Identifier (SSID).
A Wi-Fi repeater is a Wi-Fi access point that repeats packets from other Wi-Fi access points. In one embodiment, Wi-Fi repeaters are used to bridge communication between a client device and the access point with a connection to a modem (and the ISP or private network), thereby “extending” the Wi-Fi range. In one embodiment, Wi-Fi repeaters use the same SSID as the originating Wi-Fi access point.
A single point in a network of computing devices is called a node. Traditionally, Wi-Fi access points or Wi-Fi repeaters are the last node in the network before the client device.
Content is data that is generally large and has some persistence value (i.e. it is potentially still valuable at a later time). An excellent example of content is video data. Video data tends to be large, may be requested several times, and does not need to be refreshed. Examples of data that is not considered content in this disclosure are metadata describing content, messages passed between devices, request calls, and other API related data. Note that this non-content data can be repeated by SNDs.
Description of Embodiments of a Special Local Area Network (SLAN)
In one embodiment, Special Network Devices (SNDs) connect and interact with each other, thus acting as nodes in the Special Local Area Network (SLAN). The definition of the SLAN for purposes herein is the network created by all of the SNDs that are able to address each other. In one embodiment, the addressing is direct via the Wi-Fi signal. The SLAN can extend beyond the Wi-Fi signal range if there is one, or more, bridge SNDs that can act as Wi-Fi repeaters. Any data packet would “hop” through these bridge SNDs. Conceptually, this network could extend to a great geographical distance with many SNDs if there are bridge SNDs in the physically correct locations.
In
Methods for discovering and connecting between SNDs and creating SLANs are described below. Using methods described below, the SND requests information about all the SNDs on the SLAN. Depending on the embodiment, these connections are described and, in some embodiments, shared using structured lists (such as CSV, JSON, etc.) or using local or global databases (e.g., Graphing Databases, Relational Databases, NoSQL databases, etc.). In other embodiments, the addressing is not shared until there is content found. This is also described below.
Table 1 shows a textual description of the connections between the SNDs in
There are various ways to represent this table in database form, for example node and edge descriptions in a graphical database. With the right representation it is possible to discern how to address all of the SNDs in the SLAN. However, it may not be necessary for the SNDs or a network controller to know this network topology to find or transfer content around the SLAN. This is described below.
Hardware and Software for Embodiments of a SLAN
For descriptive purposes, the term “Special Network Device” (SND) is used to refer herein to a physical (or virtual) device that has all of the functionality to participate in a SLAN. In one embodiment, an SND may or may not have a connection to the Internet via a modem; one or more Wi-Fi signals; data storage capability for caching content and partitions of content; and computational hardware and software sufficient to join the network, search for content, and transfer content. While all of this could be manufactured in a single purpose-built enclosure, it could also be constructed using conventional modems, Wi-Fi access points, and computers. To be clear, in one embodiment, a SND is a traditional Wi-Fi access point with additional hardware and software needed for the SND functionality described herein.
The Main Wi-Fi Signal 305 transmits and receives data via Wi-Fi 308. In one embodiment, Main Wi-Fi signal 305 interacts with a client device. Optionally, Main Wi-Fi Signal 305 uses multiple separate Wi-Fi signals with separate SSIDs. In one embodiment, each of the multiple separate Wi-Fi signals is at different frequencies, e.g., 5.0 GHz and 2.4 GHz. In one embodiment, SNDs behave exactly like conventional Wi-Fi access points for normal requests.
The Connection Compute and Store 302 is the computer or other processing logic (e.g., one or more processors, controllers, execution units, etc.) that controls the SND functions like network discovery, content search, content caching, and controlling the transfer of content and content pieces. In one embodiment, the Connection Compute and Store 302 comprises connection logic. The connection logic comprises hardware (e.g., circuitry, digital logic, etc.), software, firmware, or a combination of all three. In one embodiment, the connection logic is coupled to the first and second communication interfaces (e.g., Wi-Fi and other communication interfaces described above), and a content cache (e.g., 303) to initiate a wireless connection with one or more access points in the plurality of access points by itself using the second wireless communication interface to transfer desired content cached by individual access points of the of the SLAN.
The Content Cache 303 is memory (volatile or non-volatile) where content is accumulated and stored temporarily. The Side Wi-Fi Signal 306 transmits and receives data via the Side Wi-Fi 309 and is dedicated to SLAN traffic. This function is employed in some embodiments, but not others, as is described below.
In some embodiments, an optional Global Positioning System 310 is included in the SND. In one embodiment, the global position is used when evaluating the analytics generated by the SND and SLAN.
In one embodiment, all of this functionality is assembled in a dedicated piece of hardware or is implemented using an off-the-shelf computer, modem, and Wi-Fi access point hardware except where noted herein.
In one embodiment, the Server Software module 407 is a Hyper-Text Transfer Protocol (HTTP) or web server (e.g. Apache HTTP server) and is common in many modem/router/Wi-Fi access point devices. This enables the device to be accessed via protocols like HTTP with settings presented to users as a webpage. Some embodiments use this software for communicating with other SNDs as well as the ISP and clients.
The SND Discovery and Connect module 401 handles the authentication for connecting to other SNDs and enabling other SNDs to connect each other and other devices. In one embodiment, the SND Discovery and Connect module 401 employs a network configuration protocol, such as, for example, but not limited to, Zero Configuration Network or Apple's Bonjour, to query the network for device capabilities, e.g., which devices are capable of SND functionality.
In one embodiment, the SLAN Local DNS Manage module 402 uses a protocol such as multicast Domain Name Server (mDNS), which is part of the Zero Configuration Network protocol, to discover, record, and share the identities of the SND on the SLAN. This is where the description of the network in database form can be (optionally) created and stored (see Table 1).
The SLAN Content Search module 403 searches for content requested by the client device.
The SLAN Content Transfer module 404 transfers and/or repeats packets to affect the transfer of data from the SND in the SLAN where the content is found to the client device.
The SND Content Cache module 405 strategically stores content, or pieces of content, that are passed through the SLAN. The strategy for caching content depends on a number of factors such as the content's novelty in the SLAN, popularity, size, frequency of access, and a number of other factors. Caching algorithms that may be used are known to those skilled in the art. In one embodiment, both heuristics and machine learned caching strategies are employed. The efficacy of the caching strategy is recorded by several metrics which are then used to improve the strategy. That measurement and learning functionality is part of this software module, in some embodiments. In other embodiments, there is a central server that collects the analytics data (see below) and performs the strategic modifications, either in real-time or off-line.
The SND Analytics module 406 reports the metrics for the caching and other information pertinent to the caching strategy, network topology, or even the business model.
The Global Position System module 408 reads and shares the global coordinates of the SND with the SLAN and network controller(s). In one embodiment, this optional component is used for analytics.
In some embodiments, a client device is connected to a traditional Wi-Fi access point and a computer is used to simulate or replicate the functions of an SND. In this case, the client device's software functionality is similar to that of the SND.
Forming a Network of SNDs
In one embodiment, SLANs are formed when at least two SNDs connect to each other. All the SNDs network together in a mesh formation.
There are at least two different types of embodiments in which SNDs discover and join a SLAN. The first type of embodiment is a self-organizing network. The SNDs form a peer-to-peer network using local discovery such as, for example, but not limited to, Zero Configuration Network, Apple's Bonjour, multicast DNS, and other similar protocols.
In an example embodiment of the network organizing process, referring to
Once connected, the SND can interact with the other devices, at first, via a system like Apple's Bonjour. The SND creates a name for it (assuring that it is unique by querying the network) and publishes that name for the other SNDs on the local network 515. In one embodiment, the SND uses its unique Media Access Control (MAC) address for a name. The SND can query for the service records (e.g., capabilities, names, addresses, ports, etc.) of all the other devices on the SLAN 520. This will cause one or more of the SNDs on the network to respond with these records 523. In many embodiments, there are multicast DNS caching schemes that reduce the number of SNDs that need to respond. Also, such a request can be used for the other SNDs to update their own records. At this point, the new SND has enough information to formulate its own local records 530.
There are ways that some of the embodiments of this invention might differ from features of standard implementations.
First, in one embodiment, the effective SLAN network only includes SNDs so all devices would have the capability when queried. In some embodiments, to reduce chatter, the SNDs might have an inherent order (alphabetical by name, numerical by IP address, age by time of connection, etc.) with which to respond. The first on the list responds with the entire record set for the whole network. If that SND does not send a response within some timeout, the second on the list sends it, and so on.
Second, in some embodiments, there is a list of connections in the network that denotes how many hops are required to reach a device is sent. Conversely, a table of information similar to Table 1 is sent to the SNDs in the SLAN.
Another difference in embodiments is that a similar broadcast protocol is used to search for specific content on the network. This is described in greater detail below.
In one embodiment, the SLAN includes a network controller and is a network controller assisted network. In one embodiment, the network controller is a typical network server, usually located on the Internet or private network, often at the ISP. This network controller has the capability for receiving, storing, and delivering information about SLAN locations, SSIDs, authentication passwords, and the pertinent information for forming the network. In one embodiment, the network controller also records the mapping of cached content and control caching decision. This is described below.
In one embodiment, a SND communicates with a network controller to find other SNDs and to join the SLAN. In one embodiment, this server is located in a specific SND or permanently attached client device that is designated as the local server. In this case, it is still necessary to access the server via the ISP, Internet, or private network to establish the first connection. In other embodiments, this server is located at the ISP or elsewhere in the Internet or private server.
With some embodiments, the network controller performs the role of DNS as well as secure password source. Referring to
SLAN Addressing and Multiple Hops
In order for the SNDs to communicate with each other, in one embodiment, they have unique identifiers (such as Media Access Control address or MAC address) and domain names (or IP addresses assigned using mDNS). The description above shows how these names are assigned, in some embodiments via peer-to-peer methodology with the list stored locally and in other embodiments with the assignment and list handled by a remote server.
With the DNS or SLAN network list, any SND is able to pass messages and/or content directly with each other using traditional protocols such as, for example, File Transfer Protocol (FTP) and HTTP. In some embodiments, however, there is a difference between this arrangement and a regular network. The SNDs in these embodiments are aware of how many (minimum) hops away another SND is. Thus, it is possible for an SND to evaluate whether it is more efficient to request content from a distant, multiple hop SND or directly from the Internet. For the purposes of this disclosure, this is called multi-hop access for multiple hops (Wi-Fi repeater) versus no hops.
Note that while Wi-Fi repeater technology is useful for extending the physical range of a Wi-Fi access point, it does so by repeating the packet and using more time and more wireless bandwidth. This should be considered dynamically when judging whether to request content that requires multi-hop access.
Data Discovery and Search
In one embodiment, when a client requests to access content (e.g. play a movie) the first step is authenticating that the client has permission (e.g. has paid for the movie). That authentication process is beyond the scope of this disclosure; however it can be assumed that either there is an interaction with a paywall server or the rule-based player technology such as described in U.S. Pat. No. 8,751,795 B2, “Secure Transfer and Tracking of Data Using Removable Non-volatile Memory Devices”, incorporated herein by reference, is used. In one embodiment, at a minimum, the request has a global unique identifier (GUID) for the session and a content identifier for the content.
To find content, or all the pieces of content, multiple types of embodiments, such as peer-to-peer and network controller, may be employed.
In peer-to-peer embodiments, the SND connected to the requesting client broadcasts the request to the SLAN similar to the Zero Configuration Network protocol. Any SND node in the network with the entire content, or a piece of the content (e.g., fragments of the content identified with metadata that enables reconstruction), responds to the request describing the content.
Note that in these embodiments, no network list is necessary. The Zero Configuration Network protocol is extended to include searching on specific content. In this case, it is unnecessary to know either the topology or address list of the SLAN ahead of time. The response to the request includes the service record and ultimately the address of the SND with the requested content.
In one embodiment, the Apple Bonjour protocol is used to search for content on the network. The relationship between Internet Protocol (IP) address and Apple Bonjour Service Record is described in publically available the Apple Bonjour developer's documentation (https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/NetServices/Introduction.html#//apple_ref/doc/uid/TP40002445-SW 1). Using the API library such as Apple's NSNetService, an SND can publish the services available. In this case, the services are pieces of content. In one embodiment, the name of the service type is slan-content. TCP and the name of a give service is <content-id>.
In an alternate embodiment, the individual SND nodes are queried directly (one by one) using the local domain name stored on the requesting SND. In an alternate embodiment, the local domain names for the SND nodes are stored on a server (as described above).
All responses are passed back the originating SND with the description of the content piece available and the addressing required to access it.
In another embodiment, a network controller system similar to BitTorrent is used. BitTorrent is a peer-to-peer content delivery system where content, or pieces of content, are stored on client devices. The Internet Protocol address and location of content and content pieces are listed on a network controller, called a Tracker. With BitTorrent, the content or pieces of content can be located in client devices anywhere around the world, called a Swarm. To access the content or piece thereof, the BitTorrent Tracker informs the requesting client of the address(es) for the content and the client requests content directly.
Some embodiments described herein can use the same approach. A network controller accounts for the address and location of content cached on SLAN. When an SND requests content the network controller informs that SND of the address(es) for the cached content in the SLAN and the SND requests content directly.
Embodiments of this invention that use this approach have a few advantages over BitTorrent. First, with BitTorrent the content is often partitioned into pieces specifically to compensate for the unbalance bandwidth offered by many ISPs. That is, the upload bandwidth is often inferior to download bandwidth. If several pieces are requested at the same time, the additive speed of multiple uploads can come closer to matching the requesters download speed. However, with the networking arrangement described herein, the transfer speed between SNDs is more or less balanced. Therefore, fragmenting the content into pieces does not matter in terms of unbalance bandwidth. (There are other reasons to fragment content into pieces. For example, fragmentation might distribute the caching burden and perhaps the local Wi-Fi congestion throughout the SLAN.)
Another advantage over BitTorrent is that the cached content is accessed within the SLAN. There is no need to access the ISP, Internet, or private network. Thus, the content access will be faster and not contribute to ISP, Internet, or private network bandwidth congestion.
Data Transfer
In one embodiment, data transfer is achieved using Internet Protocols routing between the SND nodes in the SLANs. There is no need, in most cases, to route the content through the ISP or other parts of the greater Internet. It is here that the great bandwidth and latency reductions are achieved.
In one embodiment, the SND requests content from another specific SND using a Hypertext Transfer Protocol (HTTP) GET or POST command. The minimum data in the Application Programmer's Interface (API) call is the following:
Request:
Note that the content or pieces of content can be cached on an SND node or on a client device attached to an SND node.
Content partitioning strategies, similar to those employed in BitTorrent (pieces), can reduce the caching burden on single nodes and might also reduce the content transfer burden of those nodes. These strategies are employed when dictated by topology of the network, size and popularity of the content, and other factors that are determined.
In one embodiment, routing between the nodes uses traditional network techniques that optimize data packet paths give topology and current usage. There are a number of networking strategies that can be learned given the topology of the network, usage patterns, and requests underway. Much of the network optimization and content caching algorithms used in LANs and the Internet can be exploited with SLANs.
As described above, in one embodiment, the requesting SND sends a Zero Configuration request for specific content and receives either no response or one or more responses. There are several ways for the requesting SND to determine the best source for transferring the content.
In some embodiments, the requesting SND uses Ping, a known software function, to determine the latency between the requesting SND and the SND or multiple SNDs with the content. The source of the content with the lowest latency (or other factors like bandwidth capabilities) is the SND chosen to transfer the content. In some embodiments, the requesting SND also Pings the ISP, Internet, or private network. If that Ping is the lowest latency (or other factor) then the content is downloaded directly.
In some embodiments, the requesting SND requests content from all the sources. The first content packet received is sustained. The other requests may be canceled.
In some embodiments, the topography of the network, such as that defined, for example, in Table 1, is used to predict the transfer performance based on the number of Wi-Fi repeaters, network hops, the content will have to navigate. This is a more complicated method than the two described above and only estimates the latency of a transfer.
Data Caching
The description above explains that content, or content pieces, are cached locally on SNDs. It has been stated that there are a number of ways to determine what content to cache and for how long. All of the extensive list of technologies, known to those skilled in the art, for optimizing content caching strategies may be used in embodiments described herein.
In one embodiment, however, the caching in the SLAN has a somewhat uncommon (but not unique) characteristic. The content cached across a SLAN is actually a distributed cache with the content, or content pieces, cached physically one or more of the SNDs in the SLAN. These SNDs are, in many embodiments, crowd-sourced in terms of location, capability (e.g., cache size, transfer speed, etc.), and persistence (i.e. online uptime may vary). Thus, there are challenges to create a coherent cache strategy for a SLAN.
There are a few solutions to this caching challenge. In some embodiments, the individual SNDs simply ignore any other SNDs when caching content. Presumably, a request for content on the SLAN was made without success before a request to the ISP, Internet or private network. Thus, it can be assumed that the new content—acquired not from the SLAN but from the ISP, Internet, or private network connection—is unique.
In one embodiment, when the SND receives a request for content from the client device it acts as a proxy server and requests the content first from its own cache and then from the SLAN. If the content is not found then the SND requests the content from the content server on the Internet. When the content response is delivered, the SND then caches the content locally.
In other embodiments, a network controller is used to direct specific SNDs to cache specific content as it passes through SNDs. In the response, the network controller includes a flag or other information that instructs the SND to cache the content in the response. In yet other embodiments, there are messages passed from the cached content source SND along with the content suggesting information (e.g., locations, number of hops, etc.) that would lead an SND to cache content or not.
In addition to caching content on SNDs, in some embodiments, the content or content pieces are located and accessed on client devices that are connected to SND nodes in the SLAN. In these embodiments, the content on the client device is considered a virtual extension of the SND cache. Referring again to
In some embodiments, certain content is “preloaded”, in that it is proactively downloaded and cached at some SND on the SLAN. In one embodiment, the network controller uses an API designed to instruct an SND to receive and cache content. In one embodiment, the network controller uses the Internet Protocol (IP) address of the SND in a Hypertext Transfer Protocol (HTTP) POST request to instruct the SND to cache the content and provide the content. In other embodiments, different APIs are used for this function. Which content is preloaded is a function of several factors. For example, in one embodiment, the content is predictive by artificial intelligence algorithms analyzing the consuming behaviors of the users on the SLAN. In another example, the content is part of a series of content (e.g., a television series) for which the user has subscribed. In yet another example, the content is part of a promotional package of content from a content provider (e.g. the latest offerings from Home Box Office).
In some embodiments with preloaded content, there is a network controller that knows the SLANs to which certain users are often connected. The server proactively requests that a SND in that SLAN download the content, or it transmits the content directly to the SND. This is also the case in embodiments where the SLAN is a virtual content kiosk (described below). In other embodiments, the SND proactively requests any speculative content, not already present on the SLAN, from content providers when a user connects.
There are many algorithms, both learned and heuristic, for determining which content persists and which is deleted from a given SND's cache. A common heuristic, previously mentioned, is replacing the least accessed content with the new content. However, preloaded content, especially for virtual content kiosk functionality, might be subject to different criteria.
Data and Network Security
Embodiments of the invention use traditional network security for data traffic. For example, including Transport Layer Security (TSL) and Secure Shell (SSH) can be used with certificates either preinstalled in, or requested by, the SND.
Content security is achieved (in general) by encrypting the content at the source. The SNDs, generally, do not decrypt content. The SNDs only need to know the identity of the content or content pieces to properly cache and deliver the content.
Content security can be achieved by a variety of methods. One embodiment uses the techniques found in U.S. Pat. No. 8,751,795 B2, “Secure Transfer and Tracking of Data Using Removable Non-volatile Memory Devices”, incorporated herein by reference. This includes a dedicated player with Digital Rights Management encryption, tracking, and rule-based playback. In this embodiment, only the authorized player can decrypt and play the content.
Local Peer-to-Peer Versus a Network Controller
As described above, there are different embodiments possible for connecting to a network, searching for data, and for caching decisions. In each case, these functions can be performed locally or via peer-to-peer. Alternatively, these functions can be performed with using a network controller.
In one embodiment, when connecting via peer-to-peer, the SND searches for a hidden SSID representing the SLAN signal and joins that network. In one embodiment, when connecting with a network controller, the SND uploads the list of SSIDs that it can see (and optionally its location) and the network controller suggests the SSID and password to join.
In one embodiment, when searching via peer-to-peer, the SND broadcasts a modified Zero Configuration message to the network and SNDs with the content respond. In one embodiment, when searching with network controller, the SND request content addressing instructions from the network controller which acts as the search engine for the SLAN.
In one embodiment, when caching via peer-to-peer, the SND makes the decision to cache the content based on whether or not that content is on the SLAN somewhere else (as well as a number of other possible parameters). In one embodiment, when caching with a network controller, it is the network controller that signals to an SND which data to cache.
In the descriptions of the embodiments, the functionality for connecting, searching, and caching have been presented as either peer-to-peer or facilitated with a network controller. However, in many embodiments the SND is capable of either method for one, two, or all three of the functions. Furthermore, these functions do not have to be performed the same way with every SND in an SLAN. Nor do these functions need to be performed the same way every time by the same SND. These functions can co-exist in a heterogeneous mix of SNDs.
Likewise, embodiments of the network controller(s) can be different. The connection, searching, and caching functions do not need to be performed by the same network controller or even in the same location of logical domain. A heterogeneous mix of network controllers can exist.
In one embodiment, the network controller function is physically instantiated in an SND. That is, the cached content locations, SND addresses (or multicast DNS), and APIs for caching and pre-loading content are performed by an SND. The SND is either connected directly to a server or a server is built into the SND. This embodiment has the advantage that the network controller is on the SLAN side of the ISP and no communication through the ISP is necessary. Otherwise, the same API calls for searching content and caching or pre-loading content work as described above.
SLAN Performing the Delivery of a Mo-DV Kiosk or SpeedSpot
In the embodiments described so far, the client device is assumed to be connected to the traditional Wi-Fi access point signal broadcast by the SND, and this client device is assumed to have connected to this Wi-Fi access point in the traditional way, i.e. selecting a SSID signal and entering the password. However, in some embodiments, a SLAN and/or a SND performs the functions of a content dispensing “kiosk” or SpeedSpot as described in “Content Distribution Systems and Methods,” U.S. Pat. No. 10,104,046 B2, incorporated herein by reference. In this case, the kiosk consumer client device connects and performs functions using an application on the kiosk consumer client device.
In one embodiment, the client device running the application in the background searches for a particular SSID from a Wi-Fi access point. This SSID is the generic SLAN name. The application then switches the existing Wi-Fi connection on the client device (if any) and connects to the SLAN using the SSID and authentication information (e.g., a programmed password). Then the application on the client device requests pre-authorized content and downloads it. When the process is complete, the application on the client devices reconnects to the original Wi-Fi network (if any).
These embodiments employ the same connection, search, transfer, and caching functions described above. In fact, these embodiments can be used for client devices as described above in addition to the new functions described here. These kiosks, in many embodiments, are an added function of the SND and SLAN.
The kiosk embodiments differ from that of the typical SND/SLAN functions in a few ways. In some embodiments, the “kiosk” is a physical device with branding to attract and market the product. In other embodiments, the “kiosk” is simply the SND Wi-Fi access point signals that connect to the SLAN. In other words, the idea of the kiosk is virtual. In these embodiments, the SLAN is the kiosk.
In many embodiments, the client device has software. In on embodiment, this software performs many functions such as (1) authenticating and connecting directly the SLAN Wi-Fi signal without user assistance; (2) transact or authenticate a transaction for buying or renting the content; and (3) assist the user in finding physical locations where connections to the SLAN can be made.
As described above, in some embodiments, the content is proactively delivered (preloaded) to a SND in a SLAN. As described above, the content chosen for preloading can be predicted by a learning algorithm that is measuring content traffic. This can extend to the kiosk function in the same way it did for the client device describe above.
However, in some of the kiosk embodiments, the content preloaded is a set library that is offered by a content provider. For example, the latest movie releases or game highlights could be preloaded. Note that the same embodiment can offer this service to both the kiosk users (that is client devices that automatically connect via software) and traditional client devices (client devices connected via authentication to the client SSID signal).
In other words, if a user obtains a SND to connect to their ISP, then that SND, and possibly the SLAN to which it is connected, can automatically serve as a “crowd sourced” kiosk for other users.
Dynamic Load Balancing Between the ISPs Connected to the SLAN
In some embodiments, the SLAN networks are used to load balance between ISPs. In this case, the SNDs of an SLAN are connected to two or more different ISPs. At any given time the bandwidth from the ISP to the SND can vary. In these embodiments, if an SND has a request that cannot be served locally by the SLAN (i.e. has to go through the ISP), the bandwidth of the ISP can be measured (using Ping and other software known to those skilled in the art). If the ISP bandwidth is found to be below some measures, the SND can make a request to find a SND on the SLAN connected to an ISP with better performance at the moment. Then the request is made from the first SND to the responding SND connected to the better performing ISP and the content is transferred thusly.
Client Devices
There are many client devices that can connect to an SND, with more being invented. In one embodiment, client devices include computers, tablets, and mobile phones. These devices do not need to run applications to take advantage of the SND and SLAN cached content. In one embodiment, for traditional requests, the SND will act as a proxy server to find the content, either locally or on the Internet.
However, in one embodiment, when these client devices are running applications compatible with Mo-DV's Mo2Go video delivery service, then the devices can connect automatically to a SND or SLAN and access pre-authorized content. In one embodiment, this automatic connection is performed using techniques like the method that SNDs connect to each other and are well known in the art. For example, the application on the client device, running in either the foreground or background, scans for a particular SSID that would indicate a Mo2Go enabled SND. Then, the application switches the network connection to connect to the SND, downloads the content, and switches back to the original network connection. This can be performed with or without notifying, and/or requesting permission from, the user.
In one embodiment, another client device is a set-top box. These devices are commonly used for converting cable and satellite signals into digital monitor signals, accessing the Internet, and providing a television user interface. Once again, these devices can utilize the content cache in a SND or SLAN without using software. However, in one embodiment, the Mo-DV's Mo2Go compatible software is running and thereby enabling the set-top box to access pre-authorized content.
In yet another embodiment, the client device is a Digital Video Recorder (DVR). In one embodiment, this is integrated with a set-top box, and this device caches content according to the user's instructions. In one embodiment, software is run on the DVR to enable the SND to search and transfer the content on the DVR. This makes the DVR content part of the SND and SLAN distributed content cache.
In some embodiments, the SND and the client device functions are combined in one device.
Propagating SNDs
Embodiments of the invention have the potential to create content caching and free up network bandwidth essentially at the first point of a network for a client device. This potential reduction in latency, bandwidth utilization, and the greater predictability and consistency in content delivery are highly valued features. The consumer benefits with a better experience. The ISP benefits with potentially less bandwidth and caching demands. The backbone backend network and source server companies benefit by less bandwidth and better performance. The network device manufacturers can offer SNDs with different configurations and tuning for competitive advantage. And, finally, the content provider benefits by offering a better experience and being more accessible.
There are several models for content delivery and Wi-Fi access currently. In one model, a company creates a private network and installs several Wi-Fi access points. Clearly, replacing some or all of these Wi-Fi access points with SNDs would reap a benefit, especially if the company's private network delivers a lot of the same content to multiple employees. Likewise, a company may install several SNDs connected directly to an ISP but restrict the SLAN to company installed SNDs.
In some cases, businesses set up Wi-Fi access points for customers. In places like coffee shops, airports, and stadiums using this technology could be a big advantage in high demand areas. This is an especially good environment for the content delivery kiosk.
In some cases, ISPs (such as Comcast's Xfinity) sell, rent, or give modem/Wi-Fi access points to their customers. In some cases, these devices also provide “crowd sourced” Wi-Fi hotspots (called xfinitywifi in the case of Xfinity). The customers have the technical interface to “opt out” of providing a hotspot, but many do not. Replacing these devices with SNDs would provide all the aforementioned benefits to the ISP customers and could provide kiosk and SLAN access to other customers as well. (See the example below.)
In many cases, Wi-Fi access points are located in homes and businesses without any coordination. Neighbors might have different ISPs with different capabilities and modem/Wi-Fi access point hardware devices. If these neighbors purchase or rent SND capable devices, they and their neighbors can reap the benefits. See the example below.
In one embodiment, the individual SND is configured to opt out of all or some of the functionality. For example embodiments, an SND could disallow certain other SNDs from connecting in the first place. The SND could prohibit the caching of certain content. The SND could limit the content that it requests from the SLAN. The SND could prevent others from requesting content through it to the ISP connected to that SND. The SND could prevent the query and requesting of content from certain, or all, attached client devices.
These prohibitions, and many more, can be configured either by the user or the owner of the SND (perhaps a company), saved as state, and then looked up by the SND before any functions are performed. This type of settings technology is common and straight forward and well known to those skilled in the art. However, the transparency and control these settings offer are critical for user acceptance and comfort with using this invention.
Example of a Centrally Administrated set of a SLAN
To further illuminate the character of the techniques described herein, an example system deployed by a single ISP network provider is described in this section. This example relies on the ISP's network controllers for discover, connection, DNS, and content search.
In this example embodiment, a single large ISP (e.g., Comcast's Xfinity product) provides SND hardware to a number of its customers. Most, if not all, of the SNDs are the same dedicated hardware including a modem, at least two Wi-Fi signals (one for connecting to the clients and a hidden network for creating SLANs), significant cache memory, and a CPU and software that manage the SLAN interaction.
The customers install these SNDs in their home, business, or elsewhere as they wish. Similar to the way xfininitywifi hotspots, which originate in Comcast provided hardware, the customer can used software settings opt out of SLAN networks.
The ISP server knows the locations (more or less, depending on whether GPS is used) of these SNDs. When a customer turns on their SND for the first time, the SNDs upload the SSIDs of all of the other Wi-Fi signals within range to the ISP server. The ISP server knows which of these are also its own SNDs and instructs the new SND to join the hidden SSID of a SND in the SLAN network. Now the SND and the ISP server know the topography of the specific SLAN. In one embodiment, the ISP server stores this interconnected network information in a data store.
Subsequently, the new SND receives a request for a large piece of content from a client device, perhaps a movie, and the SND sends the request to the ISP server. The ISP server initially searches for the content (or content piece) within the SNDs SLAN. If the content is not found cached on any of the SNDs in the SLAN, then the ISP requests the content from the Internet. Now when the SND receives the content from the ISP (from the Internet, not the SLAN), it is accompanied by caching instructions from the ISP server. It then caches the content locally (stored on the SND) according to those instructions. In one embodiment, the caching instructions include functions like the duration of the storage, whether it is checked for update consistency before it is accessed from the cache, whether to fragment the content, whether to push it to other SND nodes in the network, and what to do with replacement content that might be pushed from the ISP later.
Otherwise, if the content is found cached on one or more of the SND(s) in the SLAN, the ISP server instructs the SND where access the content locally. The content is the transferred to the requesting SND through usual networking means.
In this example, the SNDs perform as slaves to the central servers at the ISP. The discovery of SLAN, connection to the SLAN, discovery of content, caching instructions, and transfer of content are all orchestrated by the ISP server. All of the learning algorithms and tuning of the caching strategies are performed centrally at the ISP server.
In fact, the ISP server can uncover weaknesses in the SLAN networks, such as holes in signal that prevent effective bridging between networks or insufficient cache memory on certain nodes. The ISP, for example, can proactively alter the physical topology of the network by changing the equipment or physically installing new (non-customer) nodes.
Example of an Ad-Hoc Formed and Administrated SLAN
In these example embodiments, an SLAN is formed by the peer-to-peer interaction of SNDs within range of each other. This ad-hoc network, or any individual SND, may or may not depend on network controllers for some, or all of the network functionality.
When an SND is initially turned on it looks for the hidden secondary SLAN Wi-Fi network. Upon finding the network the SND joins it via a secure password or credentialed transaction.
As in the previous example, the new SND receives from a client device a request for a large piece of content, perhaps a movie. In this embodiment, however, the SND sends a modified Bonjour request to all of the SNDs on its network searching for the content or a piece of the content.
Similar to the previous example, if the content is not found cached on any of the SNDs in the SLAN then the SND requests the content from the Internet. Now when the SND receives the content from the Internet via the ISP, it is cached locally (stored on the SND) according to the caching instructions that are preset, learned, or accompany the content. The caching instructions include functions like the duration of the storage, whether it is checked for update consistency before it is accessed from the cache, whether to fragment the content, whether to push it to other SND nodes in the network, and what to do with replacement content that might be pushed later.
If the content is found cached on one, or more, of the SNDs in the SLAN the requesting SND Pings the SND(s) with the content and, perhaps the Internet, to determine which content source is the best in terms of bandwidth and latency. Then the requesting SND makes a direct request to that source of the content. The content is then transferred to the requesting SND through usual networking means.
There is a number of example embodiments described herein.
Example 1 is a device for use in a network arrangement comprising a plurality of access points that are part of one or more existing networks and operable to individually address and communicate with each other to form a local area network (LAN) to transfer data between two or more of the plurality of access points using point-to-point links independent of their function in the one or more first existing networks, where the client device comprises: a first communication interface to connect to the one or more existing networks; a second wireless communication interface to connect to one or more access points of the plurality of access points that are part of the one or more existing networks, via individual addresses, to transfer data using point-to-point links; a cache to store content; connection logic coupled to the first and second communication interfaces, and the cache, to initiate a wireless connection with one or more access points in the plurality of access points by itself using the second wireless communication interface to transfer desired content cached by individual access points of the plurality of access points, the wireless connection used to request at least one of the one or more of the plurality of access points to transfer the desired content via one or more direct point-to-point transfers with one or more access points in the plurality of access points.
Example 2 is the device of example 1 that may optionally include that the connection logic is operable to set up the wireless connection by itself in response to an input from a network controller that is part of the LAN.
Example 3 is the device of example 1 that may optionally include that the second wireless communication interface is a Wi-Fi connection interface.
Example 4 is the device of example 1 that may optionally include that the wireless connection is used to transfer the desired content as a repeater when transferring the desired content to the one access point.
Example 5 is the device of example 1 that may optionally include that the connection logic is operable to address one or more access points of the plurality of access points and to select among the one or more access points from which cached content is available as a source for the desired content for a client coupled to the one access point that requested the content.
Example 6 is the device of example 1 that may optionally include that the connection logic is operable to generate a request for content that is broadcast onto the LAN via the second wireless communication interface and, in response thereto, to receive a response with an address of an access point in the LAN having the desired content or part thereof.
Example 7 is the device of example 1 that may optionally include that the connection logic is operable to generate a request to a network controller in the LAN for an address of one or more access points in the LAN having the desired content and, in response thereto, to generate a request for the desired content to at least one of the one more access points.
Example 8 is the device of example 1 that may optionally include that the cache is operable to store content that may be forwarded to other access points in the plurality of access points and the connection logic is response to send content cached by the cache to one or more other access points in the LAN in response to a request received by the one or more other access points.
Example 9 is the device of example 8 that may optionally include that the request is received via a Zero Configuration Network protocol.
Example 10 is the device of example 8 that may optionally include that the content is pre-loaded into the cache.
Example 11 is the device of example 1 that may optionally include that the connection logic is operable to access desired content using an internet service provider (ISP) when the desired content is not available from an access point in the LAN.
Example 12 is the device of example 11 that may optionally include that the connection logic is operable to select among a plurality of ISPs for content based on available bandwidth of the ISPs.
Example 13 is the device of example 1 that may optionally include that the connection logic includes a controller to function as a network controller for one or more access points in the LAN for one or more of content location requests, caching instructions, and pre-loading content.
Example 14 is the device of example 1 that may optionally include that the first communication interface, the second wireless communication interface and the connection logic are part of a computer, tablet, mobile device, set top box, digital video recorder, or digital camera.
Example 15 is the device of example 1 that may optionally include that the second communication interface is operable to communicably connect to a computer, tablet, mobile device, set top box, digital video recorder, or digital camera.
Example 16 is a method for use by a device that communicates with one or more access points, via individual addressing, that are part of one or more existing networks and form a local area network (LAN) to transfer data between two or more of the plurality of access points using point-to-point links independent of their function in the one or more first existing networks, wherein each access point of the plurality of access points is associated with a cache to store content that may be forwarded to other access points in the plurality of access points, and the method comprises: the device initiating a wireless connection with one or more access points in the plurality of access points by itself using a wireless communication interface of the device to transfer desired content cached by individual access points of the plurality of access points; identifying one or more of the plurality of access points from which desired content is cached; and requesting, via the wireless connection, at least one of the one or more of the plurality of access points to transfer the desired content via one or more direct point-to-point transfers with one or more access points in the plurality of access points
Example 17 is the method of example 16 that may optionally include that setting up a wireless connection by itself is performed in response to an input from a network controller that is part of the LAN.
Example 18 is the method of example 16 that may optionally include selecting among the one or more access points from which cached content is available as a source for the desired content for a client coupled to the one access point that requested the content.
Example 19 is the method of example 16 that may optionally include generating and sending, via broadcast onto the LAN, a request for content via the wireless communication interface of the device and, in response thereto, receiving a response with an address of an access point in the LAN having the desired content or part thereof, wherein the request is received via a Zero Configuration Network protocol.
Example 20 is one or more non-transitory computer readable storage media having instructions stored thereupon which, when executed by a system having at least a processor and a memory therein, the instructions causing the system to perform a method for use by a device that communicates with one or more access points, via individual addressing, each access point being part of one or more existing networks and forming a local area network (LAN) to transfer data between two or more of the plurality of access points using point-to-point links independent of their function in the one or more first existing networks, wherein each access point of the plurality of access points is associated with a cache to store content that may be forwarded to other access points in the plurality of access points, where the method comprises: the device initiating a wireless connection with one or more access points in the plurality of access points by itself using a wireless communication interface of the device to transfer desired content cached by individual access points of the plurality of access points; identifying one or more of the plurality of access points from which desired content is cached; and requesting, via the wireless connection, at least one of the one or more of the plurality of access points to transfer the desired content via one or more direct point-to-point transfers with one or more access points in the plurality of access points.
Example 21 is the media of example 20 that may optionally include that setting up a wireless connection by itself is performed in response to an input from a network controller that is part of the LAN.
As used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the invention. This description should be read to include one or at least one and the singular also includes the plural unless it is obvious that it is meant otherwise.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
Whereas many alterations and modifications of the present invention will no doubt become apparent to a person of ordinary skill in the art after having read the foregoing description, it is to be understood that any particular embodiment shown and described by way of illustration is in no way intended to be considered limiting. Therefore, references to details of various embodiments are not intended to limit the scope of the claims which in themselves recite only those features regarded as essential to the invention.
This application is a continuation-in-part of and claims benefit to U.S. patent application Ser. No. 16/517,226, filed on Jul. 19, 2019 and entitled “SPECIAL LOCAL AREA NETWORK WITH SECURE DATA TRANSFER”.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6915124 | Kiessling et al. | Jul 2005 | B1 |
| 7653689 | Champagne et al. | Jan 2010 | B1 |
| 8194538 | Bornstein et al. | Jun 2012 | B2 |
| 8751795 | Widergren et al. | Jun 2014 | B2 |
| 9712410 | Char et al. | Jul 2017 | B1 |
| 10104046 | Boliek et al. | Oct 2018 | B2 |
| 10304349 | Stickle et al. | May 2019 | B1 |
| 10512064 | Singh | Dec 2019 | B1 |
| 10652343 | Van et al. | May 2020 | B2 |
| 10771590 | Tomkins | Sep 2020 | B2 |
| 10986387 | Parulkar | Apr 2021 | B1 |
| 11283475 | Tsai | Mar 2022 | B1 |
| 11395209 | Boliek | Jul 2022 | B2 |
| 11877350 | Boliek | Jan 2024 | B2 |
| 20020184368 | Wang | Dec 2002 | A1 |
| 20040117455 | Kaminsky et al. | Jun 2004 | A1 |
| 20040203818 | Cromer | Oct 2004 | A1 |
| 20040215687 | Klemba et al. | Oct 2004 | A1 |
| 20050073967 | Hennessey et al. | Apr 2005 | A1 |
| 20070089110 | Li | Apr 2007 | A1 |
| 20080005695 | Ozzie et al. | Jan 2008 | A1 |
| 20080009280 | Ushiki | Jan 2008 | A1 |
| 20080086574 | Raciborski et al. | Apr 2008 | A1 |
| 20090070650 | Bourlas | Mar 2009 | A1 |
| 20090080386 | Yavuz | Mar 2009 | A1 |
| 20090154466 | Townsley et al. | Jun 2009 | A1 |
| 20090257388 | Khandekar | Oct 2009 | A1 |
| 20100027491 | Reina | Feb 2010 | A1 |
| 20100124183 | Sorond | May 2010 | A1 |
| 20100198913 | Garcia-Luna-Aveces et al. | Aug 2010 | A1 |
| 20100202428 | Thompson et al. | Aug 2010 | A1 |
| 20100210279 | Karaoguz | Aug 2010 | A1 |
| 20100214996 | Santhanam | Aug 2010 | A1 |
| 20100254268 | Kim | Oct 2010 | A1 |
| 20110116465 | Miki | May 2011 | A1 |
| 20110164536 | Lin | Jul 2011 | A1 |
| 20110225311 | Liu et al. | Sep 2011 | A1 |
| 20110225312 | Liu et al. | Sep 2011 | A1 |
| 20110273996 | Kim | Nov 2011 | A1 |
| 20120066493 | Widergren et al. | Mar 2012 | A1 |
| 20120069826 | Nakao | Mar 2012 | A1 |
| 20120082131 | Agrawal et al. | Apr 2012 | A1 |
| 20120092997 | Mihaly et al. | Apr 2012 | A1 |
| 20120099519 | Kim | Apr 2012 | A1 |
| 20120209952 | Lotfallah et al. | Aug 2012 | A1 |
| 20130039291 | Blankenship | Feb 2013 | A1 |
| 20130107867 | Li | May 2013 | A1 |
| 20130128857 | Nakao | May 2013 | A1 |
| 20130215875 | Yang | Aug 2013 | A1 |
| 20130303214 | Ahmadi | Nov 2013 | A1 |
| 20140044095 | Li | Feb 2014 | A1 |
| 20140086201 | Nagata | Mar 2014 | A1 |
| 20140098780 | Kim | Apr 2014 | A1 |
| 20140189060 | Westphal | Jul 2014 | A1 |
| 20140226607 | Holma | Aug 2014 | A1 |
| 20140258771 | Xie et al. | Sep 2014 | A1 |
| 20140286299 | Ihm | Sep 2014 | A1 |
| 20150089075 | Strigeus et al. | Mar 2015 | A1 |
| 20150110032 | Nagata | Apr 2015 | A1 |
| 20150131674 | Kao et al. | May 2015 | A1 |
| 20150288732 | Phillips et al. | Oct 2015 | A1 |
| 20150319488 | Krikorian et al. | Nov 2015 | A1 |
| 20150333898 | Ji | Nov 2015 | A1 |
| 20150334729 | Ji | Nov 2015 | A1 |
| 20160056871 | Kakishima | Feb 2016 | A1 |
| 20160119165 | Keronen | Apr 2016 | A1 |
| 20160119408 | Bertz et al. | Apr 2016 | A1 |
| 20160157103 | Teng | Jun 2016 | A1 |
| 20160204916 | Dao et al. | Jul 2016 | A1 |
| 20160294971 | Li et al. | Oct 2016 | A1 |
| 20170094496 | Aoki | Mar 2017 | A1 |
| 20170318564 | Lee | Nov 2017 | A1 |
| 20170346924 | Xiong et al. | Nov 2017 | A1 |
| 20170347394 | Yasukawa | Nov 2017 | A1 |
| 20180018159 | Eller | Jan 2018 | A1 |
| 20180069862 | Cholas | Mar 2018 | A1 |
| 20180083880 | Cioffi et al. | Mar 2018 | A1 |
| 20180097908 | Ayyagari et al. | Apr 2018 | A1 |
| 20180167486 | Pacella et al. | Jun 2018 | A1 |
| 20190044921 | Boliek et al. | Feb 2019 | A1 |
| 20190104068 | Hofmann | Apr 2019 | A1 |
| 20190166225 | Yokota et al. | May 2019 | A1 |
| 20200015248 | Ji | Jan 2020 | A1 |
| 20210021906 | Boliek | Jan 2021 | A1 |
| 20210021907 | Boliek | Jan 2021 | A1 |
| 20210021988 | Boliek | Jan 2021 | A1 |
| 20210044850 | Gala et al. | Feb 2021 | A1 |
| 20210235362 | Boliek | Jul 2021 | A1 |
| 20230119540 | Boliek | Apr 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 20110068465 | Jun 2011 | KR |
| WO-2017085978 | May 2017 | WO |
| Entry |
|---|
| International Preliminary Report and Written Opinion on the Patentability of Application No. PCT/US2020/039008 Mailed Feb. 3, 2022. 8 pages. |
| International Preliminary Report and Written Opinion on the Patentability of Application No. PCT/US2020/039010 Mailed Feb. 3, 2022. 8 pages. |
| International Preliminary Report and Written Opinion on the Patentability of Application No. PCT/US2020/039015 Mailed Feb. 3, 2022. 12 pages. |
| International Search Report received for PCT Patent Application No. PCT/US20/39008, mailed on Aug. 31, 2020, 3 pages. |
| International Search Report received for PCT Patent Application No. PCT/US20/39010, mailed on Sep. 9, 2020, 3 pages. |
| International Search Report received for PCT Patent Application No. PCT/US20/39015, mailed on Sep. 28, 2020, 2 pages. |
| Written Opinion received for PCT Patent Application No. PCT/US20/39008, mailed on Aug. 31, 2020, 6 pages. |
| Written Opinion received for PCT Patent Application No. PCT/US20/39010, mailed on Sep. 9, 2020, 6 pages. |
| Written Opinion received for PCT Patent Application No. PCT/US20/39015, mailed on Sep. 28, 2020, 10 pages. |
| Mahan, et al. Secure data transfer guidance for industrial control and SCADA systems. *In: Pacific Northwest National Lab. {PNNL}. Sep. 2011 (Sep. 2011) Retrieved on Aug. 13, 2020 (Aug. 13, 2020) from <https://pnnl.gov/main/publications/external/technical_reports/PNNL-20776.pdf> entire document. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/039008, mailed on Aug. 31, 2020, 56 pages. |
| Intemational Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/039010, mailed on Sep. 9, 2020, 10 pages. |
| International Preliminary Report on Patentability received for PCT Application No. PCT/US2020/039015, mailed Sep. 28, 2020, 18 pages. |
| Non-Final Office Action received in related U.S. Appl. No. 16/534,941, mailed Apr. 11, 2024, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210021906 A1 | Jan 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16517226 | Jul 2019 | US |
| Child | 16534939 | US |
