NETWORK NODE, VEHICLE-TO-EVERYTHING APPLICATION ENABLER CLIENT, AND METHODS EMBODIED IN THE NETWORK NODE AND VEHICLE-TO-EVERYTHING APPLICATION ENABLER CLIENT - Patent application

Abstract

To provide a method of using services in a wireless communication network for a vehicle-to-anything (V2X) wireless device and a vehicle-to-everything application enabler (VAE) client.SOLUTION: In order to use a service in a wireless communication network for a V2X wireless device, a VAE client receives a V2X message for a service with a service ID from a V2X application-specific client, determines a network node for receiving an uplink V2X message on the basis of the service ID, and sends the uplink V2X message to the determined network node having the service ID.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] The embodiments herein relate to a network node, a vehicle to everything application enabler (VAE) client of a wireless device, and a method implemented in the network node, the VAE client of the wireless device. Further, a computer program product and a computer readable storage medium are also provided herein. In particular, the embodiments herein relate to enabling communication of vehicle to everything (V2X) wireless devices in a wireless communication network. [Background technology]

[0002] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STAs), vehicles and / or user equipment (UE), communicate through a radio access network (RAN) to one or more core networks (CNs). The RAN covers a geographic area and provides radio coverage over service areas or cells, sometimes referred to as beams or beam groups, with each service area or beam being 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 be denoted as a Node B, eNode B or gNode B. The radio network node communicates with wireless devices within range of the radio network node over an air interface operating on radio frequencies.

[0003] Universal Mobile Telecommunications network (UMTS) is a third generation (3G) telecommunications network that evolved from the second generation (2G) Global System for Mobile Communications (GSM). The 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 (3GPP), telecommunications suppliers propose and agree on standards for third generation networks and study improved data rates and radio capacity. In some RANs, as in the case of UMTS, some radio network nodes may be connected, for example, by landlines or microwaves, to a controller node, such as a radio network controller (RNC) or base station controller (BSC), which monitors and coordinates various activities of multiple radio network nodes connected to the controller node. This type of connection may be referred to as a backhaul connection. The RNCs and BSCs are generally connected to one or more core networks.

[0004] Specifications for the Evolved Packet System (EPS), also referred to as the fourth generation (4G) network, have been finalized within the Third Generation Partnership Project (3GPP), and this work will continue, for example, in upcoming 3GPP releases to specify the fifth generation (5G) network. The EPS comprises an Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long Term Evolution (LTE) radio access network, and an Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) core network. The E-UTRAN / LTE is a variant of the 3GPP radio access network in which the radio network nodes are connected directly to the EPC core network rather than to the RNC. In general, in the E-UTRAN / LTE, the functions of the RNC are distributed between the radio network nodes, e.g., eNodeB in LTE, and the core network. Thus, the RAN of the EPS has an essentially "flat" architecture with the radio network nodes connected directly to one or more core networks, i.e., the radio network nodes are not connected to the RNC. To compensate for that, the E-UTRAN specifications define a direct interface between radio network nodes, this interface being denoted as the X2 interface.

[0005] For the 5G system currently being standardized by 3GPP, in which the radio access network is called New Radio (NR) and the core network is called Next Generation Core (NGC), 3GPP has agreed to partially change the principles for the distribution of system information (SI) used in LTE.

[0006] During Release 12, the LTE standard was extended with support for device-to-device (D2D) features designated as "sidelink" targeting both commercial and public safety applications. Some applications enabled by Rel-12 LTE are device discovery, where a wireless device can sense the proximity of another wireless device and associated applications by broadcasting and detecting discovery messages carrying wireless device identity and application identity information. Another application consists of direct communication based on physical channels terminating directly between wireless devices. In 3GPP, all of these applications are specified under an umbrella denoted as Proximity Services (ProSe).

[0007] One of the potential extensions of the ProSe framework consists of supporting vehicle-to-everything communication, including any combination of direct communication between vehicles, pedestrians, and infrastructure. V2x communication may utilize network (NW) infrastructure when available, but at least basic V2x connectivity should be possible even in the case of lack of coverage. Providing an LTE-based V2x interface may be economically advantageous due to LTE's economies of scale, which may enable tighter integration between communication with the NW infrastructure, e.g., vehicle-to-infrastructure and vehicle-to-pedestrian and vehicle-to-vehicle communications, compared to using dedicated V2x technologies.

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

[0009] V2x communications may carry both non-safety and safety information, where each application and service may be associated with a particular set of requirements, e.g., with regard to latency, reliability, capacity, etc. From an application perspective, V2X includes the following types of communications / services, as shown in relation to FIG.

[0010] Vehicle-to-Vehicle (V2V): It covers communication between vehicles using V2V applications and is mainly broadcast-based. V2V can be realized either by direct communication between devices in the respective vehicles or through infrastructure such as cellular networks. One example of V2V is the transmission of cooperative awareness messages with vehicle status information (such as position, direction, and speed), which are repeatedly transmitted, for example, every 100ms to 1s, to other vehicles in the vicinity. Another example is the transmission of distributed environmental notification messages, which are event-triggered messages to alert vehicles. These two examples are taken from the ETSI Intelligent Transport Systems specification for V2X applications, which also specifies the conditions under which messages are generated. A key characteristic of V2V applications is the stringent requirement on latency, which can vary from 20ms (for pre-collision warning messages) to 100ms for other road safety services.

[0011] Vehicle-to-Infrastructure (V2I): This includes communication between vehicles and roadside units. RSUs can be fixed transportation infrastructure entities that communicate with vehicles in close proximity to the RSU. An example of V2I is the transmission of speed notifications from an RSU to vehicles, as well as queue information, collision risk alerts, and curve speed warnings. Due to the safety-related nature of V2I, the latency requirements are similar to those of V2V.

