Validating caller location for use in location-based number assignment - Patents.com

The system uses location-specific verification devices to authenticate and track mobile devices, ensuring compliance with location-based service restrictions and enhancing security and resource management for location-dependent services.

JP7592964B2Active Publication Date: 2024-12-03MICROSOFT TECHNOLOGY LICENSING LLC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2021559039
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2019-04-02
Filing Date
2020-03-22
Publication Date
2024-12-03
Estimated Expiration
2040-03-22

AI Technical Summary

Technical Problem

Existing communication technologies face challenges in managing location-dependent services, particularly in ensuring that mobile devices comply with regulatory requirements and prevent unauthorized use of location-restricted phone numbers or identifiers across different geographic areas.

Method used

A system utilizing location-specific verification devices, such as Bluetooth beacons or Wi-Fi access points, to authenticate and track the geographic location of mobile devices, ensuring compliance with location-based service restrictions by validating the device's proximity to these verification points before allowing access to location-dependent services.

Benefits of technology

Enhances security and compliance by preventing unauthorized use of location-restricted services, improving authentication, and enabling efficient resource management for network systems and client devices, even in areas where traditional location services are unavailable.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007592964000001
    Figure 0007592964000001
  • Figure 0007592964000002
    Figure 0007592964000002
  • Figure 0007592964000003
    Figure 0007592964000003
Patent Text Reader

Abstract

Techniques and systems are disclosed that enable location verification and tracking for use or access of a geographically specific telephone number or similar location-specific feature of a communication service by a mobile computing device at (or within) a geographic location or defined area. In one example, verification of device use at a location or area is enabled by receiving and collecting location verification data from a token having location verification and time data, such location verification data being communicated over a short-range wireless network. Verification is enabled by communicating the token to a communication service for registration of the device's identification and location, and assessing resources based on the registered use of the communication device at the geographic location. In a further example, location information security, verification, and auditing features are enabled using the token and location information.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] This application relates to verifying caller location for use in location-based number assignment. [Background technology]

[0002] The widespread deployment of wireless networks and portable computing devices allows computer users to operate their computing devices in any number of locations. For example, a user may choose to use a notebook computer, tablet, smartphone, or other mobile computing device at an airport, at home, in a restaurant, at a remote workplace, or in many other private or public locations.

[0003] The increasing mobility of computing devices and the prevalence of wireless network connections add complexity to various real-world communication scenarios, especially those involving location-dependent characteristics. As one example, a computing device may have robust wireless network connections throughout a wide geographic area and may make Voice over IP (VoIP) calls over the Internet in nearly any location where a wireless network connection can be established.

[0004] Some types of location features and services, such as the use of location-based telephone numbers or identification codes, are subject to restrictions to prevent their use outside of defined areas (cities, metropolitan areas, states, countries, etc.). Such restrictions may exist for a variety of technical or operational reasons, such as to prevent fraudulent use or to ensure that users can fulfill other communication services, such as emergency calls. As a result of these restrictions, some jurisdictions have proposed or enacted regulatory requirements that would prevent certain communication services from being made widely accessible over Wi-Fi and wide area wireless data networks. [Brief description of the drawings]

[0005] In the drawings, which are not necessarily drawn to scale, like numerals may describe like components in different views. Like numerals with different letter suffixes may represent different instances of the like component. The drawings illustrate generally, by way of example, and not by way of limitation, various embodiments discussed in the present document. [Figure 1] FIG. 2 illustrates an example scenario of a location verification communication operation, according to various examples of the present disclosure. [Diagram 2] 1 illustrates a sequence for obtaining and communicating information from a verification device for a location verification communication operation, according to various examples of the present disclosure. [Diagram 3] 1 is a flowchart of a method performed by a communication service and a verification device to enable location verification service operations, according to various examples of the present disclosure. [Figure 4] 1 is a flowchart of a method performed by a communication service to apply policies to location verification service operations, according to various examples of the present disclosure. [Diagram 5] FIG. 1 illustrates a sequence for accessing location verification service operations using web-based access, according to various examples of the present disclosure. [Figure 6] 1 is a flowchart of a method performed to enable a location verification communication operation, according to various examples of the present disclosure. [Figure 7] FIG. 1 is a schematic diagram of operational and functional components used within client and service systems within a current location verification framework, in accordance with various examples of the present disclosure. [Figure 8] FIG. 1 is a block diagram illustrating an example of a machine in which one or more embodiments may be implemented. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] In some examples, methods, systems, devices, and related operations and functionality are disclosed that enable the use of location-dependent communication applications and services for a user or user device through location-dependent verification and tracking (further described herein with respect to "location-sensitive" or "location-restricted" applications and services). The location verification and tracking techniques described herein may be applicable to perform a variety of service verification and audit functions, including, but not limited to, use with geographically-located related location-sensitive or location-restricted public switched telephone network (PSTN) services and numbers.

[0007] In one example, network service and client scenarios are disclosed that include validation (e.g., prior to network connectivity or resource usage) or verification (e.g., after network connectivity or resource usage) of a mobile device's location or mobile device's service usage. For example, this may enable validation or verification that a mobile device is using, has used, or is authorized to use a particular phone number within a geographic region or zone. This validation or verification may also occur to assist in calculations of whether a mobile device has been located within a geographic region or zone for at least a certain amount of time or timescale, such as to comply with a requirement that a mobile device must be located n percent of the time to continue to use a particular telephone area code or phone number within the geographic region.

