Global Call Reference

FUNCTION SPECIFICATION

23/155 17-CSA 121 01/8 Uen A

Copyright

© Ericsson GmbH 2017. All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Contents

Contents

1 Revision Information 1

2 General Information 3
2.1 Introduction 3
2.2 Concepts 3
2.2.1 Network Call Reference 3
2.2.2 Network ID 3
2.2.3 Call reference ID 3
2.2.4 Node ID 3
2.2.5 Originating Node 3

3 Function 5
3.1 General 5
3.2 Generation of GCR 6
3.3 Distribution of GCR for Calls 7
3.4 GCR in Charging Data Output 8
3.5 Interaction with Network Call Reference 9
3.6 Interwork with Network Nodes Not Supporting GCR 9

4 Operational Conditions 11
4.1 External Conditions 11
4.2 Application Parameters 11
4.3 Commands 11
4.4 Printouts 11
4.5 Capabilities 11

Glossary 13

Reference List 15

23/155 17-CSA 121 01/8 Uen A | 2017-01-23

Global Call Reference

23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Revision Information

1 Revision Information

Changes in MSC-S 15A

This document is based on Function Specification Global Call Reference,

23/155 17-AXE 106 30/2 Uen Rev. A.

This document has been revised as follows:

• Rev. A
− Editorial changes only.

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 1

 Global Call Reference

2 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 General Information

2 General Information

2.1 Introduction
The ‘‘Global Call Reference’’ (GCR) function is used by operators to globally
correlate Call Data Records (CDRs) belonging to the same call.

2.2 Concepts
The following concept can be found in the Glossary of Terms and Acronyms:

• Mobile Originating Location Request

2.2.1 Network Call Reference

The Network Call Reference (NCR) function has a similar purpose to GCR to
allow CDR correlation. The NCR can only be conveyed by some signaling
systems and can only be used network internally because it does not contain a
Network ID (NI) and is, therefore, not globally unique.

2.2.2 Network ID
The NI is part of the GCR parameter on ISUP and BICC and on charging data
output. It is a unique identifier of the network where the GCR is generated.

2.2.3 Call reference ID

The call reference ID is part of the GCR parameter on ISUP and BICC and also
of the charging data output. It is a sequence number assigned to the call. The
call reference ID is assigned by the node that is specified by the node ID.

2.2.4 Node ID
The node ID is part of the GCR parameter on ISUP and BICC and also of the
charging data output. It is a unique identifier of the node within the network
specified by the NI.

2.2.5 Originating Node

The originating node is the node from where the call or Location Request (LR)
originates. This includes nodes where Service Control Point (SCP) initiated
calls are started.

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 3

 Global Call Reference

4 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Function

3 Function

3.1 General
Operators can use the GCR function to globally correlate CDRs belonging
to the same call.

A call can be set up through multiple nodes, which can be part of different
networks. Each node generates charging data in terms of CDRs separately.
These CDRs are used as input for billing systems. Figure 1 shows an example
of a call originating from Node 1 of Network 1, being set up through Node 2 of
transit Network 2, and finally terminating in Network 3;

Figure 1 Call Path Through the Nodes of Different Networks and Related
CDR Output

The GCR function provides a unique call ID called GCR. It is generated in the
originating node and distributed through the signaling system to nodes that
participate in the call. Each node that supports the GCR can output it into
CDRs. The GCR is, therefore, a unique property of the call, which is present in
all CDRs generated for the call.

The GCR function consists of the following three main parts:

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 5

 Global Call Reference

Generation of GCR
Nodes generate a value for the GCR if they do not
receive it through signaling systems. It is also generated
for multiple Mobile Originating Location Requests
(MO-LRs). The GCR is generated regardless of
charging.

Distribution of GCR parameter through the traffic signaling system

The GCR is conveyed through the Initial Address
Message (IAM) on ISUP and BICC.

Output of GCR in CDR

The received or generated GCR is included in the CDRs
and is available to external billing systems.

Figure 2 shows the complete parameter layout of GCR:

Figure 2 GCR Parameter Layout

3.2 Generation of GCR

If the GCR function is active, a GCR is generated for calls in the originating
node. A GCR is also generated for multiple MO-LRs. If the GCR parameter is
not received on the incoming signaling system at non-originating nodes, the
setting of an application parameter determines if the node generates a GCR to
be used in the further call path or if the call is handled without GCR in this node.

The node that generates the GCR combines the predefined NI and node ID
with a new sequence number into one parameter.

The NI is specified in terms of six digits using application parameters. The

specified digits are coded as an object identifier according to ITU-T X.690,
Reference [2].. The resulting length of the NI is between 3 and 5 octets.

The node ID is a binary number. It is specified by command and used by a

node when generating the GCR. The node ID is generated with a fixed length
of 2 octets.

6 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Function

The call reference ID is a binary number. It is generated with a fixed length of

3 octets.

The maximum length of the GCR, which is generated by Ericsson MSC-S,

is 13 octets.

3.3 Distribution of GCR for Calls

The GCR parameter is sent in the IAM on ISUP and BICC to be distributed as a
unique reference of the call to all nodes that participate in the call path.

The following statements apply to the GCR parameter:

Supported Parameter Length

If the received GCR exceeds 15 octets, the parameter
is treated as unrecognized. In this case, a new GCR
can be generated depending on the setting of an AXE
parameter.

Route Based Suppression

The sending of the GCR can be inhibited for ISUP and
BICC using route-based suppression. This can be
applied to, for example, network gateways if forwarding
the GCR parameter to the other network is forbidden.

Call Diversion and Redirection

In general, all call legs that belong to one call use
the same GCR. This includes, but is not limited to:
call forwarding, roaming call forwarding, rerouting, or
reselection.

Inter-MSC Handover and Inter-MSC Relocation

The GCR of the call is also sent by the MSC-A in the
IAM (ISUP or BICC) on the handover or relocation call
leg towards the MSC-B. The nodes in the call path to
the new location of the Mobile Station (MS) then receive
and are able to use this GCR. If supplementary services
are invoked for the call in the MSC-A, multiple calls with
different GCRs can be assigned to the MS. In this case,
the MSC-A uses the GCR that belongs to the active call
at the time of handover or relocation.

IN and CAMEL Service

The GCR of the incoming call leg is used for all
related outgoing legs, which are created by the Service
Switching Function (SSF) or the GSM Service Switching
Function (gsmSSF).

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 7

 Global Call Reference

3.4 GCR in Charging Data Output

The GCR is output into CDRs. The following CDR types can contain the GCR:

• Transit

• MS Originating

• MS Terminating

• Call Forwarding

• Roaming Call Forwarding

• Transit IN Outgoing Call

• ISDN Call Forwarding

• IN Incoming Call

• IN Outgoing Call

• Subscriber Service Procedure

• Location Services

The subscriber service procedure CDR contains the GCR only if the invoked
subscriber service is related to a call. The GCR of the related call is output only
in case of a call-related unstructured supplementary service data transaction,
or in case of a High Penetration Notification (HPN) if the establishment of a
mobile terminating call fails. The availability of the HPN feature depends on
commercial agreements.

The location services CDR contains the GCR only in case of multiple MO-LRs
or in case of a call-related Mobile Terminating Location Request (MT-LR). If a
user initiates a multiple MO-LR a CDR is separately generated for each single
LR. A GCR is generated, which is then included in all CDRs belonging to the
multiple MO-LR.

The GCR can be output into event modules within the CDRs for the following
traffic cases:

Multi-Party Call (Supplementary Service Invocation event module)

The GCR of the active call, from where the multi-party
Supplementary Service (SS) is invoked, is chosen as
GCR for the multi-party. This GCR is output in SS
invocation event modules for the multi-party call if a new
multi-party is created or if additional calls are added to
the multi-party.

8 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Function

Explicit Call Transfer (SS Invocation event module)

The GCR of the active call, from which explicit call
transfer is invoked, is output in both related SS
invocation event modules.

