WO2012170064A1

WO2012170064A1 - Systems and methods for call handling using a group profile

Info

Publication number: WO2012170064A1
Application number: PCT/US2011/057377
Authority: WO
Inventors: Deepak SARASWAT
Original assignee: Hewlett Packard Development Co LP
Current assignee: Hewlett Packard Development Co LP
Priority date: 2011-06-08
Filing date: 2011-10-21
Publication date: 2012-12-13
Anticipated expiration: 2013-12-08

Abstract

Systems and methods for call handling in a telecommunications network using a group profile are described herein. The group profile is associated with a calling handling rule. A caller identifier is assigned to a group profile. The group profile is used for call handling of call requests.

Description

SYSTEMS AND METHODS FOR CALL HANDLING USING A GROUP PROF1L

L BACKGROUND

[0001] Service providers offer services to their customers in response to customer orders, change requests and other processes. One particular class of service providers is telecommunications service providers, which provide

telecommunication services to their customers, referred to as subscribers.

Telecommunications services currently include both wire line and wireless technologies. Examples of wire line telecommunication services include telephone service and related services such as voice mail, call forwarding, three way calling and caller identification, or cable television service and associated cable-provided services, such as internet access. Examples of wireless telecommunication services include cellular telephone service and associated services such as voice mail and three way calling, wireless electronic mail and paging.

[0002] More and more types of services are emerging on various networks.

Telecommunication networks in particular are expanding offerings of new services to retain current customers and add new service accounts.

II. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure may be better understood and its numerous features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

[0004] FIG. 1 is a topological block diagram of a telecommunications network in accordance with an embodiment.

[0005] FIG. 2 is a process flow diagram for configuration of group profiie(s) for a call handling service in accordance with an embodiment.

[0006] FIG. 3 is a process flow diagram for customized call handling in

accordance with an embodiment. [0007] FIG. 4A is a message flow diagram for configuration of a group profile in accordance with an embodiment.

[0008] FIG. 4B is a message flow diagram for call forwarding by a service provider using group profile data in accordance with an embodiment.

[0009] FIG. 4C is a message flow diagram for call handling by a mobile device using group profile data in accordance with an embodiment.

[0010] FIG, 5 illustrates a computer system in which an embodiment may be implemented.

[0011] FIG. 6 is a block diagram of an architecture of a mobile computing device in accordance with an embodiment.

III. DETAILED DESCRIPTION

[0012] One type of service that is provided by telecommunications service providers is call forwarding, which redirects all incoming calls to one telephone number to another telephone number. Call forwarding to voicemai! is one instance of a call forwarding service. In a typical communication network, a switch or other device with call control function receives a call attempt to a first phone number. The switch identifies that a call forwarding service is activated for the first phone number (i.e., called party). When activated, the switch may forward the call immediately to another phone number (e.g., voicemail system, another subscriber, etc.). Alternatively, the switch may attempt to connect the call to the first phone number, and subsequently forward the call to the other number if the call attempt to the first phone number has not been completed, e.g., called party does not answer the call, line is busy, or there is no answer for the duration of the service provider's call timeout period (e.g., four rings).

[0013] Typically, call forwarding rules are applied to all incoming calls when the calls are not completed. There is not much flexibility with respect to tailoring how call handling, including call forwarding, is applied. For example, users may keep their mobile phones on vibration mode, meeting mode, or in driving mode as per their preferences and convenience. However, these settings may make it difficult for a caller to reach the mobile phone user in a timely manner, especially under urgent conditions. Moreover, the caller is unaware of the user's status.

[0014] A service for providing customized call handling is described herein. The service may be provided by service providers and/or by a device with telephonic capabilities (e.g., mobile phone, fixed-line phone, IP phone, etc.). Systems and methods for call handling in a telecommunications network using a group profile are described herein. A call request is received and a caller identifier (SD) is

determined. A look-up is performed in a data storage that includes a mapping of a plurality of group profiles to a plurality of caller identifiers. Each group profile includes a call handling rule, and at least one caller identifier is assigned as a member of a first group profile of the plurality of group profiles. A matching group profile is identified, and a call handling rule that correlates with the matching group profile is executed.

[0015] FIG, 1 is a topological block diagram of a telecommunications network 100 in accordance with an embodiment. The telecommunications network 100 is described according to the general infrastructure and nomenclature of the Global System for Mobile Communications (GSM) standards although embodiments are not limited to application in such systems, and description thereof is for illustrative purposes. Network 100 includes a mobile network 105, a Public Switched

Telephone Network (PSTN) 107, and internet 109.

[0016] Mobile network 105 includes an originating switch 1 16, destination switch 1 14, a business support system (BSS) 140, a media platform 1 18, and a router 130, ail of which are operatively interconnected and the connection among them may include multiple network segments, transmission technologies and

components.

[0017] Originating switch 1 16 is configured to route data in location 106B of mobile network 105 and manage the communication between mobile devices and PSTN 107. Destination switch 1 14 is configured to route data, for example to a called party of mobile network 105, and manage the communication between mobile devices and PSTN 107. In a GSM mobile network, originating switch 1 16 and destination switch 1 14 may be Mobile Switching Centers (MSCs). As shown, originating switch 1 16 and destination switch 1 14 service different switching system locations in mobile network 105. Originating switch 1 16 services a location 106B and destination switch 1 14 services location 106A. Sn another embodiment, originating switch 1 16 and destination switch 1 14 are the same device, for example where a caller using mobile device 40 and a called party are both serviced by the same location, e.g., either location 106A or location 106B.

