Summer Practical Training TATA TELESERVICES LIMITED, OKHLA

INTRODUCTION:
MINS is an IP based so lution that shall be designed to cater to a subscriber base of around 1000 subscribers. It shall support all the features and functio nalities provided by the legacy switching systems. MINS was requir ed as the r ate of the Qualcomm chipset fo r the BSC (base station contro ller) was r ising day by day. Qualco mm co mpany is extr acting 5$ per subscr iber from any Indian company for using their chipset that why in MINS, BSC is constructed not using any hardware but by binding the system by some algorithms. It means that in MINS, softwar e is prepared which can do the work of the hardware chip for BSC instead of using that Qualcomm chipset. The basic aim of designing of the MINS project is the r emoval o f the Qualco mm chipset for BSC. MINS is not the whole network; it is the part of a netwo rk which contains fo llowing networks identities. They are:1. BTS CONTROLLER-Base transceiver system co ntroller 2. BSC-Base station contr oller 3. MSC-Mobile switching centre 4. HLR-Ho me location register 5. VLR-Visitor lo catio n register MINS also contains so me essential parts other than which are specified abo ve. They may be either the parts of the four of them specified abo ve or other o nes. They shou ld be considered in fo llowing lines as they co me into the act. So me assumptions are made pr eparing the MINS project. They are:SSD (Shared secret data) is shared with the VLR, in case of Authentication. MINS system shall work with the Soft switch MGC (Media Gateway Contro ller) for all the calls originating from/ter minating to the PSTN or GSM networks.

SCOPE OF TRAINING
The basic scope or we can say the aim of the training was putting our theories to pr actice. What we have learned in two years of the B.E. degree, were put to practice. Any which we just learn as a theory subject we will forget that thing very quickly, but if we have put that thing to practice we will not for get that thing in our whole life. It is not po ssible fo r a single college to provide the

practical training for all the 350 students because it is too costly to pro vide such machines or systems that a multinational company can provide to the trainees. I have done my summer practical training at Reliance Co mmunicatio n at Dhirubhai Ambani Knowledge City(DAKC), Navi Mu mbai. I t was a great experience to wor k with such great and intelligent colleagues. The who le DAKC so well designed and architect any beauty lover can t mo ve away from that. I think fo r me it was an educational tour. My training was based on MINS (Mobile integrated network system). It was a newly prepared project for wireless co mmunicatio n by the Reliance infoco mm. MINS was a under launch pr oduct whose testing was on the way. According to the project manager of MINS it will take 2-3 yrs to launch this product. So it was not po ssible fo r us to the get the whole knowledge about the MINS so we divided our tr aining to fo llowing phases: Theo retical knowledge about the networks and layers. Theo retical knowledge about the MINS from the document SRS_MINS which was provided by the company to us o n o ur personal computer at Reliance Communications. Testing of the pro ject It includes the checkin g of the message flow between the networ k subsystem when a call is initiated or released. Preparing of the training repo rt. I lear ned a one more thing that preparing a pro ject is just not preparing it but it includes it s testing also which is tedious work to do. It was very difficult for me to stay 45 days away fr om my family and parents. For me it was also one of the aims to recover from family fever. It is co mpu lsor y for every student to complete training of 90 days till we complete our B.E. degree. It is done in two phases 45 days after 2 45 days after 3
nd rd

year. year.

LEARNING OBJECTIVE
It was a long term training in which were tho ught theory about the MINS project and we worked on the testing of MINS project. In testing we worked on the UNIX operating system. MINS project team had prepared the testing environment on the operating system UNIX. They have chosen the UNIX environment as on UNIX multithreading is possible. Multithread ing is process in which mu ltip le system can wo rk at a time. What do we mean with a thread? Technically, a thread is defined as an independent stream of instructions that can be schedu led to run as such by the oper ating system. But what does this mean? In the UNIX envir onment a thread: Exists within a process and uses the pro cess r eso urces

Has its own independent flow of contr ol as long as its parent process exists and the OS supports it May share the process resources with other threads that act equally independently (and dependently) Dies if the parent process dies or so mething similar

