CLIAMS:WE CLAIM:
1. A method for handing-off calls in a Mobile Communication Network (MCN), the method comprising:
receiving, by a Femtocell Access Point (FAP), a new connection request generated by a User Equipment (UE);
determining, by the FAP, signal strengths of neighboring nodes;
identifying, by the FAP, high-priority calls amongst a plurality of ongoing calls supported by the FAP;
preparing, by the FAP, a priority list excluding the high-priority calls; and
handing-off, by the FAP, an ongoing call of the plurality of ongoing calls to a neighboring node of the neighboring nodes based on a) the signal strengths of the neighboring nodes, and b) the priority list excluding the high-priority calls.

2. The method of claim 1, further comprising determining a priority of the new connection request.

3. The method of claim 2, wherein the handing-off of the ongoing call is further based on the priority of the new connection request.

4. The method of claim 1, wherein the handing-off of the ongoing call is further based on a call-slot available with the neighboring node.

5. The method of claim 2, wherein the priority of the new connection request is determined based on a type of call to be established corresponding to the new connection request.

6. The method of claim 5, wherein the type of call to be established comprises an audio call, a video call, a data session, an emergency call, a high-revenue call, a Quality of Service (QoS) subscribed call, a Closed User Group (CUG) call, and a Lawful Interception (LI) call.

7. The method of claim 1, wherein the signal strengths of the neighboring nodes are represented using a parameter selected from the group consisting of pilot signal strength, Received Signal Strength Indicator (RSSI), and Received Signal Code Power (RSCP).

8. The method of claim 1, wherein the signal strengths of the neighboring nodes are sorted, and wherein the signal strengths are sorted in a descending order.

9. The method of claim 1, wherein the neighboring nodes comprise neighboring Femtocell Access Points (FAPs) and neighboring Base Transceiver Stations (BTSs).

10. The method of claim 1, wherein the high-priority calls are selected from the group consisting of an audio call, a video call, a data session, an emergency call, a high-revenue call, a Quality of Service (QoS) call, a Closed User Group (CUG) call, and a Lawful Interception (LI) call.

11. A Femtocell Access Point (FAP) for handing-off calls in a Mobile Communication Network (MCN), the FAP comprises:
a processor;
a memory coupled to the processor, wherein the processor is capable for executing programmed instructions stored in the memory to:
receive a new connection request generated by a User Equipment (UE);
determine signal strengths of neighboring nodes;
identify high-priority calls amongst plurality of ongoing calls supported by the FAP;
prepare a priority list excluding the high-priority calls; and
hand-off an ongoing call of the plurality of ongoing calls to a neighboring node of the neighboring nodes based on a) the signal strengths of the neighboring nodes, and b) the priority list excluding the high-priority calls.

12. The FAP of claim 11, further comprising determining a priority of the new connection request.

13. The FAP of claim 12, wherein the handing-off of the ongoing call is further based on the priority of the new connection request.

14. The FAP of claim 11, wherein the handing-off of the ongoing call is further based on a call-slot available with the neighboring node.

15. The FAP of claim 12, wherein the priority of the new connection request is determined based on a type of call to be established corresponding to the new connection request.

16. The FAP of claim 15, wherein the type of call to be established comprises an audio call, a video call, a data session, an emergency call, a high-revenue call, a Quality of Service (QoS) subscribed call, a Closed User Group (CUG) call, and a Lawful Interception (LI) call.

17. The FAP of claim 11, wherein the signal strengths of the neighboring nodes are represented using a parameter selected from the group consisting of pilot signal strength, Received Signal Strength Indicator (RSSI), and Received Signal Code Power (RSCP).

18. The FAP of claim 11, wherein the signal strengths of the neighboring nodes are sorted, and wherein the signal strengths are sorted in a descending order.

19. The FAP of claim 11, wherein the neighboring nodes comprise neighboring Femtocell Access Points (FAPs) and neighboring Base Transceiver Stations (BTSs).

20. The FAP of claim 11, wherein the high-priority calls are selected from the group consisting of an audio call, a video call, a data session, an emergency call, a high-revenue call, a Quality of Service (QoS) call, a Closed User Group (CUG) call, and a Lawful Interception (LI) call.

