Over-the-air update edges for vehicle content provision

The computing system synchronizes OTA content delivery with local infrastructure in controlled environments, addressing connectivity and state issues, ensuring reliable and efficient updates for vehicles by routing them to known network conditions, thereby improving performance and reducing rework.

WO2024227578A1PCT designated stage expired Publication Date: 2024-11-07MERCEDES BENZ GROUP AG
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/059841
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-04
Filing Date
2024-04-11
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Over-the-air (OTA) content delivery to vehicles faces reliability and efficiency issues due to inconsistent Mobile Network Operator (MNO) connectivity and limited bandwidth, as well as dependence on the vehicle's state and driver collaboration, leading to disjointed processes with remote OTA systems and local infrastructure.

Method used

A computing system that accesses vehicle identifiers and schedules to determine when a vehicle is in a controlled environment with known connectivity, allowing for synchronized content delivery through a local computing edge, enabling efficient software updates and media distribution by routing vehicles to designated locations for reliable downloads.

Benefits of technology

This approach enhances the reliability and efficiency of OTA content delivery by leveraging controlled environments for predictable network conditions, reducing computational rework and resource usage, and ensuring vehicles receive updates in a single session, thus improving vehicle performance and customer satisfaction.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024059841_07112024_PF_FP_ABST
    Figure EP2024059841_07112024_PF_FP_ABST
Patent Text Reader

Abstract

An example computing system may include processors configured to perform operations. The operations may cause the computing system to access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment. The computing system may determine, based on the vehicle identifier, that content is available for the vehicle. The computing system may output, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle. Based on the content, the computing system may determine a data payload for download to the vehicle while within the controlled environment. The computing system may initiate the output of: the data payload to a local computing infrastructure associated with the controlled environment and instructions to route the vehicle to the controlled environment.
Need to check novelty before this filing date? Find Prior Art

Description

OVER-THE-AIR UPDATE EDGES FORVEHICLE CONTENT PROVISIONRELATED APPLICATIONS

[0001] This patent application claims benefit of and priority to United States Provisional Patent Application No. 63 / 500,133 filed May 4, 2023, the contents of which are hereby incorporated herein by reference in their entirety.FIELD

[0002] The present disclosure relates generally to efficiently distributing content to vehicles from a centralized computing system. More particular, the present disclosure relates to intelligently distributing content to vehicles via a local computing edge that interfaces with the vehicles within a controlled environment, while preserving computational resources.BACKGROUND

[0003] Computing devices can be provided with information from remote computing sources. For example, over-the-air (OTA) updates include the process of wirelessly updating the software of a device, such as a smartphone, Internet of Things (loT) device, or vehicle. OTA updates allow manufacturers to push updates and patches to devices remotely. OTA updates are commonly used for fixing software bugs, improving device performance, adding new features, and addressing security vulnerabilities. OTA updates have become increasingly common in recent years as more devices are connected to the internet, making it easier for manufacturers to deliver updates quickly and efficiently.SUMMARY

[0004] Aspects and advantages of implementations of the present disclosure will be set forth in part in the following description, or may be learned from the description, or may be learned through practice of the implementations.

[0005] One example aspect of the present disclosure is directed to a computing system. The computing system includes a control circuit configured to: access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment including a location where the vehicle is in aknown state and has a known network connectivity; determine, based on the vehicle identifier, that content is available for the vehicle; initiate the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determine a data payload for download to the vehicle while the vehicle is within the controlled environment; initiate the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

[0006] In some implementations, the control circuit is further configured to: access user input data indicative of a response to the message indicating the content is available for the vehicle, wherein the user input data is based on user input, to the client computing device, from a user associated with the controlled environment.

[0007] In some implementations, the content includes a software update, and the user input data is indicative of an additional software update to be downloaded to the vehicle, and wherein the data payload includes the software update and the additional software update to be downloaded to the vehicle while the vehicle is in the controlled environment.

[0008] In some implementations, the user input data is indicative of a confirmation by the user of the content.

[0009] In some implementations, the control circuit is further configured to: initiate, for delivery to the client computing device associated with the controlled environment, the output of data indicating one or more actions for the user to facilitate the download of the data payload to the vehicle while the vehicle is within the controlled environment.

[0010] In some implementations, the data indicating the one or more actions for the user includes instructions to assist the user with one or more manual steps during download of the data payload to the vehicle.

[0011] In some implementations, the control circuit is further configured to: access data indicative of a status of the data payload; and initiate, for delivery to the client computing device associated with the controlled environment, the output of data indicating the status of the data payload.

[0012] In some implementations, the data payload includes one or more software updates, and wherein the status of the data payload is indicative of a progress in downloading each respective software update to the vehicle.

[0013] In some implementations, the computing system is configured to communicate with the client computing device via one or more APIs.

[0014] In some implementations, the control circuit is further configured to: determine, based on the time that the vehicle is estimated to be at the location, that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment rather than while the vehicle is within an uncontrolled environment where the state of the vehicle and the network connectivity of the vehicle is unknown or dynamically changes.

[0015] In some implementations, the control circuit is configured to determine that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment based on at least one of: (1) a priority of the content, (2) a size of the content, or (3) a type of the content.

[0016] In some implementations, the vehicle is travelling within an uncontrolled environment.

[0017] In some implementations, the controlled environment includes a microcell for the vehicle to download the data payload.

[0018] In some implementations, the control circuit is further configured to: access data indicative of a type of the controlled environment.

[0019] In some implementations, the type of controlled environment includes an automotive service location and wherein the user associated with the controlled environment is a technician at the automotive service location.

[0020] In some implementations, the content includes at least one of: (i) a software package, (ii) media content; or (iii) other digital content.

[0021] One example aspect of the present disclosure is directed to a computer-implemented method. The method includes: accessing data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment including a location where the vehicle is in a known state and has a known network connectivity; determining, based on the vehicle identifier, that content is available for the vehicle; initiating the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determining a data payload for download to the vehicle while the vehicle is within the controlled environment; initiating the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiating the output ofinstructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

[0022] In some implementations, the computer-implemented method further includes: accessing user input data indicative of a response to the message indicating the content is available for the vehicle, wherein the user input data is based on user input, to the client computing device, from a user associated with the controlled environment.

[0023] In some implementations, the computer-implemented method further includes: determining, based on the time that the vehicle is estimated to be at the location, that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment rather than while the vehicle is within an uncontrolled environment where the state of the vehicle and the network connectivity of the vehicle is unknown or dynamically changes.

[0024] In some implementations, one or more non-transitory computer-readable media that store instructions that are executable by a control circuit to: access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment including a location where the vehicle is in a known state and has a known network connectivity; determine, based on the vehicle identifier, that content is available for the vehicle; initiating the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determine a data payload for download to the vehicle while the vehicle is within the controlled environment; initiate the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

[0025] Other example aspects of the present disclosure are directed to other systems, methods, vehicles, apparatuses, tangible non-transitory computer-readable media, and devices for the technology described herein.

[0026] These and other features, aspects, and advantages of various implementations will become better understood with reference to the following description and appended claims. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate implementations of the present disclosure and, together with the description, serve to explain the related principles.BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Detailed discussion of implementations directed to one of ordinary skill in the art are set forth in the specification, which makes reference to the appended figures, in which:

[0028] FIG. 1 illustrates an example computing ecosystem according to an embodiment hereof.

[0029] FIGS. 2A-D illustrate diagrams of an example computing architecture for an onboard computing system of a vehicle according to an embodiment hereof.

[0030] FIG. 3 illustrates a diagram of an example computing platform that is remote from a vehicle according to an embodiment hereof.

[0031] FIG. 4 illustrates a diagram of a computing ecosystem for providing content for a vehicle according to an embodiment hereof.

[0032] FIG. 5 illustrates a diagram of an example content controller according to an embodiment hereof.

[0033] FIG. 6 illustrates a diagram of example computing ecosystem for providing content to a local computing edge according to an embodiment hereof.

[0034] FIG. 7 illustrates a diagram of an example dataflow for distributing content to vehicles according to an embodiment hereof.

[0035] FIGA. 8A-B illustrates a flowchart diagram of an example method according to an embodiment hereof.

[0036] FIG. 9 illustrates a diagram of an example computing ecosystem with computing components according to an embodiment hereof.DETAILED DESCRIPTION

[0037] Over-the-air (OTA) content delivery mechanisms can be used to reduce manual effort, cost, as well as to shorten the timeframes of delivery, etc. Also, using a centralized OTA mechanism such as a centralized, cloud-based computing platform allows for great insights into behavior of fleets, better analytics, etc.

[0038] However, certain technical hurdles are presented with this approach. For example, OTA content (e.g., software updates, media / digital content) may depend on Mobile Network Operator (MNO) connectivity and bandwidth; the former is often inconsistent and the latter is limited. This affects the reliability of content delivery as well as the velocity at which the contentcan be delivered with regard to an individual vehicle (e.g., due to the limited connection speed) and the fleet (e.g., due to limited bandwidth).

[0039] Moreover, OTA content may often depend on the specific state of the vehicle. For example, the vehicle may need to be driving while having MNO connectivity for the vehicle to download certain software updates (e.g., for battery state optimization). Additionally, or alternatively, a lot of software updates may require getting the vehicle to “safe state” (e.g., doors locked, ignition cycled, etc.). In some instances, OTA content may depend on the collaboration of the driver (e.g., confirming updates, etc.).

[0040] While the OTA process provides a lot of benefits, the process may be less reliable and more lengthy than a “legacy” attended update by a technician in a workshop. However, providing content to a vehicle by a technician may be inconsistent with the OTA process. For example, performing software updates by a technician in a workshop may be disruptive to the OTA process because those updates may happen “out-of-band” from the point of view of the central OTA computing system and often interfere with scheduled OTA updates. This also leads to a decreased customer satisfaction as well as computational inefficiencies and rework because the OTA process and workshop processes are disjointed.

[0041] An aspect of the present disclosure provides a computationally efficient process for providing OTA content to vehicles in a manner that synchronizes the processes of the remote OTA computing system and a local infrastructure (e.g., at a workshop). More particularly, the OTA computing system may access data indicative of a vehicle identifier (e.g., a VTN) and a time that the associated vehicle is estimated to be within a controlled environment (e.g., a location where the vehicle is in a known state and has a known network connectivity). This data may be accessed from a database that stores a schedule indicating when the vehicle will be within a controlled environment such as, for example, within a workshop.

[0042] The OTA computing system may determine, based on the vehicle identifier, that content is available for the vehicle. For instance, the OTA computing system may access a vehicle service hosted by an update controller. The vehicle service may be associated with a software package resolver that is configured to maintain, or otherwise access, a data structure that indicates if there are any software updates pending for the vehicle based on the vehicle identifier.

[0043] In the event that content is available for the vehicle, the OTA computing system may output a message to a client computing device associated with the controlled environment. Themessage may indicate the content (e.g., a software update) is available for the vehicle. For example, the message may be sent to a tablet of a technician at the workshop where the vehicle is to receive maintenance / service. The technician may confirm, via the tablet, that the software update should be provided to the vehicle by providing user input confirming the update.

[0044] Based on the content that is available for the vehicle, the OTA computing system may determine a data payload for download to the vehicle while the vehicle is within the workshop. The data payload may include, for example, the software code associated with the software update as well as any associated configurations and instructions for downloading. The OTA computing system may initiate the output of the data payload to a local computing infrastructure such as, for example, a computing system located at the premises of the workshop.

[0045] The OTA computing system may initiate the output of instructions for routing the vehicle to the controlled environment. For example, the OTA computing system may transmit a message to a navigation service that is configured to provide navigation to the vehicle. The message may be indicative of the workshop. The navigation service may provide routing instructions to the vehicle to route the vehicle (e.g., it’s driver) to the address of the workshop.

[0046] While within the controlled environment of the workshop, the location of the vehicle and its network connectivity is known because the vehicle can remain static at the workshop and the network connectivity of the workshop remains relatively consistent. This is in contrast to an uncontrolled environment wherein the vehicle’s location and network connectivity are dynamic, such as when the vehicle is travelling on a highway or within a city. In the event the vehicle is indeed travelling within an uncontrolled environment, but will be within a controlled environment within a reasonable timeframe, the OTA computing system may determine that it would be more effective to deliver the content (e.g., software update) to the vehicle while the vehicle is within the controlled environment (e.g., workshop) via its local computing infrastructure.

[0047] In some implementations, the mobile device of the technician may be provided with information regarding the data payload to be downloaded to the vehicle. For instance, the technician’s tablet may receive a message that indicates instructions that assist the technician with manual steps for facilitating the download to the vehicle. This may include steps for connecting the vehicle to a microcell for the vehicle to download the data payload via the local computing infrastructure, steps for progress the download via confirmation inputs to the head unit display, etc. In another example, the message received by the technician’s tablet mayindicate a status of the data payload. This may allow the technician to monitor the progress of the download until the download is completed (e.g., and the vehicle’s software is updated) within the controlled environment.

[0048] While the above example is described with respect to providing content at a workshop / service depot, the technology of the present disclosure is not limited to such locations. As will be further herein, the systems and methods for intelligently distributing content via a local OTA computing edge may be implemented with production facilities, factories, charging stations, etc.

[0049] The technology of the present disclosure can provide a number of technical effects and computing improvements. For instance, by aligning the provision of content to a vehicle by the OTA computing system and the local computing edge (while alerting a local user), the systems and methods described herein increase the reliability of the OTA process and reduce potential conflicts between the OTA computing system and the local space. This can be accomplished by leveraging controlled environments including, for example, certain locales (e.g., workshops) where it is easier to get the vehicle in a predictable state. Rather than, for example, relying on uncontrolled environments wherein the vehicle state and connectivity is unknown and relatively more dynamic. By introducing local computing infrastructure into the controlled environment, the technology of the present disclosure can extend the OTA mechanism to the particular environment and distribute content for download via a single orchestration mechanism, as opposed to utilizing a less reliable uncontrolled environment. In this manner, the technology described herein increases the fidelity of downloading content to a vehicle and avoids computational rework by improving the vehicle’s ability to download the content in a single session.

[0050] By intelligently caching content for a vehicle to download via a local computing edge according the technology described herein, the computing ecosystem (e.g., including the onboard vehicle computer, remote cloud platform, etc.) can avoid other software distribution techniques that include high computational costs. For example, the systems and methods of the present disclosure avoid incurring high volume of data transfer caused by attempting to fully synchronize all available content and distribute the packages in an uncontrolled environment, where avoidable. This saves time, bandwidth, processing, and memory resources by selectively distributing certain content to vehicles that will be available at the local, controlled environments. This also reduces the need for disseminating physical media (e.g., DVDs) to localpremises. As such, the computing ecosystem can avoid costly processing as well as the read / write functions typically needed to create and utilize such media.

