Free Essay

Traffic Cases

In:

Submitted By eliem
Words 14560
Pages 59
Traffic Cases
Charging System 5.0

CUSTOMER PRODUCT INFORMATION

2/1551-FAV 101 72/4 Uen B

Copyright © Ericsson AB 2010, 2011. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner. Disclaimer The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document. Trademark List All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Contents

Contents
1 1.1 1.2 2 3 3.1 3.2 3.3 3.4 3.5 3.6 4 4.1 4.2 4.3 Glossary Reference List Introduction Purpose and Scope Typographical Conventions General Common for all Traffic Cases Mobile Number Portability Community Charging Location Based Charging Notifications SDP Selection Subscription ID Independence Traffic Cases Real-Time Charging Services Offline Charging Services Voucher Refill and Enquiry 1 1 1 3 5 5 5 6 8 10 11 13 13 47 48 57 61

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Introduction

1

Introduction
This section describes the purpose and scope of this document, as well as typographical conventions used.

1.1

Purpose and Scope
The purpose of this document is to describe exemplify signalling sequences for different traffic scenarios in the Charging System. The signalling sequence examples provided in this document are not meant to cover all possible scenarios. The purpose is to give a general overview. The main target groups for this document are as follows: • • • • Network administrators System administrators Application administrators Operation and Maintenance (O&M) personnel

For information regarding the target groups, see the Customer Product Information Overview, Reference [1].

1.2

Typographical Conventions
This document follows a set of typographic rules that make the document consistent and easy to read. The typographic conventions is found in the Customer Product Information Overview, Reference [1]. In addition to the writing conventions mentioned above, the following applies: • • Charging System 5.0 is referenced as Charging System. The term Multi Mediation Solution is used whenever a reference to the associated products File and Event Mediation, Online Mediation, or Ericsson Multi Mediation is needed. Note: Event Mediation, Online Mediation and Ericsson Multi Mediation may appear either together or independently in other Charging System Customer Product Information (CPI), when used as example of the Multi Mediation solution needed.



The term Service Data Point (SDP) is used whenever a reference to the network element SDP Prepaid is needed.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

1

Traffic Cases



The following applies to functions marked with (ID:xxxxx). The id-tag is placed in the beginning and in the end of the description, or included in the header where the complete chapter is dedicated for this type of function. For more information about functions marked with (ID:xxxxx), see the System Description, Reference [2].

2

2/1551-FAV 101 72/4 Uen B | 2011-02-11

General

2

General
The Charging System can charge different types of calls and events. This is done either online (in real time) or offline. For all traffic cases described in this document the following applies: • • • The call-flows describe logical signalling paths, not physical connections. The call-flows describe non-fault situations. Error handling is not covered. The call-flows are dependent on service class settings and the service state.

The different protocols and services are used as follows: • • • • • • • • • CS1+ is used for voice and SMS related services. Camel Application Part version 1 (CAPv1) is used for voice related services. CAPv2 is used for voice related services. CAPv3 is used for SMS and GPRS services. Diameter, Draft 8, is used for content based services in real-time. Diameter Credit Control Application (DCCA) is used for online credit control of content based services. Ericsson RealTime Charging protocol (ERTC) is used for voice and SMS related services. Mobile Application Part version 2 (MAPv2), or higher, is used for Unstructured Supplementary Service Data (USSD) notifications. ETSI MAP can be used for USSD End of Call Notification, USSD Callback and Any Time Interrogation (ATI).

The Service Control Point (SCP) is the generic name for the function(s) that CCN realizes in the Charging System. Throughout the flowcharts in this document CCN is used as the SCP. For more information regarding Charging System, see the System Description, Reference [2].

2/1551-FAV 101 72/4 Uen B | 2011-02-11

3

Traffic Cases

4

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Common for all Traffic Cases

3

Common for all Traffic Cases
This chapter describes different features valid for all traffic cases.

3.1

Mobile Number Portability
Mobile Number Portability (MNP) in a network offers a mobile subscriber possibility to keep its number independently of a network operator choice. MNP makes it possible to differentiate charging of a Charging System subscriber for calls and SMS that the subscriber makes or receives based on the portability information retrieved from an MNP database. For CAPv2 mobile originating calls, the called party number and calling party number will be compared. If the numbers are equal, meaning the subscriber dialed their own number, then CCN sets the network identifier parameter to an operator configured value without going to the Local Number Portability (LNP) or MNP database to perform Mobile to Mobile (M2M) check. Figure 1 illustrates MNP.
CCN 1 2 3 MNP

Figure 1

Mobile Number Portability

1. The call is initiated by the Charging System subscriber. 2. If it is an originating or forwarded call: the called party number is sent to the MNP database. If it is a terminating call: the calling party number is sent to the MNP database. 3. The MNP database returns MNP information to CCN, for delivery to SDP.

3.2

Community Charging
Community Charging makes it possible to offer different tariffs when subscribers are calling within or between communities. Community Charging is not included in any of the flow charts , if not stated, in this document, but when active it is performed immediately before the first interrogation is sent to SDP. Community Charging is available for all services and for both prepaid and post-paid subscribers.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

5

Traffic Cases

Figure 2 illustrates community charging.
SDP
1 2 3 4 5

AF

SDP or Ext DB

Figure 2

Community Charging

1. CCN performs a first interrogation towards an SDP. Note: Retrieval of the non-served subscriber's community data is not performed, that is step 2 to 5 are omitted if the non-served subscriber's number is part of a number list indicating that the number is never part of a community or if there is no non-served subscriber present for pre-rated services. If the non-served subscriber's number is part of a number list indicating that the number is known to be stored in external database AF is not interrogated, and step 2 and 3 are skipped 2. SDP retrieves the SDP-ID for the non-served subscriber. 3. AF returns the SDP-ID. 4. SDP requests community data for the non-served subscriber from the entity holding the non-served subscriber's data. 5. The entity holding the non-served subscriber's community data returns community data for the non-served subscriber. This data is used for rating in SDP.

3.3

Location Based Charging
Location Based Charging (LBC), see Figure 3, can be performed for originating, terminating, and forwarded voice calls. It can also be performed for data (SCAPv2 and Gy). Location information can be fetched for ported or non-ported non-served subscribers. (ID:06753) LBC is performed for Service Charging Application Protocol (SCAP) MO SMS. (ID:06753)

6

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Common for all Traffic Cases

CCN
1 2

HLR

VLR

3 4 5

Figure 3

LBC

1. A charging request is received from the MSC, the request contains location information for the served subscriber. Note: CCN compares received call party number (originating and forwarded calls), or calling party number (terminating calls), with internal number lists. If the received number exists in the number list, a query can be sent to the HLR in step 2. If no match is found in the internal number list, a default location number is allocated to the non-served subscriber.

2. CCN requests location information for the non-served subscriber. 3. The HLR requests the location information from the VLR. 4. The VLR returns the location information to the HLR. 5. The HLR returns the location information. The received information both from the MSC and from the HLR is forwarded to SDP (not shown in figure above).

3.3.1

Dynamic Discount Solution Support
Charging System supports dynamic discount solution based on the location of the subscriber. At start of a charging session the discount is determined based on the location of the subscriber. Dynamic discount solution support is valid for originating voice and circuit switched sms sent over CS1+, CAPv2, CAPv3, and ERTC/RTCfA. Data is supported using Gy and SCAPv2.
Core network
1 2 3 4 5

CCN

SDP

HLR

. . .

6

7

Figure 4

Dynamic Discount Solution Support

2/1551-FAV 101 72/4 Uen B | 2011-02-11

7

Traffic Cases

1. The subscriber initiates a charging session. 2. The core network sends call party number to CCN. 3. CCN makes an interrogation lookup towards HLR requesting location information based on the call party number from the core network. 4. The HLR returns the location information to CCN. 5. CCN performs a SDP selection and sends the location information data collected in Step 4, along with other data, in a first interrogation/intermediate interrogation to SDP. 6. SDP uses the information and reserves money from the account based on possible discount and sends the calculated session time to CCN, together with other call data such as announcements to be played. A charging session starts and can have several intermediate interrogations. 7. At every intermediate interrogation from CCN to SDP, CCN monitors the age of the answer in Step 4 against a predetermined time period. If a certain amount of time has elapsed since the last HLR interrogation, a new interrogation towards the HLR is made and the new data received is processed. The default time period between HLR interrogations is 60 minutes but is configurable to 15, 30, or 60 minutes. It is not recommended to make the interval smaller than five minutes. Note: Step 3–7 can be repeated several times.

3.4

Notifications
In the Charging System there are different ways to communicate with the subscriber. USSD notifications is used for both sending and receiving messages while SMS notifications only is used for sending messages to the subscriber. This section describes the different End User Notifications the Charging System can send to the subscriber.

3.4.1

USSD Notifications
In Figure 5 an example of USSD end-of-call notification is shown. If end-of-call notification is enabled, these steps always follows at the end of a call.

8

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Common for all Traffic Cases

MSC/SSF
1 2

CCN

SDP

HLR

3 4 5 6

Figure 5

USSD Notifications

1. The call is released. 2. The MSC sends information to the SSF about the call, and the SSF sends an Intelligent Network Application Protocol (INAP) message to CCN about the disconnection. 3. CCN analyses the disconnection from the mobile phone and sends information about the call to SDP for rating. 4. SDP calculates the cost for the service. Then a text string is composed in the correct language and currency and if necessary the country code is added to the MSISDN. SDP sends the composed USSD message to the HLR. 5. The HLR transfers the USSD message to the correct MSC. 6. The MSC sends the USSD message to the subscribers mobile phone and the result is shown on the display.

3.4.2

SMS Notification
In Figure 6 an example of SMS end-of-call notification is shown. If end-of-call notification is enabled it is always performed at the very end of a call.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

9

Traffic Cases

MSC/SSF
1 2

CCN

SDP

SMS-C

3 4 5

Figure 6

SMS Notification

1. The service is disconnected. 2. The MSC sends information to the SSF, and the SSF sends a message to CCN about the disconnection. 3. CCN analyses the disconnection from the mobile phone and sends information about the call to SDP for rating. 4. SDP calculates the cost for the service. Then a text string is composed in the correct language and currency and if necessary the country code is added to the MSISDN. SDP sends the composed SMS message to the SMS-C. 5. The SMS-C sends the SMS message to the subscribers mobile phone and the result is shown on the display.

3.5

SDP Selection
Charging System supports scalability of accounts by adding SDP network elements. This means that accounts in Charging System may be distributed over several SDPs. To locate which SDP a specific account resides on, the Domain Name Service (DNS) database in the Account Finder (AF) is used. CCN uses AF to identify which SDP a call or session should be routed to. CCN can use either AF lookup, service key routing or number series routing towards SDPs. Which of the methods that are used is configured in CCN. It is also possible to configure CCN to cache the AF lookups in order to limit the number of requests to AF.

3.5.1

