Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.286  Word version:  18.4.0

Top   Top   Up   Prev   Next
0…   4…   6…   7…   9…   9.2…   9.3…   9.4…   9.5…   9.6…   9.7…   9.8…   9.9…   9.10…   9.11…   9.12…   9.13…   9.14…   9.15…   9.16…   9.17…   9.18   9.19…   9.20…   9.21…   9.22…   10…   10.2.8…   A   B…   C…   D… 
9.10 V2X service continuity  9.10.1 General  9.10.2 Information flows  9.10.2.1 Service continuity request  9.10.2.2 Service continuity response  9.10.2.3 Local service information request (VAE client to VAE server)  9.10.2.3a Local service information request (between VAE servers)  9.10.2.4 Local service information response  9.10.3 V2X service continuity management  9.10.3.1 General  9.10.3.2 Procedure  9.10.4 Dynamic local service information  9.10.4.1 General  9.10.4.2 Procedure  9.10.5 Procedure for dynamic local service information in multiple V2X service provider scenario 
...

 

9.10  V2X service continuity  p. 55

9.10.1  General  p. 55

The VAE server supports V2X service continuity by making available the local service information based on geographical areas to the V2X UEs.

9.10.2  Information flows  p. 55

9.10.2.1  Service continuity request  p. 55

Table 9.10.2.1-1 describes the information flow from a VAE server to issue a service continuity request to other VAE servers.
Information Element Status Description
GEO IDMGeographical area identifier (e.g. URI, tile identifier, geo-fence tile identifier)
V2X service IDMPSID or ITS-AID the V2X UE is interested in receiving (e.g. ETSI ITS DENM, ETSI ITS CAM)
Up

9.10.2.2  Service continuity response  p. 55

Table 9.10.2.2-1 describes the information flow for a VAE server to respond to a service continuity request from other VAE server.
Information Element Status Description
VAE server IDMIdentifier of the VAE server (e.g., FQDN)
ResultMThe result whether the VAE server can serve the requested GEO ID and V2X Service ID
Up

9.10.2.3  Local service information request (VAE client to VAE server)  p. 55

Table 9.10.2.3-1 describes the information flow local service information request from the VAE client to the VAE server.
Information Element Status Description
V2X UE IDMIdentity of the V2X UE requesting the service discovery information
GEO IDMGeographical area identifier for which the local service information is requested
Up

9.10.2.3a  Local service information request (between VAE servers) |R17|  p. 56

Table 9.10.2.3a-1 describes the information flow local service information request between VAE servers.
Information element Status Description
V2X UE IDOIdentity of the V2X UE requesting the service discovery information.
V2X UE locationMThe V2X UE location information for which the location service information is requested.
GEO IDMGeographical area identifier for which the local service information is requested
Up

9.10.2.4  Local service information response  p. 56

Table 9.10.2.4-1 describes the information flow local service information response from the VAE server to the VAE client and between VAE servers.
Information Element Status Description
ResultMIndicates the success or failure of getting the local service information
Local service informationO (NOTE)The local service information:
  • V2X server USD information as specified in TS 23.285
  • V2X application server address information as specified in TS 23.285 and transport port for unicast
  • V2X USD information as specified in TS 23.285
NOTE:
If the Result information element indicates failure then local service information IE is not included.
Up

9.10.3  V2X service continuity management  p. 56

9.10.3.1  General  p. 56

This subclause describes the procedure to determine the VAE server for serving a VAE client when moving to a new geographical area.

9.10.3.2  Procedure  p. 56

Pre-conditions:
  1. The VAE servers have been configured with the information of the other VAE servers.
  2. The VAE servers have obtained information of the available V2X services (e.g. identified by PSID or ITS-AIDs) and their corresponding geographical area association from the V2X application.
  3. The VAE server 1 has received a geographic location update for a geographic area outside its coverage, with GEO ID, from a VAE client as described in subclause 9.3.
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.10.3.2-1: Procedure for V2X service continuity management
Figure 9.10.3.2-1: Procedure for V2X service continuity management
(⇒ copy of original 3GPP image)
Up
Step 1.
VAE server 1 sends a service continuity request to other VAE servers (2 ... n).
Step 2.
The VAE servers provide a service continuity response to VAE server 1.

