Tracking data usage under a schematized data plan.

TRACKING DATA USE UNDER A SCHEMATICED DATA PLAN

This application refers to the following applications: US Patent Application titled Handling of Data Transfers through Network Connections Based on Priority and a Data Use Plan, US Patent Application titled Attribution on Data Use Device Network, US Patent Application entitled Network Data Consumption Prediction Regarding Data Use Patterns, US Patent Application entitled "Update of Plans and Statistics on the Use of Dynamic Data", US Patent Application entitled Profiles of Data Use for Users and Applications, US patent application entitled Recommendations to Reduce Data Consumption Based on Data Use Profiles , US Patent Application titled Dynamically Adjust a Data Use Plan Based on Data Use Statistics, and US Patent Application titled Management of Network Data Transfers in Vista of Multiple Data Use Plans. All these applications are incorporated here by reference in their duality.

BACKGROUND

With the increased popularity of smartphones, tablets, and other mobile devices, there has been a similar increase in the amount of data handled by mobile operator networks. To reduce the tension in a network infrastructure and to reduce network transfer costs, mobile operators are changing from offering unlimited mobile data plans to offering covered and measured plans. With some of the plans covered and measured, the fees for exceeding the assigned data goals can be significant. Although some existing web browsers try to optimize data traffic, existing systems generally lack mechanisms to balance each user's specific needs with data transfer costs. In addition, some of the existing systems are unable to track and accurately attribute the amount of data consumed under the plans.

As a result, with existing systems, users can exceed the assigned data covers in an unknown way and experience bandwidth regulation (for example, a reduction or limit placed on the consumption rate) and / or present with an invoice Monthly larger than normal, resulting in billing impact. Billing impact regulation can impact the user experience, leading to unsatisfied consumers, increased consumer service calls, and negative impressions of mobile operators.

BRIEF DESCRIPTION OF THE INVENTION

In the modalities of the description, data usage statistics are referred to and represented through a scheme. The scheme represents a data usage plan associated with at least one user. The data usage plan describes threshold values ​​associated with network connections of a plurality of user computing devices. The web service collects data from a mobile operator and / or the plurality of user computing devices. Data usage statistics are generated from the data collected, and represent data consumed under the data usage plan. The scheme is updated with data usage statistics generated and distributed to the plurality of computing devices.

This Brief Description is provided to introduce a selection of concepts in a simplified form that is further described below in the Detailed Description. This Brief Description is not intended to identify key characteristics or essential characteristics of the claimed issue, nor is it intended as an auxiliary when determining the scope of the claimed issue.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is an illustrative block diagram showing user computing devices that communicate over one or more networks.

Figure 2 is an illustrative flow chart showing the operation of a web service to track network data consumed by a plurality of user computing devices under a data usage plan.

Figure 3 is an illustrative flow chart showing the operation of a computing device to fill a scheme with statistics on the network data consumed by the computing device under a data usage plan.

Figure 4 is an illustrative user interface showing a summary of network data usage with different types of network connections.

Figure 5A is an illustrative user interface showing the use of data by a mobile computing device that consumes network data under a data usage plan with a monthly limit.

Figure 5B is an illustrative user interface showing the use of data by a mobile computing device that consumes network data under a usage plan of payment-for-consumption data.

Figure 5C is an illustrative user interface showing the use of data by a mobile computing device that consumes network data under a data usage plan with unlimited data usage.

Figure 6 is an illustrative block diagram showing a mobile computing device that has a mosaic for presenting network data usage statistics to a user.

Corresponding reference characters indicate corresponding parts throughout the drawings.

DETAILED DESCRIPTION

Referring to the figures, the modalities of the description allow the collection in a scheme 116 of data referring to network transfers by a plurality of computing devices. In some embodiments, a centralized service such as a web service 108 verifies the consumption of data by one or more of the computing devices under a data usage plan. For example, the web service 108 may receive data usage statistics 120 from the computing devices and / or from one or more mobile operators 111 associated with the data usage plan. Web service 108 presents the data usage statistics 120 to a user 104 in relation to threshold values ​​118 associated with the data usage plan to provide the user 104 with an indication of data usage and trend. In other embodiments, the computing devices, such as a mobile computing device 102, generate the data usage statistics 120 for presentation to the user 104.

Aspects of the description employ scheme 116 such as an extensible markup language (XML) scheme to represent the data usage plan and, in some embodiments, to represent data usage statistics 120. Scheme 116 allows descriptions of the parts, components, services, features, or other aspects of the data usage plan including, but not limited to, multi-speed data plans, peak times, roaming speeds, data consumption assigned by network connection 130, etc. In some embodiments, scheme 116 allows mobile operators 111 to send updated portions of scheme 116 corresponding to updated parts of the data usage plan.

Referring to Figure 1, an illustrative block diagram shows user computing devices that communicate through one or more networks 109. In some embodiments, one or more of the user computing devices are associated with a plan of data usage For example, a plurality of user computing devices can share data assigned under the same or common data usage plan.

User computing devices include any device that executes instructions (for example, such as application programs, operating system functionality, or both) to implement operations and functionality. The user computing devices may include, for example, mobile computing device 102 or any other portable device. In some embodiments, mobile computing device 102 includes a mobile phone, laptop, tablet, computer pad, netbooks, gaming device, electronic reader, and / or portable media player. Other computing devices 106 may include less portable devices such as personal desktop computers, kiosks, and desktop devices that have network connectivity capabilities. Additionally, each user computing device may represent a group of processing units. Although aspects of the description may be described herein with reference to mobile computing device 102, the descriptions are applicable to any of the user computing devices.