Static SDP Selection
In static SDP Selection, there is only one SDP.

10

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Common for all Traffic Cases

3.5.2

Service Key Selection
The service keys can be used for routing to the correct SDP when multiple SDPs are used. The Service keys are passed from the SSF to CCN.

3.5.3

MSISDN Selection
CCN gets the MSISDN from the IDP then SDP is selected according to the caller’s MSISDN.

3.5.4

Account Finder Selection
Account finder selection can in some cases replace service key routing. Account finder selection is not included in any of the flow charts in this document, but when active, it is performed immediately before the first interrogation is sent to SDP. In Figure 7 an example of Account Finder Selection is shown.

CCN

AF

1 2

Figure 7

Account Finder Selection

1. CCN sends the MSISDN to AF requesting which SDP the call should be routed to. 2. AF uses the MSISDN to identify the SDP and sends the result back to CCN.

3.6

Subscription ID Independence
Charging System supports other subscription identifiers than MSISDN when accessing CCN. This requires that account finder selection is used for SDP selection. CCN then sends the received subscription identifier to AF and receives which SDP to route to and the MSISDN of the subscription. The MSISDN is then used when communicating with SDP.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

11

Traffic Cases

12

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

4

Traffic Cases
This section describes the different call and service types that are supported by Charging System. In the traffic cases following, Mobile Number Portability (MNP) and Location Based Charging is not used, if it is not stated. For information about MNP, see Section 3.1 on page 5 and Section 3.3 on page 6 for Location Based Charging.

4.1

Real-Time Charging Services
The Charging System can supervise charged sessions in real time. The Charging System subscribers have the possibility to make and receive real-time calls when roaming outside the Home Public Land Mobile Network (HPLMN). A Charging System subscriber can be prevented from making calls when roaming outside the HPLMN. This is decided by business configurations and roaming agreements. To allow for efficient call handling in the HPLMN, the network operator can offer the capabilities of the Ericsson proprietary feature Extended CAMEL. With this feature, the subscriber triggers Charging System using INAP CS1+ in the HPLMN and CAMEL in the VPLMN. This chapter describes different types of real-time Charged calls.

4.1.1

Charged Calls (CS1+)
This chapter describes the traffic cases for charged calls CS1+. For an overview of the traffic cases, see Table 1.

Table 1
Description

Overview of Traffic Case, Charged Calls CS1+
Involved Charging System Network Elements CCN and SDP. CDR Gener ation in the Charging System CCN or the MSC/SSF. Applies to

The Charging System supervises each charged call in real time. A Charging System account can never be overdrawn. If a subscriber tries to make a call when the Service Scenario or account value limits has been reached then the call will never be established. If a subscriber runs out of money on the account, the call will be disconnected by the Call Cut-off procedure.

Originating, Terminating, and Forwarded Calls in the HPLMN and Terminating Calls in the VPLMN.

In Figure 8, an originating charged call, with CS1+, is shown. This is followed by an explanation of all steps in the figure. Terminating and Forwarded calls work in a similar fashion in a Charging System point of view and is not shown in detail here.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

13

Traffic Cases

MSC/SSF
1 2 5 6

CCN
3 4

SDP

7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

Figure 8

Originating Charged Call, CS1+

1. A call is initiated from a charging system subscriber. The Originating IN Category Key (OICK) of the subscriber in the VLR, routes the call to the SSF. 2. The SSF collects data about the call and triggers CCN. 3. CCN performs a SDP selection and sends the data, collected in step 2, in a first interrogation to SDP. Optionally, CCN performs an MNP lookup or an LBC lookup, or both, at this stage. 4. SDP reserves money from the account and sends the calculated call time to CCN, together with other call data such as announcements to be played. 5. CCN tells the SSF to play announcements if this has been requested by SDP. Further on, CCN tells the SSF to setup the call and to supervise it based on the call time calculated by SDP. 6. The call lasts longer than the call time sent to the SSF, so a notification is sent to CCN. 7. CCN requests SDP to make another reservation from the account with an intermediate interrogation.

14

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

8. SDP makes a new charging analysis and deducts the amount previously reserved from the account. In this example it is assumed that there is still sufficient funds left on the subscriber’s account. SDP then reserves money for the next period and forwards a new call time to CCN. 9. CCN passes the new call time on to the SSF. Note: Step 6–9 can be repeated several times. In this example, steps 10–17 describes what happens when the subscriber's account balance reaches the account empty limit. 10. The call lasts longer than the call time sent to the SSF and a notification is sent to CCN. 11. CCN requests SDP to make another reservation from the account with an intermediate interrogation. 12. SDP makes a new charging analysis and updates the account. The charging analysis shows that there is not enough money on the account to cover the requested period. SDP sends the calculated call time to CCN together with an indication that there is no money left on the account and that a call cutoff warning announcement is to be played. The time between the warning announcement and call cutoff can be configured. For this example 30 seconds is used. 13. CCN uses the 30 seconds indication from SDP and the time between call cutoff warning and call cutoff is excluded from the new call time. CCN then passes the new call time on to the SSF. 14. The SSF notifies CCN that the time sent down in step 13 has expired. 15. CCN sends the remaining 30 seconds and tells the SSF to play the call cutoff warning announcement. 16. The SSF notifies CCN that the final 30 seconds has expired. 17. CCN tells the SSF to play the call cutoff announcement and to disconnect the call. 18. The SSF notifies CCN of the call disconnection. 19. A final report is sent from CCN to SDP. SDP performs final charging of the call. 20. SDP rates the total call and sends a final report result to CCN. 21. CCN sends a call release to the SSF. Note: If end-of-call notification is enabled a notification is sent to the subscriber, see Section 3.4.1 on page 8.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

15

Traffic Cases

4.1.2

Charged Calls (ERTC)
This chapter describes the traffic cases for Charged Call ERTC. For an overview of the traffic cases, see Table 2.

Table 2
Description

Overview of Traffic Cases, Charged Calls ERTC
Involved Charging System Network Elements CCN and SDP. CDR Generation in the Charging System CCN Applies to

Charged Calls ERTC enables real time charging through the MSC in the HPLMN without the invocation of IN or CAMEL. When roaming outside the HPLMN the subscriber can have a CAMEL trigger to provide for CAMEL roaming.

Originating, Terminating, and Forwarded Calls in the HPLMN and Terminating Calls in the VPLMN

In Figure 9, a mobile originating charged call with Real Time Charging for All (RTCfA) is shown. Terminating calls work in a similar fashion in a charging system point of view. If a forwarded call triggers the Charging System, two sessions, one terminating and one originating, are executed through the Charging System to charge for the forwarded call.

MSC
1 2

CCN

SDP

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Figure 9

Originating Charged Call, ERTC

1. A call is initiated from the subscriber. 2. The MSC collects data about the call and triggers CCN.

16

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

3. The data collected from the MSC is mapped to a first interrogation in CCN. CCN makes an SDP selection and sends the data, collected in step 2, to SDP where the service scenario of the account is checked and a preliminary charging analysis takes place. 4. SDP reserves money from the account and sends the calculated call time to CCN, together with other call data such as announcements to be played. 5. CCN stores the call data received from SDP. CCN sends a reply to allow the call to continue. 6. The call lasts longer than the call time calculated. The MSC requests CCN for a new reservation. 7. CCN forwards the request to SDP to make another reservation from the account with an intermediate interrogation. 8. SDP makes a new charging analysis and deducts the amount previously reserved from the account. There is still sufficient funds on the subscriber's account, so SDP sends back a new reservation period to CCN. 9. CCN passes on the interrogation result to the MSC. Note: Step 6–9 can be repeated several times. In this example, the following steps describe what happens when the balance on the subscriber's account reaches the account empty limit. 10. The MSC call leg monitoring detects that the call reservation is due to be extended. The MSC requests CCN for a new reservation. 11. CCN forwards the request to SDP to make another reservation from the account with an intermediate interrogation. 12. SDP makes a new charging analysis and deducts the amount previously reserved from the account. The charging analysis shows that there is not enough money on the account to cover another full requested period. SDP sends the calculated maximum call time to CCN, together with a call cutoff warning announcement. 13. CCN forwards this information to the MSC. The MSC call leg monitoring detects that it is time for the call cutoff warning announcement. The MSC plays the announcement to the subscriber and then orders the call to be released. 14. The MSC releases the call, collects data about the call and sends it to CCN. 15. CCN acknowledges the call release to the MSC. 16. A final report is sent from CCN to SDP. 17. SDP calculates the total cost of the call and sends a final report result to CCN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

17

Traffic Cases

Note:

If end-of-call notification is enabled a notification is sent to the subscriber, see Section 3.4.2 on page 9.

4.1.3

Toll-Free Calls (ERTC)
This chapter describes the traffic case for Toll-Free Call ERTC. For an overview of the traffic case, see Table 3.

Table 3
Description

Overview of Traffic Case, Toll-Free Calls ERTC
Involved Charging System Network Elements CCN and SDP. CDR Gener ation in the Charging System CCN Applies to

The Charging System Operators can offer Toll-Free Numbers to their Charging System subscribers. They are stored in the Service Class of the subscriber or on a service level. Toll-Free Numbers on a service level are available to subscribers of all Service Classes.

Originating and Forwarded calls in the HPLMN.

The following, see Figure 10, applies for a originating toll-free call with RTCfA.

MSC
1 2

CCN

SDP

3 4 5

Figure 10

Toll-Free Call , ERTC

1. A call is initiated from a subscriber. 2. The MSC collects data about the call and triggers CCN. 3. A first interrogation is sent to SDP where the service scenario of the account is checked and a analysis takes place. The output from the analysis indicates that this is a toll-free call. SDP is configured so no CDRs are generated for Toll-free calls. Note: It can be configured whether a CDR is to be generated or not in CCN for toll-free calls. The generated CDR can be used for statistical purposes. If a CDR is to be generated, or call setup result is to be sent to SDP, then a final report is sent to SDP.

4. SDP returns the charging analysis result to CCN. 5. CCN forwards the result to the MSC. The Charging System has no further involvement in the call.

18

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

4.1.4

SMS IN Triggered Charging (CS1+)
This chapter describes the traffic case SMS IN Triggered Charging. For an overview of the traffic case, see Table 4.

Table 4
Description

Overview of Traffic Case, SMS IN Triggered Charging (CS1+).
Involved Charging System Network Elements CCN and SDP. CDR Generatio n in Charging System CCN or the MSC/SSF Applies to

IN triggered SMS charging allows the network operator to charge for short message transactions in real-time without using CAMEL. The Charging System will intercept the short message in the MSC/VLR and simulate a regular Charging System call.

Originating and Terminating short messages in the HPLMN and Terminating in the VPLMN.

This example, see Figure 11, describes SMS IN triggered originating charging with two interrogations. One for checking the account balance and one for deducting the cost of the SMS. Terminating calls work in a similar fashion in a charging system point of view and is not shown i detail here.

