FORM 2
THE PATENTS ACT, 1970 (39 OF
1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR RENDERING TARGETED INFORMATION AS RING BACK TONE TO CALLING PARTY”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR RENDERING TARGETED INFORMATION AS RING BACK TONE TO CALLING PARTY
TECHNICAL FIELD
5
[0001] Embodiments of the present disclosure generally relate to communication systems. More particularly, embodiments of the present disclosure relate to rendering a targeted information as a ring back tone (RBT) to a calling party.
10 BACKGROUND
[0002] The following description of the related art is intended to provide background
information pertaining to the field of the disclosure. This section may include certain aspects
of the art that may be related to various features of the present disclosure. However, it should
15 be appreciated that this section is used only to enhance the understanding of the reader with
respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first
20 generation of wireless communication technology was based on analog technology and offered
only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. Third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology
25 revolutionized wireless communication with faster data speeds, better network coverage, and
improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
30
[0004] In telecommunication, a called party is a user device end to which a call (such as a voice call) is initiated, and a calling party is a user device end from where the call is initiated for the called party. Also, a Ring Back Tone (RBT) is generally a called-party supplementary service, where the calling party is intimated with a tone when ringing in response to the initiated call
2

starts at called-party. Sometimes, users (called parties) pay a premium to the operator to keep
popular songs as RBT, but most of the called parties do not opt for this premium service and
when these users (i.e., the called parties) are called over the telecommunication network, a
default tone is rendered to the calling party. There is a ringing duration for which the calling
5 users, that is the users who make a call to another user, hear a calling tone (i.e., the ring back
tone). When a call is made by a calling party to users who have not opted for premium RBT service, the default ring back tone is rendered until the call is answered or rejected, and therefore the waiting time remains unutilized and unproductive for the calling party as well as the telecom operator. 10
[0005] However, till date, no solution has been proposed to address this huge untapped area wherein the waiting time during rendering of default ring back tone can be efficiently utilized and the user experience as well as revenue of the telecom operator can be enhanced.
15 [0006] Thus, there exists an imperative need in the art to provide a solution for rendering a
targeted information as a ring back tone (RBT) to a calling party for enhancing the ring back tone experience of a user and at the same time facilitating generation of revenue of telecom operators, which the present disclosure aims to address.
20 OBJECTS OF THE INVENTION
[0007] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
25 [0008] It is an object of the present disclosure to provide a system and a method for enriching
the user experience of a calling party when a call is made to another user.
[0009] It is another object of the present disclosure to provide a solution that enables generation of revenues for a telecom operator from one or more advertisement platforms. 30
[0010] It is another object of the present disclosure to provide a solution that conveys relevant information, such as offers, advertisements, etc., to the calling party while rendering of a default tone.
3

[0011] It is another object of the present disclosure to provide a solution that enhances awareness to the larger audience by conveying information, which may be in the public domain but largely remains unnoticed.
5 [0012] It is another object of the present disclosure to provide a solution that provides a new
advertisement platform to entities such as banks, e-commerce websites etc.
[0013] It is yet another object of the present disclosure to provide a solution for utilizing the
end user time of users during non-premium ring back tone by entertaining and offering the
10 content for their awareness based on their online behavior.
SUMMARY OF THE DISCLOSURE
[0014] This section is provided to introduce certain aspects of the present disclosure in a
15 simplified form that are further described below in the detailed description. This summary is
not intended to identify the key features or the scope of the claimed subject matter.
[0015] An aspect of the present disclosure may relate to a method for rendering a targeted information as a ring back tone (RBT) to a calling party. The method comprises determining,
20 by a determination unit of a converged telephony application server (CTAS), a role of a node,
wherein the role of the node is determined as one of a termination role, and an origination role. Further, the method comprises performing, by an analysis unit of the CTAS, a termination service procedure, wherein the termination service procedure is performed in an event the role of the node is determined as the termination role. Further, the method comprises rendering, by
25 a rendering unit of the CTAS, the targeted information as the RBT to the calling party based
on the performing of the termination service procedure.
[0016] In an exemplary aspect of the present disclosure, prior to the determining, by the
determination unit of the CTAS, the role of the node, the method comprises: receiving, by a
30 transceiver unit of the CTAS, a session initiation protocol (SIP) invite, wherein the SIP invite
is received upon initiation of a call session from the calling party to a called party.
[0017] In an exemplary aspect of the present disclosure, the termination service procedure comprises: determining, by the determination unit of the CTAS, a first level RBT preference
4

of the called party, wherein the first level RBT preference of the called party is one of a non-
premium first level RBT preference, and an other first level RBT preference. Further, the
termination service procedure comprises performing, by the analysis unit of the CTAS, one of
a non-premium subscription procedure and a premium subscription procedure, wherein the
5 non-premium subscription procedure is performed in an event the first level RBT preference
of the called party is determined as the non-premium first level RBT preference, and the premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the other first level RBT preference.
10 [0018] In an exemplary aspect of the present disclosure, the premium subscription procedure
comprises determining, by the determination unit of the CTAS, a second level RBT preference of the called party in an event the first level RBT preference of the called party is determined as the other first level RBT preference, wherein the second level RBT preference of the called party is one of a premium second level RBT preference, and an opt-out second level RBT
15 preference. Further, the premium subscription procedure comprises rendering, by the rendering
unit of the CTAS, one of a default tone as the RBT of the called party, and a set of preferred songs as the RBT of the called party, wherein the set of preferred songs is rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the premium second level RBT preference, and the default tone is rendered as the RBT of
20 the called party in an event the second level RBT preference of the called party is determined
as the opt-out second level RBT preference.
[0019] In an exemplary aspect of the present disclosure, the non-premium subscription procedure comprises extracting, by the analysis unit of the CTAS, a contact information of a
25 calling party from a P-Asserted-Identity header. Further, the non-premium subscription
procedure comprises registering, by the analysis unit of the CTAS, the calling party as a potential target in a local database associated with the CTAS. Further, the non-premium subscription procedure comprises forwarding, by the transceiver unit of the CTAS, a SIP invite request to the called party.
30
[0020] In an exemplary aspect of the present disclosure, prior to the rendering, by the rendering unit, the targeted information as the ring back tone (RBT) to the called party, the method further comprises: determining, by the determination unit, one of a presence and an absence of an alert-info header with a call-waiting indication, wherein the call-waiting indication indicates that the
5

called party is engaged in an already established session. Further, in this exemplary aspect, the
method comprises rendering, by the rendering unit, a call waiting notification to the calling
party in an event the alert-info header with the call-waiting indication is determined as present.
Further, in this exemplary aspect, the method comprises determining, by the determination unit
5 with an advertisement server, one of a positive availability and a negative availability of a target
advertisement for rendering to the calling party using one or more machine-learning based
models, in an event the alert-info header with the call-waiting indication is determined as
absent, wherein the positive availability is determined in an event the target advertisement for
rendering to the calling party is available, and the negative availability is determined in an
10 event the target advertisement for rendering to the calling party is not available. Further, in this
exemplary aspect, the method comprises receiving, by the transceiver unit from the advertisement server, a data related to the target advertisement for rendering to the calling party in an event the positive availability is determined.
[0021] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit from the advertisement server, a no-data indication in an event the negative availability is determined, wherein the no-data indication comprises an information related to a non-availability of the target advertisement for rendering to the calling party.
[0022] In an exemplary aspect of the present disclosure, the data comprises at least one of a graphical data file, and a source information of the graphical data file.
[0023] In an exemplary aspect of the present disclosure, after the rendering, by the rendering
25 unit, the targeted information as the ring back tone (RBT) to the called party, the method
comprises sending, by the transceiver unit to the advertisement server, a notification of completion.
[0024] Another aspect of the present disclosure may relate to a system for rendering a targeted
30 information as a ring back tone (RBT) to a calling party. The system comprises a converged
telephony application server (CTAS). The CTAS further comprises a determination unit configured to determine a role of a node, wherein the role of the node is determined as one of a termination role, and an origination role. Further, the CTAS comprises an analysis unit configured to perform a termination service procedure, wherein the termination service
6

procedure is performed in an event the role of the node is determined as the termination role. Further, the CTAS comprises a rendering unit configured to render the targeted information as the RBT to the calling party based on the performing of the termination service procedure.
5 [0025] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for rendering a targeted information as a ring back tone (RBT) to a calling party, the instructions include executable code which, when executed by one or more units of a system, causes: a determination unit of a converged telephony application server (CTAS) of the system to determine a role of a node, wherein the
10 role of the node is determined as one of a termination role, and an origination role. The
instructions further include executable code which, when executed by one or more units of a system, causes an analysis unit of the CTAS to perform a termination service procedure, wherein the termination service procedure is performed in an event the role of the node is determined as the termination role. The instructions further include executable code which,
15 when executed by one or more units of a system, causes a rendering unit of the CTAS to render
the targeted information as the ring back tone (RBT) to the calling party based on the performing of the termination service procedure.
[0026] Yet another aspect of the present disclosure may relate to a user equipment (UE). The
20 UE comprises a transceiver unit configured to receive a targeted information as a ring back
tone (RBT). The RBT is rendered at the UE by a system based on: determining, by a
determination unit of a CTAS, a role of a node, wherein the role of the node is determined as
one of a termination role, and an origination role; performing, by an analysis unit of the CTAS,
a termination service procedure, wherein the termination service procedure is performed in an
25 event the role of the node is determined as the termination role; and rendering, by a rendering
unit of the CTAS, the targeted information as the ring back tone (RBT) to the UE based on the performing of the termination service procedure, wherein the UE is a calling party.
DESCRIPTION OF THE DRAWINGS
30
[0027] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon
7

clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the
figures are not to be construed as limiting the disclosure, but the possible variants of the method
and system according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings
5 includes disclosure of electrical components or circuitry commonly used to implement such
components.
[0028] Fig. 1 illustrates an exemplary block diagram representation of a system connected to
a wireless communication network for rendering a targeted information as a ring back tone
10 (RBT) to a calling party, in accordance with exemplary implementations of the present
disclosure.
[0029] Fig. 2 illustrates an exemplary block diagram of a computing device upon which the
features of the present disclosure may be implemented in accordance with exemplary
15 implementation of the present disclosure.
[0030] Fig. 3 illustrates an exemplary block diagram of a system for rendering a targeted information as a ring back tone (RBT) to a calling party, in accordance with exemplary implementations of the present disclosure. 20
[0031] Fig. 4 illustrates a method flow diagram for rendering a targeted information as a ring back tone (RBT) to a calling party, in accordance with exemplary implementations of the present disclosure.
25 [0032] Fig. 5 illustrates an exemplary flow chart indicating an exemplary scenario for
rendering a targeted information as a ring back tone (RBT) to a calling party, in accordance with exemplary implementations of the present disclosure.
[0033] The foregoing shall be more apparent from the following more detailed description of
30 the disclosure.
DETAILED DESCRIPTION
8

[0034] In the following description, for the purposes of explanation, various specific details
are set forth in order to provide a thorough understanding of embodiments of the present
disclosure. It will be apparent, however, that embodiments of the present disclosure may be
practiced without these specific details. Several features described hereafter may each be used
5 independently of one another or with any combination of other features. An individual feature
may not address any of the problems discussed above or might address only some of the problems discussed above.
[0035] The ensuing description provides exemplary embodiments only, and is not intended to
10 limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description
of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth. 15
[0036] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of ordinary skill in
the art that the embodiments may be practiced without these specific details. For example,
circuits, systems, processes, and other components may be shown as components in block
20 diagram form in order not to obscure the embodiments in unnecessary detail.
[0037] Also, it is noted that individual embodiments may be described as a process which is
depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block
diagram. Although a flowchart may describe the operations as a sequential process, many of
25 the operations may be performed in parallel or concurrently. In addition, the order of the
operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0038] Further, in accordance with the present disclosure, it is to be acknowledged that the
30 functionality described for the various components/units can be implemented interchangeably.
While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative
9

arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0039] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an
5 example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed
herein is not limited by such examples. In addition, any aspect or design described herein as
“exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or
advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary
structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent
10 that the terms “includes,” “has,” “contains,” and other similar words are used in either the
detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
15 [0040] As used herein, a “processing unit” or “processor” or “operating processor” includes
one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a
20 microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array
circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
25
[0041] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing
30 the features of the present disclosure. The user equipment/device may include, but is not limited
to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least
10

one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
[0042] As used herein, “storage unit” or “memory unit” refers to a machine or computer-
5 readable medium including any mechanism for storing information in a form readable by a
computer or similar machine. For example, a computer-readable medium includes read-only
memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical
storage media, flash memory devices or other types of machine-accessible storage media. The
storage unit stores at least the data that may be required by one or more units of the system to
10 perform their respective functions.
[0043] As used herein “interface” or “user interface refers to a shared boundary across which
two or more separate components of a system exchange information or data. The interface may
also be referred to a set of rules or protocols that define communication or interaction of one
15 or more modules or one or more units with each other, which also includes the methods,
functions, or procedures that may be called.
[0044] All modules, units, components used herein, unless explicitly excluded herein, may be
software modules or hardware processors, the processors being a general-purpose processor, a
20 special purpose processor, a conventional processor, a digital signal processor (DSP), a
plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
25 [0045] As used herein the transceiver unit include at least one receiver and at least one
transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
30 [0046] As used herein the term “ring back tone” or “RBT” or “ringing tone” refers to an audible
indication heard by a calling party while waiting for a call (made by the calling party to a called party) to be answered by the called party.
11

