# US 11,444,898 B2 · Student-controlled text message reminders with third party systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,444,898 B2 - Document ID: US11444898B2 - Status: Granted - Kind: B2 - Application number: 17/411,325 - Filed: 2021-08-25 - Published: 2022-01-27 - Granted: 2022-09-13 - Earliest claimed: 2020-04-12 - Assignees: Lazy Texts, LLC - Applicants: Lazy Texts, LLC. - Inventors: Charles Levine - Web page: https://patentgrep.com/patent/US11444898B2 ## CPC - H04L 51/212: using filtering or selective blocking - H04L 51/046: Interoperability with other network applications or services - H04L 51/214: using selective forwarding - H04L 51/56: Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A computing device and computer-implemented method to provide user-control short message service (SMS). The method begins with accessing, by a server, data in a third-party format from a third-party server. The server and the third-party server are controlled by different business entities. Next, the data in the third-party format is filtered, which has been accessed according to user preferences, the user preferences including a mobile device identifier. Next, the data in the third-party format is converted which as specified by the user preferences into a format compatible with the SMS protocol or an instant message for receipt by a messaging app. Finally, the data is sent in which has been converted into the SMS format or instant message to the mobile device as specified by the mobile device identifier. ## Claims ### Claim 1 A method for providing user-control message service comprising: converting by a server, one or more user preferences into each third-party API's specific filter for one of a plurality of third-party servers, where the server and the third-party servers are each controlled by different business entities; accessing, by the server, data using the third-party API's specific filter in a plurality of third-party formats from the plurality of third-party servers, wherein the data in the plurality of third-party formats from the plurality of third-party servers, further includes accessing reminders from a syllabus using an API or optical character recognition; filtering the data in the plurality of third-party formats from the plurality of third-party servers which has been accessed according to user preferences, the user preferences including a mobile device identifier; converting the data which has been accessed and filtered using the third-party API's specific filter in the plurality of third-party formats from the plurality of third-party servers into a single structure format; converting the single structure format into at least one message service format compatible with one of a plurality of message services specified by the one or more user preferences; and sending the data which has been converted into the message service format to a mobile device as specified by the mobile device identifier. ### Claim 2 (depends on 1) The method of claim 1, wherein the converting the single structure format into at least one message service format compatible with the one or a plurality of message services is one of an SMS protocol or an instant message for receipt by a messaging app. ### Claim 3 (depends on 2) The method of claim 2, wherein the sending the data which has been converted into the SMS protocol or instant message to the mobile device as specified by the mobile device identifier. ### Claim 4 (depends on 3) The method of claim 3, further comprising: sending the data which has been converted into the SMS protocol to an SMS gateway or using a CPaaS API to send to the mobile device as specified by the mobile device identifier. ### Claim 5 (depends on 1) The method of claim 1, wherein the accessing is performed using one or more of API calls, web scraping, file transfer protocol (FTP), and http methods. ### Claim 6 (depends on 1) The method of claim 1, wherein the user preferences for filtering includes one or more of show courses, skip courses, set days, maximum assignments, maximum days, skipped classes, skip completed and skip completed to-dos. ### Claim 7 (depends on 1) The method of claim 1, wherein the user preferences for filtering includes one or more of planner is empty, time and time zone, active status, texts paused, and skipped days of week. ### Claim 8 (depends on 1) The method of claim 1, wherein the user preferences for formatting includes one or more of class, customized course names, birthday, time format, time-zone, name, and limit reminder amount. ### Claim 9 (depends on 1) The method of claim 1, wherein the data in the plurality of third-party formats from the plurality of third-party servers includes a learning management system, email system and other data sources. ### Claim 10 (depends on 1) The method of claim 1, further comprising: accessing, by the server, data in an additional third-party format from an additional third-party server, wherein the server and the additional third-party server are controlled by different business entities; filtering the data in the additional third-party format which has been accessed according to user preferences, the user preferences including a mobile device identifier; converting the data in the additional third-party format into the message service format compatible with the one or a plurality of message services, wherein the message service format is specified by the user preferences; and sending the data which has been converted into the message service format. ### Claim 11 A method for providing user-control message service for a plurality of data sources comprising: for each data source in a plurality of data sources, performing converting by a server, one or more user preferences into each third-party API's specific filter for one of a plurality of third-party servers, where the server and the third-party servers are each controlled by different business entities; accessing, by the server, data using the third-party API's specific filter in a plurality of third-party formats from the plurality of third-party servers, wherein the data in the plurality of third-party formats from the plurality of third-party servers, further includes accessing due dates using an API or optical character recognition; filtering the data in the plurality of third-party formats from the plurality of third-party servers which has been accessed according to user preferences, the user preferences including a mobile device identifier; converting the data which has been accessed and filtered using the third-party API's specific filter in the plurality of third-party formats from the plurality of third-party servers into a single structure format; converting the single structure format into at least one message service format compatible with one of a plurality of message services specified by the one or more user preferences; and sending the data which has been converted into the message service format to a mobile device as specified by the mobile device identifier. ### Claim 12 (depends on 11) The method of claim 11, wherein the converting the data from each data source in the plurality of data sources, in the plurality of third-party formats from the plurality of third-party servers into a homogeneous format compatible with the message service format includes converting into the homogeneous format with a number of total reminders merged into a single message as specified by the user preferences. ### Claim 13 (depends on 11) The method of claim 11, wherein the due dates are from a syllabus. ### Claim 14 (depends on 11) The method of claim 11, wherein the due dates are reminders from a syllabus. ### Claim 15 (depends on 11) The method of claim 11, wherein the due dates are one or more of an assignment, a quiz, and an exam. ### Claim 16 (depends on 11) The method of claim 11, wherein the due dates are one or more of a discussion topic, an announcement, and a calendar event. ### Claim 17 (depends on 11) The method of claim 11, wherein the due dates are from a planner. ### Claim 18 A device for providing user-control message service, comprising: a processor device; and a memory operably coupled to the processor device and storing computer-executable instructions causing: converting by a server, one or more user preferences into each third-party API's specific filter for one of a plurality of third-party servers, where the server and the third-party servers are each controlled by different business entities; accessing, by the server, data using the third-party API's specific filter in a plurality of third-party formats from the plurality of third-party servers, wherein the data in the plurality of third-party formats from the plurality of third-party servers, further includes accessing due dates using an API or optical character recognition; filtering the data in the plurality of third-party formats from the plurality of third-party servers which has been accessed according to user preferences, the user preferences including a mobile device identifier; converting the data which has been accessed and filtered using the third-party API's specific filter in the plurality of third-party formats from the plurality of third-party servers into a single structure format; converting the single structure format into at least one message service format compatible with one of a plurality of message services specified by the one or more user preferences; and sending the data which has been converted into the message service format to a mobile device as specified by the mobile device identifier. ### Claim 19 (depends on 18) The device of claim 18, wherein the converting the single structure format into at least one message service format compatible with the one or a plurality of message services is one of an SMS protocol or an instant message for receipt by a messaging app. ### Claim 20 (depends on 19) The device of claim 19, wherein the sending the data which has been converted into the SMS protocol or instant message to the mobile device as specified by the mobile device identifier. ### Claim 21 (depends on 18) The device of claim 18, further comprising: accessing, by the server, data in an additional third-party format from an additional third-party server, wherein the server and the additional third-party server are controlled by different business entities; filtering the data in the additional third-party format which has been accessed according to user preferences, the user preferences including a mobile device identifier; converting the data in the additional third-party format into the message service format compatible with the one or a plurality of message services, wherein the message service format is specified by the user preferences; and sending the data which has been converted into the message service format.