US20110219129A1 - System and method for connecting network sockets between applications - Google Patents
System and method for connecting network sockets between applications Download PDFInfo
- Publication number
- US20110219129A1 US20110219129A1 US13/041,319 US201113041319A US2011219129A1 US 20110219129 A1 US20110219129 A1 US 20110219129A1 US 201113041319 A US201113041319 A US 201113041319A US 2011219129 A1 US2011219129 A1 US 2011219129A1
- Authority
- US
- United States
- Prior art keywords
- application
- network
- loss
- browser
- browser application
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2567—NAT traversal for reachability, e.g. inquiring the address of a correspondent behind a NAT server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
Definitions
- This invention relates generally to the field of communication over a network, and more particularly, to communication between a browser application executing within a browser and a remote application.
- Network communication is no longer limited to PCs and laptops.
- Mobile phones and smart phones can typically connect not only to mobile telephone networks, but also Wi-fi networks, Bluetooth® networks, USB networks, etc.
- Other devices which historically were not able to connect to computer networks, are entering the market already configured to access the internet. Televisions, DVD players, and even home appliances have network and internet capability.
- Smart phones such as the iPhone® device, Android® phones, or Blackberry® phones can download and run a broad array of different applications, from games and movie players to productivity and work tools.
- Browser applications are attractive to developers because they can be relatively easy to develop and deploy. Browser applications also provide dynamic and customizable content for display within a web browser.
- a browser application developer could create, for example, a video game or media presentation application that can run within a web browser.
- Browser applications such as FLASH® applications, UnityTM applications, JavaScript® applications, and the like, can be downloaded and run by a web browser without the need to install the application directly onto a local computer. Rather, a user can run a browser application simply by directing his or her browser to a URL that provides a browser application. The web browser will then load and execute the browser application directly, downloading it just as if the user were viewing a static web page.
- Web browsers are typically subject to security restrictions.
- Web browsers often employ a security scheme, sometimes called sandbox security, that restricts browser applications from accessing resources on the local machine.
- sandbox security a security scheme that restricts browser applications from accessing resources on the local machine.
- web browsers will often prevent browser applications from accessing files on the local hard drive, operating system resources, etc.
- Web browsers may also prevent browser applications from communicating over a network, such as a local or wide area network connected to the local machine.
- the system and method includes apparatuses and operations for establishing communication over a network comprising.
- a host device may execute a browser application within a web browser.
- the web browser may include a security mechanism that prevents the browser application from discovering an endpoint device over a network.
- the browser application may receive a private network address of the endpoint device in order to establish a first network socket connection and a second network socket connection with an application executing on the endpoint device.
- the host device, the endpoint device, or both may send loss-sensitive network traffic over the first network socket connection and loss-tolerant network traffic over the second network socket connection.
- the first network socket connection may be a TCP connection and the second network socket connection may be a UDP connection.
- the data may be generated using pre-constructed packet headers configured to identify the network traffic as either loss-sensitive or loss-tolerant network traffic prior to the network traffic.
- the systems, methods, and operations described herein may determine which socket to send the network traffic over based upon the pre-constructed packet header used.
- FIG. 1 is a block diagram of an exemplary computer network architecture suitable for operation of the present invention
- FIG. 2 is a block diagram of a computer processing device
- FIG. 3 is a flowchart depicting a method for use in connection with the present invention.
- FIG. 4 is a block diagram illustrating some of the operations of the present invention.
- FIG. 5 is a block diagram illustrating network connections.
- the present invention may provide a system and method for connecting devices over a network. More particularly, the present invention may be used to connect and facilitate communication between a browser application running within a web browser and an application executing on an endpoint device.
- Web browsers often employ security schemes, sometimes referred to as sandbox security, to ensure that browser applications cannot cause harm to a local machine. These security schemes may restrict a browser application from using local machine resources, such as the hard drive of the computer, I/O, or networking capabilities.
- devices on a network can discover other devices on the network by broadcasting their presence on the network, and monitoring broadcasts from other devices.
- a browser application for example a FLASH application
- the security mechanisms of the web browser may prevent the browser application from discovering or communicating with other device connected to the network, even if those other devices are running applications that could otherwise communicate or interact with the browser application.
- the present invention provides a system and architecture 10 for controlling content within a web browser.
- the system may include host device 12 , which may execute browser application 14 within web browser 16 .
- FIG. 1 shows host device 12 as a desktop computer, however host device 12 is not limited to desktop computers.
- host device 12 may be a laptop computer, server computer, game console, mobile device, smart phone, internet television, home appliance, network- and processor-enabled remote control toy, internet enabled billboard, medical display device, iPad®, or any other device capable of running browser application 14 within web browser 16 .
- FIG. 1 also shows endpoint devices 18 , 20 .
- Endpoint device 18 may execute application 22 , which may be an application configured to communicate with browser application 14 .
- Endpoint device may typically be a network-enabled wireless handheld device, such as a PDA or smart phone, and application 22 is typically a mobile application.
- endpoint device may also be any type of device capable of running application 22 and connecting to private network 24 , such as a laptop or desktop computer, a gaming console, a game controller, etc.
- Endpoint device 20 may be another endpoint device within system 10 .
- Endpoint device 20 is depicted here merely to show that other devices may be included within system 10 and connected to private network 24 .
- endpoint device 20 may execute an application such as application 20 , may execute other applications capable of communicating with browser application 14 , or may execute applications capable of communicating with other browser applications, for example.
- Private network 18 can typically be a local are network (LAN), but may also be other types of networks, including but not limited to, a wired LAN, one or more LAN segments, a wireless LAN, a wide area network, a Bluetooth® network, a USB network, etc. Accordingly, connections 26 , 28 may be wired or wireless connections and may employ any appropriate communication technologies and protocols to enable communication between the devices.
- LAN local are network
- connections 26 , 28 may be wired or wireless connections and may employ any appropriate communication technologies and protocols to enable communication between the devices.
- Private network 24 may also comprise multiple networks coupled together, multiple LAN segments, etc.
- this disclosure will describe private network 24 as a wired/wireless Ethernet LAN, typical of internet enabled households and businesses. Wired/wireless routers, such as those provided by Linksys® and other companies, can provide such a network.
- Wired/wireless routers such as those provided by Linksys® and other companies, can provide such a network.
- the inventions herein may operate within various different types of network topologies.
- Public network 30 may be any type of LAN or WAN.
- public network 30 may represent a public network such as the internet.
- Network interface device 32 may provide a bridge between private network 24 and public network 30 , and also may provide a security barrier between private network 24 and the internet, such as a firewall. Typical examples of network interface device 32 are cable modems, DSL modems, T1 connections, and the like. Devices connected to public network 30 (i.e. the internet) typically cannot penetrate the security barrier of network interface device 32 to discover or communicate with devices on private network 32 . However, in an embodiment, network interface device 32 may allow devices on private network 24 to access public network 30 so that they can browse the internet, download applications, and communicate with devices on the internet. Network interface device 32 may be a single network interface device, or may be multiple network interface devices that provide multiple access points between private network 24 and the internet.
- Devices connected to private network 24 may receive a private network address, while devices connected to public network 30 may receive public network addresses.
- a private network address is an address specific to private network 24 .
- Devices that receive a private network address from private network 24 can typically communicate freely with other devices on private network 24 .
- devices on public network 30 typically cannot discover or communicate with devices on private network 24 having private network addresses because of the security mechanisms in network interface device 32 .
- a typical example is a home or business LAN, where devices on the LAN can communicate with each other, and can access the internet, but devices on the internet cannot discover or initiate communications with the devices on the LAN.
- network interface device 32 Since network interface device 32 is connected to public network 30 , network interface device may receive a public network address.
- a public network address is an address that can be accessed by devices on public network 30 and/or private network 24 . Since, in this example, public network 30 represents the internet, the public network address received by network interface device is a public internet address, which can be accessed by other devices on the internet. The opposite may also be true.
- devices on public network 30 can “see” network interface device 32 and its public network address, but they cannot “see” devices on private network 24 .
- Devices on private network 24 can not only “see” the other devices on private network 24 and access them using their private network addresses, they can also “see” devices on public network 30 and access them using their public network addresses.
- FIG. 1 also shows server 34 , which is executing address registration process 36 .
- Server 34 can be any type of computing device or group of devices capable of executing address registration process 36 .
- server 34 is a server computer, an internet server, a group of servers, a cluster of servers, or any configuration of server computers.
- System 10 shows a typical configuration for the inventions described herein. However, system 10 is not the only architecture within which the inventions described herein can operation. One skilled in the art will recognize that various system architectures can support the systems, methods, and apparatuses described herein. Also, although not shown, any of the applications and processes may be run by any computing device within system 10 , or by any computing device capable or running the applications and processes. For example, host device 12 may execute address registration process 36 and/or application 22 ; endpoint devices 18 , 20 may execute web browser 16 , browser application 14 , and or address registration process 36 ; and server 34 may execute web browser 16 , browser application 14 , and/or application 22 .
- browser application 14 since browser application 14 is running within the security scheme of web browser 16 , browser application 14 may not be able to discover or communicate with application 22 , and application 22 may not be able to discover or communicate with browser application 14 .
- FIG. 2 shows a block diagram of a typical processing architecture, which may execute software applications and processes.
- Computer processing device 200 is coupled to display 202 for graphical output.
- Processor 204 is a computer processor capable of executing software. Typical examples are computer processors (such as Intel® or AMD® processors), ASICs, microprocessors, and the like.
- Processor 204 is coupled to memory 206 , which is typically a volatile RAM memory for storing instructions and data while processor 204 executes.
- Processor 204 is also coupled to storage device 208 , which is a non-volatile storage medium, such as a hard drive, FLASH drive, tape drive, DVDROM, or similar device.
- Program 210 is a computer program containing instructions and/or data, and is stored on storage device 208 .
- processor 204 may load some or all of the instructions and/or data of program 210 into memory 206 for execution.
- Program 210 can be any computer program or process including, but not limited to web browser 16 , browser application 14 , address registration process 36 , application 22 , or any other computer application or process.
- Program 210 may include various instructions and subroutines, which, when loaded into memory 206 and executed by processor 204 cause processor 204 to perform various operations, some or all of which may effectuate the methods associated with the present inventions.
- computer processing device 200 typically includes various forms of input and output.
- the I/O may include network adapters, USB adapters, Bluetooth radios, mice, keyboards, touchpads, displays, touch screens, LEDs, vibration devices, speakers, microphones, sensors, or any other input or output device for use with computer processing device 200 .
- FIG. 3 shows a flowchart diagram that depicts a process for controlling content and/or establishing two-way communication within a web browser.
- the process may be implemented as software executing on one or more devices.
- the process may run on host device 12 , endpoint devices 18 , 20 , server 34 , or any combination thereof.
- the process may also be implemented on any other capable device or in any appropriate architecture.
- the content control process may operate to control content within a web browser and/or engage in two-way communication with an application running within a web browser.
- the process may facilitate connectivity and two-way communication between browser application 14 and application 22 , and allow application 22 to control web browser content displayed by browser application 14 .
- browser application 14 is a video game downloaded by a user.
- the video game runs as a browser application (e.g. a FLASH application) within web browser 16 , and is subject to the security restrictions of web browser.
- application 22 running on endpoint device 18 is a game controller application downloaded by the user.
- the controller application acts as a game controller and allows the user to control and/or play the FLASH game.
- the user may wish to connect the game controller application to the video game so he or she can play.
- the controller application and the video game may not be able to discover and communicate with each other.
- server 34 may receive 302 a communication from application 22 , which is running on endpoint device 18 .
- application 22 may send the communication in order to register its addresses with server 34 .
- the communication may include private network address of endpoint device 18 (i.e. the private network address within private network 24 ), and may also include the public address of endpoint device 18 .
- network interface device 32 is the bridge between private network 24 and public network 30 , public network address of endpoint device 18 may match, at least in part, the public network address of network interface device 32 .
- the communication may also contain an application ID.
- Application 22 may have an application ID that it sends to server 34 along with the public and private network addresses.
- Browser application 14 (running within browser 16 on host device 12 ) may also send a communication to server 34 .
- the communication from browser application 14 may serve to register browser application 14 with address registration process 36 .
- the communication may contain the public network address of host device 12 , and may also contain an application ID that uniquely identifies browser application 14 .
- the public network address of host device 12 may match, in whole or in part, the public network address of network interface device 32 , since network interface 32 provides the interface between host device 12 and public network 30 .
- the communication from browser application 14 and/or from application 22 also contains other information, such as the private network address of host device 12 , other information about host device 12 , application data, user data, or any other type of information.
- FIG. 4 shows a an example of the communications between endpoint device 18 , host device 12 , and server 34 .
- communication 402 includes the public and private network addresses of endpoint device 18 , and an application ID of application 22 .
- communication 404 contains the public network address of host device 12 and the application ID of browser application 14 . The opposite may also be true.
- Server 34 may receive communications from other endpoint devices and host devices (not shown).
- server 34 is an internet server that receives communications (include network addresses and application IDs) from devices connected to various private networks throughout cyberspace.
- Server 34 may record and catalog the information it receives from these various devices in, for example, a database or other data store.
- server 34 may determine 304 whether endpoint device 18 and host device 12 are connected to the same local network based upon the public network addresses within the communications.
- the public network address is typically associated with a public-facing device connected to the local network. In FIG. 1 , that device is network interface device 32 . Therefore, in this example, when server 34 receives communication 402 from endpoint device 18 , the public network address may indicate that endpoint device 18 is connected to private network 24 since the communication is being routed through network interface device 32 .
- the public network address in communication 404 from host device 12 may indicate that host device 12 is connected to private network 24 and that communication 404 is being routed through network interface device 32 .
- server 34 can determine which devices are connected to the same private networks.
- the public network addresses may match, in whole or in part, or may otherwise be related. For example, server 34 may determine that two devices are connected to the same private network if the public network addresses of the two devices match. In another example, server 34 may determine that two devices are connected to the same private network if the public network addresses of the two devices have the same subnet address.
- Server 34 may also contain a lookup table or other device that provides information about which public network addresses are associated with various private networks. By utilizing the lookup table or other mechanism, server 34 may determine whether received public network addresses indicate that devices are connected to the same private network.
- System 10 may also facilitate a network connection between browser application 14 and application 22 by providing 308 the private network address of endpoint device 18 to browser application 14 .
- browser application 14 and application 22 may not be able to connect or communicate with each other if the security mechanisms of web browser 16 prevent such communication.
- the security mechanisms of web browser 16 may prevent browser application 14 and from broadcasting its presence on private network 24 .
- the security mechanisms of web browser 16 may prevent browser application 14 from receiving broadcasts from application 22 .
- browser application 14 may be able to communicate directly with application 22 if browser application 14 knows the private network address of endpoint device 18 .
- the system may be able to modify the security policy of web browser 16 to allow communication between browser application 14 and application 22 .
- address registration process 36 and/or server 34 will provide the private network address of endpoint device 18 to browser application 14 only if application 22 and browser application 14 are compatible applications. For example, if address registration process 36 determines 310 that browser application 14 is a game application and application 22 is a controller application for that game, then address registration process 36 may determine that application 22 and browser application 14 are compatible applications and send the private network address of endpoint device 18 to browser application 14 , so that browser application 14 and application 22 can communicate with each other. However, if browser application 14 and application 22 are not compatible, then address registration process may not send the private network address to browser application 14 . For example, if browser application 14 is a video game, but application 22 is an application for drawing pictures, then they are likely not compatible. In this case, there may be no need to send the private network address of endpoint device 18 to browser application 14 in order to initiate communication between browser application 14 and application 22 .
- Address registration process 36 may determine 310 whether applications are compatible in various ways. In one embodiment, address registration process 36 may compare the application IDs received from application 22 and browser application 14 . If the application IDs indicate the applications are compatible, address registration process may provide 308 the private network address of endpoint device 18 to browser application 14 . The application IDs may indicate the applications are compatible if the application IDs match, for example. In other embodiments, the application IDs may indicate compatibility if they are associated in some other way. For example, address registration process 36 may have a lookup table or hash table of application IDs that links compatible application IDs.
- the application IDs may be any unique identifier and may include information such as a code representing the application and/or its version number, the name of the application, etc. The opposite may also be true.
- address registration process 36 may provide 308 the private network address to browser application 14 in various ways.
- browser application 14 may periodically poll address registration process 36 and ask for the address.
- address registration process 36 may send browser application 14 a list of the private network addresses of all endpoint devices that are running compatible applications and connected to private network 24 .
- address registration process 36 may send the private network address of an endpoint device to browser application 14 whenever an endpoint device running a compatible application and connected to private network 24 registers with address registration process 36 .
- address registration process 36 may periodically broadcast lists of private network addresses, which can be retrieved by browser application 14 whenever appropriate. Other schemes of providing 308 the private network addresses to browser application 14 may also be employed.
- the system may modify 312 the security policy of web browser 16 to allow for the communication.
- endpoint device 18 may send 314 a policy file to host device 12 .
- endpoint device 18 may send 314 policy file 406 to host device 12 by serving the policy file through a web server.
- Endpoint device 18 may execute a web server application, which may be incorporated into application 22 , or may be a standalone or off-the-shelf web server application.
- Typical off-the-shelf web server applications include the Apache® web server, Microsoft IIS® web server, etc.
- endpoint device 20 or server 34 may also execute the web server application and send 314 the policy file 406 to host device 12 .
- browser application 14 may access the web server executing on endpoint device 18 and download policy file 406 .
- Policy files are typically known in the art.
- policy file 406 may contain a new security policy for web browser 16 or changes to the security policy of web browser 16 that allow for communication between browser application 12 and application 22 .
- browser application 14 may apply the policy file to the security policy of web browser 16 to allow for such communication.
- the security policy of web browser 16 may be modified 312 through an HTML5 handshake.
- HTML5 handshakes are also typically known in the art.
- application 22 and browser application 14 may perform the HTML5 handshake in order to modify the security profile of web browser 16 and allow communication between browser application 14 and application 22 .
- the methods and systems may facilitate communication between browser application 14 and application 22 .
- web browser 16 may include security mechanisms that prevent browser application 14 from discovering or communicating with endpoint devices 18 , 20 over private network 24 .
- application 22 may send the private network address of endpoint device 18 to one or more network-enabled devices.
- application 22 may send the public and/or private network address of endpoint device 18 , and/or an application ID to server 34 .
- application 22 may send such information to any device, or may broadcast such information to any device, in order to facilitate communications between application 22 and browser application 14 .
- browser application 14 may send the public network address of host device 12 , the private network address of host device 12 , and/or an application ID to server 34 in order to facilitate communication with application 22 .
- browser application 14 may send such information to any device, or may broadcast such information to any device, in order to facilitation communications between application 22 and browser application 14 .
- application 22 and/or browser application 14 may establish socket connections in order to facilitate communications.
- socket refers to any unidirectional or bidirectional inter- or intra-process data or communication flow over a network.
- the socket connections may be initiated by application 22 , browser application 14 , or both.
- the socket connections may be any continuous or intermittent communication connections between application 22 and browser application 14 through private network 24 .
- browser application 14 and application 22 establish one or more socket connections, and are the endpoints of the socket connections.
- various other devices such as endpoint device 20 and/or an application running on endpoint device 20
- more than two devices can communicate over the socket connections.
- Browser application 14 and/or application 22 may first initiate the socket connections, which may each provide communication flow from browser application 14 to application 22 , from application 22 to browser application 14 , or both.
- browser application 14 and/or application 22 may establish a socket connection 502 and second socket connection 504 between browser application 14 and application 22 .
- FIG. 5 shows only two socket connections, one skilled in the art will recognize that the applications may also establish additional socket connections to facilitate communications.
- socket connection 502 may be a TCP connection.
- TCP is a reliable communication protocol.
- the TCP protocol provides features that limit packet and data loss between endpoints, as well as features that ensure packets are received and/or processed in a correct order.
- browser application 14 and application 22 may send loss-sensitive data over socket connection 502 .
- loss-sensitive data may include control data such as button presses, command acknowledgements, control data, setup and initiation data, etc.
- the data sent over socket connection 502 may be any data that the application deems to be loss-sensitive. In other words, any data where the absence of receipt of the data on the receiving end of the socket could cause problems, inconsistencies, or bugs in the application may be deemed loss-sensitive data and sent over socket connection 502 .
- Socket connection 504 may be a UDP connection, for example.
- UDP is an unreliable communication protocol and does not include mechanisms to ensure receipt of data.
- browser application 14 and application 22 may send loss-tolerant data over socket 504 .
- Loss tolerant data may include any type of data where the loss of at least some of the data will not cause problems, inconsistencies, or bugs in the application.
- Typical examples of loss tolerant data include streaming video, streaming audio, etc. These types of data are considered loss tolerant because, if some of the data are not received, the audio or video stream may not be significantly interrupted.
- other types of data such as accelerometer measurements from a smart phone, are considered loss-tolerant data and are sent over socket 504 .
- Packet 600 may be a network packet for transmission over socket 502 or socket 504 .
- Packet 600 may include a body 602 , which may contain a data payload, and a header 604 , which may contain routing and other information concerning the transmission of packet 600 over the network.
- header 604 may include indicator 606 , which may identify whether packet 600 contains loss-sensitive traffic and should be routed over socket 502 , or contains loss-tolerant traffic and should be routed over socket 504 .
- Indicator 606 may be any data type known in the art capable of indicating how packet 600 should be routed.
- Packet 600 may be constructed through the use of pre-constructed packet headers and/or pre-constructed packet templates. For example, if the data payload of packet 600 contains loss-sensitive data, packet 600 may be generated using a pre-constructed packet template designed to ensure packet 600 is routed over socket 502 (the TCP socket) once it enters a network stack for transmission and routing. Similarly, if the data payload of packet 600 contains loss-tolerant data, packet 600 may be generated using a pre-constructed header or template designed to ensure packet 600 is routed over socket 504 (the UDP socket) once it enters a network stack for transmission and routing. Of course, the opposite may also be true.
- the header or template used to generate packet 600 may determine the value of indicator 606 , and whether indicator 606 will indicate whether packet 600 should be routed over socket 502 or socket 504 . Accordingly, once packet 600 enters a network stack for transmission and routing, application 22 and/or browser application 14 may read indicator 606 and/or a data type encoded within header 604 or indicator 606 , and may route packet 600 over socket 502 or socket 504 as appropriate.
- an application developer may decide what types of application data are loss-tolerant and what types are loss-sensitive. In this case, the developer may determine which pre-constructed header to use for different types of data.
- browser application 14 and application 22 or a development environment used to create browser application 14 and/or application 22 , may provide defaults for particular data types. For example, browser application 14 and application 22 may, by default, use a pre-constructed header for loss-tolerant data whenever they send streaming audio or streaming video data over the network to each other.
- pre-constructed header for loss-tolerant data whenever they send streaming audio or streaming video data over the network to each other.
- One skilled in the art will recognize that various defaults may be employed so that particular types of data are routed over the appropriate type of socket connection.
- Routing loss-tolerant data over socket connection 504 and loss-sensitive data over socket connection 502 may result in reduced latency and more efficient network communication between application 22 and browser application 14 .
- loss-tolerant data such as streaming video
- socket 504 the UDP connection
- the protocol stacks of application 22 and browser application 14 may become less clocked.
- reserving socket 502 (the TCP connection) for loss-sensitive, but less voluminous data, such as command and control data may also reduce the possibility of a network stack bottleneck.
- browser application 14 and application 22 may be compatible applications designed to communicate with each other.
- browser application 14 may be a game and application 22 may be a game controller application designed to be compatible with one another.
- browser application 14 and application 22 may be the same application, e.g., they may be the same game running on different platforms and communicating, for example, in a head-to-head match.
- browser application 14 and application 22 may be different applications that can communicate with each other over the network.
- the following example shows one embodiment of the present invention.
- a video game application is used to illustrate the operation of the present invention.
- a fictional Player wants to play a video game within a web browser and use his smart phone as a game controller to control the game.
- Host device 12 is already connected to private network 24 , so Player opens web browser 16 and directs it to a web site that hosts his selected video game.
- the video game in this example is a FLASH browser application.
- web browser 16 downloads the game application, it begins to execute the game within web browser 16 .
- web browser 16 has a security policy that restricts the game from discovering other devices connected to private network 24 , or from broadcasting its presence over private network 24 . Therefore, certain operations may be needed before Player's smart phone can be used as a game controller.
- the game Once the game loads, it sends a message and registers its presence with server 34 .
- the message includes the public network address of host device 12 and the application ID of the game.
- the application ID lets server 34 know which game is running, and the public network address lets server 34 know that host device 12 is connected to private network 24
- Player picks up his smart phone (i.e. endpoint device 18 ) and downloads a game controller application for the game (i.e. application 22 ) from the internet.
- Player's smart phone is also connected to private network 24 and has received its own private network address.
- server 34 contains the public and private network address of the smart phone, and the application ID of the game controller application.
- the application ID lets server 34 know which game controller application is running, and the public network address lets server 34 know that the smart phone is connected to private network 24 .
- server 34 may make a determination, based on the public network addresses and application IDs it received, that the game controller and game applications are compatible and that host device 12 and the smart phone are connected to the same local network. If server 34 makes such a determination, it may provide the private network address of the smart phone to the game application to facilitate communication between the game and the game controller applications.
- the game application and/or the game controller application may then modify the security policy of the web browser in order to allow network communication between the applications.
- the smart phone, or another device may provide a policy file or initiate an HTML5 handshake to modify the security profile of web browser 16 .
- the game application and game controller application may then establish network communication with each other by, for example, opening one or more socket connections. Once the applications connect over the network, Player can use the game controller application running on his smart phone to control and play the game running within the web browser.
- the game controller and the game applications may then send data, including game control data, video data, audio data, button press data, accelerometer data, etc., back and forth between the game controller application and the game application.
- the game application and game controller application may then establish network communication with each other by, for example, opening one or more socket connections.
- the game application and game controller application may establish a TCP socket and a UDP socket, for example.
- the applications may send loss-sensitive data, such as button presses, acknowledgements, etc, over the TCP socket, and loss-tolerant data, such as streaming video, audio bytes, cinematics, accelerometer data, etc, over the UDP socket. In this way, the applications may avoid network or network stack bottlenecks and provide each other with low-latency network communication.
- Browser application 14 may be a browser application executing within web browser 16 , which may be executing on host device 12 .
- Browser application 14 sends a communication with the public network address of host device 12 to server 34 .
- Application 22 may be an application for communicating with and controlling content displayed by browser application 14 , and may be executing on endpoint device 18 . Application 22 may send a communication to server 34 with the public and private network addresses of endpoint device 18 .
- Server 34 may determine that application 22 and browser application 14 are compatible applications executing on devices connected to the same local network. If so, server 34 may send the private network address of endpoint 18 to browser application 14 to facilitate connectivity between the two.
- Browser application 14 and application 22 may then communicate with each other over private network 24 , and may modify the security policy of web browser 16 to allow for two way communication between browser application 14 and application 22 .
- Browser application 14 and application 22 may then establish a loss-sensitive socket connection (e.g. a TCP connection) and a loss-tolerant socket connection (e.g. a UDP connection), and reduce network latency by sending loss-sensitive data over the loss-sensitive socket connection, and loss-tolerant data over the loss-tolerant socket connection.
- a loss-sensitive socket connection e.g. a TCP connection
- a loss-tolerant socket connection e.g. a UDP connection
Abstract
Description
- This application claims priority to and benefit of Provisional Patent Application Ser. No. 61/311,102, filed on Mar. 5, 2010, and to Provisional Patent Application Ser. No. 61/421,977, filed on Dec. 10, 2010. Both applications 61/311,102 and 61/421,977 are incorporated herein by reference in their entirety.
- This invention relates generally to the field of communication over a network, and more particularly, to communication between a browser application executing within a browser and a remote application.
- With the rise of mobile computing, more and more devices are able to connect to computer networks. Network communication is no longer limited to PCs and laptops. Mobile phones and smart phones can typically connect not only to mobile telephone networks, but also Wi-fi networks, Bluetooth® networks, USB networks, etc. Other devices, which historically were not able to connect to computer networks, are entering the market already configured to access the internet. Televisions, DVD players, and even home appliances have network and internet capability.
- Mobile applications have also become increasingly popular. Smart phones, such as the iPhone® device, Android® phones, or Blackberry® phones can download and run a broad array of different applications, from games and movie players to productivity and work tools.
- Browser applications are attractive to developers because they can be relatively easy to develop and deploy. Browser applications also provide dynamic and customizable content for display within a web browser. A browser application developer could create, for example, a video game or media presentation application that can run within a web browser.
- Browser applications, such as FLASH® applications, Unity™ applications, JavaScript® applications, and the like, can be downloaded and run by a web browser without the need to install the application directly onto a local computer. Rather, a user can run a browser application simply by directing his or her browser to a URL that provides a browser application. The web browser will then load and execute the browser application directly, downloading it just as if the user were viewing a static web page.
- However, browser applications are typically subject to security restrictions. Web browsers often employ a security scheme, sometimes called sandbox security, that restricts browser applications from accessing resources on the local machine. For example, web browsers will often prevent browser applications from accessing files on the local hard drive, operating system resources, etc. Web browsers may also prevent browser applications from communicating over a network, such as a local or wide area network connected to the local machine.
- Unfortunately, because of a security mechanism of a web browser, it may be difficult for a mobile device to establish a low latency network connection with a browser application executing within the web browser.
- The system and method includes apparatuses and operations for establishing communication over a network comprising. In embodiments, a host device may execute a browser application within a web browser. The web browser may include a security mechanism that prevents the browser application from discovering an endpoint device over a network.
- The browser application may receive a private network address of the endpoint device in order to establish a first network socket connection and a second network socket connection with an application executing on the endpoint device. The host device, the endpoint device, or both may send loss-sensitive network traffic over the first network socket connection and loss-tolerant network traffic over the second network socket connection.
- In some embodiments the first network socket connection may be a TCP connection and the second network socket connection may be a UDP connection. The data may be generated using pre-constructed packet headers configured to identify the network traffic as either loss-sensitive or loss-tolerant network traffic prior to the network traffic. The systems, methods, and operations described herein may determine which socket to send the network traffic over based upon the pre-constructed packet header used.
-
FIG. 1 is a block diagram of an exemplary computer network architecture suitable for operation of the present invention; -
FIG. 2 is a block diagram of a computer processing device; -
FIG. 3 is a flowchart depicting a method for use in connection with the present invention; and -
FIG. 4 is a block diagram illustrating some of the operations of the present invention; and -
FIG. 5 is a block diagram illustrating network connections. - The present invention may provide a system and method for connecting devices over a network. More particularly, the present invention may be used to connect and facilitate communication between a browser application running within a web browser and an application executing on an endpoint device.
- Web browsers often employ security schemes, sometimes referred to as sandbox security, to ensure that browser applications cannot cause harm to a local machine. These security schemes may restrict a browser application from using local machine resources, such as the hard drive of the computer, I/O, or networking capabilities.
- Typically, devices on a network can discover other devices on the network by broadcasting their presence on the network, and monitoring broadcasts from other devices. However, if a browser application, for example a FLASH application, is running within a web browser on a machine connected to a network, the security mechanisms of the web browser may prevent the browser application from discovering or communicating with other device connected to the network, even if those other devices are running applications that could otherwise communicate or interact with the browser application.
- Referring now to
FIG. 1 , in an embodiment, the present invention provides a system andarchitecture 10 for controlling content within a web browser. The system may includehost device 12, which may executebrowser application 14 withinweb browser 16. -
FIG. 1 showshost device 12 as a desktop computer, howeverhost device 12 is not limited to desktop computers. For example,host device 12 may be a laptop computer, server computer, game console, mobile device, smart phone, internet television, home appliance, network- and processor-enabled remote control toy, internet enabled billboard, medical display device, iPad®, or any other device capable of runningbrowser application 14 withinweb browser 16. -
FIG. 1 also showsendpoint devices Endpoint device 18 may executeapplication 22, which may be an application configured to communicate withbrowser application 14. Endpoint device may typically be a network-enabled wireless handheld device, such as a PDA or smart phone, andapplication 22 is typically a mobile application. However, endpoint device may also be any type of device capable of runningapplication 22 and connecting toprivate network 24, such as a laptop or desktop computer, a gaming console, a game controller, etc. -
Endpoint device 20 may be another endpoint device withinsystem 10.Endpoint device 20 is depicted here merely to show that other devices may be included withinsystem 10 and connected toprivate network 24. Although not shown,endpoint device 20 may execute an application such asapplication 20, may execute other applications capable of communicating withbrowser application 14, or may execute applications capable of communicating with other browser applications, for example. -
Host device 12 andendpoint devices private network 18.Private network 18 can typically be a local are network (LAN), but may also be other types of networks, including but not limited to, a wired LAN, one or more LAN segments, a wireless LAN, a wide area network, a Bluetooth® network, a USB network, etc. Accordingly,connections -
Private network 24 may also comprise multiple networks coupled together, multiple LAN segments, etc. For the sake of simplicity, this disclosure will describeprivate network 24 as a wired/wireless Ethernet LAN, typical of internet enabled households and businesses. Wired/wireless routers, such as those provided by Linksys® and other companies, can provide such a network. However, one skilled in the art will recognize that the inventions herein may operate within various different types of network topologies. -
Private network 24 is shown as separated frompublic network 30 bynetwork interface device 32.Public network 30 may be any type of LAN or WAN. In this example,public network 30 may represent a public network such as the internet. -
Network interface device 32 may provide a bridge betweenprivate network 24 andpublic network 30, and also may provide a security barrier betweenprivate network 24 and the internet, such as a firewall. Typical examples ofnetwork interface device 32 are cable modems, DSL modems, T1 connections, and the like. Devices connected to public network 30 (i.e. the internet) typically cannot penetrate the security barrier ofnetwork interface device 32 to discover or communicate with devices onprivate network 32. However, in an embodiment,network interface device 32 may allow devices onprivate network 24 to accesspublic network 30 so that they can browse the internet, download applications, and communicate with devices on the internet.Network interface device 32 may be a single network interface device, or may be multiple network interface devices that provide multiple access points betweenprivate network 24 and the internet. - Devices connected to
private network 24 may receive a private network address, while devices connected topublic network 30 may receive public network addresses. A private network address is an address specific toprivate network 24. Devices that receive a private network address fromprivate network 24 can typically communicate freely with other devices onprivate network 24. However, devices onpublic network 30 typically cannot discover or communicate with devices onprivate network 24 having private network addresses because of the security mechanisms innetwork interface device 32. A typical example is a home or business LAN, where devices on the LAN can communicate with each other, and can access the internet, but devices on the internet cannot discover or initiate communications with the devices on the LAN. - Since
network interface device 32 is connected topublic network 30, network interface device may receive a public network address. A public network address is an address that can be accessed by devices onpublic network 30 and/orprivate network 24. Since, in this example,public network 30 represents the internet, the public network address received by network interface device is a public internet address, which can be accessed by other devices on the internet. The opposite may also be true. - In other words, devices on public network 30 (i.e. internet devices) can “see”
network interface device 32 and its public network address, but they cannot “see” devices onprivate network 24. Devices onprivate network 24 can not only “see” the other devices onprivate network 24 and access them using their private network addresses, they can also “see” devices onpublic network 30 and access them using their public network addresses. -
FIG. 1 also showsserver 34, which is executingaddress registration process 36.Server 34 can be any type of computing device or group of devices capable of executingaddress registration process 36. Typically,server 34 is a server computer, an internet server, a group of servers, a cluster of servers, or any configuration of server computers. -
System 10 shows a typical configuration for the inventions described herein. However,system 10 is not the only architecture within which the inventions described herein can operation. One skilled in the art will recognize that various system architectures can support the systems, methods, and apparatuses described herein. Also, although not shown, any of the applications and processes may be run by any computing device withinsystem 10, or by any computing device capable or running the applications and processes. For example,host device 12 may executeaddress registration process 36 and/orapplication 22;endpoint devices web browser 16,browser application 14, and or addressregistration process 36; andserver 34 may executeweb browser 16,browser application 14, and/orapplication 22. - As discussed, since
browser application 14 is running within the security scheme ofweb browser 16,browser application 14 may not be able to discover or communicate withapplication 22, andapplication 22 may not be able to discover or communicate withbrowser application 14. - The present inventions may be implemented as hardware, software, or a combination of hardware and software.
FIG. 2 shows a block diagram of a typical processing architecture, which may execute software applications and processes.Computer processing device 200 is coupled to display 202 for graphical output.Processor 204 is a computer processor capable of executing software. Typical examples are computer processors (such as Intel® or AMD® processors), ASICs, microprocessors, and the like.Processor 204 is coupled tomemory 206, which is typically a volatile RAM memory for storing instructions and data whileprocessor 204 executes.Processor 204 is also coupled tostorage device 208, which is a non-volatile storage medium, such as a hard drive, FLASH drive, tape drive, DVDROM, or similar device.Program 210 is a computer program containing instructions and/or data, and is stored onstorage device 208. In a typical scenario,processor 204 may load some or all of the instructions and/or data ofprogram 210 intomemory 206 for execution.Program 210 can be any computer program or process including, but not limited toweb browser 16,browser application 14,address registration process 36,application 22, or any other computer application or process. -
Program 210 may include various instructions and subroutines, which, when loaded intomemory 206 and executed byprocessor 204cause processor 204 to perform various operations, some or all of which may effectuate the methods associated with the present inventions. - Although not shown,
computer processing device 200 typically includes various forms of input and output. The I/O may include network adapters, USB adapters, Bluetooth radios, mice, keyboards, touchpads, displays, touch screens, LEDs, vibration devices, speakers, microphones, sensors, or any other input or output device for use withcomputer processing device 200. -
FIG. 3 shows a flowchart diagram that depicts a process for controlling content and/or establishing two-way communication within a web browser. The process may be implemented as software executing on one or more devices. For example, the process may run onhost device 12,endpoint devices server 34, or any combination thereof. The process may also be implemented on any other capable device or in any appropriate architecture. - In an embodiment, the content control process may operate to control content within a web browser and/or engage in two-way communication with an application running within a web browser. In a specific embodiment, the process may facilitate connectivity and two-way communication between
browser application 14 andapplication 22, and allowapplication 22 to control web browser content displayed bybrowser application 14. In one example,browser application 14 is a video game downloaded by a user. The video game runs as a browser application (e.g. a FLASH application) withinweb browser 16, and is subject to the security restrictions of web browser. In the same example,application 22 running onendpoint device 18 is a game controller application downloaded by the user. The controller application acts as a game controller and allows the user to control and/or play the FLASH game. The user may wish to connect the game controller application to the video game so he or she can play. However, since the video game is executing within the security schema ofweb browser 16, the controller application and the video game may not be able to discover and communicate with each other. - In order for the applications to communicate, server 34 (and/or address registration process 36) may receive 302 a communication from
application 22, which is running onendpoint device 18. In one embodiment,application 22 may send the communication in order to register its addresses withserver 34. Accordingly, the communication may include private network address of endpoint device 18 (i.e. the private network address within private network 24), and may also include the public address ofendpoint device 18. In this example, sincenetwork interface device 32 is the bridge betweenprivate network 24 andpublic network 30, public network address ofendpoint device 18 may match, at least in part, the public network address ofnetwork interface device 32. - In some cases, the communication may also contain an application ID.
Application 22 may have an application ID that it sends toserver 34 along with the public and private network addresses. - Browser application 14 (running within
browser 16 on host device 12) may also send a communication toserver 34. Similarly, the communication frombrowser application 14 may serve to registerbrowser application 14 withaddress registration process 36. The communication may contain the public network address ofhost device 12, and may also contain an application ID that uniquely identifiesbrowser application 14. In this case, as discussed above, the public network address ofhost device 12 may match, in whole or in part, the public network address ofnetwork interface device 32, sincenetwork interface 32 provides the interface betweenhost device 12 andpublic network 30. In some embodiments, the communication frombrowser application 14 and/or fromapplication 22 also contains other information, such as the private network address ofhost device 12, other information abouthost device 12, application data, user data, or any other type of information. -
FIG. 4 shows a an example of the communications betweenendpoint device 18,host device 12, andserver 34. As shown,communication 402 includes the public and private network addresses ofendpoint device 18, and an application ID ofapplication 22. Similarly,communication 404 contains the public network address ofhost device 12 and the application ID ofbrowser application 14. The opposite may also be true. -
Server 34 may receive communications from other endpoint devices and host devices (not shown). In one embodiment,server 34 is an internet server that receives communications (include network addresses and application IDs) from devices connected to various private networks throughout cyberspace.Server 34 may record and catalog the information it receives from these various devices in, for example, a database or other data store. - Upon receipt of the communications,
server 34 may determine 304 whetherendpoint device 18 andhost device 12 are connected to the same local network based upon the public network addresses within the communications. As described above, the public network address is typically associated with a public-facing device connected to the local network. InFIG. 1 , that device isnetwork interface device 32. Therefore, in this example, whenserver 34 receivescommunication 402 fromendpoint device 18, the public network address may indicate thatendpoint device 18 is connected toprivate network 24 since the communication is being routed throughnetwork interface device 32. Similarly, the public network address incommunication 404 fromhost device 12 may indicate thathost device 12 is connected toprivate network 24 and thatcommunication 404 is being routed throughnetwork interface device 32. - By comparing the public network address of various devices in this way,
server 34 can determine which devices are connected to the same private networks. The public network addresses may match, in whole or in part, or may otherwise be related. For example,server 34 may determine that two devices are connected to the same private network if the public network addresses of the two devices match. In another example,server 34 may determine that two devices are connected to the same private network if the public network addresses of the two devices have the same subnet address.Server 34 may also contain a lookup table or other device that provides information about which public network addresses are associated with various private networks. By utilizing the lookup table or other mechanism,server 34 may determine whether received public network addresses indicate that devices are connected to the same private network. -
System 10 may also facilitate a network connection betweenbrowser application 14 andapplication 22 by providing 308 the private network address ofendpoint device 18 tobrowser application 14. As discussed above,browser application 14 andapplication 22 may not be able to connect or communicate with each other if the security mechanisms ofweb browser 16 prevent such communication. For example, the security mechanisms ofweb browser 16 may preventbrowser application 14 and from broadcasting its presence onprivate network 24. Similarly, the security mechanisms ofweb browser 16 may preventbrowser application 14 from receiving broadcasts fromapplication 22. - However,
browser application 14 may be able to communicate directly withapplication 22 ifbrowser application 14 knows the private network address ofendpoint device 18. By providing the private network address ofendpoint device 18 tobrowser application 14, the system may be able to modify the security policy ofweb browser 16 to allow communication betweenbrowser application 14 andapplication 22. - In some embodiments, address
registration process 36 and/orserver 34 will provide the private network address ofendpoint device 18 tobrowser application 14 only ifapplication 22 andbrowser application 14 are compatible applications. For example, ifaddress registration process 36 determines 310 thatbrowser application 14 is a game application andapplication 22 is a controller application for that game, then addressregistration process 36 may determine thatapplication 22 andbrowser application 14 are compatible applications and send the private network address ofendpoint device 18 tobrowser application 14, so thatbrowser application 14 andapplication 22 can communicate with each other. However, ifbrowser application 14 andapplication 22 are not compatible, then address registration process may not send the private network address tobrowser application 14. For example, ifbrowser application 14 is a video game, butapplication 22 is an application for drawing pictures, then they are likely not compatible. In this case, there may be no need to send the private network address ofendpoint device 18 tobrowser application 14 in order to initiate communication betweenbrowser application 14 andapplication 22. -
Address registration process 36 may determine 310 whether applications are compatible in various ways. In one embodiment, addressregistration process 36 may compare the application IDs received fromapplication 22 andbrowser application 14. If the application IDs indicate the applications are compatible, address registration process may provide 308 the private network address ofendpoint device 18 tobrowser application 14. The application IDs may indicate the applications are compatible if the application IDs match, for example. In other embodiments, the application IDs may indicate compatibility if they are associated in some other way. For example, addressregistration process 36 may have a lookup table or hash table of application IDs that links compatible application IDs. - The application IDs may be any unique identifier and may include information such as a code representing the application and/or its version number, the name of the application, etc. The opposite may also be true.
- In some embodiments, address
registration process 36 may provide 308 the private network address tobrowser application 14 in various ways. In one embodiment,browser application 14 may periodically polladdress registration process 36 and ask for the address. Upon receipt of the request, addressregistration process 36 may send browser application 14 a list of the private network addresses of all endpoint devices that are running compatible applications and connected toprivate network 24. In another embodiment, addressregistration process 36 may send the private network address of an endpoint device tobrowser application 14 whenever an endpoint device running a compatible application and connected toprivate network 24 registers withaddress registration process 36. In yet another embodiment, addressregistration process 36 may periodically broadcast lists of private network addresses, which can be retrieved bybrowser application 14 whenever appropriate. Other schemes of providing 308 the private network addresses tobrowser application 14 may also be employed. - If the security of
web browser 16 prevents communication betweenbrowser application 14 andapplication 22, then the system may modify 312 the security policy ofweb browser 16 to allow for the communication. For example,endpoint device 18 may send 314 a policy file tohost device 12. - Referring to
FIGS. 3 and 4 , in one embodiment,endpoint device 18 may send 314policy file 406 tohost device 12 by serving the policy file through a web server.Endpoint device 18 may execute a web server application, which may be incorporated intoapplication 22, or may be a standalone or off-the-shelf web server application. Typical off-the-shelf web server applications include the Apache® web server, Microsoft IIS® web server, etc. One skilled in the art will recognize that other devices, such asendpoint device 20 orserver 34, may also execute the web server application and send 314 thepolicy file 406 tohost device 12. - Upon receipt of the private network address of
endpoint device 18,browser application 14 may access the web server executing onendpoint device 18 anddownload policy file 406. Policy files are typically known in the art. In this example,policy file 406 may contain a new security policy forweb browser 16 or changes to the security policy ofweb browser 16 that allow for communication betweenbrowser application 12 andapplication 22. Whenbrowser application 14 receivespolicy file 406, it may apply the policy file to the security policy ofweb browser 16 to allow for such communication. - In another embodiment, the security policy of
web browser 16 may be modified 312 through an HTML5 handshake. HTML5 handshakes are also typically known in the art. In this case,application 22 andbrowser application 14 may perform the HTML5 handshake in order to modify the security profile ofweb browser 16 and allow communication betweenbrowser application 14 andapplication 22. - In some embodiments, the methods and systems may facilitate communication between
browser application 14 andapplication 22. As discussed,web browser 16 may include security mechanisms that preventbrowser application 14 from discovering or communicating withendpoint devices private network 24. To facilitate communications,application 22 may send the private network address ofendpoint device 18 to one or more network-enabled devices. - In the example above,
application 22 may send the public and/or private network address ofendpoint device 18, and/or an application ID toserver 34. However, one skilled in the art will recognize thatapplication 22 may send such information to any device, or may broadcast such information to any device, in order to facilitate communications betweenapplication 22 andbrowser application 14. Similarly,browser application 14 may send the public network address ofhost device 12, the private network address ofhost device 12, and/or an application ID toserver 34 in order to facilitate communication withapplication 22. However, on skilled in the art will recognize thatbrowser application 14 may send such information to any device, or may broadcast such information to any device, in order to facilitation communications betweenapplication 22 andbrowser application 14. - In an embodiment,
application 22 and/orbrowser application 14 may establish socket connections in order to facilitate communications. As used herein, the term socket refers to any unidirectional or bidirectional inter- or intra-process data or communication flow over a network. The socket connections may be initiated byapplication 22,browser application 14, or both. The socket connections may be any continuous or intermittent communication connections betweenapplication 22 andbrowser application 14 throughprivate network 24. - In various embodiments,
browser application 14 andapplication 22 establish one or more socket connections, and are the endpoints of the socket connections. However, various other devices (such asendpoint device 20 and/or an application running on endpoint device 20) may establish the socket connections and may also be endpoints in the socket connections. In some embodiments where multiple devices are involved in communication, more than two devices can communicate over the socket connections. -
Browser application 14 and/orapplication 22 may first initiate the socket connections, which may each provide communication flow frombrowser application 14 toapplication 22, fromapplication 22 tobrowser application 14, or both. - Referring to
FIG. 5 , upon receipt of the private network address ofendpoint device 18 and upon initiation of communications,browser application 14 and/orapplication 22 may establish asocket connection 502 andsecond socket connection 504 betweenbrowser application 14 andapplication 22. AlthoughFIG. 5 shows only two socket connections, one skilled in the art will recognize that the applications may also establish additional socket connections to facilitate communications. - In one embodiment,
socket connection 502 may be a TCP connection. As known in the art, TCP is a reliable communication protocol. The TCP protocol provides features that limit packet and data loss between endpoints, as well as features that ensure packets are received and/or processed in a correct order. Accordingly,browser application 14 andapplication 22 may send loss-sensitive data oversocket connection 502. As an example, ifbrowser application 14 is a game andapplication 22 is a game controller application, loss-sensitive data may include control data such as button presses, command acknowledgements, control data, setup and initiation data, etc. In general, the data sent oversocket connection 502 may be any data that the application deems to be loss-sensitive. In other words, any data where the absence of receipt of the data on the receiving end of the socket could cause problems, inconsistencies, or bugs in the application may be deemed loss-sensitive data and sent oversocket connection 502. -
Socket connection 504 may be a UDP connection, for example. As known in the art, UDP is an unreliable communication protocol and does not include mechanisms to ensure receipt of data. Accordingly,browser application 14 andapplication 22 may send loss-tolerant data oversocket 504. Loss tolerant data may include any type of data where the loss of at least some of the data will not cause problems, inconsistencies, or bugs in the application. Typical examples of loss tolerant data include streaming video, streaming audio, etc. These types of data are considered loss tolerant because, if some of the data are not received, the audio or video stream may not be significantly interrupted. In some embodiments, other types of data, such as accelerometer measurements from a smart phone, are considered loss-tolerant data and are sent oversocket 504. -
Application 14 and/orbrowser application 22 may generate network packets for transmission oversockets FIG. 6 ,packet 600 may be a network packet for transmission oversocket 502 orsocket 504.Packet 600 may include abody 602, which may contain a data payload, and aheader 604, which may contain routing and other information concerning the transmission ofpacket 600 over the network. In some embodiments,header 604 may includeindicator 606, which may identify whetherpacket 600 contains loss-sensitive traffic and should be routed oversocket 502, or contains loss-tolerant traffic and should be routed oversocket 504.Indicator 606 may be any data type known in the art capable of indicating howpacket 600 should be routed. -
Packet 600 may be constructed through the use of pre-constructed packet headers and/or pre-constructed packet templates. For example, if the data payload ofpacket 600 contains loss-sensitive data,packet 600 may be generated using a pre-constructed packet template designed to ensurepacket 600 is routed over socket 502 (the TCP socket) once it enters a network stack for transmission and routing. Similarly, if the data payload ofpacket 600 contains loss-tolerant data,packet 600 may be generated using a pre-constructed header or template designed to ensurepacket 600 is routed over socket 504 (the UDP socket) once it enters a network stack for transmission and routing. Of course, the opposite may also be true. - In some embodiments, the header or template used to generate
packet 600 may determine the value ofindicator 606, and whetherindicator 606 will indicate whetherpacket 600 should be routed oversocket 502 orsocket 504. Accordingly, oncepacket 600 enters a network stack for transmission and routing,application 22 and/orbrowser application 14 may readindicator 606 and/or a data type encoded withinheader 604 orindicator 606, and may routepacket 600 oversocket 502 orsocket 504 as appropriate. - During development, an application developer may decide what types of application data are loss-tolerant and what types are loss-sensitive. In this case, the developer may determine which pre-constructed header to use for different types of data. Additionally/alternatively,
browser application 14 andapplication 22, or a development environment used to createbrowser application 14 and/orapplication 22, may provide defaults for particular data types. For example,browser application 14 andapplication 22 may, by default, use a pre-constructed header for loss-tolerant data whenever they send streaming audio or streaming video data over the network to each other. One skilled in the art will recognize that various defaults may be employed so that particular types of data are routed over the appropriate type of socket connection. - Routing loss-tolerant data over
socket connection 504 and loss-sensitive data oversocket connection 502 may result in reduced latency and more efficient network communication betweenapplication 22 andbrowser application 14. For example, by sending loss-tolerant data (such as streaming video) over socket 504 (the UDP connection), the protocol stacks ofapplication 22 andbrowser application 14 may become less clocked. Also, reserving socket 502 (the TCP connection) for loss-sensitive, but less voluminous data, such as command and control data, may also reduce the possibility of a network stack bottleneck. - Although the descriptions above provide examples with a single endpoint device, a single host device, and a single server, one skilled in the art will recognize that any combination employing single or multiple devices are possible. Any combination of single or multiple endpoint devices, single or multiple host devices, and/or single or multiple address registration server devices may fall within the scope of the invention. For example, multiple endpoint devices may connect to a single host device, a single endpoint device may connect to a single host device, single or multiple host and/or endpoint devices may communicate with single or multiple address registration server devices, etc. Other combinations are also within the scope of the invention.
- Furthermore,
browser application 14 andapplication 22 may be compatible applications designed to communicate with each other. For example,browser application 14 may be a game andapplication 22 may be a game controller application designed to be compatible with one another. Similarly,browser application 14 andapplication 22 may be the same application, e.g., they may be the same game running on different platforms and communicating, for example, in a head-to-head match. Additionally/alternatively,browser application 14 andapplication 22 may be different applications that can communicate with each other over the network. - The following example shows one embodiment of the present invention. A video game application is used to illustrate the operation of the present invention.
- In this example, a fictional Player wants to play a video game within a web browser and use his smart phone as a game controller to control the game.
Host device 12 is already connected toprivate network 24, so Player opensweb browser 16 and directs it to a web site that hosts his selected video game. The video game in this example is a FLASH browser application. Whenweb browser 16 downloads the game application, it begins to execute the game withinweb browser 16. However,web browser 16 has a security policy that restricts the game from discovering other devices connected toprivate network 24, or from broadcasting its presence overprivate network 24. Therefore, certain operations may be needed before Player's smart phone can be used as a game controller. - Once the game loads, it sends a message and registers its presence with
server 34. The message includes the public network address ofhost device 12 and the application ID of the game. The application ID letsserver 34 know which game is running, and the public network address letsserver 34 know thathost device 12 is connected toprivate network 24 - Next, Player picks up his smart phone (i.e. endpoint device 18) and downloads a game controller application for the game (i.e. application 22) from the internet. Player's smart phone is also connected to
private network 24 and has received its own private network address. When Player loads the game controller application, it sends a communication toserver 34 that contains the public and private network address of the smart phone, and the application ID of the game controller application. The application ID letsserver 34 know which game controller application is running, and the public network address letsserver 34 know that the smart phone is connected toprivate network 24. - After it receives the communications,
server 34 may make a determination, based on the public network addresses and application IDs it received, that the game controller and game applications are compatible and thathost device 12 and the smart phone are connected to the same local network. Ifserver 34 makes such a determination, it may provide the private network address of the smart phone to the game application to facilitate communication between the game and the game controller applications. - If needed, the game application and/or the game controller application may then modify the security policy of the web browser in order to allow network communication between the applications. For example, the smart phone, or another device, may provide a policy file or initiate an HTML5 handshake to modify the security profile of
web browser 16. - The game application and game controller application may then establish network communication with each other by, for example, opening one or more socket connections. Once the applications connect over the network, Player can use the game controller application running on his smart phone to control and play the game running within the web browser. The game controller and the game applications may then send data, including game control data, video data, audio data, button press data, accelerometer data, etc., back and forth between the game controller application and the game application.
- The game application and game controller application may then establish network communication with each other by, for example, opening one or more socket connections. The game application and game controller application may establish a TCP socket and a UDP socket, for example. The applications may send loss-sensitive data, such as button presses, acknowledgements, etc, over the TCP socket, and loss-tolerant data, such as streaming video, audio bytes, cinematics, accelerometer data, etc, over the UDP socket. In this way, the applications may avoid network or network stack bottlenecks and provide each other with low-latency network communication.
- The following example illustrates the operation of some embodiments of the present invention.
Browser application 14 may be a browser application executing withinweb browser 16, which may be executing onhost device 12.Browser application 14 sends a communication with the public network address ofhost device 12 toserver 34. -
Application 22 may be an application for communicating with and controlling content displayed bybrowser application 14, and may be executing onendpoint device 18.Application 22 may send a communication toserver 34 with the public and private network addresses ofendpoint device 18. -
Server 34 may determine thatapplication 22 andbrowser application 14 are compatible applications executing on devices connected to the same local network. If so,server 34 may send the private network address ofendpoint 18 tobrowser application 14 to facilitate connectivity between the two. -
Browser application 14 andapplication 22 may then communicate with each other overprivate network 24, and may modify the security policy ofweb browser 16 to allow for two way communication betweenbrowser application 14 andapplication 22. -
Browser application 14 andapplication 22 may then establish a loss-sensitive socket connection (e.g. a TCP connection) and a loss-tolerant socket connection (e.g. a UDP connection), and reduce network latency by sending loss-sensitive data over the loss-sensitive socket connection, and loss-tolerant data over the loss-tolerant socket connection. - The present disclosure makes reference to various block diagrams and flowcharts. One skilled in the art will recognize that the order and configuration of components in the block diagrams and steps in the flowcharts are not limitations and are provided for illustration only. Various appropriate configurations of components and devices, and various orders and sequences of operation may fall within the scope of the claims.
- While the invention has been described in connection with the specific embodiments thereof, it will be understood that it is capable of further modification. Furthermore, this application is intended to cover any variations, uses, or adaptations of the invention, including such departures from the present disclosure as come within known or customary practice in the art to which the invention pertains.
Claims (17)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/041,319 US8024469B1 (en) | 2010-03-05 | 2011-03-04 | System and method for connecting network sockets between applications |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US31110210P | 2010-03-05 | 2010-03-05 | |
US42197710P | 2010-12-10 | 2010-12-10 | |
US13/041,319 US8024469B1 (en) | 2010-03-05 | 2011-03-04 | System and method for connecting network sockets between applications |
Publications (2)
Publication Number | Publication Date |
---|---|
US20110219129A1 true US20110219129A1 (en) | 2011-09-08 |
US8024469B1 US8024469B1 (en) | 2011-09-20 |
Family
ID=44532226
Family Applications (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/041,319 Active US8024469B1 (en) | 2010-03-05 | 2011-03-04 | System and method for connecting network sockets between applications |
US13/041,313 Active US8019878B1 (en) | 2010-03-05 | 2011-03-04 | System and method for two way communication and controlling content in a web browser |
US13/042,286 Expired - Fee Related US8166181B2 (en) | 2010-03-05 | 2011-03-07 | System and method for two way communication and controlling content on a display screen |
US13/042,257 Active US8019867B1 (en) | 2010-03-05 | 2011-03-07 | System and method for two way communication and controlling a remote apparatus |
US13/041,951 Active US8171145B2 (en) | 2010-03-05 | 2011-03-07 | System and method for two way communication and controlling content in a game |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/041,313 Active US8019878B1 (en) | 2010-03-05 | 2011-03-04 | System and method for two way communication and controlling content in a web browser |
US13/042,286 Expired - Fee Related US8166181B2 (en) | 2010-03-05 | 2011-03-07 | System and method for two way communication and controlling content on a display screen |
US13/042,257 Active US8019867B1 (en) | 2010-03-05 | 2011-03-07 | System and method for two way communication and controlling a remote apparatus |
US13/041,951 Active US8171145B2 (en) | 2010-03-05 | 2011-03-07 | System and method for two way communication and controlling content in a game |
Country Status (7)
Country | Link |
---|---|
US (5) | US8024469B1 (en) |
EP (1) | EP2542982A4 (en) |
JP (1) | JP5730914B2 (en) |
KR (1) | KR20130018708A (en) |
AU (1) | AU2011222509C1 (en) |
CA (1) | CA2792038A1 (en) |
WO (5) | WO2011109777A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130219471A1 (en) * | 2012-02-20 | 2013-08-22 | Michael Stephen Brown | Establishing connectivity between an enterprise security perimeter of a device and an enterprise |
US9160693B2 (en) | 2010-09-27 | 2015-10-13 | Blackberry Limited | Method, apparatus and system for accessing applications and content across a plurality of computers |
US20150350068A1 (en) * | 2014-05-30 | 2015-12-03 | Apple Inc. | Client applications communicating via a user tunnel |
Families Citing this family (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2580239C (en) | 2004-09-21 | 2016-04-26 | Timeplay Entertainment Corporation | System, method and handheld controller for multi-player gaming |
US8266551B2 (en) * | 2010-06-10 | 2012-09-11 | Nokia Corporation | Method and apparatus for binding user interface elements and granular reflective processing |
AU2012212356B2 (en) | 2011-02-01 | 2016-10-06 | Timeplay Inc. | Systems and methods for interactive experiences and controllers therefor |
US20130055114A1 (en) * | 2011-08-25 | 2013-02-28 | Eitan Lev | Enhanced and Extended Browsing Via Companion Mobile Device |
US20140032733A1 (en) | 2011-10-11 | 2014-01-30 | Citrix Systems, Inc. | Policy-Based Application Management |
US8881229B2 (en) | 2011-10-11 | 2014-11-04 | Citrix Systems, Inc. | Policy-based application management |
US9215225B2 (en) | 2013-03-29 | 2015-12-15 | Citrix Systems, Inc. | Mobile device locking with context |
US9280377B2 (en) | 2013-03-29 | 2016-03-08 | Citrix Systems, Inc. | Application with multiple operation modes |
US8799994B2 (en) | 2011-10-11 | 2014-08-05 | Citrix Systems, Inc. | Policy-based application management |
US9529996B2 (en) | 2011-10-11 | 2016-12-27 | Citrix Systems, Inc. | Controlling mobile device access to enterprise resources |
US8996729B2 (en) | 2012-04-12 | 2015-03-31 | Nokia Corporation | Method and apparatus for synchronizing tasks performed by multiple devices |
EP2798483A1 (en) | 2011-12-28 | 2014-11-05 | Nokia Corporation | Application switcher |
WO2013126507A1 (en) * | 2012-02-21 | 2013-08-29 | Brass Monkey, Inc. | Mobile embedded servers systems and methods related thereto |
EP2648390B1 (en) * | 2012-04-04 | 2017-03-08 | Siemens Healthcare GmbH | Remote management of a diagnostic imaging device by means of remote desktop connections |
US9022870B2 (en) | 2012-05-02 | 2015-05-05 | Aquimo, Llc | Web-based game platform with mobile device motion sensor input |
KR101971623B1 (en) | 2012-05-10 | 2019-04-23 | 삼성전자주식회사 | Method for contents and user's interactions among multiple devices |
US20130303288A1 (en) * | 2012-05-11 | 2013-11-14 | Sony Corporation | Method and apparatus for providing content to a user device |
US9183398B2 (en) * | 2012-09-20 | 2015-11-10 | Qualcomm Incorporated | Content-driven screen polarization with application sessions |
US8745755B2 (en) | 2012-10-12 | 2014-06-03 | Citrix Systems, Inc. | Controlling device access to enterprise resources in an orchestration framework for connected devices |
US9516022B2 (en) | 2012-10-14 | 2016-12-06 | Getgo, Inc. | Automated meeting room |
US20140109176A1 (en) | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Configuring and providing profiles that manage execution of mobile applications |
US20140109171A1 (en) | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Providing Virtualized Private Network tunnels |
US8910239B2 (en) | 2012-10-15 | 2014-12-09 | Citrix Systems, Inc. | Providing virtualized private network tunnels |
CN104854561B (en) | 2012-10-16 | 2018-05-11 | 思杰系统有限公司 | Application program for application management framework encapsulates |
US9606774B2 (en) | 2012-10-16 | 2017-03-28 | Citrix Systems, Inc. | Wrapping an application with field-programmable business logic |
US20140108793A1 (en) | 2012-10-16 | 2014-04-17 | Citrix Systems, Inc. | Controlling mobile device access to secure data |
US9971585B2 (en) | 2012-10-16 | 2018-05-15 | Citrix Systems, Inc. | Wrapping unmanaged applications on a mobile device |
US20140297840A1 (en) | 2013-03-29 | 2014-10-02 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US8813179B1 (en) | 2013-03-29 | 2014-08-19 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US9455886B2 (en) | 2013-03-29 | 2016-09-27 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US10284627B2 (en) | 2013-03-29 | 2019-05-07 | Citrix Systems, Inc. | Data management for an application with multiple operation modes |
US9413736B2 (en) | 2013-03-29 | 2016-08-09 | Citrix Systems, Inc. | Providing an enterprise application store |
US9985850B2 (en) | 2013-03-29 | 2018-05-29 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US9355223B2 (en) | 2013-03-29 | 2016-05-31 | Citrix Systems, Inc. | Providing a managed browser |
US9360852B2 (en) | 2013-06-19 | 2016-06-07 | Billy R. Masten | Wireless network machine control or a hydraulic system |
JP6525967B2 (en) | 2013-12-06 | 2019-06-05 | 株式会社スクウェア・エニックス・ホールディングス | PROGRAM, RECORDING MEDIUM, INFORMATION PROCESSING DEVICE, AND CONTROL METHOD |
US9680918B2 (en) * | 2014-06-30 | 2017-06-13 | Fortinet, Inc. | Socket application program interface (API) for efficient data transactions |
CN104811760A (en) * | 2015-04-08 | 2015-07-29 | 深圳市鱼丸互动科技有限公司 | Multi-screen interaction method and system |
US10567518B2 (en) * | 2015-06-26 | 2020-02-18 | Western Digital Technologies, Inc. | Automatic discovery and onboarding of electronic devices |
US20170011595A1 (en) * | 2015-07-10 | 2017-01-12 | M-Biz Global Solutions Gmbh | Online challenge game method, online challenge game system and method for calculating advertisement costs |
JP6554350B2 (en) * | 2015-07-14 | 2019-07-31 | 株式会社Phone Appli | Service system |
US10148516B2 (en) * | 2015-07-28 | 2018-12-04 | Dell Products L.P. | Inter-networking device link provisioning system |
US9992238B2 (en) | 2015-11-11 | 2018-06-05 | International Business Machines Corporation | Proxy based data transfer utilizing direct memory access |
US10456672B2 (en) * | 2016-05-19 | 2019-10-29 | Google Llc | Methods and systems for facilitating participation in a game session |
US10999331B1 (en) | 2016-07-06 | 2021-05-04 | Google Llc | Reverse discovery and pairing of client devices to a media device |
US11794094B2 (en) | 2016-10-17 | 2023-10-24 | Aquimo Inc. | Method and system for using sensors of a control device for control of a game |
KR20180076619A (en) * | 2016-12-28 | 2018-07-06 | 에스케이테크엑스 주식회사 | Apparatus and method for recommendation of entity in smart page |
CN106740115A (en) * | 2017-01-22 | 2017-05-31 | 斑马信息科技有限公司 | Automobile instrument and middle control interactive system and method |
WO2019074952A2 (en) | 2017-10-10 | 2019-04-18 | Google Llc | Distributed sample-based game profiling with game metadata and metrics and gaming api platform supporting third-party content |
US11140207B2 (en) | 2017-12-21 | 2021-10-05 | Google Llc | Network impairment simulation framework for verification of real time interactive media streaming systems |
JP7005763B2 (en) | 2018-03-22 | 2022-01-24 | グーグル エルエルシー | Methods and systems for rendering and encoding content for online interactive gaming sessions |
FR3079380A1 (en) * | 2018-03-26 | 2019-09-27 | Orange | SECURITY MANAGEMENT OF A LOCAL COMMUNICATION NETWORK INCLUDING AT LEAST ONE COMMUNICABLE OBJECT. |
US11077364B2 (en) | 2018-04-02 | 2021-08-03 | Google Llc | Resolution-based scaling of real-time interactive graphics |
US11872476B2 (en) | 2018-04-02 | 2024-01-16 | Google Llc | Input device for an electronic system |
KR102614649B1 (en) | 2018-04-10 | 2023-12-14 | 구글 엘엘씨 | Memory management in gaming rendering |
WO2020102493A1 (en) | 2018-11-16 | 2020-05-22 | Google Llc | Shadow tracking of real-time interactive simulations for complex system analysis |
CN109739505B (en) | 2019-01-08 | 2019-11-29 | 网易(杭州)网络有限公司 | A kind for the treatment of method and apparatus of user interface |
US11159420B2 (en) * | 2019-04-17 | 2021-10-26 | Cloudflare, Inc. | Method and apparatus of automatic route optimization in a private virtual network for client devices of a local network |
CN111158632B (en) * | 2020-01-07 | 2022-02-25 | 山东超越数控电子股份有限公司 | Method for networking general audio interface under ARM processor |
US11778011B2 (en) | 2020-09-18 | 2023-10-03 | Infrared5, Inc. | Live streaming architecture with server-side stream mixing |
DE102022106007A1 (en) | 2022-03-15 | 2023-09-21 | Sebastian Pfeiffer | Entertainment system |
Citations (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010032265A1 (en) * | 2000-04-13 | 2001-10-18 | Nec Corporation. | Method of communication control and system thereof |
US6377993B1 (en) * | 1997-09-26 | 2002-04-23 | Mci Worldcom, Inc. | Integrated proxy interface for web based data management reports |
US20020091831A1 (en) * | 2000-11-10 | 2002-07-11 | Michael Johnson | Internet modem streaming socket method |
US20020151327A1 (en) * | 2000-12-22 | 2002-10-17 | David Levitt | Program selector and guide system and method |
US20030001883A1 (en) * | 2000-07-21 | 2003-01-02 | Samsung Electronics Co., Ltd. | Architecture for home network on world wide web with private-public IP address/URL mapping |
US20030046374A1 (en) * | 2001-08-31 | 2003-03-06 | Sony Corporation. | Bidirectional remote communication VIA browser plug-in |
US6678246B1 (en) * | 1999-07-07 | 2004-01-13 | Nortel Networks Limited | Processing data packets |
US20050003824A1 (en) * | 2001-11-30 | 2005-01-06 | Siris Vasilios A | Method of resource control in a wireless network |
US20050015584A1 (en) * | 2002-09-27 | 2005-01-20 | Hideaki Takechi | Server device and communication system connected to the internet |
US20050138460A1 (en) * | 2003-11-19 | 2005-06-23 | International Business Machines Corporation | Error recovery in a client/server application using two independent sockets for communication |
US20050261815A1 (en) * | 2004-05-20 | 2005-11-24 | Cowelchuk Glenn A | System for customizing settings and sounds for vehicle |
US20060039356A1 (en) * | 2004-07-23 | 2006-02-23 | Citrix Systems, Inc. | Systems and methods for facilitating a peer to peer route via a gateway |
US20060117107A1 (en) * | 2001-07-12 | 2006-06-01 | Yahoo! Inc. | Method and system for enabling a script on a first computer to exchange data with a script on a second computer over a network |
US20060152752A1 (en) * | 2002-08-23 | 2006-07-13 | Tdk Corporation | Log-in method for a client server system, a computer program, and a recording medium |
US7143137B2 (en) * | 2002-06-13 | 2006-11-28 | Nvidia Corporation | Method and apparatus for security protocol and address translation integration |
US20070100514A1 (en) * | 2005-11-02 | 2007-05-03 | Park Tai S | Remote control of conveyance and appliance functions |
US20070198144A1 (en) * | 2005-10-21 | 2007-08-23 | Norris William R | Networked multi-role robotic vehicle |
US20070232290A1 (en) * | 2006-04-03 | 2007-10-04 | Tatman Lance A | System and method for measuring user behavior and use of mobile equipment |
US7292588B2 (en) * | 2001-05-01 | 2007-11-06 | Milley Milton E | Wireless network computing |
US20080167732A1 (en) * | 1999-10-29 | 2008-07-10 | Sean Slavin | Method and system for remote control of a local system |
US20080183307A1 (en) * | 2007-01-26 | 2008-07-31 | Autani Corporation | Upgradeable Automation Devices, Systems, Architectures, and Methods |
US20080229095A1 (en) * | 2002-06-25 | 2008-09-18 | Ramesh Kalimuthu | Method and apparatus for dynamically securing voice and other delay-sensitive network traffic |
US20080261686A1 (en) * | 2007-04-19 | 2008-10-23 | James Carlton Bedingfield | Systems, methods and computer products for IPTV network game control |
US20080291916A1 (en) * | 2007-05-22 | 2008-11-27 | Bo Xiong | Systems and methods for dynamic quality of service |
US20080312782A1 (en) * | 2007-06-15 | 2008-12-18 | Gene Berdichevsky | Electric vehicle communication interface |
US7493383B1 (en) * | 2006-12-29 | 2009-02-17 | F5 Networks, Inc. | TCP-over-TCP using multiple TCP streams |
US20090055749A1 (en) * | 2007-07-29 | 2009-02-26 | Palm, Inc. | Application management framework for web applications |
US20090060452A1 (en) * | 2007-09-04 | 2009-03-05 | Apple Inc. | Display of Video Subtitles |
US20090135765A1 (en) * | 2000-12-22 | 2009-05-28 | Lewis Allan D | Wireless router system and method |
US20090153289A1 (en) * | 2007-12-12 | 2009-06-18 | Eric James Hope | Handheld electronic devices with bimodal remote control functionality |
US20090240698A1 (en) * | 2008-03-20 | 2009-09-24 | Microsoft Corporation | Computing environment platform |
US20090300137A1 (en) * | 2008-05-29 | 2009-12-03 | Research In Motion Limited | Method, system and devices for communicating between an internet browser and an electronic device |
US20090319644A1 (en) * | 2008-06-19 | 2009-12-24 | Symbol Technologies, Inc. | Methods and apparatus for automatically configuring computing devices for wireless network connections |
US7664096B2 (en) * | 2003-06-25 | 2010-02-16 | At&T Intellectual Property I, Lp | Remote location VOIP roaming behind firewalls |
US20100184422A1 (en) * | 2009-01-22 | 2010-07-22 | Yahoo! Inc. | Web-hosted framework for mobile applications |
US7797417B2 (en) * | 2000-10-02 | 2010-09-14 | Samsung Electronics Co., Ltd. | Method for providing service in IP-based network system |
US20100256971A1 (en) * | 2007-02-09 | 2010-10-07 | Dotemu | Method for simulating the operation of a device having an architecture and a processor determined by means of another device connected to a computer network |
US7818788B2 (en) * | 2006-02-14 | 2010-10-19 | Microsoft Corporation | Web application security frame |
US20100267448A1 (en) * | 2004-09-21 | 2010-10-21 | Timeplay Ip Inc. | System, method and handheld controller for multi-player gaming |
US7828654B2 (en) * | 2001-04-10 | 2010-11-09 | Carter Sr Russell O | Location based gaming system |
US20100299436A1 (en) * | 2009-05-20 | 2010-11-25 | Shafiqul Khalid | Methods and Systems for Using External Display Devices With a Mobile Computing Device |
US20110009193A1 (en) * | 2009-07-10 | 2011-01-13 | Valve Corporation | Player biofeedback for dynamically controlling a video game state |
US7890957B2 (en) * | 2006-09-08 | 2011-02-15 | Easyonme, Inc. | Remote management of an electronic presence |
Family Cites Families (72)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5694546A (en) * | 1994-05-31 | 1997-12-02 | Reisman; Richard R. | System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list |
US8062134B2 (en) * | 1996-11-14 | 2011-11-22 | Bally Gaming, Inc. | Browser manager for a networked gaming system and method |
US6468160B2 (en) * | 1999-04-08 | 2002-10-22 | Nintendo Of America, Inc. | Security system for video game system with hard disk drive and internet access capability |
US6892230B1 (en) | 1999-06-11 | 2005-05-10 | Microsoft Corporation | Dynamic self-configuration for ad hoc peer networking using mark-up language formated description messages |
AU5728500A (en) | 1999-06-11 | 2001-01-02 | Microsoft Corporation | Data driven remote device control model with general programming interface-to-network messaging adapter |
US9235955B2 (en) * | 2000-12-22 | 2016-01-12 | Bally Gaming, Inc. | Universal game monitoring unit and system |
US6684062B1 (en) * | 2000-10-25 | 2004-01-27 | Eleven Engineering Incorporated | Wireless game control system |
US7515718B2 (en) * | 2000-12-07 | 2009-04-07 | Igt | Secured virtual network in a gaming environment |
US7305697B2 (en) | 2001-02-02 | 2007-12-04 | Opentv, Inc. | Service gateway for interactive television |
US7730401B2 (en) * | 2001-05-16 | 2010-06-01 | Synaptics Incorporated | Touch screen with user interface enhancement |
US6865599B2 (en) * | 2001-09-04 | 2005-03-08 | Chenglin Zhang | Browser-to-browser, dom-based, peer-to-peer communication with delta synchronization |
US8708828B2 (en) * | 2001-09-28 | 2014-04-29 | Igt | Pluggable modular gaming modifiers and configuration templates for gaming environments |
EP1335535A1 (en) | 2002-01-31 | 2003-08-13 | BRITISH TELECOMMUNICATIONS public limited company | Network service selection |
US7818480B2 (en) | 2002-08-29 | 2010-10-19 | Raritan Americas, Inc. | Wireless management of remote devices |
FR2853187B1 (en) * | 2003-03-28 | 2006-01-13 | At & T Corp | SYSTEM FOR ALL NETWORK APPLICATION TO OPERATE TRANSPARENTLY THROUGH A NETWORK ADDRESS TRANSLATION DEVICE |
US7455590B2 (en) * | 2003-05-09 | 2008-11-25 | Microsoft Corporation | Sending messages in response to events occurring on a gaming service |
US20040266529A1 (en) * | 2003-06-30 | 2004-12-30 | Sony Computer Entertainment America Inc. | Methods and systems for remote execution of game content and presentation on a wireless portable device |
US7464272B2 (en) * | 2003-09-25 | 2008-12-09 | Microsoft Corporation | Server control of peer to peer communications |
WO2005032106A1 (en) * | 2003-09-30 | 2005-04-07 | Koninklijke Philips Electronics, N.V. | Client requested external address mapping |
TW200605574A (en) * | 2004-02-17 | 2006-02-01 | Ginganet Corp | Address resolution apparatus, address resolution method and telecommunication system thereof |
US8157635B2 (en) * | 2004-05-07 | 2012-04-17 | Scientific Games Holdings Limited | Method and apparatus for providing player incentives |
US7706401B2 (en) * | 2004-08-13 | 2010-04-27 | Verizon Business Global Llc | Method and system for providing interdomain traversal in support of packetized voice transmissions |
US8888600B2 (en) * | 2004-08-25 | 2014-11-18 | Igt | Emulation methods and devices for a gaming machine |
US20060063590A1 (en) * | 2004-09-21 | 2006-03-23 | Paul Abassi | Mechanism to control game usage on user devices |
AR051444A1 (en) * | 2004-09-24 | 2007-01-17 | Centocor Inc | PROTEINS DERIVED FROM IL-23P40 SPECIFIC IMMUNOGLOBULIN, COMPOSITIONS, EPITHOPES, METHODS AND USES |
US20060083187A1 (en) * | 2004-10-18 | 2006-04-20 | Mobile (R&D) Ltd. | Pairing system and method for wirelessly connecting communication devices |
US7966485B2 (en) * | 2004-12-01 | 2011-06-21 | Igt | Universal operating system to hardware platform interface for gaming machines |
US20060149811A1 (en) * | 2004-12-31 | 2006-07-06 | Sony Ericsson Mobile Communications Ab | Method for remotely controlling media devices via a communication network |
US20060288343A1 (en) * | 2005-06-20 | 2006-12-21 | Kim Pallister | Methods and apparatus to enable remote-user-interface-capable managed runtime environments |
US20110157196A1 (en) * | 2005-08-16 | 2011-06-30 | Exent Technologies, Ltd. | Remote gaming features |
US8278107B2 (en) * | 2005-09-13 | 2012-10-02 | Trustees Of Dartmouth College | Compositions and methods for regulating RNA translation via CD154 CA-dinucleotide repeat |
US20070088852A1 (en) | 2005-10-17 | 2007-04-19 | Zohar Levkovitz | Device, system and method of presentation of advertisements on a wireless device |
US8677020B2 (en) | 2005-10-17 | 2014-03-18 | Amobee Inc. | Device, system and method of wireless delivery of targeted advertisements |
JP5037004B2 (en) * | 2005-11-28 | 2012-09-26 | パナソニック株式会社 | Terminal equipment and communication system |
US7796982B2 (en) * | 2005-12-07 | 2010-09-14 | Tor Anumana, Inc. | Wireless controller device |
US20070184903A1 (en) * | 2006-02-08 | 2007-08-09 | Derek Liu | Network-based game system capable of serving massive number of game players |
US20070293319A1 (en) * | 2006-06-20 | 2007-12-20 | Microsoft Corporation | Transfer of Features Between Gaming Devices |
US7946918B2 (en) * | 2006-09-11 | 2011-05-24 | Apple Inc. | Allowing media and gaming environments to effectively interact and/or affect each other |
US20090156303A1 (en) * | 2006-11-10 | 2009-06-18 | Igt | Bonusing Architectures in a Gaming Environment |
US7873578B2 (en) * | 2007-03-30 | 2011-01-18 | Microsoft Corporation | Buy once play anywhere |
US8460109B2 (en) * | 2007-04-24 | 2013-06-11 | Igt | Gaming community management and personalization |
US20080287182A1 (en) * | 2007-05-14 | 2008-11-20 | Konami Gaming, Incorporated | Gaming machine and gaming system |
US9317110B2 (en) * | 2007-05-29 | 2016-04-19 | Cfph, Llc | Game with hand motion control |
US8285740B2 (en) * | 2007-06-06 | 2012-10-09 | Igt | Database queries within a gaming machine |
US20090005138A1 (en) * | 2007-06-28 | 2009-01-01 | Microsoft Corporation | User Creatable Machines |
US20090036216A1 (en) * | 2007-07-30 | 2009-02-05 | Trey Ratcliff | Video game for interactive engagement between multiple on-line participants in competition over internet websites |
WO2009026362A2 (en) | 2007-08-20 | 2009-02-26 | Garagegames, Inc. | System and method for moving a party from one game to the next |
WO2009055722A1 (en) | 2007-10-24 | 2009-04-30 | Jonathan Peter Deutsch | Various methods and apparatuses for accessing networked devices without accessible addresses via virtual ip addresses |
US20100172287A1 (en) * | 2007-10-25 | 2010-07-08 | Krieter Marcus | Temporal network server connected devices with off-line ad hoc update and interaction capability |
US20090128504A1 (en) * | 2007-11-16 | 2009-05-21 | Garey Alexander Smith | Touch screen peripheral device |
US20090172172A1 (en) * | 2007-12-21 | 2009-07-02 | Erik Lambert Graham | Systems and methods for enabling peer-to-peer communication among visitors to a common website |
JP2009169868A (en) * | 2008-01-18 | 2009-07-30 | Ntt Docomo Inc | Storage area access device and method for accessing storage area |
US20090199275A1 (en) | 2008-02-06 | 2009-08-06 | David Brock | Web-browser based three-dimensional media aggregation social networking application |
US20090248542A1 (en) | 2008-03-25 | 2009-10-01 | Houvener Robert C | Systems and methods for facilitating creative content discovery, sale and investment |
US8856268B2 (en) * | 2008-04-22 | 2014-10-07 | Microsoft Corporation | Sharing of console and web-based games and gaming profiles |
US20090291760A1 (en) * | 2008-05-22 | 2009-11-26 | Bennett Hepburn | Video Gaming Controller Bay for Mobile Devices |
US8406748B2 (en) * | 2009-01-28 | 2013-03-26 | Headwater Partners I Llc | Adaptive ambient services |
US8200795B2 (en) * | 2008-06-05 | 2012-06-12 | Sony Computer Entertainment Inc. | Mobile phone game interface |
US8727878B2 (en) * | 2008-07-18 | 2014-05-20 | Disney Enterprises, Inc. | Video game controller |
US8812361B2 (en) | 2008-07-24 | 2014-08-19 | At&T Intellectual Properties I, L.P. | System and method of targeted advertisement |
GB2463121A (en) * | 2008-09-09 | 2010-03-10 | Skype Ltd | Communications system with game playing facility |
WO2010062617A1 (en) | 2008-10-27 | 2010-06-03 | Social Gaming Network | Apparatuses, methods and systems for an interactive proximity display tether |
WO2010088313A1 (en) | 2009-01-29 | 2010-08-05 | Wms Gaming, Inc. | Configuring and controlling wagering game compatibility |
WO2010093831A1 (en) | 2009-02-11 | 2010-08-19 | Social Gaming Network | Apparatuses, methods and systems for an interactive proximity display tether with remote co-play |
JP5430982B2 (en) * | 2009-03-18 | 2014-03-05 | 任天堂株式会社 | GAME PROGRAM, GAME DEVICE, AND GAME CONTROL METHOD |
GB0905559D0 (en) | 2009-03-31 | 2009-05-13 | British Telecomm | Addressing scheme |
US9056249B2 (en) * | 2009-04-01 | 2015-06-16 | Activision Publishing, Inc. | Device and method for a streaming video game |
US8740701B2 (en) * | 2009-06-15 | 2014-06-03 | Wms Gaming, Inc. | Controlling wagering game system audio |
US9749387B2 (en) * | 2009-08-13 | 2017-08-29 | Sap Se | Transparently stateful execution of stateless applications |
US8313377B2 (en) * | 2009-10-14 | 2012-11-20 | Sony Computer Entertainment America Llc | Playing browser based games with alternative controls and interfaces |
US20110112895A1 (en) * | 2009-11-10 | 2011-05-12 | Sony Ericsson Mobile Communications Ab | Proximal game sharing |
US8631407B2 (en) * | 2010-01-07 | 2014-01-14 | Sonic Ip, Inc. | Real time flash based user interface for media playback device |
-
2011
- 2011-03-04 EP EP11751470.3A patent/EP2542982A4/en not_active Withdrawn
- 2011-03-04 CA CA2792038A patent/CA2792038A1/en not_active Abandoned
- 2011-03-04 JP JP2012556277A patent/JP5730914B2/en active Active
- 2011-03-04 US US13/041,319 patent/US8024469B1/en active Active
- 2011-03-04 AU AU2011222509A patent/AU2011222509C1/en active Active
- 2011-03-04 WO PCT/US2011/027294 patent/WO2011109777A1/en active Application Filing
- 2011-03-04 KR KR1020127024950A patent/KR20130018708A/en not_active Application Discontinuation
- 2011-03-04 WO PCT/US2011/027295 patent/WO2011109778A1/en active Application Filing
- 2011-03-04 US US13/041,313 patent/US8019878B1/en active Active
- 2011-03-07 WO PCT/US2011/027438 patent/WO2011109829A2/en active Application Filing
- 2011-03-07 US US13/042,286 patent/US8166181B2/en not_active Expired - Fee Related
- 2011-03-07 US US13/042,257 patent/US8019867B1/en active Active
- 2011-03-07 WO PCT/US2011/027431 patent/WO2011109824A1/en active Application Filing
- 2011-03-07 WO PCT/US2011/027429 patent/WO2011109822A1/en active Application Filing
- 2011-03-07 US US13/041,951 patent/US8171145B2/en active Active
Patent Citations (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6377993B1 (en) * | 1997-09-26 | 2002-04-23 | Mci Worldcom, Inc. | Integrated proxy interface for web based data management reports |
US6678246B1 (en) * | 1999-07-07 | 2004-01-13 | Nortel Networks Limited | Processing data packets |
US20080167732A1 (en) * | 1999-10-29 | 2008-07-10 | Sean Slavin | Method and system for remote control of a local system |
US20010032265A1 (en) * | 2000-04-13 | 2001-10-18 | Nec Corporation. | Method of communication control and system thereof |
US20030001883A1 (en) * | 2000-07-21 | 2003-01-02 | Samsung Electronics Co., Ltd. | Architecture for home network on world wide web with private-public IP address/URL mapping |
US7797417B2 (en) * | 2000-10-02 | 2010-09-14 | Samsung Electronics Co., Ltd. | Method for providing service in IP-based network system |
US20020091831A1 (en) * | 2000-11-10 | 2002-07-11 | Michael Johnson | Internet modem streaming socket method |
US20020151327A1 (en) * | 2000-12-22 | 2002-10-17 | David Levitt | Program selector and guide system and method |
US20090135765A1 (en) * | 2000-12-22 | 2009-05-28 | Lewis Allan D | Wireless router system and method |
US7828654B2 (en) * | 2001-04-10 | 2010-11-09 | Carter Sr Russell O | Location based gaming system |
US7292588B2 (en) * | 2001-05-01 | 2007-11-06 | Milley Milton E | Wireless network computing |
US20060117107A1 (en) * | 2001-07-12 | 2006-06-01 | Yahoo! Inc. | Method and system for enabling a script on a first computer to exchange data with a script on a second computer over a network |
US20030046374A1 (en) * | 2001-08-31 | 2003-03-06 | Sony Corporation. | Bidirectional remote communication VIA browser plug-in |
US20050003824A1 (en) * | 2001-11-30 | 2005-01-06 | Siris Vasilios A | Method of resource control in a wireless network |
US7143137B2 (en) * | 2002-06-13 | 2006-11-28 | Nvidia Corporation | Method and apparatus for security protocol and address translation integration |
US20080229095A1 (en) * | 2002-06-25 | 2008-09-18 | Ramesh Kalimuthu | Method and apparatus for dynamically securing voice and other delay-sensitive network traffic |
US20060152752A1 (en) * | 2002-08-23 | 2006-07-13 | Tdk Corporation | Log-in method for a client server system, a computer program, and a recording medium |
US20050015584A1 (en) * | 2002-09-27 | 2005-01-20 | Hideaki Takechi | Server device and communication system connected to the internet |
US7664096B2 (en) * | 2003-06-25 | 2010-02-16 | At&T Intellectual Property I, Lp | Remote location VOIP roaming behind firewalls |
US20050138460A1 (en) * | 2003-11-19 | 2005-06-23 | International Business Machines Corporation | Error recovery in a client/server application using two independent sockets for communication |
US20050261815A1 (en) * | 2004-05-20 | 2005-11-24 | Cowelchuk Glenn A | System for customizing settings and sounds for vehicle |
US20060039356A1 (en) * | 2004-07-23 | 2006-02-23 | Citrix Systems, Inc. | Systems and methods for facilitating a peer to peer route via a gateway |
US20100267448A1 (en) * | 2004-09-21 | 2010-10-21 | Timeplay Ip Inc. | System, method and handheld controller for multi-player gaming |
US20070198144A1 (en) * | 2005-10-21 | 2007-08-23 | Norris William R | Networked multi-role robotic vehicle |
US20070100514A1 (en) * | 2005-11-02 | 2007-05-03 | Park Tai S | Remote control of conveyance and appliance functions |
US7818788B2 (en) * | 2006-02-14 | 2010-10-19 | Microsoft Corporation | Web application security frame |
US20070232290A1 (en) * | 2006-04-03 | 2007-10-04 | Tatman Lance A | System and method for measuring user behavior and use of mobile equipment |
US7890957B2 (en) * | 2006-09-08 | 2011-02-15 | Easyonme, Inc. | Remote management of an electronic presence |
US7493383B1 (en) * | 2006-12-29 | 2009-02-17 | F5 Networks, Inc. | TCP-over-TCP using multiple TCP streams |
US20080183307A1 (en) * | 2007-01-26 | 2008-07-31 | Autani Corporation | Upgradeable Automation Devices, Systems, Architectures, and Methods |
US20100256971A1 (en) * | 2007-02-09 | 2010-10-07 | Dotemu | Method for simulating the operation of a device having an architecture and a processor determined by means of another device connected to a computer network |
US20080261686A1 (en) * | 2007-04-19 | 2008-10-23 | James Carlton Bedingfield | Systems, methods and computer products for IPTV network game control |
US20080291916A1 (en) * | 2007-05-22 | 2008-11-27 | Bo Xiong | Systems and methods for dynamic quality of service |
US20080312782A1 (en) * | 2007-06-15 | 2008-12-18 | Gene Berdichevsky | Electric vehicle communication interface |
US20090055749A1 (en) * | 2007-07-29 | 2009-02-26 | Palm, Inc. | Application management framework for web applications |
US20090060452A1 (en) * | 2007-09-04 | 2009-03-05 | Apple Inc. | Display of Video Subtitles |
US20090153289A1 (en) * | 2007-12-12 | 2009-06-18 | Eric James Hope | Handheld electronic devices with bimodal remote control functionality |
US20090240698A1 (en) * | 2008-03-20 | 2009-09-24 | Microsoft Corporation | Computing environment platform |
US20090300137A1 (en) * | 2008-05-29 | 2009-12-03 | Research In Motion Limited | Method, system and devices for communicating between an internet browser and an electronic device |
US7865573B2 (en) * | 2008-05-29 | 2011-01-04 | Research In Motion Limited | Method, system and devices for communicating between an internet browser and an electronic device |
US20090319644A1 (en) * | 2008-06-19 | 2009-12-24 | Symbol Technologies, Inc. | Methods and apparatus for automatically configuring computing devices for wireless network connections |
US20100184422A1 (en) * | 2009-01-22 | 2010-07-22 | Yahoo! Inc. | Web-hosted framework for mobile applications |
US20100299436A1 (en) * | 2009-05-20 | 2010-11-25 | Shafiqul Khalid | Methods and Systems for Using External Display Devices With a Mobile Computing Device |
US20110009193A1 (en) * | 2009-07-10 | 2011-01-13 | Valve Corporation | Player biofeedback for dynamically controlling a video game state |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9160693B2 (en) | 2010-09-27 | 2015-10-13 | Blackberry Limited | Method, apparatus and system for accessing applications and content across a plurality of computers |
US20130219471A1 (en) * | 2012-02-20 | 2013-08-22 | Michael Stephen Brown | Establishing connectivity between an enterprise security perimeter of a device and an enterprise |
US9015809B2 (en) * | 2012-02-20 | 2015-04-21 | Blackberry Limited | Establishing connectivity between an enterprise security perimeter of a device and an enterprise |
US20150350068A1 (en) * | 2014-05-30 | 2015-12-03 | Apple Inc. | Client applications communicating via a user tunnel |
US9485177B2 (en) * | 2014-05-30 | 2016-11-01 | Apple Inc. | Client applications communicating via a user tunnel |
Also Published As
Publication number | Publication date |
---|---|
US20110219131A1 (en) | 2011-09-08 |
US8019878B1 (en) | 2011-09-13 |
JP2013521584A (en) | 2013-06-10 |
KR20130018708A (en) | 2013-02-25 |
CA2792038A1 (en) | 2011-09-09 |
JP5730914B2 (en) | 2015-06-10 |
EP2542982A4 (en) | 2016-10-26 |
AU2011222509A1 (en) | 2012-09-27 |
WO2011109824A1 (en) | 2011-09-09 |
US20110219124A1 (en) | 2011-09-08 |
WO2011109829A2 (en) | 2011-09-09 |
WO2011109777A1 (en) | 2011-09-09 |
WO2011109822A1 (en) | 2011-09-09 |
AU2011222509C1 (en) | 2015-05-28 |
US20110219130A1 (en) | 2011-09-08 |
EP2542982A1 (en) | 2013-01-09 |
AU2011222509B2 (en) | 2015-01-22 |
US20110219062A1 (en) | 2011-09-08 |
WO2011109829A3 (en) | 2014-06-05 |
US8019867B1 (en) | 2011-09-13 |
WO2011109778A1 (en) | 2011-09-09 |
US8171145B2 (en) | 2012-05-01 |
US8024469B1 (en) | 2011-09-20 |
US8166181B2 (en) | 2012-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8024469B1 (en) | System and method for connecting network sockets between applications | |
US20220247624A1 (en) | Managing network connected devices | |
US10637724B2 (en) | Managing network connected devices | |
US9231904B2 (en) | Deploying and managing networked devices | |
US9712486B2 (en) | Techniques for the deployment and management of network connected devices | |
US20130179593A1 (en) | Cloud computing controlled gateway for communication networks | |
US10182126B2 (en) | Multilevel redirection in a virtual desktop infrastructure environment | |
US8386614B2 (en) | Network connection manager | |
JP2009508260A (en) | Port sharing among multiple processes | |
KR20140012673A (en) | Method and system of providing internet protocol(ip) data communication in a nfc peer to peer communication environment | |
US11595306B2 (en) | Executing workloads across multiple cloud service providers | |
CN110417632B (en) | Network communication method, system and server | |
Carlson et al. | An ad-hoc smart gateway platform for the web of things | |
WO2013126507A1 (en) | Mobile embedded servers systems and methods related thereto | |
US20110276669A1 (en) | Method and System for Peer-to-Peer Stream | |
KR20130100971A (en) | Method and system for providing security for universal plug and play operations in a home network environment based on ownership rights |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
AS | Assignment |
Owner name: BRASS MONKEY, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ALLEN, CHRISTOPHER;BURTON, TREVOR;ZUPKO, ANDREW;SIGNING DATES FROM 20110419 TO 20110512;REEL/FRAME:026418/0133 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: INFRARED5, INC., MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BRASS MONKEY, INC.;REEL/FRAME:036778/0292 Effective date: 20151012 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2552); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
FEPP | Fee payment procedure |
Free format text: 11.5 YR SURCHARGE- LATE PMT W/IN 6 MO, SMALL ENTITY (ORIGINAL EVENT CODE: M2556); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2553); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 12 |