ETSI TS 102 744-3-7 V1.1.1 (2015-10)

Satellite Earth Stations and Systems (SES); Family SL Satellite Radio Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 7: NAS Layer Interface Extensions for MBMS Services

DTS/SES-00299-3-7

General Information

• Status: Published
• Publication Date: 25-Oct-2015
• Technical Committee: SES SCN - Satellite Communications and Navigation
• Current Stage: 12 - Completion
• Due Date: 25-Sep-2015
• Completion Date: 26-Oct-2015

Standards Content (Sample)

TECHNICAL SPECIFICATION
Satellite Earth Stations and Systems (SES);
Family SL Satellite Radio Interface (Release 1);
Part 3: Control Plane and User Plane Specifications;
Sub-part 7: NAS Layer Interface Extensions
for MBMS Services
�
2 ETSI TS 102 744-3-7 V1.1.1 (2015-10)

Reference
DTS/SES-00299-3-7
Keywords
3GPP, GPRS, GSM, GSO, interface, MSS, radio,
satellite, TDM, TDMA, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 5
1 Scope . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Symbols and abbreviations . 7
3.1 Symbols . 7
3.2 Abbreviations . 7
4 Introduction . 7
4.1 Non-Access Stratum Layer. 7
4.2 Conventions used in the present document . 8
4.2.1 Presentation. 8
4.2.2 "Reserved" Fields and Values . 9
4.2.3 Boolean Variables . 9
4.2.4 ASN.1 Encoding Rules . 9
5 NAS Layer Interface . 9
5.1 NAS layer use of AL service access points . 9
5.2 NAS Layer MBMS Service Management Messages . 9
6 NAS Layer Protocol Data Units . 10
6.1 General NAS PDU Structure . 10
6.1.0 General . 10
6.1.1 NAS PDU Header Common Elements . 11
6.1.1.1 TransactionIdentifier (TI) . 11
6.1.1.2 ProtocolDiscriminator . 11
6.1.1.3 NasMessageType . 12
6.2 Format of standard information elements . 12
6.3 NAS MBMS Service Management Messages . 13
6.3.1 ActivatePDPContextRequest . 13
6.3.1.0 General . 13
6.3.1.1 nsapi (Network Service Access Point Identifier) . 14
6.3.1.2 requested-llcsapi . 14
6.3.1.3 requested-pdp-address (PDPAddress) . 14
6.3.1.4 apn (Access Point Name) . 15
6.3.1.5 requested-qos (QualityOfService) . 15
6.3.2 ActivatePDPContextAccept . 15
6.3.2.0 General . 15
6.3.2.1 negotiated-llc-sapi . 16
6.3.3 ActivatePDPContextReject . 16
6.3.3.0 General . 16
6.3.3.1 SMCause . 17
6.3.4 ActivateSecondaryContextRequest . 17
6.3.4.0 General . 17
6.3.4.1 nsapi (Network Service Access Point Identifier) . 18
6.3.4.2 requested-llcsapi . 18
6.3.4.3 linked-ti (Linked TI) . 18
6.3.4.4 traffic-flow-template (TFT). 18
6.3.4.5 requested-qos (QualityOfService) . 18
6.3.5 ActivateSecondaryContextAccept . 19
6.3.6 ActivateSecondaryContextReject . 20
6.3.6.0 General . 20
ETSI
4 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
6.3.6.1 SMCause . 20
6.3.7 DeactivatePDPContextRequest . 20
6.3.7.0 General . 20
6.3.7.1 tear-down-indicator . 21
6.3.8 DeactivatePDPContextAccept . 21
6.4 ActivateMBMSContextRequest . 22
6.5 ActivateMBMSContextAccept . 23
6.6 ActivateMBMSContextReject . 24
6.7 RequestMBMSContextActivation . 25
6.8 RequestMBMSContextActivationReject. 26
7 Information Elements Coding . 27
7.1 Access Point Na me . 27
7.2 Network service access point identifier (NSAPI) . 27
7.3 LLC SAPI . 27
7.4 Protocol configuration options . 27
7.4.0 General . 27
7.4.1 UE supporting ARP proxy functionality . 28
7.4.2 UE Supporting PPP (or PPPoE) interface . 28
7.5 Packet Data Protocol Address . 29
7.5.0 General . 29
7.5.1 pdp-type-organisation . 29
7.5.2 pdp-type-number . 29
7.5.3 PDPAddressInfo . 29
7.6 Quality of Service . 29
7.7 Linked TI . 31
7.8 Tear Down Indicator . 31
7.9 Packet Flow Identifier . 32
7.10 Traffic Flow Template . 32
7.11 TMGI . 34
7.12 MBMS Bearer capabilities . 35
7.13 MBMS protocol configuration options. 36
7.14 SM Cause . 37
Annex A (normative): ASN.1 . 38
Annex B (informative): Example Configure-Request for Dynamic Address allocation . 39
History . 41

