System and method for capturing notes on a mobile device

Abstract

A method and system for capturing notes on a mobile device includes displaying a lock screen on an electronic display of the mobile device and operating the mobile device in an active interactive state, the active interactive state providing write-only access to a secure file on the mobile device and providing write-only access to a secure file on the mobile device. The mobile device may present user input on top of the lock screen in a user input area on the mobile device display for a time period, store the user input in the secure file using write-only access, and cease presenting the user input in response to detecting expiration of the time period or in response to detecting user inactivity.

Description

Background Art

[0001] Note-taking has evolved from using writing tools on surfaces like pen and paper to modern computing devices that receive and transmit a variety of data electronically. Smartphones and tablets are powerful mobile computing devices that have enabled many new types of note-taking and communication. These mobile devices can also be used to store short notes and memos, such as mobile phone numbers, book titles, action items (e.g., pick up tomatoes, etc.), etc. Device users often obtain or conceive such information when the mobile device is in a screen-locked state and / or when the mobile device is busy processing other tasks or applications. Summary of the invention

[0002] Various aspects may include a method for capturing notes on a mobile device, performed by a processor of a mobile device. Various aspects may include displaying a lock screen on an electronic display of the mobile device, and operating the mobile device in a write-only interactive state, the write-only interactive state providing write-only access to a secure file on the mobile device, which enables a user to enter limited information stored in the secure file, and presenting the user input at the top of the lock screen in a user input area for a period of time and storing the user input in the secure file using write-only access, and in response to the expiration of the period of time or in response to detecting user inactivity, stopping receiving and presenting the user input. Some aspects may also include storing the contents of the secure file in a note-taking application operating on the mobile device in response to the mobile device authenticating the user and exiting the lock screen state. Some aspects may also include preventing the user from viewing, accessing, deleting, or editing the secure file until the mobile device authenticates the user.

[0003] Some aspects may also include monitoring a sensor of the mobile device to determine whether the user has picked up the mobile device or otherwise attempted to interact with the mobile device in the lock screen mode, and in response to the mobile device determining that the user has picked up the mobile device or otherwise attempted to interact with the mobile device, displaying the lock screen on the electronic display of the mobile device and operating the mobile device in a write-only interaction state. Some aspects may also include presenting a keypad on the electronic display of the mobile device in response to determining that the user has picked up the mobile device or otherwise attempted to interact with the mobile device. In some aspects, presenting user input in a user input area of ​​the mobile device display on the lock screen during the time period and storing the user input in the secure file using write-only access may include presenting text input made by the user on the presented keypad at the location of the lock screen that the user first touched.

[0004] Some aspects may also include storing user input of limited information received by the mobile device in a write-only interactive state for a predetermined duration (such as 24 hours) in a single secure file. Some aspects may also include storing the contents of multiple single secure files in a note-taking application operating on the mobile device, and autonomously organizing multiple single files locally on the mobile device or remotely via a cloud or communication network.

[0005] Some aspects may also include initiating a user authentication operation (eg, entering a password or biometric information, etc.) in response to determining that the amount of user input satisfies (eg, meets or exceeds) a threshold amount.

[0006] Other aspects may include capturing notes on a mobile device in response to a notification that appears on a screen or display. These aspects may include detecting the presence of a notification on a screen presented on a display of a mobile device, enabling a write-on-notification function of the mobile device, receiving user input associated with the notification, saving the received user input in a file, and providing access to the saved file to the mobile device user. In some aspects, saving the received user input in a file may include: saving the received user input to one or more of: a file associated with the notification or an application associated with the application, a file accessible to an email application when an announcement is a banner indicating the receipt of an email, a file accessible in a calendar application when a calendar application generates the notification, or a note file, clipboard, or other file in response when an announcement is associated with an application or function that does not receive user input. In some aspects, providing access to a saved file associated with the notification to a mobile device user may include: providing access to a saved file to a mobile device user in response to activation of an application associated with the notification, at the activation of a note or word processor application, authentication of a user, unlocking of a mobile device, or presenting a specific screen on a display.

[0007] Aspects may include a mobile device having a memory storing processor-executable instructions and a processor configured to execute the processor-executable instructions to perform the operations of any of the methods described above. Aspects may include a processor for a mobile device having a memory and configured to perform the operations of any of the methods described above. Aspects may include a mobile device having various means for performing the functions of the methods described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The accompanying drawings, which are incorporated herein and constitute a part of this specification, illustrate exemplary aspects of the various embodiments, and together with the general description given above and the detailed description given below, serve to explain features of the claims.

[0009] Figure 1is a block diagram illustrating components of an example mobile device suitable for implementing the various embodiments.

[0010] Figure 2 is a component diagram illustrating various interface screens, operating modes, and operations in a mobile device configured to capture notes in accordance with some embodiments.

[0011] FIG. 3A to FIG. 7D is a process flow diagram illustrating a method of capturing notes according to various embodiments.

[0012] Figure 8A-8E is a process flow diagram illustrating a method of activating or exiting a write-only interaction state to capture notes on a mobile device in accordance with some embodiments.

[0013] Fig. 9A and Fig. 9B is a process flow diagram illustrating a method of authenticating a user when a mobile device is operating in a write-only interaction state in accordance with some embodiments.

[0014] Fig.10 is a process flow diagram illustrating a method of capturing notes on a bulletin presented on a screen in accordance with some embodiments.

[0015] Fig.11 is a block diagram illustrating components of a mobile device suitable for implementing some embodiments. DETAILED DESCRIPTION

[0016] Various embodiments will be described in detail with reference to the accompanying drawings. Wherever possible, the same reference numerals are used throughout the drawings to represent the same or similar parts. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

[0017] Various embodiments include methods for enabling the input of short notes without unlocking or accessing the full functionality of the device and mobile devices implementing such methods, thereby providing a convenient note-taking function without compromising the security of the device or data. For example, in some embodiments, upon power-up or after a period of user inactivity, the mobile device may enter a screen lock state and / or display a lock screen and operate in a write-only interactive state, which provides write-only access to a note save file on the mobile device and / or allows the user to enter limited information stored in the note save file. In some embodiments, the write-only interactive state may activate an instant type function or present a soft key area in response to various user inputs, actions, or conditions on the mobile device. The mobile device may capture and present user input (e.g., input received via a soft key area or other means) in a user input area at the top of the lock screen for a period of time, and store the user input in the note save file using write-only access. The mobile device may stop receiving and presenting user input and / or stop writing to the note save file in response to the expiration of the time period or in response to detecting user inactivity (e.g., no input is detected within a predetermined interval). The mobile device may store the file in a more permanent file that is only accessible when the user is authenticated and the mobile device exits a screen-locked state (or other screen or state as described herein).

[0018] The term "mobile device" is used herein to refer to any of a variety of personal, portable or wireless computing devices, and includes smart phones, tablet computers, laptops, personal or mobile multimedia players, personal data assistants (PDAs), laptops, tablet computers, ultrabooks, PDAs, wireless email receivers, cellular phones supporting multimedia Internet, and similar electronic devices including programmable processors, memories, displays, and user interface functions. Wireless communication devices are also commonly referred to as user equipment (UE), mobile devices, and cellular devices. Mobile devices can receive and / or send communications via various wired and / or wireless communication networks, including wide area networks (e.g., mobile communication networks), local area networks (e.g., Wi-Fi, Bluetooth, etc.), geolocation networks (e.g., global positioning systems ("GPS")), personal area networks (e.g., wireless USB, Bluetooth, ZigBee, etc.), near field communications, etc.

[0019] The mobile device can be operated in a screen locked state or an unlocked state. The screen locked state can manage immediate access to the mobile device by requiring the user to perform specific actions before accessing certain features of the mobile device. After the mobile device transitions from the screen locked state to one of a plurality of unlocked states, the user can access the note taking feature of the mobile device.

[0020] In various operating modes or states, the mobile device can present various different screens of the display, including a blank screen, an application screen, a home screen, a lock screen, and an unlock screen. In various embodiments, the lock screen and the unlock screen can provide substantially the same or similar views, except that the former is in a locked state and the latter is in an unlocked state (e.g., in response to user authentication). In some embodiments, the unlock screen can provide different information or views from the lock screen. For example, an email notification can only show that one or more emails have arrived when in a locked state, but can provide more details (e.g., at least a portion of the email message, the sender, etc.) when in an unlocked state.

[0021] The application screen may include a graphical user interface (GUI) of a software application operating on the device, and typically occupies all or most of the display of the mobile device. The home screen may be the main screen of the mobile device, displaying virtual buttons and icons of different software applications, notifications, settings and / or features linked to the device. The home screen may also include any screen that is not an application full screen, a lock screen or an unlock screen. For example, the home screen may include a settings screen, an overlay screen, an application screen that only covers a portion of the available display area, etc. Combination screens are also possible in some cases or in operation moves, such as when a pop-up message or interface is presented on top of another screen (e.g., a home screen, an application screen, a blank screen, etc.).

[0022] The lock screen may present user interface elements that require the user to perform specific actions before accessing certain features of the mobile device. For example, the lock screen may require the user to perform a gesture on the device's touch screen (e.g., slide a virtual button, etc.), enter a password or pin, draw a pattern, touch a fingerprint reader, or look at the device's camera (e.g., face unlock, etc.) before using the device. The lock screen may also display an overview screen with (but not limited to) the current date and time, device status information (e.g., battery status, connection information, etc.), weather, recent notifications from one or more applications, contact information of the device owner (for use in the event that the device is lost or stolen, during a medical emergency, etc.), and other similar information. In addition, the lock screen may display playback controls for media and shortcuts to select applications (e.g., a camera application, etc.).

[0023] The locked to unlocked transition screen can be a transition screen displayed on the mobile device after the user has been authorized to use the device but before the mobile device has completely transitioned from a screen locked state to an unlocked state. For example, the locked to unlocked transition screen can present the user interface elements of its corresponding lock screen, but change the presentation of a closed lock to an open lock. In this case, the unlock screen (or state) can remain on the same screen (but can provide different information). In other cases, unlocking the device may cause the device to switch from the lock screen to any other screen, such as a home screen or an application screen.

[0024] In various embodiments, the unlock screen can be considered as any screen that is not a lock screen. For example, an application screen and a home screen can be an unlock screen.

[0025] A blank screen can be a screen displayed by a mobile device when the device is idle, not in use, dormant, or in a low-power mode. A blank screen can be an active presentation, or can be the result of a mobile device turning off all or part of its electronic display system. In some embodiments, the electronic display system can be in a reduced power mode in which the screen is blank, but writing on the screen can be detected by the screen. Thus, a reduced power mode is a power mode that uses more power than a low-power mode in which the screen is blank (e.g., turned off) and writing detection is turned off. In various embodiments, a mobile device can transition from a blank screen to another screen (e.g., a lock screen) in response to the mobile device detecting user interaction with the device or in response to detecting that the mobile device has moved (e.g., has been picked up, etc.).

[0026] For ease of reference, some embodiments are discussed below with reference to the lock screen and the screen lock state. However, it should be understood that any or all of the embodiments discussed in this application can be practiced on any or all screens and states discussed in this application, including the home screen (unlocked state), the application screen (unlocked), the lock to unlock transition screen (locked or unlocked state), and the blank screen (locked or unlocked state). For example, some embodiments may allow notes to be taken on a blank screen, thereby capturing user input but not immediately presenting it, thereby allowing the user to take notes discreetly or unobtrusively (e.g., in a dark room, a movie theater, etc.). As another example, some embodiments allow notes to be taken on the application screen so that the user input does not affect the underlying software application and is not stored in association with the underlying software application. This allows, for example, a user watching a video through a video streaming application to enter notes directly on top of the video display, and allows notes to be stored independently of the video streaming application (e.g., a video streaming application without recording notes, etc.).