[0008] The validation or verification techniques discussed herein may be performed through the communication and processing of location-specific credentials, tokens, or identifiers, including information provided to the mobile device via a geographically known verification device. The verification device may be, for example, a beacon or access point that provides evidence of geographic location (e.g., a unique identifier known to the verification service) that cannot be reproduced or spoofed (e.g., by use of a randomly generated identifier or by encrypted information). A network infrastructure service tracks and maintains the location-specific information in a log or other data store to prove or verify the location of the mobile device in the vicinity of the verification device.

[0009] In a further example, the location-specific token or identifier may be communicated from a verification device to a mobile device over a short-range wireless network (e.g., a network with a typical wireless communication range of less than 100 meters) as a Bluetooth or BLE (Bluetooth Low Energy) beacon, a Wi-Fi (e.g., a standard conforming to IEEE 802.11) access point, a Near Field Communication (NFC) tag, or other device. The verification device may be fixed or operational at a known mobile location. The proximity of the mobile computing device to this verification device, which can receive location verification data within the near field communication range, provides evidence that the mobile computing device is (or was) at a known geographic location. Additionally, the verification device may pass additional information to provide security features or to prevent spoofing or replay of the token or identifier.

[0010] Use of the present technology may provide many improvements and efficiencies in the network and processing operations of both client-based communication devices and server-based location-dependent communication services. First, the technology introduces a new level of authentication and auditing for issuing and using geographically unique telephone numbers and similar network identifiers. Second, the technology enables communication and tracking of geographic location information, including scenarios where clients cannot obtain information from traditional location services (e.g., indoors without access to GPS or when network equipment cannot resolve precise location). Third, the technology improves compliance with applicable regulatory rules and constraints, expanding the number of use cases in which devices are permitted or enabled (not prohibited or restricted) to use location-dependent services.

[0011] Thus, the present disclosure addresses problems with computer networking where the location of client devices is not (or cannot be) tracked completely, or location information may be potentially subject to spoofing or provided via untrusted sources. The current technology provides technical solutions and advantages applicable to client devices, location-based services, networking services and systems, and communication applications. The disclosed technology improves the functionality of multiple network processing entities by enabling the use of improved security, authentication, and resource management for both network and client systems. These and other advantages will become apparent from the following examples and figures.

[0012] 1 illustrates an exemplary scenario 100 of a location verification communication operation. A computing device 102, shown as a mobile smart phone, is a portable computing device capable of operating in different locations. Specifically, the scenario 100 illustrates the location of a mobile device 102-1 at a first location within an area defined as a first geographic location 112A, and a location of a mobile device 102-2 at a second location within an area defined as a second geographic location 112B. For example, the first geographic location 112A may be associated with a workplace of a user of the mobile device 102, and the second geographic location 112B may be associated with a home of a user of the mobile device 102.

[0013] As will be appreciated, the mobile device 102 may move between different locations of an enterprise, private, or other network deployment provided by various network access points or networks, such as a cellular network provided by carrier network stations 130A, 130B, 130C (e.g., network stations operating according to a 4G / 5G wireless data network). In another example, a network access point operating according to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi®) protocol may provide the network connectivity. The network access obtained through the network stations may be used to obtain access to the network communication services 120, which in the following example provide services that are location restricted (e.g., use of a location restricted telephone number).

[0014] In one example, network communication services 120 provide voice, video, or other communication capabilities with other devices and users as part of a voice over IP (VoIP) calling service. In a further exemplary scenario, as discussed in more detail in FIG. 2, the VoIP calling services implemented by network communication services 120 include the ability to place calls over traditional telephone services, including integration with telephone number management and location verification services (e.g., assigning or using geographically restricted telephone numbers).

[0015] Other devices or components may be used to relay or extend communications to other devices and device components. Thus, it will be understood that the techniques discussed herein are not limited to any particular form factor of the devices 102, 104A, 104B, or any peripherals or software clients used with such devices. Similarly, the techniques discussed herein are not limited to telephone or voice calls, but can be extended to various types and forms of communications.

[0016] The computing device 102 can scan for information broadcast by a verification device, such as device 104A located within a first geographic location 112A or device 104B located within a second geographic location 112B. For example, the verification device 104A can be a beacon (e.g., a Bluetooth, Bluetooth Low Energy (BLE), or NFC beacon) and the verification device 104B can be an access point (e.g., a Wi-Fi access point operating according to the IEEE 802.11 family of standards) that transmits location verification data.

[0017] The network communication service 120 may store and track multiple locations of computing devices and verification devices. The network communication service 120 may perform this tracking as part of a device location registry, as discussed further below. The association of devices with locations may be based on location information communicated by each verification device, as discussed in the examples below.

