Media content system utilizing user sponsored data

A system may receive a request to access user sponsored media content (“media content”), the request including a digital token (“token”), the media content being associated with a user sponsored account (“account”), and the account being associated with unused data from a mobile communications service plan, where the account and the mobile communications service plan are associated with a user. The system may identify token information included in the token. The system may compare the token information with stored token information. The system may determine that the token is valid based on the token information matching the stored token information. The system may provide access to the media content based on the token being valid. The system may provide information to cause data charges, for traffic flow associated with access to the media content, to be charged against the unused data associated with the account.

BACKGROUND

Service providers of mobile communications offer a variety of service plans related to mobile communications services (e.g., talk minutes, texts, data, etc.). Users of the mobile communications services (e.g., customers of the service providers) pay a fee (e.g., a monthly fee) for access to the service plans.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Service providers of mobile communications services may provide a set quantity of mobile communications services (e.g., a set quantity of minutes, a set quantity of texts, a set quantity of data, etc.) for a fee (e.g., a monthly fee). Some service providers may require the users to use/consume the set quantity of the mobile communications services, during a set period of time (e.g., a month), and may deny the user to carry over (e.g., roll-over) any unused quantity of the mobile communications services to a future period of time (e.g., unused minutes/data may not be carried over to a following billing cycle). These users may end up paying for mobile communications services not used/consumed, as these users are required to pay the fee, regardless of whether the user used/consumed the quantity of mobile communications services entirely, during the set period of time.

Other service providers may permit the unused quantity of the mobile communications services to be carried to a future period of time. However, some users may not change their usage/consumption pattern in these situations (e.g., a user may generally use/consume only 500 megabytes (MB) out of a 1 gigabyte (GB)/month mobile communications service plan each month). These users do not realize any benefit from being able to carry over unused data to a future period of time (e.g., users, whose usage/consumption pattern does not vary, will not consume 1.5 GB of data (a mobile communications services plan with 1 GB/month of data +500 MB of roll-over data) in a future billing cycle, benefiting from the roll-over data).

Additionally, a service provider may reserve bandwidth in a service provider network for the quantity of mobile communications service provided/allocated to each user. Network resources, associated with the service provider network, may be negatively impacted based on an inefficient/improper allocation of mobile communications services.

Implementations described herein enable a system to share user sponsored media content, provided by a user sponsored account, with recipient mobile devices, where users of the recipient mobile devices may access the user sponsored media content using an unused quantity of mobile communications services (e.g., an unused quantity of data or unused data) associated with the user sponsored account. The system may share the user sponsored media content using an associated uniform resource locator (URL), included in a message provided to recipients, where the recipients may access the user sponsored media content using the URL.

FIG. 1is a diagram of an overview of an example implementation100described herein. As shown inFIG. 1, and by reference number1, a user of a mobile device may create user sponsored media content (e.g., a video file, Video File 1.mp4, with a file size of 200 MB) for a user sponsored account, using a media platform application (e.g., Video Platform Application), associated with a service provider (e.g., a mobile communications service provider).

As shown inFIG. 1, and by reference number2, the user of the mobile device may associate unused data, associated with the user of the mobile device, with the user sponsored account (e.g., associate 2 GB of unused data with the user sponsored account), using a sponsored data control device (e.g., Sponsored Data Control Device), associated with the service provider. The unused data is data from a mobile communications service plan, provided by the service provider and associated with the user of the mobile device, which the user of the mobile device does not use/consume during a billing cycle.

As shown inFIG. 1, and by reference number3, the user may cause the mobile device to provide provisioning information (e.g., names of recipients, a quantity of recipients, a validity period for the recipients to access the user sponsored media content, an amount of unused data available for accessing the user sponsored media content, etc.), associated with creating a message, associated with the user sponsored media content.

