Method for providing v2x application server registration

Abstract

According to some embodiments disclosed herein, a method of operating a vehicle-to-anything, V2X, application enabler, VAE, server is provided. The method includes receiving a registration request message from a V2X application specific server. The method also includes sending a registration response message to the V2X application specific server in response to receiving the registration request message.

Description

[0001] This application is a divisional application of the Chinese patent application "Method for Providing V2X Application Server Registration" with application number 202080091741.9 (application date is October 19, 2020). Technical Field

[0002] The present disclosure relates generally to communications, and more particularly, to communication methods and related devices and nodes that support wireless communications. Background Art

[0003] 3GPP TS23.286 (referred to as reference [1] or [1]) defines the V2X application layer model for V2X communications over PC5 and Uu. Figure 1 The model is shown in FIG. The V2X application enabler (VAE) layer can provide support information to the V2X application.

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

[0005] The V2X application layer functional entities of the V2X UE and the V2X application server may be grouped into a V2X application-specific layer and a VAE layer. The VAE layer may provide VAE capabilities to the V2X application-specific layer. The V2X application layer functional model may use the SEAL service as specified in 3GPP TS 23.434 (referred to as reference [2] or [2]).

[0006] The VAE server can be located in the VAE layer. The SEAL services used by the VAE layer can include location management, group management, configuration management, identity management, key management, and network resource management. The V2X application-specific layer can include V2X application-specific functions.

[0007] The V2X application server can include a VAE server, a SEAL server, and a V2X application-specific server. The VAE server can provide V2X application layer support functions to the V2X application-specific server through the Vs reference point.

[0008] A V2X UE may include a VAE client, a SEAL client, and a V2X application-specific client. The VAE client provides V2X application layer support functions to the V2X application-specific client over the Vc reference point. In some examples, the SEAL client and server entities may be part of the VAE client and VAE server, respectively.

[0009] A VAE client may act as a VAL client for its interaction with a SEAL client, as specified in 3GPP TS 23.434 (reference [2]). A VAE server may act as a VAL server for its interaction with a SEAL server, as specified in 3GPP TS 23.434 (reference [2]).

[0010] In the VAE layer, the VAE client can communicate with the VAE server through the V1-AE reference point. In the V2X application-specific layer, the V2X application-specific client can communicate with the V2X application-specific server through the V1 application (V1-APP) reference point.

[0011] In the VAE layer, the VAE client of V2X UE2 can communicate with the VAE client of V2X UE1 through the V5-AE reference point. In the V2X application-specific layer, the V2X application-specific client of V2X UE2 can communicate with the VAE client of V2X UE1 through the V5 application (V5-APP) reference point.

[0012] The following SEAL services for V2X applications are supported: location management as specified in 3GPP TS 23.434 [2]; group management as specified in 3GPP TS 23.434 [2]; configuration management as specified in 3GPP TS 23.434 [2]; identity management as specified in 3GPP TS 23.434 [2]; key management as specified in 3GPP TS 23.434 [2]; and network resource management as specified in 3GPP TS 23.434 [2].

[0013] A VAE client may interact with a SEAL client via the SEAL-C reference point specified for each SEAL service. A VAE server may interact with a SEAL server via the SEAL-S reference point specified for each SEAL service. Interactions between SEAL clients may be supported by the SEAL-PC5 reference point specified for each SEAL service. Interactions between SEAL clients and the corresponding SEAL server may be supported by the SEAL-UU reference point specified for each SEAL service. The SEAL-C, SEAL-S, SEAL-PC5, and SEAL-UU reference points for each SEAL service are specified in 3GPP TS 23.434 [2].

[0014] To support distributed VAE server deployment, a VAE server can interact with another VAE server via the VAE-E reference point. V2X UE1 can also act as a UE-to-network relay to enable a VAE client on V2X UE2 to access the VAE server via the V1-AE reference point; and to enable a V2X application-specific client on V2X UE2 to access the V2X application-specific server via the V1-Application reference point.

[0015] The V1-AE message can be sent via unicast, transparent multicast via xMB, or transparent multicast via MB2. Non-transparent multicast via xMB can be triggered by the V1-AE message. Both transparent and non-transparent multicast modes can support multicast distribution.

[0016] The VAE server can interact with the 3GPP network system through V2, MB2, xMB, Rx and T8 reference points. EPS and 5GS (referred to as reference [4] or [4]) can be regarded as 3GPP network systems. Summary of the Invention

[0017] In some embodiments, a method for operating a vehicle-to-everything (V2X) application enabler (VAE) server is provided. The method may include receiving a registration request message from a V2X application-specific server. The method may also include sending a registration response message to the V2X application-specific server in response to receiving the registration request message.

[0018] In some other embodiments, a method for operating a vehicle-to-everything (V2X) application-specific server is provided. The method may include sending a registration request message to a vehicle-to-everything (V2X) application enabler (VAE) server. The method may also include receiving a registration response message from the VAE server, wherein the registration response message is in response to the registration request message.

[0019] Various embodiments herein describe service APIs and / or processes for a V2X application hosted at a V2X service provider (e.g., an ITS Road Authority) that may be used to register with a VAE server for the purpose of sending and / or receiving V2X messages and / or network information / notifications. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of the inventive concept. In the drawings:

[0021] Figure 1 is a block diagram illustrating an example of a V2X application layer model according to some embodiments of the present inventive concept;

[0022] Figure 2 is a block diagram illustrating an example of an API between a V2X application-specific server at a V2X application server and a VAE server according to some embodiments of the present inventive concept;

[0023] Figure 3 is a block diagram illustrating an example of an API between a V2X application-specific client at a V2X UE and a VAE client according to some embodiments of the present inventive concept;

[0024] Figure 4 is a block diagram illustrating an example of an API between a V2X service provider and a PLMN according to some embodiments of the present inventive concept;

[0025] Figure 5 is a table illustrating an example of a V2X application specific server registration request according to some embodiments of the present inventive concept;

[0026] Figure 6 is a table illustrating an example of a V2X application specific server registration response according to some embodiments of the present inventive concept;

[0027] Figure 7 is a signal flow diagram illustrating an example of a process for a V2X application-specific server to register with a VAE server according to some embodiments of the present inventive concept;

[0028] Figure 8 is a signal flow diagram illustrating an example of a process for transmitting a message from a VAE server to a target geographic area according to some embodiments of the present inventive concept;

[0029] Figure 9 is a table illustrating examples of V2X group messages according to some embodiments of the present inventive concept;

[0030] Figure 10 is a signal flow diagram of a process for transmitting a V2X group message to a VAE client according to some embodiments of the present inventive concept;

[0031] Figure 11 is a signal flow diagram of a process for transmitting a message from a V2X UE to a V2X application server according to some embodiments of the present inventive concept;

[0032] Figure 12 is a table illustrating an example of a QoS sustainability analysis registration request according to some embodiments of the inventive concept;

[0033] Figure 13 is a table illustrating an example of a QoS sustainability analysis registration response according to some embodiments of the inventive concept;

[0034] Figure 14 is a signal flow diagram of a process for registering with a VAE server for QoS sustainability analysis according to some embodiments of the present inventive concept;

[0035] Figure 15 is a table illustrating an example of a QoS change registration request based on extended NG-RAN notification according to some embodiments of the present inventive concept;

[0036] Figure 16 is a table illustrating an example of a QoS change registration response based on extended NG-RAN notification according to some embodiments of the present inventive concept;

[0037] Figure 17 is a signal flow diagram illustrating an example of a procedure for extended NG-RAN notification based QoS change registration on a VAE server according to some embodiments of the present inventive concept;

[0038] Figure 18 is a block diagram illustrating a wireless device UE according to some embodiments of the inventive concept;

[0039] Figure 19 is a block diagram illustrating a vehicle-to-everything (V2X) application enabler (VAE) server according to some embodiments of the present inventive concept;

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

[0041] Figure 21-23 is a flowchart illustrating an example of the operation of a VAE server according to some embodiments of the present inventive concept;

[0042] Figures 24-26 is a flowchart illustrating an example of the operation of a V2X application-specific server according to some embodiments of the present inventive concept;

[0043] Figure 27 is a block diagram of a wireless network according to some embodiments;

[0044] Figure 28 is a block diagram of a user equipment according to some embodiments;

[0045] Figure 29 is a block diagram of a virtualization environment according to some embodiments;

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

[0047] Figure 31is 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;

[0048] Figure 32 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;

[0049] Figure 33 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;

[0050] 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; and

[0051] 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. DETAILED DESCRIPTION

[0052] The inventive concept will now be described more fully below with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in a variety of different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided to make this disclosure detailed and complete and to fully convey the scope of the inventive concept to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed to exist / be used in another embodiment.

[0053] The following description provides various embodiments of the disclosed subject matter. These embodiments are provided as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, specific details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter.

[0054] Figure 18 is a block diagram illustrating elements of a wireless device UE 1800 (also referred to as V2X UE, V2X UE device, mobile terminal, mobile communication terminal, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment UE, user equipment node / terminal / device, etc.) configured to provide wireless communication according to an embodiment of the present inventive concept. (For example, the wireless device 1800 may be provided, as described below for Figure 27 As shown in the figure, the wireless device UE may include an antenna 1807 (e.g., corresponding to Figure 27 antenna QQ111) and transceiver circuit 1801 (also referred to as a transceiver, for example corresponding to Figure 27The transceiver circuit 1801 includes a base station configured to provide communication with a radio access network (eg corresponding to Figure 27 The wireless device UE may further comprise a processing circuit 1803 (also referred to as a processor) coupled to the transceiver circuit, for example corresponding to a transmitter and receiver for uplink and downlink radio communications of a network node QQ160 (also referred to as a RAN node). Figure 27 Processing circuit QQ120) and memory circuit 1805 (also referred to as memory, for example corresponding to) coupled to the processing circuit Figure 27 The wireless device UE may further include an interface (e.g., a user interface) coupled to the processing circuit 1803, and / or the wireless device UE may be incorporated into a vehicle.

[0055] As discussed herein, operations of the wireless device UE may be performed by the processing circuitry 1803 and / or the transceiver circuitry 1801. For example, the processing circuitry 1803 may control the transceiver circuitry 1801 to transmit communications over a radio interface to a radio access network node (also referred to as a base station) via the transceiver circuitry 1801 and / or to receive communications over a radio interface from a RAN node via the transceiver circuitry 1801. Furthermore, modules may be stored in the memory circuitry 1805, and these modules may provide instructions such that, when the instructions of the modules are executed by the processing circuitry 1803, the processing circuitry 1803 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments involving wireless devices).

[0056] Figure 19 1 is a block diagram illustrating elements of a vehicle-to-everything (V2X) application enabler (VAE) server 1900. The VAE server 1900 may include a network interface circuit 1907 (also referred to as a network interface) configured to provide communication with other servers (e.g., other VAE servers or with V2X application-specific servers) and / or V2X UE devices (e.g., via a base station, also referred to as a radio access network node or RAN node). The VAE server may also include a processing circuit 1903 (also referred to as a processor, e.g., corresponding to the processing circuit QQ170) coupled to the transceiver circuit and a memory circuit 1905 (also referred to as a memory, e.g., corresponding to the memory) coupled to the processing circuit. Figure 27180). Memory circuit 1905 may include computer-readable program code that, when executed by processing circuit 1903, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 1903 may be defined to include memory, so that a separate memory circuit is not required.

[0057] As discussed herein, operations of the VAE server may be performed by processing circuitry 1903 and / or network interface circuitry 1907. For example, processing circuitry 1903 may control network interface 1907 to send communications to one or more other servers / nodes via network interface 1907 and / or to receive communications from one or more other servers / nodes via network interface 1907. Additionally, modules may be stored in memory 1905, and these modules may provide instructions such that, when the instructions of the modules are executed by processing circuitry 1903, processing circuitry 1903 performs corresponding operations (e.g., the operations discussed below with respect to embodiments involving the VAE server).

[0058] Figure 20 is a block diagram illustrating elements of a V2X application-specific server according to an embodiment of the present inventive concept. As shown, the V2X application-specific server may include a network interface circuit 2007 (also referred to as a network interface), which is configured to provide communication with other servers and / or V2X UE devices (e.g., via one or more VAE servers and / or RAN nodes). The V2X application-specific server may also include a processing circuit 2003 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 2005 (also referred to as a memory) coupled to the processing circuit. The memory circuit 2005 may include computer-readable program code that, when executed by the processing circuit 2003, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 2003 may be defined to include a memory so that a separate memory circuit is not required.

