阅读说明：本技术 网络节点、交通工具到一切事物应用使能器客户端、及其中执行的方法 (Network node, vehicle-to-everything application enabler client, and methods performed therein ) 是由 A·厄尔厄赛利 臧云鹏 于 2019-12-23 设计创作，主要内容包括：本文实施例可以例如提供一种由无线装置的交通工具到一切事物应用使能器VAE客户端执行的用于将无线通信网络中的服务用于交通工具到一切事物V2X无线装置的方法。VAE客户端从V2X应用特定客户端接收具有服务ID的服务的V2X消息；并且基于服务ID来确定用于接收上行链路V2X消息的网络节点。VAE客户端进一步将上行链路V2X消息与服务ID一起传送到所确定的网络节点。(Embodiments herein may, for example, provide a method performed by a vehicle-to-everything application enabler, VAE, client of a wireless device for using services in a wireless communication network for a vehicle-to-everything V2X wireless device. The VAE client receives a V2X message of a service with a service ID from the V2X application-specific client; and determines a network node for receiving the uplink V2X message based on the service ID. The VAE client further transmits an uplink V2X message to the determined network node along with the service ID.)

1. A method performed by a vehicle-to-everything application enabler, VAE, client of a wireless device (10) for using services in a wireless communication network for a vehicle-to-everything V2X wireless device, the method comprising:

-receiving (712) a V2X message of a service with a service ID from a V2X application specific client;

-determining (713) a network node for receiving an uplink V2X message based on the service ID; and

-transmitting (714) the uplink V2X message with the service ID to the determined network node.

2. The method of claim 1, further comprising

-registering (711), by the VAE client of the wireless device, with the service identified by the service ID.

3. The method according to any of claims 1-2, wherein the uplink V2x message further comprises one or more of: a wireless device identification, a payload of a message, and a geographic identification of a location of the wireless device.

4. The method of any of claims 1-3, further comprising

-receiving (715) a response from the network node indicating success or failure.

5. The method according to any of claims 1-4, wherein the network node is a vehicle-to-everything application enabler server or another server.

6. A method performed by a network node (13) for handling vehicle-to-everything V2X wireless device communication in a wireless communication network, the method comprising:

-receiving (721) an uplink V2X message with a service ID from a vehicle-to-everything application enabler client of a wireless device (10); and

-handling (722) the uplink V2X message taking into account the service ID.

7. The method according to claim 6, wherein the network node (13) is a vehicle-to-everything application enabler server.

8. The method of claim 7, wherein the vehicle-to-everything application enabler server provides the uplink V2X message to a V2X application specific server.

9. A vehicle-to-everything application enabler, VAE, client for a wireless device (10) that uses services in a wireless communication network for a vehicle-to-everything V2X wireless device, wherein the VAE client is configured to:

-receiving a V2X message of a service with a service ID from a V2X application specific client;

-determining a network node for receiving an uplink V2X message based on the service ID; and

-transmitting the uplink V2X message with the service ID to the determined network node.

10. The VAE client according to claim 9, wherein the VAE client is further configured to

Register with the service identified by the service ID.

11. The VAE client according to any one of claims 9-10, wherein the uplink V2x message further includes one or more of: a wireless device identification, a payload of a message, and a geographic identification of a location of the wireless device.

12. The VAE client according to any one of claims 9-11, wherein the VAE client is further configured to

Receiving a response from the network node indicating success or failure.

13. A network node for handling vehicle-to-everything V2X wireless device communication in a wireless communication network, wherein the network node is configured to:

-receiving an uplink V2X message with a service ID from a vehicle-to-everything application enabler client of a wireless device; and

-handling the uplink V2X message taking into account the service ID.

14. The network node of claim 13, wherein the network node is a vehicle-to-everything application enabler server.

15. The network node of claim 14, wherein the vehicle-to-everything application enabler server is configured to handle the uplink V2X message by providing the uplink V2X message to a V2X application specific server.

16. A computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1-8 as performed by a VAE client or network node, respectively.

17. A computer-readable storage medium having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of claims 1-8 as performed by a VAE client or network node, respectively.

Technical Field

Embodiments herein relate to a network node, a vehicle-to-everything application enabler (VAE) client of a wireless device, and methods performed therein. Further, a computer program product and a computer readable storage medium are provided herein. In particular, embodiments herein relate to enabling vehicle-to-everything (V2X) wireless device communication in a wireless communication network.

Background

In a typical wireless communication network, wireless devices (also referred to as wireless communication devices), mobile stations, Stations (STAs), vehicles, and/or User Equipment (UE) communicate via a Radio Access Network (RAN) with one or more Core Networks (CNs). The RAN covers a geographical area and provides radio coverage over a service area or cell, which may also be referred to as a beam or a group of beams, where each service area or beam is served or controlled by a radio network node, such as a radio access node, e.g. a Wi-Fi access point or a Radio Base Station (RBS), which in some networks may also be denoted e.g. NodeB, eNodeB or gnnodeb. The radio network node communicates over an air interface operating on radio frequencies with wireless devices within range of the radio network node.

Universal mobile telecommunications network (UMTS) is a third generation (3G) telecommunications network that has evolved from the second generation (2G) global system for mobile communications (GSM). UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and/or High Speed Packet Access (HSPA) for user equipment. In a forum known as the third generation partnership project (3 GPP), telecommunications providers propose and agree to standards for third generation networks and investigate enhanced data rates and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g. by landlines or microwave, to a controller node, such as a Radio Network Controller (RNC) or a Base Station Controller (BSC), which supervises and coordinates various activities of the plurality of radio network nodes connected thereto. This type of connection is sometimes referred to as a backhaul connection. The RNCs and BSCs are typically connected to one or more core networks.

The specification of Evolved Packet System (EPS), also known as fourth generation (4G) networks, has been completed within the third generation partnership project (3 GPP) and this work continues in future 3GPP releases, for example to specify fifth generation (5G) networks. The EPS includes an evolved universal terrestrial radio access network (E-UTRAN), also known as a Long Term Evolution (LTE) radio access network, and an Evolved Packet Core (EPC), also known as a System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a variant of the 3GPP radio access network, where the radio network nodes are directly connected to the EPC core network instead of the RNC. Typically, in E-UTRAN/LTE, the functionality of the RNC is distributed between a radio network node (e.g. an eNodeB in LTE) and the core network. As such, the RAN of an EPS essentially has a "flat" architecture, comprising radio network nodes directly connected to one or more core networks, i.e. they are not connected to an RNC. To compensate for this, the E-UTRAN specification defines a direct interface between radio network nodes, which is denoted as the X2 interface.