[0047] As used herein, TAS refers to Telephony Application Server, i.e., a component used in the core network of a telecom network operator that provides telephony applications and additional multimedia functions.
5 [0048] As used herein, CTAS refers to Converged Telephony Application Server that is
capable of handling Voice over Long Term Evolution (VoLTE), fixed and enterprise subscribers simultaneously. Also, in the present solution the CTAS renders a targeted information as a ring back tone (RBT) to a calling party in accordance with the features as disclosed in the present solution.
10
[0049] As used herein, ‘Session Initiation Protocol’ or ‘SIP’ is a communication protocol used to establish, modify, and terminate multimedia sessions such as voice and video calls over IP networks. It facilitates the initiation of data exchange sessions between users, handling tasks such as, but not limited to, call setup, signalling, and teardown of connections. Also, SIP invite
15 refers to a SIP request message that initiates a SIP call. The SIP request message is a type of
message used in SIP-based communication systems to initiate, modify, or terminate communication sessions. A SIP call refers to a communication session initiated and managed using the SIP.
20 [0050] As used herein, Advertisement server refers to a server that determines whether any
relevant advertisement can be rendered to the calling party and that sends an advertisement clip to the CTAS as per the online behaviour of the calling party.
[0051] As discussed in the background section, the current known solutions have several
25 shortcomings. The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing method and system of rendering a
targeted information as a ring back tone (RBT) to a calling party. This is done by rendering
targeted information in the form of advertisements, offers etc., based on calling the party’s
online behaviour, or the called party’s choice. Based on the implementation of features of the
30 present disclosure the called party may subscribe to a plan among various plans offered by a
network operator, according to which the calling party may receive a ring back tone (RBT) of the choice of the called party, or the calling party may receive a default RBT as set by the network operator, or the calling party may receive a RBT as per the network operator’s choice, such as targeted or non-targeted advertisements for the calling party, etc.
12

[0052] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
5 [0053] Figure1 illustrates an exemplary block diagram representing interconnection between
a system [102] (also may be referred hereinafter as system [300]) and a network entity [101],
in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1,
the system [102] comprises a Converged Telephony Application Server (CTAS) [102a] (also
may be referred hereinafter as CTAS [301]) and the system [102] is connected with the network
10 entity [101]. The system [102] is implemented for rendering a targeted information as a ring
back tone (RBT) to a calling party. Further, detailed functionality of the system [102] is explained in reference to the system [300] in the description of Figure 3 as provided below.
[0054] Figure 2 illustrates an exemplary block diagram of a computing device [200] (or
15 referred to herein as a computer system [200]) upon which the features of the present disclosure
may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may be in communication with a communication network (such as a 5th generation network) and may also implement a method for rendering a targeted information as a ring back tone (RBT) to a calling party utilising the
20 system [300]. In another implementation, the computing device [200] in communication with
the communication network, itself implements the method for rendering a targeted information as a ring back tone (RBT) to a calling party using one or more units configured within the computing device [200], wherein a person skilled in the art would appreciate that, said one or more units are capable of implementing the features as disclosed in the present disclosure.
25
[0055] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory
30 [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to
the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204],
13

render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204]. 5
[0056] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED
10 (OLED) display, etc. for displaying information to a computer user. An input device [214],
including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to
15 the processor [204], and for controlling cursor movement on the display [212]. This input
device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0057] The computing device [200] may implement the techniques described herein using
20 customized hard-wired logic, one or more ASICs or FPGAs, firmware, and/or program logic
which in combination with the computing device [200] causes or programs the computing
device [200] to be a special-purpose machine. According to one implementation, the techniques
herein are performed by the computing device [200] in response to the processor [204]
executing one or more sequences of one or more instructions contained in the main memory
25 [206]. Such instructions may be read into the main memory [206] from another storage
medium, such as the storage device [210]. Execution of the sequences of instructions contained
in the main memory [206] causes the processor [204] to perform the process steps described
herein. In alternative implementations of the present disclosure, hard-wired circuitry may be
used in place of or in combination with software instructions.
30
[0058] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card,
14

cable modem, satellite modem, or a modem to provide a data communication connection to a
corresponding type of telephone line. As another example, the communication interface [218]
may be a local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such implementation, the
5 communication interface [218] sends and receives electrical, electromagnetic, or optical signals
that carry digital data streams representing various types of information.
[0059] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218].
10 In the Internet example, a server [230] might transmit a requested code for an application
program through the Internet [228], the ISP [226], the local network [222], the host [224], and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
15
[0060] Referring to Figure 3, an exemplary block diagram of a system [300] for rendering a targeted information as a ring back tone (RBT) to a calling party, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one converged telephony application server (CTAS) [301], and at least one local database
20 [310]. The system [300] may be further connected to at least one advertisement server [312].
The CTAS [301] comprises at least one transceiver unit [302], at least one determination unit [304], at least one analysis unit [306], and at least one rendering unit [308]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. Also, in Fig. 3 only a few units are shown, however, the system
25 [300] may comprise multiple such units or the system [300] may comprise any such numbers
of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may reside in a server or a network entity.
[0061] The system [300] is configured for rendering the targeted information as the ring back
30 tone (RBT) to the calling party, with the help of the interconnection between the
components/units of the system [300].
[0062] More specifically, the system [300] comprises the converged telephony application server (CTAS) [301]. The CTAS [301] further comprises a determination unit [304]. The
15

determination unit [304] may be configured to determine a role of a node, wherein the role of
the node is determined as one of a termination role, and an origination role. Hereinafter, a
calling party may be construed as a user device end where a party or a user makes / initiates a
call to a called party. The called party may be construed as a user device end where a party or
5 a user receives the call made by the calling party. Thus, in an example, say a first user makes
a call to a second user, then the first user may be referred as the calling party and the second user may be referred as the called party. Further, the node may be a network element, for example a base station server or any other server that implements a relevant function using which a calling party makes a call to the called party or the called party receives a call from a
10 calling party. If the node is connected to the calling party, the role of the node may be
determined as an originating role, and if the node is connected to the called party, the role of the node may be determined as a terminating role. For example, a first user, i.e., the calling party makes a call to a second user, i.e., the called party. For this purpose, the first user may be connected to the base station in the area where the first user is located. Further, when the user
15 makes the call, the call may be received by a base station of the area where the second user is
located. Thus, the base station where the first user is located may be the originating node, and the base station where the second user is located may be the terminating node. A person skilled in the art would appreciate that the above example is for understanding purposes only and does not limit or restrict the present disclosure in any possible manner. Also, in an implementation,
20 the CTAS [301] further comprises the transceiver unit [302]. Also, in an implementation, prior
to the determination unit [304] of the CTAS [301] determines the role of the node, the transceiver unit [302] may receive a session initiation protocol (SIP) invite. The SIP invite is received upon initiation of a call session from the calling party to the called party.
25 [0063] Further, the CTAS [301] comprises the analysis unit [306] and the rendering unit [308].
The analysis unit [306] is configured to perform a termination service procedure in an event the role of the node is determined as the termination role. Also, in case the determination unit [304] of the CTAS [301] determines the role of the node as the originating role, then some procedures related to originating services may be implemented. In an implementation, for the
30 performing of the termination service procedure, the determination unit [304] is configured to
determine a first level RBT preference of the called party, that is, a preference of the called party as to whether the called party desires the calling party to listen to a specific RBT when the calling party calls the called party, or the called party does not care for what the calling party listens to when the calling party calls the called party. The first level RBT preference of
16