METHODOLGY
The pro ject manager Mr. Praveen sing hal had allotted me a computer o n which we study or understand the theo retical knowledge of the MINS project using the SRS_MI NS document (So ftware requirement document_ MI NS) in our half time. After having my lunch when I came back to office then they allot me a laptop which connected to o ne of the subsystem of the network like BSC, BTS etc. I have to submit a report at 6:00 p.m. ever y evenin g what we have co ncluded while we are testing the project. After we put the project (MINS system) we put to a tester which they named as lo ad test. What we do whole day manually, is known as manual test and then when we put it to a tester is kno wn as load test. The flow of messages which we get in the load test can be seen in the logs of the BTS and BSC subsystem. That was work of the employees or I can say the work of my seniors or my teacher s there. When we left from there a viva voce was conducted by the project manager and we submitted the project report to them.

CONTENTS OF TRAINING
1. Initialization of the Pro ject-(Phases) 2. Requirement of these Phases 3. Some Definitions 4. MS-Mobile system 5. Complete descriptio n of MINS 6. Call scenar io of vo ice call flow 7. Call initiated by the MS of MINS 8. General call flow for MINS 9. Ad vantages of MINS

INITIALIZATION OF THE PROJECT:

MINS is a very huge and lengthy pro ject to design and launch for single man and to work on it respectively. So phases are divided and so me teams are set up to make this project a gr and success. The MINS project is divided into 2 Phases listed belo w Phase 1A: The Scope of Phase 1A is to demonstrate a successful Intra MINS and Inter MI NS call alo ng with CDR generation. Hando ff functio nality will no t be supported in this phase of MINS. Phase 1:Phase 1 will be focused on inter faces towards Billing and Mediatio n, NMS, Legal Interceptio n System, and PSTN Wo rld. This phase will also have capability to interact with the prepaid system. Alo ng with this all the bugs observed in Phase 1A will be fixed in Phase 1. At the end o f Phase 1, it will be possible to make inter MINS calls, Intra MINS Calls, Calls to PSTN world, Call to Existing Reliance Wireless Network and Send SMS on the MINS network. Also the Handoff and announcement functio nality shall be supported in this Phase. The Lo ad test as per the Specifications will be carried out after successfu l demonstration o f all the services and integration with the network elements present in the Reliance network. It will include PCF functionality and integration with data network (R world), OTAF (Over The Air Functionality) and VMS (Voice Mail System). Also all the supplementary services develop ment will be taken up in this phase.

REQUIREMENT OF THESE PHASES Phase 1A Requirement Feature o r function that shall be suppo rted by the system to be delivered in in the phase 1A.These are mandatory for the Intra MINS and Inter MINS call establish ment. All Phase 1A requirements are flagged by the letter PH 1A. Phase 1 Requirement Feature or function that shall be supported by the system to be delivered in the phase 1. These are mandatory for supporting Pr epaid functionality, SMS functionality and calls terminating on /fro m PSTN or GSM network as well as to offer Supp lementary services. All Phase 1 requirements are flagged by the letter PH 1. Phase 2 Requirement Feature or function that shall be supported by the system to be delivered in the phase 2. All Phase 2 requirement are flagged by the letter PH 2.

SOME DEFINITIONS:
So me defin itio ns sho uld be useful for upcoming infor matio n.

