Scene communication system

Abstract

A context communication system includes an external device including a communication receiver and an electronic control unit (ECU). The ECU includes data processing hardware and memory hardware that stores actions and action settings. The data processing hardware includes a contextual communication feature having a telematics system configured to detect the external device and a contextual event. The contextual communication feature is configured to selectively issue a contextual alert based on the detected external device and in response to a contextual event.

Description

[0001] Introduction

[0002] The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent it is described in this section, and aspects that may not be eligible as prior art at the time of filing, are neither expressly nor implicitly admitted as prior art against the present disclosure. Technical Field

[0003] The present disclosure generally relates to a contextual communication system. Background Art

[0004] Vehicles are typically used in combination with third - party devices. Although some third - party devices (such as mobile devices) can access geographical data, many devices used in combination with vehicles are not equipped with systems capable of independently monitoring geographical data. Therefore, manual adjustment of these devices by the user may be required. Alternatively, due to the potential inconvenience of the user performing an action or due to neglecting the manual activation step, the user may forego features that require manual adjustment or implementation. Summary of the Invention

[0005] In some aspects, a contextual communication system includes an external device that includes a communication receiver and an electronic control unit (ECU). The ECU includes data - processing hardware and memory hardware that stores actions and action settings. The data - processing hardware includes a contextual communication feature portion that has a telematics system configured to detect the external device and contextual events. The contextual communication feature portion is configured to selectively issue a contextual alert based on the detected external device and in response to a contextual event.

[0006] In some examples, an action may be associated with the external device, and the contextual communication feature portion may be configured to perform an action based on contextual event data corresponding to the detected contextual event. Optionally, the action settings stored in the memory hardware may include automatic settings and manual settings, and each action may be configured to have one of the automatic settings and the manual settings. The contextual communication feature portion may be configured to automatically perform an action configured with an automatic setting in response to a detected contextual event. In some instances, the contextual communication feature portion may be configured to issue an action notification associated with an action configured with a manual setting.

[0007] In some examples, a telematics system may include a geography application and a geofence. The situational communication feature portion may be configured to detect a communication receiver of an external device using at least one of the geography application and the geofence. In some cases, the ECU may be configured to directly access the external device to perform at least one action in response to a detected situational event. Optionally, the telematics system may be configured to detect the external device via the communication receiver. The situational communication feature portion may be configured to perform at least one action associated with the detected external device using situational event data corresponding to the situational event. A vehicle may include a situational communication system.

[0008] In other aspects, a situational communication system for a vehicle includes an external device that includes a communication receiver configured to share a connectivity state of the external device. Memory hardware stores actions and action settings, the action settings including at least one of an automatic setting and a manual setting. A geography application is configured to detect a location of the vehicle. Data processing hardware is communicatively coupled to the memory hardware and the geography application and includes a situational communication feature portion. The situational communication feature portion is configured to detect a situational event and includes a telematics system communicatively coupled to the geography application. The telematics system is configured to: detect the connectivity state of the external device, and the situational communication feature portion is configured to: selectively perform one or more of the actions in response to the detected connectivity state of the external device and the situational event.

[0009] In some examples, the situational communication feature portion may be configured to perform an action based on situational event data corresponding to a detected situational event. The situational event data may include one or more of a time of day, a location of the vehicle, a direction of travel of the vehicle, and a speed of the vehicle. The situational communication feature portion may be configured to issue an action notification associated with an action configured with a manual setting and may be configured to perform one or more actions in response to an input at the action notification. The situational communication feature portion may be configured to issue a reminder associated with an automatic setting in response to a detected situational event. Optionally, the situational communication feature portion may be configured to automatically perform at least one of one or more actions based on the location of the vehicle from the geography application.

[0010] In some cases, the data processing hardware may be configured to directly access an external device to perform at least one of one or more actions. Optionally, the external device may be configured for multiple functions, and the scenario communication feature may be configured to: based on the multiple functions of the external device, use scenario event data corresponding to the detected scenario event to perform at least one of the one or more actions. The scenario communication feature may be configured to use a telematics system to cooperate with a geographic application to identify actions associated with the multiple functions. A vehicle may include a scenario communication system.