SMS-C

MSC/SSF
1 2

CCN

SDP

3 4 5 6 7 8 9 10 11 12 13

Figure 11

IN Triggered SMS, CS1+

1. An SMS is sent based on OICK and the destination address routes it to the SSF. 2. The SSF collects data about the call and triggers CCN to check the account. 3. The data, collected in step 2, is sent in a first interrogation to SDP, where the service scenario of the account is checked and a preliminary charging analysis takes place. No reservation of money is performed in this step. 4. SDP sends the result of the interrogation to CCN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

19

Traffic Cases

5. CCN sends a successful result to the SSF. 6. The MSC delivers the SMS to the SMS-C. 7. The delivery of the SMS is confirmed by the SMS-C. 8. The MSC/SSF triggers CCN to deduct the fee of the SMS. 9. CCN sends a first interrogation to SDP where the service scenario of the account is checked and a preliminary charging analysis takes place. 10. SDP reserves money from the account and sends a successful result, together with other call data, to CCN. 11. CCN sends a final report to SDP. 12. SDP rates the total cost, deducts money from the account and sends a final report result to CCN. 13. CCN sends a release operation with a successful deduct code to the MSC/SSF. Note: If end-of-call notification is enabled a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.5

SMS Charging based on CAMEL Phase 3
This chapter describes the traffic case SMS Charging based on CAMEL Phase 3. For an overview of the traffic case, see Table 5.

Table 5
Description

Overview of Traffic Case, SMS Charging Based on CAMEL phase 3
Involved Charging System Network Elements CCN and SDP. CDR Generation in the Charging System CCN Applies to

CAMEL phase 3 SMS charging allows the operator to charge for mobile originating SMS in real time. This traffic case always interacts twice with the Charging System, once to check the account balance and once at delivery to the SMS-C to deduct the cost from the account. Both Circuit Switched (CS) and Packet Switched (PS) Mobile Originating SMS is supported.

Originating SMS in both the HPLMN and the VPLMN.

The preconditions for the traffic case, SMS charging based on CAMEL phase 3, are described in the bullet list below. • • • • • The SMS is Circuit Switched (CS). All network elements are located in the HPLMN. The SMS is charged, not toll free. The MNP is active. The community charging is active.

20

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

• •

The subscribers account is an preactivated account (life cycle notification). There are sufficient funds left on the subscriber’s account for the SMS (money available).
MSC/SSF
1 2 3

SMS-C

CCN

SDP

4 5 6 7 8 9

Figure 12

SMS Charging based on CAMEL Phase 3

1. An originating SMS is received by the MSC/SSF. 2. The MSC/SSF analyses the data and interrogates the serving CCN. 3. CCN interrogates SDP. Optionally, an MNP lookup can be performed here, see Section 3.1 on page 5. 4. SDP verifies the account status, reserves money and sends the result to CCN. If Community Charging is enabled it is performed at this stage, see Section 3.2 on page 5. 5. CCN replies to the interrogation from the SSF based on the result from SDP. 6. The MSC/SSF delivers the SMS to the SMS-C. 7. The SMS-C confirms the delivery of the SMS. 8. The MSC/SSF forwards the result to CCN. 9. CCN forwards the result to SDP. SDP charges the corresponding account. Note: If end-of-call notification is enabled a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.6

SMS Charging (ERTC)
This chapter describes the traffic case SMS Charging based on ERTC. For an overview of the traffic case, see Table 6.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

21

Traffic Cases

Table 6
Description

Overview of Traffic Case, SMS Charging Based on ERTC
Involved Charging System Network Elements CCN and SDP. CDR Gener ation in the Charging System CCN. Applies to

SMS Charging based on ERTC allows the network operator to charge for short message transactions in real-time without using CAMEL or IN. The Charging system will intercept the short message in the MSC. This traffic case will always interact twice with the Charging System, once to check the account balance and once at delivery to the SMS-C to deduct the cost from the account.

Originating and Terminating SMS in the HPLMN

The following, see Figure 13, applies for a originating SMS with RTCfA. A Terminating SMS work in a similar fashion in a Charging System point of view and is not shown here.

MSC
1 2

CCN

SDP

SMS-C

3 4 5 6 7 8 9 10 11

Figure 13

Originating SMS Charging, ERTC

1. A subscriber sends an SMS and it is received by an MSC. 2. The MSC sends an SMS indication to CCN to initiate an SMS charging session. 3. In CCN, the data collected from the MSC is mapped to a first interrogation. 4. The first interrogation is sent to SDP, where the service scenario of the account is checked and a preliminary charging analysis takes place. SDP reserves money from the account and sends the result to CCN. 5. CCN replies to the MSC with the result. 6. The MSC delivers the SMS to the SMS-C. 7. The SMS-C confirms the reception of the SMS to the MSC. 8. After successful delivery to SMS-C, the MSC sends a message to CCN, to charge for the SMS.

22

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

9. A final report is sent from CCN to SDP. SDP performs a final charging of the SMS. 10. SDP reports the total cost of the SMS and sends a final report result to CCN. 11. CCN replies with the result of the charging session to the MSC. Note: If end-of-call notification is enabled a notification is sent to the subscriber, see Section 3.4.2 on page 9.

4.1.7

GPRS Charging based on CAMEL Phase 3
This chapter describes the traffic case GPRS Charging Based on CAMEL Phase 3. For an overview of the traffic case, see Table 7.

Table 7
Description

Overview of Traffic Case, GPRS Charging Based on CAMEL Phase 3
Involved Charging System Network Elements CCN and SDP. CDR Generation in the Charging System CCN. Applies to

GPRS Charging based on CAMEL phase 3, enables charging of packet switched traffic in real-time.

Originating traffic in the HPLMN and the VPLMN.

4.1.7.1

TDP at PDP Context Establishment Acknowledgement Figure 14 Illustrates Trigger Detection Point (TDP) at Packet Data Protocol (PDP) context establishment acknowledgement.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

23

Traffic Cases

SGSN/ gprsSSF
1

CCN

SDP

HLR

2 3

4 5 6 7 8 9 10 11 12 13 14 15

Figure 14

TDP at PDP Context Establishment Acknowledgement

1. The subscriber initiates a data transfer. This initiates a PDP context in the SGSN. 2. An interrogation is made to the HLR. 3. Data is sent from the HLR, containing subscriber information such as CAMEL Subscription Information (CSI). The call is routed to the gprsSSF. 4. The SGSN triggers CCN to check if the PDP context is allowed to continue. 5. The first interrogation is sent to SDP where the service scenario of the account is checked and a preliminary charging analysis takes place. 6. SDP reserves money from the account and sends the result to CCN. 7. CCN passes the information on to the SGSN. CCN also tells the SGSN to set up the session and to supervise it. 8. The SGSN notifies CCN about reached limit. 9. CCN requests SDP to make another reservation from the account with an intermediate interrogation. 10. SDP rates the event and sends the result to CCN. 11. CCN passes the new limit to the SGSN.

24

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

Note:

Step 8–11 can be repeated several timed.

12. The SGSN notifies CCN that the user has ended the session. 13. CCN sends a final report to SDP. 14. SDP calculates the total cost of the session and sends a final report result to CCN. 15. CCN tells the SGSN to disconnect the charging session. Note: If end-of-call notification is enabled, a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.8

Service Charging based on Diameter, Draft-8
This chapter describes the traffic cases Service Charging based on Diameter, Draft-8. For an overview of the traffic cases, see Table 8.

Table 8
Description

Overview of Traffic Cases, Service Charging based on Diameter, Draft-8.
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System SDP Applies to

Service charging using SCAP over Diameter, Draft-8, enables charging of content based services in real time using either: • Session based charging with price determined by the service network. • Session based charging with price determined by the Charging System. • Direct debit of pre-rated events. • Refund

Originating sessions.

4.1.8.1

Service Charging, Diameter, Draft-8, Event Based (Direct Debit) This chapter describes the traffic case Service Charging, Diameter, Draft-8, Event Based. Figure 15 illustrates Diameter, Draft-8, event based service charging (direct debit).

2/1551-FAV 101 72/4 Uen B | 2011-02-11

25

Traffic Cases

Service node
1 2

CCN

SDP

3 4 5 6 7

Figure 15

Service Charging, Diameter, Draft-8, Event based (Direct Debit)

1. The subscriber accesses a charged service. 2. The service application checks the subscriber and connects to CCN. 3. A first interrogation is sent to SDP where the service scenario of the account is checked and a charging analysis is performed. 4. SDP reserves money and sends the result back to CCN. 5. CCN immediately sends a final report to SDP. 6. SDP deducts the reserved funds from the account and return a final report result to CCN. 7. CCN sends back a confirmation to the service application that the direct debit has been successfully executed. Note: If end-of-call notification is enabled, a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.8.2

Service Charging, Diameter, Draft-8, Session Based This chapter describes the traffic cases Service Charging, Diameter, Draft-8, Session Based. Figure 16 illustrates Diameter, Draft-8, session based service charging.

26

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

Service node
1 2

CCN

SDP

3 4 5 6 7 8 9 10 11 12 13

Figure 16

Service Charging, Diameter , Draft-8, Session

1. A subscriber accesses a charged service. 2. The service application checks the subscriber and connects to CCN. 3. CCN interrogates SDP. 4. SDP checks the account status. If required, SDP rates and reserves money. The result is returned. 5. CCN tells the serving network element to continue and monitor the session. 6. The service application notifies CCN that a limit has been reached 7. CCN requests SDP to make another reservation from the account with an intermediate interrogation. 8. SDP rates the event and sends the result to CCN. 9. CCN passes the new limit to the service application. Note: Step 6–9 can be repeated a number of times.

10. The service application notifies CCN that the user has ended the session. 11. CCN sends a final report to SDP. 12. SDP calculates the total cost of the session and sends a final report result back to CCN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

27

Traffic Cases

13. CCN tells the service application to disconnect the charging session. Note: If end-of-call notification is enabled, a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.9

Service Charging based on DCCA
This chapter describes the traffic cases Service Charging based on Diameter Credit Control Application (DCCA). For an overview of the traffic cases, see Table 9.

Table 9
Description

Overview of Traffic Cases, Service Charging based on DCCA.
Involved Charging System Network Elements CCN and SDP CDR Gener ation in the Charging System SDP Applies to

Service charging using SCAPv2 over DCCA enables online credit control of content based services using either: • Immediate Event Charging (IEC). Event charging, without reservation. • Event Charging with Unit Reservation (ECUR). Session based event charging. • Session Charging with Unit Reservation (SCUR). Service charging using Gy over DCCA enables online credit control of content based services using: • Session Charging with Unit Reservation (SCUR). • The charging scenarios above are available with both of the following combinations: • Decentralized unit determination and centralized rating • Centralized unit determination and centralized rating

Origin ating Sessions.

4.1.9.1

