is-725_c

TIA/EIA - IS-725

1

4C AUTOMATIC ROAMING OPERATIONS - CDMA2

3

4This section applies only to CDMA OTASP. It provides modifications to Section 4of IS-41.3-C "Automatic Roaming Operations", for CDMA Over-The-Air ServiceProvisioning.

5

6

7

8 Figure CC shows all the operations (new and existing) that are recommended forCDMA OTASP.

9

10

11

12

BS HLRMSC OTAF ACOTASP Data SMDPP OTASPREQ

VLR

FEATREQREDDIR

ROUTREQ

OTASPREQ

REGNOT

ASREPORT

BSCHALLAUTHDIR

MSINACT MSINACT

AUTHDIRASREPORT

BSCHALL

REGNOT

AUTHDIRASREPORT

BSCHALL13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

Figure CC OTASP Related IS-41 Operations for CDMA31

32

33

34

New operation scenarios for the following operations are included :35

36

1. SMSDeliveryPointToPoint (SMDPP) - existing operation37

38 2. OTASPRequest (OTASPREQ) - new operation39

3. AuthenticationDirective (AUTHDIR) - existing operation40

There are no new CDMA OTASP related operation scenarios for the existingoperations: ASREPORT, BSCHALL, REDDIR, FEATREQ, ROUTREQ, REGNOTand MSINACT, since the changes needed in these operations to support CDMAOTASP are minimal.

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Operations 15 CDMA-OTASP

TIA/EIA - IS-725

1

2

4.1 AuthenticationDirective (IS-41.3-C, page 6) 3

4

5The AuthenticationDirective (AUTHDIR) operation is used to request modificationof an MS’s authentication parameters. This operation is also used to transportEncryption Parameters (SMEKEY and CDMAPLCM) to the Serving MSC duringCDMA OTASP.

6

7

8

9

10

The following table lists the valid combinations of invoking and responding FEs. 11

12

13Table 2 FE Combinations for AUTHDIR

14

15INVOKING FE RESPONDING FE16

17Case 1 AC HLR 18

19

20Case 2 HLR Serving VLR21

22

Case 3 Serving VLR Serving MSC 23

24

25

26

27In addition to its use for transporting encryption parameters to the Serving MSC, Thethe AuthenticationDirective operation allows one or more of several possibleauthentication processes to be initiated:

28

29

30

1. An update of SharedSecretData (SSD) when SSD is shared. 31

322. An update of SSD when SSD is not shared. 33

343. An update of the CallHistoryCount (COUNT) parameter value.35

364. A Unique Challenge when SSD is shared (i.e., VLR-initiated).37

5. A Unique Challenge when SSD is not shared (i.e., AC-initiated). 38

396. Revocation of SSD sharing.

40

41These operation scenarios are illustrated in Sections 4.1.1 through 4.1.6C1,respectively. 42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

4.1.C1 Transport Encryption Parameters to Serving MSC for OTASP2

3

4 This operation scenario describes the use of the AuthenticationDirective operation totransport Encryption Parameters (SMEKEY and CDMAPLCM) to the Serving MSC.5

6

7

e

f

c

d

a

b

Serving System

AUTHDIR [MIN, ESN, SRVIND, MSCID, EncryptionParameters]

AC HLR VLR MSC

authdir [ ]

AUTHDIR [MIN, ESN, SRVIND, MSCID, EncryptionParameters]

AUTHDIR [MIN, ESN, SRVIND, EncryptionParameters]

ADTADTADT

authdir [ ]

authdir [ ]

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40 Figure 4.1.C1 Transport Encryption Parameters to the Serving MSC for OTASP41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1a. The AC has computed the Encryption Parameters (SMEKEY andCDMAPLCM) and needs to send them to the Serving MSC. It sends anAUTHDIR to the HLR.

2

3

4

Parameters Usage Type 5

6MIN Activation_MIN used temporarily during

OTASP.R

7

8

ESN MS's ESN. R 9

10SRVIND Indicates CDMA OTASP service. R

11

MSCID Serving MSC's System ID. R 12

13EncryptionParameters: Encryption Parameters for signaling message

encryption and voice privacy over the air-interface.

R14

15

16

[CDMAPLCM] CDMA Private LongCode Mask for voiceprivacy over the air-interface

R 17

18

19[SMEKEY] Signaling Message Encryption Key forSignaling Message Encryption over the air-interface

R20

21

22

b. The HLR forwards the AUTHDIR to the VLR currently serving the identifiedMS. The HLR is able to obtain the VLR's address from the MSCID parameterit receives from the AC. Parameters are as in Step-a.

23

24

25

26c. The Serving VLR sends an AUTHDIR to the Serving MSC. The VLR is able to

obtain the Serving MSC's address from the MSCID parameter it receives fromthe HLR. The parameters are the same as in Step a with the exception of theMSCID parameter which is not needed.

27

28

29

30

d. The Serving MSC returns an empty authdir to the Serving VLR to indicatethat the EncryptionParameters were successfully received.

31

32

33

e. The Serving VLR forwards the authdir to the HLR. 34

35f. The HLR forwards the authdir to the AC. 36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

4.35 SMSDeliveryPointToPoint (IS-41.3-C, page 141)2

3

4 The SMSDeliveryPointToPoint (SMDPP) operation is used to transfer short messagesinformation from one point to another point and report on the success or failure ofthat transfer (for example, as used in SMS and CDMA OTASP).

5

6

7

8

The following table lists the valid combinations of invoking and responding FEs.9

10

11Table 32 FE Combinations for SMDPP12

13INVOKING

FERESPONDING

FEWhen14

15

16Case 1 SME MC SMS message origination

17

18 Case 2 MC MC SMS message transition fromoriginating MC control to destinationcontrol

19

20

21

Case 3 MC SME SMS message delivery22

23

Case 4 SME SME SMS message origination to delivery24

25

Case 5 OTAF MSC CDMA OTASP message delivery26

27

28

29 The SMSDeliveryPointToPoint operation has two variations:30

31 1. Successful transfer of a short message to another point.32

2. Unsuccessful transfer of a short message to another point.33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

4.35.C1 Serving MSC Attachment to an OTAF 2

3

4This operation scenario describes the use of SMSDeliveryPointToPoint to provide anattachment between the Serving MSC and an OTAF for CDMA OTASP. 5

6

dsmdpp [ ]

smdpp [ESN, MSMIN, SYSCAP, MSCID]

a

b

OTAF

SMDPP [MIN, TRN, ACTCODE, SRVIND,SMS_BearerData, SMS_TID]

c

MSC

Serving System

SMDPP [MIN, TRN, ACTCODE, SRVIND,SMS_BearerData, SMS_TID]

SMT cs

SMTcs

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

Figure 4.35.C1 Serving MSC Attachment to an OTAF 31

32

33

34

a. An Activation_MIN to be used temporarily for the duration of this OTASPattempt is assigned. The OTAF sends an SMDPP to the Serving MSC.

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1Parameters Usage Type

2

MIN Activation_MIN used temporarily duringOTASP.

R3

4

5TRN Used to associate the SMDPP (and the OTAF)

with the OTASP call.R

6

7

ACTCODE Instructs the Serving MSC to attach to theOTAF for this call.

R8

9

10SRVIND Indicates CDMA OTASP service. R

11

SMS_BearerData This parameter is empty. It is included tocomply with IS-41 backward compatibilityrules.

MBC12

13

14

15 SMS_TID This parameter is empty. It is included tocomply with IS-41 backward compatibilityrules.

MBC16

17

18

b. The Serving MSC associates the call in question with the OTAF. It returns ansmdpp to the OTAF containing the following parameters

19

20

21Parameters Usage Type

22

ESN MS's ESN. R23

24MSMIN MIN received from the MS. R25

26 SYSCAP Serving System's authentication capabilities. R27

MSCID Serving MSC's System ID. R28

29If the AC had previously denied access to this MS, DENACC may be included.If the HLR had previously denied authorization to this MS, AUTHDEN may beincluded.

30

31

32

Steps c and d are executed to release the TRN if the OTAF is the desired OTAFand no redirection to another CSC - OTAF will take place.

33

34

35

c. The OTAF sends a second SMDPP to the MSC with the ACTCODE directingthe MSC to release the TRN, permitting the TRN to be reused.

36

37

38

39 Parameters Usage Type40


R41

42

43 TRN Used to associate the SMDPP (and the OTAF)with the OTASP call.

R44

45

ACTCODE Instructs the Serving MSC to release the TRN. R46

47 SRVIND Indicates CDMA OTASP service. R48

SMS_BearerData This parameter is empty. It is included tocomply with IS-41 backward compatibilityrules.

MBC49

50

51

52 SMS_TID This parameter is empty. It is included tocomply with IS-41 backward compatibilityrules.

MBC53

54

55

d. The MSC sends an empty smdpp to the OTAF to acknowledge the receipt ofthe SMDPP in Step c.

56

57

58

59

60


TIA/EIA - IS-725

1

4.35.C2 Exchange of OTASP Data Messages 2

3

4This operation scenario describes the use of the SMSDeliveryPointToPointoperation to exchange OTASP Data Messages between the OTAF and the ServingMSC.

5

6

7

smdpp [SMS_BearerData (OTASP Data Message)]

a

b

OTAF

SMDPP [MIN, ESN, SRVIND, SMS_TID,SMS_BearerData (OTASP Data Message)]

MSC

Serving System

SMTcx

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

Figure 4.35.C2 Exchange of OTASP Data Messages 23

24

25

26Note: In the above figure, SMTcx = (x=m, l: depending on the mode of MSoperation (if known at the OTAF), the lengths of the OTASP Data Messages beingexchanged and the corresponding response time at the MS). See Section 7 foroperation timer values in Table 63.

27

28

29

30

31

a. The OTAF sends an SMDPP to the Serving MSC. 32

33


35MIN Activation_MIN used temporarily duringOTASP

R36

37

ESN MS's ESN. R 38

39SRVIND Indicates CDMA OTASP service. R40

SMS_BearerData Contains an OTASP Data Message. R 41

42SMS_TID This parameter is empty. It is included to

comply with IS-41 backward compatibilityrules.

MBC43

44

45

b. The Serving MSC returns an smdpp to the OTAF with the SMS_BearerDatacontaining the OTASP Data Message received from the MS, as a response tothe OTASP Data Message contained in the SMS_BearerData in Step a.

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

4.35.C3 OTAF Request to Initiate MSC Procedures2

3

4 This operation scenario describes the use of SMSDeliveryPointToPoint to initiateMSC procedures.5

6

smdpp [ ]

a

b

OTAF

SMDPP [MIN, ESN, ACTCODE, NEWMIN,SRVIND, SMS_BearerData, SMS_TID]

MSC

Serving SystemDesired

SMT cx

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22 Figure 4.35.C3 OTAF Request to Initiate MSC Procedures23

24

25

Note: In the above figure, SMTcx = (x=s, m: depending on the ACTCODE value).See Section 7 for operation timer values in Table 63.

26

27

28

a. The OTAF sends an SMDPP to the Serving MSC with the MS'sActivation_MIN, ESN, ACTCODE, and the newly assigned MIN.

29

30

31Parameters Usage Type32


R33

34

35ESN MS’s ESN. R36

37 ACTCODE Instructs the Serving MSC as to whichprocedures it should initiate.

R38

39NEWMIN The new MIN assigned to the MS during this

OTASP attempt (e.g. provided to permit theMS to be registered with the responsibleHLR).

O40

41

42

43

SRVIND Indicates CDMA OTASP service. R44

45SMS_BearerData This parameter is empty. It is included to

comply with IS-41 backward compatibilityrules.

MBC46

47

48

SMS_TID This parameter is empty. It is included tocomply with IS-41 backward compatibilityrules.

MBC49

50

51

52 b. The Serving MSC initiates the desired procedures (e.g. RegistrationNotificationto the HLR pointed to by the NEWMIN) and sends an empty smdpp to theOTAF.

53

54

55

For unsuccessful cases the Serving MSC may return the AUTHDEN parameteror the SMS_CauseCode parameter, or both parameters.

56

57

58

59

60


TIA/EIA - IS-725

1

4.CC OTASPRequest 2

3

4The OTASPRequest (OTASPREQ) operation is used by the OTAF to request the ACto initiate certain procedures and to optionally return appropriate resultingparameters. The following table lists the valid combinations of invoking andresponding FEs.

5

6

7

8

9

Table 4.CC FE Combinations for OTASPREQ 10

11

INVOKING FE RESPONDING FE 12

13

Case 1 OTAF HLR 14

15Case 2 HLR AC 16

17

18

4.CC.1 OTAF Request to Initiate AC Procedures19

20

21

This operation scenario describes the use of the OTASPRequest operation to initiateAC procedures.

22

23

24

25

a

b

OTAF AC

OTASPREQ [MIN, ESN, ACTCODE, SRVIND, ACProcedureInputs]

c

d

HLR

otaspreq [AKEYPV, PublicEncryptionValues, Reports, OTASPRC]

otaspreq [AKEYPV, PublicEncryptionValues, Reports, OTASPRC]

OTASPREQ [MIN, ESN, ACTCODE, SRVIND, ACProcedureInputs]

OTARTcx

OTARTcx

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

Figure 4.CC.1 OTAF Request to Initiate AC Procedures 50

51

52

53Note: In the above figure, OTARTcx = (x=s, l: depending on the ACTCODE value).See Section 7 for operation timer values in Table 63.

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

2

3

4

a. The OTAF sends an OTASPREQ to the HLR with the ActionCode(ACTCODE) parameter requesting the AC to initiate certain procedures (e.g.the AC may be requested to initiate the SSD update procedures and possiblyreturn SSDURPT and UCHALRPT).

5

6

7

8

9 Parameters Usage Type10


R11

12

13 ESN MS’s ESN. R14

ACTCODE Request the AC to initiate a particularprocedure.

R15

16

17 SRVIND Indicates CDMA OTASP service. R18

ACProcedureInputs: Parameters needed for AC procedures.19

20 AKEYPV Supported A-Key protocol version(s). Includeif public encryption values generation isrequested.

O21

22

23MSKEY Mobile Station Partial Key. Include if A-Key

generation is requested.O24

25

MSCID Serving MSC's System ID. Include if SSDupdate or Reauthentication is requested.

O26

27

28 SYSCAP Authentication capabilities of Serving System.Include if SSD update or reauthentication isrequested.

O29

30

MSMIN MIN received from the MS at OTASP callorigination.

R31

32

33 AUTHDATA The authentication data used by the MS tocompute AUTHR. Include if reauthenticationis requested.

O34

35

36 AUTHR Authentication result provided by the MS.Include if reauthentication is requested.

O37

38 COUNT Value of CallHistoryCount provided by theMS. Include if reauthentication is requested.

O39

40RAND Random number derived from the MS provided

RANDC by the OTAF. Include ifreauthentication is requested.

O41

42

43NEWMIN The MIN to be used if OTASP completes

successfully. Include if known.

This may be a newly assigned MIN, or a MINthat has been reserved for assignment to theMS but that has not yet been downloaded tothe MS.

O44

45

46

47

48

49

b. The HLR forwards the OTASPREQ to the AC. Parameters are the same as inStep a. The AC starts executing the specified procedures.

50

51

52

c. The AC returns an otaspreq to the HLR.53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

2


4AKEYPV A-Key computation protocol version used by

the AC. Include if public encryption valuesare being returned.

O5

6

7

PublicEncryptionvalues: Parameters comprising Public EncryptionValues.

8

9

10MODVAL Modulus value. O11

PRIMVAL Primitive value. O 12

13BSKEY Base Station Partial Key. O14Reports: Reports for various AC procedures15

SSDURPT SSD Update report. Include if received fromthe Serving MSC.

O 16

17

UCHALRPT Unique Challenge report. Include if receivedfrom the Serving MSC.

O 18

19

DENACC Deny Access parameter. Include if the MS hasnot been reauthenticated correctly, or if acount mismatch was detected.

O 20

21

22

VPRPT Voice privacy report. Include if received fromthe Serving MSC.

O 23

24

25SMERPT Signaling message encryption report. Include ifreceived from the Serving MSC.

O26

27

OTASPRC Include to describe an OTASP related errorcondition at the AC, other than the ones thatcan be described by the DENACC,SSDURPT, UCHALRPT, VPRPT andSMERPT parameters.

O 28

29

30

31

32

d. The HLR forwards the otaspreq to OTAF. 33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5C VOICE FEATURE SCENARIOS - CDMA

This section applies only to CDMA OTASP. It provides modifications to Section 6of IS-41.3-C "Voice Feature Scenarios", for CDMA Over-The-Air ServiceProvisioning.

6.CC CDMA Over-the-Air Service Provisioning Scenarios

This section depicts interaction scenarios between network entities relating toCDMA OTASP.

Scenarios 27 CDMA-OTASP

TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.1a Serving MSC Attached to the Initial and Desired CSC

This operation scenario describes the use of SMSDeliveryPointToPoint to provide anattachment between the Serving MSC and the Desired OTAF, as used in CDMAsystems. In this scenario, the desired OTAF is attached to (or served by) the initialCSC.

Note, see 6.CC.1b for an alternative recommendation.

c

e

f

Dialog between MS user and CSC Operator or VRU

SMDPP [MIN, TRN, ACTCODE, SRVIND]

smdpp [MSMIN, ESN, MSCID, SYSCAP]

dInformation transfer [proprietary]

MSC OTAFMS CSC

Serving System Initial and Desired

aOTASP Call Origination (*FC+ supplementary digits)

i

j

SMDPP [ACTCODE, MIN, ESN, SRVIND]

smdpp [ ]

g

hInformation transfer [proprietary]

Information transfer [proprietary]

bCall delivery to the CSC

SMTcs

SMT cs

Figure 6.CC.1a Serving MSC Attached to the Initial and Desired CSC

CDMA-OTASP 28 Scenarios

TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. The Serving MSC recognizes the call origination to be an OTASP request fromthe OTASP Feature Code (*FC) received. It allocates a unique TemporaryReference Number (TRN) for this OTASP attempt.

b. The Serving MSC may perform normal subscriber validation and authenticationprior to proceeding. Irrespective of which, the MSC connects the voice call to aCSC, based on the Feature Code and any supplementary digits (e.g., *FC, *FC+ XX, *FC + XX + DN) specified by the user during OTASP activation. TheTRN is transferred to the CSC during call set-up. Note: The TRN may be sentas a Calling Number or a Called Number based on the signaling scheme used.

c. A call taker or a voice response unit at the CSC begins a dialog with the user.The CSC determines that the desired OTAF is attached to this CSC.

d. The CSC informs (in a proprietary manner) the OTAF of the initial contact.

e. The OTAF assigns a MIN to be used during this OTASP attempt. It sends anSMDPP to the Serving MSC. The OTAF is able to determine the routingaddress of the MSC from the TRN previously provided.

Parameters Usage Type


R

TRN Used to associate the SMDPP (and the OTAF)with the OTASP call.

R


R

SRVIND Indicates CDMA OTASP service. R

f. The Serving MSC associates the call in question with the OTAF. It returns ansmdpp to the OTAF containing the following parameters.


MSMIN MIN received from the MS. R

ESN MS's ESN. R

MSCID Serving MSC's System ID. R

SYSCAP Serving System's authentication capabilities. R

If the AC had previously denied access to this MS, DENACC may be included.If the HLR had denied authorization to this MS, AUTHDEN may be included.

g. The OTAF informs (in a proprietary manner) the CSC that the attachment withthe Serving MSC was accomplished.

h. The CSC informs (in a proprietary manner) the OTAF that it should direct theServing MSC to release the TRN.

i. The OTAF sends a second SMDPP to the MSC with the ACTCODE directingthe MSC to release the TRN, permitting the TRN to be reused. Parameterssame as in 4.35.C1, Step c.

j The MSC sends an empty smdpp to the OTAF acknowledging the receipt ofSMDPP in Step-i.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.1b Serving MSC Attached to the Initial and Desired CSC (ALT)

This operation scenario describes the use of the FeatureRequest operation to facilitateattachment following the receipt of an OTASP origination from an MS.

Note, see 6.CC.1a for an alternative recommendation.

h

a

b

c

d

e

f

i

j

MSC OTAFMS

Serving System

CSC

g

featreq [DGTSDEST]

call extended to CSC

dialog between MS user and CSC operator or VRU

FEATREQ [MIN, ESN, MSCID, BILLID]

proprietary information transfer

SMDPP [ACTCODE]

smdpp [ ]



Intitial and Desired

FRRT

SMTcs

SMTcs

OTASP Call Origination (*FC+supplementary digits)

Figure 6.CC.1b Serving MSC Attached to the Initial and Desired CSC (ALT)

a. The MSC receives an OTASP call origination.

b. The Serving MSC may perform normal subscriber validation and authenticationprior to proceeding. Irrespective of the outcome of the validation andauthentication, the Serving MSC recognizes the call as an OTASP request fromthe OTASP Feature Code (*FC) received.

As a result, it assigns a BillingID to the call and sends a FEATREQ to theOTAF to obtain a Temporary Reference Number (TRN) to use in routing thecall to the CSC. The MIN and ESN parameters are set to the values receivedfrom the MS in the origination message, and the MSC's MSCID is used topopulate that parameter. If SS7 is used, the MSC's point code and subsystemnumber are used to populate the PC_SSN parameter.

The address to be used by the OTAF to send the SMDPP messages to the MSCfor OTASP may be derived from the MSCID using a local translation function,


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

or it may be obtained from lower layer addressing information (or from thePC_SSN parameter, if present).

c. The CSC is assumed to have a pool of numbers, similar to a pool of TLDNs,that can be used to route calls to the CSC. (If one CSC serves multiple OTAFs,then, based on implementation, this pool may be partitioned into separate poolsfor each OTAF or it may be one combined pool.) Based on implementation,the OTAF selects one of these numbers that is not currently in use or it usesproprietary signaling (not shown in the figure) to obtain such a number fromthe CSC, and returns this number for use as the TRN to the MSC using theDigits (destination) parameter in the featreq.

d. The voice call to the CSC is established using the TRN as called party number.It is assumed that the CSC is connected to the PSTN using an interface, e.g.,direct inward dialing PBX trunks or an ISDN interface, that always providesthe called number as part of the signaling used to offer the call.

e. The potential new subscriber and the responding customer service agent (orVRU port) begin a dialog.

f. In parallel with Step e, proprietary signaling between the CSC and the OTAF isused to notify the OTAF of the initial contact (and of the TRN used for thatcontact).

g The OTAF assigns an Activation_MIN to be used temporarily for the durationof this OTASP attempt. It sends an SMDPP to the Serving MSC.



R


R


R


h. The Serving MSC associates the call in question with the OTAF. It returns ansmdpp to the OTAF containing the following parameters.


MSMIN MIN received from the MS R

ESN MS's ESN R

MSCID Serving MSC's System ID R

SYSCAP Serving System's authentication capabilities R

i. The OTAF sends a second SMDPP to the MSC with the ACTCODE directingthe MSC to release the TRN, permitting the TRN to be re-used.

j. The MSC sends an empty smdpp to the OTAF acknowledging the receipt ofthe SMDPP in Step i.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.2a OTASP Call Redirected from Initial CSC to Desired CSC - InitialOTAF not Attached to Serving MSC

This scenario describes the use of SMSDeliveryPointToPoint operation, to attach theServing MSC to the desired OTAF. In this scenario the desired OTAF is not attachedto (nor, served by) the initial CSC that engages in a voice conversation with the MSuser. Instead, the desired OTAF is attached to (or, served by) a CSC to which theMS's voice call gets redirected from the initial CSC. Also, in this scenario, the initialOTAF is not attached to the Serving MSC.

Note, see 6.CC.2b for an alternative recommendation.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

c

e

Dialog between MS user and initial CSC Operator or VRU



d


Call extended to desired CSC

Dialog between MS user and desired CSC Operator or VRU

i

j

f

SMDPP [MIN, ESN, ACTCODE, SRVIND]

smdpp [ ]

k

l

g

h



MSC OTAFMS CSC

Serving System

OTAF CSC

aOTASP Call Origination (*FC+supplementary digits)

bCall Delivery to the Initial CSC

Initial Desired

SMTcs

SMTcs

Figure 6.CC.2a OTASP Call Redirected from Initial CSC to Desired CSC -Initial OTAF not Attached to Serving MSC


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. The Serving MSC recognizes the call to be an OTASP request from the OTASPFeature Code (*FC) received. It allocates a unique TRN for this OTASPattempt.

b. The Serving MSC may perform normal subscriber validation and authenticationprior to proceeding. Irrespective of the outcome of the validation andauthentication, the MSC connects the voice call to a CSC, based on the FeatureCode and any supplementary digits (e.g., *FC, *FC + XX, *FC + XX + DN)specified by the user during OTASP activation. The TRN is transferred to theCSC during call set-up.

Note: The TRN may be sent as a Calling Number or a Called Number based onthe signaling schemes used.

c. A call taker or a voice response unit at the CSC begins a dialog with the userand determines that the desired OTAF is not attached to this CSC. The CSCcall taker or voice response unit . . .

d. . . . extends the voice call to another CSC that is associated with the desiredOTAF. The TRN is also forwarded to the new CSC.

e. A CSC call taker or a voice response unit at the new CSC begins a dialog withthe user.

f. The CSC contacts (in a proprietary manner) the desired OTAF.

g-l. Same as 6.CC.1a, Steps e-j.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.2b Serving MSC Redirected from Initial CSC to Desired CSC

This operation scenario describes the transfer of attachment from the OTAF/CSCpair associated to the Serving MSC to a different OTAF/CSC pair. When used, thisscenario would follow Step d in the scenario shown in 6.CC.1b.

Note, see 6.CC.2a for an alternative recommendation.

h

a

b

c

d

e

f

i

j

k

m

n

g

l

MSC OTAF CSCMS OTAF CSC

Serving System Initial Desired

dialog between MS user and Operator or VRU at Initial CSC


ROUTREQ [MIN, ESN, MSCID, BILLID]

routreq [DGTSDEST]

REDDIR [MIN, ESN, DGTSDEST, BILLID]

reddir

release call leg to Initial CSC

call extended to desired CSC


SMDPP [ACTCODE]

smdpp [ ]



dialog between MS user and Operator or VRU at Initial CSC

RRT

RDDT

SMTcs

SMTcs

Figure 6.CC.2b Serving MSC Redirected from Initial CSC to Desired CSC

a. Based on the ongoing dialog with the initial CSC, the CSC operator determinesthat the initial OTAF/CSC pair is not the desired OTAF/CSC pair. The CSC isinformed of the identify of the desired OTAF/CSC pair.

b. The initial CSC agrees to transfer attachment to the desired OTAF/CSC pair.Proprietary signaling is used to identify the desired OTAF/CSC pair to the


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

initial OTAF, which uses local tables to determine the network address of thedesired OTAF.

c. The initial OTAF sends a ROUTREQ to the desired OTAF to obtain a numberthat can be used for redirection of the OTASP call from the initial CSC to thedesired CSC. The BillingID, MSCID, MIN, and ESN in this message arepopulated with the values received at Step b in the scenario shown in 6.CC.1b(as is the PC_SSN parameter if one was received and if SS7 is used). TheOTAF uses local information to determine the Serving MSC'sSystemMyTypeCode (i.e., based on Serving MSC's MSCID).