ETSI
5 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Satellite Earth Stations and
Systems (SES).
The present document is part 3, sub-part 7 of a multi-part deliverable. Full details of the entire series can be found in
ETSI TS 102 744-1-1 [6].
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Introduction
This multi-part deliverable (Release 1) defines a satellite radio interface that provides UMTS services to users of mobile
terminals via geostationary (GEO) satellites in the frequency range 1 518,000 MHz to 1 559,000 MHz (downlink) and
1 626,500 MHz to 1 660,500 MHz and 1 668,000 MHz to 1 675,000 MHz (uplink).
ETSI
6 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
1 Scope
The present document defines the extension to the Non-Access Stratum (NAS) Layer peer-to-peer interface (defined in
ETSI TS 124 007 [1] and ETSI TS 124 008 [2]) of the Family SL satellite radio interface between the Radio Network
Controller (RNC) and the User Equipment (UE) used in the satellite network, that is required in order to support MBMS
services.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 124 007: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Mobile radio interface signalling layer 3; General Aspects
(3GPP TS 24.007 Release 4)".
[2] ETSI TS 124 008: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); Mobile radio interface Layer 3 specification; Core network
protocols; Stage 3 (3GPP TS 24.008 Release 4)".
[3] ETSI TS 123 003: "Digital cellular telecommunications system (Phase 2+) (GSM); Universal
Mobile Telecommunications System (UMTS); Numbering, Addressing and Identification
(3GPP TS 23.003 Release 4)".
[4] IETF RFC 1661 (1994): "The Point-to-Point Protocol (PPP)".
[5] IETF RFC 1332 (1992): "The PPP Internet Protocol Control Protocol (IPCP)".
[6] ETSI TS 102 744-1-1: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 1: General Specifications; Sub-part 1: Services and Architectures".
[7] ETSI TS 102 744-1-4: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 1: General Specifications; Sub-part 4: Applicable External
Specifications, Symbols and Abbreviations".
[8] ETSI TS 102 744-3-1: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 1: Bearer
Control Layer Interface".
[9] ETSI TS 102 744-3-5: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 5: Adaptation
Layer Interface".
[10] ETSI TS 102 744-3-6: "Satellite Earth Stations and Systems (SES); Family SL Satellite Radio
Interface (Release 1); Part 3: Control Plane and User Plane Specifications; Sub-part 6: Adaptation
Layer Operation".
ETSI
7 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] 3GPP TR 29.846: "3rd Generation Partnership Project (3GPP); Technical Specification Group
Core Networks; Multimedia Broadcast/Multicast Service (MBMS); CN1 procedure description
(Release 4)".
3 Symbols and abbreviations
3.1 Symbols
For the purposes of the present document, the symbols in clause 3 of ETSI TS 102 744-1-4 [7] apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations in clause 3 of ETSI TS 102 744-1-4 [7] apply.
4 Introduction
4.1 Non-Access Stratum Layer
The Non-Access Stratum (NAS) Layer provides support to the Internet Protocol (IP) Layer via the User Plane Handler
(UPH), and uses the services provided by the Adaptation Layer (AL).
The IP Layer provides support to routing protocols, such as the Internet Group Management Protocol (IGMP) used by
IPv4 systems to report their IP multicast group memberships to neighbouring multicast routers. The IGMP protocol (or
PIM-SM) is used to trigger the supported multicast services. Session management (SM) messages are used to instantiate
the MBMS contexts. The Adaptation Layer interface and operation is described in ETSI TS 102 744-3-5 [9] and
ETSI TS 102 744-3-6 [10] respectively.
The present document defines the extension to the NAS Layer peer-to-peer interface (defined in ETSI TS 124 007 [1]
and ETSI TS 124 008 [2]) between the RNC and the UE that is required in order to support MBMS services, as shown
in Figure 4.1.
All of the messages defined in the present document to replace functionality in 3GPP are Session Management
messages. All other messages not specified in the present document but that appear in 3GPP Release 4 should still be
supported.
ETSI
8 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
IP
IP
UPH UPH
BMSM BMSM
RABM/
MRABM
BMM BMM
Non-Access Stratum
RE LA Y
AL AL RANAP RANAP
Lower Lower
Lower Layers Lower Layers
Layers Layers
Access Stratum
UE RNC CN
U I
sl u
Figure 4.1: Satellite Network Higher Layers (NAS and IP)
The NAS Layer is responsible for the following:
• Multicast Radio Access Bearer Manager (MRABM): is responsible for controlling establishment,
modification and termination of Access Stratum Unicast Radio Access Bearers (RABs) and Multicast Radio
Access Bearers (MRABs) on the Iu-Broadcast Multicast (BM) interface towards the RAN.
• Broadcast/Multicast Mobility Management (BMM): is responsible for mobility management for a UE
which is operating with the BM domain. The BMM entity replicates the functionality of the GPRS Mobility
Management (GMM) entity towards the Broadcast Multicast Service Node (BMSN).
• Broadcast/Multicast Session Management (BMSM): is responsible in the for NAS signalling towards the
BM domain, replicating the functionality of the Session Management (SM) entity for establishing and
maintaining the Radio Access Bearer (RAB) endpoints for BM domain traffic handling. Within the BMSM
entity, the state of each Packet Data Protocol (PDP) Context, and the association with activated MBMS
Contexts is maintained.
It should be noted that the BMSM entity is the only entity for which a modification to the associated Packet Switched
domain NAS Layer behaviour and peer-peer interface is required, the extensions to this interface being specified within
the present document.
4.2 Conventions used in the present document
4.2.1 Presentation
The following conventions are applied throughout the present document:
• In the ASN.1, variable names are always in lower case letters with hyphenation used to improve readability
(e.g. message-type). Data Types in the ASN.1 always start with an upper case letter and may contain
additional upper case letters to improve readability (e.g. MessageType).
• In the explanatory text these variables are referred to in italics (.e.g. message-type) while Data Types are
shown in Helvetica typeface (e.g. BCnPDU).
ETSI
9 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
The layout of the data structures defined in the ASN.1 is also shown in a graphical representation. In general, the
variable names are presented in the same way they are presented in the ASN.1, with the following exceptions:
• insufficient space does not allow the complete variable name to be presented and is therefore abbreviated;
• only one particular value can be assigned to a variable in the particular structure that is presented. In this case
the variable is replaced by the appropriate numerical value;
• additional information may be added in brackets for explanatory reasons.
4.2.2 "Reserved" Fields and Values
Fields shown as Reserved BITSTRING (.) in the ASN.1 structures shall be set to zero by the sender and shall be
ignored by the receiver.
Values not allocated in distinguished value lists shall not be used by the sender and shall be ignored by the receiver.
NOTE: Distinguished Value Lists of type Integer are being used instead of the ENUMERATED data type, where
the allocated number range is larger than the number of items to be enumerated.
4.2.3 Boolean Variables
BOOLEAN variables shall be encoded as follows:
TRUE ::= 1
FALSE ::= 0
4.2.4 ASN.1 Encoding Rules
The ASN.1 presentation provided in the present document for this interface specification is normative. The encoding
rules used for this interface specification are provided in clause 4.4.4 of ETSI TS 102 744-3-1 [8].
5 NAS Layer Interface
5.1 NAS layer use of AL service access points
Protocol entities in the NAS Layer use message transport services provided by the Adaptation Layer to communicate
with their peers through two Service Access Points (SAPs):
• MMAL-SAP: MM to Adaptation Layer Service Access Point (CS domain)
• GMMAL-SAP: GMM to Adaptation Layer Service Access Point (PS domain)
• BMMAL-SAP: BMM to Adaptation Layer Service Access Point (BM domain)
These service access points are described in more detail in ETSI TS 102 744-3-6 [10].
5.2 NAS Layer MBMS Service Management Messages
The NAS Layer MBMS Service Management messages shown in Table 5.1 are supported between the UE and BMSN.
The interfaces between the UE and the BMSN are shown in Figure 7.1 in ETSI TS 102 744-1-1 [6].
ETSI
10 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
Table 5.1: Multicast NAS messages
NAS Message Direction Key Parameters
Activate_PDPContext_Request UEBMSN TI, Requested NSAPI, Requested QoS, Requested
PDPAddress, APN, Protocol Config Options
Activate_PDPContext_Accept UEBMSN TI, Negotiated QoS, PDPAddress, Protocol Config Options
Activate_PDPContext_Reject UEBMSN TI, SMCause
Deactivate_PDPContext_Request UEBMSN TI, SMCause
UEBMSN
Deactivate_PDPContext_Accept UEBMSN TI
UEBMSN
Request_MBMSContext_Activation UEBMSN TI, Linked NSAPI, Offered MulticastAddress, APN, TFT,
TMGI
Request_MBMSContext_Activation_ UEBMSN TI, SMCause
Reject
Activate_MBMSContext_Request UEBMSN TI, Requested MBMS NSAPI, Supported MBMS Bearer
Capabilities, Requested Multicast address, APN, Linked TI,
TMGI, MBMS Protocol Config Options
Activate_MBMSContext_Accept UEBMSN TI, TMGI
Activate_MBMSContext_Reject UEBMSN TI, SMCause
Activate_SecPDPContext_Request UEBMSN TI, Requested NSAPI, Requested QoS, Linked TI, TFT,
Protocol Config Options
Activate_SecPDPContext_ Accept UEBMSN TI, Negotiated QoS,
Protocol Config Options
Activate_SecPDPContext_ Reject UEBMSN TI, SMCause