3.5 Interaction with Network Call Reference

The GCR and NCR are mutually exclusive. If the GCR function is active,
no NCR is generated, conveyed, or output. The administration of the GCR
influences the NCR function.

3.6 Interwork with Network Nodes Not Supporting GCR

In order to use the function as described in this document to correlate CDRs
globally, it needs to be active in all network nodes. If the GCR is only activated
in some network nodes, it is not possible to use NCR or GCR to correlate calls
on a network-wide basis.

The GCR and the NCR are conveyed on BICC in the same parameter. If the
GCR function is only activated in some network nodes, it is possible that an
NCR is received and interpreted as a GCR by the receiving node. A route
parameter exists, which allows to inhibit the sending of GCR for ISUP and BICC
on a route basis. This can be applied temporarily until the network is updated.

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 9

 Global Call Reference

10 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Operational Conditions

4 Operational Conditions

4.1 External Conditions

ITU-T ISUP 2000, ETSI ISUP V4, or ITU-T BICC CS2 or derived market
variants are a prerequisite for GCR.

4.2 Application Parameters

An AXE parameter belonging to the parameter set AXENODEC allows to activate
or deactivate the GCR function.

An AXE parameter belonging to the parameter set AXENODEC defines whether

a GCR is generated by the node when the feature is active but no GCR has
been received from the incoming signaling system, or if the received GCR
is discarded.

Two AXE parameters belonging to the parameter set AXENODEC are used to
define the NI, which is applied when the GCR is generated by the node.

4.3 Commands
A command exists to specify on route basis if the GCR parameter is sent.

A command for changing charging exchange properties exists to define the

exchange number that is used as node ID. This data is used when the GCR
is generated.

Printout commands exist to display exchange properties and route data.

4.4 Printouts
A printout exists for CDR output. This printout can contain the GCR parameter.

A printout exists to display the route data. This printout contains the route-based
suppression settings for the GCR parameter.

A printout exists to display the charging exchange property data. This printout
contains the setting of the node ID that is used in the generation of the GCR.

4.5 Capabilities
The GCR function can be applied with minor impact on system load.

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 11

 Global Call Reference

The handling and charging data output of the GCR function is adapted to
Forlopp.

Ericsson MSC-S supports the handing of GCRs with a maximum of 15 octets

received from and sent on signaling systems.

Ericsson MSC-S nodes generate the GCR using 3 octets for the call reference
ID. The corresponding value range of the call reference ID implies that the
generated GCR value is used again after 16,777,216 calls, which includes
unsuccessful call attempts.

The GCR and NCR features are mutually exclusive.

12 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Glossary

Glossary

AXE MS
Public Telephone Exchange System Mobile Station

BICC MSC-A
Bearer Independent Call Control Anchor MSC

CAMEL MSC-B
Customized Applications for Mobile Network Non-Anchor MSC
Enhanced Logic
MSC-S
CDR MSC Server
Call Data Record
MT-LR
GCR Mobile Terminating Location Request
Global Call Reference
NCR
gsmSSF Network Call Reference
GSM Service Switching Function
NI
HPN Network ID
High Penetration Notification
SCP
IAM Service Control Point
Initial Address Message
SS
ID Supplementary Service
Identifier
SSF
IN Service Switching Function
Intelligent Network

ISDN
Integrated Services Digital Network

ISUP
ISDN User Part

LR
Location Request

LSB
Least Significant Bit

MO-LR
Mobile Originating Location Request

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 13

 Global Call Reference

14 23/155 17-CSA 121 01/8 Uen A | 2017-01-23

 Reference List

Reference List

CPI Library Internal References

[1] Glossary of Terms and Acronyms

GLOSSARY

Standard References

[2] ITU-T Recommendation X.690 (07/2002), Information technology – ASN.1

encoding rules: Specification of Basic Encoding Rules (BER), Canonical
Encoding Rules (CER) and Distinguished Encoding Rules (DER)

23/155 17-CSA 121 01/8 Uen A | 2017-01-23 15