# US 10,503,533 B2 · App streaming, bidirectional linket, phone number for mobile deep links > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,503,533 B2 - Document ID: US10503533B2 - Status: Granted - Kind: B2 - Application number: 14/998,440 - Filed: 2016-01-04 - Published: 2017-07-06 - Granted: 2019-12-10 - Earliest claimed: 2016-01-04 - Applicants: Wesley John Boudville - Inventors: Wesley John Boudville - Web page: https://patentgrep.com/patent/US10503533B2 ## CPC - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06F 16/95: Retrieval from the web - G06Q 30/0246: {Traffic} - H04W 4/50: Service provisioning or reconfiguring - H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits - G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing} - G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances} - H04L 63/101: {Access control lists [ACL]} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract An app store can have a multiuser streaming app. A thin front end appears on the user devices and the rest of the app instances run in virtual machines in a data center of the app store. A web page at an URL Phi can contain a linket Theta. Phi is seen in a mobile browser. If Theta is picked, the mobile device sends Theta and Phi to the Registry. The Registry logs both. Future analysis of the log tells where (Phi) the linket appeared. A bidirectional capability. The app server for the linket can also get Phi, and use the pair for similar analysis. An ad server which made an ad containing Theta, which appeared in Phi, can analyse the log to measure the efficacy of posting the ad to Theta. Phi can also be an app. ## Claims ### Claim 1 A method comprising: a server running a first instance of an application in a first virtual machine, in streaming mode, in a first data center; displaying, by the first instance, a window of the application on a first mobile device; creating, by the first instance, a deep link, wherein the deep link has an id of the application and a network address of the first mobile device; transmitting, by the first instance, the deep link to a second mobile device; receiving, by the server, the network address of the first mobile device from the second mobile device; running, by the server, a second instance of the application in a second virtual machine, in streaming mode; displaying, by the second instance, a window of the application on the second mobile device; and the first and the second instances interacting. ### Claim 2 (depends on 1) The method of claim 1, further comprising: transmitting the deep link, wherein the transmitting is performed by the first instance creating a barcode of the deep link; displaying, by the first instance, the barcode in the window of the application on the first mobile device. ### Claim 3 (depends on 1) The method of claim 1, further comprising: receiving, by the server, a message from the second instance; extracting, by the server, a destination network address, wherein the destination network address is the network address of the first mobile device; routing, by the server, the message in a path inside the first data center to the first instance. ### Claim 4 (depends on 1) The method of claim 1, further comprising: deploying the server across a plurality of tertiary data centers, wherein the tertiary data centers are different from the first data center; receiving, by the server, the network address from the second mobile device; for each tertiary data center, estimating, by the server, a sum of a first transmission time between the first mobile device and the tertiary data center, and a second transmission time between the tertiary data center and the second mobile device; identifying, by the server, from the plurality of tertiary data centers, a second data center with a minimum sum; migrating, by the server, the first instance from the first data center to the second data center; creating, by the server, the second instance in the second data center. ### Claim 5 (depends on 4) The method of claim 4, further comprising notifying, by the server, the first mobile device of a network address of the second data center where the first instance runs. ### Claim 6 (depends on 4) The method of claim 4, further comprising notifying, by the first instance running on the second data center, the first mobile device of the network address of the second data center. ### Claim 7 (depends on 1) The method of claim 1 further comprising: deploying, by the server, virtual machines in a plurality of tertiary data centers; receiving, by the server, the network address of the first mobile device from the second mobile device; for each tertiary data center and for the first data center, estimating, by the server, a sum of: a first transmission time between the first mobile device and a tertiary data center, twice of a second transmission time between the tertiary data center and the first data center, and a third transmission time between the tertiary data center and the second mobile device; identifying, by the server, a second data center with a minimum sum; migrating, by the server, the first instance and the second instance from the first data center to the second data center. ### Claim 8 (depends on 7) The method of claim 7, further comprising notifying, by the server, the first mobile device of a network address of the second data center where the first instance runs. ### Claim 9 (depends on 7) The method of claim 7, further comprising notifying, by the first instance running on the second data center, the first mobile device of the network address of the second data center. ### Claim 10 (depends on 4) The method of claim 4, further comprising: three or more mobile devices; for each tertiary data center, estimating, by the server, a sum of a transmission time between each mobile device and the tertiary data center; identifying, by the server, a given tertiary data center with a minimum sum; installing, by the server, the virtual machines, corresponding to each mobile device, in the given tertiary data center.