JP2013186121A - Vehicle network connectivity management system and method - Google Patents

Abstract

To improve connectivity of a vehicle network.
A network connectivity management method for determining a network to be connected in a vehicle system, including vehicle data indicating a current position of the vehicle and a destination of the vehicle from a vehicle to a connectivity management server. Sending a network data request; receiving network data associated with one or more networks from the connectivity management server; caching network data; and based on the network data, Determining whether to connect to the other network.
[Selection] Figure 5A

Description

  The present description relates to a vehicle networking system. In particular, the specification relates to systems and methods for managing vehicle network connectivity.

  Wireless communication methods such as 3G / Long Term Evolution (3G / LTE), WiFi, and satellite communication are currently rapidly used for applications related to vehicles such as in-car internet radio, streaming, mobile phones, and optional network-based services. Is being deployed. By using these, the user experience of the driver and passengers can be improved. However, disruption of these services can dramatically reduce the quality of the driver and passenger user experience. Although the coverage of wireless networks is being improved, most are in densely populated areas, and in suburbs where population density is low, wireless signals can usually be weak or unavailable. Therefore, vehicles operating in such areas may suffer from reduced or interrupted network connectivity. Since the conventional navigation system (Patent Document 1) performs route guidance without considering network connectivity, the network service may be interrupted on the guidance route.

  Conversely, there may be a case where a plurality of network services are available depending on the location. In such a case, conventionally, a connection destination network is generally determined with a predetermined priority, or a network with high received power is generally determined as a connection destination (Patent Document 2). However, since which network should be connected depends on various conditions, such a determination method cannot always improve the quality of the user experience of the driver and passengers.

JP2012-063260A JP 2009-225011 A

  The objective of this invention is providing the technique for improving the connectivity of a vehicle network.

  The present specification overcomes the shortcomings and limitations of the prior art, at least in part, by providing a system and method for determining a network. The system includes a request module and a determination module. The request module acquires network data about a network provided in the vicinity of the planned travel route of the vehicle. The determination module determines which network to connect to based on the network data.

  In one embodiment, the request includes vehicle data describing the current location of the vehicle, the destination of the vehicle, and the travel route to the destination.

In one embodiment, the network data includes the coverage area of one or more networks, the network connection history of the vehicle, the current congestion status of the one or more networks, and the network to which to connect. It describes the rules that describe how to decide. Further, in one embodiment, the network data includes connectivity data indicating a data usage amount that the vehicle has communicated with using the target network in the past, a data usage date and time when the communication is performed, and a communication provider that provides the service. Includes logs.

  In one embodiment, the determination module determines an available network for the vehicle based on the network data, and based on a data usage contract between the network data and a carrier. A rank of an available network is generated, the rank of the available network is adjusted based on an application requirement, and the network to be connected to which of the available networks is connected. And a rule indicating how the vehicle included in the network data determines a connection destination network.

  By determining the network to connect to in this way, it is possible to decide to use an appropriate network based on the data usage contract with the communication carrier, application requirements, etc. Therefore, the driver and passengers Improve the user experience.

  In one embodiment, based on the network data, the network connection is detected to be interrupted or interrupted, and when the network connection is detected to be interrupted, the network connection is provided based on the network data. A navigation module that calculates a travel route to be performed and navigates the vehicle according to the calculated travel route.

  According to such a configuration, when it is predicted that the vehicle is traveling on a route having no network connection or a vehicle is traveling on a route having no network connection, the route on which the network connection is provided Navigation is possible. Since the driver and passengers of the vehicle can use the network connection while traveling, the user experience is improved.

Further, in one embodiment, based on the network data, a network connection interruption is predicted, and the interruption period is determined based on the network data.
A buffering module is further provided for buffering data obtained from the network in preparation for the interruption period.

  According to such a configuration, even when the network connection is interrupted, it is possible to continue providing the service by using the buffered data. This is effective, for example, when a moving image is played back with media data such as audio (music) data.

  According to the present invention, the connectivity of the vehicle network can be improved.

1 is a high-level block diagram illustrating a system for managing vehicle network connectivity according to one embodiment. FIG. FIG. 2 is a block diagram detailing a network management module according to one embodiment. FIG. 2 is a block diagram illustrating a storage device according to one embodiment. 6 is a flowchart illustrating a method for determining a network according to one embodiment. 6 is a flowchart illustrating a method for determining a network according to another embodiment. 6 is a flowchart illustrating a method for determining a network according to another embodiment. 6 is a flowchart illustrating a method for navigating a vehicle based on network coverage information according to one embodiment. 6 is a flowchart illustrating a method for buffering media data in response to a network interruption, according to one embodiment.

  This specification is shown for purposes of illustration and not limitation in the accompanying drawings, wherein like reference numerals are used to refer to like elements.

  Systems and methods for managing vehicle network connectivity are described below. In the following description, numerous details are set forth to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that each embodiment may be without these specific details. In addition, in order to avoid obscuring the description, the structure and the device may be represented in the form of a block diagram. For example, one embodiment is described with a user interface and specific hardware. However, the description herein is applicable to any type of computing device and any peripheral device that receives data and commands.

  In this specification, the terms “one embodiment”, “an embodiment,” and the like indicate that a particular feature, structure, or property described in association with the embodiment is included in at least one embodiment of the present invention. means. A plurality of terms such as “in one embodiment” are used in the present specification, but these do not necessarily indicate the same embodiment.

  Some portions of the detailed descriptions that follow are provided as algorithms and symbolic representations of operations on data bits stored in non-transitory computer-readable storage media. These algorithmic descriptions and representations are used by those skilled in the data processing arts to most effectively describe the nature of their work to others skilled in the art. In this specification (and generally), an algorithm means a logical procedure for obtaining a desired result. The processing step is to physically manipulate the physical quantity. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise processed. It is convenient to refer to these signals as bits, values, elements, elements, symbols, characters, terms, numbers, etc.

  It should be noted that both these terms and similar terms are associated with appropriate physical quantities and are merely simple labels for these physical quantities. As will be apparent from the following description, unless otherwise specified, descriptions using terms such as “processing”, “calculation”, “computer calculation (processing)”, “judgment”, and “display” in this specification are computer systems and Operation and processing of similar electronic computing devices, including physical (electronic) quantities in computer system registers and memories, physical quantities in other memory and registers or similar information storage, communication devices, and display devices Operations and processes that manipulate and transform other data represented as.