[0018] As an operational example, consider a scenario in which mobile device 102-1 connects to wireless data network 130B while located at a first geographic location 112A (workplace). When mobile device 102-1 is in proximity to beacon 104A, it receives location verification data and communicates this information to network communication service 120 (e.g., when the service's resources are used or periodically). In response, network communication service 120 verifies the use of resources within the geographic location. When mobile device 102-2 moves to wireless data network 130C, it is in proximity to access point 104B and repeats the operation, but using the new location verification data.

[0019] In a scenario where location services may be accessed at different geographic locations (e.g., work, home, etc.), the location information provided via each verification device 104A, 104B may be used by the network communication service 120 to track usage at the different locations. However, in a scenario where a location-restricted service allows access within a larger service area 110 but includes restrictions to prevent access outside the service area, the location information may be used to control access or usage of resources or services. Thus, if the mobile device 102 is not in close proximity (within radio range) to a verification device within the service area, a connection via the wireless data network 130A will not result in service access or resource availability. Other default or limiting actions may also occur based on the definition of the service area, geographic location, and capabilities of the network communication service 120.

[0020] As will be appreciated, the location verification technique is not limited to cellular network connections, but may be useful in many wide area connection settings, including cellular base stations, repeaters, microcell stations, picocell stations, or home repeaters in various geographic regions. Additionally, the technique may be applicable to distributed network access (e.g., to the Internet) via many Wi-Fi® access points.

[0021] 2, an exemplary sequence 200 for obtaining and communicating information from a verification device for a location verification communication operation is shown. The operations of sequence 200 may be performed by a client device 220, a verification device 230, or a hardware implemented service 240, 250, 260, and aspects of the functionality discussed herein.

[0022] Sequence 200 shows a user 210 operating a client device 220 to access location restricted services, i.e., location restricted telephone network resources. The client device 220 receives location verification data from a network access point 230, which also acts as a verification device. This location verification data is placed into a token (or certificate or other data structure) that is communicated by the client device 220 to a location verification service 240 to access resources available via a VoIP network communication service 260.

[0023] In one example, location verification service 240 includes a processing server 242 and a database 244, which respectively determine the location of client device 220 and track the location and other location or security related values ​​of client device 220. A token may include a header containing device identification information, time information, security information (e.g., keys, signatures), etc. A token may include information specific to use with a particular platform service or application, such as a phone dialer that invokes the token and obtains associated identification information for use in dialing operations.

[0024] Validation or verification of the location of client device 220 via location verification service 240 can be used to enable, continue, renew, or modify access to resources or services provided via VoIP network communication service 260. VoIP network communication service 260 may include processing hardware 262 that allocates telephone network resources 264 for use in a communication session (telephone or video conference call) with a communication destination 270, which may also have processing hardware 272 and a terminating device 274 (e.g., for other uses such as receiving a session or call). Validation or verification of the location of client device 220 may also be coordinated with audit and management service 250, which includes a processing server 252 and a database 254 for controlling tracking or audit functions.

[0025] As an example, the technology herein may be applicable to location restrictions imposed by the use of 0AB-J numbers issued in Japan (e.g., telephone numbers used for fixed-line telephone service). Use of the technology discussed herein may enable verification of numbers or blocks of numbers that are restricted to use within a particular geographic or other service area. In some cases, future regulations may allow for a certain percentage of geographic numbers (e.g., 0AB-J numbers) to be used based on requirements such as the need to make outbound calls from a particular area more than n% (e.g., 55%) of the time. Current technology allows for keeping an inventory of such events and performing analysis for policy or commercial outcomes purposes.

[0026] FIG. 3 illustrates a flowchart of a method performed by a communication service and a verification device to enable location verification service operations. As shown, the flowchart 300 of FIG. 3 begins with the verification device generating a location-specific code as location verification data (operation 310), followed by the verification device broadcasting the location-specific code to nearby client devices, such as devices in geographic proximity (limited by short-range wireless capabilities) (operation 320). Other fields may also be communicated as (or concomitantly with) the location verification data. In other examples, another source (e.g., a location verification service) generates and communicates the location-specific code or other location-specific information. In other examples, a request / response model is used to communicate information from the verification device to nearby client devices rather than broadcasting.

[0027] The location specific code is communicated from the client device to a registry of the location verification service using a network connection (e.g., via an Internet connection) (operation 330). Based on receipt of this information, the location specific code or equivalent information for verifying the user's location at the geographic location is recorded in the location verification system (operation 340). For example, this information may be logged in a database to create an association between the client device, the verification device (or information communicated by the verification device), and the geographic location. Thereafter, the location specific code is updated and communicated via the verification device according to a controlled sequence (e.g., based on a schedule, an event, etc.) (operation 350; operations 310-340 may be repeated).

[0028] In a further example, security techniques such as encryption can be used to prevent replay attacks. For example, the verification device can encrypt a random code along with a client device's unique identifier for each client device registered with the device. The client device then communicates the encrypted random code and the client device's unique identifier to a registry. The registry can decrypt the packet using a key associated with the verification device.

[0029] The remainder of the flowchart 300 illustrates scenarios in which location validation information is used. This location validation may occur in response to a request for a location-detected or location-restricted resource, such as a request from a client device to use a geo-restricted phone number (operation 360). Based on the request, an evaluation of associated code or token, such as a token validation (decision 370), may be performed to determine whether the request for the resource can be validated based on the token provided by the mobile computing device. If the request can be validated, access to the resource (e.g., the geo-restricted phone number, or a call using the geo-restricted phone number) may be granted (operation 390). If the request cannot be validated, access to the resource may be denied (or restricted, logged, or otherwise handled).

[0030] 4 provides a flowchart 400 of a method performed by a communication service to enforce policies for location verification service operations. Specifically, the flowchart illustrates a scenario involving the connection of a call based on the use of a location-restricted phone number. Additional processing steps to perform verification or restrict usage may be instituted based on the current location status of a mobile device (e.g., a mobile device attempting to make or receive a call using a location-restricted phone number).

[0031] Flowchart 400 of Figure 4 begins with an operation involving receiving or placing a call using a location restricted telephone number via a mobile device (operation 410). This operation is followed by determining whether the current location of the mobile device is known (decision 420). For example, this determination may include determining the location of the device being communicated with via the techniques discussed in Figures 1-3 above, or via other location tracking techniques.

[0032] If the current location of the mobile device is identifiable, the location of the mobile device is obtained and used by the location verification service (operation 440). If the current location of the mobile device is unknown, inaccessible, or cannot be determined, history or modeling may be used to estimate the location (operation 430). For example, such modeling may use artificial intelligence to estimate a worst case or predicted scenario for the location of the mobile device. For example, modeling techniques may infer location based on the last known location and phone sensor data (e.g., steps recorded by the phone) indicating the distance traveled by the user. Also, for example, modeling techniques may infer location based on the use of pings by the mobile phone to nearby access points, where the ping information is entered into a database along with user information (e.g., tracked by MAC address) and the location of the AP receiving the ping.

[0033] Flowchart 400 concludes with an act for applying a policy regarding the use of location restricted phone numbers based on the known or worst case scenario location of the device (act 450), which may result in various service features or alternatives being offered by the communication service (e.g., blocking the call, offering the use of an alternative phone number, etc.).

[0034] In a further example, the operation may be performed as part of a billing or service functionality audit in connection with location verification, such as in scenarios where different charges are issued based on the usage of resources or services at different locations, and in a further example, the operation may be performed in connection with location verification as part of an emergency call service, or other location-specific or location-based use cases.

[0035] 5 illustrates an exemplary sequence 500 for accessing a location verification service operation using a web-based access, in addition to the location verification examples discussed in the examples above. Specifically, the following web-based access provides a method for communicating a token, identifier, or other information from a verification device, beacon 520, to a mobile device 510 using location verification data contained within a URL (e.g., the URL includes a randomly generated identifier tied to a known location). This URL is then accessed by the mobile device 510, which redirects a software client (e.g., a VoIP client) to a database that records user, location, and / or service IDs to enable use of the VoIP service 530.

[0036] Based on access to the VoIP service 530 via a URL, location verification data can be used to track sessions, resource usage, calls, etc. in association with location characteristics, such as in a log or data table 540. For example, information such as phone number, carrier, and timestamp can be associated with the location of the beacon 520. Similar data values ​​can also be associated and tracked.

[0037] FIG. 6 illustrates a flowchart 600 of a method for enabling location verification communication operations, including one implementation of the detailed algorithms and techniques discussed above. The flowchart 600 of FIG. 6 begins with an optional precondition of the verification device broadcasting location verification data to nearby devices, such as devices within wireless communication range to the target client device (operation 610). This location verification data includes the characteristics discussed above and may be implemented by implementation of a short-range wireless network (such as from a local area wireless network or range-limited beacon broadcast) in scenarios where the target client device is physically close (e.g., within 100 meters) to the verification device (e.g., in the same geographic location). In a further example, the location verification data provides an encrypted version of a random code. In yet a further example, the broadcast or information data is time-limited, such as by periodically changing it, having an associated expiration date, or using various mechanisms such as becoming invalid after a certain period of time. In another example (not shown), instead of being broadcast, the location verification data may be requested or queried by the client device.

[0038] Flowchart 600 continues with operations for receiving location verification data from the verification device when the client device is located at a target geographic location proximate to the verification device (operation 620). In various examples, the location verification data is specific or identifiable to the target geographic location and can be used to identify or confirm the presence of the client device at the target geographic location. The target geographic location can specify, correspond to, contain, or be associated with a location, such as a building, a floor of a building, an area of ​​a city, or a group of locations, within wireless communication range of the verification device. The target geographic location can correspond to geographic locations 112A, 112B, or an area around or at a portion of the service area 110 discussed in FIG. 1. In a further example, the location verification data can provide an encrypted version of a random code, which is synchronized and verified by the communication service for resource usage as discussed herein.

[0039] Flowchart 600 continues with creating or entering a token based on the received location verification data, time data, and other relevant identifying information related to the time-specific location of the client device (operation 630). For example, the time data may be a timestamp generated by the client device indicating use of the communication device at an indicated time at a geographic location. In some examples, the time data may be generated or provided by the verification device (e.g., when the location verification data is generated or verified). In other examples, the location verification data is associated with a time value tracked by a third party, or a time-specific or time-limited identifier is provided from the verification device to enable a third party or another entity to determine when the location verification data was provided. Thus, in some examples, additional or less information in the token may be provided from the verification device. In some examples, all of the token data may be communicated from the verification device to the client device and then from the client device, as described in the operations below.

[0040] Flowchart 600 continues with the operation of communicating (e.g., sending, uploading, indicating usage) the token from the client device to the communication service. In a further example, the token may include an identifier of the client device, such as for auditing, billing, or tracking purposes. The location verification data may be used by the communication service (or a location verification service associated with the communication service) to initiate, establish, or verify a communication session between the communication service and the client device based on verification of the token. For example, use of a geographically based communication feature of the communication service (such as a geographically restricted phone number) may be enabled based on verification of the token. In one example, the communication may be based on packets or other data provided over a network. In a further example, the token or other identifying information may be communicated from the token in a URL accessed by the client device. In some examples, the location verification data is received from a verification data source over a first wireless radio protocol (e.g., Bluetooth, BLE, NFC, Wi-Fi), while the token is transmitted to the communication service over a second wireless radio protocol (e.g., over a 4G / 5G mobile data network). In another example, the same wireless radio protocol (e.g., Wi-Fi®) is used for both receiving and transmitting, such as from the same access point configured to broadcast location verification data and also provide Internet access.

[0041] Flowchart 600 continues with accessing a resource within the communication service based on the index of the communication device with a geographic location and any accompanying registration effected with the communication service (operation 650). The resource may be part of a location-based service that provides information based on the verified location of the client device. The resource may be part of a location-independent service, such as telephony, that functions regardless of the location of the client device.

[0042] Flowchart 600 concludes with an optional operation of repeating one or more location verification options to obtain continued access to resources (operation 660) and enabling verification or auditing of the location verification operations and communicated location data (operation 670). For example, a subsequent token may be generated and communicated from the client device, including updated time data that enables tracking of the time the client device was known to be located near the verification device. Similarly, updated location verification data may be received by the client device via a subsequent verification device broadcast and included in a new token that is generated and communicated to the communication service. Verification and auditing may occur in real time or at a later time. Thus, the techniques of flow chart 600 may be implemented for current or future connection setups (or to enable or disable access to resources).

[0043] In further examples, other techniques can be used to communicate, exchange, and propagate the location verification data discussed herein. For example, information can be communicated in a peer-to-peer or ad-hoc setting of linked client devices or groups of client devices. For example, a common group of devices (e.g., trusted devices associated with a common user or entity) can exchange location verification data with each other to reduce the number of communications required between the verification devices and the communication service system.

[0044] FIG. 7 shows a schematic diagram of the operational and functional components used between a client and a service platform using current location tracking technology. These components include a communication service system 710, a verification device 750, a client computing device 770, a management / audit system 740, and various subcomponents involved in or associated with the location verification operations discussed herein. The communication service system 710 may be an example of a server that implements location services and allocates resources (e.g., VoIP, telephone network, or data service resources) discussed herein for access by the client computing device 770. The client computing device 770 may be an example of a mobile computing device discussed herein. The verification device 750 may be an example of a beacon or access point discussed herein. The management / audit system 740 may be an example of a server for implementing services for location auditing to facilitate business or technical service operations discussed herein.

[0045] The components illustrated in FIG. 7 may be embodied or implemented in hardware, software, or any combination thereof. The functionality of each component is an example of an arrangement of functionality, and one of ordinary skill in the art having the benefit of this disclosure will appreciate that other arrangements are possible. Each of the illustrated systems 710, 750, 770 is shown as including processing circuitry 715, 755, 775, such as a CPU and memory configured to execute respective software instructions. Additionally, one or more functions of one or more communication service systems 710 may be performed by distributed server-side components within the overall system. Similarly, one or more functions of one or more components of client computing device 770 may be performed by one or more other client-side components.

[0046] Client computing device 770 is shown as including location functionality 780 adapted to receive and forward location verification data using the techniques discussed above, and communication services functionality 785 for accessing and using location-dependent (e.g., location-restricted, location-detected) resources or services as discussed herein. Client computing device 770 may further include other communication interface functionality, such as VoIP software or hardware (e.g., audio processing hardware, video conferencing software) used to perform (e.g., receive input, provide output) calls, chats, conferencing, or other aspects of human-to-human or human-to-machine communication.

[0047] The client computing device 770 is shown as including a local or near area network interface 790 used to obtain location verification data (e.g., data included in location verification data structure 704) from the verification device 750. The client computing device 770 is also shown as including a wide area network interface 795 for accessing a wide area network (e.g., 4G / 5G network for Internet connectivity), and the like. The network interface may provide software and / or hardware components that enable the client computing device 770 to associate, authenticate, and connect to various networks including a network stack (e.g., Transmission Control Protocol (TCP), Internet Protocol, one or more protocol layers specified by the 802.11 family of standards promulgated by the Institute of Electrical and Electronics Engineers (IEEE), and the like). As used herein, Wi-Fi®-enabled access points and computing devices may communicate, authenticate, associate, connect, and otherwise operate in accordance with the IEEE 802.11 family of standards, such as 802.11n or 802.11ac. Computing device 770 may also include other network interfaces for communicating over other types of wired or wireless networks.

[0048] Verification device 750 is shown in FIG. 7 as including communications circuitry 760 and location functionality 765. Communications functionality 765 can facilitate respective connections with client devices (such as computing device 770) to communicate location verification data (e.g., via location verification data structure 704). In one example, at least a portion of the location verification data is provided from communication services system 710 (e.g., via location verification data structure). Verification device 750 can also recognize its location as confirmed using communication services system 710.

[0049] The communication services system 710 is shown in FIG. 7 as including communication circuitry 720, communication services function 725, and location verification function 730, operatively connected to a device location tracking database 740 and a verification information database 735. One or both of these databases may enable registry and tracking functions as discussed herein. The communication services function 725 may enable the use of voice, video, or other telecommunications services via location dependent resources as discussed herein. The location verification function 730 may obtain and process information such as a token provided by a client computing device 770 (e.g., provided in a token data structure 706), which provides proof of co-location of the client computing device 770 and the verification device 750.

[0050] Finally, management and audit system 740 is shown in Figure 7 and includes a location audit function 745 that allows an administrator or system process to verify the location and usage of location dependent resources of a communication service, such as determining or verifying the amount of time a device operates at each geographic location. Information to verify or audit may be communicated via device and location data (e.g., via device / location information data structure 708). Location audit function 745 may operate to generate reports, billing, or other information for services. Additional management control interfaces (not shown) may allow for management and provision of rules and exceptions consistent with management functions.

[0051] FIG. 8 illustrates a block diagram of an example machine 800 on which any one or more of the techniques (e.g., methodologies) discussed herein may be implemented. In alternative embodiments, the machine 800 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a network deployment, the machine 800 may operate in the capacity of a server machine, a client machine, or both in a server-client network environment. In one example, the machine 800 may function as a peer machine in a peer-to-peer (P2P) (or other distributed) network environment. The machine 800 may be a personal computer (PC), a tablet PC, a personal digital assistant (PDA), a mobile phone, a cloud-based or networked server, a virtualization server, a smartphone, The machine 800 may be a computing device such as a web appliance, a network router, an access point, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by the machine. Additionally, although only a single machine is shown, the term "machine" should also be construed to include a collection of machines (such as cloud computing, Software as a Service (SaaS), other computer cluster configurations, etc.) that individually or collectively execute a set (or sets) of instructions to perform any one or more of the methods discussed herein. The machine 800 may specifically implement any of the devices and platforms 102, 104, 120, 130, 220, 230, 240, 250, 260 of Figures 1 and 2, the operations shown in the methods implemented in Figures 3-6, or the servers and devices 710, 740, 750, 770 as referenced in Figure 7.

[0052] The examples described herein may include or operate on logic or a number of components, modules, or mechanisms (hereinafter "components"). Such components are tangible entities (such as hardware) that can perform specified operations and may be configured or arranged in a particular manner. In one example, a circuit or electrical circuit may be arranged (e.g., internally or with respect to external entities such as other circuits or electrical circuits) in a specified manner as a component. In one example, all or part of one or more computer systems (e.g., standalone, client or server computer systems) or one or more hardware processors may be configured as components that operate to perform operations specified by firmware or software (e.g., instructions, application portions, or applications). In one example, the software may reside in a machine-readable medium, such as a non-transitory machine-readable storage medium. In one example, the software, when executed by the hardware underlying the component, causes the hardware to perform the specified operations.

[0053] Thus, such components encompass tangible entities that are physically constructed, specially configured (e.g., wired), or temporarily (e.g., transiently) configured (e.g., programmed) to operate in a particular manner or to perform some or all of the operations described herein. Considering examples in which components are temporarily configured, it is not necessary for each component to be instantiated at any one time. For example, if the components include a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as each different component at different times. Thus, the software may, for example, configure the hardware processor to configure a particular component at one time and a different component at a different time.

[0054] The machine (e.g., computer system) 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804, and a static memory 806, some or all of which may communicate with each other via an interlink (e.g., a bus) 808. The machine 800 may further include a display unit 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse). In one example, the display unit 810, the input device 812, and the UI navigation device 814 may be touch screen displays. The machine 800 may further include a storage device (e.g., a drive unit) 816, a signal generating device 818 (e.g., a speaker), a network interface device 820, and one or more sensors 830, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The machine 800 may include an output controller 828, such as a serial (e.g., Universal Serial Bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection, to communicate with or control one or more peripheral devices (printers, card readers, etc.).

[0055] Storage 816 may include machine-readable medium 822 on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodied or utilized by any one or more of the techniques or functions described herein. The instructions 824 may also reside, completely or at least partially, within main memory 804, within static memory 806, or within hardware processor 802 during its execution by machine 800. In one example, one or any combination of hardware processor 802, main memory 804, static memory 806, or storage 816 may constitute a machine-readable medium.

[0056] Although machine-readable medium 822 is illustrated as a single medium, the machine-readable medium may include a single medium or multiple media (e.g., centralized or distributed databases and / or associated caches and servers) configured to store one or more instructions 824. Thus, the term machine-readable medium may include any medium that can store, encode, or carry instructions for execution by machine 800, cause machine 800 to perform any one or more of the techniques of this disclosure, or store, encode, or carry data structures used by or associated with such instructions.

[0057] Non-limiting examples of machine-readable media may include solid-state memory, as well as optical and magnetic media. Specific examples of machine-readable media may include non-volatile memory such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); solid-state drives (SSD); and CD-ROM and DVD-ROM disks. In some examples, machine-readable media may include non-transitory machine-readable media (e.g., excluding transitory propagating signals).