[0051] The technology of the present disclosure can improve computing technology. For instance, the systems and methods described herein improve the performance of a computing system that is configured to distribute content for vehicles. For instance, the computing system may access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment (e.g., where the vehicle is in a known state and has a known network connectivity). The computing system may determine, based on the vehicle identifier, that content (e.g., a software update, media content) is available for the vehicle. The computing system may output, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle. Based on the content, the computing system may determine a data payload for download to the vehicle while the vehicle is within the controlled environment. The computing system may initiate the output of the data payload to a local computing infrastructure associated with the controlled environment as well as initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

[0052] By leveraging the local computing infrastructure of the controlled environment, the computing system may more efficiently deliver the content to a vehicle at a time in which the vehicle is not being driven. This can help ensure that an OTA software package is downloaded to the vehicle in a single session rather than multiple sessions which arise from variances in network connectivity when the vehicle is being driven to a variety of locations. As such, the technology of the present disclosure helps avoid the resource intensive computational re-work (e.g., stopping and re-starting downloads) introduced by interruptions arising from bandwidth and connectivity problems in uncontrolled environments. This leads to a more computationally efficient implementation of content such as vehicle software updates. Ultimately, this can improve the performance of the vehicle itself by helping to keep the vehicle’s onboard computer up-to-date thereby improving the reliability of the vehicle’s onboard computing functions.

[0053] Reference now will be made in detail to embodiments, one or more examples of which are illustrated in the drawings. Each example is provided by way of explanation of the embodiments, not limitation of the present disclosure. In fact, it will be apparent to those skilled in the art that various modifications and variations may be made to the embodiments withoutdeparting from the scope or spirit of the present disclosure. For instance, features illustrated or described as part of one embodiment may be used with another embodiment to yield a still further embodiment. Thus, it is intended that aspects of the present disclosure cover such modifications and variations.

[0054] The technology of the present disclosure may include the collection of data associated with a user in the event that the user expressly authorizes such collection. Such authorization may be provided by the user via explicit user input to a user interface in response to a prompt that expressly requests such authorization. Collected data may be anonymized, pseudonymized, encrypted, noised, securely stored, or otherwise protected. A user may opt out of such data collection at any time.

[0055] The following description describes over-the-air (OTA) content related technology within the context of vehicles for example purposes. The technology described herein may be utilized in other Internet of Things (loT) contexts and environments. For example, computing devices may be used instead of vehicles and vehicle computing systems.

[0056] FIG. 1 illustrates an example computing ecosystem 100 according to an embodiment hereof. The ecosystem 100 may include a vehicle 105, a remote computing platform 110 (also referred to herein as computing platform 110), and a user device 115 associated with a user 120. The user 120 may be a driver of the vehicle. In some implementations, the user 120 may be a passenger of the vehicle. In some implementations, the computing ecosystem 100 may include a third party (3P) computing platform 125, as further described herein. The vehicle 105 may include a vehicle computing system 200 located onboard the vehicle 105. The computing platform 110, the user device 115, the third party computing platform 125, and / or the vehicle computing system 200 may be configured to communicate with one another via one or more networks 130.

[0057] The systems / devices of ecosystem 100 may communicate using one or more application programming interfaces (APIs). This may include external facing APIs to communicate data from one system / device to another. The external facing APIs may allow the systems / devices to establish secure communication channels via secure access channels over the networks 130 through any number of methods, such as web-based forms, programmatic access via RESTful APIs, Simple Object Access Protocol (SOAP), remote procedure call (RPC), scripting access, etc.

[0058] The computing platform 110 may include a computing system that is remote from the vehicle 105. In an embodiment, the computing platform 110 may include a cloud -based server system. The computing platform 110 may be associated with (e.g., operated by) an entity. For example, the remote computing platform 110 may be associated with an OEM that is responsible for the make and model of the vehicle 105. In another example, the remote computing platform 110 may be associated with a service entity contracted by the OEM to operate a cloud-based server system that provides computing services to the vehicle 105.

[0059] The computing platform 110 may include one or more back-end services for supporting the vehicle 105. The services may include, for example, tele-assist services, navigation / routing services, performance monitoring services, content services, etc. The computing platform 110 may host or otherwise include one or more APIs for communicating data to / from a computing system 130 of the vehicle 105 or the user device 115.

[0060] The computing platform 110 may include one or more computing devices. For instance, the computing platform 110 may include a control circuit and a non-transitory computer-readable medium (e.g., memory). A control circuit may be one or more processors. The control circuit of the computing platform 110 may be configured to perform the various operations and functions described herein. Further description of the computing hardware and components of computing platform 110 is provided herein with reference to other figures.

[0061] The user device 115 may include a computing device owned or otherwise accessible to the user 120. For instance, the user device 115 may include a phone, laptop, tablet, wearable device (e.g., smart watch, smart glasses, headphones), personal digital assistant, gaming system, personal desktop devices, other hand-held devices, or other types of mobile or non-mobile user devices. As further described herein, the user device 115 may include one or more input components such as buttons, a touch screen, a joystick or other cursor control, a stylus, a microphone, a camera or other imaging device, a motion sensor, etc. The user device 115 may include one or more output components such as a display device (e.g., display screen), a speaker, etc. In an embodiment, the user device 115 may include a component such as, for example, a touchscreen, configured to perform input and output functionality to receive user input and present information for the user 120. The user device 115 may execute one or more instructions to run an instance of a software application and present user interfaces associated therewith, as further described herein. In an embodiment, the launch of a software application may initiate a user-network session with the computing platform 110.

[0062] The third-party computing platform 125 may include a computing system that is remote from the vehicle 105, remote computing platform 110, and user device 115. In an embodiment, the third-party computing platform 125 may include a cloud -based server system. The term “third-party entity” may be used to refer to an entity that is different than the entity associated with the remote computing platform 110. For example, as described herein, the remote computing platform 110 may be associated with an OEM that is responsible for the make and model of the vehicle 105. The third-party computing platform 125 may be associated with a supplier of the OEM, a maintenance provider, a mapping service provider, an emergency provider, or other types of entities. In another example, the third-party computing platform 125 may be associated with an entity that owns, operates, manages, etc. a software application that is available to or downloaded on the vehicle computing system 200.

[0063] The third-party computing platform 125 may include one or more back-end services provided by a third-party entity. The third-party computing platform 125 may provide services that are accessible by the other systems and devices of the ecosystem 100. The services may include, for example, mapping services, routing services, search engine functionality, maintenance services, entertainment services (e.g., music, video, images, gaming, graphics), emergency services (e.g., roadside assistance, 911 support), or other types of services. The third- party computing platform 125 may host or otherwise include one or more APIs for communicating data to / from the third-party computing system 125 to other systems / devices of the ecosystem 100.

[0064] The networks 130 may be any type of network or combination of networks that allows for communication between devices. In some implementations, the networks 130 may include one or more of a local area network, wide area network, the Internet, secure network, cellular network, mesh network, peer-to-peer communication link or some combination thereof and may include any number of wired or wireless links. Communication over the networks 130 may be accomplished, for instance, via a network interface using any type of protocol, protection scheme, encoding, format, packaging, etc. In an embodiment, communication between the vehicle computing system 200 and the user device 115 may be facilitated by near field or short range communication techniques (e.g., Bluetooth low energy protocol, radio frequency signaling, NFC protocol).

[0065] The vehicle 105 may be a vehicle that is operable by the user 120. In an embodiment, the vehicle 105 may be an automobile or another type of ground -based vehicle that is manuallydriven by the user 120. For example, the vehicle 105 may be a Mercedes-Benz® car or van. In some implementations, the vehicle 105 may be an aerial vehicle (e.g., a personal airplane) or a water-based vehicle (e.g., a boat). The vehicle 105 may include operator-assistance functionality such as cruise control, advanced driver assistance systems, etc. In some implementations, the vehicle 105 may be a fully or semi-autonomous vehicle.

[0066] The vehicle 105 may include a powertrain and one or more power sources. The powertrain may include a motor (e.g., an internal combustion engine, electric motor, or hybrid thereof), e-motor (e.g., electric motor), transmission (e.g., automatic, manual, continuously variable), driveshaft, axles, differential, e-components, gear, etc. The power sources may include one or more types of power sources. For example, the vehicle 105 may be a fully electric vehicle (EV) that is capable of operating a powertrain of the vehicle 105 (e.g., for propulsion) and the vehicle’s onboard functions using electric batteries. In an embodiment, the vehicle 105 may use combustible fuel. In an embodiment, the vehicle 105 may include hybrid power sources such as, for example, a combination of combustible fuel and electricity.

[0067] The vehicle 105 may include a vehicle interior. The vehicle interior may include the area inside of the body of the vehicle 105 including, for example, a cabin for users of the vehicle 105. The interior of the vehicle 105 may include seats for the users, a steering mechanism, accelerator interface, braking interface, etc. The interior of the vehicle 105 may include a display device such as a display screen associated with an infotainment system, as further described with respect to FIG 3.

[0068] The vehicle 105 may include a vehicle exterior. The vehicle exterior may include the outer surface of the vehicle 105. The vehicle exterior may include one or more lighting elements (e.g., headlights, brake lights, accent lights). The vehicle 105 may include one or more doors for accessing the vehicle interior by, for example, manipulating a door handle of the vehicle exterior. The vehicle 105 may include one or more windows, including a windshield, door windows, passenger windows, rear windows, sunroof, etc.

[0069] The systems and components of the vehicle 105 may be configured to communicate via a communication channel. The communication channel may include one or more data buses (e.g., controller area network (CAN)), on-board diagnostics connector (e.g., OBD-II), or a combination of wired or wireless communication links. The onboard systems may send or receive data, messages, signals, etc. amongst one another via the communication channel. The vehicle may also be configured to reference one or more protocols used for transmitting data(e.g., software updates) over a charging cable, wirelessly, via short-range communication (e.g., NFC, Bluetooth®), etc.

[0070] In an embodiment, the communication channel may include a direct connection, such as a connection provided via a dedicated wired communication interface, such as a RS-232 interface, a universal serial bus (USB) interface, or via a local computer bus, such as a peripheral component interconnect (PCI) bus. In an embodiment, the communication channel may be provided via a network. The network may be any type or form of network, such as a personal area network (PAN), a local-area network (LAN), Intranet, a metropolitan area network (MAN), a wide area network (WAN), or the Internet. The network may utilize different techniques and layers or stacks of protocols, including, e.g., the Ethernet protocol, the internet protocol suite (TCP / IP), the ATM (Asynchronous Transfer Mode) technique, the SONET (Synchronous Optical Networking) protocol, or the SDH (Synchronous Digital Hierarchy) protocol.

[0071] In an embodiment, the systems / de vices of the vehicle 105 may communicate via an intermediate storage device, or more generally an intermediate non-transitory computer-readable medium. For example, the non-transitory computer-readable medium 140, which may be external to the computing system 130, may act as an external buffer or repository for storing information. In such an example, the computing system 130 may retrieve or otherwise receive the information from the non-transitory computer-readable medium 140.

[0072] Certain routine and conventional components of vehicle 105 (e.g., an engine) are not illustrated and / or discussed herein for the purpose of brevity. One of ordinary skill in the art will understand the operation of conventional vehicle components in vehicle 105.

[0073] The vehicle 105 may include a vehicle computing system 200. As described herein, the vehicle computing system 200 that is onboard the vehicle 105. For example, the computing devices and components of the vehicle computing system 200 may be housed, located, or otherwise included on or within the vehicle 105. The vehicle computing system 200 may be configured to execute the computing functions and operations of the vehicle 105.

[0074] FIG. 2A illustrates an overview of an operating system of the vehicle computing system 200. The operating system may be a layered operating system. The vehicle computing system 200 may include a hardware layer 205 and a software layer 210. The hardware and software layers 205, 210 may include sub-layers. In some implementations, the operating system of the vehicle computing system 200 may include other layers (e.g., above, below, or in betweenthose shown in FIG. 2A). In an example, the hardware layer 205 and the software layer 210 can be standardized base layers of the vehicle’s operating system.

[0075] FIG. 2B illustrates a diagram of the hardware layer 205 of the vehicle computing system 200. In the layered operating system of the vehicle computing system 200, the hardware layer 205 can reside between the physical computing hardware 215 onboard the vehicle 105 and the software (e.g., of software layer 210) that runs onboard the vehicle 105.

[0076] The hardware layer 205 may be an abstraction layer including computing code that allows for communication between the software and the computing hardware 215 in the vehicle computing system 200. For example, the hardware layer 205 may include interfaces and calls that allow the vehicle computing system 200 to generate a hardware-dependent instruction to the computing hardware 215 (e.g., processors, memories, etc.) of the vehicle 105.

[0077] The hardware layer 205 may be configured to help coordinate the hardware resources. The architecture of the hardware layer 205 may be serviced oriented. The services may help provide the computing capabilities of the vehicle computing system 105. For instance, the hardware layer 205 may include the domain computers 220 of the vehicle 105, which may host various functionality of the vehicle 105 such as the vehicle’s intelligent functionality. The specification of each domain computer may be tailored to the functions and the performance requirements where the services are abstracted to the domain computers. By way of example, this permits certain processing resources (e.g., graphical processing units) to support the functionality of a central in-vehicle infotainment computer for rendering graphics across one or more display devices for navigation, games, etc. or to support an intelligent automated driving computer to achieve certain industry assurances.

[0078] The hardware layer 205 may be configured to include a connectivity module 225 for the vehicle computing system 200. The connectivity module may include code / instructions for interfacing with the communications hardware of the vehicle 105. This can include, for example, interfacing with a communications controller, receiver, transceiver, transmitter, port, conductors, or other hardware for communicating data / information. The connectivity module 225 may allow the vehicle computing system 200 to communicate with other computing systems that are remote from the vehicle 105 including, for example, remote computing platform 110 (e.g., an OEM cloud platform).

[0079] The architecture design of the hardware layer 205 may be configured for interfacing with the computing hardware 215 for one or more vehicle control units 225. The vehicle controlunits 225 may be configured for controlling various functions of the vehicle 105. This may include, for example, a central exterior and interior controller (CEIC), a charging controller, or other controllers as further described herein.

