DE102022120803A1 - ONE-SHOT TRANSMISSION FOR V2X MESSAGING - Google Patents

Abstract

A sequence of related messages is transmitted using Semi-Persistent Scheduling (SPS) of a predefined time period. A random value for a 1-shot duration timer is set, the random value being selected between a minimum and a maximum multiple of the predefined time period. In response to the expiration of the 1-shot duration timer, 1-shot resources are allocated for a 1-shot transfer, regardless of the SPS's allocated resources by SPS, and a next packet of the sequence of connected messages is sent as 1-shot message transmitted using the 1-shot resources instead of using the SPS's allocated resources.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

The present disclosure claims the benefit of US provisional application serial number 63/234,067 , filed August 17, 2021, the disclosure of which is hereby incorporated by reference in its entirety.

TECHNICAL AREA

Aspects of the present disclosure generally relate to 1-shot transmissions for cellular vehicle-to-everything (C-V2X) messaging.

BACKGROUND ART

Vehicle-to-everything (V2X) communication enables vehicles to exchange information with other vehicles, as well as with infrastructure, pedestrians, networks, and other devices. Vehicle-to-infrastructure communication (V2I communication) enables applications to facilitate and accelerate communication or transactions between vehicles and infrastructure.

EXECUTIVE SUMMARY

In one or more illustrative examples, a system for performing duration-based 1-shot messaging is provided. The system includes a transceiver and a controller. The controller is configured to transmit a sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined period of time, setting a random value for a 1-shot duration timer, where the random value is between a minimum and a maximum multiples of the predefined time period, and in response to the expiration of the 1-shot duration timer, allocate 1-shot resources for a 1-shot transfer independent of SPS-allocated resources of the SPS and a next packet of the sequence of to transmit associated messages as a 1-shot message using the 1-shot resources instead of using the SPS's allocated resources.

In one or more illustrative examples, a method for performing duration-based 1-shot messaging is provided. A sequence of connected messages is transmitted using SPS of a predefined time period. A random value for a 1-shot duration timer is set, the random value being selected between a minimum and a maximum multiple of the predefined time period. In response to the expiration of the 1-shot duration timer Shot, 1-shot resources are allocated for a 1-shot transmission, regardless of the SPS's allocated resources by SPS, and a next packet of the sequence of connected messages is sent transmitted as a 1-shot message using the 1-shot resources instead of using the SPS's allocated resources.

In one or more illustrative examples, a non-transitory computer-readable medium includes instructions for performing 1-shot duration-based messaging that, when executed by a controller in communication with a V2X transceiver, cause the controller to perform operations. The operations include transmitting a sequence of connected messages using SPS of a predefined time period; setting a random value for a 1-shot duration timer, the random value being selected between a minimum and a maximum multiple of the predefined time period; and in response to the expiration of the 1-shot duration timer, allocating 1-shot resources for a 1-shot transmission independent of SPS-allocated resources of the SPS and transmitting a next packet of the sequence of connected messages as a 1- Shot message using the 1-shot resources instead of using the SPS's allocated resources by SPS.

character list

• 1 illustrates an example system for use in vehicles that performs duration-based 1-shot messaging over V2X;
• 2 illustrates an example of 1-shot messaging using a counter-based 1-shot approach;
• 3 illustrates an alternative example of 1-shot messaging using the counter-based 1-shot approach under heavier load conditions;
• 4 Figure 12 illustrates an example of 1-shot messaging with a similar workload as the example, using a duration-based 1-shot transmission approach instead of a counter-based 1-shot approach;
• 5 illustrates an example of 1-shot messaging at a load similar to the example, using the duration-based 1-shot transmission approach;
• 6 illustrates an example process for performing aspects of duration-based 1-shot messaging over V2X;
• 7 illustrates an example process for performing additional aspects of duration-based 1-shot messaging over V2X; and
• 8th Figure 12 illustrates an example of a computing device for performing duration-based 1-shot messaging over V2X.

DETAILED DESCRIPTION

This document describes embodiments of the present disclosure. However, it should be understood that the disclosed embodiments are merely examples and that other embodiments may take various and alternative forms. The figures are not necessarily even to the staff; some features may be exaggerated or minimized to show details of specific components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching those skilled in the art to variously employ the embodiments. It will be appreciated by those of ordinary skill in the art that various features illustrated and described with reference to any one of the figures may be combined with features illustrated in one or more other figures to produce embodiments that are not expressly illustrated or are described. The illustrated combinations of features provide representative embodiments for typical applications. However, various combinations and modifications of the features consistent with the teachings of this disclosure might be desirable for particular applications.