The address to be used by the desired OTAF in sending OTASP related SMDPPmessages to the MSC may be derived from the MSCID using a local translationfunction, or it may be obtained from the PC_SSN parameter, if present, but itshould not be obtained from lower layer addressing information (e.g., SCCPCalling Party Address).

d. The desired OTAF sends the initial OTAF the number to use in redirecting theOTAF call using the Digits (destination) parameter in the routreq. Thisnumber will serve as TRN once the call is redirected.

e. The initial OTAF sends a REDDIR to the Serving MSC, using as Digits(destination) the value received at Step d. The MIN, ESN, and BillingID arepopulated with the values received at Step b in the Scenario shown in 6.CC.1b.

f. The Serving MSC returns a reddir to the initial OTAF.

g. The MSC releases the call leg to the initial CSC. It also releases the TRN usedto route that call leg.

h. The MSC extends the OTASP call to the desired CSC, using the numberreceived in the Digits (destination) parameter at Step e as the called partynumber, and associates this number to the call as the TRN.

i. The subscriber and the responding CSC operator (or VRU port) begin a dialog.

j. In parallel with Step i, proprietary signaling between the CSC and the OTAF isused by the CSC to inform the OTAF of the contact and of the number onwhich the call arrived.

k. The OTAF assigns an Activation_MIN to be used temporarily for the durationof this OTASP attempt. It sends an SMDPP to the Serving MSC.



R


R


R


l. The Serving MSC associates the call in question with the OTAF. It returns ansmdpp to the OTAF containing the following parameters.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


MSMIN MIN received from the MS R

ESN MS's ESN R

MSCID Serving MSC's System ID R


m. The OTAF sends a second SMDPP to the MSC with the ACTCODE directingthe MSC to release the TRN, permitting the TRN to be re-used.

n. The MSC sends an empty smdpp to the OTAF acknowledging the receipt ofthe SMDPP in Step m.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.2c OTASP Call Redirected from Initial CSC to Desired CSC - InitialOTAF Initially Attached to Serving MSC

This scenario describes the use of SMSDeliveryPointToPoint operation, to attach theServing MSC to the desired OTAF. In this scenario the desired OTAF is not attachedto (or, served by) the initial CSC that engages in a voice conversation with the MSuser. Instead, the desired OTAF is attached to (or, served by) a CSC to which theMS's voice call gets redirected from the initial CSC. Also, in this scenario, the initialOTAF is initially attached to the Serving MSC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

MSC OTAFMS CSC

Serving System

OTAF CSC

aOTASP Call Origination (*FC+supplementary digits)

dSMDPP [MIN, TRN, ACTCODE, SRVIND]

esmdpp [MSMIN, ESN, MSCID, SYSCAP]

cInformation transfer [proprietary]

SMT cs

Dialog between MS user and initial CSC Operator or VRU




Call extended to desired CSC

Dialog between MS user and desired CSC Operator or VRU

SMDPP [MIN, ESN, ACTCODE, SRVIND]

smdpp [ ]

g

h

f

i

j

k

n

o

l

mInformation transfer [proprietary]


bCall delivery to the Initial CSC

Initial Desired

SMT cs

SMT cs

Figure 6.CC.2c OTASP Call Redirected from Initial CSC to Desired CSC -Initial OTAF Initially Attached to Serving MSC


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. The Serving MSC recognizes the call to be an OTASP request from the OTASPFeature Code (*FC) received. It allocates a unique TRN for this OTASPattempt.

b. The Serving MSC may perform normal subscriber validation and authenticationprior to proceeding. Irrespective of the outcome of the validation andauthentication, the MSC connects the voice call to a CSC, based on the FeatureCode and any supplementary digits (e.g., *FC, *FC + XX, *FC + XX + DN)specified by the user during OTASP activation.. The TRN is transferred to theCSC during call set-up.

Note: The TRN may be sent as a Calling Number or a Called Number based onthe signaling schemes used.

c. The CSC contacts an initial OTAF attached to it.

d-e. Same as in 6.CC.1a, Steps e-f.

f. A call taker or a voice response unit at the CSC begins a dialog with the userand determines that the desired OTAF is not attached to (or, served by) thisCSC. The CSC call taker or voice response unit . . .

g. . . . extends the voice call to another CSC that is associated with the desiredOTAF. The TRN is also forwarded to the new CSC.

h. A CSC call taker or a voice response unit at the new CSC begins a dialog withthe user.

i. The CSC contacts the desired OTAF.

j-o. Same as in 6.CC.1a, Steps e-j.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.3 A-key Generation

This operation scenario describes the use of the SMSDeliveryPointToPoint andOTASPRequest operations to perform A-Key generation procedures, the end-resultof which is an identical A-Key at the MS and the AC.

SMDPP [SMS_BearerData (MS Key Request Message), SRVIND]

Serving System

MSC OTAFMS HLR AC

OTASPREQ [ACTCODE, AKEYPV]

otaspreq [AKEYPV, MODVAL, PRIMVAL, BSKEY]

a

b

d

e

c

f

g

h

i

k

l

j

m

n

MS Key Request Message

smdpp [SMS_BearerData (MS Key Response Message)]

smdpp [SMS_BearerData(Key Generation Response Message)]

o

p

OTASPREQ [ACTCODE, AKEYPV]

MS Key Response Message

SMDPP [SMS_BearerData (Key Generation Request Message), SRVIND]

Key Generation Request Message

Key Generation Response Message

otaspreq [ ]

otaspreq [AKEYPV, MODVAL, PRIMVAL, BSKEY]

OTASPREQ [MSKEY, ACTCODE]

otaspreq [ ]

OTASPREQ [MSKEY, ACTCODE]

Home System

OTARTcs OTARTcs

SMTcl

SMTcl

OTARTcsOTARTcs

Figure 6.CC.3 A-key Generation


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. The OTAF determines that the A-Key generation procedure is to be performed,perhaps from a trigger from the CSC. It sends the HLR an OTASPREQ, whichincludes AKEYPV, corresponding to the MS's capabilities, and ACTCODE, setto Generate Public Encryption Values procedure.

b. The HLR forwards the OTASPREQ to the AC. Parameters are the same as inStep a.

c. The AC sends the AKEYPV, corresponding to the protocol version it will use,MODVAL, PRIMVAL, and BSKEY to the HLR in an otaspreq.

d. The HLR forwards the otaspreq to the OTAF. Parameters are the same as inStep c.

e. The OTAF encapsulates an air-interface OTASP Data Message (MS KeyRequest Message) containing AKEYPV, MODVAL, and PRIMVAL, inSMS_BearerData and forwards it in an SMDPP to the Serving MSC.

f. The Serving MSC removes the MS Key Request Message fromSMS_BearerData and sends it to the MS over the air-interface.

g. The MS successfully computes MSKEY and indicates this fact to the ServingMSC in RESULT_CODE sent in an air-interface OTASP Data Message (MSKey Response Message).

h. The Serving MSC encapsulates the air-interface OTASP Data Message (MSKey Response Message) containing the RESULT_CODE, in SMS_BearerDataand forwards it in an smdpp to the OTAF.

i. The OTAF encapsulates an air-interface OTASP Data Message (KeyGeneration Request Message) containing the BSKEY parameter inSMS_BearerData and forwards it in an SMDPP to the Serving MSC.

j. The Serving MSC removes the Key Generation Request Message fromSMS_BearerData and sends it to the MS over the air-interface.

k. The MS successfully computes the A-Key using BSKEY, MODVAL, and therandom exponent it had used for computing MSKEY, and indicates this fact tothe Serving MSC in RESULT_CODE using a reverse-direction air-interfaceOTASP Data Message (Key Generation Response Message). It also includesthe MSKEY parameter in this reverse direction air-interface OTASP DataMessage.

l. The Serving MSC encapsulates the air-interface OTASP Data Message (KeyGeneration Response Message) in SMS_BearerData and forwards it in ansmdpp to the OTAF. The OTAF thus receives the MSKEY parameter alongwith a confirmation, in RESULT_CODE, that the MS has successfullycomputed the A-Key.

m. The OTAF sends an OTASPREQ, containing MSKEY, and ACTCODE set toGenerate A-Key procedure, to the HLR.

n. The HLR forwards the OTASPREQ to the AC. The parameters are the same asin Step m.

o. The AC successfully computes the A-Key using MSKEY, MODVAL, and therandom exponent it had used for computing BSKEY, and indicates this fact tothe HLR by sending it an empty otaspreq.

p. The HLR forwards the empty otaspreq to the OTAF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.4 SSD Update When SSD is Not Shared

This scenario describes the use of OTASPRequest, AuthenticationDirective,BaseStationChallenge, and the AuthenticationStatusReport operations to performSSD Update for the MS for the case where SSD is not shared between the AC andthe VLR.

NOTE

The Shared SSD scenario is not supportedduring a CDMA OTASP session.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

MS MSC OTAF HLR ACVLR

OTASPREQ [MSMIN, ACTCODE, SYSCAP, MSCID, NEWMIN, SRVIND]

AUTHDIR [RANDSSD, RANDU, AUTHU, SRVIND, MSMIN, MSCID]

authdir [ ]

bschall [AUTHBS]

bschall [AUTHBS]

a

b

d

c

k

l

m

n

e

f

g

h

j

o

p

q

r

s

t

i

u

v

w

x

y

z

asreport [ ]

aa

bbotaspreq [SSDURPT, UCHALRPT]

authdir [ ]

authdir [ ]

otaspreq [SSDURPT, UCHALRPT]

update SSD [RANDSSD]

base station challenge (RANDBS)

asreport [ ]

OTASPREQ [MSMIN, ACTCODE, SYSCAP, MSCID, NEWMIN, SRVIND]

AUTHDIR [RANDSSD, RANDU, AUTHU, SRVIND, MSMIN, MSCID]

AUTHDIR [RANDSSD, RANDU, AUTHU, SRVIND]

BSCHALL [RANDBS, SRVIND]

asreport [ ]

Home SystemServing System

ADT ADTADT

BSCT

ASRRT

OTARTclOTART cl

BSCTASRRTBSCT

ASRTASRTASRT

bschall [AUTHBS]

challenge response [AUTHBS]

challenge response (AUTHU)

unique challenge (RANDU)

SSD update (success)

ASREPORT [SSDURPT, UCHALRPT, SRVIND]





Figure 6.CC.4 SSD Update when SSD is not Shared


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. The OTAF determines that SSD for the MS is to be updated, perhaps from aCSC request. It sends an OTASPREQ to the HLR indicating in the ActionCode(ACTCODE) parameter that the SSD update procedure be performed for theMS.


MSMIN MIN received from the MS. R

ACTCODE Request the AC to initiate SSD Update.. R




NEWMIN Include if a new MIN is commited in theMS.

O

b. The HLR forwards the OTASPREQ to the AC.

c. SSD Generation Procedure is executed at the AC to produce a new value of theSSD using the A-Key of the MS, ESN and a Random Number (RANDSSD)generated by the AC.

The AC chooses a Unique Random Variable (RANDU) and executesAuthentication Signature Generation procedure using the new SSD-A, ESN,MIN1, and MIN2 (Note: MIN1 and MIN2 are derived from the MSMINparameter) associated with the MS to produce the expected AuthenticationResponse for Unique Challenge (AUTHU).

An AUTHDIR is sent from the AC to the HLR associated with the MS.

d. The HLR determines the VLR address from the MSCID and forwards theAUTHDIR to the VLR.

e. The VLR determines the MSC address from the MSCID and forwards theAUTHDIR to the Serving MSC. MSCID parameter is not included.

f. The Serving MSC returns an empty authdir to the Serving VLR to indicatethat the directive has been accepted.

g. The Serving VLR forwards the authdir to the HLR.

h. The HLR forwards the authdir to the AC.

i. The Serving MSC sends an SSD Update order to the MS using the value ofRANDSSD provided by the AC. The message is sent over a voice or trafficchannel.

j. The MS executes the SSD Generation Procedure to produce a new value ofSSD using the value of RANDSSD provided in the SSD Update order, ESNand A-Key.

The MS selects a Random Number (RANDBS) and sends a Base StationChallenge order to the Serving MSC including the value of RANDBS. The MSthen executes the Authentication Signature Generation procedure to producethe expected Authentication Result (AUTHBS) using the new value of SSD-A,ESN, MIN1 and the Random Number (RANDBS).

k. The Serving MSC sends a Base Station Challenge (BSCHALL) to the ServingVLR to request a response to the Base Station Challenge Order received fromthe MS.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

l. The Serving VLR forwards the BSCHALL to the HLR.

m. The HLR forwards the BSCHALL to the AC.

n. The AC executes the Authentication Signature Generation procedure toproduce an Authentication Result (AUTHBS) using the new value of SSD-A,ESN, MIN1 (Note: MIN1 is derived from the MSMIN parameter) for the MSand the Random Number (RANDBS) provided in the BSCHALL. TheAUTHBS value is returned to the HLR in the bschall.

o. The HLR forwards the bschall to the Serving VLR.

p. The Serving VLR forwards the bschall to the Serving MSC.

q. The Serving MSC passes the AC’s computed value of AUTHBS to the MS in aBase Station Challenge response message.

r. If the AUTHBS result provided by the AC matches the value computed by theMS, the MS stores the new SSD value for use in future executions of theAuthentication Signature Generation procedure and sends an SSD UpdateConfirmation message to the Serving MSC.

s. The Serving MSC sends a Unique Challenge order to the MS using theRANDU provided in the AUTHDIR in Step-e.

t. The MS executes the Authentication Signature Generation procedure usingRANDU and the SSD-A currently stored, ESN, MIN1, and MIN2 to produce anAuthentication Response for Unique Challenge (AUTHU) which is then sent tothe Serving MSC.

The Serving MSC compares the value of AUTHU provided by the AC in theAUTHDIR with that received from the MS.

u. The Serving MSC sends an ASREPORT to the Serving VLR indicating thesuccess or failure of the SSD Update and the Unique Challenge.

v. The Serving VLR forwards the ASREPORT to the HLR.

w. The HLR forwards the ASREPORT to the AC.

x. The AC stores the new SSD value for use in future executions of theAuthentication Signature Generation procedure for the MS. The AC sends anempty asreport to the HLR.

y. The HLR forwards the asreport to the Serving VLR.

z. The Serving VLR forwards the asreport to the Serving MSC.

aa. The AC forwards the SSDURPT and the UCHALRPT parameters, if received,in an otaspreq to the HLR.

bb. The HLR forwards the otaspreq to the OTAF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.5 Re-Authentication for Voice Privacy, Message Encryption or both

This scenario describes the use of SMSDeliveryPointToPoint,AuthenticationDirective, and AuthenticationStatusReport operations to perform MSre-authentication for the purpose of computing and sending encryption parameters tothe Serving MSC. The SMEKEY and CDMAPLCM are used to invoke messageencryption and voice privacy, respectively, on the air-interface.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

HLRMSC OTAFMS

OTASPREQ [AUTHDATA, RAND, AUTHR, COUNT, MSCID, MSMIN]

AC

a

b

d

e

c

f

g

h

i

j

Re-Authenticate Response Message

smdpp [SMS_BearerData (Re-Authenticate Response Message)]

authdir [ ]

OTASPREQ [AUTHDATA, RAND, AUTHR, COUNT, MSCID, MSMIN]

AUTHDIR [SRVIND, MSCID, EncryptionParameters]

VLR

k

l

m

ASREPORT [VPRPT, SMERPT, SRVIND]n

o

p

q

r

asreport [ ]

asreport [ ]

sasreport [ ]

t

u

otaspreq [VPRPT, SMERPT]

otaspreq [VPRPT, SMERPT]

AUTHDIR [SRVIND, MSCID, EncryptionParameters]

AUTHDIR [SRVIND, EncryptionParameters]

ASREPORT [VPRPT, SMERPT, SRVIND]

ASREPORT [VPRPT, SMERPT, SRVIND]

ADTADTADT

ASRRT

OTARTcl

OTARTcl

ASRRT

ASRTASRTASRT

Serving System

SMTcm

Home System

SMDPP [SMS_BearerData (Re-Authenticate Request Message), SRVIND]

Re-Authenticate Request Message

Turn on Voice Privacy orSignaling Message Encryption or both

authdir [ ]

authdir [ ]

Figure 6.CC.5 Re-Authentication for Voice Privacy, Message Encryption, or both


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. The OTAF determines that message encryption or voice privacy or both need(s)to be invoked over the air-interface, perhaps from a CSC request. The OTAFencapsulates an air-interface OTASP Data Message (Re-Authenticate RequestMessage) containing the Random Challenge value, RAND (generated at theOTAF), in SMS_BearerData and forwards it in an SMDPP to the ServingMSC.

b. The Serving MSC sends the Re-Authenticate Request Message to the MS overthe air-interface.

c. The MS executes Authentication-Signature Generation Procedure usingRAND, ESN and AUTHDATA. The MS transmits an air-interface OTASPData Message (Re-Authenticate Response Message) to the Serving MSC. (Note:AUTHR, RANDC, COUNT and AUTHDATA are included).

d. The Serving MSC encapsulates the air-interface OTASP Data Message inSMS_BearerData and forwards it in an smdpp to the OTAF.

e. The OTAF sends an OTASPREQ including RAND, AUTHR, COUNT,AUTHDATA, the Serving MSC's value of SYSCAP and the Serving System'sMSCID to the HLR. The MSMIN may be included to facilitate accessing thepermanent subscriber record.

f. The HLR forwards the OTASPREQ to the AC. The MSMIN may be includedto facilitate accessing the permanent subscriber record.

g. The AC determines that the MS has been re-authenticated correctly. Itcomputes the EncryptionParameters and sends them to the HLR in anAUTHDIR.




EncryptionParameters: Encryption Parameters for message encryptionand voice privacy on the air-interface.

[SMEKEY] SMEKEY for message encryption over the air-interface.

R

[CDMAPLCM] CDMAPLCM for voice privacy over the air-interface.

R

h. The HLR determines the VLR address from the MSCID and forwards theAUTHDIR to the VLR. Parameters are the same as in Step g.

i. The VLR determines the MSC address from the MSCID and forwards theAUTHDIR to the Serving MSC. Parameters are the same as in Step g except theMSCID parameter, which is not forwarded.

j. The Serving MSC returns an empty authdir to the VLR, to indicate that thedirective has been accepted.

k. The VLR forwards the authdir to the HLR.

l. The HLR forwards the authdir to the AC.

m. Voice privacy or signaling message encryption or both gets turned on over theair-interface.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

n. The Serving MSC sends an ASREPORT to the VLR indicating in VPRPT andSMERPT the current status of voice privacy and signaling message encryption,respectively, on the air-interface.

o. The VLR forwards the ASREPORT to the HLR.

p. The HLR forwards the ASREPORT to the AC.

q. The AC sends an empty asreport to the HLR.

r. The HLR forwards the asreport to the VLR.

s. The VLR forwards the asreport to the Serving MSC.

t. The AC sends an otaspreq to the HLR, including the VPRPT and SMERPTparameters.

u. The HLR forwards the otaspreq to the OTAF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.6 Exchange of OTASP Data Messages

This scenario describes the use of the SMDPP message to exchange OTASP DataMessages between the OTAF and the MS via the Serving MSC.

SMDPP [SMS_BearerData (OTASP Data Message), SRVIND]

MSCMS

smdpp [SMS_BearerData (OTASP Data Message)]

OTASP Data Message

OTASP Data Message

Serving System

a

b

d

c

OTAF

SMTcx

Figure 6.CC.6 Exchange of OTASP Data Messages

Note: In the above figure, SMTcx = (x=m, l: depending on the mode of MSoperation (if known), the lengths of the OTASP Data Messages being exchanged andthe corresponding response time at the MS). See Section 7 for operation timer valuesin Table 63.

a. The OTAF determines that an OTASP Data Message needs to be sent to theMS (perhaps from a trigger from the CSC). The OTAF encapsulates theOTASP Data Message in SMS_BearerData and forwards it in an SMDPP to theServing MSC.

b. The Serving MSC extracts and sends the OTASP Data Message to the MS overthe air-interface.

c. The MS responds by sending an OTASP Data Message to the Serving MSC.

d. The Serving MSC encapsulates the received OTASP Data Message withinSMS_BearerData and sends it to the OTAF in an smdpp.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.7 AC Request to Commit A-key

This scenario describes the use of the OTASPREQ operation to request the AC tocommit the previously allocated temporary authentication key and, if generated, theassociated SSD.

a

b

OTAF AC

c

d

otaspreq [ ]

HLR

otaspreq [ ]

OTASPREQ [ACTCODE, NEWMIN, MSMIN]

OTASPREQ [ACTCODE, NEWMIN, MSMIN]

OTART cl OTART cl

Figure 6.CC.7 AC Request to Commit A-key

a. The OTAF sends an OTASPREQ to the HLR.


NEWMIN Newly assigned MIN. Include if MIN waschanged during the OTASP session.

O

MSMIN MIN received from the MS at OTASP callorigination.

R

ACTCODE Requests the AC to commit the A-Key. R

b. The HLR forwards the OTASPREQ to the AC.

c. The AC acknowledges the action to the HLR via an empty otaspreq.

d. The HLR forwards the otaspreq to the OTAF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.8 AC Request to Release Resoures

This scenario describes the use of the OTASPREQ operation to request the AC andHLR to release previously allocated resources such as the OTASPCallEntry(possibly containing the temporary authentication key and the associated SSD).

a

b

OTAF AC

OTASPREQ [ACTCODE]

c

d

otaspreq [ ]

HLR

otaspreq [ ]

OTASPREQ [ACTCODE]

OTART csOTART cs

Figure 6.CC.8 AC Request to Release Resources

a. The OTAF sends an OTASPREQ to the HLR with the ActionCode(ACTCODE) parameter set to Release Resources.

b. The HLR releases resources and forwards the OTASPREQ to the AC.

c. The AC releases resources and acknowledges the action to the HLR via anempty otaspreq.

d. The HLR forwards the otaspreq to the OTAF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.9 Registration Following Successful OTASP

This scenario describes registration following a successful OTASP when a new MINis assigned.

The new MIN is transferred to the Serving MSC in an SMDPP operation with theACTCODE instructing the Serving MSC to register the MS. In addition, the ServingMSC is instructed to delete the old MIN from its database and to perform theMSINACT operation with the old MIN1.

OTAFVLR HLR HLR

SMDPP [ACTCODE, NEWMIN, SRVIND]a

b

d

e

c

f

g

h

i

j

Home System

regnot [ ]

MSINACT [DEREG]

smdpp [ ]

MSC

Serving System Old System

REGNOT

RNT

regnot [ ]

RNT

MSIT

MSINACT [DEREG]

msinact [ ]

MSIT

cmSMT

REGNOT

msinact [ ]

Figure 6.CC.9 Registration Following Successful OTASP

1If a successful registration had occured with the old MIN.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

a. After successful OTASP in which a new MIN was assigned to the MS, theOTAF may determine that the Serving System should register the MS with newMIN and that the Serving System should delete information corresponding tothe old MIN and perform the MSINACT operation1.

The OTAF sends to the Serving MSC an SMDPP containing NEWMIN andACTCODE, instructing the Serving MSC to initiate registration.

b. The Serving MSC sends a REGNOT using the NEWMIN value to the VLR.

c. The VLR forwards the REGNOT to the appropriate HLR.

d. The HLR registers the MS and returns a regnot to the VLR.

e. The VLR forwards the regnot to the Serving MSC.

Steps f - i will be initiated only if a successful registration had occurred withthe old MIN.

f. The Serving MSC sends to the VLR containing the old MIN an MSINACT,including a DeregistrationIndicator parameter. The MSC removes all record ofthe old MIN.

g. The VLR, upon receipt of the MSINACT containing the DeregistrationIndicatorparameter, sends an empty msinact to the Serving MSC and removes allrecord of the old MIN.

h. The VLR then sends an MSINACT, including a DeregistrationIndicatorparameter to the old HLR.

i. The old HLR deregisters the MS (i.e. clears the pointer to the VLR) and sendsan empty msinact to the VLR.

j. The Serving MSC sends an smdpp to the OTAF indicating that the actionsspecified in ACTCODE were successfully initiated.

1If successful registration had occurred with the old MIN.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.CC.10 Notification of Newly Assigned MIN Following Successful OTASP

This scenario describes notification of a newly assigned MIN to the MSC following asuccessful OTASP.

The new MIN is transferred to the Serving MSC in an SMDPP operation with theActionCode instructing the Serving MSC to record the MIN. The MSC, then mayperform necessary action associated with the MS and its new MIN. The exactprocedure as to what a MSC should do is vendor definable.

OTAF

SMDPP [ACTCODE, NEWMIN, SRVIND]a

MSC

Serving System

b

SMT cs smdpp [ ]

Figure 6.CC.10 Notification of Newly Assigned MIN Following Successful OTASP

a. After successful OTASP in which a new MIN was assigned to the MS, theOTAF/CSC may determine that the Serving System should be notified of thenewly assigned MIN.

The OTAF sends to the Serving MSC an SMDPP containing the NEWMIN andthe ACTCODE set to Record New MIN.

b. The Serving MSC sends an smdpp to the OTAF indicating that the actionspecified in ACTCODE was initiated.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6C SIGNALING PROTOCOLS - CDMA

This section applies to CDMA OTASP. It provides modifications to IS-41.5-C"Signaling Protocols", for CDMA Over-The-Air Service Provisioning.

Note however, that in the interest of brevity and maintainability, Section 6C.2“Parameters” lists the Parameter Identifier codes for both (CDMA & TDMA)OTASP parameters, and parameters that are common to both (CDMA and TDMA)OTASP, as well as those that are unique to CDMA OTASP. In the correspondingsections on Parameters in the TDMA OTASP portion of this Interim Standard, arelisted those parameters that are unique to TDMA. The TDMA portion points to thisCDMA portion regarding Parameter Identifier codes and parameters common toCDMA and TDMA OTASP.

6C.1 Operations

6C.1.1 General

5.1.2 Signaling Connection Control Part (IS-41.5-C, page 8)

For IS-41 applications, the SCCP is defined in ANSI T1.112, with the followingexceptions and limitations:

• SCCP Class 0 connectionless service is used.

• The message types are Unitdata (UDT) and Unitdata Service (UDTS). TheSCCP shall return a UDTS message when a received UDT message cannotbe delivered to the specified destination and has the return message onerror option set.

• Whether to set the return message on error or discard message on erroroption in the Protocol Class parameter of the UDT message is at thediscretion of the implementation.

• The IS-41 Mobile Application Part has assigned the following SubsystemNumbers (SSN). Use of the following SSN values are recommended:

- 5: Mobile Application Part (MAP)

- 6: Home Location Register (HLR)

- 7: Visitor Location Register (VLR)

- 8: Mobile Switching Center (MSC)

- 9: Equipment Identification Register (EIR) (reserved)1

