Huawei Csoftx3000

HUAWEI CSOFTX3000 CDR Description Contents Issue 03 (2007-11-30) Huawei Technologies Proprietary i
Contents
1 Overview of Billing System....................................................................... ..............................1-1
1.1 Basic Concepts .................................................................................................................... ..........................1-2 1.2 Introduction to Billing Subsystem.................................................................................................................1-3 1.3 Billing Process ..............................................................................................................................................1-5
2 CDR Producing.................................................................... .......................................................2-1

2.1 General Process of CDR Producing ........................................................................................ ......................2-2 2.2 Call Data Collection..................................................................................................... .................................2-2 2.3 Producing of CDR.........................................................................................................................................2-3 2.3.1 Producing of Ordinary Service CDR ..................................................................................... ..............2-3 2.3.2 Producing Intelligent Service CDR......................................................................................................2-4 2.4 CDR Storage ............................................................................................................. ....................................2-5 2.4.1 CDR Storage Paths...................................................................................................... .........................2-5 2.4.2 Storage of Original CDRs ....................................................................................................................2-6 2.4.3 Storage of Final CDRs ................................................................................................. ........................2-9 2.5 CDR Processing on iGWB..........................................................................................................................2-12 2.6 CDR Sending ............................................................................................................. .................................2-13 2.7 CDR Checking ............................................................................................................ ................................2-14
3 CDR Types and Formats...................................................................... .....................................3-1

3.1 CDR Types ....................................................................................................................................................3-2 3.1.1 CDR Classification by Storage ............................................................................................................3-2 3.1.2 CDR Classification by Call Process.....................................................................................................3-2 3.1.3 CDR Classification By Scenario..........................................................................................................3-3 3.2 Final CDR Format.........................................................................................................................................3-7
4 Examples of CDR Producing ............................................................................. ......................4-1

4.1 Examples of Producing Basic Call CDRs .....................................................................................................4-2 4.1.1 Examples of Producing Ordinary Call CDRs .............................................................................. ........4-2 4.1.2 Examples of Producing IN Call CDRs in Overlay Network................................................................4-5 4.1.3 Examples of Producing IN Call CDRs in Target Network.................................................................4-10 4.1.4 Examples of Producing SM Call CDRs.............................................................................................4 -12 4.2 Examples of Producing Supplementary Service CDRs...............................................................................4-13 4.2.1 Examples of Producing Call Forwarding CDRs ............................................................................ ....4-13 Contents HUAWEI CSOFTX3000 CDR Description ii Huawei Technologies Proprietary Issue 03 (2007-11-30) 4.2.2 Examples of Producing Call Waiting CDRs ......................................................................................4-22 4.2.3 Examples of Producing Call Transfer CDRs............................................................................... .......4-23 4.2.4 Examples of Producing Multiparty Service CDRs.............................................................................4-25
4.3 CDR Fill-Out Rules.....................................................................................................................................4-26 4.3.1 Intra-MSC Call..................................................................................................................... ..............4-26 4.3.2 Gateway Outgoing Call......................................................................................................................4-28 4.3.3 Gateway Incoming Call ................................................................................................. ....................4-30 4.3.4 Transit Call.........................................................................................................................................4-32 4.3.5 Intelligent Call ...................................................................................................................................4-34 4.3.6 Short Message Call .................................................................................................... ........................4-35
5 CDR Control and Sorting ............................................................................. ............................5-1

5.1 Control on the Producing of CDRs ........................................................................................ .......................5-2 5.2 Number Conversion for CDRs......................................................................................................................5 -4 5.3 CDR Sorting at Billing Center ......................................................................................................................5-4 5.3.1 Sorting of IN CDRs .................................................................................................... .........................5-4 5.3.2 Sorting of Ordinary CDRs ...................................................................................................................5-5 HUAWEI CSOFTX3000 CDR Description Figures Issue 03 (2007-11-30) Huawei Technologies Proprietary iii
Figures
Figure 1-1 Structure of the billing subsystem.....................................................................................................1 -3 Figure 1-2 Billing process of the system ............................................................................................................1-5 Figure 2-1 Billing system for intelligent services...............................................................................................2-4 Figure 2-2 Paths of original CDR files...............................................................................................................2-6 Figure 2-3 Directory for storing original CDRs .................................................................................................2-6 Figure 2-4 Original CDR files in a folder...........................................................................................................2-7 Figure 2-5 Original CDRs in the original CDR file ...........................................................................................2-8 Figure 2-6 Paths of final CDR files..................................................................................................... ...............2-9 Figure 2-7 Directory for final CDRs on the iGWB Client ...............................................................................2-10 Figure 2-8 Final CDR files.............................................................................................................. .................2-11 Figure 2-9 Final CDR in the final CDR file .....................................................................................................2-12 Figure 2-10 CDR processing flow.......................................................................................................... ..........2-13 Figure 3-1 Details of the final CDR ........................................................................................................ ...........3-7 Figure 4-1 Calls between MS-A and MS-B in the same VMSC ........................................................................4-2 Figure 4-2 Calls between MS-A and MS-B in different VMSCs .......................................................................4-3 Figure 4-3 Calls from MS-A to PSTN subscriber B...........................................................................................4-3 Figure 4-4 Call from PSTN subscriber A to MS-B.............................................................................................4-4 Figure 4-5 Ordinary calls between mobile subscribers served by different carriers...........................................4-5 Figure 4-6 Call between PPC mobile subscribers ..............................................................................................4-6 Figure 4-7 Call from PPC MS-A to PSTN subscriber B ....................................................................................4-7 Figure 4-8 Call from PSTN subscriber A to MS-B.............................................................................................4-7 Figure 4-9 Call from an ordinary PLMN subscriber to a PPC mobile subscriber ..............................................4-8 Figure 4-10 Call from a PPC mobile subscriber to an ordinary mobile subscriber ............................................4-9 Figure 4-11 Call from MS-A to Subscriber-E.....................................................................................................4-9 Figure 4-12 Call in the same VMSC/SSP.........................................................................................................4-10 Figure 4-13 Call from MS-A to a subscriber in another PLMN.......................................................................4-11 Figures HUAWEI CSOFTX3000 CDR Description iv Huawei Technologies Proprietary Issue 03 (2007-11-30) Figure 4-14 Incoming call from MS-A to MS-B..............................................................................................4-11 Figure 4-15 CDR produced for sending SMs ................................................................................................ ...4-12 Figure 4-16 CDR produced for receiving SM................................................................................................ ..4-13 Figure 4-17 Calling and called subscribers in the different VMSCs................................................................4-14
Figure 4-18 Call from PSTN subscriber C to MS-B ........................................................................................4-15 Figure 4-19 Calling and called MSs in the same VMSC..................................................................................4-16 Figure 4-20 Calling and called subscribers in the different VMSCs................................................................4-17 Figure 4-21 Call from PSTN subscriber C to MS-B ........................................................................................4-17 Figure 4-22 Calling and called MSs in the same VMSC..................................................................................4-18 Figure 4-23 Call forwarding between different VMSC to PPC subscriber ......................................................4-19 Figure 4-24 Forwarding of fixed-to-mobile calls .............................................................................................4-20 Figure 4-25 Forwarding of mobile-to-fixed calls .............................................................................................4-21 Figure 4-26 Call forwarding with all mobile subscribers in the same VMSC..................................................4-22 Figure 4-27 Call waiting................................................................................................................. ..................4-23 Figure 4-28 Call Transfer .................................................................................................................................4-24 Figure 4-29 3WC service .................................................................................................................................4-26 HUAWEI CSOFTX3000 CDR Description Tables Issue 03 (2007-11-30) Huawei Technologies Proprietary v
Tables
Table 2-1 CDR-related paths on the iGWB server .............................................................................................2-5 Table 4-1 Billing start and end time of the CDRs.............................................................................................4-24 Table 4-2 Key fields and values of the MOC CDR for MS-A..........................................................................4-27 Table 4-3 Key fields and values of the MTC CDR for MS-B ..........................................................................4-27 Table 4-4 Key fields and values of the MOC CDR for MS-A..........................................................................4-27 Table 4-5 Key fields and values of the CFW CDR for MS-B...........................................................................4-28 Table 4-6 Key fields and values of the MTC CDR for MS-C ..........................................................................4-28 Table 4-7 Key fields and values of the MOC CDR for MS-A..........................................................................4-28 Table 4-8 Key fields and values of the gateway outgoing CDR for MS-A.......................................................4-29 Table 4-9 Key fields and values of the CDR for MS-A....................................................................................4-29 Table 4-10 Key fields and values of the CFW CDR of MS-B..........................................................................4-30 Table 4-11 Key fields and values of the gateway outgoing CDR for MS-B.....................................................4-30 Table 4-12 Key fields and values of the MTC CDR of MS-B..........................................................................4-30 Table 4-13 Key fields and values of the roaming CDR ....................................................................................4-31 Table 4-14 Key fields and values of the MTC CDR of MS-C..........................................................................4-31 Table 4-15 Key fields and values of the roaming CDR ....................................................................................4-32 Table 4-16 Key fields and values of the roaming CDR ....................................................................................4-32 Table 4-17 Key fields and values of the gateway outgoing CDR.....................................................................4-32 Table 4-18 Key fields and values of the transit CDR .......................................................................................4-33 Table 4-19 Key fields and values of the roaming CDR ....................................................................................4-33 Table 4-20 Key fields and values of the CFW CDR.........................................................................................4 -34 Table 4-21 Key fields and values of the gateway outgoing CDR.....................................................................4-34 Table 4-22 Key fields and values of the intelligent MOC CDR .......................................................................4-35 Table 4-23 Key fields and values of the............................................................................................................4-35 Table 4-24 Key fields and values of the of the MO-SMS CDR........................................................................4-35 Table 4-25 Key fields and values of the MT-SMS CDR...................................................................................4-36 Tables HUAWEI CSOFTX3000 CDR Description vi Huawei Technologies Proprietary Issue 03 (2007-11-30) Table 5-1 Example of setting parameter for gateway outgoing CDRs ...............................................................5-2 Table 5-2 Example of setting parameter for roam CDRs....................................................................................5-3 HUAWEI CSOFTX3000 CDR Description 1 Overview of Billing System Issue 03 (2007-11-30) Huawei Technologies Proprietary 1-1
Overview of Billing System
About This Chapter

The following table lists the contents of this chapter. Section Describes 1.1 Basic Concepts Basic concepts of the billing system. 1.2 Introduction to Billing Subsystem The structure and components of the billing subsystem. 1.3 Billing Process The process of producing the billing information.
1 Overview of Billing System HUAWEI CSOFTX3000 CDR Description 1-2 Huawei Technologies Proprietary Issue 03 (2007-11-30)
1.1 Basic Concepts

CDR
In the CSOFTX3000, the CDR (Call Detail Record) refers specifically to billing data units that are produced from the WCCU/WCSU boards of the CSOFTX3000 and stored in a specific data format in the iGWB hard disk.
Original CDR
Original CDR refers to the original billing information that is generated by the CSOFTX3000. The original CDR does not concern the operators.
Final CDR
Final CDR refers to the CDR that is sorted on the iGWB. The format of a final CDR is converted on the iGWB to facilitate final charging at the billing center.
The final CDR is not equal to the telephone bill that is sent to the end user. Instead, the final CDR is the basis for producing the telephone bill at the billing center.
Bill Pool
The bill pool is a storage space of fixed capacity provided by the WCSU/WCCU of the CSOFTX3000. It is used to store the original CDRs generated on the call control module. The CDRs then are sent to the iGWB through the shared resource bus. .
iGWB
The iGWB is a billing gateway device between the CSOFTX3000 and the billing center. The iGWB receives CDRs from the CSOFTX3000 and converts the billing data format. The iGWB also provides a buffer for the billing information and related billing interface functions.
HUAWEI CSOFTX3000 CDR Description 1 Overview of Billing System Issue 03 (2007-11-30) Huawei Technologies Proprietary 1-3
1.2 Introduction to Billing Subsystem

