Procedure for triggering and updating remote control driving at the V2X application server

Abstract

A method for supporting a session-oriented service for a vehicle, performed by a first server (112), includes sending a session-oriented service trigger request (1) to a second server (114) to initiate a session-oriented service for a client device. The method includes receiving a session-oriented service trigger response (2) from the second server (114) indicating whether the second server (114) has the ability to initiate a session-oriented service with the client device. In other embodiments, a method for supporting a session-oriented service for a vehicle, performed by a second server (114) communicatively connected to a network, includes receiving a session-oriented service trigger request (1) from the first server (112) to initiate a session-oriented service for the client device. The method includes sending a session-oriented service trigger response (2) to the first server (112), the session-oriented service trigger response indicating whether the second server (114) has the ability to initiate a session-oriented service with the client device.

Description

[0001] This application is a divisional application of the Chinese patent application "Process for triggering and updating remote control driving at a V2X application server" with application number 202180033596.3 (application date is April 30, 2021). Technical Field

[0002] The present disclosure relates generally to communications, and more particularly to a communication method and related devices and nodes supporting tele-operated driving (ToD). Background Art

[0003] The relevant standardization work will now be described.

[0004] Teleoperation support (TeSo) is defined in 3GPP TR 22.886 (clause 5.21), and the corresponding requirements for remote driving are in clause 7.2.5. Normative requirements are in 3GPP SA1 TS 22.186 "Service requirements for enhanced vehicle-to-everything (V2X) scenarios" V16.2.0, June 2019 (clause 5.5).

[0005] The 5G Automotive Association (5GAA) has also specified remote driving, remote driving support, and remote driving for automated parking use cases and corresponding service level requirements 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 cross-working group work item, 5GAA is researching communication solutions and operational architectures for remote driving services.

[0006] 3GPP TS 23.286 “Application layer support of V2X services; Functional architecture and information flows” V16.1.0 (June 2019) defines the V2X application layer model for V2X communications over PC5 and Uu. Figure 1 Reference Figure 1 , the V2X application enabler (VAE) layer provides support information to V2X applications.

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

[0008] The V2X application layer functional entities for V2X UEs 100a and 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 the Service Enabler Architecture Layer (SEAL) services for vertical industries specified in 3GPP TS 23.434, "Service Enabler Architecture Layer for Vertical Industries; Functional Architecture and Information Flows," V16.1.0 (June 2019).

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

[0010] Note that 3GPP TS describes the functionality of the V2X application specific layers which are not in the scope of the TS.

[0011] 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 through a Vs reference point.

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

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

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

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

[0016] Note that 3GPP TS describes that the V1-APP reference point is not in the scope of TS.

[0017] In the VAE layer, the VAE client 104b of V2X UE2 100b communicates with the VAE client 104a of V2X UE1 100a via the V5-AE reference point. In 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 via the V5-APP reference point.

[0018] Note that 3GPP TS describes that the V5-APP reference point is not in the scope of TS.

[0019] The following SEAL services for V2X applications are supported:

[0020] Location management as specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; Functional architecture and information flows” V16.1.0 (June 2019);

[0021] Group management as specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; Functional architecture and information flows” V16.1.0 (June 2019);

[0022] Configuration management as specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; Functional architecture and information flows” V16.1.0 (June 2019);

[0023] Identity management as specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; Functional architecture and information flows” V16.1.0 (June 2019);

[0024] Key management as specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; Functional architecture and information flows” V16.1.0 (June 2019); and

[0025] ● Network resource management as specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; functional architecture and information flows” V16.1.0 (June 2019).

[0026] VAE clients 104a, 104b interact with SEAL clients 106a, 106b via the SEAL-C reference point specified for each SEAL service. VAE server 114 interacts with SEAL server 116 via the SEAL-S reference point specified for each SEAL service. Interactions between SEAL clients 106a, 106b are supported by the SEAL-PC5 reference point specified for each SEAL service. Interactions between SEAL clients 106a, 106b and the corresponding SEAL server 116 are supported by the SEAL-UU reference point specified for each SEAL service.

[0027] Note that the SEAL-C, SEAL-S, SEAL-PC5 and SEAL-UU reference points for each SEAL service are specified in 3GPP TS 23.434 “Service enabler architecture layer for vertical industries; functional architecture and information flows” V16.1.0 (June 2019).

[0028] To support distributed VAE server deployment, the VAE server 114 interacts with another VAE server through a VAE-E reference point.

[0029] The V2X UE1 100a may also act as a UE-to-network relay to:

[0030] • enabling the VAE client 104b on the V2X UE2 100b to access the VAE server 114 via the V1-AE reference point; and

[0031] ● Enable the V2X application specific client 102b on the V2X UE2 100b to communicate with the V2X client via V1-

[0032] The APP reference point accesses the V2X application specific server 112 .

[0033] V1-AE messages can be sent via unicast, transparent multicast via xMB, or transparent multicast via MB2. Non-transparent multicast via xMB is triggered by a V1-AE message. Both transparent and non-transparent multicast modes support multicast distribution.

[0034] The VAE server 114 interacts with the 3GPP network system 108 through the V2, MB2, xMB, Rx, and T8 reference points. EPS and 5G, 3GPP TR 23.764 "Study on enhancements to application layer support for V2X services" V0.2.0 (July 2019) are considered as 3GPP network systems. Summary of the Invention

[0035] 3GPP TR 23.764 describes establishing session-oriented communications for services such as remote piloting. However, 3GPP TR 23.764 does not describe triggering remote piloting support, specifically when Time of Delivery (ToD) is required. This should occur before establishing a ToD session. It also does not describe device and server APIs for initiating ToD support. 3GPP TR 23.764 also does not allow a V2X application-specific server to request a VAE server to establish session-oriented communications for a remote piloting session.

[0036] According to some embodiments of the present inventive concept, a method for supporting a session-oriented service for a vehicle, performed by a first server, is provided. 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 also includes receiving a session-oriented service trigger response from the second server, the session-oriented service trigger response indicating whether the second server has the capability to initiate the session-oriented service with the client device.

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

[0038] One advantage that can be achieved using the inventive concepts described herein is that V2X service providers (e.g., road authorities) can use APIs and procedures to communicate with mobile network operators for establishing vehicle-to-vehicle session-oriented services, such as ToD support.

[0039] According to another embodiment of the present inventive concept, a method for supporting a session-oriented service for a vehicle, performed by a second server, is provided. The method includes receiving a session-oriented service trigger request from a first server to initiate a session-oriented service for a client device. The method also includes sending a session-oriented service trigger response to the first server, the session-oriented service trigger response indicating whether the second server is capable of initiating a session-oriented service with the client device.

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

[0041] According to a further embodiment of the present inventive concept, a method performed by a vehicle-to-everything (V2X) application enabler (VAE) client of a computing device is provided. The method includes receiving a session-oriented service request from a second server, the session-oriented service request including an identifier of the VAE client, an identifier of a 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 also includes providing a session-oriented service establishment notification to the V2X application-specific client.

[0042] A similar VAE client and computer program is provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] 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 certain non-limiting embodiments of the inventive concept. In the drawings:

[0044] Figure 1 is a block diagram illustrating a V2X application layer model according to some embodiments;

[0045] Figure 2 is a signaling diagram illustrating a process for triggering a VAE server to establish a session-oriented service with a VAE client according to some embodiments of the present inventive concept;

[0046] Figure 3 is a signaling diagram illustrating a process for establishing a session-oriented service between a VAE server and a VAE client according to some embodiments of the inventive concept;

[0047] Figure 4 is a signaling diagram illustrating a process for providing a session-oriented service update from a V2X application-specific server to a VAE server according to some embodiments of the present inventive concept;

[0048] Figure 5 is a signaling diagram illustrating a process for updating a session-oriented service between a VAE server and a VAE client according to some embodiments of the inventive concept;

[0049] Figure 6 is a signaling diagram illustrating a process for updating a session-oriented service triggered by a VAE client according to some embodiments of the inventive concept;

[0050] Figure 7 is a signaling diagram illustrating a process for providing a session-oriented service termination request from a V2X application-specific server to a VAE server according to some embodiments of the present inventive concept;

[0051] Figure 8 is a signaling diagram illustrating a process for terminating a session-oriented service between a VAE server and a VAE client according to some embodiments of the inventive concept;

[0052] Figure 9 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;

[0053] Figure 10 is a block diagram illustrating a V2X UE according to some embodiments of the present inventive concept;

[0054] Figure 11 is a block diagram illustrating a VAE server according to some embodiments of the present inventive concept;

[0055] Figure 12 is a block diagram illustrating a V2X application specific server according to some embodiments of the present inventive concept;

[0056] Figures 13 to 15 is a flowchart illustrating the operation of the first server according to various embodiments of the inventive concept;

[0057] Figures 16 to 23 is a flowchart illustrating the operation of the second server according to various embodiments of the inventive concept;

[0058] Figures 24 to 28 is a flowchart illustrating the operation of a VAE client according to some different embodiments of the present inventive concept;

[0059] Figure 29 is a block diagram of a wireless network according to some embodiments;

[0060] Figure 30 is a block diagram of a user equipment according to some embodiments;

[0061] Figure 31 is a block diagram of a virtualization environment according to some embodiments;

[0062] Figure 32 is a block diagram of a telecommunications network connected to a host computer via an intermediary network according to some embodiments;

[0063] Figure 33 is a block diagram of a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0064] Figure 34 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0065] Figure 35 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0066] Figure 36 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments;

[0067] Figure 37 is a block diagram of a method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments. DETAILED DESCRIPTION

[0068] The present invention will be described more fully below with reference to the accompanying drawings, in which examples of embodiments of the present invention are shown. However, the present invention can be embodied in many different forms and should not be construed as being limited to the embodiments described herein. On the contrary, these embodiments are provided to make this disclosure thorough and complete and to fully convey the scope of the present invention to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. It can be assumed that components in one embodiment are present in / used in another embodiment.

[0069] The following description provides various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and should not be interpreted as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter.

[0070] In the following description, the terms "approval" and "acceptance" are used interchangeably.

