wireless intelligent network support for location based services (3gpp2)

7/29/2019 Wireless Intelligent Network Support for Location Based Services (3GPP2)

1/151

3GPP2 X.S0009-0

Version 1.0

Date: June 2004

Wireless Intelligent Network Support forLocation Based Services

COPYRIGHT

3GPP2 and its Organizational Partners claim copyright in this document and individualOrganizational Partners may copyright and issue documents or standards publications inindividual Organizational Partner's name based on this document. Requests for

reproduction of this document should be directed to the 3GPP2 Secretariat [email protected]. Requests to reproduce individual Organizational Partner's

documents should be directed to that Organizational Partner. See www.3gpp2.org for moreinformation.


2/151

Revision History

Revision Date

Rev. 0 Initial Publication June 2004


3/151

X.S0009

1

2

3

4

5

6

7

89

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

i Contents

WIRELESS INTELLIGENT NETWORK SUPPORT FOR LOCATION BASED SERVICES

CONTENTS

List of Figures .........................................................................................................................................................v

List of Tables..........................................................................................................................................................vi

Revision History....................................................................................................................................................vii

Introduction ............................................................................................................................................................. 1

1 Objective................................................................................................................................................... 1

2 References................................................................................................................................................. 1

3 Organization.............................................................................................................................................. 1

4 Assumptions.............................................................................................................................................. 2

5 Editorial Conventions ............................................................................................................................... 3

Feature Descriptions............ .............. ............... .............. .............. .............. .............. .............. .............. .............. ..... 4

2 References................................................................................................................................................. 4

2.1 Normative References ................................................................................................................4

2.2 Informative References .............................................................................................................. 4

3 Definitions and Concepts.......................................................................................................................... 5

3.1 Definitions .................................................................................................................................. 5

4 Fleet and Asset Management (FAM)........................................................................................................ 6

4.1 Normal Procedures With Successful Outcome .......................................................................... 6

4.2 Exception Procedures or Unsuccessful Outcome....................................................................... 8

4.3 Alternative Procedures ...............................................................................................................9

4.4 Interactions With Other Wireless Services................................................................................. 9

5 Location Based Charging (LBC) ............................................................................................................10

5.1 Normal Procedures With Successful Outcome ........................................................................10

5.2 Exception Procedures or Unsuccessful Outcome..................................................................... 12

5.3 Alternative Procedures ............................................................................................................. 13

5.4 Interactions With Other Wireless Services............................................................................... 13

6 Location-Based Information Service (LBIS)..........................................................................................17

6.1 Normal Procedures With Successful Outcome ........................................................................17

6.2 Exception Procedures or Unsuccessful Outcome..................................................................... 19

6.3 Alternative Procedures ............................................................................................................. 20

6.4 Interactions with Other Wireless Services ...............................................................................20

7 Enhanced Call Routing (ECR)................................................................................................................ 22
http://x.p0009lof.pdf/http://x.p0009lot.pdf/http://x.p0009%20rh.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20section%201.pdf/http://x.p0009%20rh.pdf/http://x.p0009lot.pdf/http://x.p0009lof.pdf/


4/151

X.S0009

Contents ii

1

2

3

4

5

6

7

89

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 Normal Procedures With Successful Outcome.........................................................................22

7.2 Exception Procedures or Unsuccessful Outcome .....................................................................23

7.3 Alternative Procedures..............................................................................................................24

7.4 Interactions With Other Wireless Services...............................................................................24

TIA/EIA-41.1-D Modifications.............................................................................................................................26

4 Symbols and Abbreviations ....................................................................................................................26


8.1 Fleet and Asset Management (FAM)........................................................................................27

8.1.1 FAM for MS in Home System ...................................................................................27

8.1.1.1 FAM for MS Powers on in Home System................................................27

8.1.1.2 FAM for MS Power Down.......................................................................29

8.1.2 FAM Tracking of Target MS .....................................................................................30

8.1.3 Single Introducing Star Invocation of FAM Tracking ...............................................33

8.1.4 Feature Code Invocation of FAM Tracking ...............................................................35

8.2 Location Based Charging (LBC) ..............................................................................................378.2.1 LBC Call Origination .................................................................................................37

8.2.2 LBC Call Delivery: Local Termination at Originating MSC.....................................40

8.2.3 LBC Call Termination in Visited System ..................................................................45

8.2.4 Successful Position Determination for LBC After Intersystem Handoff...................50

8.2.5 Unsuccessful LBC Call Origination: LIR Service Denial..........................................52

8.3 Location Based Information Services (LBIS)...........................................................................53

8.3.1 Single_Introducing_Star Invocation of LBIS on SCP................................................53

8.3.2 Single_introducing_Star Invocation of LBIS on a Service Node ..............................54

8.3.3 Feature Code Invocation of LBIS...............................................................................56

8.3.4 Unsuccessful Single_introducing_Star Invocation of LBIS on a Service Node ........58

8.3.5 LBIS Invocation Upon MS Registration ....................................................................60

8.3.6 LBIS Triggered in the Visited System: SLP and MPC on Same Platform ................62

