TECHNICAL FIELD

[001] The embodiments herein relate to wireless communications and, more particularly, to a method and system for triggering one user account through another user account, in mobile communication.

BACKGROUND

[002] Currently, in addition to making and receiving calls and messages, mobile stations (MS) have plenty of applications such as camera, music and video player, internet facility, torch, GPS, maps and so on. These applications consume battery charge, which in turn affects battery life of the phone. It may happen that the charge of the MS goes down completely at the moment the user wants to make an urgent call. In another instant, the situation may be that the user forgets to take his/her MS with him and he/she wants to make call. There may be other situations where the user may not have access to the MS.

[003] In these situations, only solution might be that the user accesses a public telephone booth or else manages to get a MS from another user. When a user accesses MS of some other user, the next question is how the user can pay the other user. As the call charge may be in fractions, the payment may not be accurate. Because of this reason, most of the users may hesitate to offer their MSs to the one in need.

[004] One existing solution for this issue is virtual calling cards. A virtual calling card system provides the user certain pin number and the user account can be topped up online or by using credit cards. When the payment is made, the PIN number is delivered to the user, by email, to a password protected account. With this system, the user can make calls through any MS or land phone with the charge being deducted from his/her virtual account. But, virtual calling cards have certain disadvantages. The user must have a system with internet connectivity to receive the PIN and email confirmations. Further, though the number of users of this technology is constantly increasing, not every country supports this technology. Further, the virtual calling cards are coming with set time limits for top up and usage. If the virtual accounts are not regularly used or else if the account is not top upped in certain time periods, it may get deactivated. Further, the access number is not free with all cell phones.

[005] Another disadvantage of the existing systems is that they help users/subscribers to make calls using another device but does not provide any call forwarding mechanism to receive calls to a particular device. One existing system that facilitates call forwarding mechanism requires the call forwarding to be activated to a specific number by sending a request from the MS of the person who intends to activate the call forwarding. The disadvantage of this method is that if the MS get switched off or else if the user forgets to take his/her MS, the request can not be sent and hence the call forwarding facility can not be activated.

SUMMARY

[006] In view of the foregoing, an embodiment herein provides a method for enabling a first party in a mobile communication network to make a call using a mobile phone of a second party, the method comprising of sending an Unstructured Supplementary Service Data (USSD) string by the mobile phone of the second party to the communication network; checking account of the first party if the first party is authorized to make the call by the communication network; initiating connection by the communication network between the mobile phone and a destination number, if the first party is authorized to make the call; and charging account of the first party for the call by the communication network.

[007] Also, disclosed herein is a mobile communication network for enabling a first party to make a call using a mobile phone of a second party, the network comprising at least one means configured for checking account of the first party if the first party is authorized to make the call, on receiving an Unstructured Supplementary Service Data (USSD) string from the mobile phone of the second party; initiating connection between the mobile phone and a destination number, if the first party is authorized to make the call; and charging account of the first party for the call.

[008] Further, disclosed herein is an apparatus in a mobile communication network for enabling a first party to make a call using a mobile phone of a second party, the apparatus comprising at least one means configured for checking account of the first party if the first party is authorized to make the call, on receiving an Unstructured Supplementary Service Data (USSD) string from the mobile phone of the second party; initiating connection between the mobile phone and a destination number, if the first party is authorized to make the call; and charging account of the first party for the call.

[009] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES

[0010] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:

[0011] FIG. 1 illustrates a block diagram which shows various components of a mobile communication system, as disclosed in the embodiments herein;

[0012] FIG. 2 illustrates a block diagram which shows various components of the proposed Network, as disclosed in the embodiments herein;

[0013] FIG. 3 is a flow diagram which illustrates various steps involved in the process of registering a first party Mobile Station International Subscriber Directory Number (MSISDN) with second party account for making calls using proposed mechanism, as disclosed in the embodiments herein;

[0014] FIG. 4 is a flow diagram which illustrates various steps involved in the process of making calls using proposed mechanism, as disclosed in the embodiments herein; and

[0015] FIG. 5 is a flow diagram which illustrates various steps involved in the process of receiving a call using proposed call diverting mechanism, as disclosed in the embodiments herein.

DETAILED DESCRIPTION OF EMBODIMENTS

[0016] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0017] The embodiments herein disclose a system and method for accessing one user account through another user account by triggering one user account through another user account in a mobile communication system. Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0018] FIG. 1 illustrates a block diagram which shows various components of a mobile communication system, as disclosed in the embodiments herein. The system comprises a mobile station (MS) 101 and communication network 102. The communication network 102 further comprises a Base Transceiver Station (BTS) 102.a, a Base Station Controller (BSC) 102.b, a Mobile Switching Centre (MSC) 102.C, a Gateway MSC (GMSC) 102.d and an Intelligent Network (IN) module 102.e The MS 101 is connected to the communication network 102 through BTS 102.a. The BTS 102.a facilitates wireless communication between the MS 101 and the communication network 102. The BTS 102 may also perform functions such as encryption and decryption of data, signal filtering and so on. Further, the BTS 102 forms a part of the BSS 102.b. The BSC 102.b is responsible for handling traffic and signaling between MS 101 and the communication network 102. The BSC 102.b may also perform operations such as transcoding of speech signals, allocation of radio channels to MS 101, paging, transmission and reception over air interface and so on. Further, the BSC 102.b is connected to the MSC 102.C. The MSC 102.C is responsible for routing of messages and calls across the network. In addition to routing, the MSC 102.c also performs operations such as setting up and releasing end to end connections, handling mobility and handover requirements during the call and so on. In one embodiment, the MSC 102.c may facilitate making and receiving of calls through account triggering using the IN module 102.e. The process of account triggering may allow a first party user to make and receive calls using a second party user's MS, with call charge being deducted from the first party user's device. Further, the gateway MSC (GMSC) 102.d is responsible for identifying under which MSC 102.C the MS 101 is present at a specific instant of time. When a call arrives for the MS 101, the GMSC 102.d identifies the MSC 102.c under which the MS 101 is present and routes the call to the identified MSC 102.C. Further, the MSC 102.c and the GMSC 102.d are connected to the intelligent network (IN) module 102.e. The IN module 102.e provides real time charging and value added services to the operators. Further the IN module 102.e facilitates using a second party's mobile device for making and receiving calls with charge being deducted from the calling party's (first party here) account. The IN module 102.e may be further used for prepaid and/or postpaid charging.

[0019] FIG. 2 illustrates a block diagram which shows various components of the proposed Network, as disclosed in the embodiments herein. The network, as depicted, comprises of an Entity Identity Register (EIR) 201, an Authentication Centre (AUC) 202, a Home location Register (HLR) 203, a Visitor Location Register (VLR) 204, MSC 102.C and IN Node 102.e. The EIR 201 stores identity data related to all the MS 101 connected to the MSC 102.c. The identity data stored in the EIR 201 may be used to prevent calls from stolen MSs 101. The AUC 202 may be used to store authentication information related to each user, such as keys for encryption. The HLR 203 stores information related to all users registered with the communication network 102. The user information stored in the HLR 203 may comprise permanent information such as user profile as well as temporary information such as present location related to each user registered to the communication network 102. The VLR 204 is used to store the MSs 101 being served at a particular instant of time. Further, IN Node 102.e may be used to facilitate and receiving of calls from and to a particular MS 101 using the proposed mechanism. Using the proposed mechanism, a first party user can make calls from a second party user's device, with the call being charged from the first party user's account. Further, the proposed mechanism can be used by a first party user to receive calls to a second party user's device. In this case, the first party user may or may not get charged for the received call, based on the location of the second party user's device. For example, if the second party device is in roaming condition and if the first party receives calls to the second party device using the proposed mechanism, the first party may be charged according to the roaming norms.