The present invention also relates to an apparatus for performing the operations described herein. This device may be specially manufactured for the required purposes, or it may be constructed using a general purpose computer and selectively executed or reconfigured by a program stored in the computer It may be. Such a computer program can be connected to a computer system bus, for example, any type of disk such as a floppy disk, optical disk, CD-ROM, MO disk, magnetic disk, read-only memory (ROM), random Stored in a non-transitory computer readable storage medium, such as access memory (RAM), EPROM, EEPROM, magnetic card, flash memory, optical card, any type of medium suitable for storing electronic instructions .

  A specific embodiment of the invention may be realized entirely by hardware, may be realized entirely by software, or may be realized by both hardware and software. The preferred embodiment is implemented by software. Here, the software includes firmware, resident software, microcode, and other software.

  Further, some embodiments take the form of a computer program product accessible from a computer-usable or readable storage medium. This storage medium provides program code used by or in conjunction with a computer or any instruction execution system. A computer-usable or readable storage medium refers to any device capable of holding, storing, communicating, propagating and transferring a program used by or together with an instruction execution system or device.

  A data processing system suitable for storing and executing program code includes at least one processor connected directly or indirectly to storage elements through a system bus. The storage device temporarily stores several program codes to reduce the number of times data is acquired from the local memory, the mass storage device, and the mass storage device during execution. Including cache memory.

  Input / output (I / O) devices are, for example, keyboards, displays, pointing devices, etc., which are connected to the system directly or indirectly via an I / O controller.

  A network adapter is also connected to the system, thereby connecting to another data processing system or a remote printer or storage device via a private network or public network. Modems, cable modems, and Ethernet are just a few examples of currently available network adapters.

  Finally, the algorithms and displays presented herein are not inherently related to a particular computer or other device. Various general purpose systems having programs in accordance with the description herein may be used, and it may be appropriate to produce a special purpose device for performing the required processing steps. The required structure for these various systems will be apparent from the description below. In addition, the present invention is not associated with any particular programming language. It will be apparent that various programming languages may be utilized to implement the subject matter described herein.

System Overview FIG. 1 shows a block diagram of a system 100 for managing network connectivity of a vehicle according to one embodiment. The exemplary system 100 includes a vehicle system 101 accessed by a user 125, a connectivity server 141, an account server 171, and a unified cloud database 150. In the illustrated embodiment, the vehicle system 101, the connectivity server 141, and the unified cloud database 150 are communicatively connected through the network 105. For example, the vehicle system 101 and the connectivity server 141 are communicably connected to each other through the network 105 in order to facilitate transmission / reception of information (for example, network data and connectivity data) between them. The account server 171 is communicably connected to the connectivity server 141.

  Although only one vehicle system 101, one connectivity server 141, one account server 171 and one unified cloud database 150 are shown in FIG. It can be seen that a number of vehicle systems 101, connectivity servers 141, account servers 171, and unified cloud database 150 may be included. Further, only one network 105 is connected to the vehicle system 101, the connectivity server 141, and the unified cloud database 150. It can be seen that any number of networks 105 may be connected.

  Network 105 is of a conventional type, wired or wireless, and may include any number of configurations, such as a star configuration, a token ring configuration, or other configurations known to those skilled in the art. Further, network 105 may include a local area network (LAN), a wide area network (WAN) (eg, the Internet), and / or any other interconnected data path through which multiple devices communicate. In yet another embodiment, the network 105 may be a peer to peer network. Network 105 may be coupled to a telecommunications network or may include parts of a telecommunications network for transmitting data over a wide variety of communication protocols. For example, the network 105 is a 3G / LTE network, a 4G network, a WiFi network, or a WiMAX network. In another embodiment, the network 105 receives data via short messaging service (SMS), multimedia messaging service (MMS), hypertext transfer protocol (HTTP), direct data connection, WAP, e-mail, etc. For transmission and reception, a Bluetooth (registered trademark) communication network or a cellular communication network is included. In yet another embodiment, all or part of the links in network 105 use conventional encryption techniques such as secure socket layer (SSL), secure HTTP, and / or virtual private network (VPN). Encrypted.

  In one embodiment, the network 105 is a vehicle ad hoc network (VANET) that uses moving vehicles as nodes. The network 105 is a mobile network in which there are cars that drop out of the communication range and leave the network, while some cars enter.

  In the illustrated embodiment, connectivity server 141 is communicatively connected to network 105 through signal line 107 and signal line 109 (in a wireless manner). The account server 171 is communicably connected to the connectivity server 141 through the signal line 117. The vehicle system 101 is communicably connected to the network 105 through a signal line 115 (in a wireless manner). The user 125 interacts with the vehicle system 101 as represented by the signal line 123. The unified cloud database 150 is communicably connected to the network 105 through the signal line 111 and the signal line 113 (in a wireless manner).

  The connectivity server 141 is one or more devices having at least one processor coupled to at least one storage device (storage device) that contains instructions to be executed by the processor. For example, the connectivity server 141 is a conventional server, server array, or other one or group of computing devices having data processing and communication capabilities. In one embodiment, connectivity server 141 is a hardware server device operated by an entity.

  The connectivity server 141 includes, among other things, a data supply module 142, a connectivity database 144, and an account log database 175. The account log database 175 is drawn with a dashed line to indicate that it is an optional element of the connectivity server 141. Therefore, in one embodiment, the account log database 175 is included in the account server 171 and not included in the connectivity server 141. The connectivity server 141 can access the account log database 175 through the account server 171.

  The connectivity server 141 further includes a processor (not shown in FIG. 1), a memory (not shown in FIG. 1), and other components (such as firewalls and network cards) that are conventional in server devices. The components of the connectivity server 141 are connected so as to communicate with each other.

  In one embodiment, the components of the illustrated connectivity server 141 are implemented as a single piece of software or hardware, or as multiple pieces of software or hardware. In general, functionality described in one embodiment as being performed by one component may be performed by other components in other embodiments, or by a combination of components. Further, the functionality described in one embodiment as being performed by a component of connectivity server 141 is performed by account server 171 in other embodiments, if appropriate. In one embodiment, the functionality belonging to a particular component is implemented by different components or by multiple components cooperating.

  The various modules on the connectivity server 141 are each on a server class computer that includes one or more central processing units (CPUs), memory, network interfaces, peripheral interfaces, and other well-known components. It is implemented as a server program executed in. In one embodiment, the computer itself is on an open source operating system such as LINUX®, which has one or more CPUs, 1 gigabyte or more memory, and 100 gigabytes or more disk storage. Works with. In one embodiment, other types of computers are used, and such computers may be configured in accordance with the teachings disclosed herein as more powerful computers are developed in the future. Is expected. In another embodiment, the functionality implemented by any element may include one or more tangible and non-transitory computer readable storage media (eg, random access memory (RAM), flash solid state drive (SSD), Provided by computer program products stored on hard disk drives, optical / magnetic media, etc.

  The data supply module 142 is code and routines that, when executed by a processor (not shown), process requests for network data and supply network data to the vehicle system 101. For example, the data supply module 142 receives a request for network data from the vehicle system 101 and retrieves network data from the connectivity database 144 and the account log database 175 based at least in part on the request and through the network 105. The network data is transmitted to the vehicle system 101.

The network data includes coverage data, account data, congestion status data, and connectivity rule / policy data. The coverage data describes network coverage information such as 3G / LTE / 4G coverage map, WiFi / WiMAX hotspot information, and satellite map for each carrier candidate. The account data is a log of network connectivity information for each vehicle. For example, the account data includes a connectivity data log for each vehicle, and each entry of the log includes data usage, data It describes the date of use, data usage time, and the carrier that provides the service. The congestion status data describes how congested the network is, for example, whether the network is congested. The connectivity rule / policy data indicates rules and policies for selecting a network suitable for the vehicle. For example, the connectivity rule / policy data includes carrier priority (for example, telephone carrier A has a higher priority than telephone carrier B), wireless technology priority (for example, 3G is WiFi). , LTE, and WiMAX, WiFi is a higher rank than LTE and WiMAX, LTE is a higher rank than WiMAX), and network priority for various data types The ranking is described (for example, 3G has the highest priority in the case of safety data, and WiFi has the highest priority in the case of movie data).

  In one embodiment, the data supply module 142 receives a request from the vehicle system 101 when the user 125 enters a new destination for the vehicle or when the vehicle system 101 estimates a new destination for the vehicle. . The request received from the vehicle system 101 includes vehicle data. The vehicle data describes information related to the vehicle. For example, the vehicle data includes location data, destination data, and travel route data. The location data describes the current location of the vehicle. The destination data indicates the destination of the vehicle. The travel route data describes an expected travel route to the destination. In one embodiment, the vehicle data also includes vehicle speed data describing the average vehicle speed.

  The data supply module 142 uses the vehicle data to retrieve and discover network data from the connectivity database 144 and / or the account log database 175. For example, the discovered network data includes coverage data that describes one or more network coverage maps for the area along the expected travel route to the destination. In one embodiment, the data supply module 142 accesses the account log database 175 through the account server 171. When the requested network data is found, the data supply module 142 transmits the network data to the vehicle system 101 through the network 105.

  In one embodiment, the data supply module 142 receives a connectivity data log from the vehicle system 101. The connectivity data log is initially maintained in the vehicle system 101. For example, the connectivity data log includes a plurality of entries, each entry describing connectivity data for a vehicle that describes data usage, data usage date, data usage time, and service provider providing the service. including. Upon receipt of the connectivity data log, the data supply module 142 authenticates and analyzes each carrier's activity based at least in part on the connectivity data log. In one embodiment, the data supply module 142 stores the connectivity data log in the account log database 175. In another embodiment, the data supply module 142 transmits the connectivity data log to the account server 171 for storage in an account log database 175 included in the account server 171.