The billing subsystem of the CSOFTX3000 comprises the WCCU/WCSU boards, the iGWB, the billing center, and other devices that connect them together. Figure 1-1 shows the structure of the billing subsystem. Figure 1-1 Structure of the billing subsystem
WCS U WHS C WHS C WCCU WCS U WCCU iGWB server LAN switch Multiple service processing module Local bus CSOFTX3000 Billing center LAN switch Heartbeat path Link0 Link1 Link2 Link3 Active Standby Active Standby Active Standby Active LAN switch Standby Active iGWB server Standby FTP/ FTAM iGWB Server: iGateway Bill Server WCCU: Wireless Call Control Unit WHSC: Wireless Hot-Swap and Control Unit WCSU: Wireless Calling Control Unit and Signaling Process Unit
1 Overview of Billing System HUAWEI CSOFTX3000 CDR Description 1-4 Huawei Technologies Proprietary Issue 03 (2007-11-30)
WCCU/WCSU Call Control Units

The WCCU/WCSU call control units generate original CDRs and store the CDRs on the local bill pool. At regular intervals, the active WCCU/WCSU unit duplicates the original CDRs that are not sent to the iGWB and stores it on the standby WCCU/WCSU. It helps to prevent data loss when the active WCCU/WCSU fails.
WCCU/WCSU Bill Pool

The CDR pool is a buffer that stores and forwards the billing information to the iGWB. The storage capacities for each bill pool are different for all CSOFTX3000 versions. You can use the command DSP BLL to display the capacity and check the number of CDRs that can be stored in the pool. The Bill pool size in the message indicates the number of CDRs that can be stored in the bill pool. If failure occurs to the link between the CSOFTX3000 and the iGWB and if the CDRs cannot be sent to the iGWB successfully, the CDRs consume the storage capacity of the bill pool on the CSOFTX3000. A bill pool congestion alarm is produced when the available capacity of the bill pool drops to 70% of the total capacity. Calls are restricted if the capacity drops from 70% to 30% of the total capacity. You can set these two threshold values in the software parameters.
iGWB
The iGWB is a billing gateway device between the CSOFTX3000 and the billing center. The iGWB collects, stores, sorts, and converts the original CDRs received from the CSOFTX3000.
The iGWB also provides FTP or FTAM interface for the billing center to send billing information to the billing center. The iGWB ensures that the billing center collects the CDRs correctly. The iGWB converts the original CDRs to final CDRs. The iGWB enables the query and printout of final CDRs at the iGWB Client and also enables the query of the billing server status.
Billing Center
The billing center collects the billing information produced by the CSOFTX3000 and produces the final CDRs to the customers. The billing center is not a device of the CSOFTX3000.
HUAWEI CSOFTX3000 CDR Description 1 Overview of Billing System Issue 03 (2007-11-30) Huawei Technologies Proprietary 1-5
1.3 Billing Process

In each call process, the CSOFTX3000 collects information about the call to generate the original CDRs for final charging and settlement by network operators or service providers. Figure 1-2 shows the billing process. Figure 1-2 Billing process of the system
To billing center for final charging Final CDR Sorting and saving CDR Receiving original CDR Original CDR Final CDR Generating original CDR Sending CDR and CRC check CDR buffer CSOFTX3000 iGWB
From the figure you can see that the entire billing process comprises three major steps: Step 1 Produce the original CDR. 1. The CSOFTX3000 produces information about the original call. The information is stored in the bill pool of the CSOFTX3000. 2. The information is transferred to the iGWB in real-time through the Ethernet bus, WHSC, and the LAN Switch. 3. Before the CDR is sent to the iGWB, CRC check is conducted to guarantee the correctness of the CDR. 4. The CDR is transferred from the CSOFTX3000 to the iGWB based on sliding windows transmission protocol. Step 2 Produce the final CDR. 1. Upon receiving the original CDRs, the iGWB sorts the CDRs according to different billing conditions and stores the CDRs to different physical paths. 2. The iGWB converts the data format of the CDR so that the CDRs comply with the data format used at the billing center and facilitate CDR query. The converted formats include the source format, target format, source format for browsing and target format for browsing, and browsing before and after the saving. Step 3 Collect the final CDR. After the iGWB produces the final CDR, the billing center collects the final CDR to produce the bills for the end users. The final CDR can be collected through the following modes:
1 Overview of Billing System
HUAWEI CSOFTX3000 CDR Description 1-6 Huawei Technologies Proprietary Issue 03 (2007-11-30)
1. The iGWB sends the final CDR to the billing center without being requested. This is called the PUSH mode. 2. The billing center collects the final CDR from the iGWB. This is called the PULL mode. In normal cases, the billing center collects the final CDRs regularly from the iGWB hard disk. ----End
HUAWEI CSOFTX3000 CDR Description 2 CDR Producing Issue 03 (2007-11-30) Huawei Technologies Proprietary 2-1
CDR Producing
About This Chapter

The following table lists the contents of this chapter. Section Describes 2.1 General Process of CDR Producing The process of producing a CDR. 2.2 Call Data Collection How the information about a call is collected. 2.3 Producing of CDR How an ordinary call CDR and an intelligent call CDR is produced. 2.4 CDR Storage The directory for storing original CDRs and final CDRs. 2.5 CDR Processing on iGWB How an original CDR is sorted and converted on the iGWB. 2.6 CDR Sending Basic principles for sending CDRs from the CSOFTX3000 to the iGWB 2.7 CDR Checking CRC check on CDRs before the CDRs are stored to the bill pool.
2 CDR Producing HUAWEI CSOFTX3000 CDR Description 2-2 Huawei Technologies Proprietary Issue 03 (2007-11-30)
2.1 General Process of CDR Producing

In each call process, the CSOFTX3000 collects information about the call to generate the original CDRs for final charging and settlement by network operators or service providers. The process to produce CDRs is as follows: 1. The CSOFTX3000 collects the call data to generate the original CDRs and stores them in the bill pool. 2. The CSOFTX3000 sends the original CDRs in real time to the charging gateway (iGWB) through the local area network (LAN). 3. The iGWB produces the final CDRs and sends them to the billing center. 4. The public land mobile network (PLMN) operator produces detailed service bills for the end users based on the final CDRs. The entire process of producing a CDR comprises the collecting of information, producing the CDR, storing the CDR and transferring the CDR.
2.2 Call Data Collection

When a mobile subscriber originates or answers a call, the CSOFTX3000 records all the information about the call.
Data Collection for Mobile Originated Calls

When the call request is sent to the CSOFTX3000, the CSOFTX3000 records all the information related to the calling party, such as the calling number, international mobile station identity (IMSI), and location (home MSC, BSC, and cell). The CSOFTX3000 also records all the information related to the called party after analyzing the called number. If it is an outgoing call, the CSOFTX3000 records the data related to the trunk.
Data Collection for Mobile Terminated Calls

If the MS answers a call, the visited MSC (VMSC) records all the data related to the called party. If both the calling and called parties are served by the same VMSC, the VMSC records all the data related to the calling and the called party for producing a mobile originated call (MOC) CDR and a mobile terminated call (MTC) CDR. If the call request comes from another MSC through the trunk, then the VMSC through which the called party is served records the data about the call for producing an MTC CDR.
2.3 Producing of CDR

When a call completes, or the duration of the call reaches the threshold for a long-duration call, or the call type changes, the CSOFTX3000 records the following data: Call start date and time Duration CDR type (such as MOC or MTC) Call termination reason (such as normal release or conversation timeout) The CSOFTX3000 also collects data related to the CDRs, such as serial number of the CDRs, serial number of the initial CDR, record types (such as First Bill, Last Bill, or Intermediate Bill). The data is used for CDR management. After collecting all the CDR data, the CDRs are produced based on the collected data and are stored in the bill pool. The CDRs for intelligent users and common users are produced differently.
2.3.1 Producing of Ordinary Service CDR

The overall process of producing CDRs for an ordinary service user is as follows: 1. In the call process, the call processing module collects the billing information, such as user number, call start time, call duration, and call attributes. 2. When the call is terminated, the module records the call end time and generates the original CDRs for this call. 3. The module then sends the original CDRs to the iGWB. 4. The iGWB processes the CDRs and produces the final CDR. 5. The billing center collects the final CDR from the iGWB and sorts the CDR according to the charging policy of specific operators. The billing center then generates the telephone bill for the end user.
2.3.2 Producing Intelligent Service CDR

In intelligent service networks, the final bills may be generated through different billing systems. Figure 2-1 shows the complete structure of a billing system for intelligent services. Figure 2-1 Billing system for intelligent services
Billing Center Settlement Center SSP SCP SMP Settlement result and remote CDR Billing info CDR management Call start Call end CDR SMP: service management point SCP: service control point SSP: service switching point
When processing an intelligent call, the SSP (Service Switching Point) accomplishes the connection and play of prompt tones according to instructions given by the SCP (Service Control Point). The SCP determines whether to conduct billing on a specific call according to the relevant business policies. The overall process of producing CDRs for an intelligent service user is as follows: 1. The SSP reports the O_ANSWER/T_ANSWER event when a call is triggered. The SCP then starts the billing process. 2. The SSP reports the O_DISCONNECT/T_DISCONNECT event when the call is terminated. 3. According to the information contained in the events reported by the SSP, the SCP monitors the recording of the billing information and generates the original CDR. 4. At the same time, the SSP generates a CDR that carries an intelligent service tag for the SCP to double-check the billing information. In certain scenarios, the following processes are involved. 1. The SCP transfers the CDR to the SMP (Service Management Point). 2. The SMP then forwards the CDR to the settlement center. 3. The settlement center allocates the sum, sorts the CDRs, and then sends the CDRs with the allocated sums to different billing centers. In the entire process of an intelligent call, the SCP may conduct real-time charging and deduct the sum from the user account directly, or may conduct the charging after the call is terminated.
Control Mechanism Involved with Intelligent Service Billing

Billing for intelligent services includes local intelligent calls and toll intelligent calls. The billing policy is subject to the service administration entity and the service subscriber. The SCP is the entity that implements the billing, while the SSP is the entity that reports the billing information. The settlement center is responsible for allocating the sum to different billing parties. The two intelligent call triggers installed on the SSP are as follows: O_ANSWER/T_ANSWER trigger: When an intelligent call starts, the SSP reports to the SCP an event that contains the start time, billing ID, and billing user ID. O_DISCONNECT/T_DISCONNECT trigger: When an intelligent call terminates, the SSP reports to the SCP an event that contains the termination time, billing ID, and billing
user ID of the call. The SSP reports various call events to the SCP according to the setting of the triggers. The SCP then conducts billing according to the reported events and forwards the CDRs to the SMP, if an allocation is required. The SMP forwards the allocated sum to the settlement center for final charging.
General Principle of Producing Intelligent CDRs

In an intelligent call, the SSP need not produce the CDRs because the SSP provides information only about the call for the SCP. The CSOFTX3000, acting as an SSP, produces an ordinary service CDR for an intelligent call to allow a cross-check mechanism for the operators. It also adds an intelligent service tag to the CDR for the billing center.
2.4 CDR Storage

The WCCU/WCSU in the CSOFTX3000 stores the CDRs in the first-in-first-out (FIFO) mode. The CSOFTX3000 stores the CDRs in the bill pool and sends them to the iGWB in real time. The space of a CDR in the bill pool is not released until the CDR reaches the iGWB.
2.4.1 CDR Storage Paths

Table 2-1 lists the default CDR storage paths on the iGWB server. Table 2-1 CDR-related paths on the iGWB server Path Description D:\frontsave Storing original CDRs D:\other\mml Storing user information files used by the MML server D:\other\log Storing log files D:\other\alarm Storing history alarms E:\backsave Storing final CDRs
2.4.2 Storage of Original CDRs

