3 Definitions, symbols and abbreviations

36.4443GPPEvolved Universal Terrestrial Radio Access Network (E-UTRAN)M3 Application Protocol (M3AP)Release 17TS

3.1 Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].

Elementary Procedure: M3AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between MCEs and the EPC. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as stand alone procedures, which can be active in parallel. The usage of several M3AP EPs together or together with EPs from other interfaces is specified in stage 2 specifications (e.g. TS 23.246 [6] and TS 36.300 [3]).

An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used:

– Class 1: Elementary Procedures with response (success and/or failure).

– Class 2: Elementary Procedures without response.

For Class 1 EPs, the types of responses can be as follows:

Successful:

– A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response.

Unsuccessful:

– A signalling message explicitly indicates that the EP failed.

– On time supervision expiry (i.e. absence of expected response).

Successful and Unsuccessful:

– One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome.

Class 2 EPs are considered always successful.

MCE MBMS M3AP ID: Unique identity, referencing the MBMS-service-associated logical M3-connection within an MCE.

MME MBMS M3AP ID: Unique identity, referencing the MBMS-service-associated logical M3-connection within an MME.

MBMS E-RAB: An MBMS E-RAB refers to the concatenation of an M1 bearer and the corresponding radio bearer, as defined in TS 36.300 [3].

MBMS-service-associated signalling: When M3AP messages associated to one MBMS service uses the MBMS-service-associated logical M3-connection for association of the message to the MBMS service in MCE and EPC.

MBMS-service-associated logical M3-connection: The MBMS-service-associated logical M3-connection uses the identities MME MBMS M3AP ID and MCE MBMS M3AP ID. For a received MBMS service associated M3AP message the MME identifies the associated MBMS service based on the MME MBMS M3AP ID IE and the MCE identifies the associated MBMS service based on the MCE MBMS M3AP ID IE.

3.2 Symbols

Not applicable.

3.3 Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905 [1] 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 [1].

DL Downlink

E-RAB E-UTRAN Radio Access Bearer

eNB E-UTRAN NodeB

EP Elementary Procedure

EPC Evolved Packet Core

E-UTRAN Evolved UTRAN

GBR Guaranteed Bit Rate

GTP GPRS Tunneling Protocol

IE Information Element

MBMS Multimedia Broadcast Multicast Service

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MCE Multi-cell/multicast Coordination Entity

MME Mobility Management Entity

NAS Non-Access Stratum

PLMN Public Land Mobile Network

QoS Quality of Service

SC-PTM Single Cell Point to Multipoint

TEID Tunnel Endpoint Identifier

UE User Equipment

UL Uplink