[0012] Vehicle-to-Pedestrian (V2P): It covers communication between vehicles and vulnerable road users such as pedestrians, using V2P applications. V2P is generally between separate vehicles and pedestrians, either directly or via infrastructure such as a cellular network.

[0013] Vehicle-to-Network (V2N):This covers communication between vehicles and a centralized application server (or Intelligent transportation systems (ITS) traffic management center), both utilizing V2N applications over an infrastructure (such as a cellular network). An example is bad road condition warnings sent to all vehicles in a wide area, or traffic flow optimization, where the V2N application suggests speeds to vehicles and adjusts traffic signals. It is therefore conceivable that V2N messages can be controlled by a centralized entity, such as a traffic management center, and provisioned to vehicles in large geographical areas rather than in small areas. Furthermore, unlike V2V / V2I, V2N has more relaxed latency requirements, e.g., 1 second latency requirements are generally considered, as it is not intended to be used for non-safety purposes.

[0014] As mentioned above, sidelink transmissions (also known as D2D or ProSe) on the so-called PC5 interface in the cellular spectrum have been standardized in 3GPP since Rel-12. In 3GPP Rel-12, two different transmission modes were specified in 3GPP. In one mode (Mode 1), a UE in RRC_CONNECTED mode requests D2D resources and the eNB grants them via the Physical Downlink Control Channel (PDCCH) indicated as DCI5 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 grants via System Information Block (SIB) signaling for transmissions on carriers other than the PCell in broadcast or via dedicated signaling for transmissions on the primary cell (PCell). Thus, unlike the first operating mode, the second operating mode can be implemented by UEs in RRC_IDLE and in some cases even by UEs out of coverage.

[0015] In Rel.14, the use of sidelink is extended to the V2x domain. The original design of the sidelink physical layer in Rel.12 targeted 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 assumed low wireless device mobility. On the other hand, in V2x, the sidelink should be able to address higher load scenarios, i.e., potentially hundreds of cars competing for physical resources and high wireless device mobility, to carry time / event-triggered V2x messages, e.g., Cooperative Awareness Messages (CAM) and Distributed Environmental Notification Messages (DENM). For such reasons, 3GPP is discussing possible enhancements to the sidelink physical layer.

[0016] This disclosure deals with V2X communication from an Intelligent Transportation System (ITS) and a V2X application server and a V2X application client to wireless devices, referred to as V2X wireless devices, using V2X group communication over long-range cellular unicast communication via interface LTE Uu.

[0017] ITS messages are designed to enable ITS applications to improve safety and traffic efficiency of road transportation systems. In some V2X applications, e.g., teleoperation, fleet management, group communication is required for V2X communication from a V2X application server to V2X radio devices. The group management service provides V2X Application Enabler (VAE) support for communication from a V2X radio device or a V2X application server to a group of V2X radio devices to support V2X services, e.g., platooning groups, teleoperation of automated vehicles, etc.

[0018] 3GPP TS23.386[1] specifies the V2X application layer model for V2X communication over PC5 and LTE-Uu. The model is shown in Figure 2. The V2X Application Enabler (VAE) layer provides supporting information to the V2X application.

[0019] V2X UE1 communicates with the V2X application server via the V1 reference point. V2X UE1 and V2X UE2 communicate via the V5 reference point. V2X UE1 can also act as a UE-to-network relay to allow V2X UE2 to access the V2X application server via the V1 reference point.

[0020] The V2X application layer functional entities for the V2X radio device and the V2X application server are grouped into a V2X application specific layer and a VAE layer. The VAE layer provides VAE capabilities to the V2X application specific layer. The V2X application layer functional model utilizes the SEAL service as specified in 3GPP TS 23.434 [2].

[0021] The VAE server resides 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 functions.

[0022] The V2X application server includes a VAE server, a SEAL server, and a V2X application-specific server. The VAE server provides V2X application layer support functions to the V2X application-specific server via the Vs reference point.

[0023] The V2X UE comprises a VAE client, a SEAL client, and a V2X application-specific client. The VAE client provides V2X application layer support functions to the V2X application-specific client via the Vc reference point.

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

[0025] As specified in 3GPP TS 23.434 [2], the VAE client can act as a VAL client for the VAE client to interact with a SEAL client. As specified in 3GPP TS 23.434 [2], the VAE server can act as a vertical application layer (VAL) server for the VAE server to interact with a Service Enabler Architecture Layer for Verticals (SEAL) server.

[0026] At the VAE layer, the VAE client communicates with the VAE server via the V1-AE reference point. At the V2X application-specific layer, the V2X application-specific client communicates with the V2X application-specific server via the V1-APP reference point.

[0027] At the VAE layer, the VAE client of V2X UE2 communicates with the VAE client of V2X UE1 via the V5-AE reference point. At the V2X application-specific layer, the V2X application-specific client of V2X UE2 communicates with the VAE client of V2X UE1 via the V5-APP reference point.

[0028] The following SEAL services for V2X applications are supported: - 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].

[0029] VAE clients interact with SEAL clients through a SEAL-C reference point designated for each SEAL service. VAE servers interact with SEAL servers through a SEAL-S reference point designated for each SEAL service. Interaction between SEAL clients is supported by a SEAL-PC5 reference point designated for each SEAL service. Interaction between SEAL clients and corresponding SEAL servers is supported by a SEAL-UU reference point designated for each SEAL service.

[0030] The SEAL-C, SEAL-S, SEAL-PC5, and SEAL-Uu reference points for each SEAL service are specified in 3GPP TS 23.434[2].

[0031] To support distributed VAE server deployment, a VAE server interacts with other VAE servers via a VAE-E reference point.