A subfolder, for example, X3KC, is named after the specific product and is stored in both D:\frontsave and E:\backsave. The paths of original CDR files are fixed, as shown in Figure 2-2. Figure 2-2 Paths of original CDR files
... X3KC Date D:\frontsave Original CDR file Original CDR file Original CDR file Original CDR file Date ... ...
The original CDR files are stored in the folders by date. For example, all original CDR files produced on October 8, 2006 are stored in the subfolder named 20061008, as shown in Figure 2-3. Figure 2-3 Directory for storing original CDRs An original CDR file is named in the form "b" + 10-digit-SN + ".bil", such as b0000000491.bil.
HUAWEI CSOFTX3000 CDR Description 2 CDR Producing
Issue 03 (2007-11-30) Huawei Technologies Proprietary 2-7
Figure 2-4 shows the original CDR files in the folder 20061008. Figure 2-4 Original CDR files in a folder An original CDR file contains multiple original CDRs and the size of each file is limited. When the size of a file reaches the upper limit, or the file has been created for a certain period, the file is closed and a new file is created. You can define the size of the file.
Figure 2-5 shows the original CDRs in the file b0000000491.bil. This file contains three original CDRs: PDSN_BILL, MOC, and PDSN_BILL. Figure 2-5 Original CDRs in the original CDR file
2.4.3 Storage of Final CDRs

Figure 2-6 shows the paths of the final CDR files. You can define the paths. Figure 2-6 Paths of final CDR files
X3KC Path 1 E:\backsave E:\backsave X3KC Second Path N Path 1 Final CDR file Final CDR file Final CDR file Final CDR file Path N Date Final CDR file Final CDR file Final CDR file Final CDR file Date Date Final CDR file Final CDR file Final CDR file Final CDR file Date
In Figure 2-6: CDR files under E:\backsave\X3KC are for querying and browsing. CDR files under E:\backsave\Second are sent to the billing center.
The billing center determines whether to delete a CDR file after the final CDRs are collected. It is recommended to remove them from the iGWB.
Figure 2-7 shows the displayed query result on the iGWB Client. Under the directory 20061008 the final CDR files of the day 20061008 are stored. Figure 2-7 Directory for final CDRs on the iGWB Client The following are some concepts about the CDR storage: Path In a path, the CDR files that comply with certain conditions are stored. For example, if you sort the CDR files according to the CDR types, each CDR type will correspond to a path. In Figure 2-7, the subdirectories Normal, LIC, and Attempt under the directory Final Bill are paths corresponding to the CDR types. Refer to the user manual of the iGWB for more descriptions about the GUI. File name for final CDRs The file name for final CDRs comprises of the following: "Prefix" + "File serial number" + "." + "Suffix". For example, b00000001.dat is a file name of final CDRs. Prefix The prefix is optional and can be a string of any character. Usually, the prefix uses the name of the office, such as "Shenzhen" and "Guangzhou". By default, the prefix is "b". File serial number The serial number of the file is compulsory. By default, the serial number starts from 1. The largest serial number is an octet 99999999. Suffix The suffix depends on the configuration and the default is "dat". Creating the final CDR file Whether a new file is created to store the final CDRs depends on the size of the current file and how long the file has been created. You can define these two limits. If the size of a file reaches the size limit, or if the existence of the file reaches the time limit, a new file is created. A file for final CDRs contains one or multiple final CDRs.
Figure 2-8 shows the final CDR files under the directory 20061008. Figure 2-8 Final CDR files
Figure 2-9 shows the final CDR in the file b00002487.dat, and you can see that only one CDR "PDSN_BILL" exists in the file. Figure 2-9 Final CDR in the final CDR file
2.5 CDR Processing on iGWB

The information collected on the CSOFTX3000 is stored in the CDR pool and sent to the iGWB for processing. The iGWB receives the original CDR from the CSOFTX3000 over its self-defined protocol. The iGWB relies on a dual-machine hardware backup to guarantee correct billing information without losing or repeating a CDR. Sorted CDRs are stored in different directories to be collected by the billing center. After processing the original CDR, the iGWB produces the final CDR. The processing flow is shown in Figure 2-10.
Figure 2-10 CDR processing flow
Sorting Format Conversion Original CDR Final CDR
CDR Sorting
CDR sorting classifies CDRs of different billing conditions into different groups to process and save them to different physical paths. You can define the criteria according to the data fields in the CDR. Here, the data fields can act as the criteria for the sorting.
CDR Format Conversion

The format of a specific CDR is related to the version of the equipment. In the appendix of version release notes, the CDR format and samples are provided for your reference.
You can ask Huawei support engineers to provide correct documents about related equipment versions.
2.6 CDR Sending

To increase the reliability of the bill pool and to send the CDRs to the iGWB, the CSOFTX3000 uses the sliding window transfer protocol. This protocol ensures a timely, accurate, and continuous transfer. In this case, no CDR is lost or sent repeatedly. The process to send a CDR is as follows: 1. The iGWB and bill pool negotiates the start serial number for the CDRs to be sent through handshake messages. 2. After receiving the CDRs, the iGWB returns a response to the bill pool, indicating that it has received the negotiated CDRs. 3. If a correct reply is not received after sending a batch of CDRs, the bill pool does not send the next batch, but resends the first CDR of the same batch. 4. If the correct reply is received, the bill pool sends the CDRs of the next batch.
2.7 CDR Checking

To ensure that the CDRs are correct, the CSOFTX3000 carries out a cyclic redundancy check (CRC) when producing, sending, and receiving the CDRs. Before storing the CDRs in the bill pool, the CSOFTX3000 carries out a CRC check and stores the checksum in the bill pool. After receiving the CDRs, the iGWB performs a CRC. When the check fails, the gateway assumes that the bills have changed during transfer. When converting the original CDRs to the final CDRs, the gateway stores the final CDRs to another directory. Here, the final CDRs result from the original CDRs that fail in the CRC. The maintenance staff then handles the final CDRs.
HUAWEI CSOFTX3000 CDR Description 3 CDR Types and Formats Issue 03 (2007-11-30) Huawei Technologies Proprietary 3-1
CDR Types and Formats
About This Chapter

The following table lists the contents of this chapter. Section Describes 3.1 CDR Types The various types of CDR produced by the CSOFTX3000. 3.2 Final CDR Format The formats of original and final CDRs.
3 CDR Types and Formats HUAWEI CSOFTX3000 CDR Description 3-2 Huawei Technologies Proprietary Issue 03 (2007-11-30)
3.1 CDR Types

This section introduces the following three types of CDRs: CDRs according to storage: original CDRs and final CDRs. CDRs according to producing process: intermediate CDR and terminative CDR CDRs produced according to service type or call modes.
3.1.1 CDR Classification by Storage

Original CDR
Original CDR is the billing data unit generated and stored on the CSOFTX3000 WCCU/WCSU. The CSOFTX3000 generates and sends the original CDRs to the iGWB in real-time through an Ethernet connection.
Final CDR
Upon receiving the original CDR from the CSOFTX3000 WCCU/WCSU, the iGWB stores the CDRs on the hard disk, sorts the CDRs, and then converts the CDR data format. The sorted and converted CDRs are stored on the hard disk according to certain rules and are called the final CDR. The services providers charge the end users based on the final CDRs.
3.1.2 CDR Classification by Call Process

CDRs of the CSOFTX3000 are classified into two types according to the producing process.
Intermediate CDR
If the duration of a call exceeds the threshold of the long-duration call timer of the CSOFTX3000, a CDR is produced in each cycle of the timer. This CDR is called the intermediate CDR.
Terminative CDR
Terminative CDR is the original CDR, which is generated when a call is terminated and the resource is released by the system. A terminative CDR is produced if the duration of a call is shorter than the timer. This CDR records the information of the entire call process. In case the duration of a call is longer than the timer, an intermediate CDR and a terminative CDR are produced. The terminative CDR, however, records only the information collected within the time of the last long-duration call timer. Each intermediate CDR of the CSOFTX3000 records only the information collected in the time of the long-duration call timer that corresponds to the CDR. At the billing center, all the intermediate CDRs and the terminative CDR are added up to calculate the actual sum, which is charged for the call.
3.1.3 CDR Classification By Scenario
MOC CDR and MTC CDR

When an MS originates a call and the called party answers, an MOC CDR is produced during the call or when the call is terminated. When an MS terminates a call, an MTC CDR is produced during the call or when the call terminates.
Roam CDR
The roam CDR is generated at the GMSC for a call from a public switched telephone network (PSTN) or another mobile network to the serving network. The roam CDR is a charging reference for the PSTN or another mobile network. The roam CDR is also a reference for settling trunk occupation expenses between the serving network and the PSTN, or between two mobile networks. You can decide whether to generate the roam CDR through data configuration.
For details, see 5.1 Control on the Producing of CDRs.
Transit CDR
The transit CDR is produced on the CSOFTX3000 when: A call is routed to the CSOFTX3000, but the call is neither originated from nor terminated at the CSOFTX3000, and Both the outgoing and the incoming directions of the call are the CSOFTX3000. Transit CDRs are not produced for calls forwarded by the local CSOFTX3000. You can decide whether to generate the transit CDR by configuring data.
Gateway_Outgoing CDR
A gateway outgoing CDR is generated when: A call reaches another mobile network from a gateway office. A call reaches the PSTN from a gateway office. The gateway outgoing CDR is a reference for billing in the following cases: Settlement of trunk occupation between the serving PLMN and the PSTN Settlement of trunk occupation between two mobile networks You can decide whether to generate the gateway outgoing CDR by configuring data.
CFW CDR
A call forwarding (CFW) CDR is produced when the call forwarding service is triggered. The call forwarding service enables a call to be forwarded to another specified number. A CFW CDR covers three parties: A calling party
An original called party (the subscriber who forwards the call) A final called party (the subscriber who finally answers the call)
The CFW CDR charges only the original called party. In the CFW CDR: The calling party is the subscriber who forwards the call. The called party is the subscriber who finally answers the call. The third-party is the calling party. The IMSI and mobile directory number (MDN) contain the attributes of the original called party. The CFW CDR also displays the call forwarding type which includes the following: Call forwardingunconditional (CFU) Call forwardingbusy (CFB) Call forwardingno answer (CFNA) Call forwardingdefault (CFD)
MO_SMS CDR and MT_SMS CDR
An MO_SMS CDR is produced for the subscriber who sends the message, and an MT_SMS CDR is produced for the subscriber who receives the message. An SMS CDR does not distinguish IN subscribers from ordinary subscribers. In the SMS mode, the handset transmits characters through the signaling channel or voice channel. Different from the ordinary CDR, the MO_SMS CDR and MT_SMS CDR contain the following fields: Number of bytes This field indicates the number of bytes in the UserPart within the short message, that is, the length of the content after it is decoded. Address of the message center This field indicates the message center through which the short message travels. In the CDMA network, this field is meaningless and the CDR is produced by the local office.
Billing of short message service is conducted at the Message Center. The CDR produced from the CSOFTX3000 is for reference only.
SS Operation CDR
An SS operation CDR is produced when the HLR returns the Feature operation successfully.
EC CDR
An emergency call (EC) CDR is produced when a local MS starts an emergency call.
PDSN CDR
PDSN enables Internet access from an MS for sending and receiving E-mails, sending and receiving fax, and surfing the Internet. A PDSN CDR is produced when a local MS activates the packet data service.
ISDN_MO CDR and ISDN_MT CDR