The connectivity database 144 is a storage system that stores data and / or information related to network connectivity. For example, the connectivity database 144 stores coverage data, congestion status data, and connectivity rule / policy data. As described above with reference to the data supply module 142, the coverage data includes network coverage information, such as 3G / LTE / 4G coverage maps, WiFi / WiMAX hotspot information, and satellite maps, for each carrier candidate. It is described. The congestion status data describes how congested the network is. The connectivity rule / policy data indicates rules and policies for selecting a network suitable for the vehicle. In one embodiment, the connectivity database 144 also stores account data.

  The account log database 175 is a storage system that stores connectivity data logs transmitted from the vehicle system 101. For example, the connectivity data log is stored in time series and is classified by vehicle identifier for each vehicle. Each connectivity data log includes connectivity data describing a data usage amount, a data usage date, a data usage time, and a communication provider that provides a service for each vehicle. In one embodiment, the account log database 175 is an element of the account server 171.

  Account server 171 is one or more devices having at least one processor coupled to at least one storage device containing instructions to be executed by the processor. For example, account server 171 is a conventional server, server array, or other one or group of computing devices having data processing and communication capabilities. In one embodiment, account server 171 is a hardware server device operated by an entity.

  The account server 171 is communicably connected to the connectivity server 141 through the signal line 117. In one embodiment, the account server 171 includes an account log database 175. The account server 171 communicates with the connectivity server 141 in order to send data stored in the account log database 175 to the connectivity server 141. For example, when the vehicle system 101 requests network data, the account server 171 retrieves account data (for example, connectivity data log) from the account log database 175 and transmits the account data to the vehicle system 101 through the connectivity server 141.

  The vehicle system 101 is a system incorporated in a vehicle. For example, the vehicle is a passenger car. In one embodiment, the vehicle system 101 transmits and receives data to and from the connectivity server 141 through the network 105. For example, the vehicle system 101 transmits a request for network data to the connectivity server 141 and receives network data from the connectivity server 141.

  The vehicle system 101 includes a communication unit 102, a control unit 103 including a processor 112, a network management module 114, a navigation module 116, and a buffering module 118, a sensor 122, a camera 124, an interface 120, and a storage device 104. including. Although only one sensor 122, one camera 124, one control unit 103, one communication unit 102, one interface 120, and one storage device 104 are shown in FIG. It can be seen that the vehicle system 101 may include any number of sensors 122, cameras 124, a control unit 103, a communication unit 102, a storage device 104, and an interface 120. Further, those skilled in the art will appreciate that the vehicle system 101 may include other entities not shown in FIG. 1, such as speakers, display devices, input devices, and the like.

