# US 2014/0195690 A1 · Zero configuration communication between a browser and a networked media device

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0195690 A1
- Document ID: US20140195690A1
- Status: Published application
- Kind: A1
- Application number: 13/736,031
- Filed: 2013-01-07
- Published: 2014-07-10
- Earliest claimed: 2013-01-07
- Assignees: Free Stream Media Corp.
- Inventors: David Harrison; Jan Brittenson; Karthik Kailash
- Web page: https://patentgrep.com/patent/US20140195690A1

## CPC

- H04L 65/60: Network streaming of media packets
- G06F 15/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 {(coordinating program control therefor G06F9/52; in regulating and control system G05B)}
- G06F 21/123: {by using dedicated hardware, e.g. dongles, smart cards, cryptographic processors, global positioning systems [GPS] devices}
- G06F 21/34: involving the use of external additional devices, e.g. dongles or smart cards
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- H04L 12/189: {in combination with wireless systems (selective distribution or broadcast in wireless communication networks H04W4/06)}
- H04L 47/806: {Broadcast or multicast traffic}
- H04L 49/201: Multicast operation; Broadcast operation
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 65/611: for multicast or broadcast (systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06)
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/125: involving control of end-device applications over a network
- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04W 8/24: Transfer of terminal data
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A method, apparatus and system related to zero configuration communication between a browser and a networked media device are disclosed. In one embodiment, a method of a client device includes constraining an executable environment in a security sandbox, executing a sandboxed application in the executable environment using a processor and a memory, and automatically instantiating a connection between the sandboxed application and a sandbox reachable service of a networked media device. The method may include processing an identification data associated with the sandbox reachable service sharing a public address with the client device. The method may also include determining a private address pair of the sandbox reachable service based on the identification data. Further, the method may include establishing a communication session between the sandboxed application and the sandbox reachable service using a cross-site scripting technique of the security sandbox or appending a header of a hypertext transfer protocol.

## Claims

### Claim 1

A method of a client device comprising:
constraining an executable environment in a security sandbox;
executing a sandboxed application in the executable environment using a processor and a memory; and
automatically instantiating a connection between the sandboxed application and a sandbox reachable service of a networked media device.

### Claim 2 (depends on 1)

The method of claim 1 further comprising at least one of:
processing an identification data associated with the sandbox reachable service sharing a public address with the client device;
determining a private address pair of the sandbox reachable service based on the identification data; and
establishing a communication session between the sandboxed application and the sandbox reachable service using a cross-site scripting technique of the security sandbox.

### Claim 3 (depends on 2)

The method of claim 2 further comprising:
appending a header of a hypertext transfer protocol to permit the networked media device to communicate with the sandboxed application as a permitted origin domain through a Cross-origin resource sharing (CORS) algorithm, wherein the header is either one of a origin header when the CORS algorithm is applied and a referrer header in an alternate algorithm.

### Claim 4 (depends on 2)

The method of claim 2 further comprising:
accessing a pairing server when processing the identification data associated with the sandbox reachable service sharing the public address with the client device,
wherein the pairing server performs a discovery lookup of any device that has announced that it shares the public address associated with the client device, and
wherein the sandbox reachable service announces itself to the pairing server prior to the establishment of the communication session between the sandboxed application and the sandbox reachable service.

### Claim 5 (depends on 4)

The method of claim 4 further comprising at least one of:
wherein the sandbox reachable service announces an availability of the sandbox reachable service across a range of public addresses such that the sandboxed application communicates with the sandbox reachable service in any one of the range of the public addresses,
wherein the range of public addresses is known by the pairing server so that the announcement of the availability of the sandbox reachable service across the range of public addresses is unnecessary,
wherein the sandbox reachable service communicates at least one of a global unique identifier and an alphanumeric name to the pairing server along with the private address pair of the sandbox reachable service, and
wherein the private address pair includes a private IP address and a port number associated with the sandbox reachable service.

### Claim 6 (depends on 2)

