Systems and methods for accessory management

Abstract

Systems and methods described herein provide for mobile device accessory management. In one implementation, a mobile device accessory is identified. An attachment status of the mobile device accessory relative to the mobile device is determined. Operation of the mobile device is controlled according to the attachment state of the mobile device accessory, and the operation of the mobile device is adjusted based on an accessory profile corresponding to the mobile device accessory.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 356,799, filed on June 29, 2022, and U.S. Provisional Application No. 63 / 356,791, filed on June 29, 2022. Each of these applications is incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure relate to systems and methods for accessory management, and more particularly to managing mobile device accessories for a mobile device and / or monitoring accessories for a mobile device. Background Art

[0004] Mobile device accessories can be used with mobile devices for a variety of purposes. Various conditions may arise that affect the operation of the mobile device and / or the mobile device accessories. However, during operation of the mobile device, it is often challenging to identify and respond to such conditions in a timely manner. In addition, adjusting the operation of the mobile device after use is initiated often creates latency issues and other problems. Furthermore, it is challenging to predict how a particular mobile device accessory may affect the operation of a particular mobile device. Summary of the invention

[0005] The embodiments described and claimed herein solve the above problems by providing systems and methods for mobile device accessory management. In some embodiments, a mobile device accessory is identified. An attachment state of the mobile device accessory relative to a mobile device is determined. Operation of the mobile device is controlled based on the attachment state of the mobile device accessory, and the operation of the mobile device is adjusted based on an accessory profile corresponding to the mobile device accessory.

[0006] In some implementations, a mobile device accessory is identified. An attachment state of the mobile device accessory relative to the mobile device is determined. When the attachment state is identified as attached, an operation of the mobile device is adjusted based on an accessory profile. The accessory profile corresponds to the mobile device accessory. When the attachment state is identified as unattached, the adjustment of the operation of the mobile device is abandoned.

[0007] In some implementations, the accessory management system is configured to determine an attachment state of a mobile device accessory relative to a mobile device. The control system is configured to control an operation of the mobile device based on the attachment state of the mobile device accessory. The operation of the mobile device is adjusted based on an accessory profile corresponding to the mobile device accessory.

[0008] In some implementations, a first accessory state of a mobile device accessory is obtained. The first accessory state corresponds to an expected behavior of the mobile device accessory. Accessory data corresponding to the mobile device accessory is obtained. A second accessory state of the mobile device accessory is determined based on the accessory data. The second accessory state corresponds to a behavior of the mobile device accessory. An event that affects at least one of a mobile device operation of a mobile device or an accessory operation of the mobile device accessory is identified by comparing the expected behavior of the mobile device accessory with the behavior of the mobile device accessory. A response to the event is determined.

[0009] In some implementations, one or more sensors are configured to capture accessory data corresponding to a mobile device accessory. A monitoring system is configured to identify an event that affects at least one of a mobile device operation of a mobile device or an accessory operation of the mobile device accessory by comparing a first accessory state of the mobile device accessory with a second accessory state of the mobile device accessory. The monitoring system determines a response to the event.

[0010] Other specific implementations are also described and listed herein. In addition, although multiple specific implementations are disclosed, other specific implementations of the technology disclosed in the present invention will become apparent to those skilled in the art from the following detailed description showing and describing exemplary specific implementations of the technology disclosed in the present invention. As will be appreciated, the technology disclosed in the present invention may be modified in various aspects without departing from the spirit and scope of the technology disclosed in the present invention. Therefore, the drawings and specific embodiments are to be regarded as illustrative rather than restrictive in nature. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 An example environment for mobile device accessory management is shown.

[0012] Figure 2 An example environment for mobile device accessory monitoring is shown.

[0013] Figure 3 An example mobile device is shown.

[0014] Figure 4 Example operations for mobile device accessory management are shown.

[0015] Figure 5 Other example operations for mobile device accessory management are shown.

[0016] Figure 6 Other example operations for mobile device accessory management are shown.

[0017] Figure 7 is an example computing system that may implement various aspects of the presently disclosed technology. DETAILED DESCRIPTION

[0018] Various aspects of the currently disclosed technology relate to systems and methods for mobile device accessory management. In one aspect, the system and method actively and dynamically adjust the operation of a mobile device based on a mobile device accessory. Different mobile device accessories can affect the operation of a mobile device in various ways. In addition, the operation of a first mobile device can be affected by the mobile device accessory differently from that of a second mobile device. For example, a mobile device accessory can be attached to a mobile device configured to move from a first position toward a second position. The system and method discussed herein determine the overall device configuration of a mobile device as modified by a mobile device accessory, and control the operation of a mobile device associated with movement based on the overall device configuration. In some aspects, a mobile device accessory is identified, which may include identifying the presence of a mobile device accessory near a mobile device and obtaining an accessory profile of the mobile device accessory. For example, an accessory profile can be obtained using a visual identifier (e.g., a quick response (QR) code), a transmitted identifier, etc. The attachment state of a mobile device accessory relative to a mobile device can be determined. When the attachment state of a mobile device accessory is identified as attached, the operation of the mobile device can be adjusted or otherwise controlled based on the accessory profile, and when the attachment state of a mobile device accessory is identified as unattached, the operation of the mobile device is not adjusted. Thus, the operation of a particular mobile device is dynamically controlled based on the accessory profile and the attachment state of the particular mobile device accessory.

[0019] On the other hand, the system and method monitor the mobile device attachment and dynamically adjust the operation of the mobile device based on the state of the mobile device attachment. In some examples, the mobile device attachment may be attached to a mobile device configured to move from a first position toward a second position along a moving path. In conjunction with the movement, the mobile device attachment may experience an event that affects the operation of the mobile device attachment, affects the operation of the mobile device, and / or an irregular event relative to the expectation. The event is identified based on a comparison of the first attachment state with the second attachment state, and the response to the event is determined accordingly. In general, the currently disclosed technology observes the behavior associated with the mobile device attachment and determines any changes in the behavior of the attachment. The observation of the change of the attachment state of the mobile device attachment combined with the analysis of the change can be used to identify the event and determine one or more responses. In some cases, monitoring and response can be performed entirely by the mobile device. In general, the currently disclosed technology promptly identifies and responds to events that affect the mobile device, the mobile device attachment and / or other objects (e.g., other mobile devices) along the moving path.

[0020] To begin a detailed description of an example environment 100 for mobile device accessory management, refer to Figure 1In one implementation, the mobile device 102 is configured to move along a path of travel 104 (e.g., a route, a movement trajectory, etc.) from a first location (e.g., a starting point) toward a second location (e.g., a destination). In one example, the mobile device 102 may be operable to move along the path of travel 104 with limited input from a person, such as an occupant within the interior of the mobile device 102. In other words, the individual may simply input a destination or other instruction, and the mobile device 102 transports the occupant to the destination along the route through a series of decisions made and employed by the mobile device 102, rather than the individual operating in engagement with the mobile device 102 to control its actions. Using the positioning data, the current geographic location of the mobile device 102 within the geographic area and / or relative to the destination or other location may be determined. Using the positioning data, a route from the current geographic location to the destination may be generated, locations along the route may be determined, and so on. Additionally, depending on their nature and movement, one or more objects present in the scene along the path of travel 104 may or may not affect the actions being performed by the mobile device 102 as it moves through the scene. In one specific implementation, the mobile device 102 periodically captures sensor data of the scene to generate perception data that provides perception of the scene, which may include, but is not limited to, object recognition of one or more objects present in the scene. Object recognition may include detection, identification, classification, positioning, etc. of one or more objects present in the scene. Using the positioning data and the perception data, the mobile device 102 moves through the scene along the travel path 104 according to its perception and its motion and route planning.

