Method for identifying VAE server and related V2X wireless device and server

Abstract

The present invention relates to a method for identifying a VAE server and a related V2X wireless device and server. A method for operating a first VAE server is disclosed. V2X message information by geographic area is received from a V2X application specific server. Location information is received from a VAE client of a wireless device, wherein the location information indicates the location of the wireless device. In response to receiving the location information and in response to the V2X message information by geographic area, a second VAE server is identified based on the location information. An address of the second VAE server is sent to the VAE client of the wireless device. A related VAE server and a V2X wireless device are also disclosed.

Description

[0001] This application is a divisional application of the Chinese patent application “Method for identifying VAE server and related V2X wireless device and server” with application number 202080038538.5 (filing date March 12, 2020). Technical Field

[0002] The present disclosure relates generally to communications, and more particularly, to a communication method and related devices and nodes supporting V2X wireless communications. Background Art

[0003] Server discovery in ITS / V2X message distribution is discussed in this disclosure. A V2X wireless device UE may need to discover a V2X application server (AS) to register to receive specific ITS / V2X messages. Server discovery refers to a mechanism used by a wireless device UE to discover which servers are available and how to connect to the server. A V2X wireless device UE is typically provided with a fully qualified domain name (FQDN) and then uses the FQDN to connect to the application server AS.

[0004] 3GPP SA6 TR 23.795 (also referred to as reference [1]) and 3GPP SA6 TS 23.286 (also referred to as reference [3]) define V2X application enabler (VAE) functions at V2X AS and V2X UE. VAE is middleware that can free applications from multiple functions (e.g., location management, configuration management) and / or it can provide an interface to the network.

[0005] Figure 1A A simplified architecture model of the V2X application layer as described in reference [1] is shown (see reference [1] for details). Figure 7 .1.1.2-1). It utilizes the architecture reference model specified in subclause 4.2 of 3GPP TS 23.285 (also referred to as reference [2]), which may have an impact on application layer support aspects. Figure 1A It is shown that the Figure 7 .1.1.2-1 corresponds to the simplified architecture model of the V2X application layer, and Figure 1B The V2X application layer functional model corresponding to Figure 6.2-2 of 3GPP TS 23.286 (also referred to as reference [3]) is shown.

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

[0007] Reference point V1 supports V2X application related interactions between V2X wireless devices UE and V2X application servers AS and is specified in 3GPP TS 23.285 (reference [2]). This reference point is supported in both unicast transmission mode and multicast transmission mode. Reference point V5 supports interactions between V2X wireless devices UE and is specified in 3GPP TS 23.285 (reference [2]).

[0008] Figure 2 (corresponding to reference [1] Figure 7 .1.1.2-2) shows the detailed V2X application layer functional model defined in TR 23.795 (reference [1]). It enhances the simplified architecture model of the V2X application layer by specifying the functional entities at the V2X application layer. Figure 2 It is shown that the Figure 7 .1.1.2-2 corresponds to the V2X application layer functional model.

[0009] The V2X application server may include a V2X application enabler (VAE) server and a V2X application specific server. The VAE server provides V2X application layer support functions to the V2X application specific server through the Vs reference point.

[0010] The V2X wireless device UE may include a VAE client and a V2X application-specific client. The VAE client provides V2X application layer support functions to the V2X application-specific client via a Vc reference point.

[0011] The VAE client communicates with the VAE server via the V1-AE reference point. The V2X application-specific client communicates with the V2X application-specific server via the V1-Application (V1-APP) reference point.

[0012] The VAE client of the V2X wireless device UE2 communicates with the VAE client of the V2X wireless device UE1 via the V5-AE reference point. The V2X application specific client of the V2X wireless device UE2 communicates with the VAE client of the V2X wireless device UE1 via the V5-Application (V5-APP) reference point.

[0013] In a distributed deployment, VAE servers communicate through the VAE-E reference point.

[0014] As described above, the V2X wireless device UE may discover a V2X application server (AS) to register to receive specific ITS / V2X messages. However, the V2X application server (AS) may be associated with a geographical area / region. Accordingly, the V2X wireless device UE may register with a V2X AS associated with a geographical area / region, but the V2X wireless device UE may move outside the geographical area / region associated with the V2X AS with which it is registered. Summary of the invention

[0015] According to some embodiments of the present inventive concept, a method of operating a first vehicle-to-everything V2X application enabler (VAE) server is provided. V2X message information by geographic region is received from a V2X application specific server. Location information is received from a VAE client of a wireless device, wherein the location information indicates a location of the wireless device. In response to receiving the location information and in response to the V2X message information by geographic region, a second VAE server is identified based on the location information. An address of the second VAE server is sent to the VAE client of the wireless device.

[0016] According to some other embodiments of the present inventive concept, a method of operating a first vehicle-to-everything V2X application enabler VAE server is provided. A server discovery request is received from a second VAE server, wherein the server discovery request includes location information of a wireless device. In response to the server discovery request, a server discovery response is sent to the second VAE server, wherein the server discovery response includes an address of the first VAE server.

[0017] According to other embodiments of the inventive concept, a method for operating a vehicle-to-everything (V2X) wireless device is provided. VAE server information for a plurality of VAE servers is provided, wherein the VAE server information includes a corresponding address of each of the plurality of VAE servers, a corresponding geographic area associated with the VAE server, and / or corresponding service / message information related to a V2X service available from the VAE server. The V2X wireless device subscribes to receive V2X messages from a first VAE server (01) of the plurality of VAE servers. In response to detecting movement from a first geographic area associated with the first VAE server to a second geographic area, a second VAE server associated with the second geographic area of ​​the plurality of VAE servers is identified based on the VAE server information. In response to identifying the second VAE server, the V2X wireless device subscribes to receive V2X messages from the second VAE server.

[0018] According to other embodiments of the present inventive concept, a first vehicle-to-everything V2X application enabler VAE server is configured to operate with a communication network. The VAE server includes a processing circuit and a memory coupled to the processing circuit. The memory includes instructions, which, when executed by the processing circuit, cause the first VAE server to: receive V2X message information by geographic area from a V2X application-specific server; receive location information from a VAE client of a wireless device, wherein the location information indicates the location of the wireless device; in response to receiving the location information and in response to the V2X message information by geographic area, identify a second VAE server (02) based on the location information; and send the address of the second VAE server (02) to the VAE client of the wireless device.

[0019] According to other embodiments of the present inventive concept, a first vehicle-to-everything V2X application enabler VAE server is configured to operate with a communication network. The VAE server is adapted to: receive V2X message information by geographic area from a V2X application specific server; receive location information from a VAE client of a wireless device, wherein the location information indicates the location of the wireless device; in response to receiving the location information and in response to the V2X message information by geographic area, identify a second VAE server (02) based on the location information; and send the address of the second VAE server (02) to the VAE client of the wireless device.

[0020] According to other embodiments of the present inventive concept, a first vehicle-to-everything V2X application enabler VAE server is configured to operate with a communication network. The VAE server includes a processing circuit and a memory coupled to the processing circuit. The memory includes instructions, which, when executed by the processing circuit, cause the first VAE server to: receive a server discovery request from a second VAE server (01), wherein the server discovery request includes location information of a wireless device; and in response to the server discovery request, send a server discovery response to the second VAE server, wherein the server discovery response includes an address of the first VAE server.

[0021] According to other embodiments of the present inventive concept, a first vehicle-to-everything V2X application enabler VAE server is configured to operate with a communication network. The first VAE server is adapted to: receive a server discovery request from a second VAE server (01), wherein the server discovery request includes location information of a wireless device; and in response to the server discovery request, send a server discovery response to the second VAE server, wherein the server discovery response includes an address of the first VAE server.

[0022] According to other embodiments of the inventive concept, a computer program includes program code to be executed by a processing circuit of a first VAE server, the first VAE server being configured to operate with a communication network. The execution of the program code causes the first VAE server to: receive V2X message information by geographic area from a V2X application specific server; receive location information from a VAE client of a wireless device, wherein the location information indicates a location of the wireless device; in response to receiving the location information and in response to the V2X message information by geographic area, identify a second VAE server based on the location information; and send an address of the second VAE server to the VAE client of the wireless device.

[0023] According to other embodiments of the inventive concept, a computer program product includes a non-transitory storage medium, the non-transitory storage medium including program code to be executed by a processing circuit of a first VAE server, the first VAE server being configured to operate in a communication network. The execution of the program code causes the first VAE server to: receive V2X message information by geographic area from a V2X application-specific server; receive location information from a VAE client of a wireless device, wherein the location information indicates the location of the wireless device; in response to receiving the location information and in response to the V2X message information by geographic area, identify a second VAE server (02) based on the location information; and send an address of the second VAE server (02) to the VAE client of the wireless device.

[0024] According to other embodiments of the inventive concept, a computer program includes program code to be executed by a processing circuit of a first VAE server, the first VAE server being configured to operate with a communication network. The execution of the program code causes the first VAE server to: receive a server discovery request from a second VAE server (01), wherein the server discovery request includes location information of a wireless device; and in response to the server discovery request, send a server discovery response to the second VAE server, wherein the server discovery response includes an address of the first VAE server.

[0025] According to other embodiments of the inventive concept, a computer program product includes a non-transitory storage medium, the non-transitory storage medium including program code to be executed by a processing circuit of a first VAE server, the first VAE server being configured to operate in a communication network. The execution of the program code causes the first VAE server to: receive a server discovery request from a second VAE server (01), wherein the server discovery request includes location information of a wireless device; and in response to the server discovery request, send a server discovery response to the second VAE server, wherein the server discovery response includes an address of the first VAE server.

[0026] According to other embodiments of the inventive concept, a vehicle-to-everything V2X wireless device is configured to operate in a communication network. The V2X wireless device includes a processing circuit and a memory coupled to the processing circuit. The memory includes instructions that, when executed by the processing circuit, cause the V2X wireless device to: provide VAE server information for a plurality of VAE servers, wherein the VAE server information includes a corresponding address of each of the plurality of VAE servers, a corresponding geographic area associated with the VAE server, and / or corresponding service / message information related to a V2X service available from the VAE server; subscribe to receive V2X messages from a first VAE server (01) of the plurality of VAE servers; in response to detecting movement from a first geographic area associated with the first VAE server to a second geographic area, identify a second VAE server (02) associated with the second geographic area of ​​the plurality of VAE servers based on the VAE server information; and in response to identifying the second VAE server, subscribe to receive V2X messages from the second VAE server.

[0027] According to other embodiments of the inventive concept, a vehicle-to-everything V2X wireless device is configured to operate in a communication network. The V2X wireless device is adapted to: provide VAE server information for a plurality of VAE servers, wherein the VAE server information includes a corresponding address of each of the plurality of VAE servers, a corresponding geographic area associated with the VAE server, and / or corresponding service / message information related to a V2X service available from the VAE server; subscribe to receive V2X messages from a first VAE server (01) of the plurality of VAE servers; in response to detecting movement from a first geographic area associated with the first VAE server to a second geographic area, identify a second VAE server (02) associated with the second geographic area of ​​the plurality of VAE servers based on the VAE server information; and in response to identifying the second VAE server, subscribe to receive V2X messages from the second VAE server.

[0028] According to other embodiments of the inventive concept, a computer program includes program code to be executed by a processing circuit of a V2X wireless device, the V2X wireless device being configured to operate in a communication network. Execution of the program code causes the V2X wireless device to: provide VAE server information for a plurality of VAE servers, wherein the VAE server information includes a respective address of each of the plurality of VAE servers, a respective geographic area associated with the VAE server, and / or respective service / message information related to a V2X service available from the VAE server; subscribe to receive V2X messages from a first VAE server (01) of the plurality of VAE servers; in response to detecting movement from a first geographic area associated with the first VAE server to a second geographic area, identify a second VAE server (02) associated with the second geographic area of ​​the plurality of VAE servers based on the VAE server information; and in response to identifying the second VAE server, subscribe to receive V2X messages from the second VAE server.