For 5G systems currently being standardized by 3GPP, where the radio access network is referred to as new air interface (NR) and the core network is referred to as Next Generation Core (NGC), the 3GPP has agreed to partially change the distribution principle of System Information (SI) used in LTE.

During release 12, the LTE standard has been extended with support for device-to-device (D2D), which is specified as a "sidelink", a feature for both business and public safety applications. Some applications enabled by Rel-12 LTE are device discovery, where a wireless device is able to sense the proximity of another wireless device and associated applications by broadcasting and detecting discovery messages carrying wireless device and application identities. Another application consists of direct communication based on physical channels that terminate directly between wireless devices. In 3GPP, all these applications are defined under the general term denoted proximity services (ProSe).

One of the potential extensions of the ProSe framework consists of support for vehicle-to-everything (V2X) communications, including any combination of direct communications between vehicles, pedestrians, and infrastructure. When available, V2X communication may utilize Network (NW) infrastructure, but even in the absence of coverage, at least basic V2X connectivity should be possible. Due to LTE economies of scale, providing an LTE-based V2X interface may be economically advantageous, and it may enable tighter integration between communications with NW infrastructure (e.g., vehicle-to-infrastructure (V2I) and vehicle-to-pedestrian (V2P) and vehicle-to-vehicle (V2V) communications) than using dedicated V2X technology.

There are many research projects and field tests of connected vehicles in various countries or regions, including projects based on using existing cellular infrastructure.

V2X communications may carry both non-secure and secure information, where each of the applications and services may be associated with specific requirements in terms of, for example, latency, reliability, capacity, etc. From an application point of view, V2X includes the following types of communications/services illustrated with respect to fig. 1.

Vehicle-to-vehicle (V2V): this covers communication between vehicles using V2V applications and is primarily broadcast-based. V2V may be implemented by direct communication between devices in the respective vehicles or via an infrastructure such as a cellular network. An example of V2V is the transmission of a Cooperative Awareness Message (CAM) with vehicle status information such as location, direction, and speed, which is repeatedly transmitted to other vehicles in the vicinity, for example, every 100ms-1 s. Another example is the transmission of a Decentralized Environment Notification Message (DENM), which is an event triggered message that is used to alert a vehicle. These two examples are taken from the ETSI Intelligent Transportation System (ITS) specification applied by V2X, which also specifies the conditions under which the messages are generated. The main feature of V2V applications is the strict requirement for latency, which can vary from 20ms (for pre-crash alert messages) to 100ms for other road safety services.

Vehicle-to-infrastructure (V2I): this includes communication between the vehicle and a Road Side Unit (RSU). The RSU may be a fixed transportation infrastructure entity that communicates with vehicles in the vicinity of the fixed transportation infrastructure entity. An example of V2I is the transmission of: speed notification from RSU to vehicle, as well as queue information, collision risk warning, curve speed alert. Due to the safety-related nature of V2I, the latency requirements are similar to the V2V requirements.

Vehicle-to-pedestrian (V2P): this covers communication between vehicles using V2P applications and vulnerable road users such as pedestrians. V2P generally occurs between different vehicles and pedestrians, either directly or via an infrastructure such as a cellular network.

Vehicle-to-network (V2N): this covers communication between vehicles and centralized application servers (or Intelligent Transportation Systems (ITS) traffic management centers) via infrastructure, such as a cellular network, both using the V2N application. One example is a bad road condition alert sent to all vehicles in a wide area, or traffic flow optimization (where the V2N application suggests speeds to vehicles and coordinates traffic lights). Thus, the V2N message should be controlled by a centralized entity such as a traffic management center and may be provided to vehicles in a large geographic area rather than a small area. In addition, unlike V2V/V2I, the latency requirement is more relaxed in V2N because it is not meant to be used for non-security purposes, e.g., latency requirements of 1s are typically considered.

As mentioned before, side link transmission over the so-called PC5 interface in the cellular spectrum (also referred to as D2D or ProSe) has been standardized in 3GPP since Rel-12. In 3GPP Rel-12, two different transmission modes have been specified in 3 GPP. In one mode (mode-1), a UE in RRC _ CONNECTED mode requests D2D resources and the eNB grants them via a Physical Downlink Control Channel (PDCCH) (also denoted as DCI 5) or via dedicated signaling. In another mode (mode-2), the UE autonomously selects resources for transmission from a pool of available resources that the eNB provides in a broadcast for transmission on a carrier other than a primary cell (PCell) via System Information Block (SIB) signaling or for transmission on the PCell via dedicated signaling. Thus, unlike the first mode of operation, the second mode of operation may also be performed by UEs in RRC IDLE, and in some cases even out of coverage.

In rel.14, the use of sidelink is extended to the V2X domain. The original design of the sidelink physical layer in rel.12 targets scenarios with a small number of wireless devices, such as UEs competing for the same physical resources in the spectrum, to carry voice packets for mission critical push-to-talk (MCPTT) traffic and assumes low wireless device mobility. On the other hand, in V2X, the sidelink should be able to cope with higher load scenarios (i.e., hundreds of cars that may contend for physical resources) to carry time/event triggered V2X messages, such as Collaboration Awareness Messages (CAM) and Decentralized Environment Notification Messages (DENM), and have high wireless device mobility. For such reasons, 3GPP has discussed possible enhancements to the side-link physical layer.

The present disclosure relates to Intelligent Transport Systems (ITS) and V2X communications from a V2X application server and a V2X application client to a wireless device called a V2X wireless device, the V2X communications using V2X group communications over long range cellular unicast communications over an interface LTE Uu.

The ITS messages are designed to enable ITS applications to improve the safety and traffic efficiency of road transport systems. In several V2X applications (e.g., remote operations, fleet management), V2X communication from a V2X application server to a V2X wireless device requires group communication. The group management service will provide V2X Application Enabler (VAE) support for communication from V2X wireless devices or V2X application servers to groups of V2X wireless devices to support V2X services, such as queuing groups, remote operation of automated vehicles.

3GPP TS 23.386 [1] defines a V2X application layer model for PC5 and V2X communication over LTE-Uu. This model is shown in fig. 2. The V2X Application Enabler (VAE) layer provides support information to V2X applications.

The V2X UE1 communicates with the V2X application server through the V1 reference point. V2X UE1 and V2X UE2 communicate over a V5 reference point. V2X UE1 may also act as a UE-to-network relay to enable V2X UE2 to access the V2X application server through the V1 reference point.

The V2X application layer functional entities for the V2X wireless devices and the V2X application servers are grouped into a V2X application specific layer and a VAE layer. The VAE layer provides VAE capabilities to V2X application specific layers. The V2X application layer functional model utilizes SEAL services as specified in 3GPP TS 23.434 [2 ].