[0020] FIG. 3 is a flow diagram which illustrates various steps involved in the process of registering a first party Mobile Station International Subscriber Directory Number (MSISDN) with second party account for making calls using proposed mechanism, as disclosed in the embodiments herein. The MSISDN may refer to mobile number of the user. In order to register his/her MSISDN with a second party's network, the first party initially dials (301) an Unstructured Supplementary Service Data (USSD) string from the second party's MS 101. In one embodiment, the first party MSISDN and second party MSISDN may have to be of same service provider to use the proposed call service from each other's devices. In another embodiment, the first party MSISDN and the second party MSISDN may be of different service providers. In this case, the first party network and the second party network may have to be in terms to facilitate proposed mechanism also to provide means for exchange operator specific user data such as account balance and location information of the user. Further, plurality of operating networks may come to terms for exchange of information by sharing an agreement between them. The service providers may use a suitable interface such as XML, Diameter and so on for exchange of information. The USSD string may comprise data such as an access code, a password and first party's MSISDN in a pre defined format. The first party user may receive the access code and password for using the proposed call mechanism while registering his/her MSISDN to the proposed call service. The format in which the data in the USSD string are to be arranged may be pre-defined by the system. Upon receiving the USSD string, the system identifies the first party's MSISDN from the received USSD string. Further, the system identifies (302) account of first party user. The system may identify first party user's account by using the first party MSISDN being identified from the USSD string dialed from the second party's device. If the first party MSISDN doesn't belong to the operator of communication network 102, then the operator may forward the request to the operator of the network to which the first party MSISDN belongs, if appropriate agreement exists between the two operators. In an embodiment herein, an internal configurable list can be maintained by IN module 102.e, wherein the list enables the operator to know to which operator the first party MSISDN belongs and forward the information request to that operator using a suitable interface such as XML, DIAMETER and so on. Further the system checks (303) various parameters associated with the identified first party account. The system may check parameters such as account balance, life cycle and so on of the first party's account. Further, the obtained account information may be used by the system when the user uses the proposed mechanism. For example, when the first party user use the proposed mechanism for making or receiving calls, the system may check if the first party user account possesses a minimum balance for using this service. In one embodiment, the service provider may set a minimum balance amount for the user to use this service and the user may be allowed to use the service only if he/she possesses the minimum set balance in the account. Further, the system configures (304) the first party MSISDN with the account of the second party. In one embodiment, the system may configure the first party's MSISDN with the second party's account by storing the first party's MSISDN in a pre-defined field in the second party's account information. Further, the system sends (305) acknowledgement to the second party's device. The acknowledgement may be in the form of a text message or voice message or any other suitable form. The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.

[0021] FIG. 4 is a flow diagram which illustrates various steps involved in the process of making calls using proposed mechanism, as disclosed in the embodiments herein. After registering the first party's MSISDN with the second party's account, the first party can make call from the second party's device 101. Upon receiving (401) the call connection request from the second party's device, the system checks (402) if the received call is being triggered from a first party account or not.. In a preferred embodiment, the system checks if the received call is triggered from a first party account or not, by checking if the first party MSISDN is present in the pre-defined field of the second party account or not. In another embodiment, the system may check in the second party's account information if a flag that indicates triggering of calls from a first party's account is set ON or not. If the call is not triggered from a first party account, the system connects (403) the call to the dialed MSISDN and deducts (404) call charge from the second party's account. If the first party's MSISDN is present in pre-defined field of second party's account information, the system retrieves (405) the first party MSISDN from the pre-defined field of second party information. Further the system identifies (406) location of the second party's device and also checks (407) if the first party account has enough balance to make the call. If the first party account does not have enough balance to make the call, the system informs (410) the first party user and terminates (411) the call. If the first party account has enough balance to make the call, the system connects (408) the call to dialed MSISDN and deducts call charge from first party's account as soon as the call is finished. The call charges may be according to the norms of the service provider. The system may display the first party user's MSISDN in the device of the person who receives the call. Further, the service provider may use the first party's location information retrieved by the system for billing purposes. For example, if the second party device is in roaming condition, the first party may be charged according to roaming norms by the service provider. In one embodiment, the first party's MSISDN may be erased from the second party's account information automatically once the first party finishes the call from the second party's device. The various actions in method 400 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.

[0022] FIG. 5 is a flow diagram which illustrates various steps involved in the process of receiving a call using proposed call diverting mechanism, as disclosed in the embodiments herein. In order to receive calls using the proposed mechanism, the first party dials (501) a USSD string from the second party's device 101. The USSD string may comprise data such as access code, password and MSISDN of first party and MSISDN of second party in a specific format pre-defined by the system. In one embodiment, the first party MSISDN and the second party MSISDN may have to be of the same network and may have to be of the same network chain. In another embodiment, the first party MSISDN and the second party MSISDN may be of different network. In this case, the first service provider and the second service provider may have to may have to come into terms, may be by using an agreement, to share user information to facilitate proposed mechanism across corresponding networks. Further, on receiving the USSD string, the system stores (502) the second party's MSISDN in a pre-defined field in the first party's account information. Further, when the system receive (503) any call to the first party's MSISDN, the system checks (504) if the first party has activated call diverting service or not. In a preferred embodiment, the system checks if the first party has activated call divert or not, by checking if a second party's MSISDN has saved in the pre-defined field in first party's account information. In another embodiment, the system may also check in the first party's account, if a flag indicating activation of call diversion is set or not, to decide whether the first party has activated call diversion or not. If the first party has not activated call diverting service, the system immediately connects (506) the call to first party's MSISDN. If the first party has activated call divert to the second party's MSISDN, the system, from the pre-defined field in the first party's account information, identifies (507) the second party MSISDN to which the call is to be diverted. Further, the system identifies (508) the location of the second party's device. Further, considering the identified location of the second party's device, the system checks (509) if the second party device is in roaming condition or not. If the second party device is found to be in roaming condition, the system divert(511) the call to the second party device 101 and charges (512) the first party as per the service provider's roaming norms. If the second party device is not in roaming conditions, the system diverts (512) the call to the second party device 101. In one embodiment, the proposed call divert mechanism facilitates activation of call divert mechanism even if the first party's MS is switched off or is not with the first party, using the second party device 101. Further, the system may provide atleast one mechanism to deactivate call diverting. Further, the call diverting may be deactivated either manually by the user or automatically by the system. For example, the user may dial a USSD string in a specific format set by the network, to deactivate the service. In another case, an automatic timer may be maintained on IN end and the system may remove the second party MSISDN from the pre-defined field in the first party's account information on expiry of the time set in the timer. The various actions in method 500 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 5 may be omitted.

