You are here

About ApplicationContextName

5 posts / 0 new
Last post
saimm
About ApplicationContextName

Hi,
Who can tell me what the means ' 0 4 0 0 1 0 50 0' in:
c-capcAP-v1-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 0 50 0 }
Thanks a lot.
Mi.

Edited by: saimm on 08/08/2011 - 09:14
TomiZet
Hi, ApplicationContextName

Hi,

ApplicationContextName name is part of the larger structure Application Context. Usually it identifies protocol and protocol's version of TCAP user. Since CAPv1 operates only between gsmSSF and gsmSCF we have only one AC here. This is ASN.1 definition of taken from GSM 09.78, see the part after '::='...

CAP-v1-gsmSSF-to-gsmSCF-AC APPLICATION-CONTEXT
-- dialogue initiated by gsmSSF with InitialDP
INITIATOR CONSUMER OF {
gsmSCF-activation-ASE,
Connect-ASE
Call-handling-ASE,
BCSM-event-handling-ASE,
gsmSSF-call-processing-ASE,
Activity-test-ASE
}
::= {ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) ac(0)
cap-gsmssf-to-gsmscf(50) version1(0)};

saimm
ApplicationContextName

Oh, I know it.
The version1(0) is the CAP version?
I don't know how to ensure the version of the ApplicationContextName.
This is the ApplicationContextName in the ASN.1 file.
Please tell me how know the version of it. Because the codec part will use it.
c-capcAP-v1-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 0 50 0 }
c-capcAP-v2-assist-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 0 51 1 }
c-capcAP-v2-gsmSRF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 0 52 1 }
c-capcAP-v2-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 0 50 1 }
c-capcAP-v3-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 21 3 4 }
c-capcAP-v3-gsmSMS-AC ApplicationContextName ::= { 0 4 0 0 1 21 3 61}
c-capcAP-v4-gsmSMS-AC ApplicationContextName ::= { 0 4 0 0 1 23 3 61}
c-capcAP-v4-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 23 3 4 }
c-capcAP-v4-assist-gsmSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 23 3 6 }
c-capcAP-v4-gsmSCF-to-gsmSSF-AC ApplicationContextName ::= { 0 4 0 0 1 23 3 8 }
c-capcAP-v4-gsmSRF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 22 3 14}
c-capcAP-v4-gprsSSF-to-gsmSCF-AC ApplicationContextName ::= { 0 4 0 0 1 21 3 50}
c-capcAP-v4-gsmSCF-to-gprsSSF-AC ApplicationContextName ::= { 0 4 0 0 1 21 3 51}

TomiZet
Hi, if you check out ASN.1

Hi, if you check out ASN.1 definitions then you see the last bytes denotes the protocol version only for CAPv1 and CAPv2. I do not know why the encoding of CAPv3 ACNs is done different way - please check out info below:

CAPv1 (GSM 09.78 version 5.7.0 Release 1996):
{ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) ac(0) cap-gsmssf-to-gsmscf(50) version1(0)}

CAPv2 (GSM 09.78 version 7.1.0 Release 1998):
{ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) ac(0) cap-assist-handoff-gsmssf-to-gsmscf(51) version2(1)}
{ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) gsm-Network(1) ac(0)cap-gsmSRF-to-gsmscf(52) version2(1)}

CAPv3 (3GPP TS 29.078 V4.9.0):
id-CAP OBJECT IDENTIFIER ::= {ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) cap3(20)}
id-CAP0E OBJECT IDENTIFIER ::= {ccitt(0) identified-organization(4) etsi(0) mobileDomain(0) umts-network(1) cap3OE(21)}
id-ac OBJECT IDENTIFIER ::= {id-CAP ac(3)}
id-acE OBJECT IDENTIFIER ::= {id-CAP0E ac(3)}

-- gsmSSF/gsmSCF AC
id-ac-CAP-gsmSSF-scfGenericAC OBJECT IDENTIFIER ::= {id-acE 4}
id-ac-CAP-gsmSSF-scfAssistHandoffAC OBJECT IDENTIFIER ::= {id-acE 6}

-- gsmSRF/gsmSCF AC
id-ac-gsmSRF-gsmSCF OBJECT IDENTIFIER ::= {id-ac 14}

-- gprsSSF/gsmSCF AC
id-ac-CAP-gprsSSF-gsmSCF-AC OBJECT IDENTIFIER ::= {id-acE 50}
id-ac-CAP-gsmSCF-gprsSSF-AC OBJECT IDENTIFIER ::= {id-acE 51}

-- gprsSSF/gsmSCF or gsmSSF/gsmSCF AC
id-ac-cap3-sms-AC OBJECT IDENTIFIER ::= {id-acE 61}

saimm
Thanks a lot .

Hi TomiZet,
Thanks a lot .
I will check out the documents. And Thank you again.