The method of claim 2 further comprising:
eliminating a communication through a centralized infrastructure when the sandboxed application and the sandbox reachable service communicate in a shared network common to the client device and the networked media device when the connection is established, wherein the shared network is at least one of a local area network, a multicast network, an anycast network, and a multilan network;
minimizing a latency in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked media device when the connection is established; and
improving privacy in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked media device when the connection is established.

### Claim 7 (depends on 1)

The method of claim 1 further comprising:
wherein the sandboxed application is at least one of a web page, a script, a binary executable, an intermediate bytecode, an abstract syntax tree, and an executable application in the security sandbox,
wherein the sandboxed application comprises at least one of a markup language application such as a HyperText Markup Language 5 (HTML5) application, a Javascript® application, an Adobe® Flash® application, a Microsoft® Silverlight® application, a JQuery® application, and an Asynchronous Javascript® and a XML (AJAX) application, and
wherein an access control algorithm governs a policy through which a secondary authentication is required when establishing a communication between the sandboxed application and the networked media device.

### Claim 8 (depends on 7)

The method of claim 7 further comprising:
utilizing an exception to a same origin policy through a use of at least one of a hyperlink, a form, the script, a frame, a header, and an image when establishing the connection between the sandboxed application and the sandbox reachable service.

### Claim 9 (depends on 1)

The method of claim 1 further comprising:
extending the security sandbox with a discovery algorithm and a relay algorithm through a discovery module and a relay module added to the security sandbox; and
bypassing a pairing server having the discovery algorithm and the relay algorithm when establishing the connection between the sandboxed application and the sandbox reachable service when the security sandbox is extended with the discovery algorithm and the relay algorithm through the discovery module and the relay module added to the security sandbox.

### Claim 10 (depends on 9)

The method of claim 9 further comprising:
applying the discovery algorithm of the security sandbox to determine that the networked media device having the sandbox reachable service communicates in a shared network common to the client device and the networked media device; and
applying the relay algorithm of the security sandbox to establish the connection between the sandboxed application and the sandbox reachable service of the networked media device.

### Claim 11 (depends on 10)

The method of claim 10:
wherein the discovery algorithm utilizes a protocol comprising at least one of a Bonjour® protocol, a SSDP protocol, a LSD uTorrent® protocol, a multicast protocol, an anycast protocol, and another Local Area Network (LAN) based protocol that discovers services in a LAN based on a broadcast from any one of an operating system service, the security sandbox, the client device, the sandbox reachable service, and the networked media device.

### Claim 12 (depends on 1)

The method of claim 1:
wherein a cookie associated with the security sandbox is used to store a remote access token on a storage of the client device,
wherein the remote access token identifies at least one of a set of communicable private Internet Protocol (IP) addresses and hardware addresses associated with sandbox reachable services that previously operated on a common shared network with the client device, and
wherein the client device can communicate with the sandbox reachable services that previously operated on the common shared network through the remote access token.

### Claim 13 (depends on 1)

The method of claim 1:
wherein the client device and the networked media device reside on networks that are incommunicable with each other comprising at least one of a firewall separation, a different network separation, a physical separation, an unreachable connection separation, and
wherein the sandboxed application of the security sandbox of the client device and the sandbox reachable service of the networked media device communicate with each other through a relay service employed by a pairing server having a discovery module and a relay module to facilitate a trusted communication between the sandboxed application and the sandbox reachable service.

### Claim 14 (depends on 13)

The method of claim 13:
wherein the trusted communication is facilitated in a manner such that the sandboxed application never learns at least one of a private IP address and a hardware address of the networked media device when:
a first Network Address Translator (NAT) device coupled with a network on which the client device operates to receive communications from a public IP address of a different network on which the sandbox reachable service operates, and
wherein a second NAT device coupled with the different network on which the networked media device operates to translate the private IP address of the networked media device to the public IP address visible to the sandboxed application.

### Claim 15 (depends on 14)