Service Charging, DCCA Direct Debit Figure 17 illustrates DCCA direct debit service charging.

28

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

Service node
1 2

CCN

SDP

3 4 5

Figure 17

Service Charging, DCCA Direct Debit

1. A subscriber accesses a charged service. 2. The service application checks the subscriber and connects to CCN. 3. A first interrogation is sent to SDP where the service scenario of the account is checked and a charging analysis is performed. 4. SDP deducts funds from the account and return a final report result to CCN. 5. CCN sends back a confirmation to the service application that the direct debit has been successfully executed. Note: If end-of-call notification is enabled, a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.9.2

Service Charging, DCCA Session Figure 18 illustrates DCCA session service charging.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

29

Traffic Cases

Service node
1 2

CCN

SDP

3 4 5 6 7 8 9 10 11 12 13

Figure 18

Service Charging, DCCA Session

1. A subscriber accesses a charged service. 2. The service application checks the subscriber and connects to CCN. 3. CCN interrogates SDP. 4. SDP checks the account status. If required, SDP rates and reserves money. The result is returned. 5. CCN tells the serving network element to continue and monitor the session. 6. The service application notifies CCN that a limit has been reached 7. CCN requests SDP to make another reservation from the account with an intermediate interrogation. 8. SDP rates the event and sends the result back to CCN. 9. CCN passes the new limit to the service application. Note: Step 6–9 can be repeated a number of times.

10. The service application notifies CCN that the user has ended the session. 11. CCN sends a final report to SDP. 12. SDP calculates the total cost of the session and sends a final report result back to CCN.

30

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

13. CCN tells the service application to disconnect the charging session. Note: If end-of-call notification is enabled, a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.10

Optimized Signalling for Bonus on Incoming Call, (CS1+)
This chapter describes the traffic cases Optimized Signalling for Bonus on Incoming Call. For an overview of the traffic case, see Table 10.

Table 10
Description

Optimized Signalling for Bonus om Incoming Call CS1+
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System CCN or MSC/SSF Applies to

Optimized Signaling for Bonus on Incoming Calls (BIC) solves a specific operator’s requirements on bonus generated on terminating traffic. The purpose of this feature is to reduce the number of interactions between CCN and SDP for terminating calls and thus reduce the traffic load in these network elements and in the signaling network.

Terminat ing calls in the HPLMN.

An example of optimized signalling for bonus on incoming call, is illustrated in Figure 19.

MSC/VLR
1

GMSC/SSF
2

CCN

SDP

HLR

3 4 5
Called party answers

6 7

Call disconnect

8 9 10 11 12

Figure 19

Optimized Signalling for Bonus on Incoming Call, CS1+

1. A call is initiated to a Charging System subscriber. 2. An interrogation is made to the HLR. 3. Data is sent from the HLR containing information such as TICK. The call is routed to the SSF.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

31

Traffic Cases

4. The SSF collects data about the call and triggers CCN. 5. CCN tells the SSF to monitor called party answer. 6. At called party answer the SSF sends a response to CCN. 7. CCN tells the SSF to monitor called and calling party disconnection. 8. At called or calling party disconnection the SSF sends an indication to CCN. CCN calculates the duration of the call. 9. The calling party number belongs to a Public Switched Telephone Network (PSTN), so a first interrogation (without rating) is sent to SDP, that establishes if Family and Friends (FaF) has to be applied for the call. 10. The result of the first interrogation is sent to CCN. 11. A final report is sent from CCN to SDP. It contains the FaF parameters received in the first interrogation. 12. SDP rates the total call and adds bonus, based on the call duration, to the called party account. SDP then returns the result to CCN. Depending on the configuration a CDR is generated. Note: If end-of-call notification is enabled, a notification is sent to the subscriber, see Section 3.4.1 on page 8.

4.1.11

Roaming Calls based on CAMEL Phase 1
This chapter describes the traffic case Roaming Calls based on CAMEL Phase 1. For an overview of the traffic case, see Table 11.

Table 11
Description

Overview of Traffic Cases, Roaming Originating Calls based on CAMEL Phase 1
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System CCN or the SSF in the HPLMN Applies to

Roaming Calls based on CAMEL Phase 1 enables roaming by routing the speech path from the VPLMN to the HPLMN. This means that all calls are routed through the HPLMN. Example: The Charging System subscriber is making a call from a VPLMN to a subscriber in the same PLMN. The speech connection is setup through the HPLMN. CAMEL features are used to redirect the call to the HPLMN where the INAP CS1+ based Charging System service controls and monitors the call.

Originating and Forwarded Calls in the VPLMN.

Figure 20 illustrates a roaming originating call with CAMEL phase 1. A roaming forwarded call work in a similar fashion in the charging system and is not shown in detail here.

32

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

MSC/SSF
1 2

SSF

CCN

3 4 5

VPLMN HPLMN

Figure 20

Roaming Originating CAMEL Phase 1

1. The call is initiated from a subscriber roaming in a VPLMN. The Originating CSI (O-CSI) in the VLR routes the call to the SSF. 2. The SSF triggers and initiates CCN in the HPLMN. 3. CCN checks if all mandatory data is received and stores this data. CCN tells the SSF to reroute the call to the SSF in the HPLMN. 4. The SSF routes the call to the HPLMN using the SCP-id, in international format, as called party. 5. The SSF in the HPLMN initiates CCN. Data for the call, stored in step 3, is retrieved. Note: From now on the call works the same way as for a Originating CS1+ call, see Section 4.1.1 on page 13.

4.1.12

Charged Calls Based on CAMEL Phase 2
This chapter describes the traffic case charged calls based on CAMEL Phase 2. For an overview of the traffic case, see Table 12.

Table 12
Description

Overview of Traffic Cases, Roaming Originating Calls based on CAMEL Phase 2
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System CCN in the HPLMN Applies to

Charging System supports roaming outside the HPLMN with help of the protocol CAPv2. Extended CAMEL allows CS1+ functions in the home network together with CAPv2 functions in the visited network. Example: The Charging System subscriber makes a call from a VPLMN to a subscriber in the same PLMN, all call handling such as call monitoring of call duration is performed by the gsmSSF in the VPLMN.

Originating and Terminati ng Calls in the VPLMN and the HPLMN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

33

Traffic Cases

Figure 21 illustrates a roaming originating call with CAMEL phase 2. A terminating call work in a similar fashion in a Charging System point of view and is not shown in detail here.

MSC/SSF
1 2

SSF

SRF

CCN

SDP

3 4 5 6 7 8 9 10 VPLMN HPLMN

Figure 21

Roaming Originating CAMEL Phase 2

1. A call is initiated from a Charging System subscriber roaming in a VPLMN. The O-CSI in the VLR routes the call to the SSF. 2. The SSF in the VPLMN initiates CCN in the HPLMN. CCN processes the data. 3. The data, received in step 2, is sent to SDP where the service scenario of the account is checked and a preliminary charging analysis and reservation of funds are performed. 4. SDP sends the result of the calculated call time together with call data such as announcements to be played back to CCN. Note: Step 5–9 are only executed if an announcement is played. Playing announcements from the HPLMN is optional.

5. CCN tells the SSF in the VPLMN to connect to a assisting SSF in the HPLMN. 6. A call setup announcement is to be played, so the SSF in the VPLMN connects to the assisting SSF in the HPLMN. If the connection attempt to assisting SSF fails, CCN initiates retry attempts to the same or other defined assisting SSF. 7. The assisting SSF requests instructions from CCN. 8. CCN tells the assisting SSF to play announcements. 9. The assisting SSF tells the SRF to play an announcement.

34

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

10. CCN tells the SSF in the VPLMN to setup the call and to supervise it based on the call time calculated by SDP. Note: From now on the call is processed in the same way as for a originated CS1+ call, see Section 4.1.1 on page 13.

4.1.13

Charged Call Based on CAMEL Phase 2, Pre-Call Replenishment
This chapter describes the traffic case charged calls based on CAMEL phase 2 inside HPLMN when the Pre-Call Replenishment (PCR) function is active. For an overview of the traffic case, see Table 13.

Table 13
Description

Overview of Traffic Cases, Pre-Call Replenishment
Involved Charging System Network Elements SDP and CCN. CDR Gener ation in the Charging System CCN in the HPLMN Applie s to

The Charging System subscriber makes a call from HPLMN. The subscriber does not have enough money on the account and the PCR function is active. The subscriber gets routed to the IVR.

Origin ating Calls in the HPLM N.

Figure 22 illustrates a charged calls based on CAMEL phase 2 inside HPLMN when the PCR function is active.
MSC/gsmSSF
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Assisting SSF

CCN

SDP

Figure 22

Pre-Call Replenishment

1. An originating CAPv2 call is initiated from a Charging System subscriber inside HPLMN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

35

Traffic Cases

2. The SSF collects data about the call and triggers CCN. 3. A first interrogation is sent to SDP where the service scenario of the account is checked and a charging analysis is performed. 4. SDP sends the result indicating either low balance, insufficient balance, or account expiry. In case of low balance, the SDP sends calculated call time. Announcements could also be sent. Note: Steps 8-10 are only executed if call setup announcements are to be played.

5. CCN instructs the MSC/gsmSSF to connect the call to an assisting SSF. 6. MSC/gsmSSF connects to the assisting SSF. If the connection attempt to assisting SSF fails, CCN initiates retry attempts to the same or other defined assisting SSF. 7. The assisting SSF requests instructions from CCN. 8. CCN instructs the assisting SSF to play announcements. 9. The assisting SSF instructs the gsmSRF to play announcement. 10. Assisting SSF informs CCN that the announcements are finished. 11. CCN instructs assisting SSF to play menu options to the subscriber to refill the account or to continue the call. 12. Assisting SSF reports selected menu option to CCN. 13. CCN instructs the assisting SSF to play announcement to indicate that the call is being transferred to perform replenishment (if refill) or that the call is being connected (if selected menu option is to continue the call) 14. Assisting SSF informs CCN that announcement is finished. Continue with step 15 when selected menu option is refill. Otherwise, if selected menu option is to continue the call continue with step 16. 15. CCN instructs the MSC/gsmSSF to connect to IVR. Note: From now on the call is processed in the same way as described in Section 4.3.1.2 on page 51. CCN is not involved in the call any more. The subscriber will have to dial the destination number again to get connected.

16. CCN instructs the MSC/gsmSSF to setup the call and supervise it based on the call time calculated by SDP. Note: From now on the call is processed in the same way as for an originated CS1+ call, see Section 4.1.1 on page 13.

36

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

4.1.14

Charged Call Based on CAMEL Phase 2, Personal Greeting Service
This chapter describes the traffic case charged calls based on CAMEL phase 2 inside and outside HPLMN when the Personal Greeting Service (PGS) function is active. For an overview of the traffic case, see Table 14.

Table 14
Description

Overview of Traffic Cases, Personal Greeting Service
Involved Charging System Network Elements CCN CDR Generation in the Charging System CCN in the HPLMN and the SSF in the VPLMN Applies to

