A.1 InitialDP operation

29.0783GPPCAMEL Application Part (CAP) specificationCustomised Applications for Mobile network Enhanced Logic (CAMEL) Phase XRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

Table A.1

ISUP message IAM (Note 1)	CAP Operation InitialDP
Called party number (note 6)	CalledPartyNumber
Calling party number	CallingPartyNumber
Calling party’s category	CallingPartysCategory
Location number	LocationNumber
Original called number	OriginalCalledPartyID
User teleservice information (1^st priority) High layer compatibility IE contained in access transport (2^nd priority) (Note 2)	HighLayerCompatibility
High layer compatibility IE contained in access transport (Note 2)	HighLayerCompatibility2
Low Layer compatibility IE contained in access transport (note 4)	LowLayerCompatibility
Low Layer compatibility IE contained in access transport (note 4)	LowLayerCompatibility2
Generic number "additional calling party number"	AdditionalCallingPartyNumber
User service information prime (1^st priority) User service information (2^nd priority) (Note 3)	BearerCapability
User service information (Note 3)	BearerCapability2
Redirecting number	RedirectingPartyID
Redirection information	RedirectionInformation
Call diversion treatment indicators	ServiceInteractionIndicatorsTwo.Call diversion treatment indicators
Conference treatment indicators	ServiceInteractionIndicatorsTwo.Conference treatment indicators
User-to-user indicators (Note 5)	UU-Data.UUIndicator
User-to-user information (Note 5)	UU-Data.UUI

NOTE 1: Optional parameters may be absent, i.e. they are only mapped only if these parameters are available at the DP.

NOTE 2: If two high layer compatibility information elements are contained in the access transport parameter, then the second information element, carrying the preferred HLC, is mapped to the CAP highLayerCompatibility parameter, and the first information element, carrying the less preferred HLC, is mapped to the CAP highLayerCompatibility2 parameter.

NOTE 3: If User service information prime and User service information are present, then one of the following two mapping rules shall be applied. The principles for the choice of mapping rule are specified in 3GPP TS 23.078 [7].

One of User service information prime or User service information is mapped to Bearer Capability.
User service information prime is mapped to BearerCapability and User service information is mapped to Bearer Capability2.

NOTE 4: If two low layer compatibility information elements are contained in the access transport parameter, then the first information element, carrying the preferred LLC, is mapped to the CAP lowLayerCompatibility parameter, and the second information element, carrying the less preferred LLC, is mapped to the CAP lowLayerCompatibility2 parameter.

NOTE 5: If present in ISUP IAM, user-to-user indicators and user-to-user information may optionally be mapped into the InitialDP Operation.

NOTE 6: For trunk originating calls using overlap signalling, the called party number may contain partial address digits.

A.1.1 EventReportBCSM Operation

Table A.1.1

ISUP message SAMs (Note 1)	CAP Operation EventReportBCSM
Subsequent number	CalledPartyNumber

NOTE 1: For trunk originating calls using overlap signalling, subsequent address digits may be reported to the gsmSCF in EventReportBCSM, if requested by the gsmSCF with the ‘Collect Information’ operation.