Sharing externally captured content in communications

By leveraging remote devices to capture and share visual data, the challenges of obstructed views and safety risks in vehicle operations are mitigated, enabling secure and efficient data sharing in user-to-user communications.

JP2024546439APending Publication Date: 2024-12-24MICRON TECHNOLOGY INC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2024528468
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2021-11-15
Filing Date
2022-11-02
Publication Date
2024-12-24

AI Technical Summary

Technical Problem

Existing user-to-user communication devices face challenges in safely and effectively sharing visual data during vehicle operation, as using a mobile device's imaging device can obstruct the view and pose safety and property risks.

Method used

Utilizing a remote device, such as a vehicle or observation tower, to capture visual data which is then shared with the user's mobile device, allowing unobstructed visual data transmission without safety or property risks.

Benefits of technology

Enables safe and effective sharing of visual data by using remote devices to capture surroundings, reducing the risks associated with using a mobile device's imaging device during vehicle operation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024546439000001_ABST
    Figure 2024546439000001_ABST
Patent Text Reader

Abstract

A method, system, and device for communication are described. A connection may be established between a remote device including an imaging device and the device. Based on establishing the connection, first visual data associated with the imaging device may be received at the device. A second connection may be established between the device and a communication device, and communication between the device and the communication device may be supported via an application executing at the device. Based on establishing the second connection, visual data may be transmitted from the mobile device to the communication device via the application.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] Cross References This patent application claims priority to U.S. patent application 17 / 526,841 by Szubbocsev, entitled “SHARING EXTERNALLY CAPTURED CONTENT IN COMMUNICATIONS,” filed November 15, 2021, which is assigned to the assignee and is expressly incorporated herein by reference.

[0002] The technical field relates to sharing externally captured content in communications. [Background technology]

[0003] Devices that have access to a network (e.g., a wired network or a wireless network) may be programmed with applications that support user-to-user communication between the devices. These applications may include text, voice, or video-based messaging applications (e.g., short message service (SMS) applications, chat applications, etc.), voice-based calling applications (e.g., telephone applications), and video-based calling applications (e.g., video conferencing applications). Video-based calling applications may enable users to share with each other videos captured by their respective devices. In some examples, applications include a combination of text-based, voice-based, and video-based functionality. [Brief description of the drawings]

[0004] [Figure 1] 1 illustrates an example of a system that supports sharing of externally captured content in a communication according to examples described herein. [Figure 2A] 1 illustrates example communications supporting sharing of externally captured content according to examples described herein. [Figure 2B] 1 illustrates example communications supporting sharing of externally captured content according to examples described herein. [Diagram 3] 1 illustrates an example set of operations to support sharing of externally captured content according to examples described herein. [Figure 4] 1 illustrates a block diagram of a mobile device supporting sharing of externally captured content in a communication according to examples disclosed herein. [Diagram 5] 1 illustrates a block diagram of a communications manager supporting sharing of externally captured content in a communication according to examples disclosed herein. [Figure 6] 1 illustrates a block diagram of a remote device supporting sharing of externally captured content in a communication according to examples disclosed herein. [Figure 7] 1 illustrates a block diagram of a system including a mobile device, a remote device, and a communication device that supports sharing of externally captured content in a communication according to examples disclosed herein. [Figure 8] 1 illustrates an example set of operations to support sharing of externally captured content according to examples described herein. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] A mobile device may be used to establish a connection with another device that supports user-to-user communication (e.g., voice or video calling) while a vehicle is being operated. Based on establishing a connection, a user of the mobile device may wish to share details of the user's surroundings with a user of the other device. To do so, the user of the mobile device may enable the video calling functionality of the mobile device and capture the surroundings using an imaging device (e.g., a rear camera) in the mobile device. However, capturing the surroundings using an imaging device in the mobile device may result in a poor experience for other users (e.g., if the camera's view is obstructed by the vehicle's interior), raise safety concerns (e.g., if the driver is using the mobile device), raise property damage concerns (e.g., if the mobile device is located outside the vehicle), or any combination thereof.

[0006] To enable a mobile device to share visual aspects of the surrounding environment with improved quality, reduced risk to the mobile device, reduced risk to the driver, or a combination thereof, an imaging device in a remote device (e.g., a vehicle, observation tower, etc.) may be used by the mobile device in place of an imaging device in the mobile device. That is, the mobile device may share visual data captured by the imaging device in the remote device with a connected communication device. By sharing visual data captured by a remote device (e.g., a vehicle) by the mobile device, the mobile device may be used to share unobstructed visual data with another device with reduced risk to safety and property.

[0007] 1 illustrates an example of a system that supports sharing of externally captured content in a communication according to examples described herein. The system 100 may include a vehicle 115, a mobile device 102, a communication device 104, a network 125, and an observation device 105.

[0008] The vehicle 115 may be a motor vehicle (e.g., a motorcycle, an automobile, a sport utility vehicle, a truck, a bus, or a tractor trailer), a rail vehicle (e.g., a train, a tram, or a streetcar), a watercraft (e.g., a ship or a boat), an aircraft (e.g., an airplane, a helicopter, or a light aircraft), a spacecraft, or an amphibious vehicle. The vehicle 115 may comprise a set of sensors. The set of sensors may include one or more imaging devices 103 (e.g., an on-board camera, a backup camera, a radar, a lidar, or other imaging devices). The imaging devices 103 may be configured to capture still images (e.g., a still camera), video (e.g., a video camera), other types of images (e.g., a radar or lidar), or a combination thereof. In some examples, the imaging devices 103 may be configured to capture images outside the visible light spectrum (e.g., in the infrared spectrum). Additionally or alternatively, the imaging devices 103 may be configured to capture visual data at night (e.g., using night vision technology). The imaging device 103 may also be configured to capture audio.

[0009] Imaging devices 103 may be distributed throughout vehicle 115 to capture different views. For example, vehicle 115 may include cameras at its rear, its driver's side, its passenger's side, and its front. The different cameras may be used to capture overlapping and non-overlapping visual data related to vehicle 115. In some examples, vehicle 115 may use visual data captured by imaging devices 103 to support autonomous driving operations.

[0010] The mobile device 102 may be a personal electronic device, such as a mobile phone, laptop, personal computer, tablet, e-reader, etc. The mobile device 102 may also be a wireless device. The mobile device 102 may include one or more imaging devices 103. In some examples, the imaging device 103 in the mobile device 102 is configured differently from the imaging device 103 in the vehicle 115. For example, one or both of the hardware or functionality of the imaging device 103 in the mobile device 102 may be different from one or both of the hardware or functionality of the imaging device 103 in the vehicle 115. The mobile device 102 may be located with the vehicle 115. In some examples, multiple mobile devices (including the mobile device 102) may be included in the vehicle 115. In some examples, the mobile device 102 may be integrated with the vehicle 115 (e.g., built into or removable from the dashboard of the vehicle).

[0011] The mobile device 102 may have the capability to communicate with other devices (e.g., via a text network, a voice network, or a data network). The mobile device 102 may execute one or more applications (e.g., software applications). In some examples, a communication application is installed on the mobile device 102 that enables the mobile device 102 to support communication (e.g., text communication, voice communication, video communication) with other devices, such as the communication device 104.

[0012] The mobile device 102 may wirelessly access the network 125. The network 125 may be a communications network (e.g., a network supporting text, voice, or video communications). In some examples, the network 125 may be a data network (e.g., the Internet). The mobile device 102 may access the network 125 through an access network, e.g., a cellular network, a satellite network, or some other network supporting wireless data transfer. The network 125 may provide the mobile device 102 with access to other devices connected to the network 125, e.g., the communications device 104. In some examples, the vehicle 115 may wirelessly access the network 125. The observation device 105 may also wirelessly access the network 125.

[0013] The communication device 104 may have the capability to communicate with other devices (e.g., via a text network, a voice network, or a data network). The communication device 104 may be a personal electronic device, such as a mobile phone, a laptop, a desktop, a personal computer, a tablet, an e-reader, etc. The communication device 104 may be a wired or wireless device. The communication device 104 may access the network 125 through an access network, such as a cellular network, a satellite network, or a wired network (e.g., a cable network, a digital subscriber line network, etc.).

