Name

AVP Code

Data Type

Vendor

Additional-MBMS-Trace-Info

910

OctetString

3GPP 

Provides detailed tracing information for Multimedia Broadcast/Multicast Service (MBMS) sessions. It is designed to assist in the monitoring and debugging of MBMS services by providing data relevant to the Broadcast-Multicast Service Center (BM-SC) operations.

This AVP contains the following elements, encoded as part of the Additional MBMS Trace Info Information Element (IE) as per [TS29.060]:

Trace Reference 2: Identifies the specific trace session for MBMS.

Trace Recording Session Reference: Provides a unique reference for recording trace activities.

Triggering Events in BM-SC: Specifies events that trigger the trace recording at the BM-SC level.

Trace Depth for BM-SC: Indicates the depth of the trace to control the level of detail recorded.

List of Interfaces in BM-SC: Specifies the interfaces in the BM-SC to be included in the trace activity.

Trace Activity Control for BM-SC: Provides additional controls for trace activities at the BM-SC.

Alternative-APN

905

UTF8String

3GPP 

Used to specify a new Access Point Name (APN) for the User Equipment (UE) to establish a Multimedia Broadcast/Multicast Service (MBMS) PDP context. This AVP is optional and is typically included in scenarios where the Broadcast-Multicast Service Center (BM-SC) requires the UE to use a different APN than the one indicated in the initial Join message.

CN-IP-Multicast-Distribution

921

Enumerated

3GPP 

Used to specify whether the IP multicast distribution mechanism should be employed for delivering MBMS (Multimedia Broadcast/Multicast Service) user plane data to the UTRAN (UMTS Terrestrial Radio Access Network). It provides an enumerated indication of the distribution method for MBMS data. Values:

NO-IP-MULTICAST (0): IP multicast distribution of MBMS user plane data shall not be used. Indicates the use of alternative mechanisms for MBMS data delivery to UTRAN.

IP-MULTICAST (1): MBMS user plane data to UTRAN should be delivered using the IP multicast mechanism. Optimized for scenarios where multicast distribution is supported by the network.

MBMS-2G-3G-Indicator

907

Enumerated

3GPP 

Specifies the type of coverage areas where the MBMS bearer service will be delivered. It identifies whether the MBMS (Multimedia Broadcast/Multicast Service) bearer service is intended for 2G-only, 3G-only, or both 2G and 3G coverage areas. Values:

2G (0): The MBMS bearer service is restricted to 2G-only coverage areas.

3G (1): The MBMS bearer service is restricted to 3G-only coverage areas.

2G-AND-3G (2): The MBMS bearer service is delivered in both 2G and 3G coverage areas.

MBMS-BMSC-SSM-IP-Address

918

IPv4 Address

3GPP 

Specifies the IPv4 address of the Broadcast Multicast Service Center (BM-SC) for Source-Specific Multicasting (SSM). It is used to identify the BM-SC in scenarios where IPv4 or dual-stack connectivity is utilized.

MBMS-BMSC-SSM-IPv6-Address

919

IPv6 Address

3GPP 

Defines the IPv6 address of the Broadcast Multicast Service Center (BM-SC) for Source-Specific Multicasting (SSM). This AVP is included in scenarios where the BM-SC operates in a dual-stack configuration and utilizes IPv6 for multicast data delivery.

MBMS-Counting-Information

914

Enumerated

3GPP 

Provides information on whether MBMS Counting Procedures are applicable to the MBMS service that is about to start. This AVP applies exclusively to UTRAN access types and helps determine if user counting is required as part of the MBMS Session Start Procedure signaled by the BM-SC. Values:

COUNTING-NOT-APPLICABLE (0): MBMS Counting Procedures are not applicable for the MBMS service. Example: When the service is broadcast-only or user count data is unnecessary.

COUNTING-APPLICABLE (1): MBMS Counting Procedures are applicable for the MBMS service. Example: When resource allocation depends on the number of participating users.

MBMS-Flow-Identifier

920

OctetString

3GPP 

Represents a location-dependent subflow of a broadcast MBMS bearer service. When combined with the TMGI (Temporary Mobile Group Identity), it uniquely identifies an MBMS Bearer Context.

MBMS-GGSN-Address

916

IPv4 Address

3GPP 

