WO2019027559A1

WO2019027559A1 - Location-based call policy

Info

Publication number: WO2019027559A1
Application number: PCT/US2018/035518
Authority: WO
Inventors: Amer Aref Hassan; Russell Andrew PENAR; Rich Clive IRELAND
Original assignee: Microsoft Technology Licensing, Llc
Priority date: 2017-08-04
Filing date: 2018-06-01
Publication date: 2019-02-07

Abstract

Techniques for a location-based call policy are described. In one or more implementations, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from establishing calls with one or more restricted recipients. Next, it is determined whether the client device is at a registered location of the communication client. If it is determined that that client device is at the registered location, the call policy is applied to enable the communication client to establish calls with the one or more restricted recipients. Alternately, if it is determined that the client device is not at the registered location, the call policy is applied to continue to restrict the communication client from establishing calls with the one or more restricted recipients.

Description

LOCATION-BASED CALL POLICY

BACKGROUND

[0001] Conventional communication clients configured to communicate over a network are associated with a static registered location. For example, a business communication client may be associated with a registered location that is mapped to an address of the business. In this case, if an emergency call is initiated using the communication client, the emergency call will be routed to an emergency dispatcher or service, such as a public safety answering point, along with location information corresponding to the registered location of the communication client. This causes emergency services to be dispatched to the registered location of the communication client.

[0002] However, in the event that the communication client is installed on a mobile client device, then the user may utilize the communication client at various locations other than the registered location of the communication client. For example, the user may utilize the communication client while working at home, at a coffee shop, and so forth. In this scenario, if an emergency call is initiated using the communication client from a location outside of the registered location of the communication client, the emergency services will be dispatched to the registered location even though the user is not currently at the registered location. The incorrect routing of emergency services increases the likelihood that the user will be unable to obtain the needed emergency services, while also wasting the time and resources of the emergency services which are dispatched to the wrong location.

SUMMARY

[0003] Techniques for a location-based call policy are described. In one or more implementations, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from establishing calls with one or more restricted recipients. Next, it is determined whether the client device is at a registered location of the communication client. If it is determined that the client device is at the registered location, the call policy is applied to enable the communication client to establish calls with the one or more restricted recipients. Alternately, if it is determined that the client device is not at the registered location, the call policy is applied to continue to restrict the communication client from establishing calls with the one or more restricted recipients.

[0004] In one or more implementations, a client device includes a policy manager configured to determine whether the client device is at a registered location associated with a communication client implemented by the client device. If it is determined that the client device is not at the registered location, the policy manager applies a call policy to restrict the communication client from establishing calls with the one or more restricted recipients. Alternately, if it is determined that the client device is at the registered location, the policy manager applies the call policy to enable the communication client to establish calls with the one or more restricted recipients.

[0005] In one or more implementations, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from placing an emergency call. Next, it is determined whether the client device is at a registered location of the communication client. If it is determined that the client device is at the registered location, then the call policy is applied to enable the communication client to place the emergency call. Alternately, if it is determined that the client device is not at the registered location, then the call policy is applied to continue to restrict the communication client from placing the emergency call.

[0006] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] 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 use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.

[0008] FIG. 1 is an illustration of an environment in an example implementation that is operable to employ techniques for location-based call policy described herein.

[0009] FIG. 2 depicts an example implementation scenario for techniques for location- based call policy in accordance with one or more implementations.

[0010] FIG. 3 depicts an additional example implementation scenario for techniques for location-based call policy in accordance with one or more implementations.

[0011] FIG. 4 depicts an additional example implementation scenario for techniques for location-based call policy in accordance with one or more implementations.

[0012] FIG. 5 is a flow diagram that describes steps in a method for location-based call policy in accordance with one or more implementations. [0013] FIG. 6 is a flow diagram that describes steps in an additional method for location- based call policy in accordance with one or more implementations.

[0014] FIG. 7 is a flow diagram that describes steps in an additional method for location- based call policy in accordance with one or more implementations.

[0015] FIG. 8 illustrates an example system and computing device as described with reference to FIG. 1, which are configured to implement various aspects of the techniques described herein.

DETAILED DESCRIPTION

[0016] Techniques for location-based call policy are described. In various implementations, a call policy associated with a communication client restricts calling to one or more numbers or recipients if the client device is not at a registered location, such as a registered business address of the communication client. For example, the call policy can be applied to restrict emergency calling if the client device is not at the registered business location, while enabling the emergency calling if the client device is at the registered business location. In some cases, the restriction of emergency calling may include display of an indicator that indicates that the emergency calling is disabled and/or notifies the user to use a different communication means (e.g., the users smartphone) to place an emergency call. Thus, unlike conventional solutions in which an emergency call initiated by a communication client outside of a registered location causes emergency services to be dispatched to the wrong location, the described techniques prevent emergency calling when the communication client is outside of the registered location. Doing so reduces instances in which the time and resources of emergency services are wasted by responding to the wrong location.

[0017] The call policy may include restrictions on calling other than just emergency calling. For example, the call policy can be configured to restrict calls to recipients associated with special or premium numbers that are only to be called from a certain location, such as a hospital, a government office, or a business. For instance, the call policy can restrict calls to various business contacts when the client device is not at the registered location (e.g., an office of the business) for legal and/or security reasons. Doing so leads to increased security for such calls over an unreliable network while also preventing sensitive information from being overheard by others if the user places the call in a public location such as a coffee shop. In some instances, the call policy is associated with a group policy that can be pushed out to employees of a company or agency by an administrator. In this way, organizations and businesses can control the ways in which the communication client can be used when in the office environment versus when outside of the office environment.