the called party is one of a non-premium first level RBT preference, and an other first level
RBT preference. For example, the called party wants a user (or the calling party, that is, the
user that is calling the called party) to listen to a ring back tone of the called party’s choice,
then the called party may opt for another first level RBT preference which is other than the
5 non-premium first level RBT preference. Further in this example, if the called party wants the
user to listen to any RBT which may not be of the called party’s choice and does not care what the calling party is listening to when the calling party calls the called party, then the called party may opt for the non-premium first level RBT preference. Further, in this implementation, further for the performing of the termination service procedure, the analysis unit [306] is
10 configured to perform one of a non-premium subscription procedure and a premium
subscription procedure, wherein the non-premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the non-premium first level RBT preference, and the premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the other first level RBT
15 preference. Here, continuing with the above example, the non-premium subscription procedure
is performed when the called party does not care what the calling party is listening to when the calling party calls the called party and opts for a non-premium first level RBT preference, and the premium subscription procedure is performed when the called party has opted for a premium first level RBT preference, say for example, by paying the network operator an
20 amount for subscribing to the premium first level RBT preference.
[0064] In an implementation, for performance of the non-premium subscription procedure the analysis unit [306] is configured to extract a contact information of a calling party from a P-Asserted-Identity (PAI) header. Here, the PAI header is a header field used in the SIP (Session
25 Initiation Protocol) protocol within telecommunication networks to carry the identity of the
user (i.e., the calling party) sending the SIP message. When a SIP request travels through a network, intermediate entities, such as SIP proxies, may need to assert the identity of the user to subsequent network entities. Further, in this implementation, analysis unit [306] is configured to register the calling party as a potential target in a local database [310] associated
30 with the CTAS [301]. For example, a user (i.e., the calling party) has some interests in specific
articles and the information is present with respect to the user that this user has a particular interest, for example, in football. Then that user may be identified as a potential target in the local database [310]. Further, in this implementation, the transceiver unit [302] is configured to forward a SIP invite request to the called party. Once the ringing starts at the called party
17

side, called party may relay a “180 Ringing” message to the network, that is a specific response in the Session Initiation Protocol (SIP) used to indicate that a server has received a call request and is alerting the user.
5 [0065] Further, say for example, a user is identified as a potential target, the user may be
rendered with a targeted information as an RBT. However, prior to rendering this RBT to this
potential target, in an implementation, the determination unit [304] is configured to determine
one of a presence and an absence of an alert-info header with a call-waiting indication, wherein
the call-waiting indication indicates that the called party is engaged in an already established
10 session. Here, the Alert-Info header is a field that specifies an alternative ring tone. A typical
usage of this field is for a proxy to insert this header field to provide a distinctive ringing
feature. Further, in this implementation, the rendering unit [308] is configured to render a call
waiting notification to the calling party in an event the alert-info header with the call-waiting
indication is determined as present, which may be rendered using a media resource function
15 (MRF) unit. That is, if the called party is on another call with some other user, the calling party
may not be presented with any other information but the call-waiting indication. Further, in
this implementation, the determination unit [304] is configured to determine with an
advertisement server [312], one of a positive availability and a negative availability of a target
advertisement for rendering to the calling party, in an event the alert-info header with the call-
20 waiting indication is determined as absent. For this purpose, in an implementation, the
determination unit [304] may use one or more machine-learning based models. That is,
determination unit [304] can query the advertisement server [312] via an HTTP interface about
a targeted advertisement campaign. The advertisement server [312], within fraction of seconds,
using the one or more machine-learning based models can determine whether any
25 advertisement is available that can be rendered, and which will be meaningful for the calling
party. Also, here the positive availability is determined in an event the target advertisement for
rendering to the calling party is available, and the negative availability is determined in an
event the target advertisement for rendering to the calling party is not available. For example,
a user (i.e., the calling party) is identified as a potential target, and the user has an interest in
30 football. Thus, the determination unit [304] checks whether there is any advertisement
available that is related to football. In case the advertisement related to football is available,
then positive availability is determined by the determination unit [304] and the same
advertisement may be used to present to the calling party when the calling party makes the call
to the called party, and if there is no advertisement related to football available, then negative
18

availability is determined by the determination unit [304]. In case positive availability is
determined by the determination unit [304], then the transceiver unit [302] is configured to
receive from the advertisement server [312], a data related to the target advertisement for
rendering to the calling party. Here, the data comprises at least one of a graphical data file, and
5 a source information of the graphical data file. Pertinently, here the graphical data may be
construed not limited to visual information or audio-visual information, but also be construed to include an audio data. For clarity, it is mentioned that in case of a video call being made by the calling party, the video data or audio-visual data may be presented to the calling party as the targeted information. However, in case of audio call being made by the calling party to the
10 called party, an audio data (for example, in *.3gp format, *.mp3 format, etc.) may be presented
to the calling party as the targeted information. In an exemplary implementation, the CTAS [301] can send advertisement file name to MRF unit for rendering the advertisement, which then intimates the CTAS [301] upon completion, and CTAS [301] in turn can send completion trigger to the advertisement server [312] to register a hit against the corresponding
15 advertisement campaign. Also, in case negative availability is determined by the determination
unit [304], then the transceiver unit [302] is configured to receive, from the advertisement server [312], a no-data indication. This no-data indication may comprise an information related to a non-availability of the target advertisement for rendering to the calling party. For this purpose, in an implementation, a Media Resource Function (MRF) may be requested to render
20 the audio clip.
[0066] After this, in an implementation, the rendering unit [308] may render this above targeted
information to the calling party based on the data received from the advertisement server [312].
In an implementation, where the rendering unit [308] renders this above targeted information
25 to the calling party based on the data received from the advertisement server [312], the
rendering unit [308] is configured to send, to the advertisement server [312], a notification of completion. Then, the advertisement server [312] can generate reports in real time along with number of hits and relevant data which can be reconciled with other platforms to claim revenue.
30 [0067] Also, in an exemplary implementation, the CTAS [301] supports both hypertext
transfer protocol – secured (HTTPS) and session initiation protocol (SIP) to query the advertisement server [312] for clip name. This is configurable based on preference of advertisement server [312]. When SIP protocol is used, the CTAS [301] uses SIP OPTIONS method (OPTIONS method is used to query a user agent or a proxy server about its capabilities
19

and discover its current availability as generally known in the art), and when HTTPS
(Hypertext Transfer Protocol Secure, which is a secure protocol that uses encryption for secure
communication over a computer network) is used, the CTAS [301] uses a GET request to
retrieve clip name. In an exemplary implementation, the CTAS [301] expects the advertisement
5 server [312] to provide the clip name within 200ms (which is configurable). Any latency of
more than the configurable time of, say, 200ms may lead to delayed call setup time. Further, if
due to any ambiguity in network, the advertisement server [312] fails to provide the clip name
within this configurable time of, say, 200ms, CTAS [301] may render default RBT tone. Also,
multiple destinations of the advertisement server [312] can be configured for the purpose of
10 redundancy and CTAS [301] may facilitate even distribution of load between these destinations
and if required, the CTAS [301] can check health status of each of these destinations.
[0068] Also, in an implementation, for performing the premium subscription procedure, the determination unit [304] is configured to determine a second level RBT preference of the called
15 party in an event the first level RBT preference of the called party is determined as the other
first level RBT preference, wherein the second level RBT preference of the called party is one of a premium second level RBT preference, and an opt-out second level RBT preference. Continuing with the above example, say a user, i.e., the called party wants another user, i.e., the calling party, to listen to a ring back tone of the called party’s choice, and has therefore
20 opted for an other first level RBT preference. Further, in the second level RBT preference, say
the called party selects the opt-out second level RBT preference. Then in that case, for the purposes of this example, the calling party may be provided with the regular calling tone, that is, the default tone provided by the network operator. Also, in the second level RBT preference, say the called party selects the premium second level RBT preference, then the calling party
25 may be provided with the RBT of the called party’s choice. Thus, in this implementation, the
rendering unit [308] is configured to render one of a default tone as the RBT of the called party, and a set of preferred songs as the RBT of the called party, wherein the set of preferred songs is rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the premium second level RBT preference, and the default tone
30 is rendered as the RBT of the called party in an event the second level RBT preference of the
called party is determined as the opt-out second level RBT preference. Also, in an implementation, the user preference may be notified to the CTAS [301] via a home subscriber server (HSS) using a Sh – Diameter message (Push Notification Request). Notably, Sh interface
20

is implemented as a provider to the base Diameter protocol support in a SIP Server and the Sh – Diameter message provides details such as a user preference to the CTAS [301].
[0069] Therefore, the rendering unit [308] is configured to render the targeted information as
5 the ring back tone (RBT) to the calling party based on the performing of the termination service
procedure. Here, this targeted information can be one of: (a) a RBT of the called party’s choice
in case the first level RBT preference of the called party is the other first level RBT preference
and the second level RBT preference of the called party is the premium second level RBT
preference; (b) a default RBT in case the first level RBT preference of the called party is the
10 other first level RBT preference and the second level RBT preference of the called party is the
opt-out second level RBT preference; (c) any other RBT that may not be of the called party’s choice, such as advertisement information received from the advertisement server [312] in case the first level RBT preference of the called party is the non-premium first level RBT preference.
15 [0070] Referring to Figure 4, an exemplary method flow diagram [400] for rendering a targeted
information as a ring back tone (RBT) to a calling party, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device or at a network end to implement the features of the present disclosure. Also,
20 as shown in Figure 4, the method [400] starts at step [402].
[0071] At step 404, the method comprises determining, by a determination unit [304] of a converged telephony application server (CTAS) [301], a role of a node, wherein the role of the node is determined as one of a termination role, and an origination role. As noted above, a
25 calling party may be construed as a user device end where a party or a user that makes a call to
a called party. The called party may be construed as a user device end where a party or a user receives the call made by the calling party. Further, the node may be a network element, for example a base station server or any other server that implements a relevant function using which a calling party makes a call to the called party or the called party receives a call from a
30 calling party. If the node is connected to the calling party, the role of the node may be
determined as an originating role, and if the node is connected to the called party, the role of the node may be determined as a terminating role. Also, in an implementation, prior to the determining, by the determination unit [304] of the CTAS [301], the role of the node, the method comprises receiving, by a transceiver unit [302] of the CTAS [301], a session initiation
21

protocol (SIP) invite, wherein the SIP invite is received upon initiation of a call session from the calling party to a called party. The SIP invite is received upon initiation of a call session from the calling party to the called party.
5 [0072] At step 406, the method comprises performing, by an analysis unit [306] of the CTAS
[301], a termination service procedure, wherein the termination service procedure is performed in an event the role of the node is determined as the termination role. In an implementation, for the performing of the termination service procedure, the determination unit [304] may determine a first level RBT preference of the called party. The first level RBT preference of
10 the called party is one of a non-premium first level RBT preference, and an other first level
RBT preference. For example, the called party wants a user (or the calling party, that is, the user that is calling the called party) to listen to a ring back tone of the called party’s choice, then the called party may opt for an other first level RBT preference which is other than the non-premium first level RBT preference. Further in this example, if the called party wants the
15 user to listen to any RBT which may not be of the called party’s choice and does not care what
the calling party is listening to when the calling party calls the called party, then the called party may opt for the non-premium first level RBT preference. Further, in this implementation, further for the performing of the termination service procedure, the analysis unit [306] may perform one of a non-premium subscription procedure and a premium subscription procedure,
20 wherein the non-premium subscription procedure is performed in an event the first level RBT
preference of the called party is determined as the non-premium first level RBT preference, and the premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the other first level RBT preference. Here, continuing with the above example, the non-premium subscription procedure is performed when the called
25 party does not care what the calling party is listening to when the calling party calls the called
party and opts for a non-premium first level RBT preference, and the premium subscription procedure is performed when the called party has opted for a premium first level RBT preference, say for example, by paying the network operator an amount for subscribing to the premium first level RBT preference.
30
[0073] In an implementation, for performance of the non-premium subscription procedure the analysis unit [306] may extract a contact information of a calling party from a P-Asserted-Identity (PAI) header. Here, the PAI header is a header field used in the SIP (Session Initiation Protocol) protocol within telecommunication networks to carry the identity of the user (i.e., the
22

calling party) sending the SIP message. When a SIP request travels through a network,
intermediate entities, such as SIP proxies, may need to assert the identity of the user to
subsequent network entities. Further, in this implementation, analysis unit [306] may register
the calling party as a potential target in a local database [310] associated with the CTAS [301].
5 For example, a user (i.e., the calling party) has some interests in specific articles and the
information is present with respect to the user that this user has a particular interest, for example, in football. Then that user may be identified as a potential target in the local database [310]. Further, in this implementation, the transceiver unit [302] may forward a SIP invite request to the called party. 10
[0074] Further, say for example, a user is identified as a potential target, the user may be
rendered with a targeted information as an RBT. However, prior to rendering this RBT to this
potential target, in an implementation, the determination unit [304] may determine one of a
presence and an absence of an alert-info header with a call-waiting indication, wherein the call-
15 waiting indication indicates that the called party is engaged in an already established session.
Further, in this implementation, the rendering unit [308] may render a call waiting notification
to the calling party in an event the alert-info header with the call-waiting indication is
determined as present, which may be rendered using a media resource function (MRF) unit.
That is, if the called party is on another call with some other user, the calling party may not be
20 presented with any other information but the call-waiting indication. Further, in this
implementation, the determination unit [304] may determine with an advertisement server
[312], one of a positive availability and a negative availability of a target advertisement for
rendering to the calling party, in an event the alert-info header with the call-waiting indication
is determined as absent. For this purpose, in an implementation, the determination unit [304]
25 may use one or more machine-learning based models. That is, determination unit [304] can
query the advertisement server [312] via an HTTP interface about a targeted advertisement
campaign. The advertisement server [312], within fraction of seconds, using the one or more
machine-learning based models can determine whether any advertisement is available that can
be rendered, and which will be meaningful for the calling party. Also, here the positive
30 availability is determined in an event the target advertisement for rendering to the calling party
is available, and the negative availability is determined in an event the target advertisement for
rendering to the calling party is not available. For example, a user (i.e., the calling party) is
identified as a potential target, and the user has an interest in football. Thus, the determination
unit [304] checks whether there is any advertisement available that is related to football. In
23