[0080] The software layer 205 may be configured to provide software operations for executing various types of functionality and applications of the vehicle 105. FIG. 2C illustrates a diagram of the software layer 210 of the vehicle computing system 200. The architecture of the software layer 210 may be service oriented and may be configured to provide software for various functions of the vehicle computing system 200. To do so, the software layer 210 may include a plurality of sublayers 235A-E. For instance, the software layer 210 may include a first sublayer 235A including firmware (e.g., audio firmware) and a hypervisor, a second sublayer 235B including operating system components (e.g., open-source components), and a third sublayer 235C including middleware (e.g., for flexible integration with applications developed by an associated entity or third-party entity).

[0081] The vehicle computing system 200 may include an application layer 240. The application layer 240 may allow for integration with one or more software applications 245 that are downloadable or otherwise accessible by the vehicle 105. The application layer 240 may be configured, for example, using container interfaces to integrate with applications developed by a variety of different entities.

[0082] The layered operating system and the vehicle’s onboard computing resources may allow the vehicle computing system 200 to collect and communicate data as well as operate the systems implemented onboard the vehicle 105. FIG. 2D illustrates a block diagram of example systems and data of the vehicle 105.

[0083] The vehicle 105 may include one or more sensor systems 305. A sensor system may include or otherwise be in communication with a sensor of the vehicle 105 and a module for processing sensor data 310 associated with the sensor configured to acquire the sensor data 305. This may include sensor data 310 associated with the surrounding environment of the vehicle 105, sensor data associated with the interior of the vehicle 105, or sensor data associated with a particular vehicle function. The sensor data 310 may be indicative of conditions observed in the interior of the vehicle, exterior of the vehicle, or in the surrounding environment. For instance, the sensor data 305 may include image data, inside / outside temperature data, weather data, data indicative of a position of a user / object within the vehicle 105, weight data, motion / gesture data, audio data, or other types of data. The sensors may include one or more: cameras (e.g., visiblespectrum cameras, infrared cameras), motion sensors, audio sensors (e.g., microphones), weight sensors (e.g., for a vehicle a seat), temperature sensors, humidity sensors, Light Detection and Ranging (LIDAR) systems, Radio Detection and Ranging (RADAR) systems, or other types of sensors. The vehicle 105 may include other sensors configured to acquire data associated with the vehicle 105. For example, the vehicle 105 may include inertial measurement units, wheel odometry devices, or other sensors.

[0084] The vehicle 105 may include a positioning system 315. The positioning system 315 may be configured to generate location data 320 (also referred to as position data) indicative of a location (also referred to as a position) of the vehicle 105. For example, the positioning system 315 may determine location by using one or more of inertial sensors (e.g., inertial measurement units, etc.), a satellite positioning system, based on IP address, by using triangulation and / or proximity to network access points or other network components (e.g., cellular towers, Wi-Fi access points, etc.), or other suitable techniques. The positioning system 315 may determine a current location of the vehicle 105. The location may be expressed as a set of coordinates (e.g., latitude, longitude), an address, a semantic location (e.g., “at work”), etc.

[0085] In an embodiment, the positioning system 315 may be configured to localize the vehicle 105 within its environment. For example, the vehicle 105 may access map data that provides detailed information about the surrounding environment of the vehicle 105. The map data may provide information regarding: the identity and location of different roadways, road segments, buildings, or other items; the location and directions of traffic lanes (e.g., the location and direction of a parking lane, a turning lane, a bicycle lane, or other lanes within a particular roadway); traffic control data (e.g., the location, timing, or instructions of signage (e.g., stop signs, yield signs), traffic lights (e.g., stop lights), or other traffic signals or control devices / markings (e.g., cross walks)); or any other data. The positioning system 315 may localize the vehicle 105 within the environment (e.g., across multiple axes) based on the map data. For example, the positioning system 155 may process certain sensor data 310 (e.g., LIDAR data, camera data, etc.) to match it to a map of the surrounding environment to get an understanding of the vehicle’s position within that environment. The determined position of the vehicle 105 may be used by various systems of the vehicle computing system 200 or another computing system (e.g., the remote computing platform 110, the third-party computing platform 125, the user device 115).

[0086] The vehicle 105 may include a communications system 325 configured to allow the vehicle 105 (and its vehicle computing system 200) to communicate with other computing devices. The vehicle computing system 200 may use the communications system 325 to communicate with the remote computing platform 110 or one or more other remote computing devices over a network 130 (e.g., via one or more wireless signal connections). For example, the vehicle computing system 200 may utilize the communications system 325 to receive platform data 330 from the computing platform 110. This may include, for example, an over-the-air (OTA) software update for the operating system of the vehicle computing system 200.Additionally, or alternatively, the vehicle computing system 200 may utilize the communications unit 325 to send vehicle data 335 to the computing platform 110. The vehicle data 335 may include any data acquired onboard the vehicle including, for example, sensor data 310, location data 320, diagnostic data, user input data, data indicative of current software versions or currently running applications, occupancy data, data associated with the user 120 of the vehicle 105, or other types of data obtained (e.g., acquired, accessed, generated, downloaded, etc.) by the vehicle computing system 200.

[0087] In some implementations, the communications system 325 may allow communication among one or more of the systems on-board the vehicle 105.

[0088] In an embodiment, the communications unit 325 may be configured to allow the vehicle 105 to communicate with or otherwise receive data from the user device 115 (shown in FIG. 1). The communications unit 325 may utilize various communication technologies such as, for example, Bluetooth low energy protocol, radio frequency signaling, or other short range or near filed communication technologies. The communications unit 325 may include any suitable components for interfacing with one or more networks, including, for example, transmitters, receivers, ports, controllers, antennas, or other suitable components that may help facilitate communication.

[0089] The vehicle 105 may include one or more human-machine interfaces (HMIs) 340. The human-machine interfaces 340 may include a display device, as described herein. The display device (e.g., touchscreen) may be viewable by a user of the vehicle 105 (e.g., user 120) that is located in the front of the vehicle 105 (e.g., driver’s seat, front passenger seat). Additionally, or alternatively, a display device (e.g., rear unit) may be viewable by a user that is located in the rear of the vehicle 105 (e.g., back passenger seats). The human-machine interfaces 340 may present content 335 via a user interface for display to a user 120.

[0090] The vehicle 105 may include a plurality of vehicle functions 350A-C. A vehicle function 350A-C may be a functionality that the vehicle 105 is configured to perform based on a detected input. The vehicle functions 350A-C may include one or more: (i) vehicle comfort functions; (ii) vehicle staging functions; (iii) vehicle climate functions; (vi) vehicle navigation functions; (v) drive style functions; (v) vehicle parking functions; or (vi) vehicle entertainment functions. The user 120 may interact with a vehicle function 250A-C through user input (e.g., to an adjustable input device, UI element) that specifies a setting of the vehicle function 250A-C selected by the user.

[0091] Each vehicle function may include a controller 355A-C associated with that particular vehicle function 355A-C. The controller 355A-C for a particular vehicle function may include control circuitry configured to operate its associated vehicle function 355A-C. For example, a controller may include circuitry configured to turn the seat heating function on, to turn the seat heating function off, set a particular temperature or temperature level, etc.

[0092] In an embodiment, a controller 355A-C for a particular vehicle function may include or otherwise be associated with a sensor that captures data indicative of the vehicle function being turned on or off, a setting of the vehicle function, etc. For example, a sensor may be an audio sensor or a motion sensor. The audio sensor may be a microphone configured to capture audio input from the user 120. For example, the user 120 may provide a voice command to activate the radio function of the vehicle 105 and request a particular station. The motion sensor may be a visual sensor (e.g., camera), infrared, RADAR, etc. configured to capture a gesture input from the user 120. For example, the user 120 may provide a hand gesture motion to adjust a temperature function of the vehicle 105 to lower the temperature of the vehicle interior.

[0093] The controllers 355A-C may be configured to send signals to another onboard system. The signals may encode data associated with a respective vehicle function. The encoded data may indicate, for example, a function setting, timing, etc. In an example, such data may be used to generate content for presentation via the display device 345 (e.g., showing a current setting). Additionally, or alternatively, such data can be included in vehicle data 335 and transmitted to the computing platform 110.

[0094] FIG. 3 illustrates a diagram of computing platform 110, which is remote from a vehicle according to an embodiment hereof. As described herein, the computing platform 110 may include a cloud-based computing platform. The computing platform 110 may be implemented on one or more servers and include, or otherwise have access to, one or moredatabases. In an example, the computing platform 110 may be implemented using different servers based on geographic region.

[0095] In some implementations, the computing platform 110 may include layered infrastructure that includes a plurality of layers. For instance, the computing platform 110 may include a cloud-based layer associated with functions such as security, automation, monitoring, and resource management. The computing platform 110 may include a cloud application platform layer associated with functions such as charging station functions, live traffic, vehicle functions, vehicle-sharing functions, etc. The computing platform 110 may include applications and services that are built on these layers.

[0096] The computing platform 110 may be a modular connected service platform that includes a plurality of services that are available to the vehicle 105. In an example, the computing platform 110 may include a container-based micro-services mesh platform. The services can be represented or implemented as systems within the computing platform 110. The computing platform 110 may also include functions relating to simulation of its components, services, and subsystems. As further described herein, this may be accomplished through the use of a test computing system that is a part of (or at least in communication with) the computing platform 110.

[0097] The computing platform 110 may include a user system 405. The user system 405 may create, store, manage, or access user profile data 410. The user profile data 410 may include a plurality of user profiles, each associated with a respective user 120. A user profile may indicate various information about a respective user 120 including the user’s preferences (e.g., for music, comfort settings), frequented / past destinations, past routes, etc. The user profiles may be stored in a secure database. In some implementations, when a user 120 enters the vehicle 120, the user’s key (or user device) may provide a signal with a user or key identifier to the vehicle 105. The vehicle 105 may transmit data indicative of the identifier (e.g., via its communications system 325) to the computing platform 110. The computing platform 110 may look-up the user profile of the user 120 based on the identifier and transmit user profile data 410 to the vehicle computing system 200 of the vehicle 105. The vehicle computing system 200 may utilize the user profile data 410 to implement preferences of the user 120, present past destination locations, etc. The user profile data 410 may be updated based on information periodically provided by the vehicle 105. In some implementations, the user profile data 410 may be provided to the user device 120.

[0098] The computing platform 110 may include a remote assistance system 415. The remote assistance system 415 may provide assistance to the vehicle 105. This can include providing information to the vehicle 105 to assist with charging (e.g., charging locations recommendations), remotely controlling the vehicle (e.g., for AV assistance), roadside assistance (e.g., for collisions, flat tires), etc. The remote assistance system 415 may obtain assistance data 420 to provide its core functions. The assistance data 420 may include information that may be helpful for the remote assistance system 415 to assist the vehicle 105. This may include information related to the vehicle’s current state, an occupant’s current state, the vehicle’s location, the vehicle’s route, charge / fuel level, incident data, etc. In some implementations, the assistance data 420 may include the vehicle data 335.

[0099] The remote assistance system 415 may transmit data or command signals to provide assistance to the vehicle 105. This may include providing data indicative of relevant charging locations, remote control commands to move the vehicle, connect to an emergency provider, etc.

[0100] The computing platform 110 may include a security system 425. The security system 425 can be associated with one or more security-related functions for accessing the computing platform 1110 or the vehicle 105. For instance, the security system 425 can process security data 430 for identifying digital keys, data encryption, data decryption, etc. for accessing the services / systems of the computing platform 110. Additionally, or alternatively, the security system 425 can store security data 430 associated with the vehicle 105. A user 120 can request access to the vehicle 105 (e.g., via the user device 115). In the event the request includes a digital key for the vehicle 105 as indicated in the security data 430, the security system 425 can provide a signal to lock (or unlock) the vehicle 105.

[0101] The computing platform 110 may include a navigation system 435 that provides a back-end routing and navigation service for the vehicle 105. The navigation system 435 may provide map data 440 to the vehicle 105. The map data 440 may be utilized by the positioning system 315 of the vehicle 105 to determine a location of the vehicle 105, a point of interest, etc. The navigation system 435 may also provide routes to destinations requested by the vehicle 105 (e.g., via user input to the vehicle’s head unit). The routes can be provided as a portion of the map data 440 or as separate routing data. Data provided by the navigation system 435 can be presented as content on the display device 345 of the vehicle 105.

[0102] The computing platform 110 may include an entertainment system 445. The entertainment system 445 may access one or more databases for entertainment data 450 for auser 120 of the vehicle 105. In some implementations, the entertainment system 445 may access entertainment data 450 from another computing system (e.g., via an API) associated with a third- party service provider of entertainment content. The entertainment data 450 may include media content such as music, videos, gaming data, etc. The vehicle 105 may output the entertainment data 450 via one or more output devices of the vehicle 105 (e.g., display device, speaker, etc.).

[0103] The computing platform 110 may include a vehicle content system 455 that is configured to provide the vehicle 105 with content 460. The content 460 may include, for example, software packages, media content, or other digital content. The software packages may include new software to be downloaded to a vehicle or software updates for a vehicle (e.g., a new version of the software running on the vehicle). The media content may include images, graphics, music, photographs, video, advertisements, streaming content, podcasts, blogs, online forums, or other audio / visual / interactive content. Other digital content may include any other content, for the vehicle, that exists in the form of digital data.

[0104] The vehicle content system 455 can include or otherwise communicate with one or more back-end services for providing content 460 to vehicles. For example, the vehicle content system 455 (or a service thereof) may maintain or otherwise access a data structure (e.g., list, table) that indicates the current software or versions thereof etc. downloaded to a particular vehicle. The vehicle content system 455 (or a service thereof) may also maintain a data structure indicating content (e.g., software packages / versions) that is to be downloaded by the particular vehicle. In some implementations, the vehicle computing system 200 or computing platform 110 may maintain a data structure that indicates the computing hardware, charging hardware, or other hardware resources onboard a particular vehicle. These data structures can be organized by vehicle identifier (e.g., VIN) such that the computing platform 110 can perform a look-up function, based on the vehicle identifier, to determine the associated content for a particular vehicle.

[0105] When the vehicle 105 is connected to the computing platform 110 and is available to download its content, the vehicle 105 can request content such as, for example, a software update from the computing platform. The computing platform 110 can provide the vehicle 105 content 460 as over-the-air (OTA) content (also referred to as “OTA content”) via a network 130. The OTA content may, for example, include new versions of software currently downloaded to the vehicle, new software applications to be downloaded to the vehicle, media content, or other digital content. 1

