Professional Documents
Culture Documents
Charging Subsystem
Charging Subsystem
Charging Subsystem
Table of Contents
i
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
The Charging Subsystem comprises the Exchange Charging Subsystem and BAM
Charging Subsystem, as shown in Figure 6-1.
The Exchange Charging Subsystem mainly collects and generates charging
information. It fetches the charging information for sending to the BAM Charging
Subsystem.
The BAM receives the charging information coming from the exchange (i.e. exchange
tickets), generates the BAM tickets and transfers the charging information for storing.
Fetch Fetch
Generate ticket Detailed ticket
B F
Mail
A A Free ticket
M M
box
Restore ticket Meter ticket
BAM FAM
I. Generating principle
6-1
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
Generation of the exchange charging information mainly depends upon the data
configured by the operator. Different attributes play a major role in the data
management such as:
In terms of service attribute, there are local, national, international, etc.
In terms of charging party, there are calling party charging, called party charging,
both-party charging, third party charging, etc.
In terms of ticket, there are ordinary ticket, free ticket, complaint ticket, etc.
In terms of charging type, there are detailed ticket and meter table.
In terms of charging attribute, there are subscriber ticket and trunk ticket.
The operator can combine these attributes at will in the data management to achieve
requirements.
The complaint ticket is for the subscriber to view. All the other tickets are for the
telecommunication administration itself. Hence, if a certain number is configured as the
charging complaint in the subscriber connection data, the complaint ticket would be
generated first before other charging operations are conducted.
If ‘both-party charging’ has been set as the charging party in the charging data, then
both the calling & called parties would be charged and a ticket would be generated for
both of them.
If the charging method has been set as free, then the free ticket would be generated.
If the charging type has been set as meter table, then meter to be employed must be
set as well (from meter 1 to meter 10); if the charging type has been set as meter table
and detailed ticket, the meter table would be generated first before the detailed ticket
generation.
The storing of the exchange charging information refers to the storing of the exchange
tickets, which is divided into two levels: ticket buffer and extended memory. See Figure
6-2.
Extended
memory
When the ticket buffer is full, the content would be written into the extended memory
once for all, thereby the write/read efficiency of the extended memory could be
improved.
6-2
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
(AM/CM) (BAM)
Begin
Co nn ec t
ACK 0
D .a ta 0
.
.
D a ta 1 9
AC K 20
D a ta 2 0
.
.
.
D a ta 3
9
A C K 40
.
.
.
.
.
D a ta 1
80
D a ta 1 9
. 9
.
.
ACK 200
E nd
End
6-3
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-4
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
I. Detailed ticket
1) Detailed ticket has a length of 118 bytes and the meanings are described below in
every field in an ascending sequence:
[Serial Number]: 4 bytes
This is the unified sequence number for all the tickets since the starting of the
switching system, represented in a long format.
[Ticket Type]: 1 byte
Represents the type of the call a ticket records, with the following values:
0x01: Detailed ticket
0x02: Call record of DBO
0x03: Call record of IN
0x05: TAX record
0xF0: Meter table ticket
0xF1: Meter table statistics
0xF2: Trunk duration statistics
0xF3: Free call statistics
0xFF: Warn ticket
0x55: Failed call ticket (Incomplete call watch ticket, Partial record ticket)
Note: Ticket with this four byte valued 0x01 should be explained with the format
below.
[Checksum]: 1 byte
The sum of all the bytes except the first three fields (serial number, ticket type,
checksum), which is used to check the validity of a ticket.
6-5
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-6
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-7
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
12: Bank 2
13: Bank 3
14: Bank 4
15: Reserved
[Charging Number DnSet]: 1 byte
Indicates the numbering set of charging number.
[Charging Number]: 10 bytes
Indicates the charging number (Datatype: packed BCD, with "0xF" filling the
unoccupied space).
[Caller Number DnSet]: 1 byte
Indicates the numbering set of caller number.
[Connected Number DnSet]: 1 byte
This is the numbering set of connected number.
[Caller Number Address Nature]: 0.5 byte
This indicates the address nature of caller number.
Value:
0: Subscriber number (Caller number = Local number)
2: National valid number (Caller number = Trunk code + Local number)
3: International number (Caller number = Country code + trunk code + Local
number)
[Connected Number Address Nature]: 0.5 byte
Indicates the address nature of connected number.
Value:
0: Subscriber number, Connected number = Local number
2: National valid number, Connected number = Trunk code + Local number
3: International number, Connected number = Country code + trunk code +
Local number
[Caller Number]: 10 bytes
Data type: packed BCD, with "0xF" filling the unoccupied space.
[Connected Number]: 10 bytes
Data type: packed BCD, with "0xF" filling the unoccupied space.
[Dialed Number]: 12 bytes
Data type: packed BCD, with "0xF" filling the unoccupied space.
[CENTREX Group Number]: 2 bytes
6-8
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-9
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-10
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
5: Supplementary Service
[Service type]: 0.5 byte
Value:
0: Intra-office
1: Local
2: Local toll
3: National toll
4: International toll
5: Supplementary Service
6: PABX call
14: Local CENTREX
[Supplementary Service type]: 1 byte
Value:
0: CENTREX out
1: Register abbreviated dialing
2: Use abbreviated dialing
3: Cancel abbreviated dialing
4: Cancel all abbreviated dialing
5: Check abbreviated dialing
6: Activate hot line
7: Use hot line
8: Cancel hot line
9: Check hot line
10: Activate outgoing call barring
11: Use outgoing call barring
12: Cancel outgoing call barring
13: Check outgoing call barring
14: Activate alarm call
15: Use alarm call
16: Cancel alarm call
17: Check alarm call
18: Activate multi-alarm call
19: Cancel multi-alarm call
20: Check multi-alarm call
6-11
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-12
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-13
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-14
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-15
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
15: Unknown
Others: Reserved
[Conversation End Reason]: 0.5 byte
Value:
0: Caller on-hook; 1: Called on-hook; 2: Exception
[Reason Number]: 1 byte
[Release Index]: 1 byte
[UUS1 Count]: 1 byte
It indicates the UUS1 switch number (64 bytes form a segment).
[UUS2 Count]: 1 byte
It indicates the UUS2 switch number (64 bytes form a segment).
[UUS3 Count]: 1 byte
It gives the count of UUS3 switch (64 bytes form a segment)
[Reserved]: 4 bytes
6-16
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
Credit card complaint ticket (attributes: non centralized charging, subscriber, complaint,
calling and credit card detailed ticket)
Free of charge complaint ticket (attributes: non-centralized charging, subscriber,
complaint, free of charge and common detailed ticket).
Note: Irrespective of the charging mode (for example, "Detailed ticket" or "Meter table"),
a complaint ticket will be generated as long as the calling party has a complaint request.
z User alarm ticket (attributes: non-centralized charging, subscriber, alarm, calling
and common detailed ticket)
Trunk alarm ticket (attributes: non-centralized charging, trunk, alarm, calling and
common detailed ticket).
At the called side:
z Called detailed ticket (attributes: non-centralized charging, subscriber, charging,
called and common detailed ticket)
Outgoing trunk detailed ticket (attributes: non-centralized charging, outgoing trunk,
calling and common detailed ticket)
Note: If the charging mode is "Meter table", the above tickets will not be generated.
z Called user complaint ticket (attributes: non-centralized charging, subscriber,
complaint, called and common detailed ticket)
Outgoing trunk complaint ticket (attributes: non-centralized charging, outgoing trunk,
complaint, calling and common detailed ticket)
Note: Irrespective of the charging mode (for example, "Detailed ticket" or "Meter table"),
a complaint ticket will be generated if the called party has a complaint request.
z User alarm ticket (attributes: non-centralized charging, subscriber, alarm, called,
and common detailed ticket)
Trunk alarm ticket (attributes: non-centralized charging, trunk, alarm, called and
common detailed ticket).
Meter table ticket has totally 118 bytes and the meanings are described below in every
field in an ascending sequence:
[Serial Number]: 4 bytes
Indicates the unified number for the tickets generated since the starting of the
switching system, represented in a long int. format.
[Ticket Type]: 1 byte
Indicates the type of the ticket recorded, with the following values:
0x01: Detailed ticket
0x02: Call record for DBO
0x03: Call record for IN
0x05: Records generated by TAX
0xF0: Meter table ticket
6-17
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-18
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-19
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
This is the statistics ticket for the counting of various meters used for subscribers or
trunks with any of the four call types (intra-office, incoming, outgoing, and tandem). It
has a length of 118 bytes and the meanings are described below in every field in an
ascending sequence:
[Serial Number]: 4 bytes
Indicates the unified number for all the tickets generated since the starting of
the switching system, represented in a long int.
[Ticket Type]: 1 byte
Indicates the type of the call ticket recorded. Value:
0x01: Detailed ticket
0x02: Call record for DBO
0x03: IN call record
0x05: Record generated by TAX
0xF0: Meter table call ticket
0xF1: Meter table statistics ticket
0xF2: Trunk duration statistics ticket
0xF3: Free call statistics ticket
0xFF: Warn ticket
0x55: Failed call ticket (Incomplete call watch ticket, Partial record ticket)
Note: ticket with this field valued 0xF1 can be interpreted by the following way.
[Checksum]: 1 byte
It indicates the sum of all the bytes except the first three fields (Serial number,
Ticket type and Checksum), which is used to check whether a ticket is a valid
one.
[Reserved]: 0.5 byte
6-20
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-21
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
This ticket keeps statistics of the times of incoming calls, tandem calls & calls going out
of the current trunk (outgoing and tandem calls) and their duration. It has a length of 118
bytes and the meanings are described below in every field in ascending sequence:
[Serial Number]: 4 bytes
Indicates the unified number for all the tickets since the starting of the switching
system, represented in a long int.
[Ticket Type]: 1 byte
Indicates the type of the call ticket recorded, Value:
0x01: Detailed ticket
0x02: Call record for DBO
0x03: IN call record
0x05: Call record generated by TAX
0xF0: Meter table ticket
6-22
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
6-23
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
This ticket keeps statistics of the duration and count of all the free calls. It has a length
of 118 bytes and every field in ascending sequence describes the meanings:
[Serial number]: 4 bytes
Indicates the unified number for all the tickets since the starting of the switching
system, represented in a long int.
[Ticket type]: 1 byte
Indicates the type of the call ticket, Value:
0x01: Detailed ticket
0x02: Call record for DBO
0x03: IN call record
0x05: Record generated by TAX
0xF0: Meter table ticket
0xF1: Meter table statistics ticket
0xF2: Trunk duration statistics ticket 0xF3: Free call statistics ticket
0xFF: Warn ticket
Others: Reserved
0x55: Failed call ticket (Incomplete call watch ticket, Partial record ticket)
6-24
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
Note: Tickets with this field valued 0xF3 can be interpreted in the following way:
[Checksum]: 1 byte
It gives the sum of all the bytes except those occupied by the first three fields
(Serial number, Ticket type, and Checksum), which is used for checking the
validity of the ticket.
[Reserved]: 0.5 byte
[Validity]: 0.125 byte
Value:
0: Valid; 1: Invalid
[Reserved]: 1.375 bytes
[Ticket Generated Time]: 6 bytes
Indicates the date and time when a free call ticket is generated, with the format:
YYMMDDHHMMSS.
YY: 00-99 (binary)
MM: 1-12 (binary)
DD: 1-31 (binary)
1HH: 0-23 (binary)
MM: 0-59 (binary)
SS: 0-59 (binary)
[Module number]: 1 byte
Indicates the number of the module where the free call statistics ticket is
generated, with value ranging from 1 to 240.
[Reserved]: 1 byte
[Free Conversation Duration]: 4 bytes
It gives the statistical value of the duration of the free calls since the generation
of the latest free call statistics ticket.
[Free Call Times]: 2 bytes
Give the count of free calls since the generation of the latest free call statistics
ticket.
[Reserved]: 96 bytes
6-25
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
FAM Charge
HDLC center
Net Net
adapter adapter
A B
Net
adapter Net Net
adapter adapter
C D
LAN switch
WS/ticket
counter
Figure 6-4 Method of connection between the ticket server and BAM
6-26
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
Bill
server
Router
DDN or other
HUB E1 device
WAN
Trunk
Router
E1 device
Net
adapter
charge center HUB
Net adapter
charge center
As shown in the figure, the ticket server can connect to the charging center through
WAN or LAN.
3) Ticket processing
With a ticket server, tickets are processed in the following manner:
Step 1: Original tickets from the MPU to the BAM
A call ticket after generation, is buffered in the ticket pool of the host. The BAM regularly
sends a ticket request to the host. The host after receiving the request sends the tickets
to the BAM where they are stored on the hard disk. The ticket is first buffered on the
BAM.
After obtaining original tickets, the BAM makes a simple analysis of them. If a ticket is
checked out to be too long or its checksum is incorrect, it is taken as an incorrect ticket.
Tickets of this type are put in a special error ticket file to be manually processed. Other
tickets are stored in files with ".bil" being their extension name, which are created every
one hour.
Step 2: Original ticket sent from the BAM to ticket server
A ticket sending process runs in BAM, which can check if there is any new ticket in the
BAM as frequent as once every minute. If a new ticket is generated, it will be packaged
& sent to the ticket server and a corresponding log is made for it.
To ensure the transmission of original ticket to the ticket server from the BAM in a most
speedy & secure way, TCP/IP is used at the bottom layer and an internally defined
communication protocol is used at the application layer. The ticket in the BAM is
transmitted to the ticket server in packets with unique packet number and the sending &
receiving terminals have detailed logs. Functions, such as automatic network
re-connection after disconnection, resending of ticket packages by BAM when no
confirmation message received and the filtering of repeated transferred ticket packages
by ticket server are provided.
Step 3: The ticket server receives original tickets from the BAM
6-27
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
The ticket server receives the ticket data packages from the BAM. After opening and
authenticating these packages, the server stores the original tickets in the hard disk. It
then sends confirmation messages to the BAM and makes corresponding logs.
Step 4: The ticket server processes the received tickets
After receiving an original ticket, the ticket server saves a copy as a backup and then
processes the original ticket. First of all, it sorts the tickets. This can be done on the
basis of the value of any field in the ticket. Besides, for fields like calling and called,
which are represented in BCD code, sorting can also be made on the basis of its prefix.
The sorting conditions can be field value relations (>, < or =) or combination of these
relations (and/or). Also, original tickets go through format conversion here, that is to say,
reformatting the binary original tickets into universal text tickets. The text format,
including the content, width of each field, filler, separator of the ticket, etc., can be set
and the fields can be customized, like adding a '(' in front of each ticket or a ')' at the end
of each ticket. Then the tickets sorted in corresponding category after processing.
Step 5: Reformatted ticket is transferred from the ticket server to the charging center
After storing the tickets to the place specified by the user, the ticket server provides the
charging center with the FTP/FTAM interface. It supports Server or Client as FTP &
Responder as FTAM and opens the generated tickets to the charging center. The
charging center gets tickets from the ticket server through the LAN or WAN. The ticket
server can also send tickets actively to the charging center through Client of FTP.
4) Definition of ticket file format
z Content and format of reformatted detailed ticket
The format of the reformatted ticket is shown in Table 6-1:
6-28
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
Item Content
All the fields contained in original detailed tickets, such as calling, called,
inbound trunk group, outgoing trunk group, start year, start month, start
day, start hour, start minute, start second, end year, end month, end day,
end hour, end minute, end second, duration (second), charged target,
Content list ticket type, charge type, call type, service type, Bearer Services, count of
B channels, Centrex group number, ticket type, CTX group number,
calling CTX private number, called CTX private number, calling user type,
call terminating cause, charging, connected number, charge number
initial set and terminal service
Alignment list Left-aligned and right-aligned
Filler list Space, zero and none
Separator list Comma, space, colon, slash, dot and none
Length Ranging from 0 to 99 digits
Customized domain Any character string can be customized
Item Content
Fields, such as calling number, trunk group number, charged target, number initial
set, count of calls in table 1, count of calls in table 2, count of calls in table 3, count of
calls in table 4, count of calls in table 5, count of calls in table 6, count of calls in table
Content list
7, count of calls in table 8, count of calls in table 9, pages of table 1, pages of table 2,
pages of table 3, pages of table 4, pages of table 5, pages of table 6, pages of table
7, pages of table 8, pages of table 9 and pages of table 10.
Align list Left-aligned and right-aligned
Filler list Space, zero and none
Separator list Comma, space, comma, slash, dot and none
Length Ranging from 0 to 99 digits
Customized domain Any character string can be customized
6-29
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
needs. The full-auto mode conveniences the user and the semi-auto mode
provides the user with to a certain extent of flexibility. In general situation, the user
can select full-auto mode, while in some special situation, the user can use the
semi-auto backup mode.
z User control to the process of auto-back and manual backup is enabled. When
either of the two backup modes is in service, the user can suspend it. The user can
start automatic or manual backup through the ticket station at any time. If the
CD-ROM is found to be insufficient before its timing replacement, an alarm
message will be sent to the alarm box of the switch.
z As for final ticket files, tickets of different types can be backed up onto different
media, or only tickets of certain types can be copied.
z Support multiple backup.
z The user can view how many ticket files are stored on the backup disk and make
the label for MO on this basis.
6) Main technical indices for ticket server
The main technical indices for the ticket server include:
z The ticket server can process 1600 pages of original tickets per second.
z The alarms from the ticket server are sent to the BAM's alarm station, which then
sends all these alarms in unified manner to the alarm box of the switching system
for centralized alarms. When the ticket server is disconnected from the BAM, the
alarm box will also issue alarms.
z The minimum duration for the detailed ticket is 5 minutes from the subscriber
completing the call to the ticket being transmitted to the ticket server.
z The ticket server can support 20 terminals in operation and 60 operators.
7) Instructions about the ticket server
z TCP/IP is recommended for the network layer & transmission layer in the
connection between the ticket server & charging center and FTP or FTAM are
recommended for the application layer.
z The supported and not supported mode of X.25 connection between ticket server
and charging center
a. The ticket server is connected with the charging center via 2 routers. The routers can
be connected via X.25 protocol and the ticket server & routers are connected via
TCP/IP. This connection mode can match the ticket server of Huawei and it is illustrated
in Figure 6-6:
6-30
Technical Manual Chapter 6
C&C08 Digital SPC Switching System Charging Subsystem
Bill
server
Net
adapter TCP/IP
Router
HUB
X.25
Router
HUB
Net
adapter
charge center
b. Ticket server is connected with the charging center via one router and an X.25
adapter card is plugged into the PC of the charging center. Note that Huawei's ticket
server does not support this type of connection. The connection method is shown
in Figure 6-7:
Bill
server
Net
adapter TCP/IP
Router
HUB
X.25
X.25 card
charge center
6.
6-31