Procedures for triggering and updating teleoperated operations in a V2X application server

Abstract

To provide a communication method, a Vehicle-to-Everything (V2X) Application Enabler (VAE) client, and a program for supporting tele-operated driving (ToD) for vehicles.SOLUTION: A method implemented by a V2X application specific server to support session-oriented services for vehicles includes (1) sending a session-oriented service trigger request to a VAE server to initiate a session-oriented service for a client device, and (2) receiving a session-oriented service trigger response from the VAE server indicating whether the VAE server has the capability to initiate a session-oriented service with a VAE client.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates generally to communications, and more particularly to communications methods and related devices and nodes that support tele-operated driving (ToD). [Background technology]

[0002] Next, the standardization work involved is described.

[0003] Tele-operated support (TeSo) is specified in 3GPP TR22.886 (clause 5.21), with corresponding requirements in clause 7.2.5 for remote driving. Normative requirements are in 3GPP SA1 TS22.186, Service Requirements for Extended Vehicle-to-Everything (V2X) Scenarios, V16.2.0, June 2019 (clause 5.5).

[0004] Additionally, the 5G Automotive Association (5GAA) specified teleoperated driving use cases and corresponding service level requirements for teleoperated driving, teleoperated driving support, and automated parking in 5GAA T-190028, 5G Automotive Association; Working Group Use Cases and Technical Requirements; 5G Use Cases and Requirements - Wave 2.1; V1.0 (January 30, 2019). In an ongoing inter-working group work item, the 5GAA is researching communication solutions and operating architectures for teleoperated driving services.

[0005] 3GPP TS23.286, Application Layer Support for V2X Services; Functional Architecture and Information Flow, V16.1.0, 06-2019, specifies the V2X application layer model for V2X communications over PC5 and Uu. This model is shown in Figure 1. Referring to Figure 1, the V2X application enabler (VAE) layer provides support information to V2X applications.

[0006] V2X user equipment 1 (V2X UE1 100a) communicates with the V2X application server 110 over the V1 reference point. V2X UE1 100a and V2X user equipment 2 (V2X UE2 100b) communicate over the V5 reference point. V2X UE1 100a can also act as an inter-UE network relay to allow V2X UE2 100b to access the V2X application server 110 over the V1 reference point.

[0007] The V2X application layer functional entities for the V2X UEs 100a, 100b and the V2X application server 110 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 service enabler architecture layer for verticals (SEAL) services as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019.

[0008] The VAE server 114 is 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.

[0009] It should be noted that the 3GPP TS describes the functionality of the V2X application specific layer as being outside the scope of the TS.

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

[0011] The V2X UEs 100a, 100b include VAE clients 104a, 104b, SEAL clients 106a, 106b, and V2X application-specific clients 102a, 102b. The VAE clients 104a, 104b provide V2X application layer support functions to the V2X application-specific clients 102a, 102b over the Vc reference point.

[0012] Note that in some deployments, the SEAL client 106a, 106b and server 116 entities may be part of the VAE client 104a, 104b and VAE server 114, respectively.

[0013] The VAE clients 104a, 104b act as VAL (Vertical Application Layer) clients for their interactions with the SEAL clients 106a, 106b, as specified in 3GPP TS 23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019. The VAE server 114 acts as a VAL server for its interactions with the SEAL server 116, as specified in 3GPP TS 23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019.

[0014] At the VAE layer, the VAE clients 104a, 104b communicate with the VAE server 114 over the V1-AE reference point. At the V2X application-specific layer, the V2X application-specific clients 102a, 102b communicate with the V2X application-specific server over the V1-APP reference point.

[0015] Note that the 3GPP TS describes the V1-APP reference point as being outside the scope of the TS.

[0016] At the VAE layer, the VAE client 104b of V2X UE2 100b communicates with the VAE client 104a of V2X UE1 100a over the V5-AE reference point. At the V2X application-specific layer, the V2X application-specific client 102b of V2X UE2 100b communicates with the VAE client 104a of V2X UE1 100a over the V5-APP reference point.

[0017] Note that the 3GPP TS describes the V5-APP reference point as being outside the scope of the TS.

[0018] The following SEAL services for V2X applications are supported: Location Management, as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019 Group Management, as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019 Configuration Management, as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019 Identity Management, as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019 Key management, as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019; and Network Resource Management, as specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019.

[0019] VAE clients 104a, 104b interact with SEAL clients 106a, 106b over a SEAL-C reference point designated for each SEAL service. VAE server 114 interacts with SEAL server 116 over a SEAL-S reference point designated for each SEAL service. Interaction between SEAL clients 106a, 106b is supported by a SEAL-PC5 reference point designated for each SEAL service. Interaction between SEAL clients 106a, 106b and the corresponding SEAL server 116 is supported by a SEAL-UU reference point designated for each SEAL service.

[0020] Note that the SEAL-C, SEAL-S, SEAL-PC5, and SEAL-Uu reference points for each SEAL are specified in 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019.

[0021] To support distributed VAE server deployment, the VAE server 114 interacts with other VAE servers over a VAE-E reference point.

[0022] The V2X UE1 100a also To enable the VAE client 104b on the V2X UE2 100b to access the VAE server 114 over the V1-AE reference point; and To enable the V2X application specific client 102b on the V2X UE2 100b to access the V2X application specific server 112 over the V1-APP reference point, It can act as an inter-UE network relay.

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

[0024] The VAE server 114 interacts with the 3GPP network system 108 over the V2, MB2, xMB, Rx, and T8 reference points. EPS and 5GS, 3GPP TR23.764, Study on Extending Application Layer Support for V2X Services, V0.2.0, July 2019, are considered 3GPP network systems. Summary of the Invention

[0025] Establishing session-oriented communication for services such as teleoperated driving is described in 3GPP TR23.764. However, 3GPP TR23.764 fails to describe the trigger for teleoperated driving support, i.e., when ToD is required. This should occur before a ToD session is established. Also, device and server APIs for initiating ToD support are not described. 3GPP TR23.764 also does not allow a V2X application-specific server to request a VAE server to establish session-oriented communication for a teleoperated driving session.

[0026] According to some embodiments of the inventive concept, there is provided a method, implemented by a first server, for supporting session-oriented services for a vehicle. The method includes sending a session-oriented service trigger request to a second server to initiate the session-oriented service for a client device. The method further includes receiving a session-oriented service trigger response from the second server indicating whether the second server has the capability to initiate the session-oriented service with the client device.

[0027] A first server and computer program embodiment of a similar inventive concept is provided.

[0028] One advantage that may be realized with the inventive concepts described herein is that a V2X service provider (e.g., a road authority) may use APIs and procedures to communicate with a mobile network operator to establish session-oriented services for vehicles, such as, for example, ToD support.

[0029] According to another embodiment of the inventive concept, there is provided a method, implemented by a second server, for supporting session-oriented services for a vehicle, the method including receiving a session-oriented service trigger request from a first server to initiate a session-oriented service for a client device, the method further including sending a session-oriented service trigger response to the first server indicating whether the second server has the capability to initiate the session-oriented service with the client device.

[0030] A second server and computer program embodiment of a similar inventive concept is provided.

[0031] According to a further embodiment of the inventive concept, there is provided a method implemented by a Vehicle to Everything (V2X) Application Enabler (VAE) client of a computing device. The method includes receiving a session-oriented service request from a second server, the session-oriented service request including an identification of the VAE client, an identification of the session, and a reporting configuration. The method includes sending a session-oriented service response to the second server indicating acceptance of the session-oriented service request. The method includes providing a session-oriented service establishment notification to the V2X application-specific client.

[0032] Similar VAE clients and computer programs are provided.

[0033] The accompanying drawings, which are included to provide a further understanding of the present disclosure and are incorporated in and constitute a part of this application, illustrate several non-limiting embodiments of the inventive concepts. [Brief explanation of the drawings]

[0034] [Figure 1] FIG. 1 is a block diagram illustrating a V2X application layer model, according to some embodiments. [Figure 2] FIG. 1 is a signaling diagram illustrating a procedure for triggering a VAE server to establish a session-oriented service with a VAE client according to some embodiments of the inventive concept. [Figure 3] FIG. 2 is a signaling diagram illustrating a procedure for establishing a session-oriented service between a VAE server and a VAE client according to some embodiments of the inventive concept. [Figure 4] FIG. 1 is a signaling diagram illustrating a procedure for providing session-oriented service updates from a V2X application-specific server to a VAE server, according to some embodiments of the inventive concept. [Figure 5] FIG. 1 is a signaling diagram illustrating a procedure for updating a session-oriented service between a VAE server and a VAE client according to some embodiments of the inventive concept. [Figure 6] FIG. 1 is a signaling diagram illustrating a procedure for updating a session-oriented service triggered by a VAE client according to some embodiments of the inventive concept. [Figure 7] FIG. 1 is a signaling diagram illustrating a procedure for providing a session-oriented service termination request from a V2X application-specific server to a VAE server, according to some embodiments of the inventive concept. [Figure 8] FIG. 1 is a signaling diagram illustrating a procedure for terminating a session-oriented service between a VAE server and a VAE client according to some embodiments of the inventive concept. [Figure 9] FIG. 1 is a signaling diagram illustrating a procedure for terminating a session-oriented service triggered by a VAE client according to some embodiments of the inventive concept. [Figure 10] FIG. 1 is a block diagram illustrating a V2X UE, in accordance with some embodiments of the inventive concept. [Figure 11] FIG. 1 is a block diagram illustrating a VAE server, according to some embodiments of the inventive concept. [Figure 12]FIG. 1 is a block diagram illustrating a V2X application specific server, in accordance with some embodiments of the inventive concept. [Figure 13] 10 is a flowchart illustrating the operation of a first server, in accordance with various embodiments of the inventive concept. [Figure 14] 10 is a flowchart illustrating the operation of a first server, in accordance with various embodiments of the inventive concept. [Figure 15] 10 is a flowchart illustrating the operation of a first server, in accordance with various embodiments of the inventive concept. [Figure 16] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 17] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 18] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 19] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 20] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 21] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 22] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 23] 10 is a flowchart illustrating the operation of a second server, in accordance with various embodiments of the inventive concept. [Figure 24] 10 is a flowchart illustrating the operation of a VAE client, in accordance with some various embodiments of the inventive concept. [Figure 25] 10 is a flowchart illustrating the operation of a VAE client, in accordance with some various embodiments of the inventive concept. [Figure 26] 10 is a flowchart illustrating the operation of a VAE client, in accordance with some various embodiments of the inventive concept. [Figure 27] 10 is a flowchart illustrating the operation of a VAE client, in accordance with some various embodiments of the inventive concept. [Figure 28] 10 is a flowchart illustrating the operation of a VAE client, in accordance with some various embodiments of the inventive concept. [Figure 29] 1 is a block diagram of a wireless network according to some embodiments. [Figure 30] FIG. 2 is a block diagram of a user equipment according to some embodiments. [Figure 31] FIG. 1 is a block diagram of a virtualized environment, according to some embodiments. [Figure 32] FIG. 1 is a block diagram of a communications network connected to a host computer through an intermediate network, according to some embodiments. [Figure 33] FIG. 1 is a block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection, according to some embodiments. [Figure 34] 1 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 35] 1 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 36] 1 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments. [Figure 37] 1 is a block diagram of a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0035] The inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which example embodiments of the inventive concepts are shown. However, the inventive concepts may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It can be implicitly assumed that elements from one embodiment are present / used in another embodiment.

[0036] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as instructional examples and should not be construed as limiting the scope of the disclosed subject matter. For example, some details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter.

[0037] In the following description, the terms "approval" and "acceptance" may be used interchangeably.