8.3.7 LBIS Triggered in Visited System: Separate SLP and MPC .....................................64

8.4 Enhanced Call Routing (ECR)..................................................................................................67

8.4.1 Successful Enhanced Call Routing.............................................................................67

8.4.2 Unsuccessful Enhanced Call Routing: MS Position Not Available...........................69

8.4.3 Unsuccessful Enhanced Call Routing: LIR Service Denial .......................................71

8.4.4 Unsuccessful Enhanced Call Routing: Routing Number Not Available....................72

8.4.5 Successful Enhanced Call Routing Invoked by Dialing Special Number..................74

8.5 Non-SIM Registration Reporting..............................................................................................76

8.5.1 Non-SIM Report of MS Registration .........................................................................76

8.5.2 Non-SIM Report of MS Registration to Multiple SCFs.............................................78

8.5.3 Non-SIM Report of MS Deregistration......................................................................80

8.5.4 Activation or Deactivation of Registration Report.....................................................81

8.5.5 Activation or Deactivation of Registration Report: MDN MS Identifier...................82


5 Data Transfer Services ............................................................................................................................83
http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/


5/151

X.S0009

1

2

3

4

5

6

7

89

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

iii Contents

5.1 SS7-Based Data Transfer Services........................................................................................... 83

6 Application Services ............................................................................................................................... 83

6.4 MAP Operations.......................................................................................................................83

6.4.1 General ....................................................................................................................... 83

6.4.1.2 Operation Specifiers.................................................................................83

6.4.2 Operation Definitions................................................................................................. 836.4.2.13 FeatureRequest......................................................................................... 84

6.4.2.29 MSInactive ............................................................................................... 89

6.4.2.30 OriginationRequest ..................................................................................90

6.4.2.37 RegistrationNotification........................................................................... 95

6.4.2.h ServiceRequest.........................................................................................96

6.4.2.i AnalyzedInformation ............................................................................... 99

6.4.2.z CallControlDirective..............................................................................104

6.4.2.an InterSystemPositionRequest .................................................................. 106

6.4.2.au LCSParameterRequest ........................................................................... 110

6.4.2.av StatusNotificationRequest...................................................................... 111

6.5 Map Parameters ...................................................................................................................... 112

6.5.1 General ..................................................................................................................... 112

6.5.1.1 Parameter Identifiers .............................................................................. 112

6.5.2 Parameter Definitions .............................................................................................. 112

6.5.2.gw RegistrationReport .................................................................................112

TIA/EIA-41.6-D Modifications ............. .............. .............. .............. ............... .............. .............. ............. ........... 113

4.14 Feature Request ...................................................................................................................... 113

4.14.1 MSC Detecting Feature Request..............................................................................113

4.28 Location Request .................................................................................................................... 116

4.28.2 HLR Receiving LocationRequest INVOKE............................................................ 116

4.30 MS Inactive ............................................................................................................................121

4.30.X HLR Initiating an MS Inactive................................................................................. 121

4.30.Y SCF Receiving an MSInactive INVOKE.................................................................121

4.31 Origination Request................................................................................................................ 123

4.31.1 MSC Initiating an Origination Request ................................................................... 123

4.38 Registration Notification ........................................................................................................128

4.38.X HLR Initiating a Registration Notification ..............................................................128

4.38.Y SCF Receiving a RegistrationNotification INVOKE .............................................. 128

4.T Call Control Directive ............................................................................................................130

4.T.1 SCF Initiating a Call Control Directive ................................................................... 130

4.T.2 MSC Receiving a CallControlDirective INVOKE.................................................. 131

4.Y LCS Parameter Request.......................................................................................................... 133

4.Y.2 SCF Initiating an LCS Parameter Request...............................................................133

4.W InterSystem Position Request.................................................................................................134

4.W.2 SCF Initiating an InterSystem Position Request...................................................... 134

4.FF Status Notification Request ....................................................................................................135

4.FF.1 SCF Initiating Status Notification Request .............. .............. .............. ............... ..... 135

4.FF.2 HLR Receiving StatusNotificationRequest INVOKE .............. .............. .................135
http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/


6/151

X.S0009

Contents iv

1

2

3

4

5

6

7

89

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.Y WIN Service Logic .................................................................................................................137

7 Operation Timer Values ........................................................................................................................139

Annex A (informative) ............. .............. .............. .............. .............. ............... .............. ............. ............... ..........140
http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20annex%20a.pdf/http://x.p0009%20annex%20a.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/


7/151

X.S0009

1

2

3

4

5

6

7

89

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

v List of Figures

LIST OF FIGURES

Introduction

Feature Descriptions

TIA/EIA-41.1-D Modifications


Figure 1 FAM: MS Powers on in Home System.............................................................................27

Figure 2 FAM for MS Power Down................................................................................................ 29

Figure 3 FAM Tracking of Target MS ............................................................................................30

Figure 4 Single Introducing Star Invocation of FAM Tracking ...................................................... 33

Figure 5 Feature Code Invocation of FAM Tracking ...................................................................... 35

Figure 6 LBC Call Origination ........................................................................................................37

