Huawei Global MOCN Case Sharing

Summary Abnormal Terminal Configuration issue Other Vendor IOT Solution Faulty
24 7 15 1 1
Remark: Most of issues are due to abnormal and wrong configuration
Classification Count - Classification
Abnormal Terminal 7
Configuration issue 15
Other Vendor IOT 1
Solution Faulty 1
(empty)
Total Result 24
 Related
No. Project Scenario Source Classification
NE

1 Mexico ATT 3G MOCN KPI Change Configuration issue RNC

Azerbaijan
2 2G/3G MOCN KPI Change Other Vendor IOT MSC
Azecell

Thailand
3 3G MOCN KPI Change Abnormal Terminal RNC
TMV

Swiss
4 3G MOCN KPI Change Configuration issue RNC
Sunrise

5 3G MOCN KPI Change Abnormal Terminal UE

6 3G MOCN KPI Change Configuration issue MSC

Germany
7 LTE MOCN Onsite testing Abnormal Terminal UE
TO2

Germany
8 LTE MOCN Onsite testing Abnormal Terminal UE
TO2

9 Mexico ATT 3G MOCN Onsite testing Abnormal Terminal UE

10 3G MOCN Onsite testing Configuration issue RNC

 RNC、M
11 HYD TATA 3G MOCN Onsite testing Configuration issue
SC

12 3G MOCN Onsite testing Abnormal Terminal RNC

13 3G MOCN Onsite testing Configuration issue RNC

14 HongKong 3G MOCN Onsite testing Configuration issue RNC

Contry B
MME、e
15 operators:V LTE MOCN Onsite testing Configuration issue
NodeB
、T、O

16 HongKong 3G MOCN onsite testing Configuration issue IP BB

RNC、S
17 HongKong 3G MOCN Onsite testing Configuration issue
GSN

18 HongKong 3G MOCN Onsite testing Configuration issue SGSN

Azerbaijan
19 3G MOCN Onsite testing Configuration issue RNC
Azecell

20 3G MOCN Onsite testing Configuration issue SGSN

 Thailand
21 3G MOCN User complain Solution Faulty RNC
TMV

Thailand
22 3G MOCN Onsite testing Configuration issue RNC
TMV

23 3G MOCN Onsite testing Abnormal Terminal RNC

24 Finland SYN 2G/3G/4G MOCN KPI Change Configuration issue MSC

Description

After MOCN feature enabled, PS RAB SETUP

SUCCESS RATIO KPI is degraded.After GTAC review,
a lot RAB assignment failure due to iu-transport-
connection-failed-to-establish

A3129H:CELL.ASS.FAIL.MSC.CLR.CMD was
increased after MOCN，CSSR is degraded from
99.85% to 99.25%。

RAU KPI is degraded after MOCN at A. From the

statistic , the failure is from the operator B

RRC successful rate is degraded to "0" after

RL_OpIndex_included enabled. After checking, it is
found that MOCN private CE license is enabled as
well, which will be conflicted with this parameter

Paging successful rate is degraded after MOCN

enabled

After MOCN implenment, it is found that 3G handover

to 2G prepration successful rate is low and the fail
cause counter is TgtFail

HTC ONE handset camp on 2G/3G network and move

to 4G coverage area, UE don't select own operator's
4G cell，UE is out of service in 40 seconds during
reselect network.
Sumsung S4 handset camp on 2G/3G network and
move to 4G coverage area, UE is out of service in 20
seconds during reselect network.
Huawei Mate7 and Sumsung S4 handset always
display operator‘s logo with core configuration even
network stop send MM message to UE
During MOCN feature test,secondary operator service
is not working.
During MOCN feature test, the subscriber of
secondary operator can't register successfully.
When Non-Support UE register in MOCN cell, PLMN is
COMMON PLMN, if COMMON PLMN is inconsistent
with slave PLMN, UE will display COMMON PLMN
LOGO, display is not correct.

PLMN ID in the source RNC ID and target RNC ID of

MOCN supporting UE of slave operator during
migration is second PLMN.

During MOCN test, modify BTS type as MOCN type

can't succeed.
after implementation operator O report user cannot
accesss MOCN LTE network. From KPI, find the
ERAB request from operator is 0, and onsite testing
find UE cannot access LTE network.

after RNC KKOC04 send MOCN active message,

IUPS signaling is normal, but PS service/browsing not
working.

eSRVCC handover in MOCN, EMSC open IU-

FLEX,handover failure issue

after RNC MOCN enabled, one of the operator SIM

user PS service not working

after MOCN enablement, part UE cannot do PS

service

after MOCN enablement, 3G handover 2G failed

SUPPORT UE reselect from MOCN 2G to MOCN 3G
fail, then out of service for a long time

Non-SUPPORT UE reselect from 2G to 3G need

seconds

In the MOCN network, even close the" Intra RAT Inter

PLMN Ho Allowed
switch"（INTERPLMNHOALLOWEDINTRARAT=NO）
, different operator users can handover mutually during
the RRC phase. After RRC phase handover
successful, it will cause operator A users can handover
to operator B private cell
After 2G MOCN implenment in golden cluster, it is
found that 3G handover to 2G successful ratio is
decrease from 90% to 30%
Conclusion

There are 5 IP address from RAB assignment request

signaling, but RNC do not have these 5 IPs.Affter RNC
configure these 5 IPs and KPI is recovered

call release suspension function is not abled at NSN Core

Some UE do not have PLMN and NRI information at its RRC

connection requirement, which will cause the problem, but
no impact on the user perception

When RL_OpIndex_included and Private CE license

enabled together, NodeB will decode the OpIndex to verify
with M2000 license, if the M2000 nodeB license do not have
Opindex, then this issue will happen

