Hi everyone,

In this article I tried to give some  information about solving undefine problem
I apologize for my bad english
If you can not understand any part of this article or If you want to add something please send me a message

Solving UNDEFINE  problem in APG

prcstate -l

undefined (Error = 2)

NET START CLUSSVC If a problem occur that fault code 1068  When starting clussvc

NET START INETD Telnet service is started (If already started  continue with next step)

sc query netlogon Shows netlogon status (If status already start Stop the service )

sc stop netlogon Stopping netlogon

sc continue netlogon Starting net logon

NET START CLUSSVC Starting clussvc

prcstate -l If status change but still not fully up , start the acs_prc_clustercontrol

net start acs_prc_clustercontrol Starting acs_prc_clustercontrol

In this article I tried to give some  information about the pricing process.
I apologize for my bad english
If you can not understand any part of this article or If you want to add something please send me a message

Basic Commands
Command :
SAAEP:SAE=500,BLOCK=CHOF;

If calling time is long , system saves the charging to REM at regular intervals.End of the call ,Charging is written to harddisk.

NI ( Number of Individuals ) = Capasity of System
NIU ( Number of Individuals Used) = Using of capasity at the moment
NIE ( Number of Individuals Expansion Size )= The file size by which the Number of Individuals for the Size
Alteration Event will be increased by the function at a logical file size increase.

Must be NI > NIU , If not , Charging information will be lost . If NIU=0 that means system has a problem

Metrica subfile Control (File process Utility Function, IO Node File Subfile Print)

INFSP:FILE=NPRSTS1,DEST=NPR1; The files that have traffic reports.

Charging Subfile Control at TTFILE00

INFSP:FILE=TTFILE00,DEST=CHARGING00;

Charging Subfile Control at TTFILE01

INFSP:FILE=TTFILE01,DEST=BIP; Process of Charging files, we can see sent or failed

INFSP:FILE=TTFILE01-xxxx,DEST=BIP; The command shows that xxxx file which is sent lastly
IOIFP:FILE=TTFILE01; The command shows that which file is processed lastly

INFSP :FILE=TTFILE01-xxxx,DEST=BIP,ORDER=ALL ; The command shows that xxxx and after files which is sent lastly

Charging Methods
A- ) PULSE METERING(PM)

B – ) Toll Ticketing(TT)

A- ) PULSE METERING(PM)
system produces pulses in calling and stores in a count according to each subscriber’s price plan
a count’s value is stored at telephone exchange that name CHSUB(Changeable Subscriber Data Handling) block.

1.TARIFF DATA: Shows the interval between pulses.
2.SWİTCHING CLASS: Shows pricing that weekday and holidays
3.TARIFF CLASS: Shows you a discount at what time during the day.
4.CHARGING CASE: Shows charging in which exchange
5.TRAFIC ACTIVITY ANALYSIS: Indicates the charging according to speech, data or additional services

System checks these steps from end to start

1.TARIFF DATA:

a.NSP(Number of start pulse) : B subscriber when rise up the phone , at the moment that indicates how many credit will decrease
b.NPP(Number of periodic pulse): How many credit will decrease end of the TDS (Time duration in seconds) while calling still ongoing
c.IDS : At the moment of B subscriber rise up the phone , how long can be talk until another pulse
d.TDS(Time duration in seconds): While subscriber talking , how long time will be pass between two pulse

CHTSP:T=ALL;
CHTZI;
CHTCI;
CHTSE :T=1 ;
CHTSI:T=3,NSP=3,TDS=60,IDS=30,NPP=1;  When calling set up 3 pulse will be sent after that 1 pulse will be sent. (30 seconds between 2 pulse)After that 1 pulse will be sent every 60 seconds.
CHTAR ;                         If protection time(24 hours) still ongoing we must use this command
CHRAR ;                         For set old value

2.SWİTCHING CLASS
most operator using time discounts like between 00 am to 5 am , aim is decrease using at rush times and spread time period.Usally defines day categories like DCAT0 for weekday DCAT1 for Saturday DCAT2 for sunday and holidays

CHTZI:SWC=1;
CHSPI:SWC=1
CHSSP:SWC=ALL;
CHSSI:DCAT=0,TIME=0600&1200&1700&2100;
CHSSI:DCAT=1&2,TIME=0800&1700;
CHSPE;
CHSAR;                If protection time(24 hours) still ongoing we must use this command
CAHSAI;

3.TARIFF CLASS
511 class types can be defined for tariff. Below commands are  using for  Which tariff class can be selected in Charging case

CHCZI;
CHCPI:TC=2,SWC=1;
CHCSP:TC=2,NOP;
CHCSE:TC=2;
CHCSI:DCAT=0,T=2&3&4&5;
CHCSI:DCAT=1&2,T=8&9;
CHCPE;
CHCAI:TC=2;
CHCAR; If protection time(24 hours) still ongoing we must use this command

4.CHARGING CASE
CHAZI;
CHACI;
CHASP:CC=ALL;
CHAPI;
CHAPE:
CHASI:CC=4,TC=4,CD=3,AP,TT;
CHASE;
CHAAI,CC=4;
CHAAR; If protection time(24 hours) still ongoing we must use this command

CC=Charging case
TC=Tariff class
CD=  Shows which exchange will be record CDR records . This value can be defined from 0 to 11 For example
0 —>  Top office ,  decides that which telephone exchange will be charged the charging or itself can be charged the charging. Charging information is requested from top office. tariff indicator does not send or wait

1 —> Top office ,  decides that which telephone exchange will be charged the charging . And itself is charged the charging.tariff indicator is waiting from top office

2,3—> Top office ,  decides that which telephone exchange will be charged the charging or itself can be charged the charging. Charging information is requested from top office.

4—> lower Office , decides that which telephone exchange will be charged the charging or itself can be charged the charging. Charging information is requested from top office.

5—> decides that which telephone exchange will be charged the charging Lower office is charging point. Tariff class convert to tariff and send to lower office  like tariff indicator

CP decides subscriber who  will pay the charging

AP —– A party,

BP —– B party,

NP—– No party

5.TRAFIC ACTIVITY ANALYSIS
NCC:  NCC(New charging case)  means ,common charging case is given to specific series of number (doesnt matter what is the call type)

TSC: (Telecomunication Service Code) it determines the calling that datatransmission or speech

CI:(Call Indicator):it determines the calling that usual call , call from MSC or SMS

SSI:(Supplementary Service Indicator): decides service activation or deactivation in additional services that  is done subscriber or exchange

For Example :

CHIZI:CC=17;
CHIPI:CC=17
CHISI:BC=TSC-3&SSI-1&SSP-4,NCC=16;
CHISI:BC=SSI-5&SSP=7&NCC=9;
CHISI:BC=CI-2&&-5,NCC=3;
CHIPE;
CHIAI:CC=17;

Calendar Function :
CACLP; Shows year month day hour second milisecond and time zone

This process controlled by APZ operation system. It should be control at regular intervals. If need to change CACLC command should use

CACLC:TDSF=5;      TDSF= Time will be 5 second forward                         TDSB=Time will be 5 second before
CACAP; Shows Day Categories

CACAS:DATE=000519,DCAT=2; Shows Holidays (If swithing class was defined as DCAT=2 )
CACAR;

B -Toll Ticketing(TT):
In this method Exchange records A and B numbers , Start and end  time of call  , destination information when subscribes set up a call . End of the call these datas are recorded by taype or  they are sent to different computer through datalink .Usally these datas are sent to Billing GW . In there   unnecessary datas are discard and sent to IT departmant

HLR : (Home Location Register) :A central database that contains details of each mobile phone subscriber that is authorized to use the GSM core network.

VLR: (Visitor Location Register) : Contains selected administrative information from the HLR, necessary for call control and provision of the subscribed services, for each mobile currently located in the geographical area controlled by the VLR. In VLR , we can learn from subscriber’s Location Area Idendity (LAI) that busy , free or power off and IMEI number.HLR and VLR datas record in CP’s data store (DS)

GMSC (GATEWAY MSC) : basically a switch which is able to interrogate the subscriber’s HLR to obtain routing information, and thus contains a table linking MSISDNs to their corresponding HLR

MSISDN:(Mobile Station Integrated Services Digital Network Number) : a number used to identify a mobile phone number internationally.

In GSM and its variant DCS 1800, MSISDN is built up as
MSISDN = CC + NDC + SN
CC = Country Code
NDC = National Destination Code, identifies one or part of a PLMN
SN = Subscriber Number
In the GSM variant PCS 1900, MSISDN is built up as
MSISDN = CC + NPA + SN
CC = Country Code
NPA = Number Planning Area
SN = Subscriber Number

IMSI:(International Mobile Subscriber Identity) : A number that defined 15 digits in SIM. It contains GSM national code for company operators(for example turkey : 286) + Company operators( Turkcell : 01, Vodafone 02 …) + network code for operators (1 or 2 digits) + Mobile telephone identity number (10 or 11 digits)

MSRN (MOBILE SUBSCRIBER ROAMING NUMBER ) : Each MSC/VLR have a MSRN number.
The mobile dialed from registered VLR to IMSI that assigned a temporary number.That temporary number is MSRN and The ring tone still doesnt exist. MSRN contains Country Code + National GSM Code + Subscriber’s number

EIR(The Equipment Identity Register ) : Some informations about your phone that lost or stolen recorded by the EIR .If someone try to set up a call , HLR checks the EIR if your number is under record calling will closed by HLR

RBS(Remote Base station) : this is the radio gear that passes all calls coming in and going out of a cell site.Contains 1 transmitter and 2 receiver. MSC’s signal is received by both antennas which signal is strongest that transmit to BSC

BSC / TRC() : Between MSC/VLR and BSC.the 64 Kb / s income from MSC that through groups switch to TRC.Here 4 * 16 Kb / sec out as. Before the R7 , TRC was located in BSC named Trau,After R7 named the TRC was located in a separate cabinet.

LAPD UNCONCENTRATED : three device use by TRU. One of them for signal and the other devices require for calling.you can use 10 TRU/X for single 2 Mb in LAPD UNCONCENTRATED

LAPD CONCENTRATED :1 signalling device used by 4 TRU.in this case , 1 tru required 2.25 devices. Because of this you can use 13 TRU/X for single 2 Mb

LAPD MULTIPLEXING : dont required signalling channel . Because of this you can use 15 TRU/x for 2Mb .Suitable for 1 or 2 tru.

Have a nice day… You can find detailed explanations on the site … if there are any issues, I’ll glad if you forward to me … I will continue definitions of the system survey … This was small and easy part …And last thing , sorry for my bad English

Some abbreviations meanings

BSC : Base Station Controller
BTS=RBS : Base Station.—- 3 BTS = 1 RBS
TG : Each sector is given to a number in BTS . A BTS consist of maximum 3 sectors
TF : Timer
TRX : Consist of TCH’s
TX : transmitter
RX : reciever
TS : Telecommunication channel
TRXC : TRX Control element
KASKAT : named of indirect connections
RBLT : 2 MB direct connection port that 2 MBs coming from BSC through PCM
RILT : 2 MB connection that from a BTS through PCM to another BTS
RALT : 2 MB connection that BSC connection between MSC and BSC
MALT : 2 MB connection that MSC connection between MSC and BSC
BCCH : Each of antenna has unique signal channel and it seems always busy
SDCCH : preparation to channel of calling

Definition of the 2MB

NTCOP : SNT = ETRBLT – XXX ;                        —>Find the devices of 2 Mb
EXDAI : DEV = RBLT – XXX && – XXX ;          —>IN-SERVICE the devices of 2 Mb
BLODE : DEV = RBLT – XXX && – XXX ;          —>Deblocking the devices of the 2 Mbs

Control of the 2 MB

DTSTP : DIP = dip ; This command gives status of the DIP.If status isnt ABL or Fault Code maybe SNT was down .
NTSTP : SNT = snt;                                                —>This command gives status of the SNT
EXCLP : EQM = CLC – XX —> CLC information
NTCOP : SNT = snt ;                                              —>This command gives datas of the SNT
RADRP : DEV = RBLT – XXX ;                          —>This command could give RP number If enter the device number of 2 Mb
STDEP : DEV = RBLT – XXX && – XXX ;              —>Range of the RBLT devices

Fault codes failure of 2MB
1.MSC that our side isnt work
2.PCM that our side isnt work
3.Bit Error or MSC that opponent side isnt work
4.PCM that opponent side isnt work

Performance of 2MB

DTQSP : DIP = RBLT XX ;           —>Limit Alarms
DTQUP : DIP = RBLT XX ;

Solution quality problems of the 2 MB

DTQSR : DIP = RBLT XX , SF , DEGR , UNACC ;

Find the DEVICE’s SNT

RADEP : DEV = RBLT – XXX ;

Find EM and RP of DEVICE

RADRP : DEV = RTTFID – XXX

Find TRAU DEVICES at the POOL

RRTPP : TRAPOOL = ALL ;
RNOTRA = number of devices defined trau
ANOTRA = number of devices used trau RTTF1S1 = Control dev.
TRAIDLE = number of devices in idle that trau
TRATRAF = number of devices in traffic that trau

Find trau devices in blocks

STBSP : DETY = RTTF1D1 ;                                                       —>trau devices will appear in blocks
RXTBI : DEV = RTTFID1 XXX && – XXX ,FORCE ;            —>For Blocking
RXTBE : DEV = RTTFID1 XXX && – XXX ;                           —>For Dblocking
RXTEI : DEV = RTTFID1 XXX & - XXX , FORCE ;             —> Blocking xxx and xxx devices

Defining the RP to BTS

EXRPI : RP = rp , TYPE = STC2D ;
EXRUI : RP = rp , SUNAME = suname , SUID = suid ;
BLRPE:RP = rp ;

Status of RP

EXRPP:RP= rp ;                              —>If RP isnt work(ABL or CBL) we should try blocking and deblocking
BLRPI:RP= rp ;                               —>RP  Block
BLRPE:RP= rp;                               —> RP Dblock

BLOCK – DBLOCK OF EM

EXEMP : RP = rp , EM = ALL ;                                                 —>Finding of EM that connected the RP and TWIN RP
BLEMI : RP = rp , RPT= rpt , EM=em ;                                —> Blocking of the EM
BLEME : RP = rp , RPT= rpt , EM=em ;                               —>DBlocking of the EM
EXRPP : RP= rp ;                                                                          —>RP state

Removing of EM blocks

REPRI : RP= rp;
REMRI : RP= rp , PCB= STCP;
RECRI : RP= rp;

Checking Control of the EMRP CARD

EXEPP : EMG= emg name , EM= em ;                                  —>EM Control
BLEEI : EMG= emg name , EM= em ;                                  —>EMRP Block
BLEEE : EMG= emg name , EM= em ;                                 —>EMRP Dblock

CLC CONTROL

EXCLP : EQM = CLC – XX ;                                                      —>State must be working. If state is CBL check the RP.
EXEGP : EMG = ALL ;                                                               —>CLC State checking
EXCPP : EMG = ALL ;                                                               —>CLC state Checking (Above R7 )

we saw WO with EXCLP command and we saw BL with EXEGP Command We should perform this procedure

RECEI : EMG = emg name , STR= A ;                                —>Reset of STR BOARD
RECEI : EMG = emg name , EMRP= 0 – A ;                    —>Reset of EMRP BOARD
EXRPP : RP = rp ;                                                                    —>if RP State is ABL perform the blocking and deblocking procedure
BLRPI : RP =rp;
BLRPE : RP =rp;
BLCLI : EQM= CLC – XX ;                                                     —>CLC Block
BLCLE : EQM= CLC – XX ;                                                   —>CLC Dblock

CLC status is working .BUT SEMIPARMENENT Status is Block then perform the procedure

SYESI : EMG = emg name , EM = ALL, ;
RIBLI : EMG= emg name , EMRS= 0 ;                          —>  Blocking of RILT
RIRTI : EMG = emg name ,EMRS = 0 ;                        —> Test of RILT
RIBLE : EMG= emg name , EMRS= 0 ;                         —> Dblock of RILT
RECEI : EMG= emg name , STR= A ;
RECEI : EMG= emg name , EMRP= 0 – A ;

IF CLC is CBL —–>

BLCLI : EQM= CLC – XXX ;                                             —> CLC Block
BLCLE : EQM= CLC – XXX ;                                            —> CLC Dblock

If doesnt work perform the below

EXRPP : RP= rp ;                                                              —>If RP state is AB or ABL , Perform The blocking Dblocking
BLRPI : RP= rp ;                                                               —>RP Block
BLRPE : RP= rp;                                                               —>RP Dblock

If CLC state is SEAL perform this procedure

Check the 2 MB, Be sure working Then
EXEGP : EMG= emg name ;                                —>Find CLC and RP
EXCPP : EMG= emg name ;                                —>State of CLC
If CLC state is BL give this command ———> RECEI : EMG= emg name , STR= A ;
EXRPP : RP= rp ;                                                   —>State of RP
BLRPI : RP= rp ;                                                    —>RP Block
BLRPE : RP= rp ;                                                   —>RP Dblock

If still doesnt work (BTS, Should be reset from the EMRP card)

To make the name change SEMIPARMENENT Links
RISPE : TSLOT= RILT XX – XX && XX ;                                                               —>release the SEMIPARMENENT
RISPI : TSLOT1= RILT XX – XX , TSLOT2 = RILT – XX – XX , NAME = CTRL cid A1 , REL ;
RISPI : TSLOT1= RILT XX – XX , TSLOT2 = RILT – XX – X , NAME = TCH cid A1 ;
RISPI : TSLOT1= RILT XX – XX , TSLOT2 = RILT – XX – X , NAME = TCH cid A2 ;

Have a nice days …

1-What will 3G mean to users?

With access to any service anywhere, anytime, from one terminal, the old boundaries between communication, information, media and entertainment will disappear. Services will truly converge.

“Mobility” will be offered with many services that we currently regard as “fixed” – indeed, Mobile operators believes that mobility will become the norm for many communication services. We’ll be able to make video calls to the office and surf the internet, or play interactive games with friends at home – wherever we may be.

But 3G is not just about applications that require high speed data rates. It’s about convienience and speed of access.

2-BASIC TECHNOLOGY FEATURES 1G-2G-3G

a) TECHNOLOGY FEATURES 1G
AMPS Advanced Mobile Phone Service

• -Analog voice service
• - No data service

b) TECHNOLOGY FEATURES 2G
CDMA Code Division Multiple Access

• - Digital voice service
• - 9.6K to 14.4K bit/sec.
• - CDMA, TDMA and PDC offer one-way data transmissions only
• - Enhanced calling features like caller ID
• - No always-on data connection

TDMA Time Division Multiple Access
GSM Global System for Mobile Communications
PDC Personal digital cellular
c) TECHNOLOGY FEATURES 3G
W-CDMA (Wide-band Code Division Multiple Access )

• - Superior voice quality
• - Up to 14.0 Mbit/s on the downlink and 5.8 Mbit/s on the uplink with HSPA+
• - Broadband data services like video and multimedia
• - Enhanced roaming

CDMA-2000 Based on the Interim Standard-95 CDMA standard
TD-SCDMA Time-division synchronous code-division multiple-access
The packet based IP (Internet Protocol) technology that will form the core of future services will mean we can be on-line constantly: e-mail messages with file attachments will download to hand-held terminals instantaneously; at the push of a button we’ll be connected to our company network. We’ll have this “anytime access” with charging geared more towards how much information we are sending than to how long we are connected.

There will also be a growing need for mobile users to interact with machines, and for machines to interact with other machines, over radio connections – reporting faults, ordering new stock, or relaying location details whenever required.

Companies outside telecoms today will take advantage of 3G to develop innovative new services.

The question of 3G deployment is not a technical issue, but a regulatory and economic one. Subscriber demand is the key factor: user expectations for mobile services are being raised, and for any successful 3G license bidder time to market will be critical. The way 3G is rolled out in a particular market will depend entirely on the business plans of the mobile operators, and the license requirements imposed by the regulatory authorities.

Today’s mobile network operators can gain the vital business and market experience of providing high-speed mobile data services by introducing packet switching networks such as GPRS (General Packer Radio Service). By the time the new WCDMA, EDGE and cdma2000 wideband radio interfaces are standardized and commercially available, the market will already be attuned to the possibilities of 3G. Japan was the first market to announce specific plans to introduce wideband radio networks based on WCDMA technology. As a result, 3G went into service first in Japan in May 2001 .The 3G licensing process has completed in many countries in Europe, and the first wideband radio networks were enter commercial operation in 2002. Before then, GPRS will be introduced into GSM networks, to increase user bandwidth. The first GPRS systems was introduced early in 2000 in France but due to handset shortest and technical problems of the advance overall network architecture, it was not a success.

