# US 2025/0377906 A1 · Systems and methods for ai assistant integration on mobile

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

- Number: US 2025/0377906 A1
- Document ID: US20250377906A1
- Status: Published application
- Kind: A1
- Application number: 18/740,220
- Filed: 2024-06-11
- Published: 2025-12-11
- Earliest claimed: 2024-06-11
- Assignees: Salesforce, Inc.
- Applicants: Salesforce, Inc.
- Inventors: Stephen GOLDBERG; Andrew MANGANO; Jean Elie BOVET; Abigail SIGLER; Eric ROMERO; Stephen COYNER; Kristen MURAMOTO; Saket AGARWAL; Swati CHILAKALA; Scotland PETERS; Tanya SAARVA; Chuxiong WU
- Web page: https://patentgrep.com/patent/US20250377906A1

## CPC

- G06F 9/451: Execution arrangements for user interfaces
- G06F 21/31: User authentication
- G06F 21/32: using biometric data, e.g. fingerprints, iris scans or voiceprints
- H04L 51/02: using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed herein are mobile device, method, and computer program product embodiments for an improved integrated mobile AI assistant. The mobile device may launch a mobile application including an integration component, where the integration component is in communication, through the mobile application, with a data service and a user interface (UI) service. The integration component may receive a response including data and a data type from the data service generated by a large language model responsive to a natural language query. The integration component may customize an interface at the integration component using a rendering configuration received from the UI service to display the data, the rendering configuration generated by decomposing the data type into a predefined type.

## Claims

### Claim 1

A mobile device, comprising:
a memory; and
at least one processor coupled to the memory and configured to:
launch, at a mobile device, a mobile application including an integration component, wherein the integration component is in communication, through the mobile application, with a data service and a user interface (UI) service;
receive, at the integration component, a response including data and a data type from the data service generated by a large language model responsive to a natural language query; and
customize, by the integration component, an interface at the integration component using a rendering configuration received from the UI service to display the data, the rendering configuration generated by decomposing the data type into a predefined type.

### Claim 2 (depends on 1)

The mobile device of claim 1, wherein the at least one processor is further configured to:
receive, at the integration component, an interaction with the data at the customized interface;
receive, at the integration component, a recommended second mobile application based on the interaction, the data, and the data type, wherein the recommendation was generated by the large language model; and
launch, by the integration component, a second mobile application in response to an interaction with the recommendation, wherein the integration component is configured to communicate data with the second mobile application.

### Claim 3 (depends on 1)

The mobile device of claim 1, wherein the second mobile application is at least one of an email application, instant messaging application, an image capturing application, a video capturing application, an audio capturing application, a web browsing application, or a navigation application.

### Claim 4 (depends on 1)

The mobile device of claim 1, wherein the customized interface includes a chatbot interface and wherein the at least one processor is further configured to:
send a natural language request to update the received data, where the natural language request was input to the chatbot interface;
receive, at the integration component, a response including updated data and a data type from the data service generated by a large language model responsive to the natural language request; and
update, by the integration component, the interface at the integration component using the rendering configuration from the UI service to display the updated data.

### Claim 5 (depends on 1)

The mobile device of claim 1, wherein the at least one processor is further configured to:
authenticate a user associated with the mobile application via an authentication mechanism executed by the integration component.

### Claim 6 (depends on 5)

The mobile device of claim 5, wherein the authentication mechanism is configured to use a username, password, fingerprint, facial recognition, voiceprint, security question, or a reverse Turing test.

### Claim 7 (depends on 1)

The mobile device of claim 1, wherein the integration component is configured to input sensor data collected by the mobile device, the sensor data including GPS data, image data, video data, audio data, accelerometer data, gyroscope data, barometer data, proximity data, ambient light data, magnetometer data, and LIDAR data.

### Claim 8