Assured Mode . Mode of delivery that guarantees that a PDU will be delivered to the peer. A PDU sent in assured mode is retransmitted by the LAC Sublayer, up to a maximum nu mber of retransmissions, until the LAC entity at the sender receives an acknowledgement fo r the PDU. See also Confir mation of Delivery Authentication : A procedure used to validate mobile stations or subscriber s identity. Base Station . A fixed station used for co mmunicating with mobile stations. Depending upon the context, the term base station may refer to a cell, a sector within a cell, an MSC, or other part of the cellular system. See also MSC Common Location Register (CLR): A pr oprietary node that contains the MDN and MIN ranges and the co rresponding HLR addresses. ESN: The unique serial number of a cellular phone that identifies it to the cellular system for the purpose o f p lacing and receiving calls. Home Location Register (HLR): The HLR is the location register to which a user identity is assigned for record purposes such as subscriber information (e.g. ESN, MDN, Profile Information, Current Location, and Author ization Period). IS-41: The netwo rk standar d that allows all switches to exchange infor mation about subscr ibers. Layer 1 (L1).Layer 1 (Physical Layer) provides fo r the transmissio n and reception o f radio signals between the base station and the mobile station Layer 2 (L2). Layer 2 provides fo r delivery of signaling messages generated by Layer 3 (see below). Layer 2 co nsists o f two sub layers: the LAC Sublayer and the MAC Sublayer below). Layer 2 mak es use o f the services pro vided by Layer 1 Layer 3 (L3). Layer 3 originates and terminates sig naling messages according to the semantics and timing of the commu nication protocol between the base station and the mobile station. Layer 3 makes use of the services pro vided by Layer 2 Logical channel. A commu nication path between statio ns, descr ibed in terms of the intended use o f, and access to, the transferred data, and d ir ection o f tr ansfer. A lo gical channel can be mapped to and from one o r more physical channels Lower Layers. In this docu ment, layers belo w the LAC Sublayer (e.g., Layer 1 and the MAC Sub layer) MAC Sub layer. See Medium Access Co ntrol Sublayer Mapping. In this context, the technique for for ming associations between log ical and physical channels Message. Sig naling data unit tr ansferr ed between the base station and the mo bile station. In this document, it should be interpreted as the Layer 3 PDU o r the LAC SDU Medium Access Control (MAC) Sublayer. The MAC Sublayer is the lower sub layer of Layer 2. It implements the medium access protocol and is responsib le for transpo rt of LAC proto col data units using the services provided by Layer 1 (see

Message Control and Status Block (MCSB). In this document, a parameter block representing the inter face control infor mation transferred between Layer 3 and the LAC Sublayer. The MCSB is also used to carry relevant infor mation within the LAC Sublayer.

MDN (Mobile Directory Nu mber):It is a 10 digit unique nu mber, which identify a mobile subscriber MIN: It is a unique 10- digit decimal number programmed into the MS. This MIN is transmitted over the air interface during reg istration to info rm the netwo rk of the identity of the mo bile statio n accessing the network. It is also used as a key field to access the su bscr iber profile record stored in the HLR

Mobile Switching Center (MSC): service

A configuration o f equipment that pro vides cellular or PCS

MS (M obile Station): The Mo bile Station (MS) is the equipment that subscr ibers use to originate and receive information and calls via the wireless networ k. The MS provides the user with access to the r adio network and perfo rms other functions for the user Visitor location registers (VLR). The VLR database contains tempor ary info rmation about subscribers that is need ed by the mobile services switching center (MSC) in o rder to service visiting su bscr ibers. When a mobile statio n roams into a new mobile ser vices switching center (MSC) ar ea, the visitor lo cation reg ister (VLR) connected to that MSC will request data about the mobile statio n from the HLR, reducing the need for interrogation of the ho me location reg ister (HLR).

MS (MOBILE STATION)
The mo bile station (MS) consists o f the mobile equ ipment (the terminal) and a smart card called the Subscriber Identity Module (SIM). The SIM provides personal mo bility, so that the user can have access to subscribed services irrespective o f a specific terminal. By inserting the SIM card into another GSM terminal, the user is able to receive calls at that terminal, make calls from that terminal, and receive other subscribed services. The mo bile equipment is uniquely identified by the Internatio nal Mobile Equipment identity (IMEI). The SIM card co ntains the International Mobile Subscr iber Identity (IMSI) used to

identify the subscriber to the system, a secret key for authenticatio n, and other info rmation. The IMEI and the I MSI are independent, thereby allowing per sonal mobility. The SIM card may be protected against unautho rized use by a password or personal identity number.

COMPLTETE DESCRIPTION OF MINS

MINS is composed of the fo llowing parts which were stated in on of the above section. They are as below: 1. BTS Controller 2. Base station co ntroller 3. Mobile switching centre 4. Ho me location register 5. Visitor location register

OVERVIEW OF MINS (MOBILE INTEGRATED NETWORK SYSTEM)

Descr iptio n o f the above parts is as fo llows: 1. BTS ControllerBTS controller shall be a PowerPC based General Purpose Microcontroller residing in the BTS hardware. For the Phase 1A the BTS hardware shall be the BTS development platform made up of Commercial Off-the-Shelf (COTS) car ds and associated software. The PowerPC 8245 shall have a Real Time Operating System (RTOS) called OSE delta running on it. The BTS controller shall per for m fo llowing functions: CDMA2000 Physical Layer Control: This function will interact closely with the Base band processing algor ithms running on the Tigers ARC 201 (TS-201) DSPs. Abis functions on the BTS side: This function involves packet sing p hysical layer frames into IP PDUs, open sockets and send IP PDUs to the BSC entity of MINS as per the Abis proto col. Similar functions are executed fo r the receipt of IP packets from BSC entity.

OA&M functions for the BTS: This will broad ly include the Configuration, Fault and Perfo rmance management functio ns. I n Phase 1 A only a small subset of these fu nctions shall be implemented. The definition of the entire set of function and this small subset is in pro gress. The Base Transceiver Station houses the radio transceivers that define a cell and hand les the radio-link protoco ls with the Mobile Station. In a large urban area, there will potentially be a large nu mber of BTSs organize, thus the requirements for a BTS are ruggedness, reliability, portability, and minimum co st.

2. BSC- The Base Statio n Co ntroller manages the rad io resources for one or more BTSs. It handles radio-channel setup, frequency hopping, and hando vers, as descr ibed belo w. The BSC is the connection between the mo bile station and the Mobile service Switching Center (MSC).

In the construction o f the BSC, there are following parts. They are as follows: 1. 2. 3. 4. 5. 6. CP-Call pr ocessing Layer 3 LAC MAC ABIS Transport layer

Descr iptio n o f all the above stated parts is as fo llows: 1. Call processing (CP) Call pro cessing is, just like a heart to the human being, for BSC. It creates the messages which are used to be exchanged in between the BSC and BTS, BSC and MSC etc. As a example we take a ORM i.e. Orig ination message. Originatio n message contain three things mainly. They are: IMSI-international mobile station identity ESN- electronic serial nu mber MDN-mobile directory number Other matter also Call pr ocessing prepares the message as fo llo ws belo w:-

1. Layer 3 (L3) - Following L3 signaling messag es will be supported in MI NS BSC Subsystem, which will be sent or received on lo gical channels f-csch & r-csch. Same way the user traffic messages will be carried o n logical channels f- dsch & r-dsch. When message is passed to the L3 from the call processing then L3 will add a header to the message. Now message will be seen like as below:

2. LAC Sub layer- LAC Sub layer shall imp lement a data link proto col that provides for the correct transport and deliver y o f sig naling messages generated by Layer 3. LAC Su b layer will also add a header to the above message.

3. MAC Sub layer- The MAC Sub layer shall implement the med ium access protocol and is respo nsib le for transport o f LAC protocol data units using the ser vices provided by Layer 1. The MAC Sub layer shall also contro l the access to and from upper layer sig naling, Data Ser vices (no t in phase 1 A) and voice services to physical layer reso urces. MAC su b layer will also add a header to the above message.

4. ABIS - The Abis Interface is defined as the interface that provides signaling and traffic between Base Transceiver System (BTS) and Base Statio n Controller (BSC) for MINS Netwo rk. The signaling procedures o n Abis are divided as follo ws: Abis Applicatio n Contro l Signaling those associated with O & M signaling and Abis Signaling. Abis Traffic Sig naling are those that directly asso ciated with a call. They includ e transmit and receive message to/fro m Mo bile Statio n. Abis Transpo rt Signaling Procedures to set up and between BTS and BSC. Abis interface also add a similar head er to the above message. manage the stable link

5. Transport layer (TL) Transport layer is used to take the message fro m Abis o f the BSC to the Abis of the BTS controller.

3. MSC The MSC subsystem of the MINS will be responsible for the call routing functionalities. It will be responsible fo r Call pro cessing and the Mobility management fu nctio ns. In order to install, initialize and configure the Subsystem there will be an EMS function and to ensure the availability o f the subsystem there will be maintenance fu nctio nality built in the system. The central component of the Netwo rk Subsystem is the Mobile Switching Center (MSC). It acts like a normal switching node of the PSTN or ISDN, and additionally pro vides all the functionality needed to handle a mo bile subscriber, such as reg istration, authenticatio n, location updating, handovers, and call routing to a roaming subscriber. These services ar e provided in conjunction with several functional entities, which together fo rm the Network Subsystem. The MSC provides the connection to the fixed networks ( such as the PSTN or ISDN). Signaling between fu nctio nal entities in the Netwo rk Subsystem uses Sig naling System Nu mber 7 (SS7), used fo r trunk signaling in ISDN and widely used in current public networks.

4 . HLR (Home location register) The HLR is a database used for sto rage and management of subscriptions. The home location register stores permanent data of the subscribers; including subscr iber s ser vice pro file, lo cation information, and activity status. HLR tracks and manages individual subscr iber info rmation that is need ed by the network to confirm that callers are valid customers, to ro ute calls, and to provision services. HLR is a centralized database app licatio n that provid es call co mp letion data fo r cellular subscribers. The HLR database contains the ad ministrative information for each subscr iber reg istered in the network, alo ng with the subscr iber s current location. The HLR database is dipped whenever the switch in the mobile network requires subscriber information to complete a call. The HLR is the location register to which a user id entity is assigned for record purposes such as su bscr iber information (e.g. ESN, MIN, MDN, Profile Information, Current Location, and Autho rization Period). The HLR shall provide these two basic fu nctio ns: It shall identify the subscribers served by the MSC. It shall be responsible for pro viding instructio ns/data to MSCs fo r MS registration, call origination and call delivery.

5 . VLR (Visitor location register) The Visito r Location Register (VLR) contains selected administrative infor mation fr om the HLR, necessary for call control and pro visio n o f the subscr ibed services, fo r each mobile currently located in the geographical area controlled by the VLR. Although each functional entity can be imp lemented as an independent unit, all manufacturers of switching equ ipment to date implement the VLR together with the MSC, so that the geographical area co ntrolled by the MSC cor responds to that controlled by the VLR, thus simplifying the sig naling required. Note that the MSC contains no info rmation about particular mobile stations --- this infor matio n is stored in the location registers.

CALLS SCENARIO OF VOICE CALL FLOW

The call scenarios that shall be supported in MINS Phase 1A can be broadly classified into the fo llowing types based on the voice path: 1) Intra-Network : These are the calls between subscr ibers located within the MINS network (home & r oamed subscribers). These calls can further be classified into two sub-catego ries: I. Intra MINS : I ntra MI NS calls are the calls in which the voice path shall be established between A-party and B-par ty both belo ng ing to the same MINS. The scenarios of this category shall be