The Speed

3G enables users to transmit voice, data, and even moving images. In order to realize these services, 3G improves the data transmission speed up to 144Kbps in a high-speed moving environment, 384Kbps in a low-speed moving environment, and 2Mbps in a stationary environment. 3G provides services like Internet connection, transmission of large-scale data and moving contents photographed by digital cameras and videos, and software downloading.

3G allows simultaneous use of speech and data services and higher data rates (up to 14.0 Mbit/s on the downlink and 5.8 Mbit/s on the uplink with HSPA+). Thus, 3G networks enable network operators to offer users a wider range of more advanced services while achieving greater network capacity through improved spectral efficiency.

Security

3G networks offer a greater degree of security than 2G predecessors. By allowing the UE (User Equipment) to authenticate the network it is attaching to, the user can be sure the network is the intended one and not an impersonator. 3G networks use the KASUMI block crypto instead of the older A5/1 stream cipher. However, a number of serious weaknesses in the KASUMI cipher have been identified [14].
In addition to the 3G network infrastructure security, end-to-end security is offered when application frameworks such as IMS are accessed, although this is not strictly a 3G property.

Applications Of 3G
3G offers a wide range of applications. These applications are mainly made possible due to the enhanced data rates as a result of the 2Mbps bandwidth availabilities. Some of the applications are.

1. Mobile TV – Due to the high data transfer rate being offered due to 3G, TV can be viewed on Mobile Phones. For this have to tie up with a service provider, through which the content can be accessed. Eg.Apalya for BSNL(India).
2. Video Conferencing – It is possible to conduct a video conferencing using the available network, due to the 2 Mbps bandwidth.
3. Tele-medicine – This is an extended feature of video conferencing where a remote person can be given attention by a doctor located at a distant place.
4. Location Based Services – These are some services which can be accessed on the dependence of the service provider. These include weather updates, live road traffic view, and vehicle tracking.
5. Video on Demand – Videos can be viewed on demand from a service provider. For providing this service, the service provider should have collaborations with content providers such as Perceptknorigin (in India). This is again possible due to high buffering speed possible due to the 3G network.

Detailed Information Evolution from 2G
2G networks were built mainly for voice services and slow data transmission.
From 2G to 2.5G

The first major step in the evolution to 3G occurred with the introduction of General Packet Radio Service (GPRS). So the cellular services combined with GPRS became ’2.5G.’
GPRS could provide data rates from 56 kbit/s up to 114 kbit/s. It can be used for services such as Wireless Application Protocol (WAP) access, Multimedia Messaging Service (MMS), and for Internet communication services such as email and World Wide Web access. GPRS data transfer is typically charged per megabyte of traffic transferred, while data communication via traditional circuit switching is billed per minute of connection time, independent of whether the user actually is utilizing the capacity or is in an idle state.
From 2.5G to 2.75G (EDGE)

GPRS networks evolved to EDGE networks with the introduction of 8PSK encoding. Enhanced Data rates for GSM Evolution (EDGE), Enhanced GPRS (EGPRS), or IMT Single Carrier (IMT-SC) is a backward-compatible digital mobile phone technology that allows improved data transmission rates, as an extension on top of standard GSM. EDGE was deployed on GSM networks beginning in 2003—initially by Cingular (now AT&T) in the United States.
EDGE is standardized by 3GPP as part of the GSM family, and it is an upgrade that provides a potential three-fold increase in capacity of GSM/GPRS networks. The specification achieves higher data-rates by switching to more sophisticated methods of coding (8PSK), within existing GSM timeslots.
Evolution towards 4G

Both 3GPP and 3GPP2 are currently working on further extensions to 3G standards, named Long Term Evolution and Ultra Mobile Broadband, respectively. Being based on an all-IP network infrastructure and using advanced wireless technologies such as MIMO, these specifications already display features characteristic for IMT-Advanced (4G), the successor of 3G. However, falling short of the bandwidth requirements for 4G (which is 1 Gbit/s for stationary and 100 Mbit/s for mobile operation), these standards are classified as 3.9G or Pre-4G.
3GPP plans to meet the 4G goals with LTE Advanced, whereas Qualcomm has halted development of UMB in favour of the LTE family.[5]
On December 14, 2009 Telia Sonera announced in an official press release that “We are very proud to be the first operator in the world to offer our customers 4G services.”[15] With the launch of their network, initially they are offering services in Stockholm, Sweden and Oslo, Norway.

Disadvantages of 3G
Although 3G was successfully introduced to users across the world, some issues are debated by 3G providers and users:

• Expensive input fees for the 3G service licenses in some jurisdictions
• Differences in licensing terms between states
• Level of debt incurred by some telecommunication companies, which makes investment in 3G difficult
• Lack of state support for financially troubled operators
• Cost of 3G phones
• Lack of coverage in some areas
• Demand for broadband services in a hand-held device
• Battery life of 3G phones

Since 4G is currently still in a long development phase, there is not much in the way of a formal definition at this time. One of the strongest objectives for 4G technology will be to create a system capable of providing between 100 Mbit/s and 1 Gbit/s speeds both indoors and outdoors with premium quality, making tasks like video conferencing, VOIP, and music and video downloading much smoother than what is currently available. High security will also be a priority as developers work to create new 4G systems.

4G takes on a number of equally true definitions, depending on who you are talking to. In simplest terms, 4G is the next generation of wireless networks that will replace 3G networks sometimes in future. In another context, 4G is simply an initiative by academic R&D labs to move beyond the limitations and problems of 3G which is having trouble getting deployed and meeting its promised performance and throughput. In reality, as of first half of 2002, 4G is a conceptual framework for or a discussion point to address future needs of a universal high speed wireless network that will interface with wireline backbone network seamlessly. 4G is also represents the hope and ideas of a group of researchers in Motorola, Qualcomm, Nokia, Ericsson, Sun, HP, NTT DoCoMo and other infrastructure vendors who must respond to the needs of MMS, multimedia and video applications if 3G never materializes in its full glory. WiMAX, or Worldwide Interoperability for Microwave Access, is already available in many locations around the world and debuted in the US in September of 2008. WiMAX is available in several regions of the US from Clearwire under the brand name CLEAR (Sprint’s XOHM product is being re-branded to merge with CLEAR) and is also re-sold by Sprint (“Sprint 4G”) and others like Time Warner Cable and Comcast in select markets. Long Term Evoution, or LTE, is a second 4G technology, which carriers including Verizon Wireless and AT&T are developing to employ as the eventual broadband successor to UMTS. Verizon plans to launch their first LTE markets in the US in 2010.

Motivation for 4G Research Before 3G Has Not Been Deployed?

Compare 3G -4G

Major Requirement Driving Architecture

In 3G —> Predominantly voice driven – data was always add on
In 4G —> Converged data and voice over IP

Network Architecture

In 3G —> Wide area cell-based
In 4G —> Hybrid – Integration of Wireless LAN (WiFi, Bluetooth) and wide area

Compare of Speeds

In 3G —> 384 Kbps to 2 Mbps
In 4G —> 20 to 100 Mbps in mobile mode

Frequency Band

In 3G —> Dependent on country or continent (1800-2400 MHz)
In 4G —> Higher frequency bands (2-8 GHz)

Bandwith

In 3G —> 5 MHz – 20 MHz
In 4G —> 100 MHz or more

Switching Design Basis

In 3G —> Circuit and Packet
In 4G —> All digital with packetized voice

Access Technologies

In 3G —> W-CDMA, 1xRTT, Edge
In 4G —> OFDM and MC-CDMA (Multi Carrier CDMA)

Component Design

In 3G —> Optimized antenna design, multi-band adapters
In 4G —> Smarter Antennas, software multiband and wideband radios

IP

In 3G —> A number of air link protocols, including IP 5.0
In 4G —> All IP (IP6.0)

What is needed to Build 4G Networks of Future?

Source Wikiepedia
MSISDN Format

An MSISDN is limited to 15 digits, prefixes not included (e.g., 00 prefixes an international MSISDN when dialing from Sweden).
MSISDN – Mobile Station International Subscriber Directory Number
In GSM and its variant DCS 1800, MSISDN is built up as
MSISDN = CC + NDC + SN
CC = Country Code
NDC = National Destination Code, identifies one or part of a PLMN
SN = Subscriber Number
In the GSM variant PCS 1900, MSISDN is built up as
MSISDN = CC + NPA + SN
CC = Country Code
NPA = Number Planning Area
SN = Subscriber Number
Example
MSISDN: 79261234567
CC 7 Russia
NDC 926 MegaFon
SN 1234567 Subscriber’s number
For further information on the MSISDN format, see the ITU-T specification E.164.

Start Clone
—————————————
Necessary for BOTH NODES
—————————————
6- Give reboot both nodes and Press F2 for Bios
7- Select “Advanced Menu“
8- Select “Compact Flash” and Select “Enable“
9- Select the menu “Boot” by using Arrow Keys.
10- Select “Boot Device Priority” and press
11- Under “Exclude from boot order“, select “IDE 0“
12-Press
Note: “IDE 0″ will now be visible under “Boot priority order”
13- Select item “IDE 0″ under “Boot priority order”
14- Press <+> to make “IDE 0″ the first item under “Boot priority order”

