WO2006023836A2 - Procede et dispositif de partage par le reseau sans fil d'un fichier au moyen d'une connexion au niveau application - Google Patents

Procede et dispositif de partage par le reseau sans fil d'un fichier au moyen d'une connexion au niveau application Download PDF

Info

Publication number
WO2006023836A2
WO2006023836A2 PCT/US2005/029749 US2005029749W WO2006023836A2 WO 2006023836 A2 WO2006023836 A2 WO 2006023836A2 US 2005029749 W US2005029749 W US 2005029749W WO 2006023836 A2 WO2006023836 A2 WO 2006023836A2
Authority
WO
WIPO (PCT)
Prior art keywords
file
neighbor node
processor
identifier
received
Prior art date
Application number
PCT/US2005/029749
Other languages
English (en)
Other versions
WO2006023836A3 (fr
Inventor
Howard M. Singer
Laird Popkin
Yariv Sadan
Original Assignee
Time Warner, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/922,243 external-priority patent/US7860923B2/en
Priority claimed from US10/922,226 external-priority patent/US7860922B2/en
Application filed by Time Warner, Inc. filed Critical Time Warner, Inc.
Publication of WO2006023836A2 publication Critical patent/WO2006023836A2/fr
Publication of WO2006023836A3 publication Critical patent/WO2006023836A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • Peer-to-peer networking has altered the basic notions of how computers share data.
  • computers share information in a structured manner where one computer is a server and another computer is a client.
  • This traditional concept is known as the "client-server" model.
  • peer-to-peer networking and client-sever transactions typically both rely on a ubiquitous computer data network, for example a local area network or a wide area network (e.g. the Internet).
  • a computer operating in a peer-to-peer configuration is capable of acting both as a client and as a server, depending upon a particular data transaction.
  • a computer in a peer-to-peer network needs data
  • that computer can operate as a client.
  • the same computer can also provide data as a server when called upon to do so by another computer communicatively associated with the first computer in a peer-to-peer network.
  • Peer-to-peer networking has gained wide popularity as a means for sharing files. Peer-to-peer networking is especially popular in those instances when the shared files are media content files, for example audio content and video content files.
  • One aspect of such file sharing is that users are able to specify what files are desired and then search for the files on other computers that are attached to a peer-to-peer network.
  • the standard mechanisms for discovering files in a peer-to-peer network works fairly well because the computers attached to the peer-to-peer network are typically available when a search for a desired file is performed.
  • peer-to-peer networking breaks down in the realm of wireless devices.
  • mobile devices maintain only a transient connection with other mobile devices. This is especially true when the mobile devices interact with each other in local networking structures such as Blue Tooth and 802.11 wireless networks that do not bridge over to a wide area network. As such, it is only when two wireless devices are in proximity to each other that a local connection between them can be formed. As such, file sharing through peer-to-peer networking is limited by the short duration and limited bandwidth of a connection established between such devices.
  • a method and apparatus for sharing a file comprising recognizing a neighbor node, establishing an application-level connection with the neighbor node, determining a file that is to be shared with the neighbor node and conveying a portion of the determined file with the neighbor node.
  • Fig. 1 is a pictorial representation that depicts one illustrative use case wherein the present method is utilized for ad hoc file sharing;
  • Fig. 2 is a flow diagram that depicts one example method for wirelessly sharing a file
  • FIG. 2 A just low diagram depicts one alternative method for determining the file according to membership in a group
  • Fig. 2B is a flow diagram that depicts one alternative method for determining a file based on the availability of files from a second neighbor node
  • Fig. 3 is a flow diagram that depicts one alternative example method for determining a file to be shared by means of a file request
  • Fig. 4 is a flow diagram that depicts an alternative method for receiving an authentication token in the form of an identity code and authenticating a selected file;
  • Fig. 5 is a flow diagram that depicts an alternative method for receiving an authentication token in the form of a Global Release Identifier and authenticating a selected file;
  • Fig. 6 is a flow diagram that depicts an alternative method for receiving an authentication token in the form of a calculated value and authenticating a selected file
  • Fig. 7 is a flow diagram that depicts an example alternative method for conveying a portion of a determined file to a neighbor node
  • Fig 7A is a flow diagram that depicts an alternative method for conveying a determined file to a first neighbor node, wherein the file is obtained from a second neighbor node;
  • Fig. 8 is a flow diagram that depicts one alternative example method for establishing an incentive
  • Fig. 9 is a flow diagram that depicts one example method for noting a sale
  • FIG. 10 is a flow diagram that depicts yet another method for noting a sale
  • Fig. 11 is a flow diagram that depicts an alternative method for establishing an incentive through an offer — acceptance process
  • Fig. 12 is a block diagram that depicts several example embodiments of a wireless file provider device
  • Fig. 13 is a pictorial representation that depicts several alternative example embodiments of a file cache.
  • Fig. 14 is a data flow diagram that depicts the internal operation of several example embodiments of a wireless file provider device.
  • Fig. 1 is a pictorial representation that depicts one illustrative use case wherein the present method is utilized for ad hoc file sharing.
  • intelligent wireless devices include, but are not necessarily limited to personal digital entertainment units 15, cellular telephones 5 and personal digital assistants 10. Included in each of these example intelligent wireless devices is a wireless interface enabling the intelligent wireless device to participate in an ad hoc network 20. It should be noted that there are many varied techniques for establishing an ad hoc network 20. From the perspective of this disclosure, an ad hoc network 20 comprises a network that is temporarily established between intelligent wireless devices.
  • the ad hoc network is established when one intelligent wireless device perceives a second intelligent wireless device.
  • the two intelligent wireless devices enable the communication of one or more data packets between processes executing in each of the intelligent wireless devices.
  • a purchase manager 25 the function of which is described infra.
  • the physical structure of intelligent wireless device includes a wireless network interface.
  • a wireless network interface includes an 802.11 wireless networking interface.
  • Another form of a wireless network interface includes a Blue-Tooth interface. Doubtless, continued evolution of intelligent wireless networking will yield yet other forms of wireless network interfaces. It should be noted that the present method can be applied in any wireless networking structure and is not dependent upon any particular form of a wireless network interface herein described.
  • Fig. 2 is a flow diagram that depicts one example method for wirelessly sharing a file.
  • a file is shared wirelessly by first recognizing a neighbor node (step 35). Once a neighbor node is recognized, an application-level connection is established to the recognized neighbor node (step 40). A file that is to be shared with the neighbor node is then determined (step 45). So long as a connection with the neighbor node
  • AppPCT_TWX-0426-2n.doc remains viable (step 50), a portion of the determined file is conveyed to the neighbor node (step 55).
  • Fig. 2 A is a flow diagram that depicts one alternative method for determining a file to be shared according to membership in a group.
  • the user identifier is received from a recognized neighbor node (step 37).
  • group affiliation comprises membership in a media club.
  • a user of a recognized neighbor node may be a member of a "book of the month" club.
  • Another type of group membership may comprise membership in a "song of the day" club.
  • a file to be shared with the neighbor node is determined according to the group affiliation (step 52). For example, different files stored in a first provider node may be affiliated with a particular group.
  • Fig. 2B is a flow diagram that depicts one alternative method for determining a file based on the availability of files from a second neighbor node.
  • determining a file to be shared with the first recognized neighbor node is accomplished by recognizing a second neighbor node (step 39). Once a second neighbor node is recognized, a second application-level connection is established with the second neighbor node (step 44). It should be appreciated that a second neighbor node may have stored thereon various files that may be shared with the first recognized neighbor node. Accordingly, a list of one or more files is received from the second neighbor node (step 49).
  • this list of one or more files available on the second neighbor node is received by means of the application-level connection established with said second neighbor node.
  • the list of files available on the second neighbor node is then conveyed to the first neighbor node (step 54).
  • this is accomplished by conveying the list of one or more files to the first neighbor node using the first established application-level connection.
  • the application-level connection
  • AppPCT_TWX-0426-2n.doc 8 established with the first neighbor node is then used to receive a selection of one or more files (step 59).
  • the first recognized neighbor node will select files from the list of one or more files available on the second recognized neighbor node.
  • Fig. 3 is a flow diagram that depicts one alternative example method for determining a file to be shared by means of a file request.
  • determining a file to be shared is accomplished by receiving a request for a file (step 65).
  • a request for a file comprises an explicit request for a particular file.
  • an explicit request can include a request for a specific file (e.g. by the name of a specific title of an audio file).
  • a file is selected according to the received file request (step 70).
  • An authentication token is also received (step 75). Once the authentication token is received, the selected file is authenticated using the authentication token (step 80).
  • the selected file is declared to be the determined file, i.e. the file to be shared with the neighbor node (step 90).
  • the identity code is included in a file name by which a particular file is accessed by a file management system (e.g. an operating system).
  • a file management system e.g. an operating system
  • the identity code is included in a file header which is stored as part of the file itself. It should be appreciated that various forms of storage can be used to store the identity code and the various illustrative use cases presented herein are not intended
  • Fig. 4 is a flow diagram that depicts an alternative method for receiving an authentication token in the form of an identity code and authenticating a selected file.
  • an authentication token is received by receiving an identity code (step 100).
  • an identity code is determined for the selected file (step 105).
  • the selected file is declared as authentic (step 115).
  • an identity code can be received along with a file name for a particular file.
  • an identity code can be received as part of a file name for a particular file. In either case, the present method applies.
  • an identity code for a selected file is determined by extracting an identity code from a file name of a file that is intended to be shared with a neighbor node.
  • an identity code for a selected file is determined by extracting an identity code from the file itself. It should be further appreciated that, according to one illustrative use case, an identity code comprises a unique digital value that has been directly encoded to correspond to a specific and unique media content file. It should be further appreciated that according to this illustrative use case, two files that comprise different versions of the same audio or video track will have different unique identity codes commensurate with the teachings of the present method.
  • Fig. 5 is a flow diagram that depicts an alternative method for receiving an authentication token in the form of a Global Release Identifier and authenticating a selected
  • AppPCT_TWX-0426-2n.doc 10 file In the case where a legitimate content file is shared between neighbor mobile nodes, the legitimate content file may be identified by a Global Release Identifier (a.k.a. "GRid").
  • the Global Release Identifier is a content file identifier promulgated by a recognized authority (e.g. the Recording Industry Association of America or the International Federation of Phonographic Industries). Accordingly, one variation of the present method provides for receiving a Global Release Identifier (step 120). Once the Global Release Identifier is received, a Global Release Identifier is also determined for a selected file (step 125).
  • the selected file is declared to be authentic (step 135).
  • various means may be utilized to receive a global release identifier, for example as a separate identifier or as part of a file name. These are merely examples of the various alternative methods that can be used to receive a Global Release Identifier and these examples are not intended to limit the scope of the claims appended hereto. It should also be appreciated that various means may be utilized to determine a Global Release Identifier for a selected file.
  • a Global Release Identifier is determined by extracting a Global Release Identifier from a file name of a file that is intended to be shared with a neighbor node.
  • a Global Release Identifier is extracted from a file itself. It should further be appreciated that a Global Release Identifier can be overloaded onto many different renditions of the same audio and/or video title. For example, the same Global Release Identifier can be used to identify two different files of an audio track wherein each of the two files is encoded at a different sampling rate. In this event, the Global Release Identifier can not be used to identify a unique file.
  • Fig. 6 is a flow diagram that depicts an alternative method for receiving an authentication token in the form of a calculated value and authenticating a selected file.
  • a content file is not identified by an identity code or a Global Release
  • AppPCT_TWX- 042 6-2n.doo 1 1 Identifier provides for receiving a calculated value (step 140) that identifies a file.
  • a calculated value includes, but is not limited to a hash code and cyclic redundancy code, or "CRC”.
  • CRC cyclic redundancy code
  • a calculated value is also determined for a selected file (step 145).
  • the received calculated value is substantially equivalent to the calculated value determined for a selected file (step 150)
  • the selected file is declared to be authentic (step 155). It should be appreciated that various means may be utilized to receive a calculated value, for example as a separate identifier or as part of a file name.
  • a calculated value is determined by extracting a calculated value from a file name of a file that is intended to be shared with a neighbor node.
  • a calculated value is extracted from a file itself.
  • a selected file is subjected to an algorithm in order to generate a calculated value that can be used for comparison with a calculated value received in association with a file request.
  • Fig. 7 is a flow diagram that depicts an example alternative method for conveying a portion of a determined file to a neighbor node.
  • a portion of a determined file is conveyed to a neighbor node by first receiving from the neighbor node a segment identifier (step 160).
  • a file segment is then extracted from the, determined file according to the segment identifier (step 165).
  • a neighbor node may only need a portion of a determined file. For example, a neighbor node may have previously received a portion of a file which the neighbor node needs to augment with a further portion of the same file.
  • a neighbor node may request a further portion of a file using a segment identifier. It should be further noted that in order to determine a particular file, a selected file must first be authenticated according to the
  • both the neighbor node that has requested a further portion of the file and a provider node can have a high level of confidence that a file from which a first portion of a file is received by the neighbor node and the selected file are identical, even in the case where the first portion of a file is received from an independent node.
  • the extracted file segment is then conveyed to the neighbor node (step 170).
  • Fig 7A is a flow diagram that depicts an alternative method for conveying a determined file to a first neighbor node, wherein the file is obtained from a second neighbor node.
  • a file is shared with a first neighbor node by recognizing a second neighbor node (step 161).
  • a second application-level connection is then established with the second recognized neighbor node (step 162).
  • the second recognized neighbor node is used as a source for file to be shared with the first recognized neighbor node.
  • a list of available files is typically received from the second neighbor node commensurate with the teachings for determining a file to be shared with a first neighbor node heretofore described.
  • a portion of a determined file is then received by way of the second established connection (step 167).
  • a portion of a determined file is then conveyed to a first recognized neighbor node by means of a first established application-level connection (step 168). It should be appreciated that a first established application-level connection is established with the first recognized neighbor node.
  • Fig. 2 further illustrates that one alternative example method for sharing a file further comprises establishing an incentive for sharing the determined file with the neighbor node (step 60).
  • sharing a file in an ad-hoc network environment may require some form of incentive in order to encourage a user in control of a providing node to allow the providing node to actually provide a file.
  • a financial incentive for sharing a file needs to be provided to a copyright owner.
  • a particular file may be a media content file including, but not limited to an audio track, a static image, a moving image (i.e. a video file) and an e-book. It should be noted that
  • Fig. 8 is a flow diagram that depicts one alternative example method for establishing an incentive.
  • establishing an incentive is accomplished by communicating a sales price to a neighbor node (step 175).
  • the neighbor node will dispatch an acceptance of the sales price. Accordingly, the acceptance is received from the neighbor node (step 180).
  • a user identifier is also received from the neighbor node (step 185).
  • the user identifier includes, but is not limited to an account number, a cellular telephone number, a cellular service account number, a credit card number, and a debit card number.
  • Fig. 9 is a flow diagram that depicts one example method for noting a sale.
  • a sale is noted by communicating a sales price to a purchase manager (step 200).
  • the sales price is communicated to the purchase manager at the time of sale.
  • the sales price is communicated to the purchase manager at a time subsequent to the sale of a file.
  • a provider identifier is also communicated to the purchase manager (step 205).
  • the user identifier received from the neighbor node is also communicated to the purchase manager (step 210).
  • the purchase manager can use the user identifier in order to debit the user's account (i.e. the user that received a file from a provider node).
  • the purchase manager can also use the provider identifier to enable a credit to the user of a provider node.
  • Fig. 10 is a flow diagram that depicts yet another method for noting a sale.
  • a sale is noted by communicating the user identifier received from the neighbor node to a purchase manager (step 215).
  • a purchase manager i.e. the file received by a user using the neighbor node.
  • AppPCT_TWX-0420-2n.doc 14 communicated to the purchase manager (step 220).
  • the purchase manager is able to use the user's identifier in order to debit the user's account.
  • the identifier for the determined file can be used by the purchase manager to establish a purchase price for a file shared with the neighbor node.
  • Fig. 11 is a flow diagram that depicts an alternative method for establishing an incentive through an offer — acceptance process.
  • a sales price for a file shared with a neighbor node is communicated to the neighbor node (step 225).
  • the neighbor node can either accept the sales price or respond with a counter offer.
  • an acceptance is received (step 230) according to one variation of the present method and a counter-price is received (step 240) according to a different variation of the present method.
  • a sale of a file to the neighbor node is noted (step 235).
  • one variation of the present method provides for determining if the counter price is greater than or equal to a minimum price established for a particular file (step 245).
  • a sale of a file is noted (step 250).
  • Fig. 12 is a block diagram that depicts several example embodiments of a wireless file provider device.
  • a wireless file provider device 705 comprises a processor 700, a wireless interface 710 and a memory 730.
  • a wireless file provider device 705 further comprises a local user interface.
  • the local user interface comprises a user key 720 and a display 715.
  • the user various example embodiments of a wireless file provider device 705 as heretofore described further includes various functional modules each of which comprises an instruction sequence that can be executed by the processor.
  • An instruction sequence that implements a functional module is stored in the memory 730. The reader is advised that the term "minimally causes the processor" and
  • AppPCT_TWX-0426-2n.doc 15 variants thereof is intended to serve as an open-ended enumeration of functions performed by the processor as it executes a particular functional module (i.e. instruction sequence).
  • a particular functional module causes a processor to perform functions in addition to those defined in the appended claims is to be included in the scope of the claims appended hereto.
  • the functional modules (and their corresponding instruction sequences) described thus far that enable wirelessly sharing a file are, according to one alternative embodiment, imparted onto computer readable medium.
  • Examples of such medium include, but are not limited to, random access memory, read-only memory (ROM), Compact Disk (CD) ROM, Digital Versatile Disk (DVD), floppy disks, hard disk drives and magnetic tape.
  • This computer readable medium which alone or in combination can constitute a stand-alone product, can be used to convert a general-purpose computing device into a device for wirelessly providing files wherein said device is capable of providing a file wirelessly according to the techniques and teachings presented herein. Accordingly, the claims appended hereto are to include such computer readable medium imparted with such instruction sequences that enable execution of the present method and all of the teachings herein described.
  • a peer-to-peer module 735 Stored in the memory 730 of one example embodiment are several functional modules including a peer-to-peer module 735, a file determination module 740 and a conveyance module 755.
  • a portion of the memory 730 is used to store files. This portion of the memory is referred to as a file cache 750.
  • a file determination module 740 comprises an authentication module 742.
  • the file provider device 705 further comprises an incentive module 760.
  • the memory 730 is also used to store a list of remotely available files 752.
  • Fig. 13 is a pictorial representation that depicts several alternative example embodiments of a file cache.
  • a file cache 750 comprises various records each of which includes a file name field 800. According to this
  • the file cache 750 further comprises a file content field 825, which is used to store the contents of a file.
  • a record in the file cache 750 further includes a Global Release Identifier field 805.
  • a record included in the file cache 750 further includes an identity code field 810.
  • a record included in the file cache 750 further includes a calculated value field.
  • a record included in the file cache 750 further includes a hash code field 815.
  • a record stored in the file cache 750 further comprises a CRC field 820.
  • yet another alternative embodiment of the file cache 750 includes a sales price field 830 for a record stored therein.
  • an alternative embodiment of the file cache 750 includes a minimum price field 835.
  • the file cache 750 further includes a user group field 836.
  • the user group field 836 is typically used to affiliate a particular file stored in the file cache 750 with a particular user group.
  • a particular user group can include various memberships in various types of groups as heretofore described.
  • One alternative embodiment of a file provider device 705 supports the conveyance of a file according to a segment identifier. Accordingly, one alternative embodiment of the file cache 750 includes a file content field 825 that is segregated into individual segments (825A, 825B, 825C, etc.).
  • Fig. 14 is a data flow diagram that depicts the internal operation of several example embodiments of a wireless file provider device.
  • the processor 700 executes the peer-to-peer module 735.
  • the peer-to-peer module 735 when executed by the processor 700, minimally causes the processor to recognize a neighbor node by way of the wireless interface 710. Once a neighbor node is recognized, a part of the peer- to-peer module 735 further minimally causes the processor 700 to establish an application- level connection 711 with the recognized neighbor node using wireless interface 710.
  • the processor 700 executes the file determination module 740.
  • the file determination module 740 minimally causes the processor 700 to determine a file to be provided to the recognized neighbor node.
  • the connection 711 established with the neighbor node comprises an application-level connection established by means of the wireless interface 710.
  • a file is retrieved 870 according to a filename (stored in the filename field 800).
  • the content of the file is retrieved 870 from the file cache 750 from a field called content 825.
  • the retrieved content is then directed 875 to the peer-to-peer module 735 as the processor 700 continues to execute the conveyance module 755.
  • the file determination module 740 causes the processor to determine a file by minimally causing the processor 700 to receive a user identifier by means of the first established application-level connection.
  • the user identifier typically, is a user identifier that is affiliated with a user of a first recognize neighbor node.
  • user identifier includes therein a group identifier.
  • the group identifier will identify a particular user as a member of a particular group.
  • this alternative embodiment of a file determination module 740 minimally causes the processor 700 to select one or more files stored in the file cache 750 wherein the group identifier matches the entry in a user group field 836 included in the file cache 750.
  • the file determination module 740 causes the processor to determine which file is to be shared with a first recognized neighbor node by minimally causing the processor 700 to execute the peer-to-peer module 735. By executing the peer-to-peer module 735, the processor 700 is minimally caused to recognize a second neighbor node and then establish a second application-level connection with the second recognize neighbor node using the wireless interface 710. Once a second application- level connection is established with a second neighbor node, the processor, as it continues to
  • AppPCT_TWX-0426-2n.doc 18 execute this alternative embodiment of a file determination module 740, is further minimally caused to receive a list of one or more available files from the second neighbor node.
  • the file determination module 740 further minimally causes the processor to store in a remotely available files list 752 a filename in a filename field 827 and a node identifier in a node identifier field 803.
  • the file determination module 740 causes the processor 700 to build a list of one or more files available on a second recognized neighbor node.
  • the file determination module 740 further minimally causes the processor 700 to convey the list of one or more files available on a second recognized neighbor node to the first recognized neighbor node.
  • the file determination module 740 causes the processor 700 to convey this list to the first recognized neighbor node using the first established application- level connection which has been established with the first recognized neighbor node.
  • the file determination module 740 when executed by the processor 700, causes the processor to determine a file by minimally causing the processor to receive 850 a file request from the neighbor node by means of the application level connection 711. Based on the file request, the processor will select 855 a file from the file cache 750.
  • This alternative embodiment of a file determination module 740 further minimally causes the processor to receive an authentication token from the neighbor node by means of the application level connections 711.
  • This alternative embodiment of the file determination module 700 further minimally causes the processor 700 to authenticate the selected file according to the authentication token and execute the conveyance module 735 when the file is determined to be authentic.
  • the file determination module 740 includes an authentication module 742.
  • the file determination module 740 causes the processor to receive an authentication token in the form of a Global Release Identifier.
  • the authentication module 742 when executed by the processor 700, causes the processor to authenticate the selected file by minimally causing the processor to compare a received Global Release Identifier with a Global Release Identifier for the selected file. Accordingly, this alternative embodiment of the authentication module
  • AppPCT_TWX-042 6 -2n.doc 19 742 causes the processor 700 to retrieve a Global Release Identifier from the file cache 750, e.g. from a field called "Global Release Identifier" 805, and compare it with a Global Release Identifier received from the neighbor node by way of the wireless interface (i.e. by means of the wireless connection 711 established by the processor 700 as it continues to execute the peer-to-peer module 735) .
  • the file determination module 740 also includes an authentication module 742.
  • the file determination module 740 causes the processor to receive an authentication token in the form of an identity code.
  • the authentication module 742 of this alternative embodiment when executed by the processor 700, causes the processor 700 to authenticate the selected file by minimally causing the processor 700 to compare a received identity code with an identity code for the selected file.
  • this alternative embodiment of the authentication module 742 causes the processor to retrieve an identity code from the file cache 750, e.g. from the a field called "identity code" 810, and compare it with an identity code received from the neighbor node by way of the wireless interface (i.e. by means of the wireless connections 711 established by the processor 700 as it continues to execute the peer-to-peer module 735).
  • the file determination module 740 also includes an authentication module 742.
  • the file determination module 740 causes the processor to receive an authentication token in the form of calculated value.
  • the authentication module 742 when executed by the processor 700, causes the processor 700 to authenticate the selected file by minimally causing the processor 700 to compare a received calculated value with a calculated value for the selected file.
  • this alternative embodiment of the authentication module ' 742 causes the processor to retrieve a calculated value from the file cache 750 from a calculated value field.
  • the authentication module 742 causes the processor 700 to retrieve a hash code from a field called a hash code 815.
  • the calculated value received by the processor of this alternative embodiment comprises a hash code for the selected file.
  • the calculated value received by the processor of this alternative embodiment comprises a hash code for the selected file.
  • AppPCT_TWX-042 6 -2n.doc 20 authentication module 742 minimally causes the processor 700 to calculate a hash code for the selected file according to the content stored in the content field 825 included in the file cache 750. Then, the processor 700 is further caused to compare the received hash code with either a retrieved hash code or a calculated hash code.
  • the authentication module 742 causes the processor 700 to retrieve a CRC code from a field called CRC 815.
  • the calculated value received by the processor of this alternative embodiment comprises a CRC code for the selected file.
  • the authentication module 742 minimally causes the processor 700 to calculate a CRC code for the selected file according to the content stored in the content field 825 included in the file cache 750. Then, the processor 700 is further caused to compare the received hash code with either a retrieved CRC code or a calculated CRC code.
  • the wireless file provider device 705 includes a conveyance module 755 that, when executed by the processor, minimally causes the processor to provide a file from the file cache 750 according to a segment identifier. Accordingly, a segment identifier is received 877 from a neighbor node by means of a wireless connection 711 established by the processor as it executes the peer-to-peer module 735.
  • the conveyance module 755 causes the processor to respond to a segment identifier by retrieving a portion of a file content stored in the file cache, wherein the file content field 825 is segregated into a plurality of segments (825A, 825B, 825C, etc) and wherein retrieval is accomplished from a segment of the file content field 825 according to the received segment identifier.
  • the conveyance module 755 causes the processor 700 to convey a determined file to a first recognized neighbor node by minimally causing the processor 700 to execute the peer-to-peer module 735. By executing the peer-to- peer module 735, the processor 700 is caused to recognize a second neighbor node. The peer-to-peer module 735 further minimally causes the processor to establish a second application-level connection with the second recognized neighbor node. Using the second
  • the conveyance module 755 further minimally causes the processor 700 to receive a portion of a determined file by way of the second establish connection. As such, a portion of the determined file is received from the second recognized neighbor node. Once received from the second recognized neighbor node, the conveyance module 735 further minimally causes the processor 700 to direct the received portion of the determined file to the first recognized neighbor node. According to this alternative embodiment, this is accomplished as the processor continues to execute the conveyance module 755, wherein the conveyance module 755 further minimally causes the processor 700 to direct the received portion of the determined file to the first established application-level connection.
  • a file provider device 705 further includes an incentive module 760.
  • the incentive module 760 when executed by the processor 700, minimally causes the processor 700 to establish an incentive when a file is conveyed from the file cache 750 to a neighbor node using the application level connection 711.
  • the incentive module 760 causes the processor 700 to establish an incentive by minimally causing the processor 700 to communicate to a neighbor node by means of the wireless connection 711 a sales price for a file stored in the file cache 750.
  • this is accomplished by the processor 700 by retrieving 885 from the file cache a sales price from a sales price field 830 included in a record for particular file stored in the file cache 750.
  • the incentive module 760 then minimally causes the processor 700 to direct 890 the sales price to the peer-to-peer module 735.
  • the processor as it continues to execute the peer-to-peer module 735, is then minimally caused to convey the sales price to the neighbor node by means of the wireless connection 711.
  • the neighbor node can either accept or reject the sales price.
  • the incentive module further minimally causes the processor 700 to receive from the neighbor node by means of the application level connection 711 an acceptance 893 of the price.
  • the incentive module 760 further minimally causes the processor to receive from the neighbor node a user identifier 893.
  • the processor continues to execute the incentive module 760, it is further minimally caused to store in the memory 730 an acceptance record
  • the acceptance record 897 includes the user identifier that was received from the neighbor node.
  • the acceptance record 897 further includes a sales price.
  • the acceptance record 897 further includes a file identifier, which comprises at least one of a global release identifier, an identity code and a file name.
  • the incentive module 760 causes the processor to establish an incentive by minimally causing the processor 700 to communicate to a neighbor node by means of the application level connection 711 a sales price for a file stored in the file cache 750.
  • the incentive module 760 further minimally causes the processor to receive a counter-price from the neighbor node.
  • the incentive module 760 of this alternative embodiment further minimally causes the processor to retrieve from the file cache a minimum price value from a minimum price field 835 included in the file cache 750.
  • An acceptance 897 is then stored in the memory by the processor 700 when the counter-price received by the processor from the neighbor node is equal to or greater than the minimum sales price retrieved by the processor 700 as it continues to execute the incentive module 760.
  • the incentive module 760 when executed by the processor 700, further minimally causes the processor to convey to a purchase manager by way of the wireless interface 710 the contents of the acceptance record 897.
  • the incentive module 760 also causes the processor 700 to direct to the purchase manager by way of the wireless interface 710 at least one of a global release identifier, a file name and an identity code. According to various alternative embodiments, this includes at least one of the user identifier received from the neighbor node and the sales price.
  • the incentive module 760 also minimally causes the processor 700 to convey to the purchase manager by way of the wireless interface 710 a provider identifier.
  • the provider identifier 880 is received from the memory 730 by the processor 700 as it executes the incentive module 760.
  • the incentive module 760 causes the processor 700 to establish connection with a purchase manager using a short-range wireless interface (e.g. BlueTooth or 802.11).
  • the incentive module 760 causes the processor 700 to establish connection with a purchase manager using a wireless cellular data interface (e.g. the G3 network). This list of examples is not meant to limit the scope of the claims appended hereto.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Selon le mode de réalisation décrit dans cette invention, des connexions Ad hoc au niveau application sont établies entre des dispositifs sans fil. Une sélection autonome de fichiers sur un dispositif de prestataire facilite la migration d'un fichier depuis le fournisseur du fichier vers un récepteur du fichier. Une fois un prestataire de fichier et le récepteur du fichier reliés de manière à pouvoir communiquer au moyen d'une connexion au niveau application, une partie d'un fichier prédéterminé est acheminée depuis le noeud prestataire vers un noeud récepteur pendant que la connexion est maintenue.
PCT/US2005/029749 2004-08-18 2005-08-17 Procede et dispositif de partage par le reseau sans fil d'un fichier au moyen d'une connexion au niveau application WO2006023836A2 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US10/922,243 2004-08-18
US10/922,243 US7860923B2 (en) 2004-08-18 2004-08-18 Method and device for the wireless exchange of media content between mobile devices based on user information
US10/922,226 US7860922B2 (en) 2004-08-18 2004-08-18 Method and device for the wireless exchange of media content between mobile devices based on content preferences
US10/922,226 2004-08-18
US11/002,735 US20060041561A1 (en) 2004-08-18 2004-12-02 Method and apparatus for wirelessly sharing a file using an application-level connection
US11/002,735 2004-12-02

Publications (2)

Publication Number Publication Date
WO2006023836A2 true WO2006023836A2 (fr) 2006-03-02
WO2006023836A3 WO2006023836A3 (fr) 2006-06-01

Family

ID=35968255

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/029749 WO2006023836A2 (fr) 2004-08-18 2005-08-17 Procede et dispositif de partage par le reseau sans fil d'un fichier au moyen d'une connexion au niveau application

Country Status (1)

Country Link
WO (1) WO2006023836A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7860923B2 (en) 2004-08-18 2010-12-28 Time Warner Inc. Method and device for the wireless exchange of media content between mobile devices based on user information
US7860922B2 (en) 2004-08-18 2010-12-28 Time Warner, Inc. Method and device for the wireless exchange of media content between mobile devices based on content preferences
WO2015011564A3 (fr) * 2013-07-23 2015-04-16 Yougetitback Limited Systèmes et procédés de transfert de données de dispositif
US9177157B2 (en) 2010-12-22 2015-11-03 May Patents Ltd. System and method for routing-based internet security

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020080888A1 (en) * 2000-12-22 2002-06-27 Li Shu Message splitting and spatially diversified message routing for increasing transmission assurance and data security over distributed networks
US20030050966A1 (en) * 2001-09-13 2003-03-13 International Business Machines Corporation Method and system for redirecting data requests in peer-to-peer data networks
US20030202494A1 (en) * 2002-04-26 2003-10-30 Drews Paul C. Establishing an ad hoc network
US6678252B1 (en) * 1999-10-28 2004-01-13 Verizon Laboratories Inc. Method and apparatus for dynamic source routing in ad hoc wireless networks
US6744740B2 (en) * 2001-12-21 2004-06-01 Motorola, Inc. Network protocol for wireless devices utilizing location information

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6678252B1 (en) * 1999-10-28 2004-01-13 Verizon Laboratories Inc. Method and apparatus for dynamic source routing in ad hoc wireless networks
US20020080888A1 (en) * 2000-12-22 2002-06-27 Li Shu Message splitting and spatially diversified message routing for increasing transmission assurance and data security over distributed networks
US20030050966A1 (en) * 2001-09-13 2003-03-13 International Business Machines Corporation Method and system for redirecting data requests in peer-to-peer data networks
US6744740B2 (en) * 2001-12-21 2004-06-01 Motorola, Inc. Network protocol for wireless devices utilizing location information
US20030202494A1 (en) * 2002-04-26 2003-10-30 Drews Paul C. Establishing an ad hoc network

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7860923B2 (en) 2004-08-18 2010-12-28 Time Warner Inc. Method and device for the wireless exchange of media content between mobile devices based on user information
US7860922B2 (en) 2004-08-18 2010-12-28 Time Warner, Inc. Method and device for the wireless exchange of media content between mobile devices based on content preferences
US8050623B2 (en) 2004-08-18 2011-11-01 Time Warner, Inc. Method and device for promotion and sale of media files on ad hoc mobile device networks
US9177157B2 (en) 2010-12-22 2015-11-03 May Patents Ltd. System and method for routing-based internet security
US9634995B2 (en) 2010-12-22 2017-04-25 Mat Patents Ltd. System and method for routing-based internet security
US9762547B2 (en) 2010-12-22 2017-09-12 May Patents Ltd. System and method for routing-based internet security
US10652214B2 (en) 2010-12-22 2020-05-12 May Patents Ltd. System and method for routing-based internet security
US11303612B2 (en) 2010-12-22 2022-04-12 May Patents Ltd. System and method for routing-based internet security
US11876785B2 (en) 2010-12-22 2024-01-16 May Patents Ltd. System and method for routing-based internet security
WO2015011564A3 (fr) * 2013-07-23 2015-04-16 Yougetitback Limited Systèmes et procédés de transfert de données de dispositif
US11356429B2 (en) 2013-07-23 2022-06-07 Blancco Technology Group IP Oy Systems and methods for device data transfer

Also Published As

Publication number Publication date
WO2006023836A3 (fr) 2006-06-01

Similar Documents

Publication Publication Date Title
US20060041561A1 (en) Method and apparatus for wirelessly sharing a file using an application-level connection
US10628485B2 (en) Blockchain-based music originality analysis method and apparatus
US7860922B2 (en) Method and device for the wireless exchange of media content between mobile devices based on content preferences
US7739151B2 (en) Reservation of digital media items
US10762311B2 (en) Method for RFID tag authentication
US20100274859A1 (en) Method And System For The Creation, Management And Authentication Of Links Between Entities
US20080248779A1 (en) Media content and mobile devices
US20090075696A1 (en) System and Method for Storage and Sharing of Digital Media
US20110066503A1 (en) System and Method for Transferring Digital Media
WO2006051367A2 (fr) Systeme de courtage apres-vente a contenu numerique, procede, appareil et programme informatique associes
AU2016231576A1 (en) In-library lending activation
US20050060437A1 (en) Electronic receipt management
CN110443047B (zh) 数据交换群组系统及方法
WO2006023836A2 (fr) Procede et dispositif de partage par le reseau sans fil d'un fichier au moyen d'une connexion au niveau application
CN111582935A (zh) 一种基于区块链的积分互识方法及系统
US8200989B2 (en) External memory access device and method of accessing external memory
JP2010152753A (ja) 電子クーポン取引システム、自動販売機、プログラム
US20220393892A1 (en) Composite Cryptographic Systems with Variable Configuration Parameters and Memory Bound Functions
US20110185037A1 (en) Method for providing/accessing data on the internet and a respective client, server, and system
WO2006023734A2 (fr) Procede et appareil de distribution sans fil d'un fichier a l'aide de reseaux sans fil ad hoc
CN112905657B (zh) 一种可保护用户隐私的区块链数据处理方法及其系统
US20230370272A1 (en) Blockchain-based digital asset access method, electronic devices, and non-transitory computer-readable media utilizing the method
KR20240047731A (ko) 공유를 통한 nfc 기반 앨범 정보 제공 방법
CN118038500A (zh) 一种数据处理方法及相关装置
JP2009020917A (ja) 認証装置、認証方法、及びプログラム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase