Abstract: The present subject matter discloses a method and a device for identifying if a call is answered by one of a first communication device (110-1) and a second communication device (110-2). Further, based on the identification, it may be determined whether a caller identification associated with the first communication device (110-1) is unavailable in contacts data of the second communication device (110-2). Furthermore, it may be ascertained whether duration of the call is greater than a threshold call duration. Based in part the determining and the ascertaining charges for the call are computed for the second communication device (110-2).
FIELD OF INVENTION
[0001] The present subject matter relates to communication networks and,
particularly but not exclusively, to charging of calls in the communication networks.
BACKGROUND
[0002] Communication devices, such as cellular phones, personal digital
assistants, portable computers, and desktop computers, provide users with a variety of
mobile communication services and computer networking capabilities. These
communication services allow data, for example, voice calls, to be exchanged between
the users. Further, the users are charged for the communication services provided by a
service provider or an operator, based on various parameters. Examples of such
parameters can be location of a user who initiates a call, i.e., a caller party, and location
of a user to whom the call is directed, i.e., a called party.
[0003] Typically, a user subscribes to the communication services provided by
the operator in a pre-defined geographic coverage area or circle, which is also referred to
as a home network of the user. Further, when the user makes or receives calls outside the
home network, the user is considered to be on "roaming". Generally, if a call is made or
received in the home network, the user is charged according to the normal calling tariffs.
However, if the call is made or received outside the home network, roaming tariffs are
charged in addition to the normal calling tariffs. Owing to higher call charges incurred
while roaming, users often time don't prefer to use the communication services, which
may not only be inconvenient for the user but also result in loss of revenue for the
operators.
SUMMARY
[0004] This summary is provided to introduce concepts related to determination
of call charges in a communication network. This summary is not intended to identify
essential features of the claimed subject matter nor is it intended for use in determining or
limiting the scope of the claimed subject matter.
[0005] In an embodiment, a method includes identifying whether a call is
answered by one of a first communication device or a second communication device. In
one implementation, the call is a roaming terminating call. If it is identified that the call is
answered, it is determined whether a caller identification associated with the first
2
communication device is unavailable in contacts data of the second communication
device. In one example, the determination may be based on an identification parameter.
Further, it may be ascertained whether a duration of the call is greater than a threshold
call duration. Based, in part, on the determination of the caller identification and the
ascertainment of the call duration, charges for the call may be computed. Further, the
charges are computed for the second communication device.
[0006] In another embodiment, a device for computing charges for a call is
described. The device includes a processor and a memory coupled to the processor. The
memory includes a call analysis module configured to identify whether the call is
answered by one of a first communication device and a second communication device.
The call analysis module is also configured to determine, based on the identification,
whether a caller identification of the first communication device is unavailable in
contacts data of the second communication device. Additionally, the call analysis module
ascertains whether a duration of the call is greater than a threshold call duration. Further,
the call analysis module may also be configured to compute charges for the call, based in
part on the determination of the caller identification and the ascertainment of the call
duration. The charges for the call may be computed for the second communication
device. In one example, the device is a network entity of a communication network
having the first communication device and the second communication device.
[0007] In accordance with another embodiment of the present subject matter, a
computer readable medium having embodied thereon a computer program for executing a
method is described. The computer readable medium perform acts including identifying
whether a call is answered by one of a first communication device and a second
communication device and determining, based on the identifying, whether a caller
identification of the first communication device is unavailable in contacts data of the
second communication device. Further, the computer readable medium may also include
ascertaining whether a duration of a call is greater than a threshold call duration.
Furthermore, the computer readable medium may also perform the act of computing
charges for the call based on a secondary charge schedule, if the duration of the call is not
greater than the threshold call duration and the caller identification of the first
3
communication is not available in the contacts data of the second communication device.
The charges are computed for the second communication device.
[0008] According to another embodiment of the present subject matter, a
communication device for providing an identification parameter is described. The
communication device includes a processor and a memory having a caller identification
module. The caller identification module is configured to determine whether a caller
identification of a first communication device is available in the contacts data of a second
communication device. Further, the caller identification module is configured to provide
the identification parameter indicative of availability of the caller identification in the
contacts data. In one example, the communication device is the second communication
device.
[0009] In accordance with another embodiment of the present subject matter, a
computer readable medium having embodied thereon a computer program for executing a
method is described. The computer readable medium performs acts including determining
whether a caller identification of a first communication device is available in contacts
data of a second communication device and providing an identification parameter
indicative of availability of the caller identification in the contacts data. In one example,
the identification parameter is provided in call control (CC) connect message.
BRIEF DESCRIPTION OF THE FIGURES
[0010] The detailed description is described with reference to the accompanying
figures. In the figures, the left-most digit(s) of a reference number identifies the figure in
which the reference number first appears. The same numbers are used throughout the
figures to reference like features and components. Some embodiments of system and/or
methods in accordance with embodiments of the present subject matter are now
described, by way of example only, and with reference to the accompanying figures, in
which:
[0011] Figure I illustrates an exemplary communication network environment,
according to an embodiment of the present subject matter;
[0012] Figure 2(a) illustrates a system for determining charges for a call in a
GSM network environment, in accordance with an embodiment of the present subject
matter;
4
[0013] Figure 2(b) is an exemplary call flow diagram indicating determination of
charges for a terminating call in the GSM network environment shown in Fig. 2(a),
according to an embodiment of the present subject matter; and
[0014] Figure 3 illustrates a method to determine charges for a call in a
communication network, in accordance with an embodiment of the present subject
matter.
[0015] It should be appreciated by those skilled in the art that any block diagrams
herein represent conceptual views of illustrative systems embodying the principles of the
present subject matter. Similarly, it will be appreciated that any flow charts, flow
diagrams, state transition diagrams, pseudo code, and the like represent various processes
which may be substantially represented in computer readable medium and so executed by
a computer or processor, whether or not such computer or processor is explicitly shown.
DESCRIPTION OF EMBODIMENTS
[0016] Systems and methods for determination of charges for a call in a
communication network are described. In one example, the communication network is a
wireless communication network. In one implementation, the charges are determined for
a terminating call in a roaming scenario, also referred to as a roaming terminating call.
Typically, in the communication network, a user, referred to as a calling party, makes a
call to another user, also referred to as a called party. The call made by a calling party is
called an originating call, also referred to as, an outgoing call. Likewise, the call received
by the called party can be understood as the terminating call or the incoming call.
Further, each user in the communication network has a pre-defined geographic coverage
area associated with it, based on his/her subscription. The part of communication network
covered by the pre-defined geographic coverage area can be understood as the home
network of the user. When the user makes or receives calls outside the home network, the
user is considered to be on "roaming". Accordingly, the calls received or made outside
the home network, may be understood as calls received or made in a roaming scenario.
Further, a communication network serving a user while roaming may be referred to as a
visited network.
[0017] Generally, tariff charges, such as, call charges are higher in the roaming
scenario as compared to tariff charges for the home network. For example, typically,
5
there are higher charges for the terminating calls in case the called party is in the visited
network as compared to charges for the terminating calls in case the called party is in the
home network. Since in the roaming scenario, the terminating calls may be charged, the
called party may be reluctant to receive calls from unknown caller parties. An unknown
caller party may be understood as a caller party whose caller identification, such as,
phone number is not present in the contacts data of a communication device of the called
party.
[0018] The terminating call from the unknown caller party is often times an
unsolicited call, for example, calls for marketing products and wrong numbers, however
such calls may be important as well. In case of a terminating call being an unsolicited
call, the called party often realizes, only after answering the unsolicited call, that the
terminating call should not have been received, since the called party ends up getting
charged for the terminating call. The charging of a call may be considered as a deduction
of credit from the called party's account in case of a pre-paid subscription or billing for
the call in case of a post-paid connection.
[0019] For example, consider a case where a user with a pre-paid connection has
just enough balance to receive one call. In such a case, if the user answers a terminating
call, which turns out to be an unsolicited call, the user may not be able to take any other
call unless he adds some credit to his account. In such cases, if the user is anticipating an
important call, which may be from an unknown caller party, the user may either be
hesitant in answering the terminating call or in case, he answers an unsolicited call, the
user may not be able to take any other terminating call. Similarly, in case of post-paid
connections, receiving such unsolicited calls may result in heavy bill.
[0020] Further, in certain cases, the called party may miss a call from an
unknown caller party, and accordingly, to determine if the call was an important call or
not, the called party (which will now become a caller party) may place a call to the
unknown caller party (which will now become a called party). In case, the unknown
caller party is an unsolicited caller party, the called party may be charged for the
originating call. Thus, the called party may have to incur additional charges for the
originating calls made to the unknown caller party not only in roaming scenario, but also,
when the called party is in the home network. Further, such unnecessary charging for the
6
unsolicited calls, which can be originating or terminating calls, may be inconvenient for
users in both the home network and the visited network.
[0021] According to an embodiment of the present subject matter, systems and
methods for determining charges for a call in a communication network are described.
The call may be an originating call or a terminating call. Further, the originating call may
be made and the terminating call may be received in a visited network or a home
network. The systems and methods can be implemented in a variety of computing
devices. The computing devices that can implement the described method(s) include, but
are not limited to, desktop computers, hand-held devices, laptops or other portable
computers, and the like. Additionally, the method can be implemented in any of the
communication networks, such as Global System for Mobile Communication (GSM)
network, Universal Mobile Telecommunications System (UMTS) network. Personal
Communications Service (PCS) network. Time Division Muhiple Access (TDMA)
network, Code Division Muhiple Access (CDMA) network. Next Generation Network
(NGN), Public Switched Telephone Network (PSTN), and Integrated Services Digital
Network (ISDN). Although the description herein is with reference to certain networks,
the systems and methods may be implemented in other networks and devices, albeit with
a few variations, as will be understood by a person skilled in the art.
[0022] For the purposes of explanation and not as limitation, a communication
device whose caller identification is to be checked in contacts data of another
communication device, may be understood as the first communication device, and the
another communication device may be understood as the second communication device.
Additionally, availability of a caller identification associated with the first
communication device in the contacts data of the second communication device can be
understood to indicate that the user of the first communication device is known to the
user of the second communication device. Similarly, unavailability of a caller
identification associated with the first communication device in the contacts data may
indicate that the user of the first communication device is not known to the user of the
second communication device.
[0023] In one implementation, it may be identified whether a call is answered by
a user of a communication device. In one example, the communication device answering
7
the call may be the first communication device. In said example, the first communication
device can be understood as a called party and the second communication device can be
understood as the caller party. In another example, the communication device answering
the call may be the second communication device. In said example, the first
communication device can be understood as a caller party and the second communication
device can be understood as the called party. Thus, it will be understood that the call may
be terminating call or an originating call. Further, the call may be a roaming call, i.e., a
call made or received in a roaming scenario.
[0024] If the call is answered, it may be determined if the caller identification
associated with the first communication device is unavailable in the contacts data of the
second communication device. The caller identification can be considered to be any
detail associated with the first communication device, which facilitates identification of
the first communication device, or to say, a user of the first communication device. In one
example, the caller identification is a contact number of the first communication device.
Further, the contacts data may be a repository, which includes caller identification of
users known to a user of the second communication device. In one example, the contacts
data is a phonebook of the second communication device. Further, the contacts data may
be stored in the second communication device and/or it may also be available to a Mobile
Switching Center (MSC).
[0025] In one implementation, an identification parameter indicative of
availability of the caller identification of the first communication device in the contacts
data of the second communication device is obtained. In one example, the identification
parameter may be provided by the second communication device. Additionally or
alternately, a network entity of the communication network may be configured to
determine the identification parameter.
[0026] In one implementation, upon obtaining the identification parameter, it may
be determined if the caller idenfification of the first communicafion device is unavailable
in the contacts data. If it is determined that the caller identification is present in the
contacts data, charges for the call are computed based on a primary charge schedule. The
primary charge schedule includes usual cost structure based on a call plan of the second
communication device. Further, in one implementation, it may be ascertained, if a
8
duration of the call is greater than a threshold call duration. The threshold call duration
may be selected such that the second communication device is able to determine whether
the call is an unsolicited call or not. For example, the threshold call duration may be 5
seconds or 10 seconds.
[0027] Further, in case it is determined that the call duration of the call is greater
than the threshold call duration, the charges for the call may be computed, for example,
based on the primary charge schedule. However, if it is determined that the call duration
of the call is not greater than the threshold call duration and the caller identification
associated with the first communication device is unavailable in the contacts data of the
second communication device, charges for the call may be computed based on a
secondary charge schedule. The secondary charge schedule includes discounted rates or
charges for calls. Accordingly, the call is charged at a rate lower than the usual rates. The
discounted rate may include 100% discount, 75 % discount and so on, for the calls.
Further, it will be understood that different charges may be applicable for terminating and
originating calls. For example, if the first communication device is an unknown caller
party and the call duration of the call answered by the second communication device
(which is now the called party) is less than the threshold call duration, the second
communication device may not be charged at all for the call.
(0028] In another example, consider that the second communication device is the
caller party and the first communication device (which is now the called party) answers
the call. Further, if the caller identification of the first communication device is
unavailable in the contacts data of the second communication device and the call duration
of the call is less than the threshold call duration, the second communication device may
be charged a discounted rate, say, fNR 0.25 per minute instead of usual FNR 1 per
minute.
[0029] Thus, in case a call is received from or made to an unsolicited party, the
second communication device may release the call before the lapse of the threshold call
duration and accordingly, the second communication device may not have to
unnecessarily pay for such unsolicited calls. Further, in case the second communication
device realizes that the call is an important call, the second communication device may
9
release the call after the expiration of the threshold call duration and the charges for the
call may be computed based on the primary charge schedule.
[0030] Since, the calls are charged at a discounted rate, users, for example, users
while on roaming, may not hesitate to take the calls from or make calls to unknown caller
parties, thereby ensuring that no important calls are missed. Such a provision will not
only help in reducing call charges incurred by the users due to unimportant calls but will
also cause an increase in call traffic, thereby increasing an operator's revenue.
[0031] It should be noted that the description and figures merely illustrate the
principles of the present subject matter. It will thus be appreciated that those skilled in the
art will be able to devise various arrangements that, although not explicitly described or
shown herein, embody the principles of the present subject matter and are included within
its spirit and scope. Furthermore, all examples recited herein are principally intended
expressly to be only for pedagogical purposes to aid the reader in understanding the
principles of the present subject matter and the concepts contributed by the inventor(s) to
furthering the art, and are to be construed as being without limitation to such specifically
recited examples and conditions. Moreover, all statements herein reciting principles,
aspects, and embodiments of the present subject matter, as well as specific examples
thereof, are intended to encompass equivalents thereof.
[0032] It will also be appreciated by those skilled in the art that the words during,
while, and when as used herein are not exact terms that mean an action takes place
instantly upon an initiating action but that there may be some small but reasonable delay,
such as a propagation delay, between the initial action and the reaction that is initiated by
the initial action. Additionally, the word "connected" is used throughout for clarity of the
description and can include either a direct connection or an indirect connection.
[0033] Figure 1 illustrates a communication network environment 100
implementing a network entity 105 for determining charges for a call, according to an
embodiment of the present subject matter. The communication network environment 100
includes one or more communication devices 110-1, 110-2, 110-3, and 110-N
(collectively referred to as communication devices 110) communicating with each other
through a communication network 115. The communication devices 110 are physical
equipments used by a caller party and a called party to communicate with each other. The
10
communication devices 110 may include, without limitation, desktop computers, handheld
devices, laptops or other portable computers, network computers, mobile phones,
landline phones, and the like. Each of the communication devices 110 works on a
communication protocol as defined by the communication network 115 to which the
communication device 110 is coupled.
[0034] The communication network 115 may be a wireless or a wired network, or
a combination thereof. The communication network 115 can be a collection of individual
networks, interconnected with each other and functioning as a single large network (e.g.,
the internet or an intranet). Examples of such individual networks include, but are not
limited to. Global System for Mobile Communication (GSM) network, Universal Mobile
Telecommunications System (UMTS) network. Personal Communications Service (PCS)
network. Time Division Multiple Access (TDMA) network. Code Division Multiple
Access (CDMA) network. Next Generation Network (NGN), Public Switched Telephone
Network (PSTN), and Integrated Services Digital Network (ISDN). Depending on the
technology, the communication network 115 includes various network entities, such as
gateways, routers; however, such details have been omitted for ease of understanding.
[0035] The forgoing description is explained with reference to the communication
devices 110-1 and 110-2 and it will be understood that the same can be extended to other
communication devices as well. In order to qommunicate with each other, each of the
communication devices 110-1 and 110-2 connects to its respective base transceiver
stations (not shown in the figure), which provide radio coverage within a ceil. Multiple
base transceiver stations connect to a base station controller (not shown in the figure),
which provides local switching to effect handover between the base stations. The base
station controller is further connected to a mobile switching center (MSC), such as 120-1
and MSC 120-2, which is responsible for call handling of subscribers, i.e., a called party
and a caller party. For example, the communication device 110-1, which may be in it's
home network and can be to the MSC 120-1, hereinafter interchangeably referred to as
Home-MSC (H-MSC) 120-1, through its own base station controller and other network
entities (not shown) to transfer data, such as voice calls and messages, to the called party.
In another example, the communication device 110-2, which may be currently outside it's
home network, can be coupled to the MSC 120-2, hereinafter interchangeably referred to
11
as visited-MSC (V-MSC) 120-2, through its respective base station controller and other
network entities.
[0036] Further, the H-MSC 120-1 and the V-MSC 120-2, may be associated with
a corresponding visitor location register (VLR), such as a VLR 125-1 and a VLR 125-2,
which store on a temporary basis, data for handling calls set up or received by
communication devices 110 registered with the VLR. For example, the H-MSC 120-1
may be associated with the VLR 125-1 and the V-MSC 120-2 may be associated with the
VLR 125-2. It would be appreciated by a person skilled in the art that the H-MSC 120-1
and VLR 125-1 may be implemented as separate entities or can be implemented within a
single unit. Similarly, the V-MSC 120-2 and the VLR 125-2 may be implemented as
separate entities or can be implemented within a single unit.
[0037] In one implementation, in order to connect two MSCs 120-1 and 120-2,
the communication network 115 also includes a gateway MSC (G-MSC) 130, which acts
as a node to interconnect the two MSCs 120-1 and 120-2. It will be understood that GMSC
130 may be a separate entity or functionalities of the G-MSC 130 may be integrated
with the functionalities of the H-MSC 120-1 or the V-MSC 120-2. The G-MSC 130, the
H-MSC 120-1 and the V-MSC 120-2, as per one implementation, include processor(s)
and a memory (not shown in the figure). The processor(s) can be a single processing unit
or a number of units, all of which could include multiple computing units. The
processor(s) may be implemented as one or more microprocessors, microcomputers,
microcontrollers, digital signal processors, central processing units, state machines, logic
circuitries, and/or any devices that manipulate signals based on operational instructions.
Among other capabilities, the processor(s) are configured to fetch and execute computerreadable
instructions stored in the memory. The memory may include any computerreadable
medium known in the art including, for example, volatile memory such as
SRAMs and DRAMs and/or non-volatile memory such as EPROMs and flash memories.
[0038] For the purpose of explanation, and not as a limitation, the communication
device 110-1 is hereinafter interchangeably referred to as a first communication device
110-1 and the communication device 110-2 is hereinafter interchangeably referred to as a
second communication device 110-2. Further, in one implementation, the second
12
communication device 110-2 may not be in it's home network and accordingly it may be
understood that the second communication device 110-2 is on roaming.
[0039] Although the description of Figure 1 has been made with respect to a
terminating call in a roaming scenario, it will be understood that the network entity 105
may determine charges for an originating call in home or visited network as well. A
roaming terminating call may be understood as a call received by a user, when the user is
outside the geographical coverage area of its home network, i.e., in a visited network. For
example, consider a case, where the second communication device 110-2, which is in a
visited network, is receiving a call from the first communication device 110-1. In said
example, the H-MSC 120-1, upon receiving a call from the first communication device
110-1, forwards the call to the G-MSC 130 to route the call to a MSC, say, V-MSC 120-2
that is currently serving the second communication device 110-2. Accordingly, the GMSC
130 identifies the home location register (HLR) 135 of the second communication
device 110-2, for example, in case of GSM and UMTS networks, the HLR 135 may be
identified using Mobile Subscriber Integrated Services Digital Network (ISDN)
(MSISDN) number of the second communication device 110-2. Typically, an HLR stores
information associated with each cellular service subscriber registered in the
corresponding network. The subscriber information may include an address of an MSC
that covers the subscriber's home location and the address of an MSC where the
subscriber is currently located or was last located. The G-MSC 130 may query the HLR
135 for routing information, such as the current location of the second communication
device 110-2 in order to connect the call.
[0040] The HLR 135 requests the VLR 125-2 associated with the geographical
area in which the second communication device 110-2 is presently residing to provide a
temporary number, a Mobile Station Roaming Number (MSRN), of the second
communication device 110-2. The HLR 135 may provide the MSRN of the second
communication device 110-2 to the G-MSC 130. Based on the MSRN, the G-MSC 130
identifies the V-MSC 120-2 and the associated VLR 125-2 currently serving the second
communication device 110-2 and the call is accordingly forwarded to the V-MSC 120-2.
[0041] Further, the G-MSC 130 may be coupled to the network entity 105, which
may be configured to operate in an intelligent network architecture. The network entity
13
105 may be implemented in a device, such as, computer, laptop, desktop, mainframe
computer, and the like. The network entity 105 enables operators to deploy operatorspecific
Value Added Services (VAS). The network entity 105, amongst other things,
includes a call analysis module 140. Although, the network entity 105 has been illustrated
external to the G-MSC 130, it will be understood that the network entity 105 may be
internal to the G-MSC 130 as well. In case of GSM and CDMA networks, intelligent
network (IN) services can be provided by a service control point (SCP). The network
entity 105 includes, for example, the logic for one or more services provided by the
operator. The G-MSC 130 communicates with the network entity 105 for providing the
services. For example, in GSM networks, the G-MSC 130 communicates with the
network entity 105 over Customized Applications for Mobile Enhanced Logic (CAMEL)
protocol and in CDMA networks, the communication between G-MSC 130 and the
network entity 105 occurs over Wireless Intelligent Network (WIN) protocol.
[0042] Further, prior to forwarding the call to the V-MSC 120-2, G-MSC 130
activates the associated network entity 105. The network entity 105 may determine if the
second communication device 110-2 is allowed to receive the call, if so, the G-MSC 130
forwards the call to the V-MSC 120-2, which in turn establishes the call with the second
communication device 110-2. The call established by the V-MSC 120-2 and received by
the second communication device 110-2 can be understood as a roaming terminating call.
Once, the call is established and the second communication device 110-2 answers the
call, the call analysis module 140 of the network entity 105 determines if caller
identification, for example, contact number of the first communication device 110-1 is
unavailable in contacts data of the second communication device 110-2.
[0043] In one implementation, the second communication device 110-2 is
configured to determine if the caller identification is stored in the contacts data. The
second communication device 110-2 may further be configured to provide the details
regarding presence or absence of the caller identification in the contacts data to G-MSC
130. For example, the second communication device 110-2 may be configured to provide
an identification parameter, which indicates whether or not the caller identification of the
first communication device 110-1 is stored in the contacts data of the second
communication device 110-2.
14
[0044] In another implementation, the G-MSC 130 may have the contacts data
associated with the second communication device 110-2. For example, the G-MSC 130
may get the contacts data from the HLR 135, i.e., an HLR corresponding to the second
communication device 110-2, in case the user of the second communication device 110-2
has synchronized the contacts data with the HLR 135. In said implementation, the call
analysis module 140 may determine the caller identification based on the contacts data
available with the G-MSC 130. For example, the G-MSC 130 may provide the
identification parameter to the network entity 105. In another example, the network entity
105 may itself determine the identification parameter by querying the G-MSC 130.
[0045] If the call analysis module 140 determines that the caller identification is
present in the contacts data of the second communication device 110-2, the call charges
are computed based on a primary charge schedule. The primary charge schedule is
indicative of the usual or default charges that are to be applied for the terminating call.
For example, if typically calls during roaming are to be charged at fNR 1 per minute then
the present call is charged at FNR 1 per minute. In another example, if the called party has
taken a special plan in which customized primary charges are to be applied for a call then
in said example these customized charges are applied, for instance, the call from a
particular user may be charged at customized primary charges.
[0046] In one implementation, the call analysis module 140 is further configured
to ascertain if a duration of the call, i.e., call duration, was greater than a threshold call
duration. Further, if it is ascertained that the call duration is greater than the threshold call
duration, the call is charged based on the primary charge schedule. However, if it is
ascertained that the call duration is less than the threshold call duration and the caller
identification associated with the first communication device 110-1 is not stored in the
contacts data, call charges for the second communication device 110-2 are computed
based on a secondary charge schedule. In one example, the secondary charge schedule
may indicate that the call is not to be charged at all. In another example, the secondary
charge schedule may indicate that reduced or discounted charges are to be applied for the
call, say, instead of usual INR 1 per minute, fNR 0.5 per minute may be charged.
[0047] Thus, in case the call is from an unknown caller party, say, first
communication device 110-1, the called party, say, the second communication device
15
110-2 may release the call before the lapse of the threshold call duration if the called
party determines that this call is an unsolicited call. Accordingly, the called party in the
roaming scenario may not have to unnecessarily pay for such unsolicited calls. Further, in
case after answering the call from an unknown caller party, the called party determines
that the terminating call is an important call, the called party, may release the call based
on his preferences, which is typically after the expiration of the threshold call duration.
Accordingly, in said case the call is charged based on the primary charge schedule.
[0048] Additionally or alternately, in case the second communication device 110-
2 is not able to answer the call from a first communication device 110-1, the second
communication device 110-2 may make a call to the first communication device 110-1 to
determine if the call that is missed is an important call or not. As mentioned previously,
the call analysis module 140 may obtain the identification parameter. Based on the
identification parameter, if the call analysis module 140 determines that the caller
identification of the first communication device 110-1 (which in this case will be a called
party) is not in the contacts data of the second communication device 110-2 (which in
this case will be a caller party) and duration of the call is less than the threshold call
duration, the call analysis module 140 may charge for the call based on the secondary
charge schedule.
[0049] For example, the second communication device 110-2, either in its home
network or while roaming, may miss a call from an unknown number. If the second
communication device 110-2 reverts the call and realizing that the call is an unimportant
one releases the call within the threshold call duration, the call charges for the second
communication device 110-2 are computed based on the secondary charge schedule and
accordingly discounted charges are applied for the call. Further, in case the caller
identification of the first communication device 110-1 is available in the contacts data or
the duration of the call is greater than threshold call duration, the call analysis module
140 may compute call charges for the call based on the primary charge schedule. The
primary charge schedule may indicate that usual tariffs are applicable for the calls,
originating as well as terminating. The primary charge schedule and the secondary charge
schedule may be saved in a database (not shown in the figures) associated with the
network entity 105.
16
[0050] Further, in one embodiment, the network entity 105 may also include a
counter to keep track of number of times a call is received from or made to the first
communication device 110-1 in a predefined time-period, say, 24 hours. So, in case caller
identification of the first communication device 110-1 is not stored in the contacts data of
the second communication device 110-2 and the call duration is less than threshold call
duration, but, the second communication device 110-2 had received calls from the first
communication device 110-1 greater than a predetermined number of times in the
predefined time period, then the call is charged based on the primary charge schedule.
Similarly, in case caller identificafion of the first communication device 110-1 is not
stored in the contacts data of the second communication device 110-2 and the call
duration is less than threshold call duration, but, the second communication device 110-2
had called the first communication device 110-1 greater than a predetermined number of
times, then the call is charged based on the primary charge schedule. Thus, the call
analysis module 140 determines whether the call is answered greater than a
predetermined number of times in a predefined time-period.
[0051] Figure 2(a) illustrates an exemplary GSM network environment 200 for
determining charges for a call, and Figure 2(b) illustrates an exemplary call flow diagram
205 indicating determination of charges for a terminating call in a GSM network 210
shown in Fig. 2(a), according to an embodiment of the present matter. The various arrow
indicators used in the call-flow diagram depict the transfer of data between the second
communication device 110-2 and various entities in the communication network, i.e., the
GSM network 210. Although the description of Figure 2(a) and Figure 2(b) has been
made in considerable detail with respect to a GSM network, it will be understood the
charges for the terminating calls in a roaming scenario may determined for other
networks as well, for example, CDMA network.
[0052] The communication network environment 200 includes, amongst other
things, the first communication device 110-1 and the second communication device 110-
2 communicating via the GSM network 210. In one implementation, a call initiated by
the first communication device 110-1 may be routed to the second communication device
110-2 via, the H-MSC 120-1, the G-MSC 130, and the V-MSC 120-2. Further, the G-
17
MSC 130 may be coupled to a SCP 215, which is an example of the network entity 105,
to provide various services.
[0053] In one implementation, the SCP 215 includes processor(s) and a memory
(not shown in the figures). The processor(s) can be a single processing unit or a number
of units, all of which could include multiple computing units. The processor(s) may be
implemented as one or more microprocessors, microcomputers, microcontrollers, digital
signal processors, central processing units, state machines, logic circuitries, and/or any
devices that manipulate signals based on operational instructions. Among other
capabilities, the processor(s) are configured to fetch and execute computer-readable
instructions stored in the memory. The memory may include any computer-readable
medium known in the art including, for example, volatile memory such as SRAMs and
DRAMs and/or non-volatile memory such as EPROMs and flash memories.
[0054] In one implementation, to enable a user for making or receiving a call,
while on roaming and be reachable at the same number, the GSM network environment
200 may implement the CAMEL protocol. Typically, before routing the terminating call
to the second communication device 110-2, it may be determined if the second
communication device 110-2 has an active CAMEL subscription. The information
pertaining to CAMEL subscription, also called, CAMEL subscription information (CSl)
may be stored in the HLR 135. In order to obtain CSI, the G-MSC 130 may send a
routing information request to the HLR 135. In response, the HLR 135 may provide
routing information response, which includes the CSI that indicates if the CAMEL
subscription is active or not and the same is indicated by step 205-1 of the call flow 205.
If the CSI indicates that CAMEL subscription for the second communication device 110-
2 is active, a functional entity, say, gsm Service Switching Function (gsmSSF) 220, of the
G-MSC 130 and a functional entity, gsm Service Control Function (gsmSCF) 225, of the
SCP 215, are activated and CAMEL specific handling is initiated. The gsmSSF 220
interfaces the G-MSC 130 to the gsmSCF 225. The gsmSCF 225 includes service logic to
implement Operator Specific Services (OSS). The gsmSCF 225 may be interfaced with
the gsmSSF 220, the GSM specialized Resource Function (gsmSRF), and the HLR 135.
The gsmSRF is a functional entity which provides various specialized resources. The
gsmSRF may be interfaced with the gsmSCF 225 and the G-MSC 130.
18
[0055] The CAMEL specific handling may be initiated with the gsmSSF 220
sending an Initial detection point (InitialDP) message to the gsmSCF 225 for requesting
instructions from the gsmSCF 225 and the same is indicated by step 205-2. The InitialDP
indicates detection of trigger, which can be understood as a condition under which
external service logic is to be invoked to implement the OSS. In response to the
InitialDP, the gsmSCF 225 may send a request report Basic Call State Model (BCSM)
message to gsmSSF 220 and the same is indicated by step 205-3. The request report
BCSM message can be understood to be a request to identify the occurrence of an event,
for example, call answered, route select failure, no reply, and called party busy.
[0056] Further, the gsmSCF 225 sends an apply charging message specifying the
period of time for which a terminating call can progress before an apply charging report
is sent by the gsmSSF 220 to the gsmSCF 225 and same is indicated by step 205-4. The
apply charging message may include fields such as a flag,
ReleaselfCallDurationExceeded. The flag indicates the G-MSC 130 to release or
disconnect the call once the duration, as specified in the apply charging is reached.
Typically, during a single call, muhiple apply charging message may be sent after
predetermined time slices to check if the second communication device 110-2 has
sufficient balance to receive or continue the call.
[0057] If it is determined that the second communication device 110-2 is allowed
to receive the call, the G-MSC 130 forwards the call to the V-MSC 120-2 as indicated by
the step 205-5. In one implementation, the communication between the V-MSC 120-2
and the second communication device 110-2 may be supported by layer 3 of the GSM
network 210. The layer 3, amongst other things, functions to transfer call control and
mobility management messages between an MSC and a communication device. The layer
3 includes three sub layers, viz.. Radio Resource Management (RR), Mobility
Management (MM), and connection Management (CM). The CM sub layer in turn
includes call control (CC), short message support (SMS), and supplementary service
support.
[0058] In one implementation when the V-MSC 120-2 establishes a call with the
second communication device 110-2 a call establishment procedure is followed. The
messages in the call establishment procedure are transmitted with a CC header. The CC
19
header may include a protocol discriminator, transaction ID, message type, and common
information elements (CIE). The protocol discriminator identifies the level 3 protocol to
which the standard layer 3 message belongs; the transaction identifier distinguishes
multiple parallel transactions within one communication device; the message type
uniquely defines the function and format of each GSM layer 3 message, for example, a
CC connect message; and Common Information Elements (CIE) includes various
information elements of fixed or variable length.
[0059] In one implementation, to establish the call, the V-MSC 120-2 sends a CC
set up message to the second communication device 110-2 as indicated by step 205-6.
The second communication device 110-2 may acknowledge the receipt of the CC set up
message by sending a CC call confirmed message to the V-MSC 120-2 as indicated by
step 205-7. Generally, signaling between the second communication device 110-2 and the
V-MSC 120-2 is over Direct Transfer Access Protocol (DTAP). Further, the
communication between the V-MSC 120-2 and the G-MSC 130 may be over ISDN User
Part (ISUP) signals. Typically, upon receiving the CC call confirmed message from the
second communication device 110-2, the V-MSC 120-2 sends an ISUP address complete
message (ACM) to the G-MSC 130 as indicated by step 205-8, which indicates that the
second communication device 110-2 is reached.
[0060] Further, when the second communication device 110-2 is alerted, in other
words when the second communication device 110-2 of the called party is ringing or
vibrating, as indicated by step 205-9, the second communication device 110-2 sends a CC
alerting message to the V-MSC 120-2, which is indicated by step 205-10. The CC
alerting message notifies the V-MSC 120-2 that the second communication device 110-2
is being alerted. Additionally, upon being alerted, the second communication device 110-
2 may answer the call and the same is represented by the step 205-11. In case the call is
answered, the second communication device 110-2 sends a CC connect message to the VMSC
120-2 as indicated by the step 205-12.
[0061] In one implementation, the CC connect message may include the
identification parameter. The second communication device 110-2 may include
processor(s) and a memory coupled to the processor. The memory may include contacts
data 230 and a caller identification module 235. The contacts data 230 includes caller
20
identification of users known to the second communication device 110-2. In one
example, the contacts data 230 is a phonebook of the second communication device 110-
2. The caller identification module 235 is configured to determine whether the caller
identification of the first communication device 110-1 is stored in the contacts data 230.
Based on the determination, the caller identification module 235 may assign a value to
identification parameter. The identification parameter may be included in the CIE of the
CC Connect message. For example, if the caller identification of the first communication
device 110-1 is not stored in the contacts data 230, the caller identification module 235
may set the value of the identification parameter as 11; else the value may be set as 01. It
will be understood that the example of the flag is only for purposes of explanation and
not as a limitation. Subsequent to the determination of the identification parameter, the
CC Connect message is transmitted based on usual logic.
[0062] Further, the V-MSC 120-2 may encode the identification parameter in an
ISUP answer message (ANM) and provide the ISUP ANM message to the gsmSSF 220,
as indicated by step 205-13. Further, the gsmSSF 220 may in turn provide the
identification parameter to the gsmSCF 225 in an event report BCSM message as
indicated by step 205-14. Further, the event report BCSM may indicate that the event,
which in the present case is that the second communication device 110-2 has answered
the call, has occurred. Further, based on requirements indicated by the gsmSCF 225 in
the apply charging message (refer step 205-4), the gsmSSF 220 provides the apply
charging report to the gsmSCF 225 as indicated by step 205-15. For example, if the apply
charging message indicated that the apply charging report is to be provided after 2
minutes from the establishment of the call, the gsmSSF 220 may accordingly provide the
report after 2 minutes. The apply charging report includes information, such as duration
of the call. Further, once the call is disconnected, the gsmSSF 220 indicates the same to
the gsmSCF 225 by way the event report BCSM, which is represented by step 205-16. In
turn, the gsmSCF 225 sends a release message instructing the gsmSSF 220 to release all
channels and end the call as indicated by step 205-17. Accordingly, through the ISUP
messages, the gsmSSF 220 may instruct the V-MSC 120-2 to release the terminating call
and the same is indicated by step 205-18.
21
[0063] In one embodiment, in order to compute charges for the call answered by
the second communication device 110-2, the gsmSCF 225 includes the call analysis
module 140. The call analysis module 140 may be configured to obtain the identification
parameter. In one example, the call analysis module 140 obtains the identification
parameter from the Event Report BCSM (Answer), as indicated at step 205-14. In
another example, the SCP 215 may be configured to obtain the identification parameter
based on the contacts data 230 available with the G-MSC 130. Based on the obtained
identification parameter, if the call analysis module 140 determines that the caller
identification of the first communication device 110-1 is present in the contacts data 230
of the second communication device 110-2, the call is charged based on the primary
charge schedule.
[0064] However, if the call analysis module 140 determines that the caller
identification of the first communication device 110-1 is not stored in the contacts data
230, the call analysis module 140 ascertains whether the call duration is greater than a
threshold call duration. In one example, the call analysis module 140 ascertains the same
based on the apply charging report. If it is determined that the call duration is greater than
the threshold call duration, the call analysis module 140 computes charges for the second
communication device 110-2 for the call based on the primary charge schedule. However,
if it is determined the call duration is less than the threshold call duration, the call may be
charged based on the secondary charge schedule.
[0065] In one implementation, the call analysis module 140 may also include a
counter to keep track of the number of times the first communication device 110-1 called
the second communication device 110-2. In said implementation, once a call from the
first communication device 110-1, which is an unknown caller party, has been received
more than a predetermined number of times in the predefined time-period, the call
analysis module 140 may charge the call based on the primary charge schedule, even
when the call duration is ascertained to be less than the threshold call duration. For
example, consider the predetermined number of times to be 5 in 24 hours, so in case the
second communication device 110-2 receives a call from an unknown caller sixth time
and the call duration of the call is less than the threshold call duration, then charges for
this sixth call are also computed based on the primary charge schedule.
22
[0066] Although the present subject matter has been explained in considerable
detail with respect to a terminating call in a roaming scenario, i.e., a roaming terminating
call, it will be understood that the principles disclosed herein may be extended for
originating calls in home network or visited network as well.
[0067] Figure 3 illustrates an exemplary method 300 for determining charges for
a call in a communication network, according to an embodiment of the present subject
matter. The order in which the method 300 is described is not intended to be construed as
a limitation, and any number of the described method blocks can be combined in any
order to implement the method 300, or an alternative method. Additionally, individual
blocks may be deleted from the method without departing from the spirit and scope of the
subject matter described herein. Furthermore, the methods can be implemented in any
suitable hardware, software, firmware, or combination thereof.
[0068] A person skilled in the art will readily recognize that steps of the method
can be performed by programmed computers. Herein, some embodiments are also
intended to cover program storage devices, for example, digital data storage media,
which are machine or computer readable and encode machine-executable or computerexecutable
programs of instructions, wherein said instructions perform some or all of the
steps of the described method. The program storage devices may be, for example, digital
memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard
drives, or optically readable digital data storage media. The embodiments are also
intended to cover both communication network and communication devices configured to
perform said steps of the exemplary method.
[0069] At block 305, a call is answered by one of a first communication device
and a second communication device. The call may be a terminating call or an originating
call. Further, the call may be a roaming call or a local call. The roaming call may be
understood to include terminating calls and originating calls in a roaming scenario. The
local calls may be understood to include terminating calls and originating calls in a home
network. In one implementation, the first communication device is the first
communication device 110-1 and the second communication device is the second
communication device 110-2.
23
[0070] At block 310, an identification parameter indicative of presence of caller
identification of the first communication device in contacts data of the second
communication device is obtained. The caller identification may be understood as any
detail which facilitates identification of a user, for example, the caller identification is the
contact number of the first communication device. In one implementation, the network
entity 105 obtains the identification parameter. For example, the second communication
device 110-2 provides the identification parameter to the network entity 105. In case of
GSM networks, the identification parameter may be provided in a CC Connect message.
In another example, the network entity 105 may obtain such information from the GMSC
130.
[0071] At block 315 it is determined if the caller identificafion associated with the
first communication device is unavailable in the contacts data of the second
communication device, based on the identification parameter. In one implementation, the
network entity 105 determines the presence of the caller identification of the first
communication device in the contacts data of the second communication device. If it is
determined that the caller identification is stored in the contacts data, block 315 branches
to block 320.
[0072] At block 320, charges for the call for the second communication device
are computed based on a primary charge schedule. The primary charge schedule is
indicative of the usual or default charges that are to be applied for the call. Thus, the call
is charged as per the usual tariff charges, which are inclusive of any other special tariff
plans selected by a user.
10073] Referring back to block 315, if it is determined that the caller
identification is not stored in the contacts data, block 315 branches to block 325. At block
325, it is ascertained if a duration of the call is greater than a threshold call duration. In
case it is determined that the duration of the call is greater than the threshold call
duration, block 325 branches to block 320, where the call charges are computed based on
the primary charge schedule. However, if it is determined that the duration of the call is
not greater than the threshold call duration, block 325 branches to block 330.
[0074] It will be understood that the actions of determining whether the caller
identification of the first communication device is unavailable in the contacts data and
24
ascertaining if the duration of the call is greater than a threshold call duration may be
performed simultaneously or one may be performed one after other.
[0075] At block 330, charges for the call are computed based on the secondary
charge schedule. Thus, the second communication device is charged based on the
secondary charge schedule. The secondary charge schedule includes discounted rates or
charges for calls, such as originating calls and terminating calls. The discounted rate may
include 100% discount, 75 % discount and so on. Accordingly, the call is charged at a
rate lower than the usual rates.
[0076] Since, call charges for the second communication device are computed
based on a determination if the first communication device is associated with an
unsolicited user or not, therefore a user associated with the second communication device
is not unnecessarily charged for unsolicited calls. Thus, such users may not be reluctant
in taking calls from or making calls to unknown callers, thereby not missing on important
calls, which in turn may also result in increased revenue for an operator.
[0077] Although implementations for determining charges for a call in a
communication network have been described in language specific to structural features
and/or methods, it is to be understood that the appended claims are not necessarily
limited to the specific features or methods described. Rather, the specific features and
methods are disclosed as exemplary implementations for determining charges for the call.
I/We Claim:
1. A method comprising:
identifying whether a call is answered by one of a first communication
device (110-1) and a second communication device (110-2);
determining, based on the identifying, whether a caller identification
associated with the first communication device (110-1) is unavailable in contacts
data of the second communication device (110-2);
ascertaining whether a duration of the call is greater than a threshold call
duration; and
computing, based in part on the determining and the ascertaining, charges
for the call, wherein the charges are computed for the second communication
device (110-2).
2. The method as claimed in claim 1, wherein the determining further comprises
obtaining an identification parameter indicative of availability of the caller
identification of the first communication device (110-1) in the contacts data of the
second communication device (110-2).
3. The method as claimed in claim 2, wherein the obtaining further comprises
receiving the identification parameter generated by the second communication
device (110-2).
4. The method as claimed in claim 1, wherein the call is a roaming terminating call.
5. The method as claimed in claim 1, wherein the charges are computed based on a
secondary charge schedule, wherein the secondary charge schedule includes
discounted rates for calls.
6. The method as claimed in claim 1, wherein the ascertaining further comprises
determining whether the call is answered greater than a predetermined number of
times in a predefined time-period.
7. A device (105) comprising:
a processor; and
26
a memory coupled to the processor, the memory comprising a call analysis
module (140) configured to:
identify whether a call is answered by one of a first communication
device (110-1) and a second communication device (110-2);
determine, based on the identification, whether a caller identification
of the first communicafion device (110-1) is unavailable in contacts data of
the second communication device (110-2);
ascertain whether a duration of the call is greater than a threshold call
duration; and
compute charges for the call, based in part on the determination and
the ascertainment, wherein the charges are computed for the second
communication device (110-2).
8. The device (105) as claimed in claim 7, wherein the call analysis module (140) is
configured to determine charges based on a secondary charge schedule.
9. The device (105) as claimed in claim 7, wherein the call analysis module (140) is
configured to receive an identification parameter generated by the second
communication device (110-2).
10. The device (105) as claimed in claim 7, wherein the call analysis module (140) is
further configured to:
ascertain whether the call is answered greater than a predetermined number of
times in a predefined time-period; and
compute the charges for the call according to a secondary charge schedule,
based on the ascertainment.
11. The device (105) as claimed in claim 7, wherein the call analysis module (140) is
associated with a communication network selected from at least one of a Global
System for Mobile Communication (GSM) network, a Universal Mobile
Telecommunications System (UMTS) network, a Personal Communications
Service (PCS) network, a Time Division Multiple Access (TDMA) network, a Code
27
Division Multiple Access (CDMA) network, a Next Generation Network (NGN), a
Public Switched Telephone Network (PSTN), and an Integrated Services Digital
Network (ISDN).
12. The device (105) as claimed in claim 7, wherein the device (105) includes a service
control point (215).
13. A communication device (110-2) comprising:
a processor; and
a memory coupled to the processor, the memory comprising a caller
identification module (235) configured to:
determine whether a caller identification of a first communication
device (110-1) is available in contacts data (230) of the communication
device (110-2); and
provide an identification parameter indicative of availability of the
caller identification in the contacts data (230).
14. The communication device (110-2) as claimed in claim 13, wherein the contacts
data (230) includes a phonebook of the communication device (110-2).
15. The communication device (110-2) as claimed in claim 13, wherein the caller
identification module (235) is configured to provide the identification parameter in
a call control (CC) connect message.
16. A computer-readable medium having embodied thereon a computer program for
executing a method comprising:
identifying if a call is answered by one of a first communication device
(110-1) and a second communication device (110-2);
determining, based on the identifying, whether a caller identification of the
first communication device (110-1) is unavailable in contacts data of the second
communication device (110-2);
ascertaining whether a duration of a call is greater than a threshold call
duration; and
28
computing charges for the call based on a secondary charge schedule, if the
duration of the call is less than the threshold call duration and the caller
identification of the first communication device (110-1) is unavailable in the
contacts data of the second communication device (110-2), wherein the charges
are computed for the second communication device (110-2).
17. The computer readable medium as claimed in claim 16, further comprising
computing charges for the call based on a primary charge schedule, if the duration
of the call is greater than the threshold call duration.
18. The computer readable medium as claimed in claim 16, wherein the determining
further comprises:
receiving an identification parameter indicative of availability of the caller
identification of the first communication device (110-1) in the contacts data of the
second communication device (110-2).
19. A computer-readable medium having embodied thereon a computer program for
executing a method comprising:
determining whether a caller identification of a first communication device
(110-1) is available in contacts data (230) of a second communication device
(110-2); and
providing an identification parameter indicative of availability of the caller
identification in the contacts data (230).
20. The computer readable medium as claimed in claim 19, wherein the identification
parameter is provided in a call control (CC) connect message.
| # | Name | Date |
|---|---|---|
| 1 | 522-del-2011-GPA-(15-04-2011).pdf | 2011-04-15 |
| 2 | 522-del-2011-Correspondence-Others-(15-04-2011).pdf | 2011-04-15 |
| 3 | Abstract.jpg | 2011-10-03 |
| 4 | 522-del-2011-Form-3.pdf | 2011-10-03 |
| 5 | 522-del-2011-Form-2.pdf | 2011-10-03 |
| 6 | 522-del-2011-Form-1.pdf | 2011-10-03 |
| 7 | 522-del-2011-Drawings.pdf | 2011-10-03 |
| 8 | 522-del-2011-Description (Complete).pdf | 2011-10-03 |
| 9 | 522-del-2011-Correspondence-others.pdf | 2011-10-03 |
| 10 | 522-del-2011-Claims.pdf | 2011-10-03 |
| 11 | 522-del-2011-Abstract.pdf | 2011-10-03 |
| 12 | 522-del-2011-Petition-137-(21-11-2011).pdf | 2011-11-21 |
| 13 | 522-del-2011-Form-3-(21-11-2011).pdf | 2011-11-21 |
| 14 | 522-del-2011-Form-1-(21-11-2011).pdf | 2011-11-21 |
| 15 | 522-del-2011-Correspondence-Others-(21-11-2011).pdf | 2011-11-21 |
| 16 | 522-del-2011-Correspondence-Others-(22-01-2014).pdf | 2014-01-22 |
| 17 | 522-del-2011-Correspondence Others-(07-04-2015).pdf | 2015-04-07 |
| 18 | 522-DEL-2011-FER.pdf | 2018-07-10 |
| 19 | 522-DEL-2011-AbandonedLetter.pdf | 2019-10-12 |
| 1 | search_14-06-2018.pdf |