US2024021200A1PendingUtilityA1
Systems and methods for addressing possible interruption during interaction with digital assistant
Est. expiryMar 2, 2040(~13.6 yrs left)· nominal 20-yr term from priority
G10L 15/222G10L 2015/223G06Q 10/063116G06Q 10/1093G06F 9/453G06F 3/167
73
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Systems and methods are described for handling interruptions during a digital assistant session between a user and a digital assistant by detecting if an interruption event is to occur during the digital assistant session. In response to detecting that the interruption event is to occur, an operation that addresses the interruption event may be caused to be performed.
Claims
exact text as granted — not AI-modified1 - 32 . (canceled)
33 . A method comprising:
detecting an initiation of a digital assistant session related to a topic; computing a predicted length of time of the digital assistant session based on a history of other digital assistant sessions relating to the topic; determining that a notification of a particular type is scheduled to occur during the predicted length of time of the digital assistant session; and in response to determining that a user profile indicates that prior notifications of the particular type were typically snoozed:
automatically causing the notification to be delayed until after the digital assistant session is complete.
34 . The method of claim 33 , wherein the digital assistant session is a voice session between a user associated with the user profile and the digital assistant.
35 . The method of claim 33 , wherein the history of other digital assistant sessions relating to the topic comprises a history of previous digital assistant sessions involving a user associated with the user profile and the digital assistant relating to the topic, and a history of previous digital assistant sessions involving other users and other digital assistants relating to the topic.
36 . The method of claim 33 , wherein the detecting the initiation of the digital assistant session related to the topic comprises:
receiving a voice command from a user; and in response to receiving the voice command from the user, processing the voice command using natural language processing to determine the topic.
37 . The method of claim 33 , further comprising:
in response to the determining that the notification of the particular type is scheduled to occur during the predicted length of time of the digital assistant session: generating for output details relating to the occurrence of the notification, wherein the details include at least one of a subject matter of the notification and a time that the occurrence of the notification is scheduled to be presented.
38 . The method of claim 33 , wherein the notification type includes one of:
a notification relating to a user's calendar, a notification relating to a user's email account, or a notification relating to a user's smart device.
39 . The method of claim 33 , wherein the determining that the user profile indicates that prior notifications of the particular type were typically snoozed comprises:
receiving user information related to a user associated with the user profile responding to notifications of the particular type that occurred during the other digital assistant sessions with the digital assistant.
40 . The method of claim 33 , wherein the determining that the notification of the particular type is scheduled to occur during the predicted length of time of the digital assistant session is based on scheduling data associated with a user associated with the user profile.
41 . The method of claim 33 , further comprising:
in response to determining that the user profile indicates that prior notifications of the particular type were not typically snoozed, providing a prompt comprising selectable options to delay the digital assistant session until after the occurrence of the notification is complete or to delay or cancel the occurrence of the notification.
42 . The method of claim 33 , wherein the automatically causing the notification to be delayed is performed without generating for an output a notification to a user associated with the user profile.
43 . A system comprising:
a I/O circuitry configured to receive a user interface input; and a control circuitry configured to:
detect an initiation of a digital assistant session related to a topic based on the receiving of the user interface input;
compute a predicted length of time of the digital assistant session based on a history of other digital assistant sessions relating to the topic;
determine that a notification of a particular type is scheduled to occur during the predicted length of time of the digital assistant session; and
in response to determining that a user profile indicates that prior notifications of the particular type were typically snoozed:
automatically cause the notification to be delayed until after the digital assistant session is complete;
wherein, the I/O circuitry is configured to output the notification after the delay.
44 . The system of claim 43 , wherein the digital assistant session is a voice session between a user associated with the user profile and the digital assistant.
45 . The system of claim 43 , wherein the history of other digital assistant sessions relating to the topic comprises a history of previous digital assistant sessions involving a user associated with the user profile and the digital assistant relating to the topic, and a history of previous digital assistant sessions involving other users and other digital assistants relating to the topic.
46 . The system of claim 43 ,
wherein, the I/O circuitry is configured to receive the user interface input by receiving a voice command from a user; wherein the control circuitry is configured to detect the initiation of the digital assistant session related to the topic by:
in response to receiving the voice command from the user, processing the voice command using natural language processing to determine the topic.
47 . The system of claim 43 , wherein the control circuitry is further configured to:
in response to determining that the notification of the particular type is scheduled to occur during the predicted length of time of the digital assistant session: generate for output details relating to the occurrence of the notification, wherein the details include at least one of a subject matter of the notification and a time that the occurrence of the notification is scheduled to be presented.
48 . The system of claim 43 , wherein the notification type includes one of:
a notification relating to a user's calendar, a notification relating to a user's email account, or a notification relating to a user's smart device.
49 . The system of claim 43 , wherein the control circuitry is configured to determine that the user profile indicates that prior notifications of the particular type were typically snoozed by:
receiving user information related to a user associated with the user profile responding to notifications of the particular type that occurred during previous digital assistant sessions with the digital assistant.
50 . The system of claim 43 , wherein the control circuitry is configured to determine that the notification of the particular type is scheduled to occur during the predicted length of time of the digital assistant session based on scheduling data associated with a user associated with the user profile.
51 . The system of claim 43 , wherein the control circuitry is further configured to:
in response to determining that the user profile indicates that prior notifications of the particular type were not typically snoozed, provide a prompt comprising selectable options to delay the digital assistant session until after the occurrence of the notification is complete or to delay or cancel the occurrence of the notification.
52 . The system of claim 43 , wherein the I/O circuitry is configured to automatically cause the notification to be delayed without generating for an output a notification to a user associated with the user profile.Join the waitlist — get patent alerts
Track US2024021200A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.