HK1251843B - Techniques to configure vehicle to anything communications - Google Patents

Description

Technologies for configuring vehicle-to-everything communications

Related applications

This application claims priority to U.S. Provisional Patent Application Serial No. 62/191,770, filed on July 13, 2015, which is hereby incorporated by reference herein in its entirety.

Technical Field

Embodiments herein generally relate to communications between devices in a broadband wireless communication network.

Background Art

Vehicle-to-everything (V2X) refers to intelligent transportation systems that enable vehicles and infrastructure systems to communicate data and information. The information transmitted within V2X systems can be used for a variety of applications, including safety, mobility, and environmental applications. For example, V2X connectivity provides more accurate situational awareness across road networks, enabling optimization of traffic flow, reduction of congestion, fewer accidents, and lower emissions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1A illustrates an embodiment of a first operating environment.

FIG. 1B shows an embodiment of a first device.

FIG2 illustrates an embodiment of a second operating environment.

FIG3 illustrates an embodiment of a third operating environment.

FIG4 shows an embodiment of a first configuration process.

FIG5 shows an embodiment of a second configuration process.

FIG6 shows an embodiment of a third configuration process.

FIG. 7A shows an embodiment of a message format for transmitting parameters.

FIG. 7B illustrates an embodiment of a second message format for transmitting parameters.

FIG8 shows an embodiment of a storage medium.

FIG9 shows an embodiment of a second device.

FIG10 shows an embodiment of a third device.

FIG11 illustrates an embodiment of a wireless network.

DETAILED DESCRIPTION

Intelligent Transportation Systems (ITS), enabled by connected vehicles, can improve safety and efficiency on the roads. The Wireless Access in Vehicular Environment (WAVE) architecture and standards have been developed to support both safety and non-safety applications of ITS. The WAVE standard is based on IEEE 802.11p (i.e., Dedicated Short Range Communications (DSRC)), thus supporting V2X communications (which include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-pedestrian (V2P) communications).

Previous studies have shown that the downlink capacity of Long Term Evolution (LTE) limits its ability to handle the permanent broadcasts of traditional ITS systems, such as cooperative awareness messages (CAMs) at 10 Hertz (Hz). For example, it was observed that for a 5-megahertz (MHz) spectrum, only 10 vehicles per cell can receive CAM data sent simultaneously by 40 neighboring vehicles with a delay of 100 milliseconds (ms). Therefore, a slower transmission rate of 2 Hz and/or a smaller number of broadcasting vehicles is more capacity-friendly.

To optimize air interface resource utilization and avoid congestion, the network may implement additional functionality that can be used to better configure V2X operations. For example, a device such as a roadside unit (RSU) at an intersection may have a more comprehensive view of the surrounding environment than each individual vehicle. The RSU uses various sensors to detect traffic volume, the average speed of vehicles, the presence of pedestrians, the presence of accidents, and so on. Thus, the RSU can use its environmental awareness capabilities to better coordinate the frequency or message transmission rate at which vehicles send V2X communications. The same is true for other devices such as radio access network (RAN) nodes, user equipment (UE), content provider systems, and so on. These and other details will become more apparent in the following description.

Various embodiments may include one or more elements. Elements may include any structure that is arranged to perform certain operations. Each element may be implemented as hardware, software or any combination thereof, as required for a given set of design parameters or performance constraints. Although embodiments may be described with a limited number of elements in a specific topology by way of example, embodiments may include more or less elements in alternative topologies as required for a given implementation. It is noteworthy that any reference to "one embodiment" or "embodiment" means that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment. The phrases "in one embodiment", "in some embodiments" and "in various embodiments" that appear in various places in the specification do not necessarily all refer to identical embodiments.

The technology disclosed herein may involve transmitting data over one or more wireless connections using one or more wireless mobile broadband technologies. For example, various embodiments may involve transmission over one or more wireless connections in accordance with one or more Third Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE), and/or 3GPP LTE Advanced (LTE-A) technologies and/or standards (including their amendments, successors, and variants). Various embodiments may additionally or alternatively involve transmission in accordance with one or more Global System for Mobile Communications (GSM)/Enhanced Data Rates for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS)/High Speed Packet Access (HSPA), and/or GSM with General Packet Radio Service (GPRS) systems (GSM/GPRS) technologies and/or standards (including their amendments, successors, and variants).

Examples of wireless mobile broadband technologies and/or standards may also include, but are not limited to, any Institute of Electrical and Electronics Engineers (IEEE) 802.11p, Dedicated Short Range Communications (DSRC), International Mobile Telecommunications Advanced (IMT-ADV), Worldwide Interoperability for Microwave Access (WiMAX) and/or WiMAX II, Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), High Performance Radio Metropolitan Area Network (HIPERMAN), Wireless Broadband (WiBro), High Speed Downlink Packet Access (HSDPA), High Speed Orthogonal Frequency Division Multiplexing (OFDM) Packet Access (HSOPA), High Speed Uplink Packet Access (HSUPA) technologies and/or standards, including their amendments, successors and variants.

Some embodiments may additionally or alternatively involve wireless communications according to other wireless communication technologies and/or standards. Examples of other wireless communication technologies and/or standards that may be used in various embodiments may include, but are not limited to, other IEEE wireless communication standards (e.g., IEEE 802.11, IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, IEEE 802.11u, IEEE 802.11ac, IEEE 802.11ad, IEEE 802.11af, and/or IEEE 802.11ah, IEEE 802.11p standards), standards implemented by the IEEE High-efficiency Wi-Fi standards developed by the 802.11 High-Efficiency WLAN (HEW) study group, Wi-Fi Alliance (WFA) wireless communication standards (e.g., Wi-Fi, Wi-Fi Direct, Wi-Fi Direct Service, Wireless Gigabit (WiGig), WiGig Display Extensions (WDE), WiGig Bus Extensions (WBE), WiGig Serial Extensions (WSE) standards, and/or standards developed by the WFA Neighbor Awareness Networking (NAN) Task Group), Machine Type Communication (MTC) standards (e.g., those implemented in 3GPP Technical Report (TR) 23.887, 3GPP Technical Specification (TS) 22.368, and/or 3GPP TS 23.682), and/or Near Field Communication (NFC) standards (e.g., standards developed by the NFC Forum), including any amendments, successors, and/or variants thereof. Embodiments are not limited to these examples.

In addition to transmission over one or more wireless connections, the technology disclosed herein may involve transmitting content over one or more wired connections via one or more wired communication media. Examples of wired communication media may include wires, cables, metal leads, printed circuit boards (PCBs), backplanes, switch fabrics, semiconductor materials, twisted pairs, coaxial cables, optical fibers, and the like. The embodiments are not limited in this context.

FIG1A illustrates an example of an operating environment 100 that can represent various embodiments. Operating environment 100 may include any number of user equipment (UEs) 104-n (where n can be any positive integer) and a roadside unit (RSU) 106. In some embodiments, RSU 106 may be a fixed UE or an evolved Node B (eNB). Note that embodiments may include more than one RSU 106, which may be implemented in other devices, such as traffic lights, light poles, signs, trash cans, and the like.

The operating environment 100 may also include a radio access network (RAN) node 108, which may be an eNB capable of serving the cell 103. For example, the RAN node 108 may provide wireless connectivity to the UE 104-n and the RSU 106 via a wireless carrier of the cell 103. During ongoing operation, the RAN node 108 may identify and coordinate data to be sent to the UE 104-n and the RSU 106. The RAN node 108 is typically a fixed station that communicates with the UE 104-n and the RSU 106 and may be referred to by another term, such as a base station (BS), an access point, etc. As will be discussed in more detail below, the RAN node 108 may transmit information to the UE 104-n and the RSU 106 to coordinate vehicle-to-everything (V2X) communications between the devices.

In some embodiments, the operating environment 100 may be an intelligent transportation system that implements V2X communication, which may, for example, improve road safety and efficiency. V2X communication may enable vehicles with UEs 104-n to communicate with each other and with the RSU 106. V2X communication may include vehicle information, traffic information, location information, road condition information, road obstacle information, emergency vehicle information, intersection information, and the like.

In some embodiments, UE 104-n and RSU 106 may communicate V2X communications via one or more communication links 102-m, where m may be any positive integer. V2X communications may include V2V communications via V2V applications, V2P communications via V2P applications, and V2I communications via V2I applications. In one example embodiment, V2V communications and V2P communications may be communicated between UE 104-n, and V2I communications may be communicated between UE 104 and RSU 106. Embodiments are not limited in this manner.

Traditional system architectures for delivering vehicle-to-vehicle communications were typically developed with different requirements in mind, such as public safety (e.g., voice communications between first responders) and consumer applications (e.g., advertising, location information, social networking, etc.). These traditional systems typically transmit messages at a specified transmission rate (e.g., 10 Hertz (Hz)). As a result, these traditional systems are not scalable enough to effectively meet the latency and number of supported vehicles required for V2X communications.

Some conventional systems allow for the repetition rate of communications to be adjusted through a decentralized congestion control process within a station or UE. This process is used to reduce potential congestion and is decentralized, as each station makes its own decisions without input from other devices or the network. However, in these decentralized systems, older messages in the transmit queue may be discarded during periods of severe congestion. Therefore, embodiments involve adapting the transmission rate and implementing congestion control in a more centralized manner, for example, via RAN node 108.

For example, to optimize air interface resource utilization and avoid congestion, the network or devices (e.g., RAN node 108, UE 104-n, and RSU 106) may implement additional functionality that can be used to better configure V2X operations and communications. For example, one or more devices may include one or more sensors to form a comprehensive view of the surrounding environment. Devices using various sensors can collect environmental information, such as the volume of traffic (vehicles and communications) in a cell, the average speed of vehicles in a cell, the presence of pedestrians in a cell, the presence of accidents in a cell, and so on. Thus, the devices have extensive environmental awareness capabilities and can transmit this information to another device (e.g., RAN node 108) to better coordinate the message transmission rates used by UE 104 and RSU 106 to transmit V2X communications and data. Note that in some cases, environmental information can be collected by multiple devices to provide a more comprehensive view of the surrounding environment for transmission to RAN node 108. Embodiments are not limited in this manner.

