Hi everyone,
I work for mobile company and a requirement has come up, as I have given below(bit lengthy). The specification states that Open operating system platform needs to used. So need to use Linux. Anyone having a bit of time pls go through the specs below ! Can anyone tell me if Kannel can be used in this setup. If yes, How? What will be the architecture? Any help in this regard would be appreciated. Thanking you J Milton ------------------------------------------------------------------ TECHNICAL SPECIFICATIONS PART A - GENERAL 1. This Technical Specifications present the requirements of MOBILE OPERATOR for a System which is capable of sending SMS message to foreign roamers that enter MOBILE OPERATOR network as well as sending SMS to MOBILE OPERATORˇ¦s own subscriber that visit other networks abroad. PART B ˇV FUNCTIONAL REQUIREMENTS 1 Welcome SMS 1.1 Detecting Inbound Roamers 1.1.1 The system shall be able to detect an inbound roamers immediately when registering with MOBILE OPERATOR network. 1.1.2 The system shall be able to capture and deduce from the SS7 messages at least the following information ; i) Time Stamp ii) Message Type iii) MSISDN iv) IMSI v) Roamer home network /country vi) Status 1.1.3 The system shall be able to identify and categorised roamer ; i) New roamer ii) Registered roamer so that the susbsequent SMS message is not a Welcome SMS but contain other useful information. 1.1.4 The system shall have capability to bar / to enable the roamers who does not wish to receive SMS. The system shall allow the management of a black-list. Please explain the details. 1.1.5 The system shall have capability to modify list of networks who are barred from receiving welcome SMS. Please explain the details. 1.1.6 The system shall have a mechanism to avoid the multiple delivery of welcome message to the same inbound roamer. 1.1.7 The system shall be able to build a roamer profile which include at least the following; i) Frequency (first entry, regular visitor, long-time visitor, cross-border,ˇK.) ii) Duration of Stay iii) Country of origin iv) Language v) Operators, Mobile Group Networks vi) Subscriber data - Teleservices vii) Localisation (VLR information) 1.2 Messages Sending 1.2.1 The System shall provide an efficient SMS messages sending mechanism and process defined according to roamer profiles. Please provide the details. 1.2.2 The system shall provide an efficient mechanism and a user-friendly GUI interface to customize and manage the messages which include ; i) Short message editing and categorization ii) Able to catagorize messages into group with different themes (Greeting Message, Sports and event info, Weather Info etc) iii) Able to send groups of messages at regularly defined intervals. iii) Able to generate as many messages as wanted per respective operator. iv) Able to define the time parameters upon which the first SMS shall be send to the roamers. v) Able to determine the sending time (e.g no SMS between 10 pm to 9:30 am) to avoid disturbing roamer. vi) Can the IMSI that has been detected between 10 pm to 9:30 am be kept in the memory in order to send a SMS in the morning, conditioned that the roamer is still on MOBILE OPERATORˇ¦s network? vii) In case of modification of the content of a SMS, what is the time lag before it is effectively taken into account ? viii) The timing, frequency,validity and content of these messages shall be all totally configurable. ix) Roamers could receive specific message according to the spot of location when they come for the first time in MOBILE OPERATOR network. x) If the proposed system have restrictions and quantitative limits for the above (i) to (ix), please state precisely. (e.g 5 group message per operator, 100 SMS per group max, ˇK) 1.2.3 Please state the maximum number of simultineous SMS message the system can handle. 1.3 Report and Statistic The System shall be able to provide at least the following reports; 1.3.1 Daily Traffic Report Generation on Roamer Profile Information, Movement History and Duration of Stay. 1.3.2 Daily report on number of short message send to the Inbound Roamers. This report shall be generated in hourly basis. 1.3.3 Daily Audit Trail Report Any database modification shall be logged and the system shall generate the audit trail report with user ID, time stamp and event, every day-end. 1.3.4 System message/Event Log System message or system event such as any alarm detected by the system shall be logged into this log file. This files shall be rename and stored into the predefined partition and system shall create a new log file for continuous message/event logging. 2. SMS Bon Voyage 2.1 Detecting Outbound Roamers 2.1.1 The system shall be able to detect MOBILE OPERATOR Outbound roamers immediately when registering with foreign network abroad. 2.1.2 The system shall be able to capture and deduce from the SS7 messages at least the following information ; i) Time Stamp ii) Message Type iii) MSISDN iv) IMSI v) Roamer home network /country vi) Status 2.1.3 The system shall be able to identify and catagorized roamer ; i) New roamer ii) Registered roamer so that the subsequent SMS message is not a Bon Voyage SMS but contain other useful information. 2.1.4 The system shall have capability for not sending SMS message and subsequent SMS info for a roamer or a group of roamers who are not interested at all in receiving the SMS info. 2.1.5 The system shall have a mechanism to avoid the multiple delivery of SMS message to the same Outbound Roamer. 2.1.6 The System shall be able to build roamer profile which include ; i) Frequency (first entry, regular visitor, long-time visitor, cross-border,ˇK.) ii) Country of origin iii) Language iv) Operators, Mobile Group Networks v) Subscriber data e.g Teleservice vi) Localisation (VLR information) 2.2 Messages Sending 2.2.1 The System shall provide an efficient SMS messages sending mechanism and process defined according to roamer profiles. Please provide the details. 2.2.2 The system shall provide an efficient mechanism and a user-friendly interface to customize and manage the messages which include ; i) Short message editing, categorization and modification. ii) Able to catagorize messages into group with different themes (Greeting message, Event and Sport message, Weather message etc.) iii) Able to send groups of messages at regularly defined intervals. iv) Able to generate as many messages as wanted per respective operator. v) Able to define the time parameters upon which the first SMS shall be send to the roamers. vi) Able to determine the time to send SMS at flexibel hours (e.g no SMS between 10 pm to 9:30 am) to avoid disturbing roamer. vii) Can the IMSI that has been detected between 10 pm to 9:30 am be kept in the memory in order to send a SMS in the morning, conditioned that the roamer is still on MOBILE OPERATORˇ¦s network? viii) In case of modification of the content of a SMS, what is the time lag before it is effectively taken into account ? ix) The timing, frequency and content of these messages shall be all totally configurable. x) If the proposed system have restrictions and quantitative limits for the above (i) to (x), please state precisely. (e.g 5 group message per operator, 100 SMS per group max, ˇK) 2.2.3 Please state the maximum number of simultineous SMS message the system can handle. 3 Report and Statistic The System shall be able to provide at least the following reports; i) Daily Traffic Report Generation on Roamer Profile Information, Movement History ( arrival and departure by day) and Duration of Stay. ii) Daily report on number of short message send to the Outbound Roamers. This report shall be generated in hourly basis. iii) Number of roamers present in database and in the network. iv) Daily Audit Trail Report Any database modification shall be logged and the system shall generate the audit trail report with user ID, time stamp and event, every day-end. iv) System message/Event Log System message or system event such as any alarm detected by the system shall be logged into this log file. This files shall be rename and stored into the predefined partition and system shall create a new log file for continuous message/event logging. PART C - TECHNICAL REQUIREMENTS. 1 SYSTEM HARDWARE REQUIREMENTS 1.1 General 1.1.1 The System hardware shall consists of the following basic component: i) System Server ii) System console iii) SS7 Probe and communication component 1.2 System Server 1.3 SS7 Interface Unit and Data Communication Equipments 1.3.1 The Implementor shall provide the SS7 Interface Unit which shall allow the System to interface with the MSC. Please state type of MSCs the system has been successfully integrated to (e.g Nokia, Alcatel, Ericsson, etc) 1.3.1 The system shall be capable to support a traffic of i) 250K ˇV 300K Inbound Roamers ii) 100K ˇV 150K Outbound Roamers Implementor shall provide detail on the proposed dimensioning , compliance, no of links required and its expandability. 1.4 The System shall support the following network access type: i) TCP/IP ii) X.25 iii) PSTN 1.4 Interfacing with the SMSC 1.4.1 The System shall be able to interface to Logica Aldiscon Telepath 2700 using SMPP 3.4 / 3.3 protocol. Please state type of SMSCs the system has been successfully interfaced to (e.g CMG, Nokia, Sema, ADCNewnet etc. 1.4.2 The System shall support SNMP protocol for alarm management. 2.0 SYSTEM SOFTWARE REQUIREMENTS 2.1 Database System 2.1.1 The System shall be equipped with a commercial relational database management System (RDBMS) to store operational data. 2.1.2 The database shall contain at least the following group of data : i) Subscriber data ii) Billing data iii) Configuration data iv) Statistic data 2.2 System Software 2.2.1 This section specifies the System software required to operate the System. 2.2.2 The requirements stated here may not be able to cover all System software necessary to support efficient operation of the System. Thus, it is the responsibility of the Implementor to provide a complete package of software necessary to meet MOBILE OPERATOR requirements. 2.2.3 The software shall include but not limited to : iv) Operating System (OS) v) System Utilities vi) Naming Services vii) SS7 Stack 2.3 Operating System 2.3.1 The Operating System shall be an Open Operating System platform. 2.3.2 The Operating System shall support: i) Volume Shadowing or Disk Mirroring ii) RAID 5 Implementation 2.3.3 The operating System shall have the following features: i) Exploits symmetric multiprocessing architectures ii) Multi-threaded 2.3.4 The operating System shall support the following security features: i) password files inaccessible by normal users. ii) network wide integrated security administration. iii) NCSC level C2 security level. 2.4 Interconnection With The Network 2.5 Interconnection with NSS The Implementor shall ensure that the offered system shall be capable of interworking with MOBILE OPERATOR network elements as follows: i) MSC/VLR & HLR - Alcatel ii) MSC/VLR - Nokia iii) STP/SCCP ˇV Ericssons iv) SMSC ˇV Aldiscon 2.5.1 The supplied system shall connect on MOBILE OPERATORˇ¦s network as depicted in figure 1 for MOBILE OPERATORˇ¦s International Roaming Network Configuration. 2.5.2 The equipment offered shall support Mobile Application Part (MAP) protocol stack and principle that conform to GSM recommendation. 2.5.3 The system shall be able to analyses the inbound roamersˇ¦s (foreign roamers) message transactions between MOBILE OPERATORˇ¦s VLR and foreign roamerˇ¦s HLR. The Implementor must describe in detail the mode of operation. 2.5.4 The system shall be able to analyses the outbound roamersˇ¦s (MOBILE OPERATORˇ¦s roamers) message transactions between foreign network VLR and MOBILE OPERATORˇ¦s HLR . The Implementor must describe in detail the mode of the operation. 2.5.5 The system shall decode the localisation updating MAP procedures for every roamers on MOBILE OPERATOR network and MOBILE OPERATOR roamers on foreign network as such: i) Update location ii) Request Aucthentication iii) Date and time of transaction iv) Insert Subscriber data v) Cancel Location The system shall decode roamerˇ¦s identification by decoding the following MAP protocol fields: i) IMSI based on the E212I format ii) Mobile Global Title based on E214I format iii) MSISDN based on E164I format iv) VLR address based on E164I format i) HLR address based on E164I format. ii) Teleservices 2.5.6 To optimise the number of transaction, the system shall have the capability to filter the MAP transactions which related to inter MSC roamers movements. 2.5.7 The Implementor shall provide the SS7 software to allow system to communicate with the PLMN in real-time mode and in non-intrusive manner when collecting the SS7 information. 2.5.8 The SS7 software shall be fully comply with the requirements specified in this document (GSM Mobile Network Interface). The Implementor is to provide detailed information on the SS7. 2.5.9 The Implementor shall provide tools to configure at least the following SS7 entity: i) Signalling Point ii) Link and Linkset iii) Route and Routing set iv) Subsystem Number v) Global Title vi) Point Code __________________________________________________ Do You Yahoo!? NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1