As shown inFIG. 1, and by reference number4, the sponsored data control device may create the message, based on the provisioning information, and may associate the message with the user sponsored media content. As shown inFIG. 1, and by reference number5, the sponsored data control device may provide the message to users (e.g., Recipient1, Recipient2, Recipient3, etc.) of recipient mobile devices (e.g., Recipient Mobile Device1, Recipient Mobile Device2, Recipient Mobile Device3, etc.), identified in the provisioning information and via a sponsored data enforcement device (e.g., Sponsored Data Enforcement Device).

As shown inFIG. 1, and by reference number6, the users of the recipient mobile devices may use the unused data, associated with the user sponsored account, to access the user sponsored media content, using a URL included in the message.

In this way, network resources (e.g., the service provider network, the unused data, etc.), associated with the service provider, may be used effectively and efficiently, thereby improving network performance.

While the description to follow focuses on the user sponsored media content being video content (e.g., a video file), the description may also apply to other types of user sponsored media content (e.g., an audio file, an image file, etc.).

Additionally, while the description to follow focuses on a mobile device used to create a user sponsored account and share unused data, a user device (e.g., a laptop, a personal computer, etc.) may also be used, provided that the user of the user device has a mobile communications service plan to associate the unused data with the user sponsored account. The user device may communicate with the sponsored data control device, via a network (e.g., a cellular network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, a mesh network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, etc.).

Additionally, while the description to follow focuses on a user of the mobile device creating the user sponsored account, users of recipient mobile devices may also create user sponsored accounts and share unused data for accessing user sponsored media content, created/provided by the users of the recipient mobile devices. Additionally, the user of the mobile device may also use unused data associated with another user to access user sponsored media content provided by the other user.

FIG. 2is a diagram of an example environment200in which systems and/or methods, described herein, may be implemented. As shown inFIG. 2, environment200may include mobile device205; a base station210; a mobility management entity device (MME)215; a serving gateway (SGW)220; a packet data network gateway (PGW)225; a sponsored data enforcement device230; a sponsored data control device235; an authentication, authorization, and accounting server (AAA)240; and one or more recipient mobile devices245-1through245-N (N≧1) (hereinafter referred to collectively as “recipient mobile devices245,” and individually as “recipient mobile device245”). Devices of environment200may interconnect via wired connections, wireless connect ions, or a combination of wired and wireless connections.

Some implementations are described herein as being performed within a long term evolution (LTE) network for explanatory purposes. Some implementations may be performed within a wireless network that is not an LTE network, such as a third generation (3G) network.

Environment200may include an evolved packet system (EPS) that includes an LTE network and/or an evolved packet core (EPC) that operate based on a third generation partnership project (3GPP) wireless communication standard. The LTE network may include a radio access network (RAN) that includes one or more base stations215that take the form of evolved Node Bs (eNBs) via which mobile devices205communicate with the EPC. The EPC may include MME215, SGW220, PGW225, and sponsored data enforcement device230that enable mobile devices205to communicate with an Internet protocol (IP) multimedia subsystem (IMS) core. The IMS core may include sponsored data control device235and/or AAA240, and may manage device registration and authentication, session initiation, campaign information, etc., associated with mobile devices205. Sponsored data control device235and/or AAA240may reside in the EPC and/or the IMS core.

Mobile device205may include one or more devices capable of communicating with base station210and/or the LTE network. For example, mobile device205may include a wireless communication device, a radiotelephone, a personal communications system (PCS) terminal (e.g., that may combine a cellular radiotelephone with data processing and data communications capabilities), a smart phone, a laptop computer, a tablet computer, a personal gaming system, and/or a similar device. Mobile device205may send traffic to and/or receive traffic from the LTE network (e.g., via base station210, SGW220, and/or PGW225).

Base station210may include one or more devices capable of transferring traffic, such as audio, video, text, and/or other traffic, destined for and/or received from mobile device205. In some implementations, base station210may include an eNB associated with the LTE network that receives traffic from and/or sends traffic to the network via SGW220and/or PGW225. Additionally, or alternatively, one or more base stations210may be associated with a RAN that is not associated with the LTE network. Base station210may send traffic to and/or receive traffic from mobile device205via an air interface. In some implementations, base station210may include a small cell base station, such as a base station of a microcell, a picocell, and/or a femtocell.

MME215may include one or more devices, such as one or more server devices, capable of managing authentication, activation, deactivation, and/or mobility functions associated with mobile device205. In some implementations, MME215may perform operations relating to authentication of mobile device205. Additionally, or alternatively, MME215may facilitate the selection of a particular SGW220and/or a particular PGW225to serve traffic to and/or from mobile device205. MME215may perform operations associated with handing off mobile device205from a first base station210to a second base station210when mobile device205is transitioning from a first cell associated with the first base station210to a second cell associated with the second base station210. Additionally, or alternatively, MME215may select another MME (not pictured), to which mobile device205should be handed off (e.g., when mobile device205moves out of range of MME215).

SGW220may include one or more devices capable of routing packets. For example, SGW220may include one or more data processing and/or traffic transfer devices, such as a gateway, a router, a modem, a switch, a firewall, a network interface card (NIC), a hub, a bridge, a server device, an optical add/drop multiplexer (OADM), or any other type of device that processes and/or transfers traffic. In some implementations, SGW220may aggregate traffic received from one or more base stations210associated with the LTE network, and may send the aggregated traffic to the network (e.g., via PGW225) and/or other network devices associated with the EPC and/or the IMS core. SGW220may also receive traffic from the network and/or other network devices, and may send the received traffic to mobile device205via base station210. Additionally, or alternatively, SGW220may perform operations associated with handing off mobile device205to and/or from an LTE network.

PGW225may include one or more devices capable of providing connectivity for mobile device205to external packet data networks (e.g., other than the depicted EPC and/or LTE network). For example, PGW225may include one or more data processing and/or traffic transfer devices, such as a gateway, a router, a modem, a switch, a firewall, a NIC, a hub, a bridge, a server device, an OADM, or any other type of device that processes and/or transfers traffic. In some implementations, PGW225may aggregate traffic received from one or more SGWs220, and may send the aggregated traffic to the network. Additionally, or alternatively, PGW225may receive traffic from the network, and may send the traffic to mobile device205via SGW220and base station210. PGW225may record data usage information (e.g., byte usage), and may provide the data usage information to AAA240.

Sponsored data enforcement device230may include one or more devices capable of inspecting traffic and applying one or more provisioning rules to the traffic. For example, sponsored data enforcement device230may include a gateway, a router, a modem, a switch, a firewall, a NIC, a hub, a bridge, a server, an OADM, or a similar type of device. Sponsored data enforcement device230may receive provisioning rules from sponsored data control device235, may apply the provisioning rules to traffic received from PGW225, and may instruct PGW225how to handle the traffic based on the provisioning rules. Additionally, or alternatively, sponsored data enforcement device230may instruct AAA240how to charge for data usage associated with the traffic.

Sponsored data control device235may include one or more devices capable of receiving, generating, storing, processing, and/or providing information associated with a creating a message, associated with user sponsored media content. For example, sponsored data control device235may include a server or a similar type of device. Sponsored data control device235may receive user sponsored media content and provisioning information from mobile device205. Sponsored data control device235may create a message based on the provisioning information and associated with the user sponsored media content. Sponsored data control device235may generate provisioning rules based on the provisioning information, and may deploy the provisioning rules to one or more sponsored data enforcement devices230(e.g., associated with one or more cellular service areas).

AAA240may include one or more devices, such as one or more server devices, that perform authentication, authorization, and/or accounting operations for communication sessions associated with mobile device205. For example, AAA240may perform authentication operations for mobile device205and/or a user of mobile device205(e.g., using one or more credentials), may control access, by mobile device205, to a service and/or an application (e.g., based on one or more restrictions, such as time-of-day restrictions, location restrictions, single or multiple access restrictions, read/write restrictions, etc.), may track resources consumed by mobile device205(e.g., a quantity of voice minutes consumed, a quantity of data consumed, etc.), and/or may perform similar operations.