[0058] The instructions 824 may further be transmitted or received over a communications network 826 using a transmission medium via the network interface device 820. The machine 800 may communicate with one or more other machines utilizing any one of a number of transport protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.). Examples of communications networks include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., a cellular network), a Plain Old Telephone (POTS) network, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, the Long Term Evolution (LTE) family of standards, Universal Mobile Telephone System (UMTS), and the like. The network interface devices 820 may include wireless data networks such as networks implementing the IEEE 802.11 (Mobile Telecommunications System) family of standards, peer-to-peer (P2P) networks, among others. In one example, the network interface devices 820 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas for connecting to the communications network 826. In one example, the network interface devices 820 may include multiple antennas for wireless communication using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. In some examples, the network interface devices 820 may communicate wirelessly using multi-user MIMO technology.

[0059] Additional examples of embodiments of the methods, systems, and devices described thus far include the following non-limiting configurations: Each of the following non-limiting examples can stand on its own or can be combined in any permutation or combination with any one or more of the other examples provided below or throughout this disclosure.

[0060] Example 1 is a communications device adapted to perform location verification, the device including at least one hardware processor; and at least one memory device including instructions that, when executed, cause the hardware processor to perform location verification operations including receiving location verification data from a verification data source at a geographic location, the location verification data being specific to the geographic location; creating a token including the location verification data and time data, the time data indicating use or location of the communications device at an indicated time at the geographic location; transmitting the token from the communications device to the communications service in a scenario where the communications service is configured to register use of the communications device at an indicated time at the geographic location; and accessing resources of the communications service based on the registered use of the communications device at the geographic location.