[0059] As discussed herein, operations of the V2X application-specific server may be performed by the processing circuitry 2003 and / or the network interface circuitry 2007. For example, the processing circuitry 2003 may control the network interface circuitry 2007 to send communications to one or more other servers via the network interface circuitry 2007 and / or to receive communications from one or more other servers via the network interface circuitry 2007. Furthermore, modules may be stored in the memory 2005, and these modules may provide instructions such that, when the instructions of the modules are executed by the processing circuitry 2003, the processing circuitry 2003 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments involving a V2X application-specific server).

[0060] Various embodiments described herein relate to V2X / ITS messaging over long-range cellular communications (Uu). In particular, some embodiments describe how a V2X application-specific server (which may be owned by a V2X service provider, such as a road authority or automotive OEM), using the V2X / ITS messaging service, can register with the network.

[0061] From the perspective of the 3GPP architecture, the VAE server can be regarded as an application function (AF) relative to other network functions of the 3GPP core network. In this case, the VAE server receives network information / notifications when the AF interacts with the core network functions, information / notifications, which are then used for the functions of the VAE server. In some examples, the process for notifying the V2X application server of potential QoS changes (TS23.287 clause 6.4.1) is based on the process for QoS sustainability analysis defined in TS23.288 clause 6.9. Users of QoS sustainability analysis can request NWDAF analysis information related to QoS change statistics for past observation periods in a specific area or the possibility of QoS changes for future observation periods in a specific area.

[0062] In an additional or alternative example, QoS changes based on extended NG-RAN notification to support alternative service requirements (TS 23.287 clause 5.4.5.3) are based on the extended notification control mechanism of NG-RAN defined in TS 23.501, TS 23.502 and TS 23.503.

[0063] In both examples above, the notifications generated by the NWDAF and NG-RAN are exposed (directly or via the NEF) to the AF (which may represent the VAE server).

[0064] There may be disagreements on how a V2X application specific server owned by a V2X service provider can register with a VAE server (e.g. hosted by a mobile network operator) to send and receive V2X / ITS messages and network notifications / information (such as QoS notifications). A V2X service provider may refer to a general provider that provides or has applications associated with V2X services, such as the OEM of a car, a road authority, providers such as map providers, VRU protection, lane merging, etc. The current procedures in references [1] and [3] have addressed the distribution of ITS / V2X messages from a VAE server. The VAE server discovers the V2X application server and therefore determines that the user of the message or notification is not defined.

[0065] The messaging API in [1] includes both UL and DL messaging. If UL messaging occurs before any DL messaging, it is unclear how the VAE server can discover V2X application capabilities. There is currently no defined mechanism for determining the specific server for a V2X application.

[0066] Various embodiments herein describe APIs and procedures for V2X applications (more specifically, V2X application-specific servers or clients) to register with a VAE server or VAE client, respectively. V2X service providers can use these APIs to interact with 3GPP network systems to send and receive V2X messages and network information / notifications. V2X application-specific servers or clients can use these APIs to interact with mobile networks.

[0067] In some embodiments, a standard mechanism is provided for a V2X service provider or V2X application specific server to interact with a VAE server (which may be hosted by a mobile network operator).

[0068] In some embodiments, a V2X service provider may be described as an entity that attempts to register with a VAE client / server. A V2X service provider may refer to a general provider that provides or has applications associated with V2X services. Examples of V2X service providers may include a car's OEM, OEM tier, ITS road authority, or a general provider of services (e.g., map provider, VRU protection, lane merging). A V2X application server may refer to the server side of a V2X service provider (e.g., a car's OEM, OEM tier, ITS road authority, or the backend of a general provider). A V2X UE may refer to the device side of a V2X service provider (e.g., a vehicle, road infrastructure).

[0069] In some embodiments, network information / notification refers to information disclosed by the mobile network or notifications generated by the mobile network that may be relevant to the V2X service under consideration. Examples of such information / notifications may be extended NG-RAN notifications (generated by the NG-RAN and disclosed by the core network to the AF to notify of non-implementation / re-implementation of QoS, and in the case of non-implementation, including information about alternative QoS profiles that may currently be implemented) or notifications regarding QoS sustainability analysis (generated by the NWDAF and disclosed to the AF to notify of predicted changes in QoS capabilities on a specific path).

[0070] The service API for V2X applications is discussed below.

[0071] In some embodiments, a service API can provide packages or services to users. For example, a V2X service provider may need to establish a relationship with a VAE to access services provided by the VAE, such as sending and receiving V2X messages or receiving network information / notifications associated with V2X services. In this context, a V2X application (more specifically, a V2X application-specific server or client) is a user of the services and related information provided by the VAE. Figure 2-3 The API interfaces at the V2X application server and V2X UE are described separately. Both downlink and uplink may require service APIs.

[0072] Figure 2 This is a block diagram illustrating an example of an API between a V2X application-specific server and a VAE server at a V2X application server. V2X messages generated by the V2X application-specific servers 210a-b can be provided to the VAE servers 220a-b using the service API. V2X messages received by the VAE servers 220a-b can be provided to the V2X application-specific servers 210a-b using the service API. Information / notifications generated from a 3GPP network system can be received by the VAE servers 220a-b, and the VAE servers 220a-b can provide the information / notifications to the V2X application-specific servers 210a-b using the service API.

[0073] Figure 3 The block diagram illustrates an example of an API between a V2X application-specific client and a VAE client at a V2X UE. A V2X message received at a VAE client 320a-b may be provided to the V2X application-specific client 310a-b using a service API. A V2X message generated at a V2X application-specific client 310a-b may be provided to the VAE client 320a-b using a service API. Information / notifications received at the VAE client 320a-b may be provided to the V2X application-specific client 310a-b using a service API.

[0074] The relationship between a V2X application-specific server and a VAE server can be a mobile network (MN). The V2X application-specific server can be owned by a V2X service provider. The VAE server can be owned by the V2X service provider or a mobile network operator. The V2X application-specific server can use one or more VAE servers to reach the V2X UE. The VAE server can process data associated with one or more V2X application-specific servers. A V2X application-specific server (e.g., a client) can register with multiple VAE servers (e.g., a client).

[0075] The described service API can be generalized for use with other VAL systems.

[0076] The V2X service provider can use the service API to establish a link to the mobile network operator (e.g., hosting the VAE server). In some examples, the mobile network operator may also want to establish a link to the V2X service provider and can use the same API.

[0077] The API can be provided as a deployment option, for example through network slicing.

[0078] The API and use cases are discussed below.

[0079] V2X service providers (e.g., automotive OEMs, road traffic authorities, and other third-party service providers) can be customers of V2X communication services provided by mobile networks. V2X applications can be implemented using both V2X application-specific servers and V2X application-specific clients. A VAE server can provide a standardized way to deliver such V2X communication services to customers.

[0080] The following APIs may be required for interaction between the application-specific server and the VAE server, and between the application-specific client and the VAE client: VAE_V2X_Message_Delivery_Server and VAE_V2X_Message_Delivery_Client. These interfaces may refer to Figure 1 Vs and Vc interfaces in the application layer functional model.

[0081] Users of VAE_V2X_Message_Delivery_Server may include V2X application-specific servers. Operations of VAE_V2X_Message_Delivery_Server may include: V2X_Application_Specific_Server_Registration (request / response); V2X_Downlink_Message_Delivery_TX (request / response); V2X_Uplink_Message_Delivery_RX (subscription / notification); and V2X_Network_Information_QoS_Notification (subscription / notification).

[0082] V2X_Application_Specific_Server_Registration (request / response) may be used in some embodiments (eg, V2X_MessageDelivery_Register) for application specific server registration for uplink / downlink messaging and QoS notification.

[0083] V2X_Downlink_Message_Delivery_TX (request / response) may be defined as V2X_Message_Delivery[1] in 3GPP TS 23.286[1] clause 10.2.2.2 and may be used in some embodiments to provide message delivery status reports of both downlink messages and group messages to the V2X application specific server.

[0084] V2X_Uplink_Message_Delivery_RX (Subscribe / Notify) may be defined as V2X_Uplink_Message_Delivery[1] in 3GPP TS 23.286[1] clause 10.2.2.3 and may be used in some embodiments to provide uplink reception reporting of uplink messages from a V2X application specific server.

[0085] Users of VAE_V2X_Message_Delivery_Client may include V2X application-specific clients. Operations of VAE_V2X_Message_Delivery_Client may include: V2X_Application_Specific_Client_Registration (request / response); V2X_Uplink_Message_Delivery_TX (request / response); V2X_Downlink_Message_Delivery_RX (subscription / notification); and V2X_Network_Information_QoS_Notification (subscription / notification).

[0086] The standardized APIs of the VAE for both the V2X application-specific server and the V2X application-specific client can allow the deployment of V2X services on cellular networks in an interoperable manner (e.g., across MNOs and across V2X service providers). When implemented in a distributed manner in the PLMN domain, the relationship between the V2X application-specific server (owned by the V2X service provider) and the VAE server can be many-to-many (see 3GPP TS 23.286 [1] clause 7.2). The relationship between the V2X application-specific client (also owned by the V2X service provider) and the VAE client can be many-to-one.

[0087] Figure 4 is a block diagram illustrating an example of an API between a V2X service provider and a PLMN.

[0088] In addition to registration and (uplink / downlink) messaging, special features that may be required for V2X services (such as QoS and pre-QoS notifications) can be taken into account in the API.

[0089] The following will discuss V2X application-specific server registration, which includes a process for a V2X application-specific server to register with a VAE server to send and receive messages.

[0090] Figure 5 is a table showing an example of information flow (V2X application specific server registration request) from a V2X application specific server to a VAE server.

[0091] Figure 6 is a table showing an example of information flow from a VAE server to a V2X application specific server: V2X application specific server registration response.

[0092] Figure 7 7 is a signal flow diagram illustrating an example process for a V2X application-specific server to register with a VAE server. The V2X application-specific server may belong to a V2X service provider that has a business relationship with the VAE. The V2X application-specific server may know the address of the VAE server and be authorized to communicate with the VAE server. In operation 710, the V2X application-specific server sends a registration request to the VAE server to register for receiving uplink messages. The V2X application-specific server may subscribe to receive specific V2X messages based on the V2X service ID and GEO ID of the specific V2X message. In operation 720, the VAE server sends a registration response to the V2X application-specific server indicating success or failure.

[0093] Figure 8 is a signal flow diagram illustrating an example of a process for transmitting a message from a VAE server to a target geographic area. The VAE client may have registered with the VAE server, as described in subclause 9.2.3 of 3GPP TS 23.286 [1]. One or more VAE clients may have subscribed to a geographic area GEO ID. The VAE server may have created a mapping between geographic area information and client identification, as described in subclause 9.3.3 of 3GPP TS 23.286 [1]. The V2X application specific server may have registered with the VAE server, as described in subclause 9.3.3 of the present disclosure. Figure 7 As stated.

[0094] In operation 810, the application-specific server sends a V2X message for the service, which has a V2X service ID (e.g., ETSI ITSDENM, ETSI ITS CAM) containing the target geographic area GEO ID. In operation 820, for the V2X message targeting the geographic area GEO ID, the VAE server obtains a list of registered and subscribed clients and determines the client's V2X UE ID. In operation 830, the VAE server sends a message to each VAE client using the client ID. In operation 840, the VAE client provides the V2X message to the application-specific client. In operation 850, if indicated in the V2X message, the VAE client provides a V2X message reception report to the VAE server. In operation 860, the VAE server may provide the V2X message reception report to the V2X application-specific server.

[0095] V2X group messaging will be discussed below.

[0096] Figure 9 is a table showing an example of information flow for a VAE server to transmit V2X messages to a group of VAE clients.

[0097] Figure 10 is a signal flow diagram illustrating an example of a process for transmitting a V2X group message to a VAE client. The VAE client may have registered to receive V2X group messages as described in subclause 10.3.8 of 3GPP TS 23.434 [2]. The V2X application specific server may have registered with the VAE server as described in subclause 10.3.8 of 3GPP TS 23.434 [2]. Figure 7 As stated.

[0098] In operation 1010, the V2X application-specific server provides a V2X message for distribution to a V2X group with a V2X group ID. In operation 1020, the VAE server transmits the V2X message to all registered VAE clients with the V2X group ID. In operation 1030, the VAE client provides the V2X message to the V2X application-specific client. In operation 1040, the VAE client may provide a V2X message reception report to the VAE server. In operation 1050, the VAE server may provide a V2X message reception report to the V2X application-specific server.