[0029] According to other embodiments of the inventive concept, a computer program product includes a non-transitory storage medium, the non-transitory storage medium including program code to be executed by a processing circuit of a V2X wireless device, the V2X wireless device being configured to operate in a communication network. Execution of the program code causes the V2X wireless device to: provide VAE server information for a plurality of VAE servers, wherein the VAE server information includes a respective address of each of the plurality of VAE servers, a respective geographic area associated with the VAE server, and / or respective service / message information related to a V2X service available from the VAE server; subscribe to receive V2X messages from a first VAE server (01) of the plurality of VAE servers; in response to detecting movement from a first geographic area associated with the first VAE server to a second geographic area, identify a second VAE server (02) associated with the second geographic area of ​​the plurality of VAE servers based on the VAE server information; and in response to identifying the second VAE server, subscribe to receive V2X messages from the second VAE server.

[0030] According to some embodiments of the present inventive concept, support can be provided for V2X wireless devices moving between different geographical areas served by different VAE servers. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0032] Figure 1A It is shown that the Figure 7 .1.1.2-1 The architecture model of the V2X application layer corresponding to;

[0033] Figure 1B The V2X application layer functional model corresponding to Figure 6.2-2 of reference [3] is shown;

[0034] Figure 2 It is shown that the Figure 7 .1.1.2-2 Corresponding V2X application layer functional model;

[0035] Figure 3 shows VAE client and server publishing and server association with different geographic regions according to some embodiments of the inventive concept;

[0036] Figure 4 shows a VAE client being redirected to VAE server 02 when moving to A02 according to some embodiments of the inventive concept;

[0037] Figure 5A illustrates VAE server discovery operations when moving to a new geographic region according to some embodiments of the present inventive concepts;

[0038] Figure 5B illustrates VAE server discovery operations according to some embodiments of the inventive concept;

[0039] Fig. 6A illustrates V2X wireless device UE client operations for initial V2X UE connection to a VAE server in geographic area 01 according to some embodiments of the present inventive concepts;

[0040] Figure 6B illustrates V2X wireless device UE client operations when the V2X UE moves to geographic area 02 according to some embodiments of the present inventive concept;

[0041] Figure 7 A portion of Annex D of 3GPP TS 23.285 v15.1.0 is shown;

[0042] Figure 8 is a table illustrating server discovery requests according to some embodiments of the inventive concept;

[0043] Fig. 9 is a table illustrating server discovery responses according to some embodiments of the inventive concept;

[0044] Fig.10 is a block diagram illustrating a V2X wireless device UE according to some embodiments of the inventive concept;

[0045] Fig.11 is a block diagram illustrating a radio access network RAN ​​node (e.g. a base station eNB / gNB) according to some embodiments of the inventive concept;

[0046] Fig.12 is a block diagram illustrating a VAE server according to some embodiments of the inventive concept;

[0047] Fig.13A and 13B is a flowchart illustrating the operation of a VAE server (VAE server 01) according to some embodiments of the inventive concept;

[0048] Fig.14 is a flowchart illustrating the operation of a VAE server (VAE server 02) according to some embodiments of the inventive concept;

[0049] Fig.15is a flow chart illustrating the operation of a V2X wireless device UE according to some embodiments of the inventive concept;

[0050] Fig.16 is a block diagram of a wireless network according to some embodiments;

[0051] Fig.17 is a block diagram of a user equipment according to some embodiments;

[0052] Fig.18 is a block diagram of a virtualization environment according to some embodiments;

[0053] Fig.19 is a block diagram of a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0054] Fig. 20 is a block diagram of a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0055] Fig.21 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;

[0056] Fig. 22 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;

[0057] Fig.23 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;

[0058] Fig.24 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;

[0059] Fig.25 is a block diagram illustrating elements of a V2X service provider domain and a PLMN operator domain according to some embodiments;

[0060] Fig.26 is a table illustrating a server relocation request according to some embodiments;

[0061] Fig. 27 is a table illustrating a server relocation response according to some embodiments; and

[0062] Fig.28 is a message diagram illustrating a process for VAE server relocation according to some embodiments. DETAILED DESCRIPTION

[0063] 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 defaulted to being present / used in another embodiment.

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

[0065] Fig.10 1 is a block diagram showing units of a V2X wireless device UE1000 (also referred to as a V2X mobile terminal, a V2X mobile communication terminal, a V2X wireless communication device, a V2X wireless terminal, a V2X mobile device, a V2X wireless communication terminal, a V2X user equipment, a V2X UE, a V2X user equipment node / terminal / device, etc.) configured to provide wireless communication according to an embodiment of the present inventive concept. (For example, the V2X wireless device UE 1000 may be provided as described below for Fig.16 As shown in the figure, the V2X wireless device UE may include an antenna 1007 (eg, corresponding to Fig.16 Antenna QQ111) and transceiver circuit 1001 (also referred to as transceiver, for example corresponding to Fig.16 The transceiver circuit 1001 includes a base station (eg, corresponding to a base station of a radio access network) configured to provide a Fig.16 The V2X wireless device UE may also include a processing circuit 1003 (also referred to as a processor) coupled to the transceiver circuit, for example corresponding to the transmitter and receiver of the uplink and downlink radio communication of the network node QQ160, also referred to as the RAN node. Fig.16 A processing circuit QQ120) and a memory circuit 1005 (also referred to as a memory, for example corresponding to a memory) coupled to the processing circuit Fig.16The memory circuit 1005 may store a computer-readable program code that, when executed by the processing circuit 1003, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1003 may be defined to include a memory so that a separate memory circuit is not required. The V2X wireless device UE may also include an interface (e.g., a user interface) coupled to the processing circuit 1003, and / or the V2X wireless device UE may be included in the vehicle.

[0066] As discussed herein, the operations of the V2X wireless device UE may be performed by the processing circuit 1003 and / or the transceiver circuit 1001. For example, the processing circuit 1003 may control the transceiver circuit 1001 to send communications to a radio access network node (also referred to as a base station) through the transceiver circuit 1001 over a radio interface and / or receive communications from a RAN node through the transceiver circuit 1001 over a radio interface. The processing circuit 1003 may also control the transceiver circuit 1001 to send communications directly to another / other V2X wireless device UE over a radio interface through the transceiver circuit 1001 (without passing through a radio access network) and / or receive communications directly from another / other V2X wireless device UE through the transceiver circuit 1001 (without passing through a radio access network). In addition, modules may be stored in the memory circuit 1005, and these modules may provide instructions so that when the instructions of the modules are executed by the processing circuit 1003, the processing circuit 1003 performs corresponding operations (e.g., the operations discussed below for example embodiments involving V2X wireless devices).

[0067] Fig.11 1 is a block diagram illustrating elements of a radio access network (RAN) node 1100 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) of a radio access network (RAN) configured to provide cellular communications according to an embodiment of the present inventive concept. (For example, the RAN node 1100 may be provided as described below for Fig.16 As shown in the figure, the RAN node may include a transceiver circuit 1101 (also referred to as a transceiver, such as corresponding to Fig.16 The transceiver circuit 1101 includes a transmitter and a receiver configured to provide uplink and downlink radio communications with the mobile terminal. The RAN node may include a network interface circuit 1107 (also referred to as a network interface, for example corresponding to Fig.16The network node may also include a processing circuit 1103 (also referred to as a processor, for example corresponding to the processing circuit QQ170) coupled to the transceiver circuit and a memory circuit 1105 (also referred to as a memory, for example corresponding to the memory) coupled to the processing circuit. Fig.16 The memory circuit 1105 may include a computer readable program code that, when executed by the processing circuit 1103, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1103 may be defined to include a memory so that a separate memory circuit is not required.

[0068] As discussed herein, the operations of the RAN node may be performed by the processing circuit 1103, the network interface 1107, and / or the transceiver circuit 1101. For example, the processing circuit 1103 may control the transceiver 1101 to send downlink communications to one or more V2X wireless devices UEs via the transceiver 1101 over the radio interface and / or receive uplink communications from one or more V2X wireless devices UEs via the transceiver 1101 over the radio interface. Similarly, the processing circuit 1103 may control the network interface 1107 to send communications to one or more other network nodes via the network interface 1107 and / or receive communications from one or more other network nodes via the network interface. Thus, the RAN node 1100 may relay communications between the V2X wireless device UE and the VAE server. In addition, modules may be stored in the memory 1105, and these modules may provide instructions so that when the instructions of the modules are executed by the processing circuit 1103, the processing circuit 1103 performs corresponding operations (e.g., the operations discussed below for example embodiments involving RAN nodes).

[0069] According to some other embodiments, the network node may be implemented as a core network CN node without a transceiver. In such an embodiment, the transmission to the wireless device UE may be initiated by the network node such that the transmission to the wireless device is provided by the network node including the transceiver (e.g., by a base station or RAN node). According to an embodiment in which the network node is a RAN node including a transceiver, initiating the transmission may include sending through the transceiver.

[0070] Fig.12is a block diagram illustrating units of a VAE server 1200 according to an embodiment of the inventive concept. As shown, the VAE server may include a network interface circuit 1207 (also referred to as a network interface), which is configured to provide communication with other nodes of a core network and / or a radio access network RAN. The VAE server may also include a processing circuit 1203 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 1205 (also referred to as a memory) coupled to the processing circuit. The memory circuit 1205 may include a computer-readable program code that, when executed by the processing circuit 1203, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1203 may be defined to include a memory so that a separate memory circuit is not required.

[0071] As discussed herein, the operations of the VAE server may be performed by the processing circuit 1203 and / or the network interface circuit 1207. For example, the processing circuit 1203 may control the network interface circuit 1207 to send communications to one or more other network nodes and / or V2X wireless devices UEs through the network interface circuit 1207 and / or receive communications from one or more other network nodes and / or V2X wireless devices UEs through the network interface circuit. In addition, modules may be stored in the memory 1205, and these modules may provide instructions so that when the instructions of the modules are executed by the processing circuit 1203, the processing circuit 1203 performs corresponding operations (e.g., the operations discussed below for example embodiments involving the VAE server).

[0072] TS 23.286 (also referred to as reference [3]) describes the procedures for a VAE client of a V2X wireless device UE to register and receive V2X messages and subscribe to geolocation. However, VAE server discovery (i.e., determining the correct VAE server for serving the VAE client) may not be specified.

[0073] When a V2X wireless device UE moves to a new geographic area, the best VAE server for serving the V2X wireless device UE may change depending on multiple factors (e.g., location and V2X messages supported by the VAE server). Therefore, a server discovery process may be useful / necessary to determine the best VAE server for the V2X wireless device UE.

[0074] Depending on the deployment, there may be multiple VAE servers, each of which may provide Intelligent Transportation System ITS messages to a specific geographic region or area (e.g., corresponding to a tile or geo-fence). When a V2X wireless device UE enters a new geographic area (e.g., when it crosses a border), the V2X wireless device UE may have to discover a new VAE server responsible for transmitting ITS / V2X messages for that target geographic area. Note that ITS messages may be region-specific, and therefore when moving into a new geographic area, the V2X wireless device UE may need to start receiving messages from a new VAE server.

[0075] In current V2X work for application layer support, in TR 23.795 (reference [1]) and TS 23.286 (reference [3]), the V2X wireless device UE updates its location to the VAE server when moving to a new area, but this assumes that the V2X wireless device UE continues to receive messages from the same VAE server. Therefore, VAE server discovery can be ignored.

[0076] Annex D of 3GPP TS 23.285 v15.1.0 (June 2018) (reference [2]) describes a network-based method for changing the V2X application server and Figure 7 Figure D.1-1 of Appendix D is provided in [2], which shows the V2X message distribution server deployment options. As discussed in Appendix D of reference [2]:

[0077] In the case of non-session based V2X services (i.e. road status notification), a single V2X message may need to be delivered to multiple locally related V2X application servers. In order to provide network support to distribute these V2X messages to multiple V2X application servers, a possible deployment option includes a V2X message distribution server behind the L / PGW as shown in Figure D.1-1. It is configured to distinguish whether a V2X message needs to be delivered to multiple V2X application servers and send these messages accordingly.

[0078] The UE discovers the V2X messages and sends them to the distribution servers deployed by these networks in the same way as to the V2X application servers. From the UE's perspective, it is communicating with the V2X application servers and does not know whether any of these V2X messages are also being distributed to other servers.

[0079] NOTE: The V2X Message Distribution Server is used for illustration purposes only and is not further described in any 3GPP specification.

[0080] Note the following differences of Appendix D of reference [2] with respect to some embodiments of the inventive concept:

[0081] 1) Annex D addresses the issue when multiple V2X application servers belong to the same region instead of different regions. When the application servers belong to different regions, the publication group option of the ITS message (which can be based on geographical regions, considering both options) may be useful / needed. When the V2X application servers belong to the same region, this issue may not arise because all servers serve the same region. In principle, one of the servers can be selected using network performance, load-based or other methods.

[0082] 2) In addition, for the method in Appendix D for solving problems related to V2X application servers in different regions, the third-party V2X application server may need to provide the V2X message distribution server with release group options and information, which may be undesirable and / or infeasible.

[0083] 3) The V2X message distribution server is not part of the SA2 (TS 23.285) or SA6 (TR 23.795 and TS 23.286) functional model and it appears to act as a proxy (in the case of MQTT / ITS message distribution methods). Additional information about UEs and ITS services may be provided.