Communication between the mobile computing device 102 and other devices can occur using a protocol or mechanism by one or more of the networks 109. The networks 109 represent any infrastructure or other means to send and / or receive data. Networks 109 may include wired and / or wireless networks.

The user computing devices communicate with the web service 108, or another entity that tracks network data consumption through the user computing devices. In addition, one or more of the mobile operators 116 communicate with the web service 108 and / or the user computing devices.

In some embodiments, the mobile computing device 102 has at least one processor 110 and a memory area 112. The processor 110 includes any number of processing units, and is programmed to execute computer executable instructions to implement aspects of the description. The descriptions may be made by the processor 110 or through multiple processors that are executed within the mobile computing device 102, or made by a processor external to the mobile computing device 102. In some embodiments, the processor 110 is programmed to execute instructions such as those illustrated in the figures (for example, Figure 3).

In some embodiments, processor 110 represents an implementation of analog techniques to perform the operations described herein. For example, operations can be performed by an analog computing device and / or a digital computing device.

The mobile computing device 102 also has one or more computer-readable media such as the memory area 112. The memory area 112 includes any amount of media associated with or accessible by the mobile computing device 102. The memory area 112 it can be internal to mobile computing device 102 (as shown in Figure 1), external to mobile computing device 102 (not shown), or both (not shown). In some embodiments, the memory area 112 includes read-only memory and / or wired memory within an analog computing device.

The memory area 112 stores, among other data, one or more applications 114. The applications 114, when executed by the processor 110, operate to perform functionality in the mobile computing device 102. Illustrative applications 114 include mail application programs, web browsers, calendar application programs, calendar application programs, messaging programs, media applications, location-based services, search programs, and the like. Applications 114 can communicate with counterpart applications or services such as web services 108 accessible through network 109. For example, applications 114 may represent downloaded client-side applications that correspond to server-side services running in a cloud.

The memory area 112 also stores at least one scheme 116. Scheme 116 represents a data usage plan associated with the user 104, and can be filled with the data usage statistics 120. For example, the user 104 has hired the mobile operator 116 to receive network transfer services from the mobile operator 111. The data usage plan describes the services provided by the mobile operator 111, such as the amount of network data that the user 104 can consume for a particular duration (for example, a billing time period). For example, the data usage plan describes threshold values ​​118 associated with network connections 130 of one or more user devices 104. Network connections 130 represent communication channels or other means for sending and / or receiving data through network 109. Illustrative network connections 130 include, but are not limited to, Wi-Fi, cellular, wireless, communication Bluetooth brand, near field communication (NFC), and more. Network connections 130 may be classified into voice, text, data, or other categories or types of network traffic. The threshold values ​​118 represent the maximum amount of data consumption allocated for network connections 130. For example, a threshold value 118 may indicate the maximum amount of data consumption for a Wi-Fi connection, while another threshold value 118 indicates a maximum amount of data consumption for a cellular data connection.

Aspects of the description are operable with any number of filled schemes 116. Each of the filled out schemes 116 is associated with a different data usage plan, for example, mobile computing device 102 may have more than one cellular connection, and each of the network connections operates independently (for example, multiple radios that operate independently of each other). In such modalities, there may be multiple plans for the use of active data per cellular connection. Illustrative environments include dual active dual subscriber identity module (SIM) devices (both independently active connections) or dual SIM standby devices (one connection is in a standby mode). Additional examples include virtual SIMs, universal integrated circuit cards (UICC), and other user identity module variants.

In some embodiments, scheme 116 includes a plurality of fields. Each of the threshold values ​​118 may be associated with one or more of the fields. For example, the fields may correspond to one or more of the following: peak times, peak off-peak time, peak time data consumption rate, peak time data consumption rate, remaining peak time data consumption, remaining peak time data consumption, a speed of ¡ tinerance and rules, and a mobile operator name, a type of billing cycle, a type of network connection, identification of free or reduced cost hosts available for connection, a list of mobile hot spots, and any other information elements that belong to the data usage plan. The group of free or reduced cost hosts represents hosts evaluated at zero or other low cost (for example, visiting particular websites does not count against the data usage plan) or data types (for example, courier service data multimedia). In some modalities, hosts evaluated at reduced cost zero or data can be identified in a blacklisted form.

Scheme 116 may also include fields that support different billing speeds per accessed host, and allow each mobile operator 111 the flexibility to define complex plans including widely offered plans, and dynamic, short-term offers for specific users 104 who are likely to use a specific part or parts of general services. Other offers based on any combination of the metric obtained are available to mobile operator 111.

Scheme 116 may also include fields that correspond to data usage statistics 120 collected or generated by mobile computing device 102, web service 108, and / or mobile operator 111.

Although schema 116 can take any form or structure, schema 116 can be implemented as an XML schema. Annex A includes an illustrative XML scheme for use in aspects of the description.

The data usage statistics 120 identify, for a granularity of time (for example, per minute) or data (for example, per kilobytes), how much data has been sent and / or received by the mobile computing device 102 or the others. computing devices 106, and through which network connections 130. However, other data usage statistics 120 are contemplated. The data usage statistics 120 can be generated by the mobile computing device 102, by the web service 108, and / or by the mobile operator 111. For example, the mobile computing device 102 may collect the data usage statistics 120 representing network data consumed by the mobile computing device 102, and then update the data usage statistics 120 with information received from the web service 108 representing network data consumed by other computing devices 106 of user 104 (for example, associated with the same data usage plan).