——————————————————————-
For A Node
——————————————————————-
15- Save and exit by pressing . The node will now reboot.
16- Enter the LSI MegaRAID SCSI BIOS by pressing when “Press to run MegaRAID Configuration Utility” message appears on the screen.
17- Select Objects->Adapter and press
18-Set Fast Initialization to “On”. Move using / and press . Set the value to “On” and press again . Confirm the change by pressing “Yes”.
19-Go back to the Management Menu pressing .
Select Objects->Adapter->Adapter1
20- Open the “Other Adapter Options” menu
21- Select Initiator ID
22- Change it to 7 if on Node A and 6 if on Node B
23- Leave LSI MegaRAID SCSI BIOS by pressing again. Confirm Exit by selecting “Yes”.
24- Reboot the node by pressing .
25- Wait until the system has completed the boot process and the “Factory preinstallation” window has disappeared.
Note: The screen might “flash” multiple times during boot.
Note: There might be a popup saying that there’s and IP conflict in
the network. It’s ok, ignore that.
Connect to the server, where the flash disk software has been stored, by using the command:
“X:\>net use * \\(192.168.200.200)\sharename(alclon)“
26- Where the sharename is the directory containing the “PrepRaid” tools. Change to that server by typing: X:\>Z: (the drive that was created by using net use).
27- To prepare the system for LBB SW 8.x clone deployment execute the
following command:
“Z:\>PrepRaid.exe /8x”
Where 8x means 80 for LBB SW 8.0 and 81 for LBB SW 8.1
28- If the PrepRaid.exe reported
“All operations finished successfully, please reboot computer!” do that by typing:
Z:\>X:
X:\>exit
Note = !!! After type of “exit” System will be reboot … We have to press F2

——————————————————————-
For B Node
——————————————————————-
29- Save and exit by pressing . The node will now reboot.
30- Enter the LSI MegaRAID SCSI BIOS by pressing when “Press to run MegaRAID Configuration Utility” message appears on the screen.
31- Select Objects->Adapter and press
32-Set Fast Initialization to “On”. Move using / and press . Set the value to “On” and press again . Confirm the change by pressing “Yes”.
33-Go back to the Management Menu pressing .
Select Objects->Adapter->Adapter1
34- Open the “Other Adapter Options” menu
35- Select Initiator ID
36- Change it to 7 if on Node A and 6 if on Node B
37- Leave LSI MegaRAID SCSI BIOS by pressing again. Confirm Exit by selecting “Yes”.
38- Reboot the node by pressing .
39- Wait until the system has completed the boot process and the “Factory preinstallation” window has disappeared.
Note: The screen might “flash” multiple times during boot.
Note: There might be a popup saying that there’s and IP conflict in the network. It’s ok, ignore that.
Connect to the server, where the flash disk software has been stored, by using the command:
“X:\>net use * \\(192.168.200.200)\sharename(alclon)“
40- Where the sharename is the directory containing the “PrepRaid” tools. Change to that server by typing: X:\>Z: (the drive that was created by using net use).
41- To prepare the system for LBB SW 8.x clone deployment execute the
following command:
“Z:\>PrepRaid.exe /8x”
Where 8x means 80 for LBB SW 8.0 and 81 for LBB SW 8.1
42- If the PrepRaid.exe reported
“All operations finished successfully, please reboot computer!” do that by typing:
Z:\>X:
X:\>exit
Note = !!! After type of “exit” System will be reboot … We have to press F2
——————————————————————-
For A Node
——————————————————————-
43- Connect to the server, where the flash disk software has been stored, by using the command:

” X:\>net use * \\\sharename “

Change to that server by typing: X:\>Z: (the drive that was created by using net use).
” X:\>Z: “

44- In Z directory , run the ghost32.exe
” Z:\>ghost32.exe “

And then

Select ” LOCAL->Disk->FROM IMAGE “

45- Select ghost file for A node then select “Fujitsu Disk ” ( If u dont have disk name fujitsu u can chose disk that 38GB )
46 -End of the ghost you will see two option: ” Continue ” or ” Reset The Computer “

Press the ” Continue ” then select quit from ghost program

Then wait for another node …

——————————————————————-
For B Node
——————————————————————-
47- Connect to the server, where the flash disk software has been stored, by using the command:

” X:\>net use * \\\sharename “

Change to that server by typing: X:\>Z: (the drive that was created by using net use).
” X:\>Z: “

48- In Z directory , run the ghost32.exe
” Z:\>ghost32.exe “

And then

Select ” LOCAL->Disk->FROM IMAGE “

Select ghost file for A node then select “Fujitsu Disk ” ( If u dont have disk name fujitsu u can chose disk that 38GB )
49- End of the ghost you will see two option: ” Continue ” or ” Reset The Computer “

Press the ” Continue ” then select quit from ghost program

——————————————————————-
Both NODES
——————————————————————-
50- Type ” exit ” in the both nodes at the same time
51- Press F2 for BIOS
——————————————————————-
B node
——————————————————————-
52- Press F9 and then Press F10 for save and exit

——————————————————————-
A node
——————————————————————-
53- Wait until windows (approximately 10 or 15 seconds) on B node and then Press F9 and then Press F10 for save and exit on A node

IMPORTANT : Installition process automatically. !!!Don’t Touch Keyboard and MOUSE !!!!
It will take 1.5 hours. And then First on A node “Installitionprocess Done” messages will be shown. Dont Press wait until same message on B node.
————————————————————————————————-

Post Cloning Steps

————————————————————————————————-
After Clone some resources go offline. In cmd windows give “prcstate” on both nodes and see active and passive then give ” Cluster res ” and be sure all resources online or offline .
——————————————————————-
A node
——————————————————————-

1- If .Manage Your Server. window appears on this node select the checkbox .Don.t display this page at next logon. and close the window.

2- Check status of the A node : Check if the node A is active. If not do a failover on B node to make the A node active Do NOT use prcboot, use the following command or GUI.

” C:\>shutdown /R /t 1 /m . “

——————————————————————-
BOTH node
——————————————————————-
:\TEMP>PostCloneAP.bat

Remove PostCloneAP.bat:

C:\TEMP>del PostCloneAP.bat

——————————————————————————————————-
3.1 System parameter change Known Bugs and Limitations of FrConfig:

After Frconfig AP_1 resource may fail make it manually online
————————————————————————————————
FrConfig process:
———————————————————————————————–
NOTE! Frconfig must be run locally, it cannot be run in a remote desktop session.

——————————————————————-
A node
——————————————————————-

1- Check if the node A is active. If not do a failover on B node to make the A node active
Do NOT use prcboot, use the following command or GUI.

C:\>shutdown /R /t 1 /m .

2- Open a command prompt. Change the directory
c:\>cd \Program Files\Force\FrConfig

3- Start FrConfig:

C:\Program Files\Force\FrConfig>frconfig

4- Answer with y on the first question

“Do you really want to change the parameters:”

Enter the parameters, which need to be changed. Select the parameter from the list by typing its number and then enter its value.

5- After the parameters is entered select option

“14. Set parameters and configure the system”

6- Check if all the parameters are correct and then answer y on question
7-
“Are these parameters correct”

8- Enter the current administrator password.

9- On the final question
“Do you really want to change parameters and continuethe process”

answer y and start the process.

10- Wait until you get:

“Parameter change completely on node ”

DO NOT TOUCH THE KEYBOARD OR MOVE THE MOUSE DURING FRCONFIG.
The process can take up to 2 hours.

——————————————————————-
BOTH nodes
——————————————————————-
11- Press any key to exit.

Check that the service .Cluster Service. is started with:

C:\>net start | findstr Cluster

and locate .Cluster Service. in the list. If it is not started, start it with:

C:\>net start “Cluster Service”

If that fails reboot the node with:

C:\>shutdown /r /t 1

——————————————————————-
A node
——————————————————————-
12- Check if the node A is active. If not do a failover to make the A node active. Do NOT use prcboot, use the following command or GUI.
C:\>shutdown /R /t 1 /m .

13- Make resource AP_1 online

C:\>cluster res AP_1 /on /wait

14- Open a command prompt. Change the directory

C:\>cd \Temp

Run the following command

C:\Temp>postFrconfig.bat

NOTE: Above Script has to be implemented only when frconfig has to be executed (it solves the problem reported in HI14015).

Remove postFrconfig.bat
C:\Temp>del postFrconfig.bat

———————————————————————————————————
3.2 Post system parameter change
———————————————————————————————————
Both nodes Her 2 node ta yapilmasi gerekenler …

1- Check that one node is passive and the other is active with

c:\>prcstate

Note: If one of the nodes is undefined, make sure the cluster service is running before continuing.

2- Run configap

C:\>configap -a
Ignore error printout about missing user SUPPORT_388945a0 and missing ddi files.
Ignore error printouts like missing files in the paths c:\acs\core\fcr, c:\acs\core\prc, c:\acs\core\usa.

3- Change service account users

Run the following command

c:>setupservices .n

If error Failed[1057] occurs for one or more but not all services run the following command (NOTE! Without option .n)

c:>setupservices

——————————————————————————————————–
B NODE
——————————————————————————————————–

4- Shutdown B node Do NOT use prcboot, use the following command (note the S) or GUI.

C:\>shutdown /S /t 1 /m

——————————————————————————————————–
A NODE
——————————————————————————————————–

5- Reboot A node Do NOT use prcboot, use the following command (note the R) or GUI.

C:\>shutdown /R /t 1 /m

This reboot might take longer time then expected.

6- Be sure B node is up and working

Restart B node After the A node is up and running restart the B node remotely, using the command

C:\>fcc_reset .f other

this restart might take longer time then expected.
7- Make resource AP_1 online

C:\>cluster res AP_1 /on /wait

——————————————————————————————————–
B NODE
——————————————————————————————————–
8- After the B node is up and running do the following. In the list of users there shall be two service users with account names made up by random characters.

Start Administrative Tools-Domain Controller Security Policy-Local Policies-User Rights Assignment-Log on as a service..

In the list of users there shall be two service users with account names made up by random characters.
If one of them is missing do the following.Run the following command in an command prompt:
C:\>dsquery user .desc S*

The printout will show two service users, one of them should be found under .Log on as a service.. The missing one has to be added to .Log onas a service. by the following procedure. Press .Add User or Group. ! .Browse.. Enter the first few characters of the name of the missing service user and press Check Names. The complete name will appear, check that it is the correct one. Press OK three times and exit .Default Domain Controller Security Settings.. Run the following command:
C:\>gpupdate /force

——————————————————————————————————–
BOTH NODE
——————————————————————————————————–

9- Change service account user settings After both nodes up and running then run the following command:

C:\>setupservices .a
——————————————————————————————————–
A NODE
——————————————————————————————————–

10- Run post parameter configuration script After the B node is up and running run the following command:

C:\temp>postParamChange.bat

Remove script

C:\temp>del postParamChange.bat

11- Start the cluster resources Run the script:

C:\Temp>postStartclusrsc.bat

Remove the script:
C:\temp>del postStartclusrsc.bat