[0099] Figure 11is a signal flow diagram illustrating an example of a process for transmitting a message from a V2X UE to a V2X application server. The VAE client may have discovered the VAE server, as described in subclause 9.1.2 of 3GPP TS 23.286 [1]. The VAE client may have registered with a V2X service identified by a V2X service ID, as described in subclause 9.2 of 3GPP TS 23.286 [1]. The V2X application specific server may have registered with the VAE server, as described in subclause 9.2 of 3GPP TS 23.286 [1]. Figure 7 As stated.

[0100] In operation 1110, the V2X application-specific client sends a V2X uplink message to the VAE client. In operation 1120, the VAE client determines a VAE server for receiving the V2X uplink message with the V2X service ID. In operation 1130, the VAE client sends the V2X uplink message to the VAE server. In operation 1140, the VAE server provides the V2X uplink message to the application-specific server. In operation 1150, if indicated in the V2X uplink message, the V2X application-specific server may provide a V2X uplink message reception report to the VAE server. In operation 1160, if indicated in the V2X uplink message, the VAE server may provide a V2X uplink message reception report to the VAE client.

[0101] In some embodiments, the API enables a V2X application-specific server to register with and communicate with a VAE server to send and receive V2X messages to and from V2X UEs (including V2X groups).

[0102] The V2X_MessageDelivery_Register operation is described below.

[0103] API operation name: V2X_MessageDelivery_Register

[0104] Description: Registers to the VAE server for sending and receiving V2X messages.

[0105] Known users: V2X application-specific servers.

[0106] Input: See the disclosure of Figure 5 .

[0107] Output: Success or failure.

[0108] See the disclosure of Figure 7 To learn more about the usage of this API operation.

[0109] The following describes a process for a V2X application-specific server to register with a VAE server to receive notifications about QoS sustainability analysis. The notifications provide information about QoS change statistics for past observation periods in a specific area or the likelihood of QoS changes in future observation periods in the specific area.

[0110] Figure 12 is a table showing an example of the information flow of a QoS sustainability analysis registration request from a V2X application specific server to a VAE server.

[0111] Figure 13 is a table showing an example of the information flow of a QoS sustainability analysis registration response from a VAE server to a V2X application specific server.

[0112] Figure 14 This is a signal flow diagram illustrating an example process for registering a VAE server for QoS sustainability analysis. The V2X application-specific server may belong to a V2X service provider that has a business relationship with the VAE. The V2X application-specific server may know the address of the VAE server and be authorized to communicate with the VAE server.

[0113] In operation 1410, the V2X application-specific server sends a registration request to the VAE server to register for receiving QoS sustainability analysis notifications. The V2X application-specific server may subscribe to receive specific QoS sustainability analysis notifications based on the analysis filter information included in the request. In operation 1420, the VAE server sends a registration response to the V2X application-specific server indicating success or failure.

[0114] The following describes a procedure for a V2X application-specific server to register with a VAE server to receive notifications regarding QoS changes based on extended NG-RAN notifications. This notification provides information regarding the NG-RAN's ability to implement (or re-implement) a specific QoS flow, as well as information regarding which of the alternative service requirements associated with the QoS flow are currently expected to be met by the NG-RAN.

[0115] Figure 15 is a table showing an example of the information flow of a QoS change registration request based on extended NG-RAN notification from a V2X application specific server to a VAE server.

[0116] Figure 16 is a table showing an example of the information flow of a QoS change registration response based on extended NG-RAN notification from a VAE server to a V2X application specific server.

[0117] Figure 1717 is a signal flow diagram illustrating an example of a process for registering QoS changes based on extended NG-RAN notifications with a VAE server. The V2X application-specific server may belong to a V2X service provider that has a business relationship with the VAE. The V2X application-specific server may know the address of the VAE server and be authorized to communicate with the VAE server. In operation 1710, the V2X application-specific server sends a registration request to the VAE server to register for receiving QoS changes based on extended NG-RAN notifications. The V2X application-specific server may subscribe to receive specific QoS changes based on extended NG-RAN notifications based on the GEO ID and alternative service requirements included in the request. In operation 1720, the VAE server sends a registration response to the V2X application-specific server indicating success or failure.

[0118] Service APIs and procedures for V2X applications hosted at a V2X service provider (e.g., an ITS Road Authority) to register with the VAE server for the purpose of sending and receiving V2X messages and network information / notifications.

