This is the javadoc for the APIs supported by resource adaptor cgin-unified-ra, comprising first a table of packages and then a description of what's supported per protocol. 
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Extensions of class
No extensions of this class are defined.
Here's a table of contents to the protocol descriptions.
Here are the same protocols laid out to show their relationships.
Solid arrows represent inheritance of operations, while dashed arrows represent inclusion of operations. Operations of a sub-protocol share the same event types as inherited operations of the same names. This allows a service implemented in terms of a super-protocol to handle operations of any sub-protocol. The service can view those operations as being of a particular sub-protocol where necessary via the use of casts. The MAP APIs are shown as being included into the CAP APIs so that the operations of MAP can be used on CAP dialogues.
Overview of API for protocol callcontrol
This section summarises what's supported by the API for protocol callcontrol.
Compliance of callcontrol API to specification
This callcontrol pseudo-protocol is an abstraction from the INAP and CAP real-protocols, to allow services to be built independently of particular versions of INAP and CAP. Its ASN.1 specification is OpenCloud's abstraction from those of INAP and CAP protocols.
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.callcontrol.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of callcontrol API as extension of super-protocol
Classes of extensions in callcontrol
There are no classes of extensions in this protocol.
Coverage of OCTET STRING types in callcontrol
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
CCAChBillingChargingCharacteristics |
Varies between networks and/or operators | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
Signal |
ITU-T Q.931 (05/98) §4.5.28 p99 | ||
|
CCApplyChargingReportArg |
Varies between networks and/or operators | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
BearerCapability |
ITU-T Q.931 (05/98) §4.5.5 p58 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p22 | ||
|
CallingPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CallingPartysCategory |
ITU-T Q.763 (12/1999) §3.11 p25 | ||
|
Cause |
ITU-T Q.763 (12/1999) §3.12 p26, ITU-T Q.850 (05/98) §2.1 p1, and 3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.11 pp368-373 | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericNumber |
Ignore this row: all uses of CorrelationID are specified separately | ||
|
DateAndTime |
ETSI TS 300 374-1 September 1994 §6.3 p46 | ||
|
GenericDigits |
Ignore this row: all uses of Digits are specified separately | ||
|
GenericDigits |
CGIN internal use only; never sent to the network | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
CCFurnishChargingInformationArg.FCIBCCcs1 |
Varies between networks and/or operators | ||
|
HighLayerCompatibility |
ITU-T Q.931 (05/98) §4.5.17 p78 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CCIPSSPCapabilities |
Varies between networks and/or operators | ||
|
LegType |
Common knowledge from the grapevine | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
CCMessageID.Text.Attributes |
Varies between networks and/or operators | ||
|
OriginalCalledNumber |
ITU-T Q.763 (12/1999) §3.39 p45 | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
RedirectingPartyNumber |
ITU-T Q.763 (12/1999) §3.44 p49 | ||
|
RedirectionInformation |
ITU-T Q.763 (12/1999) §3.45 p49 | ||
|
CCScfID |
Varies between networks and/or operators | ||
|
CCSCIBillingChargingCharacteristics |
Varies between networks and/or operators | ||
|
YearMonthDay |
Comment in ASN.1 module Core-INAP-CS1-DataTypes | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
PriceInHundredthsOfUnits |
Comment in ASN.1 module CAP-datatypes | ||
|
HourMinute |
Comment in ASN.1 module Core-INAP-CS1-DataTypes |
Overview of API for protocol etsi_inap_cs1
This section summarises what's supported by the API for protocol etsi_inap_cs1.
Compliance of etsi_inap_cs1 API to specification
This API conforms to ETSI INAP CS1 (ETS 300 374-1: September 1994).
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.etsi_inap_cs1.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of etsi_inap_cs1 API as extension of super-protocol
Classes of extensions in etsi_inap_cs1
Extensions of class CS1EXTENSION in etsi_inap_cs1
No extensions of this class are defined.
Coverage of OCTET STRING types in etsi_inap_cs1
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
CCAChBillingChargingCharacteristics |
Varies between networks and/or operators | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
Signal |
ITU-T Q.931 (05/98) §4.5.28 p99 | ||
|
CCApplyChargingReportArg |
Varies between networks and/or operators | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
BearerCapability |
ITU-T Q.931 (05/98) §4.5.5 p58 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p22 | ||
|
CallingPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CallingPartysCategory |
ITU-T Q.763 (12/1999) §3.11 p25 | ||
|
Cause |
ITU-T Q.763 (12/1999) §3.12 p26, ITU-T Q.850 (05/98) §2.1 p1, and 3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.11 pp368-373 | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
GenericDigits |
Ignore this row: all uses of CorrelationID are specified separately | ||
|
DateAndTime |
ETSI TS 300 374-1 September 1994 §6.3 p46 | ||
|
GenericNumber |
Ignore this row: all uses of Digits are specified separately | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
CS1EventSpecificInformationCharging |
Varies between networks and/or operators | ||
|
CS1EventTypeCharging |
Varies between networks and/or operators | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
ForwardCallIndicators |
ITU-T Q.763 (12/1999) §3.23 p32 | ||
|
CCFurnishChargingInformationArg.FCIBCCcs1 |
Varies between networks and/or operators | ||
|
HighLayerCompatibility |
ITU-T Q.931 (05/98) §4.5.17 p78 | ||
|
CS1IPAvailable |
Varies between networks and/or operators | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CCIPSSPCapabilities |
Varies between networks and/or operators | ||
|
LegType |
Common knowledge from the grapevine | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
CCMessageID.Text.Attributes |
Varies between networks and/or operators | ||
|
OriginalCalledNumber |
ITU-T Q.763 (12/1999) §3.39 p45 | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
RedirectingPartyNumber |
ITU-T Q.763 (12/1999) §3.44 p49 | ||
|
RedirectionInformation |
ITU-T Q.763 (12/1999) §3.45 p49 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
byte[] |
Varies between networks and/or operators (ITU-T Q.1214 (10/95) §6.4.4.1 p236) | ||
|
CCScfID |
Varies between networks and/or operators | ||
|
CCSCIBillingChargingCharacteristics |
Varies between networks and/or operators | ||
|
CS1ServiceInteractionIndicators |
Varies between networks and/or operators | ||
|
CS1SFBillingChargingCharacteristics |
Varies between networks and/or operators | ||
|
YearMonthDay |
Comment in ASN.1 module Core-INAP-CS1-DataTypes | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
PriceInHundredthsOfUnits |
Comment in ASN.1 module CAP-datatypes | ||
|
HourMinute |
Comment in ASN.1 module Core-INAP-CS1-DataTypes |
Overview of API for protocol map
This section summarises what's supported by the API for protocol map.
Compliance of map API to specification
This API conforms to Mobile Application Part (MAP) (3GPP TS 29.002 v10.0.0 Release 10).
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.map.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of map API as extension of super-protocol
Classes of extensions in map
Extensions of class MAPMAP_EXTENSION in map
No extensions of this class are defined.
Coverage of OCTET STRING types in map
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
byte[] |
3GPP TS 23.032 | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
byte[] |
Implementation specific | ||
|
byte[] |
Comment in ASN.1 module MAP-CommonDataTypes | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
AccessPointName |
3GPP TS 23.003 V10.0.0 (2010-12) §9 pp30-32 | ||
|
AccessPointNameOperatorId |
3GPP TS 23.003 V10.0.0 (2010-12) §9 p31 | ||
|
byte[] |
Comment in ASN.1 module MAP-LCS-DataTypes | ||
|
byte[] |
Comment in ASN.1 module MAP-CommonDataTypes | ||
|
byte[] |
Byte array | ||
|
byte[] |
Byte array | ||
|
byte[] |
3GPP TS 22.002 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
Comment in ASN.1 module MAP-CH-DataTypes-Rel5 | ||
|
Treatment |
Comment in ASN.1 module MAP-CH-DataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p395 | ||
|
byte[] |
Byte array | ||
|
byte[] |
Byte array | ||
|
byte[] |
ITU-T Rec Q.763 | ||
|
byte[] |
ITU-T Rec Q.763 | ||
|
CellGlobalId |
3GPP TS 23-003 V10.0.0 (2010-12) §4.3.1 p23 | ||
|
byte[] |
GSM 08.08 | ||
|
byte[] |
3GPP TS 32.215 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
Byte array | ||
|
Cksn  |
3GPP TS 24.008 V10.1.0 (2010-12) §10.5.1.2 p382 | ||
|
byte[] |
GSM 08.08 | ||
|
byte[] |
3GPP TS 26.103 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
3GPP TS 23.107 | ||
|
byte[] |
Comment in ASN.1 module MAP-MS-DataTypes-ph1 | ||
|
byte[] |
ITU-T Rec Q.763 | ||
|
CUGInterLockCode |
ITU-T Q.763 (12/1999) §3.15 p28 | ||
|
byte[] |
Comment in ASN.1 module MAP-SS-DataTypes-ph1 | ||
|
byte[] |
IETF RFC 3588 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
Subclass of BearerServiceCode | ||
|
ExtForwOptions |
Comment in ASN.1 module MAP-MS-DataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p369 | ||
|
byte[] |
3GPP TS 23.032 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 and 24.008 | ||
|
byte[] |
Subclass of SS-Status | ||
|
byte[] |
Subclass of TeleserviceCode | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
ForwardingOptions |
Comment in ASN.1 module MAP-SS-DataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) §17.7.4 p402 | ||
|
byte[] |
No spec! | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
byte[] |
Q.763 | ||
|
byte[] |
3GPP TS 22.032 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
3GPP TS 49.031 | ||
|
CellGlobalId |
3GPP TS 23-003 V10.0.0 (2010-12) §4.3.1 p23 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 43.068/43.069 | ||
|
GSNAddress |
3GPP TS 23.003 V10.0.0 (2010-12) §5.1 pp25-26 | ||
|
byte[] |
GSM 08.08 | ||
|
IMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-12) §2.2 p14 | ||
|
byte[] |
3GPP TS 23.032 | ||
|
byte[] |
Byte array | ||
|
MAPCheckIMEI_v1ArgSeq |
3GPP TS 23.003 V10.0.0 (2010-12) §6.2 p26-27 | ||
|
IMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-09) §2.2 p14 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
Comment in ASN.1 module MAP-MS-DataTypes | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
ISDNSubaddress |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p420 | ||
|
byte[] |
No spec! | ||
|
byte[] |
Byte array | ||
|
byte[] |
Authentication key | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
LocationAreaId |
3GPP TS 24.008 V10.1.0 (2010-12) §10.5.1.3 p383 | ||
|
byte[] |
Comment in ASN.1 module MAP-LCS-Datatypes | ||
|
byte[] |
No spec! | ||
|
byte[] |
Subclass of USSDString | ||
|
LMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-12) §2.5 p15 | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.118 | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
byte[] |
3GPP TS 23.003/43.068/43.069 | ||
|
byte[] |
No spec! | ||
|
byte[] |
3GPP TS 48.008 | ||
|
LocalisedServiceAreaId |
3GPP TS 23.003 V10.0.0 (2010-12) §11 pp36-37 | ||
|
MMCode |
Comments in ASN.1 module MAP-MS-DataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p378 | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
byte[] |
ANSI T1.113.3 | ||
|
byte[] |
Subclass of USSDString | ||
|
byte[] |
3GPP TS 29.274 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
Comment in ASN.1 module MAP-CommonDataTypes | ||
|
byte[] |
3GPP TS 49.031 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 48.008 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
Byte array | ||
|
byte[] |
Subclass of USSDString | ||
|
byte[] |
Comment in ASN.1 module MAP-MS-DataTypes | ||
|
byte[] |
No spec! | ||
|
byte[] |
3GPP TS 48.008 | ||
|
MAPSendAuthenticationInfoArgSeq |
3GPP TS 23.003 V10.0.0 (2010-09) §2.2 p14 | ||
|
byte[] |
Ignore this row: all uses of SignalInfo are specified separately | ||
|
SMSTPDU |
3GPP TS 23.040 V9.0.0 (2009-06) | ||
|
byte[] |
3GPP TS 23.040 | ||
|
SMSTPDU |
Ignore this row: all uses of SM-RP-UI are specified separately | ||
|
byte[] |
Byte array | ||
|
SSCode |
3GPP TS 29.002 V10.0.0 (2010-09) pp405-407 | ||
|
byte[] |
3GPP TS 23.011 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 22.003 | ||
|
byte[] |
IETF RFC 3588 | ||
|
MAPSendIdentificationArgSeq |
No spec! | ||
|
byte[] |
No spec! | ||
|
byte[] |
No spec! | ||
|
byte[] |
No spec! | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
Comment in ASN.1 module MAP-SS-DataTypes-ph1 from GSM 09.02 version 3.11.0 (April 1995) p460 | ||
|
byte[] |
3GPP TS 23.038 | ||
|
byte[] |
3GPP TS 23.038 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
3GPP TS 25.413 | ||
|
byte[] |
ETS 300 356 | ||
|
byte[] |
ETS 300 356 | ||
|
byte[] |
3GPP TS 23.032 | ||
|
byte[] |
3GPP TS 23.032 | ||
|
byte[] |
No spec! | ||
|
byte[] |
Comment in ASN.1 module MAP-GR-DataTypes | ||
|
byte[] |
Byte array | ||
|
byte[] |
3GPP TS 23.003 |
Overview of API for protocol cap_v1
This section summarises what's supported by the API for protocol cap_v1.
Compliance of cap_v1 API to specification
This API conforms to CAMEL Application Part (CAP) v.1 (ETSI TS 101 046 / GSM 09.78 V5.7.0 Release 1996).
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.cap_v1.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of cap_v1 API as extension of super-protocol
public interface
CAP1Dialog extends CCDialog
Classes of extensions in cap_v1
Extensions of class CAP1EXTENSION in cap_v1
No extensions of this class are defined.
Extensions of class MAPMAP_EXTENSION in cap_v1
No extensions of this class are defined.
Coverage of OCTET STRING types in cap_v1
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
BearerCapability |
ITU-T Q.931 (05/98) §4.5.5 p58 | ||
|
CalledPartyBCDNumber |
3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.7 p363 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p22 | ||
|
CallingPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CallingPartysCategory |
ITU-T Q.763 (12/1999) §3.11 p25 | ||
|
byte[] |
Byte array | ||
|
Cause |
ITU-T Q.763 (12/1999) §3.12 p26, ITU-T Q.850 (05/98) §2.1 p1, and 3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.11 pp368-373 | ||
|
CellGlobalId |
3GPP TS 23-003 V10.0.0 (2010-12) §4.3.1 p23 | ||
|
byte[] |
Subclass of BearerServiceCode | ||
|
byte[] |
Subclass of TeleserviceCode | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
byte[] |
Q.763 | ||
|
byte[] |
3GPP TS 22.032 | ||
|
HighLayerCompatibility |
ITU-T Q.931 (05/98) §4.5.17 p78 | ||
|
IMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-09) §2.2 p14 | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
LocationAreaId |
3GPP TS 24.008 V10.1.0 (2010-12) §10.5.1.3 p383 | ||
|
LegType |
Common knowledge from the grapevine | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.118 | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
LocalisedServiceAreaId |
3GPP TS 23.003 V10.0.0 (2010-12) §11 pp36-37 | ||
|
OriginalCalledNumber |
ITU-T Q.763 (12/1999) §3.39 p45 | ||
|
RedirectingPartyNumber |
ITU-T Q.763 (12/1999) §3.44 p49 | ||
|
RedirectionInformation |
ITU-T Q.763 (12/1999) §3.45 p49 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 |
Overview of API for protocol cap_v2
This section summarises what's supported by the API for protocol cap_v2.
Compliance of cap_v2 API to specification
This API conforms to CAMEL Application Part (CAP) v.2 (ETSI TS 101 046 / GSM 09.78 V7.1.0 Release 1998).
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.cap_v2.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of cap_v2 API as extension of super-protocol
public interface
CAP2Dialog extends CAP1Dialog
Classes of extensions in cap_v2
Extensions of class CAP2EXTENSION in cap_v2
No extensions of this class are defined.
Extensions of class MAPMAP_EXTENSION in cap_v2
No extensions of this class are defined.
Coverage of OCTET STRING types in cap_v2
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
CAP2AChBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
Signal |
ITU-T Q.931 (05/98) §4.5.28 p99 | ||
|
CAP2ApplyChargingReportArg |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
BearerCapability |
ITU-T Q.931 (05/98) §4.5.5 p58 | ||
|
CalledPartyBCDNumber |
3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.7 p363 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p22 | ||
|
CallingPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CallingPartysCategory |
ITU-T Q.763 (12/1999) §3.11 p25 | ||
|
byte[] |
Byte array | ||
|
byte[] |
Varies between networks and/or operators | ||
|
CAPIPSSPCapabilities |
Comment in ASN.1 module CAP-datatypes | ||
|
Cause |
ITU-T Q.763 (12/1999) §3.12 p26, ITU-T Q.850 (05/98) §2.1 p1, and 3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.11 pp368-373 | ||
|
CellGlobalId |
3GPP TS 23-003 V10.0.0 (2010-12) §4.3.1 p23 | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericDigits |
Ignore this row: all uses of CorrelationID are specified separately | ||
|
DateAndTime |
ETSI TS 300 374-1 September 1994 §6.3 p46 | ||
|
GenericDigits |
Ignore this row: all uses of Digits are specified separately | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
byte[] |
Subclass of BearerServiceCode | ||
|
byte[] |
Subclass of TeleserviceCode | ||
|
CAP2FurnishChargingInformationArg.FCIBCCcs1 |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
byte[] |
Q.763 | ||
|
byte[] |
3GPP TS 22.032 | ||
|
HighLayerCompatibility |
ITU-T Q.931 (05/98) §4.5.17 p78 | ||
|
IMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-09) §2.2 p14 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p24 | ||
|
CAP2IPSSPCapabilities |
ASN.1 CONTAINING clause | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
LocationAreaId |
3GPP TS 24.008 V10.1.0 (2010-12) §10.5.1.3 p383 | ||
|
LegType |
Common knowledge from the grapevine | ||
|
LegType |
Common knowledge from the grapevine | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.118 | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
LocalisedServiceAreaId |
3GPP TS 23.003 V10.0.0 (2010-12) §11 pp36-37 | ||
|
CCMessageID.Text.Attributes |
Varies between networks and/or operators | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
byte[] |
ANSI T1.113.3 | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
OriginalCalledNumber |
ITU-T Q.763 (12/1999) §3.39 p45 | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
RedirectingPartyNumber |
ITU-T Q.763 (12/1999) §3.44 p49 | ||
|
RedirectionInformation |
ITU-T Q.763 (12/1999) §3.45 p49 | ||
|
CCScfID |
Varies between networks and/or operators | ||
|
CAP2SCIBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
TimeAndTimezone |
3GPP TS 23.040 V9.0.0 (2009-06) §9.2.3.11 pp67-68 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
YearMonthDay |
Comment in ASN.1 module Core-INAP-CS1-DataTypes | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
PriceInHundredthsOfUnits |
Comment in ASN.1 module CAP-datatypes | ||
|
HourMinute |
Comment in ASN.1 module Core-INAP-CS1-DataTypes |
Overview of API for protocol cap_v3
This section summarises what's supported by the API for protocol cap_v3.
Compliance of cap_v3 API to specification
This API conforms to CAMEL Application Part (CAP) v.3 (3GPP TS 29.078 V4.8.0 Release 4).
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.cap_v3.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of cap_v3 API as extension of super-protocol
public interface
CAP3Dialog extends CAP2Dialog
Classes of extensions in cap_v3
Extensions of class MAPMAP_EXTENSION in cap_v3
No extensions of this class are defined.
Extensions of class CAP3EXTENSION in cap_v3
No extensions of this class are defined.
Coverage of OCTET STRING types in cap_v3
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
AccessPointName |
3GPP TS 23.003 V8.5.0 (2009-06) §9 pp28-30 | ||
|
CAP2AChBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
Signal |
ITU-T Q.931 (05/98) §4.5.28 p99 | ||
|
CAP2ApplyChargingReportArg |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
BearerCapability |
ITU-T Q.931 (05/98) §4.5.5 p58 | ||
|
CalledPartyBCDNumber |
3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.7 p363 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p22 | ||
|
CallingPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p24 | ||
|
CallingPartysCategory |
ITU-T Q.763 (12/1999) §3.11 p25 | ||
|
byte[] |
Byte array | ||
|
byte[] |
Varies between networks and/or operators | ||
|
byte[] |
Varies between networks and/or operators | ||
|
byte[] |
Varies between networks and/or operators | ||
|
CAPIPSSPCapabilities |
Comment in ASN.1 module CAP-datatypes | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
Cause |
ITU-T Q.763 (12/1999) §3.12 p26, ITU-T Q.850 (05/98) §2.1 p1, and 3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.11 pp368-373 | ||
|
CellGlobalId |
3GPP TS 23-003 V10.0.0 (2010-12) §4.3.1 p23 | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericNumber |
Ignore this row: all uses of CorrelationID are specified separately | ||
|
CUGInterLockCode |
ITU-T Q.763 (12/1999) §3.15 p28 | ||
|
DateAndTime |
ETSI TS 300 374-1 September 1994 §6.3 p46 | ||
|
GenericDigits |
Ignore this row: all uses of Digits are specified separately | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
byte[] |
Subclass of BearerServiceCode | ||
|
byte[] |
3GPP TS 29.060 and 24.008 | ||
|
byte[] |
Subclass of TeleserviceCode | ||
|
CAP2FurnishChargingInformationArg.FCIBCCcs1 |
ASN.1 CONTAINING clause | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
CallingPartyRestriction |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
CAP3FurnishChargingInformationGPRSArg |
ASN.1 CONTAINING clause | ||
|
CAP3FurnishChargingInformationSMSArg |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
byte[] |
Q.763 | ||
|
byte[] |
3GPP TS 22.032 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
Comment in ASN.1 module CAP-datatypes | ||
|
GSNAddress |
3GPP TS 23.003 V10.0.0 (2010-12) §5.1 pp25-26 | ||
|
HighLayerCompatibility |
ITU-T Q.931 (05/98) §4.5.17 p78 | ||
|
IMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-09) §2.2 p14 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p22 | ||
|
CAP2IPSSPCapabilities |
ASN.1 CONTAINING clause | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
LocationAreaId |
3GPP TS 24.008 V10.1.0 (2010-12) §10.5.1.3 p383 | ||
|
LegType |
Common knowledge from the grapevine | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.002; superclass of CellGlobalId | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
LocalisedServiceAreaId |
3GPP TS 23.003 V10.0.0 (2010-12) §11 pp36-37 | ||
|
CCMessageID.Text.Attributes |
Varies between networks and/or operators | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
OriginalCalledNumber |
ITU-T Q.763 (12/1999) §3.39 p45 | ||
|
byte[] |
Comment in ASN.1 module CAP-datatypes | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 29.060 and 29.078 | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
RedirectingPartyNumber |
ITU-T Q.763 (12/1999) §3.44 p49 | ||
|
RedirectionInformation |
ITU-T Q.763 (12/1999) §3.45 p49 | ||
|
RPCause |
3GPP TS 24.011 V8.2.0 (2009-06) §8.2.5.4 pp39-41 | ||
|
CCScfID |
Varies between networks and/or operators | ||
|
CAP2SCIBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
CAP3SCIGPRSBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
byte[] |
Comment in ASN.1 module CAP-datatypes | ||
|
TimeAndTimezone |
3GPP TS 23.040 V9.0.0 (2009-06) §9.2.3.11 pp67-68 | ||
|
byte[] |
3GPP TS 23.040 and 23.038 | ||
|
SMSProtocolId |
3GPP TS 23.040 V9.0.0 (2009-06) §9.2.3.9 pp65-67 | ||
|
byte[] |
3GPP TS 23.040 | ||
|
byte[] |
3GPP TS 23.040 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
YearMonthDay |
Comment in ASN.1 module Core-INAP-CS1-DataTypes | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
PriceInHundredthsOfUnits |
Comment in ASN.1 module CAP-datatypes | ||
|
HourMinute |
Comment in ASN.1 module Core-INAP-CS1-DataTypes |
Overview of API for protocol cap_v4
This section summarises what's supported by the API for protocol cap_v4.
Compliance of cap_v4 API to specification
This API conforms to CAMEL Application Part (CAP) v.4 (3GPP TS 29.078 V9.1.1 Release 9).
The API is auto-generated from a combination of the protocol's ASN.1 specification
and a file of adaptation requests that allows the generated API to be customized.
Essentially, all application contexts and associated types that are defined in the ASN.1 specification
are supported - see com.opencloud.slee.resources.cgin.cap_v4.metadata for details.
The ASN.1 might not specify which extensions are supported,
nor does it define the structure of information represented in OCTET STRINGs.
Questions about these aspects can be answered by referring to the tables below.
Implementation of cap_v4 API as extension of super-protocol
public interface
CAP4Dialog extends CAP3Dialog
Classes of extensions in cap_v4
Extensions of class MAPMAP_EXTENSION in cap_v4
No extensions of this class are defined.
Extensions of class CAP4EXTENSION in cap_v4
No extensions of this class are defined.
Coverage of OCTET STRING types in cap_v4
All OCTET STRING types have a byte[] representation. If an OCTET STRING type is used in a context where a DataObject is required, then the byte[] is wrapped in an ExtendibleOctetString. If the getter and setter for an OCTET STRING deal directly with that byte[] or ExtendibleOctetString, then the information within the array must be decoded and encoded by code in the service. Otherwise, the getter and setter for an OCTET STRING deal with a type that provides methods to ease that decoding and encoding of information in the array for convenience. Note that these do not have to be used - for example, the byte[] representation can still be got using one of getEncodedForm() or getByteArray() and then decoded in service code.
The following table summarises the representations used for OCTET STRING types, noting whether a convenience API is yet to be defined and where the information content is specified.
| Name of ASN.1 def'n having OCTET STRING type | Generated Java API | Specification notes | ||
|---|---|---|---|---|
|
CAP2AChBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
Signal |
ITU-T Q.931 (05/98) §4.5.28 p99 | ||
|
CAP2ApplyChargingReportArg |
ASN.1 CONTAINING clause | ||
|
GenericNumberWithB |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumberWithB |
ITU-T Q.763 (12/1999) §3.26 p35 extended with character B encoded as 0xB | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
BearerCapability |
ITU-T Q.931 (05/98) §4.5.5 p58 | ||
|
CalledPartyBCDNumber |
3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.7 p363 and 3GPP TS 23.040 V9.0.0 (2009-06) §9.1.2.5 p48 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p22 | ||
|
CallingPartyNumber |
ITU-T Q.763 (12/1999) §3.9 p24 | ||
|
CallingPartysCategory |
ITU-T Q.763 (12/1999) §3.11 p25 | ||
|
byte[] |
Byte array | ||
|
byte[] |
Varies between networks and/or operators | ||
|
byte[] |
Varies between networks and/or operators | ||
|
CAPIPSSPCapabilities |
Comment in ASN.1 module CAP-datatypes | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
Cause |
ITU-T Q.763 (12/1999) §3.12 p26, ITU-T Q.850 (05/98) §2.1 p1, and 3GPP TS 24.008 V4.17.0 (2007-09) §10.5.4.11 pp368-373 | ||
|
CellGlobalId |
3GPP TS 23-003 V10.0.0 (2010-12) §4.3.1 p23 | ||
|
byte[] |
ITU-T Q.763 | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
GenericNumberWithB |
Ignore this row: all uses of CorrelationID are specified separately | ||
|
CUGInterLockCode |
ITU-T Q.763 (12/1999) §3.15 p28 | ||
|
DateAndTime |
ETSI TS 300 374-1 September 1994 §6.3 p46 | ||
|
GenericDigits |
Ignore this row: all uses of Digits are specified separately | ||
|
GenericNumberWithB |
ITU-T Q.763 (12/1999) §3.26 p35 extended with character B encoded as 0xB | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
GenericDigitsWithStarHash |
ITU-T Q.763 (12/1999) §3.24 p33 extended with characters * and # encoded as 0xB and 0xC respectively | ||
|
GenericDigitsWithStarHash |
ITU-T Q.763 (12/1999) §3.24 p33 extended with characters * and # encoded as 0xB and 0xC respectively | ||
|
GenericDigitsWithStarHash |
ITU-T Q.763 (12/1999) §3.24 p33 extended with characters * and # encoded as 0xB and 0xC respectively | ||
|
GenericDigitsWithStarHash |
ITU-T Q.763 (12/1999) §3.24 p33 extended with characters * and # encoded as 0xB and 0xC respectively | ||
|
byte[] |
Subclass of BearerServiceCode | ||
|
byte[] |
Subclass of TeleserviceCode | ||
|
CAP2FurnishChargingInformationArg.FCIBCCcs1 |
ASN.1 CONTAINING clause | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
CallingPartyRestriction |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
CAP3FurnishChargingInformationSMSArg |
ASN.1 CONTAINING clause | ||
|
GenericNumber |
ITU-T Q.763 (12/1999) §3.26 p35 | ||
|
byte[] |
Q.763 | ||
|
byte[] |
3GPP TS 22.032 | ||
|
HighLayerCompatibility |
ITU-T Q.931 (05/98) §4.5.17 p78 | ||
|
IMEIAddress |
3GPP TS 23.003 V10.0.0 (2010-12) §6.2 p26-27 | ||
|
IMSIAddress |
3GPP TS 23.003 V10.0.0 (2010-09) §2.2 p14 | ||
|
CalledPartyNumber |
ITU-T Q.763 (12/1999) §3.10 p22 | ||
|
CAP2IPSSPCapabilities |
ASN.1 CONTAINING clause | ||
|
AddressString |
Comment in ASN.1 module MAP-CommonDataTypes in 3GPP TS 29.002 V10.0.0 (2010-09) p419 | ||
|
LocationAreaId |
3GPP TS 24.008 V10.1.0 (2010-12) §10.5.1.3 p383 | ||
|
LegType |
Common knowledge from the grapevine | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.118 | ||
|
byte[] |
3GPP TS 29.002; superclass of CellGlobalId | ||
|
LocationNumber |
ITU-T Q.763 (12/1999) §3.30 p39 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
LocalisedServiceAreaId |
3GPP TS 23.003 V10.0.0 (2010-12) §11 pp36-37 | ||
|
CCMessageID.Text.Attributes |
Varies between networks and/or operators | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressDelimiter |
Comment in ASN.1 module CAP-datatypes | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.008 | ||
|
byte[] |
3GPP TS 24.011 | ||
|
byte[] |
ANSI ISUP T1.113 | ||
|
OriginalCalledNumber |
ITU-T Q.763 (12/1999) §3.39 p45 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
GenericDigitsWithStarHash |
ITU-T Q.763 (12/1999) §3.24 p33 extended with characters * and # encoded as 0xB and 0xC respectively | ||
|
RedirectingPartyNumber |
ITU-T Q.763 (12/1999) §3.44 p49 | ||
|
RedirectionInformation |
ITU-T Q.763 (12/1999) §3.45 p49 | ||
|
RPCause |
3GPP TS 24.011 V8.2.0 (2009-06) §8.2.5.4 pp39-41 | ||
|
CCScfID |
Varies between networks and/or operators | ||
|
CAP2SCIBillingChargingCharacteristics |
ASN.1 CONTAINING clause | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
Treatment |
Comment in ASN.1 module CAP-datatypes | ||
|
AddressString |
Comment in ASN.1 module CAP-datatypes | ||
|
TimeAndTimezone |
3GPP TS 23.040 V9.0.0 (2009-06) §9.2.3.11 pp67-68 | ||
|
byte[] |
3GPP TS 23.040 and 23.038 | ||
|
SMSProtocolId |
3GPP TS 23.040 V9.0.0 (2009-06) §9.2.3.9 pp65-67 | ||
|
byte[] |
3GPP TS 23.040 | ||
|
byte[] |
3GPP TS 23.040 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
3GPP TS 29.060 | ||
|
byte[] |
ETS 300 356 | ||
|
byte[] |
ETS 300 356 | ||
|
YearMonthDay |
Comment in ASN.1 module Core-INAP-CS1-DataTypes | ||
|
GenericDigits |
ITU-T Q.763 (12/1999) §3.24 p33 | ||
|
PriceInHundredthsOfUnits |
Comment in ASN.1 module CAP-datatypes | ||
|
HourMinute |
Comment in ASN.1 module Core-INAP-CS1-DataTypes |