Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/14—Session management
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/14—Direct-mode setup

Definitions

• the disclosed embodiments relate to peer-to-peer networking for wireless devices.
• portable personal computing devices including wireless computing devices, such as portable wireless telephones, personal digital assistants (PDAs) and paging devices that are each small, lightweight, and can be easily carried by users.
• wireless computing devices such as portable wireless telephones, personal digital assistants (PDAs) and paging devices that are each small, lightweight, and can be easily carried by users.
• the portable wireless telephones for example, further include cellular telephones that communicate voice and data packets over wireless networks.
• many such cellular telephones are being manufactured with relatively large increases in computing capabilities, and as such, are becoming tantamount to small personal computers and hand-held PDAs.
• these smaller and more powerful personal computing devices are typically severely resource constrained.
• the screen size, amount of available memory and file system space, amount of input and output capabilities and processing capability may each be limited by the small size of the device. Because of such severe resource constraints, it is often typically desirable, for example, to maintain a limited size and quantity of software applications and other information residing on such remote personal computing devices, e.g., client devices.
• FIG. 1 depicts a prior approach to such application execution on a wireless device in order to route data files between wireless devices 100, 102 connected to a communication network 104, e.g., a code division multiple access (CDMA) network, a general packet radio service (GPRS) network, a universal mobile telecommunications system (UMTS) network, or other network.
• a communication network 104 e.g., a code division multiple access (CDMA) network, a general packet radio service (GPRS) network, a universal mobile telecommunications system (UMTS) network, or other network.
• CDMA code division multiple access
• GPRS general packet radio service
• UMTS universal mobile telecommunications system
• FIG. 2 depicts operation of FIG. 1 in the form of a message sequence diagram.
• originating wireless device 100 establishes a data call connection with communication network 104 (sequence steps 21, 22, 23) and then transmits the data file to the MMS 108 (sequence step 24), which may include an indication of the destination, i.e., wireless device 102.
• MMS 108 After receipt of the data file from wireless device 100, MMS 108 notifies destination wireless device 102 of the presence of the data file on the MMS byway of a short message service (SMS) message (sequence step 25), for example.
• SMS short message service
• wireless device 102 downloads the data file from MMS 108 (sequence step 29). After completing download of the data file, wireless device 102 transmits an acknowledgement (sequence step 30) to MMS 108. In response, MMS 108 transmits an acknowledgement (sequence step 31) to wireless device 100 thereby indicating transmission of the data file to the specified destination, i.e., wireless device 102.
• transmission of the data file from wireless device 100 to wireless device 102 requires the use of a multimedia server 108 for storage and retransmission of the data file.
• additional hardware in the form of MMS 108 computer system connected with communication network 104 is required for storing the data file prior to transmission to the destination.
• message sequence steps are required for both the upload (transmission from wireless device 100 to MMS 108) and download (transmission from MMS 108 to wireless device 102) of the data file.
• the present embodiments provide server-less peer-to-peer data networking for content transfer between wireless devices.
• a system embodiment for a peer-to-peer data network for wireless devices includes a first wireless device having a first address and content, and a second wireless device.
• the first wireless device is configured to transmit a message including the first address over a first service.
• the second wireless device is configured to receive the message from the first wireless device and establish a communication path over a second service to the first address and sub-address to receive the content from the first wireless device.
• a method embodiment of communicating content between first and second wireless devices includes the steps of transmitting a message from a first wireless device to a second wireless device over a first service, wherein the message includes a first address and establishing, by the second wireless device, a communication path over a second service to the first address and sub-address to receive content from the first wireless device after receiving the message from the first wireless device.
• a further method embodiment of communicating content on a peer-to-peer data network includes transmitting a message including an address to a wireless device over a first service, establishing a communication path over a second service with the wireless device based on a received request at the address, and transmitting content via the established communication path.
• a further method embodiment of communicating content on a peer-to-peer data network includes establishing a communication path over a first address to an address based on a received message from a wireless device including the address, wherein the received message is received over a second service, and receiving content, via the established communication path, from the address and sub-address.
• a wireless-device processor embodiment for a peer-to-peer data network includes a processor configured to transmit a message including an address over a first service, establish a communication path over a second service with a wireless device based on a received request at the address, and transmit content from the memory to the established communication path.
• a further wireless-device processor for a peer-to-peer data network includes a processor configured to establish a communication path over a first address to an address of a wireless device based on a received message including the address received over a second service, and receive content, via the established communication path, from the address and sub-address.
• a memory or a computer-readable medium stores instructions which, when executed by a processor, cause the processor to transmit a message including an address over a first service, establish a communication path over a second service with a wireless device based on a received request at the address, and transmit content from the memory to the established communication path.
• a memory or a computer-readable medium stores instructions which, when executed by a processor, cause the processor to receive a message including a first address of a wireless device over a first service, establish a communication path over a second service to the first address and, based on the received message, receive content from the first address and via the established communication path.
• a method of communicating content between a first wireless device and a computer platform includes transmitting a message from a first wireless device over a first service, and establishing, by the first wireless device, a communication path over a second service to a computer platform to transmit content from the first wireless device after a predetermined time period has elapsed.
• the message includes a first address and has an intended destination of a second wireless device.
• a method of communicating content between a computer platform and a first wireless device includes receiving a message from a second wireless device over a first service, and establishing, by the first wireless device, a communication path over a second service to the computer platform to receive content from the computer platform.
• the message includes a first address of a computer platform.
• FIG. 1 is a high level diagram of a prior approach communication network
• FIG. 2 is a message sequence chart of operation of the prior approach of FIG. 1;
• FIG. 3 is a high level diagram of a communication network according to an embodiment
• FIG. 4 is a message sequence chart of operation of the FIG. 3 embodiment
• FIG. 5 is a high level functional flow chart of a portion of the process flow of a wireless device of FIG. 3;
• FIG. 6 is a diagram of a wireless network architecture that supports client devices and servers in accordance with at least one embodiment
• FIG. 7 is a more detailed diagram of a wireless network architecture that supports the client devices and servers in accordance with at least one embodiment
• FIG. 8 is a message sequence chart of operation of a second embodiment.
• FIG. 9 is a message sequence chart of operation of a second embodiment.
• the mechanism according to an embodiment provides a peer-to-peer communication of content between wireless devices using a communication network.
• the present embodiments enable wireless devices to set up peer-to-peer communication paths to exchange content, e.g., voice, text, video, and other multimedia content, without requiring a dedicated network server.
• embodiments enable wireless devices to set up communication paths using different services, e.g., short message service and packet data service.
• FIG. 3 depicts an embodiment for routing content 303, e.g., data files, between two wireless devices 300, 302 connected to a communication network 304, e.g., a CDMA network, a GPRS network, a UMTS network, and other types of communication networks.
• a peer-to-peer (PTP) application 621 i.e., a set of executable instructions, resident on each wireless device 300, 302, is executable to effect an exchange of content 303 between wireless devices 300, 302.
• PTP peer-to-peer
• communication of content 303 between wireless devices 300, 302 occurs without requiring a dedicated network server, e.g., a MMS 108 (FIG. 1).
• wireless device 302 may include content 303 (dash-dot line) for communication to wireless device 300. Further, as described below, communication of a message regarding transfer of content 303 between wireless devices 300, 302 is signaled using a separate service, e.g., in the form of a short message service (SMS) message, from the service used to transfer the content, e.g., in the form of a packet data connection.
• SMS short message service
• FIG. 4 depicts operation of the FIG. 3 embodiment in the form of a message sequence diagram.
• Originating wireless device 300 establishes a data call connection with communication network 304 (sequence steps 41, 42, 43).
• wireless device 300 obtains a network address 305, e.g., an Internet Protocol (IP) address, designating the address of the wireless device on communication network 304.
• IP Internet Protocol
• execution of PTP application 621 by wireless device 300 causes the wireless device to transmit (sequence step 44) a message 60, e.g., an SMS message, to destination wireless device 302 using communication network 304.
• a message 60 e.g., an SMS message
• Message 60 includes an indication of content 303, e.g., by use of a particular message title, subject, type, or other mechanism, to be communicated from wireless device 300 to wireless device 302.
• Message 60 also includes the address 305 of wireless device 300 as well as a predetermined secondary address or sub-address 306, e.g., a port number, at the wireless device address 305.
• sub-address 306 is a set value specified for such content transfers.
• sub- address 306 is a random value determined prior to transmission of message 60.
• message 60 omits an indication of content 303 to be transferred and includes only the address 305 to which wireless device 302 connects, as described below.
• message 60 is transmitted using a short message service such as an SMS message.
• message 60 content is encrypted to prevent eavesdropping of the message content.
• message 60 content is digitally signed to prevent tampering with the message content.
• wireless device 302 after receipt of message 60, establishes a data call connection with communication network 304 (sequence steps 45, 46, 47).
• data call connection with communication network 304 uses a different service from the transmission of message 60, e.g., a packet data service.
• wireless device 302 After establishing the data call connection, establishes a connection, such as a socket connection, with wireless device 300, at address 305 and sub-address 306 specified in message 60, using communication network 304 (sequence step 48).
• the term socket connection includes a communication connection between two uniquely identified endpoints.
• connection setup includes the exchange of encryption information, e.g., public and private key pairs, hi respective embodiments, the exchange of encryption information occurs using the service of message 60, e.g., SMS messages, or content communication, e.g., the established data connection described immediately above.
• encryption information e.g., public and private key pairs
• the exchange of encryption information occurs using the service of message 60, e.g., SMS messages, or content communication, e.g., the established data connection described immediately above.
• PTP application 621 on each wireless device 300, 302 are executed by the wireless device to communicate using the connection, e.g., a packet data service connection.
• wireless device 302 downloads content 303 from wireless device 300 using the established connection over communication network 304.
• the content 303 transferred between wireless devices 300, 302 is encrypted.
• wireless device 302 transmits an acknowledgement (sequence step 50) to the originating wireless device thereby indicating completion of the transfer.
• FIG. 5 depicts a high level functional block diagram of a portion 502 of the process flow of operation of wireless device 300 in accordance with the FIG. 4 embodiment.
• wireless device 300 process flow begins operation in an idle state 504.
• an originating packet data call is placed to network 304 (sequence step 41 of FIG. 4) and the flow transitions to an establish data call connection step 506.
• wireless device 300 performs the sequence of steps 41-43 as described above with respect to FIG. 4.
• wireless device 300 After establishing the data call connection, wireless device 300 transmits the message 60 described above to destination wireless device 302 using network 304, and the process flow transitions to a transfer content step 508. As described above with respect to FIG.
• message 60 is transmitted using a different service from the established data call connection, e.g., using an SMS message as opposed to packet data.
• wireless device 300 performs the sequence of steps 48, 49 as described above with respect to FIG. 4. Specifically, for an incoming request from a destination wireless device 302, wireless device 300 executes a handle request transition 510 to handle accepting and establishing the socket connection (sequence step 48 of FIG. 4) and transfer the content 303 (sequence step 49 of FIG. 4). [0030] After receipt of an acknowledgement from destination wireless device 302, the process flow transitions from step 508 to idle state 504. It will be understood that in different embodiments different sequences of steps and transitions may be used to accomplish the embodiments described above.
• message 60 may be transmitted to multiple destination wireless devices requiring the handling of multiple requests for the specified content 303.
• the transition from step 508 to step 504 may occur after either receipt of a number of requests corresponding to the number of transmitted messages 60 or a predetermined timeout period.
• wireless device 300 transitions from step 508 to idle state 504 without receipt of an acknowledgement from destination wireless device 302, e.g., after a predetermined time period has elapsed, etc.
• the acknowledgement maybe received from wireless device 302 using the same service as message 60, e.g., an SMS message, instead of over the packet data service.
• FIG. 8 depicts operation of a second embodiment in the form of a message sequence diagram. According to the second embodiment, a computer platform 612 (FIG.
• Originating wireless device 300 establishes a data call connection with communication network 304 (sequence steps 80, 81, 82). During establishment of the data call connection, wireless device 300 obtains a network address 305, e.g., an IP address, designating the address of the wireless device on communication network 304.
• a network address 305 e.g., an IP address
• execution of PTP application 621 by wireless device 300 causes the wireless device to transmit (sequence step 83) a message 60, e.g., an SMS message as described above, to network 304 intended for wireless device 302 (not shown); however, wireless device 302 is not connected to network 304 at the time.
• Message 60 is as described above.
• wireless device 300 transfers the content 303 to computer platform 612 (sequence step 85).
• computer platform 612 to which the content 303 is transferred is a user-designated device connected with wireless network 604 or wired network 616 (both described with reference to FIG. 6 below) and reachable by wireless device 300 via network 304. That is, computer platform 612 is a failover option to which originating wireless device 300 may transfer the content 303 destined for destination wireless device 302.
• computer platform 612 may be a user-designated desktop computer or laptop computer connected with the Internet.
• the content 303 transferred to computer platform 612 may be encrypted.
• originating wireless device 300 transmits a message 62, similar to message 60, to network 304 and destined for destination wireless device 302. Message 62 includes the address of computer platform 612 to which the content 303 has been transferred, thereby allowing destination wireless device, upon connection to network 304, to obtain the content 303 from the computer platform.
• FIG. 9 depicts a message sequence diagram of the retrieval by destination wireless device 302 of the content 303 from computer platform 612.
• Network 304 transmits (sequence step 90) message 62 to destination wireless device 302.
• Message 62 includes an indication of content 303, e.g., by use of a particular message title, subject, type, or other mechanism, to be communicated from computer platform 612 to destination wireless device 302.
• Message 62 includes the address of computer platform 612, as well as, a predetermined secondary address at the computer platform.
• destination wireless device 302 After receipt of message 62 by way of short message service, establishes a data call connection with communication network 304 (sequence steps 91, 92, 93).
• wireless device 302 After establishing the data call connection, wireless device 302 establishes a connection with computer platform 612 using communication network 304 (sequence step 94). After a connection is established, destination wireless device 302 executes PTP application 621 to communicate using the connection. As such, destination wireless device 302 downloads content 303 from computer platform 612.
• APIs application programming interfaces
• Some of the personal computing devices utilize application programming interfaces (APIs), sometimes referred to as runtime environments and software platforms, that are installed onto their local computer platform and which are used, for example, to simplify operations of such devices, such as by providing generalized calls for device specific resources. Further, some such APIs are also known to provide software developers the ability to create software applications that are fully executable on such devices.
• APIs are known to be operationally located between the computing device system software and the software applications such that the computing device computing functionality is made available to the software applications without requiring the software developer to have the specific computing device system source code.
• some APIs are known to provide mechanisms for secure communications between such personal devices (i.e., clients) and remote devices (i.e., servers) using secure cryptographic information.
• Examples of such APIs include versions of the Binary Runtime Environment for Wireless® (BREW®) developed by Qualcomm, Inc., of San Diego, California.
• BREW® is sometimes described as a thin veneer existing over a computing device's (typically a wireless cellular phone) operating system, which, among other features, provides interfaces to hardware features particularly found on personal computing devices.
• BREW® is further characterized by, at least, the one advantage of being able to be provided on such personal computing devices at a relatively low cost with respect to demands on such device resources and with respect to the price paid by consumers for devices containing the BREW ® API.
• BREW ® End-to-end software distribution platform
• At least one such currently available end-to-end software distribution platform includes logic distributed over a server-client architecture, where the server performs, for example, billing, security and application distribution functionality, and the client performs, for example, application execution, security and user interface functionality.
• One or more embodiments are used in conjunction with a runtime environment (API) executing on the computing device.
• API runtime environment
• One such runtime environment (API) is Binary Runtime Environment for Wireless® (BREW®) software previously discussed.
• BREW® Binary Runtime Environment for Wireless®
• one or more of the described embodiments can be used with other types of runtime environments (APIs) that, for example, operate to control the execution of applications on wireless client computing devices.
• FIG. 6 illustrates a block diagram of one exemplary embodiment of a wireless system 600.
• System 600 can contain client devices, such as cellular telephone 602, in communication across a wireless network 604 with at least one application download server 606 that selectively transmits software applications and components to wireless devices across a wireless communication portal or other data access to the wireless network 604.
• client devices such as cellular telephone 602
• the wireless (client) device can be a cellular telephone 602, a personal digital assistant 608, a pager 610, which is shown here as a two-way text pager, or even a separate computer platform 612 that has a wireless communication portal.
• wireless device 300 includes a transceiver or communication device for transmitting and receiving data, a processor for executing instructions and controlling operation of the wireless device, and a memory for storing the executable instructions, content 303, address 305, and sub-address 306.
• client device including a wireless communication portal, e.g., a communication device, including without limitation, wireless modems, PCMCIA cards, personal computers, access terminals, telephones, or any combination or sub- combination thereof.
• the application download server 606 is shown here on a network 616 with other computer elements in communication with the wireless network 604. There can be a stand-alone server 622, and each server can provide separate services and processes to the client devices 602, 608, 610, 612 across the wireless network 604.
• System 600 may also include at least one stored application database 618 that holds the software applications, e.g., a peer-to-peer application 621, that are downloadable by the wireless devices 602, 608, 610, 612 (the peer-to-peer application is indicated as being downloadable to the wireless devices by a dashed line).
• a peer-to-peer application 621 that are downloadable by the wireless devices 602, 608, 610, 612
• the peer-to-peer application is indicated as being downloadable to the wireless devices by a dashed line.
• the configuration illustrated in Fig. 6 is merely exemplary. Accordingly, other embodiments can include one of more servers that can each perform all the described functions and contain all necessary hardware and software, or
• System 600 is merely exemplary and can include any system whereby remote client devices, such as wireless client computing devices 602, 608, 610, 612 communicate over-the-air between and among each other and/or between and among components connected via a wireless network 604, including, without limitation, wireless network carriers and/or servers.
• the application download server 606 and the stored application database 618 communicate with a carrier network 700, through a data link, such as the Internet, a secure LAN, WAN, or other network.
• Stored application database 618 includes a peer-to-peer application 621 according to the above- described embodiments for download to each of the wireless client computer devices 602, 608, 610, 612.
• Wireless client computer devices 602, 608, 610, 612 download a copy of peer-to-peer application 621 (dashed line) from stored applications database 618.
• a server 620 can include the application download server 606, distribution server 622 and the stored application database 618. However, these servers can also be independent devices.
• carrier network 700 controls messages (generally being data packets) sent to a messaging service controller (“MSC”) 702.
• MSC messaging service controller
• Carrier network 700 communicates with the MSC 702 through another communications link, such as another network, the Internet, and/or POTS ("plain ordinary telephone system").
• MSC 702 may be connected to multiple base stations (“BTS”) 704, such as by at least one communications link, including both a data network and/or the Internet for data transfer and POTS for voice information.
• BTS 704 ultimately broadcasts messages wirelessly to the wireless communications devices, such as cellular telephones 602, in an over-the-air protocol such as short messaging service (“SMS”), etc.
• SMS short messaging service
• each wireless device such as cellular telephones 602 may include a computer platform 706 that can receive and execute software applications and display data transmitted from computer system 620 or other network servers 622.
• Computer platform 706 may include an application-specific integrated circuit (“ASIC") 708, or other chipset, processor, microprocessor, logic circuit, or other data processing device.
• ASIC 708 may be installed at the time of manufacture of cellular telephone 602.
• ASIC 708 or other processor may execute an application programming interface (“API") layer 710 that interfaces with any resident programs, e.g., PTP application 621, in a memory 712 of the wireless device.
• API 710 is a runtime environment executing on the computing device, or cellular telephone 602 in this case.
• Memory 712 can be comprised of at least one of read-only and random-access memory (RAM and ROM), EPROM, EEPROM, flash cards, and any memory common to computer platforms.
• the computer platform 706 may also include a local database 714 that can hold the software applications, e.g., PTP application 621, files, or data not actively used in memory 712.
• Local database 714 may include at least one of flash memory cells, magnetic media, EPROM, EEPROM, optical media, tape, a soft disk, a hard disk, and any other type of secondary or tertiary memory.
• each cellular telephone 602 may be loaded with applications such as peer-to-peer application 621 and/or data from computer system 620 in accordance with system 600.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Mobile Radio Communication Systems (AREA)
• Telephonic Communication Services (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=36997865

Family Applications (1)

Country Status (5)

Families Citing this family (4)

Family Cites Families (10)

• 2006
  • 2006-05-18 WO PCT/US2006/019638 patent/WO2006127543A1/en active Application Filing
  • 2006-05-18 KR KR20077029785A patent/KR100976918B1/ko active IP Right Grant
  • 2006-05-18 CN CN2006800259147A patent/CN101341723B/zh not_active Expired - Fee Related
  • 2006-05-18 JP JP2008512579A patent/JP2008546259A/ja not_active Withdrawn
  • 2006-05-18 EP EP20060760243 patent/EP1884105A1/de not_active Withdrawn
• 2011
  • 2011-05-18 JP JP2011111697A patent/JP4991952B2/ja not_active Expired - Fee Related

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events