[0014] The observation device 105 may be a device (e.g., a pole or tower) configured to observe an environment within the field of view of the observation device 105. The observation device 105 may include one or more imaging devices 103. In some examples, the imaging device 103 in the observation device 105 is configured differently than the imaging device 103 in the vehicle 115, in the mobile device 102, or both. For example, the imaging device 103 in the vehicle 115 may use different hardware (e.g., larger hardware having additional, higher quality, more complex image sensors, larger lenses, etc.) and may have different functionality (e.g., improved magnification capabilities, enhanced image processing capabilities, etc.) than the imaging device 103 in the vehicle 115, in the mobile device 102, or both.

[0015] In some examples, the mobile device 102 may be used to establish a connection with another device (e.g., communication device 104) that supports user-to-user communication (e.g., voice or video calls) while in the vehicle 115 (e.g., while the vehicle 115 is being driven). Based on establishing the connection, the user of the mobile device 102 may wish to share details of the user's surroundings with the user of the other device. To do so, the user of the mobile device 102 may enable the video calling functionality of the mobile device 102 and capture the surroundings using the imaging device 103 (e.g., rear camera) in the mobile device 102. However, capturing the surroundings using the imaging device 103 in the mobile device 102 may result in a poor experience for other users (e.g., if the camera's view is obstructed by the vehicle's interior), raise safety concerns (e.g., when the driver is using the mobile device 102), raise property damage concerns (e.g., when the mobile device 102 is located outside the vehicle 115), or any combination thereof.

[0016] To enable the mobile device to share visual aspects of the surrounding environment with improved quality, reduced risk to the mobile device, reduced risk to the driver, or a combination thereof, an imaging device in a remote device (e.g., a vehicle, observation tower, etc.) may be used by the mobile device in place of an imaging device in the mobile device. That is, the mobile device may share visual data captured by the imaging device in the remote device with a connected communication device. The remote device may be a device whose internal operation is not controllable by the mobile device 102, uses different processing circuitry than the mobile device 102, is physically separate from the mobile device 102, or any combination thereof.

[0017] In some examples, an application supporting wireless communication of text, voice, video, or any combination thereof may be activated at the mobile device 102. Before or after the application is activated, a connection between the mobile device 102 and the vehicle 115 may be established. The connection may be a wireless connection (e.g., using Bluetooth or Wi-Fi) or a wired connection (e.g., using a Universal Serial Bus (USB) connection). Based on establishing the connection, visual data captured by the vehicle 115 may be received at the mobile device 102. A second connection between the mobile device 102 and the communication device 104 may also be established (e.g., via a wireless access network and a data network). Based on establishing the second connection, visual data captured by the vehicle 115 may be transmitted from the mobile device 102 to the communication device 104 via the application.

[0018] By sharing visual data captured by a remote device (e.g., a vehicle) by a mobile device, the mobile device can be used to share unobstructed visual data with another device with reduced risk to safety and property.

[0019] 2A illustrates an example of communication supporting sharing of externally captured content according to examples described herein. Communication 200 illustrates aspects of communication between two devices, a mobile device 202 and a communication device 204. The mobile device 202 and the communication device 204 may be examples of the mobile device 102 and the communication device 104, respectively, of FIG. 1. In some examples, one or both of the mobile device 202 and the communication device 204 may not include an imaging device.

[0020] The mobile device 202 may include a first main display 205-1 and a first local display 210-1. The first main display 205-1 may display data generated by the communication application, including visual data (e.g., video feed, photos, etc.) received from the communication device 204, icons (e.g., a first camera selector icon 215-1) for accessing functionality of the communication application, and menus (e.g., a first camera menu 220-1) for selecting functionality of the communication application. The first local display 210-1 may also display data generated by the communication application, including visual data generated at the mobile device 202 (e.g., a video feed being captured by the mobile device 202). The communication device 204 may similarly include a second main display 205-2 and a local display 210-2. The communication device 204 may also similarly execute different instances of the communication application running at the mobile device 202.

[0021] As described herein, the mobile device 202 may be able to access an imaging device in a remote device, e.g., a vehicle or observation tower. In some examples, the user of the mobile device 202 may wish to share with the user of the communication device 204 visual data captured by an imaging device in the remote device rather than visual data captured by the mobile device 202. In such a case, the user of the mobile device 202 may toggle the first camera selector icon 215-1 (e.g., by touching a corresponding area of ​​the first main display 205-1). In some examples, the first camera selector icon 215-1 may be a transparent or hidden icon that appears when a corresponding screen area (e.g., a lower left portion of the first main display 205-1) is touched.

[0022] A first camera menu 220-1 may be presented to the user based on toggling the first camera selector icon 215-1, and the first camera menu 220-1 may include a list of available cameras, including the mobile device's 202 forward-view or rear-view cameras, the vehicle's forward-view, driver-view, passenger-view, rear-view, or interior-view cameras, nearby tower cameras, or a combination thereof. If a remote camera is unavailable, the first camera selector icon 215-1 may be grayed out or removed from the display entirely. In some examples, the first option 225-1 of the first camera menu 220-1 may be used to select the vehicle's forward-view camera, and the second option 225-2 of the first camera menu 220-1 may be used to select the vehicle's driver-view camera. In some examples, the mobile device 202 may receive a command (e.g., from a user) to disable one or more of the available cameras (e.g., before establishing a call or during a call) so that the disabled camera or cameras are not accessible by the mobile device 202, the communication device 204, or both.

[0023] The communication device 204 may similarly display a second camera selector icon 215-2 and a second camera menu 220-2. In such a case, the communication device 204 may receive an indication of a set of available cameras accessible to the mobile device 202. To receive an indication of the set of available cameras, the communication device 204 may send a message to the mobile device 202 inquiring whether the mobile device 202 can access cameras other than the cameras in the mobile device 202.

[0024] Based on opening the first camera menu 220-1, the mobile device 202 may receive (e.g., from a user of the mobile device 202) a selection of one of the options 225 and, thereby, one of the available cameras. Additionally or alternatively, the communication device 204 may receive a selection of one of the options in the second camera menu 220-2 and, thereby, one of the available cameras. In such a case, the communication device 204 may transmit an indication of the selected option to the mobile device 202. In some examples, based on receiving at the mobile device 202 a selection from the communication device 204, a prompt may be displayed on the mobile device requesting permission to transmit visual data captured by the selected camera to the communication device 204. In some examples, the first camera menu 220-1 may include an operation for searching for available external imaging devices to connect therewith. Such a button may initiate an operation to search for available imaging devices, connect to an identified imaging device, or a combination thereof.

[0025] 2B illustrates an example of communication sharing externally captured content according to examples described herein. Based on receiving a selection of a driver-image camera of a connected vehicle, the mobile device 202 may transmit visual data captured (or being captured) by the driver-image camera to the communication device 204. In response, the visual data of the driver-image camera may be displayed on the second main display 205-2. In some examples, the visual data of the driver-image camera is displayed on the second main display 205-2 in place of the visual data captured by the camera on the mobile device 202. In other examples, the visual data of the driver-image camera is displayed on the second main display 205-2 together with the visual data captured by the camera on the mobile device 202 (e.g., in a split screen view).

[0026] In some examples, visual data being transmitted by the mobile device 202 to the communication device 204 may be displayed on the mobile device 202 in a first local display 210-1. When multiple sets of visual data from multiple cameras are being transmitted to the communication device 204, the first local display 210-1 may be used to display one or both of the multiple sets.