[0032] V2X UE1 is - enabling a VAE client on the V2X UE2 to access a VAE server via a V1-AE reference point; and enabling a V2X application specific client on the V2X UE2 to access a V2X application specific server via the V1-APP reference point; The UE may similarly function as a UE-to-network relay for

[0033] V1-AE messages can be sent over unicast, transparent multicast over xMB, transparent multicast over MB2. Non-transparent multicast over xMB is triggered by V1-AE messages. Multicast delivery can be supported in both transparent and non-transparent multicast modes.

[0034] The VAE server interacts with the 3GPP network system via the V2, MB2, xMB, Rx, and T8 reference points. The EPS is considered as a 3GPP network system. Summary of the Invention

[0035] The current technical specification [1] only includes downlink V2X distribution procedures. Uplink V2X distribution information flows and procedures are not specified.

[0036] An objective of the embodiments herein is to provide a mechanism for efficiently improving the performance of wireless communication networks for vehicle-to-everything communications.

[0037] According to one aspect, the object is achieved by providing a method implemented by a network node for managing or handling communications of a wireless device in a V2X wireless communication network, the network node receiving an uplink V2x message with a service ID from a VAE client of the wireless device, the network node then handling the UL V2X message taking the service ID into account.

[0038] According to another aspect, the object is achieved by providing a method for a V2X wireless device, implemented by a VAE client of the wireless device, for using a service in a wireless communication network. The VAE client receives a V2X message of a service having a service ID from a V2X application specific client. The VAE client determines a network node for receiving an uplink V2X message based on the service ID, and transmits the uplink V2X message to the determined network node having 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 having the service ID.

[0039] According to yet another aspect, the object is achieved by providing a V2X wireless device with a wireless device VAE client for using a service in a wireless communication network. The VAE client is configured to receive a V2X message of a service having a service ID from a V2X application specific client. The VAE client further determines a network node for receiving an uplink V2X message based on the service ID, and transmits the uplink V2X message to the determined network node having the service ID.

[0040] According to yet another 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 being configured to receive, from a VAE client of the wireless device, an uplink V2X message having a service ID and to handle the uplink V2X message taking the service ID into account.

[0041] Further provided herein is a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the above methods, performed by a VAE client or a network node, respectively. Further provided herein is a computer-readable storage medium having stored thereon a computer program product comprising instructions that, when executed on at least one processor, cause the at least one processor to perform any of the above methods, performed by a VAE client or a network node, respectively.

[0042] The embodiments herein describe procedures and information flows for uplink V2X message delivery from a V2X UE to a network node and a V2X application server, e.g., over an air interface LTE Uu. Additionally, procedures and information flows for V2X UE to V2X UE over LTE Uu are also defined. Additionally, optimization of uplink V2X message delivery is provided herein.

[0043] The embodiments herein enable a VAE client of a wireless device, such as a V2X UE, to deliver uplink V2X messages to network nodes, such as servers, V2X ASs, and other wireless devices, and specify protocols and message fields, which will improve the performance of a wireless communication network.

[0044] Embodiments will now be described in more detail with reference to the enclosed drawings. [Brief description of the drawings]