Recipient mobile device245may include one or more devices capable of communicating with base station210and/or the LTE network. For example, recipient mobile device245may include a wireless communication device, a radiotelephone, a personal communications system (PCS) terminal (e.g., that may combine a cellular radiotelephone with data processing and data communications capabilities), a smart phone, a laptop computer, a tablet computer, a personal gaming system, and/or a similar device. Recipient mobile device245may send traffic to and/or receive traffic from the LTE network (e.g., via base station210, SGW220, and/or PGW225).

FIG. 3is a diagram of example components of a device300. Device300may correspond to mobile device205, base station210, MME215, SGW220, PGW225, sponsored data enforcement device230, sponsored data control device235, AAA240, and/or recipient mobile device245. In some implementations, mobile device205, base station210, MME215, SGW220, PGW225, sponsored data enforcement device230, sponsored data control device235, AAA240, and/or recipient mobile device245may include one or more devices300and/or one or more components of device300. As shown inFIG. 3, device300may include a bus310, a processor320, a memory330, a storage component340, an input component350, an output component360, and a communication interface370.

FIG. 4is a flow chart of an example process400for creating a message to share user sponsored media content. In some implementations, one or more process blocks ofFIG. 4may be performed by sponsored data control device235. In some implementations, one or more process blocks ofFIG. 4may be performed by another device or a group of devices separate from or including sponsored data control device235, such as mobile device205, base station210, MME215, SGW220, PGW225, sponsored data enforcement device230, AAA240, and recipient mobile device245.

As shown inFIG. 4, process400may include receiving user sponsored media content associated with a user sponsored account (block410). For example, a user of mobile device205may create a user sponsored account using a media platform application (e.g., Video Platform Application), provided on mobile device205. To create the user sponsored account, the user of mobile device205may provide account information (e.g., a user name, a password, etc.) to a sponsored data control device (e.g., sponsored data control device235), using mobile device205.

Additionally, or alternatively, the user of mobile device205may obtain media content (e.g., a video file, an audio file, an image file, etc.). In some implementations, the user of mobile device205may create the media content using the user sponsored account and/or the media platform application, provided by mobile device205. In some implementations, the user of mobile device205may receive the media content from another device.

Mobile device205may provide the media content to use as user sponsored media content to sponsored data control device235. Sponsored data control device235may store the user sponsored media content.

As shown inFIG. 4, process400may include associating unused data from a mobile communications service plan to the user sponsored account (block420). For example, sponsored data control device235may receive instructions, from the user of mobile device205, to associate unused data (e.g., all unused data, some unused data, etc.) from a mobile communications service plan, associated with the user of mobile device205, with the user sponsored account (e.g., associate 500 MB of unused data of a 2 GB/month mobile communications service plan to the user sponsored account). In some implementations, the user of mobile device205may specify a quantity of unused data to associate with the user sponsored account.

As shown inFIG. 4, process400may include creating a message associated with the user sponsored media content (block430). For example, sponsored data control device235may receive instructions from the user of mobile device205to create a message associated with the user sponsored media content. The message may be used to access the user sponsored media content by multiple recipients.

Additionally, or alternatively, sponsored data control device235may receive provisioning information, associated with the message, inputted by the user of mobile device205via an interface of mobile device205. Provisioning information may include a particular way of sharing the message (e.g., via e-mail, via social media, via text message, etc.). In some implementations, sponsored data control device235may link an external account, used for sharing the message, to the user sponsored account (e.g., linking a social media account, associated with the user, to the user sponsored account; linking an e-mail program, associated with the user, to the user sponsored account, etc.).

In some implementations, the message may be shared directly from the user sponsored account without linking the user sponsored account to an external account.

The provisioning information may include a quantity of recipients (e.g., users of recipient mobile devices245) to receive the message (e.g., 5 contacts from a contact list, 10 contacts from a contact list, all contacts from a contact list, etc.). In some implementations, sponsored data control device235may receive the identifier, associated with the recipients, from a contacts list associated with the user sponsored account. In some implementations, sponsored data control device235may receive the identifier, associated with the recipients, from a contacts list associated with the external account.