For example, the RAN node 108 may receive environmental information from one or more other devices and use the environmental information to determine V2X parameters. For example, the RAN node 108 may determine a message transmission rate for subsequent V2X communications based on these environmental characteristics. For example, the message transmission rate may be the frequency at which the UE 104 and the RSU 106 within the operating environment 100 transmit V2X communications.

In some embodiments, the RAN node 108 may determine V2X parameters based on other information (e.g., cellular information including a latency requirement for V2X communications). For example, the latency requirement may be a specified maximum amount of time between transmissions of V2X communications, such as 1000 milliseconds (ms), 100 ms, 10 ms, etc. In some embodiments, the latency requirement may directly correspond to the frequency or message transmission rate at which V2X communications are transmitted. Thus, the RAN node 108 may use this latency requirement information to determine the message transmission rate and V2X parameters for V2X communications.

Other cellular information may include the cell load of the cell and the number of UEs 104 and RSUs 106 using V2X services in the cell, and may also be used to determine V2X parameters. Embodiments are not limited in this manner. In one example, the message transmission rate may be set to a lower frequency in a high vehicle traffic area and to a higher frequency in a low vehicle traffic area. Similarly, the message transmission rate may be set to a lower frequency in a high communication traffic area and to a higher frequency in a low communication traffic area, which may be based on vehicle traffic and/or the number of pedestrians. In another example, when one or more accidents are detected, the message transmission rate may be set to a higher frequency than when no accidents are detected.

In some embodiments, the RAN node 108 may transmit the V2X parameters in a message to one or more devices, such as the UE 104 and the RSU 106. For example, the RAN node 108 may use RRC signaling to send a radio resource control (RRC) message including the V2X parameters to one or more other devices. In this example, the V2X parameters may be transmitted in a system information block (SIB) on a broadcast channel. In another example, the RAN node 108 may include the V2X parameters in a message sent directly to the one or more other devices using multicast or unicast. In some embodiments, the RAN node 108 may utilize a service such as the Multimedia Broadcast Multicast Service (MBMS) to transmit the V2X parameters via broadcast or multicast. In a third example, the RAN node 108 may use media access control (MAC) signaling to transmit the V2X parameters to the one or more other devices in a MAC header of a MAC protocol data unit (PDU). Embodiments are not limited in this manner.

The receiving device may use V2X parameters to configure V2X settings for transmitting subsequent V2X communications. V2X parameters may include message periodicity, PSID, and other V2X parameters for 3GPP and non-3GPP technologies. Other specified V2X parameters may include, but are not limited to, the type of transmission protocol (IP vs. non-IP), the type of resource allocation method, carrier information, the type of transmission technology (DSRC vs. 3GPP), and the like. This embodiment is not limited thereto.

FIG1B shows an example of a UE 104 for transmitting V2X communications. The UE 104, which includes multiple components and circuits, is capable of storing, processing, and transmitting information and data. The UE 104 includes a memory 120, circuitry 122 including logic 124, and a transceiver 126.

In an embodiment, the memory 120 may be any type of memory capable of storing information and data. For example, the memory 120 may store temporary variables and instructions, such as logic 124 that may be processed by the circuit 122. The memory 120 may be one or more of a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory, etc. The memory 120 is not limited to these memory components. For example, the memory 120 may include a non-transitory computer-readable storage medium. In some embodiments, the memory 120 may be a volatile memory or a non-volatile memory.

In some embodiments, the memory 120 may store data, such as V2X settings 215, that may be used to communicate V2X communications. The V2X settings 215 may include settings for one or more V2X communications over one or more communication links and may be based on V2X parameters. As previously discussed, the V2X settings 215 may include message transmission rates, PSIDs, and other settings for each V2X communication established between the UE 104 and one or more other devices. Note that each V2X communication may have different V2X settings 215 based on the requirements of the V2X communication, available resources, environmental factors, cellular information, and the like.

UE 104 may also include circuitry 122 that may implement and process logic 124, e.g., one or more instructions. Circuitry 122 may be part of a processor, a processing component, a computer processing unit, or the like. Circuitry 122 may process information and instructions for UE 104, e.g., those implemented as logic 124. Circuitry 122 may be a circuit that executes instructions of a computer program by performing basic arithmetic, logic, control, and input/output (I/O) operations specified by the instructions. For example, circuitry 122 may include an arithmetic logic unit (ALU) that performs arithmetic and logic operations. Circuitry 122 may also include a control unit that fetches instructions from a memory (e.g., memory 120) and "executes" them by directing coordinated operation of the ALU, registers, and other components. The embodiments are not limited in this manner, and the above description merely provides a high-level overview of the processing of circuitry 122.

In an embodiment, UE 104 may also include a transceiver 126 coupled to an antenna 128. As described above, transceiver 128 may include one or more radios capable of transmitting and receiving signals using various suitable wireless communication techniques according to one or more standards. The embodiments are not limited in this manner.

FIG2 illustrates an example of an operating environment 200 that may represent an implementation of one or more of the disclosed V2X parameter communication techniques for configuring one or more devices to transmit subsequent V2X communications. In some cases, the operating environment 200 may include a RAN node 108 and a UE 104. Note that embodiments are not limited in this manner, and the operating environment generally includes any number of UEs 104 capable of receiving V2X parameters for V2X communication. In some cases, the V2X parameters may also be received by one or more RSUs, which may be configured in a manner similar to that discussed herein. Embodiments may also include more than one RAN node, and the operating environment is not so limited.

The RAN node 108 may include a memory 218 and circuitry 222, wherein the circuitry 222 implements and includes logic 224. For example, the RAN node 108 may also include a transceiver 226 for determining and transmitting the V2X parameters 210. The RAN node 108 may be capable of processing and transmitting information, such as information related to V2X communications.

In operation, the RAN node 108 may receive an indication of a V2X communication from another device or transmit a desire for subsequent V2X communication. Additionally, the RAN node 108 may receive environmental information and cellular information, such as the type of traffic for the V2X communication, the volume of communication traffic in a communication area or cell, the volume of vehicle traffic in the communication area or cell, the average speed of vehicles in the communication area or cell, the presence of pedestrians in the communication area or cell, the presence of accidents in the communication area or cell, latency requirements for the V2X communication, and the like. The RAN node 108 may determine to change one or more V2X settings 215 for subsequent V2X communication based on the environmental information and/or cellular information.

More specifically, the RAN node 108 may determine V2X parameters based on the environmental information and the cellular information, and transmit the V2X parameters 210 to the UE 104 (and other UEs 104 and/or RSUs 106) in a message(s) to enable the UE 104 to configure V2X settings 215 for subsequent V2X communications and thereby transmit V2X data 220. The V2X parameters 210 may specify a message transmission rate and a PSID for the V2X communications. In some instances, the actual message transmission rate and PSID may be transmitted to the UE 104 in the message. In other instances, the message transmission rate and PSID may be transmitted as one or more values, which the UE 104 may use to determine the actual message transmission rate and/or PSID for the V2X communications. For example, a message periodicity integer value associated with the message transmission rate may be transmitted to the UE 104 in the message. For example, the UE 104 may receive the message including the message periodicity integer value and determine the appropriate message transmission rate based on a lookup in a table. In another example, a string value identifying the PSID can be transmitted to UE 104 in a message. For example, the string value can be the actual PSID, or it can be information used by UE 104 to look up the PSID in a table. As will be discussed in more detail below, the same message can include a message periodicity integer value for the message transmission rate and a string value for the PSID. The embodiments are not limited in this manner.

In some cases, the V2X parameters 210 may include information for V2X communications transmitted using 3GPP technology and non-3GPP technology (e.g., Dedicated Short Range Communication (DSRC)). For example, a message may include a message periodicity integer value associated with a message transmission rate for V2X communications using 3GPP technology. The same or different message may include a message periodicity DSRC integer value associated with a message transmission rate for V2X communications using non-3GPP technology. Embodiments are not limited in this manner, and other technologies may be added to the message as appropriate.

In some embodiments, the RAN node 108 may transmit the V2X parameters 210 in a broadcast message via a broadcast channel. More specifically, the V2X parameters 210 may be included in a new or existing SIB that is transmitted to the UE 104 via the broadcast channel using RRC signaling. The SIB including the V2X parameters 210 may be transmitted as a broadcast message to the UE 104 and any other devices, such as other UEs and RSUs, within range of receiving the broadcast. The UE 104 may receive and process the V2X parameters 210 to configure V2X settings 215. Once configured, the UE 104 may conduct V2X communications in accordance with the V2X settings 215, thereby transmitting V2X data 220 with devices (e.g., other UEs and RSUs).

In some embodiments, the RAN node 108 may transmit V2X parameters 210 to the UE 104 using a dedicated message using RRC signaling. For example, the RAN node 108 may send the V2X parameters 210 directly to the UE 104 in a message using multicast addressing or unicast addressing. As similarly discussed above, the V2X parameters 210 may include a message transmission rate and a PSID for subsequent V2X communications between the UE 104 and other devices. In an embodiment, the RAN node 108 transmitting and utilizing the dedicated message may configure and set different V2X settings 215 for different UEs 104. For example, the RAN node 108 may transmit first V2X parameters 210 directly to the UE 104 to establish V2X settings for the UE 104. The UE 104 may receive the V2X parameters 210, process the V2X parameters 210, and set the V2X settings 215 based on the V2X parameters 210 to conduct V2X operations with at least one other device. The RAN node 108 may establish different V2X communications for another device (e.g., another UE or RSU) by transmitting different dedicated messages with different (or the same) V2X parameters to the device. The device may receive different V2X parameters and set different V2X settings to transmit the V2X communication. Any number of V2X communications may be established between devices, and these devices may have the same or different V2X settings based on the same or different V2X parameters. The embodiments are not limited in this manner.