The Charging System subscriber makes a call from HPLMN. The PGS function is active.

Terminating calls inside and outside HPLMN

Figure 22 illustrates a charged calls based on CAMEL phase 2 inside and outside HPLMN when the PGS function is active.
MSC/gsmSSF
1 2 3 4 5 6 7 8 9 10 11 12 13

IP Player

CCN

SDP

Figure 23

Personal Greeting Service

1. A terminating CAPv2 call is initiated from a Charging System subscriber inside or outside HPLMN. 2. The SSF collects data about the call and triggers CCN. 3. A first interrogation is sent to SDP where the service scenario of the account is checked and a charging analysis is performed. 4. SDP sends the result indicating sufficient balance. The SDP sends calculated call time. 5. If caller is subscribed to PGS, CCN requests the MSC/gsmSSF to setup the call and triggers PGS announcement establishment towards assisting SSF. PCR or call setup announcements, if ordered by SDP, will be played prior to the PGS announcements

2/1551-FAV 101 72/4 Uen B | 2011-02-11

37

Traffic Cases

6. MSC/gsmSSF connects to the IP player. If the connection attempt to IP fails, CCN initiates retry attempts to the same or other defined IP. 7. The IP player requests instructions from CCN. 8. CCN instructs the IP player to play PGS announcements. 9. Continue operation is sent from CCN to SSF. 10. At called party answer the SSF sends a response to CCN. 11. CCN informs the MSC/gsmSSF to disconnect the IP player. 12. Disconnects SRF if not already disconnected. This step is optional depending on MSC vendor type. 13. The call is now connected and CCN supervises the call based on the call time calculated by SDP. From here the call continues as a normal charged call

4.1.15

Charged Call Based on CAMEL Phase 2, Charging of Voice Calls Before B-Answer
This chapter describes the traffic case charged calls based on CAMEL phase 2 inside and outside HPLMN when the charging of voice calls before B-answer function is active. For an overview of the traffic case, see Table 15.

Table 15
Description

Overview of Traffic Cases, Charging of Voice Calls Before B-Answer
Involved Charging System Network Elements CCN, SDP CDR Generation in the Charging System CCN in the HPLMN and the SSF in the VPLMN Applies to

The Charging System subscriber makes a call from HPLMN. The charging of voice calls before B-answer function is active.

Originating calls inside and outside HPLMN

The call flow for charging of voice calls before B-answer is the same as for a charged call based on CAPv2, see Section 4.1.12 on page 33, except that charging of the call starts at reception of First Interrogation Result (FIR) from SDP instead of when the call is answered. The function is only applicable for MO CAPV2 calls when CIP/IP is used and the following conditions are met: • • • Subscriber’s service class is a service class with charging of voice calls before B-answer functionality active. The subscriber makes an originating call. The originating call is allowed, that is, the subscriber has enough money on the account, and the call is to be charged.

38

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

The subscriber will be charged if the call duration before answer is longer than or equal to the configuration for free of charge period for unsuccessful call setup in the following cases: • • The call is not answered before the granted time expiry. The call is not successfully connected.

If the subscriber has low balance and the PCR function is active, no charging is made for the time prior and during the PCR.

4.1.16

Forwarded CAMEL Phase 2
This chapter describes the traffic case Forwarded Calls based on CAMEL Phase 2. For this traffic case there are two possible scenarios: • • Call forwarding in GMSC (early call forwarding). Call forwarding in MSC/VLR (late call forwarding).

4.1.16.1

Early Call Forwarding The first possible scenario for forwarded CAMEL Phase 2, call forwarding in GMSC (early call forwarding), is shown in Figure 24. An overview of the traffic case is shown in Table 16.

Table 16
Description

Overview of Traffic Cases, Early Call Forwarding
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System CCN Applies to

If the subscriber has call forwarding, there is a parameter available to decide how the charging will be performed for early call forwarding. The parameter decides if both the roaming terminating leg and the roaming forwarded leg should be charged or only the roaming forwarded leg.

Works in a similar way both ine HPLMN and the VPLMN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

39

Traffic Cases

MSC/VLR

GMSC/SSF
1 2

CCN

HLR

3 4 5 6 7 8 9 VPLMN HPLMN

Figure 24

Early Call Forwarding

1. A call is initiated to a subscriber roaming in a VPLMN. 2. An interrogation is made to the HLR. 3. The HLR fetches current subscriber location data from the VLR in the VPLMN. 4. The VLR sends subscriber location data to the HLR. 5. Data is sent from the HLR, containing information like Call Forwarding Unconditional (CFU) and T-CSI indication, and the call is routed to the SSF. 6. The SSF in the HPLMN triggers CCN where data about the call is collected. 7. CCN tells the SSF in the HPLMN to setup the call. 8. The HLR is again interrogated, now with T-CSI suppression and the call forwarding setting and O-CSI is found. 9. The HLR returns call forwarding settings and O-CSI to GMSC. Note: From now on the call is processed as a originating call, see Section 4.1.1 on page 13.

4.1.16.2

Late Call Forwarding The second possible scenario for roaming forwarded CAMEL phase 2, call forwarding in MSC/VLR (late call forwarding), is shown in Figure 25. An overview of the traffic case is shown in Table 17.

40

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

Table 17
Description

Overview of Traffic Cases, Late Call Forwarding
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System CCN Applies to -

At Late Call Forwarding the service manages the calls in a similar fashion as for forwarded calls in the HPLMN. Both originating and terminating leg is charged unless Optimal Routing at Late Call Forwarding is used. For more information about Optimal Routing at Late Call Forwarding, see Section 4.1.16.3 on page 42.

MSC/VLR

GMSC/SSF
1 2

CCN

SDP

HLR

3 4 5 6 7 8 9 10 11 12 13 14 VPLMN HPLMN

Figure 25

Late Call Forwarding

1. A call is initiated to a subscriber roaming in a VPLMN. 2. An interrogation is made to the HLR. 3. The HLR fetches current subscriber location data from the VLR in the VPLMN. 4. The VLR sends subscriber location data to the HLR. 5. Data is sent from the HLR containing such information as T-CSI and the call is routed to the SSF. 6. The SSF in the HPLMN triggers CCN where data about the call is collected. 7. The data, collected in step 6, is sent to SDP where the service scenario of the account is checked and a preliminary charging analysis and reservation of funds are performed. 8. SDP sends the result of the calculated call time as well as call data to CCN.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

41

Traffic Cases

9. CCN tells the SSF in the HPLMN to setup the call. 10. The HLR is interrogated again, now with T-CSI suppression. 11. The HLR fetches the roaming number from the VLR. 12. The VLR returns the roaming number to the HLR. 13. Data is sent back to the GMSC in the HPLMN. 14. The call is routed to the MSC/VLR in the VPLMN and if the subscriber is not reachable or does not answer the SSF initiates an originating session from the VPLMN. Note: From now on the call created is a originating call, see Section 4.1.1 on page 13.

4.1.16.3

Optimal Routing at Late Call Forwarding A traffic case for optimal routing at late call forwarding is shown in Figure 26. For an overview of the traffic case, see Table 18.

Table 18
Description

Overview of Traffic Cases, Optimal Routing at Late Call Forwarding
Involved Charging System Network Elements CCN and SDP CDR Generation in the Charging System CCN Applies to

Suppression of terminating charging at late call forwarding is only possible when Optimal Routing at Late Call Forwarding (ORLCF) is available. With ORLCF, the Charging System will handle late call forwarding the same way as early call forwarding.

-

42

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

MSC/VLR

GMSC/SSF
1 2

CCN

SDP

HLR

3 4 5 6 7 8 9 10 11 12 13 14 15 VPLMN HPLMN

Figure 26

Optimal Routing at Late Call Forwarding

1. A call is initiated to a subscriber roaming in a VPLMN. 2. An interrogation is made to the HLR. 3. The HLR fetches current subscriber location data from the VLR in the VPLMN. 4. The VLR sends subscriber location data to the HLR. 5. Data is sent from the HLR, containing such information as T-CSI, and the call is routed to the SSF. 6. The SSF in the HPLMN triggers CCN, where data about the call is collected. 7. The data, collected in step 6, is sent to SDP where the service scenario of the account is checked and a preliminary charging analysis and reservation of funds are performed. 8. SDP sends the result of the calculated call time as well as call data to CCN. 9. CCN tells the SSF in the HPLMN to setup the call. 10. The HLR is interrogated again, now with T-CSI suppression. 11. The HLR fetches the roaming number from the VLR. 12. The VLR returns the roaming number to the HLR.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

43

Traffic Cases

13. Data is sent back to the GMSC in the HPLMN. 14. The call is routed to the MSC/VLR in the VPLMN. 15. The MSC/VLR returns MAP_RESUME_CALL_HANDLING and initiates the optimal routing at late call forwarding. Note: From now on the call is processed in the same way as a early call forwarded call, see Section 4.1.16.1 on page 39.

4.1.17

Roaming, USSD Callback
This section describes the traffic case Roaming, USSD Callback. For an overview of the traffic case, see Table 19.

Table 19
Description

Overview of Traffic Cases, Roaming, USSD Callback CS1+
Involved Charging System Network Elements CCN, AF and SDP CDR Generation in the Charging System CCN or MSC/SSF Applies to

Roaming USSD callback calls are calls initiated in a VPLMN by means of using a USSD service code together with the number to be called. The service manages the calls by first connecting the calling subscriber and later the called subscriber, using the number plan of the home network.

-

Figure 27 illustrates roaming USSD callback with CS1+.

44

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

MSC/VLR gsmSSF
1

GMSC/SSF

CCN

AF

SDP

HLR

2 3 4 5 6 7

8
9 10 11 12 13 14 15 16 17 18 19

20 21 22 25 26 27 28 24

23

29 30

VPLMN

HPLMN

Figure 27

Roaming USSD Callback, CS1+

1. A USSD request is sent from a charging system subscriber roaming in a VPLMN. 2. Based on the service code, the MSC in the VPLMN routes the USSD message to the HLR in the HPLMN through the GMSC in the HPLMN. 3. The HLR performs an analysis of the USSD service code and as a result transfers it to SDP. 4. SDP checks if the USSD originates from an allowed roaming area.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

45

Traffic Cases

Note:

When ETSI MAP is used, the roaming area check is not possible, as location information is not received.

