Edge computing assisted vehicle alert system and method

Abstract

A vehicle alert system and method for implementing edge computing assistance. A multi-access edge computing (MEC) server may be configured to: obtain a plurality of messages from one or more vehicles; determining a formation of a traffic queue based on the plurality of messages; determining a plurality of zone-based speed limits; determining when a vehicle approaching the traffic queue is likely to travel faster than desired based on a position of the vehicle relative to an applicable zone-based speed limit; and generate one or more alerts.

Description

Technical Field

[0001] The present disclosure relates to systems and methods for edge computing-assisted traffic queue detection, speed limit zone creation, and / or fast approaching vehicle warning systems. Background Art

[0002] Determining appropriate vehicle speed can be challenging when road and traffic conditions are variable and changing rapidly. Summary of the invention

[0003] In various cases, multi-access edge computing (MEC) is used to detect traffic queues in an area, determine multiple speed limit zones for vehicles approaching traffic queues, determine vehicles operating at abnormal speeds, and alert other vehicles ahead. In various embodiments, cellular multicast capabilities are used to broadcast and receive messages to facilitate the warning system. For example, a 5G network can be used to facilitate real-time two-way communication between vehicles and MEC servers. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] Detailed description is set forth with respect to the accompanying drawings. The use of the same reference numerals may indicate similar or identical items. Various embodiments may utilize elements and / or components other than those shown in the accompanying drawings, and some elements and / or components may not be present in various embodiments. The elements and / or components in the accompanying drawings are not necessarily drawn to scale. Throughout this disclosure, singular and plural terms may be used interchangeably, depending on the context.

[0005] Figure 1 An illustrative environment is depicted in which systems and methods for edge computing-assisted traffic queue detection, speed limit zone creation, and / or fast approaching vehicle warning systems may be implemented in accordance with at least one embodiment of the present disclosure.

[0006] Figure 2 A diagram is shown depicting an example of an environment in which basic safety messaging (BSM) is used to relay lane data to a multi-access edge computing (MEC) server in accordance with at least one embodiment of the present disclosure.

[0007] Figure 3 A diagram is shown depicting an example of an environment in which a multi-access edge computing (MEC) server transmits information to vehicles on a road in accordance with at least one embodiment of the present disclosure.

[0008] Figure 4 A diagram is shown depicting an example of an environment in which alerts are provided in response to an abnormal condition in accordance with at least one embodiment of the present disclosure.

[0009] Figure 5 An illustrative example of a process for edge computing-assisted vehicle alerting according to one or more example embodiments of the present disclosure is shown.

[0010] Figure 6 A block diagram illustrating an example of a machine or system upon which any one or more of the techniques (eg, methodologies) discussed herein may be performed. DETAILED DESCRIPTION

[0011] Figure 1 An illustrative environment 100 is depicted in which systems and methods for edge computing-assisted traffic queue detection, speed limit zone creation, and / or fast approaching vehicle warning systems may be implemented in accordance with at least one embodiment of the present disclosure.

[0012] Figure 1 An environment is depicted in which various vehicles (such as vehicles 102 and 104 and other vehicles shown) may be present. Vehicles may be in different lanes on the road and traveling at different speeds. For example, vehicle 102 may be traveling slowly due to being in a traffic queue, while vehicle 104 may be traveling faster. One of the challenges that vehicle operators may encounter is the difficulty in determining an appropriate operating speed based on variable traffic conditions. For example, if vehicle 102 is stopped or moving slowly (e.g., <10mph) in a traffic jam, vehicles behind vehicle 102 may need to slow down when approaching the traffic jam. On a highway, the posted speed limit may be appropriate in some situations (e.g., when traffic is flowing without any interruptions), but inappropriate in other situations (e.g., when there is a traffic jam or congestion).

[0013] In various embodiments, vehicles such as vehicle 102 and vehicle 104 include sensors such as forward-facing cameras and communication modules (e.g., C-V2X communication modules). Vehicles on the road can transmit data about their location, heading, and lane data to a multi-access edge computing (MEC) server 108 via a network infrastructure 106. In various embodiments, the network infrastructure 106 uses a high-frequency communication channel to enable high-speed, low-latency communication between the vehicle and the MEC server 108.

[0014] In various embodiments, the vehicle sends out data at regular intervals in the form of basic safety messages (BSMs). The data may include information about the state of the vehicle. For example, the vehicle may send out data packets including its measured position (e.g., as GPS coordinates), the direction it is heading, its current speed, etc. In various embodiments, the vehicle also collects lane data. For example, vehicle 102 may transmit a regular BSM stream (e.g., BSM 110) to network infrastructure 106, and vehicle 104 may transmit a regular BSM stream (e.g., BSM 112) to network infrastructure 106.