[0038] FIG. 12 is a block diagram illustrating elements of a V2X UE 800 implementing a V2X application-specific client 102 and / or a VAE client 104 configured to provide wireless communication in accordance with an embodiment of the inventive concept. (A V2X UE may also be referred to as a mobile terminal, mobile communication terminal, wireless device, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment (UE), user equipment node / terminal / device, etc.) (The V2X UE 800 may be provided, for example, as described below with respect to the wireless device 4110 of FIG. 29, the UE 4200 of FIG. 30, the virtualization hardware 4430 and virtual machine 4340 of FIG. 31, the UEs 4491 and 4492 of FIG. 32, and the UE 4530 of FIG. 33, all of which are considered interchangeable in the examples and embodiments described herein unless otherwise noted and are to be within the intended scope of the present disclosure.) As shown, the V2X The UE 800 may include an antenna 1007 (e.g., corresponding to antenna 4111 of FIG. 29 and / or antenna 43225 of FIG. 31) and a transceiver circuit 1001 (e.g., also referred to as a transceiver, corresponding to interface 4114 of FIG. 29, interfaces 4205, 4209, 4211 of FIG. 30, transmitter 4233 and receiver 4235, transmitter 43210 and receiver 43220 of FIG. 31, and air interface 4537 of FIG. 33) including a transmitter and receiver configured to provide uplink and downlink wireless communication with (one or more) base stations of a communication network (e.g., corresponding to network node 4160 of FIG. 29, also referred to as a RAN node). The V2X UE 800 may also include a processing circuit 1003 (e.g., corresponding to processing circuit 4120 of FIG. 29, processor 4201 of FIG. 30, processing circuit 4360 of FIG. 31, and processing circuit 4538 of FIG. 33, also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 1005 (e.g., corresponding to device-readable medium 4130 of FIG. 29 and / or memory 4390 of FIG. 31, also referred to as a memory) coupled to the processing circuit.The memory circuit 1005 may include computer-readable program code that, when executed by the processing circuit 1003, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 1003 may be defined to include memory such that a separate memory circuit is not required. The V2X UE 800 may also include an interface (such as a user interface) coupled to the processing circuit 1003 and / or the V2X UE 800 may be integrated into the vehicle.

[0039] As described herein, operations of the V2X UE 800 may be performed by the processing circuit 1003 and / or the transceiver circuit 1001. For example, the processing circuit 1003 may control the transceiver circuit 1001 to transmit communications over an air interface to a radio access network node (also called a base station) through the transceiver circuit 1001 and / or receive communications over an air interface from a network node through the transceiver circuit 1001. Moreover, modules may be stored in the memory circuit 1005 that, when executed by the processing circuit 1003, cause the processing circuit 1003 to perform respective operations (e.g., operations described below with respect to exemplary embodiments related to a VAE client).

[0040] FIG. 11 is a block diagram illustrating elements of a V2X Application Enabler (VAE) server 114 configured to provide wireless communications in accordance with an embodiment of the inventive concept (the VAE server 114 may also be referred to as a second server, a network node, a base station, an eNodeB / eNB, a gNodeB / gNB, etc.). (VAE server 114 may be provided, for example, as described below with respect to network node 4160 of FIG. 29, virtual hardware 4330 or virtual machine 4340 of FIG. 31, base stations 4412a, 4412b, and 4412c of FIG. 32, and / or base station 4520 of FIG. 33, all of which are considered interchangeable in the examples and embodiments described herein unless otherwise noted and should be within the intended scope of the present disclosure.) As shown, VAE server 114 may include transceiver circuitry 1101 (e.g., corresponding to part of interface 4190 of FIG. 29 and / or part of wireless interface 4527 of FIG. 33) including a transmitter and a receiver configured to provide uplink and downlink wireless communication with other servers and nodes of the communication network. The VAE server 114 may include a network interface circuit 1107 (e.g., corresponding to a portion of interface 4190 in FIG. 29 , network interfaces 4370, 4380 in FIG. 31 , and / or communication interface 4526 in FIG. 33 ) configured to provide communication with other nodes of the RAN and / or core network CN (e.g., with other base stations). The VAE server 114 may also include a processing circuit 1103 (e.g., corresponding to a portion of processing circuit 4170 in FIG. 29 , processing circuit 4360 in FIG. 31 , and / or processing circuit 4528 in FIG. 33 ) coupled to the transceiver circuit, and a memory circuit 1105 (e.g., corresponding to a device-readable medium 4180 in FIG. 29 and / or memory 4390 in FIG. 31 ) coupled to the processing circuit.The memory circuit 1105 may include computer-readable program code that, when executed by the processing circuit 1103, causes the processing circuit to perform operations according to embodiments disclosed herein. According to other embodiments, the processing circuit 1103 may be defined to include memory such that a separate memory circuit is not required. The VAE server 114 may also include an interface (such as a user interface) coupled to the processing circuit 1103, and / or the VAE server 114 may be integrated into the vehicle.

[0041] As described herein, operations of VAE server 114 may be performed by processing circuit 1103 and / or transceiver circuit 1101. For example, processing circuit 1103 may control transceiver circuit 1101 to transmit communications over the wireless interface to network nodes and / or receive communications over the wireless interface from nodes through transceiver circuit 1101. Moreover, modules may be stored in memory circuit 1105 that, when executed by processing circuit 1103, cause processing circuit 1103 to perform respective operations (e.g., operations described below with respect to exemplary embodiments relating to the first server).

[0042] 12 is a block diagram illustrating elements of a V2X application-specific server 112 configured to provide wireless communications (the V2X application-specific server 112 may also be referred to as a first server, etc.) in accordance with an embodiment of the inventive concept. (The V2X application-specific server 112 may be provided, for example, as described below with respect to network node 4160 of FIG. 29, virtual hardware 4330 or virtual machine 4340 of FIG. 31, base stations 4412a, 4412b, and 4412c of FIG. 32, and / or base station 4520 of FIG. 33, all of which are considered interchangeable in the examples and embodiments described herein unless otherwise noted and are within the intended scope of the present disclosure.) As shown, the V2X application-specific server 112 may include transceiver circuitry (not shown) including a transmitter and receiver (e.g., corresponding to part of interface 4190 of FIG. 29 and / or part of air interface 4527 of FIG. 33) configured to provide uplink and downlink wireless communications with other servers and nodes of a communications network. The V2X application-specific server 112 may include a network interface circuit 407 (e.g., corresponding to a portion of interface 4190 in FIG. 29 , network interfaces 4370, 4380 in FIG. 31 , and / or communication interface 4526 in FIG. 33 ). The V2X application-specific server 112 may also include a processing circuit 1203 (e.g., corresponding to processing circuit 4170 in FIG. 29 , processing circuit 4360 in FIG. 31 , and / or processing circuit 4528 in FIG. 33 ) coupled to the transceiver circuit, and a memory circuit 1205 (e.g., corresponding to device-readable medium 4180 in FIG. 29 and / or memory 4390 in FIG. 31 ) coupled to the processing circuit. The memory circuit 1205 may include computer-readable program code that, when executed by the processing circuit 1203, causes the processing circuit to perform operations according to embodiments disclosed herein.According to other embodiments, the processing circuit 1203 may be defined to include memory such that a separate memory circuit is not required. The V2X application specific server 112 may also include an interface (such as a user interface) coupled to the processing circuit 1203.

[0043] As described herein, operations of the V2X application-specific server 112 may be performed by the processing circuit 1203 and / or the transceiver circuit 1201. For example, the processing circuit 1203 may control the transceiver circuit 1201 to transmit communications over the air interface to a network node through the transceiver circuit 1201 and / or receive communications over the air interface from a node through the transceiver circuit 1201. Moreover, modules may be stored in the memory circuit 1205 that, when executed by the processing circuit 1203, cause the processing circuit 1203 to perform respective operations (e.g., operations described below with respect to exemplary embodiments relating to a first server).

[0044] This application addresses session-oriented services such as see-through for pass maneuvers (when implemented via Vehicle-to-Network (V2N) communications), high-definition sensor sharing (when implemented via V2N communications), and remote-operated driving between a V2X application server 112 acting as a remote driver and a V2X UE 100 acting as an operated vehicle. The disclosure herein focuses on triggers for session-oriented services in the V2X application specific server 112. A session-oriented service is a service provided specifically for a session and is terminated when the session is terminated.

[0045] There are several example use cases where ToD support is required. The vehicle driver or automated driving system relies on the remote driver to take control of the vehicle for the duration of the journey to the destination. The driver or automated driving system of a vehicle entering a construction zone or accident scene sends a teleoperated driving request to a remote driver to take control of the vehicle for a limited time and area. Automated Parking: A vehicle driver or autonomous driving system enters a public or private parking area and requests remote driving assistance for automated parking. Infrastructure-based teleoperated driving: This is a way of implementing ToD using data and input from infrastructure sensors and cameras to the remote driver, rather than just from the vehicle's on-board sensors and cameras.

[0046] Thus, there are two levels of control. The remote driver sends assistance information as trajectory information (e.g. waypoints) to the vehicle or to the automated driving system, which is still responsible for the vehicle's motion control, e.g. steering wheel angle, braking, and acceleration. The remote driver has full control over the driving of the car and can remotely operate the car, for example controlling acceleration and steering wheel angle.

[0047] In session-oriented services such as teleoperated driving (ToD), a remote entity, either human or machine, provides relevant information to a remotely driven vehicle. For example, in some implementations, a remote operation center provides a trajectory for the vehicle to drive in an autonomous manner to an available / predefined parking spot. In other implementations, the remote operation center (human or machine) assumes the responsibility of driving the vehicle (i.e., sending steering / command instructions), supported by real-time video streaming and sensor information sent from the remotely driven vehicle. Overall, a teleoperated driving session involves the transmission of sensor data (interpreted objects) from the vehicle to the operation center, and, in the case of a human remote driver, progressive high-definition video / cameras (up to four cameras are required, one for each corner of the vehicle). Information sent from the remote center to the vehicle is in the form of driving trajectory (e.g., in the form of waypoints with associated timestamps) and steering commands, such as torque values ​​for braking / acceleration and steering. Depending on the implementation, teleoperated driving may require up to 20 ms latency (to ensure commands and vehicle status are synchronized) and data rates of up to 64 Mbps, allowing for transmission of video at multiple to HD qualities. Considering that when such requirements are not met, teleoperated driving cannot occur (i.e., the vehicle must cease being driven remotely and switch to fully autonomous driving or a human driver in the vehicle), it is important to know when / where teleoperated driving can be supported.

[0048] The inventive concepts described herein enable at least the following: Triggering session-oriented services, such as ToD sessions, from the V2X application-specific server to the VAE server, updating and terminating sessions. Notifications from the VAE server to the V2X application specific server about session establishment, updates (e.g., parameter changes), and termination for established sessions. Notifications from the VAE client to the V2X application-specific client about session establishment, updates, and termination for established sessions.

[0049] In various embodiments of the inventive concepts, the VAE layer provides support at the application layer for session-oriented services, such as teleoperated driving, by establishing, updating, and terminating sessions. Procedures for triggering, maintaining, modifying, and terminating session-oriented services, such as teleoperated driving, in a V2X application-specific server toward a VAE server, and notifications toward the V2X application-specific server and client, are described. Thus, a viable mechanism for a V2X application server to establish, maintain, and terminate session-oriented services, such as teleoperated driving, with a V2X UE can be achieved using the inventive concepts described herein.

[0050] A process for triggering (e.g., initiating) a session-oriented service establishment is now described. In some embodiments, the V2X application specific server 112 has received a request to trigger a session-oriented service from the V2X application specific client 102 along with information needed to perform the session-oriented service. The V2X application specific server 112 has evaluated the request from the V2X application specific client 102 and determined to trigger a session-oriented service.

[0051] 2, in operation 1, the V2X application-specific server 112 triggers the VAE server 114 to initiate a session-oriented service for the VAE client 104. The request may include information such as an identification of the VAE client, an identification of the V2X application-specific server, an identification of the service session, and the “type” or “QoS requirements” of the session.

[0052] With regard to information related to service type or QoS requirements, examples of such information may include information on how many flows are associated with a session of a session-oriented service (e.g., a session may have multiple flows, e.g., one for uplink video and one for control information), and for each of these flows the server may specify: - Primary service requirements (such as minimum bit rate) and alternative service requirements, ordered in a preferred manner. - Indication of whether notification control is required in case of QoS un-fulfillment / re-fulfilment. - An indication of whether QoS sustainability analysis information is required, as specified in TS 23.288, clause 6.9. If required, the server may also include in the request: · KPIs (Key Performance Indicators) to be considered to generate QoS sustainability analysis. Thresholds for triggering notifications on QoS sustainability analysis. Advance time to trigger notifications for QoS sustainability analysis. Information about UE measurements related to session-oriented services that can be collected at the application layer (KPIs, frequency of measurements, reporting thresholds, etc.). This indicates whether such measurements can be collected on the client side or on the server side.

[0053] In operation 2, the VAE server 114 provides a session-oriented service trigger response to the V2X application-specific server 112 indicating the capability of the VAE server 112 to initiate a session-oriented service with the VAE client. The response is based on network information and other VAE server-specific information (e.g., load). If the VAE server is not capable of supporting the session-oriented service requested by the V2X application-specific server, an indication that the VAE server 114 is not capable of supporting the session-oriented service is provided in the response.

[0054] Figure 13 illustrates the operation of Figure 2 from the perspective of a V2X application-specific server, designated as the first server 112. With reference to Figure 13, the operation of the first server 112 (implemented using the structure of the block diagram of Figure 12) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of Figure 13. For example, modules may be stored in the memory 1205 of Figure 12 that may provide instructions such that, when the instructions of the modules are executed by the respective communications device processing circuitry 1203, the processing circuitry 1203 performs the respective operations of the flowchart.

[0055] At block 1301, the processing circuit 1203 sends a session-oriented service trigger request to the second server 114 to initiate a session-oriented service for the client device 104. Sending the session-oriented service trigger request, in some embodiments, includes sending the session-oriented service trigger request along with information associated with the session-oriented service. The information may include one or more of an identification of the client device 104, an identification of the first server 112, an identification of the service session, and a type or quality of service (QoS) requirement of the session-oriented service.

[0056] The information relating to the type or QoS requirements includes information on how many flows are associated with the session-oriented service, and for each flow, the information includes one or more of: primary and alternative service requirements ordered in a prioritized manner; an indication of whether notification control is required in case of QoS failure / re-implementation; an indication of whether QoS sustainability analysis information is required; and information on user equipment (UE) measurements. When QoS sustainability analysis information is required, the information further includes one or more of: key performance indicators (KPIs) to be taken into account for generating the QoS sustainability analysis; a threshold for triggering a notification regarding the QoS sustainability analysis; and a time in advance for triggering a notification regarding the QoS sustainability analysis.

[0057] In block 1303, the processing circuit 1303 receives a session-oriented service trigger response from the second server 114 indicating whether the second server 114 has the capability to initiate a session-oriented service with the client device. As indicated above, whether the second server 114 has the capability to initiate a session-oriented service is based on network information and other server-specific information (e.g., load). If the second server 114 is not capable of supporting the session-oriented service requested by the first server 112, it is indicated in the response.

[0058] As described in the description of FIG. 3, the processing circuit 1203 receives, in block 1305, a session-oriented service establishment notification from the second server 114 indicating that the session-oriented service has been established.

[0059] 16 illustrates the operation of FIG. 2 from the perspective of a VAE server, designated as second server 114. Referring to FIG. 16, the operation of second server 114 (implemented using the structure of the block diagram of FIG. 11) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of FIG. 16. For example, modules may be stored in memory 1105 of FIG. 11 that may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1103, processing circuitry 1103 performs the respective operations of the flowchart.

[0060] In block 1601, the processing circuit 1103 receives a session-oriented service trigger request from the first server 112 to initiate a session-oriented service for the client device 104. Receiving the session-oriented service trigger request, in some embodiments, includes receiving the session-oriented service trigger request along with information associated with the session-oriented service. The information may include one or more of an identification of the client device 104, an identification of the first server 112, an identification of the service session, and a type or quality of service (QoS) requirement of the session-oriented service.

[0061] The information relating to the type or QoS requirements includes information on how many flows are associated with the session-oriented service, and for each flow, the information includes one or more of: primary and alternative service requirements ordered in a prioritized manner; an indication of whether notification control is required in case of QoS failure / re-implementation; an indication of whether QoS sustainability analysis information is required; and information on user equipment (UE) measurements. When QoS sustainability analysis information is required, the information further includes one or more of: key performance indicators (KPIs) to be taken into account for generating the QoS sustainability analysis; a threshold for triggering a notification regarding the QoS sustainability analysis; and a time in advance for triggering a notification regarding the QoS sustainability analysis.

[0062] In block 1603, the processing circuit 1103 sends a session-oriented service trigger response to the first server 112 indicating whether the second server 114 has the capability to initiate a session-oriented service with the client device 104. As indicated above, whether the second server has the capability to initiate a session-oriented service is based on network information and other server-specific information (e.g., load). If the second server 114 is not capable of supporting the session-oriented service requested by the first server 112, it is indicated in the response.

[0063] As described in the description of FIG. 3, the processing circuit 1103 in block 1605 sends a session-oriented service establishment notification to the first server 112 indicating that the session-oriented service has been established.

[0064] 3, session-oriented service establishment will be described. A V2X UE (e.g., a client device 100 having a VAE client 104 and / or a V2X application-specific client 102) is authenticated to use session-oriented services and has connected to a V2X application server 112. The VAE server 114 has agreed to establish a session upon request from the V2X application-specific server 112, as described above.

[0065] In operation 1, the VAE server 114 sends a request to one or more VAE clients to establish a session-oriented service, the request including the VAE client's identification information, the session's identification information, and a reporting configuration, which indicates what parameters should be reported and how frequently the parameters should be reported.

[0066] In operation 2, the VAE client 104 sends a session-oriented service response to the VAE server 114 indicating approval of the session establishment request by the VAE server 114 .

[0067] In operation 3, the VAE server 114 sends a session-oriented service establishment notification to the V2X application-specific server 112 (block 1305 in FIG. 13 and block 1605 in FIG. 16).

[0068] In operation 4, the VAE client 104 sends a session-oriented service establishment notification to the V2X application-specific client 102 (block 2405 of FIG. 24).

[0069] 17 illustrates the operation of FIG. 3 from the perspective of VAE server 114, designated as second server 114. Referring to FIG. 17, the operation of second server 114 (implemented using the structure of the block diagram of FIG. 11) according to some embodiments of the inventive concept in supporting session-oriented services for vehicles will now be described with reference to the flowchart of FIG. 17. For example, modules may be stored in memory 1105 of FIG. 11 that provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1103, processing circuitry 1103 performs the respective operations of the flowchart.

[0070] In block 1701, the processing circuit 1103 sends a session-oriented service request to a client device 100 having a VAE client 104 to establish a session-oriented service, where the session-oriented service request includes identification information of the VAE client 104, identification information of the session, and reporting settings.

[0071] In block 1703, the processing circuit 1103 receives a session-oriented service response indicating acceptance of the session-oriented service request from the client device 100 having the VAE client 104 to establish the session-oriented service. In block 1705, the processing circuit 1103 sends a session-oriented service establishment notification to the first server 112 in response to receiving the session-oriented service response indicating acceptance. Block 1705 is similar to block 1305 of FIG. 13 .

[0072] Figure 24 illustrates the operation of Figure 3 from the perspective of VAE client 104. Referring to Figure 24, the operation of VAE client 104 (implemented using the structure of the block diagram of Figure 10) according to some embodiments of the inventive concepts in supporting session-oriented services will now be described with reference to the flowchart of Figure 24. For example, modules may be stored in memory 1005 of Figure 10, and these modules may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1003, the processing circuitry 1003 performs the respective operations of the flowchart.

[0073] In block 2401, the processing circuit 1003 receives a session-oriented service request from the second server 114, where the session-oriented service request includes an identification of the VAE client 104, an identification of the session, and a reporting setting.

[0074] At block 2403, the processing circuit 1003 sends a session-oriented service response indicating approval of the session-oriented service request to the second server 114. At block 2405, the processing circuit 1003 provides a session-oriented service establishment notification to the V2X application-specific client 102.

[0075] As described above, once a session-oriented service is established with the VAE client 104, the V2X application-specific server 112 may need to update the parameters of the session, for example, by receiving updates regarding the remote driving session parameters from the V2X application-specific client 102.

[0076] 4, there is shown a procedure for triggering a session-oriented service change from the V2X application-specific server 112 to the VAE server 114. In operation 1, the V2X application-specific server 112 provides the VAE server 114 with a session-oriented change trigger event, including an update to the session's identification information and session parameters, e.g., a change to the session's QoS requirements.

[0077] In operation 2, the VAE server 114 provides a session-oriented service change trigger response that includes the ability to continue the session-oriented service with the VAE client 104 under the updated conditions. If the VAE server 114 is not able to continue the session-oriented service under the updated conditions, an indication that the VAE server 114 is not able to continue the session-oriented service is provided in the response.

[0078] Figure 14 illustrates the operation of Figure 4 from the perspective of a V2X application-specific server 112, designated as the first server 112. With reference to Figure 14, operation of the first server 112 (implemented using the structure of the block diagram of Figure 12) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of Figure 14. For example, modules may be stored in the memory 1205 of Figure 12 that may provide instructions such that, when the instructions of the modules are executed by the respective communications device processing circuitry 1203, the processing circuitry 1203 performs the respective operations of the flowchart.

[0079] In block 1401, the processing circuit 1203 sends a session-oriented service change request to the second server (114), where the session-oriented service change request includes one or more updates to service information or changes in server information.

[0080] In block 1403, the processing circuit 1203 receives a session-oriented service change response from the second server 114 indicating whether the second server 114 can continue the session-oriented service with the updated session parameters.

[0081] Once the session-oriented service change is completed, the processing circuit 1203 receives a session-oriented service change notification from the second server 114 in block 1405 .

[0082] 18 illustrates the operation of FIG. 4 from the perspective of VAE server 114, designated as second server 114. Referring to FIG. 18, the operation of second server 114 (implemented using the structure of the block diagram of FIG. 11) according to some embodiments of the inventive concept in supporting session orientation will now be described with reference to the flowchart of FIG. 18. For example, modules may be stored in memory 1105 of FIG. 11 that may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1103, processing circuitry 1103 performs the respective operations of the flowchart.

[0083] In block 1801, the processing circuit 1103 receives a session-oriented service change trigger request from the first server (112), the session-oriented service change request including identification information of the session-oriented service and an updated session parameter session-oriented service change request.

[0084] In block 1803, in response to determining that the session-oriented service can be provided with the updated session parameters, the processing circuit 1103 sends a session-oriented service change trigger response to the first server 112 indicating the ability to continue the session-oriented service with the updated session parameters.

[0085] In block 1805, in response to determining that the session-oriented service cannot be provided with the updated session parameters, the processing circuit 1103 sends a session-oriented service change trigger response to the first server 112 indicating that the second server 114 cannot continue the session-oriented service with the updated session parameters.

[0086] 5 , a procedure for updating a session-oriented service between the VAE server 114 and the VAE client 104 will now be described. The VAE server 114 has established a session-oriented service with the VAE client and received a session-oriented service update from the V2X application-specific server 112 as described above or received changes in QoS and network conditions from the 3GPP network system 108.

[0087] In operation 1, the VAE server 114 sends a session-oriented change request to one or more VAE clients 104, including update requirements (e.g., changes to network / QoS requirements) or changes to server information (e.g., changes to the VAE server).

[0088] In operation 2, the VAE client 104 sends a session-oriented modification response to the VAE server 114 indicating acceptance of the session-oriented modification request by the VAE server 114 .

[0089] In operation 3, the VAE server 114 sends a session-oriented service change notification to the V2X application-specific server 112.

[0090] In operation 4, the VAE client 104 sends a session-oriented service change notification to the V2X application-specific client 102.

[0091] 19 illustrates the operation of FIG. 5 from the perspective of VAE server 114, designated as second server 114. Referring to FIG. 19, the operation of second server 114 (implemented using the structure of the block diagram of FIG. 11) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of FIG. 18. For example, modules may be stored in memory 1105 of FIG. 11 that provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1103, processing circuitry 1103 performs the respective operations of the flowchart.

[0092] In block 1901, the processing circuit 1103 may include a VAE client 104. , more New requirements or Server Information In block 1903, the processing circuit 1103 receives a session-oriented modification response from the client device (100) having the VAE client (104) indicating acceptance of the modification request.

[0093] In block 1905 , the processing circuit 1103 sends a session-oriented service change notification to the first server 112 .

[0094] Figure 25 illustrates the operation of Figure 5 from the perspective of VAE client 104. Referring to Figure 25, the operation of VAE client 104 (implemented using the structure of the block diagram of Figure 10) according to some embodiments of the inventive concepts in supporting session-oriented services will now be described with reference to the flowchart of Figure 25. For example, modules may be stored in memory 1005 of Figure 10, and these modules may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1003, the processing circuitry 1003 performs the respective operations of the flowchart.

[0095] At block 2501, the processing circuit 1003 receives a session-oriented service change request from the second server 114. At block 2503, the processing circuit 1003 sends a session-oriented service change notification to the second server (114) indicating acceptance of the session-oriented service change request. At block 2505, the processing circuit 1003 provides the session-oriented service change notification to the V2X application-specific client 102.

[0096] 6 , in some embodiments of the inventive concept, session-oriented service updates are triggered from the VAE client 104. For example, this may be the case when the V2X application-specific client 102 is responsible for performing service adaptation. One example is when the V2X application-specific client 102 triggers service adaptation in reaction to receiving QoS notifications or network information, which may have been provided either from the V2X application-specific server 112 (when received from the VAE server 114) or directly from the VAE server 114 through the VAE client 104.

[0097] The procedure for updating a session-oriented service triggered by a VAE client is that the VAE client 104 receives a session-oriented change trigger request from the V2X application-specific client 102.

[0098] In operation 1, the VAE client 104 sends service information updates (e.g., activated services, vehicle trajectory updates, etc.), requirements, etc. to one or more VAE servers 114. Update (e.g., changes in network / QoS requirements), or server information UpdateThe VAE server 114 sends a session-oriented change request including the session-oriented change request (e.g., change of VAE server). The VAE server 114 inspects the received session-oriented change request and, in operation 2, sends a session-oriented change response to the VAE client 104 indicating acceptance of the session-oriented change request received from the VAE client 104. The VAE server 114 sends a session-oriented service change notification to the V2X application-specific server 112 in operation 3. The VAE client 104 sends a session-oriented service change notification to the V2X application-specific client 102 in operation 4.

[0099] 20 illustrates operations for updating a session-oriented service triggered by a VAE client from the perspective of the VAE server 114. Referring to FIG. 20, operations of the second server 114 (implemented using the structure of the block diagram of FIG. 11) according to some embodiments of the inventive concept in supporting a session-oriented service will now be described with reference to the flowchart of FIG. 20. For example, modules may be stored in the memory 1105 of FIG. 11 that provide instructions such that, when the instructions of the modules are executed by the respective communication device processing circuitry 1103, the processing circuitry 1103 performs the respective operations of the flowchart.

[0100] In block 2001, the processing circuit 1103 receives a session-oriented service change request from a client device 100 having a VAE client 104, the session-oriented service change request including one or more updates to service information or changes in server information.

[0101] In block 2003, the processing circuit 1103 sends a session-oriented service change response indicating acceptance of the session-oriented service change request to the client device 100 having the VAE client 104. In block 2005, the processing circuit 1103 sends a session-oriented service change notification to the first server 112.

[0102] 26 illustrates operations for updating a session-oriented service triggered by a VAE client 104 from the perspective of the VAE client 104. Referring to FIG. 26, operations of a VAE client 104 (implemented using the structure of the block diagram of FIG. 10) according to some embodiments of the inventive concept in supporting a session-oriented service will now be described with reference to the flowchart of FIG. 26. For example, modules may be stored in memory 1005 of FIG. 10, and these modules may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1003, the processing circuitry 1003 performs the respective operations of the flowchart.

[0103] In block 2601, the processing circuit 1003 sends a session-oriented service change request to the second server (114), where the session-oriented service change request includes one or more updates to service information or changes in server information. In block 2603, the processing circuit 1103 receives a session-oriented service change response from the second server 114 indicating acceptance of the session-oriented service change request.

[0104] A procedure for triggering a session-oriented service termination request from the V2X application-specific server 112 to the VAE server 114 is now described. The VAE server 114 has established a session-oriented service with the VAE client 1014 as described above, and the V2X application-specific server 114 has decided to terminate the session-oriented service. The decision to terminate the session-oriented service may be based on a request from the V2X application-specific client 102 or a local decision by the V2X application-specific server 112.

[0105] Referring to FIG. 7, in operation 1, the V2X application-specific server 1121 provides the VAE server 114 with a session-oriented termination trigger request to terminate a session-oriented service with the VAE client 104.

[0106] In operation 2, the VAE server 114 sends a session-oriented service termination trigger response to the V2X application-specific server 112 that the session may be terminated.

[0107] Figure 15 illustrates the operation of Figure 6 from the perspective of a V2X application-specific server 112, designated as the first server 112. With reference to Figure 15, operation of the first server 112 (implemented using the structure of the block diagram of Figure 12) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of Figure 15. For example, modules may be stored in the memory 1205 of Figure 12 that may provide instructions such that, when the instructions of the modules are executed by the respective communications device processing circuitry 1203, the processing circuitry 1203 performs the respective operations of the flowchart.

[0108] In block 1501, the processing circuit 1203 sends a session-oriented service termination trigger request to terminate the session-oriented service to the second server 114. In block 1503, the processing circuit 1203 receives a session-oriented service termination trigger response from the second server 114. In block 1505, the processing circuit 1203 receives a session-oriented service termination notification from the second server 114. The notification is received after the session-oriented service is terminated.

[0109] Figure 21 illustrates the operation of Figure 7 from the perspective of the VAE server 114. Referring to Figure 21, the operation of the second server 114 (implemented using the structure of the block diagram of Figure 11) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of Figure 21. For example, modules may be stored in the memory 1105 of Figure 11 that may provide instructions such that, when the instructions of the modules are executed by the respective communication device processing circuitry 1103, the processing circuitry 1103 performs the respective operations of the flowchart.

[0110] At block 2101, the processing circuit 1103 receives a session-oriented service termination trigger request to terminate the session-oriented service from the first server 112. At operation 2103, the processing circuit 1103 sends a session-oriented service termination trigger response to the first server 112. At operation 2105, the processing circuit 1103 sends a session-oriented service termination notification to the first server 112. The notification is sent after the session-oriented service is terminated.

[0111] 8, a procedure for terminating a session-oriented service between the VAE server 114 and the VAE client 104 will now be described. In operation 1, the VAE server 114 sends a session-oriented termination request to the VAE client 104 to terminate the session (e.g., end of a session with the VAE server or requirements for a session-oriented service that are not met).

[0112] In operation 2, the VAE client 104 sends a session-oriented termination response to the VAE server 114 indicating acceptance of the session-oriented termination request sent by the VAE server 114.

[0113] In operation 3, the VAE server 114 sends a session-oriented service termination notification to the V2X application specific server 114.

[0114] In operation 4, the VAE client 104 sends a session-oriented service termination notification to the V2X application-specific client 102.

[0115] Figure 22 illustrates the operation of Figure 8 from the perspective of the VAE server 114. Referring to Figure 22, the operation of the second server 114 (implemented using the structure of the block diagram of Figure 11) according to some embodiments of the inventive concept in supporting session-oriented services will now be described with reference to the flowchart of Figure 22. For example, modules may be stored in memory 1105 of Figure 11 that provide instructions such that, when the instructions of the modules are executed by the respective communication device processing circuitry 1103, the processing circuitry 1103 performs the respective operations of the flowchart.

[0116] In block 2201, the processing circuit 1103 sends a session-oriented service termination request to the client device 100 having the VAE client 104.

[0117] In block 2203, the processing circuit 1103 receives a session-oriented service termination response indicating acceptance of the session termination request from the client device 100 having the VAE client 104. In block 2205, the processing circuit 1103 sends a session-oriented service termination notification to the first server 112.

[0118] Figure 27 illustrates the operation of Figure 8 from the perspective of VAE client 104. Referring to Figure 27, the operation of VAE client 104 (implemented using the structure of the block diagram of Figure 10) according to some embodiments of the inventive concepts in supporting session-oriented services will now be described with reference to the flowchart of Figure 27. For example, modules may be stored in memory 1005 of Figure 19, and these modules may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1003, the processing circuitry 1003 performs the respective operations of the flowchart.

[0119] At block 2701, the processing circuit 1003 receives a session-oriented service termination request from the second server 114. At block 2703, the processing circuit 1003 sends a session-oriented service termination response indicating approval of the session-oriented service termination request to the second server 114. At block 2705, the processing circuit 1003 provides a session-oriented service termination notification to the V2X application-specific client 102.

[0120] 9 , in various other embodiments of the inventive concept, the procedure for terminating a session-oriented service is triggered from the VAE client 104. For example, this may be when the V2X application-specific client 102 is responsible for performing service adaptation. One example of this is when the V2X application-specific client 102 terminates the service (e.g., the vehicle arrives at its final destination). Another example is when the V2X application-specific client 102 triggers the termination of the session-oriented service in reaction to receiving a QoS notification or network information, for example, if the QoS notification or network information indicates that the network can no longer meet any of the service requirements associated with the service. The QoS notification or network information may have been provided either from the V2X application-specific server 112 (upon receipt from the VAE server 114) or directly from the VAE server 114 through the VAE client 104.

[0121] The procedure for terminating a session-oriented service triggered by the VAE client 104 responds to the VAE client 104 receiving a session-oriented termination trigger request from the V2X application-specific client 102, for example, due to the end of a session with the VAE server 114, the end of a V2X service, or receipt of a QoS notification indicating that requirements for the session-oriented service are not met.

[0122] In operation 1, the VAE client 102 sends a session-oriented termination request to the VAE server 114 to terminate the session (eg, end of a session with the VAE server or requirements for a session-oriented service that are not met).

[0123] In operation 2, the VAE server 114 sends a session-oriented termination response to the VAE client 104 indicating acceptance of the session-oriented termination request sent by the VAE client.

[0124] In operation 3, the VAE server 114 sends a session-oriented termination notification to the V2X application-specific server 112.

[0125] In operation 4, the VAE client 104 sends a session-oriented termination notification to the V2X application-specific client 102.

[0126] 23 illustrates the operation of terminating a session-oriented service triggered by a VAE client 104 from the perspective of the VAE server 114. Referring to FIG. 23, the operation of the second server 114 (implemented using the structure of the block diagram of FIG. 11) according to some embodiments of the inventive concept in supporting a session-oriented service will now be described with reference to the flowchart of FIG. 23. For example, modules may be stored in the memory 1105 of FIG. 11 that provide instructions such that, when the instructions of the modules are executed by the respective communication device processing circuitry 1103, the processing circuitry 1103 performs the respective operations of the flowchart.

[0127] In block 2301, the processing circuit 1103 receives a session-oriented service termination request to terminate a session-oriented service from the client device 100 having the VAE client 104. In block 2303, the processing circuit 1103 sends a session-oriented service termination response indicating acceptance of the session termination request to the client device 100 having the VAE client 104. In block 2305, the processing circuit 1103 sends a session-oriented service termination notification to the first server 112.

[0128] Figure 28 illustrates the operation of Figure 7 from the perspective of VAE client 104. Referring to Figure 28, the operation of VAE client 104 (implemented using the structure of the block diagram of Figure 10) according to some embodiments of the inventive concepts in supporting session-oriented services will now be described with reference to the flowchart of Figure 28. For example, modules may be stored in memory 1005 of Figure 10, and these modules may provide instructions such that, when the instructions of the modules are executed by respective communication device processing circuitry 1003, the processing circuitry 1003 performs the respective operations of the flowchart.

[0129] At block 2801, the processing circuit 1003 sends a session-oriented service termination request to the second server 114. At block 2803, the processing circuit 1003 receives a session-oriented service termination response from the second server 114 indicating approval of the session-oriented service termination request. In some embodiments, the session-oriented service termination request is sent in response to receiving a termination request from the V2X application-specific client 102.

[0130] Exemplary embodiments are described below. Embodiment Embodiment 1. A method implemented by a first server (112) for supporting session-oriented services for vehicles, the method comprising: Sending (1301) a session-oriented service trigger request to a second server (114) to initiate a session-oriented service for a client device (104); receiving (1303) a session-oriented service trigger response from the second server (114), the session-oriented service trigger response indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104); A method comprising: Embodiment 2. The method of embodiment 1, wherein the first server is a V2X (Vehicle to Everything) application specific server and the second server is a V2X Application Enabler (VAE) server. Embodiment 3. The method of embodiment 1 or 2, wherein sending a session-oriented service trigger request includes sending a session-oriented service trigger request along with information associated with the session-oriented service. Embodiment 4. The method of embodiment 3, wherein the information includes one or more of identification information of the client device (104), identification information of the first server (112), identification information of the service session, and a type or quality of service (QoS) requirement of the session-oriented service. Embodiment 5. The information relating to the type or QoS requirements includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes: Primary and alternative service requirements ordered in a prioritized manner; An indication of whether notification control is required in case of QoS failure / re-enforcement; an indication of whether QoS sustainability analysis information is required; and User Equipment (UE) measurement information and 5. The method of embodiment 4, comprising one or more of: Embodiment 6. When QoS sustainability analysis information is required, the information is: Key performance indicators (KPIs) to be considered to generate a QoS sustainability analysis; thresholds for triggering notifications regarding QoS sustainability analysis; Advance time and time to trigger notifications for QoS sustainability analysis 6. The method of embodiment 5, further comprising one or more of: Embodiment 7. receiving (1305) a session-oriented service establishment notification from the second server (114) indicating that the session-oriented service has been established; 7. The method of any one of embodiments 1 to 6, further comprising: Embodiment 8. Sending (1401) a session-oriented service change trigger request to a second server (114), the session-oriented service change request including one or more updates to service information or changes in server information; receiving (1403) a session-oriented service change trigger response from the second server (114), the response indicating whether the second server (114) can continue the session-oriented service with the updated session parameters; 8. The method of any one of embodiments 1 to 7, further comprising: Embodiment 9. Receiving a session-oriented service change notification from the second server (114) (1405). 9. The method of embodiment 8, further comprising: Embodiment 10. Sending (1501) a session-oriented service termination trigger request to a second server (114) for terminating a session-oriented service; receiving (1503) a session-oriented service termination trigger response from the second server (114); 8. The method of any one of embodiments 1 to 7, further comprising: Embodiment 11. Receiving a session-oriented service termination notification from the second server (114) (1505). 11. The method of embodiment 10, further comprising: Embodiment 12. A first server (112), Sending (1301) a session-oriented service trigger request to a second server (114) to initiate a session-oriented service for a client device (104); receiving (1303) a session-oriented service trigger response from the second server (114), the session-oriented service trigger response indicating whether the second server (114) will initiate a session-oriented service with the client device (104); a first server (112) adapted to perform operations including: Embodiment 13. The first server (112) according to embodiment 12, wherein the first server (112) is adapted to perform the operations according to any one of embodiments 2 to 11. Embodiment 14. A first server (112), A processing circuit (1203); a memory (1205) coupled to the processing circuit, the memory, when executed by the processing circuit, causing the first server (112) to: Sending (1301) a session-oriented service trigger request to a second server (114) to initiate a session-oriented service for a client device (104); receiving (1303) a session-oriented service trigger response from the second server (114), the session-oriented service trigger response indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104); a first server (112) including instructions to perform operations including: Embodiment 15. The first server (112) of embodiment 14, wherein the first server is a V2X (Vehicle to Everything) application specific server and the second server is a V2X Application Enabler (VAE) server. Embodiment 16. The first server (112) of embodiment 14 or 15, wherein the memory includes further instructions that, when executed by the processing circuit (1203), cause the first server (112) to perform an operation including sending a session-oriented service trigger request along with information associated with the session-oriented service, in sending a session-oriented service trigger request. Embodiment 17. The first server (112) of embodiment 16, wherein the information includes one or more of: identification information of the client device (104); identification information of the first server (112); identification information of the service session; and the type or quality of service (QoS) requirements of the session-oriented service. Embodiment 18. The information relating to the type or QoS requirements includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes: Primary and alternative service requirements ordered in a prioritized manner; An indication of whether notification control is required in case of QoS failure / re-enforcement; an indication of whether QoS sustainability analysis information is required; and User Equipment (UE) measurement information and 18. The first server (112) of embodiment 17, comprising one or more of: Embodiment 19. When QoS sustainability analysis information is required, the information is: Key performance indicators (KPIs) to be considered to generate a QoS sustainability analysis; thresholds for triggering notifications regarding QoS sustainability analysis; Advance time and time to trigger notifications for QoS sustainability analysis 18. The first server (112) of embodiment 17, further comprising one or more of: Embodiment 20. The memory, when executed by the processing circuit (1203), causes the first server (112): receiving (1305) a session-oriented service establishment notification from the second server (114) indicating that the session-oriented service has been established; 20. The first server (112) of any one of embodiments 14 to 19, further comprising instructions for performing operations including: Embodiment 21. Sending (1401) a session-oriented service change trigger request to a second server (114), the session-oriented service change request including one or more updates to service information or changes in server information; receiving (1403) a session-oriented service change trigger response from the second server (114), the response indicating whether the second server (114) can continue the session-oriented service with the updated session parameters; 21. The first server (112) of any one of embodiments 14 to 20, further comprising: Embodiment 22. The memory, when executed by the processing circuit (1203), causes the first server (112): Receiving a session-oriented service change notification from the second server (114) (1405). 22. The first server (112) of embodiment 21, further comprising instructions for performing operations including: Embodiment 23. The memory, when executed by the processing circuit (1203), causes the first server (112): Sending (1501) a session-oriented service termination trigger request to a second server (114) for terminating a session-oriented service; receiving (1503) a session-oriented service termination trigger response from the second server (114); 21. The first server (112) of any one of embodiments 14 to 20, further comprising instructions for performing operations including: Embodiment 24. The memory, when executed by the processing circuit (1203), causes the first server (112): Receiving a session-oriented service termination notification from the second server (114) (1505). 24. The first server (112) of embodiment 23, further comprising instructions for performing operations including: Embodiment 25. A computer program comprising program code to be executed by a processing circuit (1203) of a first server (112), whereby execution of the program code causes the first server (112) to perform the operations described in any one of embodiments 1 to 11. Embodiment 26. A computer program product comprising a non-transitory storage medium containing program code to be executed by a processing circuit (1203) of a first server (112), whereby execution of the program code causes the first server (112) to perform the operations described in any one of embodiments 1 to 11. Embodiment 27. A method implemented by a second server (114) communicatively coupled to a network (108) for supporting session-oriented services for a vehicle, the method comprising: Receiving (1601) a session-oriented service trigger request from a first server (112) to initiate a session-oriented service for a client device (104); sending (1603) a session-oriented service trigger response to the first server (112), indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104); A method comprising: Embodiment 28. The method of embodiment 27, wherein the first server is a V2X (Vehicle to Everything) application-specific server and the second server is a V2X Application Enabler (VAE) server.