[0021] One or more mobile device accessories 106 can be used in conjunction with the mobile device 104. In some examples, the mobile device accessories 106 can be attached to the mobile device 104 so that the mobile device accessories 106 are transported along the travel path 104 along with the mobile device 102. The mobile device accessories 106 can be attached to the mobile device 102 in various ways, such as using a connection system, including but not limited to hooks, racks, mounts, straps, cables, clamps, chains, etc. The mobile device accessories 106 can be releasably attached or secured to the mobile device 102 using the connection system. Once attached, the mobile device accessories 106 can be positioned: on the top, front, back, side, bottom, base, and / or surface of the mobile device 104; on the mobile device 104, adjacent to the mobile device 104, and / or at a distance from the mobile device 104; and / or otherwise relative to the mobile device 104. In this manner, the mobile device accessories 106 can be towed, pushed, pulled, carried, or otherwise transported by the mobile device 102. The mobile device 102 may be a vehicle, a robot, etc., and the mobile device attachment 106 may include, but is not limited to, a trailer, a frame, a vehicle, a carrier, a platform, a mount, etc. The mobile device attachment 106 may be further configured to connect, mount, hold, and / or otherwise transport a load including an attached object. Thus, the mobile device attachment 106 may have one or more attachment states, such as loaded, unloaded, partially loaded, etc., and one or more attachment states, such as attached, unattached, partially attached, improperly attached, etc.

[0022] The mobile device accessory 106 can change one or more characteristics of the mobile device 102, including, but not limited to, size (e.g., width, height, length, and / or other dimensions), weight (e.g., total weight, weight distribution, center of gravity, etc.), clearance (e.g., vertical, horizontal, portrait, etc.), sensor field of view, visibility, number of axes, etc. Such changes to the characteristics of the mobile device 102 can affect the operation of the mobile device 102, including, but not limited to, aerodynamics, movement dynamics (e.g., parking, backing up, path of movement toward a target, acceleration, deceleration, etc.), traction control, steering (e.g., steering speed, turning radius, etc.), stopping distance, braking characteristics, gear shifting, blind spot management, sensor alert activation (e.g., deactivating proximity alerts, back-up sensors, etc.), external vision, navigation, clearance management (e.g., clearance-based route planning, clearance-based lane changes, etc.), etc. The characteristics of the mobile device 102 and the associated effects on the operation of the mobile device 102 can vary depending on the type of mobile device accessory 106, characteristics of the type of mobile device accessory 106, accessory state of the mobile device accessory 106, attachment state of the mobile device accessory 106, etc. In other words, each of the mobile device accessories 106 can be different and affect the characteristics and operation of the mobile device 102 in various ways, which can further vary depending on the specific characteristics of the mobile device 102 compared to other mobile devices. Therefore, the accessory management system 108 is configured to identify a specific mobile device accessory (the mobile device accessories 106) and control the operation of the specific mobile device (the mobile device 102) accordingly.

[0023] The accessory management system 108 can be associated with the mobile device 102. For example, the accessory management system 108 can form a part of the mobile device 102, a part of a user device associated with a user of the mobile device 102 and in communication with the mobile device 102, a computing device that is removably deployed and in communication with the mobile device 102, etc. In one specific implementation, identifying the mobile device accessory 106 includes identifying the presence of the mobile device accessory 106 and obtaining an accessory profile 110 associated with the mobile device accessory 106. The presence of the mobile device accessory 106 can be identified based on detection of an accessory identifier, detection of an object near the mobile device 102, user input, establishment of a connection (e.g., wired and / or wireless connection) between the mobile device accessory 106 and the mobile device 102 (e.g., by pairing), detection of attachment of the mobile device accessory 106 to the mobile device 102, and / or in other ways. The accessory identifier can be a visual identifier, a transmitted identifier, and / or other identifier. The accessory identifier can be used by the accessory management system 108 to obtain the accessory profile 110.

[0024] For example, the visual identifier can be a QR code, a barcode, a pattern, a trademark (e.g., a manufacturer name, a manufacturer logo, a model name / number, etc.), a graphic, a text, a number, and / or other unique visual elements. The visual identifier can be scanned, read, and / or captured using an imaging device, a user device, or other computing device of the mobile device 102, thereby causing the attachment profile 110 to be obtained. For example, an attachment registry can store multiple attachment profiles corresponding to a specific mobile device attachment. The attachment registry can be stored in a local memory of the mobile device 102, a user device, or other computing device, or in a database that can be accessed via a network. Using the visual identifier, the attachment profile 110 can be obtained from the attachment registry. In another example, the visual identifier launches a web page or application containing the attachment profile 110. The transmitted identifier can be, but is not limited to, a radio frequency identification (RFID), a near field communication (NFC), a chip, identification information conveyed via a wired or wireless connection (e.g., wireless radio transmission), etc. The transmitted identifier can similarly provide or cause the attachment profile 110 to be obtained. Other identifiers may include, for example, user input that provides and / or causes the attachment profile 110 to be obtained.

[0025] In one specific implementation, the attachment profile 110 includes one or more specifications of the mobile device attachment 106. These specifications may include size, shape, weight, attachment system, operating parameters, number of axes, hook-to-axle dimensions, and / or other parameters that may define changes to the characteristics of the mobile device 102 in a manner that may affect the operation of the mobile device 102. These specifications may be provided by the manufacturer of the mobile device attachment 106, user input, attachment data, and / or other information obtained via other sources. For example, an operating manual provided by the manufacturer may detail the one or more specifications. In another example, these specifications are defined by user input when generating a customized attachment profile. An attachment identifier may be generated and associated with a specification provided by a user. A web page, application, etc. may generate, for example, a QR code, and provide an interface for capturing corresponding specifications to generate a customized attachment identifier and a customized attachment profile. The QR code may be positioned on the mobile device attachment 106 so that it may be scanned by a sensor of the mobile device 102, a user device associated with a user, etc.

[0026] The accessory profile 110 can be obtained based on accessory data captured using one or more sensors, such as a lidar. The accessory data can be used to generate the accessory profile 110 by estimating the type and specifications of the mobile device accessory 106. For example, the accessory data can be compared to multiple object models to identify a match for the mobile device accessory 106. Based on the match, the accessory profile 110 is provided. In the event that there is no match, the user can be prompted to provide the specifications of the mobile device accessory 106. The user can similarly be prompted to confirm or adjust the estimated type and specifications of the mobile device accessory 106. In another example, the accessory management system 108 can use the accessory data to detect a visual identifier, such as a manufacturer logo or model number, and retrieve the accessory profile 110.

[0027] In one specific implementation, the accessory management system 108 determines the attachment state of the mobile device accessory 106 relative to the mobile device 102 at one or more times. The attachment state can be determined in the following situations: at a starting location before the mobile device 102 moves according to its own plans and decisions; when the mobile device 102 moves from the starting location to the destination location according to its own plans and decisions; after reaching the destination location; when stopped; while moving; and so on. Therefore, the accessory management system 108 can determine whether the mobile device accessory 106 is attached, unattached, or partially attached, and whether the attachment state of the mobile device accessory 106 changes during the movement (for example, the mobile device accessory 106 becomes inadvertently detached). The attachment state can be detected using one or more sensors associated with the mobile device 102, the mobile device accessory 106, and / or other devices.