Used for the GGSN (Gateway GPRS Support Node) user plane in MBMS (Multimedia Broadcast Multicast Service) contexts. It specifies the IPv4 address of the GGSN that is responsible for delivering unicast user-plane traffic to a BM-SC (Broadcast Multicast Service Center) when requested.

MBMS-GGSN-IPv6-Address

917

IPv6 Address

3GPP 

Represents the IPv6 address of the GGSN (Gateway GPRS Support Node) used for the user plane in MBMS (Multimedia Broadcast Multicast Service) contexts. It is included by dual-stack GGSNs to provide their IPv6 unicast address to the BM-SC (Broadcast Multicast Service Center) when requested.

MBMS-HC-Indicator

922

Enumerated

3GPP 

Indicates whether header compression is applied by the BM-SC (Broadcast Multicast Service Center) during the transmission of MBMS (Multimedia Broadcast Multicast Service) user-plane data. This AVP is used to optimize the delivery of MBMS traffic by minimizing the size of packet headers, enhancing transmission efficiency in constrained network environments. Values:

0: HC-NOT-USED: Indicates that header compression is not applied to MBMS user-plane data.

1: HC-USED: Indicates that header compression is applied to MBMS user-plane data.

MBMS-Required-QoS

913

OctetString

3GPP 

Specifies the Quality of Service (QoS) parameters required for the MBMS (Multimedia Broadcast Multicast Service) bearer service. This AVP defines the relative importance and technical parameters necessary to allocate and maintain the required service quality for MBMS bearer sessions. Octet Structure:

Octet 1: Allocation/Retention Priority

Encodes the priority level of the MBMS bearer service, as specified in [TS23.107].

Priority levels are represented as binary values. Higher priority levels indicate greater importance for allocation and retention.

Octet 2-N: QoS Profile

Encodes the Quality of Service profile, starting from octet 3 of the Quality-of-Service information element, as defined in [TS24.008]. Contains detailed QoS parameters like delay, jitter, and packet loss.

MBMS-Service-Area

903

OctetString

3GPP 

Specifies the geographical area over which the Multimedia Broadcast Multicast Service (MBMS) bearer service is distributed. This AVP defines the MBMS Service Area (SA), which is composed of one or more MBMS Service Area Identities (MBMS SAIs). Each MBMS SAI identifies a group of cells within a Public Land Mobile Network (PLMN) that can receive the MBMS service. These groups are independent of Location Areas (LA), Routing Areas (RA), or Service Areas (SA), making them flexible for broadcast and multicast applications. This AVP is encoded as an OctetString and contains the following elements:

Number of MBMS SAIs (N):

• Encoded as a single octet.

• Valid range: 0x00 (0) to 0xFF (256).

List of MBMS SAIs:

• Each MBMS SAI is encoded as 2 octets (16 bits).

• Represents a decimal number between 0 and 65,535.

MBMS-Service-Type

906

Enumerated

3GPP 

Explicitly indicates the type of MBMS (Multimedia Broadcast Multicast Service) being initiated by the BM-SC (Broadcast Multicast Service Center). Values:

0: Multicast: Indicates that the Start Procedure is for a Multicast Service, delivering data to a group of users.

1: Broadcast: Indicates that the Start Procedure is for a Broadcast Service, delivering data to all users in a specific area.

MBMS-Session-Duration

904

OctetString

3GPP 

Represents the estimated duration of an MBMS session, including the data transmission phase of the MBMS service. The AVP is encoded as a three-octet field that specifies the session duration in terms of seconds and days. It supports both finite and indefinite session durations. The encoding format is as follows:

Bit 8 of octet 1 to bit 8 of octet 3 (17 bits) express seconds, for which the maximum allowed value is 86400 seconds. Bits 7 to 1 of octet 3 (7 bits) express days, for which the maximum allowed value is 18 days. 

The coding is: (the ‘s’ bits represent the seconds, the ‘d’ bits represent the days):

Bits         Octets

8           7           6           5           4           3           2           1   

s s s s s s s s 1

s s s s s s s s 2

s d d d d d d d 3

For the whole session duration the seconds and days are added together and the maximum session duration is 19 days.

The lowest value of this AVP (i.e. all 0’s), is reserved to indicate an indefinite value to denote sessions that are expected to be always-on.

MBMS-Session-Identity

908

OctetString

3GPP 