[0071] Figure 12 The present invention is a block diagram illustrating elements of a V2X UE 800 implementing a V2X application-specific client 102 and / or a VAE client 104 (a V2X UE may also be referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, a mobile device, a wireless communication terminal, a user equipment UE, a user equipment node / terminal / device, etc.), configured to provide wireless communications according to embodiments of the present inventive concept. (For example, the V2X UE 800 may be provided as follows with respect to Figure 29 Wireless device 4110, Figure 30 UE 4200, Figure 31 Virtual hardware 4430 and virtual machine 4340, Figure 32 UE4491, 4492, and Figure 33 4530, all of which should be considered interchangeable in the examples and embodiments described herein and within the intended scope of the present disclosure unless otherwise noted.) As shown, the V2X UE 800 may include an antenna 1007 (e.g., corresponding to Figure 29 Antenna 4111 and / or Figure 31 antenna 43225) and transceiver circuit 1001 (also referred to as a transceiver, for example, corresponding to Figure 29 Interface 4114, Figure 30 Interfaces 4205, 4209, 4211, transmitter 4233 and receiver 4235, Figure 31 transmitter 43210 and receiver 43220, and Figure 33The transceiver circuit includes a transmitter and a receiver, and is configured to provide communication with (one or more) base stations of the communication network (e.g., corresponding to Figure 29 The V2X UE 800 may also include a processing circuit 1003 (also referred to as a processor, e.g., corresponding to a processor) coupled to a transceiver circuit. Figure 29 The processing circuit 4120, Figure 30 Processor 4201, Figure 31 The processing circuit 4360 and Figure 33 Processing circuit 4538) and memory circuit 1005 coupled to the processing circuit (also referred to as memory, e.g., corresponding to Figure 29 Device readable medium 4130 and / or Figure 31 Memory circuit 1005 may include computer-readable program code that, when executed by processing circuit 1003, causes the processing circuit 1003 to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 1003 may be defined to include memory, so that a separate memory circuit is not required. V2X UE 800 may also include an interface (e.g., a user interface) coupled to processing circuit 1003, and / or V2X UE 800 may be incorporated into a vehicle.

[0072] As discussed herein, operations of the V2X UE 800 may be performed by the processing circuitry 1003 and / or the transceiver circuitry 1001. For example, the processing circuitry 1003 may control the transceiver circuitry 1001 to transmit communications to a radio access network node (also referred to as a base station) over a radio interface via the transceiver circuitry 100, and / or to receive communications from the network node over a radio interface via the transceiver circuitry 1001. Furthermore, modules may be stored in the memory circuitry 1005, and these modules may provide instructions such that when the processing circuitry 1003 executes the instructions of the modules, the processing circuitry 1002 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments related to a VAE client).

[0073] Figure 11 is a block diagram illustrating elements of a V2X application enabler VAE server 114 (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.) configured to provide wireless communications according to an embodiment of the present inventive concept. (For example, the VAE server 114 may be provided as follows with respect to Figure 29 Network node 4160, Figure 31 Virtual hardware 4330 or virtual machine 4340, Figure 32Base stations 4412a, 4412b and 4412c and / or Figure 33 As shown, the VAE server 114 may include a transceiver circuit 1101 (also referred to as a transceiver, e.g., corresponding to Figure 29 Portions of interface 4190 and / or Figure 33 The transceiver circuit 1101 includes a transmitter and a receiver configured to provide uplink and downlink radio communications with other servers and nodes of the communication network. The VAE server 114 may include a network interface circuit 1107 (also referred to as a network interface, e.g., corresponding to Figure 29 The interface 4190 part, Figure 31 Network interfaces 4370, 4380 and / or Figure 33 The VAE server 114 may further comprise a processing circuit 1103 (also referred to as a processor, e.g., corresponding to a processor) coupled to a transceiver circuit. Figure 29 Processing circuit 4170, Figure 31 The processing circuit 4360 and / or Figure 33 Processing circuit 4528) and memory circuit 1105 coupled to the processing circuit (also referred to as memory, e.g., corresponding to Figure 29 Device readable medium 4180 and / or Figure 31 Memory circuit 1105 may include computer-readable program code that, when executed by processing circuit 1103, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 1103 may be defined to include memory, eliminating the need for a separate memory circuit. VAE server 114 may also include an interface (e.g., a user interface) coupled to processing circuit 1103, and / or VAE server 114 may be incorporated into the vehicle.

[0074] As discussed herein, operations of the VAE server 114 may be performed by the processing circuitry 1103 and / or the transceiver circuitry 1101. For example, the processing circuitry 1103 may control the transceiver circuitry 1101 to send communications to a network node over a radio interface via the transceiver circuitry 110 and / or to receive communications from the node over a radio interface via the transceiver circuitry 1101. Furthermore, modules may be stored in the memory circuitry 1105, and these modules may provide instructions such that when the processing circuitry 1103 executes the instructions of the modules, the processing circuitry 1103 performs corresponding operations (e.g., the operations discussed below with respect to the example embodiment related to the first server).

[0075] Figure 12 is a block diagram illustrating elements of a V2X application-specific server 112 (the V2X application-specific server 112 may also be referred to as a first server, etc.) configured to provide wireless communication according to an embodiment of the present inventive concept. (For example, the V2X application-specific server 112 may be provided as follows with respect to Figure 29 Network node 4160, Figure 31 Virtual hardware 4330 or virtual machine 4340, Figure 32 Base stations 4412a, 4412b and 4412c and / or Figure 33 As shown, the V2X application specific server 112 may include a transceiver circuit (not shown) (also referred to as a transceiver, e.g., corresponding to Figure 29 Portions of interface 4190 and / or Figure 33 The V2X application specific server 112 may include a network interface circuit 407 (also referred to as a network interface, e.g., corresponding to a radio interface 4527) comprising a transmitter and a receiver configured to provide uplink and downlink radio communications with other servers and nodes of the communication network. Figure 29 The part of the interface 4190, Figure 31 Network interfaces 4370, 4380 and / or Figure 33 The V2X application specific server 112 may also include a processing circuit 1203 (also referred to as a processor, e.g., corresponding to a processor) coupled to the transceiver circuit. Figure 29 Processing circuit 4170, Figure 31 The processing circuit 4360 and / or Figure 33 Processing circuit 4528) and memory circuit 1205 coupled to the processing circuit (also referred to as memory, e.g., corresponding to Figure 29 Device readable medium 4180 and / or Figure 31Memory circuit 1205 may include computer-readable program code that, when executed by processing circuit 1203, causes the processing circuit 1203 to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 1203 may be defined to include memory, eliminating the need for a separate memory circuit. The V2X application-specific server 112 may also include an interface (e.g., a user interface) coupled to processing circuit 1203.

[0076] As discussed herein, operations of the V2X application-specific server 112 may be performed by the processing circuitry 1203 and / or the transceiver circuitry 1201. For example, the processing circuitry 1203 may control the transceiver circuitry 1201 to transmit communications to a network node over a radio interface via the transceiver circuitry 120, and / or to receive communications from the node over a radio interface via the transceiver circuitry 1201. Furthermore, modules may be stored in the memory circuitry 1205, and these modules may provide instructions such that when the processing circuitry 1203 executes the instructions of the modules, the processing circuitry 1203 performs corresponding operations (e.g., the operations discussed below with respect to the example embodiment related to the first server).

[0077] This application handles session-oriented services such as see-through overtaking maneuvers (when implemented via vehicle-to-network (V2N) communication), high-definition sensor sharing (when implemented via V2N communication), and remote control driving between the V2X application server 112 (acting as a remote driver) and the V2X UE 100 (acting as an operated vehicle). This disclosure focuses on triggers for session-oriented services at the V2X application-specific server 112. Session-oriented services are services provided specifically for a session and are terminated when the session is terminated.

[0078] There are several example use cases that require ToD support:

[0079] The driver of the vehicle or the autonomous driving system relies on the remote driver to control the vehicle for a period of time,

[0080] Until you reach your destination.

[0081] ●The driver or autonomous driving system of a vehicle entering a construction zone or accident scene sends a remote control driving request to the remote driver to control the vehicle within a limited time and area.

[0082] ●Automated Parking: The driver or the autonomous driving system of the vehicle enters a public or private parking area and requests remote driving support for automated parking.

[0083] Infrastructure-based remote driving: This is an approach to achieving ToD using data and input from infrastructure sensors and cameras to the remote driver, rather than just from the vehicle’s onboard sensors and cameras.

[0084] Therefore, there are two levels of control:

[0085] ●The remote driver sends assistance information as trajectory information (e.g., waypoints) to the vehicle or the autonomous driving system, which is still responsible for the operational control of the vehicle, such as steering wheel angle, braking, and acceleration.

[0086] The remote driver has full control over the vehicle's driving and is able to operate the vehicle remotely, such as controlling acceleration and steering wheel angle.

[0087] In session-oriented services such as tele-driving (ToD), a remote entity (human or machine) provides relevant information to the remotely driven vehicle. For example, in some implementations, a remote driving center provides trajectories to the vehicle for autonomous driving to available / predefined parking spots. In other implementations, the remote driving center (human or machine) is responsible for driving the vehicle (i.e., sending steering / command instructions), supported by real-time video streams and sensor information sent from the remotely driven vehicle. In general, in the case of a human remote driver, a tele-driving session involves the transmission of sensor data (interpreted objects) and progressive high-definition video / cameras (up to four cameras, one at each corner of the vehicle) from the vehicle to the driving center. The information sent from the remote center to the vehicle takes the form of driving trajectories (e.g., waypoints with associated timestamps) and steering commands (e.g., torque values ​​for braking / acceleration and steering). Depending on the implementation, tele-driving can require latency as low as 20ms (to ensure synchronization of commands and vehicle state) and data rates as high as 64Mbps, allowing for HD video transmission in a variety of quality levels. Knowing when / where remote control driving can be supported is important, given that when these requirements are not met, remote control driving cannot be performed (i.e., the vehicle stops being remotely driven and the vehicle must switch to fully autonomous driving or switch to a human driver in the vehicle).

[0088] The inventive concepts described herein can achieve at least the following:

[0089] ● Triggering session-oriented services (such as ToD sessions) from the V2X application-specific server to the VAE server, updating and terminating the session.

[0090] ● Notification from the VAE server to the V2X application specific server about established sessions for session establishment, update (e.g. parameter change) and termination.

[0091] ● Notification from VAE client to V2X application-specific client about established sessions for session establishment, renewal and termination

[0092] In various embodiments of the inventive concepts, the VAE layer provides support for session-oriented services (e.g., remote control piloting) at the application layer by establishing, updating, and terminating sessions. The following describes the procedures for triggering, maintaining, changing, and terminating session-oriented services (e.g., remote control piloting) at a V2X application-specific server and the notifications to the V2X application-specific server and client. Thus, the inventive concepts described herein can be used to implement a feasible mechanism for a V2X application server to establish, maintain, and terminate session-oriented services (e.g., remote control piloting) with a V2X UE.

[0093] The process for triggering (e.g., initiating) the establishment of a session-oriented service will now be described. In some embodiments, the V2X application-specific server 112 has received a request from the V2X application-specific client 102 along with information required to perform the session-oriented service to trigger the session-oriented service. The V2X application-specific server 112 evaluates the request from the V2X application-specific client 102 and determines to trigger the session-oriented service.

[0094] Go to Figure 2 In operation 1, the V2X application-specific server 112 triggers the VAE server 114 to initiate a session-oriented service to the VAE client 104. The request may include information such as the identity of the VAE client, the identity of the V2X application-specific server, the identity of the service session, and the "type" or "QoS requirements" of the session.

[0095] When it comes to information related to the service type or QoS request, examples of such information may include information on how many flows are associated with a session for 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 flow, the server may specify:

[0096] -Prioritized primary service requirements (lowest bit rate, etc.) and alternative service requirements.

[0097] - Indication of whether notification control is required in case QoS is not met / re-met.

[0098] - an indication of whether QoS sustainability analysis information as defined in clause 6.9 of TS 23.288 is required. If required, the server may also include in the request:

[0099] ■Generate KPIs (Key Performance Indicators) to be considered for QoS sustainability analysis.

[0100] ■ Thresholds for triggering notifications regarding QoS sustainability analysis.

[0101] ■ Lead time for triggering notifications about QoS sustainability analysis.

[0102] ■ Information about UE measurements related to session-oriented services that can be collected at the application layer (KPIs, measurement frequency, reporting thresholds, etc.), indicating whether such measurements can be collected on the client side or on the server side.

[0103] In operation 2, the VAE server 114 provides a session-oriented service trigger response to the V2X application-specific server 112, indicating the VAE server's 112 ability 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 cannot support the session-oriented service requested by the V2X application-specific server, the response provides an indication that the VAE server 114 cannot support the session-oriented service.

[0104] Figure 13 From the perspective of the V2X application specific server (which is designated as the first server 112) Figure 2 Go to Figure 13 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 13 Flowchart discussion (using Figure 12 The operation of the first server 112 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 12 The modules are stored in the memory 1205, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1203, the processing circuit 1203 performs the corresponding operations of the flowchart.

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

[0106] The information related to the type or QoS request includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes one or more of the following: primary service requirements and alternative service requirements in order of priority; an indication of whether notification control is required in the event of non-satisfaction / re-satisfaction of QoS; an indication of whether QoS sustainability analysis information is required; and information about user equipment (UE) measurements. When QoS sustainability analysis information is required, the information also includes one or more of the following: key performance indicators (KPIs) to be considered for generating QoS sustainability analysis; thresholds for triggering notifications about QoS sustainability analysis; and lead times for triggering notifications about QoS sustainability analysis.

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

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

[0109] Figure 16 From the perspective of the VAE server (which is designated as the second server 114) Figure 2 Go to Figure 16 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 16 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

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

[0111] The information related to the type or QoS request includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes one or more of the following: the primary service requirements and the alternative service requirements in order of priority; an indication of whether notification control is required in the event of non-satisfaction / re-satisfaction of QoS; an indication of whether QoS sustainability analysis information is required; and information about user equipment (UE) measurements. When QoS sustainability analysis information is required, the information also includes one or more of the following: key performance indicators (KPIs) to be considered for generating QoS sustainability analysis; thresholds for triggering notifications about QoS sustainability analysis; and lead times for triggering notifications about QoS sustainability analysis.

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

[0113] like Figure 3 As described in , in block 1605 , the processing circuit 1103 sends a session-oriented service establishment notification to the first server 112 , where the notification indicates that the session-oriented service has been established.

[0114] Now go to Figure 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) has been authenticated for session-oriented services and has connected to a V2X application server 112. The VAE server 114 has agreed to establish a session based on a request from the V2X application-specific server 112 as described above.

[0115] In operation 1, the VAE server 114 sends a request to one or more VAE clients for establishing a session-oriented service, the request including the VAE client's identity, the session's identity, and a reporting configuration. The reporting configuration indicates which parameters should be reported and how often the parameters should be reported.

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

[0117] In operation 3, the VAE server 114 sends a session-oriented service establishment notification ( Figure 13 Box 1305 and Figure 16 1605).

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

[0119] Figure 17 From the perspective of the VAE server 114 (which is designated as the second server 114) Figure 3 Go to Figure 17 , according to some embodiments of the inventive concept for supporting session-oriented services for vehicles, reference will now be made to Figure 17 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

[0120] In block 1701 , the processing circuit 1103 sends a session-oriented service request to the client device 100 having the VAE client 104 to establish a session-oriented service. The session-oriented service request includes an identifier of the VAE client 104 , an identifier of the session, and a report configuration.

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

[0122] Figure 24 From the perspective of VAE client 104 Figure 3 Go to Figure 24 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 24 Flowchart discussion (using Figure 10 The operation of the VAE client 104 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 10 The modules are stored in the memory 1005, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1003, the processing circuit 1003 performs the corresponding operations of the flowchart.

[0123] In block 2401 , the processing circuit 1003 receives a session-oriented service request from the second server 114 , the session-oriented service request including an identifier of the VAE client 104 , an identifier of the session, and a report configuration.

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

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

[0126] Go to Figure 4 , shows a process 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 triggering event, which includes an identifier of the session and an update of session parameters, such as a change in the QoS requirement of the session.

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

[0128] Figure 14 From the perspective of the V2X application specific server 112 (which is designated as the first server 112) Figure 4 Go to Figure 14 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 14 Flowchart discussion (using Figure 12 The operation of the first server 112 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 12 The modules are stored in the memory 1205, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1203, the processing circuit 1203 performs the corresponding operations of the flowchart.

[0129] In block 1401 , the processing circuit 1203 sends 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 to server information.

[0130] In block 1403 , the processing circuit 1203 receives a session-oriented service change 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.

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

[0132] Figure 18 From the perspective of the VAE server 114 (which is designated as the second server 114) Figure 4 Go to Figure 18 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 18 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

[0133] In block 1801 , the processing circuit 1103 receives a session-oriented service change trigger request from a first server ( 112 ), which includes an identifier of a session-oriented service and updated session parameters.

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

[0135] In block 1805 , in response to determining that the session-oriented service cannot be provided with 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.

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

[0137] In operation 1 , the VAE server 114 sends a session-oriented change request to one or more VAE clients 104 , which includes update requirements (eg, changes to network / QoS requirements) or changes to server information (eg, changes to VAE servers).

[0138] In operation 2 , the VAE client 104 sends a session-oriented change response to the VAE server 114 , where the response indicates that the session-oriented change request of the VAE server 114 is accepted.

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

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

[0141] Figure 19 From the perspective of the VAE server 114 (which is designated as the second server 114) Figure 5 Go to Figure 19 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 18 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

[0142] In block 1901, the processing circuit 1103 sends a session-oriented change request including an update requirement or a change in server information to the client device 100 having the VAE client 104. In block 1903, the processing circuit 1103 receives a session-oriented change response from the client device (100) having the VAE client (104) indicating acceptance of the change request.

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

[0144] Figure 25 From the perspective of VAE client 104 Figure 5 Go to Figure 25 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 25 Flowchart discussion (using Figure 10 The operation of the VAE client 104 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 10 The modules are stored in the memory 1005, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1003, the processing circuit 1003 performs the corresponding operations of the flowchart.

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

[0146] Go to Figure 6 In some embodiments of the present inventive concept, a session-oriented service update is triggered from the VAE client 104. This may occur, for example, 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 response to receiving a QoS notification or network information, where the QoS notification or network information may be provided from the V2X application-specific server 112 (upon receipt from the VAE server 114) or provided directly from the VAE server 114 via the VAE client 104.

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

[0148] In operation 1, the VAE client 104 sends a session-oriented change request to one or more VAE servers 114, which includes an update to service information (e.g., an update to activated services, an update to vehicle trajectories, etc.), an update to requirements (e.g., a change to network / QoS requirements), or an update to server information (e.g., a change to a VAE server). The VAE server 114 examines 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. In operation 3, the VAE server 114 sends a session-oriented service change notification to the V2X application-specific server 112. In operation 4, the VAE client 104 sends a session-oriented service change notification to the V2X application-specific client 102.

[0149] Figure 20 The operation of updating a session-oriented service triggered by a VAE client is described from the perspective of the VAE server 114. Figure 20 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 20 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

[0150] 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 to server information.

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

[0152] Figure 26 The operation of updating a session-oriented service triggered by the VAE client 104 is described from the perspective of the VAE client 104. Figure 26 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 26 Flowchart discussion (using Figure 10The operation of the VAE client 104 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 10 The modules are stored in the memory 1005, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1003, the processing circuit 1003 performs the corresponding operations of the flowchart.

[0153] In block 2601, processing circuit 1003 sends 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 to server information. In block 2603, processing circuit 1103 receives a session-oriented service change response from the second server 114 indicating acceptance of the session-oriented service change request.

[0154] The process for triggering a session-oriented service termination request from the V2X application-specific server 112 to the VAE server 114 will now be 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 can be based on a request from the V2X application-specific client 102 or a local decision of the V2X application-specific server 112.

[0155] Go to Figure 7 In operation 1 , the V2X application specific server 1121 provides a session-oriented termination trigger request to the VAE server 114 to terminate the session-oriented service with the VAE client 104 .

[0156] In operation 2 , the VAE server 114 provides the V2X application specific server 112 with a session-oriented service termination trigger response indicating that the session may be terminated.

[0157] Figure 15 From the perspective of the V2X application specific server 112 (which is designated as the first server 112) Figure 6 Go to Figure 15 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 15 Flowchart discussion (using Figure 12 The operation of the first server 112 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 12 The memory 1205 of the communication device and the modules may provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1203, the processing circuit 1203 performs the corresponding operations of the flowchart.

[0158] In block 1501, processing circuit 1203 sends a session-oriented service termination trigger request for terminating a session-oriented service to second server 114. In block 1503, processing circuit 1203 receives a session-oriented service termination trigger response from second server 114. In block 1505, processing circuit 1203 receives a session-oriented service termination notification from second server 114. This notification is received after the session-oriented service has been terminated.

[0159] Figure 21 From the perspective of the VAE server 114 Figure 7 Go to Figure 21 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 21 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

[0160] In block 2101, processing circuit 1103 receives a session-oriented service termination trigger request for terminating a session-oriented service from first server 112. In operation 2103, processing circuit 1103 sends a session-oriented service termination trigger response to first server 112. In operation 2105, processing circuit 1103 sends a session-oriented service termination notification to first server 112. This notification is sent after the session-oriented service has been terminated.

[0161] Go to Figure 8 , a process of 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., the session with the VAE server ends or the requirements for the session-oriented service are not met).

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

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

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

[0165] Figure 22 From the perspective of the VAE server 114 Figure 8 Go to Figure 22 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 22 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11 The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

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

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

[0168] Figure 27 From the perspective of VAE client 104 Figure 8 Go to Figure 27 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 27 Flowchart discussion (using Figure 10 The operation of the VAE client 104 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 19 The modules are stored in the memory 1005, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1003, the processing circuit 1003 performs the corresponding operations of the flowchart.

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

[0170] Go to Figure 9In various other embodiments of the inventive concepts, a process for terminating a session-oriented service is triggered from the VAE client 104. For example, this may occur when the V2X application-specific client 102 is responsible for performing service adaptation. An example of this is when the V2X application-specific client 102 ends the service (e.g., the vehicle reaches its final destination). Another example is when the V2X application-specific client 102 triggers termination of the session-oriented service as a 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 service requirements associated with the service. The QoS notification or network information may be provided from the V2X application-specific server 112 (upon receipt from the VAE server 114) or provided directly from the VAE server 114 via the VAE client 104.

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

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

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

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

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

[0176] Figure 23 The operation of terminating a session-oriented service triggered by the VAE client 104 is described from the perspective of the VAE server 114. Figure 23 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 23 Flowchart discussion (using Figure 11 The operation of the second server 114 is realized by the structure of the block diagram. For example, the module can be stored in Figure 11The modules are stored in the memory 1105, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1103, the processing circuit 1103 performs the corresponding operations of the flowchart.

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

[0178] Figure 28 From the perspective of VAE client 104 Figure 7 Go to Figure 28 , according to some embodiments of the inventive concept for supporting session-oriented services, reference will now be made to Figure 28 Flowchart discussion (using Figure 10 The operation of the VAE client 104 is implemented by the structure of the block diagram. For example, the module can be stored in Figure 10 The modules are stored in the memory 1005, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding communication device processing circuit 1003, the processing circuit 1003 performs the corresponding operations of the flowchart.

[0179] In block 2801, the processing circuit 1003 sends a session-oriented service termination request to the second server 114. In block 2803, the processing circuit 1003 receives a session-oriented service termination response from the second server 114, the response 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.

[0180] Example embodiments are discussed below.

[0181] Example

[0182] Embodiment 1. A method for supporting a session-oriented service for a vehicle, performed by a first server (112), the method comprising:

[0183] sending (1301) a session-oriented service triggering request to a second server (114) to initiate a session-oriented service for the client device (104); and

[0184] A session-oriented service trigger response is received (1303) from the second server (114), the response indicating whether the second server 114 has the capability to initiate a session-oriented service with the client device (104).

[0185] Embodiment 2. The method according to embodiment 1, wherein the first server is a vehicle-to-everything (V2X) application-specific server, and the second server is a V2X application enabler (VAE) server.

[0186] Embodiment 3. The method according to any one of embodiments 1-2, wherein sending a session-oriented service triggering request comprises: sending a session-oriented service triggering request having information associated with the session-oriented service.

[0187] Embodiment 4. A method according to embodiment 3, wherein the information includes one or more of the following: an identifier of the client device (104), an identifier of the first server (112), an identifier of the service session, and a type of session-oriented service or a quality of service (QoS) requirement.

[0188] Embodiment 5. The method of embodiment 4, wherein the information related to the type or QoS request includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes one or more of the following:

[0189] Prioritized primary and secondary service requirements;

[0190] Indication of whether notification control is required in case of QoS not being met / re-met;

[0191] An indication of whether QoS sustainability analysis information is required; and

[0192] Information about User Equipment (UE) measurements.

[0193] Embodiment 6. The method according to embodiment 5, wherein, when QoS sustainability analysis information is required, the information further includes one or more of the following:

[0194] Generate key performance indicators (KPIs) to be considered for QoS sustainability analysis;

[0195] Thresholds for triggering notifications regarding QoS sustainability analysis; and

[0196] The lead time used to trigger notifications about QoS sustainability analysis.

[0197] Embodiment 7. The method according to any one of embodiments 1-6, further comprising:

[0198] A session-oriented service establishment notification is received (1305) from a second server (114), the session-oriented service establishment notification indicating that a session-oriented service has been established.

[0199] Embodiment 8. The method according to any one of embodiments 1-7, further comprising:

[0200] 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 to server information; and

[0201] A session-oriented service change trigger response is received (1403) from the second server (114), the session-oriented service change trigger response indicating whether the second server (114) can continue the session-oriented service with the updated session parameters.

[0202] Example 9. The method according to Example 8, further comprising:

[0203] A session-oriented service change notification is received (1405) from a second server (114).

[0204] Embodiment 10. The method according to any one of embodiments 1-7, further comprising:

[0205] sending (1501) a session-oriented service termination trigger request for terminating the session-oriented service to a second server (114);

[0206] A session-oriented service termination trigger response is received (1503) from the second server (114).

[0207] Example 11. The method according to Example 10, further comprising:

[0208] A session-oriented service termination notification is received (1505) from the second server (114).

[0209] Embodiment 12. A first server (112) adapted to perform an operation comprising:

[0210] sending (1301) a session-oriented service triggering request to a second server (114) to initiate a session-oriented service for the client device (104); and

[0211] A session-oriented service triggering response is received (1303) from the second server (114), the session-oriented service triggering response indicating whether the second server (114) will initiate a session-oriented service with the client device (104).

[0212] Embodiment 13. The first server (112) according to embodiment 12, wherein the first server (112) is adapted to perform operations according to any one of embodiments 2-11.

[0213] Embodiment 14. A first server (112), comprising:

[0214] processing circuit (1203); and

[0215] A memory (1205) coupled to the processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the first server (112) to perform operations comprising:

[0216] sending (1301) a session-oriented service triggering request to a second server (114) to initiate a session-oriented service for the client device (104); and

[0217] A session-oriented service triggering response is received (1303) from the second server (114), the session-oriented service triggering response indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104).

[0218] Embodiment 15. The first server (112) according to embodiment 14, wherein the first server is a vehicle-to-everything (V2X) application specific server and the second server is a V2X application enabler (VAE) server.

[0219] Example 16. A first server (112) according to any one of Examples 14-15, wherein, when sending a session-oriented service trigger request, the memory includes further instructions that, when executed by the processing circuit (1203), cause the first server (112) to perform the following operations: sending a session-oriented service trigger request having information associated with the session-oriented service.

[0220] Embodiment 17. A first server (112) according to embodiment 16, wherein the information includes an identification of the client device (104), an identification of the first server (112), an identification of the service session, and one or more of a type of session-oriented service or a quality of service (QoS) requirement.

[0221] Embodiment 18. The first server (112) of embodiment 17, wherein the information related to the type or QoS request includes information about how many flows are related to the session-oriented service, and for each flow, the information includes one or more of the following:

[0222] Prioritized primary and secondary service requirements;

[0223] Indication of whether notification control is required in case of QoS not being met / re-met;

[0224] An indication of whether a QoS sustainability analysis is required; and

[0225] Information about User Equipment (UE) measurements.

[0226] Embodiment 19. The first server (112) according to embodiment 17, wherein, when QoS sustainability analysis information is required, the information further includes one or more of the following:

[0227] Generate key performance indicators (KPIs) to be considered for QoS sustainability analysis;

[0228] Thresholds for triggering notifications regarding QoS sustainability analysis; and

[0229] The lead time used to trigger notifications about QoS sustainability analysis.

[0230] Embodiment 20. The first server (112) of any one of embodiments 14-19, wherein the memory includes further instructions that, when executed by the processing circuit (1203), cause the first server (112) to perform operations, the operations further comprising:

[0231] A session-oriented service establishment notification is received (1305) from a second server (114), the session-oriented service establishment notification indicating that a session-oriented service has been established.

[0232] Embodiment 21. The first server (112) according to any one of embodiments 14-20, further comprising:

[0233] 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 to server information; and

[0234] A session-oriented service change trigger response is received (1403) from the second server (114), the session-oriented service change trigger response indicating whether the second server can continue the session-oriented service with the updated session parameters.

[0235] Embodiment 22. The first server (112) of embodiment 21, wherein the memory includes further instructions that, when executed by the processing circuit (1203), cause the first server (112) to perform operations, the operations further comprising:

[0236] A session-oriented service change notification is received (1405) from a second server (114).

[0237] Embodiment 23. The first server (112) of any one of embodiments 14-20, wherein the memory includes further instructions that, when executed by the processing circuit (1203), cause the first server (112) to perform operations, the operations further comprising:

[0238] sending (1501) a session-oriented service termination trigger request for terminating the session-oriented service to a second server (114);

[0239] A session-oriented service termination trigger response is received (1503) from the second server (114).

[0240] Embodiment 24. The first server (112) of embodiment 23, wherein the memory includes further instructions that, when executed by the processing circuit (1203), cause the first server (112) to perform operations, the operations further comprising:

[0241] A session-oriented service termination notification is received (1505) from the second server (114).

[0242] 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 operations according to any one of embodiments 1-11.

[0243] Embodiment 26. A computer program product comprising a non-transitory storage medium comprising program code executed by a processing circuit (1203) of a first server (112), whereby execution of the program code causes the first server (112) to perform operations according to any one of embodiments 1-11.

[0244] Embodiment 27. A method for supporting a session-oriented service for a vehicle, performed by a second server (114) communicatively connected to a network (108), the method comprising:

[0245] receiving (1601) a session-oriented service triggering request from a first server (112) to initiate a session-oriented service for a client device (104); and

[0246] A session-oriented service triggering response is sent (1603) to the first server (112), the session-oriented service triggering response indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104).

[0247] Embodiment 28. The method of embodiment 27, wherein the first server is a vehicle-to-everything (V2X) application-specific server and the second server is a V2X application enabler (VAE) server.

[0248] Embodiment 29. The method of any one of embodiments 27-28, wherein receiving a session-oriented service triggering request comprises receiving a session-oriented service triggering request having information associated with the session-oriented service.

[0249] Embodiment 30. A method according to embodiment 29, wherein the information includes 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 of session-oriented service or quality of service (QoS) requirement.

[0250] Embodiment 31. The method of embodiment 30, wherein the information related to the type or QoS request includes information about how many flows are related to the session-oriented service, and for each flow, the information includes one or more of the following:

[0251] Prioritized primary and secondary service requirements;

[0252] Indication of whether notification control is required in case of QoS not being met / re-met;

[0253] An indication of whether QoS sustainability analysis information is required; and

[0254] Information about User Equipment (UE) measurements.

[0255] Embodiment 32. The method of embodiment 31, wherein, when QoS sustainability analysis information is required, the information further includes one or more of the following:

[0256] Generate key performance indicators (KPIs) to be considered for QoS sustainability analysis;

[0257] Thresholds for triggering notifications regarding QoS sustainability analysis; and

[0258] The lead time used to trigger notifications about QoS sustainability analysis.

[0259] Embodiment 33. The method according to any one of embodiments 27-32, further comprising:

[0260] A session-oriented service establishment notification is sent (1605) to the first server (112), the session-oriented service establishment indicating that the session-oriented service has been established.

[0261] Embodiment 34. The method according to any one of embodiments 27-33, further comprising:

[0262] Sending (1701) a session-oriented service request to a client device (100) having a VAE client (104) to establish a session-oriented service, the session-oriented service request including an identifier of the VAE client (104), an identifier of the session, and a report configuration;

[0263] receiving (1703) a session-oriented service response from a client device (100) having a VAE client (104), the session-oriented service response indicating acceptance of the session-oriented service request to establish the session-oriented service; and

[0264] In response to receiving the session-oriented service response indicating acceptance, a session-oriented service establishment notification is sent (1705) to the first server (112).

[0265] Example 35. The method according to Example 34, further comprising:

[0266] Receiving (1801) a session-oriented service change trigger request from a first server (112), the session-oriented service change trigger request including an identifier of a session-oriented service and updated session parameters;

[0267] In response to determining that updated session parameters can be provided to the session-oriented service; sending (1803) a session-oriented service change trigger response to the first server (112), the session-oriented service change trigger response indicating an ability to continue the session-oriented service with the updated session parameters; and

[0268] In response to determining that updated session parameters cannot be provided to the session-oriented service; sending (1805) a session-oriented service change trigger response to the first server (112), the session-oriented service change trigger response indicating that the second server (114) cannot continue the session-oriented service with the updated session parameters.

[0269] Example 36. The method according to Example 35, further comprising:

[0270] Sending (1901) a session-oriented change request to a client device (100) having a VAE client (104), the session-oriented change request including an update request or a change in server information;

[0271] receiving (1903) a session-oriented change response from a client device (100) having a VAE client (104), the session-oriented change response indicating acceptance of the change request; and

[0272] A session-oriented service change notification is sent (1905) to the first server (112).

[0273] Example 37. The method according to Example 34, further comprising:

[0274] Receiving (2001) 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 to server information;

[0275] sending (2003) a session-oriented service change response to a client device (100) having a VAE client (104), the session-oriented service change response indicating acceptance of the session-oriented service change request; and

[0276] A session-oriented service change notification is sent (2005) to the first server (112).

[0277] Example 38. The method according to Example 34, further comprising:

[0278] receiving (2101) a session-oriented service termination trigger request from a first server (112) to terminate the session-oriented service from the first server (112);

[0279] sending (2103) a session-oriented service termination trigger response to the first server (112); and

[0280] A session-oriented service termination notification is sent (2105) to the first server (112).

[0281] Example 39. The method according to Example 38, further comprising:

[0282] sending (2201) a session-oriented service termination request to a client device (100) having a VAE client (104); and

[0283] A session-oriented service termination response is received (2203) from a client device (100) having a VAE client (104), the session-oriented service termination response indicating acceptance of the session termination request.

[0284] Embodiment 40. The method according to embodiment 34, further comprising:

[0285] receiving (2301) a session-oriented service termination request from a client device (100) having a VAE client (104) to terminate a session-oriented service;

[0286] sending (2303) a session-oriented service termination response to a client device (100) having a VAE client (104), the session-oriented service termination response indicating acceptance of the session termination request; and

[0287] A session-oriented service termination notification is sent (2305) to the first server (112).

[0288] Embodiment 41. A second server (114) adapted to perform operations comprising:

[0289] receiving (1601) a session-oriented service triggering request from a first server (112) to initiate a session-oriented service for a client device (104); and

[0290] A session-oriented service triggering response is sent (1603) to the first server (112), the session-oriented service triggering response indicating whether the second server (114) has session-oriented service capability with the client device (104).

[0291] Embodiment 42. The second server (114) of embodiment 41, wherein the first server (112) is adapted to perform operations according to any one of embodiments 28-40.

[0292] Embodiment 43. A second server (114), comprising:

[0293] processing circuit (1103); and

[0294] A memory (1105) coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the second server (114) to perform operations comprising:

[0295] receiving (1601) a session-oriented service triggering request from a first server (112) to initiate a session-oriented service for a client device (104); and

[0296] A session-oriented service triggering response is sent (1603) to the first server (112), the session-oriented service triggering response indicating whether the second server (114) has the capability to initiate a session-oriented service with the client device (104).

[0297] Embodiment 44. The second server (114) according to embodiment 43, wherein the first server is a vehicle-to-everything (V2X) application specific server and the second server is a V2X application enabler (VAE) server.

[0298] Example 45. A second server (114) according to any one of Examples 43-44, wherein, upon receiving a session-oriented service trigger request, the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform the following operations: receive a session-oriented service trigger request having information associated with a session-oriented service.

[0299] Example 46. A second server (114) according to Example 45, wherein the information includes one or more of the following: an identification of the client device (104), an identification of the first server (112), an identification of the service session, and a type of session-oriented service or quality of service (QoS) requirements.

[0300] Embodiment 47. The second server (114) of embodiment 46, wherein the information related to the type or QoS request includes information about how many flows are associated with the session-oriented service, and for each flow, the information includes one or more of the following:

[0301] Prioritized primary and secondary service requirements;

[0302] Indication of whether notification control is required in case of QoS not being met / re-met;

[0303] An indication of whether QoS sustainability analysis information is required; and

[0304] Information about User Equipment (UE) measurements.

[0305] Embodiment 48. The second server (114) of embodiment 47, wherein when QoS sustainability analysis information is required, the information further includes one or more of the following:

[0306] Generate key performance indicators (KPIs) to be considered for QoS sustainability analysis;

[0307] Thresholds for triggering notifications regarding QoS sustainability analysis; and

[0308] The lead time used to trigger notifications about QoS sustainability analysis.

[0309] Embodiment 49. The second server (114) of any one of embodiments 43-48, wherein the memory comprises further instructions that, when executed by the processing circuit, cause the second server 114 to perform operations comprising:

[0310] A session-oriented service establishment notification is sent (1605) to the first server (112), the session-oriented service establishment notification indicating that the session-oriented service has been established.

[0311] Embodiment 50. The second server (114) of any one of embodiments 43-47, wherein the memory comprises further instructions that, when executed by the processing circuit, cause the second server (114) to perform further operations, the further operations comprising:

[0312] Sending (1701) a session-oriented service request to a client device (100) having a VAE client (104) to establish a session-oriented service, the session-oriented service request including an identifier of the VAE client (104), an identifier of the session, and a report configuration;

[0313] receiving (1703) a session-oriented service response from a client device (100) having a VAE client (104), the session-oriented service response indicating acceptance of the session-oriented service request to establish the session-oriented service; and

[0314] In response to receiving the session-oriented service response indicating acceptance, a session-oriented service establishment notification is sent (1705) to the first server (112).

[0315] Embodiment 51. The second server (114) of embodiment 50, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform further operations, the further operations comprising:

[0316] receiving (1801) a session-oriented service change trigger request from a first server (112), the session-oriented service change trigger request including an identifier of a session-oriented service and updated session parameters;

[0317] In response to determining that updated session parameters can be provided to the session-oriented service; sending (1901) a session-oriented service change trigger response to the first server (112), the session-oriented service change trigger response indicating an ability to continue the session-oriented service with the updated session parameters; and

[0318] In response to determining that updated session parameters cannot be provided to the session-oriented service; sending (1903) a session-oriented service change trigger response to the first server (112), the session-oriented service change trigger response indicating that the second server (114) cannot continue the session-oriented service with the updated session parameters.

[0319] Embodiment 52. The second server (114) of embodiment 51, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform further operations, the further operations comprising:

[0320] Sending (1901) a change request to a client device (100) having a VAE client (104), the change request including an update request or a change in server information;

[0321] receiving (1903) a change response from a client device (100) having a VAE client (104), the change response indicating acceptance of the change request; and

[0322] A session-oriented service change notification is sent to a first server (112).

[0323] Embodiment 53. The second server (114) of embodiment 50, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform further operations, the further operations comprising:

[0324] Receiving (2001) a session-oriented service change request from a client device (100) having a VAE client (104), the session-oriented service update request including one or more updates to service information or changes to server information;

[0325] sending (2003) a change response to a client device (100) having a VAE client (104), the change response indicating acceptance of the session-oriented service change request; and

[0326] A session-oriented service change notification is sent (2005) to the first server (112).

[0327] Embodiment 54. The second server (114) of embodiment 50, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform further operations, the further operations comprising:

[0328] receiving (2101) a session-oriented service termination trigger request from a first server (112) to terminate the session-oriented service; and

[0329] A session-oriented service termination trigger response is sent (2103) to the first server (112).

[0330] Embodiment 55. The second server (114) of embodiment 54, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform the further operations comprising:

[0331] Sending (2201) a session termination request to a client device (100) having a VAE client (104);

[0332] receiving (2203) a session termination response from a client device (100) having a VAE client (104), the session termination response indicating acceptance of the session termination request; and

[0333] A session-oriented service termination notification is sent (2205) to the first server (112).

[0334] Embodiment 55. The second server (114) of any one of embodiments 50-53, wherein the memory includes further instructions that, when executed by the processing circuit, cause the second server (114) to perform further operations, the further operations comprising:

[0335] receiving (2301) a session-oriented service termination request from a client device (100) having a VAE client (104) to terminate a session-oriented service;

[0336] sending (2303) a session-oriented service termination response to a client device (100) having a VAE client (104), the session-oriented service termination response indicating acceptance of the session-oriented service termination request; and

[0337] A session-oriented service termination notification is sent (2305) to the first server (112).

[0338] 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 operations according to any one of embodiments 27-40.

[0339] Embodiment 57. A computer program product comprising a non-transitory storage medium 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-40.

[0340] Embodiment 58. A method performed by a vehicle-to-everything (V2X) application enabler (VAE) client (104) of a computer device (100), the method comprising:

[0341] receiving (2401) a session-oriented service request from a second server (114), the session-oriented service request including an identification of the VAE client (104), an identification of the session, and a report configuration;

[0342] sending (2403) a session-oriented service response to the second server (114), the session-oriented service response indicating acceptance of the session-oriented service request; and

[0343] A session-oriented service establishment notification is provided (2405) to the V2X application specific client (102).

[0344] Example 59. The method according to Example 58, further comprising:

[0345] receiving (2501) a session-oriented service change request from a second server (114);

[0346] sending (2503) a session-oriented service change notification to the second server (114), the session-oriented service change notification indicating acceptance of the session-oriented service change request; and

[0347] A session-oriented service change notification is provided (2505) to the V2X application specific client (102).

[0348] Example 60. The method according to Example 58, further comprising:

[0349] 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 to server information; and

[0350] A session-oriented service change response is received (2603) from the second server (114), the session-oriented service change response indicating acceptance of the session-oriented service change request.

[0351] Example 61. The method according to Example 58, further comprising:

[0352] receiving (2701) a session-oriented service termination request from a second server (114);

[0353] sending (2703) a session-oriented service termination response to the second server (114), the session-oriented service termination response indicating acceptance of the session-oriented service termination request; and

[0354] A session-oriented service termination notification is provided (2705) to the V2X application specific client.

[0355] Embodiment 62. The method according to any one of embodiments 58-60, further comprising:

[0356] sending (2801) a session-oriented service termination request to the second server (114); and

[0357] A session-oriented service termination response is received (2803) from the second server (114), the session-oriented service termination response indicating acceptance of the session-oriented service termination request.

[0358] Embodiment 63. The method according to embodiment 62, wherein sending the session-oriented service termination request comprises: sending the session-oriented service termination request in response to receiving a session-oriented service termination trigger request from a V2X application-specific client.

[0359] Embodiment 64. A vehicle-to-everything (V2X) application enabler (VAE) client (104), adapted to perform operations, the operations comprising:

[0360] receiving (2401) a session-oriented service request from a second server (114), the session-oriented service request including an identification of the VAE client (104), an identification of the session, and a report configuration;

[0361] sending (2403) a session-oriented service response to the second server (114), the session-oriented service response indicating approval of the session-oriented service request; and

[0362] A session-oriented service establishment notification is provided (2405) to the V2X application specific client.

[0363] Embodiment 65. The VAE client (104) of embodiment 64, wherein the VAE client (104) is adapted to perform operations according to any one of embodiments 59-63.

[0364] Embodiment 66. A vehicle-to-everything (V2X) application enabler (VAE) client (104), comprising:

[0365] processing circuit (1003); and

[0366] A memory (1005) coupled to the processing circuitry, wherein the memory includes instructions that, when executed by the processing circuitry, cause the VAE client (104) to perform operations comprising:

[0367] receiving (2401) a session-oriented service request from a second server (114), the session-oriented service request including an identification of the VAE client (104), an identification of the session, and a report configuration;

[0368] sending (2403) a session-oriented service response to the second server (114), the session-oriented service response indicating approval of the session-oriented service request; and

[0369] A session-oriented service establishment notification is provided (2405) to the V2X application specific client.

[0370] Embodiment 67. The VAE client (104) of embodiment 66, wherein the memory comprises further instructions that, when executed by the processing circuit, cause the VAE client (104) to perform further operations, the further operations comprising:

[0371] receiving (2501) a session-oriented change request from a second server (114);

[0372] sending (2503) a session-oriented change notification to the second server (114), the session-oriented change notification indicating acceptance of the session-oriented change request; and

[0373] A session-oriented service change notification is provided (2505) to the V2X application specific client (102).

[0374] Embodiment 68. The VAE client (104) of embodiment 66, wherein the memory comprises further instructions that, when executed by the processing circuit, cause the VAE client (104) to perform further operations, the further operations comprising:

[0375] sending (2601) a session-oriented service change request to a second server (114), the session-oriented service update request including one or more updates to service information or changes to server information; and

[0376] A change response is received (2603) from the second server (114), the change response indicating acceptance of the session-oriented service change request.

[0377] Embodiment 69. The VAE client (104) of embodiment 66, wherein the memory comprises further instructions that, when executed by the processing circuit, cause the VAE client (104) to perform further operations, the further operations comprising:

[0378] receiving (2701) a session-oriented service termination request from a second server (114);

[0379] sending (2703) a session-oriented service termination response to the second server (114), the session-oriented service termination response indicating approval of the session-oriented service termination request; and

[0380] A session-oriented service termination notification is provided (2705) to the V2X application specific client (102).

[0381] Embodiment 70. The VAE client (104) of embodiment 66, wherein the memory comprises further instructions that, when executed by the processing circuit, cause the VAE client (104) to perform further operations, the further operations comprising:

[0382] sending (2801) a session-oriented service termination request to the second server (114); and

[0383] A session-oriented service termination response is received (2803) from the second server (114), the session-oriented service termination response indicating approval of the session-oriented service termination request.

[0384] Embodiment 71. The VAE client (104) of embodiment 70, wherein sending the session-oriented service termination request comprises sending the session-oriented service termination request in response to receiving a session-oriented termination trigger request from the V2X application-specific client (102).

[0385] Embodiment 72. A computer program comprising program code to be executed by a processing circuit (1003) of a vehicle-to-everything (V2X) application enabler (VAE) client (104), whereby execution of the program code causes the VAE client (104) to perform operations according to any one of embodiments 58-63.

[0386] Embodiment 73. A computer program product comprising a non-transitory storage medium comprising program code to be executed by a processing circuit (1003) of a vehicle-to-everything (V2X) application enabler (VAE) client (104), whereby execution of the program code causes the VAE client (104) to perform operations according to any one of embodiments 58-63. Various abbreviations / acronyms used in this disclosure are explained below.

[0387] Abbreviation Explanation

[0388] 3GPP Third Generation Partnership Project

[0389] 5G 5th Generation

[0390] Base stations in gNB NR

[0391] ITS Intelligent Transportation System

[0392] ITS-S ITS Station

[0393] KPI Key Performance Indicator

[0394] NR New Radio

[0395] QoS Quality of Service

[0396] RAN Radio Access Network

[0397] RAT Radio Access Technology

[0398] RD Remote Driving

[0399] SEAL Service Enablement Architecture Layer

[0400] TeSo Remote Operations Support

[0401] ToD Remote Control Driving

[0402] VAE V2X Application Enabler

[0403] VAL Vertical Application Layer

[0404] V2N Vehicle to Network

[0405] V2X Vehicle to Everything

[0406] V2X AS V2X application server

[0407] V2X UE V2X User Equipment

[0408] UE User Equipment

[0409] References are listed below.

[0410] 1.3GPP TS 23.286, Application layer support for V2X services; functional architecture and information flows, V16.1.0, June 2019.

[0411] 2. 3GPP TS 23.434, Service Enabler Architecture Layer for Vertical Services; Functional Architecture and Information Flow, V16.1.0, June 2019.

[0412] 3GPP TR 23.795, Study on Application Layer Support for V2X Services, V16.0.0, September 2018.

[0413] 4. 3GPP TR 23.764, Study on Enhancements for Application Layer Support of V2X Services, V0.5.0, February 2020.

[0414] 5. 3GPP TR 22.886, Study on Enhancements to 3GPP Support for 5G V2X Services, V16.2.0, December 2018.

[0415] 6. 3GPP TS 22.186, Enhanced Service Requirements for V2X Scenario, V16.2.0, June 2019.

[0416] 7. 5GAA T-190028, 5G Automotive Association; Working Group Use Cases and Technical Requirements; 5G Use Cases and Requirements – Wave 2.1; V1.0 (2019 / 01 / 30).

[0417] 8.5GAA XWG5-190009 Work item description, requirements and architecture for remote control driving.

[0418] Additional instructions are provided below.

[0419] Generally, all terms used in this article will be interpreted according to their ordinary meaning in the relevant technical field, unless clearly given different meanings and / or implied different meanings in the context of using it. Unless otherwise clearly stated, all references to elements, devices, components, methods, steps, etc. will be openly interpreted as referring to at least one instance in elements, devices, components, methods, steps, etc. The steps of any method disclosed herein are not necessarily performed in the exact order disclosed, unless steps are clearly described as being after or before another step and / or implying that steps must be after or before another step. As long as it is appropriate, any feature of any embodiment disclosed herein may be applicable to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. From the following description, other objects, features and advantages of the disclosed embodiments will be apparent.

[0420] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are 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 set forth herein; rather, these embodiments are provided merely as examples to convey the scope of the subject matter to those skilled in the art.

[0421] Figure 29 A wireless network according to some embodiments is described.

[0422] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks (e.g., Figure 29 For simplicity, Figure 29 The wireless network shown in FIG. 4 only depicts 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 devices, V2X user devices, etc.). In practice, the wireless network may also include any additional elements suitable for supporting communications between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). Of the components shown, network node 4160 and wireless device (WD) 4110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices to access the wireless network and / or use services provided by or via the wireless network.

[0423] A wireless network may include 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. Thus, particular embodiments of a wireless network may implement communication 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 IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-wave, and / or ZigBee standards.

[0424] Network 4106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), 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 to enable communication between devices.

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

[0426] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio 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 can be classified based on the coverage they provide (or in other words, their transmit power levels), and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. 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 also referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Part of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (e.g., an MSR base station), a network controller (e.g., a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., an MSC, an MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., an 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 detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to implement and / or provide access to a wireless network to a wireless device or to provide a service to a wireless device that has accessed the wireless network.

[0427] exist Figure 29 In FIG, network node 4160 includes processing circuitry 4170, device-readable medium 4180, interface 4190, auxiliary device 4184, power supply 4186, power supply circuitry 4187, and antenna 4162. Figure 29The network node 4160 shown in the example wireless network may represent a device that includes the combination of hardware components shown, however, other embodiments may include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Moreover, although the components of the network node 4160 are depicted as a single box within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up the single shown component (e.g., the device readable medium 4180 may include multiple separate hard drives and multiple RAM modules).

[0428] Similarly, network node 4160 may include 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 its own corresponding components. In certain scenarios where network node 4160 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, each unique Node B and RNC pair may be considered a single, separate network node in some instances. In some embodiments, network node 4160 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (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). Network node 4160 may also include multiple sets of various illustrated components for different wireless technologies integrated into network node 4160, such as, for example, GSM, Wideband Code Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets within network node 4160 .

[0429] The processing circuitry 4170 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuitry 4170 may include processing information obtained by the processing circuitry 4170 (e.g., by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information), and making a determination as a result of the processing.

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

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

[0432] In certain 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 processing circuitry 4170 executing instructions stored on device-readable medium 4180 or memory within processing circuitry 4170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4170 without executing instructions stored on a separate or independent device-readable medium, such as in a hardwired manner. In any of those embodiments, processing circuitry 4170 may be configured to perform the described functionality regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited solely to processing circuitry 4170 or other components of network node 4160, but are enjoyed by network node 4160 as a whole and / or generally by end users and wireless networks.

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

[0434] Interface 4190 is used in wired or wireless communication of signaling and / or data between network node 4160, network 4106, and / or WD 4110. As shown, interface 4190 includes, for example, (one or more) ports / (one or more) terminals 4194 for sending data to network 4106 and receiving data from network 4106 via a wired connection. Interface 4190 also includes radio front-end circuitry 4192, which can be coupled to antenna 4162 or, in certain embodiments, is part of antenna 4162. Radio front-end circuitry 4192 includes filter 4198 and amplifier 4196. Radio front-end circuitry 4192 can be connected to antenna 4162 and processing circuitry 4170. Radio front-end circuitry can be configured to condition the signals transmitted between antenna 4162 and processing circuitry 4170. Radio front-end circuitry 4192 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 4192 can use a combination of filters 4198 and / or amplifiers 4196 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 can collect the radio signal, which is then converted into digital data by the radio front-end circuit 4192. The digital data can be passed to the processing circuit 4170. In other embodiments, the interface may include different components and / or different combinations of components.

[0435] In certain alternative embodiments, the network node 4160 may not include a separate radio front-end circuit 4192; instead, the processing circuit 4170 may include the radio front-end circuit and may be connected to the antenna 4162 without the need for 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 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 the baseband processing circuit 4174, which is part of the digital unit (not shown).

[0436] Antenna 4162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 4162 may be coupled to radio front-end circuitry 4192 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 4162 may include one or more omnidirectional, sectored, or flat panel antennas operable to, for example, send / receive radio signals between 2 GHz and 66 GHz. Omnidirectional antennas can be used to send / receive radio signals in any direction, sectored antennas can be used to send / receive radio signals from devices within a specific area, and flat panel antennas can be line-of-sight antennas for sending / receiving radio signals in a relatively straight line. In some instances, using more than one antenna may be referred to as MIMO. In certain embodiments, antenna 4162 may be separate from network node 4160 and may be connected to network node 4160 via an interface or port.

[0437] Antenna 4162, interface 4190 and / or processing circuit 4170 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 4162, interface 4190 and / or processing circuit 4170 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

[0438] Power circuit 4187 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 4160 for performing the functions described herein. Power circuit 4187 may receive power from power source 4186. Power source 4186 and / or power circuit 4187 may be configured to provide power to the various components of network node 4160 in a form appropriate for the respective components (e.g., at the voltage and current levels required by each respective component). Power source 4186 may be included in power circuit 4187 and / or network node 4160, or may be external to power circuit 4187 and / or network node 4160. For example, network node 4160 may be connected to an external power source (e.g., an electrical outlet) via an input circuit or interface (such as a cable), whereby the external power source provides power to power circuit 4187. As another example, power supply 4186 may include a power source in the form of a battery or battery pack connected to or integrated into 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.

[0439] Alternative embodiments of network node 4160 may include, in addition to Figure 29 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of the network node, including any of the functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 4160 may include a user interface device that allows information to be input into the network node 4160 and information to be output from the network node 4160. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 4160.

[0440] As used herein, a wireless device (WD) refers to a device that is capable of, configured, arranged, and / or operable to communicate wirelessly with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with user equipment (UE) herein. Communicating wirelessly may involve sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through the air. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network according to 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, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, V2X application enabler clients, and the like. WDs may support device-to-device (D2D) communication, for example by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in such cases may be referred to as D2D communication devices. As another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD may be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, the WD may be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering equipment (such as power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle-connected or other device that is capable of monitoring and / or reporting its operating status or other functions associated with its operation. As described above, the WD may represent an endpoint of a wireless connection, in which case it may be referred to as a wireless terminal. In addition, as described above, the WD may be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

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

[0442] Antenna 4111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and connected to interface 4114. In certain alternative embodiments, antenna 4111 may be separated from WD 4110 and may be connected to WD 4110 via an interface or port. Antenna 4111, interface 4114, and / or processing circuit 4120 may be configured to perform any receive or transmit operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the radio front-end circuit and / or antenna 4111 may be considered an interface.

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

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

[0445] As shown, processing circuitry 4120 includes one or more of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In certain embodiments, processing circuitry 4120 of WD 4110 may include an SOC. In some embodiments, RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be on separate chips or chipsets. In alternative embodiments, part or all of baseband processing circuitry 4124 and application processing circuitry 4126 may be combined into a single chip or chipset, and RF transceiver circuitry 4122 may be on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry 4122 and baseband processing circuitry 4124 may be on the same chip or chipset, and application processing circuitry 4126 may be on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be combined in a single chip or chipset. In some embodiments, RF transceiver circuitry 4122 may be part of interface 4114. RF transceiver circuitry 4122 may condition RF signals for processing circuitry 4120.

[0446] In certain embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit 4120 executing instructions stored on a device-readable medium 4130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 4120 without executing instructions stored on a separate or independent device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit 4120 may be configured to perform the described functions regardless of whether the instructions stored on the device-readable storage medium are executed. The benefits provided by such functionality are not limited solely to the processing circuit 4120 or other components of the wireless device 4110, but are enjoyed by the WD 4110 as a whole and / or generally by the end user and the wireless network.

[0447] The processing circuitry 4120 may be configured to perform any determinations, calculations, or similar operations (e.g., certain acquisition operations) described herein as being performed by the WD. Such operations, as performed by the processing circuitry 4120, may include processing information obtained by the processing circuitry 4120 (e.g., by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by the WD 4110, and / or performing one or more operations based on the obtained information or the converted information), and making determinations as a result of the processing.

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

[0449] The user interface device 4132 can provide components that allow a human user to interact with the WD 4110. Such interactions can take many forms, such as visual, auditory, tactile, etc. The user interface device 4132 can be operable to generate output to the user and allow the user to provide input to the WD 4110. The type of interaction can vary depending on the type of user interface device 4132 installed in the WD 4110. For example, if the WD 4110 is a smart phone, the interaction can be via a touch screen; if the WD 4110 is a smart meter, the interaction can be through a screen that provides usage (e.g., the 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 information to be input into the WD 4110 and is connected to the processing circuit 4120 to allow the processing circuit 4120 to process the input information. User interface device 4132 may include, for example, a microphone, proximity or other sensor, key / button, touch display, one or more cameras, USB port or other input circuit. User interface device 4132 is also configured to allow output of information from WD 4110 and allow processing circuit 4120 to output information from WD 4110. User interface device 4132 may include, for example, a speaker, display, vibration circuit, USB port, headphone jack or other output circuit. Using one or more input and output interfaces, devices and circuits of user interface device 4132, WD 4110 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.

[0450] Auxiliary devices 4134 are operable to provide more specific functions that may not typically be performed by a WD. This 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 auxiliary devices 4134 may vary depending on the embodiment and / or scenario.

[0451] In some embodiments, power source 4136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. WD 4110 may also include power circuitry 4137 for delivering power from power source 4136 to various components of the WD that require power from power source 4136 to perform any functions described or indicated herein. In some embodiments, power circuitry 4137 may include power management circuitry. Power circuitry 4137 may additionally or alternatively be operable to receive power from an external power source; in this case, WD 4110 may be connected to an external power source (such as an electrical outlet) via an input circuit or an interface such as a power cable. In some embodiments, power circuitry 4137 may also be operable to deliver power from the external power source to power source 4136. This may be used, for example, to charge power source 4136. Power circuitry 4137 may perform any formatting, conversion, or other modifications to the power from power source 4136 to produce power suitable for powering the corresponding components of WD 4110.

[0452] Figure 30 A user equipment according to some embodiments is shown.

[0453] Figure 30 One embodiment of a UE according to various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user owning and / or operating the associated equipment. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 4200 may be a UE identified by the Third Generation Partnership Project (3GPP), including an NB-loT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 30 As shown, UE 4200 is an example of a WD configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE can be used interchangeably. Therefore, although Figure 30 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0454] exist Figure 30In the embodiment, UE 4200 includes a processing circuit 4201, which is operatively coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connection interface 4211, a memory 4215 (including a random access memory (RAM) 4217, a read-only memory (ROM) 4219, and a storage medium 4221, etc.), a communication subsystem 4231, a power supply 4233, and / or any other components, or any combination thereof. The storage medium 4221 includes an operating system 4223, an application 4225, and data 4227. In other embodiments, the storage medium 4221 may include other similar types of information. Some UEs may utilize Figure 30 All components shown or only a subset of the components. The degree of integration between components may vary depending on the UE. Furthermore, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0455] exist Figure 30 In the embodiment of the present invention, processing circuit 4201 can be configured to process computer instructions and data. Processing circuit 4201 can be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as microprocessors or digital signal processors (DSPs), together 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.

[0456] In the depicted embodiment, the input / output interface 4205 can be configured to provide a communication interface to an input device, an output device, or both. The UE 4200 can be configured to use an output device via the input / output interface 4205. The output device can use the same type of interface port as the input device. For example, a USB port can be used to provide input to and output from the UE 4200. The output device can be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 4200 can be configured to use an input device via the input / output interface 4205 to allow a user to capture information into the UE 4200. The input device can include a contact-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 can include a capacitive or resistive touch sensor that senses input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0457] exist Figure 30 In the embodiment of the present invention, the RF interface 4209 can be configured to provide a communication interface to the RF components (such as a transmitter, a receiver, and an antenna). The network connection interface 4211 can be configured to provide a communication interface to the network 4243a. The network 4243a can cover 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 telecommunications network, another similar network, or any combination thereof. For example, the network 4243a may include a Wi-Fi network. The network connection interface 4211 can be configured to include a receiver and transmitter interface for communicating with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 4211 can implement receiver and transmitter functions suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.

[0458] The RAM 4217 can 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 operating systems, applications, and device drivers). The ROM 4219 can be configured to provide computer instructions or data to the processing circuit 4201. For example, the ROM 4219 can be configured to store constant low-level system code or data for basic system functions (such as basic input and output (I / O), startup, or receiving keystrokes from a keyboard stored in non-volatile memory). The storage medium 4221 can be configured to include a memory such as a RAM, a ROM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic disk, an optical disk, a floppy disk, a hard disk, a removable disk, or a flash drive. In one example, the storage medium 4221 may be configured to include an operating system 4223, an application 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.

[0459] Storage medium 4221 can be configured to include multiple 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 drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, smart card memory (such as a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. Storage medium 4221 can allow UE 4200 to access computer-executable instructions, applications, etc. stored on a temporary or non-transitory storage medium to download or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) can be tangibly embodied in storage medium 4221, which can include device-readable media.

[0460] exist Figure 30In the embodiment, processing circuit 4201 can be configured to communicate with network 4243b using communication subsystem 4231. Network 4243a and network 4243b can be the same network(s) or different networks(s). Communication subsystem 4231 can be configured to include one or more transceivers for communicating with network 4243b. For example, communication subsystem 4231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication (such as another WD, UE, or a base station of a radio access network (RAN)) according to one or more communication protocols (such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, Universal Terrestrial Radio Access Network (UTRAN), WiMax, etc.). Each transceiver can include a transmitter 4233 and / or a receiver 4235 that respectively implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for a RAN link. Further, the transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0461] In the illustrated embodiment, the communication functionality of the communication subsystem 4231 may include data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth, near-field communication), location-based communication (such as using a global positioning system (GPS) to determine location), another similar communication functionality, or any combination thereof. For example, the communication subsystem 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 4243a may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications 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.

[0462] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 4200 or may be divided across multiple components of UE 4200. Furthermore, the features, benefits, and / or functions 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 via the bus 4202. In another example, any such component may be represented by program instructions stored in a memory that, when executed by the processing circuit 4201, perform the corresponding functions described herein. In another example, the functions of any such component may be divided between the processing circuit 4201 and the communication subsystem 4231. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0463] Figure 31 A virtualized environment is shown in accordance with some embodiments.

[0464] Figure 31 4300 is a system block diagram illustrating a virtualized environment 4300 that can virtualize the functions implemented by some embodiments. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage device, and network resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and involves at least a portion of a function being implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0465] 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. Further, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0466] 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.), which are operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Applications 4320 run in a virtualized environment 4300, which provides hardware 4330 including processing circuitry 4360 and memory 4390. Memory 4390 contains instructions 4395 executable by processing circuitry 4360, whereby applications 4320 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

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

[0468] The virtual machine 4340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of instances of the virtual device 4320 can be implemented on one or more virtual machines 4340, and these implementations can be done in different ways.

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

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

[0471] Virtualization of hardware is sometimes referred to as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, both in data centers and at customer premises.

[0472] In the context of NFV, a virtual machine 4340 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 4340 and the portion of hardware 4330 that executes the virtual machine (i.e., hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 4340) form a separate virtual network element (VNE).

[0473] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 4340 on top of the hardware network infrastructure 4330 and corresponds to Figure 31 Application 4320.

[0474] 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 nodes 4330 via one or more appropriate network interfaces and may be combined with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

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

[0476] Figure 32 A telecommunications network is shown connected to a host computer via an intermediary network in accordance with some embodiments.

[0477] refer to Figure 32According to an embodiment, a communication system includes a telecommunications network 4410, such as a 3GPP-type cellular network, which includes an access network 4411 (such as a radio 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 base station 4412a, 4412b, 4412c defines a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c can be connected to the core network 4414 via a wired or wireless connection 4415. A first UE 4491 located in the coverage area 4413c is configured to be wirelessly connected to or called 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 also applicable to situations where a single UE is in the coverage area or a single UE is connected to the corresponding base station 4412.

[0478] The telecommunications network 4410 itself is connected to a host computer 4430, which may be embodied in the hardware and / or software of a standalone server, a cloud-enabled server, a distributed server, or as a processing resource in a server farm. The host computer 4430 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 4421 and 4422 between the telecommunications network 4410 and the host computer 4430 may extend directly from the core network 4414 to the host computer 4430, or may be made via an optional intermediate network 4420. The intermediate network 4420 may be one of a public, private, or managed network, or a combination of more than one of these networks; if present, the intermediate network 4420 may be a backbone network or the Internet; in particular, the intermediate network 4420 may include two or more subnetworks (not shown).

[0479] Figure 32The communication system as a whole enables connectivity between connected UEs 4491, 4492 and a host computer 4430. This connectivity can be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the 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 can be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes are unaware of the routing of uplink and downlink communications. For example, the base station 4412 may not or need not be informed of the past routing of incoming downlink communications with data originating from the host computer 4430 to be forwarded (e.g., handed over) to the connected UE 4491. Similarly, base station 4412 does not need to be aware of the future routing of outgoing uplink communications originating from UE 4491 toward host computer 4430.

[0480] Figure 33 A host computer is shown communicating with a user device via a base station over a partially wireless connection according to some embodiments.

[0481] Now refer to Figure 33 Describe the example implementations of the UE, base station, and host computer discussed in the previous paragraphs according to the embodiments. In the communication system 4500, the host 4510 includes hardware 4515, which includes a communication interface 4516 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system 4500. The host computer 4510 also includes a processing circuit 4518, which may have storage and / or processing capabilities. In particular, the processing circuit 4518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The host computer 4510 also includes software 4511, which is stored in the host computer 4510 or can be accessed by the host computer 4510 and can be executed by the processing circuit 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 connected via an OTT connection 4550 terminated at the UE 4530 and the host computer 4510. In providing services to the remote user, the host application 512 may provide user data sent using the OTT connection 4550.

[0482] The communication system 4500 also includes a base station 4520 that is provided in the telecommunications system and includes 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 communication interface 4526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 4500, and for establishing and maintaining connections with at least the terminals located in the coverage area (in the coverage area) served by the base station 4520. Figure 33 The communication interface 4526 may be configured to facilitate a connection 4560 to the host computer 4510. The connection 4560 may be direct, or it may pass through a core network of the telecommunications system (in the example embodiment). Figure 33 (not shown) and / or one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 4525 of the base station 4520 also includes processing circuitry 4528, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The base station 4520 also includes software 4521 stored internally or accessible via an external connection.

[0483] The communication system 4500 also includes the UE 4530 mentioned above. Its hardware 4535 may include a radio interface 4537 configured to establish 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 also includes processing circuitry 4538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination of these suitable for executing instructions (not shown). The UE 4530 also includes software 4531, which is stored in the UE 4530 or accessible by the UE 4530 and executable by the processing circuitry 4538. The software 4531 includes a client application 4532. The client application 4532 may be operable to provide services to human or non-human users via the UE 4530 with the support of the host computer 4510. In the host computer 4510, a host application 4512 executing therein can communicate with a client application 4532 executing therein via an OTT connection 4550 terminated at the UE 4530 and the host computer 4510. When providing a service to a user, the client application 4532 can receive request data from the host application 4512 and provide user data in response to the request data. The OTT connection 4550 can transmit both the request data and the user data. The client application 4532 can interact with the user to generate the user data it provides.

[0484] It should be noted that Figure 33The host computer 4510, base station 4520 and UE 4530 shown can be respectively Figure 32 The host computer 4430, one of the base stations 4412a, 4412b, 4412c and one of the UEs 4491, 4492 are similar or identical. That is, the internal workings of these entities may be similar to Figure 33 shown, and independently, the surrounding network topology can be Figure 32 network topology.

[0485] exist Figure 33 In FIG, OTT connection 4550 has been abstractly drawn to illustrate communication between host computer 4510 and UE 4530 via base station 4520, without explicitly referencing any intermediate devices and the precise routing of messages through these devices. The network infrastructure can determine the routing, which can be configured to conceal the routing from UE 4530, the service provider operating host computer 4510, or both. While OTT connection 4550 is active, the network infrastructure can also take decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0486] The wireless connection 4570 between the UE 4530 and the base station 4520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 4530 using the wireless connection 4570 to form the last leg of the OTT connection 4550. More specifically, the teachings of these embodiments can increase random access speed and / or reduce random access failure rate, thereby providing benefits such as faster and / or more reliable random access.

[0487] A measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. An optional network function may also be provided for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to changes in measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 4550 may be implemented in the software 4511 and hardware 4515 of the host computer 4510, or in the software 4531 and hardware 4535 of the UE 4530, or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with the communication device through which the OTT connection 4550 passes; the sensor may participate in the measurement process by supplying values ​​for the monitored quantities exemplified above, or supplying values ​​for other physical quantities from which the software 4511, 4531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 4550 may include message formats, retransmission settings, preferred routes, and the like; the reconfiguration need not affect the base station 4520, and the reconfiguration may be unknown or imperceptible to the base station 4520. Such processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc., by the host computer 4510. The measurements may be achieved because the software 4511 and 4531 cause messages (particularly empty or "dummy" messages) to be sent using the OTT connection 4550 while monitoring propagation time, errors, etc.

[0488] Figure 34 A method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown.

[0489] Figure 34 is a flow chart showing 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 a reference Figure 32 and Figure 33 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Figure 34 . 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), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0490] Figure 35 A method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown.