6 NAS Layer Protocol Data Units
6.1 General NAS PDU Structure
6.1.0 General
The following sections define the format of the Protocol Data Units (PDUs) which are used by the NAS Layer to signal
its peer (NAS-PDUs). The proposed format is similar to the 3GPP L3 messages as defined in ETSI TS 124 007 [1]. This
means that the message consists of the following parts:
• protocol discriminator;
• transaction identifier;
• message type;
• other information elements, as required.
The general NAS message format is shown in Figure 6.1.
(MSB)        Bit No         (LSB)
8 7 6 5 4 3 2 1
transaction-identifier protocol-discriminator Octet 1
transaction-identifier-extension (conditional) Octet2
nas-message-type
nas-message
Figure 6.1: General NAS PDU format
ETSI
11 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
The general format of a NAS PDU can be considered as follows:
NasPDU ::= SEQUENCE {
nas-header NasHeader,
nas-message-type NasMessageType,
nas-message NasMessage
}
Where the NAS Header consists of the following:
NasHeader::= SEQUENCE {
transaction-identifier TransactionIdentifier,
protocol-discriminator ProtocolDiscriminator,
transaction-identifier-extension TIE OPTIONAL
}
6.1.1 NAS PDU Header Common Elements
6.1.1.1 TransactionIdentifier (TI)
The transaction identifier and its use are defined in ETSI TS 124 007 [1].
The TI is defined in ETSI TS 124 007 [1] to half an octet in length, with an option to extend the TI to one and half octet.
The structure of TI is as shown in Figure 6.2.
(MSB) Bit No (LSB)
8 7 6 5 4 3 2 1
ti tio protocol-discriminator Octet 1
ext
tie Octet2
Figure 6.2: Transaction Identifier format
Two identical TI values may be used when each value pertains to a transaction initiated by the different sides of the
interface. In this case the TI flag shall avoid ambiguity. The transaction identifier flag can take the values "0" or "1".
The TI flag is used to identify which side of the interface initiated the transaction. A message has a TI flag set to "0"
when it belongs to transaction initiated by its sender, and to "1" otherwise. Hence the TI flag identifies who allocated
the TI value for this transaction and the only purpose of the TI flag is to resolve simultaneous attempts to allocate the
same TI value.
The TIE shall not be used unless TI values of 7 or greater are needed.
The transaction-identifier parameter is of type TransactionIdentifier which is defined as follows:
TransactionIdentifier ::=
SEQUENCE {
ti TI,
tio TIO
}
TI ::= BOOLEAN;
--FALSE if transaction initiated by its sender,TRUE otherwise
TIO ::= INTEGER(0.7);
--If TIO(7), the TI value is given by the TIE in octet 2