[0061] In Example 2, the subject matter of Example 1 optionally includes a feature where the location verification data provides an encrypted version of the random code, the random code being verified by the communication service for use of resources of the communication service at the geographic location.

[0062] In Example 3, the subject matter of any one or more of Examples 1-2 optionally includes a feature where the token further includes an identifier of the communication device, and where the communication service is configured to establish a communication session for the communication device using the resource in response to verifying the token.

[0063] In Example 4, the subject matter of Example 3 optionally includes a feature where the communication service is configured to enable use of a geographically-based communication feature of the communication service based on validation of the token.

[0064] In Example 5, the subject matter of any one or more of Examples 3-4 optionally includes a feature where the location verification data provided by the verification data source is synchronized with the communication service.

[0065] In Example 6, the subject matter of any one or more of Examples 1-5 optionally includes a feature where the location verification data is received from the verification data source via a first wireless radio protocol and the token is transmitted to the communication service via a second wireless radio protocol.

[0066] In Example 7, the subject matter of Example 6 is optionally further characterized in that the first wireless radio protocol is a Bluetooth Low Energy (BLE) protocol or a Bluetooth These include features such as the Bluetooth® standard protocol conforming to the Standards Interest Group family of standards, or the Wi-Fi® protocol conforming to standards from the IEEE 802.11 family of standards.