The communication unit 102 is communicably connected to the control unit 103 through the signal line 131. The sensor 122 is communicably connected to the control unit 103 through the signal line 127. The camera 124 is communicably connected to the control unit 103 through a signal line 129. The storage device 104 is communicably connected to the control unit 103 through the signal line 133. The interface 120 is communicably connected to the control unit 103 through the signal line 121. User 125 interacts with interface 120 as represented by signal line 123.

  The communication unit 102 is any computing device that transmits and receives signals. For example, the communication unit 102 includes a dedicated short range communication (DSRC) device. In one embodiment, the communication unit 102 is implemented using hardware such as a field programmable gate array (FPGA) or special purpose integrated circuit (ASIC). In another embodiment, the communication unit 102 is implemented using a combination of hardware and software. In one embodiment, the communication unit 102 includes an antenna. An antenna is an electrical device that converts current and radio waves. For example, the antenna is a movable beam directivity antenna.

  In one embodiment, the communication unit 102 is responsible for communication with the connectivity server 141 over the network 105. For example, the communication unit 102 receives a request for network data from the control unit 103 and sends it to the connectivity server 141. In another example, the communication unit 102 receives network data from the connectivity server 141 and sends it to the control unit 103.

  The control unit 103 is any processor device based on a processor. For example, the control unit 103 is an electronic control unit (ECU) mounted on the vehicle. In one embodiment, the control unit 103 is implemented using a single integrated circuit, such as a system on chip (SOC). In one embodiment, the control unit 103 generates vehicle data based at least in part on input from the user 125. For example, when the user 125 as a driver inputs a destination, the control unit 103 detects the current location of the vehicle and calculates an expected travel route to the destination. The control unit 103 then generates vehicle data describing the current location, the destination, and the expected travel route. The control unit 103 stores the vehicle data in the storage device 104. In another embodiment, control unit 103 generates vehicle data based at least in part on one or more images from camera 124 and one or more sensor signals from sensor 122. . For example, the control unit 103 receives a sensor signal describing the vehicle speed periodically at specific time intervals. The control unit 103 processes the sensor signal and generates vehicle data indicating the average vehicle speed.

  The control unit 103 includes, among other things, a processor 112, a network management module 114, a navigation module 116, and a buffering module 118. In another embodiment, the control unit 103 includes other components conventionally in the control unit, such as a memory (not shown) and an input / output interface (not shown).

  The processor 112 includes an arithmetic logic unit, a microprocessor, a general purpose controller, or some other processor array for performing calculations, retrieving data stored in the storage device 104, and the like. The processor 112 is for processing data signals and has various computing architectures such as a complex instruction set computer (CISC) architecture, a reduced instruction set computer (RISC) architecture, or an architecture that executes a combination of instruction sets. Can be included. In FIG. 1, only one processor 112 is shown, but a plurality of processors 112 may be included. The processing capability of the processor 112 may be limited to supporting only signal display and signal transmission / reception. The processing power of the processor 112 may be sufficient to perform more complex tasks such as various types of feature extraction and feature sampling. Those skilled in the art will appreciate that other processors, operating systems, sensors, displays, and physical configurations are possible.

  The network management module 114 is code and routines for managing vehicle network connectivity. For example, the network management module 114 requests network data from the connectivity server 141 based at least in part on vehicle data. The network management module 114 receives network data and determines suitable network connectivity for the vehicle based at least in part on the network data. In one embodiment, the network management module 114 caches network data and stores it in the storage device 104. In another embodiment, the network management module 114 sends a suitable network connectivity determination to the navigation module 116 to navigate the vehicle based on the preferred network connectivity. The network management module 114 will be described in more detail later with reference to FIG.

  The navigation module 116 is a code and routine for calculating a travel route suitable for the vehicle. For example, the navigation module 116 receives a determination of suitable network connectivity from the network management module 114. Based on the determination of the preferred network connectivity, the navigation module 116 calculates a preferred travel route toward the vehicle destination. For example, a suitable travel route has suitable network connectivity.

  In one embodiment, the navigation module 116 detects a network interruption and then retrieves network data from the storage device 104. The navigation module 116 uses the network data to determine one or more network coverage areas and notifies the user 125 of the one or more network coverage areas. The navigation module 116 also calculates one or more travel routes with suitable network coverage based on the network data. After the user 125 such as a driver selects a travel route, the navigation module 116 navigates the vehicle to the destination based on the travel route. In another embodiment, the navigation module 116 notifies the user 125 of the closest network coverage area in advance or later when it detects a network interruption. The navigation module 116 navigates the vehicle to the nearest network coverage area based on the agreement of the user 125.

  The buffering module 118 is code and routines for buffering or prefetching content data in the event of a network interruption. In one embodiment, the buffering module 118 retrieves network data from the storage device 104 and pre-determines whether there is a network interruption based at least in part on the network data. If it is determined in advance that there is a network interruption, the buffering module 118 buffers the content data. In another embodiment, the buffering module 118 also predicts the start time and length of the interruption period of the network interruption based at least in part on the network data. The buffering module 118 then buffers the content data in preparation for the interruption period.

