Companion conversational robot or digital companion for use with multiple users and methods of using same

Abstract

A method for multiple users to interact with a robot computing device, including computer-readable instructions, the computer-readable instructions executable by the one or more processors to communicate resource owner registration parameters to a cloud computing device to identify a resource owner to control communication between a robot computing device and a plurality of users; communicate registration instructions to a cloud computing device to register a first user to interface with a robot computing device; transmit first user robot communication parameters to the cloud computing device to identify preferences with respect to the first user in interfacing with the robot computing device; communicate registration instructions to the cloud computing device to register a second user to interface with the robot computing device; and transmit second user robot communication parameters to the cloud computing device to identify preferences with respect to the second user in interfacing with the robot computing device

Description

COMPANION CONVERSATIONAL ROBOT OR DIGITAL COMPANION FOR USE WITH MULTIPLE USERS AND METHODS OF USING SAMERELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application Serial No. 63 / 464,591, filed May 7, 2023, entitled Companion Conversational Robot Or Digital Companion For Use With Multiple Users And Methods Of Using Same and U.S. Provisional Patent Application Serial No. 63 / 642,854, filed May 5, 2024, entitled Companion Conversational Robot Or Digital Companion For Use With Multiple Users And Methods Of Using Same, the entirety of which are both incorporated by reference.BACKGROUND

[0002] Conversational robots are normally purchased to be utilized with one individual or one family at a time. Educators and / or clinical professionals would like to utilize conversational robots with one or more students and / or patients and this would require that one conversational robot be utilized with multiple students and / or patients. However, due to privacy concerns, user interface and / or software limitations, educators or clinical professionals are not able to use the conversational robots with multiple children while keeping the data private from each other. Accordingly, a need exists for conversational robots that educators or clinical professionals may utilize to interact and communicate with multiple students or patients during a same timeframe (e.g., not in the same session or visit but over a year timeframe).BRIEF DESCRIPTION OF THE DRAWINGS

[0003] A better understanding of the features, advantages and principles of the present disclosure will be obtained by reference to the following detailed description that sets forth illustrative embodiments, and the accompanying drawings of which:

[0004] Figure 1 A illustrates for a system for a social or conversational robot, digital companion or robot computing device to engage with and / or communicate with a parent according to some embodiments;

[0005] Figure IB illustrates an outline of a conversation robot or robot computing device according to some embodiments;

[0006] FigurelC illustrates a block diagram of subsystems and / or software modules for a social robot, digital companion or robot computing device to engage a child and / or a parent;

[0007] Figure 2 is a diagram depicting system architecture of robot computing device or robot (e.g., 105 of Figure IB), according to implementations;1SUBSTITUTE SHEET (RULE 26)

[0008] Figure 3 illustrates a robot computing device that may be utilized for multiple users according to some implementations;

[0009] Figure 4A illustrates a flowchart for initializing a robot computing device for use with multiple users utilizing the resource owner software application according to some embodiments;

[0010] Figure 4B illustrates a flowchart of a user or patient registration process according to some embodiments;

[0011] Figure 5 A illustrates a resource owner registering additional users according to some embodiments;

[0012] FIG. 6A illustrates an introductory screen according to exemplary embodiments, FIG. 6B illustrates a second introductory screen according to exemplary embodiments and FIG. 6C illustrates a getting started screen according to exemplary embodiments. FIG. 6D illustrates a login screen for a resource owner software application according to exemplary embodiments;

[0013] FIG. 6E illustrates a reminder screen in a resource owner software application according to some embodiments;

[0014] FIG. 6F illustrates an email security code entry screen according to some embodiments. FIG. 6G illustrates an account setup screen according to some embodiments and FIG. 6H illustrates a recovery key setup screen according to some embodiments;

[0015] FIG. 61 illustrates a COPPA certification screen according to exemplary embodiments and FIG. 6J illustrates a private policy summary statement screen according to exemplary embodiments. FIG. 6K illustrates an add child account screen according to exemplary embodiments. FIG. 6L illustrates a resource provider’s verification screen according to exemplary embodiments. FIG. 6M illustrates a resource provider’s identification selection method according to exemplary embodiments.

[0016] FIG. 6N illustrates a resource provider successful sign in screen according to exemplary embodiments. FIG. 60 illustrates a WiFi entry screen in a resource provider software application according to exemplary embodiments. FIG. 6P illustrates a QR code scan screen according to exemplary embodiments. FIG. 6Q illustrates a connecting tips screen according to exemplary embodiments. FIG. 6R illustrates a WiFi connection screen in a resource provider software application according to exemplary embodiments. FIG. 6S illustrates a robot computing device environment setup screen according to exemplary embodiments. FIG. 6T illustrates a setup environment screen according to2SUBSTITUTE SHEET (RULE 26)exemplary embodiments. FIG. 6U illustrates a second setup environment screen according to exemplary embodiments. FIG. 6V illustrates a connection success screen according to exemplary embodiments.

[0017] FIG. 6W illustrates a child information entry screen according to exemplary embodiments. FIG. 6X illustrates a robot computing device appearance customization screen according to exemplary embodiments. FIG. 6Y illustrates a robot computing device user accessibility customization screen according to exemplary embodiments. FIG. 6Z illustrates an add additional user or child input screen according to exemplary embodiments.

[0018] FIG. 7A illustrates a robot computing device ready finalization screen according to exemplary embodiments and FIG. 7B illustrates a robot computing device play initialization screen according to exemplary embodiments. FIG. 7C illustrates an account information screen for resource owner software application according to exemplary embodiments. FIG. 7D illustrates an account status screen or menu for a resource owner software application for robot computing device according to exemplary embodiments.

[0019] FIG. 7E illustrates a deactivate screen or menu according to exemplary embodiments. FIG. 7F illustrates a sign out screen according to exemplary embodiments. FIG. 7G illustrates an activity submenu or screen of an insights tab in a resource owner’s robot software application according to exemplary embodiments. FIG. 7H illustrates a badges submenu or screen of an insights tab in a resource owner’s robot software application according to exemplary embodiments. FIG. 71 illustrates a missions submenu or screen according to exemplary embodiments.

[0020] FIG. 7J illustrates an insights menu for one mentor or user associated with a resource owner according to exemplary embodiments. FIG. 7K illustrates a screen or menu allowing a resource owner to switch between insights report. FIG. 7L illustrates a mentor information selection screen / option according to exemplary embodiments. FIG. 7M illustrates an activity preference screen or menu according to exemplary embodiments. FIG. 7N illustrates a mentor or user’s interest screen. FIG. 70 illustrates an SEL Skills Development selection menu or screen according to exemplary embodiments. FIG. 7P illustrates a robot computing device physical settings menu or screen according to exemplary embodiments. FIG. 7Q illustrates a Moxie Active Menu or screen for a resource owner robot software application according to exemplary embodiments.3SUBSTITUTE SHEET (RULE 26)

[0021] FIG. 7R illustrates a scheduling menu or screen for a user or mentor according ot exemplary embodiments. FIG. 7S illustrates a robot computing device active user menu or screen according to exemplary embodiments. FIG. 7T illustrates a switch active user / child menu or screen according to exemplary embodiments. FIG. 7U illustrates an add or edit user / child menu or screen according to exemplary embodiments. FIG. 7V illustrates an instructions screen of the resource owner robot software application according to exemplary embodiments. FIG. 7W illustrates archived messages for a resource owner and / or children or users according to exemplary embodiments. FIG. 7X illustrates mission set guides for a resource owner’s software application according to exemplary embodiments.

[0022] Figure 8 illustrates a logical representation of accounts in a cloud computing device according to some embodiments;

[0023] Figure 9 A illustrates an overall insight screen or menu according to some implementations.

[0024] Figure 9B illustrates a cognitive insight screen according to some implementations. Figure 9C illustrates a social insight screen according to some implementations. Figure 9D illustrates an emotional insight screen according to some implementations.

[0025] FIG. 10A illustrates a resources screen or menu according to exemplary embodiments.

[0026] FIG. 10B illustrates a Moxie or robot computing device commands screen or menu according to embodiments. FIG. 10C illustrates a parent tutorials screen or menu according to embodiments. FIG. 10D illustrates a robot computing devices activities menu according to embodiments. FIG. 10E illustrates a Tips for Success menu or screen according to exemplary embodiments; and

[0027] FIG. 10F illustrates a help screen or menu according to exemplary embodiments.DETAILED DESCRIPTION

[0028] The following detailed description and provides a better understanding of the features and advantages of the inventions described in the present disclosure in accordance with the embodiments disclosed herein. The following detailed description describes a method and system that allows a resource owner to setup accounts and / or4SUBSTITUTE SHEET (RULE 26)collect information for multiple users (who may be patients and / or students) who are using the same robot computing device and may create individual content progression for each user.

[0029] The following detailed description further describes a method and system that stores collected information from interactions between the Moxie Robot and multiple users in separate accounts in a safe and secure manner, which allows the robot to automatically adapt a curriculum or learning path better suited to the needs of each individual user. In other words, personalize a robot computing device’s interaction for each user.

[0030] Figure 1 A illustrates for a system for a social or conversational robot, digital companion or robot computing device to engage with and / or communicate with a parent according to some embodiments. Figure IB illustrates an outline of a conversation robot or robot computing device according to some embodiments. FigurelC illustrates a block diagram of subsystems and / or software modules for a social robot, digital companion or robot computing device to engage a child and / or a parent. In some implementations, a robot computing device 105 (or digital companion) may engage with a child 111 and establish communication interactions with the child 111. In some implementations, there will be bidirectional communication between the robot computing device 105 and the child 111 with a goal of establishing multi-turn conversations (e.g., both parties taking conversation turns) in the communication interactions. In some implementations, the robot computing device 105 may communicate with the child 111 via spoken words (e.g., audio actions,), visual actions (movement of eyes or facial expressions on a display screen), and / or physical actions (e.g., movement of a neck or head or an appendage of a robot computing device). In some implementations, the robot computing device 105 may utilize one or more imaging devices or cameras to evaluate a child's body language, a child's facial expressions and may utilize speech recognition software to evaluate and analyze the child's speech.

[0031] In some implementations, the child 111 may also have one or more associate electronic devices or computing devices 110. In some implementations, the one or more electronic devices 110 may allow a child to login to a website on a server computing device in order to access a learning laboratory and / or to engage in interactive games that are housed on the web site 120. In some implementations, the child's one or more computing devices 110 may communicate with cloud computing devices 115 in order to access the website 120. In alternative embodiments, the child’s computing device 1105SUBSTITUTE SHEET (RULE 26)may communicate with the robot computing device 105 and / or also communicate with a server computing device 120 which houses interactive games and / or a learning library.