[0072] Embodiment 29. The method of embodiment 27 or 28, wherein receiving a session-oriented service trigger request includes receiving a session-oriented service trigger request along with information associated with the session-oriented service. Embodiment 30. The method of embodiment 29, wherein the information includes one or more of identification information of the client device (104), identification information of the first server (112), identification information of the service session, and a type or quality of service (QoS) requirement of the session-oriented service. The information relating to the type or QoS requirements includes information about how many flows are associated with the session-oriented service, and for each flow, the information is: Primary and alternative service requirements ordered in a prioritized manner; An indication of whether notification control is required in case of QoS failure / re-enforcement; an indication of whether QoS sustainability analysis information is required; and User Equipment (UE) measurement information and 31. The method of embodiment 30, comprising one or more of: Embodiment 32. When QoS sustainability analysis information is required, the information is: Key performance indicators (KPIs) to be considered to generate a QoS sustainability analysis; thresholds for triggering notifications regarding QoS sustainability analysis; Advance time and time to trigger notifications for QoS sustainability analysis 32. The method of embodiment 31, further comprising one or more of: Embodiment 33. Sending a session-oriented service establishment notification to the first server (112) indicating that the session-oriented service has been established (1605). 33. The method of any one of embodiments 27 to 32, further comprising: Embodiment 34. Sending a session-oriented service request (1701) to a client device (100) having a VAE client (104) to establish a session-oriented service, the session-oriented service request including identification information of the VAE client (104), identification information of the session, and a reporting setting; receiving (1703) a session-oriented service response from a client device (100) having a VAE client (104) indicating acceptance of the session-oriented service request to establish the session-oriented service; In response to receiving the session-oriented service response indicating acceptance, sending (1705) a session-oriented service establishment notification to the first server (112); 34. The method of any one of embodiments 27 to 33, further comprising: Embodiment 35. receiving (1801) a session-oriented service change trigger request from a first server (112), the session-oriented service change trigger request including an identification of the session-oriented service and updated session parameters; In response to determining that the session-oriented service can be provided with the updated session parameters, sending (1803) to the first server (112) a session-oriented service change trigger response indicating an ability to continue the session-oriented service with the updated session parameters; In response to determining that the session-oriented service cannot be provided with the updated session parameters, sending (1805) a session-oriented service change trigger response to the first server (112) indicating that the second server (114) cannot continue the session-oriented service with the updated session parameters; 35. The method of embodiment 34, further comprising: Embodiment 36. Sending a session-oriented change request (1901) to a client device (100) having a VAE client (104), the change request including an update requirement or change to server information; receiving (1903) a session-oriented modification response from a client device (100) having a VAE client (104) indicating acceptance of the modification request; Sending (1905) a session-oriented service change notification to the first server (112); 36. The method of embodiment 35, further comprising: Embodiment 37. receiving a session-oriented service change request from a client device having a VAE client, the session-oriented service change request including one or more updates to service information or changes in server information; Sending (2003) a session-oriented service change response to a client device (100) having a VAE client (104) instructing the client device to accept the session-oriented service change request; Sending (2005) a session-oriented service change notification to the first server (112); 35. The method of embodiment 34, further comprising: Embodiment 38. Receiving (2101) a session-oriented service termination trigger request from the first server (112) to terminate a session-oriented service from the first server (112); Sending (2103) a session-oriented service termination trigger response to the first server (112); Sending (2105) a session-oriented service termination notification to the first server (112); 35. The method of embodiment 34, further comprising: Embodiment 39. Sending (2201) a session-oriented service termination request to a client device (100) having a VAE client (104); receiving (2203) a session-oriented service termination response indicating acceptance of the session termination request from a client device (100) having a VAE client (104); 39. The method of embodiment 38, further comprising: Embodiment 40. receiving (2301) a session-oriented service termination request for terminating a session-oriented service from a client device (100) having a VAE client (104); Sending (2303) a session-oriented service termination response to a client device (100) having a VAE client (104) instructing the client device to accept the session termination request; Sending (2305) a session-oriented service termination notification to the first server (112); 35. The method of embodiment 34, further comprising: Embodiment 41. A second server (114), Receiving (1601) a session-oriented service trigger request from a first server (112) to initiate a session-oriented service for a client device (104); sending (1603) a session-oriented service trigger response to the first server (112) indicating whether the second server (114) has the capability for session-oriented services with the client device (104); a second server (114) adapted to perform operations including: Embodiment 42. The second server (114) of embodiment 41, wherein the first server (112) is adapted to perform the operations of any one of embodiments 28 to 40. Embodiment 43. A second server (114), A processing circuit (1103); a memory (1105) coupled to the processing circuit, the memory, when executed by the processing circuit, causing the second server (114) to: Receiving (1601) a session-oriented service trigger request from a first server (112) to initiate a session-oriented service for a client device (104); sending (1603) a session-oriented service trigger response to the first server (112), indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104); a second server (114) including instructions to perform operations including: Embodiment 44. The second server (114) of embodiment 43, wherein the first server is a V2X (Vehicle to Everything) application specific server and the second server is a V2X Application Enabler (VAE) server. Embodiment 45. The second server (114) of embodiment 43 or 44, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform an operation including receiving a session-oriented service trigger request along with information associated with the session-oriented service, in receiving a session-oriented service trigger request. Embodiment 46. The second server (114) of embodiment 45, wherein the information includes one or more of: identification information of the client device (104), identification information of the first server (112), identification information of the service session, and the type or quality of service (QoS) requirements of the session-oriented service. Embodiment 47. The information relating to the type or QoS requirements includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes: Primary and alternative service requirements ordered in a prioritized manner; An indication of whether notification control is required in case of QoS failure / re-enforcement; an indication of whether QoS sustainability analysis information is required; and User Equipment (UE) measurement information and 47. The second server (114) of embodiment 46, comprising one or more of: Embodiment 48. When QoS sustainability analysis information is required, the information is: Key performance indicators (KPIs) to be considered to generate a QoS sustainability analysis; thresholds for triggering notifications regarding QoS sustainability analysis; Advance time and time to trigger notifications for QoS sustainability analysis 48. The second server (114) of embodiment 47, further comprising one or more of: Embodiment 49. The memory, when executed by the processing circuit, causes the second server (114): Sending a session-oriented service establishment notification to the first server (112) indicating that the session-oriented service has been established (1605). 49. The second server (114) of any one of embodiments 43 to 48, further comprising instructions for performing operations including: Embodiment 50. The memory, when executed by the processing circuit, causes the second server (114): Sending a session-oriented service request (1701) to a client device (100) having a VAE client (104) to establish a session-oriented service, the session-oriented service request including identification information of the VAE client (104), identification information of the session, and a reporting setting; receiving (1703) a session-oriented service response from a client device (100) having a VAE client (104) indicating acceptance of the session-oriented service request to establish the session-oriented service; In response to receiving the session-oriented service response indicating acceptance, sending (1705) a session-oriented service establishment notification to the first server (112); 48. The second server (114) of any one of embodiments 43 to 47, further comprising instructions for performing further operations including: Embodiment 51. The memory, when executed by the processing circuit, causes the second server (114): receiving (1801) a session-oriented service change trigger request from a first server (112), the session-oriented service change trigger request including an identification of the session-oriented service and updated session parameters; In response to determining that the session-oriented service can be provided with the updated session parameters, sending (1901) to the first server (112) a session-oriented service change trigger response indicating an ability to continue the session-oriented service with the updated session parameters; In response to determining that the session-oriented service cannot be provided with the updated session parameters, sending (1903) a session-oriented service change trigger response to the first server (112) indicating that the second server (114) cannot continue the session-oriented service with the updated session parameters; 51. The second server (114) of embodiment 50, further comprising instructions for performing further operations including: Embodiment 52. The memory, when executed by the processing circuit, causes the second server (114): A client device (100) having a VAE client (104) , more New requirements or Server Information submitting a change request containing the changes (1901); receiving (1903) a change response from a client device (100) having a VAE client (104) indicating acceptance of the change request; sending a session-oriented service change notification to the first server (112); 52. The second server (114) of embodiment 51, further comprising instructions for performing further operations including: Embodiment 53. The memory, when executed by the processing circuit, causes the second server (114): receiving a session-oriented service change request from a client device having a VAE client, the session-oriented service change request including one or more updates to service information or changes in server information; Sending (2003) a change response to a client device (100) having a VAE client (104) indicating acceptance of the session-oriented service change request; Sending (2005) a session-oriented service change notification to the first server (112); 51. The second server (114) of embodiment 50, further comprising instructions for performing further operations including: Embodiment 54. The memory, when executed by the processing circuit, causes the second server (114): Receiving (2101) a session-oriented service termination trigger request for terminating a session-oriented service from a first server (112); Sending (2103) a session-oriented service termination trigger response to the first server (112); 51. The second server (114) of embodiment 50, further comprising instructions for performing further operations including: Embodiment 55. The memory, when executed by the processing circuit, causes the second server (114): Sending a session termination request (2201) to a client device (100) having a VAE client (104); receiving (2203) a session termination response indicating acceptance of the session termination request from a client device (100) having a VAE client (104); Sending (2205) a session-oriented service termination notification to the first server (112); 55. The second server (114) of embodiment 54, further comprising instructions for performing further operations including: Embodiment 55. The memory, when executed by the processing circuit, causes the second server (114): receiving (2301) a session-oriented service termination request for terminating a session-oriented service from a client device (100) having a VAE client (104); Sending (2303) a session-oriented service termination response to a client device (100) having a VAE client (104) instructing the client device to accept the session-oriented service termination request; Sending (2305) a session-oriented service termination notification to the first server (112); 54. The second server (114) of any one of embodiments 50 to 53, further comprising instructions for performing further operations including: Embodiment 56. A computer program comprising program code to be executed by a processing circuit (1103) of a second server (114), whereby execution of the program code causes the second server (114) to perform the operations described in any one of embodiments 27 to 40. Embodiment 57. A computer program product comprising a non-transitory storage medium containing program code to be executed by a processing circuit (1103) of a second server (114), whereby execution of the program code causes the second server (114) to perform the operations described in any one of embodiments 27 to 40. Embodiment 58. A method implemented by a V2X (Vehicle to Everything) Application Enabler (VAE) client (104) of a computing device (100), the method comprising: Receiving a session-oriented service request from a second server, the session-oriented service request including an identification of the VAE client, an identification of the session, and a reporting setting; Sending (2403) a session-oriented service response to the second server (114) indicating acceptance of the session-oriented service request; providing (2405) a session-oriented service establishment notification to a V2X application-specific client (102); A method comprising: Embodiment 59. receiving (2501) a session-oriented service change request from a second server (114); Sending (2503) a session-oriented service change notification to the second server (114) instructing the second server (114) to accept the session-oriented service change request; providing session-oriented service change notifications (2505) to V2X application-specific clients (102); 59. The method of embodiment 58, further comprising: Embodiment 60. Sending (2601) a session-oriented service change request to a second server (114), the session-oriented service change request including one or more updates to service information or changes in server information; receiving (2603) a session-oriented service change response from the second server (114) indicating acceptance of the session-oriented service change request; 59. The method of embodiment 58, further comprising: Embodiment 61. Receiving a session-oriented service termination request (2701) from a second server (114); Sending (2703) a session-oriented service termination response to the second server (114) instructing the second server (114) to accept the session-oriented service termination request; Providing a session-oriented service termination notification to a V2X application-specific client (2705); 59. The method of embodiment 58, further comprising: Embodiment 62. Sending (2801) a session-oriented service termination request to a second server (114); receiving (2803) a session-oriented service termination response from the second server (114) indicating acceptance of the session-oriented service termination request; 61. The method of any one of embodiments 58 to 60, further comprising:

[0063] Embodiment 63. The method of embodiment 62, wherein sending a session-oriented service termination request includes sending a session-oriented service termination request in response to receiving a session-oriented service termination trigger request from the V2X application-specific client. Embodiment 64. A V2X (Vehicle-to-Everything) Application Enabler (VAE) client (104), Receiving a session-oriented service request from a second server, the session-oriented service request including an identification of the VAE client, an identification of the session, and a reporting setting; Sending (2403) a session-oriented service response to the second server (114) indicating approval of the session-oriented service request; Providing a session-oriented service establishment notification to a V2X application-specific client (2405); a Vehicle-to-Everything (V2X) Application Enabler (VAE) client (104) adapted to perform operations including: Embodiment 65. A VAE client (104) as described in embodiment 64, wherein the VAE client (104) is adapted to perform the operations described in any one of embodiments 59 to 63. Embodiment 66. A V2X (Vehicle-to-Everything) Application Enabler (VAE) client (104), comprising: A processing circuit (1003); a memory (1005) coupled to the processing circuit, the memory, when executed by the processing circuit, providing to the VAE client (104): Receiving a session-oriented service request from a second server, the session-oriented service request including an identification of the VAE client, an identification of the session, and a reporting setting; Sending (2403) a session-oriented service response to the second server (114) indicating approval of the session-oriented service request; Providing a session-oriented service establishment notification to a V2X application-specific client (2405); A Vehicle-to-Everything (V2X) Application Enabler (VAE) client (104) including instructions to perform operations including: Embodiment 67. The memory, when executed by the processing circuit, causes the VAE client (104): receiving (2501) a session-oriented modification request from a second server (114); Sending (2503) a session-oriented change notification to the second server (114) instructing the second server (114) to accept the session-oriented change request; providing session-oriented service change notifications (2505) to V2X application-specific clients (102); 67. The VAE client (104) of embodiment 66, further comprising instructions for performing further operations including: Embodiment 68. The memory, when executed by the processing circuit, causes the VAE client (104): Sending a session-oriented service change request (2601) to a second server (114), the session-oriented service update request including one or more updates to service information or changes in server information; receiving (2603) a change response from the second server (114) indicating acceptance of the session-oriented service change request; 67. The VAE client (104) of embodiment 66, further comprising instructions for performing further operations including: Embodiment 69. The memory, when executed by the processing circuit, causes the VAE client (104): Receiving a session-oriented service termination request (2701) from a second server (114); Sending (2703) a session-oriented service termination response to the second server (114) indicating approval of the session-oriented service termination request; Providing (2705) a session-oriented service termination notification to a V2X application-specific client (102); 67. The VAE client (104) of embodiment 66, further comprising instructions for performing further operations including: Embodiment 70. The memory, when executed by the processing circuit, causes the VAE client (104): Sending (2801) a session-oriented service termination request to a second server (114); receiving (2803) a session-oriented service termination response from the second server (114) indicating approval of the session-oriented service termination request; 67. The VAE client (104) of embodiment 66, further comprising instructions for performing further operations including: Embodiment 71. The VAE client (104) of embodiment 70, wherein sending the session-oriented service termination request includes sending the session-oriented service termination request in response to receiving a session-oriented termination trigger request from the V2X application-specific client (102). Embodiment 72. A computer program comprising program code to be executed by a processing circuit (1003) of a V2X (Vehicle-to-Everything) Application Enabler (VAE) client (104), whereby execution of the program code causes the VAE client (104) to perform the operations described in any one of embodiments 58 to 63. Embodiment 73. A computer program product comprising a non-transitory storage medium containing program code to be executed by a processing circuit (1003) of a V2X (Vehicle-to-Everything) Application Enabler (VAE) client (104), whereby execution of the program code causes the VAE client (104) to perform the operations described in any one of embodiments 58 to 63. Explanations of various abbreviations / acronyms used in this disclosure are provided below. Abbreviation Description 3GPP 3rd Generation Partnership Project 5G (5th Generation) gNB NR base station ITS Intelligent Transport Systems ITS-S ITS base KPI Key Performance Indicator NR new radio QoS Quality of Service RAN Radio Access Network RAT Radio Access Technology RD Remote Operation SEAL Service-Enabled Architecture Layer TeSo Remote Control Support ToD Remote Control Operation VAE V2X Application Enabler VAL Vertical Application Layer V2N Vehicle to Network V2X Vehicle to Everything V2X AS V2X Application Server V2X UE V2X user equipment UE User Equipment

