1. Universal Computer Protocol Short Messaging Service Center
UCP Server for SMSC
Universal Computer Protocol
Server for
Short Messaging Service Center
A project report
Submitted by
NETAJI RAO DUMPALA
Regd. No.:

2. Introduction ?
7333
7337
8888
555

3. Introduction Types of short messages MO – MT AO – MT MO – AT AO – AT
AO : Application Originated
MO : Mobile Originated
AT : Application Terminated
MT : Mobile Terminated

4. Position of the UCP Server
From the SMSC view, EMI is nothing but the UCP Server
EMI – External Machine Interface
ESME – External Short Message Entity
SMSC – Short Messaging Service Center
PLMN – Public Land Mobile Network

5. What UCP Server does?
The objective of the UCP server is to accept short message data from the
ESME (External Short Message Entity) and forward it to SMSC and vice versa.
To an ESME, the UCP server has to provide access to the SMSC functions like
Submission of Short Messages
Reception of Short Messages
Reception of Notifications related to submitted Short Messages
Operate on submitted Short Messages: query, delete and modify.

6. UCP packet structure
stx <header> / <data> / <checksum> etx
E.g.: stx03/00107/O/51/ /12345/55555/1/ //
0100////////////3// D /////////////99etx
Here stx = 02(hex) and etx = 03(hex).
As separator between header and data, between data and checksum,
as well as between parameters, a “/” (2F(hex)) is used.

7. UCP packet structure Header: Data: Checksum:
TRN : Transaction Reference Number
LEN : Length of the packet
O/R : Operation or Response
OT : Operation Type
Data:
The <data> fields depend on the Operation Type
Checksum:
The <checksum> is derived by the addition of all bytes of the header,
data field separators and data fields
E.g.: stx03/00107/O/51/ /12345/55555/1/ //
0100////////////3// D /////////////99etx

8. List of UCP operations Operation Type Initiated By Command Name 60 SMT
Session management 61
List management 51
Submit SM 52
SMSC
Deliver SM 53
Deliver notification 54
Modify message 55
Inquiry message 56
Delete message 57
Response to Inquiry 58
Response to Delete 31
Alert Operation

9. Data Flow Diagram

10. The Modules The modules in the UCP server are UCP decoder
UCP operation handler
UCP response handler
AT (Application Terminated) message handler
UCP encoder

11. Testing Unit Testing Sample Test Records: ModuleName / ID
Preparation/ Settings/Special Conditions For Carrying Out The Test
Test Condition/
Input Data
Results/ Output
checksum
Using ^B (ASCII 02) as STX and ^E (ASCII 05) as ETX. Because ^C (real ETX) cannot be given as input.
^B18/00113/O/51/012345/
09876//1/ /
4/0539////// //////3// 4D
/////////////CD^E
Valid Checksum.
-do-
/////////////CE^E
Invalid Checksum.

12. Testing System Testing Sample Test cases: Module Name / ID S. No
Preparation/ Settings/ Special Conditions For Carrying Out The Test Case
Test Condition/
Input Data
Expected Results
UCP Server 1
SMSC is running. Client connected to specified IP address and port.
Send OP60 (bind) UCP packet with valid systemid (OAdC), password and subtype(1).
Client gets positive acknowledgement (ACK). The Client binds successfully. 2
-do-
Send OP60 packet with invalid systemid (OAdC) or password.
Client gets negative acknowledgement (NACK) with error code “07” (AUTHENTICATION FAILURE)

13. Conclusions
To allow applications to send and receive large number of short messages, an interface is needed to communicate with the SMSC.
The UCP server acts as the interface between application and the SMSC. The UCP server uses Universal Computer Protocol (UCP).
Applications like SMS gateway that follow UCP can communicate with the SMSC through the UCP server.

14. Future enhancements The following enhancements can be done in future
List operation (OP61)
Change password in OP60
Legacy operations (OP 01, 02, 03, 30)
Services limited by the SMSC

15. Thank You.