Detailed Error Information UDTS v0.2

7/25/2019 Detailed Error Information UDTS v0.2

1/23

116 January 2016Welcome to LogicaCMG

Detailed Error InformationCR SMSC_2002_043

Sergey Marin

Consultant


2/23

216 JanuarWelcome to Lo icaCMG

Purpose

Provide finegrained error information for t!e follo"ing messageretry functions#

$ %sual SMSC retry

$ &rror 'e(endent )etry *C) SMSC+1,,-+10./

$ ntelligent retry

$ Catc!all routing *a retry via an SMPP gate"ayC) SMSC+2002+1./


3/23


What we hae !han"ed

We c!anged error codes returned in case of an unsuccessfulM4 delivery attem(t to t!e GSM PLM5

efore in (lace of errors covered 7y t!is c!ange t!e GWreturned System 8ailure to t!e 'WGSM

n (lace of t!is System 8ailure "e (rovided detailed error codes


4/23


#ow it wor$s

:n error occurs eit!er in t!e net"or; or in t!e GW

4!e GW generates an error code *eit!er from t!e e


5/23


Error !ode !lasses

4!e return causein an *4% :5S or C!ina/%'4S?@%'4S?L%'4S SCCP (ac;et

Refuse reasonin M:PA(en confirm (ac;et

Provider errorin M:P confirm (rimitives for M:P SMS

management services User errorin M:P confirm (rimitives for M:P SMS management

services *already e


6/23


M%P&'&%(ort )* and )2

4!is a7ort occurs if an error ta;es (lace on t!e M:P user level

&L) a((lication *over GSM M:P/

$:n MSC a((lication *over GSM M:P/

User reasonand diagnostic info (rovide a7ort reason andadditional information

4!e GW ma(s 7ot! t!ese values to one value t!at is for"ardedto t!e 'WGSM


7/23.16 JanuarWelcome to Lo icaCMG

M%P&P&%(ort

4!is a7ort occurs if an error ta;es (lace on t!e M:P Providerlevel

t can 7e a local SMSC M:P (rovider *t!e one t!e GW uses/or a remote M:P (rovider *on ot!er net"or; node/

Parameter Provider Reason indicates a7ort reasonBerror code

4!e GW ma(s t!e value it receives from t!e net"or; to t!e5err value t!at is for"arded to t!e 'WGSM


8/23-16 JanuarWelcome to Lo icaCMG

M%P&+pen !onfirm

8ailed M:P o(en dialogue attem(t *on M:P Provider/

)efuse reason contains t!e error code

4!e error code can indicate M:P version incom(ati7ility#

$:((lication conte


9/23,16 JanuarWelcome to Lo icaCMG

M%P&+pen !onfirm

8ailed M:P o(en dialogue attem(t *on M:P Provider/

)efuse reason contains t!e error code

4!e error code can also 7e

$ nvalid originating reference$ nvalid destination reference

$ 5o reason (rovided

4!e originating?destination reference are c!ec;ed 7y a remote

M:P (rovider 4!e M:P (rovider generates a negative confirmation if a

reference is not correct


10/23116 JanuarWelcome to Lo icaCMG

M%P&+pen !onfirm Important

f an %'4S error occurs as a result of M:P reEuest t!e GWreceives 4C5A4C&=ind

f

$ M:P dialogue not esta7lis!ed :5'

$ M:PA(en=reE sent :5'

$ 5o M:PA(en=cnf received

$ GW M:P user receives 4C5A4C&=ind

t!is 4C5A4C&=ind according to M:P S(ec must 7ema((ed to M:PA(en=cnf refuse reason B F)emote nodenot reac!a7le

So all %'4S return causes must 7e ma((ed to F)emote nodenot reac!a7le in t!is case and t!erefore lost



M%P&+pen !onfirm Important

We decided not to do t!atH

f an %'4S error occurs "!en a M:P dialogue is notesta7lis!ed yet t!e GW ma(s t!e %'4S return causeBerrorcode to a 5err value and for"ards it to t!e 'WGSM

n t!is "ay "e do not loose t!e %'4S error infoH



'D,S-.'D,S-/'D,S SCCP pa!$et

f a M:P dialogue is already esta7lis!ed t!e 4C5A4C&=indresulting from an %'4S (ac;et is ma((ed to t!e M:P5otice=ind=

4!e GW ma(s FPro7lem diagnostic (arameter of t!e M:P

5otice=ind *containing %'4S return cause/ to a 5err value 4!e GW for"ards t!e 5err value to t!e 'WGSM




Ane im(ortant e




W!y t!e e



M%P Confirm primities

Proider Error

A(tional (arameter in follo"ing confirmation (rimitives t!e GWcan receive in M4 scenarios#

$ M:PS&5')A%45G58A8A)SM=confirm

$ M:PM48A)W:)'S>A)4M&SS:G&=confirm

$ M:P)&PA)4SM'&L&)IS4:4%S=confirm ndicates (rovider errors occurred "!ile !andling a

corres(onding reEuest (rimitive

4!e error info from M:P)&PA)4SM'&L&)IS4:4%S=confirm is not for"arded to t!e 'WGSM

&



M%P Confirm primities

'ser Error

Com(ulsory (arameter in follo"ing confirmation (rimitives t!e GWcan receive in M4 scenarios#

$ M:PS&5')A%45G58A8A)SM=confirm

$ M:PM48A)W:)'S>A)4M&SS:G&=confirm

$ M:P)&PA)4SM'&L&)IS4:4%S=confirm

ndicates user errors occurred "!ile !andling a corres(onding reEuest(rimitive

4!e error info from M:P)&PA)4SM'&L&)IS4:4%S=confirm isnot for"arded to t!e 'WGSM

&



Confi"uration

Iou can ena7le?disa7le t!is functionality 7y means of an AKMattri7ute GW+CAMMA5?SS.+&))+'&4:L+&5:L&'=

Iou do not !ave to restart t!e GW= 4!e c!ange is effective fort!e ne



Confi"uration 1Important

efore t!e c!ange t!e GW (rovided t!e indication "!et!er t!eM:P confirm (rimitives (rovider errors originated from an >L)or an MSC *t!e errors itself "ere not (rovided/=

f t!e functionality is ena7led t!e GW (rovides t!e (rovidererrors !o"ever it is not (ossi7le anymore to say from "!at ;indof a net"or; node t!e error comes=

f t!e functionality is disa7led t!e GW ;ee(s t!e old 7e!aviouras descri7ed in 7ullet one=



a!$wards !ompati(ilit

4!e values of t!e ne" error codes 7et"een t!e GW and t!e'WGSM reEuire t"o 7ytes

4!e 7+status field of t!e AS used to trans(ort t!ese codes isone 7yte long

We could not c!ange t!e AS interface# it is a (atc!

4!e GW com(resses t!e t"o 7yte error codes into one 7yte

4!e 'WGSM decom(resses t!e codes 7efore it ma(s t!emagainst t!e ((l+nerr=t



,ra!in"

n t!e AS trace you "ill see t!e com(ressed codes

4!e GW traces t!e t"o 7yte *uncom(ressed/ error as an SCerror

4!e ma((ed M&)) and MS4: you can see in t!e ' trace as

usual



%dditional information

)elease note# SMSC+09+61+012 *for release 9=6/

:4P# A(tion 11c

'esign#NNnlatt(1sfs3NsysN(roOectNsmsc

NinternNteam sout!NProOect 4S SMSC aseline N0-= (roOectdelivera7lesN01= "or;ing documentsN5: M5PN'esign+%'4S+093+01+Pro(osed+3=doc

)eEuirements reEuirements analysis and c!ange reEuestdescri(tion *C) SMSC+2002+093/#

!tt(#??telecomi?teams?smsc+reE?SMSC?aseline 9=!tm
http://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://telecomi/teams/smsc_req/SMSC/Baseline%204.htmhttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.dochttp://na%20mnp/Design_UDTS_043_01_Proposed_V3.doc


23/23216 JWelcome to Lo icaCMG

5uestions

Detailed Error Information UDTS v0.2

Documents

Transcript of Detailed Error Information UDTS v0.2