[0084] 4) TS 23.285 Annex D states that this is an open problem, but only provides a high-level diagram without any approach: "For illustrative purposes... not further described in any 3GPP specification"

[0085] 5) According to some embodiments of the inventive concept, a V2X application server may be provided as an alternative to the edge cloud approach or a V2X application server may be provided to reduce / avoid the edge cloud approach. "Edge server" is actually a deployment term. In principle, it may more accurately refer to "application server deployed at an edge site". 3GPP does not define the detailed functions of an application server or edge server.

[0086] 6) By reducing redirection, the impact on the V2X wireless device UE can be reduced. When the VAE server forwards the V2X wireless device UE message to the new VAE server, the VAE server discovery can be transparent to the V2X wireless device UE. When the V2X wireless device UE moves to a different area, the method in Appendix D may also have an impact on the V2X wireless device UE.

[0087] According to some embodiments of the present inventive concept, a process for VAE server discovery in ITS / V2X message distribution may be provided. Such a process can allow a V2X wireless device UE to receive ITS / V2X messages from a new VAE server when moving to a new geographical area.

[0088] Figure 3 The relationship between different V2X / ITS message groups and geographic locations is shown.

[0089] The V2X wireless device UE (VAE client) is registered to receive V2X / ITS messages (e.g., DENM, IVI, MAP, and CAM messages). The VAE client (V2X wireless device UE) is in geographic area 1 (A01) and subscribes to VAE server 01. The VAE client communicates with the VAE server via the V1 reference point, the VAE server communicates with the V2X application server via the Vs reference point, and the VAE server can communicate via the VAE-E reference point (also known as the VAE-x reference point).

[0090] According to some embodiments disclosed herein, two options are provided for publishing V2X / ITS messages at a VAE server. In Option 1, the VAE server publishes a message group associated only with its own geographic area. In this case, it communicates with a single V2X application server (solid line Vs). In Option 2, the VAE server publishes a message group associated with multiple geographic areas. In this case, it communicates with multiple V2X application servers (solid and dashed lines Vs).

[0091] Figure 3 VAE client (V2X wireless device UE) and server publication and association with different geographical areas are shown.

[0092] When the VAE client (V2X wireless device UE) moves to a new geographical area 02 (A02), it continues to receive messages from the VAE server 01, without taking into account the VAE discovery.

[0093] According to some embodiments of the inventive concept, when a VAE client (V2X wireless device UE) moves from A01 to A02, it sends a location update to VAE server 1. This triggers a VAE server discovery process, during which the VAE client (V2X wireless device UE) is redirected to VAE server 02. In release option 1, transitioning to VAE server 02 may be useful / necessary because VAE server 01 may no longer be able to provide messages to A02. In release option 2, transitioning to VAE server 02 may be beneficial if the new VAE server provides better connectivity (e.g., lower latency) to the VAE client (V2X wireless device UE).

[0094] Figure 4 A VAE client (V2X wireless device UE) is shown being redirected to the VAE server 02 when moving to area A02.

[0095] According to some embodiments of the present inventive concept, when moving to a new geographic area, the V2X wireless device UE may be allowed to receive ITS / V2X messages. These messages can be provided by a new VAE server that may be responsible for providing specific ITS messages for that area (e.g., when the V2X wireless device UE crosses a border to a new country) or from a VAE server that provides better connectivity.

[0096] According to some embodiments of the inventive concept, special features in 3GPP RAN (eg, Selective IP Traffic Offload SIPTO) may not be required.

[0097] Figure 5A VAE server discovery when moving to a new geographic region is illustrated according to some embodiments of the present inventive concepts.

[0098] According to some embodiments of the present inventive concept, when moving to a new geographical area, a VAE client (V2X wireless device UE) subscription procedure (location update) may be used to update the VAE client (V2X wireless device UE) on the availability of new VAE servers. Figure 5A Operations according to some embodiments are illustrated in FIG. 1 and discussed below:

[0099] 501) In response to the VAE client (V2X wireless device UE) moving to the new geographic area 02 (from the geographic area 01), the VAE client (V2X wireless device UE) provides a geographic area update (also referred to as a location update message) to the VAE server. Although the update of operation 501 is shown as a subscription request, the message can generally be provided as a location update message including information identifying the new geographic area 02 (which can be included in the subscription request message).

[0100] 502) The VAE server stores the new geographic area information 02 associated with the VAE client.

[0101] 503) The VAE server interacts with other VAE servers via the VAE-E interface to identify / discover the appropriate / best VAE server for the VAE client (V2X wireless device UE). The interaction via the VAE-E interface may include providing new geographic area location information to other VAE servers using a server discovery request message, as shown below for Figure 5B discussed.

[0102] Upon receiving the subscription request (location update message), the VAE server checks whether it can continue to provide messages for geographic area 02.

[0103] In case of publishing option 1, VAE server 01 may not be able to provide new information for geographic area 02, and therefore the VAE server should trigger the VAE discovery process.

[0104] In case of release option 2, the VAE server can still search for a new VAE server for a geographic area 02 that is closer to the VAE client (V2X wireless device UE). There are at least two possibilities to enable this search. One possibility is that each VAE server knows its own geographic location. The second possibility is that the V2X application server provides a preferred VAE server for each geographic area.

[0105] 504) The VAE server sends a redirect message to redirect the VAE client (V2X wireless device UE) to a new VAE server in area 02. The address of the VAE server 02 may be provided in a confirmation message in response to the subscription message (location update message) of operation 501.

[0106] 505) The VAE client (V2X wireless device UE) may establish a connection with the new VAE server based on the address of operation 504. If necessary, the VAE client (V2X wireless device UE) may register to the new ITS / V2X message, for example, by sending a registration message to the new VAE server.

[0107] The following provides information about Figure 5A Notes on the operation:

[0108] a. The server discovery method according to some embodiments of the inventive concept may also be used for initial registration, i.e., when a VAE client (V2X wireless device UE) subscribes to a geographical area for the first time.

[0109] b. The VAE server (or an associated location management server or part of a VAE server) may trigger the VAE server discovery process.

[0110] c. There may be multiple VAE servers in one geographical area. In this case, a central VAE server may be considered for coordination between multiple VAE servers.

[0111] d. VAE server 01 may send a server discovery request to a subset of VAE servers or a central VAE server responsible for coordination among multiple VAE servers.

[0112] e. The operations described can be applied to any V2X message (e.g. ETSI ITS, SAE).

[0113] f. The VAE server responsible for message distribution can be a message broker (such as an MQTT or AMQP server). The corresponding publishing options and server discovery process can also be applied.

[0114] The following is for Figure 5B Discuss in more detail Figure 5A Operation 503 Server Found.

[0115] exist Figure 5B , operations for identifying / determining the appropriate / best VAE server to serve a VAE client (V2X wireless device UE) at initial VAE client registration or when moving to a new geographic area are shown. Such operations may use the VAE-E reference point for interaction between VAE servers (e.g., for message transmission).

[0116] exist Figure 5B In operation 511, in response to receiving the location update message of operation 501, the VAE server may send a server discovery request (including an identification from Figure 5A information of the new geographical area 02 of the message 501).

[0117] Figure 8 The table describes the information flow of issuing a server discovery request from one VAE server to other VAE servers. For example, the server discovery request message may include a GEO ID as a geographic region identifier (e.g., a subscription URI, a block identifier, a geo-fence block identifier, etc.).

[0118] exist Figure 5B At operation 512, another VAE server may respond to the server discovery request message with a server discovery response message. For example, the server discovery response message may include an identifier (eg, FQDN) of another VAE server that sent the server discovery response message.

[0119] Fig. 9 The table describes the information flow of a VAE server responding to a server discovery request message from another VAE server. For example, the server discovery response message may include an identifier of the VAE server (sending the server discovery response message), such as a fully qualified domain name FQDN. Figure 5B Some examples:

[0120] The VAE server 01 can communicate using the VAE-E interface and can be aware of the availability of other VAE servers 02 ... x.

[0121] The VAE server 01 may receive a geolocation update (Location Update message) with a GEO ID from a VAE client, as described in subclause 8.2 of reference [3].

[0122] Discussed below Figure 5B The VAE server is found:

[0123] 511. VAE server 01 sends a server discovery request message to other VAE servers 02…x.

[0124] 512. The VAE server 02 . . . x responsible for the new geographic region (corresponding to the GEO ID of the Server Discovery Request message) responds by sending a Server Discovery Response message to the VAE server 01 .

[0125] The following is for Fig. 6A and 6B Discuss client-based approaches.

[0126] According to some embodiments, a V2X wireless device UE (ie, a VAE client) may be allowed to switch to another VAE server when moving to a new geographical area. For example, the client (V2X wireless device UE) may analyze whether it can continue to receive current V2X services and / or messages from the original VAE server and decide whether it should switch to another VAE server.

[0127] The following is for Fig. 6A Discussion of initial connection establishment:

[0128] 601) The VAE client (V2X wireless device UE) may obtain VAE server information from the configuration management server, or may be pre-configured with the corresponding addresses of VAE servers by geographical area.

[0129] 602) The VAE client (V2X wireless device UE) may obtain V2X service and message information from the VAE server 01. This may include information about available services and corresponding VAE servers by geographic area.

[0130] 603) A VAE client (V2X wireless device UE) may subscribe to receive V2X messages from a VAE server 01, which is responsible for delivering V2X services and messages of interest to V2X wireless devices UE in its initial / current geographical area.

[0131] Note that the VAE server 01 may initially provide V2X services and message information, and the VAE servers that propagate the V2X messages may be the same or different.

[0132] Fig. 6A Operations for an initial V2X wireless device UE connection to a VAE server 01 provided for a geographic area 01 are shown.

[0133] Figure 6BThe operations / messages when the V2X wireless device UE client moves to a new geographical area 02 are shown:

[0134] 621) The V2X wireless device UE client detects that it has moved to a new geographical area 02.

[0135] 622) The V2X wireless device UE client checks the V2X service information and VAE server information by geographic area 02, and decides whether it should continue to receive messages from VAE server 01 or switch to VAE server 02.

[0136] 623) The V2X wireless device UE client cancels the subscription to receive V2X messages from the VAE server 01.

[0137] 624) The V2X wireless device UE client subscribes to receive V2X messages from the VAE server 02.

[0138] Comparison between server-based and client-based approaches:

[0139] A VAE server-based approach may provide higher granularity, as information about the V2X application-specific server that publishes group information may not be fully available at the client.

[0140] The VAE server-based approach can reduce / avoid unnecessary switching to new VAE servers when the old VAE servers can still deliver services.

[0141] Client-based approaches may depend on the client implementation. The client (V2X wireless device UE) may typically terminate the connection with the server when it can no longer receive service (TCP timeout). Server-based approaches may be more proactive.