A method, comprising:
launching, at a mobile device, a mobile application including an integrated integration component, wherein the integration component is in communication, through the mobile application, with a data service and a user interface (UI) service;
receiving, at the integration component, a response including data and a data type from the data service generated by a large language model responsive to a natural language query; and
customizing, by the integration component, an interface at the integration component using a rendering configuration received from the UI service to display the data, the rendering configuration generated by decomposing the data type into a predefined type.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
receiving, at the integration component, an interaction with the data at the customized interface;
receiving, at the integration component, a recommended second mobile application based on the interaction, the data, and the data type, wherein the recommendation was generated by the large language model; and
launching, by the integration component, a second mobile application in response to an interaction with the recommendation, wherein the integration component is configured to communicate data with the second mobile application.

### Claim 10 (depends on 9)

The method of claim 9, wherein the second mobile application is at least one of an email application, instant messaging application, an image capturing application, a video capturing application, an audio capturing application, a web browsing application, or a navigation application.

### Claim 11 (depends on 8)

The method of claim 8, wherein the customized interface includes a chatbot interface and wherein method further comprises:
send a natural language request to update the received data, where the natural language request was input to the chatbot interface;
receive, at the integration component, a response including updated data and a data type from the data service generated by a large language model responsive to the natural language request; and
updating, by the integration component, the interface at the integration component using the rendering configuration from the UI service to display the updated data.

### Claim 12 (depends on 8)

The method of claim 8, further comprising:
authenticating a user associated with the mobile application via an authentication mechanism executed by the integration component.

### Claim 13 (depends on 12)

The method of claim 12, wherein the authentication mechanism is configured to use a username, password, fingerprint, facial recognition, voiceprint, security question, or a reverse Turing test.

### Claim 14 (depends on 8)

The method of claim 8, wherein the integration component is configured to input sensor data collected by the mobile device, the sensor data including GPS data, image data, video data, audio data, accelerometer data, gyroscope data, barometer data, proximity data, ambient light data, magnetometer data, and LIDAR data.

### Claim 15

A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:
launching, at a mobile device, a mobile application including an integrated integration component, wherein the integration component is in communication, through the mobile application, with a data service and a user interface (UI) service;
receiving, at the integration component, a response including data and a data type from the data service generated by a large language model responsive to a natural language query; and
customizing, by the integration component, an interface at the integration component using a rendering configuration received from the UI service to display the data, the rendering configuration generated by decomposing the data type into a predefined type.

### Claim 16 (depends on 15)

The non-transitory computer-readable device of claim 15, wherein the operations further comprise:
receiving, at the integration component, an interaction with the data at the customized interface;
receive, at the integration component, a recommended second mobile application based on the interaction, the data, and the data type, wherein the recommendation was generated by the large language model; and
launching, by the integration component, a second mobile application in response to an interaction with the recommendation,
wherein the integration component is configured to communicate data with the second mobile application; and
wherein the second mobile application is at least one of an email application, instant messaging application, an image capturing application, a video capturing application, an audio capturing application, a web browsing application, or a navigation application.

### Claim 17 (depends on 15)

The non-transitory computer-readable device of claim 15, wherein the customized interface includes a chatbot interface and the operations further comprise:
sending a natural language request to update the received data, where the natural language request was input to the chatbot interface;
receiving, at the integration component, a response including updated data and a data type from the data service generated by a large language model responsive to the natural language request; and
updating, by the integration component, the interface at the integration component using the rendering configuration from the UI service to display the updated data.

### Claim 18 (depends on 15)

The non-transitory computer-readable device of claim 15, wherein the operations further comprise:
authenticating a user associated with the mobile application via an authentication mechanism executed by the integration component.

### Claim 19 (depends on 15)

The non-transitory computer-readable device of claim 15, wherein the authentication mechanism is configured to use a username, password, fingerprint, facial recognition, voiceprint, security question, or a reverse Turing test.

### Claim 20 (depends on 15)

The non-transitory computer-readable device of claim 15, wherein the integration component is configured to input sensor data collected by the mobile device, the sensor data including GPS data, image data, video data, audio data, accelerometer data, gyroscope data, barometer data, proximity data, ambient light data, magnetometer data, and LIDAR data.