[0131] References are identified below. 1. 3GPP TS23.286, Application Layer Support for V2X Services; Functional Architecture and Information Flow, V16.1.0, 06-2019. 2. 3GPP TS23.434, Service Enabler Architecture Layer for Verticals; Functional Architecture and Information Flows, V16.1.0, 06-2019. 3. 3GPP TR23.795, Study on Application Layer Support for V2X Services, V16.0.0, September 2018. 4. 3GPP TR23.764, Study on Extending Application Layer Support for V2X Services, V0.5.0, February 2020. 5. 3GPP TR22.886, Study on Extending 3GPP Support for 5G V2X Services, V16.2.0, December 2018. 6. 3GPP TS22.186, Service Requirements for Extended V2X Scenarios, V16.2.0, June 2019. 7. 5GAA T-190028, 5G Automotive Association; Working Group Use Cases and Technical Requirements; 5G Use Cases and Requirements - Wave 2.1; V1.0 (January 30, 2019) 8. 5GAA XWG5-190009 Work Item Description, Requirements and Architecture for Teleoperated Operation

[0132] Further explanation is provided below.

[0133] In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is expressly given and / or implied from the context in which the term is used. All references to an element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or if it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Similarly, any advantage of any of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0134] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein; rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0135] FIG. 29 illustrates a wireless network according to some embodiments.

