Which message does the incoming call display come from? Is it a tup/ISUP message or a map message?

China Communication Network-Communication Resource Consulting Talent Training sharing»GSM & GPRS & edge»Q & A Forum»Which message does incoming call display come from?

Page:[1]

Syf

Which message does incoming call display come from? Is a tup/ISUP message or a map message? Please explain in detail ??

Lixing1

Yes map message Mo process 1. The mobile station Ms submits access requests and optional authentication requests (access request and Possible Authentication) to the visit Location Register vlr ); 2. The mobile station Ms submits a short message (Message Transfer) to MSC ); 3. MSC to the gateway SMS-G/iwmsc upload Short Message (forward1_message ); 4. The Gateway SMS-IWMSC submits a short message (Message Transfer) to SMC ); 5. SMC sends a response (ACK or error) to the gateway SMS-IWMSC ); 6. The SMS-IWMSC sends a response (ACK or error) to MSC ); 7. msc sends an ACK or error to Ms ). Mt Process 1. The SMS center SMC submits a message transfer request (Message Transfer) to the gateway SMS-G/iwmsc ); 2. The Gateway SMS-G/iwmsc sends a route (sendroutinginfoforshortmsg) to HLR to retrieve the user's imsi number from HLR; 3. The Gateway SMS-G/iwmsc sends a short message (forward1_message) to MSC ); 4. msc sends a route query (sendinfoformt-SMS) to vlr ); 5. msc sends a short message (Message Transfer) to the mobile station ms ); 6. MS sends a message transfer to MSC ); 7. msc send a report (delivery report) to SMS-G/iwmsc ); 8. SMS-G/iwmsc send a report (delivery report) to SMC ). (The above is the normal delivery process. When the user shuts down, is out of service, or the short message memory is full, the signaling will be relatively complicated .) Alert_ SC main process description 1. When the phone is started, returned to the service area, or the memory is deleted from the short message, the phone reports the short message function to vlr (rp_ms_to_network_sms_a ); 2. vlr notifies HLR that the mobile phone can receive short messages (regforsm ); 3. HLR sends a wake-up message (alert_ SC) to the gateway MSC ); 4. The Gateway sends a short message to the background and starts the MT process. [[I] This post was last edited by lixing1 at [/I]

Syf

May I hear more It seems that many short messages are described upstairs. Is there any relationship with this question ????

Vvcoco

The caller ID of the call display should be from the caller ID in the IAI (IAM) message in the Tup/ISUP. Generally, according to the existing signaling process, the called MSC can only obtain the calling number through IAI (IAM) messages, because in the map message, when HLR logs on to MSC/vlr for a dynamic roaming number msrn from the called user, in the provide roaming number message, only the called imsi number and the GT value of gmsc are allowed, the caller ID is not included. Therefore, the called MSC can only be obtained through IAI (IAM) messages. I understand it only. correct the error!

Cyxian