[0106] FIG. 4 illustrates a diagram of a computing ecosystem for providing content for a vehicle 105 according to an embodiment hereof. FIG. 4 shows a portion of computing platform 110 such as, for example, the vehicle content system 455. To help orchestrate the distribution of content 460 (e.g., OTA content) to vehicles, the computing platform 110 (e.g., the vehicle content system 455) may include a remote update controller system 500. The remote update controller system 500 is also referred to herein as the update controller 500. The update controller 500 may be configured to function as the orchestrator of OTA content as well as the point of contact for the vehicle 105 when it obtains content from the computing platform 110.

[0107] The update controller 500 may include and communicate with various systems / components to coordinate OTA content. FIG. 5 illustrates a diagram of update controller 500 as well as other systems that the update controller 500 may communicate with to orchestrate the distribution of OTA content.

[0108] The update controller 500 may be implemented on cloud computing infrastructure 505. This may include the infrastructure of the computing platform 110. The cloud computing infrastructure 505 may include the underlying framework and components that enable the delivery of cloud computing services over a network (e.g., the internet). The cloud computing infrastructure 505 may be provided by a cloud computing service provider. The cloud computing service provider may allow entities to access computing resources on-demand, adjust / consume resources as needed, etc. The cloud computing infrastructure 505 may provide the foundation for deploying and running a variety of cloud-based services, including software-as-a-service (SaaS), platform-as-a-service (PaaS), and infrastructure-as-a-service (laaS).

[0109] The cloud computing infrastructure 505 may include hardware, software, networking, and storage resources to support cloud-based applications, data storage, and processing. For instance, the cloud computing infrastructure 505 may include one or more servers. The servers may include physical or virtual machines that host and run applications, store data, and perform computational tasks in the cloud. The servers may be distributed across multiple data centers. The cloud computing infrastructure 505 may be managed and controlled through software platforms that provide functionalities such as resource provisioning, monitoring, security, and automation.

[0110] The cloud computing infrastructure 505 may include storage and networking resources. For example, the cloud computing infrastructure 505 may provide various types of storage options, such as object storage, file storage, block storage, etc. These storage resourcesmay be accessible over a network and allow entities to store and retrieve data. The cloud computing infrastructure 505 may include networking components, such as routers, switches, and load balancers, that enable communication between different components of the cloud system. Network connectivity can ensure data transmission and accessibility across distributed servers and data centers.

[0111] The cloud computing infrastructure 505 may incorporate various security measures to protect data, applications, and infrastructure from unauthorized access, data breaches, and other threats. This includes encryption, firewalls, access controls, and security monitoring systems.

[0112] The cloud computing infrastructure 505 may utilize virtualization technology. The virtualization technology can allow for the creation of virtual instances of servers, operating systems, and other resources. This can help provide efficient resource allocation, scalability, and isolation of different cloud tenants (users or entities) on shared physical infrastructure.

[0113] The update controller 500 may communicate with a number of services and systems to manage the distribution of OTA updates. For instance, the update controller 500 may be configured to communicate with the vehicle computing system 200 (not shown in FIG. 5) of vehicle 105. The update controller 500 may receive a request (or other type of communication) generated by the vehicle computing system 500 indicating that the vehicle 105 is available for content 515. In an example, the vehicle 105 may be considered available for the content 515 in the event that the vehicle 105 has the network connectivity to receive a package / payload associated with the content 515 or sufficient computing resources (e.g., processing, memory, power, etc.) needed to download and configure the content 515 on the vehicle 105.

[0114] The update controller 500 may communicate with one or more consumer systems 520. The consumer systems 520 may be computing systems configured to create a rule 522 for distributing the content 515.

[0115] By way of example, the rule 522 may be associated with a campaign for updating certain software versions on a group of vehicles (e.g., certain vehicle models of year X) or a campaign for providing a new software package to a group of vehicles (e.g., a new in-vehicle chatbot for finding music content). The rule 522 may define what vehicles are subject to / applicable for a software update and what content 515 is to be provided to the subject vehicles. For example, a rule 522 may be a combination of characters, text string, etc. that explicitly describes the intention to distribute given content 515 to a specific set of vehicles.

[0116] A “task” can represent the instance of a rule 522 as it applies to a discrete vehicle 105, such that when the vehicle 105 communicates with the update controller 500, the update controller 500 notifies the vehicle 105 of the task and the vehicle computing system 200 executes it. The task can include an action that that vehicle 105 is to take to implement the content 515. This can include, for example, downloading a software update package over a network, updating / changing the configuration of a component of the vehicle 105, downloading certain media content and storing it onboard for a user of the vehicle with a status identifier (e.g., “new”), etc.

[0117] The consumer systems 520 may automatically create a rule 522 or allow for manual creation of a rule 522. For instance, the consumer systems 520 may be configured to automatically create a rule 522 once the content 515 is validated, deployed, posted, or otherwise made available for distribution. Additionally, or alternatively, the consumer systems 520 may include a display device that is configured to present a user interface for a user of the consumer systems 520. The user interface may allow a user to provide user input to create a rule 522.

[0118] The update controller 500 may communicate with one or more external software services 525 to facilitate the distribution of the content 515 in accordance with a rule 522. The external software services 525 may also be referred to herein as “dependencies” 525. The external software services 525 may include platform-based systems such as back-end software services (e.g., microservices). The external software services 525 may include services that process or maintain information that can help determine whether a rule 522 applies to a particular vehicle 105 and the actions that are to be taken by the vehicle 105 to implement the content 515 associated with the rule 522. In an example, the dependencies 525 may include a vehicle calling service that maintains / accesses one or more data structures that include vehicle identification number (VINs) for all vehicles. The dependencies 525 may include a vehicle configuration service configured to access the vehicle configuration of a respective vehicle as well as external data associated therewith. In another example, the dependences 525 may include a vehicle document (VDOC) service. The VDOC service may include an external vehicle metadata service that maintains a record of the respective current and / or past configurations for each of the respective vehicles as well as any documentation (e.g., required by regulations).

[0119] The update controller 500 may include one or more services, components, systems, etc. that are configured to help orchestrate the content 515. For instance, the update controller may include a vehicle service 530 that responds to traffic from the vehicle 105. For example, thevehicle service 530 may be configured to receive a request 510 for content 515 from a vehicle 105. The request 510 may include data that indicates the vehicle 105 is available for content, if there is content that is applicable to the vehicle 105. In an example, the request 515 may be an explicit request for a particular (or any) OTA software package. The vehicle service 530 may be configured to respond to the request 510 with a data payload that is indicative of the content 515 (e.g., OTA software package) as well as the action that the vehicle 105 should take to implement the content 515.

[0120] The update controller 500 may include one or more controller components 535. The controller components 535 may be software services configured to map rules and actions to vehicle-specific tasks and carrying out a number of other related responsibilities. For example, the controller components 536 may be configured to communicate with external software services 525 or determine which external software services 525 to communicate with to gather information for particular content 515. This may help the update controller 500 determine an action for a vehicle 105 to take with respect to content 515. The controller components 535 may include, for example, a rule service (e.g., a microservice for evaluating rules), a service that is responsible for evaluating vehicle inventory, a device service, a data sync service, etc.

[0121] The update controller 500 may include an administration service 540 that is configured to expose an interface for consumer systems 520 to interact with the update controller 500. The administration service 540 may be configured to access data indicative of a rule 522 and interact with the controller components 535 to progress the rule 522 within the ecosystem. For example, the administration service 530 may be configured to coordinate with the rest of the update controller ecosystem such that if the vehicle service 530 were to get a request 510 from a vehicle 105 that is qualified for the content 515, the vehicle service 530 would be able to inform vehicle 105 of the action that needs to be taken for implementation of the content 515.

[0122] By way of example, the administration service 540 may obtain a rule 522 for distributing an OTA software package such as, “all 2021 models are to upgrade to navigation version 6.1.6.” The update controller 500 (e.g., via the controller components 535) may communicate with the external software services 525 from which the update controller 525 can obtain information for a vehicle 105, subject to the rule 522, to properly implement the OTA software package. The update controller 500 may package the collected information for the subject vehicle 105 and output such information to the vehicle 105 via the vehicle service 530.This may allow vehicle computing system 200 (onboard the vehicle 105) to take the appropriate action to implement the OTA software package.

[0123] While the example described in FIG. 5 illustrates the services and systems that may be utilized to communicate the content 515 to a vehicle based on a request from the vehicle 105, the technology of the present disclosure improves these services / systems to intelligently determine that a vehicle 105 may be available for content (with or without an explicit request from the vehicle) and communicate the content 515 to the computing system of the physical premises where the vehicle 105 is expected to be available. As further described herein, this can allow for the download of the content 515 by the vehicle 105 via a local computing infrastructure, at a time when the vehicle state and its network connectivity are known and more reliable, which improves the efficiency of delivering the content 515 to the vehicle 105.

[0124] FIG. 6 illustrates a diagram of example computing ecosystem 600 for providing content to a local computing edge according to an embodiment hereof. The components, systems, and subsystems of FIG. 6 may be implemented as modules on computing hardware. The computing ecosystem 600 of FIG. 6 may be used in association with a workshop / service station for a vehicle. However, such a location is provided for example illustrative purposes only and is not meant to be limiting. Other types of locations and facilities may utilize the described technology.

[0125] As shown in FIG. 6, a vehicle 105 may be located in different types of environments. For example, the vehicle 105 may operate within an uncontrolled environment 605 or a controlled environment 610.

[0126] The uncontrolled environment 605 may be a domain in which the state of the vehicle 105 at any given time is relatively unknown or difficult to predict, and the network connectivity of the vehicle is relatively unknown, more dynamic, or less reliable. For example, the uncontrolled environment 605 may include the vehicle 105 travelling along highways or in urban areas where many vehicles or computing devices may be connecting to the same network and where the state of the vehicle 105 (e.g., parked, on, off, idle, locked) may be dynamic.

[0127] The nature of the uncontrolled environment 605 lowers the predictability of the vehicle state and network connectivity of the vehicle 105. For example, in an uncontrolled environment 605, network connectivity may be inconsistent for the vehicle 105 because it depends on the location of the vehicle 105 (e.g., causing changes in telecommunications nodes, population density) and can often be interrupted by terrain and structure. Such unpredictabilitymay also arise from the lack of control over the vehicle 105 or the lack of control over / insight into the other users of the network to which the vehicle 105 is connected. Network bandwidth, in an uncontrolled environment 605, can be low and limited because it may depend on Mobile Network Operator (MNO) service and, thus, constrained by the agreement with the MNO. In an uncontrolled environment 605, the vehicle state may be hard to control with regards to battery state, safe state, etc.

[0128] The controlled environment 605 may include an environment or location where the vehicle 105 is (e.g., currently or will be) in a known state and has a known network connectivity. This may include, for example, a workshop, re-fueling / charging station, manufacturing facility, vehicle production center, etc. The vehicle state may be known or more predictable because the vehicle 105 remains static or the vehicle’s state may be controlled by a user associated with the remote computing system 635 such as, for example, a technician in a workshop, or the like. The network connectivity may be known because the network connectivity (and the associated telecommunications hardware) of a static location is likely to be more consistent than a vehicle that is travelling on the road, where connectivity is dynamically changing.

[0129] The nature of the controlled environment 610 increases the predictability of the vehicle state and network connectivity of the vehicle 105. For example, in a controlled environment, the network connectivity can be made consistent - either with generations of gateways that support WiFi or other LAN mechanisms, or by presenting the gateway with a local MNO microcell 615. The bandwidth in the controlled environment 610 may be substantial or virtually unlimited by, for example, sinking the microcell 615 (or other local connectivity mechanism) to a wired / fiber broadband connection. As compared to the uncontrolled environment 605, the vehicle state can be easier to control in a controlled environment 610 because the vehicle 105 may be connected to power supply (e.g., charger of the workshop), the doors may be locked on demand (e.g., by a technician or remote signal), etc. Furthermore, collaboration with the vehicle’s operator (e.g., a driver) may be more difficult in an uncontrolled environment where the operator is a retail customer driving the vehicle, rather than a user dedicated to the controlled environment 610 such as a technician.

[0130] A local computing infrastructure 620 may be associated with the controlled environment 610. For example, at least a portion of the local computing infrastructure 620 may be located at / on the physical premises of an entity (e.g., a workshop). The local computing infrastructure 620 may provide a computing edge (e.g., for the update controller 500 - an OTAsystem backend) that can interface with the vehicle 105, to deliver content 515 to the vehicle 105 while it is within the controlled environment 610. In this way, the local computing infrastructure 620 can serve as an OTA “agent” that extends the OTA mechanism and coordinates content delivery via a single orchestration mechanism.

[0131] The local computing infrastructure 610 may include various components and subsystems. For example, the local computing infrastructure 610 may include the microcell 615 that is configured to sink the vehicle 105 to the local computing infrastructure 620. The microcell 615 may be, for example, an MNO microcell or other vehicle-link solution. The microcell 615 may include a small cellular base station that covers a limited area. For example, the MNO microcell may be dedicated to the entity associated with the controlled environment 610 (e.g., the workshop) or a surrounding area.

[0132] The microcell 615 may help facilitate the generation of one or more communication channels with the vehicle 105. This may include, for example, a control channel 625 A to the vehicle 625A through local uplink via the microcell 615. The control channel 625A may allow for the transmission of control signal(s). The control signal(s) may, for example, adjust a component, position, vehicle state, or other feature of the vehicle 105 while it is connected to the local computing infrastructure 620. A payload channel 625B may also be generated through local uplink via the microcell 615. The payload channel 625B may be utilized to deliver a data payload to the vehicle 105, as further described herein.

[0133] The local computing infrastructure 620 may include a vehicle presence agent 630. The vehicle presence agent 630 may be, or otherwise include, a module that is configured to maintain or access a data structure storing data that identifies which vehicles will be within the controlled environment 610 and the times at which the vehicles will be within the controlled environment 610. For example, the vehicle presence agent 625 may include or access an appointment scheduling system that generates an appointment for the vehicle 105 to receive maintenance at a workshop. In some examples, the appointment may be generated in response to a request for an appointment (e.g., by an owner / user the vehicle 105) or automatically based on historic servicing data of the vehicle 105.

[0134] The historic servicing data may indicate the history of maintenance and services performed on the vehicle 105. The appointment scheduling system may analyze this data to predict / determine when it is preferred for the vehicle 105 to next receive servicing. This may be determined based on the predicted mileage of the vehicle 105 from its last servicing, itspurchase, etc. Additionally, or alternatively, this may be determined based on the previous services provided (or not provided) to the vehicle 105 during its last servicing.