For example, the buffering module 118 predicts a network interruption based on coverage information for an area along the travel route. Based on the coverage information, the buffering module 118 determines the location and length of the portion of the travel route that does not involve network coverage. The buffering module 118 then calculates the start time and length of the interruption period based on the location and length of the portion without network coverage and the average vehicle speed. The buffering module 118 then buffers content data (such as media data) in preparation for an expected network interruption. For example, suppose that when the passenger 125 is watching a video in the car, the buffering module 118 predicts a network interruption that starts 3 minutes and lasts 3 minutes. Buffering module 118 buffers video content in preparation for anticipated network interruptions. In this way, a long-time media file can be played back consistently in the car, or automatically resumed when playback stops.

  The sensor 122 is any type of conventional sensor configured to collect any type of data. For example, the sensor 122 is one of a laser light detection and ranging (LIDAR) sensor, an infrared detector, a motion sensor, a thermostat, and an acoustic detector. One skilled in the art will recognize that other types of sensors are possible. In one embodiment, sensor 122 measures conditions related to the vehicle. The sensor 122 generates a sensor signal describing a condition based on the measurement result. For example, the sensor 122 measures the vehicle speed and generates a sensor signal describing the vehicle speed. In another embodiment, the sensor 122 measures a condition in an environment outside the vehicle and generates a sensor signal describing the measurement result. The sensor 122 transmits a sensor signal to the control unit 103. In one embodiment, the vehicle system 101 includes a combination of different types of sensors 122.

  The camera 124 is drawn with dashed lines to show that it is an optional element of the vehicle system 101. Accordingly, in one embodiment, the vehicle system 101 does not include a camera 124.

  The camera 124 is an optical device for recording an image. For example, the camera 124 takes pictures of roads outside the vehicle, traffic lights, vehicles, pedestrians crossing the road, and the like as the car runs on the road. In one embodiment, the camera 124 is configured to capture an image including a continuous frame describing the environment surrounding the road when the driver is driving a car on the road. The camera 124 transmits an image to the control unit 103.

  The interface 120 is a device configured to be responsible for communication between the user 125 and the control unit 103. For example, the interface 120 includes one or more of an in-vehicle touch screen for receiving input from the user 125 and a microphone for capturing voice input from the user 125. The interface 120 transmits input from the user 125 to the control unit 103. In one embodiment, interface 120 is configured to transmit the output from control unit 103 to user 125. For example, the interface 120 includes a display device for displaying network connectivity information and / or travel route information to the user 125. Those skilled in the art will appreciate that interface 120 may include other types of devices for providing the functionality described herein.

  The user 125 is a user who is a person. In one embodiment, user 125 is a driver driving a car on the road. In another embodiment, the user 125 is a passenger in a car. User 125 interacts with interface 120 or otherwise provides input to interface 120, which transmits and receives various types of data to and from control unit 103. For example, the interface 120 is a touch screen, and a user 125 provides input by touching a portion of the touch screen with a finger or stylus. In one embodiment, the user 125 inputs destination data to the control unit 103 through the interface 120.

The storage device 104 is a non-transitory memory that stores data. For example, the storage device 104 is a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory, or some other memory device known in the art. In one embodiment, the storage device 104 includes a hard disk drive, a floppy disk drive, a compact disk read only memory (CD-ROM) device, a digital versatile disk read only memory (DVD-ROM) device, a digital versatile disk. Non-volatile memory or similar, such as a disk random access memory (DVD-RAM) device, a rewritable digital versatile disk (DVD-RW) device, a flash memory device, or some other non-volatile storage device known in the art Permanent storage devices and media. The storage device 104 will be described in more detail later with reference to FIG.

  The unified cloud database 150 is an online database accessible from the network 105. For example, the unified cloud database 150 is a database in which data is stored on a plurality of virtual servers provided by a plurality of companies. In one embodiment, the unified cloud database 150 stores any data for providing the functionality of the system 100. In another embodiment, the unified cloud database 150 stores data received from multiple vehicle systems 101 and from the connectivity server 141.