The method of claim 14:
wherein the networked media device comprises a plurality of sandbox reachable applications including the sandbox reachable application, and wherein a service agent module of the networked media device coordinates communications with the discovery module of at least one of the security sandbox and the pairing server,
wherein the security sandbox is at least one of an operating system on which the sandboxed application is hosted and a browser application of the operating system, and
wherein the networked media device is at least one of a television, a projection screen, a multimedia display, a touchscreen display, an audio device, and a multidimensional visual presentation device.

### Claim 16 (depends on 15)

The method of claim 15 further comprising:
utilizing at least one of a WebSocket and a long polling service message query interface to reduce a latency of message delivery during the trusted communication between the sandboxed application and the sandbox reachable service; and
optimizing a polling period between polling such that it is less than a timeout period of a session through the relay service.

### Claim 17 (depends on 16)

The method of claim 16 further comprising:
initiating the relay service through at least one of a series of web pages where information is communicated using hyperlinks that point at the pairing server, and a form having a confirmation dialog that is submitted back to the pairing server, and
wherein a global unique identifier is masked through the pairing server when the confirmation dialog is served from the pairing server.

### Claim 18

A method of a networked device comprising:
announcing a sandbox reachable service of the networked device to a discovery module using a processor and memory; and
automatically instantiating a communication between the sandbox reachable service of the networked device and a client device when a relay module sends a request from a sandboxed application of the client device to the sandbox reachable service.

### Claim 19 (depends on 18)

The method of claim 18 wherein the client device to operate in at least one manner such that the client device:
to process an identification data associated with the sandbox reachable service sharing a public address with the client device;
to determine a private address pair of the sandbox reachable service based on the identification data; and
to establish a communication session between the sandboxed application and the sandbox reachable service using a cross-site scripting technique of a security sandbox.

### Claim 20 (depends on 19)

The method of claim 19 further comprising:
appending a header of a hypertext transfer protocol to permit the networked device to communicate with the sandboxed application as a permitted origin domain through a Cross-origin resource sharing (CORS) algorithm, wherein the header is either one of a origin header when the CORS algorithm is applied and a referrer header in an alternate algorithm.

### Claim 21 (depends on 19)

The method of claim 19 wherein the client device:
to access a pairing server when processing the identification data associated with the sandbox reachable service sharing the public address with the client device,
wherein the pairing server performs a discovery lookup of any devices that have announced that they share the public address associated with the client device, and
wherein the sandbox reachable service announces itself to the pairing server prior to the establishment of the communication session between the sandboxed application and the sandbox reachable service.

### Claim 22 (depends on 21)

The method of claim 21 further comprising at least one of:
announcing an availability of the sandbox reachable service across a range of public addresses such that the sandboxed application communicates with the sandbox reachable service in any one of the range of the public addresses; and
communicating at least one of a global unique identifier, a hardware address, and an alphanumeric name to the pairing server along with the private address pair of the sandbox reachable service, and
wherein the private address pair includes a private IP address and a port number associated with the sandbox reachable service.

### Claim 23 (depends on 19)

The method of claim 19 further comprising:
eliminating a communication through a centralized infrastructure when the sandboxed application and the sandbox reachable service communicate in a shared network common to the client device and the networked device when the communication is established, wherein the shared network is at least one of a local area network, a multicast network, an anycast network, and a multilan network;
minimizing a latency in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked device when the communication is established; and
improving privacy in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked device when the communication is established.

### Claim 24 (depends on 18)

The method of claim 18:
wherein the sandboxed application is at least one of a web page, a script, a binary executable, an intermediate bytecode, an abstract syntax tree, and an executable application in a security sandbox,
wherein the sandboxed application comprises at least one of a markup language application such as a HyperText Markup Language 5 (HTML5) application, a Javascript® application, an Adobe® Flash® application, a Microsoft® Silverlight® application, a JQuery® application, and an Asynchronous Javascript® and a XML (AJAX) application, and
wherein an access control algorithm governs a policy through which a secondary authentication is required when establishing a communication between the sandboxed application and the networked device.