[0027] In some examples, a selection of a different camera (e.g., a vehicle's forward viewing camera) may be selected at the mobile device 202 or the communications device 204, and the mobile device 202 may transmit the visual data of the different camera to the communications device 204, e.g., instead of or in addition to the current set of visual data being transmitted to the communications device 204. In some examples, the mobile device 202 or the communications device 204 may receive a selection of multiple cameras. In such cases, the mobile device 202 may transmit multiple sets of visual data from multiple cameras to the communications device 204, and the multiple sets of visual data may be viewed simultaneously (e.g., in a split screen view) or alternating.

[0028] Although illustrated in FIGS. 2A and 2B in the context of a video call, the ability to share visual data captured at a remote device may similarly be used when the mobile device 202 and communication device 204 support communication using text messaging or voice calling.

[0029] FIG. 3 illustrates an example set of operations that support sharing of externally captured content according to examples described herein.

[0030] The process flow 300 may be performed by a remote device 301, which may be an example of a vehicle or observation tower described with reference to Figure 1, a mobile device 302, and a communication device 304, which may be an example of a mobile device and a communication device, respectively, described with reference to Figures 1 and 2. In some examples, the remote device 301 may be a device that is external to the mobile device 302 and includes an imaging device. One or more of the remote device 301, the mobile device 302, and the communication device 304 may include an imaging device, which may be a camera, a video camera, a ranging device, or any combination thereof.

[0031] In some examples, process flow 300 illustrates an exemplary sequence of operations that may be performed to support sharing of externally captured content in a communication. For example, process flow 300 illustrates operations for establishing a connection between a remote device and a mobile device to enable the mobile device to access an imaging device at the remote device, and operations for transmitting visual data captured at the remote device within a communication application by the mobile device to a communication device.

[0032] One or more of the operations described in process flow 300 may be performed earlier or later in the process, omitted, replaced, supplemented, or combined with other operations, etc. Also, additional operations described herein not included in process flow 300 may be included.

[0033] At 305, the remote device 301 may obtain an imaging device configuration. In some examples, the imaging device configuration may be configured during a manufacturing process - e.g., a manufacturer may select which of the imaging devices in the remote device to make accessible. In some examples, the imaging device configuration may configure a first set of imaging devices in the remote device 301 to be accessible to a first set of users (e.g., end users) and a second set of imaging devices in the remote device 301 to be accessible to a second set of users (e.g., the manufacturer or an authorized party).

[0034] At 310, a connection between the remote device 301 and the mobile device 302 may be established. In some examples, the connection between the remote device 301 and the mobile device 302 is established according to a protocol that includes exchanging messages to determine whether the remote device 301 has one or more imaging devices accessible to the other device. For example, the mobile device 302 may send a message to the remote device 301 inquiring whether the remote device 301 has imaging devices accessible to the mobile device 302, and the remote device 301 may respond with a message indicating a set of imaging devices accessible to the mobile device 302. In some examples, the response message indicates a different set of imaging devices based on attributes of the mobile device 302 (e.g., type of device, an identifier of the mobile device 302, authentication credentials provided by the mobile device, etc.). In some examples, the remote device 301 may establish connections with multiple mobile devices, including the mobile device 302.

[0035] Different protocols may be used to establish an initial communication link between the remote device 301 and the mobile device 302 through which a connection between the remote device 301 and the mobile device 302 may be established. The initial communication link may be established using a short-range wireless communication technology. For example, a Bluetooth link, a Wi-Fi link, or a wired link (e.g., using the USB protocol) may be used to establish the initial communication link.

[0036] In some examples, before indicating the set of available imaging devices, the remote device 301 may request authentication credentials from the mobile device 302, or the mobile device 302 may provide authentication credentials in an initial inquiry message. Additionally or alternatively, the remote device 301 may broadcast that one or more imaging devices at the remote device 301 are available for the mobile device to access.

[0037] In some examples, a connection between the remote device 301 and the mobile device 302 may be automatically established when the mobile device 302 enters the vicinity of the remote device 301 (e.g., when the mobile device 302 enters a vehicle). Additionally or alternatively, a connection between the remote device 301 and the mobile device 302 may be established after a communication application on the mobile device is activated. Additionally or alternatively, a connection between the remote device 301 and the mobile device 302 may be established after an initial setup procedure for registering the remote device 301 with the application is completed.

[0038] At 315, a communication application may be activated (e.g., by user input or automatically) on the mobile device 302. The communication application may be used to send text messages, voice messages, or media (e.g., photos, videos, etc.) messages between users of the application. Additionally or alternatively, the communication application may be used to establish voice calls, video calls, or both, between users of the application.

[0039] At 320, a user account for using the communications application may be created on the mobile device 302, for example, the first time the user opens the communications application. Creating a user account may include obtaining a username and password from the user along with other details of the user, including name, phone number, address, etc.

[0040] At 325, the remote device may be registered to a user account. That is, the user may add one or more remote devices to a list of available devices for the mobile device 302. In some examples, the remote device may have a unique identifier (e.g., pre-programmed or assigned during registration) so that a communication application can identify the remote device if another user attempts to add the remote device.

[0041] In some examples, during registration, the remote device 301 may display a pin (e.g., on a dashboard display) in response to receiving a registration request. The mobile device 302 may receive the pin (e.g., as a user input) prior to completing registration of the remote device 301. In some examples, the first user's account for registering the remote device 301 may be designated as an administrative account for the remote device 301. In such a case, the first user's account may be authorized to create rules that dictate how other mobile devices interface with the remote device 301. In some examples, the mobile device 302 may receive an input that prevents other user accounts from registering with the remote device 301. In some examples, the mobile device 302 may receive an input that dictates a subset of imaging devices in the remote device 301 that are accessible to other user accounts that register with the remote device 301. In some examples, the mobile device 302 may receive input granting any nearby mobile device that discovers the presence of the remote device 301 (e.g., a guest account) access to a subset of the imaging devices at the remote device 301 (e.g., an external camera of the remote device 301).

[0042] At 330, the mobile device 302 may identify a set of imaging devices at the remote device 301 available for access by the mobile device 302. For example, the mobile device 302 may identify one or more available imaging devices at the remote device 301. In some examples, the mobile device 302 selects a subset of the one or more available imaging devices for gaining access to visual data captured by the selected subset of the imaging devices.

[0043] At 335, the remote device 301 may buffer the visual data captured by one or more imaging devices configured in the remote device 301. In some examples, the remote device 301 starts buffering the visual data when the remote device 301 is powered on. Alternatively, the remote device 301 may buffer the visual data after establishing a connection with the mobile device 302. Alternatively, the remote device 301 may buffer the visual data after establishing a connection with the mobile device 302 and being registered with a user account.

[0044] At 340, the mobile device 302 may receive a visual dataset from the remote device 301. The visual dataset may include visual data captured from one or more imaging devices at the remote device 301. For example, the visual dataset may include a first set of visual data captured by a first imaging device and a second set of visual data captured by a second imaging device. The visual dataset may include buffered visual data, live visual data (e.g., photos or video streams), or both, and in some examples, the mobile device 302 received visual data from one or more imaging devices identified by the mobile device at 330.

[0045] At 345, the mobile device 302 may buffer visual data received from the remote device 301. For example, the mobile device 302 may buffer visual data received within a lifetime (e.g., within the last hour).

[0046] At 350, the mobile device 302 may select one or more of the imaging devices of the remote device 301 to make available to other communication devices, e.g., before making a call. In some examples, the mobile device 302 selects an imaging device after identifying available imaging devices at the remote device 301. The imaging device selected by the mobile device 302 may be the same or different from the imaging device selected at 330 for access by the mobile device 302.

[0047] At 355, the mobile device 302 may establish a connection with the communication device 304 via a communication application. The mobile device 302 may establish a voice call with the communication device 304. Alternatively, the mobile device 302 may establish a video call with the communication device 304. The connection may be established via an access network (e.g., a cellular or satellite network), a data network (e.g., the Internet), or both.

[0048] At 360, communication data may be exchanged between the mobile device 302 and the communication device 304 via a communication application. The communication data may include voice packets, video packets, photographs, text messages, or any combination thereof. In some examples, the video packets and photographs correspond to video captured by an imaging device in the mobile device 302.

[0049] At 365, the mobile device 302 may receive a query message from the communication 304 requesting an indication of available cameras at the mobile device 302 as part of data signaled for the communication application.

[0050] At 370, the mobile device 302 may send a response message corresponding to the inquiry message received from the communication device 304 as part of data signaled for the communication application. The response message may include an indication of one or more imaging devices available at the mobile device 302. The one or more available imaging devices may include one or more of the imaging devices at the mobile device 302 and one or more of the imaging devices at the remote device 301.

[0051] At 375, the mobile device 302 may receive a selection of one or more of the available imaging devices. For example, the mobile device 302 may select one or more of the imaging devices in the remote device 301 accessible to the mobile device 302.

[0052] At 380, the mobile device 302 may select one or more imaging devices of the remote devices 301 accessible to the mobile device 302. In some examples, the mobile device 302 may select the one or more imaging devices based on receiving a selection of the one or more imaging devices from a user of the mobile device 302. In other examples, the mobile device may select the one or more imaging devices based on receiving a selection of the one or more imaging devices from the communication device 304.

[0053] At 385, the mobile device 302 may transmit a first set of visual data to the communication device 304. The first set of visual data may include data captured by the one or more imaging devices selected at 380. In some examples, the first set of visual data includes first visual data captured by an imaging device at the remote device 301. The first set of visual data may also include second visual data captured by a second imaging device at the remote device 301 or by an imaging device at the mobile device 302.

[0054] At 390, one or more imaging devices of the remote device 301 accessible to the mobile device 302 may be selected a second time, where the one or more imaging devices may be different from the one or more imaging devices selected at 380. In some examples, the mobile device 302 may select the one or more imaging devices based on receiving a second selection of the one or more imaging devices from a user of the mobile device 302. In other examples, the mobile device may select the one or more imaging devices based on receiving a second selection of the one or more imaging devices from the communication device 304.

[0055] At 395, the mobile device 302 may transmit a second set of visual data to the communication device 304.

[0056] In some examples, the mobile device 302 may monitor the use of the remote device 301 using an established connection with the remote device 301. In such examples, the mobile device 302 may establish a communication link using a long-range wireless communication technology (e.g., cellular technology). The mobile device 302 may remotely access one or more imaging devices (e.g., internal or external imaging devices) in the remote device 301 using a communication application.

[0057] 4 illustrates a block diagram 400 of a mobile device supporting sharing of externally captured content in a communication according to an aspect of the disclosure. The mobile device 402 may be an example of an aspect of a mobile device described herein. The mobile device 402 may include a receiver 410, a transmitter 415, a communication manager 420, and an imaging device 425. The mobile device 402 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0058] The receiver 410 may provide a means for receiving information, such as packets, user data, control information, or any combination thereof. The information may be communicated to other components of the mobile device 402. The receiver 410 may use a single antenna or a set of multiple antennas.