After MOCN enabled, some of LAC paging successful rate is

degraded a lot. After analysis, it is found that it the
broadcase Common PLMN is different from UE HPLMN, this
UE will do successful location update process, but can not
do paging

the core configuration issue, including target BSC and LAC

is not configurated

Different UE have different activity when reject by core with

#15, UE is designed not comply with 3GPP protocol

Different UE have different activity when reject by core with

#15,

UE seting network name witch download from network as

highest priority.UE is designed not comply with 3GPP
protocol
When configure license resource for operator, assigned all
throughput resource to master operator, didn’t assign
throughput resource to secondary operator.
The register failure reason is due to MSC reject, the reason
of MSC rejection is no LAC information.

UE LOGO display is based on selected PLMN.non-

supporting UE doesn't support reading multi PLMN list in
system information message,

During migration, in the request message, we sent PLMN

used by UE instead of public PLMN, this is inconsistent wth
UE's expectation, this caused UE to do one more time RA,
increased the load of SGSN.
During MOCN test in filed, can't modify BTS type to MOCN
type
TAC configuraion is wrong in core network cause UE cannot
access;
EP link maping configuraion is wrong in site side of operator
B, cause user cannot create ERAB bear.
GTPU package use UDN protocal in IU interface, GTP
control package source port is 2152, GTPU data package
source port is 65535. but firewall have block the port of 2152
and 65535, cause PS package been discard, UE cannot
browsing.
there is no response after RNC recive relocation req
message. After RNC recive relocation req message will
check the GLOBAL CNID, and compare with RNC
configuraion CNID, if not same then message will be
discard. This issue is because of CN and RNC CNID
configuration not same .

core network 22 have wrong configuraiton to RNC, from core

netowrk 22 cannot route to RNC, so after RNC send attach
request to core, core 22 no response, but if RNC send
attach request to 3871, then attach normal. After modify
SGSN route transmission, core 22 working normal.

Non Supporting UE carry bakcell NRI value, the request will

first go to backcell CN, CN reject with # 13 Roaming not
allowed in this LA. In normal procedure, Bakcell CN should
send re-route indicator with reject info, then UE will try other
CN, but in ourcase CN not carry reroute indicator, find the
issue is because of bakcell CN not enable MOCN switch.
after UE handover from UMTS to GSM, RAU been reject by
SGSN，missing configuration of DNSH record on SGSN
Nokia UE reselect from GSM to 3G network, in original
directly message, the PLMN will register as RPLMN,
because only operator 99 have GSM network , so in directly
message PLMN must be 99, even the UE HPLMN is 00
operator . 00 operator user from GSM back to 3G MOCN
cell, because RPLMN is 99, so in directly message, the
PLMN must be 99,RNC will send UE's LU request message
to 99 MSC and SGSN,but it will be rejected by 99 CN with
reject cause value "location-area-not-allowed”. After that, UE
will not try to register again, it will cause long time out of
service.

The NRI ID is conflict arrange for two operator’s MSC, LAU

request is reject by another MSC

It confirm that UE terminal behavior cause this issue: D51 is

before RRC SETUP CMP,it send the original directly
message, so it clear the PLMN index. but U8800 is after
RRC SETUP CMP, it send the original directly message, so
U8800 will keep the previous PLMN index, so after RRC
SETUP CMP,the measure control message didn't include
other operator cell information.
Missing config on CS core, UE can't recive EPLMN in
2G，that UE can't do 3G to 2G IRAT reselect to 2G object
cell when recive CELL CHANGE ORDER FROM UTRAN
Solution

Modify Core and RNC configuration

Modify configuration of BSC，No impact on network

and user
open【ASSFAILSTATISTICOPT】

No impact on network and user

Modify RNC configuration，Close private CE switch

Due to abnormal of terminal activity，can't solve from

network side

Modify core configuration

Due to abnormal of terminal activity，can't solve from

network side

Due to different Terminal activity ，can't solve from

network side

Due to abnormal of terminal activity，can't solve from

network side

Use MML command "SET LICENSE" to assign throuput

resource for both operator.
Add related LAC information on MSC, then subsciber
can register successfully.

Can modify logo through NITZ function of CN, but few of

handset don't support this feature

The primary operator's PLMN is 255, Shoud treat PLMN

ID 255 as common PLMN intead of treat it as no
common PLMN.

Modify configuration，Set "IPTRANSAPARTIND" as

"SUPPORT"

Modify MME and eNodeB configuration

1) operator O MME modify TAC configuraion;
2) modify site EP configuration;

Modify firewall open 2152 and 65535 ports

Modify configuration, keep RNC and CN negotiation

data same.

Modify CN configuration issue

Modify configuration of main operator CN, enable

MOCN feature

CN add DNS info for 2G, then PS U2G handover

successful
1、If GSM support 00 and 99 roaming, 3G network
recommend use the same strategy, so after 3G modify
the strategy, the issue was solved.
2、In this scenario, RNC add new switch
MOCN_SUPP_UE_ACT_AS_NOSUPP_SWITCH(The
RNC regards MOCN supporting UEs as MOCN non-
supporting UEs) to solved this issue.when MOCN is
applied, Whether the RNC regards MOCN supporting
UEs as MOCN non-supporting UEs:
3: This switch is turned on. The RNC regards MOCN
supporting UEs as MOCN non-supporting UEs. Then,
such UEs will be moved to another operator's network
through redirection;0: This switch is turned off. The RNC
does not regard MOCN supporting UEs as MOCN non-
supporting UEs.

Modify configuration of RNC and Core, avoid CN ID

conflict

Due to abnormal of terminal activity，can't solve from

network side

Add 3G EPLMN configuration on CS Core