In some embodiments, if the web service 108 detects that the mobile computing device 102 has old or obsolete data usage statistics 120, the web service 108 may send a notification to the mobile computing device 102 to synchronize the data usage statistics 120 directly with mobile operator 111 or with web service 108.

The memory area 112 also stores one or more computer executable components. Illustrative components include a collection component 122, a data structure component 124, a communications interface component 126, and a user interface component 128. The operation of the components, when executed, is described below with reference Figure 3.

In some embodiments, the communication interface component 126 includes a network interface card and / or computer executable instructions (eg, a controller) for operating the network interface card. In some embodiments, the communications interface is operable with near field communication (NFC) tags.

The user interface component 128 may include a graphics card to present data to user 104 and receive data from user 104. The user interface component 128 may also include computer executable instructions (eg, a controller) for operating The graphics card. In addition, the user interface component 128 may include a presentation (for example, a touch screen presentation or natural user interface) and / or computer executable instructions (for example, a controller) to operate the presentation. The user interface component 128 may also include one or more of the following to provide data to the user 104 or receive data from the user 104: speakers, a sound card, a camera, a microphone, a vibration motor, one or plus accelerometers, a Bluetooth brand communication module, global positioning system (GPS) hardware, and a photo receiver light sensor. For example, user 104 can enter commands or manipulate data by moving the computing device in a particular way.

Referring later to Figure 2, an illustrative flow chart shows the operation of web service 108 to track network data consumed by user computing devices under the data usage plan. In 202, the web service 108 defines the scheme 116 that represents the data usage plan. The definition of scheme 116 includes, for example, defining scheme 116 for use by mobile operator 111. Alternatively or in addition, the definition of the scheme 116 includes receiving the scheme 116 from the mobile operator 111. The scheme 116 represents the data usage plan associated with one or more of the users 104.

At 204, the web service 108 dynamically generates the data usage statistics 120 for the user 104. The data usage statistics 120 represent data consumed under the data usage plan by one or more of the computing devices associated with the user 104. The data usage statistics 120 can be seen as a current or instantaneous screenshot of the amount of data transmitted and / or received by the user computing devices 104 that share the data usage plan. Web service 108 may collect information that refers to text messages, voice calls, minutes used, use of voice over Internet Protocol (VolP), and any other element of use consumed by, or impacting, computing devices of user to produce data usage statistics 120.

Dynamically generating the data usage statistics 120 may include receiving data from the user computing devices and / or from the mobile operator 111. The data corresponds to! at least a portion of the data usage statistics 120 and can be received in a format that suits scheme 116. For example, mobile operator 111 may have more current and / or more accurate data usage statistics 120 for one or more of the user computing devices than the user computing devices. As another example, mobile operator 111 may have more current and / or more accurate data usage statistics 120 for some of the network connections 130 than user computing devices. The mobile operator 111 may drive, or transmit on demand, such data usage statistics 120 to the web service 108. The web service 108 integrates the data from the mobile operator 111 and / or the user computing devices to produce the statistics of data usage 120.

Web service 108 can also generate data usage statistics 120 by comparing data collected from mobile operators 111 with data collected from user computing devices. For example, the web service 108 may receive first data corresponding to at least a portion of the data usage statistics 120 from the mobile operator 111, and receive second data corresponding to at least a portion of the data usage statistics. 120 from one or more of the user computing devices. If there are differences

<td>(for example,</td><td>the</td><td>data from</td><td>the</td><td>operator</td><td>mobile</td><td colspan="2">111 can be of</td>

<td>24-48 hours</td><td>from</td><td>antiquity),</td><td>the</td><td>service</td><td>Web</td><td>108 reconciles</td><td>the</td>

<td colspan="2">differences for</td><td>provide</td><td>to the</td><td>user</td><td> 104</td><td>information</td><td>plus</td>

current. Continuing with the previous example, web service 108 can reconcile the first data received and the second data received to produce dynamically generated data usage statistics.

Reconciling differences in data received from mobile operators 111 and / or user computing devices include, for example, examining registration dates or other collection dates and favoring, weighing, or choosing the most recently collected data. Continuing with the previous example, reconciling the first data received and the second data received includes, for example, comparing a registration date associated with the first data received and a registration date associated with the second data received. The web service 108 may integrate data that has the subsequent, or most recent, date of registration into the data usage statistics 120.

In 206, the web service 108 updates the defined scheme 116 with the dynamically generated data usage statistics 120. For example, the web service 108 fills a data structure that adapts to the defined scheme 116 with the data usage statistics 120 In 208, the web service 108 distributes the updated scheme 116 to the plurality of user computing devices 104 that share the same data usage plan. The plurality of computing devices can then update any of the locally stored copies of the data usage statistics 120 to reflect the current or updated network data consumed under the data usage plan.

At 210, the web service 108 may present the data usage statistics 120 to the user 104. For example, the data usage statistics 120 may be presented to the user 104 at various user interfaces (eg, see Figure 4, Figure 5A , Figure 5B, Figure 5C, and Figure 6).

Although Figure 2 shows the illustrative scenario of the web service 108 that collects data usage statistics 120, updates scheme 116, and distributes scheme 116 to user computing devices, similar operations can be performed by computing devices. user, as described below with reference to Figure 3.