[0027] The mobile device may be configured to provide a note-taking feature for making notes (e.g., text notes, drawings, audio recordings, video recordings, photos, etc.), which may be implemented in firmware, operating system functions, and / or in applications executed on the mobile device. In some embodiments, the notes may be synchronized between devices and / or used by other applications operating on the mobile device. Mobile device users may use the note-taking feature (e.g., note-taking application, etc.) to store small notes and memos, such as mobile phone numbers, book titles, action items (e.g., pick up tomatoes, etc.), etc.

[0028] The conventional process or procedure for storing notes using a note-taking application of a mobile device may include entering a password or biometric information on a lock screen to unlock the mobile device, interrupting a currently executing task or background process on the mobile device, locating the note-taking application via an operating system interface of the mobile device, launching the note-taking application on the device, waiting for the note-taking application to load, creating or selecting a note file in which to store the note, and entering the newly acquired / conceived information as a short note or memo. These operations are cumbersome and time-consuming, and because device users often acquire or conceive note information (e.g., phone numbers, addresses, etc.) when the mobile device is in a screen-locked state or when the mobile device is busy processing other tasks or applications, users generally give up using conventional note-taking applications to store quick notes or memos on their mobile devices.

[0029] Various embodiments overcome the above limitations of conventional solutions to enable mobile device users to store quick notes or memos on their mobile devices. In some embodiments, the mobile device may be configured to operate in a write-only interaction state (which may also be referred to as instant pen mode, single file write-only mode, etc.), which allows the device user to quickly capture, record, or store small amounts of information on the lock screen without first unlocking the phone, finding and launching a note-taking application, or any other cumbersome, time-consuming, or potentially distracting actions, operations, or tasks of the conventional solutions described above.

[0030] In some embodiments, the mobile device may be configured to operate in a write-only interactive state when the mobile device is in a screen lock state. When operating in a write-only interactive state, the mobile device may monitor the lock screen to obtain user input (e.g., text, voice, etc.) and / or provide the user with "write-only" permissions to a secure file and / or limited functionality of a note-taking application. The mobile device may display and capture user input received within a short period of time (e.g., 10 seconds, 30 seconds, 1 minute, etc.). In some embodiments, the mobile device may store user input in real time (or near real time) when the input is captured. In some embodiments, once inactivity is detected or the time period expires, the mobile device may stop displaying the user input and / or store the captured input in a file. Such note-saving files may be single, small, isolated, and / or secure files of relatively limited size. When the device remains in a screen lock state (or another screen state), the mobile device may prevent the user (or other users) from viewing, accessing, deleting, or editing the file. The mobile device may store the file in a note-taking application (or other suitable location) or in a more persistent file that is accessible only when the user is authenticated, and the mobile device exits the screen lock state (or another screen state described).