### Claim 25 (depends on 24)

The method of claim 24 wherein the client device:
to utilize an exception to a same origin policy through a use of at least one of a hyperlink, a form, the script, a frame, a header, and an image when establishing the communication between the sandboxed application and the sandbox reachable service.

### Claim 26 (depends on 18)

The method of claim 18 wherein the client device:
to extend a security sandbox with a discovery algorithm and a relay algorithm through the discovery module and the relay module added to the security sandbox; and
to bypass a pairing server having the discovery algorithm and the relay algorithm when establishing the communication between the sandboxed application and the sandbox reachable service when the security is extended with the discovery algorithm and the relay algorithm through the discovery module and the relay module added to the security sandbox.

### Claim 27 (depends on 26)

The method of claim 26 wherein the client device:
to apply the discovery algorithm of the security sandbox to determine that the networked device having the sandbox reachable service communicates in a shared network common to the client device and the networked device; and
to apply the relay algorithm of the security sandbox to establish the communication between the sandboxed application and the sandbox reachable service of the networked device.

### Claim 28 (depends on 27)

The method of claim 27:
wherein the discovery algorithm utilizes a protocol comprising at least one of a Bonjour® protocol, a SSDP protocol, a LSD uTorrent® protocol, a multicast protocol, an anycast protocol, and another Local Area Network (LAN) based protocol that discovers services in a LAN based on a broadcast from any one of an operating system service, the security sandbox, the client device, the sandbox reachable service, and the networked device.

### Claim 29 (depends on 28)

The method of claim 28:
wherein a cookie associated with the security sandbox is used to store a remote access token on a storage of the client device,
wherein the remote access token identifies at least one of a set of communicable private Internet Protocol (IP) addresses and hardware addresses associated with sandbox reachable services that previously operated on a common shared network with the client device, and
wherein the client device can communicate with the sandbox reachable services that previously operated on the common shared network through the remote access token.

### Claim 30 (depends on 29)

The method of claim 29:
wherein the client device and the networked device reside on networks that are incommunicable with each other comprising at least one of a firewall separation, a different network separation, a physical separation, an unreachable connection separation, and
wherein the sandboxed application of the security sandbox of the client device and the sandbox reachable service of the networked device communicate with each other through a relay service employed by the pairing server having the discovery module and the relay module to facilitate a trusted communication between the sandboxed application and the sandbox reachable service.

### Claim 31 (depends on 30)

The method of claim 30:
wherein the trusted communication is facilitated in a manner such that the sandboxed application never learns at least one of a private IP address and a hardware address of the networked device when:
a first Network Address Translator (NAT) device coupled with a network on which the client device operates to receives communications from a public IP address of a different network on which the sandbox reachable service operates, and
wherein a second NAT device coupled with the different network on which the networked device operates to translates the private IP address of the networked device to the public IP address visible to the sandboxed application.

### Claim 32 (depends on 31)

The method of claim 31:
wherein the networked device comprises a plurality of sandbox reachable applications including the sandbox reachable application, and wherein a service agent module of the networked device coordinates communications with the discovery module of at least one of the security sandbox and the pairing server,
wherein the security sandbox is at least one of an operating system on which the sandboxed application is hosted and a browser application of the operating system, and
wherein the networked device is at least one of a television, a projection screen, a multimedia display, a touchscreen display, an audio device, a weather measurement device, a traffic monitoring device, a status update device, a global positioning device, a geospatial estimation device, a tracking device, a bidirectional communication device, a unicast device, a broadcast device, and a multidimensional visual presentation device.

### Claim 33 (depends on 32)

The method of claim 32 wherein the client device:
to utilize at least one of a WebSocket and a long polling service message query interface to reduce a latency of message delivery during the trusted communication between the sandboxed application and the sandbox reachable service; and
to optimize a polling period between polling such that it is less than a timeout period of a session through the relay service.