[0067] In Example 8, the subject matter of any one or more of Examples 1-7 optionally includes a feature where the location verification operation is repeated at regular intervals or is triggered in response to a request to perform communication using the resource.

[0068] In Example 9, the subject matter of any one or more of Examples 1-8 optionally includes a feature where transmission of the token from the communication device to the communication service is provided through use of the token in a uniform resource locator (URL) accessed by the communication device.

[0069] In Example 10, the subject matter of any one or more of Examples 1-9 optionally includes a feature where the geographic location further specifies a location within the validation data source in a building, a floor of a building, an area of ​​a city, or a group of locations.

[0070] Example 11 is a method for accessing a location-specific verification service, the method including operations performed by a computing device using one or more hardware processors, the operations including: receiving location verification data from a verification data source, the location verification data being received at a geographic location, the location verification data being specific to the geographic location; creating a token including the location verification data and time data, the time data being indicative of use or location of the computing device at an indicated time at the geographic location; transmitting the token from the computing device to a communications service, the communications service being configured to register use of the computing device at the indicated time at the geographic location; and accessing resources of the communications service based on the registered use of the computing device at the geographic location.

[0071] In Example 12, the subject matter of Example 11 optionally includes a feature where the location verification data provides an encrypted version of the random code, and the random code is verified by the communication service for use of resources in the communication service at the geographic location.

