Source: http://patents.com/us-9887895.html
Timestamp: 2019-01-24 12:35:03
Document Index: 772132497

Matched Legal Cases: ['Application No. 13741633', 'Application No. 13741633', 'Application No. 13741633', 'Application No. 13741434', 'Application No. 13741434', 'Application No. 61', 'Application No. 61', 'Application No. 61']

US Patent # 9,887,895. Dynamically adjusting a data usage plan based on data usage statistics - Patents.com
United States Patent 9,887,895
Family ID: 1000003104575
14/839,243
US 20160028898 A1 Jan 28, 2016
13721069 Dec 20, 2012 9369589
Current CPC Class: H04L 43/0876 (20130101); H04L 43/045 (20130101); H04L 43/062 (20130101); H04M 15/41 (20130101); H04M 15/58 (20130101); H04M 15/60 (20130101); H04M 15/765 (20130101); H04M 15/7652 (20130101); H04M 15/80 (20130101); H04M 15/83 (20130101); H04M 15/84 (20130101); H04M 15/846 (20130101); H04M 15/85 (20130101); H04M 15/853 (20130101); H04M 15/854 (20130101); H04M 15/86 (20130101); H04W 4/003 (20130101); H04W 4/24 (20130101); H04W 8/186 (20130101); H04L 12/1435 (20130101); H04W 88/06 (20130101); H04M 1/72522 (20130101); H04M 15/775 (20130101); H04M 15/8044 (20130101); H04M 15/856 (20130101); H04W 8/18 (20130101)
Current International Class: H04M 11/00 (20060101); H04L 12/14 (20060101); H04L 12/26 (20060101); H04W 4/24 (20090101); H04W 4/00 (20090101); H04M 15/00 (20060101); H04W 88/06 (20090101); H04W 8/18 (20090101); H04M 1/725 (20060101)
7904080 March 2011 Alkins et al.
2011/0151831 June 2011 Pallabiraman
2012/0108200 May 2012 Rubin
"Notice of Allowance Issued in European Patent Application No. 13741633.5", dated Aug. 6, 2015, 7 Pages. cited by applicant .
"Mobile Data Usage Meter--Manage Mobile Data Usage & Wireless Broadband Devices", Published on: Dec. 28, 2009, Available at: http://web.archive.org/web/20091228092436/http://www.telstrabusiness.com/- business/portal/online/site/myaccounl/mobiledatausagemeter.94003, 2 pages. cited by applicant .
Heinz 11, Gerard J., "Priorities in Stream Transmission Control Protocol (SCTP) Multistreaming", A Thesis Submitted to the Faculty of the University of Delaware in Partial Fulfillment of the Requirements for the Degree of Master of Degree in Computer and Information Science, 2003, 35 Pages. cited by applicant .
"Rapid Mobile Data Service Creation and Monetization", Retrieved at <<http://www.amdocs.com/Products/network-control/Documenls/data-exp- erience-solution-datasheet.pdf>>, 2012, 7 Pages. cited by applicant .
Unuth, Nadeem, "Data Usage Monitor Apps for Your iPhone and iPad", Retrieved Date: Oct. 8, 2012 Available at: http://voip.about.com/od/voipbandwidth/tp/Data-Usage-Monitor-Apps-For-You- r-Iphone-And-Ipad.htm,1 page. cited by applicant .
Blass, Evan, "Exclusive: Windows Phone 8 Detailed", Retrieved at <<http://pocketnow.com/windows-phone/exclusive-windows-phone-8-deta- iled>> , Feb. 2, 2012, pp. 2. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,053, dated Mar. 18, 2014, 8 Pages. cited by applicant .
Applicant Initiated Interview Summary for U.S. Appl. No. 13/721,053, dated May 30, 2014, 3 pages. cited by applicant .
Examiner Initiated Interview Summary for U.S. Appl. No. 13/721,053, dated Aug. 19, 2014, 2 pages. cited by applicant .
Notice of Allowance and Fee(s) Due Issued U.S. Appl. No. 13/721,053, dated Aug. 19, 2014, 13 pages. cited by applicant .
Notice of Allowance and Fee(s) Due Issued U.S. Appl. No. 13/721,053, dated Oct. 28, 2014, 7 Pages. cited by applicant .
International Search Report & Written Opinion for PCT Patent Application No. PCT/US2013/022353, dated May 15, 2013, Filed Date: Jan. 21, 2013, 10 Pages. cited by applicant .
"International Preliminary Report on Patentability Issued in PCT Application No. PCT/US13/22353", dated Aug. 7, 2014, 7 pages. cited by applicant .
Supplementary Search Report Issued in European Patent Application No. 13741633.5, dated Sep. 18, 2014, 3 Pages. cited by applicant .
Office Action Issued in European Patent Application No. 13741633.5, dated Nov. 27, 2014, 7 Pages. cited by applicant .
"International Preliminary Report on Patentability Issued in PCT Application No. PCT/US13/22822", dated Aug. 7, 2014, 6 pages. cited by applicant .
International Search Report & Written Opinion for PCT Patent Application No. PCT/US2013/022822, dated Apr. 25, 2013, Filed Date: Jan. 24, 2013, 9 Pages. cited by applicant .
Search Report Issued in European Patent Application No. 13741434.8, dated Sep. 30, 2014, 3 Pages. cited by applicant .
Office Action Issued in European Patent Application No. 13741434.8, dated Nov. 27, 2014, 6 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,041, dated Mar. 28, 2014, 14 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,041 , dated Jan. 7, 2015, 20 Pages. cited by applicant .
Final Office Action Issued in U.S. Appl. No. 13/721,041, dated Sep. 14, 2015, 23 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,069, dated Mar. 14, 2014, 14 Pages. cited by applicant .
Final Office Action Issued in U.S. Appl. No. 13/721,069, dated Nov. 28, 2014, 23 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,069, dated Jul. 7, 2015, 27 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,029, dated Mar. 11, 2014, 13 Pages. cited by applicant .
Final Office Action Issued in U.S. Appl. No. 13/721,029, dated Oct. 1, 2014, 19 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,029, dated Mar. 17, 2015, 24 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,023, dated Mar. 28, 2014, 15 Pages. cited by applicant .
Final Office Action Issued in U.S. Appl. No. 13/721,023, dated Oct. 27, 2014, 16 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,023, dated Feb. 13, 2015, 18 Pages. cited by applicant .
Final Office Action Issued in U.S. Appl. No. 13/721,023, dated Oct. 5, 2015, 25 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,032, dated Feb. 6, 2014, 10 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,032, dated Aug. 5, 2014, 16 Pages. cited by applicant .
Notice of Allowance and Fee(s) Due Issued U.S. Appl. No. 13/721,032, dated Jan. 30, 2015, 11 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,058, dated Apr. 16, 2014, 10 Pages. cited by applicant .
Final Office Action Issued in U.S. Appl. No. 13/721,058, dated Sep. 22, 2014, 15 Pages. cited by applicant .
Non-Final Office Action Issued U.S. Appl. No. 13/721,058, dated Jan. 22, 2015, 12 Pages. cited by applicant .
Notice of Allowance and Fee(s) Due Issued U.S. Appl. No. 13/721,058, dated May 8, 2015, 7 Pages. cited by applicant .
Notice of Allowance and Fee(s) Due Issued U.S. Appl. No. 13/721,058, dated Sep. 14, 2015, 3 Pages. cited by applicant .
Non-Final Office Action Issued in U.S. Appl. No. 14/642,378 , dated Jun. 12, 2015, 12 pages. cited by applicant .
Non-Final Office action Issued U.S. Appl. No. 13/721,066, dated Feb. 13, 2015, 17 pages. cited by applicant .
Non-Final Office Action Issued in U.S. Appl. No. 13/721,083, dated Jun. 5, 2015, 10 pages. cited by applicant.
This application claims the benefit of U.S. patent application Ser. No. 13/721,069 filed Dec. 20, 2012, which claims the benefit of U.S. Provisional Application No. 61/696,472 filed Sep. 4, 2012, U.S. Provisional Application No. 61/591,503 filed Jan. 27, 2012, and U.S. Provisional Application No. 61/591,509 filed Jan. 27, 2012. The entirety of these applications are hereby incorporated by reference herein.
This application is related to the following U.S. applications: U.S. patent application Ser. No. 13/721,023 filed Dec. 20, 2012; U.S. patent application Ser. No. 13/721,029 filed Dec. 20, 2012; U.S. patent application Ser. No. 13/721,032 filed Dec. 20, 2012 and issued as U.S. Pat. No. 9,049,589; U.S. patent application Ser. No. 13/721,041 filed Dec. 20, 2012; U.S. patent application Ser. No. 14/642,378 filed Mar. 9, 2015, which is a continuation application of U.S. patent application Ser. No. 13/721,053 filed Dec. 20, 2012 and issued Mar. 10, 2015 as U.S. Pat. No. 8,977,231; U.S. patent application Ser. No. 14/835,693 filed Aug. 25, 2015, which is a continuation application of U.S. patent application Ser. No. 13/721,058 filed Dec. 20, 2012; U.S. patent application Ser. No. 13/721,066 filed Dec. 20, 2012; and U.S. patent application Ser. No. 13/721,083 filed Dec. 20, 2012. The entirety of these applications is hereby incorporated by reference herein.
1. A system for analyzing data usage statistics associated with a data usage plan, the system comprising: a memory area associated with a mobile computing device, said memory area storing data describing a plurality of data usage plans of different types; and a processor programmed to: access the data describing the plurality of data usage plans of the different types, each type of the plurality of data usage plans comprising a threshold value representing a maximum amount of network data consumption allotted to each of a plurality of different network connections; receive data usage statistics describing an amount of network data consumed by the mobile computing device under each of the plurality of data usage plans of different types compared to a total amount of network data consumed; and present, to a user of the mobile computing device, an analysis based on the accessed data, the received data usage statistics, and a type of data usage plan, wherein a different analysis is presented for each different type of data usage plan from the plurality of data usage plans.
2. The system of claim 1, wherein the processor is programmed to present at least an amount of network data remaining for use, an amount of network data consumed during the current billing period, and a quantity of time remaining within the current billing period.
3. The system of claim 1, wherein the processor is programmed to present at least an amount of network data remaining for use, an amount of network data consumed within a time period, and a quantity of time remaining for expiration of the amount of network data remaining.
4. The system of claim 1, wherein the processor is programmed to present at least a total amount of network data consumed within a time period over a plurality of different types of network connections.
5. The system of claim 1, the type of usage plan includes one or more first threshold values, at least one of the one or more first threshold values representing a maximum amount of network data consumption allotted to one or more different network connections under the type of usage plan.
6. The system of claim 1, wherein the plurality of data usage plans are stored in the memory area as extensible markup language schemas.
7. The system of claim 1, wherein the processor is programmed to receive the data usage statistics by receiving at least a portion of the data usage statistics from one or more of a mobile operator, a web service, and other computing devices associated with the user.
8. A method comprising: accessing, by a computing device, data describing a plurality of data usage plans of different types associated with at least one computing device associated with a user, each type of the plurality of data usage plans comprising a threshold value representing a maximum amount of network data consumption allotted to each of a plurality of different network connections; receiving data usage statistics describing an amount of network data consumed by the at least one computing device under each of the different types of the plurality of data usage plans compared to a total amount of network data consumed; comparing the accessed data of the plurality of data usage plans with the received data usage statistics; and presenting, to the user, an analysis based on the comparison, the analysis associated with a type of data usage plan, wherein a different analysis is presented for each different type of data usage plan from the plurality of data usage plans.
9. The method of claim 8, wherein receiving the data usage statistics comprises receiving the data usage statistics from one or more of the following: a mobile operator, a web service, and other computing devices associated with the user.
10. The method of claim 8, wherein the type of data usage plan includes one or more first threshold values, at least one of the one or more first threshold values representing a maximum amount of network data consumption allotted to one of a plurality of different network connections under the type of data usage plan.
11. The method of claim 8, wherein accessing data comprises accessing an extensible markup language schema, wherein the schema includes a plurality of fields comprising one or more of the following: peak times, off-peak times, peak time network data consumption quota, off-peak time network data consumption quota, peak time network data consumption remaining, off-peak time network data consumption remaining, a roaming rate, a mobile operator name, a billing cycle type, and a network connection type.
12. The method of claim 8, wherein a plurality of other computing devices and the at least one computing device associated with the user share the plurality of data usage plans.
13. The method of claim 8, wherein at least one of the plurality of data usage plans represents terms and conditions under which a mobile operator provides data transfer services to the at least one computing device.
14. The method of claim 8, further comprising updating a portion of at least one of the plurality of data usage plans.
15. One or more computer storage devices embodying computer-executable components, said components comprising: a communications interface component that on execution by at least one processor causes the at least one processor to: receive data describing a plurality of data usage plans of different types associated with at least one computing device, each type of the plurality of data usage plans comprising a threshold value representing a maximum amount of network data consumption allotted to each of a plurality of different network connections, and receive data usage statistics describing an amount of network data consumed by the at least one computing device under each of the plurality of data usage plans; a prediction component that on execution by the at least one processor causes the at least one processor to analyze the data usage statistics and the data describing the plurality of data usage plans as received by the communications interface component; and a user interface component that on execution by the at least one processor causes the at least one processor to present an analysis to a user of the at least one computing device based on the analysis by the prediction component and types of the plurality of data usage plans, wherein a different analysis is presented for each different type of data usage plan from the plurality of data usage plans.
16. The computer storage devices of claim 15, wherein the user interface component further displays a plurality of user interface elements that are updated on receiving updated data usage statistics.
17. The computer storage devices of claim 15, wherein the user interface component presents, based on a type of data usage plan, at least an amount of network data remaining for use, an amount of network data consumed during the current billing period, and a quantity of time remaining within the current billing period.
18. The computer storage devices of claim 15, wherein the user interface component presents, based on a type of data usage plan, at least an amount of network data remaining for use, an amount of network data consumed within a time period, and a quantity of time remaining for expiration of the amount of network data remaining.
19. The computer storage devices of claim 15, wherein the user interface component presents, for a type of data usage plan, at least a total amount of network data consumed within a time period over a plurality of different types of network connections.
20. The computer storage devices of claim 15, wherein at least one of the plurality of data usage plans represents terms and conditions under which a mobile operator provides data transfer services to the at least one computing device.
TABLE-US-00001 <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="Base/v1" elementFormDefault="qualified" targetNamespace="CarrierControl/Base/v1"> <!-- Basic types --> <xs:simpleType name="NameType"> <xs:restriction base="xs:normalizedString"> <xs:minLength value="1"/> <xs:maxLength value="255"/> <xs:whiteSpace value="collapse"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="Priority"> <xs:restriction base="xs:nonNegativeInteger"> <xs:maxExclusive value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="GUID"> <xs:annotation> <xs:documentation xml:lang="en"> The representation of a GUID, generally the id of an element. </xs:documentation> </xs:annotation> <xs:restriction base="xs:token"> <xs:pattern value="\{[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a- fA-F0-9]{4}-[a-fA-F0-9]{12}\}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="SubscriberType"> <xs:restriction base="xs:token"> <xs:maxLength value="20"/> <xs:pattern value="\w+"/> </xs:restriction> </xs:simpleType> <xs:complexType name="CertificateDetails"> <xs:annotation> <xs:documentation> Used to identify a certificate or set of certificates. SubjectName is compared against the DN provided as the certificate's Subject field, or against any Name provided in the SubjectAlternativeName extentions of type DirectoryName. IssuerName is compared against the DN provided as the certificate's Issuer field, or against any Name provided in the IssuerAlternativeName extentions of type DirectoryName. </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="SubjectName" type="xs:string"/> <xs:element name="IssuerName" type="xs:string"/> </xs:sequence> </xs:complexType> <!-- Alias definitions --> <xs:element name="AliasList"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" ref="AliasDefinition"/> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="AliasDefinitionBaseType"> <xs:attribute name="Name" type="xs:string"/> </xs:complexType> <xs:element name="AliasDefinition" type="AliasDefinitionBaseType" abstract="true"/> <!-- Locations --> <xs:simpleType name="ProviderNameType"> <xs:restrictionbase="xs:normalizedString"> <xs:minLength value="1"/> <xs:maxLength value="20"/> <xs:whiteSpace value="collapse"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="ProviderIdType"> <xs:restriction base="xs:token"> <xs:pattern value="\d{1,6}"/> </xs:restriction> </xs:simpleType> <xs:complexType name="ProviderType"> <xs:sequence> <xs:element name="ProviderID" type="ProviderIdType"/> <xs:element name="ProviderName" type="ProviderNameType"/> </xs:sequence> </xs:complexType> <xs:complexType name="LocationType"> <xs:choice maxOccurs="unbounded"> <xs:element name="Provider" type="ProviderType"/> <xs:element name="LocationAlias" type="xs:string"/> </xs:choice> <xs:attribute name="negate" type="xs:boolean" default="false"/> </xs:complexType> <xs:element name="LocationAliasDefinition" type="LocationAliasDefinitionType" substitutionGroup="AliasDefinition"/> <xs:complexType name="LocationAliasDefinitionType"> <xs:complexContent> <xs:extension base="AliasDefinitionBaseType"> <xs:sequence> <xs:element name="Location" type="LocationType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <!-- Times --> <xs:complexType name="TimeType"> <xs:choice maxOccurs="unbounded"> <xs:element name="TimePeriod" type="TimePeriod"/> <xs:element name="RecurringTimePeriod" type="RecurringTimePeriod"/> <xs:element name="TimeAlias" type="xs:string"/> </xs:choice> <xs:attribute name="negate" type="xs:boolean" default="false"/> </xs:complexType> <xs:element name="TimeAliasDefinition" type="TimeAliasDefinitionType" substitutionGroup="AliasDefinition"/> <xs:complexType name="TimeAliasDefinitionType"> <xs:complexContent> <xs:extension base="AliasDefinitionBaseType"> <xs:sequence> <xs:element name="Time" type="TimeType" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:simpleType name="TimeOfWeek"> <xs:annotation> <xs:documentation> Defines a time as an offset from the midnight preceding 12:00:01 AM Sunday (P0D) to the midnight following 11:59:59 PM Saturday (P7D). </xs:documentation> </xs:annotation> <xs:restriction base="xs:duration"> <xs:minInclusive value="P0D"/> <xs:maxInclusive value="P7D"/> </xs:restriction> </xs:simpleType> <xs:complexType name="RecurringTimePeriod"> <xs:annotation> <xs:documentation> Defines a period of time within the week as a start/end TimeOfWeek. If EndTime is less than StartTime, the period is interpreted as crossing Saturday night. </xs:documentation> </xs:annotation> <xs:attribute name="StartTime" type="TimeOfWeek" use="required"/> <xs:attribute name="EndTime" type="TimeOfWeek" use="required"/> </xs:complexType> <xs:complexType name="TimePeriod"> <xs:annotation> <xs:documentation Defines a period of time as a start/end date and time. </xs:documentation> </xs:annotation> <xs:attribute name="StartTime" type="xs:dateTime" use="required"/> <xs:attribute name="EndTime" type="xs:dateTime" use="required"/> </xs:complexType> </xs:schema> <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:base="Base/v1" elementFormDefault="qualified" targetNamespace=" CarrierControl/Plans/v1"> <xs:import schemaLocation="Alias.xsd" namespace="CarrierControl/Base/v1"/> <!-- Plan Definition --> <xs:complexType name="BillingCycleType"> <xs:attribute name="StartDate" use="required" type="xs:dateTime"/> <xs:attribute name="Duration" use="required"> <xs:simpleType> <xs:restriction base="xs:duration"> <xs:minExclusive value="PT0S"/> </xs:restriction> </xs:simpleType> </xs:attribute> <xs:attribute name="Resets" type="xs:boolean" default="true"/> </xs:complexType> <xs:simpleType name="CostStyleType"> <xs:annotation> <xs:documentation> CostType expresses the incremental cost of a plan: - Unrestricted: There is no incremental cost for consumption on this plan - Fixed: Consumption goes against a quota which the user has purchased / agreed to purchase - Variable: The user will be billed for incremental usage on this plan </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="Unrestricted"/> <xs:enumeration value="Fixed"/> <xs:enumeration value="Variable"/> </xs:restriction> </xs:simpleType> <xs:element name="Plan"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" ref="Description"/> <xs:element minOccurs="0" ref="Usage"/> </xs:sequence> <xs:attribute name="Name" use="required" type="xs:string"/> </xs:complexType> </xs:element> <xs:element name="Description" type="DescriptionBaseType" abstract="true"/> <xs:complexType name="DescriptionBaseType"> <xs:sequence> <xs:element name="BillingCycle" type="BillingCycleType" minOccurs="0"/> <xs:element name="Conditions" minOccurs="0"> <xs:complexType> <xs:all> <xs:element name="Location" type="base:LocationType" minOccurs="0"/> <xs:element name="Time" type="base:TimeType" minOccurs="0"/> <xs:element name="Direction" default="inout" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="in"/> <xs:enumeration value="out"/> <xs:enumeration value="inout"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="Destination" minOccurs="0"> <xs:complexType> <xs:annotation> <xs:documentation> PhoneNumber only applies to SMS/Voice plans; HostName only applies to data plans </xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="PhoneNumber" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:string"> <xs:pattern value="(\+)?\d+"/> </xs:restriction> </xs:simpleType> </xs:element> <xs:element name="HostName" minOccurs="0"> <xs:simpleType> <xs:restriction base="xs:anyURI"/> </xs:simpleType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="LimitedUsage" minOccurs="0"> <xs:annotation> <xs:documentation> For Fixed plans, provides details
on the user's quota: - Limit: The amount of the quota (in minutes for Voice plans, megabytes for Data plans, and messages for SMS plans) - SharedPlan: Another plan name whose quota is also consumed by usage on this plan - FallbackPlan: Another plan name whose consumption begins when this quota is exhausted. If a Fallback Plan is not provided, the current plan goes into an Overage state. </xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="Limit" use="required" type="xs:nonNegativeInteger"/> <xs:attribute name="SharedPlan" type="xs:string"/> <xs:attribute name="FallbackPlan" type="xs:string"/> </xs:complexType> </xs:element> </xs:all> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="CostStyle" use="required" type="CostStyleType"/> </xs:complexType> <xs:complexType name="DataPlanDescriptionType"> <xs:complexContent> <xs:extension base="DescriptionBaseType"> <xs:sequence> <xs:element name="BandwidthInKbps" type="xs:nonNegativeInteger" minOccurs="0"/> <xs:element name="MaxDownloadFileSizeInMegabytes" type="xs:positiveInteger" default="25" minOccurs="0"/> <xs:element name="SecurityUpdatesExempt" type="xs:boolean" default="false" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="DataPlanDescription" type="DataPlanDescriptionType" substitutionGroup="Description"/> <xs:complexType name="SmsPlanDescriptionType"> <xs:complexContent> <xs:extension base="DescriptionBaseType"/> </xs:complexContent> </xs:complexType> <xs:element name="SmsPlanDescription" type="SmsPlanDescriptionType" substitutionGroup="Description"/> <xs:complexTypename="VoicePlanDescriptionType"> <xs:complexContent> <xs:extension base="DescriptionBaseType"/> </xs:complexContent> </xs:complexType> <xs:element name="VoicePlanDescription" type="VoicePlanDescriptionType" substitutionGroup="Description"/> <xs:element name="Usage" type="PlanUsageType"/> <xs:complexType name="PlanUsageType"> <xs:attribute name="PlanName" use="required" type="xs:string"/> <xs:attribute name="OverLimit" type="xs:boolean"/> <xs:attribute name="Congested" type="xs:boolean"/> <xs:attribute name="CurrentUsage" use="required" type="xs:nonNegativeInteger"/> <xs:attribute name="UsageTimestamp" use="required" type="xs:dateTime"/> </xs:complexType> </xs:schema>
Previous Patent US 9,887,894 | Next Patent US 9,887,896