21. A non-transitory computer readable medium embodying a program executable in a Femtocell Access Point (FAP) for handing-off calls in a Mobile Communication Network (MCN), the program comprising:
a program code for receiving a new connection request generated by a User Equipment (UE);
a program code for determining signal strengths of neighboring nodes;
a program code for identifying high-priority calls amongst a plurality of ongoing calls supported by the FAP;
a program code for preparing a priority list excluding the high-priority calls; and
a program code for handing-off an ongoing call of the plurality of ongoing calls to a neighboring node of the neighboring nodes based on a) the signal strengths of the neighboring nodes, and b) the priority list excluding the high-priority calls.
,TagSPECI:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003

COMPLETE SPECIFICATION
(See Section 10 and Rule 13)

Title of invention:
DYNAMIC HAND-OFF IN A MOBILE COMMUNICATION NETWORK

Applicant
Tata Consultancy Services Limited
A Company Incorporated in India under the Companies Act, 1956
Having address:
Nirmal Building, 9th Floor,
Nariman Point, Mumbai 400021,
Maharashtra, India

The following specification particularly describes the invention and the manner in which it is to be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY

[001] The present application does not claim priority from any patent application.

TECHNICAL FIELD
[002] The present subject matter described herein, in general, relates to dynamic hand-off mechanism in a mobile communication network.