- 10: Authentication Center (AC)

- 11: Short Message Service (SMS)

- 12: Over-The-Air Service Provisioning Function (OTAF)

1Detailed transactions relative to SSN value 9 are for further study.

Protocols 57 CDMA-OTASP

TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

• In accordance with ANSI T1.112 an SSN shall be included in all messageseven if message routing is based on Global Title Translation (GTT). Thenull SSN (i.e., value 0) should be used when the subsystem is not known(e.g., before a global title translation takes place) per ANSI T1.112.

• Global Title Translation on Mobile Identification Number can be used forcommunication with the HLR. Global Title Indicator type 2 (0010) is used.A translation type value of 3 is used for “MIN to HLR” translation. Theglobal title address information field contains the 10-digit MIN1. Theencoding scheme is BCD. Each address signal is coded as described inSection 3.4.2.3.1 of the ANSI T1.112 specification.

• Global Title Translation on Mobile Identification Number can be used forcommunication with a Message Center. A translation type value of(assignment pending2) is used for Short Message Service for “MIN to MC”translation.

• Use of signaling point codes, global titles, and subsystem numbers mustmeet ANSI T1.112 requirements; such that, any allowable combination ofthese addressing elements is supported. For example, as stated in T1.112.3,Section 3.4.1:

“The address consists of any one or any combination of the following elements:

1) signaling point code,

2) global title (MIN-to-HLR for IS-41),

3) subsystem number,

where, the referenced address is either the called party address or thecalling party address fields in SCCP messages.”

• When an originating functional entity sends an SS7 message with a globaltitle in the SCCP called party address field, the SCCP calling party addressfield should include the point code and subsystem number of the originatingfunctional entity. Note that a Signaling Transfer Point (STP) is consideredto be an intermediate functional entity, not an originating functional entity.

• Replies to messages shall use the received Calling Party Address as theCalled Party Address, in accordance with ANSI T1.112

1Dialed digits must be converted to a 10-digit MIN for the Location Request Taskand Call Data Request Task when Global Title Translation communication with theHLR is used.

2Subsequently, ATIS committee T1S1 assigned translation type 12 for this GTT.

CDMA-OTASP 58 Protocols

TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.4.1.2 Operation Codes (IS-41.5-C, page 21)

The following table lists the IS-41 MAP Operation Codes:

Table 8 IS-41 MAP Operation Codes (concluded)

Operation Name Operation Code

H G F E D C B A Decimal

• • • • • • • • • • • • • •

SMSRequest 0 0 1 1 0 1 1 1 55

OTASPRequest 0 0 1 1 1 0 0 0 56

Other Values Reserved X X X X X X X X • • •

1 1 1 0 0 0 0 0 224

Reserved for Protocol Extension through • • •

1 1 1 1 1 1 1 1 255

6.4.2 Operation Definitions (IS-41.5-C, page 24)

The following table summarizes the operations defined for the IS-41 MAP:

Table 10 Summary of MAP Operations (concluded)

Operation Reference

QualificationDirective 6.4.2.32

• • • • • •

UnsolicitedResponse 6.4.2.54

OTASPRequest 6.4.2.CC

(6.4.2.TT)


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6C.1.2 Modifications to Existing Operations

6.4.2.1 AuthenticationDirective (IS-41.5-C, page 26)

The AuthenticationDirective (AUTHDIR) operation is used to request modification ofan MS’s authentication parameters. It is also used to transport encryption parametersto the Serving MSC for CDMA OTASP.

The AuthenticationDirective operation is initiated with a TCAP INVOKE (LAST).This is carried by a TCAP QUERY WITH PERMISSION package. The ParameterSet is encoded as follows:

Table 11 AuthenticationDirective INVOKE Parameters

AuthenticationDirective INVOKE Parameters Timer: ADT

Field Value Type Reference Notes

Identifier SET [NATIONAL 18] M 6.4.1.2

Length variable octets M 6.4.1.1

Contents

ElectronicSerialNumber M 6.5.2.63

MobileIdentificationNumber M 6.5.2.81 l

AuthenticationAlgorithmVersion O 6.5.2.7 a

AuthenticationResponseUniqueChallenge O 6.5.2.12 b

CallHistoryCount O 6.5.2.18 c

CDMAPrivateLongCodeMask O 6.5.2.36 m

DenyAccess O 6.5.2.54 d

LocationAreaID O 6.5.2.77 e

MobileStationMIN O 6.5.2.oC j

MSCID O 6.5.2.82 n

RandomVariableSSD O 6.5.2.103 f

RandomVariableUniqueChallenge O 6.5.2.104 b

SenderIdentificationNumber O 6.5.2.116 g

ServiceIndicator O 6.5.2.wB k

SharedSecretData O 6.5.2.119 c

SignalingMessageEncryptionKey O 6.5.2.120 m

SSDNotShared O 6.5.2.141 h

UpdateCount O 6.5.2.163 i

Notes:

a. May be included if SharedSecretData parameter is included.

b. Include if the MSC-V shall initiate a Unique Challenge to the MS.

c. Include if the SystemCapabilities include CAVE Execution and ACadministration policies allow distribution of the SSD.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

d. Include if release of system resources allocated for this access may beinitiated by the MSC. This may include disconnection of any call inprogress.

e. May be included from VLR to MSC-V. Usage from the HLR or AC is notdefined.

f. Include if the MSC-V shall initiate an SSD update to the MS.

g. Include to identify the functional entity sending this message.

h. Include if the SSD at the VLR shall be discarded.

i. Include if the MSC-V shall initiate a COUNT Update to the MS.

j. Include for CDMA OTASP to indicate the MIN value currently in the MS’spermanent memory.

k. Include for CDMA OTASP.

l. For CDMA OTASP, contains the Activation_MIN.

m. Include to transport encryption parameters to the Serving MSC.

n. Include to identify Serving System. This parameter is not included whenAuthenticationDirective INVOKE is sent from the VLR to the ServingMSC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.4.2.5 AuthenticationStatusReport (IS-41.5-C, page 33)

The AuthenticationStatusReport (ASREPORT) operation is used to report on theoutcome of an authentication operation initiated by the AC or VLR if SSD is shared.

The AuthenticationStatusReport operation is initiated with a TCAP INVOKE(LAST). This is carried by a TCAP QUERY WITH PERMISSION package. TheParameter Set is encoded as follows:

Table 19 AuthenticationStatusReport INVOKE Parameters

AuthenticationStatusReport INVOKE Parameters Timer: ASRT




Contents


MobileIdentificationNumber M 6.5.2.81 f

SystemCapabilities (Serving) M 6.5.2.146

CountUpdateReport O 6.5.2.52 a

SenderIdentificationNumber O 6.5.2.116 b

ServiceIndicator O 6.5.2.oC e

SignalingMessageEncryptionReport O 6.5.2.xB h

SSDUpdateReport O 6.5.2.142 c

UniqueChallengeReport O 6.5.2.162 d

VoicePrivacyReport O 6.5.2.zB g

Notes:

a. Include if report related to COUNT Update.

b. Include to identify the functional entity sending the message.

c. Include if report related to SSD Update.

d. Include if report related to Unique Challenge.

e. Include for CDMA OTASP.

f. For CDMA OTASP, contains the Activation_MIN.

g. Include to indicate the result of attempting to activate voice privacy on theair-interface.

h. Include to indicate the result of attempting to activate signaling messageencryption on the air-interface.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.4.2.6 BaseStationChallenge (IS-41.5-C, page 35)

The BaseStationChallenge (BSCHALL) operation is used to request a response to aBase Station Challenge Order received from an MS.

The BaseStationChallenge operation is initiated with a TCAP INVOKE (LAST).This is carried by a TCAP QUERY WITH PERMISSION package. The ParameterSet is encoded as follows:

Table 21 BaseStationChallenge INVOKE Parameters

BaseStationChallenge INVOKE Parameters Timer: BSCT




Contents


MobileIdentificationNumber M 6.5.2.81 c

RandomVariableBaseStation M 6.5.2.102

SenderIdentificationNumber O 6.5.2.116 a

ServiceIndicator O 6.5.2.wB b

Notes:

a. Include to identify the functional entity sending the message.

b. Include for CDMA OTASP.

c. For CDMA OTASP, contains the Activation_MIN.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.4.2.14 FeatureRequest (IS-41.5-C, page 47)

Table 38 FeatureRequest RETURN RESULT Parameters

FeatureRequest RETURN RESULT Parameters




Contents

FeatureResult M 6.5.2.67

AccessDeniedReason O 6.5.2.1 a

ActionCode O 6.5.2.2 b

AnnouncementList O 6.5.2.6 c

CallingPartyNumberString1 O 6.5.2.23 d

CallingPartyNumberString2 O 6.5.2.24 d

CallingPartySubaddress O 6.5.2.25 d

CarrierDigits O 6.5.2.28 d

ConferenceCallingIndicator O 6.5.2.49 e

Digits (Dialed) O 6.5.2.58 f

Digits (Destination) O 6.5.2.58 l

DMH_AccountCodeDigits O 6.5.2.59 g

DMH_AlternateBillingDigits O 6.5.2.60 g

DMH_BillingDigits O 6.5.2.61 g

DMH_RedirectionIndicator O 6.5.2.62 d

GroupInformation O 6.5.2.69 h

MobileDirectoryNumber O 6.5.2.80 g

NoAnswerTime O 6.5.2.87 d

OneTimeFeatureIndicator O 6.5.2.88 i

PACAIndicator O 6.5.2.91 j

PilotNumber O 6.5.2.95 h

RedirectingNumberDigits O 6.5.2.107 d

RedirectingNumberString O 6.5.2.108 d

RedirectingSubaddress O 6.5.2.109 d

RoutingDigits O 6.5.2.114 d

TerminationList O 6.5.2.156 k

TerminationTriggers O 6.5.2.159 d

Notes:

a. Include if access is denied. If included, no other optional parameters shallbe included (with the exception of the AnnouncementList parameter).

b. Include if action to be performed is not implied through presence of otherparameters.

c. Include if provision of one or more tones or announcements is required.

d. Include if applicable.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

e. Include to direct that ongoing call be transformed into a Conference Call.

f. Include if digits remain to be analyzed by the MSC (Dialed).

g. Include if applicable and for recording purposes (see DMH),

h. Include for multileg calls.

i. Include if modification to normal feature processing is required for call inprogress.

j. Include to indicate PACA priority level.

k. Include if call routing is required.

l. Include to return a TRN from an OTAF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.4.2.46 SMSDeliveryPointToPoint (IS-41.5-C, page 104)

The SMSDeliveryPointToPoint (SMDPP) operation is used to convey informationfrom one point to another point and report on the success or failure of that transfer(for example, as used in SMS and CDMA OTASP) a short message.

The SMSDeliveryPointToPoint operation is initiated with a TCAP INVOKE(LAST). This is carried by a TCAP QUERY WITH PERMISSION package. TheParameter Set is encoded as follows:

Table 100 SMSDeliveryPointToPoint INVOKE Parameters

SMSDeliveryPointToPoint INVOKE Parameters Timer: SMT




Contents

SMS_BearerData M 6.5.2.124

SMS_TeleserviceIdentifier M 6.5.2.137

ActionCode O 6.5.2.2 i

ElectronicSerialNumber O 6.5.2.63 a

MobileIdentificationNumber O 6.5.2.81 a, m

NewlyAssignedMIN O 6.5.2.rB j

ServiceIndicator O 6.5.2.wB k

SMS_ChargeIndicator O 6.5.2.126 b

SMS_DestinationAddress O 6.5.2.127 c

SMS_MessageCount O 6.5.2.128 d

SMS_NotificationIndicator O 6.5.2.130 e

SMS_OriginalDestinationAddress O 6.5.2.131 f

SMS_OriginalDestinationSubaddress O 6.5.2.132 g

SMS_OriginalOriginatingAddress O 6.5.2.133 h

SMS_OriginalOriginatingSubaddress O 6.5.2.134 g

SMS_OriginatingAddress O 6.5.2.135 c

TemporaryReferenceNumber O 6.5.2.yC l

Notes:

a. Include if known and either the destination is an MS-based SME or theoperation is used for CDMA OTASP.

b. Include if applicable. If not received, charge the message originator.

c. May be included if not carried by the underlying data transport. May requirean interconnection agreement to facilitate interworking between networktypes.

d. Include if applicable. If not received, assume value 0.

e. Include if no notification is necessary. If not received, assume notification isrequested.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

f. Include to indicate whether or not if not the same as the destination address(SMS_DestinationAddress, MobileIdentificationNumber, or the underlyingdata transport destination).

g. Include if applicable.

h. Include if not the same as the originating address (SMS_OriginatingAddressor the underlying data transport originating address).

i. Include for CDMA OTASP if action to be performed is not implied throughpresence of other parameters.

j Include for CDMA OTASP in requests to initiate MSC procedures1 if avalue has been assigned for the MS during the current OTASP session.

k. Include for CDMA OTASP.

l. Include for CDMA OTASP when requesting MSC attachment to the OTAFto provide a correlation between the OTASP voice and data connections.

m. For CDMA OTASP, contains the Activation_MIN.

The SMSDeliveryPointToPoint operation success is reported with a TCAP RETURNRESULT (LAST). This is carried by a TCAP RESPONSE package. The ParameterSet is encoded as follows:

Table 101 SMSDeliveryPointToPoint RETURN RESULT Parameters

SMSDeliveryPointToPoint RETURN RESULT Parameters




Contents

AuthorizationDenied O 6.5.2.13 h

DenyAccess O 6.5.2.54 c

ElectronicSerialNumber O 6.5.2.63 d

MobileStationMIN O 6.5.2.oC e

MSCID O 6.5.2.82 f

SMS_BearerData O 6.5.2.124 a

SMS_CauseCode O 6.5.2.125 b

SystemCapabilities O 6.5.2.146 g

Notes:

a. Include for positive acknowledgments, when applicable.

b. Include for all negative acknowledgments.

c. Include for CDMA OTASP to indicate why the AC has denied service tothis MS.

1The MSC procedures are “Registration Following Successful OTASP” and“Notification of Newly Assigned MIN Following Successful OTASP” in Section 7C.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

d. Include in response to an attachment request, for CDMA OTASP.

e. Include for CDMA OTASP in the response to an attachment request toindicate the MIN value currently in the MS’s permanent memory.

f. Include for CDMA OTASP in the response to an attachment request toidentify the Serving System.

g. Include for CDMA OTASP in the response to an attachment request toidentify the serving system’s authentication capabilities.

h. Include for CDMA OTASP if the HLR had previously denied authorizationto this MS or the registration attempt was unsuccessful.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6C.1.3 New Operations

6.4.2.CC OTASPRequest

The OTASPRequest (OTASPREQ) operation is used by the OTAF to initiate certainAC procedures.

The OTASPRequest operation is initiated with a TCAP INVOKE (LAST). This iscarried by a TCAP QUERY WITH PERMISSION package. The Parameter Set isencoded as follows:

Table 6.4.2.CCx OTASPRequest INVOKE Parameters

OTASPRequest INVOKE Parameters Timer: OTART




Contents

ActionCode O 6.5.2.2 a

AKeyProtocolVersion O 6.5.2.lB b

AuthenticationData O 6.5.2.9 c

AuthenticationResponse O 6.5.2.10 c

CallHistoryCount O 6.5.2.18 c

ElectronicSerialNumber O 6.5.2.63 d

MobileIdentificationNumber O 6.5.2.81 e, d

MobileStationMIN O 6.5.2.oC f

MobileStationPartialKey O 6.5.2.pB g

MSCID O 6.5.2.64 h

NewlyAssignedMIN O 6.5.2.rB i

RandomVariable O 6.5.2.101 c

ServiceIndicator O 6.5.2.wB j

SystemCapabilities O 6.5.2.146 k

Notes:

a. Include to identify action to be performed.

b. Include to identify available version(s) of A-Key Generation procedure(s) atthe MS if the generation of public encryption values is being requested.

c. Received from the MS during CDMA OTASP in the Re-AuthenticateResponse OTASP Data Message. Include for CDMA OTASP for thepurpose of re-authenticating the MS.

d. Include.

e. For CDMA OTASP, contains the Activation_MIN.

f. Include to identify the MS’s MIN value at OTASP call setup.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

g. Include for CDMA OTASP if A-Key is to be generated.

h. Include to identify the Serving System if either SSD Update orReauthentication is being requested.

i. Include for CDMA OTASP if a new MIN has been assigned to the MS (orhas been reserved for assignment) to the MS during the current OTASPsession.

j. Include for CDMA OTASP.

k. Include to identify the serving system’s authentication capabilities.

The OTASPRequest operation success is reported with a TCAP RETURN RESULT(LAST). This is carried by a TCAP RESPONSE package. The Parameter Set isencoded as follows:

Table 6.4.2.CCy OTASPRequest RETURN RESULT Parameters

OTASPRequest RETURN RESULT Parameters




Contents

AKeyProtocolVersion O 6.5.2.lB a

BaseStationPartialKey O 6.5.2.nB b

DenyAccess O 6.5.2.54 c

ModulusValue O 6.5.2.qB b

OTASP_ResultCode O 6.5.2.sB d

PrimitiveValue O 6.5.2.tB b

SignalingMessageEncryptionReport O 6.5.2.xB e

SSDUpdateReport O 6.5.2.142 f

UniqueChallengeReport O 6.5.2.162 f

VoicePrivacyReport O 6.5.2.zB e

Notes:

a. Included to indicate the selected A-Key generation protocol procedure.

b. Include to return Public Encryption Values to the OTAF.

c. Include to convey authentication failure or count mismatch during the Re-Authentication procedure.

d. Include to convey information other than what can be conveyed in theDenyAccess, UniqueChallengeReport, SSDUpdateReport,SignalingMessageEncryptionReport, and the VoicePrivacyReportparameters.

e. Include to convey the values received by the AC in theAuthenticationStatusReport INVOKE during the Re-Authenticationprocedure.

f. Include to convey the values received by the AC in theAuthenticationStatusReport INVOKE during the SSD update procedure.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6C.2 Parameters

6C.2.1 General

6.5.1.2 Parameter Identifiers (IS-41.5-C, page 124)

Table 118 IS-41 MAP Parameter Identifiers (concluded)

Parameter Identifier Name Parameter Identifier CodeH G F E D C B A

Reference(See Notes)

• • • • • • • • •

TDMAVoiceCoder

(last TSB76 assigned identifier)

1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 0 1 0 0

6.5.2.k

AKeyProtocolVersion 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 0 1 0 1

6.5.2.lB

AuthenticationResponse-Reauthentication

1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 0 1 1 0

6.5.2.mT

BaseStationPartialKey 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 0 1 1 1

6.5.2.nB

MobileStationMIN 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 0 0 0

6.5.2.oC

MobileStationPartialKey 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 0 0 1

6.5.2.pB

ModulusValue 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 0 1 0

6.5.2.qB

NewlyAssignedMIN 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 0 1 1

6.5.2.rB

Reserved 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 1 0 0

OTASP_ResultCode 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 1 0 1

6.5.2.sB

PrimitiveValue 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 1 1 0

6.5.2.tB


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

RandomVariable-Reauthentication

1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 0 1 1 1 1 1 1

6.5.2.uT

ReauthenticationReport 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 1 0 0 0 0 0 0

6.5.2.vT

ServiceIndicator 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 1 0 0 0 0 0 1

6.5.2.wB

SignalingMessageEncryption-Report

1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 1 0 0 0 0 1 0

6.5.2.xB

TemporaryReferenceNumber 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 1 0 0 0 0 1 1

6.5.2.yC

VoicePrivacyReport 1 0 0 1 1 1 1 11 0 0 0 0 0 0 10 1 0 0 0 1 0 0

6.5.2.zB

• • • • • • • • •

Notes:

a. Parameters with references ending with a “B” in them, such as "6.5.2.qB"are common to BOTH CDMA and TDMA OTASP.

b. Parameters with references ending with a “C” in them, such as "6.5.2.oC"are unique to CDMA OTASP.

c. Parameters with references ending with a “T” in them, such as "6.5.2.uT"are unique to TDMA OTASP.

Table CCC A-Key Generation Parameter Names - IS-41 and CDMA

IS-41 CDMA

ModulusValue (MODVAL) PARAM_P

PrimitiveValue (PRIMVAL) PARAM_G

MobileStationPartialKey (MSKEY)MS_RESULT

BaseStationPartialKey (BSKEY)BS_RESULT

AKeyProtocolVersion (AKEYPV)A_KEY_P_REV


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6C.2.2 Modifications to Existing Parameters

Existing parameters that are common to CDMA and TDMA OTASP are shown inthe following table.

Table 6C.2.2 Existing Parameters Common to CDMA & TDMA OTASP

Parameter Name Reference

ActionCode § 6.5.2.2 (IS-41.5-C, p-127)

MobileIdentificationNumber § 6.5.2.81 (IS-41.5-C, p-209)

SystemAccessType § 6.5.2.145 (IS-41.5-C, p-289)

Existing parameters that are common to TDMA and CDMA OTASP, and those thathave been modified uniquely for CDMA OTASP are defined below.

6.5.2.2 ActionCode (IS-41.5-C, page 127)

The ActionCode (ACTCODE) parameter specifies the nature of the action (e.g.,disconnect the call) to be performed by the designated functional entity.


Identifier ActionCodeIMPLICIT OCTET STRING

M 6.5.1.2


Contents

H G F E D C B A octet Notes

Action 1

• • • n a

Figure 9 ActionCode parameter

Notes:

a. Ignore extra octets, if received. Send only defined (or significant) octets.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 120 ActionCode value

Action (octet 1)

Bits H G F E D C B A Value Meaning

0 0 0 0 0 0 0 0 0 Not used.0 0 0 0 0 0 0 1 1 Continue processing.0 0 0 0 0 0 1 0 2 Disconnect call.0 0 0 0 0 0 1 1 3 Disconnect call leg.0 0 0 0 0 1 0 0 4 Conference Calling Drop Last Party.0 0 0 0 0 1 0 1 5 Bridge leg(s) to conference call.0 0 0 0 0 1 1 0 6 Drop leg on busy or routing failure.0 0 0 0 0 1 1 1 7 Disconnect all call legs.0 0 0 0 1 0 0 0 8 Attach MSC to OTAF.0 0 0 0 1 0 0 1 9 Initiate RegistrationNotification.0 0 0 0 1 0 1 0 10 Generate Public Encryption values.0 0 0 0 1 0 1 1 11 Generate A-Key.0 0 0 0 1 1 0 0 12 Perform SSD Update procedure.0 0 0 0 1 1 0 1 13 Perform Re-authentication procedure.0 0 0 0 1 1 0 1 14 Release TRN.0 0 0 0 1 1 1 1 15 Commit A-Key.0 0 0 1 0 0 0 0 16 Release Resources (e.g., A-Key).0 0 0 1 0 0 0 1 17 Record NEWMIN.

0 0 0 1 0 0 1 0 18• • • through

0 1 0 1 1 1 1 1 95

Reserved. Treat the same as value 1,Continue processing.

0 1 1 0 0 0 0 0 96• • • through

0 1 1 1 1 1 1 1 127

Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 1,Continue processing.

1 0 0 0 0 0 0 0 128• • • through

1 1 0 1 1 1 1 1 223

Reserved. Treat the same as value 2,Disconnect call.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255

Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 2,Disconnect call.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.81 MobileIdentificationNumber (IS-41.5-C, page 209)

The MobileIdentificationNumber (MIN) is a 10-digit representation of the MS’sMIN, coded in BCD form.


Identifier MobileIdentificationNumberIMPLICIT OCTET STRING

M 6.5.1.2

Length 5 octets M 6.5.1.1

Contents


Digit 2 Digit 1 1 a

Digit 4 Digit 3 2 a

Digit 6 Digit 5 3 a

Digit 8 Digit 7 4 a

Digit 10 Digit 9 5 a

Figure 89 MobileIdentificationNumber parameter

Notes:

a. Digit 1 is the most significant digit and Digit 10 is the least significant digit.

Table 155 MobileIdentificationNumber value

Digit n, where n={0,1, 2, …, 9} (octets 1-5)

Bits H G F Eor D C B A Value Meaning

0 0 0 0 0 Digit = 0 or filler.0 0 0 1 1 Digit = 1.0 0 1 0 2 Digit = 2.0 0 1 1 3 Digit = 3.0 1 0 0 4 Digit = 4.0 1 0 1 5 Digit = 5.0 1 1 0 6 Digit = 6.0 1 1 1 7 Digit = 7.1 0 0 0 8 Digit = 8.1 0 0 1 9 Digit = 9.X X X X - Other values reserved.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


Identifier MobileIdentificationNumberIMPLICIT OCTET STRING

M 6.5.1.2


Contents


MINType 1-5 a

Figure 89 MobileIdentificationNumber parameter

Notes:

a. Refer to the MINType parameter type (see 6.5.3.u1) for a definition of thisparameter.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.125 SMS_CauseCode (IS-41.5-C, page 257)

The SMS_CauseCode (SMS_CC) parameter indicates a reason for not delivering anSMS or OTASP message or indicates certain conditions at the Serving MSC for useduring OTASP.


Identifier SMS_CauseCodeIMPLICIT OCTET STRING

M 6.5.1.2


Contents


SMS Cause Code 1 a

• • • n b

Figure 136 SMS_CauseCode parameter

Notes:

a. Only the SMS_CauseCode SMS delivery postponed is used to indicate thatan SMS message is pending delivery and that notification shall be provided.

b. Ignore extra octets, if received. Send only defined (or significant) octets.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 177 SMS_CauseCode value

SMS Cause Code (octet 1)

A. Network Problems:


0 0 0 0 0 0 0 0 0 Address vacant. SMS Destination Addressis valid but not currently allocated to anSMS terminal. The MIN associated with avalid destination address is not known to itsHLR.

0 0 0 0 0 0 0 1 1 Address translation failure. The SMSDestination Address is invalid (e.g., addressis not a recognized address type, address isnot for a known or possible SMS functionalentity, the MIN associated with adestination MS address does notcorrespond to its HLR, the ESN associatedwith a destination MS does not match theexpected value, the SMS_Destination-Address, SMS_OriginalDestinationAddress,destination MIN, or original destinationsubaddress does not match the address of adestination SME, etc.). For CDMAOTASP, the TRN, the Activation_ MIN, orthe ESN is currently not allocated to anOTASP call, etc.)

0 0 0 0 0 0 1 0 2 Network resource shortage. Networktransmission failed due to lack of a networkresource or link capacity.

0 0 0 0 0 0 1 1 3 Network failure. A network node failed, alink failed or a required operation failed.

0 0 0 0 0 1 0 0 4 Invalid Teleservice ID. TheSMS_TeleserviceIdentifier is not known, isnot supported or is not authorized by anaddressed functional entity.

0 0 0 0 0 1 0 1 5 Other network problem. A networkproblem other than identified above.

0 0 0 0 0 1 1 0 6 Unsupported network interface. Theintersystem network interface required forthe delivery of the received message is notsupported.

0 0 0 0 0 1 1 1 7