[0119] Reference will now be made to some embodiments according to the present inventive concept. Figure 21-23 The flowchart of VAE server 1900 (using Figure 19 For example, a module can be stored in Figure 19 1905, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding VAE server processing circuit 1903, the processing circuit 1903 performs the corresponding operations of the flowchart.

[0120] At block 2110, the processing circuit 1903 receives a registration request message from the V2X application specific server via the network interface 1907, for example, as described above for Figure 7 Message / action 710 discussed above.

[0121] At block 2120, the processing circuit 1903 sends a registration response message to the V2X application specific server via the network interface 1907, for example, as described above for Figure 7 The registration response message may include an indication of the result of the registration in response to the registration request message. The indication of the result may indicate one of the success or failure of the registration in response to the registration request message, for example, as described above with respect to Figure 6 discussed.

[0122] In some embodiments, a service application programming interface (API) is used to receive a registration request message, and a service API is used to send a registration response message.

[0123] In additional or alternative embodiments, the registration request message may be a V2X application specific server registration request message (see, for example, Figure 7 The registration response message may be a V2X application specific server registration response message (e.g., see Figure 7 Operation / message 720). In some examples (e.g., Figure 5 In an embodiment, the V2X application-specific server registration request message may include at least one of the following: an identifier of the V2X application-specific server for transmitting uplink messages, a V2X service identifier to which the V2X application-specific server is registered, an identifier of the geographical area to which the V2X application-specific server is registered, and / or information of the V2X application-specific server for receiving notifications. In an additional or alternative example, the V2X application-specific server registration request message includes at least one of the following: the V2X service identifier to which the V2X application-specific server is registered and / or an identifier of the geographical area to which the V2X application-specific server is registered. The V2X application-specific server registration request message may include a request to register to receive uplink messages from the VAE server at the V2X application-specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

[0124] exist Figure 22 In block 2210, the processing circuit 1903 receives a V2X downlink message from the V2X application specific server via the network interface 1907 (e.g., after sending the V2X application specific server registration response message in block 2120), e.g., as described above for Figure 8 The operation / message 810 is discussed.

[0125] At block 2220, the processing circuit 1903 sends a V2X downlink message to the V2X UE device via the network interface 1907 (in response to receiving the V2X downlink message at block 2210), for example as described above for Figure 8 The V2X downlink message may be sent to the V2X UE via a radio access network (RAN) node (also referred to as a base station). The V2X UE device may also be referred to as a V2X UE and / or a VAE client.

[0126] At block 2230, the processing circuit 1903 receives a V2X message reception report from the V2X UE via the network interface 1907 (after sending the V2X downlink message), e.g., as described above for Figure 8 The V2X message reception report of block 2230 may correspond to a V2X downlink message.

[0127] At block 2240, processing circuitry 1903 sends, via network interface 1907, an uplink message (e.g., a V2X message reception report) from the VAE server to the V2X application specific server, e.g., as discussed above with respect to message / operation 860 of FIG. 8. Figure 8

[0128] In some embodiments, the V2X downlink message is associated with at least one of a V2X service identifier and / or an identifier of a geographic area. Sending the V2X downlink message can include sending the V2X downlink message to the V2X UE device based on the at least one of the V2X service identifier and / or the identifier of the geographic area associated with the V2X downlink message. The V2X message reception report can be sent to the V2X application specific server based on the at least one of the V2X service identifier and / or the identifier of the geographic area associated with the V2X downlink message.

[0129] In additional or alternative embodiments, the V2X downlink message can include a downlink V2X group message that is to be distributed to a plurality of V2X UE devices based on a V2X group identifier included in the downlink V2X group message. Sending the downlink V2X group message can include sending the downlink V2X group message to the plurality of V2X UE devices.

[0130] In Figure 23 , at block 2310, processing circuitry 1903 receives, via network interface 1907, a V2X uplink message from a V2X UE device (also referred to as a V2X UE or a VAE client), e.g., as discussed above with respect to message / operation 1130 of FIG. 10. Figure 11

[0131] At block 2320, processing circuitry 1903 sends, via network interface 1907, the V2X uplink message from the VAE server to the V2X application specific server based on at least one of a V2X service identifier and / or an identifier of a geographic area in response to receiving the V2X uplink message from the V2X UE device, e.g., as discussed above with respect to message / operation 1140 of FIG. 11. Figure 11

[0132] At block 2330, processing circuitry 1903 receives, via network interface 1907, a V2X uplink message reception report from the V2X application specific server, e.g., as discussed above with respect to operation / message 1150 of FIG. 12. The V2X uplink message reception report can be associated with the V2X uplink message. Figure 11

[0133] ​​​​At block 2340, the processing circuit 1903 sends a V2X uplink message transmission report to the V2X UE device via the network interface 1907 based on at least one of the V2X service identifier and / or the identifier of the geographic area, for example as described above for Figure 11 Operation 1160 is discussed above.

[0134] In some embodiments, the registration request message includes a Quality of Service (QoS) registration request message, and the registration response message includes a QoS registration response message. In additional or alternative embodiments, the QoS registration request message includes a QoS sustainability analysis registration request message, and the QoS registration response message includes a QoS sustainability analysis registration response message. In additional or alternative embodiments (e.g., Figure 12 As shown), the QoS sustainability analysis registration request message includes at least one of the following: an identifier of the V2X application-specific server, an indication of whether a QoS sustainability analysis notification should be provided to the VAE client device, a V2X service identifier to which the V2X application-specific server is registered, an identifier of a geographical area to which the V2X application-specific server is registered, information of the V2X application-specific server for receiving the QoS sustainability analysis notification, and / or analysis filter information.

[0135] In additional or alternative embodiments, the processing circuit 1903 transmits QoS sustainability analysis information between the VAE server and the V2X application specific server via the network interface 1907 based on information from the QoS registration request message.

[0136] In an additional or alternative embodiment, the QoS registration request message includes a QoS change registration request message based on an extended next generation radio access network NG-RAN notification, and the QoS registration response message includes a QoS change registration response message based on an extended NG-RAN notification. Figure 15 As shown in FIG, the QoS change registration request message based on the extended NG-RAN notification may include at least one of the following: an identifier of the V2X application specific server, an indication of whether the QoS change based on the extended NG-RAN notification should be provided to the VAE client device, a V2X service identifier to which the V2X application specific server is registered, an identifier of the geographical area to which the V2X application specific server is registered, information of the V2X application specific server for receiving the QoS change based on the extended NG-RAN notification, and / or an alternative service requirement.

[0137] In additional or alternative embodiments, the processing circuit 1903 communicates the QoS change based on the extended NG-RAN notification between the VAE server and the V2X application specific server via the network interface 1907 based on information from the QoS registration request message.

[0138] In additional or alternative embodiments, the processing circuit 1903 transmits QoS communications between the VAE server and the V2X application specific server via the network interface 1907 based on information from the QoS registration request message.

[0139] Some embodiments of VAE servers and related methods, from Figure 21-23 Various operations of the flowchart may be optional. For example, Figure 21 method (described below), Figure 22 Blocks 2210, 2220, 2230, and 2240 and Figure 23 The operations of blocks 2310, 2320, 2330, and 2340 may be optional.

[0140] Reference will now be made to some embodiments according to the present inventive concept. Figures 24-26 The flowchart of the V2X application specific server 2000 (using Figure 20 For example, a module can be stored in Figure 20 The modules are stored in the memory 2005, and these modules can provide instructions so that when the instructions of the modules are executed by the corresponding V2X application specific server processing circuit 2003, the processing circuit 2003 performs the corresponding operations of the flowchart.

[0141] At block 2410, the processing circuit 2003 sends a registration request message to the V2X application enabler VAE server via the network interface 2007, for example, as described above for Figure 7 The operation / message 710 is discussed.

[0142] At block 2420, the processing circuit 2003 receives a registration response message from the VAE server via the network interface 2007, wherein the registration response message is in response to the registration request message, for example, as described above for Figure 7 The registration response message may include an indication of the result of the registration in response to the registration request message. The indication of the result may indicate one of a success or failure of the registration in response to the registration request message. In some embodiments, a service application programming interface (API) is used to send the registration request message and a service API is used to receive the registration response message. In additional or alternative embodiments, the registration request message may be a V2X application specific server registration request message (e.g., see Figure 7 The registration response message may be a V2X application specific server registration response message (e.g., see Figure 7 Operation / message 720). In some examples (e.g., Figure 5As shown), the V2X application specific server registration request message may include at least one of the following: an identifier of the V2X application specific server used to transmit the uplink message, a V2X service identifier to which the V2X application specific server is registered, an identifier of the geographical area to which the V2X application specific server is registered, and / or information of the V2X application specific server used to receive notifications.

[0143] In an additional or alternative embodiment, the V2X application specific server registration request message includes at least one of: a V2X service identifier to which the V2X application specific server is registered and / or an identifier of a geographical area to which the V2X application specific server is registered. The V2X application specific server registration request message may include a request to register to receive uplink messages from the VAE server at the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

[0144] exist Figure 25 In block 2510, the processing circuit 2003 sends a V2X downlink message from the V2X application specific server via the network interface 2007 (e.g., after receiving the V2X application specific server registration response message), such as described above for Figure 8 The operation / message 810 is discussed.

[0145] At block 2520, the processing circuit 2003 receives an uplink message from the VAE server via the network interface 2007 based on at least one of the V2X service identifier and / or the identifier of the geographic area, for example as described above for Figure 8 As discussed above with respect to operations / messages 860 of FIG. In some embodiments, the V2X message reception report corresponds to a V2X downlink message. The V2X downlink message may be associated with at least one of a V2X service identifier and / or an identifier of a geographic area, and the V2X message reception report may be received from the VAE server based on at least one of the V2X service identifier and / or the identifier of the geographic area associated with the V2X downlink message. In additional or alternative embodiments, the V2X downlink message includes a downlink V2X group message to be distributed to a plurality of V2X UE devices based on a V2X group identifier included in the downlink V2X group message.

[0146] exist Figure 26 In block 2610, the processing circuit 2003 receives a V2X uplink message from the VAE server via the network interface 2007 based on at least one of the V2X service identifier and / or the identifier of the geographic area, for example as described above for Figure 11 Message / action 1140 discussed above.

[0147] At block 2620, the processing circuit 2003 sends a V2X uplink message reception report (in response to receiving the V2X uplink message) to the VAE server via the network interface 2007, e.g., as described above for Figure 11 The operation / message 1150 is discussed.

[0148] In some embodiments, the registration request message includes a Quality of Service (QoS) registration request message, and the registration response message includes a QoS registration response message. The QoS registration request message may include a QoS sustainability analysis registration request message, and the QoS registration response message may include a QoS sustainability analysis registration response message. In some examples (e.g., Figure 12 As shown), the QoS sustainability analysis registration request message includes at least one of the following: an identifier of the V2X application-specific server, an indication of whether a QoS sustainability analysis notification should be provided to the VAE client device, a V2X service identifier to which the V2X application-specific server is registered, an identifier of a geographical area to which the V2X application-specific server is registered, information of the V2X application-specific server for receiving the QoS sustainability analysis notification, and / or analysis filter information.

[0149] In additional or alternative embodiments, the processing circuit 2003 transmits QoS sustainability analysis information between the VAE server and the V2X application specific server via the network interface 2007 based on information from the QoS registration request message.

[0150] In additional or alternative embodiments, the QoS registration request message includes a QoS change registration request message based on an extended next generation radio access network NG-RAN notification, and the QoS registration response message includes a QoS change registration response message based on an extended NG-RAN notification. Figure 15 As shown in FIG, the QoS change registration request message based on the extended NG-RAN notification may include at least one of the following: an identifier of the V2X application specific server, an indication of whether the QoS change based on the extended NG-RAN notification should be provided to the VAE client device, a V2X service identifier to which the V2X application specific server is registered, an identifier of the geographical area to which the V2X application specific server is registered, information of the V2X application specific server for receiving the QoS change based on the extended NG-RAN notification, and / or an alternative service requirement.

[0151] In an additional or alternative embodiment, the processing circuit 2003 communicates the QoS change based on the extended NG-RAN notification between the VAE server and the V2X application specific server via the network interface 2007 based on information from the QoS registration request message.

[0152] In additional or alternative embodiments, the processing circuit 2003 transmits QoS communications between the VAE server and the V2X application specific server via the network interface 2007 based on information from the QoS registration request message.

[0153] Some embodiments of V2X application-specific servers and related methods, from Figures 24-26 Various operations of the flowchart may be optional. For example, Figure 24 method, Figure 25 Blocks 2510 and 2520 and Figure 26 The operations of blocks 2610 and 2620 may be optional.

[0154] Provided below are descriptions of various abbreviations / acronyms used in this disclosure.

[0155] Abbreviation

[0156] V2X AS V2X application server

[0157] VAE V2X Application Enabler

[0158] V2X UE User Equipment

[0159] ITS Intelligent Transportation System

[0160] ITS-S ITS Station

[0161] V2X Vehicle to Everything

[0162] VAL Vertical Application Layer

[0163] References are identified below.

[0164] References [1] 3GPP TS 23.286, Application layer support for V2X services; Functional architecture and information flows, V16.1.0, September 2019.

[0165] References [2] 3GPP TS 23.434, Service Enabler Architecture Layer for Verticals; Functional architecture and information flows, V16.1.0, September 2019.

[0166] References [3] 3GPP TR 23.795, Study on application layer support for V2X services, V16.1.0, December 2018.

[0167] References [4] 3GPP TR 23.764, Study on enhancements to application layer support for V2X services, V0.2.0, September 2019.

[0168] In view of the above, embodiments provided by the present disclosure include:

[0169] Embodiment 1. A method for operating a vehicle-to-everything (V2X) application enabler (VAE) server, the method comprising:

[0170] receiving (2110) a registration request message from the V2X application specific server; and

[0171] In response to receiving the registration request message, a registration response message is sent (2120) to the V2X application specific server.

[0172] Embodiment 2. The method according to embodiment 1, wherein a service application programming interface (API) is used to receive a registration request message, and wherein a service API is used to send a registration response message.

[0173] Embodiment 3. The method according to any one of embodiments 1-2, wherein the registration request message includes a V2X application-specific server registration request message, and wherein the registration response message includes a V2X application-specific server registration response message.

[0174] Embodiment 4. The method according to embodiment 3, wherein the V2X application-specific server registration request message includes at least one of the following: an identifier of the V2X application-specific server used to transmit uplink messages, a V2X service identifier to which the V2X application-specific server is registered, an identifier of the geographical area to which the V2X application-specific server is registered, and / or information of the V2X application-specific server used to receive notifications.

[0175] Embodiment 5. The method according to embodiment 3, wherein the V2X application-specific server registration request message includes at least one of the following: a V2X service identifier to which the V2X application-specific server is registered, and / or an identifier of a geographical area to which the V2X application-specific server is registered.

[0176] Embodiment 6. The method of embodiment 5, wherein the V2X application specific server registration request message includes a request to register to receive uplink messages from the VAE server at the V2X application specific server based on at least one of a V2X service identifier and / or an identifier of a geographic area.

[0177] Example 7. The method according to Example 6, further comprising:

[0178] An uplink message is sent (2240) from the VAE server to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

[0179] Example 8. The method according to Example 7, further comprising:

[0180] After sending the V2X application specific server registration response message, receiving (2210) a V2X downlink message from the V2X application specific server;

[0181] In response to receiving the V2X downlink message, sending (2220) a V2X downlink message to a V2X user equipment (UE) device; and

[0182] After sending the V2X downlink message, receiving (2230) a V2X message reception report from the V2X UE device, wherein the V2X message reception report corresponds to the V2X downlink message;

[0183] The sending of the uplink message includes sending a V2X message reception report from the VAE server to the V2X application specific server.

[0184] Embodiment 9. The method according to embodiment 8, wherein the V2X downlink message is associated with at least one of a V2X service identifier and / or an identifier of a geographical area, wherein sending the V2X downlink message comprises: sending the V2X downlink message to the V2X UE device based on at least one of the V2X service identifier and / or the identifier of the geographical area associated with the V2X downlink message, and wherein sending a V2X message reception report to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area associated with the V2X downlink message.

[0185] Embodiment 10. The method of any one of embodiments 8-9, wherein the V2X downlink message includes a downlink V2X group message, the downlink V2X group message being distributed to a plurality of V2X UE devices based on a V2X group identifier included in the downlink V2X group message, and wherein sending the downlink V2X group message includes sending the downlink V2X group message to the plurality of V2X UE devices.

[0186] Example 11. The method according to Example 6, further comprising:

[0187] receiving (2310) a V2X uplink message from a V2X user equipment (UE) device; and

[0188] In response to receiving the V2X uplink message from the V2X UE device, the V2X uplink message is sent (2320) from the VAE server to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

[0189] Example 12. The method according to Example 11, further comprising:

[0190] After sending the uplink message, receiving (2330) a V2X uplink message reception report from the V2X application specific server, wherein the V2X uplink message reception report is associated with the V2X uplink message; and

[0191] In response to receiving the V2X uplink message reception report, a V2X uplink message transmission report is sent (2340) to the V2X UE device based on at least one of the V2X service identifier and / or the identifier of the geographic area.

[0192] Embodiment 13. The method according to any one of embodiments 1-2, wherein the registration request message includes a Quality of Service (QoS) registration request message, and wherein the registration response message includes a QoS registration response message.

[0193] Embodiment 14. The method according to embodiment 13, wherein the QoS registration request message includes a QoS sustainability analysis registration request message, and wherein the QoS registration response message includes a QoS sustainability analysis registration response message.

[0194] Embodiment 15. The method of embodiment 14, wherein the QoS sustainability analysis registration request message includes at least one of the following: an identifier of the V2X application-specific server, an indication of whether a QoS sustainability analysis notification should be provided to the VAE client device, a V2X service identifier to which the V2X application-specific server is registered, an identifier of a geographic area to which the V2X application-specific server is registered, information of the V2X application-specific server for receiving the QoS sustainability analysis notification, and / or analysis filter information.

[0195] Example 16. The method according to any one of Examples 14-15, further comprising:

[0196] Based on the information from the QoS registration request message, QoS sustainability analysis information is transmitted between the VAE server and the V2X application specific server.

[0197] Embodiment 17. The method according to embodiment 13, wherein the QoS registration request message includes a QoS change registration request message based on an extended next generation radio access network NG-RAN notification, and wherein the QoS registration response message includes a QoS change registration response message based on an extended NG-RAN notification.

[0198] Embodiment 18. The method of embodiment 17, wherein the QoS change based on extended NG-RAN notification registration request message includes at least one of the following: an identifier of a V2X application-specific server, an indication of whether a QoS change based on extended NG-RAN notification should be provided to a VAE client device, a V2X service identifier to which the V2X application-specific server is registered, an identifier of a geographical area to which the V2X application-specific server is registered, information of a V2X application-specific server for receiving QoS changes based on extended NG-RAN notification, and / or an alternative service requirement.

[0199] Embodiment 19. The method according to any one of embodiments 17-18, further comprising:

[0200] Based on the information from the QoS Registration Request message, QoS changes based on the Extended NG-RAN Notification are communicated between the VAE server and the V2X application specific server.

[0201] Example 20. The method according to Example 13, further comprising:

[0202] Based on the information from the QoS Registration Request message, QoS communications are transmitted between the VAE server and the V2X application specific server.

[0203] Embodiment 21. The method of any one of embodiments 1-20, wherein the registration response message includes an indication of a result of the registration in response to the registration request message.

[0204] Embodiment 22. The method of embodiment 21, wherein the indication of the result indicates one of a success or a failure of the registration in response to the registration request message.

[0205] Embodiment 23. A method for operating a vehicle-to-everything V2X application-specific server, the method comprising:

[0206] Sending (2410) a registration request message to a vehicle-to-everything (V2X) application enabler (VAE) server; and

[0207] A registration response message is received (2420) from the VAE server, wherein the registration response message is in response to the registration request message.

[0208] Embodiment 24. The method according to embodiment 23, wherein a service application programming interface (API) is used to send a registration request message, and wherein a service API is used to receive a registration response message.

[0209] Embodiment 25. The method according to any one of embodiments 23-24, wherein the registration request message includes a V2X application-specific server registration request message, and wherein the registration response message includes a V2X application-specific server registration response message.

[0210] Embodiment 26. The method according to embodiment 25, wherein the V2X application-specific server registration request message includes at least one of the following: an identifier of the V2X application-specific server used to transmit uplink messages, a V2X service identifier to which the V2X application-specific server is registered, an identifier of the geographical area to which the V2X application-specific server is registered, and / or information of the V2X application-specific server used to receive notifications.

[0211] Embodiment 27. The method according to embodiment 25, wherein the V2X application-specific server registration request message includes at least one of the following: a V2X service identifier to which the V2X application-specific server is registered, and / or an identifier of a geographical area to which the V2X application-specific server is registered.

[0212] Embodiment 28. The method of embodiment 27, wherein the V2X application specific server registration request message includes a request to register to receive uplink messages from the VAE server at the V2X application specific server based on at least one of a V2X service identifier and / or an identifier of a geographic area.

[0213] Example 29. The method according to Example 28, further comprising:

[0214] An uplink message is received (2520) from the VAE server based on at least one of the V2X service identifier and / or the identifier of the geographic area.

[0215] Embodiment 30. The method according to embodiment 29, further comprising:

[0216] After receiving the V2X application specific server registration response message, sending (2510) a V2X downlink message from the V2X application specific server;

[0217] Receiving the uplink message includes: receiving a V2X message reception report from the VAE server, wherein the V2X message reception report corresponds to the V2X downlink message.

[0218] Embodiment 31. The method of embodiment 30, wherein the V2X downlink message is associated with at least one of a V2X service identifier and / or an identifier of a geographic area, and wherein the V2X message reception report is received from the VAE server based on at least one of the V2X service identifier and / or the identifier of the geographic area associated with the V2X downlink message.

[0219] Embodiment 32. The method of any one of embodiments 30-31, wherein the V2X downlink message comprises a downlink V2X group message to be distributed to a plurality of V2X UE devices based on a V2X group identifier included in the downlink V2X group message.

[0220] Embodiment 33. The method according to embodiment 28, further comprising:

[0221] A V2X uplink message is received (2610) from the VAE server based on at least one of the V2X service identifier and / or the identifier of the geographic area.

[0222] Embodiment 34. The method according to embodiment 33, further comprising:

[0223] In response to receiving the V2X uplink message, a V2X uplink message reception report is sent (2620) to the VAE server.

[0224] Embodiment 35. The method according to any one of embodiments 23-24, wherein the registration request message includes a Quality of Service (QoS) registration request message, and wherein the registration response message includes a QoS registration response message.

[0225] Embodiment 36. The method according to embodiment 35, wherein the QoS registration request message includes a QoS sustainability analysis registration request message, and wherein the QoS registration response message includes a QoS sustainability analysis registration response message.

[0226] Embodiment 37. A method according to embodiment 36, wherein the QoS sustainability analysis registration request message includes at least one of the following: an identifier of the V2X application-specific server, an indication of whether the QoS sustainability analysis notification should be provided to the VAE client device, a V2X service identifier to which the V2X application-specific server is registered, an identifier of the geographic area to which the V2X application-specific server is registered, information of the V2X application-specific server for receiving the QoS sustainability analysis notification, and / or analysis filter information.

[0227] Embodiment 38. The method according to any one of embodiments 36-37, further comprising:

[0228] Based on the information from the QoS registration request message, QoS sustainability analysis information is transmitted between the VAE server and the V2X application specific server.

[0229] Embodiment 39. A method according to embodiment 35, wherein the QoS registration request message includes a QoS change registration request message based on an extended next generation radio access network NG-RAN notification, and wherein the QoS registration response message includes a QoS change registration response message based on an extended NG-RAN notification.

[0230] Embodiment 40. The method of embodiment 39, wherein the QoS change based on extended NG-RAN notification registration request message includes at least one of the following: an identifier of a V2X application-specific server, an indication of whether a QoS change based on extended NG-RAN notification should be provided to a VAE client device, a V2X service identifier to which the V2X application-specific server is registered, an identifier of a geographical area to which the V2X application-specific server is registered, information of a V2X application-specific server for receiving QoS changes based on extended NG-RAN notification, and / or an alternative service requirement.

[0231] Embodiment 41. The method according to any one of embodiments 39-40, further comprising:

[0232] Based on the information from the QoS Registration Request message, QoS changes based on the Extended NG-RAN Notification are communicated between the VAE server and the V2X application specific server.

[0233] Example 42. The method of Example 35, further comprising:

[0234] Based on the information from the QoS Registration Request message, QoS communications are transmitted between the VAE server and the V2X application specific server.

[0235] Embodiment 43. The method of any one of Embodiments 23-42, wherein the registration response message includes an indication of a result of the registration in response to the registration request message.

[0236] Embodiment 44. The method of embodiment 43, wherein the indication of the result indicates one of a success or a failure of the registration in response to the registration request message.

[0237] Embodiment 45. A vehicle-to-everything (V2X) application enabler (VAE) server (1900), comprising:

[0238] processing circuit (1903); and

[0239] A memory (1905) coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the VAE server to perform operations according to any one of embodiments 1-22.

[0240] Embodiment 46. A vehicle-to-everything V2X application enabler VAE server (1900), adapted to be executed according to any one of embodiments 1-22.

[0241] Embodiment 47. A computer program comprising program code to be executed by a processing circuit (1903) of a vehicle-to-everything (V2X) application enabler (VAE) server (1900), whereby execution of the program code causes the VAE server (1900) to perform operations according to any one of embodiments 1-22.

[0242] Embodiment 48. A computer program product comprising a non-transitory storage medium comprising program code to be executed by a processing circuit (1903) of a vehicle-to-everything (V2X) application enabler (VAE) server (1900), whereby execution of the program code causes the VAE server (1900) to perform operations according to any one of embodiments 1-22.

[0243] Embodiment 49. A vehicle-to-everything (V2X) application-specific server (2000), comprising:

[0244] Processing Circuit (2003); and

[0245] A memory (2005) coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the V2X application specific server (2000) to perform operations according to any one of embodiments 23-44.

[0246] Embodiment 50. A vehicle-to-everything V2X application-specific server (2000), adapted to be executed according to any one of embodiments 23-44.

[0247] Embodiment 51. A computer program comprising program code to be executed by a processing circuit (2003) of a vehicle-to-everything V2X application-specific server (2000), whereby execution of the program code causes the V2X application-specific server (2000) to perform operations according to any one of embodiments 23-44.

[0248] Embodiment 52. A computer program product comprising a non-transitory storage medium comprising program code to be executed by a processing circuit (2003) of a vehicle-to-everything V2X application-specific server (2000), whereby execution of the program code causes the V2X application-specific server (2000) to perform operations according to any one of embodiments 23-44.

[0249] Additional instructions are provided below.

[0250] Generally, unless different meanings are clearly given and / or different meanings are implied in the context of the use of the term, all terms used in this article will be interpreted according to their ordinary meaning in the relevant technical field. Unless clearly stated, all references to one / an / this element, device, assembly, part, step, etc. should be openly interpreted as referring to at least one instance of this element, device, assembly, part, step, etc. Unless a step is clearly described as being after or before another step and / or a step must be after or before another step, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Likewise, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

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

[0252] Figure 27 A wireless network in accordance with some embodiments is shown.

[0253] Although the subject matter described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are with respect to wireless networks such as Figure 27For simplicity, Figure 27 The wireless network shown in FIG. 1 depicts only network QQ 106, network nodes QQ 160 and QQ 160b, and WD QQ 110, QQ 110b, and QQ 110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional units suitable for supporting communication 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 QQ 160 and wireless device (WD) QQ 110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and / or use of services provided by or via the wireless network.

[0254] A wireless network can include and / or be connected to any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, a wireless network can be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network can implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), 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.

[0255] Network QQ106 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 that enable communication between devices.

[0256] The network node QQ 160 and the WD QQ 110 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 (whether via wired or wireless connections).

[0257] 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), and NR node Bs (gNBs)). Base stations can be classified based on the amount of coverage provided by the base stations (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 (e.g., 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. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multi-standard radio (MSR) devices such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs. As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network by a wireless device or to provide a service to a wireless device that has accessed the wireless network.

[0258] exist Figure 27 In FIG, the network node QQ160 includes processing circuitry QQ170, device-readable medium QQ180, interface QQ190, auxiliary device QQ184, power supply QQ186, power supply circuitry QQ187, and antenna QQ162. Figure 27The network node QQ160 shown in the example wireless network of FIG can represent a device that includes the combination of hardware components shown, but other embodiments can 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. In addition, although the components of the network node QQ160 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 (for example, the device readable medium QQ180 may include multiple separate hard drives and multiple RAM modules).

[0259] Similarly, network node QQ160 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 some cases where network node QQ160 includes multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among multiple network nodes. For example, a single RNC may control multiple Node Bs. In such a scenario, in some cases, each unique Node B and RNC pair may be considered a single, separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media QQ180 for different RATs), while some components may be reused (e.g., the same antenna QQ162 may be shared by all RATs). Network node QQ160 may also include multiple sets of various exemplary components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into network node QQ160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node QQ 160 .

[0260] The processing circuit QQ 170 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 circuit QQ 170 may include: processing information obtained by the processing circuit QQ 170, for example, 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 determinations as a result of the processing.

[0261] The processing circuitry QQ170 can include one or more of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or combination thereof, or any other suitable circuit that is operable to provide the functionality described herein. For example, the processing circuitry QQ170 can be operable to execute instructions stored in the memory QQ180 or instructions that are otherwise provided to the processing circuitry QQ170. Such functionality can include providing various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry QQ170 can include a system on a chip (SOC).

[0262] In some embodiments, the processing circuitry QQ170 can include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, the radio frequency (RF) transceiver circuitry QQ172 and the baseband processing circuitry QQ174 can be on separate chips (or sets of chips), boards, or units, such as radio and digital units. In alternative embodiments, part or all of the RF transceiver circuitry QQ172 and the baseband processing circuitry QQ174 can be on the same chip or set of chips, boards, or units.

[0263] In particular embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network equipment can be performed by the processing circuitry QQ170 executing instructions stored in the memory QQ180 or memory within the processing circuitry QQ170. In alternative embodiments, some or all of the functionality can be provided by processing circuitry QQ170 without executing instructions stored in device readable medium, such as in a hard-wired manner. In any of these embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuitry QQ170 can be configured to perform the described functions. The benefits provided by such functionality are not limited to the processing circuitry QQ170 or other components of the network node QQ160 but extend to the network node QQ160 as a whole and to its users and wireless networks generally.

[0264] The device-readable medium QQ180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage, 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 and / or computer-executable storage device that stores information, data, and / or instructions that can be used by the processing circuit QQ170. The device-readable medium QQ180 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 can be executed by the processing circuit QQ170 and utilized by the network node QQ160. The device-readable medium QQ180 may be used to store any computations performed by the processing circuit QQ170 and / or any data received via the interface QQ190. In some embodiments, the processing circuit QQ170 and the device-readable medium QQ180 may be considered integrated.

[0265] Interface QQ190 is used for wired or wireless communication of signaling and / or data between network node QQ160, network QQ106, and / or WD QQ110. As shown, interface QQ190 includes port / terminal QQ194 for sending and receiving data to and from network QQ106, for example, via a wired connection. Interface QQ190 also includes radio front-end circuitry QQ192, which can be coupled to antenna QQ162 or, in certain embodiments, form part of antenna QQ162. Radio front-end circuitry QQ192 includes filter QQ198 and amplifier QQ196. Radio front-end circuitry QQ192 can be connected to antenna QQ162 and processing circuitry QQ170. Radio front-end circuitry QQ192 can be configured to condition signals transmitted between antenna QQ162 and processing circuitry QQ170. Radio front-end circuitry QQ192 can receive digital data to be transmitted to other network nodes or WDs via wireless connections. The radio front-end circuit QQ192 can use a combination of filters QQ198 and / or amplifiers QQ196 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 can collect the radio signal, which is then converted into digital data by the radio front-end circuit QQ192. The digital data can be passed to processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.

[0266] In certain alternative embodiments, network node QQ160 can not include separate radio front end circuitry QQ192, and instead, processing circuitry QQ170 can comprise radio front end circuitry and can be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 can be considered a part of interface QQ190. In other embodiments, interface QQ190 can include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 can communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

[0267] Antenna QQ162 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna QQ162 can be coupled to radio front-end circuitry QQ190 and can be any type of antenna and / or antennas known to be used in communication devices. In some embodiments, antenna QQ162 can include one or more omnidirectional, sector or panel antennas operable to send and receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna can be used to send and receive radio signals from any direction, a sector antenna can be used to send and receive radio signals from devices within a particular area, and a panel antenna can be a line of sight antenna used to send and receive radio signals in a relatively straight line. In some cases, the use of more than one antenna can be referred to as MIMO. In certain embodiments, antenna QQ162 can be separate from network node QQ160 and can be connectable to network node QQ160 through an interface or port.

[0268] Antenna QQ162, interface QQ190, and / or processing circuitry QQ170 can be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna QQ162, interface QQ190, and / or processing circuitry QQ170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals can be transmitted to a wireless device, another network node and / or any other network equipment.

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

[0270] Alternative embodiments of network node QQ 160 may include Figure 27 Additional components beyond those shown may be responsible for providing specific aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node QQ 160 may include a user interface device to allow information to be input into network node QQ 160 and to allow information to be output from network node QQ 160. This may allow a user to perform diagnostic, maintenance, repair, and other management functions on network node QQ 160.

[0271] As used herein, wireless device (WD) refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise mentioned, the term WD can be used interchangeably herein with user equipment (UE), and with communication device. The wireless communication can involve sending and / or receiving wireless signals using electromagnetic waves, radio waves, and / or other types of signals suitable for conveying information through air. In some embodiments, the WDs can be configured for communication without the need for direct human interaction (e.g., machine to machine (M2M) communication). For example, the WDs can be designed to transmit information to a network and / or receive information from a network without direct human input. Examples of WDs include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminals, wireless endpoints, mobile stations, tablet computers, laptops, laptop computers built-in devices (LEE), laptop computers mounted devices (LME), smart devices, wireless customer-premises equipment (CPE), in-vehicle wireless terminal equipment, etc. A WD can support device-to-device (D2D) communication, e.g., using

[0272] As shown, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device-readable medium QQ130, user interface device QQ132, auxiliary device QQ134, power supply QQ136, and power supply circuitry QQ137. WD QQ110 may include multiple groups of one or more of the components shown for the different wireless technologies supported by WD QQ110 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components in WD QQ110.

[0273] Antenna QQ111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separated from WD QQ110 and may be connected to WD QQ110 via an interface or port. Antenna QQ111, interface QQ114, and / or processing circuit QQ120 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 QQ111 may be considered an interface.

[0274] As shown, interface QQ114 includes radio front-end circuitry QQ112 and antenna QQ111. Radio front-end circuitry QQ112 includes one or more filters QQ118 and amplifier QQ116. Radio front-end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120 and is configured to condition signals transmitted between antenna QQ111 and processing circuitry QQ120. Radio front-end circuitry QQ112 may be coupled to antenna QQ111 or may be part of antenna QQ111. In some embodiments, WD QQ110 may not include a separate radio front-end circuitry QQ112; instead, processing circuitry QQ120 may include radio front-end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, part or all of RF transceiver circuitry QQ122 may be considered part of interface QQ114. Radio front-end circuitry QQ112 may receive digital data transmitted via a wireless connection to other network nodes or WDs. Radio front-end circuitry QQ112 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters QQ118 and / or amplifier QQ116. The radio signal can then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 can collect the radio signal, which is then converted into digital data by radio front-end circuit QQ112. The digital data can be passed to processing circuit QQ120. In other embodiments, the interface can include different components and / or different combinations of components.

[0275] The processing circuit QQ120 may include a combination of one or more of 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 combination of hardware, software, and / or encoded logic operable to provide WDQQ110 functionality, either alone or in combination with other WDQQ110 components (e.g., device-readable medium QQ130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit QQ120 may execute instructions stored in the device-readable medium QQ130 or in memory within the processing circuit QQ120 to provide the functionality disclosed herein.

[0276] As shown, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In certain embodiments, processing circuitry QQ120 of WD QQ110 may include a system-on-chip (SoC). In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be implemented on separate chips or chipsets. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into a single chip or chipset, while RF transceiver circuitry QQ122 may be implemented on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be implemented on the same chip or chipset, while application processing circuitry QQ126 may be implemented on a separate chip or chipset. In other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry QQ122 may be part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

[0277] In certain embodiments, some or all of the functionality described herein as being performed by the WD may be provided by processing circuit QQ120 executing instructions stored on a device-readable medium QQ130 (which may be a computer-readable storage medium in certain embodiments). In alternative embodiments, some or all of the functionality may be provided by processing circuit QQ120 without, for example, hard-wiring the execution of instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, processing circuit QQ120 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 to processing circuit QQ120 or other components of WD QQ110, but are enjoyed by WD QQ110 as a whole and / or by end users and wireless networks generally.

[0278] Processing circuit QQ 120 may be configured to perform any determination, calculation, or similar operation (e.g., a specific acquisition operation) described herein as being performed by the WD. These operations performed by processing circuit QQ 120 may include: processing information obtained by processing circuit QQ 120, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD QQ 110, 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.

[0279] The device-readable medium QQ130 is operable to store computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that are executable by the processing circuit QQ120. The device-readable medium QQ130 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 a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by the processing circuit QQ120. In some embodiments, the processing circuit QQ120 and the device-readable medium QQ130 may be considered to be integrated.

[0280] User interface device QQ132 may provide components that allow a human user to interact with WD QQ110. This interaction may take various forms, such as visual, auditory, tactile, and the like. User interface device QQ132 may be operable to generate output to the user and allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface device QQ132 installed in WD QQ110. For example, if WD QQ110 is a smartphone, interaction may occur via a touch screen; if WD QQ110 is a smart meter, interaction may occur via a screen that provides usage information (e.g., gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface device QQ132 may include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device QQ132 is configured to allow information to be input into WD QQ110 and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface device QQ132 may include, for example, a microphone, a proximity sensor or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device QQ 132 is also configured to allow information to be output from the WD QQ 110, and to allow the processing circuitry QQ 120 to output information from the WD QQ 110. The user interface device QQ 132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuitry. Using one or more input and output interfaces, devices, and circuitry of the user interface device QQ 132, the WD QQ 110 may communicate with an end user and / or wireless network, allowing them to benefit from the functionality described herein.

[0281] The auxiliary device QQ 134 can be operated to provide more specialized functions that may not normally be performed by the WD. This can include specialized sensors for measuring for various purposes, interfaces for other communication types such as wired communication, etc. The inclusion and types of components of the auxiliary device QQ 134 can vary depending on the embodiment and / or scenario.

[0282] In some embodiments, power source QQ136 can take the form of a battery or battery pack. Other types of power sources can also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. WD QQ110 may also include power circuitry QQ137 for delivering power from power source QQ136 to various components of WD QQ110 that require power from power source QQ136 to perform any functions described or indicated herein. In certain embodiments, power circuitry QQ137 may include power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source. In this case, WD QQ110 may be connected to an external power source (e.g., an electrical outlet) via an input circuit or interface (e.g., a power cord). In certain embodiments, power circuitry QQ137 may also be operable to deliver power from the external power source to power source QQ136. This may be used, for example, to charge power source QQ136. Power circuitry QQ137 may perform any formatting, conversion, or other modifications to the power from power source QQ136 to make it suitable for the respective components of WD QQ110 to which it is being supplied.

[0283] Figure 28 A user equipment according to some embodiments is shown.

[0284] Figure 28 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 who owns and / or operates 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 be, or may not initially be, associated with a specific 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). The UEQQ2200 may be any UE identified by the Third Generation Partnership Project (3GPP), including an NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 28As shown, UE QQ200 is an example of a WD that is 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 28 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0285] exist Figure 28 In the embodiment, UE QQ200 includes a processing circuit QQ201, which is operatively coupled to an input / output interface QQ205, a radio frequency (RF) interface QQ209, a network connection interface QQ211, a memory QQ215 (including a random access memory (RAM) QQ217, a read-only memory (ROM) QQ219, and a storage medium QQ221, etc.), a communication subsystem QQ231, a power supply QQ233 and / or any other components or any combination thereof. The storage medium QQ221 includes an operating system QQ223, an application QQ225, and data QQ227. In other embodiments, the storage medium QQ221 may include other similar types of information. A particular UE may utilize Figure 28 All components shown may be used, or only a subset of these components may be used. The level of integration between components may vary from one UE to another. In addition, a particular UE may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0286] exist Figure 28 In the embodiment of the present invention, processing circuit QQ201 can be configured to process computer instructions and data. Processing circuit QQ201 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 and appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) and appropriate software; or any combination thereof. For example, processing circuit QQ201 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.

[0287] In the depicted embodiment, the input / output interface QQ205 can be configured to provide a communication interface for an input device, an output device, or both. The UE QQ200 can be configured to use an output device via the input / output interface QQ205. 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 or output from the UE QQ200. 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 QQ200 can be configured to use an input device via the input / output interface QQ205 to allow a user to capture information into the UE QQ200. The input device can include a touch-sensitive display or a 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 steering wheel, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display can include a capacitive or resistive touch sensor to sense 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.

[0288] exist Figure 28 In the embodiment, RF interface QQ209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 can be configured to provide a communication interface to network QQ243a. Network QQ243a can include 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, network QQ243a can include a Wi-Fi network. Network connection interface QQ211 can be configured to include a receiver and a transmitter interface, which are used to communicate with one or more other devices via a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). Network connection interface QQ211 can implement receiver and transmitter functions suitable for a communication network link (such as optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0289] RAM QQ217 can be configured to connect to processing circuit QQ201 via bus QQ202 to provide storage or caching of data or computer instructions during the execution of software programs such as an operating system, application programs, and device drivers. ROM QQ219 can be configured to provide computer instructions or data to processing circuit QQ201. For example, ROM QQ219 can be configured to store unchanging low-level system code or data for basic system functions (e.g., basic input and output (I / O), booting, receiving keystrokes from a keyboard stored in non-volatile memory). Storage medium QQ221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cassette, or flash drive. In one example, storage medium QQ221 can be configured to include an operating system QQ223, application programs QQ225 such as a web browser application, a widget or gadget engine, or another application, and data files QQ227. The storage medium QQ 221 may store any one of various operating systems or a combination of operating systems for use by the UE QQ 200 .