Using C-V2X communication, vehicles broadcast BSMs to other vehicles in their vicinity. This may be done to enable V2X applications such as Electronic Emergency Brake Light (EEBL), Intersection Movement Assist (IMA) as some examples. Information age (IA) is a metric used to measure the age of the BSM information at the receiver for vehicles in the receiver's vicinity. The higher the IA, the higher the likelihood that the vehicle has accumulated tracking errors due to course changes, acceleration, etc. In dense vehicle environments, the IA distribution for BSM packets can have long tails. This can mean that vehicles have a low (but not zero) probability of missing several consecutive packets from nodes within their range.

In a C-V2X system, the media access layer on a node can allocate resources in the time and frequency domain for the V2X applications. This allocation can be used for 5-15 transmissions based on a randomly selected counter within this interval. For example, when the counter reaches 0, resources can be reselected with a 20% chance.

The resources can be selected by examining the energy measured in resource blocks for a certain period of time. However, when there are many vehicles, it is possible that several vehicles choose the same radio resources or at least time intervals (if two packets use the same time slot or 1ms subframe, they are invisible to their respective transmitters due to the half-duplex limitations of transceivers. This can happen even at low load). The probability increases with the number of vehicles. In these cases, the fact that the resources can be used for multiple BSM transmissions means that persistent collisions can occur, resulting in successive packet losses. This phenomenon can affect a vehicle's ability to track other vehicles in support of V2X applications.

As discussed in detail herein, a system for performing duration-based 1-shot messaging is provided. The system includes a transceiver and a controller. The controller is configured to transmit a sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined period of time, setting a random value for a 1-shot duration timer, where the random value is between a minimum and a maximum multiples of the predefined time period, and in response to the expiration of the 1-shot duration timer, allocate 1-shot resources for a 1-shot transfer independent of SPS-allocated resources of the SPS and a next packet of the sequence of associated messages using as a 1-shot message of the 1-shot resources instead of using the SPS's allocated resources. By using this improved approach, the transmission of the 1-shot message can avoid the possibility of persistent collisions and back-to-back packet losses that can occur with periodic transmissions by multiple vehicles. 1 12 illustrates an example system 100 for use in vehicles 102 that performs duration-based 1-shot messaging over V2X. The vehicle 102 may include various types of automobiles, CUVs (CUVs), sport utility vehicles (SUVs), trucks, recreational vehicles (RVs), boats, airplanes, or other mobile machines for transporting people or goods include. Such vehicles 102 may be human driven or autonomous. In many cases, the vehicle 102 may be powered by an internal combustion engine. As another possibility, the vehicle 102 may be a battery electric vehicle (BEV) powered by one or more electric motors. As another possibility, the vehicle 102 may be a hybrid electric vehicle (HEV) powered by both an internal combustion engine and one or more electric motors, such as a series hybrid electric vehicle (SHEV), a parallel hybrid electric vehicle (PHEV) or a parallel/series hybrid electric vehicle (PSHEV). The vehicle 102 may be an automated vehicle (AV) driven by a driver with driver assistance capabilities. These AV or driver support functions can be supported via received V2X data. The degree of automation can vary from different levels of driver assistance technology up to a fully automated, driverless vehicle. As the type and configuration of the vehicle 102 may vary, the capabilities of the vehicle 102 may vary accordingly. As some other possibilities, vehicles 102 may have different capabilities in terms of passenger capacity, towing capability and capacity, and storage space. Vehicles 102 may be assigned unique identifiers, such as vehicle identification numbers (VINs), for registration purposes, inventory purposes, and other purposes. It should be noted that while automobiles 102 are used as examples of road users, other types of road users may be used additionally or alternatively, such as bicycles, scooters, and pedestrians, which may be equipped with V2X technology.

The vehicle 102 may include a variety of controllers 104 configured to perform and manage various functions of the vehicle 102 using vehicle battery and/or powertrain power. As depicted, the example vehicle controls 104 are represented as discrete controls 104 (i.e., controls 104-A through 104-G). However, the vehicle controllers 104 may share physical hardware, firmware, and/or software such that the functions of multiple controllers 104 may be integrated into a single controller 104 and the functions of different such controllers 104 may be distributed among a plurality of controllers 104 .

