You are on page 1of 11

CAMBODIA MTX-INS Huawei Tech. Ltd., Co.

Co. These messages will be described in details. Figure no.. Ltd.1 below shows the trace of the messages that have been sent while the mobile originating a call to another mobile registered in the same MSC. Mobile originates a call Figure no.CAMBODIA MTX-INS Huawei Tech.1: Mobile originating a call (Part 1) .

. Co.. Ltd.CAMBODIA MTX-INS Huawei Tech.

3.2 and A5. half rate speech version 1 is also supported.Setup(BSSMSC): This message is sent from the BSS side to the MSC informing it with the requested traffic channel. CM means Call Management.CM-service accept (MSCMS): As the mobile station has been already registered in this MSC and a location update process has been taken place before the subscriber request a service. Transfer mode and coding standard. o The called subscriber information: the type of the dialed number and the dialed number itself. 2.Service Request message (MS MSC): This message is sent by the mobile equipment to the MSC through the BSC (Using the Ainterface). For example: GSM half rate speech version 1. which can be A5.. . 4. o Radio channel required: in this field MS specified the preferred channel and the supported one. The data contained in this message is as following: o CM Message type: here it is setup o GSM bearer capability: speech. o If the mobile can support or not the SMS service.3.Class mark request message(MSCMS): This message is sent by the MSC to the MS requesting MS to send some information such that: the RF power class used. 1. Ltd. o The available encryption algorithm that the mobile station can use. the supported encryption algorithms…. This message contains the following data: o Identification for the mobile which can be the IMSI or TMSI. For example: the number attribute is the ISDN telephony number plan. A5. o Speech version octet: The speech versions supported and the coding techniques used in sending this speech. the MSC will send this message to the MS informs it that the service it requested is allowed. o The SPC and the SSN of the MSC is contained in this message. o Another Important information that is contained in this message is the type of service requested by the mobile station. number: 2012100006. so the MSC check the subscriber data and if the subscriber is not barred from doing the required service. For example: full rate speech version 1 preferred. the dialed number and some other information. Some of the information contained in this message is as following: o The RF power Capability.CM. o The global cell identification that the mobile is in its coverage area while doing this call.1. this message is sent when the Mobile equipment requires making a call.etc. also there may be the GT of the MSC contained in this message. Co. o The encryption algorithms that are allowed or not allowed.Class mark update (MSMSC): This message is sent by the MS as a response of the MSC’s class mark request message.CAMBODIA MTX-INS Huawei Tech. also it contains the type of the number of digits of this identification number (it can be even or odd number of digits that consist the identification number). 5.

. Co.CAMBODIA MTX-INS Huawei Tech. Ltd..

it is sent to confirm the setting of the connection sent by the MS. This message contains the MSRN allocated for the called subscriber. the arguments may be represented in the MSISDN of the called subscriber. o The called mobile MSC data. 13.Call proceeding(MSCBSS): This message is sent by the MSC to the BSS. This message is the response of the message setup. o The type of the address attached in this message. If the close of session is not a result of any error occurring in the session. Ltd. Also. for example: MSISDN.Send route information response(HLRMSC): This message is sent by HLR to the MSC. which is the MSC number. the MSC should specify the arguments of this service.Paging(MSCMS): As the MSC received the MSRN for the called MS.MAP provide Roaming Number Response (MSCHLR): This message sent by the MSC to the HLR as a response on the message named as provide roaming information request.MAP send routing information request (MSCHLR): The MSC sends this message to the HLR requesting the routing information (MSRN) for the called subscriber. for example: send routing information. the nature of the address should be specified. which includes the IMSI and MSISDN of the called party. 10. This message is sent after the MSC sends the “SRI” message to the HLR 9. The data contained in this message is as following: o The MSC data: The signaling point of the MSC of the called mobile. The data contained in this message is as following: o The MAP service request type: the type of service requested from HLR. o Send routing information argument: if the service requested from the HLR is to send routing information. it may contain the global title in this message (GT). 14.Map send Route information(HLRMSC): This message is sent by the HLR to the MSC of the calling subscriber. The data contained in this message is as following: o The sender MSC number. the reason would be “Normal Release”. Co. 11.MAP close request (MSC HLR): This message sent by the MSC to HLR informs it to close the map session. The data contained in this message is as following: o The called MS data.MAP provide roaming information request(HLRMSC): This message is sent by the HLR to the MSC requesting MSRN for the called mobile entity. Included in this message is the reason of the closing of the session. Also. Also. 8. Simply.. 6. As the called mobile is registered in the same MSC. MSC start searching for the called MS. . o The number of the called subscriber. the subsystem number of the MSC. the HLR requests the MSRN from the MSC of the calling MS.MAP open request(MSCHLR): The MSC sends the HLR this message to start a new session. 12. it contains the IMSI and MSRN of the called subscriber.CAMBODIA MTX-INS Huawei Tech. The content of this message is the MSRN requested by the HLR for the called subscriber. 7.