[0290] The storage medium QQ 221 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, a smart card memory (e.g., a subscriber identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. The storage medium QQ 221 can allow the UE QQ 200 to access computer-executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to download or upload data. An article of manufacture, such as one utilizing a communication system, can be tangibly embodied in the storage medium QQ 221, which can include device-readable media.

[0291] exist Figure 28In the example, processing circuit QQ201 can be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b can be the same network or different networks. Communication subsystem QQ231 can be configured to include one or more transceivers for communicating with network QQ243b. For example, communication subsystem QQ231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (e.g., another WD, UE, or a base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include a transmitter QQ233 and / or a receiver QQ235 to respectively implement transmitter or receiver functions (e.g., frequency allocation, etc.) suitable for a RAN link. Furthermore, the transmitter QQ233 and receiver QQ235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0292] In the illustrated embodiment, the communication functions of the communication subsystem QQ231 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 function, or any combination thereof. For example, the communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network QQ243b may include 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 QQ243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE QQ200.

[0293] The features, benefits, and / or functions described herein may be implemented in one of the components of UE QQ200, or may be divided among multiple components of UE QQ200. 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 QQ231 may be configured to include any of the components described herein. Furthermore, the processing circuit QQ201 may be configured to communicate with any such component over the bus QQ202. In another example, any such component may be represented by program instructions stored in a memory that, when executed by the processing circuit QQ201, perform the corresponding functions described herein. In another example, the functions of any such component may be divided between the processing circuit QQ201 and the communication subsystem QQ231. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0294] Figure 29 A virtualized environment is shown in accordance with some embodiments.