a. b. c. d. e. f. g. h. i. j. II.

A11-B11 A11-B21 A12-B22 A12-B12 A21-B21 A11-BL1 A21-BL1 AL1-B L1 AL1- B11 AL1-B21

Inter M INS: Inter MINS calls are the calls in which the vo ice path shall be established between A-party and B-par ty belo ng to different MINS. The scenarios of this category shall be: a. b. c. d. e. f. g. h. A11-B22 A11-B23 A11-B12 A12-B11 A12-B21 AL1-B22 A11-BL2 AL1-BL2 MINS and other networks. The scenario s o f this

2) Inter-Network : These ar e calls between category shall be: A. Nor mal Cases: RIM-MINS(ALL- B11) MINS-RIM(A11-BLL) MINS-PSTN PSTN-MI NS B. Roaming Cases : A11-B1L ALL- BL1 A1L-BL1 AL1-B2L

CALL INITIATED BY THE MS OF MINS

1. Starting of BSC and BTS

2. Successful Link establishment Between BTS and BSC 3. BTS Reg istratio n 4. Successful Mobile Or ig inated call (for the A-party) 5. Successful mobile terminated call (for the B-party) 6. voice pack ets flow 7. Successful Call released

No w we start with the complete descr iption of the call started to the call co mp letion 1. Starting of BSC and BTS - Normally BSC and BTS are as the normal personal computer a individual is started by just switching o n them. 2. Successful Link establishment Between BTS and BSCa) The BTs and BSC have been powered on. The BTS and BSC read the Co nfiguratio n file. In configuration file the BSC read the IP address of BTS and BSC itself. The BTS and BSC also has been initialized the po rt for the communication. b) After receiving the IP address of BTS the BSC send s the Link Status Request message to the BTS. The BSC starts timer.