Figure 7 LBC Call Delivery: Local Termination at Originating MSC............................................41

Figure 8 LBC Call Termination in Visited System (1 of 2) ............................................................45Figure 9 LBC Call Termination in Visited System (2 of 2) ............................................................48

Figure 10 Successful Position Determination for LBC After Intersystem Handoff..........................50

Figure 11 Unsuccessful LBC Call Origination: LIR Service Denial ................................................52

Figure 12 Single_Introducing_Star Invocation of LBIS on SCP ...................................................... 53

Figure 13 LBIS Invocation on Service Node from the Single_Introducing_Star Trigger ................ 54

Figure 14 Feature Code Invocation of LBIS ..................................................................................... 56

Figure 15 Unsuccessful Single_introducing_Star Invocation of LBIS on a Service Node............... 58

Figure 16 LBIS Invocation Upon MS Registration........................................................................... 60

Figure 17 LBIS Triggered in Visited System: SLP and MPC on Same Platform............................. 62

Figure 18 LBIS Triggered in Visited System: Separate SLP and MPC............................................ 64

Figure 19 Successful Enhanced Call Routing ................................................................................... 67

Figure 20 Unsuccessful Enhanced Call Routing: MS Position Not Available.................................. 69

Figure 21 Unsuccessful Enhanced Call Routing: LIR Service Denial .............................................. 71

Figure 22 Unsuccessful Enhanced Call Routing: Routing Number Not Available........................... 72

Figure 23 Successful Enhanced Call Routing Invoked by Dialing a Special Number......................74

Figure 24 Non-SIM Report of MS Registration................................................................................76

Figure 25 Non-SIM Report of MS Registration to Multiple SCFs ...................................................78

Figure 26 Non-SIM Report of MS Deregistration.............................................................................80

Figure 27 Activation or Deactivation of Registration Report ...........................................................81

Figure 28 Activation or Deactivation of Registration Report: MDN MS Identifier ......................... 82



Annex A (informative)
http://x.p0009%20section%201.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20annex%20a.pdf/http://x.p0009%20annex%20a.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%201.pdf/


8/151

X.S0009

List of Tables vi

1

2

3

4

5

6

7

89

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

LIST OF TABLES

Introduction

Feature Descriptions

Table 1 LBC Subscription Options.................................................................................................11Table 2 LBIS Subscription Options................................................................................................18




Table 1 MTP Message Priority Values for TIA/EIA-41

Operations...............................................83

Table 2

TIA/EIA-41

MAP Operation Specifiers............. .............. .............. ............... .............. .......83

Table 3 Summary of MAP Operations ...........................................................................................83

Table 4 TIA/EIA-41 MAP Parameter Identifiers .........................................................................112


Table 1 SCF MSInactive Response ..............................................................................................122

Table 2 SCF RegistrationNotification Response .............. .............. ............... .............. .............. ...129

Table 3 HLR StatusNotificationRequest Response......................................................................136

Table 63 Operation Timer Values ..................................................................................................139

Annex A (informative)
http://x.p0009%20section%201.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20annex%20a.pdf/http://x.p0009%20annex%20a.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%206.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%205.pdf/http://x.p0009%20section%204.pdf/http://x.p0009%20section%203.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%202.pdf/http://x.p0009%20section%201.pdf/


9/151

X.S0009

1

2

3

4

5

6

7

89

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

vii Revision History

REVISION HISTORY

Revision Date Remarks

0 June 2004 Initial Publication


10/151

X.S0009

Revision History viii

1

2

3

4

5

6

7

89

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 is intentiaonlly left blank.


11/151

X.S0009

1

2

3

4

5

6

7

89

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

Objective 1 Introduction

INTRODUCTION

Fleet and Asset Management (FAM), Location Based Charging (LBC), Location Based

Information Service (LBIS) and Enhanced Call Routing (ECR) are WIN-based services that

enable the services to be tailored based on the subscribers current location (i.e., geographic

position). This document presents a recommended plan for the implementation of Wireless

Intelligent Network (WIN) capabilities that support these services.

1 OBJECTIVE

The purpose of this document is to describe FAM, LBC, LBIS and ECR, and to specify the

intersystem operations that enable a wireless system to provide these location-based services.

2 REFERENCES

This document builds on the following American National Standards Institute (ANSI)

standards:

TIA-664 TIA-664-000-B

, Wireless Features Description; Telecommunications

Industry Association; July 2003

TIA/EIA-41 TIA/EIA-41-D

, Cellular Radiotelecommunications Intersystem

Operations; Telecommunications Industry Association; December 1997

IS-764 TIA/EIA/IS-764

, Wireless Calling Name Feature Descriptions;

Telecommunications Industry Association; April 1998


, Wireless Intelligent Network; Telecommunication

Industry Association; December 1998.


, Wireless Intelligent Network Capabilities for EnhancedCharging Services; Telecommunications Industry Association:

October, 2000

J-STD-036 TIA/EIA J-STD-036-A

, Wireless Enhanced Emergency Services Phase II;

Telecommunications Industry Association; March 2002

DMH TIA/EIA-124-D