[0135] In some implementations, the appointment scheduling system may trigger a notification indicative of the scheduled appointment. The notification may be sent to a user device 115 of a user 120 of the vehicle 105. In some implementations, the notification may be sent to the vehicle computing system 200 for the vehicle 105. The notification may be displayed (e.g., a display device) for the user 120. In some implementations, the appointment may be confirmed, denied, or modified by the user 120 providing user input in response to the notification. Data indicative of the confirmation, denial, and / or modification may be provided to the appointment scheduling system. The vehicle presence agent 630 may access such information to determine that the vehicle 105 will be coming to the controlled environment 610 as well as the time the vehicle 105 will be there.

[0136] In some implementations, the vehicle presence agent 630 may determine the duration of time that the vehicle 105 will be within the controlled environment 610. This may be indicated in the appointment scheduling system or determined by the type of maintenance / servicing that the vehicle 105 is expected to receive.

[0137] The vehicle presence agent 630 may determine that a vehicle 105 is currently present within the controlled environment 610. The vehicle presence agent 630 may do so by accessing one or more signals indicating the vehicle’s presence. For example, the vehicle presence agent 630 may be configured to determine that the vehicle is currently located within controlled environment 610 when the vehicle 105 connects to the local computing infrastructure 620.

[0138] The vehicle presence agent 630 may be configured to communicate with a remote computing system 635. For instance, the vehicle presence agent 630 may transmit, to the remote computing system 635, data indicating when the vehicle 105 will be within the controlled environment 610 or that the vehicle 105 is currently located within the controlled environment 605. The vehicle presence agent 630 may generate such data, for example, based on the vehicle presence agent 630 accessing a workshop’s schedule, a prediction, or a user’s confirmation, as described herein.

[0139] The local computing infrastructure 620 may include local routing infrastructure 640. The local routing infrastructure 640 may provide one or more routing points for the local computing infrastructure 620 to enable communication between devices. The local routing infrastructure 640 may be configured to route and exchange data traffic to and among: thesystems of the local computing infrastructure, the vehicle 105, and / or the remote computing system 635 (and the components thereof).

[0140] The local routing infrastructure 640 may include devices and protocols used to manage and direct data traffic. For example, the local routing infrastructure 640 may include routers, switches, memories, processors, or other types of computing hardware. The local routing infrastructure 640 may include routing tables (e.g., containing information about network destinations, next-hop routers, metrics), routing protocols, (e.g., rules / algorithms for routing information and dynamically updating routing tables), and be configured for network addressing.

[0141] The local computing infrastructure 620 may include payload caching infrastructure 645. The payload caching infrastructure 645 may be responsible for ensuring that relevant payloads are available on-time within the local computing infrastructure 620. The payload caching infrastructure 645 may include a local cache that provides a storage mechanism to temporarily store data payloads that are to be provided to one or more vehicles.

[0142] In some implementations, the payload caching infrastructure 645 may include, or be associated with, a download queue. The queue may be indicative of an order, priority, etc. for each data payload stored in the queue. For example, data payloads may be queued in the order in which their associated vehicles are to arrive at the controlled environment 610 (e.g., the workshop). Additionally, or alternatively, the data payloads may be queued based on their associated content. For instance, the more vehicles to which particular content (e.g., a software update) applies, the higher the associated data payload may be in the queue.

[0143] The local computing infrastructure 620 may include a user portal 650. The user portal 650 may be or include a user computing device associated with the controlled environment 610 or may be or include a software application running on the user computing device. The user portal 650 may be a mobile client device (e.g., tablet, mobile phone), desktop computer, display device, personal digital assistance, etc. or software application running thereon. The user portal 650 may include a user interface (UI) presented via a display of the user computing device. The user interface may render information associated with the vehicle 105. This can include information about content to be downloaded to the vehicle 105. For example, the user portal 650 may receive messages indicating certain content that may be available for the vehicle 105, enable a response to the messages, present actions to take to facilitate the download, present the status of content to be downloaded or that is downloading to the vehicle, etc. This may allow a user 655 (e.g., a technician at a workshop) to determine what content 515 is intended for the vehicle 105,provide confirmation of the content 515, and monitor the status of such download. The user portal 650 may receive data from, for example, the remote computing system 635.

[0144] In some implementations, the user portal 650 may interface with the vehicle 105. For instance, the user portal 650 (e.g., tablet) may be physically connected to the vehicle 105 via a wired connection or via a wireless connection (e.g., Bluetooth Low Energy protocol, near-field communication). The user portal 650 may interface with the vehicle 105 by connecting to the same network that the vehicle 105 connects to via the microcell 615. Authorization of the connection of the user portal 650 with the vehicle 105 (e.g., to start downloads, control vehicle components) may include a confirmation by the vehicle owner or a user 655 via a user input to a display within the vehicle (e.g., of the head unit).

[0145] The user interface presented via the display of the user portal 650 may present one or more UI elements that allow the user 655 to provide user input (e.g., touch, voice, text, cursor selection) to control the vehicle 105 or the components thereof. This may allow the user 655 (e.g., technician) to change the position of the vehicle 105 or the vehicle state (e.g., to turn on the vehicle 105, lock the vehicle’s doors), connect the vehicle 105 to the microcell 615, etc.

[0146] The user portal 650 may present data indicating one or more actions (e.g., manual steps) for the user 655 to perform to facilitate the download of content 515 to the vehicle 105. This may include instructions for changing the vehicle 105 to the preferred state to download a data payload, connecting the vehicle 105 to the microcell, cycling power, etc. Such instructions may be provided by the remote computing system 605.

[0147] The remote computing system 635 may be remote from a vehicle 105 and the local computing infrastructure 620 (and the particular location where it resides). The remote computing system 635 may be, be included within, or otherwise include, the computing platform 110. In some implementations, the remote computing system 635 may include the update controller 500. One or more of the components / subsystems of the remote computing system 635 described and shown in FIG. 6 may be implemented within the update controller 500.

[0148] The remote computing system 605 may be configured to distribute content 515 for vehicles. The content may include OTA content such as, for example, OTA software packages, media content, or other digital content. To help coordinate the distribution of the content 515, the remote computing system 605 may include a content orchestrator 660 and a payload content delivery network (CDN) 665.

[0149] The content orchestrator 660 may be configured to orchestrate the distribution of data payloads 670. The content orchestrator 660 may be a system or module that is responsible for managing and coordinating the distribution of software updates to devices or systems remotely. The content orchestrator 660 may be, or include similar functionality as, the update controller 500 as described herein. For instance, the content orchestrator 660 may maintain or have access to a database or registry of vehicles, their current content (e.g., software versions), any available content for the vehicles, preferences, etc. The registry may include identifiers for the vehicles (e.g., VINs) and identifiers for the content (e.g., reference numbers, links). The content orchestrator 660 may schedule and deploy the content 515. This may include the deployment of content 515 in response to a request for available content. In some implementations, the content orchestrator 660 may be configured for error handling, security, reporting, and analytics associated with content distribution.

[0150] The content orchestrator 660 may update shadow records indicating the current content running on a vehicle 105. This may include a data structure identifying the versions of the various software applications running on the vehicle 105.

[0151] The content orchestrator 660 may communicate with the payload CDN 665 to distribute a data payload 670 that includes the content 515 to be downloaded to the vehicle 105. The payload CDN 665 may include one or more services (e.g., across various geographic regions) to deliver content 515. The payload CDN 665 may access data indicative of the content 515 (e.g., from an internal memory, external service / dependency) and generate a data payload 670 including the content 515. The data payload 670 may include other information such as, for example, metadata associated with the content 515, configurations, download instructions, etc. The payload CDN 665 may be configured to receive instructions from the content orchestrator 660 and transmit the data payload 670 to a recipient device. This may include a vehicle 105 or the local computing infrastructure 620.

[0152] The remote computing system 635 may be configured to distribute the content 515 to vehicles operating / located in different types of environments. The remote computing system 635 may be configured to determine whether to output the data payload 670 to the vehicle 105 within an uncontrolled environment 605 or a controlled environment 610.

[0153] By way of example, the vehicle 105 may be travelling in the uncontrolled environment 605 (e.g., along a highway). The content orchestrator 660 may access data (e.g., from the vehicle presence agent 630) indicating a time when the vehicle 105 may be within thecontrolled environment 610 (e.g., a workshop). The content orchestrator 660 may also access a database indicating the type, priority, size of the content 515 to be downloaded to the vehicle 105. Based on the priority of the content 515 and the time the vehicle 105 is estimated to be in the controlled environment 610, the content orchestrator 660 may determine whether too much time would pass until the vehicle 105 is to arrive within the controlled environment 610 such that it is important for the vehicle 105 to download the content 515 (e.g., a software update) within the uncontrolled environment 605. The content orchestrator 660 may determine that the size of the content 515 is appropriate for download in the uncontrolled environment 605 because it is small enough to avoid persistent download interruptions.

[0154] Within the uncontrolled environment 605, the vehicle 105 may be connected to one or more MNO stations 675. The MNO stations 675 may include one or more base stations or cell towers operated by a mobile network operator to provide wireless communication services to the vehicle 105. The connection between the vehicle 105 and the MNO stations 675 may establish one or more communications channels 680A-B. The vehicle 105 may connect to a plurality of respective MNO stations 675 as the vehicle 105 is travelling with in the uncontrolled environment 605 (e.g., along a highway). The network connectivity of the vehicle 105, the network bandwidth, signal strength, etc. may vary as the vehicle 105 travels.

[0155] The vehicle 105 may provide, the remote computing system 635, data indicating the vehicle 105 is available for content 515. This may include a request for any content 515 that is available and applicable to the vehicle 105. The content orchestrator 660 may receive the request and, in response, communicate instructions to the payload CDN 665 to distribute a data payload 670 (e.g., a software update) to the vehicle 105 via the MNO station 675, while the vehicle 105 is in the uncontrolled environment 605.

[0156] In another example, rather than provide the data payload 670 to the vehicle 105 in the uncontrolled environment 605, the content orchestrator 660 may determine that the content 515 is to be distributed to the vehicle 105 when the vehicle 105 is within the controlled environment 610. FIG. 7 illustrates a diagram of an example dataflow 700 for distributing content to vehicles in controlled environments according to an embodiment hereof.

[0157] At (705), the content orchestrator 660 (e.g., of remote computing system 635) may access data indicative of a vehicle identifier associated with a vehicle 105. The content orchestrator may access a time that the vehicle 105 is estimated to be within a controlled environment 610. Such information may be accessed via the vehicle presence agent 630.

[0158] The content orchestrator 660 may determine, based on the vehicle identifier, that content 515 is available for the vehicle 105. This may include, for example, using the vehicle identifier to perform a look-up function in a database that includes a data structure indicating what content 515 is available for the vehicle 105, which may be listed in association with the vehicle identifier.

[0159] At (710), the content orchestrator 660 may output, for delivery to the user portal 650 associated with the controlled environment 710, a message indicating the content 515 is available for the vehicle 105. The user portal 650 may process the message and present the message via a user interface (on a display device) to a user 655 associated with the controlled environment 605, at (715). For example, the user interface may present information about the content 515 such as the type (e.g., software update), data size, priority, associated vehicle components, intended function, or other contextual information.

[0160] In some implementations, the user 655 (e.g., a technician) may be solicited for user input via the user interface. For example, the user 655 may be prompted to confirm that the content 515 is to be downloaded to the vehicle 105. The user 655 may provide user input to the user portal 650. The user portal 650 may generate user input data 720, based on the user input provided from the user 655 associated with the controlled environment 610 (e.g., workshop).

[0161] Additionally, or alternatively, the user 655 may provide user input, to the user portal 650, indicating additional content to be downloaded to the vehicle 105. For instance, the additional content may include one or more additional software updates to be downloaded to the vehicle 105. In some implementations, the additional content may be a different type of content than the content 515. For example, the content 515 may include a software update and the additional content may include media content or other digital content.

[0162] At (725), the content orchestrator 660 may access user input data 720 indicative of a response to the message indicating the content 515 is available for the vehicle 105. Based on the content 515 (and in some instances, the user input data 720), the content orchestrator 660 may determine a data payload 670 for download to the vehicle 105 while the vehicle 105 is within the controlled environment 610. For example, the content orchestrator 660 may instruct a payload CDN 665 to generate a data payload 670 that includes the content 515 and any configurations / instructions for downloading and implementing the content 515. The data payload 670 may be in a format that can be downloaded to the vehicle 105.

[0163] At (730), the content orchestrator 600 may initiate the caching of the data pay load 670 at the local computing infrastructure 620. For example, the content orchestrator 660 may initiate the output of the data payload 670 to a local computing infrastructure 620 associated with the controlled environment 610 by instructing the payload CDN 665 to transmit the data payload 670. In response, the payload CDN 665 may transmit the data payload 670 to the routing infrastructure 640, which may route the data payload 670 to the payload caching infrastructure 645 of the local computing infrastructure 620. The data payload 670 (including the content 515) may be cached before the vehicle 105 is within the controlled environment 610.

[0164] At (740), the vehicle 105 may arrive at the controlled environment 610 (e.g., based on routing instructions to workshop) and operations may be performed to facilitate the download of the data payload 670 to the vehicle 105. For instance, the content orchestrator 660 may communicate data to the user portal 650 to synchronize metadata about the content 515 to be downloaded and solicit actions from the user 655 associated with the controlled environment 610 (e.g., the technician of the workshop). The actions may include manual steps for the user 655 to perform to facilitate the download of the data payload 670 to the vehicle 105. This may include, for example, connecting the vehicle 105 to the MNO microcell, putting the vehicle in a desired state (e.g., idle, power on, safe state), or other actions. At (740), the user 655 may perform such actions by interacting with the vehicle 105.

[0165] At (745), the vehicle 105 may download the data payload 670 from the payload caching infrastructure 645. While the data payload 670 is being downloaded, the content orchestrator 660 may access data indicative of a status of the download. This may include a state identifier (e.g., not started, pending, buffering, complete), a percentage, or another type of indicator of the download progress. Data indicative of the status of the download may be output to the user portal 650.

[0166] At (750), that the user 655 may monitor the progress of the download (e.g., via a user interface rendering a progress indicator) and the user 655 may aid the vehicle 105, if needed. In some implementations, the user portal 650 may directly monitor the progress of the download. This may occur in the event the user portal 650 is interfaced with the vehicle 105.

[0167] The vehicle 105 may continue to download the payload 670 until it is complete. After which, the user 655 may complete any additional servicing, charging, etc. for the vehicle 105 and the vehicle 105 may leave the controlled environment 610. In some implementations, the user655 may perform servicing, maintenance, etc. while the data payload is being downloaded to the vehicle 105.