The extended transaction identifier parameter is of type TIE, is only present if TIO has value 7, and is defined as
follows:
TIE ::= INTEGER(0.127);
-- TIE(0-6) Reserved
6.1.1.2 ProtocolDiscriminator
The Protocol Discriminator (PD) and its use are defined in ETSI TS 124 007 [1]. Normally the PD is half octet length
with all values reserved. All NAS messages towards the BM domain shall utilize a half-octet long PD, adopting the
binary value of '1010', representing GPRS Session Management messages.
ETSI
12 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
The protocol-discriminator parameter is of type ProtocolDiscriminator which is defined as follows:
ProtocolDiscriminator ::=
INTEGER {
Session Management (10)
} (0.15)
6.1.1.3 NasMessageType
The message type Information Element (IE) and its use are defined in ETSI TS 124 007 [1]. The values used towards
the BM domain are as specified for GPRS Session Management and are shown in Table 6.1.
Table 6.1: Multicast message type values relevant to the BM domain
Bits
8 7 6 5 4 3 2 1
0 1 - - - - - - Session management messages

0 1 0 0 0 0 0 1 Activate PDP context request
0 1 0 0 0 0 1 0 Activate PDP context accept
0 1 0 0 0 0 1 1 Activate PDP context reject

0 1 0 0 0 1 1 0 Deactivate PDP context request
0 1 0 0 0 1 1 1 Deactivate PDP context accept