[0018] In one or more implementations, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from establishing calls with one or more restricted recipients. Next, it is determined whether the client device is at a registered location of the communication client. If it is determined that that client device is at the registered location, the call policy is applied to enable the communication client to establish calls with the one or more restricted recipients. Alternately, if it is determined that the client device is not at the registered location, the call policy is applied to continue to restrict the communication client from establishing calls with the one or more restricted recipients.

[0019] In one or more implementations, a client device includes a policy manager configured to determine whether the client device is at a registered location associated with a communication client implemented by the client device. If it is determined that the client device is not at the registered location, the policy manager applies a call policy to restrict the communication client from establishing calls with the one or more restricted recipients. Alternately, if it is determined that the client device is at the registered location, the policy manager applies the call policy to enable the communication client to establish calls with the one or more restricted recipients.

[0020] In one or more implementations, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from placing an emergency call. Next, it is determined whether the client device is at a registered location of the communication client. If it is determined that the client device is at the registered location, then the call policy is applied to enable the communication client to place the emergency call. Alternately, if it is determined that the client device is not at the registered location, then the call policy is applied to continue to restrict the communication client from placing the emergency call.

[0021] FIG. 1 is an illustration of an environment 100 in an example implementation that is operable to employ techniques for location-based call policy described herein. The environment 100 includes a communication network 102 ("network 102"), which is representative of different connected components that exchange, process, and/or route data to enable different forms of communication. Examples of the network 102 include a local access network (LAN), wide area network (WAN), the Internet, a wireless cellular communication network, a Public Switched Telephone Network (PSTN), an Internet of Things (IoT) network, and combinations thereof. The network 102, for instance, represents a combination of interconnected wireless and wired networks that enable communication at various geographic locations and via a variety of different communication modalities.

[0022] Connected to the network 102 is a client device 104, which is representative of an end-user device configured to communicate via the network 102. The client device 104 may be configured in a variety of ways, such as a wireless cellular phone (e.g., a smartphone), a tablet, a laptop, and so forth. One example implementation of the client device 104 is presented below as the computing device 802 of FIG. 8.

[0023] The client device 104 includes a communication client 106, which is representative of functionality to enable different forms of communication via the client device 104. Examples of the communication client 106 include a voice communication application (e.g., a Voice over Internet Protocol (VoIP) client), a video communication application, a messaging application, a content sharing application, and combinations thereof. The communication client 106, for instance, enables different communication modalities to be combined to provide diverse communication scenarios. In at least some implementations, the communication client 106 represents an application that is installed on the client device 104. Additionally or alternatively, the communication client 106 can be implemented all or in part as a remote application, such as accessed via a web browser, a web application, and so forth.

[0024] According to various implementations, the communication client 106 is configured to enable various types of communication via interaction with a communication service 108. For example, the communication client 106 and the communication service 108 may enable communication of "over-the-top" content (OTT). The communication service 108 is representative of a service to perform various tasks for management of communication between the client device 104 and other recipients 111, e.g., other client devices. The communication service 108, for instance, can manage initiation, moderation, and termination of communication sessions for the client device 104. Examples of the communication service 108 include a VoIP service, an online conferencing service, a unified communications and collaboration (UC&C) service, and so forth. In at least some implementations, the communication service 108 may be implemented as and/or be connected to a private branch exchange (PBX) in communication with a Public Switched Telephone Network ("PSTN") to enable voice communication between the client device 104 and other devices and/or services. The client device 104 further includes a communication module 110 which is representative of functionality for enabling the client device 104 to communicate data to various recipients 111 via wired and/or wireless connectivity to the network 102.

[0025] In various implementations, the communication client 106 is configured to enable emergency calling by enabling communication of an emergency call to a recipient 1 11 corresponding to an emergency dispatcher or emergency service, such as a public safety answering point 112 via interaction with the communication service 108. Public safety answering point 112 (sometimes called a "public safety access point"), is a call center responsible for answering calls to an emergency telephone number for police, firefighting, and ambulance services, such as when the user dials "911". Trained telephone operators are also usually responsible for dispatching these emergency services by routing the call to the appropriate emergency service such that the emergency services are dispatched.

[0026] In one or more implementations, the communication client 106 is associated with a user profile 114, which represents a way of authenticating a particular user with the communication client 106 and the communication service 108, and for tracking user- specific authentication information (e.g., username, password, and so forth), user settings, contacts, and other data for the user. In at least some implementations, the user profile 114 is portable such that the user can authenticate with a different instance of the communication client 106, and make calls via the different instance of the communication client 106 that are identified as being connected with the user profile 114.

[0027] The user profile 114 may include a registered location 116 of the communication client 106, such as a registered address of the communication client 106. For example, the user may provide a registered address to the communication client 106 during a registration process to activate the communication client 106. In one or more implementations, the communication client 106 corresponds to a business communication client, in which case the registered location 116 may correspond to a business address. In other instances, however, the registered location 116 may correspond to an address other than a business address, such as an address of the user's home.