[0018] Mobile computing device 40 is a device with telephonic functionality.

Mobile computing device 40 may be a mobile telephone, a personal digital assistant, a handheld computer, or other mobile computing device. Mobile computing device 40 is operatively coupled to mobile network 105, via a base station and a switch, such as destination switch 1 14, and is configured to exchange electronic messages (e.g. voice and data) and other information with mobile network 105. Moreover, mobile computing device 40 includes a call handling module 41 that is configured to configure group profiles for the call handling service and to perform customized call handling as configured, for example, according to call handling rules. Call handling module 41 is also configured to store configured call handling rules, and to maintain a table that correlates a user's contact with a group profile to which the contact is assigned. For example, the contact is an entry in a user's address book of mobile computing device 40.

[0019] Media platform 1 18 is configured to deliver and manage mobile voice and data services. Media platform 1 18 includes backend server 122, profile

management service module 124, and a group profile registry 125, all of which are operatively interconnected and the connection among them may include multiple network segments, transmission technologies and components.

[0020] Backend server 122 generally is configured to enable services within mobile network 105. Profile management service module 124 is configured to enroll a subscriber with a call handling service and manage the subscriber-defined group profiles and corresponding actions (e.g., customized call forwarding). Profile management service module 124 is shown as being implemented as a standalone module, but may be implemented on a single server, such as backend server 122 or by multiple servers. Each such server is programmed with machine readable instructions, and may include at least one processor for executing these

instructions stored in a machine readable memory.

[0021] Group profile registry 125 is a data store configured to store group profiles and corresponding rules as defined by subscribers who have been enrolled for the call handling sea'iee. Specifically, group profile registry 125 includes a mapping of subscriber-defined user groups and one or more rules that are executed as a part of the call handling service. As used herein, a call handling rule is comprised of a condition and an action that is executed when the condition is fulfilled. In particular, the condition of any call handling rule is one that checks for membership of a caller in a group profile.

[0022] In one embodiment, the group profile registry 125 stores call handling rules that are executed by the service provider. In other words, the group profile registry 125 may not include rules that are executed by mobile device 40 or other device with telephony capabilities. The group profile registry 125 also maintains a table that correlates a subscriber's contact with a group profile to which the contact is assigned.

[0023] Call controller module 1 15 of destination switch 1 14 is configured to determine whether a called party is enrolled in the call handling service, identify a group profile to which a caller is bound, and execute one or more call handling rules associated with the identified group profile.

[0024] Router 130 is generally configured to process and transfer data in network 100. Router 130 is an edge device on the edge of a network, such as mobile network 105. As used herein, an edge device is a network switch, router, or other network device on the edge of a network.

[0025] Business support systems (BSS) 140 is configured to support various end- to-end services including billing, charging, and settlement. Typically, services are enforced by a charging policy. As such, the call handling service is enforced according to a corresponding charging policy. In one embodiment, a subscriber who has enrolled in the call handling service may be charged for the cost of network usage. For example, where an incoming call was forwarded by destination switch 1 14 to another phone number, the cost of airtime usage once the forwarded call was complete may be attributed to the subscriber and may not be charged to the caller's own allocations and/or charges.

[0026] In operation, a telecommunication service provider and/or a device with telephonic capabilities (e.g. mobile device) may offer a call handling service for its subscribers or users, respectfully. The call handling service may include various call handling rules, each of which are executed by either the device or the service provider. For example, rules executed by a mobile device include sending a Short Message Service (SMS) message to a specified telephone number when the caller is a member of a particular group, outputting a ringtone that was specified for a group profile to which the caller is a member, or other rules with actions involving mobile phone-related functions. Rules performed by a service provider include rules with actions involving call forwarding or other functions associated with a service provider.

[0027] Configuration of the call handling service may be performed at mobile computing device 40. During configuration, various group profiles and associated rules are established. For example, a "family" group profile is defined and one or more rules (including a condition and an action) are associated with that group. The condition may be membership in the "family" group profile. The actions include sending an SMS message to the caller and forwarding the call to another phone number, such as the subscriber's home phone number.

[0028] In one embodiment, one triggering condition for all rules is determination of either a missed call (by a mobile phone) or an incomplete call (by a service provider). As used herein, a missed call is a telephone call that is not answered by its intended recipient prior to the expiration of the call attempt. The triggering condition prompts the execution of the rule. For example, when a missed call is determined by mobile computing device 40, an action of the rule is executed if the rule condition (e.g., caller is a member of the "family" group profile) is satisfied.

[0029] In one embodiment, the mobile device may execute one or more of these rules in the "family" group profile as described above. For example, a mobile device rule specifies generating and sending an SMS message which provides notification to the caller of the user's status (e.g., mobile phone is in meeting mode or driving mode). In operation, an incoming call is received by the mobile device from a caller who is assigned to the "family" group profile. The call is typically attempted by the service provider via destination switch 1 14 for the duration of a service provider's time out period. If the user of the mobile device does not answer the call, the mobile device determines that the call was missed, and this triggers the mobile device to transmit the SMS message to the caller.