When a PRA subscriber calls a local MS, the local MSC generates an ISDN_MO CDR. When a local MS calls a PRA subscriber, the local MSC generates an ISDN_MT CDR.
OTASP CDR
OTASP (Over-The-Air Service Provisioning) is activated by an MS. By dialing the OTASP access number, an MS is able to open the account, activate the user, and set the terminal parameters. A registered subscriber can also dial the OTASP access number to modify the terminal parameters. The OTASP CDR is produced when a local MS starts an OTASP call.
OTAPA CDR
OTAPA (Over-The-Air Parameter Administration) is activated by the network operator and does not involve the MS. An operator can issue the OTAPA command to modify the terminal parameters, especially to modify the roaming list of a terminal. The OTAPA CDR is produced when an OTAPA operation is conducted successfully by the OTAF.
CT800 CDR
The CT800 service is a CDMA corporation service (TRUNKING) that aims at corporation calls, point-to-point calls, and broadcast calls. The CT800 CDR is produced for the CT800 services.
IWFQNC CDR
IWF (InterWorking Function) is a data service based on circuit domain for the interconnection between the PLMN and the other networks, such as PSTN, ISDN, and X.25. QNC (Quick Network Connection) is among one of the IWF services supported by MSCs that enables Internet access through circuit domain. The IWFQNC CDR is produced for the IWFQNC service.
MAH CDR
MAH (Mobile Access Hunting) service allows registration of a PILOT number that is associated with multiple user numbers (member numbers). When someone dials the PILOT number, the member terminal rings sequentially until one of the subscribers answers the call. The MAH CDR is produced for the MAH service.
ONLY CDR
One Number Link You (ONLY), also known as Flexible Alerting (FA) , allows registration of a PILOT number that is associated with multiple user numbers. When someone dials the PILOT number, all the member terminals ring at the same time. The ONLY subscriber can answer the call from any of the terminals. After the call is answered, the rest of the terminals stop ringing.
The ONLY CDR is produced for the ONLY service.
Enhanced Call Attempt CDR

The enhanced call attempt CDR is produced for an Interworking function (IWF) call or a voice call that fails. It provides information to locate the problem, such as CDR types, calling number, called number, third-party number, MSCID, or failure cause. The CDR includes the following CDR types: MOC_ATTEMPT/MTC_ATTEMPT CFW_ATTEMPT GWO_ATTEMPT ROAM_ATTEMPT TRANSIT_ATTEMPT SS_ATTEMPT
Brazil SMP Attempt CDR

It serves to help the Brazil telecom monitor center to monitor the network. The CDR is used in Brazil and is produced when a call fails. The CDR contains information, such as the setup time, alerting time, and allocation complete time. The CDR includes the following CDR types: MOC_ATTEMPT/MTC_ATTEMPT CFW_ATTEMPT GWO_ATTEMPT ROAM_ATTEMPT TRANSIT_ATTEMPT ISDN_MO_ATTEMPT/ISDN_MT_ATTEMPT
MSNH CDR
The CSOFTX3000 generates the MSNH CDR for the MSNH service. In the MSNH service, one UIM card is allocated with n MDNs. Each MDN can correspond to a city or an area. In the service, all the MDNs are on line and each MDN can be the called number. That is, you can connect with the called party by dialing any of the MDNs.
AIPC CDR
The advanced intelligent peripheral (AIP) is implemented. When a PPC subscriber triggers the WIN service and the announcement played for AIP connection, the MSCe generates an AIPC CDR, in which, the number of the subscriber who triggers the announcement playing flow and the dialed number are recorded for charging and settlement between networks.
3.2 Final CDR Format

The format of a final CDR can be binary, text, and ASN.1. Final CDRs are stored in the final CDR files. Final CDRs are produced based on the data fields of the original CDR, the charging policy of the billing center, and the format requirement of the final CDR for querying. See Appendix for CDR formats that are supported by the billing subsystem of the CSOFTX3000. Consider the files displayed in Figure 2-5 as an example. The details of the MOC CDR are displayed in Figure 3-1. Figure 3-1 Details of the final CDR
HUAWEI CSOFTX3000 CDR Description 4 Examples of CDR Producing Issue 03 (2007-11-30) Huawei Technologies Proprietary 4-1
Examples of CDR Producing
About This Chapter

The following table lists the contents of this chapter. Section Describes 4.1 Examples of Producing Basic Call CDRs Examples of producing CDRs for basic calls. 4.2 Examples of Producing Supplementary Service CDRs Examples of producing CDRs for supplementary service calls. 4.3 CDR Fill-Out Rules The MDNs to be filled in to the CDRs.
4 Examples of CDR Producing HUAWEI CSOFTX3000 CDR Description 4-2 Huawei Technologies Proprietary Issue 03 (2007-11-30)
4.1 Examples of Producing Basic Call CDRs

Basic calls refer to ordinary calls that are compared with supplementary service calls. Basic calls include the following three types: Ordinary subscriber calls IN subscriber calls Short message calls Intelligent network (IN) subscriber calls apply to the following types of network: Overlay network Target network
4.1.1 Examples of Producing Ordinary Call CDRs

The following examples illustrate the producing of ordinary CDRs in different scenarios: MS-A and MS-B in the Same VMSC MS-A and MS-B in Different VMSC Call from MS-A to PSTN Subscriber Call from PSTN Subscriber to MS-B
Calls
between Mobile Subscribers Served by Different PLMN Carriers
MS-A and MS-B in the Same VMSC

Both MS-A and MS-B are in the same VMSC. Figure 4-1 shows the producing of CDRs when MS-A calls MS-B. Figure 4-1 Calls between MS-A and MS-B in the same VMSC MS-A VMSC MS-B MOC MTC Originating call to B The VMSC generates the following two CDRs: An MOC CDR for charging MS-A An MTC CDR for charging MS-B.
MS-A and MS-B in Different VMSCs

MS-A and MS-B are in two different VMSCs that belong to the same PLMN. Figure 4-2 shows the producing of CDRs when MS-A calls MS-B. Figure 4-2 Calls between MS-A and MS-B in different VMSCs MS-A Originating call to B VMSCA VMSCB MOC MTC MS-B VMSCA generates an MOC CDR to charge MS-A. VMSCB generates an MTC CDR to charge MS-B.
Call from MS-A to PSTN Subscriber

Suppose that Subscriber B is a PSTN subscriber. If MS-A calls Subscriber B, the GMSC helps to connect the call between the two networks. 1. The VMSC searches a route for MS-A and connects the call to the TMSC. 2. The TMSC forwards the call to the GMSC. 3. The GMSC connects the call to the specific PSTN switch. Figure 4-3 shows the producing of the CDRs. Figure 4-3 Calls from MS-A to PSTN subscriber B
B
MOC PSTN GMSC TMSC VMSCA MS-A GATEWAY_ TRANSIT OUTGOING Originating call to B
The following describes the produced CDRs: The VMSC generates an MOC CDR to charge MS-A. The TMSC generates a transit CDR, which acts as a reference for trunk occupation settlement in the serving PLMN. The GMSC generates a gateway outgoing CDR, which acts as a reference for the outgoing trunk occupation settlement between the serving PLMN and the PSTN. If the call is routed directly from the VMSC to the GMSC and is routed to the PSTN without passing through the TMSC, no transit CDR is produced.
The producing of transit CDRs and gateway outgoing CDRs is determined by data configuration. That is, the transit CDRs (or gateway outgoing CDRs) can be produced in the other MSCs rather than the TMSC
(or GMSC). A VMSC, serving as a GMSC connected to the switch of other networks, can generate gateway CDRs through data configuration. For details, see 5.1 Control on the Producing of CDRs.
Call from PSTN Subscriber to MS-B

Suppose that Subscriber A is a PSTN subscriber who calls MS-B. The GMSC helps to connect the call between the two networks. 1. When subscriber A calls MS-B, the PSTN switch delivers the call to the GMSC. 2. The GMSC obtains the TLDN of MS-B and connects the call to the TMSC. 3. The TMSC connects the call to the VMSC. Figure 4-4 shows the producing of the CDRs. Figure 4-4 Call from PSTN subscriber A to MS-B
MTC PSTN GMSC TMSC VMSC ROAM TRANSIT Terminating call to B A MS-B
The following describes the produced CDRs: The GMSC generates a ROAM CDR as a reference for incoming trunk occupation settlement between the serving PLMN and other networks. The TMSC generates a transit CDR as a reference for trunk occupation settlement in the serving PLMN. The VMSC produces an MTC CDR to charge MS-B. When a call is routed directly from the GMSC to the VMSC without passing through the TMSC, no transit CDR is produced.
The producing of the roam CDR, transit CDR, and gateway outgoing CDR is determined by data configuration. For details, see 5.1 Control on the Producing of CDRs.
Calls between Mobile Subscribers Served by Different PLMN Carriers

MS-B is served by Carrier-W and MS-A is served by Carrier-Y. The switch of Carrier-Y produces CDRs for MS-A and the switch of Carrier-W produces CDRs for MS-B. Each carrier produces its own CDRs for inter-network settlement. 1. When MS-A calls MS-B, the VMSCA forwards the call to GMSCA. 2. GMSCA connects the call to GMSCB of Carrier-W. 3. GMSCB obtains the TLDN of MS-B and connects the call to VMSCB. Figure 4-5 shows the producing of the CDRs. Figure 4-5 Ordinary calls between mobile subscribers served by different carriers
Originating call to B ROAM MTC MS-A VMSCA TMSCA GMSCA GMSCB VMSCB MS-B GATEWAY_ OUTGOING MOC TRANSIT
The following describes the produced CDRs: VMSCA produces an MOC CDR to charge MS-A of Carrier-Y. VMSCB produces an MTC CDR to charge MS-B of Carrier-W. TMSCA produces a transit CDR. GMSCA produces a gateway outgoing CDR as a reference for outgoing trunk occupation settlement between the serving PLMN and other networks. GMSCB produces a roam CDR as a reference for incoming trunk occupation settlement between the serving PLMN and other networks.
4.1.2 Examples of Producing IN Call CDRs in Overlay Network
The following examples illustrate the producing of CDRs for different IN service scenarios in an overlay network:
Call Between PPC Subscribers

Suppose that the PPC (prepaid call) subscribers MS-A and MS-B are in the same VMSC, where MS-A calls MS-B. 1. The VMSC connects the call to the GMSC/SSP through the TMSC when it identifies that MS-A is a PPC subscriber.
2. The GMSC/SSP negotiates with the SCP of MS-A for charging. 3. The GMSC/SSP negotiates with the SCP of MS-B for charging when it identifies that MS-B is also a PPC subscriber. 4. The GMSC/SSP connects the call to the VMSC through the TMSC. Figure 4-6 shows the producing of the CDRs. Figure 4-6 Call between PPC mobile subscribers
MOC/MTC GMSC/SSP TMSC VMSC MS-A/B Originating call to B Terminating call to B TRANSIT TRANSIT
The following describes the produced CDRs: The VMSC produces an MOC CDR to charge MS-A. The VMSC produces an MTC CDR to charge MS-B. The TMSC produces two transit CDRs because the call passes the TMSC twice. The GMSC/SSP produces another transit CDR.
Calls from PPC Subscriber to PSTN Subscriber

Suppose that MS-A is a PPC mobile subscriber and Subscriber B is a PSTN subscriber. MS-A calls Subscriber B. 1. The VMSC connects the call to the TMSC. 2. The TMSC overlays the call to the GMSC/SSP. 3. The GMSC/SSP connects the call to the PSTN.
Figure 4-7 shows the producing of the CDRs. Figure 4-7 Call from PPC MS-A to PSTN subscriber B
B MOC PSTN GMSC/SSP TMSC VMSCA MS-A GATEWAY_ TRANSIT OUTGOING
The following describes the produced CDRs: The VMSC produces an MOC CDR. The GMSC/SSP produces a gateway outgoing CDR as a reference for settlement of outgoing trunk occupation between the serving PLMN and the PSTN. The TMSC produces a transit CDR.
Calls from PSTN Subscribers to PPC Subscriber