[0491] Figure 35 is a flow chart showing 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 a reference Figure 32 and Figure 33 For the sake of simplicity of this disclosure, only the host computer, base station and UE are included in this section. Figure 35 . 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. According to the teachings of the embodiments described throughout this disclosure, the transmission may be delivered via a base station. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0492] Figure 36 A method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown.

[0493] Figure 36 is a flow chart showing 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 a reference Figure 32 and Figure 33 For the sake of simplicity of this disclosure, only the host computer, base station and UE are included in this section. Figure 36 . 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 user data by executing a client application. In sub-step 4811 (which may be optional) of step 4810, the UE executes the client application, which provides user data as a reaction to the received input data provided by the host computer. When providing user data, the executed client application may also take into account user input received from the user. Regardless of the specific manner in which the user data is provided, in sub-step 4830 (which may be optional), the UE initiates transmission of the user data to the host computer. In step 4840 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0494] Figure 37A method implemented in a communication system including a host computer, a base station, and a user equipment according to some embodiments is shown.

[0495] Figure 37 is a flow chart showing 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 a reference Figure 32 and Figure 33 For the sake of simplicity of this disclosure, only the host computer, base station and UE are included in this section. Figure 37 . In step 4910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 4920 (which may be optional), the base station initiates a 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.

[0496] Any appropriate steps, methods, features, functions or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented by processing circuits, which may include one or more microprocessors or microcontrollers and other digital hardware (which may include digital signal processors (DSPs), dedicated digital logic, etc.). The processing circuit may be configured to execute program code stored in a memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory device, optical storage device, etc. In multiple embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more of the technologies described herein. In some embodiments, the processing circuit may be used to cause each functional unit to perform the corresponding functions according to one or more embodiments of the present invention.