As some non-limiting examples of vehicle controls 104: a powertrain controller 104-A may be configured to provide control of engine operating components (e.g., idle control components, fuel delivery components, emissions control components, etc.) and to monitor the status of such engine operating components (e.g., status of engine codes); A body controller 104-B may be configured to manage various power control functions, such as exterior lights, interior lights, keyless entry, remote start, and verification of the status of access points (e.g., closed status of the hood, doors, and/or trunk of the vehicle vehicle 102); a radio transceiver controller 104-C may be configured to communicate with radio keys, mobile devices, or other local devices of the vehicle 102; an autonomous controller 104-D may be configured to provide commands to control the powertrain, steering, or other aspects of the vehicle 102; a climate control management controller 104-E may be configured to provide control for heating and cooling system components (e.g., compressor clutch, blower fans, temperature sensors, etc.); a global positioning system (GPS) controller 104-F may be configured to provide vehicle location information; and a human-machine interface (HMI) controller 104-G may be configured to receive user input via various buttons or other controls, as well as provide a driver with vehicle status information, such as fuel level information, engine operating temperature information, and current location of the vehicle 102.

The vehicle 102 controllers 104 may use various sensors 106 to receive information related to the vehicle 102 environment. In an example For example, these sensors 106 may include one or more cameras (eg, advanced driver-assistance system (ADAS) cameras), ultrasonic sensors, radar systems, and/or lidar systems.

The vehicle bus 108 may include various communication methods available between the vehicle controllers 104 and between the telematics control unit (TCU) 110 and the vehicle controllers 104 . As some non-limiting examples, the vehicle bus 108 may include one or more of a controller area network (CAN), an Ethernet network, or a media-oriented system transfer (MOST) network of the vehicle. Other aspects of the construction and number of vehicle buses 108 are discussed in more detail below.

The TCU 110 may include network hardware configured to facilitate communication between the vehicle controllers 104 and with other system 100 devices. For example, the TCU 110 may include or otherwise access a cellular transceiver 112 configured to facilitate communication with other vehicles 102 or with infrastructure. Accordingly, the TCU 110 may be configured to communicate via various protocols, such as with a communication network via a network protocol (such as Uu). The TCU 110 may additionally be configured to communicate via a peer-to-peer transmission protocol (such as PC5) to enable C-V2X communications with devices such as other vehicles 102 . It should be noted that these protocols are only examples and different peer-to-peer and/or cellular technologies can be used.