The provisioning information may also or alternatively include a validity period for the recipients to access the user sponsored media content (e.g., the user sponsored media content may be accessed for 24 hours after a time the message was provided to the recipient; the user sponsored media content may be accessed for 1 week after a time the message was provided to the recipient; the user sponsored media content may be accessed for 1 month after a time the message was provided to the recipient; etc.).

The provisioning information may also include a variety of additional instructions. For example, the additional instructions may specify that only a recipient of the message, as identified by the provisioning information, may access the user sponsored media content. The additional instructions may specify that the recipient may not broadcast the user sponsored media content associated with the message. The additional instructions may specify that each recipient may only access one URL, included in the message, and associated with the user sponsored media content. These are only a few examples of additional instructions and/or provisioning information and other examples of additional instructions and/or provisioning information may be possible.

Additionally, or alternatively, sponsored data control device235may generate provisioning rules, based on the provisioning information. A provisioning rule may specify one or more provisioning conditions for enabling a user of recipient mobile device245to access the user sponsored media content associated with the message.

For example, provisioning rules may identify, based on the provisioning information, a valid time period during which a recipient of the message may access the user sponsored media content, using the URL included in the message. Additionally, or alternatively, provisioning rules may identify a quantity of data (e.g., in bytes), based on the provisioning information, to be allocated to the user sponsored account. Additionally, or alternatively, provisioning rules may identify additional instructions, based on the provisioning information, for permitting a recipient of the message to access/use the user sponsored media content using the URL included in the message.

Sponsored data control device235may combine the generated provisioning rules into a configuration file, and may provide the configuration file to one or more sponsored data enforcement devices230so that the one or more sponsored data enforcement devices230may determine whether to permit the recipient of the message access to the user sponsored media content, using the URL included in the message.

Additionally, or alternatively, sponsored data control device235may receive authorization to use the unused data to access the user sponsored media content through creating the message, based on the user interacting with an input mechanism on a display of the user device.

Additionally, or alternatively, sponsored data control device235may create digital tokens, equal in quantity to the quantity of recipients selected by the user (e.g., create 10 digital tokens based on the provisioning information specifying10recipients for the message).

A digital token is an electronic key that may be encrypted and may include token information associated with the media content file (e.g., an identifier for a creator of the user sponsored media content, a mobile directory number (MDN), an identifier associated with the user sponsored media content, the quantity of unused data associated with the user sponsored account, the validity period for accessing the user sponsored media content, etc.). The digital token may be encrypted using an encryption algorithm (e.g., a hash-based message authentication code-secure hash algorithm (HMAC-SHA) 256).

Sponsored data control device235may create the digital tokens as signing key pairs. Additionally, or alternatively, sponsored data control device235may create uniform resource locators (URLs), equal in quantity to the quantity of digital tokens, where each URL may include a digital token.

Additionally, or alternatively, sponsored data control device235may associate the media content with each URL created. Additionally, or alternatively, sponsored data control device235may create the message for distribution to the recipients (e.g., users of recipient mobile device245). The message may include a URL. Additionally, or alternatively, sponsored data control device235may store the signing key pairs, including the token information. In some implementations, sponsored data control device235may provide the digital token, including the token information, to sponsored data enforcement device230. In some implementations, sponsored data control device235may provide the signing key pair, including the token information, to sponsored data enforcement device230.

As shown inFIG. 4, process400may include providing the message associated with the user sponsored media content (block440). For example, sponsored data control device235may provide the message to the recipients (e.g., users of recipient mobile devices245), via sponsored data enforcement device230, to share the user sponsored media content.

FIGS. 5A-5Jare diagrams of an example implementation500relating to example process400shown inFIG. 4.FIGS. 5A-5Jshow an example of a process for creating a message to share user sponsored media content.

As shown inFIG. 5A, assume a user of a mobile communications service has unused data (e.g., 2 GB of unused data during a billing cycle associated with a mobile communications service plan).