[0072] In Example 13, the subject matter of any one or more of Examples 11-12 optionally includes a feature where the token further includes an identifier of the computing device, and the communication service is configured to establish a communication session with the computing device using the resource in response to verifying the token.

[0073] In Example 14, the subject matter of any one or more of Examples 11-13 optionally further comprises receiving location verification data from a verification data source via a first wireless radio protocol, the first wireless radio protocol being a Bluetooth Low Energy (BLE) protocol or a Bluetooth In a scenario where the protocol is a Bluetooth® standard that complies with the Standards Interest Group family of standards, or a Wi-Fi® protocol that complies with a standard from the IEEE 802.11 family of standards, the token includes a feature where the token is transmitted to the communication service via a second wireless radio protocol.

[0074] In Example 15, the subject matter of any one or more of Examples 11-14 optionally further comprises the action being repeated at regular intervals or triggered in response to a request to perform communication using the resource, and the geographic location further specifying a location within range of the validation data source in a building, a floor of a building, an area of ​​a city, or a group of locations.

[0075] Example 16 is a computing device adapted to access a location-specific verification service, the computing device including: means for receiving location verification data from a verification data source at a geographic location, the location verification data being specific to the geographic location; means for creating a token including the location verification data and time data, the time data indicating use or location of the computing device at an indicated time at the geographic location; means for transmitting the token to a communications service providing information to enable the communications service to register use of the computing device at the indicated time at the geographic location; and means for accessing resources of the communications service based on the registered use of the computing device at the geographic location.