, Wireless Radio Telecommunication Intersystem Non-

Signaling Data Communication DMH (Data Message Handler);

Telecommunications Industry Association; December 2001

TIA-826 TIA-826-A

, Wireless Intelligent Network Capabilities for Pre-Paid

Charging; Telecommunications Industry Association; November 2003

TIA-881 TIA-881

, Location Services Enhancements; Telecommunications IndustryAssociation; March 2004

3 ORGANIZATION

This document is organized as follows:


12/151

X.S0009

Introduction 2 Assumptions

1

2

3

4

5

6

7

89

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

The Feature Descriptions

section provides feature descriptions for FAM, LBC, LBIS

and ECR according to the structure ofTIA-664 Wireless Features Descriptions.

The TIA/EIA-41.1-D

Modifications section provides the modifications and additions

to TIA/EIA-41-D

Chapter 1 Functional Overview.

The TIA/EIA-41.3-D


to TIA/EIA-41-D

Chapter 3 Automatic Roaming Information Flows.

The TIA/EIA-41.5-D

Modifications section the modifications and additions to

TIA/EIA-41-D

Chapter 5 Signaling Protocol.

The TIA/EIA-41.6-D


to TIA/EIA-41-D

Chapter 6 Signaling Procedures.

Annex A (informative) illustrates the relationship betweenTIA-881

and this document.

4 ASSUMPTIONS

The following assumptions were used in the development of this document:

a. The capabilities supported by this document are independent of any position

determination technology.

b. This document supports position information requests which are call associated and

non-call associated.

c. Position information storage is outside the scope of this document.

d. Subscriber profile information applicable to location based services in this document

uses the HLR-based profile access defined in TIA/EIA-41

.

e. Zone operations and zone transition detection is the responsibility of application

service logic and is outside the scope of this document.

f. If an application requires periodic position information updates, the application can

periodically query an MPC for the Target MS position.

g. The interactions of location based services with multi-party and redirected calls are not

covered by this document and are for further study.

h. WIN service logic can perform application authentication and LIR authorization. The

WIN Service Logic platform has the current Location Information Restriction (LIR)

information available.

i. The interaction of the Location Based Charging service (LBC) and the Pre-paid

Charging (PPC) service has not been considered.

j. For the Enhanced Call Routing (ECR) service, WIN service logic is capable of makingthe necessary association between geoposition received and routing digits for the

nearest ECR service center. The mechanism by which WIN service logic makes this

association is outside the scope of this document.

k. For subscriber-based location services, the SCF network entity will store the Mobile

Position Capability (MPCAP) for the subscriber (i.e., provisioned or obtained from the

HLR via the LCSParameterRequest operations).


13/151

X.S0009

1

2

3

4

5

6

7

89

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

Editorial Conventions 3 Introduction

5 EDITORIAL CONVENTIONS

The following editorial conventions are used for this document:

underline: addition

cross out

: deletion

change bar: indicates additions or deletions

new sub-sections are identified in the sub-section heading

for clarity, new sub-sections are shown with vertical change bars but are not underlined


14/151

X.S0009

Feature Descriptions 4 References

1

2

3

4

5

6

7

89

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

FEATURE DESCRIPTIONS

This section provides the feature and service descriptions for Fleet and Asset Management

(FAM), Location Based Charging (LBC), Location Based Information Service (LBIS) and

Enhanced Call Routing (ECR) according to the structure ofTIA/EIA-664

. These are WIN based

services that can be tailored for the subscriber based on the MS users current geographic

position.

2 REFERENCES

2.1 Normative References

(See TIA-664, Page 3)

The following standards contain provisions that, through reference in this text, constitute

provisions of this Standard. At the time of publication, the editions indicated were valid. All

standards are subject to revision, and parties to agreements based on this Standard are

encouraged to investigate the possibility of applying the most recent editions of the standardsindicated below. ANSI and TIA maintain registers of currently valid national standards

published by them.

[

IS-848

]

TIA/EIA/IS-848

, Wireless Intelligent Network Capabilities for Enhanced

Charging Services; Telecommunications Industry Association; October 2000

[

TIA-881

]

TIA-881

, Location Services Enhancements; Telecommunications Industry

Association; March 2004

2.2 Informative References


The following references were used in the preparation of this document to ensure compatibilitywith landline features.

S.R0019, Location-Based Services System (LBSS); 3rd Generation Partnership

Project 2; September 22, 2000

Standards Requirements Document, Wireless Intelligent Network Enhancements to

Support Location-Based Services [WIN Phase III]; Cellular Telecommunications

Industry Association; December 13, 1999


15/151

X.S0009

1

2

3

4

5

6

7

89

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

Definitions and Concepts 5 Feature Descriptions

3 DEFINITIONS AND CONCEPTS

3.1 Definitions


ECR

Enhanced Call Routing

FAM

Fleet and Asset Management

Geographic Zone

A geographic area assigned by a service provider that has meaning to the subscriber.

LBC

Location Based Charging

LBIS

Location Based Information Service


16/151

X.S0009

Feature Descriptions 6 Fleet and Asset Management (FAM)