As shown inFIG. 5A, and by reference number505, a user of a mobile device (e.g., mobile device205) provides account information to create a user sponsored account (e.g., User Sponsored Account), via a media platform application (e.g., Video Platform Application), provided on mobile device205. The media platform application and/or the user sponsored account is associated with a service provider (e.g., a mobile communications service provider).

As shown inFIG. 5A, and by reference number510, sponsored data control device235, associated with the service provider, receives the account information and creates the user sponsored account.

As shown inFIG. 5B, and by reference number515, the user may upload media content using the media platform application to sponsored data control device235to use as user sponsored media content. As shown inFIG. 5C, and by reference number520, sponsored data control device235receives and stores the user sponsored media content.

As shown inFIG. 5D, and by reference number525, sponsored data control device235associates the unused data with the user sponsored account, based on instructions received by the user of mobile device205to associate the unused data with the user sponsored account (e.g., associate the 2 GB of unused data available from a mobile communications service plan, associated with the user of mobile device205, with the user sponsored account). As shown inFIG. 5E, and by reference number530, the user of mobile device205selects to share the user sponsored media content (e.g., a gift bag that includes a URL, associated with the user sponsored media content, that may be used to access the user sponsored media content by multiple recipients), by interacting with an input mechanism.

As shown in shown in5F, and by reference number535, the user inputs provisioning information to mobile device205to share the user sponsored media content in a particular way (e.g., via social media).

As shown inFIG. 5G, and by reference number540, the user continues to input provisioning information to mobile device205, by providing one or more identifiers, associated with users of recipient mobile devices245(e.g., User2, User3, User4, etc.).

As shown inFIG. 5H, and by reference number545, the user continues to input provisioning information to mobile device205, by providing a valid time period for recipients to access the user sponsored media content (e.g. an active time period for recipients to access the user sponsored media content with a start date=6/15/15 and an end date=6/22/15).

As shown inFIG. 5H, and by reference number550, sponsored data control device235receives the provisioning information and authorization to use the unused data to create the gift bag, based on the user interacting with an input mechanism on mobile device205(e.g., the user clicks a “Send Gift Bag” button).

As shown inFIG. 5I, and by reference number555, sponsored data control device235creates digital tokens (e.g., Token 1, Token 2, Token 3, etc.), equal in quantity to the quantity of recipients selected by the user, including token information. As shown inFIG. 5I, and by reference number560, sponsored data control device235creates URLs (e.g., /token 1, /token 2, /token 3, etc.) using the digital tokens (e.g., /token 1 including Token 1, /token 2 including Token 2, /token 3 including Token 3, etc.) and associates the URLs with the user sponsored media content. As shown inFIG. 5I, and by reference number565, sponsored data control device235creates the gift bag, including the URLs.

As shown inFIG. 5J, and by reference number570, sponsored data control device235provides provisioning rules, based on provision information to create provisioning conditions, to sponsored data device230. As shown inFIG. 5J, and by reference number575, sponsored data control device235provides the gift bag, in the form of a message, to users of recipient mobile devices245(e.g., Recipient1of Recipient Mobile Device245-1, Recipient10of Recipient Mobile Device245-10, etc.), via sponsored data enforcement device230.

As indicated above,FIGS. 5A-5Jare provided merely as an example. Other examples are possible and may differ from what was described with regard toFIGS. 5A-5J.

FIG. 6is a flow chart of an example process600for accessing user sponsored media content. In some implementations, one or more process blocks ofFIG. 6may be performed by sponsored data enforcement device230. In some implementations, one or more process blocks ofFIG. 6may be performed by another device or a group of devices separate from or including sponsored data enforcement device230, such as mobile device205, base station210, MME215, SGW220, PGW225, sponsored data control device235, AAA240, and recipient mobile device245.

As shown inFIG. 6, process600may include receiving a request to access user sponsored media content (block610). For example, a user of recipient mobile device245may receive a message (e.g., via social media) on recipient mobile device245. The message may include a single URL to the user sponsored media content, some of the URLs (created in connection with block430above), or all of the URLs (created in connection with block430above). Upon selection of a URL, recipient mobile device245may send a request to access the user sponsored media content to sponsored data enforcement device230. In some implementations, sponsored data enforcement device230may receive a digital token in or with the request to access the user sponsored media content.