case the advertisement related to football is available, then positive availability is determined
by the determination unit [304] and the same advertisement may be used to present to the
calling party when the calling party makes the call to the called party, and if there is no
advertisement related to football available, then negative availability is determined by the
5 determination unit [304]. In case positive availability is determined by the determination unit
[304], then the transceiver unit [302] may receive from the advertisement server [312], a data
related to the target advertisement for rendering to the calling party. Here, the data comprises
at least one of a graphical data file, and a source information of the graphical data file.
Pertinently, here the graphical data may be construed not limited to visual information or audio-
10 visual information, but also be construed to include an audio data. For clarity, it is mentioned
that in case of a video call being made by the calling party, the video data or audio-visual data
may be presented to the calling party as the targeted information. However, in case of audio
call being made by the calling party to the called party, an audio data (for example, in *.3gp
format, *.mp3 format, etc.) may be presented to the calling party as the targeted information.
15 In an exemplary implementation, the CTAS [301] can send advertisement file name to MRF
unit for rendering the advertisement, which then intimates the CTAS [301] upon completion,
and the CTAS [301] in turn can send completion trigger to the advertisement server [312] to
register a hit against the corresponding advertisement campaign. Also, in case negative
availability is determined by the determination unit [304], then the transceiver unit [302] may
20 receive, from the advertisement server [312], a no-data indication. This no-data indication may
comprise an information related to a non-availability of the target advertisement for rendering
to the calling party. For this purpose, in an implementation, a Media Resource Function (MRF)
may be requested to render the audio clip.
25 [0075] After this, in an implementation, the rendering unit [308] may render this above targeted
information to the calling party based on the data received from the advertisement server [312]. In an implementation, where the rendering unit [308] renders this above targeted information to the calling party based on the data received from the advertisement server [312], the rendering unit [308] may send, to the advertisement server [312], a notification of completion.
30 Then, the advertisement server [312] can generate reports in real time along with number of
hits and relevant data which can be reconciled with other platforms to claim revenue.
[0076] Also, in an exemplary implementation, the CTAS [301] supports both hypertext transfer protocol – secured (HTTPS) and session initiation protocol (SIP) to query the
24

advertisement server [312] for clip name. This is configurable based on preference of the
advertisement server [312]. When SIP protocol is used, the CTAS [301] uses SIP OPTIONS
method as generally known in the art, and when HTTPS is used the CTAS [301] uses a GET
request to retrieve clip name. In an exemplary implementation, the CTAS [301] expects the
5 advertisement server [312] to provide the clip name within 200ms (which is configurable). Any
latency of more than the configurable time of, say, 200ms may lead to delayed call setup time.
Further, if due to any ambiguity in network, the advertisement server [312] fails to provide the
clip name within this configurable time of, say, 200ms, the CTAS [301] may render default
RBT tone. Also, multiple destinations of the advertisement server [312] can be configured for
10 the purpose of redundancy and the CTAS [301] may facilitate even distribution of load between
these destinations and if required, the CTAS [301] can check health status of each of these destinations.
[0077] Also, in an implementation, for performing the premium subscription procedure, the
15 determination unit [304] may determine a second level RBT preference of the called party in
an event the first level RBT preference of the called party is determined as the other first level RBT preference, wherein the second level RBT preference of the called party is one of a premium second level RBT preference, and an opt-out second level RBT preference. Continuing with the above example, say a user, i.e., the called party wants another user, i.e.,
20 the calling party, to listen to a ring back tone of the called party’s choice, and has therefore
opted for an other first level RBT preference. Further, in the second level RBT preference, say the called party selects the opt-out second level RBT preference. Then in that case, for the purposes of this example, the calling party may be provided with the regular calling tone, that is, the default tone provided by the network operator. Also, in the second level RBT preference,
25 say the called party selects the premium second level RBT preference, then the calling party
may be provided with the RBT of the called party’s choice. Thus, in this implementation, the rendering unit [308] may render one of a default tone as the RBT of the called party, and a set of preferred songs as the RBT of the called party, wherein the set of preferred songs is rendered as the RBT of the called party in an event the second level RBT preference of the called party
30 is determined as the premium second level RBT preference, and the default tone is rendered as
the RBT of the called party in an event the second level RBT preference of the called party is determined as the opt-out second level RBT preference. Also, in an implementation, the user preference may be notified to the CTAS [301] via a home subscriber server (HSS) using a Sh – Diameter message (Push Notification Request).
25

[0078] Further, at step 408, the method comprises rendering, by a rendering unit [308] of the
CTAS [301], the targeted information as the ring back tone (RBT) to the calling party based
on the performing of the termination service procedure. Here, this targeted information can be
5 one of: (a) a RBT of the called party’s choice in case the first level RBT preference of the called
party is the other first level RBT preference and the second level RBT preference of the called
party is the premium second level RBT preference; (b) a default RBT in case the first level
RBT preference of the called party is the other first level RBT preference and the second level
RBT preference of the called party is the opt-out second level RBT preference; (c) any other
10 RBT that may not be of the called party’s choice, such as advertisement information received
from the advertisement server [312] in case the first level RBT preference of the called party is the non-premium first level RBT preference.
[0079] Thereafter, the method terminates at step [410]. 15
[0080] Now referring to Fig. 5 which illustrates an exemplary flow chart indicating an
exemplary scenario for rendering a targeted information as a ring back tone (RBT) to a calling
party, in accordance with exemplary implementations of the present disclosure. The method of
Fig. 5 starts at block 502. As shown in block 504 of Fig. 5, the method comprises receiving a
20 SIP invite message at CTAS [301]. The SIP invite is received upon initiation of a call session
from the calling party to the called party. Further, a role of a node is determined, wherein the role of the node is determined as one of a termination role, and an origination role (See block 504 of Fig. 5). Further, the node may be a network element, for example a base station server or any other server that implements a relevant function using which a calling party makes a
25 call to the called party or the called party receives a call from a calling party. If the node is
connected to the calling party, the role of the node may be determined as an originating role, and if the node is connected to the called party, the role of the node may be determined as a terminating role. For example, a first user, i.e., the calling party makes a call to a second user, i.e., the called party. For this purpose, the first user may be connected to the base station in the
30 area where the first user is located. Further, when the user makes the call, the call may be
received by a base station of the area where the second user is located. Thus, the base station where the first user is located may be the originating node, and the base station where the second user is located may be the terminating node. A person skilled in the art would appreciate
26