Referring later to Figure 3, an illustrative flow chart shows the operation of a computing device to fill scheme 116 with statistics on the network data consumed by the computing device under the data usage plan. Although described below with reference to the mobile computing device 102 that executes the operations illustrated in Figure 3, the operations can also be performed by the other computing devices 106 of the user 104.

In 302, the mobile computing device 102 dynamically generates the data usage statistics 120 for the user 104. For example, the mobile computing device 102 collects continuous usage data that refers to network data transfers, such as from device radios, controllers, and accelerometers. The usage data collected includes, for example, the amount of data consumed, the time and date of use, the location of use, network interface used, the SIM card or other user identity module used for dual SIM scenarios, the international mobile station equipment (IMEI) identity or other device identifier for multiple device scenarios, the IP or other address of the access point used for Wi-Fi scenarios, the IP or other address of the target computer (for example, for whitelists / blacklists in data usage), and the application responsible for data transfer.

In 304, mobile computing device 102 fills scheme 116 (eg, stored in memory area 112) with dynamically generated data usage statistics 120. In 306 mobile computing device 102 provides at least a portion of the filled scheme 116 to web service 108 for distribution to other computing devices 106 of user 104. Alternatively or in addition, the mobile computing device 102 may distribute the full scheme 116, or a portion thereof, to the other computing devices 106 of the user 104. The mobile computing device 102 can also dynamically display data usage statistics. generated 120 to the user 104 in a user interface of the mobile computing device 102.

The mobile computing device 102 may also send and receive portions of the scheme 116 that represent the data usage plan. For example, the mobile computing device 102 can load only a portion of the filled scheme 116 to the web service 108 at a particular time or during a particular time interval. As another example, the mobile computing device 102 can download only a portion of the scheme 116 from the web service 108 at a particular time or during a particular time interval.

In some embodiments, mobile computing device 102 executes the computer executable components illustrated in Figure 1 to implement one or more of the operations illustrated in Figure 3. For example, collection component 122, when executed by the processor 110, causes processor 110 to dynamically generate data usage statistics 120. Data structure component 124, when executed by processor 110, causes processor 110 to fill scheme 116 with data usage statistics 120 *

dynamically generated by the collection component 122. The communications interface component 126, when executed by the processor 110, causes the processor 110 to transmit the scheme 110 filled by the data structure component 124 to the web service 108 for distribution to the other computing devices 106 of the user 104. The communications interface component 126 can also receive the scheme 116 filled with details of the data usage plan from the web service 108 and / or from the mobile operator 111. The communications interface component 126 can also receive updated versions of the scheme 116 , or portions thereof.

The user interface component 128, when executed by the processor 110, causes the processor 110 to present the data usage statistics 120 dynamically generated by the collection component 122 to the user 104. For example, the user interface component 128 can present the use of data and a trend analysis.

Referring later to Figure 4, an illustrative user interface 402 shows a summary of network data usage with different types of network connections 130. Although the proportions of the user interfaces 402, 502, 504, 506 illustrated in Figure 4, Figure 5A, Figure 5B, Figure 5C, and Figure 6 are shown to fit a screen of the mobile computing device 102 (for example, a mobile phone), the content presented within the user interfaces 402, 502, 504, 506 can be displayed in any format on any of the user computing devices.

In Figure 4, the use of data for a plurality of network connections 130 to user 104 at user interface 402 is shown. In particular, data usage statistics 120 attributed to each of the network connections are shown. 130. For example, the amounts of data transmitted and / or received through a cellular network connection, a wireless network connection, a hot point network connection, a Wi-Fi network connection are displayed. The amounts of data are represented by proportionally sized horizontal bars.

The user interface 402 also presents the threshold values ​​118 associated with each of the network connections 130. The threshold values ​​118 are taken from the data usage plan. For example, the data usage plan indicates that user 104 has a maximum of 5 gigabytes (GB) of data usage available for the cellular network connection, 2 GB of data usage for the wireless network connection, 1 GB of data usage for the hot spot network connection, and a limited amount of data usage for the Wi-Fi network connection.

The user interface 402 in Figure 4 may also have a button or bar that, when selected by the user

104 (for example, clicked or tapped), user interface 402 allows user 104 to select options or other configuration properties to receive notifications. Notifications are sent when the amounts of data transmitted and / or received by the various network connections 130 reach particular values ​​(for example, set by user 104, mobile computing device 102, mobile operator 111, or another entity).

Referring later to Figure 5A, an illustrative user interface 502 shows the use of data by the mobile computing device 102 that consumes network data under the data usage plan that has a monthly limit. Although the general data usage views illustrated in Figures 5A, Figures 5B, and Figure 5C indicate that the data usage statistics 120 shown are by application, the user interfaces 502, 504, 506 may alternatively or also have a vis generally ta data usage added through applications 114 on the mobile computing device 102. In addition, user interfaces 502, 504, 506 may alternatively or additionally present a general view of data usage per user computing device 104 or aggregated through a plurality of user computing devices 104. For example, they can be displayed different statistics in different tabs or tiles in the user interface. In an example that involves a family that involves a family or shared data plan, the statistics for each plan member can be displayed in separate tiles.

In Figure 5A, the data usage statistics 120 include the amount of network data consumption data remaining for use (for example, the remaining monthly limit specified for the data usage plan), the amount of data consumption network data used during the current billing period, and the amount of time (for example, days) remaining within the current billing period. Data usage statistics 120 also indicate a division of data usage, such as the amount of data consumed under a cellular network connection against the amount of data consumed under a Wi-Fi network connection.