[0059] The transmitter 415 may provide a means for transmitting signals generated by other components of the mobile device 402. For example, the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof. In some examples, the transmitter 415 may be collocated with the receiver 410 in a transceiver. The transmitter 415 may use a single antenna or a set of multiple antennas.

[0060] The imaging device 425 may provide a means for capturing visual data in the vicinity of the mobile device 402. The imaging device 425 may include components for capturing visual data and components for capturing audio data. The imaging device 425 may include memory for buffering the captured visual data, audio data, or both.

[0061] The communications manager 420, the receiver 410, the transmitter 415, the imaging device 425, or various combinations or components thereof may be examples of means for implementing various aspects of the sharing of externally captured content in communications described herein. For example, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0062] In some examples, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, the processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory).

[0063] Additionally or alternatively, in some examples, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., communications management software or firmware). When implemented in code executed by a processor, the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as a means for performing or otherwise supporting the functions described in this disclosure).

[0064] In some examples, the communications manager 420 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with the receiver 410, the transmitter 415, or both. For example, the communications manager 420 may receive information from the receiver 410, transmit information to the transmitter 415, or may be integrated in combination with the receiver 410, the transmitter 415, or both to receive information, transmit information, or perform various other operations described herein. The communications manager 420 may also receive visual data, audio data, or both from the imaging device 425, and may include data received from the imaging device in packets communicated using the transmitter 415.

[0065] The communications manager 420 may support communications in a device according to examples disclosed herein. For example, the communications manager 420 may be configured as or otherwise support a means for establishing, by a mobile device, a first connection with a vehicle including a camera. The communications manager 420 may be configured as or otherwise support a means for receiving, at the mobile device, from the vehicle a set of visual data associated with the camera based at least in part on establishing the first connection with the vehicle. The communications manager 420 may be configured as or otherwise support a means for establishing, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communications between the mobile device and the device. The communications manager 420 may be configured as or otherwise support a means for transmitting, to the device via an application, a set of visual data received from the vehicle based at least in part on establishing the second connection.

[0066] 5 illustrates a block diagram of a communications manager supporting sharing of externally captured content in communications according to aspects of the disclosure. Communications manager 520 may be an example of an aspect of communications manager 420 of FIG. 4. Communications manager 520, or various components thereof, may be an example of a means for implementing various aspects of sharing of externally captured content in communications described herein. For example, communications manager 520 may include a short-range connection manager 530, a visual data manager 535, a long-range connection manager 540, a messaging component 545, a remote device manager 550, a user account manager 555, an application manager 560, or any combination thereof. Each of these components may communicate directly or indirectly (e.g., via one or more buses) with one another.

[0067] The short-range connection manager 530 may be configured as or may otherwise support a means for establishing, by the mobile device, a first connection with a vehicle including a camera. The visual data manager 535 may be configured as or may otherwise support a means for receiving, at the mobile device, from the vehicle a set of visual data associated with the camera based at least in part on establishing the first connection with the vehicle. The long-range connection manager 540 may be configured as or may otherwise support a means for establishing, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device. The messaging component 545 may be configured as or may otherwise support a means for transmitting, by an application on the mobile device, a set of visual data received from the vehicle based at least in part on establishing the second connection to the device.

[0068] In some examples, the visual data manager 535 may be configured as or may otherwise support a query from the mobile device to the vehicle based at least in part on establishing a first connection with the vehicle regarding whether the vehicle supports sharing of visual data acquired by the vehicle. In some examples, the visual data manager 535 may be configured as or may otherwise support a query from the vehicle based at least in part on sending the query that the vehicle supports sharing of visual data, and a set of visual data is received at the mobile device based at least in part on receiving the indication.

[0069] In some examples, the remote device manager 550 may be configured as or otherwise support a means for associating a first identifier of the vehicle with an account of a user of the application by the application during an initial setup procedure. In some examples, the user account manager 555 may be configured as or otherwise support a means for authorizing the user's account, based at least in part on completing an initial setup procedure, to establish a mapping that provides other accounts of other users with access to respective combinations of a plurality of cameras installed in the vehicle, the plurality of cameras including the cameras.

[0070] In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving at the mobile device an indication of a set of cameras installed in the vehicle, the set of cameras including a camera, based at least in part on launching an application. In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving at the mobile device a selection of a camera from the set of cameras, the set of visual data of the camera being received at the mobile device from the vehicle based at least in part on selecting the camera.

[0071] In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving at the mobile device a second selection of a second camera from the set of cameras. In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving at the mobile device from the vehicle a second set of visual data related to the second camera based at least in part on selecting the second camera. In some examples, the messaging component 545 may be configured as or otherwise support a means for transmitting the second set of visual data to the device via an application either simultaneously with or in place of the set of visual data.

[0072] In some examples, the user account manager 555 may be configured or otherwise support a means for an application to determine the identity of a user of a mobile device, and the set of cameras directed to the user is based at least in part on the user's identity.

[0073] In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching an application, the set of cameras including a camera. In some examples, the messaging component 545 may be configured as or otherwise support a means for sending an indication of the set of cameras from the mobile device to the device based at least in part on establishing the second connection via an application. In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving from the device a selection of a camera from the set of cameras, the set of visual data being sent to the device via the application based at least in part on the selection.

[0074] In some examples, the plurality of mobile devices may include a communication manager similar to communication manager 515. In such cases, a short-range connection manager (similar to short-range connection manager 530) in each of the plurality of mobile devices may be configured as or otherwise support a means for establishing a respective connection with the vehicle, each of the plurality of mobile devices executing a respective instance of an application, the plurality of mobile devices including a mobile device that includes the communication manager 515. Also, a visual data manager (similar to visual data manager 535) in each of the plurality of mobile devices may be configured as or otherwise support a means for receiving a set of visual data based at least in part on establishing a respective connection with the vehicle. Also, a messaging component (similar to messaging component 545) in each of the plurality of mobile devices may be configured as or otherwise support a means for transmitting a set of visual data to a respective of the plurality of devices via a respective instance of an application, the plurality of devices including a device.

[0075] In some examples, the visual data manager 535 may be configured as or otherwise support a means for receiving, at a plurality of mobile devices, an indication of a set of cameras installed in the vehicle based at least in part on establishing respective connections thereto, the set of cameras including the cameras.

