Specification
TECHNICAL FIELD
[001] The subject matter described herein, in general, relates to telecommunication and/or finance and, in particular, relates to conducting 5 transactions during voice calls.
BACKGROUND
[002] Due to advantages, such as data security, convenience of use and instantaneous transactions, mobile transaction service industry is witnessing 10 a significant growth. A significantly large number of transactions are carried out using mobile devices.
[003] Mostly, a user gets registered with a mobile transaction service provider using a multimedia device, such as smartphone, tablet, laptop, capable of connecting to the internet. The multimedia device needs to be 15 connected to the internet for the user to perform a transaction. With the increasing number of devices connected to the internet for numerous transactions, the internet has gradually become a bottleneck for the mobile transaction service industry.
20
BRIEF DESCRIPTION OF DRAWINGS
[004] The detailed description is provided 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 drawings to reference like features 25 and components.
3
[005] Fig. 1 illustrates an exemplary network environment for implementing a system to conduct a transaction between user devices, according to an implementation of the present subject matter.
[006] Fig. 2 illustrates a system for conducting a transaction between user devices, according to an implementation of the present subject matter. 5
[007] Fig. 3 illustrates a method for conducting a transaction between user devices, according to an implementation of the present subject matter.
[008] Fig. 4 illustrates a method for conducting a transaction between user devices, according to another implementation of the present subject matter. 10
DETAILED DESCRIPTION
[009] Though use of multimedia devices connected to the internet does offer an instant mechanism of conducting online transactions, the multimedia 15 devices, network connectivity, or both may not be accessible to everyone to perform such transactions at all places. For example, data connection may not always be available for conducting transaction online. For example, a user may experience poor internet connectivity when in transit, or when located indoor, for example, in a basement. Accordingly, users may not wish 20 to be restricted by their dependence on the internet for conducting transactions.
[0010] Further, the rural population, having limited access to multimedia devices and network resources is unable to reap benefits of such online transactions. Also, the inability to use high-tech multimedia devices is a major 25 road block for population having limited access to technology. Hence, such a population needs to rely on paper based transaction through banks or cash transaction amongst each other.
4
[0011] To this end, systems and methods for conducting transactions over a telephone network are described herein. The telephone network having far greater availability and penetration than that of the internet, overcomes the above-described problems associated with online transactions conducted over the internet. 5
[0012] Various embodiments of the present subject matter disclose a method and system for conducting a transaction between a first user device to a second user device. The first user device may be provided with an option of initiating the transaction between the first user device and the second user device. The option may be provided to the first user device during an active 10 voice call between the first user device and the second user device. In response to the providing, a user may enter, through the first user device, a service number associated with a transaction that the user may wish to perform. In an example, the service number may be a dual tone multi-frequency (DTMF) input. On the basis of the service number provided by the 15 user, the transaction may be performed between the first user device and the second user device.
[0013] In an implementation, an in-call announcement may be made to notify successful completion of the transaction. The in-call announcement may be made during the active voice call between the first user device and 20 the second user device. Also, the in-call announcement may simultaneously audible to the first user device and the second user device. In another implementation, a text message such as short message service (SMS) may be sent to notify successful completion of the transaction.
[0014] Thus, a user having either a stationary or and portable device with 25 active telecommunication connection is capable of conducting a transaction with another device, without connecting to the internet. The systems and methods for conducting transactions described herein, eliminate the need of
5
consistent internet connectivity and the need of multimedia device capable of connecting to the internet.
[0015] The above methods and system are further described in conjunction with the following figures. It should be noted that the description and figures merely illustrate the principles of the present subject matter. It will thus be 5 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 10 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 15 thereof, are intended to encompass equivalents thereof.
[0016] 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 20 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.
[0017] Fig. 1 illustrates a communication network environment 100 implementing a voice call system 102 for allowing users to conduct 25 transactions using voice calls, according to an embodiment of the present subject matter. The voice call system 102 may be implemented as a
6
combination of two servers, i.e., a user interaction server 104 and a transaction server 106 as illustrated in Fig. 1.
[0018] The communication network environment 100 comprises various user devices 108-1, 108-2, 108-3, ... , 108-N connected to the voice call system 102. The user devices 108-1, 108-2, 108-3, ... , 108-N, may be 5 collectively referred to as user devices 108. Examples of the user devices 108 include, but are not restricted to fixed/wired telephones, handheld devices, tablet computers, mobile phones, PDAs, smartphones, and the like. Each of the user devices 108 works on a communication protocol as defined by a communication network to which the user device 108 is coupled. 10
[0019] In the communication network environment 100 the user devices 108 communicate with each other through a communication network 110. The communication network 110 may be a wireless or a wired network, or a combination thereof. Examples of such individual networks include, but are not limited to, Global System for Mobile Communication (GSM) network, 15 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 (NON), Public Switched Telephone Network (PSTN). Depending on the technology, the communication network 110 includes 20 various network entities, such as gateways, routers; however, such details have been omitted for sake of brevity of the present description.
[0020] The voice call system 102 enables a voice call to be established between the user devices 108. In order to communicate with each other, the user devices 108 connect to their respective base transceiver stations (not 25 shown in the figure), which provide radio coverage within a cell. 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
7
stations. The base station controller is further connected to a mobile switching center (MSC) (not shown in the figure), which is responsible for allowing the different user devices 108 to communicate with each other. The mechanisms implemented to connect the user devices 108 to the communication network 110 have not been elaborated to maintain brevity of the present description. 5
[0021] In one example, the voice call system 102 may couple a calling device, such as the user device 108-1 to a callee device, such as the user devices 108-n for a voice call between the two devices. For the purpose, in one example implementation, the voice call system 102 includes the user interaction server 104 for relaying content to and from, the user device 108-1 10 and user device 108-n.
[0022] In one example implementation, the voice call system 102 also includes the transaction server 106, communicatively coupled to the user interaction server 104. The transaction server 106 may communicate with the user device 108-1 and user device 108-n to carry out a transaction during the 15 voice call.
[0023] Examples of the user interaction server 104 and the transaction server 106 include, but are not restricted to Application server, Blade server, Cloud server, Database server, Dedicated server, File server, Print server, Proxy server, Standalone server, and Web server. 20
[0024] The calling device, i.e., the user device 108-1 in the present example, may be provided with an option of initiating a transaction during the ongoing call with the calling device, i.e., the user device 108-n. In one example, the service number may be known to the user. In another example, one or more services numbers associated with different types of transactions 25 may be announced by the voice call system 102 at the time of initiation of the voice call. In an implementation, the service number may be a dual tone multi-frequency (DTMF) input. Accordingly, upon being provided with the
8
option, the user of the user device 108-1, may input a service number associated with a transaction that he may wish to perform. Based on the service number provided by the user, the transaction may be performed between the user device 108-1 and user device 108-n. In an implementation, the voice call system 102 may make an in-call announcement in the ongoing 5 voice call to notify the user device 108-1 and user device 108-n of the successful completion of the transaction.
[0025] While the foregoing description is explained with reference to the user devices 108-1 and 108-n, it will be understood that the same is only for the purpose of aiding understanding of the present subject matter. The 10 method of conducting transaction over voice call as explained here, can be extended to other user devices as well.
[0026] Fig. 2 illustrates the voice call system 102, according to an embodiment of the present subject matter. In accordance with an implementation the voice call system 102 may also be implemented as a 15 single server having engines performing different functions. In one implementation, the voice call system 102 includes processor(s) 202 coupled to a memory 204. The voice call system 102 further includes interface(s) 206, for example, to facilitate communication with the user device 108. The interface(s) 206 may include a variety of software and hardware interfaces, 20 for example, interfaces for peripheral device(s). Further, the interface(s) 206 enables the voice call system 102 to communicate with other devices, such as web servers and external repositories. The interface(s) 206 can also facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example LAN, cable, etc., and 25 wireless networks such as WLAN, cellular, or satellite. For the purpose, the interface(s) 206 may include one or more ports for connecting a number of computing devices to each other or to other server computers.
9
[0027] The processor(s) 202 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) 202 are configured to fetch and execute 5 computer-readable instructions stored in the memory 204.
[0028] The memory 204 may include a computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), etc., and/or non-volatile memory, such as erasable program read only memory 10 (EPROM), flash memory, etc.
[0029] Further, the memory 204 includes engine(s) 208 and data 210. The engine(s) 208 include, for example, the user interaction engine 212, the transaction engine 214, a notification engine 216, and other engine(s) 218. The other engine(s) 218 may include programs or coded instructions that 15 supplement applications or functions performed by the voice call system 102.
[0030] The data 210 includes a user registration data 220, service number list 222, and other data 224. In one implementation, the user registration data 220, service number list 222 are stored in the memory 204 in the form of look-up tables. Further, the other data 224, amongst other things, may serve as a 20 repository for storing data that is processed, received, or generated as a result of the execution of one or more engines in the engine(s) 208. Although the data 210 is shown internal to the voice call system 102, it may be understood that the data 210 may reside in an external repository (not shown in the figure), which is coupled to the voice call system 102. The voice call 25 system 102 may communicate with the external repository through the interface(s) 206 to obtain information from the data 210.
10
[0031] In one implementation, the voice call system 102 includes the abovementioned user interaction engine 212 to receive a request from a first user device 108-1 to initiate a voice call to a second user device 108-2. The first user device 108-1 and the second user device 104-2 are registered with the voice call system 102. Further, the user interaction engine 212 may use 5 the user registration data 220 for establishing the voice call. The user registration data 220 may include user and user device information such as name, address, date of registration, telephone number.
[0032] The user interaction engine 212 may provide the first user device 108-1 an option to conduct a transaction with the second user device 108-2. 10 In an example, the user interaction engine 212 is configured to receive an input, such as DTMF corresponding to balance transfer. In another example, the user interaction engine 212 may make an in-call announcement to provide the first user device 108-1 the option to conduct the transaction with the second user device 108-2. Also, the user interaction engine 212 may 15 provide the option of conducting transaction to the first user device 108-1 by providing specific code for an affirmative response and another specific code for a negative response. For example, the user interaction engine 212 may request the first user device 108-1 to press 2 from keypad of the first user device 108-1 for initiating the transaction and to press 3 from the keypad of 20 the first user device 108-1 for continuing with the voice call without the transaction.
[0033] Communication control between the first user device 108-1 and the second user device 108-2 may handoff to the transaction engine 214, upon receiving an affirmative response from the first user device 108-1, to conduct 25 the transaction. The transaction engine 214 may provide the first user device 108-1 with assistance for conducting the transaction.
11
[0034] In an example, the transaction engine 214 may provide the first user device 108-1 with the service number list 222. The service number list 222 may include a list of items that may be allowed to be transacted between the first user device 108-1 and the second user device 108-2, and service number corresponding to each of the item in the service number list 222. For 5 instance, the items may comprise points, credit, and balance that may be transacted between the first user device 108-1 and the second user device 108-2.
[0035] Points may be understood as loyalty points that a user may have accumulated by availing service offered by the service provider. For instance, 10 the service provider may provide links to content, such as advertisements to the user from time to time, such that if the content is viewed by the user, the user may earn loyalty points. Credit may be understood as a monetary item. For instance, credit may be bitcoins available with the user. In another example, the credit may be dollars in user’s account. Balance may be 15 understood as data usage balance or calling balance, that a user may have bought from the service provider. For instance, the user may get talk time recharged or updated from a service provider kiosk.
[0036] The transaction of each item may be considered as a service provided by the voice call system 102 and each service may be associated 20 with a different service number. A service number may be a code designated by the voice call system 102 for a given transaction service. In an example, the service number ‘*2’ may be associated with the transaction service of transferring credit form the first user device 108-1 to the second user device 108-2. In another example, a service number ‘#5’ may be associated with 25 activation of a multimedia service, such as activating a song as a ringtone.
[0037] Accordingly, in an example, the transaction engine 214 may make an in-call announcement requesting the first user device 108-1 input the
12
service number ‘*2’ to transact credit to the second user device 108-2, input the service number ‘*3’ to transact points to the second user device 108-2, or input the service number ‘*4’ to transact balance to the second user device 108-2.
[0038] Upon receiving a service number from amongst the service numbers 5 included the service number list 222 as an input from the first user device 108-1, the transaction engine 214 may compare the service number received with the service number list 222, to verify correctness of the service number received and identify the service requested by the first user device 108-1. If the service number received is incorrect, the transaction engine 214 may 10 make an in-call announcement to enter correct service number.
[0039] If the service number is correct, the transaction engine 214 may prompt the first user device 108-1 to enter the sum of item that the first user device 108-1 wishes to transfer to the second user device 108-2. In an example, the sum of the item to be transacted may be predefined by the first 15 user device 108-1. In another example, the sum of the item to be transacted may be predefined by the transaction engine 214. For example, every time the first user device 108-1 inputs the service number ‘*4’ to transfer balance, for example, balance of points, to the second user device 108-2, a default value of 100 points may be transferred from the account associated with the 20 first user device 108-1 to that of the second user device 108-2.
[0040] Next, the transaction engine 214 may verify if account of the first user device 108-1 has required quantity of the item to permit the sum of the item to be transacted. If the account of the first user device 108-1 has a quantity of the item less than the sum of the item to be transferred, then the 25 transaction fails and the first user device 108-1 is notified accordingly and may be requested to recharge the quantity of the item.
13
[0041] If the account of the first user device 108-1 has the quantity equal to or more than the sum of the item to be transferred, then transaction engine 214 requests the first user device 108-1 to enter a user specific code. The user specific code is used for authentication purposed. For example, the user specific code may be alike a password previously issued to the first user 5 device 108-1 by the service provide for authenticating transactions.
[0042] The transaction engine 214 verifies if the user specific code entered by the first user device 108-1 is valid. If the user specific code is invalid, then the first user device 108-1 may be requested to re-enter a valid user specific code. However, if the first user device 108-1 enters invalid user specific code 10 for a predetermined number of times, then the transaction gets aborted.
[0043] Finally, upon successful entry of the user specific code, the transaction engine 214 may execute the transaction between the first user device 108-1 and the second user device 108-2. The transaction engine 214 may also inform the notification engine 216 about successful transaction and 15 invoke the notification engine 216 to notify the first user device 108-1 and the second user device 108-2 about the transaction. For example, the notification engine 216 may make an in-call announcement to notify the first user device 108-1 about debit from account of the first user device 108-1 and credit to account of the second user device 108-2. 20
[0044] According to an aspect of the present subject matter, from the transaction between the first user device 108-1 and the second user device 108-2 is done over a voice call. Thus, the transactions between the first user device 108-1 and the second user device 108-2 is performed without the need for internet connectivity. 25
[0045] Fig. 3 and Fig. 4 illustrate exemplary methods for transaction over voice call, according to an implementation of the present subject matter.
14
[0046] The exemplary methods may be described in the general context of computer executable instructions embodied on a computer-readable medium. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., which perform particular functions or implement particular abstract data types. 5 The method may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices. 10
[0047] The order in which the methods rare 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 methods, or an alternative method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the methods, systems and 15 devices described herein. Furthermore, the methods can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0048] Referring to Fig. 3, at block 302, during an active voice call between a first user device 108-1 and a second user device 108-2, an option of initiating a transaction between the first user device 108-1 and the second 20 user device 108-2, may be provided to the first user device 108-1. The first user device 108-1 and the second user device 108-2 are registered with same voice call system 102.
[0049] The option may include service number dedicated for the transaction that may be provided by making an in-call announcement to the 25 first user device 108-1. For example, the announcement may be audible to the first user device 108-1 alone or to both first user device 108-1 as well as the second user device. For example, the announcement may provide the
15
option that if the first user device 108-1 wishes to transfer credits, the first user device 108-1 may enter the service number on the device. The service number may be a code designated by the voice call system 102 for the transaction service. Each service provided by the voice call system 102 may have a different service number. For example, *3 may be service number for 5 transaction service, #5 may be service number for ringtone service, and the like. In an example, the option may be provided by the user interaction engine 212.
[0050] At block 304, the service number may be received from the first user device 108-1 in response to providing the option at block 302. In an 10 implementation, the user interaction engine 212 may receive the service number from the first user device 108-1.
[0051] At block 306, based on the service number received at block 304, the transaction between the first user device 108-1 and the second user device 108-2 may be performed. In an implementation, the transaction 15 corresponding to the service number may be performed between the first user device 108-1 and the second user device 108-2 by the transaction engine 214.
[0052] Finally, at block 308, a notification may be made by a notification engine 216. The notification may, for example, be an in-call announcement to 20 confirm successful transaction from the first user device 108-1 to the second user device 108-2.
[0053] Referring to Fig. 4, at block 402, a voice call may be initiated between a first user device 108-1 and a second user device 108-2. The first user device 108-1 and the second user device 108-2 are registered with 25 same voice call system 102. The voice call initiation may be based on registration number of the first user device 108-1 and the second user device
16
108-2. In an example, the voice call may be initiated by the user interaction server 104.
[0054] At block 404, the first user device 108-1 may be provided an option to initiate a transaction with the second user device 108-1. Further, the first user device 108-1 may be informed of input to be provided by the first user 5 device 108-1, in order to initiate the transaction. For example, the first user device 108-1 may be asked to dial # as input, to initiate the transaction. In an example, the option may be provided by the user interaction server 104. The user interaction server 104, may provide the option by means of an in-call announcement. 10
[0055] At block 406, it is determined whether the first user device 108-1 wishes to initiate transaction with the second user device 108-2. In an example, the user interaction server 104 may determine whether transaction is to be initiated by the first user device 108-1.
[0056] Further, at block 410, based on the response received from the first 15 user device 108-1, a service number is notified to the first user device 108-1 for conducting the transaction with the second user device 108-2. For example, if the first user device 108-1 wishes to transfer credits, the first user device 108-1 may enter the service number on the device. In an implementation, the user interaction server 104 notifies the service number to 20 the first user device 108-1. In an example, the first user device 108-1 may be notified through in-call announcements.
[0057] Furthermore, if the first user device 108-1 does not want to perform the transaction, as disclosed at block 408, the first user device 108-1 may not enter any input. In such a scenario, the user interaction server 104 may wait 25 for a predetermined time before aborting the transaction, and continuing with voice call.
17
[0058] At block 412, the service number entered by the first user device 108-1 may be received. The service number may be received by the user interaction server 104, in an example.
[0059] At block 414, the method may verify whether or not the service number is correctly entered by the first user device 108-1. The verification 5 may be done by a transaction server 106, in accordance with an implementation.
[0060] If the service number is incorrectly entered, the method may proceed to block 422. At block 422, another notification may be provided to the first user device 108-1 for entering the service number. In an example, a 10 notification engine 216 may share the notifications through in-call announcement.
[0061] If the service number entered is correct, the method may proceed to block 4416. At block 416, the first user device 108-1 may be prompted to enter the sum of item to be transferred to the second user device 108-2. The 15 prompt to the first user device 108-1 may be provided by the transaction server 106.
[0062] At block 418, the item of credits to be transferred is received as input from the first user device 108-1. The input may be received by the transaction server 106. 20
[0063] At block 420, it is verified if the first user device’s 108-1 account balance permits the sum of the item to be transferred. The transaction server 106 may do the requisite verification, at block 420.
[0064] The method shifts to block 422, if the first user device’s 108-1 account balance is less than the sum of the item to be transferred. At block 25 422 the transaction fails and the first user device 108-1 is requested to recharge the account balance by the transaction server 106.
18
[0065] If the first user device’s 108-1 account balance is equal to or more than the sum of the item to be transferred, the method may proceed to block 424. At block 424, the first user device 108-1 may be requested to enter a user specific code by the transaction server 106. The user specific code may be used for authentication of the user. For example, user specific code may 5 be a passcode. The user specific code may be generated upon registration of user with voice call system 102. Further, the user specific mode may be unique for the user.
[0066] At block 426, the user specific code may be received from the first user device 108-1. In an example, the transaction server 106 may receive the 10 user specific code from the first user device 108-1.
[0067] At block 428, it is verified if the user specific code entered by the first user device 108-1 is valid. The verification at block 428 may be done by the transaction server 106.
[0068] If the user specific code is invalid, then the method may be 15 redirected to block 430 to re-enter a valid user specific code. However, if the first user device 108-1 enters invalid user specific code for a predetermined number of attempts, then the transaction does not get transferred to block 430 and moves to block 432 to get aborted.
[0069] If the user specific code is valid, then the method proceeds to block 20 434. At block 434, first user device’s 108-1 account is debited with the sum of the item and the second user device’s 108-2 account is credited with the sum of the credits transferred. The transfer of sum of the item from the first user device 108-1 to the second user device 108-1 may be carried out by the transaction server 106. A real-time notification may be made by the 25 notification engine of the transaction server 106 (not shown). The notification may, for example, be an in-call announcement to confirm successful transaction from the first user device 108-1 to the second user device 108-2.
19
[0070] Although implementations for performing transaction over voice call have been described in language specific to structural features and/or methods, it is to be understood that the present subject matter (and not appended claims) is not necessarily limited to the specific features or methods described. Rather, the specific features and methods for transaction 5 over voice call are disclosed as exemplary implementations of the present invention.
I/We Claim:
1. A method of conducting a transaction over voice call between a first user device (108-1) and a second user device (108-2), the method comprising: 5
providing (302) to the first user device (108-1), an option of initiating the transaction between the first user device (108-1) and the second user device (108-2), during an active voice call between the first user device (108-1) and the second user device (108-2);
receiving (304) in response to the providing, a service number 10 associated with the transaction from the first user device (108-1), during the active voice call between the first user device (108-1) and the second user device (108-2);
performing (306) the transaction between the first user device (108-1) and the second user device (108-2), based on the service 15 number received from the first user device (108-1); and
making (308) an in-call announcement in the active voice call to notify successful completion of the transaction to the first user device (108-1) and the second user device (108-2).
2. The method as claimed in claim 1 further comprising registering the 20 first user device (108-1) and the second user device (108-2) with a same voice call system (102).
3. The method as claimed in claim 1, wherein the service number is a dual tone multi-frequency (DTMF) input.
4. The method as claimed in claim 1, wherein the transaction comprises 25 transfer of items from the first user device (108-1) to the second user device (108-2), wherein the items comprise at least one of points, credit, and balance.
21
5. The method as claimed in claim 1, wherein the providing comprises providing the service number associated with the transaction to the first user device (108-1).
6. The method as claimed in claim 5, wherein the providing comprises making an in-call announcement. 5
7. The method as claimed in claim 6, wherein the in-call announcement is audible to the first user device (108-1) alone, and wherein the first user device (108-1) initiates the active voice call between the first user device (108-1) and the second user device (108-2).
8. A computer implemented system (102) for conducting a transaction 10 between a first user device (108-1) and a second user device (108-2), the system comprises:
an user interaction engine (212), operationally coupled to a processor, to:
provide to the first user device (108-1), an option of 15 initiating the transaction between the first user device (108-1) and the second user device (108-2), during an active voice call between the first user device (108-1) and the second user device (108-2);
receive, in response to the providing, a service number 20 associated with the transaction from the first user device (108-1), during the active voice call between the first user device (108-1) and the second user device (108-2);
a transaction engine (214), operationally coupled to the processor to perform the transaction between the first user device 25 (108-1) and the second user device (108-2), based on the service number received from the first user device (108-1); and
22
a notification engine (216), operationally coupled to the processor, to notify successful completion of the transaction to the first user device (108-1) and the second user device (108-2) through an in-call announcement in the active voice call.
9. The computer implemented system (102) as claimed in claim 8, 5 wherein the first user device (108-1) and the second user device (108-2) are registered with a same voice call system (102).
10. The computer implemented system (102) as claimed in claim 8, wherein the transaction comprises transfer of items from the first user device (108-1) to the second user device (108-2), wherein the items 10 comprise at least one of points, credit, and balance.
11. The computer implemented system (102) as claimed in claim 8, wherein the user interaction engine (212) provides a service number associated with the transaction to the first user device (108-1), with the option of initiating the transaction. 15
12. The computer implemented system (102) as claimed in claim 11, wherein the user interaction engine (212) provides the service number by making an in-call announcement.