Note: If one group goes into status .failed. then wait a few minutes and check if it is online with:

c:\>cluster group

Both nodes

12- Set security

The script PostCloneSecurity.bat will check if the old security configuration (apg40org.inf) exists and create it if it doesn.t, set the new security settings using secedit and reconfigure the size of the security log.

 C:\Temp>PostCloneSecurity.bat

Remove the script

 C:\Temp>del PostCloneSecurity.bat

Both nodes Configure the APG as AP1/AP2/AP3

13- Execute the FewerCloneConfig_A.bat file to configure the clone to either AP1, AP2 or AP3 configuration. ( AP1 tek bir APG var ise AP1 seciyoruz…)

 C:\Temp>FewerCloneConfig_A.bat AP1 (for AP1)
 C:\Temp>FewerCloneConfig_A.bat AP2 (for AP2)
 C:\Temp>FewerCloneConfig_A.bat AP3 (for AP3)

Note: Ignore the error .The system was unable to find the specified registry key or value..

14- Execute the swrprod batch file to assign swrsid and add the swrprod information to the different APG configurations.

 C:\Temp>swrprod_agm018_AP1.bat (for AP1)
 C:\Temp>swrprod_agm018_AP2.bat (for AP2)
 C:\Temp>swrprod_agm018_AP3.bat (for AP3)

Note: Ignore the printout swrsid: The option -r takes no arguments.
Usage: swrsid [ -n newsystem | -r | -h ]

A-node (active)

15- Configure the time zone

 C:\>mtzln .. 0

Note! - C:\>tzls can be used to check for time zones.
Example below should be typed as one line.

C:\>mtzln .(GMT+01:00) Amsterdam, Berlin, Bern, Rome,Stockholm, Vienna. 0

16- Verify & Fix RAID mirrors Verify data disk with the following commands:

 C:\temp\>postCheckRaid.bat

Note: The status should be “OPTIMAL”

17- IF The status isnt “OPTIMAL”
If needed, rebuild the disks with the following command:

 C:\>megarc .doRbld .a0 .RbldArray[1:1,1:2]

NOTE: The command above is only an example and shows how to rebuild channel 1 target 1 and channel 1 target 2.

Check Status with command:

 C:\Temp\>postCheckRaid.bat

Wait until Status is OPTIMAL.

The script checkraid.bat contains the following command:

 megarc .ldinfo .a0 .Lall | findstr Status:

Wait until the status is OPTIMAL

4 Configure AP1/AP2 for different APZ types

4.1 Configure AP1 for APZ 212 3x (Both single and dual APG40)
AP1 ve 212 30- 33 icin gecerli olan proceduredir
——————————————————————————————————–
BOTH NODE
——————————————————————————————————-

1- Check the CPTASP and APCONF parameter values set the values depending on the APZ type using soft function change.

 C:\temp>phaprint MAS_CPTASP_*

Name: MAS_CPTASP_Protocol
Level: Private Named Table: N/A
[Unsigned Int]: 0 for SDLC APZ 212 3x
1 for TCP/IP APZ 212 3x

 C:\temp>phaprint ACS_APCONFBIN_*
Name: ACS_APCONFBIN_CpAndProtocolType
Level: System Named Table: N/A
[Unsigned Int]: 0 for SDLC APZ 212 3x
1 for TCP/IP APZ 212 3x

2- If the APG40 is used as a single AP1 configuration connected to an APZ21233 continue with chapter 5

3- Dual APG connected to APZ 212 3x reconfiguration This must be done on both nodes on AP1 in a dual AP configuration connected to an APZ 212 3x

 C:\Program Files\AP\ACS\conf>2123x_ap1_2ap.bat

4.2 Configure AP1 for APZ 212 40 (Both single and dual APG40) Both nodes

AP1 ve 212 40 icin gecerli olan proceduredir
——————————————————————————————————–
BOTH NODE
——————————————————————————————————–
Open C:\Program Files\AP\ACS\conf\ 21240.dhcp in an editor and replace the dummy MAC addresses, numbers starting with 00000 on line 8, 10, 21 and 23, with correct values. The correct values are the MAC addresses for the network interfaces for eib_a, eib_b, eic_a and eic_b.
NOTE! It is possible to change the dummy MAC addresses later via the GUI

1- Single AP configuration connected to an APZ 212 40 reconfiguration

 C:\Program Files\AP\ACS\conf>21240_ap1_1ap.bat

2- Dual AP configuration connected to an APZ 212 40 reconfiguration

 C:\Program Files\AP\ACS\conf>21240_ap1_2ap.bat
4.3 Configure AP1 for APZ 212 50 (Both single and dual APG40)

——————————————————————————————————–
BOTH NODE
——————————————————————————————————–
There is no need to change the file C:\Program Files\AP\ACS\conf\21240.dhcp, the MAC addresses will be change automatically to correct value by MODDBIN.

1- Single AP configuration connected to an APZ 212 50 reconfiguration Run the script.

 C:\Program Files\AP\ACS\conf>21250_ap1_1ap.bat

2- Dual AP configuration connected to an APZ 212 50 reconfiguration Run the script.

 C:\Program Files\AP\ACS\conf>21250_ap1_2ap.bat

4.4 Configure AP2 for APZ 212 3x

If the APG40 is used as an AP2 connected to an APZ21233 continue with chapter 5

4.5 Configure AP2 for APZ 212 40

This must be done on both nodes on AP2 in an dual AP configuration connected to an APZ 212 40

 C:\Program Files\AP\ACS\conf>21240_ap2_2ap.bat

4.6 Configure AP2 for APZ 212 50

This must be done on both nodes on AP2 in an dual AP configuration connected to an APZ 212 50

 C:\Program Files\AP\ACS\conf>21250_ap2_2ap.bat

Cleanup

——————————————————————————————————–
BOTH NODE
——————————————————————————————————–
Delete the files in C:\Temp and C:\Test
Run command:
 C:\>del C:\Temp\*.* /S /Q
 C:\>del C:\Test\*.* /S /Q
 C:\>rd C:\Test /S /Q

Installation of AM FW version 1.13

1- Log on as a user to both nodes.Check the status of the node by entering the command “prcstate” from the “Command Prompt”.

 Prcstate

2- Check the latest installed Platform Package

 C:\>swrprint

Note the LBB Platform Package Version. The LBB Platform Package must be P3.4 or higher, to be allowed to proceed with the next steps.

3- Check on the passive node which version of the AM-FW that is installed:

 C:\>fcc_amversion own

Perform the following for Platform Package Version P3.4 or higher: If the name of the FW is “1.13″ the AM-FW is already installed.If so, proceed with step if this is the first node,
or exit if this is the second node.

4- Install the AM-FW by entering the following commands: Move to the following directory:

 C:\>cd C:\Program Files\Force\Am_services

Enter the following for Platform Package Version P3.4 or higher:
C:\Program Files\Force\Am_services> klasoru icerisinden

 C:\Program Files\Force\Am_services>fcc_am_download own -file:lbb_am_appl_1_13_0_r_sys_ram.bin -f

5- Perform a manual reboot on the passive node: A reboot will occur.

 C:\>prcboot -f

6- Log on as a user to this node.

7- Check the version of AM-FW installed using the following command

 C:\>fcc_amversion own

8- Log on as a user to the other active node.

9- Perform a fail-over by rebooting the active node:

 C:\>prcboot -f

A reboot will occur, and the active node will become the passive node.

10- Repeat the steps 3) – 7) for this passive node.

Configure CP
——————————————————————————————————-
BOTH NODE
——————————————————————————————————–

1- Update IPN SW if needed.This needs to be done only on APZ 212 3x based AXE. On APZ 212

40 and 50 this shall not be done. Check the status/revision of the IPN SOFTWARE on the IPN Adapter

on the CP. Compare it to the status/revision of the IPN SOFTWARE, provided on the APG40 and do a

function change of the IPN SOFTWARE if necessary. Use the OPI ref [1] 3/154 31-CNZ 221 109 Uen,

Inter-Platform Network Software, Change. If needed do the procedure .Load IPN Software.

from OPI on the active node, steps (step numbers refer to rev D) 30-46.
—————————————————————————————————
AFTER POST CLONE , INSTALL IAM18
—————————————————————————————————
1.1 Extract update file
——————————————————————————————————–
BOTH NODE
——————————————————————————————————–
Extract the update package file to the temp directory F drive.
 F:\TEMP>pkzipc -extract -dir -over=all 018_19099-5_LZY242060_1018_A.exe F:\TEMP
After the extraction on both nodes delete the package files.
 F:\TEMP>del 018_19099-5_LZY242060_1018_A.exe /q
Update procedure for AP1
Passive node
1. Logon to node
Verify that the node is the passive node

 F:\TEMP>prcstate

Verify that all cluster resources are online
 F:\TEMP>cluster group
2. Synchronize the nodes time with the time of the cluster
 F:\TEMP>net time \\192.168.169.33 /SET /y
3. Check the FCH state
 F:\TEMP>fchstate
The state should be noFCH

4. Check for the automatic backup execution
Before starting the function change please check for the FCR auto backup using the below command.
 F:\TEMP>prcstate –l
Printout:
active node is up and working
passive node is up and working
backup/restore in progress
If the backup is running please wait till it finishes then start the function change
5. Start function change
Note: While doing this function change –j nonStandard option must be used
 F:\TEMP>fchstart –k F:\TEMP\options1.txt
The procedure will install the CXC’s. After the installation a reboot is initiated.

Procedure is described in installation instructions for update of the AP software, see Ref [6] 1/154 31-CNZ 222 79 Uen, APG40,Hard function change ,Software change. Function Change session lasts approximately 40 minutes. This time does not include time necessary for the supervision period, that depends on configuration of the machine.

Log on as administrator to this node. Several attempts may be required to be able to log on, due to the reboot.

A switchover of the resources will be performed automatically by FCH. The passive node will become active. Check the prcstate:

 F:\TEMP>prcstate

Check the FCH state:

 F:\TEMP>fchstate

Wait for the printout to be “SUPERVISION HAS BEGUN”.
Updated active node
6. Commit the software when the supervision period has finished the system shall be committed
 F:\Temp>fchcommit
Non-updated passive node
7. Logon to the non-updated node
Verify that the node is the passive node

 F:\TEMP>prcstate