[0011] In another aspect, a system includes at least one external device, a user device, and a vehicle. The at least one external device includes a communication receiver configured to share data of the at least one external device. The vehicle includes an electronic control unit (ECU). The ECU is communicatively coupled to the communication receivers of the at least one external device and the user device. The ECU includes a scenario communication feature configured to detect scenario events and configured to perform actions in response to the detected scenario events. The user device is configured to: receive a scenario alert from the scenario communication feature in response to the scenario event associated with the action. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are for illustrative purposes only for selected configurations and are not intended to limit the scope of the present disclosure.

[0013] Figure 1 is a perspective view of a vehicle and an external device of a scenario communication system according to the present disclosure;

[0014] Figure 2 is an enlarged partial perspective view of the interior of the vehicle, where an action notification according to the present disclosure is displayed on an infotainment display;

[0015] Figure 3 is a schematic block diagram of a scenario communication system according to the present disclosure;

[0016] Figure 4 is an example flowchart for a scenario communication system according to the present disclosure;

[0017] Figure 5 is another example flowchart for a scenario communication system according to the present disclosure; and

[0018] Figure 6 is Figure 5 an example flowchart of the scenario communication system of.

[0019] In all the drawings, corresponding reference numerals represent corresponding components. DETAILED DESCRIPTION

[0020] Example configurations will now be described more fully with reference to the accompanying drawings. The example configurations are provided so that this disclosure will be thorough and will fully convey the scope of the disclosure to those of ordinary skill in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configurations of this disclosure. It will be apparent to those of ordinary skill in the art that specific details need not be employed, that the example configurations may be embodied in many different forms, and that the specific details and example configurations should not be construed as limiting the scope of the disclosure.

[0021] The terms used herein are for the purpose of describing particular example configurations only and are not intended to be limiting. As used herein, the singular articles "a" and "the" may also be intended to include the plural forms, unless the context clearly indicates otherwise. The terms "comprising," "including," and "having" are inclusive and thus specify the presence of stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein should not be construed as necessarily requiring them to be performed in the particular order discussed or illustrated, unless specifically identified as an order of performance. Additional or alternative steps may be employed.

[0022] When an element or layer is referred to as being "on," "engaged to," "connected to," "attached to," or "coupled to" another element or layer, it can be directly on, engaged, connected, attached, or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on," "directly engaged to," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, intervening elements or layers may not be present. Other words used to describe the relationship between elements should be interpreted in a like manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.). As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0023] The terms "first," "second," "third," etc. may be used herein to describe various elements, components, regions, layers, and / or sections. These elements, components, regions, layers, and / or sections should not be limited by these terms. These terms may be used only to distinguish one element, component, region, layer, or section from another. Unless the context clearly indicates otherwise, terms such as "first," "second," and other numerical terms do not imply an order or sequence. Thus, a first element, component, region, layer, or section discussed below may be referred to as a second element, component, region, layer, or section without departing from the teachings of the example configurations.

[0024] In this application, including the following definitions, the term "module" may be replaced by the term "circuit". The term "module" may refer to an application specific integrated circuit (ASIC), be part of or include it; digital, analog or mixed analog / digital discrete circuits; digital, analog or mixed analog / digital integrated circuits; combinational logic circuits; field programmable gate arrays (FPGAs); processors (shared, dedicated or groups) that execute code; memories (shared, dedicated or groups) that store code executed by the processors; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.

[0025] As used above, the term "code" may include software, firmware, and / or microcode, and may refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes a processor that, in combination with additional processors, executes some or all of the code from one or more modules. The term "shared memory" encompasses a single memory that stores some or all of the code from multiple modules. The term "group memory" includes a memory that, in combination with additional memories, stores some or all of the code from one or more modules. The term "memory" may be a subset of the term "computer-readable medium". The term "computer-readable medium" does not include transient electrical and electromagnetic signals propagated through a medium, and thus may be considered tangible and non-transient memory. Non-limiting examples of non-transitory memory include tangible computer-readable media that include non-volatile memory, magnetic memory, and optical memory.

[0026] The devices and methods described in this application may be implemented in part or in whole by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions stored on at least one non-transitory tangible computer-readable medium. The computer programs may also include and / or rely on stored data.

[0027] A software application (i.e., a software resource) may refer to computer software that causes a computing device to perform tasks. Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0028] A non-transitory memory can be a physical device for temporarily or permanently storing programs (e.g., sequences of instructions) or data (e.g., program state information) for use by a computing device. The non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware such as a boot program). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and magnetic disks or tapes.

