Data stitching for networked automation

• US 9,775,039 B2
• Filed: 11/18/2014
• Issued: 09/26/2017
• Est. Priority Date: 11/18/2014
• Status: Active Grant

• Current Assignee: T-Mobile USA, Inc. (Deutsche Telekom AG)
• Original Assignee: T-Mobile USA, Inc. (Deutsche Telekom AG)
• Inventors: Yocam, Eric W., Obaidi, Ahmad Arash
• Primary Examiner(s): Poltorak, Peter
• Application Number:
  US14/546,902
• Publication Number:
  US 20160142916A1
• Time in Patent Office: 1,043 Days
• CPC Class Codes: G06Q 20/3224 Transactions dependent on location of M-devices
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/63 Location-dependent; Proximity-dependent
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences

Abstract

A telecommunication carrier may stitch data from multiple sources to support device automation and access control. A state may be assigned to a user of a user device at a telecommunication carrier based on a data stitch of information from multiple data sources. The data sources may include data on a geolocation of the user device. The state may be provided to a rules engine at a remote location via a carrier network of the telecommunication carrier. An indication from the rules engine that the user device is granted or denied access to one or more entities at the location based on the state may be received via the carrier network at the telecommunication carrier. In turn, the telecommunication carrier may provide the indication of the granted or denied access to the user device of the user.

Claims

1. A computer-implemented method, comprising:

assigning a state to a user of a user device at a telecommunication carrier based at least on a data stitch of information from multiple data sources and a type of data registered in advance to be received by a rules engine at a remote location, the multiple data sources including data on a geolocation of the user device, wherein different types of states are assigned to different classes of rules engines;

providing, via a carrier network of the telecommunication carrier, the state to the rules engine at the remote location;

receiving, via the carrier network, an indication from the rules engine that the user is granted or denied access to one or more entities at the remote location based at least on the state; and

providing, via the carrier network, the indication of granted or denied access to the user device of the user.

2. The computer-implemented method of claim 1, further comprising:

sending, via the carrier network, a request for an input of authentication information from the user on behalf of the rules engine following the user being denied access to the one or more entities by the rules engine;

providing, via the carrier network, the authentication information of the user to the rules engine;

receiving, via the carrier network, an additional indication from the rules engine that the user device is granted access to the one or more entities in response to the rules engine determining that the authentication information is valid; and

providing, via the carrier network, the additional indication of the granted access to the user device of the user.

3. The computer-implemented method of claim 1, further comprising receiving, via the carrier network, the information from at least one of a database of another telecommunication carrier, a database of a government agency, or a database of a private firm.

4. The computer-implemented method of claim 1, further comprising receiving, via the carrier network, the geolocation of the user device from a mobile hotspot at the remote location, the geolocation being received at an occurrence of a trigger event at the remote location or as a portion of a periodic data report aggregated by the mobile hotspot.

5. The computer-implemented method of claim 1, further comprising:

receiving, via the carrier network, an additional geolocation of the user device; and

sending the additional geolocation of the user device to a financial institution to repudiate a transaction that occurred at a location that is different from the additional geolocation.

6. The computer-implemented method of claim 1, wherein the one or more entities include at least one of an automation device that responds to remote control from the rules engine, or a data resource that comprises a document, an email, a file, or a website.

7. The computer-implemented method of claim 1, wherein assigning a state to the user includes determining that the user is in a restricted area based at least on the data stitch of the information from the multiple data sources.

8. The computer-implemented method of claim 7, further comprising in response to determining that the user is in the restricted area, performing, via the carrier network, at least one of sending a warning to the user device of the user indicating that the user is in the restricted area, providing a geolocation of the user device to one or more organizations, or informing one or more additional user devices that the user device is in the restricted area.

9. The computer-implemented method of claim 8, wherein providing the geolocation include providing the geolocation of the user device to at least one of a law enforcement agency or a private firm that controls access to the restricted area.

10. One or more non-transitory computer-readable media storing computer-executable instructions that upon execution cause one or more processors to perform acts comprising:

receiving, via a carrier network, information from multiple data sources that include a database of a telecommunication carrier that at least stores a geolocation of a user device;

assigning a state to a user of the user device based at least on a data stitch of the information from the multiple data sources that includes the geolocation of the user device and a type of data registered in advance to be received by a rules engine at a remote location, wherein different types of states are assigned to different classes of rules engines;

providing, via the carrier network, the state to the rules engine at the remote location;

receiving, via the carrier network, an indication from the rules engine that the user is granted or denied access to one or more entities at the remote location based at least on the state; and

providing, via the carrier network, the indication of granted or denied access to the user device of the user.

11. The one or more non-transitory computer-readable media of claim 10, wherein the acts further comprise:

sending, via the carrier network, a request for an input of authentication information from the user on behalf of the rules engine following the user being denied access to the one or more entities by the rules engine;

providing, via the carrier network, the authentication information of the user to the rules engine;

receiving, via the carrier network, an additional indication from the rules engine that the user device is granted access to the one or more entities in response to the rules engine determining that the authentication information is valid; and

providing, via the carrier network, the additional indication of the granted access to the user device of the user.

12. The one or more non-transitory computer-readable media of claim 10, where the acts further comprise:

receiving, via the carrier network, an additional geolocation of the user device; and

sending the additional geolocation of the user device to a financial institution to repudiate a transaction that occurred at a location that is different from the additional geolocation.

13. The one or more non-transitory computer-readable media of claim 10, wherein the receiving includes receiving the geolocation of the user device from a mobile hotspot at the remote location, the geolocation being received at an occurrence of a trigger event at the remote location or as a portion of a periodic data report aggregated by the mobile hotspot.

14. The one or more non-transitory computer-readable media of claim 10, wherein the one or more entities include at least one of an automation device that responds to remote control from the rules engine, or a data resource that comprises a document, an email, a file, or a website.

15. The one or more non-transitory computer-readable media of claim 10, wherein the assigning the state to the user includes determining that the user is in a restricted area based at least on the data stitch of the information from the multiple data sources.

16. The one or more non-transitory computer-readable media of claim 15, wherein the acts further comprise in response to determining that the user is in the restricted area, performing, via the carrier network, at least one of sending a warning to the user device of the user indicating that the user is in the restricted area, providing a geolocation of the user device to one or more organizations, or informing one or more additional user devices that the user device is in the restricted area.

17. The one or more non-transitory computer-readable media of claim 16, wherein providing the geolocation include providing the geolocation of the user device to at least one of a law enforcement agency or a private firm that controls access to the restricted area.

18. A computing device, comprising:

one or more processors; and

memory having instructions stored therein, the instructions, when executed by the one or more processors, cause the one or more processors to perform acts comprising;

receiving, via a carrier network, information from multiple data sources that include a database of a telecommunication carrier that at least stores a geolocation of a user device;

assigning a state to a user of the user device based at least on a data stitch of the information from the multiple data sources that includes the geolocation of the user device and a type of data registered in advance to be received by a rules engine at a remote location, wherein different types of states are assigned to different classes of rules engines;

providing, via the carrier network, the state to the rules engine at the remote location;

receiving, via the carrier network, an indication from the rules engine that the user is granted or denied access to one or more entities at the remote location based at least on the state; and

providing, via the carrier network, the indication of granted or denied access to the user device of the user.

19. The computing device of claim 18, wherein the acts further comprise:

sending, via the carrier network, a request for an input of authentication information from the user on behalf of the rules engine following the user being denied access to the one or more entities by the rules engine;

providing, via the carrier network, the authentication information of the user to the rules engine;

receiving, via the carrier network, an additional indication from the rules engine that the user device is granted access to the one or more entities in response to the rules engine determining that the authentication information is valid; and

providing, via the carrier network, the additional indication of the granted access to the user device of the user.

20. The computing device of claim 18, wherein the receiving includes receiving the geolocation of the user device from a mobile hotspot at the remote location, the geolocation being received at an occurrence of a trigger event at the remote location or as a portion of a periodic data report aggregated by the mobile hotspot.