[0032] In some implementations, the website 120 may be housed on server computing devices. In some implementations, the website 120 may include the learning laboratory (which may be referred to as a global robotics laboratory (GRL) where a child can interact with digital characters or personas that are associated with the robot computing device 105. In some implementations, the website 120 may include interactive games where the child can engage in competitions or goal setting exercises. In some implementations, there may be other server or cloud computing devices which host a robot computing device manufacturer e-commerce website. The robot computing device does not communicate with the e-commerce website. In some implementation, other users may be able to interface with an e-commerce website or program, where the other users (e.g., parents or guardians) may purchases items that are associated with the robot (e.g., comic books, toys, badges or other affiliate items).

[0033] In some implementations, the system may include a parent computing device 125. In some implementations, the parent computing device 125 may include one or more processors and / or one or more memory devices. In some implementations, computer- readable instructions may be executable by the one or more processors to cause the parent computing device 125 to perform a number of features and / or functions. In some implementations, these features and functions may include generating and running a parent interface for the system. In some implementations, the software executable by the parent computing device 125 may also alter user (e.g., child, parent or guardian) settings. In some implementations, the software executable by the parent computing device 125 may also allow the parent or guardian to manage their own account or their child's account in the system. In some implementations, the software application may be referred to as a parent application or a parent app. In some implementations, the software executable by the parent computing device 125 may allow the parent or guardian to initiate or complete parental consent to allow certain features of the robot computing device to be utilized. In some implementations, the software executable by the parent computing device 125 may allow a parent or guardian to set goals or thresholds or settings what is captured from the robot computing device and what is analyzed and / or utilized by the system. In some implementations, the software executable by the one or more processors of the parent computing device 125 may allow the parent or guardian to view the different analytics generated by the system in order to see how the robot6SUBSTITUTE SHEET (RULE 26)computing device is operating, how their child is progressing against established goals, and / or how the child is interacting with the robot computing device. In some implementations, although the parent application is installed on the parent computing device, some functions of the software may be stored in a cloud computing device which interfaces with the parent application.

[0034] In some implementations, the system may include a cloud server computing device 115. In some implementations, the cloud server computing device 115 may include one or more processors and one or more memory devices. In some implementations, computer-readable instructions may be retrieved from the one or more memory devices and executable by the one or more processors to cause the cloud server computing device 115 to perform calculations and / or additional functions. In some implementations, the software (e.g., the computer-readable instructions executable by the one or more processors) may manage accounts for all the users (e.g., the child, the parent and / or the guardian). In some implementations, the software may also manage the storage of personally identifiable information in the one or more memory devices of the cloud server computing device 115. In some implementations, the software may also execute the audio processing (e.g., speech recognition and / or context recognition) of sound files that are captured from the child, parent or guardian, as well as generating speech and related audio file that may be spoken by the robot computing device 115. In some implementations, the software in the cloud server computing device 115 may perform and / or manage the video processing of images that are received from the robot computing devices and / or the creation of facial expression datapoints. In some implementations, the software in the cloud server computing device 115 may analyze images provided from the robot computing devices to identify a primary user of the robot computing device 105.

[0035] In some implementations, the software of the cloud server computing device 115 may analyze received inputs from the various sensors and / or other input modalities as well as gather information from other software applications as to the child's progress towards achieving set goals. In some implementations, the cloud server computing device 115 software may be executable by the one or more processors in order perform analytics processing. In some implementations, analytics processing may be behavior analysis on how well the child is doing with respect to established goals.

[0036] In some implementations, the software of the cloud server computing device 115 may receive input regarding how the user or child is responding to content, for example, does the child like the story, the augmented content, and / or the output being7SUBSTITUTE SHEET (RULE 26)generated by the one or more output modalities of the robot computing device 105. In some implementations, the cloud server computing device 115 may receive the input regarding the child's response to the content and may perform analytics on how well the content is working and whether or not certain portions of the content may not be working (e.g., perceived as boring or potentially malfunctioning or not working).

[0037] In some implementations, the software of the cloud server computing device 115 may receive inputs such as parameters or measurements from hardware components of the robot computing device 105 such as the sensors, the batteries, the motors, the display and / or other components. In some implementations, the software of the cloud server computing device 115 may receive the parameters and / or measurements from the hardware components and may perform IOT Analytics processing on the received parameters, measurements or data to determine if the robot computing device 105 is malfunctioning and / or not operating at an optimal manner.

[0038] In some implementations, the cloud server computing device 115 may include one or more memory devices. In some implementations, portions of the one or more memory devices may store user data for the various account holders. In some implementations, the user data may be user address, user goals, user details and / or preferences. In some implementations, the user data may be encrypted and / or the storage may be a secure and / or encrypted storage.

[0039] FIG. 1C illustrates functional modules of a system including a robot computing device according to some implementations. In some embodiments, at least one method described herein is performed by a system 300 that includes the conversation system 216, a machine control system 121, a multimodal output system 122, a multimodal perceptual system 123, a testing system 350, and / or an evaluation system 215. In some implementations, at least one of the conversation system 216, a machine control system 121, a multimodal output system 122, a multimodal perceptual system 123, a testing system 350, and / or an evaluation system 215 may be included in a robot computing device or a machine. In some embodiments, the machine is a robot, a robot computing device, a digital companion, and / or computing devices that have facial recognition software, gesture analysis software, speech recognition software, and / or sound recognition software. In the specification, terms such as robot computing device, robot, machine, and / or digital companion may be utilized interchangeably. In the specification, terms such as conversation engine, conversation system, conversation module and / or conversation agent may be utilized interchangeably.8SUBSTITUTE SHEET (RULE 26)

[0040] In some implementations, the conversation system 216 may be communicatively coupled a control system 121 of the machine. In some embodiments, the conversation system may be communicatively coupled to the evaluation system 215. In some implementations, the conversation system 216 may be communicatively coupled to a conversational content repository 220. In some implementations, the conversation system 216 may be communicatively coupled to a conversation testing system 350. In some implementations, the conversation system 216 may be communicatively coupled to a conversation authoring system 141. In some implementations, the conversation system 216 may be communicatively coupled to a goal authoring system 140. In some implementations, the conversation system 216 may be a cloud-based conversation system provided by a conversation system server that is communicatively coupled to the control system 121 via the Internet or other global communications network. In some implementations, the conversation system 216 may be the Embodied Chat Operating System.

[0041] In some implementations, the conversation system 216 may be an embedded conversation system that is included in the robot computing device or implementations. In some implementations, the control system 121 may be constructed to control a multimodal output system 122 and a multimodal perceptual system 123 that includes at least one sensor. In some implementations, the control system 121 may be constructed to interact with the conversation system 216. In some implementations, the machine or robot computing device may include the multimodal output system 122. In some implementations, the multimodal output system 122 may include at least one of an audio output sub-system, a video display sub-system, a mechanical robotic subsystem, a light emission sub-system, a LED (Light Emitting Diode) ring, and / or a LED (Light Emitting Diode) array. In some implementations, the machine or robot computing device may include the multimodal perceptual system 123, wherein the multimodal perceptual system 123 may include the at least one sensor. In some implementations, the multimodal perceptual system 123 includes at least one of a sensor of a heat detection sub-system, a sensor of a video capture sub-system, a sensor of an audio capture sub-system, a touch sensor, a piezoelectric pressor sensor, a capacitive touch sensor, a resistive touch sensor, a blood pressure sensor, a heart rate sensor, and / or a biometric sensor. In some implementations, the multimodal perceptual system 123 may include one or more microphones and / or one or more cameras or imaging devices. In some implementations, the evaluation system 215 may be communicatively coupled to the control system 121. In9SUBSTITUTE SHEET (RULE 26)some implementations, the evaluation system 130 may be communicatively coupled to the multimodal output system 122. In some implementations, the evaluation system 215 may be communicatively coupled to the multimodal perceptual system 123. In some implementations, the evaluation system 215 may be communicatively coupled to the conversation system 216. In some implementations, the evaluation system 215 may be communicatively coupled to a client device 110 (e.g., a parent or guardian’s mobile device or computing device). In some implementations, the evaluation system 215 may be communicatively coupled to the goal authoring system 140. In some implementations, the evaluation system 215 may include computer-readable-instructions of a goal evaluation module that, when executed by the evaluation system, may control the evaluation system 215 to process information generated from the multimodal perceptual system 123 to evaluate a goal associated with conversational content processed by the conversation system 216. In some implementations, the goal evaluation module is generated based on information provided by the goal authoring system 140.

[0042] In some implementations, the goal evaluation module 215 may be generated based on information provided by the conversation authoring system 141. In some embodiments, the goal evaluation module 215 may be generated by an evaluation module generator 142. In some implementations, the conversation testing system may receive user input from a test operator and may provide the control system 121 with multimodal output instructions (either directly or via the conversation system 216). In some implementations, the conversation testing system 350 may receive event information indicating a human response sensed by the machine or robot computing device (either directly from the control system 121 or via the conversation system 216). In some implementations, the conversation authoring system 141 may be constructed to generate conversational content and store the conversational content in one of the content repository 220 or the conversation system 216. In some implementations, responsive to updating of content currently used by the conversation system 216, the conversation system may be constructed to store the updated content at the content repository 220.

[0043] In some embodiments, the goal authoring system 140 may be constructed to generate goal definition information that is used to generate conversational content. In some implementations, the goal authoring system 140 may be constructed to store the generated goal definition information in a goal repository 143. In some implementations, the goal authoring system 140 may be constructed to provide the goal definition information to the conversation authoring system 141. In some implementations, the goal10SUBSTITUTE SHEET (RULE 26)authoring system 143 may provide a goal definition user interface to a client device that includes fields for receiving user-provided goal definition information. In some embodiments, the goal definition information specifies a goal evaluation module that is to be used to evaluate the goal. In some implementations, each goal evaluation module is at least one of a sub -system of the evaluation system 215 and a sub -system of the multimodal perceptual system 123. In some embodiments, each goal evaluation module uses at least one of a sub-system of the evaluation system 215 and a sub-system of the multimodal perceptual system 123. In some implementations, the goal authoring system 140 may be constructed to determine available goal evaluation modules by communicating with the machine or robot computing device, and update the goal definition user interface to display the determined available goal evaluation modules.

[0044] In some implementations, the goal definition information defines goal levels for goal. In some embodiments, the goal authoring system 140 defines the goal levels based on information received from the client device (e.g., user-entered data provided via the goal definition user interface). In some embodiments, the goal authoring system 140 automatically defines the goal levels based on a template. In some embodiments, the goal authoring system 140 automatically defines the goal levels based on information provided by the goal repository 143, which stores information of goal levels defined form similar goals. In some implementations, the goal definition information defines participant support levels for a goal level. In some embodiments, the goal authoring system 140 defines the participant support levels based on information received from the client device (e.g., user-entered data provided via the goal definition user interface). In some implementations, the goal authoring system 140 may automatically define the participant support levels based on a template. In some embodiments, the goal authoring system 140 may automatically define the participant support levels based on information provided by the goal repository 143, which stores information of participant support levels defined form similar goal levels. In some implementations, conversational content includes goal information indicating that a specific goal should be evaluated, and the conversational system 216 may provide an instruction to the evaluation system 215 (either directly or via the control system 121) to enable the associated goal evaluation module at the evaluation system 215. In a case where the goal evaluation module is enabled, the evaluation system 215 executes the instructions of the goal evaluation module to process information generated from the multimodal perceptual system 123 and generate evaluation information. In some implementations, the evaluation system 215 provides generated11SUBSTITUTE SHEET (RULE 26)evaluation information to the conversation system 215 (either directly or via the control system 121). In some implementations, the evaluation system 215 may update the current conversational content at the conversation system 216 or may select new conversational content at the conversation system 100 (either directly or via the control system 121), based on the evaluation information.

[0045] Figure IB illustrates a robot computing device according to some implementations. In some implementations, the robot computing device 105 may be a machine, a robot, a digital companion, an electro-mechanical device including computing devices. These terms may be utilized interchangeably in the specification. In some implementations, as shown in Figure IB, the robot computing device 105 may include a head assembly 103d, a display device 106d, at least one mechanical appendage 105d (two are shown in FIG. IB), a body assembly 104d, a vertical axis rotation motor 163, and / or a horizontal axis rotation motor 162. In some implementations, the robot computing device may include a multimodal output system 122 and the multimodal perceptual system 123. In some implementations, the display device 106d may allow facial expressions 106b to be shown or illustrated after being generated. In some implementations, the facial expressions 106b may be shown by the two or more digital eyes, a digital nose and / or a digital mouth. In some implementations, other images or parts may be utilized to show facial expressions. In some implementations, the horizontal axis rotation motor 163 may allow the head assembly 103d to move from side-to-side which allows the head assembly 103d to mimic human neck movement like shaking a human’s head from side-to-side. In some implementations, the vertical axis rotation motor 162 may allow the head assembly 103d to move in an up-and-down direction like shaking a human’s head up and down. In some implementations, an additional motor may be utilized to move the robot computing device (e.g., the entire robot or computing device) to a new position or geographic location in a room or space (or even another room). In this implementation, the additional motor may be connected to a drive system that causes wheels, tires or treads to rotate and thus physically move the robot computing device.

[0046] In some implementations, the body assembly 104d may include one or more touch sensors. In some implementations, the body assembly’s touch sensor(s) may allow the robot computing device to determine if it is being touched or hugged. In some implementations, the one or more appendages 105d may have one or more touch sensors. In some implementations, some of the one or more touch sensors may be located at an end of the appendages 105d (which may represent the hands). In some implementations,12SUBSTITUTE SHEET (RULE 26)this allows the robot computing device 105 to determine if a user or child is touching the end of the appendage (which may represent the user shaking the user’s hand).

[0047] Figure 2 is a diagram depicting system architecture of robot computing device or robot (e.g., 105 of Figure IB), according to implementations. In some implementations, the robot computing device or system of Figure 2 may be implemented as a single hardware device. In some implementations, the robot computing device and system of FIG. 2 may be implemented as a plurality of hardware devices. In some implementations, the robot computing device and system of Figure 2 may be implemented as an ASIC (Application-Specific Integrated Circuit). In some implementations, the robot computing device and system of Figure 2 may be implemented as an FPGA (Field-Programmable Gate Array). In some implementations, the robot computing device and system of Figure 2 may be implemented as a SoC (System-on-Chip). In some implementations, the bus 201 may interface with the processors 226 A-N, the main memory 227 (e.g., a random access memory (RAM)), a read only memory (ROM) 228, one or more processor-readable storage mediums 210, and one or more network device 211. In some implementations, bus 201 interfaces with at least one of a display device (e.g., 102c) and a user input device. In some implementations, bus 101 interfaces with the multi-modal output system 122. In some implementations, the multi-modal output system 122 may include an audio output controller. In some implementations, the multi-modal output system 122 may include a speaker. In some implementations, the multi-modal output system 122 may include a display system or monitor. In some implementations, the multi-modal output system 122 may include a motor controller. In some implementations, the motor controller may be constructed to control the one or more appendages (e.g., 105d) of the robot system of FIG. IB. In some implementations, the motor controller may be constructed to control a motor of an appendage (e.g., 105d) of the robot system of Figure IB. In some implementations, the motor controller may be constructed to control a motor (e.g., a motor of a motorized, a mechanical robot appendage).

[0048] In some implementations, a bus 201 may interface with the multi-modal perceptual system 123 (which may be referred to as a multi-modal input system or multimodal input modalities. In some implementations, the multi-modal perceptual system 123 may include one or more audio input processors. In some implementations, the multimodal perceptual system 123 may include a human reaction detection sub-system. In some implementations, the multimodal perceptual system 123 may include one or more13SUBSTITUTE SHEET (RULE 26)microphones. In some implementations, the multimodal perceptual system 123 may include one or more camera(s) or imaging devices.

[0049] In some implementations, at least one of a central processing unit (processor), a GPU, and a multi-processor unit (MPU) may be included. In some implementations, the processors and the main memory form a processing unit 225. In some implementations, the processing unit 225 includes one or more processors communicatively coupled to one or more of a RAM, ROM, and computer-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and computer-readable storage medium via a bus; and the one or more processors execute the received instructions. In some implementations, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some implementations, the processing unit may be a SoC (System-on-Chip). In some implementations, the processing unit may include at least one arithmetic logic unit (ALU) that supports a SIMD (Single Instruction Multiple Data) system that provides native support for multiply and accumulate operations. In some implementations the processing unit is a Central Processing Unit such as an Intel Xeon processor. In other implementations, the processing unit includes a Graphical Processing Unit such as NVIDIA Tesla.

[0050] In some implementations, the one or more network adapter devices or network interface devices 205 may provide one or more wired or wireless interfaces for exchanging data and commands. Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like. In some implementations, the one or more network adapter devices or network interface devices 205 may be wireless communication devices. In some implementations, the one or more network adapter devices or network interface devices 205 may include personal area network (PAN) transceivers, wide area network communication transceivers and / or cellular communication transceivers. In some implementations, the one or more network adapter devices or network interface devices 205 may provide one or more wired or wireless interfaces for exchanging data and commands. Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like. In some implementations, the one or more network adapter devices or network interface devices 205 may be wireless communication devices. In some implementations, the one or more network adapter devices or network interface devices14SUBSTITUTE SHEET (RULE 26)205 may include personal area network (PAN) transceivers, wide area network communication transceivers and / or cellular communication transceivers.

[0051] In some implementations, the one or more network devices 205 may be communicatively coupled to another robot computing device (e.g., a robot computing device similar to the robot computing device 105 of Figure IB). In some implementations, the one or more network devices 205 may be communicatively coupled to an evaluation system module (e.g., 215). In some implementations, the one or more network devices 205 may be communicatively coupled to a conversation system module (e.g., 110). In some implementations, the one or more network devices 205 may be communicatively coupled to a testing system. In some implementations, the one or more network devices 205 may be communicatively coupled to a content repository (e.g., 220). In some implementations, the one or more network devices 205 may be communicatively coupled to a client computing device (e.g., 110). In some implementations, the one or more network devices 205 may be communicatively coupled to a conversation authoring system (e.g., 160). In some implementations, the one or more network devices 205 may be communicatively coupled to an evaluation module generator. In some implementations, the one or more network devices may be communicatively coupled to a goal authoring system. In some implementations, the one or more network devices 205 may be communicatively coupled to a goal repository. In some implementations, computer-executable instructions in software programs (such as an operating system 211, application programs 212, and device drivers 213) may be loaded into the one or more memory devices (of the processing unit) from the processor-readable storage medium, the ROM or any other storage location. During execution of these software programs, the respective computer-executable instructions may be accessed by at least one of processors 226 A - 226N (of the processing unit) via the bus 201, and then may be executed by at least one of processors. Data used by the software programs may also be stored in the one or more memory devices, and such data is accessed by at least one of one or more processors 226A - 226N during execution of the computer-executable instructions of the software programs.

[0052] In some implementations, the processor-readable storage medium 210 may be one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid-state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. In some implementations, the processor-readable storage medium 210 may include computer-15SUBSTITUTE SHEET (RULE 26)executable instructions (and related data) for an operating system 211, software programs or application software 212, device drivers 213, and computer-executable instructions for one or more of the processors 226A - 226N of FIG. 2.

[0053] In some implementations, the processor-readable storage medium 210 may include a machine control system module 214 that includes computer-executable instructions for controlling the robot computing device to perform processes performed by the machine control system, such as moving the head assembly of robot computing device.

[0054] In some implementations, the processor-readable storage medium 210 may include an evaluation system module 215 that includes computer-executable instructions for controlling the robotic computing device to perform processes performed by the evaluation system. In some implementations, the processor-readable storage medium 210 may include a conversation system module 216 that may include computer-executable instructions for controlling the robot computing device 105 to perform processes performed by the conversation system. In some implementations, the processor-readable storage medium 210 may include computer-executable instructions for controlling the robot computing device 105 to perform processes performed by the testing system. In some implementations, the processor-readable storage medium 210, computer-executable instructions for controlling the robot computing device 105 to perform processes performed by the conversation authoring system.

[0055] In some implementations, the processor-readable storage medium 210, computer-executable instructions for controlling the robot computing device 105 to perform processes performed by the goal authoring system. In some implementations, the processor-readable storage medium 210 may include computer-executable instructions for controlling the robot computing device 105 to perform processes performed by the evaluation module generator.

[0056] In some implementations, the processor-readable storage medium 210 may include the content repository 220. In some implementations, the processor-readable storage medium 210 may include the goal repository 143. In some implementations, the processor-readable storage medium 210 may include computer-executable instructions for an emotion detection module. In some implementations, emotion detection module may be constructed to detect an emotion based on captured image data (e.g., image data captured by the perceptual system 123 and / or one of the imaging devices). In some implementations, the emotion detection module may be constructed to detect an emotion16SUBSTITUTE SHEET (RULE 26)based on captured audio data (e.g., audio data captured by the perceptual system 123 and / or one of the microphones). In some implementations, the emotion detection module may be constructed to detect an emotion based on captured image data and captured audio data. In some implementations, emotions detectable by the emotion detection module include anger, contempt, disgust, fear, happiness, neutral, sadness, and surprise. In some implementations, emotions detectable by the emotion detection module include happy, sad, angry, confused, disgusted, surprised, calm, unknown. In some implementations, the emotion detection module is constructed to classify detected emotions as either positive, negative, or neutral. In some implementations, the robot computing device 105 may utilize the emotion detection module to obtain, calculate or generate a determined emotion classification (e.g., positive, neutral, negative) after performance of an action by the machine, and store the determined emotion classification in association with the performed action (e.g., in the storage medium 210).

[0057] In some implementations, the testing system 350 may a hardware device or computing device separate from the robot computing device, and the testing system includes at least one processor, a memory, a ROM, a network device, and a storage medium (constructed in accordance with a system architecture similar to a system architecture described herein for the machine 120), wherein the storage medium stores computer-executable instructions for controlling the testing system 350 to perform processes performed by the testing system, as described herein.

[0058] In some implementations, the conversation authoring system may be a hardware device separate from the robot computing device 105, and the conversation authoring system may include at least one processor, a memory, a ROM, a network device, and a storage medium (constructed in accordance with a system architecture similar to a system architecture described herein for the robot computing device 105), wherein the storage medium stores computer-executable instructions for controlling the conversation authoring system to perform processes performed by the conversation authoring system.

[0059] In some implementations, the evaluation module generator may be a hardware device separate from the robot computing device 105, and the evaluation module generator may include at least one processor, a memory, a ROM, a network device, and a storage medium (constructed in accordance with a system architecture similar to a system architecture described herein for the robot computing device), wherein the storage medium stores computer-executable instructions for controlling the evaluation module17SUBSTITUTE SHEET (RULE 26)generator to perform processes performed by the evaluation module generator, as described herein.

[0060] In some implementations, the goal authoring system may be a hardware device separate from the robot computing device, and the goal authoring system may include at least one processor, a memory, a ROM, a network device, and a storage medium (constructed in accordance with a system architecture similar to a system architecture described instructions for controlling the goal authoring system to perform processes performed by the goal authoring system. In some implementations, the storage medium of the goal authoring system may include data, settings and / or parameters of the goal definition user interface described herein. In some implementations, the storage medium of the goal authoring system may include computer-executable instructions of the goal definition user interface described herein (e.g., the user interface). In some implementations, the storage medium of the goal authoring system may include data of the goal definition information described herein (e.g., the goal definition information). In some implementations, the storage medium of the goal authoring system may include computer-executable instructions to control the goal authoring system to generate the goal definition information described herein (e.g., the goal definition information).

[0061] Figure 3 illustrates a robot computing device that may be utilized for multiple users according to some implementations. In some implementations, the robot computing device or digital companion 300 may include one or more imaging devices 315, a robot body 305, a root head assembly 310, a robot base335, a robot display assembly 320, one or more microphones 355, one or more touch sensors (not shown), one or more IMU sensors (not shown), one or more motors and / or motor controllers for controlling movement one of or more robot appendages or arms 325 (not shown), one or more power sources or batteries 345, one or more light assemblies or light bars or LEDs 330, one or more power interfaces or power ports 340 and / or one or more speakers 351. As described in detail in Figure 2, in some implementations, the robot computing devices may include one or more processors 226A - 226N, one or more memory devices 227, and / or one or more wireless communication transceivers 205. In some implementations, computer- readable instructions (reference numbers 211, 212, 213, 214, 215, 216, and 220) may be stored in the one or more memory devices 227 and may be executable by the one or more processors 226A - 226N, to perform numerous actions, features and / or functions. In some implementations, the robot computing device 300 may perform analytics processing on data, parameters and / or measurements, audio files and / or image files captured and / or18SUBSTITUTE SHEET (RULE 26)obtained from the components of the robot computing device listed above. Figure 3 illustrates a front view of another robot or robot computing device according to some embodiments. In some embodiments, the robot or robot computing device 300 may include a robot body 305, a robot head assembly 310, and / or a robot base 335. In some embodiments, the power interface or power port 340 may connect to a power cord (not shown) which plugs into an external power source. In some embodiments, the external power source may provide power to the one or more rechargeable batteries 345 through the power port or interface 340.

[0062] In some implementations, the one or more touch sensors may measure if a user (child, parent or guardian) touches the robot computing device or if another object or individual comes into contact with the robot computing device. In some implementations, the one or more touch sensors may measure a force of the touch and / or dimensions of the touch to determine, for example, if it is an exploratory touch, a push away, a hug or another type of action. In some implementations, for example, the touch sensors may be located or positioned on a front and back of an appendage or a hand (hand touch sensor 353) of the robot computing device or on a stomach area (body touch sensor 354) of the robot computing device. Thus, the software and / or the touch sensors may determine if a child is shaking a hand or grabbing a hand of the robot computing device or if they are rubbing the stomach of the robot computing device. In some implementations, other touch sensors may determine if the child is hugging the robot computing device. In some implementations, the touch sensors may be utilized in conjunction with other robot computing device software where the robot computing device could tell a child to hold their left hand if they want to follow one path of a story of hold a left hand if they want to follow the other path of a story.

[0063] In some implementations, the one or more imaging devices 315 may capture images and / or video of a child, parent or guardian interacting with the robot computing device. In some implementations, the one or more imaging devices 315 may be located on a top area of a robot computing device 300 in order to capture a larger area in front of the user. In some implementations, the one or more imaging devices 315 may be located on of the display assembly or screen 320. In some implementations, the one or more imaging devices 315 may capture images and / or video of the area around the child, parent or guardian. In some implementations, the one or more microphones 355 may capture sound or verbal commands spoken by the child, parent or guardian. In some implementations, the one or more microphones 355 may be positioned or located on top19SUBSTITUTE SHEET (RULE 26)of the robot computing device 300. In some implementations, computer-readable instructions executable by the processor or an audio processing device may convert the captured sounds or utterances into audio files for processing.

[0064] In some implementations, the one or more IMU sensors (not shown) may measure velocity, acceleration, orientation and / or location of different parts of the robot computing device. In some implementations, for example, the IMU sensors may determine a speed of movement of an appendage or a neck. In some implementations, for example, the IMU sensors may determine an orientation of a section or the robot computing device, for example of a neck, a head, a body or an appendage in order to identify if the hand is waving or in a rest position. In some implementations, the use of the IMU sensors may allow the robot computing device to orient its different sections in order to appear more friendly or engaging to the user.

[0065] In some implementations, the robot computing device 300 may have one or more motors (e.g., 162 or 163) and / or motor controllers. In some implementations, the computer-readable instructions may be executable by the one or more processors and commands or instructions may be communicated to the one or more motor controllers to send signals or commands to the motors to cause the motors to move sections of the robot computing device 300. In some implementations, the sections may include appendages or arms 325 of the robot computing device and / or a neck or a head 310 of the robot computing device 300.

[0066] In some implementations, the robot computing device 300 may include a display or monitor or display assembly 320. In some implementations, the monitor or display assembly 320 may allow the robot computing device 300 to display facial expressions (e.g., eyes, nose, mouth expressions) as well as to display videos, animations, or messages to the child, parent or guardian.

[0067] In some implementations, the robot computing device 300 may include one or more speakers 351, which may be referred to as an output modality. In some implementations, the one or more speakers 351 may enable or allow the robot computing device to communicate words, phrases and / or sentences and thus engage in conversations with the user. In addition, the one or more speakers 351 may emit audio sounds or music for the child, parent or guardian when they are performing actions and / or engaging with the robot computing device 300.

[0068] Descried herein is operation of a software program that allows a resource owner to utilize a robot computing device with multiple users or children. In some20SUBSTITUTE SHEET (RULE 26)embodiments, a resource owner may be a clinician and / or an educator. In some embodiments, a clinician may be a doctor, a psychologist, a therapist, or a psychiatrist. In some embodiments, an educator may be a teacher, a teaching assistant, a librarian, and / or a school nurse or therapist. In this case, the resource owner may be a renter of the companion robot. In some embodiments, the resource owner may utilize the resource owner software application to set up the software to interface with the children. In some embodiments, a resource owner may be a parent of multiple children or may be a guardian of multiple children, all of which may be utilizing and / or interfacing with the robot computing device.

[0069] A unique aspect of the subject matter described herein is the ability for a medical professional (e.g., doctor, physical therapist, speech therapist, Applied Behavioral Analysis (ABA) therapist) to utilize a robot computing device with multiple users or children with each user or child having their own account. An additional unique aspect of the subject matter described herein is the ability of a parent or guardian to not have to purchase multiple robot computing devices if they are parent or guardian of multiple children. In this case, the parent or guardian may keep track of each child’s goals and progressions towards the children’s goals utilizing a single robot computing device. A further unique aspect of the subject matter described herein is the ability for an educational professional (e.g., a teacher, a professor, a librarian, a teacher’s aide, etc.) to utilize the robot computing device for multiple students and have individual tracking of each students’ performance and to separate out each student’s data from one another. Further, the accounts are secure and encrypted and protected from unauthorized use. Further, there is a unique workflow for authenticating both the resource owner and / or each user or child that is interacting or interfacing with the robot computing device. In some embodiments, a resource owner may have access to a resource owner software application which is similar to a parent application except that the resource owner has the ability to track, communicate with and / or monitor multiple users or children. In some implementations, the resource owner software application may include computer-readable instructions stored in one or more memory devices on a mobile computing device and / or a cloud-based server computing device. In some embodiments, the computer-readable instructions may be executable by one or more processors on the mobile computing device and / or cloud-based computing device in order to initiate and / or operate the resource owner software application.21SUBSTITUTE SHEET (RULE 26)

[0070] In some embodiments, the resource owner software application may enable a resource owner to keep track of multiple users’ progress and / or interactions with the robot computing device. As noted above, the users may be patients, students, children or subjects. This is a unique feature because any existing software applications that are utilized with a robot computing device do not include the ability to interact with multiple users (e.g., they can only interact with one user or track interactions with one user). In some embodiments, the resource owner software application may allow a resource owner to setup accounts for two or more users or children and to switch between the users accounts when reviewing the user or patient’s progress. In addition, the resource owner may set up or establish different operation and / or data collection parameters for each user. This feature allows a resource owner to customize an interaction with each child or user to make the robot computing device more focused on each child.

[0071] In some embodiments, the resource owner software application may request that the resource owner create login information for accessing the resource owner software application and to provide personal contact information to allow the robot device to contact the resource owner, which may include your name and email address. In some embodiments, for each user or child, the resource owner software application may request a user’s first name and birthdate, developmental goal information for each of the users or children, and / or birthday, appointments or significant dates for the user or child (or family). In some embodiments, developmental goals may include Socio-Emotional Learning (SEL) parameter goals, which include self-awareness goal values, selfmanagement goal values, social awareness goal values, relationship goal values, and / or cognitive skill goal values and these may be customizable for each user and / or updatable for each user. In some embodiments, the resource owner may be able to customize robot computing device operation features for each of the users or children to uniquely configure the robot computing device with specific characteristics. In some embodiments, the Moxie operation features may include, but are not limited to, selecting no sound effects; no visual effects; slowed down speech for the robot; longer pauses for input from the user or child, and / or limited use of the heads-up display, as will be illustrated in detail later. In some embodiments, the robot computing device might support multiple variations of a language and / or multiple languages. The subject matter described herein allows a user to select a language for each of the users or children. This allows a resource owner to utilize the robot computing device with multiple users, even if the users speak many different languages. In these implementations, the resource owner22SUBSTITUTE SHEET (RULE 26)may select a language for each of the children, mentors, or users. In some embodiments, the resource owner software application might perform an assessment of each of the user(s) based upon data input by the resource owner, in order to adjust the interaction depending on the characteristics of each user (e.g., state of mind, personal traits, etc.). In some embodiments, the resource owner may also obtain reading levels (e.g., reading grade levels) for each of the users in order to adjust an interaction with the robot computing device, including but not limited to adjusting content provided to the user during interactions with the robot computing device. In other words, the user and robot computing device interactions may be adjusted and / or unique for each of the users.

[0072] In some embodiments, the parent application software application may also communicate with the robot computing device and / or the robot device company cloud server to receive performance statistics for each of the users in their interaction with the robot computing device. Illustratively, in some embodiments, using the resource owner software application, resource owners may access each user’s personal information, update personal information previously provided, and / or change and update the developmental goals for each user or child according to some embodiments. Illustratively, the resource owner software application may receive the following information and / or parameters for each of users or children and present it as part of the user’s account in the resource owner software application: Activity Data (such as books read, calculated reading comprehension, calculated vocabulary level, amount of time spent interacting or reading, badges or trophies received, activity patterns) and Insight Data (data or parameters generated through analysis of the activity data and / or an artificial intelligence engine on the robot device owner’s cloud computing device that provides insights on your child’s developmental progress). In some implementations, the Activity Data and / or Insight Data may be captured and / or generated by the robot computing device and / or generated or created by the robot cloud-based computing device 115. The privacy of each user or child’s performance is only accessible by the resource owner through the resource owner application since the data is encrypted and anonymized when processed by the device owner’s cloud computing device. Thus, the privacy of each user or child’s performance is controlled by the resource owner as he would only share the Activity Data and / or Insight Data for each user or child with the user or child (or the user or child’s parent or guardian upon request).

[0073] Figure 4A illustrates a flowchart for initializing a robot computing device for use with multiple users utilizing the resource owner software application according to23SUBSTITUTE SHEET (RULE 26)some embodiments. In some embodiments, in step 405, a resource owner may purchase a companion robot for use in their job or workplace, or at home. In some embodiments, in step 410, the resource owner may download a resource owner mobile software application onto the resource owner’s mobile computing device. In some embodiments, the mobile computing device may be a mobile communication device (e.g., a smart phone or a mobile phone), a laptop computing device, and / or a tablet computing device. In some embodiments, a resource owner may utilize a desktop computing device to receive the owner mobile software application. The owner mobile software application may be referred to as the resource owner application, the owner application or the parent application because it is similar to the parent software application that is utilize with single user robot computing devices (such as Embodied’s Moxie robot computing device).

[0074] In some embodiments, in step 415, a resource owner may register the owner application with a cloud-based server computing device 115. In some embodiments, because the resource owner may be working with children, the robot’s manufacturer (or other entities) may wish to verify that the resource owner is authentic (e.g., the resource owner is who he or she says they are). In some embodiments, in step 420, the cloudbased server computing device may communicate with a third-party verification server computing device to verify that the resource owner is authentic. In some embodiments, companies like PRIVO provide this third-party verification or authentication services. In some embodiments, in step 425, the Embodied server computing device may receive an authentication notification from the third-party verification computing device.

[0075] In some embodiments, in step 430, the cloud-based server computing device 115 may communicate a clinical, education or multi-user privacy policy to the resource owner computing device in order to have a resource owner verify that he or she or they will abide by robot company’s privacy policy and / or specifically the robot company’s collection of information from the resource owner’s users, clients, children or patients. In some embodiments, in step 435, the Embodied server computing device may receive privacy policy compliance verification from the resource owner computing device.

[0076] In some embodiments, in step 440, the cloud-based service computing device may assign the resource owner a resource owner identifier. In some embodiments, the resource owner identifier may be a recovery key. In some embodiments, the resource owner identifier may be derived from a recovery key assigned to the resource owner. In some embodiments, a resource owner’s recovery key may be utilized by a resource owner24SUBSTITUTE SHEET (RULE 26)to recover lost data by working with a robot company and / or the cloud-based server computing device 115. In some embodiments, the resource owner mobile computing device may communicate the recovery key to the cloud-based server computing device 115 in order to retrieve and / or reload customer data. In some embodiments, the robot may be provided with a robot identifier (e.g., robot ID) which may be embedded and / or stored in one or more memory devices with the robot computing device.

[0077] Figure 4B illustrates a flowchart of a user, child, student or patient registration process according to some embodiments. In some embodiments, in step 445, the resource owner may wish to start registering users with who the resource owner may be utilizing a companion robot (e.g., a physician or therapist or a teacher who would like to utilize the robot computing device with a number of children, patients or students). In some embodiments, the resource owner may wish to register multiple users or children. In some embodiments, the multiple users may be children and specifically for children under 13 or 16, the resource owner must make sure to obtain parental consent in order to interface and / or interact with users who are children. In some embodiments, if children under 13 or 16 are the users or patients, a parent or guardian must provide parental consent. Accordingly, a parent or guardian of any child who the resource owner is registering may have to be verified and then may have to provide parental consent to allow a resource owner to utilize the companion robot to interface and / or communicate with their child (and collect information).

[0078] With respect to each of the user’s or patients, in some embodiments, in step 445, the resource owner may obtain a user’s age, a user’s first name, a parent email address and / or other relevant information or parameters. In some embodiments, in step 450, the resource owner computing device may communicate a user’s age, a first name of a user and a parent email address to the Embodied server computing device. In some embodiments, in step 455, the cloud-based server computing device may create and / or establish an account for the user. While this may be referred to as a user account, a parent or guardian may be in charge of verifying information for the user account especially if the user is not of an age to be able to consent to certain activities or actions. In some embodiments, the cloud-based server computing device may initiate a parental verification process. In some embodiments, in step 460, the cloud-based server computing device may communicate a parent email address to a third-party verification computing device in order for the third-party verification computing device to communicate with the parent. In these embodiments, in step 465, the third-party25SUBSTITUTE SHEET (RULE 26)verification computing device may verify that the parent or guardian is authentic (e.g., authenticate the parent’s or guardian’s identify) by communicating offline with the parent and / or guardian. If a parent is authenticated, in these embodiments, in step 470, the third- party verification computing device may communicate the parental verification authentication to the cloud-based server computing device and / or the resource owner computing device to let the resource owner know the parent has been verified. In some embodiments, because the robot computing device may be collecting personal information about a user (which may be a child), in step 475, the cloud-based server computing device may communicate with the third-party verification computing device to have the third-party obtain parental consent from a parent or guardian to utilize the robot computing device. In some embodiments, in step 480, the third-party verification computing device may communicate a privacy policy (e.g., the robot company privacy policy) to the parent or guardian computing device to attempt to obtain parental consent to utilize the robot companion with his, her or their child. In some embodiments, in step 485, the third-party verification computing device may obtain parent or guardian consent and may communicate the electronic parent or guardian consent to the cloud-based server computing device and / or the resource owner computing device. In some embodiments, in step 490, the Embodied server computing device may generate a user account identifier or analytics user identifier (AUID) for the user or child. In some embodiments, the AUID may be derived from the recovery key and in other embodiments, the AUID may be derived from a resource owner identifier.

[0079] Figure 5A illustrates a resource owner registering additional users according to some embodiments. In some embodiments, the resource owner may wish to start registering additional users who the resource owner may be utilizing a robot computing device with (e.g., a physician or therapist who would like to utilize the robot computing device with a second or third or fourth users or children). In some embodiments, the resource owner may wish to register multiple users or children. In some embodiments, the additional users may be children and specifically children under 13 or 16, the resource owner must make sure to obtain parental consent in order to interface and / or interact with users who are children. In some embodiments, if children under 13 or 16 are the additional users or patients, a parent or guardian must provide parental consent. In some embodiments, if the children are between 13 and 18, the resource owner may want to at least obtain user consent (e.g., the children’s consent) for the collection of information, parameters and / or data. In some embodiments, if the children or users are over 18, the26SUBSTITUTE SHEET (RULE 26)resource owner may want to obtain user or child consent for the collection of information, parameters and / or data. This is a novel aspect of the robot computing device and its capability of collecting information on multiple users and / or children to interface with a robot computing device and to keep this information safe and secure.

[0080] With respect to the each of the additional user’s or patients, in some embodiments, in step 505, the resource owner may obtain an additional user’s age, an additional user’s first name, a parent email address and / or other relevant information or parameters. In some embodiments, in step 510, the resource owner computing device may communicate an additional user’s age, first name and parent email address to the cloud-based server computing device. In some embodiments, in step 515, the cloudbased server computing device may create and / or establish an additional account for the additional user, which is different from the account for the first user. In some embodiments, in step 520, the cloud-based server computing device may communicate a parent email address to a third-party verification computing device in order for the third- party verification computing device to communicate with the parent. In these embodiments, in step 525, the third-party verification computing device may verify that the parent or guardian is authentic (e.g., authenticate the parent’s or guardian’s identify with respect to the additional user) by communicating offline with the parent and / or guardian. If a parent or guardian is authenticated, in these embodiments, in step 530, the third-party verification computing device may communicate the parental verification authentication to the cloud-based server computing device and / or the resource owner computing device to let the resource owner know the parent has been verified. In some embodiments, because the robot computing device may be collecting personal information about an additional user (which may be a child), in step 535, the cloud-based server computing device may communicate with the third-party verification computing device to have the third-party obtain parental consent from a parent or guardian to utilize the robot computing device. In some embodiments, in step 540, the third-party verification computing device may communicate a privacy policy (e.g., the robot company privacy policy) to the parent or guardian computing device to attempt to obtain parental consent to utilize the robot companion with his, her or their additional user or child. In some embodiments, in step 545, the third-party verification computing device may obtain parent or guardian consent and may communicate the electronic parent or guardian consent to the cloud-based server computing device and / or the resource owner computing device. In some embodiments, in step 550, the robot server computing device27SUBSTITUTE SHEET (RULE 26)may generate an additional user account identifier or analytics user identifier (AUID) for the user or child. In some implementations, the additional AUIDs may be unique for each user or child who the resource owner is working with. In some implementations, the AUID is utilized to index any data that is collected. In some implementations, the AUID is automatically generated and no one may know the AUID. In some implementations, the resource owner may repeat the actions of steps 505 - 550 for each additional user that will be registered to utilize the robot computing device. In some implementations, the resource owner is a parent in a family with multiple children and thus steps 505-550 are repeated for each of the children in the family. In such cases the resource owner (parent) might re-use the same email address for each of the children. Other robot computing devices do not include this unique and novel feature.

[0081] Figure 5B illustrates a robot computing device connection process and / or collection process according to some implementations. After a first user or child is registered, the robot computing device may setup communications with the resource owner (and / or specifically the resource owner computing device), which may be wireless communications (e.g., Bluetooth, Near Field Communications, WiFi or 802.11 protocol wireless communications). This may allow the resource owner to provide information from any of the users or children that are registered by the resource owner. In some embodiments, in step 555, the robot server computing device may communicatively connect with the robot computing device to interface and / or interact with the user (or child). In some embodiments, for a first user or patient, the Embodied server computing device may generate commands and / or instructions to pair the robot companion device with the resource owner computing device and / or the Embodied server computing device. In some embodiments, the pairing may utilize Bluetooth communications or other wireless communication protocols. In some embodiments, in step 560, the robot server computing device may also establish communications with the resource owner computing device, in order to allow communications of collected information and / or parameters to be communicated between the robot computing device and / or the robot server computing device and the resource owner computing device in order for the resource owner to be able to understand how the user (or child) is interacting with the robot computing device. In some implementations, this connection and / or pairing allows the robot companion device to collect video and / or audio information from interactions and / or communications with the user (and / or child) and communicate specific information to the Embodied server28SUBSTITUTE SHEET (RULE 26)computing device and / or the resource owner computing device or application (which will be described in detail below).

[0082] A unique aspect of the multi-user software application is the ability to assign multiple users to one robot computing device, collect consented information and store the collected information in separate accounts that are protected and associated with keys, indexes or AUIDs. An additional unique aspect is that the collected information may be different for each user based on configuration parameters established by the user and / or resource owner. In some embodiments, it is also possible to have multiple users connect with multiple robot computing devices. As an illustrative example, in a classroom, in order for all of the students to have time with the robot computing device, 5 robots may be purchased and six students may be assigned to each of the robot computing devices (so 30 students in total are interacting with the five robots). Each child will have unique keys, indexes or AUIDs to keep their information private. This lessens the economic impact on the educational or medical establishment while also offering numerous students the ability to interface with the robot computing device and also keep their data private.

[0083] In some embodiments, the resource owner may utilize the resource owner software application to setup limitations, configurations and / or other parameters to have the robot computing device collect specific information in specific manner with different users. In other words, the resource owner software application may be uniquely and separately configured to communicate with each user. This will be described in detail in Figure 6A - 6Z and 7A-7Z below with screen shots from the resource owner software application. After the resource owner has configured the resource owner software application for the users or children who are registered to communicate and / or interface with the robot computing device, the robot computing device may begin communicating with the user or child and / or initiate collection of information and / or parameters during conversations with the user or child.

[0084] In some embodiments, in step 565, the robot computing device may initiate a conversation with the user. In some implementations, in step 570, the robot computing device may collect raw audio files from one or more microphones on the robot computing device during the conversation interactions. In some implementations, in step 572, the robot computing device may collect raw video files from interactions with the user or child.

[0085] In some implementations, the robot computing device may perform operations on the collected audio files and / or video files. With respect to the collected or captured29SUBSTITUTE SHEET (RULE 26)video files, in some implementations, in step 575, the robot computing device may generate facial expression datapoints and create one or more facial expression datapoint files. In some implementations, the robot computing device may delete the raw video files from one or more memory devices in the robot computing device. In some implementations, in step 580, the robot computing device may communicate the one or more facial expression datapoint files to the Embodied server computing device. In some implementations, in step 581, computer-readable instructions executable by one or more processors of the Embodied or robot company server computing device may analyze the captured facial expression data to determine expressions and / or feeling of the user and / or child during a communication interaction with the robot computing device and may generate expression parameters. In some implementations, in step 582, the expression parameters and / or the facial expression datapoint files may be stored in one or more memory devices of the Embodied server computing device and the expression parameters and / or the facial expression datapoint files may be indexed with the user’s or children’s AUID, index or key. In some embodiments, the facial expression datapoint files may be encrypted on the robot company server computing devices. In some embodiments, the Embodied server computing device may utilize the expression parameters to assist in continuing communication interactions between the robot computing device and the user.

[0086] Figure 5C illustrates a robot computing device connection process and / or collection process according to some implementations. In some implementations, in step 583, the robot computing device may analyze the captured audio data to determine expressions and feelings of the user and / or child during a communication interaction with the user or child. The robot computing device may generate audio expression parameters. In other embodiments, computer-readable instructions executable by one or more processors of the robot server computing device (or a third-party server computing device) may analyze the captured audio to determine expressions and / or feeling of the user and / or child during a communication interaction with the robot computing device and may generate audio expression parameters. In some implementations, in step 584, the audio expression parameters may be stored in one or more memory devices of the robot server computing device and the audio expression parameters may be indexed with the user’s or children’s AUID. In some embodiments, the audio expression parameters may be encrypted on the robot company server computing devices. In some embodiments, the robot server computing device may utilize the audio expression30SUBSTITUTE SHEET (RULE 26)parameters to assist in continuing communication interactions between the robot computing device and the user.

[0087] In some implementations, in step 585, the robot computing device may communicate the captured and / or recorded audio files to the Embodied server computing device. In some implementations, in step 586, the Embodied server computing device may communicate the captured audio files to a third-party cloud speech-to-text (STT) computing device. In some implementations, the captured audio files may be encrypted over the wire as they are being communicated to the third-party computing device. In some implementations, the captured audio files may be encrypted before being communicated to the third-party cloud STT computing device. In some implementations, the audio files have no identifiers so that the third-party STT computing device will not know an identity of the child or user.

[0088] In some embodiments, in step 587, the STT computing device may automatically transcribe the audio to generate audio transcription files. In some embodiments, in step 588, the cloud STT computing device may communicate and / or transmit the generated audio transcription files to the robot computing device that provided the raw audio files. In some implementations, the cloud STT computing device may delete the audio files and the audio transcription files and not store them. In some embodiments, the robot computing device may index and / or associate the received audio transcription files with an AUTD or other identifier. In some implementations, in step 589, the robot computing device may communicate the audio transcription files and the AUID (or other identifier) to the robot server computing device. In some implementations, the robot computing device may encrypt the audio transcription files and AUID index with a secret robot key. In some embodiments, the audio transcription files and AUID may be encrypted-at-rest on the robot cloud-based servers. In some implementations, in step 590, the robot company (e.g., Embodied) server computing device may store the audio transcription files with the AUID, index or key in one or more memory devices of the robot server computing device.

[0089] In some implementations, in step 591, the robot computing device may analyze the generated audio transcription files to determine expressions and feelings of the user and / or child during a communication interaction with the user or child. The robot computing device may generate audio expression datapoints from the audio transcriptions. In other embodiments, computer-readable instructions executable by one or more processors of the robot server computing device (or a third-party server31SUBSTITUTE SHEET (RULE 26)computing device) may analyze the generated audio transcription files to determine expressions and / or feeling of the user and / or child during a communication interaction with the robot computing device and may generate audio expression datapoints. In some implementations, in step 592, the audio expression datapoints may be stored in one or more memory devices of the robot server computing device and the audio expression datapoints may be indexed with the user’s or children’s AUID. In some embodiments, the audio expression datapoints may be encrypted on the robot company server computing devices. In some embodiments, the robot server computing device may utilize the audio expression datapoints to assist in continuing communication interactions between the robot computing device and the user.

[0090] In some implementations, computer-readable instructions may be executable by one or more processors or controllers on the robot server computing device to combine facial expression datapoints or parameters, audio expression parameters, and / or audio expression datapoints to provide and / or create combined user expression parameters and / or datapoints. In these implementations, the combined user expression parameters and / or datapoints may be utilized by the robot server computing device to determine aggregated expressions and / or feelings of the user and / or child.

[0091] In some implementations, executable computer-readable instructions on the robot computing device and / or the robot company server computing device may utilize the one or more received audio transcription files in order to engage in conversations with the users and / or patient by utilizing the natural language processing software on the robot computing device and / or the robot company server computing device. In some implementations, the robot computing device and / or robot server computing device may not be able to answer questions posed by the user or patient. In these implementations, in step 594, the robot server computing device may communicate the associated audio transcription files to a proprietary or to a third-party natural language processing (NLP) computing device. In some implementations, in step 595, the proprietary or third-party NLP computing device may generate responsive audio transcriptions files and communicate the responsive audio transcription files to the robot server computing device and / or the robot computing device. In some implementations, the responsive audio transcription files may be utilized in communications with the user or patient. In some embodiments, if the audio transcription files are transmitted to the third-party NLP computing device, they may not include the AUID so that the third-party NLP computing device does not have any personally-identifiable information. In some embodiments, the32SUBSTITUTE SHEET (RULE 26)third-party NLP computing device may not store the responsive audio transcription files. In some embodiment, the NLP computing device might consult a knowledge database and / or other cloud-based information or knowledge servers located on the internet to obtain information to create the adequate response. In some implementations, the third- party NLP computing device may be generative artificial intelligence computing devices or servers (e.g., such as OpenAI, Google, or Facebook). Any communication with the third-party NLP computing devices will not include personal identifiers so that the third- party NLP computing device will not know an identity of the users.

[0092] In some embodiments, the Audio Transcript Data may be utilized by the robot computing device to understand content of the captured Audio Data, respond to the user in conversations in multi-turn conversations, and improve the artificial intelligence (Al) or communicability of the robot computing device.

[0093] In some implementations, the robot computing device company has access to the Audio Transcript Data, but cannot link the Audio Transcript Data to any particular user, account or device. This is because the robot computing device company does not have access to the AUTD. Thus, the resource owner themselves must either be using the resource owner software application (and thus request access to the AUTD) or have a copy of the Recovery Key to access or delete the Audio Transcript Data associated with a specific user or child because these will have to be provided to the robot computing device to access the data.

[0094] In some embodiments, in step 596, the robot computing device may create and / or generate Activity Data by analyzing the received Audio Data, the Audio Transcript Data, the Video Data and / or by receiving communications from a robot computing device interactive game or laboratory website 120. In some embodiments, the Activity Data may include information and / or parameters such as how long children are using the robot computing device, if children read a book with the robot computing device , how many missions the children have completed with the robot computing device, badges and trophies earned, and other information to help parent’s track a user’s or child’s general activities and progress in communicating with the robot computing device. In other words, the Activity Data may be summary information about the user’s or child’s activities with the robot computing device. In some embodiments, the Activity Data may include information about the expressions and / or feelings of the user during the interaction with the robot computing device.33SUBSTITUTE SHEET (RULE 26)

[0095] In some embodiments, the robot cloud server device 115 may index the Activity Data with an AUID. In some embodiments, the Activity Data with the indexed AUID may be stored in a database in the robot computing device cloud server device but in a separate database from the other data collected by Moxie (Audio Expression Parameters, Audio Transcript Data, Facial Expression Datapoints, Audio Expression Datapoints, Primary User Audio / Image Datapoints, Moxie Interaction Data, Insight Data, and / or other personal information). In some embodiments, the Activity Data may be encrypted at rest on the robot company’s cloud computing device 115. The Activity Data on a particular child’s interactions and progress is accessible through the Parent App or with the recovery key and linked to the robot ID accessibly by Embodied.

[0096] In some embodiments, in step 597, the system described herein may also create and / or generate Robot Interaction Data. In some embodiments, Robot Interaction Data may be associated with the user’s interactions with the robot computing device. In some embodiments, the Robot Interaction Data may be associated with the Audio Transcript Data (collected through the robot’s microphones), Audio Expression Parameters, Audio Expression Datapoints, Facial Expression Datapoints and Primary User Audio Datapoints, Primary User Image Datapoints (collected through the robot computing device’s camera or imaging device), whether and where other objects or persons may be located in a room (collected through the robot’s camera or imaging device), responses communicated to the robot computing device, and / or what robot facial animations are utilized are utilized on the display or screen of the robot computing device. In some embodiments, the robot computing device may include touch sensors that determine if a child is touching or hugging the robot. In some embodiments, the Robot Interaction Data is collected and processed on robot computing and is utilized to enhance the child’s interaction with the robot computing device and is associated with an AUID of the user or child that is interacting with the robot computing device. In some embodiments, the Robot Interaction Data may be encrypted during transmission to the robot cloud computing device and stored in one or more memory devices of the robot cloud computing device. In some embodiments, the Robot Interaction Data may be stored in the same account as the anonymized Insight Data, Audio Expression Parameters, Audio Transcript Data, Audio Expression Datapoints, Facial Expression and Primary User Audio Datapoints, Primary User Image Datapoints.

[0097] In some embodiments, in step 598, the robot company computing system may also generate Insight Data for users. In some implementations, the Insight Data may be34SUBSTITUTE SHEET (RULE 26)data derived from the robot device company’s artificial intelligence software engine and / or models. In some embodiments, the robot company’s Al software engine (and / or models) may analyze how a child is performing in achieving missions and goals and progressing towards achieving those goals. In other words, the robot company’s Al software engine (and / or models) may analyze Interaction data, Audio / Facial Expression Datapoints, Audio Transcript Data and other data to provide an analytical assessment of a child’s progress. In some embodiments, the Insight Data or parameters may include improvements in language skills, how long the child was engaged with the robot, and / or number of words read per minute. In some embodiments, the Insight Data may be indexed with the AUID. In some embodiments, the Insight Data may be stored in one or more memory devices of the robot cloud computing device for the life of the account (e.g., resource owner’s account). In some embodiments, the resource owner software application may present Activity Data and Insight Data to the resource owner via the resource owner mobile software application.

[0098] In some embodiments, in step 599, the robot computing device may also collect robot sensor and telemetry data. In some embodiments, the robot computing device may communicate the robot sensor and / or telemetry data to the robot company cloud server computing device. In some embodiments, computer-readable instructions executable by the one or more processors on the robot company server computing device may analyze the received sensor and telemetry data from the robot computing device to identify and / or troubleshoot problems. In some embodiments, the received robot computing device may be indexed with a robot identifier, such as a robot ID. In some embodiments, the received robot computing device may be stored in one or more memory devices of the robot cloud server computing device. In some embodiments, robot cloud server computing device may communicate with the robot computing device to provide guidance to help improved hardware and software operations based on the received robot sensor and / or telemetry data. An important aspect of the subject matter disclosed herein is that each user will have their own unique Activity Data, Insight Data, robot interaction data, and robot sensor and telemetry data so the robot computing device experience is personalized for each of the users, children, students and / or patients.

[0099] Figure 8 illustrates a logical representation of accounts in the robot company cloud computing device 800 according to exemplary embodiments. In other words, the robot company cloud server computing device 800 may be able to store multiple resource owner accounts where each of the resource owners have multiple mentor, user, children,35SUBSTITUTE SHEET (RULE 26)student or patient accounts. In other words, there is secure storage for multiple resource owners and the associated one or more mentors or users that have registered with each of the multiple resource owners. Figure 8 illustrates a robot cloud computing device 800 which may include resource owner A’s account 805 and resource owner B’s account 810. In some implementations, an unlimited amount of resource owners may have accounts in the cloud computing device 800. Resource owner A may be a teacher or educator and Resource owner B may be a clinician or a parent with multiple children. In some implementations, resource owner A’s account 805 may include resource owner A’s information, parameters and settings 806. Resource owner A’s parameters and settings may include name and email and other contact information, along with a recovery key as well as other details specific to resource owner A and their interaction with the robot. Further, in some implementations, resource owner A’s account may include mentor account 1 807, mentor account 2 808 and mentor account 3 808. Each of the mentor accounts 807, 808 and 809 may have specific parameters and settings for each of the mentors or users that the resource owner may help set or establish with help from the mentors or users. In addition, each of the mentor accounts (mentor 1 807, mentor 2 808, and mentor 3 809 may have specific and unique AUIDs in order to index and / or identify the mentor or user’s data and / or parameters. As an example, mentor l’s account 807 may have one set of SEL skills development parameters and / or accessibility parameters and mentor 3’s account may have completely different SEL skills development parameters and / or accessibility parameters. Additional categories of types of parameters may also be customized for each of the mentors or users and are described below with regards to FIGS. 6A - 6Z and 7A - 7Z. In some implementations, resource owner B’s account 810 may include resource owner B’s parameters and settings 811 including name and email and other contact information along with a recovery key as well as other details specific to resource owner B and their interaction with the robot. Similarly, in some implementations, resource owner B’s account 810 may also be associated with multiple mentor accounts (e.g., mentor 4’s account 812 and mentor 5’s account 813). Both of resource owner B mentor 4’s and mentor 5’s account may have specific parameters and settings for each of the mentors or users 4 and 5 that the resource owner B may set or establish. In addition, each of the mentor accounts 812 and 813 may have specific and unique AUIDs in order to index and / or identify the mentor or user’s data and / or parameters from other data and / or parameters in the cloud computing device. For example, mentor 4’s account may include parameter settings that no visual display is36SUBSTITUTE SHEET (RULE 26)needed and that the mentor 4 has a specific bedtime so that no interaction is needed. As an additional example, mentor 5’s account may include parameter settings that the mentor likes topics like toys, dinosaurs and travel and that the robot computing device should talk in a slower than normal speech pattern.

[0100] Thus, the storage and indexing and privacy of the mentor and user’s data is something unique. In some embodiments, robot cloud computing device 800 may have accounts for each of the resource owners (e.g., from 1 to 1,000,000 resource owners may be stored in the one or more memory devices of the robot cloud computing device 800), where each of the resource owners accounts will be indexed by a secret key. In some embodiments, the secret key may be created and / or generated from the recovery key that is assigned to the resource owner. In some embodiments, each of the resource owner’s accounts may have one or more mentor or user accounts associated with or assigned to the resource owner’s accounts. In some embodiments, each mentor or user for the resource owner will have a unique AUID and may have their specific account data may be indexed by the AUID.

[0101] In addition, there may be implementations where educational professionals, medical professionals and / or parents of multiple children may want to share data regarding the users, children and / or mentors that they have registered. This may be a voluntary selection. In these embodiments, the parent application software may request (from the parent or guardian, educational professional, and / or medical professional) if there are other resource owners with whom selected data, information, settings, and / or conversation interactions may be shared. In each of these cases, the parent or guardian must consent to the mentor’s, children’s or user’s data being shared about the child or user. In other words, the medical professionals or educational professionals may not make this determination on their own. However, if multiple medical professionals and / or educational professionals may be interacting with one mentor, child or user through one robot computing device and / or multiple robot computing devices, the robot computing device system described above herein may allow for this data, setting and / or information sharing to occur upon request, but only if the necessary consents are obtained.

[0102] In some embodiments, the resource owner may utilize a resource owner software application that is installed on the resource owner’s mobile communication device and that communicates with the robot cloud computing devices. This provides the resource owner with information on how each of the users or children are interacting the robot computing device and provide analytical insights for each user. Figures 6A - 6Z,37SUBSTITUTE SHEET (RULE 26)7 A - 7Z, 9 A - 9D, and 10A - 1OF illustrate screen shots of initialization and operation of an illustrative resource owner software application according to some embodiments. FIG. 6A illustrates an introductory screen according to exemplary embodiments, FIG. 6B illustrates a second introductory screen according to exemplary embodiments and FIG. 6C illustrates a getting started screen according to exemplary embodiments. FIG. 6D illustrates a login screen for a resource owner software application according to exemplary embodiments. In some embodiments, a resource owner may sign into the software application utilizing a resource owner email address into an email address in input area 601. FIG. 6E illustrates a reminder screen in a resource owner software application according to some embodiments where a resource owner is reminded to check their email for a code for backup email verification. FIG. 6F illustrates an email security code entry screen according to some embodiments. FIG. 6G illustrates an account setup screen according to some embodiments and FIG. 6H illustrates a recovery key setup screen according to some embodiments. In exemplary embodiments, a resource owner may enter an email address in field 602, a first name in field 603, a second name in field 604 in FIG. 6G. In exemplary embodiments, a resource owner may see a recovery key and copy or export the recovery key via field 605 in FIG. 6H and store in a safe place. FIG. 61 illustrates a COPPA certification screen according to exemplary embodiments and FIG. 6J illustrates a private policy summary statement screen according to exemplary embodiments.

[0103] FIG. 6K illustrates an add child account screen according to exemplary embodiments. In FIG. 6K, a resource owner may enter a child’s name in field 606, a child’s last name in field 607, and a birthday in field 608. FIG. 6L illustrates a resource provider’s verification screen according to exemplary embodiments. FIG. 6M illustrates a resource provider’s identification selection method according to exemplary embodiments. In FIG. 6M, a resource provider may select between driver’s license verification, credit card verification, and / or social security number verification in field 609. FIG. 6N illustrates a resource provider successful sign in screen according to exemplary embodiments.

[0104] FIG. 60 illustrates a WiFi entry screen in a resource provider software application according to exemplary embodiments. FIG. 6P illustrates a QR code scan screen according to exemplary embodiments. FIG. 6Q illustrates a connecting tips screen according to exemplary embodiments. FIG. 6R illustrates a WiFi connection screen in a resource provider software application according to exemplary embodiments. FIG. 6S38SUBSTITUTE SHEET (RULE 26)illustrates a robot computing device environment setup screen according to exemplary embodiments. FIG. 6T illustrates a setup environment screen according to exemplary embodiments. FIG. 6U illustrates a second setup environment screen according to exemplary embodiments. FIG. 6V illustrates a connection success screen according to exemplary embodiments.

[0105] FIG. 6W illustrates a child information entry screen according to exemplary embodiments. In FIG. 6W, the child information entry screen may include a mentor or child’s first name field 611, a child’s last name field 612, a child’s birthday field 613, and / or a child or user’s nickname field 614. In exemplary embodiments, the child information entry screen may include additional fields such as a chattiness or communication style field 615, and / or a user predictability field 616. FIG. 6X illustrates a robot computing device appearance customization screen according to exemplary embodiments. In FIG. 6X, a resource owner may select a customized robot computing device appearance for each user by selecting an eye color field 617 and / or a skin color field 618. FIG. 6Y illustrates a robot computing device user accessibility customization screen according to exemplary embodiments. In FIG. 6Y, a robot user accessibility customization screen may include a limited heads-up display field 620, a no sound effects field 621, a no visual effects field 622 and / or a slowed down speech field 623. FIG. 6Z illustrates an add additional user or child input screen according to exemplary embodiments. This screen is a unique and novel feature of the resource owner software application. In exemplary embodiments, FIG. 6Z illustrates an add child field or icon 625 that allows a resource owner to add another child through going the steps outlined in FIGS. 6K - 6Y. FIG. 7 A illustrates a robot computing device ready finalization screen according to exemplary embodiments and FIG. 7B illustrates a robot computing device play initialization screen according to exemplary embodiments.

[0106] FIG. 7C illustrates an account information screen for resource owner software application according to exemplary embodiments. The input fields of resource owner first name, resource owner second name and email address have already been discussed above. In exemplary embodiments, a resource owner may be able to change a resource owner’s email via field 701, revoke data sharing consent for themselves or users via field 702 and / or a deactivate an account via field 703. FIG. 7D illustrates an account status screen or menu for a resource owner software application for robot computing device according to exemplary embodiments. In FIG. 7D, a resource owner may allow notifications to be set in field 704, may activate notifications when a robot’s battery is39SUBSTITUTE SHEET (RULE 26)low via field 705 and may also activate tips or advice notifications via field 706. As illustrated in FIG. 7D, the resource owner robot computing device software application may include four main submenus, each with icons on a bottom of a screen. In exemplary embodiments, the submenus or icons may be a Moxie or robot icon 707, a resources icon 708, an insights icon 709 and / or an account icon 710 (which is what is shown in FIG. 7D).

[0107] FIG. 7E illustrates a deactivate screen or menu according to exemplary embodiments. In FIG. 7E, a resource owner can deactivate their account and erase all data associated with the account. In exemplary embodiments, the erasing of data may be permanent. FIG. 7F illustrates a sign out screen according to exemplary embodiments.

[0108] FIG. 7J illustrates an insights menu for one mentor or user associated with a resource owner according to exemplary embodiments. In FIG. 7J, the insights menu may show insight data for one mentor or user 717 (which may be changed to another mentor or user which is a unique and novel aspect). In FIG.7J, the insights menu may show an amount of time in activities via graph 716, a number of missions completed, a number of badges earned, an elected theme, an academic skills range score 718, a social skills range score 719, and / or an emotional intelligence range score 720. FIG. 7G illustrates an activity submenu or screen of an insights tab in a resource owner’s robot software application according to exemplary embodiments. In FIG. 7G, the activity submenu may include a) a graph 711 illustrating activity in a last set time period (e.g., a week), b) a length of a current chat session with the robot computing device or a length of a selected activity (as shown in the Moxie chat field 712), and / or c) a length of a clearance check session with a robot computing device (as shown in Clearance check field 713) or a length of another activity. FIG. 7H illustrates a badges submenu or screen 714 of an insights tab in a resource owner’s robot software application according to exemplary embodiments. FIG. 71 illustrates a missions submenu or screen 715 according to exemplary embodiments. FIG. 7K illustrates a screen or menu allowing a resource owner to switch between insights report (e.g., FIG. 7J) between users or menu. This allows easy viewing of progress of multiple users or children.

[0109] FIG. 7Q illustrates a Moxie Active Menu or screen for a resource owner robot software application according to exemplary embodiments. In FIG. 7Q, the robot active menu includes an icon or field 750 to switch between mentors, children or users. In FIG. 7Q, in exemplary embodiments, the active menu or screen may show an active child, a40SUBSTITUTE SHEET (RULE 26)robot battery status, a settings icon, a speaker volume icon and / or a scheduling icon or field 721.

[0110] FIG. 7L illustrates a mentor information selection screen / option according to exemplary embodiments. In FIG. 7L, a resource owner may select between a child information screen / option 722, a robot customization screen / option 723 according to exemplary embodiments, a chat topics screen / option 724, an activity preferences screen / option 725, a learning focus screen / option 726 and / or an interaction style or accessibility screen / option 727 according to exemplary embodiments.[OHl] FIG. 7M illustrates an activity preference screen or menu according to exemplary embodiments. In FIG. 7M, a resource owner may select different activity options for a child, mentor or user such as creative play, calming activities, reading books aloud, movement activities, playful or interactive games and / or solving riddles or puzzles. FIG. 7N illustrates a mentor or user’s interest screen. In some implementations, a mentor interest screen may allow selection of specific individual mentor, child or user’s interests. In some implementations, for example, the specific interest or topics may include but are not limited to robots, school, sports, toys, grown-up jobs, dinosaurs, art and / or animals. In some implementations, a free text box (not shown in figure 7N) might be used to collect a textual description of the user’s interests. FIG. 70 illustrates an SEL Skills Development selection menu or screen according to exemplary embodiments. In some implementations, the SEL selection screen may allow a user to select skill level for individual users, children or mentors of a high or low self-awareness level for a selected user or mentor; a high or low self-management level or managing emotions for a selected user or mentor; and / or a high or low social awareness (understanding social norms) level for a selected user or mentor, a developing positive relationships and communication skills level, an understanding emotions in others or empathy or compassion level. FIG.7P illustrates a robot computing device physical settings menu or screen according to exemplary embodiments. In exemplary embodiments, a resource owner may select a face brightness level 731, a touch to wake settings option 732, a wake button option 733 and / or an audio wave sensitivity option 734. These wake options allow different ways of waking up the robot computing device from a sleep stage.

[0112] FIG. 7R illustrates a scheduling menu or screen for a user or mentor according ot exemplary embodiments. In FIG. 7R, the scheduling menu or screen 735 may include a bedtime schedule option 736, a sensitive communications option 737, a play date scheduling option 738 and / or an events or holiday scheduling or identification options41SUBSTITUTE SHEET (RULE 26)739. In some implementations, the resource owner can utilize this screen to identify sensitive conversation topics for the user / mentor, when the user should go to bed, when the user or mentor has playdates and important events or holidays of the user or mentor. Again, this allows unique setups for each of the children, users or mentors.

[0113] FIG. 7S illustrates a robot computing device active user menu or screen according to exemplary embodiments. In FIG. 7S, a mentor may either add / or edit other user profiles via field or icon 740 and / or may switch to another child / mentor or user via icon or field 741. FIG. 7T illustrates a switch active user / child menu or screen according to exemplary embodiments. In FIG. 7T, when a resource owner switches active users, the switch active child menu or screen 742 may appear and a resource owner may select from a plurality of users (e.g., in FIG. 7T, the different users may be Aria Bennett 743, Elijah Parker 744, or Isabel Ramirez 745). FIG. 7U illustrates an add or edit user / child menu or screen according to exemplary embodiments. If a resource provider selects an add or edit menu, the resource provider robot software application may display the add or edit menu or screen 746 which lists the children, users, or mentors the resource owner may have registered through the resource owner robot software application. In some implementations, the user or mentor information may include name, birthday, age and / or other information as well as a status (e.g., registered, pending parental consent, etc.) for each of the children or users.

[0114] In some implementations, a resource owner may select different resources that a resource owner can utilize to interface between the child / user and / or the robot computing device. These resources may be accessed utilizing the Resources tab. FIG. 10A illustrates a resources screen or menu according to exemplary embodiments. In FIG. 10A, a resources menu 1005 may allow a resource owner to select a number of resource categories such as tips for success 1006, a parent tutorials category 1007, a moxie commands category 1008, a mission set guides category 1009, a moxie activities category 1010 and / or an add / switch child category 1011. FIG. 7V illustrates an instructions screen of the resource owner robot software application according to exemplary embodiments. In FIG. 7V, the software application may display instructions to switch between children or user and / or to add children or users to the resource owner’s list of registered children. FIG. 7W illustrates archived messages for a resource owner and / or children or users according to exemplary embodiments. FIG. 7X illustrates mission set guides for a resource owner’s software application according to exemplary embodiments. In FIG. 7X, the list of mission set guides in the mission set guides screen or menu may include a42SUBSTITUTE SHEET (RULE 26)number of guides or references including, but not limited to, an understanding emotions mission guide, a making friends mission guide, a being kind mission guide, a knowing your space mission guide, a being helpful mission guide, a making mistakes mission guide, and / or a missing people mission guide. FIG. 10B illustrates a Moxie or robot computing device commands screen or menu according to embodiments. FIG. IOC illustrates a parent tutorials screen or menu according to embodiments. FIG. 10D illustrates a robot computing devices activities menu according to embodiments. In FIG. 10B, a robot computing device commands screen or menu provides a list of robot computing device commands, which may include but are not limited to a Hello, Moxie, Moxie please wake up, Moxie Go to Sleep, Moxie Please Do something else (which moves to a different activity or Moxie please repeat that (which repeats the last response by the robot computing device), Moxie earmuffs (only respond to a command Moxie listen to me), Moxie Please listen to me (rotates to person last speaking). FIG. IOC provide access to parent tutorials to teach resource owners or parents a best way of interacting with the robot computing device. FIG. 10D provides a list of potential robot computing device activities such as affirmation, animal breathing, body scan, brain twisters, dance, draw and / or events or holidays. Additional activities may be name that feeling, password, picture pose, reading, scavenger hunt, Simon says, stories, tell a story and / or this day in history. FIG. 10E illustrates a Tips for Success menu or screen according to exemplary embodiments. In some implementations, the Tips for Success menu may include tips for how a parent should teach their children how to interact with a robot computing device as well as ideal environments for a robot computing device along with specific commands to utilize with the robot computing device. FIG. 10F illustrates a help screen or menu according to exemplary embodiments. In exemplary embodiments, the help screen or menu may include a support email 1051, a support telephone number 1052, a support text message number 1053, a frequently asked questions or parents guide link 1054, a face icons guide link 1055 and / or a privacy policy link 1056.

[0115] In exemplary embodiments, the resource owner may also be able to monitor insights for each of the mentors or users. This is a unique feature of the multiuser software in that insight data (cognitive parameters, social parameters, and / or emotional parameters) may be monitor for a number of mentors who each are interfacing with the robot computing device. Figure 9A illustrates an overall insight screen or menu according to some implementations. In some implementations, the overall insight screen 900 may include a hour activity monitor 905, a completed mission parameter or value43SUBSTITUTE SHEET (RULE 26)906, a completed or earned badges parameter or value 907, a time period parameter 908, a cognitive insight parameter 909, a social insight parameter 910 and / or an emotional insight parameter 911. In some implementations, a time period parameter or value 908 may identify a timeframe for which the insight parameters were collected from the mentor’s interaction with the robot computing device (e.g., in Figure 9A the timeframe is January 5 - 11). In some implementations, the hour activity monitor 905 may display an amount of time one specific mentor or user may have spent or interacted with the robot computing device. In some implementations, a completed mission parameter 906 may identify how many missions a specific mentor or user has completed in the specified timeframe. In some implementations, an earned badges parameter 907 may identify how many badges or awards a mentor or user has earned in interacting with the robot computing device in the specified time frame. In some implementations, an overall cognitive graph 909 may display a mentor’s cognitive score in a graph format and a cognitive trending percentage during a specified timeframe. In some implementations, an overall social graph 910 may display a mentor’s social score in a graph format and a social trending percentage during a specified timeframe. In some implementations, an overall emotional graph 911 may display an emotional score in a graph format and an emotion trending percentage during a specified timeframe.

[0116] Figure 9B illustrates a cognitive insight screen according to some implementations. In some implementations, a cognitive insight screen 915 may include a cognitive insight score in a graph form and also a cognitive insight trending percentage916. In some implementations, the cognitive insight score may include cognitive STAR Goals where a robot’s content contains questions that are targeted towards cognitive goals, such as inferencing, predicting, reading comprehension, and understanding themes such as making mistakes and helpfulness. In some implementations, during conversations between a robot computing device and a mentor or child, cognitive STAR goal scores are calculated based on a mentor’s responses to these targeted questions. In some implementations, a cognitive insight screen may include a suggestions panel or screen917, where the suggestions panel or screen provides an activity to improve or enhance a mentor’s cognitive insight score and / or a mentor’s cognitive development. In some implementations, a cognitive insight screen may also include adjective usage values 918, number of wh — type questions (e.g., what, why, who, where) 919, a number of books read by a mentor or user (not shown) and / or a mentor or user’s reading time (in terms of the mentor reading to the robot computing device).44SUBSTITUTE SHEET (RULE 26)

[0117] Figure 9C illustrates a social insight screen according to some implementations. In some implementations, a social insight screen 920 may include a social insight score in graph form 921. In some implementations, a social insight score may include Social STAR Goals, which are calculated based on a robot computing device’s content contains questions that are targeted towards social goals, such as asking questions, answering “wh” questions, and understanding themes including Making Friends and Kindness. In some implementations, during conversation between the robot computing device and a mentor or user, social STAR goals are calculated based on a mentor or user’s responses to these targeted questions. In some implementations, a social insight screen may include a social suggestion screen 922, where the social suggestion screen includes an activity to increase a social insight score such as asking a followup question when a user or mentor responds with a single word response. In some implementations, a social insight screen 920 may also include a words per second value 923 for a mentor or use, an eye gaze value 924 for a mentor or user to talk to a robot computing device; an engagement time value which keeps track of the amount of time a mentor or user spends actively engaged with the robot computing device including sitting in robot’s field of view, responding to robot computing device’s questions, and participating in content; a turn balance value which tracks a percentage of how much a user contributes to an interaction with the robot, and / or an average utterance length which keeps track of an average number of words a mentor or user says in a sentence with a conversation interaction with a robot computing device.

[0118] Figure 9D illustrates an emotional insight screen according to some implementations. In some implementations, an emotional insight screen 925 includes an emotional insight score in a graph form 926 for a timeframe. In some implementations, an emotional insight score may be calculated based on an Emotional STAR Goals, wherein an emotional star goal is calculated based on a robot’s content contains questions that are targeted towards emotional goals, such as understanding emotions in self and others, and knowledge of self-regulation strategies. In some implementations, during conversations between a robot computing device and a mentor or user, emotional STAR goals may be calculated based on a mentor or user’s responses to these targeted questions. In some implementations, an emotional insight screen 925 may include an emotional suggestion panel 927 including suggestions for activities to improve a mentor or user’s emotional insight, such as providing calming strategies to a mentor or child. In some implementations, an emotional insight screen may include a time spent smiling value 928,45SUBSTITUTE SHEET (RULE 26)a smile intensity value 929, a mindfulness exercise value which keeps track of an amount of time a mentor or child has spent engaged in regulation activities (such as mindfulness journeys and animal breathing), and / or an empathy badge value which represents a number of badges a child or mentor has earned with the robot computing device centered around teaching empathy.

[0119] A method to allow a resource owner to allow multiple users to interact with a robot computing device includes one or more processors; one or more memory devices; computer-readable instructions, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to communicate resource owner registration parameters to a cloud computing device to identify a resource owner to control communication between the robot computing device and a plurality of users; communicate registration instructions to a cloud computing device to register a first user to interface with the robot computing device; transmit first user robot communication parameters to the cloud computing device to identify first user preferences in interfacing with the robot computing device; communicate registration instructions to the cloud computing device to register a second user to interface with the robot computing device; and transmit second user robot communication parameters to the cloud computing device to identify second user preferences to interface with the robot computing device.

[0120] In some implementations, the first user preferences are different from the second user preferences. In some implementations, the first user preferences and the second user preferences include a brightness parameter, a volume parameter, a timeframe of use parameter, a sensitive conversation parameter, a scheduling parameter, or a game website access parameter. In some implementations, the first user preferences and the second user preferences include a heads-up display parameter, a sound effects parameter, a visual effects parameter, a speech speed parameter, or a response or pause time parameter. In some implementations, the first user preferences and the second user preferences include a talkative scale parameter or a routine consistency parameter. In some implementations, the first user preferences and the second user preferences include topics of interest or activities of interest for the first user or the second user.

[0121] In exemplary embodiments, the computer-readable instructions accessed from the one or more memory devices and are executable by the one or more processors to receive privacy parameters on data collection from a third-party computing device; communicate a message to a resource owner computing device to request that registered users consent to the received privacy parameters on data collection; receive verification46SUBSTITUTE SHEET (RULE 26)from a third-party computing device that a first user or the first user’s parent or guardian has consented to privacy parameters on data collection by the robot computing device; receive verification from a third-party computing device that the second user or the second user’s parent or guardian has consented to privacy parameters on data collection by the robot computing device, and display, on a screen of a resource owner’s computing device, a list of the plurality of users that have completed a registration process. In exemplary embodiments, the computer-readable instructions executable by the one or more processors may generate a first analytics user identifier for the first user after completion of registration for the first user, the first analytics user identifier configured to be utilized as an index for specific data collected by the robot computing device about the first user; generate a second analytics user identifier for the second user after completion of registration for the second user, the second analytics user identifier configured to be utilized as an index for specific data collected by the robot computing device about the second user.

[0122] In exemplary embodiments, a method for multiple users to sequentially communicate with a robot computing device may include one or more processors; one or more memory devices; computer-readable instructions, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to display, on a screen of a resource owner’s computing device, a list of the plurality of users that have completed a registration process with the resource owner with respect to the robot computing device; select a first user to interface with the robot computing device; communicate first user communication preference parameters to the cloud-computing device to establish guidelines for communication interactions between the first user and the robot computing device; establish communications between the robot computing device and the first user, wherein the robot computing device and / or a cloud computing device collects information from one or more conversation interactions with the first user and stores portions of the collected information in one or more memory devices of the cloud computing device; terminate the communication interaction between the robot computing device and the first user; select a second user to interface with a robot computing device; communicate second user communication preference parameters to the cloud-computing device to establish guidelines for communication interactions between the second user and the robot computing device; and establish communications between the robot computing device and the second user, wherein the robot computing device and / or a cloud computing device collects information from one or more47SUBSTITUTE SHEET (RULE 26)conversation interactions with the second user and stores portions of the collected information in the one or more memory devices of the cloud computing device.

[0123] In some implementations, the collected information stored in the one or more memory devices may include facial expression datapoints of a first user, audio transcription files of the one or more conversation interactions with the first user and the robot computing device, facial expression datapoints of the second user, and audio transcription files of the one or more conversation interactions with the second user and the robot computing device. In some implementations, the collected information stored in the one or more memory devices may include whether and where other objects or persons may be located in a room (collected through the robot’s camera or imaging device) with the first user, responses communicated to the robot computing device by the first user, and / or what robot facial animations are utilized on the display or screen of the robot computing device during conversation interactions with the first user; whether and where other objects or persons may be located in a room (collected through the robot’s camera or imaging device) with the second user, responses communicated to the robot computing device by the second user, and / or what robot facial animations are utilized on the display or screen of the robot computing device during conversation interactions with the second user.

[0124] In some implementations, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to generate first user activity data from the collected information for the first user wherein the activity data includes number of books read, calculated reading comprehension, calculated vocabulary level, amount of time spent interacting with the robot computing device, amount of time spent on an activity like reading, badges or trophies received, and / or different activities in which the first user engaged; generate second user activity data from the collected information for the second user wherein the activity data includes number of books read, calculated reading comprehension, calculated vocabulary level, amount of time spent interacting with the robot computing device, amount of time spent on an activity like reading, badges or trophies received, and / or different activities in which the second user engaged; and store the first user activity data and the second user activity data in the one or more memory devices of the cloud computing device.

[0125] In exemplary embodiments, the computer-readable instructions accessed from the one or more memory devices and executable by the one or more processors may generate first user insight data from the collected information for the first user wherein48SUBSTITUTE SHEET (RULE 26)the insight data includes progress against a first user’s social educational learning goal parameters; generate second user insight data from the collected information for the second user wherein the insight data includes progress against a second user’s social educational learning goal parameters; and store the first user insight data and the second user insight data in the one or more memory devices of the cloud computing device.

[0126] In some implementations, the first user communication preference parameters and the second user communication preference parameters include a brightness value, a volume value, a timeframe of use value, a sensitive conversation parameter, a scheduling parameter, or a game website access parameter. In some implementations, the first user communication preference parameters and the second user communication preference parameters may include a heads-up display parameter, a sound effects parameter, a visual effects parameter, a speech speed parameter, and / or a response time parameter. In some implementations, the first user communication preference parameters and the second user communication preference parameters include topics of interest and activities of interest. In some implementations, the first user communication preference parameters and the second user communication preference parameters may include a talkative scale parameter or a routine consistency parameter. In some implementation, the first user communication preference parameters may include social educational learning (SEL) parameter goals, the SEL parameter goals including self-awareness goal values, selfmanagement goal values, social awareness goal values, relationship goal values, and cognitive skill goal values.

[0127] As detailed above, the computing devices and systems described and / or illustrated herein broadly represent any type or form of computing device or system capable of executing computer-readable instructions, such as those contained within the modules described herein. In their most basic configuration, these computing device(s) may each comprise at least one memory device and at least one physical processor.

[0128] The term “memory” or “memory device,” as used herein, generally represents any type or form of volatile or non-volatile storage device or medium capable of storing data and / or computer-readable instructions. In one example, a memory device may store, load, and / or maintain one or more of the modules described herein. Examples of memory devices comprise, without limitation, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical disk drives, caches, variations or combinations of one or more of the same, or any other suitable storage memory.49SUBSTITUTE SHEET (RULE 26)

[0129] In addition, the term “processor” or “physical processor,” as used herein, generally refers to any type or form of hardware-implemented processing unit capable of interpreting and / or executing computer-readable instructions. In one example, a physical processor may access and / or modify one or more modules stored in the above-described memory device. Examples of physical processors comprise, without limitation, microprocessors, microcontrollers, Central Processing Units (CPUs), Field- Programmable Gate Arrays (FPGAs) that implement softcore processors, Application- Specific Integrated Circuits (ASICs), portions of one or more of the same, variations or combinations of one or more of the same, or any other suitable physical processor.

[0130] Although illustrated as separate elements, the method steps described and / or illustrated herein may represent portions of a single application. In addition, in some embodiments one or more of these steps may represent or correspond to one or more software applications or programs that, when executed by a computing device, may cause the computing device to perform one or more tasks, such as the method step.In addition, one or more of the devices described herein may transform data, physical devices, and / or representations of physical devices from one form to another. For example, one or more of the devices recited herein may receive image data of a sample to be transformed, transform the image data, output a result of the transformation to determine a 3D process, use the result of the transformation to perform the 3D process, and store the result of the transformation to produce an output image of the sample. Additionally or alternatively, one or more of the modules recited herein may transform a processor, volatile memory, non-volatile memory, and / or any other portion of a physical computing device from one form of computing device to another form of computing device by executing on the computing device, storing data on the computing device, and / or otherwise interacting with the computing device.

[0131] The term “computer-readable medium,” as used herein, generally refers to any form of device, carrier, or medium capable of storing or carrying computer-readable instructions. Examples of computer-readable media comprise, without limitation, transmission-type media, such as carrier waves, and non-transitory-type media, such as magnetic-storage media (e.g., hard disk drives, tape drives, and floppy disks), optical- storage media (e.g., Compact Disks (CDs), Digital Video Disks (DVDs), and BLU-RAY disks), electronic-storage media (e.g., solid-state drives and flash media), and other distribution systems.50SUBSTITUTE SHEET (RULE 26)

[0132] A person of ordinary skill in the art will recognize that any process or method disclosed herein can be modified in many ways. The process parameters and sequence of the steps described and / or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and / or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed.

[0133] The various exemplary methods described and / or illustrated herein may also omit one or more of the steps described or illustrated herein or comprise additional steps in addition to those disclosed. Further, a step of any method as disclosed herein can be combined with any one or more steps of any other method as disclosed herein.

[0134] Unless otherwise noted, the terms “connected to” and “coupled to” (and their derivatives), as used in the specification and claims, are to be construed as permitting both direct and indirect (i.e., via other elements or components) connection. In addition, the terms “a” or “an,” as used in the specification and claims, are to be construed as meaning “at least one of.” Finally, for ease of use, the terms “including” and “having” (and their derivatives), as used in the specification and claims, are interchangeable with and shall have the same meaning as the word “comprising.

[0135] The processor as disclosed herein can be configured with instructions to perform any one or more steps of any method as disclosed herein.

[0136] As used herein, the term “or” is used inclusively to refer items in the alternative and in combination.

[0137] As used herein, characters such as numerals refer to like elements.

[0138] Embodiments of the present disclosure have been shown and described as set forth herein and are provided by way of example only. One of ordinary skill in the art will recognize numerous adaptations, changes, variations and substitutions without departing from the scope of the present disclosure. Several alternatives and combinations of the embodiments disclosed herein may be utilized without departing from the scope of the present disclosure and the inventions disclosed herein. Therefore, the scope of the presently disclosed inventions shall be defined solely by the scope of the appended claims and the equivalents thereof.51SUBSTITUTE SHEET (RULE 26)

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A method to allow a resource owner to allow multiple users to interact with a robot computing device, comprising: one or more processors; one or more memory devices; computer-readable instructions, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to: communicate resource owner registration parameters to a cloud computing device to identify a resource owner to control communication between the robot computing device and a plurality of users; communicate registration instructions to a cloud computing device to register a first user to interface with the robot computing device; transmit first user robot communication parameters to the cloud computing device to identify first user preferences in interfacing with the robot computing device; communicate registration instructions to the cloud computing device to register a second user to interface with the robot computing device; and transmit second user robot communication parameters to the cloud computing device to identify second user preferences to interface with the robot computing device.

2. The method of claim 1, wherein the first user preferences are different from the second user preferences.

3. The method of claim 1, wherein the first user preferences or the second user preferences include a brightness parameter, a volume parameter, a timeframe of use parameter, a sensitive conversation parameter, a scheduling parameter, or a game website access parameter.

4. The method of claim 1, wherein the first user preferences and the second user preferences include a heads-up display parameter, a sound effects parameter, a visual effects parameter, a speech speed parameter, or a response or pause time parameter.

5. The method of claim 1, wherein the first user preferences and the second user preferences include a talkative scale parameter or a routine consistency parameter.

6. The method of claim 1, wherein the first user preferences and the second user preferences include topics of interest or activities of interest for the first user or the second user.52SUBSTITUTE SHEET (RULE 26)7. The method of claim 1, the computer-readable instructions accessed from the one or more memory devices and executable by the one or more processors to: receive privacy parameters on data collection from a third-party computing device; and communicate a message to a resource owner computing device to request that registered users consent to the received privacy parameters on data collection.

8. The method of claim 1, the computer-readable instructions accessed from the one or more memory devices and executable by the one or more processors to: receive verification from a third-party computing device that a first user or the first user’s parent or guardian has consented to privacy parameters on data collection by the robot computing device.

9. The method of claim 8, the computer-readable instructions accessed from the one or more memory devices and executable by the one or more processors to: receive verification from a third-party computing device that the second user or the second user’s parent or guardian has consented to privacy parameters on data collection by the robot computing device.

10. The method of claim 1, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to: display, on a screen of a resource owner’s computing device, a list of the plurality of users that have completed a registration process.

11. The method of claim 1, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to: generate a first analytics user identifier for the first user after completion of registration for the first user, the first analytics user identifier configured to be utilized as an index for specific data collected by the robot computing device about the first user; and generate a second analytics user identifier for the second user after completion of registration for the second user, the second analytics user identifier configured to be utilized as an index for specific data collected by the robot computing device about the second user.

12. A method for multiple users to sequentially communicate with a robot computing device, comprising: one or more processors; one or more memory devices;53SUBSTITUTE SHEET (RULE 26)computer-readable instructions, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to: display, on a screen of a resource owner’s computing device, a list of the plurality of users that have completed a registration process with the resource owner with respect to the robot computing device; select a first user to interface with the robot computing device; communicate first user communication preference parameters to the cloudcomputing device to establish guidelines for communication interactions between the first user and the robot computing device; establish communications between the robot computing device and the first user, wherein the robot computing device and / or a cloud computing device collects information from one or more conversation interactions with the first user and stores portions of the collected information in one or more memory devices of the cloud computing device; terminate the communication interaction between the robot computing device and the first user; select a second user to interface with a robot computing device; communicate second user communication preference parameters to the cloudcomputing device to establish guidelines for communication interactions between the second user and the robot computing device; and establish communications between the robot computing device and the second user, wherein the robot computing device and / or a cloud computing device collects information from one or more conversation interactions with the second user and stores portions of the collected information in the one or more memory devices of the cloud computing device.

13. The method of claim 12, wherein the collected information stored in the one or more memory devices includes facial expression datapoints of a first user, audio transcription files of the one or more conversation interactions with the first user and the robot computing device, facial expression datapoints of the second user, and audio transcription files of the one or more conversation interactions with the second user and the robot computing device.

14. The method of claim 12, wherein the collected information stored in the one or more memory devices further includes whether and where other objects or persons may be located in a room (collected through the robot’s camera or imaging device) with the first user, responses communicated to the robot computing device by the first user,54SUBSTITUTE SHEET (RULE 26)and / or what robot facial animations are utilized on the display or screen of the robot computing device during conversation interactions with the first user; and wherein the collected information stored in the one or more memory devices further includes whether and where other objects or persons may be located in a room (collected through the robot’s camera or imaging device) with the second user, responses communicated to the robot computing device by the second user, and / or what robot facial animations are utilized on the display or screen of the robot computing device during conversation interactions with the second user.

15. The method of claim 12, the computer-readable instructions accessed from the one or more memory device and executable by the one or more processors to generate first user activity data from the collected information for the first user wherein the activity data includes number of books read, calculated reading comprehension, calculated vocabulary level, amount of time spent interacting with the robot computing device, amount of time spent on an activity like reading, badges or trophies received, and / or different activities in which the first user engaged; generate second user activity data from the collected information for the second user wherein the activity data includes number of books read, calculated reading comprehension, calculated vocabulary level, amount of time spent interacting with the robot computing device, amount of time spent on an activity like reading, badges or trophies received, and / or different activities in which the second user engaged; and store the first user activity data and the second user activity data in the one or more memory devices of the cloud computing device.

16. The method of claim 12, the computer-readable instructions accessed from the one or more memory devices and executable by the one or more processors to generate first user insight data from the collected information for the first user wherein the insight data includes progress against a first user’s social educational learning goal parameters; generate second user insight data from the collected information for the second user wherein the insight data includes progress against a second user’s social educational learning goal parameters; and store the first user insight data and the second user insight data in the one or more memory devices of the cloud computing device.

17. The method of claim 12, wherein the first user communication preference parameters and the second user communication preference parameters include a55SUBSTITUTE SHEET (RULE 26)brightness value, a volume value, a timeframe of use value, a sensitive conversation parameter, a scheduling parameter, or a game website access parameter.

18. The method of claim 12, wherein the first user communication preference parameters and the second user communication preference parameters include a heads-up display parameter, a sound effects parameter, a visual effects parameter, a speech speed parameter, and / or a response time parameter.

19. The method of claim 12, wherein the first user communication preference parameters and the second user communication preference parameters include topics of interest and activities of interest.

20. The method of claim 12, wherein the first user communication preference parameters and the second user communication preference parameters include a talkative scale parameter or a routine consistency parameter.

21. The method of claim 1, wherein the preferences include social educational learning (SEL) parameter goals, the SEL parameter goals including self-awareness goal values, self-management goal values, social awareness goal values, relationship goal values, and cognitive skill goal values.56SUBSTITUTE SHEET (RULE 26)

Images