Suppose that MS-B is a PPC subscriber and Subscriber A is a PSTN subscriber. Subscriber A calls MS-B. The PSTN switch connects the call to the GMSC/SSP. The GMSC/SSP forwards the call to the TMSC.
The
TMSC connects the call to the VMSC. Figure 4-8 shows the producing of the CDRs. Figure 4-8 Call from PSTN subscriber A to MS-B
A MTC PSTN GMSC/SSP TMSC VMSC MS-B ROAM TRANSIT
The following describes the produced CDRs: The GMSC produces a ROAM CDR as a reference for settlement of incoming trunk occupation between the serving PLMN and the PSTN. The VMSC produces an MTC CDR to charge MS-B. The TMSC produces a transit CDR.
Calls from Ordinary Mobile Subscriber to Local PPC Subscriber

Suppose that MS- A is an ordinary mobile subscriber and MS-B is a PPC mobile subscriber. MS-A calls MS-B. VMSCA connects the call to TMSCA. TMSCA connects the call to the GMSC/SSP. The GMSC/SSP searches a route and connects the call to TMSCB. TMSCB connects the call to VMSCB. Figure 4-9 shows the producing of the CDRs. Figure 4-9 Call from an ordinary PLMN subscriber to a PPC mobile subscriber
Originating call to B TRANSIT MTC MS-A VMSCA TMSCA GMSC/SSP TMSCB VMSCB IN MS-B MOC TRANSIT TRANSIT
The following describes the produced CDRs: VMSCA produces an MOC CDR to charge MS-A. VMSCB produces an MTC CDR to charge MS-B. TMSCA and TMSCB produce two TRANSIT CDRs each because the call passes TMSCA and TMSCB twice. The GMSC/SSP produces a TRANSIT CDR.
Calls from PPC Subscribers to Local Ordinary Mobile Subscribers

Suppose that MS-A is a PPC subscriber and MS-B is an ordinary mobile subscriber, MS-A calls MS-B. 1. VMSCA connects the call to TMSCA. 2. TMSCA overlays the call to the GMSC/SSP. 3. The GMSC/SSP searches a route and connects the call to TMSCB. 4. TMSCB connects the call to VMSCB.
Figure 4-10 shows the producing of the CDRs. Figure 4-10 Call from a PPC mobile subscriber to an ordinary mobile subscriber
Originating call to B TRANSIT MTC IN MS-A VMSCA TMSCA GMSC/SSP TMSCB VMSCB MS-B MOC TRANSIT TRANSIT
The following describes the produced CDRs: VMSCA produces an MOC CDR to charge MS-A.
VMSCB TMSCA
produces an MTC CDR to charge MS-B. and TMSCB produce two TRANSIT CDRs each because the call passes TMSCA and TMSCB twice. The GMSC/SSP produces a transit CDR.
Calls from PPC Subscriber to Subscriber of another PLMN

Suppose that MS-A is a PPC mobile subscriber and MS-B is a mobile subscriber of another PLMN. MS-A calls MS-B. 1. VMSCA connects the call to TMSCA. 2. TMSCA overlays the call to the GMSCA/SSP. 3. GMSCA/SSP connects the call to GMSCB. 4. GMSCB connects the call to VMSCB. Figure 4-11 shows the producing of the CDRs. Figure 4-11 Call from MS-A to Subscriber-E
Originating call to B ROAM MTC IN MS-A VMSCA TMSCA GMSCA/SSP GMSCB VMSCB Ordinary MS-B GATEWAY_ OUTGOING MOC TRANSIT
The following describes the produced CDRs: VMSCA produces an MOC CDR to charge MS-A. VMSCB produces an MTC CDR to charge MS-B. TMSCA produces a transit CDR. GMSCA/SSP produces a gateway outgoing CDR. GMSCB produces a roaming CDR.
4.1.3 Examples of Producing IN Call CDRs in Target Network

The following examples illustrate the producing of CDRs for different IN service scenarios in a target network:
Calls in the Local MSC

Suppose that MS-A and MS-B are two IN subscribers in the same VMSC/SSP. MS-A calls MS-B. Figure 4-12 shows the producing of the CDRs. Figure 4-12 Call in the same VMSC/SSP
IN MS-A VMSC/SSP IN MS-B MOC MTC Originating call to B
The VMSC/SSP produces the following two CDRs: An MOC CDR for charging MS-A. An MTC CDR for charging MS-B.
Gateway Outgoing Calls

Suppose that MS-A is an IN subscriber, and MS-A calls MS-B in another PLMN. Figure 4-13 shows the producing of the CDRs. Figure 4-13 Call from MS-A to a subscriber in another PLMN
MOC GMSC/SSP TMSC VMSC/SSP IN MS-A TRANSIT
Originating call to B MS-B GATEWAY_ OUTGOING
The following describes the produced CDRs: __________The VMSC/SSP produces an MOC CDR to charge MS-A. The GMSC/SSP produces a gateway outgoing CDR as a reference for settlement of the outgoing trunk occupation between the serving PLMN and other PLMN. The TMSC produces a transit CDR.
Gateway Incoming Calls

Suppose MS-A is an overlay IN subscriber in another PLMN and MS-B is a target IN subscriber in local PLMN. MS-A calls MS-B. Figure 4-14 shows the producing of the CDRs. Figure 4-14 Incoming call from MS-A to MS-B
Originating call to B ROAM MTC IN MS-A VMSCA TMSC GMSCA/SSP GMSCB/SSP VMSCB/SSP IN MS-B MOC TRANSIT GATEWAY_ OUTGOING
The following describes the produced CDRs: VMSCA produces an MOC CDR to charge MS-A. VMSCB/SSP produces an MTC CDR to charge MS-B. The TMSC produces a TRANSIT CDR. GMSCB/SSP produces a ROAM CDR. GMSCA/SSP produces a GATEWAY_OUTGOING CDR.
4.1.4 Examples of Producing SM Call CDRs

Sending SM
Suppose that MS-A sends short message to MS-B. Figure 4-15 shows the producing of the CDRs. Figure 4-15 CDR produced for sending SMs
Originating SMS to B MC MC/GMSC MSCA MSA MO_SMS Forward Short Message Forward Short Message
MSCA produces an MO_SMS CDR to charge MS-A.

Receiving SM
Suppose that MS-A sends short message to MS-B. Figure 4-16 shows the producing of the CDRs. Figure 4-16 CDR produced for receiving SM
MC MC/GMSC MSCB MSB SMS transfer MT_SMS Forward Short Message
MSCB produces an MT_SMS CDR to charge MS-B.
4.2 Examples of Producing Supplementary Service CDRs

This section illustrates the producing of CDRs for different supplementary services.
4.2.1 Examples of Producing Call Forwarding CDRs

Call forwarding enables an incoming call to be forwarded to a specified number. The MS originating call forwarding is charged. For example, if MS-A calls MS-B, and MS-B forwards the call to MS-C, then MS-B is charged.
For intelligent service subscribers, the forwarded-to number may be registered either at the HLR or at the SCP.
The following describes different types of call forwarding: Call forwardingunconditional (CFU) Call forwardingbusy (CFB) Call forwardingno answer (CFNA) Call forwardingdefault (CFD)
Call ForwardingUnconditional
The GMSC or the originating MSC can initiate the CFU service. During a CFU, the HLR returns the forwarded-to number when the CSOFTX3000 requests for the route data of the called party. The producing of CDR is not related to the exact location of the called party. The following describes some CFU scenarios where CDRs are produced. Calls between mobile subscribers in different VMSCs. In this scenario, the intelligent network is an overlay network. MS-A and MS-C are in the same VMSC while MS-B is in another VMSC. The forwarded-to party MS-C is a PPC subscriber. When MS-A calls MS-B, MS-B unconditionally forwards the call to MS-C. 1. MS-A calls MS-B and the VMSC requests for the TLDN MS-B from the HLR where MS-B is registered. 2. The HLR returns the forwarded-to number, the MDN of MS-C. 3. The VMSC connects the call to the GMSC/SSP through the TMSC when it identifies that MS-C is a PPC subscriber. 4. The GMSC/SSP searches a route and connects the call to the VMSC through the TMSC.
The SCP can return the forwarded-to number of MS-C. This is common in the following call forwarding scenarios.
Figure 4-17 shows the producing of the CDRs. Figure 4-17 Calling and called subscribers in the different VMSCs
MOC MTC CFW GMSC/SSP TMSC VMSC MS-A/C TRANSIT Originating call to B Terminating call to C
The following describes the produced CDRs: The VMSC produces an MOC CDR to charge MS-A. The VMSC produces a CFW CDR to charge MS-B. The VMSC produces an MTC CDR to charge MS-C. The TMSC produces two transit CDRs. The GMSC/SSP produces another transit CDR.
HUAWEI CSOFTX3000
CDR Description 4 Examples of CDR Producing Issue 03 (2007-11-30) Huawei Technologies Proprietary 4-15
In the CFW CDR: Caller_party_number is the MDN of MS-B. Called_party_number is the MDN of MS-C. Third_party_number is the MDN of MS-A. MDN is the MDN of MS-B. Roam number is null (the VMSC cannot obtain the TLDN because the MS-C is a PPC subscriber). Service Feature Indication is CFU.
Calls
from PSTN subscriber to mobile subscriber. In this scenario, MS-A and MS-B are in the same VMSC while Subscriber C is a PSTN subscriber. When Subscriber C calls MS-A, MS-A unconditionally forwards the call to MS-B. 1. The PSTN switch connects the call to the GMSC/SSP. 2. The GMSC/SSP requests the TLDN of MS-A from the HLR where MS-A is registered. 3. The HLR returns the forwarded-to number, the MDN of MS-B. 4. The GMSC/SSP requests the TLDN of MS-B from the HLR where MS-B is registered. 5. The GMSC/SSP connects the call to the VMSC through the TMSC. Figure 4-18 shows the producing of the CDRs. Figure 4-18 Call from PSTN subscriber C to MS-B
MTC GMSC/SSP TMSC VMSC MS-A/B TRANSIT PSTN ROAM CFW
The following describes the produced CDRs: The GMSC/SSP produces a roaming CDR. The GMSC/SSP produces a CFW CDR to charge MS-A. The VMSC produces an MTC CDR to charge MS-B. The TMSC produces a transit CDR. Calls originated by PPC subscriber and forwarded between mobile subscribers in the same VMSC. In this scenario, MS-C is a PPC subscriber in an overlay network. MS-A, MS-B and MS-C are in the same VMSC. When MS-C calls MS-A, MS-A unconditionally forwards the call to MS-B. 1. The VMSC connects the call to the GMSC/SSP through the TMSC. 2. The GMSC/SSP requests the TLDN MS-A from the HLR where MS-A is registered. 3. The HLR returns the forwarded-to number, the MDN of MS-B. 4. The GMSC/SSP requests the TLDN of MS-B from the HLR where MS-B is registered.
5. The GMSC/SSP connects the call to the VMSC through the TMSC. Figure 4-19 shows the producing of the CDRs. Figure 4-19 Calling and called MSs in the same VMSC MOC MTC GMSC/SSP TMSC VMSC MS-A/B/C TRANSIT PSTN CFW The following describes the produced CDRs: The VMSC produces an MOC CDR to charge MS-C.
The The The
GMSC/SSP produces a CFW CDR to charge MS-A. VMSC produces an MTC CDR to charge MS-B. TMSC produces two transit CDRs. The GMSC/SSP produces another transit CDR.
If MS-B registers CFU, a CFW CDR is produced in the CSOFTX3000 that obtains the TLDN of MS-B. The producing of CFW CDR is impertinent to the location of MS-B. In the first scenario, the VMSC obtains the TLDN and generates the CFW CDR. In the second scenario, the GMSC obtains the TLDN and generates the CFW CDR. In the third scenario, the GMSC/SSP obtains the TLDN and generates the CFW CDR.
Call ForwardingBusy and Call Forwarding No Answer

