Patent Grant
8320414
This application is related to the following applications, all of which are incorporated herein by reference in their entireties: application Ser. No. 11/755,808, published as U.S. Pub. No. 2008/0301017; application Ser. No. 11/755,780, published as U.S. Pub. No. 2008/0298327, application Ser. No. 11/755,775, published as U.S. Pub. No. 2008/0301017, and application Ser. No. 11/755,806, published as U.S. Pub. No. 2008/0301039.
The invention generally relates to systems and methods for sharing bandwidth in ad hoc networks, and more particularly to systems and methods for the formation and rearrangement of lender devices that perform multiplexing functions within bandwidth-sharing ad hoc networks.
Mobile computing is becoming increasingly pervasive, and will approach ubiquity in wireless devices (e.g., notebook computers, smart phones, personal digital assistants (PDAs), etc.) over the next decade. One consistent trend in this mobile computing space is the fact that such platforms increasingly communicate over a variety of wireless protocols. Common protocols in use today for wireless data transfer include EV-DO, IEEE 802.11a/b/g, ZigBee® (registered trademark of ZIGBEE ALLIANCE of California), Bluetooth® (registered trademark of BLUETOOTH SIG, INC. of Delaware), and many other related protocols. By their very nature, differentials do exist, and will continue to exist, between the speed, or bandwidth, with which mobile devices can communicate with each other, vis-à-vis communications speeds with the broader network where a device's target data may reside.
It is often the case that a wireless device will have a relatively fast wireless connection to other local devices and a relatively slow wireless connection to the broader network (e.g., the Internet). For example, local wireless connections, provided by protocols such as IEEE 802.11a, 802.11b, 802.11g, 802.15.1 (e.g., Bluetooth®), and 802.15.4 (e.g., Zigbee®) provide fast data transfer rates of about 3 to 54 megabits per second (Mbps). However, such transfer protocols often have a limited maximum transmission range of about 30 to 300 ft. On the other hand, wireless telephony protocols (e.g., EV-DO, CDMA, EDGE, GPRS, etc.) have relatively large maximum transmission ranges on the order of miles, but only provide data transfer rates of about 10 kilobits per second (kbps) to 1 Mbps. Thus, while a user of a mobile device may enjoy relatively fast data transfer amongst local devices, the user is often limited to a slow wireless connection to the outside world (e.g., the Internet).
Accordingly, there exists a need in the art to overcome the deficiencies and limitations described hereinabove.
In a first aspect of the invention, a method comprises establishing an ad-hoc network between a borrower and at least two lenders of bandwidth and establishing one lender of the at least two lenders as a multiplexer to manage data flow over the ad-hoc network between the borrower and lenders of the at least two lenders of bandwidth.
In another aspect of the invention, the method comprises establishing an ad-hoc network between a borrower and at least two lenders of bandwidth by broadcasting a table to the at least two lenders. The method further comprises requesting one of the at least two lenders to be a multiplexer to manage data flow over the ad-hoc network based on required criteria, and establishing the one of the at least two lenders as the multiplexer based on information provided by the at least two lenders which meets the required criteria.
In another aspect of the invention, a method for providing a formation of a multiplexed ad-hoc network comprises providing a computer infrastructure. The computer infrastructure being operable to: establish an ad-hoc network between a borrower and at least two lenders of bandwidth by broadcasting a table to the at least two lenders; request one of the at least two lenders to be a multiplexer to manage data flow over the ad-hoc network; and establish the one of the at least two lenders as the multiplexer based on required criteria provided by the borrower.
In another aspect of the invention, a system comprises a server having a database containing data associated with one or more lenders and a borrower in an ad-hoc network. At least one of a hardware and software component establishes an ad-hoc network between a borrower and at least two lenders of bandwidth by broadcasting a table to the at least two lenders; requests one of the at least two lenders to be a multiplexer to manage data flow over the ad-hoc network based on required criteria; and establishes the one of the at least two lenders as the multiplexer based on information provided by the at least two lenders which meets the required criteria.
In yet another aspect of the invention, a computer program product comprises a computer usable medium having readable program code embodied in the medium. The computer program product includes at least one component to: establish an ad-hoc network between a borrower and at least two lenders of bandwidth; and establish one lender of the at least two lenders as a multiplexer to manage data flow over the ad-hoc network between the borrower and lenders of the at least two lenders of bandwidth.
The invention generally relates to systems and methods for the formation and rearrangement of lender devices that perform multiplexing functions. More particularly, the present invention is directed to systems and methods for the formation of lender devices that perform multiplexing functions in a bandwidth-sharing ad hoc network. More particularly, the present invention is directed to systems and methods for the rearrangement of lender devices that perform multiplexing functions in a bandwidth-sharing ad hoc network should a lender device performing multiplexing functions become unavailable.
By implementing the methods and systems of the invention, e.g., the formation and rearrangement of lender devices that perform multiplexing functions, multiple disparate wireless connections in conjunction with multiple devices using a variety of service providers, for example, can be used to create a single virtual fat pipe for transmission of data over a network. The individuals who share their current connections, i.e., bandwidth, acting as gateway devices, are ‘lenders’ of bandwidth; whereas, the individuals who require additional bandwidth are ‘borrowers’. By implementing the systems and methods of the invention, borrowers and/or multiplexers are able to form and rearrange lender devices to perform multiplexing functions in a bandwidth-sharing ad hoc network.
In general, the processor 20 executes computer program code, which is stored in memory 22A and/or storage system 22B. While executing computer program code, the processor 20 can read and/or write data to/from memory 22A, storage system 22B, and/or I/O interface 24. The bus 26 provides a communications link between each of the components in the computing device 14. The I/O device 28 can comprise any device that enables an individual to interact with the computing device 14 or any device that enables the computing device 14 to communicate with one or more other computing devices using any type of communications link.
The computing device 14 can comprise any general purpose computing article of manufacture capable of executing computer program code installed thereon (e.g., a personal computer, server, handheld device, etc.). However, it is understood that the computing device 14 is only representative of various possible equivalent computing devices that may perform the processes described herein. To this extent, in embodiments, the functionality provided by computing device 14 can be implemented by a computing article of manufacture that includes any combination of general and/or specific purpose hardware and/or computer program code. In each embodiment, the program code and hardware can be created using standard programming and engineering techniques, respectively.
Similarly, the computer infrastructure 12 is only illustrative of various types of computer infrastructures for implementing the invention. For example, in embodiments, the computer infrastructure 12 comprises two or more computing devices (e.g., a server cluster) that communicate over any type of communications link, such as a network, a shared memory, or the like, to perform the process described herein. Further, while performing the processes described herein, one or more computing devices in the computer infrastructure 12 can communicate with one or more other computing devices external to computer infrastructure 12 using any type of communications link. The communications link can comprise any combination of wired and/or wireless links; any combination of one or more types of networks (e.g., the Internet, a wide area network, a local area network, a virtual private network, etc.); and/or utilize any combination of transmission techniques and protocols.
In embodiments, the invention provides a business method that performs the steps of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to perform the processes described herein. In this case, the service provider can create, maintain, deploy, support, etc., a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
“Ad hoc” relationships are becoming increasingly important in the communal sharing of immediately available resources, and most particularly, the sharing of bandwidth. With the creation of peer-to-peer networks and bit torrent type services a file may be stored in a large number of locations to allow very fast download of the file in sections simultaneously from multiple locations. Groups of devices may congregate, or coexist, in one place and each may have limited bandwidth to the outside world. However, the groups of devices may have high bandwidth to other devices within close proximity. An example is a 802.11g local area connection that creates a high-speed wireless connection between two cellular phone devices within close range (high bandwidth), and wherein the cellular phones' cellular connection to the outside world may provide bandwidth at less than one percent of the 802.11g connection.
In embodiments of the invention, a lender performs multiplexing functions within a bandwidth-sharing ad hoc network formed between a borrower and one or more lenders. In embodiments, a lender may reactively promote themselves as a multiplexing device, proactively or in response to a request by a borrower. In further embodiments, the borrower or multiplexer may rearrange the bandwidth-sharing ad hoc network when the multiplexer lender is no longer available or can no longer provide the originally requested functions.
In order to utilize the formation and rearrangement schemes of lender devices that perform multiplexing functions in bandwidth-sharing networks, an ad hoc network may be created between a borrower node and one or more lender nodes. This process may include both an initial discovery mechanism of the proposed role each node may play, and a negotiation and acceptance of the agreed compensation scheme.
In this implementation, a borrower B may request information, e.g., transfer of files, from a central location, CL (or distributed locations). To increase its bandwidth capacity, the borrower B may request bandwidth from any of the lenders, L1 or L2 via any known wireless protocol. By way of example, upon a broadcast request from the borrower B, any of the lenders, L1 or L2 may allow the borrower B to use their excess bandwidth for file transfers with the central location, CL (or distributed locations). Upon authorization, the lenders, via a wireless protocol, for example, will download information from the central locations, CL (or distributed locations), and send this information to the borrower, B, thus effectively increasing the borrower's bandwidth. It should be understood that data could be transferred from distributed locations, rather than the central location, CL.
In order to form a new ad hoc network, a borrower may scan all available potential lenders and prioritize the potential lenders for a data transfer. An illustrative formation and rearrangement of ad hoc network bandwidth-sharing architecture is set forth in application Ser. No. 11/755,775.
By way of illustration and shown in application Ser. No. 11/755,775, the formation of the ad hoc network, in embodiments, may use a “borrower/lender” table as shown in
In the borrower/lender table of
The “Price” column may be a price set by the lender to use the lender's bandwidth. The price may be stated in price/MB, number of minutes to be used in a wireless service plan or any other charging mechanism. The “Service Level Objective” column may describe the negotiated service levels of the node. For example, the requested bandwidth, the availability of the node, reliability and so forth. Additionally, the “Service Level Objective”, may contain reliability information, such as the ability to provide a bandwidth amount for a period of time, or a bandwidth amount within a range of bandwidth (i.e., between 1 kb/second and 2 kb/second). The “Current Quality of Service” column may contain the current quality of service (QoS) of the node. The QoS information may contain a status of the node, e.g., how well the service levels are being met, the current transfer rate, or the current progress of the file download.
In aspects of the invention, a borrower and a lender may not see all of the table on their respective devices, and some of the table information may be generated automatically. For example, the location of a lender's device or borrower's device may be known by the device itself. Thus, the user may not need to complete this portion of the table. Rather, the information for that portion of the table would be automatically completed by the device. Furthermore, the automatic generation of the information in the table may also apply to the Node Type, Node Name, Service Level Objective, Price and Current Quality of Service columns. For example, a borrower may have preset levels of service level objectives that they require whenever they borrow bandwidth, so that generation of the Service Level Objective column may be performed automatically by the borrower's device. Additionally, a potential lender may have a set price for lending bandwidth already input into their device, such that the Price column information is automatically generated.
A borrower may, for example, initially generate the table by clicking on an icon, and when prompted, input the File Requested for Download information. The borrower's device could generate the remaining portions of the information in the table. When a potential lender receives the borrower's request, their device may simply prompt for a decision to be a lender. If the potential lender answers “yes”, then their device may prompt the potential lender for a price. As set forth above, the rest of the information in the table may be generated automatically. The lender may also designate itself as a potential multiplexer as discussed below in more detail.
In order for a lender to become a multiplexer, a borrower may request that a lender/potential multiplexer have certain characteristics. A borrower may request that a potential multiplexer have a fast connection to the data required by the borrower. This could be a connection to the Internet or other wide area network, as shown in
A borrower may request that the multiplexer have the ability to directly connect to the other lenders in the ad hoc network, as shown in
The multiplexer should also be an intelligent device capable of multiplexing functions. The multiplexing functions may include, for example, managing the state table, breaking up the data stream into multiple data “chunks” that can be sent to and received by lenders in the ad hoc network.
An example of an arrangement that may meet these multiplexer attributes are a lender device that is a PC or Laptop connected to a high speed Wi-Fi network to the Internet, or other network, and has the ability to broadcast out to the ad hoc local wireless network. Another example may be a cellular device that has an EDGE or 3G fast connection and a local broadcast protocol such as Bluetooth®.
While multiplexer attributes were described above as ideal when the bandwidth of the multiplexer both to the network, and to the lenders in the ad hoc network was higher (or at least close to higher) than the aggregate bandwidth of the other lenders, it should be understood that a multiplexer may still be desirable to a borrower when the multiplexer's bandwidth to either the network, or to the lenders in the ad hoc network, is equal to or lower than the aggregate bandwidth connections of the lenders to the network. For example, a multiplexer may be slower, but based on other factors, e.g., price, service quality objectives, reliability, guaranteed time within the ad hoc network, may still meet the borrower's bandwidth sharing needs. The reasons as to why the lender may want to be “promoted” to a multiplexer may include an ability to charge a higher price than the price charged to be only a lender, for example.
The steps of the flow diagrams described herein may be implemented in the environment of
The flow diagrams may equally represent high-level block diagram of the invention. The steps of the flow diagrams may be implemented and executed from either a server, in a client server relationship, or they may run on a user workstation with operative information conveyed to the user workstation. Additionally, the invention can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment containing both hardware and software elements. In an embodiment, the software elements include firmware, resident software, microcode, etc.
Furthermore, the invention can take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program code for use by or in connection with a computer or any instruction execution system. The software and/or computer program product can be implemented in the environment of
As shown in the flow chart of
At step 105, the borrower may broadcast a request to form an ad hoc network. This broadcast, in embodiments, includes the table for completion by any available nodes within range that could be used to form the ad hoc network. The table may be broadcast over the wireless network using a plurality of different protocols such as Bluetooth®, Wi-Fi or Cellular. The table can be represented in binary, xml, text or other data format optimized for the type of data transport.
A node receives the broadcast, including the table, and at step 110, a potential lender may complete necessary information in the table. For example, as shown in TABLE 2, below, Lender 1 is a node on the same Wi-Fi network ‘Airport’ and is able to perform lender functions for $5/MB at a rate of 10 kb/second. The “File Requested for Transfer” column may remain blank, because the borrower has not yet decided which of the potential lenders will be part of the bandwidth-sharing ad hoc network. Additionally, the “Current Quality of Service” column may remain blank, because no bandwidth sharing has occurred yet.
Lender 1, at step 115, may send back this information to Borrower 1. The processes, at steps 110 and 115, may be repeated for other potential lenders of bandwidth in the ad hoc network. In this manner, the table may gradually be built up such that the borrower can select lenders to use.
For example, as shown below in TABLE 3, additional nodes, Lender 2 and Lender 3, provided the information for each lender, and this information has been tabulated by the borrower, upon receipt. In this example, Lender 2 is on a Bluetooth Network and can download the file requested for transfer at a price of $10/MB and a rate of 2 kb/second. Additionally, Lender 3, is on some other protocol, and can download the file requested for transfer at a price of $10/MB and a rate of 5 kb/second.
At step 120, the borrower may browse through the table to determine which lenders should be part of the bandwidth-sharing ad hoc network. By way of example, using a combination of “Service Level Objectives” and “Price”, Borrower 1 may decide how many lenders to use and at what cost. The borrower may then select the best number of lenders and file chunks such that the price remains low and the speed is reasonably fast, as one example.
At step 125, for example, the Borrower 1 may then transmit the table to Lender 1, Lender 2 and Lender 3 with the following information of TABLE 4.
In this example, Borrower 1 is requesting that Lender 1 transfer the first ⅓ of the file requested for download, ‘myfile’, and requesting that Lender 2 transfer the second ⅓ of the file, ‘myfile’, and requesting that Lender 3 transfer the last ⅓ of the file, ‘myfile’.
In the above example, there are three lenders, Lender 1, Lender 2, and Lender 3 and one borrower, Borrower 1, as indicated in the borrower/lender state table. In the situation where Lender 1 would like to become a multiplexer, at step 130, Lender 1 may look through the state table to determine whether it has the desired attributes of a multiplexer. This may include a faster (or very close to faster) connection speed to the network than the other lenders combined connection speed to the network, in an ideal case. Additionally, Lender 1 should be an intelligent device capable of multiplexing functions. However, as Lender 1 knows its device capabilities, Lender 1 would not need the information in the state table to make the intelligent device determination.
Assuming that the lender meets certain criteria, at step 135, the lender may update the state table information to request that the lender become a multiplexer. In the above example, Lender 1 may update the table with the following information of TABLE 5.
As shown in TABLE 5, Lender 1 has changed their “Node Type” column information from “Lender” to “Multiplexer?”. Additionally, as shown in TABLE 5, Lender 1 may indicate more than one pricing scheme, e.g., a price for being a lender and a price for being a multiplexer. At step 140, the lender, in this example Lender 1, may send the updated table back to the borrower.
At step 145, the borrower, in this example Borrower 1, may elect to use the lender, Lender 1, as a multiplexer. If the borrower decides to use Lender 1 as a multiplexer, at step 150, the borrower may designate Lender 1 as a multiplexer. In the above example, Lender 1 may update the table with the following information of TABLE 6.
As shown in TABLE 6, Borrower 1 has changed Lender 1's “Node Type” column information from “Multiplexer?” to “Multiplexer”. Additionally, as shown in TABLE 6, the “File Requested for Transfer” column may be cleared, as the multiplexer is now responsible for allocating the file portions amongst the lenders in the bandwidth-sharing ad hoc network.
At step 155, the multiplexer manages the download via the bandwidth-sharing ad hoc network. An illustrative multiplexed, gateway bandwidth-sharing architecture is set forth in application Ser. No. 11/755,380. An illustrative formation and rearrangement of ad hoc network bandwidth-sharing architecture is set forth in application Ser. No. 11/755,775.
Alternatively, at step 145, the borrower may decide to not use the potential multiplexer as a multiplexer, but rather only use the potential multiplexer as a lender. At step 160, the borrower may manage the download via a non-multiplexed bandwidth-sharing ad hoc network. An illustrative non-multiplexed, bandwidth-sharing architecture is set forth in application Ser. No. 11/755,808.
In another embodiment, it may not be necessary for a lender, interested in becoming a multiplexer, to wait until the state table is completed by the potential lenders in the ad hoc network before indicating a desire to be a multiplexer. Rather, a lender may indicate an interest in acting as a multiplexer earlier, i.e. be a proactive lender. This may allow the borrower to make the determination that the potential multiplexer is suitable to be a multiplexer in a quicker manner.
As shown in the flow chart of
As shown in TABLE 7, Lender 1 has entered their “Node Type” column information as “Multiplexer?”. At step 215, the lender, in this example Lender 1, may send the updated table back to the borrower. As Lender 1 may not yet know who else is available to share bandwidth in the ad hoc network, Lender 1 may not be able to make a determination of whether his bandwidth, or connection speeds, to both the network and other lenders in the ad hoc network is sufficient to satisfy the borrower's needs. However, Lender 1 may indicate a desire and willingness to act as a multiplexer pending the approval of Borrower 1. Additionally, as shown in TABLE 7, Lender 1 may indicate more than one pricing scheme, e.g., a price for being a lender and a price for being a multiplexer.
The processes, at steps 210 and 215, may be repeated for other potential lenders of bandwidth in the ad hoc network. In this manner, the table may gradually be built up such that borrower can select lenders to use. For example, as shown below in TABLE 8, additional nodes, Lender 2 and Lender 3, provide the information for each lender, and this information has been tabulated by the borrower, upon receipt.
At step 220, the borrower may browse through the table to determine whether the potential multiplexer meets the needs of the borrower with regards to the multiplexer attributes. If the borrower determines that the potential multiplexer is capable of multiplexing (i.e., has the requested multiplexer attributes), at step 225, the borrower may decide to use a lender as a multiplexer.
At step 240, for example, the Borrower 1 may send an updated table to Lender 1, Lender 2 and Lender 3 with the following information of TABLE 9.
As shown in TABLE 9, Borrower 1 has changed Lender 1's “Node Type” column information from “Multiplexer?” to “Multiplexer”, thereby indicating that Lender 1 will act as a multiplexer.
At step 245, the multiplexer may manage the download via the bandwidth-sharing ad hoc network. This step may include the multiplexer initiating the download by sending an updated table to Lender 2, Lender 3 and Borrower 1, indicating the file portions for each lender to download. An illustrative multiplexed, gateway bandwidth-sharing architecture is set forth in application Ser. No. 11/755,780. An illustrative formation and rearrangement of ad hoc network bandwidth-sharing architecture is set forth in application Ser. No. 11/755,775.
Alternatively, at step 220, the borrower may determine that the potential multiplexer does not meet the borrower's requirements for a multiplexer. Additionally, at step 225, the borrower may decide to not use the potential multiplexer as a multiplexer, but rather only use the potential multiplexer as a lender, even though the potential multiplexer may meet the borrower's needs. In either case, at step 230, the borrower may manage the download via a non-multiplexed bandwidth-sharing ad hoc network. This may include, at step 230, the borrower sending a table to lenders to initiate bandwidth sharing with the following information of TABLE 10.
An illustrative non-multiplexed, bandwidth-sharing architecture is set forth in application Ser. No. 11/755,808.
Situations may arise in a multiplexed bandwidth-sharing ad hoc network, when a multiplexer may no longer be able, or willing, to serve as the multiplexer. This situation may arise when the multiplexer goes out of range of the ad hoc network, loses bandwidth available to share (i.e., requires more bandwidth for itself), or otherwise becomes unavailable. In these or other scenarios, the borrower that is in communication with the multiplexer, through the ongoing download of data, may discover that the multiplexer is unavailable. Each of the lenders that are leveraging the multiplexer may also report problems that the data they are requesting is no longer available. In these or other scenarios, the borrow may elect to wait for a period of time to determine whether the multiplexer becomes available again; or begin immediately to determine whether any other lenders are able to promote themselves to a multiplexer.
Additionally, the borrower may elect to revert to a non-multiplexed, peer-to-peer bandwidth-sharing arrangement. As an ad hoc network is dynamic, new potential lenders willing to share bandwidth may have entered the ad hoc network. A situation may arise where, when initially forming the bandwidth-sharing ad hoc network, the best option for the borrower (based on, e.g., price, bandwidth or service quality objectives) may have been to utilize a multiplexed arrangement. However, at a later time, when the borrower may be forced to rearrange the bandwidth-sharing ad hoc network, due to an unavailable multiplexer, the better option (based on, e.g., price, bandwidth, or service quality objectives) is to use more lenders, different lenders, or the remaining lenders in a non-multiplexed environment.
Furthermore, it should be recognized that a borrower could opt to rearrange the bandwidth-sharing ad hoc network proactively, rather than reactively. For example, a borrower at any time could monitor if new potential lenders have located within the ad hoc network range, and opt to use a different multiplexer, or use different or additional lenders in a non-multiplexed environment.
However, switching from a multiplexed environment to a non-multiplexed environment may not always be possible, depending on the content of the data being downloaded. For example, the data may be too complex for individual lenders in a non-multiplexed, peer-to-peer bandwidth-sharing arrangement to receive portions of the data from the source. An example of this may be a data stream of a music file. As an illustration, in a multiplexed environment, the multiplexer may have the ability to obtain the data in a stereo format, and ‘chunk’ the data up into a left signal data stream and a right signal data stream, sending those signals via different lenders in the ad hoc network to the borrower, where the two data streams are recombined into a stereo signal. In a non-multiplexed, peer-to-peer bandwidth-sharing arrangement, the lenders may not be able to access just the left signal data stream and a right signal data stream individually from the source, as the source may not provide the data in a broken-up format. Therefore, a borrower, if using the ad hoc network to download this type of file, may need to reestablish another multiplexer before continuing the download, and may not be able to revert to a non-multiplexed, peer-to-peer bandwidth-sharing arrangement.
If, at step 305, a determination is made that the multiplexer is unavailable, a borrower may, at step 325, immediately halt the download, or alternatively, at step 310, wait a grace period (wait a predetermined amount of time, e.g., 5 seconds) for the multiplexer to become available again. At step 315, if a multiplexer becomes available again, the process may proceed to step 360, where a determination of whether the download is complete may be made, as set forth above. If, at step 315, the multiplexer has not become available again, the process may proceed to step 320. At step 320, a determination may be made as to whether the wait time period has expired. If the wait time period has not yet expired, the process may proceed to step 310, where the borrower may continue to wait. If the wait time has expired at step 320, the process may proceed to step 325.
At step 325, the multiplexed download may be halted. While it should be understood that if a multiplexer becomes unavailable, the download may stop because all the downloaded data is passed through the multiplexer, step 325 may be an active decision by the borrower to put the download on hold in order to rearrange the bandwidth-sharing arrangement. At step 330, the borrower may decide to remain in a multiplexed environment, and proceed to step 335, or alternatively the borrower may decide to download in a non-multiplexed environment, at step 345. As set forth above, at step 330, it may not always be possible for a borrower to rearrange the bandwidth-sharing network from a multiplexed environment to a non-multiplexed environment, due to the type of data being downloaded.
At step 335, the borrower may seek out another lender willing and capable to be a multiplexer. This step, in embodiments, may include the borrower looking to the state table for another lender already advertised as willing to act as a multiplexer. (As set forth above, a lender may have already indicated, or advertised, a willingness to act as a multiplexer by filling in the “Node Type” column in the state table with “Multiplexer?”.) Additionally, in embodiments, if no other lender has advertised a willingness to act as a multiplexer, the borrower may send a new request for a new multiplexer, in a manner similar to the initial formation of the ad hoc network. This step may include the borrower updating the state table with a flag that a new multiplexer should be found and broadcasting the updated state table, with lenders responding by updating the state table, as described above, possibly with updated prices and associated bandwidth objectives. Additionally, in embodiments, the borrower may entice a lender to act as a multiplexer by offering to pay a higher price to the lender to act as a multiplexer. The borrower selects a new multiplexer to use, at step 340. At this step, the multiplexed download may continue. This step may also include the new multiplexer determining how much of the download is still incomplete and start the data transfer from that point. At step 360, a determination is made as to whether the download is complete, as set forth above.
Alternatively, at step 330, the borrower may decide to proceed to step 345, and may use a non-multiplexed bandwidth-sharing ad hoc network. This step may indicate the initiation of a non-multiplexed download, or a continuation of a non-multiplexed download. The details of establishing a non-multiplexed bandwidth sharing ad hoc network are set forth in application Ser. No. 11/755,808, and the details of forming and rearranging bandwidth sharing ad hoc networks is set forth in application Ser. No. 11/755,775.
At step 350, a determination may be made as to whether the non-multiplexed download is complete. If the non-multiplexed download is not complete, the process may proceed to step 345, where the download may continue. If the non-multiplexed download is complete, the process may proceed to step 365, where the download ends.
Additionally, a multiplexer may already know that it may become unavailable soon and signal its status to the borrower, so that the borrower may proactively rearrange the bandwidth-sharing ad hoc network. In this embodiment, the step of waiting a time period may be unnecessary, as the borrower knows that the multiplexer will not become re-available. Alternatively, a multiplexer that knows they may become unavailable soon may proactively seek out another multiplexer, rather than simply informing the borrower.
It should be understood that while the above examples disclosed a single lender interested in acting as a multiplexer, multiple lenders may be interested in acting as multiplexers, and respond accordingly in the state table. This may occur during the original formation of the bandwidth-sharing ad hoc network, or when a multiplexer becomes unavailable and a borrower seeks out another multiplexer. The potential multiplexers may respond by updating the state table with pricing, available bandwidth, and service level objectives, and the borrower can then select which multiplexer to use—based on price, bandwidth or other service level objective.
Additionally, it should be understood that a multiplexer may also act as a lender, while performing multiplexer duties, as shown in
While the invention has been described in terms of embodiments, those skilled in the art will recognize that the invention can be practiced with modifications and in the spirit and scope of the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5390113 | Sampson | Feb 1995 | A |
| 5437054 | Rappaport et al. | Jul 1995 | A |
| 5490201 | Moberg et al. | Feb 1996 | A |
| 5953338 | Ma et al. | Sep 1999 | A |
| 5959975 | Sofman et al. | Sep 1999 | A |
| 6006084 | Miller et al. | Dec 1999 | A |
| 6035281 | Crosskey et al. | Mar 2000 | A |
| 6047268 | Bartoli et al. | Apr 2000 | A |
| 6366907 | Fanning et al. | Apr 2002 | B1 |
| 6396805 | Romrell | May 2002 | B2 |
| 6397061 | Jordan et al. | May 2002 | B1 |
| 6477522 | Young | Nov 2002 | B1 |
| 6522735 | Fortman et al. | Feb 2003 | B1 |
| 6653933 | Raschke et al. | Nov 2003 | B2 |
| 6751196 | Hulyalkar et al. | Jun 2004 | B1 |
| 6763248 | Odamura | Jul 2004 | B1 |
| 6810428 | Larsen et al. | Oct 2004 | B1 |
| 6850764 | Patel | Feb 2005 | B1 |
| 6879574 | Naghian et al. | Apr 2005 | B2 |
| 6941378 | Apostolopoulos et al. | Sep 2005 | B2 |
| 6954616 | Liang et al. | Oct 2005 | B2 |
| 6954790 | Forslöw | Oct 2005 | B2 |
| 6961575 | Stanforth | Nov 2005 | B2 |
| 6975613 | Johansson | Dec 2005 | B1 |
| 6980511 | Li | Dec 2005 | B1 |
| 6990113 | Wang et al. | Jan 2006 | B1 |
| 7016375 | Rosenberg et al. | Mar 2006 | B1 |
| 7028096 | Lee | Apr 2006 | B1 |
| 7043225 | Patel et al. | May 2006 | B1 |
| 7058014 | Sim | Jun 2006 | B2 |
| 7058387 | Kumar et al. | Jun 2006 | B2 |
| 7065367 | Michaelis et al. | Jun 2006 | B2 |
| 7075890 | Ozer et al. | Jul 2006 | B2 |
| 7085281 | Thomas et al. | Aug 2006 | B2 |
| 7089301 | Labio et al. | Aug 2006 | B1 |
| 7130283 | Vogel et al. | Oct 2006 | B2 |
| 7174385 | Li | Feb 2007 | B2 |
| 7224964 | Souissi et al. | May 2007 | B2 |
| 7240015 | Karmouch et al. | Jul 2007 | B1 |
| 7257632 | Zhang et al. | Aug 2007 | B2 |
| 7274658 | Bornstein et al. | Sep 2007 | B2 |
| 7310641 | Moore et al. | Dec 2007 | B2 |
| 7340759 | Rodriguez | Mar 2008 | B1 |
| 7376747 | Hartop | May 2008 | B2 |
| 7401153 | Traversat et al. | Jul 2008 | B2 |
| 7440573 | Lor et al. | Oct 2008 | B2 |
| 7447656 | Parthasarathy | Nov 2008 | B2 |
| 7450517 | Cho | Nov 2008 | B2 |
| 7450949 | Choksi | Nov 2008 | B2 |
| 7460549 | Cardei et al. | Dec 2008 | B1 |
| 7463890 | Herz | Dec 2008 | B2 |
| 7489656 | Guo et al. | Feb 2009 | B2 |
| 7530102 | Moskowitz | May 2009 | B2 |
| 7546342 | Li et al. | Jun 2009 | B2 |
| 7593333 | Li et al. | Sep 2009 | B2 |
| 7609748 | Karlsson | Oct 2009 | B2 |
| 7623524 | Muthukrishnan et al. | Nov 2009 | B2 |
| 7633908 | Kwong et al. | Dec 2009 | B1 |
| 7788133 | Delenda | Aug 2010 | B2 |
| 7817623 | Dawson et al. | Oct 2010 | B2 |
| 7830834 | Das et al. | Nov 2010 | B2 |
| 20010027484 | Nishi | Oct 2001 | A1 |
| 20010029182 | McCann et al. | Oct 2001 | A1 |
| 20020013767 | Katz | Jan 2002 | A1 |
| 20020029274 | Allen | Mar 2002 | A1 |
| 20020053033 | Cooper et al. | May 2002 | A1 |
| 20020053082 | Weaver et al. | May 2002 | A1 |
| 20020058499 | Ortiz | May 2002 | A1 |
| 20020061009 | Sorensen | May 2002 | A1 |
| 20020069278 | Forslöw | Jun 2002 | A1 |
| 20020071477 | Orava | Jun 2002 | A1 |
| 20020075940 | Haartsen | Jun 2002 | A1 |
| 20020102987 | Souisse et al. | Aug 2002 | A1 |
| 20020110110 | Tiihonen et al. | Aug 2002 | A1 |
| 20020120873 | Salmivalli | Aug 2002 | A1 |
| 20020122410 | Kulikov et al. | Sep 2002 | A1 |
| 20020141358 | Requena | Oct 2002 | A1 |
| 20020145978 | Batsell et al. | Oct 2002 | A1 |
| 20020173272 | Liang et al. | Nov 2002 | A1 |
| 20030032433 | Daniel et al. | Feb 2003 | A1 |
| 20030037033 | Nyman et al. | Feb 2003 | A1 |
| 20030053493 | Graham Mobley et al. | Apr 2003 | A1 |
| 20030068975 | Qiao et al. | Apr 2003 | A1 |
| 20030117978 | Haddad | Jun 2003 | A1 |
| 20030120594 | Shaginaw et al. | Jun 2003 | A1 |
| 20030137976 | Zhu et al. | Jul 2003 | A1 |
| 20030139180 | McIntosh et al. | Jul 2003 | A1 |
| 20030153338 | Herz et al. | Aug 2003 | A1 |
| 20030235174 | Pichna et al. | Dec 2003 | A1 |
| 20030235175 | Naghian et al. | Dec 2003 | A1 |
| 20040006621 | Bellinson et al. | Jan 2004 | A1 |
| 20040022224 | Billhartz | Feb 2004 | A1 |
| 20040029553 | Cain | Feb 2004 | A1 |
| 20040064351 | Mikurak | Apr 2004 | A1 |
| 20040078323 | Johnston et al. | Apr 2004 | A1 |
| 20040100929 | Garcia-Luna-Aceves | May 2004 | A1 |
| 20040128231 | Morita | Jul 2004 | A1 |
| 20040156312 | Salonidis et al. | Aug 2004 | A1 |
| 20040162871 | Pabla et al. | Aug 2004 | A1 |
| 20040165548 | Backes | Aug 2004 | A1 |
| 20040185777 | Bryson | Sep 2004 | A1 |
| 20040192204 | Periyalwar et al. | Sep 2004 | A1 |
| 20040203820 | Billhartz | Oct 2004 | A1 |
| 20040260808 | Strutt | Dec 2004 | A1 |
| 20040264466 | Huang | Dec 2004 | A1 |
| 20050063419 | Schrader et al. | Mar 2005 | A1 |
| 20050080872 | Davis et al. | Apr 2005 | A1 |
| 20050111418 | Yang et al. | May 2005 | A1 |
| 20050153725 | Naghian et al. | Jul 2005 | A1 |
| 20050157661 | Cho | Jul 2005 | A1 |
| 20050169209 | Miu et al. | Aug 2005 | A1 |
| 20050169257 | Lahetkangas et al. | Aug 2005 | A1 |
| 20050193221 | Yoneyama | Sep 2005 | A1 |
| 20050203834 | Prieston | Sep 2005 | A1 |
| 20050213503 | Guo et al. | Sep 2005 | A1 |
| 20060002326 | Vesuna | Jan 2006 | A1 |
| 20060034330 | Iwamura | Feb 2006 | A1 |
| 20060085543 | Hrastar et al. | Apr 2006 | A1 |
| 20060095582 | Nitya et al. | May 2006 | A1 |
| 20060109787 | Strutt et al. | May 2006 | A1 |
| 20060114853 | Hasty et al. | Jun 2006 | A1 |
| 20060126504 | Meier et al. | Jun 2006 | A1 |
| 20060167784 | Hoffberg | Jul 2006 | A1 |
| 20060176829 | McLaughlin et al. | Aug 2006 | A1 |
| 20060179143 | Walker et al. | Aug 2006 | A1 |
| 20060187858 | Kenichi et al. | Aug 2006 | A1 |
| 20060193295 | White et al. | Aug 2006 | A1 |
| 20060205408 | Nakagawa et al. | Sep 2006 | A1 |
| 20060224502 | McGowan | Oct 2006 | A1 |
| 20060233377 | Chang et al. | Oct 2006 | A1 |
| 20060274214 | Carro | Dec 2006 | A1 |
| 20060294258 | Powers-Boyle et al. | Dec 2006 | A1 |
| 20070005797 | Fontijn et al. | Jan 2007 | A1 |
| 20070019771 | Ambuehl et al. | Jan 2007 | A1 |
| 20070117537 | Hui et al. | May 2007 | A1 |
| 20070124204 | de Boer et al. | May 2007 | A1 |
| 20070140272 | Gulliksson | Jun 2007 | A1 |
| 20070206528 | Walton et al. | Sep 2007 | A1 |
| 20070258359 | Ogasawara et al. | Nov 2007 | A1 |
| 20070298764 | Clayton | Dec 2007 | A1 |
| 20080008140 | Forssell | Jan 2008 | A1 |
| 20080040481 | Joshi et al. | Feb 2008 | A1 |
| 20080104202 | Barrett et al. | May 2008 | A1 |
| 20080167982 | Leo et al. | Jul 2008 | A1 |
| 20080204448 | Dawson et al. | Aug 2008 | A1 |
| 20080281529 | Tenenbaum et al. | Nov 2008 | A1 |
| 20080298283 | Dawson et al. | Dec 2008 | A1 |
| 20080298314 | Dawson et al. | Dec 2008 | A1 |
| 20080301017 | Dawson et al. | Dec 2008 | A1 |
| 20090323587 | Trachewsky et al. | Dec 2009 | A1 |
| 20100008221 | Hong et al. | Jan 2010 | A1 |
| 20100205116 | Erlanger | Aug 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 0999662 | May 2005 | EP |
| 9915960 | Apr 1999 | WO |
| 03037009 | May 2003 | WO |
| 04001585 | Dec 2003 | WO |
| 2006004628 | Jan 2006 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20080300889 A1 | Dec 2008 | US |