### Claim 34 (depends on 33)

The method of claim 33 wherein the client device:
to initiate the relay service through at least one of a series of web pages where information is communicated using hyperlinks that point at the pairing server, and a form having a confirmation dialog that is submitted back to the pairing server, and
wherein a global unique identifier is masked through the pairing server when the confirmation dialog is served from the pairing server.

### Claim 35

A system comprising:
a networked device to announce a sandbox reachable service of the networked device to a discovery module using a processor and memory; and
a client device to constrain an executable environment in a security sandbox, to execute a sandboxed application in the security sandbox, and to automatically instantiate a connection between the sandboxed application and the sandbox reachable service of the networked device.

### Claim 36 (depends on 35)

The system of claim 35 wherein the client device:
to process an identification data associated with the sandbox reachable service sharing a public address with the client device;
to determine a private address pair of the sandbox reachable service based on the identification data; and
to establish a communication session between the sandboxed application and the sandbox reachable service using a cross-site scripting technique of the security sandbox.

### Claim 37 (depends on 36)

The system of claim 36:
wherein the communication session is established by appending a header of a hypertext transfer protocol to permit the networked device to communicate with the sandboxed application as a permitted origin domain through a Cross-origin resource sharing (CORS) algorithm, wherein the header is either one of a origin header when the CORS algorithm is applied and a referrer header in an alternate algorithm.

### Claim 38 (depends on 36)

The system of claim 36 wherein the client device:
to access a pairing server when processing the identification data associated with the sandbox reachable service sharing the public address with the client device,
wherein the pairing server performs a discovery lookup of any device that have announced that they share the public address associated with the client device, and
wherein the sandbox reachable service announces itself to the pairing server prior to the establishment of the communication session between the sandboxed application and the sandbox reachable service.

### Claim 39 (depends on 38)

The system of claim 38 wherein the networked device to at least one of:
announce an availability of the sandbox reachable service across a range of public addresses such that the sandboxed application communicates with the sandbox reachable service in any one of the range of the public addresses,
communicate at least one of a global unique identifier and an alphanumeric name to the pairing server along with at least one of a hardware address associated with the networked device, a public address pair associated with a sandbox reachable service of the networked device, and a private address pair associated with the sandbox reachable service of the networked device, and
wherein the private address pair includes a private IP address and a port number associated with the sandbox reachable service.

### Claim 40 (depends on 39)

The system of claim 39 wherein the client device:
to eliminate a communication through a centralized infrastructure when the sandboxed application and the sandbox reachable service communicate in a shared network common to the client device and the networked device when the connection is established, wherein the shared network is at least one of a local area network, a multicast network, an anycast network, and a multilan network;
to minimize a latency in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked device when the connection is established; and
to improve privacy in the communication session when the sandboxed application and the sandbox reachable service communicate in the shared network common to the client device and the networked device when the connection is established.

### Claim 41 (depends on 35)

The system of claim 35:
wherein the sandboxed application is at least one of a web page, a script, a binary executable, an intermediate bytecode, an abstract syntax tree, and an executable application in the security sandbox,
wherein the sandboxed application comprises at least one of a markup language application such as a HyperText Markup Language 5 (HTML5) application, a Javascript® application, an Adobe® Flash® application, a Microsoft® Silverlight® application, a JQuery® application, and an Asynchronous Javascript® and a XML (AJAX) application, and
wherein an access control algorithm governs a policy through which a secondary authentication is required when establishing a communication between the sandboxed application and the networked device.

### Claim 42 (depends on 41)

The system of claim 41 wherein the client device:
to utilize an exception to a same origin policy through a use of at least one of a hyperlink, a form, the script, a frame, a header, and an image when establishing the connection between the sandboxed application and the sandbox reachable service.

### Claim 43 (depends on 35)

