# US 10,455,059 B2 · Sending messages to mobile devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,059 B2 - Document ID: US10455059B2 - Status: Granted - Kind: B2 - Application number: 16/158,834 - Filed: 2018-10-12 - Published: 2019-02-14 - Granted: 2019-10-22 - Earliest claimed: 2016-04-11 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Guanqun Bao; Okeno R. Palmer; Saumitra Kumar; Harsha Vardhana Reddy Hardhagari; Gaurav Gupta - Web page: https://patentgrep.com/patent/US10455059B2 ## CPC - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 51/224: providing notification on incoming messages, e.g. pushed notifications of received messages - H04L 67/125: involving control of end-device applications over a network - H04L 67/53: using third party service providers - H04L 67/55: Push-based network services - H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] - H04W 4/50: Service provisioning or reconfiguring - H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A device may receive a request for a mobile device to obtain an application. The request may include a mobile device identifier for the mobile device. The device may send, to the mobile device, a link to a web page. The device may receive, from the mobile device, a request for the web page. The device may send, to the mobile device, a redirect to a software distribution platform to obtain the application from the software distribution platform. The device may receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform. The device may send, to a message server, a request for a message to be sent to the mobile device. The request may be based on the registration identifier and the application. ## Claims ### Claim 1 A device, comprising: one or more memories; and one or more processors, communicatively coupled to the one or more memories, to: receive, from a mobile device, a first request for the mobile device to obtain an application, the first request including a mobile device identifier for the mobile device; send, to the mobile device and based on the first request, a link to a web page; receive, from the mobile device, a second request for the web page; send, to the mobile device and based on the second request, a redirect to a software distribution platform to obtain the application from the software distribution platform, the redirect causing the mobile device to obtain the application from the software distribution platform; receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform, the registration identifier being received by the mobile device from a message server; map the mobile device identifier from a session cookie to the registration identifier, the mobile device identifier including one of: a mobile device number (MDN), an international mobile subscriber identity (IMSI), or a temporary mobile subscriber identity (TMSI); store information associated with the mapping of the mobile device identifier to the registration identifier and at least one of: an application identifier, information associated with an operating system of the mobile device, or information associated with a registration time; send, to the message server, a third request for a message to be sent to the mobile device, the third request being based on the registration identifier and the application; and receive, from a third party device and before sending the third request, a fourth request to send the message to the mobile device, the fourth request being based on the mobile device identifier, and the third request being based on the fourth request. ### Claim 2 (depends on 1) The device of claim 1, where launching of the application causes the mobile device to send a registration request to the message server. ### Claim 3 (depends on 1) The device of claim 1, where the one or more processors, when receiving the first request for the mobile device to obtain the application, are further to: receive the first request for the mobile device to obtain the application via user input associated with a web site. ### Claim 4 (depends on 1) The device of claim 1, where the one or more processors, when sending, to the mobile device, the link to the web page, are to: send, to the mobile device, a short message service (SMS) message, the SMS message including a uniform resource locator (URL) for the web page. ### Claim 5 (depends on 1) The device of claim 1, where the one or more processors are further to: determine the operating system of the mobile device before sending, to the mobile device, the redirect to the software distribution platform; and where the redirect to the software distribution platform is based on the operating system. ### Claim 6 (depends on 1) The device of claim 1, where the one or more processors, when receiving the registration identifier for the mobile device, are to: receive the registration identifier from the mobile device. ### Claim 7 (depends on 1) The device of claim 1, where the one or more processors, when sending the redirect to the software distribution platform, are to: send the redirect to the software distribution platform along with the session cookie. ### Claim 8 A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors, cause the one or more processors to: receive, from a mobile device, a first request for the mobile device to obtain an application, the first request including a mobile device identifier for the mobile device; send, to the mobile device, a link to a web page, the web page being based on the mobile device identifier; receive, from the mobile device, a second request for the web page; send, to the mobile device and based on the second request, a redirect to a software distribution platform, the redirect causing the mobile device to obtain the application from the software distribution platform; receive a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform, the registration identifier being received by the mobile device from a message server; map the mobile device identifier from a session cookie to the registration identifier, the mobile device identifier including one of: a mobile device number (MDN), an international mobile subscriber identity (IMSI), or a temporary mobile subscriber identity (TMSI); store information associated with the mapping of the mobile device identifier to the registration identifier and at least one of: an application identifier, information associated with an operating system of the mobile device, or information associated with a registration time; send, to the message server, a third request for a message to be sent, to the mobile device, based on the registration identifier, the message being based on the application; and receive, from a third party device and before sending the third request, a fourth request to send the message to the mobile device, the fourth request being based on the mobile device identifier, and the third request being based on the fourth request. ### Claim 9 (depends on 8) The non-transitory computer-readable medium of claim 8, where the first request from the mobile device to obtain the application includes an application identifier. ### Claim 10 (depends on 8) The non-transitory computer-readable medium of claim 8, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to: generate a unique uniform resource locator (URL) for each pairing of a mobile device identifier and an application identifier. ### Claim 11 (depends on 8) The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to send, to the mobile device, the link to the web page, cause the one or more processors to: send, to the mobile device, a short message service (SMS) message, the SMS message including a uniform resource locator (URL) for the web page. ### Claim 12 (depends on 11) The non-transitory computer-readable medium of claim 11, where the second request for the web page is initiated based on the URL for the web page in the SMS message. ### Claim 13 (depends on 8) The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive the registration identifier for the mobile device, cause the one or more processors to: receive the registration identifier from the mobile device. ### Claim 14 (depends on 8) The non-transitory computer-readable medium of claim 8, where the message includes a uniform resource identifier (URI) for at least one of: a specific location within the application, or a specific content within the application. ### Claim 15 A method, comprising: receiving, by a device and from a mobile device, a first request for the mobile device to obtain an application, the first request including a mobile device identifier for the mobile device, and the first request being received from a third party device; sending, by the device, to the mobile device, and based on the first request, a link to a web page; receiving, by the device and from the mobile device, a second request for the web page; sending, by the device and to the mobile device, a redirect based on the second request, the redirect causing the mobile device to obtain the application from a software distribution platform; receiving, by the device, a registration identifier for the mobile device after the mobile device obtains the application from the software distribution platform, the registration identifier being received by the mobile device from a message server; mapping, by the device, the mobile device identifier from a session cookie to the registration identifier, the mobile device identifier including one of: a mobile device number (MDN), an international mobile subscriber identity (IMSI), or a temporary mobile subscriber identity (TMSI); storing, by the device, store information associated with the mapping of the mobile device identifier to the registration identifier and at least one of: an application identifier, information associated with an operating system of the mobile device, or information associated with a registration time; sending, by the device and to the message server, a third request based on the registration identifier, the third request causing the message server to send a message to the mobile device, the message being based on the application; and receiving, by the device, from a third party device, and before sending the third request, a fourth request to send the message to the mobile device, the fourth request being based on the mobile device identifier, and the third request being based on the fourth request. ### Claim 16 (depends on 15) The method of claim 15, further comprising: generating the session cookie for the mobile device based on the mobile device identifier, the session cookie to store the mobile device identifier. ### Claim 17 (depends on 16) The method of claim 16, where the mapping is between the mobile device identifier, the application identifier, the operating system of the mobile device, and the session cookie. ### Claim 18 (depends on 15) The method of claim 15, where sending, to the mobile device, the link to the web page comprises: sending, to the mobile device, a short message service (SMS) message, the SMS message including a uniform resource locator (URL) for the web page; and where the web page is based on at least one of the mobile device identifier or the application. ### Claim 19 (depends on 15) The method of claim 15, further comprising: determining the operating system of the mobile device before sending the redirect based on the second request; and selecting the software distribution platform based on the operating system for the mobile device. ### Claim 20 (depends on 15) The method of claim 15, where the message includes a uniform resource identifier (URI) for at least one of: a specific location within the application, or a specific content within the application.