[0497] The term unit may have the conventional meaning in the field of electronic devices, electrical equipment, and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output, and / or display functions, etc., such as those described herein.

[0498] Further definitions and examples are discussed below.

[0499] In the description of the various embodiments of the above inventive concept, it should be understood that the terms used herein are only used to describe the purpose of specific embodiments and are not intended to limit the inventive concept. Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meanings as commonly understood by those of ordinary skill in the art to which the inventive concept belongs. It should be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of this specification and related technology, and unless clearly defined herein, will not be interpreted in an idealized or overly formal sense.

[0500] When an element is referred to as being "connected," "coupled," "responsive" or variations thereof to another element, it may be directly connected, coupled or responsive to the other element, or there may be intermediate elements. In contrast, when an element is referred to as being "directly connected," "directly coupled," "directly responsive" or variations thereof to another element, there are no intermediate elements. Similar numbers refer to similar elements throughout the text. In addition, "coupling," "connecting," "responsive" or variations thereof used in this article may include wireless coupling, connection or response. As used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms, unless the context clearly indicates otherwise. For the sake of brevity and / or clarity, well-known functions or structures may not be described in detail. The term "and / or" (abbreviated as " / ") includes any and all combinations of one or more of the associated listed items.

[0501] It will be understood that although the terms first, second, third, etc. may be used to describe various elements / operations in this article, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another element / operation. Therefore, without departing from the teachings of the present invention, the first element / operation in some embodiments may be referred to as the second element / operation in other embodiments. The same reference numerals or the same reference identifiers represent the same or similar elements throughout the text.