[0076] In some examples, the messaging component 545 may be configured as or otherwise support a means for transmitting a second set of visual data from the mobile device to the device via an application based at least in part on establishing a second connection, where the second set of visual data is captured by a camera of the mobile device and the set of vehicle visual data is transmitted in place of or simultaneously with the second set of visual data.

[0077] In some examples, the application supports text communication, voice communication, video communication, or any combination thereof. In some examples, the first connection with the vehicle is established based at least in part on launching the application.

[0078] In some examples, the application manager 560 may be configured as or otherwise support an application on the mobile device that supports wireless communication with other devices, and establishing a first connection with the vehicle is based at least in part on launching the application.

[0079] 6 illustrates a block diagram of a remote device supporting sharing of externally captured content in a communication according to an embodiment of the disclosure. The remote device 601 may be or may include an example of the components of a remote device described herein. The remote device 601 may communicate with other devices (e.g., mobile devices) wirelessly or via a wired connection. The remote device 601 may include components for two-way data communication, including components for transmitting and receiving communications, such as an I / O controller 610, a transceiver 615, a communications manager 620, one or more antennas 625, a memory 630, code 635, a processor 640, and an imaging device 645. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 650).

[0080] The I / O controller 610 may manage input and output signals for the remote device 601. The I / O controller 610 may also manage peripherals that are not integrated into the remote device 601. In some cases, the I / O controller 610 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 610 may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 610 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 610 may be implemented as part of a processor, e.g., processor 640. In some cases, a user may interact with the remote device 601 through the I / O controller 610 or through hardware components controlled by the I / O controller 610.

[0081] In some cases, the remote device 601 may include one or more antennas 625 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver 615 may communicate bidirectionally via the one or more antennas 625, a wired link, or a wireless link as described herein. In some examples, the one or more antennas 625 support short-range communication (e.g., with a mobile device), long-range communication (over a network), or both.

[0082] For example, the transceiver 615 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 615 may also include a modem for modulating packets, for providing modulated packets to one or more antennas 625 for transmission, and for demodulating packets received from the one or more antennas 625. The transceiver 615, or the transceiver 615 and the one or more antennas 625, may be an example of a transmitter, a receiver, or any combination or components thereof, as described herein.

[0083] Memory 630 may include random access memory (RAM) and read-only memory (ROM). Code 635 may be stored by memory 630. Code 635 may be computer readable and computer executable and may include instructions that, when executed by processor 640, cause remote device 601 to perform various functions described herein. Code 635 may be stored in a non-transitory computer readable medium, such as system memory or another type of memory. In some cases, code 635 may not be directly executable by processor 640, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some cases, memory 630 may include a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0084] The processor 640 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 640 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 640. The processor 640 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 630) to cause the remote device 601 to perform various functions (e.g., functions or tasks supporting sharing of externally captured content in a communication). For example, the remote device 601 or a component of the remote device 601 may include a processor 640 and a memory 630 coupled to the processor 640, where the processor 640 and the memory 630 are configured to perform various functions described herein.

[0085] The imaging device 645 may be configured to capture visual data, audio data, or both in the vicinity of the remote device 601. Data captured by the imaging device 645 may be stored in the memory 630.

[0086] The communications manager 620 may be configured to manage communications (e.g., control and data communications) between the remote device 601 and an access network. The communications manager 620 may also be configured to manage communications between the remote device 601 and another device over a wireless or wired link. The communications manager 620 may also be configured to manage aspects of communications between devices (e.g., a mobile device and a communication device) that occur via a communication application. For example, the communications manager 620 may be configured to handle a request from a mobile device for a set of available cameras at the remote device 601. The communications manager 620 may also be configured to transmit visual data, audio data, or both to the mobile device.

[0087] The communications manager 620 may be configured as or otherwise support a means for establishing a short-range connection with a mobile device, a long-range connection with a network, or both. The communications manager 620 may also be configured as or otherwise support a means for establishing a connection with a mobile device according to a protocol related to advertising a set of available imaging devices in the remote device 601 and providing visual data to the mobile device.

[0088] In some examples, communications manager 620 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in other ways in conjunction with transceiver 615, one or more antennas 625, or any combination thereof. Although communications manager 620 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 620 may be supported or performed by processor 640, memory 630, code 635, or any combination thereof. For example, code 635 may include instructions executable by processor 640 to cause remote device 601 to perform various aspects of sharing externally captured content in communications as described herein, or processor 640 and memory 630 may be otherwise configured to perform or support such operations.

[0089] 7 shows a block diagram of a system including a mobile device, a remote device, and a communication device that supports sharing of externally captured content in a communication according to examples disclosed herein. The system 700 may include a mobile device 702, a remote device 701, a network 755, and a communication device 704.

[0090] The mobile device 702 may be or may include an example of a component of a mobile device described herein. The mobile device 702 may communicate with other devices (e.g., remote devices or communication devices) wirelessly or via a wired connection. For example, the mobile device 702 may communicate with a remote device 701 via a wireless connection or a wired connection, which may be an example of a remote device described herein. The mobile device 702 may also communicate with a network 755 via a wireless connection, which may be an example of a network described herein. The network 755 may include an access network (e.g., a cellular or satellite access network) and a data network.

[0091] Mobile device 702 may include components for two-way data communication, including components for transmitting and receiving communications, such as an I / O controller 710, a transceiver 715, a communications manager 720, one or more antennas 725, memory 730, code 735, a processor 740, and an imaging device 745. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 750).

[0092] The I / O controller 710 may manage input and output signals for the mobile device 702. The I / O controller 710 may also manage peripherals that are not integrated into the mobile device 702. In some cases, the I / O controller 710 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 710 may use an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally or alternatively, the I / O controller 710 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 710 may be implemented as part of a processor, e.g., the processor 740. In some cases, a user may interact with the mobile device 702 through the I / O controller 710 or through hardware components controlled by the I / O controller 710.

[0093] In some cases, the mobile device 702 may include one or more antennas 725 that may be capable of simultaneously sending or receiving multiple wireless transmissions. The one or more antennas 725 may be used to support both short-range communications (e.g., using Bluetooth) and long-range communications (e.g., using cellular or satellite technologies).

[0094] The transceiver 715 may communicate bidirectionally via one or more antennas 725, a wired link, or a wireless link as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the transceiver 715 may communicate with a remote device 701 via a wired link or via a wireless link via one or more antennas 725 and may communicate with a network 755 via a wireless link. The transceiver 715 may also include a modem to modulate packets, to provide modulated packets to the one or more antennas 725 for transmission, and to demodulate packets received from the one or more antennas 725. The transceiver 715, or the transceiver 715 and the one or more antennas 725, may be an example of a transmitter, a receiver, or any combination thereof or components thereof, as described herein.

[0095] Memory 730 may include RAM and ROM. Code 735 may be stored by memory 730. Code 735 may be computer readable and computer executable and may include instructions that, when executed by processor 740, cause mobile device 702 to perform various functions described herein. Code 735 may be stored in a non-transitory computer readable medium, such as system memory or another type of memory. In some cases, code 735 may not be directly executable by processor 740, but may (e.g., when compiled and executed) cause a computer to perform functions described herein. In some cases, memory 730 may include a BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices, among other things.

[0096] The processor 740 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 740 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 740. The processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 730) to cause the mobile device 702 to perform various functions (e.g., functions or tasks supporting sharing of externally captured content in a communication). For example, the mobile device 702 or a component of the mobile device 702 may include a processor 740 and a memory 730 coupled to the processor 740, where the processor 740 and the memory 730 are configured to perform various functions described herein.

[0097] The imaging device 745 may be configured to capture visual data, audio data, or both in the vicinity of the mobile device 702. Data captured by the imaging device 745 may be stored in the memory 730.

[0098] The communications manager 720 may be configured to manage communications (e.g., control and data communications) between the mobile device 702 and an access network. The communications manager 620 may also be configured to manage communications between the remote device 601 and another device over a wireless or wired link. The communications manager 720 may also be configured to manage aspects of communications between devices (e.g., the remote device 701 and the communications device 704) that occur via a communications application. For example, the communications manager 720 may be configured to handle a request from the communications device 704 for a set of available / accessible cameras at the mobile device 702. The communications manager 720 may also be configured to receive visual data, audio data, or both from the remote device 701 and may be further configured to store the received data, relay the received data, or both.