[0028] Environment 100 further includes a location module 118 which is representative of functionality for receiving, transmitting, and/or processing location information. The location module 118, for instance, supports transmission, reception, and processing of position information according to a variety of different technologies, such as Global Positioning System (GPS), cellular communication, WiFi™, satellite communication, radio frequency (RF) communication, subnet information, Ethernet switch and/or port data, Internet Protocol (IP) address information, and so forth.

[0029] According to various implementations, the location module 118 can communicate with a position information system 120 to obtain position information for the client device 104. The position information system 120 is representative of various types of position information systems that can transmit and/or receive position information. Examples of the position information system 120 include GPS satellites, cellular telephone networks, wireless data (e.g., WiFi™) networks, location information services (LIS), radio frequency identifier (RFID) functionality, subnets of wired networks, Ethernet switches and/or ports, and so forth. In this example, the location module 118 can be implemented at the communication service 108 and/or at the client device 104, or as a remote third party service.

[0030] In one or more implementations, client device 104 further includes a call policy 122 that is managed and applied by a policy manager 124. Alternately or additionally, the call policy 122 and/or policy manager 124 can be implemented at the communication service 108. The call policy 122 provides various rules or restrictions that can be applied to the communication client 106 based on whether or not the client device is at the registered location 116. In one or more implementations, the policy manager 124 communicates with the location module 118 to determine the current location of the client device 104, and then applies the call policy 122 in order to restrict calls to one or more recipients 111 if the client device 104 is not currently located at the registered location 116. As an example, the policy manager 124 can apply call policy 122 to disable or restrict emergency calling (e.g., calls to public safety answering point 112) if the client device 104 is not currently located at the registered location 116. Doing so prevents emergency services from being dispatched to an incorrect location in cases where emergency calls are placed outside of the registered location 116. In one or more implementations, policy manager 124 is implemented as a component of communication client 106 and/or communication service 108. Alternately, policy manager 124 can be implemented as an infrastructure component of client device 104 that is not affiliated or associated with the communication client, such as an "Entitlement Component". In these implementations, the policy manager 124 may be configured to apply the call policy 122 to restrict calling by the communication client 106, as well as other communication means of the client device 104, such as calls over a mobile network or calls initiated using a different communication client.

[0031] In one or more implementations, call policy 122 is a group policy that is managed by an administrator of a group (e.g., a business or organization) of communication clients. The group policy enables rule-based enforcement of a group of communication clients 106 associated with the group. In this scenario, the group policy can be updated by the administrator and pushed out to different communication clients 106 of the group. In some cases, different members of the group may have different group policies. For example, the group policy may allow a certain subset of employees of a business to access certain share point material, while a different subset of employees is blocked.

[0032] While the techniques herein will be described in terms of restricting calling, it is to be appreciated that the techniques may be applied to restrict voice and video calling, as well as other types of communication sessions, such as email or other text-based messaging.

[0033] Having described an example environment in which the techniques described herein may operate, consider now a discussion of some example implementation scenarios for location-based call policy in accordance with one or more implementations.

[0034] The following section describes example implementation scenarios for emergency calling. The implementation scenarios may be implemented in the environment 100 discussed above, the system 800 described below, and/or any other suitable environment.

[0035] FIG. 2 depicts an example implementation scenario 200 for techniques for location-based call policy in accordance with one or more implementations. While the scenario 200 is illustrated as being implemented in the environment 100 introduced above, it is to be appreciated that various aspects of the scenario 200 may be in any other suitable environment.

[0036] In scenario 200, location module 118 communicates with position information system 120 to obtain position information 202 for the client device 104. The position information system 120 is representative of various types of position information systems that can transmit and/or receive position information. Examples of the position information system 120 include GPS satellites, cellular telephone networks, wireless data (e.g., WiFi™) networks, location information services (LIS), radio frequency identifier (RFID) functionality, subnets of wired networks, Ethernet switches and/or ports, and so forth. As discussed throughout, the location module 118 can be implemented at client device 104, and/or at the communication service 108, or as a remote third party service.

[0037] The location module 118 is configured to determine a current location 204 of the client device 104 based on the position information 202 received from the position information system 120. The current location 204 of the client device 104 can be determined by the location module 118 based on a variety of different types of position information 202 received from position information system 120. The location module 118, for instance, supports transmission, reception, and processing of position information according to a variety of different technologies, such as Global Positioning System (GPS), cellular communication, WiFi™, satellite communication, radio frequency (RF) communication, subnet information, Ethernet switch and/or port data, Internet Protocol (IP) address information, and so forth.

[0038] In one or more implementations, the location module 118 may be further configured to generate a reliability metric 206 indicating a reliability or accuracy of the determine current location 204 of client device 104. For example, based on the position information 202 received from the position information system 120, the location module 118 can determine a reliability of the determined current location 204. In cases where the current location is based on GPS data, the reliability metric 206 may indicate a high reliability or accuracy of the current location 204. In other cases, the location module 118 may be able to determine that the client device 104 is not currently at the registered location 116, but may be unable to determine an accurate current location 204. In this case, the reliability metric 206 may indicate a low reliability or accuracy of the current location 204.

[0039] FIG. 3 depicts an additional example implementation scenario 300 for location- based call policy in accordance with one or more implementations. While the scenario 300 is illustrated as being implemented in the environment 100 introduced above, it is to be appreciated that various aspects of the scenario 300 may be in any other suitable environment.