[0015] The network infrastructure 106 may facilitate communications between vehicles (e.g., vehicle 102 and vehicle 104) and the MEC server 108. The network infrastructure may include cellular communication towers that provide high-speed, low-latency communications with the MEC server 108. In various embodiments, the MEC server 108 receives BSMs from vehicles in nearby proximity and uses the data to determine appropriate travel speeds based on known traffic conditions. For example, Figure 1 The left hand portion of the traffic jam may depict a traffic jam or congestion, wherein vehicles in the traffic jam send a BSM with their location, speed (e.g., less than 10 mph), and lane to the MEC server 108. The MEC server 108 may use the BSM information to determine where deceleration occurs, the size and location of the queue, and a plurality of traffic-aware speed zones. Each zone may have an associated speed limit that encodes the appropriate speed at which the vehicle should travel in the zone. For example, the first zone may encompass a queue of vehicles on the left hand portion that specifies a low speed due to the close proximity of the vehicles to each other and the vehicles generally traveling at a slow speed. The vehicle 114 may be located in the second zone, and the vehicle 114 may receive a message indicating that the vehicle should travel at a slower speed so as to be able to have a desired braking distance when arriving at the traffic queue. Continuing with this example, the vehicle 104 may be in a third zone, where the speed limit is relatively higher than the first and second zones, because the vehicle 104 is farther away and has a longer deceleration and braking distance before arriving at the traffic queue.

[0016] In various embodiments, the MEC server 108 receives BSM data, determines when the vehicle is operating outside of specified parameters, and is able to issue an alert. As an example, consider the following situation: the MEC server 108 has received BSM data to determine that there is a traffic queue in front of the vehicle 104, determines the zone-based speed limit of the vehicle 104, and also determines that the vehicle 104 is traveling faster than the zone-based speed limit. In this scenario, the MEC server 108 may send a zone-based speed warning 116 to the vehicle 104. The zone-based speed warning 116 may be transmitted to the vehicle 104 via the network infrastructure 106 and may be presented to the operator of the vehicle. For example, the operator of the vehicle may receive a visual and / or audio indication of a deceleration or a traffic queue ahead. In some embodiments, the vehicle operator is autonomous or semi-autonomous, so that the vehicle can programmatically respond to the zone-based speed warning 116 without human intervention, and initiate braking in response to receiving the zone-based speed warning 116. In some embodiments, the MEC server 108 may send a fast approaching vehicle warning 118 to the vehicle in front of the speeding vehicle. For example, if vehicle 104 is traveling at a speed that exceeds the speed limit expected based on the zone, one or more cars in the same lane ahead of vehicle 104 may be alerted. The MEC server may use lane data from the BSM to identify which vehicles should be alerted. For example, vehicle 102 is directly ahead of vehicle 104 and may receive a fast approaching vehicle alert 118 and may respond to the alert, for example, by pulling over to the shoulder, activating a turn signal indicator or other visual indicator, or performing other mitigation measures to avoid or reduce potential adverse consequences if the vehicle is unable to stop in time.

[0017] Figure 2 A diagram is shown depicting an example of an environment 200 in which basic safety messaging (BSM) is used to relay lane data to a multi-access edge computing (MEC) server in accordance with at least one embodiment of the present disclosure.

[0018] In various embodiments, vehicles within environment 200 are configured to receive and / or transmit messages. Messages may be used to relay information about vehicle speed, location, heading, lane information, or other relevant data in real time or near real time. In various embodiments, messages are implemented as basic safety messages (BSM) or other standardized message formats. Vehicles may be equipped with dedicated short range communication (DSRC) technology and / or cellular V2X (C-V2X) technology to communicate with other vehicles, infrastructure, or other electronic devices in the surrounding environment.

[0019] In various embodiments, the vehicle will broadcast a BSM (e.g., BSM 210) at regular intervals, which can be received by other vehicles or infrastructure within range, such as a multi-access edge computing (MEC) server 208. The information contained in the BSM can then be used by the receiving vehicle or infrastructure to make informed decisions about how to operate in a more desirable manner.

[0020] The network infrastructure 206 can facilitate communication between the vehicle and the MEC server 208. The network infrastructure may include cellular communication towers that provide high-speed, low-latency communication with the MEC server 208. In various embodiments, the MEC server 208 receives BSMs from vehicles in nearby proximity and uses the data to determine appropriate travel speeds based on known traffic conditions. The MEC server 208 can receive BSMs from vehicles with GPS locations, current lane data, speed directions, etc. In various embodiments, the MEC server 208 collects these BSMs and determines when a traffic queue is formed (e.g., length, location, average speed, road topology, etc.).

