SMSC example - Successful UCP submit

An Application (e.g. password validation) want to send to a mobile user. In this case its done using an SMPP application which has to identify itself. This succeeded first time, it than submit a message is send after the message is successfully stored (this is a true store and forward SMSC) a successful submission response is returned. The the core starts a delivery attempt. It was choice to be found in the HLR (meaning the mobile is reachable via the SS7 network) and then it successfully delivered to the mobile. This delivery result in the message being deleted. The delivery stops as it is indicated that there are no more messages stored. This is just one of many (millions) permutations. Use the choices on the right to make different diagrams or even different starting points (e.g. App, UCP, CIMD2, SMPP, UE, SIP, SS7 or CORE).

The generated MSG-Flow

App APP-IW CORE STORE
| | | |
+-start-UCP
Info for start-UCP
No link information between act and comp for start-UCP
| | |
|-------60-O
Info for 60-O
No link information between msg and prot for 60-O
------->| | |
|<-------60-R
Info for 60-R
No link information between msg and prot for 60-R
resultok
-------| | |
+-login-succeeded
Info for login-succeeded
No link information between act and comp for login-succeeded
| | |
|-------51-O
Info for 51-O
No link information between msg and prot for 51-O
resultok
AMsgTest SM
------->| | |
| |----submit-sm
Info for submit-sm
No link information between msg and prot for submit-sm
resultok
src_protucp
AMsgTest SM
--->| |
| | |-----store-sm
Info for store-sm
No link information between msg and prot for store-sm
resultok
src_protucp
AMsgTest SM
---->|
| | | +-msg-stored
Info for msg-stored
No link information between act and comp for msg-stored
| | |<--store-sm-resp
Info for store-sm-resp
No link information between msg and prot for store-sm-resp
resultok
src_protucp
AMsgTest SM
--|
| |<-submit-sm-resp
Info for submit-sm-resp
No link information between msg and prot for submit-sm-resp
resultok
src_protucp
AMsgTest SM
-| |
|<-------51-R
Info for 51-R
No link information between msg and prot for 51-R
resultok
src_protucp
AMsgTest SM
-------| | |
+-submit-succeeded
Info for submit-succeeded
No link information between act and comp for submit-succeeded
| | |
+-shutdown-session
Info for shutdown-session
No link information between act and comp for shutdown-session
| | |
| | +-msg-no-delivery
Info for msg-no-delivery
action msg-no-deliveryDo not deliver now, this part of the flow stopped.
section Visible actions
component CORERepresents the core of the SMSC.
|

You can and paste the above flow representation in a text file or in your favourite text editor using a monospace font. Ofcourse you will loose the context sensitive output and the links towards additional information.

Decission table

The decission table shows which decissions have been made so far and which to make. The header contains the choice number and the entity making the choice. The choices are shown from left (latest) to right (earlier) which make it handier to follow or adapts. All choices you could have choisen on a specific level are displayed. You can click on the description to make a different choice.

UCP-flows : The main start of an UCP-Application.
  #6
CORE		 #5
App		 #4
STORE		 #3
CORE		 #2
App		 #1
APP-IW
1 msg-deliver-app UCP-submit-a-sm msg-ok submit-reject UCP-submit-a-sm UCP-Auth-ok
2 msg-deliver-mob UCP-wait msg-failed submit-store UCP-wait UCP-Auth-nok
3 msg-deliver-later UCP-shutdown     UCP-shutdown  

Additional Generated Information

Below is the graphical representaion rendered using PlantUML Try it yourself online

Cannot render UML

You can the following url to refer to the graph. Or copy as to have it embeded in usable HTML code.

Be aware that changes/improvements will not be reflected in the graph.
The plain text, which can be used by some editors, is given below. Use it if you want to make edit in you favorite editor. It does not contain links as they are not supported by some editors. You can copy the text and paste it e.g. into WebSequenceDiagrams, SequenceDiagram or SwimLanes. You can also copy it for and paste it into PlantUML.