[0030] Furthermore, the service provider may execute one or more of the associated rules in the "family" group profile as described above. Typically, a switch of the service provider may perform call forwarding (e.g., to a voicemail system) when the cali has not been completed. As described herein, call controller module 1 15 of destination switch 1 14 may perform call forwarding as specified for the user-defined group profile where the subscriber has enrolled in the call handling service. For example, the service provider rule specifies forwarding a call to the subscriber's home phone number. Sn operation, an incoming cali from a caller who is assigned to the "family" group profile is missed by mobile device 40. Destination switch 1 14 detects an incomplete cali which triggers destination switch 1 14 to forward the call to the subscriber's home phone number, as specified in the "family" group profile.

[0031] Depending on the actions that are specified for a particular group profile, the service provider or the mobile device may fulfill the call handling service. In another embodiment, both the service provider and the mobile device execute actions to collectively provide the call handling service.

[0032] In one embodiment, a subscriber is enrolled for the call handling service offered by the service provider. Enrollment may be initiated by the subscriber via an enrollment request. The enrollment request specifies a phone number associated with the subscriber and may be provided using voice service (via a mobile device or iandline), Short Message Service (SMS), Multimedia Messaging Service (MMS), or through a call handling module on the phone device (e.g., device 40), etc.

[0033] Where the enrollment request is provided via a mobile device (e.g., a voice call using mobile voice service), the incoming call is sent to profile management service module 124 via an Interactive Voice Response Server (IVRS) for processing. The enrollment request may be provided to a sub-module of profile management service module 124 that handles enrollment for subscribers.

[0034] Where the enrollment request is provided via a land line (e.g., subscriber calls the telecommunications service provider using a land line), the enrollment request is received by router 130 through PSTN 107, and is forwarded to profile management service module 124 via an !VRS. The enrollment request may be provided to a sub-module of profile management service module 124 that handles enrollment for subscribers. In another embodiment, PSTN 107 includes a profile management service module which is similar in functionality to profile management service 124 and as such, the enrollment request is received by a switch and forwarded to the profile management service module, all within PSTN 107. The switch within PSTN 107 may include a call controller module similar in functionality to call controller module 1 15.

