Content for TS 29.468 Word version: 18.0.0

3.1 Definitions 3.2 Abbreviations 4.1 Reference Model 4.2 Functional Elements
...

1 Scope p. 6

This document defines the protocol for the MB2 reference point between the Group Communication Service Application Server (GCS AS) and the Broadcast-Multicast Service Centre (BM-SC).

The MB2 reference point and related stage 2 procedures are defined in TS 23.468 as part of the Group Communication System Enablers for LTE. The stage 1 requirements for Group Communication System Enablers are specified in TS 22.468.

2 References p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 22.468: "Group Communication System(GCSE)".

[3]

TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description".

[4]

TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); stage 2".

[5]

TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".

[6]

TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".

[7]

TS 29.212: "Policy and Charging Control (PCC); Reference points".

[8]

TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".

[9]

TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".

[10]

TS 33.246: "Security of Multimedia Broadcast/Multicast Service (MBMS)".

[11]

RFC 791: "Transmission Control Protocol".

[12]

RFC 768: "User Datagram Protocol".

[13]

RFC 2234: "Augmented BNF for syntax specifications".

[14] Void

[15]

RFC 4960: "Stream Control Transmission Protocol".

[16]

RFC 5719: "Updated IANA Considerations for Diameter Command Code Allocations".

[17]

RFC 5996: "The Internet Key Exchange (IKE)".

[18]

RFC 3947: "Negotiation of NAT-Traversal in the IKE".

[19]

RFC 3948: "UDP Encapsulation of IPsec ESP Packets".

[20]

RFC 4303: "IP Encapsulating Security Payload (ESP)".

[21]

RFC 6347: "Datagram Transport Layer Security Version 1.2".#

[22]

TS 23.007: "Restoration procedures".

[23]

TS 29.229: "Cx and Dx interfaces based on the Diameter protocol".

[24]

TS 36.300: "E-UTRA and E-UTRAN overall description; Stage 2".

[25]

RFC 7944: "Diameter Routing Message Priority".

[26]

RFC 8583: "Diameter Load Information Conveyance".

[27]

RFC 6733: "Diameter Base Protocol".

[28]

TS 23.285: "Architecture Enhancements for V2X services".

[29]

RFC 5795: "The Robust Header Compression (ROHC) Framework".

[30]

RFC 3095, "Robust Header Compression (ROHC): Framework and four profiles: RTP, UDP, ESP, and uncompressed"

[31]

RFC 6363: "Forward Error Correction (FEC) Framework,".

[32] Void.

[33]

TS 29.214: " Policy and Charging Control over Rx reference point".

3 Definitions, symbols and abbreviations p. 8

3.1 Definitions p. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply:

MBMS bearer:

The service provided by the EPS to deliver the same IP datagrams to multiple receivers in a designated location.

3.2 Abbreviations p. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

ARP

Allocation and Retention Priority

AVP

Attribute-Value Pair

BM-SC

Broadcast-Multicast Service Centre

DRMP

Diameter Routing Message Priority

DSCP

Differentiated Services Code Point

DTLS

Datagram Transport Layer Security

ESP

Encapsulating Security Payload

FEC

Forward Error Correction

GAA

GCS-Action-Answer

GAR

GCS-Action-Request

GCS

Group Communication Service

GCSE

Group Communication System Enablers

GCS AS

Group Communication Service Application Server

GNA

GCS-Notification-Answer

GNR

GCS-Notification-Request

MBMS-GW

MBMS Gateway

PCRF

Policy and Charging Rules Function

P-GW

PDN Gateway

ROHC

Robust Header Compression

TMGI

Temporary Mobile Group Identity

UDP

User Datagram Protocol

V2X

Vehicle-to-Everything

4 Architectural Overview p. 8

4.1 Reference Model p. 8

Figure 4.1-1 shows a high level reference model of the architectural elements relevant to understand the MB2 reference point. More complete reference models for GCSE are contained in TS 23.468.

Reproduction of 3GPP TS 29.468, Fig. 4.1-1: Reference Model

Figure 4.1-1: Reference Model

For the V2X Localized User Plane supported feature, the reference model in clause B.3 of TS 23.285 applies.

4.2 Functional Elements p. 9

4.2.1 Group Communication Service Application Server (GCS AS) p. 9

The GCS AS is defined in TS 23.468 and supports the following functionality:

Exchanging GC1 signalling with the UE.
Receiving unicast uplink data from the UE via the SGi reference point.
Delivery of data to all the UEs belonging to a group using unicast delivery over the SGi reference point and/or MBMS delivery over the MB2 reference point.
Support for service continuity procedures for a UE to switch between unicast delivery and MBMS delivery.
For MBMS delivery:
- MB2 C procedures defined in TS 23.468, for requesting the BM SC to activate, deactivate, modify an MBMS bearer, allocate/deallocate TMGI.
- Forwarding of data to be delivered via an MBMS bearer to the BM SC via the MB2 U reference point.

In addition to the functions defined in TS 23.468, an GCS AS which acts as a V2X Application Server may support the following functions:

For the V2X Localized User Plane supported feature, MB2 C procedures defined in subclause 5.4.2.2 of TS 23.285 for requesting the BM-SC to activate an MBMS bearer for local MBMS based MBMS data delivery.

In addition to the functions defined in TS 23.468, an GCS AS may take further actions based on the MBMS bearer status and diagnostic information notified by the BM-SC in the MB2 reference point.

4.2.2 Broadcast-Multicast Service Centre (BM-SC) p. 10

The BM SC is defined in TS 23.246, with additions related to the MB2 reference point in TS 23.468, and supports the following functionality:

MBMS Broadcast Mode procedures defined in TS 23.246 (stage 2) and in TS 29.061 (stage 3).
MB2 C procedures defined in TS 23.468, for activating, deactivating, modifying an MBMS bearer, allocating/deallocating TMGI and notifying the TMGI expiry or the MBMS Bearer condition to GCS AS.
SGmb procedures for controlling MBMS broadcast bearers defined in TS 29.061.
Reception of user data from the GCS AS via the MB2 U reference point and forwarding those data via the SGi mb reference point as described in TS 29.061.

In addition to the functions defined in TS 23.468, the BM-SC may support the following functions for V2X services:

For the V2X Localized User Plane supported feature, MB2 C procedures defined in subclause 5.4.2.2 of TS 23.285 for receiving Local MBMS information defined in TS 23.285 from an GCS AS which acts as a V2X Application Server.

In addition to the functions defined in TS 23.468, the BM-SC may notify the MBMS bearer status and diagnostic information to the GCS AS.