• • • through0 0 0 1 1 1 1 1 31

Reserved. Treat the same as value 5, Othernetwork problem.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 177 (continued)


B. Terminal Problems :


0 0 1 0 0 0 0 0 32 No page response. The addressedMS-based SME is known, but it does notrespond to a page. SMS Notification is notpending.

0 0 1 0 0 0 0 1 33 Destination busy. The destinationMS-based SME is SMS capable, but iscurrently engaged in a call, a service or acall mode that precludes the use of SMS orthe destination SME is congested. Thisvalue shall only be used between the MSCand the MC when allowed by bilateralagreement. SMS Notification is notpending.

0 0 1 0 0 0 1 0 34 No acknowledgment. The destinationSME does not acknowledge receipt of theSMS delivery (e.g., SMS or an OTASPData message). This value may be usedwhen terminal busy and no page responseare not appropriate. SMS Notification is notpending.

0 0 1 0 0 0 1 1 35 Destination resource shortage. A requiredterminal resource (e.g., memory, etc.) is notavailable to process this message. SMSnotification is not pending.

0 0 1 0 0 1 0 0 36 SMS delivery postponed. Delivery is notcurrently possible (e.g., No page response,Destination busy, No acknowledgment,Destination out of service, Other terminalproblem), but SMS notification is pending.

0 0 1 0 0 1 0 1 37 Destination out of service. The addresseddestination is out of service for an extendedperiod of time (e.g., MS sleep, inactive,power off). SMS notification is notpending.

0 0 1 0 0 1 1 0 38 Destination no longer at this address.The MS-based SME is no longer at thetemporary SMS routing address. Themessage sender should not re-use thetemporary SMS routing address. SMSnotification is not pending.

0 0 1 0 0 1 1 1 39 Other terminal problem. A terminalproblem other than described above. SMSnotification is not pending.

0 0 1 0 1 0 0 0 40• • • through

0 0 1 0 1 1 1 1 47

Reserved. Treat the same as value 39, Otherterminal problems.

0 0 1 1 0 0 0 0 48• • • through

0 0 1 1 1 1 1 1 63

Reserved. Treat the same as value 36, SMSdelivery postponed.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 177 (continued)


C. Radio Interface Problems :


0 1 0 0 0 0 0 0 64 Radio interface resource shortage. Thereis no channel available or there is radiocongestion at this time.

0 1 0 0 0 0 0 1 65 Radio interface incompatibility. The MSfor an MS-based SME is operating in amode that does not support SMS at thistime. This cause code may also be used toindicate that the air-interface does notsupport OTASP Data Message delivery.

0 1 0 0 0 0 1 0 66 Other radio interface problem. A radiointerface problem to an MS-based SMEother than described above.

0 1 0 0 0 0 1 1 67• • • through

0 1 0 1 1 1 1 1 95

Reserved. Treat the same as value 66, Otherradio interface problem


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 177 (concluded)


D. General Problems :


0 1 1 0 0 0 0 0 96 Encoding problem. The size of aparameter or field is not what is expected.

0 1 1 0 0 0 0 1 97 SMS origination denied The originatingMIN is not recognized, the originatingaddress is not allowed for the originatingMIN, the ESN does not match theoriginating MIN, the origination is notauthorized, the originating address is notrecognized, etc.

0 1 1 0 0 0 1 0 98 SMS termination denied. The destinationis not authorized to receive the SMSmessage, the MC refused the message, thedestination SME refused the message, thedestination is not authorized for a requiredsupplementary service, etc. This cause codemay also be used to indicate that an MSrejected an OTASP Data Message.

0 1 1 0 0 0 1 1 99 Supplementary service not supported.The originating supplementary service isnot known or supported, the sender is notauthorized for an originating supplementaryservice, etc.

0 1 1 0 0 1 0 0 100 SMS not supported. SMS is not supportedby an addressed functional entity.

0 1 1 0 0 1 0 1 101 Reserved.0 1 1 0 0 1 1 0 102 Missing expected parameter An optional

parameter that is required for a particularfunction).

0 1 1 0 0 1 1 1 103 Missing mandatory parameter. Aparameter is missing that is mandatory for aparticular message.

0 1 1 0 1 0 0 0 104 Unrecognized parameter value. A knownparameter has a unknown or unsupportedvalue.

0 1 1 0 1 0 0 1 105 Unexpected parameter value. A knownparameter has a known, but unexpectedvalue.

0 1 1 0 1 0 1 0 106 User Data size error. The User Data sizeis too large for access technology, transportnetwork, or call mode, etc. The User Datasize is not what is expected for theindicated teleservice.

0 1 1 0 1 0 1 7 107 Other general problems.

0 1 1 0 1 1 0 0 108• • • through

1 1 0 1 1 1 1 1 223

Reserved. Treat the same as value 107,Other general problems.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255

Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 107,Other general problems.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.145 SystemAccessType (IS-41.5-C, page 289)

The SystemAccessType (SYSACCTYPE) parameter defines the type of systemaccess made by the MS.


Identifier SystemAccessTypeIMPLICIT OCTET STRING

M 6.5.1.2

Length 1 octet M 6.5.1.1

Contents


System Access Type 1

Figure 160 SystemAccessType parameter

Table 187 SystemAccessType value

System Access Type (octet 1)


0 0 0 0 0 0 0 0 0 Not used.0 0 0 0 0 0 0 1 1 Unspecified.0 0 0 0 0 0 1 0 2 Flash request.0 0 0 0 0 0 1 1 3 Autonomous registration.0 0 0 0 0 1 0 0 4 Call origination.0 0 0 0 0 1 0 1 5 Page response.0 0 0 0 0 1 1 0 6 No access. Used when the authentication

procedure was initiated on the ControlChannel.

0 0 0 0 0 1 1 1 7 Power down registration.0 0 0 0 1 0 0 0 8 SMS page response.0 0 0 0 1 0 0 1 9 OTASP.

0 0 0 0 1 0 1 0 10

• • • through1 1 0 1 1 1 1 1 223

Reserved. Treat the same as value 1,Unspecified.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255

Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 1,Unspecified.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6C.2.3 New Parameters

New parameters that are common to CDMA and TDMA OTASP are shown in thefollowing table.

Table 6C.2.3 New Parameters Common to CDMA & TDMA OTASP

Parameter Name Reference

AKeyProtocolVersion § 6.5.2.lB

BaseStationPartialKey § 6.5.2.nB

MobileStationPartialKey § 6.5.2.pB

ModulusValue § 6.5.2.qB

NewlyAssignedMIN § 6.5.2.rB

OTASPResultCode § 6.5.2.sB

PrimitiveValue § 6.5.2.tB

ServiceIndicator § 6.5.2.wB

SignalingMessageEncryptionReport § 6.5.2.xB

VoicePrivacyReport § 6.5.2.zB

New parameters that are common to TDMA and CDMA OTASP, and those thathave been created uniquely for CDMA OTASP are defined below.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.lB AKeyProtocolVersion

The AKeyProtocolVersion (AKEYPV) parameter is used to send A-Key GenerationProcedure protocol version(s) supported by the MS or selected by the AC.


Identifier AKeyProtocolVersionIMPLICIT OCTET STRING

M 6.5.1.2


Contents


1st A-Key Generation Procedure Protocol Version 1

• • • • • •

nth A-Key Generation Procedure Protocol Version n

Figure lB AKeyProtocolVersion parameter

Table lB AKeyProtocolVersion values

A-Key Generation Procedure Protocol Version values (octets 1-n)


0 0 0 0 0 0 0 0 0 Not used.0 0 0 0 0 0 0 1 1 A-Key Generation not supported.0 0 0 0 0 0 1 0 2 Diffie Hellman with 768-bit modulus,

160-bit primitive, and 160-bit exponents.0 0 0 0 0 0 1 1 3 Diffie Hellman with 512-bit modulus,

160-bit primitive, and 160-bit exponents.

0 0 0 0 0 1 0 0 4• • • through

1 1 0 1 1 1 1 1 223Reserved. Treat the same as value 1, A-Key Generation not supported.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 1, A-Key Generation not supported.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.nB BaseStationPartialKey

The BaseStationPartialKey (BSKEY) parameter is used to send the Base Stationpartial key value for the A-Key Generation procedure.


Identifier BaseStationPartialKeyIMPLICIT OCTET STRING

M 6.5.1.2


Contents


MSB 1

BS partial key value • • •

LSB n a

Figure nB BaseStationPartialKey parameter

Notes:

a. The length of this field corresponds to the AKeyProtocolVersion valueused.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.oC MobileStationMIN

The MobileStationMIN (MSMIN) parameter is used to send the MIN value stored inthe MS’s permanent memory at an OTASP call origination.


Identifier MobileStationMINIMPLICIT MINType

M 6.5.1.2


Contents


MINType 1-5 a

Figure oC MobileStationMIN parameter

Notes:



TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.pB MobileStationPartialKey

The MobileStationPartialKey (MSKEY) parameter is used to send the MS partial keyvalue for the A-Key Generation procedure.


Identifier MobileStationPartialKeyIMPLICIT OCTET STRING

M 6.5.1.2


Contents


MSB 1

MS partial key value • • •

LSB n a

Figure pB MobileStationPartialKey parameter

Notes:



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.qB ModulusValue

The ModulusValue (MODVAL) parameter is used to return the A-Key Generationprocedure modulus value.


Identifier ModulusValueIMPLICIT OCTET STRING

M 6.5.1.2


Contents


MSB 1

Modulus value • • •

LSB n a

Figure qB ModulusValue parameter

Notes:



TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.rB NewlyAssignedMIN

The NewlyAssignedMIN (NEWMIN) parameter contains the MIN that may beassigned following the successful completion of the OTASP process.


Identifier NewlyAssignedMINIMPLICIT MINType

M 6.5.1.2


Contents


MINType 1-5 a

Figure rB NewlyAssignedMIN parameter

Notes:



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.sB OTASP_ResultCode

The OTASP_ResultCode (OTASPRC) parameter is used to specify the result of anOTASP related AC procedure.


Identifier OTASP_ResultCodeIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Result Code 1 a

Figure sB OTASP_ResultCode parameter

Notes:

a. The absence of this parameter or the presence of value 0 (for “Accepted”;see Table sB below) indicates a successful result.

Table sB OTASP_ResultCode value

Result Code (octet 1)


0 0 0 0 0 0 0 0 0 Accepted - Successful.0 0 0 0 0 0 0 1 1 Rejected - Unknown cause.0 0 0 0 0 0 1 0 2 Computation Failure - E.g., unable to

compute A-key.0 0 0 0 0 0 1 1 3 CSC Rejected - CSC challenge failure.0 0 0 0 0 1 0 0 4 Unrecognized OTASPCallEntry.0 0 0 0 0 1 0 1 5 Unsupported AKeyProtocolVersion(s).0 0 0 0 0 1 1 0 6 Unable to Commit.

0 0 0 0 0 1 1 1 7• • • through

1 1 0 1 1 1 1 1 223Reserved. Treat the same as value 1Rejected - Unknown Cause.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 1 Rejected- Unknown Cause.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.tB PrimitiveValue

The PrimitiveValue (PRIMVAL) parameter is used to return the A-Key Generationprocedure primitive value from the AC to the OTAF.


Identifier PrimitiveValueIMPLICIT OCTET STRING

M 6.5.1.2


Contents


MSB 1

Primitive value • • •

LSB n a

Figure tB PrimitiveValue parameter

Notes:



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.wB ServiceIndicator

The ServiceIndicator (SRVIND) parameter indicates a type of service.


Identifier ServiceIndicatorIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Service 1

• • • n a

Figure wB ServiceIndicator parameter

Notes:

a. Ignore extra octets, if received. Send only defined (or significant) octets.

Table wB ServiceIndicator value

Service (octet 1)


0 0 0 0 0 0 0 0 0 Undefined Service.0 0 0 0 0 0 0 1 1 CDMA OTASP Service.0 0 0 0 0 0 1 0 2 TDMA OTASP Service.

0 0 0 0 0 0 1 1 3• • • through

1 1 0 1 1 1 1 1 223Reserved. Treat the same as value 0Undefined Service

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 0Undefined Service


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.xB SignalingMessageEncryptionReport

The SignalingMessageEncryptionReport (SMERPT) parameter indicates theoutcome of the Signaling Message Encryption initiated by the serving MSC.


Identifier SignalingMessageEncryptionReportIMPLICIT OCTET STRING

M 6.5.1.2


Contents


SME Report 1

Figure xB SignalingMessageEncryptionReport parameter

Table xB SignalingMessageEncryptionReport value

SMEReport (octet 1)


0 0 0 0 0 0 0 0 0 Not used0 0 0 0 0 0 0 1 1 Signaling Message Encryption enabling

not attempted.0 0 0 0 0 0 1 0 2 Signaling Message Encryption enabling

no response.0 0 0 0 0 0 1 1 3 Signaling Message Encryption enabling

successful.0 0 0 0 0 1 0 0 4 Signaling Message Encryption enabling

failed.

0 0 0 0 0 1 0 1 5• • • through

1 1 0 1 1 1 1 1 223Reserved. Treat the same as value 1Signaling Message Encryption notattempted.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 1Signaling Message Encryption notattempted.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.yC TemporaryReferenceNumber

The TemporaryReferenceNumber (TRN) parameter is used to correlate the voiceconnection between the MS and CSC with the data connection between the MSC andOTAF, during an OTASP session.


Identifier TemporaryReferenceNumberIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Digit 2 Digit 1 1 a

Digit 4 Digit 3 2 a

• • • • • • • • •

Nth Digit N-1st Digit n a

Figure yC TemporaryReferenceNumber parameter

Notes:

a. Digit 1 is the most significant digit and the Nth Digit is the least significantdigit.

Table yC TemporaryReferenceNumber value

Digit N, where N={1, 2, …,} (octets 1-n)


0 0 0 0 0 Digit = 0.0 0 0 1 1 Digit = 1.0 0 1 0 2 Digit = 2.0 0 1 1 3 Digit = 3.0 1 0 0 4 Digit = 4.0 1 0 1 5 Digit = 5.0 1 1 0 6 Digit = 6.0 1 1 1 7 Digit = 7.1 0 0 0 8 Digit = 8.1 0 0 1 9 Digit = 9.1 1 1 1 15 filler.X X X X - Other values reserved.

Note: For odd number of digits, the Nth digit is set to the filler value.


TIA/EIA IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.2.zB VoicePrivacyReport

The VoicePrivacyReport (VPRPT) parameter indicates the outcome of the VoicePrivacy procedure initiated by the Serving MSC.


Identifier VoicePrivacyReportIMPLICIT OCTET STRING

M 6.5.1.2


Contents


Voice Privacy Report 1

Figure zB VoicePrivacyReport parameter

Table zB VoicePrivacyReport value

VoicePrivacy Report (octet 1)


0 0 0 0 0 0 0 0 0 Not used.0 0 0 0 0 0 0 1 1 Voice Privacy not attempted.0 0 0 0 0 0 1 0 2 Voice Privacy no response.0 0 0 0 0 0 1 1 3 Voiec Privacy successful.0 0 0 0 0 1 0 0 4 Voice Privacy failed.0 0 0 0 0 1 0 1 5

• • • through1 1 0 1 1 1 1 1 223

Reserved. Treat the same as value 1, VoicePrivacy not attempted.

1 1 1 0 0 0 0 0 224• • • through

1 1 1 1 1 1 1 1 255Reserved for IS-41 protocol extension. Ifunknown, treat the same as value 1, VoicePrivacy not attempted.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6.5.3 Parameter Type Definitions

This Section provides the definitions of the parameter types used in this InterimStandard.

6.5.3.u1 MINType

The MINType parameter type is a representation of an MSMobileIdentificationNumber (MIN), coded in BCD form.


Identifier MINTypeMPLICIT OCTET STRING

M 6.5.1.2


Contents


Digit 2 Digit 1 1 a

Digit 4 Digit 3 2 a

Digit 6 Digit 5 3 a

Digit 8 Digit 7 4 a

Digit 10 Digit 9 5 a

Figure u1 MINType parameter type

Notes:

a. Digit 1 is the most significant digit and Digit 10 is the least significant digit.

Table u1 Digit value

Digit n, where n={0,1, 2, …, 9} (octets 1-5)


0 0 0 0 0 Digit = 0 or filler.0 0 0 1 1 Digit = 1.0 0 1 0 2 Digit = 2.0 0 1 1 3 Digit = 3.0 1 0 0 4 Digit = 4.0 1 0 1 5 Digit = 5.0 1 1 0 6 Digit = 6.0 1 1 1 7 Digit = 7.1 0 0 0 8 Digit = 8.1 0 0 1 9 Digit = 9.X X X X - Other values reserved.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

7C SIGNALING PROCEDURES - CDMA

This section applies only to CDMA OTASP. It provides modifications to IS-41.6-C"Signaling Procedures", for CDMA Over-The-Air Service Provisioning.

3.2 Origination Call Tasks

3.2.1 Idle MS Origination (IS-41.6-C, page 12)

When the MS attempts to originate a call, the Serving MSC shall do the following:

1 IF an appropriate idle voice or traffic channel is available for the identified airinterface control channel, the MSC may pre-seize the channel by:

1-1 Reserve the available voice or traffic channel.

1-2 Order the MS to acquire the reserved voice or traffic channel.

1-3 Verify the MS has properly tuned to this voice or traffic channel.

2 ENDIF.

3 IF the MS is not authenticated and authentication is active (AUTH=1 in theOverhead Message Train):

3-1 IF the MS has authentication capabilities:

3-1-1 Include the SystemAccessType parameter set to Call origination.

3-1-2 Execute the “MSC Initiating an Authentication Request” task (see4.4.1).

3-1-3 IF authentication fails AND the OTASP Feature Code (*FC) is notdialed:

3-1-3-1 Execute “Local Recovery Procedures” task (see 3.5.1).

3-1-3-2 Exit this task.

3-1-4 ENDIF.

3-2 ENDIF.

4 ENDIF.

5 IF the MS is not registered OR IF the location of the MS has not changed sincethe last registration:

5-1 Execute the “MSC Initiating MS Registration” task (see 4.38.1).

6 ELSEIF the MSC requires the MS’s service profile (e.g., per call authorizationrequired or the service profile is not present):

6-1 Execute the “MSC Initiating Qualification Request” task (see 4.33.1).

7 ENDIF.

8 Execute “Initialize the OneTimeFeatureIndicator Parameter” task (see 3.2.8).

9 Execute “MSC Analyze MS Dialed Number” task (see 3.2.3).

10 IF the PointOfReturn is ToneTermination:

10-1 Execute “Apply Access Denial Treatment” task (see 3.4.5).

10-2 Exit this task.

Procedures 97 CDMA-OTASP

TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

11 ENDIF.

12 IF the MS is not authorized, and the OTASP feature code (*FC) was not dialed:



13 ENDIF.

14 Execute the “MSC PACA Call Origination Invocation” task (see 5.17.2).

15 IF unsuccessful:


16 ELSE (seize the channel by):

16-1 Reserve the available voice or traffic channel.

16-2 Order the MS to acquire the reserved voice or traffic channel.

16-3 Verify the MS has properly tuned to this voice or traffic channel.

16-4 IF unsuccessful:

16-4-1 Execute “Apply Access Denial Treatment” task (see 3.4.5).

16-5 ENDIF.

17 ENDIF.

18 Execute the “MSC MWN Call Origination Invocation” task (see 5.13.7).

19 ENDIF.

20 IF the AnnouncementList parameter is received:

20-1 Execute the “Play All Announcements in the AnnouncementList” task (see3.2.5).

21 ENDIF.

22 Execute the “MSC Routing Points Of Return” task (see 3.2.6).

22 IF OTASP feature code (*FC) was dialed:

22-1 Include TRN.

22-2 Route the call to the CSC.

23 ELSE:

23-1 Execute the “MSC Routing Points of Return” task (see 3.2.6).

24 ENDIF.

25 Exit this task.

CDMA-OTASP 98 Procedures

TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3.2.3 MSC Analyze MS Dialed Number (IS-41.6-C, Page 15)

Upon demand the Anchor MSC shall do the following:

1 IF flash privileges are suspended (by the Flash Privileges in the OneTime-FeatureIndicator parameter e.g., Call Transfer, Call Waiting, Three-WayCalling):

1-1 Include the TransactionCapability parameter with the number of multipleterminations set to 0.

2 ELSEIF Call Transfer, Three-Way Calling or similar feature is being invoked:

2-1 Include the TransactionCapability parameter with the number of multipleterminations set to 1.

3 ELSE:

3-1 Include the TransactionCapability parameter with the number of multipleterminations set appropriately.

4 ENDIF.

5 IF an OTASP Feature Code (*FC) is received:

5-1 Execute "MSC Obtaining a TRN" task (see 5.C1.1).

5-2 IF unsuccessful indication is received:

5-2-1 Execute "Apply Access Denial Treatment" task (see 3.4.5).

5-2-2 Exit this task.

5-3 ENDIF.

5-4 Associate the TRN with the OTASP Call.

5-5 Execute the "MSC Record the DMH Parameters" task (see 3.3.7)

5-6 IF the MSC administers TRNs itself:

5-6-1 IF the user specified a directory number during OTASP activation andthe directory number is verified by the Serving MSC

5-6-1-1 The Called Party Number for the CSC is the directory numberspecified by the user during the OTASP activation.

5-6-2 ELSE:

5-6-2-1 The Called Party Number for the CSC is determined at the MSC. Itmay correcpond to the TRN.

5-6-3 ENDIF.

5-7 ELSE:

5-7-1 The Called Party Number for the CSC is the TRN, returned above inthe "MSC Obtaining a TRN" task (see 5.C1.1).

5-8 ENDIF.

5-9 Return TRN to the Calling Task.


6 ENDIF.

7 IF the MS dialed a locally allowed number (e.g., 9-1-1, *-9-1-1, N11, *N11):

...........

29 Return to the calling task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.1 Authentication Directive

4.1.1 AC Initiation of an Authentication Directive (IS-41.6-C, page 42)

When an AC determines that the authentication parameters associated with an MSmust be changed, it shall start the authentication directive process. For example, theauthentication parameters may be changed due to AC administrative procedures,when an authentication abnormality is detected or periodically.

The AC shall perform the following:

1 Include the ElectronicSerialNumber parameter set to identify the MS.

2 Include the MobileIdentificationNumber parameter set to identify the MS.

3 IF the ServiceIndicator parameter set to the CDMA OTASP Service value isreceived:

3-1 Relay the ServiceIndicator parameter.

3-2 Relay the MobileStationMIN parameter.

3-3 Set the MobileIdentificationNumber to the received Activation_MIN value.

4 ENDIF.

5 IF SharedSecretData (SSD) presently shared with the VLR shall be discarded:

5-1 Include the SSDNotShared (NOSSD) parameter.

6 ENDIF.

7 IF an SSD update shall be initiated:

7-1 Select a RandomVariableSSD (RANDSSD) and execute CAVE using thevalue of the MS’s A-Key recorded in the AC’s database to produce apending SSD (for CDMA OTASP the A-Key may have been recorded inthe OTASPCallEntry and, if the OTASPCallEntry is present, the pendingSSD shall be stored under it).

7-2 Include the RandomVariableSSD (RANDSSD) parameter.

7-3 Mark the MS pending SSD update.

7-4 IF AC administrative procedures indicate that the pending SSD shall beshared with the VLR for the SSD update operation AND IF theServiceIndicator parameter set to the CDMA OTASP service value is notincluded:

7-4-1 IF the VLR’s SystemCapabilities (SYSCAP) indicates that the VLR isable to execute the CAVE algorithm:

7-4-1-1 Include the SharedSecretData (SSD) parameter set to the pendingSSD value.

7-4-1-2 IF the AuthenticationAlgorithmVersion (AAV) parameter for thisMS is different than the default value:

7-4-1-2-1 Include the AuthenticationAlgorithmVersion (AAV)parameter.

7-4-1-3 ENDIF.

7-4-2 ENDIF.

7-5 ELSE (the SharedSecretData (SSD) is not to be shared):


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

7-5-1 Select a RandomVariableUniqueChallenge (RANDU) and executeCAVE using the value of the pending SSD to produce anAuthenticationResponseUnique (AUTHU) (For CDMA OTASP theSSD may have been stored in the OTASPCallEntry and theAuthenticationData (AUTHDATA) is derived from theMobileStationMIN (MSMIN) received from the OTAF).

7-5-2 Include the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters.

7-5-3 Mark the MS pending Unique Challenge.

7-6 ENDIF.

8 ELSE (SSD update not initiated):

8-1 IF the SharedSecretData (SSD) shall be shared with the VLR:

8-1-1 IF the VLR’s SystemCapabilities (SYSCAP) indicates the VLR iscapable of executing the CAVE algorithm:

8-1-1-1 Include the SharedSecretData (SSD) and CallHistoryCount(COUNT) parameters.

8-1-1-2 IF the AuthenticationAlgorithmVersion (AAV) parameter for thisMS is different than the default value.

8-1-1-2-1 Include the AuthenticationAlgorithmVersion (AAV)parameter.

8-1-1-3 ENDIF.

8-1-2 ENDIF.

8-2 ENDIF.

8-3 IF a Unique Challenge shall be initiated:

8-3-1 Select a RandomVariableUniqueChallenge (RANDU) and executeCAVE using the value of the MS’s SharedSecretData (SSD) recordedin the AC’s database to produce an AuthenticationResponseUnique(AUTHU).

8-3-2 Include the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters.

8-3-3 Mark the MS pending Unique Challenge.

8-4 ENDIF.

9 ENDIF.

10 IF a COUNT update shall be initiated:

10-1 Include the UpdateCount (UPDCOUNT) parameter.

10-2 Mark the MS pending COUNT update.

11 ENDIF.

12 IF the ServiceIndicator parameter set to CDMA OTASP service value, and theActionCode parameter set to Perform Re-Authentication are received:

12-1 Generate CDMAPrivateLongCodeMask (CDMAPLCM) andSignalingMessageEncryptionKey (SMEKEY)

12-2 Include the CDMAPLCM and SMEKEY parameters.

12-3 Mark the MS pending Voice Privacy Status Report and Signaling MessageEncryption Status Report .


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

13 ENDIF.

14 Send an AuthenticationDirective INVOKE to the HLR associated with the MS.

15 Start the Authentication Directive Timer (ADT).

16 WAIT for an Authentication Directive response:

17 WHEN a RETURN RESULT is received:

17-1 Stop timer (ADT).

17-2 IF the message can be processed:

17-2-1 IF the MS is marked pending SSD update, OR IF the MS is markedpending Unique Challenge, OR IF the MS is marked pending COUNTupdateOR IF the MS is marked pending Voice Privacy StatusReportOR IF the MS is marked pending Signaling Message EncryptionReport

17-2-1-1 Execute the “AC Awaiting AuthenticationStatusReport INVOKE”task (see 4.5.4).

17-2-1-2 For CDMA OTASP, relay any received indicators and parametersto the invoking task.

17-2-2 ENDIF.


17-3 ELSE (the message cannot be processed):

