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 Procedures and information flows  9.1 Usage of SEAL services  9.1.1 Group management service  9.1.1.1 General  9.1.1.2 Information flows  9.1.1.3 Procedures  9.1.2 Configuration management service  9.1.2.1 General  9.1.2.2 Information flows  9.1.2.3 Procedures  9.1.3 Location management service  9.1.3.1 General  9.1.3.2 Information flows  9.1.3.3 Procedures  9.1.4 Identity management service  9.1.4.1 General  9.1.4.2 Information flows  9.1.4.3 Procedures  9.1.5 Key management service  9.1.5.1 General  9.1.5.2 Information flows  9.1.5.3 Procedures  9.1.6 Network resource management service  9.1.6.1 General  9.1.6.2 Information flows  9.1.6.3 Procedures 
...

 

9  Procedures and information flows  p. 29

9.1  Usage of SEAL services  p. 29

9.1.1  Group management service  p. 29

9.1.1.1  General  p. 29

The VAE capabilities (VAE client and VAE server) utilize the group management service procedures (e.g. creation, join, leave) of SEAL based on the group configuration information (e.g. group join policy, group leader) provided by the V2X application specific layer. The decisions and corresponding triggers (e.g. group creation, join, leave) for group management are responsibility of the V2X application specific layer and the details of the group management are abstracted by the VAE capabilities. The group management service of SEAL provides support for platooning groups and pre-arranged groups for V2X communications.
Up

9.1.1.2  Information flows  p. 29

The following information flows of group management service of SEAL as specified in TS 23.434 are applicable for the V2X applications:
The usage of the above information flows are clarified as below:
  • The identity list is the list of V2X UE IDs.
    • During group creation the identity list contains the list of V2X UE IDs that are part of the group to be created. If the group member list is empty, an empty group is created; and
  • The VAL service ID list is the list of V2X service IDs whose service communications are to be enabled on the group.
  • Table 9.1.1.2.1-1 describes the VAL service specific information corresponding to the V2X applications.
Information Element Status Description
V2X group IDOThe group ID to be used for the V2X group. If group ID is not provided then the group ID should be allocated by group management server
Group join policyO (NOTE)The policy information to be enforced by the group management server for members joining the group
Group leader IDO (NOTE)The identity information of the V2X user to be used for user controlled group join
NOTE:
If the information elements, identity list specified in TS 23.434 is empty and group leader ID is not included, then group join policy information element must be included.
  • The VAL group ID is the V2X group ID.
  • The identity is the V2X UE ID;
  • The VAL server is the VAE server;
  • The VAL group configuration information is the V2X group configuration information;
  • The VAL group configuration data is the V2X group configuration information;
  • The VAL group information reference is the V2X group information reference; and
  • The VAL services requested is the V2X service IDs.
Up

9.1.1.3  Procedures  p. 31

The following procedures of group management service of SEAL as specified in TS 23.434 are applicable for the V2X applications:
  • Group creation specified in subclause 10.3.3;
    • Group creation support is provided for the V2X applications (e.g. platooning and cooperative short distance grouping) to provide a dedicated group for the V2X UEs to communicate with each other. The group creation supports group without any group members to enable group member joining.
  • Group information query specified in subclause 10.3.4;
  • Group membership specified in subclause 10.3.5;
  • Group configuration management specified in subclause 10.3.6;
  • Location-based group creation specified in clause 10.3.7;
  • Group announcement and join specified in subclause 10.3.8;
  • Group member leave specified in clause 10.3.9;
  • Temporary groups specified in clause 10.3.10;
Up

9.1.2  Configuration management service  p. 32

9.1.2.1  General  p. 32

The VAE capabilities (VAE client and VAE server) utilize configuration management service procedures of SEAL to support V2X services for unicast and multicast delivery over LTE-Uu. The configuration management service of SEAL is utilized for offline configuration (before the V2X UE is receiving the V2X service from the V2X application specific server) and online configuration (during the V2X UE is receiving the V2X service from the V2X application specific server).

9.1.2.2  Information flows  p. 32

The following information flows of configuration management service are applicable for the V2X applications:
The usage of the above information flows are clarified as below:
  • The VAL UE ID is the V2X UE ID;
  • VAL service ID is the V2X service ID; and
  • VAL UE configuration data is the V2X UE configuration data. The V2X UE configuration data includes:
    • V2X server USD information as specified in TS 23.285; and
    • V2X application server address information as specified in TS 23.285 and transport port for unicast.
Up

9.1.2.3  Procedures  p. 32

The following procedures of configuration management service are applicable for the V2X applications:
  • VAL UE configuration data specified in subclause 11.3.3 of TS 23.434.
    • Once the V2X UEs are connected to the serving PLMN, the V2X UE is configured with configuration data (e.g. local service information) for receiving V2X services.

9.1.3  Location management service  p. 32

9.1.3.1  General  p. 32

The VAE capabilities (VAE client and VAE server) utilize location management (e.g. network location of UEs) service procedures of SEAL to support V2X services.

9.1.3.2  Information flows  p. 32

The following information flows of location management service of SEAL as specified in TS 23.434 are applicable for the V2X applications:
The usage of the above information flows are clarified as below:
  • The identity is the V2X UE ID or V2X group ID;
  • The set of identities is the V2X UE ID;
  • The identity list or identities list is the list of V2X UE IDs; and
  • The VAL server is the VAE server.
Up

9.1.3.3  Procedures  p. 33

The following procedures of location management service of SEAL as specified in TS 23.434 are applicable for the V2X applications:
  • Event-triggered location reporting procedure specified in subclause 9.3.3;
  • On-demand location reporting procedure specified in subclause 9.3.4;
  • Client-triggered or VAL server-triggered location reporting procedure specified in clause 9.3.5;
  • Location reporting event triggers configuration cancel specified in subclause 9.3.6;
  • Location information subscription procedure specified in subclause 9.3.7;
  • Event-trigger location information notification procedure specified in subclause 9.3.8;
  • On-demand usage of location information procedure specified in subclause 9.3.9;
  • Obtaining UE(s) information at a location specified in clause 9.3.10;
Up

9.1.4  Identity management service  p. 33

9.1.4.1  General  p. 33

The VAE capabilities (VAE client and VAE server) utilizes identity management service procedures (e.g. authentication and authorization of UEs) of SEAL to support V2X services.

9.1.4.2  Information flows  p. 33

The information flows of identity management service are specified in subclause 12.3.2 of TS 23.434 and are applicable for the V2X applications.

9.1.4.3  Procedures  p. 33

The following procedures of identity management service are applicable for the V2X applications:

9.1.5  Key management service  p. 34

9.1.5.1  General  p. 34

The VAE capabilities (VAE client and VAE server) utilizes key management service procedures of SEAL to support V2X services.

9.1.5.2  Information flows  p. 34

The information flows of key management service are specified in subclause 13.3 of TS 23.434 and are applicable for the V2X applications.

9.1.5.3  Procedures  p. 34

The procedures of key management service are specified in subclause 13.3 of TS 23.434 and are applicable for the V2X applications.

9.1.6  Network resource management service  p. 34

9.1.6.1  General  p. 34

The VAE capabilities (VAE client and VAE server) utilizes network resource management service procedures of SEAL to support V2X services.

9.1.6.2  Information flows  p. 34

The following information flows of network resource management service of SEAL specified in TS 23.434 are applicable for the V2X applications:
Up

9.1.6.3  Procedures  p. 34

The following procedures of network resource management service of SEAL specified TS 23.434 are applicable for the V2X applications:
Up

Up   Top   ToC