SDP can, based on the configuration, perform an optional AF lookup for retrieval of correct SDP ID. The AF lookup is only done if the indicated subscriber is not located under the current SDP. 5. AF returns the subscribers SDP ID. 6. SDP sends an order to the SCF to set up the call. 7. The SCF sends available information to the correct SDP where the service scenario of the account is checked and a preliminary charging analysis takes place. 8. SDP sends the result of the calculated call time together with call data back to SCF. No reservation is made. 9. The SCF tells the SSF in the HPLMN to connect the Charging System subscriber. 10. A roaming interrogation is made to the HLR to retrieve the roaming number. 11. HLR fetches the roaming number from the VLR. 12. The VLR returns the roaming number to the HLR. 13. The roaming number is sent back from the HLR to the GMSC. 14. The speech connection, between the calling Charging System subscriber and the SSF in the HPLMN, is established. 15. The SSF signals to the SCF when the Charging System subscriber answers. 16. The SCF order a reconnection-loop through the SSF. 17. The SSF simulates a normal call from the calling subscriber. This is needed to allow call supervision and charging. This work around is due to charging limitations in the SSF. 18. The SCF performs a new Interrogation to SDP. Optionally, an MNP lookup can be performed here, see Section 3.1 on page 5. 19. SDP rates and sends the result to the SCF and reserves money. If Community Charging is enabled it is performed at this stage, see Section 3.2 on page 5. 20. The SCF tells the SSF to establish a connection to the called subscriber. 21. The call lasts longer than the call time sent to the SSF, so the SSF notifies the SCF.

46

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

22. The SCF requests SDP to make another reservation from the account with an intermediate interrogation. 23. SDP makes a new charging analysis and deducts the amount previously reserved from the account. There is still money left on the subscriber's account, so SDP sends a new call time to the SCF. 24. The SCF sends the new allowed call time to the SSF. Note: Step 21–24 can be repeated.

25. The calling subscriber releases the call. 26. The SSF in the VPLMN notifies the SSF in the HPLMN of the call disconnection. 27. The SSF notifies the SCF of the call disconnection. 28. A final report is sent from the SCF to SDP. 29. SDP rates the total call and sends a final report result back to the SCF. 30. The SCF sends a call release to the SSF. Note: If end-of-call notification is enabled a notification in sent to the subscriber, see Section 3.4.1 on page 8.

4.2

Offline Charging Services
If an event for some reason cannot be charged using online charging, the Charging System has the possibility to charge the subscribers' accounts offline by collecting and post processing CDRs.

4.2.1

CDR Processing
This section describes the traffic case CDR processing. An overview of the traffic case is shown in Table 20.

Table 20
Description

Overview of Traffic Cases, CDR Processing
Involved Charging System Network Elements SDP and AF. CDR Gener ation in the Charging System SDP Applie s to

Charging Data Record (CDR) processing provides the possibility to adjust the Charging System subscriber’s account by collecting and post-processing CDRs. The Multi Mediation Solution receives the original CDRs from the charging- ,core- and service network and reformats them to an SDP specific format.

-

A traffic case, showing the CDR processing, can be seen in Figure 28.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

47

Traffic Cases

Network
1

SDP

HLR

EMM
2 3 4

AF

5 6 7 8

Figure 28

CDR Processing

1. The Multi Mediation Solution receives CDRs from the network. Note: The Multi Mediation Solution module used in this traffic case is the File and Event mediation module.

2. The Multi Mediation Solution filters and reformats the CDRs and interrogates AF to get the SDP IP-address. 3. AF translates MSISDN into SDP IP-address and returns it to the Multi Mediation Solution. 4. The Multi Mediation Solution sends the CDR to SDP, which performs a check of account status, rates the CDR and updates the account. 5. The subscriber is barred in the HLR for the offline service if the account status indicates no money or no services. See Community Charging, Section 3.2 on page 5. 6. USSD notification is enabled, so SDP sends the USSD information to the HLR, for delivery to the subscriber. 7. For further delivery, the HLR passes the USSD information to the MSC/VLR. 8. SDP notifies the Multi Mediation Solution that the CDR has been processed. The notification with the result from the rating is sent in a CDR.

4.3

Voucher Refill and Enquiry
A voucher is considered as cash and the value lies with the hidden information. A refill does not only add money to the account, but can also adjust the account expiry dates. This can be done in a number of different ways. It is possible for a subscriber to get account information presented on the mobile phone. Whit the use of different service codes it is possible to request account information and get it presented either through a text or voice announcement. This section describes the two different kinds of voucher refill and enquiry.

48

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

4.3.1

IVR Voucher Refill and Enquiry
This section describes Voucher Refill and Enquiry using voice notifications.

4.3.1.1

Voucher Refill through IVR This chapter describes the traffic case Voucher Refill through the Interactive Voice Response (IVR). For an overview of the traffic case, see Table 21. In Figure 29 the traffic case of voucher refill through IVR is illustrated.

Table 21
Description

Overview of Traffic Cases, Voucher Refill through IVR
Involved Charging System Network Elements SDP, the VS, AIR and AF. CDR Generation in the Charging System AIR Applies to

The subscriber calls a service number and gets routed to the IVR. Through announcements and voice prompts the IVR helps the caller to interact with the Charging System for refill procedures.

-

MSC/VLR
1

SDP

EMM

VS

AIR

IVR

HLR

AF

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22

Figure 29

Refill through IVR

1. A refill call is initiated by the Charging System subscriber. 2. The call is routed to the IVR. The IVR checks if the calling party number is complete.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

49

Traffic Cases

3. The IVR requests account information from AIR. 4. AIR interrogates AF to get the SDP IP address. 5. AF returns the SDP IP-address. 6. AIR uses the returned SDP IP address to request account and subscriber data information from SDP. 7. SDP checks if any account updates are necessary and sends the result of the account information requests back to AIR. 8. AIR sends the requested information to the IVR, for example preferred language. The IVR plays a standard welcome announcement and a menu announcement. The subscriber selects the menu option Voucher Refill and enters the voucher activation number. 9. The entered activation code and the mobile number of the subscriber is sent to AIR for verification. 10. AIR requests account information from SDP. 11. SDP sends the result of the account information request back to AIR. AIR verifies that the subscriber exists and is not barred from refill. 12. AIR sends the entered voucher activation code to the Voucher Server (VS) for verification. 13. When the VS has verified the voucher activation code and reserved the voucher, it returns a response to AIR. 14. AIR receives a response from the VS indicating if the verification was successful or not. It was successful, so AIR sends a refill request to SDP. 15. The account balance is increased in SDP database for the account. CDR processing is used and has caused an SMS/GPRS barring. Unbarring of SMS and GPRS in the HLR is supported when a certain account threshold has been reached. In this case through a refill. 16. SDP sends the result of the refill back to AIR. 17. The refill was successful, so AIR requests the VS to set the voucher in used state. 18. The VS responds with the result back to AIR. 19. AIR sends a response to the IVR including the account balance and an indication if the refill was successful or not. A CDR including the refill data is generated. 20. The IVR uses the voice prompt to notify the subscriber of the result. 21. The subscriber releases the call.

50

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

22. A CDR is sent to the Multi Mediation Solution as a receipt (optional). Note: The Multi Mediation Solution module used in this traffic case is the File and Event mediation module.

4.3.1.2

Enquiry through IVR The traffic case of enquiry through IVR is illustrated in Figure 30. For an overview of the traffic case, see Table 22.

Table 22
Description

Overview of Traffic Cases, Enquiry through IVR
Involved Charging System Network Elements SDP, AIR, the IVR and AF. CDR Gener ation in the Charging System Applie s to

The subscriber calls a service number and gets routed to the IVR. Through announcements and voice prompts the IVR helps the caller to interact with the Charging System for account balance enquiries, accumulator enquiries, and expiry date enquiries.

-

MSC/VLR
1 2

SDP

AIR

IVR

AF

3 4 5 6 7 8 9 10 11 12 13 14 15

Figure 30

Enquiry through IVR

1. An enquiry call is initiated by the Charging System subscriber. 2. The call is routed to the IVR. The IVR checks if the calling party number is complete. 3. The IVR requests account information from AIR. 4. AIR interrogates AF to get the SDP IP address. 5. AF returns the SDP IP address.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

51

Traffic Cases

6. AIR uses the returned SDP IP address to requests account and subscriber data information from SDP. 7. SDP checks if any account updates are necessary and sends the result of the account information requests back to AIR. 8. AIR sends the requested information to the IVR, for example preferred language. The IVR plays a standard welcome announcement and a menu announcement. The subscriber selects the menu option Balance Enquiry. 9. A balance enquiry request with the mobile number of the subscriber is sent to AIR. 10. AIR enquires SDP for account information. 11. SDP sends the requested account information to AIR. 12. AIR forwards the account information to the IVR. 13. The IVR plays a response message. 14. The subscriber releases the call. 15. The MSC informs the IVR about the completion of the call.

4.3.2

USSD Voucher Refill and Enquiry
This section describes Voucher Refill and Enquiry using notifications through the mobile handset.

4.3.2.1

USSD Voucher Refill This section describes the traffic case of USSD Voucher Refill. The traffic case is illustrated in Figure 31. For an overview if the traffic case, see Table 23.

Table 23
Description

Overview of Traffic Cases, USSD Voucher Refill
Involved Charging System Network Elements SDP, the VS, AIR and AF. CDR Generation in the Charging System AIR Appli es to -

The subscriber enters a USSD service code and a voucher activation code using the mobile handset. AIR interacts with SDP for refill of the subscriber's account. The subscriber receives an USSD text message with a notification if the voucher refill was successful or not.

52

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

MSC/VLR
1

SDP

EMM

VS

AIR

HLR

AF

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

Figure 31

USSD Voucher Refill

1. A Charging System subscriber originates an USSD message with the USSD service code corresponding to voucher refill and the voucher activation code. 2. The MSC forwards the message to the HLR. 3. The HLR analyses the USSD service code and forwards the message to AIR. 4. AIR interrogates AF to get the SDP IP address. 5. AF returns the SDP IP address. 6. AIR uses the returned SDP IP address to requests account and subscriber data information from SDP. 7. SDP checks if any account updates are necessary and sends the result of the account information request back to AIR. AIR verifies that the subscriber exists and is not barred from refill. 8. AIR sends the activation code to the VS for verification. 9. When the VS has verified the activation code and reserved the voucher, it returns a response to AIR. 10. AIR receives a response from the VS indicating if the verification was successful or not. It was successful, so AIR sends a refill request to SDP. 11. The account balance is increased in the SDP database.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

53

Traffic Cases

CDR processing is used and has caused an SMS/GPRS barring. Unbarring of SMS and GPRS in the HLR is supported when a certain account threshold has been reached. In this case through a refill. 12. SDP sends the result of the refill back to AIR. 13. The refill was successful, so AIR requests the VS to set the voucher in used state. 14. The VS responds with the result back to AIR. 15. AIR reformats the response into a USSD text string and sends it to the HLR. The response is successful, so the appropriate successful message is sent, otherwise a failure response with the reason for failure would have been sent. A CDR including the refill data is generated. 16. The HLR forwards the response to the MSC and the response is displayed on the subscriber’s handset. 17. A CDR is sent to the Multi Mediation Solution as a receipt (optional). Note: The Multi Mediation Solution module used in this traffic case is the File and Event mediation module.