[0021] In various embodiments, the vehicle includes a cellular vehicle-to-everything (C-V2X) module 204 for performing communications between the vehicle and its surroundings, including other vehicles, infrastructure, etc. In various embodiments, the C-V2X module 204 subscribes to a local MNO to receive traffic data via multicast / broadcast. V2X communications include both V2V (vehicle-to-vehicle) and V2I (vehicle-to-infrastructure) communications, as well as other forms of communications such as V2P (vehicle-to-pedestrian) and V2B (vehicle-to-bicycle). Vehicle-to-vehicle (V2V) communications can be used to exchange BSMs with other nearby vehicles to warn of potential adverse situations, and vehicle-to-infrastructure (V2I) communications can communicate with roadside infrastructure (such as traffic lights, cameras, or message signs) to obtain information about road conditions or receive warnings. In various embodiments, the vehicle uses a cellular V2X (C-V2X) communication module to transmit messages to / receive messages from a 5G network infrastructure.

[0022] The vehicle may have various onboard sensors. These sensors may include cameras, accelerometers, speedometers, etc. In various embodiments, the vehicle's forward camera 202 captures an image of the environment in front of the vehicle and may be processed to determine the vehicle's lane information. For example, if the vehicle is traveling south on a three-lane highway, the lane information may be encoded as a number (e.g., from 0 to 2), where each number maps to a lane, such as 0=leftmost lane, 1=center lane, and 2=rightmost lane. This is merely an illustrative example of how lane information may be encoded, and is not intended to be limiting, and other implementations are contemplated within the scope of the present disclosure. The lane information may be determined using an onboard processor or a remote processor (e.g., by sending raw footage captured by the forward camera to a cloud server with greater computing power). For example, image processing techniques based on machine learning (ML) may be used to determine lane information.

[0023] Some or all vehicles in the traffic environment may transmit a BSM (e.g., BSM 210) to the MEC server 208. The MEC server may receive the BSM message and detect when and where the formation of a traffic queue occurs. In various embodiments, the MEC server 208 determines the traffic conditions in each lane of the road based on the BSM transmitted by the vehicles on the road, and determines the corresponding speed limits of multiple zones and vehicles in each lane based on the traffic conditions. Figure 3 Zone-based speed limits are discussed in more detail in .

[0024] Figure 3 A diagram is shown depicting an example of an environment 300 in which a multi-access edge computing (MEC) server transmits information to vehicles on a road in accordance with at least one embodiment of the present disclosure.

[0025] In various embodiments, the MEC server 308 receives the BSM from the vehicle via the network infrastructure 306. The MEC server 308 may determine the traffic conditions on the road and transmit messages (e.g., messages 302 and 304) to the vehicle to provide a zone-based speed limit. The vehicle on the road may transmit a message with lane indication information (e.g., learned from a forward camera, etc.) to the local MEC server 308. The MEC server 308 collects these messages and detects queues on the road. The MEC server 308 broadcasts messages to all vehicles in the area, the message including various information such as location, direction, and zone-based speed limits based on queue location / length / speed. For example, a vehicle in zone 1 may already be in a traffic queue and receive a message 302 indicating that vehicles traveling in each lane should travel at a speed of less than 10mph. Continuing, the MEC server 308 may send other messages to vehicles in zone 2, which may be at a distance between 0 meters and 100 meters from the end of the traffic queue and have a slightly higher zone-based speed limit of 20mph. Continuing, zone 3 may be at a further distance of 100 to 500 meters from the end of the traffic queue and have a different zone-based speed limit of 30 mph. Finally, vehicles in zone 4 may receive a message 304 having a zone-based speed limit of 40 mph at a distance of more than 500 meters. It should be noted that Figure 3 The regions depicted in FIG. 1 are not necessarily drawn to scale and are presented for illustrative purposes only.

[0026] In various embodiments, the zone-based speed limit includes location data, direction, and speed limit. The location data may define the boundaries of the zone and may specify specific lanes (e.g., left lane, center lane, right lane) in which the zone-based speed limit applies (e.g., in the case where one lane has a traffic queue and the other lanes do not). In various embodiments, the MEC server 208 broadcasts / multicasts the zone-based speed limit to all vehicles in the zone. In various embodiments, the following vehicles receive messages with zone-based speed limits and compare their current locations with these zone messages and display corresponding data (e.g., location, direction, speed limit) to the driver, for example, via an HMI.

[0027] As traffic conditions change and as vehicles move through the road, the MEC server 308 will send new messages to the vehicles to maintain their assessment of the current traffic conditions. Thus, the messages may encode different zone-based speed limit values ​​based on the location of the vehicle, the direction of the vehicle, the lane in which the vehicle is traveling, etc., which provides a more accurate assessment of appropriate operating conditions than indicated speed limit signs that do not provide any insight into upcoming road and traffic conditions in real time. For example, the MEC server 308 may broadcast zone-based speed information (e.g., as a BSM), which includes location information (e.g., GPS coordinates) of the zone, direction information, and speed limit information. Message 302 may be transmitted to vehicles in zone 1 having a first zone-based speed limit (e.g., based on a BSM message with their location), and message 304 may be transmitted to vehicles in zone 4 having a different zone-based speed limit.