[0040] In scenario 300, a communication client 106 implemented at a client device 104 is executed, such as when the client device 104 first powers on or when user input is received to launch the communication client 106. At 302, in response to execution of the communication client 106, policy manager 124 applies call policy 122 to the communication client 106 in order to restrict calling to one or more restricted recipients 304 identified in the call policy 122. Alternately, rather than applying the call policy when the communication client is executed, the call policy can be applied when the user initiates a call, such as when the user dials an emergency phone number (e.g., "911") into a user interface of the communication client 106 or selects an emergency call control. In one or more implementations, applying the call policy further causes display of one or more indicators to indicate that calls to the one or more restricted recipients is restricted or disabled.

[0041] In one or more implementations, the restricted recipient corresponds to an emergency dispatcher, such as public safety answering point 112. Alternately or additionally, the call policy can be configured to restrict calling to various business contacts when the client device is not at the registered location (e.g., an office of the business). This can lead to increased security for such calls over an unreliable network while also preventing sensitive information from being overheard by others if the user places the call in a public location such as a coffee shop.

[0042] At 306, policy manager 124 determines whether the client device is currently located at the registered location 116 of the communication client 106. As discussed above, the registered location 116 of the communication client 106 generally represents a registered address of the communication client 106. For example, the user may provide a registered address to the communication client 106 in order to activate the communication client. In one or more implementations, the communication client 106 corresponds to a business communication client, in which case the registered location 116 may correspond to a business address. In other instances, however, the registered location 116 may correspond to an address other than a business address, such as an address of the user's home.

[0043] In order to determine whether the client device is at the registered location 116, policy manager 124 can query location module 118 to determine the current location 204 of the client device 104, and compare the current location 204 of the client device 104 to the registered location 116 of the communication client 106. If the current location 204 is different than the registered location 116, then the policy manager 124 determines that the client device 104 is not at the registered location 116. Alternately, if the current location 204 matches the registered location 116, then the policy manager 124 determines that the client device 104 is at the registered location 116.

[0044] In some cases, the policy manager 124 can determine that the client device 104 is at the registered location 116 based on a current network connection of the client device. For example, the registered location 116 may include an associated network. A registered business location, for instance, may include a business network that can only be connected to if the client device 104 is currently at the business location. As such, the policy manager 124 can determine that the client device 104 is at the registered location 116 if the client device is connected to a network associated with the registered location 116, and determine that the client device is not at the registered location if the client device 104 is not connected to the network associated with the registered location 116.

[0045] At 308, in response to determining that the client device 104 is currently at the registered location 116, the policy manager 124 applies the call policy to enable the communication client to establish calls with the one or more restricted recipients 304. In other words, the policy manager 124 removes the restriction on calling the restricted recipients such that the user can establish calls with the restricted recipients 304 using the communication client 106. As used herein, "placing a call", "making a call", "calling", "establishing a call", can refer to dialing out from the client device 104 and/or receiving a call at the client device 104 dialed from a different device.

[0046] Alternately, at 310, in response to determining that the client device 104 is not at the current location 204, the policy manger 124 applies the call policy 122 to restrict the communication client 106 from establishing calls with the one or more restricted recipients 304. Notably, in cases where the call policy restricts calls to the restricted recipients 304 as a default configuration when the communication client 106 is executed, then the policy manger 124 continues to enforce the call policy 122 in which calls to the one or more restricted recipients 304 are restricted. Doing so means that in cases where the policy manager 124 is unable to determine whether or not the user is at the registered location 116, that the policy manager 124 will still enforce the call policy 122 until it can be reliably determined that the user is at the registered location 116.

[0047] In one or more implementations, the call policy 122 is configured to restrict emergency calling if the client device 104 is not at the registered location 116. As an example, consider FIG. 4 which depicts an additional example implementation scenario 400 for location-based call policy in accordance with one or more implementations. While the scenario 400 is illustrated as being implemented in the environment 100 introduced above, it is to be appreciated that various aspects of the scenario 400 may be in any other suitable environment.

[0048] In scenario 400, a communication client 106 implemented at a client device 104 is executed, such as when the client device 104 first powers on or when user input is received to launch the communication client 106. At 402, in response to execution of the communication client 106, policy manager 124 applies call policy 122 to restrict the communication client 106 from placing an emergency call 404. In one or more implementations, policy manager 124 restricts the communication client 106 from placing an emergency call 404 by disabling all emergency calls using communication client 106. For example, policy manager 124 can disable emergency calling such that the communication client 106 is unable to place an emergency call.

[0049] In one or more implementations, policy manager 124 may be further configured to restrict emergency calling by causing display of one or more indicators which indicate emergency calling is disabled. For example, policy manager 124 can "gray out" or remove an emergency call icon that can be selected to place an emergency call. As another example, policy manager 124 can cause display of a user interface element that indicates that "Emergency Calling is Disabled". In this way, the user is notified that emergency calling is disabled, and can choose to use a different communication method in order to place an emergency call, such as by placing the call over a mobile network using a smart phone.

[0050] At 406, policy manager 124 determines whether the client device is currently located at the registered location 116 of the communication client 106. As discussed above, the registered location 116 of the communication client 106 generally represents a registered address of the communication client 106. For example, the user may provide a registered address to the communication client 106 in order to activate the communication client. In one or more implementations, the communication client 106 corresponds to a business communication client, in which case the registered location 116 may correspond to a business address. In other instances, however, the registered location 116 may correspond to an address other than a business address, such as an address of the user's home.