Verify that all cluster resources are online
 F:\TEMP>cluster group
End the function change
 F:\TEMP>fchend

After the installation of the SW the node will be rebooted
8. Logon to node
Verify that the node is the passive node
 F:\TEMP>prcstate
Verify that all cluster resources are online
 F:\TEMP>cluster group

9. Check the FCH state
 F:\TEMP>fchstate The state should be noFCH

10. Execute the following command
 F:\TEMP>configap –i –s –d
1.2 Update procedure for AP2

Passive node
 Logon to node
Verify that the node is the passive node
 F:\TEMP>prcstate

Verify that all cluster resources are online
 F:\TEMP>cluster group
 Synchronize the nodes time with the time of the cluster
 F:\TEMP>net time \\192.168.169.34 /SET /y
 Check the FCH state
 F:\TEMP>fchstate
The state should be noFCH
 Check for the automatic backup execution
Before starting the function change please check for the FCR auto backup using the below command.
 F:\TEMP>prcstate –l
Printout:
active node is up and working
passive node is up and working
backup/restore in progress
If the backup is running please wait till it finishes then start the function change
 Start function change
Note: While doing this function change –j nonStandard option must be used
Check whether the H/W is APG40 C/2 or C/4
 C:\temp>hwver

AP HARDWARE VERSION
APG40C/4 or APG40C/2
If APG40C/2 continue with
 F:\TEMP>fchstart –k F:\TEMP\options2.txt
Else if C/4 then continue with
 F:\TEMP>fchstart –k F:\TEMP\options1.txt
The procedure will install the CXC’s. After the installation a reboot is initiated.

Procedure is described in installation instructions for update of the AP software, see Ref [6] 1/154 31-CNZ 222 79 Uen, APG40,Hard function change ,Software change . Function Change session lasts approximately 40 minutes. This time does not include time necessary for the supervision period, that depends on configuration of the machine..
Log on as administrator to this node. Several attempts may be required to be able to log on, due to the reboot.
A switchover of the resources will be performed automatically by FCH. The passive node will become active. Check the prcstate:

 F:\TEMP>prcstate

Check the FCH state:

 F:\TEMP>fchstate

Wait for the printout to be “SUPERVISION HAS BEGUN”.
Updated active node
Commit the software When the supervision period has finished the system shall be committed
 F:\Temp>fchcommit
Non-updated passive node
Logon to the non-updated node
Verify that the node is the passive node

 F:\TEMP>prcstate

Verify that all cluster resources are online

 F:\TEMP>cluster group
End the function change

 F:\TEMP>fchend

After the installation of the SW the node will be rebooted
Logon to node Verify that the node is the passive node

 F:\TEMP>prcstate

Verify that all cluster resources are online
 F:\TEMP>cluster group
Check the FCH state
 F:\TEMP>fchstate
The state should be noFCH

10. Execute the following command
 F:\TEMP>configap –i –s -d
1.3 Update procedure for AP3
Passive node
Logon to node Verify that the node is the passive node
 F:\TEMP>prcstate

Verify that all cluster resources are online
 F:\TEMP>cluster group
Synchronize the nodes time with the time of the cluster
 F:\TEMP>net time \\192.168.169.33 /SET /y
 Check the FCH state
 F:\TEMP>fchstate

The state should be noFCH
Check for the automatic backup execution
Before starting the function change please check for the FCR auto backup using the below command.
 F:\TEMP>prcstate –l
Printout:
active node is up and working
passive node is up and working
backup/restore in progress
If the backup is running please wait till it finishes then start the function change
Start function change
Note: While doing this function change –j nonStandard option must be used
Check whether the H/W is APG40 C/2 or C/4
C:\temp>hwver

AP HARDWARE VERSION
APG40C/4 or APG40C/2
If APG40C/2 continue with
 F:\TEMP>fchstart –k F:\TEMP\options2.txt
Else if C/4 then continue with
 F:\TEMP>fchstart –k F:\TEMP\options1.txt
The procedure will install the CXC’s. After the installation a reboot is initiated.

Procedure is described in installation instructions for update of the AP software, see Ref [6] 1/154 31-CNZ 222 79 Uen, APG40,Hard function change ,Software change . Function Change session lasts approximately 40 minutes. This time does not include time necessary for the supervision period, that depends on configuration of the machine..

Log on as administrator to this node. Several attempts may be required to be able to log on, due to the reboot.

A switchover of the resources will be performed automatically by FCH. The passive node will become active. Check the prcstate:
 F:\TEMP>prcstate

Check the FCH state:
 F:\TEMP>fchstate

Wait for the printout to be “SUPERVISION HAS BEGUN”.
Updated active node
Commit the software When the supervision period has finished the system shall be committed
 F:\Temp>fchcommit
Non-updated passive node
Logon to the non-updated node Verify that the node is the passive node
 F:\TEMP>prcstate

Verify that all cluster resources are online
 F:\TEMP>cluster group
End the function change
 F:\TEMP>fchend

After the installation of the SW the node will be rebooted
Logon to node Verify that the node is the passive node
 F:\TEMP>prcstate

Verify that all cluster resources are online
 F:\TEMP>cluster group
Check the FCH state
 F:\TEMP>fchstate
The state should be noFCH
10) Execute the following command

 F:\TEMP>configap –i –s –d

1.4 Update software product identification
Both nodes
Execute the product update installation script
 F:\TEMP>swrprod_iam018.bat

1.5 Remove the installation files

Both nodes
 Remove installation files:

 F:\TEMP>del /q F:\TEMP\*

 C:\>rd F:\TEMP\ /s /q

 C:\>md F:\TEMP\

 C:\>rd C:\TEMP\ /s /q

 C:\>md C:\TEMP\

Key benefits

The unique scalability of the MSC-S Blade Cluster gives network operators great flexibility when building
their mobile softswitch networks and expanding network capacity as traffic grows, all without complicating network topology by adding more and more MSC servers. The MSC-S Blade Cluster fulfills the extreme in-service performance requirements put on large nodes. First, it is designed to ensure zero downtime – planned or unplanned. Second, it can be integrated into established and proven  network-resilience concepts such as MSC in Pool. Because MSC-S Blade Cluster operation and maintenance (O&M) does not depend on the number of blades, the scalability feature, significantly reduces operating expenses per subscriber as node capacity expands. Compared with traditional, Nonscalable MSC servers, the MSC-S Blade Cluster has the potential to reduce power consumption by up to 60 percent and the physical footprint by up to 90 percent thanks especially to its optimized redundancy concepts and advanced
components. Many of its generic components are used in other applications, such as IMS. The MSC-S Blade Cluster also supports advanced, business-efficient network  solutions, such as MSC-S nodes that cover  multiple countries or are part of a shared mobile-softswitch core network  (Table 1). 

Key components

The key components of the MSC-S Blade Cluster (Figure 1) are the MSC-S blades, a signaling proxy (SPX), an IP load balancer, an I/O system and a site infrastructure support system (SIS). The MSC-S blades are advanced generic processor boards, grouped into clusters and jointly running the MSC server application that controls circuitswitched calls and the mobile media gateways. The signaling proxy (SPX) serves as the Network interface for SS7 signaling traffic over TDM, ATM and IP. It distributes external SS7 signaling traffic to the MSC-S blades. Two SPXs give 1+1 redundancy. Each SPX resides on a doublesided APZ processor. The IP load balancer serves as the network interface for non-SS7-based IP-signaling traffic, such as the session
initiation protocol (SIP). It distributes external IP signaling to the MSC-S blades. Two IP load-balancer boards give 1+1 redundancy.The I/O system handles the transfer of data – for example, charging data, hot billing data, input via the manmachine interface, and statistics to and from MSC-S blades and SPXs. The MSC-S Blade Cluster I/O system uses the APG43 (Adjunct Processor Group version 43) and is 1+1 redundant. It is Connected to the operation support system (OSS). Each I/O system resides on a doublesided processor.The site infrastructure support system, which is also connected to the operation support system, provides the I/O system to Ericsson’s Infrastructure components.

Key characteristics
Compared with traditional MSC-S nodes, the MSC-S Blade Cluster offers breakthrough advances in terms of
redundancy and scalability. Redundancy The MSC-S Blade Cluster features tailored redundancy schemes in different domains. The network signaling interfaces (C7 and non-C7) and the I/O systems work in a 1+1 edundancy configuration.If one of the components is unavailable, the other takes over, ensuring that service availability is not affected, regardless of whether component downtime is planned (for instance, for an upgrade or maintenance actions) or unplanned (hardware failure). The redundancy scheme in the domain of the MSC-S blades is n+1.Although the individual blades do not feature hardware redundancy, the cluster of blades is fully redundant. All blades are equal, meaning that every blade can assume every role in the system.
Furthermore, no subscriber record, mobile media gateway, or neighboring node is bound to any given blade.