c) The BTS response the BSC by send ing Link status Request message. The BSC sto ps timer after receiving the response from BSC. At this point it co nsidered the link between BTS and BSC is up. 3. BTS Registration a) The BTS sends the Register Request message to the BSC indicating that the BTS is available to support radio network o peratio ns. This message is repeated until a Register Response acknowledges it. b) The BSC sends the Register Response Messag e to the BTS if the registration is successful. Fro m this point the BTS shall operate in the network mode. The BTS shall now be able to receive configuration informatio n fro m the BSC over the Abis interface.

No w the diagrammatically BTS and BSC are shown as below on the next page.

1. Successful Mobile Originated calls (for the A-party) initially ms send s ORM (origination message) to BSC, then BSC create the CCR (call connection reference) . That is BSC assign a reference nu mber to every call i.e. to o rig inated call (A party) and ter minated call (B party). CCR increases up to 4294967295 calls or it is its final limit for CCR. Then normal messaging start thro ugh the stack already had been establishment between BSC and BTS controller, when they were started earlier. When Abis set up is received by BSC, When Abis set up ackno wledgement is received by BTS, and then it creates some dedicated stacks. Now all messages and vo ice frames are sent on dedicated stacks till call is released and Abis Release Ack is not received by BTS. Now it is shown d iagrammatically as on next page. Ded icated stacks ar e in different colour.

