Here you are an interesting Integration Step Guide for better understanding how to implement to network an RNC (Radiomobile Access Network Equipment) qwith MML commands, for NSN.

1. Installation: Software
Extract the SW archive file using ZIXX
Create new SW package ZWQC:NAME=<package name>,
DIRE=Q4011400:FORM=FAILED
Change the SW package to NW
Copy customer specific feature file FIFILE to LFILES directory and
Copy licence files to LICENCE directory
ZWSC
Add the Change Delivery
Creating another SW package on the same directory with new SW package directory
ZWNA:STAT=NW:1
ZWQC:NAME=R400000N,DIRE=..,:FORM=FAILED,CW=NEW,;
Activate SW package that contains CD
Create CDTEMP directory on the new SW package directory
ZWSS:NAME=R400000N;
Activate the SW package by defining new default SW package, and it will automatically bring system restart
ZWSD:STAT=NW
Extracting CD archive file into CDTEMP ZIXX:,/,R400000N.ZIP::,/Q4011400/CDTEMP:TIME=2400,PATHS=N;
ZIWY:S
ZIWY:D
ZIBC
ZIWL::WS,NODEF:<package directory>:CDTEMP;
Change
Delivery
NewSW
package
Change the new SW package
status to BU
ZWSC:NAME=R400000N, STAT=BU;

2. Commissioning (1/4)
Service Terminal remote session
in the OMU ZDSS:OMU;
Monitoring the start-up unit
ZLP:1,RCJ;
Create new user profile (OPTIONAL) in
Z1I:ALL;
Check the connection createed between logical files
used for printing alarms and the VPP device
ZE
TELNETorHTTP
connectiontotheOMUIP
usingport11111
Activate the RCJUUS Service Terminal extension
Quit to Service Terminal remote session
ZIAH:<user ID>, <profile>;
ZIID::<logical file name>:LF=ALARMS:DEV=VPP-99
Change the connection createed between logical files
used for printing alarms and the VPP device
ZIIS::<logical file name>:LF=ALARMS:DEV=VPP-97
Check the VPP state
ZIHI:VTP=97
Activate the HME Service Terminal extension for HMS System ZLP:2,HME;
Display HMS system configuration Z2DP;
Check HMN SW version in single unit Z2CO:<cabinet>, <subrack>, <ppa> ;
Quit to Service Terminal remote session
Service Terminal remote session
in the OMU ZDSS:OMU;
ZE;
Modify time and date
Define NTP IP Server address
ZDCS: <date>, <time>: ST<summer time>;
ZDCM: <ip version>, <ip address>;
HMSSYSTEM

3. Commissioning (2/4)
Interrogate cabinet information
ZWFI:J;
Interrogate plug in unit address information
ZWFI:C;
ZWFI:P:[<plug-inunittype>],[<plug-inunitindex>]:
[<cabinetHMSnumber>],[<subrackHMSnumber>],
[<PPA>]:[<subracklocation>]:[<unittype>],[<unit
index>],[<unitgroupindex>]:[<masterunittype>],
[<masterunitgroupindex>];
Interrogate subrack information
ZWFI:S:<cabinetHMSnumber>,<subrackHMSnumber>,
<PPA>,[<porttype>],[<portindex>];
Interrogate port information in plug in unit
EQDATA
INTERROGATION
HWDATA
INUNIT
EEPROM
Interrogate plug-in unit data
Interrogate subrack data
ZWFL:P;
ZWFL:S;
SWDATA
Interrogate software package structure in SOMAFI that
poins to 8 packages in WDU
Check the erroueous version of the software package
ZWQO:CR;
ZWQB:NAME<sw build name>:FORM=FAILED;
Check the version of single plug.in unit ZWDI:UT=<functional unit type>;
Update the SW in plug-in unit If is different than WDU ZWDR:UT=<unit type>, UI=<unitindex>;
Reset the unit for activating the SW in the plug.in unit ZUSU:<unit type>,<unitindex>;