[0045] [Figure 1] FIG. 2 is a logical overview of vehicle communications. [Diagram 2] FIG. 1 is a schematic block diagram illustrating vehicle communications. [Diagram 3] 1 is a schematic diagram illustrating a wireless communication network according to an embodiment herein. [Figure 4] FIG. 2 is a combined flow chart and signaling scheme diagram according to some embodiments herein. [Diagram 5] FIG. 2 is a combined flow chart and signaling scheme diagram according to some embodiments herein. [Figure 6] FIG. 2 is a combined flow chart and signaling scheme diagram according to some embodiments herein. [Figure 7a] FIG. 2 is a combined flow chart and signaling scheme diagram according to some embodiments herein. [Figure 7b] 1 is a flowchart illustrating a method performed by a VAE client according to some embodiments of the present disclosure. [Figure 7c] 1 is a flowchart illustrating a method performed by a network node, according to some embodiments of the present disclosure. [Figure 8] 1 is a schematic block diagram illustrating a wireless device having a VAE client according to an embodiment of the present disclosure. [Figure 9] FIG. 2 is a schematic block diagram representing a network node according to embodiments herein. [Figure 10] FIG. 1 illustrates a schematic diagram of a communications network connected to a host computer via an intermediate network. [Figure 11] FIG. 2 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection. [Figure 12] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 13] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 14] 1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. [Figure 15]1 is a flow chart illustrating a method implemented in a communications system including a host computer, a base station, and user equipment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0046] The embodiments herein generally relate to wireless communication networks. Figure 3 is an overview of a wireless communication network 1. The wireless communication network 1 comprises one or more RANs and one or more core networks (CNs). The wireless communication network 1 may use one or several different technologies, such as New Radio (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 name just a few possible implementations. Although the embodiments herein relate to recent technology trends of particular interest in the 5G context, the embodiments are also applicable in the further evolution of existing wireless communication networks, e.g. WCDMA and LTE.

[0047] In the wireless communication network 1, wireless devices 10, referred to herein as V2X UEs with VAE clients, such as mobile stations, non-access point (non-AP) STAs, STAs, user equipment and / or wireless terminals, may communicate to one or more core networks (CNs) via one or more access networks (ANs), such as RANs. It should be understood by those skilled in the art that "wireless devices" is a non-limiting term meaning any terminal, wireless communication terminal, user equipment, Internet of Things (IoT) enabled device, machine type communication (MTC) device, device-to-device (D2D) terminal, or node, such as a smartphone, laptop computer, mobile phone, sensor, relay, mobile tablet, or even a small base station, communicating within a service area. The embodiments herein generally relate to resource management of wireless communication networks with the participation of device-to-device enabled UEs, such as vehicle-to-vehicle (V2V) certified UEs or ProSe certified UEs. Another wireless device 10' may also be present in the wireless communication network 1.

[0048] The wireless communication network 1 comprises a radio network node 12 providing radio coverage over a geographical area, called a service area 11 or cell, which may be provided by one or more beams, or beam groups, a group of beams covering a service area of ​​a first radio access technology (RAT), such as NR, 5G, LTE, Wi-Fi, or the like. Also, a radio network node, such as the radio network node 12, may serve multiple cells. The radio network node 12 may be a transmitting and receiving 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 Node B, an evolved Node B (eNB, eNodeB), a gNodeB, a base transceiver station, a radio remote unit, an access point base station, a base station router, a transmitting configuration of a radio base station, a standalone access point, or any other network unit capable of communicating with wireless devices within a service area served by the radio network node, e.g. depending on the radio access technology and terminology used. The radio network node 12 communicates with the wireless device 10 via downlink (DL) transmissions to and uplink (UL) transmissions from the wireless device 10 over an air interface, such as LTE-Uu.

[0049] 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.

[0050] The embodiments herein enable a VAE client of a wireless device, such as a V2X UE, 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 having 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 having the service ID.

[0051] Embodiments herein may disclose a procedure when a VAE client sends an uplink (UL) V2X message, indicated as V2X uplink message delivery, to a network node 13.

[0052] The VAE capabilities may provide support for uplink V2X message delivery from the V2X UE to a V2X application specific server.

[0053] Information Flow V2X Message Table 1 describes information for a VAE client, for example in a wireless device 10 or 10', for transmitting in an uplink V2X message to a network node 13, for example a VAE server. TIFF0007636475000001.tif104170

[0054] V2X Message Response Table 2 describes the information flow for a network node 13, such as a VAE server, in response to an uplink V2X message received from a VAE client. TIFF0007636475000002.tif35170

[0055] Procedures for Uplink V2X Message Delivery This subclause describes a procedure for delivering V2X messages from a wireless device 10, such as a V2X UE, to a network node 13, such as a V2X application server.

[0056] procedure Prerequisites 1. The VAE client may have already discovered the VAE server, as described in subclause 9.1.2 of [1]. 2. As described in subclause 9.2 of [1], the VAE client may have already registered for a V2X service identified by a V2X service ID.

[0057] FIG. 4 shows a procedure for delivering a message from a V2X UE to a V2X application server.

[0058] 401. The V2X application specific client sends a V2X message for a service having a service ID to the VAE client.

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

[0060] 403. The VAE client sends a V2X message to the VAE server.

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

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

[0063] V2X Uplink Message Delivery for UE to UE Communication via LTE Uu The VAE capability may provide support for V2X message delivery from a V2X UE to another V2X UE using LTE Uu.

[0064] Information Flow Table 3 describes the information for the VAE client to send to the VAE server in a V2X message. TIFF0007636475000003.tif88170

[0065] V2X Message Response Table 4 describes the information flow for the VAE server in response to a V2X message received from a VAE client. TIFF0007636475000004.tif37170

[0066] Uplink V2X Message Delivery This subclause describes a procedure for delivering V2X messages from a V2X UE to a V2X application server.

[0067] procedure Prerequisites 1. The VAE client may have already discovered the VAE server, as described in subclause 9.1.2 of [1]. 2. As described in subclause 9.2 of [1], the VAE client may have already registered for a V2X service identified by a V2X service ID. 3. The VAE client may already have established connections with other V2X UEs.

[0068] FIG. 5 shows a procedure for delivering a message from a V2X UE to a V2X application server.

[0069] 501. The V2X application specific client sends a V2X message for a service having a service ID to the VAE client.

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

[0071] 503. The VAE client sends a V2X message to the VAE server.

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

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

[0074] After receiving the V2X message, the V2X application specific server delivers the V2X message to the intended V2X UE.

[0075] FIG. 6 shows a procedure for delivering a message from a V2X application server to a V2X UE.

[0076] 601. The V2X application specific server provides a V2X message for a service having a service ID to the VAE server.

[0077] 602. The VAE server distributes the V2X message to VAE client #2.

[0078] 603. VAE client #2 may provide a V2X message response to the VAE server.

[0079] 604. VAE client #2 provides V2X messages to application-specific clients.

[0080] optimization Uplink V2X messages can be used to update the geographical area of ​​the V2X UE at the V2X application server without the explicit need for geographical area tracking messages. Optimization for uplink V2X message delivery based on downlink received V2X messages: V2X UEs may refrain from sending uplink V2X messages so that only a portion of the vehicles report to the V2X AS and vehicles that have already started receiving messages do not need to deliver uplink messages. The V2X application server may decide to deliver messages received in the uplink to the V2X UEs via unicast or multicast or other modes. The V2X application server does not need to deliver V2X messages, e.g. legacy messages, to the V2X UE. The V2X application server does not have to distribute V2X messages to all V2X UEs, e.g. V2X UEs that have left the group or changed geographical area. The same or a different VAE server may be used to deliver V2X messages for other V2X UEs. Uplink V2X messages can proceed to the VAE server without being forwarded to a V2X application specific server.

[0081] FIG. 7a is a combined flow chart and signaling scheme according to some embodiments herein.

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

[0083] Action 702. The wireless device 10 then transmits a UL V2X message to or towards the network node 13 via the VAE client, the UL V2X message including one or more of a wireless device identification, a payload of the message such as a location of a detected object, a service ID of the service, and a geographical 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 data relating to and / or describing the service, and an indication of a geographical area. The UL message may include an indication for a receiving wireless device such as a UE ID for forwarding the UL message.

[0084] Action 703. The network node 13 may then handle the UL message upon receipt thereof, for example processing the payload and delivering it to the service.

[0085] Action 704. The network node 13 may then respond upon receipt of the message with a response indicating success or failure.

[0086] Procedures and information flows for uplink V2X communication from a V2X UE to a V2X application server and other V2X UEs using long range cellular LTE Uu are described herein. Several optimizations are also disclosed.

[0087] Method actions performed by a VAE client of a wireless device 10 to use 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 Figure 7b. The actions do not have to be taken in the order described below, but may be taken in any suitable order. Actions that are performed in some embodiments are marked with dotted boxes.

[0088] Action 711. The VAE client may register with the service identified by the service ID.

[0089] Action 712. The VAE client receives a V2X message for a service having a service ID from a V2X application specific client.

[0090] Action 713. The VAE client determines a network node 13 for receiving the uplink V2X message based on the service ID. Note that the network node may be a vehicle application enabler server or another server. The VAE server may be owned by a service provider such as a mobile network operator or a road authority.

[0091] Action 714. The VAE client sends an uplink V2X message to the determined network node having the service ID. The uplink V2X message may further include one or more of a wireless device identification, a message payload, and a geographic identification of the location of the wireless device.

[0092] Action 715. The VAE client may receive a response from the network node indicating success or failure.

[0093] Method actions performed by a network node 13, such as a VAE server, for handling communication of vehicle to anything (V2X) wireless devices in a wireless communication network according to embodiments herein will now be described with reference to the flowchart depicted in Figure 7c. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions that are performed in some embodiments are marked with dotted boxes.

[0094] Action 721. The network node 13 receives an uplink V2X message having a service ID from a VAE client of a wireless device.

[0095] Action 722. The network node 13 handles the uplink V2X message taking into account the service ID, e.g. when the network node is a vehicle application enabler server, it provides the uplink V2X message to a V2X application specific server associated with the service ID, e.g.

[0096] The network node may further send a response to the VAE client indicating success or failure.

[0097] FIG. 8 is a schematic block diagram illustrating a wireless device 10 equipped with a VAE client for using services in a wireless communication network for a V2X wireless device.

[0098] The wireless device 10 may comprise a processing circuit element 801, e.g., one or more processors, configured to perform the methods herein. The VAE client may be configured to register with a service identified by a service ID.

[0099] The wireless device 10 may include an acquisition unit 802, such as a receiver or transceiver. The VAE client, the wireless device 10, the processing circuit 801, and / or the acquisition unit 802 are configured to receive a V2X message of a service having a service ID from a V2X application specific client. The VAE client, the wireless device 10, the processing circuit 801, and / or the acquisition unit 802 may be configured to acquire a UL message having a service ID. The wireless device 10 may acquire the UL message from an application / service or from another wireless device.

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

[0101] The wireless device 10 may comprise a selection unit 804. The wireless device 10, the processing circuit 801, and / or the selection unit 804 may be configured to select a network node 13.

[0102] The wireless device 10 may comprise a transmitting unit 805, such as, for example, a transmitter or transceiver. The VAE client, the wireless device 10, the processing circuit 801, and / or the transmitting unit 805 are configured to transmit a UL V2X message to the determined network node 13 having the service ID. The uplink V2x message may further include one or more of a wireless device identification, a message payload, and a geographic identification of the location of the wireless device.

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

[0104] The wireless device 10 further comprises a memory 806, which comprises one or more memory units. The memory 806 comprises instructions executable by the processing circuitry 801 to perform methods herein when executed in the wireless device 10. The memory 806 is arranged to be used to store, for example, information, data (such as UE ID, service ID, geo ID, network node ID, status, location, speed, category, etc.).

[0105] The methods according to the embodiments described herein for the wireless device 10 may be implemented by means of, for example, a computer program 807 or computer program product 807, respectively, comprising instructions, i.e., software code portions, that when executed on at least one processor cause the at least one processor to perform actions described herein as performed by the wireless device 10. The computer program product 807 may be stored on a computer readable storage medium 808, for example, 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 perform actions described herein as 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 element 801 and a memory 806, the memory 806 comprising instructions executable by the processing circuit element 801, such that the wireless device 10 is operable to perform the methods herein.

[0106] 9 is a schematic block diagram representing a network node 13 for handling communication of a V2X wireless device in a wireless communication network, which communicates with, for example, a wireless device 10, for example via a radio network node 12 in the wireless communication network 1. The network node may be a vehicle application enabler server or another server.

[0107] The network node 13 may comprise processing circuitry 901, for example one or more processors, configured to perform the methods herein.

[0108] The network node 13 may comprise a receiving unit 902, e.g. a receiver or transceiver. The network node 13, the processing circuit 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. receiving a UL message from the wireless device, the UL message including at least the service ID.

[0109] The network node 13 may comprise a handling unit 903. The network node 13, the processing circuit 901, and / or the handling unit 903 are configured to handle the uplink V2X message taking into account the service ID, e.g., handling 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 a V2X application specific server.

[0110] The network node 13 further comprises a memory 904, comprising one or more memory units. The memory 904 comprises instructions executable by the processing circuit element 901 to perform methods herein when executed at the network node 13. The memory 904 is arranged to be used to store, for example, information, data (such as applications, service IDs, UE IDs, etc.).

[0111] The methods according to the embodiments described herein for the network node 13 are implemented by means of, for example, a computer program 905 or computer program product 905, comprising instructions, i.e. software code portions, that, when executed on at least one processor, cause the at least one processor to perform the actions described herein to be performed by the network node 13, respectively. The computer program product 905 may be stored on a computer readable storage medium 906, for example a disk, a USB stick, or the like. The computer readable storage medium 906 storing the computer program product 905 may comprise instructions, that, when executed on at least one processor, cause the at least one processor to perform the actions described herein to be 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 element 901 and a memory 904, said memory 904 comprising instructions executable by said processing circuit element 901, whereby said network node 13 is operable to perform the methods described herein.

[0112] As will be readily understood by those familiar with communications design, the means, units, or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, some 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 between them. Some of the functions may be implemented, for example, on a processor shared with other functional components of a wireless terminal or network node.

[0113] Alternatively, some of the functional elements of the described processing means may be provided through the use of dedicated hardware, while other functional elements are provided with hardware for executing software, in association with appropriate software or firmware. Thus, the terms "processor" or "controller" as used herein do not refer exclusively to hardware capable of executing software, but may implicitly include, but are not limited to, 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. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0114] 10, according to one embodiment, a communication system includes a communication network 3210, such as a 3GPP type cellular network, comprising an access network 3211, such as a radio access network, and a core network 3214. The access network 3211 comprises a number of base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs, or other types of wireless access points, which are examples of radio network nodes 12 herein, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c can be connected to the core network 3214 over a wired or wireless connection 3215. A first user equipment (UE) 3291, which is an example of a wireless device 10, located in the coverage area 3213c, is configured to wirelessly connect to or be paged by the corresponding base station 3212c. A second UE 3292 in the coverage area 3213a can wirelessly connect to the corresponding base station 3212a. Although multiple UEs 3291, 3292 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or connects to the corresponding base station 3212.

