Source: http://www.google.com/patents/US8194701?dq=6,208,537
Timestamp: 2018-01-22 23:15:13
Document Index: 763962419

Matched Legal Cases: ['Application No. 200680045997', 'Application No. 2008', 'Application No. 10', 'Application No. 200680045997', 'Application No. 06846487', 'Application No. 06846507']

Patent US8194701 - System and/or method for downstream bidding - Google Patents
Digital objects may be transmitted to a destination via data networks. In particular, a node may facilitate bidding for the business of forwarding digital objects in a data transmission network. The node may receive a first bid request and generate a second bid request based on the first bid request....http://www.google.com/patents/US8194701?utm_source=gb-gplus-sharePatent US8194701 - System and/or method for downstream bidding
Publication number US8194701 B2
Application number US 11/296,828
Priority date Dec 6, 2005
Also published as CN101326777A, CN101326777B, EP1966953A2, EP1966953A4, US20070133553, WO2007067934A2, WO2007067934A3, WO2007067934A8
Publication number 11296828, 296828, US 8194701 B2, US 8194701B2, US-B2-8194701, US8194701 B2, US8194701B2
Inventors Shabbir Khan, Alexander Cohen
Original Assignee Lippershy Celestial Llc
Patent Citations (188), Non-Patent Citations (49), Referenced by (4), Classifications (22), Legal Events (4)
System and/or method for downstream bidding
US 8194701 B2
Digital objects may be transmitted to a destination via data networks. In particular, a node may facilitate bidding for the business of forwarding digital objects in a data transmission network. The node may receive a first bid request and generate a second bid request based on the first bid request. The second bid request may be transmitted to one or more intermediary nodes, and the node may receive one or more bids responsive to the second bid request. The node may subsequently receive and forward a digital object specified by the first bid request.
receiving from a first node within a computer network a first bid request to forward a specified digital object to a destination node via the computer network, wherein the first bid request is received by a second node that is an intermediary node within the computer network and that includes a computer system;
generating, at the second node, a second bid request to forward the specified digital object to the destination node via the computer network, wherein the second bid request is generated based, at least in part, on the first bid request;
transmitting the second bid request from the second node to one or more nodes downstream to the second node, including a third node that is another intermediary node within the computer network;
receiving, at the second node, a set of one or more bids that are responsive to the second bid request, wherein at least a first bid of the set of one or more bids is for forwarding the specified digital object from the second node to the destination node via the third node, wherein the first bid has been generated by the third node based, at least in part, on bid requests successively forwarded from the third node to nodes within the computer network, and on one or more bids received by the third node in response to the successively forwarded bid requests;
the second node computer system generating a second bid based, at least in part, on information in the first bid, wherein the generated second bid is responsive to the first bid request and is for forwarding the specified digital object from the first node to the destination node; and
transmitting the generated second bid from the second node to the first node.
2. The method of claim 1, further comprising identifying the one or more nodes downstream to the second node as capable of forwarding the specified digital object to a destination node, wherein said identifying is performed by the second node.
receiving, at the second node, a message indicative of the acceptance of the transmitted second bid; and
transmitting, from the second node, a message to one or more selected ones of the nodes downstream to the second node to accept at least one of the received set of one or more bids.
4. The method of claim 1, wherein the first node is a source node.
subsequent to an acceptance of the transmitted second bid, receiving the specified digital object at the second node; and
forwarding the specified digital object from the second node to at least one of the one or more nodes downstream to the second node according to the transmitted second bid.
6. The method of claim 5, wherein forwarding the specified digital object to at least one of the one or more nodes downstream to the second node further comprises:
formatting the specified digital object into one or more data packets;
associating the one or more data packets with a switch label; and
forwarding one or more of the data packets to a label switch router.
7. The method of claim 1, wherein the received set of one or more bids include price terms.
8. The method of claim 1, wherein the bid requests successively forwarded from the third node include a bid request sent to a fourth node, and wherein the fourth node has not directly received a bid request to forward the specified digital object from the second node.
9. The method of claim 1, wherein the first bid request is received from an Internet service provider.
10. The method of claim 1, wherein the first bid request is received from an intermediary node employing multiprotocol label switching (MPLS).
means for receiving from a first node within a computer network a first bid request to forward a specified digital object to a destination node via the computer network;
means for transmitting a second bid request from the apparatus to one or more nodes downstream to the apparatus, including a third node that is an intermediary node within the computer network, wherein the second bid request is to forward the specified digital object to the destination node and is based, at least in part, on the first bid request;
means for receiving a set of one or more bids that are responsive to the second bid request, wherein at least a first bid of the set of one or more bids is for forwarding the specified digital object from the apparatus to the destination node via the third node, wherein the first bid has been generated by the third node based, at least in part, on bid requests successively forwarded from the third node to nodes within the computer network, and on one or more bids received by the third node in response to the successively forwarded bid requests; and
means for transmitting a second bid to the first node, wherein the transmitted second bid is generated based, at least in part, on information in the first bid, wherein the generated second bid is responsive to the first bid request and is for forwarding the specified digital object from the first node to the destination node.
12. The apparatus of claim 11, further comprising means for identifying one or more intermediary nodes as capable of forwarding the specified digital object to the destination node.
13. The apparatus of claim 11, wherein the first node is a source node.
14. The apparatus of claim 11, further comprising means for receiving an indication of the acceptance of the transmitted second bid by the first node.
15. The apparatus of claim 14, wherein the first node is an intermediary.
16. The apparatus of claim 14, further comprising means for transmitting an acceptance message to at least one of the one or more nodes downstream to the apparatus in response to an indication of the acceptance of the transmitted second bid by the first node.
17. An article of manufacture including a non-transitory computer-readable storage medium having instructions stored thereon that are executable by a computing device to cause the computing device to perform operations comprising:
receiving from a first node a first bid request to forward a specified digital object to a destination node, wherein the first bid request is received by a second node that includes the computing device;
generating a second bid request to forward the specified digital object to the destination node, wherein the second bid request is generated based, at least in part, on the first bid request;
transmitting the second bid request to one or more intermediary nodes including a third node;
receiving a set of one or more bids from the one or more intermediary nodes that are responsive to the second bid request, wherein at least a first bid of the set of one or more bids is for forwarding the specified digital object from the computing device to the destination node via the third node, wherein the first bid has been generated by the third node based, at least in part, on bid requests successively forwarded from the third node to other nodes, and on one or more bids received by the third node in response to the successively forwarded bid requests;
generating a second bid based, at least in part, on information included in the first bid, wherein the generated second bid is responsive to the first bid request and is for forwarding the specified digital object from the first node to the destination node; and
transmitting the generated second bid to the first node.
18. The article of manufacture of claim 17, wherein the operations further include identifying the one or more intermediary nodes as capable of forwarding the specified digital object.
19. The article of manufacture of claim 17, wherein the operations further include receiving a message indicative of an acceptance of the transmitted second bid.
20. The article of manufacture of claim 17, wherein the first node is a source node and the one or more intermediary nodes do not include at least one destination node for a transmission of the specified digital object from a source node.
21. The article of manufacture of claim 17, wherein the operations further include:
22. The article of manufacture of claim 17, wherein the first bid request is received from an intermediary node employing multiprotocol label switching (MPLS).
23. The article of manufacture of claim 17, wherein the operations further include transmitting an acceptance message to at least one of the one or more intermediary nodes in response to the indication of acceptance of the transmitted bid.
24. The article of manufacture of claim 17, wherein one or more terms expressed in the received set of one or more bids include a price term.
a memory configured to couple to the processor, wherein the memory has stored thereon instructions executable by the processor to cause the computer system to perform operations comprising:
receiving, from a first node, a first bid request to forward a particular digital object to a destination node via a data transmission network;
generating, a second bid request to forward the particular digital object to the destination node via the data transmission network, wherein the second bid request is generated based, at least in part, on the first bid request;
receiving a set of one or more bids that are responsive to the second bid request, wherein at least a first bid of the set of one or more bids is for forwarding the particular digital object from the computer system to the destination node via the third node, wherein the first bid has been generated by the third node based, at least in part, on bid requests successively forwarded from the third node to other nodes within the data transmission network, and on one or more bids received by the third node in response to the successively forwarded bid requests;
generating a second bid to forward the particular digital object based, at least in part, on information in the first bid, wherein the generated second bid is responsive to the first bid request and is for forwarding the particular digital object from the first node to the destination node; and
transmitting the generated bid to the first node.
26. The computer system of claim 25, wherein the computer system is further configured to identify the one or more intermediary nodes as capable of forwarding the particular digital object;
wherein the first node from which the first bid request is received is a source node; and
wherein the computer system is an intermediary node.
27. The computer system of claim 25, wherein the computer system is further configured to:
receive from the first node a first message indicative of an acceptance of the transmitted second bid by the first node; and
transmit a second message to one or more selected ones of the intermediary nodes in response to receiving the first message, wherein the second message is indicative of the computer system accepting at least one of the received set of one or more bids.
28. The computer system of claim 25, further comprising a label switch router configured to:
receive the particular digital object from the first node; and
forward the particular digital object to at least one of the one or more intermediary nodes.
29. The computer system of claim 25, further comprising a label switch router configured to:
receive the particular digital object as one or more data packets; and
forward one or more of the data packets to a downstream label switch router.
30. The computer system of claim 25, wherein the computer system is controlled by an Internet service provider.
31. The computer system of claim 25, wherein the computer system is an intermediary node and is further configured to forward the particular digital object to a plurality of other nodes based, at least in part, on an indication of acceptance of the transmitted second bid received from the first node.
32. The computer system of claim 25, wherein the computer system is further configured to transmit an acceptance message to at least one of the one or more intermediary nodes in response to an indication of acceptance of the transmitted second bid received from the first node.
33. The computer system of claim 25, wherein one or more terms expressed in the received set of one or more bids includes an expected delivery time for the particular digital object.
The subject matter disclosed herein relates to the transmission of digital objects in a data transmission network.
Information exchange mechanisms using the Internet have been available for free for many services. To forward information from a source node to a destination node, one or more intermediary parties may forward the information over at least a portion of a path coupling the source node to the destination node. Such intermediary parties typically own, lease, control and/or operate equipment such as routers and/or the like for forwarding information according to a network protocol such as the Internet Protocol. The intermediary parties incur substantial costs in the deployment, maintenance and operation of equipment for the purpose of forwarding information to a destination node.
Non-limiting and non-exhaustive embodiments of the present invention will be described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.
FIG. 1 is a schematic diagram of a data transmission network according to an embodiment.
FIG. 2 is a schematic diagram of a router that may be owned, leased, controlled and/or operated by an intermediary for transmitting at least a portion of a digital object to a destination node according to an embodiment.
FIG. 3 is schematic diagram of a data transmission network for transmitting a digital object to two or more destination nodes according to an embodiment.
FIG. 4 is a flow diagram illustrating a process to initiate transmission of a digital object from a source node according to an embodiment.
FIG. 5 is a flow diagram illustrating a process to act upon a bid request received at an intermediary according to an embodiment.
FIG. 6 is a schematic diagram of a data transmission network for transmitting a digital object from a source node to a destination node through two or more intermediaries.
FIG. 7 is a flow diagram illustrating a process to act upon a bid request received at an intermediary according to an embodiment.
FIG. 8 is a schematic diagram of a data transmission network comprising a first network to transmit a digital object from a source node to a destination node and second network to facilitate bidding among intermediaries.
FIG. 9 is a flow diagram illustrating a process to initiate transmission of a digital object to one or more destination nodes according to an embodiment of the data transmission network of FIG. 8.
FIG. 10 is a flow diagram illustrating a process to facilitate bidding for the service of forwarding a digital object to one or more destination nodes according to an embodiment of the data transmission network of FIG. 8.
A “data transmission network” as referred to herein relates to infrastructure that is capable of transmitting data among nodes which are coupled to the data transmission network. For example, a data transmission network may comprise links capable of transmitting data between nodes according to one or more data transmission protocols. Such links may comprise one or more types of transmission media capable of transmitting information from a source to a destination. However, these are merely examples of a data transmission network and claimed subject matter is not limited in these respects.
In the transmission of data in a data transmission network, a “source node” may initiate transmission of data to one or more “destination nodes” coupled to the data transmission network. In one particular embodiment, although the claimed subject matter is not limited in this respect, a source node may initiate the transmission of data to the destination node based, at least in part, upon a destination address associated with the destination node. Here, according to a communication protocol of a particular embodiment, the source node may transmit data to the destination node in one or more “data packets” which are routed to the destination node through the data transmission network based, at least in part, on the destination address. However, these are merely examples of how data may be transmitted from a source node to a destination node in a data transmission network and claimed subject matter is not limited in these respects.
A node in a data transmission network may “forward” information to one or more other nodes in the data transmission network over data links. In one particular example, a first node may forward information to a second node by transmitting one or more data packets according to a communication protocol. Such data packets may comprise a header portion containing an address of an intended destination node and a payload containing forwarded information. If the second node is not the ultimate intended destination, the second node may also forward the data packets to a third node which comprises and/or is coupled to the ultimate intended destination node. However, these merely examples of how information may be forwarded in a data transmission network and claimed subject matter is not limited in these respects.
A “digital object” as referred to herein relates to information that is organized and/or formatted in a digitized form. For example, a digital object may comprise one or more documents, visual media and/or audio media, and/or combinations thereof. However, these are merely examples of the types of information that may be maintained in a digital object and claimed subject matter is not limited in this respect. Such a digital object may be maintained in a compressed format to enable efficient storage of the digital object in a storage medium and/or transmission of the digital in a data transmission network. In other embodiments, such a digital object may be encrypted for transmission in a secure communication channel. In one particular embodiment, although the claimed subject matter is not limited in this respect, a digital object may be formatted at a source node for transmission to one or more destination nodes. Also, a digital object may be transmitted to one or more destination nodes as one or more data packets routed to the one or more data nodes according to a communication protocol. However, these are merely examples of a digital object and claimed subject matter is not limited in these respects.
A “bid” as referred to herein relates to an expression of a proposal to perform a service. In one particular example, a customer and/or client may receive bids from more than one party competing for the business of the customer and/or client. A bid may specify terms under which a service may be performed such as, for example, price, quality, timeliness and/or reliability. However, these are merely examples of terms that may be expressed in a bid and claimed subject matter is not limited in this respect. Also, in some commercial contexts, acceptance of a bid by a customer and/or client may be binding on the parties. In other commercial contexts, however, acceptance of a bid by a customer and/or client, in and of itself, may not be binding. Here, additional actions by one or more parties may result in a binding arrangement. It should be understood that these are merely examples of a bid and claimed subject matter is not limited in this respect.
A “bid request” as referred to herein relates to an expression of an invitation to provide a bid for performing a service. In one particular example, such a bid request may specify a desired service to be performed by a service provider. In some embodiments, the bid request may specify some of the terms, but not necessarily all of the terms, under which a desired service is to be performed. However, these are merely examples of a bid request and claimed subject matter is not limited in these respects.
In response to receipt of a bid from a service provider for providing a service, a potential customer and/or client may provide an “acceptance message” to the bidding service provider. Such an acceptance message may express a willingness of the customer and/or client to receive services from the service provider according to at least some terms set forth in the received bid. However, this is merely an example of an acceptance message and the claimed subject matter is not limited in this respect.
According to an embodiment, two or more parties may exchange messages in the course of agreeing to terms under which a service may be provided according to a “negotiation protocol.” In one particular embodiment, although claimed subject matter is not limited in this respect, a negotiation protocol may define how parties express a bid, bid request and/or acceptance message. In another embodiment, parties may exchange messages according to a negotiation protocol until a particular predefined state and/or event defining closure. Here, such a closure may define agreed terms under which a service is to be provided. It should be understood, however, that these are merely examples of a negotiation protocol and claimed subject matter is not limited in these respects.
In forwarding a digital object from a source node to a destination node over a data transmission network, equipment which is owned, leased, controlled and/or operated by one or more “intermediaries” or “intermediary parties” may forward at least a portion of the digital object over at least a portion of the data transmission network toward the destination node. As illustrated below, the term “intermediary” may refer to a party that may forward a digital object over at least a portion of the data transmission network and/or equipment that is owned, leased, controlled and/or operated by the party for performing this service.
Equipment that is owned, leased, controlled and/or maintained by an intermediary may comprise equipment that is capable of transmitting information to and/or receiving information a data transmission network. Here, such equipment may comprise one or more “communication ports” capable of receiving information from a source node and/or transmitting information to a destination node over one or more data transmission mediums forming links in the data transmission network. Such a communication port may be capable of transmitting and/or receiving information from any one of several types of data transmission media such as, for example, cabling (e.g., optical, coaxial, unshielded twisted wire pair cabling, etc.) and/or wireless transmission media (e.g., by terrestrial or satellite links). However, these are merely examples of a communication port that may couple equipment which is owned, leased controlled and/or operated by an intermediary to a data transmission network, and claimed subject matter is not limited in these respects.
“Storage medium” as referred to herein relates to media capable of maintaining expressions which are perceivable by one or more machines. For example, a storage medium may comprise one or more storage devices for storing machine-readable instructions and/or information. Such storage devices may comprise any one of several media types including, for example, magnetic, optical or semiconductor storage media. However, these are merely examples of a storage medium and claimed subject matter is not limited in these respects.
“Logic” as referred to herein relates to structure for performing one or more logical operations. For example, logic may comprise circuitry which provides one or more output signals based upon one or more input signals. Such circuitry may comprise a finite state machine which receives a digital input and provides a digital output, or circuitry which provides one or more analog output signals in response to one or more analog and/or digital input signals. Such circuitry may be provided in an application specific integrated circuit (ASIC) or field programmable gate array (FPGA). Also, logic may comprise machine-readable instructions stored in a storage medium in combination with processing circuitry to execute such machine-readable instructions. However, these are merely examples of structures which may provide logic and claimed subject matter is not limited in this respect.
An “agent” as referred to herein relates to a process that executes on a first device and is capable of communicating with a second device over a data transmission network. In one particular embodiment, for example, an agent process may collect information associated with the first device and enable transmission of the collected information to the second device. In another embodiment, an agent may receive control signals from the second device to enable remote control of at least one aspect of the first device. However, these are merely examples of how an agent may enable communication between devices and the claimed subject matter is not limited in these respects. In another embodiment, an agent may execute on a processor under the control of machine-readable instructions stored on a storage medium. In another embodiment, an agent may be executed on different types of structure that provide logic. However, these are merely examples of an agent and claimed subject matter is not limited in these respects.
A “quality of service” (“QoS”) as referred to herein relates to a characteristic of a data transmission service to provide data to a recipient within particular constraints. In particular examples, although claimed subject matter is not limited in this respect, QoS may refer to delivery of a service within expected bandwidth constraints, time constraints and/or error constraints. A quality of service may refer to a characteristic of a transmission control protocol/internet protocol (TCP/IP) type protocol, and/or a user datagram protocol/internet protocol (UDP/IP) type protocol. In one or more embodiments, a quality of service may refer to a threshold error transmission rate, for example where one or more data packets may not arrive, and/or where one or more data packets that do arrive may include one or more corrupted bits of information. In one or more embodiments, a quality of service may refer to where no errors and/or no error rate is acceptable, and/or to a threshold where the number of errors and/or the error rate may not exceed a predetermined value, and/or to a range within which a number of errors and/or an error rate may be acceptable, although the scope of claimed subject matter is not limited in this respect. In a particular embodiment, for example, a QoS may be associated with the transmission of a digital object from a source node to a destination node. Here, for example, a QoS may dictate that all or a portion of the digital object arrive at the destination node within a defined bandwidth limits, and/or within some time constraint, and/or with or without number of errors and/or within error rate limits. In another embodiment, a QoS may define, at least in part, an effective data rate at which a digital object is to be transmitted to the destination node. However, this is merely an example of how QoS may be applied in the transmission of a digital object and claimed subject matter is not limited in this respect.
Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “selecting,” “forming,” “enabling,” “inhibiting,” “identifying,” “initiating,” “receiving,” “transmitting,” “determining” and/or the like refer to the actions and/or processes that may be performed by a computing platform, such as a computer or a similar electronic computing device, that manipulates and/or transforms data represented as physical electronic and/or magnetic quantities and/or other physical quantities within the computing platform's processors, memories, registers, and/or other information storage, transmission, reception and/or display devices. Further, unless specifically stated otherwise, process described herein, with reference to flow diagrams or otherwise, may also be executed and/or controlled, in whole or in part, by such a computing platform.
FIG. 1 is a schematic diagram of a data transmission network 25 according to an embodiment. A source node 2 and destination nodes 18 through 24 may access data transmission network 25 using any one of several data transmission access technologies such as, for example, public switched telephone network (PSTN), digital subscriber line (DSL), coaxial/optical cable or wireless access (e.g., using satellite and/or terrestrial links). However, these are merely examples of how a node may obtain access to a data transmission network and claimed subject matter is not limited in these respects. Data transmission network 25 may be capable of transmitting data packets among nodes in a network topology according to an Internet Protocol (IP). However, this is merely an example of a communication protocol that may be used in transmission of all or portions of a digital object from a source node to a destination node and claimed subject matter is not limited in this respect. Here, in a particular embodiment illustrated in FIG. 1, source node 2 and destination nodes 18 through 24 may access data network 25 through the facilities of Internet service providers (ISPs) 10 and 16. For example, source node 2 and/or destination nodes 18 through 24 may comprise subscribers of corresponding ISPs that enable access to data transmission network 25 for a subscription fee. However, an ISP is merely an example of how a source and/or destination node may access a data transmission network and claimed subject matter is not limited in this respect.
According to an embodiment, source node 2 and/or destination nodes 18 through 24 may comprise any one of several types of devices which are capable of transmitting and/or receiving digital objects. In one particular example, source node and/or destination nodes 18 through 24 may comprise a communication port (not shown) that is adapted for transmitting data to and/or receiving data from an ISP through a data transmission medium using one or more of the aforementioned access technologies. In addition to communication ports, source node 2 and/or destination nodes 18 through 24 may also comprise a computing platform employing a processor, one or more memory devices and appropriate input/output devices for communicating between processes executing on the processor and communication ports. Here, such processes executing on a computing platform may be controlled, at least in part, by machine-readable instructions stored in one or more memory devices of the computing platform. In one particular embodiment, a computing platform at source node 2 may execute one or more processes to create and/or format a digital object for transmission on data transmission network 25. However, this is merely an example of how a source node 2 may create and/or format a digital object for transmission on a data transmission network and claimed subject matter is not limited in this respect. In another particular embodiment, a computing platform at a destination node may execute one or more processes to utilize a digital object received from data transmission network 25 through a communication port. However, this is merely an example of how a destination node may process a digital object received from a data transmission network and claimed subject matter is not limited in this respect.
According to an embodiment, equipment that is owned, leased, controlled and/or operated by intermediaries 12 may transmit digital objects between ISPs 10 and 16. Links coupling the intermediary equipment to ISPs 10 and 16 may comprise any one of several data transmission mediums such as, for example, cabling (e.g., fiber optic, coaxial and/or unshielded twisted wire pair cabling) and/or wireless transmission media (e.g., using terrestrial and/or satellite based links). However, these are merely examples of transmission media that may be used to transmit digital objects in a data transmission network and claimed subject matter is not limited in these respects.
As illustrated in FIG. 1, ISP 10 may transmit a digital object to ISP 16 in any one of multiple paths comprising at least one corresponding intermediary 12. Here, according to a particular embodiment, ISP 10 may transmit a digital object to ISP 16 through any one of the intermediaries 12 a, 12 b and/or 12 c. As discussed below, according to a particular embodiment, source node 2 and/or ISP 10 may select a particular intermediary 12 to forward the digital object to the ISP 16 based, at least in part, upon one or more bids received from intermediaries 12 a, 12 b and/or 12 c. However, this is merely an example of how an intermediary may be selected for forwarding a digital object and claimed subject matter is not limited in this respect.
According to an embodiment, although claimed subject matter in not limited in this respect, intermediaries 12 may route digital objects between ISPs 10 and 16 in one or more data packets formatted according to a particular network protocol such as an Internet Protocol (IP). Such data packets may be forwarded on data links connecting intermediaries 12 and ISPs according to any one of several data link layer protocols such as, for example, Ethernet, Asynchronous Transfer Mode (ATM), Frame Relay and/or Synchronous Optical NETwork/Sychronous Digital Hierarchy (SONET/SDH) data link protocols. In embodiments employing wireless communication links, data packets may be forwarded on such wireless communication links according to any one of several satellite and/or terrestrial wireless data link protocols such as, for example, IEEE Stds. 802.11, and 802.16. However, these are merely examples of data link protocols that may be used to forward data packets in a data transmission network and claimed subject matter is not limited in this respect.
According to an embodiment, an intermediary 12 may comprise one or more routers for forwarding data packets originating at source node 2 to destination nodes. FIG. 2 is a schematic diagram of a router 28 which may be owned, leased and/or operated at an intermediary for transmitting at least a portion of a digital object to a destination node according to an embodiment. Router 28 may comprise one or more ingress communication ports 24 to receive data packet communications according to one or more of the aforementioned protocols. Here, one or more of ingress communication ports 24 may be capable of receiving all or a portion of a digital object from ISP 10 (and originating at source node 2). Router 28 may also comprise one or more egress communication ports 26 to transmit data packet communications according to one or more of the aforementioned protocols. Here, one or more of egress communication ports 26 may be capable of transmitting all or a portion of a digital object to ISP 16 (to then be forwarded to one or more destination nodes).
According to an embodiment, router 28 may comprise logic to determine how to forward packets received on ingress communication ports 24 to egress communication ports 26. For example, router 28 may determine an egress communication port 26 for forwarding a received data packet based, at least in part, on information associated with the received data packet such as, for example, a destination address. Here, according to a particular embodiment, router 28 may determine an egress port 26 for forwarding the received data packet according to one or more look up tables associating destination IP address with egress ports 26. However, this is merely an example of how a router may determine an egress port for forwarding a data packet and claimed subject matter is not limited in this respect. Notwithstanding the existence of a valid destination address associated with a received data packet, according to an embodiment, router 28 may also select whether or not to forward a received data packet based, at least in part, on information such as destination and/or source associated with the data packet, or other information associated with the data packet.
According to an embodiment, the aforementioned logic of router 28 to control routing data packets from an ingress communication port 24 to an egress communication port 26 may comprise one or more computing platforms comprising one or more processors and memory devices. The memory devices may comprise machine-readable instructions to execute on the one or more processors for controlling the routing of data packets. Alternatively, router 28 may comprise one or more ASIC devices to control routing, and/or combinations of one or more ASIC devices and one or more computing platforms to control routing. However, these are merely examples of logic that may be employed in a router for controlling forwarding of data packets and claimed subject matter is not limited in these respects.
According to an embodiment, an intermediary 12 (FIG. 1) may employ more than one router 28 to forward a digital object to a destination node. A digital object received from source node 2 at a first router may be forwarded to a second router where both first and second routers are owned, leased, controlled and/or operated by intermediary 12. Here, the first router may receive the digital object from the ISP 10 and forward the received digital object to the second router either directly to the second router or via one or more other routing devices. The second router may then forward to ISP 16 the digital object received from the first router. However, this is merely an example of how an intermediary may employ multiple routers for forwarding a digital object from a source node to a destination node, and claimed subject matter is not limited in this respect.
According to an embodiment, the intermediaries 12 and/or ISPs 10 and 16 may employ multiprotocol label switching (MPLS) according to the MPLS Architecture set forth in Internet Engineering Task Force (IETF), Network Working Group, RFC 3031, 2001. Here, ISP 10 may comprise a “label edge router” (LER) that is capable of assigning label values to packets received from source node 2 for transmission to a destination node. One or more routers of the intermediaries 12 may comprise a “label switch router” (LSR) to make forwarding decisions for received data packets based, at least in part, upon label values assigned to the received data packets. At a network hop between ISP 10 and ISP 16, an LSR associated with an intermediary 12 may strip off an existing label of a received data packet and apply a new label indicating how the next downstream LSR is to forward the data packet to a destination. LSRs coupled to forward a digital object from ISP 10 to ISP 16 may then form a Label Switch Path (LSP) determined, at least in part, according to labels (e.g., selected from a hierarchy of labels such as a label stack) assigned to data packets transporting a digital object at network hops between ISP 10 and ISP 16. However, this is merely an example of how a digital object may be transmitted between nodes on a data transmission network using MPLS and claimed subject matter is not limited in these respects.
FIG. 3 is schematic diagram of a data transmission network 100 for transmitting a digital object to two or more destination nodes according to an embodiment. A source node 102 may transmit a digital object to more than one destination node coupled to one or more ISPs 116. Two or more intermediaries 112 may then be employed to forward the digital object to two or more destinations. According to an embodiment, a digital object formatted for transmission to a destination node may be copied at either the ISP 110 or an intermediary 112 for transmission to multiple destinations.
According to an embodiment, a digital object may be segmented and/or partitioned in to smaller sub-digital objects for transmission through two or more intermediaries. Here, in a particular embodiment, a sub-digital object may range in size from being as large as the larger digital object, as small as a null object containing no data, or of an intermediate size containing, for example, packet, sub-packet, aggregation of packets and/or an aggregation of bits forming the sub-digital object. According to an embodiment, although claimed subject matter is not limited in this respect, sub-digital objects forming a digital object may be independently transmitted through a data transmission network to a destination using the same or different paths. Subject to any QoS requirements, for example, intermediaries may bid for the service of forwarding individual sub-digital objects of a larger digital object as described herein. Here, for example, a digital object may be sufficiently large such that it may be desirable to split the digital object into one or more sub-digital objects, for example at source node and/or at one or more of intermediary nodes, where one or more of the sub-digital objects may be provided with its own individual routing requirements, quality of service, routing paths, and so on, and where the sub-digital objects may be reassembled at one or more of intermediary nodes and/or one or more of destination nodes. Such a sub-digital object concept in one or more embodiments may be analogous to data transfer utilizing packets, where the sub-digital objects may be at a higher level of organization that a packets, but may be at a lower level of organization that of a larger digital object. For example, a multimedia object may be split into a video sub-digital object and an audio sub-digital object, and/or a multimedia object may be split into a sub-digital objects corresponding to the scenes contained in the multimedia object, although the scope of claimed subject matter is not limited in this respect. An example of such a digital object that may be suitable for being split up into one may be where the digital object is a movie. In one or more embodiments, a transmission of such an object may include a multiple input, multiple output (MIMO) transmission system and/or a spatial division, multiple access system, for example where two or more sub-objects may be transmitted in parallel in two or more links. In one particular embodiment, a network that may be suitable for splitting a digital object into one or more sub-digital objects may comprise at least a portion of the network operating in compliance with an Institute of Electrical and Electronics Engineers (IEEE) 802.16 type standard such as a WiMax type standard, although the scope of claimed subject matter is not limited in this respect.
As in data transmission network 25 illustrated above, an intermediary 112 may comprise one or more routers (such as router 28, for example) to forward data packets to a destination node. Also, data transmission network 100 may employ MPLS and select particular intermediaries for forwarding a digital object to destinations.
In the particular embodiment shown in FIG. 3, a single intermediary 112 b may be capable of forwarding a digital object from ISP 110 to destination nodes coupled to any of the ISPs 116 a, 116 b and/or 116 c. On the other hand, neither intermediary 112 a nor intermediary 112 c may, by itself, be capable of forwarding a digital object to destination nodes coupled to all three ISPs 116 a, 116 b and 116 c. To forward the digital object to destination nodes coupled to all three ISPs, the ISP 110 and/or source node 102 may select either the intermediary 112 b, or intermediaries 112 a and 112 c.
According to embodiments of data transmission networks shown in FIG. 1 and/or FIG. 3, an intermediary may incur a cost for forwarding a digital object from in at least a portion of a data transmission network. To offset such a cost, an intermediary may receive compensation from a party associated with a source node, ISP and/or destination in exchange for forwarding a digital object over a portion of the network. According to an embodiment, an intermediary may provide a bid specifying terms under which the intermediary would forward a digital object over at least a portion of a data transmission network. A party that is to compensate an intermediary may select from among multiple bids for the business of forwarding the digital object over at least a portion of the network. However, this is merely an example embodiment and claimed subject matter is not limited in these respects.
According to an embodiment, any node such as intermediary nodes and/or ISP acting on behalf of another node such as source node, intermediary nodes, ISP and/or destination node 118, for example, may request transmission of a digital object. Likewise, a source node and/or destination node may together request and/or otherwise agree to transmit a digital object, for example as a result of a handshake between the source node and/or destination node, and/or between at least one of the source node and/or destination node, intermediary nodes, and/or one or more proxy nodes. In one or more embodiments, a handshake may refer to a challenge handshake authentication protocol (CHAP) type authentication between a network server and a client device, although the scope of claimed subject matter is not limited in this respect. A handshake may occur via direct communication between two or more nodes, and/or alternatively a handshake may occur via indirect communication between two or more nodes, for example using electronic mail or other suitable protocol. In one or more embodiments, a “proxy server” may refer to a server, node, and/or client device that may operate to provide, implement, process and/or intercept requests on behalf of given other server, node, and/or client device, and/or to operate interposed between a first server, node, and/or client device and second server, node, and/or other client device. Such a proxy sever may operate to provide, implement, process, and/or intercept a request on behalf of and/or in lieu of at least one of such a server, node, and/or client device, and/or may operate as an agent of at least one of such a server, node, and/or client device, and in one or more embodiments may appear to other servers, nodes, and/or client devices on a data transmission network as though it were in fact the server, node, and/or client device for which such a proxy may be acting as an agent thereof. Such a proxy server and/or an agent may be implemented on any one or more of a source node, source ISP, intermediary nodes, destination ISP, and/or destination nodes, and/or on other nodes on a data transmission network. In one or more embodiments, such a proxy server and/or agent may be utilized to implement one or more specialized functions as part of the overall process and/or processes for transmitting a digital object via a data transmission network. For example, if a digital object were a larger sized object that could be partitioned into one or more smaller sized sub-digital objects and/or packets for more efficient transmission, a proxy server dedicated to such partitioning of a digital object may be utilized. Other such specialized functions of a proxy server and/or agent may exist, for example compression, decompression, recombining, and so on. However, these are merely examples of how a proxy server and/or agent may operate on a data transmission network, and the scope of claimed subject matter is not limited in these respects.
FIG. 4 is a flow diagram illustrating a process 200 to initiate transmission of a digital object from a source node according to embodiments of data transmission networks 25 and 100. All or some portions of process 200 may be performed by logic at a source node. In one particular embodiment, as illustrated below, portions of process 200 may be performed at a proxy server (e.g., at an ISP or other unidentified node in a data transmission network) that is capable of communicating with a source node and one or more intermediaries. At block 202, a source node may form a digital object for transmission to one or more destination nodes. In a particular embodiment, a computer operator may form the digital object through interactions with a graphical user interface (GUI) of a computing platform associated with and/or coupled to the source node. However, this is merely an example of how a digital object may be formed and claimed subject matter is not limited in these respects. In one particular embodiment, the digital object may be formatted into one or more data packets according to a network protocol such as the IP protocol. As such, the one or more data packets may comprise a header portion with a destination IP address associated with a destination node. If the digital object is to be transmitted to more than one destination node, block 202 may format multiple sets of data packets for corresponding destination nodes with corresponding destination IP addresses. According to particular embodiments, although claimed subject matter is not limited in these respects, such multiple sets of data packets may be copied for transmission to corresponding multiple destination at a source node, ISP and/or intermediary. However, these are merely examples of where copies of data packets of digital object may be made for transmission to multiple destinations, and claimed subject matter is not limited in these respects.
A particular intermediary in a data transmission network may or may not be capable of transmitting a digital object to a destination node. In the particular embodiment of data transmission network 100 shown in FIG. 3, for example, there is no link connecting intermediary 112 a with ISP 116 c, and no link connecting intermediary 112 c with ISP 116 a. Accordingly, intermediary 112 a may be deemed incapable of forwarding digital objects to destination nodes 118 c, 120 c and/or 122 c. Likewise, intermediary 112 c may be deemed incapable of forwarding digital objects to destination nodes 118 a, 120 a and 122 a. In other embodiments, an intermediary may or may not be capable of forwarding a digital object to a destination based, at least in part, on other factors regardless of whether the intermediary is connected to a source and/or destination node by a link. Here, for example, such an intermediary node may be deemed incapable based, at least in part, on known equipment failures, inability to forward the digital object according to a desired QoS, and the like. However, these are merely examples of how and/or why an intermediary may be incapable of forwarding a digital object to destination and claimed subject matter is not limited in these respects.
At block 204 the source node and/or a proxy server may identify intermediaries that are capable of forwarding a digital object to one or more destination nodes. In one embodiment, a source node and/or proxy server may identify intermediaries that are capable of forwarding a digital object based, at least in part, on information in a database. Such a database may be maintained at a source node and/or proxy server and may identify particular intermediaries that are connected to the source node and capable of receiving digital object for forwarding. Such a database may also associate information with intermediaries such as, for example, capability to forward digital objects while achieving a certain QoS, operational status (e.g., functioning, down for maintenance, malfunctioning, etc.) and information indicative of destinations to which intermediaries may forward digital objects. However, this is merely an example of information that may be associated with intermediaries in a database for the purpose of identifying intermediaries which are capable of forwarding digital object to a destination and claimed subject matter is not limited in this respect.
At block 206, a source node and/or proxy server may initiate the transmission of bid requests to one or more intermediaries, requesting bids for a service of forwarding the digital object to one or more destination nodes. Here, a bid request may be transmitted through an in-band management channel of links that carry data packets of digital objects transmitted between a source and an intermediary. Alternatively, a bid request may be transmitted to the intermediary in a link that is separate from a link carrying digital objects. A source node and/or proxy server may transmit bid requests to intermediaries according to any one of several communication protocols. In one particular embodiment, for example, a source node and/or proxy server may transmit bid request in one or more data packets using a user datagram protocol/Internet protocol (UDP/IP). However, these are merely examples of how a source node and/or proxy server may transmit a bid request to one or more intermediaries and claimed subject matter is not limited in these respects.
According to an embodiment, a digital transmission form (DTF) may comprise metadata associated with a digital object that may be separately stored, represented and/or transmitted independently of the associated digital object. In particular embodiments, although claimed subject matter is not limited in this respect, DTFs associated with digital objects may be transmitted among nodes in a data transmission network (e.g., source node, ISPs and/or intermediaries) using the data paths used for transmitting the digital objects. In alternative embodiments, DTFs associated with digital objects may be transmitted among nodes in a data transmission using data paths that are distinct from data paths used for transmitting digital objects. However, these are merely examples of how DTFs may be transmitted among nodes in a data transmission network and claimed subject matter is not limited in these respects.
According to a particular embodiment, a bid request may be formatted as DTF that may be transmitted in one or more messages according to a negotiation protocol. Here, a DTF may comprise predefined fields that specify terms of a bid request for the service of transmitting a digital object to a destination node. Such predefined fields may be used for providing information to a bidding party such as, for example, size of the digital object to be transmitted (e.g., in bits, bytes, cells, packets, etc.), destination address(es), QoS, compression format, security, encryption, billing account number and/or the like. Alternatively, a DTF may comprise a reference to a pre-defined field definition schema and/or the schema itself, and/or the field values expressed in a format, e.g., XML. However, these are merely examples of predefined fields that may be used in DTF for providing a bid request and claimed subject matter is not limited in these respects.
As pointed out above, a DTF may facilitate a process of bidding for a service of forwarding an associated digital object to a destination. In addition to forwarding digital objects as consequence of bidding, in particular embodiments, although claimed subject matter is not limited in this respect, a data transmission network may permit the forwarding of other data traffic that does not require acceptance of a bid as a consequence of formation and/or transmission of a DTF. Here, for example, parties may have existing agreements and/or routes to forward traffic that obviates a need for bidding. However, this is merely an example of how a data transmission network may forward data traffic without the use of a DTF and claimed subject matter is not limited in this respect.
As discussed above, a source node may forward a digital object to more than one destination node. Also, as pointed out above, certain intermediaries may not be capable of forwarding a digital object to all intended destination nodes. Accordingly, in a particular embodiment, different bid request messages may be forwarded to different intermediaries based, at least in part, on known abilities of particular intermediaries in forwarding the digital object to particular destinations (e.g., as determined at block 204). Referring to the example of FIG. 3, according to a particular embodiment, source node 102 may format a digital object for transmission to destination nodes 118 a, 118 b and 118 c. Intermediary 112 a may receive one or more bid requests for forwarding the digital object to destination nodes 118 a and 118 b, but not for forwarding the digital object to destination node 118 c. Likewise, intermediary 112 c may receive one or more bid requests for forwarding the digital object to destination nodes 118 b and 118 c, but not for forwarding the digital object to destination node 118 a.
In embodiments illustrated above, block 204 may identify one or more intermediaries that are capable of forwarding a digital object to a destination node. In alternative embodiments, however, block 206 may forward bid requests to any identifiable intermediary nodes, regardless of whether such intermediary nodes are determined to be capable of providing a desired service. This enables the intermediaries to determine for themselves as to whether they are capable forwarding the digital object to the destination under the terms of the bid. Accordingly, use of block 204 in identifying capable intermediaries is merely an optional embodiment, and claimed subject matter is not limit in these respects.
After a time period following transmission of bid requests to intermediaries at block 206, source node and/or proxy server may receive one or more bids from one or more intermediaries expressing an ability and/or willingness to forward a digital object to one or more destination according to terms set forth in the one or more received bids. Such terms in the bid may include, for example, price, QoS, expected delivery time and/or maximum latency. However, these are merely examples of terms that an intermediary may provide in a bid for the transmission of a digital object to one or more destination, and claimed subject matter is not limited in this respect.
Upon receipt of one or more bids from one or more intermediaries, a source node and/or proxy server may process received bids at block 208. Block 208 may select one or more intermediaries to forward the digital object to one or more destination nodes based, at least in part, on one or more received bids. In one particular embodiment, to forward a digital object to a particular destination node, block 208 may select an intermediary specifying a lowest price in its bid for this service. Alternatively, block 208 may select an intermediary specifying a lowest bid for a minimum specified QoS associated with forwarding the digital object to the destination node. In one particular embodiment, although claimed subject matter is not limited in this respect, acceptance and/or rejection of a bid, and/or termination of a biding process may be determined, at least in part, on a predetermined negotiation protocol. Here, for example, such a negotiation protocol may determine a format for bids, mechanisms to reject bids arriving late (e.g., after a timeout period), rejection of bids because a party soliciting a bid has pre-existing relationships with other intermediaries to provide a service of forwarding a digital object, and/or the like.
A negotiation protocol may also define multiple message types including, for example, bid requests, bids, acknowledgement of a bid request and/or bid, rejection and/or acceptance of a bid, broadcasting results of a bid request and subsequent bids, and/or changes for future bidding for the service of forwarding a digital object. However, these are merely examples of messages that may be defined as part of a negotiation protocol and claimed subject matter is not limited in these respects.
Upon selecting an intermediary to forward a digital object to a destination node, the source node and/or proxy server may initiate the selected intermediary to forward data packets carrying the digital object to one or more destination nodes. In a particular embodiment employing the aforementioned MPLS protocol, for example, the source node and/or proxy server may intiate a node in a data transmission network (e.g., source node or ISP connected to source node) to act as an LER. Here, such an LER may associate data packets carrying a digital object with a switch label identifying the digital object and how the digital object is to be processed by a recipient LSR. The LER may then forward data packets carrying the digital object to an ingress communication port of router acting as an LSR and which is owned, leased, controlled and/or operated by the selected intermediary. However, this is merely an example of how such a selected intermediary may be set to forward data packets carrying a digital object to a destination node and claimed subject matter is not limited in this respect.
FIG. 5 is a flow diagram illustrating a process embodiment 300 to act upon a bid request received at an intermediary according to an embodiment. Process embodiment 300 may be executed by logic associated with an intermediary such as, for example, a computer system as illustrated above. However, this is merely an example of logic that is capable of executing a process to act upon a bid request and claimed subject matter is not limited in this respect. According to an embodiment, an intermediary may receive a message comprising a bid request (e.g., in the form of a DTF) at block 302. As described above, a bid request may be transmitted from a source node and/or proxy server according to a communication protocol using an in-band message transmitted in links for transmitting digital objects. As such, an intermediary may receive a bid request at an ingress communication port of a router that is capable of receiving data packets carrying digital objects from a source node. Alternatively, an intermediary may receive a bid request at a communication port that is coupled to a link of a different network that is dedicated for transmitting and/or receiving messages comprising bid requests, bids and/or other management messages. However, these are merely examples of how a bid request may be received at an intermediary and claimed subject matter is not limited in this respect.
Block 304 may determine terms for a bid for a service of forwarding a digital object to a destination node. As illustrated above, such a bid may specify terms and/or conditions under which an intermediary may agree to for the business of forwarding a digital object to a destination node. Block 304 may determine these terms and/or conditions based, at least in part, on capital equipment costs (e.g., for routers and related support equipment), operating costs (including, for example, asset maintenance, rent, power, personnel), current and/or predicted capacity, current and/or predicted asset utilization, prior experience and/or history, pre-existing contracts with other parties, vendor preference, anticipated bid behavior from competing intermediaries for the transmission of the digital object to the destination, anticipated demand and/or ability to provide a particular QoS for the transmission of the digital object. However, these are merely examples of information that an intermediary may utilize in determining terms for a bid for the transmission of a digital object to a destination node and claimed subject matter is not limited in this respect.
Following determining terms of a bid at block 304, an intermediary may transmit the bid to a source node and/or proxy server at block 306. Such a bid may be transmitted to a source node and/or proxy server through a communication port which is capable of receiving digital objects from the source node and/or transmitting digital objects to destinations in the data transmission network. Alternatively, such a bid may be transmitted in an out-of-band message in a different data link. However, these are merely examples of links that may be used for transmitting a message comprising a bid and claimed subject matter is not limited in these respects. In another embodiment, the message comprising a bid may be transmitted according to any one of several protocols such as, for example, UDP/IP and/or a proprietary protocol. However, this is merely an example of a communication protocol that may be used for the transmission of a bid to a source node and/or proxy server and claimed subject matter is not limited in this respect.
It should be understood that, according to a particular embodiment, an intermediary receiving a bid request at block 302 may choose not to respond to the bid request for any one of several reasons such as, for example, an inability to forward the digital object to a specified destination node and/or insufficient capacity to satisfy requested QoS service, a policy to not do business with this particular solicitor or class of solicitors and/or the like. Alternatively, an intermediary may transmit a message to a source node and/or proxy server indicating that the intermediary will not bid for the business of forwarding the digital object at issue. In another embodiment, an intermediary may also transmit a reason for not participating in the bidding process.
Following transmission of a bid at block 306, process 300 may wait for a response from a source node and/or proxy server indicating that the transmitted bid has either been accepted or rejected. Such an acceptance message from a source node and/or proxy server may take the form of a message transmitted in-band along with digital objects or as an out-of-band message in a separate network. In one embodiment, for example, diamond 308 may determine acceptance of a bid upon receipt of one or more data packets at an ingress communication port carrying at least a portion of the digital object and addressed to the destination node, providing an implied acceptance message. In an alternative embodiment, diamond 308 may determine a rejection of the bid if no such data packets carrying at least a portion of the digital object are received at an ingress communication port within a predetermined period following transmission of the bid at block 306. In another alternative embodiment, the diamond 308 may determine whether the bid is accepted or rejected based on an explicit acceptance message or rejection message received from an in-band and/or out-of-band data link. However, these are merely examples of how an intermediary may determine acceptance and/or rejection of a bid for a service of forwarding a digital object and claimed subject matter is not limited in these respects.
In response to an indication that a bid has been accepted, diamond 308 may enable forwarding a digital object to a destination node at block 310. According to an embodiment in which an intermediary comprises one or more routers capable of acting as LSRs in an MPLS network, for example, block 310 may enable one or more routers in an LSP to forward data packets to one or more destination nodes. Data packets identified as carrying the digital object based upon associated switch labels may be forwarded through the LSP toward the one or more destination nodes. According to an embodiment, the intermediary may receive data packets carrying a digital object at an ingress communication port of an initial router. Data packets carrying a digital object along an LSP (or possibly multiple LSPs for more than one destination node) may traverse one or more routers until being transmitted from an egress port of a final router toward the destination node. In an alternative embodiment, an Interior Gateway Protocol (IGP) may be used for routing traffic. However, these are merely examples of how an intermediary may enable forwarding of a digital object to a destination and claimed subject matter is not limited in these respects.
In response to an indication that a bid has been rejected, diamond 308 may inhibit forwarding a digital object to the destination node at block 312 if the bid is rejected. In one particular embodiment, for example, block 312 may inhibit forwarding data packets received at an ingress port of a router by, for example, dropping packets being received at an ingress port of a router without informing a sender. However, this is merely an example of how an intermediary may inhibit the forwarding of a digital object to a destination node and claimed subject matter is not limited in these respects.
As pointed out above, a bid request and/or related bid may relate to forwarding a digital object to multiple destination nodes. Here, in a particular embodiment, a source node and/or proxy server may accept a portion of a bid for forwarding a digital object to one destination node and reject a portion of the bid for forwarding the digital object to one or more other destination nodes. Accordingly, in this particular embodiment, diamond 308 may enable forwarding of a digital object to some destination nodes (relating to an accepted portion of a bid) and inhibit forwarding of the digital object to other destination nodes (relating to a rejected portion of the bid). However, this is merely an example of how an intermediary may process a partial acceptance of a bid for a service of forwarding a digital object and claimed subject matter is not limited in these respects.
FIG. 6 is a schematic diagram of a data transmission network 400 for transmitting a digital object from a source node to one or more destination nodes through two or more intermediaries. A source node 402, coupled to data transmission network 400 through ISP 410, may desire forwarding a digital object to a destination node coupled to ISP 416. ISP 410 may forward a digital object to intermediaries 412 a, 412 b and/or 412 c without any intervening network hops. However, intermediaries 412 a, 412 b and/or 412 c may not necessarily be capable of forwarding a digital object to a destination node without assistance of one or more downstream intermediaries. Here, no single intermediary 412 a, 412 b and/or 412 c may necessarily be capable of forwarding a digital object to ISP 416 without forwarding the digital object through at least one downstream intermediary 413 a, 413 b, 413 c, 413 d, 413 e, 413 f and/or 413 g. Likewise, no single intermediary 413 a, 413 b, 413 c, 413 d, 413 e, 413 f and/or 413 g may be capable of forwarding a digital object to ISP 416 without routing the digital object through an intermediary 415 a, 415 b and/or 415 c.
In response to a request for a bid for the service of forwarding a digital object from ISP 410 to a destination node 404, 406 and/or 408, according to a particular embodiment, an intermediary 412 a, 412 b and/or 412 c may provide a bid comprising terms which are based, at least in part, upon a cost associated with forwarding the digital object through one of downstream intermediaries 413 a through g. While executing process 300 (FIG. 5), according to a particular embodiment for responding to the request for a bid, at block 304 an intermediary 412 a, 412 b and/or 412 c may transmit a bid request to one or more downstream intermediaries 413 a through g. Upon receiving bids from one or more of downstream intermediaries, intermediary 412 a, 412 b and/or 412 c may determine terms for a bid for the transmission of the digital object received from the ISP 410 based, at least in part, on terms from one or more bids received from one or more downstream intermediaries. Intermediary 412 a, 412 b and/or 412 may then complete process 300 as illustrated above. In determining bids in response to bid requests from intermediaries 412 a, 412 b and/or 412 c, intermediaries 413 a through g may similarly request bids of and/or receive bids from downstream intermediaries 415 a, 415 b and/or 415 c as illustrated above.
FIG. 7 is a flow diagram illustrating a process embodiment 450 to act upon a bid request received at an intermediary according to an embodiment. According to particular embodiment, process embodiment 450 may be executed by one or more of intermediaries 412 in response to a bid request from a source node and/or proxy server. In another embodiment, process embodiment 450 may be executed by one or more of the downstream intermediaries 413 in response to a bid request from an intermediary 412. At block 452, an intermediary may receive a bid request as illustrated above with reference to block 302 of FIG. 5. In the case of receiving a bid request at a downstream intermediary 413, however, it should be understood that such a bid request may originate from an intermediary 412. Block 454 may identify one or more downstream intermediaries capable of transmitting the digital object to the destination node as illustrated above with reference to block 204 of process 200.
Block 456 may formulate and transmit a downstream bid request to downstream intermediaries identified in block 454. The terms set forth in such a bid request may be based, at least in part, upon terms set forth in one or more bid requests received at block 452. In a particular embodiment, for example, a bid request formulated at block 456 may characterize a digital object, specify one or more destination nodes and indicate how the digital object is to be transmitted to the one or more destination nodes as described above with reference to block 206 in FIG. 4. Bid requests formulated at block 456 may then be transmitted to one or more downstream intermediaries as an in-band and/or out-of-band message as illustrated above with reference to block 206 above.
At block 458, an intermediary may receive one or more bids in response to bid requests transmitted at block 456. Such bids received at block 458 may express terms such as those expressed in bids received at block 208 as illustrated above. Here, process embodiment 450 may wait for responses following transmission of the bid requests at block 456 for a predetermined period following a transmission of one or more bid requests. Then, block 460 may determine terms for one or more bids to respond to the bid request received at block 452. Terms set forth in these bids may be based, at least in part, upon terms set forth in one or more bids received at block 456. Here, for example, block 460 may determine a price associated with a bid responsive to the bid request received at block 452 based, at least in part, a cost associated with one or more of the bids received at block 458. However, these are merely examples of how terms of a bid for a service of transmitting a digital object to a destination may be determined and claimed subject matter is not limited in this respect.
The discussion above illustrates a process by which intermediaries may bid for the business of providing a service of forwarding digital objects to destination nodes. In particular embodiments, a data transmission network may transport digital objects in data packets over links connecting a source node and/or ISP with intermediaries, and connecting intermediaries with destination nodes. In additional embodiments, a separate network, apart from a data transmission network used for forwarding digital objects, may facilitate an exchange of management messages such as, for example, bid requests, bids, and their status. This may enable centralized deployment of the activities of bidding and billing for the services of forwarding digital objects over the data transmission network.
FIG. 8 is a schematic diagram of a data transmission network 500 comprising a first network to transmit a digital object from a source node to a destination node, and second network to facilitate bidding among intermediaries. A source node 502 may be coupled to the data transmission network 500 by an ISP 510. Source node 502 may transmit a digital object to one or more destination nodes 518 through ISP 510, intermediaries 512 and/or ISP 516. For the purpose of illustration, nodes are connected by data links of the first network represented with solid lines and nodes are connected by data links of the second network represented by broken lines. According to a particular embodiment, data links represented by solid lines are capable of transmitting a digital object toward a destination over a corresponding portion of the first network. Also, data links represented by broken lines may be capable of transmitting control messages, such as, for example, bid requests, bids and acceptance messages, between a server 522 and other nodes in the data transmission network 500.
According to an embodiment, source node 502 may transmit bid requests to intermediaries 512 for a service of forwarding a digital object to one or more destination nodes 508 as discussed above. The intermediaries 512 may also respond to such bids for this service as discussed above. In this particular embodiment, however, server 522 may communicate with source node 502, ISP 510 and/or intermediate nodes through data links in the second network to, among other things, transmit bid requests to and/or receive bids from intermediaries 512.
According to an embodiment, an agent process embodiment 520 may execute on one or more intermediaries 512 to communicate with server 522. For example, in a particular embodiment, an instance of agent process embodiment 520 may be executed by logic such as machine-readable instructions capable of executing on a computer system operated by one or more intermediaries 512. Also, intermediaries 512 may comprise out-of-band communication ports which are capable of communicating on the second network that are distinct from communication ports used for forwarding digital objects on the first network. In a particular embodiment, agent process 520 may communicate with server 522 through such out-of-band communications ports.
According to an embodiment, links of the second network may comprise any one of several types of transmission media such as, for example, any of the aforementioned cabling and/or wireless mediums. Again, however, these are merely examples of transmission media that may used for transmitting messages in the second network and claimed subject matter in not limited in these respects. According to a particular embodiment, messages may be transmitted in links of the second network using any one of the aforementioned data link layer protocols, and may be formatted for transmission on the second network according to any one of the aforementioned network protocols. Again, however, these are merely examples of data link and/or network protocols and claimed subject matter is not limited in these respects.
According to an embodiment, a process of bidding for the service of forwarding a digital object from source node 502 to one or more destination nodes 518 may be governed, at least in part, by server 522 and/or agent process embodiment 520. FIG. 9 is a flow diagram illustrating a process 600 to initiate transmission of a digital object to one or more destination nodes according to an embodiment of data transmission network 500. In a particular embodiment, for example, process embodiment 600 may be performed by logic at the source node 502 and/or ISP 510. At block 602, a digital object may be formulated as illustrated above with reference to block 202 of FIG. 4. However, rather than forwarding bid requests directly to intermediaries, process 600 may forward a bid request to sever 522 (e.g., over the second network). As illustrated below with reference to FIG. 10, server 522 may then facilitate a bidding process among intermediaries 512 for the service of forwarding the digital object to a destination node and selecting an intermediary for forwarding the digital object. Block 606 may receive information (e.g., over the second network) from server 522 which enables forwarding of the digital object to the selected intermediary. For example, block 606 may receive a network address and/or some other identifier associated with a selected intermediary 512 from which the ISP 510 may transmit data packets carrying a digital object to the selected intermediary 512. Block 608 may then initiate transmission of the digital object to a selected intermediary based, at least in part, upon the forwarding instructions received at block 606.
FIG. 10 is a flow diagram illustrating a process embodiment 700 facilitating bidding for the service of forwarding a digital object to one or more destination nodes according to a particular embodiment of a data transmission network of FIG. 8. Block 702 may receive a bid request from source node 502 and/or ISP 510 from the second network (e.g., transmitted at block 604). Block 704 may then broadcast the bid request to one or more intermediaries 512 over the second network. Upon receipt of bid requests from the second network, an instance of agent 520 executing on an associated intermediary may process the bid request and provide a bid as illustrated above with reference to FIG. 5. In this particular embodiment, however, the instance of agent 520 may receive bid requests from, and transmit bids to server 522 over the second network.
In one embodiment, process embodiment 700 may initially identify intermediaries 512 which may be capable of forwarding a digital object to the destination as illustrated above with reference to block 204 (FIG. 4), and limit transmission of bid requests at block 704 to such capable intermediaries 512. Alternatively, process embodiment 700 may merely rely on responses to the bid requests and/or absences of responses to determine the capabilities of the intermediaries 512 as illustrated above.
Upon receiving bids from instances of agent 520, process embodiment 700 may select one or more intermediaries 512 to forward a digital object to one or more destinations, based, at least in part, upon terms set forth in the received bids as illustrated above with reference to block 208 (FIG. 4). Block 708 may then transmit information to be used in forwarding the digital object (e.g., network address(es) of selected intermediary(ies)) over the second network to source node 502 and/or ISP 510 based, at least in part, on the one or more selected intermediaries.
According to an embodiment, server 522 and/or agent process embodiment 520 may maintain billing information for client source nodes and/or ISPs. For example, server 522 may maintain an account of charges owed to intermediaries for forwarding digital objects which have accrued as a result of the bidding process described above or otherwise. In a particular embodiment, block 710 may update the account of source node 502 and/or ISP 510 according to terms of a bid provided by the intermediary 512 selected to forward the digital object to the destination node. For example, server 522 may associate charges with an account number provided in a field of a DTF as part of a bid request received at block 702. However, this is merely an example of maintaining and/or updating an account for charges accrued for the forwarding of digital objects and claimed subject matter is not limited in these respects.
In another particular embodiment, server 522 may coordinate periodic invoicing of accrued charges to nodes that have used the services of intermediaries in forwarding objects in the data transmission network. Server 522 may also facilitate connection charges and/or payment to intermediaries having performed the services of forwarding the digital objects. In one embodiment, server 522 may maintain credit accounts for parties (e.g., source nodes and/or ISPs) that may employ the services of intermediaries in forwarding digital objects. Here, server 522 may charge payment to intermediaries for services performed for parties against the parties' credit accounts. However, these are merely examples of how server 522 may coordinate period invoicing for services performed by intermediaries and claimed subject matter is not limited in these respects.
As illustrated in FIG. 3 above, a source node may forward a digital object to multiple destination nodes over multiple paths. A first intermediary may be selected for forwarding the digital object to one or more destination nodes over a first path and a second intermediary may be selected for transmitting the digital object to one or more other destination nodes over a second path. It should be apparent that the embodiments of FIG. 8 through 10 may facilitate bidding among intermediaries for the service of forwarding the digital object in multiple paths to multiple destinations. Here, server 522 may provide information for forwarding the digital object at block 708 to two or more intermediaries corresponding to the multiple paths.
FIGS. 6 and 7 above illustrate a method and/or system for the transmission of a digital object to a destination node by forwarding the digital object over two or more intermediaries. Here, according to a particular embodiment, the second network may couple server 522 to a source node and/or ISP as well as intermediaries capable of receiving a digital object from the ISP. In response to bid requests from server 522, instances of agent 520 (executing on the intermediaries coupled to the second network) may obtain bids from one or more downstream intermediaries (not shown). Instances of agent 520 may then determine terms for bids for the service of forwarding the digital object to the destination node as illustrated above in process embodiment 450 and transmit the bids to server 522 over the second network. Upon acceptance of one or more of the bids, server 522 may transmit one or more acceptance messages to one or more instances of agent 520 over the second network. Alternatively, as illustrated above, an acceptance may be implied upon receipt of one or more data packets at an intermediary carrying all or a portion of the digital object. Upon an indication of such an acceptance (explicit and/or implied), an instance of agent 520 may accept one or more of said bids received from one or more downstream intermediaries as illustrated above.
While there has been illustrated and described what are presently considered to be example embodiments, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from claimed subject matter. Additionally, many modifications may be made to adapt a particular situation to the teachings of claimed subject matter without departing from the central concept described herein. Therefore, it is intended that claimed subject matter not be limited to the particular embodiments disclosed, but that claimed subject matter may also include all embodiments falling within the scope of claimed subject matter, and equivalents thereof.
US4041398 Jun 3, 1976 Aug 9, 1977 Icc, Inc. Bi-directional digital communication network
US4339807 Feb 25, 1980 Jul 13, 1982 Tokyo Electric Co., Ltd. Postal charge processing system including a weight measuring unit, postal charge calculating unit and a meter stamp issuing unit
US4668758 Sep 30, 1985 May 26, 1987 Shell Oil Company Cure rate control in epoxy resin compositions
US4829443 Feb 2, 1987 May 9, 1989 Pitney Bowes Inc. Insertion machine with computerized postage search and prioritized selection of inserts
US4868758 Feb 2, 1987 Sep 19, 1989 Canon Kabushiki Kaisha Data communication system
US4885777 Apr 11, 1988 Dec 5, 1989 Hitachi, Ltd. Electronic transaction system
US4975830 Dec 5, 1988 Dec 4, 1990 Dayna Communications, Inc. Computer communication system having supplemental formats
US4995082 Feb 23, 1990 Feb 19, 1991 Schnorr Claus P Method for identifying subscribers and for generating and verifying electronic signatures in a data exchange system
US5101437 Feb 11, 1991 Mar 31, 1992 Ecole Polytechnique Method and apparatus for comparing a test handwritten signature with a reference signature by using information relative to curvilinear and angular velocities of the signature
US5111512 May 14, 1991 May 5, 1992 At&T Bell Laboratories Method for signature verification
US5195133 Jan 11, 1991 Mar 16, 1993 Ncr Corporation Apparatus and method for producing a digitized transaction record including an encrypted signature
US5202930 Apr 9, 1991 Apr 13, 1993 Alexander Livshitz High precision on-line signature dynamic verification system
US5203263 Feb 19, 1991 Apr 20, 1993 Ascom Autelca Ag Device for triggering a postage meter machine
US5222138 Aug 6, 1992 Jun 22, 1993 Balabon Sam D Remote signature rendering system & apparatus
US5386369 Jul 12, 1993 Jan 31, 1995 Globetrotter Software Inc. License metering system for software applications
US5465299 Nov 29, 1993 Nov 7, 1995 Hitachi, Ltd. Electronic document processing system and method of forming digital signature
US5557320 Jan 31, 1995 Sep 17, 1996 Krebs; Mark Video mail delivery system
US5719942 Mar 21, 1995 Feb 17, 1998 International Business Machines Corp. System and method for establishing a communication channel over a heterogeneous network between a source node and a destination node
US5790642 Oct 24, 1995 Aug 4, 1998 Dialogic Corporation Competitively bidding service centers
US5838920 Jul 18, 1997 Nov 17, 1998 Advanced System Technologies, Inc. Method and apparatus for identifying transactions
US5909595 Aug 18, 1997 Jun 1, 1999 Nvidia Corporation Method of controlling I/O routing by setting connecting context for utilizing I/O processing elements within a computer system to produce multimedia effects
US5995503 Jun 12, 1996 Nov 30, 1999 Bay Networks, Inc. Method and apparatus for providing quality of service routing in a network
US6047313 Aug 6, 1997 Apr 4, 2000 Fuji Xerox Co., Ltd. Data routing apparatus, server and data terminal equipment
US6073176 Apr 30, 1997 Jun 6, 2000 Cisco Technology, Inc. Dynamic bidding protocol for conducting multilink sessions through different physical termination points
US6073716 Mar 30, 1998 Jun 13, 2000 Textron Inc. Hydraulic system for vehicular traction drive
US6081591 Apr 16, 1997 Jun 27, 2000 Skoog; Frederick H. Signaling network gateway device and method for use in a signaling network
US6141325 Dec 18, 1996 Oct 31, 2000 International Business Machines Corporation Paradigm for enabling interoperability between different subnetworks
US6163807 Nov 3, 1998 Dec 19, 2000 British Telecommunications Public Limited Company Packet network
US6199054 Mar 5, 1998 Mar 6, 2001 Skylight Software, Inc. Automated software metering of digital payloads
US6289371 Sep 30, 1998 Sep 11, 2001 Hewlett-Packard Company Network scan server support method using a web browser
US6314093 Jun 2, 1998 Nov 6, 2001 Nortel Networks Limited Traffic route finder in communications network
US6366575 Nov 1, 1996 Apr 2, 2002 Teloquent Communications Corporation Extended access for automatic call distributing system
US6400687 Jun 12, 1997 Jun 4, 2002 British Telecommunications Public Limited Company ATM network management
US6426948 Jun 2, 1999 Jul 30, 2002 Accenture Llp Video conferencing fault management in a hybrid network
US6487172 Dec 29, 1998 Nov 26, 2002 Nortel Networks Limited Packet network route selection method and apparatus using a bidding algorithm
US6522735 Oct 10, 2000 Feb 18, 2003 Nortel Networks Limited Network selection support in a communications service bidding exchange
US6538991 Aug 3, 1999 Mar 25, 2003 Lucent Technologies Inc. Constraint-based routing between ingress-egress points in a packet network
US6580721 Aug 11, 1998 Jun 17, 2003 Nortel Networks Limited Routing and rate control in a universal transfer mode network
US6631132 Oct 4, 1999 Oct 7, 2003 Veraz Networks Ltd. Urgent packet transmission
US6683874 Oct 29, 1999 Jan 27, 2004 Kabushiki Kaisha Toshiba Router device and label switched path control method using upstream initiated aggregation
US6687230 Jul 2, 1999 Feb 3, 2004 Fujitsu Limited Routing system and method
US6901445 Jul 1, 2002 May 31, 2005 Fastforward Networks, Inc. Proximity-based redirection system for robust and scalable service-node location in an internetwork
US6947390 Sep 5, 2001 Sep 20, 2005 Telefonaktiebolaget Lm Ericsson (Publ) Method for the selection of transmission entities
US6954435 Apr 29, 2002 Oct 11, 2005 Harris Corporation Determining quality of service (QoS) routing for mobile ad hoc networks
US6970939 May 15, 2001 Nov 29, 2005 Intel Corporation Method and apparatus for large payload distribution in a network
US6975594 Jun 27, 2000 Dec 13, 2005 Lucent Technologies Inc. System and method for providing controlled broadband access bandwidth
US6981032 Jul 27, 2001 Dec 27, 2005 International Business Machines Corporation Enhanced multicast-based web server
US6985960 Dec 26, 2000 Jan 10, 2006 Fujitsu Limited Routing information mapping device in a network, method thereof and storage medium
US7068600 Apr 29, 2002 Jun 27, 2006 Harris Corporation Traffic policing in a mobile ad hoc network
US7079538 Mar 9, 2001 Jul 18, 2006 Infineon Technologies Ag High-speed router
US7164665 Jan 15, 2002 Jan 16, 2007 Nokia Corporation Transfer of IP data in telecommunications system
US7177832 Mar 23, 1999 Feb 13, 2007 The Trustees Of Columbia University In The City Of New York System and method for performing a progressive second price auction technique
US7206850 * Jan 31, 2001 Apr 17, 2007 Passology Co., Ltd. Communication system, relay device, service providing device, relaying method, service providing method and program product
US7212975 Feb 16, 2001 May 1, 2007 International Business Machines Corporation Apparatus and methods for providing an estimated time of arrival based marketplace
US7260598 May 3, 2002 Aug 21, 2007 Cisco Technology, Inc. Methods and apparatus for processing client requests in a content distribution network using client lists
US7269185 May 22, 2001 Sep 11, 2007 Nortel Networks Limited Management and control of multi-layer networks
US7289817 Jun 20, 2003 Oct 30, 2007 Lg Electronics Inc. File downloading apparatus and method for mobile communication system
US7336663 Sep 9, 2003 Feb 26, 2008 Nec Corporation Resource reservation protocol substitute reply router, resource reservation protocol substitute reply system and resource reservation protocol substitute reply method used in the same
US7415268 * Mar 2, 2004 Aug 19, 2008 Nokia Corporation Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties
US7418518 Oct 20, 2006 Aug 26, 2008 Akamai Technologies, Inc. Method for high-performance delivery of web content
US7472274 Jun 12, 2003 Dec 30, 2008 Stmicrolectronics S.A. Authentication of an electronic tag
US7526646 May 15, 2002 Apr 28, 2009 Sony Corporation Authentication system and an authentication method for authenticating mobile information terminals
US7558859 Oct 17, 2005 Jul 7, 2009 Microsoft Corporation Peer-to-peer auction based data distribution
US7616661 Jan 2, 2001 Nov 10, 2009 Samsung Electronics Co., Ltd. Apparatus for transmitting/receiving a bit stream in a network and method therefor
US20010025310 Feb 5, 2001 Sep 27, 2001 Srikanth Krishnamurthy System for pricing-based quality of service (PQoS) control in networks
US20010027449 Jan 22, 2001 Oct 4, 2001 Wright Carl A. Instantaneous internet charging
US20010029479 Feb 22, 2001 Oct 11, 2001 International Business Machines Corporation Purchase price bid research system, product provision system, auction server, product retailing method, product purchasing method, and storage medium and program transmission apparatus therefor
US20010049730 Jan 26, 2001 Dec 6, 2001 Brendes Dan Alan Methods and systems for providing converged network management functionality in a gateway routing node
US20010053693 Aug 20, 2001 Dec 20, 2001 Baaziz Achour System and method for selecting a voice service option
US20010053696 Mar 6, 2001 Dec 20, 2001 Pillai Radhakrishna Pillai Raghavan Communication apparatus
US20020002602 Apr 16, 2001 Jan 3, 2002 Mark Vange System and method for serving a web site from multiple servers
US20020004843 Dec 21, 2000 Jan 10, 2002 Loa Andersson System, device, and method for bypassing network changes in a routed communication network
US20020015386 Mar 22, 2001 Feb 7, 2002 Yasuhiro Kajiwara Communication apparatus with selective route optimization capabilities
US20020059624 Aug 1, 2001 May 16, 2002 Kazuhiro Machida Server based broadcast system, apparatus and method and recording medium and software program relating to this system
US20020059625 Aug 24, 2001 May 16, 2002 Nobukazu Kurauchi Nonlinear broadcast system
US20020069179 Jun 6, 2001 Jun 6, 2002 Slater Calvin N. Processing electronic documents with embedded digital signatures
US20020071389 Nov 21, 2001 Jun 13, 2002 Hyun-Chul Seo Data structure for implementation of traffic engineering function in multiprotocol label switching system and storage medium for storing the same
US20020124111 Sep 13, 2001 Sep 5, 2002 Narad Networks, Inc. System and method for message transmission based on intelligent network element device identifiers
US20020150041 Mar 7, 2002 Oct 17, 2002 Onetier Communications, Inc. Method and system for providing an improved quality of service for data transportation over the internet
US20020180781 May 29, 2002 Dec 5, 2002 Cezeaux Thomas Edward Web-based content on an electronic program guide
US20020188562 Jun 5, 2002 Dec 12, 2002 Yoichiro Igarashi Billing system, and device constituting same
US20020196461 Jun 25, 2001 Dec 26, 2002 Hanna Stephen D. Compressed data transmission over a plurality of transmission paths
US20030005049 Jan 31, 2001 Jan 2, 2003 Hideharu Ogawa Communication system,relay device, service providing device,relaying method, service providing method and program product
US20030005148 Aug 31, 2001 Jan 2, 2003 Misato Mochizuki Assistant server and path connection control method for service provider's network
US20030016679 Mar 30, 2001 Jan 23, 2003 Steve Adams Method and apparatus to perform network routing
US20030018539 Jul 3, 2002 Jan 23, 2003 Koninklijke Kpn N.V. Centrum Voor Wiskunde En Informatica Method and system for automated marketing of attention area content
US20030036970 Jun 19, 2002 Feb 20, 2003 Brustoloni Jose C. Method and apparatus for protecting electronic commerce from distributed denial-of-service attacks
US20030059762 Aug 14, 2002 Mar 27, 2003 Sayuri Fujiwara Textbook distribution apparatus, textbook distribution system, textbook distributing method, textbook distribution program, recording medium in which the textbook distribution program is recorded, and textbook display system
US20030088529 Nov 1, 2002 May 8, 2003 Netvmg, Inc. Data network controller
US20030093520 Oct 24, 2002 May 15, 2003 Beesley Richard Craig Method of controlling the amount of data transferred between a terminal and a server
US20030105960 Jun 28, 2001 Jun 5, 2003 Sunao Takatori Host computer, mobile communication device, program, and recording medium
US20030140144 Jan 20, 2002 Jul 24, 2003 Sasisekharan Raguram Coherent provisioning of multiple traffic paths in transport networks
US20030147400 Feb 1, 2002 Aug 7, 2003 Fujitsu Network Communications, Inc. Optimizing path selection for multiple service classes in a network
US20030200439 Apr 17, 2003 Oct 23, 2003 Moskowitz Scott A. Methods, systems and devices for packet watermarking and efficient provisioning of bandwidth
US20030202469 Apr 29, 2002 Oct 30, 2003 Harris Corporation Traffic policing in a mobile ad hoc network
US20030210686 Oct 18, 2001 Nov 13, 2003 Troika Networds, Inc. Router and methods using network addresses for virtualization
US20030212827 May 8, 2002 Nov 13, 2003 Abheek Saha Method and system for providing peer-to-peer exchange of terminal information over a meshed network
US20040008689 Jun 20, 2003 Jan 15, 2004 Cedric Westphal QoS signaling for mobile IP
US20040019901 Apr 11, 2003 Jan 29, 2004 The Boeing Company Methodology for display/distribution of multiple content versions based on demographics
US20040032856 Jul 11, 2002 Feb 19, 2004 Sandstrom Mark Henrik Transparent, look-up-free packet forwarding method for optimizing global network throughput based on real-time route status
US20040052259 Jul 31, 2003 Mar 18, 2004 Agilent Technologies, Inc. Measuring network operational parameters as experienced by network operational traffic
US20040064692 Oct 2, 2003 Apr 1, 2004 Corporation For National Research Initiatives, A Virginia Corporation Identifying, managing, accessing, and tracking digital objects and associated rights and payments
US20040105446 Jul 2, 2003 Jun 3, 2004 Juyoung Park Routing apparatus and method for guaranteeing quality of service on internet
US20040111308 Dec 9, 2002 Jun 10, 2004 Brighthaul Ltd. Dynamic resource allocation platform and method for time related resources
US20040114605 Sep 30, 2003 Jun 17, 2004 Jeyhan Karaoguz Quality of service support in a media exchange network
US20040172373 Feb 28, 2003 Sep 2, 2004 Shuwei Chen Method and system of range-based floating pricing for electronic transaction
US20040192324 Jul 17, 2002 Sep 30, 2004 Steven Rudkin Communications network
US20040199472 Sep 30, 2003 Oct 7, 2004 Dobbins Kurt A. Method and apparatus for billing over a network
US20040213224 Jun 25, 2001 Oct 28, 2004 Mark Goudreau Apparatus and method for classifying packets
US20040236957 Jul 24, 2002 Nov 25, 2004 Alain Durand Method for managing purchase of broadcast digital contents and means for downloading same
US20040246372 Aug 7, 2002 Dec 9, 2004 Magdy Megeid Mpeg-4 remote communication device
US20040261116 Jul 3, 2002 Dec 23, 2004 Mckeown Jean Christophe Broadband communications
US20050002354 Aug 25, 2003 Jan 6, 2005 Kelly Thomas J. Systems and methods for providing network communications between work machines
US20050037787 Jun 24, 2004 Feb 17, 2005 Rosett-Wireless Corporation Wireless intelligent portable-server system (WIPSS)
US20050038707 Jun 21, 2004 Feb 17, 2005 Navio Systems, Inc. Methods and apparatus for enabling transactions in networks
US20050038724 Jun 21, 2004 Feb 17, 2005 Navio Systems, Inc. Methods and apparatus for enabling transaction relating to digital assets
US20050044016 Aug 19, 2003 Feb 24, 2005 Convergys Information Management Group, Inc. System and method for securing digital content
US20050135234 Feb 9, 2005 Jun 23, 2005 Saleh Ali N. Method for routing information over a network
US20050135379 Jul 1, 2004 Jun 23, 2005 Callaway Edgar H.Jr. Methods and apparatuses for routing data in a personal area network
US20050152355 Mar 22, 2002 Jul 14, 2005 Bengt Henriques Reducing transmission time for data packets controlled by a link layer protocol comprising a fragmenting/defragmenting capability
US20050152378 Dec 11, 2004 Jul 14, 2005 Bango Joseph J. Method of providing guaranteed delivery through the use of the internet for priority e-mail, files and important electronic documents
US20050187968 Apr 28, 2005 Aug 25, 2005 Dunning Ted E. File splitting, scalable coding, and asynchronous transmission in streamed data transfer
US20050193114 Feb 11, 2005 Sep 1, 2005 Cisco Technology, Inc. Method and apparatus for directing a flow of packets based on request and server attributes
US20050195842 Mar 31, 2005 Sep 8, 2005 Dowling Eric M. Federated multiprotocol communication
US20050197098 Mar 2, 2004 Sep 8, 2005 Nokia Corporation Method and apparatus to provide charging for ad-hoc service provisioning between trusted parties and between untrusted parties
US20050201380 Feb 9, 2005 Sep 15, 2005 Saleh Ali N. Method for routing information over a network
US20050204042 Mar 11, 2004 Sep 15, 2005 Sujata Banerjee Requesting a service from a multicast network
US20050209927 Mar 18, 2004 Sep 22, 2005 Nokia Corporation System and associated terminal, method and computer program product for uploading content
US20050234860 Mar 30, 2005 Oct 20, 2005 Navio Systems, Inc. User agent for facilitating transactions in networks
US20050246193 Mar 29, 2005 Nov 3, 2005 Navio Systems, Inc. Methods and apparatus for enabling transaction relating to digital assets
US20060002406 Jun 30, 2005 Jan 5, 2006 Takeshi Ishihara Network connection apparatus, program, and method
US20060059253 Sep 29, 2005 Mar 16, 2006 Accenture Llp. Architectures for netcentric computing systems
US20060140162 Dec 23, 2004 Jun 29, 2006 Yojak Vasa Alternate-location content delivery apparatus, methods and computer program products
US20060195565 Aug 1, 2003 Aug 31, 2006 Antoine De-Poorter Method and Apparatus for Routing a Service Request
US20070058568 Sep 14, 2005 Mar 15, 2007 Previdi Stefano B Controlled distribution of inter-area routing information
US20070061891 May 3, 2006 Mar 15, 2007 Fujitsu Limited Environment information transmission method, service controlling system, and computer product
US20070127372 Dec 6, 2005 Jun 7, 2007 Shabbir Khan Digital object routing
US20070130046 Dec 6, 2005 Jun 7, 2007 Shabbir Khan Quality of service for transmission of digital content
US20070133553 Dec 6, 2005 Jun 14, 2007 Shabbir Kahn System and/or method for downstream bidding
US20070133570 Dec 6, 2005 Jun 14, 2007 Shabbir Khan System and/or method for bidding
US20070133571 Dec 6, 2005 Jun 14, 2007 Shabbir Kahn Bidding network
US20070133710 Dec 6, 2005 Jun 14, 2007 Shabbir Khan Digital object title and transmission information
US20070136209 Dec 6, 2005 Jun 14, 2007 Shabbir Khan Digital object title authentication
US20070192872 Feb 6, 2007 Aug 16, 2007 Rhoads Geoffrey B Methods and Devices Employing Content Identifiers
US20070291773 Dec 6, 2005 Dec 20, 2007 Shabbir Khan Digital object routing based on a service request
CN1650578A Apr 28, 2003 Aug 3, 2005 哈里公司 Traffic policing in a mobile ad hoc network
EP0915594A2 Oct 6, 1998 May 12, 1999 AT&amp;T Corp. Method for route selection from a central site
EP0982901A1 Aug 17, 1999 Mar 1, 2000 Northern Telecom Limited Route selection method and apparatus in a packet network
EP1187505B1 Sep 6, 2000 Feb 27, 2008 Telefonaktiebolaget LM Ericsson (publ) Method for the selection of transmission entities
EP1513301B1 Sep 3, 2004 Nov 16, 2016 University-Industry Cooperation Group of KyungHee University Method and device for delivering multimedia data using IETF QoS protocols
GB2399257B Title not available
GB2411549B Title not available
WO2004006486A3 Jul 8, 2003 May 27, 2004 Precache Inc Packet routing via payload inspection for alert services, for digital content delivery and for quality of service management and caching with selective multicasting in a publish-subscribe network
1 Brett J. Vickers, et al., "Source-Adaptive Multilayered Multicast Algorithms for Real-Time Video Distribution," IEEE/ACM Transactions on Networking, vol. 8, No. 6, Dec. 2000, XP011038900, pp. 720-733.
2 High Energy, by Tom Kaneshige, published on www.Line56.com on Oct. 17, 2001.
3 International Preliminary Report in Application No. PCT/US2006/061702 dated Jun. 19, 2008, 7 pages.
4 International Preliminary Report on Patentability issued Jul. 29, 2008 for PCT/IB06/004281, 7 pages.
5 International Preliminary Report on Patentability issued Jul. 8, 2008 for PCT/US06/61653, 6 pages.
6 International Preliminary Report on Patentability issued Jun. 11, 2008 for PCT/US06/61650, 7 pages.
7 International Preliminary Report on Patentability issued Jun. 11, 2008 for PCT/US06/61657, 5 pages.
8 International Preliminary Report on Patentability issued Jun. 11, 2008 for PCT/US06/61701, 5 pages.
9 International Preliminary Report on Patentability issued Jun. 11, 2008 for PCT/US06/61702, 7 pages.
10 International Preliminary Report on Patentability issued Oct. 28, 2008 for PCT/US06/61660, 4 pages.
11 International Preliminary Report on Patentability issued Sep. 3, 2008 for PCT/US07/61697, 5 pages.
12 International Search Report and Written Opinion for Application No. PCT/US06/61650 dated Sep. 25, 2007, 9 pages.
13 International Search Report and Written Opinion for Application No. PCT/US06/61697 dated Aug. 28, 2008, 7 pages.
14 International Search Report and Written Opinion for Application No. PCT/US06/61702 dated Oct. 16, 2007, 9 pages.
15 International Search Report and Written Opinion in Application No. PCT/US2006/061702 dated Oct. 16, 2007, 9 pages.
16 International Search Report for Application No. PCT/US06/61659 dated Jul. 7, 2008, 3 pages.
17 Knightson,et al., NGN Architecture: Generic Principles, Functional Architecture, and Implementation; Oct. 8, 2005; pp. 49-56.
18 Multiprotocol Label Switching Architecture Memo, Copyright © The Internet Society (2001).
19 Office Action for U.S. Appl. No. 11/295,769 mailed Jan. 22, 2009, 12 pages.
20 Office Action for U.S. Appl. No. 11/295,769 mailed Oct. 3, 2008, 9 pages.
21 Office Action for U.S. Appl. No. 11/296,011 mailed Dec. 16, 2008, 12 pages.
22 Office Action for U.S. Appl. No. 11/296,011 mailed Jun. 20, 2008, 12 pages.
23 Office Action for U.S. Appl. No. 11/296,819 mailed Dec. 11, 2008, 10 pages.
24 Official Action in Chinese Application No. 200680045997.6 issued Aug. 3, 2010, 7 pages. English Translation Available.
25 Official Action in Japanese Application No. 2008-544643 dated Oct. 21, 2010. English Translation Available.
26 Official Action in Korean Application No. 10-2008-7015497 issued Aug. 24, 2010. English Summary Available.
27 PCT Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration, mailed Oct. 16, 2007, cited in PCT Application No. PCT/US06/61702.
28 Pending Claims and Summary of Office Action in Chinese Application No. 200680045997.6 issued Nov. 28, 2011, 5 pages.
29 Response to Office Action of Jun. 20, 2008 for U.S. Appl. No. 11/296,011 mailed Sep. 22, 2008, 13 pages.
30 Response to Office Action of Oct. 3, 2008 for U.S. Appl. No. 11/295,769 mailed Jan. 5, 2009, 20 pages.
31 RFC 3031, 2001; IETF Networking Group, by E. Rosen et al.
32 Search Report and Written Opinion for Application No. PCT/US06/61659 dated Jul. 7, 2008, 7 pages.
33 Search Report-Written Opinion issued Aug. 28, 2008 for PCT/US07/61697, 7 pages.
34 Search Report—Written Opinion issued Aug. 28, 2008 for PCT/US07/61697, 7 pages.
35 Search Report-Written Opinion issued Oct. 11, 2007 for PCT/US06/61701, 9 pages.
36 Search Report—Written Opinion issued Oct. 11, 2007 for PCT/US06/61701, 9 pages.
37 Search Report-Written Opinion issued Oct. 16, 2007 for PCT/US06/61650, 9 pages.
38 Search Report—Written Opinion issued Oct. 16, 2007 for PCT/US06/61650, 9 pages.
39 Search Report-Written Opinion issued on Aug. 8, 2008 PCT/US06/61660, 7 pages.
40 Search Report—Written Opinion issued on Aug. 8, 2008 PCT/US06/61660, 7 pages.
41 Search Report-Written Opinion issued on Jul. 7, 2008 for PCT/IB06/004281, 9 pages.
42 Search Report—Written Opinion issued on Jul. 7, 2008 for PCT/IB06/004281, 9 pages.
43 Search Report-Written Opinion Issued on Mar. 20, 2008 for PCT/US06/61653, 9 pages.
44 Search Report—Written Opinion Issued on Mar. 20, 2008 for PCT/US06/61653, 9 pages.
45 Search Report-Written Opinion issued on Nov. 15, 2007 for PCT/US06/61657, 7 pages.
46 Search Report—Written Opinion issued on Nov. 15, 2007 for PCT/US06/61657, 7 pages.
47 Supplemental European Search Report and opinion for European Application No. 06846487, mailed Dec. 1, 2009, 7 pages.
48 Supplemental European Search Report and Opinion in European Application No. 06846507.9 dated Sep. 9, 2010.
49 Terms and conditions of the extended download warranty for digital products purchased on the Symantec Store, Jun. 27, 2005.
US9111288 Mar 25, 2011 Aug 18, 2015 Infosys Limited Method and system for providing real time communications services by a service provider in collaboration with a communications service provider
US9235844 Nov 21, 2012 Jan 12, 2016 Infosys Limited Method and system for providing real-time communications services
US9305301 * Nov 21, 2012 Apr 5, 2016 Infosys Limited Method and system for providing real-time communications services
US20130084830 * Nov 21, 2012 Apr 4, 2013 Infosys Technologies Limited Method and system for providing real-time communication services
U.S. Classification 370/469, 370/395.2, 370/231
International Classification H04L12/28, H04J3/16, G01R31/08
Cooperative Classification H04L45/42, H04L12/145, H04L12/14, H04L47/24, H04L45/32, H04L47/10, H04L45/12, H04L45/00
European Classification H04L12/14, H04L47/24, H04L45/42, H04L45/00, H04L45/32, H04L45/12, H04L12/14N2, H04L47/10
Owner name: LIPPERSHY CELESTIAL LLC, NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAHN, SHABBIR;COHEN, ALEXANDER;REEL/FRAME:017940/0511;SIGNING DATES FROM 20060328 TO 20060518
Owner name: LIPPERSHY DELESTIAL LLC, NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAHN, BHABBR;OOHAN, ALEXANDER;REEL/FRAME:018101/0875;SIGNING DATES FROM 20060328 TO 20060518
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAHN, SHABBIR;COHEN, ALEXANDER;SIGNING DATES FROM 20060328 TO 20060518;REEL/FRAME:017940/0511
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KAHN, BHABBR;OOHAN, ALEXANDER;SIGNING DATES FROM 20060328 TO 20060518;REEL/FRAME:018101/0875
Free format text: MERGER;ASSIGNOR:LIPPERSHY CELESTIAL LLC;REEL/FRAME:036639/0009