1

2

3

4

5

6

7

89

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 FLEET AND ASSET MANAGEMENT (FAM)

Fleet and Asset Management (FAM) enables the position of one or more mobile stations to be

tracked. A mobile stations position information can be tracked if the MS is idle or engaged in

a call.

For typical FAM operation, two roles of FAM users are defined: FAM Member and FAM

Supervisor.

The FAM Member role applies to the FAM user or asset being tracked or monitored. All FAM

Members are equipped with appropriate mobile stations.

The FAM Supervisor role applies to the FAM user who is tracking (e.g., obtaining the position

of) active FAM Members. A FAM user may operate under both FAM Member and FAM

Supervisor roles simultaneously. A FAM Supervisor may activate or de-activate FAM service

for a FAM Member. FAM Supervisors may or may not be equipped with mobile stations. A

FAM Supervisor has a group of one or more FAM Members defined which it can track. A FAM

Supervisor may also be a FAM Member of a group.

For example, the FAM Supervisor can be the leader of a fleet, the owner of an asset or the parent

of a child. The FAM Member can be a driver of a fleet vehicle, the asset or the child.

The FAM Supervisor can have access to real-time geographic position information for all of the

FAM Members in its defined group. If this information is not available, the best available

position information may be provided with an indication of the reason the real-time information

is not available.The report of the FAM Members MS position includes the time at which the

position was determined.

FAM does not impact a FAM Members ability to originate or terminate calls.

Applicability to Telecommunications Services

FAM is applicable to all telecommunication services.

4.1 Normal Procedures With Successful Outcome

Authorization

FAM may be provided after pre-arrangement with the service provider. FAM Members must be

assigned to a FAM group.

De-Authorization

FAM may be withdrawn at the subscribers request or for administrative reasons.

Registration

FAM shall be registered upon authorization.


17/151

X.S0009

1

2

3

4

5

6

7

89

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

Fleet and Asset Management (FAM) 7 Feature Descriptions

De-Registration

FAM shall be de-registered upon de-authorization.

Activation

FAM may be activated upon authorization.

FAM Supervisor Role Activation of Group FAM Member

A FAM Supervisor may activate a FAM Member in a FAM group by specifying a FAM

activation feature code, as in:

FC + FAM Member Identifier + .

If the activation is accepted, the FAM Supervisor shall receive feature confirmation treatment.

If the FAM Member Identifier is not present, then the activation applies to the FAM

Supervisors own FAM Member status.

De-Activation

FAM shall be de-activated upon de-authorization.

FAM Supervisor Role De-Activation of Group Member

A FAM Supervisor may de-activate a FAM Member in a FAM group by specifying a FAM de-


FC0 + FAM Member Identifier + .

If the de-activation is accepted, the FAM Supervisor shall receive feature confirmation

treatment.

If the FAM Member Identifier is not present, then the de-activation applies to the FAM

Supervisors own FAM Member status.

Invocation

FAM Supervisor FAM Member Invocation

FAM is invoked when a FAM Supervisor requests the position information for a FAM

Members MS. The FAM Supervisor can request the current position information or multiple

reports of the FAM Members MS position. Multiple reports can be provided for a specified

duration of time (e.g., 24 hours). The reports can be provided periodically (e.g., every 30minutes), when the location of the FAM Members MS changes (e.g., when the MS registers in

a new MSC), when the status of the FAM Members MS changes (e.g., when the MS powers

on, powers down, becomes inactive, becomes active), or when a call event (call origination or

termination) occurs.

* SEND

* SEND


18/151

X.S0009

Feature Descriptions 8 Fleet and Asset Management (FAM)

1

2

3

4

5

6

7

89

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

FAM Member Invocation

FAM is invoked when a FAM Member initiates the sending of the MSs position information

to the FAM Supervisor.

Normal Operation with Successful Outcome

FAM Supervisor Initiated Operation

When a FAM Supervisor requests a FAM Members position information, the FAM Supervisor

will receive the position information.

FAM Member Initiated Operation

When a FAM Member initiates the sending of the MSs position, the FAM Supervisor will be

sent the position information.

Call Detail Record

The system should record call detail information for the following:

FAM activation and de-activation events

FAM invocation events

FAM usage duration

SeeDMH

for the specific information to be included for each element.

4.2 Exception Procedures or Unsuccessful Outcome

Registration

None identified.

De-Registration

None identified.

Activation

None identified.

De-Activation

None identified.

Invocation

If the network determines that the position information for the specified FAM Member is not

available, the network may send the best available position information and the reason that the

position information is not available (e.g., MS inactive).


19/151

X.S0009

1

2

3

4

5

6

7

89

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

Fleet and Asset Management (FAM) 9 Feature Descriptions

Exceptions While Roaming

FAM may not be active for the MS when the MS is roaming outside the FAM service area.

Position information may not be available when an MS is roaming outside the FAM service

area.

Optionally, notification may be provided to the FAM Supervisor that the FAM member is

outside the FAM service area.

Exceptions During Intersystem Handoff

None identified.

4.3 Alternative Procedures

None identified.