[0076] In Example 17, the subject matter of Example 16 optionally includes the location verification data providing an encrypted version of the random code, the random code being verified by the communication service for use of resources of the communication service at the geographic location.

[0077] In Example 18, the subject matter of any one or more of Examples 16-17 optionally includes wherein the token further includes an identifier of the computing device, and wherein the communication service is configured to establish a communication session for the computing device using the resource in response to verifying the token.

[0078] In Example 19, the subject matter of any one or more of Examples 16-18 optionally includes means for receiving location verification data from a verification data source via a first wireless radio protocol; and means for transmitting the token to a communication service via a second wireless radio protocol.

[0079] In Example 20, the subject matter of any one or more of Examples 16-19 optionally includes further specifying that the geographic location is a location within the validation data source in a building, a floor of a building, an area of ​​a city, or a group of locations.

Claims

1. 1. A communication device adapted to perform location verification, the communication device comprising: at least one hardware processor; at least one memory device containing instructions; The instructions, when executed, cause the hardware processor to: receiving location verification data broadcast from a verification data source device at a geographic location, the location verification data being specific to the geographic location and including an encrypted version of a random code, the random code being a location specific code generated by the verification data source device, the random code being updated according to a controlled sequence; creating a token including the location verification data and time data, the time data indicating that the communications device is located at the geographic location at an indicated time; transmitting the token from the communication device to a communication service configured to register use of the communication device at the geographic location at the indicated time, the random code being verified by the communication service for use of resources of the communication service at the geographic location, and the location verification data provided by the verification data source device being synchronized with the communication service; and accessing the resources of the communication service based on the registered use of the communication device at the geographic location, where accessing the resources causes a location verification operation to be performed, the location verification operation including initiating, establishing, or verifying a communication session between the communication service and the client device. Communications equipment.

2. The communication device of claim 1 , wherein the token further includes an identifier of the communication device, and the communication service is configured to establish a communication session for the communication device using the resource in response to validating the token.

3. The communication device of claim 2 , wherein the communication service is configured to enable use of a geographically based communication feature of the communication service based on validation of the token.

4. 2. The communication device of claim 1, wherein the location verification data is received from the verification data source device over a first wireless radio protocol and the token is transmitted to the communication service over a second wireless radio protocol.

5. 5. The communication device of claim 4, wherein the first wireless radio protocol is a Bluetooth Low Energy (BLE) protocol or a Bluetooth (registered trademark) standard protocol conforming to the Bluetooth Standards Interest Group family of standards, or a Wi-Fi (registered trademark) protocol conforming to a standard from the IEEE 802.11 family of standards.

6. The communications device of claim 1 , wherein the location verification operation is repeated at regular intervals or is triggered in response to a request to perform a communication using the resource.

7. 2. The communication device of claim 1, wherein transmission of the token from the communication device to the communication service is provided by use of the token in a uniform resource locator (URL) accessed by the communication device.

8. 8. The communications device of claim 1, wherein the geographic location further specifies a location within range of the validation data source device in a building, a floor of a building, an area of ​​a city, or a group of locations.

9. 1. A method for accessing a location specific verification service, the method including operations performed by a computing device using one or more hardware processors, the operations including: receiving location verification data broadcast from a verification data source device, the location verification data being received at a geographic location, the location verification data being specific to the geographic location and including an encrypted version of a random code, the random code being a location specific code generated by the verification data source device, the random code being updated according to a controlled sequence; creating a token including the location verification data and time data, the time data indicating that the computing device is located at the geographic location at an indicated time; transmitting the token from the computing device to a communications service configured to register use of the computing device at the geographic location at the indicated time, the random code being verified by the communications service for use of resources of the communications service at the geographic location, and the location verification data provided by the verification data source device being synchronized with the communications service; and accessing the resources of the communication service based on the registered use of the computing device at the geographic location, where accessing the resources includes initiating, establishing, or validating a communication session between the communication service and a client device. method.

10. 10. The method of claim 9, wherein the token further includes an identifier of a communications device, and the communications service is configured to establish a communications session for the computing device using the resource in response to validating the token.

11. 10. The method of claim 9, wherein the location verification data is received from the verification data source device via a first wireless radio protocol and the token is transmitted to the communication service via a second wireless radio protocol, the first wireless radio protocol being a Bluetooth Low Energy (BLE) protocol or a Bluetooth standard protocol conforming to the Bluetooth Standards Interest Group family of standards, or a Wi-Fi protocol conforming to a standard from the IEEE 802.11 family of standards.

12. 12. The method of claim 9, wherein the operation is repeated at regular intervals or triggered in response to a request to perform a communication using the resource, and the geographic location further specifies a location within range of the validation data source device in a building, a floor of a building, an area of ​​a city, or a group of locations.

Citation Information

Patent Citations

  • Token generation and authentication method, and authentication server

    EP3316544A1

  • Secure digital storage

    US20130212704A1

  • Systems and methods for reusing generic tokens using bluetooth low energy (BLE) beacons

    US20160021687A1

  • Location awareness session management and cross application session management

    US9271110B1

  • Identity and / or risk management system and method

    WO2016050990A1