The system of claim 35 wherein the client device:
to extend the security sandbox with a discovery algorithm and a relay algorithm through the discovery module and a relay module added to the security sandbox, and
to bypass a pairing server having the discovery algorithm and the relay algorithm when establishing the connection between the sandboxed application and the sandbox reachable service when the security is extended with the discovery algorithm and the relay algorithm through the discovery module and the relay module added to the security sandbox.

### Claim 44 (depends on 43)

The system of claim 43 wherein the client device:
to apply the discovery algorithm of the security sandbox to determine that the networked device having the sandbox reachable service communicates in a shared network common to the client device and the networked device, and
to apply the relay algorithm of the security sandbox to establish the connection between the sandboxed application and the sandbox reachable service of the networked device.

### Claim 45 (depends on 44)

The system of claim 44:
wherein the discovery algorithm utilizes a protocol comprising at least one of a Bonjour® protocol, a SSDP protocol, a LSD uTorrent® protocol, a multicast protocol, an anycast protocol, and another Local Area Network (LAN) based protocol that discovers services in a LAN based on a broadcast from any one of an operating system service, the security sandbox, the client device, the sandbox reachable service, and the networked device.

### Claim 46 (depends on 45)

The system of claim 45:
wherein a cookie associated with the security sandbox is used to store a remote access token on a storage of the client device,
wherein the remote access token identifies at least one of a set of communicable private Internet Protocol (IP) addresses and hardware addresses associated with sandbox reachable services that previously operated on a common shared network with the client device, and
wherein the client device can communicate with the sandbox reachable services that previously operated on the common shared network through the remote access token.

### Claim 47 (depends on 46)

The system of claim 46:
wherein the client device and the networked device reside on networks that are incommunicable with each other comprising at least one of a firewall separation, a different network separation, a physical separation, an unreachable connection separation, and
wherein the sandboxed application of the security sandbox of the client device and the sandbox reachable service of the networked device communicate with each other through a relay service employed by the pairing server having the discovery module and the relay module to facilitate a trusted communication between the sandboxed application and the sandbox reachable service.

### Claim 48 (depends on 47)

The system of claim 47:
wherein the trusted communication is facilitated in a manner such that the sandboxed application never learns at least one of a private IP address and a hardware address of the networked device when:
a first Network Address Translator (NAT) device coupled with a network on which the client device operates to receives communications from a public IP address of a different network on which the sandbox reachable service operates, and
wherein a second NAT device coupled with the different network on which the networked device operates to translates the private IP address of the networked device to the public IP address visible to the sandboxed application.

### Claim 49 (depends on 48)

The system of claim 48:
wherein the networked device comprises a plurality of sandbox reachable applications including the sandbox reachable application, and wherein a service agent module of the networked device coordinates communications with the discovery module of at least one of the security sandbox and the pairing server,
wherein the security sandbox is at least one of an operating system on which the sandboxed application is hosted and a browser application of the operating system, and
wherein the networked device is at least one of a television, a projection screen, a multimedia display, a touchscreen display, an audio device, a weather measurement device, a traffic monitoring device, a status update device, a global positioning device, a geospatial estimation device, a tracking device, a bidirectional communication device, a unicast device, a broadcast device, and a multidimensional visual presentation device.

### Claim 50 (depends on 49)

The system of claim 49 wherein the client device:
to utilize at least one of a WebSocket and a long polling service message query interface to reduce a latency of message delivery during the trusted communication between the sandboxed application and the sandbox reachable service, and
to optimize a polling period between polling such that it is less than a timeout period of a session through the relay service.

### Claim 51 (depends on 50)

The system of claim 50 wherein the client device:
to initiate the relay service through at least one of a series of web pages where information is communicated using hyperlinks that point at the pairing server, and a form having a confirmation dialog that is submitted back to the pairing server, and
wherein a global unique identifier is masked through the pairing server when the confirmation dialog is served from the pairing server.

### Claim 52