[0168] FIGS. 8A-B illustrate flowchart diagrams of example methods for distributing content to vehicles according to an embodiment hereof. The methods may be performed by a computing system described with reference to the other figures (e.g., FIGS. 1-6, 9). In an embodiment, the methods may be performed by a control circuit of a computing system. One or more portions of the methods may be implemented as an algorithm on the hardware components of the devices described herein. For example, the steps of the methods may be implemented as operations / instructions that are executable by computing hardware. This can include one or more non-transitory computer-readable media that store instructions that are executable by a control circuit (e.g., one or more processors) to perform the operations of FIGS. 8A-B.

[0169] FIGS. 8A-B illustrate elements performed in a particular order for purposes of illustration and discussion. Those of ordinary skill in the art, using the disclosures provided herein, will understand that the elements of any of the methods discussed herein may be adapted, rearranged, expanded, omitted, combined, or modified in various ways without deviating from the scope of the present disclosure.

[0170] FIGS. 8A-B are described with reference to elements / terms described with respect to other systems and figures, for example illustrated purposes and is not meant to be limiting. One or more portions of the methods may be performed additionally, or alternatively, by other systems.

[0171] In an embodiment, the method 800 may begin with or otherwise include an operation 805, in which a computing system (e.g., remote computing system 635) may access data indicative of a vehicle identifier associated with a vehicle 105 and a time that the vehicle 105 is estimated to be within a controlled environment 610. As described herein, the controlled environment 610 may include a location where the vehicle 105 is (or will be) in a known state and has (or will have) a known network connectivity. For example, the controlled environment 610 may be an automotive service location such as a workshop (or other vehicle-related facility) where the vehicle 105 can be entered into a particular vehicle state (e.g., by a technician). The workshop may also have a general level / range of network connectivity that is known and that is (or will be) available to the vehicle 105.

[0172] To determine the time the vehicle 105 is estimated to be at the controlled environment 610 (e.g., the workshop), the computing system may obtain data indictive of a scheduled servicefor the vehicle 105 and determine the time that the vehicle 105 is estimated to arrive at the controlled environment 610 based on the scheduled service for the vehicle 105. The data indicative of the scheduled service may be an appointment notification that includes the vehicle identifier for the vehicle 105. Additionally, or alternatively, as described herein, the time the vehicle 105 is to be within the controlled environment 610 may be predicted based on historic servicing data associated with the vehicle 105.

[0173] In some implementations, the computing system may access a request by the vehicle 105 for available content (e.g., applicable software updates). The request may include the vehicle identifier, which the computing system may utilize to structure a query to determine the time the vehicle 105 is to be within the controlled environment 610, if any.

[0174] The method 800 in an embodiment may include an operation 810, in which the computing system may determine, based on the vehicle identifier, that content 515 is available for the vehicle 105. As described herein, the content 515 may include, for example, at least one of: (i) a software package (e.g., software update), (ii) media content; or (iii) other digital content. The computing system may determine that the content 515 is available for the vehicle 105 by communicating with one or more other systems or services. For example, the computing system may access its databases, transmit a query to another system, etc. to determine if there is relevant content for the vehicle 105 (e.g., based on its make / model / year).

[0175] In some examples, the computing system may determine whether the content 515 for the vehicle 105 is already stored in a local computing infrastructure 620 (e.g., local cache storage) located at the controlled environment 610. For instance, the computing system may transmit a request to the local computing infrastructure 620, which may access its local payload caching infrastructure 645 to determine whether the content 515 that is relevant and available for the vehicle 105 is already locally cached. To do so, the local computing infrastructure 620 may generate a search query or perform a look-up function in the local payload caching infrastructure 645 using an identifier associated with the content 515 (e.g., a reference number, serial number, name, etc. provided by the computing system). In the event that the local payload caching infrastructure 645 already includes the content 515, the local payload caching infrastructure 645 may provide an instruction to associate a vehicle identifier of the vehicle 105 with that content 515. This may include making a data entry, completing data field(s), etc. to indicate that the content 515 should be distributed to the vehicle 105 associated with the particular vehicle identifier.

[0176] The local payload caching infrastructure 645 may transmit a communication to the computing system (e.g., the content orchestrator 660) indicating whether or not the content 515 is already locally cached.

[0177] In an embodiment, the method 800 may include an operation 815, in which the computing system may access data indicative of a type of the controlled environment 610. For example, the computing system may access data including an identifier associated with the controlled environment 610. This identifier (e.g., a facility identifier) may be obtained, for example, when the computing system is determining whether the vehicle 105 is to be at the controlled environment 610 and a time associated therewith. The identifier may be indicated in a schedule and may indicate the facility, entity, etc. that creates the controlled environment 610.

[0178] The computing system may perform a look-up function on a data structure, using the identifier associated with the controlled environment 610. The data structure may include a data entry or field that identifies the type of controlled environment 610. The type may indicate, for example, that the controlled environment 610 includes an automotive service location (e.g., workshop), a dealership, a vehicle manufacturing facility, a vehicle production center, a charging station, or another entity / facility. The data structure may include a data entry or field that indicates network information for the controlled environment 610. This may include an IP address, security information, network connectivity, etc. In this way, the identifier associated with the controlled environment 610 may be used to access information that allows the computing system to confirm the network connectivity will be in a known state (e.g., via the network information) and the vehicle state will be known (e.g., because it is within an automotive service location and can be controlled)

[0179] In an embodiment, the method 800 may include an operation 820, in which the computing system may determine, based on the time that the vehicle 105 is estimated to be at the location, that the content 515 is to be provided for download to the vehicle 105 while the vehicle is within the controlled environment 610 rather than while the vehicle 105 is within an uncontrolled environment 605 where the state of the vehicle 105 and the network connectivity of the vehicle 105 is unknown or dynamically changes. The computing system may determine that the content 515 is to be provided for download to the vehicle 105 while the vehicle 105 is within the controlled environment 610 based on at least one of: (1) a priority of the content (e.g., high / medium / low, numerical value), (2) a size of the content (e.g., in KB, MB, GB), or (3) a type of the content (e.g., software update, audio book, podcast, music, map update).

[0180] By way of example, the vehicle 105 may be traveling within the uncontrolled environment 605 such as within a major metropolitan city. The computing system may determine that there is a software update that is available for the vehicle 105. The software update may be an update to certain display elements within a user interface of the vehicle’s head unit. Thus, the priority associated with the software update may be low. The size of the software update may be larger such that it may require significant bandwidth and consistent network connectivity to avoid download interruptions. Moreover, the time that the vehicle 105 is estimated to be at the location associated with the controlled environment 610 may indicate the vehicle 105 will be at a workshop (e.g., for an upcoming appointment) within the next two days. As a result, the computing system may determine that due to the inconsistent network connectivity and unknown state of the vehicle 105 while it is travelling within the city, it would be better for the vehicle 105 to wait to download the software update while it is at the workshop for its upcoming appointment than to try to download the software update while travelling in the city.

[0181] In another example, the content 515 available to the vehicle 105 may include a suggested audio book. Given the type of content 515, the computing system may determine that the vehicle 515 may wait to download the content 515 until it is at the workshop, rather than while travelling within the city.

[0182] In an embodiment, the method 800 may include an operation 825, in which the computing system may initiate, for delivery to a client computing device associated with the controlled environment 610, the output of a message indicating the content 515 is available for the vehicle 105. The computing system may be configured to communicate with the client computing device via one or more APIs. The client computing device may include the user portal 650. The client computing device may include a display device and may be configured to render a user interface via the display device, for a user 655 associated with the controlled environment 610. The user 655 associated with the controlled environment 610 may be, for example, a technician at an automotive service location. The client computing device may include a tablet or mobile user device located at the premises of the automotive service location.

[0183] The message may be presented via a user interface of the display device, of the client computing device. The message may include text, numbers, characters, graphics, etc. that inform the user 655 that the content 515 is available for the vehicle 105, which is estimated to be at the controlled environment 610. For instance, the message may indicate to the user 655 (e.g., a service technician) that a software update is available for the vehicle 105 and prompt the user655 to confirm that the software update can be / is to be downloaded when the vehicle 105 is within the controlled environment (e.g., the workshop).

[0184] In some instances, the message may allow the user 655 to request other or additional content to be downloaded to the vehicle 105. For example, the user interface may include a UI element that is selectable by the user 655 (e.g., a soft button, text field, drop down menu). The UI element may allow the user 655 to indicate alternative or additional content to be downloaded to the vehicle 105. For example, a drop down menu may indicate available content for selection by the user 655 or an editable field may allow the user 655 to enter or search for other content.

[0185] In an embodiment, the method 800 may include an operation 830, in which the computing system may access user input data indicative of a response to the message indicating the content 515 is available for the vehicle 105. The user input data may be based on user input, to the client computing device, from a user 655 associated with the controlled environment 610. The user input may include touch input (e.g., to a touch screen), voice input, text input, cursorbased input, etc.

[0186] For example, the content 515 (e.g., indicated in the message to the client device) may include a software update for the vehicle 105. In response to the message, the user 655 may provide user input (e.g., to the UI elements of the user interface) to select additional software updates that the user 655 desires to be provided for download to the vehicle 105. The client computing device may transmit data (e.g., over a network) to the computing system in a format that is ingestible by the computing system (e.g., via an API). This may include user input data indicative of the user’s response. For example, the user input data may be indicative of an additional software update to be downloaded to the vehicle 105.

[0187] In another example, the user input data may indicate one or more different types of content than content 515 indicated by the computing system. For example, the user 655 may indicate media content or other digital content to be provided for download to the vehicle 105 when the vehicle 105 is in the controlled environment 610.

[0188] Additionally, or alternatively, the user input data may be indicative of a confirmation by the user 655 of the content 515. For instance, the user 655 may provide user input confirming the content 515 is to be downloaded to the vehicle 105 when the vehicle 105 is within the controlled environment 610 (e.g., at a later time). The client computing device may generate the user input data based on the confirmation and transmit it to the computing system, which is remote from the controlled environment 610.

[0189] In an embodiment, the method 800 may include an operation 835, in which the computing system may, based on the content, determine a data payload 670 for download to the vehicle 105 while the vehicle 105 is within the controlled environment 610. For instance, as described herein, the computing system (e.g., including a content orchestrator 660) may communicate with a payload CDN 665 to distribute a data payload 670 that includes the content 515 to be downloaded to the vehicle 105. The payload CDN 665 may include one or more services configured to package or deliver content 515. The payload CDN 665 may access data indicative of the content 515 (e.g., from an internal memory, third party service) and generate the data payload 670 including the content 515. The data payload 670 may include other information such as, for example, metadata associated with the content 515, configurations, download instructions, etc.

[0190] In an example, the data payload 670 may be determined based on the user input data. As described herein, the user input data may indicate alternative or additional content to be provided for download by the vehicle 105. For instance, the content 515 may include a software update (e.g., for a vehicle head unit software version) and the user 655 may have provided user input indicating that an additional software update (e.g., for on-vehicle comfort setting personalization) be provided for vehicle download. The data payload 670 may include the software update and the additional software update to be downloaded to the vehicle 105 while the vehicle 105 is in the controlled environment 610.

[0191] In an embodiment, the method 800 may include an operation 840, in which the computing system may initiate the output of the data payload 670 to a local computing infrastructure 620 associated with the controlled environment 610. For instance, the computing system may transmit a signal to have one or more of its components (e.g., a payload CDN 665) or a third party service / system transmit the data payload 670 over a network to the local computing infrastructure 620. As described herein, the local computing infrastructure 620 may be configured to store the data payload 670 within a payload caching infrastructure 645, where the data payload 670 may be locally cached for provision to the vehicle 105 when the vehicle 105 is within the controlled environment 610.

[0192] In an embodiment, the method 800 may include an operation 845, in which the computing system may initiate, for delivery to the client computing device associated with the controlled environment 610, the output of data indicating one or more actions for the user 655 to facilitate the download of the data payload 670 to the vehicle 105 while the vehicle 105 is withinthe controlled environment 610. The data indicative of the one or more actions may be presented to the user 655 via the user portal 650.

[0193] The data indicating the one or more actions for the user may include instructions to assist the user 655 with one or more manual steps before, during, after, etc. the download of the data payload 670 to the vehicle 105.

[0194] The actions may be intended to help with the download. By way of example, the actions may instruct the user 655 to connect the vehicle 105 to the network of the controlled environment 610. The controlled environment 610 may include a microcell 615 for the vehicle 105 to download the data payload 670. The actions may include the user 655 interacting with the head unit of the vehicle 105 to connect the vehicle 105 to the microcell 615. The actions may instruct the user 655 to connect the client computing device (e.g., user portal 650) to the vehicle 105 wirelessly or wired connection.

[0195] The actions may instruct the user 655 to interact with the vehicle 105 to enter the vehicle 105 into a particular vehicle state. This may include the vehicle 105 being powered on (e.g., without the engine running), the doors being locked, one or more components being powered down, entering a safe state, etc. During the download, the actions may include, for example, checking the progress of the download, ensuring the connection to the microcell is maintained, changing the vehicle state, interacting with the vehicle 105 to advance the download (e.g., by providing user input to the head unit display to progress forward iterative stages of the download), performing other work on the vehicle, etc. After the download, the actions may include steps for confirming the content 515 is working properly, verifying the download is complete, changing the vehicle state, disconnecting the vehicle 105 from the microcell, etc.

[0196] In an embodiment, the method 800 may include an operation 850, in which the computing system may initiate the output of instructions for routing the vehicle 105 to the controlled environment 610 where the data payload 670 is available for download via the local computing infrastructure 620. For instance, the computing system may provide routing instructions to the vehicle 105 such that the vehicle 105 can present the routing instructions to a user 120 of the vehicle 105 (e.g., via the display of the head unit) or such that the vehicle’s computing system can autonomously navigate the vehicle 105 according to the routing instructions.

[0197] In an example, the computing system may communicate with a navigation service or system that provides navigation to the vehicle 105. This may include navigation system 435. Thecomputing system may request that routing instructions be provided to a location / entity (e.g., workshop) associated with the controlled environment 610. The request may include an identifier associated therewith. The navigation service / system may generate the routing instructions to the requested location (or within proximity thereto) and output the routing instructions to the vehicle 105.