9.10.4  Dynamic local service information  p. 57

9.10.4.1  General  p. 57

For the V2X scenarios like extended sensors, platooning, the V2X UEs may be connected to the serving PLMN, but the V2X application server information may change as per the geographical location. Also it is not practically feasible to provide all the V2X server USDs to the V2X UE via the initial V2X UE configuration by the PLMN. It is hence required that the V2X server USDs may be provided considering the mobility of the V2X UE. This subclause describes the procedure for obtaining the local service information by the V2X UE via V1-AE.
Up

9.10.4.2  Procedure  p. 57

Figure 9.10.4.2-1 illustrates the procedure for obtaining the dynamic local service information by the V2X UE via V1-AE.
Pre-conditions:
  1. The V2X UE is connected to the VAE server in geographical area A.
  2. The V2X UE has no local service information for geographical area B.
  3. If multicast delivery mode is used, the MBMS bearer being used is activated by the VAE server.
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.10.4.2-1: Obtaining dynamic local service information by V2X UE via V1-AE
Figure 9.10.4.2-1: Obtaining dynamic local service information by V2X UE via V1-AE
(⇒ copy of original 3GPP image)
Up
Step 1.
The VAE client sends a local service information request to the VAE server (responsible for geographic location A) which may include mobility information like the geographic locations (geographic location B).
Step 2.
The VAE server determines the local service information (e.g. V2X server USD(s), V2X USD) corresponding to the geographic locations information received in step 1.
Step 3.
The VAE server provides the local service information (e.g. V2X server USD(s), V2X USD) with the corresponding geographic locations information to the VAE client via a local service information response. The V2X USD information consists of TMGI, list of SAIs, frequency and SDP information with the local service information for local V2X application server discovery. The details of V2X server USD are specified in subclause 4.4.7.3 in TS 23.285. This message can be sent via unicast or multicast.
Step 4.
Upon receiving the local service information in step 3, the VAE client stores the received information.
Up

9.10.5  Procedure for dynamic local service information in multiple V2X service provider scenario |R17|  p. 58

The procedure for V2X UE (having V2X application subscription with V2X service provider A) obtaining the dynamic local service information (offered by V2X service provider B) while in the service area of V2X service provider B is illustrated in Figure 9.10.5-1.
Pre-conditions:
  1. The V2X UE has connected to the VAE server of V2X service provider A with whom the V2X UE has V2X application subscription with.
  2. The V2X UE is in the service area of the VAE server 2 operated by V2X service provider B.
  3. The service area and VAE server 2 information of V2X service provider B mapping is available at VAE server 1 of V2X service provider A.
Copy of original 3GPP image for 3GPP TS 23.286, Fig. 9.10.5-1: Dynamic local service information in multiple V2X service provider scenario
Figure 9.10.5-1: Dynamic local service information in multiple V2X service provider scenario
(⇒ copy of original 3GPP image)
Up
Step 1.
The VAE client sends a local service information request to the VAE server 1 (responsible for geographic location A) with V2X UE ID and current V2X UE location.
Step 2.
The VAE server 1 determines the V2X UE is in the service area of VAE server 2 of V2X service provider B, and the local service information corresponding to the service area of VAE server 2 is not available at VAE server 1. If the local service information corresponding to the service area of VAE server 2 is available, then go to step 5.
Step 3.
The VAE server 1 sends the local service information request to the VAE server 2 to get the local service information information for the V2X UE. The V2X UE location is included in the request.
Step 4.
The VAE server 2 determines the local service information (e.g. V2X server USD(s), V2X USD) with the corresponding geographic locations information based on UE location, and sends local service information response to the VAE server 1. This message carries the local service information. Upon receiving the local service information corresponding to the service area of VAE server 2, the VAE server 1 stores the received information.
Step 5.
The VAE server 1 provides the local service information to the VAE client. Upon receiving the local service information, the VAE client stores the received information.
Up

Up   Top   ToC