0 1 0 0 1 1 0 1 Activate secondary PDP context request
0 1 0 0 1 1 1 0 Activate secondary PDP context accept
0 1 0 0 1 1 1 1 Activate secondary PDP context reject

0 1 0 1 0 1 1 0 Activate MBMS Context Request
0 1 0 1 0 1 1 1 Activate MBMS Context Accept
0 1 0 1 1 0 0 0 Activate MBMS Context Reject
0 1 0 1 1 0 0 1 Request MBMS Context Activation
0 1 0 1 1 0 1 0 Request MBMS Context Activation Reject

NasMessageType ::=
INTEGER {
ActivatePDPContextRequest (65),
ActivatePDPContextAccept (66),
ActivatePDPContextReject (67),
DeactivatePDPContextRequest (70),
DeactivatePDPContextAccept (71),
ActivateSecondaryPDPContextRequest (77),
ActivateSecondaryPDPContextAccept (78),
ActivateSecondaryPDPContextReject (79),
ActivateMBMSContextRequest (86),
ActivateMBMSContextAccept (87),
ActivateMBMSContextReject (88),
RequestMBMSContextActivation (89),
RequestMBMSContextActivationReject (90),
} (0.255)
6.2 Format of standard information elements
Standard IE and its use are defined in ETSI TS 124 007 [1] and may have the following parts, in that order:
• an information element identifier (IEI) ;
• a length indicator (LI);
• a value part.
ETSI
13 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
A standard IE has one of the formats shown in Table 6.2.
Table 6.2: Formats of information elements
Format Meaning IEI present LI present Value part present
T Type only yes No no
V Value only no No yes
TV Type and Value yes No yes
LV Length and Value no Yes yes
TLV Type, Length and Value yes Yes yes