[0028] Based on the attachment state of the mobile device accessory 106, the operation of the mobile device 102 can be controlled. For example, when the mobile device accessory 106 is in the attached state, the operation of the mobile device 102 can be adjusted based on the accessory profile 110. When the mobile device accessory 106 is in the unattached state, the operation of the mobile device 102 is not adjusted based on the accessory profile 110, so that the mobile device 102 operates normally based on the characteristics of the mobile device 102. When the mobile device 106 is in the partially attached state, the operation of the mobile device 102 can be adjusted to transition the mobile device accessory 106 to the attached or unattached state, stop the movement of the mobile device 102, generate an alert, etc. In this way, the accessory management system 108 can identify and respond to accessory state changes.

[0029] In addition, the accessory management system 108 can determine the accessory state of the mobile device accessory 106, such as loaded, unloaded and / or partially loaded, and control the operation of the mobile device 102 accordingly. Using one or more sensors, user input, etc., the accessory state and accessory state parameters can be determined. The accessory state parameters may include, but are not limited to, the size of the load, the shape of the load, the total weight of the load, the weight distribution of the load, the attachment security of the load (e.g., whether the load is tied or loose), the configuration state of the mobile device accessory 106 (e.g., open door, flat tire, disconnected light, etc.), etc. The accessory state and accessory state parameters can be derived in various ways. For example, based on the specifications of the mobile device accessory 106 obtained from the accessory profile 110, the mobile device accessory 106 has a known weight. Therefore, when the mobile device 102 initiates movement, the additional weight associated with the load and the weight distribution (e.g., more or less tongue weight) can be detected, thereby estimating the accessory state and accessory state parameters. Similarly, known suspension values ​​can be used to determine whether the bicycle rack is loaded and how many bicycles are loaded. Using known values ​​of the mobile device 102 and the mobile device accessory 106, the accessory state and accessory state parameters may be determined and the operation of the mobile device 102 controlled accordingly. Additionally, the known configuration of the mobile device accessory 106 may be considered in the operation of the mobile device 102. For example, the mobile device accessory 106 may include a swinging door and the mobile device 102 provides a clearance distance for opening the swinging door during parking.

[0030] Based on the attachment status and the accessory status, the operation of the mobile device 102 can be controlled. In one specific implementation, the operation of the mobile device 102 is controlled based on the accessory profile 110, the accessory status parameters, etc. For example, the operation can include, but is not limited to, parking, reversing, navigating, moving, accelerating, decelerating, traction control, steering, stopping distance, braking characteristics, shifting, blind spot management, sensor alert activation, vision, clearance management, etc. A visual confirmation can be provided to the user device or presented on a display for the user to verify the accessory profile 110, the attachment status, and the accessory status.

[0031] Additionally, controlling the operation of the mobile device 102 may also include controlling the accessory operation of the mobile device accessory 106. For example, the accessory management system 108 may detect automated features of the mobile device accessory 106 (e.g., automated trailer hitch, automated doors, brakes, lights, automated sensors, automated actuators, etc.) and control these automated features based on the accessory profile 110, accessory state parameters, etc. In one specific implementation, the control operation is to automatically move the automated trailer hitch and the mobile device 102 and / or the mobile device accessory 106 to automatically attach and detach the mobile device accessory 106 to and from the mobile device 102 using the automated trailer hitch. The mobile device 102 and the mobile device accessory 106 may be configured for trusted pairing or authenticated communication, thereby allowing control and sharing of data when the mobile device accessory 106 is in an attached state.

[0032] In some examples of changes in the weight of the mobile device 102 as modified by the mobile device accessory 106, acceleration, stopping distance, traction control, steering, braking, gear shifting, etc. may be adjusted. In other examples of changes in the size and / or clearance of the mobile device 102 as modified by the mobile device accessory 106, parking, backing up, blind spot management, clearance management, etc. may be adjusted. The mobile device 102 may generate a route or movement path based on clearance along the route, make lane changes based on increased length, adjust turning radius, adjust movement based on increased drag or other aerodynamic considerations, adjust movement based on the configuration of the mobile device accessory 106, and / or other operations based on changes in size and / or clearance. For example, when the mobile device 102 (e.g., using a hook) is towing the mobile device accessory 106, the backing operation changes. In order to reach a target location (such as a parking spot), when backing up with the mobile device accessory 106 in an attached state, the mobile device 102 moves along a series of movements, directions, and orientations that are different relative to when the mobile device accessory 106 is in an unattached state. Thus, the parameters of the parking spot (e.g., size, clearance, orientation, etc.) are identified, and the mobile device 102 backs the mobile device accessory 106 into the parking spot according to the accessory profile 110, the accessory state parameters, and / or the parameters of the parking spot, such that the parking spot can be identified and the mobile device accessory 106 backs into the parking spot autonomously. In some examples, the mobile device 102 and / or the mobile device accessory 106 can be positioned within the parking spot relative to the charging station.

[0033] Similarly, based on size and positioning, the mobile device accessories 106 and / or payload may block the field of view or other visibility of one or more sensors of the mobile device 102, which may trigger false proximity alerts, false back-up alerts (e.g., during a back-up maneuver), or result in incomplete sensory data. Accordingly, proximity alerts may be disabled, external vision may be generated or otherwise provided, and the like.

[0034] In one embodiment where visibility is blocked by the mobile device accessory 106 and / or the load, an external vision of an unobstructed view is provided. For example, images or videos may be captured from a sensor of the mobile device accessory 106 and transmitted to the mobile device 102 for presentation (e.g., on a windshield, a window surface, a rearview mirror, an internal display, a user device, a head-up display, etc.). In another example, a sensor of the mobile device 102 may capture multiple images of a scene around the mobile device 102. A composite image may be generated from multiple images in which the mobile device accessory 106 is removed from the field of view based on the specifications (e.g., size) of the accessory profile 110. The composite image may be generated by stitching, using visual object removal, image replacement, and / or other image processing techniques to provide unobstructed visibility. The composite image may be presented, for example, using a windshield, a window surface, a rearview mirror, an internal display, a user device, a head-up display, etc.

[0035] In some implementations where the mobile device 102 is deployed in a fleet of mobile devices, the accessory management system 108 can be used to determine the accessory state and attachment state of the mobile device accessories 106 to customize the user experience according to the user's needs. For example, a user can request to be collected from a mobile device that includes a bicycle rack. One or more mobile devices with bicycle racks can be identified, and the mobile device 102 can be dispatched to the user's location. The accessory management system 108 can determine when a bicycle is loaded onto the rack, whether the bicycle is secured in the rack, and the accessory parameters of the bicycle (e.g., size, shape, weight, whether it is one of multiple bicycles, etc.) and adjust the operation of the mobile device 102 accordingly.

[0036] It should be appreciated that the operation of mobile device 102 may be controlled based on numerous other mobile device accessories and scenarios. In general, the presently disclosed technology provides mobile device accessory management such that the operation of a particular mobile device is dynamically controlled based on its accessory profile and attachment state.