[0295] Figure 29 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating a virtual version of an apparatus or device, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may 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 relates to an implementation in which at least a portion of a function is 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).

[0296] 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 QQ 300 hosted by one or more hardware nodes QQ 330. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0297] These functions may be implemented by one or more applications QQ320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement certain features, functions, and / or benefits of some embodiments disclosed herein. Applications QQ320 run in a virtualized environment QQ300, which provides hardware QQ330 including processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360, thereby enabling applications QQ320 to operate to provide one or more features, benefits, and / or functions disclosed herein.

[0298] The virtualization environment QQ300 includes a general-purpose or specialized network hardware device QQ330, which includes a set of one or more processors or processing circuits QQ360, 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 may include memory QQ390-1, which can be non-persistent memory for temporarily storing instructions QQ395 or software executed by the processing circuit QQ360. Each hardware device may include one or more network interface controllers (NICs) QQ370 (also known as network interface cards), which include a physical network interface QQ380. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium QQ390-2 in which software QQ395 and / or instructions executable by the processing circuit QQ360 are stored. Software QQ395 may include any type of software, including software for instantiating one or more virtualization layers QQ350 (also known as hypervisors), software for executing virtual machines QQ340, and software that enables them to perform functions, features and / or benefits associated with some embodiments described herein.

[0299] Virtual machine QQ 340 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer QQ 350 or a system hypervisor. Different embodiments of instances of virtual device QQ 320 can be implemented on one or more virtual machines QQ 340 and can be implemented in different ways.