[0099] The communications manager 720 may be configured as or may otherwise support a means for establishing, by the mobile device, a first connection with a vehicle including a camera. The communications manager 620 may be configured as or may otherwise support a means for receiving, at the mobile device, from the vehicle a set of visual data associated with the camera based at least in part on establishing the first connection with the vehicle. The communications manager 620 may be configured as or may otherwise support a means for establishing, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device. The communications manager 620 may be configured as or may otherwise support a means for transmitting, by the mobile device, a set of visual data received from the vehicle based at least in part on establishing the second connection to the device via the application.

[0100] In some examples, communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in other ways in conjunction with transceiver 715, one or more antennas 725, or any combination thereof. Although communications manager 720 is shown as a separate component, in some examples, one or more functions described with reference to communications manager 720 may be supported or performed by processor 740, memory 730, code 735, or any combination thereof. For example, code 735 may include instructions executable by processor 740 to cause mobile device 702 to perform various aspects of sharing externally captured content in communications as described herein, or processor 740 and memory 730 may be otherwise configured to perform or support such operations.

[0101] 8 illustrates an example set of operations supporting sharing of externally captured content according to examples described herein. The operations of method 800 may be implemented by a mobile device or components thereof as described herein. For example, the operations of method 800 may be performed by a mobile device as described with reference to FIGS. 1 through 5 and 7. In some examples, the mobile device may execute a set of instructions to control functional elements of the mobile device to perform the described functionality. Additionally or alternatively, the mobile device may perform aspects of the described functionality using dedicated hardware.

[0102] At 805, the method may include establishing, by the mobile device, a first connection with a vehicle that includes a camera. The operations of 805 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 805 may be performed by a short-range connection manager 530 as described with reference to FIG.

[0103] At 810, the method may include receiving at the mobile device from the vehicle a set of visual data associated with the camera based at least in part on establishing a first connection with the vehicle. The operations of 810 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 810 may be performed by visual data manager 535 as described with reference to FIG.

[0104] At 815, the method may include establishing, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device. The operations of 815 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 815 may be performed by a long-range connection manager 540 as described with reference to FIG.

[0105] At 820, the method may include transmitting the set of visual data received from the vehicle based at least in part on establishing the second connection from the mobile device to the device via the application. The operations of 820 may be performed according to examples disclosed herein. In some examples, aspects of the operations of 820 may be performed by messaging component 545 as described with reference to FIG.

[0106] In some examples, an apparatus described herein may perform one or more methods, such as method 800. An apparatus may include features, circuitry, logic, means, or instructions (e.g., a non-transitory computer-readable medium that stores instructions executable by a processor), or any combination thereof, for performing the following aspects of the present disclosure.

[0107] Aspect 1: A method or apparatus including operational features, electrical circuitry, logic, means, or instructions, or any combination thereof, for establishing a first connection by a mobile device with a vehicle including a camera; receiving at the mobile device from the vehicle a set of visual data related to the camera based at least in part on establishing the first connection with the vehicle; and establishing a second connection by an application on the mobile device with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device; and transmitting the set of visual data received from the vehicle based at least in part on establishing the second connection from the mobile device to the device via the application.

[0108] Aspect 2: The method or apparatus of aspect 1 further includes operations, features, electrical circuitry, logic, means, or instructions, or any combination thereof, for sending a query from the mobile device to the vehicle regarding whether the vehicle supports sharing of visual data acquired by the vehicle based at least in part on establishing a first connection with the vehicle, and receiving an indication from the vehicle that the vehicle supports sharing of the visual data based at least in part on sending the query, wherein the set of visual data is received at the mobile device based at least in part on receiving the indication.

[0109] Aspect 3: The method or apparatus of any of aspects 1 to 2, further including operations, features, circuitry, logic, means, or instructions, or any combination thereof, for associating a first identifier of the vehicle with an account of a user of the application by the application during an initial setup procedure, and authorizing the user's account to establish a mapping that provides access to respective combinations of a plurality of cameras installed in the vehicle to other accounts of other users, the plurality of cameras including the cameras, based at least in part on completing the initial setup procedure.

[0110] Aspect 4: The method or apparatus of any of Aspects 1 to 3, further including operations, features, circuitry, logic, means, or instructions, or any combination thereof, for receiving at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching the application, the set of cameras including a camera, and receiving at the mobile device a selection of a camera from the set of cameras, wherein a set of visual data of the cameras is received at the mobile device from the vehicle based at least in part on selecting the camera.

[0111] Aspect 5: The method or apparatus of aspect 4, further including operations, features, electrical circuitry, logic, means, or instructions, or any combination thereof, for receiving at the mobile device a second selection of a second camera from the set of cameras, receiving at the mobile device a second set of visual data from the vehicle related to the second camera based at least in part on the selection of the second camera, and transmitting the second set of visual data to the device via the application either simultaneously with or in place of the set of visual data.

[0112] Aspect 6: The method or apparatus of any of aspects 4 to 5, further comprising operations, features, circuitry, logic, means, or instructions, or any combination thereof, for determining, by an application, an identity of a user of the mobile device, wherein the set of cameras to be directed to the user is based at least in part on the identity of the user.

[0113] Aspect 7: The method or apparatus of any of aspects 1 to 6, further including operations, features, circuitry, logic, means, or instructions, or any combination thereof, for receiving at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching an application, the set of cameras including a camera; transmitting the indication of the set of cameras from the mobile device to the device via the application based at least in part on establishing a second connection; and receiving from the device a selection of a camera from the set of cameras, the set of visual data being transmitted to the device via the application based at least in part on the selection.

[0114] Aspect 8: The method or apparatus of any of aspects 1-7, further including operations, features, circuitry, logic, means, or instructions, or any combination thereof, for establishing, by a plurality of mobile devices, a respective connection with the vehicle, where each mobile device of the plurality of mobile devices executes a respective instance of the application, the plurality of mobile devices including a mobile device; receiving at the plurality of mobile devices a set of visual data from the vehicle based at least in part on establishing the respective connection with the vehicle; and transmitting, from each mobile device of the plurality of mobile devices to a respective device of the plurality of devices via the respective instance of the application, the plurality of devices including a mobile device.

[0115] Aspect 9: The method or apparatus of aspect 8, further comprising receiving, at a plurality of mobile devices, an indication of a set of cameras installed in the vehicle based at least in part on establishing respective connections, the set of cameras including a camera, and further comprising operations, features, circuitry, logic, means, or instructions, or any combination thereof, for performing the receiving.

[0116] Aspect 10: The method or apparatus of any of aspects 1 to 9, further including operations, features, circuitry, logic, means, or instructions, or any combination thereof, for transmitting a second set of visual data from the mobile device to the device via an application based at least in part on establishing a second connection, wherein the second set of visual data is captured by a camera of the mobile device, and the set of visual data of the vehicle is transmitted in place of or simultaneously with the second set of visual data.

[0117] Aspect 11: The method or apparatus of any of aspects 1 to 10, further including operations, features, circuitry, logic, means, or instructions, or any combination thereof, such that the application supports text communication, voice communication, video communication, or any combination thereof.

[0118] Aspect 12: The method or apparatus of any of aspects 1 to 11, further including operations, features, electrical circuitry, logic, means, or instructions, or any combination thereof, whereby a first connection with the vehicle is established based at least in part on launching an application.

[0119] Aspect 13: The method or apparatus of any of aspects 1 to 12, further comprising: launching, at the mobile device, an application that supports wireless communication with other devices, and establishing a first connection with the vehicle is based at least in part on launching the application; and further comprising operations, features, electrical circuitry, logic, means, or instructions, or any combination thereof, for performing the launching.

[0120] It should be noted that the methods described herein describe possible implementations, that acts and steps can be interchanged or otherwise modified, and that other implementations are possible. Additionally, portions of two or more of the methods may be combined.

[0121] DETAILED DESCRIPTION OF THE DEVICE The following provides an overview of aspects of the device described herein.

[0122] Aspect 14: An apparatus comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to establish, by a mobile device, a first connection with a vehicle including a camera; receive at the mobile device from the vehicle a set of visual data related to the camera based at least in part on establishing the first connection with the vehicle; establish, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device; and transmit, by way of the application, the set of visual data received from the vehicle based at least in part on establishing the second connection from the mobile device to the device.