The VAE server is located in the VAE layer. The SEAL services utilized by the VAE layer are location management, group management, configuration management, identity management, key management, and network resource management. The V2X application specific layer consists of V2X application specific functionality.

The V2X application servers include VAE servers, SEAL servers, and V2X application specific servers. The VAE server provides V2X application-specific servers with V2X application-layer support functions through a Vs reference point.

The V2X UE includes VAE clients, SEAL clients, and V2X application specific clients. The VAE client provides V2X application-layer support functionality to the V2X application-specific client through the Vc reference point.

In some deployments, the client and server entities of the SEAL may be part of the VAE client and VAE server, respectively.

The VAE client acts as a VAL client for its interaction with SEAL clients, as specified in 3GPP TS 23.434 [2 ]. The VAE server may act as a Vertical Application Layer (VAL) server for its interaction with a Service Enabler Architecture Layer (SEAL) server for a vertical, as specified in 3GPP TS 23.434 [2 ].

In the VAE layer, a VAE client communicates with a VAE server through a V1-AE reference point. In the V2X application specific layer, the V2X application specific client communicates with the V2X application specific server through the V1-APP reference point.

In the VAE layer, VAE clients of V2X UE2 communicate with VAE clients of V2X UE1 through V5-AE reference points. In the V2X application specific layer, the V2X application specific client of the V2X UE2 communicates with the VAE client of the V2X UE1 through the V5-APP reference point.

The following SEAL services supporting V2X applications:

-location management as specified in 3GPP TS 23.434 [2 ];

group management as specified in 3GPP TS 23.434 [2 ];

-configuration management as specified in 3GPP TS 23.434 [2 ];

identity management as specified in 3GPP TS 23.434 [2 ];

key management as specified in 3GPP TS 23.434 [2 ]; and

network resource management as specified in 3GPP TS 23.434 [2 ].

The VAE client interacts with the SEAL client through the SEAL-C reference point specified for each SEAL service. The VAE server interacts with the SEAL server through the SEAL-S reference points specified for each SEAL service. The interaction between the SEAL clients is supported by the SEAL-PC5 reference point specified for each SEAL service. The interaction between the SEAL client and the corresponding SEAL server is supported by a SEAL-UU reference point specified for each SEAL service.

The SEAL-C, SEAL-S, SEAL-PC, SEAL-Uu reference point for each SEAL service is specified in 3GPP TS 23.434 [2 ].

To support distributed VAE server deployment, a VAE server interacts with another VAE server through a VAE-E reference point.

V2X UE1 may also act as a UE-to-network relay,

to enable VAE clients on V2X UE2 to access the VAE server through the V1-AE reference point; and

to enable V2X application specific clients on V2X UE2 to access V2X application specific servers through the V1-APP reference point.

The V1-AE message may be sent by unicast, transparent multicast via xMB, transparent multicast via MB 2. Non-transparent multicast via xMB is triggered by a V1-AE message. Multicast distribution may be supported by both transparent and non-transparent multicast modes.

The VAE server interacts with the 3GPP network system through V2, MB2, xMB, Rx, and T8 reference points. EPS is considered a 3GPP network system.

Disclosure of Invention

The current technical specification [1] includes only the downlink V2X distribution procedure. Uplink V2X is not specified to deliver information flow and procedures.

It is an object of embodiments herein to provide a mechanism to improve the performance of a wireless communication network with respect to vehicle-to-everything communication in an efficient manner.

According to an aspect, the object is achieved by providing a method performed by a network node for managing or handling communication of a V2X wireless device in a wireless communication network. The network node receives an uplink V2x message with a service ID from the VAE client of the wireless device. The network node then handles the UL V2X message in view of the service ID.

According to another aspect, the object is achieved by providing a method performed by a VAE client of a wireless device for using a service in a wireless communication network for a V2X wireless device. The VAE client receives a V2X message for a service with a service ID from the V2X application specific client. The VAE client determines a network node for receiving the uplink V2X message based on the service ID and transmits the uplink V2X message to the determined network node together with the service ID. For example: a wireless device for communicating, handling, or using a service in a wireless communication network is disclosed herein. The wireless device determines a network node for receiving an uplink message, such as a V2x message, based on the service ID. The wireless device then transmits the uplink message to the determined network node along with the service ID.

According to a further aspect, the object is achieved by providing a VAE client for a wireless device that uses a service in a wireless communication network for a V2X wireless device. The VAE client is configured to receive a V2X message for a service with a service ID from a V2X application-specific client. The VAE client further determines a network node for receiving the uplink V2X message based on the service ID; and transmitting the uplink V2X message with the service ID to the determined network node.

According to a further aspect, the object is achieved by providing a network node for handling communication of a V2X wireless device in a wireless communication network. The network node is configured to receive an uplink V2X message with a service ID from a VAE client of a wireless device; and handling the uplink V2X message in consideration of the service ID.

Furthermore, a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out any one of the above methods as performed by a VAE client or a network node, respectively, is provided herein. Additionally, a computer-readable storage medium having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of the above methods as performed by a VAE client or a network node, respectively.

The embodiments herein describe the procedure and information flow for uplink V2X message delivery from a V2X UE to a network node and a V2X application server over e.g. the radio interface LTE Uu. Further, procedures and information flows are also defined via V2X UE to V2X UE of LTE Uu. Further, optimization for uplink V2X message delivery is provided herein.

The embodiments herein enable VAE clients of wireless devices, such AS V2X UEs, to deliver uplink V2X messages to network nodes, such AS servers, V2X AS, and other wireless devices, and specify protocols and message fields. This will lead to improved performance of the wireless communication network.

Drawings

Embodiments will now be described in more detail with respect to the accompanying drawings, in which:

FIG. 1 is a schematic logic overview depicting vehicle communications;

FIG. 2 is a schematic block diagram depicting vehicle communications;

fig. 3 is a schematic diagram depicting a wireless communication network according to embodiments herein;

fig. 4 is a combined flow diagram and signaling scheme according to some embodiments herein;

fig. 5 is a combined flow diagram and signaling scheme according to some embodiments herein;

fig. 6 is a combined flow diagram and signaling scheme according to some embodiments herein;

fig. 7a is a combined flow chart and signaling scheme according to some embodiments herein;

fig. 7b is a flow diagram depicting a method performed by a VAE client according to some embodiments herein;

fig. 7c is a flow diagram depicting a method performed by a network node according to some embodiments herein;