[0502] As used herein, the terms "comprises," "comprising," "having," or variations thereof are open ended and include one or more stated features, integers, elements, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Furthermore, as used herein, the general abbreviation "e.g.," derived from the Latin phrase "exampligratia," may be used to introduce or specify one or more general examples of aforesaid items without intending to limit such items. The common abbreviation "ie," derived from the Latin phrase "id est," may be used to specify a specific item from a more general enumeration.

[0503] Example embodiments are described herein with reference to block diagrams and / or flowcharts of computer-implemented methods, apparatus (systems and / or devices), and / or computer program products. It will be understood that the blocks of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to a processor circuit of a general-purpose computer circuit, a special-purpose computer circuit, and / or other programmable data processing circuit to produce a machine so that instructions, which are executed via a processor of a computer and / or other programmable data processing device, transform and control transistors, values ​​stored in memory locations, and other hardware components in such circuits to implement the functions / actions specified in the block diagrams and / or (one or more) flowchart blocks, thereby creating a device (function) and / or structure for implementing the functions / behaviors specified in the block diagrams and / or (one or more) flowchart blocks.

[0504] These computer program instructions may also be stored in a tangible computer-readable medium that can instruct a computer or other programmable data processing apparatus to operate in a specific manner so that the instructions stored in the computer-readable medium produce an article of manufacture including instructions for implementing the functions / actions specified in the block diagram and / or (one or more) flowchart blocks. Thus, embodiments of the inventive concept 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 are collectively referred to as "circuits," "modules," or variations thereof.