Represents a unique identifier for a specific MBMS session transmission. The value is allocated by the BM-SC (Broadcast-Multicast Service Center). This AVP, in conjunction with the TMGI (Temporary Mobile Group Identity), serves to uniquely identify the transmission of a specific MBMS session.

MBMS-Session-Repetition-Number

912

OctetString

3GPP 

Provides an identifier for the repetition sequence of MBMS session transmissions. This AVP works in conjunction with the MBMS-Session-Identity AVP to manage retransmissions and ensure proper sequencing of MBMS data delivery. Values:

0: Indicates the first transmission of the session.

1-255: Represents the retransmission sequence number of the session.

MBMS-StartStop-Indication

902

Enumerated

3GPP 

Defines the type of procedure being signaled in an MBMS session. This AVP provides a clear indication of whether a session is starting, stopping, updating, or maintaining synchronization (heartbeat). Values:

0: START: Indicates an MBMS session start.

1: STOP: Indicates an MBMS session stop.

2: UPDATE: Indicates an MBMS session update.

3: HEARTBEAT: Indicates an MBMS session heartbeat.

MBMS-Time-To-Data-Transfer

911

OctetString

3GPP 

Provides the expected time duration between the receipt of the MBMS Session Start command (RAR(Start)) and the actual commencement of MBMS data transmission. 

The value is encoded as per the Time to MBMS Data Transfer Value Part Coding specified in [TS48.018]. This coding specifies the time interval between session start and data transfer in a compact, standardized format.

MBMS-User-Data-Mode-Indication

915

Enumerated

3GPP 

Specifies the mode of operation (Unicast or Multicast) for MBMS user data transmission. Its meaning is contextual, depending on whether the Broadcast-Multicast Service Center (BM-SC) or the Gateway GPRS Support Node (GGSN) sends the message. The absence of this AVP implies a Unicast mode of operation. Values:

0: Unicast:

• BM-SC: Supports only Unicast mode. Data packets will be encapsulated in a unicast header over UDP.

• GGSN: Requests BM-SC to send data using Unicast mode.

1: Multicast and Unicast:

• BM-SC: Supports both Multicast and Unicast modes.

• GGSN: Requests BM-SC to send data using Multicast mode.

RAI (Routing Area Identity)

909

UTF8String

3GPP 

The RAI (Routing Area Identity) AVP represents the Routing Area Identity of the SGSN where the User Equipment (UE) is registered. It is encoded as a UTF-8 string that captures the unique identifiers for routing purposes, such as the Mobile Country Code (MCC), Mobile Network Code (MNC), Location Area Code (LAC), and Routing Area Code (RAC). This AVP value is encoded as a UTF-8 string, consisting of:

MCC: Encoded as three UTF-8 characters, each representing a decimal digit. Total length: 3 octets.

MNC: Encoded as two or three UTF-8 characters, depending on the MNC length (2 or 3 digits). Total length: 2 or 3 octets.

LAC (Location Area Code): Encoded as four UTF-8 characters, representing the hexadecimal digits of the 16-bit binary LAC value. Total length: 4 octets.

RAC (Routing Area Code): Encoded as two UTF-8 characters, representing the hexadecimal digits of the 8-bit binary RAC value. Total length: 2 octets.

Required-MBMS-Bearer-Capabilities

901

UTF8String

3GPP 

Specifies the minimum bearer capabilities required by the User Equipment (UE) to support the MBMS (Multimedia Broadcast/Multicast Service). These capabilities are encoded as a UTF-8 string representing MBMS bearer capability information, as defined in [TS24.008].

Temporary Mobile Group Identity (TMGI)

900

OctetString

3GPP 

Used to uniquely identify a Multimedia Broadcast Multicast Service (MBMS) bearer service within a network. It is allocated by the Broadcast-Multicast Service Center (BM-SC) and serves as an identifier for the broadcast/multicast session. The TMGI includes information such as the Mobile Country Code (MCC) and Mobile Network Code (MNC), ensuring global uniqueness. Structure and Encoding:

MCC (Mobile Country Code): 3 digits (decimal), UTF-8 encoded.

MNC (Mobile Network Code): 2 or 3 digits (decimal), UTF-8 encoded.

MBMS Service ID: 24-bit identifier allocated by the BM-SC.

Example:

A TMGI with:

MCC = 310

MNC = 260

Service ID = 12345

Encoded String: 31026012345