[0123] Aspect 15: The apparatus of aspect 14, wherein the instructions are further executable by the processor to: send a query from the mobile device to the vehicle regarding whether the vehicle supports sharing of visual data acquired by the vehicle based at least in part on establishing a first connection with the vehicle; and receive an indication from the vehicle that the vehicle supports sharing of the visual data based at least in part on sending the query, wherein the set of visual data is received at the mobile device based at least in part on receiving the indication.

[0124] Aspect 16: The apparatus of any of aspects 14 to 15, wherein the instructions are further executable by the processor to: associate a first identifier of the vehicle with an account of a user of the application by the application during an initial setup procedure; and authorize the user's account to establish a mapping that provides other accounts of other users with access to respective combinations of a plurality of cameras installed in the vehicle, the plurality of cameras including the cameras, based at least in part on completing the initial setup procedure.

[0125] Aspect 17: The apparatus of any of aspects 14 to 16, wherein the instructions are further executable by the processor to receive at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching the application, the set of cameras including a camera, and receive at the mobile device a selection of a camera from the set of cameras, wherein the set of visual data of the cameras is received at the mobile device from the vehicle based at least in part on selecting the camera.

[0126] Aspect 18: The apparatus of any of aspects 14 to 17, wherein the instructions are further executable by the processor to: receive at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching the application, the set of cameras including a camera; transmit the indication of the set of cameras from the mobile device to the device via the application based at least in part on establishing the second connection; and receive from the device a selection of a camera from the set of cameras, the set of visual data being transmitted to the device via the application based at least in part on the selection.

[0127] Aspect 19: The apparatus of any of aspects 14-18, wherein the instructions are further executable by the processor to: establish, by the plurality of mobile devices, respective connections with the vehicle, where each mobile device of the plurality of mobile devices executes a respective instance of the application, the plurality of mobile devices including a mobile device; receive at the plurality of mobile devices a set of visual data from the vehicle based at least in part on establishing the respective connections with the vehicle; and transmit, from each mobile device of the plurality of mobile devices to a respective device of the plurality of devices via the respective instance of the application, the plurality of devices including a mobile device.

[0128] Non-Transitory Computer-Readable Media Described Below is provided an overview of aspects of the non-transitory computer-readable media described herein.

[0129] Aspect 20: A non-transitory computer readable medium storing code for wireless communication in a second device, the code including instructions executable by a processor to establish, by a mobile device, a first connection with a vehicle including a camera; receive, at the mobile device, a set of visual data associated with the camera from the vehicle based at least in part on establishing the first connection with the vehicle; establish, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device; and transmit, from the mobile device via the application, the set of visual data received from the vehicle based at least in part on establishing the second connection to the device.

[0130] Aspect 21: The non-transitory computer readable medium of aspect 20, wherein the code is further executable by the processor to: send a query from the mobile device to the vehicle regarding whether the vehicle supports sharing of visual data captured by the vehicle based at least in part on establishing a first connection with the vehicle; and receive an indication from the vehicle that the vehicle supports sharing of the visual data based at least in part on sending the query, wherein the set of visual data is received at the mobile device based at least in part on receiving the indication.

[0131] Aspect 22: The non-transitory computer readable medium of any of aspects 20 to 21, wherein the code is further executable by the processor to: associate a first identifier of the vehicle with an account of a user of the application by the application during an initial setup procedure; and authorize the user's account to establish a mapping that provides other accounts of other users with access to respective combinations of a plurality of cameras installed in the vehicle, the plurality of cameras including the cameras, based at least in part on completing the initial setup procedure.

[0132] Aspect 23: The non-transitory computer-readable medium of any of aspects 20 to 22, wherein the code is further executable by the processor to receive at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching the application, the set of cameras including a camera, and receive at the mobile device a selection of a camera from the set of cameras, wherein the set of visual data of the cameras is received at the mobile device from the vehicle based at least in part on selecting the camera.

[0133] Aspect 24: The non-transitory computer-readable medium of any of aspects 20 to 23, wherein the code is further executable by a processor to: receive at the mobile device an indication of a set of cameras installed in the vehicle based at least in part on launching the application, the set of cameras including a camera; transmit via the application the indication of the set of cameras from the mobile device to the device based at least in part on establishing a second connection; and receive from the device a selection of a camera from the set of cameras, the set of visual data being transmitted to the device via the application based at least in part on the selection.

[0134] Aspect 25: The non-transitory computer-readable medium of any of aspects 20-24, wherein the code is further executable by a processor to: establish, by the plurality of mobile devices, a respective connection with the vehicle, where each mobile device of the plurality of mobile devices is executing a respective instance of the application, the plurality of mobile devices including a mobile device; receive at the plurality of mobile devices a set of visual data from the vehicle based at least in part on establishing the respective connection with the vehicle; and transmit, from each mobile device of the plurality of mobile devices to a respective device of the plurality of devices via the respective instance of the application, the plurality of devices including a mobile device.

[0135] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Although some figures may show a signal as a single signal, a signal may represent a bus of signals, and the bus may have various bit widths.

[0136] The terms "if," "when," "based on," or "based at least in part on" may be used synonymously. In some instances, when the terms "if," "when," "based on," or "based at least in part on" are used to describe conditional actions, conditional processes, or connections between portions of processes, the terms may be interchangeable.

[0137] The term "in response to" may refer to a condition or action that occurs at least partially, if not completely, as a result of a previous condition or action. For example, a first condition or action may be implemented and a second condition or action may occur at least partially as a result of the previous condition or action occurring (either immediately after or after one or more other intermediate conditions or actions that occur after the first condition or action).

[0138] The terms "determine" or "determining" encompass a wide variety of actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, looking up (e.g., via looking up in a table, database, or another data structure), ascertaining, and the like. "Determining" can also include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. "Determining" can also include ascertaining, selecting, choosing, establishing, and other such similar actions.

[0139] With reference to the accompanying drawings, the description set forth herein describes example configurations and does not represent every example that may be implemented or is within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0140] In the accompanying figures, similar components or features may have the same reference label. Furthermore, various components of the same type may be distinguished by following the reference label with a hyphen and a second label that distinguishes the similar components. When merely a first reference label is used herein, the description is applicable to any one of the similar components having the same first reference label, regardless of the second reference label.

[0141] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, depending on the nature of the software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that parts of the functions are implemented in different physical locations.

[0142] For example, the various illustrated blocks and components described in connection with the disclosure herein may be implemented or embodied with a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0143] As used herein, including the claims, "or" used in a list of terms (e.g., a list of terms beginning with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such as, for example, listing at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be construed as referring to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be construed the same as the phrase "based at least in part on."

[0144] Computer-readable media includes both non-transitory computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. Non-transitory storage media may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of media. As used herein, disk and disc include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0145] The description in this specification is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will become apparent to those skilled in the art, and the general principles defined herein may be applied to other modifications without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. Establishing a first connection with a vehicle equipped with a camera by a mobile device; receiving, from the vehicle at the mobile device, a set of visual data associated with the camera based at least in part on establishing the first connection with the vehicle; establishing a second connection with a device remote from the mobile device by an application on the mobile device, the second connection supporting wireless communication between the mobile device and the device; transmitting the set of visual data received from the vehicle based at least in part on establishing the second connection from the mobile device to the device via the application; A method comprising:

2. sending an inquiry from the mobile device to the vehicle based at least in part on establishing the first connection with the vehicle regarding whether the vehicle supports sharing of visual data acquired by the vehicle; receiving an indication from the vehicle that the vehicle supports sharing of the visual data based at least in part on sending the query, wherein the set of visual data is received at the mobile device based at least in part on receiving the indication; The method of claim 1 further comprising:

3. associating a first identifier of the vehicle with an account of a user of the application by the application during an initial set-up procedure; authorizing the account of the user, based at least in part on completing the initial setup procedure, to establish a mapping that provides other accounts of other users with access to a respective combination of a plurality of cameras installed in the vehicle, the plurality of cameras including the camera; The method of claim 1 further comprising:

4. receiving, at the mobile device based at least in part on launching the application, an indication of a set of cameras installed in the vehicle, the set of cameras including the camera; receiving at the mobile device a selection of the camera from the set of cameras, the set of visual data of the cameras being received at the mobile device from the vehicle based at least in part on selecting the camera; The method of claim 1 further comprising:

5. receiving at the mobile device a second selection of a second camera from the set of cameras; receiving at the mobile device from the vehicle a second set of visual data associated with the second camera based at least in part on selecting the second camera; transmitting the second set of visual data to the device via the application simultaneously with or in place of the set of visual data; The method of claim 4 further comprising:

6. determining, by the application, an identity of a user of the mobile device, wherein the set of cameras to be directed to the user is based at least in part on the identity of the user; The method of claim 4 further comprising:

7. receiving, at the mobile device based at least in part on launching the application, an indication of a set of cameras installed in the vehicle, the set of cameras including the camera; transmitting the indication of the set of cameras from the mobile device to the device via the application based at least in part on establishing the second connection; receiving from the device a selection of the camera from the set of cameras, the set of visual data being transmitted to the device via the application based at least in part on the selection; The method of claim 1 further comprising:

8. establishing, by a plurality of mobile devices, respective connections with the vehicle, each mobile device of the plurality of mobile devices executing a respective instance of the application, the plurality of mobile devices including the mobile device; receiving, at the plurality of mobile devices, the set of visual data from the vehicle based at least in part on establishing the respective connections with the vehicle; transmitting the set of visual data from each mobile device of the plurality of mobile devices to a respective one of a plurality of devices via the respective instances of the application, the plurality of devices including the device; The method of claim 1 further comprising:

9. receiving, at the plurality of mobile devices, an indication of a set of cameras installed in the vehicle based at least in part on establishing the respective connections, the set of cameras including the camera; The method of claim 8 further comprising:

10. transmitting a second set of visual data from the mobile device to the device via the application based at least in part on establishing the second connection, the second set of visual data being captured by the camera of the mobile device, and the set of visual data of the vehicle being transmitted to the device instead of or simultaneously with the second set of visual data. The method of claim 1 further comprising:

11. The method of claim 1 , wherein the application supports text communication, voice communication, video communication, or any combination thereof.

12. The method of claim 1 , wherein the first connection with the vehicle is established based at least in part on launching the application.

13. launching, on the mobile device, the application supporting wireless communication with other devices, wherein establishing the first connection with the vehicle is based at least in part on launching the application. The method of claim 1 further comprising:

14. An apparatus comprising: A processor; a memory coupled to the processor; stored in the memory, Establishing a first connection by the mobile device with a vehicle equipped with a camera; receiving, from the vehicle at the mobile device, a set of visual data associated with the camera based at least in part on establishing the first connection with the vehicle; establishing, by an application on the mobile device, a second connection with a device remote from the mobile device, the second connection supporting wireless communication between the mobile device and the device; and transmitting the set of visual data received from the vehicle based at least in part on establishing the second connection from the mobile device to the device via the application. instructions executable by the processor to cause the device to An apparatus comprising:

15. The instructions further include: sending an inquiry from the mobile device to the vehicle based at least in part on establishing the first connection with the vehicle regarding whether the vehicle supports sharing of visual data acquired by the vehicle; receiving an indication from the vehicle that the vehicle supports sharing of the visual data based at least in part on sending the query, wherein the set of visual data is received at the mobile device based at least in part on receiving the indication; The apparatus of claim 14 , executable by the processor to:

16. The instructions further include: associating a first identifier of the vehicle with an account of a user of the application by the application during an initial set-up procedure; authorizing the account of the user, based at least in part on completing the initial setup procedure, to establish a mapping that provides other accounts of other users with access to a respective combination of a plurality of cameras installed in the vehicle, the plurality of cameras including the camera; The apparatus of claim 14 , executable by the processor to:

17. The instructions further include: receiving, at the mobile device based at least in part on launching the application, an indication of a set of cameras installed in the vehicle, the set of cameras including the camera; receiving at the mobile device a selection of the camera from the set of cameras, the set of visual data of the cameras being received at the mobile device from the vehicle based at least in part on selecting the camera; The apparatus of claim 14 , executable by the processor to:

18. The instructions further include: receiving, at the mobile device based at least in part on launching the application, an indication of a set of cameras installed in the vehicle, the set of cameras including the camera; transmitting the indication of the set of cameras from the mobile device to the device via the application based at least in part on establishing the second connection; receiving from the device a selection of the camera from the set of cameras, the set of visual data being transmitted to the device via the application based at least in part on the selection; The apparatus of claim 14 , executable by the processor to:

19. The instructions further include: establishing, by a plurality of mobile devices, respective connections with the vehicle, each mobile device of the plurality of mobile devices executing a respective instance of the application, the plurality of mobile devices including the mobile device; receiving, at the plurality of mobile devices, the set of visual data from the vehicle based at least in part on establishing the respective connections with the vehicle; transmitting the set of visual data from each mobile device of the plurality of mobile devices to a respective one of a plurality of devices via the respective instances of the application, the plurality of devices including the device; The apparatus of claim 14 , executable by the processor to:

20. 1. A non-transitory computer readable medium storing code for wireless communication in a second device, the code comprising: Establishing a first connection with a vehicle equipped with a camera by a mobile device; receiving, from the vehicle at the mobile device, a set of visual data associated with the camera based at least in part on establishing the first connection with the vehicle; establishing a second connection with a device remote from the mobile device by an application on the mobile device, the second connection supporting wireless communication between the mobile device and the device; transmitting the set of visual data received from the vehicle based at least in part on establishing the second connection from the mobile device to the device via the application; A non-transitory computer-readable medium comprising instructions executable by a processor to perform the steps of:

21. The code further comprises: sending an inquiry from the mobile device to the vehicle based at least in part on establishing the first connection with the vehicle regarding whether the vehicle supports sharing of visual data acquired by the vehicle; receiving an indication from the vehicle that the vehicle supports sharing of the visual data based at least in part on sending the query, wherein the set of visual data is received at the mobile device based at least in part on receiving the indication; 21. The non-transitory computer-readable medium of claim 20, executable by the processor to:

22. The code further comprises: associating a first identifier of the vehicle with an account of a user of the application by the application during an initial set-up procedure; authorizing the account of the user, based at least in part on completing the initial setup procedure, to establish a mapping that provides other accounts of other users with access to a respective combination of a plurality of cameras installed in the vehicle, the plurality of cameras including the camera; 21. The non-transitory computer-readable medium of claim 20, executable by the processor to:

23. The code further comprises: receiving, at the mobile device based at least in part on launching the application, an indication of a set of cameras installed in the vehicle, the set of cameras including the camera; receiving at the mobile device a selection of the camera from the set of cameras, the set of visual data of the cameras being received at the mobile device from the vehicle based at least in part on selecting the camera; 21. The non-transitory computer-readable medium of claim 20, executable by the processor to:

24. The code further comprises: receiving, at the mobile device based at least in part on launching the application, an indication of a set of cameras installed in the vehicle, the set of cameras including the camera; transmitting the indication of the set of cameras from the mobile device to the device via the application based at least in part on establishing the second connection; receiving from the device a selection of the camera from the set of cameras, the set of visual data being transmitted to the device via the application based at least in part on the selection; 21. The non-transitory computer-readable medium of claim 20, executable by the processor to:

25. The code further comprises: establishing, by a plurality of mobile devices, respective connections with the vehicle, each mobile device of the plurality of mobile devices executing a respective instance of the application, the plurality of mobile devices including the mobile device; receiving, at the plurality of mobile devices, the set of visual data from the vehicle based at least in part on establishing the respective connections with the vehicle; transmitting the set of visual data from each mobile device of the plurality of mobile devices to a respective one of a plurality of devices via the respective instances of the application, the plurality of devices including the device; 21. The non-transitory computer-readable medium of claim 20, executable by the processor to:

Citation Information

Patent Citations

  • Onboard telephone system

    JP2006254055A

  • Information providing system, in-vehicle device, and portable terminal

    JP2010250376A

  • Drive recorder system and in-vehicle camera system

    JP2013256167A

  • Vehicle surveillance system and vehicle surveillance method

    JP2021020484A

  • Electronic device and method for switching network connection between plurality of electronic devices

    US20200383157A1