Co. o The BSC data: The signaling point of the BSC where the MS is registered. 20.ADD REQ (MSOFTUMG): This message is used to allocate resources for the called party in the UMG. 17. we specified the channel rate (the preferred and the allowed). asking it to allocate circuit resources for the call. Ltd. this message is similar to the message “Call proceeding” sent by the MSC in response to the message setup sent by the BSS. it may contain the global title for the BSC. 24. This is message to inform the MSOFT that the resource reservation is done. This message is used to inform the called party with the characteristics of the connection. Also. for example this could be “speech”. This message contains the location area identification of the called mobile. 15. For example: half or full rate TCH. 21. 16. For example: the radio channel required field that is supported. also the cell identification of the called mobile.Assignment complete (BSSMSOFT): This message is sent from BSS side to the MSOFT to inform the MSOFT that the requested channel has been allocated. The TCH type is specified in this message. 23.ADD Reply(UMGMSOFT): This message is sent by the UMG to confirm the allocation of the resources and give the allocated TID. this is because the message is generated from the side that originates the transactions and in this case it is the MSC side. as UMG resources have already been allocated to the calling party.. also the circuit pool number and the message type which would be BSSMAP assignment complete message. .Assignment REQ(MSCBSS): This message is sent by the MSC to the BSS requesting it to assign traffic channel for the call. the UMG specifies the TID allocated. o The actual Circuit identity code that are going to be used. full rate preferred. as radio resources have already been allocated to the calling party.Assignment REQ(MSCBSS): This message is used to allocate radio resources for the called party. 18.ADD Reply(UMGMSOFT): This message is sent by the UMG as a response for the ADD REQ message. The data included in this message is as following: o The channel type: in this field the MSC specifies the type of data that would be transferred along this link.Setup(MSCBSS): This message is sent for this time by MSC not from BSS. 19. o The Cell identification of the cell where the mobile is registered. Also. also its SSN. so that if the preferred is not available it can use the allowed.Paging response(BSSMSC): This message is sent form BSS side to the MSC as a response for the paging message sent by the MSC.Call confirmed(BSSMSC): This message is sent by the BSS side. Also. 22.CAMBODIA MTX-INS Huawei Tech.ADD REQ(MSOFTUMG): This message is sent by the MSOFT to UMG.

Connect(BSSMSC): This message is sent from the BSS side to the MSC informing the MSC that the called mobile answers the call. 31. 29.MOD REQ (MSOFTUMG): This message is sent to the UMG to send the ringing tone to the calling mobile.Connect (MSCBSS): This message is sent by the MSC to the BSS informing the calling mobile that the called party is connected.CAMBODIA MTX-INS Huawei Tech. An important field in this message is the cause of the disconnection which in normal disconnecting cases . and from the signal type I know that this message is to send ring tone signaling to the called mobile. 32. I know that this message is sent to the calling mobile from the transaction flag as it indicates that the message is sent to the side that start the transaction which is BSS in case of the calling mobile. Ltd..MOD Reply (UMGMSOFT): This message is just an acknowledgment to the “MOD REQ” message.Connect ACK (BSSMSOFT): This message is sent by the BSS to the MSC to acknowledge the connect message. 27.Disconnect (BSSMSC): This message is sent by the BSS side to inform the MSC that mobile disconnects the call. 33. 35. o Second. 34. I know that this message is for the calling mobile not the called from the TID specified in this message is for the calling not the called. I know that the called mobile is the one mentioned here form two things: o First.Alert (MSCMS): This time the “Alert” message is sent from the MSC to the MS. 26. as the signal field in this message is empty. Co.Assignment complete (BSSMSC): This message is sent by the BSS side to confirm the allocation of the RF resources. 30. the user connected id in the message is for the called mobile.Connect ACK (MSCBSS): This message is sent by the MSC to the BSS to acknowledge the connect message. 28. this message is used to make the caller hearing alerting tone.MOD REQ(MSOFTUMG): This message is sent from the MSC to UMG to stop the ringing tone that is sent to the calling mobile. In this message we will find the type of the channel allocated to this connection. the transaction flag of the message indicates that the message is sent to the side that originates the transaction which is the MSC in case of the called mobile. because these tones are stored in the UMG. The ID of the mobile subscriber can be found in the user ID filed in this message. The message is sent to inform the MSC that the called mobile is now ringing. 25.Alert (MSMSC): This message is sent from the MS to the MSC side. as the MSC when requesting RF resources specifies the allowed and the preferred channel rather than specifying a certain channel.

The mobile is identified by its “User connected ID” filed in the message. 41. Note that this message is from the BSS side because the called subscriber is the one who disconnects first.. 38. Ltd. The mobile is defined by its SCCP ID.CAMBODIA MTX-INS Huawei Tech.SUB Reply(UMGMSOFT): This is a reply for the request from MSOFT to clear the UMG resources. This is to inform the MSC that the calling mobile signaling resources are now released. . 37. 40. 43. 42.Clear complete(BSSMSC): This message is sent by the BSS to confirm the release of the mobile station RF resources.Clear command(MSCBSS): This message is sent by the MSC to the BSS side to ask it to release the RF resources allocated to a mobile station.SUB REQ(MSOFTUMG): This message is sent by the MSOFT to the UMG to release the resources of UMG allocated to a certain mobile.Release complete (MSCBSS): This message is sent by the MSC to BSS to inform it that the calling mobile signaling resources are now released from its side. 39. The resource is identified in the TID field.Release complete (BSSMSC): This message is sent by the BSS to MSC to inform it that the calling mobile resources are now released from its side. 36. should be “Normal Clear”. Co. to release the traffic channel used. 44.Release (BSSMSC): This message is sent by the BSS as an acknowledgment for the Disconnect message sent by the MSC.Release (MSCBSS): This message comes as a response for the message “Disconnect”.Disconnect (MSCBSS): This message is sent by the MSC to the BSS to inform the calling mobile station the disconnecting of the call.

3: The Alert and connect messages sequence . Co. BSS 1 MSC BSS 2 Calling Called Figure no. Alert Alert Connect Connect Calling BSS1 MSC BSS2 Figure no.2: The actual situation for two mobiles in different BSS parts.CAMBODIA MTX-INS Huawei Tech.. Ltd.

CAMBODIA MTX-INS Huawei Tech. Co. Ltd. Note 1: the Alert for the calling mobile is originating form the MSC side.. this alert is sent by the UMG to the mobile through the BSS part. Note 2: the above situation is for a MS calling a MS in the same BSC and registered in the same MSC. .