[0505] It should also be noted that in some alternative implementations, the functions / actions noted in the blocks may not occur in the order noted in the flow chart. For example, two blocks shown in succession may actually be performed substantially simultaneously, or may sometimes be performed in reverse order, depending on the functions / actions involved. In addition, the functions of a given block of a flow chart and / or block diagram may be divided into multiple blocks, and / or the functions of two or more blocks of a flow chart and / or block diagram may be at least partially integrated. Finally, other blocks may be added / inserted between the blocks shown, and / or blocks / operations may be omitted without departing from the scope of the present invention. In addition, although some figures include arrows on communication paths to show the primary direction of communication, it should be understood that communication may occur in the direction opposite to the arrows shown.

[0506] In the case of not departing substantially from the principle of the present invention concept, many changes and modifications can be made to the embodiment. All such deformations and modifications are included in the scope of the present invention concept. Therefore, the subject matter disclosed above should be regarded as illustrative, not restrictive, and the examples of the embodiments are intended to cover all such modifications, enhancements and other embodiments, which fall within the spirit and scope of the present invention concept. Therefore, to the maximum extent permitted by law, the scope of the present invention concept will be determined by the most widely permitted interpretation of the present disclosure, including the embodiments and their equivalent examples, and should not be bound or limited by the above-mentioned specific embodiments.