[0037] Steering Figure 2, an example environment 200 for mobile device accessory management is shown. In one specific implementation, one or more mobile device accessories (e.g., mobile device accessory 204) are used in conjunction with mobile device 202. In some examples, mobile device 202 can be similar to mobile device 102, and mobile device accessory 204 can be similar to mobile device accessory 106. Mobile device accessory 204 can be attached to mobile device 202, move with mobile device 202, and / or otherwise associated with mobile device 202. In some examples, mobile device 202 is directly or indirectly attached to mobile device accessory 204 using attachment system 208. For example, mobile device accessory 204 can be bolted, welded, tethered, joined (e.g., using a ball joint), mounted, releasably connected, etc. to mobile device 202. Attachment system 208 can be a magnetic system using one or more magnets. For example, mobile device accessory 204 and / or mobile device 202 can include a magnet that releasably attaches mobile device accessory 204 to mobile device 202 using a magnetic field.

[0038] In one specific implementation, the mobile device 202 is configured to move from a first location (e.g., a starting point) toward a second location (e.g., a destination) along a movement path 206 (e.g., a route, a movement trajectory, a travel path, etc.). In one example, the mobile device 202 may be operable to move along the movement path 206 through a series of route and motion planning decisions made and taken by the mobile device 202, as described herein.

[0039] The monitoring system 212 may communicate with the sensor system via wired and / or wireless communications for monitoring the mobile device accessory 204 in conjunction with the movement along the movement path 206. The sensor system may include one or more sub-sensor systems (e.g., sensor system 210, sensor system 214, etc.). The monitoring system 212 and / or the sensor system may be part of the mobile device 202, the mobile device accessory 204, other devices, and / or a combination thereof. The sensor system 210 may include one or more sensors configured to capture accessory data associated with the mobile device accessory 204. For example, the sensor system 210 may include a two-dimensional (2D) sensor, such as a camera, for receiving a visual image associated with the mobile device accessory 204. The sensor system 210 may include one or more 3D sensors, such as light detection and ranging (lidar), sound navigation and ranging (sonar), radio detection and ranging (radar), or any combination thereof, for receiving any spatial context associated with the mobile device accessory 204. For example, the spatial context associated with the mobile device accessory 204 may include the distance of the mobile device accessory 204 to the mobile device 202, which may be determined using radar. The sensor system 210 may also include a microphone for capturing audible context associated with the mobile device accessory 204; a thermal sensor configured to detect the temperature of the mobile device accessory, etc. The accessory data may be captured and processed in real time, near real time, or in some cases may be delayed. Although various example sensors are described to facilitate understanding of the currently disclosed technology, it should be understood that any suitable one or more sensors of the same or different types may be used to capture accessory data associated with the mobile device accessory 204 and / or the movement of the mobile device 202 and the mobile device accessory 204 along the movement path 206.

[0040] In some implementations, the monitoring device 212 may be communicatively coupled to a sensor system 214 disposed on or otherwise associated with the mobile device accessory 204. For example, the sensor system 214 may include one or more sensors configured to measure operating values ​​of the mobile device accessory 204, such as pressure (e.g., tire pressure), temperature, system values ​​(e.g., standard operating range, etc.). The sensor system 210 and / or the sensor system 214 may include an accelerometer for detecting vibrations of the mobile device accessory 204, a gyroscope for detecting orientation and / or leveling of the mobile device accessory 204. Using the accessory data, the monitoring system 212 identifies an event that affects the mobile device operation of the mobile device 202, the accessory operation of the mobile device accessory 204, and / or one or more objects along the mobile path 206. A response to the event is determined. In some examples, the monitoring system 212 is associated with the mobile device 202 so that the mobile device 202 both captures the accessory data for identifying the event and executes a response to the event. The accessory data can correspond to mobile device accessory 204 and / or mobile device 202 (such that a change in the state of mobile device accessory 204 can be inferred based on a change in the behavior of mobile device 202). In these examples, additional sensors and / or monitoring devices (such as sensor system 214) can be eliminated.

[0041] An event may be identified based on a change in the accessory state of the mobile device accessory 204 associated with movement along the movement path 206. In one specific implementation, the monitoring system 212 may identify an event by detecting a change in the behavior of the mobile device accessory 204 relative to an expected behavior. The change in behavior may be determined based on the accessory data, and in some cases, also based on additional information about the mobile device accessory 204. As a non-limiting example, the monitoring system 212 may identify an event by determining whether a change in tilt associated with the mobile device accessory 204 has increased beyond a baseline (e.g., expected) level of tilt of the mobile device accessory 204. The monitoring system 212 may take into account historical observations, such as movement, vibration, and speed of behavior change of the mobile device accessory 204. The monitoring system 212 may compare the accessory data to a threshold value to identify whether a change in behavior has occurred that warrants a response. For example, if the vibration of the accessory increases beyond a threshold value, the monitoring system 212 may determine and trigger a specific response. In some cases, multiple thresholds may be used in conjunction with a graded response. For example, if the vibration increases beyond a first threshold, a first response (e.g., a notification to the user) may be triggered, and if the vibration increases beyond a second threshold that is greater than the first threshold, a second response (e.g., a robotic action to stop movement of the mobile device 202) may be triggered.

[0042] Additionally or alternatively, predefined characteristics such as the level, orientation, size, range of motion, etc. associated with the mobile device accessory 204 may be considered. As an example, if the level of the mobile device accessory 204 changes (e.g., the mobile device accessory 204 tilts) by more than a threshold amount, a specific response may be triggered. Similarly, changes in conditions such as color changes, temperature changes, the presence of external objects or conditions (e.g., debris, etc.), shape changes, weight distribution changes, composition (e.g., gas, etc.) changes, etc. may be detected. Thus, the accessory data may generally be used to determine the behavior of the mobile device 202 and / or the mobile device accessory 204 in relation to movement along the movement path 204 (which may include movement, appearance, one or more values, attachment status, etc.), and compare the behavior to the expected behavior of the mobile device 202 and / or the mobile device accessory 204 during movement.

[0043] Generally, an event may be identified by determining a change between a first accessory state of the mobile device accessory 204 and a second accessory state of the mobile device accessory 204. A change in accessory state may be determined by observing the behavior of the mobile device accessory 204 during movement along the movement path 206 relative to the expected behavior of the mobile device 204 during movement. In some examples, a change in accessory state may be inferred by observing the behavior of the mobile device 202 during movement along the movement path 206 relative to the expected behavior of the mobile device 202 when attached to the mobile device accessory 204 during movement. In determining a change in accessory state, the monitoring device 212 may analyze the accessory data in various ways, such as using one or more thresholds, ranges, profiles, values, behavioral models, machine learning, artificial intelligence, and the like. For example, an event of a tire deflation may be detected based on a change in level measured using an on-device sensor, based on visual tilt captured using a camera, and the like.

[0044] In some cases, monitoring system 212 may be configured to indicate a priority level for a particular event. The priority level may be a plurality of priority levels corresponding to a hierarchical response of multiple responses that are upgraded or downgraded from a previous response. For example, an event with a lower priority may correspond to a maintenance type event, and an event with a higher priority may correspond to a mobile type event. Generally speaking, a mobile type event may correspond to an event in which movement along a mobile path is affected. A maintenance type event may correspond to an event within a predetermined level of change between accessory states. In some cases, multiple occurrences of the same type of event may upgrade the response and / or otherwise assign a higher priority.

