3 Definitions, symbols and abbreviations

36.4433GPPEvolved Universal Terrestrial Radio Access Network (E-UTRAN)M2 Application Protocol (M2AP)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: M2AP consists of Elementary Procedures (Eps). An Elementary Procedure is a unit of interaction between eNBs and the MCE. 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 standalone procedures, which can be active in parallel. The usage of several M2AP Eps together or together with Eps from other interfaces is specified in stage 2 specifications (e.g. TS 36.300 [3] and TS 23.246 [8]).

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.

eNB MBMS M2AP ID: Unique identity, referencing the MBMS-service-associated logical M2-connection within an eNB.

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

MBMS E-RAB: denotes both, the data bearer established between the eNB and the UE(s) to transport MBMS data and the MBMS M1 data bearer.

MBMS-service-associated signalling: When M2AP messages associated to one MBMS service uses the MBMS-service-associated logical M2-connection for association of the message to the respective MBMS service in eNB and EPC.

MBMS-service-associated logical M2-connection: The MBMS-service-associated logical M2-connection uses the identities eNB MBMS M2AP ID and MCE MBMS M2AP ID. For a received M2AP message the MCE identifies the associated MBMS E-RAB based on the MCE MBMS M2AP ID IE and the eNB identifies the associated MBMS-RAB based on the eNB MBMS M2AP ID IE.

3.2 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].

MCCH Multicast Control Channel

PMCH Physical Multicast Channel

SC-PTM Single Cell Point to Multipoint