[0023] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 2 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0024] The embodiment disclosed herein specifies a system for triggering one user's account through another user's account. The mechanism allows making and receiving of calls from and to a second party user's account, with charge being deducted from the first party user's account providing a system thereof. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server, MS or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof, e.g. one processor and two FPGAs. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means are at least one hardware means and/or at least one software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. The device may also include only software means. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.

[0025] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the claims as described herein.

CLAIMS

We claim:

1. A method for enabling a first party in a mobile communication network to make a call using a mobile phone of a second party, said method comprising of

Sending an Unstructured Supplementary Service Data (USSD) string by said mobile phone of said second party to said communication network;

Checking account of said first party if said first party is authorized to make said call by said communication network;

Initiating connection by said communication network between said mobile phone and a destination number, if said first party is authorized to make said call; and

Charging account of said first party for said call by said communication network.

2. The method, as claimed in claim 1, wherein said USSD string comprises of

Mobile Subscriber ISDN (Integrated Services Digital Network) Number (MSISDN) of said first party; Password of account of said first party; and Said destination number.

3. The method, as claimed in claim 1, wherein checking if said first party is authorized to make said call comprises of

Verifying said password provided by said first party by said communication network; and

Checking if account of said first party has sufficient balance for said call by said communication network.

4. The method, as claimed in claim 1, wherein said method further comprises of

checking location information of said mobile phone of said second party by said communication network; and

charging account of said first party by said communication network, depending on said location information of said mobile phone of said second party.

5. The method, as claimed in claim 1, wherein said method further comprises of displaying MSISDN of said first party as calling party to said destination number by said communication network.

6. A mobile communication network for enabling a first party to make a call using a mobile phone of a second party, said network comprising at least one means configured for

Checking account of said first party if said first party is authorized to make said call, on receiving an Unstructured Supplementary Service Data (USSD) string from said mobile phone of said second party;

Initiating connection between said mobile phone and a destination number, if said first party is authorized to make said call; and Charging account of said first party for said call.

7. The communication network, as claimed in claim 6, wherein said communication network is configured for checking if said first party is authorized to make said call by performing steps of

Verifying said password provided by said first party; and Checking if account of said first party has sufficient balance for said call.

8. The communication network, as claimed in claim 6, wherein said communication network further comprises at least one means configured for checking location information of said mobile phone of said second party; and charging account of said first party, depending on said location information of said mobile phone of said second party.

9. The communication network, as claimed in claim 6, wherein said communication network further comprises at least one means configured for displaying MSISDN of said first party as calling party to said destination number.

10. An apparatus in a mobile communication network for enabling a first party to make a call using a mobile phone of a second party, said apparatus comprising at least one means configured for

Checking account of said first party if said first party is authorized to make said call, on receiving an Unstructured Supplementary Service Data (USSD) string from said mobile phone of said second party;

Initiating connection between said mobile phone and a destination number, if said first party is authorized to make said call; and Charging account of said first party for said call.

11. The apparatus, as claimed in claim 10, wherein said apparatus is configured for checking if said first party is authorized to make said call by performing steps of

Verifying said password provided by said first party; and Checking if account of said first party has sufficient balance for said call.

12. The apparatus, as claimed in claim 10, wherein said apparatus further comprises at least one means configured for

checking location information of said mobile phone of said second party; and charging account of said first party, depending on said location information of said mobile phone of said second party.

13. The apparatus, as claimed in claim 10, wherein said apparatus further c at least one means configured for displaying MSISDN of said first party as calling party to said destination number.