Referring later to Figures 5B, an illustrative user interface 504 shows the use of data by the mobile computing device 102 that consumes network data under a pay-per-use data usage plan. In Figure 5B, the data usage statistics 120 include the amount of network data consumption remaining for use (for example, the rest of the amount of payment for consumption specified by the data usage plan), the amount of recently consumed network data (for example, within the last 30 days), and the amount of time (for example, days) remaining. For example, the remaining bandwidth (for example, data consumption) expires in 16 days. Data usage statistics 120 also indicate a division of data usage, such as the amount of data consumed under a cellular network connection against the amount of data consumed under a network connection.

Wifi.

Referring later to Figure 5C, an illustrative user inferred 506 shows the use of data by the mobile computing device 102 that consumes network data under the data usage plan with unlimited data usage. In Figures 5C, data usage statistics 120 include the amount of network data consumed recently (for example, within the last 30 days). Data usage statistics 120 also indicate a division of data usage, such as the amount of data consumed under a cellular network connection against the amount of data consumed under a Wi-Fi network connection. The data usage statistics 120 also indicate a total amount of use by the mobile computing device 102.

Referring later to Figure 6, an illustrative block diagram shows the mobile computing device 102 as a mobile phone 602 having a mosaic to present the data usage statistics 120 to the user 104. The mobile phone 602 has a plurality of tiles (for example, active tiles) that can be updated with data usage statistics 120. In some embodiments, tiles represent elements of the mosaic user interface. In the example of Figure 6, mobile phone 602 indicates that 78% of the allocation for text messages has been consumed, while 55% of the allocation of data usage has been consumed.

In addition, any of the mosaics presenting the data usage statistics 120 can be secured to a mobile phone home screen 602 to allow the user 104 to instantly see if data is being consumed, how much data is being consumed, how the data is being consumed. data, and how much data remains available under the data usage plan.

Additional Examples

In an illustrative scenario, user 104 has a monthly data usage plan of 750 megabyte (MB) for mobile computing device 102. The user 104 observes the data usage plan at the user interface of the mobile computing device 102, and is able to immediately see the threshold values ​​118, the amount of data currently consumed under the data usage plan, and how much data consumption subtracts and by which of the network connections 130 (for example, voice, text, data, etc.).

At least a portion of the functionality of the various elements in Figure 1 may be performed by other elements in Figure 1, or an entity (for example, processor, web service, server, application program, computing device, etc.) not shown in Figure 1.

In some embodiments, the operations illustrated in Figure 2 and Figure 3 can be implemented as software instructions encoded in a computer-readable medium, in hardware programmed or designed to perform the operations, or both. For example, aspects of the description can be implemented as a system on a chip or other circuit system that includes a plurality of interconnected, electrically conductive elements.

The term roaming as used herein refers, in some modalities, to connectivity provided outside an area of ​​the subscriber's home that may be subject to additional fees, fees, or restrictions. The roaming service may or may not be provided by the same mobile operator 111. The term tethered (network tethering or attached) as used herein refers, in some modalities, to situations where a device acts as an access point for another device for network access. An attached connection can occur through a wired connection or a wireless connection. The term Wi-Fi as used here, in some modalities, for a wireless local area network that uses high frequency radio signals for data transmission. The term BLUETOOTH as used herein refers to some modalities, to a wireless technology standard for exchanging data over short distances using short wavelength radio transmission. The term "cellular" as used herein refers, in some embodiments, to a wireless communication system that uses short-range radio stations that, when joined, allow data transmission over a wide geographic network. The term NFC as used herein refers in some modalities to a short range high frequency wireless communication technology for exchanging data over short distances.

The modalities have been described with reference to verified and / or collected data from users 104. In some modalities, users 104 of the data collection may be provided (for example, through a dialog or preference setting ) and users 104 are provided the opportunity to provide or deny consent for verification and / or collection. The consent can take the form of consent of inclusion or consent of exclusion.

Illustrative Operating Environment

Illustrative computer-readable media include flash drives, digital versatile discs (DVDs), compact discs (CDs), floppy disks, tape cassettes. By way of example and not limitation, computer readable media comprises computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for information storage such as computer readable instructions, data structures, program modules or other data. Computer storage media are tangible and mutually exclusive for media. In some embodiments, computer storage media is implemented in hardware. Illustrative computer storage media includes hard drives, flash drives, and other solid state memory. In contrast, the media typically represents computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any means of delivering information.

Although described in connection with an illustrative computing environment, the modes of the description are capable of implementation with numerous other environments, configurations, general purpose or special purpose computing system devices.

Examples of well-known systems, environments, and / or computing configurations that may be suitable for use with aspects of the invention include, but are not limited to, mobile computing devices, personal computers, server computers, portable or laptop devices. , multiprocessor systems, game consoles, microprocessor-based systems, cable TV boxes, programmable consumer electronics, mobile phones, network PCs, minicomputers, macrocomputers, distributed computing environments that include any of the previous systems or devices, and the like. Such systems or devices may accept user input 104 in any form, including from computing devices such as a keyboard or pointing device, through gesture input, and / or through voice input.

The embodiments of the invention can be described in the general context of computer executable instructions, such as program modules, executed by one or more computers or other devices. The computer executable instructions can be organized into one or more components or modules executable by computer. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the invention can be implemented with any organization number of such components or modules. For example, aspects of the invention are not limited to the specific computer-executable instructions or to the specific components or modules illustrated in the figures and described herein. Other embodiments of the invention may include different instructions or computer-executable components that have more or less functionality as illustrated and described herein.