[0028] In various embodiments, zone distances and / or speed limits may be determined based on vehicle characteristics. For example, different types of vehicles (e.g., based on make or model) may have larger or smaller zones, higher or lower zone-based speed limits, to accommodate a greater or lesser amount of braking distance required. For example, Figure 3 An example zone for sedans may be depicted, while an unloaded straight haul truck may have a lower speed limit (or longer distance) over the same zone, while a fully loaded line transport truck may have an even lower speed limit or longer distance, and so on.

[0029] Vehicles approaching the traffic queue can use the message to take appropriate action. For example, the message 304 can be transmitted to a vehicle 310 that has sufficient time to respond to the changing traffic conditions and initiate braking or deceleration before approaching the traffic queue or other vehicles in the area in front of the vehicle.

[0030] Figure 4 A diagram is shown depicting an example of an environment 400 in which alerts are provided in response to abnormal conditions in accordance with at least one embodiment of the present disclosure.

[0031] In various embodiments, Figure 4 Vehicles (e.g., vehicle 402 and vehicle 404) may provide basic safety messages (BSMs) to a nearby multi-access edge computing (MEC) server 408 via network infrastructure 406. In various embodiments, MEC server 408 monitors traffic conditions based on BSMs received from vehicles on the road and determines where there are slowdowns, traffic queues, or other traffic conditions. MEC server 408 may determine that a traffic queue has formed and the positions of various vehicles relative to the traffic queue. For example, MEC server 408 may use BSMs to determine Figure 4A traffic queue has been formed at the left portion of , and vehicle 402 is the last vehicle in the traffic queue.

[0032] In various embodiments, the vehicle 404 provides a BSM to the MEC server 408. The BSM may include lane data. The MEC server 408 may determine that the vehicle 404 is approaching a traffic queue and is located in a lane in which a traffic queue has been formed. The MEC server 408 may send an alert 414 to the vehicle 404, indicating that there is an upcoming queue, a speed limit based on the zone, or other information that can be used by the vehicle to determine the appropriate operating conditions. In various embodiments, the vehicle 404 will receive the alert 414. The alert can be used to present information to the vehicle operator, for example, to present an audio or visual indication of an upcoming traffic queue, a deceleration, or other relevant conditions to the driver. In various embodiments, the traffic queue may be forming around a turn, and the driver may not be able to directly see the traffic queue when receiving the alert. In various embodiments, the alert 414 includes a speed limit based on the zone, and the vehicle compares the current speed of the vehicle with the speed limit based on the zone. If the vehicle is traveling faster than the speed limit based on the zone, a beep, a visual indication, a warning message, or other information may be provided to the vehicle. In some embodiments, the MEC server 408 uses the BSM to determine whether the vehicle is traveling at a speed exceeding a zone-based speed limit and transmits a warning message or alert to the vehicle, and transmits instructions to the autonomous or driver assistance system to take appropriate action.

[0033] In various embodiments, the vehicle operator (e.g., driver or autonomous driving system) may receive an alert to perform a mitigation action. For example, the mitigation action may be causing the vehicle 404 to reduce its speed. In some embodiments, the mitigation action may be causing the driver to change lanes, such as to Figure 4 In some embodiments, vehicle 402 will receive an alert 412 of a rapidly approaching vehicle behind it, which may allow vehicle 402 or its operator time to perform mitigation measures, such as pulling over to the shoulder, activating a turn signal indicator or other visual indication, or performing other mitigation measures to avoid or reduce a potentially adverse situation for vehicle 404 if the vehicle is unable to stop in time.