4.4 Interactions With Other Wireless Services

No interactions have been identified with the following exceptions:

Location Information Restriction (LIR)

LIR is invoked before FAM.


20/151

X.S0009

Feature Descriptions 10 Location Based Charging (LBC)

1

2

3

4

5

6

7

89

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 LOCATION BASED CHARGING (LBC)

Location Based Charging (LBC) permits wireless subscribers to be charged different rates for

telecommunications services based on MS position. Different rates may be charged based on

position or changes in position. Different rates may be charged for the duration of the call or

any part thereof. LBC may be made available to individual subscribers or to groups of

subscribers based on logical associations or locations.

LBC Services for Individual Subscribers

LBC can be an individual subscriber service. LBC presents the opportunity to individually

define and benefit from geographical areas or zones that have been custom designed for that

particular subscribers daily route and life style. These geographical areas could be designed to

maximize benefit from the LBC service by providing lower rates for usage in a subscribers

most frequently visited areas. Examples could be a home zone or an office zone. The LBC

service could provide yet another rate for usage in shopping malls or golf courses or country

clubs. LBC services might also offer different rates for usage based on time of day or day of

week in the zones that they have defined.

Optional notification to subscribers of their current zone or billing tier may be provided.

Optional notification of changes in zone or billing tier may also be provided as the subscriber

crosses a geographic boundary

LBC Services for Commercial Business Groups

LBC can provide services for commercial business groups. LBC can provide corporate campus

areas, work zones or business zones that have multiple tier billing rates for groups of

commercials users. LBC may include Freephone (FPH), Premium Rate Charging (PRC) and

other specialized services that are based on the MS position (seeIS-848).

Virtual national campus zones can also be part of a commercial LBC application supporting amultiple location virtual national campus. Optional notification to commercial users as to which

zone or billing tier they are currently in may be provided.


LBC is applicable to all telecommunications services.


Authorization

LBC is provided after pre-arrangement with service providers.


21/151

X.S0009

1

2

3

4

5

6

7

89

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

Location Based Charging (LBC) 11 Feature Descriptions

The authorization may have the following subscription options:

De-Authorization

LBC may be withdrawn at the subscribers request, the business customers request or for

administrative reasons.

Registration

LBC has no registration.

De-Registration

LBC has no de-registration.

Activation

LBC can be activated using special feature codes on a subscriber or business customer basis.

LBC may be activated by a Demand All-Services Activation authorized subscriber byspecifying a feature code, as in:

FC + .

If the activation is accepted, the system shall indicate success with feature confirmation

treatment.

LBC may be activated by a Demand Single-Call Activation authorized subscriber by

specifying a feature code and a termination address:

FC + # + termination address + , or

FC + termination address + .


treatment. In this case LBC applies only to charges for voice telecommunication services

associated with the call origination attempt.

Subscription Options Values

Single-Call Activation

Demand. The subscriber is authorized to activate LBC for a singlecall origination.

Permanent. LBC may not be activated for single call originations.

All-Services Activation

Demand. The subscriber is authorized to control the activation andde-activation of LBC for all telecommunications services.

Permanent. LBC is active for all telecommunications services.

Table 1 LBC Subscription Options

* SEND

* SEND

* SEND


22/151

X.S0009


1

2

3

4

5

6

7

89

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

De-Activation

LBC can be de-activated using special feature codes on a subscriber or business customer basis.

LBC may be de-activated by a Demand All-Services Activation authorized subscriber by

specifying a feature code, as in:

FC0 + .

If the de-activation is accepted, the system shall indicate success with feature confirmation

treatment.

For a Single-Call activation, LBC is automatically de-activated after the single call attempt is

cleared.

Invocation

LBC may be invoked by initial mobile station registration, autonomous registration, or by calls

placed or received by the mobile station.


Upon invocation, LBC can determine the MS location and establish the current zone of the

subscriber. LBC would notify the subscriber of their current zone. As the subscriber changes

zones the subscriber may be notified of changes to their zone and the rate may be changed.

Call Detail Record


LBC activation and de-activation events

LBC invocation events

MS position information at invocation (e.g., Serving Cell ID, Location Area ID, or

geographic position)

Zone identification

Zone boundary crossing

SeeDMHfor the specific information to be included for each element.


Registration

None identified.

De-Registration

None identified.

* SEND


23/151

X.S0009

1

2

3

4

5

6

7

89

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


Activation

None identified.

De-Activation

None identified.

Invocation

None identified


If a mobile station with LBC active roams into a system that does not support the LBC location

service, the following services may be available to the subscriber:

a. Call to customer service.

b. Optional notification of the out of coverage situation using an appropriate method(e.g., MS Display, SMS notification).


When the subscriber is handed off to a system that does not support LBC, the LBC service will

not be available in that system. Notification about rate change and zone change may not be

available and the LBC zone or location dependent rate will not be applied to the remainder of

the call.

The following services may be available to the subscriber:

a. Optional notification of the out of service coverage situation (e.g., warning tone, SMS

notification).


If the LBC subscriber has blocked their location information, the network shall not provide

the mobile station location information to any service logic application unless specifically