[0136] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with reference to a wireless network, such as the exemplary wireless network shown in FIG. 29. For simplicity, the wireless network of FIG. 29 illustrates only network 4106, network nodes 4160 and 4160b (also referred to herein as V2X servers), and WDs 4110, 4110b, and 4110c (also referred to herein as mobile terminals, user equipment, V2X user equipment, etc.). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the components shown, network node 4160 and wireless device (WD) 4110 are illustrated with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate their access to the wireless network and / or use of services offered by or via the wireless network.

[0137] A wireless network may comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network, or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Accordingly, particular embodiments of a wireless network may implement communications standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Vehicle to Everything (V2X), and / or other suitable 2G, 3G, 4G, or 5G standards, wireless local area network (WLAN) standards such as the IEEE 802.11 standard, and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0138] The network 4106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks for enabling communication between devices.

[0139] The network node 4160 and the WD 4110 comprise various components, which are described in more detail below. These components cooperate to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0140] As used herein, a network node refers to a device capable of, set up, configured, and / or operable to communicate directly or indirectly with wireless devices and / or other network nodes or devices in a wireless network to enable and / or provide wireless access to wireless devices and / or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), V2X servers (e.g., V2X application-specific servers, V2X application enabler servers), and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated another way, their transmit power level), and may then be referred to as femto, pico, micro, or macro base stations. A base station may control a relay, or a relay donor node. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. Portions of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Still further examples of network nodes include multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), a V2X server node, and / or an MDT.As another example, a network node may be a virtual network node, as described in more detail below. More generally, however, a network node may represent any suitable device (or group of devices) capable of, configured to, and / or operable to enable and / or provide wireless devices with access to a wireless network or to provide some service to wireless devices that have accessed the wireless network.

[0141] In FIG. 29 , the network node 4160 includes a processing circuit 4170, a device-readable medium 4180, an interface 4190, auxiliary equipment 4184, a power source 4186, a power circuit 4187, and an antenna 4162. While the network node 4160 shown in the example wireless network of FIG. 29 may represent a device including the shown combination of hardware components, other embodiments may comprise a network node with a different combination of components. It should be understood that a network node comprises any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, while the components of the network node 4160 are illustrated as a single box located within a larger box or as a single box nested within multiple boxes, in reality the network node may comprise multiple different physical components that make up the single depicted component (e.g., the device-readable medium 4180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0142] Similarly, the network node 4160 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In some scenarios in which the network node 4160 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may, in some instances, be considered a single separate network node. In some embodiments, the network node 4160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 4180 for different RATs) and some components may be reused (e.g., the same antenna 4162 may be shared by the RATs). The network node 4160 may also include multiple sets of the various shown components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into the network node 4160. These wireless technologies may be integrated into the same or different chips or sets of chips and other components within the network node 4160.

[0143] The processing circuit 4170 is configured to perform any decision, computation, or similar operations (e.g., some acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuit 4170 may include processing information acquired by the processing circuit 4170, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making a decision.

[0144] The processing circuit 4170 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide network node 4160 functionality, either alone or in conjunction with other network node 4160 components, such as device readable medium 4180. For example, the processing circuit 4170 may execute instructions stored on the device readable medium 4180 or in memory within the processing circuit 4170. Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, the processing circuit 4170 may include a system on a chip (SOC).

[0145] In some embodiments, the processing circuit 4170 may include one or more of a radio frequency (RF) transceiver circuit 4172 and a baseband processing circuit 4174. In some embodiments, the radio frequency (RF) transceiver circuit 4172 and the baseband processing circuit 4174 may be on separate chips (or sets of chips), boards, or units such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 4172 and the baseband processing circuit 4174 may be on the same chip or set of chips, board, or unit.

[0146] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 4170 executing instructions stored on a device-readable medium 4180, or on a memory within the processing circuitry 4170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 4170 without executing instructions stored on a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 4170 may be configured to perform the described functionality, regardless of whether or not it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are enjoyed by the network node 4160 as a whole, and / or by end users and the wireless network generally, and not by the processing circuitry 4170 alone or by other components of the network node 4160.

[0147] The device-readable medium 4180 may comprise any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuit 4170. The device-readable medium 4180 may store any suitable instructions, data, or information, including applications including one or more of computer programs, software, logic, rules, code, tables, etc., and / or other instructions that can be executed by the processing circuit 4170 and utilized by the network node 4160. The device-readable medium 4180 may be used to store calculations performed by the processing circuit 4170 and / or data received via the interface 4190. In some embodiments, the processing circuit 4170 and the device-readable medium 4180 may be considered to be integrated.

[0148] The interface 4190 is used in wired or wireless communication of signaling and / or data between the network node 4160, the network 4106, and / or the WD 4110. As shown, the interface 4190 comprises port(s) / terminal(s) 4194 for sending and receiving data to and from the network 4106, for example, over a wired connection. The interface 4190 also includes a radio front-end circuit 4192 that is coupled to the antenna 4162 or, in some embodiments, may be part of the antenna 4162. The radio front-end circuit 4192 comprises a filter 4198 and an amplifier 4196. The radio front-end circuit 4192 may be connected to the antenna 4162 and the processing circuit 4170. The radio front-end circuit 4192 may be configured to condition signals communicated between the antenna 4162 and the processing circuit 4170. The radio front-end circuit 4192 may receive digital data to be sent to another network node or WD via a wireless connection. The radio front-end circuit 4192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 4198 and / or amplifiers 4196. The radio signal may then be transmitted via the antenna 4162. Similarly, when receiving data, the antenna 4162 may collect the radio signal, which is then converted to digital data by the radio front-end circuit 4192. The digital data may be passed to the processing circuit 4170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0149] In some alternative embodiments, the network node 4160 may not include a separate radio front-end circuit 4192; instead, the processing circuit 4170 may comprise a radio front-end circuit and be connected to the antenna 4162 without a separate radio front-end circuit 4192. Similarly, in some embodiments, all or a portion of the RF transceiver circuit 4172 may be considered part of the interface 4190. In still other embodiments, the interface 4190 may include one or more ports or terminals 4194, the radio front-end circuit 4192, and the RF transceiver circuit 4172 as part of a radio unit (not shown), and the interface 4190 may communicate with a baseband processing circuit 4174 that is part of a digital unit (not shown).

[0150] The antenna 4162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. The antenna 4162 may be coupled to the radio front-end circuitry 4192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 4162 may comprise one or more omnidirectional, sector, or panel antennas operable to transmit / receive wireless signals, for example, between 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices within a specific area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively straight line. In some instances, the use of two or more antennas may be referred to as MIMO. In some embodiments, the antenna 4162 may be separate from the network node 4160 and connectable to the network node 4160 through an interface or port.

[0151] The antenna 4162, the interface 4190, and / or the processing circuit 4170 may be configured to perform any receiving operation and / or some obtaining or transmitting operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 4162, the interface 4190, and / or the processing circuit 4170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0152] The power circuit 4187 may comprise or be coupled to power management circuitry and is configured to supply power to the components of the network node 4160 for performing the functions described herein. The power circuit 4187 may receive power from a power source 4186. The power source 4186 and / or the power circuit 4187 may be configured to provide power to the various components of the network node 4160 in a form suitable for each component (e.g., at the voltage and current levels required for each respective component). The power source 4186 may either be included in the power circuit 4187 and / or the network node 4160 or may be external to the power circuit 4187 and / or the network node 4160. For example, the network node 4160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source supplies power to the power circuit 4187. As a further example, power supply 4186 may comprise a power source in the form of a battery or battery pack connected to or integrated in power circuit 4187. The battery may provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0153] 29 that may be responsible for providing some aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, the network node 4160 may include user interface devices to enable input of information into the network node 4160 and output of information from the network node 4160. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 4160.

[0154] As used herein, a wireless device (WD) refers to a device capable of, configured to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably with user equipment (UE) herein. Communicating wirelessly may involve transmitting and / or receiving radio signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEEs), laptop mounted equipment (LMEs), smart devices, wireless customer premises equipment (CPEs), in-vehicle wireless terminal devices, V2X application enabler clients, etc. A WD may support device-to-device (D2D) communications, e.g., by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), in which case it may be referred to as a D2D communications device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another WD and / or network node.The WD, in this case, may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in a 3GPP context. As one specific example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), and personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment capable of monitoring and / or reporting on its operational status or other functionality associated with its operation. The WD described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the WD described above may be mobile, in which case the device may be referred to as a mobile device or mobile terminal.

[0155] As shown, wireless device 4110 includes antenna 4111, interface 4114, processing circuitry 4120, device-readable medium 4130, user interface equipment 4132, auxiliary equipment 4134, power supply 4136, and power circuitry 4137. WD4110 may include multiple sets of one or more of the shown components for different wireless technologies supported by WD4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few. These wireless technologies may be integrated on the same or different chip or set of chips as other components within WD4110.

[0156] The antenna 4111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to the interface 4114. In some alternative embodiments, the antenna 4111 may be separate from the WD 4110 and connectable to the WD 4110 through an interface or port. The antenna 4111, the interface 4114, and / or the processing circuit 4120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuit and / or the antenna 4111 may be considered an interface.

[0157] As shown, the interface 4114 comprises a radio front-end circuit 4112 and an antenna 4111. The radio front-end circuit 4112 comprises one or more filters 4118 and an amplifier 4116. The radio front-end circuit 4112 is connected to the antenna 4111 and the processing circuit 4120 and is configured to condition signals communicated between the antenna 4111 and the processing circuit 4120. The radio front-end circuit 4112 may be coupled to or part of the antenna 4111. In some embodiments, the WD 4110 may not include a separate radio front-end circuit 4112; rather, the processing circuit 4120 may comprise the radio front-end circuit and be connected to the antenna 4111. Similarly, in some embodiments, some or all of the RF transceiver circuit 4122 may be considered part of the interface 4114. The radio front-end circuit 4112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 4112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 4118 and / or amplifiers 4116. The radio signal may then be transmitted via the antenna 4111. Similarly, when receiving data, the antenna 4111 may collect the radio signal, which is then converted to digital data by the radio front-end circuitry 4112. The digital data may be passed to the processing circuitry 4120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0158] The processing circuit 4120 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide WD4110 functionality, either alone or in conjunction with other WD4110 components, such as the device-readable medium 4130. Such functionality may include providing any of the various wireless features or benefits described herein. For example, the processing circuit 4120 may execute instructions stored on the device-readable medium 4130 or in memory within the processing circuit 4120 to provide the functionality disclosed herein.