Here is the d iagram o f message flow during the su ccessfu l mobile originated call.

5 Successful mobile termination call ---Here ar e the messages flow during the process when Bpart pick up the receiver of the phone or connect to the calling par ty i.e. A-party.

1. Voice packet flows - --Any voice signal is first convert into a message using some algorithms and Walsh code. Voice signals after converted into a message are transferred as shown in the explanatio n o f BSC subsystem 2. Successful call released by MINS Subscriber release of a voice call. ---Here shown is the message flow during the

GENERAL CALL FLOW FOR MINS SUBSCRIBER:

The call flo ws that shall be co mmo n to all MS present in the network are described in the general call flow from A-party to B-party. Specific scenarios arising due to the lo cation or the conditio n of the MS have been covered subsequently. Call flows are divided into three sections- voice, data and message.

Voice Call Flow (BSC-MSC-HLR-BSC):

An end- to-end voice call (BSC-A to BSC-B) can be divid ed into the follo wing sections: 1. 2. 3. 4. 5. 6. 7. 8. 9. Registration Call Initiation B-Party Locating Call Connectio n Call Terminatio n Feature Invocatio n ( Only Call Forwarding Unconditional) Deregistration Profile Updated at the HLR Data unreliable at the HLR

Registration

MS Initiated Registratio n
The MS may initiate registration fo r a number of reasons according to the parameters passed by the BSC. The var io us conditio ns under which a MS gets registered with the MSC can be divided into the fo llowing four scenarios; Call flows for the same are discussed below: i. ii. iii. iv. v. vi. Reg istration initiated by MS when in its Ho me Location Registration initiated by MS when in Roaming Locatio n Registration initiated by MS during a call (zone chang e/time based). Multiple R egistrations with Cancellation Denied at VLR. R egistration initiated by MS when in RIM Network Registration initiated by RIM MS when in MINS Network

B- Party locating After Authorizatio n and channel assignment A-par ty MSC shall try to lo cate the B- party serving MSC. A- party MSC shall check whether B-party belongs to its own home network (MINS) by checking whether the B-party MDN is within the MDN range defined at the MSC. It shall be static loo kup table maintained in the MSC. Note: In case of MINS the MINS IP Address, MSC IP Addr ess, VLR IP Address and the HLR I P Address shall be the same. Each MINS shall have its own unique MSC ID. the indiv idual nodes of MINS (MSC, BSC, HLR and VLR) shall be identified by their respective Identification Nu mber. The combinatio n of the MSC ID and the Identificatio n Number shall be unique to identify a particu lar subsystem of the MINS. This combinatio n shall be used to check the valid ity of the network element

Intra MINS Call

If B-party belo ngs to the or ig inating MI NS system, then MSC shall d ir ectly send LOCREQ to the HLR, else MSC shall query CLR to find the MINS IP Address and Ho me HLR-ID of Bparty. Then, the LOCREQ message shall be sent to the B-Party Home HLR. Between MSC and CLR there will be flow of proprietary informatio n. At the B-party HLR, it shall be checked whether the A-party Current MSC is the same as the Bparty Current MSC. If yes, then no ROUTREQ message shall be sent and the HLR shall send the locreq message towards the MSC. In this case it shall include the B-party MDN as the TLDN for that particular call. The LOCREQ message contains Bill ID (Billing Id) , Dialed Digits (B party MDN),A party MSC-ID etc. The locreq return result message contains the follo wing parameters MIN, ESN, and MSCID. After getting the lo creq message, the B-party serving MSC shall check whether