4.3.2.2

USSD Balance Enquiry This section describes the traffic case of USSD Balance Enquiry. The traffic case is illustrated in Figure 31. For an overview of the traffic case, see Table 24.

Table 24
Description

Overview of Traffic Cases, USSD Balance Enquiry
Involved Charging System Network Elements SDP, AIR and AF. CDR Generation in the Charging System Applies to -

The subscriber enters a USSD service code using the mobile handset. AIR interacts with SDP for balance enquiries, accumulator enquiries, and expiration date enquiries. The subscriber then receives an USSD text message with the account information.

MSC/VLR
1

SDP

AIR

HLR

AF

2 3 4 5 6 7 8 9

Figure 32

USSD Balance Enquiry

54

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Traffic Cases

1. A Charging System subscriber originates a USSD message with the USSD service code corresponding to enquiry. 2. The MSC forwards the message to the HLR. 3. The HLR analyses the USSD service code and forwards the message to AIR. 4. AIR interrogates AF to get the SDP IP address. 5. AF returns the SDP IP address. 6. AIR uses the returned SDP IP address to request account and subscriber data information from SDP. 7. SDP sends the requested account information to AIR. 8. AIR reformats the response into a USSD text string and send to the HLR. The response is successful, so the appropriate successful message is sent, otherwise a failure response with the reason for failure would have been sent. 9. The HLR forwards the response to the MSC and the response is displayed on the subscriber’s handset.

2/1551-FAV 101 72/4 Uen B | 2011-02-11

55

Traffic Cases

56

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Glossary

Glossary

Active Service Service scenario of a Charging System account AF Account Finder AIR Account Information and Refill A-Number The calling party ATI Any Time Interrogation B-Number The called party CAMEL Customized Application for Mobile Enhanced Logic CAP CAMEL Application Part CCN Charging Control Node CDR Charging Data Record CFB Call Forward on Busy CFU Call Forwarding Unconditional Charging System Subscriber Either a master- or an associated- subscriber to a Charging System account. C-Number Forwarded to number CSI CAMEL Subscription Information

CS1+ Ericsson’s IN protocol supporting all capabilities of Ericsson INAP 2.1 and ETSI Core INAP CS1. DCCA Diameter Credit Control Application DNS Domain Name Service ECUR Event Charging with Unit Reservation EOICK Extended OICK Ericsson MM Ericsson Multi Mediation ETICK Extended TICK ERTC Ericsson Real Time Charging FNR Flexible Numbering Register Full Service Service scenario of a Charging System account GMSC Gateway MSC GPRS General Packet Radio Service GSM Global System for Mobile Communication gsmSCF Executes the IN service in case of service execution initiated by the gsmSSF through CAMEL

2/1551-FAV 101 72/4 Uen B | 2011-02-11

57

Traffic Cases

gsmSRF Service Resource Function gsmSSF Functional entity that interfaces the GMSC to the gsmSCF HLR Home Location Register HPLMN Home Public Land Mobile Network ID Identity IDP Initial Detection Point IEC Immediate Event Charging INAP Intelligent Network Application Protocol In-call Announcements Warning announcement that the money on the Charging System account is running out ISDN Integrated Services Digital Network IVR Interactive Voice Response LNP Local Number Portability M2M Mobile to Mobile MNP Mobile Number Portability MSC Mobile Services Switching Centre MSISDN Mobile Station ISDN number

No Service Service scenario of a Charging System account non-served subscriber Subscriber other than the served subscriber O-CSI Originating CAMEL Subscription Information OICK Originating IN Category Key Passive Service Service scenario of a Charging System account. PCR Pre-Call Replenishment PDP Packet Data Protocol PRS Policy and Rating Server PS Packet Switched PSTN Public Switched Telephone Network Refill Procedure for adding value to a Charging System account. RTCfA Real Time Charging for All SCAP Service Charging Application Protocol SCF Service Control Function SCP Service Control Point SCUR Session Charging with Unit Reservation

58

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Glossary

SDP Service Data Point served subscriber The subscriber to whom the charging service is provided Service Class Pre-customized Charging System services used to differentiate Charging System. Service Scenario Defines the state of a Charging System account. SM Short Message SMS Short Message Service SMS-C SMS Center SMS-IWMSC SMS Interworking MSC SRAP Service Rating Application Protocol SRF Service Resource Function SSF Service Switching Function T-CSI Terminating CAMEL Subscription Information TDP Trigger Detection Point TICK Terminating IN Category Key USSD Unstructured Supplementary Service Data VLR Visiting Location Register

VPLMN Visited Public Land Mobile Network VS Voucher Server Voucher Used to refill a Charging System account

2/1551-FAV 101 72/4 Uen B | 2011-02-11

59

Traffic Cases

60

2/1551-FAV 101 72/4 Uen B | 2011-02-11

Reference List

Reference List

[1] [2]

Customer Product Information Overview, 1551-FAV 101 72/4 Uen System Description, 1/1551-FAV 101 72/4 Uen

2/1551-FAV 101 72/4 Uen B | 2011-02-11

61

Similar Documents

Premium Essay

Air Traffic Controller Case Study

...1.0 Introduction Air Traffic Controller is one of imperative individual that can work at ATC tower proximate to the runway to assure the flight were sheltered when they had take off, saddling and landing. In any case, afore they can took care of this employment they should have a liscened. The area of Abu Dhabi Ecumenical Airplane terminal (AUH/OMAA) was assigned at Emirate of Abu Dhabi which capital of Joined Bedouin Emirate. Size of that Airplane terminal is 16.5 nautical miles (30.6 km,19.0 Mil) of the Abu Dhabi city(second most astronomically immense in the UAE), Its scope was N24* 25.9833, Longitude E54* 39. 0667 the tallness 26.82 from the ocean level . 20 millions peregrinator expected in 2014. Its have 3 terminal there is Terminal 1. Terminal 1 was isolated into 2 terminal(Terminal 1A and Terminal 1B), Terminal 2 and Terminal 3 (Terminal 3 worth UED 1 Billion or US $270 Million). Figured 1.1: Abu Dhabi International Airport Figured 1.2 : interior and exterior of Terminal 1 Figured 1.3 Terminal 2 and 3 Abu Dhabi Macrocosmic Air terminal have a special animal of Airport regulation Tower. ATCC was done at 2010. outfits the...

Words: 1215 - Pages: 5

Premium Essay

Air Traffic Control Case Study

...of stress that air traffic controllers face on the job? Why or why not? No, I don’t think I would be able to handle the stress of being an air traffic controller. After reading the case study, I understood just how much pressure and responsibility that is put on their shoulders. According to the National Air Traffic Controllers Association (NATCA), on an average day, controllers handle 87,000 flights. That’s a couple million people’s lives in my hands on any given day and if I make any kind of small mistake, 400 people could lose their lives just like that. On the last case study I was asked if I would want to manage an IKEA store because I didn’t think I could handle watching over all of the employees, so I definitely wouldn’t be able to or want to handle millions of people’s lives. 2) In your opinion, which causes of work stress, or organizational stressors, are likely to be among the most common experienced by air traffic controllers? Explain your reasoning. I would say that Task Demands are the most common stressors experienced by air traffic controllers. I say this because they have such a highly demanding job which depends upon high levels of responsibility, quick decisions, and critical decisions. On the job, air traffic controllers have to make decisions quickly while realizing that the wrong one may endanger, or even end, the lives of hundreds and thousands of people. 3) Controller Pete Rodgers says that any gathering of air traffic controllers is ‘almost...

Words: 752 - Pages: 4

Free Essay

“the Effects of Road Traffic Congestion on Residential Decision- Making of Inhabitants of the City of Accra- a Case Study of Communities Along Three Congested Routes”

...Topic: “The effects of road traffic congestion on residential decision- making of inhabitants of the city of Accra- A case study of communities along three congested routes” Transportation is essentially a response to the mobility needs of people, and this must be done in a timely fashion in order for people to realize its full benefits. Consequently, transportation plays a crucial role in the socio-economic and politico-cultural development of people and their communities. However, there are some related problems (such as congestion, mobility gaps, urban sprawl, and emissions amongst others) that come with it. In Ghana, transportation is almost synonymous with road transport as it is the major means by which peoples’ mobility needs are answered on daily basis. Road traffic congestion in the city of Accra has almost become an’ acceptable norm’ since residents have to live with this phenomenon every passing day of their lives. The factors responsible for this trend are as follows: growth in the population of Accra over the last 15 years (and this has been estimated to double in the next 20 years) associated with a continuing trend of reduction in population density; expansion in built-up area; growth in per capital income (which has also been estimated to have increased five folds over the last 15 years) with a concomitant increase in car ownership. Currently over 70% of major roads in Accra and Kumasi-the two biggest cities in the country- are said to be congested and should the...

Words: 567 - Pages: 3

Premium Essay

Traffic Crash Case Report

...INVESTIGATION: On 06-30-2016, I was notified at approximately 0021 hours, of a traffic crash fatality on Bearss Avenue east of Livingston Avenue. I responded to the crash scene and arrived at approximately 00103 hours. Upon my arrival at the scene, I met with, Corporal Morrill, Detective Parsons, who forensically mapped the scene and took digital photographs of the crash scene and Deputy Moraniec. Deputy Moraniec completed the Department of Highway Safety and Motor Vehicle Traffic Crash Report (6560901). I conducted an interview of Anthony Walter Chavez, the driver of the Lincoln Navigator. During the interview, Chavez refused to submit to a blood draw. During the time we spoke, I noticed no indication of impairment with Chavez. I also conducted an interview with the passenger from the Lincoln...

Words: 989 - Pages: 4

Premium Essay

Driving Defensively

...now back to reality. Seriously. A lot of drivers barely pay attention to their own habits (wander in other lanes? text? make sudden stops? you know who you are). One of the best skills you could acquire is to drive defensively. Some insurance will even give you a discount for taking a course in it. What does it mean to drive defensively? Think of it like this. When you get behind the wheel of a vehicle. Don't. Trust. Anyone. It's that simple. Don't assume the other driver will obey all traffic laws. Humans make mistakes. People get too comfortable and distracted while driving. They tend to forget they are in control...

Words: 553 - Pages: 3

Premium Essay

The Australian Road Rules

...unlearn much of what he has learned in his own State and to learn a lot that is strange to him. This produces irritation – or worse - in the motor owner and motor driver, and tends to unnecessary costs of traffic administration (which the motorist usually has to pay for). It also adds to traffic dangers through ignorance or unfamiliarity with local conditions or practices on the part of drivers. Therefore, anything that can be done to lay down a national basis for motor traffic control must be of much practical value. Commonsense suggests that there should be uniformity instead of variety, and that the growing volume of interstate traffic requires a national instead of a local viewpoint in things common to traffic in all of the States. Were all motor vehicles kept within their own State boundaries, little disadvantage would arise from the present welter of confusing motor legislation, but when a system becomes national, a system (or lack of system) of arbitrarily fixed laws that differ substantially in matters in which there should be common agreement appears absurd, if not intolerable. I do not consider that it would be very difficult, once the groundwork had been prepared, to induce the various State Governments to agree to a national conference of traffic authorities and representatives of the recognised motoring organisations in the...