[0034] Figure 5An illustrative example of a process 500 for edge computing-assisted vehicle warning according to one or more example embodiments of the present disclosure is shown. In at least one embodiment, some or all of the process 500 (or any other process described herein, or variations and / or combinations thereof) is executed under the control of one or more computer systems storing computer executable instructions, and may be implemented as code (e.g., computer executable instructions, one or more computer programs, or one or more applications) that is executed collectively on one or more processors, implemented by hardware, software, or a combination thereof. In at least one embodiment, the code is stored on a computer-readable storage medium in the form of a computer program that stores a plurality of computer-readable instructions that can be executed by one or more processors. In at least one embodiment, the computer-readable storage medium is a non-transitory computer-readable medium. In at least one embodiment, at least some of the computer-readable instructions that can be used to perform the process 500 are not stored using only transient signals (e.g., propagated transient electrical or electromagnetic transmissions). The non-transitory computer-readable medium does not necessarily include non-transitory data storage circuits (e.g., buffers, caches, and queues) within the transceiver of the transient signal. The process 500 may be implemented in various systems and methods described elsewhere in the present disclosure (such as in conjunction with Figures 1 to 4 In at least one embodiment, process 500 or a portion thereof is implemented by a controller system of a vehicle. In various embodiments, steps of process 500 and / or other processes are performed by a multi-access edge computing (MEC) server.

[0035] In various embodiments, process 500 includes a step 502 of obtaining a plurality of basic safety messages (BSMs) from one or more vehicles. In various embodiments, the vehicles emit data at regular intervals in the form of basic safety messages (BSMs). The data may include information about the state of the vehicle. For example, a vehicle may emit a data packet including its measured position (e.g., as GPS coordinates), the direction it is heading, its current speed, and so on. In various embodiments, the vehicle also collects lane data. For example, a vehicle may stream regular BSMs to a nearby network infrastructure, which routes the BSMs to a system (e.g., an MEC server) that performs process 500.

[0036] In various embodiments, process 500 includes determining the formation of a traffic queue based on the BSM 504. The traffic queue may be determined based on BSM data (including lane data) that vehicles are slowing down, are in close proximity to each other, or there may be other indications of queues, congestion, or other traffic conditions that vehicles are experiencing based on the BSM.

[0037] In various embodiments, process 500 includes a step 506 of determining a plurality of zone-based speed limits. The zone-based speed limits may be determined relative to a queue of traffic. For example, a first zone-based speed limit may encompass the queue itself, and there may be additional zone-based speed limits that have progressively larger values ​​based on distance from the queue, such as in conjunction with Figure 3 discussed.

[0038] In various embodiments, process 500 includes a step 508 of obtaining a message from a first vehicle approaching a traffic queue, wherein the message includes a location of the first vehicle and a speed of the first vehicle. The message may be a BSM having lane data indicating the location of the vehicle (e.g., GPS coordinates) and the speed of the vehicle. The vehicle may use one or more sensors (e.g., a camera) to determine lane data specifying a particular lane in which the vehicle is located.

[0039] In various embodiments, process 500 includes a step 510 of selecting an applicable zone-based speed limit from a plurality of zone-based speed limits based at least in part on the location of the first vehicle. The location of the vehicle may be mapped to one of the zones, and the zone may have a corresponding zone-based speed limit, e.g., as combined with Figure 3 as described.

[0040] In various embodiments, process 500 includes determining to generate one or more alerts based at least in part on a comparison between an applicable zone-based speed limit and the speed of the first vehicle 512. If the vehicle is traveling faster than the applicable zone-based speed limit, a zone-based speed alert may be provided to the vehicle.

[0041] In various embodiments, process 500 includes a step 514 of transmitting an alert. For example, a zone-based speed alert may be transmitted to vehicles approaching the queue. The last vehicle in the queue may receive an approaching vehicle alert of the presence of a rapidly approaching vehicle in the same lane, thereby providing the vehicle with an opportunity to change lanes or pull over on the shoulder. In some cases, multiple vehicles located at or near the end of the traffic queue receive alerts of rapidly approaching vehicles. In some embodiments, the alert includes instructions for causing an autonomous or semi-autonomous driving system to, for example, apply brakes, change the vehicle to a diverging lane, or take other precautions.

[0042] Figure 6A block diagram of an example of a machine 600 or system on which any one or more of the techniques (e.g., methods) discussed herein may be performed is shown. The machine (e.g., computer system) 600 may include any combination of the components shown. For example, the machine 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a tensor processing unit (TPU) including an artificial intelligence application specific integrated circuit (ASIC), a hardware processor core, or any combination thereof), a main memory 604, and a static memory 606, some or all of which may communicate with each other via an interconnect (e.g., a bus) 608. The machine 600 may also include a power management device 632, a graphics display device 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In an example, the graphics display device 610, the alphanumeric input device 612, and the UI navigation device 614 may be a touch screen display. The machine 600 may additionally include a storage device (i.e., a drive unit) 616, a signal generating device 618 (e.g., a data signal), a network interface device / transceiver 620 coupled to an antenna 630, and one or more sensors 628, such as a sound detection sensor (e.g., a microphone), an accelerometer, a magnetometer, a position sensor, etc. The machine 600 may include an output controller 634, such as a serial (e.g., Universal Serial Bus (USB)), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, other sensors, etc.).

[0043] The storage device 616 may include a machine-readable medium 622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 624 may also reside, in whole or in part, within the main memory 604, within the static memory 606, or within the hardware processor 602 during execution of the instructions 624 by the machine 600. In an example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute a machine-readable medium. In various embodiments, the controller system of the vehicle is implemented using one or more machines (e.g., the machine 600).