Network management module 114
Reference is now made to FIG. 2, which shows the network management module 114 in more detail. FIG. 2 is a block diagram 200 illustrating the network management module 114 according to one embodiment. The network management module 114 includes a communication module 201, a request module 203, a determination module 205, a logging module 207, and a graphical user interface (GUI) module 211. These components of the network management module 114 are communicatively connected to the bus 220 for communication with each other.

  In the exemplary embodiment, communication module 201 is communicatively connected to bus 220 through signal line 222. The request module 203 is communicably connected to the bus 220 through the signal line 224. The determination module 205 is communicably connected to the bus 220 through the signal line 226. The logging module 207 is communicably connected to the bus 220 through the signal line 228. The GUI module 211 is communicably connected to the bus 220 through the signal line 232. The processor 112 is communicably connected to the bus 220 through the signal line 236. The storage device 104 is communicably connected to the bus 220 through the signal line 133.

  The communication module 201 is code and routines responsible for communication between the components of the network management module 114 and between the other components of the vehicle system 101. For example, the communication module 201 receives a request for network data from the request module 203 and transmits it to the connectivity server 141. The communication module 201 receives network data from the connectivity server 141 and sends it to the determination module 205. In one embodiment, the communication module 201 also caches network data and stores it in the storage device 104. The communication module 201 is communicably connected to the bus 220 through the signal line 222.

  The communication module 201 receives the connectivity data log from the logging module 207. In one embodiment, the communication module 201 sends a connectivity data log to the connectivity server 141 for analysis and storage. In another embodiment, the communication module 201 stores the connectivity data log in the storage device 104 as log data.

  In one embodiment, the communication module 201 receives graphical data from the GUI module 211. The communication module 201 transmits graphical data to the interface 120 for displaying information to the user 125. For example, the graphical data is used to generate a user interface for displaying network connectivity information (eg, recommended network operators or recommended wireless technologies such as WiFi) to the user 125. .

  In one embodiment, the communication module 201 is also responsible for communication between the other submodules 203, 205, 207, and 211 in the network management module 114. For example, the communication module 201 communicates with the determination module 205 and the logging module 207 to pass the output of the determination module 205 (such as determining suitable network connectivity) to the logging module 207. However, in this description, reference to the communication module 201 may be omitted for clarity and convenience. For example, for clarity and convenience, the above scenario may be described as the decision module 205 delivers output (such as determining suitable network connectivity) to the logging module 207.

  The request module 203 is code and routines for requesting network data. For example, after the user 125 enters a new destination or the navigation module 116 estimates a new destination for the vehicle, the vehicle data is updated and the request module 203 retrieves the updated vehicle data from the storage device 104. . The updated vehicle data describes the new destination, the current location of the vehicle, and the expected travel route to the new destination. The request module 203 generates a request for network data based at least in part on the updated vehicle data. The request module 203 is communicably connected to the bus 220 through the signal line 224.

  In one embodiment, the request module 203 periodically retrieves vehicle data from the storage device 104 and requests network data based at least in part on the vehicle data at specific time intervals. For example, the request module 203 requests network data from the connectivity server 141 based on the vehicle data at predetermined time intervals such as 30 minutes, 1 hour, and 5 hours. In another embodiment, once the destination data and / or travel route data is updated, the request module 203 retrieves the updated vehicle data from the storage device 104 and based at least in part on the updated vehicle data. Request network data.

  The request module 203 generates a request for network data based at least in part on the vehicle data. For example, the request module 203 generates a request including vehicle data describing a destination, a current location, and an expected travel route to the destination. In this way, the connectivity server 141 can provide the requested network data based at least in part on the vehicle data. For example, the connectivity server 141 provides network data describing network coverage information about an area along the predicted travel route based at least in part on the predicted travel route.

  The determination module 205 is code and routines for determining one or more networks suitable for the vehicle. For example, the determination module 205 determines one or more networks suitable for the vehicle based at least in part on network data received from the connectivity server 141. The determination module 205 transmits the determination of one or more suitable networks to the logging module 207. The determination module 205 is communicably connected to the bus 220 through the signal line 226.

  The determination module 205 receives network data from the connectivity server 141 through the communication module 201. The network data includes coverage data, account data, congestion status data, and connectivity rule / policy data. The determination module 205 caches the network data and stores it in the storage device 104. In one embodiment, the determination module 205 determines one or more available networks based at least in part on the coverage data. For example, the determination module 205 analyzes the network data for coverage information about the current location and / or an area along the expected travel route to determine one or more available networks.

  In one embodiment, the determination module 205 ranks one or more available networks based at least in part on account data, congestion data, and data volume agreements with the carrier. To do. For example, the determination module 205 ranks a less crowded network higher than a more crowded network, so that a network with a large amount of data that can be used by a vehicle is a network that has a smaller amount of data that can be used by a vehicle. Rank higher. The determination module 205 also balances the amount of data used, that is, the amount of communication among the carriers based on the agreement of the amount of data with the carriers. For example, if a certain number of vehicles are connected to a network provided by a certain carrier for a certain period of time, the other carriers are ranked higher than this carrier.

  In one embodiment, the determination module 205 adjusts the ranks of available networks based on which applications in the vehicle require network connectivity. For example, if a user 125 (eg, a driver or a passenger) is watching music or video on the Internet that requires high bandwidth, the decision module 205 may select a network that provides greater bandwidth. Rank higher. As another example, if the vehicle requires transmission of diagnostic data to the connectivity server 141, the decision module 205 may use a more reliable network technology (eg, 3G or GSM network technology). ) Is ranked higher.

  In one embodiment, the determination module 205 determines one or more preferred networks from one or more available networks based on ranks and priorities included in the connectivity rule policy data. . For example, the determination module 205 analyzes network data for connectivity rule / policy data. Connectivity rule policy data includes carrier priority, wireless network technology general priority, and wireless network technology priority for various data types. For example, in general, Verizon has a higher priority than AT & T, generally 3G has a higher priority than WiFi, WiFi has a higher priority than LTE, and LTE has a higher priority than WiMAX. Also have a high priority. However, in the case of movie data, WiFi has the highest priority, and in the case of safety data, 3G has a higher priority. The determination module 205 uses the rank and priority to determine a suitable network (eg, a suitable carrier and / or a suitable wireless network technology).

  The logging module 207 is a code and routine for logging connectivity data. For example, the logging module 207 receives a decision from a decision module 205 that includes one or more suitable networks. In one embodiment, logging module 207 logs connectivity data and stores the connectivity data log in storage device 104 once the vehicle is connected to one of the preferred networks. The connectivity data describes data usage, data usage date, data usage time, and one or more of the carriers that provide the service. The logging module 207 is communicably connected to the bus 220 through the signal line 228.

  In one embodiment, the logging module 207 sends connectivity data logs to the connectivity server 141 for analysis periodically at specific time intervals. For example, the logging module 207 transmits the connectivity data log to the connectivity server 141 at predetermined time intervals such as 1 hour, 10 hours, and 24 hours. In another embodiment, the logging module 207 sends the connectivity data log to the connectivity server 141 for analysis when the connectivity data log is updated. For example, when the vehicle is connected to a new network, the logging module 207 is based on data describing the carrier and / or wireless technology of the new network, the date and time of connection, and the data usage since the connection. , Update the connectivity data log.

  The GUI module 211 is code and routines for providing graphical data for the user 125. The GUI module 211 is communicably connected to the bus 220 through the signal line 232. In one embodiment, the GUI module 211 generates graphical data for drawing a user interface for notifying the user 125 of one or more suitable networks. For example, the GUI module 211 receives information describing one or more carriers and / or wireless technologies of a suitable available network. The GUI module 211 generates graphical data for drawing a user interface for displaying information about a preferred available network to the user 125. The GUI module 211 sends the generated graphical data to the interface 120 so that the user 125 can select a network from the preferred available networks through the user interface. To present.

Storage device 104
FIG. 3 is a block diagram 300 illustrating a storage device 104 according to one embodiment. The storage device 104 includes coverage data 301, account data 303, connectivity rule / policy data 305, congestion status data 307, log data 309, navigation data 311, content data 313, and vehicle data 315. Including. Those skilled in the art will appreciate that the storage device 104 may include other data to provide the functionality described herein.

  Coverage data 301 is data describing network coverage information. For example, the coverage data 301 includes a 3G / LTE / 4G coverage map, WiFi / WiMAX hotspot information, and a satellite map for each carrier candidate. In one embodiment, the connectivity server 141 receives coverage data 301 from various carriers and stores it in the connectivity database 144. When the vehicle system 101 requests the coverage data 301 based on the new destination and / or new travel route, the connectivity server 141 sends the coverage data 301 regarding the new destination and / or new travel route to the vehicle system 101. provide. The vehicle system 101 stores the coverage data 301 in the storage device 104.