According to the MS called flowchart: [Img] Quit The process is described as follows: (1) Call the ISUP/Tup part of the customer through the signaling method No. 7, and the entry MSC (gmsc) receives the call from the fixed network (1sdn/PSTN. (2) gmsc asks HLR about the MSC address (msrn) accessed by the called mobile customer ). (3) HLR requests to visit vlr and allocate msrn. Msrn is allocated by visiting vlr each time a customer calls and notifies HLR. (4) After gmsc obtains msrn from HLR, it can find the path from which the route is established to the accessed MSC. (5) (6) the accessed MSC obtains customer data from vlr. (7) (8) MSC sends a paging message to the mobile station through all the base station BTS in the location zone. (9) (10) after the Mobile Station of the called mobile customer sends back the page call response message, the following operations are performed: (1), (2), (3), (4) wait until the mobile device rings the bell and send the call-through confirmation signal to the caller. (11) mobile clients receive a response and send a response connection message to the fixed network. Now, the call is in progress. As shown in the figure, the paging message should have a calling number, so I think it is a map process. [[I] This post was last edited by cyxian at,-7-24 [/I]

Vvcoco

The upstairs is right, but the paging message occurs only after the connection. Only after the IAI (IAM) message is connected to the called MSC, called MSC paging users using imsi or tmsi Based on the MSRN-IMSI table. The figure above is exactly like this! So it should be obtained on the Tup/ISUP, rather than the map message. What does the upstairs think?

Lixing1

[Quote] the original post was published by [I] Syf [/I] On It seems that many short messages are described upstairs. Is there any relationship with this question ???? [/Quote] I saw it wrong. Sorry.

Syf

Please delete useless information. Thank you. [Quote] the original post was published by [I] lixing1 [/I] On I saw it wrong. Sorry [/quote]

Syf

Please continue. Mobile Networks and fixed networks are very different. Are there many problems worth studying? I hope you can continue. Please add more points to the above.

Vvcoco

Haha, the moderator is right. The mobile network is very different from the fixed network, but for the call display, the fixed network is more likely to be map (map is the Mobile Application Part ^_^, I personally think this topic has a discussion significance. The landlord will initiate some award-winning topics. Haha, this method is very wrong, and mutual communication will be more in-depth!

Dndwxb

Fixed Network is the calling party number in IAM. the mobile network is the paging message of map. of course, in the mobile network, if the master is not in the same MSC, the inter-Bureau message is ISUP or Iam in BICC. in fact, different types of calls also affect the number displayed by the caller, such as the generic Number Parameter in connect and continewithargument in camel calls. we suggest you take a look at the relevant clip specifications.

Cyxian

Agree that for the GSM system, inter-office messages are transmitted through Tup/ISUP, but the moving part should be transmitted through map.

Vvcoco

I think the upstairs analysis is correct, but the map and bssap messages are incorrect! A map message is generally a message transmitted between MSC, and a paging message should belong to bssap. If it is under port A, even the 7 signal is no longer, it is a lap or LAPD message.

Syf

I personally think 1. It is necessary to study this problem. 2. Call to display the locreq message from the map message. Continue. Another reason may be the system. You cannot score the score yet. Please forgive me!

Syf

I think this topic is necessary for research. [Quote] original Post published by [I] vvcoco [/I] Haha, the moderator is right. The mobile network is very different from the fixed network, but for the call display, the fixed network is more likely to be map (map is the Mobile Application Part ^_^, I personally think this topic has a discussion significance. The landlord will initiate some award topics. Haha, this method is very good... [/quote]

Dndwxb

In the mobile network, it should be the setup message of bssap. You can refer to the ts123.081.

Vvcoco

Hehe, does Syf call the display parameters (functions )? In this case, it is an incorrect understanding. I thought you mentioned that the caller's number in the call display came from ~ _~. If it is a call display function, it should be a map message. During Location Updating, HLR will pass the clip parameter of the user to the registration vlr. 8 interesting, 8 interesting ^_^

Vvcoco

In addition, if the opposite party is forcibly hidden and the called party is not forcibly displayed, the mandatory hidden information of the caller should be controlled by the user Line Identification byte in the IAI or Iam messages in the ISUP/Tup. The clip stored in the called vlr only controls whether the called can display incoming calls.

Patrick_xu

In the mobile network, if the caller is from the Internet (such as CMCC, CT/Cu/CN), their caller numbers are all sent from Iam/IAI messages. If the caller is a mobile user of this website, the caller number is obtained from the vlr where the caller is located, and the map message is sent to the called MSC/vlr. In addition, a vswitch can modify the sent calling number, such as adding a local area code.

Vvcoco

Upstairs, I know about the GSM network (actually tracked signaling messages). In a specific Sri message, there is no information about the caller's address segment, and what is entered in PRI is the called imsi field, there is no calling information. The called MSC/vlr cannot get the calling number information through map? Although in CDMA networks, location request will contain the caller's Address message, it is clear that in actual applications, in order to make it easier to implement non-standard transfer of the caller's number, the caller ID is also extracted from the Tup message. I wonder if different equipment vendors have different implementation methods ?????? Haha, it seems that the moderator is right. It's really interesting to discuss. Haha! Pai_^

View the complete version: Which message does the incoming call display come from?

Powered Discuz! Archiver 4.0.02001-2005 comsenz Technology Ltd
Processed in 0.027905 second (s), 2 queries