In eMBMS Node test case, the MB2 is the reference point between the GCS AS and the BM-SC. Available on eMBMS Node when eMBMS-GW and BMSC is enabled and on IP Application node when SIP VoIP , GM only and Capacity Test Activity are enabled.
MC-PTT is linked to eMBMS for broadcasting information. The physical link is MB2-U and MB2-C interfaces. These interfaces originate from the MCPTT AS and GSC AS and connect into the BM-SC.
The MB2 interface provides the ability for the application to use the functionality of the MBMS system to deliver data to group members over MBMS. The procedures supported include:
Deallocation of a set of TMGI (s) by the BM-SC at the request of the GCS AS (see clause 5.1.2.2.3)
Activating an MBMS bearer (see clause 5.1.2.3.2):
This may include request to BM-SC applying FEC or RoHC (Robust Header Compression) or both to a set of media.
Deactivating an active MBMS bearer (5.1.2.3.3)
Modifying characteristics of an active MBMS bearer (see clause 5.1.2.4)
Reporting of MBMS delivery status from the BM-SC to the GCS AS (see clause 5.1.2.5)
Structure of TMGI - per TS 23.003. MB2-C Diameter Control Plane per IETF RFC 3588.
The MB2 interface between the GCS AS and the BM-SC is established before any MB2 messages are sent between these two entities, and carries all MB2 messages between the two entities for all MBMS bearers used by the GCS AS. The TMGI/Flow ID (see TS 23.246) is the unique identifier used by the GCS AS and BM-SC to refer to the MBMS bearer.
|
Quality of Service
|
Quality of Service |
|
TMGIs and Service Areas |
|
|
Enter the BMSC Port. Available on eMBMS Node test case. Range : 0 to 4294967295 Default : 9470 Tcl Parameter: Mb2BmscPort |
|
|
Select to enter the Temporary Mobile Group Identity (TMGI) Expiration Timer in seconds. Per TS 29.468. Available on eMBMS Node test case. Range : 0 to 4294967295 Default : 10 Tcl Parameter: Mb2TmgiTimer |
|
|
Select the Feature-List-Id. Enter the Value or Select the options listed below and the value will automatically be calculated for you. Range : 0 to 32 Options : 0 - Heartbeat , 1 MBMS Cell List , V2X Localized User Plane , 3 - FEC, 4 - ROHC Tcl Parameter: Mb2FeatListId |
| Number of TMGIs per MCPTT Group |
Select to support up to 5 Temporary Mobile Group Identity (TMGIs) per group. The table below becomes available to provide Service Area assignments for each TMGI Group. Range : 1 to 5 Default : 1 Tcl Parameter: Mb2TmgiGroups |
||||
| Starting Serving Area |
Service Area identifies the location of the serving network to which the UE (mobile subscriber) is attached. Starting Service Area and Number of Service Areas are combined used to configure service area list for Temporary Mobile Group Identity (TMGI) Goups which is included in MBMS Session Start Request message. It will auto increase if multiple service areas or multiple MBMS bearers need to configure. Available when Manually Assigned Service Areas to TMGIs is not selected. Range: 1 — 65535 (0 is skipped) Default: 1 Tcl Parameter: Mb2StartingServiceArea |
||||
| Number of Service Areas |
Identifies the number of service areas to be configured for a MBMS bearer in Session Start Request message. Available when Manually Assigned Service Areas to TMGIs is not selected. Range: 1 — 256 Default: 1 Tcl Parameter: Mb2NumServiceArea |
||||
| Manually Assign Service Areas to TMGI Groups |
Select to enable the table below to manually enter up to 100 Temporary Mobile Group Identity (TMGI) Groups. Starting Service Area, Number of Service Areas are both Disabled. Tcl Parameter: Mb2TmgiGroupsEn |
||||
| Auto-Increment the Manually Assigned Service Areas |
Available when Manually Assign Service Areas to TMGIs is enabled. Select to Auto-Increment the Manually Assigned Service Areas. Tcl Parameter: Mb2TmgiAutoIncEn |
||||
| Number of TMGI Groups and Service Area ID (s) |
Enabled when Manually Assign Service Areas to TMGI Groups is selected. Remaining Bearers at the end of the pane will display the remaining bearers left to be configured. The TMGI # Groups that are entered in Number of TMGIs per MCPTT Group. They are not available when “eMBMS-GW” emulator mode is selected.
For example: Starting Service Area Id = 100, Number of Service Area per TMGI = 2, and Number of TMGIs per MCPTT Group = 5, then: TMGI Index = 1 , Service Area IDs = 100, 101 TMGI Index = 2 , Service Area IDs = 102, 103 TMGI Index = 3 , Service Area IDs = 104, 105 TMGI Index = 4 , Service Area IDs = 106, 107 TMGI Index = 5 , Service Area IDs = 108, 109
Additional examples in ExamplesMb2 Document. |
QoS measurements applies to eMBMS session loads and user service bandwidths to control network quality-of-service for sessions of multicast and broadcast MBMS bearer services.
QoS is not available on IP Application Node.
|
The Class ID in the Bearer QOS applies to the Uplink (UL) and Downlink (DL) IP flows. LTE test cases provide you with the ability to configure various QCI. You can choose to use the same QoS Class ID for all IP contexts or you can define different Class IDs for each context. Range: 0 — 255
Tcl Parameter: Mb2ClassId
|
||||
|
Use the ARP (Priority of Allocation and Retention) to determine the relative priority level during admission and congestion processes. The primary purpose of ARP is to decide whether a bearer establishment/modification request is accepted or needs to be rejected in case of resource limitations (typically available radio capacity in case of GBR bearers). In addition, the ARP is also used (e.g. by the eNodeB) to decide which bearer(s) to drop during exceptional resource limitations (e.g. at handover). Once successfully established, a bearer's ARP does not have any impact on the bearer level packet forwarding treatment (e.g. scheduling and rate control).
Range: 1 - 15 Default: 1 Tcl Parameter: Mb2ArpValue
|
||||
|
The Set Bandwidth/Bit Rate checkbox is available only when Class Identifier value is 0 or between 10 and 255. Range : 0 to 255 Select Set Bit Rates to enter the Maximum Requested Bandwidth and Guaranteed Bit Rates values for DL traffic. Tcl Parameter: Mb2QosBrEn |
||||
|
Selecting this checkbox indicates that the bearer may preempt other bearers with a lower ARP value when resource limitations are reached. Tcl Parameter: Mb2QosArpPreemptCapEn |
||||
|
Selecting indicates that a bearer is vulnerable to being dropped when resource limitations have been reached and there is a bearer with a higher ARP value in service. Tcl Parameter: Mb2QosArpPreemptVulnEn |
||||
|
Maximum Requested Bandwidth DL (kilobits/sec) and Guaranteed Bit Rate DL (kilobits/sec) |
Define the IP flow Maximum Requested Bandwidth DL (kilobits/sec) and Guaranteed Bit Rate DL (kilobits/sec) for DL traffic. Range: 0 - 4294967295 Default: 1
Tcl Parameters:
|