the TLDN received is defined in its Routing Table. I f yes, then no pag ing procedure shall be initiated. If no, then the Serving MSC (B-Party) shall send a Pag ing Request message to the Serving BSC ( B-party). The BSC (B-party) shall find out the exact lo cation of the B-party and then return the Pag ing Response message to the Serving MSC ( B- party). The Pag ing Request message contains the parameters MIN , ServiceOption etc. The Paging Respo nse message contains the parameters B-party s MIN , ESN , User Zone ID , the Service Option etc . If the Paging Request fails (Timer expiry), the B-par ty serving MSC shall try again and restart the timer, configurable number o f times. If the BSC fails to receive an Assignment Request message or Clear Command message in response to the Paging Response message pr ior to the expiration of timer T303 , then it shall send a Reorder or Release message to the B-party MS, and shall clear all the associated resources

Inter network
RIM to MINS:

Inter Network call MINS to RIM

RIM - MINS

Inter Network Call - MINS-RIM i. ii. MINS to PSTN Since the called party is PSTN subscriber, there is no procedure for Bparty locating. Refer sectio n PSTN to MINS

Inter Network call Call Connect ion

PSTN - MINS

The B-par ty serving MSC shall send the Assignment Request message to wards the B-party serving BSC, to request for allocation of rad io resources. This shall also include the port number of the MSC for the BSC to use for voice path establishment .After allocating the rad io resources

fo r that particular request, the B-party serving BSC shall respond by sending Assignment Complete message to wards the B-party serving MSC. This shall also include the port nu mber of the BSC for the MSC to use for voice path establishment .

Intra MINS Call Connection

After this, the ring back tone shall be played at the A- party MS, using RTP sessio n through the port received in the C M Service Request . No w the B-party Serving MSC shall send the Alert with Info rmation message to the B-party Serving BSC, which shall make the handset o f the B-party to start audible ring ing. When the B-party goes o ff-hoo k, the B-party serving BSC shall send a Connect message to the B-party serving MSC, indicating the same. CALL TERMINATION

Intra MINS Call Termination

When any MS wants to terminate the call, the respective Ser ving BSC shall send the Clear Request message to its r esp ective Serving MSC to indicate that it wishes to release all ServiceOption connections and the associated dedicated resource to that MS.

The C lear Request message shall contain the following parametersCause ( OAM Intervention, Equipment failure, protocol error, radio interface failure, normal cause ) and Cause Layer 3 (when the MS send s the Release Order to clear the call), which indicate the exact reason fo r send ing this message

Intra MINS Call Termination In response to Clear Request , Clear Command message shall be sent from serving MSC to serving BSC instructing it to release all service option connections to the MS and the associated dedicated reso urces. This message shall also contain the Cause and Cause Layer 3 parameters. Then the ser ving BSC shall send Clear Complete message to the serving MSC to inform that all service o ption connections to the MS and the associated ded icated resource have been successfu lly cleared. The Clear Complete message shall have the Power Down indicato r flag that indicates that the mobile powered down at the end o f the call. After that the Clear Co mmand and Clear Complete message shall be exchanged to clear all the r eso urces fo r the seco nd party engaged in the call.

Feature Invocation The FEATREQ (Feature Request) operation is used to request feature subscr iption on behalf o f a registered MS. When per for ming digit analysis o f the dialed digits received from the MS, the MSC shall detect that the dialed digits are a feature control access. After Valid ating tehA-party permissions, the Serving MSC shall send the feature code string (i.e. a string of digits includ ing a feature code), received from the served MS to the HLR associated with the MS in the FEATREQ message. The HLR shall determine the appropriate feature treatment based on the received info rmation and shall return this in a featr eq response message. In this case, the response from the HLR shall not include instructions for the Serving System to set up the call.

Registrat ion Cancellation: The Reg istration Cancellation ( REGCANC ) operation is used to report, to the prior serving VLR or prior serving MSC, that a previously registered MS is no longer in its serving area. The scenarios identified for Reg istratio n Cancellation are: 1) 2) 3) 4) 5) MS de-registration by HLR due to Single Access. MS de-registration by HLR due to Multiple Access Successful scenario. MS de-registration by HLR due to Multiple Access Unsuccessful scenario MS Deregistered by Serving MSC MS Deregistered by Serving VLR

6) MS Deregistered by MINS (HLR) 7) MS Deregistered by RIM

Bulk Deregist ration The BULKDEREG (Bulk Dereg istration) o peration is used by a VLR to infor m the HLR that all ro aming MS data asso ciated with the VLR has been remo ved. The VLR shall send the BULKDEREG message to the HLR to inform the HLR that the VLR has removed all the ro aming MS data asso ciated with that HLR. The HLR shall acknowledge the receipt of this message by an empty bulkdereg .