[0198] The vehicle 105 may travel to and arrive within the controlled environment 610 (e.g., based on the routing instructions). As described herein, the controlled environment 610 may include a microcell 615 for the vehicle 105 to download the data payload 670. The vehicle 105 may connect to the network associated with the controlled environment 610 via the microcell 615. The data payload 670 may be provided to the vehicle 105, from the payload caching infrastructure 645. The vehicle 105 may begin downloading the data payload 670 while within the controlled environment 610. This can occur via the stable network that has network connectivity that is generally known, while the vehicle 105 is in a known state (e.g., a prefer state for downloading content).

[0199] With reference to FIG. 8B, in an embodiment, the method 800 may include an operation 855, in which the computing system may access data indicative of a status of the data payload 670. The status may indicate a discrete state of the download (e.g., ready, not yet started, starting, buffering, pending, currently in progress, complete) or a percentage / level / numerical value / etc. indicating a progress of the download. For example, the data payload 670 may include one or more software updates, and the status of the data payload 670 may be indicative of a progress in downloading each respective software update to the vehicle 105.

[0200] For instance, the client computing device may provide data to the computing system indicating the progress of the download to the vehicle 105. The client computing device may automatically obtain such information by monitoring the download while the client computing device is connected to the vehicle 105 (e.g., wired, wirelessly).

[0201] Additionally, or alternately, the user 655 (e.g., technician) may provide user input indicative of the download status. For instance, the user 655 may read the percentage of the download that has been completed, as it is displayed via the vehicle’s head unit. The user 655 may provide user input to the client computing device indicating the progress and the client computing device may communicate this information to the computing system that is remote from the controlled environment 610.

[0202] In some implementations, the computing system may access the data indicative of a status of the data payload 670 from the vehicle 105. For example, the computing system may communicate with the vehicle 105 while it is within the controlled environment 610 (e.g., to request a status update) or the vehicle 105 may be configured to provide the data indicative of the status to the computing system (e.g., periodically during the download).

[0203] In some implementations, the computing system may obtain the data indicative of the status of the data payload 670 from the local computing infrastructure 620. This data may arise from a component other than the client computing device (e.g., user portal 650). For example, the payload caching infrastructure 645 (or a system associated therewith) may monitor the status of the data payload 670 being downloaded to the vehicle 105 and communicate data indicative of the status to the computing system (e.g., via the routing infrastructure 640).

[0204] In an embodiment, the method 900 may include an operation 860, in which the computing system initiates, for delivery to the client computing device associated with the controlled environment 610, data indicative the status of the data payload 670. The client computing device (e.g., user portal 650) may process such data and presented for the user 655 via a user interface on a display.

[0205] In an embodiment, the method 800 may include an operation 865, in which the computing system may access data indicating the content download is complete. The vehicle 105, the client computing device, or another component of the local computing infrastructure 620 may provide such data to the computing system. The completion of the download may arise when the entire data payload 670 (or at least the portion intended for download to the vehicle 105) is downloaded to the onboard computing system 200 of the vehicle 105.

[0206] In an embodiment, the method 800 may include an operation 865, in which the computing system may update a record associated with the vehicle 105 to reflect the completed download of the content 515 (and any additional content). As described herein, the vehicle 105 may be associated with a shadow record, which indicates the current components, content, etc. onboard the vehicle 105. This can include, for example, the current software versions running on the vehicle 105, the currently downloaded media / other digital content, etc. The computing system can access and adjust the shadow record of the vehicle 105 or request such an update by a service / system that maintains the shadow record. Adjusting the shadow record may include updating or creating a data field with a data entry to indicate the content 515 that was downloaded to the vehicle 105. For example, a data entry can be written in the data structure ofthe shadow record to reflect that the vehicle 105 has downloaded a particular software update, as well as the additional software updates requested by the user 655, if any. In this way, the computing system may maintain an accurate representation of the onboard computing system 200 of the vehicle 105 (and its content) even for content delivered locally to the vehicle 105 while within the controlled environment 610.

[0207] FIG. 12 illustrates a block diagram of an example computing system 7000 according to an embodiment hereof. The system 7000 includes a computing system 6005 (e.g., a computing system onboard a vehicle), a remote computing system 7005 (e.g., a server computing system, a cloud computing platform, a testing computing system, etc. that is remote from the vehicle), and a user device 8005 (e.g., user device of a vehicle user, user device of a user associated with a controlled environment) that are communicatively coupled over one or more networks 9050. The computing system 6005, remote computing system 7005, user device 8005, and networks 9050 may represent the systems (and the components of those systems) and networks described herein with reference to other figures.

[0208] The computing system 6005 may include one or more computing devices 6010 or circuitry. For instance, the computing system 6005 may include a control circuit 6015 and a non- transitory computer-readable medium 6020, also referred to herein as memory. In an embodiment, the control circuit 6015 may be or otherwise include one or more processors (e.g., microprocessors), one or more processing cores, a programmable logic circuit (PLC) or a programmable logic / gate array (PLA / PGA), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other control circuit. In some implementations, the control circuit 6015 may be part of, or may form, a vehicle control unit (also referred to as a vehicle controller) that is embedded or otherwise disposed in a vehicle (e.g., a Mercedes-Benz® car or van). For example, the vehicle controller may be or may include an infotainment system controller (e.g., an infotainment head-unit), a telematics control unit (TCU), an electronic control unit (ECU), a central powertrain controller (CPC), a charging controller, a central exterior & interior controller (CEIC), a zone controller, or any other controller. In an embodiment, the control circuit 6015 may be programmed by one or more computer-readable or computer-executable instructions stored on the non-transitory computer-readable medium 6020.

[0209] In an embodiment, the non-transitory computer-readable medium 6020 may be a memory device, also referred to as a data storage device, which may include an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storagedevice, a semiconductor storage device, or any suitable combination thereof. The non-transitory computer-readable medium 6020 may form, e.g., a hard disk drive (HDD), a solid state drive (SDD) or solid state integrated memory, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), dynamic random access memory (DRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), and / or a memory stick.

[0210] The non-transitory computer-readable medium 6020 may store information that may be accessed by the control circuit 6015. For instance, the non-transitory computer-readable medium 6020 (e.g., memory devices) may store data 6025 that may be obtained, received, accessed, written, manipulated, created, and / or stored. The data 6025 may include, for instance, any of the data or information described herein. In some implementations, the computing system 6005 may obtain data from one or more memories that are remote from the computing system 6005.

[0211] The non-transitory computer-readable medium 6020 may also store computer- readable instructions 6030 that may be executed by the control circuit 6015. The instructions 6030 may be software written in any suitable programming language or may be implemented in hardware. The instructions may include computer-readable instructions, computer-executable instructions, etc. As described herein, in various embodiments, the terms “computer-readable instructions” and “computer-executable instructions” are used to describe software instructions or computer code configured to carry out various tasks and operations. In various embodiments, if the computer-readable or computer-executable instructions form modules, the term “module” refers broadly to a collection of software instructions or code configured to cause the control circuit 6015 to perform one or more functional tasks. The modules and computer- readable / executable instructions may be described as performing various operations or tasks when the control circuit 6015 or other hardware component is executing the modules or computer-readable instructions.

[0212] The instructions 6030 may be executed in logically and / or virtually separate threads on the control circuit 6015. For example, the non-transitory computer-readable medium 6020 may store instructions 6030 that when executed by the control circuit 6015 cause the control circuit 6015 to perform any of the operations, methods and / or processes described herein. In some cases, the non-transitory computer-readable medium 620 may store computer-executableinstructions or computer-readable instructions, such as instructions to perform at least a portion of the method of FIGS. 11 A-C.

[0213] The computing system 6005 may include one or more communication interfaces 6035. The communication interfaces 6035 may be used to communicate with one or more other systems. The communication interfaces 6035 may include any circuits, components, software, etc. for communicating via one or more networks (e.g., networks 750). In some implementations, the communication interfaces 6035 may include for example, one or more of a communications controller, receiver, transceiver, transmitter, port, conductors, software and / or hardware for communicating data / information.

[0214] The computing system 6005 may also include one or more user input components 6040 that receives user input. For example, the user input component 6040 may be a touch- sensitive component (e.g., a touch-sensitive display screen or a touch pad) that is sensitive to the touch of a user input object (e.g., a finger or a stylus). The touch-sensitive component may serve to implement a virtual keyboard. Other example user input components include a microphone, a traditional keyboard, cursor-device, joystick, or other devices by which a user may provide user input.

[0215] The computing system 6005 may include one or more output components 6045. The output components 6045 may include hardware and / or software for audibly or visually producing content. For instance, the output components 6045 may include one or more speakers, earpieces, headsets, handsets, etc. The output components 6045 may include a display device, which may include hardware for displaying a user interface and / or messages for a user. By way of example, the output component 6045 may include a display screen, CRT, LCD, plasma screen, touch screen, TV, projector, tablet, and / or other suitable display components.

[0216] The remote computing system 7005 may include one or more computing devices 710. In an embodiment, the remote computing system 7005 may include or is otherwise implemented by one or more server computing devices. In instances in which the remote computing system 7005 includes plural server computing devices, such server computing devices may operate according to sequential computing architectures, parallel computing architectures, or some combination thereof.

[0217] The remote computing system 7005 may include a control circuit 7015 and a non- transitory computer-readable medium 7020, also referred to herein as memory 7020. In an embodiment, the control circuit 7015 may be or otherwise include one or more processors (e.g.,microprocessors), one or more processing cores, a programmable logic circuit (PLC) or a programmable logic / gate array (PLA / PGA), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other control circuit. In an embodiment, the control circuit 7015 may be programmed by one or more computer-readable or computerexecutable instructions stored on the non-transitory computer-readable medium 7020.

[0218] In an embodiment, the non-transitory computer-readable medium 7020 may be a memory device, also referred to as a data storage device, which may include an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. The non-transitory computer-readable medium may form, e.g., a hard disk drive (HDD), a solid state drive (SDD) or solid state integrated memory, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), dynamic random access memory (DRAM), a portable compact disc read-only memory (CD-ROM), or a digital versatile disk (DVD), and / or a memory stick.

[0219] The non-transitory computer-readable medium 7020 may store information that may be accessed by the control circuit 7015. For instance, the non-transitory computer-readable medium 7020 (e.g., memory devices) may store data 7025 that may be obtained, received, accessed, written, manipulated, created, and / or stored. The data 7025 may include, for instance, any of the data or information described herein. In some implementations, the remote computing system 7005 may obtain data from one or more memories that are remote from the remote computing system 7005.

[0220] The non-transitory computer-readable medium 7020 may also store computer- readable instructions 7030 that may be executed by the control circuit 7015. The instructions 7030 may be software written in any suitable programming language or may be implemented in hardware. The instructions may include computer-readable instructions, computer-executable instructions, etc. As described herein, in various embodiments, the terms “computer-readable instructions” and “computer-executable instructions” are used to describe software instructions or computer code configured to carry out various tasks and operations. In various embodiments, if the computer-readable or computer-executable instructions form modules, the term “module” refers broadly to a collection of software instructions or code configured to cause the control circuit 7015 to perform one or more functional tasks. The modules and computer- readable / executable instructions may be described as performing various operations or taskswhen the control circuit 7015 or other hardware component is executing the modules or computer-readable instructions.

[0221] The instructions 7030 may be executed in logically and / or virtually separate threads on the control circuit 7015. For example, the non-transitory computer-readable medium 7020 may store instructions 7030 that when executed by the control circuit 7015 cause the control circuit 7015 to perform any of the operations, methods and / or processes described herein. This may include the operations described as being performed by the test computing system 610. In some cases, the non-transitory computer-readable medium 7020 may store computer-executable instructions or computer-readable instructions, such as instructions to perform at least a portion of the dataflows and methods / processes of FIGS. 7 and 8A-B.

[0222] The server computing system 7005 may include one or more communication interfaces 7035. The communication interfaces 7035 may be used to communicate with one or more other systems. The communication interfaces 7035 may include any circuits, components, software, etc. for communicating via one or more networks (e.g., networks 9050). In some implementations, the communication interfaces 7035 may include for example, one or more of a communications controller, receiver, transceiver, transmitter, port, conductors, software and / or hardware for communicating data / information.

[0223] The computing system 6005 and / or the server computing system 7005 may also be in communication with a user device 8005 that is communicatively coupled over the networks 9050.

[0224] The user device 8005 may include one or more computing devices 8010. The user device 8005 may include a control circuit 8015 and a non-transitory computer-readable medium 8020, also referred to herein as memory 8020. In an embodiment, the control circuit 8015 may be or otherwise include one or more processors (e.g., microprocessors), one or more processing cores, a programmable logic circuit (PLC) or a programmable logic / gate array (PLA / PGA), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other control circuit. In an embodiment, the control circuit 8015 may be programmed by one or more computer-readable or computer-executable instructions stored on the non-transitory computer-readable medium 8020.

[0225] In an embodiment, the non-transitory computer-readable medium 8020 may be a memory device, also referred to as a data storage device, which may include an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storagedevice, a semiconductor storage device, or any suitable combination thereof. The non-transitory computer-readable medium may form, e.g., a hard disk drive (HDD), a solid state drive (SDD) or solid state integrated memory, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), dynamic random access memory (DRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), and / or a memory stick.

[0226] The non-transitory computer-readable medium 8020 may store information that may be accessed by the control circuit 8015. For instance, the non-transitory computer-readable medium 820 (e.g., memory devices) may store data 8025 that may be obtained, received, accessed, written, manipulated, created, and / or stored. The data 8025 may include, for instance, any of the data or information described herein. In some implementations, the user device 8005 may obtain data from one or more memories that are remote from the user device 8005.

[0227] The non-transitory computer-readable medium 8020 may also store computer- readable instructions 8030 that may be executed by the control circuit 8015. The instructions 8030 may be software written in any suitable programming language or may be implemented in hardware. The instructions may include computer-readable instructions, computer-executable instructions, etc. As described herein, in various embodiments, the terms “computer-readable instructions” and “computer-executable instructions” are used to describe software instructions or computer code configured to carry out various tasks and operations. In various embodiments, if the computer-readable or computer-executable instructions form modules, the term “module” refers broadly to a collection of software instructions or code configured to cause the control circuit 8015 to perform one or more functional tasks. The modules and computer- readable / executable instructions may be described as performing various operations or tasks when the control circuit 8015 or other hardware component is executing the modules or computer-readable instructions.

[0228] The instructions 8030 may be executed in logically or virtually separate threads on the control circuit 8015. For example, the non-transitory computer-readable medium 8020 may store instructions 8030 that when executed by the control circuit 8015 cause the control circuit 8015 to perform any of the operations, methods and / or processes described herein. In some cases, the non-transitory computer-readable medium 8020 may store computer-executable instructions or computer-readable instructions, such as instructions to perform at least a portion of the processes and methods of FIGS. 7 and 8A-B.