A method of a pairing server comprising:
receiving at least one of a global unique identifier and an alphanumeric name in an announcement from a networked device along with at least one of a hardware address associated with the networked device, a public address pair associated with a sandbox reachable service of the networked device, and a private address pair associated with the sandbox reachable service of the networked device;
storing at least one of the global unique identifier and the alphanumeric name in the announcement from the networked device along with at least one of the hardware address associated with the networked device, the public address pair associated with the sandbox reachable service of networked device, and the private address pair associated the sandbox reachable service of the networked device using a processor and a memory; and
communicating at least one of the global unique identifier and the alphanumeric name along with at least one of the hardware address associated with the network device, the public address pair associated with the sandbox reachable service of the networked device, and the private address pair associated with the sandbox reachable service of the networked device to a client device when a shared network is determined to be commonly associated with the client device and the networked device, wherein the shared network is at least one of a local area network, a multicast network, an anycast network, and a multilan network.

### Claim 53 (depends on 52)

The method of claim 52:
wherein the range of public addresses is known by the pairing server so that the announcement of the availability of the sandbox reachable service across the range of public addresses is unnecessary, and
wherein the shared network is determined to be commonly associated with the client device and the networked device when it is presently shared by the networked device and the client device.

### Claim 54 (depends on 52)

The method of claim 52:
wherein the shared network is determined to be commonly associated with the client device and the networked device when it was previously shared by the networked device and the client device,
wherein a cookie associated with a security sandbox of the client device is used to store a remote access token on a storage of the client device,
wherein the remote access token identifies at least one of a set of communicable private Internet Protocol (IP) addresses and hardware addresses associated with sandbox reachable services that previously operated on a common shared network with the client device, and
wherein the client device can communicate with the sandbox reachable services that previously operated on the common shared network through the remote access token.

### Claim 55 (depends on 52)

The method of claim 52:
wherein the client device and the networked device reside on networks that are incommunicable with each other comprising at least one of a firewall separation, a different network separation, a physical separation, an unreachable connection separation, and
wherein a sandboxed application of a security sandbox of the client device and the sandbox reachable service of the networked device communicate with each other through a relay service employed by the pairing server having a discovery module and a relay module to facilitate a trusted communication between the sandboxed application and the sandbox reachable service.

### Claim 56 (depends on 55)

The method of claim 55:
wherein the trusted communication is facilitated in a manner such that the sandboxed application never learns at least one of a private IP address and a hardware address of the networked device when:
a first Network Address Translator (NAT) device coupled with a network on which the client device operates to receives communications from a public IP address of a different network on which the sandbox reachable service operates, and
wherein a second NAT device coupled with the different network on which the networked device operates to translates the private IP address of the networked device to the public IP address visible to the sandboxed application.

### Claim 57 (depends on 56)

The method of claim 56:
wherein the networked device comprises a plurality of sandbox reachable applications including the sandbox reachable application, and wherein a service agent module of the networked device coordinates communications with the discovery module of at least one of the security sandbox and the pairing server,
wherein the security sandbox is at least one of an operating system on which the sandboxed application is hosted and a browser application of the operating system, and
wherein the networked device is at least one of a television, a projection screen, a multimedia display, a touchscreen display, an audio device, a weather measurement device, a traffic monitoring device, a status update device, a global positioning device, a geospatial estimation device, a tracking device, a bidirectional communication device, a unicast device, a broadcast device, and a multidimensional visual presentation device.

### Claim 58 (depends on 57)

The method of claim 57 further comprising:
utilizing at least one of a WebSocket and a long polling service message query interface to reduce a latency of message delivery during the trusted communication between the sandboxed application and the sandbox reachable service; and
optimizing a polling period between polling such that it is less than a timeout period of a session through the relay service.

### Claim 59 (depends on 58)

The method of claim 58 further comprising:
initiating the relay service through at least one of a series of web pages where information is communicated using hyperlinks that point at the pairing server, and a form having a confirmation dialog that is submitted back to the pairing server, and
wherein the global unique identifier is masked through the pairing server when the confirmation dialog is served from the pairing server.