[0051] In order to determine whether the client device is at the registered location 116, policy manager 124 can query location module 118 to determine the current location 204 of the client device 104, and compare the current location 204 of the client device 104 to the registered location 116 of the communication client 106. If the current location 204 is different than the registered location 116, then the policy manager 124 determines that the client device 104 is not at the registered location 116. Alternately, if the current location 204 matches the registered location 116, then the policy manager 124 determines that the client device 104 is at the registered location 116.

[0052] In some cases, the policy manager 124 can determine that the client device 104 is at the registered location 116 based on a current network connection of the client device. For example, the registered location 116 may include an associated network. A registered business location, for instance, may include a business network that can only be connected to if the client device 104 is currently at the business location. As such, the policy manager 124 can determine that the client device 104 is at the registered location 116 if the client device is connected to a network associated with the registered location 116, and determine that the client device is not at the registered location if the client device 104 is not connected to the network associated with the registered location 116.

[0053] At 408, in response to determining that the client device 104 is currently at the registered location 116, the policy manager 124 enables emergency calling in accordance with the call policy 122. In other words, the policy manager 124 removes the restriction on placing emergency calls such that the user is able to use to the communication client 106 to place an emergency call. [0054] Client device 104 can then establish the emergency call, such as by communicating data of the emergency call to the communication service 108 via network 102. The communication service 108 receives the data of the emergency call 302 from client device 104 via network 102, and identifies the call as corresponding to an emergency call, and then forwards the data of the emergency call to the public safety answering point 112. The public safety answering point 112 can then dispatch emergency services (e.g., police services, fire- fighting services, or ambulance services) to registered location 116 without concern as to whether or not the user is currently at the registered location. Doing so prevents the emergency services from being dispatched to the wrong location.

[0055] Alternately, at 410, in response to determining that the client device 104 is not at the current location 204, the policy manger 124 restricts emergency calling 304. Notably, in cases where the call policy restricts emergency calling as a default configuration, then the policy manger 124 continues to enforce the call policy 122 which restricts emergency calling.

[0056] Having discussed various example implementation scenarios, consider now some example procedures in accordance with one or more implementations.

[0057] The following discussion describes some example procedures for location-based call policy in accordance with one or more implementations. The example procedures may be employed in the environment 100 of FIG. 1, the system 800 of FIG. 8, and/or any other suitable environment. The procedures, for instance, represent example procedures for implementation of the scenarios described above. In at least some implementations, the steps described for the various procedures can be implemented automatically and independent of user interaction.

[0058] FIG. 5 is a flow diagram that describes steps in a method 500 for location-based call policy in accordance with one or more implementations. In one or more implementations the method 500 describes steps implemented by a communication client, such as communication client 106 at a client device 104, and/or by a communication service, such as communication service 108.

[0059] At 502, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from establishing calls with one or more restricted recipients. For example, in response to execution of communication client 106 implemented at client device 104, policy manager 124 applies a call policy 122 to restrict communication client 106 from establishing calls with one or more restricted recipients 304. In one or more implementations, the restricted recipient corresponds to an emergency dispatcher, such as public safety answering point 112.

[0060] At 504, it is determined whether the client device is at a registered location of the communication client. For example, policy manager 124 determines whether the client device 104 is currently located at a registered location 116 of the communication client 106. In order to determine whether the client device is at the registered location 116, policy manager 124 can query location module 118 to determine the current location 204 of the client device 104, and compare the current location 204 of the client device 104 to the registered location 116 of the communication client 106. If the current location 204 is different than the registered location 116, then the policy manager 124 determines that the client device 104 is not at the registered location 116. Alternately, if the current location 204 matches the registered location 116, then the policy manager 124 determines that the client device 104 is at the registered location 116.

[0061] At 506, responsive to determining that the client device is at the registered location, the call policy is applied to enable the communication client to establish calls with the one or more restricted recipients. For example, in response to determining that the client device 104 is currently at the registered location 116, the policy manager 124 applies the call policy to enable the communication client 106 to establish calls with the one or more restricted recipients 304. In other words, the policy manager 124 removes the restriction on calling the restricted recipients such that the user can establish calls with the restricted recipients 304 using the communication client 106.

[0062] Alternately, at 508, responsive to determining that the client device is not at the registered location, the call policy is applied to restrict the communication client from establishing calls with the one or more restricted recipients. For example, in response to determining that the client device 104 is not at the current location 204, the policy manger 124 applies the call policy 122 to restrict the communication client 106 from establishing calls with the one or more restricted recipients 304. Notably, in cases where the call policy restricts calls to the restricted recipients 304 as a default configuration, then the policy manger 124 continues to enforce the call policy 122 in which calls to the one or more restricted recipients 304 are restricted.

[0063] FIG. 6 is a flow diagram that describes steps in a method 600 for location-based call policy in accordance with one or more implementations. In one or more implementations the method 600 describes steps implemented by a communication client, such as communication client 106 at a client device 104, and/or by a communication service, such as communication service 108. [0064] At 602, in response to execution of a communication client implemented at a client device, a call policy is applied to restrict the communication client from placing an emergency call. For example, in response to execution of communication client 106 implemented at client device 104, policy manager 124 applies a call policy 122 to restrict communication client 106 from placing an emergency call 404.