[0159] As shown, the processing circuit 4120 includes one or more of an RF transceiver circuit 4122, a baseband processing circuit 4124, and an application processing circuit 4126. In other embodiments, the processing circuit may comprise different components and / or different combinations of components. In some embodiments, the processing circuit 4120 of the WD4110 may comprise a SOC. In some embodiments, the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126 may be on separate chips or sets of chips. In alternative embodiments, some or all of the baseband processing circuit 4124 and the application processing circuit 4126 may be combined into one chip or set of chips, and the RF transceiver circuit 4122 may be on a separate chip or set of chips. In yet further alternative embodiments, some or all of the RF transceiver circuit 4122 and the baseband processing circuit 4124 may be on the same chip or set of chips, and the application processing circuit 4126 may be on a separate chip or set of chips. In yet other alternative embodiments, some or all of the RF transceiver circuitry 4122, the baseband processing circuitry 4124, and the application processing circuitry 4126 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry 4122 may be part of the interface 4114. The RF transceiver circuitry 4122 may condition RF signals for the processing circuitry 4120.

[0160] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry 4120 executing instructions stored on a device-readable medium 4130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 4120 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuitry 4120 may be configured to perform the described functionality, regardless of whether it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are enjoyed by the WD4110 as a whole and / or by end users and wireless networks generally, and not limited to the processing circuitry 4120 alone or other components of the WD4110.

[0161] The processing circuit 4120 may be configured to perform any of the determination, calculation, or similar operations (e.g., some acquisition operations) described herein as being performed by a WD. These operations as performed by the processing circuit 4120 may include processing information acquired by the processing circuit 4120, for example, by converting the acquired information into other information, comparing the acquired or converted information with information stored by the WD 4110, and / or performing one or more operations based on the acquired or converted information and as a result of the processing making a decision.

[0162] The device-readable medium 4130 may be operable to store applications, including one or more of computer programs, software, logic, rules, codes, tables, etc., and / or other instructions that can be executed by the processing circuit 4120. The device-readable medium 4130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact discs (CDs) or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuit 4120. In some embodiments, the processing circuit 4120 and the device-readable medium 4130 may be considered to be integrated.

[0163] The user interface device 4132 may provide components that allow a human user to interact with the WD4110. Such interaction may be in many forms, such as visual, auditory, tactile, etc. The user interface device 4132 may be operable to produce output to the user and to allow the user to provide input to the WD4110. The type of interaction may vary depending on the type of user interface device 4132 installed on the WD4110. For example, if the WD4110 is a smartphone, interaction may be via a touchscreen; if the WD4110 is a smart meter, interaction may be through a screen that provides usage (e.g., number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 4132 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 4132 is configured to allow input of information to the WD4110 and is connected to the processing circuit 4120 to allow the processing circuit 4120 to process the input information. The user interface devices 4132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface devices 4132 are also configured to enable output of information from the WD4110 and to enable the processing circuit 4120 to output information from the WD4110. The user interface devices 4132 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface devices 4132, the WD4110 may communicate with end users and / or wireless networks, enabling the end users and / or wireless networks to benefit from the functionality described herein.

[0164] The auxiliary device 4134 is operable to provide more specific functionality that may not generally be performed by the WD. It may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 4134 may vary depending on the embodiment and / or scenario.

[0165] The power source 4136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or cells. The WD4110 may further comprise a power circuit 4137 for delivering power from the power source 4136 to various portions of the WD4110 that require power from the power source 4136 to perform any of the functions described or indicated herein. The power circuit 4137 may, in some embodiments, comprise a power management circuit. The power circuit 4137 may additionally or alternatively be operable to receive power from an external power source, in which case the WD4110 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface, such as a power cable. The power circuit 4137 may also, in some embodiments, be operable to deliver power from the external power source to the power source 4136. This may be, for example, for charging the power source 4136. The power circuitry 4137 may perform any formatting, converting, or other modification on the power from the power supply 4136 to make the power suitable for the respective component of the WD4110 being powered.

[0166] FIG. 30 illustrates a user equipment according to some embodiments.

[0167] FIG. 30 illustrates one embodiment of a UE in accordance with various aspects described herein. User equipment or UE, as used herein, does not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not initially be associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 42200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine-type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. The UE 4200 shown in Figure 30 is an example of a WD configured for communication according to one or more communications standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the 3GPP's GSM, UMTS, LTE, and / or 5G standards. As mentioned above, the terms WD and UE may be used interchangeably. Thus, while Figure 30 is a UE, the components described herein are equally applicable to a WD, and vice versa.

[0168] In FIG. 30, the UE 4200 includes a processing circuit 4201 operably coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connection interface 4211, memory 4215 including random access memory (RAM) 4217, read-only memory (ROM) 4219, and storage medium 4221, a communications subsystem 4231, a power source 4213, and / or other components, or any combination thereof. The storage medium 4221 includes an operating system 4223, application programs 4225, and data 4227. In other embodiments, the storage medium 4221 may include other similar types of information. Some UEs may utilize all of the components shown in FIG. 30 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0169] 30, processing circuit 4201 may be configured to process computer instructions and data. Processing circuit 4201 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, processing circuit 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0170] In the illustrated embodiment, the input / output interface 4205 may be configured to provide an input device, an output device, or a communication interface for an input / output device. The UE 4200 may be configured to use an output device via the input / output interface 4205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 4200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 4200 may be configured to use an input device via the input / output interface 4205 to allow a user to capture information on the UE 4200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor for detecting input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0171] In FIG. 30 , the RF interface 4209 may be configured to provide a communication interface to RF components, such as a transmitter, receiver, and antenna. The network connection interface 4211 may be configured to provide a communication interface to a network 4243a. The network 4243a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communications network, another similar network, or any combination thereof. For example, the network 4243a may comprise a Wi-Fi network. The network connection interface 4211 may be configured to include a receiver and transmitter interface used to communicate with one or more other devices over a communications network according to one or more communications protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 4211 may implement receiver and transmitter functionality appropriate for a communications network link (e.g., optical, electrical, etc.). The transmitter and receiver functionality may share circuit components, software, or firmware, or alternatively, may be implemented separately.

[0172] The RAM 4217 may be configured to interface to the processing circuit 4201 via the bus 4202 to provide storage or caching of data or computer instructions during the execution of software programs, such as an operating system, application programs, and device drivers. The ROM 4219 may be configured to provide computer instructions or data to the processing circuit 4201. For example, the ROM 4219 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. The storage medium 4221 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, the storage medium 4221 may be configured to include an operating system 4223, an application program 4225, such as a web browser application, a widget or gadget engine, or another application, and data files 4227. The storage medium 4221 may store any of a variety of different operating systems or combinations of operating systems for use by the UE 4200.

[0173] The storage medium 4221 may be configured to include several physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical disk drive, an internal hard disk drive, a Blu-ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM SDRAM, a smart card memory such as a subscriber identity module or removable user identity module (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 4221 may enable the UE 4200 to access, offload data, or upload data to, computer-executable instructions, application programs, etc. stored on a temporary or non-transitory memory medium. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied in the storage medium 4221, which may comprise a device-readable medium.

[0174] In FIG. 30 , the processing circuit 4201 may be configured to communicate with network 4243b using a communications subsystem 4231. Network 4243a and network 4243b may be the same network or networks or different networks or networks. The communications subsystem 4231 may be configured to include one or more transceivers used to communicate with network 4243b. For example, the communications subsystem 4231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communications protocols such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 4233 and / or a receiver 4235 for implementing transmitter or receiver functions, respectively, appropriate for the RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software or firmware, or may alternatively be implemented separately.

[0175] In the illustrated embodiment, the communication capabilities of the communication subsystem 4231 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem 4231 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 4243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communications network, another similar network, or any combination thereof. For example, the network 4243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 4213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 4200.

[0176] The features, benefits, and / or functionality described herein may be implemented in one of the components of the UE 4200 or distributed across multiple components of the UE 4200. Furthermore, the features, benefits, and / or functionality described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 4231 may be configured to include any of the components described herein. Furthermore, the processing circuit 4201 may be configured to communicate with any of such components over the bus 4202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuit 4201, perform the corresponding functions described herein. In another example, the functionality of any of such components may be distributed between the processing circuit 4201 and the communication subsystem 4231. In another example, non-computationally intensive functionality of any of such components may be implemented in software or firmware, and computationally intensive functionality may be implemented in hardware.

[0177] FIG. 31 illustrates a virtualized environment according to some embodiments.

[0178] 31 is a schematic block diagram illustrating a virtualization environment 4300 in which functionality implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. Virtualization, as used herein, may apply to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or component of that device, and relates to implementations in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0179] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 4300 hosted by one or more of the hardware nodes 4330. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0180] The functionality may be implemented by one or more applications 4320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 4320 are run in a virtualized environment 4300, which provides hardware 4330 comprising processing circuitry 4360 and memory 4390. The memory 4390 includes instructions 4395 executable by the processing circuitry 4360, such that the applications 4320 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0181] The virtualization environment 4300 includes general-purpose or dedicated network hardware devices 4330 that include one or more sets of processors or processing circuits 4360, which may be commercial off-the-shelf (COTS) processors, dedicated application-specific integrated circuits (ASICs), or any other type of processing circuitry, including digital or analog hardware components or dedicated processors. Each hardware device may include memory 4390-1, which may be non-persistent memory for temporarily storing instructions 4395 or software executed by the processing circuits 4360. Each hardware device may include one or more network interface controllers (NICs) 4370, also known as network interface cards, which include physical network interfaces 4380. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 4390-2 that stores software 4395 and / or instructions executable by the processing circuits 4360. Software 4395 may include any type of software, including software for instantiating one or more virtualization layers 4350 (also called hypervisors), software for running virtual machines 4340, and software that enables it to perform the functions, features, and / or benefits described in connection with some embodiments described herein.

[0182] The virtual machines 4340 may comprise virtual processes, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of the virtual appliance 4320 instance may be implemented on one or more of the virtual machines 4340, and the implementation may be done in different ways.

[0183] During operation, processing circuitry 4360 executes software 4395 to instantiate a hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 4350 may present to the virtual machine 4340 a virtual operating platform that appears to be networking hardware.

[0184] 31, hardware 4330 may be a standalone network node with general or specific components. Hardware 4330 may include antenna 43225 and may implement some functionality via virtualization. Alternatively, hardware 4330 may be part of a larger cluster of hardware (e.g., as in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via a management and orchestration (MANO) 43100 that, among other things, oversees the lifecycle management of application 4320.

[0185] Hardware virtualization is referred to in some contexts as network functions virtualization (NFV), which can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0186] In the context of NFV, a virtual machine 4340 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each virtual machine 4340 and the portion of hardware 4330 on which it runs, whether hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other ones of virtual machines 4340, form a separate virtual network element (VNE).

[0187] Further in the context of NFV, a virtual network function (VNF) is responsible for handling a specific network function running in one or more virtual machines 4340 on top of the hardware networking infrastructure 4330 and corresponds to application 4320 in FIG. 31.

[0188] In some embodiments, one or more radio units 43200, each including one or more transmitters 43220 and one or more receivers 43210, may be coupled to one or more antennas 43225. The radio units 43200 may communicate directly with the hardware node 4330 via one or more appropriate network interfaces and may be used in combination with a virtualization component to provide a virtual node with wireless capabilities, such as a wireless access node or base station.

[0189] In some embodiments, some signaling may be accomplished using a control system 43230, which may alternatively be used for communication between the hardware node 4330 and the radio unit 43200.

[0190] FIG. 32 illustrates a communications network connected to a host computer through an intermediate network, according to some embodiments.

[0191] 32 , according to one embodiment, a communication system includes a communication network 4410, such as a 3GPP-type cellular network, comprising an access network 4411, such as a wireless access network, and a core network 4414. The access network 4411 includes a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c can be connected to the core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in the coverage area 4413c wirelessly connects to or is configured to be paged by the corresponding base station 4412c. A second UE 4492 in the coverage area 4413a can be wirelessly connected to the corresponding base station 4412a. Although multiple UEs 4491, 4492 are shown 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 the corresponding base station 4412.

[0192] The communications network 4410 is itself connected to a host computer 4430, which 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 4430 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 4421 and 4422 between the communications network 4410 and the host computer 4430 may extend directly from the core network 4414 to the host computer 4430 or may proceed through an optional intermediate network 4420. The intermediate network 4420 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them; the intermediate network 4420 may be a backbone network or the Internet, if any; in particular, the intermediate network 4420 may comprise two or more subnetworks (not shown).

[0193] The communication system of FIG. 32 as a whole enables connectivity between connected UEs 4491, 4492 and a host computer 4430. The connectivity may be described as an over-the-top (OTT) connection 4450. The host computer 4430 and connected UEs 4491, 4492 are configured to communicate data and / or signaling via the OTT connection 4450 using the access network 4411, the core network 4414, any intermediate networks 4420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 4450 may be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes are unaware of the routing of the uplink and downlink communications. For example, the base station 4412 may not, or need not, be informed about the past routing of incoming downlink communications involving data originating from the host computer 4430 that is to be forwarded (e.g., handed over) to the connected UE 4491. Similarly, the base station 4412 does not need to be aware of the future routing of outgoing uplink communications originating from the UE 4491 and destined for the host computer 4430.

[0194] FIG. 33 illustrates a host computer communicating with user equipment via a base station over a partially wireless connection, according to some embodiments.