Words: 3747 - Pages: 15

Premium Essay

Rumors in a Small Town

...Wimberley for the last couple of weeks. Everybody’s been either happy about it or they’ve been up in arms over it. We finally got confirmation about it this last week. HEB has bought some land right in the middle of Wimberley. I’m in the camp of being up in arms over it. I’m usually a proponent of change, but in this case, I’m not. Wimberley had an Ace Hardware that was right in the middle of town. It caught on fire and burnt down about 6 months ago. They are rebuilding but the building now is a lot bigger than the previous one. That being said, I don’t feel there needs to be another big building right behind it, right in the middle of town. It will completely change the landscape of the town. People come to Wimberley for the tourist experience. Not for the big town experience. They can stay home for that. There are two roads on either side of the land where they want to build. They are two lane roads. The town put in really nice sidewalks a few years ago. Where are they going to expand the roads to accommodate the amount of traffic that will be coming? They have Market Days on the first Saturday of the month. That day is a good indication of the amount of traffic we will get on a daily basis. The camp that is happy about HEB coming thinks that it will be competition for Brookshire Bros. and then BB will have to lower their prices. I’ve even heard some people say that hopefully it will put Brookshire Brothers out of business. These people can’t see the big picture. Let me ask...

Words: 379 - Pages: 2

Premium Essay

Two Lane Road Research Paper

...On April 18, a man was attempting to make a left turn on his ATV when the motorcyclist behind him attempted to pass him, causing crash in Anderson County. The motorcyclist was flown to the University of Tennessee Medical Center where he was treated for non-life threatening injuries. This accident is a reminder that it is important to take the proper precautions when passing another vehicle. When passing another vehicle on a two-lane road, make sure you can safely pass before encountering oncoming traffic. This includes giving yourself time to get back in your correct lane before oncoming traffic arrives. When in doubt, wait to pass the vehicle. Only pass another vehicle when it is legal to do so. This includes not crossing solid yellow lines...

Words: 365 - Pages: 2

Premium Essay

Type of Drivers

...What Type of Driver Are You? Driving is a task we must take part in on a daily basis, but after several years of driving in frustrating and hectic rush hour traffic one can begin to hate even the thought of going to the grocery store. The roads are filled with very different types of drivers; Competent, Overly Cautious, Distracted, and Reckless are just a few of them. How we determine which category we best fall under can be a challenge, because in our minds we think we are good drivers, but in most cases we’re too oblivious to these classifications. First, there are the rare competent drivers who drive safely by not speeding and obey the common driving laws. Competent drivers are always coming to a full stop, looking both ways, using turn signals, and yielding when necessary. This type of driver is the most agreeable of the bunch, putting others at no risk. More of them on the road and the world would be a better place. We tend to think of bad drivers as the ones who charge down the road, wrecking everything in their path, but is it just as bad to be too cautious? Second to the competent, are the overly cautious drivers. They seem to be the ones to cause traffic jams and frustrate other drivers, because they are so indecisive and unpredictable. You know the kind - won't speed up to merge and stops at the end of on-ramps, sits helplessly at a four-way stop because they don't know what to do, slams on the brakes for no apparent reason, and, of course, refusing to exceed the...

Words: 515 - Pages: 3

Free Essay

Mr Khan

...Intro: I am going to be explaining about what happened in the role play? We had a role play, where there was a case about Jackie Jones who was accused of dangerously driving contrary to Section 2 of the Road Traffic Act. The classroom was arranged into a Crown Court. There was one judge, one witness, one clerk, couple of students were members of the jury and some were members of the other juries, there were one usher, there were two lawyers, one lawyer was a defendant lawyer while the other lawyer was the prosecution lawyer, there were press and public watching finally there was a defendant who was the criminal. In this role I was actively a criminal and this is what I fulfilled. When the classroom was organised into a Crown Court, I took my seat and sat at the back of the court room as was instructed by the usher. I kept completely silent for the time being, until it was my turn to go to the witness box and give my statement. The minute the usher stood up and removed me from my seat and took me over to the witness box, this is the exact statement I gave. Statement I gave while I was inside the witness box: “I took delivery of my new Mazda sports car, from the garage Brookside Mazda and I was driving alongside Hillside Road. I live at 32 Able Close and I got stuck in the usual traffic jam. I am very familiar with the road as I drive it every day If I get stuck in traffic when I get close to my turning I have a habit of pulling out to the other side of the road...

Words: 1046 - Pages: 5

Free Essay

Survey in Highway and Traffic Engineering

...THE TECHNICAL UNIVERSITY OF KENYA NAME: MOSES GITOBU KINYUA REG NO.: 111/00104 COURSE: Bachelor of Engineering Geospatial Engineering DEPARTMENT: SURVEYING SCIENCE & TECHNOLOGY UNIT: HIGHWAY & TRANSPORTATION ENGINEERING ASSIGNMENT: How to reduce the number of road accidents in Kenya. LECTURER: Mr. Ogutu Submission date April 14, 2014. Introduction A road accident, also known as a traffic accident, motor vehicle collision, motor vehicle accident, car accident, automobile accident, road traffic collision, car crash, or car smash occurs when a vehicle collides with another vehicle, pedestrian, animal, road debris, or other stationary obstruction, such as a tree or utility pole for instance electricity poles or fence poles. Traffic collisions may result in injury, death, vehicle damage and property damage. They have led to loss of thousands of life and others being paralyzed for the rest of their lives while others are left with permanent scars which remind them of the occurrence. It is regarded as one of the main cause of death after diseases. Here I am going to concentrate on how to reduce road accidents in Kenya through the various engineering disciplines in the country. These disciplines include geospatial engineering, civil and building engineering, mechanical engineering (automotive engineering) and electrical engineering. A. Improvement of road design to reduce accidents on black spots This area has the geospatial and civil engineers who mainly deal...

Words: 1158 - Pages: 5

Premium Essay

Cycling

...Cycling – Creating the New Norm Martina Kahn Western Governors University WGU Student ID # 000390369 Cycling – Creating the New Norm Sitting down, whether in a vehicle, office or home, has become the principal offender in a worldwide obesity and diabetes pandemic that is damaging healthcare systems to the breaking point and increasing health risks to millions of overweight people. Administrations everywhere consider solutions that are economically feasible, easy to implement and improves patient health all at the same time. Together, they may have discovered their answer in a simple piece of engineering able to resolve all of these issues; the bicycle. However, research suggests that American society is not cyclist friendly due to drivers and/or cyclists not always being properly trained. Also, there is a need for bike lanes and laws that require road sharing. For the last five decades, only motorized vehicles have been considered in street designs throughout our country. Driver focused polices, education, and behaviors are an important part of the cycling safety encounter. Revolution in road and cycling infrastructure design is also needed as our population keeps growing. Care needs to be taken and investments made to ensure that everyone has a safe place to travel. In many ways, there has never been a better time to be a bicyclist. If you thought there were more bicyclists on the roads lately, you’d be right. Biking is thriving. The number of cyclists are growing...

Words: 2665 - Pages: 11

Free Essay

Reverse Around a Corner

...Reverse round a corner step by step technique The reverse round a corner or left corner reverse as it is sometimes known is one of 4 manoeuvres you will need to learn before taking the driving test. The reverse round a corner manoeuvre is also one of the more common manoeuvres asked by the test examiner for you to perform. This tutorial will demonstrate an ideal technique that the examiner will be looking for in order to pass this part of the driving test. The test examiner will be looking for 3 key skills demonstrated by yourself in order to successfully complete the reverse round a corner manoeuvre. These skills are: • • • Accuracy - The test examiner will be assessing your ability to reverse round the corner, not touching the curb or straying too far onto the other side of the road. Control - The examiner will be judging your ability to keep the car at a slow and stable speed by use of clutch control. Observation. Effective and all round observation must be taken whilst performing the reverse round a corner manoeuvre. Reverse round a corner diagram A During the driving test, the examiner will ask you to park up on the left on many occasions. They are observing your accuracy and safety for parking. Another occasion may be the examiner is going to request you demonstrate the reverse round a corner. The examiner will ask you to park up on the left, just before the turn you are going to reverse into as in diagram A. When the examiner asks you to park ...

Words: 2333 - Pages: 10

Free Essay

The Collision

...to toward work. The sides of the freeway were flooded and too many cars tend to be going the same direction as mine. It was heavy traffic and other driver’s frustration appeared; when they were swerving their cars left and right trying to make their way out of traffic. I had my radio on and the news was about a car accident on San Mateo Bridge, which already started my day off wrong from that moment. As I was counting down the miles toward my destination, driving my car on the carpool lane going 65 miles per hour which was the legal speed limit for the freeway. Cruising on the far left lane, driving a 2005 black Jeep Cherokee that had four large tires which made me higher and oversee the whole view of the freeway. The incident started when I took a quick glance over my right shoulder and saw a blue, shiny-rimmed Toyota Runner, suv spinning out of control. The car instantly took my attention; the car was at the very far right lane so at the moment I did not doubt that the driver was going to make his way towards me immediately. Because it was raining hard and the road was wet which made him to slide all the way to the far left lane. At first he hit the concrete freeway dividers suddenly, I instantly slammed my breaks until I saw smoke coming out from the tires and then blew up. He spun 180 degrees and stopped facing the incoming traffic. I look at my right side and many cars were coming and my left side was the divider of the freeway. I was trying to avoid crashing...

Words: 895 - Pages: 4

Free Essay

My Information

...Actions of all roadway users including pedestrians, animals, bicyclists, and other drivers impact your level of risk as a driver. To help manage risk, it is essential that you remain alert to conditions or objects that can increase levels of risk. Here is a checklist to help you manage risk: Conduct a thorough visual search. Search 30 seconds ahead of your path of travel for objects or conditions that could become a threat. Have a plan. Identify an alternate path of travel 15 seconds ahead, and the level of traction available in case of an emergency. Never tailgate. Always travel with an adequate cushion of space ahead of your vehicle. Position your vehicle with space to the sides and the front with an escape route, should you need it. Obey all traffic controls. Exercise the right-of-way rules. Drive defensively. Try to predict the possible actions of other highway users. Do not drive where you cannot see. If your vision is blocked, reduce your speed and reposition your vehicle so you can see well ahead, and around your vehicle; do not forget to look behind. See and be seen. Communicate your presence to other road users by always driving with your daytime running lights or low-beam headlights. Remember, if you cannot see them, they probably cannot see you. Look where you want your vehicle to go. Avoid distractions. Avoid sudden steering and braking movements. Be a considerate driver. Keep your vehicle in...

Words: 256 - Pages: 2