Claims

1. A method, performed by a vehicle-to-everything (V2X) application-specific server, for supporting a session-oriented service for a vehicle, the method comprising: Sending a session-oriented service trigger request to the V2X application enabler (VAE) server to initiate a session-oriented service for the VAE client of the V2X user equipment; receiving a session-oriented service trigger response from the VAE server, the session-oriented service trigger response indicating whether the VAE server has the capability to initiate a session-oriented service with the VAE client; receiving a session-oriented service establishment notification from the VAE server, the session-oriented service establishment notification indicating that a session-oriented service has been established; Sending a session-oriented service change trigger request to the VAE server, where the session-oriented service change trigger request includes an identifier of a session of the session-oriented service and an update of a QoS requirement of the session; as well as A session-oriented service change trigger response is received from the VAE server, the session-oriented service change trigger response indicating whether the VAE server can continue the session-oriented service with the updated QoS requirement.

2. The method according to claim 1, wherein Sending the session-oriented service triggering request includes sending the session-oriented service triggering request having information associated with the session-oriented service.

3. The method according to claim 2, wherein: The information includes one or more of the following: an identifier of the VAE client, an identifier of the V2X application-specific server, the identifier of the session, and a type of session-oriented service or a quality of service (QoS) requirement.

4. The method according to any one of claims 1 to 3, wherein The session-oriented service change trigger request includes a change in server information; and The session-oriented service change trigger response from the VAE server indicates whether the VAE server can continue the session-oriented service with the changed server information.