The TCU 110 may include various types of computing devices to support the performance of the TCU 110 functions described herein. In one example, the TCU 110 may include one or more processors 114 configured to execute computer instructions and a storage medium 116 on which the computer-executable instructions and/or data may be maintained. A computer-readable storage medium (also referred to as processor-readable medium or tray 116) includes any non-transitory (e.g., physical) medium that participates in the delivery of data (e.g., instructions) to be executed by a computer (e.g., readable by the one or more processors. In general, processor 114 receives instructions and/or data, e.g. e.g., from memory 116, etc., in memory and executes the instructions using the data, thereby performing one or more processes that include one or more of the processes described herein. Computer-executable instructions may be compiled or interpreted by computer programs created using a variety of programming languages and/or technologies, including but not limited to and either alone or in combination, JAVA, C, C++, C#, FORTRAN, PASCAL, VISUAL BASIC, PYTHON , JAVA SCRIPT, PERL ETC.

The TCU 110 may be configured to include one or more interfaces from which vehicle information may be sent and received. This information can be collected, recorded and sent to cloud server 124 . In an example, cloud server 124 may also include one or more processors (not shown) configured to execute computer instructions and a storage medium (not shown) on which the computer-executable instructions and/or data may reside.

The TCU 110 may be configured to facilitate the collection of networked vehicle data and/or other vehicle information from the vehicle controllers 104 networked to the one or more vehicle buses 108 . Although only a single vehicle bus 108 is illustrated, it should be noted that multiple vehicle buses 108 are included in many examples, with a subset of the controllers 104 being networked to each vehicle bus 108 . Accordingly, to access a given controller 104, the TCU 110 may be configured to maintain an association of which vehicle buses 108 are networked to which controllers 104 and access the appropriate vehicle bus 108 for a controller 104 when communicating therewith specific controller 104 is desired.

The TCU 110 may also be configured to periodically transmit associated messages 122 for receipt by other vehicles 102 . For example, the frequency may be on the order of every ten milliseconds. The TCU 110 may also be configured to receive networked messages 122 from other vehicles 102 . In one example, management of sending and receiving data from a connected vehicle may be handled by a connected application 120 executed by the TCU 110 . The networked messages 122 may include aggregated information provided by the controllers 104 about the driving zeugbusse 108 can be accessed. In many examples, the collected information data may include information useful for autonomous vehicle operations or driver assistance vehicle operations. The connected vehicle information data retrieved by the TCU 110 may include, as some non-limiting examples, latitude, longitude, time, heading angle, speed, lateral acceleration, longitudinal acceleration, yaw rate, throttle position, braking condition, steering angle , headlight condition, wiper condition, exterior temperature, turn signal condition, vehicle length, vehicle width, vehicle mass, and bumper height. The connected vehicle information data may also include weather data (such as ambient temperature, atmospheric pressure, etc.), traction control status, windshield wiper status, or other vehicle status information (such as vehicle exterior lamp status, vehicle type, anti-lock braking (ABS) system status, etc .) include. In one example, the associated messages 122 may take the form of BSM messages, as described in the relevant standards document J2735 from the Society of Automotive Engineers (SAE).

Although not shown, in some examples, road users may additionally include communications via one or more roadside units (RSUs). The RSU may be a device with processing capabilities and networking capabilities and may be configured to be placed near the roadway 118 for use in communicating with the vehicles 102 . In one example, the RSU may include hardware configured to communicate via peer-to-peer transmission protocol (such as PC5) to facilitate C-V2X communications with vehicles 102 . Accordingly, the RSU may be able to communicate with multiple vehicles 102 along a specific lane 118 or in a specific area. The RSU may also have wired or wireless backhaul capability to enable communication with other elements of a traffic control system, e.g. B. via Ethernet or a cellular connection to the cellular network infrastructure, for example via a Uu interface.

The SAE J3161 standard specifies the minimum performance requirements for C-V2X BSMs. In general, BSMs can be transmitted using SPS, which is a reservation-based approach as opposed to the access contention-based approach used by dedicated short range communication (DSRC). Using SPS, periodic transmissions are allocated on the spectrum, rather than requiring the transmitter to periodically allocate resources to send each transmission. This may improve efficiency for messages sent from a vehicle 102 periodically. It is also possible to send messages for non-periodic events. These are referred to here as 1-shot transfer. J3161/1 mandates the use of 1-shot transfers intermittently based on a different random count between two and six. When this counter (referred to as the 1-shot counter) reaches zero, the vehicle 102 allocates a one-time set of resources to transmit the next BSM. Such 1-shot transmissions are intended to break a pattern of collisions that may occur. 2 FIG. 2 illustrates an example 200 for 1-shot messaging using a counter-based 1-shot approach. In the illustrated example 200, Max_ITT = 100 ms while the 1-shot count ranges from two to six. Such settings may be appropriate for cases where the utilization level of the V2X frequencies is low. The 1-shot timer starts sample 200 at a value of four. For each period, the 1-shot timer is decremented. The 1-shot transfer is performed in response to the counter reaching zero. This occurs twice in example 200 as shown.

3 Figure 300 illustrates an alternative example 300 for 1-shot messaging using the counter-based 1-shot approach under heavier load conditions. In the illustrated example 300, Max_ITT = 150 while the 1-shot count again ranges from two to six. Such settings may be appropriate for cases where the utilization level of the V2X frequencies is medium rather than low. As shown in the example 300 as opposed to the example 200, the 1-shot counter is only triggered once instead of twice. Logically, the higher ms Max_ITT, the rarer the 1-shot transmissions, resulting in higher IA values. In higher density environments, when a congestion control algorithm is invoked and the frequency of transmission of the associated message 122 decreases (eg, Max_ITT increases), it can be seen that with the 1-shot counter-based approach, gaps between the 1-shot Transmissions increase in a relevant way.

4 Figure 4 illustrates an example 400 for 1-shot messaging with a similar workload as example 200, using a duration-based 1-shot transmission approach instead of a counter-based 1-shot approach is used. In the duration-based approach, a minimum and a maximum can be specified as integer multiples of a minimum update interval T, e.g. B. T = 100 ms. These values can be adjusted so that the average represents the maximum time interval that the V2X application can tolerate for updates from other vehicles 102 . This can ensure that any persistent collisions occurring in the PLC resources are broken by the 1-shot transfer, regardless of the other factors such as the transfer rate variation (dictated by the rate control) and the PLC parameters.

As shown in example 400, Max_ITT = 100 ms while the 1-shot minimum and maximum range is 200 to 600 ms. In response to the 1-shot timer reaching zero before the intended transfer, the 1-shot transfer is triggered. This occurs twice in example 400.

5 Figure 5 illustrates an example 500 for 1-shot messaging with a similar workload as example 300 using the duration-based 1-shot transmission approach. As shown in example 500, Max_ITT = 150 ms while the 1-shot minimum and maximum range is again 200 to 600 ms. In response to the 1-shot timer reaching zero before the intended transfer, the 1-shot transfer is triggered. This occurs twice in example 500. Accordingly, the 1-shot timer in the counter-based 1-shot approach triggers the same number of 1-shot transmissions, regardless of load, compared to the reduced frequency of 1-shot transmissions in the counter-based 1-shot approach.

6 FIG. 6 illustrates an example process 600 for performing aspects of duration-based 1-shot messaging over V2X. In an example, the process 600 may be performed by the TCU 110 of the vehicle 102 in the context of the other vehicles 102 of the system 100 .

At operation 602 an upper layer packet arrives at the MAC layer at the TCU 110 . This packet may include data for transmission by the vehicle 102 in an associated message 122 . In one example, associated message 122 may be a BSM. The transmission of the connected message 122 can be used to activate AV or driver assistance functions for other vehicles 102 .

At operation 604, the TCU 110 determines whether a 1-shot transfer flag is set. This flag may be set as shown in process 700 below. If the 1-shot transfer flag is set, control transfers to process 606. Otherwise, control transfers to process 608.

At operation 606, the TCU 110 transmits the packet using PLC flow resources. These resources may have been pre-allocated by the TCU 110 of the vehicle 102 for the periodic transmission of associated messages 122 by the vehicle 102 .

At operation 608 , the TCU 110 allocates resources for the transmission of the associated 1-shot message 122 . These resources are separate from PLC operation and thus may not have been allocated by the TCU 110 of the vehicles 102 for the vehicle 102 to periodically transmit associated messages 122 .

At operation 610, the TCU 110 transmits the packet using a 1-shot transmission. Accordingly, the associated 1-shot message 122 is sent by the vehicle 102 . Since the 1-shot message is sent outside of the message transmission sequence in the SPS flow, the transmission of the 1-shot message can avoid the possibility of persistent collisions and consecutive packet losses that can occur when multiple vehicles 102 transmit periodically. Thus, by sending the 1-shot message in this approach, the system 100 can improve the ability of vehicles 102 to track other vehicles 102 to support V2X applications.

At operation 612, the TCU 110 sets the 1-shot duration counter to a random value. This random value can be specified as a number of milliseconds within a minimum and maximum transmission range. As discussed above, the minimum and maximum can be specified as integer multiples of a minimum update interval T, e.g. B. T = 100 ms. These values can be adjusted so that the average represents the maximum time interval that the V2X application can tolerate for updates from other vehicles 102 .

At operation 614, the TCU 110 starts the timer for transmission 1-shot of the associated message 122. The TCU 110 may also reset the transmission 1-shot flag to the unset state. After the timer expires, the 1-shot transmission flag can be set again so that it can be determined that the 1-shot transfer takes place. After operation 614, process 600 ends.

7 illustrates an example process 700 for performing additional aspects of duration-based 1-shot messaging over V2X. Like the process 600, the process 700 may be performed by the TCU 110 and/or one or more other controllers of the vehicle 102 in the context of the other vehicles 102 of the system 100. It should be noted that the process 700 is typically executed in a loop fashion, for example as a callback function for a timer that is set with a predefined periodic callback period (e.g., the period T discussed above).

At operation 702, the TCU 110 determines whether the 1-shot timer has expired. In one example, the TCU 110 may determine whether the current time from the time the timer started has exceeded the amount of time set for the 1-shot duration counter at operation 612 . In one implementation, this can be done periodically by subtracting the timer update interval from the counter on each cycle of a periodic message loop such that the timer expires once the timer counter is less than or equal to zero. If the timer expires, control transfers to process 704 where the TCU 110 sets the 1-shot transfer flag. Otherwise, control transfers to operation 706 where the TCU 110 leaves the 1-shot transfer flag unset. After operation 706, the process 700 ends. Thus, the disclosed approach ensures that sustained collisions occurring in the PLC resources are broken by the 1-shot transfer. Since the disclosed approach is not counter-based but time-based, it provides the same time interval statistics between consecutive 1-shot transmissions regardless of the congestion level, which the counter-based method does not. Accordingly, the disclosed approach is robust to fluctuations in the BSM rate dictated by rate control and traffic density. In addition, the disclosed approach significantly improves IA and packet spacing under heavy loads.

8th Figure 8 illustrates an example 800 of a computing device 802 for performing duration-based 1-shot messaging over V2X. With reference to 8th and referring to 1-7 Vehicles 102, controllers 104, TCU 110, and cloud server 124 may be examples of such computing devices 802. As shown, the computing device 802 includes a processor 804 operatively connected to a data store 806 , a network device 808 , an output device 810 , and an input device 812 . Note that this is just an example and computing devices 802 can be used with more, fewer, or different components.

Processor 804 may include one or more integrated circuits that implement central processing unit (CPU) and/or graphics processing unit (GPU) functionality. In some examples, processors 804 are a system on a chip (SoC) that integrates CPU and GPU functionality. The SoC may optionally include other components such as data storage 806 and network device 808 in a single integrated device. In other examples, the CPU and GPU are coupled together via a peripheral connection device, such as Peripheral Component Interconnect (PCI) Express or other suitable peripheral data connection. In one example, the CPU is a commercially available central processing device that implements an instruction set, such as one of the x86, ARM, Power, or Microprocessor Without Interlocked Pipeline Stage (MIPS) instruction set families.

Regardless of the details, processor 804 executes stored program instructions retrieved from data storage 806 during operation. Accordingly, the stored program instructions include software that controls the operation of the processors 804 to perform the operations described herein. Data storage 806 may include both non-volatile memory and volatile memory. Non-volatile memory includes the following: Solid state memory, such as Not AND (NAND) flash memory, magnetic and optical storage media, or any other suitable data storage device that retains data when the system is disabled or its power is removed. The volatile memory includes static and dynamic random-access memory (RAM) on which program instructions and data are stored during system 100 operation.

The GPU may include hardware and software for displaying at least two dimensional (2D) and optionally three dimensional (3D) graphics on the output device 810 . The output device 810 can be a graphical or visual display device, such as an electronic display screen, a projector, a printer, or any other suitable device direction that reflects a graphic display. As another example, the output device 810 may include an audio device, such as a speaker or a headphone. As yet another example, the output device 810 may include a tactile device, such as a mechanically incrementable device, which in one example may be configured to display braille or other physical output that can be touched to provide information to a user.

Input device 812 may include any of various devices that enable computing device 802 to receive control input from users. Examples of suitable input devices that receive input via a human interface may include keyboards, mice, trackballs, touch screens, voice input devices, graphics tablets, and the like.

Network devices 808 may each include any of various devices that enable vehicles 102 and cloud server 124 to send and/or receive data from external devices over networks. Examples of suitable network devices 808 include an Ethernet interface, a Wi-Fi transceiver, a cellular transceiver, a BLUETOOTH or BLUETOOTH Low Energy (BLE) transceiver, or other network adapter or peripheral connection device that/ receiving data from another computer or external data storage device, which can be useful for receiving large data sets in an efficient manner.

The processes, methods, or algorithms disclosed herein may be deliverable/implemented by a processing device, controller, or computer, which may include any existing programmable electronic control unit or dedicated electronic control unit. Likewise, the processes, methods, or algorithms can be stored as data and instructions executable by a controller or computer in many forms, the information being persistently stored on non-writable data storage media, such as read-only memory devices. memory only - ROM), and information alterably stored on writable data storage media such as floppy disks, magnetic tape, compact discs (CDs), RAM devices, and other magnetic and optical media. The processes, methods, or algorithms may also be implemented in a software executable object. Alternatively, the processes, methods, or algorithms may be implemented in whole or in part using suitable hardware components, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), state machines, controllers, or others Hardware components or devices, or a combination of hardware, software, and firmware components.