6.3 NAS MBMS Service Management Messages
NAS PDUs containing NAS messages transferred in the UE-BMSN direction are carried within a
UplinkDirectTransfer Adaptation Layer (AL) messages, while NAS PDUs transferred in the BMSN-UE direction are
carried within DownlinkDirectTransfer AL messages (see ETSI TS 102 744-3-5 [9]). The NAS messages are passed
transparently through the RNC.
NASMessage ::= CHOICE {
empty-sig NULL,
activate-pdp-context-request ActivatePDPContextRequest,
activate-pdp-context-accept ActivatePDPContextAccept,
activate-pdp-context-reject ActivatePDPContextReject,
deactivate-pdp-context-request DeactivatePDPContextRequest,
deactivate-pdp-context-accept DeactivatePDPContextAccept
activate-sec-context-request ActivateSecondaryContextRequest,
activate-sec-context-accept ActivateSecondaryContextAccept,
activate-sec-context-reject ActivateSecondaryContextReject,
activate-mbms-context-request ActivateMBMSContextRequest,
activate-mbms-context-accept ActivateMBMSContextAccept,
activate-mbms-context-reject ActivateMBMSContextReject,
request-mbms-context-activate RequestMBMSContextActivate,
request-mbms-context-reject RequestMBMSContextReject
}
6.3.1 ActivatePDPContextRequest
6.3.1.0 General
The ActivatePDPContextRequest NAS message is used by the UE to access services within the BM domain as
referenced by the Access Point Name (APN).
If the UE is GPRS Attached, the UE transmits an ActivatePDPContextRequest(NSAPI, APN) NAS message to the
RAN encapsulated in an UplinkDirectTransfer AL message towards the BM-domain. The RAN identifies that this
NAS message contains a message for the multicast domain and forwards the ActivatePDPContextRequest(NSAPI,
APN) to the BMSN via the Iu interface using a InitialDirectTransfer (specifying the International Mobile Subscriber
Identity (IMSI) of the UE).
The format of an ActivatePDPContextRequest is as shown in Table 6.3.

Table 6.3: ActivatePDPContextRequest message content
IEI Information Element Type/ Presence Format Length
Protocol discriminator Protocol discriminator M V 0,5
Transaction identifier Transaction identifier M V 0,5 - 1,5
Activate PDP Context Request Message type M V 1
NSAPI NSAPI M V 1
Requested LLC SAPI LLC Service Access Point ID M V 1
Requested QoS Quality of Service M LV 12
Requested PDP address Packet data protocol address M LV 3 - 19
28 Requested Access point name Access point name O TLV 3 - 102
27 Protocol configuration options Protocol configuration options O TLV 3 - 253

ETSI
14 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
The definition of ActivatePDPContextRequest is as follows:
ActivatePDPContextRequest ::= SEQUENCE {
nas-header NasHeader,
nas-message-type NasMessageType,
nsapi NSAPI,
request-llc-sapi RequestLLCSAPI,
requested-quality-of-service QualityOfService,
requested-pdp-address PDPAddress,
requested-apn APN OPTIONAL,
protocol-configuration-options
ProtocolConfigurationOptions OPTIONAL
}
When operating with (this version of) the BM domain, requested-apn information element shall be present, while the
protocol-configuration-options information element may be present (potential support for future features). The
structure of ActivatePDPContextRequest is as shown in Figure 6.3.
(MSB) Bit No (LSB)
8 7 6 5 4 3 2 1
transaction-identifier protocol-discriminator Octet 1
transaction-identifier-extension (conditional) Octet2
nas-message-type
nsapi
request-llc-sapi
requested-quality-of-service
requested-pdp-address
requested-apn
protocol-configuration-options (optional)

