Telecommunications

MOCN HO   (PA5)

Location Updating via Iu-i/f

Upon LU via Iu-i/f (RANAP Initial UE), MMM gets the selected PLMN id with GETUEDATA/ACK and stores it.

Later, after successful authentication and ciphering, MVLRP will receive RELEASEAUTHR (@LUAUTHREL). If ciphering is successful (AUTHRESULT) then after sending UPDATEMSLOC2/ACK it will send to new signal GETUEDATA to MMM.

MMM at reception of GETUEDATA it will reply back to MVLRP with GETUEDATAACK including the previously stored PLMN id.

MVLRP at reception of GETUEDATAACK it will use new combine signal UPDSPLMNID/ACK to MTV to store the PLMN in VLR.

Note: the impact in MMM after ACCONFDATLR sending the UPDSPLMNID/ACK, it will be removed.

MTV at reception of UPDSPLMNID it will store the PLMN id and additionally to already designed code, it will set a validity indicator. This indicator will be reset at LOADDEFAULTDATA.

[pic 1]

MO- SMS/LCS/SS, Paging Response

After successful authentication, MVLRP will receive AUTHENTICATE2R (@xxAUTHSTART). After sending INITCOMID, MVLRP will use new combine signal READSPLMN/ACK to MTV to fetch the PLMN id and the validity.

If the PLMN is valid, MVLRP it will send new signal STORESPLMNID to MMM.

MMM at reception of STORESPLMNID it will forward it to downlink.

MRRM/MUAMCO at reception of STORESPLMNID they will store the PLMN id and also set a validity indicator. No need to include a validity indicator in STORESPLMNID. MRRM/MUAMCO will initiate it locally at seizure).

[pic 2]

Signalling Handover while storing the PLMN-id from MMM

There might be the case where when sending STORESPLMNID to downlink, a signalling handover is taking place and therefore MMM has downlink the MHO, MUREL, MHOC or MUHOC. MUREL and MHO, if HO is ongoing, they will buffer the signal (i.e. keep an indication that is received and store the signal data in record vars) the request and sent it later when handover/relocation complete is received. Else, they will send it immediately. (MUREL will send it with HURRY). The handling will be similar to design base signal INITCOMID. Add a new sub-variable in structure of BUFSIGIND of MUREL.

MHOC and MUHOC upon reception of STORESPLMNID, they will just store the PLMN in their record.

Handovers General

In order for the PLMN-id to be used in target side, it will be transferred via the handover CB (see 2/IWD of MMS). A new tag=18 will be used. Below is an overview of the blocks that will read/write this IE in the HO CB:

According to above table, whenever a user block receives design base signal GETSERVDATA it will write in the HO CB the PLMN id if valid.

Whenever a user block receives design base signal TAKESERVDAT it will read from the HO CB the PLMN id if exists.