While exemplary embodiments are described above, these embodiments are not intended to describe all possible forms that are encompassed by the claims. The terms used in the specification are words of description rather than limitation, and it is understood that various changes can be made without departing from the spirit and scope of the disclosure. As previously described, the features of various embodiments can be combined to form further embodiments of the disclosure that may not be expressly described or illustrated. Although various embodiments may have been described as advantageous or preferred over other embodiments or implementations of the prior art with respect to one or more desired properties, those of ordinary skill in the art will recognize that compromises may be made in one or more features or properties in order to achieve the desired overall attributes of the system, which depend on the specific application and implementation. These attributes may include, but are not limited to, cost, strength, durability, life cycle cost, marketability, appearance, packaging, size, maintainability, weight, manufacturability, ease of assembly, etc. Accordingly, to the extent that any embodiment is described as being less desirable than other prior art embodiments or implementations with respect to one or more characteristics, those embodiments are not beyond the scope of the disclosure and may be desirable for particular applications.

With respect to the processes, systems, methods, heuristics, etc. described herein, it should be understood that while the steps of such processes, etc. have been described as occurring according to some ordered sequence, such processes could be implemented in practice, wherein the described steps be performed in an order determined by the order described in this document differs. It is further understood that certain steps could be performed simultaneously, that other steps could be added, or that certain steps described herein could be omitted. In other words, the descriptions of processes in this document are for the purpose of illustrating certain embodiments and should in no way be construed as limiting the claims.