authorized to do so. In such cases, the location information will not be available to the LBC

service logic, and alternative procedures shall be applied (e.g., call denial, connection to

customer service). See interaction with LIR service1.



Call Delivery (CD)

LBC is invoked before CD.

1 See TIA-881 for a description of the Location Information Restriction (LIR) service


24/151

X.S0009


1

2

3

4

5

6

7

89

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

Call ForwardingBusy (CFB)

LBC is invoked before CFB.

Call ForwardingDefault (CFD)

LBC is invoked before CFD.

Call ForwardingNo Answer (CFNA)

LBC is invoked before CFNA.

Call ForwardingUnconditional (CFU)

LBC is invoked before CFU.

Call Transfer (CT)

LBC is invoked before CT.

Call Waiting (CW)

LBC is invoked before CW.

Calling Name Presentation (CNAP)

LBC is invoked before CNAP.

Calling Number Identification Presentation (CNIP)

LBC is invoked before CNIP.

Conference Calling (CC)

LBC is invoked before CC.

Data Privacy (DP)

For Further Study.

Do Not Disturb (DND)

LBC is invoked before DND

Emergency Services (9-1-1)

Emergency Services is invoked before LBC.

Enhanced Call Routing (ECR)

LBC is invoked before ECR.


25/151

X.S0009

1

2

3

4

5

6

7

89

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


Flexible Alerting (FA)

LBC is invoked before FA.

Group 3 Facsimile Service (G3 Fax)

Not applicable.

Incoming Call Screening (ICS)

LBC is invoked before ICS.

Location Based Information Services (LBIS)

LBC is invoked before LBIS.


LIR is invoked before LBC.

Message Waiting Notification (MWN)

LBC is invoked before MWN.

Mobile Access Hunting (MAH)

Interaction between LBC and MAH is beyond the scope of this standard.

Network Directed System Selection (NDSS)

LBC is invoked before NDSS.

Non-Public Mode Service (NP)

LBC is invoked before NP.

Over-the-Air Activation (OTA)

For Further Study.

Password Call Acceptance (PCA)

LBC is invoked before PCA.

Preferred Language (PL)

LBC is invoked before PL.

Priority Access and Channel Assignment (PACA)

LBC is invoked before PACA.


26/151


27/151

X.S0009

1

2

3

4

5

6

7

89

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

Location-Based Information Service (LBIS) 17 Feature Descriptions

6 LOCATION-BASED INFORMATION SERVICE(LBIS)

Location-Based Information Service (LBIS) allows subscribers to access information services

for which the information content is tailored to the current position of the MS.

Examples of LBIS include:

Wireless network operator customer service,

Concierge (hotel and restaurant finder) service,

Travel and tourism information service,

Automobile association roadside assistance service,

Directory assistance (local yellow pages),

Self-location (Where am I?) service,

Traffic information service to help subscribers avoid traffic congestion.

The information may be delivered to the subscriber through various means, such as:

Announcement,

Call set-up to an Interactive Voice Response system,

Graphical display (map, floor plan, picture, image),

Text message,

Call set-up to an operator.

LBIS may be invoked either:

1. Manually by the subscriber entering a feature code or originating a call to a directory

number associated with the specific location-based information service; or

2. Automatically by the network (such as the power on or zone change indicator); or

3. Periodically as determined by service logic.


LBIS is applicable to all telecommunications services.


Authorization

LBIS may be made generally available for all subscribers by the service provider or after pre-

arrangement with the service provider.


28/151

X.S0009

Feature Descriptions 18 Location-Based Information Service (LBIS)

1

2

3

4

5

6

7

89

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

LBIS may be authorized for the following options:

De-Authorization

LBIS may be withdrawn at the subscribers request or for administrative reasons.

Registration

LBIS has no registration.

De-Registration

LBIS has no de-registration.

Activation

LBIS may be activated upon authorization.

LBIS may be activated by a Demand Activation authorized subscriber specifying a LBIS


FC + .


treatment.

De-Activation

LBIS shall be de-activated upon de-authorization.

LBIS Demand De-Activation

LBIS may be de-activated by a Demand Activation authorized subscriber specifying a LBISde-activation feature code, as in:

FC0 + .

If the de-activation is accepted, the system shall indicate success with feature confirmation

treatment.

Subscription Options Values

Manual Invocation

Subscribed. The subscriber is authorized to invoke LBIS by dialing afeature code or an appropriate directory number.

Not subscribed.

Activation

Permanent. LBIS is active while authorized.

Demand. The subscriber is authorized to control the activation andde-activation of LBIS.

Table 2 LBIS Subscription Options

* SEND

* SEND


29/151

X.S0009

1

2

3

4

5

6

7

89

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


Invocation

LBIS may be invoked upon authorization.

Manual Invocation

LBIS may be invoked by a Manual Invocation authorized subscriber originating a call to a

directory number for which LBIS is active, as in:

FC + .


This section describes a normal sequence of procedures for LBIS operation.

Manual Invocation

Subscriber invokes the information service by entering a feature code or originating a

call to a directory number associated with that service;

