CONTEXT BASED DATA MEDIATION

• US 20100284290A1
• Filed: 04/09/2010
• Published: 11/11/2010
• Est. Priority Date: 04/09/2009
• Status: Abandoned Application

• Current Assignee: Aegis Mobility Incorporated
• Original Assignee: Aegis Mobility Incorporated
• Inventors: Williams, Stephen
• Application Number:
  US12/757,840
• Publication Number:
  US 20100284290A1
• Time in Patent Office: Days
• US Class Current: 370/252
• CPC Class Codes: H04W 28/0263 involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
• CPC Class Codes: H04W 8/08 Mobility data transfer
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/22 Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

A communication environment includes of one or more subscriber terminals capable of receiving and transmitting data over a communication network via a communication management system. The communication management system receives mobile communication device context information and mobile communication device identification information from the mobile communication device. The communication management system then identifies data availability profiles reflective of a prior determination of mobile communication device availability to receive data communications according to context. The communication management system then implements data filtering rules corresponding to a current data availability profile.

Claims

1. A computer-implemented method, comprising:

receiving context change notification messages transmitted by a mobile communications device, at least some of said context change notification messages based on motion-based context assessments performed by the mobile communications device;

maintaining state data in computer storage based, at least in part, on the received context change notification messages, wherein the state data is maintained and updated in said computer storage at least during time periods in which the mobile communications device is not being used by the user, said computer storage being separate from the mobile communications device and wherein the state data includes mobile communication device identification information associated with data communications associated with the mobile communication device;

in response to an incoming request data request, using at least said state data, as maintained in said computer storage prior receipt of said request, to determine, at least, whether to perform an action on the data request as specified in the state data;

receiving updated context change notification messages corresponding to the mobile communications device;

associating the mobile communications device with updated state data, the updated state data; and

in response to a second incoming data request, using at least the updated state data, as maintained in said computer storage prior receipt of said request, to determine, at least, whether to perform an action on the data request as specified in the state data.

2. The computer-implemented method as recited in claim 1, wherein receiving updated context change notification messages corresponding to the mobile communications device includes receiving updated context change notification messages corresponding to the mobile communications device from the mobile communications device.

3. The computer-implemented method as recited in claim 1, wherein receiving updated context change notification messages corresponding to the mobile communications device includes receiving updated context change notification messages corresponding to the mobile communications device from a network node.

4. The computer-implemented method as recited in claim 1, wherein using at least said state data to determine whether to perform an action on the data request includes determining whether to at least one of reject, deny or drop data packets corresponding to the data request.

5. The computer-implemented method as recited in claim 4 further comprising mitigating the data requests based on a determination to at least one of reject, deny or drop data packets corresponding to the data request.

6. The computer-implemented method as recited in claim 5, wherein mitigating the data requests includes maintaining at least a portion of the data packets.

7. The computer-implemented method as recited in claim 5, wherein mitigating the data requests includes diverting at least a portion of the data packets.

8. The computer-implemented method as recited in claim 5, wherein mitigating the data request includes queuing at least a portion of the data packets.

9. The computer-implemented method as recited in claim 1, wherein the mobile communication device identification information includes an Internet Protocol address assigned to the mobile communication device.

10. The computer-implemented method as recited in claim 1, wherein the mobile communication device identification information includes identification assigned to the mobile communication device.

11. The computer-implemented method as recited in claim 10, wherein the identification assigned to the mobile communication device is selected from one of transport information, mobile identification number, international mobile subscriber identity information, network access identifier information, and session initiated protocol address information.

12. The computer-implemented method as recited in claim 1, wherein the mobile communication device identification information includes identification assigned to a user associated with mobile communication device.

13. A system for managing communications associated with a mobile communication device comprising:

a mobile communication device interface for bilateral communications with a mobile communication device, wherein the mobile communication device interface obtains mobile communication device context information;

a mobile communication device data store for maintaining mobile communication device availability profiles according to specific mobile communication device contexts, wherein the mobile communication device availability is determined asynchronously to communication requests and includes information for identifying data communications designated for the mobile communication device; and

a communication management component for managing data communications between a mobile communication device and another device based on the mobile communication device profiles, wherein managing data communications includes determining whether to perform an action on the data request as specified in the availability profiles.

14. The system as recited in claim 13, wherein the mobile telecommunications device can be associated with two or more mobile communication device contexts.

15. The system as recited in claim 13, wherein the communication management component is further operable to receive further updated context change notification messages corresponding to the mobile communications device and associate the mobile communications device with updated availability profiles, the updated availability profiles at least reflecting a different determination of whether to perform an action on the data request as specified in the availability profiles.

16. The system as recited in claim 13, wherein the communication management component is operable to determine whether to at least one of reject, deny or drop data packets corresponding to the data request.

17. The system as recited in claim 16, wherein the communication management component is further operable to mitigate data requests based on a determination to at least one of reject, deny or drop data packets corresponding to the data request.

18. The system as recited in claim 17, wherein the communication management component mitigates data request by maintaining at least a portion of the data packets.

19. The system as recited in claim 17, wherein the communication management component mitigates data request by diverting at least a portion of the data packets.

20. The system as recited in claim 17, wherein the communication management component mitigates data request by queuing at least a portion of the data packets.

21. The system as recited in claim 13, wherein the mobile communication device identification information includes an Internet Protocol address assigned to the mobile communication device.

22. The system as recited in claim 13, wherein the mobile communication device identification information includes identification assigned to the mobile communication device.

23. The system as recited in claim 22, wherein the identification assigned to the mobile communication device is selected from one of transport information, mobile identification number, international mobile subscriber identity information, network access identifier information, and session initiated protocol address information.

24. A method for managing communications associated with a mobile communication device comprising:

maintaining a mobile communication device profile, wherein the mobile communication device profile defines criteria for processing data processing profiles based on a current mobile communication device context and identification information attributed to a mobile communication device;

prior to a data request associated with a mobile communication device, determining data filtering rules reflective of an unavailability of the mobile communication device based on processing current mobile communication device context information with the mobile communication device profile, wherein the mobile communication device availability is an assessment of a desirability of facilitating data communications;

subsequently managing data communication requests between the mobile communication device and another communication device, wherein managing communications includes determining whether to perform an action on data packets associated with the data communications based on the data filtering rules;

receiving updated context change notification messages corresponding to the mobile communications device;

determining an updated set of data filtering rules reflective of an unavailability of the mobile communication device based on processing the updated mobile communication device context information; and

in response to a second incoming data communication request, determining whether to perform an action on data packets associated with the data communications based on the updated data filtering rules.

25. The method as recited in claim 24, wherein determining whether to perform an action on the data request includes determining whether to at least one of reject, deny or drop data packets corresponding to the data request.

26. The method as recited in claim 25 further comprising mitigating the data requests based on a determination to at least one of reject, deny or drop data packets corresponding to the data request.

27. The method as recited in claim 24, wherein determining an updated set of data filtering rules reflective of an unavailability of the mobile communication device based on processing the updated mobile communication device context information includes determining a difference between the set of data filtering rules and the updated set of data filtering rules.

28. The method as recited in claim 27 further comprising updating the set of data filtering rules based on the determined difference between the set of data filtering rules and the updated set of data filtering rules.