[0044] Although machine-readable medium 622 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (eg, a centralized or distributed database, and / or associated caches and servers) configured to store one or more instructions 624 .

[0045] Various embodiments may be implemented in whole or in part in software and / or firmware. This software and / or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable the execution of the operations described herein. The instructions may be in any suitable form, such as, but not limited to, source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such computer-readable media may include any tangible, non-transitory media for storing information in a form that can be read by one or more computers, such as, but not limited to, read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, and the like.

[0046] The term "machine-readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600; and causing the machine 600 to perform any one or more of the techniques of the present disclosure; or capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of machine-readable media may include solid-state memory and optical and magnetic media. In an example, a large-capacity machine-readable medium includes a machine-readable medium having a plurality of particles having a rest mass. Specific examples of large-scale machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

[0047] Instructions 624 may also be transmitted or received over a communication network 626 using a transmission medium via a network interface device / transceiver 620 utilizing any of a variety of transmission protocols (e.g., frame relay, Internet Protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include DOCSIS, fiber optics, a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (POTS) network, a wireless data network (e.g., a wireless network known as The Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, known as The IEEE 802.16 family of standards), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, etc. In an example, the network interface device / transceiver 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 626. In an example, the network interface device / transceiver 620 may include multiple antennas to communicate wirelessly using at least one of the following: single-input multiple-output (SIMO) technology, multiple-input multiple-output (MIMO) technology, or multiple-input single-output (MISO) technology. The term "transmission medium" should be taken to include any intangible medium that can store, encode, or carry instructions executed by the machine 600 and includes digital or analog communication signals or other intangible media to facilitate the communication of such software.

[0048] The operations and processes described and shown above may be implemented or performed in any suitable order when necessary in various implementations. In addition, in some implementations, at least a portion of the operations may be performed in parallel. In addition, in some implementations, fewer or more operations than the described operations may be performed.

[0049] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The terms "computing device", "user device", "communication station", "station", "handheld device", "mobile device", "wireless device" and "user equipment" (UE) as used herein refer to a wireless communication device such as a cable box, a wearable smart device, a cellular phone, a smart phone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal or other personal communication system (PCS) device. The device may be mobile or fixed.

[0050] As used in this document, the term "communication" is intended to include transmission or reception, or both transmission and reception. This may be particularly useful in claims when describing the organization of data transmitted by one device and received by another device, but requiring only the functionality of one of those devices violates the claims. Similarly, a two-way data exchange between two devices (during which both devices transmit and receive) may be described as "communication" when only the functionality of one of those devices is claimed. The term "communication" as used herein with respect to wireless communication signals includes transmitting wireless communication signals and / or receiving wireless communication signals. For example, a wireless communication unit capable of transmitting wireless communication signals may include a wireless transmitter for transmitting wireless communication signals to at least one other wireless communication unit and / or a wireless communication receiver for receiving wireless communication signals from at least one other wireless communication unit.

[0051] As used herein, unless otherwise indicated, the use of ordinal adjectives "first," "second," "third," etc. to describe common objects indicates merely that different instances of similar objects are mentioned and is not intended to imply that the objects so described must be in a given sequence in time, space, ranking, or in any other manner.

[0052] Some embodiments may be used in conjunction with various devices and systems, such as wearable smart devices, personal computers (PCs), desktop computers, mobile computers, laptop computers, notebook computers, tablet computers, server computers, handheld computers, handheld devices, personal digital assistant (PDA) devices, handheld PDA devices, vehicle-mounted devices, off-vehicle devices, hybrid devices, vehicle devices, non-vehicle devices, mobile or portable devices, consumer devices, non-mobile or non-portable devices, wireless communication stations, wireless communication devices, wireless access points (APs), wired or wireless routers, wired or wireless modems, video devices, audio devices, audio-video (A / V) devices, wired or wireless networks, wireless area networks, wireless video area networks (WVANs), local area networks (LANs), wireless LANs (WLANs), personal area networks (PANs), wireless PANs (WPANs), and the like.

[0053] Some embodiments may be used in conjunction with: one-way and / or two-way radio communication systems, cellular radio-telephone communication systems, mobile phones, cellular phones, cordless phones, personal communication system (PCS) devices, PDA devices including wireless communication devices, mobile or portable global positioning system (GPS) devices, devices including GPS receivers or transceivers or chips, devices including RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices with one or more internal antennas and / or external antennas, digital video broadcasting (DVB) devices or systems, multi-standard radio devices or systems, wired or wireless handheld devices (e.g., smart phones), wireless application protocol (WAP) devices, etc.

[0054] Some embodiments may be used in conjunction with one or more types of wireless communication signals and / or systems that comply with one or more wireless communication protocols, such as DOCSIS, radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), time division multiplexing (TDM), time division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi-tone (DMT), Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee, Ultra-Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data Rates for GSM Evolution (EDGE), etc. Other embodiments may be used in various other devices, systems and / or networks.