17-3-1 IF the MS is marked pending SSD update:

17-3-1-1 IF the MS’s pending SSD is stored in the AC’s database.

17-3-1-1-1 Remove the pending SSD from the AC’s database.

17-3-1-2 ENDIF.

17-3-2 ENDIF.

17-3-3 Clear all the MS’s pending operation flags.

17-3-4 Execute the “Local Recovery Procedures” task (see 3.5.1).

17-3-5 IF the invoking task is related to CDMA OTASP:

17-3-5-1 Indicate failure to the calling task.

17-3-6 ENDIF.

17-4 Return to the invoking process.

17-5 ENDIF.

18 WHEN a RETURN ERROR or REJECT is received:

18-1 Stop timer (ADT).

18-2 IF the MS is marked pending SSD update:

18-2-1 IF the MS’s pending SSD is stored in the AC’s database.

18-2-2 Remove the pending SSD from the AC’s database.

18-2-3 ENDIF.

18-3 ENDIF.

18-4 Clear all the MS’s pending operation flags.

18-5 Execute the “Local Recovery Procedures” task (see 3.5.1).



18-5-2 ENDIF.



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

19 WHEN timer (ADT) expires:


19-1-1 IF the MS’s pending SSD is stored in the AC’s database.

19-1-1-1 Remove the pending SSD from the AC’s database.

19-1-2 ENDIF.

19-2 ENDIF.





19-4-2 ENDIF.


20 ENDWAIT.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.1.2 HLR Receiving AuthenticationDirective INVOKE (IS-41.6-C, page 44)

When an HLR receives an AuthenticationDirective INVOKE, it shall perform thefollowing:

1 IF the received message can be processed:

1-1 Include the SenderIdentificationNumber set to the identification number ofthe HLR.

1-2 Relay all other received parameters.

1-3 Send an AuthenticationDirective INVOKE to the VLR currently serving theMS.

1-4 Start the Authentication Directive Timer (ADT).

1-5 WAIT for an Authentication Directive response:

1-6 WHEN a RETURN RESULT is received:

1-6-1 Stop timer (ADT).

1-6-2 IF the message can be processed:

1-6-2-1 Relay all received parameters.

1-6-2-2 Send a RETURN RESULT to the requesting AC.


1-6-3 ELSE (the message cannot be processed):

1-6-3-1 Send a RETURN ERROR to the requesting AC.

1-6-3-2 Execute the “Local Recovery Procedures” task (see 3.5.1).


1-6-4 ENDIF.

1-7 WHEN a RETURN ERROR or REJECT is received:

1-7-1 Stop timer (ADT).

1-7-2 CASE Error Code OF:

1-7-3 ParameterError:

1-7-3-1 IF the parameter was originated from the initiating functionalentity:

1-7-3-1-1 Send a RETURN ERROR with Error Code set to indicateParameterError.

1-7-3-2 ELSE:

1-7-3-2-1 Send a RETURN ERROR with Error Code set to indicateSystemFailure.

1-7-3-3 ENDIF.

1-7-4 OperationSequenceProblem:

1-7-4-1 Send a RETURN ERROR with Error Code set to indicateOperationSequenceProblem.

1-7-5 DEFAULT:

1-7-5-1 Send a RETURN ERROR with Error Code set to indicateSystemFailure.

1-7-6 ENDCASE.



1-8 WHEN timer (ADT) expires:


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

1-8-1 Send a RETURN ERROR with Error Code set to indicateSystemFailure.



1-9 ENDWAIT.

2 ELSE (the received message cannot be processed):

2-1 Send a RETURN ERROR with the proper Error Code value (see thefollowing table) to the requesting AC.

3 ENDIF.

4 Exit this task.

Table 1 HLR AuthenticationDirective Response

Problem Detection and Recommended Response from HLR to AC

PROBLEM DEFINITION 1 2 3 4 5 6 7 8 9 10 11 Notes

RETURN ERRORError Code

UnrecognizedMIN X e

UnrecognizedESN X e

MIN/HLRMismatch X

OperationSequenceProblem X e

ResourceShortage X e

OperationNotSupported X b, e

TrunkUnavailable a

ParameterError X d, e

SystemFailure X e

UnrecognizedParameterValue X d, e

FeatureInactive a

MissingParameter X d, e

RETURN RESULT X c, e

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported, by the receiving HLR,

or the requesting functional entity is not authorized.2. A required HLR resource (e.g., internal memory record, HLR is fully occupied) is temporarily

not available (e.g., congestion).3. A required resource (e.g., data base access, functional entity) is not presently accessible due to

a failure. Human intervention may be required for resolution.4. A supplied parameter value has an encoding problem (e.g., The supplied

MobileIdentificationNumber parameter digit values do not meet the BCD specification).5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used).6. The supplied MobileIdentificationNumber parameter is not in the HLR’s range of MINs or

directory numbers (suspect routing error).7. The supplied MobileIdentificationNumber parameter is within the range of the HLR, but the

MIN is not Authentication capable or authorized.8. An optional parameter required by the HLR was expected, but not received (e.g., only

MobileIdentificationNumber and ElectronicSerialNumber parameters received).9. The supplied MobileIdentificationNumber parameter is within the range of the HLR, but the

supplied ElectronicSerialNumber parameter is not valid for the MIN’s authentication record.10. The HLR has another Authentication process in-progress for the supplied

MobileIdentificationNumber parameter.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

11. The HLR supports Authentication, but it does not support the requested Authentication feature(e.g., Count updates, Sharing secret data), initiate an AuthenticationStatusReport INVOKE.

Notes:a. This Error Code is not an appropriate HLR response to an AuthenticationDirective

transaction.b. It is recommended that an HLR supports AuthenticationDirective transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.e. This response may have been originated by the VLR (MSC).


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.1.3 VLR Receiving AuthenticationDirective INVOKE (IS-41.6-C, page 47)

When a VLR receives an AuthenticationDirective INVOKE, it shall perform thefollowing:


1-1 IF the SSDNotShared (NOSSD) parameter is received:

1-1-1 Remove the MS’s current SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’s database.

1-2 ENDIF.

1-3 IF the ServiceIndicator parameter set to the CDMA OTASP Service value isreceived:

1-3-1 Create an OTASPCallEntry if one does not already exist.

1-3-2 IF the OTASPCallEntry could not be created:

1-3-2-1 Send a RETURN ERROR with the Error Code indicating SystemFailure.


1-3-3 ELSE:

1-3-3-1 Store the address of the HLR.

1-3-4 ENDIF.

1-4 ENDIF.

1-5 IF the RandomVariableSSD (RANDSSD) parameter is received:

1-5-1 IF the ServiceIndicator parameter set to the CDMA OTASP Servicevalue is received:

1-5-1-1 IF the SharedSecretData (SDD) parameter is received:

1-5-1-1-1 Send a RETURN ERROR with the Error Code indicatingOperationSequenceProblem.

1-5-1-1-2 Exit this task.

1-5-1-2 ENDIF

1-5-1-3 Relay the ServiceIndicator parameter.

1-5-2 ENDIF

1-5-3 IF SharedSecretData (SSD) is shared:

1-5-3-1 Remove the MS’s current SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’s database.

1-5-4 ENDIF.

1-5-5 Relay the received RandomVariableSSD (RANDSSD) parameter.

1-5-6 Mark the MS pending SSD update.

1-5-7 IF the SharedSecretData (SSD) parameter is received:

1-5-7-1 Store the pending SharedSecretData (SSD) value.

1-5-7-2 IF the AuthenticationAlgorithmVersion (AAV) parameter isreceived:

1-5-7-2-1 Store the received AuthenticationAlgorithmVersion (AAV)value.

1-5-7-3 ENDIF.

1-5-7-4 IF the CallHistoryCount (COUNT) parameter is received:


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

1-5-7-4-1 Store the received CallHistoryCount (COUNT) value.

1-5-7-5 ENDIF.

1-5-7-6 Select a RandomVariableUniqueChallenge (RANDU) and executeCAVE using the value of the pending SSD to produce anAuthenticationResponseUnique (AUTHU)(For CDMA OTASP,AuthenticationData (AUTHDATA) is derived from receivedMobileStationMIN (MSMIN) .

1-5-7-7 Include the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters.

1-5-7-8 Mark the MS pending Unique Challenge.

1-5-8 ELSE (pending SSD is not shared):

1-5-8-1 Relay the RandomVariableUniqueChallenge (RANDU) parameter.

1-5-8-2 Relay the AuthenticationResponseUnique (AUTHU) parameter.


1-5-9 ENDIF.

1-6 ELSE (an SSD update is not requested by the AC):

1-6-1 IF the SharedSecretData (SSD) parameter is received:

1-6-1-1 Store the received pending SharedSecretData (SSD).

1-6-1-2 IF the AuthenticationAlgorithmVersion (AAV) parameter isreceived:

1-6-1-2-1 Store the AuthenticationAlgorithmVersion (AAV) value.

1-6-1-3 ENDIF.

1-6-1-4 IF the CallHistoryCount (COUNT) parameter is received:

1-6-1-4-1 Store the received CallHistoryCount (COUNT) value.

1-6-1-5 ENDIF.

1-6-2 ENDIF.

1-6-3 IF the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters are received:

1-6-3-1 Relay the received RandomVariableUniqueChallenge (RANDU)and AuthenticationResponseUnique (AUTHU) parameters.


1-6-4 ENDIF.

1-7 ENDIF.

1-8 IF the UpdateCount (UPDCOUNT) parameter is received:

1-8-1 Relay the received UpdateCount (UPDCOUNT) parameter.

1-8-2 Mark the MS pending COUNT update.

1-9 ENDIF.

1-10 Optionally include the LocationAreaID parameter.

1-11 IF CDMAPLCM parameter is received:

1-11-1 Relay the received CDMAPLCM parameter.

1-11-2 Mark the MS pending Voice Privacy Status Report.

1-12 ENDIF

1-13 IF SMEKEY parameter is received:

1-13-1 Relay the received SMEKEY parameter.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

1-13-2 Mark the MS pending Signaling Message Encryption Status Report.

1-14 ENDIF

1-15 IF the MS is not marked pending SSD update, AND IF the MS is notmarked pending Unique Challenge, AND IF the MS is not marked pendingCOUNT update AND IF the MS is not marked pending Voice PrivacyStatus Report AND IF the MS is not marked pending Signaling MessageEncryption Status Report :

1-15-1 IF the CallHistoryCount (COUNT) is available:

1-15-1-1 Include the CallHistoryCount (COUNT) parameter.

1-15-2 ENDIF.

1-15-3 Send an AuthenticationDirective RETURN RESULT to the requestingHLR.


1-16 ELSE (the MS is marked pending SSD update, OR the MS is markedpending Unique Challenge, OR the MS is marked pending COUNT updateOR the MS is marked pending Voice Privacy Status Report OR IF the MS ismarked pending Signaling Message Encryption Status Report ):

1-16-1 Include the SenderIdentificationNumber set to the identificationnumber of the VLR.

1-16-2 Send an AuthenticationDirective INVOKE to the MSC currentlyserving the MS.

1-16-3 Start the Authentication Directive Timer (ADT).

1-16-4 WAIT for an Authentication Directive response:

1-16-5 WHEN a RETURN RESULT is received:

1-16-5-1 Stop timer (ADT).

1-16-5-2 IF the message can be processed:

1-16-5-2-1 Relay all received parameters.

1-16-5-2-2 IF the CallHistoryCount (COUNT) is received:

1-16-5-2-2-1 Include the CallHistoryCount (COUNT) parameter.

1-16-5-2-3 ENDIF.

1-16-5-2-4 Send a RETURN RESULT to the requesting HLR.

1-16-5-2-5 Execute the “VLR Awaiting AuthenticationStatusReportINVOKE” task (see 4.5.2).


1-16-5-3 ELSE (the message cannot be processed):

1-16-5-3-1 Send a RETURN ERROR to the requesting HLR.

1-16-5-3-2 IF the MS is marked pending SSD update:

1-16-5-3-2-1 IF the pending SSD is stored in the VLR’s database:

1-16-5-3-2-1-1 Remove the MS’s pending SSD andAuthenticationAlgorithmVersion (AAV) from theVLR’s database.

1-16-5-3-2-2 ENDIF.

1-16-5-3-3 ENDIF.

1-16-5-3-4 Clear all the MS’s pending operation flags.

1-16-5-3-5 Execute “Local Recovery Procedures” task (see 3.5.1).



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

1-16-5-4 ENDIF.

1-16-6 WHEN a RETURN ERROR or REJECT is received:

1-16-6-1 Stop timer (ADT).

1-16-6-2 CASE Error Code OF:

1-16-6-3 ParameterError:

1-16-6-3-1 IF the parameter was originated from the initiating functionalentity:

1-16-6-3-1-1 Send a RETURN ERROR with the Error Code indicatingParameterError.

1-16-6-3-2 ELSE:

1-16-6-3-2-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure.

1-16-6-3-3 ENDIF.

1-16-6-4 OperationSequenceProblem:


1-16-6-5 DEFAULT:

1-16-6-5-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure.

1-16-6-6 ENDCASE.

1-16-6-7 IF the MS is marked pending SSD update:

1-16-6-7-1 IF the pending SSD is stored in the VLR’s database:

1-16-6-7-1-1 Remove the MS’s pending SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’sdatabase.

1-16-6-7-2 ENDIF.

1-16-6-8 ENDIF.

1-16-6-9 Clear all the MS’s pending operation flags.



1-16-7 WHEN timer (ADT) expires:

1-16-7-1 Send a RETURN ERROR with the Error Code set to indicateSystemFailure.

1-16-7-2 IF the MS is marked pending SSD update:

1-16-7-2-1 IF the pending SSD is stored in the VLR’s database:

1-16-7-2-1-1 Remove the MS’s pending SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’sdatabase.

1-16-7-2-2 ENDIF.

1-16-7-3 ENDIF.



1-16-8 ENDWAIT.

1-17 ENDIF.


2-1 Send a RETURN ERROR to the requesting HLR.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3 ENDIF.

4 Exit this task.

Table 2 VLR AuthenticationDirective Response

Problem Detection and Recommended Response from VLR to HLR



UnrecognizedMIN X eUnrecognizedESN X eMIN/HLRMismatch aOperationSequenceProblem X eResourceShortage X eOperationNotSupported X b, eTrunkUnavailable aParameterError X d, eSystemFailure X eUnrecognizedParameterValue X d, eFeatureInactive aMissingParameter X d, e

RETURN RESULT X X c, e

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported, by the receiving VLR,

or the requesting functional entity is not authorized.2. A required VLR resource (e.g., internal memory record, VLR is fully occupied) is temporarily



MobileIdentificationNumber parameter digit values do not meet the BCD specification).5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used).6. A VLR record does not presently exist for the supplied MobileIdentificationNumber

parameter.7. An optional parameter required by the VLR was expected, but not received (e.g., only

MobileIdentificationNumber and ElectronicSerialNumber parameters received). A receivedoptional parameter required the VLR to expect an additional optional parameter that was notreceived (e.g., RandomVariableSSD (RANDSSD) and SharedSecretData (SSD) orRandomVariableSSD (RANDSSD), RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU)).

8. A VLR record exists for the supplied MobileIdentificationNumber parameter, but the suppliedElectronicSerialNumber parameter does not match the ESN in the VLR record.

9. The VLR has another Authentication process in-progress for the suppliedMobileIdentificationNumber parameter.

10. The VLR supports Authentication, but it does not support the requested Authentication feature(e.g., Count updates, Sharing secret data), initiate an AuthenticationStatusReport INVOKE.

11. The VLR supports Authentication, SSD is not presently being shared for the suppliedMobileIdentificationNumber parameter, thus the VLR did not expect to receive aSSDNotShared (NOSSD) parameter.

Notes:a. This Error Code is not an appropriate VLR response to an AuthenticationDirective

transaction.b. It is recommended that an VLR supports AuthenticationDirective transactions.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.e. This response may have been originated by the MSC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.1.6 MSC Receiving Authentication Parameters (IS-41.6-C, page 53)

When an MSC receives authentication parameters, the Serving MSC shall performthe following for the specified MS:

1 IF the DenyAccess parameter is received:

1-1 IF the indicated MS is involved in a call or service operation anchored bythis MSC, and the call is not an OTASP call:

1-1-1 The Serving MSC may optionally discontinue the call or serviceoperation currently in progress.

1-2 ENDIF.

1-3 Return to the calling task.

2 ENDIF.

3 IF the RandomVariableSSD (RANDSSD) parameter is received (an SSD updateis requested):

3-1 IF the MS is involved in a call and has been handed off to another MSC:

3-1-1 Include the SSDUpdateReport parameter set to indicate SSD update notattempted.

3-1-2 Execute the “MSC Initiating an Authentication Status Report” task (see4.5.1).

3-1-3 Return to the invoking process.

3-2 ELSEIF the SSD update cannot be attempted:

3-2-1 Include the SSDUpdateReport parameter set to indicate SSD update notattempted.



3-3 ELSE (SSD update can be attempted):

3-3-1 Send an SSD update order to the MS using the RandomVariableSSD(RANDSSD) value received.

3-3-2 IF a Base Station Challenge order is not received from the MS:

3-3-2-1 Include the SSDUpdateReport parameter set to indicate SSDupdate no response.

3-3-2-2 Execute the “MSC Initiating an Authentication Status Report” task(see 4.5.1).

3-3-2-3 Return to the invoking process.

3-3-3 ELSE (Base Station Challenge order is received from the MS):

3-3-3-1 Execute the “MSC Initiating a Base Station Challenge” task (see4.6.1) using the value of RandomVariableBaseStation (RANDBS)provided by the MS.

3-3-3-2 IF the SSD update fails, the MSC shall:

3-3-3-2-1 Include the SSDUpdateReport parameter set to indicate SSDupdate failed.

3-3-3-2-2 Execute the “MSC Initiating an Authentication Status Report”task (see 4.5.1).

3-3-3-2-3 Return to the invoking process.

3-3-3-3 ELSE (SSD update successful):

3-3-3-3-1 (Continue this task.)


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-3-3-4 ENDIF.

3-3-4 ENDIF.

3-4 ENDIF.

4 ENDIF.

5 IF the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters are received (a UniqueChallenge is requested):


5-1-1 Include the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters received.

5-1-2 Execute the “MSC Initiating an Authentication Directive Forward” task(see 4.2.1).

5-1-3 IF the Unique Challenge was not attempted:

5-1-3-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge not attempted.

5-1-3-2 IF an SSD update was performed:

5-1-3-2-1 Include the SSDUpdateReport parameter set to indicate SSDupdate successful.

5-1-3-3 ENDIF.

5-1-3-4 Execute the “MSC Initiating an Authentication Status Report” (see4.5.1) task.


5-1-4 ELSEIF there was no response to the Unique Challenge:

5-1-4-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge no response.



5-1-4-3 ENDIF.



5-1-5 ELSEIF the Unique Challenge failed:

5-1-5-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge failed.



5-1-5-3 ENDIF.



5-1-6 ELSE (Unique Challenge successful):

5-1-6-1 (Continue this task.)

5-1-7 ENDIF.

5-2 ELSEIF the Unique Challenge cannot be attempted:


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5-2-1 Include the UniqueChallengeReport parameter set to indicate UniqueChallenge not attempted.

5-2-2 IF an SSD update was performed:

5-2-2-1 Include the SSDUpdateReport parameter set to indicate SSDupdate successful.

5-2-3 ENDIF.

5-2-4 Execute the “MSC Initiating an Authentication Status Report” (see4.5.1) task.


5-3 ELSE (Unique Challenge can be attempted):

5-3-1 Send a Unique Challenge order to the MS using theRandomVariableUniqueChallenge (RANDU) value received.

5-3-2 IF the MS does not respond to the Unique Challenge Order:

5-3-2-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge no response.



5-3-2-3 ENDIF.



5-3-3 ENDIF.

5-3-4 IF the AuthenticationResponseUnique (AUTHU) response from theMS is not equal to the AuthenticationResponseUnique (AUTHU) valuereceived from the VLR:

5-3-4-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge failed.



5-3-4-3 ENDIF.



5-3-5 ELSE (Unique Challenge successful):


5-3-6 ENDIF.

5-4 ENDIF.

6 ENDIF.

7 IF a COUNT update is requested by the VLR:


7-1-1 Include the CountUpdateReport parameter set to indicate Count Updatenot attempted.




TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

7-1-3 ENDIF.

7-1-4 IF a Unique Challenge was performed:

7-1-4-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge successful.

7-1-5 ENDIF.



7-2 ELSEIF the COUNT update cannot be attempted:

7-2-1 Include the CountUpdateReport parameter set to indicate Count Updatenot attempted.



7-2-3 ENDIF.

7-2-4 IF a Unique Challenge was performed:

7-2-4-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge successful.

7-2-5 ENDIF.



7-3 ELSE (COUNT update can be attempted):

7-3-1 Send a Parameter Update order to the MS using theRandomVariableUniqueChallenge (RANDU) value received.

7-3-2 IF the MS does not respond to the Parameter Update order:

7-3-2-1 Include the CountUpdateReport parameter set to indicate CountUpdate no response.



7-3-2-3 ENDIF.

7-3-2-4 IF a Unique Challenge was performed:

7-3-2-4-1 Include the UniqueChallengeReport parameter set to indicateUnique Challenge successful.

7-3-2-5 ENDIF.

7-3-2-6 Execute the “MSC Initiating an Authentication Status Report” task(see 4.5.1).


7-3-3 ELSE (COUNT update successful):


7-3-4 ENDIF.

7-4 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

8 ENDIF.

9 IF the CDMAPrivateLongCodeMask (CDMAPLCM) ORSignalingMessageEncryptionKey (SMEKEY) is received:

9-1 Initiate Voice Privacy and Signaling Message Encryption over the air-interface, per the Serving MSC’s capabilities.

9-2 Include the VoicePrivacyReport and theSignalingMessageEncryptionReport parameters set to appropriate values.

9-3 Execute the "MSC Initiating an Authentication Status Report" task (see4.5.1)


10 ENDIF.

11 IF an SSD update was performed OR IF a Unique Challenge was performed ORIF a COUNT update was performed:

11-1 IF an SSD update was performed:

11-1-1 Include the SSDUpdateReport parameter set to indicate SSD updatesuccessful.

11-2 ENDIF.

11-3 IF a Unique Challenge was performed:

11-3-1 Include the UniqueChallengeReport parameter set to indicate UniqueChallenge successful.

11-4 ENDIF.

11-5 IF a COUNT update was performed:

11-5-1 Include the CountUpdateReport parameter set to indicate COUNTupdate successful.

11-6 ENDIF.

11-7 Execute the “MSC Initiating an Authentication Status Report” task (see4.5.1).


12 ELSE:


13 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.5 Authentication Status Report

4.5.1 MSC Initiating an Authentication Status Report (IS-41.6-C, Page 92)

When an MSC determines that an Authentication Status Report is necessary to reportthe outcome of authentication operations requested by the VLR, it shall perform thefollowing:

1 IF the outcome of an SSD update shall be reported:

1-1 Include the SSDUpdateReport parameter set to the value indicated by thecalling task.

2 ENDIF.

3 IF the outcome of a Unique Challenge shall be reported:

3-1 Include the UniqueChallengeReport parameter set to the value indicated bythe calling task.

4 ENDIF.

5 IF the outcome of a COUNT update shall be reported:

5-1 Include the CountUpdateReport parameter set to the value indicated by thecalling task.

6 ENDIF.

7 IF the outcome of the enabling of CDMA Voice Privacy shall be reported:

7-1 Include VoicePrivacyReport parameter received from the calling task.

8 ENDIF.

9 IF the outcome of the enabling of CDMA Signaling Message Encryption shallbe reported:

9-1 Include SignalingMessageEncryptionReport parameter received from thecalling task.

10 ENDIF.

11 Include the SenderIdentificationNumber set to the identification number of thesending functional entity.

12 Include the SystemCapabilities (SYSCAP) parameter indicating whetherauthentication parameters were requested for this system access.

13 IF the MS is in a call and the call was originated using an OTASP Feature Code(*FC):

13-1 Include the ElectronicSerialNumber parameter set to the MS’sElectronicSerialNumber value.

13-2 Include the MobileIdentificationNumber parameter set to theActivation_MIN value.

13-3 Include the ServiceIndicator parameter set to the CDMA OTASP Servicevalue.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

14 ENDIF.

15 Send an AuthenticationStatusReport INVOKE to the MSC’s associated VLR.

16 Start the Authentication Status Report Timer (ASRT).

17 WAIT for an Authentication Status Report response:


18-1 Stop timer (ASRT).


18-2-1 Execute the “MSC Receiving Authentication Parameters” task (see4.1.6) using the parameters received.





18-4 ENDIF.


19-1 Stop timer (ASRT).



20 WHEN timer (ASRT) expires:



21 ENDWAIT.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.5.2 VLR Awaiting AuthenticationStatusReport INVOKE (IS-41.6-C, Page 93)

When a VLR requests the Serving MSC to perform authentication operations thatrequire the Serving MSC to report the outcome, the VLR shall perform thefollowing:

1 Start the Authentication Status Report Response Timer (ASRRT).

2 WAIT for an AuthenticationStatusReport INVOKE:

3 WHEN an AuthenticationStatusReport INVOKE is received:

3-1 Stop timer (ASRRT).

3-2 IF the received message can be processed:

3-3 IF the ServiceIndicator parameter set to CDMA OTASP Service value isreceived:

3-3-1 IF OTASPCallEntry is not found:

3-3-1-1 Send a RETURN ERROR with the Error Code indicatingUnrecognized MIN.


3-3-2 ENDIF.

3-4 ENDIF.

3-4-1 IF the AuthenticationStatusReport INVOKE reports the outcome ofoperations initiated by the VLR:


3-4-1-2 Send a RETURN RESULT to the requesting MSC.

3-4-1-3 IF COUNT updating has been completed:

3-4-1-3-1 Increment the value of CallHistoryCount (COUNT) in theVLR’s database.

3-4-1-4 ENDIF.

3-4-1-5 IF all of the authentication operations initiated by the VLR havebeen successfully completed:


3-4-1-6 ELSE (the INVOKE reports the failure of an authenticationoperation initiated by the VLR):

3-4-1-6-1 Execute the “VLR Initiating an Authentication Failure Report”task (see 4.3.5) with the ReportType parameter set to indicatethe authentication failure reported by the Serving MSC.


3-4-1-7 ENDIF.

3-4-2 ENDIF.


3-4-3-1 IF the pending SSD is stored in the VLR’s database:

3-4-3-1-1 Remove the pending SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’sdatabase.

3-4-3-2 ENDIF.

3-4-4 ENDIF.



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-4-6 Relay the received SystemCapabilities (SYSCAP) parameter modifyingit to indicate whether the VLR is able to execute CAVE.


3-4-8 Relay all other received parameters.

3-4-9 Send an AuthenticationStatusReport INVOKE to the HLR associatedwith the MS (For CDMA OTASP, the HLR address is stored in theOTASPCallEntry).