[0115] The communication network 3210 is connected to a host computer 3230, which may itself 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 owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connection 3221, 3222 between the communication network 3210 and the host computer 3230 may extend directly from the core network 3214 to the host computer 3230, or may proceed through an optional intermediate network 3220. The intermediate network 3220 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and the intermediate network 3220 may be a backbone network or the Internet, if any, and in particular the intermediate network 3220 may comprise two or more sub-networks (not shown).

[0116] The communication system of FIG. 10 as a whole enables connectivity between one of the connected UEs 3291, 3292 and the host computer 3230. The connectivity may be described as an over-the-top (OTT) connection 3250. The host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and / or signaling via the OTT connection 3250 using the access network 3211, the core network 3214, any intermediate network 3220, and possible further infrastructure (not shown) as intermediaries. The OTT connection 3250 may be transparent in the sense that the involved communication devices through which the OTT connection 3250 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 3212 may not be or need not be informed regarding the past routing of an incoming downlink communication involving data originating from the host computer 3230 to be forwarded (e.g., handed over) to the connected UE 3291. Similarly, the base station 3212 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 3291 and destined for the host computer 3230.

[0117] Now, with reference to FIG. 11, an exemplary implementation of the UE, base station and host computer described in the previous paragraph according to an embodiment will be described. In the communication system 3300, the host computer 3310 comprises hardware 3315 including a communication interface 3316 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 3300. The host computer 3310 further comprises processing circuitry 3318, which may have storage and / or processing capabilities. In particular, the processing circuitry 3318 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof adapted to execute instructions (not shown). The host computer 3310 further comprises software 3311, which is stored in or accessible by the host computer 3310 and is executable by the processing circuitry 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 a UE 3330 connecting via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing services to a remote user, the host application 3312 may provide user data that is transmitted using the OTT connection 3350.

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