[0055] Embodiments according to the present disclosure are particularly disclosed in the attached claims, which relate to methods, storage media, devices and computer program products, wherein any feature mentioned in one claim category (e.g., method) may also be claimed in another claim category (e.g., system). The dependencies or references in the attached claims are selected for formal reasons only. However, any subject matter resulting from deliberate reference to any previous claim (especially multiple dependencies) may also be claimed, so that any combination of claims and their features is disclosed and may be claimed, regardless of the dependencies selected in the attached claims. The subject matter that may be claimed includes not only the combination of features set forth in the attached claims, but also any other combination of features in the claims, wherein each feature mentioned in the claims may be combined with any other feature in the claims or with a combination of other features. In addition, any of the embodiments and features described or depicted herein may be claimed in a separate claim and / or in any combination with any embodiment or feature described or depicted herein or with any feature of the attached claims.

[0056] The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0057] Certain aspects of the present disclosure are described above with reference to block diagrams and flow charts of systems, methods, devices and / or computer program products according to various implementations. It should be understood that one or more blocks of the block diagrams and flow charts and combinations of blocks in the block diagrams and flow charts may be implemented by computer executable program instructions, respectively. Likewise, according to some implementations, some blocks of the block diagrams and flow charts may not necessarily need to be executed in the order presented, or may not necessarily need to be executed at all.

[0058] These computer executable program instructions may be loaded onto a special purpose computer or other specific machine, processor, or other programmable data processing device to produce a specific machine, so that the instructions executed on the computer, processor, or other programmable data processing device create a device for implementing one or more functions specified in one or more flowchart blocks. These computer program instructions may also be stored in a computer-readable storage medium or memory, which may guide a computer or other programmable data processing device to function in a specific manner when executed, so that the instructions stored in the computer-readable storage medium produce a product including an instruction device that implements one or more functions specified in one or more flowchart blocks. As an example, some implementations may provide a computer program product, which includes a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, and the computer-readable program code is suitable for being executed to implement one or more functions specified in one or more flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operating elements or steps to be executed on a computer or other programmable device to produce a computer-implemented process, so that the instructions executed on a computer or other programmable device provide elements or steps for implementing the functions specified in one or more flowchart blocks.

[0059] Therefore, the blocks of the block diagrams and flow charts support a combination of means for performing the specified functions, a combination of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow charts and the combination of blocks in the block diagrams and flow charts can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions that performs the specified functions, elements or steps.

[0060] Implementations of the systems, devices, apparatuses, and methods disclosed herein may include or utilize a dedicated or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory as discussed herein. Computer executable instructions include, for example, instructions and data, which, when executed at a processor, cause a general-purpose computer, a dedicated computer, or a dedicated processing device to perform a specific function or group of functions. Implementations of the apparatus, systems, and methods disclosed herein may communicate via a computer network. A "network" is defined as one or more data links that support the transmission of electronic data between computer systems and / or modules and / or other electronic devices.

[0061] Although the subject matter has been described in language specific to structural features and / or methodological acts, it should be understood that the subject matter defined in the appended claims may not necessarily be limited to the features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

[0062] Although various embodiments of the present disclosure have been described above, it should be understood that various embodiments of the present disclosure are presented only by way of example and not by way of limitation. It will be understood by those skilled in the relevant art that various changes in form and detail may be made without departing from the spirit and scope of the present disclosure. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above exemplary embodiments, but should only be limited according to the attached claims and their equivalents. The foregoing description has been presented for the purpose of illustration and description. The foregoing description is not intended to be exhaustive or to limit the present disclosure to the precise form disclosed. In view of the above teachings, many modifications and variations are possible. In addition, it should be noted that any or all of the foregoing alternative implementations may be used in any desired combination to form additional hybrid implementations of the present disclosure. For example, any one of the functionalities described with respect to a particular device or component may be performed by another device or component. Unless otherwise specifically stated or otherwise understood in context when used, conditional languages ​​such as, in particular, "can", "may", "can" or "may" are generally intended to express that certain embodiments may include certain features, elements and / or steps, while other embodiments may not include certain features, elements and / or steps. Thus, such conditional language is generally not intended to imply that each feature, element, and / or step is in any way required for one or more embodiments.

[0063] According to one embodiment, the plurality of messages comprises lane data of the one or more vehicles.