Accordingly, it is to be understood that the foregoing description is intended to be illustrative and not restrictive. Many other embodiments and applications, other than the examples provided, will become apparent from reading the foregoing description. The scope should not be determined with reference to the foregoing description, but should instead be determined with reference to the appended claims, along with the full range of equivalents to which such claims are entitled. It is anticipated and intended that there will be future developments in the prior art discussed herein and that the disclosed systems and methods will be incorporated into such future embodiments. As a whole, it should be understood that the application is capable of modification and variation.

All terms used in the claims are intended to be given their broadest reasonable interpretation and their general meanings as known to those skilled in the art and technologies described in this specification, unless expressly stated otherwise in this specification. In particular, the use of singular articles, such as "a", "an", "the", "the", "the", etc., should be understood to refer to one or more of the specified items, unless a The claim states an express limitation to the contrary.

The Summary of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it will be apparent that various features in various embodiments are grouped together for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.

While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the disclosure. Rather, the terms used in the specification are words of description rather than limitation, and it is understood that various changes can be made without departing from the spirit and scope of the disclosure. Additionally, the features of different implementing embodiments can be combined to form further embodiments of the disclosure.

According to the present invention there is provided a system for performing duration-based 1-shot messaging, comprising: a transceiver; and a controller configured to transmit a sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined period of time, setting a random value for a 1-shot duration timer, the random value between a minimum and a maximum multiple of the predefined time period, and in response to the expiration of the 1-shot duration timer, allocate 1-shot resources for a 1-shot transfer independent of SPS-allocated resources of the SPS and a next packet transmit the sequence of associated messages as a 1-shot message using the 1-shot resources instead of using the SPS's allocated resources.

