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.287  Word version:  18.4.0

Top   Top   Up   Prev   Next
1…   4…   4.2.1.2…   4.2.2…   4.3…   5…   5.2…   5.3…   5.4…   5.4.2…   5.5   5.6…   5.7…   5.10…   6…   6.2…   6.3…   6.3.3…   6.4…   6.5…   A… 
5.10 MBS Service Description for V2X use  5.10.1 General  5.10.2 MBS session announcement for V2X communication  5.10.3 MBS session announcement for V2X Application Server Discovery  5.11 Support of NR PC5 Carrier Aggregation operations 
...

 

5.10  MBS Service Description for V2X use |R18|  p. 40

5.10.1  General  p. 40

The announced service information for V2X use should follow the guidance in clauses 5.10.2 and 5.10.3.

5.10.2  MBS session announcement for V2X communication  p. 41

As the V2X Application Server is out of scope of 3GPP, the exact information to be included in the MBS session announcement for V2X communication cannot be controlled. However, the V2X Application Server should make sure that at least the information listed in Table 5.10.2-1 is included in the MBS session announcement it provides.
The V2X message formats are handled by upper layer via Session Description Protocol (SDP).
Information element Description
TMGI (NOTE 4)TMGI information
MBS Service TypeIndicates whether the MBS Session for the service is multicast or broadcast.
MBS service area information (NOTE 1)Identifies the service area for the MBS session.
Frequency and/or MBS Frequency Selection Area (FSA) ID(s)
(NOTE 3)		Identification of frequency if multi carrier support is provided
SDP information (NOTE 2)SDP with IP multicast address and port number used for V2X communication via MBS.
Depending on the V2X application, the V2X message can be carried directly on top of UDP, without any streaming protocols.
NOTE 1:
MBS service area information is optional for multicast services.
NOTE 2:
Typical V2X application does not require Codec information in the SDP information.
NOTE 3:
The Frequency and/or FSA ID(s) are optional and only apply to broadcast MBS sessions.
NOTE 4:
In addition to TMGI, NID is used in case of SNPN, as specified in TS 23.247.
Up

5.10.3  MBS session announcement for V2X Application Server Discovery  p. 41

The MBS session announcement for V2X Application Server Discovery is used to configure the UE for receiving local V2X Application Server information when it is provided over broadcast MBS session, as specified in clause 6.4.2.
The local Service Information contained in the broadcast is as described in clause 6.4.2, and should include similar information defined in clause 5.1.3.1.
Information element Description
TMGI (NOTE 1)TMGI information
MBS Service TypeIndicates that the MBS Session for the service is broadcast.
MBS service area informationIdentifies the service area for the MBS session.
Frequency and/or MBS Frequency Selection Area (FSA) ID(s)Identification of frequency if multi carrier support is provided.
SDP informationSDP with IP multicast address and port number used for V2X Application Server discovery via MBS.
The content of the message carries the local Service Information and should include following information:
  • Mapping of the V2X service types to V2X Application Server address information (consisting of IP address/FQDN and transport layer port#) for unicast, and MBS session announcement for V2X communication via MBS.
NOTE 1:
In addition to TMGI, NID is used in case of SNPN, as specified in TS 23.247.
Up

5.11  Support of NR PC5 Carrier Aggregation operations |R18|  p. 42

For NR based unicast, groupcast and broadcast mode communication over PC5 reference point, PC5 Carrier Aggregation (CA) operations are supported.
The V2X layer provides the radio frequencies to the AS layer based on the configuration as described in clause 5.1.2.1.
The V2X layer provides the NR eTx Profiles to the AS layer e.g. when providing other information such as the radio frequencies for the PC5 QoS Flow for transmission. When there is no NR eTx Profile available to be mapped for the PC5 QoS Flow for transmission, the V2X layer does not provide NR eTx Profile to the AS layer.
Support for NR PC5 CA operations in the AS layer is specified in TS 38.300.
For broadcast or groupcast, the AS layer determines whether the NR PC5 CA operation is needed, e.g. based on the NR eTx Profile, the radio frequencies for the PC5 QoS Flow for transmission provided by the V2X layer.
For unicast, two UEs exchange SL CA related capability in the AS layer for the NR PC5 CA operation.
Up

Up   Top   ToC