9 Elements for M2AP Communication
36.4433GPPEvolved Universal Terrestrial Radio Access Network (E-UTRAN)M2 Application Protocol (M2AP)Release 17TS
9.1 Message Functional Definition and Content
9.1.1 General
Sub clauses 9.1 and 9.2 describe the structure of the messages and information elements required for the M2AP protocol in tabular format. Sub clause 9.3 provides the corresponding ASN.1 definition.
The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality.
9.1.1 Message Contents
9.1.1.1 Presence
All information elements in the message descriptions below are marked mandatory, optional or conditional according to table 4.
Table 4. Meaning of abbreviations used in M2AP messages
Abbreviation |
Meaning |
M |
Ies marked as Mandatory (M) shall always be included in the message. |
O |
Ies marked as Optional (O) may or may not be included in the message. |
C |
Ies marked as Conditional (C) shall be included in a message only if the condition is satisfied. Otherwise the IE shall not be included. |
9.1.1.2 Criticality
Each Information Element or Group of Information Elements may have criticality information applied to it.
Following cases are possible:
Table 5. Meaning of content within “Criticality” column
Abbreviation |
Meaning |
– |
No criticality information is applied explicitly. |
YES |
Criticality information is applied. This is usable only for non-repeatable Ies. |
GLOBAL |
The IE and all its repetitions together have one common criticality information. This is usable only for repeatable Ies. |
EACH |
Each repetition of the IE has its own criticality information. It is not allowed to assign different criticality values to the repetitions. This is usable only for repeatable Ies. |
9.1.1.3 Range
The Range column indicates the allowed number of copies of repetitive Ies/IE groups.
9.1.1.4 Assigned Criticality
This column provides the actual criticality information as defined in subclause 10.3.2 in TS 36.413 [4], if applicable.
9.1.2 MBMS SESSION START REQUEST
This message is sent by the MCE to establish an MBMS-service-associated logical M2-connection.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
reject |
||
TMGI |
M |
9.2.3.3 |
YES |
reject |
||
MBMS Session Identity |
O |
9.2.3.4 |
YES |
ignore |
||
MBMS Service Area |
M |
9.2.3.6 |
YES |
reject |
||
TNL Information |
1 |
YES |
reject |
|||
>IP Multicast Address |
M |
IP Address 9.2.2.1 |
– |
|||
>IP Source Address |
M |
IP Address 9.2.2.1 |
– |
|||
>GTP DL TEID |
M |
GTP-TEID |
– |
|||
Alternative TNL Information |
O |
YES |
ignore |
|||
>Alternative IP Multicast Address |
M |
IP Address 9.2.2.1 |
– |
|||
>Alternative IP Source Address |
M |
IP Address 9.2.2.1 |
– |
|||
>GTP DL TEID |
M |
GTP-TEID |
Shall be set to same value as the GTP DL TEID IE of the TNL Information IE. |
– |
||
SC-PTM information |
O |
9.2.1.22 |
YES |
reject |
9.1.3 MBMS SESSION START RESPONSE
This message is sent by the eNB to report the successful outcome of the request from the MBMS SESSION START REQUEST message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
ignore |
||
eNB MBMS M2AP ID |
M |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.4 MBMS SESSION START FAILURE
This message is sent by the eNB to report the unsuccessful outcome of the request from the MBMS SESSION START REQUEST message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
ignore |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.5 MBMS SESSION STOP REQUEST
This message is sent by the MCE to release the corresponding MBMS E-RAB and the MBMS-service-associated logical M2-connection.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
reject |
||
eNB MBMS M2AP ID |
M |
9.2.3.2 |
YES |
reject |
9.1.6 MBMS SESSION STOP RESPONSE
This message is sent by the eNB to acknowledge the MBMS SESSION STOP message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
ignore |
||
eNB MBMS M2AP ID |
M |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.7 MBMS SCHEDULING INFORMATION
This message is sent by the MCE to provide MCCH related information to the eNB.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCCH Update Time |
M |
9.2.1.19 |
YES |
reject |
||
MBSFN Area Configuration List |
1 |
YES |
reject |
|||
>MBSFN Area Configuration Item Ies |
1 to <maxnoofMBSFNareas> |
|||||
>>PMCH Configuration List |
1 |
YES |
reject |
|||
>>>PMCH Configuration Item Ies |
0 to <maxnoofPMCHsperMBSFNarea> |
EACH |
reject |
|||
>>>>PMCH Configuration |
M |
9.2.1.8 |
– |
|||
>>>>MBMS Session List per PMCH |
M |
9.2.1.9 |
– |
|||
>>Subframes Configuration List |
1 |
YES |
reject |
|||
>>>Subframes Configuration Item Ies |
1 to <maxnoofMBSFN-Allocations> |
EACH |
reject |
|||
>>>>MBSFN Subframe Configuration |
M |
9.2.1.17 |
– |
|||
>>Common Subframe Allocation Period |
M |
9.2.1.18 |
YES |
reject |
||
>>MBSFN Area ID |
M |
9.2.1.14 |
YES |
reject |
||
>>MBMS Suspension Notification List |
0..1 |
YES |
ignore |
|||
>>>MBMS Suspension Notification Item Ies |
1 to <maxnoofPMCHsperMBSFNarea> |
EACH |
ignore |
|||
>>>>SFN |
M |
INTEGER (0..1023) |
SFN of the first radio frame containing the information that the MBMS session(s) are to be suspended. |
– |
– |
|
>>>>MBMS Sessions To Be Suspended List per PMCH |
1 |
– |
– |
|||
>>>>>MBMS Sessions To Be Suspended List per PMCH Item |
1 to <maxnoofSessionsPerPMCH> |
– |
– |
|||
>>>>>>MBMS Service Identity |
M |
TMGI |
– |
– |
Range bound |
Explanation |
maxnoofMBSFNareas |
Maximum no. of MBSFN areas served by a single eNB. The value for maxnoofMBSFNareas is 256. |
maxnoofPMCHsperMBSFNarea |
Maximum no. of PMCHs possible per MBSFN .The value for maxnoofMCHsperMBSFNarea is 15. |
maxnoofMBSFN-Allocations |
Maximum no. of MBSFN frame allocations with different offset. The value for maxnoofMBSFN-Allocations is 8. |
maxnoofSessionsPerPMCH |
Maximum no. of Sessions per PMCH. The value for maxnoofSessionsPerPMCH is 29. |
9.1.8 MBMS SCHEDULING INFORMATION RESPONSE
This message is sent by the eNB to acknowledge the MBMS SCHEDULING INFORMATION message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.9 RESET
This message is either sent by the eNB or the MCE and is used to request the M2 interface or part of M2 interface to be reset.
Direction: eNB MCE, MCE eNB
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
CHOICE Reset Type |
M |
YES |
reject |
|||
>M2 interface |
||||||
>>Reset All |
M |
ENUMERATED (Reset all, …) |
– |
– |
||
>Part of M2 interface |
||||||
>>MBMS-Service-associated logical M2-connection list |
1 |
– |
– |
|||
>>>MBMS-Service –associated logical M2-connection Item |
1 to < maxNrOfIndividualM2ConnectionsToReset > |
EACH |
reject |
|||
>>>>eNB MBMS M2AP ID |
O |
9.2.3.2 |
– |
– |
||
>>>>MCE MBMS M2AP ID |
O |
9.2.3.1 |
– |
– |
Range bound |
Explanation |
maxNrOfIndividualM2ConnectionsToReset |
Maximum no. of MBMS-Service-associated logical M2-connections allowed to reset in one message. Value is 256. |
9.1.10 RESET ACKNOWLEDGE
This message is sent as a response to the RESET message.
Direction : MCE eNB, eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MBMS-Service-associated logical M2-connection list |
0..1 |
YES |
ignore |
|||
>MBMS-Service –associated logical M2-connection Item |
1 to < maxNrOfIndividualM2ConnectionsToReset > |
EACH |
ignore |
|||
>>eNB MBMS M2AP ID |
O |
9.2.3.2 |
– |
– |
||
>>MCE MBMS M2AP ID |
O |
9.2.3.1 |
– |
– |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
Range bound |
Explanation |
maxNrOfIndividualM2ConnectionsToReset |
Maximum no. of MBMS-Service-associated logical M2-connections allowed to reset in one message. Value is 256. |
9.1.11 M2 SETUP REQUEST
This message is sent by the eNB to initiate the M2 interface instance.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Global eNB ID |
M |
9.2.1.10 |
YES |
reject |
||
eNB Name |
O |
Printable String (1..150,…) |
YES |
ignore |
||
eNB MBMS Configuration data per cell |
1 |
YES |
reject |
|||
>eNB MBMS Configuration data Item Ies |
1 to <maxnoofCells> |
EACH |
reject |
|||
>>eNB MBMS Configuration data Item |
M |
9.2.1.12 |
– |
Range bound |
Explanation |
maxnoofCells |
Maximum no. of cells that may be served by an eNB. The value for maxnoofCells is 256. |
9.1.12 M2 SETUP RESPONSE
This message is sent by the MCE to complete the initiation of an M2 interface instance, providing MCCH related BCCH information.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Global MCE ID |
M |
9.2.1.16 |
YES |
reject |
||
MCE Name |
O |
Printable String (1..150,…) |
YES |
ignore |
||
MCCH related BCCH Configuration data per MBSFN area |
1 |
YES |
reject |
|||
>MCCH related BCCH Configuration data Item Ies |
1 to <maxnoofMBSFNareas> |
EACH |
reject |
|||
>> MCCH related BCCH Configuration Item |
M |
9.2.1.13 |
– |
|||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
||
MCCH related BCCH Extended Configuration data per MBSFN area |
0..1 |
YES |
reject |
|||
>MCCH related BCCH Extended Configuration data Item Ies |
1 to <maxnoofMBSFNareas> |
EACH |
reject |
|||
>>MCCH related BCCH Extended Configuration Item |
M |
9.2.1.27 |
– |
Range bound |
Explanation |
maxnoofMBSFNareas |
Maximum no. of MBSFN areas served by a single eNB. The value for maxnoofMBSFNareas is 256. |
9.1.13 M2 SETUP FAILURE
This message is sent by the MCE to indicate non acceptance of the M2 Setup Request.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
Time To Wait |
O |
9.2.1.15 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.14 ENB CONFIGURATION UPDATE
This message is sent by the eNB to indicate that application level configuration data has changed in the eNB.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Global eNB ID |
O |
9.2.1.10 |
YES |
reject |
||
eNB Name |
O |
Printable String (1..150,…) |
YES |
ignore |
||
eNB MBMS Configuration data per cell |
0..1 |
YES |
reject |
|||
>eNB MBMS Configuration data per cell Item Ies |
1 to <maxnoofCells> |
EACH |
reject |
|||
>>CHOICE MBMS Configuration Update |
M |
|||||
>>>Configuration Data |
||||||
>>>>eNB MBMS Configuration data Item |
9.2.1.12 |
|||||
>>>E-CGI |
||||||
>>>>E-UTRAN CGI |
9.2.1.11 |
Range bound |
Explanation |
maxnoofCells |
Maximum no. of cells that may be served by an eNB. The value for maxnoofCells is 256. |
9.1.15 ENB CONFIGURATION UPDATE ACKNOWLEDGE
This message acknowledges the ENB CONFIGURATION UPDATE message.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCCH related BCCH Configuration data per MBSFN area |
0..1 |
YES |
reject |
|||
>MCCH related BCCH Configuration data Item Ies |
1 to <maxnoofMBSFNareas> |
EACH |
reject |
|||
>>MCCH related BCCH Configuration Item |
M |
9.2.1.13 |
– |
|||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
||
MCCH related BCCH Extended Configuration data per MBSFN area |
0..1 |
YES |
reject |
|||
>MCCH related BCCH Extended Configuration data Item Ies |
1 to <maxnoofMBSFNareas> |
EACH |
reject |
|||
>>MCCH related BCCH Extended Configuration Item |
M |
9.2.1.27 |
– |
Range bound |
Explanation |
maxnoofMBSFNareas |
Maximum no. of MBSFN areas served by a single eNB. The value for maxnoofMBSFNareas is 256. |
9.1.16 ENB CONFIGURATION UPDATE FAILURE
This message is sent by the MCE to indicate non acceptance of the eNB Configuration Update.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
Time To Wait |
O |
9.2.1.15 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.17 MCE CONFIGURATION UPDATE
This message is sent by the MCE to indicate that application level configuration data has changed in the MCE.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Global MCE ID |
O |
9.2.1.16 |
YES |
reject |
||
MCE Name |
O |
Printable String (1..150,…) |
YES |
ignore |
||
MCCH related BCCH Configuration data per MBSFN area |
0..1 |
YES |
reject |
|||
>MCCH related BCCH Configuration data Item Ies |
1 to <maxnoofMBSFNareas> |
EACH |
reject |
|||
>>MCCH related BCCH Configuration Item |
M |
9.2.1.13 |
– |
|||
MCCH related BCCH Extended Configuration data per MBSFN area |
0..1 |
YES |
reject |
|||
>MCCH related BCCH Extended Configuration data Item Ies |
1 to <maxnoofMBSFNareas> |
EACH |
reject |
|||
>>MCCH related BCCH Extended Configuration Item |
M |
9.2.1.27 |
– |
Range bound |
Explanation |
maxnoofMBSFNareas |
Maximum no. of MBSFN areas served by a single eNB. The value for maxnoofMBSFNareas is 256. |
9.1.18 MCE CONFIGURATION UPDATE ACKNOWLEDGE
This message acknowledges the MCE CONFIGURATION UPDATE message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.19 MCE CONFIGURATION UPDATE FAILURE
This message is sent by the eNB to indicate non acceptance of the MCE Configuration Update.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
Time To Wait |
O |
9.2.1.15 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.20 ERROR INDICATION
This message is sent by both the MCE and the eNB and is used to indicate that some error has been detected in the node.
Direction: MCE eNB and eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
ignore |
||
MCE MBMS M2AP ID |
O |
9.2.3.1 |
YES |
ignore |
||
eNB MBMS M2AP ID |
O |
9.2.3.2 |
YES |
ignore |
||
Cause |
O |
9.2.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.21 MBMS SESSION UPDATE REQUEST
This message is sent by the MCE to the eNB in order to inform of the change of session characteristics e.g. service area of one MBMS service session.
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
reject |
||
eNB MBMS M2AP ID |
M |
9.2.3.2 |
YES |
reject |
||
TMGI |
M |
9.2.3.3 |
YES |
reject |
||
MBMS Session Identity |
O |
9.2.3.4 |
YES |
ignore |
||
MBMS Service Area |
O |
9.2.3.6 |
YES |
ignore |
||
TNL Information |
O |
YES |
reject |
|||
>IP Multicast Address |
M |
9.2.2.1 |
– |
|||
>IP Source Address |
M |
IP Address 9.2.2.1 |
– |
|||
>GTP DL TEID |
M |
GTP-TEID |
– |
|||
SC-PTM information |
O |
9.2.1.22 |
YES |
reject |
9.1.22 MBMS SESSION UPDATE RESPONSE
This message is sent by the eNB to report the successful outcome of the request from the MBMS SESSION UPDATE REQUEST message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
ignore |
||
eNB MBMS M2AP ID |
M |
9.2.3.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.23 MBMS SESSION UPDATE FAILURE
This message is sent by the eNB to report the unsuccessful outcome of the request from the MBMS SESSION UPDATE REQUEST message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCE MBMS M2AP ID |
M |
9.2.3.1 |
YES |
ignore |
||
eNB MBMS M2AP ID |
M |
9.2.3.2 |
YES |
ignore |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.24 MBMS SERVICE COUNTING REQUEST
This message is sent by the MCE to request the eNB to report the number of connected mode Ues that are receiving or interested in the MBMS service(s).
Direction: MCE eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MCCH Update Time |
M |
9.2.1.19 |
YES |
reject |
||
MBSFN Area ID |
M |
9.2.1.14 |
YES |
reject |
||
MBMS Counting Request Session |
M |
YES |
reject |
|||
>MBMS Counting Request Session Item |
1 to <maxnoofcountingservice> |
EACH |
reject |
|||
>>TMGI |
M |
9.2.3.3 |
– |
– |
Range bound |
Explanation |
maxnoofcountingservice |
Maximum no. of the services that are counted by RAN. The value for maxnoofcountingservice is 16. |
9.1.25 MBMS SERVICE COUNTING RESPONSE
This message is sent by the eNB to acknowledge the MBMS SERVICE COUNTING REQUEST message.
Direction: eNBMCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.26 MBMS SERVICE COUNTING FAILURE
This message is sent by the eNB to report the unsuccessful outcome of the request from the MBMS SERVICE COUNTING REQUEST message.
Direction: eNB MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
Cause |
M |
9.2.1.2 |
YES |
ignore |
||
Criticality Diagnostics |
O |
9.2.1.7 |
YES |
ignore |
9.1.27 MBMS SERVICE COUNTING RESULTS REPORT
This message is sent by the eNB to report the number of connected mode Ues that are receiving or interested in the MBMS service(s) as indicated in the MBMS SERVICE COUNTING REQUEST message.
Direction: eNBMCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MBSFN Area ID |
M |
9.2.1.14 |
YES |
reject |
||
MBMS Counting Result List |
M |
YES |
reject |
|||
>MBMS Counting Result Item |
1 to <maxnoofcountingservice> |
EACH |
reject |
|||
>>TMGI |
M |
9.2.3.3 |
– |
|||
>>Counting Result |
M |
9.2.1.21 |
– |
Range bound |
Explanation |
Maxnoofcountingservice |
Maximum no. of the services that are counted by RAN. The value for maxnoofcountingservice is 16. |
9.1.28 MBMS OVERLOAD NOTIFICATION
This message is sent by the eNB to notify the MCE about MBMS overload status.
Direction: eNBMCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
---|---|---|---|---|---|---|
Message Type |
M |
9.2.1.1 |
YES |
reject |
||
MBSFN Area ID |
M |
9.2.1.14 |
YES |
reject |
||
Overload Status Per PMCH List |
1 |
YES |
reject |
|||
>Overload Status Per PMCH Item Ies |
1..<maxnoofPMCHsperMBSFNarea> |
– |
– |
|||
>>PMCH Overload Status |
M |
ENUMERATED (Normal, Overload, …) |
YES |
reject |
||
>>Active MBMS Session List |
0..1 |
YES |
reject |
|||
>>>Active MBMS Session Item Ies |
1 to <maxnoofSessionsPerPMCH> |
– |
– |
|||
>>>>MBMS Service Identity |
M |
TMGI |
YES |
reject |
Range bound |
Explanation |
maxnoofPMCHsperMBSFNarea |
Maximum no. of PMCHs possible per MBSFN .The value is 15. |
maxnoofSessionsPerPMCH |
Maximum no. of Sessions per PMCH. The value for maxnoofSessionsPerPMCH is 29. |
9.2 Information Element Definitions
9.2.1 Radio Network Layer Related Ies
9.2.1.1 Message Type
The Message Type IE uniquely identifies the message being sent. It is mandatory for all messages.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Message Type |
||||
>Procedure Code |
M |
INTEGER (0..255) |
||
>Type of Message |
M |
CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, …) |
9.2.1.2 Cause
The purpose of the Cause IE is to indicate the reason for a particular event for the M2AP protocol.
IE/Group Name |
Presence |
Range |
IE Type and Reference |
Semantics Description |
CHOICE Cause Group |
M |
|||
>Radio Network Layer |
||||
>>Radio Network Layer Cause |
M |
ENUMERATED Unspecified, Invalid QoS combination, Not supported QCI value) |
||
>Transport Layer |
||||
>>Transport Layer Cause |
M |
ENUMERATED |
||
>NAS |
||||
>>NAS Cause |
M |
ENUMERATED (Unspecified, |
||
>Protocol |
||||
>>Protocol Cause |
M |
ENUMERATED |
||
>Misc |
||||
>>Miscellaneous Cause |
M |
ENUMERATED |
The meaning of the different cause values is described in the following table. In general, “not supported” cause values indicate that the related capability is missing. On the other hand, “not available” cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action.
Radio Network Layer cause |
Meaning |
Unknown or already allocated MCE MBMS M2AP ID |
The action failed because the MCE MBMS M2AP ID is either unknown, or (for a first message received at the eNB) is known and already allocated to an existing MBMS service related context. |
Unknown or already allocated eNB MBMS M2AP ID |
The action failed because the eNB MBMS M2AP ID is either unknown, or (for a first message received at the MCE) is known and already allocated to an existing context. |
Unknown or inconsistent pair of MBMS M2AP IDs |
The action failed because both MBMS M2AP IDs are unknown, or are known but do not define a single MBMS context. |
Radio resources not available |
No requested radio resources are available |
Interaction with other procedure |
The action is due to an ongoing interaction with another procedure |
Unspecified |
Sent for radio network layer cause when none of the specified cause values applies |
Invalid QoS combination |
The action was failed because of invalid QoS combination. |
Not supported QCI Value |
The E-RAB setup failed because the requested QCI is not supported. |
Transport Layer cause |
Meaning |
Transport Resource Unavailable |
The required transport resources are not available. |
Unspecified |
Sent for transport network layer cause when none of the specified cause values applies. |
NAS cause |
Meaning |
Unspecified |
Sent for NAS cause when none of the specified cause values applies. |
Protocol cause |
Meaning |
Transfer Syntax Error |
The received message included a transfer syntax error. |
Abstract Syntax Error (Reject) |
The received message included an abstract syntax error and the concerning criticality indicated “reject”. |
Abstract Syntax Error (Ignore And Notify) |
The received message included an abstract syntax error and the concerning criticality indicated “ignore and notify”. |
Message Not Compatible With Receiver State |
The received message was not compatible with the receiver state. |
Semantic Error |
The received message included a semantic error. |
Abstract Syntax Error (Falsely Constructed Message) |
The received message contained Ies or IE groups in wrong order or with too many occurrences. |
Unspecified |
Sent for protocol cause when none of the specified cause values applies. |
Miscellaneous cause |
Meaning |
Control Processing Overload |
Control processing overload. |
Hardware Failure |
Action related to hardware failure |
O&M Intervention |
The action is due to O&M intervention. |
Unspecified |
Sent when none of the above cause values applies and the cause is not related to any of the categories Radio Network Layer, Transport Network Layer, NAS or Protocol. |
9.2.1.3 Void
9.2.1.4 Void
9.2.1.5 Void
9.2.1.6 Void
9.2.1.7 Criticality Diagnostics
The Criticality Diagnostics IE is sent by the eNB or the MCE when parts of a received message have not been comprehended or were missing, or if the message contained logical errors. When applicable, it contains information about which Ies were not comprehended or were missing.
For further details on how to use the Criticality Diagnostics IE, (see section 10 in TS 36.413 [4]).
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Procedure Code |
O |
INTEGER (0..255) |
Procedure Code is to be used if Criticality Diagnostics is part of Error Indication procedure, and not within the response message of the same procedure that caused the error. |
|
Triggering Message |
O |
ENUMERATED (initiating message, successful outcome, unsuccessful outcome) |
The Triggering Message is used only if the Criticality Diagnostics is part of Error Indication procedure. |
|
Procedure Criticality |
O |
ENUMERATED (reject, ignore, notify) |
This Procedure Criticality is used for reporting the Criticality of the Triggering message (Procedure). |
|
Information Element Criticality Diagnostics |
0 to <maxnooferrors> |
|||
>IE Criticality |
M |
ENUMERATED(reject, ignore, notify) |
The IE Criticality is used for reporting the criticality of the triggering IE. The value ‘ignore’ shall not be used. |
|
>IE ID |
M |
INTEGER (0..65535) |
The IE ID of the not understood or missing IE. |
|
>Type of Error |
M |
ENUMERATED(not understood, missing, …) |
Range bound |
Explanation |
maxnooferrors |
Maximum no. of IE errors allowed to be reported with a single message. The value for maxnooferrors is 256. |
9.2.1.8 PMCH Configuration
This information element provided PMCH configuration related content for MCCH.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
Allocated Subframes End |
M |
INTEGER (0..1535) |
Encoded as the sf-AllocEnd IE in TS 36.331 [11]. |
− |
− |
|
Modulation and Coding Scheme |
M |
INTEGER (0..28) |
Encoded as the dataMCS IE in TS 36.331 [11]. |
− |
− |
|
MCH Scheduling Period |
M |
ENUMERATED (rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024) |
Encoded as the mch-SchedulingPeriod IE in TS 36.331 [11]. |
− |
− |
|
Modulation and Coding Scheme 2 |
O |
INTEGER (0..27) |
Encoded as the t2 in the dataMCS IE in TS 36.331 [11]. If this IE is present, the value signalled in the Modulation and Coding Scheme IE is ignored. |
YES |
reject |
|
MCH Scheduling Period Extended |
O |
ENUMERATED (rf4, …) |
Encoded as the mch-SchedulingPeriod-r12 IE in TS 36.331 [11]. If this IE is present, the value signalled in the MCH Scheduling Period IE is ignored. |
YES |
reject |
|
MCH Scheduling Period Extended 2 |
O |
ENUMERATED (rf1, rf2, …) |
Encoded as the mch-SchedulingPeriod-v14x0 IE in TS 36.331 [11]. If this IE is present, the value signalled in the MCH Scheduling Period IE is ignored. |
YES |
reject |
9.2.1.9 MBMS Session List per PMCH
This information element provided PMCH configuration related content for MCCH.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBMS Session List per PMCH Item Ies |
1 to <maxnoofSessionsPerPMCH> |
|||
>MBMS Service Identity |
M |
TMGI |
||
>LCID |
M |
INTEGER (0..28) |
Logical Channel Identity. |
Range bound |
Explanation |
maxnoofSessionsPerPMCH |
Maximum no. of Sessions per PMCH. The value for maxnoofSessionsPerPMCH is 29. |
9.2.1.10 Global eNB ID
This information element is used to globally identify an eNB (see TS 36.401 [2]).
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PLMN Identity |
M |
9.2.3.7 |
||
CHOICE eNB ID |
M |
|||
>eNB ID |
||||
>>Macro eNB ID |
BIT STRING (20) |
Equal to the 20 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see section 9.2.1.11) of each cell served by the eNB. |
||
>Short Macro eNB ID |
||||
>>Short Macro eNB ID |
M |
BIT STRING (SIZE(18)) |
Equal to the 18 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see section 9.2.1.11) of each cell served by the eNB. |
|
>Long Macro eNB ID |
||||
>>Long Macro eNB ID |
M |
BIT STRING (SIZE(21)) |
Equal to the 21 leftmost bits of the Cell Identity IE contained in the E-UTRAN CGI IE (see section 9.2.1.11) of each cell served by the eNB. |
9.2.1.11 E-UTRAN CGI
This information element is used to globally identify a cell (see TS 36.401 [2]).
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PLMN Identity |
M |
9.2.3.7 |
||
Cell Identity |
M |
BIT STRING (28) |
The 20 leftmost bits of the Cell Identity correspond to the eNB ID (Global eNB ID IE defined in section 9.2.1.10). |
9.2.1.12 eNB MBMS Configuration data Item
This information element provides MBMS related configuration information from the eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
E-UTRAN CGI |
M |
9.2.1.11 |
||
MBSFN Synchronisation Area Id |
M |
9.2.1.20 |
||
MBMS Service Area List |
1 |
|||
>MBMS Service Area Item |
1 to <maxnoofMBMSServiceAreasPerCell> |
|||
>>MBMS Service Area |
M |
9.2.3.6 |
Range bound |
Explanation |
maxnoofMBMSServiceAreasPerCell |
Maximum no. of Service Areas per cell. The value for maxnoofMBMSServiceAreasPerCell is 256. |
9.2.1.13 MCCH related BCCH Configuration Item
This information element provides MCCH related BCCH configuration information to the eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
MBSFN Area Id |
M |
9.2.1.14 |
− |
− |
||
PDCCH Length |
M |
ENUMERATED (s1, s2,…) |
This IE is encoded along the number of OFDM symbols for PDCCH as of table 6.7-1. In TS 36.211 [12]. |
− |
− |
|
Repetition Period |
M |
ENUMERATED (rf32, rf64, rf128, rf256) |
The same encoding as the mcch-RepetitionPeriod IE in the mcch-Config IE as specified in TS 36.331 [11]. |
− |
− |
|
Repetition Period Extended |
O |
ENUMERATED (rf1, rf2, rf4, rf8, rf16, …) |
The same encoding as the mcch-RepetitionPeriod-v14x0 IE in the mcch-Config IE as specified in TS 36.331 [11]. If this IE is present, the value signalled in the Repetition Period IE is ignored. |
YES |
reject |
|
Offset |
M |
INTEGER (0..10) |
The same encoding as the mcch-Offset in mcch-Config IE as specified in TS 36.331 [11]. |
− |
− |
|
Modification Period |
M |
ENUMERATED (rf512, rf1024) |
The same encoding as the mcch-ModificationPeriod IE in the mcch-Config IE as specified in TS 36.331 [11]. |
− |
− |
|
Modification Period Extended |
O |
ENUMERATED (rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, …) |
The same encoding as the mcch-ModificationPeriod-v14x0 IE in the mcch-Config IE as specified in TS 36.331 [11]. If this IE is present, the value signalled in the Modification Period IE is ignored. |
YES |
reject |
|
Subframe Allocation Info |
M |
BIT STRING (SIZE(6)) |
The same encoding as the sf-AllocInfo IE specified in TS 36.331 [11]. |
− |
− |
|
Modulation and Coding Scheme |
M |
ENUMERATED (n2, n7, n13, n19) |
The same encoding as the signallingMCS IE specified in TS 36.331 [11]. |
− |
− |
|
Cell Information List |
0..1 |
|||||
>Cell Information |
1 to <maxnoofCells> |
|||||
>>E-UTRAN CGI |
M |
9.2.1.11 |
− |
− |
||
>>Cell Reservation Info |
M |
ENUMERATED (reservedCell, nonReservedCell, …) |
− |
− |
||
Subcarrier Spacing MBMS |
O |
ENUMERATED (khz-7dot5, khz-1dot25, …) |
Semantics along the definition of the subcarrierSpacingMBMS-r14 IE as specified in TS 36.331 [11]. |
YES |
reject |
Range bound |
Explanation |
maxnoofCells |
Maximum no. of cells that may be served by an eNB. The value for maxnoofCells is 256. |
9.2.1.14 MBSFN Area Id
This IE defines the MBSFN Area Id.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBSFN Area Id |
M |
INTEGER (0..255) |
The same encoding as the mbsfn-AreaId IE specified in TS 36.331 [11]. |
9.2.1.15 Time to Wait
This IE defines the minimum allowed waiting time.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Time to Wait |
M |
ENUMERATED(1s, 2s, 5s, 10s, 20s, 60s,…) |
9.2.1.16 Global MCE ID
This IE is used to globally identify an MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PLMN Identity |
M |
9.2.3.8 |
||
MCE ID |
M |
OCTET STRING (SIZE(2)) |
9.2.1.17 MBSFN Subframe Configuration
This IE indicates the MBSFN Subframe Configuration, as defined in TS 36.331 [11].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Radio Frame Allocation Period |
M |
ENUMERATED (n1, n2, n4, n8, n16, n32) |
Semantics along the IE definition in TS 36.331 [11]. |
|
Radio Frame Allocation Offset |
M |
INTEGER (0..7) |
Semantics along the IE definition in TS 36.331 [11]. |
|
CHOICE Subframe Allocation |
M |
|||
>One Frame |
||||
>>One Frame Item |
M |
BIT STRING (SIZE(6)) |
Semantics along the IE definition in TS 36.331 [11]. |
|
>Four Frames |
||||
>>Four Frame Item |
M |
BIT STRING (SIZE(24)) |
Semantics along the IE definition in TS 36.331 [11]. |
|
CHOICE Subframe Allocation Extended |
O |
|||
>One Frame Extension |
||||
>>One Frame Extension Item |
M |
BIT STRING (SIZE(2)) |
Semantics along the definition of the MBSFN-SubframeConfig-v1430 IE as specified in TS 36.331 [11]. |
|
>Four Frames Extension |
||||
>>Four Frame Extension Item |
M |
BIT STRING (SIZE(8)) |
Semantics along the definition of the MBSFN-SubframeConfig-v1430 IE as specified in TS 36.331 [11]. |
|
CHOICE Subframe Allocation Further Extension |
O |
|||
>One Frame Further Extension |
||||
>>One Frame Further Extension Item |
M |
BIT STRING (SIZE(2)) |
Semantics along the definition of the MBSFN-SubframeConfig-v1610 IE as specified in TS 36.331 [11]. |
|
>Four Frames Further Extension |
||||
>>Four Frame Further Extension Item |
M |
BIT STRING (SIZE(8)) |
Semantics along the definition of the MBSFN-SubframeConfig-v1610 IE as specified in TS 36.331 [11]. |
9.2.1.18 Common Subframe Allocation Period
This IE defines the period during which allocated subframes are divided between PMCHs configured for the MBSFN area, see TS 36.331 [11].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Common Subframe Allocation Period |
M |
ENUMERATED (rf4, rf8, rf16, rf32, rf64, rf128, rf256) |
The same encoding as the commonSF-AllocPeriod IE as specified in TS 36.331 [11]. |
9.2.1.19 MCCH Update Time
This IE indicates the time at which the eNB shall apply the update of the MCCH as specified in TS 36.300 [3].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MCCH Update Time |
M |
INTEGER (0..255) |
This IE indicates the modification period, as an absolute value, from when the MCCH update should be applied. |
9.2.1.20 MBSFN Synchronisation Area Id
This IE defines the MBSFN Synchronisation Area Identity as specified in TS 36.300 [3].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBSFN Synchronisation Area Id |
M |
INTEGER (0..65535) |
The MBSFN Synchronisation Area is defined in TS 36.300 [3]. |
9.2.1.21 Counting Result
This IE defines the number of connected mode Ues that are receiving or interested in a MBMS service.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Counting Result |
M |
INTEGER(0..1023) |
This IE indicates the number of connected mode Ues that are receiving or interested in a MBMS service. The value 1023 is used if the UE number is equal to or more than 1023. |
9.2.1.22 SC-PTM information
This IE defines the SC-PTM information.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBMS Cell List Item |
1 .. < maxnoofCellsforMBMS > |
|||
>Cell ID |
M |
E-UTRAN CGI 9.2.1.11 |
Global ID of the cell. |
|
MBMS E-RAB QoS parameters |
M |
9.2.1.23 |
Range bound |
Explanation |
maxnoofCellsforMBMS |
Maximum no. of cells for the MBMS service. The value for maxnoofCellsforMBMS is 4096. |
9.2.1.23 MBMS E-RAB QoS parameters
This IE defines the QoS to be applied to an MBMS E-RAB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBMS E-RAB QoS Parameters |
||||
>QCI |
M |
INTEGER (0..255) |
QoS Class Identifier defined in TS 23.246 [8]. |
|
>GBR QoS Information |
O |
9.2.1.24 |
This IE applies to GBR bearers only and shall be ignored otherwise. |
|
>Allocation and Retention Priority |
M |
9.2.1.26 |
9.2.1.24 GBR QoS Information
This IE indicates the maximum and guaranteed bit rates of a GBR bearer for downlink.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBMS E-RAB Maximum Bit Rate Downlink |
M |
Bit Rate 9.2.1.25 |
Desc.: This IE indicates the maximum downlink MBMS E-RAB Bit Rate (i.e. from the EPC to E-UTRAN) for this bearer. |
|
MBMS E-RAB Guaranteed Bit Rate Downlink |
M |
Bit Rate 9.2.1.25 |
Desc.: This IE indicates the downlink guaranteed MBMS E-RAB Bit Rate (provided that there is data to deliver) from the EPC to the E-UTRAN for this bearer. |
9.2.1.25 Bit Rate
This IE indicates the number of bits delivered by E-UTRAN in DL within a period of time, divided by the duration of the period. It is used, for example, to indicate the maximum or guaranteed bit rate for a GBR bearer, or an aggregated maximum bit rate.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Bit Rate |
INTEGER (0..10,000,000,000) |
The unit is: bit/s |
9.2.1.26 Allocation and Retention Priority
This IE specifies the relative importance of an MBMS E-RAB compared to other MBMS E-RABs for allocation and retention of the MBMS E-RAB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Allocation/Retention Priority |
||||
>Priority Level |
M |
INTEGER (0..15) |
Desc.: This IE should be understood as the “priority of allocation and retention” (see TS 23.246 [6]). Usage: Value 15 means “no priority”. Values between 1 and 14 are ordered in decreasing order of priority, i.e. 1 is the highest and 14 the lowest. Value 0 shall be treated as a logical error if received. |
|
>Pre-emption Capability |
M |
ENUMERATED(shall not trigger pre-emption, may trigger pre-emption) |
This IE indicates the pre-emption capability of the request on other MBMS E-RABs. |
|
>Pre-emption Vulnerability |
M |
ENUMERATED(not pre-emptable, pre-emptable) |
This IE indicates the vulnerability of the MBMS E-RAB to 55ehaviour55n of other MBMS E-RABs. |
9.2.1.27 MCCH related BCCH Extended Configuration Item
This information element provides MCCH related BCCH configuration information to the eNB in line with either the MBSFN-AreaInfo-r16 IE or the MBSFN-AreaInfo-r17 IE as defined in TS 36.331 [11].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
Criticality |
Assigned Criticality |
MBSFN Area Id |
M |
9.2.1.14 |
– |
– |
||
Repetition Period Expanded |
M |
ENUMERATED (rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, …) |
The same encoding as the mcch-RepetitionPeriod-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. |
– |
– |
|
Offset |
M |
INTEGER (0..10) |
The same encoding as the mcch-Offset-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. |
– |
– |
|
Modification Period Expanded |
M |
ENUMERATED (rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024, …) |
The same encoding as the mcch-ModificationPeriod-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. |
– |
– |
|
Subframe Allocation Info Expanded |
M |
BIT STRING (SIZE(10)) |
The same encoding as the sf-AllocInfo-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. |
– |
– |
|
Modulation and Coding Scheme |
M |
ENUMERATED (n2, n7, n13, n19) |
The same encoding as the signallingMCS-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. |
– |
– |
|
Subcarrier Spacing MBMS Expanded |
M |
ENUMERATED (khz-7dot5, khz-2dot5, khz-1dot25, khz-0dot37, …, kHz-15) |
The same encoding as the subcarrierSpacingMBMS-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. The value “kHz-15” is only applicable in case the Additional Configuration Parameters IE is present. |
– |
– |
|
Time separation |
O |
ENUMERATED (sl2, sl4, … ) |
The same encoding as the timeSeparation-r16 IE in the mcch-Config-r16 IE as specified in TS 36.331 [11]. |
– |
– |
|
Cell Information List |
0..1 |
|||||
>Cell Information |
1 to <maxnoofCells> |
|||||
>>E-UTRAN CGI |
M |
9.2.1.11 |
– |
– |
||
>>Cell Reservation Info |
M |
ENUMERATED (reservedCell, nonReservedCell, …) |
– |
– |
||
Additional Configuration Parameters |
O |
9.2.1.28 |
This IE is included for a configuration corresponding to the MBSFN-AreaInfoList-r17 IE as specified in TS 36.331 [11]. |
YES |
reject |
Range bound |
Explanation |
maxnoofCells |
Maximum no. of cells that may be served by an eNB. The value for maxnoofCells is 256. |
9.2.1.28 Additional Configuration Parameters
This information element provides additional MCCH related BCCH configuration information to the eNB in line with the MBSFN-AreaInfo-r17 IE as defined in TS 36.331 [11].
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PMCH Bandwidth |
M |
ENUMERATED (n40, n35, n30, …) |
The same encoding as the pmch-Bandwidth-r17 IE as specified in TS 36.331 [11]. |
9.2.2 Transport Network Layer Related Ies
9.2.2.1 IP Address
This information element is an IP address.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
IP Address |
M |
OCTET STRING (4..16) |
The Radio Network Layer is not supposed to interpret the address information. It should pass it to the transport layer for interpretation. For details on the IP Address, see ref. TS 36.445 [13]. |
9.2.2.2 GTP-TEID
This information element is the GTP Tunnel Endpoint Identifier to be used for the user plane transport between eNB and the MBMS-GW.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
GTP TEID |
M |
OCTET STRING (4) |
For details and range, see TS 29.281 [14]. |
9.2.3 NAS Related Ies
9.2.3.1 MCE MBMS M2AP ID
The MCE MBMS M2AP ID uniquely identifies the MBMS Service association over the M2 interface within the MCE.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MCE MBMS M2AP ID |
M |
INTEGER (0 .. 224 -1) |
9.2.3.2 eNB MBMS M2AP ID
The eNB MBMS M2AP ID uniquely identifies the MBMS Service association over the M2 interface within the eNB.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
eNB MBMS M2AP ID |
M |
INTEGER (0 .. 65535) |
9.2.3.3 TMGI
The TMGI uniquely identifies the MBMS Bearer Service.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
TMGI |
||||
>PLMN identity |
M |
9.2.3.7 |
||
>Service ID |
M |
OCTET STRING (SIZE (3)) |
9.2.3.4 MBMS Session Identity
The MBMS Session Identity identifies the session of an MBMS Bearer Service in E-UTRAN and is used by the UE to recognise repetitions of the session.
This IE is transparent to RAN.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBMS Session Identity |
M |
OCTET STRING (SIZE (1)) |
Coded same way as the MBMS Session Identity IE as defined in TS 29.061 [9]. |
9.2.3.5 Void
9.2.3.6 MBMS Service Area
The MBMS Service Area IE consists of a list of one or several MBMS Service Area Identities where each MBMS Service Area Identity is frequency agnostic and can be mapped onto one or more cells.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
MBMS Service Area |
M |
OCTET STRING |
Value part coded per MBMS Service Area AVP as defined in TS 29.061 [9]. |
9.2.3.7 PLMN Identity
This information element indicates the PLMN Identity.
IE/Group Name |
Presence |
Range |
IE type and reference |
Semantics description |
PLMN identity |
M |
OCTET STRING (SIZE (3)) |
– digits 0 to 9, encoded 0000 to 1001, -The Selected PLMN identity consists of 3 digits from MCC followed by either |
9.3 Message and Information Element Abstract Syntax (with ASN.1)
9.3.1 General
M2AP ASN.1 definition conforms with ITU-T Rec. X.691 [5] and ITU-T Rec. X.680 [6].
Sub clause 9.3 presents the Abstract Syntax of the M2AP protocol with ASN.1. In case there is contradiction between the ASN.1 definition in this sub clause and the tabular format in sub clause 9.1 and 9.2, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional elements, in which the tabular format shall take precedence.
The ASN.1 definition specifies the structure and content of M2AP messages. M2AP messages can contain any Ies specified in the object set definitions for that message without the order or number of occurrence being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct an M2AP message according to the PDU definitions module and with the following additional rules (Note that in the following IE means an IE in the object set with an explicit id. If one IE needed to appear more than once in one object set, then the different occurrences have different IE ids):
– Ies shall be ordered (in an IE container) in the order they appear in object set definitions.
– Object set definitions specify how many times Ies may appear. An IE shall appear exactly once if the presence field in an object has value “mandatory”. An IE may appear at most once if the presence field in an object has value “optional” or “conditional”. If in a tabular format there is multiplicity specified for an IE (i.e. an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list in which the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements.
If an M2AP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error in clause 10.
9.3.2 Usage of Private Message Mechanism for Non-standard Use
The private message mechanism for non-standard use may be used:
– for special operator (and/or vendor) specific features considered not to be part of the basic functionality, i.e. the functionality required for a complete and high-quality specification in order to guarantee multivendor inter-operability.
– by vendors for research purposes, e.g. to implement and evaluate new algorithms/features before such features are proposed for standardisation.
The private message mechanism shall not be used for basic functionality. Such functionality shall be standardised.
9.3.3 Elementary Procedure Definitions
— **************************************************************
—
— Elementary Procedure definitions
—
— **************************************************************
M2AP-PDU-Descriptions {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) m2ap (4) version1 (1) m2ap-PDU-Descriptions (0) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
— **************************************************************
—
— IE parameter types from other modules.
—
— **************************************************************
IMPORTS
Criticality,
ProcedureCode
FROM M2AP-CommonDataTypes
SessionStartRequest,
SessionStartResponse,
SessionStartFailure,
SessionStopRequest,
SessionStopResponse,
SessionUpdateRequest,
SessionUpdateResponse,
SessionUpdateFailure,
MbmsSchedulingInformation,
MbmsSchedulingInformationResponse,
ErrorIndication,
Reset,
ResetAcknowledge,
M2SetupRequest,
M2SetupResponse,
M2SetupFailure,
ENBConfigurationUpdate,
ENBConfigurationUpdateAcknowledge,
ENBConfigurationUpdateFailure,
MCEConfigurationUpdate,
MCEConfigurationUpdateAcknowledge,
MCEConfigurationUpdateFailure,
MbmsServiceCountingRequest,
MbmsServiceCountingResponse,
MbmsServiceCountingFailure,
MbmsServiceCountingResultsReport,
PrivateMessage,
MbmsOverloadNotification
FROM M2AP-PDU-Contents
id-sessionStart,
id-sessionStop,
id-sessionUpdate,
id-mbmsServiceCounting,
id-mbmsServiceCountingResultsReport,
id-mbmsSchedulingInformation,
id-errorIndication,
id-reset,
id-m2Setup,
id-eNBConfigurationUpdate,
id-mCEConfigurationUpdate,
id-privateMessage,
id-mbmsOverloadNotification
FROM M2AP-Constants;
— **************************************************************
—
— Interface Elementary Procedure Class
—
— **************************************************************
M2AP-ELEMENTARY-PROCEDURE ::= CLASS {
&InitiatingMessage ,
&SuccessfulOutcome OPTIONAL,
&UnsuccessfulOutcome OPTIONAL,
&procedureCode ProcedureCode UNIQUE,
&criticality Criticality DEFAULT ignore
}
WITH SYNTAX {
INITIATING MESSAGE &InitiatingMessage
[SUCCESSFUL OUTCOME &SuccessfulOutcome]
[UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome]
PROCEDURE CODE &procedureCode
[CRITICALITY &criticality]
}
— **************************************************************
—
— Interface PDU Definition
—
— **************************************************************
M2AP-PDU ::= CHOICE {
initiatingMessage InitiatingMessage,
successfulOutcome SuccessfulOutcome,
unsuccessfulOutcome UnsuccessfulOutcome,
…
}
InitiatingMessage ::= SEQUENCE {
procedureCode M2AP-ELEMENTARY-PROCEDURE.&procedureCode ({M2AP-ELEMENTARY-PROCEDURES}),
criticality M2AP-ELEMENTARY-PROCEDURE.&criticality ({M2AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
value M2AP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({M2AP-ELEMENTARY-PROCEDURES}{@procedureCode})
}
SuccessfulOutcome ::= SEQUENCE {
procedureCode M2AP-ELEMENTARY-PROCEDURE.&procedureCode ({M2AP-ELEMENTARY-PROCEDURES}),
criticality M2AP-ELEMENTARY-PROCEDURE.&criticality ({M2AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
value M2AP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({M2AP-ELEMENTARY-PROCEDURES}{@procedureCode})
}
UnsuccessfulOutcome ::= SEQUENCE {
procedureCode M2AP-ELEMENTARY-PROCEDURE.&procedureCode ({M2AP-ELEMENTARY-PROCEDURES}),
criticality M2AP-ELEMENTARY-PROCEDURE.&criticality ({M2AP-ELEMENTARY-PROCEDURES}{@procedureCode}),
value M2AP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({M2AP-ELEMENTARY-PROCEDURES}{@procedureCode})
}
— **************************************************************
—
— Interface Elementary Procedure List
—
— **************************************************************
M2AP-ELEMENTARY-PROCEDURES M2AP-ELEMENTARY-PROCEDURE ::= {
M2AP-ELEMENTARY-PROCEDURES-CLASS-1 |
M2AP-ELEMENTARY-PROCEDURES-CLASS-2 ,
…
}
M2AP-ELEMENTARY-PROCEDURES-CLASS-1 M2AP-ELEMENTARY-PROCEDURE ::= {
sessionStart |
sessionStop |
sessionUpdate |
mbmsSchedulingInformation |
reset |
m2Setup |
eNBConfigurationUpdate |
mCEConfigurationUpdate |
mbmsServiceCounting ,
…
}
M2AP-ELEMENTARY-PROCEDURES-CLASS-2 M2AP-ELEMENTARY-PROCEDURE ::= {
errorIndication |
privateMessage |
mbmsServiceCountingResultsReport |
mbmsOverloadNotification ,
…
}
— **************************************************************
—
— Interface Elementary Procedures
—
— **************************************************************
sessionStart M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE SessionStartRequest
SUCCESSFUL OUTCOME SessionStartResponse
UNSUCCESSFUL OUTCOME SessionStartFailure
PROCEDURE CODE id-sessionStart
CRITICALITY reject
}
sessionStop M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE SessionStopRequest
SUCCESSFUL OUTCOME SessionStopResponse
PROCEDURE CODE id-sessionStop
CRITICALITY reject
}
sessionUpdate M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE SessionUpdateRequest
SUCCESSFUL OUTCOME SessionUpdateResponse
UNSUCCESSFUL OUTCOME SessionUpdateFailure
PROCEDURE CODE id-sessionUpdate
CRITICALITY reject
}
mbmsSchedulingInformation M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE MbmsSchedulingInformation
SUCCESSFUL OUTCOME MbmsSchedulingInformationResponse
PROCEDURE CODE id-mbmsSchedulingInformation
CRITICALITY reject
}
errorIndication M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE ErrorIndication
PROCEDURE CODE id-errorIndication
CRITICALITY ignore
}
reset M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE Reset
SUCCESSFUL OUTCOME ResetAcknowledge
PROCEDURE CODE id-reset
CRITICALITY reject
}
m2Setup M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE M2SetupRequest
SUCCESSFUL OUTCOME M2SetupResponse
UNSUCCESSFUL OUTCOME M2SetupFailure
PROCEDURE CODE id-m2Setup
CRITICALITY reject
}
eNBConfigurationUpdate M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE ENBConfigurationUpdate
SUCCESSFUL OUTCOME ENBConfigurationUpdateAcknowledge
UNSUCCESSFUL OUTCOME ENBConfigurationUpdateFailure
PROCEDURE CODE id-eNBConfigurationUpdate
CRITICALITY reject
}
mCEConfigurationUpdate M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE MCEConfigurationUpdate
SUCCESSFUL OUTCOME MCEConfigurationUpdateAcknowledge
UNSUCCESSFUL OUTCOME MCEConfigurationUpdateFailure
PROCEDURE CODE id-mCEConfigurationUpdate
CRITICALITY reject
}
mbmsServiceCounting M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE MbmsServiceCountingRequest
SUCCESSFUL OUTCOME MbmsServiceCountingResponse
UNSUCCESSFUL OUTCOME MbmsServiceCountingFailure
PROCEDURE CODE id-mbmsServiceCounting
CRITICALITY reject
}
mbmsServiceCountingResultsReport M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE MbmsServiceCountingResultsReport
PROCEDURE CODE id-mbmsServiceCountingResultsReport
CRITICALITY reject
}
privateMessage M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE PrivateMessage
PROCEDURE CODE id-privateMessage
CRITICALITY ignore
}
mbmsOverloadNotification M2AP-ELEMENTARY-PROCEDURE ::= {
INITIATING MESSAGE MbmsOverloadNotification
PROCEDURE CODE id-mbmsOverloadNotification
CRITICALITY reject
}
END
9.3.4 PDU Definitions
— **************************************************************
—
— PDU definitions for M2AP.
—
— **************************************************************
M2AP-PDU-Contents {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) m2ap (4) version1 (1) m2ap-PDU-Contents (1) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
— **************************************************************
—
— IE parameter types from other modules.
—
— **************************************************************
IMPORTS
Cause,
CriticalityDiagnostics,
ENB-MBMS-Configuration-data-Item,
ENB-MBMS-Configuration-data-ConfigUpdate-Item,
ENB-MBMS-M2AP-ID,
ENBname,
GlobalENB-ID,
GlobalMCE-ID,
MBSFN-Area-ID,
MBMS-Service-Area,
MBMS-Session-ID,
MBMSsessionListPerPMCH-Item,
MBMS-Service-associatedLogicalM2-ConnectionItem,
MBSFN-Subframe-Configuration,
MCCH-Update-Time,
MCCHrelatedBCCH-ConfigPerMBSFNArea-Item,
MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item,
MCE-MBMS-M2AP-ID,
MCEname,
PMCH-Configuration,
Common-Subframe-Allocation-Period,
TimeToWait,
TMGI,
TNL-Information,
SFN,
MBMSsessionsToBeSuspendedListPerPMCH-Item,
SC-PTM-Information
FROM M2AP-Ies
PrivateIE-Container{},
ProtocolExtensionContainer{},
ProtocolIE-Container{},
ProtocolIE-ContainerList{},
ProtocolIE-ContainerPair{},
ProtocolIE-ContainerPairList{},
ProtocolIE-Single-Container{},
M2AP-PRIVATE-IES,
M2AP-PROTOCOL-EXTENSION,
M2AP-PROTOCOL-IES,
M2AP-PROTOCOL-IES-PAIR
FROM M2AP-Containers
id-MCE-MBMS-M2AP-ID,
id-ENB-MBMS-M2AP-ID,
id-TMGI,
id-MBMS-Session-ID,
id-MBMS-Service-Area,
id-TNL-Information,
id-Alternative-TNL-Information,
id-CriticalityDiagnostics,
id-Cause,
id-MBSFN-Area-Configuration-List,
id-MBSFN-Subframe-Configuration-Item,
id-MBSFN-Subframe-Configuration-List,
id-MCCH-Update-Time,
id-PMCH-Configuration-List,
id-PMCH-Configuration-Item,
id-Common-Subframe-Allocation-Period,
id-GlobalENB-ID,
id-ENBname,
id-ENB-MBMS-Configuration-data-List,
id-ENB-MBMS-Configuration-data-Item,
id-GlobalMCE-ID,
id-MCEname,
id-MCCHrelatedBCCH-ConfigPerMBSFNArea,
id-MCCHrelatedBCCH-ConfigPerMBSFNArea-Item,
id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea,
id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item,
id-TimeToWait,
id-ENB-MBMS-Configuration-data-List-ConfigUpdate,
id-ENB-MBMS-Configuration-data-ConfigUpdate-Item,
id-MBSFN-Area-ID,
id-ResetType,
id-MBMS-Service-associatedLogicalM2-ConnectionItem,
id-MBMS-Service-associatedLogicalM2-ConnectionListResAck,
id-MBMS-Counting-Request-Session,
id-MBMS-Counting-Request-Session-Item,
id-MBMS-Counting-Result-List,
id-MBMS-Counting-Result-Item,
id-MBMS-Suspension-Notification-List,
id-MBMS-Suspension-Notification-Item,
id-PMCH-Overload-Status,
id-Overload-Status-Per-PMCH-List,
id-Active-MBMS-Session-List,
id-SC-PTM-Information,
maxnoofMBSFN-Allocations,
maxnoofMBSFNareas,
maxnoofPMCHsperMBSFNarea,
maxnoofCells,
maxnoofMBMSServiceAreasPerCell,
maxnoofSessionsPerPMCH,
maxnooferrors,
maxNrOfIndividualM2ConnectionsToReset,
maxnoofCountingService
FROM M2AP-Constants;
— **************************************************************
—
— SESSION START REQUEST
—
— **************************************************************
SessionStartRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{SessionStartRequest-Ies}},
…
}
SessionStartRequest-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY reject TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory}|
{ ID id-TMGI CRITICALITY reject TYPE TMGI PRESENCE mandatory}|
{ ID id-MBMS-Session-ID CRITICALITY ignore TYPE MBMS-Session-ID PRESENCE optional}|
{ ID id-MBMS-Service-Area CRITICALITY reject TYPE MBMS-Service-Area PRESENCE mandatory}|
{ ID id-TNL-Information CRITICALITY reject TYPE TNL-Information PRESENCE mandatory}|
{ ID id-Alternative-TNL-Information CRITICALITY ignore TYPE TNL-Information PRESENCE optional}|
{ ID id-SC-PTM-Information CRITICALITY reject TYPE SC-PTM-Information PRESENCE optional},
…
}
— **************************************************************
—
— SESSION START RESPONSE
—
— **************************************************************
SessionStartResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ SessionStartResponse-Ies}},
…
}
SessionStartResponse-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY ignore TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY ignore TYPE ENB-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
…
}
— **************************************************************
—
— SESSION START FAILURE
—
— **************************************************************
SessionStartFailure ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ SessionStartFailure-Ies}},
…
}
SessionStartFailure-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY ignore TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
…
}
— **************************************************************
—
— SESSION STOP REQUEST
—
— **************************************************************
SessionStopRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{SessionStopRequest-Ies}},
…
}
SessionStopRequest-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY reject TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY reject TYPE ENB-MBMS-M2AP-ID PRESENCE mandatory } ,
…
}
— **************************************************************
—
— SESSION STOP RESPONSE
—
— **************************************************************
SessionStopResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ SessionStopResponse-Ies}},
…
}
SessionStopResponse-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY ignore TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY ignore TYPE ENB-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional } ,
…
}
— **************************************************************
—
— SESSION UPDATE REQUEST
—
— **************************************************************
SessionUpdateRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{SessionUpdateRequest-Ies}},
…
}
SessionUpdateRequest-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY reject TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory}|
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY reject TYPE ENB-MBMS-M2AP-ID PRESENCE mandatory}|
{ ID id-TMGI CRITICALITY reject TYPE TMGI PRESENCE mandatory}|
{ ID id-MBMS-Session-ID CRITICALITY ignore TYPE MBMS-Session-ID PRESENCE optional}|
{ ID id-MBMS-Service-Area CRITICALITY ignore TYPE MBMS-Service-Area PRESENCE optional}|
{ ID id-TNL-Information CRITICALITY reject TYPE TNL-Information PRESENCE optional}|
{ ID id-SC-PTM-Information CRITICALITY reject TYPE SC-PTM-Information PRESENCE optional},
…
}
— **************************************************************
—
— SESSION UPDATE RESPONSE
—
— **************************************************************
SessionUpdateResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ SessionUpdateResponse-Ies}},
…
}
SessionUpdateResponse-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY ignore TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY ignore TYPE ENB-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
…
}
— **************************************************************
—
— SESSION UPDATE FAILURE
—
— **************************************************************
SessionUpdateFailure ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ SessionUpdateFailure-Ies}},
…
}
SessionUpdateFailure-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY ignore TYPE MCE-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY ignore TYPE ENB-MBMS-M2AP-ID PRESENCE mandatory } |
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory } |
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
…
}
— **************************************************************
—
— MBMS SCHEDULING INFORMATION
—
— **************************************************************
MbmsSchedulingInformation ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MbmsSchedulingInformation-Ies}},
…
}
MbmsSchedulingInformation-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCCH-Update-Time CRITICALITY reject TYPE MCCH-Update-Time PRESENCE mandatory }|
{ ID id-MBSFN-Area-Configuration-List CRITICALITY reject TYPE MBSFN-Area-Configuration-List PRESENCE mandatory },
…
}
MBSFN-Area-Configuration-List ::= SEQUENCE (SIZE(1.. maxnoofMBSFNareas)) OF ProtocolIE-Container { { MBSFN-Area-Configuration-Item } }
MBSFN-Area-Configuration-Item M2AP-PROTOCOL-IES ::= {
{ ID id-PMCH-Configuration-List CRITICALITY reject TYPE PMCH-Configuration-List PRESENCE mandatory }|
{ ID id-MBSFN-Subframe-Configuration-List CRITICALITY reject TYPE MBSFN-Subframe-ConfigurationList PRESENCE mandatory }|
{ ID id-Common-Subframe-Allocation-Period CRITICALITY reject TYPE Common-Subframe-Allocation-Period PRESENCE mandatory }|
{ ID id-MBSFN-Area-ID CRITICALITY reject TYPE MBSFN-Area-ID PRESENCE mandatory }|
{ ID id-MBMS-Suspension-Notification-List CRITICALITY ignore TYPE MBMS-Suspension-Notification-List PRESENCE optional },
…
}
PMCH-Configuration-List ::= SEQUENCE (SIZE(0.. maxnoofPMCHsperMBSFNarea)) OF ProtocolIE-Single-Container { { PMCH-Configuration-ItemIEs } }
PMCH-Configuration-ItemIEs M2AP-PROTOCOL-IES ::= {
{ ID id-PMCH-Configuration-Item CRITICALITY reject TYPE PMCH-Configuration-Item PRESENCE mandatory },
…
}
PMCH-Configuration-Item ::= SEQUENCE {
pmch-Configuration PMCH-Configuration,
mbms-Session-List MBMSsessionListPerPMCH-Item,
iE-Extensions ProtocolExtensionContainer { { PMCH-Configuration-ItemExtIEs} } OPTIONAL,
…
}
PMCH-Configuration-ItemExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
MBSFN-Subframe-ConfigurationList ::= SEQUENCE (SIZE(1.. maxnoofMBSFN-Allocations)) OF ProtocolIE-Single-Container { { MBSFN-Subframe-ConfigurationItem } }
MBSFN-Subframe-ConfigurationItem M2AP-PROTOCOL-IES ::= {
{ ID id-MBSFN-Subframe-Configuration-Item CRITICALITY reject TYPE MBSFN-Subframe-Configuration PRESENCE mandatory },
…
}
MBMS-Suspension-Notification-List ::= SEQUENCE (SIZE(1.. maxnoofPMCHsperMBSFNarea)) OF ProtocolIE-Single-Container { { MBMS-Suspension-Notification-ItemIEs } }
MBMS-Suspension-Notification-ItemIEs M2AP-PROTOCOL-IES ::= {
{ ID id-MBMS-Suspension-Notification-Item CRITICALITY ignore TYPE MBMS-Suspension-Notification-Item PRESENCE optional},
…
}
MBMS-Suspension-Notification-Item ::= SEQUENCE {
sfn SFN,
mbms-Sessions-To-Be-Suspended-List MBMSsessionsToBeSuspendedListPerPMCH-Item,
iE-Extensions ProtocolExtensionContainer { { MBMS-Suspension-Notification-ItemExtIEs} } OPTIONAL,
…
}
MBMS-Suspension-Notification-ItemExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
— **************************************************************
—
— MBMS SCHEDULING INFORMATION RESPONSE
—
— **************************************************************
MbmsSchedulingInformationResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MbmsSchedulingInformationResponse-Ies}},
…
}
MbmsSchedulingInformationResponse-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
…
}
— **************************************************************
—
— M2 SETUP REQUEST
—
— **************************************************************
M2SetupRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{M2SetupRequest-Ies}},
…
}
M2SetupRequest-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-GlobalENB-ID CRITICALITY reject TYPE GlobalENB-ID PRESENCE mandatory}|
{ ID id-ENBname CRITICALITY ignore TYPE ENBname PRESENCE optional}|
{ ID id-ENB-MBMS-Configuration-data-List CRITICALITY reject TYPE ENB-MBMS-Configuration-data-List PRESENCE mandatory},
…
}
ENB-MBMS-Configuration-data-List ::= SEQUENCE (SIZE(1.. maxnoofCells)) OF ProtocolIE-Single-Container { { ENB-MBMS-Configuration-data-ItemIEs } }
ENB-MBMS-Configuration-data-ItemIEs M2AP-PROTOCOL-IES ::= {
{ ID id-ENB-MBMS-Configuration-data-Item CRITICALITY reject TYPE ENB-MBMS-Configuration-data-Item PRESENCE mandatory },
…
}
— **************************************************************
—
— M2 SETUP RESPONSE
—
— **************************************************************
M2SetupResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ M2SetupResponse-Ies}},
…
}
M2SetupResponse-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-GlobalMCE-ID CRITICALITY reject TYPE GlobalMCE-ID PRESENCE mandatory }|
{ ID id-MCEname CRITICALITY ignore TYPE MCEname PRESENCE optional }|
{ ID id-MCCHrelatedBCCH-ConfigPerMBSFNArea CRITICALITY reject TYPE MCCHrelatedBCCH-ConfigPerMBSFNArea PRESENCE mandatory }|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
{ ID id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea CRITICALITY reject TYPE MCCHrelatedBCCH-ExtConfigPerMBSFNArea PRESENCE optional },
…
}
MCCHrelatedBCCH-ConfigPerMBSFNArea ::= SEQUENCE (SIZE(1.. maxnoofMBSFNareas)) OF ProtocolIE-Single-Container { { MCCHrelatedBCCH-ConfigPerMBSFNArea-ItemIEs } }
MCCHrelatedBCCH-ConfigPerMBSFNArea-ItemIEs M2AP-PROTOCOL-IES ::= {
{ ID id-MCCHrelatedBCCH-ConfigPerMBSFNArea-Item CRITICALITY reject TYPE MCCHrelatedBCCH-ConfigPerMBSFNArea-Item PRESENCE mandatory },
…
}
MCCHrelatedBCCH-ExtConfigPerMBSFNArea ::= SEQUENCE (SIZE(1.. maxnoofMBSFNareas)) OF ProtocolIE-Single-Container { { MCCHrelatedBCCH-ExtConfigPerMBSFNArea-ItemIEs } }
MCCHrelatedBCCH-ExtConfigPerMBSFNArea-ItemIEs M2AP-PROTOCOL-IES ::= {
{ ID id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item CRITICALITY reject TYPE MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item PRESENCE mandatory },
…
}
— **************************************************************
—
— M2 SETUP FAILURE
—
— **************************************************************
M2SetupFailure ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ M2SetupFailure-Ies}},
…
}
M2SetupFailure-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
{ ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional}|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
— **************************************************************
—
— ENB CONFIGURATION UPDATE
—
— **************************************************************
ENBConfigurationUpdate ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ENBConfigurationUpdate-Ies}},
…
}
ENBConfigurationUpdate-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-GlobalENB-ID CRITICALITY reject TYPE GlobalENB-ID PRESENCE optional }|
{ ID id-ENBname CRITICALITY ignore TYPE ENBname PRESENCE optional }|
{ ID id-ENB-MBMS-Configuration-data-List-ConfigUpdate CRITICALITY reject TYPE ENB-MBMS-Configuration-data-List-ConfigUpdate PRESENCE optional },
…
}
ENB-MBMS-Configuration-data-List-ConfigUpdate ::= SEQUENCE (SIZE(1.. maxnoofCells)) OF ProtocolIE-Single-Container { { ENB-MBMS-Configuration-data-ConfigUpdate-ItemIEs } }
ENB-MBMS-Configuration-data-ConfigUpdate-ItemIEs M2AP-PROTOCOL-IES ::= {
{ ID id-ENB-MBMS-Configuration-data-ConfigUpdate-Item CRITICALITY reject TYPE ENB-MBMS-Configuration-data-ConfigUpdate-Item PRESENCE mandatory },
…
}
— **************************************************************
—
— ENB CONFIGURATION UPDATE ACKNOWLEDGE
—
— **************************************************************
ENBConfigurationUpdateAcknowledge ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ ENBConfigurationUpdateAcknowledge-Ies}},
…
}
ENBConfigurationUpdateAcknowledge-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCCHrelatedBCCH-ConfigPerMBSFNArea CRITICALITY reject TYPE MCCHrelatedBCCH-ConfigPerMBSFNArea PRESENCE optional }|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }|
{ ID id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea CRITICALITY reject TYPE MCCHrelatedBCCH-ExtConfigPerMBSFNArea PRESENCE optional },
…
}
— **************************************************************
—
— ENB CONFIGURATION UPDATE FAILURE
—
— **************************************************************
ENBConfigurationUpdateFailure ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ ENBConfigurationUpdateFailure-Ies}},
…
}
ENBConfigurationUpdateFailure-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
{ ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional}|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
— **************************************************************
—
— MCE CONFIGURATION UPDATE
—
— **************************************************************
MCEConfigurationUpdate ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{MCEConfigurationUpdate-Ies}},
…
}
MCEConfigurationUpdate-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-GlobalMCE-ID CRITICALITY reject TYPE GlobalMCE-ID PRESENCE optional }|
{ ID id-MCEname CRITICALITY ignore TYPE MCEname PRESENCE optional }|
{ ID id-MCCHrelatedBCCH-ConfigPerMBSFNArea CRITICALITY reject TYPE MCCHrelatedBCCH-ConfigPerMBSFNArea PRESENCE optional }|
{ ID id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea CRITICALITY reject TYPE MCCHrelatedBCCH-ExtConfigPerMBSFNArea PRESENCE optional },
…
}
— **************************************************************
—
— MCE CONFIGURATION UPDATE ACKNOWLEDGE
—
— **************************************************************
MCEConfigurationUpdateAcknowledge ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MCEConfigurationUpdateAcknowledge-Ies}},
…
}
MCEConfigurationUpdateAcknowledge-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
— **************************************************************
—
— MCE CONFIGURATION UPDATE FAILURE
—
— **************************************************************
MCEConfigurationUpdateFailure ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MCEConfigurationUpdateFailure-Ies}},
…
}
MCEConfigurationUpdateFailure-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
{ ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional}|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
— **************************************************************
—
— ERROR INDICATION
—
— **************************************************************
ErrorIndication ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ErrorIndication-Ies}},
…
}
ErrorIndication-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCE-MBMS-M2AP-ID CRITICALITY ignore TYPE MCE-MBMS-M2AP-ID PRESENCE optional}|
{ ID id-ENB-MBMS-M2AP-ID CRITICALITY ignore TYPE ENB-MBMS-M2AP-ID PRESENCE optional}|
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional}|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
— **************************************************************
—
— RESET
—
— **************************************************************
Reset ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{Reset-Ies}},
…
}
Reset-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
{ ID id-ResetType CRITICALITY reject TYPE ResetType PRESENCE mandatory},
…
}
ResetType ::= CHOICE {
m2-Interface ResetAll,
partOfM2-Interface MBMS-Service-associatedLogicalM2-ConnectionListRes,
…
}
ResetAll ::= ENUMERATED {
reset-all,
…
}
MBMS-Service-associatedLogicalM2-ConnectionListRes ::= SEQUENCE (SIZE(1.. maxNrOfIndividualM2ConnectionsToReset)) OF ProtocolIE-Single-Container { { MBMS-Service-associatedLogicalM2-ConnectionItemRes } }
MBMS-Service-associatedLogicalM2-ConnectionItemRes M2AP-PROTOCOL-IES ::= {
{ ID id-MBMS-Service-associatedLogicalM2-ConnectionItem CRITICALITY reject TYPE MBMS-Service-associatedLogicalM2-ConnectionItem PRESENCE mandatory},
…
}
— **************************************************************
—
— RESET ACKNOWLEDGE
—
— **************************************************************
ResetAcknowledge ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ResetAcknowledge-Ies}},
…
}
ResetAcknowledge-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MBMS-Service-associatedLogicalM2-ConnectionListResAck CRITICALITY ignore TYPE MBMS-Service-associatedLogicalM2-ConnectionListResAck PRESENCE optional}|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
MBMS-Service-associatedLogicalM2-ConnectionListResAck ::= SEQUENCE (SIZE(1.. maxNrOfIndividualM2ConnectionsToReset)) OF ProtocolIE-Single-Container { { MBMS-Service-associatedLogicalM2-ConnectionItemResAck } }
MBMS-Service-associatedLogicalM2-ConnectionItemResAck M2AP-PROTOCOL-IES ::= {
{ ID id-MBMS-Service-associatedLogicalM2-ConnectionItem CRITICALITY ignore TYPE MBMS-Service-associatedLogicalM2-ConnectionItem PRESENCE mandatory},
…
}
— **************************************************************
—
— PRIVATE MESSAGE
—
— **************************************************************
PrivateMessage ::= SEQUENCE {
privateIEs PrivateIE-Container {{PrivateMessage-Ies}},
…
}
PrivateMessage-Ies M2AP-PRIVATE-IES ::= {
…
}
— **************************************************************
—
— MBMS SERVICE COUNTING REQUEST
—
— **************************************************************
MbmsServiceCountingRequest ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{MbmsServiceCountingRequest-Ies}},
…
}
MbmsServiceCountingRequest-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MCCH-Update-Time CRITICALITY reject TYPE MCCH-Update-Time PRESENCE mandatory }|
{ ID id-MBSFN-Area-ID CRITICALITY reject TYPE MBSFN-Area-ID PRESENCE mandatory }|
{ ID id-MBMS-Counting-Request-Session CRITICALITY reject TYPE MBMS-Counting-Request-Session PRESENCE mandatory },
…
}
MBMS-Counting-Request-Session ::= SEQUENCE (SIZE(1.. maxnoofCountingService)) OF ProtocolIE-Container { { MBMS-Counting-Request-Session-Item } }
MBMS-Counting-Request-Session-Item M2AP-PROTOCOL-IES ::= {
{ ID id-MBMS-Counting-Request-Session-Item CRITICALITY reject TYPE MBMS-Counting-Request-SessionIE PRESENCE mandatory },
…
}
MBMS-Counting-Request-SessionIE ::= SEQUENCE{
tmgi TMGI,
iE-Extensions ProtocolExtensionContainer { { MBMS-Counting-Request-SessionIE-ExtIEs} } OPTIONAL,
…
}
MBMS-Counting-Request-SessionIE-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
— **************************************************************
—
— MBMS SERVICE COUNTING RESPONSE
—
— **************************************************************
MbmsServiceCountingResponse ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{MbmsServiceCountingResponse-Ies}},
…
}
MbmsServiceCountingResponse-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional },
…
}
— **************************************************************
—
— MBMS SERVICE COUNTING FAILURE
—
— **************************************************************
MbmsServiceCountingFailure ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MbmsServiceCountingFailure-Ies}},
…
}
MbmsServiceCountingFailure-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory}|
{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional},
…
}
— **************************************************************
—
— MBMS SERVICE COUNTING RESULTS REPORT
—
— **************************************************************
MbmsServiceCountingResultsReport ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MbmsServiceCountingResultsReport-Ies}},
…
}
MbmsServiceCountingResultsReport-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MBSFN-Area-ID CRITICALITY reject TYPE MBSFN-Area-ID PRESENCE mandatory}|
{ ID id-MBMS-Counting-Result-List CRITICALITY reject TYPE MBMS-Counting-Result-List PRESENCE mandatory},
…
}
MBMS-Counting-Result-List ::= SEQUENCE (SIZE(1.. maxnoofCountingService)) OF ProtocolIE-Container { { MBMS-Counting-Result-Item } }
MBMS-Counting-Result-Item M2AP-PROTOCOL-IES ::= {
{ ID id-MBMS-Counting-Result-Item CRITICALITY reject TYPE MBMS-Counting-Result PRESENCE mandatory },
…
}
MBMS-Counting-Result ::= SEQUENCE{
tmgi TMGI,
countingResult CountingResult,
iE-Extensions ProtocolExtensionContainer { { MBMS-Counting-Result-ExtIEs} } OPTIONAL,
…
}
MBMS-Counting-Result-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
CountingResult ::= INTEGER (0..1023)
— **************************************************************
—
— MBMS OVERLOAD NOTIFICATION
—
— **************************************************************
MbmsOverloadNotification ::= SEQUENCE {
protocolIEs ProtocolIE-Container {{ MbmsOverloadNotification-Ies}},
…
}
MbmsOverloadNotification-Ies M2AP-PROTOCOL-IES ::= {
{ ID id-MBSFN-Area-ID CRITICALITY reject TYPE MBSFN-Area-ID PRESENCE mandatory}|
{ ID id-Overload-Status-Per-PMCH-List CRITICALITY reject TYPE Overload-Status-Per-PMCH-List PRESENCE mandatory},
…
}
Overload-Status-Per-PMCH-List ::= SEQUENCE (SIZE(1..maxnoofPMCHsperMBSFNarea)) OF ProtocolIE-Container { { Overload-Status-Per-PMCH-Item } }
Overload-Status-Per-PMCH-Item M2AP-PROTOCOL-IES ::= {
{ ID id-PMCH-Overload-Status CRITICALITY reject TYPE PMCH-Overload-Status PRESENCE mandatory }|
{ ID id-Active-MBMS-Session-List CRITICALITY reject TYPE Active-MBMS-Session-List PRESENCE optional },
…
}
PMCH-Overload-Status ::= ENUMERATED {normal, overload, …}
Active-MBMS-Session-List ::= SEQUENCE (SIZE(1..maxnoofSessionsPerPMCH)) OF ProtocolIE-Container { { Active-MBMS-Session-Item } }
Active-MBMS-Session-Item M2AP-PROTOCOL-IES ::= {
{ ID id-TMGI CRITICALITY reject TYPE TMGI PRESENCE mandatory },
…
}
END
9.3.5 Information Element definitions
— **************************************************************
—
— Information Element Definitions
—
— **************************************************************
M2AP-Ies {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) m2ap (4) version1 (1) m2ap-Ies (2) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
IMPORTS
id-MCH-Scheduling-PeriodExtended,
id-MCH-Scheduling-PeriodExtended2,
id-Modification-PeriodExtended,
id-Modulation-Coding-Scheme2,
id-Repetition-PeriodExtended,
id-Subcarrier-SpacingMBMS,
id-SubframeAllocationExtended,
id-SubframeAllocationFurtherExtension,
id-AdditionalConfigParameters,
maxnoofMBSFNareas,
maxnoofPMCHsperMBSFNarea,
maxnoofCells,
maxnoofMBMSServiceAreasPerCell,
maxnoofSessionsPerPMCH,
maxnooferrors,
maxnoofCellsforMBMS
FROM M2AP-Constants
Criticality,
ProcedureCode,
ProtocolIE-ID,
TriggeringMessage
FROM M2AP-CommonDataTypes
ProtocolExtensionContainer{},
ProtocolIE-Single-Container{},
M2AP-PROTOCOL-EXTENSION,
M2AP-PROTOCOL-IES
FROM M2AP-Containers;
— A
AdditionalConfigParameters ::= SEQUENCE {
pmch-Bandwidth PMCH-Bandwidth,
iE-Extensions ProtocolExtensionContainer { {AdditionalConfigParameters-ExtIEs} } OPTIONAL
}
AdditionalConfigParameters-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
AllocatedSubframesEnd ::= INTEGER (0..1535)
AllocationAndRetentionPriority ::= SEQUENCE {
priorityLevel PriorityLevel,
pre-emptionCapability Pre-emptionCapability,
pre-emptionVulnerability Pre-emptionVulnerability,
iE-Extensions ProtocolExtensionContainer { {AllocationAndRetentionPriority-ExtIEs} } OPTIONAL
}
AllocationAndRetentionPriority-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
— B
BitRate ::= INTEGER (0..10000000000)
— C
Cause ::= CHOICE {
radioNetwork CauseRadioNetwork,
transport CauseTransport,
nAS CauseNAS,
protocol CauseProtocol,
misc CauseMisc,
…
}
CauseMisc ::= ENUMERATED {
control-processing-overload,
hardware-failure,
om-intervention,
unspecified,
…
}
CauseNAS ::= ENUMERATED {
unspecified,
…
}
CauseProtocol ::= ENUMERATED {
transfer-syntax-error,
abstract-syntax-error-reject,
abstract-syntax-error-ignore-and-notify,
message-not-compatible-with-receiver-state,
semantic-error,
abstract-syntax-error-falsely-constructed-message,
unspecified,
…
}
CauseRadioNetwork ::= ENUMERATED {
unknown-or-already-allocated-MCE-MBMS-M2AP-ID,
unknown-or-already-allocated-eNB-MBMS-M2AP-ID,
unknown-or-inconsistent-pair-of-MBMS-M2AP-IDs,
radio-resources-not-available,
interaction-with-other-procedure,
unspecified,
…,
invalid-QoS-combination,
not-supported-QCI-value
}
CauseTransport ::= ENUMERATED {
transport-resource-unavailable,
unspecified,
…
}
Cell-Information ::= SEQUENCE {
eCGI ECGI,
cellReservationInfo ENUMERATED {reservedCell, nonReservedCell, …},
iE-Extensions ProtocolExtensionContainer { { Cell-Information-ExtIEs} } OPTIONAL,
…
}
Cell-Information-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
Cell-Information-List ::= SEQUENCE (SIZE(1..maxnoofCells)) OF Cell-Information
CriticalityDiagnostics ::= SEQUENCE {
procedureCode ProcedureCode OPTIONAL,
triggeringMessage TriggeringMessage OPTIONAL,
procedureCriticality Criticality OPTIONAL,
iEsCriticalityDiagnostics CriticalityDiagnostics-IE-List OPTIONAL,
iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-ExtIEs} } OPTIONAL,
…
}
CriticalityDiagnostics-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
CriticalityDiagnostics-IE-List ::= SEQUENCE (SIZE (1..maxnooferrors)) OF
SEQUENCE {
iECriticality Criticality,
iE-ID ProtocolIE-ID,
typeOfError TypeOfError,
iE-Extensions ProtocolExtensionContainer { {CriticalityDiagnostics-IE-List-ExtIEs} } OPTIONAL,
…
}
CriticalityDiagnostics-IE-List-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
— D
— E
ECGI ::= SEQUENCE {
pLMN-Identity PLMN-Identity,
eUTRANcellIdentifier EUTRANCellIdentifier,
iE-Extensions ProtocolExtensionContainer { {ECGI-ExtIEs} } OPTIONAL,
…
}
ECGI-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
ENB-ID ::= CHOICE {
macro-eNB-ID BIT STRING (SIZE (20)),
… ,
short-Macro-eNB-ID BIT STRING (SIZE(18)),
long-Macro-eNB-ID BIT STRING (SIZE(21))
}
ENB-MBMS-Configuration-data-Item ::= SEQUENCE {
eCGI ECGI,
mbsfnSynchronisationArea MBSFN-SynchronisationArea-ID,
mbmsServiceAreaList MBMS-Service-Area-ID-List,
iE-Extensions ProtocolExtensionContainer { { ENB-MBMS-Configuration-data-Item-ExtIEs} } OPTIONAL,
…
}
ENB-MBMS-Configuration-data-Item-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
ENB-MBMS-Configuration-data-ConfigUpdate-Item ::= CHOICE {
mBMSConfigData ENB-MBMS-Configuration-data-Item,
eCGI ECGI,
…
}
ENB-MBMS-M2AP-ID ::= INTEGER (0..65535)
ENBname ::= PrintableString (SIZE (1..150,…))
EUTRANCellIdentifier ::= BIT STRING (SIZE (28))
— F
— G
GBR-QosInformation ::= SEQUENCE {
mBMS-E-RAB-MaximumBitrateDL BitRate,
mBMS-E-RAB-GuaranteedBitrateDL BitRate,
iE-Extensions ProtocolExtensionContainer { { GBR-QosInformation-ExtIEs} } OPTIONAL,
…
}
GBR-QosInformation-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
GlobalENB-ID ::= SEQUENCE {
pLMN-Identity PLMN-Identity,
eNB-ID ENB-ID,
iE-Extensions ProtocolExtensionContainer { {GlobalENB-ID-ExtIEs} } OPTIONAL,
…
}
GlobalENB-ID-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
GlobalMCE-ID ::= SEQUENCE {
pLMN-Identity PLMN-Identity,
mCE-ID MCE-ID,
iE-Extensions ProtocolExtensionContainer { {GlobalMCE-ID-ExtIEs} } OPTIONAL,
…
}
GlobalMCE-ID-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
GTP-TEID ::= OCTET STRING (SIZE (4))
— H
— I
IPAddress ::= OCTET STRING (SIZE(4..16))
— J
— K
— L
LCID ::= INTEGER (0..28)
— M
MBMS-Cell-List ::= SEQUENCE (SIZE(1.. maxnoofCellsforMBMS)) OF ECGI
MBMS-E-RAB-QoS-Parameters ::= SEQUENCE {
qCI QCI,
gbrQosInformation GBR-QosInformation OPTIONAL,
allocationAndRetentionPriority AllocationAndRetentionPriority,
iE-Extensions ProtocolExtensionContainer { { MBMS-E-RAB-QoS-Parameters-ExtIEs} } OPTIONAL,
…
}
MBMS-E-RAB-QoS-Parameters-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
MBMS-Service-associatedLogicalM2-ConnectionItem ::= SEQUENCE {
eNB-MBMS-M2AP-ID ENB-MBMS-M2AP-ID OPTIONAL,
mCE-MBMS-M2AP-ID MCE-MBMS-M2AP-ID OPTIONAL,
iE-Extensions ProtocolExtensionContainer { { MBMS-Service-associatedLogicalM2-ConnectionItemExtIEs} } OPTIONAL,
…
}
MBMS-Service-associatedLogicalM2-ConnectionItemExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
MBMS-Service-Area ::= OCTET STRING
MBMS-Service-Area-ID-List ::= SEQUENCE (SIZE(1..maxnoofMBMSServiceAreasPerCell)) OF MBMS-Service-Area
MBMS-Session-ID ::= OCTET STRING (SIZE (1))
MBMSsessionListPerPMCH-Item ::= SEQUENCE (SIZE(1..maxnoofSessionsPerPMCH)) OF SEQUENCE {
tmgi TMGI,
lcid LCID,
iE-Extensions ProtocolExtensionContainer { { MBMSsessionListPerPMCH-Item-ExtIEs} } OPTIONAL,
…
}
MBMSsessionListPerPMCH-Item-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
MBMSsessionsToBeSuspendedListPerPMCH-Item ::= SEQUENCE (SIZE(1..maxnoofSessionsPerPMCH)) OF SEQUENCE {
tmgi TMGI,
iE-Extensions ProtocolExtensionContainer { { MBMSsessionsToBeSuspendedListPerPMCH-Item-ExtIEs} } OPTIONAL,
…
}
MBMSsessionsToBeSuspendedListPerPMCH-Item-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
MBSFN-Area-ID ::= INTEGER (0..255)
MBSFN-SynchronisationArea-ID ::= INTEGER (0..65535)
MBSFN-Subframe-Configuration ::= SEQUENCE {
radioframeAllocationPeriod ENUMERATED {n1, n2, n4, n8, n16, n32},
radioframeAllocationOffset INTEGER (0..7),
subframeAllocation CHOICE {
oneFrame BIT STRING (SIZE (6) ),
fourFrames BIT STRING (SIZE (24) ) },
iE-Extensions ProtocolExtensionContainer { { MBSFN-Subframe-Configuration-ExtIEs} } OPTIONAL,
…
}
MBSFN-Subframe-Configuration-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
{ID id-SubframeAllocationExtended CRITICALITY reject EXTENSION SubframeAllocationExtended PRESENCE optional}|
{ID id-SubframeAllocationFurtherExtension CRITICALITY reject EXTENSION SubframeAllocationFurtherExtension PRESENCE optional},
…
}
MCCH-Update-Time ::= INTEGER (0..255)
MCCHrelatedBCCH-ConfigPerMBSFNArea-Item ::= SEQUENCE {
mbsfnArea MBSFN-Area-ID,
pdcchLength ENUMERATED {s1, s2, …},
repetitionPeriod ENUMERATED {rf32, rf64, rf128, rf256},
offset INTEGER (0..10),
modificationPeriod ENUMERATED {rf512, rf1024},
subframeAllocationInfo BIT STRING (SIZE(6)),
modulationAndCodingScheme ENUMERATED {n2, n7, n13, n19},
cellInformationList Cell-Information-List OPTIONAL,
iE-Extensions ProtocolExtensionContainer { { MCCHrelatedBCCH-ConfigPerMBSFNArea-Item-ExtIEs} } OPTIONAL,
…
}
MCCHrelatedBCCH-ConfigPerMBSFNArea-Item-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
— Extension for Rel-14 to support MCCH repetition period values –-
{ID id-Repetition-PeriodExtended CRITICALITY reject EXTENSION Repetition-PeriodExtended PRESENCE optional}|
— Extension for Rel-14 to support MCCH modification period values –-
{ID id-Modification-PeriodExtended CRITICALITY reject EXTENSION Modification-PeriodExtended PRESENCE optional}|
{ID id-Subcarrier-SpacingMBMS CRITICALITY reject EXTENSION Subcarrier-SpacingMBMS PRESENCE optional},
…
}
MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item ::= SEQUENCE {
mbsfnArea MBSFN-Area-ID,
repetitionPeriodExpanded ENUMERATED {rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, …},
offset INTEGER (0..10),
modificationPeriodExpanded ENUMERATED {rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024, …},
subframeAllocationInfoExpanded BIT STRING (SIZE(10)),
modulationAndCodingScheme ENUMERATED {n2, n7, n13, n19},
subcarrier-SpacingMBMSExpanded ENUMERATED {khz-7dot5, khz-2dot5, khz-1dot25, khz-0dot37, …, kHz-15},
timeSeparation ENUMERATED {sl2, sl4, …} OPTIONAL,
cellInformationList Cell-Information-List OPTIONAL,
iE-Extensions ProtocolExtensionContainer { { MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item-ExtIEs} } OPTIONAL,
…
}
MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
— Extension for Rel-17 to support PMCH Bandwidth values –-
{ID id-AdditionalConfigParameters CRITICALITY reject EXTENSION AdditionalConfigParameters PRESENCE optional},
…
}
MCE-ID ::= OCTET STRING (SIZE(2))
MCE-MBMS-M2AP-ID ::= INTEGER (0.. 16777215)
MCEname ::= PrintableString (SIZE (1..150,…))
MCH-Scheduling-Period ::= ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024}
MCH-Scheduling-PeriodExtended ::= ENUMERATED {rf4, …}
MCH-Scheduling-PeriodExtended2 ::= ENUMERATED {rf1, rf2, …}
Modulation-Coding-Scheme2 ::= INTEGER (0..27)
Modification-PeriodExtended ::= ENUMERATED {rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, …}
— N
— O
— P
PLMN-Identity ::= OCTET STRING (SIZE(3))
PMCH-Bandwidth ::= ENUMERATED {n40, n35, n30, …}
PMCH-Configuration ::= SEQUENCE {
allocatedSubframesEnd AllocatedSubframesEnd,
dataMCS INTEGER (0..28),
mchSchedulingPeriod MCH-Scheduling-Period,
iE-Extensions ProtocolExtensionContainer { {PMCH-Configuration-ExtIEs} } OPTIONAL,
…
}
PMCH-Configuration-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
— Extension for Rel-12 to support 256QAM for MTCH –
{ID id-Modulation-Coding-Scheme2 CRITICALITY reject EXTENSION Modulation-Coding-Scheme2 PRESENCE optional}|
— Extension for Rel-12 to support shorter MCH scheduling period –
{ID id-MCH-Scheduling-PeriodExtended CRITICALITY reject EXTENSION MCH-Scheduling-PeriodExtended PRESENCE optional}|
— Extension for Rel-14 to support shorter MCH scheduling period values –
{ID id-MCH-Scheduling-PeriodExtended2 CRITICALITY reject EXTENSION MCH-Scheduling-PeriodExtended2 PRESENCE optional},
…
}
Common-Subframe-Allocation-Period ::= ENUMERATED {rf4, rf8, rf16, rf32, rf64, rf128, rf256}
Pre-emptionCapability ::= ENUMERATED {
shall-not-trigger-pre-emption,
may-trigger-pre-emption
}
Pre-emptionVulnerability ::= ENUMERATED {
not-pre-emptable,
pre-emptable
}
PriorityLevel ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15)
— Q
QCI ::= INTEGER (0..255)
— R
Repetition-PeriodExtended ::= ENUMERATED {rf1, rf2, rf4, rf8, rf16, …}
— S
SC-PTM-Information ::= SEQUENCE {
mbmsCellList MBMS-Cell-List,
mbms-E-RAB-QoS-Parameters MBMS-E-RAB-QoS-Parameters,
iE-Extensions ProtocolExtensionContainer { {SC-PTM-Information-ExtIEs} } OPTIONAL,
…
}
SC-PTM-Information-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
SFN ::= INTEGER (0..1023)
Subcarrier-SpacingMBMS ::= ENUMERATED {khz-7dot5, khz-1dot25, …}
SubframeAllocationExtended ::= CHOICE {
oneFrameExtension BIT STRING (SIZE(2)),
fourFrameExtension BIT STRING (SIZE(8)),
choice-extension ProtocolIE-Single-Container { { SubframeAllocationExtended-ExtIEs} },
…
}
SubframeAllocationExtended-ExtIEs M2AP-PROTOCOL-IES ::= { …
}
SubframeAllocationFurtherExtension ::= CHOICE {
oneFrameFurtherExtension BIT STRING (SIZE(2)),
fourFrameFurtherExtension BIT STRING (SIZE(8)),
choice-extension ProtocolIE-Single-Container { { SubframeAllocationFurtherExtension-ExtIEs} },
…
}
SubframeAllocationFurtherExtension-ExtIEs M2AP-PROTOCOL-IES ::= { …
}
— T
TimeToWait ::= ENUMERATED {v1s, v2s, v5s, v10s, v20s, v60s, …}
TMGI ::= SEQUENCE {
pLMNidentity PLMN-Identity,
serviceID OCTET STRING (SIZE (3)),
iE-Extensions ProtocolExtensionContainer { {TMGI-ExtIEs} } OPTIONAL,
…
}
TMGI-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
TNL-Information ::= SEQUENCE {
iPMCAddress IPAddress,
iPSourceAddress IPAddress,
gTP-TEID GTP-TEID,
iE-Extensions ProtocolExtensionContainer { {TNL-Information-ExtIEs} } OPTIONAL,
…
}
TNL-Information-ExtIEs M2AP-PROTOCOL-EXTENSION ::= {
…
}
TypeOfError ::= ENUMERATED {
not-understood,
missing,
…
}
— U
— V
— W
— X
— Y
— Z
END
9.3.6 Common definitions
— **************************************************************
—
— Common definitions
—
— **************************************************************
M2AP-CommonDataTypes {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) m2ap (4) version1 (1) m2ap-CommonDataTypes (3) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
— **************************************************************
—
— Extension constants
—
— **************************************************************
maxPrivateIEs INTEGER ::= 65535
maxProtocolExtensions INTEGER ::= 65535
maxProtocolIEs INTEGER ::= 65535
— **************************************************************
—
— Common Data Types
—
— **************************************************************
Criticality ::= ENUMERATED { reject, ignore, notify }
Presence ::= ENUMERATED { optional, conditional, mandatory }
PrivateIE-ID ::= CHOICE {
local INTEGER (0.. maxPrivateIEs),
global OBJECT IDENTIFIER
}
ProcedureCode ::= INTEGER (0..255)
ProtocolIE-ID ::= INTEGER (0..maxProtocolIEs)
TriggeringMessage ::= ENUMERATED { initiating-message, successful-outcome, unsuccessful-outcome}
END
9.3.7 Constant definitions
— **************************************************************
—
— Constant definitions
—
— **************************************************************
M2AP-Constants {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) m2ap (4) version1 (1) m2ap-Constants (4) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
IMPORTS
ProcedureCode,
ProtocolIE-ID
FROM M2AP-CommonDataTypes;
— **************************************************************
—
— Elementary Procedures
—
— **************************************************************
id-sessionStart ProcedureCode ::= 0
id-sessionStop ProcedureCode ::= 1
id-mbmsSchedulingInformation ProcedureCode ::= 2
id-errorIndication ProcedureCode ::= 3
id-reset ProcedureCode ::= 4
id-m2Setup ProcedureCode ::= 5
id-eNBConfigurationUpdate ProcedureCode ::= 6
id-mCEConfigurationUpdate ProcedureCode ::= 7
id-privateMessage ProcedureCode ::= 8
id-sessionUpdate ProcedureCode ::= 9
id-mbmsServiceCounting ProcedureCode ::= 10
id-mbmsServiceCountingResultsReport ProcedureCode ::= 11
id-mbmsOverloadNotification ProcedureCode ::= 12
— **************************************************************
—
— Lists
—
— **************************************************************
maxnoofMBSFNareas INTEGER ::= 256
maxnoofMBSFN-Allocations INTEGER ::= 8
maxnoofPMCHsperMBSFNarea INTEGER ::= 15
maxnoofCells INTEGER ::= 256
maxnoofMBMSServiceAreasPerCell INTEGER ::= 256
maxnoofSessionsPerPMCH INTEGER ::= 29
maxnooferrors INTEGER ::= 256
maxNrOfIndividualM2ConnectionsToReset INTEGER ::= 256
maxnoofCountingService INTEGER ::= 16
maxnoofCellsforMBMS INTEGER ::= 4096
— **************************************************************
—
— Ies
—
— **************************************************************
id-MCE-MBMS-M2AP-ID ProtocolIE-ID ::= 0
id-ENB-MBMS-M2AP-ID ProtocolIE-ID ::= 1
id-TMGI ProtocolIE-ID ::= 2
id-MBMS-Session-ID ProtocolIE-ID ::= 3
id-MBMS-Service-Area ProtocolIE-ID ::= 6
id-TNL-Information ProtocolIE-ID ::= 7
id-CriticalityDiagnostics ProtocolIE-ID ::= 8
id-Cause ProtocolIE-ID ::= 9
id-MBSFN-Area-Configuration-List ProtocolIE-ID ::= 10
id-PMCH-Configuration-List ProtocolIE-ID ::= 11
id-PMCH-Configuration-Item ProtocolIE-ID ::= 12
id-GlobalENB-ID ProtocolIE-ID ::= 13
id-ENBname ProtocolIE-ID ::= 14
id-ENB-MBMS-Configuration-data-List ProtocolIE-ID ::= 15
id-ENB-MBMS-Configuration-data-Item ProtocolIE-ID ::= 16
id-GlobalMCE-ID ProtocolIE-ID ::= 17
id-MCEname ProtocolIE-ID ::= 18
id-MCCHrelatedBCCH-ConfigPerMBSFNArea ProtocolIE-ID ::= 19
id-MCCHrelatedBCCH-ConfigPerMBSFNArea-Item ProtocolIE-ID ::= 20
id-TimeToWait ProtocolIE-ID ::= 21
id-MBSFN-Subframe-Configuration-List ProtocolIE-ID ::= 22
id-MBSFN-Subframe-Configuration-Item ProtocolIE-ID ::= 23
id-Common-Subframe-Allocation-Period ProtocolIE-ID ::= 24
id-MCCH-Update-Time ProtocolIE-ID ::= 25
id-ENB-MBMS-Configuration-data-List-ConfigUpdate ProtocolIE-ID ::= 26
id-ENB-MBMS-Configuration-data-ConfigUpdate-Item ProtocolIE-ID ::= 27
id-MBMS-Service-associatedLogicalM2-ConnectionItem ProtocolIE-ID ::= 28
id-MBSFN-Area-ID ProtocolIE-ID ::= 29
id-ResetType ProtocolIE-ID ::= 30
id-MBMS-Service-associatedLogicalM2-ConnectionListResAck ProtocolIE-ID ::= 31
id-MBMS-Counting-Request-Session ProtocolIE-ID ::= 32
id-MBMS-Counting-Request-Session-Item ProtocolIE-ID ::= 33
id-MBMS-Counting-Result-List ProtocolIE-ID ::= 34
id-MBMS-Counting-Result-Item ProtocolIE-ID ::= 35
id-Modulation-Coding-Scheme2 ProtocolIE-ID ::= 36
id-MCH-Scheduling-PeriodExtended ProtocolIE-ID ::= 37
id-Alternative-TNL-Information ProtocolIE-ID ::= 38
id-Overload-Status-Per-PMCH-List ProtocolIE-ID ::= 39
id-PMCH-Overload-Status ProtocolIE-ID ::= 41
id-Active-MBMS-Session-List ProtocolIE-ID ::= 42
id-MBMS-Suspension-Notification-List ProtocolIE-ID ::= 43
id-MBMS-Suspension-Notification-Item ProtocolIE-ID ::= 44
id-SC-PTM-Information ProtocolIE-ID ::= 45
id-Modification-PeriodExtended ProtocolIE-ID ::= 46
id-Repetition-PeriodExtended ProtocolIE-ID ::= 47
id-MCH-Scheduling-PeriodExtended2 ProtocolIE-ID ::= 48
id-Subcarrier-SpacingMBMS ProtocolIE-ID ::= 49
id-SubframeAllocationExtended ProtocolIE-ID ::= 50
id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea-Item ProtocolIE-ID ::= 51
id-MCCHrelatedBCCH-ExtConfigPerMBSFNArea ProtocolIE-ID ::= 52
id-SubframeAllocationFurtherExtension ProtocolIE-ID ::= 53
id-AdditionalConfigParameters ProtocolIE-ID ::= 54
END
9.3.8 Container definitions
— **************************************************************
—
— Container definitions
—
— **************************************************************
M2AP-Containers {
itu-t (0) identified-organization (4) etsi (0) mobileDomain (0)
eps-Access (21) modules (3) m2ap (4) version1 (1) m2ap-Containers (5) }
DEFINITIONS AUTOMATIC TAGS ::=
BEGIN
— **************************************************************
—
— IE parameter types from other modules.
—
— **************************************************************
IMPORTS
maxPrivateIEs,
maxProtocolExtensions,
maxProtocolIEs,
Criticality,
Presence,
PrivateIE-ID,
ProtocolIE-ID
FROM M2AP-CommonDataTypes;
— **************************************************************
—
— Class Definition for Protocol Ies
—
— **************************************************************
M2AP-PROTOCOL-IES ::= CLASS {
&id ProtocolIE-ID UNIQUE,
&criticality Criticality,
&Value,
&presence Presence
}
WITH SYNTAX {
ID &id
CRITICALITY &criticality
TYPE &Value
PRESENCE &presence
}
— **************************************************************
—
— Class Definition for Protocol Ies
—
— **************************************************************
M2AP-PROTOCOL-IES-PAIR ::= CLASS {
&id ProtocolIE-ID UNIQUE,
&firstCriticality Criticality,
&FirstValue,
&secondCriticality Criticality,
&SecondValue,
&presence Presence
}
WITH SYNTAX {
ID &id
FIRST CRITICALITY &firstCriticality
FIRST TYPE &FirstValue
SECOND CRITICALITY &secondCriticality
SECOND TYPE &SecondValue
PRESENCE &presence
}
— **************************************************************
—
— Class Definition for Protocol Extensions
—
— **************************************************************
M2AP-PROTOCOL-EXTENSION ::= CLASS {
&id ProtocolIE-ID UNIQUE,
&criticality Criticality,
&Extension,
&presence Presence
}
WITH SYNTAX {
ID &id
CRITICALITY &criticality
EXTENSION &Extension
PRESENCE &presence
}
— **************************************************************
—
— Class Definition for Private Ies
—
— **************************************************************
M2AP-PRIVATE-IES ::= CLASS {
&id PrivateIE-ID,
&criticality Criticality,
&Value,
&presence Presence
}
WITH SYNTAX {
ID &id
CRITICALITY &criticality
TYPE &Value
PRESENCE &presence
}
— **************************************************************
—
— Container for Protocol Ies
—
— **************************************************************
ProtocolIE-Container {M2AP-PROTOCOL-IES : IesSetParam} ::=
SEQUENCE (SIZE (0..maxProtocolIEs)) OF
ProtocolIE-Field {{IesSetParam}}
ProtocolIE-Single-Container {M2AP-PROTOCOL-IES : IesSetParam} ::=
ProtocolIE-Field {{IesSetParam}}
ProtocolIE-Field {M2AP-PROTOCOL-IES : IesSetParam} ::= SEQUENCE {
id M2AP-PROTOCOL-IES.&id ({IesSetParam}),
criticality M2AP-PROTOCOL-IES.&criticality ({IesSetParam}{@id}),
value M2AP-PROTOCOL-IES.&Value ({IesSetParam}{@id})
}
— **************************************************************
—
— Container for Protocol IE Pairs
—
— **************************************************************
ProtocolIE-ContainerPair {M2AP-PROTOCOL-IES-PAIR : IesSetParam} ::=
SEQUENCE (SIZE (0..maxProtocolIEs)) OF
ProtocolIE-FieldPair {{IesSetParam}}
ProtocolIE-FieldPair {M2AP-PROTOCOL-IES-PAIR : IesSetParam} ::= SEQUENCE {
id M2AP-PROTOCOL-IES-PAIR.&id ({IesSetParam}),
firstCriticality M2AP-PROTOCOL-IES-PAIR.&firstCriticality ({IesSetParam}{@id}),
firstValue M2AP-PROTOCOL-IES-PAIR.&FirstValue ({IesSetParam}{@id}),
secondCriticality M2AP-PROTOCOL-IES-PAIR.&secondCriticality ({IesSetParam}{@id}),
secondValue M2AP-PROTOCOL-IES-PAIR.&SecondValue ({IesSetParam}{@id})
}
— **************************************************************
—
— Container Lists for Protocol IE Containers
—
— **************************************************************
ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, M2AP-PROTOCOL-IES : IesSetParam} ::=
SEQUENCE (SIZE (lowerBound..upperBound)) OF
ProtocolIE-Container {{IesSetParam}}
ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, M2AP-PROTOCOL-IES-PAIR : IesSetParam} ::=
SEQUENCE (SIZE (lowerBound..upperBound)) OF
ProtocolIE-ContainerPair {{IesSetParam}}
— **************************************************************
—
— Container for Protocol Extensions
—
— **************************************************************
ProtocolExtensionContainer {M2AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::=
SEQUENCE (SIZE (1..maxProtocolExtensions)) OF
ProtocolExtensionField {{ExtensionSetParam}}
ProtocolExtensionField {M2AP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE {
id M2AP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}),
criticality M2AP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}),
extensionValue M2AP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id})
}
— **************************************************************
—
— Container for Private Ies
—
— **************************************************************
PrivateIE-Container {M2AP-PRIVATE-IES : IesSetParam} ::=
SEQUENCE (SIZE (1..maxPrivateIEs)) OF
PrivateIE-Field {{IesSetParam}}
PrivateIE-Field {M2AP-PRIVATE-IES : IesSetParam} ::= SEQUENCE {
id M2AP-PRIVATE-IES.&id ({IesSetParam}),
criticality M2AP-PRIVATE-IES.&criticality ({IesSetParam}{@id}),
value M2AP-PRIVATE-IES.&Value ({IesSetParam}{@id})
}
END
9.4 Message Transfer Syntax
M2AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax as specified in ref. ITU-T Rec. X.691 [5].