[0142] In another implementation, more than one V2X AS and / or VAE may serve a particular geographical area. This may be suitable, for example, to meet low latency requirements by placing servers closer to the radio cells (edge ​​cloud), while servers further away serve less latency-critical applications (e.g. vehicle signage is not really latency-critical, but emergency brake warnings are). In this case, the V2X radio device UE communicates with multiple servers, applying the previously described process for each of them.

[0143] According to some embodiments of the inventive concept, a method for server discovery may be provided that enables a VAE client (V2X wireless device UE) to connect to a (new) VAE server when initially starting the VAE client or when moving to a new geographic area (e.g., across a border). Such a method may provide interaction between VAE servers via a VAE-E interface, and / or may allow discovery of appropriate VAE servers to serve the VAE client (V2X wireless device UE) when moving to a new geographic area. According to some embodiments, an application server discovery process may be provided in an ITS message distribution.

[0144] According to some embodiments of the present inventive concept, reference will now be made to Fig.13A -B flowchart to discuss the VAE server 1200 (using Fig.12 The structure of the implementation, such as the operation of the VAE server 01). For example, the module can be stored in Fig.12 The modules may be stored in the memory 1205, and these modules may provide instructions so that when the instructions of the modules are executed by the corresponding VAE server processing circuit 1203, the processing circuit 1203 performs the corresponding operations of the flowchart.