[0300] During operation, processing circuit QQ 360 executes software QQ 395 to instantiate a hypervisor or virtualization layer QQ 350 , which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ 350 may present a virtual operating platform that appears to be networked hardware to virtual machine QQ 340 .

[0301] like Figure 29As shown, hardware QQ 330 can be a standalone network node with general or specific components. Hardware QQ 330 can include antenna QQ 3225 and can implement some functions via virtualization. Alternatively, hardware QQ 330 can be part of a larger hardware cluster (e.g., such as in a data center or customer premises equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) QQ 3100, which, among other things, oversees the lifecycle management of application QQ 320.

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

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

[0304] 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 QQ340 on top of the hardware networking infrastructure QQ330 and corresponds to Figure 29 Application QQ320.

[0305] In some embodiments, one or more radio units QQ 3200, each including one or more transmitters QQ 3220 and one or more receivers QQ 3210, may be coupled to one or more antennas QQ 3225. The radio unit QQ 3200 may communicate directly with the hardware node QQ 330 via one or more appropriate network interfaces, and may be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0306] In some embodiments, some signaling may be implemented using a control system QQ3230, which may alternatively be used for communication between the hardware node QQ330 and the radio unit QQ3200.

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

[0308] refer to Figure 30According to an embodiment, a communication system includes a telecommunications network QQ410, such as a 3GPP-type cellular network, which includes an access network QQ411, such as a radio access network, and a core network QQ414. The access network QQ411 includes a plurality of base stations QQ412a, QQ412b, QQ412c (e.g., NBs, eNBs, gNBs) or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c can be connected to the core network QQ414 via a wired or wireless connection QQ415. A first UE QQ491 located in the coverage area QQ413c is configured to wirelessly connect to or be paged by the corresponding base station QQ412c. A second UE QQ492 in the coverage area QQ413a can wirelessly connect to the corresponding base station QQ412a. Although multiple UEs QQ491 , QQ492 are shown in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or only one UE is connected to the corresponding base station QQ412 .

[0309] Telecommunications network QQ410 itself is connected to a host computer QQ430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunications network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430, or may be via an optional intermediary network QQ420. Intermediary network QQ420 may be one of a public, private, or managed network, or a combination of more than one of these; intermediary network QQ420, if present, may be a backbone network or the Internet; in particular, intermediary network QQ420 may include two or more subnetworks (not shown).

[0310] Overall, Figure 30The communication system enables connectivity between connected UEs QQ491 and QQ492 and a host computer QQ430. This connectivity can be described as an over-the-top (OTT) connection QQ450. The host computer QQ430 and the connected UEs QQ491 and QQ492 are configured to communicate data and / or signaling via the OTT connection QQ450, using the access network QQ411, the core network QQ414, any intermediate networks QQ420, and possibly other infrastructure (not shown) as intermediaries. The OTT connection QQ450 can be transparent because the participating communication devices through which the OTT connection QQ450 passes are unaware of the routing of uplink and downlink communications. For example, the base station QQ412 may not be informed or need not be informed of the past routing of incoming downlink communications with data originating from the host computer QQ430 to be forwarded (e.g., handed over) to the connected UE QQ491. Similarly, the base station QQ412 does not need to be aware of the future routing of outgoing uplink communications from the UE QQ491 to the host computer QQ430.

[0311] Figure 31 A host computer is shown communicating with a user device via a base station over a partially wireless connection in accordance with some embodiments.

[0312] Now refer to Figure 31 To describe an example implementation of the UE, base station, and host computer discussed in the previous paragraphs according to the embodiment. In the communication system QQ500, the host computer QQ510 includes hardware QQ515, which includes a communication interface QQ516 configured to establish and maintain a wired or wireless connection with different communication devices of the communication system QQ500. The host computer QQ510 also includes a processing circuit QQ518, which may have storage and / or processing capabilities. In particular, the processing circuit QQ518 may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The host computer QQ510 also includes software QQ511, which is stored in the host computer QQ510 or can be accessed by the host computer QQ510 and can be executed by the processing circuit QQ518. The software QQ511 includes a host application QQ512. Host application QQ512 is operable to provide services to a remote user, such as a UE QQ530 connected via an OTT connection QQ550 terminating at the UE QQ530 and the host computer QQ510. In providing services to the remote user, host application QQ512 may provide user data sent using the OTT connection QQ550.