In some embodiments, the RAN node 108 may transmit the V2X parameters 210 to the UE 104 in a MAC header of a MAC PDU. In some cases, for example, the V2X parameters 210 may be transmitted in the MAC header of the MAC PDU using MAC signaling on a broadcast channel or a multicast channel. In some embodiments, the RAN node 108 may receive a message from another UE or UE 104 that includes the V2X parameters 210 or information indicating desired settings for V2X communication. The RAN node 108 may generate or add a MAC header including the V2X parameters 210 at the MAC layer for use in subsequent V2X communication. More specifically, the RAN node 108 may broadcast or multicast the MAC PDU with the MAC header including the V2X parameters 210 to the UE 104 and devices within range (e.g., other UEs and RSUs) for use in subsequent V2X communication. As a result, all or at least some of the other devices may transmit V2X communication based on the V2X parameters 210 received in the MAC header of the MAC PDU. For example, a UE 104 in the operating environment 200 may receive V2X parameters 210 in a MAC header of a MAC PDU from the RAN node 108, process the V2X parameters 210, and set V2X settings 215 for subsequent V2X communications with one or more other devices, including the originating UE 104. The embodiments are not limited in this manner, and other devices may perform similar operations.

FIG3 illustrates an example operating environment 300, which may represent an implementation of one or more of the disclosed V2X parameter communication techniques for configuring one or more devices to transmit subsequent V2X communications. In one or more embodiments, for example, a Multimedia Broadcast Multicast Service (MBMS) system 305 providing channels to support an MBMS 302 may be used to configure UEs and RSUs for V2X communications. The MBMS 302 may be a functional entity and may provide services including MBMS bearer services and MBMS user services through an MBMS Broadcast Multicast Service Center (BM-SC), an MBMS Gateway (GW), a Mobility Management Entity (MME), and the like. Note that the MBMS system 305 may include one or more computing devices (e.g., nodes) for providing MBMS services.

In some embodiments, for example, the MBMS system 305 can receive cellular information 310, which can include cellular measurements sent by any number of other RAN nodes 108-k (e.g., eNBs and RSUs 106-p) via the MBMS GW. In this illustrated embodiment, the MBMS system 305 can use the cellular information 310 to generate V2X parameters 210 to configure devices to transmit V2X communications. In some instances, the MBMS system 305 can receive the cellular information from a content provider 350 (e.g., an Intelligent Transportation System (ITS) content provider) for use in generating the V2X parameters 210. Embodiments are not limited in this manner.

Cellular measurements may include the cellular load of a communication area or cell, the number of devices utilizing V2X services in the communication area or cell, and the latency requirement for subsequent V2X communications. Furthermore, the cellular load may be a measurement of the amount of communication traffic in a cell at a specific point in time, or may be an average of the amount of communication traffic within a specific time frame. The number of devices may include the number of UEs and RSUs communicating within the cell, and the latency requirement may be the maximum amount of time between V2X communication transmissions.

In some embodiments, the MBMS system 305 can determine whether the current V2X settings support V2X communication based on the received cellular information 310. If the current V2X settings support the requirements, the MBMS system 305 may not transmit new V2X parameters 210 to change the V2X settings 215. However, if the device's current V2X settings do not support the requirements specified in the cellular information 310 or the V2X settings 215 cannot be determined, the MBMS system 305 may transmit V2X parameters 210 to adjust the V2X settings 215 for the receiving device. For example, the MBMS system 305 may broadcast or multicast the V2X parameters 210 to one or more UEs 104 and/or RSUs 106 using services provided by MBMS 302. In some embodiments, the MBMS system 305 may transmit the V2X parameters 210 to the device using 3GPP technology and/or non-3GPP technology. Note that the MBMS system 305 may determine the V2X parameters 210 for communication based on the cellular information 310 and, in some instances, other information (e.g., environmental information that may be received from the RAN node 108-k, the RSU 106-p, and the content provider 350).

In some instances, one or more of the RAN nodes 108-k may determine the V2X parameters 210 and transmit them to the UE 104 and RSU 106 via the MBMS system 305 that provides communication services (e.g., multicast services and broadcast services). In other words, the MBMS system 305 may operate as a communication service provider to transmit messages and information between the RAN node 108-k, the RSU 106-p, the content provider 350, and other devices (e.g., the UE 104), thereby providing the V2X parameters 210 to one or more other devices. For example, the content provider 350 and/or one or more RSUs 106-p may provide information, such as cellular information 310, environmental information, etc., to one or more RAN nodes 108-k via the MBMS system 305. The RAN node 108-k may receive and use the information to determine the V2X parameters 210, which may be transmitted to other devices, such as the UE 104, via the MBMS system 305.

The UE and RSU (eg, UE 104) that receive the V2X parameters 210 may process the V2X parameters 210 and generate V2X settings 215 for subsequent V2X communication. For example, the UE and RSU may then perform subsequent V2X communication to transmit V2X data 220 between each other.

4 illustrates an example of a first configuration process 400 that may be representative of some embodiments discussed herein. For example, the configuration process 400 may illustrate operations performed by the RAN node 108. However, the embodiments are not limited in this manner, and one or more operations discussed below may be performed by other devices (e.g., the UE 104 or the RSU 106).

At block 405, the configuration process 400 may include determining V2X parameters for subsequent V2X communications. For example, the V2X parameters may be based on environmental information, such as vehicle traffic volume, average vehicle speed, presence of pedestrians, presence of accidents, and the like. The environmental information may be determined/detected by one or more sensors (not shown), such as those implemented in a UE, RSU, eNB, and the like. In some instances, the information may be measured and/or calculated by components of one or more other devices and transmitted to the determining device. The embodiments are not limited in this manner.

In some embodiments, the V2X parameters may also be based on cellular information, such as cellular load, the number of devices utilizing V2X services, and latency requirements for subsequent V2X communications. In one example using cellular load, the message transmission rate may be lower when the cellular load is high (above a load threshold) and higher when the cellular load is low (below a load threshold). The threshold may be predetermined and/or set by a user of the system. In some instances, the message transmission rate may be inversely proportional to the cellular load. Embodiments are not limited in this manner, and similar determinations may be made using the number of devices utilizing V2X services, e.g., the message transmission rate may be lower when the number of devices is high and higher when the number of devices is low.

In another example, latency requirements can be used to determine V2X parameters. For example, cooperative adaptive cruise control (CACC), V2I/V2N traffic flow optimization, and curve speed warnings require a 1000 millisecond delay. Road safety services through infrastructure require a 500ms delay. Autonomous driving, on the other hand, has very strict requirements of 1ms latency. Compared to traffic with more stringent latency requirements, the UE and RSU may transmit V2X communications less frequently or at a lower message transmission rate for traffic with less stringent latency requirements. More specifically, the message transmission rate for CACC communications may be lower than that for road safety service communications and autonomous driving communications. In another example, the message transmission rate for road safety service communications may be higher than the message transmission rate for CACC communications, but lower than the message transmission rate for autonomous driving communications. Embodiments are not limited to these examples, and other environmental and cell characteristics may be used to determine V2X parameters.

Configuration process 400 may also include, at block 410, generating a message including V2X parameters. As previously described, the V2X parameters may be included in the message using a new or existing SIB. In another example, the V2X parameters may be included in a message transmitted directly to another device. In a third example, the V2X parameters may be included in a MAC header of a MAC PDU. Embodiments are not limited in this manner.

Furthermore, at block 415, configuration process 400 may include transmitting a message to at least one other device. As previously described, the message may be transmitted via broadcast, multicast, or unicast. For example, a message including a new or existing SIB may be transmitted via a broadcast channel using RRC signaling. In another example, a direct message may be transmitted to another device via multicast or unicast using RRC signaling. In a third example, V2X parameters may be transmitted in a MAC PDU using broadcast, multicast, or unicast communication via MAC signaling. Embodiments are not limited in this manner.

5 illustrates an example of a second configuration process 500 that may be representative of some embodiments discussed herein. For example, the configuration process 500 may illustrate operations performed by the UE 104, the RSU 106, or another device.

At block 505, the configuration process 500 may include receiving a message including V2X parameters. The V2X parameters may include a message transmission rate for communicating over a 3GPP network, a message transmission rate for communicating over a non-3GPP network (e.g., DSRC), a PSID of the network, and one or more other V2X parameters. The V2X parameters may be received in a broadcast, multicast, or unicast message transmitted from another device (e.g., a RAN node 108 or, in some instances, an RSU 106). Furthermore, the message may include a new or existing SIB with the V2X parameters, a MAC PDU with the V2X parameters in a MAC header, and/or may be a direct message. Embodiments are not limited in this manner.

The configuration process 500 also includes configuring one or more V2X settings for subsequent V2X communications based on the V2X parameters. More specifically, the V2X parameters can be transmitted as values that need to be processed by the receiving device to determine the V2X parameters. For example, the message transmission rate can be transmitted as a message periodicity integer value (e.g., an integer value between one and ten (1-10)). The integer value can be converted into a frequency value, for example, the integer value of one can be converted into one Hertz (Hz). Therefore, in some instances, the integer value can be a frequency value. However, in some instances, the integer value may not directly correspond to the frequency value. For example, the integer value can range from 1 to 20, while the frequency can range from 1 Hz to 10 Hz. Therefore, an even (or odd) integer value can represent 1/2 Hz based on the starting value. The embodiments are not limited in this manner.

Additionally, the V2X parameters may include a PSID as a PSID string value, which may be used to configure the V2X settings so that the correct PSID is used to transmit V2X communications. For example, the PSID string value may represent an abbreviation or some other representation corresponding to the PSID. Embodiments are not limited in this manner.

In some embodiments, the V2X parameters may include parameters for non-3GPP communications. For example, the V2X parameters may include a message periodicity DSRC integer value corresponding to a message transmission rate for V2X communications using a non-3GPP radio technology. As similarly discussed above, the message periodicity DSRC integer value may be used in a manner similar to that discussed above for the message periodicity integer value.