fig. 8 is a schematic block diagram depicting a wireless device having a VAE client in accordance with embodiments herein;

fig. 9 is a schematic block diagram depicting a network node according to embodiments herein;

FIG. 10 schematically illustrates a telecommunications network connected to a host computer via an intermediate network;

FIG. 11 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partial wireless connection; and

fig. 12-15 are flow diagrams illustrating methods implemented in a communication system including a host computer, a base station, and a user equipment.

Detailed Description

Embodiments herein relate generally to wireless communication networks. Fig. 3 is a schematic overview depicting a wireless communication network 1. The wireless communication network 1 includes one or more RANs and one or more Core Networks (CNs). The wireless communication network 1 may use one or more different technologies such as new air interface (NR), Wi-Fi, Long Term Evolution (LTE), LTE-advanced, 5G, Wideband Code Division Multiple Access (WCDMA), global system for mobile communications/enhanced data rates for GSM evolution (GSM/EDGE), worldwide interoperability for microwave access (WiMax), or Ultra Mobile Broadband (UMB), to mention just a few possible implementations. The embodiments herein relate to recent technical trends of particular interest in the 5G context, however, the embodiments may also be applied to further developments of existing wireless communication networks, such as e.g. WCDMA and LTE.

In the wireless communication network 1, a wireless device 10, e.g., a mobile station, a non-access point (non-AP) STA, a STA, user equipment and/or a wireless terminal, referred to herein as a V2X UE having VAE client(s), may communicate with one or more Core Networks (CNs) via one or more Access Networks (ANs), e.g., RANs. Those skilled in the art will appreciate that "wireless device" is a non-limiting term meaning any terminal, wireless communication terminal, user equipment, internet of things (IoT) -capable device, Machine Type Communication (MTC) device, device-to-device (D2D) terminal, or node, such as a smartphone, laptop, mobile phone, sensor, relay, mobile tablet, or even a small base station communicating within a service area. Embodiments herein relate generally to resource management for wireless communication networks with device-to-device capable UEs participation, such as vehicle-to-vehicle (V2V) authorized UEs or ProSe authorized UEs. Another wireless device 10' may also be present in the wireless communication network 1.

The wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area referred to as a service area 11 or cell, which service area 11 or cell may be provided by one or more beams or beam groups covering the service area of a first Radio Access Technology (RAT), such as NR, 5G, LTE, Wi-Fi, or similar. A radio network node, such as the radio network node 12, may also serve multiple cells. The radio network node 12 may be a transmission and reception point, e.g. a radio access network node, such as a Wireless Local Area Network (WLAN) access point or access point station (AP STA), an access controller, a base station (e.g. a radio base station, such as a NodeB, evolved node B (eNB, eNode B), gbnodeb), a base transceiver station, a radio remote unit, an access point base station, a base station router, a transmission arrangement of radio base stations, a stand-alone access point, or any other network unit capable of communicating with wireless devices within a service area served by the radio network node, depending on e.g. the radio access technology and terminology used. The radio network node 12 communicates with the wireless device 10 by means of Downlink (DL) transmissions to and Uplink (UL) transmissions from the wireless device 10 over a radio interface such as LTE-Uu.

The wireless communication network 1 further comprises a network node 13, such AS a VAE server, a V2X Application Server (AS), a V2X server or another application server.

The embodiments herein enable VAE clients of wireless devices, such as V2X UEs, to deliver uplink V2X messages to network nodes 13, such as V2X servers, and other wireless devices, and specify protocols and message fields. For example, a Vehicle Application Enabler (VAE) client of the wireless device 10 receives a V2X message for a service with a service ID from a V2X application specific client. The VAE client further determines a network node for receiving the uplink V2X message based on the service ID; and transmits the uplink V2X message to the determined network node together with the service ID.

Embodiments herein may disclose a process when a VAE client transmits an Uplink (UL) V2X message to the network node 13, denoted as V2X uplink message delivery.

The VAE capability may provide support for uplink V2X message delivery from V2X UEs to V2X application specific servers.

Information flow

V2X message

Table 1 describes information transmitted by a VAE client, e.g., in a wireless device 10 or 10', to a network node 13, e.g., a VAE server, in an uplink V2X message.

Table 1: uplink V2X message

Information element	Status of state	Description of the invention
			V2X UE ID	Force the	An identifier of the V2X UE, such as the StationID specified in ETSI TS 102894-2.
V2X message	Force the	V2X message payload, e.g. ETSI ITS DENM as specified in ETSI EN 302637-3
			V2X service ID	Optionally	V2X service ID, V2X UE is transmitting to V2X AS (e.g., PSID of ETSI ITS CAM, ETSI ITS DENM or ITS AID)
GEO ID	Optionally	Geographic area identifier (e.g., subscription URI, tile (tile) identifier, geo-fence tile identifier)

V2X message response

Table 2 describes the information flow of the network node 13 (such as the VAE server) in response to the uplink V2X message received from the VAE client.

Table 2: V2X message response

Information element	Status of state	Description of the invention
			Results	Optionally	Results from the VAE server in response to the V2X message indicating success or failure

Procedure for uplink V2X message delivery

The subclause describes the process of delivering a V2X message from a wireless device 10, such as a V2X UE, to a network node 13, such as a V2X application server.

Procedure

The preconditions are as follows:

1. the VAE client may have discovered the VAE server as described in subclause 9.1.2 of [1 ].

2. The VAE client may have registered with the V2X service identified by the V2X service ID, as described in subclause 9.2 in [1 ].

Fig. 4 shows a process of delivering a message from a V2X UE to a V2X application server.

401. The V2X application specific client sends a V2X message for the service with the service ID to the VAE client.

402. The VAE client determines a VAE server for receiving a V2X message having a V2X service ID.

403. The VAE client transmits the V2X message to the VAE server.

404. The VAE server provides the V2X message to the application specific server.

405. The VAE server may provide a V2X message response to the VAE client.

V2X uplink message delivery for UE-to-UE communication over LTE Uu

The VAE capability may provide support for V2X message delivery from a V2X UE to another V2X UE using LTE Uu.

Information flow

Table 3 describes information that the VAE client transmits to the VAE server in a V2X message.

Table 3: UL V2X message

Information element	Status of state	Description of the invention
			V2X UE receiver ID	Force the	An identifier of a V2X UE receiving the V2X message (e.g., StationaID specified in ETSI TS 102894-2)
V2X UE sender ID	Force the	V2X UE identifier (e.g., StationID specified in ETSI TS 102894-2)
			V2X message	Force the	V2X message payload (e.g., ETSI ITS DENM as specified in ETSI EN 302637-3)
