PROXY COORDINATED WIRELESS COMMUNICATION OPERATION FOR VEHICULAR ENVIRONMENTS
Proxy coordinated wireless communication operation is described for vehicular environments. In one example, a first user equipment receives a proxy operation authorization from a vehicular environment proximity services function for the first user equipment to operate as a Proxy for the proximity services function. The first user equipment then controls configuration information of other user equipment. The first user equipment also controls the vehicular environment operation mode used by the other user equipment.
This patent application is a continuation of and claims benefit of U.S. patent application Ser. No. 15/577,885, filed on Nov. 29, 2017 and entitled PROXY COORDINATED WIRELESS COMMUNICATION OPERATION FOR VEHICULAR ENVIRONMENTS which is a U.S. National Phase Application under 35 U.S.C. § 371 of International Application No. PCT/US2015/000251, filed Dec. 23, 2015, entitled PROXY COORDINATED WIRELESS COMMUNICATION OPERATION FOR VEHICULAR ENVIRONMENTS, which claims priority to U.S. Provisional Application No. 62/186,614, filed Jun. 30, 2015, entitled PROXY COORDINATED V2X OPERATION.
FIELDThe present description is related to wireless communications and in particular to proxy coordinated communication for wireless vehicle communications
BACKGROUNDIntelligent Transportation Systems (ITS) endeavor to improve safety and efficiency on roadways by adding intelligence to moving vehicles and also to fixtures on and around roadways. There are many different functions and purposes that could be enabled by ITS. Some of these include managing traffic flow and lane occupancy, collecting tolls, tracking freight, providing road condition alerts, alerting about pedestrians and other obstacles on the roadway, and the like. In addition to intelligent vehicles and fixtures, ITS seeks to allow vehicles to communicate with other vehicles and with other proximate devices on or near the roadway.
The Wireless Access in Vehicular Environments (WAVE) architecture and standards have been developed to support ITS safety and non-safety applications. Most ITS applications rely on the concept of situational awareness by the vehicles and the fixtures that is then enhanced by a co-operative awareness. The co-operative awareness is based on periodic and event-driven broadcast of basic safety messages (BSM) between vehicles (i.e., vehicle to vehicle (V2V) communication), between vehicles and infrastructure fixtures (i.e., vehicle to infrastructure (V2I) communications), and between vehicles and pedestrians (i.e., vehicle to pedestrian (V2P) communications). Collectively, V2V, V2I, and V2P communications are designated as vehicle to everything (V2X) communications.
In several ITS scenarios, Road Side Units (RSUs) are defined as communication nodes that are able to provide safety services (e.g. interaction collision warning) and non-safety (mobility information) services to vehicles and to other RSUs through broadcast messages.
V2X communications are provided in part by a dedicated short range communications (DSRC) channel, which may be carried by a local and metropolitan area network such as defined in the IEEE 802.11p standard and by a cellular network (e.g., long term evolution (LTE), fifth generation (5G), etc.). The 802.11p standard may use channels of 10 MHz bandwidth in the 5.9 GHz band (5.850-5.925 GHz). The DSRC may be one or more one-way or two-way short-range or medium-range wireless communication channels that are specifically designed for automotive vehicles. V2X devices may be equipped with multiple radios operating in different spectrum bands. Cellular networks may be used to assist V2X devices to discover and take advantage of safety and non-safety services, which may be broadcasted over one or more DSRC channels.
In order to send and receive messages in a DSRC 802.11p wireless local area network, a device (e.g. RSU or vehicle) sets up or discovers and joins a WAVE basic service set (WBSS), which is a basic service set (BSS) where devices may operate in the WAVE mode and may communicate without the need to execute the typical 802.11 authentication and association procedures. In order to discover a given WBSS, V2X devices scan multiple DSRC channels for messages from that WBSS. The WBSS will be identified by a BSSID (Base Station Subsystem Identification) in the 802.11 MAC (Media Access Control) layer frames.
The deployment of DSRC/802.11p-based Road Side Units (RSU) may involve large investments in roadway infrastructure due to coverage limitations of the 802.11p standard. Existing cellular systems, such as LTE, are being considered as an alternative to DSRC/802.11p for ITS applications given its large scale coverage and efficient spectrum utilization. The LTE Proximity Services (ProSe) functionality is being considered for enabling ITS use cases through direct device communications.
Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements.
Short BSM messages are useful locally to identify urgent situations (e.g. collision warning, emergency stop, pre-crash warning, etc.) within very short intervals (e.g. 20 to 100 ms). As such, minimizing the overhead involved in enabling scalable transmission and reception of BSMs will allow BSM to be sent much more quickly for V2X (V2V, V2I and V2P) over cellular systems. However, LTE ProSe protocols are not scalable and efficient to meet latency and scalability desires of V2X communications. This limits the usefulness of BSM for ITS safety applications.
Several V2X use cases described in the 3GPP V2X study group can be enabled by V2V communications only. For instance, cooperative adaptive cruise control (CACC), emergency vehicle/forward collision warning, and pre-crash sensing warning may be implemented without requirement for RSU support. Furthermore, many of these safety applications are mission critical and should continue to operate even in areas without eNB coverage.
The DSRC Implementation Guide states: “While there have been proposals for adaptive sending rate algorithms to better preserve bandwidth (especially during periods of slow moving dense traffic), at this time none is adopted in the standard and a static transmission rate of every 100 ms is used.”
As adoption of V2X technology increases, the impact of V2X communications on network capacity will have to be carefully managed. The adaptation of the BSM transmissions may be used to support future mission critical safety applications with extremely low latency, such as autonomous driving, and manage spectrum resources more efficiently.
A RSU may be implemented as a standalone UE. In several scenarios, the RSU may implement additional functionality (e.g. cameras, traffic sensors, radar, etc.), which can be used to better configure the V2X operation of other UEs based on context information. For instance, a car collision risk in the middle of a traffic jam is low, while demand for user communications may increase. In this case, reducing the V2X cooperative transmission rate would reduce the load on the air interface and improve resource utilization.
In another example, a RSU in a busy intersection may have a more comprehensive view of the surrounding environment than each individual vehicle. The RSU can use its environment awareness capability to better coordinate how vehicles transmit safety messages.
Thus, there are several parameters that may be adjusted. These parameters can be adjusted by the ProSe/V2X function in the core network. However, as discussed above, communication with the core network may experience longer latency. Moreover, if a UE is outside the coverage area, it has no access to the ProSe function.
Because the ProSe Function is part of the Core Network (CN), the configuration of V2X operation parameters uses user plane communication over a PC3 interface which involves several network nodes, as described below in further detail in the context of
As described herein functionalities and procedures enable control of V2X operation by authorized UEs using a PC5 interface without any requirement for direct involvement of the ProSe Function in the CN. This functionality supports an extremely low latency (e.g. 1 to 20 ms) useful for emergency and traffic control BSM. This functionality also enables V2X services outside network coverage.
A procedure is described that may be performed over the PC5 interface to enable direct UE to UE coordination of V2X operations. This may include a V2X Proxy functionality that enables a V2X UE to take control over V2X operation of other UEs without direct communication with the V2X ProSe function, where the V2X Proxy functionalities are implemented by UEs, which may also implement RSU functionalities. This may also include a protocol to enable V2X UEs to obtain authorization of the V2X ProSe function to utilize V2X Proxy functionalities. A new V2X message header may be used that includes a field announcing that the UE is operating as a V2X Proxy and is allowed to perform certain V2X configuration functions within its coverage range on behalf of the V2X ProSe Function. A further protocol may be used to enable configuration of V2X operation parameters between V2X UEs and a V2X UE operating as a V2X Proxy.
Embodiments include enhancements to the LTE ProSe function to enable more efficient direct coordination between UEs within very strict latency constraints. This may be used to support several V2I and V2V use cases. It also enables continuation of V2X services outside network coverage. In the present description a V2X UE refers to a UE that supports ProSe and V2X enabling features. The V2X ProSe Function is a ProSe function with V2X specific functionality that may be part of the ProSe function or that may be stand alone.
The proximity services use a ProSe application 120, 122 at each participating UE coupled to one or more ProSe application servers 124 through a PCI or similar link. The ProSe application server delivers ProSe functions 126 to the UEs 104, 106 through a PC3 or similar link. The ProSe application servers also deliver ProSe functions to the HSS 116 and a SUPL (Secure User Plane Location) location platform (SLP) 128 through PC4 or similar links which delivers location awareness to the UEs and to any other mobile nodes in the system. The ProSe function may also connect with other services and systems to perform the described and other functions.
The LTE ProSe specification introduced new functionalities and interfaces as shown. ProSe (also referred to as direct device-to-device (D2D) communications) may allow a first user equipment (UE) to detect the presence of a second UE that is proximate to the first UE, establish a direct connection or communication session, and communicate with the second UE over the direct connection. A UE, mobile terminal, mobile communication device, etc., that is enabled for V2X communications may be referred to as a “V2X device”, a “V2X UE”, and the like. One of the new functionalities of the LTE ProSe specification is the EPC (Enhanced Packet Core) support for WLAN direct discovery and communication. This functionality allows the EPC network to enable two or more ProSe-enabled WLAN-capable UEs to directly communicate using WLAN technology. This decision can be taken, for example, when the EPC network supports EPC-level ProSe discovery and becomes aware that two or more UEs are in close proximity and when the EPC network knows that a first UE (UE-A) requests to communicate with a second UE (UE-B).
The E-UTRAN is further coupled to an MME through S1-MME which may also be coupled to the serving gateway through S11. The MME provides connections to a variety of different functions and systems that may be integrated into the MME or provided separately. These may include a home subscriber server (HSS) 218, a serving GPRS (general packet radio service) support node (SGSN) 216 as well as UTRAN and GSM (Global System for Mobile communications) EDGE (Enhanced Data Rated for GSM Evolution) radio access network (GERAN) and any other desired services.
In this case, the V2X configuration update procedure is shown as being carried out between one of the V2X UEs 201 through the eNB 204. The UE begins this transaction procedure by sending a V2X configuration update 231 to the V2X ProSe function 212 through the local eNB 204, in this case an E-UTRAN. The radio access node (RAN) 204 forwards 232 the V2X message to the V2X ProSe function 212. At the V2X ProSe function, the V2X configuration update message is processes 233. This may include checking credentials, determining configuration parameters for the WBSS, and other functions. These functions may access the external ITS servers 210. When finished, the V2X ProSe function sends 234, a V2X configuration update response back to the RAN 204 to be forwarded to the destination UE 201. The RAN, then sends 235 the V2X response message to the UE. At this stage the UE is able to apply the configuration information in the response message 235. The configuration information may be the same as or different from the configuration information in the original request message 231.
In order to enable efficient distributed coordination between UEs, while following rules and policies set by the V2X ProSe function, a V2X Proxy may be used. A V2X Proxy as described herein enables UEs after having been authorized by the V2X ProSe function to control the configuration information (e.g. V2X operation mode and cooperative message transmission rate) of other UEs. The V2X Proxy acts under authorization and supervision of a V2X ProSe function, but eliminates much of the overhead for coordination with the ProSe function over the PC3 interface as shown in
In one embodiment, UEs implementing RSU functions may operate as a V2X Proxy and control the V2X mode and cooperative messages (BSM) transmission rates of other UEs under its coverage. In other words some UEs may receive an authorization from the ProSe Function to communicate directly with other UEs to control the local V2X configuration information. Multiple V2X proxies may be established to allow configuration update responses to be sent even faster and to more UEs at the same time.
A V2X UE may be pre-configured with information to operate as V2X Proxy, which is sent to the V2X ProSe Function during initial service authorization. The V2X ProSe function has the responsibility to verify the credentials and authorize the UE to operate as a V2X Proxy. Optionally, the Proxy capability of the V2X UE may be part of the UE subscription.
In another embodiment, the V2X UE can also send a request to the V2X ProSe function to operate as a V2X Proxy at any time after configuration and initialization. The ProSe function may use the UEs V2X credentials and consult external servers (e.g. geolocation and ITS servers) to decide whether the UE should be allowed to operate as a V2X Proxy. An example embodiment of a V2X Proxy registration procedure is described in the context of
After receiving a proxy request 310 from the V2X UE, the receiving V2X ProSe Function 304 then attempts to determine whether the requesting V2X UE is authorized to receive a proxy. This may be done by sending a request 312 from the home PLMN 304 to the visitor or local PLMN 306 to obtain authorization information. If available, then the local PLMN 306 sends 314 an authorization response back to the home PLMN. The home PLMN may also or alternatively request 318 authorization from external ITS servers 308. If available, then the external ITS servers may send 320 an authorization response. All of these requests and responses for authorization may contain V2X configuration information that the proxy UE may use to update V2X configurations of other UEs. If the V2X UE 302 is authorized to act as a proxy for the ProSe Function 304, then the ProSe Function at the home PLMN may send a response 322 which includes the authorization and the authorized V2X proxy configuration.
The V2X UE after receiving the authorization may send an acknowledgment back to the ProSe Function at the home PLMN 304. The ProSe Function at the home PLMN may also send notifications to the ITS servers 308 and any other appropriate entities that the UE has registered with the ProSe Function and has received a proxy authorization response.
In one embodiment, in addition to the V2X UE's identification and security related credentials, a V2X Proxy registration request may also include a V2X Proxy configuration request. An example of such a request is shown in Table 1. More or fewer fields may be used to suit different implementations. The V2X ProSe Function sends back the final V2X Proxy configuration to be used by the UE.
A V2X proxy header may be used by a UE proxy to indicate its status as a proxy. If authorized, a V2X UE may include the V2X Proxy header in messages sent over a PC5 interface, and set an X bit in the Proxy header to advertise its status as an authorized V2X Proxy.
An example of a V2X Proxy header is shown in
V2X Proxy after being authorised may send advertisements within the network coverage area and, if authorised, then it may also send advertisements outside of the network coverage area. Using the header preamble above, the V2X UE authorized to operate as a V2X Proxy sets the X bit in the V2X Proxy header of V2X messages sent over a PC5 interface. It may also include other Information Elements as desired. The V2X Proxy may also set the P bit in the V2X Proxy header to indicate that it supports the service(s) described in the PSID field.
V2X UEs are able to discover a UE, RSU or other component acting as a V2X Proxy by monitoring the X bit in the V2X messages. They may further verify whether they can use the V2X Proxy services by comparing the PSID(s) in the received messages with the PSID(s) that they support.
If a V2X ProSe registered V2X UEs loses network coverage, it can still operate in V2X mode if it detects a V2X Proxy. The V2X UE may operate using PC5 links even without the LTE-Uu links. If an out of coverage V2X UE does not receive any V2X messages with the X bit set for a given time interval (the UE may be configured with an out of coverage timeout parameter that may be pre-configured or set by the service provider), it may suspend its V2X operation until it discovers another V2V proxy, re-enters network coverage, or becomes a V2X Proxy itself, if the UE is pre-authorized to operate as a V2X Proxy.
If the V2X Proxy authorizes the new requested configuration, it responds with a configuration update 516 confirming (or adapting) the V2X operational parameters. The V2X UE can confirm the reception of the re-configuration information by setting the A bit in the header of its next V2X ProSe transmission 518. This transmission may be BSM or any other type of allowed V2X message. This transmission may also be received by the proxy UE if it is a BSM or other broadcast.
As shown, the V2X Proxy UE may have an ITS application, and can choose to send the messages received to the ITS application or forward the messages to an eNB, to be sent to the ProSe/V2X function in the core network. This may be done after the configuration update of the UE so that the UE configuration is not delayed by any network messaging. This decision can be done based on the message type or some indication in the MAC header of the requesting UE.
A V2X Proxy UE may include the V2X Proxy capability indication as part of the “UE Network Capability” in the Attach Request and/or Tracking Area Update Request message. The MME stores this information for ProSe/V2X operation.
If the V2X Proxy UE is capable of providing Proxy services based on UE subscription, the MME may include a Proxy authorization indication in the S1 AP Initial Context Setup Request. Note that the UE may still get authorization from the ProSe function in order to operate in Proxy mode.
In embodiments, the electronic device logic may include signaling logic 604, which may include radio transmit logic 606 and receive logic 608 coupled to control logic 602. In embodiments, the transmit and/or receive logic may be elements or modules of transceiver logic, as shown 604. The electronic device may be coupled with or include one or more plurality of antenna elements of one or more antennas 610.
The electronic device and/or the components of the electronic device may be configured to perform operations similar to those described elsewhere in this disclosure. In embodiments where the electronic device is a V2X UE, or is implemented into or otherwise part of a V2X UE, the control logic may be to identify a V2X proximity services (ProSe) function. The transmit logic may be to transmit, to the ProSe function, a request for the V2X UE to operate as a V2X proxy.
In some embodiments, the control logic may be to implement a vehicle to anything (V2X) proximity services (ProSe) function. The receive logic may be to receive, from a V2X user equipment (UE), a request for the V2X UE to operate as a V2X proxy in which the V2X UE is able to control V2X operation of one or more other V2X UEs. The transmit logic may be to transmit, in response to the request, an authorization to the V2X UE to operate as a V2X proxy.
In embodiments where the electronic device is implemented in an eNB or a core network (CN) element, the control logic may authorize registration of a WBSS service for a user UE. To authorize registration of the WBSS service for the UE, the control logic may authenticate credentials associated with the UE with a serving network of the UE and/or one or more external ITS servers. In such embodiments, the signaling logic may provide a registration response to the UE. The registration response may include an indication as to whether the UE has been authorized for the WBSS services.
In embodiments where the electronic device is implemented in an eNB, the signaling logic may receive a registration request message from a UE over a LTE-Uu interface. Further, in embodiments where the electronic device is implemented in an eNB, the control logic may include a ProSe authorised indication or a V2X authorized indication in an X2-application protocol (AP) Handover Request message during X2-based handover procedure. The ProSe authorized indication may indicate that the UE is authorized to use ProSe and the V2X authorized indication may indicate that the UE is authorized to use WBSS services and/or wireless local area network (WLAN) direct services.
In embodiments where the electronic device is implemented in a CN element, the CN element may be communicatively coupled via an interface with a serving gateway (SGW) or a packet data network (PDN) gateway (PGW). Furthermore, when the electronic device is implemented in an MME, the signaling logic may receive a message including a capability indication. In such embodiments, the control logic may store the capability indication, and provide the capability information to authorize capabilities indicated by the capability information.
In embodiments, the signaling logic and/or the ProSe logic may be elements or modules of transceiver logic and the like. The electronic device may be coupled with or include one or more plurality of antenna elements of one or more antennas 620. The electronic device and/or the components of the electronic device may be configured to perform operations similar to those described elsewhere in this disclosure. For example, in embodiments where the electronic device is implemented in a UE, the V2X logic may generate a registration request message to be sent to a ProSe Function. The signaling logic may provide the registration request message to the ProSe Function, and the ProSe logic may provide a direct communications session over a DSRC channel when the ProSe Function indicates that the UE is authorized to provide the direct communications session.
As used herein, the term “logic” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. Specifically, the logic may at be at least partially implemented in, or an element of, hardware, software, and/or firmware. In some embodiments, the electronic device logic may be implemented in, or functions associated with the logic may be implemented by, one or more software or firmware modules.
In some embodiments, the electronic device of
In some embodiments, the electronic device of
Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.
The application logic 2 may include one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.
The baseband logic 4 may include one or more single-core or multi-core processors. The processor(s) may include a baseband processor 6 and/or additional or alternative processors 8 that may be designed to implement functions or actions of the control logic, transmit logic, and/or receive logic described elsewhere herein.
The baseband logic may handle various radio control functions that enable communication with one or more radio networks via the RF logic 10. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband logic may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband logic may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband logic is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband logic.
In various embodiments, baseband logic may include logic to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband logic may include logic to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
RF logic 10 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF logic may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, RF logic may include logic to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF logic may include logic to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
In various embodiments, transmit logic, control logic, and/or receive logic discussed or described herein may be embodied in whole or in part in one or more of the RF logic 10, the baseband logic 4, and/or the application logic 2. It should be noted that the various logic types disclosed previously may be combined or separated into different logic types and/or referred to as different logic types. For example, in some embodiments, the baseband logic may be combined with the RF logic to operate as signaling logic, communications logic, and the like.
By way of another example, in some embodiments, the baseband logic, the baseband processor, and/or any other like processing device may be referred to a “processing logic,” “control logic,” and the like. As used herein, the term “logic” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. Specifically, the logic may at be at least partially implemented in, or an element of, hardware, software, and/or firmware. In some embodiments, the electronic device logic may be implemented in, or functions associated with the logic may be implemented by, one or more software or firmware modules.
In some embodiments, some or all of the constituent components of the baseband logic, the application logic, and/or the memory/storage may be implemented together on a system on a chip (SOC).
Memory/storage 12 may be used to load and store data and/or instructions, for example, for system 100. Memory/storage for one embodiment may include any combination of suitable volatile memory (e.g., dynamic random access memory (DRAM)) and/or non-volatile memory (e.g., Flash memory).
In various embodiments, the I/O interface 14 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.
In various embodiments sensor 16 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband logic and/or RF logic to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.
The sensor and the camera in a vehicular environment may be configured to provide situational awareness for a vehicle and any other connected devices. There may be many different camera in different positions and sensor of different types such as laser, sonar, infrared, radar and environmental sensors. The camera and sensors may be coupled to various vehicle safety and autonomy systems such as cooperative adaptive cruise control (CACC), emergency vehicle/forward collision warning, and pre-crash sensing warnings. The camera and sensor may be able to detect any of a variety of different safety conditions and provide these to the application logic for safety applications related to safety services and safety messages.
In various embodiments, the display 20 may include a display (e.g., a liquid crystal display, a touch screen display, etc.).
In various embodiments, the system may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system may have more or less components, and/or different architectures.
In various embodiments, the system may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, a vehicular communication system or device, an in-vehicle infotainment (IVI) system or device, an in-car entertainment (ICE) system or device, a driver monitoring system or device, a driver attention monitoring device or system, an in-vehicle monitoring system or device, etc. In various embodiments, system may have more or less components, and/or different architectures. For example, in some embodiments the RF logic and/or the baseband logic may be embodied in communication logic (not shown).
The communication logic may include one or more single-core or multi-core processors and logic circuits to provide signal processing techniques, for example, encoding, modulation, filtering, converting, amplifying, etc., suitable to the appropriate communication interface over which communications will take place. The communication logic may communicate over wireline, optical, or wireless communication mediums. In embodiments in which the system is configured for wireless communication, the communication logic may include the RF logic and/or baseband logic to provide for communication compatible with one or more radio technologies. For example, in some embodiments, the communication logic may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
Embodiments of the technology herein may be described as related to the third generation partnership project (3GPP) long term evolution (LTE) or LTE-advanced (LTE-A) standards. For example, terms or entities such as eNodeB (eNB), mobility management entity (MME), user equipment (UE), etc. may be used that may be viewed as LTE-related terms or entities. However, in other embodiments the technology may be used in or related to other wireless technologies such as the Institute of Electrical and Electronic Engineers (IEEE) 802.16 wireless technology (WiMax), IEEE 802.11 wireless technology (Wi-Fi), various other wireless technologies such as global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE radio access network (GERAN), universal mobile telecommunications system (UMTS), UMTS terrestrial radio access network (UTRAN), or other 2G, 3G, 4G, 5G, etc. technologies either already developed or to be developed. In those embodiments, where LTE-related terms such as eNB, MME, UE, etc. are used, one or more entities or components may be used that may be considered to be equivalent or approximately equivalent to one or more of the LTE-based terms or entities.
The detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of the described embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the claimed embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the present embodiment with unnecessary detail.
ExamplesExample 1 may include a system including V2X UEs, one or more V2X ProSe functions and external servers, in which a V2X UE sends a request to the ProSe function to operate as a V2X Proxy;
Example 2 may include the system of example 1 or some other example herein, in which V2X UEs operating as V2X Proxy are able to control the V2X operation configuration of other V2X UEs;
Example 3 may include the system of example 1 or some other example herein, in which the V2X UE includes its Proxy configuration parameters in the request sent to the V2X ProSe function including supported services identifiers (PSID), coverage area and whether the UE can operate out of coverage;
Example 4 may include the system of example 1 or some other example herein, in which the V2X ProSe function may forward the Proxy request to other V2X ProSe Functions and/or external servers in order to get authorization for enabling the V2X UE to operate as a V2X Proxy;
Example 5 may include the system of example 1 or some other example herein, in which the V2X ProSe function is a V2X specific functionality that is implemented as part of the ProSe function;
Example 6 may include the system of example 1 or some other example herein, in which the V2X ProSe function is a V2X specific functionality that is implemented as a standalone function;
Example 7 may include the system of example 1 or some other example herein, in which the V2X ProSe function sends a response to the V2X UE including the authorization and V2X Proxy configuration that the UE is allowed to use in order to operate as a V2X Proxy, which includes the coverage area, the out of coverage authorization and the validity.
Example 8 may include the system of example 1 or some other example herein, in which a V2X Proxy announces its capability by setting a proxy field (P) in V2X messages transmitted over the PC5 interface;
Example 9 may include the system of example 1 or some other example herein, in which a V2X Proxy may use a combination of location, service subscription and higher layer context information to decide where and when to update V2X Operation of one or more UEs by including the V2X Proxy header in its V2X messages containing the V2X operation information.
Example 10 may include the system of example 1 or some other example herein, where V2X UEs that are capable and authorized to implement configuration updates from the V2X Proxy assistance use V2X operation information in the announcement message to update their configuration accordingly;
Example 11 may include the system of example 1 or some other example herein, in which V2X UEs may request a V2X Proxy to update its V2X operation configuration;
Example 12 may include the system of example 1 or some other example herein, in which the V2X Proxy may authorize the UE request to update its V2X configuration and sends back a response with the approved configuration to be used;
Example 13 may include the system of example 1 or some other example herein, in which V2X UEs and V2X Proxy exchange V2X messages and/or one or more basic safety messages (BSMs) while outside network coverage.
Example 14 may include the system of example 1 or some other example herein, in which the V2X Proxy implements both PC5 and user-plane interfaces;
Example 15 may include the system of example 1 or some other example herein, in which V2X UEs may include the V2X Proxy capability indication as part of the “UE Network Capability” in the Attach Request and/or Tracking Area Update Request message.
Example 16 may include the system of example 1 or some other example herein, in which the MME may include a Proxy authorization indication in the S1 AP Initial Context Setup Request, also indicating whether the UE is capable of supporting V2X Proxy services.
Example 17 may include a vehicle to anything (V2X) user equipment (UE) comprising: control logic to: identify a V2X proximity services (ProSe) function; and transmit logic coupled with the control logic, the transmit logic to transmit, to the ProSe function, a request for the V2X UE to operate as a V2X proxy.
Example 18 may include the V2X UE of example 17 or some other example herein, wherein the control logic is to control V2X operation configuration(s) of one or more other V2X UEs when the V2X UE is a V2X proxy.
Example 19 may include the V2X UE of example 17 or some other example herein, wherein the request includes one or more of: an indication of one or more proxy configuration parameters of the V2X UE, an indication of one or more supported services identifiers (PSIDs), an indication of coverage area, and/or an indication of whether the V2X UE can operate out of the coverage area.
Example 20 may include the V2X UE of example 17 or some other example herein, further comprising receive logic coupled with the transmit logic, the receive logic to receive, from the V2X ProSe function, an authorization related to the request, wherein the authorization includes an indication of a V2X Proxy configuration, a coverage area, an out of coverage authorization and/or validity.
Example 21 may include the V2X UE of example 17 or some other example herein, wherein the transmit logic is further to transmit a capability announcement that includes a proxy field (P) in one or more V2X messages transmitted over a PC5 interface.
Example 22 may include the V2X UE of example 17 or some other example herein, wherein the control logic is to use a combination of location, service subscription and higher layer context information decide where and when to update V2X Operation of one or more UEs by including the V2X Proxy head in its V2X messages containing the V2X operation information.
Example 23 may include the V2X UE of example 22 or some other example herein, where V2X UEs that are capable and authorized to implement configuration updates from the V2X Proxy assistance use V2X operation information in the announcement message to update their configuration accordingly;
Example 24 may include the V2X UE of example 17 or some other example herein, further comprising receive logic coupled with the control logic, the receive logic to receive, from one or more other V2X UEs, a request for the V2X UE to update its V2X operation configuration.
Example 25 may include the V2X UE of example 24 or some other example herein, wherein the transmit logic is further to transmit, based on the request, an authorization that includes an approved configuration.
Example 26 may include the V2X UE of example 17 or some other example herein, in which the V2X UE is to exchange, via the transmit logic and/or receive logic coupled with the transmit logic, one or more V2X messages and/or one or more basic safety messages (BSMs) with another UE while outside network coverage.
Example 27 may include the V2X UE of example 17 or some other example herein, in which the control logic, transmit logic and/or receive logic are to implement both PC5 and user-plane interfaces.
Example 28 may include the V2X UE of example 17 or some other example herein, in which one or more UEs with which the V2X UE is communicatively coupled are to include a V2X Proxy capability indication as part of a “UE Network Capability” indication in an Attach Request and/or Tracking Area Update Request message.
Example 29 may include the V2X UE of example 17 or some other example herein, further comprising receive logic coupled with the transmit logic, the receive logic to receive, from a mobility management entity (MME), a Proxy authorization indication in a S1 AP Initial Context Setup Request, also indicating whether the V2X UE is capable of supporting V2X Proxy services.
Example 30 may include a method comprising: identifying, by a vehicle to anything (V2X) user equipment (UE), that the V2X UE is to operate as a V2X proxy; and transmitting, by the V2X UE to a proximity services (ProSe) function, a request for the V2X UE to operate as the V2X proxy.
Example 31 may include the method of example 30 or some other example herein, further comprising controlling, by the V2X UE, V2X operation configuration(s) of one or more other V2X UEs when the V2X UE is a V2X proxy.
Example 32 may include the method of example 30 or some other example herein, wherein the request includes one or more of: an indication of one or more proxy configuration parameters of the V2X UE, an indication of one or more supported services identifiers (PSIDs), an indication of coverage area, and/or an indication of whether the V2X UE can operate out of the coverage area.
Example 33 may include the method of example 30 or some other example herein, further comprising receiving, by the V2X UE from the V2X ProSe function, an authorization related to the request, wherein the authorization includes an indication of a V2X Proxy configuration, a coverage area, an out of coverage authorization and/or validity.
Example 34 may include the method of example 30 or some other example herein, further comprising transmitting, by the V2X UE, a capability announcement that includes a proxy field (P) in one or more V2X messages transmitted over a PC5 interface.
Example 35 may include the method of example 30 or some other example herein, wherein the V2X UE is to use a combination of location, service subscription and higher layer context information decide where and when to update V2X Operation of one or more UEs by including the V2X Proxy header in its V2X messages containing the V2X operation information.
Example 36 may include the method of example 35 or some other example herein, where V2X UEs that are capable and authorized to implement configuration updates from the V2X Proxy assistance use V2X operation information in the announcement message to update their configuration accordingly;
Example 37 may include the method of example 30 or some other example herein, further comprising receiving, by the V2X UE from one or more other V2X UEs, a request for the V2X UE to update its V2X operation configuration.
Example 38 may include the method of example 37 or some other example herein, further comprising transmitting, by the V2X UE based on the request, an authorization that includes an approved configuration.
Example 39 may include the method of example 30 or some other example herein, further comprising exchanging, by the V2X UE, one or more V2X messages and/or one or more basic safety messages (BSMs) with another UE while outside network coverage.
Example 40 may include the method of example 30 or some other example herein, in which the V2X UE is to implement both PC5 and user-plane interfaces.
Example 41 may include the method of example 30 or some other example herein, in which one or more UEs with which the V2X UE is communicatively coupled are to include a V2X Proxy capability indication as part of a “UE Network Capability” indication in an Attach Request and/or Tracking Area Update Request message.
Example 42 may include the method of example 30 or some other example herein, further comprising receiving, by the V2X UE, from a mobility management entity (MME), a Proxy authorization indication in a S1 AP Initial Context Setup Request, also indicating whether the V2X UE is capable of supporting V2X Proxy services.
Example 43 may include an electronic device comprising: control logic to implement a vehicle to anything (V2X) proximity services (ProSe) function; receive logic coupled with the control logic, the receive logic to receive, from a V2X user equipment (UE), a request for the V2X UE to operate as a V2X proxy in which the V2X UE is able to control V2X operation of one or more other V2X UEs; and transmit logic coupled with the receive logic, the transmit logic to transmit, in response to the request, an authorization to the V2X UE to operate as a V2X proxy.
Example 44 may include the electronic device of example 43 or some other example herein, wherein the request includes one or more of: an indication of one or more proxy configuration parameters of the V2X UE, an indication of one or more supported services identifiers (PSIDs), an indication of coverage area, and/or an indication of whether the V2X UE can operate out of the coverage area.
Example 45 may include the electronic device of example 43 or some other example herein, wherein the transmit logic is further to forward the request to one or more other V2X ProSe functions and/or external servers; and the receive logic is to receive an indication of authorization from the one or more other V2X ProSe functions and/or external servers.
Example 46 may include the electronic device of example 45 or some other example herein, wherein the authorization to the V2X UE includes the authorization from the one or more other V2X ProSe functions and/or external servers, an indication of a V2X Proxy configuration, an indication of a coverage area, an indication of an out of coverage authorization, and/or an indication of validity.
Example 47 may include the electronic device of example 43 or some other example herein, wherein the control logic is to implement the V2X ProSe function as a V2X specific functionality that is implemented as part of a ProSe function and/or as a standalone function.
Example 48 may include a method comprising: receiving, by a V2X proximity services (ProSe) function from a V2X user equipment (UE), a request for the V2X UE to operate as a V2X proxy in which the V2X UE is able to control V2X operation of one or more other V2X UEs; and transmitting, by the V2X ProSe function in response to the request, an authorization to the V2X UE to operate as a V2X proxy.
Example 49 may include the method of example 48 or some other example herein, wherein the request includes one or more of: an indication of one or more proxy configuration parameters of the V2X UE, an indication of one or more supported services identifiers (PSIDs), an indication of coverage area, and/or an indication of whether the V2X UE can operate out of the coverage area.
Example 50 may include the method of example 48 or some other example herein, further comprising forwarding, by the V2X ProSe function, the request to one or more other V2X ProSe functions and/or external servers; and receiving, by the V2X ProSe function, an indication of authorization from the one or more other V2X ProSe functions and/or external servers.
Example 51 may include the method of example 50 or some other example herein, wherein the authorization to the V2X UE includes the authorization from the one or more other V2X ProSe functions and/or external servers, an indication of a V2X Proxy configuration, an indication of a coverage area, an indication of an out of coverage authorization, and/or an indication of validity.
Example 52 may include the method of example 48 or some other example herein, wherein the V2X ProSe function is implemented as a V2X specific functionality that is implemented as part of a ProSe function and/or as a standalone function.
Example 53 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-26, 30-42, 48-52, and/or any other method or process described herein.
Example 54 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-26, 30-42, 48-52, and/or any other method or process described herein.
Example 55 may include an apparatus comprising control logic, transmit logic, and/or receive logic to perform one or more elements of a method described in or related to any of examples 1-26, 30-42, 48-52, and/or any other method or process described herein.
Example 56 may include a method of communicating in a wireless network as shown and described herein.
Example 57 may include a system for providing wireless communication as shown and described herein.
Example 58 may include a device for providing wireless communication as shown and described herein.
The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the claims to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various implementations.
In the following description and claims, the term “coupled” along with its derivatives, may be used. “Coupled” is used to indicate that two or more elements co-operate or interact with each other, but they may or may not have intervening physical or electrical components between them.
As used in the claims, unless otherwise specified, the use of the ordinal adjectives “first”, “second”, “third”, etc., to describe a common element, merely indicate that different instances of like elements are being referred to, and are not intended to imply that the elements so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.
The following examples pertain to further embodiments. The various features of the different embodiments may be variously combined with some features included and others excluded to suit a variety of different applications. Some embodiments pertain to a machine-readable medium having instructions thereon that when operated on by the machine cause the machine to perform operations that include a machine-readable medium having instructions thereon that when operated on by the machine cause the machine to perform operations that include receiving a proxy operation authorization at a first user equipment (UE) from a vehicle to anything (V2X) proximity services (ProSe) function for the first UE to operate as a Proxy UE for the ProSe function, controlling configuration information by the first UE of other UEs, controlling by the first UE a V2X operation mode.
Further embodiments include controlling cooperative messages transmission rates of the other UEs by the first UE.
In further embodiments the cooperative messages comprise basic safety messages (BSM).
Further embodiments include transmitting a V2X message from the proxy UE having a header that includes a field announcing that the proxy UE is operating as a proxy UE for a ProSe function.
In further embodiments the proxy UE operates as a proxy UE by performing V2X configuration functions within its coverage range on behalf of the V2X ProSe Function.
Further embodiments include verifying the credentials of the UE at the V2X ProSe function.
In further embodiments verifying the credentials comprises sending the credentials to the V2X ProSe function during initial service authorization, and wherein receiving a proxy authorization comprises receiving a proxy operation authorization at the proxy UE if the credentials are verified by the ProSe function.
In further embodiments the proxy UE is pre-configured with information to operate as a V2X Proxy
In further embodiments the proxy UE requests proxy information from a ProSe function
In further embodiments the ProSe function verifies the proxy UE by consulting external servers, for example. geolocation and International Traffic System (ITS) servers, to decide whether the proxy UE should be allowed to operate as a V2X Proxy.
Further embodiments include the proxy UE advertising its status as a V2X Proxy by sending messages using a header that indicates that the proxy UE is authorized as a V2X proxy.
In further embodiments the header has a bit set to indicate a V2X proxy status.
Some embodiments relate to processing circuitry of a user equipment (UE) in a vehicular environment. The processing circuitry is to detect the presence of a vehicle to anything (V2X) Proxy user equipment (UE) by a V2X UE, request, by the UE, the V2X Proxy UE to update V2X operation parameters of the UE, and if the V2X Proxy UE authorizes the new requested configuration, the UE receiving updated operation parameters for V2X from the V2X Proxy UE.
In further embodiments the request includes a V2X Proxy address as a destination address, the requested operational parameters in a V2X information element (IE), and the provider service identifiers (PSID(s)) to which the request applies.
Further embodiments include confirming reception of the operation parameters to the V2X Proxy by setting an A bit in a next V2X ProSe header transmission from the UE.
In further embodiments requesting comprises requesting through a wireless local area network interface for direct communication with the V2X Proxy UE.
In further embodiments the V2X Proxy UE has an ITS application, and sends the message received from the UE to the application.
In further embodiments sending the message comprises forwarding the messages through an eNB, to a ProSe/V2X function in the core network.
In further embodiments the V2X Proxy UE conditionally sends the message based on the message type and an indication in the media access control layer header.
In further embodiments the V2X Proxy UE authorizes the UE based on a subscription of the UE.
Further embodiments include receiving by the V2X Proxy UE from an mobility management entity (MME) a Proxy authorization indication in an S1 AP Initial Context Setup Request.
Further embodiments include receiving an Attach Request and/or Tracking Area Update Request message including a V2X Proxy capability indication as part of the “UE Network Capability” from the V2X Proxy UE and wherein requesting is performed after receiving the message.
Further embodiments include a UE with the processing circuitry and baseband logic to provide communication with the V2X proxy UE to receive the updated operation parameters.
Some embodiments relate to an apparatus that includes control logic of a vehicular user equipment (UE) to generate a registration request to operate as a vehicle to anything (V2X) proxy, and signaling logic coupled to the control logic to send the registration request to an enhanced node B (eNB) and to receive a response including an authorized V2X proxy configuration from the enB.
Further embodiments include a sensor coupled to the control logic to detect a safety condition and to provide the safety condition to the control logic, the signaling logic to send a basic safety message (BSM) based on the safety condition.
Claims
1-20. (canceled)
21. A machine-readable medium having instructions thereon that when operated on by the machine cause the machine to perform operations comprising:
- receiving authorization at a first user equipment (UE) at a vehicle from a function specifying the first UE is to send V2X configuration information to other UEs, the V2X configuration information configured by the network;
- communicating directly, by the first UE, with the other UEs by sending the V2X configuration information to the other UEs; and
- controlling, by the first UE sending the V2X configuration information, V2X operation of at least one of the other UEs.
22. The medium of claim 21 further comprising determining sidelink interface resources associated with the other UEs.
23. The medium of claim 22 wherein controlling of V2X operation by the first UE is by transmitting the V2X configuration information via a sidelink interface, associated with the determined the sideline interface resources, without direct involvement of the network.
24. The medium of claim 21 wherein sending the V2X configuration information is via direct communication between pairs of UEs through a sidelink interface.
25. The medium of claim 21 wherein the first UE receives the V2X configuration information from the network in a response message.
26. The medium of claim 21 wherein the V2X configuration information configures the other UEs to control message transmission.
27. The medium of claim 21 further comprising detecting, by the first UE, presence of the other UEs that are proximate to the first UE, establish a direct communication, by the first UE, with each of the other UEs, and communicating with the other UEs over the direction connection.
28. The medium of claim 21 further comprising controlling cooperative messages transmission rates of the other UEs by the first UE.
29. The medium of claim 28 wherein the cooperative messages comprise basic safety messages (BSM).
30. Processing circuitry of a user equipment (UE) in a vehicular environment, the circuitry to:
- receive authorization at a first user equipment (UE) at a vehicle from a function specifying the first UE is to send V2X configuration information to other UEs, the V2X configuration information configured by the network;
- communicate directly, by the first UE, with the other UEs by sending the V2X configuration information to the other UEs; and
- control, by the first UE sending the V2X configuration information, V2X operation of at least one of the other UEs.
31. The processing circuitry of claim 30 further comprising determining sidelink interface resources associated with the other UEs.
32. The processing circuitry of claim 31 wherein V2X operation is controlled by the first UE is by transmitting the V2X configuration information via a sidelink interface, associated with the determined the sideline interface resources, without direct involvement of the network.
33. The processing circuitry of claim 30 wherein the V2X configuration information is sent via direct communication between pairs of UEs through a sidelink interface.
34. The processing circuitry of claim 30 wherein the first UE receives the V2X configuration information from the network in a response message.
35. The processing circuitry of claim 30 wherein the V2X configuration information configures the other UEs to control message transmission.
36. The processing circuitry of claim 30 further comprising detecting, by the first UE, presence of the other UEs that are proximate to the first UE, establish a direct communication, by the first UE, with each of the other UEs, and communicating with the other UEs over the direction connection.
37. The processing circuitry of claim 30 further comprising controlling cooperative messages transmission rates of the other UEs by the first UE.
38. The processing circuitry of claim 37 wherein the cooperative messages comprise basic safety messages (BSM).
39. A first UE at a vehicle comprising:
- control logic to receive authorization from a function specifying the first UE is to send V2X configuration information to other UEs, the V2X configuration information configured by the network; and
- signaling logic coupled to the control logic to communicate directly with the other UEs by sending the V2X configuration information to the other UEs, and control, by sending the V2X configuration information, V2X operation of at least one of the other UEs.
40. The first UE of claim 39 wherein the signaling logic is operable to:
- determine sidelink interface resources associated with the other UEs; and
- transmitting the V2X configuration information via a sidelink interface, associated with the determined the sideline interface resources, without direct involvement of the network in order to control the V2X operations of the other UEs.
Type: Application
Filed: Jul 6, 2020
Publication Date: Nov 24, 2022
Inventors: Dave CAVALCANTI (Portland, OR), Anna Lucia PINHEIRO (Hillsboro, OR)
Application Number: 16/921,746