3-4-10 Start the Authentication Status Report Timer (ASRT).

3-4-11 WAIT for an Authentication Status Report response:


3-4-12-1 Stop timer (ASRT).


3-4-12-2-1 IF the DenyAccess parameter is received:

3-4-12-2-1-1 Relay the DenyAccess parameter.

3-4-12-2-2 ENDIF.

3-4-12-2-3 IF the SSDNotShared (NOSSD) parameter is received:

3-4-12-2-3-1 Remove the MS’s current SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’sdatabase.

3-4-12-2-4 ENDIF.

3-4-12-2-5 IF the RandomVariableSSD (RANDSSD) is received:

3-4-12-2-5-1 IF SharedSecretData (SSD) is shared:

3-4-12-2-5-1-1 Remove the MS’s current SharedSecretData (SSD)and AuthenticationAlgorithmVersion (AAV) fromthe VLR’s database.

3-4-12-2-5-2 ENDIF.

3-4-12-2-5-3 Relay the received RandomVariableSSD (RANDSSD)parameter.

3-4-12-2-5-4 Mark the MS pending SSD update.

3-4-12-2-5-5 IF the SharedSecretData (SSD) is received:

3-4-12-2-5-5-1 Store the pending SharedSecretData (SSD) value.

3-4-12-2-5-5-2 IF the AuthenticationAlgorithmVersion (AAV)parameter is received:

3-4-12-2-5-5-2-1 Store the AuthenticationAlgorithmVersion(AAV) value.

3-4-12-2-5-5-3 ENDIF.

3-4-12-2-5-5-4 Select a RandomVariableUniqueChallenge(RANDU) and execute CAVE using the value of thepending SharedSecretData (SSD) to produce anAuthenticationResponseUnique (AUTHU).

3-4-12-2-5-5-5 Include the RandomVariableUniqueChallenge(RANDU) and AuthenticationResponseUnique(AUTHU) parameters.

3-4-12-2-5-5-6 Mark the MS pending Unique Challenge.

3-4-12-2-5-6 ELSE (the SharedSecretData (SSD) is not received):


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-4-12-2-5-6-1 Relay the RandomVariableUniqueChallenge(RANDU) parameter.

3-4-12-2-5-6-2 Relay the AuthenticationResponseUnique (AUTHU)parameter.


3-4-12-2-5-7 ENDIF.

3-4-12-2-6 ELSE (an SSD update is not requested by the AC):

3-4-12-2-6-1 IF the SharedSecretData (SSD) parameter is received:

3-4-12-2-6-1-1 Store the SharedSecretData (SSD) value.

3-4-12-2-6-1-2 IF the AuthenticationAlgorithmVersion (AAV)parameter is received:

3-4-12-2-6-1-2-1 Store the AuthenticationAlgorithmVersion(AAV) value.

3-4-12-2-6-1-3 ENDIF.

3-4-12-2-6-1-4 IF the CallHistoryCount (COUNT) parameter isreceived:

3-4-12-2-6-1-4-1 Store the received CallHistoryCount (COUNT)value.

3-4-12-2-6-1-5 ENDIF.

3-4-12-2-6-2 ENDIF.

3-4-12-2-6-3 IF the RandomVariableUniqueChallenge (RANDU):

3-4-12-2-6-3-1 Relay the received RandomVariableUniqueChallenge(RANDU) and AuthenticationResponseUnique(AUTHU) parameters.


3-4-12-2-6-4 ENDIF.

3-4-12-2-7 IF the UpdateCount (UPDCOUNT) parameter is received:

3-4-12-2-7-1 Relay the received UpdateCount (UPDCOUNT)parameter.

3-4-12-2-7-2 Mark the MS pending COUNT update.

3-4-12-2-8 ENDIF.

3-4-12-2-9 Send an AuthenticationStatusReport RETURN RESULT tothe requesting MSC.

3-4-12-2-10 IF the MS is marked pending SSD update, OR IF the MS ismarked pending Unique Challenge, OR IF the MS is markedpending COUNT update:

3-4-12-2-10-1 Execute the “VLR Awaiting AuthenticationStatusReportINVOKE” task (see 4.5.2).

3-4-12-2-11 ENDIF.



3-4-12-3-1 Send a RETURN ERROR to the requesting MSC.


3-4-12-4 ENDIF.


3-4-13-1 Stop timer (ASRT).


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60





3-4-13-3-2 ELSE:


3-4-13-3-3 ENDIF.



3-4-13-5 DEFAULT:


3-4-13-6 ENDCASE.



3-4-14 WHEN timer (ASRT) expires:

3-4-14-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure.



3-4-15 ENDWAIT.


3-5-1 Send a RETURN ERROR to the MSC.


3-5-2-1 IF the pending SSD is stored in the VLR’s database:

3-5-2-1-1 Remove the pending SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’sdatabase.

3-5-2-2 ENDIF.

3-5-3 ENDIF.




3-6 ENDIF.

4 WHEN timer (ASRRT) expires:


4-1-1 IF the pending SharedSecretData (SSD) is stored in the VLR’sdatabase:

4-1-1-1 Remove the pending SharedSecretData (SSD) andAuthenticationAlgorithmVersion (AAV) from the VLR’s database.

4-1-2 ENDIF.

4-2 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60



5 ENDWAIT.

6 Exit this task.

Table 11 VLR AuthenticationStatusReport Response

Problem Detection and Recommended Responsefrom VLR to MSC



UnrecognizedMIN X a

UnrecognizedESN aMIN/HLRMismatch X eOperationSequenceProblem aResourceShortage X eOperationNotSupported X b, eTrunkUnavailable aParameterError X dSystemFailure X eUnrecognizedParameterValue X d, eFeatureInactive aMissingParameter X d, e

RETURN RESULT X X X c

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported by the receiving AC

(HLR/VLR) or the requesting functional entity is not authorized.2. A required AC (HLR) resource (e.g., internal memory record, AC (HLR/VLR) is fully

occupied) is temporarily not available (e.g., congestion).3. A required resource (e.g., data base access, functional entity) is not presently accessible due to

a failure. Human intervention may be required for resolution.4. A supplied parameter value an encoding problem (e.g., the supplied

MobileIdentificationNumber parameter or Digits (Dialed) parameter digit values do not meetthe expected BCD specification).

5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used, theSystemCapabilities (SYSCAP) parameter indicated authentication is not supported (AUTH is0), but this AuthenticationStatusReport was received).

6. The supplied MobileIdentificationNumber parameter’s AC (HLR) responded that the MIN isnot in the AC (HLR)’s range of MIN’s or directory numbers (suspect routing error).

7. An optional parameter required by the AC (HLR) was expected, but not received (e.g., a SSDupdate process was in-progress and a ReportType set to SSD update successful was received,but the expected second ReportType parameter indicating the CallHistoryCount’s (COUNT’s)incrementing status (e.g., COUNT update successful, COUNT mismatch, Count update noresponse etc.) was not received).

8. The supplied MobileIdentificationNumber parameter’s AC (HLR) responded that the MIN iswithin the range of the AC (HLR), but the MIN is not presently assigned to a subscriber.DenyAccess parameter value is Unspecified.

9. An AC (HLR) record exists for the supplied MobileIdentificationNumber parameter, but thesupplied ElectronicSerialNumber parameter does not match the ESN in the MIN’s record.DenyAccess parameter value is Unspecified.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

10. An AC (HLR) record exists for the supplied MobileIdentificationNumber parameter, but theMIN is either a DelinquentAccount, StolenUnit, DuplicateUnit or Unspecified. DenyAccessparameter value is Unspecified.

11. The VLR does not have a OTASPCallEntry for the CDMA OTASP transaction.

Notes:a. This Error Code is not an appropriate AC (HLR) response to a AuthenticationStatusReport

transaction.b. It is recommended that an AC (HLR) supports AuthenticationStatusReport transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.e. This response may have been originated by the AC (HLR).


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.5.3 HLR Receiving AuthenticationStatusReport INVOKE (IS-41.6-C, Page 98)

When an HLR receives an AuthenticationStatusReport INVOKE, it shall perform thefollowing:






1-1-2 ENDIF.

1-2 ENDIF



1-5 Start the Authentication Status Report Timer (ASRT).

1-6 Send an AuthenticationStatusReport INVOKE to the AC associated with theMS (For CDMA OTASP, the AC address is stored in theOTASPCallEntry).

1-7 WAIT for an Authentication Status Report response:


1-8-1 Stop timer (ASRT).



1-8-2-2 Send a RETURN RESULT to the requesting VLR.

1-8-3 ELSE:

1-8-3-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure to the requesting VLR.

1-8-4 ENDIF.


1-9-1 Stop timer (ASRT).





1-9-3-2 ELSE:


1-9-3-3 ENDIF.




TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

1-9-5 DEFAULT:


1-9-6 ENDCASE.



1-10 WHEN timer (ASRT) expires:

1-10-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure.



1-11 ENDWAIT.


2-1 Send a RETURN ERROR to the requesting VLR.

3 ENDIF.

4 Exit this task.

Table 12 HLR AuthenticationStatusReport Response

Problem Detection and Recommended Responsefrom HLR to VLR



UnrecognizedMIN X a

UnrecognizedESN aMIN/HLRMismatch X eOperationSequenceProblem aResourceShortage X eOperationNotSupported X b, eTrunkUnavailable aParameterError X dSystemFailure X eUnrecognizedParameterValue X d, eFeatureInactive aMissingParameter X d, e


Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported by the receiving AC