At block 515, the configuration process 500 may include subsequent communication with at least one other device. For example, one or more UEs and/or RSUs may send and receive one or more messages containing V2X data with one or more other UEs and/or RSUs. The V2X data may include vehicle information, traffic information, location information, road condition information, road obstacle information, emergency vehicle information, intersection information, and the like.

6 illustrates an example of a third configuration process 600 that may be representative of some embodiments discussed herein.For example, configuration process 600 may illustrate operations performed by MBMS system 305 providing a service (eg, MBMS 302).

At block 605, the configuration process 600 may include receiving cellular information, the cellular information including at least one of a cellular load, a number of devices utilizing V2X services, and a latency requirement for subsequent V2X communications. The cellular load may be a measurement of the amount of communication traffic in a cell at a specific point in time, or may be an average of the amount of communication traffic within a specific time frame. The number of devices may include the number of UEs and/or RSUs communicating within the cell, and the latency requirement may be a maximum amount of time between transmissions of V2X communications. In some instances, the latency requirement may be based on the communication type of the subsequent V2X communications. Note that the cellular information may be received, for example, from one or more RAN nodes, RSUs, and/or content providers, or determined by the RAN node itself.

In some embodiments, configuration process 600 may include determining one or more V2X parameters based on cellular information at block 610. For example, embodiments may include setting a message transmission rate for V2X communications based on cellular load, the number of devices utilizing V2X services, and latency requirements. In some instances, embodiments may include determining V2X parameters based on environmental information in addition to cellular information. Embodiments are not limited in this manner.

At block 615, configuration process 600 may also include generating a message including V2X parameters. As previously described, the V2X parameters may be included in a message with a new or existing SIB. In another example, the V2X parameters may be included in a message transmitted directly to another device. In a third example, the V2X parameters may be included in a MAC header of a MAC PDU. Embodiments are not limited in this manner.

Furthermore, at block 620, configuration process 600 may include transmitting a message to at least one other device. As previously described, the message may be transmitted via broadcast, multicast, or unicast. For example, a message including a new or existing SIB may be transmitted via a broadcast channel. In another example, a direct message may be transmitted via multicast or unicast. In a third example, the V2X parameters may be transmitted in a MAC PDU in a broadcast, multicast, or unicast communication. Embodiments are not limited in this manner.

In some embodiments, one or more devices (e.g., a UE and/or an RSU) may receive V2X parameters, process the V2X parameters, and configure V2X settings for subsequent V2X communications, for example, as previously discussed in FIG5 . The devices may transmit V2X communications including V2X data based on the V2X parameters. Embodiments are not limited in this manner.

7A/7B illustrate example message formats 700 and 750 that may include V2X parameters 210 for transmission to another device to configure V2X communication. More specifically, FIG7A illustrates a radio resource control (RRC) message 700 including an SIB 720 with the V2X parameters 210. In some embodiments, the SIB 720 may be a new SIB or an existing SIB defined in one or more specifications (e.g., 3GPP TS 36.331).

In an example embodiment, the information element (IE) SystemInformationBlockTypeX may be used to transmit V2X parameters as follows:

SystemlnformationBlockTypeX IE

Table 1

Furthermore, as defined in Table 1, the message periodicity may be an integer value between 1 and 10 and is used to determine the message transmission rate used to transmit subsequent V2X communications. For example, an integer value of 10 may correspond to 10 Hz, and an integer value of 1 may correspond to 1 Hz. As previously mentioned, embodiments are not limited in this manner.

In another example, the network can also define message periodicity for other non-3GPP radio technologies. The following is an example of a SIB that defines message periodicity for DSRC and LTE. The SIB in this example can be applied to UEs that support LTE and DSRC or other non-3GPP technologies. These other technologies can be added as appropriate.

SystemInformationBlockTypeX information element

Table 2

Note that the message periodicity can be an integer value between 1 and 10 and is used to determine the message transmission rate for transmitting subsequent V2X communications via 3GPP technology. Similarly, the message periodicity DSRC can include the maximum allowed period for non-3GPP communications. The message periodicity DSRC can also be an integer value between 1 and 10 and is used to determine the message transmission rate for transmitting subsequent V2X communications. Note that embodiments are not limited to these integer values and other values can be used as the message periodicity parameter.

In a third example, additional fields may be added to one of the above SIBs as shown below.

SystemInformationBlockTypeX information element

Table 3

As described in Table 3, the message periodicity may include the maximum allowed period for 3GPP communications. Furthermore, the PSID identifies the application service using V2X communication. The V2X ProSe function may use the PSID value to determine the type of communication service the V2X UE is authorized to use. Note that other fields may be added to the SIB for communication with other devices. Embodiments are not limited to these example SIBs. For example, other SIBs may be defined based on other fields included as V2X parameters.

FIG7B shows a MAC PDU 750 having a MAC header 760 and a MAC payload 770. The MAC header 760 may include the V2X parameters 210 and multiple MAC subheaders (not shown). In some embodiments, the MAC subheaders may include the V2X parameters 210. The MAC header 760 may also include multiple other fields (not shown), such as a logical channel ID (LCID) field, a length field, a format field, and an extension field. Embodiments are not limited in this manner.

As previously discussed, the V2X parameters 210 may be added to the MAC header 760 by a device (e.g., an eNB, a RAN node, or an RSU) at the MAC layer. In some cases, the MAC header 760 may be added to one or more messages generated by another device (e.g., a UE) and added by the RAN node, eNB, or RSU for broadcast or multicast within a cell or communication area. The embodiments are not limited in this manner.

FIG8 illustrates an embodiment of a storage medium 800 and an embodiment of a storage medium 850. Storage media 800 and 850 may include any non-transitory computer-readable storage medium or machine-readable storage medium, such as optical, magnetic, or semiconductor storage media. In various embodiments, storage media 800 and 850 may include articles of manufacture. In some embodiments, storage media 800 and 850 may store computer-executable instructions, such as computer-executable instructions for implementing logic flows 400, 500, and 600, respectively. Examples of computer-readable storage media or machine-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and the like. Examples of computer-executable instructions may include any appropriate type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, and the like. The embodiments are not limited in this context.

As used herein, the term "circuit" may refer to, may be part of, or may include an application specific integrated circuit (ASIC), an electronic circuit, a (shared, dedicated, or group) processor and/or (shared, dedicated, or group) memory that executes one or more software or firmware programs, combinational logic circuits, and/or other appropriate hardware components that provide the described functionality. In some embodiments, the circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, the circuit may include logic that is at least partially operable in hardware. The embodiments described herein may be implemented as a system using any appropriately configured hardware and/or software.

9 shows an example of a UE device 900 that can represent a UE that implements one or more disclosed techniques in various embodiments. For example, the UE device 900 can represent the UE 104 according to some embodiments. In some embodiments, the UE device 900 can include at least application circuitry 902, baseband circuitry 904, radio frequency (RF) circuitry 906, front-end module (FEM) circuitry 908, and one or more antennas 910, coupled together as shown.

Application circuitry 902 may include one or more application processors. For example, application circuitry 902 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and specialized processors (e.g., graphics processors, application processors, etc.). The processor(s) may be coupled to and/or include memory/storage devices and may be configured to execute instructions stored in the memory/storage devices to enable various applications and/or operating systems to run on the system.

The baseband circuitry 904 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 904 may include one or more baseband processors and/or control logic to process baseband signals received from the receive signal path of the RF circuitry 906 and generate baseband signals for the transmit signal path of the RF circuitry 906. The baseband processing circuitry 904 may interface with the application circuitry 902 for generating and processing baseband signals and for controlling the operation of the RF circuitry 906. For example, in some embodiments, the baseband circuitry 904 may include a second generation (2G) baseband processor 904a, a third generation (3G) baseband processor 904b, a fourth generation (4G) baseband processor 904c, and/or one or more other baseband processors 904d for other existing generations, generations in development, or generations to be developed in the future (e.g., fifth generation (5G), 6G, etc.). Baseband circuitry 904 (e.g., one or more of baseband processors 904a-d) may handle various radio control functions to support communication with one or more radio networks via RF circuitry 906. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 904 may include fast Fourier transform (FN), precoding, and/or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuitry of baseband circuitry 904 may include convolution, tail-biting, turbo, Viterbi, and/or low-density parity check (LDPC) encoder/decoder functions. Embodiments of the modulation/demodulation and encoder/decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

In some embodiments, the baseband circuitry 904 may include elements of a protocol stack, such as elements of the Evolved Universal Terrestrial Radio Access Network (EUTRAN) protocol, including, for example, physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. The central processing unit (CPU) 904e of the baseband circuitry 904 may be configured to execute signaling elements of the protocol stack for the PHY, MAC, RLC, PDCP, and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processors (DSPs) 904f. The audio DSP(s) 904f may include elements for compression and/or decompression and/or echo cancellation, and in other embodiments may include other suitable processing elements. In some embodiments, the components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or suitably arranged on the same circuit board. In some embodiments, some or all of the components of the baseband circuitry 904 and the application circuitry 902 may be implemented together, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 904 can provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 904 can support communications with the Evolved Universal Terrestrial Radio Access Network (EUTRAN) and/or other wireless metropolitan area networks (WMANs), wireless local area networks (WLANs), and wireless personal area networks (WPANs). Embodiments in which the baseband circuitry 904 is configured to support radio communications of multiple wireless protocols can be referred to as multi-mode baseband circuitry.

RF circuitry 906 may support communication with a wireless network using modulated electromagnetic radiation over a non-solid medium. In various embodiments, RF circuitry 906 may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. RF circuitry 906 may include a receive signal path, which may include circuitry for down-converting RF signals received from FEM circuitry 908 and providing a baseband signal to baseband circuitry 904. RF circuitry 906 may also include a transmit signal path, which may include circuitry for up-converting baseband signals provided by baseband circuitry 904 and providing an RF output signal to FEM circuitry 908 for transmission.