Account data 303 includes a connectivity data log. For example, each entry in the log records vehicle data usage information such as, for example, data usage, data usage date, data usage time, and telecommunications carrier that provides the service. In one embodiment, account data 303 indicates how much data the vehicle is allowed to use during a particular time period. In one embodiment, the connectivity server 141 receives connectivity data logs from various vehicle systems 101 and stores them in the account log database 175. The connectivity server 141 authenticates and analyzes each carrier's activity based on the connectivity data log. When a certain vehicle system 101 requests its own connectivity data log, the connectivity server 141 retrieves the connectivity data log from the account log database 175, and the vehicle system 10
1 to send. The vehicle system 101 receives the connectivity data log and stores it in the storage device 104 as account data 303.

  The connectivity rule / policy data 305 is data describing rules and policies for selecting a network suitable for the vehicle. For example, the connectivity rule policy data 305 indicates the carrier priority, the general priority of the wireless network technology, and the priority of the wireless network technology for various data types. In one embodiment, the connectivity server 141 retrieves the connectivity rule / policy data 305 from the connectivity database 144 based on a request from the vehicle system 101 and transmits it to the vehicle system 101. The vehicle system 101 stores the connectivity rule / policy data 305 in the storage device 104.

  The congestion status data 307 is data describing how congested the network is. For example, the congestion status data 307 indicates whether each network candidate is congested (congested). In one embodiment, the connectivity server 141 retrieves the congestion status data 307 from the connectivity database 144 and transmits it to the vehicle system 101 when the vehicle system 101 requests the congestion status data 307. The vehicle system 101 stores the congestion status data 307 in the storage device 104.

  Log data 309 includes a connectivity data log maintained in the vehicle. For example, the logging module 207 periodically generates and updates the connectivity data log at specific time intervals such as 1 hour, 5 hours, 12 hours, and 24 hours. The connectivity data log records vehicle data usage information such as data usage, data usage date and time, and telecommunications carriers that provide services. In one embodiment, the logging module 207 sends an updated connectivity data log to the connectivity server 141 to authenticate and analyze each carrier's activity.

  The navigation data 311 is generated by the navigation module 116. For example, the navigation data 311 includes data describing one or more travel routes with suitable network coverage. In one embodiment, the navigation module 116 determines one or more network coverage areas based at least in part on the network data and calculates one or more travel routes with suitable network coverage. . The navigation module 116 stores data describing one or more travel routes having suitable network coverage in the storage device 104 as navigation data 311.

  The content data 313 is data that is buffered by the buffering module 118. For example, the content data 313 includes media data from the Internet such as video content data and audio content data. In one embodiment, the buffering module 118 predicts a network interruption and calculates an interruption period based at least in part on the network data. The buffering module 118 buffers content data 313 from the Internet in preparation for network interruption.

Vehicle data 315 includes data associated with the vehicle. For example, the vehicle data 315 includes location data, destination data, and travel route data. In another example, the vehicle data 315 also includes vehicle speed data. The location data describes the current location of the vehicle. The destination data indicates the destination of the vehicle. The travel route data describes an expected travel route to the destination. In one embodiment, the control unit 103 generates vehicle data 315 and stores it in the storage device 104. The request module 203 generates a request for a network based at least in part on the vehicle data 315.

Methods Various embodiments of the methods herein will now be described with reference to FIGS. 4-6B.

  FIG. 4 is a flowchart illustrating a method 400 for determining a network according to one embodiment. The request module 203 transmits a request for network data to the connectivity server 141 (402). In one embodiment, the request includes vehicle data describing the current location of the vehicle, the destination of the vehicle, and the travel route to the destination. The connectivity server 141 provides network data based at least in part on vehicle data.

  In step 404, the determination module 205 receives the requested network data from the connectivity server 141 through the communication module 201. For example, the requested network data includes coverage data, account data, congestion status data, and connectivity rule / policy data.

  In step 406, the determination module 205 is suitable for the vehicle based at least in part on the requested network data including coverage data, account data, congestion status data, and connectivity rule policy data. Determine the network. A suitable network is determined using network data as a factor. Furthermore, the preferred network is variable based on vehicle data (for example, destination and travel route), date and time.

  5A-5B are flowcharts illustrating a method 500 for determining one or more preferred networks. The request module 203 retrieves vehicle data (502). For example, after the user 125 enters a new destination or after the navigation module 116 estimates a new destination, the request module 203 retrieves updated vehicle data from the storage device 104. The updated vehicle data describes the new destination, the current location of the vehicle, and the expected travel route to the new destination.

  In step 504, the request module 203 generates a request for network data based on the vehicle data. For example, the request includes updated vehicle data describing the new destination, the current location of the vehicle, and the expected travel route to the new destination. In step 506, the request module 203 transmits the request to the connectivity server 141. In this way, the connectivity server 141 can provide network data to the determination module 205 based at least in part on the vehicle data.

  In step 508, the determination module 205 receives network data from the connectivity server 141. For example, the network data includes coverage data, account data, congestion status data, and connectivity rule / policy data. In step 510, the determination module 205 caches network data. For example, the determination module 205 stores network data in the storage device 104.

Referring now to FIG. 5B, shown is a subroutine 555 for determining one or more suitable networks based on network data, according to one embodiment. The determination module 205 determines one or more available networks based on the network data (532). For example, the determination module 205 analyzes the network data for coverage information about an area along the expected travel route to the current location and / or destination of the vehicle to determine one or more available networks.

  In step 534, the determination module 205 ranks available networks. For example, the determination module 205 ranks the available networks based at least in part on account data, congestion status data, and data volume contracts with carriers.

  In step 536, the determination module 205 adjusts the rank based at least in part on connectivity requirements from in-vehicle applications. For example, if the in-car application requires high bandwidth, for example, requiring video playback, the decision module 205 ranks the network that provides higher bandwidth to rank higher. Adjust.

  In step 538, the determination module 205 determines one or more suitable networks based at least in part on the rank and connectivity rule policy data. For example, connectivity rule policy data includes carrier priority, wireless network technology general priority, and wireless network technology priority for various data types. The decision module 205 uses the rank and priority to determine one or more suitable carriers such as one or more suitable carriers and / or one or more suitable wireless network technologies. Determine the network.

  After step 538, subroutine 555 ends and method 500 returns to step 512. Referring again to FIG. 5A, at step 512, logging module 207 logs connectivity data. For example, once the vehicle is connected to one of the preferred networks, logging module 207 logs connectivity data and stores the connectivity data log in storage device 104.

  FIG. 6 is a flowchart illustrating a method 600 for navigating a vehicle based on network coverage information according to one embodiment. The navigation module 116 detects a network interruption (602) and retrieves network data from the storage device 104 in response to detecting the network interruption. The detection of the network interruption may detect that the network is actually interrupted, or may predict in advance that the network is interrupted based on received power or network data (particularly coverage data). The network data extracted when detecting a network interruption includes coverage data describing network coverage information. The navigation module 116 determines one or more network coverage areas surrounding the current location of the vehicle based at least in part on the network coverage information. In step 604, the navigation module 116 notifies the user 125 of one or more network coverage areas.

  In step 606, the navigation module 116 calculates a travel route having suitable network coverage based at least in part on the network coverage information. In step 608, the navigation module 116 navigates the vehicle based on the travel route. For example, the navigation module 116 transmits data describing the travel route to the interface 120 for display to a user 125 such as a driver. If the user 125 agrees to the travel route, the navigation module 116 navigates the vehicle to the destination based on the travel route.