Figure 6.3: ActivatePDPContextRequest format
6.3.1.1 nsapi (Network Service Access Point Identifier)
The nsapi information element is an UE-allocated reference called the Network Service Access Point Identifier. Values
in the range 0.15 identify a PDP Context endpoint within the scope of a UE.
The nsapi parameter is of type NSAPI which is defined in clause 7.2.
6.3.1.2 requested-llcsapi
The requested-llcsapi is of type LLCSAPI as defined in clause 7.3. This information element is not used by the BM
domain of the Core Network (CN) but is left in the definition to be consistent with 3GPP. Default value '00000000'B
(requested-llcsapi not assigned).
ETSI
15 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
6.3.1.3 requested-pdp-address (PDPAddress)
The requested-pdp-address is used to request an IP address to utilized for this PDP context, and is of type PDPAddress
as defined in clause 7.5.
6.3.1.4 apn (Access Point Name)
Access Point Name value is used to reference an external network domain and is defined in ETSI TS 123 003 [3]. The
apn parameter is of type APN which is defined in clause 7.1.
6.3.1.5 requested-qos (QualityOfService)
The requested-qos parameter is of type QualityOfService as specified in clause 7.6, and is used to define the requested
quality of service characteristics of the PDP Context.
6.3.2 ActivatePDPContextAccept
6.3.2.0 General
The ActivatePDPContextAccept NAS message is used by the BMSN to accept an ActivatePDPContextRequest
from a UE. When the BMSN receives that the Radio Access Bearer has been established successfully then the BMSN
sends this message to the UE via the RAN.
The format of an ActivatePDPContextAccept is as shown in Table 6.4.
Table 6.4: ActivatePDPContextAccept message content
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator M V 0,5
Transaction identifier Transaction identifier M V 0,5 - 1,5
Activate PDP Context Accept Message type M V 1
Negotiated LLC SAPI LLC service access point identifier M V 1
Negotiated QoS Quality of Service M LV 12
Radio priority Radio priority M V 0,5
Spare half octet Spare half octet M V 0,5
2B PDP Address Packet Data Protocol Address O TLV 4 - 20
27 Protocol configuration options Protocol configuration options O TLV 3 - 253
34 Packet Flow Identifier Packet Flow Identifier O TLV 3

The definition of ActivatePDPContextAccept is as follows:
ActivatePDPContextAccept ::= SEQUENCE {
nas-header NasHeader,
nas-message-type NasMessageType,
negotiated-llc-sapi LLCSAPI,
negotiated-quality-of-service QualityOfService,
radio-priority RadioPriority,
pdp-address PDPAddress OPTIONAL,
protocol-configuration-options ProtocolConfigurationOptions
(OPTIONAL),
packet-flow-id PacketFlowId OPTIONAL
}
For operation with the BM domain, pdp-address shall always be present, protocol-configuration-options may be
present, packet-flow-id shall not be present. The structure is as shown in Figure 6.4.
ETSI
16 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
(MSB) Bit No (LSB)
8 7 6 5 4 3 2 1
transaction-identifier protocol-discriminator Octet 1
transaction-identifier-extension (conditional)
nas-message-type
negotiated-llc-sapi
negotiated-quality-of-service
spare radio-priority
pdp-address
protocol-configuration-options (optional)

Figure 6.4: ActivatePDPContextAccept format (as presented to BM domain)
6.3.2.1 negotiated-llc-sapi
The negotiated-llcsapi parameter is of type LLCSAPI as defined in clause 7.3. It is not currently used by the BM
domain of the CN but is left in the definition to be consistent with 3GPP. Default value '00000000'B (negotiated-llcsapi
not assigned).
6.3.3 ActivatePDPContextReject
6.3.3.0 General
The ActivatePDPContextReject NAS message is used by the BMSN to reject an ActivatePDPContextRequest
from a UE. If the UE is not provisioned in the Broadcast Multicast Service Centre (BMSC) database it will reject the
service.
The format of an ActivatePDPContextReject is as shown in Table 6.5.
Table 6.5: ActivatePDPContextReject message content
IEI Information Element Type/Reference Presence Format Length
Protocol discriminator Protocol discriminator M V 0,5
Transaction identifier Transaction identifier M V 0,5 - 1,5
Activate PDP Context Reject Message type M V 1
SM cause SM Cause M V 1
27 Protocol configuration options Protocol configuration options O TLV 3 - 253

The definition of ActivatePDPContextReject is as follows:
ActivatePDPContextReject ::= SEQUENCE {
nas-header NasHeader
nas-message-type NasMessageType,
sm-cause SMCause,
protocol-configuration-options
ProtocolConfigurationOptions OPTIONAL
}
ETSI
17 ETSI TS 102 744-3-7 V1.1.1 (2015-10)
For operation with this version of the BM domain, protocol-configuration-options shall not be present, and therefore the
format of the ActivatePDPContextReject shall be as shown in Figure 6.5.
(MSB) Bit No (LSB)
8 7 6 5 4 3 2 1
transaction-identifier protocol-discriminator Octet 1
transaction-identifier-extension (conditional)
nas-message-type
sm-cause
Figure 6.5: ActivatePDPContextReject format (from BM domain)
6.3.3.1 SMCause
The Information Element sm-cause is
...