[0031] In some embodiments, the mobile device can be configured to implement an instant type function. The mobile device can respond to detecting that a user has begun typing on a connected keyboard (e.g., The instant type function can be activated by typing on a soft keyboard (e.g., keyboard, etc.) or on an electronic display of the mobile device. The mobile device can also activate the instant type function in response to various inputs, actions or conditions on the mobile device, or present a soft keyboard suitable for activating the instant type function. For example, the mobile device can be configured to activate the instant type function and / or present a soft keyboard in response to determining (e.g., based on gyroscope measurements, etc.) that the mobile device is lifted by the user. In some embodiments, the mobile device can be configured to activate the instant type function and / or present a soft keyboard in response to detecting a touch on a display screen or button of the mobile device. In some embodiments, the mobile device can be configured to activate the instant type function and / or present a soft keyboard in response to detecting the actuation of an on-screen control (e.g., button press, slide-in window input, etc.). In some embodiments, the mobile device can be configured to activate the instant type function and / or present a soft keyboard in response to receiving activation information from an associated device (e.g., smart watch).

[0032] In some embodiments, the mobile device may be configured to perform operations to authenticate the user while the mobile device is operating in a write-only interactive state. For example, the mobile device may display a lock screen and operate in a write-only interactive state, begin presenting user input in a user input area at the top of the lock screen for a period of time, store the user input in a secure file using write-only access, perform a facial recognition operation (or other similar operation) to authenticate the user while the user continues to prove input, unlock the mobile device based on the user authentication, and continue to present the user input at the top of the lock screen or at the top of a subsequent screen for a period of time, or until the user stops entering information or becomes inactive. The mobile device may store user input of limited information received by the mobile device in the write-only interactive state for a predetermined duration in a single secure file.

[0033] In some cases, the mobile device may be in a screen locked state and unlocked. For example, on some devices (e.g., iPad, iPhone, etc.), the mobile device may authenticate the user, change the presentation of a closed lock to an open lock, and continue to display the lock screen (or lock to unlock transition screen) until the user performs an appropriate input gesture (e.g., swipe up, left, or right). A mobile device configured according to various embodiments may enable a user to write on a lock to unlock transition screen before the user performs an appropriate input gesture (e.g., swipe up, left, or right to enter the home screen). In some embodiments, when the device is in a screen locked state and unlocked (e.g., when the user has been authenticated but has not yet performed an appropriate input gesture (e.g., swipe up, left, or right), the mobile device may be configured to support advanced note-taking features, such as (but not limited to) jumping to a note-taking application or generating a note pop-up graphical user interface (GUI). That is, when the device is in a screen locked state and unlocked, additional features that may not be available when the device is in a screen locked state and locked may be available.

[0034] In some embodiments, when the mobile device is operating in a write-only interactive state, the mobile device can utilize a single note-taking application. In some embodiments, when the mobile device is operating in a write-only interactive state, the mobile device can utilize multiple different note-taking applications. In some embodiments, the mobile device can be configured to dynamically determine or select a note-taking application from multiple note-taking applications and use the selected note-taking application to capture or store notes.

[0035] In some embodiments, the mobile device can be configured to determine or select a note-taking application based on user input or preferences. For example, the mobile device can be configured to present a dialog box, input box, or otherwise allow the user to select a note-taking application from a plurality of note-taking applications. In some embodiments, the mobile device can allow the user to select a note-taking application before or during a note-taking operation (e.g., capture, present, or store user input).

[0036] In some embodiments, the mobile device can be configured to determine or select a note-taking application based on context. For example, using various sensors (e.g., navigation sensors, motion sensors, cameras for light sensing, microphones, clocks, etc.), a processor of the mobile device can determine the location of the device, nearby activity, the user's activity, and other contextual elements related to whether a note-taking application should be activated. As a non-limiting example, if accelerometer data indicates that the user is walking or standing while carrying the mobile device, the processor can determine that the note-taking feature should be activated based on that context because the user is unlikely to be typing an email or writing a document in this case.

[0037] In some embodiments, the mobile device can be configured to determine or select a note-taking application based on the type of input received from the user. For example, the mobile device can select a first note-taking application (app 1) in response to determining that the user input is text input received on the keypad, select another note-taking application (app 2) in response to determining that the user input is a character shape received when the user handwrites on the device, and select yet another note-taking application (app 3) in response to determining that the user input is an audio recording or voice input received via a microphone.

[0038] In some embodiments, the mobile device can be configured to determine whether input received in a note saving input box (e.g., on a lock screen, in "insta-pen" mode, etc.) is input using a stylus. The mobile device can identify the stylus based on a current Bluetooth connection, receipt of a stylus ID, or other techniques known in the art, and determine or select a note-taking application based on the identified stylus or stylus type. For example, the mobile device can select a first note-taking application (app 1) in response to determining that the user is writing with a first stylus (stylus ID=1), and select another note-taking application (app 2) in response to determining that the user is writing with another stylus (stylus ID=2).

[0039] In some embodiments, the mobile device may be configured to determine or select a note-taking application based on user actuation of a button, such as a soft button on a screen, a physical button on a device, a physical / soft button on an associated device (e.g., a paired stylus, a smartwatch, etc.), etc. For example, the mobile device may select a first note-taking application (app 1) in response to determining that a button has not been actuated, and select another note-taking application (app 2) in response to detecting actuation of a button.

[0040] In some embodiments, the mobile device can be configured to determine or select a note-taking application based on a user ID associated with a current user of the mobile device. For example, the mobile device can identify the current user of the mobile device and select a note-taking application (e.g., app 1 or app 2) based on the identified user or user ID.

[0041] In some embodiments, the mobile device can be configured to determine or select a note-taking application based on the current location of the mobile device. For example, the mobile device can select a first note-taking application (app 1) in response to determining that the mobile device is in a first location (e.g., home, etc.), and select another note-taking application (app 2) in response to determining that the mobile device is in another location (e.g., work, a movie theater, a car, etc.).

[0042] In some embodiments, the mobile device can be configured to determine or select a note-taking application based on the current date or time of day. In some embodiments, the mobile device can be configured to determine or select a note-taking application based on the user's calendar in conjunction with the current date and / or time of day, such as when the current date / time corresponds to a scheduled meeting or event where use of the mobile device will be limited (e.g., in a meeting, at a gym, at a party, etc.).

[0043] In some embodiments, the mobile device may be configured to determine or select a note-taking application based on the operating state of the mobile device. For example, the mobile device may select a first note-taking application (app 1) in response to determining that the mobile device is in a screen-locked state, and select another note-taking application (app 2) in response to determining that the mobile device is not in a screen-locked state. As another example, the mobile device may select a first note-taking application (app 1) in response to determining that the mobile device is locked, and select another note-taking application (app 2) in response to determining that the mobile device is unlocked (authenticated).

[0044] In some embodiments, the mobile device may be configured to determine or select a note-taking application based on a location on the screen where a user input is detected and / or based on a location on the display where a note save input box is presented. For example, the mobile device may select a first note-taking application (app 1) in response to determining that the user is writing in a first portion of the screen (e.g., the upper half of the screen, the upper right portion of the screen, etc.), and select a second note-taking application (app 2) in response to determining that the user is writing in a second portion of the screen (e.g., the lower half of the screen, the lower right portion of the screen, the upper left portion of the screen, etc.). As another example, the mobile device may select a first note-taking application (app 1) in response to determining that the user is writing on a notification or widget of a first software application, and select another note-taking application (app 2) in response to determining that the user is writing on a notification or widget of a second software application.

[0045] In some embodiments, the mobile device may be configured to store the captured input in a note save file, and store the note save file in a note-taking application (or other suitable location), or in a more permanent file that is accessible only when the user is authenticated and the mobile device is not on the current screen or in a screen-locked state. In some embodiments, the mobile device may store the note save file in association with an application (e.g., a note-taking application). In some embodiments, the mobile device may store the note save file in memory without being associated with the application, and at a later point in time (e.g., when the user unlocks the device, the user views and organizes files, etc.), associate the stored note save file with the application.

[0046] In some embodiments, the mobile device can be configured to request the user to perform an authentication operation (e.g., enter a password or biometric information, etc.) to exit the lock screen (or unlock the device) in response to determining that the user input exceeds a threshold size (e.g., file size, number of characters, etc.) and / or in response to determining that a time period allowing use of a write-only interactive state has expired.

[0047] In some embodiments, the mobile device can be configured to provide autonomous organization of notes / files locally on the device and / or remotely via a cloud or communication network. In some embodiments, the mobile device can be configured to autonomously organize notes / files based on word recognition and / or language context.

[0048] In some embodiments, the mobile device may be configured to populate and store the note save file in the memory of the mobile device without authenticating the user to the mobile device.

[0049] In some embodiments, the mobile device may be configured to not present or display the contents of the note save file after the note save file is stored in memory.

[0050] In some embodiments, the mobile device may be configured to store all notes / input received within a predefined duration (eg, 20 seconds, etc.) in the same note saving file.

[0051] In some embodiments, the mobile device may be configured to automatically name the note save file.

[0052] In some embodiments, the note saving file may be a database file and / or the mobile device may be configured to create or store the note saving file using database technology.

[0053] In some embodiments, the mobile device may be configured to store all notes or received input in a single note storage file.

[0054] In some embodiments, the mobile device may be configured to store each note in conjunction with a timestamp and / or location information.

[0055] In some embodiments, the mobile device can be configured to determine the number of input characters received as a note or within a predefined duration (e.g., 20 seconds, etc.) and compare it to an input threshold. The mobile device can be configured to trigger an authentication process (e.g., requesting the user to enter a password or biometric information on the lock screen to unlock the mobile device) in response to determining that the number of input characters meets (e.g., reaches or exceeds) the input threshold.

[0056] In some embodiments, the mobile device may be configured to automatically delete the note save file in response to detecting the presence or absence of a particular condition. For example, in some embodiments, the mobile device may be configured to automatically delete the note save file in response to determining that the mobile device has not been unlocked for a certain period of time (e.g., to prevent / ignore erroneous input or notes from people who do not have access to the device). In some embodiments, the mobile device may be configured to automatically delete the note save file in response to determining that the notes have not been acted upon, such as if the user is too lazy to sort the notes after the device is unlocked, then the notes may not be important enough to store.

[0057] In some embodiments, the mobile device can be configured to present a view of note saving files when the user launches a note-taking application and / or when the device is operating in a normal, full, or unlocked operating mode where the lock screen is no longer displayed. The view of the note saving files may include a list of note saving files, the contents of the note saving files, etc. The view may group the note saving files by date, time, location, length, relevance, etc. In some embodiments, the view may be configured by the user and / or based on user preferences. In some embodiments, the mobile device may generate or present a view of the note saving files remotely or locally on the device. By default, the view may be generated locally, and the user may choose to generate the view remotely.

[0058] In some embodiments, the mobile device may be configured to convert the contents of an audio-based note save file to a text file, and vice versa. In some embodiments, the mobile device may be configured to convert written material to text. In some embodiments, the mobile device may be configured to perform the conversion (e.g., from an audio-based note save file to a text file, from written material to text, etc.) after the mobile device enters an unlocked state. For example, the mobile device may be configured to store the original input (e.g., original audio or text, etc.) when the device is locked and operating in a write-only interactive state, and in response to determining that the device has been converted from a locked state to an unlocked state, convert the stored original input (e.g., converted to text, etc.). In some embodiments, the mobile device may perform the conversion (i.e., store the converted material, not the original input data) when the device is locked or in a screen lock state. In some embodiments, the mobile device may be configured to store the original input, the conversion, or both the original input and its conversion in a memory when the device operates in a locked or unlocked state.

[0059] In some embodiments, the mobile device can be configured to autonomously organize, categorize, name, provide, combine, etc. descriptive information of the note saving files (e.g., by date, time, location, file name, length, relevance, priority, etc.).

[0060] In some embodiments, the mobile device can be configured to generate and / or organize note save files such that each note save file is an action item (eg, all book titles, etc.).

[0061] In some embodiments, the mobile device can be configured to associate or apply different categories or principles to each note saving file.

[0062] In some embodiments, the mobile device may be configured to send the note save file to a cloud server for further processing and / or organization.

[0063] In some embodiments, the mobile device can be configured to present a note save input box on the lock screen after detecting user activity. In some embodiments, the mobile device can stop presenting the note save input box after detecting inactivity (e.g., after detecting a set amount of inactivity). In some embodiments, the mobile device can stop presenting the note save input box after a time period expires, such as after a set amount of time from the start of the input.

[0064] In some embodiments, the mobile device can be configured to always present the note save input box on the lock screen.

[0065] In some embodiments, the mobile device may be configured to present a note save input box on the lock screen or any other screen (e.g., when the device is unlocked and the user is using other applications on the device, etc.) in response to detecting a special finger gesture.

[0066] In some embodiments, the mobile device may be configured to fade out or stop displaying older input as the user continues to provide input and / or over time. For example, in some embodiments, the mobile device may present the text entered by the user so that only the most recently entered words or characters (e.g., characters entered in the past 2, 5, 10, or 15 seconds) are displayed in the note saving input box, while previously entered characters gradually become illegible or invisible. In some embodiments, the mobile device may present the text entered by the user so that only a certain number of characters (e.g., 5, 10, 15, etc. characters) are displayed in the note saving input box, and as the user adds new characters, the earliest input characters fade out and / or disappear. In some embodiments, the mobile device may present the text entered by the user so that only a certain amount of screen space is consumed, and as the user provides additional input that consumes more space on the screen, the earlier input fades out or disappears from the edge of the screen space. For example, if the user takes down 4 lines of notes, the first line may fade out when the third line is entered. Therefore, the user may only see the last N lines or may only see the current line.

[0067] In some embodiments, the mobile device may display and capture user input received within a short period of time (e.g., 10 seconds, 30 seconds, 1 minute, etc.) In some embodiments, the number of characters / words, the amount of time used to display the characters / words, and / or the amount of space the displayed characters take up may be user configurable.

[0068] In some embodiments, the mobile device may be configured to sort the note-keeping files as recorders in chronological order in a database file.

[0069] In some embodiments, the mobile device can be configured to determine and add the time and location of each note save file to facilitate automatic further processing of the notes.

[0070] In some embodiments, the mobile device can be configured to group the note-keeping files according to time (eg, date, time, etc.) and present the user with a view of a list of files, where each file is numbered with a date.

[0071] In some embodiments, the mobile device can be configured to group the note save files together. The mobile device can further expand the grouped notes so that the note records can be presented to the user for reading and further processing.

[0072] In some embodiments, the mobile device can be configured to supplement the note save file locally or remotely. For example, when operating in the functional mode of various embodiments, the mobile device can identify note records that only include a few words and / or do not describe the full meaning, and provide the user with options for supplementing these notes, such as by adding words, punctuation marks, etc.

[0073] In some embodiments, the mobile device can be configured to store each note or each group of received input (e.g., input received within a predefined duration) in a separate note save file. In these embodiments, each note or note save file can provide a time and / or date description in the file name and / or title of the note save file. For example, the mobile device can generate a file name "1212201301.txt" for a note created at 1:01 PM on December 12, 2020. Alternatively or additionally, the mobile device can generate a note save file to include metadata or a title that contains a time and / or date description (e.g., "Note from 12 / 12 / 20 at 1:01 PM").

[0074] In some embodiments, the mobile device can be configured to provide periodic reminders to the user to save notes or otherwise act on notes (e.g., save, edit, categorize, ignore, etc.). The mobile device can present reminders on the lock screen or on any other screen (e.g., when the device is unlocked, the user is using other applications, etc.).

[0075] In some embodiments, the mobile device can be configured to operate in a "whiteboard" mode. The mobile device can determine whether the input received in the note saving input box (e.g., on the lock screen, in "insta pen" mode, etc.) was entered using a stylus / finger. The mobile device can store non-text input from the stylus / finger as writing or convert it to text. For example, the mobile device can convert shapes drawn on the lock screen to letters. The mobile device can perform the conversion in the screen locked state or after the device is unlocked (e.g., the input can be saved in the screen locked state and then converted).

[0076] In some embodiments, the mobile device can be configured to save notes written on the device by pressing a save button (e.g., a soft button on the screen, a physical button on the device, a physical / soft button on an associated device (e.g., a paired stylus, smartwatch, etc.), etc.). In some embodiments, the mobile device can be configured so that notes being written on the device are saved by locking the device (e.g., pressing a button locks the device even if the device is already locked), based on an inactivity timer since the last note was written, periodically (auto-save feature), etc.

[0077] In some embodiments, the mobile device may be configured to support multiple users by distinguishing notes / inputs from different users and switching user profiles. For example, the mobile device may associate input received from a first stylus with one user and switch another user from input received from a second stylus. The mobile device may switch user profiles based on the stylus used. In some embodiments, the mobile device may be configured to switch user profiles based on actuation of a selection button included on a stylus, a mobile device, or another device communicatively coupled to the mobile device. In some embodiments, the mobile device may be configured to distinguish users based on biometrics (e.g., facial recognition, fingerprints, etc.), via a stylus, via a smart watch / ring, or other methods traditionally used to authenticate users. In some embodiments, the mobile device may be configured to classify a user as an unknown user, create a profile for an unknown user, and / or switch to an unknown user profile (e.g., when user authentication fails, etc.).

[0078] In some embodiments, the mobile device can be configured to differentiate between users based on writing style (eg, handwriting or character recognition) or any other means known in the art for determining between a first user profile and a second user profile (or an unknown user profile).

[0079] Various embodiments improve the security, privacy, performance, and / or functionality of a mobile device. For example, by only allowing a user to enter a limited amount of information when the device is locked, embodiments prevent hackers or other malicious actors from entering large amounts of information that consume large amounts of the device's memory resources and / or negatively impact other background applications operating on the device. By storing information in isolated and secure files, various embodiments prevent hackers or other malicious actors from injecting malware or entering information (e.g., a uniform resource locator (URL) to a website with a virus, etc.), which could compromise the mobile device. By preventing a user who is entering notes from accessing previously recorded notes or data from other applications, embodiments improve the privacy and functionality of a mobile device.

[0080] Figure 1 Components of a mobile device 100 suitable for implementing various embodiments are shown. Figure 1 In the example shown, the mobile device 100 includes a subscriber identity module (SIM) interface 102, an identity module SIM 104, a general processor 106 (e.g., a central processing unit (“CPU”)), a coder / decoder (CODEC) 108, a speaker 110, a microphone 112, a memory 114, a baseband modem processor 116, a radio frequency (RF) resource 118, an antenna 120, a system on a chip (SOC) 122, a physical button 124, a touch screen display 126, peripherals 128 (e.g., a camera, etc.), and various controllers / microcontrollers 130. In some embodiments, the general processor 106, the memory 114, the baseband processor 116, and the RF resource 118 may be included in the SOC 122. In some embodiments, the SIM 104 and its corresponding interface 102 may be external to the SOC 122.

[0081] In some embodiments, the mobile device 100 may also include a graphics processor unit (GPU), a modem digital signal processor (DSP), an application processor unit (APU), and / or other special-purpose processors or hardware accelerators (not shown). Any or all processors in the mobile device 100 may include one or more homogeneous or heterogeneous processor cores. Homogeneous processor cores may be cores configured for the same purpose and / or having the same or similar performance characteristics. Heterogeneous processor cores may be cores configured for different purposes and / or having different performance characteristics. The heterogeneity of such heterogeneous processor cores may include different instruction set architectures, pipelines, operating frequencies, etc. Examples of such heterogeneous processor cores may include a so-called "big.LITTLE" architecture, in which a slower, lower-power processor core may be coupled with a more powerful, higher-power processor core.

[0082] SIM interface 102 may be configured to receive an identity module SIM 104 associated with a subscription to a mobile telephone network. In some embodiments, mobile device 100 may be a multi-subscription mobile device including additional SIM interfaces, each of which may receive additional identity modules SIM associated with other subscriptions and / or other mobile telephone networks.

[0083] The general purpose processor 106 may be coupled to a CODEC 108, which may be coupled to a speaker 110 and a microphone 112. The general purpose processor 106 may also be coupled to at least one memory 114. The memory 114 may be a non-transitory computer-readable storage medium that stores processor-executable instructions. The memory 114 may also store operating system (OS) software, application data, user applications, software, and / or executable instructions, including instructions configured to cause the processor to perform the operations of the various embodiments.

[0084] The baseband modem processor 116 may be an integrated chip capable of managing the SIM 104 or the protocol stack of the subscription and implementing the coexistence manager software.

[0085] The RF resources 118 may include communication circuitry or a transceiver that performs transmit / receive functions for the associated SIM 104 of the mobile device 100. The RF resources 118 may include communication circuitry that includes separate transmit and receive circuitry, or may include a transceiver that combines transmitter and receiver functions. The RF resources 118 may be configured to support multiple radio access technologies / wireless networks operating according to different wireless communication protocols. The RF resources 118 may include or provide connections to a collection of different amplifiers, digital-to-analog converters, analog-to-digital converters, filters, voltage-controlled oscillators, etc. Multiple antennas 120 and / or receive blocks may be coupled to the RF resources 118 to facilitate multi-mode communications using various combinations of antennas and receiver / transmitter frequencies and protocols (e.g., LTE, Wi-Fi, Bluetooth, near field communications, etc.). The RF resources 118 may also be coupled to the baseband modem processor 116.

[0086] The mobile device 100 can be configured to operate within various communication systems such as a mobile phone network. The mobile device 100 can communicate with the mobile phone network via a cellular connection to a base station of the mobile phone network. The cellular connection can be achieved by a two-way wireless communication link using a variety of communication technologies such as long-term evolution (LTE), fifth generation (5G), fourth generation (4G), third generation (3G), code division multiple access (CDMA), time division synchronous code division multiple access (TD-SCDMA), wideband code division multiple access (WCDMA), global system for mobile communications (GSM) and other mobile phone communication technologies. Other connections can include various other wireless connections, including WLAN, such as Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, and wireless positioning services, such as global positioning system (GPS); WPAN, such as wireless USB, Bluetooth and ZigBee; and / or near field communication.

[0087] Figure 2 A mobile device 202 (eg, Figure 1 Various interface screens, operating modes, and operations in the mobile device 100, etc. shown in FIG. Figure 1 and Figure 2, the mobile device 202 may include a fingerprint scanner 208 configured to detect fingerprint features of a user in response to the user engaging a finger on the fingerprint scanner 208 while the user is holding the mobile device 202. Alternatively or additionally, the mobile device 202 may include a camera 210 and / or other sensors configured to detect and evaluate facial features of the user in response to the user moving or using the mobile device 202, and may be used to authenticate the user based on facial recognition.

[0088] In some embodiments, a processor in mobile device 202 (e.g., general purpose processor 106, etc.) can be configured to authenticate a user by receiving data representing facial or fingerprint features of the user, comparing these features with biometric information stored in memory (e.g., memory 114), and / or sending the data representing these features to a remote computing device for analysis. Mobile device 202 can be configured to enter an unlocked state in response to determining that the detected features match the biometric information stored in memory or in response to receiving an indication from a remote computing device that the data representing the features is accepted for unlocking mobile device 202.

[0089] In various embodiments, the mobile device 202 can be configured to authenticate the user before, during, or after entering the write-only interactive state. In some embodiments, the mobile device 202 can be configured to authenticate the user in the screen. For example, the mobile device can be configured to collect fingerprint information from the user while the user is typing or writing notes on the screen. The mobile device can authenticate the user based on the collected in-screen fingerprint information.

[0090] In some embodiments, the mobile device 202 can be configured to transition from the lock screen to the application screen of the note-taking application. For example, the mobile device 202 can present the lock screen, enter a write-only interactive state, and begin capturing and presenting user input in the user input area on the lock screen. The mobile device can authenticate the user (e.g., based on collected in-screen fingerprint information, etc.) while continuing to capture and present user input in the user input area on top of the lock screen. In response to authenticating the user, the mobile device can transition from displaying the lock screen to displaying the application screen of the note-taking application. The mobile device can continue to capture user input and present the captured user input at the top of the application screen of the note-taking application (e.g., in the same user input area or location on the electronic display, but on top of a different screen or background, etc.).

[0091] To save battery resources, the mobile device 202 can be configured to enter an inactive interaction state when the mobile device 202 is not being used. While in the inactive interaction state, the mobile device 202 can execute background applications, such as an instant pen application, and restrict or limit the user and external applications from reading or writing files stored on the mobile device 202. The mobile device 202 can also monitor its sensors (e.g., touch screen, gyroscope, camera, etc.) to collect sensor data, which can include measurements of the movement of the mobile device 202 and / or gestures made by the user of the mobile device 202. The mobile device 202 can determine whether the user has picked up the mobile device 202 or otherwise attempted to interact with the mobile device 202 based on the collected sensor data.

[0092] The mobile device 202 may enter a write-only interaction state, an instant pen mode, a screen lock state, and / or display a lock screen 204 in response to determining that a user has picked up the mobile device 202 or otherwise attempted to interact with the mobile device 202. The lock screen 204 may govern instant access to the mobile device 202 by requiring the user to perform a specific action before accessing specific features of the mobile device 202. For example, the lock screen 204 may require the user to authenticate, such as by having the user perform a gesture on the device's touch screen 206, touch a fingerprint reader 208, look at the device's camera 210 (e.g., face unlock, etc.), enter a password or pin, draw a pattern, etc.

[0093] When operating in a write-only interactive state in a screen-locked state, the mobile device 202 can provide the user and selected device applications with limited or partial access to the processing and storage resources of the mobile device 102. For example, when in a write-only interactive state, the mobile device 202 can allow the instant pen application to operate in the background of the mobile device and provide the user with "write-only" permissions to allow the user to write to the instant pen application. In addition, the mobile device 202 can display the user inputting a time period (e.g., 10 seconds, 30 seconds, 1 minute, etc.) in the user input area 212 on the electronic display of the mobile device 202.

[0094] Once user inactivity is detected and / or the time period allowed by the write-only interaction state has expired, the mobile device 202 can stop presenting the user input area 212 on the electronic display (although the lock screen 204 continues to be presented). The mobile device 20 can store the input in a small isolated file in the memory of the mobile device 202. Whether the mobile device 202 remains in the active interaction state, continues to display the lock screen 204, or re-enters the inactive interaction state, the mobile device 202 can stop presenting the user input area 212. The mobile device 202 can also prevent the user from viewing, accessing, deleting, or editing the file until the mobile device 202 authenticates the user and exits the screen lock state. In some embodiments, the mobile device 202 can be configured to store all inputs collected within a time period (e.g., 1 hour, 1 day, etc.) in a single file.

[0095] In some embodiments, in response to determining that user input has exceeded a threshold (e.g., file size, number of characters, etc.) or in response to determining that a time period has expired, mobile device 202 can be configured to request the user to perform an authentication operation (e.g., enter a password or biometric information, etc.) to exit lock screen 204.

[0096] The mobile device 202 may authenticate the user (e.g., in response to receiving a valid pin, facial scan, fingerprint, etc.), cease displaying the lock screen 204, exit the screen lock state, and begin displaying an unlock screen 220 that allows the user to access applications installed on the mobile device 202 (e.g., notes, weather, settings, app store, etc.). The unlock screen 220 may include a note-taking application 222, selection of which by the user may cause the mobile device 202 to display a note file screen 230 that provides the user with access to notes captured in a previous write-only interactive state session. The note file screen 230 and / or the instant pen application may provide the user with autonomous organization of notes / files stored locally on the device and / or notes or files stored remotely on a network or cloud server.

[0097] In some embodiments, mobile device 202 can be configured to monitor its sensors (e.g., touch screen, camera, etc.) to detect gestures after the user has been authenticated. Mobile device 202 can determine whether the detected gesture matches a gesture stored in memory, and in response to determining that the detected gesture matches a gesture stored in memory, begin displaying user input in user input area 240 in unlock screen 220.

[0098] Figure 3A , Figure 3B , Figure 4 and Figure 5 Methods 300, 320, 400, 500 for capturing notes by a mobile device are shown. Figures 1 to 5The operations of methods 300, 320, 400, and 500 may be performed or implemented in hardware components and / or software components of a mobile device (e.g., mobile device 100, mobile device 202, etc.), the operations of which may be controlled by one or more processors (e.g., processors 106, 116, etc.).

[0099] refer to Figure 3A , in block 302 , the mobile device may enter and operate in an inactive interaction state that limits or restricts users and external applications from reading or writing files stored on the mobile device.

[0100] In box 310, the processor can cause the mobile device to operate in an active interactive state that provides write-only access to a small secure file on the mobile device. In some embodiments, the write-only access secure file can be isolated from other software applications operating on the mobile device. In some embodiments, the mobile device can be configured to present a note save input box on the lock screen after detecting user activity. In some embodiments, the mobile device can be configured to always present the note save input box on the lock screen. In some embodiments, the mobile device can be configured to present a note save input box on the lock screen or any other screen (e.g., when the device is unlocked and the user is using other applications on the device, etc.) in response to detecting a special finger gesture.

[0101] In various embodiments, the write-only mode initiated in block 310 may allow a user to enter a limited amount of text or numbers and a limited time (eg, 10 seconds, 30 seconds, 1 minute, etc.).

[0102] In some embodiments, in box 310, the mobile device can be configured to operate in a "whiteboard" mode. The mobile device can determine whether the input received in the note saving input box (e.g., on the lock screen, in "insta pen" mode, etc.) is input using a stylus / finger. The mobile device can store non-text input from the stylus / finger as writing or convert it to text. For example, the mobile device can convert shapes drawn on the lock screen to letters. The mobile device can perform the conversion in the screen locked state or after the device is unlocked (e.g., the input can be saved in the screen locked state and then converted).

[0103] In some embodiments, in box 310, the mobile device may be configured to support multiple users by distinguishing notes / inputs from different users and switching user profiles. For example, the mobile device may associate input received from a first stylus with one user and switch another user from input received from a second stylus. The mobile device may switch user profiles based on the stylus used. In some embodiments, the mobile device may be configured to switch user profiles based on actuation of a selection button included on a stylus, a mobile device, or another device communicatively coupled to the mobile device. In some embodiments, the mobile device may be configured to distinguish users based on biometrics (e.g., facial recognition, fingerprints, etc.), via a stylus, via a smart watch / ring, or other methods traditionally used to authenticate users. In some embodiments, the mobile device may be configured to classify a user as an unknown user, create a profile for an unknown user, and / or switch to an unknown user profile (e.g., when user authentication fails, etc.). In some embodiments, the mobile device may be configured to distinguish users based on writing style (e.g., handwriting or character recognition) or any other means known in the art for determining between a first user profile and a second user profile (or an unknown user profile).

[0104] In block 312, the mobile device may display a lock screen at the top of the lock screen in a user input area (e.g., Figure 2 The user input is presented in an isolated and secure file (e.g., area 240 on display 212 shown in FIG. 310 , etc.) for a limited time period (e.g., 10 seconds, 30 seconds, 1 minute, etc.), and the user input is stored in a secure file using write-only access provided by the active interactive state in box 310. The size and security of the file can allow a user to enter a limited amount of information when the device is locked. Limiting the amount of information that can be entered in this mode can prevent hackers or other malicious actors from entering large amounts of information that consume large amounts of memory resources of the device and / or can negatively impact other background applications running on the mobile device. In addition, by storing information in an isolated and secure file, various embodiments prevent hackers or other malicious actors from injecting malware or inputting information that could compromise the mobile device (e.g., URLs to websites with viruses, etc.).

[0105] In some embodiments, the mobile device may be configured to populate and store a note save file in a memory of the mobile device without authenticating the user to the mobile device. In some embodiments, the mobile device may be configured not to present or display the contents of the note save file after the note save file is stored in the memory. In some embodiments, the mobile device may be configured to store all notes / inputs received within a predefined duration (e.g., 20 seconds, etc.) in the same note save file. In some embodiments, the mobile device may be configured to automatically name the note save file, for example, at the time of save or at any other suitable time. In some embodiments, the note save file may be a database file and / or the mobile device may be configured to create or store the note save file using database technology. In some embodiments, the mobile device may be configured to store all notes or received inputs in a single note save file. In some embodiments, the mobile device may be configured to store each note in conjunction with a timestamp and / or location information.

[0106] In determination block 314, the mobile device may determine whether a time period for receiving and presenting user input has expired and / or whether the user has become inactive (e.g., has stopped typing, speaking, or otherwise entering information) for a time period (e.g., 5 seconds, 10 seconds, etc.). In some embodiments, the mobile device may stop presenting the note save input box after detecting inactivity or expiration of the time period. In response to determining that the time period has not expired and the user has not become inactive (i.e., determination block 314 = "No"), in block 312, the mobile device may continue to present the user input on the lock screen in the user input area on the mobile device display.

[0107] In response to determining that the time period for receiving and presenting user input has expired or the user has become inactive (ie, determination block 314 = "Yes"), the mobile device may stop displaying the lock screen at the top of the lock screen in a user input area (eg, Figure 2 212 shown in FIG. 24 ) on the display 212. By suspending the write-only interactive state (i.e., stopping receiving and presenting user input on top of the lock screen), various embodiments can prevent a user who enters a quick note while the device is in the screen lock state from accessing previously recorded notes or data from other applications. This can improve the privacy and functionality of the mobile device.

[0108] refer to Figure 3B, in blocks 302 and 308-316, the mobile device may perform the operations of the like numbered blocks of the method 300. In block 304, the mobile device may monitor sensors of the mobile device that provide information that helps determine whether the user has picked up the mobile device or is otherwise interacting with or attempting to interact with the mobile device. For example, the processor may monitor an electronic gyroscope and / or accelerometer to detect motion consistent with the user picking up the mobile device. As another example, the processor may monitor a front-facing camera to determine whether the user is looking at the mobile device. As another example, the processor may interpret touches on a touch-sensitive display when the user attempts to interact with the mobile device.

[0109] In determination block 306, the mobile device may determine whether the user has picked up the mobile device or is otherwise interacting with or attempting to interact with the mobile device based on the sensor input and analysis in block 304. In response to determining that the user has not picked up the mobile device or is not otherwise interacting with or attempting to interact with the mobile device (i.e., determination block 306 = "No"), the mobile device may continue to monitor the sensors of the mobile device in block 304.

[0110] In response to determining that the user has picked up the mobile device or is otherwise interacting or attempting to interact with the mobile device (ie, determination block 306 = “Yes”), the mobile device may perform the operations of blocks 308 - 316 of method 300 .

[0111] refer to Figure 4 (It can be used Figure 1 -3 or any other embodiment disclosed herein), in block 402 of method 400, the mobile device may use various conventional authentication mechanisms to authenticate the mobile device user. For example, the mobile device may request the user to perform a gesture on the device's touch screen, enter a password or pin, draw a pattern, touch a fingerprint reader, or look at the device's camera (e.g., face unlock, etc.), and if the user's input or biometric information matches the information stored in the memory, the mobile device user is authenticated. In some embodiments, the mobile device may be configured to determine the number of input characters received for a note within a predetermined duration (e.g., 20 seconds, etc.) and compare it to an input threshold, and trigger an authentication procedure (e.g., requesting the user to enter a password or biometric information on the lock screen to unlock the mobile device) in response to determining that the number of input characters meets (e.g., reaches or exceeds) the input threshold.

[0112] In response to authenticating the user in block 402 , the mobile device may display an unlock screen in block 404 that provides the user with full access to the mobile device, including access to data stored on the device and use of software applications.

[0113] In block 406, the mobile device may store the contents of the secure file (e.g., received as part of the operation in block 312, etc.) in a note-taking application of the mobile device. Thus, notes entered by the user on the lock screen during plain text mode may be stored in memory within the note-taking application and may be accessed (e.g., read, edit, or delete) by the user through the note-taking application once the user has been authenticated by the mobile device.

[0114] refer to Figure 5 (It can be used Figures 1 to 4 ), in block 502 of method 500, the mobile device may store (e.g., in a single file, in multiple files, in local memory of the mobile device, in a cloud server, etc.) user input received while the device was operating in a locked and active interactive state (e.g., blocks 308-312, etc.) for a previous duration (e.g., the previous 24 hours, etc.). Thus, as a user enters notes and text in a plain text lock screen mode, the input may be temporarily stored in memory and then merged into a single file spanning a predetermined amount of time. For example, a user may configure a plain text lock screen application to merge all notes entered over a period of one hour, one workday, 24 hours, one week, etc., into a single file.

[0115] In boxes 402 and 404, the mobile device can authenticate the user and display an unlock screen that provides the user with more robust access to the device or its software applications, as described by the same numbered boxes of method 400. In some embodiments, the mobile device can be configured to present a view of the note saving file when the user launches the note-taking application and / or when the device is operated in a normal, full, or unlocked operating mode in which the lock screen is no longer displayed. The view of the note saving file may include a list of note saving files, the contents of the note saving file, etc. The view can group the note saving files by date, time, location, length, relevance, etc. In some embodiments, the view can be configured by the user and / or based on user preferences. In some embodiments, the mobile device can generate or present a view of the note saving file remotely or locally on the device. By default, the view can be generated locally, and the user can choose to generate the view remotely.

[0116] In box 508, the mobile device may store the contents of one or more secure files in the note-taking application, each secure file storing user input collected over a duration (e.g., 24 hours, etc.) when the device is operating in a locked and active interactive state. In some embodiments, the mobile device may be configured to store each note or each group of received inputs (e.g., inputs received over a predefined duration) in a separate note save file. In such embodiments, each note or note save file may provide a time and / or date description in the file name and / or title of the note save file. For example, the mobile device may generate a file name "1212201301.txt" for a note created at 1:01 p.m. on December 12, 2020. Alternatively or additionally, the mobile device may generate a note save file to include metadata or a title that includes a time and / or date description (e.g., "Notes from 12 / 12 / 20 at 1:01 p.m."). In some embodiments, the mobile device may be configured so that notes written on the device are saved by pressing a save button (e.g., a soft button on the screen, a physical button on the device, a physical / soft button on a related device (e.g., a paired stylus, a smartwatch, etc.), etc.). In some embodiments, a mobile device can be configured such that notes being written on the device are saved by locking the device (e.g., pressing a button that locks the device even if the device is already locked), based on an inactivity timer since the last note was written, periodically (auto-save functionality), etc.

[0117] The mobile device may autonomously organize one or more secure files locally on the mobile device or remotely via a cloud or communication network in block 510. For example, a user may define that the processor should organize notes and information entered by the user via a plain text lock screen application by user-set categories, selection criteria, storage locations, routing information, and other user-specified manners.

[0118] In some embodiments, in box 510, the mobile device may be configured to convert the contents of an audio-based note save file to a text file, and vice versa. In some embodiments, in box 510, the mobile device may be configured to automatically organize the note save files (e.g., by date, time, location, file name, length, relevance, priority, etc.). In some embodiments, in box 510, the mobile device may be configured to generate and / or organize the note save files so that each note save file is an action item (e.g., all book names, etc.). In some embodiments, in box 510, the mobile device may be configured to associate or apply different categories or principles to each note save file. In some embodiments, in box 510, the mobile device may be configured to send the note save file to a cloud server for further processing and / or organization.

[0119] In some embodiments, in box 510, the mobile device may be configured to categorize the note save files into recorders in a database file in chronological order. In some embodiments, in box 510, the mobile device may be configured to determine and add the time and location of each note save file to facilitate automatic further processing of the notes. In some embodiments, in box 510, the mobile device may be configured to group the note save files according to time (e.g., date, time, etc.) and present a view of the file list to the user, where each file is numbered with a date. In some embodiments, in box 510, the mobile device may be configured to group the note save files together. The mobile device may further expand the grouped notes so that the note records can be presented to the user for reading and further processing.

[0120] In some embodiments, the mobile device may be configured to locally or remotely supplement the note save file in block 510. For example, when operating in the functional mode of various embodiments, the mobile device may identify note records that include only a few words and / or do not describe the full meaning, and provide the user with options for automatically supplementing these notes, such as by adding words, punctuation marks, etc.

[0121] In some embodiments, the mobile device can be configured to provide periodic reminders to the user to save notes or otherwise act on notes (e.g., save, edit, categorize, ignore, etc.). The mobile device can present reminders on the lock screen or on any other screen (e.g., when the device is unlocked, the user is using other applications, etc.).

[0122] Figure 6 A method 600 of capturing notes on a mobile device according to some embodiments is shown. Figures 1 to 6 The operations of method 600 may be performed or implemented in hardware components and / or software components of a mobile device (eg, mobile device 100, mobile device 202, etc.), the operations of which may be controlled by one or more processors (eg, processors 106, 116, etc.).

[0123] In block 602, the mobile device may display a lock screen on an electronic display of the mobile device and operate in a write-only interactive state that provides write-only access to a secure file on the mobile device and enables a user to enter limited information stored in the secure file.

[0124] In block 604, the mobile device may present the user input in the user input area at the top of the lock screen for a time period and store the user input in the secure file using write-only access. The mobile device may stop receiving and presenting the user input in response to expiration of the time period or in response to detecting user inactivity.

[0125] In block 606, the mobile device may store in a single secure file limited information user input received by the mobile device in a write-only interactive state over a predefined duration.

[0126] 7A to 7D Methods 700, 720, 740, 760 of capturing notes on a mobile device according to some embodiments are shown. Figures 1 to 7D The operations of methods 700, 720, 740, and 760 may be performed or implemented in hardware components and / or software components of a mobile device (e.g., mobile device 100, mobile device 202, etc.), the operations of which may be controlled by one or more processors (e.g., processors 106, 116, etc.).

[0127] refer to Fig. 7A In block 702 of method 700, the mobile device may operate in a write-only interactive state or instant pen mode. In block 704, the mobile device may monitor user input (e.g., text, voice, etc.), or provide the user with "write-only" access to limited functionality of a secure file or note-taking application. In block 706, when user input is received in real time (or near real time), the mobile device may display the user input and capture the user input in a note saving file.

[0128] refer to Figure 7B In blocks 702 and 704 of method 720, the mobile device may perform the operations of the same numbered blocks of the above method 700. In block 7B, the mobile device may display and capture user input received within a short period of time (e.g., 10 seconds, 30 seconds, 1 minute, etc.).

[0129] refer to Figure 7C , after the operations in box 706 of method 700 or box 722 of method 720, when inactivity or expiration of the time period is detected in box 742 of method 740, the mobile device may stop displaying the user input and / or store the captured input in a note saving file. Such a note saving file may be a single, small, isolated and / or secure file of relatively limited size. In box 744, the mobile device may prevent the user (or other users) from viewing, accessing, deleting, or editing the file while the device remains on the current screen or is in a screen-locked state. In box 746, the mobile device may store the file in a note-taking application (or other suitable location), or in a more permanent file that is accessible only when the user is authenticated and the mobile device is not on the current screen or is not in a screen-locked state.

[0130] refer to Fig.7DIn blocks 702 and 704 of method 760, the mobile device may perform the operations of the like numbered blocks of described methods 700 and 720. In block 762, the mobile device may begin displaying and capturing user input.

[0131] In determination block 764, the mobile device may determine whether the captured user input satisfies a threshold. For example, in block 762, the mobile device may determine the number of input characters received for a note or within a predefined duration (e.g., 20 seconds, etc.) and compare it to an input threshold. As another example, in block 762, the mobile device may determine whether the mobile device has not been unlocked within a threshold amount of time or test any other similar condition.

[0132] In response to determining that the captured user input satisfies the threshold (ie, determination block 764 = “Yes”), the mobile device may store the captured input in a note saving file in block 766 .

[0133] In response to determining that the captured user input does not meet the threshold (i.e., determination block 764 = "No"), the mobile device may ignore, not store, or delete the user input in block 768. For example, in block 768, the mobile device may delete input that is too short, such as input that is shorter than a threshold (e.g., 0.5 seconds, 1 second, etc.).

[0134] FIG. 8A to FIG. 8E Methods 800, 820, 840, 860, 880 of activating or exiting a write-only interaction state to capture a note on a mobile device are shown in accordance with some embodiments. Figures 1 to 8E The operations of methods 800, 820, 840, 860, and 880 may be performed or implemented in hardware components and / or software components of a mobile device (e.g., mobile device 100, mobile device 202, etc.), the operations of which may be controlled by one or more processors (e.g., processors 106, 116, etc.).

[0135] refer to Fig. 8A In block 802 of method 800, the mobile device may detect user input outside of a user input element of a current screen. In some embodiments, the current screen may be a lock screen. In block 804, the mobile device may activate a write-only interaction state. That is, Fig. 8A In the example shown, in response to the mobile device detecting user input outside of the user input element of the current screen (lock screen), the mobile device activates the write-only interaction state. When operating in the write-only interaction state, the mobile device can monitor the user input (e.g., text, voice, etc.) on the screen and / or provide the user with "write-only" permissions to the secure file and / or to limited functions of the note-taking application. The mobile device can then execute block 302 of method 300, block 702 of method 700, or block 842 of method 840 ( Figure 8C ) in one of the following operations.

[0136] refer to Figure 8B In block 822 of method 820, the mobile device may monitor the mobile device system to detect actuation of a physical or virtual button on the mobile device, activation of a stylus or other connected device, a voice command, or other appropriate specified user input that indicates that the mobile device should operate in a write-only interaction state and / or that the user intends to take notes on the mobile device. In determination block 824, the mobile device may determine whether the appropriate specified user input has been received on the mobile device. For example, the mobile device may determine whether a specified physical or virtual button has been actuated, whether a stylus or connected device has been activated, whether an appropriate voice command has been received, etc.

[0137] In response to determining that the appropriate designated user input has not been received (ie, determination block 824 = “No”), the mobile device may continue to monitor for actuation of a physical or virtual button or the like in block 822 .

[0138] In response to determining that the appropriate specified user input has been received (i.e., determination block 824 = "Yes"), the mobile device may activate the write-only interaction state in block 804. The mobile device may then execute block 302 of method 300, block 702 of method 700, or block 842 of method 840 ( Figure 8C ) in one of the following operations.

[0139] refer to Figure 8C In block 842 of method 840, the mobile device may operate in the write-only interaction state according to any of the methods discussed above (e.g., methods 800, 820, etc.). In block 844, after entering the write-only interaction state, the mobile device may monitor the mobile device system to detect actuation of a physical or virtual button on the mobile device, activation of a stylus or other connected device, a voice command, or other appropriately designated user input indicating that the mobile device should operate in the write-only interaction state, that the user has finished entering notes on the mobile device, or that the notes should be otherwise saved or deleted.

[0140] In determination block 846, while operating in the write-only interaction state, the mobile device may determine whether appropriate designated user input has been received on the mobile device. In response to determining that appropriate designated user input has not been received (i.e., determination block 846 = "No"), the mobile device may continue to operate in the write-only interaction state in block 842 according to any of the methods discussed above (e.g., methods 800, 820, etc.).

[0141] In response to determining that the appropriate specified user input has been received (ie, determination block 846 =“Yes”), the mobile device may exit the write-only interaction state in block 848 .

[0142] refer to Fig.8D In block 842 of method 860, the mobile device may operate in a write-only interaction state according to any of the methods 800, 820, or 840. In block 864, the mobile device may restart the inactivity timer after each user input.

[0143] In determination block 866, the mobile device may determine whether the inactivity timer meets a threshold. Such a threshold may be defined by the user and corresponds to an amount of time consistent with the user completing the input note. For example, the threshold may be between 10 seconds and 1 minute.

[0144] In response to determining that the inactivity timer does not meet the threshold (ie, determination block 866 = "No"), the mobile device may continue to operate the device in the write-only interaction state in block 842, restarting the inactivity timer in block 864 whenever user input is received.

[0145] In response to determining that the inactivity timer meets the threshold (i.e., determination block 866 = "Yes"), the mobile device may exit the write-only interaction state in block 848. In other words, once the user has stopped inputting (e.g., typing, writing with a stylus, etc.) for a period of time consistent with the user completing input (i.e., the threshold), the mobile device may exit the write-only interaction state, e.g., return to lock screen mode.

[0146] refer to Fig. 8E In block 842 of method 880, the mobile device may operate in a write-only interactive state according to any of the methods 800, 820, 840, or 860. In block 886, the mobile device may determine whether the user input satisfies a threshold. For example, the threshold may be a maximum number of letters or words for a write-only interactive function. As another example, the threshold may be a maximum time allowed to use the write-only interactive state. Other types of thresholds and values ​​of the thresholds may be user configurable.

[0147] In response to determining that the user input does not satisfy the threshold (ie, determination block 886 = "No"), in block 842 the mobile device may continue to operate in the write-only interaction state.

[0148] In response to determining that the user input satisfies the threshold (ie, determination block 886 =“Yes”), the mobile device may exit the write-only interaction state in block 848 .

[0149] In some embodiments, the mobile device may be configured to perform operations to authenticate a user while the mobile device is operating in a write-only interactive state. For example, the mobile device may display a lock screen and operate in a write-only interactive state, begin presenting user input in a user input area at the top of the lock screen for a period of time, store the user input in a secure file using write-only access, perform a facial recognition operation (or other similar operation) to authenticate the user while the user continues to verify input, unlock the mobile device based on the user authentication, and continue to present the user input at the top of the lock screen or at the top of a subsequent screen for a period of time or until the user stops entering information or becomes inactive. The mobile device may store user input of limited information received by the mobile device in a read-only interactive state for a predetermined duration in a single secure file.

[0150] Fig. 9A and 9B Methods 900, 920 of authenticating a user when a mobile device is operating in a write-only interaction state are shown according to some embodiments. Figures 1 to 9B The operations of methods 900 and 920 may be performed or implemented in hardware components and / or software components of a mobile device (e.g., mobile device 100, mobile device 202, etc.), the operations of which may be controlled by one or more processors (e.g., processors 106, 116, etc.).

[0151] refer to Fig. 9A In block 902 of method 900, the mobile device may display a lock screen (or other type of screen not associated with a note-taking application) on an electronic display of the mobile device and operate the mobile device in a write-only interaction state.

[0152] In block 904 , the mobile device may begin presenting user input in a user input area on top of the lock screen for a period of time and store the user input in a secure file using write-only access.

[0153] In block 906 , as the user continues to provide input, the mobile device may authenticate the user (eg, by performing facial recognition operations, collecting and analyzing fingerprints, etc.).

[0154] In box 908, the mobile device can unlock the mobile device (in response to authenticating the user in box 906), and in box 910, continue to present user input on top of the lock screen (or the top of a subsequent screen) for a period of time or until the user becomes inactive.

[0155] In block 912, the mobile device may store user input of limited information received by the mobile device in a write-only interaction state for a predefined duration.

[0156] refer to Fig. 9BIn blocks 902-906 of method 920, the mobile device may perform operations of the same numbered blocks of method 900. In block 922, the mobile device may change the presentation of a closed lock to an open lock, and continue to display the lock screen (or unlock screen) until the user performs an appropriate input gesture (e.g., swipe up, left, or right). In block 924, the mobile device may continue to display the lock screen (or lock to unlock transition screen) until the user performs an appropriate input gesture, such as swiping up or swiping left or right.

[0157] In block 926, the mobile device may continue to allow the user to write on the lock screen (or on the lock to unlock transition screen) before the user performs an appropriate input gesture (e.g., swipe up, left, or right to enter the home screen). Thus, a mobile device configured in accordance with some embodiments may enable the user to write on the lock-unlock transition screen before the user performs an appropriate input gesture (e.g., swipe up, left, or right to enter the home screen).

[0158] As described above, some screens (e.g., lock screen, home screen, etc.) may display notifications (or pop-up messages or interfaces presented on top of another screen, etc.) notifying the user of incoming emails, texts, etc. In some embodiments, the mobile device may be configured to allow the user to write notes or add tags directly to the notification (or pop-up message, etc.) or on top of it. For example, the mobile device may be configured to start operating and / or presenting a soft keyboard in a write-only interactive state in response to detecting a user touch on a notification message. The mobile device may capture and present user input on top of the notification and store the user input in a note-taking file using write-only access. The mobile device may stop receiving user input or presenting user input on top of the notification message in response to expiration of a time period, in response to detecting user inactivity, in response to determining that the notification has been closed, in response to determining that the notification display period has expired, etc. When the user is authenticated and the mobile device exits the screen lock state (or other screens or states as described herein), the mobile device may store the user input in the note-taking file and / or store the note-taking file in a more permanent file. The user input / file may be stored in association with or without a notification and / or in association with or without a software application corresponding to the notification. The mobile device may also use the user input or the contents of a note or more permanent file to invoke a feature or function on the mobile device. For example, as described in more detail below, in some embodiments, the mobile device may be configured to generate a draft reply email message based on user input added directly to or on top of a displayed notification (such as an incoming email notification).

[0159] In some embodiments, the mobile device may be configured to allow the user to select a notification and allow the selected notification to be associated with user input received anywhere on the screen (e.g., above the notification, below the notification, to the side of the notification, etc.). For example, the mobile device may be configured to begin operating in a write-only interactive state and / or present a soft keyboard in response to determining that the user has touched an area on the display screen while displaying a notification. The mobile device may present the user input in a user input area (e.g., an area on the screen touched by the user, etc.), and / or store the received input in a note-taking file. The mobile device may stop receiving, presenting, or storing user input in response to detecting a cancellation of a notification message, in response to determining that the notification has been closed, in response to an expiration of the notification display period, in response to expiration of the time period, in response to detecting user inactivity, etc. The mobile device may store the user input in a note-taking file, and / or store the note-taking file in a more permanent file that is accessible only when the user is authenticated and the mobile device exits a screen lock state (or other screens or states described herein). The mobile device may also use the user input or the content of the note-taking file or a more permanent file to invoke features or functions on the mobile device. For example, as described in more detail below, in some embodiments, the mobile device can be configured to generate a draft reply email message based on user input added directly to or on top of a displayed notification (e.g., an incoming email notification).

[0160] In some embodiments, the mobile device may be configured to store the user input, a note save file, or a more permanent file (or a reference thereto, etc.) in association with the notification message.

[0161] In some embodiments, the mobile device may be configured to store user input, note save files, or more permanent files in association with a software application (eg, a note taking application, etc.).

[0162] In some embodiments, the mobile device may be configured to store user input, a note save file, a more permanent file, etc. directly within the software application corresponding to the notification. For example, in response to an email notification, the mobile device may cause the corresponding email software application to generate a draft reply message, populate the body of the draft reply message based on the user input or the content of the note save file, and store the draft reply message in a "Drafts" or "Saved" mailbox of the email software application. In some embodiments (e.g., embodiments where the notification is presented on a lock screen or when the device is in a screen lock state, etc.), the mobile device may store the user input or note save file (or reply email message, reply text, etc.) in memory until (at least) the device exits the lock screen and / or exits the screen lock state.

[0163] In some embodiments, the mobile device may be configured to automatically invoke a feature of a software application corresponding to the notification when the device exits a lock screen or screen lock state. For example, when the mobile device exits a lock screen or screen lock state, the mobile device may automatically send a reply email generated based on the user input received at the top of the email notification. As another example, the mobile device may be configured to open an email application and notify the user that the email is ready for viewing when the device exits a lock screen or screen lock state. In this example, the email may not be sent until the user opens the email application, retrieves the draft email, and then clicks a send button.

[0164] In some embodiments, the mobile device can be configured to display a pop-up window or user input dialog box to request the user to confirm whether a feature of the software application corresponding to the notification or user input should be invoked. For example, in response to the device exiting a lock screen or screen lock state (or any appropriate time thereafter), the mobile device can prompt the user to confirm whether a reply email message generated based on the user input received at the top of the email notification message should be sent (and / or whether an email application should be opened). The mobile device can send the reply email in response to the user confirming that the email is to be sent. The mobile device can also allow the user to discard or further edit the draft reply email (e.g., in response to the user not confirming that the draft email is to be sent, etc.).

[0165] In some embodiments, the mobile device can be configured to store user input, note save files, and / or more permanent files, and contextual information about the notification or about the software application corresponding to the notification. For example, the mobile device can store text entered by the user and information such as "email from John Smith." As another example, the mobile device can store user input and a screenshot or other representation of the notification (e.g., presenting the notification or the content of the notification) that provides context to the user or software application (e.g., a note is entered in response to a notification of a text message received from John Smith, etc.).

[0166] In some embodiments, the mobile device may allow a user to write or provide input on a notification or widget associated with a software application, generate a note save file or more permanent file for the associated software application, and / or cause the software application to perform a task or take a responsive action based on the notification or user input. For example, in response to receiving an email notification, the mobile device may create a draft email, use the writing smart widget and / or user input to populate the draft email with text or content, and cause the software application to store and / or send the draft email.

[0167] In some embodiments, the mobile device may be configured to store user input or a note save file (or a portion of a notification selected by the user) in a paste buffer or clipboard file. The clipboard may be a portion of a buffer or memory that is provided by the operating system of the mobile device and used for short-term storage and / or transmission of information within and between software applications. The mobile device may store user input or a note save file in a clipboard to supplement or replace a more permanent memory. For example, in addition to or in lieu of storing user input in a single secure file, the mobile device may store user input of limited information received by the mobile device in a write-only interactive state in a paste buffer or clipboard. In response to determining that the device exits a screen lock state and / or locks the screen, the mobile device may provide the user with the option of pasting the contents of the clipboard into a note-taking application (or other associated software application). In some embodiments, each "note" added to the clipboard may replace the last "note" stored in the clipboard. In some embodiments, the clipboard may store multiple notes, and functionality may enable the user to later select one or more notes from the multiple notes to paste into a document or application (e.g., an email application). In some embodiments, the mobile device may be configured to store only the last X clips / notes. In some cases, after X number of clips / notes were saved to the clipboard, the oldest stored note might be replaced as each new note was added.

[0168] As described above, the mobile device can be configured to allow the user to provide user input directly to or on top of the notification (e.g., write notes and / or add tags), and use the user input to invoke features or functions on the mobile device. In some embodiments, the notification can be displayed on the lock screen. In other embodiments, the notification (e.g., a slide-in banner, a pop-up notification, etc.) can be received while the device is in use (e.g., on the home screen or in another application). Thus, when using the mobile device in the current application when a banner alert notification corresponding to an email appears, the user can write directly on the notification without opening the application associated with the notification, opening the input interface, and / or ending or pausing the current application.

[0169] That is, in some embodiments, the mobile device may be configured to open a keyboard interface in response to detecting a user input / gesture (e.g., a user swiping down, etc.) associated with a particular displayed notification (e.g., a text banner alert). The mobile device may allow a user to respond to a notification (e.g., type a response message, etc.) without having to open a software application corresponding to the notification (e.g., a messaging application corresponding to a text banner alert, etc.). In the case of a physical keyboard connected (e.g., a Bluetooth keyboard, a built-in keyboard, etc.), the user may respond similarly without having to open a software application corresponding to the notification (e.g., a messaging application corresponding to a text banner alert, etc.). In an embodiment using writing input, the user may respond similarly without having to open a software application corresponding to the notification (e.g., a messaging application corresponding to a text banner alert, etc.). In addition to and independently of these features, a mobile device configured in accordance with some embodiments may allow a user to enter information directly on a notification, and store user input associated or unassociated with a notification or a software application corresponding to the notification.

[0170] In some embodiments, the mobile device may be configured to store only the user input in a note save file or a more permanent file (converted or original text). In some embodiments, the mobile device may be configured to store all or part of the notification along with the user input in a note save file or a more permanent file. Storing all or part of the notification may provide the user with context for the user input stored in the note save file, thereby enabling the user to make a very brief or cryptic note (e.g., "no" or "yes") and subsequently be able to recall the intent based on the context provided by the notification prompting the brief user note.

[0171] In some embodiments, the mobile device can be configured to highlight or annotate notifications. For example, the mobile device can be configured to allow the user to underline or highlight specific words in an email / text notification or other notification, and store the underlined or highlighted portion of the notification. This can allow the user to review the notification later and follow the annotation.

[0172] In some embodiments, the mobile device may be configured to use annotations to cause or invoke corresponding actions. For example, if a mobile device user receives a notification that he has a meeting at 1:00 p.m., he may write "2:30" on the notification to cause the mobile device to automatically take action to change the meeting time, such as changing the appointment time in a calendar application, notifying other participants (e.g., via an email application), etc. As another example, the mobile device user may write on the notification: "Will be 10 minutes late," which may cause the mobile device to send a message (e.g., in text form and / or written form) with these words to other meeting participants. In various embodiments, the sent message may be converted or translated into other texts. For example, the message may be changed to "arrive in 10 minutes," or translated into a different language suitable for the message recipient (one of the meeting participants).

[0173] As described above, the mobile device can be configured to store the user input in the note-taking file and / or store the note-taking file in a more permanent file when the user is authenticated and the mobile device exits the screen lock state (or other screens or states as described herein). Also as described above, the user input / file can be stored in association with or without the notification and / or in association with the software application corresponding to the notification or not. In some embodiments, the user input / file can be stored in association with a software application that does not directly correspond to the notification. For example, the mobile device can be configured to display a notification of an incoming call (e.g., a banner alert), start operating and / or presenting a soft keyboard in a write-only interactive state in response to detecting a user touch on the notification, and receive and present user input (e.g., "can't talk now", "call you right away", etc.) at the top of the notification. The user input can be converted text and / or raw input (e.g., an image showing what is written), which can be captured and saved as discussed in this application. In some embodiments, the mobile device can allow the user to write directly on the incoming call screen.

[0174] In some embodiments, the mobile device can be configured to store all or part of the text / information included in the notification as user input (e.g., text in an email notification), such as in a manner similar to a copy and paste function. The mobile device can store the "copied" text in the clipboard described above.

[0175] Fig.10 A method 100 of capturing a note on or in association with a notification message (eg, a banner) and saving the user input or note with the notification message or an application associated with the notification is shown in accordance with some embodiments. Figures 1 to 10The operations of method 1000 may be performed or implemented in hardware components and / or software components of a mobile device (eg, mobile device 100, mobile device 202, etc.), the operations of which may be controlled by one or more processors (eg, processors 106, 116, etc.).

[0176] In block 1002 of method 1000, the mobile device may detect the presence of a notification on the mobile device, such as on a screen (e.g., a lock screen, a home screen, etc.) and / or on an electronic display of the mobile device. As an example, if an application running in the background generates an announcement banner that is presented on a screen presented by an active application, the mobile device may detect the event. In some embodiments, detecting the presence of a notification may include detecting an audible notification.

[0177] In box 1004, the mobile device may enable a write-on-notification feature to enable a user to provide input (e.g., a note or highlight) related to the notification. In some embodiments, the write-on-notification feature may be active before the notification is detected and used to enable the user to provide input related to the notification. In some embodiments, the write-on-notification feature may be active in the background before the notification is detected and, in response to the detection in box 1002, may be presented in the foreground to enable the user to provide input related to the notification. In some embodiments, the write-on-notification feature may be inactive before the notification is detected and, in response to the detection in box 1002, the mobile device may activate the feature to enable the user to provide input related to the notification. In some embodiments, the write-on-notification feature may be associated with the application that is generating the notification and provide the user with the ability to input on or about the notification as part of generating the notification. In some embodiments, the write-on-notification feature may be separate from the application (i.e., a different software application) that generates the notification, but is triggered or activated by the application when the notification is generated. In some embodiments, the file may be associated with an application different from the application currently being used (e.g., when the notification appears in the display screen of the first application). In some embodiments, activating the write on notification functionality may include activating an instant type function and / or presenting a soft keyboard, which may include presenting an input window on or near the notification. In some embodiments, the write on notification functionality may be a subset of the functionality available / provided when the mobile device is operating in a write-only interaction state, which provides write-only access to secure files on the mobile device and allows a user to enter limited information stored in the secure file, as described above. In some embodiments, the write on notification functionality may be independent, separate from, or distinct from the write-only interaction state discussed above.

[0178] In box 1006, the mobile device can receive user input. In some embodiments, the write on notification function can be configured to receive user input from an electronic pen or stylus. For example, the write on notification function can enable a user to use an electronic pen or stylus to write notes, mark, cross out or underline a portion of a notification presented on an electronic display. In some embodiments, the write on notification function can present a key area for entering text, receive text input from the user on the presented key area, and present the input made at a location on the screen, such as on or near the notification, or at a location indicated or touched by the user. The user input can also be an audio recording or voice input received via a microphone, or any other form of user input discussed in this application.

[0179] In box 1008, the mobile device may save the received user input in a file or other file or memory system. In some embodiments, the file may be associated with the notification. In some embodiments, the file may be associated with the application that generated the notification (e.g., stored as a file in the application or application folder). For example, when the announcement is a banner indicating that an email has been received, the mobile device may save the user input in a file accessible to the email application, so that the user can reference or edit the stored input when the email application is activated. As another example, when the notification is generated by a calendar application, the mobile device may save the user input in a file accessible in the calendar application. As another example, when the announcement is associated with an application or function that does not receive user input (such as a news feed application), the mobile device may save the user input in a note-taking file, a more permanent file, a clipboard, or any other file or memory system.

[0180] In box 1010, the mobile device may provide user access to the file. In some embodiments, the mobile device may provide user access to the file when the application associated with the notification is activated. For example, when the user begins to use the application or function associated with the notification detected in box 1002, the mobile device may provide the user with access to the file when a note-taking application, an email application, etc. are activated. In some embodiments, the mobile device may provide user access to the file when a note-taking or word processor application is activated. In some embodiments, the mobile device may provide user access to the file in response to the user's authentication and / or the mobile device being unlocked. In some embodiments, the mobile device may provide user access to the file in response to the presentation of a specific screen on the display, such as a home screen, the presentation of a previously presented notification (which may be presented on the home screen), the home screen of a specific application, etc.

[0181] Various embodiments (including but not limited to the above reference Figures 1 to 10The described embodiments) may be implemented in various mobile devices including wireless communication devices, Fig.11 Examples suitable for use with various embodiments are shown in . The mobile device 1100 may include a processor 1102 coupled to a touch screen controller 1104 and an internal memory 1106. The processor 1102 may be one or more multi-core integrated circuits designated for general or specific processing tasks. The internal memory 1106 may be volatile or non-volatile memory, and may also be secure and / or encrypted memory, or unsecure and / or unencrypted memory, or any combination thereof. The touch screen controller 1104 and the processor 1102 may also be coupled to a touch screen panel 1112, such as a resistive sensing touch screen, a capacitive sensing touch screen, an infrared sensing touch pad, or the like. In addition, the display of the computing device 1100 need not have touch screen capabilities.

[0182] The mobile device 1100 may have one or more radio signal transceivers 1108 (e.g., Peanut, Bluetooth, ZigBee, Wi-Fi, RF radios) and antennas 1110 for sending and receiving communications coupled to each other and / or to the processor 1102. The transceiver 1108 and antenna 1110 may be used with the circuits described above to implement various wireless transmission protocol stacks and interfaces. The mobile device 1100 may include a cellular network wireless modem chip 1116 that is capable of communicating via a cellular network and is coupled to the processor.

[0183] The mobile device 1100 may have one or more radio signal transceivers 1108 (e.g., Peanut, Bluetooth, ZigBee, Wi-Fi, RF radios) and antennas 1110 for sending and receiving communications coupled to each other and / or to the processor 1102. The transceiver 1108 and antenna 1110 may be used with the circuits described above to implement various wireless transmission protocol stacks and interfaces. The mobile device 1100 may include a cellular network wireless modem chip 1116 capable of communicating via a cellular network and coupled to the processor.

[0184] The mobile device 1100 may include a peripheral device connection interface 1118 coupled to the processor 1102. The peripheral device connection interface 1118 may be configured solely to accept one type of connection, or may be configured to accept various types of physical and communication connections, public or proprietary, such as Universal Serial Bus (USB), FireWire, Thunderbolt, or PCIe. The peripheral device connection interface 1118 may also be coupled to a similarly configured peripheral device connection port (not shown).

[0185] The mobile device 1100 may also include a speaker 1114 for providing audio output. The mobile device 1100 may also include a housing 1120 constructed of plastic, metal, or a combination of materials for housing all or part of the components described herein. The mobile device 1100 may include a power source 1122, such as a disposable or rechargeable battery, coupled to the processor 1102. The rechargeable battery may also be coupled to a peripheral device connection port to receive a charging current from a source external to the wireless communication device 1100. The mobile device 1100 may also include a physical button 1124 for receiving user input. The mobile device 1100 may also include a power button 1126 for turning the mobile device 1100 on and off.

[0186] As used in this application, the terms "component", "module", "system", "engine", "generator", "manager", etc. are intended to include computer-related entities, such as but not limited to hardware, firmware, a combination of hardware and software, software, or software in execution, which is configured to perform a specific operation or function. For example, a component can be but not limited to a process, a processor, an object, an executable file, an execution thread, a program, and / or a computer running on a processor. As an example, two applications running on a mobile device can be referred to as components. One or more components can reside within a process and / or an execution thread, and a component can be located on a processor or core and / or distributed between two or more processors or cores. In addition, these components can be executed from various non-temporary computer-readable media on which various instructions and / or data structures are stored. Components can communicate through local and / or remote processing, function or program calls, electronic signals, data packets, memory read / write, and other known network, computer, processor, and / or process-related communication methods.

[0187] Many different types of memory and memory technologies are available or expected in the future, any or all of which may be included and used in systems and mobile devices implementing various embodiments. Such memory technologies / types may include non-volatile random access memory (NVRAM), such as magnetoresistive RAM (M-RAM), resistive random access memory (ReRAM or RRAM), phase change random access memory (PRAM, PC-RAM or PCM), ferroelectric RAM (F-RAM), spin transfer torque magnetoresistive random access memory (STT-MRAM) and three-dimensional crosspoint (3D-XPOINT) memory. Such memory technologies / types may also include non-volatile or read-only memory (ROM) technologies, such as programmable read-only memory (PROM), field programmable read-only memory (FPROM), one-time programmable non-volatile memory (OTP NVM). Such memory technologies / types may also include volatile random access memory (RAM) technologies, such as dynamic random access memory (DRAM), double data rate (DDR) synchronous dynamic random access memory (DDR SDRAM), static random access memory (SRAM) and pseudo-static random access memory (PSRAM). Systems and mobile devices implementing various embodiments may also include or use electronic (solid-state) non-volatile computer storage media, such as flash memory. Each of the above memory technologies includes, for example, elements suitable for storing instructions, programs, control signals, and / or data for use in or by a computer or other digital electronic device. Any reference to terminology and / or technical details related to a single type of memory, interface, standard, or memory technology is for illustrative purposes only and is not intended to limit the scope of the claims to a particular memory system or technology, unless specifically stated in the claim language.

[0188] Computer program code or "program code" for execution on a programmable processor to perform the operations of various embodiments may be written in a high-level programming language such as C, C++, C#, Smalltalk, Java, JavaScript, Visual Basic, Structured Query Language (e.g., Transact-SQL), Perl, or various other programming languages. Program code or programs stored on a computer-readable storage medium used in the present application may refer to machine language code (such as object code) in a format that can be understood by a processor.

[0189] The above method descriptions and process flow charts are provided only as illustrative examples and are not intended to require or imply that the operations of the various embodiments must be performed in the order presented. Those skilled in the art will appreciate that the order of operations in the foregoing embodiments may be performed in any order. Words such as "thereafter," "then," "next," and the like are not intended to limit the order of operations; these words are simply used to guide the reader through the description of the method. In addition, any reference to a claim element in the singular form, for example, the use of "a," "an," or "the" shall not be construed as limiting the element to the singular form.

[0190] The various illustrative logic blocks, modules, circuits, and algorithmic operations described in conjunction with the various embodiments may be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and operations have been generally described above with respect to their functionality. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. A skilled person may implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the claims.

[0191] Hardware for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the various embodiments disclosed herein may be implemented or executed with a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. Such components may be included in a system on a chip (SOC) or a system in a package (SIP). Alternatively, certain operations or methods may be performed by circuits specific to a given function.

[0192] In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a non-transitory computer-readable medium or a non-transitory processor-readable medium. The operation of the method or algorithm disclosed herein may be embodied in a processor-executable software module, which may reside on a non-transitory computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable storage medium may be any storage medium that can be accessed by a computer or processor. As an example but not limited to, such a non-transitory computer-readable or processor-readable medium may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks generally reproduce data magnetically and optical disks reproduce data optically with lasers. The above combinations are also included within the scope of non-transitory computer-readable and processor-readable media. Furthermore, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transitory processor-readable medium and / or computer-readable medium, which may be incorporated into a computer program product.

[0193] The foregoing description of the disclosed embodiments is provided to enable those skilled in the art to make or use the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and implementations without departing from the scope of the claims. Therefore, the present disclosure is not intended to be limited to the various embodiments and implementations described herein, but is to be accorded the widest scope consistent with the appended claims and the principles and novel features disclosed herein.

Claims

1. A method for capturing notes on a mobile device, comprising: displaying a lock screen on an electronic display of the mobile device and operating the mobile device in a write-only interaction state that provides write-only access to a secure file on the mobile device and allows a user to enter limited information stored in the secure file; presenting user input in a user input area at the top of the lock screen for a period of time, and storing the user input in a secure file with write-only access; ceasing to receive and present user input in response to expiration of the time period or in response to detecting user inactivity; as well as storing in a single secure file limited information user input received by the mobile device in a write-only interactive state for a first predetermined duration, Wherein, the method further comprises: determining a number of user inputs received and presented on top of the lock screen within a second predetermined duration and comparing it to a threshold amount; A user authentication operation is triggered in response to determining that the number of user inputs received and presented on top of the lock screen satisfies the threshold amount.

2. The method according to claim 1, further comprising: In response to the mobile device authenticating the user and exiting a lock screen state, the contents of the secure file are stored in a note-taking application operating on the mobile device.

3. The method according to claim 2, further comprising: Prevents a user from viewing, accessing, deleting, or editing secure files until the mobile device authenticates the user.

4. The method according to claim 1, further comprising: monitoring sensors of the mobile device while in lock screen mode to determine whether a user has picked up the mobile device or otherwise attempted to interact with the mobile device; as well as In response to the mobile device determining that the user has picked up the mobile device or otherwise attempted to interact with the mobile device, a lock screen is displayed on an electronic display of the mobile device, and the mobile device is operated in a write-only interaction state.

5. The method according to claim 4, further comprising: In response to determining that the user has picked up the mobile device or otherwise attempted to interact with the mobile device, a keypad is presented on an electronic display of the mobile device.

6. The method according to claim 5, wherein: Presenting user input in a user input area at the top of the lock screen for the time period and storing the user input in a secure file with write-only access comprises: The user's text input on the presented keypad is presented on the lock screen at the location of the user's first touch.

7. The method according to claim 1, wherein: The first predetermined duration and the time period are the same.

8. The method according to claim 1, further comprising: storing the contents of a plurality of individual secure files in a note-taking application operating on a mobile device; as well as Autonomously organize multiple single secure files locally on a mobile device or remotely via the cloud or communication network.

9. A mobile device, comprising: monitor; as well as a processor coupled to the display and configured with processor-executable instructions to: displaying a lock screen on a display of the mobile device and operating the mobile device in a write-only interactive state that provides write-only access to a secure file on the mobile device and allows a user to enter limited information stored in the secure file; presenting user input in a user input area at the top of the lock screen for a period of time, and storing the user input in a secure file with write-only access; ceasing to receive and present user input in response to expiration of the time period or in response to detecting user inactivity; as well as storing in a single secure file limited information user input received by the mobile device in a write-only interactive state for a first predetermined duration, The processor is further configured with processor executable instructions to: determining a number of user inputs received and presented on top of the lock screen within a second predetermined duration and comparing it to a threshold amount; A triggering user authentication operation is initiated in response to determining that the number of user inputs received and presented on top of the lock screen satisfies the threshold amount.

10. The mobile device according to claim 9, wherein: The processor is also configured with processor executable instructions to: In response to the mobile device authenticating the user and exiting a lock screen state, the contents of the secure file are stored in a note-taking application operating on the mobile device.

11. The mobile device according to claim 10, wherein: The processor is also configured with processor executable instructions to: Prevents a user from viewing, accessing, deleting, or editing secure files until the mobile device authenticates the user.

12. The mobile device according to claim 9, wherein: The processor is also configured with processor executable instructions to: monitoring sensors of the mobile device while in lock screen mode to determine whether a user has picked up the mobile device or otherwise attempted to interact with the mobile device; as well as In response to the mobile device determining that the user has picked up the mobile device or otherwise attempted to interact with the mobile device, a lock screen is displayed on an electronic display of the mobile terminal and the mobile device is operated in a write-only interaction state.

13. The mobile device according to claim 12, wherein: The processor is also configured with processor executable instructions to: In response to determining that the user has picked up the mobile device or otherwise attempted to interact with the mobile device, a keypad is presented on an electronic display of the mobile device.

14. The mobile device according to claim 13, wherein: The processor is also configured with processor executable instructions to: Presenting user input in the user input area at the top of the lock screen for the time period and storing the user input in the secure file using write-only access is performed by presenting user text input on a presented keypad at a location of the user's first touch on the lock screen.

15. The mobile device according to claim 9, wherein: The first predetermined duration and the time period are the same.

16. The mobile device according to claim 9, wherein: The processor is also configured with processor executable instructions to: storing the contents of the plurality of individual secure files in a note-taking application operating on the mobile device; and Autonomously organize multiple single secure files locally on a mobile device or remotely via the cloud or communication network.

17. A mobile device comprising: means for displaying a lock screen and operating the mobile device in a write-only interactive state that provides write-only access to secure files on the mobile device and allows a user to enter limited information stored in the secure files; means for presenting user input in a user input area at the top of the lock screen for a period of time and storing the user input in a secure file with write-only access; means for ceasing to receive and present user input in response to expiration of the time period or in response to detecting user inactivity; means for storing in a single secure file limited information user input received by a mobile device in a write-only interactive state for a first predetermined duration; means for determining a quantity of user input received and presented on top of the lock screen within a second predetermined duration and comparing it to a threshold amount; as well as Means for triggering a user authentication operation in response to determining that the number of user inputs received and presented on top of the lock screen satisfies the threshold amount.

18. The mobile device of claim 17, further comprising: Means for storing contents of a secure file in a note-taking application operating on the mobile device in response to the mobile device authenticating the user and exiting a lock screen state.

19. The mobile device of claim 18, further comprising: Means for preventing a user from viewing, accessing, deleting or editing a secure file until a mobile device authenticates the user.

20. The mobile device of claim 17, further comprising: means for monitoring a sensor of a mobile device in a lock screen mode to determine whether a user has picked up the mobile device or otherwise attempted to interact with the mobile device; as well as Means for displaying a lock screen on an electronic display of a mobile terminal and operating the mobile device in a write-only interaction state in response to the mobile device determining that a user has picked up the mobile device or otherwise attempted to interact with the mobile device.

21. The mobile device of claim 20, further comprising: Means for presenting a keypad on an electronic display of a mobile device in response to determining that a user has picked up the mobile device or otherwise attempted to interact with the mobile device.

22. The mobile device according to claim 21, wherein: Means for presenting user input in a user input area at the top of the lock screen within the time period and storing the user input in a secure file using write-only access include means for presenting user text input on a presented key area at the location of the user's first touch on the lock screen.

23. The mobile device of claim 17, wherein: The first predetermined duration and the time period are the same.

24. The mobile device of claim 17, further comprising: means for storing the contents of a plurality of individual secure files in a note-taking application operating on a mobile device; as well as Means for autonomously organizing multiple individual secure files locally on a mobile device or remotely via a cloud or communications network.

Images