V2X service ID	Optionally	V2X service ID, V2X UE is transmitting to V2X AS (e.g., PSID of ETSI ITS CAM, ETSI ITS DENM or ITS AID)
			GEO ID	Optionally	Geographic area identifiers (e.g., subscription URI, tile (tile) identifier, geo-fence tile identifier)）

V2X message response

Table 4 describes the information flow of the VAE server in response to the V2X message received from the VAE client.

Table 4: V2X message response

Information element	Status of state	Description of the invention
			Results	Optionally	Results from the VAE server indicating success or failure in response to the V2X message

Uplink V2X message delivery

This subclause describes the procedure for delivering a V2X message from a V2X UE to a V2X application server.

Procedure

The preconditions are as follows:

1. the VAE client may have discovered the VAE server as described in subclause 9.1.2 of [1 ].

2. The VAE client may have registered with the V2X service identified by the V2X service ID, as described in subclause 9.2 in [1 ].

3. The VAE client may have established a connection with other V2X UEs.

Fig. 5 shows a process of delivering a message from a V2X UE to a V2X application server.

501. The V2X application specific client sends a V2X message for the service with the service ID to the VAE client.

502. The VAE client determines a VAE server for receiving a V2X message having a V2X service ID.

503. The VAE client transmits the V2X message to the VAE server.

504. The VAE server provides the V2X message to the application specific server.

505. The VAE server may provide a V2X message response to the VAE client.

Upon receiving the V2X message, the V2X application specific server delivers the V2X message to the intended V2X UE.

Fig. 6 illustrates a process of delivering a message from a V2X application server to a V2X UE.

601. The V2X application specific server provides the VAE server with V2X messages for services with a service ID.

602. The VAE server delivers the V2X message to the VAE client # 2.

603. The VAE client #2 may provide a V2X message response to the VAE server.

604. VAE client #2 provides a V2X message to the application specific client.

Optimization

The uplink V2X message may be used to update the geographic area of the V2X UE at the V2X application server without explicitly requiring geographic area tracking messages.

Optimization for uplink V2X message distribution based on downlink received V2X messages. The V2X UE may refrain from sending uplink V2X messages so that only a subset of vehicles report to the V2X AS, those vehicles that have begun to receive messages do not need to deliver uplink messages.

The V2X application server may decide to deliver the received message in uplink to the V2X UE via unicast or multicast or other mode.

The V2X application server may not deliver V2X messages, e.g., outdated messages, to the V2X UE.

The V2X application server may not deliver V2X messages to all V2X UEs, e.g., V2X messages to V2X UEs that have left a group or changed geographic area.

The same or different VAE servers may be used to deliver V2X messages for other V2X UEs.

Uplink V2X messages may go to the VAE server and not be forwarded to the V2X application specific server.

Fig. 7a is a combined flow chart and signaling scheme according to some embodiments herein.

Act 701. The wireless device 10 may determine a network node for receiving a UL message, such as a V2x message, based on the service ID of the service used. The service ID may be obtained from the service used.

Act 702. The wireless device 10 then transmits a UL V2X message to or towards the network node 13 via the VAE client, wherein the UL V2X message comprises one or more of: a wireless device identification, a payload of a message (such as the location of the detected object), a service ID of the service, and a geographic identification of the location of the wireless device. Thus, the UL V2X message may include data indicative of the wireless device (such as a UE ID), and may include one or more of the following: data relating to and/or describing the service; and an indication indicating a geographic area. The UL message may include an indication of the receiving wireless device, such as a UE ID for forwarding the UL message.

Act 703. The network node 13 may then handle the UL message, e.g. process the payload and distribute it to the services, when it is received.

Act 704. The network node 13 may then respond with a response indicating success or failure upon receiving the message.

Described herein are processes and information flows for uplink V2X communications from V2X UEs to V2X application servers and to other V2X UEs using long range cellular LTE Uu. Several optimizations are also disclosed.

Method acts performed by the VAE client of the wireless device 10 for using services in a wireless communication network for a V2X wireless device according to embodiments herein will now be described with reference to the flowchart depicted in fig. 7 b. The acts are not necessarily performed in the order described below, but may be performed in any suitable order. The actions performed in some embodiments are marked with a dashed box.

Act 711. The VAE client may register with the service identified by the service ID.

Act 712. The VAE client receives a V2X message for a service with a service ID from the V2X application specific client.

Act 713. The VAE client determines the network node 13 for receiving the uplink V2X message based on the service ID. It should be noted that the network node may be a vehicle application enabler server or another server. The VAE server may be owned by a mobile network operator or a service provider (as a road authority).

Act 714. The VAE client transmits the uplink V2X message to the determined network node along with the service ID. The uplink V2x message may further include one or more of the following: a wireless device identification, a payload of a message, and a geographic identification of a location of the wireless device.

Act 715. The VAE client may receive a response from the network node indicating success or failure.

Method actions performed by the network node 13, such as a VAE server, for handling vehicle-to-everything V2X wireless device communication in a wireless communication network according to embodiments herein will now be described with reference to the flowchart depicted in fig. 7 c. The acts are not necessarily performed in the order described below, but may be performed in any suitable order. The actions performed in some embodiments are marked with a dashed box.

Act 721. The network node 13 receives an uplink V2X message with a service ID from the VAE client of the wireless device.

Act 722. The network node 13 handles the uplink V2X message taking into account the service ID. For example, when the network node is a vehicle application enabler server, the network node provides an uplink V2X message to a V2X application specific server, e.g., associated with a service ID.

The network node may further transmit a response to the VAE client indicating success or failure.

Fig. 8 is a schematic block diagram depicting a wireless device 10 having a VAE client for utilizing services in a wireless communication network for a V2X wireless device.

The wireless device 10 may include processing circuitry 801 (e.g., one or more processors) configured to perform the methods herein. The VAE client may be configured to register with the service identified by the service ID.

The wireless device 10 may comprise an obtaining unit 802, such as a receiver or transceiver. The VAE client, wireless device 10, processing circuitry 801, and/or obtaining unit 802 is configured to receive a V2X message from the V2X application-specific client for a service having a service ID. The VAE client, wireless device 10, processing circuitry 801, and/or obtaining unit 802 may be configured to obtain a UL message with a service ID. The wireless device 10 may obtain the UL message from an application/service or from another wireless device.

The wireless device 10 may comprise a determination unit 803. The VAE client, wireless device 10, processing circuitry 801, and/or determining unit 803 are configured to determine the network node 13 for receiving the UL V2X message based on the service ID.

The wireless device 10 may include a selection unit 804. The wireless device 10, the processing circuitry 801, and/or the selecting unit 804 may be configured to select the network node 13.