[0045] refer to Figure 3 , turn Figure 3, an example mobile device 300 is shown, which may be the mobile device 102, the mobile device 202, or another mobile device. In one specific implementation, the mobile device 300 is associated with a sensor system 302, a monitoring system 304, and an equipment system 306. The sensor system 302 and / or the monitoring system 304 may be part of the mobile device 300, the sensor system 302, and / or the equipment system 306 or may be separate from the mobile device 300, the sensor system 302, and / or the equipment system 306 but communicate with them. It should be understood that any of the perception system 316, the planning system 318, the control system 320, the subsystem 322, and / or the management system 328 may be part of the equipment system 306 or separate from the equipment system. In some cases, the management system 328 may be the attachment management system 108. In other cases, the management system 328 may communicate with the attachment management system 108. Similarly, the operation control system 324, the marking system 326 may be part of the monitoring system 304 or separate from the monitoring system. Systems 302 to 328 may generally be separate components, integrated components, or a combination thereof.

[0046] The sensor system 302 has one or more sensors configured to capture sensor data of the field of view of the mobile device 300, such as one or more images, positioning data corresponding to the position, heading and / or orientation of the mobile device 200, movement data corresponding to the movement of the mobile device 200, etc. The sensor system 302 may also capture accessory data corresponding to the movement of the mobile device accessory 204 along the movement path 206. For example, the one or more sensors may include a contextual sensor 308, such as one or more three-dimensional (3D) sensors configured to capture 3D images, radar sensors, sonar sensors, infrared (IR) sensors, optical sensors, visual detection and ranging (VIDAR) sensors, etc. The one or more 3D sensors may include one or more lidar sensors (e.g., scanning lidar sensors) or other depth sensors.

[0047] The sensor system 302 may also include one or more visual sensors 310, such as cameras (e.g., RGB cameras). These cameras may capture color images, grayscale images, and / or other 3D images. One or more audio sensors 312 (such as microphones) may capture audio data. Other sensors 314 may be implemented to be suitable for capturing accessory data and / or other information about the behavior of the mobile device accessory 104, such as temperature, pressure, composition, and / or other values. Other sensors 314 may further include, but are not limited to, global navigation satellite systems (GNSS), inertial navigation systems (INS), inertial measurement units (IMUs), global positioning systems (GPS), attitude and heading reference systems (AHRS), compasses, and / or other positioning systems.

[0048] In some examples, the perception system 316 generates perception data that can use sensor data to detect, identify, classify, and / or determine the location of one or more objects. The perception data may include attachment data for obtaining an attachment profile 110, an attachment state, an attachment state, and the like. The perception data may also be used by the planning system 318 to generate one or more actions of the mobile device 300, such as generating a motion plan with at least one movement action for autonomously moving the mobile device 300 through a scene based on the presence of an object and in accordance with the attachment profile 110, the attachment state, and / or the attachment state. The control system 318 may be used to control various operations of the mobile device 300 when executing the motion plan. The motion plan may include various operational instructions for the subsystem 322 of the mobile device 300 to autonomously execute to perform movement actions and other actions.

[0049] In some examples, the sensing system 316 generates sensing data that can be used to determine the attachment state of the mobile device accessory 204. The sensing data may include the attachment data or be otherwise generated based on the attachment data. The sensing data can be used by the monitoring system 304 to identify events and determine one or more responses to the events. The monitoring system 304 can use the operating control system 324, the marking system 326, etc. to trigger a response. For example, the operating control system can trigger one or more actions performed by the mobile device 300 and / or the mobile device accessory 104. The marking system 326 can mark the event. The monitoring system 304 can also trigger a response by communicating with a remote device, with a user device, etc. via a network.

[0050] The planning system 318 can generate instructions corresponding to one or more actions of the mobile device 300 for performing one or more responses to the event. For example, the instructions may include a motion plan having at least one movement action for autonomously moving the mobile device 300 to perform the response. The control system 318 can be used to control various operations of the mobile device 300 when executing the motion plan. The motion plan may include various operational instructions for execution by the subsystems 322 of the mobile device 300 to perform the response.

[0051] In a non-limiting example, the mobile device 300 may tow a mobile device accessory 204 in the form of a trailer having a tire that experiences a pressure loss on a first side. Due to the pressure loss, the mobile device accessory 104 may tilt toward the first side at a certain percentage of inclination. The visual sensor 310 may detect the percentage inclination, and the monitoring system 304 may compare the percentage inclination with a threshold inclination. If the percentage inclination exceeds the threshold inclination, an event associated with a flat tire may be detected, and a response (e.g., slowing down or stopping movement, contacting a remote device, notifying one or more occupants, etc.) may be determined accordingly. Other sensors may be used similarly to detect such events. For example, an event may be inferred based on additional rolling resistance, which is based on speed load. As another example, if the loss of pressure is immediate, the audio sensor 312 may capture sounds that match a model of such an event.

[0052] Steering Figure 4 , an example operation 400 for mobile device accessory management is shown. In one specific implementation, operation 402 identifies a mobile device accessory. The mobile device accessory is associated with a mobile device that is configured to move from a first position toward a second position according to its own planning and decision-making. Operation 402 may include identifying the presence of a mobile device accessory and obtaining an accessory profile. In one specific implementation, the accessory profile is obtained using a visual identifier, a transmitted identifier, etc. The visual identifier may include, for example, a QR code. The accessory profile may be obtained in response to scanning the visual identifier with a camera, which may be associated with a user device, a mobile device, and / or a computing device. The accessory profile may be generated using accessory data corresponding to the mobile device accessory, wherein the accessory data is captured using one or more sensors.

[0053] Operation 404 determines the attachment state of the mobile device accessory relative to the mobile device. The attachment state can be detected using accessory data captured using one or more sensors. In one specific implementation, the attachment state is determined at one or more times. The one or more times may include, but are not limited to, a first time before the mobile device moves from a first position to a second position, a second time when the mobile device is moving from a first position to a second position, etc. The attachment state and / or attachment profile can be communicated to a user device or other computing device (e.g., a display in or associated with a mobile device and / or a mobile device accessory, etc.).

[0054] Operation 406 controls the operation of the mobile device according to the attachment state of the mobile device accessory. In one specific implementation, the operation of the mobile device is adjusted based on the accessory profile corresponding to the mobile device accessory. For example, when the attachment state is identified as attached, operation 406 can adjust the operation of the mobile device based on the accessory profile, and when the attachment state is identified as unattached, operation 406 can abandon the adjustment of the operation of the mobile device. The operation of the mobile device may include steering, sensor alarm activation, backing up, external vision, acceleration, deceleration, navigation, etc. In addition, operation 406 may include controlling the accessory operation of the mobile device accessory.

[0055] In one example, the operation includes a turning operation, wherein the turning operation is performed according to a turning radius determined based on an accessory profile. The turning operation may include, but is not limited to, a three-point turn, a U-turn, or other turns. In another example, the operation of the mobile device includes a deceleration operation. The deceleration operation may be performed according to a deceleration rate, a stopping distance, etc. determined based on an accessory profile. In another example, the operation of the mobile device includes a clearance operation. The clearance operation may include generating a route based on an accessory profile. The route has a vertical clearance exceeding the vertical height of the mobile device accessory and any load as determined based on the accessory status.

[0056] Steering Figure 5 , example operations 500 for mobile device accessory management are shown. In one specific implementation, operation 502 identifies a type of mobile device accessory. The type of mobile device accessory can be identified using accessory data, user input, etc. Operation 504 obtains an accessory profile including one or more specifications for the type of mobile device accessory. Operation 506 determines an attachment state of the mobile device accessory (e.g., based on the accessory profile), and operation 508 determines an attachment state of the mobile device accessory relative to the mobile device. Operation 510 determines an operational adjustment to the mobile device based on the accessory state, the attachment state, and the accessory profile.