[0313] The communication system QQ500 also includes a base station QQ520 provided in the telecommunications system, and the base station QQ520 includes hardware QQ525 that enables it to communicate with the host computer QQ510 and the UE QQ530. The hardware QQ525 may include a communication interface QQ526 for establishing and maintaining wired or wireless connections with different communication devices of the communication system QQ500, and for establishing and maintaining connections with the network devices located in the coverage area ( Figure 31 The communication interface QQ526 may be configured to facilitate a connection QQ560 with the host computer QQ510. The connection QQ560 may be direct, or the connection QQ560 may be through a core network (e.g., a telecommunications system) of the telecommunications system. Figure 31 (not shown) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware QQ525 of base station QQ520 also includes processing circuitry QQ528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions. Base station QQ520 also has software QQ521 stored internally or accessible via an external connection.

[0314] The communication system QQ500 also includes the UE QQ530 mentioned above. The hardware QQ535 of the UE QQ530 may include a radio interface QQ537, which is configured to establish and maintain a wireless connection QQ570 with a base station serving the coverage area in which the UE QQ530 is currently located. The hardware QQ535 of the UE QQ530 also includes processing circuitry QQ538, which may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination of these items (not shown) suitable for executing instructions. The UE QQ530 also includes software QQ531 stored in the UE QQ530 or accessible by the UE QQ530 and executable by the processing circuitry QQ538. The software QQ531 includes a client application QQ532. The client application QQ532 is operable to provide services to human or non-human users via the UE QQ530 with the support of the host computer QQ510. In the host computer QQ 510, the executing host application QQ 512 can communicate with the executing client application QQ 532 via an OTT connection QQ 550 that terminates at the UE QQ 530 and the host computer QQ 510. In providing services to users, the client application QQ 532 can receive request data from the host application QQ 512 and provide user data in response to the request data. The OTT connection QQ 550 can transmit both the request data and the user data. The client application QQ 532 can interact with the user to generate the user data it provides.

[0315] Notice, Figure 31 The host computer QQ510, base station QQ520 and UE QQ530 shown can be respectively Figure 30 The host computer QQ430, one of the base stations QQ412a, QQ412b, QQ412c and one of the UEs QQ491, QQ492 are similar or identical. That is, the internal working principles of these entities can be as follows Figure 31 shown, and independently, the surrounding network topology can be Figure 30 The surrounding network topology.

[0316] exist Figure 31 In FIG, OTT connection QQ 550 has been abstractly drawn to illustrate communication between host computer QQ 510 and UE QQ 530 via base station QQ 520, without explicitly referencing any intermediate devices and the precise routing of messages through these devices. The network infrastructure can determine the routing, and the network infrastructure can be configured to hide the routing from UE QQ 530 or the service provider operating host computer QQ 510, or both. While OTT connection QQ 550 is active, the network infrastructure can further make decisions based on which it dynamically changes the routing (e.g., based on load balancing considerations or network reconfiguration).

[0317] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments can improve the performance of OTT services provided to the UE QQ530 using the OTT connection QQ550 (where the wireless connection QQ570 forms the final segment). 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.

[0318] A measurement process may be provided for the purpose of monitoring data rate, latency, and other factors that one or more embodiments improve upon. In response to changes in measurement results, an optional network function may also be provided for reconfiguring the OTT connection QQ550 between the host computer QQ510 and the UE QQ530. The measurement process and / or network function for reconfiguring the OTT connection QQ550 may be implemented in the software QQ511 and hardware QQ515 of the host computer QQ510, or in the software QQ531 and hardware QQ535 of the UE QQ530, 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 QQ550 passes; the sensor may participate in the measurement process by providing values ​​of the monitored quantities exemplified above, or other physical quantities from which the software QQ511 or QQ531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ550 may include message formats, retransmission settings, preferred routing, and the like. The reconfiguration need not affect the base station QQ520 and may be unknown or imperceptible to the base station QQ520. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer QQ510 to measure throughput, propagation time, latency, etc. The measurements may be achieved because software QQ511 and QQ531 cause messages, particularly empty or "dummy" messages, to be sent using OTT connection QQ550 during their monitoring of propagation time, errors, etc.

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

[0320] Figure 32 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 30 and Figure 31 In order to simplify the present disclosure, only the host computers, base stations and UEs described in this section are included. Figure 32 Reference is made to the accompanying drawings of FIG. In step QQ610, the host computer provides user data. In sub-step QQ611 of step QQ610 (which may be optional), the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (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 QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

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

[0322] Figure 33 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 30 and Figure 31 To simplify the present disclosure, this section only includes the host computer, base station and UE described in Figure 33 Reference is made to the accompanying drawings of the present invention. In step QQ710 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 QQ720, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout this disclosure, this transmission may be through a base station. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

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

[0324] 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 30 and Figure 31 To simplify the present disclosure, this section only includes the host computer, base station and UE described in Figure 34 Reference is made to the accompanying drawings. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In sub-step QQ821 (which may be optional) of step QQ820, the UE provides user data by executing a client application. In sub-step QQ811 (which may be optional) of step QQ810, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, the UE initiates transmission of the user data to the host computer in sub-step QQ830 (which may be optional). In step QQ840 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the host computer receives user data sent from the UE.

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

[0326] 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 30 and Figure 31 To simplify the present disclosure, this section only includes the host computer, base station and UE described in Figure 35 Reference is made to the accompanying drawings. In step QQ910 (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 QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0327] 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 via a processing circuit, which may include one or more microprocessors or microcontrollers and other digital hardware that may include a digital signal processor (DSP), 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 a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, etc. 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 technologies described herein. In some implementations, the processing circuit may be used to cause the corresponding functional units to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0328] The term "unit" may have a 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. as described herein.

[0329] abbreviation

[0330] At least some of the following abbreviations may be used in this disclosure. If there is a discrepancy between abbreviations, the above usage shall take precedence. If listed multiple times below, the first listing shall take precedence over subsequent listings.

[0331] 1x RTT CDMA2000 1x Radio Transmission Technology

[0332] 3GPP Third Generation Partnership Project

[0333] 5G fifth generation

[0334] ABS Almost Blank Subframe

[0335] ARQ Automatic Repeat Request

[0336] AWGN Additive White Gaussian Noise

[0337] BCCH Broadcast Control Channel

[0338] BCH Broadcast Channel

[0339] Carrier Aggregation (CA)

[0340] CC carrier component

[0341] CCCH SDU Common Control Channel SDU

[0342] CDMA Code Division Multiple Access

[0343] CGI Cell Global Identifier

[0344] CIR Channel Impulse Response

[0345] CP Cyclic Prefix

[0346] CPICH Common Pilot Channel

[0347] CPICH Ec / No CPICH received energy per chip divided by the power density in the frequency band

[0348] CQI Channel Quality Information

[0349] C-RNTI Cell RNTI

[0350] CSI Channel State Information

[0351] DCCH Dedicated Control Channel

[0352] DL Downlink

[0353] DM demodulation

[0354] DMRS Demodulation Reference Signal

[0355] DRX Discontinuous Reception

[0356] DTX Discontinuous Transmission

[0357] DTCH Dedicated Traffic Channel

[0358] DUT device under test

[0359] E-CID enhanced cell ID (positioning method)

[0360] E-SMLC evolved serving mobile location center

[0361] ECGI evolved CGI

[0362] eNB E-UTRAN Node B

[0363] ePDCCH enhanced physical downlink control channel

[0364] E-SMLC evolved serving mobile location center

[0365] E-UTRA evolved UTRA

[0366] E-UTRAN evolved UTRAN

[0367] FDD frequency division duplex

[0368] FFS further study

[0369] GERAN GSM EDGE radio access network

[0370] gNB base station in NR

[0371] GNSS global navigation satellite system

[0372] GSM global system for mobile communications

[0373] HARQ hybrid automatic repeat request

[0374] HO handover

[0375] HSPA high speed packet access

[0376] HRPD high rate packet data

[0377] LOS line of sight

[0378] LPP LTE positioning protocol

[0379] LTE long term evolution

[0380] MAC medium access control

[0381] MBMS multimedia broadcast multicast service

[0382] MBSFN multimedia broadcast multicast service single frequency network

[0383] MBSFN ABS MBSFN Almost Blank Subframe

[0384] MDT Minimized Drive Test

[0385] MIB Master Information Block

[0386] MME Mobility Management Entity

[0387] MSC Mobile Switching Center

[0388] NPDCCH Narrowband Physical Downlink Control Channel

[0389] NR New Radio

[0390] OCNG OFDMA channel noise generator

[0391] OFDM Orthogonal Frequency Division Multiplexing

[0392] OFDMA Orthogonal Frequency Division Multiple Access

[0393] OSS Operation Support System

[0394] OTDOA observed time difference of arrival

[0395] O&M

[0396] PBCH Physical Broadcast Channel

[0397] P-CCPCH Primary Common Control Physical Channel

[0398] PCell Primary Cell

[0399] PCFICH Physical Control Format Indicator Channel

[0400] PDCCH Physical Downlink Control Channel

[0401] PDP Profile Delay Profile

[0402] PDSCH Physical Downlink Shared Channel

[0403] PGW Packet Gateway

[0404] PHICH Physical Hybrid ARQ Indicator Channel

[0405] PLMN Public Land Mobile Network

[0406] PMI Precoder Matrix Indicator

[0407] PRACH Physical Random Access Channel

[0408] PRS Positioning Reference Signal

[0409] PSS Primary Synchronization Signal

[0410] PUCCH Physical Uplink Control Channel

[0411] PUSCH Physical Uplink Shared Channel

[0412] RACH Random Access Channel

[0413] QAM Quadrature Amplitude Modulation

[0414] RAN Radio Access Network

[0415] RAT Radio Access Technology

[0416] RLM Radio Link Management

[0417] RNC Radio Network Controller

[0418] RNTI Radio Network Temporary Identifier

[0419] RRC Radio Resource Control

[0420] RRM Radio Resource Management

[0421] RS reference signal

[0422] RSCP Received Signal Code Power

[0423] RSRP Reference Symbol Received Power or Reference Signal Received Power

[0424] RSRQ Reference Signal Received Quality or Reference Symbol Received Quality

[0425] RSSI Received Signal Strength Indicator

[0426] RSTD Reference Signal Time Difference

[0427] SCH Synchronization Channel

[0428] SCell Secondary Cell

[0429] SDU Service Data Unit

[0430] SFN System Frame Number

[0431] SGW Service Gateway

[0432] SI System Information

[0433] SIB System Information Block

[0434] SNR signal-to-noise ratio

[0435] SON self-optimizing network

[0436] SS synchronization signal

[0437] SSS Secondary synchronization signal

[0438] TDD Time Division Duplex

[0439] TDOA Time Difference of Arrival

[0440] TOA Time of Arrival

[0441] TSS three-level synchronization signal

[0442] TTI Transmission Time Interval

[0443] UE User Equipment

[0444] UL Uplink

[0445] UMTS Universal Mobile Telecommunications System

[0446] USIM Universal Subscriber Identity Module

[0447] UTDOA Uplink Time Difference of Arrival

[0448] UTRA Universal Terrestrial Radio Access

[0449] UTRAN Universal Terrestrial Radio Access Network

[0450] WCDMA Wideband CDMA

[0451] WLAN broadband local area network

[0452] Additional definitions and examples are discussed below.

[0453] In the above description of various embodiments of the present invention concept, it will be understood that the terms used herein are only for the purpose of describing specific embodiments and are not intended to be limitations of the present invention concept. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those generally understood by those of ordinary skill in the art to which the present invention concept belongs. It will also be 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 art, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.

[0454] When a unit is referred to as being "connected to," "coupled to," "responsive to" (or variations thereof) another unit, it may be directly connected to, coupled to, or responsive to the other unit, or there may be intermediate units. In contrast, when a unit is referred to as being "directly connected to," "directly coupled to," "directly responsive to" (or variations thereof) another unit, there are no intermediate units. Identical numbers refer to identical units herein. In addition, as used herein, "coupling," "connecting," "responsive" or variations thereof may include wireless coupling, connection, or response. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, 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 listed associated items.

[0455] It will be understood that although the terms first, second, third, etc. may be used herein to describe various units / operations, these units / operations should not be limited by these terms. These terms are only used to distinguish one unit / operation from another unit / operation. Thus, a first unit / operation in some embodiments may be referred to as a second unit / operation in other embodiments without departing from the teachings of the present inventive concept. The same reference numerals or the same reference indicators within this specification represent the same or similar units.

[0456] As used herein, the terms "comprises," "includes," "having," or variations thereof are open ended and include one or more stated features, integers, units, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, units, steps, components, functions, or combinations thereof. Furthermore, as used herein, the general abbreviation "such as," derived from the Latin phrase "exempli gratia," may be used to introduce or specify one or more general examples of previously mentioned items and is not intended as a limitation of such items. The general abbreviation "i.e.," derived from the Latin phrase "id est," may be used to specify a specific item from a more general description.

[0457] 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 these instructions, when executed by a processor of a computer and / or other programmable data processing device, transform and control transistors, values ​​stored in storage cells, and other hardware components within such circuits to implement the functions / operations specified in one or more blocks in the block diagrams and / or flowcharts, thereby generating an apparatus (function) and / or structure that implements the functions / operations specified in the blocks in the block diagrams and / or flowcharts.

[0458] These computer program instructions may also be stored in a tangible computer-readable medium, which may cause a computer or other programmable data processing device 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 / operations specified in one or more blocks in the block diagrams and / or flowcharts. Therefore, embodiments of the inventive concept may be embodied in hardware and / or software (including firmware, resident software, microcode, etc.), which runs on a processor such as a digital signal processor, and the hardware and / or software may be collectively referred to as "circuits," "modules," or variations thereof.

[0459] It should also be noted that in some alternative implementations, the function / operation marked in the block can occur in a sequence different from that marked in the flow chart. For example, two continuous blocks can actually be performed substantially in parallel, and they also can be performed in reverse order sometimes, depending on the function / operation involved. In addition, the function of the given block of flow chart and / or block diagram can be divided into a plurality of blocks, and / or the function of two or more blocks of flow chart and / or block diagram can be integrated at least in part. Finally, other blocks can be added / inserted between the blocks shown, and / or blocks / operation can be omitted and not depart from the scope of the present invention's concept. In addition, although some figures comprise arrows to illustrate the primary direction of communication on communication paths, it will be understood that communication can occur in the direction opposite to the arrows shown.

[0460] Many changes and modifications can be made to the embodiment without departing substantially from the principle of the inventive concept. In this article, all these changes and modifications are intended to be included in the scope of the inventive concept. Therefore, the subject matter disclosed above is considered to be illustrative and not restrictive, and the example of the embodiment is intended to cover all these modifications, enhancements and other embodiments that fall within the spirit and scope of the inventive concept. Therefore, to the maximum extent allowed by law, the scope of the inventive concept will be determined by the most extensive permitted interpretation of this disclosure (including the example of the embodiment and its equivalent), and should not be defined or limited by the detailed description above.

Claims

1. A method for operating a vehicle-to-everything (V2X) application enabler (VAE) server, the method comprising: receiving a V2X application specific server registration request message from the V2X application specific server, the V2X application specific server registration request message including an identifier of the V2X application specific server for receiving a V2X uplink message originating from a V2X user equipment (UE); as well as In response to receiving the V2X application specific server registration request message, sending a V2X application specific server registration response message to the V2X application specific server.

2. The method according to claim 1, wherein The V2X application specific server registration request message further includes at least one of a V2X service identifier to which the V2X application specific server is registered and / or an identifier of a geographical area to which the V2X application specific server is registered.

3. The method according to claim 2, wherein: The V2X application specific server registration request message further includes a request to register to receive V2X uplink messages originated from the V2X UE device from the VAE server at the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

4. The method according to claim 3, further comprising: A V2X uplink message originating from a V2X UE device is sent from the VAE server to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

5. The method according to claim 2, further comprising: Receive V2X uplink messages from V2X UE devices; as well as In response to receiving the V2X uplink message from the V2X UE device, the V2X uplink message is sent from the VAE server to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

6. The method according to any one of claims 1 to 5, wherein The V2X application specific server registration response message includes an indication of a result of registration in response to the V2X application specific server registration request message, wherein the indication of the result indicates one of success or failure of the registration in response to the V2X application specific server registration request message.

7. A method for operating a vehicle-to-everything (V2X) application-specific server, the method comprising: Sending a V2X application-specific server registration request message to a vehicle-to-everything (V2X) application enabler (VAE) server, the V2X application-specific server registration request message including an identifier of a V2X application-specific server for receiving V2X uplink messages originating from a V2X user equipment (UE); as well as A V2X application-specific server registration response message is received from the VAE server, wherein the V2X application-specific server registration response message is in response to the V2X application-specific server registration request message.

8. The method according to claim 7, wherein: The V2X application specific server registration request message further includes at least one of a V2X service identifier to which the V2X application specific server is registered and / or an identifier of a geographical area to which the V2X application specific server is registered.

9. The method according to claim 8, wherein The V2X application specific server registration request message further includes a request to register to receive V2X uplink messages originated from the V2X UE device from the VAE server at the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

10. The method according to claim 9, further comprising: A V2X uplink message originating from a V2X UE device is received from the VAE server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

11. The method according to any one of claims 7 to 10, wherein: The V2X application specific server registration response message includes an indication of a result of registration in response to the V2X application specific server registration request message, wherein the indication of the result indicates one of success or failure of the registration in response to the V2X application specific server registration request message.

12. A vehicle-to-everything (V2X) application enabler (VAE) server, adapted to execute: receiving a V2X application specific server registration request message from the V2X application specific server, the V2X application specific server registration request message including an identifier of the V2X application specific server for receiving a V2X uplink message originating from a V2X user equipment (UE); and In response to receiving the V2X application specific server registration request message, sending a V2X application specific server registration response message to the V2X application specific server.

13. The vehicle-to-everything (V2X) application enabler (VAE) server according to claim 12, wherein: The V2X application specific server registration request message further includes at least one of a V2X service identifier to which the V2X application specific server is registered and / or an identifier of a geographical area to which the V2X application specific server is registered.

14. The vehicle-to-everything (V2X) application enabler (VAE) server according to claim 13, wherein: The V2X application specific server registration request message further includes a request to register to receive V2X uplink messages originating from the V2X UE device from the VAE server at the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

15. The vehicle-to-everything (V2X) application enabler (VAE) server according to claim 14, further adapted to execute: A V2X uplink message originating from a V2X UE device is sent from the VAE server to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

16. The vehicle-to-everything (V2X) application enabler (VAE) server according to claim 13, further adapted to execute: receiving a V2X uplink message from a V2X UE device; and In response to receiving the V2X uplink message from the V2X UE device, the V2X uplink message is sent from the VAE server to the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

17. The vehicle-to-everything (V2X) application enabler (VAE) server according to any one of claims 12 to 16, wherein: The V2X application specific server registration response message includes an indication of a result of registration in response to the V2X application specific server registration request message, wherein the indication of the result indicates one of success or failure of the registration in response to the V2X application specific server registration request message.

18. A computer-readable storage medium storing program code to be executed by a processing circuit of a vehicle-to-everything (V2X) application enabler (VAE) server, whereby execution of the program code causes the VAE server to perform the method according to any one of claims 1-6.

19. A vehicle-to-everything (V2X) application-specific server, adapted to execute: Sending a V2X application-specific server registration request message to a vehicle-to-everything (V2X) application enabler (VAE) server, the V2X application-specific server registration request message including an identifier of a V2X application-specific server for receiving V2X uplink messages originating from a V2X user equipment (UE); and Receive a V2X application specific server registration response message from the VAE server, wherein: The V2X application specific server registration response message is in response to the V2X application specific server registration request message.

20. The vehicle-to-everything (V2X) application-specific server according to claim 19, wherein: The V2X application specific server registration request message further includes at least one of a V2X service identifier to which the V2X application specific server is registered and / or an identifier of a geographical area to which the V2X application specific server is registered.

21. The vehicle-to-everything (V2X) application-specific server according to claim 20, wherein: The V2X application specific server registration request message further includes a request to register to receive V2X uplink messages originated from the V2X UE device from the VAE server at the V2X application specific server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

22. The vehicle-to-everything (V2X) application-specific server according to claim 21, further adapted to execute: A V2X uplink message originating from a V2X UE device is received from the VAE server based on at least one of the V2X service identifier and / or the identifier of the geographical area.

23. The vehicle-to-everything (V2X) application-specific server according to any one of claims 19 to 22, wherein: The V2X application specific server registration response message includes an indication of a result of registration in response to the V2X application specific server registration request message, wherein the indication of the result indicates one of success or failure of the registration in response to the V2X application specific server registration request message.

24. A computer-readable storage medium storing program code to be executed by a processing circuit of a vehicle-to-everything (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 7-11.

Images