[0119] The communication system 3300 further includes the already mentioned UE 3330. Its hardware 3335 may include a wireless interface 3337 configured to set up and maintain a wireless connection 3370 with a base station serving the coverage area in which the UE 3330 is currently located. The hardware 3335 of the UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof adapted to execute instructions (not shown). The UE 3330 further includes software 3331 stored in or accessible by 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 a human or non-human user via the UE 3330 with the support of the host computer 3310. At the host computer 3310, a running host application 3312 may communicate with a running client application 3332 via an OTT connection 3350 that terminates at the UE 3330 and the host computer 3310. In providing services to a 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 transfer both the request data and the user data. The client application 3332 may interact with the user to generate the user data that the client application 3332 provides.

[0120] It should be noted that the host computer 3310, base station 3320 and UE 3330 shown in Figure 11 may be equivalent to the host computer 3230, one of the base stations 3212a, 3212b, 3212c and one of the UEs 3291, 3292, respectively, of Figure 10. That is, the inner workings of these entities may be as shown in Figure 11 and, separately, the surrounding network topology may be that of Figure 10.

[0121] 11, the OTT connection 3350 is depicted abstractly, without explicit reference to intermediate devices and the exact routing of messages through these devices, to show communication between the host computer 3310 and the user equipment 3330 via the base station 3320. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 3330 or from the service provider operating the host computer 3310, or both. The network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network) while the OTT connection 3350 is active.

[0122] The wireless connection 3370 between the UE 3330 and the base station 3320 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 3330 using the OTT connection 3350 of which the wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments improve latency by allowing the wireless device to transmit UL V2x messages, which may result in benefits such as reduced user waiting time and better responsiveness.

[0123] Measurement procedures may be provided for the purpose of monitoring data rates, latency and other factors that one or more embodiments improve upon. There may further be optional network functionality to reconfigure the OTT connection 3350 between the host computer 3310 and the UE 3330 in response to variations in the measurement results. The measurement procedures and / or the network functionality to reconfigure 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 an embodiment, sensors (not shown) may be deployed in or in association with the communication devices through which the OTT connection 3350 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software 3311, 3331 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 3350 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 3320, and the reconfiguration may be unknown or imperceptible to the base station 3320. Such procedures and functionality may be known and implemented in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 3310 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in the software 3311, 3331 causing messages, particularly empty or "dummy" messages, to be sent using the OTT connection 3350 while the software 3311, 3331 monitors propagation times, errors, etc.