According to one embodiment, the transceiver and controller are embedded in a vehicle-to-everything (V2X) capable vehicle in communication with other V2X vehicles.

According to one embodiment, the transceiver and controller are embedded in a roadside unit in communication with V2X-enabled vehicles. According to one embodiment, the sequence of connected messages is formed according to the relevant standards document J2735 of the Society of Automotive Engineers (SAE).

According to one embodiment, the minimum and maximum multiples of the predefined time period are set as integer multiples of the predefined time period. According to one embodiment, the maximum multiple of the predefined time period is set as a maximum time interval that a V2X application will tolerate for updates from other vehicles.

According to one embodiment, the predefined time period is of the order of 100 ms, the minimum is twice the predefined time period and the maximum is six times the predefined time period.

According to the present invention, a method for performing duration-based 1-shot messaging includes transmitting a sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined period of time; setting a random value for a 1-shot duration timer, the random value being selected between a minimum and a maximum multiple of the predefined time period; and in response to the expiration of the 1-shot duration timer, allocating 1-shot resources for a 1-shot transmission independent of SPS-allocated resources of the SPS and transmitting a next packet of the sequence of connected messages as a 1- Shot message using the 1-shot resources instead of using the SPS's allocated resources by SPS.

In one aspect of the invention, the sequence of associated messages is formed in accordance with the relevant standards document J2735 of the Society of Automotive Engineers (SAE).

In one aspect of the invention, the minimum and maximum multiples of the predefined time period are set as integer multiples of the predefined time period. In one aspect of the invention, the maximum multiple of the predefined time period is set as a maximum time interval that a V2X application will tolerate for updates from other vehicles.

In one aspect of the invention, the predefined time period is on the order of 100 ms, the minimum is twice the predefined time period and the maximum is six times the predefined time period.

According to the present invention, there is provided a non-transitory computer-readable medium having instructions for performing duration-based 1-shot messaging that, when executed by a controller in communication with a V2X transceiver, cause the controller to perform operations including: transmitting a Sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined time period; setting a random value for a 1-shot duration timer, the random value being selected between a minimum and a maximum multiple of the predefined time period; and in response to the expiration of the 1-shot duration timer, allocating 1-shot resources for a 1-shot transmission independent of SPS-allocated resources of the SPS and transmitting a next packet of the sequence of connected messages as a 1- Shot message using the 1-shot resources instead of using the SPS's allocated resources by SPS.