[0145] At block 1300, the processing circuit 1203 may receive V2X message information by geographic region from a V2X application specific server (e.g., as described above with respect to Figure 5A (as discussed in operation 500 of FIG. 1 ).

[0146] According to some embodiments, at block 1300, a VAE server (e.g., VAE server 01) may receive information about available V2X messages for a geographic area from a V2X application-specific server. For example, the VAE server may obtain information about available V2X services (e.g., identified by a provider service identifier PSID of an intelligent transportation system application object identifier ITS-AID) and their corresponding geographic area associations from a V2X application.

[0147] At block 1301, the processing circuit 1203 may receive location information from a VAE client of a V2X wireless device (e.g., as described above with respect to Figure 5A ), wherein the location information indicates the location of the V2X wireless device.

[0148] According to some embodiments, at block 1301, the VAE server may receive location information from the VAE client as a geolocation update with a geographic region identifier GEO ID. For example, the VAE server may receive a geolocation update with a GEO ID from the VAE client for a geographic region outside of its coverage.

[0149] In response to receiving the location information and in response to the V2X message information by geographic area, the processing circuit 1203 may identify a second VAE server (eg, VAE server 02) based on the location information at block 1303 (eg, as described above for Figure 5A (as discussed in operation 503 of FIG. 1 ).

[0150] At block 1304, the processing circuit 1203 may send the address of the second VAE server to the VAE client of the wireless device (eg, as described above for Figure 5A (as discussed in operation 504 of FIG. 1 ).

[0151] According to some embodiments of the inventive concept, the operation of block 1303 may be as follows: Fig. 13B For example, the processing circuit 1203 may send a server discovery request (e.g., as described above for the VAE server 02 . . . x) to multiple other VAE servers (e.g., VAE servers 02 . . . x) including the second VAE server at block 511 through the network interface 1207. Figure 5B ), wherein the server discovery request includes location information. At block 1312, processing circuit 1203 may receive a server discovery response (via network interface 1207) from a second VAE server (e.g., as described above with respect to Figure 5B ), wherein the server discovery response includes an address of the second VAE server.

[0152] According to some embodiments, at block 1311, the server discovery request may be referred to as a server relocation request or a service continuity request, and the server discovery request may be sent over a VAE-E reference point. For example, a first VAE server (e.g., VAE server 01) may send a service continuity request to all VAE servers to which it is connected or a subset of VAE servers (e.g., within the same PLMN). According to some embodiments, at block 1312, the server discovery response may be referred to as a server relocation response or a service continuity response.

[0153] According to some embodiments of the present inventive concept, VAE capabilities may enable a V2X wireless device (also referred to as a V2X UE) with a VAE client to continue receiving V2X services from the same or a different VAE server when changing geographical areas.

[0154] Some embodiments of VAE servers and related methods, from Fig.13A - Various operations of the flowchart of B may be optional. For example, with respect to the method of Example Embodiment 1 (described below), Fig.13A The operations of blocks 1311 and 1312 of -B may be optional.

[0155] According to some embodiments of the present inventive concept, reference will now be made to Fig.14 The flowchart of the first VAE server 1200 (using Fig.12 The structure of the implementation, such as the operation of the VAE server 02). For example, the module can be stored in Fig.12 The modules may be stored in the memory 1205, and these modules may provide instructions so that when the instructions of the modules are executed by the corresponding VAE server processing circuit 1203, the processing circuit 1203 performs the corresponding operations of the flowchart.

[0156] At block 1411, the processing circuit 1203 may receive a server discovery request (via the network interface 1207) from a second VAE server (eg, VAE server 01) (eg, as described above with respect to Figure 5B In addition, the server discovery request may include location information of the wireless device.

[0157] According to some embodiments, at block 1411 , the server discovery request may be referred to as a server relocation request or a service continuity request, and the server discovery request may be received over a VAE-E reference point.

[0158] At block 1411a , the processing circuit 1203 may compare the location information with a service area of ​​the first VAE server in response to receiving the server discovery request.

[0159] At block 1412, the processing circuit 1203 may send a server discovery response (e.g., as described above for the server discovery request) to the second VAE server in response to the server discovery request. Figure 5B ), wherein the server discovery response includes the address of the first VAE server. For example, the server discovery response may be sent in response to the location information of blocks 1411 and 1411a matching the service area of ​​the first VAE server.

[0160] According to some embodiments, at block 1312, the server discovery response may be referred to as a server relocation response or a service continuity response.

[0161] Some embodiments of VAE servers and related methods, from Fig.14 Various operations of the flowchart may be optional. For example, with respect to the method of example embodiment 13 (described below), Fig.14 The operation of block 1411a may be optional.

[0162] According to some embodiments of the present inventive concept, reference will now be made to Fig.15 The flowchart of wireless device 1000 (using Fig.10For example, the module can be stored in Fig.10 The modules may be stored in the memory 1005 of the wireless device, and these modules may provide instructions so that when the instructions of the modules are executed by the corresponding wireless device processing circuit 1003, the processing circuit 1003 performs the corresponding operations of the flowchart.

[0163] At block 1501, processing circuit 1003 may provide VAE server information for a plurality of VAE servers (e.g., as described above with respect to Fig. 6A The VAE server information may include a corresponding address of each of the plurality of VAE servers, a corresponding geographic region associated with the VAE server, and / or corresponding service / message information related to the V2X service available from the VAE server.

[0164] At block 1503, the processing circuit 1003 may subscribe to receive V2X messages (eg, as described above for VAE server 01) from a first VAE server (eg, VAE server 01) among the plurality of VAE servers. Fig. 6A (as discussed in operation 603 of FIG. 1 ).

[0165] At block 1505 , the processing circuit 1003 may determine whether the V2X wireless device UE has moved.

[0166] In response to detecting movement from a first geographic region associated with a first VAE server to a second geographic region at block 1505, the processing circuit may identify (622, 1507) a second VAE server (e.g., VAE server 02) associated with the second geographic region from among the plurality of VAE servers based on the VAE server information at block 1507 (e.g., as described above with respect to Figure 6B (as discussed in operations 621 / 622).

[0167] In response to detecting the movement and / or in response to identifying the second VAE server, the processing circuit 1003 may unsubscribe from the first VAE server at block 1509 (e.g., as described above with respect to Figure 6B (as discussed in operation 623 of FIG. 1 ).

[0168] In response to identifying the second VAE server, the processing circuit 1003 may subscribe to receive V2X messages from the second VAE server at block 1511 (e.g., as described above with respect to Figure 6B (as discussed in operation 624 of FIG. 1 ).

[0169] Some embodiments of wireless devices and related methods are provided from Fig.15 Various operations of the flowcharts may be optional. For example, with respect to the method of example embodiment 20 (described below), Fig.15The operation of block 1509 may be optional.

[0170] The process for VAE server relocation is discussed below.

[0171] TS 23.286 describes the procedures for registering to receive V2X messages and subscribing to geolocation by a VAE client, and the reasons for the changes are discussed below.

[0172] When a V2X UE registers to receive V2X messages or moves to a new geographic area, the best VAE server for serving the V2X UE may change based on multiple factors, such as the location and V2X messages supported by the VAE server. Accordingly, a process for determining the best VAE server for a V2X UE is disclosed.

[0173] The current TS (Technical Specification) describes multiple deployment scenarios. In multiple distributed deployment scenarios, VAE servers communicate via the VAE-E interface. Currently, the VAE-E interface is not specified.

[0174] The VAE servers communicate to determine the best serving VAE server for the V2X UE based on the V2X UE location and the VAE capability to continue serving the V2X UE when moving to a new geographic area. For example, when different VAE servers are responsible for different geographic areas, the current VAE server may not be able to continue serving the V2X UE. In this case, VAE server relocation may be useful.

[0175] Fig.25 Elements of the V2X service provider domain and the PLMN operator domain are shown.

[0176] The following changes to 3GPP TS 23.286 v1.0 are proposed, wherein server relocation, including VAE server relocation, is discussed below according to some embodiments.

[0177] A process for determining the best VAE server for serving a VAE client when moving to a new geographic region is discussed. The process utilizes VAE-E reference points for interaction between VAE servers.

[0178] against Fig.26 (Server Relocation Request) and Fig. 27 (Server Relocation Response) discusses information flow. Fig.26 The table shows the information flow of server relocation requests from one VAE server to other VAE servers. Fig. 27 The table shows the information flow of a server relocation response from a VAE server in response to a server relocation request from another VAE server.

[0179] The following discusses the process for VAE server relocation, including prerequisites and the VAE server relocation process. The prerequisites may include:

[0180] VAE servers are using the VAE-E interface to communicate and are aware of the availability of other VAE servers.

[0181] The VAE server has received information about available V2X messages for the geographical area from the V2X application specific server.

[0182] The VAE server has received a geolocation update with a GEO ID from the VAE client. Fig.28 The process for VAE server relocation is shown in Fig.28 At operation / message 1, the VAE server sends a server relocation request to other VAE servers via the VAE-E reference point. Fig.28 At operation / message 2 of , the VAE server responsible for the new geographic area with the GEO ID provides a server relocation response to the VAE server over the VAE-E reference point.

[0183] The VAE server receives information about available V2X services from the V2X application specific server and these services may be geographical area specific. The VAE server uses / needs such information to transmit V2X messages to the V2X UE.

[0184] The V2X UE is able to continue receiving V2X services when changing geographical areas. This may be from the same or a different VAE server. The VAE capability supports service continuity.

[0185] According to some embodiments, various aspects of the V2X application layer functional architecture are discussed below. The VAE client and the VAE server may support one or more V2X applications. The VAE capability may be provided to the V2X application as an API. The VAE capability may enable the V2X UE to obtain the address of an available V2X application server associated with the provided geographic area information. The VAE capability may enable the V2X UE to obtain information about available V2X services (e.g., identified by a PSID or ITS-AID). The VAE server may obtain information about available V2X services (e.g., identified by a PSID or ITS-AID) and their corresponding geographic area associations from the V2X application.

[0186] According to some embodiments, various aspects of V2X (e.g., ETSIITS, SAE) message distribution are discussed below. A VAE server may provide a mechanism to distribute V2X messages to all registered receivers in a target geographic area. A VAE server may enable transmission of multiple V2X messages over the same connection. A VAE client may have the ability to register to V2X messages in one or more geographic areas. A VAE server may have the ability to forward V2X messages only to authorized V2X UEs in a target geographic area. A VAE server may provide a mechanism for priority support of different V2X messages (e.g., safety messages). VAE capabilities may enable a V2X UE to continue to receive V2X services from the same or different VAE servers when changing geographic areas.

[0187] Example embodiments are discussed below.

[0188] 1. A method for operating a first vehicle-to-everything V2X application enabler (VAE) server (01), the method comprising: receiving (500, 1300) V2X message information by geographic area from a V2X application specific server; receiving (501, 1301) location information from a VAE client of a wireless device, wherein the location information indicates a location of the wireless device; in response to receiving the location information and in response to the V2X message information by geographic area, identifying (503, 1303) a second VAE server (02) based on the location information; and sending (504, 1304) an address of the second VAE server (02) to the VAE client of the wireless device.

[0189] 2. A method according to embodiment 1, wherein identifying the second VAE server includes: sending (511, 1311) a server discovery request to multiple other VAE servers (02...x) including the second VAE server, wherein the server discovery request includes location information; and receiving (512, 1312) a server discovery response from the second VAE server, wherein the server discovery response includes the address of the second VAE server.

[0190] 3. The method according to Example 2, wherein sending a server discovery request comprises sending a server discovery request to a second VAE server via a VAE-E interface, and / or wherein receiving a server discovery response comprises receiving a server discovery response from a second VAE server via a VAE-E interface.

[0191] 4. The method according to any one of embodiments 1-3, wherein receiving the location information comprises: receiving a location update message from a VAE client of the wireless device, wherein the location update message comprises the location information.

[0192] 5. The method of any one of embodiments 1-3, wherein receiving the location information comprises receiving an initial registration message from a VAE client of the wireless device, wherein the initial registration message comprises the location information.

[0193] 6. The method according to any one of embodiments 1-5, wherein sending the address comprises: sending a redirection message to a VAE client of the wireless device, wherein the redirection message comprises an address of a second VAE server.

[0194] 7. A method according to any one of embodiments 1-6, wherein the location information includes a geographic area identifier.

[0195] 8. The method of embodiment 7, wherein the geographic area identifier comprises at least one of a subscription uniform resource identifier, a block identifier, and / or a geo-fence block identifier.

[0196] 9. The method of any one of embodiments 1-8, wherein the address of the second VAE server comprises a fully qualified domain name of the second VAE server.

[0197] 10. The method according to any one of embodiments 1-9, wherein the first VAE server is a message agent responsible for message distribution.

[0198] 11. The method according to any one of embodiments 1-10, wherein the V2X message information by geographic area is received by the VAE server from the V2X application server through the Vs interface.

[0199] 12. The method of any one of embodiments 1-11, wherein identifying the second VAE server is based on location information and based on a publishing option of the V2X message by geographic area.

[0200] 13. A method for operating a first vehicle-to-everything V2X application enabler VAE server (02), the method comprising: receiving (511, 1411) a server discovery request from a second VAE server (01), wherein the server discovery request includes location information of a wireless device; and in response to the server discovery request, sending (512, 1412) a server discovery response to the second VAE server, wherein the server discovery response includes an address of the first VAE server.

[0201] 14. The method according to Example 13 further includes: in response to receiving a server discovery request, comparing the location information with the service area of ​​the first VAE server (02) (1411a); wherein sending a server discovery response includes: in response to the location information matching the service area of ​​the first VAE server (02), sending a server discovery response.

[0202] 15. A method according to any one of Examples 13-14, wherein receiving a server discovery request includes: receiving a server discovery request from a second VAE server via a VAE-E interface, and / or wherein sending a server discovery response includes: sending a server discovery response to the second VAE server via a VAE-E interface.

[0203] 16. A method according to any one of embodiments 13-15, wherein the location information includes a geographic area identifier.

[0204] 17. The method of embodiment 16, wherein the geographic region identifier comprises at least one of a subscription uniform resource identifier, a block identifier, and / or a geo-fence block identifier.

[0205] 18. The method according to any one of embodiments 13-17, wherein the address of the first VAE server (02) includes a fully qualified domain name of the first VAE server.

[0206] 19. The method according to any one of embodiments 13-18, wherein the second VAE server is a message agent responsible for message distribution.

[0207] 20. A method for operating a vehicle-to-everything (V2X) wireless device, the method comprising: providing (601 / 602, 1501) VAE server information for a plurality of VAE servers, wherein the VAE server information comprises a corresponding address of each of the plurality of VAE servers, a corresponding geographic area associated with the VAE server, and / or corresponding service / message information related to a V2X service available from the VAE server; subscribing (603, 1503) to receive V2X messages from a first VAE server (01) of the plurality of VAE servers; in response to detecting movement from a first geographic area associated with the first VAE server to a second geographic area, identifying (622, 1507) a second VAE server (02) of the plurality of VAE servers associated with the second geographic area based on the VAE server information; and in response to identifying the second VAE server, subscribing (624, 1511) to receive V2X messages from the second VAE server.

[0208] 21. The method of embodiment 20 further comprising: in response to detecting movement and / or in response to identifying a second VAE server, unsubscribing from the first VAE server (623, 1509).

[0209] 22. A method according to any one of embodiments 20-21, wherein providing VAE server information includes: obtaining a corresponding address of each of the multiple VAE servers and / or a corresponding geographical area associated with each of the multiple VAE servers from a configuration management server.

[0210] 23. A method according to any one of embodiments 20-21, wherein providing VAE server information includes: pre-configuring a corresponding address of each of the multiple VAE servers and / or a corresponding geographical area associated with each of the multiple VAE servers.

[0211] 24. A method according to any one of embodiments 20-23, wherein providing VAE server information includes: obtaining corresponding service / message information related to the V2X service available from each of the multiple VAE servers from a VAE server among the multiple VAE servers.

[0212] 25. A VAE server (1200) configured to operate with a communication network, the VAE server comprising: a processing circuit (1203); and a memory (1205) coupled to the processing circuit, wherein the memory comprises instructions that, when executed by the processing circuit, cause the VAE server to perform operations according to any one of embodiments 1-19.

[0213] 26. A VAE server (1200) configured to operate with a communication network, wherein the VAE server is suitable for performing according to any one of embodiments 1-19.

[0214] 27. A computer program comprising program code to be executed by a processing circuit (1203) of a VAE server (1200), the VAE server (1200) being configured to operate with a communication network, whereby execution of the program code causes the VAE server (1200) to perform operations according to any one of embodiments 1-19.

[0215] 28. A computer program product comprising a non-transitory storage medium storing program code to be executed by a processing circuit (1203) of a VAE server (1200), the VAE server (1200) being configured to operate in a communication network, whereby execution of the program code causes the VAE server (1200) to perform operations according to any one of embodiments 1-19.

[0216] 29. A V2X wireless device (1000) configured to operate in a communication network, the V2X wireless device comprising: a processing circuit (1003); and a memory (1005) coupled to the processing circuit, wherein the memory comprises instructions that, when executed by the processing circuit, cause the V2X wireless device to perform operations according to any one of embodiments 20-24.

[0217] 30. A V2X wireless device (1000) configured to operate in a communication network, wherein the V2X wireless device is adapted to perform according to any one of embodiments 20-24.

[0218] 31. A computer program comprising program code to be executed by a processing circuit (1003) of a V2X wireless device (1000), the V2X wireless device (1000) being configured to operate in a communication network, whereby execution of the program code causes the V2X wireless device (1000) to perform operations according to any one of embodiments 20-24.

[0219] 32. A computer program product comprising a non-transitory storage medium including program code to be executed by a processing circuit (1003) of a V2X wireless device (1000), the V2X wireless device (1000) being configured to operate in a communication network, whereby execution of the program code causes the V2X wireless device (1000) to perform operations according to any one of embodiments 20-24.

[0220] A description of the various abbreviations / acronyms used in this disclosure is provided below.

[0221] Abbreviation

[0222] V2X Vehicle to Everything

[0223] V2X AS V2X Application Server

[0224] VAE V2X Application Enabler

[0225] V2X UE User Equipment

[0226] ITS Intelligent Transportation System

[0227] FQDN Fully Qualified Domain Name

[0228] MQTT message queue telemetry transport

[0229] AMQP Advanced Message Queuing Protocol

[0230] DENM decentralized environment notification message

[0231] IVI Infrastructure to Vehicle Information

[0232] CAM Collaborative Awareness Message

[0233] SAE Society of Automotive Engineers

[0234] ETSI European Telecommunications Standards Institute

[0235] URI Uniform Resource Identifier

[0236] References are identified below.

[0237] Reference [1]: 3GPP TR 23.795 V16.1.0 (December 2018), Study on application layer support for V2X services

[0238] Reference [2]: 3GPP TS 23.285 V16.0.0 (March 2019), Architecture Enhancements for V2X Services

[0239] Reference [3]: 3GPP TS 23.286 V1.0.0 (March 2019), Application layer support for V2X services; functional architecture and information flow

[0240] Additional instructions are provided below.

[0241] Generally, unless different meanings are clearly given and / or different meanings are implied in the context of using the term, all terms used in this article will be interpreted according to their common meanings in the relevant technical field. Unless clearly stated, all references to one / an / the element, device, assembly, part, step, etc. should be publicly interpreted as referring to at least one instance of the element, device, assembly, part, step, etc. Unless a step is explicitly described as being after or before another step and / or a step must be after or before another step implicitly, 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. Similarly, 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.

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

[0243] Fig.16 A wireless network in accordance with some embodiments is shown.

[0244] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks such as Fig.16 For simplicity, Fig.16 The wireless network of FIG. 1 depicts only the network QQ106, the network nodes QQ160 and QQ160b, and the WDQQ110, QQ110b, and QQ110c (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). In the components shown, the network node QQ160 and the wireless device (WD) QQ110 are depicted with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.

[0245] A wireless network may 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 may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), 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.

[0246] The network QQ106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0247] The network node QQ160 and WD QQ110 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the 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).

[0248] 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 a wireless device and / or perform other functions (e.g., management) in a 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 station (or in other words, their transmit power levels), and then they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can 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) that is 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 certain service to a wireless device that has accessed a wireless network.

[0249] exist Fig.16 In the embodiment, the network node QQ160 includes a processing circuit QQ170, a device readable medium QQ180, an interface QQ190, an auxiliary device QQ184, a power supply QQ186, a power supply circuit QQ187, and an antenna QQ162. Fig.16The network node QQ160 shown in the example wireless network may represent a device including a combination of the hardware components shown, but other embodiments may include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node QQ160 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that make up a single shown component (for example, the device readable medium QQ180 may include multiple separate hard drives and multiple RAM modules).

[0250] Similarly, the network node QQ160 may include multiple physically separated 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 the network node QQ160 includes multiple separate components (e.g., a BTS and a BSC component), one or more separate components may be shared between 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 as a single separate network node. In some embodiments, the network node QQ160 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device-readable media QQ180 for different RATs), while some components may be reused (e.g., the same antenna QQ162 may be shared by RATs). The network node QQ160 may also include multiple groups of various example components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, Wi-Fi, or Bluetooth wireless technologies) integrated into the network node QQ160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node QQ160.

[0251] The processing circuit QQ170 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. Such operations performed by the processing circuit QQ170 may include: processing information obtained by the processing circuit QQ170, 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 a determination as a result of the processing.

[0252] The processing circuit QQ170 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 a combination of hardware, software, and / or encoded logic operable to provide network node QQ160 functionality alone or in combination with other network node QQ160 components (e.g., device readable medium QQ180). For example, the processing circuit QQ170 may execute instructions stored in the device readable medium QQ180 or in a memory within the processing circuit QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit QQ170 may include a system on a chip (SOC).

[0253] In some embodiments, the processing circuit QQ170 may include one or more of a radio frequency (RF) transceiver circuit QQ172 and a baseband processing circuit QQ174. In some embodiments, the radio frequency (RF) transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, some or all of the RF transceiver circuit QQ172 and the baseband processing circuit QQ174 may be on the same chip or chipset, board, or unit.

[0254] In a particular embodiment, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuit QQ170 executing instructions stored on a device-readable medium QQ180 or a memory within processing circuit QQ170. In an alternative embodiment, some or all of the functions may be provided by processing circuit QQ170 without the need to execute instructions stored on a separate or separate device-readable medium, such as in a hardwired manner. In any of these embodiments, whether or not instructions stored on a device-readable storage medium are executed, processing circuit QQ170 can be configured to perform the described functions. The benefits provided by such functions are not limited to processing circuit QQ170 or other components of network node QQ160, but are enjoyed by network node QQ160 as a whole and / or generally by end users and wireless networks.

[0255] 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., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or 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, codes, 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 calculations 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 to be integrated.

[0256] 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 to send and receive data to network QQ106, for example, via wired connection. Interface QQ190 also includes radio front-end circuit QQ192 that can be coupled to antenna QQ162 or as a part of antenna QQ162 in a specific embodiment. Radio front-end circuit QQ192 includes filter QQ198 and amplifier QQ196. Radio front-end circuit QQ192 can be connected to antenna QQ162 and processing circuit QQ170. Radio front-end circuit QQ192 can be configured to adjust the signal transmitted between antenna QQ162 and processing circuit QQ170. Radio front-end circuit QQ192 can receive digital data that will be sent to other network nodes or WDs via wireless connection. The radio front end circuit QQ192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters QQ198 and / or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect the radio signal, which is then converted into digital data by the radio front end circuit QQ192. The digital data may be passed to the processing circuit QQ170. In other embodiments, the interface may include different components and / or different combinations of components.

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

[0258] Antenna QQ162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna QQ162 may be coupled to the radio front end circuit QQ190 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna QQ162 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals from devices within a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In a specific embodiment, antenna QQ162 may be separated from network node QQ160 and may be connected to network node QQ160 via an interface or port.

[0259] Antenna QQ162, interface QQ190 and / or processing circuit QQ170 may be configured to perform any receiving operation and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signal may be received from a wireless device, another network node and / or any other network device. Similarly, antenna QQ162, interface QQ190 and / or processing circuit QQ170 may be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal may be sent to a wireless device, another network node and / or any other network device.

[0260] The power circuit QQ187 may include or be coupled to a power management circuit and is configured to provide power for performing the functions described herein to the components of the network node QQ160. The power circuit QQ187 may receive power from the power supply QQ186. The power supply QQ186 and / or the power circuit QQ187 may be configured to provide power to the various components of the network node QQ160 in a form suitable for the various components (e.g., with the voltage and current level required by each corresponding component). The power supply QQ186 may be included in the power circuit QQ187 and / or the network node QQ160 or outside thereof. For example, the 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 the power circuit QQ187. As another example, the power supply QQ186 may include a power source in the form of a battery or battery pack connected to or integrated in the power circuit QQ187. If the external power supply fails, the battery can provide backup power. Other types of power supplies, such as photovoltaic devices, may also be used.

[0261] Alternative embodiments of network node QQ 160 may include Fig.16 Additional components beyond those shown, which 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, the network node QQ 160 may include a user interface device to allow information to be input into the network node QQ 160 and to allow information to be output from the network node QQ 160. This may allow a user to perform diagnostics, maintenance, repair, and other management functions for the network node QQ 160.

[0262] As used herein, wireless device (WD) refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, WD may be configured to send and / or receive information without direct human interaction. For example, WD may be designed to send information to the network in a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop computer built-in devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other cases, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. WD as described above can represent an endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, the WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0263] As shown, the wireless device QQ110 includes an antenna QQ111, an interface QQ114, a processing circuit QQ120, a device-readable medium QQ130, a user interface device QQ132, an auxiliary device QQ134, a power supply QQ136, and a power supply circuit QQ137. The WD QQ110 may include multiple groups of one or more of the components shown for different wireless technologies supported by the 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 the WD QQ110.