[0124] FIG. 12 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 as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 12 are included in this section. In a first step 3410 of the method, the host computer provides user data. In an optional sub-step 3411 of the 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 carrying the user data to the UE. In an optional third step 3430, the base station transmits the user data carried in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In an optional fourth step 3440, the UE executes a client application associated with the host application executed by the host computer.

[0125] 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 as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 13 are included in this section. In a first step 3510 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In a second step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may proceed via the base station according to the teachings of the embodiments described throughout this disclosure. In an optional third step 3530, the UE receives the user data carried in the transmission.

[0126] 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 as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing references to FIG. 14 are included in this section. In an optional first step 3610 of the method, the UE receives input data provided by the host computer. Additionally or alternatively, in an optional second step 3620, the UE provides user data. In an optional sub-step 3621 of the second step 3620, the UE provides the 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, which provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. 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 an 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.

[0127] FIG. 15 is a flow chart illustrating a method performed in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only a drawing reference to FIG. 15 is included in this section. In an 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 a transmission of the received user 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.

[0128] Modifications of the disclosed embodiments and other embodiments will occur to those skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It is understood, therefore, that the embodiments are 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, these terms are used in a generic and descriptive sense only and not for purposes of limitation.

[0129] quotation [1]3GPP TS23.286, Application layer support for V2X services; Functional architecture and information flows, V1.1.0, April 2019 [2] 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional architecture and information flows, V1.1.0, April 2019

[0130] Abbreviations 2X AS V2X Application Server VAE V2X Application Enabler V2X UE User Equipment ITS Intelligent Transport System ITS-S ITS station V2X Vehicle to Everything

[0131] appendix 1. Introduction The current TS describes the procedure for downlink V2X message delivery from V2X AS to V2X UE. In some V2X applications, e.g. road obstacle warning use case, vehicles send warning messages about detected dangerous situations to a backend server, which further disseminates the warning messages to other vehicles via downlink communication. In this case, the V2X messages need to be delivered from V2X UE to V2X AS.

[0132] 2. Reasons for the change To specify the procedure for uplink V2X message delivery from a V2X UE to a V2X AS.

[0133] 3. Conclusion <Conclusion section (optional)>

[0134] 4. Proposal It is proposed to agree to the following changes to 3GPP TS 23.286 v1.1.0: TIFF0007636475000005.tif12170

[0135] 9.x V2X Uplink Message Delivery 9.x.1 Overview The VAE capability provides support for uplink V2X message delivery from the V2X UE to a V2X application specific server.

[0136] 9.x.2 Information Flow 9.x.2.1 V2X messages Table 9.x.2.1-1 describes the information flow for a VAE client to send a V2X message to a VAE server. TIFF0007636475000006.tif71170

[0137] 9.x.2.2 V2X Message Response Table 9.x.2.2-1 describes the information flow for the VAE server responding to a V2X message received from a VAE client. TIFF0007636475000007.tif31170

[0138] 9.x.3 Uplink V2X Message Delivery 9.x.3.1 Overview This subclause describes a procedure for delivering V2X messages from a V2X UE to a V2X application server.

[0139] 9.x.3.2 Procedure Prerequisites 1. The VAE client has discovered the VAE server as described in subclause 9.1.2. 2. The VAE client has registered for a V2X service identified by a V2X service ID as described in subclause 9.2.

[0140] Figure 4: Procedure for delivering a message from a V2X UE to a V2X application server 1. The V2X application specific client sends a V2X message for a service with a V2X service ID to the VAE client. 2. The VAE client determines the VAE server for receiving the V2X message with the V2X service ID. 3. The VAE client sends the V2X message to the VAE server. 4. The VAE server provides V2X messages to the application-specific server. 5. The VAE server may provide a V2X message response to the VAE client. TIFF0007636475000008.tif11170

[0141] 2 References The following documents contain contributions which, through reference in this text, are considered contributions of this document: - References may be unique (identified by publication date, edition, version number, etc.) or non-unique. - For unique references, subsequent review does not apply. - For non-specific references, the latest version applies. In the case of references to 3GPP documents (including GSM documents), the non-specific reference implicitly refers to the latest version of this document in the same publication as this document. · [1]3GPP TR21.905: “Vocabulary for 3GPP Specifications” · [2]3GPP TS22.185: “Service requirements for V2X services;Stage 1” · [3]3GPP TS22.186: “Enhancement of 3GPP support for V2X scenarios;Stage 1” · [4]3GPP TS23.280: “Common functional architecture to support mission critical services” · [5]3GPP TS23.285: “Architecture enhancements for V2X services” · [6]3GPP TS23.434: “Service enabler architecture layer for verticals;Functional architecture and information flows;Stage 2” · [7]3GPP TS23.468: “Group Communication System Enablers for LTE(GCSE_LTE);Stage 2” · [8]3GPP TS23.682: “Architecture enhancements to facilitate communications with packet data networks and applications” · [9]3GPP TR23.795: “Study on application layer support for V2X services” ·

[10] 3GPP TS26.346:「Multimedia Broadcast / Multicast Service(MBMS);Protocols and codecs」 ·

[11] 3GPP TS26.348:「Northbound Application Programming Interface(API)for Multimedia Broadcast / Multicast Service(MBMS)at the xMB reference point」 ·

[12] 3GPP TS29.214:「Policy and Charging Control over Rx reference point」 ·