that the above example is for understanding purposes only and does not limit or restrict the present disclosure in any possible manner.
[0081] Further, a termination service procedure is performed in an event the role of the node
5 is determined as the termination role (See block 506 of Fig. 5). Also, in case the role of the
node is determined as the originating role, then procedures related to originating services may
be implemented (See block 508 of Fig. 5). Further, for performing the termination service
procedure, a first level RBT preference of the called party is determined to check whether the
preference of the called party is of non-premium RBT or not (See block 510 of Fig. 5) (The
10 first level RBT preference of the called party is one of a non-premium first level RBT
preference, and an other first level RBT preference). The first level RBT preference of the called party is a preference of the called party as to whether the called party desires the calling party to listen to a specific RBT when the calling party calls the called party, or the called party
does not care for what the calling party listens to when the calling party calls the called party.
15
[0082] Also, for performance of the non-premium subscription procedure a contact
information of a calling party from a P-Asserted-Identity (PAI) header may be extracted (See
block 518 of Fig. 5). Further, one of a presence and an absence of an alert-info header with a
call-waiting indication may be determined, wherein the call-waiting indication indicates that
20 the called party is engaged in an already established session (See block 520 of Fig. 5). Further,
when a user makes a call to the called party, the alert for the called party should be received at the called party end, that is ‘180 ringing’ or such an alert should be received (see block 522 of Fig. 5). Here, a call waiting notification may be provided to the calling party as a call waiting service, in an event the alert-info header with the call-waiting indication is determined as
25 present (See block 524 of Fig. 5). That is, if the called party is on another call with some other
user, the calling party may not be presented with any other information but the call-waiting indication. Further, one of a positive availability and a negative availability of a target advertisement may be determined for rendering to the calling party, in an event the alert-info header with the call-waiting indication is determined as absent (See block 526 of Fig. 5). For
30 this purpose, a query may be sent to the advertisement server [312] via an HTTP interface about
a targeted advertisement campaign. The advertisement server [312], within fraction of seconds, using the one or more machine-learning based models may determine whether any advertisement is available that can be rendered, and which will be meaningful for the calling party. Also, here the positive availability is determined in an event the target advertisement for
27

rendering to the calling party is available, and the negative availability is determined in an
event the target advertisement for rendering to the calling party is not available. In case positive
availability is determined, then a data related to the target advertisement for rendering to the
calling party may be received (See block 526 of Fig. 5). Also, in case negative availability is
5 determined by the determination unit [304], then the transceiver unit [302] is configured to
receive, from the advertisement server [312], a no-data indication, in which case a default tone
may be rendered as RBT. Also, where the data related to the target advertisement for rendering
to the calling party is received, the targeted information/target advertisement may be rendered
to the calling party based on the data received from the advertisement server [312] (See block
10 528 of Fig. 5).
[0083] Also, for performing the premium subscription procedure, a second level RBT preference of the called party may be determined in an event the first level RBT preference of the called party is determined as the other first level RBT preference, wherein the second level
15 RBT preference of the called party is one of a premium second level RBT preference (See
block 512 of Fig. 5), and an opt-out second level RBT preference (See block 514 of Fig. 5). Also, in the second level RBT preference, say the called party selects the premium second level RBT preference, then the calling party may be provided with the RBT of the called party’s choice. Further, one of a default tone as the RBT of the called party, and a set of preferred
20 songs as the RBT of the called party may be rendered, wherein the set of preferred songs is
rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the premium second level RBT preference, and the default tone is rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the opt-out second level RBT preference (See block 516 of Fig.
25 5).
[0084] A person skilled in the art would appreciate that the above explanation with reference
to Fig. 5 is an exemplary scenario provided for understanding purposes only, and does not limit
or restrict the present disclosure in any possible manner. 30
[0085] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for rendering a targeted information as a ring back tone (RBT) to
a calling party, the instructions include executable code which, when executed by one or more
units of a system [300], causes: a determination unit [304] of a converged telephony application
35 server (CTAS) [301] to determine a role of a node, wherein the role of the node is determined
28

as one of a termination role, and an origination role; an analysis unit [306] of the CTAS [301]
to perform a termination service procedure, wherein the termination service procedure is
performed in an event the role of the node is determined as the termination role; and a rendering
unit [308] of the CTAS [301] to render the targeted information as the ring back tone (RBT) to
5 the called party based on the performing of the termination service procedure.
[0086] The present disclosure further discloses a user equipment (UE). The UE comprises a transceiver unit [302] configured to receive a targeted information as a ring back tone (RBT). The RBT is rendered at the UE by a system [300] based on: determining, by a determination
10 unit [304] of a CTAS [301], a role of a node, wherein the role of the node is determined as one
of a termination role, and an origination role; performing, by an analysis unit [306] of the CTAS [301], a termination service procedure, wherein the termination service procedure is performed in an event the role of the node is determined as the termination role; and rendering, by a rendering unit [308] of the CTAS [301], the targeted information as the ring back tone (RBT)
15 to the UE based on the performing of the termination service procedure, wherein the UE is a
calling party.
[0087] As is evident from the above, the present disclosure provides a technically advanced solution for rendering a targeted information as a ring back tone (RBT) to a calling party. The
20 present solution enriches the user experience of a calling party when a call is made to another
user. The solution conveys relevant information, such as offers, advertisements, etc., to the calling party instead of rendering a default tone. Also, with this, the solution that enables generation of revenues for a telecom operator from advertisement platforms. With the conveyance of information, the solution enhances awareness of important information to a
25 larger audience, which may be in public domain but largely remains unnoticed. Further, the
time of the calling end is also utilized by the entertaining content that is played for them while they are waiting for the call to be answered by the called party. Also, the solution further facilitates offering the relevant content for the end users based on their behavior.
30 [0088] While considerable emphasis has been placed herein on the disclosed implementations,
it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to
35 be implemented is illustrative and non-limiting.
29

We Claim:

5
10

1. A method for rendering a targeted information as a ring back tone (RBT) to a calling party, the method comprising:
- determining, by a determination unit [304] of a converged telephony application server (CTAS) [301], a role of a node, wherein the role of the node is determined as one of a termination role, and an origination role;
- performing, by an analysis unit [306] of the CTAS [301], a termination service procedure, wherein the termination service procedure is performed in an event the role of the node is determined as the termination role; and
- rendering, by a rendering unit [308] of the CTAS [301], the targeted information as the ring back tone (RBT) to the calling party based on the performing of the termination service procedure.

15
20
25
30

2. The method as claimed in claim 1, wherein prior to the determining, by the
determination unit [304] of the CTAS [301], the role of the node, the method comprises:
- receiving, by a transceiver unit [302] of the CTAS [301], a session initiation
protocol (SIP) invite, wherein the SIP invite is received upon initiation of a call
session from the calling party to a called party.
3. The method as claimed in claim 2, wherein the termination service procedure
comprises:
- determining, by the determination unit [304] of the CTAS [301], a first level RBT preference of the called party, wherein the first level RBT preference of the called party is one of a non-premium first level RBT preference, and an other first level RBT preference; and
- performing, by the analysis unit [306] of the CTAS [301], one of a non-premium subscription procedure and a premium subscription procedure, wherein the non-premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the non-premium first level RBT preference, and the premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the other first level RBT preference.

30

5
10
15
20

4. The method as claimed in claim 3, wherein the premium subscription procedure
comprises:
- determining, by the determination unit [304] of the CTAS [301], a second level RBT preference of the called party in an event the first level RBT preference of the called party is determined as the other first level RBT preference, wherein the second level RBT preference of the called party is one of a premium second level RBT preference, and an opt-out second level RBT preference; and
- rendering, by the rendering unit [308] of the CTAS [301], one of a default tone as the RBT of the called party, and a set of preferred songs as the RBT of the called party, wherein the set of preferred songs is rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the premium second level RBT preference, and the default tone is rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the opt-out second level RBT preference.
5. The method as claimed in claim 3, wherein the non-premium subscription procedure
comprises:
- extracting, by the analysis unit [306] of the CTAS [301], a contact information of a calling party from a P-Asserted-Identity header;
- registering, by the analysis unit [306] of the CTAS [301], the calling party as a potential target in a local database [310] associated with the CTAS [301]; and
- forwarding, by the transceiver unit [302] of the CTAS [301], a SIP invite request to the called party.