[0057] Figure 6 Example operations 600 for mobile device accessory management are shown. In one specific implementation, operation 602 obtains a first accessory state of a mobile device accessory. The first accessory state may correspond to an expected behavior of the mobile device accessory during motion. For example, the expected behavior may include expected movement, expected appearance, one or more expected values, expected attachment state, etc. The expected movement may include, but is not limited to, range of motion, flow of motion, vibration level, speed of change, level of external motion (e.g., caused by debris), etc. The expected appearance includes, but is not limited to, leveling (e.g., relative level of points along a plane), orientation, size, shape, texture, color, etc. The expected values ​​may include, but are not limited to, temperature, pressure, composition, subsystem operation values, etc. of the mobile device or the mobile device accessory.

[0058] Operation 604 obtains attachment data corresponding to a mobile device attachment. The attachment data is captured in conjunction with movement along a movement path from a first position toward a second position. For example, attachment data may be captured at a first position, along a movement path, at a second position, before movement, during movement, after movement, and the like. The mobile device attachment may be attached to the mobile device, move along the movement path with the mobile device, and / or otherwise associated with movement of the mobile device. One or more sensors may be used to capture attachment data. The sensor may form part of or otherwise be associated with the mobile device, the mobile device attachment, and / or another computing device (e.g., a removable computing device deployed to monitor mobile device attachments). The sensor may include, but is not limited to, depth, lidar, camera, sonar, radar, microphone, infrared, thermal, and the like.

[0059] Operation 606 determines a second accessory state of the mobile device accessory based on the accessory data. The second accessory state may correspond to a behavior of the mobile device accessory related to the movement. The behavior of the mobile device accessory related to the movement may include, but is not limited to, movement, appearance, one or more values, attachment state, etc. Operation 608 identifies an event that affects at least one of a mobile device operation of the mobile device or an accessory operation of the mobile device accessory. In one specific implementation, operation 608 compares an expected behavior of the mobile device accessory with a behavior of the mobile device accessory.

[0060] Operation 610 determines a response to the event. The response may be performed by the mobile device, the mobile device accessory, the remote device, the user device, etc. In some examples, the response includes, but is not limited to: controlling the mobile device operation; controlling the mobile device accessory operation; marking the event; prompting manual control of the mobile device; sending a communication to the remote device; initiating remote control of the mobile device and / or the mobile device accessory; deploying a second mobile device to the location of the mobile device (e.g., the current location or the predicted future location), scheduling maintenance, etc. The deployment of the second mobile device may involve deploying one or more resources for addressing or resolving the event.

[0061] In one specific implementation, an event type of the event is determined, and a response is determined based on the event type. The event type may be a movement type event, a maintenance type event, and the like. Generally speaking, a movement type event may correspond to an event in which movement along a movement path is affected. A maintenance type event may correspond to an event within a predetermined level of change between a first accessory state and a second accessory state. The predetermined level of change may be visual-based, auditory-based, value-based (e.g., pressure value, temperature value, composition value, etc.), and the like. In some examples, movement along the movement path is allowed, or movement along the movement path may continue, in view of the maintenance type event.

[0062] When the event type is a movement type event, the response may include controlling the mobile device operation and / or the accessory operation. For example, controlling the mobile device operation may include, but is not limited to: adjusting the movement path (e.g., exiting the movement path, rerouting the movement path, etc.); slowing down the movement; stopping the movement; adjusting the parameters of the movement (e.g., speed, steering, etc.); adjusting the subsystems (e.g., lights, brakes, gear shifting, external communications, planning, etc.); etc. Similarly, controlling the accessory operation may include, but is not limited to: adjusting the parameters of the movement of the mobile device accessory; adjusting the movement path of the accessory relative to the mobile device; adjusting the attachment state of the mobile device accessory to the mobile device; adjusting the subsystem; stopping one or more operations of the mobile device accessory; etc.

[0063] When the event type is a maintenance type event, the response may include marking the event. For example, marking the event may include generating an alert, recording information corresponding to the event in a log (e.g., a diagnostic log), etc. The alert may be sent to a mobile device, a user device, and / or a remote device. The alert may be presented using a presentation system. The presentation system may visually display the alert, audibly play an alarm, and / or use tactile feedback. The alert may prompt an action, such as scheduling maintenance, deploying resources, generating recommendations for resolving the event, etc.

[0064] In one specific implementation, the response is a hierarchical response of multiple responses. Multiple attachment states can be determined in conjunction with movement along a movement path. Based on any change between states, a subsequent response can upgrade or downgrade a previous response. For example, a second response that upgrades the response can be determined based on a change from a second attachment state to a third attachment state. Therefore, for each event and / or state change, a priority level can be assigned and the response can be customized accordingly.

[0065] Figure 7 An example computing system 700 is shown having one or more computing units that can implement the various systems and methods discussed herein. The computing system 700 can be applied to the mobile device 102, the mobile device accessory 106, the accessory management system 108, the mobile device 202, the mobile device accessory 204, the monitoring system 304, the device system 306, the management system 328, and other computing or network devices. It should be understood that the specific implementation of these devices can have possible different specific computing architectures, not all of which are specifically discussed herein, but will be understood by those of ordinary skill in the art.

[0066] The computing system 700 may be a computing system capable of executing a computer program product to perform a computer process. Data and program files may be input into the computing system 700, which reads the files and executes the programs therein. Figure 7Some of the elements of computing system 700 are shown in FIG. 7 , including one or more hardware processors 702, one or more data storage devices 704, one or more memory devices 706, and / or one or more ports 708, 710, 712. In addition, other elements that those skilled in the art will recognize may be included in computing system 700 but are not shown in FIG. Figure 7 The various elements of computing system 700 may be connected via one or more communication buses, point-to-point communication paths, or Figure 7 communicate with each other by other means of communication not explicitly described.

[0067] Processor 702 may include, for example, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), and / or one or more internal levels of cache. There may be one or more processors 702, such that processor 702 includes a single central processing unit or multiple processing units capable of executing instructions and performing operations in parallel with each other (commonly referred to as a parallel processing environment).

[0068] Computer system 700 may be a conventional computer, a distributed computer, or any other type of computer, such as one or more external computers available via a cloud computing architecture. The techniques described herein are optionally implemented in software stored on one or more data storage devices 704, stored on one or more memory devices 706 (e.g., one or more tangible, non-transitory computer-readable storage media), and / or communicated via one or more of ports 708, 710, 712, thereby communicating Figure 7 The computing system 700 in the embodiment of the present invention is converted into a special-purpose machine for implementing the operations described herein. Examples of the computing system 700 include personal computers, servers, special-purpose autonomous processors, terminals, workstations, mobile phones, tablet computers, laptop computers, etc.

[0069] The one or more data storage devices 704 may include any non-volatile data storage device capable of storing data generated or employed within the computing system 700, such as computer executable instructions for executing computer processes, which may include instructions for both application programs and operating systems (OS) that manage various components of the computing system 700. The data storage device 704 may include, but is not limited to, a disk drive, an optical drive, a solid-state drive (SSD), a flash drive, and the like. The data storage device 704 may include removable data storage media, non-removable data storage media, and / or external storage devices available via a wired or wireless network architecture using such a computer program product, including one or more database management products, network server products, application server products, and / or other additional software components. Examples of removable data storage media include compact disk read-only memory (CD-ROM), digital versatile disk read-only memory (DVD-ROM), magneto-optical disk, flash drive, and the like. Examples of non-removable data storage media include internal magnetic hard disks, SSDs, and the like. The one or more memory devices 706 may include volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM), and the like) and / or non-volatile memory (e.g., read-only memory (ROM), flash memory, and the like).