Aspects of the invention transform a general purpose computer into a special purpose computing device when configured to execute the instructions described herein.

The modalities illustrated and described here as well as modalities not specifically described herein but within the scope of aspects of the invention constitute illustrative modalities for defining scheme 116 to describe individual portions of the data usage plan.

The order of execution or performance of operations in embodiments of the invention illustrated and described herein is not essential, unless otherwise specified. That is, the operations can be performed in any order, unless otherwise specified, and the embodiments of the invention may include additional operations or at least those described herein. For example, it is contemplated that executing or performing a particular operation before, at one time with, or after another operation is within the scope of aspects of the invention.

When elements of aspects of the invention or the modalities of the invention are introduced, articles one, one, and said are intended to mean that there are one or more of the elements. The terms that you understand, that include, and that you intend to be inclusive and imply that they may be additional elements and different from the elements listed. The illustrative term is intended to mean an example of. The phrase one or more of the following: A, B, and C means at least one of A and / or at least one of B and / or at least one of C.

Having described aspects of the invention in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the invention as defined in the appended claims. Since several changes could be made in the above constructions, products, and methods without departing from the scope of the aspects of the invention, it is intended that all material contained in the above description and shown in the accompanying drawings should be interpreted as illustrative and not in a limiting sense.

Annex A

Listed below are portions of illustrative schema that are operable in aspects of the description. Although written in an extensible markup language (XML) format, the scheme can be implemented in other formats.

&lt;? xml version = 1.0 encoding = UTF-8?&gt;

&lt;xs: xmlns scheme: xs = Base / v1

Fo rm adeeleme nt oP network determined = "qualified is paci odeNom breo bjet i vo = Centroide Portad or / Base / v1&gt;

&lt;l - Basic types -&gt;

&lt;xs: Ti pos imple name = Type of Name&gt;

&lt;xs: restriction base = xs: Normalized sequence&gt;

&lt;xs: Minimum Length Value = “rv&gt;

&lt;xs: Maximum Length Value = 255 /&gt;

&lt;xs: White space value = collapse /&gt;

&lt;/ xs: restriction&gt; &lt;/ xs: Simple types&gt;

&lt;xs: Ti pos imple name = Priority&gt;

&lt;xs: restriction base = xs: EnteronoNegativo&gt;

&lt;xs: Maximum maximum value = “1 0 /&gt;

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple types&gt;

&lt;xs: Simple Type Name = GUID&gt;

&lt;xs: annotation&gt;

&lt;xs: documentation xml: lang = en&gt; The representation of a GUID, usually the id of an element. &lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: restriction base = xs: symbol&gt;