Call forwardingbusy (CFB) and call forwardingno answer (CFNA) are conditional forwarding. The CDRs produced in these two types of forwarding are similar, except the value of Service Feature Indication 1. In these two types of forwarding, a call is first routed to the called party. If the HLR detects that the called party complies with the forwarding criteria, the call is forwarded. The following describes some CFB and CFNA scenarios where CDRs are produced. Calls between mobile subscribers in different VMSCs. In this scenario, the intelligent network is an overlay network. MS-A and MS-C are in the same VMSC while MS-B is in another VMSC. The forwarded-to party MS-C is a PPC subscriber. When MS-A calls MS-B, MS-B is busy and the call is forwarded to MS-C. 1. VMSCA requests the TLDN of MS-B from the HLR where MS-B is registered. 2. The HLR identifies that MS-B is busy and then obtains the forwarded-to number, the MDN of MS-C. 3. VMSCA connects the call to GMSCA/SSP through TMSCA when it identifies that MS-C is a PPC subscriber.
4. GMSCA/SSP obtains the TLDN of MS-C and connects the call to VMSCA through TMSCB. Figure 4-20 shows the producing of the CDRs. Figure 4-20 Calling and called subscribers in the different VMSCs
TRANSIT MS-B VMSCB TMSCB GMSC/SSP TMSCA VMSCA MS-A/C TRANSIT MOC MTC CFW
The following describes the produced CDRs: VMSCA produces an MOC CDR to charge MS-A. VMSCA produces a CFW CDR to charge MS-B and the Service Feature Indication is CFB. VMSCA produces an MTC CDR to charge MS-C. TMSCA produces a transit CDR. Calls from PSTN subscriber to mobile subscriber. In this scenario, MS-A and MS-B are in the same VMSC while Subscriber C is a PSTN subscriber. When Subscriber C calls MS-A, MS-A is busy and the call is forwarded to MS-B. 1. The PSTN switch connects the call to the GMSC/SSP. 2. The GMSC requests the TLDN of MS-A from the HLR where MS-A is registered. 3. The HLR identifies that MS-A is busy and obtains a forwarded-to number, the MDN of MS-B. 4. The GMSC/SSP connects the call to the VMSC through the TMSC. Figure 4-21 shows the producing of the CDRs. Figure 4-21 Call from PSTN subscriber C to MS-B
MTC
GMSC/SSP TMSC VMSC MS-A/B TRANSIT PSTN ROAM CFW 4 Examples of CDR Producing HUAWEI CSOFTX3000 CDR Description 4-18 Huawei Technologies Proprietary Issue 03 (2007-11-30)
The following describes the produced CDRs: The GMSC/SSP produces a roam CDR to charge MS-A. The Service Feature Indication is CFB. The GMSC/SSP produces a CFW CDR to charge MS-B. The VMSC produces an MTC CDR. The TMSC produces a transit CDR. Calls originated by PPC subscriber and forwarded between mobile subscribers in the same VMSC. In this scenario, MS-C is a PPC subscriber in an overlay network. MS-A, MS-B and MS-C are in the same VMSC. When MS-C calls MS-A, MS-A does not answer and the call is forwarded to MS-B. 1. The VMSC connects the call to the GMSC/SSP. 2. The GMSC/SSP requests the TLDN of MS-A from the HLR where MS-A is registered and then connects the call to the VMSC. 3. MS-A does not answer the call. The GMSC/SSP obtains the forwarded-to number, the MDN of MS-B, from the HLR. 4. The GMSC/SSP connects the call to the VMSC through the TMSC. The call is connected to MS-B. Figure 4-22 shows the producing of the CDRs. Figure 4-22 Calling and called MSs in the same VMSC
MOC MTC GMSC/SSP TMSC VMSC MS-A/B/C TRANSIT PSTN CFW
The following describes the produced CDRs: The VMSC produces an MOC CDR to charge MS-C. The GMSC/SSP produces a CFW CDR to charge MS-A. The Service Feature Indication is CFNA. The VMSC produces an MTC CDR to charge MS-B. The TMSC produces a transit CDR.
In these three scenarios, the MSs share the same position but the forwarding conditions are different. Therefore, the CFW CDRs are produced in different MSCs. For the CFB and the CFNA, CDRs are produced in the CSOFTX3000 that initiates the call forwarding, that is, the originating MSC or the GMSC.
Call ForwardingDefault
The Call ForwardingDefault (CFD) integrates all types of call forwarding, which were described previously. The call forwarding is activated according to the actual cases. The condition of CFD is the same as that of CFU, CFB, or CFNA. The only difference is that the value of Service Feature Indication is CFD.
Multiple Forwarding
The approaches to produce CDRs for various types of multiple forwarding (CFU, CFB, CFNA) are the same. The following takes the CFU as an example. Call forwarding to PPC subscriber with calling and called parties in different VMSCs In this scenario, MS-A, MS-C, MS-D and MS-E are in the same VMSC. MS-B is in another VMSC of the same PLMN. When MS-A calls MS-B, the call is unconditionally forwarded from MS-B to MS-C, then from MS-C to MS-D, and then from MS-D to MS-E. MS-E is a PPC subscriber, and the intelligent network is an overlay network. The call connection process is as follows: 1. The VMSC of MS-A requests the TLDN of MS-B from the HLR where MS-B is registered. 2. The HLR returns the forwarded-to number, the MDN of MS-C. 3. The VMSC requests the TLDN MS-C from the HLR where MS-C is registered. 4. The HLR returns the forwarded-to number, the MDN of MS-D. 5. The VMSC requests the TLDN MS-D from the HLR where MS-D is registered. 6. The HLR returns the forwarded-to number, the MDN of MS-E. 7. The VMSC identifies that MS-E is a PPC subscriber, and connects the call to GMSC/SSP through TMSC. 8. The GMSC/SSP routes and connects the call to the VMSC through the TMSC. 9. MS-E is connected. Figure 4-23 shows the process to produce the CDR. Figure 4-23 Call forwarding between different VMSC to PPC subscriber
GMSC/SSP TMSC VMSC MS-A/C/D/E TRANSIT MOC MTC CFW
The
VMSC produces an MOC to charge MS-A. In the CDR, the calling party is A, called party is B, and the third party number is the number of MS-E.
The
VMSC produces three call forwarding CDRs (CFW) The CDR for MS-B: calling party is B, called party is C, and third party is A. The CDR for MS-C: calling party is C, called party is D, and third party is A. The CDR for MS-D: calling party is D, called party is E, and third party is A. The VMSC produces an MTC CDR to charge MS-E. The TMSC produces a transit CDR. The GMSC/SSP produces a transit CDR in which the calling party is A and the called party is E.
In the CFW CDR, the TLDN is null because in a CFU, the VSMC is unable to obtain the correct TLDN. The Service Feature Indication is CFU.
Call
forwarding of fixed-to-mobile calls In this scenario, MS-A, MS-B, and MS-D are in the same VMSC. Subscriber C is a PSTN subscriber. When C calls MS-A, the call is unconditionally forwarded from MS-A to MS-B and then from MS-B to MS-D. The call connection process is as follows: 1. The PSTN switch connects the call to the GMSC/SSP. 2. The GMSC/SSP requests the TLDN MS-A from the HLR where MS-A is registered. 3. The HLR returns the forwarded-to number, the MDN of MS-B. 4. The GMSC/SSP requests the TLDN of MS-B from the HLR where MS-B is registered. 5. The HLR returns the forwarded-to number, the MDN of MS-D. 6. The GMSC/SSP requests the TLDN MS-D from the HLR where MS-D is registered. 7. The GMSC/SSP routes the call and connects the call to the VMSC through the TMSC.
Figure 4-24 shows the process to produce the CDR. Figure 4-24 Forwarding of fixed-to-mobile calls
GMSC/SSP TMSC VMSC MS-A/B/D TRANSIT MTC PSTN ROAM CFW
The
GMSC/SSP produces a ROAM CDR. In the CDR, the calling party is C and the called party is A. The GMSC/SSP produces the following two call forwarding CDRs (CFW): 1. The CDR for MS-A: the calling party is A, called party is B, and third party is C. 2. The CDR for MS-B: the calling party is B, called party is D, and third party is C. The VMSC produces a terminative CDR (MTC) to charge MS-D. The calling party is B, called party is D, and third party is C.
The
TMSC produces a transit CDR, where the calling party is C and called party is D. forwarding of mobile-to-fixed calls In this scenario, MS-A, MS-B, and MS-C are in the same VMSC. Subscriber D is a PSTN subscriber. When MS-A calls MS-B, the call is unconditionally forwarded from MS-B to MS-C and then from MS-C to Subscriber D. The call connection process is as follows: 1. The VMSC of MS-A requests the TLDN of MS-B from the HLR where MS-B is registered. 2. The HLR returns the forwarded-to number, the MDN of MS-C. 3. The VMSC requests the TLDN MS-C from the HLR, where MS-C is registered. 4. The HLR returns the forwarded-to number, the DN of D. 5. The VMSC routes the call and connects the call to the GMSC/SSP through the TMSC. 6. The GMSC connects the call to the PSTN. Figure 4-25 shows the process to produce the CDR. Figure 4-25 Forwarding of mobile-to-fixed calls
Call
GMSC/SSP TMSC VMSC MS-A/B/C TRANSIT MTC PSTN GATEWAY_ OUTGOING
MOC CFW
The
GMSC/SSP produces a GATEWAY_OUTGOING CDR. In the CDR, the calling party is A and the called party is D. The VMSC produces an MOC CDR to charge MS-A. In the CDR the calling party is A, called party is B, and the third party is D. The VMSC produces the following two CFW CDRs: 1. The CDR for MS-B: the calling party is B, called party is C, and third party is A. 2. The CDR for MS-C: the calling party is C, called party is D, and third party is A. The TMSC produces a transit CDR, where the calling party is A and called party is D. Call forwarding with all mobile subscribers in the same VMSC In this scenario, MS-A, MS-B, and MS-C are in the same VMSC. MS-C is a PPC subscriber. When MS-C calls MS-A, the call is unconditionally forwarded from MS-A to MS-B and the intelligent network is an overlay network. The call connection process is as follows: 1. The VMSC connects the call to the GMSC/SSP through the TMSC. 2. The GMSC/SSP requests the TLDN MS-A from the HLR where MS-A is registered.
3. The HLR returns the forwarded-to number, the MDN of MS-B. 4. The GMSC/SSP requests the TLDN of MS-B from the HLR where MS-B is registered.
5. The GMSC/SSP connects the call to the VMSC through the TMSC. Figure 4-26 shows the process to produce the CDR. Figure 4-26 Call forwarding with all mobile subscribers in the same VMSC
GMSC/SSP TMSC VMSC MS-A/B/C CFW TRANSIT MOC MTC
The The
VMSC produces an MOC to charge MS-C. GMSC/SSP produces a CFW CDR to charge MS-A. The VMSC produces an MTC CDR to charge MS-B. The TMSC produces two transit CDRs. The GMSC/SSP produces one transit CDR. The following are some remarks about CFW CDR: If a subscriber registered with CFU is the called party, the CDR is generated at the CSOFTX3000 that requests the TLDN. In the first two scenarios of the previous examples, the VMSC requests the TLDN and generates the CDR. In the third scenario, however, the GMSC/SSP requests the TLDN and generates the CDR. The CFW CDRs are produced at different places when two subscribers registered with CFNA and CFB are in the same location, but are configured with different forwarding conditions. The CDR for CFNA and CFB users is produced on the CSOFTX3000 that triggers the forwarding, usually the originating office or the gateway office. The fill-out rules for these two types of CFW CDRs are the same as that of the CFU CDRs. Only the service feature indications are different. CFD is a combination of CFB and CFNA. The prerequisites for trigging the CFD are the same as those for trigging CFB and CFNA. The only difference is that the Service Feature Indication in this scenario is CFD.
In the previous examples, calls are forwarded to PPC subscribers. If the forwarded-to number is not a PPC subscriber number, GMSC/SSP is not involved.
4.2.2 Examples of Producing Call Waiting CDRs