In some embodiments, RF circuitry 906 may include a receive signal path and a transmit signal path. The receive signal path of RF circuitry 906 may include mixer circuitry 906a, amplifier circuitry 906b, and filter circuitry 906c. The transmit signal path of RF circuitry 906 may include filter circuitry 906c and mixer circuitry 906a. RF circuitry 906 may also include synthesizer circuitry 906d for synthesizing a frequency spectrum for use by mixer circuitry 906a in the receive signal path and the transmit signal path. In some embodiments, mixer circuitry 906a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 908 based on the synthesized frequency provided by synthesizer circuitry 906d. Amplifier circuitry 906b may be configured to amplify the downconverted signal, and filter circuitry 906c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 904 for further processing. In some embodiments, the output baseband signal may be a zero-frequency baseband signal, but this is not required.In some embodiments, the mixer circuit 906a of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this respect.

In some embodiments, mixer circuit 906a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 906d to generate an RF output signal for FEM circuit 908. The baseband signal can be provided by baseband circuit 904 and can be filtered by filter circuit 906c. Filter circuit 906c can include a low-pass filter (LPF), but the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion, respectively. In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuit 906a of the receive signal path and the mixer circuit 906a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 906 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 904 may include a digital baseband interface for communicating with RF circuitry 906.

In some dual-mode embodiments, separate radio integrated circuit (IC) circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, synthesizer circuit 906 d may be a fractional-N synthesizer or a fractional-N/N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, synthesizer circuit 906 d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

Synthesizer circuit 906d may be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 906a of RF circuit 906. In some embodiments, synthesizer circuit 906d may be a fractional-N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage-controlled oscillator (VCO), but this is not required. The divider control input can be provided by baseband circuitry 904 or application processor 902, depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) can be determined from a lookup table based on the channel indicated by application processor 902.

The synthesizer circuit 906d of the RF circuit 906 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on the implementation) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to decompose the VCO cycle into a maximum of Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuit 906d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and can be used in conjunction with a quadrature generator and divider circuit to generate multiple signals at the carrier frequency with multiple phases different from each other. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 906 can include an IQ/polarity converter.

FEM circuitry 908 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 910, amplify the received signals, and provide the amplified versions of the received signals to RF circuitry 906 for further processing. FEM circuitry 908 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 906 for transmission by one or more of the one or more antennas 910.

In some embodiments, the FEM circuitry 908 may include a TX/RX switch to switch between transmit and receive modes of operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low noise amplifier (LNA) to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 906). The transmit signal path of the FEM circuitry 908 may include a power amplifier (PA) to amplify an input RF signal (e.g., provided by the RF circuitry 906) and may include one or more filters to generate an RF signal for subsequent transmission (e.g., via one or more antennas 910).

In some embodiments, the UE device 900 may include additional elements, such as memory/storage, a display, a camera, sensors, and/or input/output (I/O) interfaces.

FIG10 illustrates an embodiment of a communications device 1000 that may implement one or more of UE 104, RSU 106, process flows 400, 500, and 600, storage medium 800, storage medium 850, and UE 900. In various embodiments, device 1000 may include logic circuitry 1028. Logic circuitry 1028 may include physical circuitry for performing operations described, for example, with respect to one or more of UE 104, RSU 106, process flows 400, 500, and 600, and UE 900 of FIG9. As shown in FIG10, device 1000 may include a radio interface 1010, baseband circuitry 1020, and a computing platform 1030, although embodiments are not limited to this configuration.

The device 1000 may implement some or all of the structure and/or operations for one or more of the UE 104, RSU 106, process flows 400, 500, and 600, storage medium 800, storage medium 850, and UE 900, and logic circuitry 1028 in a single computing entity, such as an entity within a single device. Alternatively, the device 1000 may use a distributed system architecture (e.g., a client-server architecture, a 3-tier architecture, an N-tier architecture, a tightly coupled or clustered architecture, a peer-to-peer architecture, a master-slave architecture, a shared database architecture, and other types of distributed systems) to distribute portions of the structure and/or operations for one or more of the UE 104, RSU 106, process flows 400, 500, and 600, storage medium 800, storage medium 850, and UE 900, and logic circuitry 1028 across multiple computing entities. The embodiments are not limited in this context.

In one embodiment, the radio interface 1010 may include a component or combination of components suitable for transmitting and/or receiving single-carrier or multi-carrier modulated signals (e.g., including complementary code keying (CCK), orthogonal frequency division multiplexing (OFDM), and/or single-carrier frequency division multiple access (SC-FDMA) symbols), but embodiments are not limited to any particular air interface or modulation scheme. The radio interface 1010 may include, for example, a receiver 1012, a frequency synthesizer 1014, and/or a transmitter 1016. The radio interface 1010 may include a deviation control, a crystal oscillator, and/or one or more antennas 1018-f. In another embodiment, the radio interface 1010 may use an external voltage-controlled oscillator (VCO), a surface acoustic wave filter, an intermediate frequency (IF) filter, and/or an RF filter, as needed. Due to the variety of potential RF interface designs, a comprehensive description thereof is omitted.

The baseband circuitry 1020 can communicate with the radio interface 1010 to process receive and/or transmit signals and can include, for example, a mixer for downconverting received RF signals, an analog-to-digital converter 1022 for converting analog signals to digital form, a digital-to-analog converter 1024 for converting digital signals to analog form, and a mixer for upconverting signals for transmission. Furthermore, the baseband circuitry 1020 can include baseband or PHY processing circuitry 1026 for physical layer (PHY) link layer processing of corresponding receive/transmit signals. The baseband circuitry 1020 can include, for example, medium access control (MAC) processing circuitry 1027 for MAC/data link layer processing. The baseband circuitry 1020 can include a memory controller 1032 for communicating with the MAC processing circuitry 1027 and/or the computing platform 1030, for example, via one or more interfaces 1034.

In some embodiments, PHY processing circuitry 1026 may include a frame construction and/or detection module in combination with additional circuitry, such as a buffer memory, to construct or deconstruct communication frames. Alternatively or additionally, MAC processing circuitry 1027 may share processing for some of these functions or perform these processes independently of PHY processing circuitry 1026. In some embodiments, MAC and PHY processing may be integrated into a single circuit.

The computing platform 1030 may provide computing functionality for the device 1000. As shown, the computing platform 1030 may include a processing component 1040. In addition to or in lieu of the baseband circuitry 1020, the device 1000 may use the processing component 1040 to perform processing operations or logic for one or more of the UE 104, the RSU 106, the process flows 400, 500, and 600, the storage medium 800, the storage medium 850, and the UE 900, and the logic circuitry 1028. The processing component 1040 (and/or the PHY 1026 and/or the MAC 1027) may include various hardware elements, software elements, or a combination of both. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processor circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory cells, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. Examples of software elements may include software components, programs, applications, computer programs, application programs, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols, or any combination thereof. Determining whether to use hardware elements and/or software elements to implement an embodiment may vary depending on any number of factors, such as the desired computing rate, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints desired for a given implementation.

The computing platform 1030 may also include other platform components 1050. Other platform components 1050 include common computing elements, such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components (e.g., digital displays), power supplies, etc. Examples of memory cells may include, but are not limited to, various types of computer-readable and machine-readable storage media in the form of one or more higher-speed memory cells, such as read-only memory (ROM), random-access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory (e.g., ferroelectric polymer memory, ovonic memory, phase change or ferroelectric memory, silicon oxide nitride oxide silicon (SONOS) memory), magnetic or optical cards, device arrays such as redundant array of independent disks (RAID) drives, solid-state memory devices (e.g., USB memory, solid-state drives (SSDs)), and any other type of storage medium suitable for storing information.

Device 1000 can be, for example, an ultra-mobile device, a mobile device, a fixed device, a machine-to-machine (M2M) device, a personal digital assistant (PDA), a mobile computing device, a smartphone, a telephone, a digital telephone, a cellular telephone, a user device, an e-book reader, a cell phone, a one-way pager, a two-way pager, a messaging device, a computer, a personal computer (PC), a desktop computer, a laptop computer, a notebook computer, a netbook computer, a handheld computer, a tablet computer, a server, a server array or server farm, a web server, a network server, an internet server, a workstation, a minicomputer, a mainframe computer, a supercomputer, a network appliance, a web appliance, a distributed computing system, a multiprocessor system, a processor-based system, consumer electronics, programmable consumer electronics, a gaming device, a display, a television, a digital television, a set-top box, a wireless access point, a base station, a node B, a subscriber station, a mobile subscriber center, a radio network controller, a router, a hub, a gateway, a bridge, a switch, a machine, or a combination thereof. Thus, the functionality and/or specific configurations of device 1000 described herein may be included or omitted in various embodiments of device 1000 as appropriately desired.

Embodiments of the device 1000 may be implemented using a single-input single-output (SISO) architecture. However, certain implementations may include multiple antennas (e.g., antennas 1018-f) for transmitting and/or receiving using adaptive antenna techniques for beamforming or spatial division multiple access (SDMA) and/or using MIMO communication techniques.

The components and features of device 1000 may be implemented using any combination of discrete circuits, application specific integrated circuits (ASICs), logic gates, and/or single chip architectures. Additionally, features of device 1000 may be implemented using microcontrollers, programmable logic arrays, and/or microprocessors, or any combination thereof, where appropriate. Note that hardware, firmware, and/or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

It should be understood that the exemplary device 1000 shown in the block diagram of Figure 10 may represent a functional descriptive example of many potential implementations. Therefore, the division, omission, or inclusion of block functions depicted in the figures should not be inferred that hardware components, circuits, software, and/or elements for implementing these functions must be divided, omitted, or included in the embodiments.