As further shown inFIG. 6, process600may include determining whether the digital token is valid (block620). For example, sponsored data enforcement device230may identify an identifier, for a creator of the user sponsored media content, from token information included in the digital token. Additionally, or alternatively, sponsored data enforcement device230may retrieve stored token information, associated with the identifier for the creator, from a memory associated with sponsored data enforcement device230. In some implementations, sponsored data enforcement device230may retrieve stored token information, associated with the identifier for the creator, from sponsored data control device235.

Additionally, or alternatively, sponsored data enforcement device230may compare the token information with the stored token information. If the token information matches the stored token information, then the digital token is valid. If the token information does not match the stored token information, then the digital token is not valid.

In some implementations, sponsored data enforcement device230may retrieve a signing key pair, associated with the identifier for the creator, from the memory associated with sponsored data enforcement device230. In some implementations, sponsored data enforcement device230may retrieve a signing key pair, associated with the identifier for the creator, from sponsored data control device235.

Additionally, or alternatively, sponsored data enforcement device230may create a second digital token based on the signing key pair, using an encryption algorithm used to create the digital token. In some implementations, sponsored data enforcement device230may retrieve the second digital token from sponsored data control device235.

Additionally, or alternatively, sponsored data enforcement device230may compare the second digital token with the digital token. If the second digital token matches the digital token, then the digital token is valid. If the second digital token does not match the digital token, then the digital token is not valid.

As further shown inFIG. 6, if the digital token is not valid (block620—No), then process600may include providing a notification that the user sponsored media content cannot be accessed (block630). For example, sponsored data enforcement device230may provide a notification that the user sponsored media content cannot be accessed. In some implementations, sponsored data enforcement device230may provide a reason to recipient mobile device245so that the user of recipient mobile device245may understand why the user sponsored media content cannot be accessed (e.g., the digital token is not valid).

As further shown inFIG. 6, if the token is valid (block620—Yes), process600may include determining whether provisioning conditions are satisfied (block640). For example, sponsored data enforcement device230may determine whether one or more provisioning conditions are satisfied. Provisioning conditions may be identified in provisioning rules received from sponsored data control device235.

As an example, a provisioning condition may specify a valid time period during which the user sponsored media content may be accessed. If the request to access the user sponsored media content is received during the valid time period, then the provisioning condition may be satisfied. If the request to access the user sponsored media content is not received during the valid time period, then the provisioning condition may not be satisfied.

As another example, a provisioning condition may specify a quantity of unused data (e.g., bytes), associated with the user sponsored account, that may be allocated for accessing the user sponsored media content. Sponsored data enforcement device230may determine whether there are any bytes, out of the allocated amount of bytes, available to be allocated to the request to access user sponsored media content.

For example, sponsored data enforcement device230may periodically request and/or may periodically receive, from sponsored data control device235, information that identifies a quantity of available bytes (e.g., available unused data). Sponsored data control device235may receive information regarding used bytes from one or more sponsored data enforcement devices230, and may update the quantity of available bytes based on the received information. If there are available bytes to be allocated to the request to access the user sponsored media content, then the provisioning condition may be satisfied. If there are no available bytes (or not enough available bytes) to be allocated to the user sponsored media content, then sponsored data enforcement device230may determine that the provisioning conditions are not satisfied.

As further shown inFIG. 6, if the provisioning conditions are not satisfied (block640—No), process600may include providing a notification that the user sponsored media content cannot be accessed (block630). For example, sponsored data enforcement device230may provide a notification that the user sponsored media content cannot be accessed. In some implementations, sponsored data enforcement device230may provide a reason to recipient mobile device245so that the user of recipient mobile device245may understand why the user sponsored media content cannot be accessed (e.g., the digital token is not valid based on the provisioning conditions not being satisfied).