(HLR/VLR) or the requesting functional entity is not authorized.2. A required AC (HLR) resource (e.g., internal memory record, AC (HLR/VLR) is fully






TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

6. The supplied MobileIdentificationNumber parameter’s AC (HLR) responded that the MIN isnot in the AC (HLR)’s range of MIN’s or directory numbers (suspect routing error).

7. An optional parameter required by the AC (HLR) was expected, but not received (e.g., a SSDupdate process was in-progress and a ReportType set to SSD update successful was received,but the expected second ReportType parameter indicating the CallHistoryCount’s (COUNT’s)incrementing status (e.g., COUNT update successful, COUNT mismatch, Count update noresponse etc.) was not received).

8. The supplied MobileIdentificationNumber parameter’s AC (HLR) responded that the MIN iswithin the range of the AC (HLR), but the MIN is not presently assigned to a subscriber.DenyAccess parameter value is Unspecified.

9. An AC (HLR) record exists for the supplied MobileIdentificationNumber parameter, but thesupplied ElectronicSerialNumber parameter does not match the ESN in the MIN’s record.DenyAccess parameter value is Unspecified.

10. An AC (HLR) record exists for the supplied MobileIdentificationNumber parameter, but theMIN is either a Delinquent Account, StolenUnit, DuplicateUnit or Unspecified. DenyAccessparameter value is Unspecified.

11. The HLR does not have an OTASPCallEntry for the CDMA OTASP transaction.

Notes:a. This Error Code is not an appropriate AC (HLR) response to a AuthenticationStatusReport

transaction.b. It is recommended that an AC (HLR) supports AuthenticationStatusReport transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.e. This response may have been originated by the AC (HLR).


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.5.4 AC Awaiting AuthenticationStatusReport INVOKE (IS-41.6-C, page 100)

When an AC requests the VLR to perform authentication operations that require theVLR to report the outcome, the AC shall perform the following:

1 Start the Authentication Status Report Response Timer (ASRRT).

2 WAIT for an AuthenticationStatusReport INVOKE:

3 WHEN an AuthenticationStatusReport INVOKE is received:

3-1 Stop timer (ASRRT).

3-2 IF the received message can be processed:

3-2-1 IF the ServiceIndicator parameter set to CDMA OTASP Service valueis received:

3-2-1-1 Indicate success and relay received parameters to the calling task.

3-2-2 ENDIF.


3-2-4 IF the INVOKE message reports that the application of Voice Privacyis NOT successful:

3-2-4-1 Return failure to the calling task.

3-2-5 ENDIF.

3-2-6 IF the INVOKE message reports that the application of Signaling

3-2-7 Message Encryption is NOT successful:

3-2-7-1 Return failure to the calling task.

3-2-8 ENDIF.

3-2-9 IF the INVOKE reports that SSD updating has been successful:

3-2-9-1 Update the AC’s database to indicate that the pendingSharedSecretData (SSD) value is now the value used by the MS(For CDMA OTASP, the AC's database is updated only if thecorresponding A-Key was not generated as part of the currentCDMA OTASP transaction).

3-2-10 ENDIF.

3-2-11 IF the INVOKE reports that COUNT updating has been successful:

3-2-11-1 Increment the value of COUNT in the AC’s database.

3-2-12 ENDIF.

3-2-13 IF an authentication failure has been detected:

3-2-13-1 Execute recovery procedures according to the AC’s internalalgorithm.

3-2-14 ENDIF.

3-2-15 IF local administrative procedures request that service shall be denied:

3-2-15-1 Include the DenyAccess parameter:

3-2-16 ENDIF.

3-2-17 IF SharedSecretData (SSD) presently shared with the VLR shall bediscarded:

3-2-17-1 Include the SSDNotShared (NOSSD) parameter.

3-2-18 ENDIF.

3-2-19 IF an SSD update shall be initiated:


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-2-19-1 Select a RandomVariableSSD (RANDSSD) and execute CAVEusing the value of the MS’s A-key recorded in the AC’s databaseto produce a pending SharedSecretData (SSD).

3-2-19-2 Include the RandomVariableSSD (RANDSSD) parameter.

3-2-19-3 Mark the MS pending SSD update.

3-2-19-4 IF AC administrative procedures indicate that the pendingSharedSecretData (SSD) shall be shared with the VLR for the SSDupdate operation AND IF the ServiceIndicator parameter set toCDMA OTASP Service value is not received:

3-2-19-4-1 IF the VLR’s SystemCapabilities indicates that the VLR isable to execute the CAVE algorithm:

3-2-19-4-1-1 Include the SharedSecretData (SSD) parameter set to thepending SSD value.

3-2-19-4-1-2 IF the AuthenticationAlgorithmVersion (AAV) parameteris received:

3-2-19-4-1-2-1 Store the AuthenticationAlgorithmVersion (AAV)value.

3-2-19-4-1-3 ENDIF.

3-2-19-4-2 ENDIF.

3-2-19-5 ELSE (pending SharedSecretData (SSD) is not to be shared:

3-2-19-5-1 Select a RandomVariableUniqueChallenge (RANDU) andexecute CAVE using the value of the pending SSD to producean AuthenticationResponseUnique (AUTHU).

3-2-19-5-2 Include the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters.

3-2-19-5-3 Mark the MS pending Unique Challenge.

3-2-19-6 ENDIF.

3-2-20 ELSE (SSD update not initiated):

3-2-20-1 IF the SharedSecretData (SSD) shall be shared with the VLR:

3-2-20-1-1 IF the VLR’s SystemCapabilities indicates the VLR is capableof executing the CAVE algorithm:

3-2-20-1-1-1 Include the SharedSecretData (SSD) andCallHistoryCount (COUNT) parameters.

3-2-20-1-1-2 IF the AuthenticationAlgorithmVersion (AAV) parameteris received:

3-2-20-1-1-2-1 Store the AuthenticationAlgorithmVersion (AAV)value.

3-2-20-1-1-3 ENDIF.

3-2-20-1-2 ENDIF.

3-2-20-2 ENDIF.

3-2-20-3 IF a Unique Challenge shall be initiated:

3-2-20-3-1 Select a RandomVariableUniqueChallenge (RANDU) andexecute CAVE using the value of the MS’s SharedSecretData(SSD) recorded in the AC’s database to produce anAuthenticationResponseUnique (AUTHU).

3-2-20-3-2 Include the RandomVariableUniqueChallenge (RANDU) andAuthenticationResponseUnique (AUTHU) parameters.

3-2-20-3-3 Mark the MS pending Unique Challenge.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-2-20-4 ENDIF.

3-2-21 ENDIF.

3-2-22 IF a COUNT update shall be initiated:

3-2-22-1 Include the UpdateCount (UPDCOUNT) parameter.

3-2-22-2 Mark the MS pending COUNT update.

3-2-23 ENDIF.

3-2-24 Send an AuthenticationStatusReport RETURN RESULT to therequesting HLR.

3-2-25 IF the MS is marked pending SSD update, OR IF the MS is markedpending Unique Challenge, OR IF the MS is marked pending COUNTupdate:

3-2-25-1 Execute the “AC Awaiting AuthenticationStatusReport INVOKE”task (see 4.5.4).

3-2-26 ENDIF.



3-3-1 Send a RETURN ERROR to the requesting HLR.



3-3-3 ENDIF.


3-3-4-1 Remove the pending SharedSecretData (SSD) from the AC’sdatabase.

3-3-5 ENDIF.




3-4 ENDIF.

4 WHEN timer (ASRRT) expires:


4-1-1 Remove the pending SharedSecretData (SSD) from the AC’s database.

4-2 ENDIF.



4-5 IF the invoking task is related to CDMA OTASP:

4-5-1 Indicate failure to the calling task.

4-6 ENDIF.

5 ENDWAIT.

6 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 13 AC AuthenticationStatusReport Response

Problem Detection and Recommended Responsefrom AC to HLR



UnrecognizedMIN X a

UnrecognizedESN aMIN/HLRMismatch XOperationSequenceProblem aResourceShortage XOperationNotSupported X bTrunkUnavailable aParameterError X dSystemFailure XUnrecognizedParameterValue X dFeatureInactive aMissingParameter X d


Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported by the receiving AC or

the requesting functional entity is not authorized.2. A required AC resource (e.g., internal memory record, AC is fully occupied) is temporarily





6. The supplied MobileIdentificationNumber parameter’s AC (HLR) responded that the MIN isnot in the AC’s range of MIN’s or directory numbers (suspect routing error).

7. An optional parameter required by the AC was expected, but not received (e.g., a SSD updateprocess was in-progress and a ReportType set to SSD update successful was received, but theexpected second ReportType parameter indicating the CallHistoryCount’s (COUNT’s)incrementing status (e.g., COUNT update successful, COUNT mismatch, Count update noresponse) was not received).

8. The supplied MobileIdentificationNumber parameter’s AC responded that the MIN is withinthe range of the AC, but the MIN is not presently assigned to a subscriber. DenyAccessparameter value is Unspecified.

9. An AC record exists for the supplied MobileIdentificationNumber parameter, but the suppliedElectronicSerialNumber parameter does not match the ESN in the MIN’s record. DenyAccessparameter value is Unspecified.

10. An AC record exists for the supplied MobileIdentificationNumber parameter, but the MIN iseither a DelinquentAccount, StolenUnit, DuplicateUnit or Unspecified. DenyAccessparameter value is Unspecified.

11. The AC does not have an OTASPCallEntry for the CDMA OTASP transaction.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Notes:a. This Error Code is not an appropriate AC response to a AuthenticationStatusReport

transaction.b. It is recommended that an AC supports AuthenticationStatusReport transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.6 Base Station Challenge

4.6.1 MSC Initiating a Base Station Challenge (IS-41.6-C, page 104)

When an MSC receives a Base Station Challenge Order from an MS, it shall performthe following:

1 Include the ElectronicSerialNumber parameter set to identify the MS.

2 Include the MobileIdentificationNumber parameter set to identify the MS.

3 IF the MS is in a call AND the call was originated using an OTASP FeatureCode (*FC):

3-1 Include the ServiceIndicator parameter set to the CDMA OTASP Servicevalue.

3-2 Set the MobileIdentificationNumber parameter to the Activation_MINvalue.

4 ENDIF.

5 Include the RandomVariableBaseStation (RANDBS) parameter provided by theMS.

6 Send a BaseStationChallenge INVOKE to the MSC’s associated VLR.

7 Start the Base Station Challenge Timer (BSCT).

8 WAIT for a Base Station Challenge response:


9-1 Stop timer (BSCT).


9-2-1 Send a Base Station Challenge response to the MS that includes thereceived AuthenticationResponseBaseStation (AUTHBS).

9-3 ENDIF.


10-1 Stop timer (BSCT).


11 WHEN timer (BSCT) expires:


12 ENDWAIT.

13 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.6.2 VLR Receiving BaseStationChallenge INVOKE (IS-41.6-C, page 104)

When a VLR receives a BaseStationChallenge INVOKE, it shall perform thefollowing:


2 IF the ServiceIndicator parameter set to CDMA OTASP Service value isreceived:

2-1 IF OTASPCallEntry is not found:

2-1-1 Send a RETURN ERROR with the Error Code indicatingUnrecognized MIN.


2-2 ENDIF.

3 ENDIF.

3-1 IF the pending SharedSecretData (SSD) was provided to the VLR AND IFthe ServiceIndicator parameter set to CDMA OTASP Service value is notreceived:

3-1-1 Execute CAVE using the pending SharedSecretData (SSD) of the MSand the RandomVariableBaseStation (RANDBS) provided in theBaseStationChallenge INVOKE to produce theAuthenticationResponseBaseStation (AUTHBS).

3-1-2 Include the AuthenticationResponseBaseStation (AUTHBS) parameter.

3-1-3 Send a RETURN RESULT to the requesting MSC.

3-2 ELSE (The AuthenticationResponseBaseStation is to be computed by theAC:


3-2-2 Relay all other received parameters.

3-2-3 Send a BaseStationChallenge INVOKE to the HLR associated with theMS (For CDMA OTASP, HLR address is stored in theOTASPCallEntry).

3-2-4 Start the Base Station Challenge Timer (BSCT).

3-2-5 WAIT for a Base Station Challenge response:


3-2-6-1 Stop timer (BSCT).



3-2-6-2-2 Send the RETURN RESULT to the requesting MSC.



3-2-6-3-1 Send a RETURN ERROR to the requesting MSC.


3-2-6-4 ENDIF.


3-2-7-1 Stop timer (BSCT).



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60




3-2-7-3-2 ELSE:


3-2-7-3-3 ENDIF.



3-2-7-5 DEFAULT:


3-2-7-6 ENDCASE.



3-2-8 WHEN timer (BSCT) expires:

3-2-8-1 Send a RETURN ERROR with Error Code SystemFailure.



3-2-9 ENDWAIT.

3-3 ENDIF.


4-1 Send a RETURN ERROR to the requesting MSC.

5 ENDIF.

6 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 14 VLR BaseStationChallenge Response

Problem Detection and Recommended Response from VLR to an MSC

PROBLEM DEFINITION 1 2 3 4 5 6 7 8 Notes


UnrecognizedMIN XUnrecognizedESN XMIN/HLRMismatch X dOperationSequenceProblem X dResourceShortage X dOperationNotSupported X b, dTrunkUnavailable aParameterError X dSystemFailure X dUnrecognizedParameterValue aFeatureInactive aMissingParameter a

RETURN RESULT c

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported by the VLR or the

requesting functional entity is not authorized.2. A required VLR resource (e.g., voice channel, internal memory record, VLR is fully



MobileIdentificationNumber parameter digit values do not meet the BCD specification).5. The supplied MIN’s HLR indicated the MobileIdentificationNumber parameter is not in the

HLR’s range of MINs or Directory Numbers (suspect routing error).6. The VLR has another Authentication process active for the supplied

MobileIdentificationNumber parameter.7. The VLR does not presently have a record for the supplied MobileIdentificationNumber

parameter (The VLR does not have an OTASPCallEntry for the CDMA OTASP transaction).

8. The VLR presently has a record for the supplied MobileIdentificationNumber parameter, butthe supplied ElectronicSerialNumber parameter does not match the ESN in theMobileIdentificationNumber’s record.

Notes:a. This Error Code is not an appropriate VLR response to a BaseStationChallenge transaction.b. It is recommended that a VLR supports BaseStationChallenge transactions.c. Only the RETURN RESULT operations needing clarification have been included.d. This response may have been originated by the HLR (AC).


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.6.3 HLR Receiving BaseStationChallenge INVOKE (IS-41.6-C, page 106)

When an HLR receives a BaseStationChallenge INVOKE, it shall perform thefollowing:






1-1-2 ENDIF.

1-2 ENDIF.



1-5 Send a BaseStationChallenge INVOKE to the AC associated with the MS(For CDMA OTASP, the AC address is stored in the OTASPCallEntry).

1-6 Start the Base Station Challenge Timer (BSCT).

1-7 WAIT for a Base Station Challenge response:


1-8-1 Stop timer (BSCT).


1-8-2-1 Send a RETURN RESULT to the requesting VLR.


1-8-3 ENDIF.


1-9-1 Stop timer (BSCT).





1-9-3-2 ELSE:


1-9-3-3 ENDIF.



1-9-5 DEFAULT:


1-9-6 ENDCASE.



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


1-10 WHEN timer (BSCT) expires:

1-10-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure.



1-11 ENDWAIT.


2-1 Send a RETURN ERROR to the requesting VLR.

3 ENDIF.

4 Exit this task.

Table 15 HLR BaseStationChallenge Response

Problem Detection and Recommended Response from HLR to a VLR

PROBLEM DEFINITION 1 2 3 4 5 6 7 Notes


UnrecognizedMIN XUnrecognizedESN XMIN/HLRMismatch X dOperationSequenceProblem dResourceShortage X dOperationNotSupported X b, dTrunkUnavailable aParameterError X dSystemFailure X dUnrecognizedParameterValue aFeatureInactive aMissingParameter a

RETURN RESULT c

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported by the HLR or the

requesting functional entity is not authorized.2. A required HLR resource (e.g., voice channel, internal memory record, HLR is fully



MobileIdentificationNumber parameter digit values do not meet the BCD specification).5. The supplied MobileIdentificationNumber parameter is not in the HLR’s range of MINs or

Directory Numbers (suspect routing error).6. The HLR does not presently have a record for the supplied MobileIdentificationNumber

parameter (The HLR does not have an OTASPCallEntry for the CDMA OTASP transaction).

7. The HLR presently has a record for the supplied MobileIdentificationNumber parameter, butthe supplied ElectronicSerialNumber parameter does not match the ESN in the MIN’s record.

Notes:a. This Error Code is not an appropriate HLR response to a BaseStationChallenge transaction.b. It is recommended that a HLR supports BaseStationChallenge transactions.c. Only the RETURN RESULT operations needing clarification have been included.d. This response may have been originated by the AC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.6.4 AC Receiving BaseStationChallenge INVOKE (IS-41.6-C, page 108)

When an AC receives a BaseStationChallenge INVOKE, it shall perform thefollowing:






1-1-2 ENDIF.

2 ENDIF.

2-1 Execute CAVE using the pending SSD of the MS and theRandomVariableBaseStation (RANDBS) provided in theBaseStationChallenge INVOKE (for CDMA OTASP theAuthenticationData is derived from the MobileStationMIN parameter valuestored in the OTASPCallEntry), to produce theAuthenticationResponseBaseStation (AUTHBS).

2-2 Include the AuthenticationResponseBaseStation (AUTHBS) parameter.

2-3 Send a RETURN RESULT to the requesting HLR.


3-1 Send a RETURN ERROR to the requesting HLR.

4 ENDIF.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 16 AC BaseStationChallenge Response

Problem Detection and Recommended Response from AC to a HLR



UnrecognizedMIN XUnrecognizedESN XMIN/HLRMismatch XOperationSequenceProblem XResourceShortage XOperationNotSupported X bTrunkUnavailable aParameterError XSystemFailure XUnrecognizedParameterValue aFeatureInactive aMissingParameter a

RETURN RESULT c

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported by the AC or the

requesting functional entity is not authorized.2. A required AC resource (e.g., voice channel, internal memory record, AC is fully occupied) is

temporarily not available (e.g., congestion).3. A required resource (e.g., data base access, functional entity) is not presently accessible due to


MobileIdentificationNumber parameter digit values do not meet the BCD specification).5. The supplied MobileIdentificationNumber parameter is not in the AC’s range of MINs or

Directory Numbers (suspect routing error).6. The AC has another Authentication process active for the supplied

MobileIdentificationNumber parameter.7. The AC does not presently have a record for the supplied MobileIdentificationNumber

parameter (The AC does not have an OTASPCallEntry for the CDMA OTASP transaction).

8. The AC presently has a record for the supplied MobileIdentificationNumber parameter, butthe supplied ElectronicSerialNumber parameter does not match the ESN in the MIN’s record.

Notes:a. This Error Code is not an appropriate AC response to a BaseStationChallenge transaction.b. It is recommended that an AC supports BaseStationChallenge transactions.c. Only the RETURN RESULT operations needing clarification have been included.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.35 Redirection Directive

4.35.2 MSC Receiving RedirectionDirective INVOKE (ALT) (IS-41.6-C, page 223)

When an MSC receives a RedirectionDirective INVOKE, it shall perform thefollowing:


1-1 IF there is a call or leg in progress that is associated with the receivedBillingID and the MobileIdentificationNumber parameters:

1-1-1 Release the associated facilities, which may be facilities toward atoward the requesting MSC, or, if the call being redirected is anOTASP call, release the associated facilities toward the attached CSC.

1-1-2 Send a RETURN RESULT to the requesting network element, whichmay be an MSC, or, if the call being redirected is an OTASP call, maybe an OTAF.

1-1-3 Redirect the call to the received destination address.

1-1-4 IF applicable:

1-1-4-1 Maintain the transmission of answer supervision on the incomingfacility, if applicable.

1-1-5 ENDIF.

1-1-6 IF there was a TRN associated to the call that has been redirected:

1-1-6-1 Replace that association by an association to a new TRN whosevalue is the received destination address.

1-1-7 ENDIF.



1-2 ELSE (there is no call or leg in process):

1-2-1 Send a RETURN ERROR with a proper Error Code value (see thefollowing table) to the requesting network element, which may be anMSC, or, if the call being redirected is an OTASP call, may be anOTAF.


1-3 ENDIF.


2-1 Execute “Local Recovery Procedures” task (see 3.5.1).

2-2 Send a RETURN ERROR with a proper Error Code value (see thefollowing table) to the requesting network element, which may be an MSC,or, if the call being redirected is an OTASP call, may be an OTAF.

3 ENDIF.

4 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

4.38 Registration Notification

4.38.1 MSC Initiating MS Registration (IS-41.6-C, page 235)

When an MSC determines that a roaming Mobile Station (MS) is now within itsservice area (through autonomous registration, call origination, call termination (e.g.,a page response following a call to the roamer access number), or other mechanism,except for detection by a call handoff), or if instructed to do so for CDMA OTASP,this new Serving MSC shall start the registration notification process by doing thefollowing:

1 Include the QualificationInformationCode parameter set according to theinformation needed from the VLR.

2 Include the SystemAccessType parameter set to the type of access performed bythe MS.

3 IF the MS enters an OTASP session (initiated by either the MS or the ServingMSC):

3-1 Include the SystemAccessType parameter set to OTASP.

4 ENDIF.

5 IF the access occurred in a border cell:

..........

27 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C1 OTAF Attachment With Serving MSC

5.C1.1 MSC Obtaining a TRN

When the MSC determines that a TRN is required:

1 IF the MSC administers TRNs itself:

1-1 IF a TRN is available:

1-1-1 Assign a TRN.

1-1-2 Include the TRN.

1-1-3 Return to the calling task.

1-2 ELSE:

1-2-1 Return to the calling task with an unsuccessful indication.

1-3 ENDIF.

2 ELSE (the MSC obtains TRNs from the OTAF):

2-1 Include the BillingID parameter set to identify the OTASP call.

2-2 Include the Digits (Dialed) parameter set to the digits received from the MS.

2-3 Include the ElectronicSerialNumber parameter set to theElectronicSerialNumber received from the MS.

2-4 Include the MobileIdentificationNumber parameter set toMobileIdentificationNumber received from the MS.

2-5 Include the MSCID parameter set to the identity of the MSC.

2-6 Include TransactionCapability parameter set to indicate that theTerminationList is not supported.

2-7 Send a FeatureRequest INVOKE to the OTAF associated with the MSC.

2-8 Start the Feature Request Response Timer (FRRT).

2-9 WAIT for Feature Request response:


2-10-1 Stop timer (FRRT).


2-10-2-1 IF Digits (Destination) parameter is received:

2-10-2-1-1 Use the destination digits as TRN.

2-10-2-1-2 Include the TRN as CalledPartyNumber.

2-10-2-1-3 Return to the calling task.

2-10-2-2 ELSE:

2-10-2-2-1 Return to the calling task with an unsuccessful indication.

2-10-2-3 ENDIF.

2-10-3 ELSE (the message cannot be processed):

2-10-3-1 Return to the calling task with an unsuccessful indication.

2-10-4 ENDIF.


2-11-1 Stop timer (FRRT).


3 WHEN timer (FRRT) expires:

3-1 Return to the calling task with an unsuccessful indication.

3-2 ENDWAIT.

3-3 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C1.2 OTAF Initiating an SMDPP INVOKE to Attach with Serving MSC

Upon request by the CSC to attach with the Serving MSC (the request must includethe TRN), the OTAF shall do the following:

1 Allocate an Activation_MIN value to the transaction.

2 IF no Activation_MIN value is available:

2-1 Return failure indication to CSC.

3 ELSE:

3-1 Mark the Activation_MIN as busy.

4 ENDIF.

5 Identify Serving MSC’s address. The OTAF may translate the received TRNvalue to the Serving MSC address and save its result for subsequentcommunication with the MSC.

6 IF Serving MSC address is not found:

6-1 Release the Activation_MIN.

6-2 Return failure indication to CSC.

7 ENDIF.

8 Include the SMS_BearerData parameter with its length set to zero.

9 Include the SMS_TeleserviceIdentifier parameter with its length set to 0.

10 Include the MobileIdentificationNumber parameter set to the Activation_MINvalue.

11 Include the ServiceIndicator parameter set to the CDMA OTASP Service value.

12 Include the ActionCode parameter set to indicate “Attach MSC to OTAF”.

13 Include the TRN parameter set to the value received from the CSC.

14 Send an SMDPP INVOKE towards the Serving MSC.

15 Start the SMDPP timer (SMTcs).

16 WAIT for an SMDPP response:


16-1-1 Stop the timer (SMTcs).

16-1-2 IF the message cannot be processed:

16-1-2-1 Execute the “OTAF Recovery Procedure” task (see 5.C6.1).

16-1-3 ELSE:

16-1-3-1 IF the message contains an SMS_CauseCode parameter:

16-1-3-1-1 Store the SMS_CauseCode.

16-1-3-1-2 Execute "OTAF Recovery Procedure" task (see 5.C6.1).

16-1-3-2 ENDIF.

16-1-3-3 IF the message contains an ElectronicSerialNumber parameter:

16-1-3-3-1 Store the ElectronicSerialNumber parameter.

16-1-3-4 ENDIF.

16-1-3-5 IF the message contains an MobileStationMIN parameter:

16-1-3-5-1 Store the MobileStationMIN parameter.

16-1-3-6 ENDIF.

16-1-3-7 IF the message contains an SystemCapabilities parameter:

16-1-3-7-1 Store the SystemCapabilities parameter.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

16-1-3-8 ENDIF.

16-1-3-9 IF the message contains an MSCID parameter:

16-1-3-9-1 Store the MSCID parameter.

16-1-3-10 ENDIF.

16-1-3-11 IF the message contains an AuthorizationDenied parameter or aDenyAccess parameter, or both:

16-1-3-11-1 Relay the information to the CSC.

16-1-3-12 ENDIF.

16-1-3-13 Notify CSC.

16-1-4 ENDIF.

16-2 WHEN a REJECT is received:

16-2-1 Stop the timer (SMTcs).

16-2-2 Execute “OTAF Recovery Procedure” task (see 5.C6.1).

16-3 WHEN the timer (SMTcs) expires:


17 ENDWAIT.

18 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C1.3 MSC Receiving an SMDPP INVOKE to Attach with OTAF

Upon receipt of an SMDPP INVOKE with the ActionCode parameter indicating“Attach MSC to OTAF” and the ServiceIndicator parameter indicates CDMAOTASP service, the MSC shall do the following:


1-1 IF the TRN is known AND corresponds to an active OTASP call:

1-1-1 Determine MS's MobileIdentificationNumber andElectronicSerialNumber associated with the TRN.

1-1-2 Create an OTASPCallEntry.

1-1-3 IF OTASPCallEntry could not be created:

1-1-3-1 Include the SMS_CauseCode parameter set to indicate NetworkResource Shortage.

1-1-4 ELSE:

1-1-4-1 Include the MobileStationMIN parameter set to MS'sMobileIdentificationNumber value.

1-1-4-2 Include the ElectronicSerialNumber parameter set to MS'sElectronicSerialNumber value.

1-1-4-3 Include the MSCID parameter set to Serving MSC's MSCIDvalue.

1-1-4-4 Include the SystemCapabilities parameter set to indicate ServingSystem's authentication capabilities.

1-1-4-5 IF the mobile is operating in an unsupported mode

1-1-4-5-1 Set the SMS_CauseCode to Radio Interface Incompatibility.

1-1-4-6 ELSEIF the MS has performed intersystem handoff:

1-1-4-6-1 Include the SMS_CauseCode parameter set to indicateNetwork Interface not Supported.

1-1-4-7 ENDIF.

1-1-4-8 IF the AC has denied access to this MS:

1-1-4-8-1 Include DenyAccess parameter.

1-1-4-9 ENDIF.

1-1-4-10 IF the HLR has denied access to this MS OR the registrationattempt was unsuccessful:

1-1-4-10-1 Include AuthorizationDenied parameter.

1-1-4-11 ENDIF.

1-1-5 ENDIF.

1-2 ELSE:

1-2-1 Include the SMS_CauseCode parameter set to indicate AddressTranslation Failure.

1-3 ENDIF.

2 ELSE:

2-1 Include the SMS_CauseCode parameter set to the proper value.

3 ENDIF.

4 Send an SMDPP RETURN RESULT to the requesting OTAF.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C1.4 OTAF Initiating an SMDPP INVOKE to Release TRN

Upon request by the CSC to release TRN, the OTAF shall do the following:

1 Set the length of the SMS_BearerData parameter to zero.

2 Set the length of the SMS_TeleserviceIdentifier parameter to zero.

3 Include the ElectronicSerialNumber parameter set to the MS'sElectronicSerialNumber value returned from the Serving MSC.

4 Set the MobileIdentificationNumber parameter to the Activation_MIN value.

5 Set the ServiceIndicator parameter to the CDMA OTASP Service value.

6 Set the ActionCode parameter to indicate Release TRN.

7 Send the SMDPP Invoke message to the Serving MSC.




10-1 Stop the timer (SMTcs).

10-2 IF the message can not be processed:


10-3 ELSE:

10-3-1 IF the message contains an SMS_CauseCode parameter:

10-3-1-1 Store the SMS_CauseCode.

10-3-1-2 Execute “OTAF Recovery Procedure” task (see 5.C6.1).

10-3-2 ENDIF.

10-3-3 Notify CSC.

10-4 ENDIF:

11 WHEN a REJECT is received:


11-2 Execute “OTAF Recovery Procedure” task (see 5.C6.1).

12 WHEN the timer (SMTcs) expires:

12-1 Execute “OTAF Recovery Procedure” task (see 5.C6.1).13 ENDWAIT.

14 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C1.5 MSC Receiving an SMDPP INVOKE to Release TRN

Upon receipt of an SMDPP INVOKE with the ActionCode parameter indicatingRelease TRN and the ServiceIndicator parameter indicating CDMA OTASP Service,the MSC shall do the following:


1-1 IF an OTASPCallEntry is found:

1-1-1 Release TRN.

1-2 ELSE:

1-2-1 Set the SMS_CauseCode to Address translation Failure.

1-3 ENDIF.

2 ELSE:

2-1 Set the SMS_CauseCode to proper value.

3 ENDIF.

4 Send an SMDPP RETURN RESULT message to the requesting OTAF.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C2 OTAF Attachment With Serving MSC (ALT)

5.C2.1 OTAF Receiving a FeatureRequest INVOKE (ALT)

When an OTAF receives a FeatureRequest INVOKE, it shall perform the following:


1-1 IF the received Digits (Dialed) parameter contains an OTASP feature code:

1-1-1 IF a TRN is available:

1-1-1-1 Assign (or obtain) a TRN.

1-1-1-2 Include the Digits (Destination) parameter set to the TRN

1-1-1-3 Include the FeatureResult parameter set to Successful to indicatesuccessful feature operation.

1-1-2 ELSE (a TRN is not available):

1-1-2-1 IF there is an alternate OTAF/CSC designated to handle overflowtraffic:

1-1-2-1-1 Execute “OTAF Requesting TRN from an Alternate OTAF”task (see 5.C2.2).

1-1-2-1-2 IF a TRN is obtained fron the overflow OTAF/CSC:

1-1-2-1-2-1 Include the Digits (Destination) parameter set to the TRN

1-1-2-1-2-2 Include the FeatureResult parameter set to Successful toindicate successful feature operation.

1-1-2-1-3 ELSE (a TRN is not obtained from the overflow OTAF/CSC):

1-1-2-1-3-1 Include the FeatureResult parameter set to Unsuccessfulto indicate unsuccessful feature operation.

1-1-2-1-4 ENDIF.

1-1-2-2 ELSE (there is no OTAF/CSC designated to handle overflow):

1-1-2-2-1 Include the FeatureResult parameter set to Unsuccessful toindicate unsuccessful feature operation.

1-1-2-3 ENDIF.

1-1-3 ENDIF.

1-2 ELSE:

1-2-1 Include the FeatureResult parameter set to Unsuccessful to indicateunsuccessful feature operation.

1-3 ENDIF.

1-4 Send a RETURN RESULT.


2-1 Send a RETURN ERROR with a proper Error Code value to the requestingMSC.

3 ENDIF.

4 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 5.C2.1 OTAF FeatureRequest Response

Problem Detection and Recommended Response from OTAF to MSC



UnrecognizedMIN aUnrecognizedESN aMIN/HLRMismatch aOperationSequenceProblem XResourceShortage XOperationNotSupported X bTrunkUnavailable aParameterError X dSystemFailure XUnrecognizedParameterValue X dFeatureInactive aMissingParameter X d

RETURN RESULTAccessDeniedReason

c

Unassigned directory number aInactive aBusy aTermination Denied XNo Page Response aUnavailable a

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported, by the receiving OTAF,

or the requesting functional entity is not authorized.2. A required OTAF resource (e.g., internal memory record, the OTAF is fully occupied) is

temporarily not available (e.g., congestion).3. A required resource (e.g., data base access, functional entity) is not presently accessible due to

a failure. Human intervention may be required for resolution.4. A supplied parameter has an encoding problem (e.g., the supplied

MobileIdentificationNumber parameter digit values do not meet the BCD specification, theDigits (Dialed) parameter has an inconsistent length, digits in the Digits (Dialed) parameter dono meet the BCD specification).

5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used, thesupplied Digits (Dialed) parameter contain an unexpected Code 11, Code 12, or ST digit, thesupplied Digits (Dialed) parameter is an unexpected length, or a Digits (Dialed) parameter isusing an unrecognized value for numbering plan, encoding, or type of digit).

6. An expected, or required, optional parameter (e.g., BillingId MSCID) was not received.7. The supplied ElectronicSerialNumber parameter is in use for another activation in progress.8. The MS is AuthorizationDenied (e.g., Delinquent Account, Stolen Unit, Duplicate Unit, or

Unspecified).

Notes:a. This Error Code is not an appropriate OTAF response to a FeatureRequest transaction.b. It is recommended that an OTAF support FeatureRequest transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.

.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C2.2 OTAF Requesting TRN from an Alternate OTAF (ALT)

When an OTAF requires a TRN to be used to direct or redirect an OTASP call to aCSC associated to a different OTAF, it shall perform the following:

1 IF the OTAF had received a FeatureRequest INVOKE for the OTASP call:

1-1 Relay the received BillingID parameter to identify the call on theOriginating MSC.

1-2 Relay the received MobileIdentificationNumber parameter.

1-3 Relay the received ElectronicSerialNumber parameter.

1-4 Relay the received MSCID parameter to identify the Originating MSC.

1-5 Include the SystemMyTypeCode parameter.

1-6 IF the PC_SSN parameter is received:

1-6-1 Relay the received PC_SSN parameter to address the Originating MSC.

1-7 ENDIF.

1-8 Include SenderIdentificationNumber parameter set to the OTAF’sidentification number.

1-9 Send a RoutingRequest INVOKE to the OTAF from which a TRN isneeded.

1-10 Start the Routing Request Timer (RRT).

1-11 WAIT for a Routing Request response.


1-12-1 Stop timer (RRT).

1-12-2 IF the message cannot be processed:

1-12-2-1 Return to the calling task with an unsuccessful indication.

1-12-3 ELSE (the message can be processed):

1-12-3-1 IF Digits (destination) are received)

1-12-3-1-1 Use the destination digits as TRN.

1-12-3-1-2 Include the TRN as CalledPartyNumber.

1-12-3-1-3 Return to the calling task.

1-12-3-2 ELSE:

1-12-3-2-1 Return to the calling task with an unsuccessful indication.

1-12-3-3 ENDIF.

1-12-4 ENDIF.


1-13-1 Stop timer (RRT).


1-14 WHEN timer (RRT) expires:


1-15 ENDWAIT.

2 ELSE (no FEATREQ had been received for this OTASP call):

2-1 Return to the calling task with an unsuccessful indication.

3 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C2.3 OTAF Receiving RoutingRequest INVOKE (ALT)

When an OTAF receives a RoutingRequest INVOKE, it shall perform the following:


1-1 IF a TRN is available:

1-1-1 Assign (or obtain) a TRN.

1-1-2 Include the Digits (Destination) parameter set to the TRN

1-1-3 Include the MSCID parameter set to the value received in theRoutingRequest INVOKE

1-1-4 Send a RETURN RESULT to the requesting OTAF.

1-2 ELSE (no TRN is available):

1-2-1 Send a RETURN ERROR with Error Code ResourceShortage to therequesting OTAF.

1-3 ENDIF.


2-1 Send a RETURN ERROR with a proper Error Code value to the requestingOTAF.

3 ENDIF.

4 Exit this task.

Table 5.C2.3 OTAF RoutingRequest Response

Problem Detection and Recommended Response from OTAF to OTAF

PROBLEM DEFINITION 1 2 3 4 5 6 7 Notes


UnrecognizedMIN aUnrecognizedESN aMIN/HLRMismatch aOperationSequenceProblem aResourceShortage XOperationNotSupported X bTrunkUnavailable aParameterError X dSystemFailure XUnrecognizedParameterValue X dFeatureInactive aMissingParameter X d

RETURN RESULTAccessDeniedReason

c

Unassigned directory number eInactive eBusy eTermination Denied XNo Page Response eUnavailable e

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported, by the receiving OTAF,

or the requesting functional entity is not authorized.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

2. A required OTAF resource (e.g., internal memory record, the OTAF is fully occupied, allTRNs already assigned) is temporarily not available (e.g., congestion).

3. A required resource (e.g., data base access, functional entity) is not presently accessible due toa failure. Human intervention may be required for resolution.

4. A supplied parameter has an encoding problem (e.g., the suppliedMobileIdentificationNumber parameter digit values do not meet the BCD specification).

5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used).6. An expected, or required, optional parameter (e.g., SenderIdentificationNumber) was not

received.7. The MS is AuthorizationDenied (e.g., Delinquent Account, Stolen Unit, Duplicate Unit, or

Unspecified).

Notes:a. This Error Code is not an appropriate OTAF response to a RoutingRequest transaction.b. It is recommended that an OTAF supports RoutingRequest transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.e. This AccessDeniedReason is not an appropriate MSC response to a RoutingRequest

transaction.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C2.4 OTAF Initiating MSC Redirection of an OTASP Call (ALT)

When an OTAF determines that it should initiate MSC redirection of an OTASP call,it shall perform the following:

1 IF the OTAF had received a FeatureRequest INVOKE for the OTASP call:

1-1 Execute “OTAF Requesting TRN from an Alternate OTAF” task (see5.C2.2).

1-2 IF a TRN is obtained:

1-2-1 Include the Digits (Destination) parameter set to the TRN.

1-2-2 Relay the received BillingID parameter.

1-2-3 Relay the received MobileIdentificationNumber parameter.

1-2-4 Relay the received ElectronicSerialNumber parameter.

1-2-5 Include the SystemMyTypeCode parameter to identify themanufacturer of the OTAF.

1-2-6 Include the SenderIdentificationNumber, parameter set to the OTAF’sidentification number.

1-2-7 Send a RedirectionDirective INVOKE to the Originating MSCassociated with the OTASP call.

1-2-8 Start the Redirection Directive Timer (RDT).

1-2-9 WAIT for a Redirection Directive response:


1-2-10-1 Stop timer (RDT).


1-2-10-2-1 IF the call is still connected to the CSC:

1-2-10-2-1-1 Direct the CSC to release the call.

1-2-10-2-2 ENDIF.



1-2-10-3-1 Execute the “Local Recovery Procedures” task (see 3.5.1).


1-2-10-4 ENDIF.

1-2-11 WHEN the CSC notifies the OTAF that the call has disconnected:







1-2-13 WHEN timer (RDT) expires:



1-2-14 ENDWAIT.

1-3 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

2 ENDIF.

Table 5.C2.4 Originating MSC RedirectionDirective Response for OTASP

Problem Detection and Recommended Responsefrom Originating MSC to an OTAF



UnrecognizedMIN XUnrecognizedESN XMIN/HLRMismatch aOperationSequenceProblem aResourceShortage XOperationNotSupported X bTrunkUnavailable aParameterError X dSystemFailure XUnrecognizedParameterValue X dFeatureInactive aMissingParameter X d

RETURN RESULT c

Problem Detections:1 The requested IS-41 MAP operation is recognized, but not supported, by the receiving

Originating MSC, or the requesting functional entity is not authorized.2 A required Originating MSC resource (e.g., internal memory record, MSC is fully occupied)

is temporarily not available (e.g., congestion).3 A required resource (e.g., data base access, functional entity) is not presently accessible due to

a failure or the Digits (Destination) parameter received from the HLR is not acceptable.Human intervention may be required for resolution.

4 A supplied parameter value has an encoding problem (e.g., The suppliedMobileIdentificationNumber parameter digit values do not meet the BCD specification).

5 A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used, theOriginating MSC does not presently have a routed call attempt active for the suppliedBillingID parameter).

6 The Originating MSC does not presently have a routed call attempt active for the suppliedMobileIdentificationNumber parameter.

7 The Originating MSC has a routed call attempt active for the suppliedMobileIdentificationNumber parameter, but the supplied ElectronicSerialNumber parameterdoes not match the ESN of the routed call.

Notes:a. This Error Code is not an appropriate MSC response to a RedirectionRequest transaction.b. It is recommended that an Originating MSC supports RedirectionRequest transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifier in question as the FaultyParameter parameter.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C3 Exchange of OTASP Data Messages

5.C3.1 OTAF Initiating SMDPP INVOKE for OTASP Data MessageExchange

When triggered (the trigger must include the formatted IS-683 message), the OTAFshall do the following:

1 Include the SMS_BearerData parameter set identical to the OTASP Datamessage.

2 Include the SMS_TeleserviceIdentifier parameter with its length set equal tozero.



5 Include the ServiceIndicator parameter set to CDMA OTASP service value.

6 Send an SMDPP INVOKE to the Serving MSC.

7 Start the SMDPP timer (SMTcx)(x=m, l: depending on the mode of MSoperation, the lengths of the OTASP Data Messages being exchanged and thecorresponding response time at the MS).



9-1 Stop the timer (SMTcx).


9-2-1 Execute the “OTAF Recovery Procedure” task (see 5.C6.1).

9-3 ELSE:

9-3-1 IF the SMS_CauseCode parameter is present:

9-3-1-1 Relay the SMS_CauseCode value to the invoking task (Failurereason).

9-3-2 ELSE:

9-3-2-1 Relay contents of SMS_BearerData parameter to invoking task.

9-3-3 ENDIF.

9-4 ENDIF.


10-1 Stop the timer (SMTcx).


11 WHEN the timer (SMTcx) expires:


12 ENDWAIT.

13 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C3.2 MSC Receiving SMDPP INVOKE for OTASP Data MessageExchange

Upon receipt of an SMDPP INVOKE with ServiceIndicator parameter indicatingCDMA OTASP Service AND SMS_BearerData parameter with non-zero length, theMSC shall do the following:


1-1 IF the OTASPCallEntry is found:

1-1-1 IF the MS is operating in an unsupported mode:

1-1-1-1 Include the SMS_CauseCode parameter set to indicate RadioInterface Incompatibility.

1-1-2 ELSE:

1-1-2-1 IF the MS performed an intersystem handoff

1-1-2-1-1 Include the SMS_CauseCode parameter set to indicateNetwork Interface not supported.

1-1-2-2 ELSE:

1-1-2-2-1 Extract the OTASP Data Message from the SMS_BearerDataParameter.

1-1-2-2-2 Send the OTASP Data Message to the MS.

1-1-2-2-3 IF the message could not be sent:

1-1-2-2-3-1 Include the SMS_CauseCode parameter set to indicateNetwork Failure

1-1-2-2-4 ELSE:

1-1-2-2-4-1 WAIT for response from the MS (the waiting period mustnot exceed its associated voice call duration):

1-1-2-2-4-2 CASE MS event OF:

1-1-2-2-4-3 OTASP Data Message response:

1-1-2-2-4-3-1 Include the SMS_BearerData parameter madeidentical to the OTASP Data Message.

1-1-2-2-4-3-2 IF the OTASP Data Message exceeds IS-41 messagetransport size limitations:

1-1-2-2-4-3-2-1 Include the SMS_CauseCode parameter set toindicate Encoding Problem.

1-1-2-2-4-3-3 ENDIF.

1-1-2-2-4-4 No Layer 2 acknowledgment:

1-1-2-2-4-4-1 Include the SMS_CauseCode parameter set toindicate No Acknowledgment.

1-1-2-2-4-5 Reject Order received:

1-1-2-2-4-5-1 Include the SMS_CauseCode parameter set toindicate SMS Termination Denied.

1-1-2-2-4-6 ENDCASE.

1-1-2-2-5 ENDIF.

1-1-2-3 ENDIF.

1-1-3 ENDIF.

1-2 ELSE:


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

1-2-1 Include the SMS_CauseCode parameter set to indicate AddressTranslation Failure.

1-3 ENDIF.

2 ELSE (message can not be processed):

2-1 Include the SMS_CauseCode set to the proper value.

3 ENDIF.

4 Send an SMDPP RETURN RESULT to the requesting OTAF.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C4 MSC Procedure Triggers for OTASP

5.C4.1 OTAF Initiating SMDPP INVOKE for MS Registration

When triggered (the trigger must include the newly assignedMobileIdentificationNumber value), the OTAF shall do the following:

1 Include the SMS_BearerData parameter with its length set equal to zero.




5 Include the ServiceIndicator parameter set to the CDMA OTASP Service value.

6 Include the ActionCode parameter set to indicate Initiate RegistrationNotification.

7 Include the NewlyAssignedMIN parameter set to the MIN value received fromthe CSC.


9 Start the SMDPP timer (SMTcm).



11-1 Stop the timer (SMTcm).



11-3 ELSE:


11-3-2 Record the failure result and the SMS_CauseCode value.

11-3-3 ELSE:

11-3-4 Record the successful result.

11-3-5 ENDIF.

11-3-6 Return the results to the invoking task.

11-4 ENDIF.


12-1 Stop the timer (SMTcm).


13 WHEN the timer (SMTcm) expires:


14 ENDWAIT.

15 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C4.2 MSC Receiving SMDPP INVOKE for Registration of MS

Upon receipt of an SMDPP INVOKE with the ActionCode parameter indicatingInitiate Registration Notification and the ServiceIndicator parameter indicatesCDMA OTASP Service, the MSC shall do the following:



1-1-1 Record the received NewlyAssignedMIN value.

1-1-2 Execute “MSC Initiating MS Registration” task (see 4.38.1).

1-1-3 IF the previous task was unsuccessful:

1-1-3-1 Set the SMS_CauseCode to indicate Other Network Problem.

1-1-4 ELSE.

1-1-4-1 Include the AuthorizationDenied parameter if received.

1-1-5 ENDIF.

1-1-6 Execute “MSC initiating an MS Inactive” task (see 4.30.1).

1-1-7 IF the previous task was unsuccessful:

1-1-7-1 Set the SMS_CauseCode to indicate Other Network Problem.

1-1-8 ENDIF.

1-1-9 Include SMS_CauseCode parameter if set during this procedure.

1-2 ELSE (OTASPCallEntry could not be found):

1-2-1 Send an SMDPP RETURN RESULT to the OTAF withSMS_CauseCode parameter set to indicate Address translation Failure.

1-3 ENDIF.



3 ENDIF.

4 Send the SMDPP RETURN RESULT to the requesting OTAF.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C4.3 OTAF Initiating SMDPP INVOKE to Record New MIN

When triggered (the trigger must include the newly assignedMobileIdentificationNumber value), the OTAF shall do the following:

1 Include the SMS_BearerData parameter with its length set equal to zero.




5 Include the ServiceIndicator parameter set to CDMA OTASP Service value.

6 Include the ActionCode parameter set to indicate Record NEWMIN.

7 Include the NewlyAssignedMIN parameter set to theMobileIdentificationNumber value received from the CSC.








11-3 ELSE:


11-3-1-1 Record the failure result and the SMS_CauseCode.

11-3-2 ELSE:

11-3-2-1 Record the successful result.

11-3-3 ENDIF.

11-3-4 Relay the results to invoking task.

11-4 ENDIF.




13 WHEN the timer (SMTcs) expires:


14 ENDWAIT.

15 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C4.4 MSC Receiving SMDPP INVOKE to Record NEW MIN

Upon receipt of an SMDPP INVOKE with the ActionCode parameter indicatingRecord NEWMIN and the ServiceIndicator parameter indicates CDMA OTASPService, the MSC shall do the following:



1-1-1 Record the received NewlyAssignedMIN value.

1-2 ELSE:

1-2-1 Send an SMDPP RETURN RESULT to the OTAF withSMS_CauseCode parameter set to indicate Address translation Failure.

1-3 ENDIF.



3 ENDIF.

4 Send the SMDPP RETURN RESULT to the requesting OTAF.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C5 CSC Triggers to Execute OTASP Procedures

5.C5.1 CSC Trigger for OTASP Data Message Exchange

When triggered, the OTAF shall do the following:

1 Format the appropriate OTASP Data message as instructed by the CSC.

2 Execute “OTAF Initiating SMSDeliveryPointToPoint INVOKE for OTASPData Message Exchange" task (see 5.C3.1).

3 IF the previous task was successful:

3-1 Parse the response and relay results to the CSC.

4 ELSE:

4-1 Indicate failure to the CSC.

5 ENDIF

6 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C5.2 CSC Trigger for OTASP for A-Key Generation


1 Execute “OTAF Initiating OTASPRequest INVOKE" task (see 5.C7.1), usingActionCode value Generate Public Encryption Values.

2 IF the previous task was unsuccessful:


2-2 Exit this task.

3 ENDIF.

4 IF OTASP_ResultCode is received:

4-1 Relay information contained therein to the CSC.

4-2 Exit this task.

5 ENDIF.

6 Format the MS Key Request message.




8-2 Exit this task.

9 ENDIF.

10 IF SMS_CauseCode is received:



11 ENDIF.

12 Parse received MS Key Response message.

13 IF an Error is detected:

13-1 Relay this information to the CSC.


14 ENDIF.

15 Format the Key Generation Request message.



17-1 Indicate failure to the CSC..


18 ENDIF.




20 ENDIF.

21 Parse received Key Generation Response message.




TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60


23 ENDIF.

24 Execute “OTAF Initiating OTASPRequest INVOKE" task (see 5.C7.1), usingthe ActionCode value Generate A-Key.




26 ENDIF.

27 IF OTASP_ResultCode is received:


28 ELSE:

28-1 Execute “OTAF Initiating OTASPRequest INVOKE” task (see 5.C7.1)using ActionCode value Perform SSD Update.

28-2 Relay received information to the CSC.

29 ENDIF.

30 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C5.3 CSC Trigger for OTASP for Perform SSD Update


1 Execute “OTAF Initiating OTASPREQ INVOKE" task (see 5.C7.1).



2-2 Exit this task.

3 ENDIF.

4 Relay all received information to the CSC.

5 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C5.4 CSC Trigger for OTASP for Perform Reauthentication


1 Format the Re-Authenticate Request message.




3-2 Exit this task.

4 ENDIF.



5-2 Exit this task.

6 ENDIF.

7 Parse received Re-Authenticate Response message.



8-2 Exit this task.

9 ENDIF.

10 Execute “OTAF Initiating OTASPRequest INVOKE" task (see 5.C7.1), usingActionCode value Perform Re-Authentication.




12 ENDIF.

13 Relay all received information to the CSC.

14 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C6 OTAF Recovery

5.C6.1 OTAF Recovery Procedure

When the OTAF detects an abnormal condition, it may perform the following actionsas determined by internal algorithms and the specific condition encountered.

1 Record the abnormal condition.

2 IF the OTASP call is recoverable:

2-1 Take proper action.

3 ELSE:

3-1 Report the failure to the CSC.

4 ENDIF.

5 IF the OTASP call is lost:

5-1 Execute “OTAF Initiating OTASPREQ INVOKE for ‘End OTASP Session’“ task (see 5.C12.1).

5-2 Release the Activation_MIN.

6 ENDIF.

7 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C7 OTASPRequest

The OTASPRequest operation triggers the AC to initiate certain procedures. TheActionCode parameter which is included in the OTASPRequest INVOKE specifiesthe procedures that the AC shall initiate.

5.C7.1 OTAF Initiating OTASPRequest INVOKE

Upon being triggered, the OTAF shall perform the following:



3 Include the ServiceIndicator parameter set to CDMA OTASP Service value.

4 Include the ActionCode parameter set to indicate the procedures that the ACshall initiate.

4-1 Include the MobileStationMIN parameter returned from the Serving MSC.

5 CASE ActionCode OF:

5-1 Generate Public Encryption Values:

5-1-1 Include the AKeyProtocolVersion parameter set to MS-supported A-Key protocol version(s) value(s).

5-2 Generate A-Key:

5-2-1 Include the MobileStationPartialKey parameter received from the MS.

5-3 Perform SSD Update Procedure:

5-3-1 Include the MSCID parameter set to the Serving System's MSCIDvalue.

5-3-2 Include the SystemCapabilities parameter set to indicate ServingSystem's authentication capabilities returned from Serving MSC.

5-4 Perform Re-authentication Procedure:

5-4-1 Include the AuthenticationData parameter set to the value receivedfrom the MS.

5-4-2 Include the RandomVariable parameter set to the value sent to the MSfrom the OTAF.

5-4-3 Include the AuthenticationResponse parameter set to the value receivedfrom the MS.

5-4-4 Include the CallHistoryCount parameter set to the value received fromthe MS.

5-4-5 Include the MSCID parameter set to the Serving System's MSCIDvalue.

5-4-6 Include the SystemCapabilities parameter set to indicate ServingSystem's authentication capabilities returned from Serving MSC.

5-5 Commit A-Key:

5-5-1 IF a NewlyAssignedMIN parameter is assigned to the MS during thisOTASP session:

5-5-1-1 Include the NewlyAssignedMIN parameter set to the new MobileIdentification Number value.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5-5-2 ENDIF.

5-6 Release Resources.

5-6-1 NOTE: There are no other parameters included.

6 ENDCASE.

7 Send an OTASPRequest INVOKE to the appropriate HLR.

8 Start the OTASPRequest Timer (OTARTcx), (x=s, l: depending on theActionCode value).

9 WAIT for an OTASPRequest response:


10-1 Stop timer (OTARTcx).


10-2-1 Indicate success and relay all received parameters to the invoking task.


10-3 ELSE:

10-3-1 Execute "OTAF Recovery Procedures" task (see 5.C6.1).

10-4 ENDIF.



11-2 Execute "OTAF Recovery Procedures" task (see 5.C6.1).

12 WHEN timer (OTARTcx) expires:

12-1 Execute "OTAF Recovery Procedures" task (see 5.C6.1)

13 ENDWAIT.

14 Indicate failure to invoking task.

15 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C7.2 HLR Receiving an OTASPREQ INVOKE

When an HLR receives an OTASPREQ INVOKE from the OTAF with theServiceIndicator parameter indicating CDMA OTASP Service, it shall perform thefollowing:

1 IF the received mesage cannot be processed:

1-1 Send a RETURN ERROR with the proper Error Code value (see thefollowing table) to the requesting OTAF.

1-2 Exit this task.

2 ENDIF.

3 IF no permanent record exists which corresponds to the received MSMIN value:

3-1 CASE ActionCode of:

3-1-1 Generate Public Encryption Values:

3-1-1-1 IF an OTASPCallEntry exists:

3-1-1-1-1 Retrieve the network address of the AC.

3-1-1-2 ELSE:

3-1-1-2-1 Create OTASPCallEntry.

3-1-1-2-2 IF OTASPCallEntry could not be created:

3-1-1-2-2-1 Send a RETURN ERROR with the Error Code ofSystemFailure to the requesting OTAF.

3-1-1-2-2-2 Exit this task.

3-1-1-2-3 ENDIF.

3-1-1-2-4 Store network address of AC.

3-1-1-3 ENDIF.

3-1-2 Generate A-Key:



3-1-2-2 ELSE:

3-1-2-2-1 Include the OTASP_ResultCode parameter set toUnrecognizedOTASPCallEntry.

3-1-2-2-2 Send a RETURN RESULT to the requesting OTAF.


3-1-2-3 ENDIF.

3-1-3 Perform SSD Update Procedure:



3-1-3-2 ELSE:

3-1-3-2-1 Create OTASPCallEntry.

3-1-3-2-2 IF OTASPCallEntry could not be created:

3-1-3-2-2-1 Send a RETURN ERROR with the Error Code ofSystemFailure to the requesting OTAF.


3-1-3-2-3 ENDIF.

3-1-3-2-4 Store network address of AC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-1-3-3 ENDIF.

3-1-4 Perform Re-Authentication Procedure:



3-1-4-2 ELSE:




3-1-4-3 ENDIF.

3-1-5 Commit A-Key:



3-1-5-2 ELSE:




3-1-5-3 ENDIF.

3-1-6 Release Resources:

3-1-6-1 Retrieve OTASPCallEntry.

3-1-6-2 IF an OTASPCallEntry is found:


3-1-6-2-2 Delete the OTASPCallEntry.

3-1-6-3 ELSE:



3-1-6-4 ENDIF.

3-2 ENDCASE.

4 ENDIF.

5 Relay all received parameters (for the OTASPRequest INVOKE to be sent to theAC).

6 Send an OTASPREQ INVOKE to the appropriate AC.

7 Start the OTASPRequest Timer Stop timer (OTARTcx), (x=s, l: depending onthe ActionCode value).

8 WAIT for an OTASPRequest response:




9-2-1 Relay all received parameters (for the OTASPRequest RETURNRESULT to be sent to the requesting OTAF).

9-2-2 Send a RETURN RESULT to the requesting OTAF.



TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

9-3-1 Sent a RETURN ERROR to the requesting OTAF with the Error Codeindicating SystemFailure.


9-4 ENDIF.



10-2 IF a RETURN ERROR is received:

10-2-1 Relay the received Error Code.

10-2-2 Send a RETURN ERROR to the requesting OTAF.

10-3 ELSE:

10-3-1 Send a RETURN ERROR to the requesting OTAF with the Error Codeindicating SystemFailure.

10-4 ENDIF.


11 WHEN timer (OTARTcx) expires:

11-1 Send a RETURN ERROR to the requesting OTAF with the Error Codeindicating SystemFailure.


12 ENDWAIT.

13 Exit this task.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 5.C7.2 HLR OTASPRequest Response

Problem Detection and Recommended Response from HLR to OTAF

PROBLEM DEFINITION 1 2 3 4 5 6 7 8 9 10 11 12 Notes


UnrecognizedMIN aUnrecognizedESN aMIN/HLRMismatch aOperationSequenceProblem aResourceShortage XOperationNotSupported X b,eTrunkUnavailable aParameterError X d,eSystemFailure XUnrecognizedParameterValue X d,eFeatureInactive aMissingParameter X d,e

RETURN RESULT c

DenyAccess X f

OTASP_ResultCode X f

SignalingMessageEncryption

Report

X f

SSDUpdateReport X f

UniqueChallengeReport X f

VoicePrivacyReport X f

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported, by the receiving HLR,

or the requesting functional entity is not authorized.2. A required HLR resource (e.g., internal memory record, HLR is fully occupied) is temporarily



MobileIdentificationNumberparameter digit values do not meet the BCD specification).5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used).6. An expected, or required, optional parameter was not received.7. The supplied DenyAccess parameter indicates if the MS fails re-authentication or if there is a

COUNT mismatch.8. The supplied OTASP_ResultCode parameter identifies the reason for an unsuccessful

procedure at the AC.9. The supplied SignalingMessageEncryptionReport parameter provides more information on an

unsuccessful attempt by the AC to initiate Signaling Message Encryption at the Serving MSC.10. The supplied SSDUpdateReport parameter provides more information on an unsuccessful

attempt by the AC to initiate SSD Update.11. The supplied UniqueChallengeReport parameter provides more information on an

unsuccessful attempt to perform Unique Challenge with the MS as part of the SSD Updateprocedure.

12. The supplied VoicePrivacyReport parameter provides more information on an unsuccessfulattempt by the AC to initiate Voice Privacy at the Serving MSC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Notes:a. This Error Code is not an appropriate HLR response to a OTASPRequest transaction.b. It is recommended that an HLR supports OTASPRequest transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifierin question as the FaultyParameter parameter.e. This response may have been originated by the AC.f. This response shall have been originated by the AC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

5.C7.3 AC Receiving an OTASPREQ INVOKE

When an AC receives an OTASPRequest INVOKE from the HLR with theServiceIndicator parameter indicating CDMA OTASP service, it shall perform thefollowing:

1 IF the received mesage cannot be processed:

1-1 Send a RETURN ERROR with the proper Error Code value (see thefollowing table) to the requesting HLR.

1-2 Exit this task.

2 ENDIF.

3 CASE ActionCode of:

3-1 Generate Public Encryption Values:

3-1-1 IF an OTASPCallEntry does not exist:

3-1-1-1 Create OTASPCallEntry.

3-1-1-2 IF OTASPCallEntry could not be created:

3-1-1-2-1 Send a RETURN ERROR with the Error Code ofSystemFailure to the requesting HLR.


3-1-1-3 ENDIF.

3-1-2 ENDIF.

3-1-3 IF one of the received A-Key Protocol Versions is supported by theAC:

3-1-3-1 Select and store the AKeyProtocolVersion parameter value thatshall be used by the AC.

3-1-4 ELSE:

3-1-4-1 Include the OTASP_ResultCode parameter set toUnsupportedAKeyProtocolVersion.

3-1-4-2 Send a RETURN RESULT to the requesting HLR.


3-1-5 ENDIF.

3-1-6 Compute Base Station Partial Key value.

3-1-7 IF Base Station Partial Key value was successfully computed:

3-1-7-1 Store the ModulusValue parameter value used for computingBaseStationPartialKey.

3-1-7-2 Store the exponent value used for computingBaseStationPartialKey.

3-1-7-3 Include the AKeyProtocolVersion parameter set to the protocolversion value previously stored by the AC.

3-1-7-4 Include the ModulusValue parameter set to the value used forcomputing BaseStationPartialKey.

3-1-7-5 Include the PrimitiveValue parameter set to the value used forcomputing BaseStationPartialKey.

3-1-7-6 Include the BaseStationPartialKey parameter set to the computedBase Station Partial Key value.


3-1-8 ELSE:


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-1-8-1 Include the OTASP_ResultCode parameter set toComputationFailure.



3-1-9 ENDIF.


3-2 Generate A-Key:

3-2-1 Retrieve OTASPCallEntry.

3-2-2 IF an OTASPCallEntry does not exist:

3-2-2-1 Include the OTASP_ResultCode parameter set toUnrecognizedOTASPCallEntry.



3-2-3 ENDIF.

3-2-4 Compute A-Key using received MobileStationPartialKey parametervalue.

3-2-5 IF A-Key was successfully computed:

3-2-5-1 Store the A-Key in the OTASPCallEntry.

3-2-5-2 Send an empty RETURN RESULT to the requesting HLR.

3-2-6 ELSE:

3-2-6-1 Include the OTASP_ResultCode parameter set to indicateComputationFailure.



3-2-7 ENDIF.


3-3 Perform SSD Update Procedure:

3-3-1 IF a permanent record exists which corresponds to the receivedMSMIN value:

3-3-1-1 IF an OTASPCallEntry exists AND IF the OTASPCallEntrycontains an A-Key:

3-3-1-1-1 Retrieve the A-Key from the OTASPCallEntry for use duringSSD update.

3-3-1-2 ELSE:

3-3-1-2-1 Retrieve the A-Key from the permanent record for use duringSSD update.

3-3-1-3 ENDIF.

3-3-2 ELSE:


3-3-2-2 IF an OTASPCallEntry does not exist:




3-3-2-3 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-3-2-4 Retrieve the A-Key from the OTASPCallEntry for use during SSDupdate.

3-3-3 ENDIF:

3-3-4 Execute “AC Initiating AuthenticationDirective INVOKE” task (see4.1.1) using all received parameters.

3-3-5 IF the above task returned with a success indication:



3-3-6 ELSE:

3-3-6-1 Send a RETURN ERROR to the requesting HLR with the ErrorCode indicating SystemFailure.

3-3-7 ENDIF.


3-4 Perform Re-Authentication Procedure:

3-4-1 IF a permanent record exists which corresponds to the receivedMSMIN value:

3-4-1-1 IF an OTASPCallEntry exists AND IF the OTASPCallEntrycontains an A-Key:

3-4-1-1-1 IF the OTASPCallEntry contains an SSD:

3-4-1-1-1-1 Retrieve the SSD from the OTASPCallEntry for useduring Re-Authentication.

3-4-1-1-2 ELSE:

3-4-1-1-2-1 Send a RETURN ERROR with the Error Code ofOperationSequenceProblem to the requesting HLR.


3-4-1-1-3 ENDIF.

3-4-1-2 ELSE:

3-4-1-2-1 Retrieve the SSD from the permanent record for use duringRe-Authentication.

3-4-1-3 ENDIF.

3-4-2 ELSE:


3-4-2-2 IF an OTASPCallEntry does not exist:




3-4-2-3 ENDIF.

3-4-2-4 IF OTASPCallEntry contains SSD:

3-4-2-4-1 Retrieve the SSD from the OTASPCallEntry for use duringRe-Authentication.

3-4-2-5 ELSE:

3-4-2-5-1 Send a RETURN ERROR with the Error Code ofOperationSequenceProblem to the requesting HLR.


3-4-2-6 ENDIF.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-4-3 ENDIF.

3-4-4 Execute the Authentication-Signature Generation procedure usingreceived RandomVariable, ElectronicSerialNumber andAuthenticationData parameter values and using the retrieved SSD forthe MS.

3-4-5 IF the Authentication-Signature Generation procedure result and thereceived AuthenticationResponse parameter value match:

3-4-5-1 IF a COUNT mismatch is relevant AND the stored count and thereceived CallHistoryCount parameter value do not significantlymatch:

3-4-5-1-1 Include the DenyAccess parameter set to COUNT Mismatch.



3-4-5-2 ENDIF.

3-4-5-3 Execute “AC Initiating AuthenticationDirective INVOKE” task(see 4.1.1) using all received parameters.

3-4-5-4 IF the above task was successful:



3-4-5-5 ELSE:

3-4-5-5-1 Send a RETURN ERROR with the Error Code indicatingSystemFailure to the requesting HLR.

3-4-5-6 ENDIF.

3-4-6 ELSE (AuthenticationResponse received does not match):

3-4-6-1 Include the DenyAccess parameter set to AUTHR mismatch.


3-4-7 ENDIF.


3-5 Commit A-Key1:

3-5-1 Retrieve OTASPCallEntry.


3-5-2-1 Include the OTASP_ResultCode parameter set toUnrecognizedOTASPCallEntry.



3-5-3 ENDIF.

3-5-4 IF the received message contains a NEWMIN parameter:

3-5-4-1 Store the temporary A-Key and SSD (if present) into a permanentrecord corresponding to the received NEWMIN and ESN values(permanent record may previously exist or be created by thisprocedure).

1A-Key generated during an OTASP session can be transferred to a permanentrecord at the AC using the following procedures. If system policy permits, the ACmay remove the old record, if one exists.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

3-5-5 ELSE:

3-5-5-1 Store the temporary A-Key and SSD (if present) into a permanentrecord corresponding to the received MSMIN and ESN values(permanent record may previously exist or be created by thisprocedure).

3-5-6 ENDIF.

3-5-7 IF unable to permanently store the A-Key (and possibly SSD):

3-5-7-1 Include the OTASP_ResultCode parameter set to Unable toCommit.



3-5-8 ENDIF.

3-5-9 Remove the A-Key and, if present, the SSD from the OTASPCallEntry.

3-5-10 Send a RETURN RESULT to the requesting HLR.


3-6 Release Resources:

3-6-1 IF an OTASPCallEntry is found:

3-6-1-1 Delete the OTASPCallEntry.

3-6-2 ENDIF.

3-6-3 Send a RETURN RESULT to the requesting HLR.


4 ENDCASE.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Table 5.C7.3 AC OTASPRequest Response

Problem Detection and Recommended Response from AC to HLR

PROBLEM DEFINITION 1 2 3 4 5 6 7 8 9 10 11 12 13 Notes


UnrecognizedMIN aUnrecognizedESN aMIN/HLRMismatch aOperationSequenceProblem X eResourceShortage XOperationNotSupported X bTrunkUnavailable aParameterError X dSystemFailure XUnrecognizedParameterValue X dFeatureInactive aMissingParameter X d

RETURN RESULT c

DenyAccess X

OTASP_ResultCode X

SignalingMessageEncryption

Report

X

SSDUpdateReport X

UniqueChallengeReport X

VoicePrivacyReport X

Problem Detections:1. The requested IS-41 MAP operation is recognized, but not supported, by the receiving AC, or

the requesting functional entity is not authorized.2. A required AC resource (e.g., internal memory record, HLR is fully occupied) is temporarily



MobileIdentificationNumberparameter digit values do not meet the BCD specification).5. A supplied parameter value is unrecognized or has nonstandard values (e.g., Not used).6. An expected, or required, optional parameter was not received.7. The supplied DenyAccess parameter indicates if the MS fails re-authentication or if there is a

COUNT mismatch.8. The supplied OTASP_ResultCode parameter identifies the reason for an unsuccessful

procedure at the AC.9. The supplied SignalingMessageEncryptionReport parameter provides more information on an

unsuccessful attempt by the AC to initiate Signaling Message Encryption at the Serving MSC.10. The supplied SSDUpdateReport parameter provides more information on an unsuccessful

attempt by the AC to initiate SSD Update.11. The supplied UniqueChallengeReport parameter provides more information on an

unsuccessful attempt to perform Unique Challenge with the MS as part of the SSD Updateprocedure.

12. The supplied VoicePrivacyReport parameter provides more information on an unsuccessfulattempt by the AC to initiate Voice Privacy at the Serving MSC.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

Notes:a. This Error Code is not an appropriate AC response to a OTASPRequest transaction.b. It is recommended that an AC supports OTASPRequest transactions.c. Only RETURN RESULT operations needing clarification have been included.d. Include the Parameter Identifierin question as the FaultyParameter parameter.e. The requested action cannot be performed or is not expected in the current state.


TIA/EIA - IS-725

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

7 Operation Timer Values

Table 63 Operation Timer Values (continued)

Timer Default(sec.)

Started when Normally stoppedwhen

Action whentimer

expires

• • • • • • • • • • • • • • •

OTARTcs

OTASPRequestTimer

30 OTASPRequestINVOKE is sent withACTCODE set toGenerate A-Key,Generate PublicEncryption KeyValues, or ReleaseResources.

OTASPRequestRETURN RESULT isreceived.

Executerecoveryprocedures.

OTARTcl

OTASPRequestTimer

90 OTASPRequestINVOKE is sent withACTCODE set toPerform SSD Update,Perform Re-Authentication, orCommit A-Key.

OTASPRequestRETURN RESULT isreceived.


• • • • • • • • • • • • • • •

SMTcsShort MessageDelivery Timer

6 SMSDeliveryPointToPoint INVOKE issent to the ServingMSC.

SMSDeliveryPointToPoint RETURNRESULT is received.


SMTcm

Short MessageDelivery Timer




SMTcl

Short MessageDelivery Timer





1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

This page intentionally left blank.

End of ... 185 ... CDMA-OTASP

is-725_c

Documents