FIG11 illustrates an embodiment of a broadband wireless access system 1100. As shown in FIG11 , the broadband wireless access system 1100 may be an Internet Protocol (IP) type network, including an Internet 1110 type network capable of supporting mobile wireless access and/or fixed wireless access to the Internet 1110, etc. In one or more embodiments, the broadband wireless access system 1100 may include any type of orthogonal frequency division multiple access (OFDMA) or single carrier frequency division multiple access (SC-FDMA) based wireless network, for example, a system compatible with one or more of the 3GPP LTE specifications and/or the IEEE 802.16 standards, and the scope of the claimed subject matter is not limited in these respects.

In exemplary broadband wireless access system 1100, radio access networks (RANs) 1112 and 1118 can be coupled with evolved Node Bs (eNBs) 1114 and 1120, respectively, to provide wireless communications between one or more fixed devices 1116 and the Internet 1110 and/or between one or more mobile devices 1122 and the Internet 1110. An example of fixed device 1116 and mobile device 1122 is device 1000 of FIG. 10 , where fixed device 1116 comprises a stationary version of device 1000 and mobile device 1122 comprises a mobile version of device 1000. RANs 1112 and 1118 can implement profiles that define mappings of network functions to one or more physical entities on broadband wireless access system 1100. eNBs 1114 and 1120 may include radio equipment to provide RF communications with fixed devices 1116 and/or mobile devices 1122 (such as described with reference to device 1000), and may include, for example, PHY and MAC layer equipment compatible with the 3GPP LTE specification or the IEEE 802.16 standard. eNBs 1114 and 1120 may also include an IP backplane to couple to the Internet 1110 via RANs 1112 and 1118, respectively, although the scope of the claimed subject matter is not limited in these respects.

The broadband wireless access system 1100 may further include a visitor core network (CN) 1124 and/or a home CN 1126, each of which may be capable of providing one or more network functions, including but not limited to proxy and/or relay type functions, such as authentication, authorization, and accounting (AAA) functions, dynamic host configuration protocol (DHCP) functions, or domain name service control, etc., domain gateways such as public switched telephone network (PSTN) gateways or voice over internet protocol (VoIP) gateways, and/or internet protocol (IP) type server functions, etc. However, these are merely examples of the types of functions that the visitor CN 1124 and/or home CN 1126 may provide, and the scope of the claimed subject matter is not limited in these respects. The visiting CN 1124 may be referred to as a visiting CN where the visiting CN 1124 is not part of a regular service provider for the fixed device 1116 or mobile device 1122 (e.g., where the fixed device 1116 or mobile device 1122 is traveling away from its respective home CN 1126), or where the broadband wireless access system 1100 is part of a regular service provider for the fixed device 1116 or mobile device 1122, but the broadband wireless access system 1100 may be in another location or state that is not the primary or home location of the fixed device 1116 or mobile device 1122. The embodiments are not limited in this context.

Fixed device 1116 can be located anywhere within the range of one or both of eNBs 1114 and 1120, for example, in or near a home or business, to provide the home or business customer with broadband access to Internet 1110 via eNBs 1114 and 1120, RANs 1112 and 1118, and home CN 1126, respectively. It is worth noting that while fixed device 1116 is typically deployed in a static location, it can be moved to different locations as needed. For example, mobile device 1122 can be utilized at one or more locations if it is within the range of one or both of eNBs 1114 and 1120. According to one or more embodiments, an operations support system (OSS) 1128 can be part of broadband wireless access system 1100 to provide management functions for broadband wireless access system 1100 and to provide interfaces between functional entities of broadband wireless access system 1100. The broadband wireless access system 1100 of FIG. 11 is merely one type of wireless network illustrating a certain number of components of the broadband wireless access system 1100 , and the scope of the claimed subject matter is not limited in these respects.