Call Waiting (CW) is a supplementary service originated by the network. When subscribers activate the CW service, they can receive a notice for another incoming call while holding the current call. In this case, they can choose to accept, refuse, or ignore this incoming call. In this scenario, MS-A and MS-B are in VMSCA, and MS-B has the CW service activated. 1. MS-A calls MS-B, and they are in conversation. 2. MS-C, from another network, calls MS-B and the CW service is activated. 3. MS-B holds the call with MS-A and starts conversation with MS-C.
Figure 4-27 shows the producing of the CDRs. Figure 4-27 Call waiting
GMSC TMSC VMSC MS-A/B ROAM TRANSIT MOC MTC MTC MS-C
The following describes the produced CDRs: The VMSC produces an MOC CDR to charge MS-A. In the CDR, the calling party is A and the called party is B.
The
VMSC produces an MTC CDR to charge MS-B. In the CDR, the calling party is A and the called party is B. The VMSC produces an MTC CDR to charge MS-B. In the CDR, the calling party is C, the called party is B, and the Service Feature Indication is CW. The GMSC/SSP produces a roam CDR. The TMSC produces a transit CDR.
4.2.3 Examples of Producing Call Transfer CDRs

If a subscriber registered with the Call Transfer (CT) service sets up two calls (incoming or outgoing calls), this subscriber can connect these two remote parties through an ordinary call. After the setup of connection, this subscriber releases the call connection with those two remote parties. After the CT service, the charging rule and rate remain. MOC CDRs and MTC CDRs are produced for each connected party. In this scenario, MS-A and MS-B are in the same VMSC. MS-A has the CT service registered and activated. MS-C is in another network. 1. MS-A calls MS-B, and the call is held. 2. MS-A calls MS-C and hangs up after MS-C is connected or alerted. 3. MS-B and MS-C start conversation.
Figure 4-28 shows the producing of the CDRs. Figure 4-28 Call Transfer
GMSC TMSC VMSC MS-A/B TRANSIT MS-C GATEWAY_ OUTGOING MOC MOC MTC
In this call process, CDRs are produced for two separate calls. One of the calls is between MS-A and MS-B, and the other call is between MS-A and MS-C. When the call between MS-B and MS-C is released, two MOC CDRs are produced for MS-A. In these two CDRs, MS-A is the calling party, while MS-B and MS-C are the called parties. The Service Feature Indication in the CDRs is CT. The following describes the produced CDRs: The VMSC produces an MOC CDR to charge MS-A. In the CDR, the calling party is A and the called party is B. The VMSC produces an MOC CDR to charge MS-A. In the CDR, the calling party is A and the called party is C. The Service Feature Indication in the CDR is CT. The VMSC produces an MTC CDR to charge MS-B. In the CDR, the calling party is A and the called party is B. The GMSC/SSP produces a gateway outgoing CDR. The TMSC produces a Transit CDR. Table 4-1 lists the billing start and end time for the CDRs. In the table, means billing is conducted, and means billing is not conducted. Table 4-1 Billing start and end time of the CDRs Calling time point AB AC None MOC MTC MOC GATEWAY_
OUTGOING 1. A-B connected 2. A-C connected 3. A conduct CT 4. B-C connected 5. Call released ; Start: 1 End: 5 ; Start: 1 End: 5 ; Start: 2 End: 5 Set CT tag ; Start: 2 End: 5
Calling time point AB AC 1. A-B connected 2. A-C rings 3. A conduct CT 4. B-C rings 5. B-C connected 6. Call released ; Start: 1 End: 6 ; Start: 1 End: 6 ; Start: 5 End: 6 Set CT tag ; Start: 5 End: 6 1. A-B connected 2. A-C rings 3. A conduct CT 4. B-C rings 5. B released or C premature release ; Start: 1
End: 5 ; Start: 1 End: 5
4.2.4 Examples of Producing Multiparty Service CDRs

The multiparty service enables a subscriber to communicate with multiple remote subscribers at the same time and to facilitate a multiparty meeting. The multiparty meeting includes Three-Way Calling (3WC) and Conference Call (CC). The 3WC service enables a subscriber to communicate with two remote subscribers at the same time. The CC service enables a subscriber to facilitate a multiparty conference. In this conference, each attendee can hear others. During the conference, the convener can hold the call and add or delete remote subscribers. The maximum number of remote subscribers that can be connected is registered in the HLR. In this scenario, MS-A and MS-B are in the same VMSC. MS-C is in another network. 1. MS-A calls MS-B and the call is held. 2. MS-A calls MS-C and starts conversation. 3. MS-A activates 3WC service and all the three parties are in conversation.
Figure 4-29 shows the producing of the CDRs. Figure 4-29 3WC service
GMSC TMSC VMSC MS-A/B TRANSIT MS-C GATEWAY_ OUTGOING MOC MTC MOC
The following describes the produced CDRs: The VMSC produces two MOC CDR to charge MS-A. The calling party is MS-A and the called parties are MS-B and MS-C. The VMSC produces one MTC CDR to charge MS-B. The calling party is MS-A and the called party is MS-B. The GMSC/SSP produces a gateway outgoing CDR. The TMSC produces a transit CDR. If MS-A activates the 3WC service: The VMSC produces an MOC CDR to charge MS-A. The calling party is MS-A and the called party is MS-B. The VMSC produces an MOC CDR to charge MS-A. The calling party is MS-A and the called party is MS-C. The Service Feature Indication is 3WC. If MS-A activates the CC service: The VMSC produces an MOC CDR to charge MS-A. The calling party is MS-A and the called party is MS-B. When MS-A calls MS-B using the operation service code, the Service Feature Indication is CC. The VMSC produces an MOC CDR to charge MS-A. The calling party is MS-A and the called party is MS-C. The Service Feature Indication is CC.
4.3 CDR Fill-Out Rules
This section introduces the fill-out rules of different types of CDRs.
4.3.1 Intra-MSC Call

The following describes the fill-out rules of the CDRs for intra-MSC calls.
Call from MS-A to MS-B

Table 4-2 lists the key fields and values of the MOC CDR for MS-A.
Table 4-2 Key fields and values of the MOC CDR for MS-A Key Field Value Description CDR_type MOC For billing on the calling party Caller_party_number MDN of A MDN of MS-A Called_party_number MDN of B Called party number being dialed, in the same format with the calling number Charged_MDN MDN of A The party to be charged, which is the MDN of the calling party Table 4-3 lists the key fields and values of the MTC CDR for MS-B. Table 4-3 Key fields and values of the MTC CDR for MS-B Key Field Value Description CDR_type MTC For billing on the called party Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Charged_MDN MDN OF B The party to be charged, which is the MDN of the called party
Call from MS-A to MS-B and Forwarded to MS-C

Table 4-4 lists the key fields and values of the MOC CDR for MS-A. Table 4-4 Key fields and values of the MOC CDR for MS-A Key Field Value Description CDR_type MOC For billing on the calling party Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number MDN OF C The third party number, which is valid when CFW occurs Charged_MDN MDN OF A The party to be charged, which is the MDN of the calling party
Table 4-5 lists the key fields and values of the CFW CDR for MS-B. Table 4-5 Key fields and values of the CFW CDR for MS-B Key Field Value Description CDR_type CFW For billing on the party that initiates CFW Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number MDN OF A The third party number, which is valid when CFW occurs Charged_MDN MDN OF B The party to be charged, which is the MDN of
the party that initiates CFW Table 4-6 lists the key fields and values of the MTC CDR for MS-C. Table 4-6 Key fields and values of the MTC CDR for MS-C Key Field Value Description CDR_type MTC For billing on the called party Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number MDN OF A The third party number, which is valid when CFW occurs Charged_MDN MDN OF C The party to be charged, which is the MDN of the called party
4.3.2 Gateway Outgoing Call

The following describes the fill-out rules of the CDRs for gateway outgoing calls.
Call from Local MS-A to MS-B in Other Network

Table 4-7 lists the key fields and values of the MOC CDR for MS-A. Table 4-7 Key fields and values of the MOC CDR for MS-A Key Field Value Description CDR_type MOC For billing on the calling party Caller_party_number MDN OF A MDN of the calling party
Key Field Value Description Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number - The third party number, which is valid when CFW occurs Charged_MDN MDN OF A The party to be charged, which is the MDN of the calling party Table 4-8 lists the key fields and values of the gateway outgoing CDR for MS-A. Table 4-8 Key fields and values of the gateway outgoing CDR for MS-A Key Field Value Description CDR_type GATEWAY_OUTGOING For inter-network settlement Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN -
Call from MS-A to MS-B and Forwarded to MS-C in Other Network

MS-A and MS-B are in the serving PLMN, whereas MS-C is in another LPMN. Table 4-9 lists the key fields and values of the CDR for MS-A. Table 4-9 Key fields and values of the CDR for MS-A Key Field Value Description CDR_type MOC For billing on the calling party Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number MDN OF C The third party number, which is valid when CFW occurs
Charged_MDN MDN OF A The party to be charged, which is the MDN of the calling party
Table 4-10 lists the key fields and values of the CFW CDR of MS-B. Table 4-10 Key fields and values of the CFW CDR of MS-B Key Field Value Description CDR_type CFW For billing on the party that initiates CFW Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number MDN OF A The third party number, which is valid when CFW occurs Charged_MDN MDN OF B The party to be charged, which is the MDN of the party that initiates CFW Table 4-11 lists the key fields and values of the gateway outgoing CDR for MS-B when the call is forwarded to MS-C. Table 4-11 Key fields and values of the gateway outgoing CDR for MS-B Key Field Value Description CDR_type GATEWAY_OUTGOING For inter-network settlement Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN -
4.3.3 Gateway Incoming Call

The following describes the fill-out rules of the CDRs for gateway incoming calls.
Call to MS-B in Serving PLMN from other PLMN

Table 4-12 lists the key fields and values of the MTC CDR of MS-B. Table 4-12 Key fields and values of the MTC CDR of MS-B Key Field Value Description CDR_type MTC For billing on the called party Caller_party_number MDN OF A MDN of the calling party
Key Field Value Description Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN MDN OF B The party to be charged, which is the MDN of the called party Table 4-13 lists the key fields and values of the roaming CDR. Table 4-13 Key fields and values of the roaming CDR Key Field Value Description CDR_type ROAM For inter-network settlement Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same
format with the calling number Third_party_number Charged_MDN -
Call from MS-A to MS-B and Forwarded to MS-C

MS-A and MS-B are in another network, whereas MS-C is in the serving PLMN. Table 4-14 lists the key fields and values of the MTC CDR of MS-C. Table 4-14 Key fields and values of the MTC CDR of MS-C Key Field Value Description CDR_type MTC For billing on the called party Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number MDN OF A The third party number, which is valid when CFW occurs Charged_MDN MDN OF C The party to be charged, which is the MDN of the called party
Table 4-15 lists the key fields and values of the roaming CDR. Table 4-15 Key fields and values of the roaming CDR Key Field Value Description CDR_type ROAM For inter-network settlement Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN -
4.3.4 Transit Call

The following describes the fill-out rules of the transit CDRs.
Call between other PLMN and Transit by Local Office