[0035] Where the enrollment request is provided via the internet (e.g., subscriber accesses a telecommunications service provider's website), the enrollment request is received by router 130 through internet 109, and is forwarded to profile management service module 124 via backend server 122. Likewise, the enrollment request may be provided to a sub-module of profile management service module 124 that handles registration for subscribers. In one embodiment, the enrollment is subscription-based, such as with other services, and may be discontinued or extended as desired.

[0038] Enrollment with the service provider may not be conducted where the actions associated with a group profile are executed solely by the device, such as mobile device 40.

[0037] Embodiments can also be applied in other network topologies and environments. Telecommunications network 100 may be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, network 100 can be a local area network (LAN), such as an Ethernet network, a Token-Ring network and/or the like; a wide-area network; a virtual network, including without limitation a virtual private network (VPN); the Internet; an intranet; an extranet; a public switched telephone network (PSTN); an infra-red network; a wireless network (e.g., a network operating under any of the IEEE 802.1 1 suite of protocols, the Bluetooth protocol in the art, and/or any other wireless protocol); and/or any combination of these and/or other networks.

[0038] FIG, 2 is a process flow diagram for configuration of group profiie(s) for a call handling service in accordance with an embodiment. The depicted process flow 200 may be carried out by execution of sequences of executable instructions. In another embodiment, various portions of the process flow 200 are carried out by components of a device with telephonic functionality, telecommunication media platform, a switch in a telecommunications network, an arrangement of hardware logic, e.g., an Application-Specific Integrated Circuit (ASIC), etc. For example, blocks of process flow 200 may be performed by execution of sequences of executable instructions in a call handling module of the device and/or a profile management service module 124 of a mobile service provider.

[0039] A call handling service for providing customized handling of incoming calls is implemented in a telecommunications network. To initiate the call handling service, group profiles are configured. A group profile includes a group name and a call handling rule. At step 210, a group name is determined, for example by the device or by a telecommunication media platform in a telecommunications network.

[0040] At step 220, one or more call handling rules are associated with the group name of the group profile. Together, the group name and associated rules comprise a group profile. The call handling rules are the attributes of the group profile. Each call handling rule specifies a group membership condition and an action that is performed. By using groups, call handling rules may be defined for a class of callers, rather than for all callers. The actions may include sending a session-less (e.g., SMS, Multimedia Messaging Service (MMS) including instant messaging (I ), etc.) message, beginning a session-based (push-to-talk) communication, sending an e-mail message, forwarding the call to voicemail or to another entity or phone number, providing a ringtone associated with the group name to the called party, etc.

[0041] At step 230, a contact is assigned to one of the group profiles. For example, a contact is an entry in a users address book of the mobile device or other database. Each contact entry includes fields, such as first name, last name, email address, phone number, etc. As described herein, a contact further includes a group profile field, which specifies membership of that contact to a particular group profile. The membership assignment may be made, for example, by the user of the device. Where configuration of the group profiles is performed via the service provider, the membership assignment is stored in a data store that is operatively coupled to the service provider. Where the configuration is performed via the user's device (e.g., mobile device), the membership assignment is stored on the device or in a data store that is operatively coupled to the device.

[0042] As previously mentioned, the actions in the call handling rules may be performed by the device (e.g., mobile device) or the service provider. This distinction is made at step 235, where it is determined whether the action in the call handling rule is performed by another entity. For example, where the configuration is performed via the user's device, the mobile device determines whether any of the call handling rules include actions that are not executed by the mobile device itself, and instead, are executed by another entity (e.g., the service provider).

[0043] Actions in the call handling rule that are performed by the device include sending a session-less (e.g., SMS, MMS including IM, etc.) message, beginning a session-based (push-to-talk) communication, sending an e-mail message, priority calling or invoking a conference call among the users of the same group, etc.

Actions in the call handling rule that are performed by the service provider includes call forwarding (e.g., to voicemail, to another phone number or entity, etc.), call- blocking, location based services, and other services that are provided by service providers.

[0044] Where the action in the call handling rule is not performed by another entity, a flag is set for the call handling rule at step 240, indicating that the action in the call handling rule is one that is executed by the entity that performs the configuration. Continuing with the previous example, a set flag indicates that the action in the call handling rule should be executed by the mobile device itself.

[0045] On the other hand, where the action in the call handling rule is performed by another entity, a synchronization request is sent at step 250. The

synchronization request includes data about the group profile, including a subset of the associated call handling rules. The subset includes those rules that are determined to be performed by the other entity. For example, the synchronization request includes rules that are executed by the service provider and does not include those rules that are executed by the mobile device, if the configuration is performed on the mobile device.

[0046] Configuration is complete when the synchronization request is sent to the other entity and confirmation of the synchronization is received. The

synchronization request is received by the other entity and is used to create and/or update group profile records therewith. Furthermore, additional synchronization requests may be triggered in order to maintain data coherency between the entities (e.g., between the mobile device and service provider). For example, a

modification to the group profiles or to a subscriber's contact with a group profile even after the configuration stage may trigger the generation of another

synchronization request. In another embodiment, the synchronization requests are generated at a defined time interval or upon a user-initiated request.

[0047] Additional Embodiments

[0048] As previously described, a group profile may be created for a "family" group profile. In one embodiment, the "family" group profile is configured with a call forwarding action to the voicemail of the intended recipient and an SMS action, which sends to the caller an SMS message including the status of the intended recipient. In this case, if the intended recipient does not answer an incoming call made by a caller who belongs to the "family" group profile, the call is automatically forwarded to voicemail and an SMS message (including status information of the intended recipient) is sent to the caller, as specified in the "family" group profile.

[0049] A "business" group profile may be created such that calls from any business clients in a user's contacts list are handled in a similar manner. Sn one embodiment, the "business" group profile is configured with a call forwarding action to the office land line number of the intended recipient. If the intended recipient does not answer an incoming call made by a caller who belongs to the "business" group profile, the call is automatically handled as specified in the "business" group profile, thereby improving the reachability of the intended recipient.

[0050] A "default" group profile may be created such that calls from any source which are unknown or are known contacts but not assigned to a particular group profile are handled in a similar manner. In one embodiment, the "default" group profile is configured with a call forwarding action to voicemail, and without SMS notifications. If the intended recipient does not answer an incoming call made by a caller who belongs to the "default" group profile, the call is automatically handled as specified.

[0051] FIG, 3 is a process flow diagram for customized call handling in

accordance with an embodiment. The depicted process flow 300 may be carried out by execution of sequences of executable instructions. In another embodiment, various portions of the process flow 300 are carried out by components of a device with telephonic functionality, telecommunication media platform, a switch in a telecommunications network, an arrangement of hardware logic, e.g., an

Application-Specific Integrated Circuit (ASIC), etc. For example, blocks of process flow 300 may be performed by execution of sequences of executable instructions in a call handling module of the device, a destination switch in the

telecommunications network and/or a media platform in the telecommunications network.

[0052] A call handling service for providing customized handling of incoming calls is implemented in a telecommunications network. The call handling service may be activated after configuration, as described with respect to FIG. 2. At step 310, an incoming call is received, for example at a mobile device. In a mobile

telecommunications network, such as the Global System for Mobile

communications (GSM), a call to a mobile device is called a mobile terminated call. The incoming call is sent to a Mobile Switching Center (MSG) that services the geographic area at which the mobile device is located, in particular, an incoming request for setting up a mobile terminated call is directed to the MSG, The MSG routes the call to the MSG that is currently able to reach the called mobile subscriber. The device of the called mobile subscriber is then paged in its current location area.

[0053] The identification data of the caller is determined at step 315. Typically, the caller's number is provided to the called party during a call attempt.

[0054] At step 325, it is determined whether the caller is assigned to a group profile. For example, a look-up is performed in an address book of the mobile device or other data store that includes a listing of the contacts. The identification data (e.g., caller ID) of the incoming call is used as a key to perform the lookup. If the group profile field of the matching contact entry identifies a group profile, it is determined that the caller is an assigned member of the group profile. If the caller is not assigned to a group profile, normal call routing is performed, at step 330.

[0055] The call handling rules specified for the identified group profile are determined. At step 340, a call handling rule of the group profile to which the caller is assigned is executed. The call handling rule is located, for example, by searching a data store that includes a listing of the configured group profiles. As previously described, an action in a call handling rule may be executed by a device (e.g., mobile device). Another action may be executed by a service provider (e.g., destination switch, media platform, etc.).

[0056] For example, the mobile device may receive the incoming call and execute an action in a call handling rule that is flagged, or otherwise indicated as an action that should be performed by the mobile device. In other words, it is determined whether the mobile device is responsible for executing the action. The mobile device may execute the action of the rule after detecting that the incoming call was missed.

[0057] In another embodiment, the incoming call is received by the destination switch. As used herein, the destination switch is a device that is responsible for routing calls to a served party. The incoming call may have been forwarded to the destination switch from the originating switch. [0058] Upon receiving the incoming call, the destination switch determines whether the dialed telephone number is enrolled in the call handling service.

During enrollment, a data store, such as a profile registry, is populated with the group profiles, including the associated call handling rules. The data store also includes a correlation of a subscribers contact and an identification of the group profile to which that contact has been assigned. Furthermore, a Home Location Register (HLR) or Home Subscriber Server (HSS) in the telecommunication network is updated to reflect that the subscriber has enrolled in the call handling service. To determine whether the dialed telephone number is enrolled, a search is performed for the dialed telephone number in a list of subscription services stored in the HLR or HSS.

[0059] if enrolled, the destination switch (e.g., destination MSG) may execute an action in a call handling rule that is flagged, or otherwise indicated as an action that should be performed by the destination switch. In other words, it is determined whether the service provider is responsible for executing the action. The call handling rule is determined by searching the profile registry. The destination switch may execute on the rule after detecting that the incoming call was not completed or the timeout period has lapsed.

[0060] If the entity assigned to the dialed number is has not enrolled in the call handling service, normal call routing is performed.

[0061] As described, the call handling service provides an improved call handling experience for a caller, for example, when a call is unanswered by the called party. Furthermore, where the service is implemented solely by the called party's mobile device, a subscription with the service provider is not needed and as such no additional fees are incurred.

[0062] FIG. 4A is a message flow diagram for configuration of a group profile in accordance with an embodiment. In this example, a user employs a mobile device 401 to initiate the configuration of a group profile for the call management service. The mobile device 401 determines that at least one call handling rule includes an action that is executed by mobile device 401 . Ail group profile data, including call handling rules are stored on mobile device 401 or in a data store that is operativeiy coupled to mobile device 401 . Rules that are determined to be executed by mobile device 401 are flagged.

[0063] Furthermore, mobile device 401 determines that at least one call handling rule includes an action that is not executed by mobile device 401 , but rather, is executed by a service provider, As such, mobile device 401 sends a

synchronization request 415 to the mobile telecommunications network via a base station and originating switch 1 16.

[0064] The synchronization request 415 is handled by originating switch 1 18, which then forwards synchronization request 415 to a profile management service module 124 of the service providers media platform. Upon receiving

synchronization request 415, profile management service module 124 determines whether the caller ID associated with synchronization request 415 is enrolled in the call handling service. If enrolled, synchronization request 415 is processed. In one embodiment, synchronization request 415 includes data about a group profile, including a subset of the associated call handling rules, as defined by the subscriber (e.g., user of mobile device 401 ). The subset includes those rules that are executed by the service provider and does not include those rules that are executed by mobile device 401 . The group profile data also includes a mapping of a subscriber's contact with one of the group profiles.

[0065] The group profile data is extracted from synchronization request 415 and is used to generate an update request 419. The update request 419 includes group profile data that has not been synchronized with the service-related data

represented by the service provider. The update request 419 is sent to a group profile registry 125, which then provides a status message 420 when the update has been accomplished. For example, the group profile data may be used to create and/or update group profile records in group profile registry 125. In one embodiment, profile management service module 124 provides a confirmation message 422 to indicate the data synchronization is complete.

[0066] FIG, 4B is a message flow diagram for call forwarding by a service provider using group profile data in accordance with an embodiment. Continuing with the example as described in FIG 4A, a caller, using mobile device 451 , initiates a call to the mobile device 401 , which previously configured a group profile for the call management service. In one embodiment, the group profile is associated with call handling rules that are executed by the service provider. The call is initiated when the user of mobile device 451 dials a phone number. The mobile device 451 sends a call setup request message 424 to the mobile telecommunications network via a base station and an originating switch 464.

[0087] The call setup request message 424 is handled by originating switch 464, which checks whether the incoming call is allowed by referencing a subscriber record in a location register (e.g., Home Location Register, Visiting Location Register) of the service provider.

[0068] If allowed, originating switch 1 16 forwards a call establishment request 426 to destination switch 1 14. Upon receiving the call establishment request 426, destination switch 1 14 identifies that the call handling service is activated for the dialed phone number (e.g., called party), determines the caller identification (ID) of the incoming call, and generates a group profile request 428, which is used to determine whether the caller is associated with a group profile. The group profile request 428 may be in the format of any signaling protocol, such as Signaling System Number 7 (SS7) and Session Initiation Protocol (SIP), among others. The group profile request 428, which includes the extracted caller ID, is transmitted to call management service module 124 of the service provider's media platform.

[0069] Call management service module 124 generates a match query 430 which includes the caller ID and transmits the match query 430 to group profile registry 125. The match query 430 may be in the format of any signaling protocol, such as Signaling System Number 7 (SS7) and Session Initiation Protocol (SIP), among others. Group profile registry 125 obtains from the received match query 430 the caller SD and performs a lookup using the caller ID as a key. As previously described, group profile registry 125 includes group profiles and corresponding rules as defined by subscribers who have been enrolled for the call handling service. The group profile registry 125 also maintains a table that correlates a subscriber's contact with a group profile to which the subscriber is assigned. [0070] Call management service module 124 receives a match response 432, which is used to determine whether the caller is associated with a group profile. If the caller is associated with a group profile, the match response 432 includes a call forwarding phone number that was specified for the group profile to which the caller was assigned. In this example, the group profile specified that calls received from callers in the "family" group profile be forwarded to a phone number of call forwarding device 454.

[0071] No further service-related messages are sent if match response 432 indicates a match was unsuccessful (i.e., caller is not associated with a group profile). Furthermore, if there is no match, the call is routed through typical methods using a call establishment request to mobile device 401 . On the other hand, if match response 432 indicates a positive match (i.e., the caller is associated with a group profile), call management service module 124 provides to destination switch 1 14 a response message 434 that includes the specified call forwarding number.

[0072] Destination switch 1 14 attempts to connect the call by forwarding the call establishment request 428 to mobile device 401 (i.e., called party). If the call attempt to mobile device 401 has not been completed (e.g., called party does not answer the call, no answer for the duration of the service provider's call timeout period, etc.), destination switch 1 14 forwards the call immediately to the specified call forwarding phone number by sending call establishment request 426 to call forwarding device 454. As such, customized call forwarding is implemented using group profile data.

[0073] FIG. 4C is a message flow diagram for call handling by a mobile device using group profile data in accordance with an embodiment. Continuing with the example as described in FSG 4A, a caller, using mobile device 451 , initiates a call to the mobile device 401 , which previously configured a group profile for the call management service. In one embodiment, the group profile is associated with call handling rules that are executed by mobile device 401 . The call is initiated when the user of mobile device 451 dials a phone number. The mobile device 451 sends a call setup request message 424 to the mobile telecommunications network via a base station and originating switch 464.

[0074] The call setup request message 424 is handled by originating switch 464, which checks whether the incoming call is allowed by referencing a subscriber record in a location register (e.g., Home Location Register, Visiting Location Register) of the service provider.

[0075] If allowed, originating switch 1 16 forwards a call establishment request 428 to destination switch 1 14. Upon receiving the call establishment request 428, destination switch 1 14 forwards call establishment request 426 to mobile device 401 (i.e., called party). The call is attempted until it has been completed or there is no answer for the duration of the service provider's call timeout period.

[0076] Mobile device 401 obtains a caller ID, which is used to determine whether the caller is associated with a group profile. In particular, mobile device 401 performs a lookup in its own data store using the caller ID as a key. The data store includes group profiles and corresponding rules as defined by the user of mobile device 401 . The data store also maintains a table that correlates a user's contact with a group profile to which the contact is assigned. If there is no match, the call is handled through typical methods. On the other hand, if there is a match (i.e., the caller is associated with a group profile), a call handling rule that was specified for the group profile to which the caller is assigned is determined.

[0077] When mobile device 401 determines that the incoming call was missed, the specified call handling rule is executed, if flagged. Sn this context, flagged rules indicate that the action associated with the rule is one that should be executed by the mobile device and not by the service provider. In this example, the flagged rule specifies that an SMS message is provided to the caller. As such, mobile device 401 generates an SMS message 440 that notifies the caller of the status of the called party when the missed call was detected. For example, SMS message 440 may indicate that mobile device 401 was in meeting mode. The status information may be determined, for example, by interfacing with a phone module that manages the phone profiles. The SMS message 440 is sent to caller mobile device 451 . As such, customized call handling is implemented using group profile data. [0078] It should be recognized that the processes described with respect to FIG. 4B and FIG. 4C may occur in parallel.

[0079] FIG. 5 illustrates a computer system in which an embodiment may be implemented. The system 500 may be used to implement any of the computer systems described above. The computer system 500 is shown comprising hardware elements that may be electrically coupled via a bus 524. The hardware elements may include at least one central processing unit (CPU) 502, at least one input device 504, and at least one output device 506. The computer system 500 may also include at least one storage device 508. By way of example, the storage device 508 can include devices such as disk drives, optical storage devices, solid- state storage device such as a random access memory ("RAM") and/or a read-only memory ("ROM"), which can be programmable, fiash-updateable and/or the like.

[0080] The computer system 500 may additionally include a computer-readable storage media reader 512, a communications system 514 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.), and working memory 518, which may include RAM and ROM devices as described above. In some embodiments, the computer system 500 may also include a processing acceleration unit 518, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.

[0081] The computer-readable storage media reader 512 can further be connected to a computer-readable storage medium 510, together (and in combination with storage device 508 in one embodiment) comprehensively representing remote, local, fixed, and/or removable storage devices plus any- tangible non-transitory storage media, for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information (e.g., instructions and data). Computer-readable storage medium 510 may be non- transitory such as hardware storage devices (e.g., RAM, ROM, EPROM (erasable programmable ROM), EEPROM (electrically erasable programmable ROM), hard drives, and flash memory). The communications system 514 may permit data to be exchanged with the network and/or any other computer described above with respect to the system 500. Computer-readable storage medium 510 includes a call management service module 525, which may be a call controller module or a user profile management service module.

[0082] The computer system 500 may also comprise software elements, which are machine readable instructions, shown as being currently located within a working memory 518, including an operating system 520 and/or other code 522, such as an application program (which may be a client application, Web browser, mid-tier application, etc.). It should be appreciated that alternate embodiments of a computer system 500 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.

[0083] The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense, it will, however, be evident that various modifications and changes may be made.

[0084] Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Thus, unless expressly stated otherwise, each feature disclosed is one example of a generic series of equivalent or similar features.

[0085] FIG. 6 is a block diagram of an architecture of a mobile computing device 801 , which is shown as, but not limited to, a device with telephonic functionality, in accordance with an embodiment. Mobile computing device 601 may be a mobile telephone, a personal digital assistant, a handheld computer, or other mobile computing device.

[0086] Mobile computing device 601 includes a central processor 620, a power supply 640, and a radio subsystem 650.

[0087] The central processor 620 is configured for operation with a computer operating system 620a. The operating system is an interface between hardware and an application, with which a user typically interfaces. The operating system is responsible for the management and coordination of activities and the sharing of resources of the mobile computing device 801 . The operating system provides a host environment for applications that are run on the mobile computing device 601 . As a host, one of the purposes of an operating system is to handle the details of the operation of the mobile computing device 601 . Examples of an operating system (OS") include PALM OS and PALM WEB08, MICROSOFT WINDOWS (including WINDOWS 7, WINDOWS CE, and WINDOWS MOBILE), SYMBIAN OS, RIM BLACKBERRY OS, APPLE OS (including MAC OS and IPHONE OS), GOOGLE OS (CHROME or ANDROID), and LINUX.

[0088] The central processor 620 communicates with an audio system 610, camera 612, flash memory 614, RAM 616, a short range radio module 618 (e.g., Bluetooth, and Wireless Fidelity (WiFi) component (e.g., IEEE 802.1 1 )). The central processor 620 communicatively couples these various components or modules through a data line (or bus) 678. The power supply 640 powers central processor 820, radio subsystem 650 and a display driver 830 (which may be contact or inductive-sensitive). The power supply 640 may correspond to a direct current source (e.g., a battery pack, including rechargeable) or an alternating current (AC) source. The power supply 840 powers the various components through a power line (or bus) 679.

[0089] The central processor 820 communicates with applications executing within mobile computing device 601 through the operating system 620a. In addition, intermediary components, for example, a window manager module 622 and a screen manager module 828, provide additional communication channels between the central processor 620 and operating system 620 and system components, for example, the display driver 630.

[0090] In one embodiment, the window manager 622 comprises a software or firmware module that includes instructions that initialize a virtual display space stored in the RAM 816 and/or the flash memory 614. The screen manager 626 comprises a software or firmware module that includes instructions that manages content displayed on a screen of mobile computing device 601 . [0091] A call handling module 628 comprises software that includes machine readable instructions that are, for example, integrated with the operating system or configured to be an application operational with the operating system. In some embodiments call handling module 628 may comprise firmware, for example, stored in the flash memory 614. The call handling module 628 is configured to configure group profiles for a call handling service. The call handling module 628 is further configured to determine whether a caller of an incoming call is associated with a group profile, and if so, execute one or more call handling rules specified for a group profile to which the initiator of the incoming call is assigned.

[0092] It is noted that call handling module 628 is configured to interface with applications, such as, but not limited to, contact lists, calendars, task lists, notepads, calculator applications, spreadsheets, games, ringtone settings, and a phone application or messaging application. In turn, these applications may interface with the radio subsystem, for example, to receive incoming telephone calls, incoming short message service (SMS), and electronic mail messages.

[0093] In one embodiment, central processor 620 executes logic (e.g., by way of programming, code, or instructions) corresponding to executing applications. It is noted that numerous other components and variations are possible to the hardware architecture of the mobile computing device 601 , thus an embodiment such as shown by FIG. 6 is illustrative of one implementation for an embodiment.

[0094] Radio subsystem 650 includes a transceiver 664. Transceiver 664 may be two separate components for transmitting and receiving signals or a single component for both transmitting and receiving signals. In either instance, it is referenced as transceiver 664. The receiver portion of the transceiver 664 communicatively couples with a radio signal input of device 601 , e.g., an antenna, where communication signals are received from an established call (e.g., a connected or on-going call). The received communication signals include voice (or other sound signals) received from the call and processed by the radio processor 660. The transmitter portion of the transceiver 664 communicatively couples a radio signal output of device 601 , e.g., the antenna, where communication signals are transmitted to an established (e.g., a connected or active) call. [0095] In one embodiment, communications using the described radio

communications may be over a voice or data network. Examples of voice networks include Global System of Mobile (GSM) communication system, a Code Division, Multiple Access (CDMA system), and a Universal Mobile Telecommunications System (UMTS). Examples of data networks include General Packet Radio Service (GPRS), third-generation (3G) mobile (or greater), High Speed Download Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), and Worldwide Interoperability for Microwave Access (WiMAX).

[0096] While other components may be provided with the radio subsystem 650, the basic components shown provide the ability for the mobile computing device to perform radio-frequency communications, including telephonic communications. A radio processor may communicate with central processor 820 using the data line (or bus) 678.

[0097] The card interface 624 is adapted to communicate, wirelessiy or wired, with external accessories (or peripherals), for example, media cards inserted into the expansion slot (not shown). The card interface 624 transmits data and/or instructions between central processor 620 and an accessory, e.g., an expansion card or media card, coupled within the expansion slot. The card interface 624 also transmits control signals from central processor 620 to the expansion slot to configure the accessory. It is noted that the card interface 624 is described with respect to an expansion card or media card; it also may be structurally configured to couple with other types of devices external to device 601 , for example, an inductive charging station for the power supply 640 or a printing device.

Claims

WHAT IS CLAIMED IS:

1 . A method for call handling in a telecommunications network, the method comprising:

receiving, by a device of the telecommunications network, a call request; determining a caller identifier from the call request;

performing a look-up in a data storage using the caller identifier as an index, wherein the data storage includes a mapping of a plurality of group profiles to a plurality of caller identifiers, wherein each group profile includes a call handling rule, and wherein at least one caller identifier of the plurality of caller identifiers is assigned as a member of a first group profile of the plurality of group profiles;

identifying a matching group profile of the plurality of group profiles based on the look-up; and

executing a call handling rule that correlates with the matching group profile.

2. The method of claim 1 , wherein executing the call handling rule further comprises:

determining an action associated with the call handling rule that correlates with the matching group profile;

determining whether the mobile device is responsible for executing the action; and

executing the action by the mobile device.

3. The method of claim 1 , wherein executing the call handling rule further comprises:

determining whether a service provider of the telecommunications network is responsible for executing the action; and

executing the action by the service provider.

4. The method of claim 1 , wherein the call handling rule is executed upon detection of a triggering condition.

5. The method of claim 4, wherein the triggering condition is detecting the call request was not answered.

8. A method for configuring a call handling service in a

telecommunications network, the method comprising:

determining, by a mobile phone device of the telecommunications network, a group name of a group profile;

associating a call handling rule with the group profile, wherein the call handling rule includes a condition and an action that is executed upon fulfillment of the condition;

assigning a caller identifier of a plurality of caller identifiers in the mobile phone device to the group profile; and

determining whether the mobile device is responsible for executing the action, wherein the group profile is used for call handling call requests from the caller identifier.

7. The method of claim 6, wherein the mobile device is responsible for executing the action, further comprising:

flagging the call handling rule.

8. The method of claim 6, wherein the mobile device is not responsible for executing the action, further comprising:

generating a synchronization request, wherein the synchronization request includes the group name of the group profile, the associated call handling rule, and the caller identifier; and

transmitting the synchronization request to a service provider in the telecommunications network.

9. The method of claim 8, further comprising receiving a confirmation message indicating an update to a data storage of the service provider was performed to include a mapping of the group profile to the caller identifier,

10. The method of claim 6, further comprising associating the call handling rule with a second action, wherein the mobile device is responsible for executing the action and is not responsible for executing the second action.

1 1 . A non-transitory computer-readable medium storing a plurality of instructions to control a data processor, the plurality of instructions comprising

instructions that cause the data processor to:

receive a call request;

determine a caller identifier from the call request;

perform a look-up in a data storage using the caller identifier as an index, wherein the data storage includes a mapping of a plurality of group profiles to a plurality of caller identifiers, wherein each group profile includes a call handling rule, and wherein at least one caller identifier of the plurality of caller identifiers is assigned as a member of a first group profile of the plurality of group profiles;

identify a matching group profile of the plurality of group profiles based on the look-up; and

execute a call handling rule that correlates with the matching group profile.

12. The non-transitory computer-readable medium of claim 1 1 , wherein the instructions that cause the data processor to execute the call handling rule comprise instructions that cause the data processor to:

determine an action associated with the call handling rule that correlates with the matching group profile;

determine whether the mobile device is responsible for executing the action; and

execute the action by the mobile device.

13. The non-transitory computer-readable medium of claim 1 1 , wherein the instructions that cause the data processor to execute the call handling rule comprise instructions that cause the data processor to:

determine whether a service provider of the telecommunications network is responsible for executing the action; and

execute the action by the service provider,

14. The non-transitory computer-readable medium of claim 11 , wherein the call handling rule is executed upon detection of a triggering condition.

15. The non-transitory computer-readable medium of claim 14, wherein the triggering condition is detecting the call request was not answered.