Various embodiments can be realized using hardware elements, software elements or a combination thereof.The example of hardware elements can include processors, microprocessors, circuits, circuit elements (for example, transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. The example of software can include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols or any combination thereof. Determining to use hardware elements and/or software elements to realize an embodiment may vary according to any number of factors, for example, desired computing rate, power level, heat resistance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed and other design or performance constraints.

One or more aspects of at least one embodiment can be implemented by representative instructions stored on a machine-readable medium representing each logic within a processor, which, when read by a machine, causes the machine to manufacture logic to perform the technology described herein. Such representations (referred to as "IP cores") can be stored on tangible, machine-readable media and provided to various customers or manufacturing facilities to be loaded into manufacturing machines that actually manufacture logic or processors. Some embodiments can be implemented, for example, using a machine-readable medium or article that can store instructions or instruction sets, which, if executed by a machine, can cause the machine to perform methods and/or operations according to the embodiments. Such a machine may include, for example, any appropriate processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any appropriate combination of hardware and/or software. The machine-readable medium or article may include, for example, any suitable type of storage unit, storage device, storage article, storage medium, storage device device, storage device article, storage device medium and/or storage device unit, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, compact disk read only memory (CD-ROM), compact disk recordable (CD-R), compact disk rewritable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or disks, various types of digital versatile disks (DVDs), magnetic tape, tape cassettes, etc. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc., implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language.

The following examples relate to further embodiments:

Example 1 may include a method comprising: sending a broadcast message including V2X parameters from a network to a UE; and receiving and processing the broadcast message in the UE.

Example 2 may include the method of Example 1 or some other examples herein, wherein the broadcast message is sent on a System Information Broadcast (SIB) dedicated to V2X parameters.

Example 3 may include the method of Example 1 or some other examples herein, wherein the broadcast message is sent over an existing system information broadcast (SIB) message.

Example 4 may include the method of Example 1 or some other examples herein, wherein the V2X parameters include at least a value of a maximum allowed transmission frequency of the V2X message.

Example 5 may include the method of Example 1 or some other examples herein, wherein the V2X parameters include at least a PSID (Provider Service Identifier).

Example 6 may include the method of Example 4 or some other examples herein, wherein a UE that receives and processes the broadcast message limits the transmission frequency of the V2X message to a maximum allowed value.

Example 7 may include a method comprising: sending a broadcast message including V2X parameters from a network to a UE; and optionally, wherein the V2X parameters include one or more of: a maximum allowed transmission frequency of the V2X message, and a PSID (Provider Service Identifier).

Example 8 may include a method comprising: sending a V2X message from a network to a set of at least one UE and including one or more V2X parameters in a MAC header of a MAC PDU; receiving and processing the MAC header in the UE.

Example 9 may include the method of Example 8 or some other examples herein, wherein the V2X parameters include at least a maximum allowed transmission frequency of the V2X message.

Example 10 may include the method of Example 9 or some other examples herein, wherein the UE receiving and processing the MAC PDU limits the transmission frequency of the V2X message to a maximum allowed value.

Example 11 may include the method of Example 8 or some other examples herein, wherein the MAC PDU is a PDU reserved only for V2X messages.

Example 12 may include a method comprising: sending cell measurements from a RAN node to an MBMS functional entity; receiving and processing the cell measurements in the MBMS functional entity; and sending V2X parameters from the MBMS functional entity, the V2X parameters to be sent to at least one UE subscribed to the V2X service.

Example 13 may include the method of Example 12 or some other examples herein, wherein the MBMS functional entity is a Broadcast Multicast Service Center (BM-SC) or an MBMS GW.

Example 14 may include the method of Example 12 or some other examples herein, wherein the V2X parameters include at least a maximum message transmission rate allowed to be used by a UE subscribed to the V2X service.

Example 15 may include a method comprising: generating, by a radio access network (RAN) node, a message comprising one or more vehicle-to-everything (V2X) related parameters; and broadcasting, by the RAN node, the message.

Example 16 may include the method of Example 15 or some other examples herein, further comprising broadcasting the message by the RAN node via a system information broadcast (SIB).

Example 17 may include the method of Example 16 or some other examples herein, wherein the SIB is dedicated to broadcasting V2X parameters.

Example 18 may include the method of Example 15 or some other examples herein, wherein the V2X parameter includes at least a value related to a maximum allowed transmission frequency of the V2X message.

Example 19 may include the method of Example 15 or some other examples herein, wherein the V2X parameters include at least a provider service identifier (PSID).

Example 20 may include the method of Example 15 or some other examples herein, wherein the RAN node is an evolved Node B (eNB).

Example 21 may include a radio access network (RAN) node comprising: control logic for generating a message comprising one or more vehicle-to-everything (V2X) related parameters; and transmission logic coupled to the control logic, the transmission logic for broadcasting the message.

Example 22 may include the RAN node of Example 21 or some other examples herein, wherein the transmitting logic is further configured to broadcast the message via a system information broadcast (SIB).

Example 23 may include the RAN node of Example 22 or some other examples herein, wherein the SIB is dedicated to broadcasting V2X parameters.

Example 24 may include the RAN node of Example 21 or some other examples herein, wherein the V2X parameters include at least a value related to a maximum allowed transmission frequency of the V2X messages.

Example 25 may include the RAN node of Example 21 or some other examples herein, wherein the V2X parameters include at least a provider service identifier (PSID).

Example 26 may include the RAN node of Example 21 or some other examples herein, wherein the RAN node is an evolved Node B (eNB).

Example 27 may include a method comprising: receiving, by a user equipment, a broadcast message including one or more vehicle-to-everything (V2X) related parameters; and performing, by the UE, a V2X process based on the received one or more V2X parameters.

Example 28 may include the method of Example 27 or some other examples herein, further comprising: receiving, by the UE, a message via a system information broadcast (SIB).

Example 29 may include the method of Example 28 or some other examples herein, wherein the SIB is dedicated to broadcasting V2X parameters.

Example 30 may include the method of Example 27 or some other examples herein, wherein the V2X parameter includes at least a value related to a maximum allowed transmission frequency of the V2X message.

Example 31 may include the method of Example 27 or some other examples herein, wherein the V2X parameters include at least a provider service identifier (PSID).

Example 32 may include the method of Example 27 or some other examples herein, wherein performing the V2X process includes limiting, by the UE, a transmission frequency of the V2X message to a maximum allowed value based on one or more received V2X parameters.

Example 33 may include a user equipment (UE) comprising: receiving logic for receiving a broadcast message comprising one or more vehicle-to-everything (V2X) related parameters; and control logic coupled to the receiving logic, the control logic for performing a V2X process based on the received one or more V2X parameters.

Example 34 may include the UE of Example 33 or some other examples herein, wherein the receiving logic is to receive the message via a system information broadcast (SIB).

Example 35 may include the UE of Example 34 or some other examples herein, wherein the SIB is dedicated to broadcasting V2X parameters.

Example 36 may include the UE of Example 33 or some other examples herein, wherein the V2X parameters include at least a value related to a maximum allowed transmission frequency of the V2X message.

Example 37 may include the UE of Example 33 or some other examples herein, wherein the V2X parameters include at least a provider service identifier (PSID).

Example 38 may include the UE of Example 33 or some other examples herein, wherein the control logic is further configured to limit a transmission frequency of the V2X message to a maximum allowed value based on the received one or more V2X parameters.

Example 39 may include a method comprising: generating, by a radio access network (RAN) node, a MAC packet data unit (PDU) having a medium access control (MAC) header including one or more vehicle-to-everything (V2X) related parameters; and sending, by the RAN node, a message including the MAC PDU.

Example 40 may include the method of Example 39 or some other examples herein, wherein the one or more V2X parameters include an indication of a maximum allowed transmission frequency of the V2X messages.

Example 41 may include the method of Example 39 or some other examples herein, wherein the MAC PDU is a PDU reserved only for V2X messages.

Example 42 may include the method of Example 39 or some other examples herein, wherein the RAN node is an evolved Node B (eNB).

Example 43 may include a radio access network (RAN) node comprising: control logic for generating a media access control (MAC) packet data unit (PDU) having a MAC header including one or more vehicle-to-everything (V2X) related parameters; and transmission logic coupled to the control logic, the transmission logic for transmitting a message including the MAC PDU.

Example 44 may include the RAN node of Example 43 or some other examples herein, wherein the one or more V2X parameters include an indication of a maximum allowed transmission frequency of the V2X messages.

Example 45 may include the RAN node of Example 43 or some other examples herein, wherein the MAC PDU is a PDU reserved only for V2X messages.

Example 46 may include the RAN node of Example 43 or some other examples herein, wherein the RAN node is an evolved Node B (eNB).

Example 47 may include a method comprising: receiving, by a user equipment (UE), a message including a media access control (MAC) packet data unit (PDU) having a MAC header including one or more vehicle-to-anything (V2X)-related parameters; and performing, by the UE, a V2X-related procedure based on the one or more V2X parameters.

Example 48 may include the method of Example 47 or some other examples herein, wherein the one or more V2X parameters include an indication of a maximum allowed transmission frequency of the V2X messages.

Example 49 may include the method of Example 47 or some other examples herein, wherein the MAC PDU is a PDU reserved only for V2X messages.

Example 50 may include the method of Example 47 or some other examples herein, wherein performing the V2X-related process includes limiting, by the UE, a transmission frequency of the V2X message to a maximum allowed value based on one or more V2X parameters.

Example 51 may include a user equipment (UE) comprising: receiving logic to receive a message including a medium access control (MAC) packet data unit having a MAC header including one or more vehicle-to-everything (V2X) related parameters; and control logic coupled to the receiving logic, the control logic performing a V2X-related process based on the one or more V2X parameters.

Example 52 may include the UE of Example 51 or some other examples herein, wherein the one or more V2X parameters include an indication of a maximum allowed transmission frequency of the V2X messages.

Example 53 may include the UE of Example 51 or some other examples herein, wherein the MAC PDU is a PDU reserved only for V2X messages.

Example 54 may include the UE of Example 51 or some other examples herein, wherein the control logic is further configured to limit a transmission frequency of the V2X message to a maximum allowed value based on one or more V2X parameters.

Example 55 may include a method comprising: sending, by a radio access network (RAN) node, one or more cell measurements to a multimedia broadcast multicast service (MBMS) functional entity; receiving, by the RAN node, an indication of one or more V2X-related parameters related to a vehicle-to-everything (V2X) service, wherein the one or more V2X parameters are based on the cell measurements; and sending, by the RAN node, an indication of the one or more V2X parameters to a user equipment (UE) subscribed to the V2X service.

Example 56 may include the method of Example 55 or some other examples herein, wherein the MBMS functional entity is a Broadcast Multicast Service Center (BM-SC) or an MBMS Gateway (GW).

Example 57 may include the method of Example 55 or some other examples herein, wherein the one or more V2X parameters include at least a maximum message transmission rate allowed to be used by a UE subscribed to the V2X service.

Example 58 may include the method of Example 55 or some other examples herein, wherein the RAN node is an evolved Node B (eNB).

Example 59 may include a radio access network (RAN) node comprising: receiving logic for receiving, from a multimedia broadcast multicast service (MBMS) functional entity, an indication of one or more V2X-related parameters related to a vehicle-to-everything (V2X) service, wherein the one or more V2X parameters are based on cell measurements of the RAN node; and transmitting logic coupled to the receiving logic, the transmitting logic for transmitting the indication of the one or more V2X parameters to a user equipment (UE) subscribed to the V2X service.

Example 60 may include the RAN node of Example 59 or some other examples herein, wherein the MBMS functional entity is a Broadcast Multicast Service Center (BM-SC) or an MBMS Gateway (GW).

Example 61 may include the RAN node of Example 59 or some other examples herein, wherein the one or more V2X parameters include at least a maximum message transmission rate allowed to be used by a UE subscribed to the V2X service.

Example 62 may include the RAN node of Example 59 or some other examples herein, wherein the RAN node is an evolved Node B (eNB).

Example 63 may include a method comprising: receiving, by a Multimedia Broadcast Multicast Service (MBMS) functional entity, an indication of one or more cell measurements; identifying, by the MBMS functional entity, one or more V2X-related parameters related to a vehicle-to-everything (V2X) service based on the one or more cell measurements; and sending, by the MBMS functional entity, an indication of the one or more V2X parameters.

Example 64 may include the method of Example 63 or some other examples herein, wherein the MBMS functional entity is a Broadcast Multicast Service Center (BM-SC) or an MBMS Gateway (GW).

Example 65 may include the method of Example 63 or some other examples herein, wherein the one or more V2X parameters include at least a maximum message transmission rate allowed to be used by a UE subscribed to the V2X service.

Example 66 may include a multimedia broadcast multicast service (MBMS) functional entity, comprising: receiving logic for receiving an indication of one or more cell measurements; control logic, coupled to the receiving logic, the control logic for identifying one or more V2X-related parameters related to a vehicle-to-everything (V2X) service based on the one or more cell measurements; and transmitting logic, coupled to the receiving logic, the transmitting logic for transmitting an indication of the one or more V2X parameters.

Example 67 may include the MBMS functional entity of Example 63 or some other examples herein, wherein the MBMS functional entity is a broadcast multicast service center (BM-SC) or an MBMS gateway (GW).

Example 68 may include the MBMS functional entity of Example 63 or some other examples herein, wherein the one or more V2X parameters include at least a maximum message transmission rate allowed to be used by a UE subscribed to the V2X service.

Many specific details have been set forth herein to provide a thorough understanding of the embodiments. However, it will be understood by those skilled in the art that the embodiments may be practiced without these specific details. In other cases, well-known operations, components, and circuits have not been described in detail to avoid obscuring the embodiments. It will be understood that the specific structural and functional details disclosed herein may be representative and do not necessarily limit the scope of the embodiments.

The expressions "coupled" and "connected," as well as their derivatives, may be used to describe some embodiments. These terms are not intended to be synonymous with each other. For example, the terms "connected" and/or "coupled" may be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

Unless expressly stated otherwise, it is understood that terms such as "process," "calculate," "evaluate," "determine," and the like refer to the action and/or processing of a computer or computing system, or similar electronic computing device, that manipulates and/or transforms data represented as physical quantities (e.g., electronic) within registers and/or memories of the computing system into other data similarly represented as physical quantities within memories, registers, or other such information storage, transmission, or display devices of the computing system. The embodiments are not limited in this context.

It should be noted that the methods described herein do not have to be performed in the order described, or in any particular order. In addition, the various activities described with respect to the methods identified herein can be performed in serial or parallel fashion.

Although specific embodiments have been shown and described herein, it will be understood that any arrangement calculated to achieve the same purpose may replace the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of the various embodiments. It will be understood that the above description has been made in an illustrative and non-restrictive manner. Upon reviewing the above description, combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art. Therefore, the scope of the various embodiments includes any other applications using the above combinations, structures, and methods.

It is emphasized that the Abstract of the present disclosure is provided to comply with the requirement of 37 C.F.R. Section 1.72(b) that the abstract will allow the reader to quickly ascertain the nature of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing Detailed Description, it may be seen that various features are grouped together in a single embodiment for the purpose of simplifying the disclosure. This approach of the present disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than expressly recited in each claim. Rather, as reflected in the following claims, the inventive subject matter lies in less than all the features of a single disclosed embodiment. Accordingly, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. In the appended claims, the terms "including" and "in which" are used as the simplified English equivalents of the respective terms "comprising" and "in which," respectively. Furthermore, the terms "first," "second," and "third," etc. are used merely as labels and are not intended to impose numbering requirements on their objects.

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

Claims (34)

1. An apparatus comprising: Memory; and Logic, at least a portion of which is implemented in processing circuitry coupled to the memory, the logic being used for: Receive environmental information from one or more devices in the network, the environmental information being detected by one or more sensors implemented in the one or more devices; At least in part based on the environmental information, one or more V2X parameters for transmitting subsequent vehicle-to-everything (V2X) communication are determined, the one or more V2X parameters specifying the message transmission rate and provider service identifier (PSID) for the subsequent V2X communication; Generate a message that includes one or more V2X parameters; and This enables the message to be transmitted to at least one other device for use in transmitting the subsequent V2X communication. The memory and the logic are implemented in one of the Radio Access Network (RAN) nodes, the evolved Node B (eNB), and the Multimedia Broadcast Multicast Service (MBMS) functional entity system. 2. The apparatus of claim 1, wherein the logic is configured to enable the transmission via a broadcast channel of the message comprising a Radio Resource Control (RRC) message having a System Information Block (SIB) dedicated to the one or more V2X parameters. 3. The apparatus of claim 1, wherein the logic is configured to transmit the message, comprising a Radio Resource Control (RRC) message having an Existing System Information Block (SIB), via a broadcast channel, wherein the Existing SIB has the one or more V2X parameters. 4. The apparatus of claim 1, wherein the logic is configured to transmit the message that includes the one or more V2X parameters in the MAC header of the Media Access Control (MAC) Protocol Data Unit (PDU). 5. The apparatus according to claim 1, wherein the logic is used for: Receive cellular information, the cellular information including at least one of cellular load, the number of devices utilizing V2X services, and latency requirements for the subsequent V2X communication; and In addition to the environmental information, the one or more V2X parameters are also determined based on the cellular information for transmission in the message. 6. The apparatus of claim 1, wherein the one or more V2X parameters include at least one of a message periodicity integer value and a PSID string value. 7. The apparatus according to any one of claims 1 to 4, comprising: Antenna, which is coupled to the memory and the processing circuitry; and A transceiver coupled to the antenna, the memory, and the processing circuitry, the transceiver being used to transmit the message. 8. A computer-readable storage medium comprising a plurality of instructions, which, when executed, cause processing circuitry of one of a radio access network (RAN) node, an evolved Node B (eNB), and a multimedia broadcast multicast service (MBMS) functional entity system to perform the following operation: receiving environmental information from one or more devices in the network, the environmental information being detected by one or more sensors implemented in the one or more devices; At least in part based on the environmental information, one or more V2X parameters for transmitting subsequent vehicle-to-everything (V2X) communication are determined, the one or more V2X parameters specifying the message transmission rate and provider service identifier (PSID) for the subsequent V2X communication; Generate a message that includes one or more V2X parameters; and This enables the message to be transmitted to at least one other device for use in transmitting the subsequent V2X communication. 9. The computer-readable storage medium of claim 8, comprising the plurality of instructions, which, when executed, cause the processing circuitry to: cause the message, comprising a radio resource control (RRC) message having a system information block (SIB) dedicated to the one or more V2X parameters, to be transmitted via a broadcast channel. 10. The computer-readable storage medium of claim 8, comprising the plurality of instructions, which, when executed, cause the processing circuitry to: cause the message comprising a Radio Resource Control (RRC) message using an existing System Information Block (SIB), wherein the existing SIB has the one or more V2X parameters, to be transmitted via a broadcast channel. 11. The computer-readable storage medium of claim 8, comprising the plurality of instructions, which, when executed, cause the processing circuitry to: transmit the message including the one or more V2X parameters in the MAC header of a Media Access Control (MAC) Protocol Data Unit (PDU). 12. The computer-readable storage medium of claim 8, comprising the plurality of instructions, which, when executed, cause the processing circuitry to perform the following operations: Receive cellular information about the cellular network, the cellular information including at least one of cellular load, the number of devices utilizing V2X services, and latency requirements for subsequent V2X communication; and In addition to the environmental information, one or more V2X parameters are determined based on the cellular information for transmission in the message. 13. The computer-readable storage medium of claim 8, wherein the one or more V2X parameters include at least one of a message periodicity integer value and a PSID string value. 14. An apparatus comprising: Memory; and Logic, at least a portion of which is implemented in processing circuitry coupled to the memory, the logic being used for: Receive a message including one or more Vehicle-to-Everything (V2X) parameters, wherein the V2X parameters are determined at least in part based on environmental information by one of the Radio Access Network (RAN) nodes, Evolved Node Bs (eNBs), and Multimedia Broadcast Multicast Service (MBMS) functional entities, and the one or more V2X parameters specify a message transmission rate and a Provider Service Identifier (PSID) for subsequent V2X communication, wherein the environmental information is detected by one or more sensors implemented in one or more devices in the network; V2X settings are configured based on one or more V2X parameters for transmitting subsequent V2X communication, the V2X settings including at least a message transmission rate for the subsequent V2X communication; and The subsequent V2X communication will be based on the aforementioned V2X settings. The memory and the logic are implemented in one of the user equipment (UE) and the roadside unit (RSU). 15. The apparatus of claim 14, wherein the logic is configured to receive, via a broadcast channel, the message comprising a Radio Resource Control (RRC) message having a System Information Block (SIB) dedicated to the one or more V2X parameters. 16. The apparatus of claim 14, wherein the logic is configured to receive, via a broadcast channel, the message comprising a Radio Resource Control (RRC) message using an existing System Information Block (SIB), wherein the existing SIB has the one or more V2X parameters. 17. The apparatus of claim 14, wherein the logic is configured to receive the message which includes the one or more V2X parameters in the MAC header of a Media Access Control (MAC) Protocol Data Unit (PDU). 18. The apparatus of claim 14, wherein the one or more V2X parameters include at least one of a message transmission rate value and a PSID value. 19. A computer-readable storage medium comprising a plurality of instructions, which, when executed, cause user equipment (UE) and roadside unit (RSU) processing circuitry to perform the following operations: Receive a message including one or more Vehicle-to-Everything (V2X) parameters, wherein the V2X parameters are determined at least in part based on environmental information by one of the Radio Access Network (RAN) nodes, Evolved Node Bs (eNBs), and Multimedia Broadcast Multicast Service (MBMS) functional entities, and the one or more V2X parameters specify a message transmission rate and a Provider Service Identifier (PSID) for subsequent V2X communication, wherein the environmental information is detected by one or more sensors included in one or more devices in the network; V2X settings are configured based on one or more V2X parameters for transmitting subsequent V2X communication, the V2X settings including at least a message transmission rate for the subsequent V2X communication; and The subsequent V2X communication is based on the aforementioned V2X settings. 20. The computer-readable storage medium of claim 19, comprising the plurality of instructions, which, when executed, enable the processing circuitry to: receive, via a broadcast channel, the message comprising a radio resource control (RRC) message having a system information block (SIB) dedicated to the one or more V2X parameters. 21. The computer-readable storage medium of claim 19, comprising the plurality of instructions, which, when executed, enable the processing circuitry to: receive, via a broadcast channel, the message comprising a Radio Resource Control (RRC) message using an existing System Information Block (SIB), wherein the existing SIB has the one or more V2X parameters. 22. The computer-readable storage medium of claim 19, comprising the plurality of instructions, which, when executed, enable the processing circuitry to: receive the message comprising the one or more V2X parameters in the MAC header of a Media Access Control (MAC) Protocol Data Unit (PDU). 23. The computer-readable storage medium of claim 19, wherein the one or more V2X parameters include at least one of a message periodicity integer value and a PSID string value. 24. An apparatus comprising: Means for receiving environmental information from one or more devices in a network, the environmental information being detected by one or more sensors implemented in the one or more devices; means for determining one or more V2X parameters for transmitting subsequent vehicle-to-everything (V2X) communication based at least in part on the environmental information, the one or more V2X parameters specifying a message transmission rate and a provider service identifier (PSID) for the subsequent V2X communication. A means for generating a message including one or more V2X parameters; and A means for causing the message to be transmitted to at least one other device for use in transmitting the subsequent V2X communication. The device is implemented in one of the following: a Radio Access Network (RAN) node, an evolved Node B (eNB), and a Multimedia Broadcast Multicast Service (MBMS) functional entity system. 25. The device of claim 24, wherein the message comprises a radio resource control (RRC) message having a system information block (SIB) dedicated to the one or more V2X parameters, transmitted via a broadcast channel. 26. The device of claim 24, wherein the message includes a Radio Resource Control (RRC) message having an Existing System Information Block (SIB) transmitted via a broadcast channel, wherein the Existing SIB has the one or more V2X parameters. 27. The device of claim 24, wherein the message includes the one or more V2X parameters in the MAC header of the Media Access Control (MAC) Protocol Data Unit (PDU). 28. The device according to claim 24, comprising: A means for receiving cellular information, the cellular information including at least one of cellular load, the number of devices utilizing V2X services, and latency requirements for subsequent V2X communication; and A means for determining one or more V2X parameters based on the cellular information in addition to the environmental information for transmission in the message. 29. The device of claim 24, wherein the one or more V2X parameters include at least one of a message periodicity integer value and a PSID string value. 30. An apparatus comprising: A means for receiving a message including one or more Vehicle-to-Everything (V2X) parameters, wherein the V2X parameters are determined at least in part based on environmental information by one of a Radio Access Network (RAN) node, an Evolved Node B (eNB), and a Multimedia Broadcast Multicast Service (MBMS) functional entity system, and one or more of the V2X parameters specify a message transmission rate and a Provider Service Identifier (PSID) for subsequent V2X communication, wherein the environmental information is detected by one or more sensors included in one or more devices in the network; A means for configuring V2X settings for transmitting subsequent V2X communication based on one or more V2X parameters, the V2X settings including at least a message transmission rate for the subsequent V2X communication; and A means for performing the subsequent V2X communication based on the V2X settings. The device is implemented in either the User Equipment (UE) or the Roadside Unit (RSU). 31. The device of claim 30, wherein the message comprises a Radio Resource Control (RRC) message received via a broadcast channel having a System Information Block (SIB) dedicated to the one or more V2X parameters. 32. The device of claim 30, wherein the message includes a Radio Resource Control (RRC) message received via a broadcast channel having an Existing System Information Block (SIB), wherein the Existing SIB has the one or more V2X parameters. 33. The device of claim 30, wherein the message includes the one or more V2X parameters in the MAC header of the Media Access Control (MAC) Protocol Data Unit (PDU). 34. The device of claim 30, wherein the one or more V2X parameters include at least one of a message periodicity integer value and a PSID string value.