[0065] In one or more implementations, policy manager 124 restricts the communication client 106 from placing an emergency call 404 by disabling all emergency calls using communication client 106. For example, policy manager 124 can disable emergency calling such that the communication client 106 is unable to place an emergency call. In one or more implementations, policy manager 124 may be further configured to disable emergency calling by causing display of an indication that emergency calling is disabled. For example, policy manager 124 can "gray out" or remove an emergency call icon that can be selected to place an emergency call. As another example, policy manager 124 can cause display of a user interface element that indicates that "Emergency Calling is Disabled". In this way, the user is notified that emergency calling is disabled, and can choose to use a different communication method in order to place an emergency call, such as by placing the call over a mobile network using a smart phone

[0066] At 604, it is determined whether the client device is at a registered location of the communication client. For example, policy manager 124 determines whether the client device 104 is currently located at a registered location 116 of the communication client 106. In order to determine whether the client device is at the registered location 116, policy manager 124 can query location module 118 to determine the current location 204 of the client device 104, and compare the current location 204 of the client device 104 to the registered location 116 of the communication client 106. If the current location 204 is different than the registered location 116, then the policy manager 124 determines that the client device 104 is not at the registered location 116. Alternately, if the current location 204 matches the registered location 116, then the policy manager 124 determines that the client device 104 is at the registered location 116.

[0067] At 606, responsive to determining that the client device is at the registered location, the call policy is applied to enable the communication client to place the emergency call. For example, in response to determining that the client device 104 is currently at the registered location 116, the policy manager 124 applies the call policy to enable the communication client 106 to place emergency call 404.

[0068] Alternately, at 608, responsive to determining that the client device is not at the registered location, the call policy is applied to restrict the communication client from placing the emergency call. For example, in response to determining that the client device 104 is not at the current location 204, the policy manger 124 applies the call policy 122 to restrict the communication client 106 from placing the emergency call 404.

[0069] FIG. 7 is a flow diagram that describes steps in a method 700 for location-based call policy in accordance with one or more implementations. In one or more implementations the method 700 describes steps implemented by policy manager 124 when configured as an infrastructure component, such as an entitlement component. The infrastructure component can be implemented by a client device, such as client device 104, and/or by a communication service, such as communication service 108.

[0070] At 702, user input is received, at a client device, to place a call. For example, user input to place a call is received at a client device 104. In some cases, the user input corresponds to user input to place an emergency call, such as when the user dials "911".

[0071] At 704, an infrastructure component applies a call policy that restricts or allows the call based on a user profile of the user placing the call. For example, an infrastructure component, such as an entitlement component, can restrict or allow the call based on a user profile 104 of the user placing the call.

[0072] In some cases, the user profile includes a registered location of a communication client that is utilized to place the call. For example, user profile 114 can include registered location 116. The infrastructure component can be implemented to restrict the call if the client device is not currently located at the registered location 116, or allow the call if the client device 104 is currently located at the registered location 116. In one or more implementations, the call policy is applied to restrict the call if the client device is not at the registered location and the call corresponds to an emergency call. In one or more implementations, the call policy corresponds to group policy that includes one or more rules to restrict or allow the call based on the user profile and the number dialed.

[0073] The infrastructure component can determine whether the client device is at the registered location in a variety of different ways. In some cases, a current location 204 of the client device is passed to the infrastructure component along with data of the call when the call is placed. Alternately, in response to the call being placed, the infrastructure component can query location module 118 for the current location 204. Then, the infrastructure component compares the current location 204 of the client device to the registered location 116. If the current location 204 is different than the registered location 116, then the infrastructure component determines that the client device 104 is not at the registered location 116. Alternately, if the current location 204 matches the registered location 116, then the policy manager 124 determines that the client device 104 is at the registered location 116.

[0074] FIG. 8 illustrates an example system generally at 800 that includes an example computing device 802 that is representative of one or more computing systems and/or devices that may implement various techniques described herein. For example, the client device 104 discussed above with reference to FIG. 1 can be embodied as the computing device 802. The computing device 802 may be, for example, a server of a service provider, a device associated with the client (e.g., a client device), an on-chip system, and/or any other suitable computing device, apparatus, and/or computing system.

[0075] The example computing device 802 as illustrated includes a processing system 804, one or more computer-readable media 806, and one or more I/O Interfaces 808 that are communicatively coupled, one to another. Although not shown, the computing device 802 may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.

[0076] The processing system 804 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 804 is illustrated as including hardware element 810 that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 810 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.

[0077] The computer-readable media 806 is illustrated as including memory/storage 812. The memory/storage 812 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage 812 may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage 812 may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media 806 may be configured in a variety of other ways as further described below.

[0078] Input/output interface(s) 808 are representative of functionality to allow a user to enter commands and information to computing device 802, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for implementing voice and/or spoken input), a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to detect movement that does not involve touch as gestures), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device 802 may be configured in a variety of ways as further described below to support user interaction.

[0079] Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms "module," "functionality," and "component" as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

[0080] An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 802. By way of example, and not limitation, computer-readable media may include "computer-readable storage media" and "computer-readable signal media."

[0081] "Computer-readable storage media" may refer to media and/or devices that enable persistent storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Computer-readable storage media do not include signals per se. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer- readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.