Therefore, the MSC-S Blade Cluster continues to offer full service availability when any of its blades is unavailable. Subscriber records are always maintained on two blades to ensure that subscriber data cannot be lost. In the unlikely event of simultaneous failure of multiple blades, the cluster will remain fully operational, experiencing only a loss of capacity (roughly proportional to the number of failed blades) and minor loss of subscriber records. With the exception of very short interruptions that have no affect on in-service performance, blade failures have no affect on connectivity to other nodes. Nor do blade failures affect availability for traffic of the userplane resources controlled by the MSC-S Blade Cluster. To achieve n+1 redundancy, the cluster of MSC-S blades employs a set of advanced distribution algorithms. Fault-tolerant middleware ensures that the blades share a consistent view of the cluster configuration at all times. The
MSC-S application uses stateless distribution algorithms that rely on this cluster view. The middleware also provides a safe group-communication mechanism for the blades. Static configuration data is replicated on every blade. This way, each blade that is to execute a requested service has access to the requisite data. Dynamic data, such as subscriber records or the state of external traffic devices, is replicated on two or more blades. Interworking between the two redundancy domains in the MSC-S Blade Cluster is handled in an i innovative manner. Components of the 1+1 redundancy domain do not require detailed information about the distribution of tasks and roles among the MSC-S blades. The SPX and IP load balancer, for example, can base their forwarding decisions on stateless algorithms. The blades,on the other hand, use enhanced, industry-standard redundancy mechanisms when they interact with the 1+1 redundancy domain for, say, selecting
the outgoing path. The combination of cluster middleware, data replication and stateless distribution algorithms provides a distributed system architecture that is highly redundant and robust. One particular benefit of n+1 redundancy is the potential to isolate an MSC-S blade from traffic to allow maintenance activities – for example, to update or upgrade software without disturbing cluster operation. This means zero planned cluster downtime.
Scalability
The MSC-S Blade Cluster was designed with scalability in mind: to increase system capacity one needs only add MSC-S blades to the cluster. The shared cluster components, such as the I/O system, the SPX and IP load balancer, have been designed and dimensioned to support a wide range of cluster capacities from
very small to very large.
The individual MSC-S blades are not visible to neighboring network nodes, such as the BSC, RNC, M-MGw, HLR, SCP,P-CSCF and so on. This first enabler is essential for smooth scalability: blades can be added immediately without affecting the configuration of cooperating nodes. Other parts of the network might
also have to be expanded to make full use of increased blade cluster capacity. When this is the case, these steps can be decoupled and taken independently. The second enabler is the ability of the MSC-S Blade cluster to dynamically adapt its internal distribution to a new blade configuration without manual intervention. As a consequence, the capacity-expansion procedure is almost fully automatic – only a few manual steps are needed to add a blade to the running system. When a generic processor board is inserted and registered with the cluster middleware, the new blade is loaded with a 1-to-1 copy of the application software and a configuration of the active blades. The blade then joins the cluster and is prepared for manual test traffic.
For the time being it remains isolated from regular traffic. The blades automatically update their internal distribution tables to the new cluster configuration and replicate all necessary dynamic data, such as subscriber records, on the added blade. These activities run in the background and have no affect on cluster capacity or availability. After a few minutes, when the internal preparations are complete and test results are satisfactory, the blade can be activated for traffic. From this point on, it handles its share of the cluster load
and becomes an integral part of the cluster redundancy scheme. MSC-S Blade Cluster hardware Building practice The MSC-S Blade Cluster is housed in an Enhanced Generic Equipment Magazine (E-GEM). Compared with the GEM, the E-GEM provides even more power per subrack and better cooling capabilities, which translates into a smaller footprint.
Generic processor board
The Generic Processor Board (GEP) used for the MSC-S blades is equipped with an x86 64-bit architecture processor. There are several variants of the equipped GEP board, all manufactured from the same printed circuit board. In addition, the GEP is used in a variety of configurations for several other components in
the MSC-S Blade Cluster, namely the APG43, the SPX and SIS, and other application systems. Infrastructure components The infrastructure components provide layer-2 and layer-3 infrastructure for the blades, incorporating routers, SIS and switching components. They also provide the main on-site layer-2 protocol infrastructure for the MSC-S Blade Cluster. Ethernet is used on the backplane for signaling traffic. Hardware layout The MSC-S Blade Cluster consists of one or two cabinets (Figure 2). One cabinet houses mandatory subracks for the MSC-S blades with Infrastructure components,the APG43 and SPX. The other cabinet can be used to house a subrack for expanding the MSC-S blades and two subracks for TDM or ATM signaling interfaces.Power consumption Low power consumption is achieved by using advanced low-power processors in E-GEMs and GEP boards. The high subscriber capacity of the blade-cluster node means very low power consumption per subscriber.
Conclusion
The MSC-S Blade Cluster makes Ericsson’s Mobile Softswitch solution even better – one that is easy to scale
both in terms of capacity and functionality. It offers downtime-free MSC-S upgrades and updates, and outstanding node and network availability. What is more, the hardware can be reused in future node and network migrations. The architecture, which is based on a cluster of blades, is aligned with Ericsson’s Integrated Site concept and other components, such as the APG43 and SPX. O&M is supported by the OSS.
The MSC-S Blade Cluster distributes subscriber traffic between available blades. One can add, isolate or remove blades without disturbing traffic. The system redistributes the subscribers and replicates subscriber data when the number of MSC-S blades changes. Cluster reconfiguration is an automatic procedure; moreover, the procedure is invisible to entities outside the node.

Source

1 – Short explanations of basic terms

The GSM network consists mainly of the following functional parts:

• MSC – the mobile service switching centre (MSC) is the core switching entity in the network.
The MSC is connected to the radio access network (RAN); the RAN is formed by the BSCs and
BTSs within the Public Land Mobile Network (PLMN). Users of the GSM network are registered
with an MSC; all calls to and from the user are controlled by the MSC. A GSM network has
one or more MSCs, geographically distributed.

• VLR – the visitor location register (VLR) contains subscriber data for subscribers registered in
an MSC. Every MSC contains a VLR. Although MSC and VLR are individually addressable,
they are always contained in one integrated node.

• GMSC – the gateway MSC (GMSC) is the switching entity that controls mobile terminating calls. When a call is established towards a GSM subscriber, a GMSC contacts the HLR of that
subscriber, to obtain the address of the MSC where that subscriber is currently registered. That
MSC address is used to route the call to that subscriber.
• HLR – The Home Location Register (HLR) is the database that contains a subscription record for
each subscriber of the network. A GSM subscriber is normally associated with one particular
HLR. The HLR is responsible for the sending of subscription data to the VLR (during registration)
or GMSC (during mobile terminating call handling).
• CN – the core network (CN) consists of, amongst other things, MSC(s), GMSC(s) and HLR(s).
These entities are the main components for call handling and subscriber management. Other
main entities in the CN are the equipment identification register (EIR) and authentication centre
(AUC). CAMEL has no interaction with the EIR and AUC; hence EIR and AUC are not further
discussed.
• BSS – the base station system (BSS) is composed of one or more base station controllers (BSC)
and one or more base transceiver stations (BTS). The BTS contains one or more transceivers
(TRX). The TRX is responsible for radio signal transmission and reception. BTS and BSC are
connected through the Abis interface. The BSS is connected to the MSC through the A interface.
• MSC – Mobile Switching Center the primary service delivery node for GSM, responsible for handling voice calls and SMS as well as other services (such as conference calls, FAX and circuit switched data). The MSC sets up and releases the end-to-end connection, handles mobility and hand-over requirements during the call and takes care of charging and real time pre-paid account monitoring.

A GSM network is a public land mobile network (PLMN). Other types of PLMN are the time
division multiple access (TDMA) network or code division multiple access (CDMA) network. GSM
uses the following sub-division of the PLMN:

• Home PLMN (HPLMN) – the HPLMN is the GSM network that a GSM user is a subscriber of.
That implies that GSM user’s subscription data resides in the HLR in that PLMN. The HLR
may transfer the subscription data to a VLR (during registration in a PLMN) or a GMSC (during
mobile terminating call handling). The HPLMN may also contain various service nodes, such as
a short message service centre (SMSC), service control point (SCP), etc.
• Visited PLMN (VPLMN) – the VPLMN is the GSM network where a subscriber is currently
registered. The subscriber may be registered in her HPLMN or in another PLMN. In the latter
case, the subscriber is outbound roaming (from HPLMN’s perspective) and inbound roaming
(from VPLMN’s perspective). When the subscriber is currently registered in her HPLMN, then
the HPLMN is at the same time VPLMN.1
• Interrogating PLMN (IPLMN) – the IPLMN is the PLMN containing the GMSC that handles
mobile terminating (MT) calls. MT calls are always handled by a GMSC in the PLMN, regardless
of the origin of the call. For most operators, MT call handling is done by a GMSC in the HPLMN;
in that case, the HPLMN is at the same time IPLMN. This implies that calls destined for a GSM
subscriber are always routed to the HPLMN of that GSM subscriber. Once the call has arrived in
the HPLMN, the HPLMN acts as IPLMN. MT call handling will be described in more detail in
subsequent sections. When basic optimal routing (BOR) is applied, the IPLMN is not the same
PLMN as the HPLMN.

The user of a GSM network is referred to as the served subscriber; the MSC that is serving that
subscriber is known as the serving MSC. Examples are:

• mobile originated call – the MSC that is handling the call is the serving MSC for this call; the
calling subscriber is the served subscriber;
• mobile terminated call – the GMSC that is handling the call is the serving GMSC for this call;
the called subscriber is the served subscriber.
2 – Signalling in GSM

The various entities in the GSM network are connected to one another through signalling networks.
Signalling is used for example, for subscriber mobility, subscriber registration, call establishment,
etc. The connections to the various entities are known as ‘reference points’. Examples include:
• A interface – the connection between MSC and BSC;
• Abis interface – the connection between BSC and BTS;
• D interface – the connection between MSC and HLR;
• Um interface – the radio connection between MS and BTS.
Various signalling protocols are used over the reference points. Some of these protocols for GSM
are the following:
• mobile application part (MAP) – MAP is used for call control, subscriber registration, short
message service, etc.; MAP is used over many of the GSM network interfaces;
• base station system application part (BSSAP) – BSSAP is used over the A interface;
• direct transfer application part (DTAP) – DTAP is used between MS and MSC; DTAP is carried
over the Abis and the A interface. DTAP is specified in GSM TS 04.08 [49];
• ISDN user part (ISUP) – ISUP is the protocol for establishing and releasing circuit switched
calls. ISUP is also used in landline Integrated Services Digital Network (ISDN). A circuit is the
data channel that is established between two users in the network. Within ISDN, the data channel
is generally a 64 kbit/s channel. The circuit is used for the transfer of the encoded speech or
other data. ISUP is specified in ITU-T Q.763 [137].
When it comes to call establishment, GSM makes a distinction between signalling and payload.
Signalling refers to the exchange of information for call set up; payload refers to the data that is
transferred within a call, i.e. voice, video, fax etc. For a mobile terminated GSM call, the signalling
consists of exchange of MAP messages between GMSC, HLR and visited MSC (VMSC). The
payload is transferred by the ISUP connection between GMSC and VMSC. It is a continual aim
to optimize the payload transfer through the network, as payload transfer has a direct cost aspect
associated with it. Some network services are designed to optimize the payload transfer. One
example is optimal routing.

3 – GSM Mobility

