This article describe the procedure for the verification of the multicast trunking feature. Please see more details below.
The eSE620X vESS is an important part of Huawei's industry wireless communication system. It can be used as BMSC and MCE and it cooperates with the MCPTT Server or video platform to provide multicast scheduling services to meet the needs of the industry market.
The Multicast Trunking feature enables the vESS to provide the evolved multimedia broadcast multicast service (eMBMS) defined by 3GPP for evolved packet systems (EPSs). In eMBMS, both SGi-mb and M1 interfaces support multicast transmission for point-to-multipoint one-way multimedia services.
Multimedia broadcast service data is sent to UEs in cells via common channels over air interfaces, saving air-interface resources. On the network side, IP multicast is used to transmit multimedia broadcast services to save transmission resources.
This guide will help you verify whether the Multicast Trunking feature is enabled correctly.
1. Verification of data configurations for interworking with the MBMS-GW
1.1. Check the network connection between the local and peer devices.
Log in to ESS and run the PING command on CGP:
%%PING: IPTYPE=IPV4, LOCALIP4="192.168.53.37", PEERIP4="192.168.55.64", DATATYPE=DYNAMICLEN;%%
Local IP: SGMB interface IP
Peer IP:MBMS-****mbif interface IP
1.2. Check whether the Diameter Link Status is UP in BMSC for MBMS-GW:
%%DSP DIAMLNK:;%%
1.3. Check whether MBMS-GW is configured as a peer device:
%%LST DIAMPEER: LTP=LOCAL;%%
1.4. Check whether the Diameter Peer status is UP for MBMS-GW:
%%DSP DIAMPEER:;%%
2. Verification of data configurations for interworking with the eAPP
2.1. Check the network connection between the local and peer devices.
Log in to ESSand run the PING command on CGP:
%%PING: IPTYPE=IPV4, LOCALIP4="192.168.53.31", PEERIP4="192.168.50.21", DATATYPE=DYNAMICLEN;%%
Local IP: MB2-C interface IP
Peer IP: eMDC IP
2.2. Check whether Diameter Link Status is UP in BMSC for eAPP.
(Application Server):
%%DSP DIAMLNK:;%%
2.3. Check whether eAPP is configured as a peer device:
%%LST DIAMPEER: LTP=LOCAL;%%
2.4. Check whether the Diameter Peer status is UP for eAPP:
%%DSP DIAMPEER:;%%
3. Verification of data configurations for interworking with the MME
3.1.Check network connection between local and peer devices.
Log in to ESSand run the PING command on CGP:
%%PING: IPTYPE=IPV4, LOCALIP4="192.168.53.41", PEERIP4="192.168.55.55", DATATYPE=DYNAMICLEN;%%
Local IP: M3 Interface IP of ESS
Peer IP: M3 IP of vUSN
3.2. Check whether the M3APLINK state is NORMAL in MCE:
%%DSP M3APLINK:;%%
4. Verification of the service
- Check whether the TMGI information is activated or not:
%%DSP TMGI: SELTYPE=STATUS, STATUS=ACTIVATED;%%
- Create the M2 interface trace right after resetting the session on MCE:
%%RST MCEMBMSSESSION:;%%
NOTE:
The request and responses will appear after the session has been reset, otherwise the trace will be empty.
- Open the WebLMT page of eNodeB, go to Monitor, open Cell Performance Monitoring in the left pane, select monitor item MA Scheduling Statistics, chooseSpecial TMGI and submit.
- When you press the PTT button on the terminal, the Lost Sync PDU Count (1-7) column should be empty during PTT. Also, you must see the MBSFN Area Scheduled Bytes (1-2) as more than 0.