[0029] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and can be implemented in high-level procedural and / or object-oriented programming languages and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., a magnetic disk, an optical disk, a memory, a programmable logic device (PLD)) that provides machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal that provides machine instructions and / or data to a programmable processor.

[0030] Various implementations of the systems and techniques described herein can be implemented in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application-specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementations in one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which can be special-purpose or general-purpose, coupled to receive data and instructions from, and to send data and instructions to, a storage system, at least one input device, and at least one output device.

[0031] The processes and logical flows described in this specification can be performed by one or more programmable processors (also referred to as data processing hardware) that execute one or more computer programs to perform functions by operating on input data and generating output. The processes and logical flows can also be performed by special purpose logic circuitry, such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). As an example, processors suitable for the execution of a computer program include both general and special purpose microprocessors, and any one or more processors of any type of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include one or more mass storage devices for storing data (such as magnetic disks, magneto-optical disks, or optical disks), or be operatively coupled to receive data therefrom or transfer data thereto or both. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0032] To provide for interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device (such as, for example, a CRT (Cathode Ray Tube), LCD (Liquid Crystal Display) monitor, or touch screen) for displaying information to the user and, optionally, a keyboard and a pointing device (such as, for example, a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input received from the user may be in any form, including acoustic, speech, or tactile input. Additionally, a computer may interact with a user by sending documents to and receiving documents from the device used by the user; for example, by sending a web page to a web browser on a client device of the user in response to a request received from the web browser.

[0033] Referring Figures 1-3 , the scenario communication system 10 is configured to interconnect the vehicle 100 and at least one external device 200. The external device 200 may include, but is not limited to, a trailer, a solar panel, a trunk, lighting devices, and any other external device or feature that can be operated via the scenario communication system 10. For example, Figure 1Shows a trailer 200a equipped with a solar panel 200b. The external device(s) 200 are described in more detail below. Although the context communication system 10 is described with respect to the vehicle 100 and the external device 200, it is contemplated that the context communication system 10 may include a user device(s) 300 that can communicate with the external device 200.

[0034] For example, the user device 300 may be a mobile device equipped with the features described herein with respect to the vehicle 100. Additionally or alternatively, the user device 300 may be used in combination with the vehicle 100 to receive an input 302 from the user, as described in more detail below. The vehicle 100 includes an infotainment display 102 that can also receive an input 302 from the user. As described herein, the input 302 generally corresponds to a selection and / or execution made by the user with respect to the context communication system 10.

[0035] The vehicle 100 includes an electronic control unit (ECU) 12 configured with data processing hardware 14 and memory hardware 16. As described in more detail herein, the data processing hardware 14 includes a context communication feature portion 18 that, as part of the context communication system 10, cooperates to communicate with a communication receiver 202 of the external device 200. The context communication feature portion 18 is configured to detect a context event 20 and store context event data 22. The context event data 22 includes, but is not limited to, the time of day 24, location 26, direction of travel 28, and / or speed 30 of the vehicle 100. In addition to the above context events 20, the context event 20 may also include an off-board event, such as arriving at a predetermined destination and points of interest that may be associated with one or more external devices 200. The context event data 22 may be collected or otherwise identified and monitored by a telematics system 32 of the context communication feature portion 18. The telematics system 32 is configured to detect the external device 200 and the context event 20. In addition, the telematics system 32 monitors the location 26 of the vehicle 100 and receives updated location information regarding any detected external device 200.

[0036] The telematics system 32 may include a geography application 34 that can be used to monitor the location 26 of the vehicle 100. It is contemplated that the application 34 may be selectively deactivated by the user. Thus, if the telematics system 32 cannot identify the location 26 of the vehicle 100, the context communication feature portion 18 may prompt the user that the current location 26 is unavailable. The context communication feature portion 18 may then prompt the user to activate the geography application 34 by authorizing location sharing.

[0037] The telematics system 32 can also be used by the context communication system 10 to monitor any detected external device 200. For example, the telematics system 32 can detect the external device 200 and determine the connection status of the detected external device 200. The telematics system 32 is communicatively coupled to the communication receiver 202 of the external device 200. Accordingly, the telematics system 32 also receives and monitors the location and movement status of the external device 200. The geographic application 34 of the telematics system 32 can define a geofence 36 related to the vehicle 100 and the detected external device 200. The geofence 36 aids in tracking context event data 22 related to the vehicle 100 and the external device 200. For example, the context communication feature 18 is configured to detect the communication receiver 202 of the external device 200 using at least one of the geographic application 34 and the geofence 36.

[0038] The telematics system 32 aids the context communication feature 18 in identifying context events 20. For example, the context communication feature 18 can selectively issue a context alert 38 in response to context event data 22 and based on the detected external device 200, which can include a selection for the user of the external device 200 based on the context event 20. The telematics system 32 can also aid the context communication feature 18 in identifying an action 40 for the vehicle 100 and / or the external device 200 based on the context event 20. The action 40 can be associated with the external device 200, and the context communication feature 18 can be configured to perform the action 40 based on the context event data 22. For example, the telematics system 32 can be used to identify relative positioning data 42 of the external device 200 based on the geofence 36, as described in more detail below. The relative positioning data 42 can include, but is not limited to, channel sounding, ultra wideband, and / or low energy anchor for providing orientation and remote adjustment.

[0039] Still referring to Figures 1-3, before performing action 40, the situational communication feature unit 18 can issue a situational alert 38 in response to the situational event 20. The situational alert 38 can be displayed on the infotainment display 102 of the vehicle 100 and / or on the display 304 of the user device 300. The ECU 12 can receive an input 302 indicating a selection in response to the situational alert 38, which will be described in more detail below. The situational alert 38 is associated with one or more actions 40 that can be performed by the situational communication system 10. In some examples, the action 40 can be performed by the situational communication system 10 without the situational communication feature unit 18 issuing the situational alert 38. For example, certain actions 40 can be programmed as part of the situational communication system 10 to occur in response to the associated situational event 20.

[0040] The action 40 can be stored in the memory hardware 16 and can have a corresponding action setting 44. The action 40 can be associated with an external device 200 such that the ECU 12 can select the action 40 to be performed from one or more actions 40 based on the situational event data 22. The action 40 is configured with an action setting 44, and the action setting 44 includes an automatic setting 46 and a manual setting 48. The action setting 44 defines whether an action notification 50 associated with the action 40 configured with the manual setting 48 is issued by the situational communication feature unit 18 in response to the situational event 20. For example, the situational communication system 18 is configured to issue the action notification 50 when the action 40 associated with the detected situational event 20 has the manual setting 48. The manual setting 48 of the action 40 is defined as the ECU12 receiving an input 302 from the user before performing the action 40. Certain actions 40 can be preset or have a default manual setting 48.

[0041] The action setting 44 can be set by the user of the situational communication system 10 and / or can be set by the manufacturer. The action setting 44 can be adjusted or otherwise changed by the user to personalize the user preferences. In some cases, the action setting 44 can be changed by the user such that some action settings 44 can be changed between the automatic setting 46 and the manual setting 48 according to the user preferences. Additionally or alternatively, the action setting 44 for the corresponding action 40 can be set by the manufacturer to maximize the efficiency of the vehicle 100. In some examples, the automatic setting 46 can be associated with a light-emitting diode (LED) lighting device 200 such that the automatic activation of the LED lighting device 200 is negligible with respect to the efficiency of the vehicle 100.

[0042] The situational communication feature unit 18 is configured to automatically perform an action 40 configured with an automatic setting 46 in response to a detected situational event 20. The situational communication feature unit 18 may also issue a reminder 52 associated with the action 40 configured with the automatic setting 46. The reminder 52 may provide the user with an option to change the action setting 44 associated with the corresponding automatic action 40 from the automatic setting 46 to a manual setting 48. The reminder 52 may be dismissed by the user, and the ECU 12 may be configured to stop issuing the reminder 52 after a predetermined number of times the user dismisses it.

[0043] Still referring to Figures 1-3 , each action 40 is associated with a situational event 20 detected by the situational communication feature unit 18 such that the situational communication feature unit 18 can prompt the user for an action 40 determined to be associated with the situational event 20 and the external device 200 based on the situational event data 22. The situational event 20 may be determined at least in part by the telematics system 32 via the geography application 34, as described above. The geography application 34 is configured to detect the location 26 of the vehicle 100 and share the location and other relevant situational event data 22 with the external device 200 via the telematics system 32. The situational communication feature unit 18 may also share situational event data 22 associated with the speed 30 and direction of travel 28 of the vehicle 100 and the time of day 24 during which the vehicle 100 is operating with the external device 200. For example, the situational communication feature unit 18 may transmit the time of day 24 and the location 26 to an external LED lighting device 200, and the external LED lighting device 200 may be activated in response to the provided situational event data 22. The situational event data 22 may be shared with the external device 200 using short-range wireless. In some examples, short-range wireless may include, but is not limited to The ECU 12 determines whether sharing with the external device 200 is available and determines the type of external device 200 connected to the situational communication system 10.

[0044] As described above, the external device 200 may include a series of devices separate from the ECU 12 but capable of communicating with the ECU 12. For example, the memory hardware 16 may include stored devices 60, and the stored devices 60 include the external device 200. The ECU 12 may determine which of the stored devices 60 are detected using the situational communication system 10 via detection by the telematics system 32. For example, the telematics system 32 may use a geofence 36 to identify the communication receiver 202 of the corresponding external device 200. In some cases, a single communication receiver 202 may be used for multiple external devices 200.

[0045] For example, Figure 1The solar panel 200b shown is disposed on the trailer 200a. In this example, the solar panel 200b can utilize the same communication receiver 202 as the trailer 200a. Thus, the telematics system 32 can identify both the trailer 200a and the solar panel 200b via the communication receiver 202. Additionally or alternatively, each external device 200 can have a different communication receiver 202, and the telematics system 32 can use the geofence 36 and the corresponding communication receiver 202 to distinguish the detected external devices. The telematics system 32 is configured to receive a connection signal 204 from the communication receiver 202, and the telematics system 32 uses this connection signal 204 to detect the connection status 204a of the external device 200. The context communication feature 18 is configured to selectively perform one or more of the actions in response to the detected connection status 204a of the external device 200 and the context event 20.

[0046] The geofence 36 of the telematics system 32 can also be used as a context event 20 such that the telematics system 32 can detect that the external device 200 and / or the vehicle 100 is within the geofence 36 defined by the ECU 12. In response, the context communication feature 18 can determine whether to perform the action 40 or continue to issue the context alert 38 based on the context configuration of the external device 200. The communication receiver 202 can generally be used to identify the external device 200 and any associated external devices 200. The communication receiver 202 can indicate to the telematics system 32 which external devices 200 are currently active and / or connected to the vehicle 100. As described above, the memory hardware 16 can store the stored devices 60 that can be associated with the detected external devices 200. The memory hardware 16 can associate the action 40 and the context event 20 with the stored device 60 and store the action 40 and the context event 20. Thus, the context communication feature 18 can easily identify the action 40 based on the context event 20 and the detected external device 200.

[0047] The stored device 60 may include active and / or connected external devices 200, as well as inactive or disconnected external devices 200. As described above, communication may be via a short-range wired or wireless connection between the ECU 12 and the external device 200. For example, the external device 200 may have a multi-functional use, such as a trailer and / or recreational vehicle (RV), where the location 26 and the time of day 24 may be advantageous data points for the operation of the external device 200. The situational communication feature 18 is configured to perform at least one of the actions 40 based on the multi-functional use of the external device 200 using situational event data 22 corresponding to the detected situational event 20. The situational communication feature 18 collaborates with the telematics system 32 and the geographic application 34 to identify the actions 40 associated with the multi-functional use of the external device 200. Additionally, in this example, the ECU 12 may provide global positioning system (GPS) data as part of the situational event data 22 to the external device 200 (such as a satellite antenna) via the situational communication feature 18 for the external device 200 to automatically locate the satellite position. The relative positioning data 42 received from the situational communication feature 18 via the telematics system 32 may be used to automatically tune the satellite antenna.

[0048] In other examples, the external device 200 may have a single function, such as a low-energy connection. A non-limiting example of a low-energy connection of the external device 200 may include a solar panel or a satellite, which may be selectively repositioned to maximize functionality. For example, the situational communication feature 18 may provide the situational event data 22 to the solar panel 200b via the telematics system 32, so that the solar panel 200b can track the position of the sun and take into account cloud cover to maximize energy capture. Another example of the external device 200 includes that the ECU 12 has direct and full access to the connected device, such as an LED lighting device. For example, the ECU 12 may be configured with direct access to the external device 200 to perform at least one of the actions 40 in response to the detected situational event 20. Some external devices 200 may be controlled by a setup routine 206. The routine 206 may be configured based on the situational event data 22, otherwise the external device 200 may not receive or detect the situational event data 22 independently of the situational communication feature 18. For example, the routine 206 may include, but is not limited to, opening awnings, deploying extension devices, lowering leveling jacks, and / or starting a water heater and a furnace.

[0049] Further reference Figures 1 to 3Once the vehicle 100 is in operation, the ECU 12 monitors the external device 200. The ECU 12 can detect a new external device 200 and / or detect a known external device 200. For example, the ECU 12 can search for the external device 200 until the external device 200 is detected and connected. Once the external device 200 is detected, the ECU 12 monitors the scenario event 20.

[0050] The scenario communication system 10 is configured to determine whether to perform one or more actions 40 based on the scenario event data 22. For example, one or more actions 40 are available to be performed by the ECU 12, and the scenario communication feature unit 18 determines whether to perform the action 40 based on the scenario event data 22 and the action setting 44 of the corresponding action 40. In some examples, the ECU 12 can determine that the associated available action 40 has a manual setting 48 such that the scenario communication feature unit 18 performs the scenario alert 38 instead of automatically performing the action 40. Thus, the user can determine whether to activate the action 40. In some cases, the action 40 can have an automatic setting 46 such that the ECU 12 can automatically perform the action 40. In this example, the ECU 12 can issue a reminder 52 to the user that the ECU 12 has performed the action 40 with the automatic setting 46. The user can adjust the action setting 44 or dismiss the reminder 52.

[0051] In other examples, the action 40 can have a manual setting 48 such that the scenario alert 38 is prompted to the user to authorize the execution of the action 40. The scenario alert 38 notifies the user of the available action 40 to provide an option to perform the action 40. If the user authorizes the action 40, the external device 200 performs the associated action 40 based on the scenario event data 22. If the user rejects the scenario alert 38, the ECU 12 continues to monitor the scenario event 20 and potentially associated actions 40.

[0052] Still referring to Figures 1-3 the ECU 12 uses the telematics system 32 and the communication receiver 202 of the external device 200 to determine the relative positioning data 42 of the external device 200. The ECU 12 can use the relative positioning data 42 associated with the corresponding external device 200 to define the spatial awareness between the external devices 200 and / or to effect an adjustment to the external device 200. For example, the ECU 12 can be configured to transmit the relative positioning data 42 in combination with the action 40 to relocate or otherwise identify the displacement of the external device 200. Thus, depending on the external device 200 and the action 40, the relative positioning data 42 can be used in combination with one or more of the actions 40.

[0053] In some instances, the situational communication feature 18 may be configured to issue a situational alert 38 in response to a detected situational event 20 rather than prompting for an action 40. For example, the situational communication feature 18 may determine whether the situational alert 38 is configured for the infotainment display 102 of the vehicle 100 or the user's user device 300. The situational communication feature 18 may push the situational alert 38 to the user device 300 via a text message and / or an application on the user device 300. The situational alert 38 may provide the user with options to adjust the action 40 and may also include instructions for the user.

[0054] Now referring to Figures 3 to 6 , an example flowchart of the situational communication system 10 is described. The ECU 12 determines at 400 whether location sharing is available. If location sharing is not available, the ECU 12 notifies the user at 402 that location sharing is not available. If location sharing is available, the ECU 12 determines at 404 whether any external devices 200 are connected. If no external devices 200 are connected, the ECU 12 notifies the user at 406 that no connected external devices 200 have been detected. If one or more external devices 200 are detected, the ECU 12 determines at 408 what type of external device 200 is connected. For example, the ECU 12 may detect a direct control device 200 at 410. Optionally, at 412, the ECU 12 may detect a single-function device 200. In other cases, the ECU 12 may detect a multi-functional device 200 at 414.

[0055] Figure 5 and Figure 6Shows another example flowchart of the situational communication system 10. The ECU 12 determines at 500 whether an external device 200 is connected and detected. If the external device 200 is not detected, the ECU 12 continues to monitor for any potential connections. If the external device 200 is detected, the ECU 12 monitors the situational event 20 at 502. The ECU 12 determines at 504 whether the situational event 20 is detected. If the situational event 20 is not detected, the ECU 12 continues to monitor the situational event 20. If the situational event 20 is detected, the ECU 12 determines at 506 whether to execute the action 40 or the situational alert 38. When the action 40 is executed, the ECU 12 determines at 508 whether the action 40 has an automatic setting 46 or a manual setting 48. If the action 40 has a manual setting 48, the ECU 12 determines at 510 whether the action 40 is confirmed. If the action 40 is not confirmed, the ECU 12 continues to monitor other situational events 20. If the action 40 is confirmed, the ECU 12 determines at 512 whether there is relative positioning data 42 known for the external device 200 and the associated action 40. Similarly, if the action 40 has an automatic setting 46, the ECU 12 continues to determine whether there is relative positioning data 42 known for the external device 200 and the associated action 40. If there is known relative positioning data 42, the ECU 12 provides an adjustment based on the relative positioning data 42 at 514 and executes the action 40 at 516. If no relative positioning data 42 is known, the ECU 12 executes the action 40 at 516.

[0056] If the ECU 12 determines at 506 to execute the situational alert 38, the ECU 12 determines at 520 whether the situational alert 38 is defined. If the situational alert 38 is not defined, the ECU 12 returns to monitoring the situational event 20. If the situational alert 38 is defined, the ECU 12 determines at 522 where the situational alert 38 is defined. For example, the ECU 12 can determine at 524 that the situational alert 38 is defined as an in-vehicle alert. Additionally or alternatively, the ECU 12 can determine at 526 that the situational alert 38 is defined as a user device alert. The ECU 12 then determines at 528 whether there is authorization from the user. If there is authorization from the user, the ECU 12 executes the action 40 at 530.

[0057] Refer again to Figures 1 to 6, the situational communication system 10 advantageously interconnects a plurality of external devices 200 with the vehicle 100 and / or the user device 300 via the situational communication feature unit 18. The situational communication feature unit 18 shares situational event data 22 with the external device 200 to assist the external device 200 in performing an action 40 based on the detected situational event 20. The external device 200 can actually utilize the telematics system 32 of the situational communication feature unit 18 to navigate various actions 40 and utilize the situational event data 22 that may otherwise be unavailable. In addition, the use of a short-range wired or wireless connection between the situational communication feature unit 18 and the external device 200 minimizes the energy consumption for providing the situational event data 22 and performing various associated actions 40. Therefore, the situational communication system 10 maximizes the performance and connectivity between the vehicle 100 and the associated external device 200.

[0058] Numerous embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of the present disclosure. Accordingly, other embodiments are within the scope of the appended claims.

[0059] The foregoing description has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements or features of a particular configuration are generally not limited to that particular configuration but, where applicable, are interchangeable and can be used in a selected configuration, even if not specifically shown or described. It can also vary in many ways. Such variations should not be regarded as a departure from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. A situational communication system for a vehicle, the situational communication system comprising: an external device comprising a communication receiver; as well as An electronic control unit (ECU) comprising data processing hardware and memory hardware for storing actions and action settings, the data processing hardware including a contextual communication feature having a telematics system configured to detect the external device and contextual events, the contextual communication feature configured to selectively issue a contextual alert based on the detected external device and in response to the contextual event.

2. The situational communication system according to claim 1, wherein: The action is associated with the external device, and the context communication feature is configured to perform the action based on context event data corresponding to the detected context event.

3. The situational communication system according to claim 1, wherein: The action settings stored in the memory hardware include automatic settings and manual settings, and each action is configured to have one of the automatic settings and the manual settings.

4. The situational communication system according to claim 3, wherein: The contextual communication feature is configured to automatically perform an action configured with the automatic setting in response to a detected contextual event.

5. The situational communication system according to claim 3, wherein: The contextual communication feature is configured to issue an action notification associated with an action configured with the manual setting.

6. The situational communication system according to claim 1, wherein: The telematics system includes a geo-application and a geo-fence, and the contextual communication feature is configured to detect the communication receiver of the external device using at least one of the geo-application and the geo-fence.

7. The situational communication system according to claim 1, wherein: The ECU is configured to directly access the external device to perform at least one of the actions in response to a detected contextual event.

8. The situational communication system according to claim 1, wherein: The telematics system is configured to detect the external device via the communication receiver, and the contextual communication feature is configured to perform at least one action associated with the detected external device using contextual event data corresponding to the contextual event.

9. The situational communication system according to claim 8, wherein: The contextual event data includes one or more of: time of day, location of the vehicle, direction of travel of the vehicle, and speed of the vehicle.

10. A vehicle comprising the situational communication system according to claim 1.

Images