4. Commissioning (3/4)
Interrogate I/O device state (i.e. WDU) ZIHI
Change I/O device state ZIHE
Display the Diagnostic report
Start I/O device total test
ZUDH
ZUDD
Interrogate the current test ZUDQI/ODEVICES
CORRECTPOSITION
OFPLUG-INUNITAND
SWITCHOVEROK
Activate the HME Service Terminal extension for HMS System ZLP:3,POH;
Display all computing unit in messaging system Z3F:::1;
Check If the unit answer (so If the switchover works) Z3YY;
Quir to Service Terminal remote session
Service Terminal remote session
in the OMU ZDSS:OMU;
ZE;
Check which SET are active for collecting external syncronization ZDYP:;
Interrogate syncronization system ZDYI:;
SYNCRONIZATION

5. Commissioning (4/4)
Logical file definition for association with VDS
ZIFF:<unit>:<application>:SIZE=<diskfilesize>,
AMO=<diskfileamount>,COMP=<compressionmode>,
SKIP=<skippingmode>,OVERW=<overwritemode>;
Connect logical file to
the VDS
ZIIS:<systemname>,<destinationunit>:<logicalfile
name>,<logicalfiletype>:<currentobject
identification>:<newobjectidentification>;
VDSFORSTATISTICAL
REPORTTONETACT

6. SET, PET,
IMA, PROTGR
?
IMA Group PROT GROUP
PHYSICAL TRAIL TERMINATION POINT
ATM INTERFACE
ACCESS PROFILE
INTERFACE TYPE
?
NEMU GUI: COCO, FMC, WBTS, WCELL, HOP, …
MML: O&M LINK
VP TERMINATION POINT
VC TERMINATION POINT
SIGNALLING,
USER DATA
?
ZYBC
ZYDC
ZLAC
ZLAF
ZLCC
ZLCC
ZYWCZYBI
ZYA..
ZYWI
ZYDI
ZLAI
ZLAQ
Iub
Iu-CS, Iu-PS, Iur
ZLCI
ZLCI
SIGNALLING USER DATA
IP OVER ATM INTERFACE
IP ADDRESS FOR
IP OVER ATM INTERFACE
DEFAULT/STATIC ROUTES
ZQMF
ZQRN
ZQKC
ZQMI
ZQRI
ZQKB
SET, PET
Interface integration (1/2) (ATM over SDH)

7. MTP SERVICES
OWN SPC
SIGNALLING LINK
SIGNALLING LINK SET
SIGNALLING ROUTE SET
ACTIVATE SIGNALLING LINK
ACTIVATE SIGNALLING ROUTE SET
LOCAL & REMOTE SUBSYSTEMS
ACTIVATE LOCAL & REMOTE SCCP
ACTIVATE LOCAL & REMOTE SUBSYSTEMS
BROADCASTING
ATM ROUTE
ENDPOINT GROUP
ENDPOINT
UNBLOCK AAL2 PATH
ANALYSIS COMPONENTS
IP OVER ATM INTERFACE
IP ADDRESS FOR
IP OVER ATM INTERFACE
DEFAULT/STATIC ROUTES
INTERFACE
?
ZNPC
ZNRP
ZNCS
ZNSC/ZNSP
ZNRC
ZNVA
ZNVC
ZNFD
ZNGC
ZNHC
ZOBM; ZOBC
ZRRC
ZLIC
ZLJC
ZLSU
ZRDE
ZQMF
ZQRN
ZQKC
ZNPI
ZNRI
ZNCI
ZNSI
ZNRI
ZNLI
ZNVI
ZNFI; ZNFJ
ZNGI
ZNHI
ZOBI; ZOBL
ZRRI ZQMI
ZQRI
ZQKB
ZLII
ZLJI
ZRIL
Iu-PSIu-CS, Iur
ZNLA
ZNLC
ASSOCIATION SET
ASSOCIATION
SOURCE IP
ZOYC
ZOYA
ZOYN
ZOYI
SS7 vs. IP
*
* Create first IP interface, IP
address and routing
SS7 IP
ZOYL
DIGIT ANALYSISZRDC ZRII
SIGNALLING,
USER DATA
?
SIGNALLING
USER DATA
Interface integration (2/2) (ATM over SDH)