BACKGROUND
[003] Macrocells created by a Base Transceiver Station (BTS) are generally ineffective at providing superior signal coverage to a User Equipment (UE) at all locations across a city. Thus, the signal strength received by the UE from the BTS may be insufficient when the UE is at locations far from the BTS. This often results in problems like network unavailability, poor voice quality during call hand-off, call drops, and poor rate of data transfer during active data sessions.
[004] In order to solve the above mentioned problem, Femtocell Access Points (FAPs) are installed at several locations which are deprived of sufficient signal strengths from coverage of the macrocells. Each of the FAPs creates a femtocell or an area based on configured access points. The FAPs register the users under coverage of the FAPs and provides access to registered users. The FAPs manage calls and data sessions for the UE’s present within coverage. When a user moves from one coverage area to another, the FAPs or the BTSs may register any succeeding user. Thus, the BTSs and the FAPs, altogether, manage the calls and the data sessions for a moving UE.
[005] The UE communicating with the FAPs save a lot of power when compared to the UE communicating with the BTSs. The FAPs are low power access points installed to save power of the UE by providing connections to the UE within smaller distances. Further, using the FAPs, through this process of data offloading there is a greater reduction of marginal costs per Gigabyte (GB) of data. It is also an ideal way for the telecom operators to save bandwidth in the macrocells.
[006] Further, the process of managing calls between the macrocells and the femtocells is already known in the art. The calls are being managed using a hand-off technique, wherein an ongoing call through an FAP or a BTS may be transferred to an adjacent FAP or to an adjacent BTS. The ongoing call is transferred based on the signal strength received by the UE from the adjacent FAP or the adjacent BTS. After a successful hand-off, the ongoing call is handled by the adjacent FAP or by the adjacent BTS to which the ongoing call is transferred. As known, each FAP has a limited call handling capacity. The limited call handling capacity of an FAP exists due to a limited number of call-slots available with the FAP.
SUMMARY
[007] This summary is provided to introduce aspects related to Femtocell Access Point (FAP) and methods for handing-off calls in a Mobile Communication Network (MCN) and the aspects are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[008] In one implementation, a method for handing-off calls in a mobile communication network (MCN) is disclosed. The method may comprise receiving a new connection request generated by a User Equipment (UE). The method may further comprise determining signal strengths of neighboring nodes. The method may comprise identifying high-priority calls amongst a plurality of ongoing calls supported by the FAP. The method may comprise preparing a priority list excluding the high-priority calls. The method may further comprise handing-off an ongoing call of the plurality of ongoing calls to a neighboring node of the neighboring nodes based on a) the signal strengths of the neighboring nodes, and b) the priority list excluding the high-priority calls.
[009] In one implementation, a Femto Access Point (FAP) for handing-off calls in a mobile communication network (MCN) is disclosed. The FAP may comprise a memory coupled to a processor for executing programmed instructions stored in the memory. The FAP may receive a new connection request generated by a User Equipment (UE). The FAP may further determine signal strengths of neighboring nodes. The FAP may further identify high-priority calls amongst a plurality of ongoing calls supported by the FAP. The FAP may further prepare a priority list excluding the high-priority calls. The FAP may further hand-off an ongoing call of the plurality of ongoing calls to a neighboring node of the neighboring nodes based on a) the signal strengths of the neighboring nodes, and b) the priority list excluding the high-priority calls.
[0010] In one implementation, a non-transitory computer readable medium embodying a program executable in a computing device for handing-off calls in a mobile communication network (MCN) is disclosed. The program may comprise a program code for receiving a new connection request generated by a User Equipment (UE). The program may further comprise a program code for determining signal strengths of neighboring nodes. The program may further comprise a program code for identifying high-priority calls amongst a plurality of ongoing calls supported by the FAP. The program may further comprise a program code for preparing a priority list excluding the high-priority calls. The program may further comprise a program code for handing-off an ongoing call of a plurality of ongoing calls running on the FAP to a neighboring node of the neighboring nodes based on a) the signal strengths of the neighboring nodes, and b) the priority list excluding the high-priority calls.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The detailed description is described with reference to the accompanying Figures. In the Figures, the left-most digit(s) of a reference number identifies the Figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.
[0012] Figure 1 illustrates a Mobile Communication Network (MCN), in accordance with an embodiment of the present subject matter.
[0013] Figure 2a, 2b and 2c jointly show a flowchart illustrating a method for handing-off calls in a Mobile Communication Network (MCN), in accordance with an embodiment of the present subject matter.
[0014] Figure 3 shows a flowchart illustrating a method for handing-off calls in a Mobile Communication Network (MCN), in accordance with an embodiment of the present subject matter.
DETAILED DESCRIPTION
[0015] Systems and methods for managing calls during hand-off between nodes present in a mobile communication network (MCN) are described. The nodes may comprise Femtocell Access Points (FAPs) and Base Transceiver Stations (BTSs). The FAPs are also known in the art as home Node B or Home eNode B.
[0016] The nodes may provide mobile network coverage to User Equipments (UEs) in order to allow the UEs to make and receive calls, use Internet, and the like. The UEs may scan for signals and may determine signal strengths received from the FAPs and the BTSs and may establish a connection with a node having maximum signal strength.
[0017] In one embodiment, the node may be a FAP. As known, the FAP may have a limited call handling capacity due to limited call-slots or ports available with the FAP. The call-slots available with the FAP may also be identified as resources, bandwidth, frequency range, time slots, channel codes, and scrambling codes pertaining to bearer channels. During a peak call traffic situation, all the call-slots of the FAP may be busy due to existing call by user occupancy and the FAP may not be able to support a new connection request. The new connection request may correspond to an incoming call, an outgoing call or a data session. However, in case a new connection request arrives at the FAP, the FAP may communicate with the UEs for identifying a neighboring node having maximum signal strength. Post determining a) a neighboring node having the maximum signal strength and b) the priority of the ongoing calls, the FAP may hand-off an ongoing call to the neighboring node in order to release a call-slot. The call-slot after being released may be used for accommodating the incoming call through the FAP. In this manner, the FAP may perform a dynamic hand-off in the MCN.
[0018] While aspects of described system and method for handing-off calls in a mobile communication network (MCN) may be implemented in any number of Femtocell Access Points (FAPs), different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system.
[0019] Referring now to Figure 1, a Mobile Communication Network (MCN) 100 is shown, in accordance with an embodiment of the present subject matter. The mobile communication network (MCN) 100 may include a plurality of nodes. The nodes may comprise a Base Transceiver Station (BTS) 102 and a Femtocell Access Point (FAP) 104. The nodes may support User Equipments (UEs) 106 for receiving and making calls, establishing data sessions, and the like. In one implementation, the UEs 106 may be connected to the FAP 104 located at a distance from the UEs 106. The nodes present around the FAP 104 may be identified as neighboring nodes 108, wherein the neighboring nodes 108 may comprise neighboring FAPs 110 and neighboring BTSs 112. The FAP 104 and the neighboring FAPs 110 may be connected to a femto gateway 114 via a broadband service 116. The femto gateway 114 may provide an access to a core network 118. The core network 118 may further be connected to Internet 120 for establishing a complete network path and hence provide services to the UEs 106.
[0020] The BTS 102 and the neighboring BTSs 112 may be connected to a Radio Network Controller (RNC) 122. The RNC 122 may support radio resources management using the BTS 102 and the neighboring BTSs 112. The RNC 122 may further be connected to the core network 118. The core network 118 may further be connected to the Internet 120 for establishing a complete network path and thus providing services to the UEs 106.
[0021] In one embodiment, the UEs 106 may scan for signals and may determine signal strengths received from FAPs (FAP 104 and neighboring FAPs 110) and BTSs (BTS 102 and neighboring BTSs 112) and may establish a connection with a node having maximum signal strength. In one example, the node having the maximum signal strength may be a FAP 104. As known, the FAP 104 may have a limited call handling capacity due to limited call-slots available with the FAP 104. During a high call traffic situation, all the call-slots of the FAP 104 may be busy and the FAP 104 may not be able to support a new connection request from the UE’s 106. The FAP 104 may accommodate the new connection request by handing-off at least one existing low priority call. In order to accommodate the new connection request, the FAP 104 may, at first, determine the call type of the new connection request. Based on the call type of the new connection request, the FAP 104 may determine a priority of the new connection request. The new connection request may correspond to a high priority call or a low priority call. Examples of high priority calls may include emergency calls, international calls, high revenue calls, Lawful Interception (LI) calls, Quality of Service (QoS) subscribed calls and the like. It may be understood that the priority of calls may be preset by an administrator in the FAP 104 while configuring the same. Further, the priority of the calls may be received from the core network.
[0022] After determining the priority of the new connection request, the FAP 104 may have to accommodate the new connection request in a call-slot. In order to accommodate the new connection request, the FAP 104 may have to vacate a call-slot occupied by an ongoing call. For vacating the call-slot, the FAP 104 may hand-off an ongoing call to a neighboring node of neighboring nodes 108. In order to hand-off the ongoing call, the FAP 104 may determine the priorities of the ongoing calls and then may hand-off an ongoing call having a least priority. The priority of the ongoing calls may be determined based upon a type of the ongoing calls. For example, if an ongoing call is one of an emergency call, an international call, a high revenue call, a Lawful Interception (LI) call, a Quality of Service (QoS) subscribed call, or the like, then the ongoing call may be identified as a high priority call. Otherwise, the ongoing call would be recognized as a low priority call. Each type of the ongoing call may be assigned a priority, as set by the administrator. The FAP 104 may preserve the ongoing call by handing-off the ongoing call to the neighboring node of the neighboring nodes 108 instead of terminating/dropping the call. Thus, the FAP 104 may increase an availability of networks to UE’s 106 by handing-off the calls in above described manner.
[0023] Post determining the priority of the new connection request and identifying the priority of the ongoing calls, the FAP 104 may determine the signal strengths of the neighboring nodes 108. The FAP 104 may determine the signal strengths received by the UEs 106 from the neighboring nodes 108 while the UEs 106 are involved in the ongoing calls supported by the FAP 104. The FAP 104 may communicate with the UEs 106 in order to determine the signal strengths of the neighboring nodes 108. The FAP 104 may identify the neighboring nodes 108 providing maximum signal strengths to the UEs 106.
[0024] Post determining a) the priority of the new connection request, b) the priority of the ongoing calls, and c) the neighboring nodes 108 providing the maximum signal strengths to the UEs 106, the FAP 104 may hand-off the ongoing call having the least priority to the neighboring node. Upon handing-off an ongoing call having least priority to the neighboring node, a call-slot may be released at the FAP 104. The call-slot after being released may be used for accommodating the new connection request of using the FAP 104. The FAP 104 may accommodate the new connection request for establishing a call corresponding to the new connection request. In this manner, the FAP 104 may hand-off the calls in the MCN 100.
[0025] In one embodiment, the FAP 104 may include processor(s) 126, a memory 128, and interface(s) 130. Further, the processor(s) 126 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) 126 is configured to fetch and execute computer-readable instructions stored in the memory 128.
[0026] The memory 128 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
[0027] The interface(s) 130 may include a variety of software and hardware interfaces, for example, a web interface, a Graphical User Interface (GUI), a Command Line Interface (CLI) and the like. The interface(s) 130 may be used for configuring the FAP 104.
[0028] In one implementation, the broadband service 116 may be implemented using a cable, a Digital Subscriber Line/Loop (DSL), and an optical fiber. The DSL connection may be implemented in different topologies depending on a required data speed and distance of implementation. The different topologies of DSL may comprise xDSL (Asynchronous Digital Subscriber Line (ADSL) and Synchronous Digital Subscriber Line (SDSL)), Integrated Services Digital Network (ISDN), ISDN Digital Subscriber Line (IDSL), High-speed Digital Subscriber Line (HDSL), and Very-high-bit-rate Digital Subscriber Line (VDSL). Further, the optical fiber may be used in several configurations depending on the distance of installation. The optical fiber may be used for implementing a Fiber To The Node/Neighborhood (FTTN), a Fiber To The Desktop (FTTD), a Fiber To The Curb/Cabinet (FTTC), a Fiber To The Home (FTTH), a Fiber To The Building (FTTB), and the like.
[0029] Further, the Mobile Communication Network (MCN) 100 may be implemented using communication standards such as IEEE 802.16 (WiMAX), 3GPP-LTE, and other standards which require an exclusive set of frequency bands and where nodes periodically send signals on each band in the exclusive set, even when no user communication is performed. For example, a communication standard may periodically communicate synchronization and control signals. These signals may be time-slotted, but they have to be transmitted on the entire frequency band, as is the case for Long Term Evolution (LTE). The invention is also understood to be applicable to various networks in which unreserved spectrum are available, as in Frequency Division Multiple Access (FDMA) deployment. The invention may be implemented using other communication standards and technologies present in the art.
[0030] The BTSs (BTS 102 and the neighboring BTSs 112) may comprise suitable logic, interfaces, circuitry, and/or code that may be operable to communicate data wirelessly utilizing one or more cellular standards such as IS-95, CDMA2000, GSM, UMTS, TD-SCDMA, extensions thereto, and/or variants thereof. The BTSs may communicate with the UEs 106. Exemplary cellular standards supported by the BTSs may be specified in the International Mobile Telecomunnications-2000 (IMT-2000) standard and/or developed by the 3rd generation partnership project (3GPP) and/or the 3rd generation partnership project 2 (3GPP2).
[0031] The FAPs (FAP 104 and the neighboring FAPs 110) may each comprise suitable logic, interfaces, circuitry, and/or code that may be operable to communicate wirelessly utilizing one or more cellular standards such as IS-95, CDMA2000, GSM, UMTS, TD-SCDMA, extensions thereto, and/or variants thereof. In this regard, the FAPs may each communicate with communication devices such as the UEs 106. Exemplary cellular standards supported by the FAPs may be specified in the International Mobile Telecomunnications-2000 (IMT-2000) standard and/or developed by the 3rd generation partnership project (3GPP) and/or the 3rd generation partnership project 2 (3GPP2). Additionally, the FAPs may each comprise suitable logic, interfaces, circuitry, and/or code that may be operable to communicate over IP capable networks.
[0032] The UEs 106 may transmit and receive data packets through one or more of the nodes to a Radio Network Controller (RNC) 122 or a Femto Gateway 114 for communicating with a core network 118 for supporting transport of voice and data packets in the MCN 100. Examples of the UEs 106 may include a mobile phone, a smart phone, a PDA, a laptop, Modem, or any other computing device.
[0033] The core network 118 may include specific carrier related servers and devices and connectivity to other networks such as a corporate intranet, the Internet, public switched telephone network (PSTN), a Serving General Packet Radio Services (GPRS) Support Node (SGSN), a Gateway GPRS Support Node (GGSN), Evolved Packet Core (EPC) and may transport voice and data packets between each UE and such networks. A UE may be any data device that communicates through a wireless channel or through a wired channel.
[0034] Referring now to Figures 2a, 2b, and 2c which jointly show a flowchart 200 illustrating a method for handing-off calls in a Mobile Communication Network (MCN) 100, in accordance with an embodiment of the present subject matter. The method 200 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 200 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.
[0035] The order in which the method 200 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 200 or alternate methods. Additionally, individual blocks may be deleted from the method 200 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 200 may be considered to be implemented as described in the FAP 104.
[0036] At block 202, a new connection request may be received. The new connection request may be initiated by a UE of the UEs 106 towards establishing a call. The new connection request may be received by the FAP 104 (shown in Figure 1) for establishing the call. At block 204, the FAP 104 may check for availability of a call slot at the FAP 104. In case of a call slot available at the FAP, at step 206, the FAP may establish a connection using the call slot. In case of unavailability of a call slot with the FAP 104, at step 208, a priority of the new connection request may be determined. The priority may be determined by the FAP 104 for the new connection request based upon a type of the new connection request. The new connection request may be of the form/type such as a local call, a video call, a conference call, an emergency call, a Lawful Interception (LI) calls, a high-revenue call, a Quality of Service (QoS) subscribed call, a call made by a user subscribed locally to the FAP 104, a data session, or the like. In one example, the new connection request may be a high priority new connection request if it is one of an emergency call or an LI call. This can be preset by the user while configuring the FAP 104.
[0037] At block 210, post determining the priority of the new connection request, the FAP 104 may receive signal strengths monitored by the User Equipments (UEs) 106. The UEs 106 may be involved in ongoing calls supported by the FAP 104. In one example, the signal strengths may be represented using a parameter selected from the group consisting of pilot signal strength, Received Signal Strength Indicator (RSSI), and Received Signal Code Power (RSCP). The UEs 106 may scan for signals available from the neighboring nodes 108.
[0038] After receiving the signal strengths, the FAP 104 may prepare a list 1 comprising ongoing calls supported by the FAP 104 at 212. The ongoing calls may be sorted in a descending order of the signal strengths of the neighboring nodes 108. At block 214, the emergency calls present in the list 1 are identified. The FAP 104 may identify the emergency calls based on the destination numbers called by the UEs 106. The FAP 104 may identify the destination number corresponding to the emergency calls like 100 for calling police, 101 for calling a fire station, and 102 for calling an ambulance. Post identifying the emergency calls, the FAP 104 may prepare a list 2 at block 216. The list 2 may exclude the emergency calls present in the list 1.
[0039] Post preparing the list 2, the FAP 104 may identify the Lawful Interception (LI) calls present in the list 2, at block 218. The LI calls are generally established by a network operator upon receiving a request from a law enforcement agency (LEA), a regulatory or administrative agency, and an intelligence service. Establishing the LI calls may involve resources like media servers, and gateways. Establishment of the LI calls upon determining availability of the resources and allocation the resources may consume a considerable amount of time. Thus, it is not suitable to drop or to hand-off the established LI calls. Thus, the FAP 104 may identify the LI calls present in the list 2 by identifying the resources involved in the LI calls. Post identifying the LI calls, the FAP 104 may prepare a list 3 at block 220. The list 3 may exclude the LI calls present in the list 2.
[0040] Subsequent to preparing the list 3, the FAP 104 may identify the high-revenue calls present in the list 3, at block 222. The high-revenue calls may comprise video calls established on a Third Generation (3G) network or a Fourth Generation (4G) network, a conference call (audio/video), and an International Subscriber Dialing (ISD) call and the like. The FAP 104 may identify the high-revenue calls present in the list 3 by identifying a country code of a calling/called number, bandwidth utilization for an established call/session, a directory number corresponding to special call services charged with high prices, and number of users involved in the calls. Further, a list 4 excluding the high-revenue calls present in the list 3 may be prepared at block 224.
[0041] Upon preparing the list 4, the FAP 104 may identify the Quality of Service (QoS) subscribed calls present in the list 4, at block 226. The FAP 104 may identify the QoS subscribed calls upon checking the subscription details of users, QCI (QoS Class Identifier) value for an ongoing session. The subscription details of the users may be stored at a Home Location Register (HLR), Visiting Location Register (VLR), Home Subscriber Server (HSS) and the like of the MCN 100. In case the subscription details of a user involved in an ongoing call is found to be present at the HLR, VLR or HSS, the call made by the user is identified as a QoS subscribed call. Further, a list 5 excluding the QoS subscribed calls present in the list 4 may be prepared at block 228.
[0042] After preparing the list 5, the FAP 104 may identify the calls made by locally subscribed users present in the list 5, at block 230. A subscriber/user registered at an Access Point (AP) may be identified as a locally subscribed user. An AP may be classified in to three categories based on a type of service provided by the AP to the users. The AP may be classified into a private AP, a public AP, or a hybrid AP. The private AP provides services to a user already registered at the private AP. The public AP provides services to both a registered user and an unregistered user. The hybrid AP may comprise a few call-slots kept reserved for providing services to the locally subscribed users (closed subscriber group) and remaining call-slots of the hybrid AP may be kept unreserved for supporting unregistered users. Thus, the FAP 104 may identify the calls corresponding to the locally subscribed users in order to provide a priority to the locally subscribed users while establishing the call. Further, at block 232, the calls made by the locally subscribed users may be excluded from the list 5 and a list 6 may be prepared. Finally, the list 6 prepared by the FAP 104 may comprise a set of low-priority calls only and may exclude all the high priority calls. The list 6 may be referred to as a priority list in further description.
[0043] At block 234, a first ongoing call may be selected from the priority list for handing-off the same to a neighboring node. Further, at block 236, a hand-off request may be sent to one or more neighboring nodes (neighboring FAPs 110 and neighboring BTSs 112) for handing-off the first call. In case the hand-off is unsuccessful, the FAP 104 may select a next call from the priority list, at 240, for handing-off the same as explained in block 236.
[0044] However, if a neighboring node having an available call-slot accepts the hand-off request transmitted by the FAP 104, the hand-off may be recognized as successful. The neighboring node may then be used for supporting the ongoing call supported by the FAP 104. After the hand-off, a call slot occupied by the ongoing call may get released. The released call slot may be used to establish a call corresponding to the new connection request at 242. Thus, in one embodiment, the FAP 104 may manage the calls between the nodes present in the MCN 100 in the above described manner. It must be understood that the FAP 104 may hand-off the calls in the MCN 100 in other manners lying within the spirit and scope of the present subject matter.
[0045] Referring now to Figure 3 which shows a flowchart 300 illustrating a method for handing-off the calls in a Mobile Communication Network (MCN) 100, in accordance with an embodiment of the present subject matter. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, etc., that perform particular functions or implement particular abstract data types. The method 300 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.
[0046] The order in which the method 300, as illustrated in Figure 3, is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 300 may be considered to be implemented on the above described Femtocell Access Point (FAP) 104.
[0047] At block 302, a new connection request may be received. The new connection request may be generated by a User Equipment (UE) of UEs 106. The new connection request may be received by the FAP 104.
[0048] At block 304, a priority of ongoing calls may be determined. The priority of the ongoing calls may be determined based on a type of the ongoing call. The type of the ongoing call may include local calls, video calls, conference calls, emergency calls, Lawful Interception (LI) calls, high-revenue calls, Quality of Service (QoS) subscribed calls, calls made by locally subscribed users, data sessions and the like. In one implementation, the priority of the ongoing call may be determined by the FAP 104.
[0049] At block 306, signal strengths of neighboring nodes 108 may be received. The FAP 104 may communicate with the UE and may receive the signal strengths of the neighboring nodes 108. The signal strengths of the neighboring nodes 108 may be represented in the form of a Received Signal Strength Indicator (RSSI).
[0050] At block 308, an ongoing call running on the FAP 104 may be hand-offed to a neighboring node of the neighboring nodes 108 based on:
a) the priority of the ongoing calls; and
b) the signal strengths of the neighboring nodes 108.
[0051] Although implementations for methods and systems for handing-off calls in the Mobile Communication Network (MCN) 100 have been described in language specific to structural features and/or methods, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for managing the calls between the nodes present in the MCN 100.