As further shown inFIG. 6, if the provisioning conditions are satisfied (block640—Yes), process600may include providing access to the user sponsored media content (block650). For example, sponsored data enforcement device230may provide access to the user sponsored media content to the user of recipient mobile device245. Additionally, or alternatively, sponsored data enforcement device230may provide information that causes a traffic flow, associated with the user of recipient mobile device245accessing the user sponsored media content, to charge data usage against the unused data allocated to the user sponsored media content. In some implementations, sponsored data enforcement device230may mark the traffic flow and/or packets associated with the traffic flow as being associated with the user sponsored media content.

As an example, sponsored data enforcement device230may provide information to PGW225to mark packets, associated with the traffic flow so that data charges may be charged against the unused data associated with the user sponsored account. PGW225may route traffic (e.g., packets) associated with a requested service (e.g., the request to access the user sponsored media content).

Additionally, or alternatively, PGW225and/or sponsored data enforcement device230may count a quantity of data (e.g., in bytes) used in association with the requested service, and may provide data usage information (e.g., that identifies a quantity of data used) to AAA240. Additionally, or alternatively, sponsored data enforcement device230and/or PGW225may provide an instruction, to AAA240, that causes the data used in association with the requested service to be deducted from the unused data allocated to the user sponsored account.

In some implementations, sponsored data enforcement device230and/or PGW225may provide an instruction, to AAA240, that causes data charges, for the traffic flow associated with access to the user sponsored media content to be charged against the unused data associated with the user sponsored account, in real-time or in near real-time. In some implementations, sponsored data enforcement device230and/or PGW225may provide an instruction, to AAA240, that causes data charges, for the traffic flow associated with access to the user sponsored media content, not to be charged against data associated with a mobile communications service plan, associated with a user of recipient mobile device245.

Additionally, or alternatively, sponsored data enforcement device230and/or PGW225may provide an instruction, to AAA240, that causes data charges, for the traffic flow associated with access to the user sponsored media content, that were charged against data associated with the mobile communications service plan, associated with a user of the recipient mobile device, to be credited.

FIGS. 7A-7Bare diagrams of an example implementation700relating to example process600shown inFIG. 6and relating to diagrams of example implementation500shown inFIGS. 5A-5J.FIGS. 7A-7Bshow an example of accessing user sponsored media content.

As shown inFIG. 7A, assume a user (e.g., Recipient) of recipient mobile device245receives a message relating to user sponsored media content. As shown inFIG. 7A, and by reference number710, a sponsored data enforcement device (e.g., sponsored data enforcement device230) receives a request from the user of recipient mobile device245to access user sponsored media content (e.g., a video file with a file size of 200 MB), based on the user clicking on a URL link:/ token 1 provided in the message). As shown inFIG. 7A, and by reference number720, sponsored data enforcement device230determines that a digital token, received with the request to access the user sponsored media content is valid and that provisioning conditions are satisfied (e.g., the request to access the user sponsored media content on 6/17/15 is within the active time period between 6/15/15 and 6/22/15; 2 GB of unused data is available, etc.).

As shown inFIG. 7B, and by reference number730, sponsored data enforcement device230provides the user sponsored media content. As shown inFIG. 7B, and by reference number740, sponsored data enforcement device230provides information to PGW225to mark packets associated with traffic flow for accessing the user sponsored media content. As shown inFIG. 7B, and by reference number750, sponsored data enforcement device230and/or PGW225may provide data usage information to AAA240(e.g., AAA240receives data usage information and determines that 1800 MB of available unused data remains after the Recipient accesses the video file with the file size of 200 MB, using token 1).

As indicated above,FIGS. 7A-7Bare provided merely as an example. Other examples are possible and may differ from what was described with regard toFIGS. 7A-7B.

By permitting a user of a mobile device to share user sponsored media content, using a user sponsored account that allows recipients of the user sponsored media content (e.g., users of recipient mobile devices) to access the user sponsored media content using the user's unused data from a mobile communications service plan, network resources of a service provider, associated with the user sponsored account and the mobile communications data plan, may be used effectively and efficiently, thereby improving the service provider's network performance.