[0229] The user device 8005 may include one or more communication interfaces 8035. The communication interfaces 8035 may be used to communicate with one or more other systems. The communication interfaces 8035 may include any circuits, components, software, etc. for communicating via one or more networks (e.g., networks 9050). In some implementations, the communication interfaces 8035 may include for example, one or more of a communications controller, receiver, transceiver, transmitter, port, conductors, software and / or hardware for communicating data / information.

[0230] The user device 8005 may also include one or more user input components 840 that receives user input. For example, the user input component 8040 may be a touch-sensitive component (e.g., a touch-sensitive display screen or a touch pad) that is sensitive to the touch of a user input object (e.g., a finger or a stylus). The touch-sensitive component may serve to implement a virtual keyboard. Other example user input components include a microphone, a traditional keyboard, cursor-device, joystick, or other devices by which a user may provide user input.

[0231] The user device 8005 may include one or more output components 8045. The output components 8045 may include hardware and / or software for audibly or visually producing content. For instance, the output components 8045 may include one or more speakers, earpieces, headsets, handsets, etc. The output components 8045 may include a display device, which may include hardware for displaying a user interface and / or messages for a user. By way of example, the output component 8045 may include a display screen, CRT, LCD, plasma screen, touch screen, TV, projector, tablet, and / or other suitable display components.

[0232] The one or more networks 9050 may be any type of communications network, such as a local area network (e.g., intranet), wide area network (e.g., Internet), or some combination thereof and may include any number of wired or wireless links. In general, communication over a network 9050 may be carried via any type of wired and / or wireless connection, using a wide variety of communication protocols (e.g., TCP / IP, HTTP, SMTP, FTP), encodings or formats (e.g., HTML, XML), and / or protection schemes (e.g., VPN, secure HTTP, SSL).Additional Discussion of Various Embodiments

[0233] Embodiment 1 relates to a computing system. The computing system includes a control circuit configured to: access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, thecontrolled environment including a location where the vehicle is in a known state and has a known network connectivity; determine, based on the vehicle identifier, that content is available for the vehicle; initiate the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determine a data payload for download to the vehicle while the vehicle is within the controlled environment; initiate the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

[0234] Embodiment 2 includes the computing system of Embodiment 1. In this embodiment, the control circuit is further configured to: access user input data indicative of a response to the message indicating the content is available for the vehicle, wherein the user input data is based on user input, to the client computing device, from a user associated with the controlled environment.

[0235] Embodiment 3 includes the computing system of any of Embodiments 1 or 2. In this embodiment, the content includes a software update, and the user input data is indicative of an additional software update to be downloaded to the vehicle, and wherein the data payload includes the software update and the additional software update to be downloaded to the vehicle while the vehicle is in the controlled environment.

[0236] Embodiment 4 includes the computing system of any of Embodiments 1-3. In this embodiment, the user input data is indicative of a confirmation by the user of the content.

[0237] Embodiment 5 includes the computing system of any of Embodiments 1-4. In this embodiment, the control circuit is further configured to: initiate, for delivery to the client computing device associated with the controlled environment, the output of data indicating one or more actions for the user to facilitate the download of the data payload to the vehicle while the vehicle is within the controlled environment.

[0238] Embodiment 6 includes the computing system of any of Embodiments 1-5. In this embodiment, the data indicating the one or more actions for the user includes instructions to assist the user with one or more manual steps during download of the data payload to the vehicle.

[0239] Embodiment 7 includes the computing system of any of Embodiments 1-6. In this embodiment, the control circuit is further configured to: access data indicative of a status of thedata payload; and initiate, for delivery to the client computing device associated with the controlled environment, the output of data indicating the status of the data payload.

[0240] Embodiment 8 includes the computing system of any of Embodiments 1-7. In this embodiment, the data payload includes one or more software updates, and wherein the status of the data payload is indicative of a progress in downloading each respective software update to the vehicle.

[0241] Embodiment 9 includes the computing system of any of Embodiments 1-8. In this embodiment, the computing system is configured to communicate with the client computing device via one or more APIs.

[0242] Embodiment 10 includes the computing system of any of Embodiments 1 -8. In this embodiment, the control circuit is further configured to: determine, based on the time that the vehicle is estimated to be at the location, that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment rather than while the vehicle is within an uncontrolled environment where the state of the vehicle and the network connectivity of the vehicle is unknown or dynamically changes.

[0243] Embodiment 11 includes the computing system of any of Embodiments 1 -10. In this embodiment, the control circuit is configured to determine that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment based on at least one of: (1) a priority of the content, (2) a size of the content, or (3) a type of the content.

[0244] Embodiment 12 includes the computing system of any of Embodiments 1 -11. In this embodiment, the vehicle is travelling within an uncontrolled environment.

[0245] Embodiment 13 includes the computing system of any of Embodiments 1-12. In this embodiment, the controlled environment includes a microcell for the vehicle to download the data payload.

[0246] Embodiment 14 includes the computing system of any of Embodiments 1-13. In this embodiment, the control circuit is further configured to: access data indicative of a type of the controlled environment.

[0247] Embodiment 15 includes the computing system of any of Embodiments 1-14. In this embodiment, the type of controlled environment includes an automotive service location and wherein the user associated with the controlled environment is a technician at the automotive service location.

[0248] Embodiment 16 includes the computing system of any of Embodiments 1 -15. In this embodiment, the content includes at least one of: (i) a software package, (ii) media content; or (iii) other digital content.

[0249] Embodiment 17 relates to a computer-implemented method. The method includes: accessing data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment including a location where the vehicle is in a known state and has a known network connectivity; determining, based on the vehicle identifier, that content is available for the vehicle; initiating the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determining a data payload for download to the vehicle while the vehicle is within the controlled environment; initiating the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiating the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

[0250] Embodiment 18 includes the computer-implemented method of Embodiment 17. In this embodiment, the computer-implemented method further includes: accessing user input data indicative of a response to the message indicating the content is available for the vehicle, wherein the user input data is based on user input, to the client computing device, from a user associated with the controlled environment.

[0251] Embodiment 19 includes the computer-implemented method of any of Embodiments 17-8. In this embodiment, the computer-implemented method further includes: determining, based on the time that the vehicle is estimated to be at the location, that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment rather than while the vehicle is within an uncontrolled environment where the state of the vehicle and the network connectivity of the vehicle is unknown or dynamically changes.

[0252] Embodiment 30 relates to one or more non-transitory computer-readable media that store instructions that are executable by a control circuit to: access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment including a location where the vehicle is in a known state and has a known network connectivity; determine, based on the vehicle identifier, that content is available for the vehicle; initiating the output of, for delivery to a client computingdevice associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determine a data payload for download to the vehicle while the vehicle is within the controlled environment; initiate the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.Additional Disclosure

[0253] As used herein, adjectives and their possessive forms are intended to be used interchangeably unless apparent otherwise from the context and / or expressly indicated. For instance, “component of a / the vehicle” may be used interchangeably with “vehicle component” where appropriate. Similarly, words, phrases, and other disclosure herein is intended to cover obvious variants and synonyms even if such variants and synonyms are not explicitly listed.

[0254] Computing tasks and operations discussed herein as being performed at or by computing device(s) remote from the vehicle can instead be performed at the vehicle (e.g., via the vehicle computing system), or vice versa.

[0255] The technology discussed herein makes reference to servers, databases, software applications, and other computer-based systems, as well as actions taken and information sent to and from such systems. The inherent flexibility of computer-based systems allows for a great variety of possible configurations, combinations, and divisions of tasks and functionality between and among components. For instance, processes discussed herein may be implemented using a single device or component or multiple devices or components working in combination. Databases and applications may be implemented on a single system or distributed across multiple systems. Distributed components may operate sequentially or in parallel.

[0256] While the present subject matter has been described in detail with respect to various specific example embodiments thereof, each example is provided by way of explanation, not limitation of the disclosure. Those skilled in the art, upon attaining an understanding of the foregoing, may readily produce alterations to, variations of, and equivalents to such embodiments. Accordingly, the subject disclosure does not preclude inclusion of such modifications, variations and / or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art. For instance, features illustrated or described as partof one embodiment may be used with another embodiment to yield a still further embodiment. Thus, it is intended that the present disclosure cover such alterations, variations, and equivalents.

[0257] Aspects of the disclosure have been described in terms of illustrative implementations thereof. Numerous other implementations, modifications, or variations within the scope and spirit of the appended claims may occur to persons of ordinary skill in the art from a review of this disclosure. Any and all features in the following claims may be combined or rearranged in any way possible. Accordingly, the scope of the present disclosure is by way of example rather than by way of limitation, and the subject disclosure does not preclude inclusion of such modifications, variations or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art. Moreover, terms are described herein using lists of example elements joined by conjunctions such as “and,” “or,” “but,” etc. It should be understood that such conjunctions are provided for explanatory purposes only. The term “or” and “and / or” may be used interchangeably herein. Lists joined by a particular conjunction such as “or,” for example, may refer to “at least one of’ or “any combination of’ example elements listed therein, with “or” being understood as “and / or” unless otherwise indicated. Also, terms such as “based on” should be understood as “based at least in part on.”

[0258] Those of ordinary skill in the art, using the disclosures provided herein, will understand that the elements of any of the claims, operations, or processes discussed herein may be adapted, rearranged, expanded, omitted, combined, or modified in various ways without deviating from the scope of the present disclosure. At times, elements may be listed in the specification or claims using a letter reference for exemplary illustrated purposes and is not meant to be limiting. Letter references, if used, do not imply a particular order of operations or a particular importance of the listed elements. For instance, letter identifiers such as (a), (b), (c), . . . , (i), (ii), (iii), . . . , etc. may be used to illustrate operations or different elements in a list. Such identifiers are provided for the ease of the reader and do not denote a particular order, importance, or priority of steps, operations, or elements. For instance, an operation illustrated by a list identifier of (a), (i), etc. may be performed before, after, or in parallel with another operation illustrated by a list identifier of (b), (ii), etc.

Claims

WHAT IS CLAIMED IS:

1. A computing system comprising: a control circuit configured to: access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment comprising a location where the vehicle is in a known state and has a known network connectivity; determine, based on the vehicle identifier, that content is available for the vehicle; initiate the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determine a data payload for download to the vehicle while the vehicle is within the controlled environment; initiate the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

2. The computing system of claim 1, wherein the control circuit is further configured to: access user input data indicative of a response to the message indicating the content is available for the vehicle, wherein the user input data is based on user input, to the client computing device, from a user associated with the controlled environment.

3. The computing system of claim 2, wherein the content comprises a software update, and the user input data is indicative of an additional software update to be downloaded to the vehicle, and wherein the data payload comprises the software update and the additional software update to be downloaded to the vehicle while the vehicle is in the controlled environment.

4. The computing system of any of claims 1 to 3, wherein the user input data is indicative of a confirmation by the user of the content.

5. The computing system of any of claims 1 to 4, wherein the control circuit is further configured to: initiate, for delivery to the client computing device associated with the controlled environment, the output of data indicating one or more actions for the user to facilitate the download of the data payload to the vehicle while the vehicle is within the controlled environment.

6. The computing system of claim 5, wherein the data indicating the one or more actions for the user comprises instructions to assist the user with one or more manual steps during download of the data payload to the vehicle.

7. The computing system of any of claims 1 to 6, wherein the control circuit is further configured to: access data indicative of a status of the data pay load; and initiate, for delivery to the client computing device associated with the controlled environment, the output of data indicating the status of the data payload.

8. The computing system of claim 7, wherein the data payload comprises one or more software updates, and wherein the status of the data payload is indicative of a progress in downloading each respective software update to the vehicle.

9. The computing system of any of claims 1 to 8, wherein the computing system is configured to communicate with the client computing device via one or more APIs.

10. The computing system of any of claims 1 to 9, wherein the control circuit is further configured to: determine, based on the time that the vehicle is estimated to be at the location, that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment rather than while the vehicle is within an uncontrolled environment where the state of the vehicle and the network connectivity of the vehicle is unknown or dynamically changes.

11. The computing system of claim 10, wherein the control circuit is configured to determine that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment based on at least one of: (1) a priority of the content, (2) a size of the content, or (3) a type of the content.

12. The computing system of any of claims 1 to 11, wherein the vehicle is travelling within an uncontrolled environment.

13. The computing system of any of claims 1 to 12, wherein the controlled environment comprises a microcell for the vehicle to download the data payload.

14. The computing system of any of claims 1 to 13, wherein the control circuit is further configured to: access data indicative of a type of the controlled environment.

15. The computing system of claim 14, wherein the type of controlled environment comprises an automotive service location and wherein the user associated with the controlled environment is a technician at the automotive service location.

16. The computing system of any of claims 1 to 15, wherein the content comprises at least one of: (i) a software package, (ii) media content; or (iii) other digital content.

17. A computer-implemented method comprising: accessing data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment comprising a location where the vehicle is in a known state and has a known network connectivity; determining, based on the vehicle identifier, that content is available for the vehicle; initiating the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determining a data payload for download to the vehicle while the vehicle is within the controlled environment;initiating the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiating the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

18. The computer-implemented method of claim 17, further comprising: accessing user input data indicative of a response to the message indicating the content is available for the vehicle, wherein the user input data is based on user input, to the client computing device, from a user associated with the controlled environment.

19. The computer-implemented method of any of claims 17 or 18, further comprising: determining, based on the time that the vehicle is estimated to be at the location, that the content is to be provided for download to the vehicle while the vehicle is within the controlled environment rather than while the vehicle is within an uncontrolled environment where the state of the vehicle and the network connectivity of the vehicle is unknown or dynamically changes.

20. One or more non-transitory computer-readable media that store instructions that are executable by a control circuit to: access data indicative of a vehicle identifier associated with a vehicle and a time that the vehicle is estimated to be within a controlled environment, the controlled environment comprising a location where the vehicle is in a known state and has a known network connectivity; determine, based on the vehicle identifier, that content is available for the vehicle; initiating the output of, for delivery to a client computing device associated with the controlled environment, a message indicating the content is available for the vehicle; based on the content, determine a data payload for download to the vehicle while the vehicle is within the controlled environment; initiate the output of the data payload to a local computing infrastructure associated with the controlled environment; and initiate the output of instructions for routing the vehicle to the controlled environment where the data payload is available for download via the local computing infrastructure.

Citation Information

Patent Citations

  • Method for upgrading vehicle software and related system

    EP4116817A1

  • Vehicle software deployment system

    WO2021133416A1