[0082] "Computer-readable signal media" may refer to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device 802, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.

[0083] As previously described, hardware elements 810 and computer-readable media 806 are representative of instructions, modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein. Hardware elements may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware devices. In this context, a hardware element may operate as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element as well as a hardware device utilized to store instructions for execution, e.g., the computer-readable storage media described previously.

[0084] Combinations of the foregoing may also be employed to implement various techniques and modules described herein. Accordingly, software, hardware, or program modules and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements 810. The computing device 802 may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of modules as a module that is executable by the computing device 802 as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements 810 of the processing system. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 802 and/or processing systems 804) to implement techniques, modules, and examples described herein.

[0085] As further illustrated in FIG. 8, the example system 800 enables ubiquitous environments for a seamless user experience when running applications on a personal computer (PC), a television device, and/or a mobile device. Services and applications run substantially similar in all three environments for a common user experience when transitioning from one device to the next while utilizing an application, playing a video game, watching a video, and so on.

[0086] In the example system 800, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one embodiment, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.

[0087] In one implementation, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one embodiment, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.

[0088] In various implementations, the computing device 802 may assume a variety of different configurations, such as for computer 814, mobile 816, and television 818 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 802 may be configured according to one or more of the different device classes. For instance, the computing device 802 may be implemented as the computer 814 class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.

[0089] The computing device 802 may also be implemented as the mobile 816 class of device that includes mobile devices, such as a mobile phone, wearable device, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device 802 may also be implemented as the television 818 class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on.

[0090] The techniques described herein may be supported by these various configurations of the computing device 802 and are not limited to the specific examples of the techniques described herein. For example, functionalities discussed with reference to the client device 104, communication client 106, location module 118, and/or policy manager 124 may be implemented all or in part through use of a distributed system, such as over a "cloud" 820 via a platform 822 as described below.

[0091] The cloud 820 includes and/or is representative of a platform 822 for resources 824. The platform 822 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 820. The resources 824 may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device 802. Resources 824 can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi™ network.

[0092] The platform 822 may abstract resources and functions to connect the computing device 802 with other computing devices. The platform 822 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources 824 that are implemented via the platform 822. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system 800. For example, the functionality may be implemented in part on the computing device 802 as well as via the platform 822 that abstracts the functionality of the cloud 820.

[0093] Discussed herein are a number of methods that may be implemented to perform techniques discussed herein. Aspects of the methods may be implemented in hardware, firmware, or software, or a combination thereof. The methods are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. Further, an operation shown with respect to a particular method may be combined and/or interchanged with an operation of a different method in accordance with one or more implementations. Aspects of the methods can be implemented via interaction between various entities discussed above with reference to the environment 100.

[0094] Example implementations described herein include, but are not limited to, one or any combinations of one or more of the following examples.

[0095] In one or more examples, a method implemented by a communication client implemented at a client device comprises: in response to execution of the communication client implemented at the client device, applying a call policy to restrict the communication client from establishing calls with one or more restricted recipients; determining whether the client device is at a registered location of the communication client; and responsive to determining that the client device is at the registered location, applying the call policy to enable the communication client to establish calls with the one or more restricted recipients.

[0096] An example as described alone or in combination with any of the other examples described above or below, wherein the call policy is configured to restrict the communication client from placing emergency calls if the client device is not at the registered location, and enable the communication client to place emergency calls if the client device is at the registered location.

[0097] An example as described alone or in combination with any of the other examples described above or below, wherein group policy is configured to restrict the communication client from establishing calls with one or more business contacts when the client device is not at the registered location.

[0098] An example as described alone or in combination with any of the other examples described above or below, further comprising responsive to determining that the client device is not at the registered location, applying the call policy to continue to restrict the communication client from establishing calls with the one or more restricted recipients.

[0099] An example as described alone or in combination with any of the other examples described above or below, wherein restricting the communication client from establishing calls with the one or more restricted recipients further comprises preventing the communication client from both placing a call to the one or more restricted recipients and receiving a call from the one or more restricted recipients.

[00100] An example as described alone or in combination with any of the other examples described above or below, wherein restricting the communication client from establishing calls with the one or more restricted recipients further comprises displaying one or more indicators to indicate that calls to the one or more restricted recipients is restricted.

[00101] An example as described alone or in combination with any of the other examples described above or below, wherein the determining whether the client device is at the registered location further comprises: determining a current location of the client device based on position information received from a position information system; comparing the current location of the client device to the registered location of the communication client; determining that the client device is at the registered location if the current location of the client device matches the registered location of the communication client; or determining that the client device is not at the registered location if the current location of the client device does not match the registered location of the communication client.

[00102] An example as described alone or in combination with any of the other examples described above or below, wherein the determining whether the client device is at the registered location further comprises determining that the client device is not at the registered location if an accurate current location of the client device cannot be determined.

[00103] An example as described alone or in combination with any of the other examples described above or below, wherein the determining whether the client device is at the registered location further comprises determining that the client device is at the registered location if the client device is connected to a network associated with the registered location, and determining that the client device is not at the registered location if the client device is not connected to the network associated with the registered location.

[00104] An example as described alone or in combination with any of the other examples described above or below, wherein the registered location comprises a business address or a home address associated with the communication client.