[13] 3GPP TS29.468:「Group Communication System Enablers for LTE(GCSE_LTE);MB2 Reference Point;Stage 3」 ·

[14] 3GPP TS36.300:「Evolved Universal Terrestrial Radio Access(E-UTRA)and Evolved Universal Terrestrial Radio Access Network(E-UTRAN);Overall description;Stage 2」 ·

[15] ETSI TS102 894-2(V1.2.1):「Intelligent Transport Systems(ITS);Users and applications requirements;Part2:Applications and facilities layer common data dictionaryMultimedia Broadcast / Multicast Service(MBMS);Protocols and codecs」 ·

[16] ETSI TS102 965(V1.4.1):「Intelligent Transport Systems(ITS);Application Object Identifier(ITS-AID);Registration」 ·

[17] ISO TS17419: “Intelligent Transport Systems - Cooperative systems - Classification and management of ITS applications in a global context” · [X]ETSI-EN302 637-3(V1.3.0): “Intelligent Transport Systems(ITS);Vehicular Communications;Basic Set of Applications;Part3:Specifications of Decentralized Environmental Notification Basic Service”

[0142] 1. Introduction This contribution proposes a pCR in the architectural requirements to include VAE capability support for uplink V2X message delivery.

[0143] In some V2X applications, e.g., road obstacle warning use cases, vehicles send warning messages about detected dangerous situations to a backend server, which then further disseminates the warning messages to other vehicles via downlink communication. In this case, the V2X messages need to be delivered from the V2X UE to the V2X AS.

[0144] 2. Reasons for the change The VAE capability supports the delivery of V2X messages from the V2X UE to the V2X application.

[0145] 3. Conclusion <Conclusion section (optional)>

[0146] 4. Proposal It is proposed to agree to the following changes to 3GPP TS 23.286 v1.1.0: ***First Change****

[0147] 4.5 V2X Application Message Delivery 4.5.1 Description This subclause specifies V2X (e.g., ETSI ITS, SAE) message delivery requirements.

[0148] 4.5.2 Requirements [AR-4.5.2-a] The VAE server provides a mechanism for having V2X messages distributed to all registered receivers within a target geographic area. [AR-4.5.2-b] The VAE server allows the delivery of several V2X messages over the same connection. [AR-4.5.2-c] The VAE client has the capability to register for V2X messages within one or more geographic areas. [AR-4.5.2-d] The VAE Server has the capability only to forward V2X messages to authorized V2X UEs within the target geographic area. [AR-4.5.2-e] The VAE server provides a mechanism for prioritized support of different V2X messages (e.g. safety messages). [AR-4.5.2-f] The VAE capability supports the delivery of V2X messages from the V2X UE to the V2X application.

Claims

1. 1. A method implemented by a Vehicle-to-Everything Application Enabler (VAE) client of a wireless device (10) for using a service in a wireless communication network for a Vehicle-to-Anything (V2X) wireless device, the method comprising: receiving (712) a V2X message for a service having a service ID from a V2X application specific client; - determining (713) a VAE server for receiving uplink V2X messages based on said service ID; sending the uplink V2X message to the VAE server determined based on the service ID, such that the VAE server determined based on the service ID provides the uplink V2X message to a V2X application specific server associated with the service ID (714); A method comprising:

2. - Registering (711) by the VAE client of the wireless device to the service identified by the Service ID. The method of claim 1 further comprising:

3. 3. The method of claim 1, wherein the uplink V2X message further includes one or more of a wireless device identification, a message payload, and a geographic identification of a location of the wireless device.

4. - receiving a response from the VAE server indicating success or failure (715); The method of claim 1 , further comprising:

5. 1. A method implemented by a Vehicle-to-Everything Application Enabler (VAE) server (13) for handling communications of a Vehicle-to-Everything (V2X) wireless device in a wireless communication network, comprising: receiving (721) an uplink V2X message having a service ID from a VAE client of a wireless device (10), the VAE client having received the uplink V2X message for a service having the service ID from a V2X application specific client, and determining the VAE server for receiving the uplink V2X message based on the service ID; providing said uplink V2X message to a V2X application specific server with which said service ID is associated; A method comprising:

6. A Vehicle-to-Everything Application Enabler (VAE) client of a wireless device (10) for using a service in a wireless communication network for a Vehicle-to-Anything (V2X) wireless device, comprising: receiving a V2X message for a service having a service ID from a V2X application specific client; determining a VAE server for receiving an uplink V2X message based on the service ID; sending the uplink V2X message to the VAE server determined based on the service ID, such that the VAE server determined based on the service ID provides the uplink V2X message to a V2X application specific server associated with the service ID; The VAE client is configured to:

7. The VAE client: Registering for the service identified by the service ID. The VAE client of claim 6 , further configured to:

8. 8. The VAE client of claim 6 or 7, wherein the uplink V2X message further includes one or more of a wireless device identification, a message payload, and a geographic identification of a location of the wireless device.

9. The VAE client: receiving a response from the VAE server indicating success or failure; The VAE client of claim 6 , further configured to:

10. A Vehicle-to-Everything Application Enabler (VAE) server for handling communications of a Vehicle-to-Anything (V2X) wireless device in a wireless communication network, comprising: receiving an uplink V2X message having a service ID from a VAE client of a wireless device, the VAE client receiving the uplink V2X message for a service having the service ID from a V2X application specific client, and determining the VAE server for receiving the uplink V2X message based on the service ID; providing the uplink V2X message to a V2X application specific server with which the service ID is associated; The VAE server is configured to:

11. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to perform the method of any one of claims 1 to 4 as implemented by the VAE client.

12. A computer program comprising instructions that, when executed on at least one processor, cause the at least one processor to perform the method of claim 5 as implemented by the VAE server.

Images