Bulk Deregistration Call Flow Unreliable Roamer Data Directive The UNRELDIR (UnreliableRo amerDataDirective) o peration is used by the HLR to infor m its associated Serving System VLRs that it has experienced a failure, which has rendered its roaming MS data unreliable. The VLR shall remo ve all record of the MS associated with the HLR from its memor y and shall acknowledge the r eceipt of the same via an empty unreld ir .

Unreliable Roamer Data Directive Call Flow

Qualification Direct ive The QUALDI R (QualificationDirective) operation is used to update the authorization information, profile informatio n, or both, previously obtained for an MS. One o f the several possible results is achieved: 1. The MS is re-author ized with an indicatio n o f the authorization duration. 2. The MS is re-authorized with an indication of the authorizatio n dur atio n along with the deliver y o f the MS s updated calling capabilities to the serving system. 3. An update of the MS s calling capabilities is delivered to the serving system. 4. The MS is de-authorized with reason (e.g., due to a delinquent account).

ADVANTAGES OF MINS:All things are done on Internet Protoco l (IP). That s why it so fast, cheaper than other systems. Ro yalty on the Qualco mm chip was as belo w: 5$ per subscr iber in I NDIA 2$ per subscr iber in CHINA Nothing in U.S.A. But in the manufacture of the MINS system Qualcomm chip for BSC was not required so automatically cost is reduced. Co mpact size and can be install anywhere on a single table also . It more useful for the inter co mmunicatio n in between the remote areas in INDI A. After MINS launch, local calls in INDIA should be free only on the monthly rental. After MINS launch, ISD calls rate will be near about 2 Rs. /min.

ACHIEVEMENTS
The knowledge we acquired from this training in depth abo ut how a mobile makes a call and get connected to other mobile was something like having a plethora amount of knowledge in mobile network system. It is not only just a knowledge we gained through this training, but how to co pe up with the environment, how to manage ourselves when there is no guard ian with us to take care of us and to guide us and at mo st how to behave in o ffice, in fro nt of our seniors and with our team-mates. We were always treated as an emplo yee there, never as a trainee, so it was also a plus po int for us to have a exper ience o f what we will really would able to get somewhere after completing our engineer ing degree. We had experienced just like that we are working in a multinational company fo r 45 days. It was incredible exper ience being there with those brilliant technies.

CONCLUSIONS
The 45 days su mmer practical training undertaken at Reliance Co mmunicatio n, Dhiru bhai Ambani Knowledge City, Navi Mumbai was co mpleted with a great enthusiasm and success. The main aim of having introduced to a totally new office environment and to lear n stunning new things in life was covered in the training period. We came near to the life what we have to face in our coming life working 12 hrs a days, 6days a week and only 10-15days leave in who le year. We came to know that life is too fast and sho rt; this is the only time when we can do something to make o ur career. It will worth to regret afterwards in life that we have not work hard when we have to. So we have to work hard now only.

GLOSSARY
ITIC internet techno logy information centre DAKC-Dhir ubhai ambani knowledge city MI NS- mobile integrated network system MS- mo bile system BSC- Base station contro ller BTS- Base transceiver system MSC-mobile switching centre HLR-home lo cation reg ister VLR-visitor location register CLR-co mmon location register

MGC- Media Gateway Controller SSD-Shared Secret Data GSM-Global System fo r Mobile Commu nication PSTN-Public Switched Telep ho ne Network OTAF-Over The Air fu nctio nality VMS-voice mail system LIS-legal interception system ESN- Electronic ser ial nu mber MDN-mobile directory number MAC-medium access control MCSB-message control and status block SIM-subscriber identity module IMEI-Internatio nal mobile equ ipment identity IMSI-International mo bile subscriber identity COTS-commercial Off-the-shelf RTOS-Real time operating system CDMA-code d ivision multiple access CP-Call pro cessing TL-Transport layer ECAM-Extended channel assignment message ORM-originatio n message CCR- call connectio n reference CRBT- caller ring back tone ACK-Acknowledgement MCC- Mobile country code MCSB-message control and status block CDR-call data reco rder CLI-caller line identificatio n DSP-Digital signal pr ocessing CCS- common channel sig naling UDP-user datagram protocol OAM-operation ad ministrator management LAC-link access channel MAC-Medium access channel TCP-transmission co ntrol protocol CTR- channel transmitter reception