[0070] A computer program product containing mechanisms for implementing systems and methods according to the techniques described herein may reside in a data storage device 704 and / or a memory device 706, which may be referred to as a machine-readable medium. It should be understood that a machine-readable medium may include any tangible, non-transitory medium capable of storing or encoding instructions to perform any one or more of the operations of the present disclosure for execution by a machine, or capable of storing or encoding data structures and / or modules used by or associated with such instructions. A machine-readable medium may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated caches and servers) storing one or more executable instructions or data structures.

[0071] In some implementations, computing system 700 includes one or more ports for communicating with other computing devices, network devices, or vehicle devices, such as input / output (I / O) port 708, communication port 710, and subsystem port 712. It should be understood that ports 708-712 may be combined or separated, and more or fewer ports may be included in computing system 700.

[0072] I / O port 708 may be connected to I / O devices or other devices through which information is input to or output from computing system 700. Such I / O devices may include, but are not limited to, one or more input devices, output devices, and / or environmental transducer devices.

[0073] In one implementation, the input device converts human-generated signals such as human voice, physical movement, physical touch or pressure into electrical signals as input data to the computing system 700 via the I / O port 708. Similarly, the output device can convert electrical signals received from the computing system 700 via the I / O port 708 into signals that can be sensed by a person as output, such as sound, light and / or touch. The input device can be a mixed digital and alphanumeric input device, including alphanumeric keys and other keys for transmitting information and / or command selections to the processor 702 via the I / O port 708. The input device can be another type of user input device, including but not limited to: direction and selection control devices, such as mice, trackballs, cursor direction keys, joysticks and / or wheels; one or more sensors, such as cameras, microphones, position sensors, orientation sensors, gravity sensors, inertial sensors and / or accelerometers; and / or touch-sensitive display screens ("touch screens"). Output devices can include but are not limited to displays, touch screens, speakers, tactile and / or haptic output devices, etc. In some implementations, for example, in the case of touch screens, the input device and the output device can be the same device.

[0074] The environmental transducer device converts one form of energy or signal into another form for input to or output from the computing system 700 via the I / O port 708. For example, an electrical signal generated within the computing system 700 can be converted into another type of signal, and / or vice versa. In one specific implementation, the environmental transducer device senses a characteristic or aspect of the environment local or remote to the computing system 700, such as light, sound, temperature, pressure, magnetic field, electric field, chemical property, physical movement, orientation, acceleration, gravity, etc. In addition, the environmental transducer device can generate a signal to exert some effect on the environment local or remote to the example computing system 700, such as physical movement of an object (e.g., a mechanical actuator), heating or cooling of a substance, adding a chemical substance, etc.

[0075] In one specific implementation, the communication port 710 is connected to a network, and the computing system 700 can receive network data through the port, which can be used to perform the methods and systems described herein and transmit information and network configuration changes determined thereby. In other words, the communication port 710 connects the computing system 700 to one or more communication interface devices, which are configured to transmit and / or receive information between the computing system 700 and other devices through one or more wired or wireless communication networks or connections. Examples of such networks or connections include, but are not limited to, Universal Serial Bus (USB), Ethernet, Wi-Fi, Near Field Communication (NFC), cellular, and the like. One or more such communication interface devices may be used via the communication port 710 to communicate with one or more other machines directly through a point-to-point communication path, through a wide area network (WAN) (e.g., the Internet), through a local area network (LAN), through a cellular (e.g., a third generation (3G), fourth generation (4G) network, or fifth generation (5G)) network, or through another communication means. In addition, the communication port 710 may communicate with an antenna for electromagnetic signal transmission and / or reception. In some examples, an antenna may be used to receive global positioning system (GPS) data to facilitate determining the location of a machine, a vehicle, or another device.

[0076] In some examples, the mobile device (e.g., 102, 202) described herein is a vehicle, and the mobile device accessory (e.g., 104, 206) is a vehicle accessory. The computing system 700 may include a subsystem port 712 for communicating with one or more systems associated with the vehicle to control the operation of the vehicle and / or exchange information between the computing system 700 and one or more subsystems of the vehicle. Examples of such subsystems of the vehicle include, but are not limited to, imaging systems, radars, lidars, motor controllers and systems, battery controls, fuel cells or other energy storage systems or controls, autonomous or semi-autonomous processors and controllers, steering systems, braking systems, lighting systems, navigation systems, environmental controls, entertainment systems, etc. for such vehicles having hybrid or electric motor systems.

[0077] Entities implementing this technology should adhere to established privacy policies and / or practices. These privacy policies and / or practices should meet or exceed industry or government requirements for maintaining the privacy and security of personal data. In addition, users should be allowed to "opt in" or "opt out" of allowing mobile devices to participate in such services. Third parties may assess these implementers to confirm their compliance with established privacy policies and practices.

[0078] Figure 7 The system shown is only one possible example of a computing system that can employ or be configured according to aspects of the present disclosure. It should be understood that other non-transitory tangible computer-readable storage media storing computer-executable instructions for implementing the disclosed technology on a computing system can be used.

[0079] In the present disclosure, the disclosed method may be implemented as an instruction set or software readable by a device. In addition, it should be understood that the specific order or hierarchical structure of the steps in the method disclosed in the present invention is an example of an example method. Based on design preferences, it should be understood that the specific order or hierarchical structure of the steps in the method can be rearranged while being retained within the subject matter disclosed in the present invention. The requirements claimed in the attached method are to present the elements of various steps in a sample order, and do not necessarily mean to be limited to the specific order or hierarchical structure presented. The present disclosure described may be provided as a computer program product or software that may include a non-transitory machine-readable medium having instructions stored thereon, which can be used to program a computing system (or other electronic device) to perform a process according to the present disclosure. Machine-readable media include any mechanism for storing information in a form (e.g., software, processing application) readable by a machine (e.g., computer).

[0080] Although the present disclosure has been described with reference to various specific implementations, it should be understood that these specific implementations are illustrative and the scope of the present disclosure is not limited to these specific implementations. Many variations, modifications, additions and improvements are possible. More generally, various aspects according to the present disclosure have been described in the context of specific specific implementations. Functions can be separated or combined together in boxes in different ways in various aspects of the present disclosure, or described in different terms. These and other variations, modifications, additions and improvements may fall within the scope of the present disclosure as defined in the following claims.

Claims

1. One or more tangible, non-transitory computer-readable storage media storing computer-executable instructions for planning movement of a mobile device, the computer-executable instructions comprising: identifying a mobile device accessory, the mobile device accessory being associated with a mobile device, the mobile device being configured to plan a path of travel and corresponding movement from a first location toward a second location; determining an attachment status of the mobile device accessory relative to the mobile device; as well as An operation of the mobile device is controlled according to the attachment state of the mobile device accessory, the operation of the mobile device being adjusted based on an accessory profile corresponding to the mobile device accessory.

2. The one or more tangible, non-transitory computer-readable storage media of claim 1, wherein the attachment state is detected using accessory data captured using one or more sensors of the mobile device.

3. The one or more tangible, non-transitory computer-readable storage media of claim 1, wherein identifying the mobile device accessory comprises identifying a presence of the mobile device accessory and obtaining the accessory profile.

