SHORT MESSAGE SERVICE TERMINATING FOR GSM.docVIP

SHORT MESSAGE SERVICE TERMINATING FOR GSM Version 1.0 2001-5-15 ABSTRACT This description regarding the short message mobile terminating function needed for transferring a short message from a service center to a MS. Also there are the varied cases with the message flow. I’ll really appreciate it very much if you can point out the mistakes involved in this essay and give me some instructive advice. Functional options : HY_U_HLR attribute: F-SMS-004 ( f19 ): True: Priority Indication treatment (SRI SMS) False: Priority Indication not treatment (SRI SMS) F-SMS-001 (f28): True : Multi Service Center treatment False : Mono Service Center treatment F-SMS-006 ( f79): True : reject SRI if SMS-GMSC not in HPLMN False : do not reject SRI in above case F-SMS-008 ( f99): True : Diagnostics returned to SC with absent subscriber error False : Diagnostics not returned to SC with absent subscriber error Impact on database: In HYR_HLS: HY_ENTIN, HY_AC1_V Short Message Alert HY_ACMAX, Byte 20 Maximum phase allowed for incoming short message gateway Application Context . HY_ACMAX, Byte 24 Maximum phase allowed for incoming short message waiting data Application Context . REFERENCED DOCUMENTS [1] AAC020298500DT – Mobile Terminating point to point SMS [2] AAC030546500DT – Mobile Originating point to point SMS [3] AAC030546500DS – Mobile Originating point to point SMS [4] AAC030542500DS – Short Message Service Application Protocol (SMSAP) Network structure LINK5 LINK3 LINK2 LINK1 LINK2 LINK4 In many networks the function SC,SMS-GMSC and SMS-IWMSC are collocated in one machine called SMSC or IWF-SMS. SME (Short message entity) is an entity which may send Short messages. The SME may be located in a fixed network, an MS or an SC. The following MAP are used: 1.1 SC Refer to link1. No man