According to one embodiment, the transceiver and controller are embedded in a vehicle-to-everything (V2X) capable vehicle in communication with other V2X vehicles.

According to one embodiment, the transceiver and controller are embedded in a roadside unit in communication with V2X-enabled vehicles. According to one embodiment, the sequence of connected messages is formed according to the Society of Automotive Engineers (SAE) standard document J2735.

According to one embodiment, the minimum and maximum multiples of the predefined time period are set as integer multiples of the predefined time period. According to one embodiment, the maximum multiple of the predefined time period is set as a maximum time interval that a V2X application will tolerate for updates from other vehicles.

According to one embodiment, the predefined time period is of the order of 100 ms, the minimum is twice the predefined time period and the maximum is six times the predefined time period.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• US63/234067 [0001]

Claims (15)

A system for performing duration-based 1-shot messaging, comprising: a transceiver; and a controller configured to: transmitting a sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined period of time; setting a random value for a 1-shot duration timer, the random value being selected between a minimum and a maximum multiple of the predefined time period, and in response to the 1-shot duration timer expiring, allocating 1-shot resources for a 1-shot transmission independently of SPS-allocated resources of the SPS and transmitting a next packet of the sequence of connected messages as a 1-shot -Message using the 1-shot resources instead of using the SPS's allocated resources by SPS. system after claim 1 wherein the transceiver and controller are embedded in a vehicle-to-everything (V2X) capable vehicle in communication with other V2X vehicles. system after claim 1 wherein the transceiver and controller are embedded in a roadside unit in communication with V2X-enabled vehicles. system after claim 1 , wherein the sequence of associated messages is formed in accordance with the relevant standards document J2735 of the Society of Automotive Engineers (SAE). system after claim 1 , where the minimum and maximum multiples of the predefined period are specified as integer multiples of the predefined period. system after claim 1 , where the maximum multiple of the predefined period is set as a maximum time interval that a V2X application will tolerate for updates from other vehicles. system after claim 1 , where the predefined time period is of the order of 100 ms, the minimum is twice the predefined time period and the maximum is six times the predefined time period. A method for performing duration-based 1-shot messaging, comprising: transmitting a sequence of connected messages using Semi-Persistent Scheduling (SPS) of a predefined period of time; setting a random value for a 1-shot duration timer, the random value being selected between a minimum and a maximum multiple of the predefined time period; and in response to the 1-shot duration timer expiring, allocating 1-shot resources for a 1-shot transmission independently of SPS-allocated resources of the SPS and transmitting a next packet of the sequence of connected messages as a 1-shot -Message using the 1-shot resources instead of using the SPS's allocated resources by SPS. procedure after claim 8 , wherein the sequence of associated messages is formed in accordance with the relevant standards document J2735 of the Society of Automotive Engineers (SAE). procedure after claim 8 , where the minimum and maximum multiples of the predefined period are set as integer multiples of the predefined period. procedure after claim 8 , where the maximum multiple of the predefined period is set as a maximum time interval that a V2X application will tolerate for updates from other vehicles. procedure after claim 8 , where the predefined time period is of the order of 100 ms, the minimum is twice the predefined time period and the maximum is six times the predefined time period. Non-transitory computer-readable medium includes instructions for performing duration-based 1-shot messaging that, when executed by a controller in communication with a V2X transceiver, cause the controller to perform operations that include: transmitting a sequence of connected messages using semi -Persistent Scheduling (SPS) of a predefined period; setting a random value for a 1-shot duration timer, the random value being selected between a minimum and a maximum multiple of the predefined time period; and in response to the expiration of the 1-shot duration timer, allocating 1-shot resources for a 1-shot transmission independent of SPS-allocated resources of the SPS and transmitting a next packet of the sequence of connected messages as a 1- Shot message using the 1-shot resources instead of the Use of the SPS's resources allocated by SPS. medium after Claim 13 wherein one or more of the following apply: the transceiver and the controller are embedded in a vehicle-to-everything (V2X) capable vehicle in communication with other V2X vehicles; the transceiver and controller are embedded in a roadside unit in communication with V2X-enabled vehicles. medium after Claim 13 , wherein one or more of the following apply: the minimum and maximum multiples of the predefined time period are set as integer multiples of the predefined time period; the maximum multiple of the predefined time period is set as a maximum time interval that a V2X application will tolerate for updates from other vehicles; or the predefined time period is of the order of 100 ms, the minimum is twice the predefined time period and the maximum is six times the predefined time period.

Images