[0195] An exemplary implementation of the UE, base station, and host computer described in the previous paragraph, according to one embodiment, will now be described with reference to FIG. 33. In the communication system 4500, the host computer 4510 comprises hardware 4515 including a communication interface 4516 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 4500. The host computer 4510 further comprises processing circuitry 4518, which may have storage and / or processing capabilities. In particular, the processing circuitry 4518 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 host computer 4510 further comprises software 4511, which is stored on or accessible by the host computer 4510 and executable by the processing circuitry 4518. The software 4511 includes a host application 4512. The host application 4512 may be operable to provide services to a remote user, such as a UE 4530 connecting via an OTT connection 4550 that terminates at the UE 4530 and the host computer 4510. In providing services to the remote user, the host application 4512 may provide user data that is transmitted using the OTT connection 4550.

[0196] The communications system 4500 further includes a base station 4520 provided in the communications system, the base station 4520 comprising hardware 4525 that enables the base station 4520 to communicate with the host computer 4510 and the UE 4530. The hardware 4525 may include a communications interface 4526 for setting up and maintaining wired or wireless connections with interfaces of different communications devices of the communications system 4500, as well as a wireless interface 4527 for setting up and maintaining at least a wireless connection 4570 with a UE 4530 located in a coverage area (not shown in FIG. 33 ) served by the base station 4520. The communications interface 4526 may be configured to facilitate a connection 4560 to the host computer 4510. The connection 4560 may be direct, or alternatively, the connection 4560 may pass through a core network (not shown in FIG. 33 ) of the communications system and / or one or more intermediate networks external to the communications system. In the illustrated embodiment, the hardware 4525 of the base station 4520 further includes processing circuitry 4528, 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 4520 further has software 4521 that is stored internally or accessible via an external connection.

[0197] The communication system 4500 further includes the previously mentioned UE 4530. The hardware 4535 of the UE 4530 may include a wireless interface 4537 configured to set up and maintain a wireless connection 4570 with a base station serving the coverage area in which the UE 4530 is currently located. The hardware 4535 of the UE 4530 further includes a processing circuit 4538, 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 UE 4530 further includes software 4531 stored on or accessible by the UE 4530 and executable by the processing circuit 4538. The software 4531 includes a client application 4532. The client application 4532 may be operable to provide services to a human or non-human user via the UE 4530 with support from the host computer 4510. On the host computer 4510, a running host application 4512 may communicate with a running client application 4532 via an OTT connection 4550 that terminates at the UE 4530 and the host computer 4510. In providing services to a user, the client application 4532 may receive request data from the host application 4512 and provide user data in response to the request data. The OTT connection 4550 may transfer both the request data and the user data. The client application 4532 may interact with the user to generate the user data that the client application 4532 provides.

[0198] It should be noted that the host computer 4510, base station 4520, and UE 4530 shown in Figure 33 may be similar to or equivalent to the host computer 4430, one of the base stations 4412a, 4412b, and 4412c, and one of the UEs 4491 and 4492, respectively, of Figure 32. That is, the inner workings of these entities may be as shown in Figure 33, and separately, the surrounding network topology may be that of Figure 32.

[0199] 33, the OTT connection 4550 is depicted abstractly to show communication between the host computer 4510 and the UE 4530 via the base station 4520, without explicit reference to intermediary devices and the exact routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 4530 or from the service provider operating the host computer 4510, or both. While the OTT connection 4550 is active, the network infrastructure may also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0200] The wireless connection 4570 between the UE 4530 and the base station 4520 follows the teachings of embodiments described throughout this disclosure. One or more of various embodiments may improve performance of the OTT service provided to the UE 4530 using the OTT connection 4550 of which the wireless connection 4570 forms the last segment. More precisely, the teachings of these embodiments may improve random access speed and / or reduce random access failure rates, thereby providing benefits such as faster and / or more reliable random access.

[0201] 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 for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to fluctuations in the measurement results. The measurement procedures and / or the network functionality for reconfiguring the OTT connection 4550 may be implemented in software 4511 and hardware 4515 of the host computer 4510 or in software 4531 and hardware 4535 of the UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 4550 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 4511, 4531 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 4550 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 4520, and the reconfiguration may be unknown or imperceptible to the base station 4520. Such procedures and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 4510 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in software 4511 and 4531 causing messages, particularly empty or “dummy” messages, to be sent using the OTT connection 4550 while the software 4511 and 4531 monitors propagation times, errors, etc.

[0202] FIG. 34 illustrates a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments.

[0203] Figure 34 is a flowchart illustrating a method implemented in a communications system according to one embodiment. The communications system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 32 and 33. For simplicity of this disclosure, only a drawing reference to Figure 34 is included in this section. In step 4610, the host computer provides user data. In sub-step 4611 of step 4610 (which may be optional), the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission carrying the user data to the UE. In step 4630 (which may be optional), the base station transmits the user data carried in the host computer initiated transmission to the UE, in accordance with the teachings of embodiments described throughout this disclosure. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0204] FIG. 35 illustrates a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments.

[0205] Figure 35 is a flowchart 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 Figures 32 and 33. For simplicity of this disclosure, only a drawing reference to Figure 35 is included in this section. In step 4710 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 step 4720, the host computer initiates a transmission carrying the user data to the UE. The transmission may go through a base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0206] FIG. 36 illustrates a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments.

[0207] Figure 36 is a flowchart illustrating a method implemented in a communications system according to one embodiment. The communications system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 32 and 33. For simplicity of this disclosure, only a drawing reference to Figure 36 is included in this section. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In sub-step 4821 (which may be optional) of step 4820, the UE provides the user data by executing a client application. In sub-step 4811 (which may be optional) of step 4810, the UE executes a client application that 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 consider 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 sub-step 4830 (which may be optional). In method step 4840, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0208] FIG. 37 illustrates a method implemented in a communication system including a host computer, a base station, and user equipment, according to some embodiments.

[0209] Figure 37 is a flowchart 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 Figures 32 and 33. For simplicity of this disclosure, only drawing references to Figure 37 are included in this section. In step 4910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of embodiments described throughout this disclosure. In step 4920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0210] Any suitable step, method, feature, function, or benefit disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0211] The term unit may have its usual meaning in the field of electronics, electrical devices, and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solids and / or discrete devices, computer programs or instructions, etc., for performing respective tasks, procedures, calculations, output, and / or display functions, such as those described herein.

[0212] Further definitions and embodiments are described below.

[0213] In the above description of various embodiments of the inventive concept, it should be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the inventive concept. Unless otherwise specified, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the inventive concept belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning in accordance with the meaning of those terms in the context of this specification and related art, and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0214] When an element is referred to as being "connected," "coupled," or "responsive" to another element, or variations thereof, the element may be directly connected, coupled, or responsive to the other element, or intervening elements may be present. In contrast, when an element is referred to as being "directly connected," "directly coupled," or "directly responsive" to another element, or variations thereof, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, as used herein, "coupled," "connected," "responsive," or variations thereof may include wirelessly coupled, wirelessly connected, or wirelessly responsive. As used herein, the singular forms "a," "an," and "the" are intended to include the plural unless the context clearly dictates otherwise. For brevity and / or clarity, well-known functions or constructions may not be described in detail. The term "and / or" (abbreviated " / ") includes any and all combinations of one or more of the associated listed items.

[0215] Although terms such as first, second, third, etc. may be used herein to describe various elements / operations, it will be understood that these elements / operations are not limited by these terms. These terms are merely used to distinguish one element / operation from another. Thus, a first element / operation in some embodiments may be referred to as a second element / operation in other embodiments without departing from the teachings of the inventive concept. The same reference numbers or characters may refer to the same or similar elements throughout this specification.

[0216] As used herein, the terms "comprise," "comprising," "comprises," "include," "including," "includes," "have," "has," "having," or variations thereof, are open-ended and include one or more stated features, integers, elements, steps, components, or functions, but do not exclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Furthermore, as used herein, the common abbreviation "eg," from the Latin phrase "exempli gratia," may be used to introduce or specifically name one or more general examples of the aforementioned items, without limiting such items. The common abbreviation "ie," from the Latin phrase "id est," may be used to specifically name a particular item from a more general statement.

[0217] Exemplary embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices), and / or computer program products. It should be understood that blocks of the block diagrams and / or flowchart illustrations, and combinations of blocks in the block diagrams and / or flowchart illustrations, can be implemented by computer program instructions performed by one or more computer circuits. These computer program instructions can be provided to processor circuits of general-purpose computer circuits, special-purpose computer circuits, and / or other programmable data processing circuits to create machines, such that the instructions executing via the processor of the computer and / or other programmable data processing apparatus transform and control transistors, values ​​stored in memory locations, and other hardware components within such circuits to implement the functions / acts specified in one or more blocks of the block diagrams and / or flowcharts, and thereby create means (functions) and / or structures for implementing the function / acts specified in the block diagram and / or flowchart block(s).

[0218] The computer program instructions may also be stored on a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored on the computer-readable medium produce an article of manufacture containing instructions that implement the functions / acts specified in one or more blocks of the block diagrams and / or flowcharts. Thus, embodiments of the inventive concepts may be embodied in hardware and / or in software (including firmware, resident software, microcode, etc.) running on a processor, such as a digital signal processor, which may be collectively referred to as a "circuit," "module," or variations thereof.

[0219] It should also be noted that in some alternative implementations, the functions / acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functions / acts involved. Moreover, the functionality of a given block of the flowcharts and / or block diagrams may be separated into multiple blocks, and / or the functionality of two or more blocks of the flowcharts and / or block diagrams may be at least partially integrated. Finally, other blocks may be added / inserted between the shown blocks, and / or blocks / acts may be omitted without departing from the scope of the inventive concept. Moreover, while some of the figures include arrows on communication paths to indicate a primary direction of communication, it should be understood that communication may occur in the opposite direction to the illustrated arrows.

[0220] Numerous variations and modifications may be made to the embodiments without substantially departing from the principles of the inventive concept. All such variations and modifications are intended to be included herein within the scope of the inventive concept. Accordingly, the subject matter disclosed above should be considered illustrative and not limiting, and the example embodiments are intended to cover all such modifications, extensions, and other embodiments that fall within the spirit and scope of the inventive concept. Therefore, to the fullest extent permitted by law, the scope of the inventive concept should be determined by the broadest permissible interpretation of this disclosure, including example embodiments and their equivalents, and should not be limited or restricted by the above detailed description.

Claims

1. A method performed by a Vehicle to Everything (V2X) Application Enabler (VAE) client (104) of a client device (100), the method comprising: Receiving a session-oriented service request from a Vehicle to Everything (V2X) Application Enabler (VAE) server (114) (2401), the session-oriented service request including an identification of the VAE client (104), an identification of a session, and a reporting configuration; sending (2403) a session-oriented service response to the VAE server (114) indicating approval of the session-oriented service request; providing a session-oriented service establishment notification to a V2X application-specific client (102) (2405); A method comprising:

2. receiving (2501) a session-oriented service change request from the VAE server (114); sending a session-oriented service change response to the VAE server (114) indicating acceptance of the session-oriented service change request (2503); providing 2505 a session-oriented service change notification to the V2X application-specific client 102; The method of claim 1 further comprising:

3. The method of claim 2 , wherein the session-oriented service change request comprises an update requirement or a change in server information.

4. The method of claim 3 , wherein the updated requirements include changes in network requirements or changes in Quality of service (QoS) requirements.

5. Sending a session-oriented service change request (2601) to the VAE server (114), the session-oriented service change request including one or more updates in service information or changes in server information; receiving a session-oriented service change response from the VAE server (114) indicating acceptance of the session-oriented service change request (2603); The method of claim 1 further comprising:

6. The method of claim 5 , wherein the session-oriented service change request comprises an update to service information, an update to requirements, or an update to server information.

7. The method of claim 6 , wherein the updates to the service information include updates to activated services or updates to vehicle trajectories.

8. receiving a session-oriented service termination request from the VAE server (114) (2701); Sending a session-oriented service termination response (2703) to the VAE server (114) indicating acceptance of the session-oriented service termination request; providing a session-oriented service termination notification to the V2X application-specific client (2705); 8. The method of claim 1, further comprising:

9. 9. The method of claim 8, wherein the session-oriented service termination request indicates an end of the session with the VAE server or indicates that a request for the session-oriented service cannot be satisfied.

10. Sending a session-oriented service termination request to the VAE server (114) (2801); receiving a session-oriented service termination response from the VAE server (114) indicating acceptance of the session-oriented service termination request (2803); 8. The method of claim 1, further comprising:

11. 11. The method of claim 10, wherein transmitting the session-oriented service termination request comprises transmitting the session-oriented service termination request in response to receiving a session-oriented service termination trigger request from the V2X application-specific client.

12. 12. The method of claim 1, wherein the client device is a Vehicle to Everything User Equipment (V2X UE) or a vehicle.

13. A Vehicle-to-Everything (V2X) Application Enabler (VAE) client (104), comprising: Receiving a session-oriented service request from a Vehicle-to-Everything (V2X) Application Enabler (VAE) server (114) (2401), the session-oriented service request including an identification of the VAE client (104), an identification of a session, and a reporting configuration; sending (2403) a session-oriented service response to the VAE server (114) indicating approval of the session-oriented service request; providing a session-oriented service establishment notification to a V2X application-specific client (2405); A VAE client (104) adapted to perform operations including:

14. 14. The VAE client (104) of claim 13, wherein the VAE client (104) is adapted to perform the operations of any one of claims 2 to 12.

15. 13. A computer program comprising program code executed by a processing circuit (1003) of a Vehicle-to-Everything (V2X) Application Enabler (VAE) client (104), the execution of the program code causing the VAE client (104) to perform the operations of any one of claims 1 to 12.

Images