[0264] 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 a specific alternative embodiment, 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 receiving or transmitting operation described herein as being performed by 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.

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

[0266] 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 alone or in combination with other WD QQ110 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 a memory within the processing circuit QQ120 to provide the functionality disclosed herein.

[0267] As shown, the processing circuit QQ120 includes one or more of the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In a specific embodiment, the processing circuit QQ120 of the WD QQ110 may include a SOC. In some embodiments, the RF transceiver circuit QQ122, the baseband processing circuit QQ124, and the application processing circuit QQ126 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit QQ124 and the application processing circuit QQ126 may be combined into one chip or chipset, and the RF transceiver circuit QQ122 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit QQ122 and the baseband processing circuit QQ124 may be on the same chip or chipset, and the application processing circuit QQ126 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit QQ122, baseband processing circuit QQ124, and application processing circuit QQ126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit QQ122 may be part of the interface QQ114. The RF transceiver circuit QQ122 may condition the RF signal for the processing circuit QQ120.

[0268] In certain embodiments, some or all of the functions described herein as being performed by WD may be provided by processing circuit QQ120 executing instructions stored on device-readable medium QQ130 (which may be a computer-readable storage medium in certain embodiments). In alternative embodiments, some or all of the functions may be provided by processing circuit QQ120 without the need to execute instructions stored on a separate or separate device-readable storage medium, such as in a hardwired manner. In any of these specific embodiments, processing circuit QQ120 may be configured to perform the described functions, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions 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 in general.

[0269] Processing circuit QQ120 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. Such operations performed by processing circuit QQ120 may include: processing information obtained by processing circuit QQ120, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD QQ110, and / or performing one or more operations based on the obtained information or the converted information; and making a determination as a result of the processing.

[0270] 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 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., hard disk), removable storage media (e.g., compact disk (CD) or 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.

[0271] The user interface device QQ132 may provide components that allow a human user to interact with the WD QQ110. This interaction may be in a variety of forms, such as visual, auditory, tactile, etc. The user interface device QQ132 may be operable to generate output to the user and allow the user to provide input to the WD QQ110. The type of interaction may vary depending on the type of user interface device QQ132 installed in the WD QQ110. For example, if the WD QQ110 is a smart phone, the interaction may be via a touch screen; if the WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected).

[0272] The user interface device QQ132 may include an input interface, device and circuit and an output interface, device and circuit. The user interface device QQ132 is configured to allow information to be input to the WD QQ110, and is connected to the processing circuit QQ120 to allow the processing circuit QQ120 to process the input information. The user interface device QQ132 may include, for example, a microphone, a proximity sensor or other sensors, a key / button, a touch display, one or more cameras, a USB port or other input circuits. The user interface device QQ132 is also configured to allow information to be output from the WD QQ110, and allows the processing circuit QQ120 to output information from the WD QQ110. The user interface device QQ132 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone interface or other output circuits. Using one or more input and output interfaces, devices and circuits of the user interface device QQ132, the WD QQ110 may communicate with an end user and / or a wireless network, and allow them to benefit from the functions described herein.

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

[0274] In some embodiments, the power supply QQ136 may take the form of a battery or a battery pack. Other types of power supplies may also be used, such as an external power supply (e.g., a power outlet), a photovoltaic device, or a battery. WD QQ110 may also include a power circuit QQ137 for delivering power from the power supply QQ136 to various parts of the WD QQ110, which require power from the power supply QQ136 to perform any functions described or indicated herein. In a specific embodiment, the power circuit QQ137 may include a power management circuit. The power circuit QQ137 may additionally or alternatively be operable to receive power from an external power source. In this case, the WD QQ110 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a power cord). In a specific embodiment, the power circuit QQ137 may also be operable to deliver power from an external power source to the power supply QQ136. This may be used, for example, to charge the power supply QQ136. The power circuit QQ137 may perform any formatting, conversion, or other modification of the power from the power supply QQ136 to make the power suitable for the corresponding components of the WD QQ110 to which the power is provided.

[0275] Fig.17 A user equipment according to some embodiments is shown.

[0276] Fig.17 An 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). UEQQ2200 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.17As shown, UE QQ200 is an example of a WD that is configured to communicate according to 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 mentioned above, the terms WD and UE can be used interchangeably. Therefore, although Fig.17 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0277] exist Fig.17 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 Fig.17 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.

[0278] exist Fig.17 In the embodiment of the present invention, the processing circuit QQ201 can be configured to process computer instructions and data. The 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 a 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 of the above. For example, the processing circuit QQ201 can include two central processing units (CPUs). The data can be information in a form suitable for use by a computer.

[0279] In the depicted embodiment, the input / output interface QQ205 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE QQ200 may be configured to use an output device via the input / output interface QQ205. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to or output from the UE QQ200. The output device may 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 may be configured to use an input device via the input / output interface QQ205 to allow the user to capture information into the UE QQ200. The input device may 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 roller, a smart card, etc. The presence-sensitive display may 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.

[0280] exist Fig.17 In the embodiment of the present invention, the RF interface QQ209 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface QQ211 can be configured to provide a communication interface to the network QQ243a. The 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, the network QQ243a can include a Wi-Fi network. The network connection interface QQ211 can be configured to include a receiver and a transmitter interface, which is used to communicate with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface QQ211 can implement receiver and transmitter functions suitable for communication network links (such as optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can be implemented separately instead.

[0281] RAM QQ217 can be configured to be connected to processing circuit QQ201 via bus QQ202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications 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 unchanged low-level system code or data for basic system functions (e.g., basic input and output (I / O), startup, reception of keystrokes stored in non-volatile memory from a keyboard). Storage medium QQ221 can be configured to include memories such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cassette or flash drive. In one example, storage medium QQ221 can be configured to include operating system QQ223, application QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. The storage medium QQ221 may store any one of various operating systems or a combination of operating systems for use by the UE QQ200 .

[0282] The storage medium QQ221 may 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 optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a user identity module or a removable user identity (SIM / RUIM) module), other memories, or any combination thereof. The storage medium QQ221 may allow the UEQQ200 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. An article of manufacture such as one utilizing a communication system may be tangibly embodied in the storage medium QQ221, which may include a device-readable medium.

[0283] exist Fig.17In the embodiment of the present invention, the processing circuit QQ201 can be configured to communicate with the network QQ243b using the communication subsystem QQ231. The network QQ243a and the network QQ243b can be the same network or different networks. The communication subsystem QQ231 can be configured to include one or more transceivers for communicating with the network QQ243b. For example, the 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 base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (e.g., IEEE802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include a transmitter QQ233 and / or a receiver QQ235 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter QQ233 and the receiver QQ235 of each transceiver can share circuit components, software or firmware, or can be implemented separately instead.

[0284] 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 the 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.

[0285] 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. In addition, 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 component described herein. In addition, the processing circuit QQ201 may be configured to communicate with any such component on the bus QQ202. In another example, any such component may be represented by a program instruction stored in a memory, which executes the corresponding function described herein when executed by the processing circuit QQ201. In another example, the function 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.

[0286] Fig.18 A virtualized environment is shown in accordance with some embodiments.

[0287] Fig.18 is a schematic block diagram showing a virtualization environment QQ300 in which functions implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are 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).

[0288] 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 QQ300 hosted by one or more hardware nodes QQ330. 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.

[0289] These functions may be implemented by one or more applications QQ320 (which may alternatively be referred to as software instances, virtual devices, 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, whereby applications QQ320 are operable to provide one or more features, benefits, and / or functions disclosed herein.

[0290] The virtualized environment QQ300 includes a general-purpose or special-purpose 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 special-purpose processors. Each hardware device may include a memory QQ390-1, which may be a 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-temporary 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 the functions, features and / or benefits associated with some of the embodiments described herein.

[0291] The virtual machine QQ340 includes virtual processing, virtual memory, virtual network or interface, and virtual storage, and can be run by a corresponding virtualization layer QQ350 or a system hypervisor. Different embodiments of instances of the virtual device QQ320 can be implemented on one or more virtual machines QQ340 and can be implemented in different ways.

[0292] During operation, processing circuit QQ360 executes software QQ395 to instantiate a hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present to virtual machine QQ340 a virtual operating platform that appears to be networked hardware.

[0293] like Fig.18As shown, hardware QQ330 can be an independent network node with common or specific components. Hardware QQ330 can include antenna QQ3225, and some functions can be implemented via virtualization. Alternatively, hardware QQ330 can be part of a larger hardware cluster (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) QQ3100, which, among other items, oversees the life cycle management of application QQ320.

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

[0295] In the context of NFV, a virtual machine QQ340 may be a software implementation of a physical machine that runs a program as if the program were executed on a physical, non-virtual machine. Each virtual machine QQ340 and the portion of the hardware QQ330 that executes the virtual machine (hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines QQ340) form a separate virtual network element (VNE).

[0296] 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 Fig.18 Application QQ320.

[0297] In some embodiments, one or more radio units QQ3200, each including one or more transmitters QQ3220 and one or more receivers QQ3210, may be coupled to one or more antennas QQ3225. The radio unit QQ3200 may communicate directly with the hardware node QQ330 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.

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

[0299] Fig.19 A telecommunications network is shown connected to a host computer via an intermediary network in accordance with some embodiments.

[0300] refer to Fig.19According to an embodiment, a communication system includes a telecommunication 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., NB, eNB, gNB) or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c may 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 be wirelessly connected to or paged by the corresponding base station QQ412c. A second UE QQ492 in the coverage area QQ413a may be wirelessly connected 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 a UE is in the coverage area or only a UE is connected to the corresponding base station QQ412 .