[00105] An example as described alone or in combination with any of the other examples described above or below, wherein the call policy comprises a group policy that is managed by an administrator of a group of communication clients.

[00106] In one or more examples, a client device comprises: at least one processor; and one or more computer-readable storage media including instructions stored thereon that, responsive to execution by the at least one processor, implement a policy manager configured to: determine whether the client device is at a registered location associated with a communication client implemented by the client device; responsive to determining that the client device is not at the registered location, apply a call policy to restrict the communication client from establishing calls with the one or more restricted recipients; or responsive to determining that the client device is at the registered location, apply the call policy to enable the communication client to establish calls with the one or more restricted recipients.

[00107] An example as described alone or in combination with any of the other examples described above or below, wherein the policy manager is associated with the communication client. [00108] An example as described alone or in combination with any of the other examples described above or below, wherein the policy manager corresponds to an infrastructure component that is not affiliated or associated with the communication client.

[00109] An example as described alone or in combination with any of the other examples described above or below, wherein the call policy is applied in response to user input to place a call.

[00110] An example as described alone or in combination with any of the other examples described above or below, wherein the policy manger is configured to apply the call policy when the communication client is executed at the client device, and wherein a default configuration of the call policy restricts the communication client from establishing calls with the one or more restricted recipients.

[00111] An example as described alone or in combination with any of the other examples described above or below, wherein the policy manager is configured to apply the call policy to restrict emergency calling if the client device is not at the registered location, and enable emergency calling if the client device is at the registered location.

[00112] In one or more examples, a method implemented by a communication client implemented at a client device comprises: in response to execution of the communication client implemented at the client device, applying a call policy to restrict the communication client from placing an emergency call; determining whether the client device is at a registered location of the communication client; and responsive to determining that the client device is at the registered location, applying the call policy to enable the communication client to place the emergency call.

[00113] An example as described alone or in combination with any of the other examples described above or below, further comprising responsive to determining that the client device is not at the registered location, applying the call policy to continue to restrict the communication client from placing the emergency call.

[00114] An example as described alone or in combination with any of the other examples described above or below, wherein restricting the communication client from placing the emergency call further comprises displaying one or more indicators which indicate emergency calling is disabled.

[00115] Although the example implementations have been described in language specific to structural features and/or methodological acts, it is to be understood that the implementations defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed features.

Claims

1.A method implemented by a communication client implemented at a client device, the method comprising:

in response to execution of the communication client implemented at the client device, applying a call policy to restrict the communication client from establishing calls with one or more restricted recipients;

determining whether the client device is at a registered location of the communication client; and

responsive to determining that the client device is at the registered location, applying the call policy to enable the communication client to establish calls with the one or more restricted recipients.

2. The method of claim 1, wherein the call policy is configured to restrict the communication client from placing emergency calls if the client device is not at the registered location, and enable the communication client to place emergency calls if the client device is at the registered location.

3. The method of claim 1, wherein group policy is configured to restrict the communication client from establishing calls with one or more business contacts when the client device is not at the registered location.

4. The method of claim 1, further comprising responsive to determining that the client device is not at the registered location, applying the call policy to continue to restrict the communication client from establishing calls with the one or more restricted recipients.

5. The method of claim 1, wherein restricting the communication client from establishing calls with the one or more restricted recipients further comprises preventing the communication client from both placing a call to the one or more restricted recipients and receiving a call from the one or more restricted recipients.

6. The method of claim 1, wherein restricting the communication client from establishing calls with the one or more restricted recipients further comprises displaying one or more indicators to indicate that calls to the one or more restricted recipients is restricted.

7. The method of claim 1, wherein the determining whether the client device is at the registered location further comprises:

determining a current location of the client device based on position information received from a position information system;

comparing the current location of the client device to the registered location of the communication client;

determining that the client device is at the registered location if the current location of the client device matches the registered location of the communication client; or

determining that the client device is not at the registered location if the current location of the client device does not match the registered location of the communication client.

8. The method of claim 7, wherein the determining whether the client device is at the registered location further comprises determining that the client device is not at the registered location if an accurate current location of the client device cannot be determined.

9. The method of claim 1, wherein the determining whether the client device is at the registered location further comprises determining that the client device is at the registered location if the client device is connected to a network associated with the registered location, and determining that the client device is not at the registered location if the client device is not connected to the network associated with the registered location.

10. The method of claim 1, wherein the registered location comprises a business address or a home address associated with the communication client.

11. The method of claim 1, wherein the call policy comprises a group policy that is managed by an administrator of a group of communication clients.

12. A client device comprising:

at least one processor; and

one or more computer-readable storage media including instructions stored thereon that, responsive to execution by the at least one processor, implement a policy manager configured to:

determine whether the client device is at a registered location associated with a communication client implemented by the client device;

responsive to determining that the client device is not at the registered location, apply a call policy to restrict the communication client from establishing calls with the one or more restricted recipients; or

responsive to determining that the client device is at the registered location, apply the call policy to enable the communication client to establish calls with the one or more restricted recipients.

13. The client device of claim 12, wherein the policy manager is associated with the communication client.

14. The client device of claim 12, wherein the policy manager corresponds to an infrastructure component that is not affiliated or associated with the communication client.

15. The client device of claim 12, wherein the policy manager is configured to apply the call policy to restrict emergency calling if the client device is not at the registered location, and enable emergency calling if the client device is at the registered location.