The wireless device 10 may include a transmitting unit 805, such as a transmitter or transceiver. The VAE client, wireless device 10, processing circuitry 801, and/or transmitting unit 805 are configured to transmit the UL V2X message with the service ID to the determined network node 13. The uplink V2x message may further include one or more of the following: a wireless device identification, a payload of a message, and a geographic identification of a location of the wireless device.

The VAE client may be configured to receive a response from the network node indicating success or failure.

The wireless device 10 also includes memory 806, the memory 806 including one or more memory units. Memory 806 comprises instructions executable by processing circuit 801 to perform the methods herein when executed in wireless device 10. The memory 806 is arranged for storing, for example, a set of information, data, such as UE ID, service ID, geo ID, network node ID, condition, location, speed, category, etc.

The method for the wireless device 10 according to embodiments described herein is implemented by means of, for example, a computer program 807 or a computer program product 807, respectively, the computer program 807 or the computer program product 807 comprising instructions, i.e. software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein as being performed by the wireless device 10. The computer program product 807 may be stored on a computer readable storage medium 808, such as a disk, a Universal Serial Bus (USB) device, or the like. The computer-readable storage medium 808 having stored thereon the computer program product 807 may comprise instructions that, when executed on at least one processor, cause the at least one processor to carry out the acts described herein as being performed by the wireless device 10. In some embodiments, the computer-readable storage medium 808 may be a transitory or non-transitory computer-readable storage medium. Thus, the wireless device 10 may comprise a processing circuit 801 and a memory 806, said memory 806 comprising instructions executable by said processing circuit 801 whereby said wireless device 10 is operable to perform the methods herein.

Fig. 9 is a schematic block diagram depicting a network node 13, the network node 13 for handling communication of a V2X wireless device in a wireless communication network (e.g., communicating with a wireless device 10 via, for example, a radio network node 12 in the wireless communication network 1). The network node may be a vehicle application enabler server or another server.

The network node 13 may comprise processing circuitry 901 (e.g., one or more processors) configured to perform the methods herein.

The network node 13 may comprise a receiving unit 902, such as a receiver or a transceiver. The network node 13, the processing circuitry 901, and/or the receiving unit 902 are configured to receive an uplink V2X message with a service ID from a VAE client of the wireless device, e.g. a UL message from the wireless device, wherein the UL message comprises at least the service ID.

The network node 13 may comprise a handling unit 903. The network node 13, the processing circuitry 901, and/or the handling unit 903 is configured to handle the uplink V2X message in view of the service ID, e.g. handle the UL V2X message based on the service ID in the UL message. The vehicle application enabler server may be configured to handle the uplink V2X message by providing the uplink V2X message to the V2X application specific server.

The network node 13 further comprises a memory 904, the memory 904 comprising one or more memory units. The memory 904 comprises instructions executable by the processing circuitry 901 to perform the methods herein when executed in the network node 13. The memory 904 is arranged for storing, for example, information, data, such as applications, service IDs, UE IDs, etc.

The method for the network node 13 according to embodiments described herein is implemented by means of, for example, a computer program 905 or a computer program product 905, respectively, the computer program 905 or the computer program product 905 comprising instructions, i.e. software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein as being performed by the network node 13. The computer program product 905 may be stored on a computer readable storage medium 906 (e.g., a disk, a USB stick, or the like). The computer-readable storage medium 906 having stored thereon the computer program product 905 may comprise instructions that, when executed on at least one processor, cause the at least one processor to carry out the actions described herein as being performed by the network node 13. In some embodiments, the computer-readable storage medium may be a transitory or non-transitory computer-readable storage medium. Thus, the network node 13 may comprise a processing circuit 901 and a memory 904, said memory 904 comprising instructions executable by said processing circuit 901, whereby said network node 13 is operable to perform the methods herein.

The components, units, or modules may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware, as will be readily understood by those familiar with communication design. In some embodiments, several or all of the various functions may be implemented together, such as in a single Application Specific Integrated Circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces therebetween. For example, several of the functions may be implemented on a processor shared with other functional components of the wireless terminal or network node.

Alternatively, several of the functional elements of the processing means in question may be provided by using dedicated hardware in association with appropriate software or firmware, while other functional elements are provided together with hardware for executing software. Thus, the term "processor" or "controller" as used herein refers not exclusively to hardware capable of executing software, and may implicitly include, without limitation, Digital Signal Processor (DSP) hardware, Read Only Memory (ROM) for storing software, random access memory for storing software and/or program or application data, and non-volatile memory. Other hardware, conventional and/or custom, may also be included. The designer of the communication receiver will appreciate the cost, performance and maintenance tradeoffs inherent in these design choices.

Referring to fig. 10, according to an embodiment, the communication system includes a telecommunications network 3210, such as a 3 GPP-type cellular network, the telecommunications network 3210 including an access network 3211 (such as a radio access network) and a core network 3214. The access network 3211 includes a plurality of base stations 3212a, 3212b, 3212c, such as NBs, enbs, gnbs or other types of wireless access points as examples of the radio network node 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213 c. Each base station 3212a, 3212b, 3212c is connectable to a core network 3214 by a wired or wireless connection 3215. A first User Equipment (UE) 3291 (as an example of a wireless device 10) located in a coverage area 3213c is configured to wirelessly connect to a corresponding base station 3212c or be paged by the corresponding base station 3212 c. A second UE 3292 in coverage area 3213a may be wirelessly connected to a corresponding base station 3212 a. Although multiple UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or where only one UE is connected to a corresponding base station 3212.

The telecommunications network 3210 itself is connected to a host computer 3230, which host computer 3230 may be embodied in hardware and/or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 3230 may be under the ownership or control of the service provider, or may be operated by or on behalf of the service provider. Connections 3221, 3222 between the telecommunications network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230 or may be via an optional intermediate network 3220. The intermediate network 3220 may be one of a public, private, or managed network or a combination of more than one of a public, private, or managed network; intermediate network 3220 (if any) may be a backbone network or the internet; in particular, the intermediate network 3220 may include two or more sub-networks (not shown).

The communication system of fig. 10 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230. Connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and connected UEs 3291, 3292 are configured to communicate data and/or signaling using the access network 3211, the core network 3214, any intermediate networks 3220, and possibly additional infrastructure (not shown) as intermediaries via the OTT connection 3250. OTT connection 3250 may be transparent in the sense that the participating communication devices through which OTT connection 3250 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 3212 may not or need not be informed of past routes of incoming downlink communications with data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 need not know the future route of outgoing uplink communications originating from the UE 3291 towards the host computer 3230.