FIG. 7 is a flow diagram illustrating a method 700 for buffering media data in response to a network interruption, according to one embodiment. The buffering module 118 predicts a network interruption (702). For example, the buffering module 118 retrieves network data from the storage device 104 and determines in advance whether there is a network interruption based at least in part on the network data. In one embodiment, the buffering module 118 predetermines that there is a network interruption.

  In step 704, the buffering module 118 determines an interruption period based on the network data. For example, the buffering module 118 calculates the start time and length of the interruption period according to the location and length of a portion of the travel route that does not involve network coverage and the average vehicle speed.

  In step 706, the buffering module 118 buffers the media data according to the interruption period. For example, the buffering module 118 buffers video content that a user 125 (eg, a passenger) is watching in a vehicle in preparation for an expected interruption period.

  The foregoing description of the embodiments has been made for purposes of illustration and description. Accordingly, the disclosed embodiments are not exhaustive and are not intended to limit the present invention to the above-described embodiments. The present invention can be variously modified in accordance with the above disclosure. The scope of the present invention should not be construed as being limited to the above-described embodiments, but should be construed according to the claims. Those skilled in the art of the present invention will understand that the present invention can be implemented in various other forms without departing from the spirit and essential characteristics thereof. Similarly, the naming and partitioning methods for modules, processes, features, attributes, methods, and other aspects of the invention are neither essential nor important. Further, the mechanism for implementing the present invention and its features may have different names, division methods, and configurations. Further, those skilled in the art will appreciate that modules, processes, features, attributes, methods, and other aspects of the invention can be implemented as software, hardware, firmware, or combinations thereof. When the present invention is implemented as software, each element such as a module may be implemented in any manner. For example, stand-alone programs, parts of large programs, different programs, static or dynamic link libraries, kernel loadable modules, device drivers, and other methods known to those skilled in computer programming Can do. Further, implementations of the invention are not limited to a particular programming language, nor are they limited to a particular operating system or environment. As described above, the above description of the present invention is illustrative rather than limiting, and the scope of the present invention is defined according to the appended claims.

101 vehicle system 102 communication unit 103 control unit 104 storage device 105 network 112 processor 114 network management module 116 navigation module 118 buffering module 141 connectivity server 142 data supply module 144 connectivity database 150 unified cloud database 171 account server 175 account log Database 201 Communication module 203 Request module 205 Determination module 207 Logging module 211 GUI module

Claims (17)

A network connectivity management method for determining a network to which a vehicle is connected,
A vehicle system of the vehicle includes:
Obtaining network data for a network provided in the vicinity of the planned travel route of the vehicle;
Determining which network to connect to based on the network data;
A network connectivity management method that performs. The network data includes a coverage area for a network, a network connection history of the vehicle, a congestion situation of the network, and a rule for determining a network to which the vehicle is connected.
The network connectivity management method according to claim 1. Determining which network to connect to based on the network data comprises:
Determining a network available to the vehicle based on the network data;
Generating a rank of the available network based on the network data and a data usage agreement with a carrier;
Adjusting the rank of the available network based on application requirements;
Which network to connect to among the available networks, the adjusted rank, and rules indicating how the vehicle included in the network data determines a network to connect to. A step of making a decision based on;
The network connectivity management method according to claim 1 or 2, comprising: The network data includes a data usage, a data usage date and time, and a connectivity data log indicating a telecommunications carrier that provides the service.
The network connectivity management method according to claim 1. Logging network data including network connection history of the vehicle;
Sending the connectivity data log to a connectivity server;
The network connectivity management method according to claim 4, wherein the vehicle system further executes: Obtaining the network data comprises:
Transmitting a request including vehicle data including a current position and a destination of the vehicle to a connectivity server storing the network data;
Receiving network data transmitted from the connectivity server;
The network connectivity management method according to claim 5, comprising: Detecting the interruption or interruption of the network connection based on the network data;
Calculating a travel route in which network connection is provided based on the network data when interruption of the network connection is detected;
Navigating the vehicle according to the calculated travel route;
The network connectivity management method according to claim 1, wherein the vehicle system further executes. Predicting a network connection interruption based on the network data;
Determining an interruption period based on the network data;
Buffering data obtained from the network in preparation for the interruption period;
The network connectivity management method according to claim 1, wherein the vehicle system further executes. A vehicle system mounted on a vehicle for determining a network to which the vehicle is connected,
An acquisition module for acquiring network data about a network provided in the vicinity of the planned travel route of the vehicle;
A determination module for determining which network to connect to based on the network data;
A vehicle system comprising: The network data includes a coverage area for a network, a network connection history of the vehicle, a congestion situation of the network, and a rule for determining a network to which the vehicle is connected.
The vehicle system according to claim 9. The determination module is
Based on the network data, determine a network that the vehicle can use;
Generating a rank of the available network based on the network data and a data usage contract with a carrier;
Adjust the rank of the available network based on application requirements;
Which network to connect to among the available networks, the adjusted rank, and rules indicating how the vehicle included in the network data determines a network to connect to. To make a decision based on
The vehicle system according to claim 9 or 10. The network data includes a data usage, a data usage date and time, and a connectivity data log indicating a telecommunications carrier that provides the service.
The vehicle system according to any one of claims 9 to 11. Logging network data including a network connection history of the vehicle, and further comprising a logging module for transmitting the connectivity data log to a connectivity server;
The vehicle system according to claim 12. The acquisition module is
Sending a request containing vehicle data including the current location and destination of the vehicle to a connectivity server storing the network data;
Receiving network data transmitted from the connectivity server;
The vehicle system according to claim 13. Detecting that the network connection is interrupted or interrupted based on the network data;
When a break in the network connection is detected, a travel route in which the network connection is provided is calculated based on the network data,
Navigating the vehicle according to the calculated travel route;
A navigation module;
The vehicle system according to any one of claims 9 to 14. Based on the network data, predict network interruptions,
Based on the network data, determine an interruption period;
Buffering data obtained from the network in preparation for the interruption period;
A buffering module;
The vehicle system according to any one of claims 9 to 15.   The computer program which makes a computer perform each step of the method in any one of Claims 1-8.

Images