[0301] The telecommunications network QQ410 itself is connected to a host computer QQ430, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The 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. The connections QQ421 and QQ422 between the telecommunications network QQ410 and the host computer QQ430 may extend directly from the core network QQ414 to the host computer QQ430, or may be via an optional intermediate network QQ420. The intermediate network QQ420 may be one of a public, private, or managed network, or a combination of more than one thereof; the intermediate network QQ420 (if any) may be a backbone network or the Internet; in particular, the intermediate network QQ420 may include two or more subnetworks (not shown).

[0302] Overall, Fig.19The communication system realizes the connectivity between the connected UE QQ491, QQ492 and the host computer QQ430. The connectivity can be described as an over-the-top (OTT) connection QQ450. The host computer QQ430 and the connected UE QQ491, QQ492 are configured to use the access network QQ411, the core network QQ414, any intermediate network QQ420 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection QQ450. The OTT connection QQ450 can be transparent because the participating communication devices through which the OTT connection QQ450 passes do not know the routes of the uplink and downlink communications. For example, the base station QQ412 may not be notified or need not be notified of the past routes of the incoming downlink communications of the data to be forwarded (e.g., handed over) to the connected UE QQ491 originating from the host computer QQ430. Similarly, the base station QQ412 does not need to know the future routes of the outgoing uplink communications from the UE QQ491 to the host computer QQ430.

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

[0304] Now refer to Fig. 20 To describe the example implementation of the UE, base station and host computer discussed in the previous paragraph 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 the interface of 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. Software QQ511 includes a host application QQ512. The 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, the host application QQ512 may provide user data sent using the OTT connection QQ550.

[0305] The communication system QQ500 also includes a base station QQ520 provided in the telecommunication 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 a wired or wireless connection with different communication devices of the communication system QQ500, and a communication interface QQ526 for establishing and maintaining a connection with the network located in the coverage area ( Fig. 20 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 wireless communication network) of the telecommunications system. Fig. 20 ) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware QQ525 of the 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 of these items (not shown) suitable for executing instructions. The base station QQ520 also has software QQ521 stored internally or accessible via an external connection.

[0306] The communication system QQ500 also includes the UE QQ530 already mentioned. 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 where the UE QQ530 is currently located. The hardware QQ535 of the UE QQ530 also includes a processing circuit 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 circuit 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 QQ510, the executing host application QQ512 can communicate with the executing client application QQ532 via the OTT connection QQ550 terminated at the UE QQ530 and the host computer QQ510. In providing services to users, the client application QQ532 can receive request data from the host application QQ512 and provide user data in response to the request data. The OTT connection QQ550 can transmit both the request data and the user data. The client application QQ532 can interact with the user to generate the user data it provides.

[0307] Notice, Fig. 20 The host computer QQ510, base station QQ520 and UE QQ530 shown can be respectively Fig.19 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 Fig. 20 shown, and independently, the surrounding network topology can be Fig.19 The surrounding network topology.

[0308] exist Fig. 20 , an OTT connection QQ550 has been abstractly drawn to illustrate communications between a host computer QQ510 and a UE QQ530 via a base station QQ520, without explicit reference to any intermediate devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide the routing from the UE QQ530 or from the service provider operating the host computer QQ510, or both. When the OTT connection QQ550 is active, the network infrastructure may further make a decision according to which the network infrastructure dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0309] The wireless connection QQ570 between the UE QQ530 and the base station QQ520 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments may improve the performance of the OTT service provided to the UE QQ530 using the OTT connection QQ550 (where the wireless connection QQ570 forms the last segment). More specifically, the teachings of these embodiments may improve the random access speed and / or reduce the random access failure rate, thereby providing benefits such as faster and / or more reliable random access.

[0310] The measurement process may be provided for the purpose of monitoring data rates, delays, and other factors on which one or more embodiments are improved. In response to changes in the measurement results, there may also be an optional network function 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 a communication device through which the OTT connection QQ550 passes or is associated with such a communication device; the sensor may participate in the measurement process by providing the value of the monitored quantity of the above example or providing the value of other physical quantities from which the software QQ511, QQ531 can calculate or estimate the monitored quantity. The reconfiguration of the OTT connection QQ550 may include message formats, retransmission settings, preferred routes, etc. The reconfiguration does not need to affect the base station QQ520, and it 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 the host computer QQ510 to measure throughput, propagation time, latency, etc. The measurements may be achieved because the software QQ511 and QQ531 cause messages, particularly empty or "dummy" messages, to be sent using the OTT connection QQ550 during its monitoring of propagation time, errors, etc.

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

[0312] Fig.21 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.19 and Fig. 20 In order to simplify the present disclosure, only the host computer, base station and UE described in this section are included. Fig.21 Reference is made to the accompanying drawings of . In step QQ610, the host computer provides user data. In sub-step QQ611 of step QQ610 (which may be optional), the host computer provides user data by executing a host application. In step QQ620, the host computer initiates a transmission to the UE carrying the user data. In step QQ630 (which may be optional), in accordance with the teachings of the embodiments described throughout the present 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.

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

[0314] Fig. 22 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.19 and Fig. 20 In order to simplify the present disclosure, this section only includes the host computer, base station and UE described in the present disclosure. Fig. 22 . 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 the present disclosure, the transmission may be through a base station. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

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

[0316] Fig.23 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.19 and Fig. 20 In order to simplify the present disclosure, this section only includes the host computer, base station and UE described in the present disclosure. Fig.23 . 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 of step QQ820 (which may be optional), the UE provides user data by executing a client application. In sub-step QQ811 of step QQ810 (which may be optional), the UE executes a client application, which 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 of providing user data, the UE initiates transmission of 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 the present disclosure, the host computer receives user data sent from the UE.

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

[0318] Fig.24 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.19 and Fig. 20 In order to simplify the present disclosure, this section only includes the host computer, base station and UE described in the present disclosure. Fig.24 In step QQ910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. 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.

[0319] 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 codes 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 unit to perform the corresponding functions according to one or more embodiments of the present disclosure.

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

[0321] abbreviation

[0322] At least some of the following abbreviations may be used in the present disclosure. If there is an inconsistency between the abbreviations, the above usage should be preferred. If listed multiple times below, the first listing should take precedence over subsequent listings.

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

[0324] 3GPP Third Generation Partnership Project

[0325] 5G Fifth Generation

[0326] ABS Almost Blank Subframe

[0327] ARQ Automatic Repeat Request

[0328] AWGN Additive White Gaussian Noise

[0329] BCCH Broadcast Control Channel

[0330] BCH Broadcast Channel

[0331] CA Carrier Aggregation

[0332] CC Carrier Component

[0333] CCCH SDU Common Control Channel SDU

[0334] CDMA Code Division Multiple Access

[0335] CGI Cell Global Identifier

[0336] CIR Channel Impulse Response

[0337] CP Cyclic Prefix

[0338] CPICH Common Pilot Channel

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

[0340] CQI Channel Quality Information

[0341] C-RNTI Cell RNTI

[0342] CSI Channel State Information

[0343] DCCH Dedicated Control Channel

[0344] DL Downlink

[0345] DM Demodulation

[0346] DMRS Demodulation Reference Signal

[0347] DRX Discontinuous Reception

[0348] DTX Discontinuous Transmission

[0349] DTCH Dedicated Traffic Channel

[0350] DUT Device Under Test

[0351] E-CID Enhanced Cell ID (positioning method)

[0352] E-SMLC Evolved Serving Mobile Location Center

[0353] ECGI Evolved CGI

[0354] eNB E-UTRAN Node B

[0355] ePDCCH Enhanced Physical Downlink Control Channel

[0356] E-SMLC Evolved Serving Mobile Location Center

[0357] E-UTRA Evolved UTRA

[0358] E-UTRAN Evolved UTRAN

[0359] FDD Frequency Division Duplex

[0360] FFS needs further study

[0361] GERAN GSM EDGE Radio Access Network

[0362] Base stations in gNB NR

[0363] GNSS Global Navigation Satellite System

[0364] GSM Global System for Mobile Communications

[0365] HARQ Hybrid Automatic Repeat Request

[0366] HO Switchover

[0367] HSPA High Speed ​​Packet Access

[0368] HRPD High Rate Packet Data

[0369] LOS Line of Sight

[0370] LPP LTE Positioning Protocol

[0371] LTE Long Term Evolution

[0372] MAC Media Access Control

[0373] MBMS Multimedia Broadcast Multicast Service

[0374] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0375] MBSFN ABS MBSFN Almost Blank Subframe

[0376] MDT Minimized Drive Test

[0377] MIB Master Information Block

[0378] MME Mobility Management Entity

[0379] MSC Mobile Switching Center

[0380] NPDCCH Narrowband Physical Downlink Control Channel

[0381] NR New Radio

[0382] OCNG OFDMA Channel Noise Generator

[0383] OFDM Orthogonal Frequency Division Multiplexing

[0384] OFDMA Orthogonal Frequency Division Multiple Access

[0385] OSS Operation Support System

[0386] OTDOA observed time difference of arrival

[0387] O&M

[0388] PBCH Physical Broadcast Channel

[0389] P-CCPCH Primary Common Control Physical Channel

[0390] PCell Primary Cell

[0391] PCFICH Physical Control Format Indicator Channel

[0392] PDCCH Physical Downlink Control Channel

[0393] PDP Profile Delay Profile

[0394] PDSCH Physical Downlink Shared Channel

[0395] PGW Packet Gateway

[0396] PHICH Physical Hybrid ARQ Indicator Channel

[0397] PLMN Public Land Mobile Network

[0398] PMI Precoder Matrix Indicator

[0399] PRACH Physical Random Access Channel

[0400] PRS Positioning Reference Signal

[0401] PSS Primary Synchronization Signal

[0402] PUCCH Physical Uplink Control Channel

[0403] PUSCH Physical Uplink Shared Channel

[0404] RACH Random Access Channel

[0405] QAM Quadrature Amplitude Modulation

[0406] RAN Radio Access Network

[0407] RAT Radio Access Technology

[0408] RLM Radio Link Management

[0409] RNC Radio Network Controller

[0410] RNTI Radio Network Temporary Identifier

[0411] RRC Radio Resource Control

[0412] RRM Radio Resource Management

[0413] RS reference signal

[0414] RSCP Received Signal Code Power

[0415] RSRP Reference Symbol Received Power or

[0416] Reference signal received power

[0417] RSRQ Reference Signal Received Quality or

[0418] Reference symbol reception quality

[0419] RSSI Received Signal Strength Indicator

[0420] RSTD Reference Signal Time Difference

[0421] SCH Synchronization Channel

[0422] SCell Secondary Cell

[0423] SDU Service Data Unit

[0424] SFN System Frame Number

[0425] SGW Service Gateway

[0426] SI System Information

[0427] SIB System Information Block

[0428] SNR Signal to Noise Ratio

[0429] SON Self-Optimizing Network

[0430] SS Sync Signal

[0431] SSS Secondary synchronization signal

