# US 10,372,710 B2 · Using metadata to take action on an SMS message on a proprietary system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,372,710 B2 - Document ID: US10372710B2 - Status: Granted - Kind: B2 - Application number: 15/682,360 - Filed: 2017-08-21 - Published: 2018-02-01 - Granted: 2019-08-06 - Earliest claimed: 2016-02-22 - Assignees: Fitbit, Inc. - Applicants: Fitbit, Inc. - Inventors: Brian Jett; Henry Levak; Robert Earl Yawn - Web page: https://patentgrep.com/patent/US10372710B2 ## CPC - G06F 16/2455: Query execution - G06F 1/163: {Wearable computers, e.g. on a belt} - H04M 3/42025: {Calling or Called party identification service} - H04M 3/42042: {Notifying the called party of information on the calling party (details within substation equipment H04M1/57, signalling details H04Q3/72)} - H04M 3/42382: {Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks} - H04W 4/14: Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD] - H04W 4/16: Communication-related supplementary services, e.g. call-transfer or call-hold - H04M 2203/354: Reverse directory service - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Apparatuses, systems, and processes are discussed for using metadata to take action on an SMS message on a proprietary system. In some embodiments, a wearable electronic device has a wearable device application that can present an SMS notification from an SMS application of a mobile computing device. The wearable device application can provide SMS notification data to a partner application of the mobile computing device. The partner application can perform a reverse look-up in a contacts application of the mobile computing device and construct a first contacts list with potential SMS-message senders. The wearable device application can present one or more SMS-message actions to a user of the wearable electronic device for a user selection thereof. The partner application can communicate with a partner server, which, in turn, can communicate with an SMS provider to effect the user selection of the one or more SMS-message actions. ## Claims ### Claim 1 An apparatus, comprising: a wearable electronic device configured to cooperate with one or more processors to execute instructions to present a short message service (“SMS”) notification of an SMS message on a display screen of the wearable electronic device, a first memory configured to cooperate with a security algorithm to store an access token for access to an SMS account of a user as an encrypted access token in the first memory and to store user-provided authentication information for the SMS account as encrypted data in the first memory, a first routine configured to periodically refresh the access token for access to the user's SMS account from an SMS provider by periodically supplying the user-provided authentication information in an encrypted form to one or more SMS-message servers, and a first application configured to analyze the SMS notification, rather than the SMS message itself, and derive a set of notification data from the SMS notification to be sent with the access token for access to the user's SMS account on one or more SMS-message servers to obtain an instance of the SMS message itself from that SMS-message server. ### Claim 2 (depends on 1) The apparatus of claim 1, wherein the first application is configured to cooperate with a partner application resident in a second memory of a mobile computing device, and in response to a reply being generated to the SMS message through the wearable electronic device, where the first application is configured to present an ordered list of SMS-message recipients that should receive the reply to the SMS message, where the ordered list of SMS-message recipients is displayed to be selectable by the user, where the ordered list of additional SMS-message recipients is derived, at least in part, from the analysis of the notification of the SMS message as well as a database of preferred contacts. ### Claim 3 (depends on 2) The apparatus of claim 2, where the first application is configured to send the derived set of notification data from the SMS notification to the partner application, wherein the partner application is configured to perform a reverse look-up using the notification data in a contacts application resident in the second memory of the mobile computing device, and where the partner application is configured to construct the ordered list of SMS-message recipients, based on the reverse look up, consisting of one or more SMS-message recipients in addition to a sender of the SMS-message that should receive the reply by the user to the SMS message, and where the first application is then configured to present the ordered list on the display of the wearable electronic device for a selection of the SMS-message recipients by the user. ### Claim 4 (depends on 1) The apparatus of claim 1, where the first application is configured to provide on the display of the wearable electronic device one or more standard messages to populate into a reply to the SMS message and then allow editing of a first standard message populated into the reply to the SMS message before sending the reply. ### Claim 5 (depends on 1) The apparatus of claim 1, where a partner server is configured to receive the set of notification data derived from the SMS notification, where the partner server is configured to reference the set of notification data against a database of SMS providers and users serviced by the SMS providers, on the partner server, and where the partner server is configured to determine one or more of the SMS providers to use in order to retrieve the instance of the SMS message itself from a server of that SMS provider. ### Claim 6 (depends on 5) The apparatus of claim 5, where the partner server is configured to reference a database of application programming interfaces (APIs) and their API format and schema for the SMS providers, and then communicate in a first schema and format required by an API of a first SMS provider to retrieve the instance of the SMS message itself from that SMS-message server using the access token and the set of notification data. ### Claim 7 (depends on 1) The apparatus of claim 1, where the wearable electronic device is one of a fitness tracker device, a smart watch, or a combination of a fitness tracker and smart watch, wherein the mobile computing device is a smart phone, and the access token includes a password and user account name. ### Claim 8 (depends on 1) The apparatus of claim 1, where the first application is configured to be resident in the wearable electronic device and is configured to communicate bi-directionally directly with a first SMS server. ### Claim 9 (depends on 1) The apparatus of claim 1, where the first application is configured to present one or more SMS-message actions on the display of the wearable electronic device that are selectable by the user to request one or more of these SMS-message actions for the SMS message, wherein the first application is then configured to communicate with a partner server, which is configured to communicate with an API of an SMS provider in order to effect the selected SMS-message actions regarding the SMS message. ### Claim 10 (depends on 1) The apparatus of claim 1, where the first application is configured to cooperate with a partner application resident in a second memory of a mobile computing device, wherein the first application is configured to send information in a package to the partner application at least including i) an action to take for the SMS-message, ii) a name of a sender of the SMS-message, and iii) any additional user-selected content or user-created content in reply to the SMS message itself. ### Claim 11 A method for a wearable electronic device, comprising: configuring the wearable electronic device to cooperate with one or more processors to execute instructions to present a short message service (“SMS”) notification of an SMS message on a display screen of the wearable electronic device, configuring a first memory to cooperate with a security algorithm to store an access token for access to an SMS account of a user as an encrypted access token in the first memory and to store user-provided authentication information for the SMS account as encrypted data in the first memory, configuring a first routine to periodically refresh the access token for access to the user's SMS account from an SMS provider by periodically supplying the user-provided authentication information in an encrypted form to one or more SMS-message servers, and configuring a first application to analyze the SMS notification, rather than the SMS message itself, and derive a set of notification data from the SMS notification to be sent with the access token for access to the user's SMS account on one or more SMS-message servers to obtain an instance of the SMS message itself from that SMS-message server. ### Claim 12 (depends on 11) The apparatus of claim 11, further comprising: configuring the first application to cooperate with a partner application resident in a second memory of a mobile computing device, and in response to a reply being generated to the SMS message through the wearable electronic device, and configuring the first application to present an ordered list of SMS-message recipients that should receive the reply to the SMS message, where the ordered list of SMS-message recipients is displayed to be selectable by the user, where the ordered list of additional SMS-message recipients is derived, at least in part, from the analysis of the notification of the SMS message as well as a database of preferred contacts. ### Claim 13 (depends on 12) The method of claim 12, further comprising: configuring the first application to send the derived set of notification data from the SMS notification to the partner application, wherein the partner application is configured to perform a reverse look-up using the notification data in a contacts application resident in the second memory of the mobile computing device, and where the partner application is configured to construct the ordered list of SMS-message recipients, based on the reverse look up, consisting of one or more SMS-message recipients in addition to a sender of the SMS-message that should receive the reply by the user to the SMS message, and configuring the first application to then present the ordered list on the display of the wearable electronic device for a selection of the SMS-message recipients by the user. ### Claim 14 (depends on 11) The method of claim 11, further comprising: configuring the first application to provide on the display of the wearable electronic device one or more standard messages to populate into a reply to the SMS message and then allowing editing of a first standard message populated into the reply to the SMS message before sending the reply. ### Claim 15 (depends on 11) The method of claim 11, further comprising: configuring the first application to send the set of notification data derived from the SMS notification to a partner server, where the partner server is configured to reference the set of notification data against a database of SMS providers and users serviced by the SMS providers, on the partner server, and where the partner server is configured to determine one or more of the SMS providers to use in order to retrieve the instance of the SMS message itself from a server of that SMS provider. ### Claim 16 (depends on 15) The method of claim 15, where the partner server is configured to reference a database of APIs and their API format and schema for the SMS providers, and then communicate in a first schema and format required by an API of a first SMS provider to retrieve the instance of the SMS message itself from that SMS-message server using the access token and the set of notification data. ### Claim 17 (depends on 11) The method of claim 11, where the wearable electronic device is one of a fitness tracker device, a smart watch, or a combination of a fitness tracker and smart watch, wherein the mobile computing device is a smart phone, and the access token includes a password and user account name. ### Claim 18 (depends on 11) The method of claim 11, further comprising: configuring the first application to be resident in the wearable electronic device and to communicate bi-directionally directly with a first SMS server. ### Claim 19 (depends on 11) The method of claim 11, further comprising: configuring the first application to present one or more SMS-message actions on the display of the wearable electronic device that are selectable by the user to request one or more of these SMS-message actions for the SMS message, wherein the first application is then configured to communicate with a partner server, which is configured to communicate with an API of an SMS provider in order to effect the selected SMS-message actions regarding the SMS message. ### Claim 20 (depends on 11) The method of claim 11, further comprising: configuring the first application to cooperate with a partner application resident in a second memory of a mobile computing device, wherein the first application is configured to send information in a package to the partner application at least including i) an action to take for the SMS-message, ii) a name of a sender of the SMS-message, and iii) any additional user-selected content or user-created content in reply to the SMS message itself.