The subscriber is connected to the service provider;

The service provider tailors the information content as per the current MS location and

provides the information to the subscriber in the context of the call.

Automatic Invocation

Network automatically connects the subscriber to the service provider when subscriber

powers on the mobile station;

The service provider tailors the information content as per the current MS location and

provides the information to the subscriber;

The information is provided to the subscriber.

Data Record

The following data shall be recorded:

1. LBIS invocation activities and events.

2. LBIS usage duration and times.

3. Application or Service Identifier.



Registration

None identified.

De-Registration

None identified.

* SEND


30/151


31/151

X.S0009

1

2

3

4

5

6

7

89

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



OTA is invoked before LBIS.

Subscriber PIN Access (SPINA)

SPINA is invoked before LBIS.

Subscriber PIN Intercept (SPINI)

SPINI is invoked before LBIS


32/151

X.S0009

Feature Descriptions 22 Enhanced Call Routing (ECR)

1

2

3

4

5

6

7

89

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 ENHANCED CALL ROUTING (ECR)

Enhanced Call Routing (ECR) allows calls to be routed to the appropriate destination based on

the position of the MS. The following are examples of ECR calls:

The MS user dials #427 (i.e., #GAS) and the call is routed to the nearest gas station.

The MS users call is completed via the lowest cost route.

The MS users call is sent to a toll free 800 number.

The MS users call is routed to the nearest private network node.

As an option, the call may be air time free to the caller and the called party may be charged for

the air time.


ECR is applicable to all telecommunications services.


Authorization

ECR may be generally available or after pre-arrangement with the service provider.

De-Authorization

ECR may be withdrawn at the subscribers request or for administrative reasons.

Registration

ECR has no registration.

De-Registration

ECR has no de-registration.

Activation

ECR has no activation.

De-Activation

ECR has no de-activation.


33/151

X.S0009

1

2

3

4

5

6

7

89

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

Enhanced Call Routing (ECR) 23 Feature Descriptions

Invocation

For initiation of ECR from the mobile station, the user enters the # abbreviated dialing code

followed by supplementary digits (e.g., any number of digits to be interpreted by the MSC). The

following are examples:

# + XX + .

Where XX indicates any number of supplementary digits that represent an abbreviated dialing

string.

# + DN + .

Where DN indicates a directory number (NPA-NXX-XXXX).

# + ZZ + DN + .

Where ZZ indicates supplementary digits followed by a DN (directory number).


This section describes a normal sequence of procedures for ECR operation:

1. The MS user dials an abbreviated dialing sequence such as # + XX + .

2. The network routes the call to the appropriate geographic destination based on theposition of the MS and the dialed digits. For example, if the MS user dials #427(i.e., #GAS), the call will be routed to the nearest gas station. Or, if the MS user dials# + DN, the call will be routed to the nearest network node.

Call Detail Record


Identity of the calling party.

The called number.

MS position.

Call duration and times.

Identity of the party that should be billed for the ECR call.

Special routing details (e.g., virtual private network).



Registration

None identified.

SEND

SEND

SEND

SEND


34/151

X.S0009

Feature Descriptions 24 Enhanced Call Routing (ECR)

1

2

3

4

5

6

7

89

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

De-Registration

None identified.

Activation

None identified.

De-Activation

None identified.

Invocation

If the MS position is not available at the time of call setup, local exception procedure shall be

used.


None identified.


None identified.


At the option of the serving wireless service provider, originating ECR calls may be billed to

the called party.



Emergency Services (9-1-1)

Emergency Services is invoked before ECR.

Location Based Charging (LBC)

LBC is invoked before ECR.


LIR is invoked before ECR.

Mobile Access Hunting (MAH)

For further study.


35/151

X.S0009

1

2

3

4

5

6

7

89

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

Enhanced Call Routing (ECR) 25 Feature Descriptions


OTA is invoked before ECR.

Subscriber PIN Access (SPINA)

SPINA is invoked before ECR.

Subscriber PIN Intercept (SPINI)

SPINI is invoked before ECR.


36/151

X.S0009

TIA/EIA-41.1-D Modifications 26 Symbols and Abbreviations

1

2

3

4

5

6

7

89

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

TIA/EIA-41.1-DMODIFICATIONS

This section provides new functional overview information for Wireless Intelligent Network

Capabilities for Location Based Services according to the structure ofTIA/EIA-41-D Chapter 1.

4 SYMBOLS AND ABBREVIATIONS(See TIA/EIA-41.1-D, page 1-14)

REGREPORT RegistrationReport parameter

STATNOTREQ StatusNotificationRequest INVOKE

statnotreq StatusNotificationRequest RETURN RESULT


37/151

X.S0009

1

2

3

4

5

6

7

89

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

Fleet and Asset Management (FAM) 27 TIA/EIA-41.3-D Modifications

TIA/EIA-41.3-DMODIFICATIONS

This section provides the additions and modifications to TIA/EIA-41-D Chapter 3 automatic

roaming information flows for Wireless Intelligent Network Capabilities for Location Based

wireless intelligent network support for location based services (3gpp2)

Documents