According to an embodiment, an example implementation of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to fig. 11. In the communications system 3300, the host computer 3310 includes hardware 3315, the hardware 3315 including a communications interface 3316, the communications interface 3316 configured to set up and maintain a wired or wireless connection with the interface of the different communications devices of the communications system 3300. The host computer 3310 further includes a processing circuit 3318, which processing circuit 3318 may have storage and/or processing capabilities. In particular, the processing circuit 3318 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The host computer 3310 further includes software 3311, which software 3311 is stored in the host computer 3310 or is accessible by the host computer 3310 and executable by the processing circuit 3318. The software 3311 includes a host application 3312. The host application 3312 may be operable to provide services to a remote user, such as UE 3330, which UE 3330 connects via an OTT connection 3350 that terminates at UE 3330 and host computer 3310. In providing services to remote users, the host application 3312 may provide user data that is communicated using the OTT connection 3350.

The communication system 3300 also includes a base station 3320, which base station 3320 is provided in the telecommunications system and includes hardware 3325 that enables it to communicate with host computers 3310 and UEs 3330. The hardware 3325 may include a communications interface 3326 for setting up and maintaining wired or wireless connections to interfaces of different communication devices of the communication system 3300, and a radio interface 3327 for setting up and maintaining at least a wireless connection 3370 with a UE 3330 located in a coverage area (not shown in fig. 11) served by the base station 3320. Communication interface 3326 may be configured to facilitate connection 3360 to a host computer 3310. The connection 3360 may be direct or it may pass through the core network of the telecommunications system (not shown in fig. 11) and/or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 3325 of the base station 3320 also includes processing circuitry 3328, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 3320 further has software 3321 stored internally or accessible via an external connection.

The communication system 3300 also includes the already mentioned UE 3330. Its hardware 3335 may include a radio interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving the coverage area where the UE 3330 is currently located. The hardware 3335 of the UE 3330 also includes processing circuitry 3338, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The UE 3330 further includes software 3331, which software 3331 is stored in the UE 3330 or is accessible to the UE 3330 and executable by the processing circuitry 3338. The software 3331 includes a client application 3332. The client application 3332 may be operable to provide services to human or non-human users via the UE 3330 with the support of a host computer 3310. Within host computer 3310, executing host application 3312 may communicate with executing client application 3332 via OTT connection 3350 that terminates at UE 3330 and host computer 3310. In providing services to the user, the client application 3332 may receive request data from the host application 3312 and provide user data in response to the request data. The OTT connection 3350 may transport both request data and user data. The client application 3332 may interact with the user to generate the user data it provides.

Note that host computer 3310, base station 3320, and UE 3330 illustrated in fig. 11 may be the same as host computer 3230, one of base stations 3212a, 3212b, 3212c, and one of UEs 3291, 3292, respectively, of fig. 10. That is, the internal workings of these entities may be as shown in fig. 11, and independently, the surrounding network topology may be that of fig. 10.

In fig. 11, the OTT connection 3350 has been abstractly drawn to illustrate communication between the host computer 3310 and the user equipment 3330 via the base station 3320 without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure may determine the route, which may be configured to hide the route from UE 3330 or from the service provider operating host computer 3310, or both. While the OTT connection 3350 is active, the network infrastructure may further make decisions whereby it dynamically changes routing (e.g., based on reconfiguration of the network or load balancing considerations).

The wireless connection 3370 between the UE 3330 and the base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 3330 using an OTT connection 3350 in which the wireless connection 3370 forms the final segment in the OTT connection 3350. More precisely, the teachings of these embodiments may improve latency by having the wireless device transmit UL V2x messages, and thereby provide benefits such as reduced user latency and better responsiveness.

Measurement procedures may be provided for the purpose of monitoring one or more embodiments for improved data rate, latency, and other factors. There may further be optional network functionality for reconfiguring the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to changes in the measurement results. The measurement procedures and/or network functionality for reconfiguring the OTT connection 3350 may be implemented in the software 3311 of the host computer 3310 or in the software 3331 of the UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with the communication device through which OTT connection 3350 passes; the sensors may participate in the measurement process by supplying the values of the monitored quantities exemplified above or supplying the values of other physical quantities from which the software 3311, 3331 may calculate or estimate the monitored quantities. The reconfiguration of OTT connection 3350 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect base station 3320 and it may be unknown or imperceptible to base station 3320. Such procedures and functionality may be known and practiced in the art. In certain embodiments, the measurements may involve dedicated UE signaling that facilitates measurements of throughput, propagation time, latency, etc. of the host computer 3310. The measurements may be achieved because the software 3311, 3331 causes the OTT connection 3350 to be used to transmit messages, particularly null or "dummy" messages, as it monitors propagation time, errors, etc.

Fig. 12 is a flow diagram illustrating a method implemented in a communication system in accordance with one embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 10 and 11. To simplify the present disclosure, only figure references to fig. 12 will be included in this section. In a first step 3410 of the method, the host computer provides user data. In optional sub-step 3411 of first step 3410, the host computer provides the user data by executing a host application. In a second step 3420, the host computer initiates a transmission to the UE carrying the user data. In an optional third step 3430, the base station transmits user data carried in a host computer initiated transmission to the UE according to the teachings of embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with a host application executed by the host computer.

Fig. 13 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 10 and 11. To simplify the present disclosure, only figure references to FIG. 13 will be included in this section. In a first step 3510 of the method, a host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In a second step 3520, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of embodiments described throughout this disclosure, transmissions may be communicated via a base station. In an optional third step 3530, the UE receives user data carried in a transmission.

Fig. 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 10 and 11. To simplify the present disclosure, only figure references to FIG. 14 will be included in this section. In an optional first step 3610 of the method, the UE receives input data provided by a host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In optional sub-step 3621 of second step 3620, the UE provides user data by executing a client application. In a further optional sub-step 3611 of the first step 3610, the UE executes a client application that provides user data as a reaction to received input data provided by the host computer. The executed client application may further consider user input received from the user when providing the user data. Regardless of the particular manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in optional third sub-step 3630. In a fourth step 3640 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

Fig. 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station and a UE, which may be those described with reference to fig. 10 and 11. To simplify the present disclosure, only figure references to FIG. 15 will be included in this section. In optional first step 3710 of the method, the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In an optional second step 3720, the base station initiates transmission of the received data to the host computer. In a third step 3730, the host computer receives the user data carried in the transmission initiated by the base station.

Modifications and other embodiments of the disclosed embodiments will come to mind to one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the embodiment(s) is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the present disclosure. Although specific terms may be employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Reference documents:

[1] 3GPP TS 23.286，Application layer support for V2X services；Functional architecture and information flows，V1.1.0，04-2019。

[2] 3GPP TS 23.434，Service Enabler Architecture Layer for Verticals；Functional architecture and information flows，V1.1.0，04-2019。

abbreviations

2X AS V2X application server

VAE V2X application enabler

V2X UE user equipment

ITS intelligent transportation system

ITS-S ITS station

V2X vehicle-to-everything

Appendix

1. Introduction to the design reside in

The current TS describes the process of downlink V2X message distribution from V2X AS to V2X UEs. In several V2X applications, such as road hazard warning use cases, where vehicles send warning messages of detected hazard situations to a back-end server, the back-end server further distributes the warning messages to other vehicles via downlink communications. In this case, the V2X message needs to be delivered from the V2X UE to the V2X AS.

2. Reason for change

To specify the procedure for uplink V2X message delivery from V2X UEs to V2X AS.

3. Conclusion

< conclusion part (optional) >

4. Advising

The following changes to 3GPP TS 23.286 v1.1.0 are suggested to be agreed.

First change

9, x V2X uplink message delivery

Summary of 9.x.1

The VAE capability provides support for uplink V2X message delivery from V2X UEs to V2X application specific servers.

X.2 information flow

9. x.2.1V 2X message

Table 9.x.2.1-1 describes the information flow for the VAE client to transmit a V2X message to the VAE server.

Table 9. x.2.1-1: V2X message

Information element	Status of state	Description of the invention
			V2X UE ID	M	Identifiers of V2X UEs (e.g., ETSI TS 102894-2 [15 ]]Station ID of the statement
V2X message	M	V2X message payload (e.g., ETSI ITS DENM [ X ]]）
			V2X service ID	O	V2X service ID, V2X UE is transmitting to V2X AS (e.g., PSID of ETSI ITS CAM, ETSI ITS DENM or ITS AID)
GEO ID	O	Geographic area identifier (e.g., subscription URI, tile (tile) identifier, geo-fence tile identifier)

9. x.2.2V 2X message response

Table 9.x.2.2-1 describes the information flow of the VAE server in response to a V2X message received from the VAE client.

Table 9. x.2.2-1: V2X message response

Information element	Status of state	Description of the invention
			Results	O	Results from the VAE server in response to the V2X message indicating success or failure

X.3 uplink V2X message delivery

Summary of 9.x.3.1

This subclause describes the procedure for delivering a V2X message from a V2X UE to a V2X application server.

X.3.2 Process

The preconditions are as follows:

1. the VAE client has discovered the VAE server as described in subclause 9.1.2.

2. The VAE client has registered with the V2X service identified by the V2X service ID, as described in subclause 9.2.

FIG. 4: procedure to deliver messages from V2X UE to V2X application server.

1. The V2X application specific client sends a V2X message for the service with the service ID to the VAE client.

2. The VAE client determines a VAE server for receiving a V2X message having a V2X service ID.

3. The VAE client transmits the V2X message to the VAE server.

4. The VAE server provides the V2X message to the application specific server.

5. The VAE server may provide a V2X message response to the VAE client.

Change next

2 reference

The following documents contain the provisions that constitute the provisions specified in this document by reference in this text.

References are specific (identified by publication date, version number, etc.) or non-specific.

For a particular reference, subsequent revisions do not apply.

For non-specific references, the latest version applies. Where 3GPP documents (including GSM documents) are cited, non-specific references implicitly refer to the latest version of the document in the same version as the present document.

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications"。

[2] 3GPP TS 22.185: "Service requirements for V2X services; Stage 1"。

[3] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1"。

[4] 3GPP TS 23.280: "Common functional architecture to support mission critical services"。

[5] 3GPP TS 23.285: "Architecture enhancements for V2X services"。

[6] 3GPP TS 23.434: "Service enabler architecture layer for verticals; Functional architecture and information flows; Stage 2"。

[7] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); Stage 2"。

[8] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications"。

[9] 3GPP TR 23.795: "Study on application layer support for V2X services"。

[10] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs"。

[11] 3GPP TS 26.348: "Northbound Application Programming Interface (API) for Multimedia Broadcast/Multicast Service (MBMS) at the xMB reference point"。

[12] 3GPP TS 29.214: "Policy and Charging Control over Rx reference point"。

[13] 3GPP TS 29.468: "Group Communication System Enablers for LTE (GCSE_LTE); MB2 Reference Point; Stage 3"。

[14] 3GPP TS 36.300: " Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2"。

[15] ETSI TS 102 894-2 (V1.2.1): "Intelligent Transport Systems (ITS); Users and applications requirements; Part 2: Applications and facilities layer common data dictionaryMultimedia Broadcast/Multicast Service (MBMS); Protocols and codecs"。

[16] ETSI TS 102 965 (V1.4.1): "Intelligent Transport Systems (ITS); Application Object Identifier (ITS-AID); Registration"。

[17] ISO TS 17419: "Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context"。

[X] ETSI - EN 302 637-3 (V1.3.0): " Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification Basic Service"。

1. Introduction to the design reside in

This document proposes a pCR for the architecture requirements to include VAE capability support for uplink V2X message distribution.

In several V2X applications, such as road hazard warning use cases, where vehicles send warning messages of detected hazard situations to a back-end server, the back-end server further distributes the warning messages to other vehicles via downlink communications. In this case, the V2X message needs to be delivered from the V2X UE to the V2X AS.

2. Reason for change

VAE capability should support the delivery of V2X messages from V2X UEs to V2X applications.

3. Conclusion

< conclusion part (optional) >

4. Advising

The following changes to 3GPP TS 23.286 v1.1.0 are suggested to be agreed upon.

First change

4.5V 2X application message distribution

4.5.1 description

This subclause specifies the V2X (e.g., ETSI ITS, SAE) message distribution requirements.

4.5.2 requirements

The [ AR-4.5.2-a ] VAE server should provide a mechanism for distributing the V2X message to all registered receivers in the target geographical area.

The [ AR-4.5.2-b ] VAE server should be able to enable the delivery of several V2X messages on the same connection.

[ AR-4.5.2-c ] VAE clients should have the ability to register with V2X messages within one or more geographic regions.

The [ AR-4.5.2-d ] VAE server should be able to forward the V2X message only to authorized V2X UEs in the target geographic area.

The [ AR-4.5.2-e ] VAE server should provide a mechanism for priority support for different V2X messages (e.g., security messages).

[ AR-4.5.2-f ] VAE capability should support the delivery of V2X messages from V2X UEs to V2X applications.