25 6. The method as claimed in claim 2, wherein prior to the rendering, by the rendering unit
[308], the targeted information as the ring back tone (RBT) to the called party, the method further comprises:
- determining, by the determination unit [304], one of a presence and an absence of
an alert-info header with a call-waiting indication, wherein the call-waiting
30 indication indicates that the called party is engaged in an already established
session;
31

- rendering, by the rendering unit [308], a call waiting notification to the calling party
in an event the alert-info header with the call-waiting indication is determined as
present;
- determining, by the determination unit [304] with an advertisement server [312],
5 one of a positive availability and a negative availability of a target advertisement
for rendering to the calling party using one or more machine-learning based models,
in an event the alert-info header with the call-waiting indication is determined as
absent, wherein the positive availability is determined in an event the target
advertisement for rendering to the calling party is available, and the negative
10 availability is determined in an event the target advertisement for rendering to the
calling party is not available; and
- receiving, by the transceiver unit [302] from the advertisement server [312], a data
related to the target advertisement for rendering to the calling party in an event the
positive availability is determined.
15
7. The method as claimed in claim 6, the method further comprising:
- receiving, by the transceiver unit [302] from the advertisement server [312], a no-
data indication in an event the negative availability is determined, wherein the no-
data indication comprises an information related to a non-availability of the target
20 advertisement for rendering to the calling party.
8. The method as claimed in claim 6, wherein the data comprises at least one of a graphical data file, and a source information of the graphical data file.

25
30

9. The method as claimed in claim 6, wherein after the rendering, by the rendering unit
[308], the targeted information as the ring back tone (RBT) to the called party, the
method comprises:
- sending, by the transceiver unit [302] to the advertisement server [312], a notification of completion.
10. A system [300] for rendering a targeted information as a ring back tone (RBT) to a
calling party, the system [300] comprising a converged telephony application server
(CTAS) [301], the CTAS [301] further comprising:

32

- a determination unit [304] configured to determine a role of a node, wherein the role of the node is determined as one of a termination role, and an origination role;
- an analysis unit [306] configured to perform a termination service procedure, wherein the termination service procedure is performed in an event the role of the
5 node is determined as the termination role; and
- a rendering unit [308] configured to render the targeted information as the ring back
tone (RBT) to the calling party based on the performing of the termination service
procedure.
10
11. The system [300] as claimed in claim 10, wherein the CTAS [301] further comprises a
transceiver unit [302], wherein prior to the determination unit [304] of the CTAS [301]
determines the role of the node, the transceiver unit [302] is configured to:
15
- receive a session initiation protocol (SIP) invite, wherein the SIP invite is received
upon initiation of a call session from the calling party to a called party.
12. The system [300] as claimed in claim 11, wherein for the performing of the termination
service procedure:
20
25
- the determination unit [304] is configured to determine a first level RBT preference of the called party, wherein the first level RBT preference of the called party is one of a non-premium first level RBT preference, and an other first level RBT preference; and
- the analysis unit [306] is configured to perform one of a non-premium subscription procedure and a premium subscription procedure, wherein the non-premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the non-premium first level RBT preference, and the premium subscription procedure is performed in an event the first level RBT preference of the called party is determined as the other first level RBT preference.
13. The system [300] as claimed in claim 12, wherein for performance of the premium
30 subscription procedure:
- the determination unit [304] is configured to determine a second level RBT
preference of the called party in an event the first level RBT preference of the called
party is determined as the other first level RBT preference, wherein the second level
33

RBT preference of the called party is one of a premium second level RBT preference, and an opt-out second level RBT preference; and
- the rendering unit [308] is configured to render one of a default tone as the RBT of
the called party, and a set of preferred songs as the RBT of the called party, wherein
5 the set of preferred songs is rendered as the RBT of the called party in an event the
second level RBT preference of the called party is determined as the premium second level RBT preference, and the default tone is rendered as the RBT of the called party in an event the second level RBT preference of the called party is determined as the opt-out second level RBT preference. 10
14. The system [300] as claimed in claim 12, wherein for performance of the non-premium
subscription procedure:
- the analysis unit [306] is configured to:
o extract a contact information of a calling party from a P-Asserted-Identity
15 header; and
o register the calling party as a potential target in a local database [310] associated with the CTAS [301]; and
- the transceiver unit [302] is configured to forward a SIP invite request to the called
party.
20
15. The system [300] as claimed in claim 11, wherein prior to the rendering unit [308]
rendering the targeted information as the ring back tone (RBT) to the called party:
- the determination unit [304] is configured to determine one of a presence and an
absence of an alert-info header with a call-waiting indication, wherein the call-
25 waiting indication indicates that the called party is engaged in an already established
session;
- the rendering unit [308] is configured to render a call waiting notification to the
calling party in an event the alert-info header with the call-waiting indication is
determined as present;
30 - the determination unit [304] is configured to determine with an advertisement server
[312], one of a positive availability and a negative availability of a target advertisement for rendering to the calling party using one or more machine-learning based models, in an event the alert-info header with the call-waiting indication is determined as absent, wherein the positive availability is determined in an event the

target advertisement for rendering to the calling party is available, and the negative availability is determined in an event the target advertisement for rendering to the calling party is not available; and
- the transceiver unit [302] is configured to receive from the advertisement server
5 [312], a data related to the target advertisement for rendering to the calling party in
an event the positive availability is determined.
16. The system [300] as claimed in claim 15, wherein the transceiver unit [302] is further
configured to:
10 - receive, from the advertisement server [312], a no-data indication in an event the
negative availability is determined, wherein the no-data indication comprises an
information related to a non-availability of the target advertisement for rendering to
the calling party.
15 17. The system [300] as claimed in claim 15, wherein the data comprises at least one of a
graphical data file, and a source information of the graphical data file.
18. The system [300] as claimed in claim 15, wherein post the rendering unit [308]
rendering the targeted information as the ring back tone (RBT) to the called party, the
20 transceiver unit [302] is configured to:
- send, to the advertisement server [312], a notification of completion.
19. A user equipment (UE) comprising:
- a transceiver unit configured to: receive a targeted information as a ring back tone
25 (RBT), wherein the RBT is rendered at the UE by a system [300] based on:
- determining, by a determination unit [304] of a CTAS [301], a role of a node,
wherein the role of the node is determined as one of a termination role, and an
origination role;
- performing, by an analysis unit [306] of the CTAS [301], a termination service
30 procedure, wherein the termination service procedure is performed in an event the
role of the node is determined as the termination role; and
- rendering, by a rendering unit [308] of the CTAS [301], the targeted information as
the ring back tone (RBT) to the UE based on the performing of the termination
service procedure, wherein the UE is a calling party.