4. The one or more tangible, non-transitory computer-readable storage media of claim 3, wherein the attachment profile is obtained by scanning a visual identifier using a camera.

5. The one or more tangible, non-transitory computer-readable storage media of claim 4, wherein the visual identifier comprises a Quick Response (QR) code.

6. The one or more tangible, non-transitory computer-readable storage media of claim 3, wherein the accessory profile is obtained using a transmitted identifier via a wireless radio transmission.

7. The one or more tangible, non-transitory computer-readable storage media of claim 6, wherein the transmitted identifier is transmitted via near field communication (NFC).

8. One or more tangible, non-transitory computer-readable storage media according to claim 1, wherein the accessory profile is generated using accessory data corresponding to the mobile device accessory, the attachment data is captured using one or more sensors, and the accessory profile includes at least an indication of the size of the mobile device accessory.

9. The one or more tangible, non-transitory computer-readable storage media of claim 1, wherein the operation of the mobile device comprises a turning operation performed according to a turning radius determined based on the accessory profile.

10. One or more tangible, non-transitory computer-readable storage media according to claim 1, wherein the operation of the mobile device includes a deceleration operation, and the deceleration operation is performed according to at least one of a deceleration rate or a stopping distance determined based on the accessory profile.

11. One or more tangible, non-transitory computer-readable storage media according to claim 1, wherein the operation of the mobile device includes a clearance operation, the clearance operation comprising generating a route based on the accessory profile, the route having a vertical clearance that exceeds the vertical height of the mobile device accessory.

12. A method for managing accessories of a mobile device, the method comprising: identifying a mobile device accessory, the mobile device accessory being associated with a mobile device, the mobile device being configured to plan a path of travel and corresponding movement from a first location toward a second location; determining an attachment status of the mobile device accessory relative to the mobile device; When the attachment state is identified as attached, adjusting operation of the mobile device based on an accessory profile, the accessory profile corresponding to the mobile device accessory; as well as When the attachment state is identified as unattached, adjusting the operation of the mobile device is abandoned. The method of claim 12 , wherein the attachment state is identified using accessory data captured using one or more sensors.

14. The method of claim 12, wherein identifying the mobile device accessory comprises identifying the presence of the mobile device accessory and obtaining the accessory profile.

15. The method of claim 12, wherein the accessory profile is obtained using at least one of a visual identifier or a transmitted identifier.

16. A system for managing attachments of a mobile device, the system comprising: an accessory management system configured to determine an attachment state of a mobile device accessory relative to a mobile device configured to plan a path of travel and corresponding movement from a first position toward a second position; as well as A control system is configured to control operation of the mobile device based on the attachment state of the mobile device accessory and an accessory profile corresponding to the mobile device accessory.

17. The system of claim 16, wherein at least one of the attachment status or the accessory profile is communicated to a user device.

18. The system of claim 16, wherein the attachment profile is obtained in response to scanning a visual identifier with a camera.

19. The system of claim 18, wherein the camera is associated with at least one of a user device or the mobile device.

20. The system of claim 16, wherein the accessory profile is obtained in conjunction with detecting presence of the mobile device accessory in proximity to the mobile device.

21. One or more tangible, non-transitory computer-readable storage media storing computer-executable instructions for executing a computer process on a computing system, the computer process comprising: obtaining a first accessory state of a mobile device accessory, the first accessory state corresponding to an expected behavior of the mobile device accessory during motion; obtaining accessory data corresponding to the mobile device accessory, the accessory data being captured in conjunction with movement along a movement path from a first location toward a second location, the mobile device accessory being attached to the mobile device; determining a second accessory state of the mobile device accessory based on the accessory data, the second accessory state corresponding to a behavior of the mobile device accessory related to the movement; identifying an event that affects at least one of mobile device operation of the mobile device or accessory operation of the mobile device accessory by comparing the expected behavior of the mobile device accessory to the behavior of the mobile device accessory; as well as A response to the event is determined.

22. The one or more tangible, non-transitory computer-readable storage media of claim 21, further comprising: An event type of the event is determined, and the response is determined based on the event type.

23. One or more tangible, non-transitory computer-readable storage media according to claim 22, wherein the response includes controlling at least one of the mobile device operation or the accessory operation when the event type is a movement type event, and the movement type event corresponds to the movement being affected by the event.

24. The one or more tangible, non-transitory computer-readable storage media of claim 23, wherein controlling the mobile device operation comprises adjusting the movement path.

25. The one or more tangible, non-transitory computer-readable storage media of claim 23, wherein controlling the accessory operation comprises stopping one or more operations of the mobile device accessory.

26. The one or more tangible, non-transitory computer-readable storage media of claim 23, wherein controlling the mobile device operation comprises at least one of slowing or stopping the movement.

27. One or more tangible, non-transitory computer-readable storage media according to claim 22, wherein the response includes marking the event when the event type is a maintenance type event, and the maintenance type event is within a predetermined level of change between the first accessory state and the second accessory state.

28. The one or more tangible, non-transitory computer-readable storage media of claim 27, wherein marking the event comprises generating an alert that is sent to at least one of the mobile device, a user device, or a remote device.

29. The one or more tangible, non-transitory computer-readable storage media of claim 28, wherein marking the event comprises recording information corresponding to the event in a log.

30. A method for managing accessories for a mobile device, the method comprising: obtaining a first accessory state of a mobile device accessory, the first accessory state corresponding to an expected behavior of the mobile device accessory during motion; obtaining accessory data corresponding to the mobile device accessory, the accessory data being captured in conjunction with movement along a movement path from a first location toward a second location, the mobile device accessory moving along the movement path with the mobile device; determining a second accessory state of the mobile device accessory based on the accessory data, the second accessory state corresponding to a behavior of the mobile device accessory related to the movement; identifying an event that affects at least one of mobile device operation of the mobile device or accessory operation of the mobile device accessory by comparing the expected behavior of the mobile device accessory to the behavior of the mobile device accessory; as well as A response to the event is determined.

31. The method of claim 30, wherein the responding comprises sending a communication to a remote device.

32. The method of claim 31, wherein the communication triggers at least one of control of the operation of the mobile device by the remote device or deployment of a second mobile device to the location of the mobile device.

33. The method of claim 30, wherein the expected behavior comprises an expected movement and an expected appearance.

34. The method of claim 33, wherein the expected movement comprises one or more of range of motion, flow of motion, vibration level, speed of change, and level of external motion, wherein the expected appearance comprises one or more of leveling, orientation, size, shape, texture, and color.

35. The method of claim 30, wherein the expected behavior comprises an expected temperature.

36. The method of claim 30, wherein the expected behavior comprises an expected attachment state.

37. A system for managing attachments of a mobile device, the system comprising: one or more sensors configured to capture accessory data corresponding to a mobile device accessory, the accessory data being captured in conjunction with movement along a movement path from a first location toward a second location, the mobile device accessory moving along the movement path with the mobile device; A monitoring system configured to identify an event that affects at least one of a mobile device operation of the mobile device or an accessory operation of the mobile device accessory by comparing a first accessory state of the mobile device accessory with a second accessory state of the mobile device accessory, and the monitoring system determines a response to the event.

38. The system of claim 37, wherein the mobile device comprises the one or more sensors and the responding is performed by the mobile device.

39. The system of claim 37, wherein the one or more sensors include at least one of a lidar, sonar, radar, camera, or microphone.

40. The system of claim 37, wherein the monitoring system determines a second response to escalate the response based on a change from the second accessory state to a third accessory state.

Images