When MS-A and MS-B are in another PLMN and the call from MS-A to MS-B is transited by local MSC, the following CDRs are generated. Table 4-16 lists the key fields and values of the roaming CDR. Table 4-16 Key fields and values of the roaming CDR Key Field Value Description CDR_type ROAM For inter-network settlement Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN Table 4-17 lists the key fields and values of the gateway outgoing CDR for MS-A calling MS-B. Table 4-17 Key fields and values of the gateway outgoing CDR Key Field Value Description CDR_type GATEWAY_OUTGOING For inter-network settlement Caller_party_number MDN OF A MDN of the calling party
HUAWEI CSOFTX3000 CDR Description 4 Examples of CDR Producing
Issue 03 (2007-11-30) Huawei Technologies Proprietary 4-33
Key Field Value Description Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN When MS-A and MS-B are in the serving PLMN and the call from MS-A to MS-B is transited by local MSC, the following CDRs are generated. Table 4-18 lists the key fields and values of the transit CDR. Table 4-18 Key fields and values of the transit CDR Key Field Value Description CDR_type TRANSIT For inter-network settlement Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN -
Call from other PLMN to Local MS-B and Forwarded to other PLMN
When MS-A and MS-C are in another PLMN and MS-B is in the serving PLMN, the following CDRs are produced. Table 4-19 lists the key fields and values of the roaming CDR. Table 4-19 Key fields and values of the roaming CDR Key Field Value Description CDR_type ROAM For inter-network settlement Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN 4 Examples of CDR Producing HUAWEI CSOFTX3000 CDR Description 4-34 Huawei Technologies Proprietary Issue 03 (2007-11-30)
Table 4-20 lists the key fields and values of the CFW CDR. Table 4-20 Key fields and values of the CFW CDR Key Field Value Description CDR_type CFW For billing on the party that initiates CFW Caller_party_number MDN OF B MDN of the party that initiates CFW Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number MDN OF A The third party number, which is valid when CFW occurs Charged_MDN MDN OF B The party to be charged, which is the MDN of the party that initiates CFW Table 4-21 lists the key fields and values of the gateway outgoing CDR for the call forwarded from B to C Table 4-21 Key fields and values of the gateway outgoing CDR Key Field Value Description CDR_type GATEWAY_OUTGOING For inter-network settlement Caller_party_number MDN OF B MDN of the party that initiates CFW
Called_party_number MDN OF C Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN -
4.3.5 Intelligent Call

The following describes the fill-out rules of the IN call CDRs.
In the intelligent service CDR, intelligent service tags are used to indicate the service feature. This tag corresponds to the intelligent service key.
Mobile Originating Intelligent Call

Table 4-22 lists an intelligent call MOC CDR for the calling party is produced at the MSC, where the intelligent call originating process is triggered.
Table 4-22 Key fields and values of the intelligent MOC CDR Key Field Value Description CDR_type MOC For billing on the calling party Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number - Charged_MDN MDN OF A The party to be charged, which is the MDN of the calling party Intelligent_service_flag - Intelligent service tag of the party to be charged
Mobile Terminating Intelligent Call

Table 4-23 lists an intelligent MTC CDR for the called party is produced at the MSC where the intelligent call terminating process is triggered. Table 4-23 Key fields and values of the Key Field Value Description CDR_type MTC For billing on the called party Caller_party_number MDN OF A MDN of the calling party Called_party_number MDN OF B Called party number being dialed, in the same format with the calling number Third_party_number Charged_MDN MDN OF B The party to be charged, which is the MDN of the called party Intelligent_service_flag Intelligent service tag of the party to be charged
4.3.6 Short Message Call

SM Sending
Table 4-24 Key fields and values of the of the MO-SMS CDR Key Field Value Description CDR_type MO_SMS For charging the subscriber who sends the SM, or for statistics
Key Field Value Description Caller_party_number Subscriber
number of A MDN of the subscriber who sends the SM Called_party_number Subscriber number of B MDN of the subscriber who receives the SM Charged_MDN MDN number of A The party to be charged, which is the MDN of the subscriber who sends the SM SMC ID SMC address
SM Receiving
Table 4-25 Key fields and values of the MT-SMS CDR Key Field Value Description CDR_type MT_SMS For charging the subscriber who receives the SM, or for statistics Caller_party_number Subscriber number of A MDN of the subscriber who sends the SM Called_party_number Subscriber number of B MDN of the subscriber who receives the SM Charged_MDN MDN number of B The party to be charged, which is the MDN of the subscriber who receives the SM SMC ID SMC address
HUAWEI CSOFTX3000 CDR Description 5 CDR Control and Sorting Issue 03 (2007-11-30) Huawei Technologies Proprietary 5-1
CDR Control and Sorting
About This Chapter

The following table lists the contents of this chapter. Section Describes 5.1 Control on the Producing of CDR The reason and method of controlling the producing of specific types of CDR, such as the gateway outgoing CDR. 5.2 Number Conversion for CDRs The reason and method of number changing in CDRs. 5.3 CDR Sorting at Billing Center Sorting of intelligent service CDRs and ordinary CDRs.
5 CDR Control and Sorting HUAWEI CSOFTX3000 CDR Description 5-2 Huawei Technologies Proprietary Issue 03 (2007-11-30)
5.1 Control on the Producing of CDRs

The control on CDR producing helps network operators to conduct flexible billing policies.
Basic CDR Types

Incorrect execution of the command MOD BBLL may result in complete loss of CDRs of a certain type. Do not execute the command unless you obtain the written permission from the director of the billing center and from a Huawei technical support engineer. By default, the CSOFTX3000 generates all types of CDRs. You can determine the types of CDR that must be produced in the basic CDR configuration. You can use the command LST BBLL to query the CDR types. For example, if you intend to stop the producing of the MTC CDR and INMTC CDR: MOD BBLL: BTYP=MTC, MMN="LOCAL", GBLL=FALSE; MOD BBLL: BTYP=INMTC, MMN="LOCAL", GBLL=FALSE;
Gateway Outgoing CDR

The GMSC generates a gateway outgoing CDR when: A call is from a gateway office to another mobile network. A call is from a gateway office to the PSTN. To allow the producing of a gateway outgoing CDR to a certain office direction, use the command ADD BLLCTRL and set the parameters, as listed in Table 5-1. Table 5-1 Example of setting parameter for gateway outgoing CDRs Parameter Setting Office direction name Direction name of the peer office Peer office type Other network Generate gateway outgoing bill at GMSC Yes
Roam CDR
The GMSC generates a roaming CDR for calls originated from the PSTN or other mobile networks. To allow the producing of a roaming CDR to a certain office direction, use the command ADD BLLCTRL and set the parameters, as listed in Table 5-2. Table 5-2 Example of setting parameter for roam CDRs Parameter Setting Office direction name Direction name of the peer office Peer office type Other network Generate roam bill at GMSC Yes
Ensure that you allow the producing of gateway outgoing CDR and roaming CDR in the basic control configuration. The peer office type must be "other network".
Call Attempt CDR

When a call occupies a trunk but is not successfully connected, the CSOFTX3000 generates a call attempt CDR. To allow the producing of call attempt CDRs on a certain trunk group, use the command MOD N7TG and set the parameter Generate call attempt bill to YES.
Transit CDRs
Before you allow the producing of the gateway outgoing CDR, roaming CDR, and transit CDR, ensure that you set the Generate bill to Yes in the basic control configuration. For a transit call, a transit CDR is produced. To generate a transit CDR, the peer office must be in the same PLMN. Use the command ADD BLLCTRL and set the parameter Peer office type to CDMA network.
CDRs for Long-Duration Calls

When the duration of a conversation reaches a threshold, the CSOFTX3000 creates an
intermediate CDR. As the conversion continues, the CSOFTX3000 creates more intermediate CDRs each time the timer expires. This avoids the loss of the entire CDRs due to call drop. To set the timer for producing intermediate CDRs, use the command MOD LBTM. The CSOFTX3000 allows timer time from 0 to 120 minutes. The default timer for long-duration call is 30 minutes. The CSOFTX3000 does not generate the intermediate CDR if you set the timer time to zero.
5 CDR Control and Sorting HUAWEI CSOFTX3000 CDR Description 5-4 Huawei Technologies Proprietary Issue 03 (2007-11-30)
CDRs for Multiple Time Zones

When subscribers of the same CSOFTX3000 are in different time zones, the CDRs must reflect the correct local time of the subscriber. This is because the differentiated price packages offered by network operators to their customers are often based on an accurate time. When setting up a connection, the CSOFTX3000 checks the time zone of the calling and called party, and converts the time in the CDR into the local time when the call is released. You can use the command SET TZ to set the local time zone and summer time on the CSOFTX3000.
5.2 Number Conversion for CDRs

Sometimes you may require conversion of the numbers in the CDRs, such as changing the calling number, the called number, the third party number, or the called party MDN. Incorrect configuration may cause unexpected loss to the network operator. Therefore, conduct dialing test to the relevant number segment after you convert the numbers, and ensure that all types of numbers in the CDR are correctly converted. Use the command ADD BLLMNG when you change the numbers in the CDRs.
5.3 CDR Sorting at Billing Center

The billing center sorts the final CDR and discards CDRs that need not be charged. CDR sorting includes the following types: IN CDR sorting Ordinary CDR sorting
5.3.1 Sorting of IN CDRs

IN CDR sorting is carried out in the following two IN modes: Target network Overlay network
Target Network Mode

The billing center can identify the IN CDRs according to the IN service identifier and user types. The relevant value is in the IN service identifier of IN CDRs, and the value is invalid in the IN service identifier of ordinary CDRs.
Overlay Network Mode

The PPC service in the overlay network requires that IN subscribers have special number segment or access code, so that the sorting of CDRs can be conducted at the billing center based on the following: The calling number segment or access code in the MOC CDRs from the originating office, and The called number segment or access code in the MTC CDRs from the called office
5.3.2 Sorting of Ordinary CDRs
The sorting of ordinary CDRs is subject to the charging policy of network operators. For example, at the billing center, CDRs can by sorted by types. In case a CDR type is "emergency call", the CDR is deleted.

Huawei Csoftx3000

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei Csoftx3000

Uploaded by

Copyright:

Available Formats

HUAWEI CSOFTX3000 CDR Description Contents Issue 03 (2007-11-30) Huawei Technologies Proprietary i

2 CDR Producing.................................................................... .......................................................2-1

3 CDR Types and Formats...................................................................... .....................................3-1

4 Examples of CDR Producing ............................................................................. ......................4-1

5 CDR Control and Sorting ............................................................................. ............................5-1

Overview of Billing System

About This Chapter

1.1 Basic Concepts

1.2 Introduction to Billing Subsystem

WCCU/WCSU Call Control Units

WCCU/WCSU Bill Pool

1.3 Billing Process

About This Chapter

2.1 General Process of CDR Producing

2.2 Call Data Collection

Data Collection for Mobile Originated Calls

Data Collection for Mobile Terminated Calls

2.3 Producing of CDR

2.3.1 Producing of Ordinary Service CDR

2.3.2 Producing Intelligent Service CDR

Control Mechanism Involved with Intelligent Service Billing

General Principle of Producing Intelligent CDRs

2.4 CDR Storage

2.4.1 CDR Storage Paths

2.4.2 Storage of Original CDRs

Issue 03 (2007-11-30) Huawei Technologies Proprietary 2-7

2.4.3 Storage of Final CDRs

2.5 CDR Processing on iGWB

Figure 2-10 CDR processing flow

Sorting Format Conversion Original CDR Final CDR

CDR Format Conversion

2.6 CDR Sending

2.7 CDR Checking

CDR Types and Formats

About This Chapter

3.1 CDR Types

3.1.1 CDR Classification by Storage

3.1.2 CDR Classification by Call Process

3.1.3 CDR Classification By Scenario

MOC CDR and MTC CDR

MO_SMS CDR and MT_SMS CDR

ISDN_MO CDR and ISDN_MT CDR

The ONLY CDR is produced for the ONLY service.

Enhanced Call Attempt CDR

Brazil SMP Attempt CDR

3.2 Final CDR Format

Examples of CDR Producing

About This Chapter

4.1 Examples of Producing Basic Call CDRs

4.1.1 Examples of Producing Ordinary Call CDRs

between Mobile Subscribers Served by Different PLMN Carriers

MS-A and MS-B in the Same VMSC

MS-A and MS-B in Different VMSCs

Call from MS-A to PSTN Subscriber

Call from PSTN Subscriber to MS-B

Calls between Mobile Subscribers Served by Different PLMN Carriers

4.1.2 Examples of Producing IN Call CDRs in Overlay Network

Call Between PPC Subscribers

Calls from PPC Subscriber to PSTN Subscriber

Calls from PSTN Subscribers to PPC Subscriber

Calls from Ordinary Mobile Subscriber to Local PPC Subscriber

Calls from PPC Subscribers to Local Ordinary Mobile Subscribers