5. The method according to any one of claims 1 to 3, further comprising: A session-oriented service change notification is received from the VAE server.

6. The method according to any one of claims 1 to 3, further comprising: Sending a session-oriented service termination trigger request to the VAE server to terminate the session-oriented service; as well as A session-oriented service termination trigger response is received from the VAE server.

7. The method according to claim 6, further comprising: A session-oriented service termination notification is received from the VAE server.

8. A V2X application-specific server, adapted to perform operations, the operations comprising: Sending a session-oriented service trigger request to the VAE server to initiate a session-oriented service for the VAE client of the V2X user equipment; receiving a session-oriented service trigger response from the VAE server, the session-oriented service trigger response indicating whether the VAE server will initiate a session-oriented service with the VAE client; receiving a session-oriented service establishment notification from the VAE server, the session-oriented service establishment notification indicating that a session-oriented service has been established; Sending a session-oriented service change trigger request to the VAE server, where the session-oriented service change trigger request includes an identifier of a session of the session-oriented service and an update of a QoS requirement of the session; as well as A session-oriented service change trigger response is received from the VAE server, the session-oriented service change trigger response indicating whether the VAE server can continue the session-oriented service with the updated QoS requirement.

9. The V2X application specific server according to claim 8, wherein: Sending the session-oriented service triggering request includes sending the session-oriented service triggering request having information associated with the session-oriented service.

10. The V2X application specific server according to claim 9, wherein: The information includes one or more of the following: an identifier of the VAE client, an identifier of the V2X application-specific server, the identifier of the session, and a type of session-oriented service or a quality of service (QoS) requirement.

11. The V2X application specific server according to any one of claims 8 to 10, wherein: The session-oriented service change trigger request includes a change in server information; and The session-oriented service change trigger response from the VAE server indicates whether the VAE server can continue the session-oriented service with the changed server information.

12. The V2X application specific server according to any one of claims 8 to 10, wherein: The V2X application specific server is further adapted to perform operations including: A session-oriented service change notification is received from the VAE server.

13. The V2X application specific server according to any one of claims 8 to 10, wherein: The V2X application specific server is further adapted to perform operations including: Sending a session-oriented service termination trigger request to the VAE server to terminate the session-oriented service; and A session-oriented service termination trigger response is received from the VAE server.

14. The V2X application specific server according to claim 13, wherein: The V2X application specific server is further adapted to perform operations including: A session-oriented service termination notification is received from the VAE server.

15. A computer program product comprising program code to be executed by a processing circuit of a V2X application specific server, whereby execution of the program code causes the V2X application specific server to: Sending a session-oriented service trigger request to the VAE server to initiate a session-oriented service for the VAE client of the V2X user equipment; receiving a session-oriented service trigger response from the VAE server, the session-oriented service trigger response indicating whether the VAE server will initiate a session-oriented service with the VAE client; receiving a session-oriented service establishment notification from the VAE server, the session-oriented service establishment notification indicating that a session-oriented service has been established; Sending a session-oriented service change trigger request to the VAE server, where the session-oriented service change trigger request includes an identifier of a session of the session-oriented service and an update of a QoS requirement of the session; as well as A session-oriented service change trigger response is received from the VAE server, the session-oriented service change trigger response indicating whether the VAE server can continue the session-oriented service with the updated QoS requirement.

16. The computer program product according to claim 15, comprising further program code to be executed by the processing circuit of the V2X application specific server, whereby execution of the program code causes the V2X application specific server to perform the method according to any one of claims 2 to 7.

17. A method for supporting a session-oriented service for a vehicle, performed by a VAE server communicatively connected to a network, the method comprising: receiving a session-oriented service triggering request from the V2X application specific server to initiate a session-oriented service for the VAE client of the V2X user equipment; sending a session-oriented service trigger response to the V2X application-specific server, where the session-oriented service trigger response indicates whether the VAE server has the capability to initiate a session-oriented service with the VAE client; sending a session-oriented service establishment notification to the V2X application specific server, wherein the session-oriented service establishment notification indicates that a session-oriented service has been established; receiving a session-oriented service change trigger request from the V2X application specific server, the session-oriented service change trigger request including an identifier of a session of the session-oriented service and an update of a QoS requirement of the session; as well as A session-oriented service change trigger response is sent to the V2X application-specific server, where the session-oriented service change trigger response indicates whether the VAE server can continue the session-oriented service with the updated QoS requirement.

18. The method according to claim 17, wherein Receiving the session-oriented service triggering request includes receiving the session-oriented service triggering request having information associated with the session-oriented service.

19. The method according to claim 18, wherein The information includes one or more of the following: an identifier of the VAE client, an identifier of the V2X application-specific server, the identifier of the session, and a type of session-oriented service or a quality of service (QoS) requirement.

20. The method according to any one of claims 17 to 19, further comprising: Sending a session-oriented service request to the VAE client to establish the session-oriented service, the session-oriented service request including an identifier of the VAE client, the identifier of the session, and a report configuration; receiving a session-oriented service response from the VAE client, wherein the session-oriented service response indicates acceptance of the session-oriented service request to establish the session-oriented service; as well as In response to receiving the session-oriented service response indicating acceptance, sending a session-oriented service establishment notification to the V2X application-specific server.

21. The method according to any one of claims 17 to 19, further comprising: In response to determining that the updated QoS requirement can be provided for the session-oriented service; sending a session-oriented service change trigger response to the V2X application specific server, the session-oriented service change trigger response indicating a capability to continue the session-oriented service with the updated QoS requirement; as well as In response to determining that the updated QoS requirement cannot be provided for the session-oriented service; sending a session-oriented service change trigger response to the V2X application-specific server, the session-oriented service change trigger response indicating that the VAE server cannot continue the session-oriented service with the updated QoS requirement.

22. The method according to any one of claims 17 to 19, further comprising: Sending a session-oriented change request to the VAE client, wherein the session-oriented change request includes an update request or a change in server information; receiving a session-oriented change response from the VAE client, the session-oriented change response indicating acceptance of the change request; as well as Sending a session-oriented service change notification to the V2X application-specific server.

23. The method according to any one of claims 17 to 19, further comprising: receiving a session-oriented service termination trigger request from the V2X application-specific server to terminate the session-oriented service from the V2X application-specific server; as well as Sending a session-oriented service termination trigger response to the V2X application specific server.

24. The method according to claim 23, further comprising: Sending a session-oriented service termination request to the VAE client; receiving a session-oriented service termination response from the VAE client, the session-oriented service termination response indicating acceptance of the session termination request; as well as Sending a session-oriented service termination notification to the V2X application specific server.

25. A VAE server, adapted to perform an operation comprising: receiving a session-oriented service triggering request from the V2X application specific server to initiate a session-oriented service for the VAE client of the V2X user equipment; sending a session-oriented service trigger response to the V2X application-specific server, where the session-oriented service trigger response indicates whether the VAE server has the capability to initiate a session-oriented service with the VAE client; sending a session-oriented service establishment notification to the V2X application specific server, wherein the session-oriented service establishment notification indicates that a session-oriented service has been established; receiving a session-oriented service change trigger request from the V2X application specific server, the session-oriented service change trigger request including an identifier of a session of the session-oriented service and an update of a QoS requirement of the session; as well as A session-oriented service change trigger response is sent to the V2X application-specific server, where the session-oriented service change trigger response indicates whether the VAE server can continue the session-oriented service with the updated QoS requirement.

26. The VAE server according to claim 25, wherein: Receiving the session-oriented service triggering request includes receiving the session-oriented service triggering request having information associated with the session-oriented service.

27. The VAE server according to claim 26, wherein: The information includes one or more of the following: an identifier of the VAE client, an identifier of the V2X application-specific server, the identifier of the session, and a type of session-oriented service or a quality of service (QoS) requirement.

28. The VAE server according to any one of claims 25 to 27, wherein: The VAE server is further adapted to perform operations including: Sending a session-oriented service request to the VAE client to establish the session-oriented service, the session-oriented service request including an identifier of the VAE client, the identifier of the session, and a report configuration; receiving a session-oriented service response from the VAE client, wherein the session-oriented service response indicates acceptance of the session-oriented service request to establish the session-oriented service; as well as In response to receiving the session-oriented service response indicating acceptance, sending a session-oriented service establishment notification to the V2X application-specific server.

29. The VAE server according to any one of claims 25 to 27, wherein: The VAE server is further adapted to perform operations including: In response to determining that the updated QoS requirement can be provided for the session-oriented service; sending a session-oriented service change trigger response to the V2X application-specific server, the session-oriented service change trigger response indicating an ability to continue the session-oriented service with the updated QoS requirement; as well as In response to determining that the updated QoS requirement cannot be provided for the session-oriented service; sending a session-oriented service change trigger response to the V2X application-specific server, the session-oriented service change trigger response indicating that the VAE server cannot continue the session-oriented service with the updated QoS requirement.

30. The VAE server according to any one of claims 25 to 27, wherein: The VAE server is further adapted to perform operations including: Sending a session-oriented change request to the VAE client, wherein the session-oriented change request includes an update request or a change in server information; receiving a session-oriented change response from the VAE client, the session-oriented change response indicating acceptance of the change request; as well as Sending a session-oriented service change notification to the V2X application-specific server.

31. The VAE server according to any one of claims 25 to 27, wherein: The VAE server is further adapted to perform operations including: receiving a session-oriented service termination trigger request from the V2X application-specific server to terminate the session-oriented service from the V2X application-specific server; as well as Sending a session-oriented service termination trigger response to the V2X application specific server.

32. The VAE server according to claim 31, wherein: The VAE server is further adapted to perform operations including: Sending a session-oriented service termination request to the VAE client; receiving a session-oriented service termination response from the VAE client, the session-oriented service termination response indicating acceptance of the session termination request; as well as Sending a session-oriented service termination notification to the V2X application specific server.

33. A computer program product comprising program code to be executed by processing circuitry of a VAE server, whereby execution of the program code causes the VAE server to: receiving a session-oriented service triggering request from the V2X application specific server to initiate a session-oriented service for the VAE client of the V2X user equipment; sending a session-oriented service trigger response to the V2X application-specific server, where the session-oriented service trigger response indicates whether the VAE server has the capability to initiate a session-oriented service with the VAE client; sending a session-oriented service establishment notification to the V2X application specific server, wherein the session-oriented service establishment notification indicates that a session-oriented service has been established; receiving a session-oriented service change trigger request from the V2X application specific server, the session-oriented service change trigger request including an identifier of a session of the session-oriented service and an update of a QoS requirement of the session; as well as A session-oriented service change trigger response is sent to the V2X application-specific server, where the session-oriented service change trigger response indicates whether the VAE server can continue the session-oriented service with the updated QoS requirement.

34. A computer program product according to claim 33, comprising further program code to be executed by the processing circuitry of the VAE server, whereby execution of the program code causes the VAE server to perform the method according to any one of claims 18 to 24.

Images