&lt;xs: pattern value = \ {[a-fA-F0-9] {8} - [af A-FO-9] {4} - [a-fA-F0-9J {4} - [a-fA -F0-9] {4} - [a-fA-F0-9] {12} \} /&gt; &lt;/ xs: restriction&gt; &lt;/ xs: Simple types&gt;

&lt;xs: Simple Type name = “T¡podeSuscriptor&gt;

&lt;xs: restriction base = xs: symbol&gt;

&lt;xs: Maximum Length Value = 20 /&gt;

&lt;xs: pattern value = \ w + /&gt;

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple type&gt;

&lt;xs: Complex Type name = Certificate Details&gt; &lt;xs: annotation&gt;

&lt;xs: documentation&gt; Used to identify a certificate or group of certificates, SubjectName is compared against the DN provided in the Certificate Subject field, or against any Name provided in the extensions of AlternativeName of Subject of type DirectoryName. IssuerName is compared against the DN provided as the Certificate Issuer field, or against any Name provided in the Issuer AlternativeName extensions of the DirectoryName type. &lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: sequence&gt;

&lt;xs: element name = SubjectName ”type = xs: sequence /&gt;

&lt;xs: element name = IssuerName ”type = xs: sequence /&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: Complex type&gt;

«--Alias ​​Definitions -&gt;

&lt;xs: element name = Alias ​​List&gt;

&lt;xs: Complex type&gt;

&lt;xs: sequence&gt;

&lt;xs: element Maximum or maximum = unlimited ”ref = Definition of AIs /&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: element&gt;

&lt;xs: Complex Type name = AliasBaseTipo Definition&gt;

&lt;xs: attribute name = Name ”type = xs: sequence /&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: element name = Definition of Alias ​​”type = Definition of AliasBaseType summary = true'7&gt;

&lt;! - Locations -&gt;

&lt;xs: Simple Type Name = ProviderName Type&gt;

&lt;xs: restriction base = xs: Normalized sequence&gt;

&lt;xs: Minimum Length Value = “r7&gt;

&lt;xs: Long¡tudmáx¡ma value = 20'7&gt;

&lt;xs: white space value = collapse'7&gt;

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple type&gt;

&lt;xs: Simple Type Name = Provider Type&gt;

&lt;xs: restriction base = xs: symbol&gt;

&lt;xs: pattern value = \ d {1,6} '7&gt;

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple type&gt;

&lt;xs: Complex Type name = Provider Type&gt; &lt;xs: sequence&gt;

&lt;xs: element name = lProviderDel ”type = VendorDriver Type'7&gt;

&lt;xs: element name = VendorName ”type = Vendor Type of Name'7&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: name of Complex Type = Location Type&gt;

&lt;xs: Ocurremáx¡mo = unlimited choice&gt;

&lt;xs: element name = Vendor ”type = Provider Type'7&gt;

&lt;xs: name of e e nto = Al i asde Location type = xs: sequence /&gt;

&lt;/ xs: choice&gt;

&lt;xs: name of at ri bu to = deny ”type = xs: boolean default o = fa lso /&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: element name = Defin¡c¡ondeAI¡asasUb¡cation type = "LocationDefinition Type of Location Alias

Groupsustituto = Def¡ ció ndeAlias

&lt;xs: name of

Type complex

Type of definition of AIs from Uca!

&lt;xs: Complex content&gt;

&lt;xs: extension base

Type of AI Definition Base&gt;

&lt;xs: sequence&gt;

&lt;xs: item name = Location type = LocationLocation /&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: extension&gt;

&lt;/ xs: Complex content&gt;

&lt;/ xs: Complex type&gt;

&lt;! - Times -&gt;

&lt;xs: complex type name = time type&gt;

&lt;xs: elecc¡óhOcurremáx¡mo = unlimited¡tado&gt;

&lt;xs: element name = Time Period type = Time Period'7&gt;

&lt;xs: item name

Recurrent Time Period ”type = Recurring Time Period /&gt;

&lt;xs: element name = Time Allas ”type = xs: sequence'7&gt;

&lt;/ xs: choice&gt;

&lt;xs: attribute name = deny ”type = xs: boolean” default = false'7&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: element name = Definition of Time Alias ​​”type = Type of Time Definition of Time Groups Groups = Defmlc where Where^,7&gt;

&lt;xs: complex type name =

Type of AI definition as of time&gt;

&lt;xs: Complex content&gt;

&lt;xs: extension base =

Type of BaseDefin¡c¡whereAI¡as&gt;

&lt;xs: sequence&gt;

&lt;xs: element name = Time ”type = Time Type

Maximum occurrence = unlimited'7&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: extension&gt;

&lt;/ xs: Complex content&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: TypeName! job = Weektime&gt;

&lt;xs: annotation&gt;

&lt;xs: documentation&gt; Define a time as a displacement from the preceding midnight 12:00:01 AM Sunday (POD) to the next midnight 11:59:59 PM Saturday (P7D).

&lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: restriction base = xs: duration&gt;

&lt;xs: minimum lll value = POD /&gt;

&lt;xs; maximum lnclusive value = P7D /&gt;

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple types&gt;

&lt;xs: complex type name = recurring time period&gt; &lt;xs: annotation&gt;

&lt;xs: documentation&gt; Defines a period of time within the week as the start / end of Weektime. If Final Time is less than Time of Death, the period is interpreted as crossing the Saturday night. &lt;/ xs: documentation&gt; &lt;/ xs: annotation&gt;

&lt;xs: attribute name = Start Time ”type = Week Time” use = required /&gt;

&lt;xs: attribute name = End Time ”type = Week Time” use = required /&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: complex type name = Time Period&gt; &lt;xs: annotation&gt;

&lt;xs: documentation&gt; Defines a period of time as a start / end date and time.

&lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: attribute name = Start Time ”type = xs: Date Time” use = required /&gt;

&lt;xs: attribute name = End Time ”type = xs: Date Time” use = required'7&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: scheme&gt;

&lt;? xml version = 1.0 ”encoding = UTF-8?&gt;

&lt;xs: xmlns scheme: base = Base / v1

Default Shape = “cal¡f¡each is peaceful or Nameobject i vo =“ Cont rolde Portad or / PI an en / v 1&gt;

&lt;xs: Import scheme location = Alias.xsd is pac i ode name = Portad Control or / Base / v 1 /&gt;

&lt;! - Plan Definition -&gt;

&lt;xs: Complex Type name = T¡podeC¡códe Billing&gt;

&lt;xs: attribute name = Start Date ”use = required” type = xs: Date Time /&gt;

&lt;xs: attribute name = Duration ”use = required&gt;

&lt;xs: Simple types&gt;

&lt;xs: restriction base = xs: duration&gt;

&lt;xs: Exclusive exclusive value = PT0S'7&gt;

&lt;/ xs: restriction »&lt;/ xs: Simple type&gt;

&lt;/ xs: attribute&gt;

&lt;xs: attribute name = Resettings ”type = xs: boolean” default = true /&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: Simple Type Name = Cost Style Type&gt; &lt;xs: annotation&gt;

&lt;xs: documentation&gt; Type of Cost expresses the increasing cost of a plan: -Not restricted: There is no increasing cost to consume in this plan - Fixed: Consumption goes against a fee that the user has bought / agreed to buy - Variable: The user will be charged for increasing use in this plan &lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: restriction base = xs: sequence&gt;

&lt;xs: enumeration value = Not restricted /&gt;

&lt;xs: enumeration value = Fixed /&gt;

&lt;xs: enumeration value = Variable /&gt;

&lt;/ xs: restriction »&lt;/ xs: Simple type» &lt;xs: element name = Plan&gt;

&lt;xs: Complex type »&lt;xs: sequence&gt;

&lt;xs: element

Ocurremínimo = “0 ref = Descr¡pc¡ón'7&gt;

&lt;xs: Ocurremínimo element = “0” ref = Use /&gt;

&lt;/ xs: sequence&gt;

&lt;xs: attribute name = Name ”use = required” type = xs: sequence /&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: element&gt;

&lt;xs: item name³ Description ”type = DescriptionBase Type” summary = true'7&gt;

&lt;xs: Complex Type name = DescriptionBase Type&gt;

&lt;xs: sequence&gt;

&lt;xs: item name³ Function Cycle &lt;xs: element name³ Terms"

Ocurremínimo = “0”&gt;

&lt;xs: Complex type&gt;

&lt;xs: all&gt;

&lt;xs: element name = Location ”type = base: Location Type Minimum occurs³ “0'7&gt; &lt;xs: element name = Time” type = base: Type of Ocurremimimo Time = “0'7&gt; &lt;xs: element name = Address” default = outside ”Ocurremínimo =“ 0 ”&gt;

&lt;xs: Simple types&gt;

&lt;xs: restriction base = xs: symbol&gt;

enumeration = "within'7&gt;

&lt;xs: value of &lt;xs: enumeration value = outside /&gt;

enumeration = outside

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple types&gt;

&lt;/ xs: element&gt;

&lt;xs: value of &lt;xs: element name = Destination

Ocurremínimo = “0”&gt;

&lt;xs: Complex type&gt;

&lt;xs: annotation&gt;

&lt;xs: documentation&gt; Telephone number only applies plans for

SMS / Voice;

. Hostname only applies to data plans &lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: sequence&gt;

&lt;xs: element name = Ocurremínimo phone number = “0”&gt;

&lt;xs: Simple types&gt;

constraint = xs: sequence&gt;

&lt;xs: base of &lt;xs: pattern value = (\ +)? \ d + /&gt;

&lt;/ xs: restriction&gt;

&lt;/ xs: Simple types&gt;

&lt;/ xs: element&gt;

&lt;xs: element name = Hostname ”Ocurremínimo =“ 0 ”&gt;

&lt;xs: Simple types&gt;

&lt;xs: restriction base = xs: anyURI /&gt;

&lt;/ xs: Simple types&gt;

&lt;/ xs: element&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: element&gt;

&lt;xs: element name = Unlimited Use ”Very rare =“ 0 ”&gt;

&lt;xs: annotation&gt;

&lt;xs: documentation&gt; For Fixed plans, provide details about the user fee: - Limit: The amount of the fee (in minutes for Voice plans, megabytes for Data plans, and messages for SMS plans) Shared Plan: Other name of plan whose quota is also consumed by use in this plan - Security Plan: Another name of plan whose consumption begins when this quota is used up. If a Security Plan is not provided, the current plan enters a Surplus state. &lt;/ xs: documentation&gt;

&lt;/ xs: annotation&gt;

&lt;xs: Complex type&gt;

&lt;xs: attribute name = Limit ”us o = required or type = xs: EnteronoNegat¡vo /&gt;

&lt;xs: name of attribute = Shared Plan type = xs: sequence /&gt;

&lt;xs: attribute name = Security Plan ”type = xs: sequence /&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: element&gt;

&lt;/ xs: all&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: element&gt;

&lt;/ xs: sequence&gt;

&lt;xs: attribute name = Cost Style ”use = required” type = Cost Style Type /&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: name of

Ti little mplejo = Ti can Description of Data Plan ”&gt;

&lt;xs: Complex content&gt;

&lt;xs: extension base = DescriptionBase Type&gt; &lt;xs: sequence&gt;

&lt;xs: element name = Bandwidth In Kbps ”

Ocurremínimo = “0” /&gt;

&lt;xs: name of you po = xs: Negative Entering of element = Maximum Download File Size In Megabytes type = xs: Interopositive ”default = 25” Ocurremimimo = “0” /&gt;

&lt;xs: element name = Security Updates Exemption ”type = xs: default boolean = false” Ocurremínimo = “0'7&gt;

&lt;/ xs: sequence&gt;

&lt;/ xs: extension&gt;

&lt;/ xs: Conten i docomplejo&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: element name = Description of DataPlan ”type = T¡podeDescriptionofPlandeData Groups substitute =“ Description ”/&gt;

&lt;xs: name of

Typecomplex = T¡podeDescripc¡ondePlandeSms&gt;

&lt;xs: Complex content&gt;

&lt;xs: extension base = T¡podeBasedeDescr¡pc¡ón /&gt;

&lt;/ xs: Complex content&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: element name = Description of SMS Plan ”type = TypeDescription Type of SMS Groups substitute =“ Description ”/&gt;

&lt;xs: Complex Type name = T! Power Plan Description&gt;

&lt;xs: Complex content&gt;

&lt;xs: extension base = T¡podeBasedeDescription /&gt;

&lt;/ xs: Contain gone complex&gt;

&lt;/ xs: Complex type&gt;

&lt;xs: element name = Voice Plan Description ”type = Voice Plan Description Type substitute Groups =“ Description ”/&gt;

&lt;xs: element name = Usage ”type = UsagePlan Type /&gt;

&lt;xs: name of Complex Type = Type of Usage Plan&gt;

&lt;xs: attribute name = PlanName ”use = required” type = xs: sequence /&gt;

&lt;xs: attribute name = Over Limit ”type = xs: boolean /&gt;

&lt;xs: attribute name = Congested ”type = xs: boolean /&gt;

&lt;xs: attribute name = Current Use ”use = required type = xs: EnteronoNegativo /&gt;

&lt;xs: attribute name = UseRegistration Date ”use = required” type = xs: Date Time /&gt;

&lt;/ xs: Complex type&gt;

&lt;/ xs: scheme&gt;