[0432] TDD Time Division Duplex

[0433] TDOA Time Difference of Arrival

[0434] TOA Time of Arrival

[0435] TSS three-level synchronization signal

[0436] TTI Transmission Time Interval

[0437] UE User Equipment

[0438] UL Uplink

[0439] UMTS Universal Mobile Telecommunications System

[0440] USIM Universal Subscriber Identity Module

[0441] UTDOA Uplink Time Difference of Arrival

[0442] UTRA Universal Terrestrial Radio Access

[0443] UTRAN Universal Terrestrial Radio Access Network

[0444] WCDMA Wideband CDMA

[0445] WLAN broadband local area network

[0446] Additional definitions and embodiments are discussed below.

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

[0448] 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. The same numbers herein refer to the same units. In addition, as used herein, "coupling," "connecting," "responsiveness" 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" includes any and all combinations of one or more listed associated items.

[0449] 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. Therefore, the first unit / operation in some embodiments may be referred to as the second unit / operation in other embodiments without departing from the teaching of the inventive concept. The same reference numerals or the same reference designators in this specification represent the same or similar units.

[0450] As used herein, the terms "comprises," "including," "having," or variations thereof are open ended and include one or more stated features, integers, units, steps, components, or functions, but do not exclude the presence or addition of one or more other features, integers, units, steps, components, functions, or combinations thereof. In addition, 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 "that is," derived from the Latin phrase "id est," may be used to specify a specific item from a more general description.

[0451] Example embodiments are described herein with reference to block diagrams and / or flow charts 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 flow charts, and the combination of the blocks in the block diagrams and / or flow charts, 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 via 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 flow charts, thereby generating a device (function) and / or structure that implements the functions / operations specified in the blocks in the block diagrams and / or flow charts.

[0452] 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 diagram and / or flow chart. 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.

[0453] It should also be noted that in some alternative implementations, the function / operation marked in the square frame can occur in a sequence different from that marked in the flow chart. For example, two continuous square frames can actually be performed substantially in parallel, and they can also be performed in reverse order sometimes, depending on the function / operation involved. In addition, the function of the given square frame of flow chart and / or block diagram can be divided into a plurality of square frames, and / or the function of two or more square frames of flow chart and / or block diagram can be integrated at least in part. Finally, other square frames can be added / inserted between the square frames shown, and / or square frame / operation can be omitted without departing from the scope of the inventive concept. In addition, although some figures include arrows on the communication path to illustrate the main direction of communication, it will be understood that communication can occur in the direction opposite to the arrows shown.

[0454] Many changes and modifications can be made to the embodiments without departing substantially from the principles 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 rather than restrictive, and the examples of the embodiments are 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 permitted by law, the scope of the inventive concept will be determined by the most widely permitted interpretation of the disclosure (including examples of the embodiments and their equivalents), and should not be limited or restricted by the above detailed description.

Claims

1. A method for operating a first vehicle-to-everything V2X application enabler (VAE) server, the method comprising: Receiving V2X message information by geographic area from a V2X application specific server; receiving location information from a VAE client of a wireless device, wherein the location information indicates a location of the wireless device; In response to receiving the location information and in response to the V2X message information by geographic area, identifying a second VAE server based on the location information; and Send the address of the second VAE server to the VAE client of the wireless device.

2. The method according to claim 1, wherein: Identifying the second VAE server includes: sending a server continuity request to multiple other VAE servers including the second VAE server, wherein the server continuity request includes the location information; and receiving a server continuity response from the second VAE server, wherein the server continuity response includes the address of the second VAE server.

3. The method according to claim 1, wherein: Receiving the location information includes: receiving a location update message from the VAE client of the wireless device, wherein the location update message includes the location information.

4. The method according to claim 1, wherein: Receiving the location information includes receiving an initial registration message from the VAE client of the wireless device, wherein the initial registration message includes the location information.

5. The method according to claim 1, wherein: Sending the address includes: sending a redirect message to the VAE client of the wireless device, wherein the redirect message includes the address of the second VAE server.

6. The method according to claim 1, wherein: The location information includes a geographic area identifier GEO ID.

7. The method according to claim 1, wherein: The address of the second VAE server includes a fully qualified domain name of the second VAE server.

8. The method according to claim 1, wherein: The first VAE server is a message agent responsible for message distribution.

9. The method according to claim 1, wherein: Identifying the second VAE server is based on the location information and based on a publication option of V2X messages by geographic area.

10. The method according to claim 1, wherein: The location information is received from the VAE client as a geolocation update having a geographic area identifier GEOID.

11. A method for operating a first vehicle-to-everything V2X application enabler (VAE) server, the method comprising: receiving a server continuity request from a second VAE server, wherein the server continuity request includes location information of the wireless device; In response to the server continuity request, sending a server continuity response to the second VAE server, wherein the server continuity response includes an address of the first VAE server; and In response to receiving the server continuity request, comparing the location information with a service area of ​​the first VAE server; The sending of the server continuity response includes: sending the server continuity response in response to the location information matching a service area of ​​the first VAE server.

12. The method according to claim 11, wherein: The location information includes a geographic area identifier.

13. The method according to claim 11, wherein: The second VAE server is a message agent responsible for message distribution.

14. A method of operating a vehicle-to-everything (V2X) wireless device, the method comprising: Providing VAE server information for a plurality of VAE servers, wherein the VAE server information includes a respective address of each of the plurality of VAE servers, a respective geographic region associated with the VAE server, and / or respective service / message information related to a V2X service available from the VAE server; subscribing to receive V2X messages from a first VAE server among the plurality of VAE servers; In response to detecting movement from a first geographic region associated with the first VAE server to a second geographic region, identifying a second VAE server associated with the second geographic region from among the plurality of VAE servers based on the VAE server information; and In response to identifying the second VAE server, subscribing to receive V2X messages from the second VAE server.

15. The method according to claim 14, further comprising: In response to detecting the movement and / or in response to identifying the second VAE server, unsubscribing from the first VAE server.

16. The method according to claim 14, wherein: Providing the VAE server information includes: obtaining a corresponding address of each of the plurality of VAE servers and / or a corresponding geographical area associated with each of the plurality of VAE servers from a configuration management server.

17. The method according to claim 14, wherein: Providing the VAE server information includes pre-configuring a corresponding address of each of the plurality of VAE servers and / or a corresponding geographical area associated with each of the plurality of VAE servers.

18. The method according to claim 14, wherein: Providing the VAE server information includes: obtaining, from one of the plurality of VAE servers, corresponding service / message information related to a V2X service available from each of the plurality of VAE servers.

19. A first vehicle-to-everything V2X application enabler VAE server, configured to operate with a communication network, the VAE server comprising: Processing circuit; as well as a memory coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the first VAE server to: Receiving V2X message information by geographic area from a V2X application specific server; receiving location information from a VAE client of a wireless device, wherein the location information indicates a location of the wireless device; In response to receiving the location information and in response to the V2X message information by geographic area, identifying a second VAE server based on the location information; and Send the address of the second VAE server to the VAE client of the wireless device.

20. The first VAE server according to claim 19, wherein: The instructions that, when executed by the processing circuit, cause the first VAE server to identify the second VAE server include instructions that, when executed by the processing circuit, cause the first VAE server to: sending a server continuity request to a plurality of other VAE servers including the second VAE server, wherein the server continuity request includes the location information; and A server continuity response is received from the second VAE server, wherein the server continuity response includes the address of the second VAE server.

21. The first VAE server according to claim 19, wherein: The instructions that, when executed by the processing circuit, cause the first VAE server to receive the location information include instructions that, when executed by the processing circuit, cause the first VAE server to receive a location update message from the VAE client of the wireless device, wherein the location update message includes the location information.

22. The first VAE server according to claim 19, wherein: The instructions that, when executed by the processing circuit, cause the first VAE server to receive the location information include instructions that, when executed by the processing circuit, cause the first VAE server to receive an initial registration message from the VAE client of the wireless device, wherein the initial registration message includes the location information.

23. The first VAE server according to claim 19, wherein: The instructions that, when executed by the processing circuit, cause the first VAE server to send the address include instructions that, when executed by the processing circuit, cause the first VAE server to send a redirect message to the VAE client of the wireless device, wherein the redirect message includes the address of the second VAE server.

24. The first VAE server according to claim 19, wherein: The location information includes a geographic area identifier GEO ID.

25. The first VAE server of claim 19, wherein: The address of the second VAE server includes a fully qualified domain name of the second VAE server.

26. The first VAE server of claim 19, wherein: The first VAE server is a message agent responsible for message distribution.

27. The first VAE server according to claim 19, wherein: Identifying the second VAE server is based on the location information and based on a publication option of V2X messages by geographic area.

28. The first VAE server of claim 19, wherein: The location information is received from the VAE client as a geolocation update having a geographic area identifier GEO ID.

29. A first vehicle-to-everything V2X application enabler VAE server, configured to operate with a communication network, the VAE server comprising: Processing circuit; as well as a memory coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the first VAE server to: receiving a server continuity request from a second VAE server, wherein the server continuity request includes location information of the wireless device; and In response to the server continuity request, sending a server continuity response to the second VAE server, wherein the server continuity response includes an address of the first VAE server, and In response to receiving the server continuity request, comparing the location information with a service area of ​​the first VAE server, The sending of the server continuity response includes: sending the server continuity response in response to the location information matching a service area of ​​the first VAE server.

30. The first VAE server according to claim 29, wherein: The location information includes a geographic area identifier.

31. The first VAE server of claim 29, wherein: The second VAE server is a message agent responsible for message distribution.

32. A computer-readable storage medium storing program code to be executed by a processing circuit of a first VAE server, the first VAE server being configured to operate in a communication network, whereby execution of the program code causes the first VAE server to perform operations according to any one of claims 1-13.

33. A vehicle-to-everything (V2X) wireless device configured to operate in a communication network, the V2X wireless device comprising: Processing circuit; as well as a memory coupled to the processing circuit, wherein the memory includes instructions that, when executed by the processing circuit, cause the V2X wireless device to: Providing VAE server information for a plurality of VAE servers, wherein the VAE server information includes a respective address of each of the plurality of VAE servers, a respective geographic region associated with the VAE server, and / or respective service / message information related to a V2X service available from the VAE server; subscribing to receive V2X messages from a first VAE server among the plurality of VAE servers; In response to detecting movement from a first geographic region associated with the first VAE server to a second geographic region, identifying a second VAE server associated with the second geographic region from among the plurality of VAE servers based on the VAE server information; and In response to identifying the second VAE server, subscribing to receive V2X messages from the second VAE server.

34. The V2X wireless device according to claim 33, wherein: The instructions, when executed by the processing circuit, further cause the V2X wireless device to perform the following operations: In response to detecting the movement and / or in response to identifying the second VAE server, unsubscribing from the first VAE server.

35. The V2X wireless device of claim 33, wherein: The instructions that, when executed by the processing circuit, cause the V2X wireless device to provide the VAE server information include instructions that, when executed by the processing circuit, cause the V2X wireless device to obtain a corresponding address of each of the multiple VAE servers and / or a corresponding geographic area associated with each of the multiple VAE servers from a configuration management server.

36. The V2X wireless device of claim 33, wherein: The instructions that, when executed by the processing circuit, cause the V2X wireless device to provide the VAE server information include instructions that, when executed by the processing circuit, cause the V2X wireless device to pre-configure a respective address of each of the plurality of VAE servers and / or a respective geographic area associated with each of the plurality of VAE servers.

37. The V2X wireless device of claim 33, wherein: The instructions that, when executed by the processing circuit, cause the V2X wireless device to provide the VAE server information include instructions that, when executed by the processing circuit, cause the V2X wireless device to obtain, from one of the plurality of VAE servers, corresponding service / message information related to V2X services available from each of the plurality of VAE servers.

38. A computer-readable storage medium storing program code to be executed by a processing circuit of a V2X radio device, the V2X radio device being configured to operate in a communication network, whereby execution of the program code causes the V2X radio device to perform operations according to any one of claims 14-18.

Images