Roaming with GSM is made possible through the separation of switching capability and subscription
data. A GSM subscriber has her subscription data, including CAMEL data, permanently registered
in the HLR in her HPLMN. The GSM operator is responsible for provisioning this data in the HLR.
The MSC and GMSC in a PLMN, on the other hand, are not specific for one subscriber group.
The switching capability of the MSC in a PLMN may be used by that PLMN’s own subscribers,
but also by inbound roaming subscribers; see the image the GSM user who is a subscriber of PLMN-A roams to PLMN-B. The HLR in PLMN-A transfers the user’s subscription data to the MSC in PLMN-B. The subscriber’s subscription data remains in the MSC/VLR as long as she is served by a BSS that is connected to that
MSC. Even when the user switches her MS off and then on again, the subscription data remains
in the MSC. After an extended period of the MS being switched off, the subscription data will
be purged from the MSC. When the subscriber switches her MS on again, the subscriber has to
re-register with the MSC, which entails the MSC asking the HLR in the HPLMN to re-send the
subscription data for that subscriber.

When the subscriber moves from one MSC service area (MSC-1) to another MSC service area
(MSC-2), the HLR will instruct MSC-1 to purge the subscription data of this subscriber and will
send the subscription data to MSC-2.
4 – Mobile Station
The MS, i.e. the GSM handset, is logically built up from the following components:
• mobile equipment (ME) – this is the GSM terminal, excluding the SIM card;
• subscriber identification module (SIM) – this is the chip embedded in the SIM card that identifies
a subscriber of a GSM network; the SIM is embedded in the SIM card. When the SIM card is
inserted in the ME, the subscriber may register with a GSM network. The ME is now effectively
personalized for this GSM subscriber; The image shows. The characteristics of the SIM are specified
in GSM TS 11.11. The SIM card contains information such as IMSI, advice of charge parameters,
operator-specific emergency number, etc. For the UMTS network an enhanced SIM is specified,
the universal subscriber identity module (USIM); refer 3GPP TS 31.102.

5 – Identifiers in the GSM Network

GSM uses several identifiers for the routing of calls, identifying subscribers (e.g. for charging),
locating the HLR, identifying equipment, etc. Some of these identifiers play an important role for
CAMEL.

5.1 International Mobile Subscriber Identity

The international mobile subscriber identity (IMSI) is embedded on the SIM card and is used to
identify a subscriber. The IMSI is also contained in the subscription data in the HLR. The IMSI is
used for identifying a subscriber for various processes in the GSM network. Some of these are:

• location update – when attaching to a network, the MS reports the IMSI to the MSC, which uses
the IMSI to derive the global title (GT) of the HLR associated with the subscriber;
• terminating call – when the GSM network handles a call to a GSM subscriber, the HLR uses
the IMSI to identify the subscriber in the MSC/VLR, to start a process for delivering the call to
that subscriber in that MSC/VLR.
• roaming charging – a VPLMN uses the IMSI to send billing records to the HPLMN of
a subscriber.
Image shows the format of the IMSI.
• mobile country code (MCC) – the MCC identifies the country for mobile networks. The MCC is
not used for call establishment. The usage of MCC is defined in ITU-T E.212 [129]. The MCC
values are allocated and published by the ITU-T.
• mobile network code (MNC) – the MNC identifies the mobile network within a mobile country
(as identified by MCC). MCC and MNC together identify a PLMN. Refer to ITU-T E.212 [129]
for MNC usage. The MNC may be two or three digits in length. Common practice is that, within
a country (as identified by MCC), all MNCs are either two or three digits.
• mobile subscriber identification number (MSIN) – the MSIN is the subscriber identifier within
a PLMN.
The IMSI is reported to the SCP during CAMEL service invocation. The IMSI may be needed,
for example, when identifying a country; countries in North America have equal country code
(country code = 1), but different MCC (e.g. Canada = 303; Mexico = 334).

5.2 Mobile Station Integrated Services Digital Network Number (MSISDN Number)

The MSISDN is used to identify the subscriber when, among other things, establishing a call to that
subscriber or sending an SMS to that subscriber. Hence, the MSISDN is used for routing purposes.
The image shows the structure of the MSISDN.
• country code (CC) – the CC identifies the country or group of countries of the subscriber;
• national destination code (NDC) – each PLMN in a country has one or more NDCs allocated to
it; the NDC may be used to route a call to the appropriate network;
• subscriber number (SN) – the SN identifies the subscriber within the number plan of a PLMN.

The MSISDN is not stored on the subscriber’s SIM card and is normally not available in the
MS.2 The MSISDN is provisioned in the HLR, as part of the subscriber’s profile, and is sent to
MSC during registration. The MSISDN is also reported to SCP when a CAMEL service is invoked.
One subscriber may have multiple MSISDNs. These MSISDNs are provisioned in the HLR. At
any one moment, only a single MSISDN is available in the MSC/VLR for the subscriber.
5.3 International Mobile Equipment Identifier

The international mobile equipment identifier (IMEI) is used to identify the ME [or user equipment
(UE) in UMTS network]. Each ME has a unique IMEI. The IMEI is hard-coded in the ME and
cannot be modified. The image shows the structure of the IMEI. The IMEI is not used for routing
or subscriber identification.
Refer to GSM TS 03.03 [27] for the type approval code (TAC), final assembly code (FAC)
and serial number (SNR). The software version (SV) may be included in the IMEI (‘IMEISV’) to
indicate the version of software embedded in the ME. The IMEI is always encoded as an eight-octet
string. As from CAMEL Phase 4, the IMEI(SV) may be reported to the SCP.
5.4 Mobile Station Roaming Number

The mobile station roaming number (MSRN) is used in the GSM network for routing a call to a
MS. The need for the MSRN stems from the fact that the MSISDN identifies a subscriber, but not
the current location of that subscriber in a telecommunications network. The MSRN is allocated to
a subscriber during MT call handling and is released when the call to that subscriber is established.
Each MSC in a PLMN has a (limited) range of MSRNs allocated to it. An MSRN may be allocated
to any subscriber registered in that MSC. The MSRN has the form of an E.164 number and can
be used by the GMSC for establishing a call to a GSM subscriber. An MSRN is part of a GSM
operator’s number plan. The MSRN indicates the GSM network a subscriber is registered in, but
not the GSM network the subscriber belongs to. The image shows how the MSRN is used for call
routing. The MSRN is not meant for call initiation. GSM operators may configure their MSC such
that subscribers cannot dial numbers that fall within the MSRN range of that operator.

6 Basic Services

All activities that may be done in the GSM network, such as establishing a voice call, establishing
a data call, sending a short message, etc., are classified as basic services. In order for a subscriber
to use a GSM basic service, she must have a subscription to that service.3 The handling of a basicservice is fully standardized. Hence, a subscriber may use a basic service in any GSM network
she roams to, provided that that basic service is supported in that network. The HLR will send
a list of subscribed basic services to the MSC/VLR, during registration. When a GSM subscriber
initiates a call, the MS supplies the serving MSC with a set of parameters describing the circuitswitched
connection that is requested. These parameters are the bearer capability (BC), low-layer
compatibility (LLC) and high-layer compatibility (HLC), as will be described below. The MSC
uses the BC, LLC and HLC to derive the basic service for this call. The rules for deriving the basic
service from LLC, HLC and BC are specified in GSM TS 09.07 [55]. The MSC then checks whether
the subscriber has a subscription to the requested basic service, i.e. whether the subscription data
in the VLR contains that basic service. If the service is not subscribed to, then the MSC disallows
the call. The basic service is not transported over ISUP.

When a CAMEL service is invoked, the MSC reports the requested basic service to the SCP. The
SCP may use the indication of the requested basic service for call service processing. Examples
include:
• video calls may be charged at a higher rate than speech calls;
• for data calls and fax calls, the CAMEL service shall not play any announcements or tones.
Basic services are divided into two groups: tele services and bearer services.

6.1 Tele Services

Table 1.1 provides an overview of the available tele services (TS);

6.2 Bearer Services

Table 1.2 provides an overview of the available bearer services (BS). The two bearer service groups
are sub-divided into a variety of bearer services with different characteristics.

6.3 Circuit Bearer Description

Bearer capability, low-layer compatibility and high-layer compatibility are descriptors of a circuitswitched
(CS) connection. When a GSM subscriber initiates a call, the BC, LLC and HLC are
transported from MS to MSC over DTAP. The MSC includes the parameters in the ISUP signal to
the destination. These parameters are also reported to the SCP during CAMEL service invocation.
That enables a CAMEL service to adapt the service logic processing to the type of call. The image
shows the relation between LLC, HLC and BC on the DTAP and the corresponding parameters
on ISUP.

• Low-layer compatibility – the LLC is transported transparently between the calling entity and
called entity; it may be used by the respective entities to adapt codecs for interworking purposes.
LLC describes mainly characteristics related to the data transfer.
• High-layer compatibility – the HLC is also transported transparently between the calling entity
and called entity; it is used to describe the requested service, such as telephony, Fax, video
telephony, etc.
• Bearer capability – the BC describes the characteristics of the 64 kbit/s circuit requested for
the call.

7 Supplementary Services
Supplementary services (SS) in GSM are a means of enriching the user experience. An SS may,
for example, forward a call in the case of no reply from the called party, bar certain outgoing or
incoming calls, show the number of the calling party to the called party, etc. In order to use an
SS, a GSM user needs a subscription to that SS. The subscription to supplementary services is
contained in the HLR and is sent to the MSC/VLR during registration. The supplementary services
are fully standardized. A GSM subscriber can therefore use her supplementary services in any GSM
network, provided that the network supports these supplementary services, and have the same user
experience.

Supplementary services may be provisioned for an individual basic service or for a group of
basic services, e.g. a subscriber may have barring of all outgoing calls for all tele services and all
bearer services, except SMS (tele service group 20). Such a subscriber is barred from establishing
outgoing calls (except emergency calls), but may still send short messages. Some supplementary
services may be activated or deactivated by the user. Examples include call forwarding and call
barring. An operator may decide to bar certain subscribers or subscriber groups from modifying
their supplementary services.

Table 1.3 shows the Supplementary Services. They are combined in service groups. Subscriptions
are per individual Supplementary Service. The right-most column indicates the GSM technical
specifications (TS) that specify the service requirement for the respective Supplementary Service(s).
The chapters on CAMEL Phases 1–4 describe the interaction between CAMEL and the various
supplementary services. Not all GSM networks support all supplementary services. Many of
the supplementary services in GSM have equivalent supplementary services in ISDN. The ISDN
supplementary services are described in ITU-T recommendations.