[0064] According to one embodiment, as a result of execution by the one or more processors, the executable instructions further cause the one or more processors to: determine that both a second vehicle and the first vehicle are located in a lane of the traffic queue; and transmit a warning to the second vehicle, wherein the warning includes an indication of an approaching vehicle.

[0065] According to one embodiment, as a result of execution by the one or more processors, the executable instructions further cause the one or more processors to: transmit the warning to a third vehicle in the lane.

[0066] According to one embodiment, the plurality of messages are a plurality of Basic Safety Messages (BSMs).

[0067] According to one embodiment, the plurality of zone-based speed limits are determined relative to the traffic queue.

Claims

1. A method wherein include: Obtaining, by one or more processors of a multi-access edge computing (MEC) server, a plurality of messages from one or more vehicles; determining, by the one or more processors, formation of a traffic queue; determining, by the one or more processors, a plurality of zone-based speed limits; obtaining, by the one or more processors, a first message from a first vehicle approaching the traffic queue, wherein the message includes a position of the first vehicle and a speed of the first vehicle; selecting, by the one or more processors and based at least in part on the location of the first vehicle, an applicable zone-based speed limit from the plurality of zone-based speed limits; as well as Generating one or more alerts is determined by the one or more processors and based at least in part on a comparison between the applicable zone-based speed limit and the speed of the first vehicle.

2. The method according to claim 1, further comprising: include: An alert is transmitted, by the one or more processors, to the first vehicle, wherein the alert includes an indication that the speed of the first vehicle exceeds the applicable zone-based speed limit. 3 . The method of claim 1 , wherein the plurality of messages include lane data for the one or more vehicles.

4. The method according to claim 3, further comprising: include: determining, by the one or more processors, that both a second vehicle and the first vehicle are located in a lane of the traffic queue; as well as An alert is transmitted, by the one or more processors, to the second vehicle, wherein the alert includes an indication of an approaching vehicle.

5. The method according to claim 4, further comprising: include: The alert is transmitted by the one or more processors to a third vehicle in the lane.

6. The method of claim 1, wherein the plurality of messages are a plurality of basic safety messages (BSMs).

7. The method of claim 1, wherein the plurality of zone-based speed limits are determined relative to the traffic queue.

8. A non-transitory computer-readable storage medium storing executable instructions that, as a result of execution by one or more processors of a computer system of a vehicle, cause the computer system to at least: Obtain a plurality of messages from one or more vehicles; determining formation of a traffic queue based at least in part on the plurality of messages; Determine multiple zone-based speed limits; obtaining a message from a first vehicle approaching the traffic queue, wherein the message includes a position of the first vehicle and a speed of the first vehicle; selecting an applicable zone-based speed limit from the plurality of zone-based speed limits based at least in part on the location of the first vehicle; and A determination to generate one or more alerts is based at least in part on a comparison between the applicable zone-based speed limit and the speed of the first vehicle.

9. The non-transitory computer-readable storage medium of claim 8, wherein as a result of execution by the one or more processors, the executable instructions further cause the computer system to: An alert is transmitted to the first vehicle, wherein the alert includes an indication that the speed of the first vehicle exceeds the applicable zone-based speed limit.

10. The non-transitory computer-readable storage medium of claim 8, wherein the plurality of messages includes lane data for the one or more vehicles.

11. The non-transitory computer-readable storage medium of claim 10, wherein as a result of execution by the one or more processors, the executable instructions further cause the computer system to: determining that both a second vehicle and the first vehicle are located in a lane of the traffic queue; and An alert is transmitted to the second vehicle, wherein the alert includes an indication of an approaching vehicle.

12. The non-transitory computer-readable storage medium of claim 11, wherein as a result of execution by the one or more processors, the executable instructions further cause the computer system to: The warning is transmitted to a third vehicle in the lane.

13. The non-transitory computer-readable storage medium of claim 8, wherein the plurality of messages are a plurality of basic safety messages (BSMs).

14. A multi-access edge computing (MEC) server, include: one or more processors; as well as a memory storing executable instructions that, as a result of execution by the one or more processors, cause the one or more processors to: Obtain a plurality of messages from one or more vehicles; determining formation of a traffic queue based at least in part on the plurality of messages; Determine multiple zone-based speed limits; obtaining a message from a first vehicle approaching the traffic queue, wherein the message includes a position of the first vehicle and a speed of the first vehicle; selecting an applicable zone-based speed limit from the plurality of zone-based speed limits based at least in part on the location of the first vehicle; and A determination to generate one or more alerts is based at least in part on a comparison between the applicable zone-based speed limit and the speed of the first vehicle.

15. The server of claim 14, wherein as a result of execution by the one or more processors, the executable instructions further cause the one or more processors to: An alert is transmitted to the first vehicle, wherein the alert includes an indication that the speed of the first vehicle exceeds the applicable zone-based speed limit.

Images