US20100192207A1 - Virtual service provider systems - Google Patents
Virtual service provider systems Download PDFInfo
- Publication number
- US20100192207A1 US20100192207A1 US12/380,783 US38078309A US2010192207A1 US 20100192207 A1 US20100192207 A1 US 20100192207A1 US 38078309 A US38078309 A US 38078309A US 2010192207 A1 US2010192207 A1 US 2010192207A1
- Authority
- US
- United States
- Prior art keywords
- service
- network
- processor
- usage
- agent
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 230000006854 communication Effects 0.000 claims abstract description 465
- 238000004891 communication Methods 0.000 claims abstract description 462
- 238000000034 method Methods 0.000 claims abstract description 162
- 238000005192 partition Methods 0.000 claims abstract description 28
- 230000006870 function Effects 0.000 claims description 418
- 238000001994 activation Methods 0.000 claims description 305
- 230000004913 activation Effects 0.000 claims description 278
- 238000012544 monitoring process Methods 0.000 claims description 211
- 238000012360 testing method Methods 0.000 claims description 94
- 238000004458 analytical method Methods 0.000 claims description 58
- 230000009471 action Effects 0.000 claims description 34
- 238000003860 storage Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 4
- 239000003795 chemical substances by application Substances 0.000 description 740
- 230000006855 networking Effects 0.000 description 261
- 230000000694 effects Effects 0.000 description 190
- 238000012795 verification Methods 0.000 description 154
- 238000007726 management method Methods 0.000 description 85
- 238000005259 measurement Methods 0.000 description 85
- 238000010586 diagram Methods 0.000 description 80
- 238000007493 shaping process Methods 0.000 description 66
- 238000013459 approach Methods 0.000 description 62
- 238000013461 design Methods 0.000 description 62
- 238000012545 processing Methods 0.000 description 60
- 230000008569 process Effects 0.000 description 57
- 230000004044 response Effects 0.000 description 53
- XIJXHOVKJAXCGJ-XLPZGREQSA-N 1-[(2r,4s,5r)-4-hydroxy-5-(hydroxymethyl)oxolan-2-yl]-5-iodopyrimidin-2-one Chemical compound C1[C@H](O)[C@@H](CO)O[C@H]1N1C(=O)N=CC(I)=C1 XIJXHOVKJAXCGJ-XLPZGREQSA-N 0.000 description 44
- 230000036961 partial effect Effects 0.000 description 44
- 230000005540 biological transmission Effects 0.000 description 42
- 238000009826 distribution Methods 0.000 description 41
- 238000004519 manufacturing process Methods 0.000 description 31
- 238000007689 inspection Methods 0.000 description 27
- 230000008901 benefit Effects 0.000 description 24
- 230000001010 compromised effect Effects 0.000 description 24
- 238000011144 upstream manufacturing Methods 0.000 description 24
- 238000013475 authorization Methods 0.000 description 23
- 238000005516 engineering process Methods 0.000 description 23
- 239000000047 product Substances 0.000 description 23
- 238000012546 transfer Methods 0.000 description 23
- 230000006399 behavior Effects 0.000 description 21
- 238000009432 framing Methods 0.000 description 20
- 230000002829 reductive effect Effects 0.000 description 20
- 230000001360 synchronised effect Effects 0.000 description 18
- 230000002776 aggregation Effects 0.000 description 17
- 238000004220 aggregation Methods 0.000 description 17
- 238000012790 confirmation Methods 0.000 description 17
- 238000011161 development Methods 0.000 description 17
- 230000003044 adaptive effect Effects 0.000 description 16
- 230000001965 increasing effect Effects 0.000 description 14
- 239000000872 buffer Substances 0.000 description 13
- 230000007246 mechanism Effects 0.000 description 13
- 238000001914 filtration Methods 0.000 description 12
- 230000001976 improved effect Effects 0.000 description 11
- 230000000737 periodic effect Effects 0.000 description 10
- 230000002265 prevention Effects 0.000 description 10
- 238000012384 transportation and delivery Methods 0.000 description 10
- 230000008859 change Effects 0.000 description 9
- 238000001514 detection method Methods 0.000 description 9
- 239000000835 fiber Substances 0.000 description 9
- 238000002955 isolation Methods 0.000 description 9
- 230000007935 neutral effect Effects 0.000 description 9
- 238000000638 solvent extraction Methods 0.000 description 8
- 101001094649 Homo sapiens Popeye domain-containing protein 3 Proteins 0.000 description 7
- 101000608234 Homo sapiens Pyrin domain-containing protein 5 Proteins 0.000 description 7
- 101000578693 Homo sapiens Target of rapamycin complex subunit LST8 Proteins 0.000 description 7
- 102100027802 Target of rapamycin complex subunit LST8 Human genes 0.000 description 7
- 230000003213 activating effect Effects 0.000 description 7
- 230000000903 blocking effect Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 230000001960 triggered effect Effects 0.000 description 7
- 230000003111 delayed effect Effects 0.000 description 6
- 238000013519 translation Methods 0.000 description 6
- 230000014616 translation Effects 0.000 description 6
- 230000003139 buffering effect Effects 0.000 description 5
- 239000000969 carrier Substances 0.000 description 5
- 238000009434 installation Methods 0.000 description 5
- 238000012163 sequencing technique Methods 0.000 description 5
- 230000009977 dual effect Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 239000002243 precursor Substances 0.000 description 4
- 238000012552 review Methods 0.000 description 4
- 238000005070 sampling Methods 0.000 description 4
- 238000007619 statistical method Methods 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 3
- 238000012512 characterization method Methods 0.000 description 3
- 230000004069 differentiation Effects 0.000 description 3
- 238000005111 flow chemistry technique Methods 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 230000000670 limiting effect Effects 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000001404 mediated effect Effects 0.000 description 3
- 239000000203 mixture Substances 0.000 description 3
- 238000010998 test method Methods 0.000 description 3
- 230000005641 tunneling Effects 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- LHMQDVIHBXWNII-UHFFFAOYSA-N 3-amino-4-methoxy-n-phenylbenzamide Chemical compound C1=C(N)C(OC)=CC=C1C(=O)NC1=CC=CC=C1 LHMQDVIHBXWNII-UHFFFAOYSA-N 0.000 description 2
- 230000002547 anomalous effect Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 235000014510 cooky Nutrition 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000001121 heart beat frequency Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- 230000007420 reactivation Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000001228 spectrum Methods 0.000 description 2
- 230000008093 supporting effect Effects 0.000 description 2
- 230000009897 systematic effect Effects 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007175 bidirectional communication Effects 0.000 description 1
- 210000000988 bone and bone Anatomy 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- -1 delay Substances 0.000 description 1
- 230000001627 detrimental effect Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 239000000796 flavoring agent Substances 0.000 description 1
- 235000019634 flavors Nutrition 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 238000010348 incorporation Methods 0.000 description 1
- 238000009533 lab test Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000036316 preload Effects 0.000 description 1
- 230000035755 proliferation Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 210000004722 stifle Anatomy 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 239000004557 technical material Substances 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
- G06F15/177—Initialisation or configuration control
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06315—Needs-based resource requirements planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0637—Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals
- G06Q10/06375—Prediction of business process outcome or impact based on a proposed change
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
- G06Q30/0284—Time or distance, e.g. usage of parking meters or taximeters
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/12—Accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/40—Business processes related to the transportation industry
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
- H04L12/1407—Policy-and-charging control [PCC] architecture
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1432—Metric aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5029—Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2408—Traffic characterised by specific attributes, e.g. priority or QoS for supporting different services, e.g. a differentiated services [DiffServ] type of service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/046—Interoperability with other network applications or services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
- H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0853—Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
- H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/49—Connection to several service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/58—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on statistics of usage or network monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/66—Policy and charging system
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/80—Rating or billing plans; Tariff determination aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/80—Rating or billing plans; Tariff determination aspects
- H04M15/8044—Least cost routing
- H04M15/8055—Selecting cheaper transport technology for a given service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/88—Provision for limiting connection, or expenditure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/03—Protecting confidentiality, e.g. by encryption
- H04W12/037—Protecting confidentiality, e.g. by encryption of the control plane, e.g. signalling traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/30—Security of mobile devices; Security of mobile applications
- H04W12/37—Managing security policies for mobile devices or for controlling mobile applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
- H04W28/12—Flow control between communication endpoints using signalling between network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/04—Wireless resource allocation
- H04W72/044—Wireless resource allocation based on the type of the allocated resource
- H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0876—Aspects of the degree of configuration automation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5019—Ensuring fulfilment of SLA
- H04L41/5025—Ensuring fulfilment of SLA by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/564—Enhancement of application control based on intercepted application data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
- H04M2215/01—Details of billing arrangements
- H04M2215/0188—Network monitoring; statistics on usage on called/calling number
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/80—Management or planning
Definitions
- Wi-Fi Wireless Fidelity wireless networks
- EVDO Evolution-Data Optimized
- HSPA High Speed Packet Access
- LTE Long Term Evolution
- WiMax Worldwide Interoperability for Microwave Access
- Wi-Fi Wireless Fidelity
- wire line access networks such as cable and DSL
- wire line user service consumption habits are trending toward very high bandwidth applications that can quickly consume the available capacity and degrade overall network service experience. Because some components of service provider costs go up with increasing bandwidth, this trend will also negatively impact service provider profits.
- FIG. 1 illustrates a simplified (e.g., “flattened”) network architecture in accordance with some embodiments.
- FIG. 2 illustrates another simplified (e.g., “flattened”) network architecture including an MVNO (Mobile Virtual Network Operator) relationship in accordance with some embodiments.
- MVNO Mobile Virtual Network Operator
- FIG. 3 illustrates another simplified (e.g., “flattened”) network architecture including two central providers in accordance with some embodiments.
- FIG. 4 illustrates a network architecture including a Universal Mobile Telecommunications System (UMTS) overlay configuration in accordance with some embodiments.
- UMTS Universal Mobile Telecommunications System
- FIG. 5 illustrates a network architecture including an Evolution Data Optimized (EVDO) overlay configuration in accordance with some embodiments.
- EVDO Evolution Data Optimized
- FIG. 6 illustrates a network architecture including a 4G LTE and Wi-Fi overlay configuration in accordance with some embodiments.
- FIG. 7 illustrates a network architecture including a WiMax and Wi-Fi overlay configuration in accordance with some embodiments.
- FIG. 8 illustrates another simplified (e.g., “flattened”) network architecture including multiple wireless access networks (e.g., 3G and 4G Wireless Wide Area Networks (WWANs)) and multiple wire line networks (e.g., Data Over Cable Service Interface Specification (DOCSIS) and Digital Subscriber Line Access Multiplexer (DSLAM) wire line networks) in accordance with some embodiments.
- WWANs Wireless Wide Area Networks
- DOCSIS Data Over Cable Service Interface Specification
- DSLAM Digital Subscriber Line Access Multiplexer
- FIG. 9 illustrates a hardware diagram of a device that includes a service processor in accordance with some embodiments.
- FIG. 10 illustrates another hardware diagram of a device that includes a service processor in accordance with some embodiments.
- FIG. 11 illustrates another hardware diagram of a device that includes a service processor in accordance with some embodiments.
- FIG. 12 illustrates another hardware diagram of a device that includes a service processor in accordance with some embodiments.
- FIG. 13 illustrates another hardware diagram of a device that includes a service processor implemented in external memory of a System On Chip (SOC) in accordance with some embodiments.
- SOC System On Chip
- FIG. 14 illustrates another hardware diagram of a device that includes a service processor implemented in external memory of a System On Chip (SOC) in accordance with some embodiments.
- SOC System On Chip
- FIGS. 15A through 15C illustrate hardware diagrams of a device that include a service processor and a bus structure extension using intermediate modem or networking device combinations in accordance with various embodiments.
- FIG. 16 is a functional diagram illustrating a device based service processor and a service controller in accordance with some embodiments.
- FIG. 17 is another functional diagram illustrating the device based service processor and the service controller in accordance with some embodiments.
- FIG. 18 is another functional diagram illustrating the device based service processor and the service controller in which the service processor controls the policy implementation for multiple access network modems and technologies in accordance with some embodiments.
- FIG. 19 is another functional diagram illustrating the service processor and the service controller in accordance with some embodiments.
- FIG. 20 is another functional diagram illustrating the service processor and the service controller in accordance with some embodiments.
- FIG. 21 is another functional diagram illustrating the service processor and the service controller in accordance with some embodiments.
- FIG. 22 provides a table summarizing various service processor agents (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments.
- FIG. 23 provides a table summarizing various service controller server elements (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments.
- FIG. 24 is a functional diagram illustrating the service control device link of the service processor and the service control service link of the service controller in accordance with some embodiments.
- FIG. 25 is a functional diagram illustrating framing structure of a service processor communication frame and a service controller communication frame in accordance with some embodiments.
- FIGS. 26A through 26E provide tables summarizing various service processor heartbeat functions and parameters in accordance with some embodiments.
- FIGS. 27A through 27G provide tables summarizing various device based service policy implementation verification techniques in accordance with some embodiments.
- FIGS. 28A through 28C provide tables summarizing various techniques for protecting the device based service policy from compromise in accordance with some embodiments.
- FIG. 29 is a functional diagram illustrating a device communications stack that allows for implementing verifiable traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 30 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 31 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 32 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 33 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 34 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 35 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 36 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 37 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 38 is a functional diagram illustrating a device service processor packet processing flow in accordance with some embodiments.
- FIG. 39 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments.
- FIG. 40 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments.
- FIG. 41 provides a table summarizing various privacy levels for service history reporting in accordance with some embodiments.
- FIGS. 42A through 42F provide tables summarizing various service policy control commands in accordance with some embodiments.
- FIGS. 43A through 43B are flow diagrams illustrating a flow diagram for a service processor authorization sequence as shown in FIG. 43A and a flow diagram for a service controller authorization sequence as shown in FIG. 43B in accordance with some embodiments.
- FIGS. 44A through 44B are flow diagrams illustrating a flow diagram for a service processor activation sequence as shown in FIG. 44A and a flow diagram for a service controller activation sequence as shown in FIG. 44B in accordance with some embodiments.
- FIGS. 45A through 45B are flow diagrams illustrating a flow diagram for a service processor access control sequence as shown in FIG. 45A and a flow diagram for a service controller access control sequence as shown in FIG. 45B in accordance with some embodiments.
- FIG. 46 is a functional diagram illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments.
- FIGS. 47A through 47B are transactional diagrams illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments.
- FIG. 48 illustrates a network architecture including a service controller device control system and a service controller analysis and management system in accordance with some embodiments.
- FIG. 49 illustrates a network architecture for an open developer platform for virtual service provider (VSP) partitioning in accordance with some embodiments.
- VSP virtual service provider
- FIG. 50 illustrates a network architecture including a billing to service controller interface for accommodating minimum changes in existing central billing, AAA and/or other network components in accordance with some embodiments.
- FIG. 51 illustrates a network architecture for locating service controller device control functions with AAA and network service usage functions in accordance with some embodiments.
- FIG. 52 illustrates a network architecture for locating service controller device control functions in the access transport network in accordance with some embodiments.
- FIG. 53 illustrates a network architecture for locating service controller device control functions in the radio access network in accordance with some embodiments.
- FIG. 54 illustrates a network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments.
- FIG. 55 illustrates another network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments.
- FIG. 56 illustrates a 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments.
- FIG. 57 illustrates a network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments.
- FIG. 58 illustrates another 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments.
- FIG. 59 illustrates another network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments.
- FIG. 60 illustrates a 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments.
- FIG. 61 illustrates another network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments.
- FIG. 62 illustrates another 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments.
- FIG. 63 illustrates another network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments.
- FIG. 64 illustrates another network architecture including a system located in the manufacturing or distribution chain for the device that provides the device provisioning or partial provisioning, and any pre-activation required for the device to later activate on the network in accordance with some embodiments.
- the invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor.
- these implementations, or any other form that the invention may take, may be referred to as techniques.
- the order of the steps of disclosed processes may be altered within the scope of the invention.
- a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task.
- the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- network user capacity is increased and user service costs are reduced by managing and billing for service consumption in a more refined manner (e.g., to satisfy network neutrality requirements).
- a more refined manner e.g., to satisfy network neutrality requirements.
- managing service consumption in a user friendly manner the overall service capacity required to satisfy the user device needs can be tailored more closely to the needs of a given user thereby reducing user service costs and increasing service provider profits.
- managing service usage while maintaining user satisfaction includes service usage policy implementation and policy management to identify, manage and bill for service usage categories, such as total traffic consumption, content downloads, application usage, information or content subscription services, electronic commerce transactions, people or asset tracking services or machine to machine networking services.
- service activity is used to refer to any service usage or traffic usage that can be associated with, for example, an application; a network communication end point, such as an address, uniform resource locator (URL) or other identifier with which the device is communicating; a traffic content type; a transaction where content or other material, information or goods are transacted, purchased, reserved, ordered or exchanged; a download, upload or file transfer; email, text, SMS, IMS or other messaging activity or usage; VOIP services; video services; a device usage event that generates a billing event; service usage associated with a bill by account activity (also referred to as billing by account) as described herein; device location; device service usage patterns, device user interface (UI) discovery patterns, content usage patterns or other characterizations of device usage; or other categories of user or device activity that can be identified, monitored, recorded, reported, controlled or processed in accordance with a set of verifiable service control policies.
- URL uniform resource locator
- UI device user interface
- some embodiments identify various service activities for the purpose of decomposing overall service usage into finer sub-categories of activities that can be verifiably monitored, categorized, cataloged, reported, controlled, monetized and used for end user notification in a manner that results in superior optimization of the service capabilities for various levels of service cost or for various types of devices or groups.
- service activity or service usage are associated with categorizing and possibly monitoring or controlling data traffic, application usage, communication with certain network end points, or transactions, and it will also be apparent that in some embodiments the term service activity is intended to include one or more of the broader aspects listed above.
- service usage can be used interchangeably with service activity, but neither term is intended in general to exclude any aspect of the other.
- service usage or service activity are used, more specific descriptors such as traffic usage, application usage, website usage, and other service usage examples are also used to provide more specific examples or focus in on a particular element of the more encompassing terms.
- employing this level of service categorization and control is accomplished in a manner that satisfies user preferences. In some embodiments, employing this level of service categorization and control is accomplished in a manner that also satisfies government rules or regulations regarding open access, for example, network neutrality requirements. In some embodiments, service management solutions that also collect and/or report user or device service usage or service activity behavior to determine how best to meet the user's simultaneous desires for service quality and lower service costs are disclosed. For example, such monitoring and reporting are accomplished in a manner that includes approval by the user and in a manner that also protects the privacy of user information and service usage behavior or service activity history.
- a system and method for increasing network user capacity for wireless networks in the face of increasing service demand per user by providing for a greater number of base stations, also sometimes referred to as access points, base terminals, terminal nodes or other well known acronyms, to be more easily and/or more cost effectively deployed.
- base stations also sometimes referred to as access points, base terminals, terminal nodes or other well known acronyms
- the installation complexity and the network infrastructure required for the base station to obtain backhaul service to the various networks that users desire to connect with are reduced.
- dense base station deployments are simplified by reducing the requirement to aggregate or concentrate the base station traffic through a specific dedicated core network infrastructure, so that the base stations connect to the desired user networks through a more diverse set of local loop, back bone and core routing options.
- This approach also reduces network infrastructure equipment, installation and maintenance costs.
- this is accomplished by distributing the network traffic policy implementation and control away from the core network by providing for more control for service policy implementation and management on the end user device and, in some embodiments, in the end user device with respect to certain service policies and the network (e.g., control plane servers) with respect to other service policies.
- this approach facilitates connecting the base stations directly to the local loop Internet with a minimum of specific dedicated networking infrastructure.
- service and transaction billing event capture and logging are distributed to the device. For example, providing service and transaction billing event capture and logging at the device provides a greater capability to monitor, classify and control deeper aspects of service usage or service activity at the device as compared to the relatively less capability for the same in the network infrastructure (e.g., for certain traffic flows, such as encrypted traffic flows). Furthermore, billing at the device provides for very specialized with many different billing and service plans for different device and service usage or service activity scenario combinations without the problem of attempting to propagate and manage many different deep packet inspection (DPI) and traffic shaping profiles in the networking equipment infrastructure. For example, service billing at the device can provide for more sophisticated, more specialized and more scalable billing and service plans.
- DPI deep packet inspection
- service billing at the device can provide for more sophisticated, more specialized and more scalable billing and service plans.
- Another form of billing that needs improvement is electronic commerce transaction billing with device assisted central billing.
- Today, most central billing and content distribution models require either centralized content distribution maintained by the central service provider or central billing authority, or a centralized ecommerce website or portal traffic aggregation system controlled by the central service provider or central billing provider, or both.
- content and transaction providers such as media providers, application developers, entertainment providers, transaction website providers and others must adapt their mainstream electronic offering and commerce systems, such as shopping experience websites, to fit within the various proprietary customized infrastructure and content storage solutions for ecommerce markets, such as BREW® (Binary Runtime Environment for Wireless from Qualcomm® Inc.), Symbian OS (from Symbian Software Ltd) and Apple iPhone 3G App Store (from Apple Inc.).
- a superior approach includes device based transaction billing for an open ecosystem in which a central billing provider provides users and ecommerce transaction providers with a central billing solution and experience that does not require extensive custom development or ecommerce infrastructure interfacing.
- products that incorporate device assisted service policy implementation, network services and service profiles are disclosed, as described below.
- aspects of the service policy e.g., a set of policies/policy settings for the device for network services, typically referring to lower level settings, such as access control settings, traffic control settings, billing system settings, user notification settings, user privacy settings, user preference settings, authentication settings and admission control settings
- service usage or service activity monitoring and reporting including, for example, privacy filtering, customer resource management monitoring and reporting including, for example, privacy filtering, adaptive service policy control, service network access control services, service network authentication services, service network admission control services, service billing, transaction billing, simplified service activation and sign up, user service usage or service activity notification and service preference feedback and other service capabilities.
- benefits of certain embodiments include the ability to manage or bill for a richer and more varied set of network services, better manage overall network capacity, better manage end user access costs, simplify user or new device service activation, simplify development and deployment of new devices with new service plans (e.g., service profile and billing/costs information associated with that service profile), equip central service providers with more effective open access networks for new third party solutions, simplify the equipment and processes necessary to deploy wireless base stations and simplify the core networking equipment required to deploy certain access networks.
- new service plans e.g., service profile and billing/costs information associated with that service profile
- the central provider network generally refers to the access network required to connect the device to other networks.
- the central provider network generally includes the physical layer, the Media Access Control (MAC) and the various networking functions that can be implemented to perform authentication, authorization and access control, and to route traffic to a network that connects to the control plane servers, as discussed below.
- the service provider network generally refers to the network that includes the control plane servers.
- a central provider network and a service provider network are the same, and in some embodiments, they are different.
- the owner or manager of the central provider network and the owner or manager of the service provider network are the same, and in some embodiments, they are different.
- control of the device service policies is accomplished with a set of service control plane servers that reside in the access network or any network that can be reached by the device.
- This server based control plane architecture provides for a highly efficient means of enabling third party control of services and billing, such as for central carrier open development programs or Mobile Virtual Network Operator (MVNO) relationships.
- MVNO Mobile Virtual Network Operator
- MVNO Mobile Virtual Network Operator
- device processing and memory capacity expands, moving to this distributed service policy processing architecture also becomes more efficient and economical.
- several aspects of user privacy and desired network neutrality are provided by enabling user control of certain aspects of device based service usage or service activity reporting, traffic reporting, service policy control and customer resource management (CRM) reporting.
- CRM customer resource management
- bandwidth capacity is a valuable resource in the face of the increasing popularity of devices, applications and content types that consume more bandwidth.
- a typical present service provider practice is to charge enough per user for access to make service plans profitable for the higher bandwidth users.
- this is not an optimal situation for users who desire to pay less for lower bandwidth service usage or service activity scenarios.
- a range of service plan pricing can be enabled that also maintains service profitability for the service provider, for example, by providing a more refined set of management and control capabilities for service profiles.
- this approach generally leads to service management or traffic shaping where certain aspects of a service are controlled down based on service policies to lower levels of quality of service.
- the first problem is maintaining user privacy preferences in the reporting of service usage or service activity required to set, manage or verify service policy implementation.
- This problem is solved in a variety of ways by the embodiments described below with a combination of user notification, preference feedback and approval for the level of traffic information the user is comfortable or approves and the ability to filter service usage or service activity, in some embodiments, specifically traffic usage or CRM reports so that only the level of information the user prefers to share is communicated.
- the second problem is satisfying network neutrality requirements in the way that traffic is shaped or services are managed.
- This problem is solved in a variety of ways as described in the embodiments described below by empowering the user to make the choices on how service usage, service activity, traffic usage or CRM data is managed down to control costs, including embodiments on user notification and service policy preference feedback.
- the third problem is to help the user have an acceptable and enjoyable service experience for the lower cost plans that will result in much wider scale adoption of connected devices and applications but are more constrained on service activity usage or options or bandwidth or traffic usage.
- lower cost service plans are offered, including plans where the basic connection service may be free, these service plans will require service provider cost controls to maintain profitability or preserve network capacity that result in lower limits on service usage or service activity.
- service usage or service activity limit plans will result in more users who are likely run over service usage limits and either experience service shutdown or service cost overages unless they are provided with more capable means for assistance on how to use and control usage for the lower cost services.
- the above described various embodiments for device based service policy and/or service profile communications control are implemented using network based service control, for example, for satisfying various network neutrality and/or privacy requirements, based on indication(s) received from the device (e.g., user input provided using the device UI using the service processor) and network based service control (e.g., using a DPI service monitor or DPC policy implementation and/or other network elements).
- a virtual network overlay includes a device service processor, a network service controller and a control plane communication link to manage various aspects of device based network service policy implementation.
- the virtual network overlay networking solution is applied to an existing hierarchical network (e.g., for wireless services), and in some embodiments, is applied to simplify or flatten the network architecture as will be further described below.
- the large majority of the complex data path network processing required to implement the richer service management objectives of existing hierarchical networks are moved into the device, leaving less data path processing required in the edge network and in some cases even less in the core network.
- this architecture can be overlaid onto all the important existing access network architectures used today.
- this architecture can be employed to greatly simplify core access network routing and data plane traffic forwarding and management. For example, in the case of wireless networks, the incorporation of device assisted service policy implementation architectures can result in base stations that directly connect to the Internet local loop and the data traffic does not need to be concentrated into a dedicated core network. This results, for example, in a large reduction in backhaul cost, core network cost and maintenance cost.
- the present invention provides the necessary teaching to enable this powerful transformation of centralized network service architectures to a more distributed device based service architectures.
- Device based billing can be compromised, hacked and/or spoofed in many different ways. Merely determining that billing reports are being received from the device, that the device agent software is present and properly configured (e.g., the billing agent is present and properly configured) is insufficient and easily spoofed (e.g., by spoofing the agent itself, providing spoofed billing reports using a spoofed billing agent or providing spoofed agent configurations). Accordingly, in some embodiments, verifiable device assisted and/or network based service policy implementation is provided. For example, verifiable service usage and/or service usage billing can be provided as described herein with respect to various embodiments.
- embodiments described below focus on paid service networks, those of ordinary skill in the art will appreciate that many of the embodiments also apply to other networks, such as enterprise networks.
- the same device assisted network services that create access control services, ambient activation services and other service profiles can be used by corporate IT managers to create a controlled cost service policy network for corporate mobile devices.
- embodiments described below for providing end user service control can also allow a service provider to offer parental controls by providing parents with access to a website with a web page that controls the policy settings for the access control networking service for a child's device.
- FIG. 1 illustrates a simplified (e.g., “flattened”) network architecture in accordance with some embodiments.
- this provides for a simplified service infrastructure that exemplifies a simplified and “flattened” network architecture in accordance with some embodiments that is advantageous for wireless network architectures.
- This also reduces the need for complex data path protocol interaction between the base station and network infrastructure.
- the base stations 125 are connected directly to the Internet 120 via firewalls 124 (in some embodiments, the base stations 125 include the firewall functionality 124 ).
- a central provider network is no longer required to route, forward, inspect or manipulate data plane traffic, because data plane traffic policy implementation is conducted in the device 100 by the service processor 115 .
- Base station control plane communication for access network AAA (Authentication, Authorization, and Accounting) server 121 , DNS/DHCP (Domain Name System/Dynamic Host Configuration Protocol) server 126 , mobile wireless center 132 (sometimes referenced to in part as a home location register (HLR) or other acronym) or other necessary functions are accomplished, for example, with a secure IP tunnel or TCP connection between the central provider network and the base stations.
- the base station 125 is used to refer to multiple base station embodiments where the base station itself is directly connected to the RAN, or where the base station connects to a base station controller or base station aggregator function that in turn connects to the RAN, and all such configurations are collectively referred to herein as base station 125 in FIG. 1 and most figures that follow that reference base station 125 as described below.
- the central provider access network is both 3G and 4G capable
- the devices 100 can be either 3G, 4G or multi-mode 3G and 4G.
- the network could be 2G, 3G and 4G capable, or the device could be 2G, 3G and 4G capable with all or a subset of Global System for Mobile (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) 1 ⁇ , High Speed Packet Access (HSPA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE) and WiMax modem capability.
- GSM Global System for Mobile
- GPRS General Packet Radio Service
- CDMA Code Division Multiple Access
- HSPA High Speed Packet Access
- EVDO Evolution Data Optimized
- LTE Long Term Evolution
- the 3G devices 100 will be activated with a service profile applied to service processor 115 that is consistent with the 3G network capacity and speed, and the 4G devices will be activated with service profiles applied to service processor 115 that are consistent with 4G network capacity and speed.
- the same service controller 122 manages services for both sets of devices in accordance with some embodiments.
- the service processor 115 can be activated with a dual mode service profile capability in which the service profile for 3G offers a similar rich set of services as the service profile for 4G but with, for example, scaled back bandwidth.
- this approach is allows central providers to offer a richer set of service offerings with 3G and then migrate the same set of service offerings to 4G but with higher performance.
- this approach allows 3G to 4G rich service migration to occur, for example, with the only change being the increased bandwidth settings in the service profiles that will be available in 4G at the same cost as 3G with lower service profile bandwidth settings.
- a network selection policy implementation within service processor 115 is provided, or in some embodiments, a network selection policy is driven by policy decisions made in service controller 122 based on service availability reports received from service processor 115 .
- the network selection policy allows the selection of the network that corresponds to the most desirable service profile to meet the user's service preferences.
- the best profile is likely to be the 4G network as 4G is typically faster, except perhaps, for example, if the device 100 is closer to the 3G base station so that there is a much stronger signal or if the 4G network is much more heavily loaded than the 3G network.
- the user preference set specifies cost as the most important factor, then depending on the central provider service costs the 3G network may prove to be the most desirable service profile. This is a simple example and many other selection criteria are possible in the network selection embodiment as discussed further below.
- IPDRs Internet Protocol Detail Records, also sometimes and interchangeably referred to herein as Charging Data Records or CDRs, which as used herein refer to any network measure of service usage or service activity for voice and/or data traffic (e.g., IPDRs can include a time stamp, a device ID, and various levels of network measures of service usage for the device associated with that device ID, such as perhaps total traffic usage, network destination, time of day or device location)) are generated by and collected from the access network equipment.
- IPDRs Internet Protocol Detail Records, also sometimes and interchangeably referred to herein as Charging Data Records or CDRs, which as used herein refer to any network measure of service usage or service activity for voice and/or data traffic (e.g., IPDRs can include a time stamp, a device ID, and various levels of network measures of service usage for the device associated with that device ID, such as perhaps total traffic usage, network destination, time of day or device location)
- the IPDRs can be generated by one or more of the following: base station 125 , RAN or transport gateways and AAA 121 .
- the IPDRs are transmitted to equipment functions that aggregated the IPDRs for the purpose of service billing and other functions. Aggregation can occur in the AAA, the transport gateways or other functions including the billing system 123 .
- a service usage data store 118 e.g., a real-time service usage collection stored in a database or a delayed feed service usage collection stored in a database, or some other network function.
- IPDRs may not be obtained from a variety of other network functions, and in some embodiments, the IPDRs are obtained from other network functions as disclosed herein.
- existing IPDR sources are utilized to obtain network based service usage measures for multiple purposes including but not limited to service policy or profile implementation verification, triggering service verification error responds actions, and service notification synchronization.
- Certain types of IPDRs can be based on, or based in part on, what are sometimes referred to as CDRs (Charging Data Records, which can track charges for voice and data usage) or modifications of CDRs.
- the IPDRs can originate in the base stations or a router or gateway in the central provider network 110 , and the IPDRs are collected at the AAA server 121 and stored in the service usage data store 118 .
- the central billing system 123 collects the IPDRs from the AAA server 121 for service billing accounting purposes.
- a central billing system 123 collects the IPDRs directly from the initial IPDR source or some other aggregator.
- outside partners like MVNOs gain access to the IPDRs from the central billing system 123 . As discussed below, it is assumed that the IPDRs are obtained from the AAA server 121 , and it is understood that the source of the IPDRs is interchangeable in the embodiments.
- an IPDR feed (e.g., also referred to as a charging data record (CDR)) flows between network elements.
- an IPDR feed can flow from the RAN gateway 410 (e.g., SGSN 410 , BSC packet control 510 or RNC 512 ) and the transport gateway 420 (e.g., GGSN or PDSN).
- the IPDRs originate and flow from the base station 125 or some other component/element in the network.
- one or more of these IPDR feeds is transmitted to an IPDR aggregation function (e.g., also referred to as a charging gateway).
- this aggregation function can be located in the AAA 121 , in the mobile wireless center 132 (and/or in the home location register (HLR) or other similar function referred to by other common industry names), in the transport gateway 420 , or in some other network element.
- This aggregation function collects the IPDR feeds into a database with an entry for each device 100 .
- an intermediate aggregation function is provided that feeds a higher level aggregation function
- the transport gateway 420 can receive IPDR feeds from the RAN gateway 410 or the base station 125 before sending them to another aggregation function.
- the IPDR aggregation function sends summary information or detailed information of the IPDRs for a given device or group of devices to the billing system for billing and/or reconciliation.
- the IPDR feed for the service controller 122 is derived from the aggregated feed, either by having the billing system 123 transmit it to the service controller 122 , or by copying it from the IPDR aggregation function.
- the IPDR feed is obtained from the network function that is generating or aggregating the IPDR feed as described herein.
- the IPDR feed is copied from the aggregation function in a manner that does not interrupt the operation of the network.
- a switch based port analysis function can be used to copy the traffic to a traffic analysis or server element that filters out the IPDR traffic and records it to a data base that is then either pushed to the service controller 122 (or any other network element that uses IPDR information as described herein), or is queried by the service controller 122 (or any other function that uses the IPDR information as described herein).
- the IPDR information transmitted to the billing system can be collected from one or more of the sources discussed above including, for example, from another aggregation point (e.g., the feed to the charging gateway, AAA server and/or mobile wireless center/HLR), one or more of the gateways 410 , 420 , 508 , 512 , 520 , 608 , 612 , 620 , 708 , 712 , 720 the base station 125 and/or another network element.
- the IPDR feeds from these or other network functions are copied to a database as described above, which is either pushed or queried to get the information to the service controller 122 or other network elements that request the IPDR information.
- the service processor 115 includes various components, such as device agents, that perform service policy implementation or management functions. In some embodiments, these functions include service policy or implementation verification, service policy implementation tamper prevention, service allowance or denial, application access control, traffic control, network access control services, various network authentication services, service control plane communication, device heartbeat services, service billing, transaction billing, simplified activation services and/or other service implementations or service policy implementations.
- network control of the service policy settings and services as discussed above is accomplished with the service controller 122 which in various embodiments includes one or more server functions.
- service controller 122 server naming and functional breakout is also a design choice and is provided mainly to aid in the discussion. It will be apparent to those of ordinary skill in the art that the server names and functional breakouts do not imply that each name is an individual server, and, for example, a single named function in the various embodiments can be implemented on multiple servers, or multiple named functions in the various embodiments can be implemented on a single server.
- open content transaction partner sites 134 represent the websites or experience portals offered by content partners or ecommerce transaction partners of the service provider.
- transaction servers 134 can provide an electronic commerce offering and transaction platform to the device.
- the central provider has ownership and management of the service controller 122 , so the central provider and the service provider are the same, but as discussed below the service provider that uses the service controller 122 to manage the device services by way of service processor 115 is not always the same as the central provider who provides the access network services.
- further distribution of central provider access networking functions such as access network AAA server 121 , DNS/DHCP server 126 , and other functions are provided in the base stations 125 .
- network based device service suspend/resume control are also provided in the base stations 125 (or in some embodiments, for hierarchical or overlay networks, this function is provided by one or more of the following: RAN gateways, transport gateways, AAA 121 or some other network function).
- central provider network 110 central provider billing system 123 , dedicated leased lines 128 (e.g., for other services/providers), central provider service controller 122 , a content management (e.g., content switching, content billing, and content catching) system 130 , central provider DNS/DHCP server 126 , access network AAA server 121 , service usage data store 118 and central provider mobile wireless center 132 .
- central provider billing system 123 dedicated leased lines 128 (e.g., for other services/providers)
- content management e.g., content switching, content billing, and content catching
- central provider DNS/DHCP server 126 central provider DNS/DHCP server 126
- access network AAA server 121 access network AAA server 121
- service usage data store 118 service usage data store 118
- central provider mobile wireless center 132 central provider mobile wireless center
- the base stations 125 implement a firewall function via firewall 124 and are placed directly onto the local loop Internet for backhaul.
- Voice traffic transport is provided with a secure protocol with Voice Over IP (VOIP) framing running over a secure IP session, for example, Virtual Private Network (VPN), IP Security (IPSEC) or another secure tunneling protocol.
- VOIP Voice Over IP
- VPN Virtual Private Network
- IPSEC IP Security
- the VOIP channel employs another layer of application level security on the aggregated VOIP traffic trunk before it is placed on the secure IP transport layer.
- Base station control traffic and other central provider traffic can be provided in a number of ways with secure transport protocols running over Transmission Control Protocol (TCP), Internet Protocol (IP) or User Datagram Protocol (UDP), although TCP provides a more reliable delivery channel for control traffic that is not as sensitive to delay or jitter.
- TCP Transmission Control Protocol
- IP Internet Protocol
- UDP User Datagram Protocol
- One example embodiment for the control channel is a control link buffering, framing, encryption and secure transport protocol similar to that described below for the service control link between a device and the network.
- a service control heartbeat function is provided to the base stations 125 similar to that implemented between the service controller 122 and the service processor 115 as described below.
- the device based services control plane traffic channel between the service processor 115 and the service controller 122 is implemented over the same control plane channel used for the flat base station control architecture, or in some embodiments, over the Internet.
- the device bases services control plane channel for service processor 115 to service controller 122 communications is established through the Internet 120 or through the access network using IP protocols as this is the more general case and applies to overlay network applications for various embodiments as well as applications where various embodiments are used to enable flattened access networks.
- base stations 125 can be more efficiently provisioned and installed, because, for example, the base station 125 can accommodate a greater variety of local loop backhaul options. In such embodiments, it is advantageous to perform certain basic network functions in the base station 125 rather than the central provider network.
- a basic device suspend/resume function for allowing or disallowing the device Internet access is provided by the base stations 125 (or in some embodiments, for hierarchical or overlay networks in some embodiments this function is provided by one or more of the following: RAN gateways, transport gateways, AAA 121 or some other network function).
- This functionality is important for certain embodiments involving taking action to resolve, for example, service policy verification errors.
- this function is performed at the base station (e.g., base stations 125 ) thereby eliminating the need for a more complex networking equipment hierarchy and traffic concentration required to perform the suspend/resume function deeper in the network.
- Access network base stations control media access and are therefore designed with awareness of which device identification number a given traffic packet, group of packets, packet flow, voice connection or other traffic flow originates from and terminates to.
- the suspend/resume function is implemented in the base station 125 by placing an access control function in the traffic path of each device traffic flow.
- the suspend resume function can be used by various network elements, and in the context of the present embodiment can be used by the service controller 122 (e.g., in some embodiments, access control integrity server 1654 ( FIG. 16 ) of service controller 122 or other service controller elements) to suspend and resume device service based on the assessment of the service policy implementation verification status as described below.
- At least a basic traffic monitoring or service monitoring function is performed at the base station (e.g., base stations 125 ) similar to the service history records or IPDRs collected deeper in the network in more conventional hierarchical access network infrastructure architectures.
- the service or traffic monitoring history records are advantageous for tracking device network service usage or service activity behavior and for certain verification methods for device based service policy implementation or higher device based services as discussed below.
- a traffic monitoring function is provided in the base station 125 in which the traffic for each device is at least counted for total traffic usage and recorded. In some embodiments, traffic inspection beyond simply counting total traffic usage is provided.
- the base station traffic monitor can record and report IP addresses or include a DNS lookup function to report IP addresses or IP addresses and associated Uniform Resource Locators (URLs).
- Another example allows the base station 125 to attach location data to the IPDR to provide device location data in the records.
- traffic inspection includes recording deeper levels of traffic or service monitoring.
- device traffic associated with service verification conditions indicating service usage is out of policy or profile limits or allowances is routed to a quarantine network rather than or as an initial alternative to a suspending service.
- a quarantine network rather than or as an initial alternative to a suspending service.
- the advantages for this approach and a more detailed description of the quarantine network are discussed below.
- the quarantine network capability is provided for in which rather than simply suspending device traffic completely from the network as described above, the base station 125 includes a firewall function (e.g., firewall 124 ) that is capable of passing device access traffic with the quarantine network destinations and blocking device access to all other destinations.
- service verification conditions indicate that service usage is out of policy or profile limits or allowances
- one or more of the following actions are taken: the user is notified of the overage condition, the user is required to acknowledge the overage condition, the user account is billed for the overage condition, and the device is flagged for further analysis by a network device analysis function or a network manager.
- network complexity is reduced using the device without moving completely to a flat base station network as described above.
- Device participation in the core network services implementation provides for numerous measures for simplifying or improving network architecture, functionality or performance. For example, two approaches are discussed below ranging from a simple overlay of the service processor 115 onto devices and the service controller 122 in a conventional hierarchical access network as illustrated in FIGS. 4 through 7 , to a completely flat network as illustrated in FIGS. 1 through 3 and 8 .
- the network based service history records and the network based suspend-resume functionality used in certain embodiments involving service implementation verification are assumed to be derived from the device service history 1618 (as shown in FIG. 16 ) central provider network element and the AAA server 121 central provider network element, and in some embodiments, working in conjunction with other central provider network elements. It is understood that these functions provided by the network can be rearranged to be provided by other networking equipment, including the base station as discussed above. It is also understood that the network based device traffic monitoring, recording and reporting to the device service history 1618 element can be accomplished at the base stations.
- AAA server 121 is assumed to provide the suspend/resume functionality, quarantine network routing or limited network access called for in some embodiments, the AAA server 121 can be a management device in which the actual implementation of the traffic suspend/resume, firewall, routing, re-direction forwarding or traffic limiting mechanisms discussed in certain embodiments can be implemented in the base stations as discussed above or in another network element.
- an activation server 160 (or other activation sequencing apparatus) provides for provisioning, as described below, of the devices 100 and/or network elements in the central provider network so that, for example, the device credentials can be recognized for activation and/or service by the network.
- the activation server 160 provides activation functions, as described below, so that, for example, the devices can be recognized by the network, gain access to the network, be provided with a service profile, be associated with a service account and/or be associated with a service plan.
- the activation server 160 is connected to the central provider core network 110 . In this configuration, the activation server 160 acts as, an over the network or over the air, activation function.
- the activation server 160 is connected to apparatus in the manufacturing or distribution channel, or over the Internet 120 , or as part of the service controller 122 to service provisioning or activation functions.
- the activation server 160 is connected to the central provider core network 110 .
- the activation server 160 is connected to other network extensions such as an MVNO network or the Internet 120 if, for example, the routers in the service gateways or base stations have the capability to direct traffic from devices that are not fully activated or provisioned to an Internet destination, or if the service processor 115 is used for such direction.
- the activation server 160 is included in the service controller 122 .
- FIG. 2 illustrates another simplified (e.g., “flattened”) network architecture including an MVNO (Mobile Virtual Network Operator) relationship in accordance with some embodiments.
- MVNO Mobile Virtual Network Operator
- an open MVNO configuration is provided in a simplified network as similarly described above with respect to FIG. 1 .
- the service provider e.g., service owner
- the service controller 122 is defined by the entity that maintains and/or manages the service controller 122 associated with and controlling the service processors 115 that are inside the devices 100 using the service.
- the service controller 122 requires only a non-real time relatively low data rate secure control plane communication link to the service processors 115 .
- the service controller 122 servers can reside in any network that can connect to (e.g., be in network communication with) the Internet 120 .
- this approach provides for a more efficient provisioning of the equipment used to set up an MVNO partnership between the central provider and the service provider, and as shown in FIG. 2 , an MVNO network 210 is in network communication with the Internet 120 just as with the central provider network 110 is in network communication with the Internet 120 .
- the following are connected to (e.g., in network communication with) the MVNO core network 210 : MVNO billing system 123 , MVNO service controller 122 , MVNO content management system 130 , MVNO DNS/DHCP server 126 , MVNO AAA server 121 , and MVNO mobile wireless center 132 .
- FIG. 2 By showing two service controllers 122 , one connected to (e.g., in network communication with) the MVNO network 210 and one connected to the central provider network 110 , FIG. 2 also illustrates that some embodiments allow two entities on the same access network to each use the service controller 122 and service processor 115 to control different devices and offer different or similar services. As described below, the unique secure communication link pairing that exists between the two ends of the service control link, 1691 and 1638 (as shown in FIG. 16 ), ensure that the two service controllers 122 can only control the devices associated with the correct service provider service profiles.
- FIG. 3 illustrates another simplified (e.g., “flattened”) network architecture including two central providers in accordance with some embodiments. For example, this provides for roaming agreements while maintaining rich services across different networks with completely different access layers.
- the mobile devices 100 are assumed to have a dual mode wireless modem that will operate on both a 4G network, for example LTE or WiMax, and a 3G network, for example HSPA or EVDO.
- a 4G network for example LTE or WiMax
- 3G network for example HSPA or EVDO.
- One example roaming condition would be both Central Provider # 1 and Central Provider # 2 providing 3G and 4G network resources.
- the mobile devices 100 can connect to both 3G and 4G base stations 125 owned and operated by the central provider with whom they have signed up for service, or when neither is available from the central provider the user signed up with the device can roam onto the other central provider access network and still potentially offer the same rich service set using the same service profiles provided, for example, the roaming service costs are reasonable.
- the service processor 115 is configured with a roaming service profile that reduces or tailors service usage or service activity through a combination of one or more of user notification, user preference feedback regarding traffic shaping or service policy management preference collected and acted on by service processor 115 , adaptive policy control in service processor 115 that tracks increasing roaming service costs and scales back service, or recognition of the change in network that causes the service controller 122 to configure service processor 115 of device 100 with a roaming service profile.
- network selection can be based on an automatic network selection with network selection being determined, for example, by a combination of user service profile preferences, service provider roaming deals and/or available roaming network capabilities and cost, as discussed further below.
- the devices 100 are again assumed to be multimode 3G and 4G devices (e.g., the mobile devices 100 are assumed to have a dual mode wireless modem that will operate on both a 4G network, for example LTE, and a 3G network, for example HSPA or EVDO), with the devices 100 being billed for service by Central Provider # 1 being, for example, EVDO and LTE capable, and the devices 100 being billed for service by Central Provider # 2 being, for example, HSPA and LTE capable.
- the devices 100 can roam using the 4G LTE network of the roaming central provider when neither the 3G nor 4G networks are available with the home central provider.
- the service processors 115 and service controllers 122 are capable of providing similar services on the 4G roaming network and the 3G home network as on the 4G home network, however, the varying costs and available network capacity and speed differences of 3G home, 4G roaming and 4G home may also encourage the use of different, such as three different, service profiles to allow for the most effective and efficient selection and control of services based on the current network.
- FIG. 4 illustrates a network architecture including a Universal Mobile Telecommunications System (UMTS) overlay configuration in accordance with some embodiments.
- FIG. 4 includes a 4G/3G/2G HSPA/Transport access network operated by a central provider and two MVNO networks 210 operated by two MVNO partners.
- the central provider can offer improved service capabilities using a conventional UMTS network.
- the base stations 125 do not connect directly to the Internet 120 , and instead the base stations 125 connect to the conventional UMTS network.
- the service processor 115 still connects through the secure control plane link to service controller 122 .
- the data plane traffic is backhauled across the various UMTS network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the access network AAA server 121 .
- the 4G/3G/2G HSPA/Transport access network as shown in FIG.
- the LTE/HSPA and HSPA/GPRS base stations/nodes 125 are in communication with 4G/3G/2G Service/Serving GPRS Support Nodes (SGSNs) cluster 410 via a radio access network 405 , which are in communication with 4G/3G/2G Gateway GPRS Support Nodes (GGSNs) cluster 420 via an access transport network 415 (e.g., a GPRS-IP network), which are then in communication with central provider core network 110 .
- SGSNs 4G/3G/2G Service/Serving GPRS Support Nodes
- GGSNs Gateway GPRS Support Nodes
- service usage data store 118 is a functional descriptor for a network level service usage information collection and reporting function located in one or more of the networking equipment boxes attached to one or more of the sub-networks in the Figure (e.g., RAN, transport and/or core networks).
- service usage 118 is shown as an isolated function connected to the central provider core network 110 and the intention of this depiction is to facilitate all the possible embodiments for locating the service usage 118 function.
- the service usage 118 function is located or partially located in the GGSN gateway (or gateway cluster) 420 .
- service usage 118 functionality is located or partially located in the SGSN gateway (or gateway cluster) 410 .
- service usage 118 functionality is located or partially located in the equipment cluster that includes the AAA 121 and/or the mobile wireless center 132 .
- service usage 118 functionality is located or partially located in the base station, base station controller and/or base station aggregator, collectively referred to as base station 125 in FIG. 4 and many other figures described herein.
- service usage 118 functionality is located or partially located in a networking component in the transport network 415 , a networking component in the core network 110 , the billing system 123 and/or in another network component or function.
- a central provider provides open development services to MVNO, Master Value Added Reseller (MVAR) and/or Original Equipment Manufacturer (OEM) partners.
- all three service providers, central provider service provider, MVNO # 1 service provider and MVNO # 2 service provider have service control and billing control of their own respective devices 100 through the unique pairing of the service processors 115 and service controllers 122 .
- MVNO # 1 and MVNO # 2 can each have open development billing agreements with the central provider and each can own their respective billing systems 123 . As shown in FIG.
- MVNO # 1 core network 210 is in communication with the central provider core network 110 via the Internet 120
- MVNO # 2 core network 210 is in communication with the central provider core network 110 via an alternate landline(LL)/VPN connection 425 .
- the two MVNOs each offer completely different devices and/or services, and the devices and/or services also differ significantly from those offered by the central provider, and the service profiles are adapted as required to service the different devices and respective service offerings.
- the central billing system 123 allows all three service provider user populations to access ecommerce experiences from transaction provider partners operating transaction servers 134 , to choose central provider billing options that combine their third party transaction bills on their service provider bill, and each subscriber population can experience a service provider specified look and feel that is unique to the respective service provider even though the different user populations are interfacing to the same transaction servers and the transaction partners do not need to require significant custom development to provide the unique central billing and unique consistent user experience look and feel.
- a central provider offers open network device and service developer services using one service controller server 122 (e.g., a service controller server farm) and allows the open development partners to lease server time and server tools to build their own service profiles.
- the central provider also provides service billing on behalf of services to the open development partners. For example, this reduces costs associated with setting up an MVNO network for the open development partners and does not require the partners to give up significant control or flexibility in device and/or service control.
- FIG. 5 illustrates a network architecture including an Evolution Data Optimized (EVDO) overlay configuration in accordance with some embodiments. This figure is similar to FIG. 4 except for the various particular variations of the EVDO network architecture as compared to the HSPA/GPRS wireless access network architecture as will be apparent to one of ordinary skill in the art. As shown, FIG. 5 includes an EVDO access network operated by a central provider and two MVNO networks 210 operated by two MVNO partners.
- EVDO Evolution Data Optimized
- the EVDO access network includes LTE/EVDO and EVDO/1 ⁇ RTT base stations 125 in communication with Base Station Controller (BSC) packet control 508 and radio network controller 512 via a radio access network (RAN) 505 , which are in communication with packet data service node 520 via an access transport network 515 , which is in communication with central provider core network 110 .
- BSC Base Station Controller
- RAN radio access network
- a RAN AAA server 521 is also in communication with the access transport network 515 .
- the central provider can offer improved service capabilities using a wireless access network.
- the base stations 125 do not connect directly to the Internet 120 , and instead the base stations 125 connect to the wireless access network.
- the service processor 115 still connects through the secure control plane link to service controller 122 .
- the data plane traffic is backhauled as shown across the various network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the access network AAA server 121 .
- FIG. 6 illustrates a network architecture including a 4G LTE and Wi-Fi overlay configuration in accordance with some embodiments. This figure is also similar to FIG. 4 except for the various particular variations of the 4G LTE/Wi-Fi network architecture as compared to the HSPA/GPRS wireless access network architecture as will be apparent to one of ordinary skill. As shown, FIG. 6 includes a 4G LTE and Wi-Fi access network operated by a central provider and two MVNO networks 210 operated by two MVNO partners.
- the 4G LTE/Wi-Fi access network as shown includes LTE eNodeB and HSPA/EVDO base stations 125 in communication with Base Station Controller (BSC) packet control (EVDO & 1 ⁇ RTT) 608 and SGSN (HSPA & GPRS) 612 via a radio access network (RAN) 605 , which are in communication with System Architecture Evolution (SAE) Gateway (GW) 620 via an access transport network 615 , which is then in communication with central provider (core) network 110 .
- SAE System Architecture Evolution
- GW Gateway
- MME Mobile Management Entity
- a Wi-Fi Access Point (AP) 602 is also in communication with the access transport network 615 via Wi-Fi Access Customer Premises Equipment (CPE) 604 .
- CPE Wi-Fi Access Customer Premises Equipment
- the central provider can offer improved service capabilities using the wireless access network as depicted in FIG. 6 .
- the base stations 125 do not connect directly to the Internet 120 , and instead the base stations 125 connect to the wireless access network.
- the service processor 115 still connects through the secure control plane link to service controller 122 .
- the data plane traffic is backhauled as shown across the various network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the access network AAA server 121 .
- various embodiments can be implemented independent of the wireless access network technology, and for example, can be implemented in 3G, 4G and any other wireless access network technology.
- FIG. 7 illustrates a network architecture including a WiMax and Wi-Fi overlay configuration in accordance with some embodiments. This figure is also similar to FIG. 4 except for the various particular variations of a combined WiMax/Wi-Fi network as compared to the HSPA/GPRS wireless access network architecture as will be apparent to one of ordinary skill in the art.
- FIG. 7 includes both a WiMax and Wi-Fi network (e.g., a combined WiMax/Wi-Fi network) operated by a central provider and two MVNO networks 210 operated by two MVNO partners.
- the Wi-Fi and WiMax access technologies are different wireless access networking technologies, with WiMax providing a wide area networking technology and Wi-Fi providing a local area networking technology, which efficiently operates using the two wireless access networking capabilities.
- some embodiments employ the automatic network selection capability as described above to choose the best available network service profile, and, for example, the user can force the decision or the service controller can make the decision. For example, if free Wi-Fi services have adequate coverage, in most cases, the decision criteria programmed into the automatic network selection algorithm will select Wi-Fi as long as the Wi-Fi access points are associated with a known and trusted provider.
- transaction billing from central provider billing system 123 or MVNO # 1 or MVNO # 2 billing systems 123 will work with the transaction servers when connected over Wi-Fi just as when connected over any other access technology (including wire line based connections).
- the WiMax/Wi-Fi access network as shown includes WiMax base stations 125 , Wi-Fi access points/hotspots 702 and/or Wi-Fi mesh access networks 702 (in some embodiments, femto cells can be used in addition to and/or as an alternative to Wi-Fi), and Wi-Fi access customer-premises equipment (CPE) 704 in communication with WiMax service controller 708 and Wi-Fi service controller 712 via a radio access network 705 , which are in communication with WiMax core gateway 720 via an access transport network 715 , which is then in communication with central provider (core) network 110 .
- CPE customer-premises equipment
- the central provider can offer improved service capabilities using the wireless access network as depicted in FIG. 7 .
- the base stations 125 do not connect directly to the Internet 120 , and instead the base stations 125 connect to the wireless access network.
- the service processor 115 still connects through the secure control plane link to service controller 122 .
- the data plane traffic is backhauled as shown across the various network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the access network AAA server 121 .
- the Wi-Fi connection can be replaced with a femto cell (and the Wi-Fi modem shown in FIGS. 15 B( 3 ) and 15 B( 4 ) can be replaced with a femto cell modem (base station side functionality)).
- the service processor 115 is provided on the femto cell to control subscriber access in a verifiable manner as similarly described herein with respect to various embodiments (e.g., the Wi-Fi related embodiments).
- the femto cell service provider e.g., the entity that owns the spectrum the femto cell is using
- the femto cell service provider can operate the femto cell as a local access mechanism for the home subscriber (or other who purchased or installed the femto cell), and then also use it to provide pay-for-service or additional free services, with controlled access and/or traffic control and/or service control and/or billing control performed locally or in combination with network equipment as described herein.
- the WWAN devices being used at home or work with the femto cell include a portion of the service processor functionality.
- this allows the service provider for femto cells to provide service and monetize service in a controlled way even though the femto cell is not connected to the service provider network the way conventional base stations are connected to the service provider network, but is connected through the Internet 120 .
- the secure heartbeat function can be extended to include data traffic so that it is encrypted and secured along with the control plane traffic.
- the decision of whether or not to admit a device onto the femto cell can be made through the service processor 115 connection to the service controller 122 and subsequent look up of the credentials for the device and the associated service plan and service profile that is then programmed into the service processor on the femto cell and/or the device itself.
- the femto cell can also offer a landing page to devices through the service processor so that devices that do not belong to the network can gain access to the network by signing up over the femto cell.
- the intermediate device embodiments for Wi-Fi on one end and WWAN on the other can be accomplished by using the Wi-Fi connection in the cell phone in AP mode so that it becomes the intermediate device.
- the service processor 115 on the cell phone can then act in the same manner as described for the intermediate device as described herein.
- FIG. 8 illustrates another simplified (e.g., “flattened”) network architecture including multiple wireless access networks (e.g., 3G and 4G Wireless Wide Area Networks (WWANs)) and multiple wire line networks (e.g., Data Over Cable Service Interface Specification (DOCSIS) and Digital Subscriber Line Access Multiplexer (DSLAM) wire line networks) in accordance with some embodiments.
- WWANs Wireless Wide Area Networks
- wire line networks e.g., Data Over Cable Service Interface Specification (DOCSIS) and Digital Subscriber Line Access Multiplexer (DSLAM) wire line networks
- DOCSIS Data Over Cable Service Interface Specification
- DSLAM Digital Subscriber Line Access Multiplexer
- 3G and 4G wireless access networks including a 4G base station 125 and a 3G base station 125 , and both DOCSIS and DSLAM wire line networks (e.g., a combined WWAN/wire line network), including DOCSIS Head End 125 and DSLAM 125 , operated by a central provider via central provider (core) network 110 and an MVNO partner via MVNO network 210 via the Internet 120 .
- DOCSIS and DSLAM wire line networks e.g., a combined WWAN/wire line network
- core central provider
- the service processor 115 can reside on a number of different types of devices 100 that work on 3G or 4G wireless, DSL or DOCSIS, and the service controller 122 is capable of controlling each of these types of devices with a consistent service experience, for example, using different service profiles, service capabilities and service profile cost options depending on which network the device is connected to and/or other criteria.
- a download of a High Definition (HD) movie can be allowed when the service controller 122 is managing service profile policies for a service processor 115 residing on a DOCSIS device 100 (e.g., a computer or laptop connected to a cable modern), but not when the same service controller 122 is managing service profile policies for a service processor 115 residing on a 3G device 100 (e.g., a smart phone connected to a mobile 3G network).
- DOCSIS device 100 e.g., a computer or laptop connected to a cable modern
- 3G device 100 e.g., a smart phone connected to a mobile 3G network
- the present invention can be provided across any access network and a set of service profiles can be defined in a variety of ways including, for example, to user preference feedback, access network performance, access network cost, access network central provider partnership status with the service provider central provider and roaming deals and costs.
- a set of service profiles can be defined in a variety of ways including, for example, to user preference feedback, access network performance, access network cost, access network central provider partnership status with the service provider central provider and roaming deals and costs.
- various embodiments allow for users to have superior service experiences based on the ability to control certain of their service settings, and service providers can also more efficiently deploy a greater variety of services/service plans to users.
- the service processor 115 and the service controller 122 provide an overlay for existing networks without significantly changing the billing system 123 , gateways/routers or other network components/elements, and also provide verifiable service monitoring to control services and/or service usage/costs without involving, for example, a service provider or MVNO (e.g., for smart phone devices and/or laptops or netbooks (or any other network accessible device) with an unlimited data plan or any other service plan).
- MVNO e.g., for smart phone devices and/or laptops or netbooks (or any other network accessible device) with an unlimited data plan or any other service plan.
- applications that are deployed by device owners or service subscribers (e.g., an IT manager) and do not involve a service provider include roaming services provided as an after-market product without carrier/service provider involvement.
- device activity is recorded by the service processor 115 and transmitted to the service controller 122 (e.g., the IT manager controls the service controller 122 ).
- the service controller 122 e.g., the IT manager controls the service controller 122 .
- the device management entity e.g., the IT manager or parents of the device user for parental controls
- VSP Virtual Service Provider
- the VSP secure website techniques described herein can also be applied to service provider owned servers with device partitions for the purpose of controlling, for example, Deep Packet Inspection (DPI) controllers (e.g., DPC policy implementation 5402 as shown in FIG. 54 ) to provide similar or substantially equivalent service usage/control capabilities using network based service control techniques, as similarly described in detail below with respect to FIGS. 49 and 54 (e.g., IT manager VSP control of a group partition and/or MVNO VSP control of a group partition).
- DPI Deep Packet Inspection
- FIG. 9 illustrates a hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments.
- the service processor 115 is stored in a non volatile memory 910 and a memory 920 of the device 100 .
- the present invention can operate with virtually any device architecture, and the device architectures discussed herein (e.g., with respect to FIGS. 9 through 15 ) are examples of various implementations on certain devices (e.g., of different representations of device 100 ).
- device 100 also includes a processor 930 , sometimes referred to as a CPU or central processor unit, an APU or application processor unit, a core processor, a computing device, or many other well known terms.
- device 100 includes one or more processors and/or a multicore processor.
- processor 930 includes a sub-processor 935 .
- processor 930 and/or sub-processor 935 are based on an architecture sometimes referred to as a complex instruction set computer or CISC, a reduced instruction set computer or RISC, a parallel processor, a combination of two or more architectures or any other processor architecture.
- processor 930 has a design that is based on logic and circuitry from one or more standard design library or published architecture, or includes specialized logic and circuitry designed for a given device 100 or collection of such devices.
- a device includes more than one processor and/or sub-processor, and in such a device, one processor and/or sub-processor can have one architecture while another may have a somewhat different or completely different architecture.
- one or more of the processors and/or sub-processors can have a general purpose architecture or instruction set, can have an architecture or instruction set that is partially general or partially specialized, or can have an instruction set or architecture that is entirely specialized.
- a device includes more than one processor and/or sub-processor, and in such a device, there can be a division of the functionality for one or more processors and/or sub-processors.
- one or more processors and/or sub-processors can perform general operating system or application program execution functions, while one or more others can perform communication modem functions, input/output functions, user interface functions, graphics or multimedia functions, communication stack functions, security functions, memory management or direct memory access functions, computing functions, and/or can share in these or other specialized or partially specialized functions.
- any processor 930 and/or any sub-processor 935 can run a low level operating system, a high level operating system, a combination of low level and high level operating systems, or can include logic implemented in hardware and/or software that does not depend on the divisions of functionality or hierarchy of processing functionality common to operating systems.
- device 100 also includes non-volatile memory 910 , memory 920 , graphics memory 950 and/or other memory used for general and/or specialized purposes.
- device 100 also includes a graphics processor 938 (e.g., for graphics processing functions). In some embodiments, graphics processing functions are performed by processor 930 and/or sub-processor 935 , and a separate graphics process 938 is not included in device 100 .
- device 100 includes the following modems: wire line modem 940 , WWAN modem 942 , USB modem 944 , Wi-Fi modem 946 , Bluetooth modem 948 , and Ethernet modem 949 .
- device 100 includes one or more of these modems and/or other modems (e.g., for other networking/access technologies).
- some or all of the functions performed by one or more of these modems are performed by the processor 930 and/or sub processor 935 .
- processor 930 can implement some or all of certain WWAN functional aspects, such as the modem management, modem physical layer and/or MAC layer DSP, modem I/O, modem radio circuit interface, or other aspects of modem operation.
- processor 930 as functionality discussed above is provided in a separate specialized processor as similarly shown with respect to the graphics and/or multimedia processor 938 .
- device 100 includes an internal (or external) communication bus structure 960 .
- the internal communication bus structure 960 generally connects the components in the device 100 to one another (e.g., allows for intercommunication).
- the internal communication bus structure 960 is based on one or more general purpose buses, such as AMBA, AHP, USB, PCIe, GPIO, UART, SPI, I 2 C, Fire wire, DisplayPort, Ethernet, Wi-Fi, Bluetooth, Zigbee, IRDA, and/or any other bus and/or I/O standards (open or proprietary).
- the bus structure is constructed with one or more custom serial or parallel interconnect logic or protocol schemes. As will be apparent to one of ordinary skill in the art, any of these or other bus schemes can be used in isolation and/or in combination for various interconnections between device 100 components.
- all or a portion of the service processor 115 functions disclosed herein are implemented in software. In some embodiments, all or a portion of the service processor 115 functions are implemented in hardware. In some embodiments, all or substantially all of the service processor 115 functionality (as discussed herein) is implemented and stored in software that can be performed on (e.g., executed by) various components in device 100 .
- FIG. 9 illustrates an embodiment in which service processor 115 is stored in device memory, as shown, in memory 920 and/or non-volatile memory 910 , or a combination of both.
- service processor 115 it is advantageous to store or implement certain portions or all of service processor 115 in protected or secure memory so that other undesired programs (and/or unauthorized users) have difficulty accessing the functions or software in service processor 1 15 .
- service processor 115 at least in part, is implemented in and/or stored on secure non-volatile memory (e.g., non volatile memory 930 can be secure non-volatile memory) that is not accessible without pass keys and/or other security mechanisms.
- the ability to load at least a portion of service processor 115 software into protected non-volatile memory also requires a secure key and/or signature and/or requires that the service processor 1 15 software components being loaded into non-volatile memory are also securely encrypted and appropriately signed by an authority that is trusted by a secure software downloader function, such as service downloader 1663 as discussed below (and as shown in FIG. 16 ).
- a secure software download embodiment also uses a secure non-volatile memory.
- all memory can be on-chip, off-chip, on-board and/or off-board.
- the service processor 115 which as shown in FIG. 9 is stored or implemented in non volatile memory 910 and memory 920 , can be implemented in part on other components in device 100 .
- device 100 also includes a user interfaces device component 980 for communicating with user interface devices (e.g., keyboards, displays and/or other interface devices) and other I/O devices component 985 for communicating with other I/O devices.
- user interface devices e.g., keyboards, displays and/or other interface devices
- other I/O devices component 985 for communicating with other I/O devices.
- User interface devices such as keyboards, display screens, touch screens, specialized buttons or switches, speakers, and/or other user interface devices provide various interfaces for allowing one or more users to use the device 100 .
- FIG. 10 illustrates another hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments.
- the service processor 115 is implemented on the processor 930 of the device 100 .
- this implementation can be in part or whole accomplished in software stored, implemented and/or executed on the processor 930 .
- the implementation and/or execution can be in part or whole accomplished in hardware that is on the processor 930 .
- the service processor 115 is shown in FIG. 10 as stored, implemented and/or executed on the processor 930 , in other embodiments, the service processor 115 is implemented in part on other components in device 100 , for example, as discussed below.
- FIG. 11 illustrates another hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments.
- the service processor 115 is implemented on the WWAN modem 942 of the device 100 .
- this implementation can be in part or whole accomplished in software stored, implemented and/or executed on the WWAN modem 942 .
- the implementation and/or execution can be in part or whole accomplished in hardware that is on the WWAN modem 942 .
- service process 115 is implemented on another modem component of device 100 and/or one or more of the modem components of device 100 .
- the service processor 115 is implemented on a modem processor (e.g., WWAN modem 942 or WWAN/Wi-Fi modem), and the service processor 115 can be installed and/or executed in protected and/or secure memory or processor hardware on the modem.
- the modem memory can be made robust to hacking or tampering and, in some embodiments, is only accessible from a secure network management channel or secure device management port and not by most end users.
- a portion of the service processor 115 is implemented on a modem processor (e.g., WWAN modem 942 hardware or software), and a portion of the service processor 115 is implemented on another device 100 processor 930 .
- the device service monitor agent 1696 and one or more service usage measurement points can be implemented on a modem processor, and other service processor 115 elements can be implemented in the main device operating system processor 930 .
- a second (or first) service monitor agent 1696 and one or more service usage measurement points can be implemented on a modem processor, and a first (or second) service monitor 1696 with one or more service measurement points can be implemented on the main operating system processor 930 for device 100 .
- such embodiments can be configured to provide a service usage measurement and reporting system that offers a diversified countermeasure to protect against hacking, tampering or other errors for device based service usage measurements that can be made harder to hack or tamper with than certain software embodiments on the processor 930 .
- such embodiments can be employed when one or more of the following capabilities are not available: network based service usage measures, network based service profile or policy implementation verification measures, and network based service usage verification error response action capabilities.
- certain portions of the service processor 115 that deal with application layer service monitoring or traffic flow identification are implemented on a main processor 930 , and other portions of the service processor 115 are implemented on a modem processor (e.g., WWAN modem 942 ).
- a modem processor e.g., WWAN modem 942
- the WWAN modem is a wide area access technology modem such as 2G, 2 . 5 G, 3G or 4G.
- the connection to the WWAN modem 942 can be a connection internal to device 100 , for example a USB, GPIO, AMBA or other bus, or can be a connection that extends external to the device such as for example a USB, Ethernet, Wi-Fi, Bluetooth or other LAN or PAN connection.
- bus is internal to the device
- a PCIe modem card running over USB or PCIe
- a GPIO connection running from a processor 930 chipset to a modem chipset inside a mobile device
- a Wi-Fi connection running from a Wi-Fi modem inside of device 100 to an intermediate modem or networking device combination that forwards the access network traffic between the access network connection and the device via the Wi-Fi connection.
- service processor 115 in addition to the service processor 115 being implemented on the WWAN modem 942 either internal or external to the device 100 , similarly service processor 115 can be implemented on a wire line modem 940 , such as DSL, Cable or fiber, another wireless LAN or PAN modem, such as Wi-Fi, Zigbee, Bluetooth modem 948 , White Space, or some other modem, connected internal to device 100 or external to device 100 via a LAN or PAN extension of internal or external communications bus structure 960 .
- wire line modem 940 such as DSL, Cable or fiber
- another wireless LAN or PAN modem such as Wi-Fi, Zigbee, Bluetooth modem 948 , White Space, or some other modem
- a complete turn-key reference design product for the device modem (one or more of 942 , 946 , 948 , 949 , 944 , 940 ) combined with a built-in service processor 115 , possibly with a well defined and documented application interface and a well defined and documented service processor developers kit (SPDK) provides for a powerful product embodiment for the purpose of achieving mass market distribution and usage for the modem with service processor 115 and associated service controller 122 features.
- SPDK service processor developers kit
- embodiments that include the WWAN modem 942 can be combined with a pre-tested or pre-certified integrated embodiment of the service processor 115 , possibly in combination with a well defined API for writing software applications that interface to, reside on or communicate with this turn-key modem embodiment.
- the advantageous capabilities of the service processor 115 to assist in monitoring, control, billing and verification for services is made more available for device 100 manufacturers in such a form, because the manufacturers do not need to spend as much time and resources to develop a custom modem only for a subset of devices that the turn-key modem can be used to support.
- the service processor 115 can be configured to provide device assisted service monitoring, control, billing and/or verification across not just when connected to the WWAN network via the WWAN modem, but also when connected to the other networks corresponding to the other access modems included in the turn-key combined module plus service processor 115 (or SPDK or chipset plus service processor 115 ) design.
- the pre-integrated service processor 115 and API possibly in combination with testing and certification can be packaged in a small form factor that may have standardized interfaces such as USB, PCIe, firewire, Display Port, GPIO, or other interface.
- the form factor may be miniaturized into standard configurations such as minicard, half minicard or even smaller form factors, or it can be designed into a non-standard or proprietary form factor.
- the module form factor can be well documented to simplify integration into various device 100 designs.
- the SPDK embodiments can be designed to contain one or more of the following: hardware integration and use documentation, software integration documentation, software programming documentation, application interface documentation, service controller documentation, overall testing guidelines and overall use guidelines.
- the modem module can be integrated with the service processor 115 functionality as a combined chipset, firmware and/or software product, with other SPDK features very similar to those listed above.
- the service controller programming guide for these turn-key embodiments can also be documented for the SPDK service processor 115 software, turn-key module with service processor 115 or integrated chipset with service processor 115 . Accordingly, these embodiments provide various solutions to simplify the OEM task of integrating, developing, testing and shipping device 100 products (or integrated networking device products) with any of the device assisted service monitoring, control, billing or verification capabilities disclosed herein.
- FIG. 12 illustrates another hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments.
- the service processor 115 is implemented on the other I/O devices component 980 of the device 100 .
- this implementation can be in part or whole accomplished in software stored, implemented and/or executed on the other I/O devices component 980 (e.g., a SIM/USIM card or other secure hardware I/O device).
- the implementation and/or execution can be in part or whole accomplished in hardware that is on the other I/O devices component 980 .
- various embodiments include product designs in which the service processor 115 resides on device volatile or non-volatile memory (see FIG. 9 ), the device application processor or CPU (see FIG. 10 ), the wireless access modem (see FIG. 11 ) (or any other modem), or another I/O device (see FIG. 12 ). While these are just a few of the example service processor 115 placement embodiments, these embodiments show that the placement of where the software or hardware for implementing the service processor 115 can reside in the device 100 is very flexible and can be implemented in a myriad of places and ways depending on the device and/or other technical design choices.
- FIG. 13 illustrates another hardware diagram of a device 100 that includes a service processor 115 implemented in external memory of a System On Chip (SOC) 1310 in accordance with some embodiments.
- the service processor 115 is implemented on the external memory 1320 of the device 100 .
- this implementation can be in part or whole accomplished in software stored, implemented and/or executed on the external memory 1320 .
- the implementation and/or execution can be in part or whole accomplished in hardware that is on the external memory 1320 .
- SOC chipset 1310 and external memory 1320 provide a portion or all of the hardware of device 100 .
- FIG. 14 illustrates another hardware diagram of a device 100 that includes a service processor 115 implemented in external memory of a System On Chip (SOC) 1310 in accordance with some embodiments.
- the service processor 115 is stored in a non volatile memory 910 and a memory 920 of the SOC chipset 1310 , as similarly discussed above with respect to FIG. 9 .
- SOC chipset 1310 and external memory 1320 provide a portion or all of the hardware of device 100 .
- various embodiments include product designs including the SOC chipset 1310 in which the service processor 115 resides on internal volatile or non-volatile memory 910 of the SOC chipset 1310 (see FIG. 14 ), the device application processor or CPU 930 and/or sub processor 935 , the modems 940 , 942 , 944 , 946 , 948 , and/or 949 (or any other modem), another I/O device 985 , and/or external memory 1320 (see FIG. 13 ) (and/or any combinations thereof).
- SOC chipset 1310 and/or the external memory 1320 of the device 100 is very flexible and can be implemented in a myriad of places and ways depending on the device and/or other technical design choices.
- FIGS. 9 through 14 illustrating various internal hardware embodiments for device 100 apply equally to this partitioning of device functionality or any other partitioning of how the components in device 100 are configured, whether they are all separate components, some of the components are combined into a single chipset but there are still multiple chipsets, or all of the components are combined into a chipset.
- FIGS. 9 through 14 illustrating various internal hardware embodiments for device 100 show several access modem components including the wire line modem 940 , wireless wide area network (WWAN) modem 942 , USB modem 944 , Wi-Fi modem 946 , Bluetooth modem 948 , and Ethernet modem 949 .
- WWAN wireless wide area network
- wire line modem 940 is a DSL or cable modem such as DOCSIS, or some other modem with a hard connection such as fiber.
- connection to the wire line or wireless access network is accomplished through an extension of the internal or external communications bus structure 960 .
- such an extension is accomplished using one or the other modems, such as Wi-Fi modem 946 or Ethernet modem 949 , connecting to a local area network that in turn connects to the access network via a device that bridges the local area network to the access network.
- connection can be via a direct connection to the network, such as a 3G or 4G WWAN modem 942 connection to a 3G or 4G WWAN network, or can be a connection to the access network through an intermediate connection, such as a Wi-Fi modem 946 connection to a modem or networking device combination that has a Wi-Fi LAN connection and a 3G or 4G network access network connection.
- a Wi-Fi modem 946 connection to a modem or networking device combination that has a Wi-Fi LAN connection and a 3G or 4G network access network connection.
- Another example of an extended modem connection embodiment includes a Wi-Fi modem 946 device connection to a modem or networking device combination that includes a Wi-Fi LAN connection and a DOCSIS or DSL network access connection.
- Other examples of such combinations will be readily apparent to one of ordinary skill in the art.
- FIGS. 15A through 15C illustrate hardware diagrams of a device 100 that include a service processor 115 and a bus structure extension 1510 using intermediate modem or networking device combinations in accordance with various embodiments.
- FIGS. 15A and 15B illustrate various extended modem alternatives for access network connection through an intermediate modem or networking device combination that has a connection (e.g., LAN connection) to one or more devices 100 .
- a connection e.g., LAN connection
- deyice 100 includes a 3G and/or 4G network access connection in combination with the Wi-Fi LAN connection to the device 100 .
- the intermediate device or networking device combination can be a device that simply translates the Wi-Fi data to the WWAN access network without implementing any portion of the service processor 115 as shown in FIG. 15 B( 1 ).
- an intermediate device or networking device combination includes a more sophisticated implementation including a networking stack and some embodiments a processor, as is the case for example if the intermediate networking device or networking device combination includes a router function, in which case the service processor 115 can be implemented in part or entirely on the intermediate modem or networking device combination.
- the intermediate modem or networking device combination can also be a multi-user device in which more than one user is gaining access to the 3G or 4G access network via the Wi-Fi LAN connection.
- the access network connection can include several managed service links using multiple instantiations of service processor 115 , each instantiation, for example, being implemented in whole or in part on device 100 with the intermediate modem or networking device combination only providing the translation services from the Wi-Fi LAN to the WWAN access network.
- the service processors 115 are implemented in part or in whole on the intermediate modem or networking device combination.
- the service processor 115 can be implemented for each device or each user in the network so that there are multiple managed service provider accounts all gaining access through the same intermediate modem or networking device combination.
- the functions of service processor 115 are implemented on an aggregate account that includes the WWAN access network traffic for all of the users or devices connected to the Wi-Fi LAN serviced by the intermediate modem or networking device combination.
- the central provider can also provide an aggregated account service plan, such as a family plan, a corporate user group plan and/or an instant hotspot plan.
- an aggregated account service plan such as a family plan, a corporate user group plan and/or an instant hotspot plan.
- the intermediate modem or networking device combination can implement a local division of services to one or more devices 100 or users in which the services are controlled or managed by the intermediate modem or networking device combination or the device 100 , but the management is not subject to service provider control and is auxiliary to the service management or service policy implementation performed by service processors 115 .
- another service model can also be supported in which there is an aggregate service provider plan associated with one intermediate modem or networking device combination, or a group of intermediate modems or networking device combinations but where each user or device still has its own service plan that is a sub-plan under the aggregate plan so that each user or device has independent service policy implementation with a unique instantiation of service processor 115 rather than aggregate service policy implementation across multiple users in the group with a single instantiation of service processor 115 .
- device 100 includes a Wi-Fi modem 946 , a Wi-Fi modem 946 combined with a 3G and/or 4G WWAN modem 1530 on intermediate modem or networking device combination 1510 , and the intermediate modem or networking device combination forwards WWAN access network traffic to and from device 100 via the Wi-Fi link.
- the service processor 115 can be implemented in its entirety on device 100 and the service provider account can be associated exclusively with one device. This is an embodiment associated with one or more of FIG. 29 , 31 , 32 or 34 discussed below, in which the modem bus represents the Wi-Fi LAN connection via the Wi-Fi modem 946 .
- such an implementation can be provided using a different access modem and access network, such as a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem or networking device combination 1510 .
- a different access modem and access network such as a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem or networking device combination 1510 .
- various other embodiments similarly use DSL as shown in FIGS. 15 A and 15 B( 4 ), USB, Ethernet, Bluetooth, or another LAN or point to point connection from device 100 to the intermediate modem or networking device combination 1510 .
- a portion of the service processor 115 is implemented on the device 100 , such as the application interface agent 1693 and other supporting agents (see FIG. 16 ), and another portion of the service provider 115 is implemented on the intermediate modem or networking device combination, such as policy implementation agent 1690 or possibly modem firewall 1655 as well as other agents (see FIG. 16 ).
- This is an embodiment associated with one or more of FIG. 30 or 36 discussed below, in which the modem bus in the figure represents the Wi-Fi LAN connection via the Wi-Fi modem 946 .
- the service provider 115 can still offer individual service plans associated exclusively with one device, or can offer an aggregate plan in which the portion of the service processor 115 located on the intermediate modem or networking device combination 1510 aggregates service plans into one WWAN connection but each individual device 100 has a unique service interface via the application interface agents and associated agents located on device 100 .
- such an implementation can be provided using a different access modem and access network, for example a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem or networking device combination 1510 .
- various other embodiments similarly use USB, Ethernet, Bluetooth, or another LAN or point to point connection from device 100 to the intermediate modem or networking device combination 1510 .
- all of the service processor 115 is implemented on the intermediate modem or networking device combination 1510 and the aggregate device or user traffic demand from the LAN port is serviced through one service provider service plan account.
- This is an embodiment associated with FIG. 35 in which as discussed below the modem bus in the figure represents the Wi-Fi LAN connection via the Wi-Fi modem 946 .
- such an implementation can be provided using a different access modem and access network, for example a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem or networking device combination 1510 .
- various other embodiments similarly use USB, Ethernet, Bluetooth, or another LAN or point to point connection from device 100 to the intermediate modem or networking device combination 1510 .
- the device 100 uses the on-board WWAN modem 942 when it is outside of Wi-Fi LAN coverage area for one or more trusted access networks for the device, and when the device comes within range of a Wi-Fi network associated with a intermediate modem or networking device combination connected to a trusted wire line access network, the device can switch to the Wi-Fi link service to connect service processor 115 to the trusted wire line access network.
- the decision to switch to the Wi-Fi LAN associated with a trusted wire line access network can be made automatically by the device based on the policy implementation rules settings for the modem selection and control 1811 and/or the policy control agent 1692 , can be made by the user, or can be made by the service controller 122 (see FIG. 18 ).
- various other embodiments similarly use USB, Ethernet, Bluetooth, or another LAN or point to point connection from device 100 to the intermediate modem or networking device combination 1510 .
- FIG. 15C illustrates another hardware diagram of a device 100 that includes a service processor 115 and a bus structure extension 1510 using intermediate modem or networking device combinations in accordance with various embodiments.
- more than one access network connection is implemented in the intermediate modem or networking device combination 1510 .
- This allows the device 100 to potentially connect through the intermediate modem or networking device combination with a choice of access network services.
- An example of such an embodiment is illustrated in FIG. 15C in which an access network router (e.g., an enterprise router) connected to a LAN with a wire line primary backhaul connection and a back up WWAN connection, for example 3G or 4G, to provide access services when the primary wire line connection fails.
- an access network router e.g., an enterprise router
- the service provider service profile for service processor 115 and the service plan account can be set up as an aggregate account with multiple users connected to the LAN.
- the service provider can elect to use an embodiment that includes a portion of the service processor 115 on each device 100 so that the account can be managed for each user or each device, or the service provider can elect to implement all of the necessary features in the service processor 115 on the intermediate modem or networking device combination so that there is no visibility to the individual devices 100 or users.
- various embodiments provide many service policy implementation options that can enhance the service provider control of the service experience and cost, or enhance the user control of the service experience and cost by providing a verifiable or compromise resistant solutions to manage service policy implementation on the intermediate modem or networking device combination, for one or both of the WWAN or wire line access networks, when the WWAN access network is active, or when the WWAN access network is inactive.
- the level of service control, user preference feedback and service policy implementation verification or compromise resistance enabled by these embodiments improves the offered back up services and primary wire line services.
- any number of wire line and/or wireless network access connections can be supported by the various embodiments as described herein, with any number of device architectures and architectures for intermediate modem or networking device combinations bridging the device to the access network of choice.
- various embodiments provide a verifiable managed service architecture, design and implementation for any number of single access and/or multi-access networks in which the service account can be consistent across multiple networks, and the service policies can be changed from network to network as deemed appropriate by the service provider with service notification, service cost control and privacy preference inputs from the user.
- the verification embodiments discussed herein for service policy implementation verification or service policy implementation compromise protection can be applied.
- a service provider service plan account rather than attaching a service provider service plan account to a single device, it is attached to (e.g., associated with) a user. For example, when the user logs onto an access network with a service controller controlled by a service provider, regardless of what device the user logs onto with the user's service plan profile can be automatically looked up in the central billing system 123 and dynamically loaded (e.g., downloaded) onto the device 100 from the service controller 122 (e.g., a service profile provided on demand based on the user's identity).
- one or more of the user's preferences including notification, service control, traffic monitor reporting privacy and Customer Relationship Management (CRM) reporting privacy are also dynamically loaded. For example, this allows the user to have the same service settings, performance and experience regardless of the device the user is logged into and using on the network.
- CCM Customer Relationship Management
- the user service plan profile that includes all of the above in addition to the service plan profile changes that take effect between different types of access network, can be used on any device and on any network, providing the user with a verifiable or compromise resistant, consistent service experience regardless of network or device.
- Various embodiments of the device 100 described above include other I/O devices 985 .
- these other devices include other modems, other special purpose hardware components, and/or other I/O devices or drivers or modems to connect to other I/O devices.
- these other devices include a Subscriber Identity Module (SIM) or Universal Subscriber Identity Module (USIM) device.
- SIM Subscriber Identity Module
- USIM Universal Subscriber Identity Module
- the other I/O devices 985 include a hardware device designed to implement a portion or all of the service processor 115 functions.
- this is advantageous in cases in which the original device 100 was not manufactured with the service processor 115 ; in cases in which dedicated hardware is desired to improve one or more aspects of service processor 115 performance; allowing users, for example, to have the same service settings, performance and experience regardless of the device the user is using on the network by using such a SIM and/or USIM (e.g., or implemented as a type of dongle); and/or in cases in which a separate component is desired to assist in compromise protection for one or more aspects of service processor 115 .
- SIM and/or USIM e.g., or implemented as a type of dongle
- some embodiments described herein provide for billing of certain access services.
- various applications do not require or involve billing of certain services.
- applications like enterprise IT (Information Technology) group management of enterprise workforce access policy implementation or access cost control or access security policy, privacy control, parental control, network quality of service control or enhancement, private network services, free access services, publicly funded access services, flat rate no-options service and other services, or other examples that will be apparent to one of ordinary skill in the art do not require billing functionality but benefit from many other aspects of various embodiments.
- enterprise IT Information Technology
- FIG. 16 is a functional diagram illustrating a device based service processor 115 and a service controller 122 in accordance with some embodiments. For example, this provides relatively full featured device based service processor implementation and service controller implementation. As shown, this corresponds to a networking configuration in which the service controller 122 is connected to the Internet 120 and not directly to the access network 1610 . As shown, a data plane (e.g., service traffic plane) communication path is shown in solid line connections and control plane (e.g., service control plane) communication path is shown in dashed line connections. As previously discussed, it is understood that the division in functionality between one device agent and another is based on, for example, design choices, networking environments, devices and/or services/applications, and various different combinations can be used in various different implementations.
- service traffic plane e.g., service traffic plane
- control plane e.g., service control plane
- the functional lines can be re-drawn in any way that the product designers see fit. As shown, this includes certain divisions and functional breakouts for device agents as an illustrative implementation, although other, potentially more complex, embodiments can include different divisions and functional breakouts for device agent functionality specifications, for example, in order to manage development specification and testing complexity and workflow.
- the placement of the agents that operate, interact with or monitor the data path can be moved or re-ordered in various embodiments. For example, as discussed below in some embodiments, one or more of the policy implementation or service monitoring functions can be placed on one of the access modems located below the modem driver and modem bus in the communication stack as illustrated in certain figures and described herein.
- service processor 115 includes a service control device link 1691 .
- the service control device link 1691 provides the device side of a system for transmission and reception of service agent to/from network element functions.
- the traffic efficiency of this link is enhanced by buffering and framing multiple agent messages in the transmissions.
- the traffic efficiency is further improved by controlling the transmission frequency or linking the transmission frequency to the rate of service usage or traffic usage.
- one or more levels of security or encryption are used to make the link robust to discovery, eavesdropping or compromise.
- the service control device link 1691 also provides the communications link and heartbeat timing for the agent heartbeat function. As discussed below, various embodiments disclosed herein for the service control device link 1691 provide an efficient and secure solution for transmitting and receiving service policy implementation, control, monitoring and verification information with other network elements.
- the service control device link 1691 agent messages are transmitted asynchronously as they are generated by one or more of the service agents.
- the service control device link 1691 performs collection or buffering of agent messages between transmissions.
- the service control device link 1691 determines when to transmit based potentially on several parameters including, for example, one or more of the following parameters: periodic timer trigger, waiting until a certain amount of service usage or traffic usage has occurred, responding to a service controller message, responding to a service controller request, initiated by one or more agents, initiated by a verification error condition, initiated by some other error or status condition.
- the service control device link 1691 assembles all buffered agent communications and frames the communications.
- the transmission trigger is controlled by waiting for an amount of service usage, such as waiting until a certain amount of data traffic has passed, which reduces the control plane communication channel traffic usage to a fraction of the data plane traffic. For example, this approach preserves network capacity and reduces service cost even in traffic scenarios in which data traffic is light.
- the transmission trigger is based on waiting for an amount of service usage, and also including a minimum transmission rate that triggers a transmission according to one or more of the following parameters: a maximum time between transmissions clock to keep the service processor 115 in communication with the service controller 122 when little or no service usage is occurring, a polling request of some kind from the service controller 122 , a response to a service controller heartbeat, a transmission generated by a service verification error event, or a transmission generated by some other asynchronous event with time critical service processor 115 (or service controller 122 ) messaging needs, such as a transaction or service billing event or a user request.
- service control plane traffic down is reduced to a relatively inexpensive and capacity conserving trickle when device 100 data traffic is not significant.
- this approach also provides an effective flow of real time or near real-time service control plane traffic that is both cost and capacity efficient, because the service control plane traffic is a relatively small percentage of the data plane traffic when data plane traffic usage is heavy.
- the time when close monitoring of service policy implementation verification or compromise prevention can be particularly important and by keeping the control plane overhead to a fraction of data plane traffic close monitoring and control of services are maintained at a reasonable cost in terms of percentage of both bandwidth used and network capacity.
- the service usage or service activity trigger occurs based on some other measure than traffic usage, such as a number of messages transacted, one or more billing events, number of files downloaded, number of applications run or time that an application has been running, usage of one or more specified applications, GPS coordinate changes, roaming event, an event related to another network connection to the device and/or other service related measures.
- the service control device link 1691 provides for securing, signing, encrypting or otherwise protecting communications before sending.
- the service control device link 1691 can send to the transport layer or directly to the link layer for transmission.
- the communications are further secured with transport layer encryption, such as TCP TLS (Transport Control Protocol Transport Layer Security) or another secure transport layer protocol.
- transport layer encryption such as TCP TLS (Transport Control Protocol Transport Layer Security) or another secure transport layer protocol.
- communications are encrypted at the link layer, such as IPSEC (Internet Protocol Security), various VPN (Virtual Private Network) services, other forms of IP layer encryption and/or another link layer encryption technique.
- the service control link 1691 includes the above discussed agent heartbeat function in which the agents provide certain required reports to the service controller 122 for the purpose of service policy implementation verification (e.g., verification related reports on certain aspects of the service processor 115 ) or for other purposes.
- agent heartbeat messages can be in the open/clear (unencrypted) or encrypted, signed and/or otherwise secured.
- these messages include one or more of the below described types of messages: an agent information message, an agent check-in message and/or agent cross check message.
- an agent information message is included in the agent heartbeat service policy implementation verification message, which includes, for example, any information the agent needs to communicate to the service controller 122 as part of the operation of the service policy implementation system.
- an agent response to a service controller challenge can be included in the agent heartbeat service policy implementation verification message.
- an agent check-in message is included in an agent heartbeat service policy implementation verification message, which includes, for example, a transmission of a unique agent identifier, secure unique identifier, and/or hashed encrypted and signed message beginning with some shared secret or state variable for the hash.
- an agent self-check can be included in the agent heartbeat service policy implementation verification message, which includes reporting on agent configuration, agent operation, agent code status, agent communication log, agent error flags, and/or other agent associated information potentially hashed, encrypted, signed or otherwise secured in the message (e.g., using a shared secret unique to that agent).
- agent heartbeat service policy implementation verification message which includes, for example, reports on the status, configuration, operation observations, communication log or other aspects of another agent.
- agent environment reports can be included in the agent heartbeat service policy implementation verification message, which includes, for example, reports on certain aspects of the service processor 1 15 operating environment, such as software presence (e.g., installation status of certain operating system and/or application software and/or components thereof), observed communication with agents or communication attempts, memory accesses or access attempts, network accesses or access attempts, software downloads or attempted downloads, software removal or download blocking, service policy implementation verification or compromise event error conditions with respect to the operating environment for the service processor 115 , and/or other messages regarding the verification or possibility of compromise associated with the service processor 115 operating environment or agents.
- software presence e.g., installation status of certain operating system and/or application software and/or components thereof
- the agent heartbeat function also provides regular updates for information important to user service notification services.
- the network based elements can provide regular synchronization updates for the device based service usage or service activity counters in which service usage or service activity measures available from one or more network service history elements is transmitted to the device 100 . This allows the service usage counter errors between the device service counter and the counters used for central billing to be minimized.
- a common service usage or service activity measure is total traffic usage measured to date within a time frame over which a service limit is applicable. Other service usage or service activity measures can also be tracked and reconciled in a similar manner.
- the service controller 122 verifies that the scheduled agent reports are being received and that the reports are within expected parameters.
- the access control integrity server 1654 issues signed challenge/response sequences to the policy implementation agent 1690 .
- the challenges can be asynchronous, issued when an event or error condition occurs, issued on a schedule or issued when a certain amount of data has passed.
- This approach provides a second layer of service policy implementation verification that strengthens the service usage or service activity measurement verification.
- a challenge/response can be sent over the heartbeat link for the purpose of verifying device agent integrity.
- Various challenge/response related verification embodiments are described below.
- the challenge/response heartbeat message can include sending any kind of command or query, secure or transmitted in the open, receiving a response from the agent and then evaluating the response to determine if the response is within a range of parameters expected for a correctly configured agent, an agent that is operating properly, an agent that is not partially compromised or an agent that is not entirely compromised.
- the agent is only required to respond with a simple acknowledgement of the challenge.
- the agent is required to respond with a message or piece of information that is known by the agent.
- the agent is required to respond with a message or piece of information that is difficult for the agent to respond correctly with if it were to be partially or entirely compromised.
- the agent is required to respond back with information regarding the operation or configuration of the agent that is difficult for the agent to respond properly with if the agent is not properly configured, not operating properly, is partially compromised or is entirely compromised.
- the first agent is required to respond back with information regarding the operation, configuration, status or behavior of a second agent that is difficult for the first or second agent to respond properly with if the first or second agent is not properly configured, not operating properly, is partially compromised or is entirely compromised.
- the agent is required to respond with a response that includes a shared secret.
- the agent is required to respond with information regarding the presence, configuration, operating characteristics or other information regarding other programs in the operating environment of the agent.
- the agent is required to respond with hashed information to be portions of code or a code sample (e.g., the code portion or code sample can be specified by the service controller 122 ).
- the information the agent responds with is a response to a signed or encrypted message from the service controller 122 in which the agent must know how to decode the encrypted controller message in order to respond correctly or it would be difficult for the agent to respond properly if the agent is not configured properly, is not operating within appropriate limits, is partially compromised or is entirely compromised.
- the agent signs or encrypts information in such a manner that it is difficult to respond correctly when the message is decoded by the service controller 122 unless the agent is configured properly, is operating within appropriate limits, is not partially compromised and is not entirely compromised.
- the agent is required to respond with a signed or encrypted hash of information that is difficult for the agent to generate unless the agent is configured properly, is operating within appropriate limits, is not partially compromised and is not entirely compromised.
- the hashed information can be local device configuration information, portions of code or all of the code, and/or the code portion to be used in the response can be specified by the service controller.
- the hashed information the agent responds with can include a shared secret, and/or the hashed information can be information regarding the presence, configuration, operating characteristics or other information regarding other programs in the operating environment of the agent.
- the agent heartbeat function provides an important and efficient system in some embodiments for verifying the service policy implementation or protecting against compromise events.
- the agent heartbeat service can perform and some are described herein while others will be apparent to one of ordinary skill in the art given the principles, design background and various embodiments provided herein.
- the service control device link 1691 facilitates another important function, which is the download of new service processor software elements, revisions of service processor software elements, and/or dynamic refreshes of service processor software elements. There are many embodiments for such operations.
- the software is received as a single file over the service control device link 1691 .
- the file can have encryption or signed encryption beyond any provided by the communication link protocol itself.
- the software files are segmented into smaller packets that are communicated in multiple messages sent over the service control device link 1691 .
- the file(s) are received, or the segmented portions of the file(s) are received, they are communicated to a service downloader 1663 for file aggregation and installation, which, in some embodiments, is performed after further measures to verify the service processor software are completed.
- the files are sent using other delivery means, such a direct TCP socket connection to the service downloader 1663 or some other software installer, which can also involve secure transport and additional levels of encryption.
- an agent communication bus 1630 represents a functional description for providing communication for the various service processor 115 agents and functions.
- the architecture of the bus is generally multipoint to multipoint so that any agent can communicate with any other agent, the service controller or in some cases other components of the device, such user interface 1697 and/or modem components.
- the architecture can also be point to point for certain agents or communication transactions, or point to multipoint within the agent framework so that all agent communication can be concentrated, or secured, or controlled, or restricted, or logged or reported.
- the agent communication bus is secured, signed, encrypted, hidden, partitioned and/or otherwise protected from unauthorized monitoring or usage.
- there are multiple layers of security applied to the agent communication bus 1630 communication protocols such as including one or more of the following: point to point message exchange encryption using one or more keys that are partially shared or shared within the service processor 115 agent group and/or the service controller 122 , point to point message exchange that using one or more keys that are private to the two endpoints of the communication, a bus-level message exchange encryption that can be in place of or in addition to other encryption or security, or using one or more keys that are partially shared or shared within the service processor 115 agent group and/or the service controller 122 , a set of secure messages that can only be decoded or observed by the agents they are intended for, a set of secure messages that allow communication between certain agents or service processor functions and entities outside of the service processor operating environment.
- the service control device link 1691 is assumed to be equivalent to an agent for communication purposes, and, in the case of the service control device link 1691 , the communication is not restricted to the agent communication bus 1630 but also extends to the service control communications link 1653 .
- the system has the capability to replace keys or signatures on occasion or on a regular basis to further secure against monitoring, eavesdropping or compromise of the agent communication system.
- agent bus encryption using shared key for all agents provided and updated by the secure server
- agent bus encryption using point to point keys in which the secure server informs the bus and agents of keys and updates as appropriate
- agent level encryption using agent to agent shared keys in which the secure server informs agents of the key and updates the key as appropriate
- agent level encryption using agent to agent point to point key in which the secure server informs agent of the point to point keys that are required and updates the keys as appropriate
- agent level access authorization which only allows access to the agents that are on the secure authorization list and in which the list is provided by the secure server and signatures are provided by the secure server
- UI messages are only analyzed and passed, in which the UI cannot have access to configuration information and cannot issue challenges
- agent level heartbeat encryption which can be point to point or shared key for that agent
- control link level heartbeat encryption TLS (Transport Layer Security) communication protocols
- server level heartbeat encryption which can be point to point or shared key for that agent
- the design of the agent communication bus depends on the nature of the design embodiments for the agents and/or other functions. For example, if the agents are implemented largely or entirely in software, then the agent communication bus can be implemented as an inter-process software communication bus.
- an inter-process software communication bus is a variant of D-bus (e.g., a message bus system for inter-process software communication that, for example, helps applications/agents to talk to one another), or another inter-process communication protocol or system, running a session bus in which all communications over the session bus can be secured, signed, encrypted or otherwise protected.
- the session bus can be further protected by storing all software (e.g., software components, applications and/or agents) in secure memory, storing all software in encrypted form in secure memory, and/or executing all software and communications within a secure execution environment, hardware environment and/or protected memory space.
- software e.g., software components, applications and/or agents
- the agents and other functions are designed with a mixture of software and hardware, or primarily with hardware, then the implementation of the bus design will vary, and the principles and embodiments described herein will enable one of ordinary skill in the art to design the specifics of the agent communication bus 1630 to meet a particular set of product and desired functional requirements.
- an access control integrity agent 1694 collects device information on service policy, service usage or service activity, agent configuration and agent behavior. In some embodiments, the access control integrity agent 1694 also cross checks this information to identify integrity breaches in the service policy implementation and control system. In some embodiments, the access control integrity agent 1694 also initiates action when a service policy violation or a system integrity breach is suspected. In some embodiments, the access control integrity agent 1694 also performs asynchronous or periodic agent checks to verify presence, configuration or proper operation of other agents. In some embodiments, the access control integrity agent 1694 also performs challenge-response sequence verification of other agents.
- the access control integrity agent 1694 obtains service usage or service activity measures from a service monitor agent 1696 and compares one or more first service usage measurement points against one or more second service usage measurement points to verify service policy implementation. For example, as shown in FIG. 21 , if the service usage at measurement point IV is inconsistent with measurement point III, which, for example, can indicate, for example, that an unauthorized or unmonitored usage of the access modem (e.g., modems 2122 , 2123 , 2124 , 2125 or 2141 ) is taking place. As another example, as also shown in FIG.
- upstream traffic usage measurement point II which represents the upstream demand side of policy implementation agent 1690
- upstream traffic measurement point III which represents delivered traffic from the policy implementation agent 1690
- the policy implementation agent 1690 may not be operating properly.
- service measurement point III and IV indicate that firewall agent 1655 is passing traffic to URLs or IP addresses that are in the blocked policy settings
- a verification error condition can be set for the access control policy.
- the policy controller reports traffic usage statistics that are inconsistent with traffic usage policy settings, then a traffic usage policy verification error may have occurred.
- the service usage counter synchronization information received from the service controller 122 , the device service history 1618 and/or the central billing system 1619 is compared to the service usage history reported by the service monitor agent and the two are found to be outside of acceptable tolerance limits for the comparison, then there may be a verification error in the service monitor service usage or service activity accounting.
- device service policy implementations are verified by comparing various service usage measures used at the device against expected service usage or service activity behavior given the policies (e.g., one or more service policy settings, service profile or service profile settings for network based access/services, and/or service plan or service plan for network based access/services). For example, verification is performed based on a measure of total data passed at the device as compared to the service policy for total data usage. For example, verification is performed based on a measure of data passed in a period of time at the device as compared to the service policy for data passed in such a period of time. For example, verification is performed based on a monitoring of communications from the device based on IP addresses as compared to the policy for permissible IP addresses.
- verification is performed based on a measure of total data passed from the device per IP address as compared to the policy for total data usage per IP address.
- Other examples include such actual versus policy comparisons based on other measures at/from/to the device, such as location, downloads, email accessed, URLs, and/or any other data, location, application, time or other criteria or any combination of criteria that can be measured for comparing with various policy settings and/or restrictions.
- the access control integrity agent 1694 monitors agent self-check reports to verify that agents are properly configured. In some embodiments, the access control integrity agent 1694 reports the agent self check reports to the service controller 122 . In some embodiments, the access control integrity agent 1694 performs a role in service usage test transmission, reception and/or monitoring, with the usage test being tailored to test monitoring or control aspects for any subset of service activities. In some embodiments, the access control integrity agent 1694 performs a role in billing test event generation and/or monitoring. In some embodiments, the access control integrity agent 1694 checks and reports the result of service usage monitoring verification tests, service usage billing verification tests and/or transaction billing verification tests.
- the access control integrity agent 1694 receives agent access attempt reports to determine if unauthorized agent access attempts are occurring.
- the access control integrity agent 1694 acts as a central secure communications hub for agent to agent or service controller 122 to agent communication.
- the access control integrity agent 1694 can be used so that no other software or function can access other agents or so that agents cannot access other agents except through the secure point to multipoint communications hub. In some embodiments, this approach further enhances compromise resistance for the agents.
- some or all of the agent communications, including agent to agent or service controller 122 to agent communications, and possibly including unauthorized attempts to communication with agents, are monitored and logged so that a trace log of some or all agent communications can be maintained.
- the agent communication trace log can be summarized and/or compressed for transmission efficiency or regularly reported, such as through the heartbeat function, or the agent communication trace log can be reported only when the service controller 122 requests the agent communication trace log or when there is a verification error event.
- the partitioning of agent functions and server functions is provided herein mainly to aid in disclosing various embodiments but those of ordinary skill in the art will appreciate that other partitioning of agent functions and server functions can be used based on different design choices.
- the central agent communication hub function is performed in some embodiments by the access control integrity agent 1694 , however, in other embodiments that function is performed by the service control device link 1691 .
- the device link can be a single point to multipoint secure communications hub for all agent to agent and service controller 122 to agent communications.
- this approach has certain advantages from a service policy implementation verification or compromise protection robustness perspective, or has certain advantages from a communications protocol efficiency perspective, or simply can be more efficient to implement.
- the agent to agent and agent to service controller 122 communications can be multipoint to multipoint, with each agent having the capability to communicate with other agents or the service controller, this communication can be secure, signed or otherwise encrypted or protected in some embodiments and in the open/clear in others.
- the agents can maintain their own communications or attempted communications log, which can then be reported to the service controller 122 .
- the agents implement restrictions on which device components or agents the agents will conduct communications with so that only agents that need to communicate with one another can do so.
- the service control device link 1691 reviews local billing event history and compares such history to billing event reports to verify that a billing agent 1695 is functioning properly (e.g., has not been tampered with or compromised). In some embodiments, the service control device link 1691 cross-checks service usage or service activity against billing event reports from the billing agent 1695 to verify that billing events are properly billing for service usage or service activity. In some embodiments, the service control device link 1691 cross-checks transaction billing process or records against transaction billing reports to ensure that transaction billing events are being properly reported by the billing agent 1695 . In some embodiments, the service control device link 1691 determines if one or more agents have been compromised, and if so, initiates a dynamic agent download process to replace any such potentially compromised agent.
- the access control integrity agent 1694 verifies that the service usage counter is reporting service usage or service cost to the user within acceptable limits of accuracy when compared to the service usage reports obtained from the service monitor agent 1696 , the service controller 122 , the device service history 1618 and/or the central billing system 1619 . In some embodiments, the access control integrity agent 1694 checks to verify that user privacy filter preferences are being properly implemented. In some embodiments, the access control integrity agent 1694 checks to verify that the user is properly receiving UI warnings regarding service usage or roaming service usage conditions.
- the access control integrity agent 1694 checks to verify that the device is not beginning service usage until it has been authenticated, authorized or granted access to the network. In some embodiments, access control integrity agent 1694 checks with the service controller 122 or the billing system 1619 to verify that the user or device has a valid service standing and should be admitted to access on the network.
- an Activation Tracking Service is provided in which the service monitoring function (e.g., performed by the service monitor agent 1696 and/or some other agent/component or combinations thereof on the device) is used in part to determine which access networks are being connected to and to record and/or report this information.
- the ATS is only enabled if the device user approves reporting of access networks connected to by the user device.
- the ATS is protected from tampering.
- the ATS can be hardened, that is, to be more tamper resistant, using a variety of techniques, including any of the following: the ATS can be located (e.g., stored) in secure memory and/or secure hardware; the ATS can be implemented in the system BIOS, the access modem and/or another hard to access portion of the device; a second device agent can confirm the presence of the ATS with a report to a network based server; the second agent or the network server can initiate a reinstall of the ATS if it is missing or is found to be operating improperly; and/or the ATS can be placed in a secure area of the OS so that it cannot be removed or if removed must be replaced for proper device operation to resume.
- a variety of other tamper resistance techniques can also be used to protect the ATS from tampering as similarly described herein with respect to other device based functions/software components/agents.
- the access control integrity agent 1694 verifies that ATS software or hardware is present, properly configured or operating properly. In some embodiments, the access control integrity agent 1694 reviews network connection or activity history and compares such to ATS reports to verify activation tracking service reports are occurring properly. In some embodiments, the access control integrity agent 1694 replaces ATS software if it has been removed. In some embodiments, the access control integrity agent 1694 monitors access or compromise of ATS software to determine if it may have been compromised. In some embodiments, the access control integrity agent 1694 reports status of ATS functions.
- the access control integrity agent 1694 scans the local agent execution environment to determine if there are unauthorized accesses to service processor functions, settings or code. In some embodiments, the access control integrity agent 1694 monitors software loading activity, protected memory access or communication with service processor 115 agents to detect unauthorized changes to service processor software or configuration. For example, the access control integrity agent 1694 can have a local database of potentially malicious elements and compare entries in the database against the elements detected locally. As another example, the access control integrity agent 1694 can communicate a list of some or all of the elements detected locally to the service controller 122 to augment or take the place of the database comparison function that may be performed locally.
- the access control integrity agent 1694 detects new software downloads, installs or invocations and immediately issues an error flag report when potentially malicious software is downloaded, installed or invoked. In some embodiments, the access control integrity agent 1694 scans the local software loading and invocation activity along with a log of other software runtime events and regularly reports this trace so that when an error or compromise event occurs the trace preceding the event can be analyzed to determine the offending software or activity trace that took place to cause the compromise or error. Once the software or activity that caused the compromise is known, it can be entered into a refreshed version of the database that the device and other devices use to detect potentially malicious pre-cursor conditions.
- pre-cursor events include software invocations, software downloads, attempts to uninstall certain agent and/or application software/components or OS components, a sequence of memory I/O events, a sequence of software access events, a sequence of network address or URL communications or downloads or a sequence of access modem I/O activity.
- the agent performs or (securely) communicates with other software/hardware device/network components that perform other well known signature, behavior blocking and/or intrusion detection identification/detection and/or blocking techniques based on the presence of potentially unwanted and/or potentially or known malicious software and/or intrusion attempts by unauthorized software and/or unauthorized users, using, for example, real-time, on access, periodic, and/or on demand scanning.
- the access control integrity agent 1694 detects or blocks potentially compromising behavior of other software programs/users attempting unauthorized behavior in the service processor 115 operating environment. In some embodiments, the access control integrity agent 1694 detects software that is being loaded that has the same or similar name, identification, memory location or function as one or more of the service processor 115 agents. In some embodiments, the access control integrity agent 1694 blocks operation or loading of such software. In some embodiments, the access control integrity agent 1694 detects or blocks unauthorized access of service processor 115 protected memory. In some embodiments, the access control integrity agent 1694 verifies configuration and operation of secure service downloader 1663 .
- the access control integrity agent 1694 monitors network and I/O activity to detect potentially compromising events, such as a program that is downloaded from known detrimental or potentially suspect IP addresses or URLs or a program that accesses certain IP addresses or URLs.
- the access control integrity agent 1694 scans of the service processor operating environment are recorded and kept for a period of time, and if a service policy verification error occurs, then the scans immediately prior to the error are analyzed or reported to the service controller 122 for analysis. In some embodiments, such scans are regularly reported to the service controller 122 without the presence of service policy verification error conditions.
- the access control integrity agent 1694 requests a dynamic agent download of certain critical service processor functions, including in some cases the access control integrity agent 1694 on a periodic basis, or on a periodic basis when network access activity is not required or minimal.
- the access control integrity agent 1694 determines if a threshold has been surpassed for a max usage trigger for ambient and/or other services that should not be using significant amounts of data (e.g., based on the type of device and/or service profile settings).
- the access control integrity agent 1694 determines if verification errors exist in one or more of the verification process embodiments and, in some embodiments, reports errors immediately or in the next agent heartbeat to the service controller 122 . In some embodiments, any number of results from the above checks, monitoring activities, reports or tests are reported to the service controller 122 .
- a policy control agent 1692 receives policy instructions from the service controller 122 and/or the user via the billing agent 1695 and adapts device service policy settings (e.g., instantaneous device service policy settings) in one or more of the following agents/components: a policy implementation agent 1690 , the modem firewall 1655 and/or an application interface agent 1693 .
- the modem firewall 1655 is in communication with a modem driver 1640 , which is in communication with the agent communication bus 1630 and access network 1610 .
- a central billing server 1619 , an access network AAA server 1621 and device server history 1618 are also provided.
- the Internet 120 is accessible via the access network 1610 and firewall 124 , from which device 100 can then access various Internet services 1615 .
- the policy control agent 1692 adapts low level service policy rules/settings to perform one or more of the following objectives: achieve higher level service usage or cost objectives, reduce network control channel capacity drain, reduce network control plane server processing bandwidth, and/or provide a higher level of user privacy or network neutrality while satisfying service usage or service activity objectives.
- the policy control agent 1692 performs a policy control function to adapt instantaneous service policies to achieve a service usage objective.
- the policy control agent 1692 receives service usage information from the service monitor agent 1696 to evaluate service usage history as compared to service usage goals.
- the policy control agent 1692 uses service monitor 1696 service usage or service activity history and various possible algorithm embodiments to create an estimate of the future projected service usage.
- the policy control agent 1692 uses a future projection of service usage to determine what service usage or service activity controls need to be changed to maintain service usage goals.
- the policy control agent 1692 uses service usage history to perform a service usage or service activity analysis to determine the distribution of service usage across service usage elements within categories, such as usage by application, usage by URL, usage by address, usage by content type, usage by time of day, usage by access network, usage by location, and/or any other categories for classifying service usage.
- the policy control agent 1692 uses the service usage distribution analysis to determine which service usage elements or service activities are creating the largest service usage (e.g., if e-mail, social networking, or multimedia/online video application categories are creating the largest service usage).
- the policy control agent 1692 is instructed, for example, by the user, through billing agent 1695 to perform a service control algorithm, such as traffic shaping or download management, to manage service usage or service activities to assist the user in controlling service costs.
- a service control algorithm such as traffic shaping or download management
- the traffic shaping algorithm can simply reduce traffic speed for all applications and traffic types successively until the service usage projections are within service usage limits for the present service billing period.
- the traffic shaping algorithm can identify the highest traffic usage applications and/or websites and successively reduce traffic speed just for the highest usage applications and/or websites until the service usage projections are within service usage limits for the present service billing period.
- These examples thereby reduce network traffic for the user in accordance with the user's service usage objectives while maintaining overall satisfactory service usage experience for the user in a manner that satisfies various net neutrality requirements (e.g., the traffic throttling of certain applications/websites based on user input in which categories based on service usage history are selected by the user, for example, a certain application may be using 90% of the aggregate traffic usage).
- adaptive throttling algorithms can be used to throttle application traffic that the user requests throttling, such as recursively throttling of the specified application traffic (e.g., to denigrate the traffic usage associated with that application and thereby reduce overall service data usage).
- the policy control agent 1692 adjusts service policy based on time of day. In some embodiments, the policy control agent 1692 obtains a measure of network availability and adjusts traffic shaping policy settings based on available network capacity. In some embodiments, the policy control agent 1692 automatically and dynamically adjusts service policy based on one or more other service policy settings, the service profile and/or the service plan associated with the device and/or user of the device.
- various lower level service policy implementation embodiments are combined with a higher level set of service policy supervision functions to provide device assisted verifiable network access control, authentication and authorization services.
- ambient access generally refers to an initial service access in which such service access is in some manner limited, such as where service options are significantly limited (e.g., low bandwidth network browsing and/or access to a specific transactional service), limited bandwidth, limited duration access before which a service plan must be purchased to maintain service or have service suspended/disabled or throttled or otherwise limited/reduced/downgraded, and/or any other time based, quality based, scope of service limited initial access for the network enabled device.
- service options are significantly limited (e.g., low bandwidth network browsing and/or access to a specific transactional service), limited bandwidth, limited duration access before which a service plan must be purchased to maintain service or have service suspended/disabled or throttled or otherwise limited/reduced/downgraded, and/or any other time based, quality based, scope of service limited initial access for the network enabled device.
- ambient activation is provided by setting access control to a fixed destination (e.g., providing access to a portal, such as a web page (e.g., for a hotspot) or WAP (Wireless Application Protocol) page, that provides the user with service plan options for obtaining a service plan for the user desired access, such as the service plan options for data usage, service types, time period for access (e.g., a day pass, a week pass or some other duration), and costs of service plan(s)).
- a portal such as a web page (e.g., for a hotspot) or WAP (Wireless Application Protocol) page
- service plan options for obtaining a service plan for the user desired access
- service plan options for data usage e.g., service types, time period for access (e.g., a day pass, a week pass or some other duration)
- time period for access e.g., a day pass, a week pass or some other duration
- costs of service plan(s) e
- service data usage of the ambient activated device is verified using IPDRs (e.g., using the device ID/device number for the device 101 to determine if the device has been used in a manner that is out of plan for the service plan associated with the device 101 , such as based on the amount of data usage exceeding the service plan's service data usage limits, out of plan/unauthorized access to certain websites, and/or out of plan/unauthorized transactions).
- service data usage of the ambient activated device is verified by setting a maximum data rate in the policy control agent 1692 and if/when it is determined that the device is exceeding a specified data rate/data usage, then the service data usage is throttled accordingly.
- various other verification approaches are used for ambient activation purposes.
- the policy control agent 1692 (and/or another agent/component of the service processor 115 and/or service controller 122 ) performs a service control algorithm to assist in managing overall network capacity or application QoS (Quality of Service). In some embodiments, the policy control agent 1692 (and/or another agent/component of the service processor 115 ) performs an access network selection algorithm to determine which access network to connect to based on connection options and determined strengths of available wireless networks, network preference or security settings, service usage cost based network preferences, and/or any other criteria.
- service usage or service activities can be measured by various agents at various different measurement points, which provides for a more robust verification and integrity of device based services communication. For example, it is much less likely and more difficult to compromise and/or spoof multiple agents.
- various verification and integrity checks are performed, including, for example, network based service usage measurement (e.g., using IPDRs); heartbeat monitoring; agent based heartbeat (e.g., challenge/response queries); agent operating environment protection; monitoring agent communications; agent cross-checks; comparing device based and network based measures (e.g., service usage measures); dynamic software/agent download; and/or any combination of these and various other verification/integrity check techniques described herein and/or apparent from the various embodiments described herein.
- network based service usage measurement e.g., using IPDRs
- agent based heartbeat e.g., challenge/response queries
- agent operating environment protection e.g., agent operating environment protection
- monitoring agent communications e.g., agent cross-checks
- comparing device based and network based measures e.g., service usage measures
- dynamic software/agent download e.g., dynamic software/agent download
- the device 100 is capable of connecting to more than one network and device service policies are potentially changed based on which network the device is connected to at the time.
- the network control plane servers detect a network connection change and initiate the service policy implementation established for the second network.
- the device based adaptive policy control agent as described herein (e.g., policy control agent 1692 ), detects network connection changes and implements the service policies established for the second network.
- the network when more than one access network is available, the network is chosen based on which network is most preferred according to a network preference list or according to which network that optimizes a network cost function.
- the network preference list can be pre-established by the service provide and/or the user and/or later modified/adjusted by either the service provider and/or the user.
- the cost function can be based on determining a minimum service cost, maximum network performance, whether or not the user or device has access to the network, maximizing service provider connection benefit, reducing connections to alternative paid service providers, and/or any other cost related criteria for network selection purposes.
- the device 100 detects when one or more preferred networks are not available, implements a network selection function or intercepts other network selection functions, and offers a connection to the available service network that is highest on a preference list.
- the preference list can be set by the service provider, the user and/or the service subscriber.
- a notification is provided to the device/user when the device is not connected to a network (e.g., indicating in a pop-up/bubble or other UI based display a notification, such as “You are not connected to the network. Click here to learn more, get free trial, use a session, sign-up for service”).
- the notification content can be determined based on usage service patterns, locally stored and/or programmable logic on the device and/or a server (e.g., device reports that user is not connected and WWAN is available). Decisions on what bubble to present when may be in pre-stored logic on device.
- service policies are automatically adapted based on the network to which device 100 is connected.
- the device can be a cellular communication based device connected to a macrocell, a microcell, a picocell, or a femtocell (e.g., femto cells generally provide a low power, small area cellular network used, for example, in homes or offices, which, for example, can be used as an alternative to Wi-Fi access).
- service monitoring agent 1696 and/or billing agent 1695 modify service usage counting and/or billing based on whether the device is connected to a macrocell, microcell, picocell or femtocell.
- the device recognizes which type of network it is currently connecting to (e.g., looking up in a local or network table for the current base station connected to, and/or the information is broadcast to the device upon the connection with the base station), that is, whether it is a macrocell, microcell, picocell or femtocell. In other embodiments, the device does not recognize which type of network it is currently connected to, but reports its current base station, and the network uses a network lookup function to determine which type of network it is connected to.
- the device adjusts the billing based on the type of network it is connected to, or in other embodiments, the device calculates an offset to such billing based on the type of network it is connected to, and/or in other embodiments, the device records such service usage associated with the type of network it is connected to and the network billing can adjust the billing accordingly. For example, the billing can be lower for service data usage over a femtocell versus a macrocell.
- service policies are adjusted based on the type of network that the device is connected, such as billing, user notification, data usage/bandwidth, throttling, time of day, who owns the cellular network connection (e.g., user's home femtocell, or user's work femtocell, or a commercial business's femtocell like a coffee shop or any other common area like an airport) and/or any other service policy can be different for a femtocell connection (or for any other type of connection, such as a macrocell, microcell, or picocell).
- a femtocell connection or for any other type of connection, such as a macrocell, microcell, or picocell.
- the local service usage counter is adjusted based on the type of network (and/or based on the time of day of such service activity) that the device is connected, such as billing, user notification, data usage/bandwidth, and/or any other service policy can be different for a femtocell connection (or for any other type of connection, such as a macrocell, microcell, or picocell).
- the service policies and/or billing policies are adjusted based on network congestion.
- the policy control agent 1692 can simply pass instantaneous service policy settings directly to the agents responsible for implementing instantaneous service policies.
- a policy implementation agent 1690 implements traffic shaping and QoS policy rules for the device 100 .
- the policy implementation agent 1690 provides a firewall function.
- the policy implementation agent 1690 performs traffic inspection and characterization.
- packet inspection is aided by literal or virtual application layer tagging while in other embodiments packet inspection is performed entirely in/by the policy implementation agent 1690 .
- the policy implementation agent 1690 accepts service policy implementation settings from the policy control agent 1692 or directly from the service controller 122 . More detail on specific embodiments for the policy implementation agent 1690 is provided below with respect to the figures associated with communication stack and communication protocol flow.
- the burst size, buffer delay, acknowledgement delay and drop rate used in upstream and downstream traffic shaping are optimized with the goal of reducing access network traffic overhead, and excess capacity usage that can result from mismatches in traffic transmission parameters with the access network MAC and PHY or from excess network level packet delivery protocol re-transmissions.
- the application interface agent 1693 is used to literally tag or virtually tag application layer traffic so that the policy implementation agent(s) 1690 has the necessary information to implement selected traffic shaping solutions. As shown in FIG. 16 , the application interface agent 1693 is in communication with various applications, including a TCP application 1604 , an IP application 1605 , and a voice application 1602 .
- downstream literal or virtual application tagging are delayed until a traffic flow passes through the service policy implementation functions and to the application interface function where the service flow is then identified and associated with the underlying traffic and application parameters, and the literal or virtual tag is then communicated to the first policy implementation function or service monitoring function in the downstream traffic processing stack.
- the traffic flow prior to being associated with a literal or virtual tag, the traffic flow is allowed to pass with no traffic shaping, and once the traffic flow is identified and tagged, the appropriate traffic shaping is applied.
- a set of traffic shaping policy parameters are applied to the unidentified traffic flow before the flow is identified, and then the traffic shaping policy for the flow is updated when the flow is tagged.
- the traffic flow can be blocked at the application interface agent even before the tag is passed to the policy implementation functions if it is found to be associated with traffic parameters that are blocked by policy once packet processing, framing and encryption are removed.
- a service monitor agent 1696 records and reports device service usage or service activities of device 100 .
- service usage history is verified by a number of techniques including verifying against network based service usage history (e.g., device service history 1618 ) and the various service policy implementation techniques as described herein.
- the service monitor agent 1696 includes the capability to filter service usage history reporting with the decision on which aspects of service history to report being determined by policies including possibly privacy policies defined by the device user or control plane servers in the network.
- the service monitor agent 1696 monitors and possibly records or reports Customer Resource Management (CRM) information such as websites visited, time spent per website, interest indications based on website viewing, advertisements served to the device, advertisements opened by the user, location of the user, searches conducted by the user, application usage profile, device user interface usage history, electronic commerce transactions, music or video files played, applications on device, and/or when the user is actively working or playing or inactive.
- CRM Customer Resource Management
- the user is provided with options on how much of the information to share and the user's response to the options are recorded and used to determine the filtering policy for how much of the CRM data to report (e.g., CRM filter level options selected by the user via the device UI and/or via various service plan or service profile or service policy options) and how much to suppress or to not even monitor/record/store in the first place.
- options on how much of the information to share and the user's response to the options are recorded and used to determine the filtering policy for how much of the CRM data to report (e.g., CRM filter level options selected by the user via the device UI and/or via various service plan or service profile or service policy options) and how much to suppress or to not even monitor/record/store in the first place.
- the user is provided with options on how much of the information to share and the user's response to the options are recorded and used to determine the filtering policy for how much of the GPS/location tracking related data to report (e.g., GPS/location tracking filter level options) and how much to suppress or to not even monitor/record/store in the first place.
- the service processor 115 allows the user to provide feedback on the user's preferences, such as for privacy/CRM data to report.
- the user can also specify their preference(s) for notification (e.g., related to service usage/cost, traffic reporting and other service usage/monitored information) and/or service controls.
- the service monitor agent 1696 observes and possibly records or reports service usage categorized by network possibly including roaming networks, paid service networks or free service networks. In some embodiments, the service monitor agent 1696 observes and possibly records or reports service usage categorized by sub-accounts for various types of traffic or various types of network.
- service monitor reports can be provided to the service controller 122 .
- Service is monitored through various embodiments that can involve service usage logging or traffic inspection and usage logging at the application level, various levels in the networking communication stack or the access modem. Some embodiments involve multiple levels of service or traffic measurement at various levels in the communications stack as described further below.
- service or traffic monitoring includes monitoring one or more of the following: traffic associated with one or more users; traffic downstream and/or upstream data rate; total traffic received and/or transmitted over a period of time; traffic transmitted and/or received by IP addresses, domain names, URLs or other network address identifiers; traffic transmitted and/or received by email downloads or uploads; traffic transmitted and/or received by an application; traffic transmitted and/or received by network file transfers; traffic transmitted and/or received by file download or upload content types; traffic transmitted and/or received by mobile commerce transactions; traffic transmitted and/or received by one or more time periods; traffic transmitted and/or received by differing levels of network activity and network capacity availability; traffic transmitted and/or received by one or more delivered levels of quality of service; traffic transmitted and/or received by software downloads; traffic transmitted and/or received by application downloads; traffic transmitted and/or received by one or more activities associated with the service control plane link or other network related functions, or traffic that may not directly result in service usage or service activity that the user values or desires; traffic transmitted and/or received to
- the service monitor agent 1696 implements traffic inspection points between the applications and the networking stack application interface, such as the sockets API.
- the application interface agent 1693 performs traffic inspection and reports the results to the service monitor agent 1696 .
- Traffic inspection can be accomplished in several ways, including, for example, implementing a T-buffer at each socket connection and feeding the side traffic into a traffic flow analyzer, which in combination with a mapping of application to socket provides much of the information listed above. In cases in which it is necessary to obtain traffic information from the application itself, some embodiments call for the application to be adapted to provide the information to either the application interface agent 1693 or the service monitor agent 1696 .
- the application interface agent 1693 or the service monitor agent 1696 can monitor and decode advertisements downloaded via HTTP, but if the browser and HTTP server employ security above the sockets protocol stack layer then the application interface agent can communicate with the browser via a java applet or some other inter-process communication method.
- the service monitor agent 1696 , the billing agent 1695 and/or the policy control agent 1692 can monitor and/or control (e.g., allow, block and/or replace) advertisement traffic flow into the device.
- the monitoring and control of advertisement traffic flow into the device is also used for bill by account purposes (e.g., charges, such as service charges, billed to the advertiser, sponsor, and/or service or transactional service provider).
- some or all of the service usage monitoring occurs below the application interface for the networking stack. In this case, some portion of the information listed above may not always be available due to encryption applied at the higher layers and/or the computational costs associated with performing deep packet inspection on mobile devices.
- the service monitor agent 1696 is also monitors the operating software install or loading systems, and/or otherwise monitors software installs or loads and/or software uninstalls/deinstallations.
- Some of the information above may be considered by some users, advocacy groups or agencies as customer sensitive personal information. Simply sending the above information to the network for unspecified purposes may not, therefore, be acceptable for some service providers. However, if the user provides specific approval (e.g., informed consent) for the device, network or service provider to use some or all of the information that may be sensitive for specified purposes, then the user can control the level of information that is used and the purpose the information is used for. Accordingly, various embodiments described herein provide the user with control of what information is used and the purposes it is used for thereby allowing the user adequate control of any such sensitive information. In some embodiments, information that is thought to perhaps be sensitive and is reported to the network must first receive user approval for the reporting.
- Some basic information is generally not considered sensitive and is necessary for certain basic service provider needs. For example, total data transmitted and/or received, traffic downstream and/or upstream speed, overall traffic usage by time of day are generally not considered private from the service provider's perspective and are necessary in many basic service policy implementations. As additional examples, perhaps other service usage history, such as total traffic email downloads and uploads but not the type of files or any specifics about the email traffic, the total web browsing traffic but nothing specific about the sites visited or content viewed, total file transfer traffic but not the type of files transferred or the addresses involved in the transfer, and other examples may not be viewed as private and, in some embodiments, provide valuable information for the service provider to manage services.
- information such as websites visited, content viewed, mobile commerce transactions completed, advertisements visited, GPS location history and other service usage history the service monitor is capable of recording may be sensitive or private for some users and would thereby benefit from the various embodiments that provide enhanced user control of the reporting of such potentially sensitive or private data. It should also be appreciated that there is an inherent advantage to implementing traffic monitoring, traffic, service monitoring or service control on a device, because it is not necessary to report sensitive information to the network to accomplish many of these service policy implementation objectives.
- the service monitor agent 1696 assists in virtual application tagging of traffic flows through the networking stack policy implementation by tracking the virtually tagged packets through the stack processing and communicating the flow tags to the service policy implementation agent(s) 1690 .
- the service monitor agent 1696 maintains a history and provides reports or summary reports of which networks in addition to the networks controlled by the service controller 122 to which the device has connected.
- this network activity summary includes a summary of the networks accessed, activity versus time per connection, and/or traffic versus time per connection.
- the traffic reports that go to the network are first filtered according to rules defined by user preference selection at the time of service activation (e.g., service plan/service plan option selection), time of first device use, at a time the user selected the option on the service UI or at a time the user chose to change the option on the service UI or some other time/mechanism allowing for user preference selection.
- time of service activation e.g., service plan/service plan option selection
- time of first device use e.g., time the user selected the option on the service UI or at a time the user chose to change the option on the service UI or some other time/mechanism allowing for user preference selection.
- the service monitor agent 1696 monitors application usage (e.g., which application the user executes on the device 101 , such as e-mail applications, web browsing applications and/or media content streaming applications).
- application usage e.g., which application the user executes on the device 101 , such as e-mail applications, web browsing applications and/or media content streaming applications.
- multimedia file usage e.g., based on multimedia file type and/or based on specific multimedia files, such as specific movies and/or songs.
- the service monitor agent 1696 monitors the device user interface, application, and content discovery history (e.g., monitoring which applications/content the user accesses from the device, including monitoring the pattern by which the user accesses such applications/content, such as how the user navigates the user interface on the device to access such applications/content and maintaining such patterns and history, such as which icons the user access on a home page, secondary or other portion/mechanism on the device for accessing various applications/content).
- the service monitor agent 1696 monitors advertisements provided to the user on the device 101 .
- the service monitor agent 1696 monitors advertisements viewed (e.g., accessed, such as by clicking on a web advertisement) by the user on the device 101 .
- the service monitor agent 1696 monitors GPS/location information for the device 101 .
- the service monitor agent 1696 can monitor a wide variety of activities performed by the device/user of the device and/or based on other information related to the device 101 such as GPS/location information.
- the user of the device 101 can also specify which activities that the user authorizes for such monitoring (e.g., the user may prefer to not allow for such GPS/location monitoring).
- the application interface agent 1693 provides an interface for device application programs. In some embodiments, the application interface agent 1693 identifies application level traffic, reports virtual service identification tags or appends literal service identification tags to assist service policy implementation, such as access control, traffic shaping QoS control, service type dependent billing or other service control or implementation functions. In some embodiments, the application interface agent 1693 assists with application layer service usage monitoring by, for example, passively inspecting and logging traffic or service characteristics at a point in the software stack between the applications and the standard networking stack application interface, such as the sockets API.
- the application interface agent 1693 intercepts traffic between the applications and the standard network stack interface API in order to more deeply inspect the traffic, modify the traffic or shape the traffic (e.g., thereby not requiring any modification of the device networking/communication stack of the device OS).
- the application interface agent 1693 implements certain aspects of service policies, such as application level access control, application associated billing, application layer service monitoring or reporting, application layer based traffic shaping, service type dependent billing, or other service control or implementation functions.
- application layer based traffic monitoring and shaping can be performed as described below.
- the traffic from each application can be divided into one or more traffic flows that each flow through a traffic queue, with each queue being associated with one or more additional classifications for that application (e.g., the application can be a browser that is associated with multiple queues representing different destinations or groups of destinations it is connected to, with each destination or group of destinations having potentially different access control or traffic control policies, or the application can be associated with different content types or groups of content types with each content type having different queues, the application might be an email program with email text traffic going to one queue and downloads going to another with different policies for each).
- queues are formed for all applications or groups of applications that are associated with one or more traffic parameters such as destination, content type, time of day or groups of applications can be similarly assigned to different queues.
- the functions performed by the application layer queues can be similar to the functions described for the policy implementation agent, such as pass, block, buffer, delay, burst in order to control the traffic or network access associated with the queue.
- the drop function can also be implemented, such as for application layer protocols that include reliable transmission methods, but if the application layer protocol does not involve reliable retransmission of lost information this can result in lost data or unreliable communication which may be acceptable in some cases.
- the manner in which the queues are controlled can be constructed to result in a similar approach for controlling services or implementing service activity control similar to the other embodiments described herein, including, for example, the policy control agent 1692 implementing an higher layer of service control to achieve a higher level objective as discussed herein.
- the application interface agent 1693 interacts with application programs to arrange application settings to aid in implementing application level service policy implementation or billing, such as email file transfer options, peer to peer networking file transfer options, media content resolution or compression settings and/or inserting or modifying browser headers.
- the application interface agent 1693 intercepts certain application traffic to modify traffic application layer parameters, such as email file transfer options or browser headers.
- the application interface agent 1693 transmits or receives a service usage test element to aid in verifying service policy implementation, service monitoring or service billing.
- the application interface agent 1693 performs a transaction billing intercept function to aid the billing agent 1695 in transaction billing.
- the application interface agent 1693 transmits or receives a billing test element to aid in verifying transaction billing or service billing.
- a modem firewall 1655 blocks or passes traffic based on service policies and traffic attributes. In some embodiments, the modem firewall 1655 assists in virtual or literal upstream traffic flow tagging. Although not shown in FIG. 16 , in some embodiments, the modem firewall 1655 is located on either side of the modem bus and in some embodiments it is advantageous to locate it on the modem itself.
- the billing agent 1695 detects and reports service billing events. In some embodiments, the billing agent 1695 plays a key role in transaction billing. In some embodiments, the billing agent 1695 performs one or more of the following functions: provides the user with service plan options, accepts service plan selections, provides options on service usage notification policies, accepts user preference specifications on service usage notification policies, provides notification on service usage levels, provides alerts when service usage threatens to go over plan limits or to generate excess cost, provides options on service usage control policy, accepts choices on service usage control policy, informs policy control agent 1692 of user preference on service usage control policy, provides billing transaction options and/or accepts billing transaction choices. In some embodiments, the billing agent 1695 interacts with transaction servers (e.g., open content transaction partner sites 134 ) to conduct ecommerce transactions with central billing 1619 .
- transaction servers e.g., open content transaction partner sites 134
- service processor 115 includes one or more service usage or service activity counters.
- the service monitor agent 1696 , billing agent 1695 or a combination of these agents and/or other agents/components of service processor 115 can include such a local service usage counter(s) for the device 101 .
- a service usage counter monitors service usage including data usage to/from the device 101 with the access network 1610 .
- the service usage counter periodically, in response to a user request, in response to a service processor 115 agent's request (e.g., the billing agent 1695 , the policy control agent 1692 , or another agent of service processor 115 ), in response to the service controller 122 , and/or in response to the central billing 1619 (e.g., for billing purposes and/or for storing in the device service history 1618 ), provides a service usage report, including monitored service usage for the device 101 .
- the service usage counter periodically, or in response to a request, synchronizes the service usage counter on the device 101 with a network (and/or billing) service usage counter, such as that maintained potentially at central billing 1619 .
- service processor 115 utilizes the service usage counter to provide a service usage projection. In some embodiments, service processor 115 utilizes the service usage counter to provide a service usage cost estimate. In some embodiments, service usage projections from policy control agent 1692 are used to estimate the projected future service usage if user service usage behavior remains consistent. In some embodiments, service processor 115 utilizes the service usage counter to provide a cost of service usage, and the service processor 115 then periodically, or in response to a request, synchronizes the cost of service usage with, for example, the central billing 1619 .
- the service processor 115 utilizes the service usage counter to determine whether the user is exceeding and/or is projected to exceed their current service plan for data usage, and then various actions can be performed as similarly described herein to allow the user to modify their service plan and/or modify (e.g., throttle) their network data usage.
- the service usage counter can support providing to the user the following service usage related data/reports: service usage, known usage and estimated usage, projected usage, present costs, projected costs, cost to roam, cost to roam options, and/or projected roaming costs.
- including a local service data usage counter on the device 101 allows the service processor 115 to more accurately monitor service data usage, because, for example, network (and/or billing) service usage counters may not accurately also include, for example, control plane data traffic sent to/from the device 101 in their monitored service data usage count.
- verifiable device based service billing solutions are provided.
- various device based service billing solutions can include a wide range of verification techniques to ensure that the device is properly reporting service billing events (e.g., to verify/ensure that the service billing is not malfunctioning and/or has not been tampered with/compromised such that it is not accurately or timely providing service billing information).
- service billing generally refers the billing for one or more services for a device, such as device 101 (e.g., email service billing for data usage associated with received/sent email related data over the access network 1610 , web browsing service billing for data usage associated with received/sent web browsing related data over the access network 1610 and/or any other network based service, and/or any transactional based services, such as for multimedia content purchases or other transactions).
- a device such as device 101
- email service billing for data usage associated with received/sent email related data over the access network 1610
- web browsing service billing for data usage associated with received/sent web browsing related data over the access network 1610 and/or any other network based service
- transactional based services such as for multimedia content purchases or other transactions.
- verifiable device based service billing is provided by sending dummy(/test) billing events, such as having an access control integrity server 1654 of the service controller 122 instruct the access control integrity agent 1694 to send a dummy(/test) billing event to the billing agent 1695 . If the billing agent does not then send the expected report, which should reflect the dummy(/test) (or fails to timely send any report), then the system can verify whether the billing process is working properly.
- a dummy(/test) transaction can be used to verify transaction based billing through a variety of approaches (e.g., the access control integrity agent 1694 can similarly send a dummy(/test) transactional billing event to the billing agent 1695 as a test to determine whether the billing agent 1695 then provides the expected report reflecting that dummy(/test) transaction).
- the test billing events can be trapped by a device assisted billing mediation server and removed from the user account billing.
- verifiable device based service billing is provided by sending one or more data bursts to the device to confirm that data was received and to confirm that the service monitor agent 1696 properly logged the data burst(s) in the local service usage or service activity counter.
- data bursts can be used to verify data throttling (e.g., if the device has exceeded service data usage limits and/or is approaching such limits such that service data usage should be throttled, then sending data bursts can be used to verify whether the expected throttling is properly being performed on the device).
- verifiable device based service billing is provided by submitting requests to connect to an unauthorized service/website to verify if that unauthorized service usage is properly blocked.
- verifiable device based service billing is provided by submitting requests to perform an unauthorized transaction to verify if that unauthorized transaction is properly blocked.
- verifiable device based service billing is provided by verifying device service activities relative to IPDRs for the device.
- the IPDRs for the device are periodically and/or upon request sent to the device, as described herein.
- IPDRs for the device can be compared to the device's local service data usage counter and/or to the service plan for the device to determine if the overall service data usage limit has been exceeded, whether out of plan/unauthorized/unrecorded websites/other services have been performed by the device, whether service plan/profile bandwidth limits have been exceeded, whether out of plan/unauthorized/unrecorded transactions have been performed (e.g., verifying IPDR transaction logs, assuming such are included in the IPDRs, with the local transaction logs of the device to determine, for example, whether the local device records indicate that fewer than the network recorded number of content downloads, such as downloaded songs, were purchased), and/or whether any other activities verifiable based on a comparison of IPDRs indicate that the device has been used in any manner that is out of or exceeds the service plan/profile for the device.
- verifying IPDR transaction logs assuming such are included in the IPDRs, with the local transaction logs of the device to determine, for example, whether the local device records indicate that fewer than the
- device based service billing includes recording billing option response history. For example, this approach can be particularly important for service plan overage conditions (e.g., when the use of the device is exceeding the service plan associated with the device in some manner, such as service data usage, bandwidth, service or transaction access and/or in some other manner).
- service plan overage conditions e.g., when the use of the device is exceeding the service plan associated with the device in some manner, such as service data usage, bandwidth, service or transaction access and/or in some other manner.
- the user in a service plan overage condition, the user is requested to confirm that user has acknowledged notification of service plan overage, such as via the user interface 1697 .
- such service plan overage acknowledgements require that the user enter a unique identification to validate authorization by the user identity associated with the device (e.g., another type of verification mechanism, in the event a device is stolen or being used by someone other than the authorized user of the device, then that unauthorized user would not be able to confirm the service plan overage acknowledgement, and appropriate actions can then be taken, such as throttling, quarantining or (temporarily) suspending service/network access).
- a unique identification to validate authorization by the user identity associated with the device (e.g., another type of verification mechanism, in the event a device is stolen or being used by someone other than the authorized user of the device, then that unauthorized user would not be able to confirm the service plan overage acknowledgement, and appropriate actions can then be taken, such as throttling, quarantining or (temporarily) suspending service/network access).
- the billing system determines billing for such service usage overage costs.
- This overage billing can be initiated by the device 100 (e.g., service processor 115 ), the service controller 122 , the billing system 123 , the AAA 121 , or some other network function.
- the device is compromised/hacked (e.g., by a user of the device), and the device is used in a manner that results in a service usage overage, one or more of the following actions is taken: the user is notified, the user is required to acknowledge the notification, the device traffic is sent to SPAN (or similar traffic sampling and analysis function), and/or the device is flagged for further analysis.
- SPAN traffic sampling and analysis function
- device based service billing includes an option to bill by account, such as to bill different service activities and/or transactions to a specified account (e.g., other than the user's account associated with the general service plan for the device).
- bill by account can provide for billing according to application, content type, website, transaction, network chatter (e.g., heartbeat communications and/or other network traffic that is used by, for example, the central/service provider to generally maintain network access for the device), and/or transaction partner sponsored activities and then report such bill by account information for billing mediation/reconciliation.
- a bill by account report can be sent by billing agent 1695 from the device to central billing 1619 (e.g., as a billing event); or alternatively, sent to an intermediate server/aggregator, which can then reformat and send the reformatted report to central billing 1619 (e.g., providing the billing report in a format required by central billing 1619 ); or alternatively, sent to a mediation server, which can re-compute the billing based on the bill by account report (e.g., offset the bill based on network chatter, transaction based billing, transaction partner sponsored activities, content providers, website providers and/or advertising providers) and then send the recomputed (and potentially reformatted) report to central billing 1619 .
- a mediation server which can re-compute the billing based on the bill by account report (e.g., offset the bill based on network chatter, transaction based billing, transaction partner sponsored activities, content providers, website providers and/or advertising providers) and then send the recomputed (and potentially reformatted) report to central
- one or more of the mediation/reconciliation functions for device assisted billing, device generated billing events, device generated bill by account events and device generated open transaction billing events can be implemented in the service controller 122 (e.g., the billing event server 1662 ) or in another function located in the billing system 123 or elsewhere.
- This billing mediation server function accepts the device based billing events discussed immediately above, reformats the billing events into a format accepted and recognized by the billing system, mediates the billing event information to remove service usage billing from the user account and place it in other bill by account categories as appropriate according to the bill by account mediation rules, adds other billing events for service usage or transactions to the user account as appropriate according to the device based billing rules, and then applies the information to the billing information the user account to correct or update the account.
- a bill by account can allow for a website provider, such as Google or Yahoo, to pay for or offset certain account usage for web browsing, web based searching, web based email, or any other web based or other service usage activities, which may also be based (in whole or in part) on the activities performed by the user on such transactional services (e.g., based on advertisement viewing/accessing or click-through activities by the user, by which an advertisement business model used by such website providers directly or indirectly supports such service account subsidies).
- a bill by account can allow for an advertiser to pay for or offset certain account usage for viewing and/or accessing (e.g., clicking through) a web placed advertisement or other advertisement sent via the network to the device.
- various network chatter e.g., heartbeat related network and other network chatter related service data usage
- service data usage for access to a transactional service such as a multimedia content download service (e.g., music, eBook, music/video streaming, and/or movie or other multimedia content download service), or an online shopping site (e.g., Amazon, eBay or another online shopping site), can be billed to a transactional service account assigned to a transactional service partner that sponsors access to that sponsor's transactional service, thereby allowing that transactional service partner to pays for or offset (e.g., subsidize) the account usage for such activities, which may also be based (in whole or in part) on the transactions actually performed by the user on such transactional services (e.g., based on the volume/cost of the multimedia service download purchases by the user and/or online activities).
- a multimedia content download service e.g., music, eBook, music/video streaming, and/or movie or other multimedia content download service
- an online shopping site e.g., Amazon, eBay or another online shopping site
- device based service billing includes recording billing events on the device and then reporting such billing to the network (e.g., central billing 1619 ).
- device based service billing includes reporting service usage events and/or applying cost look-up and logging/reporting service billing updates. For example, this allows for reporting not only service usage but also cost of such service usage to the user via the user interface of device 101 . Also, for example, the cost of such service usage can also be reported to the billing server.
- device based service billing includes reporting service usage to the network, and the network determines the cost for such service usage.
- a roaming server can include a roaming service cost data table for roaming service partners.
- the device e.g., device 101
- the device can also receive the roaming service data rate based on the roaming service cost data table provided by the roaming server.
- the roaming server can send the roaming service cost data table (or a modified format of the same) to the device thereby allowing the device to determine the costs for such roaming network service usage or service activity.
- the device can also automatically use a roaming service profile when connecting to the roaming network service and/or the user can be notified of the roaming service profile options based on the roaming service data costs and then select the desired roaming service profile accordingly.
- the user is provided with a list of service costs based on locally stored roaming table and a search of available roaming partners that the device 100 detects and can connect to.
- the user is provided with a projected cost per day for one or more roaming service provider options based on typical service usage history and the cost for each service provider.
- the user is provided with a set of options for service usage notification, controlling or throttling service usage and/or cost while roaming (e.g., using the service notification and cost control techniques as similarly discussed herein but applied to the roaming network).
- these controls are set by a VSP (or, e.g., an IT manager using VSP functions).
- roaming tables are updated periodically in the background while on a home network (or other low cost network) and cached.
- cache updates occur based on fixed time period (e.g., late at night when updates are less expensive due to network inactivity).
- the roaming partner cost table cache updates are done whenever connected to a desirable network that is not as expensive or bandwidth constrained (e.g., at home, work, or off the WWAN).
- updates occur at time of day that network is not busy.
- updates occur based on network push when roaming table is changed (e.g., one or more of the roaming partners changes the rate).
- the service cost to update the roaming service cost table is charged to bill by account and possibly not charged to end user.
- the roaming service center is provided as a service that is paid for (e.g., potentially bill by account tracks all related costs).
- this type of roaming cost control can be provided as a service through central provider, MVNO, roaming partner provider, VSP or as a third party application not associated with any service provider (e.g., IT manager).
- the controls for how to update cache, set service control policies, and other controls can be defined by any number of VSP entities including the user through a website service.
- a roaming service center is provided as a service in which, for example, the user is provided with a list of service costs based on a locally stored (or remotely accessed) roaming table.
- the roaming service center provides the user with a projected cost per day for one or more roaming service provider options based on typical service usage history and the cost for each service provider.
- the roaming service center provides the user with a set of options for controlling/throttling usage and/or cost while roaming.
- these controls are set by a VSP (e.g., an IT manager using VSP functions).
- VSP e.g., an IT manager using VSP functions.
- roaming tables can be updated periodically in the background while on a home network and cached.
- cache updates occur based on a fixed time period.
- the roaming partner cost table cache updates are done whenever the device is connected to a desirable network that is not as expensive or bandwidth constrained (e.g., at home, work and/or off the WWAN).
- updates occur at time of day that network is not busy.
- updates occur based on a network push when a roaming table is changed (e.g., one or more of the roaming partners changes the rate).
- the service cost to update the roaming service cost table is charged to bill by account and possibly not charged to the user.
- the roaming service center is provided as a service that is paid for by the user and/or part of a service plan.
- a bill by account function tracks all related costs.
- the roaming service center can be provided as a service through central provider, MVNO, roaming partner provider, VSP or as a third party application not associated with any service provider (e.g., IT manager).
- a synchronized local service usage counter based on time stamped central billing information is provided.
- the local service usage counter can also be synchronized to past service usage records (e.g., time stamped central billing records of service usage for the device) and use local estimates for current/present service usage estimates for the device.
- the central billing system e.g., central billing 1619
- the device e.g., device 101
- the device can pull the time stamped central billing information
- an intermediate server can provide a mediated push or pull process.
- synchronization is performing periodically based on service usage levels with free-running estimates between synchronizations.
- service usage is projected based on calculated estimates of service usage based on synchronized service usage and local service usage count information.
- projected service usage can be calculated on the device or calculated on a server (e.g., a billing server or an intermediate billing server), which provides the calculated projected service usage information to the device, such as using various adaptive algorithms for service usage projections.
- an adaptive algorithm can use historical/past synchronized network service usage information (e.g., synchronized with local service usage data based on time stamps associated with IPDRs) to assist in service usage projections, based on, for example, total service usage count, service usage count by certain service related criteria (e.g., application, content, service type, website and/or time of day).
- an adaptive algorithm synchronizes to past service usage data (e.g., the local estimate of past service usage data is updated to be synchronized up through the point in time associated with the latest IPDR time stamp that has been received) and current local estimates of service usage collected since the latest time stamp are then added to the time stamped IPDR service usage counter to minimize the service usage counter offset so that it is no greater than the difference between the network service usage measure and the local service usage measure since the latest IPDR time stamp.
- these adaptive algorithm techniques are performed on the device and/or performed on the network (e.g., on a network server) for processing.
- an algorithm can be employed to estimate any systematic sources for the offset and correct the local service usage count to minimize the offsets.
- the IPDR service usage count is typically off by a fixed percentage, either high or low, then an algorithm can be employed to estimate a multiplier that is applied to the local service usage count to minimize the offset between IPDR service usage synchronization events.
- synchronized service usage data is used to create an improved analysis of the statistical patterns of service usage to provide more accurate service usage projections.
- additional adaptive algorithm techniques can be used including those that provide for various statistical analysis techniques and/or other techniques.
- service usage is projected for the end of a billing/service period for a service plan versus the service usage allowed under the service plan for that billing/service period.
- a display of excess charges is also provided for the projected rate of service usage based on the monitored service usage behavior through the end of the billing/service period (e.g., this can be zero if the service usage is projected to be less than that allowed under the service plan and a positive cost number if it is projected to be more than the service plan).
- this can be implemented in numerous ways, such as on a server in the network, on a gateway/router/switch in the network, and/or on the device, as discussed below and generally described herein with respect to other service/cost usage monitoring and notification embodiments.
- the service/cost usage projections and related information can be pushed to the device, or the device can be notified that such information is available to pull and/or periodically pushed/pulled.
- the service usage information/estimates can be collected from the device, the network or both (e.g., reconciled and/or synchronized) as similarly described herein.
- the service usage information/estimates are then analyzed to determine service usage/cost projects as similarly described herein and compared to the service plan for the device to determine the projected service/cost usage overage (if any).
- one or more of the following are determined by, reported to and/or displayed on the device: service usage value, projected service usage value, service usage plan limit, projected service usage overage, projected service cost overage, service plan period time duration, service plan time remaining before end of period and/or other pertinent information.
- the device also determines service costs based on the synchronized service usage count thereby allowing the device to also report the service cost information to the user.
- the device can locally store a service cost look-up table(s), locally store different service cost look-up tables for different networks and/or for roaming networks, and/or request such information from a billing or intermediate billing server (and/or a roaming server) on the network.
- the device can obtain the calculated service costs based on the synchronized local service usage count and/or network service usage count from an intermediate server (e.g., a billing or intermediate billing server) thereby offloading the computational costs associated with calculated these projections and the data storage for service cost lookup tables onto the intermediate server on the network using the network service usage counter with or, alternatively, without the synchronized local service usage counter.
- an intermediate server e.g., a billing or intermediate billing server
- service usage count categorization by network e.g., a home network (such as a Wi-Fi, WAN, femtocell or other home network) versus a roaming network
- network e.g., a home network (such as a Wi-Fi, WAN, femtocell or other home network) versus a roaming network
- the synchronized local service usage counter can be synchronized by network.
- a synchronized local service usage count for networks controlled by a central provider, for networks controlled by other providers (e.g., MVNO), and/or free networks can similarly be provided.
- a service notification and billing interface is provided.
- service usage and projected service usage such as described herein, can be displayed to the user of the device (e.g., via user interface 1697 ).
- expected/projected service or cost overrun/overage such as described herein, can also be displayed to the user.
- a most cost effective plan can be determined/projected based on historical and/or projected service usage, and this determined/projected most cost effective plan can be displayed to the user.
- a list of available networks accessible by the device can be displayed to the user. In this example, one or more undesired available networks can also be blocked from display thereby only displaying to the user desired and/or preferred available networks.
- service usage plans and/or service usage plan option comparison for one or more alternative networks or roaming networks can also be displayed to the user.
- service cost plans and/or service/cost plan option comparison for one or more alternative networks or roaming networks can also be displayed to the user.
- roaming service usage, projected roaming service usage, estimated roaming service cost, and/or projected estimated roaming service cost can also be displayed to the user. These roaming service usage/costs can also be displayed to the user so that the user can utilize this information for selecting various roaming service billing options.
- alternative and/or least cost networks are determined and displayed to the user.
- alternative warnings are displayed to the user for any or specified roaming networks.
- the service notification and billing interface notifies the user of expected network coverage (e.g., based on the device's current geography/location and the accessible networks for the device from that current geography/location) and displays options to the user based on the expected network coverage information.
- the service notification and billing interface notifies the user of their current service usage at specified service usage points and displays various options to the user (e.g., service usage options and/or billing options). For example, the user's responses to the presented options are recorded (e.g., stored locally on the device at least temporarily for reporting purposes or permanently in a local configuration data store until such configuration settings are otherwise modified or reset) and reported, such as to the billing server (e.g., central billing 1619 ).
- the billing server e.g., central billing 1619
- user input such as selected options and/or corresponding policy settings
- the service notification and billing interface displays options to the user for how the user wants to be notified and how the user wants to control service usage costs, the user's input on such notification options is recorded, and the cost control options (e.g., and the billing agent 1695 and policy control agent 1692 ) are configured accordingly.
- the user's input on service plan options/changes can be recorded, and the service plan options/changes (e.g., and the billing agent 1695 and policy control agent 1692 ) are configured/updated accordingly.
- the service notification and billing interface provides various traffic control profiles, such as for where the user requests assistance in controlling service usage costs (e.g., service data usage and/or transactional usage related activities/costs).
- the service notification and billing interface can provide various notification options, such as for where the user wants advance warning on service coverage.
- the service notification and billing interface provides options for automatic pre-buy at a set point in service usage.
- the service notification and billing interface provides the option to choose different notification and cost control options for alternative networks or roaming networks.
- an online portal or web server is provided for allowing the user to select and/or update policy settings.
- user input provided via the online portal/web server can be recorded and reported to the billing server (e.g., central billing 1619 ).
- the online portal/web server can display transaction billing information and/or accept input for a transaction billing request, which can then be reported to the billing server accordingly.
- the service processor 115 includes a service interface or user interface 1697 .
- the user interface 1697 provides the user with information and accepts user choices or preferences on one or more of the following: user service information, user billing information, service activation, service plan selection or change, service usage or service activity counters, remaining service status, service usage projections, service usage overage possibility warnings, service cost status, service cost projections, service usage control policy options, privacy/CRM/GPS related options, and/or other service related information, settings, and/or options.
- the user interface 1697 can collect service usage information from service monitor agent 1696 to update the local service usage counter (and/or, alternatively, the service usage information is obtained from the service controller 122 ) to update user interface service usage or service cost information for display to the user.
- service billing records obtained from central billing system 1619 can be used to synchronize local service usage counters and service monitor agent 1696 information to perform real-time updating of local service usage counters between billing system 1619 synchronizations.
- the user interface 1697 can display options and accept user preference feedback, such as similarly discussed above with respect to user privacy/CRM/GPS filtering, traffic monitoring and service controls.
- the user interface 1697 can allow the user of the device to modify their privacy settings, provide user feedback on service preferences and/or service experiences, modify their service profiles (e.g., preferences, settings, configurations, and/or network settings and options), to review service usage data (e.g., based on local service usage counters and/or other data monitored by the service processor 115 ), to receive various events or triggers (e.g., based on projected service usage/costs), and/or the user interface 1697 can provide/support various other user input/output for service control and service usage.
- service profiles e.g., preferences, settings, configurations, and/or network settings and options
- service usage data e.g., based on local service usage counters and/or other data monitored by the service processor 115
- receive various events or triggers e.g., based on projected service usage/costs
- the user by providing the service policy implementation and the control of service policy implementation to the preferences of the user, and/or by providing the user with the option of specifying or influencing how the various service notification and control policies or control algorithms are implemented, the user is provided with options for how to control the service experience, the service cost, the capabilities of the service, the manner in which the user is notified regarding service usage or service cost, the level of sensitive user information that is shared with the network or service provider entity, and the manner in which certain service usage activities may or may not be throttled, accelerated, blocked, enabled and/or otherwise controlled. Accordingly, some embodiments provide the service control to beneficially optimize user cost versus service capabilities or capacities in a manner that facilitates an optimized user experience and does not violate network neutrality goals, regulations and/or requirements.
- some embodiments allow the service provider, device manufacturer, device distributor, MVNO, VSP, service provider partner, and/or other “entity” to implement valuable or necessary service controls while allowing the user to decide or influence the decision on which service usage activities are controlled, such as how they are controlled or throttled and which service usage activities may not be throttled or controlled in some manner.
- the service processor 115 includes the service downloader 1663 .
- the service downloader 1663 provides a download function to install or update service software elements on the device.
- the service downloader 1663 requires a secure signed version of software before a download is accepted.
- the download can require a unique key for a particular service downloader 1663 .
- the service downloader 1663 can be stored or execute in secure memory or execute a secure memory partition in the CPU memory space.
- the service processor 115 includes a modem driver 1640 .
- the modem driver 1640 converts data traffic into modem bus (not shown) traffic for one or more modems via the modem firewall 1655 .
- modem selection and control 1811 selects the access network connection and is in communication with the modem firewall 1655
- modem drivers 1831 , 1815 , 1814 , 1813 , 1812 convert data traffic into modem bus traffic for one or more modems and are in communication with the modem selection and control 1811 .
- FIG. 1 the modem driver 1640 converts data traffic into modem bus (not shown) traffic for one or more modems via the modem firewall 1655 .
- modem selection and control 1811 selects the access network connection and is in communication with the modem firewall 1655
- modem drivers 1831 , 1815 , 1814 , 1813 , 1812 convert data traffic into modem bus traffic for one or more modems and are in communication with the modem selection and control 1811 .
- modems 2141 , 2125 , 2124 , 2123 , 2122 which are in communication with the modem bus 2120 , connect the device to one or more networks.
- different profiles are selected based on the selected network connection (e.g., different service profiles/policies for WWAN, WLAN, WPAN, Ethernet and/or DSL network connections), which is also referred to herein as multimode profile setting.
- service profile settings can be based on the actual access network (e.g., home DSL/cable or work network) behind the Wi-Fi not the fact that it is Wi-Fi (or any other network, such as DSL/cable, satellite, or T-1), which is viewed as different than accessing a Wi-Fi network at the coffee shop.
- the service controller can sit in a service provider cloud or an MVNO cloud, the service controls can be provided by a VSP capability offered by the service provider (e.g., as described herein with respect to. FIG.
- the service controller can be owned by the hotspot service provider that uses the service controller on their own without any association with an access network service provider.
- the service processors can be controlled by the service controller to divide up the available bandwidth at the hotspot according to QoS or user sharing rules (e.g., with some users having higher differentiated priority (potentially for higher service payments) than other users).
- ambient services can be provided for the hotspot for verified service processors.
- the service processor 115 and service controller 122 are capable of assigning multiple service profiles associated with multiple service plans that the user chooses individually or in combination as a package.
- a device 100 starts with ambient services that include free transaction services wherein the user pays for transactions or events rather than the basic service (e.g., a news service, eReader, PND service, pay as you go session Internet) in which each service is supported with a bill by account capability to correctly account for any subsidized partner billing to provide the transaction services (e.g., Barnes and Noble may pay for the eReader service and offer a revenue share to the service provider for any book or magazine transactions purchased form the device 100 ).
- the basic service e.g., a news service, eReader, PND service, pay as you go session Internet
- each service is supported with a bill by account capability to correctly account for any subsidized partner billing to provide the transaction services (e.g., Barnes and Noble may pay for the eReader service and offer a revenue share to the service provider for any book or magazine
- the bill by account service can also track the transactions and, in some embodiments, advertisements for the purpose of revenue sharing, all using the service monitoring capabilities disclosed herein.
- the service controller 122 After initiating services with the free ambient service discussed above, the user may later choose a post-pay monthly Internet, email and SMS service.
- the service controller 122 would obtain from the billing system 123 in the case of network based billing (or in some embodiments the service controller 122 billing event server 1622 in the case of device based billing) the billing plan code for the new Internet, email and SMS service. In some embodiments, this code is cross referenced in a database (e.g., the policy management server 1652 ) to find the appropriate service profile for the new service in combination with the initial ambient service.
- the new superset service profile is then applied so that the user maintains free access to the ambient services, and the billing partners continue to subsidize those services, the user also gets access to Internet services and may choose the service control profile (e.g., from one of the embodiments disclosed herein).
- the superset profile is the profile that provides the combined capabilities of two or more service profiles when the profiles are applied to the same device 100 service processor.
- the device 100 (service processor 115 ) can determine the superset profile rather than the service controller 122 when more than one “stackable” service is selected by the user or otherwise applied to the device.
- the flexibility of the service processor 115 and service controller 122 embodiments described herein allow for a large variety of service profiles to be defined and applied individually or as a superset to achieve the desired device 100 service features.
- the service controller 122 includes a service control server link 1638 .
- device based service control techniques involving supervision across a network are more sophisticated, and for such it is increasingly important to have an efficient and flexible control plane communication link between the device agents (e.g., of the service processor 115 ) and the network elements (e.g., of the service controller 122 ) communicating with, controlling, monitoring, or verifying service policy.
- the communication link between the service control server link 1638 of service controller 122 and the service control device link 1691 of the service processor 115 can provide an efficient and flexible control plane communication link, a service control link 1653 as shown in FIG.
- this control plane communication link provides for a secure (e.g., encrypted) communications link for providing secure, bidirectional communications between the service processor 115 and the service controller 122 .
- the service control server link 1638 provides the network side of a system for transmission and reception of service agent to/from network element functions.
- the traffic efficiency of this link is enhanced by buffering and framing multiple agent messages in the transmissions (e.g., thereby reducing network chatter).
- the traffic efficiency is further improved by controlling the transmission frequency and/or linking the transmission frequency to the rate of service usage or traffic usage.
- one or more levels of security and/or encryption are used to secure the link against potential discovery, eavesdropping or compromise of communications on the link.
- the service control server link 1638 also provides the communications link and heartbeat timing for the agent heartbeat function. As discussed below, various embodiments described herein for the service control server link 1638 provide an efficient and secure mechanism for transmitting and receiving service policy implementation, control, monitoring and verification information between the device agents (e.g., service processor agents/components) and other network elements (e.g., service controller agents/components).
- the service control server link 1638 can employ the counterpart service control plane secure transmission methods discussed above with respect to the service control device link 1691 .
- one or more layers of security can be used to secure the communications link, including, for example, basic IP layer security, TCP layer security, service control link layer security, and/or security specific from service controller servers to service processor agents.
- the service control server link 1638 reduces network chatter by efficiently transmitting service control related communications over the link.
- the service control server link 1638 can transmit server messages asynchronously as they arrive.
- the service control server link 1638 can perform collection or buffering of server messages between transmissions.
- the service control server link 1638 can determine when to transmit based potentially on several parameters, such as one or more of: periodic timer trigger, waiting until a certain amount of service usage or traffic usage has occurred, responding to a service agent message, responding to a service agent request, initiated by one or more servers, initiated by a verification error condition, and/or initiated by some other error condition.
- the service control server link 1638 can take all buffered agent communications and frame the communications.
- the service control server link 1638 can provide for an efficient communication link based on various embodiments related to the timing of transmissions over the service control link, as similarly discussed above with respect to the service control device link 1691 description.
- the timing functions such as asynchronous messages or polling for messages, constant frequency transmission, transmission based on how much service usage or data traffic usage has taken place, transmission in response to device side control link message, service verification error events, other error events, and/or other message transmission trigger criteria can be determined, controlled and/or initiated by either the device side or the network side depending on the embodiment.
- the service control server link 1638 provides for securing, signing, encrypting and/or otherwise protecting the communications before sending such communications over the service control link 1653 .
- the service control server link 1638 can send to the transport layer or directly to the link layer for transmission.
- the service control server link 1638 further secures the communications with transport layer encryption, such as TCP TLS or another secure transport layer protocol.
- the service control server link 1638 can encrypt at the link layer, such as using IPSEC, various possible VPN services, other forms of IP layer encryption and/or another link layer encryption technique.
- the service control server link 1638 includes the agent heartbeat function in which the agents provide certain required reports to the service processor for the purpose of service policy implementation verification or for other purposes.
- the heartbeat function can also be used to issue queries or challenges, messages, service settings, service control objectives, information requests or polling, error checks and/or other communications to the agents.
- agent heartbeat messages can be in the open or encrypted, signed and/or otherwise secured. Additional heartbeat function and the content of heartbeat messages can be provided as similarly described herein, such as described above with respect to the service control device link 1691 and the access control integrity agent 1694 and other sections.
- the service controller 122 and/or agents of the service controller 122 are programmed to periodically provide reports, such as upon a heartbeat response (e.g., an agent can repeatedly send necessary reports each heartbeat), and appropriate actions can then be taken based upon such received reports.
- a heartbeat response e.g., an agent can repeatedly send necessary reports each heartbeat
- appropriate actions can then be taken based upon such received reports.
- the heartbeat function provides an important and efficient system in various embodiments described herein for verifying the service policy implementation and/or protecting against compromise events.
- the agent heartbeat service can perform many of which are discussed herein, while many others will be apparent to one of ordinary skill in the art given the principles, design background and various embodiments provided herein.
- the service control server link 1638 also provides a service control software download function for various embodiments, which, for example, can include a download of new service software elements, revisions of service software elements, and/or dynamic refreshes of service software elements of the service processor 115 on the device.
- this function is performed by the service control server link 1638 transmitting the service control software as a single file over the service control link.
- the file can have encryption or signed encryption beyond any provided by the communication link protocol itself for service control link 1653 .
- the service control software files can be segmented/divided into smaller packets that are transmitted in multiple messages sent over the service control link 1653 .
- the service control software files can be transmitted using other delivery mechanism, such as a direct TCP socket connection from a service download control server 1660 , which can also involve secure transport and additional levels of encryption.
- the service control server link 1638 and/or service download control server 1660 use(s) an agent serial number and/or a security key look up when agents are updated and/or when a dynamic agent download occurs.
- the service controller 122 includes an access control integrity server 1654 .
- the access control integrity server 1654 collects device information on service policy, service usage, agent configuration and/or agent behavior. For example, the access control integrity server 1654 can cross check this information to identify integrity breaches in the service policy implementation and control system. In another example, the access control integrity server 1654 can initiate action when a service policy violation or a system integrity breach is suspected.
- the access control integrity server 1654 (and/or some other agent of service controller 122 ) acts on access control integrity agent reports and error conditions. Many of the access control integrity agent 1654 checks can be accomplished by the server. For example, the access control integrity agent 1654 checks include one or more of the following: service usage measure against usage range consistent with policies (e.g., usage measure from the network and/or from the device); configuration of agents; operation of the agents; and/or dynamic agent download.
- the access control integrity server 1654 (and/or some other agent of service controller 122 ) verifies device service policy implementations by comparing various service usage measures (e.g., based on network monitored information, such as by using IPDRs, and/or local service usage monitoring information) against expected service usage behavior given the policies that are intended to be in place.
- device service policy implementations can include measuring total data passed, data passed in a period of time, IP addresses, data per IP address, and/or other measures such as location, downloads, email accessed, URLs, and comparing such measures expected service usage behavior given the policies that are intended to be in place.
- the access control integrity server 1654 (and/or some other agent of service controller 122 ) verifies device service policy, and the verification error conditions that can indicate a mismatch in service measure and service policy include one or more of the following: unauthorized network access (e.g., access beyond ambient service policy limits); unauthorized network speed (e.g., average speed beyond service policy limit); network data amount does not match policy limit (e.g., device not stop at limit without re-up/revising service policy); unauthorized network address; unauthorized service usage (e.g., VOIP, email, and/or web browsing); unauthorized application usage (e.g., email, VOIP, email, and/or web); service usage rate too high for plan, and policy controller not controlling/throttling it down; and/or any other mismatch in service measure and service policy.
- unauthorized network access e.g., access beyond ambient service policy limits
- unauthorized network speed e.g., average speed beyond service policy limit
- network data amount does not match policy limit e.g.,
- the access control integrity server 1654 (and/or some other agent of service controller 122 ) verifies device service policy based at least in part on, for example, various error conditions that indicate a mismatch in service measure and service policy.
- various verification error conditions that can indicate a mismatch in service measure and service policy include one or more of the following: mismatch in one service measure and another service measure; agent failure to report in; agent failure to respond to queries (e.g., challenge-response sequence and/or expected periodic agent reporting); agent failure to respond correctly to challenge/response sequence; agent improperly configured; agent failure in self checks; agent failure in cross-checks; unauthorized agent communication or attempted unauthorized communication; failure in service policy implementation test; failure in service usage reporting test; failure in service usage billing test; failure in transaction billing test; failure in download sequence; environment compromise event, such as unauthorized software load or execution (or attempt), unauthorized memory access (or attempt), unauthorized agent access (or attempt), known harmful software, and/or known harmful communications signature; and/or failure
- the access control integrity server 1654 (and/or some other agent of service controller 122 ) verifies device service policy by performing automated queries and analysis, which are then reported (e.g., anomalous/suspicious report results can be reported for further analysis by a person responsible for determining whether such activities indicate out of policy activities or to provide information to the user to inform the user of such anomalous/suspicious report results that may indicate out of policy activities). For example, the user can review the report to authorize whether such activities were performed by the user (e.g., website access requests, specific transactions, and/or phone calls) and/or indicate that such activities were not authorized by the user (e.g., indicate a potential compromise of the device, such as by malware or other unauthorized software/user use of the device).
- anomalous/suspicious report results can be reported for further analysis by a person responsible for determining whether such activities indicate out of policy activities or to provide information to the user to inform the user of such anomalous/suspicious report results that may indicate out of policy activities.
- the user can
- the user can also be connected to communicate with service support of the service provider regarding such reported activities (e.g., by text/chat, voice/phone, and/or video conference to a service support).
- the access control integrity server 1654 (and/or some other agent of service controller 122 ) provides a policy/service control integrity service to continually (e.g., periodically and/or based on trigger events) verify that the service control of the device has not been compromised and/or is not behaving out of policy.
- the device upon detection of one or more service verification errors, such as the various service verification errors discussed above, the device is directed to a quarantine network status in which the device can, for example, only access network control plane functions, billing functions, and other functions generally controlled by the access network service provider or the central service provider.
- quarantine network access restrictions and routing can be accomplished with the access network AAA and routing system (e.g., access network AAA server 1621 and one or more of the gateways 410 , 420 , 508 , 512 , 520 , 608 , 612 , 620 , 708 , 712 , 720 ) or can be accomplished with device based access control or traffic control policy implementation.
- Quarantine network equipment or servers can, for example, be located within the access network or within another network with access to the access network. Communication with the quarantine network infrastructure can be accomplished, for example, with a secure link with one or more encryption levels or a dedicated private link.
- quarantining a device includes, for example, a two step process for routing quarantine network device traffic, first, to a quarantine traffic handling router or server and, second, from there to the actual quarantine network infrastructure, with the route being determined by device parameters, user parameters, access service provider parameters or other parameters associated with the quarantine network routing.
- the device is completely suspended from the network in which, for example, the device can first issue a user interface message to the user or issuing another form of a message to the user or service subscriber, such as via email, hard copy message and/or voice message.
- the device network access, service capabilities and/or traffic shaping are limited, partially restricted or completely restricted, service capabilities. For example, these limitations and/or restrictions can be implemented in the device and/or in the network. For example, implementing a device quarantine (e.g., using a RADIUS server to quarantine the device) can involve assigning the device to a different billing profile.
- switch based port analysis is performed to further monitor the device (e.g., referred to as Switched Port Analyzer (SPAN) on Cisco switches, and various other vendors have different names for it, such as Roving Analysis Port (RAP) on 3Com switches).
- the device service policy implementation behavior is monitored at a deeper level in the network by copying device traffic in the switch so that it goes to both an intended data path destination and to a specified port for switch based port analysis (e.g., the traffic content can be analyzed and recorded using deep packet inspection (DPI) techniques, which can provide a finer level of detail than the typical IPDR).
- DPI deep packet inspection
- an advantage of performing a switch based port analysis function is that the traffic need not be analyzed in real time, and a sample subset of the devices on the network can be selected for such analysis based on, for example, either identifying devices that have suspect service policy implementation behavior and/or a regular sampling algorithm that eventually samples all devices, or some other selection approaches.
- a scheduled switch based port analysis sampling can be applied that eventually rotates through all devices and designates a higher priority in the sampling queue for devices that are suspect.
- switch based port analysis allows for off-line sampled or non-real-time DPI, as described above, as a verification measure for the device based service control measures that are implemented.
- sophisticated DPI techniques are used to enhance the content of the IPDRs so that they provide detailed information that can be made available in the network. For example, some of the DPI packet analysis may be redundant between the device and the network, but this approach provides for a much finer grain validation for the device based service and less reliance on the device for some of the service traffic analysis that service providers need.
- the device control server functions and the service control policy verification functions are implemented in an integrated hardware/software system (e.g., a gateway, server, router, switch, base station, base station aggregator, AAA server cluster or any other hardware or hardware/software system) located in the network that the network level traffic inspection is accomplished in, or in one or more servers integrated to operate in a coordinated manner with the DPI boxes.
- an integrated hardware/software system e.g., a gateway, server, router, switch, base station, base station aggregator, AAA server cluster or any other hardware or hardware/software system
- the device control server functions and the service control policy verification functions are implemented in an integrated hardware/software system (e.g., a gateway, server, router, switch, base station, base station aggregator, AAA server cluster or any other hardware or hardware/software system) located in the network that provides deep service control capability (e.g., using DPI techniques) for devices that have some or all of the service processor functions installed and, in some embodiments, also providing coarser network control of the basics for devices that do not have a service processor installed in the device (e.g., such coarser network control functions include max data rate and/or max total data).
- an integrated hardware/software system e.g., a gateway, server, router, switch, base station, base station aggregator, AAA server cluster or any other hardware or hardware/software system located in the network that provides deep service control capability (e.g., using DPI techniques) for devices that have some or all of the service processor functions installed and, in some embodiments, also providing coarser network control of the basics for devices that do not have a service processor installed in the
- the SPAN function is used in a revolving periodic manner as well to augment CDR data with deeper packet information for the purpose of spot-checking device based service usage measures.
- spot checking network address access policies spot checking ambient access policies
- spot checking billing event reports spot checking intermediate networking device/end point device count (via checking network source or destination addresses, token, cookies or other credentials, etc).
- the periodic SPAN can be scheduled for all devices equally, for certain devices or users with higher priority, frequency or depth of SPAN than others, higher priority, higher frequency or immediate priority for devices with higher usage patterns or unusual usage patterns, immediate or very high priority for devices with a policy violation status.
- a combination traffic inspection and service control approach implements traffic and service control functions in the network that are conducive for a network based implementation and implements traffic and service control functions in the device that are either more conducive for performing in the device or can only be performed in the device (e.g., activities involving inspection of traffic that is encrypted once it is transmitted to the network).
- activities that can be done in the network are generally performed in the network and/or are more efficiently performed in the network than the device, and activities that are more efficiently performed in the device or can only be performed in the device are performed in the device (e.g., depending on device processing/storage capabilities and/or other design/security considerations).
- network based packet processing capability limitations e.g., encrypted traffic, application layer information unavailable once the traffic goes into the networking stack, other application/usage context information available on the device but not in the network
- information that is generally/preferably maintained and processed locally in the device for network neutrality reasons e.g., network neutrality issues can generally be efficiently implemented by keeping all, substantially all or at least some aspect of decisions on how to implement algorithms to control traffic local to the device and under user decision control, and/or by providing the user with a set of pre-packaged choices on how to manage service usage or service activity usage or manage service usage versus service cost or price
- information that is generally/preferably maintained and processed locally in the device for user privacy reasons e.g., deeper levels of traffic monitoring and service usage monitoring data where it is available for assisting the user in achieving the best, lowest cost experience and implementing a CRM filter function to the user so that the user can control the level of CRM the network is allowed to
- a network based solution is provided for a more basic set of services for all devices that do not have service control capabilities, and a super-set of services and/or additional services are provided for devices that include a service processor.
- a service controller function can be located in various places in the network in accordance with various embodiments.
- various other embodiments described herein also employ a hybrid service control function performing certain service control functions in the network (e.g., collecting network service usage information, such as IPDRs, and/or performing DPI related functions in the network for collecting network service usage information and/or throttling/shaping traffic) and service control functions in the device (e.g., service processor 115 , which, for example, monitors service usage in the device and/or performs throttling or traffic shaping in the device and/or performs certain billing event recording and reporting functions that are aptly performed on the device).
- certain service control functions in the network e.g., collecting network service usage information, such as IPDRs, and/or performing DPI related functions in the network for collecting network service usage information and/or throttling/shaping traffic
- service control functions in the device e.g., service processor 115 , which, for example, monitors service usage in the device and/or performs throttling or traffic shaping in the device and/or performs certain billing event recording and reporting functions
- lower level service policy implementation embodiments are combined with a higher level set of service policy supervision functions to provide device assisted verifiable network access control, authentication and authorization services.
- device based access control services are extended and combined with other policy design techniques to create a simplified device activation process and connected user experience referred to herein as ambient activation.
- ambient activation can be provided by setting access control to a fixed destination, verifying access with IPDRs, verifying access by setting a max data rate and triggering off in the network if it exceeds the max data rate, and/or by various other techniques.
- service controller 122 includes a service history server 1650 .
- the service history server 1650 collects and records service usage or service activity reports from the Access Network AAA Server 1621 and the Service Monitor Agent 1696 .
- service usage history from the network elements can in certain embodiments be less detailed than service history from the device, the service history from the network can provide a valuable source for verification of device service policy implementation, because, for example, it is extremely difficult for a device error or compromise event on the device to compromise the network based equipment and software.
- service history reports from the device can include various service tracking information, as similarly described above.
- the service history server 1650 provides the service history on request to other servers and/or one or more agents.
- the service history server 1650 provides the service usage history to the device service history 1618 .
- the service history server 1650 maintains a history of which networks the device has connected to.
- this network activity summary can include a summary of the networks accessed, activity versus time per connection, and/or traffic versus time per connection.
- this activity summary can further be analyzed or reported to estimate the type of service plan associated with the traffic activity for the purpose of bill sharing reconciliation.
- service controller 122 includes a policy management server 1652 .
- the policy management server 1652 transmits policies to the service processor 115 via the service control link 1653 .
- the policy management server 1652 manages policy settings on the device (e.g., various policy settings as described herein with respect to various embodiments) in accordance with a device service profile.
- the policy management server 1652 sets instantaneous policies on policy implementation agents (e.g., policy implementation agent 1690 ). For example, the policy management server 1652 can issue policy settings, monitor service usage and, if necessary, modify policy settings.
- the policy management server 1652 can maintain a relatively high frequency of communication with the device to collect traffic and/or service measures and issue new policy settings.
- device monitored service measures and any user service policy preference changes are reported, periodically and/or based on various triggers/events/requests, to the policy management server 1652 .
- user privacy settings generally require secure communication with the network (e.g., a secure service control link 1653 ), such as with the policy management server 1652 , to ensure that various aspects of user privacy are properly maintained during such configuration requests/policy settings transmitted over the network.
- information can be compartmentalized to service policy management and not communicated to other databases used for CRM for maintaining user privacy.
- the policy management server 1652 provides adaptive policy management on the device.
- the policy management server 1652 can issue policy settings and objectives and rely on the device based policy management (e.g., service processor 115 ) for some or all of the policy adaptation.
- This approach can require less interaction with the device thereby reducing network chatter on service control link 1653 for purposes of device policy management (e.g., network chatter is reduced relative to various server/network based policy management approaches described above).
- This approach can also provide robust user privacy embodiments by allowing the user to configure the device policy for user privacy preferences/settings so that, for example, sensitive information (e.g., geo-location data, website history) is not communicated to the network without the user's approval.
- sensitive information e.g., geo-location data, website history
- the policy management server 1652 adjusts service policy based on time of day. In some embodiments, the policy management server 1652 receives, requests or otherwise obtains a measure of network availability and adjusts traffic shaping policy and/or other policy settings based on available network capacity.
- the policy management server 1652 performs a service control algorithm to assist in managing overall network capacity or application QoS. In some embodiments, the policy management server 1652 performs an algorithm to determine which access network is best to connect to, such as based on network capacity or application QoS, service usage costs, and/or any other criteria. In some embodiments, the device is capable of connecting to more than one network, and accordingly, device service policies can be selected/modified based on which network the device is connected to. In some embodiments, the network control plane servers detect a network connection change from a first network to a second network and initiate the service policy implementation established for the second network. In other embodiments, the device based adaptive policy control agent (e.g., policy control agent 1692 described herein) detects network connection changes from the first network to the second network and implements the service policies established for the second network.
- the device based adaptive policy control agent e.g., policy control agent 1692 described herein
- the network when more than one access network is available, the network is chosen based on which network is most preferred according to a network preference list or according to the network that optimizes a network cost function.
- the preference list can be pre-established by the service provide and/or the user.
- the network cost function can be based on a minimum service cost, maximum network performance, determining whether or not the user or device has access to the network, maximizing service provider connection benefit, reducing connections to alternative paid service providers, and/or a variety of other network preference criteria.
- the device detects when one or more preferred networks are not available, implements a network selection function or intercepts other network selection functions, and offers a connection to the available service network that is highest on a preference list.
- the preference list can be set by the service provider, the user and/or the service subscriber.
- service controller 122 includes a network traffic analysis server 1656 .
- the network traffic analysis server 1656 collects/receives service usage history for devices and/or groups of devices and analyzes the service usage.
- the network traffic analysis server 1656 presents service usage statistics in various formats to identify improvements in network service quality and/or service profitability.
- the network traffic analysis server 1656 estimates the service quality and/or service usage for the network under variable settings on potential service policy.
- the network traffic analysis server 1656 identifies actual or potential service behaviors by one or more devices that are causing problems for overall network service quality or service cost.
- service controller 122 includes a beta test server 1658 .
- the beta test server 1658 publishes candidate service plan policy settings to one or more devices.
- the beta test server 1658 provides summary reports of network service usage or user feedback information for one or more candidate service plan policy settings.
- the beta test server 1658 provides a mechanism to compare the beta test results for different candidate service plan policy settings or select the optimum candidates for further policy settings optimization.
- service controller 122 includes a service download control server 1660 .
- the service download control server 1660 provides a download function to install and/or update service software elements (e.g., the service processor 115 and/or agents/components of the service processor 115 ) on the device, as described herein.
- service controller 122 includes a billing event server 1662 .
- the billing event server 1662 collects billing events, provides service plan information to the service processor 115 , provides service usage updates to the service processor 115 , serves as interface between device and central billing server 1619 , and/or provides trusted third party function for certain ecommerce billing transactions.
- the Access Network AAA server 1621 is in network communication with the access network 1610 .
- the Access Network AAA server 1621 provides the necessary access network AAA services (e.g., access control and authorization functions for the device access layer) to allow the devices onto the central provider access network and the service provider network.
- another layer of access control is required for the device to gain access to other networks, such as the Internet, a corporate network and/or a machine to machine network. This additional layer of access control can be implemented, for example, by the service processor 115 on the device.
- the Access Network AAA server 1621 also provides the ability to suspend service for a device and resume service for a device based on communications received from the service controller 122 .
- the Access Network AAA server 1621 also provides the ability to direct routing for device traffic to a quarantine network or to restrict or limit network access when a device quarantine condition is invoked. In some embodiments, the Access Network AAA server 1621 also records and reports device network service usage (e.g., device network service usage can be reported to device service history 1618 ).
- device network service usage e.g., device network service usage can be reported to device service history 1618 .
- the device service history 1618 is in network communication with the access network 1610 .
- the device service history 1618 provides service usage data records used for various purposes in various embodiments.
- the device service history 1618 is used to assist in verifying service policy implementation.
- the device service history 1618 is used to verify service monitoring.
- the device service history 1618 is used to verify billing records and/or billing policy implementation.
- the device service history 1618 is used to synchronize and/or verify the local service usage counter.
- the central provider billing server 1619 is in network communication with the access network 1610 .
- the central provider billing server 1619 provides a mediation function for central provider billing events.
- the central provider billing server 1619 can accept service plan changes.
- the central provider billing server 1619 provides updates on device service usage, service plan limits and/or service policies.
- the central provider billing server 1619 collects billing events, formulates bills, bills service users, provides certain billing event data and service plan information to the service controller 122 and/or device 100 .
- device and network apparatus coordinate one or more of the following: network service policy implementation settings, device service policy implementation settings, network service profile implementation settings, device service profile implementation settings, network service usage measures used for the purpose of verifying service policy implementation, device service usage measures used for the purpose of verifying service policy implementation, network actions taken upon detection of service usage policy violation and device actions taken upon detection of service usage policy violation.
- local device settings for the service monitoring, usage and/or billing profile or policy settings used, for example, by a device service processor 115 are associated with corresponding records for the various network apparatus that also rely upon the service policy and profile settings to monitor, control and/or bill for services or to respond to out of policy service usage conditions.
- such network apparatus include the service controller 122 or similar functions, the billing system 123 or similar functions, the network AAA 121 , gateways 410 , 420 , 508 , 512 , 520 , 608 , 612 , 620 , 708 , 712 , 720 , or other networking equipment.
- the service profile or policy settings are associated between the device and network in a manner that allows for effective and coordinated operation between the device service processor 115 and the network apparatus, but does not require an explicit function that simultaneously controls/coordinates the service policy or profile implementation and/or verification actions taken by the device 100 (e.g., the service processor 115 ) and the network apparatus.
- such embodiments can be applied in overlay applications as discussed below.
- a network function obtain, derive or otherwise determine the association of the service profile or policy settings to program a device service processor 115 and the various network apparatus functions (e.g., possibly including but not limited to the service controller 122 or similar functions, the billing system 123 or similar functions, the network AAA 121 , gateways 410 , 420 , 508 , 512 , 520 , 608 , 612 , 620 , 708 , 712 , 720 , or other networking equipment) by reading, receiving, querying, pulling or otherwise obtaining the settings from one or more of the network apparatus functions or from a data base that stores the service policy or profile settings for one or more of the network apparatus functions.
- the various network apparatus functions e.g., possibly including but not limited to the service controller 122 or similar functions, the billing system 123 or similar functions, the network AAA 121 , gateways 410 , 420 , 508 , 512 , 520 , 608 , 612 , 620 , 708 , 7
- a mapping (e.g., an association) of the network apparatus settings to the appropriate device 100 (service processor 115 ) settings can be determined to advantageously support the service usage monitoring, service usage control, service usage billing or service usage verification objectives being addressed.
- the policy or profile settings for the device can be a direct translation of the policy or profile settings used for the network apparatus, or the device policy or profile settings can be less directly derived from the network apparatus policy or profile settings.
- service usage limits contained in the billing system 123 service plan can be either directly mapped to usage limit settings on the device service processor 115 (e.g., service usage stops when the limit is hit or the user is notified or the user is billed), or the usage limits can be mapped to a number of service profiles the user may select from (e.g., as discussed herein, the user can select from options involving various actual usage versus usage limit notification policies and/or service usage control, limitations or throttling policies).
- the service usage policy or profile limits or allowances maintained for the network apparatus functions can be read or queried by a network function (e.g., the service controller 122 or the service controller 122 through a second intermediary server connected to the billing system 123 and/or the AAA system 121 ), and the service usage limits stored in these networking apparatus can be either directly translated to the settings for the service processor 115 or may need to be interpreted, expanded or otherwise modified to obtain the required service processor 115 policy and/or profile settings.
- the service usage limits set in the billing system 123 service plan record, and/or the service profile record stored in the AAA system 121 can be acquired (e.g., from the apparatus or from a database storing the settings for the apparatus) by the service controller (or another network function) and directly translated and used to program the settings in the service processor 123 .
- the service usage limits are determined or obtained by the activation server apparatus embodiments, other apparatus embodiments associated with service activation, or the virtual service provider embodiments, as described herein.
- the service policy or profile for service monitoring, control, billing, verification and/or actions taken on verification error can be coordinated between device and network even if some of the network functions act independent of some of the device functions.
- associating the service usage policies and/or profiles between the device service processor 115 and the various network apparatus functions, and then allowing for independent operation or action by the various functions in a manner that results in a coordinated outcome facilitates an overlay of the device assisted services technology onto existing network equipment in a manner that results in reliable and verifiable service enhancements while minimizing the need for major existing network equipment upgrades.
- the association of the service profile or policy settings used by a device service processor 115 and the service profile or policy settings used by the various network apparatus functions can be provided by a centralized network function that determines the appropriate settings for the network apparatus and the service processor 115 and sets one or more settings to each function.
- this networking function is provided by a centralized network management function or service account activation function (e.g., the activation server apparatus embodiments, one of the other disclosed apparatus embodiments associated with service activation or the virtual service provider apparatus embodiments, as described herein).
- the association of the service profile or policy settings used by a device service processor 115 and the service profile or policy settings used by the various network apparatus functions can be provided by a network function that by reads, receives, queries, pulls or otherwise obtains the setting used by the service controller 122 or the service processor 115 .
- the network function can then determine the association of the service profile or policy settings used by a device service processor 115 and the service profile or policy settings required by the various network apparatus functions before writing, transmitting, pushing, or otherwise recording the appropriate settings required by each of the other network apparatus functions.
- this functionality can be implemented in the service controller (e.g., the policy management server, possibly acting in coordination with another network function or server), which then links into the databases used for storing the policy or profile settings for the other network apparatus.
- the network based service usage measures e.g., IPDRs communicated to the billing system 123 , the AAA 121 , service controller 122 or other network functions used to verify service usage and/or take actions
- the network apparatus e.g., billing system 123 and AAA 121
- independent service profile or policy verification error response actions can be taken by the network apparatus (e.g., suspend, quarantine, SPAN or flag device 100 , notify the user and possibly require acknowledgement, or bill the user account for service usage overage) without direct involvement by the service processor 115 and/or the service controller 122 .
- the network apparatus e.g., suspend, quarantine, SPAN or flag device 100 , notify the user and possibly require acknowledgement, or bill the user account for service usage overage
- the association between service profile and/or service policy that is implemented on the device 100 (e.g., service processor 115 ) and the service profile and/or policy usage limits recorded in network apparatus can be associated with one another by one or more of the following: (A) implementing a function to read from the network database (e.g., the billing 123 data base, AAA 121 data base, service controller 122 data base, etc.) and mapping the network profiles and/or policies to device 100 (e.g., service processor 115 ) profiles and/or policies; (B) implementing a function that simultaneously sets the device profile and/or policy and the network equipment profile and/or policy recorded in the appropriate data base records; and (C) implementing a function that reads the profile and/or policy on the device 100 (e.g., service processor 115 ) or the service controller 122 and then sets the network equipment profile and/or policy recorded in the appropriate data base records.
- A implementing a function to read from the network database (e.g., the billing 123 data base, AAA 121
- FIG. 17 is another functional diagram illustrating the device based service processor 115 and the service controller 122 in accordance with some embodiments.
- FIG. 17 provides for various embodiments as similarly described above with respect to the various embodiments described above with respect to FIG. 16 , with one of the differences being that the service controller 122 as shown in FIG. 17 is connected to the access network and not (directly) connected to the Internet. Accordingly, as shown in FIG. 17 , in some embodiments, the service control link 1653 is a communications link between the service controller 122 and the service processor 115 over the access network 1610 .
- FIG. 18 is another functional diagram illustrating the device based service processor 115 and the service controller 122 in which the service processor controls the policy implementation for multiple access network modems and technologies in accordance with some embodiments.
- FIG. 18 provides for various embodiments as similarly described above with respect to the various embodiments described above with respect to FIG. 16 , with one of the differences being that the service processor controls the policy implementation for multiple access network modems and technologies.
- a connection manager 1804 which as shown is in control plane communication with a modem selection and control 1811 , provides a control and supervision function for one or more modem drivers or modems that connect to an access network.
- the modem selection and control 1811 selects the access network connection and is in communication with the modem firewall 1655 , and modem drivers, which as shown include Dial/DSL modem driver 1831 , Ethernet modem driver 1815 , WPAN modem driver 1814 , WLAN modem driver 1813 , and WWAN modem driver 1812 , convert data traffic into modem bus traffic for one or more modems and are in communication with the modem selection and control 1811 .
- modem drivers which as shown include Dial/DSL modem driver 1831 , Ethernet modem driver 1815 , WPAN modem driver 1814 , WLAN modem driver 1813 , and WWAN modem driver 1812 , convert data traffic into modem bus traffic for one or more modems and are in communication with the modem selection and control 1811 .
- FIG. 19 is another functional diagram illustrating the service processor 115 and the service controller 122 in accordance with some embodiments.
- a stripped down (e.g., reduced set of agents/components/functionality) embodiment of the service processor 115 and the service controller 122 are provided in which service policy is not adaptive but rather is set by the service controller 122 .
- the agent within the service processor 115 that implements service policy is the policy implementation agent 1690 .
- the service controller 122 is similarly stripped down to a simplified configuration (e.g., reduced set of agents/components/functionality).
- many of the service policy implementation verification and compromise protection techniques are similarly provided using these simplified configurations of the service processor 115 and the service controller 122 , as described above with respect to, for example, FIG. 16 .
- the service control device link 1691 and service control server link 1638 can be used for downloading service policies to the policy implementation agent 1690 (but, in some embodiments, cannot perform the heartbeat or authentication function).
- a basic service profile or service policy implementation verification technique for this reduced configuration calls for the access control integrity server 1654 to obtain IPDRs from access network AAA server 1621 (or 121 ) (e.g., or other network functions as described herein) and compare the service usage exhibited by device 100 with a range of expected service usage that would be expected if the intended service policies were in place on the device.
- the access control integrity server 1654 initiates or carries out one or more of the service usage profile or policy verification error response actions disclosed herein, including, for example, one or more of the following: notify the user of the out of policy or overage condition, require the user to acknowledge the condition and/or acknowledge a subsequent billing event to proceed, bill the user for service overage, suspend the device from the network, quarantine the device, SPAN the device, or notify a network manager or device management or error handling function.
- a service profile or service policy implementation verification technique for this reduced configuration calls for the billing system 123 to obtain IPDRs from access network AAA server 1621 (or 121 ) (or other network functions as discussed herein) and compare the service usage exhibited by device 100 with a range of expected service usage that would be expected if the intended service policies were in place on the device.
- the billing system 123 initiates or carries out one or more of the service usage profile or policy verification error response actions disclosed herein, including, for example, one or more of the following: notify the user of the out of policy or overage condition, require the user to acknowledge the condition and/or acknowledge a subsequent billing event to proceed, bill the user for service overage, suspend the device from the network, quarantine the device, SPAN the device, or notify a network manager or device management or error handling function.
- a service profile or service policy implementation verification technique for this reduced configuration calls for the AAA server 1621 (or 121 ) itself to compare the service usage exhibited by device 100 with a range of expected service usage that would be expected if the intended service policies were in place on the device.
- the AAA server 1621 (or 121 ) initiates or carries out one or more of the service usage profile or policy verification error response actions disclosed herein, including, for example, one or more of the following: notify the user of the out of policy or overage condition, require the user to acknowledge the condition and/or acknowledge a subsequent billing event to proceed, bill the user for service overage, suspend the device from the network, quarantine the device, SPAN the device, or notify a network manager or device management or error handling function.
- this approach provides a basic first layer of service policy implementation verification that does not depend on device based agent behavior for the verification. If the service policy is in error in a way that violates the expected service policy usage limits, then the access control integrity server 1654 will detect this condition and appropriate action can be taken. In some embodiments, if one or more service policy integrity verification tests fail, the appropriate responsive actions can include routing the device to quarantine status, sending an error message to the device or device user interface and then suspend access for the device, and/or limiting access in some way without completely suspending access, as similarly described above.
- the appropriate responsive actions can include logging excess service usage above the intended service policy limits and billing the user for some or all of the excess usage; sending the user a notification and/or acknowledgement response request (possibly including a simple keystroke acknowledgement, or a password, a biometric signature or other secure response), and/or limiting access in some way without completely suspending access, as similarly described above:
- a billing system technique provides another verification overlay.
- the service processor 115 can have a set of service policy implementations (or service profile) that calls for maintaining service usage within a certain limit, or assisting the user or network to maintain service usage to that limit.
- the billing system 123 can be implemented in a way to provide a “back stop” to the service usage controls or limits provided for by the service processor 115 , so that even if the service processor 115 is compromised, hacked, spoofed or is otherwise in error, the billing system 123 protects the service provider, “service owner”, carrier, VSP or network operator from unpaid access beyond the service limits.
- the billing system 123 can receive service usage information from the IPDRs that are aggregated in the network as in the case of a conventional billing system, and because these network based measures are independent from the device agent operation, they cannot be spoofed by merely spoofing something on the device or service processor 115 . In this manner, defeating the service processor 115 service agent control mechanisms described herein simply results in a billing charge and not free service.
- the user can be notified as discussed herein, and the user can be required to acknowledge the overage and approve a billing charge for the overage as also discussed herein, with the acknowledgement being communicated back to the network in some embodiments.
- This positive acknowledgement also provides a layer of protection and verification of the service control and usage limit control for the device service processor 115 .
- the user is requested to input a password, biometric or other secure response to the usage overage notification, providing yet another layer of protection to verify that the user intends to pay for the service usage overage.
- the service processor 115 assistance for service usage control can be verified and/or protected from compromise.
- the service control device link 1691 and service control server link 1638 are used to implement the service processor 115 heartbeat authentication and communication functions to strengthen the verification of a proper service policy implementation of the embodiments of FIG. 19 .
- the heartbeat function can be used as authentication for service monitoring versus network reports.
- the heartbeat function can be used as authentication for challenge/response queries of agents.
- the heartbeat function can be used as authentication for access control.
- the communication access to the policy implementation agent 1690 is restricted so that software or hardware on device 100 and/or on a network cannot have authorized access to the policy implementation agent 1690 .
- authorized access to the policy implementation agent 1690 can be restricted to include only the service controller 122 through the service control device link 1691 and the service control server link 1638 .
- the agent control bus 1630 can be secured with encryption and/or other security techniques so that only the service control device link 1691 can have authorized access to the policy implementation agent 1690 .
- the agent level message encryption can be used as described herein.
- the service policy implementation agent 1690 of the embodiments of FIG. 19 can be further strengthened against errors, intrusion, tampering, hacking and/or other inadvertent or intentional integrity degradation by using various other techniques.
- the dynamic agent download feature of the service controller 122 can download a new version of the policy implementation agent 1690 .
- the new agent code can be identical in functionality and also hashed, obfuscated or ordered differently before signing and encryption so that any hacking attempt must be reinitiated, and this process can be periodically repeated or repeated upon a triggering event.
- the new dynamically loaded agent can be required to perform an environment scan to determine if the system configuration or operation are as expected, and/or it can seek to detect elements in the execution environment that can be harmful or threatening to the integrity of the policy implementation.
- the agent can also be required to report back on the scan within a relatively short period of time so that any attempt to compromise the agent does not have sufficient time to be effective.
- the service policy implementation agent 1690 of the embodiments of FIG. 19 can be further strengthened to protect the policy implementation from compromise attempts by locating the software and/or hardware used onto an access modem associated with the service.
- the modem can make it difficult to get access to the policy implementation agent 1690 by employing one or more security elements on one or more access ports into the modem, such as the device bus, an I/O port, a network connection or the debug port.
- the modem can also store and/or execute the policy implementation agent in secure memory.
- the modem can also require a secure download key or a secure software signature to accept any updates to the agent software.
- the service policy implementation agent 1690 of the embodiments of FIG. 19 can be further strengthened against compromise attempts by performing scans of the device 100 code execution environment and/or code storage environment to identify potentially malicious and/or unwanted/untrusted software or hardware. For example, this function can be performed by the policy implementation agent 1690 .
- the agent can have a local database of potentially malicious elements and compare the entries in the database against the elements detected locally using various malicious code, behavior blocking, intrusion detection, and/or other well known techniques for security analysis.
- the agent can communicate a list of some or all of the elements detected locally to the service controller 122 to augment or take the place of the database comparison function that can be performed locally, thereby performing such or further such security analysis on the network (e.g., by the service controller 122 ), and, in some embodiments, if not automatically detected, such elements detected locally (e.g., and/or samples of such detected potentially malicious code or logs of potentially malicious/suspicious behavior/intrusions) forwarded to security analysts for the service provider for further security analysis (e.g., service provider security analysts and/or an outside security vendor engaged to protect the service provider's network and supported devices).
- security analysts e.g., service provider security analysts and/or an outside security vendor engaged to protect the service provider's network and supported devices.
- the agent detects new software downloads, installs and/or invocations and immediately issues an error flag report when potentially malicious software is downloaded, installed or invoked (e.g., file and network based on access security detection techniques).
- the agent scans the local software loading and invocation activity along with a log of other software runtime events and regularly reports this trace so that when an error or compromise event occurs the trace preceding the event can be analyzed to determine the offending software or activity trace that took place to cause the compromise or error. For example, once the software or activity that caused the compromise is known or otherwise detected, it can be entered into a refreshed version of the database that the device and other devices use to detect potentially malicious precursor conditions. Examples of such precursor events can include software invocations, software downloads, a sequence of memory I/O events, a sequence of software access events, a sequence of network address or URL communications or downloads, or a sequence of access modem I/O activity.
- FIG. 20 is another functional diagram illustrating the service processor 115 and the service controller 122 in accordance with some embodiments. As shown in FIG. 20 , the modem firewall 1655 has been removed, and firewall and access control and traffic shaping functions are performed in these embodiments by the policy implementation agent 1690 and application interface agent 1693 .
- FIG. 21 is another functional diagram illustrating the service processor 115 and the service controller 122 in accordance with some embodiments.
- FIG. 21 illustrates the various modem drivers and modems 2122 through 2125 and 2141 .
- the modems which include WWAN modem 2122 , WLAN modem 2123 , WPAN modem 2124 , Ethernet modem 2125 , and Dial/DSL modem 2141 , which are in communication with the modem bus 2120 , connect the device to one or more networks.
- the service measurement points labeled I through VI represent various service measurement points for service monitor agent 1696 and/or other agents to perform various service monitoring activities. Each of these measurement points can have a useful purpose in various embodiments described herein.
- each of the traffic measurement points that is employed in a given design can be used by a monitoring agent to track application layer traffic through the communication stack to assist policy implementation functions, such as the policy implementation agent 1690 , or, in some embodiments, the modem firewall agent 1655 or the application interface agent 1693 , in making a determination regarding the traffic parameters or type once the traffic is farther down in the communication stack where it is sometimes difficult or impossible to make a complete determination of traffic parameters.
- policy implementation functions such as the policy implementation agent 1690 , or, in some embodiments, the modem firewall agent 1655 or the application interface agent 1693 , in making a determination regarding the traffic parameters or type once the traffic is farther down in the communication stack where it is sometimes difficult or impossible to make a complete determination of traffic parameters.
- the present invention does not need to implement any or all of the measurement points illustrated in FIG. 21 to have an effective implementation as was similarly shown with respect to FIG. 19 , various embodiments benefit from these and/or similar measurement points.
- the exact measurement points can be moved to different locations in the traffic processing stack,
- measurement point I occurs at the application interface agent 1693 interface to the applications.
- the application traffic can be monitored before it is framed, packetized or encrypted by the lower layers of the networking stack. For example, this allows inspection, characterization, tagging (literal or virtual) and, in some embodiments, shaping or control of services or traffic.
- traffic can be more readily associated with applications, URLs or IP addresses, content type, service type, and other higher level parameters.
- email traffic and downloads, web browser applications and end points, media file transfers, application traffic demand, URL traffic demand and other such service monitoring parameters are more readily observed (e.g., accessible in the clear without the need for deep packet inspection and/or decryption), recorded and possibly shaped or controlled.
- the downstream delivered traffic can be optimally observed at this measurement point.
- traffic measurement points II and III are situated on the upstream and downstream sides of policy implementation agent 1690 . As described herein, these two locations allow potential tracking of upstream and downstream traffic through the stack portions associated with the policy implementation agent 1690 . These two locations also provide for potential cross-checking of how the policy implementation agent 1690 is impacting the demand and delivery of traffic.
- measurement point III in connection with measurement point IV provide an opportunity for packet tracing through the stack components associated with the modem firewall 1655 and provide for the opportunity to observe the demand and delivery sides of the modem firewall 1655 .
- Traffic measurement point V provides the potential for observing the traffic at the modem bus drivers for each of the modems.
- traffic measurement point VI provides, in some embodiments, the ultimate measure of access traffic, for example, the traffic that actually transacts over the access network through the modem.
- measurement point VI is at the modem side of the internal or external communications bus 1630 , and it will be appreciated that, in some embodiments, this measurement point can be further down the modem stack closer to the MAC or physical layer (e.g., at the designer's discretion).
- An advantage of having a measurement point deep in the modem is, for example, that if the software or hardware that implements the measurement and reporting is well secured against compromise, then this measure can be almost as strong from a verification perspective as the measure that comes from the network (e.g., from the network elements). Accordingly, this makes it possible to compare this measure against the other measures to determine if there is a traffic path that is leaking past the other measurement point or one or more policy implementation points.
- FIG. 22 provides a table summarizing various service processor 115 agents (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments. Many of these agents are similarly described above, and the table shown in FIG. 22 is not intended to be an exhaustive summary of these agents, nor an exhaustive description of all functions that the agents perform or are described herein, but rather FIG. 22 is provided as a summary aid in understanding the basic functions of each agent in accordance with some embodiments and how the agents interact with one another, with the service controller server elements, and/or with other network functions in certain embodiments to form a reliable device based service delivery solution and/or platform.
- FIG. 23 provides a table summarizing various service controller 122 server elements (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments. Many of these agents are similarly described above, and the table shown in FIG. 23 is not intended to be an exhaustive summary of these server elements, nor an exhaustive description of all functions that the elements perform or are described herein, but rather FIG. 23 is provided as a summary aid in understanding the basic functions of each element in accordance with some embodiments and how the elements interact with one another, certain network elements, and/or the service processor agents in certain embodiments to form a reliable device based service delivery solution and/or platform.
- a control plane between the service processor and the service controller using a flexible connection or communication path that, for example, will work between virtually any two network connection endpoints, one being the service controller and one being the device, in a secure yet scalable manner.
- a control plane between the service processor and the service controller using a flexible connection or communication path that, for example, will work between virtually any two network connection endpoints, one being the service controller and one being the device, in a secure yet scalable manner.
- control plane communication channel between the service processor 115 and the service controller 122 .
- Various embodiments described herein disclose a secure and bandwidth efficient control plane that is compatible with any IP based network (including the ability to locate the service controller 122 over the Internet); provides for consistent device assisted service monitoring, control, verification and/or billing while roaming across multiple networks with different access technologies; and allows continuous device assisted service control verification and/or authentication with a variety of mechanisms for setting the transmission heartbeat frequency.
- control plane in the access network control plane channel
- IP or data packet framing mechanisms e.g., IPV6
- IPV6 IP or data packet framing mechanisms
- FIG. 24 is a functional diagram illustrating the service control device link 1691 of the service processor 115 and the service control service link 1638 of the service controller 122 in accordance with some embodiments.
- the service control device link 1691 of the service processor 115 and the service control service link 1638 of the service controller 122 as shown in FIG. 24 provide for secure control plane communication over the service control link 1653 between the service processor 115 and the service controller 122 in accordance with some embodiments.
- Various embodiments include two or three layers of encryption in the service control link, with one embodiment or layer being implemented in the encrypt functions ( 2408 , 2428 ) and decode functions ( 2412 , 2422 ), and another embodiment or layer implemented in the transport services stack ( 2410 , 2420 ).
- An optional third embodiment or layer of encryption is implemented below the transport services stack, for example, with IPSEC or another IP layer encryption, VPN or tunneling scheme.
- various known security encryption techniques can be implemented in the encrypt functions ( 2408 , 2428 ), with public/private or completely private keys and/or signatures so that very strong levels of security for service processor control plane traffic can be achieved even through the basic transport services ( 2410 , 2420 ) implemented with standard secure or open Internet networking protocols, such as TLS or TCP.
- the service processor agent communications local to the device can be conducted to and from the service controller elements via the service control device link 1691 connection to the agent communication bus 1630 .
- the combination of the service control device link 1691 and the agent communication bus 1630 which in some embodiments is also securely encrypted or signed, provides a seamless, highly secure, asynchronous control plane connection between the service processor and service controller server elements and the service controller and service controller agents that works over a wide range of access networks, such as any access network that has the capability to connect IP or TCP traffic to another TCP or IP endpoint on the access network, another private network or over the Internet 120 .
- the agent communication bus 1630 also provides a fourth level of encrypted or signed communication to form a secure closed system on the device for agent to agent communication, for example, making it very difficult or practically impossible for software or applications to gain access to one or more of the a service processor agents on the device in any way other than the service control device link 1691 .
- the agent communication bus 1630 and the service processor agents can only be accessed by one another as necessary or permitted by agent communication policies, or by the service controller or other authorized network function with proper security credentials communicating over the service control device link 1691 .
- communications between a subset of two or more agents, or between one or more agents and one or more service controller server elements are encrypted with unique keys or signatures in such a way that a fourth level of security providing private point to point, point to multipoint, or multipoint to multipoint secure communication lines is provided.
- all of the service control device link 1691 communications are transformed into a continuous control plane connection, with a frequency based on the rate of service usage, a minimum set period between connections, and/or other methods for establishing communication frequency.
- this heartbeat function provides a continuous verification link by which the service controller verifies that the service processor and/or device are operating properly with the correct service policies being implemented.
- the service control device link 1691 includes a heartbeat send counter 2402 in communication with the agent communication bus 1630 .
- the heartbeat send counter 2402 can provide a count for triggering when a service processor 115 communication (e.g., periodic communication based on a heartbeat mechanism) should be sent to the service controller 122 , and a heartbeat buffer 2404 , also in communication with the agent communication bus 1630 , buffers any such information for the next service processor 115 communication, in accordance with various heartbeat based embodiments, as similarly described herein.
- the heartbeat buffer 2404 is in communication with a framing element 2406 and an encrypt element 2408 for framing and encrypting any service processor 115 communications transmitted to the service controller 122 by a transport services stack 2410 over the service control link 1653 .
- the service control server link 1638 includes a heartbeat send counter 2434 in communication with a service controller network 2440 , a heartbeat buffer 2432 , also in communication with the service controller network 2440 , buffers any such information for the next service controller 122 communication, in accordance with various heartbeat based embodiments, as similarly described herein.
- the heartbeat buffer 2432 is in communication with a framing element 2430 and an encrypt element 2428 for framing and encrypting any such service controller 122 communications transmitted to the service processor 115 by a transport services stack 2420 over the service control link 1653 .
- the service control device link 1691 includes a decode element 2412 for decoding any received service controller 122 communications (e.g., decrypting encrypted communications), an unpack element 2414 for unpacking the received service controller 122 communications (e.g., assembling packetized communications), and an agent route 2416 for routing the received service controller 122 communications (e.g., commands, instructions, heartbeat related information or status reports, policy related information or configuration settings and/or updates, challenge/response queries, agent refreshes and/or new software for installation) to the appropriate agent of the service processor 115 .
- a decode element 2412 for decoding any received service controller 122 communications (e.g., decrypting encrypted communications)
- an unpack element 2414 for unpacking the received service controller 122 communications (e.g., assembling packetized communications)
- an agent route 2416 for routing the received service controller 122 communications (e.g., commands, instructions, heartbeat related information or status reports, policy related information or configuration settings and/or updates, challenge/res
- the service control server link 1638 also includes a decode element 2422 for decoding any received service processor 115 communications (e.g., decrypting encrypted communications), an unpack element 2424 for unpacking the received service processor 115 communications (e.g., assembling packetized communications), and an agent route 2426 for routing the received service processor 115 communications (e.g., responses to instructions and/or commands, heartbeat related information or status reports, policy related information or configuration settings and/or updates, challenge/response queries, agent status information, network service/cost usage and/or any other reporting related information) to the appropriate agent of the service controller 122 .
- a decode element 2422 for decoding any received service processor 115 communications (e.g., decrypting encrypted communications), an unpack element 2424 for unpacking the received service processor 115 communications (e.g., assembling packetized communications), and an agent route 2426 for routing the received service processor 115 communications (e.g., responses to instructions and/or commands, heartbeat related information or status reports, policy related information
- the various secure communications between the service controller 122 and the service processor 115 can be performed using the embodiment as shown in FIG. 24 , and those of ordinary skill in the art will also appreciate that a variety of other embodiments can be used to similarly provide the various secure communications between the service controller 122 and the service processor 115 (e.g., using different software and/or hardware architectures to provide secure communications, such as using additional and/or fewer elements/functions or other design choices for providing such secure communications).
- an efficient and effective communication framing structure between the service processor and service controller is provided, and the following embodiments (e.g., as shown and described with respect to FIG. 25 ) teach such a structure that packs the various service processor agent control plane communications and the various service controller element control plane connections into a format that does not consume excessive bandwidth to enable a continuous control plane connection between the device and service controller.
- an efficient and effective communication framing structure between the service processor and service controller is provided to buffer such communication messages for some period of time before framing and transmitting, such as in a heartbeat frequency that is based on rate of service usage.
- an efficient and effective communication framing structure between the service processor and service controller is provided to allow for the frame to be easily packed, encrypted, decoded, unpacked and the messages distributed.
- FIG. 25 is a functional diagram illustrating a framing structure of a service processor communication frame 2502 and a service controller communication frame 2522 in accordance with some embodiments.
- the service control device link 1691 of the service processor 115 and the service control service link 1638 of the service controller 122 (e.g., as shown in FIG. 24 ) provide for secure control plane communication over the service control link 1653 between the service processor 115 and the service controller 122 using communication frames in the format of the service processor communication frame 2502 and the service controller communication frame 2522 as shown in FIG. 25 in accordance with some embodiments.
- the service processor communication frame 2502 includes a service processor framing sequence number 2504 , a time stamp 2506 , an agent first function ID 2508 , an agent first function message length 2510 , an agent first function message 2512 , and assuming more than one message is being transmitted in this frame, an agent Nth function ID 2514 , an agent Nth function message length 2516 , and an agent Nth function message 2518 .
- the service processor communication frame 2502 can include one or more messages as shown in FIG. 25 , which can depend on networking frame length requirements and/or other design choices.
- the service controller communication frame 2522 includes a service controller framing sequence number 2524 , a time stamp 2526 , an agent first function ID 2528 , an agent first function message length 2530 , an agent first function message 2532 , and assuming more than one message is being transmitted in this frame, an agent Nth function ID 2534 , an agent Nth function message length 2536 , and an agent Nth function message 2538 .
- the service controller communication frame 2522 can include one or more messages as shown in FIG. 25 , which can depend on networking frame length requirements and/or other design choices:
- FIGS. 26A through 26E provide tables summarizing various service processor heartbeat functions and parameters (e.g., implemented by various agents, components, and/or functions implemented in software and/or hardware) in accordance with some embodiments. Many of these heartbeat functions and parameters are similarly described above, and the tables shown in FIGS. 26A-E are not intended to be an exhaustive summary of these heartbeat functions and parameters, but rather are provided as an aid in understanding these functions and parameters in accordance with some heartbeat based embodiments described herein.
- FIGS. 27A through 27G provide tables summarizing various device based service policy implementation verification techniques in accordance with some embodiments. Many of these device based service policy implementation verification techniques are similarly described above, and the tables shown in FIGS. 27A-G are not intended to be an exhaustive summary of these device based service policy implementation verification techniques, but rather are provided as an aid in understanding these techniques in accordance with some device based service policy embodiments described herein.
- FIGS. 28A through 28C provide tables summarizing various techniques for protecting the device based service policy from compromise in accordance with some embodiments. Many of these techniques for protecting the device based service policy from compromise are similarly described above, and the tables shown in FIGS. 28A-C are not intended to be an exhaustive summary of these techniques for protecting the device based service policy from compromise, but rather are provided as an aid in understanding these techniques in accordance with some device based service policy embodiments described herein.
- FIG. 29 is a functional diagram illustrating a device communications stack that allows for implementing verifiable traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- several service agents take part in data path operations to achieve various data path improvements, and, for example, several other service agents can manage the policy settings for the data path service, implement billing for the data path service, manage one or more modem selection and settings for access network connection, interface with the user and/or provide service policy implementation verification.
- the service measurement points labeled I through VI represent various service measurement points for service monitor agent 1696 and/or other agents to perform various service monitoring activities. Each of these measurement points can have a useful purpose in various embodiments described herein.
- each of the traffic measurement points that is employed in a given design can be used by a monitoring agent to track application layer traffic through the communication stack to assist policy implementation functions, such as the policy implementation agent 1690 , or in some embodiments the modem firewall agent 1655 or the application interface agent 1693 , in making a determination regarding the traffic parameters or type once the traffic is farther down in the communication stack where it is sometimes difficult or impossible to make a complete determination of traffic parameters.
- policy implementation functions such as the policy implementation agent 1690 , or in some embodiments the modem firewall agent 1655 or the application interface agent 1693 , in making a determination regarding the traffic parameters or type once the traffic is farther down in the communication stack where it is sometimes difficult or impossible to make a complete determination of traffic parameters.
- a detailed set of embodiments describing how the various measurement points can be used to help strengthen the verification of the service control implementation are described herein, including, for example, the embodiments described with respect to FIG. 16 and FIG. 21 .
- one or more measurement points within the device can be used to assist in service control verification and/or device or service troubleshooting.
- the service monitor agent and/or other agents implement virtual traffic tagging by tracking or tracing packet flows through the various communication stack formatting, processing and encryption steps, and providing the virtual tag information to the various agents that monitor, control, shape, throttle or otherwise observe, manipulate or modify the traffic.
- This tagging approach is referred to herein as virtual tagging, because there is not a literal data flow, traffic flow or packet tag that is attached to flows or packets, and the book-keeping to tag the packet is done through tracking or tracing the flow or packet through the stack instead.
- the application interface and/or other agents identify a traffic flow, associate it with a service usage activity and cause a literal tag to be attached to the traffic or packets associated with the activity.
- This tagging approach is referred to herein as literal tagging.
- some standard communication stacks provide for unused, unspecified or otherwise available bit fields in a packet frame or flow, and these unused, unspecified or otherwise available bit fields can be used to literally tag traffic without the need to re-write all of the standard communication stack software, with only the portions of the stack that are added to enhance the verifiable traffic control or service control capabilities of the standard stack needing to decode and use the literal tagging information encapsulated in the available bit fields.
- the tags are removed prior to passing the packets or flows to the network or to the applications utilizing the stack.
- the manner in which the virtual or literal tagging is implemented can be developed into a communication standard specification so that various device or service product developers can independently develop the communication stack and/or service processor hardware and/or software in a manner that is compatible with the service controller specifications and the products of other device or service product developers.
- any or all of the measurement points illustrated in FIG. 29 is not required to have an effective implementation, such as was similarly shown with respect to various embodiments described herein, such as with respect to FIGS. 19 and 21 , various embodiments can benefit from these and/or similar measurement points. It will also be appreciated that the exact measurement points can be moved to different locations in the traffic processing stack, just as the various embodiments described herein can have the agents affecting policy implementation moved to different points in the traffic processing stack while still maintaining effective operation. In some embodiments, one or more measurement points are provided deeper in the modem stack (e.g., such as for embodiments similarly described herein with respect to FIGS. 35 and 36 ) where, for example, it is more difficult to circumvent and can be more difficult to access for tampering purposes if the modem is designed with the proper software and/or hardware security to protect the integrity of the modem stack and measurement point(s).
- the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack.
- Example measurement point VI resides within or just above the modem driver layer: For example, the modem driver performs modem bus communications, data protocol translations, modem control and configuration to interface the networking stack traffic to the modem. As shown, measurement point VI is common to all modem drivers and modems, and it is advantageous for certain embodiments to differentiate the traffic or service activity taking place through one modem from that of one or more of the other modems. In some embodiments, measurement point VI, or another measurement point, is located over, within or below one or more of the individual modem drivers.
- a modem selection & control layer for multimode device based communication is provided.
- this layer is controlled by a network decision policy that selects the most desirable network modem for some or all of the data traffic, and when the most desirable network is not available the policy reverts to the next most desirable network until a connection is established provided that one of the networks is available.
- certain network traffic such as verification, control, redundant or secure traffic, is routed to one of the networks even when some or all of the data traffic is routed to another network. This dual routing capability provides for a variety of enhanced security, enhanced reliability or enhanced manageability devices, services or applications.
- a modem firewall is provided.
- the modem firewall provides for traditional firewall functions, but unlike traditional firewalls, in order to rely on the firewall for verifiable service usage control, such as access control and security protection from unwanted networking traffic or applications, the various service verification techniques and agents described herein are added to the firewall function to verify compliance with service policy and prevent tampering of the service controls.
- the modem firewall is implemented farther up the stack, possibly in combination with other layers as indicated in other Figures.
- a dedicated firewall function or layer is provided that is independent of the other processing layers, such as the policy implementation layer, the packet forwarding layer and/or the application layer.
- the modem firewall is implemented farther down the stack, such as within the modem drivers, below the modem drivers, or in the modem itself.
- Example measurement point IV resides between the modem firewall layer and an IP queuing and routing layer.
- an IP queuing and routing layer is separate from the policy implementation layer where the policy implementation agent implements a portion of the traffic control and/or service usage control policies.
- these functions are separated so that a standard network stack function can be used for IP queuing and routing, and the modifications necessary to implement the policy implementation agent functions can be provided in a new layer inserted into the standard stack.
- the IP queuing and routing layer is combined with the traffic or service usage control layer.
- Measurement point III resides between the IP queuing and routing layer and a policy implementation agent layer.
- Measurement point II resides between the policy implementation agent layer and the transport layer, including TCP, UDP, and other IP as shown.
- the session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- the network services API resides above the session layer.
- Measurement point I resides between the network services API layer and an application layer, shown as application service interface agent in the device communications stack of FIG. 29 .
- the application service interface layer is above the standard networking stack API and, in some embodiments, its function is to monitor and in some cases intercept and process the traffic between the applications and the standard networking stack API.
- the application service interface layer identifies application traffic flows before the application traffic flows are more difficult or practically impossible to identify farther down in the stack.
- the application service interface layer in this way assists application layer tagging in both the virtual and literal tagging cases. In the case of upstream traffic, the application layer tagging is straight forward, because the traffic originates at the application layer.
- the traffic or service activity classification relies on traffic attributes that are readily obtainable, such as source address or URL, application socket address, IP destination address, time of day or any other readily obtained parameter
- the traffic type can be identified and tagged for processing by the firewall agent or another agent as it initially arrives.
- the solution is generally more sophisticated when a traffic parameter that is needed to classify the manner in which the traffic flow is to be controlled or throttled is not readily available at the lower levels of the stack, such as association with an aspect of an application, type of content, something contained within TLS, IPSEC or other secure format, or other information associated with the traffic.
- the networking stack identifies the traffic flow before it is fully characterized, categorized or associated with a service activity, and then passes the traffic through to the application interface layer where the final classification is completed.
- the application interface layer then communicates the traffic flow ID with the proper classification so that after an initial short traffic burst or time period the policy implementation agents can properly control the traffic.
- there is also a policy for tagging and setting service control policies for traffic that cannot be fully identified with all sources of tagging including application layer tagging.
- Various applications and/or a user service interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)).
- the billing agent which is in communication with the agent communication bus 1630 , communicates user information and decision query and/or user input to the user service interface agent, as shown.
- the policy control agent communicates service settings and/or configuration information via this communications bus 1630 , as shown (illustrating such communications with a reference (B) via the application layer, policy implementation agent layer, which is lower in the communications stack as shown, and/or the modem firewall layer).
- the connection manager agent communicates select and control commands and/or modem and access network information via this communications stack, as shown (illustrating such communications with a reference (C) via the modem selection and control layer).
- Various other communications e.g., service processor and/or service controller related communications, such as service usage measure information and/or application information
- service processor and/or service controller related communications such as service usage measure information and/or application information
- these communications are provided at various levels of this communications stack, as shown (illustrating such communications with references (D) at the application layer, (E) at the policy implementation agent layer, and (F) at the modem firewall layer).
- a service monitor agent which is also in communication with the agent communication bus 1630 , communicates with various layers of the device communications stack. For example, the service monitor agent, performs monitoring at each of measurement points I through VI, receiving information including application information, service usage and other service related information, and assignment information.
- An access control integrity agent is in communication with the service monitor agent via the agent communications bus 1630 , as also shown.
- one or more of the networking stack modifications described herein in combination one or more of the service verification and tamper prevention techniques described herein is provided.
- the various example embodiments for assisting service control verification described herein and as summarized in the example tables provided in FIGS. 26 , 27 and 28 can be employed individually or in combination to create increasingly secure cross-functional service control verification embodiments.
- the presence of the access control integrity agent, policy control agent, service monitor agent and the other agents that perform verification and/or tamper prevention functions illustrates verifiable service control aspects in accordance with some embodiments.
- the presence of the billing agent combined with the service verification and/or tamper prevention agents and techniques described herein provides for a set of verifiable billing embodiments for service billing, service billing offset corrections, bill by account, transaction billing and other billing functions.
- the presence of the user service interface agent in combination with the service control agent functions in the modified networking stack provide for embodiments involving a combination of service control with user preferences, which as described herein, provides the user with the capability to optimize service versus service cost in a network neutral manner.
- the user control of service control policy is provided along with the service control verification and/or tamper prevention.
- the presence of the policy control agent that in some embodiments implements a higher than most basic level of policy decision and control with the policy implementation agents in the modified networking stack allows for, for example, the device to possess the capability to implement a higher level of service control for the purpose of obtaining a higher level service usage or service activity objective.
- the application layer tagging in combination with other embodiments described herein provides for deep service activity control that is verifiable.
- verifiable traffic shaping as described herein can be performed using the device communications stack in a variety of embodiments for the combination of service control within the networking stack and service control verification and/or tamper prevention, with various embodiments depicted in FIGS. 29 through 37 . Additional levels of detail regarding how such embodiments can be used to implement verifiable traffic shaping are provided in and described with respect to FIGS. 38 through 40 which depict example functional diagrams of packet processing flows for verifiable traffic shaping or service activity control in a device service processor for both upstream and downstream flows. Along with several other interesting features embodied in FIGS. 38 through 40 , application traffic layer tagging is depicted in additional detail in accordance with some embodiments.
- the application interface agent can determine service data usage at the application layer using measurement point I and a local service usage counter, and can, for example, pass this information to the service monitor agent. If service usage exceeds a threshold, or if using a service usage prediction algorithm results in predicted service usage that will exceed a threshold, then the user can be notified of which applications are causing the service usage overrun or potential service usage overrun, via the user service interface agent. The user can then identify which application service (e.g., traffic associated with a specified high service use or non-critical application, such as for example a high bandwidth consumption social networking website or service, media streaming website or service, or any other high bandwidth website or service transmitting and/or receiving data with the service network) that the user prefers to throttle.
- application service e.g., traffic associated with a specified high service use or non-critical application, such as for example a high bandwidth consumption social networking website or service, media streaming website or service, or any other high bandwidth website or service transmitting and/or receiving data with the service network
- the user could select a service policy that allows for video chat services until those services threaten to cause cost over-runs on the user's service plan, and at that time the service policy could switch the chat service to voice only and not transmit or receive the video.
- the traffic associated with the user specified application can then be throttled according to user preference input. For example, for downstream traffic, packets (e.g., packets that are virtually or literally tagged and/or otherwise associated with the application traffic to be throttled) from the access network can be buffered, delayed and/or dropped to throttle the identified application traffic.
- packets e.g., packets that are virtually or literally tagged and/or otherwise associated with the application traffic to be throttled
- packets can be buffered, delayed and/or dropped before being transmitted to the access network to throttle the identified application traffic.
- traffic shaping as described herein can be verified, such as by the service monitor agent via the various measurement points and/or using other agents.
- the embodiments depicted in FIG. 30 and other figures generally require enhancements to conventional device networking communication stack processing.
- these enhancements can be implemented in whole or in part in the kernel space for the device OS, in whole or in part in the application space for the device, or partially in kernel space and partially in application space.
- the networking stack enhancements and the other elements of the service processor can be packaged into a set of software that is pre-tested or documented to enable device manufacturers to quickly implement and bring to market the service processor functionality in a manner that is compatible with the service controller and the applicable access network(s).
- the service processor software can also be specified in an interoperability standard so that various manufacturers and software developers can develop service processor implementations or enhancements, or service controller implementations or enhancements that are compatible with one another.
- FIG. 30 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- a portion of the service processor is implemented on the modem (e.g., on modem module hardware or modem chipset) and a portion of the service processor is implemented on the device application processor subsystem.
- the modem e.g., on modem module hardware or modem chipset
- the service processor is implemented on the device application processor subsystem.
- the service processor can be distributed as a standard feature set contained in a modem chipset hardware of software package or modem module hardware or software package, and such a configuration can provide for easier adoption or development by device OEMs, a higher level of differentiation for the chipset or modem module manufacturer, higher levels of performance or service usage control implementation integrity or security, specification or interoperability standardization, and/or other benefits.
- the device communications stack provides a communication layer for modem MAC/PHY layer at the bottom of the device communications stack.
- Measurement point IV resides above the modem MAC/PHY layer.
- the modem firewall layer resides between measurement points IV and III.
- the policy implementation agent is provided, in which the policy implementation agent is implemented on the modem (e.g., on modem hardware).
- Measurement point II resides between the policy implementation agent and the modem driver layer, which is then shown below a modem bus layer.
- the next higher layer is shown as the IP queuing and routing layer, followed by the transport layer, including TCP, UDP, and other IP as shown.
- the session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- Measurement point I resides between the network services API layer and an application layer, shown as application service interface agent in the device communications stack of FIG. 30 .
- Various applications and/or a user service,interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)).
- the billing agent which is in communication with the agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown.
- the policy control agent B communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (B)) via the application layer.
- the policy control agent A communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (D)) via the policy implementation agent layer and/or the modem firewall layer.
- connection manager agent communicates select & control commands and/or modem and access network information via this communications stack, as shown (illustrating such communications with a reference (C)) via the modem driver layer.
- Various other communications e.g., service processor and/or service controller related communications, such as service usage measure information, and/or application information
- communications with references (E)) are provided at various levels of this communications stack, as shown (illustrating such communications with references (E)) at the application layer through the modem driver layer with the service monitor agent B as shown (and an access control integrity agent B is also shown), and communications with references (F) at the policy implementation agent layer and (G) at the modem firewall layer with the service monitor agent A as shown (and an access control integrity agent A is also shown).
- the service usage policy verification or tamper prevention embodiments described herein can be applied, in isolation or in combination, in the context of FIG. 31 to provide for embodiments with increasing levels of service usage policy control verification certainty, such as provided with FIGS. 26 , 27 and 28 .
- FIG. 31 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- the service processor is a simplified implementation. For example, this approach can be used for applications with less capable device application processors, rapid time to market needs, fewer service usage control needs, and/or other reasons that lead to a need for a lower complexity implementation.
- the device communications stack provides a communication layer for the modem layer at the bottom of the device communications stack.
- the modem driver layer resides above the modem bus layer as shown.
- the policy implementation agent is provided, and the policy implementation agent is also in communication with the agent communication bus 1630 as shown.
- the next higher layer is shown as the transport layer, including TCP, UDP, and other IP as shown.
- the session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- Applications communicate with the device communications stack via the network services API as shown.
- Policy settings from the network e.g., service settings
- the connection manager communicates select and control as well as modem and access network information via the modem driver as shown.
- FIG. 31 does not depict all of the service usage control verification functions provided by certain embodiments calling for additional service verification or control agents, a high level of service policy implementation verification certainty can be achieved within the context of the embodiments depicted in FIG. 31 by applying a subset of the service usage policy verification or tamper prevention embodiments described herein.
- the embodiments depicted in FIG. 31 can be combined with the service controller embodiments that utilize IPDRs to verify service usage is in accordance with the desired service policy.
- FIG. 32 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- the service processor is a simplified implementation embodiment with device based monitoring and integrity control.
- FIG. 32 provides for somewhat higher complexity (e.g., relative to the embodiments depicted in FIG. 30 ) in exchange for the enhanced service monitoring, control or verification that are possible by implement additional agent embodiments, such as the service monitor agent and the access control integrity agent functions.
- the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack.
- Measurement point II resides above the modem selection & control layer, which resides above the modem buses for each modem.
- Measurement point I resides between the policy implementation agent (policy based router/firewall) layer and the transport layer, including TCP, UDP, and other IP as shown.
- the session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- Applications communicate with the device communications stack via the network services API as shown.
- Policy settings from the network e.g., service settings
- the connection manager communicates select and control as well as modem and access network information via the modem selection and control layer as shown.
- the service monitor agent which is also in communication with the agent communication bus 1630 , communicates with various layers of the device communications stack. For example, the service monitor agent, performs monitoring at each of measurement points I and II, receiving information including application information, service usage and other service related information, and assignment information.
- An access control integrity agent is in communication with the service monitor agent via the agent communications bus 1630 , as also shown. As similarly described with respect to FIGS. 30 and 31 , many of the service usage control verification embodiments described herein can be applied in isolation or in combination in the context of FIG. 32 .
- FIG. 33 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack.
- Measurement point III resides above the modem selection & control layer, which resides above the respective modem buses for each modem.
- Measurement point II resides between the policy implementation agent (policy based router/firewall) layer and the transport layer, including TCP, UDP, and other IP as shown.
- the session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- Measurement point I resides between the network services API layer and an application layer, shown as application service interface agent in the device communications stack of FIG. 33 .
- Various applications and/or a user service interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)).
- the billing agent which is in communication with the agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown.
- the policy control agent communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (B)) via the policy implementation agent layer.
- the connection manager agent communicates select & control commands and/or modem and access network information via this communications stack, as shown (illustrating such communications with a reference (C)) via the modem selection and control layer.
- Various other communications e.g., service processor and/or service controller related communications, such as service usage measure information, application information
- service processor and/or service controller related communications such as service usage measure information, application information
- a service monitor agent which is also in communication with the agent communication bus 1630 , communicates with various layers of the device communications stack. For example, the service monitor agent, performs monitoring at each of measurement points I through III, receiving information including application information, service usage and other service related information, and assignment information.
- An access control integrity agent is in communication with the service monitor agent via the agent communications bus 1630 , as also shown.
- many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context of FIG. 33 .
- FIG. 34 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- the data path processing for the service processor is provided in conjunction with a single modem driver as shown.
- the service processor communication stack processing is provided below the standard network communication stack and in combination with a modem driver (e.g., and this approach can be extended to more than one modem).
- the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack.
- Measurement point II resides above the modem driver 1 layer.
- Measurement point I resides between the policy implementation agent (policy based router/firewall) layer and the modem selection and control layer, for the modem driver 1 stack in this single modem driver embodiment.
- the transport layer including TCP, UDP, and other IP resides above the IP queuing and routing layer, which resides above the modem selection and control layer, as shown.
- the session layer which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer, resides above the transport layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- HTTP HyperText Transfer Protocol
- HTTPS HyperText Transfer Protocol
- FTP File Transfer Protocol
- SMTP Simple Mail Transfer Protocol
- POP3, DNS resides above the session layer.
- applications communicate with the device communications stack via the network services API as shown (illustrating such communications with a reference (A)).
- Policy settings from the network e.g., service settings
- the policy implementation agent as shown (illustrating such communications with a reference (B)).
- the service monitor agent which is also in communication with the agent communication bus 1630 , communicates with policy implementation agent layer of the device communications stack. Also, the service monitor agent performs monitoring at each of measurement points I and II, receiving information including application information, service usage and other service related information, and assignment information.
- An access control integrity agent is in communication with the service monitor agent via the agent communications bus 1630 , as also shown.
- Various other communications e.g., service processor and/or service controller related communications, such as service usage measure information, application information
- these communications are provided at various levels of this communications stack, as shown (illustrating such communications with references (C)) at the policy implementation agent layer.
- the billing agent which is in communication with the agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown.
- many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context of FIG. 34 .
- FIG. 35 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 35 illustrates a single modem hardware embodiment as shown.
- the service processor network communication stack processing is provided on the modem hardware (e.g., and this approach can be extended to more than one modem).
- This approach allows for the service processor to be distributed as a standard feature set contained in a modem chipset hardware of software package or modem module hardware or software package, which, for example, can provide for easier adoption or development by device OEMs, a higher level of differentiation for the chipset or modem module manufacturer, higher levels of performance or service usage control implementation integrity, or other benefits.
- the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack.
- measurement points I and II and the policy implementation agent reside on the modem 1 (e.g., implemented as hardware and/or software on modem 1 ).
- Measurement point I resides above the policy implementation agent (policy based router/firewall) layer, and measurement point II resides below the policy implementation agent later.
- the modem selection and control layer resides above the modem drivers layer, as shown.
- the transport layer, including TCP, UDP, and other IP resides above the IP queuing and routing layer, which resides above the modem selection and control layer, as shown.
- the session layer which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer, resides above the transport layer.
- the network services API e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS
- HTTP HyperText Transfer Protocol
- HTTPS HyperText Transfer Protocol
- FTP File Transfer Protocol
- SMTP Simple Mail Transfer Protocol
- POP3, DNS resides above the session layer.
- applications communicate with the device communications stack via the network services API as shown.
- Policy settings from the network e.g., service settings
- the service monitor agent which is also in communication with the agent communication bus 1630 , communicates with policy implementation agent layer of the modem 1 . Also, the service monitor agent performs monitoring at each of measurement points I and II, receiving information including application information, service usage and other service related information, and assignment information.
- An access control integrity agent is in communication with the service monitor agent via the agent communications bus 1630 , as also shown.
- FIG. 36 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 36 illustrates a single modem hardware embodiment, in which modem 1 includes a portion of the service processor networking communication stack processing and measurement points II and III and the policy implementation agent, as similarly shown in FIG. 35 , and the higher levels of the device communications stack above the modem 1 layer, such as the application service interface layer, are implemented on the device application processor or in the device application processor memory as similarly described above, for example, with respect to FIG. 33 , in which a measurement point I is shown between the application service interface agent layer and the network services API layer.
- this approach allows for the application service interface agent to be provided on the device application processor or memory so that application layer service usage monitoring or control can be implemented.
- the differences between the embodiments depicted in FIG. 36 and those of FIG. 30 include a simplified implementation and a policy control agent that is entirely implemented on the modem and not partially implemented in the application processor memory.
- Various applications and/or a user service interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)).
- the billing agent which is in communication with the agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown.
- the policy control agent communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (B)) via the policy implementation agent layer.
- Various other communications e.g., service processor and/or service controller related communications, such as service usage measure information and/or application information
- C communications with reference
- D communications with reference
- the service monitor agent B communicates with the application service interface agent and measurement point I
- the service monitor agent A communicates with the policy implementation agent layer and measurement points II and III of the modem 1 .
- many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context of FIG. 36 .
- FIG. 37 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments.
- FIG. 37 illustrates a device communications stack as similarly shown in FIG. 36 , with the difference being that the service processor subsystem networking communication stack processing is implemented on a hardware function that is separate from the application processor and the modem.
- this approach provides security advantages with a dedicated hardware system to protect some or all of the service usage control system from tampering.
- some or all of the service processor can be implemented on a SIM card module.
- some or all of the service processor can be encapsulated on a self contained hardware module that can be added to a device without the need to modify the networking communication stack software or hardware.
- FIG. 38 is a functional diagram illustrating a device service processor packet processing flow in accordance with some embodiments.
- both an example upstream service processor packet processing flow (device to the network) and an example downstream service processor packet processing flow (network to the device) are shown in FIG. 38 .
- the service processor packet processing flow can be performed by the device communications stack, such as described above with respect to FIG. 29 .
- the various embodiments for packet processing flow depicted in FIGS. 38 through 40 are self explanatory to one of ordinary skill in the art and not all the processing steps and flow sequences are described herein.
- the burst size, buffer delay, acknowledgement delay and drop rate used in upstream and downstream traffic shaping are optimized with the goal of reducing access network traffic overhead, and excess capacity usage that can result from mismatches in traffic transmission parameters with the access network MAC and PHY or from excess network level packet delivery protocol re-transmissions.
- an application interface agent 1693 is used to literally tag or virtually tag application layer traffic so that the policy implementation agent(s) 1690 has the necessary information to implement selected traffic shaping solutions. As shown in FIG. 16 , the application interface agent 1693 is in communication with various applications, including a TCP application 1604 , an IP application 1605 , and a voice application 1602 .
- the upstream traffic service policy implementation step corresponds to the traffic shaping step described herein.
- this step is depicted as shown as an alternate exploded view including four upstream sub-steps of apply QoS queue priority, apply traffic shaping rules, network optimized buffer/delay and remove application ID tag.
- An additional approach shown in FIG. 38 involves two exploded view sub-steps associated with the firewall service policy implementation step and these sub-steps are pass/block packet and pass/redirect packet.
- the functions performed by these six sub-steps can be depicted in any number of sub-steps, the order of the steps can be appropriately performed in various different orders to provide for upstream traffic shaping within the network communication stack.
- 39 and 40 show the two steps of policy implementation and firewall as one step and the six exploded view sub-steps are included under the same policy implementation step and are performed in a different order than in FIG. 38 . It should also be noted that a number of embodiments are possible in which the access control, traffic control or firewall functions are moved to the application service interface layer or another layer.
- the number of sub-steps, the order of sub-steps and the location of the sub-steps in the downstream networking stack processing can be depicted in any number of sub-steps, order and/or location, and various other embodiments will be apparent to one of ordinary skill in the art, including embodiments which locate some or all of the steps in the application service interface layer or other layers as depicted in FIGS. 39 and 40 .
- the details of the packet flow processing design for the downstream can be somewhat more complex in certain embodiments as compared to the upstream processing in two ways.
- the packet tagging that requires application level information can require the initial portion of the packet flow burst to pass through the upstream networking communication stack until the application service interface layer can associate the packet flow with the appropriate information visible at the application level at which time the packet flow tag is communicated to the other service processor agent functions so that they can properly monitor or control the traffic associated with the flow.
- TCP upper layer reliable communication protocols
- ACK packet receipt acknowledge
- the packet traffic control parameters (e.g., downstream delay, drops, burst length, burst frequency and/or burst jitter) are optimized for TCP re-transmission efficiency so that changes in traffic control access bandwidth or speed for one or more service activities are implemented in such a manner that the TCP re-transmission delay at the network transmitting end adapts to be long enough so that wasted packet re-transmission bandwidth is reduced.
- the packet traffic control parameters e.g., downstream delay, drops, burst length, burst frequency and/or burst jitter
- the packet traffic control parameters can be adjusted so that the access network downstream MAC and/or PHY efficiencies are optimized.
- traffic shaping is performed in a verifiable manner
- traffic shaping is performed in a manner that results in improved network capacity by taking into account to some degree the manner in which the access network PHY layer and/or MAC layer responds to packet parameters (e.g.
- traffic shaping is performed in a manner that results in improved network capacity by taking into account how the packet parameters (e.g., burst delay, burst drops, burst length, burst frequency and/or burst jitter) impact layer 3 and higher ACK protocol or other network protocol network capacity efficiencies
- packet shaping is performed in a manner that is aware of and optimized for the particular type of communication protocol or packets being sent (e.g., TCP packets can be dropped to slow the application rate of transfer whereas UDP packets are never dropped, because there is no re-transmission)
- E a virtual or literal packet tagging system is used in a verifiable traffic shaping service control system to provide a deeper level of service monitoring and control or to simplify the processing of the packets, and/or (F) starting with these low level packet processing, traffic control or access control building blocks one or more additional layers of higher level policy control can
- FIG. 39 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments.
- both an example upstream service processor packet processing flow (device to the network) and an example downstream service processor packet processing flow (network to the device) are shown in FIG. 39 (e.g., of a less feature rich device service processor embodiment, such as one similar to that depicted in FIG. 32 ).
- FIG. 40 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments.
- FIG. 41 provides a table summarizing various privacy levels for service history reporting in accordance with some embodiments. Many of these privacy levels are similarly described above, and the table shown in FIG. 41 is not intended to be an exhaustive summary of these privacy levels, but rather is provided as an aid in understanding these privacy levels in accordance with user privacy related embodiments described herein. For example, there are many other parameters that can be associated with privacy filtering, and as will be apparent to one of ordinary skill in the art in view of the various embodiments described herein, the unique feature of user defined or user influenced privacy filtering for service usage, service activity or CRM reports can be implemented with a variety of embodiments that are variations of those described herein.
- FIGS. 42A through 42F provide tables summarizing various service policy control commands in accordance with some embodiments. Many of these service policy control commands are similarly described above, and the tables shown in FIGS. 42A-F are not intended to be an exhaustive summary of these service policy control commands and do not include summaries of all the embodiments described herein, but rather are provided as a summary aid in understanding these service policy control commands in accordance with various embodiments described herein.
- QoS is employed for devices with a service processor 115 .
- QoS can be employed in a crowded hot spot where the service processor 115 profile has been changed from WWAN to WLAN, but the WLAN is backed up as too many users are trying to use it.
- the service processor 115 can have a hierarchical access to the hotspot at that point; or the service processor 115 that pays less can be throttled while those that pay more are opened up; or the service processor 115 can initiate a policy that slows down transmissions to improve trunking efficiency.
- FIGS. 43A through 43B are flow diagrams illustrating a flow diagram for a service processor authorization sequence as shown in FIG. 43A and a flow diagram for a service controller authorization sequence as shown in FIG. 43B in accordance with some embodiments.
- the device is in an offline state.
- the service processor e.g., service processor 115
- the service processor of the device collects device service processor credentials and access control integrity information.
- the service processor of the device selects a best network.
- the device connects to an access network.
- the service processor of the device sends an authorization request to the service controller (e.g., service controller 122 ) and also sends the credentials and access control integrity information.
- the service processor determines whether an integrity error has occurred. If so, then the service processor performs integrity error handling at 4314 . Otherwise, the service processor determines whether the device is activated and/or authorized for network access at 4316 .
- the service processor performs a device activation sequence at 4318 .
- the service processor performs the following: updates critical software, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, and sends stored CRM and billing information.
- the device is in an online state.
- device control is in an offline state.
- the service controller e.g., service controller 122
- receives a device authorization request verifies device service plan standing, verifies device access control integrity standing, verifies device access control integrity information, verifies service processor heartbeat, and performs various additional service processor integrity checks (e.g., as similarly described herein).
- the service controller determines whether the device integrity checks have all passed. If not, then the service controller sends an integrity error to the service processor (e.g., service processor 115 ) at 4338 .
- the service controller performs integrity error handling.
- the service controller determines whether the device is activated at 4342 . If not, then the service controller sends an activation message to the service processor at 4344 . At 4346 , the service controller performs a service activation sequence. Otherwise (the device is activated), the service controller sends an authorization at 4348 .
- the service controller performs the following: updates critical software on the service processor, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, sends stored CRM and billing information.
- the service controller is in a device online state.
- FIGS. 44A through 44B are flow diagrams illustrating a flow diagram for a service processor activation sequence as shown in FIG. 44A and a flow diagram for a service controller activation sequence as shown in FIG. 44B in accordance with some embodiments.
- a service processor activation sequence is initiated.
- the service processor e.g., service processor 115
- the service processor displays an activation site (e.g., HTTP site, WAP site or portal) to the user for the user's service activation choice.
- the user selects service plan, billing information and CRM information.
- the service processor sends an activation request and user billing and CRM information to, for example, the service controller.
- the service processor determines whether there is an integrity error. If so, then the service processor performs integrity error handling at 4412 . Otherwise, the service processor determines whether there has been a selection input error at 4414 .
- the service processor displays the selection input error to the user at 4416 and returns to the activation site/portal at 4404 . Otherwise, the service processor identifies the activated service plan at 4418 .
- the service processor performs the following: updates critical software, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, and sends stored CRM and billing information.
- the device is in an online and activated state.
- a service controller activation sequence is initiated.
- the service controller e.g., service controller 122
- receives an activation request including user billing and CRM information, and sends such to central billing.
- the service controller receives a response from central billing.
- the service controller verifies the integrity of the service processor. If an integrity error is detected, then an integrity error is sent at 4440 .
- the service controller performs integrity error handling.
- the service controller determines whether the service plan has been activated. If not, then the service controller sends a selection input error to the device at 4446 and returns to 4432 .
- the service controller sends the service plan activation information to the device at 4448 .
- the service controller performs the following: updates critical software, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, and sends stored CRM and billing information.
- the service controller is in a device online and activated state.
- FIGS. 45A through 45B are flow diagrams illustrating a flow diagram for a service processor access control sequence as shown in FIG. 45A and a flow diagram for a service controller access control sequence as shown in FIG. 45B in accordance with some embodiments.
- the device is in an online state.
- the service processor e.g., service processor 115
- the service processor processes any new heartbeat messages received from the service controller (e.g., service controller 122 ).
- the service processor updates software if necessary, updates service policy and control settings if necessary, synchronizes service counters, updates service cost data if necessary, and updates CRM rules if necessary.
- the service processor performs access control integrity checks.
- the service processor determines whether there are any access control integrity errors. If so, then the service processor performs integrity error handling at 4512 .
- the service processor updates user service UI gauges, provides notification if necessary, and accepts input if available at 4514 .
- the service processor sends new service processor heartbeat messages to the heartbeat message queue.
- the service processor processes any pending billing transactions.
- the service processor determines if a heartbeat transmission is due, and if not, returns to 4504 for processing any received heartbeat messages. If so, at 4522 , the service processor sends the new service processor heartbeat message to the service controller.
- the device is in an online state.
- the service controller e.g., service controller 122
- the service controller processes any new heartbeat messages received from the service processor.
- the service controller performs access control integrity checks.
- the service controller determines whether there are any access control integrity errors. If so, then the service controller performs integrity error handling at 4540 .
- the service controller updates the billing database, updates the CRM information, synchronizes service counters, updates cost database if needed, and synchronizes CRM rules if necessary.
- the service controller processes any pending billing transactions.
- the service controller sends new service processor heartbeat messages to the heartbeat message queue.
- the service controller determines if a heartbeat transmission is due, and if not, returns to 4534 for processing any received heartbeat messages. If so, at 4550 , the service controller sends new service processor heartbeat message to the service processor.
- device information can be embedded in HTTP, WAP or other portal browser/network header request information that indicates a central billing option is available to a compatible third party transaction server, as further described below with respect to FIGS. 46 and 47 A-B.
- FIG. 46 is a functional diagram illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments.
- a service processor 4615 of the device 100 e.g., any mobile device capable of storing and executing the service processor 4615
- an application 4604 e.g., an HTML/WAP web browser
- a mobile payment agent 4699 are also included in the device, such as part of the service processor 4615 as shown.
- the application 4604 is not integrated as part of the service processor 4615 , but is executing and/or stored on the device.
- the mobile payment agent 4699 includes billing agent 1695 , user interface 1697 and/or application interface agent 1693 , and/or various other functional components/agents.
- the service processor 4615 is in communication with a carrier access network 4610 , which is in network communication with the Internet 120 .
- device information can be embedded in HTTP, WAP or other portal browser/network header request information that indicates a central billing option is available to a compatible third party transaction server, such as the open content transaction partner site(s) 134 .
- the compatible transaction server can then send a signed confirmation request over a pre-assigned control socket channel to the billing agent 1695 with the billing agent 1695 confirming the signed confirmation request by either performing the signature check locally based on a stored and synchronized list of approved transaction servers or by passing the signed request onto a billing server 4630 for confirmation.
- a triangle confirmation can be set up in which the billing server 4630 can confirm the transaction set up with the transaction server 134 or the transaction server 134 can confirm the transaction set up with the billing server 4630 .
- the device/transaction server pair can then optionally further exchange keys for the remainder of the transaction for enhanced security.
- the transaction server 134 can also redirect the user browsing experience to one tailored to one or more of device type, service provider, device manufacturer or user. When the user selects a transaction, the transaction server sends the billing agent 1695 a transaction bill that describes the transaction and the amount.
- the billing agent 1695 can optionally confirm that the user account has sufficient credit limit to make the purchase by either confirming the stored credit limit on the device or querying the billing server 4630 .
- the billing agent 1695 then invokes the device UI 1697 to display the transaction description and amount and request user approval for the billing to be conducted through the central billing option.
- User approval can be acquired, for example, by a simple click operation or require a secure password, key and/or biometric response from the user.
- the billing agent 1695 Upon user approval, the billing agent 1695 generates a billing approval and sends it to the transaction server 134 , the transaction server 134 completes the transaction and then sends a bill to the billing agent 1695 .
- the billing agent 1695 optionally sends a confirmation to the transaction server 134 and sends the bill to the billing server 4630 .
- a triangle confirmation can be formed by the billing server sending a confirmation to the transaction server 134 , or the transaction server 134 can send the bill to the billing server 4630 .
- the billing server 4630 can also communication such billed transactions to a central provider billing system 4623 via the carrier access network 4610 .
- an alternate location billing server 4632 is in communication via the Internet 120
- an alternate location central provider billing system 4625 is also in communication via the Internet 120 .
- FIGS. 47A through 47B are transactional diagrams illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments.
- the device application 4604 browses (e.g., based on the user submitting a browse request using a browser application) to transaction server 134 (e.g., a transaction web server, such as the open content transaction partner site 134 ).
- the transaction server 134 provides an offer to the device application 4604 .
- the device application 4604 selects a purchase (e.g., based on the user's selection input).
- the transaction server 134 seeks an API connection with the device mobile payment agent 4699 , which then confirms the API connection.
- the transaction server 134 requests user purchase confirmation (mediated by the device mobile agent 4699 as shown), and the purchase is confirmed by the device application 4604 (e.g., based on the user's acknowledgement as similarly described above with respect to FIG. 46 ).
- the transaction server 134 then transmits a purchase receipt, and the device application 4604 confirms the receipt.
- the transaction server 134 then transmits the purchase bill to the device mobile payment agent 4699 , which then sends the purchase bill to the device billing server (e.g., billing server 4630 ).
- the transaction server also optionally sends a confirmation of the purchase bill to the device billing server for a triangle confirmation, as similarly described above with respect to FIG. 46 .
- the device billing server sends a copy of the purchase bill to the central provider billing system (e.g., central provider billing system 4623 ).
- the device application 4604 browses (e.g., based on the user submitting a browse request using a browser application) to transaction server 134 (e.g., a transaction web server, such as the open content transaction partner site 134 ), in which the browse request includes device ID information, such as similarly described above with respect to FIG. 46 .
- the transaction server 134 establishes API contact with the device mobile agent 4699 , which then confirms contact and good standing for transactional purchases from the device.
- the transaction server 134 provides an offer to the device application 4604 .
- the device application 4604 selects a purchase (e.g., based on the user's selection input).
- the transaction server 134 notifies the device mobile payment agent 4699 of the purchase description and amount, and the device mobile payment agent 4699 then requests user purchase confirmation.
- the purchase is confirmed by the device application 4604 (e.g., based on the user's acknowledgement as similarly described above with respect to FIG. 46 ), and the device mobile payment agent 4699 then transmits a purchase confirmation to the transaction server 134 .
- the transaction server 134 then transmits a purchase receipt, and the device application 4604 confirms the receipt.
- the transaction server 134 then transmits the purchase bill to the device mobile payment agent 4699 , which then sends the purchase bill to the device billing server (e.g., billing server 4630 ).
- the device billing server e.g., billing server 4630
- the transaction server also optionally sends a confirmation of the purchase bill to the device billing server for a triangle confirmation, as similarly described above with respect to FIG. 46 .
- the device billing server sends the purchase bill to the central provider billing system (e.g., central provider billing system 4623 ).
- the communications described above with respect to FIGS. 47A-B with the billing server and the central provider billing system are with the alternate location billing server 4632 and/or alternate location central provider billing system 4625 via the Internet 120 .
- the transaction servers 134 are connected to the Internet 120 .
- these transaction billing embodiments do not require centralized content storage or content and transaction exchange infrastructure.
- the transactions can be conducted over the Internet, and the user experience and content can be tailored versions of the transaction server/content provider's normal experience and content.
- This approach provides for a much wider array of content and transaction partners with minimal or no need to accommodate proprietary specialized systems.
- the compatibility between the device billing agent transaction system and the transaction provider server is easily established, for example, by writing specifications for the header information transmitted by the device and for the secure handshake and signed message transactions that take place between the device billing agent, the transaction server and optionally the transaction server and the billing server.
- the service provider can place the transaction partner on the compatible and approved list and exchange security keys and/or certificates. If a common user experience is desired by the service provider across multiple transaction partners, then the experience specifications for the browser redirects can also be specified in the compatibility specification and tested before the transaction partner gains approval.
- FIG. 48 illustrates a network architecture including a service controller device control system and a service controller analysis and management system in accordance with some embodiments.
- the RAN gateway 410 generally represents the functionality of the various specific RAN gateway functional elements shown and/or discussed herein.
- these RAN gateway 410 functional elements represent the gateways used to aggregate the radio access network traffic, control, charging and roaming functions and/or other functions and are shown and/or discussed herein using other terminology specific to certain industry standards, including SGSN gateway 410 and gateways 508 , 512 , 608 , 612 , 708 and 712 .
- the RAN gateway 410 represents any or all of the RAN gateway functional elements 410 , 508 , 512 , 608 , 612 , 708 , 712 or any other similar industry equipment or functions depending on the embodiment.
- transport gateway 420 represents the next higher level of gateway aggregation for the transport layer that is used in many networks, and this term transport gateway 420 can be interchanged with any or all of the gateways 420 , 520 , 620 , 720 or any other similar industry equipment or functions depending on the embodiment.
- gateway description applies to a respective embodiment in which the terms RAN gateway 410 , gateway 410 , transport gateway 420 or gateway 420 are referenced herein.
- the service controller is divided into two main functions (e.g., as compared with the embodiments of service controller 122 depicted in FIG. 16 ): (1) a service controller device control system 4825 and (2) a service controller design, policy analysis, definition, test, publishing system 4835 .
- the service controller device control system 4825 performs the device service control channel functions as previously described herein with respect to various embodiments.
- the service controller design, policy analysis, definition, test, publishing system 4835 separates out the service analysis, control policy design and publishing from the device service control channel functions.
- the service controller design, policy analysis, definition, test, publishing system 4835 performs a variety of functions as described below.
- the service controller design, policy analysis, definition, test, publishing system 4835 provides service usage statistical analysis, notification policy or procedure response analysis and/or billing policy or procedure response analysis for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- the service controller design, policy analysis, definition, test, publishing system 4835 detects, singles out and reports device service usage, notification responses or billing behavior that is outside of expected limits but may or may not be violating policy.
- the service controller design, policy analysis, definition, test, publishing system 4835 provides service cost and profitability analysis for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- the service controller design, policy analysis, definition, test, publishing system 4835 provides user service control policy, notification policy or billing policy statistical satisfaction analysis for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- the service controller design, policy analysis, definition, test, publishing system 4835 provides statistical take rate analysis for transaction offers and billing offers for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- the service controller design, policy analysis, definition, test, publishing system 4835 provides service control policy definition work screens and “dry-lab” (pre-beta) testing against usage database for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- the service controller design, policy analysis, definition, test, publishing system 4835 provides service control policy, notification policy and/or billing policy beta testing (e.g., using beta test server 1658 ) in which the beta test profile is published to a subset of users or devices.
- beta devices/users may or may not know that the service policy is being tested with them.
- beta test apparatus includes offering system that provides user options to accept beta test and provide feedback in exchange for an offer (e.g., show them an offer page that comes up with their existing subscription service or ambient service—offer a free trial, a discount to something and/or reward zone points (or other incentives/rewards) if they accept the trial).
- a beta test workstation e.g., in communication with the beta test server 1658 , such as VSP remote workstation 4920 as shown in FIG. 49 ) allows the beta test manager to define one or more beta test service policy, notification policy and/or billing policy control profiles.
- the beta test workstation publishes each profile to specific individual (single) devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- the beta test workstation allows the beta test manager to analyze usage statistics, notification response statistics and/or billing/transaction offer response statistics for devices, users, groups of devices or groups of users and compare actual real-time usage versus beta test usage goals.
- the beta test workstation allows the beta test manager to fine tune service, notification and/or billing/transaction policies and re-publish to observe changes to actual service usage until the service policy and/or notification control policies achieve the desired result.
- the beta test workstation also allows the beta test manager to collect direct user feedback to a set of pre-designed user satisfaction or other questions regarding service usage. For example, questions can be presented through a pre-designed beta test portal or through a series of brief pop-ups that come up when the user initiates a particular action or at a particular time.
- the beta test workstation also collects details of service and device usage (e.g., CRM data) that the beta test users have approved for collection.
- the beta test workstation can decompose this data to determine if the users are using the service in the manner intended by the beta test goals.
- the beta test workstation also allows for publishing multiple variants of the service and/or notification policy control settings and compare the service usage for each group with convenient screens with information displays (e.g., statistical usage versus time of day, usage of particular activities, billing activity, device discovery activity, user response to notification message and options, user satisfaction with a particular notification policy or billing policy or traffic control policy).
- the screens can be designed by the beta test manager.
- the service download control server 1660 has a workstation screen that allows the service manager to specify which group of devices are to receive the new service policy configuration.
- the service download control server 1660 allows the service manager to define specific individual (single) devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service.
- a service (e.g., a newly created or new version of an existing service) is tested and/or enhanced using a new service testing model.
- a new service (or a new version of an existing service) is loaded onto a server for testing, the new service is (optionally) tested against existing device usage statistics, a new service control definition (e.g., implemented as service processor 115 for publishing to devices 100 and a corresponding new service controller 122 for the service provider, such as a central provider or an MVNO partner, and, for example, the new service processor and service controller can be implemented using the below described SDK) for the new service is developed and possibly adjusted based on the testing against existing device usage statistics, the new service control definition is then published to beta devices (e.g., various devices 100 used for beta testing the new service), which then use the new service, service usage statistics and/or user feedback statistics are then collected (e.g., to ensure that the service is functioning properly and so that the service control definition can be tuned to ensure adequate service, user experience and for
- beta devices
- the service control definition can be published to specified groups of devices for using the new service.
- this service control testing model for groups of devices and service partners is provided by a virtual MVNO or VSP. For example, this allows for new services to be more efficiently and more effectively developed, tested and proliferated.
- service history IPDRs come from within a networking component connected to the central provider core network 110 as depicted by (e.g., real-time) service usage 118 (which as discussed elsewhere is a general purpose descriptor for a function located in one or more of the networking equipment boxes).
- service history IPDRs are collected/aggregated (in part) from the central billing system 123 .
- service history IPDRs are collected/aggregated (in part) from the transport gateways 420 .
- service history IPDRs are collected/aggregated (in part) from the RAN gateways 410 .
- service history IPDRs are collected/aggregated (in part) from the base station(s) 125 or a networking component co-located with the base station(s) 125 , a networking component in the transport network 415 , a networking component in the core network 110 or from another source.
- VSP virtual service provider
- VSP capabilities include making available to a third party service partner one or more of the following: (1) device group definition, control and security, (2) provisioning definition and execution, (3) ATS activation owner, (4) service profile definitions, (5) activation and ambient service definition, (6) billing rules definition, (7) billing process and branding controls, (8) bill by account settings, (9) service usage analysis capabilities by device, sub-group or group, (10) beta test publishing capabilities by device, sub-group or group, and (11) production publishing, fine tuning and re-publishing.
- FIG. 49 illustrates a network architecture for an open developer platform for virtual service provider (VSP) partitioning in accordance with some embodiments.
- the service controller design, policy analysis, definition, test, publishing system 4835 is configured so that multiple “service group owners” (e.g., the service provider for certain smart phones) or “device group owners” (e.g., eReader devices for the eReader service provider(s)) or “user group owners” (e.g., IT for Company X for their employees' corporate mobile devices), collectively referred to as the “Virtual Service Provider” (VSP), are serviced with the same service controller infrastructure and the same (or substantially similar) service processor design from virtual service provider workstation server 4910 and/or virtual service provider remote workstation(s) 4920 .
- VSP Virtual Service Provider
- the virtual service provider remote workstation(s) 4920 communicates with the virtual service provider workstation server 4910 via VPN, leased line or secure Internet connections.
- the dashed lines shown in FIG. 49 are depicted to represent that, in some embodiments, the virtual service provider workstation server 4910 is networked with the service controller device control system 4825 and/or, in some embodiments, the service controller design, policy analysis, definition, test, publishing system 4835 .
- VSP workstation server 4910 can also be networked in various embodiments with billing system 123 , AAA server 121 , gateways 410 or 420 , or other network components to perform, for example, various network provisioning and activation related functions discussed herein for the device group assigned to one or more VSPs, or for other reasons as will be apparent to a given VSP embodiment.
- the service controller functionality is partitioned for a VSP by setting up one or more secure workstations, secure portals, secure websites, secure remote software terminals and/or other similar techniques to allow the service managers who work for the VSP to analyze, fine tune, control or define the services they decide to publish to one or more groups of devices or groups of users that the VSP “owns,”
- the VSP “owns” such groups by virtue of a relationship with the central provider in which the VSP is responsible for the service design and profitability.
- the central provider receives payment from the VSP for wholesale access services.
- the VSP workstations 4910 and 4920 only have access to the service analysis, design, beta testing and publishing functions for the devices or users “owned” by the VSP.
- the user or device base serviced by the central provider network is securely partitioned into those owned by the central provider, those owned by the VSP, and those owned by any other VSPs.
- the VSP manages their devices from the VSP workstations 4910 and 4920 using device based service control techniques as described herein. In some embodiments, the VSP manages their devices from the VSP workstations 4910 and 4920 using device assisted and network based service control techniques as described herein. In some embodiments, the VSP manages their devices from the VSP workstations 4910 and 4920 using network based service control techniques (e.g., DPI techniques) as described herein.
- DPI techniques network based service control techniques
- this approach is particularly well suited for “open developer programs” offered by the central providers in which the central provider brings in VSPs who offer special value in the devices or service plans, and using this approach, neither the central provider nor the VSP needs to do as much work as would be required to set up a conventional MVNO or MVNE system, which often requires some degree of customization in the network solution, the billing solution or the device solution for each new device application and/or service application that is developed and deployed.
- the service customization is simplified by implementing custom policy settings on the service processor and service controller, and the custom device is quickly brought onto the network using the SDK and test/certification process.
- the VSP functionality is also offered by an entity other than the central provider.
- an MVNE entity can develop a wholesale relationship with one or more carriers, use the service controller to create the VSP capabilities, and then offer VSP services for one network or for a group of networks.
- the service customization is simplified by implementing custom policy settings through the VSP embodiments on the network equipment, including, in some embodiments, service aware or DPI based network equipment that has a relatively deep level of service activity control capability.
- VSP embodiments for performing one or more of analyzing traffic usage and defining, managing service profiles or plans, dry lab testing service profiles or plans, beta testing service profiles or plans, fine tuning service profiles or plans, publishing service profiles or plans, or other policy related settings can involve programming settings in the network equipment and/or programming settings or software on the device.
- the service processor settings are controlled by the service controller, which can be partitioned to allow groups of devices to be controlled.
- equipment in the network involved with network based service control can similarly be programmed to utilize various VSP embodiments to implement that portion of the service profile (or service activity usage control) that is controlled by network level functions, and it will be appreciated that substantially all or all of the service activity control for certain embodiments can be accomplished with the network functions instead of the device.
- the device service processor settings control functions of the service processor can have a group of devices that are partitioned off and placed under the control of a VSP
- various VSP control embodiments can partition off a group of devices that have service usage activity controlled by the networking equipment, including, in some embodiments, sophisticated service aware DPI based service control equipment, to achieve similar objectives.
- SDK Open Development System for Access Services
- an SDK is provided that allows developers, such as device manufacturers, service providers, MVNO, MVNE and/or VSPs, to develop various service processors (e.g., different versions of the service processor 115 ) for various devices (e.g., various types of devices 100 ) and corresponding service controllers (e.g., different versions of the service controller 122 ) for various types of services and network environments.
- developers such as device manufacturers, service providers, MVNO, MVNE and/or VSPs, to develop various service processors (e.g., different versions of the service processor 115 ) for various devices (e.g., various types of devices 100 ) and corresponding service controllers (e.g., different versions of the service controller 122 ) for various types of services and network environments.
- a device manufacturer can use the SDK to develop a new service processor for their new device (e.g., mobile phone, PDA, eBook reader, portable music device, computer, laptop, netbook, or any other network accessible device).
- the device manufacturer
- the new device can be preinstalled with the new service processor to provide ambient services, as similarly discussed herein in various embodiments.
- the SDK can allow for substantially similar service processors to be installed on similar and/or different devices thereby minimizing any unnecessary differences between service processor elements for device assisted services.
- a set of numbers e.g., dummy numbers
- the set of (dummy) numbers used for ambient access by the device can also be used for associate of the device with a service provider or a type of device (e.g., eReader or some other type of network accessible device), and upon activation, the service provider assigns a real number for the activated device (e.g., which can be provided at the time of manufacture of the device, point of sale of the device, or after the point of sale of the device, such as upon activation of the device).
- a real number for the activated device e.g., which can be provided at the time of manufacture of the device, point of sale of the device, or after the point of sale of the device, such as upon activation of the device.
- ambient access of the device can use the device ID, SIM ID, assigned phone (real or dummy) number, and/or other information associated with the device for assigning appropriate service control and service policy/profile for the device.
- the service processor 115 is distributed as an SDK to any device that the central provider or the VSP desires to offer services with so that the service processor 115 can be efficiently designed or adapted by the device OEM, ODM or manufacturer for operation on the service network.
- the SDK includes either a complete set of service processor 115 agent software designed for and/or tested for the OS (Operating System) and processor set being used on the device, or a mature reference design for the OS and processor set being used on the device, or a less mature reference design (potentially for the same OS and/or processor set or a different OS and/or processor set being used on the device) that the OEM (Original Equipment Manufacturer) ports to the desired OS or processor set, or a basic set of example software programs that the OEM or ODM (Original Design Manufacturer) can use to develop software compatible with the service, or a set of specifications and descriptions (possibly forming an interoperability standard) of how to design the software to be compatible with the service.
- the SDK includes a set of OEM lab test procedures and/or test criteria to ensure that the implementation of the service SDK is compatible with the service and will operate properly.
- the SDK includes a set of network certification test procedures and/or test criteria to ensure that the implementation of the service SDK is compatible with the service and will operate properly.
- the certification procedures are approved for testing by the OEM, the central provider, the VSP and/or a trusted third party.
- the central provider is typically in control of the SDK and the test procedures, but others can be in control.
- the test procedures are at least in part common across multiple central provider networks.
- the SDK concept is extended to include one or more modem modules where one or more of the SDK embodiments described above is combined with a standard reference design or a standard hardware sales package for one or more modems so that the entire package forms a turn-key product that allows a device manufacturer, central provider, VSP or other entity bring new devices or device applications onto the central provider network possibly in combination with other networks in a manner that requires less engineering time and resources and less network certification time and resources than would be required in some designs that do not use this standard SDK plus module approach.
- the standard SDK plus module product embodiments can be pre-certified and tested with one or more central providers to further reduce development time and expense.
- the standard SDK plus module embodiments can also use a multi-mode modem (e.g., modems based on a multimode CDMA, EVDO, UMTS, HSPA chipset as in the Gobi global multimode chipset product or modems based on other recently announced LTE plus HSPA chipsets, WiMax plus Wi-Fi chipsets or LTE plus EVDO chipsets) and a multi-mode connection manager agent so that the same SDK plus modem embodiment may satisfy a wide range of applications for many service providers around the world.
- a multi-mode modem e.g., modems based on a multimode CDMA, EVDO, UMTS, HSPA chipset as in the Gobi global multimode chipset product or modems based on other recently announced LTE plus HSPA chipsets, WiMax plus Wi-Fi chipsets or LTE plus EVDO chipsets
- the device is associated with an MVNO.
- the MVNO can provide an ambient service that provides a service provider clearing house, in which the device can access a network in ambient access mode (e.g., a wholesale MVNO connection through the access network) for purposes of selecting a service provider (e.g., a VSP, MVNO or carrier).
- a service provider e.g., a VSP, MVNO or carrier.
- the device credentials and/or service processor are reprogrammed and/or new software is downloaded/installed to activate the device with the selected service provider, as described herein for provisioning the device and the account on that service provider network (e.g., the ATS can track such activation, for example, for revenue sharing purposes, as an activation incentive fee).
- ATS is implemented entirely in the network as described below.
- the device master agent programs a unique credential in the device that cannot be re-programmed or removed (or is difficult to re-program or remove) and that can be recognized and recorded by the network at the time of activation or at some other time.
- the ATS process can then be implemented by using a database search function to scan through the database of activated devices to form a list of devices that have been activated for the purpose of master agent reconciliation.
- Example credentials that can suffice are MEID, hardware MAC address, and/or serial number, that are picked up and recorded by the service provider or other service entity at time of activation or before or after activation.
- FIG. 50 illustrates a network architecture including a billing to service controller interface for accommodating minimum changes in existing central billing, AAA and/or other network components in accordance with some embodiments.
- the central billing system 123 includes a mediation, customer service and billing databases, historical usage, billing systems component 5010 and a billing to service controller interface component 5020 .
- the billing to service controller interface component 5020 allows for the central billing system 123 to efficiently communicate with the service controller (e.g., service controller device control system 4825 ).
- an interface server e.g., the billing databases, historical usage, billing systems component 5010 and/or the billing to service controller interface component 5020 ) is provided that reads the IPDRs, service profile and/or service plan information stored in the billing and/or service record database(s).
- the interface server performs these functions in a manner that is compatible with communication formats of the billing and/or service record database(s) so that little or no changes are required in the configuration, communication formats or software of the existing central billing, AAA and/or other network components.
- the interface server (e.g., including the billing databases, historical usage, billing systems component 5010 and the billing to service controller interface component 5020 ) is co-located with the central billing system components as shown, or in other embodiments, the interface server is located elsewhere.
- the interface server can be located close to or within the components that comprise the service controller or anywhere else in the network.
- the interface server performs certain communication protocol translation or data format translation required to interface the information stored in the billing and/or service record database(s) to the service controller functions so that the central billing system 123 and other existing components in the network do not need to change much (if at all) to enable the service controller and service processor to implement device based/assisted service control.
- the central billing system 123 or other network components are not required to be aware of the service control functions being implemented by the service controller or service processor, because the interface server acquires the network based information needed by the service controller and/or service processor while requiring little or no specialized awareness, communication, data formatting, user interfacing, service profile processing or service plan processing on the part of existing billing, database or networking components.
- various embodiments described herein can be used to quickly upgrade the capabilities of existing networks for new devices while minimizing the required changes to the existing network that supports legacy devices.
- a new ambient service plan can be implemented within the central billing system 123 that is associated with a zero or low cost billing plan and a usage limit (e.g., ambient service) that may be difficult or impossible to support in a manner that would result in high user satisfaction and a high level of control for service cost and service policy definition.
- the zero or low cost plan can be implemented in a manner that results in high user satisfaction and a cost controlled service by using the service controller and/or service processor and the interface server to implement the ambient services access control, service usage control, user interface, service usage notification, transaction billing or bill by account functionality.
- this approach can be implemented by reading the service plan and/or service policy settings for a device in the central billing database using the interface server, looking up the corresponding service policy, user notification policy, transaction billing policy and bill by account policy associated with the particular service profile or service plan, and then implementing the policies with the assistance of the service controller and/or service processor.
- multiple tiers of service control and user notification policies can be added to any number of new service profiles or service plans that would not otherwise be supported with the central billing system 123 and other network components, all with minimal or no modifications to the pre-existing network and billing system.
- Another embodiment calls for receiving a standard IPDR feed from central billing 123 or another network component just like an MVNO would.
- the interface server function can be located in the central billing system, service processor or elsewhere in the network. This provides the IPDR records for service usage policy verification and service usage notification synchronization with little or no need to modify existing billing or network apparatus.
- duplicate the IPDRs are sent from the network equipment to the billing system and/or network management system that are currently used for generating service billing or are used for device management or network management.
- duplicate records are filtered to send only those records for devices controlled by the service controller and/or service processor. For example, this approach can provide for the same level of reporting, lower level of reporting, and/or higher level of reporting as compared to the reporting required by the central billing system.
- a bill-by-account billing offset is provided using the interface server.
- bill-by-account billing offset information is informed to the billing system through an existing data feed and by updating the billing database using the interface server.
- transaction billing is provided using the interface server.
- transaction billing log information is provided to the billing system through an existing data feed and by updating the billing database using the interface server.
- existing/new service plan choice screens are displayed to the user, a user choice or decision/input is confirmed for a selected service plan, and then the service is implemented upon confirmation of the billing system update for the new service plan.
- the service is implemented upon the user selection of a new service plan and then retracted if not confirmed as updated by the billing system within a certain period of time.
- the new service plan information is updated in the billing system through an existing data feed or by updating the database using the interface server.
- FIG. 51 illustrates a network architecture for locating service controller device control functions with AAA and network service usage functions in accordance with some embodiments.
- an integrated device service control, AAA, device usage monitoring system 5110 is provided that integrates service controller functions (e.g., service controller device control system functions 4825 of FIG. 48 ) with access network AAA server 121 functions and network (e.g., real-time) service usage 118 functions.
- service controller functions e.g., service controller device control system functions 4825 of FIG. 48
- access network AAA server 121 e.g., real-time
- FIG. 52 illustrates a network architecture for locating service controller device control functions in the access transport network in accordance with some embodiments.
- the service controller device control system 4825 is located in the access transport network 415 , or in some embodiments, in the 4G/3G/2G RAN gateways 410 (as indicated by the dashed line with the arrow), or alternatively, in the 4G/3G/2G transport gateways 420 (as indicated by the dashed line with the arrow).
- FIG. 53 illustrates a network architecture for locating service controller device control functions in the radio access network in accordance with some embodiments.
- the service controller device control system 4825 is located in the radio access network 405 , or in some embodiments, in the 4G/3G base station(s) 125 (as indicated by the dashed line with the arrow), or alternatively, in the 3G/2G base stations 125 (as indicated by the dashed line with the arrow).
- provisioning includes one or more of the following: a process or result of assigning, programming, storing or embedding into the device and/or network a set of credentials, or otherwise providing the credentials to the user; the credentials being at least in part carried on the device or with the user; and/or at least a portion of or a counterpart to the credentials being stored or recognized by the network so that the various network elements responsible for admitting the device access to the appropriate service activities do so once the device or user service is active.
- the credentials can include one or more of the following: phone number, device identification number, device security signature or other security credentials, device identification and/or security hardware such as a SIM, device type identifier, one or more IP addresses, one or more connection MAC addresses, any other address identifier, device service owner or VSP identifier, device OEM, device distributor or master agent, and/or any other information the network can use for admission control, authorization control, identifying the device with a service profile, identifying the device with an initial activation or ambient experience, identifying the device with a service plan or authorized set of service activity capabilities, identifying the device with a service provider or service owner, identifying the device with an OEM or master agent, identifying the device with a distributor or master agent, or identifying the device with a user group or user.
- device identification and/or security hardware such as a SIM, device type identifier, one or more IP addresses, one or more connection MAC addresses, any other address identifier, device service owner or VSP identifier, device OEM, device distributor or master agent, and/
- provisioning includes assigning, programming or embedding into the device and/or network the information to define the level of service activity, referred to as a service profile, that the device is authorized to receive.
- provisioning also includes establishing the device settings and/or network settings to define an ambient activation experience in which the device user receives a set of services after (e.g., within a short period of time after) purchasing or otherwise obtaining or installing the device whether the device has or has not been registered and activated with the device user or device owner.
- the ambient experience is the user experience that is available at the time the device is sold in the event the user has not yet signed up for a service plan.
- the ambient experience is defined by an ambient service profile, an ambient service plan and/or the other service usage activity control policies in effect in the network, on the device, or a combination of both.
- the initial provisioning and activation settings in the service processor, and possibly the service controller can define the user service upgrade offering choices, network destination access control possibilities, traffic control policies, mobile commerce transaction capabilities (e.g., which transaction websites, WAP sites or portals the user can access to purchase information, content, music, games and/or eBooks), possibly free news or weather or other modest bandwidth Internet services that are provided free of charge to entice the user into using/upgrading the service or using the transactions or viewing advertisements, what advertisements are displayed to the user or what advertisement based websites the user is exposed to, certain applications may have access while others are blocked (e.g., Internet based text services have access but email downloads do not), or other example service capabilities.
- mobile commerce transaction capabilities e.g., which transaction websites, WAP sites or portals the user can access to purchase information, content, music, games and/or eBooks
- free news or weather or other modest bandwidth Internet services that are provided free of charge to entice the user into using/upgrading the service or using the transactions or viewing advertisements, what advertisements are displayed to
- each service activity can, for example, be separately tracked with the service monitor and other agents and server functions to produce a billing offset that allows categorization and mediation of different billing entities (accounts) provides the capability for the service provider to individually account for the costs of each ambient service element.
- the ambient services can be a potential source of losses for the service provider.
- the ambient service capabilities can be modified over time to reduce service cost to the service provider or VSP based on a variety of decision factors. For example, the user can have one level of traffic control for a period of time, and if the user has not signed up for service by the end of the period, the ambient service access is reduced by changing the service control policy settings in the service processor, and the service level can be further reduced over time if the user continues to not sign up for service or the user does not create much transaction revenue.
- the recursive throttling algorithms discussed herein can be utilized to one or more of the service activities offered in ambient service mode so that the user experiences what full speed service is like, and if the user continues consuming appreciable bandwidth with the service activity, then the activity is throttled back to reduce costs.
- the service processor or service controller can issue the user a notification explaining that their service is currently free so their usage is being throttled, and if they desire to receive better service, service plan upgrade offers can be delivered to the UI.
- the various ambient service parameters including the provisioning and activation processes used to create the ambient service activation, can also be managed by the VSP apparatus and processes described herein. For example, this allows the same service controllers and service processor solutions to be used to define a wide range of ambient experiences for various device groups or user groups that are controlled by different VSPs.
- the ambient service profile settings rather than controlling the ambient service profile settings using the VSP functions to control the service controller, service processor, provisioning and activation settings, other embodiments call for the ambient service profile settings to be controlled by the network based service activity control equipment as similarly discussed herein.
- the level of service control and service monitoring sophistication e.g., highly advanced DPI or service aware techniques
- some, much, most or all of the above described ambient services functionality can be implemented using network based service controls and the VSP management and control embodiments described herein.
- a device is suspended based on inactivity, or the device is placed in a suspended service state or suspended account state, so that the network does not get bogged down with a significant number of devices and credentials that are inactive. For example, this can also result in a portion of the device credentials being assigned back to an available pool rather than reserved for that particular device (e.g., phone numbers if phone numbers are scarce).
- the device account and/or activation state can be re-activated when the device comes back online.
- the suspend state can be a simple suspension of services without changing the account status, in which case the re-activation process can be automatically completed as a subset or entire set of the activation sequence that occurs when the device is initially used as described herein.
- the suspend state can also involve changing the account status to inactive, in which case the re-activation process can automatically reconfigure the account status back to an active state when the device re-accesses the network.
- the suspend state can involve de-assigning or possibly re-claiming a portion of the device credentials. If a portion of the credentials are de-assigned, then when the device re-accesses the network credentials can be automatically re-assigned as described in various embodiments described herein.
- FIGS. 54 through 63 depict various embodiments for combinations of device based service monitoring, control or control assistance, usage notification or usage notification assistance and/or network based service monitoring, control or control assistance, usage notification or usage notification assistance.
- FIG. 54 illustrates a network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments.
- an integrated device service control, device usage monitoring system 5410 is provided that integrates service controller functions including a deep packet control (DPC) policy implementation function 5402 with access network AAA server 121 functions and network real-time service usage 118 functions.
- DPC deep packet control
- the AAA server 121 function can be re-located to another point in the network or network equipment partitioning with no loss in generality.
- many of the functional partitions described for the various embodiments within integrated device service control, device usage monitoring system 5410 can be re-drawn with no loss in applicability, function or generality.
- one or more of the functional elements described within the integrated device service control, device usage monitoring system 5410 can be removed for simplified embodiments and that not all the functionality described herein is necessary in some embodiments.
- the integrated device service control, device usage monitoring system 5410 provides for network based service monitoring or control that satisfies various network neutrality and/or privacy requirements based on indication(s) received from the device or user (e.g., user input provided using the device UI using the service processor 115 ; user input provided through another website, WAP site or portal; or user input provided through the service contract where the user agrees to the monitoring and/or service control levels) and network based service control using a DPI service monitor 5412 and/or the DPC policy implementation 5402 .
- indication(s) received from the device or user e.g., user input provided using the device UI using the service processor 115 ; user input provided through another website, WAP site or portal; or user input provided through the service contract where the user agrees to the monitoring and/or service control levels
- network based service control using a DPI service monitor 5412 and/or the DPC policy implementation 5402 .
- the integrated device service control, device usage monitoring system 5410 provides for network based service monitoring or service control that satisfies various privacy requirements using indication(s) received from the device or user (e.g., user input provided using the device UI using the service processor 115 ; user input provided through another website, WAP site or portal; or user input provided through the service contract where the user agrees to the monitoring and/or service control levels) and network based DPI service usage monitoring or DPC policy implementation using the DPI service monitor 5412 or DPC policy implementation 5402 as described below.
- the DPI service monitor 5412 and/or DPC policy implementation 5402 include a secure database for storing service monitoring and CRM information for each device/device user.
- the DPI service monitor 5412 and/or DPC policy implementation 5402 can be integrated with the integrated device service control, device usage monitoring system 5410 (as shown) or provided within a separate router, server, and/or software/hardware implemented function that is in secure communication with the integrated device service control, device usage monitoring system 5410 and/or other network elements based on the network architecture.
- a secure data store such as a secure database, is not integrated with the DPI service monitor 5412 or DPC policy implementation 5402 but is in secure communication with the DPI service monitor 5412 or DPC policy implementation 5402 , the integrated device service control, device usage monitoring system 5410 and/or other network elements depending on the architecture (e.g., a billing server or any other network element).
- the user selects limits and/or restrictions on who can access remotely stored service usage history and/or other CRM/privacy related data (e.g., CRM/privacy gatekeeper settings), and, for example, other network elements and/or network administrators access to such data can be limited and/or restricted accordingly.
- access to such stored service monitoring and CRM information can require certain security credentials and/or using various other well known secure data storage techniques, such as the various secure storage techniques described herein.
- the secure database possessing user service usage information that is considered sensitive and has not been approved for distribution by the user can be made unavailable to the credentials possessed by network managers or network functions except, for example, for emergency service situations of government mandated monitoring needs where special credentials are brought out of secure storage that are not normally available.
- a certain set of restrictions are assumed unless the user selects information filtering settings that allow more information to be shared with the network functions, network administrators or service provider partners.
- the information is filtered to remove information thought to be sensitive but still transmits service usage information needed for monitoring network services or other important parameters. For example, the website destinations a user is visiting can be classified with generic identifiers that are not decodable or the individual website information can be completely removed. Many other examples will be apparent to one of ordinary skill in the art.
- the stored service monitoring and CRM information can also be organized into groups to define group CRM profiles to store service monitoring information for every user indexed by the user credentials (e.g., such groups can also be used for various VSP related functions, as described herein).
- the DPI service monitor 5412 or DPC policy implementation 5402 also uses the secure storage to store service monitoring information for each user indexed by the user credentials or another aspect of the device identifier or address assignment (e.g., IP address or MAC address).
- a CRM information manager e.g., a supervisor program executing on the integrated device service control, device usage monitoring system 5410 ) communicates with the other network functions and provides filtered service usage and CRM information according to CRM filtering rules for each user or for groups of users.
- the filtered CRM data can be made available using secure communications with other networking equipment by the integrated device service control, usage monitoring system 5410 .
- the filter settings for some users allow more information to be shared from the secure service usage information than others due to the differences in user preference settings and/or service plan agreements.
- user privacy preference information is used to determine the privacy filter settings, which are securely implemented by the integrated device service control, device usage monitoring system 5410 .
- service CRM filter settings can be received at the time of service contract sign up (e.g., service plan selection) and/or allow the user to log into service preferences web page to change settings (e.g., without involving any interaction with local software on the device).
- software on the device can be used for selecting user CRM/privacy preferences, which are securely communicated to the integrated device service control, device usage monitoring system 5410 (e.g., the device can include credentials that can be verified to allow for selection/modification of CRM/privacy preferences or other user based preferences securely maintained in a network server, such as the integrated device service control, device usage monitoring system 5410 or another network element, such as shown in various other embodiments described herein).
- the filtered CRM data is available from the integrated device service control, device usage monitoring system 5410 for other network components over a secure or open communication link.
- user CRM/privacy preferences are input using a web server hosted by the integrated device service control, device usage monitoring system 5410 or the central billing system 123 .
- software on the device e.g., including the service processor 115
- an intermediate server that acts as a device manager and intermediate server for devices or device groups and the integrated device service control, device usage monitoring system 5410 .
- the integrated device service control, device usage monitoring system 5410 provides for network based service control as described below.
- the DPI service monitor 5412 or DPC policy implementation 5402 includes secure storage (e.g., a secure database) for storing service monitoring information (e.g., based on user selections/preferences), and the DPC policy implementation 5402 performs traffic shaping/throttling algorithms for each user based on the stored service monitoring information from DPI service monitor 5412 .
- secure storage e.g., a secure database
- service monitoring information e.g., based on user selections/preferences
- the DPC policy implementation 5402 performs traffic shaping/throttling algorithms for each user based on the stored service monitoring information from DPI service monitor 5412 .
- network based DPI traffic inspection by the DPI service monitor 5412 can use the secure storage to save service monitoring information for each user indexed by the user credentials or other parameters, such as IP address or other network tag.
- the DPC policy implementation 5402 can implement service usage history statistical analysis inside the secure storage and maintain a service usage history analysis for each device/user and/or perform various traffic shaping and/or throttling algorithms based on various device, user selected and/or service plan related settings (e.g., for network neutrality purposes) allowing for various higher level service usage goals for one or more users, as similarly described herein with respect to various device based service usage monitoring embodiments (e.g., except for certain encrypted network traffic flows or application related flows for which traffic control generally needs information from the application level and/or content specific traffic control).
- service plan related settings e.g., for network neutrality purposes
- input is collected on how to implement service control (e.g., from the user of the device). For example, such input can be determined based on one or more of the following: a service plan choice for the device; input provided by a user via a website (e.g., web based portal) for indicating changes to service control policies, as similarly described above; input provided by a user via the device (e.g., including the service processor 115 ), which securely communicates the input to the DPC policy implementation 5402 , for example, which can be supervised by the policy management server 1652 ; and input provided by a user via the device (e.g., including the service processor 115 ), which securely communicates the input to an intermediate server for the DPC policy implementation 5402 , as similarly described above.
- such service control is based on various algorithms as described herein that identify the heaviest usage service activities and recursively control the speed for those activities while leaving certain others unaffected, and in a manner that is specified or selected by the user to ensure network neutrality.
- the user is offered a choice for controlling service usage and/or selects an algorithm that controls all activities equally/neutrally (e.g., based on selected user preferences).
- network neutral traffic control or service usage control can be maintained.
- the DPI service monitor 5412 possibly in conjunction with the service usage notification 5420 and/or service history server 1650 , provides service usage/service cost (e.g., a real-time service usage counter) related notifications to the device based on user preferences, as similarly described above with respect to various device based service usage/service related notification embodiments.
- service usage/service cost e.g., a real-time service usage counter
- the DPI service monitor 5412 for example, in conjunction with the service usage notification 5420 and/or service history server 1650 , can perform service usage/service related notification algorithms based on one or more of the following: service plans, device settings, and/or user selected preferences (e.g., such notification messages can be securely communicated to the device and/or to the device via an intermediate server).
- policies that govern how the user is notified of service usage or service cost can be determined by the policy management server 1652 and/or the service usage notification 5420 .
- user acknowledgements of important notification messages and/or user choices related to important service usage decisions can be requested, as similarly discussed above with respect to device based service usage/control embodiments, which can then be communicated to the central billing system 123 as confirmation for any such important notification messages (e.g., related to service usage overage charges and/or confirmation of service upgrades).
- various other service usage algorithms related to service usage and/or service cost forward projections described herein with respect device based service usage forward projection embodiments are performed in the network, such as by the integrated device service control, device usage monitoring system 5410 , and such forward projections can then be communicated to each respective device as service usage notification messages (e.g., using a push based approach (initiated in the network) and/or pull based approach (initiated by a request from the device)).
- these embodiments for projected service usage methods can be helpful for determining when the user is using services in a manner that will cause the user to run over a service limit so that the user can be notified, or the service can be controlled or throttled if the user has selected a control or throttling option.
- one or more intermediate servers are provided for workload balancing and/or off-loading the integrated device service control, device usage monitoring system 5410 and perform one or more of the functions described above with respect to various embodiments of the integrated device service control, device usage monitoring system 5410 .
- service plans, device settings, and/or user selected preferences are used to associate each device/user with a preprogrammed profile to more efficiently associate such devices/users with their selected service plans, device settings, and/or user preferences.
- the process of setting a service profile for a given device can be determined by assigning the device to a service flow that has the pre-defined service profile and is shared with other devices within the integrated device service control, device usage monitoring system 5410 rather than individually processing the service flow manipulations for each device.
- the act of provisioning and activating a service profile for a given devices involves setting up the service flow definition and identifier within the integrated device service control, device usage monitoring system 5410 (if it is not already set up) and then assigning the routing of the device credentials to that service flow identifier.
- User preferences can, for example, be accounted for by assigning the device service flow to one of several pre-defined profiles based on user preferences that are all supported under the same service plan. For example, one service flow profile can call for service usage notification but no control under the same service plan as another service flow profile that calls for less notification but active service usage control to maintain user costs to a monthly post-pay limit.
- the bill by account function is implemented in the context of the integrated device service control, device usage monitoring system 5410 or other network based system embodiments described herein.
- the DPI service monitor 5412 in some cases in conjunction with service history server 1650 , can operate in conjunction with bill by account policy settings stored in the billing event server 1662 so that service activities are divided into the account classifications defined by the service profile settings.
- the bill by account feeds can then be sent to the billing system or to an intermediate billing event aggregation server that collects this type of deep packet inspection generated information from one or more integrated device service control, device usage monitoring system 5410 units to aggregate and format the information in a manner that may be used by the central billing system 123 .
- the bill by account information collected in a network box like the integrated device service control, device usage monitoring system 5410 is augmented by bill by account information collected on the device as described herein, and any intermediate server that can be used to aggregate and format these bill by account feeds for the central billing system deals with both types of data, from the network and from the devices.
- integrated device service control, device usage monitoring system 5410 includes the service control server link 1638 , which, for example, can be used as described above (e.g., with respect to FIG. 16 and other embodiments described herein) to communicate with device service processors 115 .
- billing server 1662 within integrated device service control, device usage monitoring system 5410 detects service usage events reported by DPI service monitor 5412 , in some cases in conjunction with service history server 1650 , generates a billing event that can be recorded or transmitted to the central billing system 123 .
- billing server 1662 receives information from device billing agent 1695 and/or device service monitor agent 1696 and transmits the device service usage billing events to the central billing system 123 .
- certain billing events that are advantageously collected in the network are combined with certain billing events that are advantageously collected on the device (e.g., service monitor agent 1696 and/or billing agent 1695 ), and both sources of billing information are transmitted to the billing system 123 .
- certain service usage information is collected with service usage monitor agent 1696 , and that information is combined with service usage information collected from DPI service monitor 5412 and/or service history server 1650 and/or service usage 118 .
- certain service aspects are controlled using network based DPC policy implementation 5402 , in some cases in conjunction with or supervised by network based policy management server 1652 , and other service aspects are controlled using device based policy implementation agent 1690 , in some cases in conjunction with or supervised by policy control agent 1692 .
- device based policy implementation agent 1690 in some cases in conjunction with or supervised by policy control agent 1692 .
- access control integrity server 1662 and many other service control verification embodiments described herein make it apparent that the integrated device service control, device usage monitoring system 5410 embodiments also provide for affirmative verification of whatever functions are implemented on the device. It will also be apparent that all of the above combinations of device and network functions, and many others, can be accomplished in ways that are network neutral and/or protect user privacy preferences by implementing the service control algorithms in a network neutral manner and/or receiving user preference input on how to implement service control, and by maintaining service usage and CRM information security and filtering on both the device 100 and the network based integrated device service control, device usage monitoring system 5410 .
- the integrated device service control, device usage monitoring system 5410 facilitates or plays a part in automated provisioning and activation of the devices as similarly described above with respect to various device based automated provisioning and activation embodiments.
- the activation server 160 is integrated into or partially integrated into device service control, device usage monitoring system 5410 .
- the integrated device service control, device usage monitoring system 5410 facilitates ambient services as similarly described above with respect to various device based ambient services embodiments.
- the integrated device service control, device usage monitoring system 5410 facilitates VSP and ODI solutions as similarly described above with respect to various device based VSP and ODI embodiments.
- FIG. 55 illustrates another network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments.
- the service processor 115 is not present on the devices 100 , and the integrated device service control, device usage monitoring system 5510 performs all service monitoring, service control, billing, and notification functions.
- FIG. 56 illustrates a 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments.
- a 4G/3G/2G DPI/DPC enabled gateway 5610 e.g., implemented in either gateway 420 or gateway 410 or a combination of both
- the conventional service gateway functions 5616 e.g., routing, switching, protocol translation/tunneling, charging data function (CDF), charging gateway function (GCF), mobility management, and/or suspend/resume
- CDF charging data function
- GCF charging gateway function
- mobility management e.g., RAN and/or transport gateways
- the service gateways e.g., RAN and/or transport gateways
- DPI service monitor 5412 service history server 1650 , device usage 118 , DPC policy implementation 5402 , policy management server 1652 , user notification 5618 , billing event server 1662 , access control integrity server 1654 , service control service link 1638
- data plane I/O 5612 e.g., used to
- the packet processing architecture shown in this figure calls for a multi-point to multi-point backplane bus scheme, but it will apparent that other data path configurations are possible including serial.
- the above described configuration can also be applied to either the transport gateway 420 and/or the RAN gateway 410 .
- Network neutrality can also be maintained in this configuration by maintaining network neutrality in the service control algorithm and/or soliciting user input on how to control service usage just as discussed above for other network service control implementations or as discussed in the device based service control descriptions.
- the bill by account function is implemented in the context of the 4G/3G/2G DPI/DPC gateway 5610 embodiment or other network based system embodiments described herein.
- the bill by account information can be completely derived from the network box (e.g., 4G/3G/2G DPI/DPC gateway 5610 ) without assistance from device based service monitoring or billing capabilities, or none may exist on the device.
- the DPI service monitor 5412 in some cases in conjunction with service history server 1650 , can operate in conjunction with bill by account policy settings stored in the billing event server 1662 so that service activities are divided into the account classifications defined by the service profile settings.
- the bill by account feeds can then be sent to the billing system or to an intermediate billing event aggregation server that collects this type of deep packet inspection generated information from one or 4G/3G/2G DPI/DPC gateway 5610 units to aggregate and format the information in a manner that can be used by the central billing system 123 .
- the bill by account information collected in a network box, such as the 4G/3G/2G DPI/DPC gateway 5610 is augmented, refined or otherwise added to by bill by account information collected on the device as described herein and any intermediate server that can be used to aggregate and format these bill by account feeds for the central billing system deals with both types of data, from the network and from the devices.
- FIG. 57 illustrates a network architecture including the VSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways 410 and 420 in accordance with some embodiments.
- the VSP workstation server 4910 is in communication with the 4G/3G/2G DPI/DPC gateways 410 and/or 420 , the Service Controller Design, Policy Analysis, Test, Publishing System 4835 , and/or other networking elements including possibly the central billing system 123 , the mobile wireless center 132 (HLR) and/or the AAA server 121 for the purpose of provisioning and/or controlling settings in the 4G/3G/2G DPI/DPC gateways 410 and/or 420 , the mobile wireless center 132 and possibly other equipment for the purpose of implementing a portion of the VSP open partner functionality discussed herein.
- HLR mobile wireless center 132
- AAA server 121 the purpose of provisioning and/or controlling settings in the 4G/3G/2G DPI/DPC gateways 410 and/or 420
- the 4G/3G/2G DPI/DPC gateway 5610 functionality as shown in FIG. 56 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 as similarly described above.
- the VSP functionality can also be used to set higher level policies associated with the 4G/3G/2G DPI/DPC gateway 420 or 410 , such as provisioning or activation profiles or policies, ambient service profiles or policies, and/or bill by account service profiles or the other higher level service profile or service plan embodiments discussed herein.
- the provisioning and/or activation steps described herein involve setting service policies in the 4G/3G/2G DPI/DPC gateway 420 or 410 .
- ambient services or ambient activation involve setting up service profiles within the 4G/3G/2G DPI/DPC gateway 420 or 410 that allow the desired activities and block the undesired activities. For example, these settings can be included as part of the open service provider partner programming capabilities of the VSP workstation server 4910 embodiments.
- FIG. 58 illustrates another 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments.
- a 4G/3G/2G DPI/DPC gateway 5810 e.g., implemented in either gateway 420 and/or gateway 410
- the service processor connection e.g., via service control server link 1638 as shown in FIG. 56
- the 4G/3G/2G DPI/DPC gateway 5610 e.g., gateways 410 and/or 420 .
- FIG. 59 illustrates another network architecture including the VSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways 410 and 420 , the AAA 121 and the mobile wireless center 132 in accordance with some embodiments.
- FIG. 59 provides a network diagram corresponding to FIG. 58 , with similar functionality to the embodiment shown in FIG. 57 , in which the service processors 115 are not present on the devices 100 .
- the 4G/3G/2G DPI/DPC gateway 5810 functionality as shown in FIG. 58 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 as similarly described above.
- FIG. 60 illustrates a 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments.
- enhanced network based service monitoring, control, billing and notification as discussed above is implemented using a 4G/3G/2G DPI/DPC enabled gateway 6010 and service controller device control system 6025 as shown.
- the functions shown in the figure to be inside of the service controller device control system 6025 have been moved from the 4G/3G/2G DPI/DPC gateway 5610 of FIG. 56 (e.g., or from gateways 410 and/or 420 ) so that they reside in a separate server embodiment or other network equipment function separate from the 4G/3G/2G DPI/DPC gateway 6010 .
- this architecture can be used when the network equipment manufacturer desires to separate these functions or has an existing product that it is desirable to upgrade by adding a separate box.
- this architecture can be used when the 4G/3G/2G DPI/DPC gateway 6010 is not capable of keeping up with large numbers of individual user profiles so it is desirable to go to a scalable server configuration in which load balancing can be applied with a potentially more flexible programming environment for implementing service policy management functions, statistical service history analysis algorithms, service usage projection, and/or service control (or throttling) algorithms.
- a secure storage is provided on the 4G/3G/2G DPI/DPC gateway 6010 and/or the service controller device control system 6025 that requires secure credentials to get into so that, for example, user privacy can be protected and service usage information or CRM information can be filtered according to user preferences prior to sending to another network function or network manager, and the same allowances can also be applied, for example, for emergency or government monitoring purposes.
- network neutrality can also be maintained in this configuration by maintaining network neutrality in the service control algorithm construction and/or soliciting user input on how to control service usage just as discussed above for other network service control implementations or as discussed in the device based service control descriptions.
- FIG. 61 illustrates another network architecture including the VSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways 410 and 420 , AAA 121 and mobile wireless center 132 in accordance with some embodiments.
- the 4G/3G/2G DPI/DPC gateway 6010 functionality as shown in FIG. 60 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 , as similarly described above, and which are in communication with the service controller device control system 6025 as shown.
- FIG. 62 illustrates another 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments. As shown, the capability to communicate with the service processor 115 has been removed so that all service monitoring, control, billing event collection and transmission, and notification are performed by the 4G/3G/2G DPI/DPC gateways 6210 (e.g., implemented in gateways 410 and/or 420 ) in conjunction with the service controller device control system 6225 without assistance from the service processors 115 .
- the 4G/3G/2G DPI/DPC gateways 6210 e.g., implemented in gateways 410 and/or 420
- FIG. 63 illustrates another network architecture including the VSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways 410 and 420 , AAA 121 and mobile wireless center 132 in accordance with some embodiments.
- the 4G/3G/2G DPI/DPC gateway 6210 functionality as shown in FIG. 62 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 , as similarly described above, and which are in communication with the service controller device control system 6225 as shown.
- automated provisioning and activation includes automation of one or more of the following functions: (1) programming device credentials or partial credentials and recording them in a database (or providing same when they are programmed into the device), (2) associating these credentials with the proper provisioning and/or activation actions to be taken on the device and in the network, (3) directing the device to the proper activation function (e.g., activation server) sequence when it attempts to connect to the network, (4) completing provisioning of the device, (5) programming the AAA, billing system, gateways, mobile wireless center and other network equipment to the proper initial device service control settings, and (6) establishing a service account for the device.
- the proper activation function e.g., activation server
- activation includes one or more of the following: a process or result of associating a service account with device or user credentials; with the service account potentially further being associated with a service profile defining the service activities that the device is authorized to access; creating or updating a service usage or billing record and associating it with the service account to create a service plan; and/or initiating service to the device or user in which the network equipment allows access to the appropriate level of service activities.
- VSP embodiments include the provisioning and activation apparatus embodiments of any or all forms.
- the provisioning and activation process required to create a user service account and enable the device to access the desired level of service activities can limit mass market, low cost or user friendly applications of the device or service, because the process can often be cumbersome, time consuming and/or expensive for the service provider, service owner, master agent (service distributor), MVNO, VSP and/or user. Accordingly, the various embodiments for provisioning and activation described herein simplify the provisioning and activation process for mobile devices.
- provisioning and activation for the device and/or the network accommodates a wide variety of device types and service profile types, with the capability to perform the provisioning and activation at a number of points in the manufacturing, distribution, sales and usage progression for the device, and the ability to either pre-activate before first device use or very quickly activate during first device use (or during some later use of the device).
- provisioning generally refers to those actions/processes associated with programming the device with credentials or other device settings or software installations used to later activate the device, as well as, in some embodiments, creating database entries and other credential associations in the network so that the network and/or device have the information used to recognize the device or credentials and implement the service policies in the service profile and/or service plan once the service profile and/or service plan are activated.
- the term activation generally refers to the process of creating or selecting the service plan and/or service profile, programming the settings that are used in each (e.g., required) network function and/or each (e.g., required) device function so that the system can properly associate the device credentials with the appropriate service activity policies, and then admitting the device onto the network.
- the term activation can also refer in some embodiments to the creation of a user or device service account, in some cases, with user or device owner information or billing information.
- the process of provisioning amounts to assigning credentials to the device and programming a portion or all of the credentials on the device, entering a portion or all of the credentials in the various necessary network equipment databases so that the network components are capable of identifying the device and associating it with the network based portion of the admission, traffic processing, service monitoring, billing, service limits and other policies that are eventually defined by the service profile and service plan.
- the network based service profile policies include network access level, traffic routing, service monitoring, service limits and actions taken upon reaching service limits.
- the device credentials and the associated service profile are communicated throughout the necessary network elements so that each element can implement its part of the network portion of the service profile policies.
- This process of propagating the service profile settings to all the required network equipment components is a portion of what is referred to herein as activation in accordance with some embodiments.
- the activation process includes associating the credentials with the proper service plan and/or service profile, and possibly completing the process of programming the device functions and/or network functions so that the device can be admitted to the appropriate level of network services.
- activation also includes the service processor software settings, configurations or installs for each function or agent in the service processor to implement its part of the service profile, service plan, service billing or transaction billing policies.
- activation also includes the creation of entries in the various service account databases and/or billing databases to create a user account or device owner account for the purpose of managing the user choices for service plan and other account information storage and management aspects, such as maintaining status information, maintaining the central service profile configuration, conducting reconciliation and billing exchanges, service usage history, and/or account history.
- the term credentials generally refers to the set of information parameters that the network and/or device uses (e.g., requires) to admit the device onto the network and associate it with the appropriate service profile and/or service plan.
- the credentials can include one or more of the following: phone number, device ID, hardware security device ID, security signatures, IP or MAC address, signature algorithms, passwords, or other secure authorization processes, service provider, OEM, master agent (service distributor), device distributor, VSP, service processor settings or version, or other information used/required by the network to authorize network admission or activate service.
- at least some of the credentials are unique to the device, and, in some embodiments, groups of devices share one or more aspects of the credentials.
- the term permanent credentials generally refers to the set of credentials that include at least a subset that are intended to be assigned to a device or user on a permanent basis.
- the term temporary credentials generally refers to the set of credentials that include at least a subset that are intended to be assigned to a device or user on a temporary basis.
- temporary credentials are eventually replaced by permanent credentials.
- at least some elements in the temporary credentials e.g., phone number and/or access or authorization security credential
- the temporary credentials are recycled from one or more devices and used for one or more other devices, for example, when they remain unused for a period of time or when they are replaced with permanent credentials on one or more devices.
- partial credentials or pre-activation credentials generally refer to a subset of credentials that are to gain access to limited network services for the purpose of provisioning of credentials and/or activation of a service plan or service profile.
- a device can gain access to a limited set of network server destinations in which embedded information contained in the device (e.g., the partial credentials) is provided to the server, the server associates that information with the proper additional credentials (including the phone number) to assign to the device and/or associates the information with the proper service profile to activate service.
- the server associates that information with the proper additional credentials (including the phone number) to assign to the device and/or associates the information with the proper service profile to activate service.
- partial credentials can include device type, OEM, service provider, VSP, device identification number, SIM, service processor configuration or some other information used by the server to determine what the credentials should be and the proper service profile.
- a permanent service account generally refers to the service account that is permanently associated with the user and/or device.
- this account includes an association with the device or user credentials, user information or billing information, service profile, billing profile, network authorization status and other aspects that define the device or user service policies and billing policies.
- the term temporary service account generally refers to a service account that is temporarily set up and associated with the device before some or all of the required permanent account information is available or entered for a device or user.
- this account can be set up with an association with an actual user, or can be set up with a mock user or unassigned user association so that the network and billing system can recognize the credentials, authenticate the device, admit the device, provide the proper level of service activity control according to the service profile associated with the temporary service account, or collect the service activity usage information for various network and billing system accounting needs before actual user information or billing information has been entered into the network systems.
- a temporary service account can make it possible or easier to use existing billing systems or other network systems to provide simplified provisioning, simplified activation or ambient services.
- a temporary service account can also become a permanent service account by replacing mock user or unassigned user information with actual user information, or a temporary service account may need to be replaced by a permanent service account when actual user information needs to be entered into the network systems, possibly including the billing or service profile databases.
- temporary or permanent device credentials and other information used/required for provisioning the device are generated with apparatus located at the manufacturer or in the distribution channel as discussed below.
- the apparatus includes a local onsite server that typically shares some aspects of the provisioning information (e.g., phone number, phone number range, MEID or MEID range, SIM number or SIM number range, IP address or IP address range, MAC address or MAC address range, other secure device credential elements) with a network provisioning database.
- the apparatus includes a server terminal, and the aforementioned portion of the credentials is generated by the network and shared with the local provisioning apparatus.
- the provisioning credentials are in part generated in the network and shared with the device while it is connected online to an activation server (e.g., activation server 160 ) that is connected to the access network.
- an activation server e.g., activation server 160
- a device when a device is provisioned and entered into the network provisioning database, it is associated with the automatic provisioning and/or activation sequence the device is intended to go through once it connects to the network or to the apparatus that will complete the process.
- one or more device parameters e.g., service owner, device type, OEM, plan type, IP address, security credential and/or software version
- this association information is stored in the network provisioning database for propagation of the provisioning profiles or activation profiles to the various network equipment elements.
- the network provisioning database is provided (e.g., in the network) that associates the pre-activation provisioning information (e.g., generated, as described herein, at time of manufacture, sometime during distribution, by the user on a website by a sales associate or other activation assistant, or by the network when a new device enters the automatic activation process).
- the pre-activation provisioning information informs the network whether or not to let the device onto an activation sequence when the device attempts access, and in some cases, also instructs the network to direct the device to a specific activation sequence including, for example, an activation server (or other activation sequencing apparatus) sequence as described herein.
- a central database is queried by other network equipment or the central database is included in one or more of the network elements (e.g., the AAA server and/or billing system, mobile wireless center 132 ), or the database is copied in part or in whole in various network elements (e.g., the central database, AAA server, mobile wireless center, billing system and/or gateways).
- the network elements e.g., the AAA server and/or billing system, mobile wireless center 132
- the database is copied in part or in whole in various network elements (e.g., the central database, AAA server, mobile wireless center, billing system and/or gateways).
- propagating the network equipment provisioning information for a given device or group of devices is accomplished with a network provisioning system that has access to the network provisioning database and is capable of programming the appropriate network equipment.
- this network equipment is referred to as “network management” equipment or “network provisioning” equipment.
- the AAA server 121 there are several functions that take part individually or in concert, including, for example, the AAA server 121 , service controller 122 (either with device based/assisted services through the service processor related embodiments or with network only embodiments as described herein), the mobile wireless center 132 (e.g., including the home location register (HLR) or other similar function referred to by other industry terms), the activation server(s) 160 , other network provisioning or management equipment attached to or associated with the billing database system, and/or some other equipment apparatus.
- the local database on the device, database in the AAA server and/or database elsewhere in network is provisioned to inform the gateway of the process for handling the pre-provisioned device according to, for example, the credentials.
- the device connection or communication can be directed (or routed) to a generic activation server that provides an activation sequence that is not necessarily determined by one or more of the specific device credential elements, partial credential elements, device profile or partial device profile that define something specific about the activation sequence for the device.
- the device in which the device is not recognized or authenticated as an activated device with associated service profile and/or service plan, the device can be directed (or routed) to an activation service (or other activation sequencing apparatus) that uses some part of the credentials or range of partial credentials or a portion of a partial or complete device profile to determine a desired pre-determined device specific or device group specific activation sequence that is implemented by a specific activation service sequence or other activation sequence apparatus.
- an activation service or other activation sequencing apparatus
- a portion of the device credentials or partial credentials can be used as a look-up index into a database that determines what the specific device activation sequence should be, and the device can be directed (or routed) to a specific activation server sequence or other activation sequencing apparatus.
- a database in the AAA server or database elsewhere in network is provisioned to inform the gateway what to do with a pre-provisioned device according to the credentials.
- devices can be authenticated (for activated devices), routed to activation servers (or other activation sequencing apparatus) or denied access.
- the AAA server (and/or other network elements) provide the above discussed look-up function for the above gateway description in which a lookup database, locally stored or stored in a central database, is queried to provide secondary routing information to the specific or generic activation servers.
- the pre-provisioned database is located in the billing system.
- the billing system accesses the pre-provisioned database (e.g., stored on the billing system or another network element) for the purpose of setting up temporary accounts or permanent accounts and associating those accounts with pre-activation status, activated free ambient or activated paying customer.
- all the required pre-provisioning or programming of the above network elements, or others is coordinated by the network provisioning system at some point after the partial or full device credentials have been associated with the device or reserved for a particular device type or service type.
- the network provisioning system also coordinates the information to or from the device provisioning apparatus that is described elsewhere.
- the automated or background provisioning, activation and ambient embodiments described herein can be accomplished with network based approaches, device based approaches, or network/device combination/hybrid based approaches.
- the access control for the provisioning process is accomplished in the device (e.g., a device based approach)
- the activation server can be located anywhere on the Internet, and the device will ensure that the activation process is conducted with the activation server while blocking other traffic from occurring.
- some or all of the ambient provisioning programming steps become steps to program the access control, traffic control, application control, bill by account rules, and/or other aspects in the service processor or service controller as described herein.
- the provisioning apparatus described herein can be a computer located in the user's home or business, and the user or an IT manager has access to a website that provides the provisioning information, in which the computer serves as the provisioning or software programming apparatus.
- the network itself possibly through an activation server 160 , website or other interface to the device, becomes the provisioning apparatus, in some cases, with the assistance of software on the device to affect the programming of provisioning information from the network or the communication of device credentials or other information to the network.
- this software can be a background process that runs without user interaction, a portal/widget program, a web browser based program, a WAP browser based program, and/or any other program that provides a counterpart function to the network functions effecting the provisioning (e.g., activation server).
- the activation server either initiates a specific provisioning sequence if device software is present to assist or routes to a website for manual entry if there is no software present.
- FIG. 64 illustrates another network architecture including a system located in the manufacturing or distribution chain for the device that provides the device provisioning or partial provisioning, and any pre-activation required for the device to later activate on the network in accordance with some embodiments.
- Device credential, software and settings server 6420 provides a link to the network functions that generate or provide device credentials, and/or associate device credentials with activation profiles or pre-activation profiles in the network equipment (e.g., the billing system 123 , service controller device control system 6225 , gateways 410 , 420 , base station 125 , credential generation and association server 6410 , activation server 160 , service download control server 1660 and/or other network apparatus).
- the billing system 123 the billing system 123 , service controller device control system 6225 , gateways 410 , 420 , base station 125 , credential generation and association server 6410 , activation server 160 , service download control server 1660 and/or other network apparatus.
- the link between the device credential, software and settings server 6420 to the central provider core network equipment can be over the Internet 120 (e.g., a secure link over the Internet) as shown or over another connection such as a leased line.
- the device credential, software and settings server 6420 obtains credentials or partial credentials from the network apparatus that generates them, illustrated by the credential generation & association server 6410 .
- Credential generation & association server 6410 need not be directly connected to the central provider core network 110 as shown, but can be located elsewhere (e.g., in another location connected by a secure Internet link).
- Credential generation & association server 6410 assigns credentials, or partial credentials, for use by device credential, software and settings server 6420 . When these credentials are assigned to a device, they are programmed, loaded or otherwise associated with the device by device credential provisioning apparatus 6430 , which is connected to the device wirelessly or via a wire line connection.
- a device software loading and programming apparatus 6440 provides software loading or device settings functions that form a portion or all of the provisioning or pre-provisioning device configuration, or form a portion or all of the device activation profile configuration, or form the device service owner, master agent or VSP device assignment or signature, and in some embodiments, using an activation tracking service (ATS) system.
- ATS activation tracking service
- the ATS monitors network connections and aspects of traffic that provide insight into which networks the device 100 is gaining access to, in some embodiments, for the purpose of ensuring that an OEM, master agent, device service owner or VSP is being compensated for devices that activate on a service provider network.
- the ATS agent connects to a server counterpart that records and, in some embodiments, also analyzes the service or network connection information to make a determination of the type of access service the device is receiving and, in some cases, determine which networks the device is activated on.
- the ATS is installed on the device in a manner that makes it difficult to tamper with or remove so that the entity that is intended to get credit for device service activation does get credit
- the ATS agent can be loaded into secure memory, it can be installed with software that makes it difficult to de-install, it can be installed on the modem possibly in secure memory, it can be installed in the BIOS, it can be installed deep in the OS kernel, it can be installed with one or more additional device agents that monitor the ATS agent and alert a network function or re-install it if tampered with).
- the SIM inventory 6450 is provided to illustrate that, in some embodiments, hardware elements (e.g., a SIM security module as shown) or hardware configurations are also installed or manipulated in device 100 and these operations and the recording of the resulting associations form a portion of the provisioning or pre-provisioning process.
- hardware elements e.g., a SIM security module as shown
- hardware configurations are also installed or manipulated in device 100 and these operations and the recording of the resulting associations form a portion of the provisioning or pre-provisioning process.
- the credentials or partial credentials are loaded, programmed, set, installed, read from the device or otherwise recorded, they are, in some cases, all associated together in a database that allows for later identification of the device and its appropriate provisioning and/or activation process through such associations. For example, this can involve reading device parameters such as MEID, MAC address, device type, or other information that is associated with the information being loaded or configured on the device.
- this credential configuration and association information is stored in the network equipment responsible using it to configure the network to activate the device in one of the various embodiments disclosed herein.
- Some embodiments include tying some or all of the activation provisioning steps and information settings together into a database that defines a higher level activation profile for a group of users(/devices), and a server is used to perform device and equipment programming for the devices in the group, including, for example, associating the following device information into the group definition: credentials, service owner or master agent, provisioning information and/or activation profile. Some embodiments further provide for this device group information being distributed to the various network equipment components required to activate the devices as discussed elsewhere. In some embodiments, this programming and device group association is accomplished using the VSP workstation server 4910 . For example, a device can be manufactured and distributed in a manner that provides flexible assignment of the device to a group that is assigned to an activation profile or a service owner.
- multiple activation servers 160 are provided (as shown), which illustrates that there can be multiple device activation servers 160 each with a different device activation experience and potentially controlled by a different VSP, service owner, service provider, OEM or master agent.
- a device 100 can be routed to the proper activation server 160 so that the device provisioning and activation process can be completed.
- all devices that are not activated are re-directed (or routed) to an activation server that reads one or more parameters in the device credentials.
- the device credential information can be determined either through the device identification information associated with the access network connection itself (e.g., MEID, IP address, phone number, security credentials, or other credentials identified for a device that gains access with the network), or with the aid of the device in a pre-arranged query-response sequence.
- the device can then be re-directed (or routed) to the appropriate activation server for that device, device group, device service owner or VSP.
- the same process described above can be accomplished with a single re-direction from a service gateway 420 or 410 , or another router enable network element.
- the gateway or network element itself decodes the device credential information as described herein and performs the correct re-direct (or route) to the appropriate activation server 160 for that device.
- the activation server 160 can be incorporated directly into the gateway 420 or 410 , the base station 125 or other network component.
- the activation server 160 can be incorporated into the service controller 122 or the service controller device control system 6225 .
- apparatus other than the activation server are used to facilitate provisioning of credentials or partial credentials, or activation, during manufacturing or device distribution, and, for example, these apparatus can augment, supplement, compliment or replace the activation server function.
- apparatus include, for example, device programming equipment (e.g., device credential provisioning apparatus 6430 , device software loading and programming apparatus 6440 or SIM inventory 6450 ), equipment that is networked into a central provider, MVNO or VSP database (e.g., device credential, software and settings server 6420 ) to gain access to provisioning information or activation information that is programmed into a device or group of devices, or to place device credential or partial credential information in a network database for later recognition, or to receive or communicate security information such as certificates for devices or SIM modules that will later be used to complete provisioning or complete activation or gain access to a network.
- device programming equipment e.g., device credential provisioning apparatus 6430 , device software loading and programming apparatus 6440 or SIM inventory 6450
- these apparatus can be networked into a service provider network or device database, an MVNO network or device database or a VSP network or device database.
- programming of the device credentials or other information associated with the service processor or device is provided, so that, for example, the device can be recognized by an activation server or similar network function at a later point in time so that provisioning or activation can be completed in an automated manner, potentially with reduced or no user involvement, that provides a provisioning or activation configuration that is in some way unique for the service provider or service provider partner, device type, user group, VSP, MVNO, master agent or other entity.
- this programming is provided in a manner that is difficult to change without the proper authorization so that the device is properly associated with the proper “service owner” or master agent (e.g., for the purpose of activation incentive payments).
- the device credential or other settings or software provisioning so that the settings or software are secure or protected, or so that if the software is removed, replaced or modified it is reported or replace or restored.
- VSP control of the provisioning, partial provisioning or activation of devices is provided during manufacture or at different points in the distribution channel.
- some of these embodiments allow the central provider to offer to service partners (e.g., VSPs, MVNOs, master agents, and/or OEMs) similar types of control for device activation experience design or device service assignment control (e.g., sometimes referred to as service provider device locking so that other service providers cannot provide primary access to the device) during the manufacturing or distribution process that are possible with devices manufactured and distributed for the central service provider.
- service partners e.g., VSPs, MVNOs, master agents, and/or OEMs
- similar types of control for device activation experience design or device service assignment control e.g., sometimes referred to as service provider device locking so that other service providers cannot provide primary access to the device
- the device is provisioned before the user obtains the device with permanent credentials, temporary credentials or partial credentials.
- the necessary credential programming of the device occurs during manufacture, at some point in the device distribution, such as at a distribution depot or in a store, or at the point of sale or point of shipment.
- provisioning of network information as discussed above is used, and the network information is provisioned at the same time, before or after the device information is provisioned.
- the device provisioning information is programmed with dedicated apparatus that connects to the device either with wires or wirelessly.
- the dedicated apparatus can be local to the location where the device is being provisioned, or it can be partially or entirely networked into a database or provisioning solution located elsewhere and operated by the central provider, a VSP, OEM or other entity.
- the apparatus to program the network portions of the provisioning information can also be networked and the operators who set up the required network programming for a device or group of devices may be in the vicinity of the servers that host the provisioning and management tools or they may network into the servers.
- provisioning system operators have full or partial control of any device provisioning equipment associated with the entity they work for (e.g., OEM, VSP or master agent) but only have remote access via secure terminal, secure website or other techniques to network into a central provider or VSP server farm in which they control or partially control the network portion of provisioning capabilities for that subset of devices that are assigned to the entity they work for with (e.g. OEM, VSP or master agent).
- provisioning is accomplished over the air on the mobile access network for mobile devices, or over the wired access network or WLAN connection for wired access networks, either before the user receives the device or after the user receives the device.
- the device can be connected to general purpose equipment, such as a computer to perform the programming required to complete provisioning.
- the device provisioning can be triggered by a user initiated sequence, or can be initiated by an automated background sequence at any time after the device is powered on.
- partial credentials that include information such as device type, OEM or service provider are used to assist in determining how to complete the provisioning, and the information can also include secure information, certificate or signature programmed into the partial credentials that is required for the network to perform the provisioning of the remaining credential information in the device and possibly the network.
- any network information used/required to provision the device or service is generated at the time the partial credentials are determined rather than beforehand.
- the device is activated for service before the user obtains the device with permanent credentials, temporary credentials or partial credentials, or with a permanent service account or a temporary service account.
- the necessary steps of provisioning and activating service for the device can occur during manufacture, at some point in the device distribution, such as at a distribution depot or in a store, or at the point of sale or point of shipment.
- the steps for activating service include one or more of the following: provision the device (e.g., with permanent, temporary or partial credentials), provision the necessary network databases and equipment to prepare them to recognize the device and associate it with the service profile and/or service plan, create or select the service account (e.g., permanent or temporary service account), select or create the service profile and/or service plan, program any elements in the device required to activate service (e.g., account ID, device aspects of the service profile and/or service plan), and program the necessary network databases and equipment with the required associations of device credentials and service profile and/or service plan policy settings.
- the device oriented programming portions of the service activation steps occur at the same time, before or after the network oriented programming portions of the service activation steps.
- the device activation information is programmed with dedicated apparatus that connects to the device via a wireless or wire line connection.
- the dedicated apparatus can be local to the location where the device is being provisioned, or the dedicated apparatus can be partially or entirely networked into a database or service activation solution located elsewhere and operated by the central provider, a VSP, OEM or other entity.
- the apparatus to program the network portions of the activation information can also be networked and the operators who set up the required network programming for a device or group of devices can be in the vicinity of the servers that host the service activation and management tools or they can network into the servers.
- activation server tools operators have full or partial control of any device activation apparatus associated with the entity they work for (e.g., OEM, VSP or master agent) but only have remote and partial access via secure terminal, secure website or other techniques to network into the network portion of the activation tools that are controlled by the central provider or VSP.
- the server tools operators can be restricted in some embodiments to providing network activation information or settings only for those devices or device groups that are assigned to the entity they work for with (e.g., OEM, VSP or master agent).
- the device control group restriction can be accomplished with a secure database that has secure sub-partitions for one or more entities so that they cannot impact the control of one another's network activation settings but can control their own devices.
- a centralized set of activation tools resources controlled by a central provider, VSP or other entity can be partitioned so that different entities can have partial or full control of the activation service definition for devices or groups of devices without impact or risk to others who share the network and activation tools resources.
- activation is accomplished with an over the air interface to a mobile device, or over the wired access network or WLAN connection for wired access networks, either before the user receives the device or after the user receives the device.
- the device can be connected to general purpose equipment such as a computer to perform the programming required to complete activation.
- the final device activation process can be triggered by a user initiated sequence, or can be initiated by an automated background sequence at any time after the device is powered on. In such cases, some embodiments call for a temporary service account that is used to bring the device onto the network before the user has input the information necessary to create a permanent service account.
- a temporary or permanent service account can be applied to the device at the time the device reaches the network, and the type of account, service profile and/or service plan can be influenced (e.g., partially determined or informed) or determined by information embedded in the device credentials or partial credentials, such as device type, device ID, SIM, OEM or service provider.
- the device credentials can also include secure information, certificate or signature that can be required by the network to perform the activation steps for temporary or permanent service account status.
- the service profile and service plan are set up for ambient services as described herein.
- the device is activated during the manufacturing or distribution process, and then the activated device status is suspended.
- the temporary or permanent service account is set up, with appropriate service profile and/or service plan and temporary or permanent credentials, in some networks and billing systems the service can often be more easily resumed once suspended as compared to provisioning and activating the device from scratch.
- the device is then later resumed (or re-activated) when some event triggers the resume process, such as when it ships to the end user or when the end user attempts to use it. This process prevents the network from needing to manage credentials and accounts for devices that have been activated but are not yet on the network.
- provisioning is accomplished at least in part with temporary credentials in a manner which is automated and convenient for the user or device owner.
- at least some subset of the temporary credential elements replaced at a later point in time by permanent credential elements in a manner that is also automated and convenient for the user or device owner.
- the temporary credential set is pre-programmed into the device along with a temporary or permanent service account including service profile during the manufacturing or distribution process so that the device is activated with temporary credentials when it ships.
- the aforementioned pre-programming is performed for the network via a secure set of server access equipment that networks into the network databases used to define the service profile and/or the service plan.
- a subset of the temporary credentials is recycled once it is replaced, if a temporary service account is not activated or used after some period of time, if a permanent account is not activated or used after some period of time, or if the credentials subset is revoked from the device for some other reason.
- more than one device is assigned one or more elements of the temporary credentials, such as the phone number, which may be limited in supply.
- a network will accept more than one set of temporary credentials, one or more redundant elements, for two or more different devices.
- the temporary credentials are used to log onto the network to conduct an over the air or over the network activation process in which an activation server reads at least a portion the device credentials to determine some aspect of how the device service profile.
- the aforementioned over the air activation process is accomplished in the background without user intervention.
- the over the air activation process is initiated when the user first attempts to use the device or when the user first attempts to access the network or upon user request or approval.
- the over the air activation process is initiated using a temporary service account for the device and/or network to gain access to the network.
- the over the air activation process is initiated after the user has entered the information required to create a permanent user account into the device or into the network.
- the user is required to enter the aforementioned user information before using the device or using some aspect of the device.
- the temporary service account is replaced by a permanent service account some time after the user has entered the necessary information to create a permanent account into the device or network.
- the over the air activation process is initiated using a permanent service account assignment for the device and/or network to gain access to the network.
- the service profile is assigned to the device and/or network during the aforementioned over the air activation to be a pay for service profile with a free trial period.
- the service profile assigned to the device and/or network during the aforementioned over the air activation includes pre-pay, post-pay, session based pay or pay as you go options for service.
- various embodiments disclosed herein are particularly well suited for control or pre-pay services.
- the service profile that is assigned to the device and/or network during the aforementioned over the air activation is an ambient service profile providing service access before all the user information is available to assign a permanent account.
- the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing a service upgrade selection option interface to the user.
- the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing transaction services to the user.
- the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing bill by account functionality for the network.
- the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing some amount of free networking or information service to entice the user to use the other ambient services.
- the aforementioned ambient service is at least partially implemented with device based service activity control or control assistance. In some embodiments, the aforementioned ambient service is at least partially implemented by gateways, routers or switches in the network that are programmed according to the ambient access profile for the device to implement the ambient policies for network access control, routing control, traffic control or service monitoring and reporting for bill by account.
- activation is accomplished at least in part with a temporary service account in a manner that is automated and convenient for the user or device owner.
- at least some subset of the temporary service account is replaced at a later point in time by permanent service account subset in a manner that is also automated and convenient for the user or device owner.
- the temporary service account settings e.g., including the service profile settings and/or the service plan settings
- the aforementioned pre-programming for the network is performed via a secure set of server access equipment that networks into the network databases used-to define the service profile and/or the service plan.
- the device is suspended once it is activated but before the user is using it, and then resumed before or commensurate with the point in time that the user begins to use it.
- some subset of the temporary service account is recycled once it is replaced, if the temporary service account is not used after some period of time, if the temporary service account is not upgraded to a permanent service account after some period of time, or if the activation is revoked from the device for some other reason.
- more than one device is assigned to the same temporary service account.
- a network accepts more than one device on the same temporary service account.
- a device includes or is associated with two or more temporary service accounts, in which at least a subset of the temporary service account elements are different, so that if one account is already being used to access the network then one or more reserve accounts can be drawn upon to gain access to the network.
- the temporary service account is associated with a temporary credentials set. In some embodiments, the temporary service account is associated with a permanent credentials set.
- un-activated devices are detected by the network routing equipment (e.g., service gateways or routers in hierarchical networks or base stations with embedded gateways in flat networks) and the device routing is programmed to re-direct un-activated devices to an activation server network destination.
- the activation server can first inspect the information associated with the device to determine if the device belongs to the list of devices, device types or device groups that the network is programmed to provide access to.
- the information used to determine this can include device type, service provider, phone number, device ID, SIM ID or configuration, secure information used to qualify the device, IP address, MAC address, user, user group, VSP, OEM, device distributor, service distributor (master agent), service processor presence or configuration, presence or configuration of other software or hardware.
- activation definition information embedded in the credentials, or associated with some portion of the credentials, or programmed additionally on the device that informs the activation server as to the service profile and/or service plan and/or service account that should be established for the device. If activation information (the service profile, service plan and/or service account information) is found through association with the device credentials (e.g., device ID, phone number, IP address, MAC address, SIM or other security credentials) rather than being read directly from information embedded in the device or device credentials, then the pertinent aspects of the credentials can be used as a cross reference to look up the service plan and/or service profile information stored in a database networked to or within the activation server.
- the device credentials e.g., device ID, phone number, IP address, MAC address, SIM or other security credentials
- the activation information can include information to define a wide variety of service plans and service profiles that when properly implemented on the network functions, and perhaps device if necessary, can provide for a wide range of service activity policies, service billing policies, transaction billing policies and service account types that can be associated with the device over the air or over the network.
- the activation server once the activation server has determined the activation information from the device or from a look up based on some aspect of the device credentials, then the activation server initiates the necessary network settings and billing database entries to be programmed by sending the service profile instructions to the network provisioning and activation apparatus and the service plan instructions to the billing system. In some embodiments, the activation server can then also send the any necessary service profile and/or service plan settings required for the device to a provisioning and activation support software function on the device, such as various embodiments of the service processor, so that the device provisioning and activation can be completed.
- the provisioning can be with permanent credentials or temporary credentials, and the service account that is set up may be permanent or temporary.
- the activation process described above is completed perhaps before the user has entered some or all of the user information necessary to set up a permanent service account, and, in these cases, a temporary service account can be set up.
- the activation process can be completed in the background before the user has completed an attempt to access the network and the service profile can be set up to provide ambient services to a temporary service account.
- the user is required to enter the information required to establish a permanent service account prior to gaining full use of the device, either on the device, on a computer or in the store, so that by the time the user begins using the device the above activation embodiments can provide for ambient services activation with permanent account status so that the user can purchase a service upgrade or any transaction without entering any more account information.
- a device status is changed from a temporary service account to a permanent service account. If the device is activated with a temporary service account, and the user information is available to set up a permanent account, then if the billing system rules and interfaces allow for such, the user information can be changed from the mock information to the actual user information while maintaining the same account identifiers in the billing system. If the billing system will not allow for such, then the user information can be used to establish a new account, the device credentials can be re-associated with the new account, in some cases, after modifying one or more of the device credential parameters, and the network functions can be re-programmed as required, and, in some cases, the device can be re-programmed as required to accommodate the new permanent account.
- code on the device pulls a temporary or permanent set of credentials.
- the network associates the device with an ambient service profile according to one or more of the following: embedded device information identifying device type, service owner (e.g., VSP), user group, or user, or device ID is cross referenced to a database that is populated some time from manufacturing time to post sale where the database provides information identifying device type, service owner (e.g., VSP), user group, or user.
- the device is then re-directed accordingly (e.g., for device based this is a matter of setting the policies or loading the software for the service processor, for the network based approach this is a matter of populating the routing tables and service profile).
- credentials can be re-cycled after a period of time, and/or some portion of the credentials can be redundant with other devices.
- this is essentially a dynamic service for (temporarily) assigning device credentials, and the duration of the temporary credential validity for that device ID can be time limited to give the user time to activate a real account or a free trial, session limited, or a longer duration of time that is perhaps refreshed each time the device logs on.
- the device could also already have permanent or temporary credentials but not have a service account.
- the above process can be used to assign a temporary or permanent service account as well. Once the service account is assigned and the appropriate service profile is propagated to the network elements, the device can then be directed to or use the appropriate activation profile service activities or the appropriate ambient service activities.
- the device is activated in the background in a manner that is virtually transparent to the user.
- the device is programmed to seek the activation server system described above as soon as it is turned on, or as soon as some other event occurs like the user using the device or the user attempting to gain access.
- the device connects to the network and the gateways or routers re-direct the device to an activation server, as discussed above.
- the activation server either derives information from the device that informs the server what service the device should be activated with, or the server derives that information from a database look up with a portion of the device credentials as the cross reference parameter.
- the activation server causes all the necessary network settings and billing database entries to be configured/programmed by sending the service profile instructions to the network provisioning and activation apparatus and the service plan instructions to the billing system.
- the activation server can then also send the any necessary service profile and/or service plan settings required for the device to a provisioning and activation support software function on the device, such as various embodiments of the service processor, so that the device provisioning and activation can be completed.
- the provisioning can be with permanent credentials or temporary credentials
- the service account that is set up can be permanent or temporary.
- background activation is performed using the aforementioned activate/suspend process.
- the device is programmed to seek to resume service as soon as it is turned on, or as soon as some other event occurs like the user using the device or the user attempting to gain access.
- the device attempts to connect to the network and the gateways or routers re-direct the device to an activation server as described herein.
- the activation server either derives information from the device that informs the server that the device is ready to resume service, or the server derives that information from a database look up with a portion of the device credentials as the cross reference parameter. Once the server is aware of this information, it sends a message to resume service to the billing system, or other network function that controls the suspend/resume function, and the service is resumed.
- background activation is performed as described below.
- the service processor and the credentials are pre-programmed during the manufacturing or distribution process to provide the desired service profile support and/or billing profile support for the desired initial ambient service. As described herein, this programming can be accomplished with dedicated apparatus at the manufacturer or distribution depot. Furthermore, the party responsible for defining the service (e.g., typically the central provider, OEM, VSP, distributor or master agent) can network into the service processor programming apparatus to control service processor and/or credential programming for all or a subset or group of the devices or device types locally available.
- the service processor enabled device is programmed to seek the activation server system described above as soon as it is turned on, or as soon as some other event occurs like the user using the device or the user attempting to gain access.
- the activation server is the access control server previously discussed or the access control server can act in concert with another server that performs the activation function.
- the device connects to the network and the gateways or routers re-direct the device to the activation server.
- the activation server can communicate with the service processor to verify the service processor security credentials, agents and configuration.
- the activation server determines that the pre-programmed settings stored in the service processor need to be modified to provide the latest version of the desired service, or if the service processor agent software needs to be updated, then this can be accomplished prior to completing the activation process.
- the activation server causes the necessary network settings and billing database entries to be programmed by sending the service profile instructions to the network provisioning and activation apparatus and the service plan instructions to the billing system.
- the service processor can perform some or much of the service activity control or control assistance, the service control options are generally larger than without the service processor, and there can be less configuration to perform for other networking equipment to complete the provisioning and activation process.
- the provisioning can be with permanent credentials or temporary credentials, and the service account that is set up can be permanent or temporary.
- pre-programming and pre-activation of devices with temporary credentials and a temporary service account are used to ship devices that are pre-activated. Given that the credentials are temporary and can be recycled when the permanent credentials are assigned, concerns about using up too many pre-assigned credentials are reduced. In embodiments in which a portion of credentials elements can be used for multiple devices, this concern is further reduced. If there is a concern about too many activated devices being assigned that are not actually active and generating service revenue, then the suspend/resume process discussed herein can be employed. In some embodiments, the temporary credentials and/or temporary account can be replaced with permanent credentials and/or account assignments at any time as follows.
- the device When a pre-programmed event in the device is triggered, then the device initiates a program that seeks the aforementioned activation server or another server that has the capability of fulfilling the device request to exchange the temporary credentials for permanent credentials and/or exchange the temporary account for a permanent account.
- the event that triggers the credential exchange can be the same or different than the event that triggers the service account exchange.
- the service account exchange can typically be triggered by the point in time that the user enters account information.
- the aforementioned ambient service is partly implemented with a combination of the techniques for pre-provisioning during manufacturing or distribution and at least partially implementing the service activity control (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage) required for implementing ambient using the service policy provisioning capabilities in the data path gateways, routers or switches in the network.
- the gateways, router or switches are pre-programmed as discussed herein according to the ambient access profile for the device to implement the ambient policies for network access control, routing control, traffic control or service monitoring and reporting for bill by account.
- the provisioning credential elements are not all pre-programmed before the device ships, but a subset of the credential elements are programmed using the activation server technique discussed herein. This over the air automated provisioning is combined with the activation server reading the device credentials to derive the service activity control settings for the gateways, routers or switches that will result in the desired ambient services activity controls.
- the aforementioned ambient service is implemented with a combination of the techniques for pre-activation during manufacturing or distribution and at least partially implementing the service activity control (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage) required for implementing ambient using the service policy control capabilities in the data path gateways, routers or switches in the network.
- the gateways, router or switches are programmed to recognize the pre-activated device credentials as discussed herein according to the ambient access profile for the device to implement the ambient policies for network access control, routing control, traffic control or service monitoring and reporting for bill by account.
- the device activation profile and/or service account are not pre-programmed in the network and/or the device before the device ships but the activation profile and/or service account are programmed using the activation server technique discussed herein. This over the air automated provisioning is combined with the activation server reading the device credentials to derive the service profile activity control settings for the gateways, routers or switches that results in the desired ambient services activity controls.
- a VSP capability is enabled by providing a secure network connection to the service policy settings tools that define the device pre-provisioning settings, the device pre-activation service profile settings, the network equipment service activity control policy settings (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage), and the network billing system database.
- the service policy settings tools that define the device pre-provisioning settings, the device pre-activation service profile settings, the network equipment service activity control policy settings (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage), and the network billing system database.
- the networking equipment is implemented to secure device service group domains in which the service policies for a group of devices can be controlled.
- the pre-provisioning and pre-activation techniques are substituted with the over the air activation server techniques discussed herein, and a secure device group partition capability is provided in the activation server as well so that the activation server device group partition control capabilities can be added to the secure device group partition control capabilities of the network gateways, routers and/or switches, the device programming tools and the billing system to form a VSP partition solution for over the air activation of various device/service plan combinations.
- the device groups are relatively small so that beta trials of arbitrarily large or small size can be designed and implemented by defining a service control group as described above, and after fine tuning and perfecting the beta trial settings the device group can be expanded to publish the automated provisioning and activation service settings to a larger user or device group for production services.
- device based service activity control assistance (e.g., based on the various service processor embodiments described herein) is combined with simplified provisioning techniques described herein so that service processor enabled devices can be shipped with pre-provisioned credentials (temporary or permanent) or can obtain credentials in an automated manner that is convenient and efficient for the user or device owner.
- the service processor embodiments in combination with the manufacturing and supply chain credentials and provisioning apparatus described elsewhere provide various approaches for provisioning pre-provisioned service processor enabled devices.
- the service processor embodiments in combination with the activation server variants discussed above provide various approaches for over the air or over the network simplified post-sale provisioning for service processor enabled devices. For example, these embodiments can also be used for ambient services given that as discussed herein the service processor has capability to implement service profile policies for deep control of ambient service activity control.
- provisioning includes provisioning partial device credentials that include, for example, a secure certificate that is used to authorize full credential provisioning and/or activation by performing a process for a later look-up/validation of the full device credentials.
- the look-up/validation of the full device credentials can be performed by a gateway, router or similar network device that re-directs to a provisioning server and/or activation server or other network components that either: (1) recognizes the partial credentials that serve as a reference to direct the device communication to a specific provisioning/activation server determined from the partial credentials; or (2) does not recognize the partial credentials, and directs the device communication to a less specific provisioning/activation server that is not necessarily associated with a reference to the partial credentials.
- the partial device credentials e.g., temporary or permanent credentials
- the partial credentials are read (e.g., and/or other credentials can be looked up based on the partial credentials as described above).
- the device is authorized if the proper credentials and/or secure certificate is present.
- the device credential provisioning is then completed (e.g., using activation server commands or settings to a device based software and/or hardware element), and the credentials are, in some cases, also communicated to the various network equipment elements.
- partial or full device credential provisioning is performed, such as described above.
- a service account e.g., temporary or permanent service account
- a service account is created or looked up based on the partial device credentials (e.g., a user account associated with the device through embedded partial or full credentials or a look up process, or based on a dynamically created/assigned temporary account associated with the device through embedded partial or full credentials).
- An initial service profile and, in some cases, an initial service plan e.g., service control policy settings including a billing profile
- a look up process e.g., based on the device type and/or partial or full device credentials.
- the device is then programmed to enable access with the service profile and plan, and, in some cases, the various network components/elements are programmed to enable the service profile and plan, and, in some cases, proper entries in the billing system are made or confirmed, and the device credentials are, thus, activated for service.
- the above described provisioning and/or activation processes are performed with the provisioning server(s) and/or activation server(s) in the background with reduced, minimal or no user input required, for example, after the device is sold to the user and the user turns on the device so that by the time the user attempts to access the service using the device, the provisioning and/or activation process is already completed.
- device based service activity control assistance (e.g., based on the service processor embodiments) is combined with simplified activation techniques described herein so that service processor enabled devices can be shipped with pre-activated accounts (temporary or permanent), or can obtain activated account status in an automated manner that is convenient and efficient for the user or device owner.
- the service processor embodiments in combination with the manufacturing and supply chain activation and provisioning apparatus described elsewhere provide various approaches for pre-activated service processor enabled devices.
- the service processor embodiments in combination with the activation server variants discussed above provide various approaches for over the air or over the network simplified post-sale account activation for service processor enabled devices. These embodiments can also be used for ambient services given that as discussed herein the service processor has capability to implement service profile policies for deep control of ambient service activity control.
- the service processor can be combined with the pre-provisioning and pre-activation techniques described above to create an ambient service solution that will work on roaming networks in which the central provider or VSP has no control or minimal control over the network elements.
- the device includes a service processor pre-programmed for ambient service activity control as discussed herein, and the device credentials and other settings are pre-provisioned and pre-activated for the central provider network, all of which is described in numerous embodiments disclosed herein. Provided that the service provider has a roaming agreement with other service providers, or provided that the device may gain access to the roaming network, when the device is roaming it will be capable of ambient connectivity with bill by account functionality and all the other features of ambient.
- the ambient service activity control policies can be different for different roaming networks to accommodate the varying network costs and performance. Also, for example, it would be permissible to sign up for initial services or additional upgrade services with the central provider while roaming on the roaming partner network.
- This also allows for creating a VSP or MVNO for the purpose of creating a clearing house for central provider service activations according to geography or user choice.
- the MVNO or VSP can provide consistent ambient services across multiple carriers and multiple geographies while still maintaining a good degree of cost control.
- the VSP or MVNO can then provide service purchase options to the user based on the carrier networks available to the device, or the VSP or MVNO can broker the user off to any of the carriers by activating the device onto the carriers main central provider service.
- these embodiments provide flexible capabilities for activating a device or group of devices with a broad range of service profiles and service plans by simply programming the device with the proper credentials at some time during manufacturing or distribution, or simply programming a database associated with the network so that a portion of the device credentials can be used to look up the desired service profile and service plan.
- various activation embodiments described herein are highly convenient for the end user and need not, in many cases, involve any human intervention.
- the service processor 115 , service controller 122 , policy implementation and/or profile implementation and various embodiments disclosed herein are applicable to conventional communication products as well as machine to machine applications. For example, if the machine to machine device includes a service processor 115 with an activated account, then the service profile settings can be optimized for machine communications to provide only the limited access required to support the particular machine to machine application. This allows for cost optimized access services and prevents the machine to machine device or access modem from being misappropriated and used for some other service access than that intended.
- the device can be automatically provisioned and activated on the service network with a service account when deployed, thus eliminating the need for costly or time consuming human intervention.
- the various embodiments that make it simpler to design, manufacture, test and deploy devices may also be equally applied to machine to machine devices. These embodiments include the service processor 115 developers kit and the automated provisioning and activation management tools among others. Also, the service analysis and test tools and the virtual service provider embodiments can also be applied to machine to machine applications.
- an intermediate networking device is a communications device in which the service processor 115 is configured at least in part to allow the intermediate networking device to act as a service intermediary or intermediate connection between the network and one or more end point devices (e.g., communications devices).
- a service controller 122 or other suitable network functions can be employed to assist with the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments described herein.
- an intermediate networking device does this by implementing the service policies required for assisting service usage control of the intermediate networking device and connecting the network to provide services to one or more end point devices that are connected to the intermediate networking device.
- the intermediate networking device also monitors the service use activities of the intermediate networking device and/or the end point devices connected to the intermediate networking device.
- the intermediate networking device and/or end point device service usage is verified to ensure that the service usage is within the expected ranges for the policies that are implemented.
- the intermediate networking device connects with the network using one modem technology and connects with the end point devices using one or more additional technologies.
- an intermediate networking device connects the end point devices to the network by passing, bridging, forwarding, routing, traffic shaping or otherwise allowing the end point devices to communicate with the network.
- Example intermediate networking device embodiments include a Wi-Fi to WWAN (e.g., 2G, 3G, 4G or other wireless wide area networking access technology) bridge or router device, a Wi-Fi to DSL, cable or fiber gateway device, a WWAN to DSL or Cable femto cell device, a WWAN and Wi-Fi to DSL, Cable or fiber back-hauled femto cell device, a WWAN to WWAN router device, a WWAN to WLAN, WPAN or LAN bridge, router or gateway device, or a WWAN back up connection device for an enterprise router.
- WWAN Wi-Fi to WWAN
- WWAN wireless wide area networking access technology
- An intermediate networking device can also be provided in some embodiments by including a bridging, forwarding or routing function between two modems in a communications enabled device that connects to the network.
- an intermediate networking device configuration can be a cell phone, smart phone, mobile internet device or any other mobile device that includes a WWAN modem and a Wi-Fi, WLAN, WPAN or LAN connection that can be used to connect to other end point devices.
- the mobile device WWAN modem can connect to the network
- a service processor 115 can be included on the device processor to assist monitoring, controlling and billing for services between the WWAN network and end point devices connected to a Wi-Fi modem.
- a service controller 122 or other suitable network functions can be employed to assist with verifiable service usage monitoring, control and verification as disclosed in numerous embodiments disclosed throughout herein.
- the Wi-Fi modem can be configured in access point mode or in ad hoc mode to communicate with other end point devices in the area covered by the mobile device WLAN modem.
- a service processor 115 and a service controller 122 or other suitable network functions can be employed to enable the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments described herein.
- Another example embodiment is a notebook or sub-notebook computer with a WWAN modem and a Wi-Fi, Ethernet, Firewire, Bluetooth, near field or Zigbee modem in which the notebook processor has a service processor 115 running on the notebook processor and the service processor 115 is used to assist monitoring, control and billing for services communicated between the WWAN network and end point devices connected to the notebook or sub-notebook WLAN, LAN or WPAN.
- a Wi-Fi hot spot with a service processor 115 capability.
- Another example embodiment is a WWAN back up modem in an access network router where the back up modem connection to the WWAN network is used when the main wired network connection goes down, and a router processor or a WWAN back up modem processor runs a service processor 115 to assist monitoring, controlling and billing for services between the WWAN network and the access router (e.g., the service provider may only wish to enable a connection when the main wired network is down to ensure that the WWAN modem is not used for everyday access).
- a service processor 115 and a service controller 122 or other suitable network functions can be employed to enable the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments described herein.
- Another example embodiment is a two-way home gateway configured to perform various functions such as reading power consumption of the home and/or components in the home, providing WLAN, WPAN or LAN connectivity for such components or to the power meters/controllers attached to such components, providing a WWAN or WAN connection to a network that reads, records, monitors and/or controls the home and/or component power consumption, and possibly to provide other wide area network services for other devices in the home such as computers or entertainment electronics in a similar manner to the WWAN, DSL, cable and fiber gateway embodiments.
- the WLAN, WPAN connections can be made with one or more of Wi-Fi, Zigbee, Bluetooth, NFC or any other suitable wireless modem technology, and any desired wired LAN connections may be made with one or more of Ethernet, USB, Firewire, data over cable, data over power line or any other suitable wired modem technology.
- the WWAN connections can be made with one or more of 2G (e.g. CDMA 1 ⁇ RT, GPRS), 3G (e.g. WCDMA UMTS/HSPA/non-MIMO HSPA+, CDMA EVDOrA/B, 802.16d/e WiMax), 4G (e.g.
- a service processor 115 and a service controller 122 or other suitable network functions can be employed to enable the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments disclosed throughout herein.
- an intermediate networking device can be used to connect one end point device to a network and assist in implementing service policies, or an intermediate networking device can connect multiple end point devices to one or more networks and assist in implementing service policies.
- an intermediate networking device can be associated with one service profile, one service plan or one service account, or an intermediate networking device can be associated with multiple service profiles, multiple service plans or multiple service accounts.
- end point devices connected to an intermediate networking device can have service usage policies implemented in aggregate for all end point devices, or service policies can be implemented differentially for different end point devices.
- an intermediate networking device can have a network connection associated with a single account and manage QOS between end point devices under one umbrella service profile or collection of profiles.
- an intermediate networking device can treat all connected end point devices equally from a service sharing or QOS perspective so that, for example, service usage is based on end point device demand and/or contention.
- an intermediate networking device differentiates service QOS between different end point devices based on end point device service demand or service usage patterns, EDP device type or device group, end point device user or user group, end point device service account status or service plan status, or end point device application type, and/or traffic type or service type.
- the service processor 115 function assisting intermediate networking device implementation can be included on the intermediate networking device, can be included in part on the intermediate networking device and one or more end point devices, or can be implemented mainly or entirely on one or more end point devices.
- an intermediate networking device can be constructed in which end point devices connect to the intermediate networking device and gain access services to a WWAN network through a WWAN/Wi-Fi enabled intermediate networking device that is supplied with services associated with a single account and service profile.
- the intermediate networking device service processor 115 can assist in monitoring, control and billing for WWAN service usage for all end point devices in the area covered by the intermediate networking device Wi-Fi link.
- end point devices receive service on first come first serve basis with no differentiation.
- end point devices receive fair distribution of services so that if one end point device is using more significantly more service than the other end point devices, or is demanding more service than the intermediate networking device service profile settings provide for a single end point device (e.g., “bandwidth hogging”), then the high demand end point device is throttled and the other end point devices are not.
- end point devices receive hierarchical distribution of services based on one or more of service type, device type, user type, and/or account status.
- an intermediate networking device can provide for a large or unlimited number of end point devices to connect to the network and simply control aggregate service usage parameters for the intermediate networking device WWAN connection.
- the intermediate networking device limits the number of end point devices that are allowed to connect to the WWAN network according the end point device count limits programmed in the service processor 115 service profile settings in the intermediate networking device.
- end point device traffic can be identified by various end point device credential aspects including, for example, by Wi-Fi ID, MAC ID, IP address, user ID, LAN tag, end point device agent credentials, and/or browser token or cookie.
- the intermediate networking device service account can be billed for overall service usage and/or by number of end point device connections allowed or experienced.
- one ore more aspects of the service usage policy implementation and/or profile implementations in the service processor 115 profile settings can be increased.
- network based service usage measures for verification can be applied to the intermediate networking device just as if the intermediate networking device were an end point device.
- network based service usage measures e.g., IPDR information
- IPDR information can be used to perform network verification checks to ensure that intermediate networking device service usage is within acceptable ranges based on intermediate networking device policy settings as similarly described with respect to various device embodiments.
- a notification can be sent to the intermediate networking device main account owner.
- the main intermediate networking device account owner can also be required to acknowledge the notification.
- the notification can also be sent to one or more other users of the intermediate networking device connection, including possibly all users.
- Other actions that can be taken if the network based intermediate networking device service usage measure does not match the policy limits set on the service processor 115 include notify the user, notify the user and require acknowledgement, bill the user for service overage, suspend the end point device, quarantine the end point device, SPAN the end point device, and/or alert network manager or alert an automated network troubleshooting function.
- a device based usage measure can be verified against a network based service usage measure.
- the individual end point device service usage measures logged or reported from the end point devices and/or the intermediate networking device can be aggregated to form a total intermediate networking device usage measure that is compared to an aggregate intermediate networking device usage measure logged or reported in the network. In some embodiments, if these measures do not match, then an error condition results and an action is taken. In some embodiments, the aggregate intermediate networking device service usage measure is compared to the aggregate network based service usage measure and as long as these two measures are within an acceptable tolerance, then the intermediate networking device service usage measures are trusted and can be used for deeper intermediate networking device and end point device usage measures for service control and/or billing than may be possible in the network.
- the individual end point device service usage measures gained from the intermediate networking device or end point device can be used to verify end point device service usage versus service policy allowances.
- end point device service usage measures are compared with intermediate networking device measures for the same end point devices.
- the IPDR records for one or more networks can include individual end point device service usage information. This is the case for example when the IPDRs include information broken down by end point device credential, such as IP address or other end point device credential.
- end point device credential such as IP address or other end point device credential.
- intermediate networking device embodiments can be employed in which the individual end point device service usage information measured in the network can be compared with the service usage policy allowances or limits for the end point device.
- the individual end point device service usage measures from an end point device service usage monitor and/or an intermediate networking device service usage monitor can be compared with the network based service usage information to verify an end point device and/or an intermediate networking device service usage monitor is operating properly.
- service usage and service usage monitor reports can be periodically verified by performing a SPAN function on the traffic for an intermediate networking device.
- the SPAN traffic can be analyzed in a real-time manner or in a non-real-time manner in the network and the results can be compared with the intermediate networking device or end point device service policies or service usage measures.
- the synchronized device notification and acknowledgement embodiments can also be employed in the case in which one service account is applied to the intermediate networking device.
- the service usage counters in the intermediate networking device can be synchronized or updated with the network based measures and the differences between the two may be minimized.
- the service usage notification can be sent to one or more of the end point devices connected to the intermediate networking device. For example, the notification can be sent to the intermediate networking device manager or service owner, all end point devices or the most active end point devices.
- user preference feedback can be collected from one or more of the service users connected to the intermediate networking device.
- user preferences or user service selections or service settings are collected from one user or a subset of end point devices used by the service subscriber.
- more than one service user can provide preference information or service settings even if there is only one user account.
- user preferences can be used set service control policies that provide the user with their selected balance of cost and service capability in a manner that meets network neutrality requirements.
- the service monitoring and customer resource management information collected on the intermediate networking device or end point devices can be filtered according to user privacy preferences to maintain the level of user privacy selected by the user.
- Adaptive intermediate networking device policy implementation can also be performed in the intermediate networking device service processor 115 embodiments, as similarly described with respect to various device embodiments.
- the service policy implementation for the intermediate networking device can be adapted by the service processor 115 agents (e.g., policy control agent 1692 working to control the settings in policy implementation agent 1690 , and/or another service processor agent or function) to achieve a higher level service usage goal.
- the usage goals or adaptation can be based on aggregate end point device usage for the intermediate networking device network services, and in some embodiments, the higher level usage goals or adaptation can apply to one or more individual end point devices.
- an intermediate networking device service profile that includes the service capabilities that are to be delivered to a multitude of end point devices or users.
- some end point devices or users have a different profile within the intermediate networking device service processor 115 with differentiated capabilities as compared to the intermediate networking device service processor 115 profile for other end point devices or users. This is the case for some of the examples provided herein.
- These multi-end point device or multi-user service profiles in the intermediate networking device service processor 115 can share services equally or can allow more capable access services to some end point devices or users than others.
- a service profile implemented by the intermediate networking device service processor 115 for one end point device or user is different than that in the service profile implemented by the service processor 115 for another end point device or user (e.g., providing differentiated service profile implementations by end point devices and/or users).
- End point devices can be uniquely identified for purposes involving implementation of different service profiles in the intermediate networking device service processor 115 agents (e.g., depending on the embodiment, service monitor agent 1696 , policy implementation agent 1690 , policy control agent 1692 , application interface agent 1693 and/or other service processor agents or functions) based on a number of parameters, such as IP address, local area network address (e.g., Wi-Fi address), MAC address end point device ID, user ID, and/or end point device application layer tag. This allows for independent service usage monitoring and control for different end point devices or users.
- IP address e.g., IP address, local area network address (e.g., Wi-Fi address), MAC address end point device ID, user ID, and/or end point device application layer tag.
- an intermediate networking device also bridges services to end point devices or users that have individually managed service profiles, service plans or service accounts.
- individual end point device service policy implementation and/or service profile implementation can be accomplished by classifying end point device service usage according to an end point device identifier so that service monitoring, control assistance and reporting may be differentiated between one or more end point devices. These end point device identifiers can then be associated with a different service plan or account in the service processor 115 and/or billing system 123 .
- the end point device or user specific service usage monitoring, reporting, notification and control assistance can be accomplished by running one or more profiles for each end point device or each user.
- billing can also be implemented with a single account encompassing service usage for all users or end point devices connected to an intermediate networking device, or for individual users, end point devices, user groups or end point device groups connected to an intermediate networking device. As similarly described with respect to the service profile, this is accomplished by associating service usage events and associated billing events with a end point device identifier, user identifier, end point device group identifier, and/or user group identifier.
- end point devices or users connect to more than one intermediate networking device with the same service account, service plan or service profile.
- the intermediate networking device requires an authentication sequence for the end point device or user before allowing connection to the network through the intermediate networking device. This authentication sequence can involve the end point device communicating an active account or admission credential with the intermediate networking device.
- the intermediate networking device can compare the credential with a local database or may query a database in the network to admit the end point device to the intermediate networking device network connection.
- the service processor 115 service profile settings for the end point device are applied and service is then established as discussed herein. In these cases, the verification can be accomplished as described herein.
- the intermediate networking device will accurately assist in control and reporting of service usage for the different end point devices or users, and the appropriate service policy controls and/or billing can be maintained.
- the intermediate networking device can offer the end point device or user a service sign up experience.
- This experience can be implemented in a number of ways, including a website, WAP site, portal, download of agent software, and other methods.
- an automated recognition of new devices can redirect unauthorized end point devices to browse into a website, WAP site, or portal site located on the intermediate networking device or in the network. If the site is located on the intermediate networking device, it can be cached and refreshed at a time of day when the network is not overly busy.
- the user or end point device selects the plan choice they desire, inputs account information and, in some embodiments, downloads device agent software to aid in network service policy implementation and/or profile implementation with the intermediate networking device.
- the information is logged into the network data base, the service account is established and the intermediate networking device service profile for that user or end point device is activated and the user can begin using the service.
- a website, WAP site, or portal site located in the intermediate networking device can be used to provide the end point device user with a service usage monitor interface and a service purchase interface for cases in which the end point device does not posses any special software to allow it to display a more specialized service usage monitor function for information received from the intermediate networking device or network service usage counters.
- the service usage monitor for the intermediate networking device can be synchronized, as similarly described with respect to various device embodiments.
- the service usage notification system can also display cost data from a usage to cost look-up function.
- the service usage notification system can display projected service usage or projected cost, as similarly described with respect to various device embodiments.
- the service usage monitor to drive these service notification embodiments can be located on one or more of the end point device, the intermediate networking device or the network.
- verification can be performed on the service controls for the end point device or user service usage.
- the end point device or user service usage comparison with usage policy settings can be verified in the ways described herein. If the usage is found to be out of policy, then any of the out of policy actions described herein can be performed, including, for example, notify the end user, notify and require acknowledgement, bill for overage, suspend, quarantine, SPAN, and/or flag to network manager or network error handling function.
- the verification methods shown in and described with respect to FIGS. 22 , 23 , 26 , 27 and 28 can be applied for the embodiments where intermediate networking devices have multiple account, multiple service plan, multiple service profile, multiple end point device, and/or multiple user capabilities.
- Ambient services can be employed on the intermediate networking device and the ambient services can thus be provided to the end point devices. It will be apparent that the ambient service profile embodiments disclosed herein can similarly be applied to the intermediate networking device, and then the intermediate networking device can supply those ambient services to end point devices connected to the intermediate networking device. It will also be apparent that the intermediate networking device can provide an ambient service profile as described herein to end point devices or users that have not yet signed up for service, while providing other paid for service profiles to end point devices or users that have signed up for service.
- Bill by account embodiments can similarly be applied to the intermediate networking device embodiments.
- bill by account can be used in embodiments in which all end point devices or users are connected to the intermediate networking device under one account, or to embodiments in which some end point devices or users are accounted for separately with different service accounts, service plans or service profiles.
- end point device or user identification credential aspects discussed herein can be used in a bill by account profile to account for any end point device or service activity.
- billing event reports for those activities that include the end point device or user identifiers can also be provided for billing mediation and reconciliation down to the individual end point device or user level. For example, this allows for very deep service monitoring and billing capabilities with intermediate networking devices.
- the intermediate networking device embodiments described above also have uses in machine to machine applications. It will be apparent that if the end point device includes the correct credentials to gain access to an existing account, or to allow an automated provisioning and activation account to be established, then the end point device can be connected to the network through the intermediate networking device without human intervention. Furthermore, the service profile that is established with the end point device for machine to machine communications can be set up to provide the access required to support the machine to machine application allowing for low cost access services and preventing the end point device from being misused for some service other than that intended. For example, the verification techniques and embodiments disclosed herein can similarly be applied to such machine to machine applications.
- identifiers discussed above for bill by account mediation with accounting down to the individual end point device or user level can be combined with a billing mediation server in the network that accepts intermediate networking device billing events with end point device identification or user identification indexed billing, performs the necessary bill by account mediation functions, formats the billing events into the format used by the billing system, and transmits the mediated billing information to the billing system 123 .
- the intermediate networking device service processor 115 functionality can be split. The division ranges from some or all of the service processor 115 on the device to some or all of the service processor 115 on the intermediate networking device.
- all of the service processor 115 is on the intermediate networking device.
- the end point device does not participate in service processor 115 functions and has no service processor 115 interface software.
- the end point device has small subset of service processor 115 capabilities, including, for example, a service notification UI or a logon client with credentials.
- service monitoring is implemented on the end point device or on both the end point device and in the intermediate networking device.
- the end point device has additional service processor 115 capabilities including, for example, application layer tagging that associates application layer activity with service processor 115 service monitoring or service policy implementation and/or service profile implementation information.
- Another example involves assigning IP addresses in the intermediate networking device networking stack to the end point devices so that different types of end point device traffic can be routed into service processor 115 traffic shaping queues, each queue having a policy profile implementation engine, and application layer tagging information or similar traffic indentifying information is used to determine which policy implementation engine the traffic should be routed to in order to accomplish the desired traffic shaping for the traffic type, application type, service type, and/or content type.
- the traffic control policy is implemented on the end point device either with an application layer traffic controller, or by implementing more of the service processor 115 functionality, as similarly described with respect to various device embodiments.
- the service processor 115 functionality is implemented on the end point device and the intermediate networking device functionality can be reduced to a bridging, forwarding or routing function between the end point devices and the network that performs little or no service control, monitoring and/or billing functions.
- the service usage monitoring agents can also be provided on the end point device to aid in verification.
- the software can be loaded at time of manufacture or during distribution, loaded later, and/or made available for download through the intermediate networking device.
- the end point device agent SW is downloaded through the end point device, there can be locally cached copies of the SW for one or more OS variants stored in a cache on the intermediate networking device, with the cache being updated over the network at convenient or conducive times, or the software can be downloaded live over the network when it is needed by the end point device.
- Logging the service usage to download this software is another example in which bill by account functionality can be used to track network traffic that may not be desirable to bill to a end point device owner or user, and bill by account functionality can be used to log and mediate such usage out of the user or end point device owner's bill.
- Any end point device agent software required to connect to the intermediate networking device can also be implemented as a service processor 115 developer's kit as described herein and distributed to aid manufacturers, service provider and virtual service providers in bringing new devices onto networks with intermediate networking device capability.
- the voice and data traffic is routed through a VPN tunnel controlled by the service processor 115 and connected to a network element, such as the transport gateway or another specified traffic concentration destination for the femto cell.
- the voice traffic, the data traffic or both can be routed in secure or open Internet channels to different destinations, or the data can be routed directly to the Internet destination specified by the packets.
- the femto cell intermediate networking device controls the femto cell frequencies or local frequency channel strength surveys over the intermediate networking device control channel.
- the service processor 115 has a VPN connection to a network base station hand off controller to assist in handoff to and from the WWAN network and/or has the capability to instruct the end point device and the base station handoff controller.
- the service provider desires to set up a service processor 115 profile to get the end point device to connect to the femto cell even if it has a strong signal with one or more WWAN base stations so that the WWAN traffic may be offloaded.
- the service processor 115 can form a secure control plane link with network AAA functions to manage authorization and admission of end point devices the femto cell has not yet admitted, or the network policies can require re-authorization every time a end point device attempts access.
- the verifiable traffic monitoring, control and billing functions described herein can be applied to various application embodiments.
- the intermediate networking device service policy verification techniques disclosed herein, as similarly described with respect to various device embodiments, can similarly be applied to the femto cell intermediate networking device embodiments.
- the service provider desires to keep the number of end point devices or users that access an intermediate networking device below a certain count specified in the service processor 115 profile. In some embodiments, this is accomplished by controlling the number of IP addresses allowed onto the intermediate networking device local area side connection. In some embodiments, this is facilitated by observing the end point device identification parameters available in the end point device traffic. In some embodiments, this is facilitated by observing the traffic patterns to determine the likely number of devices connecting to the network. For example, traffic demand patterns can be examined to determine how many users are likely to be demanding access at one time.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- General Business, Economics & Management (AREA)
- Economics (AREA)
- Marketing (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Educational Administration (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Technology Law (AREA)
- Operations Research (AREA)
- Databases & Information Systems (AREA)
- Probability & Statistics with Applications (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Cardiology (AREA)
- Primary Health Care (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
- Meter Arrangements (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Various embodiments are disclosed for a services policy communication system and method. In some embodiments, a network device executes a service controller for a plurality of device groups, in which the service controller includes a capability to securely partition one or more device group database partitions, each device group partition includes service controller system settings, and each device group includes a plurality of communication devices controlled by a virtual service provider.
Description
- This application claims priority to U.S. Provisional Patent Application No. 61/206,354 (Attorney Docket No. RALEP001+) entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Jan. 28, 2009, U.S. Provisional Patent Application No. 61/206,944 (Attorney Docket No. RALEP002+) entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 4, 2009, U.S. Provisional Application No. 61/207,393 (Attorney Docket No. RALEP003+) entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed Feb. 10, 2009, and U.S. Provisional Patent Application No. ______ (Attorney Docket No. RALEP004+) entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed on Feb. 13, 2009, which are incorporated herein by reference for all purposes.
- With the advent of mass market digital communications and content distribution, many access networks such as wireless networks, cable networks and DSL (Digital Subscriber Line) networks are pressed for user capacity, with, for example, EVDO (Evolution-Data Optimized), HSPA (High Speed Packet Access), LTE (Long Term Evolution), WiMax (Worldwide Interoperability for Microwave Access), and Wi-Fi (Wireless Fidelity) wireless networks increasingly becoming user capacity constrained. Although wireless network capacity will increase with new higher capacity wireless radio access technologies, such as MIMO (Multiple-Input Multiple-Output), and with more frequency spectrum being deployed in the future, these capacity gains are likely to be less than what is required to meet growing digital networking demand.
- Similarly, although wire line access networks, such as cable and DSL, can have higher average capacity per user, wire line user service consumption habits are trending toward very high bandwidth applications that can quickly consume the available capacity and degrade overall network service experience. Because some components of service provider costs go up with increasing bandwidth, this trend will also negatively impact service provider profits.
- Various embodiments of the invention are disclosed in the following detailed description and the accompanying drawings.
-
FIG. 1 illustrates a simplified (e.g., “flattened”) network architecture in accordance with some embodiments. -
FIG. 2 illustrates another simplified (e.g., “flattened”) network architecture including an MVNO (Mobile Virtual Network Operator) relationship in accordance with some embodiments. -
FIG. 3 illustrates another simplified (e.g., “flattened”) network architecture including two central providers in accordance with some embodiments. -
FIG. 4 illustrates a network architecture including a Universal Mobile Telecommunications System (UMTS) overlay configuration in accordance with some embodiments. -
FIG. 5 illustrates a network architecture including an Evolution Data Optimized (EVDO) overlay configuration in accordance with some embodiments. -
FIG. 6 illustrates a network architecture including a 4G LTE and Wi-Fi overlay configuration in accordance with some embodiments. -
FIG. 7 illustrates a network architecture including a WiMax and Wi-Fi overlay configuration in accordance with some embodiments. -
FIG. 8 illustrates another simplified (e.g., “flattened”) network architecture including multiple wireless access networks (e.g., 3G and 4G Wireless Wide Area Networks (WWANs)) and multiple wire line networks (e.g., Data Over Cable Service Interface Specification (DOCSIS) and Digital Subscriber Line Access Multiplexer (DSLAM) wire line networks) in accordance with some embodiments. -
FIG. 9 illustrates a hardware diagram of a device that includes a service processor in accordance with some embodiments. -
FIG. 10 illustrates another hardware diagram of a device that includes a service processor in accordance with some embodiments. -
FIG. 11 illustrates another hardware diagram of a device that includes a service processor in accordance with some embodiments. -
FIG. 12 illustrates another hardware diagram of a device that includes a service processor in accordance with some embodiments. -
FIG. 13 illustrates another hardware diagram of a device that includes a service processor implemented in external memory of a System On Chip (SOC) in accordance with some embodiments. -
FIG. 14 illustrates another hardware diagram of a device that includes a service processor implemented in external memory of a System On Chip (SOC) in accordance with some embodiments. -
FIGS. 15A through 15C illustrate hardware diagrams of a device that include a service processor and a bus structure extension using intermediate modem or networking device combinations in accordance with various embodiments. -
FIG. 16 is a functional diagram illustrating a device based service processor and a service controller in accordance with some embodiments. -
FIG. 17 is another functional diagram illustrating the device based service processor and the service controller in accordance with some embodiments. -
FIG. 18 is another functional diagram illustrating the device based service processor and the service controller in which the service processor controls the policy implementation for multiple access network modems and technologies in accordance with some embodiments. -
FIG. 19 is another functional diagram illustrating the service processor and the service controller in accordance with some embodiments. -
FIG. 20 is another functional diagram illustrating the service processor and the service controller in accordance with some embodiments. -
FIG. 21 is another functional diagram illustrating the service processor and the service controller in accordance with some embodiments. -
FIG. 22 provides a table summarizing various service processor agents (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments. -
FIG. 23 provides a table summarizing various service controller server elements (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments. -
FIG. 24 is a functional diagram illustrating the service control device link of the service processor and the service control service link of the service controller in accordance with some embodiments. -
FIG. 25 is a functional diagram illustrating framing structure of a service processor communication frame and a service controller communication frame in accordance with some embodiments. -
FIGS. 26A through 26E provide tables summarizing various service processor heartbeat functions and parameters in accordance with some embodiments. -
FIGS. 27A through 27G provide tables summarizing various device based service policy implementation verification techniques in accordance with some embodiments. -
FIGS. 28A through 28C provide tables summarizing various techniques for protecting the device based service policy from compromise in accordance with some embodiments. -
FIG. 29 is a functional diagram illustrating a device communications stack that allows for implementing verifiable traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 30 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 31 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 32 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 33 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 34 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 35 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 36 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 37 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. -
FIG. 38 is a functional diagram illustrating a device service processor packet processing flow in accordance with some embodiments. -
FIG. 39 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments. -
FIG. 40 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments. -
FIG. 41 provides a table summarizing various privacy levels for service history reporting in accordance with some embodiments. -
FIGS. 42A through 42F provide tables summarizing various service policy control commands in accordance with some embodiments. -
FIGS. 43A through 43B are flow diagrams illustrating a flow diagram for a service processor authorization sequence as shown inFIG. 43A and a flow diagram for a service controller authorization sequence as shown inFIG. 43B in accordance with some embodiments. -
FIGS. 44A through 44B are flow diagrams illustrating a flow diagram for a service processor activation sequence as shown inFIG. 44A and a flow diagram for a service controller activation sequence as shown inFIG. 44B in accordance with some embodiments. -
FIGS. 45A through 45B are flow diagrams illustrating a flow diagram for a service processor access control sequence as shown inFIG. 45A and a flow diagram for a service controller access control sequence as shown inFIG. 45B in accordance with some embodiments. -
FIG. 46 is a functional diagram illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments. -
FIGS. 47A through 47B are transactional diagrams illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments. -
FIG. 48 illustrates a network architecture including a service controller device control system and a service controller analysis and management system in accordance with some embodiments. -
FIG. 49 illustrates a network architecture for an open developer platform for virtual service provider (VSP) partitioning in accordance with some embodiments. -
FIG. 50 illustrates a network architecture including a billing to service controller interface for accommodating minimum changes in existing central billing, AAA and/or other network components in accordance with some embodiments. -
FIG. 51 illustrates a network architecture for locating service controller device control functions with AAA and network service usage functions in accordance with some embodiments. -
FIG. 52 illustrates a network architecture for locating service controller device control functions in the access transport network in accordance with some embodiments. -
FIG. 53 illustrates a network architecture for locating service controller device control functions in the radio access network in accordance with some embodiments. -
FIG. 54 illustrates a network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments. -
FIG. 55 illustrates another network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments. -
FIG. 56 illustrates a 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments. -
FIG. 57 illustrates a network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments. -
FIG. 58 illustrates another 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments. -
FIG. 59 illustrates another network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments. -
FIG. 60 illustrates a 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments. -
FIG. 61 illustrates another network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments. -
FIG. 62 illustrates another 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments. -
FIG. 63 illustrates another network architecture including the VSP workstation server in communication with the 4G/3G/2G DPI/DPC gateways in accordance with some embodiments. -
FIG. 64 illustrates another network architecture including a system located in the manufacturing or distribution chain for the device that provides the device provisioning or partial provisioning, and any pre-activation required for the device to later activate on the network in accordance with some embodiments. - The invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer readable storage medium; and/or a processor, such as a processor configured to execute instructions stored on and/or provided by a memory coupled to the processor. In this specification, these implementations, or any other form that the invention may take, may be referred to as techniques. In general, the order of the steps of disclosed processes may be altered within the scope of the invention. Unless stated otherwise, a component such as a processor or a memory described as being configured to perform a task may be implemented as a general component that is temporarily configured to perform the task at a given time or a specific component that is manufactured to perform the task. As used herein, the term ‘processor’ refers to one or more devices, circuits, and/or processing cores configured to process data, such as computer program instructions.
- A detailed description of one or more embodiments of the invention is provided below along with accompanying figures that illustrate the principles of the invention. The invention is described in connection with such embodiments, but the invention is not limited to any embodiment. The scope of the invention is limited only by the claims and the invention encompasses numerous alternatives, modifications and equivalents. Numerous specific details are set forth in the following description in order to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention may be practiced according to the claims without some or all of these specific details. For the purpose of clarity, technical material that is known in the technical fields related to the invention has not been described in detail so that the invention is not unnecessarily obscured.
- With the development and increasing proliferation of mass market digital communications and content distribution, communication network capacity gains are being outpaced by growing digital networking demand. For example, some industry experts project average wireless device usage of four devices per subscriber, with a mixture of general purpose devices like smart phones and computers along with special purpose devices like music players, electronic readers, connected (e.g., networked) cameras and connected gaming devices. In addition, wire line user service consumption habits are trending toward very high bandwidth applications that can quickly consume the available capacity and degrade overall network service experience if not efficiently managed. Because some components of service provider costs go up with increasing bandwidth, this trend will also negatively impact service provider profits.
- There is a need for a communication system and method that provides for flexible service plans and management of user network services to provide consumer choice of more refined service plan offerings and efficient management of network capacity.
- Also, it is becoming increasingly important to more deeply manage the level of services delivered to networked devices to provide cost effective services that match growing digital networking usage patterns. For example, access providers can move away from only billing for basic access and move toward billing for higher level service delivery with example services including rich Internet access and email, application based billing, content distribution, entertainment activities, information or content subscription or gaming. In addition, a growing number of new special purpose and general purpose networked devices are fueling demand for new service plans, for example, tailored to the new device usage models (e.g., a special service plan for an e-book reader device).
- As network capabilities grow and new networked device offerings grow, access network service providers will realize increasing value in opening up their networks to allow innovation and expanded offerings for network service consumers. However, opening up the networks to provide efficient third party definition of alternative service and billing models requires more flexible service and billing policy management solutions. For example, machine to machine applications such as telemetry, surveillance, shipment tracking and two way power control systems are example new applications that would require new offerings to make such available to network service customers. The need to customize service offerings for these new applications requires more efficient methods for defining, testing and launching new services with more refined control of service functions and service costs. In some embodiments, this means billing for different types of service elements, such as total traffic, content downloads, application usage, information or content subscription services, people or asset tracking services, real time machine to machine information or electronic commerce transactions.
- In some embodiments, network user capacity is increased and user service costs are reduced by managing and billing for service consumption in a more refined manner (e.g., to satisfy network neutrality requirements). By managing service consumption in a user friendly manner, the overall service capacity required to satisfy the user device needs can be tailored more closely to the needs of a given user thereby reducing user service costs and increasing service provider profits. For example, managing service usage while maintaining user satisfaction includes service usage policy implementation and policy management to identify, manage and bill for service usage categories, such as total traffic consumption, content downloads, application usage, information or content subscription services, electronic commerce transactions, people or asset tracking services or machine to machine networking services. As described herein, service activity is used to refer to any service usage or traffic usage that can be associated with, for example, an application; a network communication end point, such as an address, uniform resource locator (URL) or other identifier with which the device is communicating; a traffic content type; a transaction where content or other material, information or goods are transacted, purchased, reserved, ordered or exchanged; a download, upload or file transfer; email, text, SMS, IMS or other messaging activity or usage; VOIP services; video services; a device usage event that generates a billing event; service usage associated with a bill by account activity (also referred to as billing by account) as described herein; device location; device service usage patterns, device user interface (UI) discovery patterns, content usage patterns or other characterizations of device usage; or other categories of user or device activity that can be identified, monitored, recorded, reported, controlled or processed in accordance with a set of verifiable service control policies. As will be apparent to one of ordinary skill in the art in view of the embodiments described herein, some embodiments identify various service activities for the purpose of decomposing overall service usage into finer sub-categories of activities that can be verifiably monitored, categorized, cataloged, reported, controlled, monetized and used for end user notification in a manner that results in superior optimization of the service capabilities for various levels of service cost or for various types of devices or groups. In some embodiments, it will be apparent to one of ordinary skill in the art that the terms service activity or service usage are associated with categorizing and possibly monitoring or controlling data traffic, application usage, communication with certain network end points, or transactions, and it will also be apparent that in some embodiments the term service activity is intended to include one or more of the broader aspects listed above. The shortened term service usage can be used interchangeably with service activity, but neither term is intended in general to exclude any aspect of the other. In some cases, where the terms service usage or service activity are used, more specific descriptors such as traffic usage, application usage, website usage, and other service usage examples are also used to provide more specific examples or focus in on a particular element of the more encompassing terms.
- In some embodiments, employing this level of service categorization and control is accomplished in a manner that satisfies user preferences. In some embodiments, employing this level of service categorization and control is accomplished in a manner that also satisfies government rules or regulations regarding open access, for example, network neutrality requirements. In some embodiments, service management solutions that also collect and/or report user or device service usage or service activity behavior to determine how best to meet the user's simultaneous desires for service quality and lower service costs are disclosed. For example, such monitoring and reporting are accomplished in a manner that includes approval by the user and in a manner that also protects the privacy of user information and service usage behavior or service activity history.
- In some embodiments, a system and method is disclosed for increasing network user capacity for wireless networks in the face of increasing service demand per user by providing for a greater number of base stations, also sometimes referred to as access points, base terminals, terminal nodes or other well known acronyms, to be more easily and/or more cost effectively deployed. For example, to simplify the process of deploying base stations, the installation complexity and the network infrastructure required for the base station to obtain backhaul service to the various networks that users desire to connect with are reduced.
- In some embodiments, dense base station deployments are simplified by reducing the requirement to aggregate or concentrate the base station traffic through a specific dedicated core network infrastructure, so that the base stations connect to the desired user networks through a more diverse set of local loop, back bone and core routing options. This approach also reduces network infrastructure equipment, installation and maintenance costs. In some embodiments, this is accomplished by distributing the network traffic policy implementation and control away from the core network by providing for more control for service policy implementation and management on the end user device and, in some embodiments, in the end user device with respect to certain service policies and the network (e.g., control plane servers) with respect to other service policies. For example, this approach facilitates connecting the base stations directly to the local loop Internet with a minimum of specific dedicated networking infrastructure.
- In some embodiments, service and transaction billing event capture and logging are distributed to the device. For example, providing service and transaction billing event capture and logging at the device provides a greater capability to monitor, classify and control deeper aspects of service usage or service activity at the device as compared to the relatively less capability for the same in the network infrastructure (e.g., for certain traffic flows, such as encrypted traffic flows). Furthermore, billing at the device provides for very specialized with many different billing and service plans for different device and service usage or service activity scenario combinations without the problem of attempting to propagate and manage many different deep packet inspection (DPI) and traffic shaping profiles in the networking equipment infrastructure. For example, service billing at the device can provide for more sophisticated, more specialized and more scalable billing and service plans.
- Another form of billing that needs improvement is electronic commerce transaction billing with device assisted central billing. Today, most central billing and content distribution models require either centralized content distribution maintained by the central service provider or central billing authority, or a centralized ecommerce website or portal traffic aggregation system controlled by the central service provider or central billing provider, or both. In such systems, content and transaction providers such as media providers, application developers, entertainment providers, transaction website providers and others must adapt their mainstream electronic offering and commerce systems, such as shopping experience websites, to fit within the various proprietary customized infrastructure and content storage solutions for ecommerce markets, such as BREW® (Binary Runtime Environment for Wireless from Qualcomm® Inc.), Symbian OS (from Symbian Software Ltd) and
Apple iPhone 3G App Store (from Apple Inc.). This approach requires a large amount of unnecessary custom interface development and stifles open market creativity for HTTP, WAP or portal/widget based shopping destinations and experiences. As disclosed below, a superior approach includes device based transaction billing for an open ecosystem in which a central billing provider provides users and ecommerce transaction providers with a central billing solution and experience that does not require extensive custom development or ecommerce infrastructure interfacing. - In some embodiments, products that incorporate device assisted service policy implementation, network services and service profiles (e.g., a service profile includes a set of one or more service policy settings for the device for a service on the network) are disclosed, as described below. For example, aspects of the service policy (e.g., a set of policies/policy settings for the device for network services, typically referring to lower level settings, such as access control settings, traffic control settings, billing system settings, user notification settings, user privacy settings, user preference settings, authentication settings and admission control settings) that are moved out of the core network and into the end user device include, for example, certain lower level service policy implementations, service usage or service activity monitoring and reporting including, for example, privacy filtering, customer resource management monitoring and reporting including, for example, privacy filtering, adaptive service policy control, service network access control services, service network authentication services, service network admission control services, service billing, transaction billing, simplified service activation and sign up, user service usage or service activity notification and service preference feedback and other service capabilities.
- As discussed below, product designs that move certain aspects of one or more of these service profile or service policy implementation elements into the device provide several advantageous solutions to the needs described above. For example, benefits of certain embodiments include the ability to manage or bill for a richer and more varied set of network services, better manage overall network capacity, better manage end user access costs, simplify user or new device service activation, simplify development and deployment of new devices with new service plans (e.g., service profile and billing/costs information associated with that service profile), equip central service providers with more effective open access networks for new third party solutions, simplify the equipment and processes necessary to deploy wireless base stations and simplify the core networking equipment required to deploy certain access networks.
- As discussed below, there are two network types that are discussed: a central provider network and a service provider network. The central provider network generally refers to the access network required to connect the device to other networks. The central provider network generally includes the physical layer, the Media Access Control (MAC) and the various networking functions that can be implemented to perform authentication, authorization and access control, and to route traffic to a network that connects to the control plane servers, as discussed below. The service provider network generally refers to the network that includes the control plane servers. In some embodiments, a central provider network and a service provider network are the same, and in some embodiments, they are different. In some embodiments, the owner or manager of the central provider network and the owner or manager of the service provider network are the same, and in some embodiments, they are different.
- In some embodiments, control of the device service policies is accomplished with a set of service control plane servers that reside in the access network or any network that can be reached by the device. This server based control plane architecture provides for a highly efficient means of enabling third party control of services and billing, such as for central carrier open development programs or Mobile Virtual Network Operator (MVNO) relationships. As device processing and memory capacity expands, moving to this distributed service policy processing architecture also becomes more efficient and economical. In some embodiments, several aspects of user privacy and desired network neutrality are provided by enabling user control of certain aspects of device based service usage or service activity reporting, traffic reporting, service policy control and customer resource management (CRM) reporting.
- In many access networks, such as wireless access networks, bandwidth capacity is a valuable resource in the face of the increasing popularity of devices, applications and content types that consume more bandwidth. To maintain reasonable service profit margins, a typical present service provider practice is to charge enough per user for access to make service plans profitable for the higher bandwidth users. However, this is not an optimal situation for users who desire to pay less for lower bandwidth service usage or service activity scenarios.
- Accordingly, in some embodiments, a range of service plan pricing can be enabled that also maintains service profitability for the service provider, for example, by providing a more refined set of management and control capabilities for service profiles. For example, this approach generally leads to service management or traffic shaping where certain aspects of a service are controlled down based on service policies to lower levels of quality of service. Generally, there are three problems that arise when these techniques are implemented. The first problem is maintaining user privacy preferences in the reporting of service usage or service activity required to set, manage or verify service policy implementation. This problem is solved in a variety of ways by the embodiments described below with a combination of user notification, preference feedback and approval for the level of traffic information the user is comfortable or approves and the ability to filter service usage or service activity, in some embodiments, specifically traffic usage or CRM reports so that only the level of information the user prefers to share is communicated. The second problem is satisfying network neutrality requirements in the way that traffic is shaped or services are managed. This problem is solved in a variety of ways as described in the embodiments described below by empowering the user to make the choices on how service usage, service activity, traffic usage or CRM data is managed down to control costs, including embodiments on user notification and service policy preference feedback. By allowing the user to decide how they want to spend and manage their service allowance or resources, a more neutral or completely neutral approach to network usage can be maintained by the service provider. The third problem is to help the user have an acceptable and enjoyable service experience for the lower cost plans that will result in much wider scale adoption of connected devices and applications but are more constrained on service activity usage or options or bandwidth or traffic usage. As lower cost service plans are offered, including plans where the basic connection service may be free, these service plans will require service provider cost controls to maintain profitability or preserve network capacity that result in lower limits on service usage or service activity. These lower service usage or service activity limit plans will result in more users who are likely run over service usage limits and either experience service shutdown or service cost overages unless they are provided with more capable means for assistance on how to use and control usage for the lower cost services. This problem is solved in a variety of ways with a rich collection of embodiments on user notification, service usage and cost projection, user notification policy feedback, user service policy preference feedback, and adaptive traffic shaping or service policy implementation. As described herein, some embodiments allow a wide range of flexible and verifiable service plan and service profile implementations ranging from examples such as free ambient services that are perhaps sponsored by transaction revenues and/or bill by account sponsored service partner revenues, to intermediately priced plans for basic access services for mass market user devices or machine to machine communication devices, to more expensive plans with very high levels of service usage or service activity limits or no limits at all. Several bill by account embodiments also provide for the cataloging of service usage that is not a direct benefit to end users but is needed for basic maintenance of the device control channels and access network connection, so that the maintenance traffic service cost can be removed from the user billing or billed to non-user accounts used to track or account for such service costs. These embodiments and others result in a service usage or service activity control capability that provides more attractive device and service alternatives to end users while maintaining profitability for service providers and their partners.
- In some embodiments, the above described various embodiments for device based service policy and/or service profile communications control are implemented using network based service control, for example, for satisfying various network neutrality and/or privacy requirements, based on indication(s) received from the device (e.g., user input provided using the device UI using the service processor) and network based service control (e.g., using a DPI service monitor or DPC policy implementation and/or other network elements).
- In some embodiments, a virtual network overlay includes a device service processor, a network service controller and a control plane communication link to manage various aspects of device based network service policy implementation. In some embodiments, the virtual network overlay networking solution is applied to an existing hierarchical network (e.g., for wireless services), and in some embodiments, is applied to simplify or flatten the network architecture as will be further described below. In some embodiments, the large majority of the complex data path network processing required to implement the richer service management objectives of existing hierarchical networks (e.g., for wireless services) are moved into the device, leaving less data path processing required in the edge network and in some cases even less in the core network. Because the control plane traffic between the service control servers and the device agents that implement service policies can be several orders of magnitude slower than the data plane traffic, service control server network placement and back-haul infrastructure is much less performance sensitive than the data plane network. In some embodiments, as described further below, this architecture can be overlaid onto all the important existing access network architectures used today. In some embodiments, this architecture can be employed to greatly simplify core access network routing and data plane traffic forwarding and management. For example, in the case of wireless networks, the incorporation of device assisted service policy implementation architectures can result in base stations that directly connect to the Internet local loop and the data traffic does not need to be concentrated into a dedicated core network. This results, for example, in a large reduction in backhaul cost, core network cost and maintenance cost. These cost savings can be re-deployed to purchase and install more base stations with smaller cells, which results in higher data capacity for the access network leading to better user experience, more useful applications and lower service costs. This flattened networking architecture also results in latency reduction as fewer routes are needed to move traffic through the Internet. In some embodiments, the present invention provides the necessary teaching to enable this powerful transformation of centralized network service architectures to a more distributed device based service architectures.
- Device based billing can be compromised, hacked and/or spoofed in many different ways. Merely determining that billing reports are being received from the device, that the device agent software is present and properly configured (e.g., the billing agent is present and properly configured) is insufficient and easily spoofed (e.g., by spoofing the agent itself, providing spoofed billing reports using a spoofed billing agent or providing spoofed agent configurations). Accordingly, in some embodiments, verifiable device assisted and/or network based service policy implementation is provided. For example, verifiable service usage and/or service usage billing can be provided as described herein with respect to various embodiments.
- While much of the below discussion and embodiments described below focus on paid service networks, those of ordinary skill in the art will appreciate that many of the embodiments also apply to other networks, such as enterprise networks. For example, the same device assisted network services that create access control services, ambient activation services and other service profiles can be used by corporate IT managers to create a controlled cost service policy network for corporate mobile devices. As another example, embodiments described below for providing end user service control can also allow a service provider to offer parental controls by providing parents with access to a website with a web page that controls the policy settings for the access control networking service for a child's device.
- Network Architecture for Device Assisted/Based Service Control
-
FIG. 1 illustrates a simplified (e.g., “flattened”) network architecture in accordance with some embodiments. As shown, this provides for a simplified service infrastructure that exemplifies a simplified and “flattened” network architecture in accordance with some embodiments that is advantageous for wireless network architectures. This also reduces the need for complex data path protocol interaction between the base station and network infrastructure. For example, in contrast to a complex edge and core network infrastructure connecting base stations to the central service provider network, as shown thebase stations 125 are connected directly to theInternet 120 via firewalls 124 (in some embodiments, thebase stations 125 include the firewall functionality 124). Accordingly, in some embodiments, a central provider network is no longer required to route, forward, inspect or manipulate data plane traffic, because data plane traffic policy implementation is conducted in thedevice 100 by theservice processor 115. However, it is still an option, in some embodiments, to bring data plane traffic in from thebase stations 125 to a central provider network using either open or secure Internet routing if desired. Base station control plane communication for access network AAA (Authentication, Authorization, and Accounting)server 121, DNS/DHCP (Domain Name System/Dynamic Host Configuration Protocol)server 126, mobile wireless center 132 (sometimes referenced to in part as a home location register (HLR) or other acronym) or other necessary functions are accomplished, for example, with a secure IP tunnel or TCP connection between the central provider network and the base stations. Thebase station 125 is used to refer to multiple base station embodiments where the base station itself is directly connected to the RAN, or where the base station connects to a base station controller or base station aggregator function that in turn connects to the RAN, and all such configurations are collectively referred to herein asbase station 125 inFIG. 1 and most figures that follow thatreference base station 125 as described below. - As shown, the central provider access network is both 3G and 4G capable, the
devices 100 can be either 3G, 4G or multi-mode 3G and 4G. Those of ordinary skill in the art will also appreciate that in the more general case, the network could be 2G, 3G and 4G capable, or the device could be 2G, 3G and 4G capable with all or a subset of Global System for Mobile (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) 1×, High Speed Packet Access (HSPA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE) and WiMax modem capability. If the devices are single mode, then the3G devices 100 will be activated with a service profile applied toservice processor 115 that is consistent with the 3G network capacity and speed, and the 4G devices will be activated with service profiles applied toservice processor 115 that are consistent with 4G network capacity and speed. In both cases, thesame service controller 122 manages services for both sets of devices in accordance with some embodiments. If the devices are multimode, then theservice processor 115 can be activated with a dual mode service profile capability in which the service profile for 3G offers a similar rich set of services as the service profile for 4G but with, for example, scaled back bandwidth. For example, this approach is allows central providers to offer a richer set of service offerings with 3G and then migrate the same set of service offerings to 4G but with higher performance. In particular, this approach allows 3G to 4G rich service migration to occur, for example, with the only change being the increased bandwidth settings in the service profiles that will be available in 4G at the same cost as 3G with lower service profile bandwidth settings. - In some embodiments, if the devices are multimode, a network selection policy implementation within
service processor 115 is provided, or in some embodiments, a network selection policy is driven by policy decisions made inservice controller 122 based on service availability reports received fromservice processor 115. The network selection policy allows the selection of the network that corresponds to the most desirable service profile to meet the user's service preferences. For example, if the user specifies, within the framework of the service notification and user preference feedback embodiments described below, that maximum performance is the most important factor in selecting which access network to connect to, then the best profile is likely to be the 4G network as 4G is typically faster, except perhaps, for example, if thedevice 100 is closer to the 3G base station so that there is a much stronger signal or if the 4G network is much more heavily loaded than the 3G network. On the other hand, if the user preference set specifies cost as the most important factor, then depending on the central provider service costs the 3G network may prove to be the most desirable service profile. This is a simple example and many other selection criteria are possible in the network selection embodiment as discussed further below. - Network Based Service Usage Monitoring for Verification and Other Purposes
- In some embodiments, if the base station data plane traffic is transmitted via the
Internet 120 as discussed above, then IPDRs (Internet Protocol Detail Records, also sometimes and interchangeably referred to herein as Charging Data Records or CDRs, which as used herein refer to any network measure of service usage or service activity for voice and/or data traffic (e.g., IPDRs can include a time stamp, a device ID, and various levels of network measures of service usage for the device associated with that device ID, such as perhaps total traffic usage, network destination, time of day or device location)) are generated by and collected from the access network equipment. Depending on the specific network configuration, as discussed herein, for a WWAN network the IPDRs can be generated by one or more of the following:base station 125, RAN or transport gateways andAAA 121. In some access network embodiments, the IPDRs are transmitted to equipment functions that aggregated the IPDRs for the purpose of service billing and other functions. Aggregation can occur in the AAA, the transport gateways or other functions including thebilling system 123. As discussed below, it is often the case that the IPDRs is assumed to be obtained from theAAA server 121 and/or a service usage data store 118 (e.g., a real-time service usage collection stored in a database or a delayed feed service usage collection stored in a database), or some other network function. However, this does not imply that the IPDRs may not be obtained from a variety of other network functions, and in some embodiments, the IPDRs are obtained from other network functions as disclosed herein. In some embodiments, existing IPDR sources are utilized to obtain network based service usage measures for multiple purposes including but not limited to service policy or profile implementation verification, triggering service verification error responds actions, and service notification synchronization. Certain types of IPDRs can be based on, or based in part on, what are sometimes referred to as CDRs (Charging Data Records, which can track charges for voice and data usage) or modifications of CDRs. Although the capability to monitor, categorize, catalog, report and control service usage or service activity is in general higher on the device than it is in the network, and, as described herein, device based service monitoring or control assistance is in some ways desirable as compared to network based implementations, as described herein many embodiments take advantage of network based service monitoring or control to augment device assisted service monitoring or control and vice versa. For example, even though many embodiments work very well with minimal IPDR service usage or service activity information that is already available in a network, deeper levels of IPDR packet inspection information in general enable deeper levels of service monitoring or service control verification, which can be desirable in some embodiments. As another example, deeper levels of network capability to control service usage or service activity can provide for more sophisticated error handling in some embodiments, for example, providing for more options of the Switched Port Analyzer (SPAN) and network quarantine embodiments as described herein. As another example, in some embodiments it is advantageous to take advantage of network based service monitoring or control for those service aspects the network is capable of supporting, while using device assisted service monitoring or control for the service aspects advantageously implemented on the device. - In some embodiments, where base station data plane traffic is backhauled and concentrated in a central
provider core network 110, then the IPDRs can originate in the base stations or a router or gateway in thecentral provider network 110, and the IPDRs are collected at theAAA server 121 and stored in the serviceusage data store 118. In some embodiments, thecentral billing system 123 collects the IPDRs from theAAA server 121 for service billing accounting purposes. In some embodiments, acentral billing system 123 collects the IPDRs directly from the initial IPDR source or some other aggregator. In some embodiments, outside partners like MVNOs gain access to the IPDRs from thecentral billing system 123. As discussed below, it is assumed that the IPDRs are obtained from theAAA server 121, and it is understood that the source of the IPDRs is interchangeable in the embodiments. - In some embodiments, the IPDR information is used by the
service processor 115, theservice controller 122 and/or other network apparatus or device apparatus to implement service control verification is provided as described below. In some embodiments, an IPDR feed (e.g., also referred to as a charging data record (CDR)) flows between network elements. For example, an IPDR feed can flow from the RAN gateway 410 (e.g.,SGSN 410, BSC packet control 510 or RNC 512) and the transport gateway 420 (e.g., GGSN or PDSN). In other embodiments, the IPDRs originate and flow from thebase station 125 or some other component/element in the network. In some embodiments, one or more of these IPDR feeds is transmitted to an IPDR aggregation function (e.g., also referred to as a charging gateway). For example, this aggregation function can be located in theAAA 121, in the mobile wireless center 132 (and/or in the home location register (HLR) or other similar function referred to by other common industry names), in thetransport gateway 420, or in some other network element. This aggregation function collects the IPDR feeds into a database with an entry for eachdevice 100. In some embodiments, an intermediate aggregation function is provided that feeds a higher level aggregation function, for example, thetransport gateway 420 can receive IPDR feeds from theRAN gateway 410 or thebase station 125 before sending them to another aggregation function. At some point in time (e.g., at the end of a specified time period, at the end of a device network connection session and/or at a specified time of day), the IPDR aggregation function sends summary information or detailed information of the IPDRs for a given device or group of devices to the billing system for billing and/or reconciliation. In some embodiments, in which the IPDR aggregation feed to the billing system is frequent enough for one or more of the IPDR information purposes described herein, the IPDR feed for theservice controller 122 is derived from the aggregated feed, either by having thebilling system 123 transmit it to theservice controller 122, or by copying it from the IPDR aggregation function. - In some embodiments, the IPDR feed is obtained from the network function that is generating or aggregating the IPDR feed as described herein. In some embodiments, the IPDR feed is copied from the aggregation function in a manner that does not interrupt the operation of the network. For example, a switch based port analysis function can be used to copy the traffic to a traffic analysis or server element that filters out the IPDR traffic and records it to a data base that is then either pushed to the service controller 122 (or any other network element that uses IPDR information as described herein), or is queried by the service controller 122 (or any other function that uses the IPDR information as described herein). In some embodiments, if the aggregated IPDR information transmitted to the billing system is delayed from real-time traffic usage events by an amount of time that is, for example, too long for desired operation, or for any other reason that makes it less desirable to obtain the IPDR information from the same aggregated feed used for the
billing system 123, the IPDR information can be collected from one or more of the sources discussed above including, for example, from another aggregation point (e.g., the feed to the charging gateway, AAA server and/or mobile wireless center/HLR), one or more of thegateways base station 125 and/or another network element. In some embodiments, the IPDR feeds from these or other network functions are copied to a database as described above, which is either pushed or queried to get the information to theservice controller 122 or other network elements that request the IPDR information. - In some embodiments, the
service processor 115 includes various components, such as device agents, that perform service policy implementation or management functions. In some embodiments, these functions include service policy or implementation verification, service policy implementation tamper prevention, service allowance or denial, application access control, traffic control, network access control services, various network authentication services, service control plane communication, device heartbeat services, service billing, transaction billing, simplified activation services and/or other service implementations or service policy implementations. It will be apparent to those of ordinary skill in the art that the division in functionality between one device agent and another is a design choice, that the functional lines can be re-drawn in any technically feasible way that the product designers see fit, and that the placing divisions on the naming and functional breakouts for device agents aids in understanding, although in more complex embodiments, for example, it can make sense to the product designer to break out device agent functionality specifications in some other manner in order to manage development specification and testing complexity and workflow. - In some embodiments, network control of the service policy settings and services as discussed above is accomplished with the
service controller 122 which in various embodiments includes one or more server functions. As with theservice processor 115 agent naming and functional break out, it is understood thatservice controller 122 server naming and functional breakout is also a design choice and is provided mainly to aid in the discussion. It will be apparent to those of ordinary skill in the art that the server names and functional breakouts do not imply that each name is an individual server, and, for example, a single named function in the various embodiments can be implemented on multiple servers, or multiple named functions in the various embodiments can be implemented on a single server. - As shown, there are multiple open content transaction partner sites 134 (e.g., open content transaction servers), which represent the websites or experience portals offered by content partners or ecommerce transaction partners of the service provider. For example,
transaction servers 134 can provide an electronic commerce offering and transaction platform to the device. In some embodiments, the central provider has ownership and management of theservice controller 122, so the central provider and the service provider are the same, but as discussed below the service provider that uses theservice controller 122 to manage the device services by way ofservice processor 115 is not always the same as the central provider who provides the access network services. - In some embodiments, further distribution of central provider access networking functions such as access
network AAA server 121, DNS/DHCP server 126, and other functions are provided in thebase stations 125. In some embodiments, network based device service suspend/resume control are also provided in the base stations 125 (or in some embodiments, for hierarchical or overlay networks, this function is provided by one or more of the following: RAN gateways, transport gateways,AAA 121 or some other network function). As shown, the following are connected (e.g., in network communication with) the central provider network 110: centralprovider billing system 123, dedicated leased lines 128 (e.g., for other services/providers), centralprovider service controller 122, a content management (e.g., content switching, content billing, and content catching)system 130, central provider DNS/DHCP server 126, accessnetwork AAA server 121, serviceusage data store 118 and central providermobile wireless center 132. These embodiments may be advantageous particularly for flat networks as that shown inFIG. 1 that are provided by the present invention. - In some embodiments, the
base stations 125 implement a firewall function viafirewall 124 and are placed directly onto the local loop Internet for backhaul. Voice traffic transport is provided with a secure protocol with Voice Over IP (VOIP) framing running over a secure IP session, for example, Virtual Private Network (VPN), IP Security (IPSEC) or another secure tunneling protocol. In some embodiments, the VOIP channel employs another layer of application level security on the aggregated VOIP traffic trunk before it is placed on the secure IP transport layer. Base station control traffic and other central provider traffic can be provided in a number of ways with secure transport protocols running over Transmission Control Protocol (TCP), Internet Protocol (IP) or User Datagram Protocol (UDP), although TCP provides a more reliable delivery channel for control traffic that is not as sensitive to delay or jitter. One example embodiment for the control channel is a control link buffering, framing, encryption and secure transport protocol similar to that described below for the service control link between a device and the network. In some embodiments, a service control heartbeat function is provided to thebase stations 125 similar to that implemented between theservice controller 122 and theservice processor 115 as described below. If the need to maintain a bandwidth efficient control plane channel between the base stations and the central provider base station control network is not as critical as it is in the case of access network connection to the device, then there are many other approaches for implementing a secure control channel over the Internet including, for example, one or more of various packet encryption protocols running at or just below the application layer, running TCP Transport Layer Security (TLS), and running IP level security or secure tunnels. - In some embodiments, the device based services control plane traffic channel between the
service processor 115 and theservice controller 122 is implemented over the same control plane channel used for the flat base station control architecture, or in some embodiments, over the Internet. As discussed below, it is assumed that the device bases services control plane channel forservice processor 115 toservice controller 122 communications is established through theInternet 120 or through the access network using IP protocols as this is the more general case and applies to overlay network applications for various embodiments as well as applications where various embodiments are used to enable flattened access networks. - In some embodiments, by enabling the device to verifiably implement a rich set of service features as described herein, and by enabling the
base station 125 to connect directly to theInternet 120 with a local firewall for device data traffic, tunnel the voice to a voice network with VOIP and secure Internet protocols, and control thebase station 125 over a secure control plane channel using base station control servers located in a central provider network,base stations 125 can be more efficiently provisioned and installed, because, for example, thebase station 125 can accommodate a greater variety of local loop backhaul options. In such embodiments, it is advantageous to perform certain basic network functions in thebase station 125 rather than the central provider network. - In some embodiments, a basic device suspend/resume function for allowing or disallowing the device Internet access is provided by the base stations 125 (or in some embodiments, for hierarchical or overlay networks in some embodiments this function is provided by one or more of the following: RAN gateways, transport gateways,
AAA 121 or some other network function). This functionality, as will be discussed below, is important for certain embodiments involving taking action to resolve, for example, service policy verification errors. In some embodiments, this function is performed at the base station (e.g., base stations 125) thereby eliminating the need for a more complex networking equipment hierarchy and traffic concentration required to perform the suspend/resume function deeper in the network. Access network base stations control media access and are therefore designed with awareness of which device identification number a given traffic packet, group of packets, packet flow, voice connection or other traffic flow originates from and terminates to. In some embodiments, the suspend/resume function is implemented in thebase station 125 by placing an access control function in the traffic path of each device traffic flow. The suspend resume function can be used by various network elements, and in the context of the present embodiment can be used by the service controller 122 (e.g., in some embodiments, access control integrity server 1654 (FIG. 16 ) ofservice controller 122 or other service controller elements) to suspend and resume device service based on the assessment of the service policy implementation verification status as described below. - In some embodiments, at least a basic traffic monitoring or service monitoring function is performed at the base station (e.g., base stations 125) similar to the service history records or IPDRs collected deeper in the network in more conventional hierarchical access network infrastructure architectures. For example, the service or traffic monitoring history records are advantageous for tracking device network service usage or service activity behavior and for certain verification methods for device based service policy implementation or higher device based services as discussed below. In some embodiments, a traffic monitoring function is provided in the
base station 125 in which the traffic for each device is at least counted for total traffic usage and recorded. In some embodiments, traffic inspection beyond simply counting total traffic usage is provided. For example, the base station traffic monitor can record and report IP addresses or include a DNS lookup function to report IP addresses or IP addresses and associated Uniform Resource Locators (URLs). Another example allows thebase station 125 to attach location data to the IPDR to provide device location data in the records. In some embodiments, traffic inspection includes recording deeper levels of traffic or service monitoring. - In some embodiments, device traffic associated with service verification conditions indicating service usage is out of policy or profile limits or allowances is routed to a quarantine network rather than or as an initial alternative to a suspending service. For example, the advantages for this approach and a more detailed description of the quarantine network are discussed below. In some embodiments, the quarantine network capability is provided for in which rather than simply suspending device traffic completely from the network as described above, the
base station 125 includes a firewall function (e.g., firewall 124) that is capable of passing device access traffic with the quarantine network destinations and blocking device access to all other destinations. In some embodiments, when it is discovered that service verification conditions indicate that service usage is out of policy or profile limits or allowances, then one or more of the following actions are taken: the user is notified of the overage condition, the user is required to acknowledge the overage condition, the user account is billed for the overage condition, and the device is flagged for further analysis by a network device analysis function or a network manager. - In some embodiments, network complexity is reduced using the device without moving completely to a flat base station network as described above. Device participation in the core network services implementation provides for numerous measures for simplifying or improving network architecture, functionality or performance. For example, two approaches are discussed below ranging from a simple overlay of the
service processor 115 onto devices and theservice controller 122 in a conventional hierarchical access network as illustrated inFIGS. 4 through 7 , to a completely flat network as illustrated inFIGS. 1 through 3 and 8. Those of ordinary skill in the art will appreciate that the disclosed embodiments provided herein can be combined with the above embodiments and other embodiments involving flat network base stations to provide several advantages including, for example, richer service capability, less access network complexity, lower access network expenses, more flexible base station deployments, or less complex or less expensive base station back haul provisioning and service costs. - In most of the discussion that follows, the network based service history records and the network based suspend-resume functionality used in certain embodiments involving service implementation verification are assumed to be derived from the device service history 1618 (as shown in
FIG. 16 ) central provider network element and theAAA server 121 central provider network element, and in some embodiments, working in conjunction with other central provider network elements. It is understood that these functions provided by the network can be rearranged to be provided by other networking equipment, including the base station as discussed above. It is also understood that the network based device traffic monitoring, recording and reporting to thedevice service history 1618 element can be accomplished at the base stations. Furthermore, it is understood that while theAAA server 121 is assumed to provide the suspend/resume functionality, quarantine network routing or limited network access called for in some embodiments, theAAA server 121 can be a management device in which the actual implementation of the traffic suspend/resume, firewall, routing, re-direction forwarding or traffic limiting mechanisms discussed in certain embodiments can be implemented in the base stations as discussed above or in another network element. - In some embodiments, an activation server 160 (or other activation sequencing apparatus) provides for provisioning, as described below, of the
devices 100 and/or network elements in the central provider network so that, for example, the device credentials can be recognized for activation and/or service by the network. In some embodiments, theactivation server 160 provides activation functions, as described below, so that, for example, the devices can be recognized by the network, gain access to the network, be provided with a service profile, be associated with a service account and/or be associated with a service plan. As shown inFIG. 1 , theactivation server 160 is connected to the centralprovider core network 110. In this configuration, theactivation server 160 acts as, an over the network or over the air, activation function. In some embodiments, theactivation server 160, or variations of theactivation server 160 as described below, is connected to apparatus in the manufacturing or distribution channel, or over theInternet 120, or as part of theservice controller 122 to service provisioning or activation functions. In some embodiments, theactivation server 160 is connected to the centralprovider core network 110. In some embodiments, theactivation server 160 is connected to other network extensions such as an MVNO network or theInternet 120 if, for example, the routers in the service gateways or base stations have the capability to direct traffic from devices that are not fully activated or provisioned to an Internet destination, or if theservice processor 115 is used for such direction. In some embodiments, theactivation server 160 is included in theservice controller 122. -
FIG. 2 illustrates another simplified (e.g., “flattened”) network architecture including an MVNO (Mobile Virtual Network Operator) relationship in accordance with some embodiments. As shown, an open MVNO configuration is provided in a simplified network as similarly described above with respect toFIG. 1 . In some embodiments, the service provider (e.g., service owner) is defined by the entity that maintains and/or manages theservice controller 122 associated with and controlling theservice processors 115 that are inside thedevices 100 using the service. In some embodiments, theservice controller 122 requires only a non-real time relatively low data rate secure control plane communication link to theservice processors 115. Accordingly, in some embodiments, theservice controller 122 servers can reside in any network that can connect to (e.g., be in network communication with) theInternet 120. For example, this approach provides for a more efficient provisioning of the equipment used to set up an MVNO partnership between the central provider and the service provider, and as shown inFIG. 2 , anMVNO network 210 is in network communication with theInternet 120 just as with thecentral provider network 110 is in network communication with theInternet 120. As shown, the following are connected to (e.g., in network communication with) the MVNO core network 210:MVNO billing system 123,MVNO service controller 122, MVNOcontent management system 130, MVNO DNS/DHCP server 126,MVNO AAA server 121, and MVNOmobile wireless center 132. - By showing two
service controllers 122, one connected to (e.g., in network communication with) theMVNO network 210 and one connected to thecentral provider network 110,FIG. 2 also illustrates that some embodiments allow two entities on the same access network to each use theservice controller 122 andservice processor 115 to control different devices and offer different or similar services. As described below, the unique secure communication link pairing that exists between the two ends of the service control link, 1691 and 1638 (as shown inFIG. 16 ), ensure that the twoservice controllers 122 can only control the devices associated with the correct service provider service profiles. -
FIG. 3 illustrates another simplified (e.g., “flattened”) network architecture including two central providers in accordance with some embodiments. For example, this provides for roaming agreements while maintaining rich services across different networks with completely different access layers. As shown, themobile devices 100 are assumed to have a dual mode wireless modem that will operate on both a 4G network, for example LTE or WiMax, and a 3G network, for example HSPA or EVDO. One example roaming condition would be bothCentral Provider # 1 andCentral Provider # 2 providing 3G and 4G network resources. In this example, themobile devices 100 can connect to both 3G and4G base stations 125 owned and operated by the central provider with whom they have signed up for service, or when neither is available from the central provider the user signed up with the device can roam onto the other central provider access network and still potentially offer the same rich service set using the same service profiles provided, for example, the roaming service costs are reasonable. In some embodiments, if roaming service costs are significantly more expensive than home network service costs, then theservice processor 115 is configured with a roaming service profile that reduces or tailors service usage or service activity through a combination of one or more of user notification, user preference feedback regarding traffic shaping or service policy management preference collected and acted on byservice processor 115, adaptive policy control inservice processor 115 that tracks increasing roaming service costs and scales back service, or recognition of the change in network that causes theservice controller 122 to configureservice processor 115 ofdevice 100 with a roaming service profile. In some embodiments, in roaming situations, network selection can be based on an automatic network selection with network selection being determined, for example, by a combination of user service profile preferences, service provider roaming deals and/or available roaming network capabilities and cost, as discussed further below. - In some embodiments, the
devices 100 are again assumed to be multimode 3G and 4G devices (e.g., themobile devices 100 are assumed to have a dual mode wireless modem that will operate on both a 4G network, for example LTE, and a 3G network, for example HSPA or EVDO), with thedevices 100 being billed for service byCentral Provider # 1 being, for example, EVDO and LTE capable, and thedevices 100 being billed for service byCentral Provider # 2 being, for example, HSPA and LTE capable. For example, thedevices 100 can roam using the 4G LTE network of the roaming central provider when neither the 3G nor 4G networks are available with the home central provider. As similarly discussed above with respect to the above described roaming embodiments, theservice processors 115 andservice controllers 122 are capable of providing similar services on the 4G roaming network and the 3G home network as on the 4G home network, however, the varying costs and available network capacity and speed differences of 3G home, 4G roaming and 4G home may also encourage the use of different, such as three different, service profiles to allow for the most effective and efficient selection and control of services based on the current network. -
FIG. 4 illustrates a network architecture including a Universal Mobile Telecommunications System (UMTS) overlay configuration in accordance with some embodiments. As shown,FIG. 4 includes a 4G/3G/2G HSPA/Transport access network operated by a central provider and twoMVNO networks 210 operated by two MVNO partners. In some embodiments, the central provider can offer improved service capabilities using a conventional UMTS network. As shown, thebase stations 125 do not connect directly to theInternet 120, and instead thebase stations 125 connect to the conventional UMTS network. However, as in various previous embodiments, theservice processor 115 still connects through the secure control plane link toservice controller 122. In some embodiments, the data plane traffic is backhauled across the various UMTS network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the accessnetwork AAA server 121. Referring now to the 4G/3G/2G HSPA/Transport access network as shown inFIG. 4 , the LTE/HSPA and HSPA/GPRS base stations/nodes 125 are in communication with 4G/3G/2G Service/Serving GPRS Support Nodes (SGSNs)cluster 410 via aradio access network 405, which are in communication with 4G/3G/2G Gateway GPRS Support Nodes (GGSNs)cluster 420 via an access transport network 415 (e.g., a GPRS-IP network), which are then in communication with centralprovider core network 110. - As shown in
FIG. 4 , as discussed elsewhere, serviceusage data store 118 is a functional descriptor for a network level service usage information collection and reporting function located in one or more of the networking equipment boxes attached to one or more of the sub-networks in the Figure (e.g., RAN, transport and/or core networks). As shown inFIG. 4 ,service usage 118 is shown as an isolated function connected to the centralprovider core network 110 and the intention of this depiction is to facilitate all the possible embodiments for locating theservice usage 118 function. In some UMTS network embodiments, theservice usage 118 function is located or partially located in the GGSN gateway (or gateway cluster) 420. In some embodiments,service usage 118 functionality is located or partially located in the SGSN gateway (or gateway cluster) 410. In some embodiments,service usage 118 functionality is located or partially located in the equipment cluster that includes theAAA 121 and/or themobile wireless center 132. In some embodiments,service usage 118 functionality is located or partially located in the base station, base station controller and/or base station aggregator, collectively referred to asbase station 125 inFIG. 4 and many other figures described herein. In some embodiments,service usage 118 functionality is located or partially located in a networking component in thetransport network 415, a networking component in thecore network 110, thebilling system 123 and/or in another network component or function. This discussion on the possible locations for the network based service usage history logging and reporting function can be easily generalized to all the other figures described herein by one of ordinary skill in the art (e.g.,RAN Gateway 410 and/or Transport Gateway 420), and this background will be assumed even if not directly stated in all discussion above and below. - In some embodiments, a central provider provides open development services to MVNO, Master Value Added Reseller (MVAR) and/or Original Equipment Manufacturer (OEM) partners. In some embodiments, all three service providers, central provider service provider,
MVNO # 1 service provider andMVNO # 2 service provider have service control and billing control of their ownrespective devices 100 through the unique pairing of theservice processors 115 andservice controllers 122. For example,MVNO # 1 andMVNO # 2 can each have open development billing agreements with the central provider and each can own theirrespective billing systems 123. As shown inFIG. 4 ,MVNO # 1core network 210 is in communication with the centralprovider core network 110 via theInternet 120, andMVNO # 2core network 210 is in communication with the centralprovider core network 110 via an alternate landline(LL)/VPN connection 425. In some embodiments, the two MVNOs each offer completely different devices and/or services, and the devices and/or services also differ significantly from those offered by the central provider, and the service profiles are adapted as required to service the different devices and respective service offerings. In addition, thecentral billing system 123 allows all three service provider user populations to access ecommerce experiences from transaction provider partners operatingtransaction servers 134, to choose central provider billing options that combine their third party transaction bills on their service provider bill, and each subscriber population can experience a service provider specified look and feel that is unique to the respective service provider even though the different user populations are interfacing to the same transaction servers and the transaction partners do not need to require significant custom development to provide the unique central billing and unique consistent user experience look and feel. - In some embodiments, a central provider offers open network device and service developer services using one service controller server 122 (e.g., a service controller server farm) and allows the open development partners to lease server time and server tools to build their own service profiles. The central provider also provides service billing on behalf of services to the open development partners. For example, this reduces costs associated with setting up an MVNO network for the open development partners and does not require the partners to give up significant control or flexibility in device and/or service control.
-
FIG. 5 illustrates a network architecture including an Evolution Data Optimized (EVDO) overlay configuration in accordance with some embodiments. This figure is similar toFIG. 4 except for the various particular variations of the EVDO network architecture as compared to the HSPA/GPRS wireless access network architecture as will be apparent to one of ordinary skill in the art. As shown,FIG. 5 includes an EVDO access network operated by a central provider and twoMVNO networks 210 operated by two MVNO partners. The EVDO access network includes LTE/EVDO and EVDO/1×RTT base stations 125 in communication with Base Station Controller (BSC)packet control 508 andradio network controller 512 via a radio access network (RAN) 505, which are in communication with packetdata service node 520 via anaccess transport network 515, which is in communication with centralprovider core network 110. As shown, aRAN AAA server 521 is also in communication with theaccess transport network 515. - In some embodiments, the central provider can offer improved service capabilities using a wireless access network. As shown, the
base stations 125 do not connect directly to theInternet 120, and instead thebase stations 125 connect to the wireless access network. However, as in various previous embodiments, theservice processor 115 still connects through the secure control plane link toservice controller 122. In some embodiments, the data plane traffic is backhauled as shown across the various network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the accessnetwork AAA server 121. -
FIG. 6 illustrates a network architecture including a 4G LTE and Wi-Fi overlay configuration in accordance with some embodiments. This figure is also similar toFIG. 4 except for the various particular variations of the 4G LTE/Wi-Fi network architecture as compared to the HSPA/GPRS wireless access network architecture as will be apparent to one of ordinary skill. As shown,FIG. 6 includes a 4G LTE and Wi-Fi access network operated by a central provider and twoMVNO networks 210 operated by two MVNO partners. The 4G LTE/Wi-Fi access network as shown includes LTE eNodeB and HSPA/EVDO base stations 125 in communication with Base Station Controller (BSC) packet control (EVDO & 1×RTT) 608 and SGSN (HSPA & GPRS) 612 via a radio access network (RAN) 605, which are in communication with System Architecture Evolution (SAE) Gateway (GW) 620 via anaccess transport network 615, which is then in communication with central provider (core)network 110. As shown, a Mobile Management Entity (MME)server 619 is also in communication with theaccess transport network 615. Also as shown, a Wi-Fi Access Point (AP) 602 is also in communication with theaccess transport network 615 via Wi-Fi Access Customer Premises Equipment (CPE) 604. As will be apparent to those of ordinary skill in the art, the embodiments of network architectures shown, for example, inFIGS. 1-8 are exemplary network architecture embodiments in which one or more of the shown network elements may not be required or included, alternative network elements included, and/or additional network elements included based on network design choices, network standards and/or other functional/design considerations and choices. - In some embodiments, the central provider can offer improved service capabilities using the wireless access network as depicted in
FIG. 6 . As shown, thebase stations 125 do not connect directly to theInternet 120, and instead thebase stations 125 connect to the wireless access network. However, as in various previous embodiments, theservice processor 115 still connects through the secure control plane link toservice controller 122. In some embodiments, the data plane traffic is backhauled as shown across the various network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the accessnetwork AAA server 121. Accordingly, as shown inFIGS. 4 through 6 , various embodiments can be implemented independent of the wireless access network technology, and for example, can be implemented in 3G, 4G and any other wireless access network technology. -
FIG. 7 illustrates a network architecture including a WiMax and Wi-Fi overlay configuration in accordance with some embodiments. This figure is also similar toFIG. 4 except for the various particular variations of a combined WiMax/Wi-Fi network as compared to the HSPA/GPRS wireless access network architecture as will be apparent to one of ordinary skill in the art. As shown,FIG. 7 includes both a WiMax and Wi-Fi network (e.g., a combined WiMax/Wi-Fi network) operated by a central provider and twoMVNO networks 210 operated by two MVNO partners. Although the Wi-Fi and WiMax access technologies are different wireless access networking technologies, with WiMax providing a wide area networking technology and Wi-Fi providing a local area networking technology, which efficiently operates using the two wireless access networking capabilities. As similarly discussed above with respect to the switching between 3G and 4G networks, some embodiments employ the automatic network selection capability as described above to choose the best available network service profile, and, for example, the user can force the decision or the service controller can make the decision. For example, if free Wi-Fi services have adequate coverage, in most cases, the decision criteria programmed into the automatic network selection algorithm will select Wi-Fi as long as the Wi-Fi access points are associated with a known and trusted provider. In some embodiments, transaction billing from centralprovider billing system 123 orMVNO # 1 orMVNO # 2billing systems 123 will work with the transaction servers when connected over Wi-Fi just as when connected over any other access technology (including wire line based connections). The WiMax/Wi-Fi access network as shown includesWiMax base stations 125, Wi-Fi access points/hotspots 702 and/or Wi-Fi mesh access networks 702 (in some embodiments, femto cells can be used in addition to and/or as an alternative to Wi-Fi), and Wi-Fi access customer-premises equipment (CPE) 704 in communication withWiMax service controller 708 and Wi-Fi service controller 712 via aradio access network 705, which are in communication withWiMax core gateway 720 via anaccess transport network 715, which is then in communication with central provider (core)network 110. - In some embodiments, the central provider can offer improved service capabilities using the wireless access network as depicted in
FIG. 7 . As shown, thebase stations 125 do not connect directly to theInternet 120, and instead thebase stations 125 connect to the wireless access network. However, as in various previous embodiments, theservice processor 115 still connects through the secure control plane link toservice controller 122. In some embodiments, the data plane traffic is backhauled as shown across the various network routers and gateways as is the control plane traffic, and the IPDRs are obtained from the accessnetwork AAA server 121. - Referring to
FIG. 7 , the Wi-Fi connection can be replaced with a femto cell (and the Wi-Fi modem shown in FIGS. 15B(3) and 15B(4) can be replaced with a femto cell modem (base station side functionality)). In some embodiments, theservice processor 115 is provided on the femto cell to control subscriber access in a verifiable manner as similarly described herein with respect to various embodiments (e.g., the Wi-Fi related embodiments). For example, the femto cell service provider (e.g., the entity that owns the spectrum the femto cell is using) can operate the femto cell as a local access mechanism for the home subscriber (or other who purchased or installed the femto cell), and then also use it to provide pay-for-service or additional free services, with controlled access and/or traffic control and/or service control and/or billing control performed locally or in combination with network equipment as described herein. In some embodiments, the WWAN devices being used at home or work with the femto cell include a portion of the service processor functionality. For example, this allows the service provider for femto cells to provide service and monetize service in a controlled way even though the femto cell is not connected to the service provider network the way conventional base stations are connected to the service provider network, but is connected through theInternet 120. For example, the secure heartbeat function can be extended to include data traffic so that it is encrypted and secured along with the control plane traffic. The decision of whether or not to admit a device onto the femto cell can be made through theservice processor 115 connection to theservice controller 122 and subsequent look up of the credentials for the device and the associated service plan and service profile that is then programmed into the service processor on the femto cell and/or the device itself. The femto cell can also offer a landing page to devices through the service processor so that devices that do not belong to the network can gain access to the network by signing up over the femto cell. For example, the intermediate device embodiments for Wi-Fi on one end and WWAN on the other can be accomplished by using the Wi-Fi connection in the cell phone in AP mode so that it becomes the intermediate device. Theservice processor 115 on the cell phone can then act in the same manner as described for the intermediate device as described herein. -
FIG. 8 illustrates another simplified (e.g., “flattened”) network architecture including multiple wireless access networks (e.g., 3G and 4G Wireless Wide Area Networks (WWANs)) and multiple wire line networks (e.g., Data Over Cable Service Interface Specification (DOCSIS) and Digital Subscriber Line Access Multiplexer (DSLAM) wire line networks) in accordance with some embodiments. It is a common network architecture for multi-access central providers to have one or more wired access networks and one or more wireless access networks. As shown,FIG. 8 includes both 3G and 4G wireless access networks, including a4G base station 125 and a3G base station 125, and both DOCSIS and DSLAM wire line networks (e.g., a combined WWAN/wire line network), includingDOCSIS Head End 125 andDSLAM 125, operated by a central provider via central provider (core)network 110 and an MVNO partner viaMVNO network 210 via theInternet 120. - As shown, the
service processor 115 can reside on a number of different types ofdevices 100 that work on 3G or 4G wireless, DSL or DOCSIS, and theservice controller 122 is capable of controlling each of these types of devices with a consistent service experience, for example, using different service profiles, service capabilities and service profile cost options depending on which network the device is connected to and/or other criteria. For example, a download of a High Definition (HD) movie can be allowed when theservice controller 122 is managing service profile policies for aservice processor 115 residing on a DOCSIS device 100 (e.g., a computer or laptop connected to a cable modern), but not when thesame service controller 122 is managing service profile policies for aservice processor 115 residing on a 3G device 100 (e.g., a smart phone connected to a mobile 3G network). - As will now be apparent to one of ordinary skill in the art in view of the above description of
FIGS. 1 through 8 , the present invention can be provided across any access network and a set of service profiles can be defined in a variety of ways including, for example, to user preference feedback, access network performance, access network cost, access network central provider partnership status with the service provider central provider and roaming deals and costs. For example, as discussed below, various embodiments allow for users to have superior service experiences based on the ability to control certain of their service settings, and service providers can also more efficiently deploy a greater variety of services/service plans to users. - In some embodiments, the
service processor 115 and theservice controller 122 provide an overlay for existing networks without significantly changing thebilling system 123, gateways/routers or other network components/elements, and also provide verifiable service monitoring to control services and/or service usage/costs without involving, for example, a service provider or MVNO (e.g., for smart phone devices and/or laptops or netbooks (or any other network accessible device) with an unlimited data plan or any other service plan). For example, applications that are deployed by device owners or service subscribers (e.g., an IT manager) and do not involve a service provider include roaming services provided as an after-market product without carrier/service provider involvement. In this example, device activity is recorded by theservice processor 115 and transmitted to the service controller 122 (e.g., the IT manager controls the service controller 122). In another example, a third party after-market product is provided in which theservice controller 122 is hosted by the third party and the device management entity (e.g., the IT manager or parents of the device user for parental controls) uses a secure Virtual Service Provider (VSP) website to control the devices that belong to that management entity's device partition (e.g., VSP partitions and techniques are described below with respect toFIG. 49 ). The VSP secure website techniques described herein can also be applied to service provider owned servers with device partitions for the purpose of controlling, for example, Deep Packet Inspection (DPI) controllers (e.g.,DPC policy implementation 5402 as shown inFIG. 54 ) to provide similar or substantially equivalent service usage/control capabilities using network based service control techniques, as similarly described in detail below with respect toFIGS. 49 and 54 (e.g., IT manager VSP control of a group partition and/or MVNO VSP control of a group partition). - Service Processor Configurations for Devices
-
FIG. 9 illustrates a hardware diagram of adevice 100 that includes aservice processor 115 in accordance with some embodiments. As shown inFIG. 9 , theservice processor 115 is stored in a nonvolatile memory 910 and amemory 920 of thedevice 100. As will be appreciated by those of ordinary skill in the art, the present invention can operate with virtually any device architecture, and the device architectures discussed herein (e.g., with respect toFIGS. 9 through 15 ) are examples of various implementations on certain devices (e.g., of different representations of device 100). - As shown in
FIG. 9 ,device 100 also includes aprocessor 930, sometimes referred to as a CPU or central processor unit, an APU or application processor unit, a core processor, a computing device, or many other well known terms. In some embodiments,device 100 includes one or more processors and/or a multicore processor. As shown,processor 930 includes a sub-processor 935. In some embodiments,processor 930 and/or sub-processor 935 are based on an architecture sometimes referred to as a complex instruction set computer or CISC, a reduced instruction set computer or RISC, a parallel processor, a combination of two or more architectures or any other processor architecture. In some embodiments,processor 930 has a design that is based on logic and circuitry from one or more standard design library or published architecture, or includes specialized logic and circuitry designed for a givendevice 100 or collection of such devices. In some embodiments, a device includes more than one processor and/or sub-processor, and in such a device, one processor and/or sub-processor can have one architecture while another may have a somewhat different or completely different architecture. In some embodiments, one or more of the processors and/or sub-processors can have a general purpose architecture or instruction set, can have an architecture or instruction set that is partially general or partially specialized, or can have an instruction set or architecture that is entirely specialized. In some embodiments, a device includes more than one processor and/or sub-processor, and in such a device, there can be a division of the functionality for one or more processors and/or sub-processors. For example, one or more processors and/or sub-processors can perform general operating system or application program execution functions, while one or more others can perform communication modem functions, input/output functions, user interface functions, graphics or multimedia functions, communication stack functions, security functions, memory management or direct memory access functions, computing functions, and/or can share in these or other specialized or partially specialized functions. In some embodiments, anyprocessor 930 and/or any sub-processor 935 can run a low level operating system, a high level operating system, a combination of low level and high level operating systems, or can include logic implemented in hardware and/or software that does not depend on the divisions of functionality or hierarchy of processing functionality common to operating systems. - As shown in
FIG. 9 ,device 100 also includesnon-volatile memory 910,memory 920,graphics memory 950 and/or other memory used for general and/or specialized purposes. As shown,device 100 also includes a graphics processor 938 (e.g., for graphics processing functions). In some embodiments, graphics processing functions are performed byprocessor 930 and/orsub-processor 935, and aseparate graphics process 938 is not included indevice 100. As shown inFIG. 9 ,device 100 includes the following modems:wire line modem 940,WWAN modem 942,USB modem 944, Wi-Fi modem 946,Bluetooth modem 948, andEthernet modem 949. In some embodiments,device 100 includes one or more of these modems and/or other modems (e.g., for other networking/access technologies). In some embodiments, some or all of the functions performed by one or more of these modems are performed by theprocessor 930 and/orsub processor 935. For example,processor 930 can implement some or all of certain WWAN functional aspects, such as the modem management, modem physical layer and/or MAC layer DSP, modem I/O, modem radio circuit interface, or other aspects of modem operation. In some embodiments,processor 930 as functionality discussed above is provided in a separate specialized processor as similarly shown with respect to the graphics and/ormultimedia processor 938. - As also shown in
FIG. 9 ,device 100 includes an internal (or external)communication bus structure 960. The internalcommunication bus structure 960 generally connects the components in thedevice 100 to one another (e.g., allows for intercommunication). In some embodiments, the internalcommunication bus structure 960 is based on one or more general purpose buses, such as AMBA, AHP, USB, PCIe, GPIO, UART, SPI, I2C, Fire wire, DisplayPort, Ethernet, Wi-Fi, Bluetooth, Zigbee, IRDA, and/or any other bus and/or I/O standards (open or proprietary). In some embodiments, the bus structure is constructed with one or more custom serial or parallel interconnect logic or protocol schemes. As will be apparent to one of ordinary skill in the art, any of these or other bus schemes can be used in isolation and/or in combination for various interconnections betweendevice 100 components. - In some embodiments, all or a portion of the
service processor 115 functions disclosed herein are implemented in software. In some embodiments, all or a portion of theservice processor 115 functions are implemented in hardware. In some embodiments, all or substantially all of theservice processor 115 functionality (as discussed herein) is implemented and stored in software that can be performed on (e.g., executed by) various components indevice 100.FIG. 9 illustrates an embodiment in whichservice processor 115 is stored in device memory, as shown, inmemory 920 and/ornon-volatile memory 910, or a combination of both. In some embodiments, it is advantageous to store or implement certain portions or all ofservice processor 115 in protected or secure memory so that other undesired programs (and/or unauthorized users) have difficulty accessing the functions or software inservice processor 1 15. In some embodiments,service processor 115, at least in part, is implemented in and/or stored on secure non-volatile memory (e.g., nonvolatile memory 930 can be secure non-volatile memory) that is not accessible without pass keys and/or other security mechanisms. In some embodiments, the ability to load at least a portion ofservice processor 115 software into protected non-volatile memory also requires a secure key and/or signature and/or requires that theservice processor 1 15 software components being loaded into non-volatile memory are also securely encrypted and appropriately signed by an authority that is trusted by a secure software downloader function, such asservice downloader 1663 as discussed below (and as shown inFIG. 16 ). In some embodiments, a secure software download embodiment also uses a secure non-volatile memory. Those of ordinary skill in the art will also appreciate that all memory can be on-chip, off-chip, on-board and/or off-board. In some embodiments, theservice processor 115 which as shown inFIG. 9 is stored or implemented in nonvolatile memory 910 andmemory 920, can be implemented in part on other components indevice 100. - As shown,
device 100 also includes a userinterfaces device component 980 for communicating with user interface devices (e.g., keyboards, displays and/or other interface devices) and other I/O devices component 985 for communicating with other I/O devices. User interface devices, such as keyboards, display screens, touch screens, specialized buttons or switches, speakers, and/or other user interface devices provide various interfaces for allowing one or more users to use thedevice 100. -
FIG. 10 illustrates another hardware diagram of adevice 100 that includes aservice processor 115 in accordance with some embodiments. As shown inFIG. 10 , theservice processor 115 is implemented on theprocessor 930 of thedevice 100. In some embodiments, this implementation can be in part or whole accomplished in software stored, implemented and/or executed on theprocessor 930. In some embodiments, the implementation and/or execution can be in part or whole accomplished in hardware that is on theprocessor 930. While theservice processor 115 is shown inFIG. 10 as stored, implemented and/or executed on theprocessor 930, in other embodiments, theservice processor 115 is implemented in part on other components indevice 100, for example, as discussed below. - Service Processor Implemented on a Communications Modem
-
FIG. 11 illustrates another hardware diagram of adevice 100 that includes aservice processor 115 in accordance with some embodiments. As shown inFIG. 11 , theservice processor 115 is implemented on theWWAN modem 942 of thedevice 100. In some embodiments, this implementation can be in part or whole accomplished in software stored, implemented and/or executed on theWWAN modem 942. In some embodiments, the implementation and/or execution can be in part or whole accomplished in hardware that is on theWWAN modem 942. In some embodiments,service process 115 is implemented on another modem component ofdevice 100 and/or one or more of the modem components ofdevice 100. - In some embodiments, the
service processor 115 is implemented on a modem processor (e.g.,WWAN modem 942 or WWAN/Wi-Fi modem), and theservice processor 115 can be installed and/or executed in protected and/or secure memory or processor hardware on the modem. The modem memory can be made robust to hacking or tampering and, in some embodiments, is only accessible from a secure network management channel or secure device management port and not by most end users. In some embodiments, a portion of theservice processor 115 is implemented on a modem processor (e.g.,WWAN modem 942 hardware or software), and a portion of theservice processor 115 is implemented on anotherdevice 100processor 930. For example, the deviceservice monitor agent 1696 and one or more service usage measurement points (see discussion associated withFIG. 21 ) can be implemented on a modem processor, andother service processor 115 elements can be implemented in the main deviceoperating system processor 930. As another example, a second (or first)service monitor agent 1696 and one or more service usage measurement points can be implemented on a modem processor, and a first (or second)service monitor 1696 with one or more service measurement points can be implemented on the mainoperating system processor 930 fordevice 100. For example, such embodiments can be configured to provide a service usage measurement and reporting system that offers a diversified countermeasure to protect against hacking, tampering or other errors for device based service usage measurements that can be made harder to hack or tamper with than certain software embodiments on theprocessor 930. For example, such embodiments can be employed when one or more of the following capabilities are not available: network based service usage measures, network based service profile or policy implementation verification measures, and network based service usage verification error response action capabilities. - In some embodiments, certain portions of the
service processor 115 that deal with application layer service monitoring or traffic flow identification (e.g., tagging or traffic flow shaping as disclosed elsewhere) are implemented on amain processor 930, and other portions of theservice processor 115 are implemented on a modem processor (e.g., WWAN modem 942). - In some embodiments, the WWAN modem is a wide area access technology modem such as 2G, 2.5G, 3G or 4G. As discussed above and below, the connection to the
WWAN modem 942 can be a connection internal todevice 100, for example a USB, GPIO, AMBA or other bus, or can be a connection that extends external to the device such as for example a USB, Ethernet, Wi-Fi, Bluetooth or other LAN or PAN connection. Three example embodiments in which the bus is internal to the device are as follows: a PCIe modem card running over USB or PCIe, a GPIO connection running from aprocessor 930 chipset to a modem chipset inside a mobile device, or a Wi-Fi connection running from a Wi-Fi modem inside ofdevice 100 to an intermediate modem or networking device combination that forwards the access network traffic between the access network connection and the device via the Wi-Fi connection. In some embodiments, in addition to theservice processor 115 being implemented on theWWAN modem 942 either internal or external to thedevice 100, similarlyservice processor 115 can be implemented on awire line modem 940, such as DSL, Cable or fiber, another wireless LAN or PAN modem, such as Wi-Fi, Zigbee,Bluetooth modem 948, White Space, or some other modem, connected internal todevice 100 or external todevice 100 via a LAN or PAN extension of internal or externalcommunications bus structure 960. - In some embodiments, a complete turn-key reference design product for the device modem (one or more of 942, 946, 948, 949, 944, 940) combined with a built-in
service processor 115, possibly with a well defined and documented application interface and a well defined and documented service processor developers kit (SPDK) provides for a powerful product embodiment for the purpose of achieving mass market distribution and usage for the modem withservice processor 115 and associatedservice controller 122 features. For example, embodiments that include theWWAN modem 942, possibly in combination with one or more additional modems including Wi-Fi modem 946,bluetooth modem 948,USB modem 944 andEthernet modem 949, can be combined with a pre-tested or pre-certified integrated embodiment of theservice processor 115, possibly in combination with a well defined API for writing software applications that interface to, reside on or communicate with this turn-key modem embodiment. As disclosed herein, the advantageous capabilities of theservice processor 115, possibly in conjunction with theservice controller 122, to assist in monitoring, control, billing and verification for services is made more available fordevice 100 manufacturers in such a form, because the manufacturers do not need to spend as much time and resources to develop a custom modem only for a subset of devices that the turn-key modem can be used to support. In some embodiments, theservice processor 115, as discussed herein, can be configured to provide device assisted service monitoring, control, billing and/or verification across not just when connected to the WWAN network via the WWAN modem, but also when connected to the other networks corresponding to the other access modems included in the turn-key combined module plus service processor 115 (or SPDK or chipset plus service processor 115) design. Thepre-integrated service processor 115 and API possibly in combination with testing and certification can be packaged in a small form factor that may have standardized interfaces such as USB, PCIe, firewire, Display Port, GPIO, or other interface. The form factor may be miniaturized into standard configurations such as minicard, half minicard or even smaller form factors, or it can be designed into a non-standard or proprietary form factor. The module form factor can be well documented to simplify integration intovarious device 100 designs. The SPDK embodiments can be designed to contain one or more of the following: hardware integration and use documentation, software integration documentation, software programming documentation, application interface documentation, service controller documentation, overall testing guidelines and overall use guidelines. In some embodiments, the modem module can be integrated with theservice processor 115 functionality as a combined chipset, firmware and/or software product, with other SPDK features very similar to those listed above. The service controller programming guide for these turn-key embodiments can also be documented for theSPDK service processor 115 software, turn-key module withservice processor 115 or integrated chipset withservice processor 115. Accordingly, these embodiments provide various solutions to simplify the OEM task of integrating, developing, testing andshipping device 100 products (or integrated networking device products) with any of the device assisted service monitoring, control, billing or verification capabilities disclosed herein. -
FIG. 12 illustrates another hardware diagram of adevice 100 that includes aservice processor 115 in accordance with some embodiments. As shown inFIG. 12 , theservice processor 115 is implemented on the other I/O devices component 980 of thedevice 100. In some embodiments, this implementation can be in part or whole accomplished in software stored, implemented and/or executed on the other I/O devices component 980 (e.g., a SIM/USIM card or other secure hardware I/O device). In some embodiments, the implementation and/or execution can be in part or whole accomplished in hardware that is on the other I/O devices component 980. - As discussed above, various embodiments include product designs in which the
service processor 115 resides on device volatile or non-volatile memory (seeFIG. 9 ), the device application processor or CPU (seeFIG. 10 ), the wireless access modem (seeFIG. 11 ) (or any other modem), or another I/O device (seeFIG. 12 ). While these are just a few of theexample service processor 115 placement embodiments, these embodiments show that the placement of where the software or hardware for implementing theservice processor 115 can reside in thedevice 100 is very flexible and can be implemented in a myriad of places and ways depending on the device and/or other technical design choices. -
FIG. 13 illustrates another hardware diagram of adevice 100 that includes aservice processor 115 implemented in external memory of a System On Chip (SOC) 1310 in accordance with some embodiments. As shown inFIG. 13 , theservice processor 115 is implemented on theexternal memory 1320 of thedevice 100. In some embodiments, this implementation can be in part or whole accomplished in software stored, implemented and/or executed on theexternal memory 1320. In some embodiments, the implementation and/or execution can be in part or whole accomplished in hardware that is on theexternal memory 1320. In some embodiments,SOC chipset 1310 andexternal memory 1320 provide a portion or all of the hardware ofdevice 100. -
FIG. 14 illustrates another hardware diagram of adevice 100 that includes aservice processor 115 implemented in external memory of a System On Chip (SOC) 1310 in accordance with some embodiments. As shown, theservice processor 115 is stored in a nonvolatile memory 910 and amemory 920 of theSOC chipset 1310, as similarly discussed above with respect toFIG. 9 . In some embodiments,SOC chipset 1310 andexternal memory 1320 provide a portion or all of the hardware ofdevice 100. - As similarly discussed above with respect to
FIGS. 9 through 12 , various embodiments include product designs including theSOC chipset 1310 in which theservice processor 115 resides on internal volatile ornon-volatile memory 910 of the SOC chipset 1310 (seeFIG. 14 ), the device application processor orCPU 930 and/orsub processor 935, themodems O device 985, and/or external memory 1320 (seeFIG. 13 ) (and/or any combinations thereof). While these are just a few of theexample service processor 115 placement embodiments, these embodiments show that the placement of where the software or hardware for implementing theservice processor 115 can reside in the.SOC chipset 1310 and/or theexternal memory 1320 of thedevice 100 is very flexible and can be implemented in a myriad of places and ways depending on the device and/or other technical design choices. - The above discussion with respect to
FIGS. 9 through 14 illustrating various internal hardware embodiments fordevice 100 applies equally to this partitioning of device functionality or any other partitioning of how the components indevice 100 are configured, whether they are all separate components, some of the components are combined into a single chipset but there are still multiple chipsets, or all of the components are combined into a chipset. For example,FIGS. 9 through 14 illustrating various internal hardware embodiments fordevice 100 show several access modem components including thewire line modem 940, wireless wide area network (WWAN)modem 942,USB modem 944, Wi-Fi modem 946,Bluetooth modem 948, andEthernet modem 949. In some embodiments,wire line modem 940 is a DSL or cable modem such as DOCSIS, or some other modem with a hard connection such as fiber. In some embodiments, as discussed above and below, connection to the wire line or wireless access network is accomplished through an extension of the internal or externalcommunications bus structure 960. For example, such an extension is accomplished using one or the other modems, such as Wi-Fi modem 946 orEthernet modem 949, connecting to a local area network that in turn connects to the access network via a device that bridges the local area network to the access network. One of ordinary skill in the art will appreciate that when discussing device connection to any access network the connection can be via a direct connection to the network, such as a 3G or4G WWAN modem 942 connection to a 3G or 4G WWAN network, or can be a connection to the access network through an intermediate connection, such as a Wi-Fi modem 946 connection to a modem or networking device combination that has a Wi-Fi LAN connection and a 3G or 4G network access network connection. Another example of an extended modem connection embodiment includes a Wi-Fi modem 946 device connection to a modem or networking device combination that includes a Wi-Fi LAN connection and a DOCSIS or DSL network access connection. Other examples of such combinations will be readily apparent to one of ordinary skill in the art. - Service Processor Configurations for Intermediate Networking Devices
-
FIGS. 15A through 15C illustrate hardware diagrams of adevice 100 that include aservice processor 115 and abus structure extension 1510 using intermediate modem or networking device combinations in accordance with various embodiments. For example,FIGS. 15A and 15B illustrate various extended modem alternatives for access network connection through an intermediate modem or networking device combination that has a connection (e.g., LAN connection) to one ormore devices 100. - In some embodiments,
deyice 100 includes a 3G and/or 4G network access connection in combination with the Wi-Fi LAN connection to thedevice 100. For example, the intermediate device or networking device combination can be a device that simply translates the Wi-Fi data to the WWAN access network without implementing any portion of theservice processor 115 as shown in FIG. 15B(1). In some embodiments, an intermediate device or networking device combination includes a more sophisticated implementation including a networking stack and some embodiments a processor, as is the case for example if the intermediate networking device or networking device combination includes a router function, in which case theservice processor 115 can be implemented in part or entirely on the intermediate modem or networking device combination. The intermediate modem or networking device combination can also be a multi-user device in which more than one user is gaining access to the 3G or 4G access network via the Wi-Fi LAN connection. In the case of such a multi-user network, the access network connection can include several managed service links using multiple instantiations ofservice processor 115, each instantiation, for example, being implemented in whole or in part ondevice 100 with the intermediate modem or networking device combination only providing the translation services from the Wi-Fi LAN to the WWAN access network. - Referring now to FIGS. 15A and 15B(2)-(4), in some embodiments, the
service processors 115 are implemented in part or in whole on the intermediate modem or networking device combination. In the case where theservice processor 115 is implemented in part or in whole on the intermediate modem or networking device combination, theservice processor 115 can be implemented for each device or each user in the network so that there are multiple managed service provider accounts all gaining access through the same intermediate modem or networking device combination. In some embodiments, the functions ofservice processor 115 are implemented on an aggregate account that includes the WWAN access network traffic for all of the users or devices connected to the Wi-Fi LAN serviced by the intermediate modem or networking device combination. In some embodiments, the central provider can also provide an aggregated account service plan, such as a family plan, a corporate user group plan and/or an instant hotspot plan. In the case where there is one account for the intermediate modem or networking device combination, the intermediate modem or networking device combination can implement a local division of services to one ormore devices 100 or users in which the services are controlled or managed by the intermediate modem or networking device combination or thedevice 100, but the management is not subject to service provider control and is auxiliary to the service management or service policy implementation performed byservice processors 115. In some embodiments, another service model can also be supported in which there is an aggregate service provider plan associated with one intermediate modem or networking device combination, or a group of intermediate modems or networking device combinations but where each user or device still has its own service plan that is a sub-plan under the aggregate plan so that each user or device has independent service policy implementation with a unique instantiation ofservice processor 115 rather than aggregate service policy implementation across multiple users in the group with a single instantiation ofservice processor 115. - As shown in FIGS. 15A and 15B(2), in some embodiments,
device 100 includes a Wi-Fi modem 946, a Wi-Fi modem 946 combined with a 3G and/or4G WWAN modem 1530 on intermediate modem ornetworking device combination 1510, and the intermediate modem or networking device combination forwards WWAN access network traffic to and fromdevice 100 via the Wi-Fi link. For example, theservice processor 115 can be implemented in its entirety ondevice 100 and the service provider account can be associated exclusively with one device. This is an embodiment associated with one or more ofFIG. 29 , 31, 32 or 34 discussed below, in which the modem bus represents the Wi-Fi LAN connection via the Wi-Fi modem 946. Similarly, as shown in FIGS. 15A and 15B(3), such an implementation can be provided using a different access modem and access network, such as a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem ornetworking device combination 1510. In addition, various other embodiments similarly use DSL as shown in FIGS. 15A and 15B(4), USB, Ethernet, Bluetooth, or another LAN or point to point connection fromdevice 100 to the intermediate modem ornetworking device combination 1510. - In some embodiments, a portion of the
service processor 115 is implemented on thedevice 100, such as theapplication interface agent 1693 and other supporting agents (seeFIG. 16 ), and another portion of theservice provider 115 is implemented on the intermediate modem or networking device combination, such aspolicy implementation agent 1690 or possiblymodem firewall 1655 as well as other agents (seeFIG. 16 ). This is an embodiment associated with one or more ofFIG. 30 or 36 discussed below, in which the modem bus in the figure represents the Wi-Fi LAN connection via the Wi-Fi modem 946. In this example, theservice provider 115 can still offer individual service plans associated exclusively with one device, or can offer an aggregate plan in which the portion of theservice processor 115 located on the intermediate modem ornetworking device combination 1510 aggregates service plans into one WWAN connection but eachindividual device 100 has a unique service interface via the application interface agents and associated agents located ondevice 100. Similarly, such an implementation can be provided using a different access modem and access network, for example a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem ornetworking device combination 1510. In addition, various other embodiments similarly use USB, Ethernet, Bluetooth, or another LAN or point to point connection fromdevice 100 to the intermediate modem ornetworking device combination 1510. - In some embodiments, all of the
service processor 115 is implemented on the intermediate modem ornetworking device combination 1510 and the aggregate device or user traffic demand from the LAN port is serviced through one service provider service plan account. This is an embodiment associated withFIG. 35 in which as discussed below the modem bus in the figure represents the Wi-Fi LAN connection via the Wi-Fi modem 946. Similarly, such an implementation can be provided using a different access modem and access network, for example a 2G and/or 3G WWAN, DSL wire line, cable DOCSIS wire line or fiber wire line configuration in place of the 3G and/or 4G access network connection to the intermediate modem ornetworking device combination 1510. In addition, various other embodiments similarly use USB, Ethernet, Bluetooth, or another LAN or point to point connection fromdevice 100 to the intermediate modem ornetworking device combination 1510. - In some embodiments, the
device 100 uses the on-board WWAN modem 942 when it is outside of Wi-Fi LAN coverage area for one or more trusted access networks for the device, and when the device comes within range of a Wi-Fi network associated with a intermediate modem or networking device combination connected to a trusted wire line access network, the device can switch to the Wi-Fi link service to connectservice processor 115 to the trusted wire line access network. In some embodiments, the decision to switch to the Wi-Fi LAN associated with a trusted wire line access network can be made automatically by the device based on the policy implementation rules settings for the modem selection andcontrol 1811 and/or thepolicy control agent 1692, can be made by the user, or can be made by the service controller 122 (seeFIG. 18 ). In addition, various other embodiments similarly use USB, Ethernet, Bluetooth, or another LAN or point to point connection fromdevice 100 to the intermediate modem ornetworking device combination 1510. -
FIG. 15C illustrates another hardware diagram of adevice 100 that includes aservice processor 115 and abus structure extension 1510 using intermediate modem or networking device combinations in accordance with various embodiments. In some embodiments, more than one access network connection is implemented in the intermediate modem ornetworking device combination 1510. This allows thedevice 100 to potentially connect through the intermediate modem or networking device combination with a choice of access network services. An example of such an embodiment is illustrated inFIG. 15C in which an access network router (e.g., an enterprise router) connected to a LAN with a wire line primary backhaul connection and a back up WWAN connection, for example 3G or 4G, to provide access services when the primary wire line connection fails. As discussed above, the service provider service profile forservice processor 115 and the service plan account can be set up as an aggregate account with multiple users connected to the LAN. The service provider can elect to use an embodiment that includes a portion of theservice processor 115 on eachdevice 100 so that the account can be managed for each user or each device, or the service provider can elect to implement all of the necessary features in theservice processor 115 on the intermediate modem or networking device combination so that there is no visibility to theindividual devices 100 or users. - As described herein, various embodiments provide many service policy implementation options that can enhance the service provider control of the service experience and cost, or enhance the user control of the service experience and cost by providing a verifiable or compromise resistant solutions to manage service policy implementation on the intermediate modem or networking device combination, for one or both of the WWAN or wire line access networks, when the WWAN access network is active, or when the WWAN access network is inactive. The level of service control, user preference feedback and service policy implementation verification or compromise resistance enabled by these embodiments improves the offered back up services and primary wire line services. One of ordinary skill in the art will also now appreciate that any number of wire line and/or wireless network access connections can be supported by the various embodiments as described herein, with any number of device architectures and architectures for intermediate modem or networking device combinations bridging the device to the access network of choice. Accordingly, various embodiments provide a verifiable managed service architecture, design and implementation for any number of single access and/or multi-access networks in which the service account can be consistent across multiple networks, and the service policies can be changed from network to network as deemed appropriate by the service provider with service notification, service cost control and privacy preference inputs from the user.
- In various embodiments, the verification embodiments discussed herein for service policy implementation verification or service policy implementation compromise protection can be applied. In some embodiments, rather than attaching a service provider service plan account to a single device, it is attached to (e.g., associated with) a user. For example, when the user logs onto an access network with a service controller controlled by a service provider, regardless of what device the user logs onto with the user's service plan profile can be automatically looked up in the
central billing system 123 and dynamically loaded (e.g., downloaded) onto thedevice 100 from the service controller 122 (e.g., a service profile provided on demand based on the user's identity). In some embodiments, in addition to dynamically loading the user's service policy implementation and control settings, one or more of the user's preferences including notification, service control, traffic monitor reporting privacy and Customer Relationship Management (CRM) reporting privacy are also dynamically loaded. For example, this allows the user to have the same service settings, performance and experience regardless of the device the user is logged into and using on the network. In addition, as discussed herein, in the various embodiments that call for roaming from one type of access network to another, the user service plan profile, that includes all of the above in addition to the service plan profile changes that take effect between different types of access network, can be used on any device and on any network, providing the user with a verifiable or compromise resistant, consistent service experience regardless of network or device. - Many of the embodiments described herein refer to a
user using device 100. It is understood that there are also applications for these various embodiments that do not involve user interfaces. Examples of such applications include equipment, apparatus or devices for automation, telemetry, sensors, security or surveillance, appliance control, remote machine to machine data connections, certain remote access configurations, two way power metering or control, asset tracking, people tracking or other applications in which a human user interface is not required fordevice 100. - Various embodiments of the
device 100 described above include other I/O devices 985. In some embodiments, these other devices include other modems, other special purpose hardware components, and/or other I/O devices or drivers or modems to connect to other I/O devices. In some embodiments, these other devices include a Subscriber Identity Module (SIM) or Universal Subscriber Identity Module (USIM) device. In some embodiments, it is advantageous to implement some or all of theservice processor 115 functions on an embodiment ofdevice 100 that includes a SIM and/or a USIM. In some embodiments, the other I/O devices 985 include a hardware device designed to implement a portion or all of theservice processor 115 functions. For example, this is advantageous in cases in which theoriginal device 100 was not manufactured with theservice processor 115; in cases in which dedicated hardware is desired to improve one or more aspects ofservice processor 115 performance; allowing users, for example, to have the same service settings, performance and experience regardless of the device the user is using on the network by using such a SIM and/or USIM (e.g., or implemented as a type of dongle); and/or in cases in which a separate component is desired to assist in compromise protection for one or more aspects ofservice processor 115. - As discussed above, some embodiments described herein provide for billing of certain access services. In some embodiments, various applications do not require or involve billing of certain services. For example, applications like enterprise IT (Information Technology) group management of enterprise workforce access policy implementation or access cost control or access security policy, privacy control, parental control, network quality of service control or enhancement, private network services, free access services, publicly funded access services, flat rate no-options service and other services, or other examples that will be apparent to one of ordinary skill in the art do not require billing functionality but benefit from many other aspects of various embodiments.
- Service Processor and Service Controller for Verifiable Service Monitoring, Notification and Control
-
FIG. 16 is a functional diagram illustrating a device basedservice processor 115 and aservice controller 122 in accordance with some embodiments. For example, this provides relatively full featured device based service processor implementation and service controller implementation. As shown, this corresponds to a networking configuration in which theservice controller 122 is connected to theInternet 120 and not directly to theaccess network 1610. As shown, a data plane (e.g., service traffic plane) communication path is shown in solid line connections and control plane (e.g., service control plane) communication path is shown in dashed line connections. As previously discussed, it is understood that the division in functionality between one device agent and another is based on, for example, design choices, networking environments, devices and/or services/applications, and various different combinations can be used in various different implementations. For example, the functional lines can be re-drawn in any way that the product designers see fit. As shown, this includes certain divisions and functional breakouts for device agents as an illustrative implementation, although other, potentially more complex, embodiments can include different divisions and functional breakouts for device agent functionality specifications, for example, in order to manage development specification and testing complexity and workflow. In addition, the placement of the agents that operate, interact with or monitor the data path can be moved or re-ordered in various embodiments. For example, as discussed below in some embodiments, one or more of the policy implementation or service monitoring functions can be placed on one of the access modems located below the modem driver and modem bus in the communication stack as illustrated in certain figures and described herein. As discussed below, some simplified embodiment figures illustrate that not all the functions illustrated in all the figures are necessary for many designs, so a product/service designer can choose to implement those functions believed to be most advantageous or sufficient for the desired purposes and/or environment. The functional elements shown inFIG. 16 are described below. - As shown,
service processor 115 includes a servicecontrol device link 1691. For example, as device based service control techniques involving supervision across a network become more sophisticated, it becomes increasingly important to have an efficient and flexible control plane communication link between the device agents and the network elements communicating with, controlling, monitoring, or verifying service policy. In some embodiments, the servicecontrol device link 1691 provides the device side of a system for transmission and reception of service agent to/from network element functions. In some embodiments, the traffic efficiency of this link is enhanced by buffering and framing multiple agent messages in the transmissions. In some embodiments, the traffic efficiency is further improved by controlling the transmission frequency or linking the transmission frequency to the rate of service usage or traffic usage. In some embodiments, one or more levels of security or encryption are used to make the link robust to discovery, eavesdropping or compromise. In some embodiments, the servicecontrol device link 1691 also provides the communications link and heartbeat timing for the agent heartbeat function. As discussed below, various embodiments disclosed herein for the servicecontrol device link 1691 provide an efficient and secure solution for transmitting and receiving service policy implementation, control, monitoring and verification information with other network elements. - In some embodiments, the service
control device link 1691 agent messages are transmitted asynchronously as they are generated by one or more of the service agents. In some embodiments, the servicecontrol device link 1691 performs collection or buffering of agent messages between transmissions. In some embodiments, the servicecontrol device link 1691 determines when to transmit based potentially on several parameters including, for example, one or more of the following parameters: periodic timer trigger, waiting until a certain amount of service usage or traffic usage has occurred, responding to a service controller message, responding to a service controller request, initiated by one or more agents, initiated by a verification error condition, initiated by some other error or status condition. In some embodiments, once a transmission trigger has occurred, the servicecontrol device link 1691 assembles all buffered agent communications and frames the communications. - In some embodiments, the transmission trigger is controlled by waiting for an amount of service usage, such as waiting until a certain amount of data traffic has passed, which reduces the control plane communication channel traffic usage to a fraction of the data plane traffic. For example, this approach preserves network capacity and reduces service cost even in traffic scenarios in which data traffic is light.
- In some embodiments, the transmission trigger is based on waiting for an amount of service usage, and also including a minimum transmission rate that triggers a transmission according to one or more of the following parameters: a maximum time between transmissions clock to keep the
service processor 115 in communication with theservice controller 122 when little or no service usage is occurring, a polling request of some kind from theservice controller 122, a response to a service controller heartbeat, a transmission generated by a service verification error event, or a transmission generated by some other asynchronous event with time critical service processor 115 (or service controller 122) messaging needs, such as a transaction or service billing event or a user request. For example, service control plane traffic down is reduced to a relatively inexpensive and capacity conserving trickle whendevice 100 data traffic is not significant. At the same time, this approach also provides an effective flow of real time or near real-time service control plane traffic that is both cost and capacity efficient, because the service control plane traffic is a relatively small percentage of the data plane traffic when data plane traffic usage is heavy. For example, when data plane traffic usage is heavy is generally the time when close monitoring of service policy implementation verification or compromise prevention can be particularly important and by keeping the control plane overhead to a fraction of data plane traffic close monitoring and control of services are maintained at a reasonable cost in terms of percentage of both bandwidth used and network capacity. In some embodiments, the service usage or service activity trigger occurs based on some other measure than traffic usage, such as a number of messages transacted, one or more billing events, number of files downloaded, number of applications run or time that an application has been running, usage of one or more specified applications, GPS coordinate changes, roaming event, an event related to another network connection to the device and/or other service related measures. - In some embodiments, the service
control device link 1691 provides for securing, signing, encrypting or otherwise protecting communications before sending. For example, the servicecontrol device link 1691 can send to the transport layer or directly to the link layer for transmission. In some embodiments, the communications are further secured with transport layer encryption, such as TCP TLS (Transport Control Protocol Transport Layer Security) or another secure transport layer protocol. In some embodiments, communications are encrypted at the link layer, such as IPSEC (Internet Protocol Security), various VPN (Virtual Private Network) services, other forms of IP layer encryption and/or another link layer encryption technique. - In some embodiments, the
service control link 1691 includes the above discussed agent heartbeat function in which the agents provide certain required reports to theservice controller 122 for the purpose of service policy implementation verification (e.g., verification related reports on certain aspects of the service processor 115) or for other purposes. For example, such agent heartbeat messages can be in the open/clear (unencrypted) or encrypted, signed and/or otherwise secured. In some embodiments, these messages include one or more of the below described types of messages: an agent information message, an agent check-in message and/or agent cross check message. - In some embodiments, an agent information message is included in the agent heartbeat service policy implementation verification message, which includes, for example, any information the agent needs to communicate to the
service controller 122 as part of the operation of the service policy implementation system. For example, an agent response to a service controller challenge, as described below, can be included in the agent heartbeat service policy implementation verification message. - In some embodiments, an agent check-in message is included in an agent heartbeat service policy implementation verification message, which includes, for example, a transmission of a unique agent identifier, secure unique identifier, and/or hashed encrypted and signed message beginning with some shared secret or state variable for the hash. For example, an agent self-check can be included in the agent heartbeat service policy implementation verification message, which includes reporting on agent configuration, agent operation, agent code status, agent communication log, agent error flags, and/or other agent associated information potentially hashed, encrypted, signed or otherwise secured in the message (e.g., using a shared secret unique to that agent).
- In some embodiments, an agent cross-check message is included in the agent heartbeat service policy implementation verification message, which includes, for example, reports on the status, configuration, operation observations, communication log or other aspects of another agent. For example, agent environment reports can be included in the agent heartbeat service policy implementation verification message, which includes, for example, reports on certain aspects of the
service processor 1 15 operating environment, such as software presence (e.g., installation status of certain operating system and/or application software and/or components thereof), observed communication with agents or communication attempts, memory accesses or access attempts, network accesses or access attempts, software downloads or attempted downloads, software removal or download blocking, service policy implementation verification or compromise event error conditions with respect to the operating environment for theservice processor 115, and/or other messages regarding the verification or possibility of compromise associated with theservice processor 115 operating environment or agents. - In some embodiments, the agent heartbeat function also provides regular updates for information important to user service notification services. For example, the network based elements can provide regular synchronization updates for the device based service usage or service activity counters in which service usage or service activity measures available from one or more network service history elements is transmitted to the
device 100. This allows the service usage counter errors between the device service counter and the counters used for central billing to be minimized. A common service usage or service activity measure is total traffic usage measured to date within a time frame over which a service limit is applicable. Other service usage or service activity measures can also be tracked and reconciled in a similar manner. - In some embodiments for the heartbeat function, the
service controller 122 verifies that the scheduled agent reports are being received and that the reports are within expected parameters. In some embodiments, the accesscontrol integrity server 1654 issues signed challenge/response sequences to thepolicy implementation agent 1690. For example, the challenges can be asynchronous, issued when an event or error condition occurs, issued on a schedule or issued when a certain amount of data has passed. This approach, for example, provides a second layer of service policy implementation verification that strengthens the service usage or service activity measurement verification. For example, a challenge/response can be sent over the heartbeat link for the purpose of verifying device agent integrity. Various challenge/response related verification embodiments are described below. - In some embodiments, the challenge/response heartbeat message can include sending any kind of command or query, secure or transmitted in the open, receiving a response from the agent and then evaluating the response to determine if the response is within a range of parameters expected for a correctly configured agent, an agent that is operating properly, an agent that is not partially compromised or an agent that is not entirely compromised. In some embodiments, the agent is only required to respond with a simple acknowledgement of the challenge. In some embodiments, the agent is required to respond with a message or piece of information that is known by the agent. In some embodiments, the agent is required to respond with a message or piece of information that is difficult for the agent to respond correctly with if it were to be partially or entirely compromised. In some embodiments, the agent is required to respond back with information regarding the operation or configuration of the agent that is difficult for the agent to respond properly with if the agent is not properly configured, not operating properly, is partially compromised or is entirely compromised. In some embodiments, the first agent is required to respond back with information regarding the operation, configuration, status or behavior of a second agent that is difficult for the first or second agent to respond properly with if the first or second agent is not properly configured, not operating properly, is partially compromised or is entirely compromised. In some embodiments, the agent is required to respond with a response that includes a shared secret. In some embodiments, the agent is required to respond with information regarding the presence, configuration, operating characteristics or other information regarding other programs in the operating environment of the agent. In some embodiments, the agent is required to respond with hashed information to be portions of code or a code sample (e.g., the code portion or code sample can be specified by the service controller 122).
- In some embodiments, the information the agent responds with is a response to a signed or encrypted message from the
service controller 122 in which the agent must know how to decode the encrypted controller message in order to respond correctly or it would be difficult for the agent to respond properly if the agent is not configured properly, is not operating within appropriate limits, is partially compromised or is entirely compromised. In some embodiments, the agent signs or encrypts information in such a manner that it is difficult to respond correctly when the message is decoded by theservice controller 122 unless the agent is configured properly, is operating within appropriate limits, is not partially compromised and is not entirely compromised. In some embodiments, the agent is required to respond with a signed or encrypted hash of information that is difficult for the agent to generate unless the agent is configured properly, is operating within appropriate limits, is not partially compromised and is not entirely compromised. For example, the hashed information can be local device configuration information, portions of code or all of the code, and/or the code portion to be used in the response can be specified by the service controller. In another example, the hashed information the agent responds with can include a shared secret, and/or the hashed information can be information regarding the presence, configuration, operating characteristics or other information regarding other programs in the operating environment of the agent. - Accordingly, as described above, the agent heartbeat function provides an important and efficient system in some embodiments for verifying the service policy implementation or protecting against compromise events. For example, there are many other functions the agent heartbeat service can perform and some are described herein while others will be apparent to one of ordinary skill in the art given the principles, design background and various embodiments provided herein.
- In some embodiments, the service
control device link 1691 facilitates another important function, which is the download of new service processor software elements, revisions of service processor software elements, and/or dynamic refreshes of service processor software elements. There are many embodiments for such operations. In some embodiments, the software is received as a single file over the servicecontrol device link 1691. For example, the file can have encryption or signed encryption beyond any provided by the communication link protocol itself. In some embodiments, the software files are segmented into smaller packets that are communicated in multiple messages sent over the servicecontrol device link 1691. In some embodiments, once the file(s) are received, or the segmented portions of the file(s) are received, they are communicated to aservice downloader 1663 for file aggregation and installation, which, in some embodiments, is performed after further measures to verify the service processor software are completed. In some embodiments, the files are sent using other delivery means, such a direct TCP socket connection to theservice downloader 1663 or some other software installer, which can also involve secure transport and additional levels of encryption. - As shown in
FIG. 16 , anagent communication bus 1630 represents a functional description for providing communication for thevarious service processor 115 agents and functions. In some embodiments, as represented in the functional diagram illustrated inFIG. 16 , the architecture of the bus is generally multipoint to multipoint so that any agent can communicate with any other agent, the service controller or in some cases other components of the device,such user interface 1697 and/or modem components. As described below, the architecture can also be point to point for certain agents or communication transactions, or point to multipoint within the agent framework so that all agent communication can be concentrated, or secured, or controlled, or restricted, or logged or reported. In some embodiments, the agent communication bus is secured, signed, encrypted, hidden, partitioned and/or otherwise protected from unauthorized monitoring or usage. - In some embodiments, as described below, there are multiple layers of security applied to the
agent communication bus 1630 communication protocols, such as including one or more of the following: point to point message exchange encryption using one or more keys that are partially shared or shared within theservice processor 115 agent group and/or theservice controller 122, point to point message exchange that using one or more keys that are private to the two endpoints of the communication, a bus-level message exchange encryption that can be in place of or in addition to other encryption or security, or using one or more keys that are partially shared or shared within theservice processor 115 agent group and/or theservice controller 122, a set of secure messages that can only be decoded or observed by the agents they are intended for, a set of secure messages that allow communication between certain agents or service processor functions and entities outside of the service processor operating environment. In some embodiments, and as described herein, the servicecontrol device link 1691 is assumed to be equivalent to an agent for communication purposes, and, in the case of the servicecontrol device link 1691, the communication is not restricted to theagent communication bus 1630 but also extends to the service control communications link 1653. In some embodiments, the system has the capability to replace keys or signatures on occasion or on a regular basis to further secure against monitoring, eavesdropping or compromise of the agent communication system. - For example, various forms of message encryption and security framework techniques can be applied to encrypt and/or secure the agent communication bus 1630, including one or more of the following: agent bus encryption using shared key for all agents provided and updated by the secure server; agent bus encryption using point to point keys in which the secure server informs the bus and agents of keys and updates as appropriate; agent level encryption using agent to agent shared keys in which the secure server informs agents of the key and updates the key as appropriate; agent level encryption using agent to agent point to point key in which the secure server informs agent of the point to point keys that are required and updates the keys as appropriate; agent level access authorization, which only allows access to the agents that are on the secure authorization list and in which the list is provided by the secure server and signatures are provided by the secure server; UI messages are only analyzed and passed, in which the UI cannot have access to configuration information and cannot issue challenges; agent level heartbeat encryption, which can be point to point or shared key for that agent; control link level heartbeat encryption; TLS (Transport Layer Security) communication protocols; server level heartbeat encryption, which can be point to point or shared key for that secure server; and/or the access control integrity agent 1694 or heartbeat function can become point to multipoint secure communications hubs.
- In some embodiments of the
agent communication bus 1630, the design of the agent communication bus depends on the nature of the design embodiments for the agents and/or other functions. For example, if the agents are implemented largely or entirely in software, then the agent communication bus can be implemented as an inter-process software communication bus. In some embodiments, such an inter-process software communication bus is a variant of D-bus (e.g., a message bus system for inter-process software communication that, for example, helps applications/agents to talk to one another), or another inter-process communication protocol or system, running a session bus in which all communications over the session bus can be secured, signed, encrypted or otherwise protected. For example, the session bus can be further protected by storing all software (e.g., software components, applications and/or agents) in secure memory, storing all software in encrypted form in secure memory, and/or executing all software and communications within a secure execution environment, hardware environment and/or protected memory space. In some embodiments, if the agents and other functions are designed with a mixture of software and hardware, or primarily with hardware, then the implementation of the bus design will vary, and the principles and embodiments described herein will enable one of ordinary skill in the art to design the specifics of theagent communication bus 1630 to meet a particular set of product and desired functional requirements. - As shown in
FIG. 16 , an accesscontrol integrity agent 1694 collects device information on service policy, service usage or service activity, agent configuration and agent behavior. In some embodiments, the accesscontrol integrity agent 1694 also cross checks this information to identify integrity breaches in the service policy implementation and control system. In some embodiments, the accesscontrol integrity agent 1694 also initiates action when a service policy violation or a system integrity breach is suspected. In some embodiments, the accesscontrol integrity agent 1694 also performs asynchronous or periodic agent checks to verify presence, configuration or proper operation of other agents. In some embodiments, the accesscontrol integrity agent 1694 also performs challenge-response sequence verification of other agents. - In some embodiments, the access
control integrity agent 1694 obtains service usage or service activity measures from aservice monitor agent 1696 and compares one or more first service usage measurement points against one or more second service usage measurement points to verify service policy implementation. For example, as shown inFIG. 21 , if the service usage at measurement point IV is inconsistent with measurement point III, which, for example, can indicate, for example, that an unauthorized or unmonitored usage of the access modem (e.g.,modems FIG. 21 , if one or more aspects of upstream traffic usage measurement point II, which represents the upstream demand side ofpolicy implementation agent 1690, is inconsistent with upstream traffic measurement point III, which represents delivered traffic from thepolicy implementation agent 1690, then thepolicy implementation agent 1690 may not be operating properly. As another example, as also shown inFIG. 21 , if service measurement point III and IV indicate thatfirewall agent 1655 is passing traffic to URLs or IP addresses that are in the blocked policy settings, then a verification error condition can be set for the access control policy. As another example, if the policy controller reports traffic usage statistics that are inconsistent with traffic usage policy settings, then a traffic usage policy verification error may have occurred. As another example, if the service usage counter synchronization information received from theservice controller 122, thedevice service history 1618 and/or thecentral billing system 1619, is compared to the service usage history reported by the service monitor agent and the two are found to be outside of acceptable tolerance limits for the comparison, then there may be a verification error in the service monitor service usage or service activity accounting. There are numerous additional embodiments of such comparisons as described herein and others as will be readily apparent to one of ordinary skill in the art given the principles, design background and specific examples and various embodiments described herein. - In some embodiments, device service policy implementations are verified by comparing various service usage measures used at the device against expected service usage or service activity behavior given the policies (e.g., one or more service policy settings, service profile or service profile settings for network based access/services, and/or service plan or service plan for network based access/services). For example, verification is performed based on a measure of total data passed at the device as compared to the service policy for total data usage. For example, verification is performed based on a measure of data passed in a period of time at the device as compared to the service policy for data passed in such a period of time. For example, verification is performed based on a monitoring of communications from the device based on IP addresses as compared to the policy for permissible IP addresses. For example, verification is performed based on a measure of total data passed from the device per IP address as compared to the policy for total data usage per IP address. Other examples include such actual versus policy comparisons based on other measures at/from/to the device, such as location, downloads, email accessed, URLs, and/or any other data, location, application, time or other criteria or any combination of criteria that can be measured for comparing with various policy settings and/or restrictions.
- In some embodiments, the access
control integrity agent 1694 monitors agent self-check reports to verify that agents are properly configured. In some embodiments, the accesscontrol integrity agent 1694 reports the agent self check reports to theservice controller 122. In some embodiments, the accesscontrol integrity agent 1694 performs a role in service usage test transmission, reception and/or monitoring, with the usage test being tailored to test monitoring or control aspects for any subset of service activities. In some embodiments, the accesscontrol integrity agent 1694 performs a role in billing test event generation and/or monitoring. In some embodiments, the accesscontrol integrity agent 1694 checks and reports the result of service usage monitoring verification tests, service usage billing verification tests and/or transaction billing verification tests. - In some embodiments, the access
control integrity agent 1694 receives agent access attempt reports to determine if unauthorized agent access attempts are occurring. In some embodiments, the accesscontrol integrity agent 1694 acts as a central secure communications hub for agent to agent orservice controller 122 to agent communication. For example, the accesscontrol integrity agent 1694 can be used so that no other software or function can access other agents or so that agents cannot access other agents except through the secure point to multipoint communications hub. In some embodiments, this approach further enhances compromise resistance for the agents. In some embodiments, some or all of the agent communications, including agent to agent orservice controller 122 to agent communications, and possibly including unauthorized attempts to communication with agents, are monitored and logged so that a trace log of some or all agent communications can be maintained. For example, the agent communication trace log can be summarized and/or compressed for transmission efficiency or regularly reported, such as through the heartbeat function, or the agent communication trace log can be reported only when theservice controller 122 requests the agent communication trace log or when there is a verification error event. As similarly described above, the partitioning of agent functions and server functions is provided herein mainly to aid in disclosing various embodiments but those of ordinary skill in the art will appreciate that other partitioning of agent functions and server functions can be used based on different design choices. For example, the central agent communication hub function is performed in some embodiments by the accesscontrol integrity agent 1694, however, in other embodiments that function is performed by the servicecontrol device link 1691. For example, when the central agent communication hub function is located in the servicecontrol device link 1691, then architecturally the device link can be a single point to multipoint secure communications hub for all agent to agent andservice controller 122 to agent communications. In some embodiments, this approach has certain advantages from a service policy implementation verification or compromise protection robustness perspective, or has certain advantages from a communications protocol efficiency perspective, or simply can be more efficient to implement. It should be noted that in other embodiments described herein the agent to agent and agent toservice controller 122 communications can be multipoint to multipoint, with each agent having the capability to communicate with other agents or the service controller, this communication can be secure, signed or otherwise encrypted or protected in some embodiments and in the open/clear in others. Also, as discussed in some embodiments, the agents can maintain their own communications or attempted communications log, which can then be reported to theservice controller 122. In some embodiments, the agents implement restrictions on which device components or agents the agents will conduct communications with so that only agents that need to communicate with one another can do so. - In some embodiments, the service
control device link 1691 reviews local billing event history and compares such history to billing event reports to verify that abilling agent 1695 is functioning properly (e.g., has not been tampered with or compromised). In some embodiments, the servicecontrol device link 1691 cross-checks service usage or service activity against billing event reports from thebilling agent 1695 to verify that billing events are properly billing for service usage or service activity. In some embodiments, the servicecontrol device link 1691 cross-checks transaction billing process or records against transaction billing reports to ensure that transaction billing events are being properly reported by thebilling agent 1695. In some embodiments, the servicecontrol device link 1691 determines if one or more agents have been compromised, and if so, initiates a dynamic agent download process to replace any such potentially compromised agent. - In some embodiments, the access
control integrity agent 1694 verifies that the service usage counter is reporting service usage or service cost to the user within acceptable limits of accuracy when compared to the service usage reports obtained from theservice monitor agent 1696, theservice controller 122, thedevice service history 1618 and/or thecentral billing system 1619. In some embodiments, the accesscontrol integrity agent 1694 checks to verify that user privacy filter preferences are being properly implemented. In some embodiments, the accesscontrol integrity agent 1694 checks to verify that the user is properly receiving UI warnings regarding service usage or roaming service usage conditions. - In some embodiments, the access
control integrity agent 1694 checks to verify that the device is not beginning service usage until it has been authenticated, authorized or granted access to the network. In some embodiments, accesscontrol integrity agent 1694 checks with theservice controller 122 or thebilling system 1619 to verify that the user or device has a valid service standing and should be admitted to access on the network. - In some embodiments, an Activation Tracking Service (ATS) is provided in which the service monitoring function (e.g., performed by the
service monitor agent 1696 and/or some other agent/component or combinations thereof on the device) is used in part to determine which access networks are being connected to and to record and/or report this information. In some embodiments, the ATS is only enabled if the device user approves reporting of access networks connected to by the user device. In some embodiments, the ATS is protected from tampering. For example, the ATS can be hardened, that is, to be more tamper resistant, using a variety of techniques, including any of the following: the ATS can be located (e.g., stored) in secure memory and/or secure hardware; the ATS can be implemented in the system BIOS, the access modem and/or another hard to access portion of the device; a second device agent can confirm the presence of the ATS with a report to a network based server; the second agent or the network server can initiate a reinstall of the ATS if it is missing or is found to be operating improperly; and/or the ATS can be placed in a secure area of the OS so that it cannot be removed or if removed must be replaced for proper device operation to resume. A variety of other tamper resistance techniques can also be used to protect the ATS from tampering as similarly described herein with respect to other device based functions/software components/agents. - In some embodiments, the access
control integrity agent 1694 verifies that ATS software or hardware is present, properly configured or operating properly. In some embodiments, the accesscontrol integrity agent 1694 reviews network connection or activity history and compares such to ATS reports to verify activation tracking service reports are occurring properly. In some embodiments, the accesscontrol integrity agent 1694 replaces ATS software if it has been removed. In some embodiments, the accesscontrol integrity agent 1694 monitors access or compromise of ATS software to determine if it may have been compromised. In some embodiments, the accesscontrol integrity agent 1694 reports status of ATS functions. - In some embodiments, the access
control integrity agent 1694 scans the local agent execution environment to determine if there are unauthorized accesses to service processor functions, settings or code. In some embodiments, the accesscontrol integrity agent 1694 monitors software loading activity, protected memory access or communication withservice processor 115 agents to detect unauthorized changes to service processor software or configuration. For example, the accesscontrol integrity agent 1694 can have a local database of potentially malicious elements and compare entries in the database against the elements detected locally. As another example, the accesscontrol integrity agent 1694 can communicate a list of some or all of the elements detected locally to theservice controller 122 to augment or take the place of the database comparison function that may be performed locally. In some embodiments, the accesscontrol integrity agent 1694 detects new software downloads, installs or invocations and immediately issues an error flag report when potentially malicious software is downloaded, installed or invoked. In some embodiments, the accesscontrol integrity agent 1694 scans the local software loading and invocation activity along with a log of other software runtime events and regularly reports this trace so that when an error or compromise event occurs the trace preceding the event can be analyzed to determine the offending software or activity trace that took place to cause the compromise or error. Once the software or activity that caused the compromise is known, it can be entered into a refreshed version of the database that the device and other devices use to detect potentially malicious pre-cursor conditions. Examples of such pre-cursor events include software invocations, software downloads, attempts to uninstall certain agent and/or application software/components or OS components, a sequence of memory I/O events, a sequence of software access events, a sequence of network address or URL communications or downloads or a sequence of access modem I/O activity. In various other embodiments of the accesscontrol integrity agent 1694, the agent performs or (securely) communicates with other software/hardware device/network components that perform other well known signature, behavior blocking and/or intrusion detection identification/detection and/or blocking techniques based on the presence of potentially unwanted and/or potentially or known malicious software and/or intrusion attempts by unauthorized software and/or unauthorized users, using, for example, real-time, on access, periodic, and/or on demand scanning. - In some embodiments, the access
control integrity agent 1694 detects or blocks potentially compromising behavior of other software programs/users attempting unauthorized behavior in theservice processor 115 operating environment. In some embodiments, the accesscontrol integrity agent 1694 detects software that is being loaded that has the same or similar name, identification, memory location or function as one or more of theservice processor 115 agents. In some embodiments, the accesscontrol integrity agent 1694 blocks operation or loading of such software. In some embodiments, the accesscontrol integrity agent 1694 detects or blocks unauthorized access ofservice processor 115 protected memory. In some embodiments, the accesscontrol integrity agent 1694 verifies configuration and operation ofsecure service downloader 1663. In some embodiments, the accesscontrol integrity agent 1694 monitors network and I/O activity to detect potentially compromising events, such as a program that is downloaded from known detrimental or potentially suspect IP addresses or URLs or a program that accesses certain IP addresses or URLs. In some embodiments, the accesscontrol integrity agent 1694 scans of the service processor operating environment are recorded and kept for a period of time, and if a service policy verification error occurs, then the scans immediately prior to the error are analyzed or reported to theservice controller 122 for analysis. In some embodiments, such scans are regularly reported to theservice controller 122 without the presence of service policy verification error conditions. - In some embodiments, the access
control integrity agent 1694 requests a dynamic agent download of certain critical service processor functions, including in some cases the accesscontrol integrity agent 1694 on a periodic basis, or on a periodic basis when network access activity is not required or minimal. - In some embodiments, the access
control integrity agent 1694 determines if a threshold has been surpassed for a max usage trigger for ambient and/or other services that should not be using significant amounts of data (e.g., based on the type of device and/or service profile settings). - In some embodiments, the access
control integrity agent 1694 determines if verification errors exist in one or more of the verification process embodiments and, in some embodiments, reports errors immediately or in the next agent heartbeat to theservice controller 122. In some embodiments, any number of results from the above checks, monitoring activities, reports or tests are reported to theservice controller 122. - In some embodiments, a
policy control agent 1692 receives policy instructions from theservice controller 122 and/or the user via thebilling agent 1695 and adapts device service policy settings (e.g., instantaneous device service policy settings) in one or more of the following agents/components: apolicy implementation agent 1690, themodem firewall 1655 and/or anapplication interface agent 1693. As shown inFIG. 16 , themodem firewall 1655 is in communication with amodem driver 1640, which is in communication with theagent communication bus 1630 andaccess network 1610. As shown with respect toaccess network 1610, acentral billing server 1619, an accessnetwork AAA server 1621 anddevice server history 1618 are also provided. As shown, theInternet 120 is accessible via theaccess network 1610 andfirewall 124, from whichdevice 100 can then accessvarious Internet services 1615. - In some embodiments, the
policy control agent 1692 adapts low level service policy rules/settings to perform one or more of the following objectives: achieve higher level service usage or cost objectives, reduce network control channel capacity drain, reduce network control plane server processing bandwidth, and/or provide a higher level of user privacy or network neutrality while satisfying service usage or service activity objectives. In some embodiments, thepolicy control agent 1692 performs a policy control function to adapt instantaneous service policies to achieve a service usage objective. In some embodiments, thepolicy control agent 1692 receives service usage information from theservice monitor agent 1696 to evaluate service usage history as compared to service usage goals. In some embodiments, thepolicy control agent 1692 usesservice monitor 1696 service usage or service activity history and various possible algorithm embodiments to create an estimate of the future projected service usage. In some embodiments, thepolicy control agent 1692 uses a future projection of service usage to determine what service usage or service activity controls need to be changed to maintain service usage goals. In some embodiments, thepolicy control agent 1692 uses service usage history to perform a service usage or service activity analysis to determine the distribution of service usage across service usage elements within categories, such as usage by application, usage by URL, usage by address, usage by content type, usage by time of day, usage by access network, usage by location, and/or any other categories for classifying service usage. In some embodiments, thepolicy control agent 1692 uses the service usage distribution analysis to determine which service usage elements or service activities are creating the largest service usage (e.g., if e-mail, social networking, or multimedia/online video application categories are creating the largest service usage). - In some embodiments, the
policy control agent 1692 is instructed, for example, by the user, throughbilling agent 1695 to perform a service control algorithm, such as traffic shaping or download management, to manage service usage or service activities to assist the user in controlling service costs. As a basic example of such a traffic shaping algorithm, the traffic shaping algorithm can simply reduce traffic speed for all applications and traffic types successively until the service usage projections are within service usage limits for the present service billing period. To illustrate an algorithm that is more sophisticated and provides the advantage of leaving many service usage elements or service activities unaffected while only controlling down usage on the most aggressive service usage elements or service activities, the traffic shaping algorithm can identify the highest traffic usage applications and/or websites and successively reduce traffic speed just for the highest usage applications and/or websites until the service usage projections are within service usage limits for the present service billing period. These examples thereby reduce network traffic for the user in accordance with the user's service usage objectives while maintaining overall satisfactory service usage experience for the user in a manner that satisfies various net neutrality requirements (e.g., the traffic throttling of certain applications/websites based on user input in which categories based on service usage history are selected by the user, for example, a certain application may be using 90% of the aggregate traffic usage). For example, adaptive throttling algorithms can be used to throttle application traffic that the user requests throttling, such as recursively throttling of the specified application traffic (e.g., to denigrate the traffic usage associated with that application and thereby reduce overall service data usage). - In some embodiments, the
policy control agent 1692 adjusts service policy based on time of day. In some embodiments, thepolicy control agent 1692 obtains a measure of network availability and adjusts traffic shaping policy settings based on available network capacity. In some embodiments, thepolicy control agent 1692 automatically and dynamically adjusts service policy based on one or more other service policy settings, the service profile and/or the service plan associated with the device and/or user of the device. - In some embodiments, various lower level service policy implementation embodiments are combined with a higher level set of service policy supervision functions to provide device assisted verifiable network access control, authentication and authorization services.
- In some embodiments, device based access control services are extended and combined with other policy design techniques to create a simplified device activation process and connected user experience referred to herein as ambient activation. In some embodiments, ambient access generally refers to an initial service access in which such service access is in some manner limited, such as where service options are significantly limited (e.g., low bandwidth network browsing and/or access to a specific transactional service), limited bandwidth, limited duration access before which a service plan must be purchased to maintain service or have service suspended/disabled or throttled or otherwise limited/reduced/downgraded, and/or any other time based, quality based, scope of service limited initial access for the network enabled device. In some embodiments, ambient activation is provided by setting access control to a fixed destination (e.g., providing access to a portal, such as a web page (e.g., for a hotspot) or WAP (Wireless Application Protocol) page, that provides the user with service plan options for obtaining a service plan for the user desired access, such as the service plan options for data usage, service types, time period for access (e.g., a day pass, a week pass or some other duration), and costs of service plan(s)). In some embodiments, service data usage of the ambient activated device is verified using IPDRs (e.g., using the device ID/device number for the device 101 to determine if the device has been used in a manner that is out of plan for the service plan associated with the device 101, such as based on the amount of data usage exceeding the service plan's service data usage limits, out of plan/unauthorized access to certain websites, and/or out of plan/unauthorized transactions). In some embodiments, service data usage of the ambient activated device is verified by setting a maximum data rate in the
policy control agent 1692 and if/when it is determined that the device is exceeding a specified data rate/data usage, then the service data usage is throttled accordingly. In some embodiments, various other verification approaches are used for ambient activation purposes. - In some embodiments, the policy control agent 1692 (and/or another agent/component of the
service processor 115 and/or service controller 122) performs a service control algorithm to assist in managing overall network capacity or application QoS (Quality of Service). In some embodiments, the policy control agent 1692 (and/or another agent/component of the service processor 115) performs an access network selection algorithm to determine which access network to connect to based on connection options and determined strengths of available wireless networks, network preference or security settings, service usage cost based network preferences, and/or any other criteria. - Accordingly, as described herein with respect to various embodiments, service usage or service activities can be measured by various agents at various different measurement points, which provides for a more robust verification and integrity of device based services communication. For example, it is much less likely and more difficult to compromise and/or spoof multiple agents. As described herein, various verification and integrity checks are performed, including, for example, network based service usage measurement (e.g., using IPDRs); heartbeat monitoring; agent based heartbeat (e.g., challenge/response queries); agent operating environment protection; monitoring agent communications; agent cross-checks; comparing device based and network based measures (e.g., service usage measures); dynamic software/agent download; and/or any combination of these and various other verification/integrity check techniques described herein and/or apparent from the various embodiments described herein.
- In some embodiments, the
device 100 is capable of connecting to more than one network and device service policies are potentially changed based on which network the device is connected to at the time. In some embodiments, the network control plane servers detect a network connection change and initiate the service policy implementation established for the second network. In some embodiments, the device based adaptive policy control agent, as described herein (e.g., policy control agent 1692), detects network connection changes and implements the service policies established for the second network. - In some embodiments, when more than one access network is available, the network is chosen based on which network is most preferred according to a network preference list or according to which network that optimizes a network cost function. For example, the network preference list can be pre-established by the service provide and/or the user and/or later modified/adjusted by either the service provider and/or the user. For example, the cost function can be based on determining a minimum service cost, maximum network performance, whether or not the user or device has access to the network, maximizing service provider connection benefit, reducing connections to alternative paid service providers, and/or any other cost related criteria for network selection purposes.
- In some embodiments, the
device 100 detects when one or more preferred networks are not available, implements a network selection function or intercepts other network selection functions, and offers a connection to the available service network that is highest on a preference list. For example, the preference list can be set by the service provider, the user and/or the service subscriber. In some embodiments, a notification is provided to the device/user when the device is not connected to a network (e.g., indicating in a pop-up/bubble or other UI based display a notification, such as “You are not connected to the network. Click here to learn more, get free trial, use a session, sign-up for service”). In some embodiments, the notification content can be determined based on usage service patterns, locally stored and/or programmable logic on the device and/or a server (e.g., device reports that user is not connected and WWAN is available). Decisions on what bubble to present when may be in pre-stored logic on device. - In some embodiments, service policies are automatically adapted based on the network to which
device 100 is connected. For example, the device can be a cellular communication based device connected to a macrocell, a microcell, a picocell, or a femtocell (e.g., femto cells generally provide a low power, small area cellular network used, for example, in homes or offices, which, for example, can be used as an alternative to Wi-Fi access). In some embodiments,service monitoring agent 1696 and/orbilling agent 1695 modify service usage counting and/or billing based on whether the device is connected to a macrocell, microcell, picocell or femtocell. In some embodiments, the device recognizes which type of network it is currently connecting to (e.g., looking up in a local or network table for the current base station connected to, and/or the information is broadcast to the device upon the connection with the base station), that is, whether it is a macrocell, microcell, picocell or femtocell. In other embodiments, the device does not recognize which type of network it is currently connected to, but reports its current base station, and the network uses a network lookup function to determine which type of network it is connected to. In some embodiments, the device adjusts the billing based on the type of network it is connected to, or in other embodiments, the device calculates an offset to such billing based on the type of network it is connected to, and/or in other embodiments, the device records such service usage associated with the type of network it is connected to and the network billing can adjust the billing accordingly. For example, the billing can be lower for service data usage over a femtocell versus a macrocell. In some embodiments, service policies are adjusted based on the type of network that the device is connected, such as billing, user notification, data usage/bandwidth, throttling, time of day, who owns the cellular network connection (e.g., user's home femtocell, or user's work femtocell, or a commercial business's femtocell like a coffee shop or any other common area like an airport) and/or any other service policy can be different for a femtocell connection (or for any other type of connection, such as a macrocell, microcell, or picocell). In some embodiments, the local service usage counter is adjusted based on the type of network (and/or based on the time of day of such service activity) that the device is connected, such as billing, user notification, data usage/bandwidth, and/or any other service policy can be different for a femtocell connection (or for any other type of connection, such as a macrocell, microcell, or picocell). In some embodiments, the service policies and/or billing policies are adjusted based on network congestion. - In some embodiments, if adaptive service policy control is not required, then the
policy control agent 1692 can simply pass instantaneous service policy settings directly to the agents responsible for implementing instantaneous service policies. - In some embodiments, a
policy implementation agent 1690 implements traffic shaping and QoS policy rules for thedevice 100. In some embodiments, thepolicy implementation agent 1690 provides a firewall function. In some embodiments, thepolicy implementation agent 1690 performs traffic inspection and characterization. In some embodiments, packet inspection is aided by literal or virtual application layer tagging while in other embodiments packet inspection is performed entirely in/by thepolicy implementation agent 1690. In some embodiments, thepolicy implementation agent 1690 accepts service policy implementation settings from thepolicy control agent 1692 or directly from theservice controller 122. More detail on specific embodiments for thepolicy implementation agent 1690 is provided below with respect to the figures associated with communication stack and communication protocol flow. - In some embodiments, the burst size, buffer delay, acknowledgement delay and drop rate used in upstream and downstream traffic shaping are optimized with the goal of reducing access network traffic overhead, and excess capacity usage that can result from mismatches in traffic transmission parameters with the access network MAC and PHY or from excess network level packet delivery protocol re-transmissions. In some embodiments, the
application interface agent 1693 is used to literally tag or virtually tag application layer traffic so that the policy implementation agent(s) 1690 has the necessary information to implement selected traffic shaping solutions. As shown inFIG. 16 , theapplication interface agent 1693 is in communication with various applications, including aTCP application 1604, anIP application 1605, and avoice application 1602. - In some embodiments, downstream literal or virtual application tagging are delayed until a traffic flow passes through the service policy implementation functions and to the application interface function where the service flow is then identified and associated with the underlying traffic and application parameters, and the literal or virtual tag is then communicated to the first policy implementation function or service monitoring function in the downstream traffic processing stack. In some embodiments, prior to being associated with a literal or virtual tag, the traffic flow is allowed to pass with no traffic shaping, and once the traffic flow is identified and tagged, the appropriate traffic shaping is applied. In some embodiments, a set of traffic shaping policy parameters are applied to the unidentified traffic flow before the flow is identified, and then the traffic shaping policy for the flow is updated when the flow is tagged. In some embodiments, the traffic flow can be blocked at the application interface agent even before the tag is passed to the policy implementation functions if it is found to be associated with traffic parameters that are blocked by policy once packet processing, framing and encryption are removed.
- In some embodiments, a
service monitor agent 1696 records and reports device service usage or service activities ofdevice 100. In some embodiments, service usage history is verified by a number of techniques including verifying against network based service usage history (e.g., device service history 1618) and the various service policy implementation techniques as described herein. - In some embodiments, the
service monitor agent 1696 includes the capability to filter service usage history reporting with the decision on which aspects of service history to report being determined by policies including possibly privacy policies defined by the device user or control plane servers in the network. In some embodiments, theservice monitor agent 1696 monitors and possibly records or reports Customer Resource Management (CRM) information such as websites visited, time spent per website, interest indications based on website viewing, advertisements served to the device, advertisements opened by the user, location of the user, searches conducted by the user, application usage profile, device user interface usage history, electronic commerce transactions, music or video files played, applications on device, and/or when the user is actively working or playing or inactive. In some embodiments, to protect the privacy of this user CRM information, the user is provided with options on how much of the information to share and the user's response to the options are recorded and used to determine the filtering policy for how much of the CRM data to report (e.g., CRM filter level options selected by the user via the device UI and/or via various service plan or service profile or service policy options) and how much to suppress or to not even monitor/record/store in the first place. In some embodiments, to protect the privacy of this user's GPS/location tracking related information, the user is provided with options on how much of the information to share and the user's response to the options are recorded and used to determine the filtering policy for how much of the GPS/location tracking related data to report (e.g., GPS/location tracking filter level options) and how much to suppress or to not even monitor/record/store in the first place. In some embodiments, theservice processor 115 allows the user to provide feedback on the user's preferences, such as for privacy/CRM data to report. In some embodiments, the user can also specify their preference(s) for notification (e.g., related to service usage/cost, traffic reporting and other service usage/monitored information) and/or service controls. In some embodiments, theservice monitor agent 1696 observes and possibly records or reports service usage categorized by network possibly including roaming networks, paid service networks or free service networks. In some embodiments, theservice monitor agent 1696 observes and possibly records or reports service usage categorized by sub-accounts for various types of traffic or various types of network. - For example, service monitor reports can be provided to the
service controller 122. Service is monitored through various embodiments that can involve service usage logging or traffic inspection and usage logging at the application level, various levels in the networking communication stack or the access modem. Some embodiments involve multiple levels of service or traffic measurement at various levels in the communications stack as described further below. - In some embodiments, service or traffic monitoring includes monitoring one or more of the following: traffic associated with one or more users; traffic downstream and/or upstream data rate; total traffic received and/or transmitted over a period of time; traffic transmitted and/or received by IP addresses, domain names, URLs or other network address identifiers; traffic transmitted and/or received by email downloads or uploads; traffic transmitted and/or received by an application; traffic transmitted and/or received by network file transfers; traffic transmitted and/or received by file download or upload content types; traffic transmitted and/or received by mobile commerce transactions; traffic transmitted and/or received by one or more time periods; traffic transmitted and/or received by differing levels of network activity and network capacity availability; traffic transmitted and/or received by one or more delivered levels of quality of service; traffic transmitted and/or received by software downloads; traffic transmitted and/or received by application downloads; traffic transmitted and/or received by one or more activities associated with the service control plane link or other network related functions, or traffic that may not directly result in service usage or service activity that the user values or desires; traffic transmitted and/or received to support one or more service provider third party service partner offerings; software usage history; application usage history; device discovery history for UI components, applications, settings, tutorials; ads served history; ads visited history; and/or device location history.
- In some embodiments, some or all of the service usage monitoring occurs at the application layer. In some embodiments, the
service monitor agent 1696 implements traffic inspection points between the applications and the networking stack application interface, such as the sockets API. In other embodiments, theapplication interface agent 1693 performs traffic inspection and reports the results to theservice monitor agent 1696. Traffic inspection can be accomplished in several ways, including, for example, implementing a T-buffer at each socket connection and feeding the side traffic into a traffic flow analyzer, which in combination with a mapping of application to socket provides much of the information listed above. In cases in which it is necessary to obtain traffic information from the application itself, some embodiments call for the application to be adapted to provide the information to either theapplication interface agent 1693 or theservice monitor agent 1696. As an example, theapplication interface agent 1693 or theservice monitor agent 1696 can monitor and decode advertisements downloaded via HTTP, but if the browser and HTTP server employ security above the sockets protocol stack layer then the application interface agent can communicate with the browser via a java applet or some other inter-process communication method. In some embodiments, theservice monitor agent 1696, thebilling agent 1695 and/or the policy control agent 1692 (or some other software or hardware function on the device) can monitor and/or control (e.g., allow, block and/or replace) advertisement traffic flow into the device. In some embodiments, the monitoring and control of advertisement traffic flow into the device is also used for bill by account purposes (e.g., charges, such as service charges, billed to the advertiser, sponsor, and/or service or transactional service provider). - In some embodiments, some or all of the service usage monitoring occurs below the application interface for the networking stack. In this case, some portion of the information listed above may not always be available due to encryption applied at the higher layers and/or the computational costs associated with performing deep packet inspection on mobile devices.
- In some embodiments, the
service monitor agent 1696 is also monitors the operating software install or loading systems, and/or otherwise monitors software installs or loads and/or software uninstalls/deinstallations. - Some of the information above may be considered by some users, advocacy groups or agencies as customer sensitive personal information. Simply sending the above information to the network for unspecified purposes may not, therefore, be acceptable for some service providers. However, if the user provides specific approval (e.g., informed consent) for the device, network or service provider to use some or all of the information that may be sensitive for specified purposes, then the user can control the level of information that is used and the purpose the information is used for. Accordingly, various embodiments described herein provide the user with control of what information is used and the purposes it is used for thereby allowing the user adequate control of any such sensitive information. In some embodiments, information that is thought to perhaps be sensitive and is reported to the network must first receive user approval for the reporting. Some basic information is generally not considered sensitive and is necessary for certain basic service provider needs. For example, total data transmitted and/or received, traffic downstream and/or upstream speed, overall traffic usage by time of day are generally not considered private from the service provider's perspective and are necessary in many basic service policy implementations. As additional examples, perhaps other service usage history, such as total traffic email downloads and uploads but not the type of files or any specifics about the email traffic, the total web browsing traffic but nothing specific about the sites visited or content viewed, total file transfer traffic but not the type of files transferred or the addresses involved in the transfer, and other examples may not be viewed as private and, in some embodiments, provide valuable information for the service provider to manage services. Conversely, information such as websites visited, content viewed, mobile commerce transactions completed, advertisements visited, GPS location history and other service usage history the service monitor is capable of recording may be sensitive or private for some users and would thereby benefit from the various embodiments that provide enhanced user control of the reporting of such potentially sensitive or private data. It should also be appreciated that there is an inherent advantage to implementing traffic monitoring, traffic, service monitoring or service control on a device, because it is not necessary to report sensitive information to the network to accomplish many of these service policy implementation objectives.
- In some embodiments, the
service monitor agent 1696 assists in virtual application tagging of traffic flows through the networking stack policy implementation by tracking the virtually tagged packets through the stack processing and communicating the flow tags to the service policy implementation agent(s) 1690. In some embodiments, theservice monitor agent 1696 maintains a history and provides reports or summary reports of which networks in addition to the networks controlled by theservice controller 122 to which the device has connected. In some embodiments, this network activity summary includes a summary of the networks accessed, activity versus time per connection, and/or traffic versus time per connection. In some embodiments, the traffic reports that go to the network, possibly toservice controller 122,billing system 1619 and/ordevice service history 1618, are first filtered according to rules defined by user preference selection at the time of service activation (e.g., service plan/service plan option selection), time of first device use, at a time the user selected the option on the service UI or at a time the user chose to change the option on the service UI or some other time/mechanism allowing for user preference selection. - In some embodiments, the
service monitor agent 1696 monitors application usage (e.g., which application the user executes on the device 101, such as e-mail applications, web browsing applications and/or media content streaming applications). In some embodiments, theservice monitor agent 1696 monitors multimedia file usage (e.g., based on multimedia file type and/or based on specific multimedia files, such as specific movies and/or songs). In some embodiments, theservice monitor agent 1696 monitors the device user interface, application, and content discovery history (e.g., monitoring which applications/content the user accesses from the device, including monitoring the pattern by which the user accesses such applications/content, such as how the user navigates the user interface on the device to access such applications/content and maintaining such patterns and history, such as which icons the user access on a home page, secondary or other portion/mechanism on the device for accessing various applications/content). In some embodiments, theservice monitor agent 1696 monitors advertisements provided to the user on the device 101. In some embodiments, theservice monitor agent 1696 monitors advertisements viewed (e.g., accessed, such as by clicking on a web advertisement) by the user on the device 101. In some embodiments, theservice monitor agent 1696 monitors GPS/location information for the device 101. As will be appreciated by those of ordinary skill in the art, theservice monitor agent 1696 can monitor a wide variety of activities performed by the device/user of the device and/or based on other information related to the device 101 such as GPS/location information. As described herein, in some embodiments, the user of the device 101 can also specify which activities that the user authorizes for such monitoring (e.g., the user may prefer to not allow for such GPS/location monitoring). - In some embodiments, the
application interface agent 1693 provides an interface for device application programs. In some embodiments, theapplication interface agent 1693 identifies application level traffic, reports virtual service identification tags or appends literal service identification tags to assist service policy implementation, such as access control, traffic shaping QoS control, service type dependent billing or other service control or implementation functions. In some embodiments, theapplication interface agent 1693 assists with application layer service usage monitoring by, for example, passively inspecting and logging traffic or service characteristics at a point in the software stack between the applications and the standard networking stack application interface, such as the sockets API. In some embodiments, theapplication interface agent 1693 intercepts traffic between the applications and the standard network stack interface API in order to more deeply inspect the traffic, modify the traffic or shape the traffic (e.g., thereby not requiring any modification of the device networking/communication stack of the device OS). In some embodiments, theapplication interface agent 1693 implements certain aspects of service policies, such as application level access control, application associated billing, application layer service monitoring or reporting, application layer based traffic shaping, service type dependent billing, or other service control or implementation functions. - In some embodiments, application layer based traffic monitoring and shaping can be performed as described below. The traffic from each application can be divided into one or more traffic flows that each flow through a traffic queue, with each queue being associated with one or more additional classifications for that application (e.g., the application can be a browser that is associated with multiple queues representing different destinations or groups of destinations it is connected to, with each destination or group of destinations having potentially different access control or traffic control policies, or the application can be associated with different content types or groups of content types with each content type having different queues, the application might be an email program with email text traffic going to one queue and downloads going to another with different policies for each). In some embodiments, queues are formed for all applications or groups of applications that are associated with one or more traffic parameters such as destination, content type, time of day or groups of applications can be similarly assigned to different queues. The functions performed by the application layer queues can be similar to the functions described for the policy implementation agent, such as pass, block, buffer, delay, burst in order to control the traffic or network access associated with the queue. The drop function can also be implemented, such as for application layer protocols that include reliable transmission methods, but if the application layer protocol does not involve reliable retransmission of lost information this can result in lost data or unreliable communication which may be acceptable in some cases. The manner in which the queues are controlled can be constructed to result in a similar approach for controlling services or implementing service activity control similar to the other embodiments described herein, including, for example, the
policy control agent 1692 implementing an higher layer of service control to achieve a higher level objective as discussed herein. - In some embodiments, the
application interface agent 1693 interacts with application programs to arrange application settings to aid in implementing application level service policy implementation or billing, such as email file transfer options, peer to peer networking file transfer options, media content resolution or compression settings and/or inserting or modifying browser headers. In some embodiments, theapplication interface agent 1693 intercepts certain application traffic to modify traffic application layer parameters, such as email file transfer options or browser headers. In some embodiments, theapplication interface agent 1693 transmits or receives a service usage test element to aid in verifying service policy implementation, service monitoring or service billing. In some embodiments, theapplication interface agent 1693 performs a transaction billing intercept function to aid thebilling agent 1695 in transaction billing. In some embodiments, theapplication interface agent 1693 transmits or receives a billing test element to aid in verifying transaction billing or service billing. - In some embodiments, a
modem firewall 1655 blocks or passes traffic based on service policies and traffic attributes. In some embodiments, themodem firewall 1655 assists in virtual or literal upstream traffic flow tagging. Although not shown inFIG. 16 , in some embodiments, themodem firewall 1655 is located on either side of the modem bus and in some embodiments it is advantageous to locate it on the modem itself. - In some embodiments, the
billing agent 1695 detects and reports service billing events. In some embodiments, thebilling agent 1695 plays a key role in transaction billing. In some embodiments, thebilling agent 1695 performs one or more of the following functions: provides the user with service plan options, accepts service plan selections, provides options on service usage notification policies, accepts user preference specifications on service usage notification policies, provides notification on service usage levels, provides alerts when service usage threatens to go over plan limits or to generate excess cost, provides options on service usage control policy, accepts choices on service usage control policy, informspolicy control agent 1692 of user preference on service usage control policy, provides billing transaction options and/or accepts billing transaction choices. In some embodiments, thebilling agent 1695 interacts with transaction servers (e.g., open content transaction partner sites 134) to conduct ecommerce transactions withcentral billing 1619. - In some embodiments,
service processor 115 includes one or more service usage or service activity counters. For example, theservice monitor agent 1696,billing agent 1695 or a combination of these agents and/or other agents/components ofservice processor 115 can include such a local service usage counter(s) for the device 101. In some embodiments, a service usage counter monitors service usage including data usage to/from the device 101 with theaccess network 1610. In some embodiments, the service usage counter periodically, in response to a user request, in response to aservice processor 115 agent's request (e.g., thebilling agent 1695, thepolicy control agent 1692, or another agent of service processor 115), in response to theservice controller 122, and/or in response to the central billing 1619 (e.g., for billing purposes and/or for storing in the device service history 1618), provides a service usage report, including monitored service usage for the device 101. In some embodiments, the service usage counter periodically, or in response to a request, synchronizes the service usage counter on the device 101 with a network (and/or billing) service usage counter, such as that maintained potentially atcentral billing 1619. In some embodiments,service processor 115 utilizes the service usage counter to provide a service usage projection. In some embodiments,service processor 115 utilizes the service usage counter to provide a service usage cost estimate. In some embodiments, service usage projections frompolicy control agent 1692 are used to estimate the projected future service usage if user service usage behavior remains consistent. In some embodiments,service processor 115 utilizes the service usage counter to provide a cost of service usage, and theservice processor 115 then periodically, or in response to a request, synchronizes the cost of service usage with, for example, thecentral billing 1619. In some embodiments, theservice processor 115 utilizes the service usage counter to determine whether the user is exceeding and/or is projected to exceed their current service plan for data usage, and then various actions can be performed as similarly described herein to allow the user to modify their service plan and/or modify (e.g., throttle) their network data usage. In some embodiments, the service usage counter can support providing to the user the following service usage related data/reports: service usage, known usage and estimated usage, projected usage, present costs, projected costs, cost to roam, cost to roam options, and/or projected roaming costs. For example, including a local service data usage counter on the device 101 allows theservice processor 115 to more accurately monitor service data usage, because, for example, network (and/or billing) service usage counters may not accurately also include, for example, control plane data traffic sent to/from the device 101 in their monitored service data usage count. - In some embodiments, verifiable device based service billing solutions are provided. For example, as described herein, various device based service billing solutions can include a wide range of verification techniques to ensure that the device is properly reporting service billing events (e.g., to verify/ensure that the service billing is not malfunctioning and/or has not been tampered with/compromised such that it is not accurately or timely providing service billing information). As described herein, service billing generally refers the billing for one or more services for a device, such as device 101 (e.g., email service billing for data usage associated with received/sent email related data over the
access network 1610, web browsing service billing for data usage associated with received/sent web browsing related data over theaccess network 1610 and/or any other network based service, and/or any transactional based services, such as for multimedia content purchases or other transactions). - In some embodiments, verifiable device based service billing is provided by sending dummy(/test) billing events, such as having an access
control integrity server 1654 of theservice controller 122 instruct the accesscontrol integrity agent 1694 to send a dummy(/test) billing event to thebilling agent 1695. If the billing agent does not then send the expected report, which should reflect the dummy(/test) (or fails to timely send any report), then the system can verify whether the billing process is working properly. In addition, a dummy(/test) transaction can be used to verify transaction based billing through a variety of approaches (e.g., the accesscontrol integrity agent 1694 can similarly send a dummy(/test) transactional billing event to thebilling agent 1695 as a test to determine whether thebilling agent 1695 then provides the expected report reflecting that dummy(/test) transaction). For example, the test billing events can be trapped by a device assisted billing mediation server and removed from the user account billing. - In some embodiments, verifiable device based service billing is provided by sending one or more data bursts to the device to confirm that data was received and to confirm that the
service monitor agent 1696 properly logged the data burst(s) in the local service usage or service activity counter. In some embodiments, data bursts can be used to verify data throttling (e.g., if the device has exceeded service data usage limits and/or is approaching such limits such that service data usage should be throttled, then sending data bursts can be used to verify whether the expected throttling is properly being performed on the device). In some embodiments, verifiable device based service billing is provided by submitting requests to connect to an unauthorized service/website to verify if that unauthorized service usage is properly blocked. In some embodiments, verifiable device based service billing is provided by submitting requests to perform an unauthorized transaction to verify if that unauthorized transaction is properly blocked. - In some embodiments, verifiable device based service billing is provided by verifying device service activities relative to IPDRs for the device. In some embodiments, the IPDRs for the device (possibly in a modified format) are periodically and/or upon request sent to the device, as described herein. For example, IPDRs for the device can be compared to the device's local service data usage counter and/or to the service plan for the device to determine if the overall service data usage limit has been exceeded, whether out of plan/unauthorized/unrecorded websites/other services have been performed by the device, whether service plan/profile bandwidth limits have been exceeded, whether out of plan/unauthorized/unrecorded transactions have been performed (e.g., verifying IPDR transaction logs, assuming such are included in the IPDRs, with the local transaction logs of the device to determine, for example, whether the local device records indicate that fewer than the network recorded number of content downloads, such as downloaded songs, were purchased), and/or whether any other activities verifiable based on a comparison of IPDRs indicate that the device has been used in any manner that is out of or exceeds the service plan/profile for the device.
- In some embodiments, device based service billing includes recording billing option response history. For example, this approach can be particularly important for service plan overage conditions (e.g., when the use of the device is exceeding the service plan associated with the device in some manner, such as service data usage, bandwidth, service or transaction access and/or in some other manner). In some embodiments, in a service plan overage condition, the user is requested to confirm that user has acknowledged notification of service plan overage, such as via the
user interface 1697. In some embodiments, such service plan overage acknowledgements require that the user enter a unique identification to validate authorization by the user identity associated with the device (e.g., another type of verification mechanism, in the event a device is stolen or being used by someone other than the authorized user of the device, then that unauthorized user would not be able to confirm the service plan overage acknowledgement, and appropriate actions can then be taken, such as throttling, quarantining or (temporarily) suspending service/network access). In some embodiments, if the device is compromised/hacked (e.g., by the user of the device), and the device is used in a manner that results in a service usage overage (e.g., determined based on device assisted service usage monitoring, and/or network based service usage monitoring using IPDRs/CDRs), then the billing system determines billing for such service usage overage costs. This overage billing can be initiated by the device 100 (e.g., service processor 115), theservice controller 122, thebilling system 123, theAAA 121, or some other network function. In some embodiments, if the device is compromised/hacked (e.g., by a user of the device), and the device is used in a manner that results in a service usage overage, one or more of the following actions is taken: the user is notified, the user is required to acknowledge the notification, the device traffic is sent to SPAN (or similar traffic sampling and analysis function), and/or the device is flagged for further analysis. - In some embodiments, device based service billing includes an option to bill by account, such as to bill different service activities and/or transactions to a specified account (e.g., other than the user's account associated with the general service plan for the device). For example, bill by account can provide for billing according to application, content type, website, transaction, network chatter (e.g., heartbeat communications and/or other network traffic that is used by, for example, the central/service provider to generally maintain network access for the device), and/or transaction partner sponsored activities and then report such bill by account information for billing mediation/reconciliation. For example, a bill by account report can be sent by
billing agent 1695 from the device to central billing 1619 (e.g., as a billing event); or alternatively, sent to an intermediate server/aggregator, which can then reformat and send the reformatted report to central billing 1619 (e.g., providing the billing report in a format required by central billing 1619); or alternatively, sent to a mediation server, which can re-compute the billing based on the bill by account report (e.g., offset the bill based on network chatter, transaction based billing, transaction partner sponsored activities, content providers, website providers and/or advertising providers) and then send the recomputed (and potentially reformatted) report tocentral billing 1619. - In some embodiments, one or more of the mediation/reconciliation functions for device assisted billing, device generated billing events, device generated bill by account events and device generated open transaction billing events can be implemented in the service controller 122 (e.g., the billing event server 1662) or in another function located in the
billing system 123 or elsewhere. This billing mediation server function accepts the device based billing events discussed immediately above, reformats the billing events into a format accepted and recognized by the billing system, mediates the billing event information to remove service usage billing from the user account and place it in other bill by account categories as appropriate according to the bill by account mediation rules, adds other billing events for service usage or transactions to the user account as appropriate according to the device based billing rules, and then applies the information to the billing information the user account to correct or update the account. - For example, a bill by account can allow for a website provider, such as Google or Yahoo, to pay for or offset certain account usage for web browsing, web based searching, web based email, or any other web based or other service usage activities, which may also be based (in whole or in part) on the activities performed by the user on such transactional services (e.g., based on advertisement viewing/accessing or click-through activities by the user, by which an advertisement business model used by such website providers directly or indirectly supports such service account subsidies). As another example, a bill by account can allow for an advertiser to pay for or offset certain account usage for viewing and/or accessing (e.g., clicking through) a web placed advertisement or other advertisement sent via the network to the device. As yet another example, various network chatter (e.g., heartbeat related network and other network chatter related service data usage) can be assigned to a dummy account and such can be used to offset the bill and/or used for tracking the data usage for such activities for the device. In another example, service data usage for access to a transactional service, such as a multimedia content download service (e.g., music, eBook, music/video streaming, and/or movie or other multimedia content download service), or an online shopping site (e.g., Amazon, eBay or another online shopping site), can be billed to a transactional service account assigned to a transactional service partner that sponsors access to that sponsor's transactional service, thereby allowing that transactional service partner to pays for or offset (e.g., subsidize) the account usage for such activities, which may also be based (in whole or in part) on the transactions actually performed by the user on such transactional services (e.g., based on the volume/cost of the multimedia service download purchases by the user and/or online activities).
- In some embodiments, device based service billing includes recording billing events on the device and then reporting such billing to the network (e.g., central billing 1619). In some embodiments, device based service billing includes reporting service usage events and/or applying cost look-up and logging/reporting service billing updates. For example, this allows for reporting not only service usage but also cost of such service usage to the user via the user interface of device 101. Also, for example, the cost of such service usage can also be reported to the billing server. In some embodiments, device based service billing includes reporting service usage to the network, and the network determines the cost for such service usage.
- In some embodiments, billing information for roaming partners is provided. For example, a roaming server can include a roaming service cost data table for roaming service partners. In this example, when the device (e.g., device 101) connects to a roaming network provided by a roaming service partner, then the device can also receive the roaming service data rate based on the roaming service cost data table provided by the roaming server. Alternatively, the roaming server can send the roaming service cost data table (or a modified format of the same) to the device thereby allowing the device to determine the costs for such roaming network service usage or service activity. As described herein, the device can also automatically use a roaming service profile when connecting to the roaming network service and/or the user can be notified of the roaming service profile options based on the roaming service data costs and then select the desired roaming service profile accordingly.
- In some embodiments, the user is provided with a list of service costs based on locally stored roaming table and a search of available roaming partners that the
device 100 detects and can connect to. In some embodiments, the user is provided with a projected cost per day for one or more roaming service provider options based on typical service usage history and the cost for each service provider. In some embodiments, the user is provided with a set of options for service usage notification, controlling or throttling service usage and/or cost while roaming (e.g., using the service notification and cost control techniques as similarly discussed herein but applied to the roaming network). In some embodiments, these controls are set by a VSP (or, e.g., an IT manager using VSP functions). In some embodiments, roaming tables are updated periodically in the background while on a home network (or other low cost network) and cached. In some embodiments, cache updates occur based on fixed time period (e.g., late at night when updates are less expensive due to network inactivity). In some embodiments, the roaming partner cost table cache updates are done whenever connected to a desirable network that is not as expensive or bandwidth constrained (e.g., at home, work, or off the WWAN). In some embodiments, updates occur at time of day that network is not busy. In some embodiments, updates occur based on network push when roaming table is changed (e.g., one or more of the roaming partners changes the rate). In some embodiments, the service cost to update the roaming service cost table is charged to bill by account and possibly not charged to end user. In some embodiments, the roaming service center is provided as a service that is paid for (e.g., potentially bill by account tracks all related costs). For example, this type of roaming cost control can be provided as a service through central provider, MVNO, roaming partner provider, VSP or as a third party application not associated with any service provider (e.g., IT manager). For example, the controls for how to update cache, set service control policies, and other controls can be defined by any number of VSP entities including the user through a website service. - In some embodiments, a roaming service center is provided as a service in which, for example, the user is provided with a list of service costs based on a locally stored (or remotely accessed) roaming table. In some embodiments, the roaming service center provides the user with a projected cost per day for one or more roaming service provider options based on typical service usage history and the cost for each service provider. In some embodiments, the roaming service center provides the user with a set of options for controlling/throttling usage and/or cost while roaming. In some embodiments, these controls are set by a VSP (e.g., an IT manager using VSP functions). For example, roaming tables can be updated periodically in the background while on a home network and cached. In some embodiments, cache updates occur based on a fixed time period. In some embodiments, the roaming partner cost table cache updates are done whenever the device is connected to a desirable network that is not as expensive or bandwidth constrained (e.g., at home, work and/or off the WWAN). In some embodiments, updates occur at time of day that network is not busy. In some embodiments, updates occur based on a network push when a roaming table is changed (e.g., one or more of the roaming partners changes the rate). In some embodiments, the service cost to update the roaming service cost table is charged to bill by account and possibly not charged to the user. In some embodiments, the roaming service center is provided as a service that is paid for by the user and/or part of a service plan. In some embodiments, a bill by account function tracks all related costs. For example, the roaming service center can be provided as a service through central provider, MVNO, roaming partner provider, VSP or as a third party application not associated with any service provider (e.g., IT manager).
- In some embodiments, a synchronized local service usage counter based on time stamped central billing information is provided. For example, the local service usage counter, as similarly described above, can also be synchronized to past service usage records (e.g., time stamped central billing records of service usage for the device) and use local estimates for current/present service usage estimates for the device. In this example, the central billing system (e.g., central billing 1619) can push the time stamped central billing information to the device (e.g., device 101), the device can pull the time stamped central billing information, and/or an intermediate server can provide a mediated push or pull process. In some embodiments, synchronization is performing periodically based on service usage levels with free-running estimates between synchronizations.
- In some embodiments, service usage is projected based on calculated estimates of service usage based on synchronized service usage and local service usage count information. For example, projected service usage can be calculated on the device or calculated on a server (e.g., a billing server or an intermediate billing server), which provides the calculated projected service usage information to the device, such as using various adaptive algorithms for service usage projections. For example, an adaptive algorithm can use historical/past synchronized network service usage information (e.g., synchronized with local service usage data based on time stamps associated with IPDRs) to assist in service usage projections, based on, for example, total service usage count, service usage count by certain service related criteria (e.g., application, content, service type, website and/or time of day). In another example, an adaptive algorithm synchronizes to past service usage data (e.g., the local estimate of past service usage data is updated to be synchronized up through the point in time associated with the latest IPDR time stamp that has been received) and current local estimates of service usage collected since the latest time stamp are then added to the time stamped IPDR service usage counter to minimize the service usage counter offset so that it is no greater than the difference between the network service usage measure and the local service usage measure since the latest IPDR time stamp. In some embodiments, these adaptive algorithm techniques are performed on the device and/or performed on the network (e.g., on a network server) for processing. In some embodiments, if there is an offset in the local device based service usage count between IPDR synchronization events and the IPDR service usage count between IPDR synchronization events, then an algorithm can be employed to estimate any systematic sources for the offset and correct the local service usage count to minimize the offsets. As an example, if the IPDR service usage count is typically off by a fixed percentage, either high or low, then an algorithm can be employed to estimate a multiplier that is applied to the local service usage count to minimize the offset between IPDR service usage synchronization events. In another example, there can be a consistent constant offset and a multiplier offset, both of which can be estimated and corrected for. Those of ordinary skill in the art will appreciate that more sophisticated algorithms can be employed to estimate the nature of any systematic offsets, including, for example, offsets that occur due to specific service usage activities or network chatter to manage the device, and such offsets can then be minimized between IPDR service synchronization events. In some embodiments, synchronized service usage data is used to create an improved analysis of the statistical patterns of service usage to provide more accurate service usage projections. Those of ordinary skill in the art will also appreciate that a variety of additional adaptive algorithm techniques can be used including those that provide for various statistical analysis techniques and/or other techniques.
- In some embodiments, service usage is projected for the end of a billing/service period for a service plan versus the service usage allowed under the service plan for that billing/service period. A display of excess charges is also provided for the projected rate of service usage based on the monitored service usage behavior through the end of the billing/service period (e.g., this can be zero if the service usage is projected to be less than that allowed under the service plan and a positive cost number if it is projected to be more than the service plan). For example, this can be implemented in numerous ways, such as on a server in the network, on a gateway/router/switch in the network, and/or on the device, as discussed below and generally described herein with respect to other service/cost usage monitoring and notification embodiments. If implemented in the network server or gateway/router/switch, then the service/cost usage projections and related information can be pushed to the device, or the device can be notified that such information is available to pull and/or periodically pushed/pulled. The service usage information/estimates can be collected from the device, the network or both (e.g., reconciled and/or synchronized) as similarly described herein. The service usage information/estimates are then analyzed to determine service usage/cost projects as similarly described herein and compared to the service plan for the device to determine the projected service/cost usage overage (if any). In some embodiments, one or more of the following are determined by, reported to and/or displayed on the device: service usage value, projected service usage value, service usage plan limit, projected service usage overage, projected service cost overage, service plan period time duration, service plan time remaining before end of period and/or other pertinent information.
- In some embodiments, the device also determines service costs based on the synchronized service usage count thereby allowing the device to also report the service cost information to the user. For example, the device can locally store a service cost look-up table(s), locally store different service cost look-up tables for different networks and/or for roaming networks, and/or request such information from a billing or intermediate billing server (and/or a roaming server) on the network. As another example, the device can obtain the calculated service costs based on the synchronized local service usage count and/or network service usage count from an intermediate server (e.g., a billing or intermediate billing server) thereby offloading the computational costs associated with calculated these projections and the data storage for service cost lookup tables onto the intermediate server on the network using the network service usage counter with or, alternatively, without the synchronized local service usage counter.
- In some embodiments, service usage count categorization by network (e.g., a home network (such as a Wi-Fi, WAN, femtocell or other home network) versus a roaming network) is provided. Similarly, the synchronized local service usage counter can be synchronized by network. Also, a synchronized local service usage count for networks controlled by a central provider, for networks controlled by other providers (e.g., MVNO), and/or free networks can similarly be provided.
- In some embodiments, a service notification and billing interface is provided. For example, service usage and projected service usage, such as described herein, can be displayed to the user of the device (e.g., via user interface 1697). Similarly, expected/projected service or cost overrun/overage, such as described herein, can also be displayed to the user. As another example, a most cost effective plan can be determined/projected based on historical and/or projected service usage, and this determined/projected most cost effective plan can be displayed to the user. In yet another example, a list of available networks accessible by the device can be displayed to the user. In this example, one or more undesired available networks can also be blocked from display thereby only displaying to the user desired and/or preferred available networks. In this example, service usage plans and/or service usage plan option comparison for one or more alternative networks or roaming networks can also be displayed to the user. Similarly, service cost plans and/or service/cost plan option comparison for one or more alternative networks or roaming networks can also be displayed to the user. In addition, roaming service usage, projected roaming service usage, estimated roaming service cost, and/or projected estimated roaming service cost can also be displayed to the user. These roaming service usage/costs can also be displayed to the user so that the user can utilize this information for selecting various roaming service billing options. In another example, alternative and/or least cost networks are determined and displayed to the user. In another example, alternative warnings are displayed to the user for any or specified roaming networks.
- In some embodiments, the service notification and billing interface notifies the user of expected network coverage (e.g., based on the device's current geography/location and the accessible networks for the device from that current geography/location) and displays options to the user based on the expected network coverage information. In some embodiments, the service notification and billing interface notifies the user of their current service usage at specified service usage points and displays various options to the user (e.g., service usage options and/or billing options). For example, the user's responses to the presented options are recorded (e.g., stored locally on the device at least temporarily for reporting purposes or permanently in a local configuration data store until such configuration settings are otherwise modified or reset) and reported, such as to the billing server (e.g., central billing 1619). For example, user input, such as selected options and/or corresponding policy settings, can be stored locally on the device via a cache system. As another example, the service notification and billing interface displays options to the user for how the user wants to be notified and how the user wants to control service usage costs, the user's input on such notification options is recorded, and the cost control options (e.g., and the
billing agent 1695 and policy control agent 1692) are configured accordingly. Similarly, the user's input on service plan options/changes can be recorded, and the service plan options/changes (e.g., and thebilling agent 1695 and policy control agent 1692) are configured/updated accordingly. In another example, the service notification and billing interface provides various traffic control profiles, such as for where the user requests assistance in controlling service usage costs (e.g., service data usage and/or transactional usage related activities/costs). Similarly, the service notification and billing interface can provide various notification options, such as for where the user wants advance warning on service coverage. In another example, the service notification and billing interface provides options for automatic pre-buy at a set point in service usage. In another example, the service notification and billing interface provides the option to choose different notification and cost control options for alternative networks or roaming networks. - In some embodiments, an online portal or web server is provided for allowing the user to select and/or update policy settings. For example, user input provided via the online portal/web server can be recorded and reported to the billing server (e.g., central billing 1619). In another example, the online portal/web server can display transaction billing information and/or accept input for a transaction billing request, which can then be reported to the billing server accordingly.
- As shown in
FIG. 16 , theservice processor 115 includes a service interface oruser interface 1697. In some embodiments, theuser interface 1697 provides the user with information and accepts user choices or preferences on one or more of the following: user service information, user billing information, service activation, service plan selection or change, service usage or service activity counters, remaining service status, service usage projections, service usage overage possibility warnings, service cost status, service cost projections, service usage control policy options, privacy/CRM/GPS related options, and/or other service related information, settings, and/or options. For example, theuser interface 1697 can collect service usage information fromservice monitor agent 1696 to update the local service usage counter (and/or, alternatively, the service usage information is obtained from the service controller 122) to update user interface service usage or service cost information for display to the user. As another example, service billing records obtained fromcentral billing system 1619 can be used to synchronize local service usage counters andservice monitor agent 1696 information to perform real-time updating of local service usage counters betweenbilling system 1619 synchronizations. As another example, theuser interface 1697 can display options and accept user preference feedback, such as similarly discussed above with respect to user privacy/CRM/GPS filtering, traffic monitoring and service controls. For example, theuser interface 1697 can allow the user of the device to modify their privacy settings, provide user feedback on service preferences and/or service experiences, modify their service profiles (e.g., preferences, settings, configurations, and/or network settings and options), to review service usage data (e.g., based on local service usage counters and/or other data monitored by the service processor 115), to receive various events or triggers (e.g., based on projected service usage/costs), and/or theuser interface 1697 can provide/support various other user input/output for service control and service usage. - In some embodiments, by providing the service policy implementation and the control of service policy implementation to the preferences of the user, and/or by providing the user with the option of specifying or influencing how the various service notification and control policies or control algorithms are implemented, the user is provided with options for how to control the service experience, the service cost, the capabilities of the service, the manner in which the user is notified regarding service usage or service cost, the level of sensitive user information that is shared with the network or service provider entity, and the manner in which certain service usage activities may or may not be throttled, accelerated, blocked, enabled and/or otherwise controlled. Accordingly, some embodiments provide the service control to beneficially optimize user cost versus service capabilities or capacities in a manner that facilitates an optimized user experience and does not violate network neutrality goals, regulations and/or requirements. For example, by offering the user with a set of choices, ranging from simple choices between two or more pre-packaged service control settings options to advanced user screens where more detailed level of user specification and control is made available, some embodiments allow the service provider, device manufacturer, device distributor, MVNO, VSP, service provider partner, and/or other “entity” to implement valuable or necessary service controls while allowing the user to decide or influence the decision on which service usage activities are controlled, such as how they are controlled or throttled and which service usage activities may not be throttled or controlled in some manner. These various embodiments allow the service provider, device manufacturer, device distributor, MVNO, VSP, service provider partner, or other “entity” to assist the user in managing services in a manner that is network neutral with respect to their implementation and service control policies, because the user is making or influencing the decisions, for example, on cost versus service capabilities or quality. By further providing user control or influence on the filtering settings for the service usage reporting or CRM reporting, various levels of service usage and other user information associated with device usage can be transmitted to the network, service provider, device manufacturer, device distributor, MVNO, VSP, service provider partner, and/or other “entity” in a manner specified or influenced by the user to maintain the user's desired level of information privacy.
- As shown in
FIG. 16 , theservice processor 115 includes theservice downloader 1663. In some embodiments, theservice downloader 1663 provides a download function to install or update service software elements on the device. In some embodiments, theservice downloader 1663 requires a secure signed version of software before a download is accepted. For example, the download can require a unique key for aparticular service downloader 1663. As another example, theservice downloader 1663 can be stored or execute in secure memory or execute a secure memory partition in the CPU memory space. Those of ordinary skill in the art will appreciate that there are a variety of other security techniques that can be used to ensure the integrity of theservice downloader 1663. - As shown in
FIG. 16 , theservice processor 115 includes amodem driver 1640. In some embodiments, themodem driver 1640 converts data traffic into modem bus (not shown) traffic for one or more modems via themodem firewall 1655. As shown inFIG. 18 , in some embodiments, modem selection andcontrol 1811 selects the access network connection and is in communication with themodem firewall 1655, andmodem drivers control 1811. As shown inFIG. 21 , in some embodiments,modems modem bus 2120, connect the device to one or more networks. In some embodiments, different profiles are selected based on the selected network connection (e.g., different service profiles/policies for WWAN, WLAN, WPAN, Ethernet and/or DSL network connections), which is also referred to herein as multimode profile setting. For example, service profile settings can be based on the actual access network (e.g., home DSL/cable or work network) behind the Wi-Fi not the fact that it is Wi-Fi (or any other network, such as DSL/cable, satellite, or T-1), which is viewed as different than accessing a Wi-Fi network at the coffee shop. For example, in a Wi-Fi hotspot situation in which there are a significant number of users on a DSL or T-1 backhaul, the service controller can sit in a service provider cloud or an MVNO cloud, the service controls can be provided by a VSP capability offered by the service provider (e.g., as described herein with respect to.FIG. 49 ) or the service controller can be owned by the hotspot service provider that uses the service controller on their own without any association with an access network service provider. For example, the service processors can be controlled by the service controller to divide up the available bandwidth at the hotspot according to QoS or user sharing rules (e.g., with some users having higher differentiated priority (potentially for higher service payments) than other users). As another example, ambient services (as similarly described herein) can be provided for the hotspot for verified service processors. - In some embodiments, the
service processor 115 andservice controller 122 are capable of assigning multiple service profiles associated with multiple service plans that the user chooses individually or in combination as a package. For example, adevice 100 starts with ambient services that include free transaction services wherein the user pays for transactions or events rather than the basic service (e.g., a news service, eReader, PND service, pay as you go session Internet) in which each service is supported with a bill by account capability to correctly account for any subsidized partner billing to provide the transaction services (e.g., Barnes and Noble may pay for the eReader service and offer a revenue share to the service provider for any book or magazine transactions purchased form the device 100). In some embodiments, the bill by account service can also track the transactions and, in some embodiments, advertisements for the purpose of revenue sharing, all using the service monitoring capabilities disclosed herein. After initiating services with the free ambient service discussed above, the user may later choose a post-pay monthly Internet, email and SMS service. In this case, theservice controller 122 would obtain from thebilling system 123 in the case of network based billing (or in some embodiments theservice controller 122 billing event server 1622 in the case of device based billing) the billing plan code for the new Internet, email and SMS service. In some embodiments, this code is cross referenced in a database (e.g., the policy management server 1652) to find the appropriate service profile for the new service in combination with the initial ambient service. The new superset service profile is then applied so that the user maintains free access to the ambient services, and the billing partners continue to subsidize those services, the user also gets access to Internet services and may choose the service control profile (e.g., from one of the embodiments disclosed herein). The superset profile is the profile that provides the combined capabilities of two or more service profiles when the profiles are applied to thesame device 100 service processor. In some embodiments, the device 100 (service processor 115) can determine the superset profile rather than theservice controller 122 when more than one “stackable” service is selected by the user or otherwise applied to the device. The flexibility of theservice processor 115 andservice controller 122 embodiments described herein allow for a large variety of service profiles to be defined and applied individually or as a superset to achieve the desireddevice 100 service features. - As shown in
FIG. 16 , theservice controller 122 includes a servicecontrol server link 1638. In some embodiments, device based service control techniques involving supervision across a network (e.g., on the control plane) are more sophisticated, and for such it is increasingly important to have an efficient and flexible control plane communication link between the device agents (e.g., of the service processor 115) and the network elements (e.g., of the service controller 122) communicating with, controlling, monitoring, or verifying service policy. For example, the communication link between the servicecontrol server link 1638 ofservice controller 122 and the servicecontrol device link 1691 of theservice processor 115 can provide an efficient and flexible control plane communication link, aservice control link 1653 as shown inFIG. 16 , and, in some embodiments, this control plane communication link provides for a secure (e.g., encrypted) communications link for providing secure, bidirectional communications between theservice processor 115 and theservice controller 122. In some embodiments, the servicecontrol server link 1638 provides the network side of a system for transmission and reception of service agent to/from network element functions. In some embodiments, the traffic efficiency of this link is enhanced by buffering and framing multiple agent messages in the transmissions (e.g., thereby reducing network chatter). In some embodiments, the traffic efficiency is further improved by controlling the transmission frequency and/or linking the transmission frequency to the rate of service usage or traffic usage. In some embodiments, one or more levels of security and/or encryption are used to secure the link against potential discovery, eavesdropping or compromise of communications on the link. In some embodiments, the servicecontrol server link 1638 also provides the communications link and heartbeat timing for the agent heartbeat function. As discussed below, various embodiments described herein for the servicecontrol server link 1638 provide an efficient and secure mechanism for transmitting and receiving service policy implementation, control, monitoring and verification information between the device agents (e.g., service processor agents/components) and other network elements (e.g., service controller agents/components). - In some embodiments, the service
control server link 1638 can employ the counterpart service control plane secure transmission methods discussed above with respect to the servicecontrol device link 1691. For example, one or more layers of security can be used to secure the communications link, including, for example, basic IP layer security, TCP layer security, service control link layer security, and/or security specific from service controller servers to service processor agents. - In some embodiments, the service
control server link 1638 reduces network chatter by efficiently transmitting service control related communications over the link. For example, the servicecontrol server link 1638 can transmit server messages asynchronously as they arrive. As another example, the servicecontrol server link 1638 can perform collection or buffering of server messages between transmissions. As another example, the servicecontrol server link 1638 can determine when to transmit based potentially on several parameters, such as one or more of: periodic timer trigger, waiting until a certain amount of service usage or traffic usage has occurred, responding to a service agent message, responding to a service agent request, initiated by one or more servers, initiated by a verification error condition, and/or initiated by some other error condition. For example, once a transmission trigger has occurred, the servicecontrol server link 1638 can take all buffered agent communications and frame the communications. In addition, the servicecontrol server link 1638 can provide for an efficient communication link based on various embodiments related to the timing of transmissions over the service control link, as similarly discussed above with respect to the servicecontrol device link 1691 description. For example, the timing functions, such as asynchronous messages or polling for messages, constant frequency transmission, transmission based on how much service usage or data traffic usage has taken place, transmission in response to device side control link message, service verification error events, other error events, and/or other message transmission trigger criteria can be determined, controlled and/or initiated by either the device side or the network side depending on the embodiment. - In some embodiments, the service
control server link 1638 provides for securing, signing, encrypting and/or otherwise protecting the communications before sending such communications over theservice control link 1653. For example, the servicecontrol server link 1638 can send to the transport layer or directly to the link layer for transmission. In another example, the servicecontrol server link 1638 further secures the communications with transport layer encryption, such as TCP TLS or another secure transport layer protocol. As another example, the servicecontrol server link 1638 can encrypt at the link layer, such as using IPSEC, various possible VPN services, other forms of IP layer encryption and/or another link layer encryption technique. - In some embodiments, the service
control server link 1638 includes the agent heartbeat function in which the agents provide certain required reports to the service processor for the purpose of service policy implementation verification or for other purposes. For example, the heartbeat function can also be used to issue queries or challenges, messages, service settings, service control objectives, information requests or polling, error checks and/or other communications to the agents. As another example, agent heartbeat messages can be in the open or encrypted, signed and/or otherwise secured. Additional heartbeat function and the content of heartbeat messages can be provided as similarly described herein, such as described above with respect to the servicecontrol device link 1691 and the accesscontrol integrity agent 1694 and other sections. In some embodiments, theservice controller 122 and/or agents of theservice controller 122 are programmed to periodically provide reports, such as upon a heartbeat response (e.g., an agent can repeatedly send necessary reports each heartbeat), and appropriate actions can then be taken based upon such received reports. Accordingly, the heartbeat function provides an important and efficient system in various embodiments described herein for verifying the service policy implementation and/or protecting against compromise events. There are many other functions the agent heartbeat service can perform many of which are discussed herein, while many others will be apparent to one of ordinary skill in the art given the principles, design background and various embodiments provided herein. - In some embodiments, the service
control server link 1638 also provides a service control software download function for various embodiments, which, for example, can include a download of new service software elements, revisions of service software elements, and/or dynamic refreshes of service software elements of theservice processor 115 on the device. In some embodiments, this function is performed by the servicecontrol server link 1638 transmitting the service control software as a single file over the service control link. For example, the file can have encryption or signed encryption beyond any provided by the communication link protocol itself forservice control link 1653. In another example, the service control software files can be segmented/divided into smaller packets that are transmitted in multiple messages sent over theservice control link 1653. In yet another example, the service control software files can be transmitted using other delivery mechanism, such as a direct TCP socket connection from a servicedownload control server 1660, which can also involve secure transport and additional levels of encryption. In some embodiments, the servicecontrol server link 1638 and/or servicedownload control server 1660 use(s) an agent serial number and/or a security key look up when agents are updated and/or when a dynamic agent download occurs. - As shown in
FIG. 16 , theservice controller 122 includes an accesscontrol integrity server 1654. In some embodiments, the accesscontrol integrity server 1654 collects device information on service policy, service usage, agent configuration and/or agent behavior. For example, the accesscontrol integrity server 1654 can cross check this information to identify integrity breaches in the service policy implementation and control system. In another example, the accesscontrol integrity server 1654 can initiate action when a service policy violation or a system integrity breach is suspected. - In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) acts on access control integrity agent reports and error conditions. Many of the access
control integrity agent 1654 checks can be accomplished by the server. For example, the accesscontrol integrity agent 1654 checks include one or more of the following: service usage measure against usage range consistent with policies (e.g., usage measure from the network and/or from the device); configuration of agents; operation of the agents; and/or dynamic agent download. - In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy implementations by comparing various service usage measures (e.g., based on network monitored information, such as by using IPDRs, and/or local service usage monitoring information) against expected service usage behavior given the policies that are intended to be in place. For example, device service policy implementations can include measuring total data passed, data passed in a period of time, IP addresses, data per IP address, and/or other measures such as location, downloads, email accessed, URLs, and comparing such measures expected service usage behavior given the policies that are intended to be in place.
- In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy, and the verification error conditions that can indicate a mismatch in service measure and service policy include one or more of the following: unauthorized network access (e.g., access beyond ambient service policy limits); unauthorized network speed (e.g., average speed beyond service policy limit); network data amount does not match policy limit (e.g., device not stop at limit without re-up/revising service policy); unauthorized network address; unauthorized service usage (e.g., VOIP, email, and/or web browsing); unauthorized application usage (e.g., email, VOIP, email, and/or web); service usage rate too high for plan, and policy controller not controlling/throttling it down; and/or any other mismatch in service measure and service policy.
- In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy based at least in part on, for example, various error conditions that indicate a mismatch in service measure and service policy. For example, various verification error conditions that can indicate a mismatch in service measure and service policy include one or more of the following: mismatch in one service measure and another service measure; agent failure to report in; agent failure to respond to queries (e.g., challenge-response sequence and/or expected periodic agent reporting); agent failure to respond correctly to challenge/response sequence; agent improperly configured; agent failure in self checks; agent failure in cross-checks; unauthorized agent communication or attempted unauthorized communication; failure in service policy implementation test; failure in service usage reporting test; failure in service usage billing test; failure in transaction billing test; failure in download sequence; environment compromise event, such as unauthorized software load or execution (or attempt), unauthorized memory access (or attempt), unauthorized agent access (or attempt), known harmful software, and/or known harmful communications signature; and/or failure to respond to various messages, such as send message and suspend and/or send message and quarantine. In some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) verifies device service policy by performing automated queries and analysis, which are then reported (e.g., anomalous/suspicious report results can be reported for further analysis by a person responsible for determining whether such activities indicate out of policy activities or to provide information to the user to inform the user of such anomalous/suspicious report results that may indicate out of policy activities). For example, the user can review the report to authorize whether such activities were performed by the user (e.g., website access requests, specific transactions, and/or phone calls) and/or indicate that such activities were not authorized by the user (e.g., indicate a potential compromise of the device, such as by malware or other unauthorized software/user use of the device). In another example, the user can also be connected to communicate with service support of the service provider regarding such reported activities (e.g., by text/chat, voice/phone, and/or video conference to a service support). Accordingly, in some embodiments, the access control integrity server 1654 (and/or some other agent of service controller 122) provides a policy/service control integrity service to continually (e.g., periodically and/or based on trigger events) verify that the service control of the device has not been compromised and/or is not behaving out of policy.
- In some embodiments, upon detection of one or more service verification errors, such as the various service verification errors discussed above, the device is directed to a quarantine network status in which the device can, for example, only access network control plane functions, billing functions, and other functions generally controlled by the access network service provider or the central service provider. For example, quarantine network access restrictions and routing can be accomplished with the access network AAA and routing system (e.g., access
network AAA server 1621 and one or more of thegateways - In some embodiments, upon detection of one or more service verification errors, such as the various service verification errors discussed above, switch based port analysis is performed to further monitor the device (e.g., referred to as Switched Port Analyzer (SPAN) on Cisco switches, and various other vendors have different names for it, such as Roving Analysis Port (RAP) on 3Com switches). In some embodiments, the device service policy implementation behavior is monitored at a deeper level in the network by copying device traffic in the switch so that it goes to both an intended data path destination and to a specified port for switch based port analysis (e.g., the traffic content can be analyzed and recorded using deep packet inspection (DPI) techniques, which can provide a finer level of detail than the typical IPDR). For example, an advantage of performing a switch based port analysis function is that the traffic need not be analyzed in real time, and a sample subset of the devices on the network can be selected for such analysis based on, for example, either identifying devices that have suspect service policy implementation behavior and/or a regular sampling algorithm that eventually samples all devices, or some other selection approaches. As another example, a scheduled switch based port analysis sampling can be applied that eventually rotates through all devices and designates a higher priority in the sampling queue for devices that are suspect.
- In some embodiments, switch based port analysis allows for off-line sampled or non-real-time DPI, as described above, as a verification measure for the device based service control measures that are implemented. In some embodiments, sophisticated DPI techniques are used to enhance the content of the IPDRs so that they provide detailed information that can be made available in the network. For example, some of the DPI packet analysis may be redundant between the device and the network, but this approach provides for a much finer grain validation for the device based service and less reliance on the device for some of the service traffic analysis that service providers need. In some embodiments, the device control server functions and the service control policy verification functions are implemented in an integrated hardware/software system (e.g., a gateway, server, router, switch, base station, base station aggregator, AAA server cluster or any other hardware or hardware/software system) located in the network that the network level traffic inspection is accomplished in, or in one or more servers integrated to operate in a coordinated manner with the DPI boxes. In some embodiments, the device control server functions and the service control policy verification functions are implemented in an integrated hardware/software system (e.g., a gateway, server, router, switch, base station, base station aggregator, AAA server cluster or any other hardware or hardware/software system) located in the network that provides deep service control capability (e.g., using DPI techniques) for devices that have some or all of the service processor functions installed and, in some embodiments, also providing coarser network control of the basics for devices that do not have a service processor installed in the device (e.g., such coarser network control functions include max data rate and/or max total data).
- In some embodiments, the SPAN function is used in a revolving periodic manner as well to augment CDR data with deeper packet information for the purpose of spot-checking device based service usage measures. Examples of where this can be beneficial include spot checking network address access policies, spot checking ambient access policies, spot checking billing event reports, spot checking intermediate networking device/end point device count (via checking network source or destination addresses, token, cookies or other credentials, etc). For example, the periodic SPAN can be scheduled for all devices equally, for certain devices or users with higher priority, frequency or depth of SPAN than others, higher priority, higher frequency or immediate priority for devices with higher usage patterns or unusual usage patterns, immediate or very high priority for devices with a policy violation status.
- In some embodiments, a combination traffic inspection and service control approach implements traffic and service control functions in the network that are conducive for a network based implementation and implements traffic and service control functions in the device that are either more conducive for performing in the device or can only be performed in the device (e.g., activities involving inspection of traffic that is encrypted once it is transmitted to the network). For example, using this approach, activities that can be done in the network are generally performed in the network and/or are more efficiently performed in the network than the device, and activities that are more efficiently performed in the device or can only be performed in the device are performed in the device (e.g., depending on device processing/storage capabilities and/or other design/security considerations). For example, the following are various traffic and service control functions that, in some embodiments, are preferably or can only be performed in the device: network based packet processing capability limitations (e.g., encrypted traffic, application layer information unavailable once the traffic goes into the networking stack, other application/usage context information available on the device but not in the network); information that is generally/preferably maintained and processed locally in the device for network neutrality reasons (e.g., network neutrality issues can generally be efficiently implemented by keeping all, substantially all or at least some aspect of decisions on how to implement algorithms to control traffic local to the device and under user decision control, and/or by providing the user with a set of pre-packaged choices on how to manage service usage or service activity usage or manage service usage versus service cost or price); information that is generally/preferably maintained and processed locally in the device for user privacy reasons (e.g., deeper levels of traffic monitoring and service usage monitoring data where it is available for assisting the user in achieving the best, lowest cost experience and implementing a CRM filter function to the user so that the user can control the level of CRM the network is allowed to receive, such as with the higher levels of information being exchanged for something of value to the user, and/or user location information); information that is generally/preferably maintained and processed locally in the device for the purpose of informing the user of service control settings or service activity usage or to adjust service activity control settings or receive user feedback to choices regarding service usage policies or billing options (e.g., providing the user with a UI for the purpose of monitoring an estimate of service usage and/or notifying the user of at least some aspect of estimated service usage or projected service usage, providing the user with a UI for the purpose of monitoring an estimate of service cost and/or notifying the user of at least some aspect of estimated service cost or projected service cost, providing the user with a UI for the purpose of providing the user with one or more service usage and/or service cost notification messages that require user acknowledgement and/or a user decision and obtaining or reporting the user acknowledgements and/or decisions, providing the user with a UI for the purpose of providing the user with service options and/or service payment options, providing the user with a UI for the purpose of obtaining user choice for such options when service usage or cost estimates are about to run over limits or have run over limits or are projected to run over limits, providing the user with a UI for the purpose of monitoring or conducting open central billing transactions or other transactions, providing the user with a UI for the purpose of selecting the service control techniques and/or policies and/or algorithms and/or pre-packaged configurations that can be used to define or partially define the service activity usage control policies implemented in the device service processor or the network service control equipment/billing system or a combination of both); service control for roaming on different networks that typically do not have compatible DPI-type techniques with the home network; certain service notification and traffic control algorithms (e.g., stack-ranked activity statistical analysis and control of only the high usage activities); and/or a function for assigning a device to a service experience or ambient activation experience or virtual service provider (VSP) at various times from manufacturing to device distribution to a user of the device. In some embodiments, certain activities are implemented in the device as a solution for networks in which a new centralized DPI approach is not possible, not economically feasible, or for any number of reasons not an option or not a preferred option.
- In some embodiments, a network based solution is provided for a more basic set of services for all devices that do not have service control capabilities, and a super-set of services and/or additional services are provided for devices that include a service processor. As described herein, a service controller function can be located in various places in the network in accordance with various embodiments. It should also be noted that various other embodiments described herein also employ a hybrid service control function performing certain service control functions in the network (e.g., collecting network service usage information, such as IPDRs, and/or performing DPI related functions in the network for collecting network service usage information and/or throttling/shaping traffic) and service control functions in the device (e.g.,
service processor 115, which, for example, monitors service usage in the device and/or performs throttling or traffic shaping in the device and/or performs certain billing event recording and reporting functions that are aptly performed on the device). - In some embodiments, lower level service policy implementation embodiments are combined with a higher level set of service policy supervision functions to provide device assisted verifiable network access control, authentication and authorization services.
- In some embodiments, device based access control services are extended and combined with other policy design techniques to create a simplified device activation process and connected user experience referred to herein as ambient activation. As similarly discussed above, ambient activation can be provided by setting access control to a fixed destination, verifying access with IPDRs, verifying access by setting a max data rate and triggering off in the network if it exceeds the max data rate, and/or by various other techniques.
- As shown in
FIG. 16 ,service controller 122 includes aservice history server 1650. In some embodiments, theservice history server 1650 collects and records service usage or service activity reports from the AccessNetwork AAA Server 1621 and theService Monitor Agent 1696. For example, although service usage history from the network elements can in certain embodiments be less detailed than service history from the device, the service history from the network can provide a valuable source for verification of device service policy implementation, because, for example, it is extremely difficult for a device error or compromise event on the device to compromise the network based equipment and software. For example, service history reports from the device can include various service tracking information, as similarly described above. In some embodiments, theservice history server 1650 provides the service history on request to other servers and/or one or more agents. In some embodiments, theservice history server 1650 provides the service usage history to thedevice service history 1618. In some embodiments, for purposes of facilitating the activation tracking service functions (described below), theservice history server 1650 maintains a history of which networks the device has connected to. For example, this network activity summary can include a summary of the networks accessed, activity versus time per connection, and/or traffic versus time per connection. As another example, this activity summary can further be analyzed or reported to estimate the type of service plan associated with the traffic activity for the purpose of bill sharing reconciliation. - As shown in
FIG. 16 ,service controller 122 includes apolicy management server 1652. In some embodiments, thepolicy management server 1652 transmits policies to theservice processor 115 via theservice control link 1653. In some embodiments, thepolicy management server 1652 manages policy settings on the device (e.g., various policy settings as described herein with respect to various embodiments) in accordance with a device service profile. In some embodiments, thepolicy management server 1652 sets instantaneous policies on policy implementation agents (e.g., policy implementation agent 1690). For example, thepolicy management server 1652 can issue policy settings, monitor service usage and, if necessary, modify policy settings. For example, in the case of a user who prefers for the network to manage their service usage costs, or in the case of any adaptive policy management needs, thepolicy management server 1652 can maintain a relatively high frequency of communication with the device to collect traffic and/or service measures and issue new policy settings. In this example, device monitored service measures and any user service policy preference changes are reported, periodically and/or based on various triggers/events/requests, to thepolicy management server 1652. In this example, user privacy settings generally require secure communication with the network (e.g., a secure service control link 1653), such as with thepolicy management server 1652, to ensure that various aspects of user privacy are properly maintained during such configuration requests/policy settings transmitted over the network. For example, information can be compartmentalized to service policy management and not communicated to other databases used for CRM for maintaining user privacy. - In some embodiments, the
policy management server 1652 provides adaptive policy management on the device. For example, thepolicy management server 1652 can issue policy settings and objectives and rely on the device based policy management (e.g., service processor 115) for some or all of the policy adaptation. This approach can require less interaction with the device thereby reducing network chatter onservice control link 1653 for purposes of device policy management (e.g., network chatter is reduced relative to various server/network based policy management approaches described above). This approach can also provide robust user privacy embodiments by allowing the user to configure the device policy for user privacy preferences/settings so that, for example, sensitive information (e.g., geo-location data, website history) is not communicated to the network without the user's approval. In some embodiments, thepolicy management server 1652 adjusts service policy based on time of day. In some embodiments, thepolicy management server 1652 receives, requests or otherwise obtains a measure of network availability and adjusts traffic shaping policy and/or other policy settings based on available network capacity. - In some embodiments, the
policy management server 1652 performs a service control algorithm to assist in managing overall network capacity or application QoS. In some embodiments, thepolicy management server 1652 performs an algorithm to determine which access network is best to connect to, such as based on network capacity or application QoS, service usage costs, and/or any other criteria. In some embodiments, the device is capable of connecting to more than one network, and accordingly, device service policies can be selected/modified based on which network the device is connected to. In some embodiments, the network control plane servers detect a network connection change from a first network to a second network and initiate the service policy implementation established for the second network. In other embodiments, the device based adaptive policy control agent (e.g.,policy control agent 1692 described herein) detects network connection changes from the first network to the second network and implements the service policies established for the second network. - In some embodiments, when more than one access network is available, the network is chosen based on which network is most preferred according to a network preference list or according to the network that optimizes a network cost function. For example, the preference list can be pre-established by the service provide and/or the user. For example, the network cost function can be based on a minimum service cost, maximum network performance, determining whether or not the user or device has access to the network, maximizing service provider connection benefit, reducing connections to alternative paid service providers, and/or a variety of other network preference criteria. In other embodiments, the device detects when one or more preferred networks are not available, implements a network selection function or intercepts other network selection functions, and offers a connection to the available service network that is highest on a preference list. For example, the preference list can be set by the service provider, the user and/or the service subscriber.
- As shown in
FIG. 16 ,service controller 122 includes a networktraffic analysis server 1656. In some embodiments, the networktraffic analysis server 1656 collects/receives service usage history for devices and/or groups of devices and analyzes the service usage. In some embodiments, the networktraffic analysis server 1656 presents service usage statistics in various formats to identify improvements in network service quality and/or service profitability. In other embodiments, the networktraffic analysis server 1656 estimates the service quality and/or service usage for the network under variable settings on potential service policy. In other embodiments, the networktraffic analysis server 1656 identifies actual or potential service behaviors by one or more devices that are causing problems for overall network service quality or service cost. - As shown in
FIG. 16 ,service controller 122 includes abeta test server 1658. In some embodiments, thebeta test server 1658 publishes candidate service plan policy settings to one or more devices. In some embodiments, thebeta test server 1658 provides summary reports of network service usage or user feedback information for one or more candidate service plan policy settings. In some embodiments, thebeta test server 1658 provides a mechanism to compare the beta test results for different candidate service plan policy settings or select the optimum candidates for further policy settings optimization. - As shown in
FIG. 16 ,service controller 122 includes a servicedownload control server 1660. In some embodiments, the servicedownload control server 1660 provides a download function to install and/or update service software elements (e.g., theservice processor 115 and/or agents/components of the service processor 115) on the device, as described herein. - As shown in
FIG. 16 ,service controller 122 includes abilling event server 1662. In some embodiments, thebilling event server 1662 collects billing events, provides service plan information to theservice processor 115, provides service usage updates to theservice processor 115, serves as interface between device andcentral billing server 1619, and/or provides trusted third party function for certain ecommerce billing transactions. - As shown in
FIG. 16 , the AccessNetwork AAA server 1621 is in network communication with theaccess network 1610. In some embodiments, the AccessNetwork AAA server 1621 provides the necessary access network AAA services (e.g., access control and authorization functions for the device access layer) to allow the devices onto the central provider access network and the service provider network. In some embodiments, another layer of access control is required for the device to gain access to other networks, such as the Internet, a corporate network and/or a machine to machine network. This additional layer of access control can be implemented, for example, by theservice processor 115 on the device. In some embodiments, the AccessNetwork AAA server 1621 also provides the ability to suspend service for a device and resume service for a device based on communications received from theservice controller 122. In some embodiments, the AccessNetwork AAA server 1621 also provides the ability to direct routing for device traffic to a quarantine network or to restrict or limit network access when a device quarantine condition is invoked. In some embodiments, the AccessNetwork AAA server 1621 also records and reports device network service usage (e.g., device network service usage can be reported to device service history 1618). - As shown in
FIG. 16 , thedevice service history 1618 is in network communication with theaccess network 1610. In some embodiments, thedevice service history 1618 provides service usage data records used for various purposes in various embodiments. In some embodiments, thedevice service history 1618 is used to assist in verifying service policy implementation. In some embodiments, thedevice service history 1618 is used to verify service monitoring. In some embodiments, thedevice service history 1618 is used to verify billing records and/or billing policy implementation. In some embodiments, thedevice service history 1618 is used to synchronize and/or verify the local service usage counter. - As shown in
FIG. 16 , the centralprovider billing server 1619 is in network communication with theaccess network 1610. In some embodiments, the centralprovider billing server 1619 provides a mediation function for central provider billing events. For example, the centralprovider billing server 1619 can accept service plan changes. In some embodiments, the centralprovider billing server 1619 provides updates on device service usage, service plan limits and/or service policies. In some embodiments, the centralprovider billing server 1619 collects billing events, formulates bills, bills service users, provides certain billing event data and service plan information to theservice controller 122 and/ordevice 100. - Establishing Coordinated Service and Verification Policies for Service Processor, Service Controller and Network Functions
- In some embodiments, device and network apparatus coordinate one or more of the following: network service policy implementation settings, device service policy implementation settings, network service profile implementation settings, device service profile implementation settings, network service usage measures used for the purpose of verifying service policy implementation, device service usage measures used for the purpose of verifying service policy implementation, network actions taken upon detection of service usage policy violation and device actions taken upon detection of service usage policy violation. In some embodiments, local device settings for the service monitoring, usage and/or billing profile or policy settings used, for example, by a
device service processor 115, are associated with corresponding records for the various network apparatus that also rely upon the service policy and profile settings to monitor, control and/or bill for services or to respond to out of policy service usage conditions. For example, such network apparatus include theservice controller 122 or similar functions, thebilling system 123 or similar functions, thenetwork AAA 121,gateways device service processor 115 and the network apparatus, but does not require an explicit function that simultaneously controls/coordinates the service policy or profile implementation and/or verification actions taken by the device 100 (e.g., the service processor 115) and the network apparatus. As an example, such embodiments can be applied in overlay applications as discussed below. - In some embodiments, a network function (e.g., the
service controller 122, and/or more specifically thepolicy management server 1652 function, or other similar function) obtain, derive or otherwise determine the association of the service profile or policy settings to program adevice service processor 115 and the various network apparatus functions (e.g., possibly including but not limited to theservice controller 122 or similar functions, thebilling system 123 or similar functions, thenetwork AAA 121,gateways billing system 123 service plan can be either directly mapped to usage limit settings on the device service processor 115 (e.g., service usage stops when the limit is hit or the user is notified or the user is billed), or the usage limits can be mapped to a number of service profiles the user may select from (e.g., as discussed herein, the user can select from options involving various actual usage versus usage limit notification policies and/or service usage control, limitations or throttling policies). - For example, the service usage policy or profile limits or allowances maintained for the network apparatus functions (e.g., the service profile or service plan usage limits stored in the
billing system 123 or AAA 121) can be read or queried by a network function (e.g., theservice controller 122 or theservice controller 122 through a second intermediary server connected to thebilling system 123 and/or the AAA system 121), and the service usage limits stored in these networking apparatus can be either directly translated to the settings for theservice processor 115 or may need to be interpreted, expanded or otherwise modified to obtain the requiredservice processor 115 policy and/or profile settings. - In some embodiments, the service usage limits set in the
billing system 123 service plan record, and/or the service profile record stored in theAAA system 121 can be acquired (e.g., from the apparatus or from a database storing the settings for the apparatus) by the service controller (or another network function) and directly translated and used to program the settings in theservice processor 123. In some embodiments, the service usage limits are determined or obtained by the activation server apparatus embodiments, other apparatus embodiments associated with service activation, or the virtual service provider embodiments, as described herein. In this manner, once the association of the service usage profile or policy settings used by adevice service processor 115 and the profile or policy settings used by the various network apparatus functions is established, then the service policy or profile for service monitoring, control, billing, verification and/or actions taken on verification error can be coordinated between device and network even if some of the network functions act independent of some of the device functions. - For example, associating the service usage policies and/or profiles between the
device service processor 115 and the various network apparatus functions, and then allowing for independent operation or action by the various functions in a manner that results in a coordinated outcome, facilitates an overlay of the device assisted services technology onto existing network equipment in a manner that results in reliable and verifiable service enhancements while minimizing the need for major existing network equipment upgrades. - In some embodiments, the association of the service profile or policy settings used by a
device service processor 115 and the service profile or policy settings used by the various network apparatus functions can be provided by a centralized network function that determines the appropriate settings for the network apparatus and theservice processor 115 and sets one or more settings to each function. In some embodiments, this networking function is provided by a centralized network management function or service account activation function (e.g., the activation server apparatus embodiments, one of the other disclosed apparatus embodiments associated with service activation or the virtual service provider apparatus embodiments, as described herein). - In some embodiments, the association of the service profile or policy settings used by a
device service processor 115 and the service profile or policy settings used by the various network apparatus functions can be provided by a network function that by reads, receives, queries, pulls or otherwise obtains the setting used by theservice controller 122 or theservice processor 115. The network function can then determine the association of the service profile or policy settings used by adevice service processor 115 and the service profile or policy settings required by the various network apparatus functions before writing, transmitting, pushing, or otherwise recording the appropriate settings required by each of the other network apparatus functions. In some embodiments, this functionality can be implemented in the service controller (e.g., the policy management server, possibly acting in coordination with another network function or server), which then links into the databases used for storing the policy or profile settings for the other network apparatus. - In some embodiments, once the association is established between service policy or profile settings in the network apparatus and the service policy or profile settings in the
service processor 115, then the network based service usage measures (e.g., IPDRs communicated to thebilling system 123, theAAA 121,service controller 122 or other network functions used to verify service usage and/or take actions) used for verification ofdevice 100 service usage versus service policy or profile can be monitored by the network apparatus (e.g.,billing system 123 and AAA 121) independent of coordination with theservice processor 115 and/or independent of theservice controller 122. In some embodiments, in addition to independent monitoring and verification of service usage versus policy, independent service profile or policy verification error response actions can be taken by the network apparatus (e.g., suspend, quarantine, SPAN orflag device 100, notify the user and possibly require acknowledgement, or bill the user account for service usage overage) without direct involvement by theservice processor 115 and/or theservice controller 122. - Accordingly, the association between service profile and/or service policy that is implemented on the device 100 (e.g., service processor 115) and the service profile and/or policy usage limits recorded in network apparatus can be associated with one another by one or more of the following: (A) implementing a function to read from the network database (e.g., the
billing 123 data base,AAA 121 data base,service controller 122 data base, etc.) and mapping the network profiles and/or policies to device 100 (e.g., service processor 115) profiles and/or policies; (B) implementing a function that simultaneously sets the device profile and/or policy and the network equipment profile and/or policy recorded in the appropriate data base records; and (C) implementing a function that reads the profile and/or policy on the device 100 (e.g., service processor 115) or theservice controller 122 and then sets the network equipment profile and/or policy recorded in the appropriate data base records. This allows for a simplified but coordinated response to monitoring, controlling and billing for service usage, for verifying service usage versus service usage profile or policy, and/or initiating or carrying out network actions in response to service usage versus profile or policy verification errors and/or device actions in response to service usage versus profile or policy verification errors. -
FIG. 17 is another functional diagram illustrating the device basedservice processor 115 and theservice controller 122 in accordance with some embodiments.FIG. 17 provides for various embodiments as similarly described above with respect to the various embodiments described above with respect toFIG. 16 , with one of the differences being that theservice controller 122 as shown inFIG. 17 is connected to the access network and not (directly) connected to the Internet. Accordingly, as shown inFIG. 17 , in some embodiments, theservice control link 1653 is a communications link between theservice controller 122 and theservice processor 115 over theaccess network 1610. -
FIG. 18 is another functional diagram illustrating the device basedservice processor 115 and theservice controller 122 in which the service processor controls the policy implementation for multiple access network modems and technologies in accordance with some embodiments. As shown,FIG. 18 provides for various embodiments as similarly described above with respect to the various embodiments described above with respect toFIG. 16 , with one of the differences being that the service processor controls the policy implementation for multiple access network modems and technologies. Accordingly, as shown inFIG. 18 , in some embodiments, aconnection manager 1804, which as shown is in control plane communication with a modem selection andcontrol 1811, provides a control and supervision function for one or more modem drivers or modems that connect to an access network. In some embodiments, the modem selection andcontrol 1811 selects the access network connection and is in communication with themodem firewall 1655, and modem drivers, which as shown include Dial/DSL modem driver 1831,Ethernet modem driver 1815,WPAN modem driver 1814,WLAN modem driver 1813, andWWAN modem driver 1812, convert data traffic into modem bus traffic for one or more modems and are in communication with the modem selection andcontrol 1811. -
FIG. 19 is another functional diagram illustrating theservice processor 115 and theservice controller 122 in accordance with some embodiments. As shown inFIG. 19 , a stripped down (e.g., reduced set of agents/components/functionality) embodiment of theservice processor 115 and theservice controller 122 are provided in which service policy is not adaptive but rather is set by theservice controller 122. In this example, the agent within theservice processor 115 that implements service policy is thepolicy implementation agent 1690. Also, in this example, theservice controller 122 is similarly stripped down to a simplified configuration (e.g., reduced set of agents/components/functionality). - Referring to
FIG. 19 , in some embodiments, many of the service policy implementation verification and compromise protection techniques are similarly provided using these simplified configurations of theservice processor 115 and theservice controller 122, as described above with respect to, for example,FIG. 16 . For example, the servicecontrol device link 1691 and servicecontrol server link 1638 can be used for downloading service policies to the policy implementation agent 1690 (but, in some embodiments, cannot perform the heartbeat or authentication function). - For example, a basic service profile or service policy implementation verification technique for this reduced configuration calls for the access
control integrity server 1654 to obtain IPDRs from access network AAA server 1621 (or 121) (e.g., or other network functions as described herein) and compare the service usage exhibited bydevice 100 with a range of expected service usage that would be expected if the intended service policies were in place on the device. In some embodiments, the accesscontrol integrity server 1654 initiates or carries out one or more of the service usage profile or policy verification error response actions disclosed herein, including, for example, one or more of the following: notify the user of the out of policy or overage condition, require the user to acknowledge the condition and/or acknowledge a subsequent billing event to proceed, bill the user for service overage, suspend the device from the network, quarantine the device, SPAN the device, or notify a network manager or device management or error handling function. - In some embodiments, a service profile or service policy implementation verification technique for this reduced configuration calls for the
billing system 123 to obtain IPDRs from access network AAA server 1621 (or 121) (or other network functions as discussed herein) and compare the service usage exhibited bydevice 100 with a range of expected service usage that would be expected if the intended service policies were in place on the device. In some embodiments, thebilling system 123 initiates or carries out one or more of the service usage profile or policy verification error response actions disclosed herein, including, for example, one or more of the following: notify the user of the out of policy or overage condition, require the user to acknowledge the condition and/or acknowledge a subsequent billing event to proceed, bill the user for service overage, suspend the device from the network, quarantine the device, SPAN the device, or notify a network manager or device management or error handling function. - In some embodiments, a service profile or service policy implementation verification technique for this reduced configuration calls for the AAA server 1621 (or 121) itself to compare the service usage exhibited by
device 100 with a range of expected service usage that would be expected if the intended service policies were in place on the device. In some embodiments, the AAA server 1621 (or 121) initiates or carries out one or more of the service usage profile or policy verification error response actions disclosed herein, including, for example, one or more of the following: notify the user of the out of policy or overage condition, require the user to acknowledge the condition and/or acknowledge a subsequent billing event to proceed, bill the user for service overage, suspend the device from the network, quarantine the device, SPAN the device, or notify a network manager or device management or error handling function. - Accordingly, this approach provides a basic first layer of service policy implementation verification that does not depend on device based agent behavior for the verification. If the service policy is in error in a way that violates the expected service policy usage limits, then the access
control integrity server 1654 will detect this condition and appropriate action can be taken. In some embodiments, if one or more service policy integrity verification tests fail, the appropriate responsive actions can include routing the device to quarantine status, sending an error message to the device or device user interface and then suspend access for the device, and/or limiting access in some way without completely suspending access, as similarly described above. In some embodiments, if one or more service policy integrity verification tests fail, the appropriate responsive actions can include logging excess service usage above the intended service policy limits and billing the user for some or all of the excess usage; sending the user a notification and/or acknowledgement response request (possibly including a simple keystroke acknowledgement, or a password, a biometric signature or other secure response), and/or limiting access in some way without completely suspending access, as similarly described above: - In some embodiments, a billing system technique provides another verification overlay. For example, the
service processor 115 can have a set of service policy implementations (or service profile) that calls for maintaining service usage within a certain limit, or assisting the user or network to maintain service usage to that limit. Thebilling system 123 can be implemented in a way to provide a “back stop” to the service usage controls or limits provided for by theservice processor 115, so that even if theservice processor 115 is compromised, hacked, spoofed or is otherwise in error, thebilling system 123 protects the service provider, “service owner”, carrier, VSP or network operator from unpaid access beyond the service limits. This can be accomplished, for example, by assigning a service usage limit within thebilling system 123 so that if theservice processor 115 is compromised and the service usage runs over the desired limit, thebilling system 123 automatically charges the user account for the overage. Thebilling system 123 can receive service usage information from the IPDRs that are aggregated in the network as in the case of a conventional billing system, and because these network based measures are independent from the device agent operation, they cannot be spoofed by merely spoofing something on the device orservice processor 115. In this manner, defeating theservice processor 115 service agent control mechanisms described herein simply results in a billing charge and not free service. In some embodiments, if the service usage runs over the service usage limit specified in the service profile, the user can be notified as discussed herein, and the user can be required to acknowledge the overage and approve a billing charge for the overage as also discussed herein, with the acknowledgement being communicated back to the network in some embodiments. This positive acknowledgement also provides a layer of protection and verification of the service control and usage limit control for thedevice service processor 115. In some embodiment also discussed herein, the user is requested to input a password, biometric or other secure response to the usage overage notification, providing yet another layer of protection to verify that the user intends to pay for the service usage overage. In these embodiments taken individually or in combination, theservice processor 115 assistance for service usage control can be verified and/or protected from compromise. - In some embodiments, the service
control device link 1691 and servicecontrol server link 1638 are used to implement theservice processor 115 heartbeat authentication and communication functions to strengthen the verification of a proper service policy implementation of the embodiments ofFIG. 19 . For example, the heartbeat function can be used as authentication for service monitoring versus network reports. In addition, the heartbeat function can be used as authentication for challenge/response queries of agents. Also, the heartbeat function can be used as authentication for access control. In some embodiments, to strengthen verification of the basic system illustrated inFIG. 19 , the communication access to thepolicy implementation agent 1690 is restricted so that software or hardware ondevice 100 and/or on a network cannot have authorized access to thepolicy implementation agent 1690. For example, authorized access to thepolicy implementation agent 1690 can be restricted to include only theservice controller 122 through the servicecontrol device link 1691 and the servicecontrol server link 1638. For example, theagent control bus 1630 can be secured with encryption and/or other security techniques so that only the servicecontrol device link 1691 can have authorized access to thepolicy implementation agent 1690. As another example, the agent level message encryption can be used as described herein. - In some embodiments, the service
policy implementation agent 1690 of the embodiments ofFIG. 19 can be further strengthened against errors, intrusion, tampering, hacking and/or other inadvertent or intentional integrity degradation by using various other techniques. For example, the dynamic agent download feature of theservice controller 122 can download a new version of thepolicy implementation agent 1690. In this example, the new agent code can be identical in functionality and also hashed, obfuscated or ordered differently before signing and encryption so that any hacking attempt must be reinitiated, and this process can be periodically repeated or repeated upon a triggering event. Additionally, once the new dynamically loaded agent is in place, it can be required to perform an environment scan to determine if the system configuration or operation are as expected, and/or it can seek to detect elements in the execution environment that can be harmful or threatening to the integrity of the policy implementation. The agent can also be required to report back on the scan within a relatively short period of time so that any attempt to compromise the agent does not have sufficient time to be effective. - In some embodiments, the service
policy implementation agent 1690 of the embodiments ofFIG. 19 can be further strengthened to protect the policy implementation from compromise attempts by locating the software and/or hardware used onto an access modem associated with the service. For example, the modem can make it difficult to get access to thepolicy implementation agent 1690 by employing one or more security elements on one or more access ports into the modem, such as the device bus, an I/O port, a network connection or the debug port. The modem can also store and/or execute the policy implementation agent in secure memory. The modem can also require a secure download key or a secure software signature to accept any updates to the agent software. - In some embodiments, the service
policy implementation agent 1690 of the embodiments ofFIG. 19 can be further strengthened against compromise attempts by performing scans of thedevice 100 code execution environment and/or code storage environment to identify potentially malicious and/or unwanted/untrusted software or hardware. For example, this function can be performed by thepolicy implementation agent 1690. The agent can have a local database of potentially malicious elements and compare the entries in the database against the elements detected locally using various malicious code, behavior blocking, intrusion detection, and/or other well known techniques for security analysis. Alternatively or in addition, the agent can communicate a list of some or all of the elements detected locally to theservice controller 122 to augment or take the place of the database comparison function that can be performed locally, thereby performing such or further such security analysis on the network (e.g., by the service controller 122), and, in some embodiments, if not automatically detected, such elements detected locally (e.g., and/or samples of such detected potentially malicious code or logs of potentially malicious/suspicious behavior/intrusions) forwarded to security analysts for the service provider for further security analysis (e.g., service provider security analysts and/or an outside security vendor engaged to protect the service provider's network and supported devices). In some embodiments, the agent detects new software downloads, installs and/or invocations and immediately issues an error flag report when potentially malicious software is downloaded, installed or invoked (e.g., file and network based on access security detection techniques). In some embodiments, the agent scans the local software loading and invocation activity along with a log of other software runtime events and regularly reports this trace so that when an error or compromise event occurs the trace preceding the event can be analyzed to determine the offending software or activity trace that took place to cause the compromise or error. For example, once the software or activity that caused the compromise is known or otherwise detected, it can be entered into a refreshed version of the database that the device and other devices use to detect potentially malicious precursor conditions. Examples of such precursor events can include software invocations, software downloads, a sequence of memory I/O events, a sequence of software access events, a sequence of network address or URL communications or downloads, or a sequence of access modem I/O activity. -
FIG. 20 is another functional diagram illustrating theservice processor 115 and theservice controller 122 in accordance with some embodiments. As shown inFIG. 20 , themodem firewall 1655 has been removed, and firewall and access control and traffic shaping functions are performed in these embodiments by thepolicy implementation agent 1690 andapplication interface agent 1693. -
FIG. 21 is another functional diagram illustrating theservice processor 115 and theservice controller 122 in accordance with some embodiments.FIG. 21 illustrates the various modem drivers andmodems 2122 through 2125 and 2141. In some embodiments, the modems, which includeWWAN modem 2122,WLAN modem 2123,WPAN modem 2124,Ethernet modem 2125, and Dial/DSL modem 2141, which are in communication with themodem bus 2120, connect the device to one or more networks. As shown, the service measurement points labeled I through VI represent various service measurement points forservice monitor agent 1696 and/or other agents to perform various service monitoring activities. Each of these measurement points can have a useful purpose in various embodiments described herein. For example, each of the traffic measurement points that is employed in a given design can be used by a monitoring agent to track application layer traffic through the communication stack to assist policy implementation functions, such as thepolicy implementation agent 1690, or, in some embodiments, themodem firewall agent 1655 or theapplication interface agent 1693, in making a determination regarding the traffic parameters or type once the traffic is farther down in the communication stack where it is sometimes difficult or impossible to make a complete determination of traffic parameters. It should be noted that although the present invention does not need to implement any or all of the measurement points illustrated inFIG. 21 to have an effective implementation as was similarly shown with respect toFIG. 19 , various embodiments benefit from these and/or similar measurement points. It should also be noted that the exact measurement points can be moved to different locations in the traffic processing stack, just as the various embodiments described herein can have the agents affecting policy implementation moved to different points in the traffic processing stack while still maintaining effective operation. - As shown in
FIG. 21 , measurement point I occurs at theapplication interface agent 1693 interface to the applications. At this measurement point, the application traffic can be monitored before it is framed, packetized or encrypted by the lower layers of the networking stack. For example, this allows inspection, characterization, tagging (literal or virtual) and, in some embodiments, shaping or control of services or traffic. At this measurement point, traffic can be more readily associated with applications, URLs or IP addresses, content type, service type, and other higher level parameters. For example, at this level email traffic and downloads, web browser applications and end points, media file transfers, application traffic demand, URL traffic demand and other such service monitoring parameters are more readily observed (e.g., accessible in the clear without the need for deep packet inspection and/or decryption), recorded and possibly shaped or controlled. As described herein, it is also possible to monitor upstream traffic demand at this point and compare it to the other measurement points to determine if the traffic policies in place are meeting overall traffic control policy objectives or to determine if traffic policy implementation is operating properly. For example, the downstream delivered traffic can be optimally observed at this measurement point. - As shown in
FIG. 21 , traffic measurement points II and III are situated on the upstream and downstream sides ofpolicy implementation agent 1690. As described herein, these two locations allow potential tracking of upstream and downstream traffic through the stack portions associated with thepolicy implementation agent 1690. These two locations also provide for potential cross-checking of how thepolicy implementation agent 1690 is impacting the demand and delivery of traffic. In a similar manner, measurement point III in connection with measurement point IV provide an opportunity for packet tracing through the stack components associated with themodem firewall 1655 and provide for the opportunity to observe the demand and delivery sides of themodem firewall 1655. Traffic measurement point V provides the potential for observing the traffic at the modem bus drivers for each of the modems. - As shown in
FIG. 21 , traffic measurement point VI provides, in some embodiments, the ultimate measure of access traffic, for example, the traffic that actually transacts over the access network through the modem. As shown, measurement point VI is at the modem side of the internal orexternal communications bus 1630, and it will be appreciated that, in some embodiments, this measurement point can be further down the modem stack closer to the MAC or physical layer (e.g., at the designer's discretion). An advantage of having a measurement point deep in the modem is, for example, that if the software or hardware that implements the measurement and reporting is well secured against compromise, then this measure can be almost as strong from a verification perspective as the measure that comes from the network (e.g., from the network elements). Accordingly, this makes it possible to compare this measure against the other measures to determine if there is a traffic path that is leaking past the other measurement point or one or more policy implementation points. -
FIG. 22 provides a table summarizingvarious service processor 115 agents (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments. Many of these agents are similarly described above, and the table shown inFIG. 22 is not intended to be an exhaustive summary of these agents, nor an exhaustive description of all functions that the agents perform or are described herein, but ratherFIG. 22 is provided as a summary aid in understanding the basic functions of each agent in accordance with some embodiments and how the agents interact with one another, with the service controller server elements, and/or with other network functions in certain embodiments to form a reliable device based service delivery solution and/or platform. -
FIG. 23 provides a table summarizingvarious service controller 122 server elements (and/or components/functions implemented in software and/or hardware) in accordance with some embodiments. Many of these agents are similarly described above, and the table shown inFIG. 23 is not intended to be an exhaustive summary of these server elements, nor an exhaustive description of all functions that the elements perform or are described herein, but ratherFIG. 23 is provided as a summary aid in understanding the basic functions of each element in accordance with some embodiments and how the elements interact with one another, certain network elements, and/or the service processor agents in certain embodiments to form a reliable device based service delivery solution and/or platform. - In some embodiments, it is desirable to provide a control plane between the service processor and the service controller using a flexible connection or communication path that, for example, will work between virtually any two network connection endpoints, one being the service controller and one being the device, in a secure yet scalable manner. In view of the embodiments described herein, one of ordinary skill in the art will recognize that it is possible to achieve such features with a variety of different embodiments that share similar core features to the embodiments described herein.
- Service Control Device Link and Continuous Heartbeat Authentication
- As described herein, there are numerous ways to implement the control plane communication channel between the
service processor 115 and theservice controller 122. Various embodiments described herein disclose a secure and bandwidth efficient control plane that is compatible with any IP based network (including the ability to locate theservice controller 122 over the Internet); provides for consistent device assisted service monitoring, control, verification and/or billing while roaming across multiple networks with different access technologies; and allows continuous device assisted service control verification and/or authentication with a variety of mechanisms for setting the transmission heartbeat frequency. Other techniques that could be used for this function include, for example, encapsulating the control plane in the access network control plane channel, encapsulating the control plane in IP or data packet framing mechanisms (e.g., IPV6), running a more conventional VPN or IPSEC channel, and/or using an independent access network connection. -
FIG. 24 is a functional diagram illustrating the servicecontrol device link 1691 of theservice processor 115 and the servicecontrol service link 1638 of theservice controller 122 in accordance with some embodiments. In particular, the servicecontrol device link 1691 of theservice processor 115 and the servicecontrol service link 1638 of theservice controller 122 as shown inFIG. 24 provide for secure control plane communication over theservice control link 1653 between theservice processor 115 and theservice controller 122 in accordance with some embodiments. Various embodiments include two or three layers of encryption in the service control link, with one embodiment or layer being implemented in the encrypt functions (2408, 2428) and decode functions (2412, 2422), and another embodiment or layer implemented in the transport services stack (2410, 2420). An optional third embodiment or layer of encryption is implemented below the transport services stack, for example, with IPSEC or another IP layer encryption, VPN or tunneling scheme. For example, various known security encryption techniques can be implemented in the encrypt functions (2408, 2428), with public/private or completely private keys and/or signatures so that very strong levels of security for service processor control plane traffic can be achieved even through the basic transport services (2410, 2420) implemented with standard secure or open Internet networking protocols, such as TLS or TCP. For example, the service processor agent communications local to the device can be conducted to and from the service controller elements via the servicecontrol device link 1691 connection to theagent communication bus 1630. The combination of the servicecontrol device link 1691 and theagent communication bus 1630, which in some embodiments is also securely encrypted or signed, provides a seamless, highly secure, asynchronous control plane connection between the service processor and service controller server elements and the service controller and service controller agents that works over a wide range of access networks, such as any access network that has the capability to connect IP or TCP traffic to another TCP or IP endpoint on the access network, another private network or over theInternet 120. As described herein, in some embodiments, theagent communication bus 1630 also provides a fourth level of encrypted or signed communication to form a secure closed system on the device for agent to agent communication, for example, making it very difficult or practically impossible for software or applications to gain access to one or more of the a service processor agents on the device in any way other than the servicecontrol device link 1691. In this way, in some embodiments, theagent communication bus 1630 and the service processor agents can only be accessed by one another as necessary or permitted by agent communication policies, or by the service controller or other authorized network function with proper security credentials communicating over the servicecontrol device link 1691. Additionally, in some embodiments, communications between a subset of two or more agents, or between one or more agents and one or more service controller server elements are encrypted with unique keys or signatures in such a way that a fourth level of security providing private point to point, point to multipoint, or multipoint to multipoint secure communication lines is provided. - In some embodiments, all of the service
control device link 1691 communications are transformed into a continuous control plane connection, with a frequency based on the rate of service usage, a minimum set period between connections, and/or other methods for establishing communication frequency. In some embodiments, this heartbeat function provides a continuous verification link by which the service controller verifies that the service processor and/or device are operating properly with the correct service policies being implemented. In view of the following heartbeat function embodiments described herein, it will be apparent to one of ordinary skill in the art that different approaches for implementing the various heartbeat embodiments are possible, and it will be clear that there are many ways to achieve the essential features enabling a reliable, sometimes continuous control link and verification function for the purpose of assisting control of service usage in a verifiable manner. As shown, inside theservice processor 115, the servicecontrol device link 1691 includes aheartbeat send counter 2402 in communication with theagent communication bus 1630. For example, the heartbeat send counter 2402 can provide a count for triggering when aservice processor 115 communication (e.g., periodic communication based on a heartbeat mechanism) should be sent to theservice controller 122, and aheartbeat buffer 2404, also in communication with theagent communication bus 1630, buffers any such information for thenext service processor 115 communication, in accordance with various heartbeat based embodiments, as similarly described herein. Theheartbeat buffer 2404 is in communication with aframing element 2406 and anencrypt element 2408 for framing and encrypting anyservice processor 115 communications transmitted to theservice controller 122 by a transport services stack 2410 over theservice control link 1653. Similarly, as shown inside theservice controller 122, the servicecontrol server link 1638 includes aheartbeat send counter 2434 in communication with aservice controller network 2440, aheartbeat buffer 2432, also in communication with theservice controller network 2440, buffers any such information for thenext service controller 122 communication, in accordance with various heartbeat based embodiments, as similarly described herein. Theheartbeat buffer 2432 is in communication with aframing element 2430 and anencrypt element 2428 for framing and encrypting anysuch service controller 122 communications transmitted to theservice processor 115 by a transport services stack 2420 over theservice control link 1653. - As also shown inside the
service processor 115 ofFIG. 24 , the servicecontrol device link 1691 includes adecode element 2412 for decoding any receivedservice controller 122 communications (e.g., decrypting encrypted communications), anunpack element 2414 for unpacking the receivedservice controller 122 communications (e.g., assembling packetized communications), and anagent route 2416 for routing the receivedservice controller 122 communications (e.g., commands, instructions, heartbeat related information or status reports, policy related information or configuration settings and/or updates, challenge/response queries, agent refreshes and/or new software for installation) to the appropriate agent of theservice processor 115. Similarly, as shown inside theservice controller 122, the servicecontrol server link 1638 also includes adecode element 2422 for decoding any receivedservice processor 115 communications (e.g., decrypting encrypted communications), anunpack element 2424 for unpacking the receivedservice processor 115 communications (e.g., assembling packetized communications), and anagent route 2426 for routing the receivedservice processor 115 communications (e.g., responses to instructions and/or commands, heartbeat related information or status reports, policy related information or configuration settings and/or updates, challenge/response queries, agent status information, network service/cost usage and/or any other reporting related information) to the appropriate agent of theservice controller 122. Accordingly, as described herein with respect to various embodiments, the various secure communications between theservice controller 122 and theservice processor 115 can be performed using the embodiment as shown inFIG. 24 , and those of ordinary skill in the art will also appreciate that a variety of other embodiments can be used to similarly provide the various secure communications between theservice controller 122 and the service processor 115 (e.g., using different software and/or hardware architectures to provide secure communications, such as using additional and/or fewer elements/functions or other design choices for providing such secure communications). - In some embodiments, an efficient and effective communication framing structure between the service processor and service controller is provided, and the following embodiments (e.g., as shown and described with respect to
FIG. 25 ) teach such a structure that packs the various service processor agent control plane communications and the various service controller element control plane connections into a format that does not consume excessive bandwidth to enable a continuous control plane connection between the device and service controller. In some embodiments, an efficient and effective communication framing structure between the service processor and service controller is provided to buffer such communication messages for some period of time before framing and transmitting, such as in a heartbeat frequency that is based on rate of service usage. In some embodiments, an efficient and effective communication framing structure between the service processor and service controller is provided to allow for the frame to be easily packed, encrypted, decoded, unpacked and the messages distributed. In view of the various embodiments described herein, it will be apparent to one of ordinary skill in the art that many framing structures will work for the intended purpose of organizing or framing agent communications and the uniqueness and importance of combining such a system element with the device service controller functions, the service processor functions, the service control verification functions and/or the other purposes. -
FIG. 25 is a functional diagram illustrating a framing structure of a serviceprocessor communication frame 2502 and a servicecontroller communication frame 2522 in accordance with some embodiments. In particular, the servicecontrol device link 1691 of theservice processor 115 and the servicecontrol service link 1638 of the service controller 122 (e.g., as shown inFIG. 24 ) provide for secure control plane communication over theservice control link 1653 between theservice processor 115 and theservice controller 122 using communication frames in the format of the serviceprocessor communication frame 2502 and the servicecontroller communication frame 2522 as shown inFIG. 25 in accordance with some embodiments. As shown, the serviceprocessor communication frame 2502 includes a service processorframing sequence number 2504, atime stamp 2506, an agentfirst function ID 2508, an agent firstfunction message length 2510, an agentfirst function message 2512, and assuming more than one message is being transmitted in this frame, an agentNth function ID 2514, an agent Nthfunction message length 2516, and an agentNth function message 2518. Accordingly, the serviceprocessor communication frame 2502 can include one or more messages as shown inFIG. 25 , which can depend on networking frame length requirements and/or other design choices. Similarly, as shown, the servicecontroller communication frame 2522 includes a service controllerframing sequence number 2524, atime stamp 2526, an agentfirst function ID 2528, an agent firstfunction message length 2530, an agentfirst function message 2532, and assuming more than one message is being transmitted in this frame, an agentNth function ID 2534, an agent Nthfunction message length 2536, and an agentNth function message 2538. Accordingly, the servicecontroller communication frame 2522 can include one or more messages as shown inFIG. 25 , which can depend on networking frame length requirements and/or other design choices: -
FIGS. 26A through 26E provide tables summarizing various service processor heartbeat functions and parameters (e.g., implemented by various agents, components, and/or functions implemented in software and/or hardware) in accordance with some embodiments. Many of these heartbeat functions and parameters are similarly described above, and the tables shown inFIGS. 26A-E are not intended to be an exhaustive summary of these heartbeat functions and parameters, but rather are provided as an aid in understanding these functions and parameters in accordance with some heartbeat based embodiments described herein. -
FIGS. 27A through 27G provide tables summarizing various device based service policy implementation verification techniques in accordance with some embodiments. Many of these device based service policy implementation verification techniques are similarly described above, and the tables shown inFIGS. 27A-G are not intended to be an exhaustive summary of these device based service policy implementation verification techniques, but rather are provided as an aid in understanding these techniques in accordance with some device based service policy embodiments described herein. -
FIGS. 28A through 28C provide tables summarizing various techniques for protecting the device based service policy from compromise in accordance with some embodiments. Many of these techniques for protecting the device based service policy from compromise are similarly described above, and the tables shown inFIGS. 28A-C are not intended to be an exhaustive summary of these techniques for protecting the device based service policy from compromise, but rather are provided as an aid in understanding these techniques in accordance with some device based service policy embodiments described herein. - Device Assisted Service Control and Traffic Control
- As described below, various techniques are disclosed for implementing device assisted traffic shaping and service control at the lower levels of service usage policy implementation.
-
FIG. 29 is a functional diagram illustrating a device communications stack that allows for implementing verifiable traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. As shown, several service agents take part in data path operations to achieve various data path improvements, and, for example, several other service agents can manage the policy settings for the data path service, implement billing for the data path service, manage one or more modem selection and settings for access network connection, interface with the user and/or provide service policy implementation verification. Additionally, in some embodiments, several agents perform functions to assist in verifying that the service control or monitoring policies intended to be in place are properly implemented, the service control or monitoring policies are being properly adhered to, that the service processor or one or more service agents are operating properly, to prevent unintended errors in policy implementation or control, and/or to prevent tampering with the service policies or control. As shown, the service measurement points labeled I through VI represent various service measurement points forservice monitor agent 1696 and/or other agents to perform various service monitoring activities. Each of these measurement points can have a useful purpose in various embodiments described herein. For example, each of the traffic measurement points that is employed in a given design can be used by a monitoring agent to track application layer traffic through the communication stack to assist policy implementation functions, such as thepolicy implementation agent 1690, or in some embodiments themodem firewall agent 1655 or theapplication interface agent 1693, in making a determination regarding the traffic parameters or type once the traffic is farther down in the communication stack where it is sometimes difficult or impossible to make a complete determination of traffic parameters. For example, a detailed set of embodiments describing how the various measurement points can be used to help strengthen the verification of the service control implementation are described herein, including, for example, the embodiments described with respect toFIG. 16 andFIG. 21 . The particular locations for the measurement points provided in these figures are intended as instructional examples, and other measurement points can be used for different embodiments, as will be apparent to one of ordinary skill in the art in view of the embodiments described herein. Generally, in some embodiments, one or more measurement points within the device can be used to assist in service control verification and/or device or service troubleshooting. - In some embodiments, the service monitor agent and/or other agents implement virtual traffic tagging by tracking or tracing packet flows through the various communication stack formatting, processing and encryption steps, and providing the virtual tag information to the various agents that monitor, control, shape, throttle or otherwise observe, manipulate or modify the traffic. This tagging approach is referred to herein as virtual tagging, because there is not a literal data flow, traffic flow or packet tag that is attached to flows or packets, and the book-keeping to tag the packet is done through tracking or tracing the flow or packet through the stack instead. In some embodiments, the application interface and/or other agents identify a traffic flow, associate it with a service usage activity and cause a literal tag to be attached to the traffic or packets associated with the activity. This tagging approach is referred to herein as literal tagging. There are various advantages with both the virtual tagging and the literal tagging approaches. For example, it can be preferable in some embodiments to reduce the inter-agent communication required to track or trace a packet through the stack processing by assigning a literal tag so that each flow or packet has its own activity association embedded in the data. As another example, it can be preferable in some embodiments to re-use portions of standard communication stack software or components, enhancing the verifiable traffic control or service control capabilities of the standard stack by inserting additional processing steps associated with the various service agents and monitoring points rather than re-writing the entire stack to correctly process literal tagging information, and in such cases, a virtual tagging scheme may be desired. As yet another example, some standard communication stacks provide for unused, unspecified or otherwise available bit fields in a packet frame or flow, and these unused, unspecified or otherwise available bit fields can be used to literally tag traffic without the need to re-write all of the standard communication stack software, with only the portions of the stack that are added to enhance the verifiable traffic control or service control capabilities of the standard stack needing to decode and use the literal tagging information encapsulated in the available bit fields. In the case of literal tagging, in some embodiments, the tags are removed prior to passing the packets or flows to the network or to the applications utilizing the stack. In some embodiments, the manner in which the virtual or literal tagging is implemented can be developed into a communication standard specification so that various device or service product developers can independently develop the communication stack and/or service processor hardware and/or software in a manner that is compatible with the service controller specifications and the products of other device or service product developers.
- It will be appreciated that although the implementation/use of any or all of the measurement points illustrated in
FIG. 29 is not required to have an effective implementation, such as was similarly shown with respect to various embodiments described herein, such as with respect toFIGS. 19 and 21 , various embodiments can benefit from these and/or similar measurement points. It will also be appreciated that the exact measurement points can be moved to different locations in the traffic processing stack, just as the various embodiments described herein can have the agents affecting policy implementation moved to different points in the traffic processing stack while still maintaining effective operation. In some embodiments, one or more measurement points are provided deeper in the modem stack (e.g., such as for embodiments similarly described herein with respect toFIGS. 35 and 36 ) where, for example, it is more difficult to circumvent and can be more difficult to access for tampering purposes if the modem is designed with the proper software and/or hardware security to protect the integrity of the modem stack and measurement point(s). - Referring to
FIG. 29 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack. Example measurement point VI resides within or just above the modem driver layer: For example, the modem driver performs modem bus communications, data protocol translations, modem control and configuration to interface the networking stack traffic to the modem. As shown, measurement point VI is common to all modem drivers and modems, and it is advantageous for certain embodiments to differentiate the traffic or service activity taking place through one modem from that of one or more of the other modems. In some embodiments, measurement point VI, or another measurement point, is located over, within or below one or more of the individual modem drivers. The respective modem buses for each modem reside between example measurement points V and VI. In the next higher layer, a modem selection & control layer for multimode device based communication is provided. In some embodiments, this layer is controlled by a network decision policy that selects the most desirable network modem for some or all of the data traffic, and when the most desirable network is not available the policy reverts to the next most desirable network until a connection is established provided that one of the networks is available. In some embodiments, certain network traffic, such as verification, control, redundant or secure traffic, is routed to one of the networks even when some or all of the data traffic is routed to another network. This dual routing capability provides for a variety of enhanced security, enhanced reliability or enhanced manageability devices, services or applications. In the next higher layer, a modem firewall is provided. For example, the modem firewall provides for traditional firewall functions, but unlike traditional firewalls, in order to rely on the firewall for verifiable service usage control, such as access control and security protection from unwanted networking traffic or applications, the various service verification techniques and agents described herein are added to the firewall function to verify compliance with service policy and prevent tampering of the service controls. In some embodiments, the modem firewall is implemented farther up the stack, possibly in combination with other layers as indicated in other Figures. In some embodiments, a dedicated firewall function or layer is provided that is independent of the other processing layers, such as the policy implementation layer, the packet forwarding layer and/or the application layer. In some embodiments, the modem firewall is implemented farther down the stack, such as within the modem drivers, below the modem drivers, or in the modem itself. Example measurement point IV resides between the modem firewall layer and an IP queuing and routing layer. As shown, an IP queuing and routing layer is separate from the policy implementation layer where the policy implementation agent implements a portion of the traffic control and/or service usage control policies. As described herein, in some embodiments, these functions are separated so that a standard network stack function can be used for IP queuing and routing, and the modifications necessary to implement the policy implementation agent functions can be provided in a new layer inserted into the standard stack. In some embodiments, the IP queuing and routing layer is combined with the traffic or service usage control layer. Examples of this combined functionality are shown and described with respect toFIGS. 31 , 32 and 33. For example, a combined routing and policy implementation layer embodiment can also be used with the other embodiments, such as shown inFIG. 29 . Various detailed embodiments describing how the policy implementation layer can control traffic or other service usage activities are described with respect toFIG. 38 . Measurement point III resides between the IP queuing and routing layer and a policy implementation agent layer. Measurement point II resides between the policy implementation agent layer and the transport layer, including TCP, UDP, and other IP as shown. The session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. Measurement point I resides between the network services API layer and an application layer, shown as application service interface agent in the device communications stack ofFIG. 29 . - As shown, the application service interface layer is above the standard networking stack API and, in some embodiments, its function is to monitor and in some cases intercept and process the traffic between the applications and the standard networking stack API. In some embodiments, the application service interface layer identifies application traffic flows before the application traffic flows are more difficult or practically impossible to identify farther down in the stack. In some embodiments, the application service interface layer in this way assists application layer tagging in both the virtual and literal tagging cases. In the case of upstream traffic, the application layer tagging is straight forward, because the traffic originates at the application layer. In some downstream embodiments, where the traffic or service activity classification relies on traffic attributes that are readily obtainable, such as source address or URL, application socket address, IP destination address, time of day or any other readily obtained parameter, the traffic type can be identified and tagged for processing by the firewall agent or another agent as it initially arrives. In other embodiments, as described herein, in the downstream case, the solution is generally more sophisticated when a traffic parameter that is needed to classify the manner in which the traffic flow is to be controlled or throttled is not readily available at the lower levels of the stack, such as association with an aspect of an application, type of content, something contained within TLS, IPSEC or other secure format, or other information associated with the traffic. Accordingly, in some embodiments the networking stack identifies the traffic flow before it is fully characterized, categorized or associated with a service activity, and then passes the traffic through to the application interface layer where the final classification is completed. In such embodiments, the application interface layer then communicates the traffic flow ID with the proper classification so that after an initial short traffic burst or time period the policy implementation agents can properly control the traffic. In some embodiments, there is also a policy for tagging and setting service control policies for traffic that cannot be fully identified with all sources of tagging including application layer tagging.
- Various applications and/or a user service interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)). Also, the billing agent, which is in communication with the
agent communication bus 1630, communicates user information and decision query and/or user input to the user service interface agent, as shown. The policy control agent communicates service settings and/or configuration information via thiscommunications bus 1630, as shown (illustrating such communications with a reference (B) via the application layer, policy implementation agent layer, which is lower in the communications stack as shown, and/or the modem firewall layer). The connection manager agent communicates select and control commands and/or modem and access network information via this communications stack, as shown (illustrating such communications with a reference (C) via the modem selection and control layer). Various other communications (e.g., service processor and/or service controller related communications, such as service usage measure information and/or application information) are provided at various levels of this communications stack, as shown (illustrating such communications with references (D) at the application layer, (E) at the policy implementation agent layer, and (F) at the modem firewall layer). - As shown in
FIG. 29 , a service monitor agent, which is also in communication with theagent communication bus 1630, communicates with various layers of the device communications stack. For example, the service monitor agent, performs monitoring at each of measurement points I through VI, receiving information including application information, service usage and other service related information, and assignment information. An access control integrity agent is in communication with the service monitor agent via theagent communications bus 1630, as also shown. - In some embodiments, one or more of the networking stack modifications described herein in combination one or more of the service verification and tamper prevention techniques described herein is provided. As similarly described with respect to
FIG. 29 , the various example embodiments for assisting service control verification described herein and as summarized in the example tables provided inFIGS. 26 , 27 and 28 can be employed individually or in combination to create increasingly secure cross-functional service control verification embodiments. InFIG. 29 , the presence of the access control integrity agent, policy control agent, service monitor agent and the other agents that perform verification and/or tamper prevention functions illustrates verifiable service control aspects in accordance with some embodiments. Furthermore, the presence of the billing agent combined with the service verification and/or tamper prevention agents and techniques described herein provides for a set of verifiable billing embodiments for service billing, service billing offset corrections, bill by account, transaction billing and other billing functions. In addition, the presence of the user service interface agent in combination with the service control agent functions in the modified networking stack provide for embodiments involving a combination of service control with user preferences, which as described herein, provides the user with the capability to optimize service versus service cost in a network neutral manner. In some embodiments, the user control of service control policy is provided along with the service control verification and/or tamper prevention. The presence of the policy control agent that in some embodiments implements a higher than most basic level of policy decision and control with the policy implementation agents in the modified networking stack allows for, for example, the device to possess the capability to implement a higher level of service control for the purpose of obtaining a higher level service usage or service activity objective. In some embodiments, the application layer tagging in combination with other embodiments described herein provides for deep service activity control that is verifiable. - In some embodiments, verifiable traffic shaping as described herein can be performed using the device communications stack in a variety of embodiments for the combination of service control within the networking stack and service control verification and/or tamper prevention, with various embodiments depicted in
FIGS. 29 through 37 . Additional levels of detail regarding how such embodiments can be used to implement verifiable traffic shaping are provided in and described with respect toFIGS. 38 through 40 which depict example functional diagrams of packet processing flows for verifiable traffic shaping or service activity control in a device service processor for both upstream and downstream flows. Along with several other interesting features embodied inFIGS. 38 through 40 , application traffic layer tagging is depicted in additional detail in accordance with some embodiments. For example, the application interface agent can determine service data usage at the application layer using measurement point I and a local service usage counter, and can, for example, pass this information to the service monitor agent. If service usage exceeds a threshold, or if using a service usage prediction algorithm results in predicted service usage that will exceed a threshold, then the user can be notified of which applications are causing the service usage overrun or potential service usage overrun, via the user service interface agent. The user can then identify which application service (e.g., traffic associated with a specified high service use or non-critical application, such as for example a high bandwidth consumption social networking website or service, media streaming website or service, or any other high bandwidth website or service transmitting and/or receiving data with the service network) that the user prefers to throttle. As another example, the user could select a service policy that allows for video chat services until those services threaten to cause cost over-runs on the user's service plan, and at that time the service policy could switch the chat service to voice only and not transmit or receive the video. The traffic associated with the user specified application can then be throttled according to user preference input. For example, for downstream traffic, packets (e.g., packets that are virtually or literally tagged and/or otherwise associated with the application traffic to be throttled) from the access network can be buffered, delayed and/or dropped to throttle the identified application traffic. For upstream traffic, packets (e.g., packets that are virtually or literally tagged and/or otherwise associated with the application traffic to be throttled) can be buffered, delayed and/or dropped before being transmitted to the access network to throttle the identified application traffic. As similarly described above, traffic shaping as described herein can be verified, such as by the service monitor agent via the various measurement points and/or using other agents. - The embodiments depicted in
FIG. 30 and other figures generally require enhancements to conventional device networking communication stack processing. For example, these enhancements can be implemented in whole or in part in the kernel space for the device OS, in whole or in part in the application space for the device, or partially in kernel space and partially in application space. As described herein, the networking stack enhancements and the other elements of the service processor can be packaged into a set of software that is pre-tested or documented to enable device manufacturers to quickly implement and bring to market the service processor functionality in a manner that is compatible with the service controller and the applicable access network(s). For example, the service processor software can also be specified in an interoperability standard so that various manufacturers and software developers can develop service processor implementations or enhancements, or service controller implementations or enhancements that are compatible with one another. -
FIG. 30 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In some embodiments, a portion of the service processor is implemented on the modem (e.g., on modem module hardware or modem chipset) and a portion of the service processor is implemented on the device application processor subsystem. It will be apparent to one of ordinary skill in the art that variations of the embodiment depicted inFIG. 30 are possible where more or less of the service processor functionality is moved onto the modem subsystem or onto the device application processor subsystem. For example, such embodiments similar to that depicted inFIG. 30 can be motivated by the advantages of containing some or all of the service processor network communication stack processing and/or some or all of the other service agent functions on the modem subsystem (e.g., and such an approach can be applied to one or more modems). For example, the service processor can be distributed as a standard feature set contained in a modem chipset hardware of software package or modem module hardware or software package, and such a configuration can provide for easier adoption or development by device OEMs, a higher level of differentiation for the chipset or modem module manufacturer, higher levels of performance or service usage control implementation integrity or security, specification or interoperability standardization, and/or other benefits. - Referring to
FIG. 30 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for modem MAC/PHY layer at the bottom of the device communications stack. Measurement point IV resides above the modem MAC/PHY layer. The modem firewall layer resides between measurement points IV and III. In the next higher layer, the policy implementation agent is provided, in which the policy implementation agent is implemented on the modem (e.g., on modem hardware). Measurement point II resides between the policy implementation agent and the modem driver layer, which is then shown below a modem bus layer. The next higher layer is shown as the IP queuing and routing layer, followed by the transport layer, including TCP, UDP, and other IP as shown. The session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. Measurement point I resides between the network services API layer and an application layer, shown as application service interface agent in the device communications stack ofFIG. 30 . - Various applications and/or a user service,interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)). Also, the billing agent, which is in communication with the
agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown. The policy control agent B communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (B)) via the application layer. The policy control agent A communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (D)) via the policy implementation agent layer and/or the modem firewall layer. The connection manager agent communicates select & control commands and/or modem and access network information via this communications stack, as shown (illustrating such communications with a reference (C)) via the modem driver layer. Various other communications (e.g., service processor and/or service controller related communications, such as service usage measure information, and/or application information) are provided at various levels of this communications stack, as shown (illustrating such communications with references (E)) at the application layer through the modem driver layer with the service monitor agent B as shown (and an access control integrity agent B is also shown), and communications with references (F) at the policy implementation agent layer and (G) at the modem firewall layer with the service monitor agent A as shown (and an access control integrity agent A is also shown). In some embodiments, the service usage policy verification or tamper prevention embodiments described herein can be applied, in isolation or in combination, in the context ofFIG. 31 to provide for embodiments with increasing levels of service usage policy control verification certainty, such as provided withFIGS. 26 , 27 and 28. -
FIG. 31 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In some embodiments, the service processor is a simplified implementation. For example, this approach can be used for applications with less capable device application processors, rapid time to market needs, fewer service usage control needs, and/or other reasons that lead to a need for a lower complexity implementation. - Referring to
FIG. 31 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for the modem layer at the bottom of the device communications stack. The modem driver layer resides above the modem bus layer as shown. In the next higher layer, the policy implementation agent is provided, and the policy implementation agent is also in communication with theagent communication bus 1630 as shown. The next higher layer is shown as the transport layer, including TCP, UDP, and other IP as shown. The session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. Applications communicate with the device communications stack via the network services API as shown. Policy settings from the network (e.g., service settings) are communicated with the policy implementation agent as shown. The connection manager communicates select and control as well as modem and access network information via the modem driver as shown. AlthoughFIG. 31 does not depict all of the service usage control verification functions provided by certain embodiments calling for additional service verification or control agents, a high level of service policy implementation verification certainty can be achieved within the context of the embodiments depicted inFIG. 31 by applying a subset of the service usage policy verification or tamper prevention embodiments described herein. For example, the embodiments depicted inFIG. 31 can be combined with the service controller embodiments that utilize IPDRs to verify service usage is in accordance with the desired service policy. There are also many other service usage control embodiments described herein that can be applied in isolation or in combination to the embodiments depicted inFIG. 31 to provide increasing levels of service usage control verification certainty, as will be apparent to one of ordinary skill in the art in view ofFIGS. 26 , 27 and 28 and the various embodiments described herein. -
FIG. 32 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In some embodiments, the service processor is a simplified implementation embodiment with device based monitoring and integrity control. For example,FIG. 32 provides for somewhat higher complexity (e.g., relative to the embodiments depicted inFIG. 30 ) in exchange for the enhanced service monitoring, control or verification that are possible by implement additional agent embodiments, such as the service monitor agent and the access control integrity agent functions. - Referring to
FIG. 32 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack. Measurement point II resides above the modem selection & control layer, which resides above the modem buses for each modem. Measurement point I resides between the policy implementation agent (policy based router/firewall) layer and the transport layer, including TCP, UDP, and other IP as shown. The session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. Applications communicate with the device communications stack via the network services API as shown. Policy settings from the network (e.g., service settings) are communicated with the policy implementation agent as shown. The connection manager communicates select and control as well as modem and access network information via the modem selection and control layer as shown. The service monitor agent, which is also in communication with theagent communication bus 1630, communicates with various layers of the device communications stack. For example, the service monitor agent, performs monitoring at each of measurement points I and II, receiving information including application information, service usage and other service related information, and assignment information. An access control integrity agent is in communication with the service monitor agent via theagent communications bus 1630, as also shown. As similarly described with respect toFIGS. 30 and 31 , many of the service usage control verification embodiments described herein can be applied in isolation or in combination in the context ofFIG. 32 . -
FIG. 33 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. Referring toFIG. 33 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack. Measurement point III resides above the modem selection & control layer, which resides above the respective modem buses for each modem. Measurement point II resides between the policy implementation agent (policy based router/firewall) layer and the transport layer, including TCP, UDP, and other IP as shown. The session layer resides above the transport layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. Measurement point I resides between the network services API layer and an application layer, shown as application service interface agent in the device communications stack ofFIG. 33 . - Various applications and/or a user service interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)). Also, the billing agent, which is in communication with the
agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown. The policy control agent communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (B)) via the policy implementation agent layer. The connection manager agent communicates select & control commands and/or modem and access network information via this communications stack, as shown (illustrating such communications with a reference (C)) via the modem selection and control layer. Various other communications (e.g., service processor and/or service controller related communications, such as service usage measure information, application information) are provided at various levels of this communications stack, as shown (illustrating such communications with references (D)) at the application layer and (E) at the policy implementation agent layer. - As shown in
FIG. 33 , a service monitor agent, which is also in communication with theagent communication bus 1630, communicates with various layers of the device communications stack. For example, the service monitor agent, performs monitoring at each of measurement points I through III, receiving information including application information, service usage and other service related information, and assignment information. An access control integrity agent is in communication with the service monitor agent via theagent communications bus 1630, as also shown. As similarly described with respect toFIGS. 30 , 31 and 32, many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context ofFIG. 33 . -
FIG. 34 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In some embodiments, the data path processing for the service processor is provided in conjunction with a single modem driver as shown. As shown, the service processor communication stack processing is provided below the standard network communication stack and in combination with a modem driver (e.g., and this approach can be extended to more than one modem). - Referring to
FIG. 34 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack. Measurement point II resides above themodem driver 1 layer. Measurement point I resides between the policy implementation agent (policy based router/firewall) layer and the modem selection and control layer, for themodem driver 1 stack in this single modem driver embodiment. The transport layer, including TCP, UDP, and other IP resides above the IP queuing and routing layer, which resides above the modem selection and control layer, as shown. The session layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer, resides above the transport layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. - As shown in
FIG. 34 , applications communicate with the device communications stack via the network services API as shown (illustrating such communications with a reference (A)). Policy settings from the network (e.g., service settings) are communicated with the policy implementation agent as shown (illustrating such communications with a reference (B)). The service monitor agent, which is also in communication with theagent communication bus 1630, communicates with policy implementation agent layer of the device communications stack. Also, the service monitor agent performs monitoring at each of measurement points I and II, receiving information including application information, service usage and other service related information, and assignment information. An access control integrity agent is in communication with the service monitor agent via theagent communications bus 1630, as also shown. Various other communications (e.g., service processor and/or service controller related communications, such as service usage measure information, application information) are provided at various levels of this communications stack, as shown (illustrating such communications with references (C)) at the policy implementation agent layer. Also, the billing agent, which is in communication with theagent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown. As similarly described with respect toFIGS. 30 , 31, 32 and 33, many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context ofFIG. 34 . -
FIG. 35 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In particular,FIG. 35 illustrates a single modem hardware embodiment as shown. As shown, the service processor network communication stack processing is provided on the modem hardware (e.g., and this approach can be extended to more than one modem). This approach allows for the service processor to be distributed as a standard feature set contained in a modem chipset hardware of software package or modem module hardware or software package, which, for example, can provide for easier adoption or development by device OEMs, a higher level of differentiation for the chipset or modem module manufacturer, higher levels of performance or service usage control implementation integrity, or other benefits. - Referring to
FIG. 35 , describing the device communications stack from the bottom to the top of the stack as shown, the device communications stack provides a communication layer for each of the modems of the device at the bottom of the device communications stack. As shown, measurement points I and II and the policy implementation agent reside on the modem 1 (e.g., implemented as hardware and/or software on modem 1). Measurement point I resides above the policy implementation agent (policy based router/firewall) layer, and measurement point II resides below the policy implementation agent later. The modem selection and control layer resides above the modem drivers layer, as shown. The transport layer, including TCP, UDP, and other IP resides above the IP queuing and routing layer, which resides above the modem selection and control layer, as shown. The session layer, which is shown as a socket assignment and session management (e.g., basic TCP setup, TLS/SSL) layer, resides above the transport layer. The network services API (e.g., HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer. - As shown in
FIG. 35 , applications communicate with the device communications stack via the network services API as shown. Policy settings from the network (e.g., service settings) are communicated with the policy implementation agent as shown (illustrating such communications with a reference (A)). The service monitor agent, which is also in communication with theagent communication bus 1630, communicates with policy implementation agent layer of themodem 1. Also, the service monitor agent performs monitoring at each of measurement points I and II, receiving information including application information, service usage and other service related information, and assignment information. An access control integrity agent is in communication with the service monitor agent via theagent communications bus 1630, as also shown. Various other communications (e.g., service processor and/or service controller related communications, such as service usage measure information and/or application information) are provided at various levels of this communications stack, as shown (illustrating such communications with references (B)) at the policy implementation agent layer. As similarly described with respect toFIGS. 30 , 31, 32, 33 and 34, many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context ofFIG. 35 . -
FIG. 36 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In particular,FIG. 36 illustrates a single modem hardware embodiment, in whichmodem 1 includes a portion of the service processor networking communication stack processing and measurement points II and III and the policy implementation agent, as similarly shown inFIG. 35 , and the higher levels of the device communications stack above themodem 1 layer, such as the application service interface layer, are implemented on the device application processor or in the device application processor memory as similarly described above, for example, with respect toFIG. 33 , in which a measurement point I is shown between the application service interface agent layer and the network services API layer. For example, this approach allows for the application service interface agent to be provided on the device application processor or memory so that application layer service usage monitoring or control can be implemented. For example, the differences between the embodiments depicted inFIG. 36 and those ofFIG. 30 include a simplified implementation and a policy control agent that is entirely implemented on the modem and not partially implemented in the application processor memory. - Various applications and/or a user service interface agent communicate via this communications stack, as shown (illustrating such communications with a reference (A)). Also, the billing agent, which is in communication with the
agent communication bus 1630 communications user information and decision query and/or user input to the user service interface agent, as shown. The policy control agent communicates service settings and/or configuration information via this communications stack, as shown (illustrating such communications with a reference (B)) via the policy implementation agent layer. Various other communications (e.g., service processor and/or service controller related communications, such as service usage measure information and/or application information) are provided at various levels of this communications stack, as shown (illustrating such communications with reference (C) at the application layer and communications with reference (D) at the policy implementation agent layer). As shown, the service monitor agent B communicates with the application service interface agent and measurement point I, and the service monitor agent A communicates with the policy implementation agent layer and measurement points II and III of themodem 1. As similarly described with respect toFIGS. 30 , 31, 32, 33, 34 and 35, many of the service usage control verification embodiments disclosed herein can be applied in isolation or in combination in the context ofFIG. 36 . -
FIG. 37 is another functional diagram illustrating the device communications stack that allows for implementing traffic shaping policy, access control policy and/or service monitoring policy in accordance with some embodiments. In particular,FIG. 37 illustrates a device communications stack as similarly shown inFIG. 36 , with the difference being that the service processor subsystem networking communication stack processing is implemented on a hardware function that is separate from the application processor and the modem. For example, this approach provides security advantages with a dedicated hardware system to protect some or all of the service usage control system from tampering. For example, some or all of the service processor can be implemented on a SIM card module. As another example, some or all of the service processor can be encapsulated on a self contained hardware module that can be added to a device without the need to modify the networking communication stack software or hardware. -
FIG. 38 is a functional diagram illustrating a device service processor packet processing flow in accordance with some embodiments. In particular, both an example upstream service processor packet processing flow (device to the network) and an example downstream service processor packet processing flow (network to the device) are shown inFIG. 38 . For example, the service processor packet processing flow can be performed by the device communications stack, such as described above with respect toFIG. 29 . The various embodiments for packet processing flow depicted inFIGS. 38 through 40 are self explanatory to one of ordinary skill in the art and not all the processing steps and flow sequences are described herein. - In some embodiments, the burst size, buffer delay, acknowledgement delay and drop rate used in upstream and downstream traffic shaping are optimized with the goal of reducing access network traffic overhead, and excess capacity usage that can result from mismatches in traffic transmission parameters with the access network MAC and PHY or from excess network level packet delivery protocol re-transmissions. In some embodiments, an
application interface agent 1693 is used to literally tag or virtually tag application layer traffic so that the policy implementation agent(s) 1690 has the necessary information to implement selected traffic shaping solutions. As shown inFIG. 16 , theapplication interface agent 1693 is in communication with various applications, including aTCP application 1604, anIP application 1605, and avoice application 1602. - Referring to
FIGS. 38 through 40 , in some embodiments, the upstream traffic service policy implementation step corresponds to the traffic shaping step described herein. Referring toFIG. 38 , this step is depicted as shown as an alternate exploded view including four upstream sub-steps of apply QoS queue priority, apply traffic shaping rules, network optimized buffer/delay and remove application ID tag. An additional approach shown inFIG. 38 involves two exploded view sub-steps associated with the firewall service policy implementation step and these sub-steps are pass/block packet and pass/redirect packet. For example, the functions performed by these six sub-steps can be depicted in any number of sub-steps, the order of the steps can be appropriately performed in various different orders to provide for upstream traffic shaping within the network communication stack. For example,FIGS. 39 and 40 show the two steps of policy implementation and firewall as one step and the six exploded view sub-steps are included under the same policy implementation step and are performed in a different order than inFIG. 38 . It should also be noted that a number of embodiments are possible in which the access control, traffic control or firewall functions are moved to the application service interface layer or another layer. - Referring now to the downstream portion of
FIG. 38 , there are two steps again termed traffic service policy implementation and firewall service policy implementation in this traffic shaping, access control and firewall example. These two packet flow processing steps are depicted as shown in the exploded view as the five sub-steps of tag with flow ID, pass/block packet, apply QoS, apply traffic shaping rules and network optimized buffer, delay, and drop. As with the upstream packet processing flow, the number of sub-steps, the order of sub-steps and the location of the sub-steps in the downstream networking stack processing can be depicted in any number of sub-steps, order and/or location, and various other embodiments will be apparent to one of ordinary skill in the art, including embodiments which locate some or all of the steps in the application service interface layer or other layers as depicted inFIGS. 39 and 40 . The details of the packet flow processing design for the downstream can be somewhat more complex in certain embodiments as compared to the upstream processing in two ways. First, as described herein, in some embodiments, the packet tagging that requires application level information can require the initial portion of the packet flow burst to pass through the upstream networking communication stack until the application service interface layer can associate the packet flow with the appropriate information visible at the application level at which time the packet flow tag is communicated to the other service processor agent functions so that they can properly monitor or control the traffic associated with the flow. - Independently, another complication arises when upper layer reliable communication protocols, such as TCP, are employed in the networking stack in which the downstream transmitting end repeats the packet transmission if the receiving TCP protocol stack does not send a packet receipt acknowledge (ACK) within a certain period of time. If packets are arbitrarily delayed or dropped, then the TCP re-transmission traffic can reduce, completely eliminate or even reverse the network capacity advantage gained by reducing the average traffic speed or other transmission quality measure for one or more service activities. To solve this problem, in some embodiments, the packet traffic control parameters (e.g., downstream delay, drops, burst length, burst frequency and/or burst jitter) are optimized for TCP re-transmission efficiency so that changes in traffic control access bandwidth or speed for one or more service activities are implemented in such a manner that the TCP re-transmission delay at the network transmitting end adapts to be long enough so that wasted packet re-transmission bandwidth is reduced. In addition, and either in combination or in isolation, in some embodiments, the packet traffic control parameters (e.g., downstream delay, drops, burst length, burst frequency and/or burst jitter) can be adjusted so that the access network downstream MAC and/or PHY efficiencies are optimized.
- Numerous other embodiments for the detailed implementation of packet flow processing in both downstream and upstream will be apparent to one of ordinary skill in the art in view of the various embodiments described herein. In some embodiments, as described herein, the following are provided: (A) traffic shaping is performed in a verifiable manner, (B) traffic shaping is performed in a manner that results in improved network capacity by taking into account to some degree the manner in which the access network PHY layer and/or MAC layer responds to packet parameters (e.g. burst delay, burst drops, burst length, burst frequency and/or burst jitter), (C) traffic shaping is performed in a manner that results in improved network capacity by taking into account how the packet parameters (e.g., burst delay, burst drops, burst length, burst frequency and/or burst jitter) impact layer 3 and higher ACK protocol or other network protocol network capacity efficiencies, (D) packet shaping is performed in a manner that is aware of and optimized for the particular type of communication protocol or packets being sent (e.g., TCP packets can be dropped to slow the application rate of transfer whereas UDP packets are never dropped, because there is no re-transmission), (E) a virtual or literal packet tagging system is used in a verifiable traffic shaping service control system to provide a deeper level of service monitoring and control or to simplify the processing of the packets, and/or (F) starting with these low level packet processing, traffic control or access control building blocks one or more additional layers of higher level policy control can be added on the device or in the network to create service profiles for the service provider network that define complete services, such as ambient services and many other variations of service profile settings that each define a device or user service experience and can be associated with a billing plan. For example, the use of higher layers of service profile control to form more complete service solutions starting with these relatively simple low-level traffic control, access control or firewall processing steps or functions is also described herein.
-
FIG. 39 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments. In particular, both an example upstream service processor packet processing flow (device to the network) and an example downstream service processor packet processing flow (network to the device) are shown inFIG. 39 (e.g., of a less feature rich device service processor embodiment, such as one similar to that depicted inFIG. 32 ). -
FIG. 40 is another functional diagram illustrating the device service processor packet processing flow in accordance with some embodiments. In particular, both an example upstream service processor packet processing flow (device to the network) and an example downstream service processor packet processing flow (network to the device) are shown inFIG. 40 (e.g., of a mid=-featured embodiment of a device service processor, such as one similar to that depicted inFIG. 33 ). -
FIG. 41 provides a table summarizing various privacy levels for service history reporting in accordance with some embodiments. Many of these privacy levels are similarly described above, and the table shown inFIG. 41 is not intended to be an exhaustive summary of these privacy levels, but rather is provided as an aid in understanding these privacy levels in accordance with user privacy related embodiments described herein. For example, there are many other parameters that can be associated with privacy filtering, and as will be apparent to one of ordinary skill in the art in view of the various embodiments described herein, the unique feature of user defined or user influenced privacy filtering for service usage, service activity or CRM reports can be implemented with a variety of embodiments that are variations of those described herein. -
FIGS. 42A through 42F provide tables summarizing various service policy control commands in accordance with some embodiments. Many of these service policy control commands are similarly described above, and the tables shown inFIGS. 42A-F are not intended to be an exhaustive summary of these service policy control commands and do not include summaries of all the embodiments described herein, but rather are provided as a summary aid in understanding these service policy control commands in accordance with various embodiments described herein. - In some embodiments, QoS is employed for devices with a
service processor 115. For example, QoS can be employed in a crowded hot spot where theservice processor 115 profile has been changed from WWAN to WLAN, but the WLAN is backed up as too many users are trying to use it. Theservice processor 115 can have a hierarchical access to the hotspot at that point; or theservice processor 115 that pays less can be throttled while those that pay more are opened up; or theservice processor 115 can initiate a policy that slows down transmissions to improve trunking efficiency. -
FIGS. 43A through 43B are flow diagrams illustrating a flow diagram for a service processor authorization sequence as shown inFIG. 43A and a flow diagram for a service controller authorization sequence as shown inFIG. 43B in accordance with some embodiments. - Referring to
FIG. 43A , at 4302, the device is in an offline state. At 4304, the service processor (e.g., service processor 115) of the device collects device service processor credentials and access control integrity information. At 4306, the service processor of the device selects a best network. At 4308, the device connects to an access network. At 4310, the service processor of the device sends an authorization request to the service controller (e.g., service controller 122) and also sends the credentials and access control integrity information. At 4312, the service processor determines whether an integrity error has occurred. If so, then the service processor performs integrity error handling at 4314. Otherwise, the service processor determines whether the device is activated and/or authorized for network access at 4316. If not, then the service processor performs a device activation sequence at 4318. At 4320, the service processor performs the following: updates critical software, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, and sends stored CRM and billing information. At 4322, the device is in an online state. - Referring to
FIG. 43B , at 4332, device control is in an offline state. At 4334, the service controller (e.g., service controller 122) receives a device authorization request, verifies device service plan standing, verifies device access control integrity standing, verifies device access control integrity information, verifies service processor heartbeat, and performs various additional service processor integrity checks (e.g., as similarly described herein). At 4336, the service controller determines whether the device integrity checks have all passed. If not, then the service controller sends an integrity error to the service processor (e.g., service processor 115) at 4338. At 4340, the service controller performs integrity error handling. Otherwise (the device integrity checks have all passed), the service controller determines whether the device is activated at 4342. If not, then the service controller sends an activation message to the service processor at 4344. At 4346, the service controller performs a service activation sequence. Otherwise (the device is activated), the service controller sends an authorization at 4348. At 4350, the service controller performs the following: updates critical software on the service processor, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, sends stored CRM and billing information. At 4352, the service controller is in a device online state. -
FIGS. 44A through 44B are flow diagrams illustrating a flow diagram for a service processor activation sequence as shown inFIG. 44A and a flow diagram for a service controller activation sequence as shown inFIG. 44B in accordance with some embodiments. - Referring to
FIG. 44A , at 4402, a service processor activation sequence is initiated. At 4404, the service processor (e.g., service processor 115) of the device displays an activation site (e.g., HTTP site, WAP site or portal) to the user for the user's service activation choice. At 4406, the user selects service plan, billing information and CRM information. At 4408, the service processor sends an activation request and user billing and CRM information to, for example, the service controller. At 4410, the service processor determines whether there is an integrity error. If so, then the service processor performs integrity error handling at 4412. Otherwise, the service processor determines whether there has been a selection input error at 4414. If so, the service processor displays the selection input error to the user at 4416 and returns to the activation site/portal at 4404. Otherwise, the service processor identifies the activated service plan at 4418. At 4420, the service processor performs the following: updates critical software, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, and sends stored CRM and billing information. At 4422, the device is in an online and activated state. - Referring to
FIG. 44B , at 4432, a service controller activation sequence is initiated. At 4434, the service controller (e.g., service controller 122) receives an activation request, including user billing and CRM information, and sends such to central billing. At 4436, the service controller receives a response from central billing. At 4438, the service controller verifies the integrity of the service processor. If an integrity error is detected, then an integrity error is sent at 4440. At 4442, the service controller performs integrity error handling. At 4444, the service controller determines whether the service plan has been activated. If not, then the service controller sends a selection input error to the device at 4446 and returns to 4432. Otherwise (device has been activated), the service controller sends the service plan activation information to the device at 4448. At 4450, the service controller performs the following: updates critical software, initializes service policy and control settings, synchronizes service counters, updates service cost data, applies policy settings, applies CRM rules settings, obtains transaction identity certificate, and sends stored CRM and billing information. At 4452, the service controller is in a device online and activated state. -
FIGS. 45A through 45B are flow diagrams illustrating a flow diagram for a service processor access control sequence as shown inFIG. 45A and a flow diagram for a service controller access control sequence as shown inFIG. 45B in accordance with some embodiments. - Referring to
FIG. 45A , at 4502, the device is in an online state. At 4504, the service processor (e.g., service processor 115) of the device processes any new heartbeat messages received from the service controller (e.g., service controller 122). At 4506, the service processor updates software if necessary, updates service policy and control settings if necessary, synchronizes service counters, updates service cost data if necessary, and updates CRM rules if necessary. At 4508, the service processor performs access control integrity checks. At 4510, the service processor determines whether there are any access control integrity errors. If so, then the service processor performs integrity error handling at 4512. Otherwise, the service processor updates user service UI gauges, provides notification if necessary, and accepts input if available at 4514. At 4516, the service processor sends new service processor heartbeat messages to the heartbeat message queue. At 4518, the service processor processes any pending billing transactions. At 4520, the service processor determines if a heartbeat transmission is due, and if not, returns to 4504 for processing any received heartbeat messages. If so, at 4522, the service processor sends the new service processor heartbeat message to the service controller. - Referring to
FIG. 45B , at 4532, the device is in an online state. At 4534, the service controller (e.g., service controller 122) processes any new heartbeat messages received from the service processor. At 4536, the service controller performs access control integrity checks. At 4538, the service controller determines whether there are any access control integrity errors. If so, then the service controller performs integrity error handling at 4540. At 4542, the service controller updates the billing database, updates the CRM information, synchronizes service counters, updates cost database if needed, and synchronizes CRM rules if necessary. At 4544, the service controller processes any pending billing transactions. At 4546, the service controller sends new service processor heartbeat messages to the heartbeat message queue. At 4548, the service controller determines if a heartbeat transmission is due, and if not, returns to 4534 for processing any received heartbeat messages. If so, at 4550, the service controller sends new service processor heartbeat message to the service processor. - Open Content Distribution and Transaction System
- Referring now to FIGS. 46 and 47A-B, in another set of embodiments an open, decentralized, device based system for enabling central billing for third party electronic commerce transactions for mobile commerce is provided as shown. For example, in these embodiments, device information can be embedded in HTTP, WAP or other portal browser/network header request information that indicates a central billing option is available to a compatible third party transaction server, as further described below with respect to FIGS. 46 and 47A-B.
-
FIG. 46 is a functional diagram illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments. As shown, aservice processor 4615 of the device 100 (e.g., any mobile device capable of storing and executing the service processor 4615) includes accesscontrol integrity agent 1694,billing agent 1695,agent communication bus 1630,user interface 1697,policy control agent 1692,service monitor agent 1696,application interface agent 1693,policy implementation agent 1690, and modem router andfirewall 1655, as similarly described herein with respect to various other service processor embodiments. In some embodiments, an application 4604 (e.g., an HTML/WAP web browser) and amobile payment agent 4699 are also included in the device, such as part of theservice processor 4615 as shown. In some embodiments, theapplication 4604 is not integrated as part of theservice processor 4615, but is executing and/or stored on the device. In some embodiments, themobile payment agent 4699 includesbilling agent 1695,user interface 1697 and/orapplication interface agent 1693, and/or various other functional components/agents. As shown, theservice processor 4615 is in communication with acarrier access network 4610, which is in network communication with theInternet 120. - In some embodiments, device information can be embedded in HTTP, WAP or other portal browser/network header request information that indicates a central billing option is available to a compatible third party transaction server, such as the open content transaction partner site(s) 134. For example, the compatible transaction server can then send a signed confirmation request over a pre-assigned control socket channel to the
billing agent 1695 with thebilling agent 1695 confirming the signed confirmation request by either performing the signature check locally based on a stored and synchronized list of approved transaction servers or by passing the signed request onto abilling server 4630 for confirmation. Optionally, in another example, a triangle confirmation can be set up in which thebilling server 4630 can confirm the transaction set up with thetransaction server 134 or thetransaction server 134 can confirm the transaction set up with thebilling server 4630. Once the device confirms the compatible and approved status of thetransaction server 134, the device/transaction server pair can then optionally further exchange keys for the remainder of the transaction for enhanced security. In another example, thetransaction server 134 can also redirect the user browsing experience to one tailored to one or more of device type, service provider, device manufacturer or user. When the user selects a transaction, the transaction server sends the billing agent 1695 a transaction bill that describes the transaction and the amount. Thebilling agent 1695 can optionally confirm that the user account has sufficient credit limit to make the purchase by either confirming the stored credit limit on the device or querying thebilling server 4630. Thebilling agent 1695 then invokes thedevice UI 1697 to display the transaction description and amount and request user approval for the billing to be conducted through the central billing option. User approval can be acquired, for example, by a simple click operation or require a secure password, key and/or biometric response from the user. Upon user approval, thebilling agent 1695 generates a billing approval and sends it to thetransaction server 134, thetransaction server 134 completes the transaction and then sends a bill to thebilling agent 1695. Thebilling agent 1695 optionally sends a confirmation to thetransaction server 134 and sends the bill to thebilling server 4630. Again, optionally a triangle confirmation can be formed by the billing server sending a confirmation to thetransaction server 134, or thetransaction server 134 can send the bill to thebilling server 4630. In some embodiments, thebilling server 4630 can also communication such billed transactions to a centralprovider billing system 4623 via thecarrier access network 4610. Also, in some embodiments, an alternatelocation billing server 4632 is in communication via theInternet 120, and an alternate location centralprovider billing system 4625 is also in communication via theInternet 120. -
FIGS. 47A through 47B are transactional diagrams illustrating open, decentralized, device based mobile commerce transactions in accordance with some embodiments. Referring toFIG. 47A , thedevice application 4604 browses (e.g., based on the user submitting a browse request using a browser application) to transaction server 134 (e.g., a transaction web server, such as the open content transaction partner site 134). Thetransaction server 134 provides an offer to thedevice application 4604. Thedevice application 4604 selects a purchase (e.g., based on the user's selection input). In response, thetransaction server 134 seeks an API connection with the devicemobile payment agent 4699, which then confirms the API connection. Thetransaction server 134 requests user purchase confirmation (mediated by the devicemobile agent 4699 as shown), and the purchase is confirmed by the device application 4604 (e.g., based on the user's acknowledgement as similarly described above with respect toFIG. 46 ). Thetransaction server 134 then transmits a purchase receipt, and thedevice application 4604 confirms the receipt. Thetransaction server 134 then transmits the purchase bill to the devicemobile payment agent 4699, which then sends the purchase bill to the device billing server (e.g., billing server 4630). The transaction server also optionally sends a confirmation of the purchase bill to the device billing server for a triangle confirmation, as similarly described above with respect toFIG. 46 . The device billing server sends a copy of the purchase bill to the central provider billing system (e.g., central provider billing system 4623). - Referring now to
FIG. 47B , thedevice application 4604 browses (e.g., based on the user submitting a browse request using a browser application) to transaction server 134 (e.g., a transaction web server, such as the open content transaction partner site 134), in which the browse request includes device ID information, such as similarly described above with respect toFIG. 46 . Thetransaction server 134 establishes API contact with the devicemobile agent 4699, which then confirms contact and good standing for transactional purchases from the device. Thetransaction server 134 provides an offer to thedevice application 4604. Thedevice application 4604 selects a purchase (e.g., based on the user's selection input). Thetransaction server 134 notifies the devicemobile payment agent 4699 of the purchase description and amount, and the devicemobile payment agent 4699 then requests user purchase confirmation. The purchase is confirmed by the device application 4604 (e.g., based on the user's acknowledgement as similarly described above with respect toFIG. 46 ), and the devicemobile payment agent 4699 then transmits a purchase confirmation to thetransaction server 134. Thetransaction server 134 then transmits a purchase receipt, and thedevice application 4604 confirms the receipt. Thetransaction server 134 then transmits the purchase bill to the devicemobile payment agent 4699, which then sends the purchase bill to the device billing server (e.g., billing server 4630). The transaction server also optionally sends a confirmation of the purchase bill to the device billing server for a triangle confirmation, as similarly described above with respect toFIG. 46 . The device billing server sends the purchase bill to the central provider billing system (e.g., central provider billing system 4623). In some embodiments, the communications described above with respect toFIGS. 47A-B with the billing server and the central provider billing system are with the alternatelocation billing server 4632 and/or alternate location centralprovider billing system 4625 via theInternet 120. Similarly, in some embodiments, thetransaction servers 134 are connected to theInternet 120. - Accordingly, these transaction billing embodiments do not require centralized content storage or content and transaction exchange infrastructure. For example, the transactions can be conducted over the Internet, and the user experience and content can be tailored versions of the transaction server/content provider's normal experience and content. This approach provides for a much wider array of content and transaction partners with minimal or no need to accommodate proprietary specialized systems. Moreover, the compatibility between the device billing agent transaction system and the transaction provider server is easily established, for example, by writing specifications for the header information transmitted by the device and for the secure handshake and signed message transactions that take place between the device billing agent, the transaction server and optionally the transaction server and the billing server. Once a transaction partner shows compatibility test results and concludes a business relationship with the service provider, the service provider can place the transaction partner on the compatible and approved list and exchange security keys and/or certificates. If a common user experience is desired by the service provider across multiple transaction partners, then the experience specifications for the browser redirects can also be specified in the compatibility specification and tested before the transaction partner gains approval.
- Design and Testing for Service Control
-
FIG. 48 illustrates a network architecture including a service controller device control system and a service controller analysis and management system in accordance with some embodiments. As described herein, theRAN gateway 410 generally represents the functionality of the various specific RAN gateway functional elements shown and/or discussed herein. For example, theseRAN gateway 410 functional elements represent the gateways used to aggregate the radio access network traffic, control, charging and roaming functions and/or other functions and are shown and/or discussed herein using other terminology specific to certain industry standards, includingSGSN gateway 410 andgateways SGSN gateway 410 andRAN gateway 410, it will be appreciated that theRAN gateway 410 represents any or all of the RAN gatewayfunctional elements transport gateway 420 represents the next higher level of gateway aggregation for the transport layer that is used in many networks, and thisterm transport gateway 420 can be interchanged with any or all of thegateways terms RAN gateway 410,gateway 410,transport gateway 420 orgateway 420 are referenced herein. - While the embodiments described below with respect to
FIGS. 48 through 63 are depicted in the context of a conventional multi-tier access network, one of ordinary skill in the art will appreciate that such embodiments can also be generalized to other network topologies including the various flattened network topologies described herein. As shown, the service controller is divided into two main functions (e.g., as compared with the embodiments ofservice controller 122 depicted inFIG. 16 ): (1) a service controllerdevice control system 4825 and (2) a service controller design, policy analysis, definition, test,publishing system 4835. The service controllerdevice control system 4825 performs the device service control channel functions as previously described herein with respect to various embodiments. - The service controller design, policy analysis, definition, test,
publishing system 4835 separates out the service analysis, control policy design and publishing from the device service control channel functions. The service controller design, policy analysis, definition, test,publishing system 4835 performs a variety of functions as described below. In some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835 provides service usage statistical analysis, notification policy or procedure response analysis and/or billing policy or procedure response analysis for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. In some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835 detects, singles out and reports device service usage, notification responses or billing behavior that is outside of expected limits but may or may not be violating policy. In some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835 provides service cost and profitability analysis for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. In some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835 provides user service control policy, notification policy or billing policy statistical satisfaction analysis for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. In some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835 provides statistical take rate analysis for transaction offers and billing offers for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. - In some embodiments, the service controller design, policy analysis, definition, test,
publishing system 4835 provides service control policy definition work screens and “dry-lab” (pre-beta) testing against usage database for single devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. In some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835 provides service control policy, notification policy and/or billing policy beta testing (e.g., using beta test server 1658) in which the beta test profile is published to a subset of users or devices. In some embodiments, beta devices/users may or may not know that the service policy is being tested with them. In some embodiments, if they do know, then beta test apparatus includes offering system that provides user options to accept beta test and provide feedback in exchange for an offer (e.g., show them an offer page that comes up with their existing subscription service or ambient service—offer a free trial, a discount to something and/or reward zone points (or other incentives/rewards) if they accept the trial). In some embodiments, a beta test workstation (e.g., in communication with thebeta test server 1658, such as VSPremote workstation 4920 as shown inFIG. 49 ) allows the beta test manager to define one or more beta test service policy, notification policy and/or billing policy control profiles. In some embodiments, the beta test workstation publishes each profile to specific individual (single) devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. In some embodiments, the beta test workstation allows the beta test manager to analyze usage statistics, notification response statistics and/or billing/transaction offer response statistics for devices, users, groups of devices or groups of users and compare actual real-time usage versus beta test usage goals. In some embodiments, the beta test workstation allows the beta test manager to fine tune service, notification and/or billing/transaction policies and re-publish to observe changes to actual service usage until the service policy and/or notification control policies achieve the desired result. In some embodiments, the beta test workstation also allows the beta test manager to collect direct user feedback to a set of pre-designed user satisfaction or other questions regarding service usage. For example, questions can be presented through a pre-designed beta test portal or through a series of brief pop-ups that come up when the user initiates a particular action or at a particular time. In some embodiments, the beta test workstation also collects details of service and device usage (e.g., CRM data) that the beta test users have approved for collection. In some embodiments, the beta test workstation can decompose this data to determine if the users are using the service in the manner intended by the beta test goals. In some embodiments, the beta test workstation also allows for publishing multiple variants of the service and/or notification policy control settings and compare the service usage for each group with convenient screens with information displays (e.g., statistical usage versus time of day, usage of particular activities, billing activity, device discovery activity, user response to notification message and options, user satisfaction with a particular notification policy or billing policy or traffic control policy). In some embodiments, the screens can be designed by the beta test manager. - In some embodiments, once a service is completely tested and approved for production publication, the service
download control server 1660 has a workstation screen that allows the service manager to specify which group of devices are to receive the new service policy configuration. In some embodiments, the servicedownload control server 1660 allows the service manager to define specific individual (single) devices, groups of devices, types of devices, groups of users, classes of users, or an entire set of devices and users that subscribe to a given service. - In some embodiments, a service (e.g., a newly created or new version of an existing service) is tested and/or enhanced using a new service testing model. For example, a new service (or a new version of an existing service) is loaded onto a server for testing, the new service is (optionally) tested against existing device usage statistics, a new service control definition (e.g., implemented as
service processor 115 for publishing todevices 100 and a correspondingnew service controller 122 for the service provider, such as a central provider or an MVNO partner, and, for example, the new service processor and service controller can be implemented using the below described SDK) for the new service is developed and possibly adjusted based on the testing against existing device usage statistics, the new service control definition is then published to beta devices (e.g.,various devices 100 used for beta testing the new service), which then use the new service, service usage statistics and/or user feedback statistics are then collected (e.g., to ensure that the service is functioning properly and so that the service control definition can be tuned to ensure adequate service, user experience and for service pricing/profitability purposes), the service/service control definition is then fine tuned based on the service usage/user feedback statistics. Upon completion of the above testing and refinement of the service/service control definition, the service control definition can be published to specified groups of devices for using the new service. In some embodiments, this service control testing model for groups of devices and service partners is provided by a virtual MVNO or VSP. For example, this allows for new services to be more efficiently and more effectively developed, tested and proliferated. - In some embodiments, service history IPDRs come from within a networking component connected to the central
provider core network 110 as depicted by (e.g., real-time) service usage 118 (which as discussed elsewhere is a general purpose descriptor for a function located in one or more of the networking equipment boxes). In some embodiments, service history IPDRs are collected/aggregated (in part) from thecentral billing system 123. In some embodiments, service history IPDRs are collected/aggregated (in part) from thetransport gateways 420. In some embodiments, service history IPDRs are collected/aggregated (in part) from theRAN gateways 410. In some embodiments, service history IPDRs are collected/aggregated (in part) from the base station(s) 125 or a networking component co-located with the base station(s) 125, a networking component in thetransport network 415, a networking component in thecore network 110 or from another source. - Virtual Service Provider for Service Control
- In some embodiments, virtual service provider (VSP) capabilities include making available to a third party service partner one or more of the following: (1) device group definition, control and security, (2) provisioning definition and execution, (3) ATS activation owner, (4) service profile definitions, (5) activation and ambient service definition, (6) billing rules definition, (7) billing process and branding controls, (8) bill by account settings, (9) service usage analysis capabilities by device, sub-group or group, (10) beta test publishing capabilities by device, sub-group or group, and (11) production publishing, fine tuning and re-publishing.
-
FIG. 49 illustrates a network architecture for an open developer platform for virtual service provider (VSP) partitioning in accordance with some embodiments. As shown, the service controller design, policy analysis, definition, test,publishing system 4835 is configured so that multiple “service group owners” (e.g., the service provider for certain smart phones) or “device group owners” (e.g., eReader devices for the eReader service provider(s)) or “user group owners” (e.g., IT for Company X for their employees' corporate mobile devices), collectively referred to as the “Virtual Service Provider” (VSP), are serviced with the same service controller infrastructure and the same (or substantially similar) service processor design from virtual serviceprovider workstation server 4910 and/or virtual service provider remote workstation(s) 4920. As shown, the virtual service provider remote workstation(s) 4920 communicates with the virtual serviceprovider workstation server 4910 via VPN, leased line or secure Internet connections. The dashed lines shown inFIG. 49 are depicted to represent that, in some embodiments, the virtual serviceprovider workstation server 4910 is networked with the service controllerdevice control system 4825 and/or, in some embodiments, the service controller design, policy analysis, definition, test,publishing system 4835. Based on the discussion herein, it will be apparent to one of ordinary skill in the art that theVSP workstation server 4910 can also be networked in various embodiments withbilling system 123,AAA server 121,gateways - In some embodiments, the service controller functionality is partitioned for a VSP by setting up one or more secure workstations, secure portals, secure websites, secure remote software terminals and/or other similar techniques to allow the service managers who work for the VSP to analyze, fine tune, control or define the services they decide to publish to one or more groups of devices or groups of users that the VSP “owns,” In some embodiments, the VSP “owns” such groups by virtue of a relationship with the central provider in which the VSP is responsible for the service design and profitability. In some embodiments, the central provider receives payment from the VSP for wholesale access services. In some embodiments, the
VSP workstations - In some embodiments, the VSP manages their devices from the
VSP workstations VSP workstations VSP workstations - For example, this approach is particularly well suited for “open developer programs” offered by the central providers in which the central provider brings in VSPs who offer special value in the devices or service plans, and using this approach, neither the central provider nor the VSP needs to do as much work as would be required to set up a conventional MVNO or MVNE system, which often requires some degree of customization in the network solution, the billing solution or the device solution for each new device application and/or service application that is developed and deployed. In some embodiments, the service customization is simplified by implementing custom policy settings on the service processor and service controller, and the custom device is quickly brought onto the network using the SDK and test/certification process. In some embodiments, the VSP functionality is also offered by an entity other than the central provider. For example, an MVNE entity can develop a wholesale relationship with one or more carriers, use the service controller to create the VSP capabilities, and then offer VSP services for one network or for a group of networks. In some embodiments, the service customization is simplified by implementing custom policy settings through the VSP embodiments on the network equipment, including, in some embodiments, service aware or DPI based network equipment that has a relatively deep level of service activity control capability. For example, using the embodiments described herein, and possibly also including some of the activation and provisioning embodiments, it is possible to efficiently design and implement custom ambient service plans that are different for different types of devices, different OEMs, different VSPs, different distributors, or different user groups all using the same general infrastructure, whether the service control policy implementation is accomplished primarily (or exclusively) with networking equipment (network) based service control, primarily (or exclusively) with device based service control or with a combination of both (e.g., hybrid device and network based service control).
- As discussed herein, various VSP embodiments for performing one or more of analyzing traffic usage and defining, managing service profiles or plans, dry lab testing service profiles or plans, beta testing service profiles or plans, fine tuning service profiles or plans, publishing service profiles or plans, or other policy related settings can involve programming settings in the network equipment and/or programming settings or software on the device. For example, as discussed herein, the service processor settings are controlled by the service controller, which can be partitioned to allow groups of devices to be controlled. As another example, equipment in the network involved with network based service control, such as DPI based gateways, routers or switches, can similarly be programmed to utilize various VSP embodiments to implement that portion of the service profile (or service activity usage control) that is controlled by network level functions, and it will be appreciated that substantially all or all of the service activity control for certain embodiments can be accomplished with the network functions instead of the device. Continuing this example, just as the device service processor settings control functions of the service processor can have a group of devices that are partitioned off and placed under the control of a VSP, various VSP control embodiments can partition off a group of devices that have service usage activity controlled by the networking equipment, including, in some embodiments, sophisticated service aware DPI based service control equipment, to achieve similar objectives. It will be appreciated that the discussion herein regarding service controller design, policy analysis, test, publishing 4835, and the discussion regarding device group, user group and other VSP related embodiments, should be understood as applicable to various embodiments described in view of device based services control, control assistance and/or monitoring, or network based services control, control assistance and/or monitoring, or a combination of device based services control, control assistance and/or monitoring and network based services control, control assistance and/or monitoring. The various embodiments described herein related to service activation and provisioning also,make apparent how the programming of network equipment service control, service control assistance and/or monitoring can be implemented prior to and following activation of the device. It will also be appreciated that the VSP capabilities described herein can also be applied to those devices that have services controlled by, provided by and/or billed by the central provider, so these techniques can be applied to central provider service embodiments, MVNO embodiments and other embodiments.
- Open Development System for Access Services—SDK
- In some embodiments, an SDK is provided that allows developers, such as device manufacturers, service providers, MVNO, MVNE and/or VSPs, to develop various service processors (e.g., different versions of the service processor 115) for various devices (e.g., various types of devices 100) and corresponding service controllers (e.g., different versions of the service controller 122) for various types of services and network environments. For example, a device manufacturer can use the SDK to develop a new service processor for their new device (e.g., mobile phone, PDA, eBook reader, portable music device, computer, laptop, netbook, or any other network accessible device). The device manufacturer can also preload/preinstall their new service processor on their new devices. In this example, users of the new device would then be able to utilize the new device to access network based services using the new service processor, which communicates with the deployed new service controller, as similarly discussed herein in various embodiments. For example, the device can be preinstalled with the new service processor to provide ambient services, as similarly discussed herein in various embodiments. For example, the SDK can allow for substantially similar service processors to be installed on similar and/or different devices thereby minimizing any unnecessary differences between service processor elements for device assisted services. In some embodiments, for ambient services for a group of devices, or devices associated with a certain service provider, a set of numbers (e.g., dummy numbers) can be assigned for use for attempting access via the access network using a new device that is not yet otherwise subscribed for service. In some embodiments, the set of (dummy) numbers used for ambient access by the device can also be used for associate of the device with a service provider or a type of device (e.g., eReader or some other type of network accessible device), and upon activation, the service provider assigns a real number for the activated device (e.g., which can be provided at the time of manufacture of the device, point of sale of the device, or after the point of sale of the device, such as upon activation of the device). For example, ambient access of the device can use the device ID, SIM ID, assigned phone (real or dummy) number, and/or other information associated with the device for assigning appropriate service control and service policy/profile for the device.
- In some embodiments, the
service processor 115 is distributed as an SDK to any device that the central provider or the VSP desires to offer services with so that theservice processor 115 can be efficiently designed or adapted by the device OEM, ODM or manufacturer for operation on the service network. In some embodiments, the SDK includes either a complete set ofservice processor 115 agent software designed for and/or tested for the OS (Operating System) and processor set being used on the device, or a mature reference design for the OS and processor set being used on the device, or a less mature reference design (potentially for the same OS and/or processor set or a different OS and/or processor set being used on the device) that the OEM (Original Equipment Manufacturer) ports to the desired OS or processor set, or a basic set of example software programs that the OEM or ODM (Original Design Manufacturer) can use to develop software compatible with the service, or a set of specifications and descriptions (possibly forming an interoperability standard) of how to design the software to be compatible with the service. In some embodiments, the SDK includes a set of OEM lab test procedures and/or test criteria to ensure that the implementation of the service SDK is compatible with the service and will operate properly. In some embodiments, the SDK includes a set of network certification test procedures and/or test criteria to ensure that the implementation of the service SDK is compatible with the service and will operate properly. In some embodiments, the certification procedures are approved for testing by the OEM, the central provider, the VSP and/or a trusted third party. For example, the central provider is typically in control of the SDK and the test procedures, but others can be in control. In some embodiments, the test procedures are at least in part common across multiple central provider networks. In some embodiments, the SDK concept is extended to include one or more modem modules where one or more of the SDK embodiments described above is combined with a standard reference design or a standard hardware sales package for one or more modems so that the entire package forms a turn-key product that allows a device manufacturer, central provider, VSP or other entity bring new devices or device applications onto the central provider network possibly in combination with other networks in a manner that requires less engineering time and resources and less network certification time and resources than would be required in some designs that do not use this standard SDK plus module approach. For example, the standard SDK plus module product embodiments can be pre-certified and tested with one or more central providers to further reduce development time and expense. The standard SDK plus module embodiments can also use a multi-mode modem (e.g., modems based on a multimode CDMA, EVDO, UMTS, HSPA chipset as in the Gobi global multimode chipset product or modems based on other recently announced LTE plus HSPA chipsets, WiMax plus Wi-Fi chipsets or LTE plus EVDO chipsets) and a multi-mode connection manager agent so that the same SDK plus modem embodiment may satisfy a wide range of applications for many service providers around the world. - In some embodiments, at the time of manufacture, the device is associated with an MVNO. For example, the MVNO can provide an ambient service that provides a service provider clearing house, in which the device can access a network in ambient access mode (e.g., a wholesale MVNO connection through the access network) for purposes of selecting a service provider (e.g., a VSP, MVNO or carrier). Based on the service provider selection, the device credentials and/or service processor are reprogrammed and/or new software is downloaded/installed to activate the device with the selected service provider, as described herein for provisioning the device and the account on that service provider network (e.g., the ATS can track such activation, for example, for revenue sharing purposes, as an activation incentive fee).
- In some embodiments ATS is implemented entirely in the network as described below. At the time of manufacture or at sometime during device distribution, the device master agent programs a unique credential in the device that cannot be re-programmed or removed (or is difficult to re-program or remove) and that can be recognized and recorded by the network at the time of activation or at some other time. In this manner, even if other, possibly primary, device credentials are reprogrammed or removed, there will still be a credential that is associated with the device master agent. The ATS process can then be implemented by using a database search function to scan through the database of activated devices to form a list of devices that have been activated for the purpose of master agent reconciliation. Example credentials that can suffice are MEID, hardware MAC address, and/or serial number, that are picked up and recorded by the service provider or other service entity at time of activation or before or after activation.
- Interface Server Overlay for Billing/IPDR Feed Mediation
-
FIG. 50 illustrates a network architecture including a billing to service controller interface for accommodating minimum changes in existing central billing, AAA and/or other network components in accordance with some embodiments. As shown, thecentral billing system 123 includes a mediation, customer service and billing databases, historical usage, billing systems component 5010 and a billing to servicecontroller interface component 5020. For example, the billing to servicecontroller interface component 5020 allows for thecentral billing system 123 to efficiently communicate with the service controller (e.g., service controller device control system 4825). - In some embodiments, an interface server (e.g., the billing databases, historical usage, billing systems component 5010 and/or the billing to service controller interface component 5020) is provided that reads the IPDRs, service profile and/or service plan information stored in the billing and/or service record database(s). In some embodiments, the interface server performs these functions in a manner that is compatible with communication formats of the billing and/or service record database(s) so that little or no changes are required in the configuration, communication formats or software of the existing central billing, AAA and/or other network components. In some embodiments, the interface server (e.g., including the billing databases, historical usage, billing systems component 5010 and the billing to service controller interface component 5020) is co-located with the central billing system components as shown, or in other embodiments, the interface server is located elsewhere. For example, the interface server can be located close to or within the components that comprise the service controller or anywhere else in the network.
- In some embodiments, the interface server performs certain communication protocol translation or data format translation required to interface the information stored in the billing and/or service record database(s) to the service controller functions so that the
central billing system 123 and other existing components in the network do not need to change much (if at all) to enable the service controller and service processor to implement device based/assisted service control. In some embodiments, thecentral billing system 123 or other network components are not required to be aware of the service control functions being implemented by the service controller or service processor, because the interface server acquires the network based information needed by the service controller and/or service processor while requiring little or no specialized awareness, communication, data formatting, user interfacing, service profile processing or service plan processing on the part of existing billing, database or networking components. In this type of overlay approach, various embodiments described herein can be used to quickly upgrade the capabilities of existing networks for new devices while minimizing the required changes to the existing network that supports legacy devices. - For example, a new ambient service plan can be implemented within the
central billing system 123 that is associated with a zero or low cost billing plan and a usage limit (e.g., ambient service) that may be difficult or impossible to support in a manner that would result in high user satisfaction and a high level of control for service cost and service policy definition. Even if thecentral billing system 123 is not highly involved in the process, the zero or low cost plan can be implemented in a manner that results in high user satisfaction and a cost controlled service by using the service controller and/or service processor and the interface server to implement the ambient services access control, service usage control, user interface, service usage notification, transaction billing or bill by account functionality. For example, this approach can be implemented by reading the service plan and/or service policy settings for a device in the central billing database using the interface server, looking up the corresponding service policy, user notification policy, transaction billing policy and bill by account policy associated with the particular service profile or service plan, and then implementing the policies with the assistance of the service controller and/or service processor. Similarly, in another definition, multiple tiers of service control and user notification policies can be added to any number of new service profiles or service plans that would not otherwise be supported with thecentral billing system 123 and other network components, all with minimal or no modifications to the pre-existing network and billing system. - Another embodiment calls for receiving a standard IPDR feed from
central billing 123 or another network component just like an MVNO would. For example, the interface server function can be located in the central billing system, service processor or elsewhere in the network. This provides the IPDR records for service usage policy verification and service usage notification synchronization with little or no need to modify existing billing or network apparatus. - In some embodiments, duplicate the IPDRs are sent from the network equipment to the billing system and/or network management system that are currently used for generating service billing or are used for device management or network management. In some embodiments, duplicate records are filtered to send only those records for devices controlled by the service controller and/or service processor. For example, this approach can provide for the same level of reporting, lower level of reporting, and/or higher level of reporting as compared to the reporting required by the central billing system.
- In some embodiments, a bill-by-account billing offset is provided using the interface server. For example, bill-by-account billing offset information is informed to the billing system through an existing data feed and by updating the billing database using the interface server. In some embodiments, transaction billing is provided using the interface server. For example, transaction billing log information is provided to the billing system through an existing data feed and by updating the billing database using the interface server.
- In some embodiments, existing/new service plan choice screens are displayed to the user, a user choice or decision/input is confirmed for a selected service plan, and then the service is implemented upon confirmation of the billing system update for the new service plan. In some embodiments, the service is implemented upon the user selection of a new service plan and then retracted if not confirmed as updated by the billing system within a certain period of time. In some embodiments, the new service plan information is updated in the billing system through an existing data feed or by updating the database using the interface server.
- Integrated Service Control
-
FIG. 51 illustrates a network architecture for locating service controller device control functions with AAA and network service usage functions in accordance with some embodiments. As shown, an integrated device service control, AAA, deviceusage monitoring system 5110 is provided that integrates service controller functions (e.g., service controller devicecontrol system functions 4825 ofFIG. 48 ) with accessnetwork AAA server 121 functions and network (e.g., real-time)service usage 118 functions. -
FIG. 52 illustrates a network architecture for locating service controller device control functions in the access transport network in accordance with some embodiments. As shown, the service controllerdevice control system 4825 is located in theaccess transport network 415, or in some embodiments, in the 4G/3G/2G RAN gateways 410 (as indicated by the dashed line with the arrow), or alternatively, in the 4G/3G/2G transport gateways 420 (as indicated by the dashed line with the arrow). -
FIG. 53 illustrates a network architecture for locating service controller device control functions in the radio access network in accordance with some embodiments. As shown, the service controllerdevice control system 4825 is located in theradio access network 405, or in some embodiments, in the 4G/3G base station(s) 125 (as indicated by the dashed line with the arrow), or alternatively, in the 3G/2G base stations 125 (as indicated by the dashed line with the arrow). - Ambient Services
- In some embodiments, improved and simplified processes for provisioning a device or user for service on a central provider network, an MVNO network or a virtual service provider (VSP) on the central provider network are provided. In some embodiments, provisioning includes one or more of the following: a process or result of assigning, programming, storing or embedding into the device and/or network a set of credentials, or otherwise providing the credentials to the user; the credentials being at least in part carried on the device or with the user; and/or at least a portion of or a counterpart to the credentials being stored or recognized by the network so that the various network elements responsible for admitting the device access to the appropriate service activities do so once the device or user service is active. As an example, the credentials can include one or more of the following: phone number, device identification number, device security signature or other security credentials, device identification and/or security hardware such as a SIM, device type identifier, one or more IP addresses, one or more connection MAC addresses, any other address identifier, device service owner or VSP identifier, device OEM, device distributor or master agent, and/or any other information the network can use for admission control, authorization control, identifying the device with a service profile, identifying the device with an initial activation or ambient experience, identifying the device with a service plan or authorized set of service activity capabilities, identifying the device with a service provider or service owner, identifying the device with an OEM or master agent, identifying the device with a distributor or master agent, or identifying the device with a user group or user. In some embodiments, provisioning includes assigning, programming or embedding into the device and/or network the information to define the level of service activity, referred to as a service profile, that the device is authorized to receive. In some embodiments, provisioning also includes establishing the device settings and/or network settings to define an ambient activation experience in which the device user receives a set of services after (e.g., within a short period of time after) purchasing or otherwise obtaining or installing the device whether the device has or has not been registered and activated with the device user or device owner.
- In some embodiments, the ambient experience is the user experience that is available at the time the device is sold in the event the user has not yet signed up for a service plan. For example, the ambient experience is defined by an ambient service profile, an ambient service plan and/or the other service usage activity control policies in effect in the network, on the device, or a combination of both. For example, if the device service processor is used in large part to define the ambient service profile, then the initial provisioning and activation settings in the service processor, and possibly the service controller, can define the user service upgrade offering choices, network destination access control possibilities, traffic control policies, mobile commerce transaction capabilities (e.g., which transaction websites, WAP sites or portals the user can access to purchase information, content, music, games and/or eBooks), possibly free news or weather or other modest bandwidth Internet services that are provided free of charge to entice the user into using/upgrading the service or using the transactions or viewing advertisements, what advertisements are displayed to the user or what advertisement based websites the user is exposed to, certain applications may have access while others are blocked (e.g., Internet based text services have access but email downloads do not), or other example service capabilities. It will be apparent to one of ordinary skill in the art that allowing all of these services, and blocking other ambient user service attempts (e.g., unpaid large file size Internet downloads or uploads or movie viewing or other access that would consume bandwidth and cause the ambient service to be a potential source of losses for the service provider) is made possible by the service profile control capabilities of the service processor and/or the service controller. The bill by account embodiments, as discussed herein, in which each service activity can, for example, be separately tracked with the service monitor and other agents and server functions to produce a billing offset that allows categorization and mediation of different billing entities (accounts) provides the capability for the service provider to individually account for the costs of each ambient service element. This allows business models wherein the free access to the end user is paid for or partially paid for by one or more service provider partners who are billed for service access using the bill by account capabilities (e.g., the transaction partners pay for user access to their transaction experience and perhaps pay a revenue share for transaction billing, the advertising sponsored website partners pay for their access service share).
- While the service control capabilities of the service processor and the bill by account service cost sharing and transaction revenue sharing in some cases can create a profitable ambient business model, in other cases, the ambient services can be a potential source of losses for the service provider. Accordingly, in some embodiments, the ambient service capabilities can be modified over time to reduce service cost to the service provider or VSP based on a variety of decision factors. For example, the user can have one level of traffic control for a period of time, and if the user has not signed up for service by the end of the period, the ambient service access is reduced by changing the service control policy settings in the service processor, and the service level can be further reduced over time if the user continues to not sign up for service or the user does not create much transaction revenue. As another example, the recursive throttling algorithms discussed herein can be utilized to one or more of the service activities offered in ambient service mode so that the user experiences what full speed service is like, and if the user continues consuming appreciable bandwidth with the service activity, then the activity is throttled back to reduce costs. In these examples, the service processor or service controller can issue the user a notification explaining that their service is currently free so their usage is being throttled, and if they desire to receive better service, service plan upgrade offers can be delivered to the UI. It will now be apparent to one of ordinary skill in the art that the various ambient service parameters, including the provisioning and activation processes used to create the ambient service activation, can also be managed by the VSP apparatus and processes described herein. For example, this allows the same service controllers and service processor solutions to be used to define a wide range of ambient experiences for various device groups or user groups that are controlled by different VSPs.
- Similarly, rather than controlling the ambient service profile settings using the VSP functions to control the service controller, service processor, provisioning and activation settings, other embodiments call for the ambient service profile settings to be controlled by the network based service activity control equipment as similarly discussed herein. Depending on the level of service control and service monitoring sophistication (e.g., highly advanced DPI or service aware techniques), some, much, most or all of the above described ambient services functionality can be implemented using network based service controls and the VSP management and control embodiments described herein.
- In some embodiments, a device is suspended based on inactivity, or the device is placed in a suspended service state or suspended account state, so that the network does not get bogged down with a significant number of devices and credentials that are inactive. For example, this can also result in a portion of the device credentials being assigned back to an available pool rather than reserved for that particular device (e.g., phone numbers if phone numbers are scarce). The device account and/or activation state can be re-activated when the device comes back online. For example, the suspend state can be a simple suspension of services without changing the account status, in which case the re-activation process can be automatically completed as a subset or entire set of the activation sequence that occurs when the device is initially used as described herein. The suspend state can also involve changing the account status to inactive, in which case the re-activation process can automatically reconfigure the account status back to an active state when the device re-accesses the network. For example, the suspend state can involve de-assigning or possibly re-claiming a portion of the device credentials. If a portion of the credentials are de-assigned, then when the device re-accesses the network credentials can be automatically re-assigned as described in various embodiments described herein.
- Network Based Service Monitoring, Notification and Control
- In some embodiments, as described herein, it is desirable to implement some or all of the deep service usage monitoring, service control or control assistance, or service notification or notification assistance associated with a service profile in network apparatus rather than in the device, or to implement some of the deep service monitoring, control, control assistance, notification or notification assistance in the device and others in the network. This is the case, for example, in a mixed network in which some devices have some, or at least one, or all of the service processor capabilities discussed herein, but other devices do not have as much or any of the service processor capabilities. Another example is for networks or devices that do not have any service processor capabilities or where it is desirable to do all of the service monitoring, control and notification in the network rather than the device. As described below,
FIGS. 54 through 63 depict various embodiments for combinations of device based service monitoring, control or control assistance, usage notification or usage notification assistance and/or network based service monitoring, control or control assistance, usage notification or usage notification assistance. -
FIG. 54 illustrates a network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments. As shown, an integrated device service control, deviceusage monitoring system 5410 is provided that integrates service controller functions including a deep packet control (DPC)policy implementation function 5402 with accessnetwork AAA server 121 functions and network real-time service usage 118 functions. In the following discussion, it is understood that theAAA server 121 function can be re-located to another point in the network or network equipment partitioning with no loss in generality. It is also understood that many of the functional partitions described for the various embodiments within integrated device service control, deviceusage monitoring system 5410 can be re-drawn with no loss in applicability, function or generality. Finally, it is understood that one or more of the functional elements described within the integrated device service control, deviceusage monitoring system 5410 can be removed for simplified embodiments and that not all the functionality described herein is necessary in some embodiments. - In some embodiments, the integrated device service control, device
usage monitoring system 5410 provides for network based service monitoring or control that satisfies various network neutrality and/or privacy requirements based on indication(s) received from the device or user (e.g., user input provided using the device UI using theservice processor 115; user input provided through another website, WAP site or portal; or user input provided through the service contract where the user agrees to the monitoring and/or service control levels) and network based service control using aDPI service monitor 5412 and/or theDPC policy implementation 5402. - In some embodiments, the integrated device service control, device
usage monitoring system 5410 provides for network based service monitoring or service control that satisfies various privacy requirements using indication(s) received from the device or user (e.g., user input provided using the device UI using theservice processor 115; user input provided through another website, WAP site or portal; or user input provided through the service contract where the user agrees to the monitoring and/or service control levels) and network based DPI service usage monitoring or DPC policy implementation using theDPI service monitor 5412 orDPC policy implementation 5402 as described below. In some embodiments, theDPI service monitor 5412 and/orDPC policy implementation 5402 include a secure database for storing service monitoring and CRM information for each device/device user. In some embodiments, theDPI service monitor 5412 and/orDPC policy implementation 5402 can be integrated with the integrated device service control, device usage monitoring system 5410 (as shown) or provided within a separate router, server, and/or software/hardware implemented function that is in secure communication with the integrated device service control, deviceusage monitoring system 5410 and/or other network elements based on the network architecture. In some embodiments, a secure data store, such as a secure database, is not integrated with theDPI service monitor 5412 orDPC policy implementation 5402 but is in secure communication with theDPI service monitor 5412 orDPC policy implementation 5402, the integrated device service control, deviceusage monitoring system 5410 and/or other network elements depending on the architecture (e.g., a billing server or any other network element). In some embodiments, the user selects limits and/or restrictions on who can access remotely stored service usage history and/or other CRM/privacy related data (e.g., CRM/privacy gatekeeper settings), and, for example, other network elements and/or network administrators access to such data can be limited and/or restricted accordingly. For example, access to such stored service monitoring and CRM information can require certain security credentials and/or using various other well known secure data storage techniques, such as the various secure storage techniques described herein. - In some embodiments, the secure database possessing user service usage information that is considered sensitive and has not been approved for distribution by the user can be made unavailable to the credentials possessed by network managers or network functions except, for example, for emergency service situations of government mandated monitoring needs where special credentials are brought out of secure storage that are not normally available. In some embodiments, rather than the user selecting limits, a certain set of restrictions are assumed unless the user selects information filtering settings that allow more information to be shared with the network functions, network administrators or service provider partners. In some embodiments, the information is filtered to remove information thought to be sensitive but still transmits service usage information needed for monitoring network services or other important parameters. For example, the website destinations a user is visiting can be classified with generic identifiers that are not decodable or the individual website information can be completely removed. Many other examples will be apparent to one of ordinary skill in the art.
- For example, the stored service monitoring and CRM information can also be organized into groups to define group CRM profiles to store service monitoring information for every user indexed by the user credentials (e.g., such groups can also be used for various VSP related functions, as described herein). The DPI service monitor 5412 or
DPC policy implementation 5402 also uses the secure storage to store service monitoring information for each user indexed by the user credentials or another aspect of the device identifier or address assignment (e.g., IP address or MAC address). In some embodiments, a CRM information manager (e.g., a supervisor program executing on the integrated device service control, device usage monitoring system 5410) communicates with the other network functions and provides filtered service usage and CRM information according to CRM filtering rules for each user or for groups of users. In some embodiments, the filtered CRM data can be made available using secure communications with other networking equipment by the integrated device service control,usage monitoring system 5410. In some embodiments, the filter settings for some users allow more information to be shared from the secure service usage information than others due to the differences in user preference settings and/or service plan agreements. - In some embodiments, user privacy preference information is used to determine the privacy filter settings, which are securely implemented by the integrated device service control, device
usage monitoring system 5410. For example, service CRM filter settings can be received at the time of service contract sign up (e.g., service plan selection) and/or allow the user to log into service preferences web page to change settings (e.g., without involving any interaction with local software on the device). As another example, software on the device (e.g., including the service processor 115) can be used for selecting user CRM/privacy preferences, which are securely communicated to the integrated device service control, device usage monitoring system 5410 (e.g., the device can include credentials that can be verified to allow for selection/modification of CRM/privacy preferences or other user based preferences securely maintained in a network server, such as the integrated device service control, deviceusage monitoring system 5410 or another network element, such as shown in various other embodiments described herein). In these examples, the filtered CRM data is available from the integrated device service control, deviceusage monitoring system 5410 for other network components over a secure or open communication link. In another example, user CRM/privacy preferences are input using a web server hosted by the integrated device service control, deviceusage monitoring system 5410 or thecentral billing system 123. In another example, software on the device (e.g., including the service processor 115) can be used for securely communicating user preference decisions to an intermediate server that acts as a device manager and intermediate server for devices or device groups and the integrated device service control, deviceusage monitoring system 5410. - In some embodiments, the integrated device service control, device
usage monitoring system 5410 provides for network based service control as described below. In some embodiments and similar to the above described network based CRM filtering embodiments, the DPI service monitor 5412 orDPC policy implementation 5402 includes secure storage (e.g., a secure database) for storing service monitoring information (e.g., based on user selections/preferences), and theDPC policy implementation 5402 performs traffic shaping/throttling algorithms for each user based on the stored service monitoring information fromDPI service monitor 5412. For example, network based DPI traffic inspection by the DPI service monitor 5412 can use the secure storage to save service monitoring information for each user indexed by the user credentials or other parameters, such as IP address or other network tag. As another example, theDPC policy implementation 5402, for example, which can be supervised bypolicy management server 1652 as described herein with respect to various other embodiments, can implement service usage history statistical analysis inside the secure storage and maintain a service usage history analysis for each device/user and/or perform various traffic shaping and/or throttling algorithms based on various device, user selected and/or service plan related settings (e.g., for network neutrality purposes) allowing for various higher level service usage goals for one or more users, as similarly described herein with respect to various device based service usage monitoring embodiments (e.g., except for certain encrypted network traffic flows or application related flows for which traffic control generally needs information from the application level and/or content specific traffic control). - In some embodiments, input is collected on how to implement service control (e.g., from the user of the device). For example, such input can be determined based on one or more of the following: a service plan choice for the device; input provided by a user via a website (e.g., web based portal) for indicating changes to service control policies, as similarly described above; input provided by a user via the device (e.g., including the service processor 115), which securely communicates the input to the
DPC policy implementation 5402, for example, which can be supervised by thepolicy management server 1652; and input provided by a user via the device (e.g., including the service processor 115), which securely communicates the input to an intermediate server for theDPC policy implementation 5402, as similarly described above. In some embodiments, such service control is based on various algorithms as described herein that identify the heaviest usage service activities and recursively control the speed for those activities while leaving certain others unaffected, and in a manner that is specified or selected by the user to ensure network neutrality. In some embodiments, the user is offered a choice for controlling service usage and/or selects an algorithm that controls all activities equally/neutrally (e.g., based on selected user preferences). For example, by implementing service control algorithms that are network neutral (e.g., throttling all activities equally or throttling the highest usage algorithms without singling out certain activities for throttling unless they satisfy certain network neutral usage history or usage statistics criteria), or that are approved, selected or otherwise specified by the user, network neutral traffic control or service usage control can be maintained. - In some embodiments, the
DPI service monitor 5412, possibly in conjunction with theservice usage notification 5420 and/orservice history server 1650, provides service usage/service cost (e.g., a real-time service usage counter) related notifications to the device based on user preferences, as similarly described above with respect to various device based service usage/service related notification embodiments. For example, theDPI service monitor 5412, for example, in conjunction with theservice usage notification 5420 and/orservice history server 1650, can perform service usage/service related notification algorithms based on one or more of the following: service plans, device settings, and/or user selected preferences (e.g., such notification messages can be securely communicated to the device and/or to the device via an intermediate server). For example, the policies that govern how the user is notified of service usage or service cost can be determined by thepolicy management server 1652 and/or theservice usage notification 5420. As another example, user acknowledgements of important notification messages and/or user choices related to important service usage decisions can be requested, as similarly discussed above with respect to device based service usage/control embodiments, which can then be communicated to thecentral billing system 123 as confirmation for any such important notification messages (e.g., related to service usage overage charges and/or confirmation of service upgrades). In some embodiments, various other service usage algorithms related to service usage and/or service cost forward projections described herein with respect device based service usage forward projection embodiments are performed in the network, such as by the integrated device service control, deviceusage monitoring system 5410, and such forward projections can then be communicated to each respective device as service usage notification messages (e.g., using a push based approach (initiated in the network) and/or pull based approach (initiated by a request from the device)). For example, these embodiments for projected service usage methods, as described herein, can be helpful for determining when the user is using services in a manner that will cause the user to run over a service limit so that the user can be notified, or the service can be controlled or throttled if the user has selected a control or throttling option. - In some embodiments, one or more intermediate servers are provided for workload balancing and/or off-loading the integrated device service control, device
usage monitoring system 5410 and perform one or more of the functions described above with respect to various embodiments of the integrated device service control, deviceusage monitoring system 5410. In some embodiments, service plans, device settings, and/or user selected preferences are used to associate each device/user with a preprogrammed profile to more efficiently associate such devices/users with their selected service plans, device settings, and/or user preferences. For example, the process of setting a service profile for a given device can be determined by assigning the device to a service flow that has the pre-defined service profile and is shared with other devices within the integrated device service control, deviceusage monitoring system 5410 rather than individually processing the service flow manipulations for each device. In some embodiments, the act of provisioning and activating a service profile for a given devices involves setting up the service flow definition and identifier within the integrated device service control, device usage monitoring system 5410 (if it is not already set up) and then assigning the routing of the device credentials to that service flow identifier. User preferences can, for example, be accounted for by assigning the device service flow to one of several pre-defined profiles based on user preferences that are all supported under the same service plan. For example, one service flow profile can call for service usage notification but no control under the same service plan as another service flow profile that calls for less notification but active service usage control to maintain user costs to a monthly post-pay limit. - In some embodiments, the bill by account function is implemented in the context of the integrated device service control, device
usage monitoring system 5410 or other network based system embodiments described herein. For example, theDPI service monitor 5412, in some cases in conjunction withservice history server 1650, can operate in conjunction with bill by account policy settings stored in thebilling event server 1662 so that service activities are divided into the account classifications defined by the service profile settings. The bill by account feeds can then be sent to the billing system or to an intermediate billing event aggregation server that collects this type of deep packet inspection generated information from one or more integrated device service control, deviceusage monitoring system 5410 units to aggregate and format the information in a manner that may be used by thecentral billing system 123. In some embodiments, the bill by account information collected in a network box like the integrated device service control, deviceusage monitoring system 5410 is augmented by bill by account information collected on the device as described herein, and any intermediate server that can be used to aggregate and format these bill by account feeds for the central billing system deals with both types of data, from the network and from the devices. - As shown in
FIG. 54 , in some embodiments, integrated device service control, deviceusage monitoring system 5410 includes the servicecontrol server link 1638, which, for example, can be used as described above (e.g., with respect toFIG. 16 and other embodiments described herein) to communicate withdevice service processors 115. In some embodiments,billing server 1662 within integrated device service control, deviceusage monitoring system 5410 detects service usage events reported byDPI service monitor 5412, in some cases in conjunction withservice history server 1650, generates a billing event that can be recorded or transmitted to thecentral billing system 123. In some embodiments,billing server 1662 receives information fromdevice billing agent 1695 and/or deviceservice monitor agent 1696 and transmits the device service usage billing events to thecentral billing system 123. In some embodiments, certain billing events that are advantageously collected in the network (e.g., DPI service monitor. 5412 and/or billing event server 1662) are combined with certain billing events that are advantageously collected on the device (e.g.,service monitor agent 1696 and/or billing agent 1695), and both sources of billing information are transmitted to thebilling system 123. Similarly, in some embodiments, certain service usage information is collected with serviceusage monitor agent 1696, and that information is combined with service usage information collected fromDPI service monitor 5412 and/orservice history server 1650 and/orservice usage 118. In some embodiments, certain service aspects are controlled using network basedDPC policy implementation 5402, in some cases in conjunction with or supervised by network basedpolicy management server 1652, and other service aspects are controlled using device basedpolicy implementation agent 1690, in some cases in conjunction with or supervised bypolicy control agent 1692. As will now be apparent to one of ordinary skill in the art in view of the numerous embodiments described herein, many hybrid approaches to service usage monitoring, service control, service notification or service billing can be accomplished with some aspects of the policy, notification, control, monitoring or billing being implemented/performed on the device apparatus described herein and others implemented/performed on the network apparatus described herein. The presence of accesscontrol integrity server 1662 and many other service control verification embodiments described herein make it apparent that the integrated device service control, deviceusage monitoring system 5410 embodiments also provide for affirmative verification of whatever functions are implemented on the device. It will also be apparent that all of the above combinations of device and network functions, and many others, can be accomplished in ways that are network neutral and/or protect user privacy preferences by implementing the service control algorithms in a network neutral manner and/or receiving user preference input on how to implement service control, and by maintaining service usage and CRM information security and filtering on both thedevice 100 and the network based integrated device service control, deviceusage monitoring system 5410. - In some embodiments, the integrated device service control, device
usage monitoring system 5410 facilitates or plays a part in automated provisioning and activation of the devices as similarly described above with respect to various device based automated provisioning and activation embodiments. In some embodiments, theactivation server 160 is integrated into or partially integrated into device service control, deviceusage monitoring system 5410. - In some embodiments, the integrated device service control, device
usage monitoring system 5410 facilitates ambient services as similarly described above with respect to various device based ambient services embodiments. - In some embodiments, the integrated device service control, device
usage monitoring system 5410 facilitates VSP and ODI solutions as similarly described above with respect to various device based VSP and ODI embodiments. - Various other network architectures for network based service control including deep packet inspection functions can similarly be used as will be apparent to one of ordinary skill in the art in view of the various embodiments described herein.
-
FIG. 55 illustrates another network architecture for locating service controller device control functions with AAA and network service usage including deep packet inspection functions in accordance with some embodiments. As shown, theservice processor 115 is not present on thedevices 100, and the integrated device service control, deviceusage monitoring system 5510 performs all service monitoring, service control, billing, and notification functions. -
FIG. 56 illustrates a 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments. As shown, a 4G/3G/2G DPI/DPC enabled gateway 5610 (e.g., implemented in eithergateway 420 orgateway 410 or a combination of both) where the conventional service gateway functions 5616 (e.g., routing, switching, protocol translation/tunneling, charging data function (CDF), charging gateway function (GCF), mobility management, and/or suspend/resume) are combined with one or more of the following embodiments and integrated into one or a combination of the service gateways (e.g., RAN and/or transport gateways):DPI service monitor 5412,service history server 1650,device usage 118,DPC policy implementation 5402,policy management server 1652,user notification 5618,billing event server 1662, accesscontrol integrity server 1654, servicecontrol service link 1638, data plane I/O 5612 (e.g., used to represent the I/O port(s) for the gateway), and/or DPI/DPC gateway control plane link 5622 (e.g., used to represent the control plane network channel connecting the above elements to other network equipment and in communication with gateway control communication 5620). The packet processing architecture shown in this figure calls for a multi-point to multi-point backplane bus scheme, but it will apparent that other data path configurations are possible including serial. As will also be apparent, the above described configuration can also be applied to either thetransport gateway 420 and/or theRAN gateway 410. As mentioned above, it is possible to maintain a secure storage on the 4G/3G/2G DPI/DPC gateway - In some embodiments, the bill by account function is implemented in the context of the 4G/3G/2G DPI/
DPC gateway 5610 embodiment or other network based system embodiments described herein. For example, the bill by account information can be completely derived from the network box (e.g., 4G/3G/2G DPI/DPC gateway 5610) without assistance from device based service monitoring or billing capabilities, or none may exist on the device. In this example, theDPI service monitor 5412, in some cases in conjunction withservice history server 1650, can operate in conjunction with bill by account policy settings stored in thebilling event server 1662 so that service activities are divided into the account classifications defined by the service profile settings. The bill by account feeds can then be sent to the billing system or to an intermediate billing event aggregation server that collects this type of deep packet inspection generated information from one or 4G/3G/2G DPI/DPC gateway 5610 units to aggregate and format the information in a manner that can be used by thecentral billing system 123. In some embodiments, the bill by account information collected in a network box, such as the 4G/3G/2G DPI/DPC gateway 5610, is augmented, refined or otherwise added to by bill by account information collected on the device as described herein and any intermediate server that can be used to aggregate and format these bill by account feeds for the central billing system deals with both types of data, from the network and from the devices. -
FIG. 57 illustrates a network architecture including theVSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways VSP workstation server 4910 is in communication with the 4G/3G/2G DPI/DPC gateways 410 and/or 420, the Service Controller Design, Policy Analysis, Test,Publishing System 4835, and/or other networking elements including possibly thecentral billing system 123, the mobile wireless center 132 (HLR) and/or theAAA server 121 for the purpose of provisioning and/or controlling settings in the 4G/3G/2G DPI/DPC gateways 410 and/or 420, themobile wireless center 132 and possibly other equipment for the purpose of implementing a portion of the VSP open partner functionality discussed herein. InFIG. 57 , the 4G/3G/2G DPI/DPC gateway 5610 functionality as shown inFIG. 56 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 as similarly described above. For example, the VSP functionality can also be used to set higher level policies associated with the 4G/3G/2G DPI/DPC gateway DPC gateway DPC gateway VSP workstation server 4910 embodiments. -
FIG. 58 illustrates another 4G/3G/2G DPI/DPC enabled gateway in accordance with some embodiments. As shown, a 4G/3G/2G DPI/DPC gateway 5810 (e.g., implemented in eithergateway 420 and/or gateway 410) is provided in which the service processor connection (e.g., via servicecontrol server link 1638 as shown inFIG. 56 ) is not present so that all service monitoring, control, billing event collection and transmission, and notification are performed by the 4G/3G/2G DPI/DPC gateway 5610 (e.g.,gateways 410 and/or 420). -
FIG. 59 illustrates another network architecture including theVSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways AAA 121 and themobile wireless center 132 in accordance with some embodiments. As shown,FIG. 59 provides a network diagram corresponding toFIG. 58 , with similar functionality to the embodiment shown inFIG. 57 , in which theservice processors 115 are not present on thedevices 100. InFIG. 59 , the 4G/3G/2G DPI/DPC gateway 5810 functionality as shown inFIG. 58 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420 as similarly described above. -
FIG. 60 illustrates a 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments. In some embodiments, enhanced network based service monitoring, control, billing and notification as discussed above is implemented using a 4G/3G/2G DPI/DPC enabledgateway 6010 and service controllerdevice control system 6025 as shown. In some embodiments, the functions shown in the figure to be inside of the service controllerdevice control system 6025 have been moved from the 4G/3G/2G DPI/DPC gateway 5610 ofFIG. 56 (e.g., or fromgateways 410 and/or 420) so that they reside in a separate server embodiment or other network equipment function separate from the 4G/3G/2G DPI/DPC gateway 6010. For example, this architecture can be used when the network equipment manufacturer desires to separate these functions or has an existing product that it is desirable to upgrade by adding a separate box. As another example, this architecture can be used when the 4G/3G/2G DPI/DPC gateway 6010 is not capable of keeping up with large numbers of individual user profiles so it is desirable to go to a scalable server configuration in which load balancing can be applied with a potentially more flexible programming environment for implementing service policy management functions, statistical service history analysis algorithms, service usage projection, and/or service control (or throttling) algorithms. In some embodiments, a secure storage is provided on the 4G/3G/2G DPI/DPC gateway 6010 and/or the service controllerdevice control system 6025 that requires secure credentials to get into so that, for example, user privacy can be protected and service usage information or CRM information can be filtered according to user preferences prior to sending to another network function or network manager, and the same allowances can also be applied, for example, for emergency or government monitoring purposes. For example, network neutrality can also be maintained in this configuration by maintaining network neutrality in the service control algorithm construction and/or soliciting user input on how to control service usage just as discussed above for other network service control implementations or as discussed in the device based service control descriptions. -
FIG. 61 illustrates another network architecture including theVSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways AAA 121 andmobile wireless center 132 in accordance with some embodiments. InFIG. 61 , the 4G/3G/2G DPI/DPC gateway 6010 functionality as shown inFIG. 60 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420, as similarly described above, and which are in communication with the service controllerdevice control system 6025 as shown. -
FIG. 62 illustrates another 4G/3G/2G DPI/DPC enabled gateway and service controller device control system in accordance with some embodiments. As shown, the capability to communicate with theservice processor 115 has been removed so that all service monitoring, control, billing event collection and transmission, and notification are performed by the 4G/3G/2G DPI/DPC gateways 6210 (e.g., implemented ingateways 410 and/or 420) in conjunction with the service controllerdevice control system 6225 without assistance from theservice processors 115. -
FIG. 63 illustrates another network architecture including theVSP workstation server 4910 in communication with the 4G/3G/2G DPI/DPC gateways AAA 121 andmobile wireless center 132 in accordance with some embodiments. InFIG. 61 , the 4G/3G/2G DPI/DPC gateway 6210 functionality as shown inFIG. 62 is implemented in the 4G/3G/2G DPI/DPC RAN gateway 410 and/or the 4G/3G/2G DPI/DPC transport gateway 420, as similarly described above, and which are in communication with the service controllerdevice control system 6225 as shown. - As will be apparent to one of ordinary skill in the art, the above described embodiments can be extended to include some or all of the functions depicted in the 4G/3G/2G DPI/DPC service gateways of
FIG. 56 in the base station orbase station controller 125. - Provisioning and Activation
- In some embodiments, automated provisioning and activation includes automation of one or more of the following functions: (1) programming device credentials or partial credentials and recording them in a database (or providing same when they are programmed into the device), (2) associating these credentials with the proper provisioning and/or activation actions to be taken on the device and in the network, (3) directing the device to the proper activation function (e.g., activation server) sequence when it attempts to connect to the network, (4) completing provisioning of the device, (5) programming the AAA, billing system, gateways, mobile wireless center and other network equipment to the proper initial device service control settings, and (6) establishing a service account for the device.
- In some embodiments, improved processes for activating service for a device or user with a network service provided by a central provider network, an MVNO network or a VSP on the central provider network are provided. In some embodiments, activation includes one or more of the following: a process or result of associating a service account with device or user credentials; with the service account potentially further being associated with a service profile defining the service activities that the device is authorized to access; creating or updating a service usage or billing record and associating it with the service account to create a service plan; and/or initiating service to the device or user in which the network equipment allows access to the appropriate level of service activities. In some embodiments, VSP embodiments include the provisioning and activation apparatus embodiments of any or all forms.
- In conventional mobile device provisioning systems, the provisioning and activation process required to create a user service account and enable the device to access the desired level of service activities can limit mass market, low cost or user friendly applications of the device or service, because the process can often be cumbersome, time consuming and/or expensive for the service provider, service owner, master agent (service distributor), MVNO, VSP and/or user. Accordingly, the various embodiments for provisioning and activation described herein simplify the provisioning and activation process for mobile devices. In some embodiments, provisioning and activation for the device and/or the network accommodates a wide variety of device types and service profile types, with the capability to perform the provisioning and activation at a number of points in the manufacturing, distribution, sales and usage progression for the device, and the ability to either pre-activate before first device use or very quickly activate during first device use (or during some later use of the device).
- In some embodiments, as described herein, the term provisioning generally refers to those actions/processes associated with programming the device with credentials or other device settings or software installations used to later activate the device, as well as, in some embodiments, creating database entries and other credential associations in the network so that the network and/or device have the information used to recognize the device or credentials and implement the service policies in the service profile and/or service plan once the service profile and/or service plan are activated. In some embodiments, as described herein, the term activation generally refers to the process of creating or selecting the service plan and/or service profile, programming the settings that are used in each (e.g., required) network function and/or each (e.g., required) device function so that the system can properly associate the device credentials with the appropriate service activity policies, and then admitting the device onto the network. The term activation can also refer in some embodiments to the creation of a user or device service account, in some cases, with user or device owner information or billing information. In some embodiments, the process of provisioning amounts to assigning credentials to the device and programming a portion or all of the credentials on the device, entering a portion or all of the credentials in the various necessary network equipment databases so that the network components are capable of identifying the device and associating it with the network based portion of the admission, traffic processing, service monitoring, billing, service limits and other policies that are eventually defined by the service profile and service plan.
- Further examples of the network based service profile policies include network access level, traffic routing, service monitoring, service limits and actions taken upon reaching service limits. Once the service profile is created and activated during the activation process, the device credentials and the associated service profile are communicated throughout the necessary network elements so that each element can implement its part of the network portion of the service profile policies. This process of propagating the service profile settings to all the required network equipment components is a portion of what is referred to herein as activation in accordance with some embodiments. In some embodiments, the activation process includes associating the credentials with the proper service plan and/or service profile, and possibly completing the process of programming the device functions and/or network functions so that the device can be admitted to the appropriate level of network services. In some embodiments, activation also includes the service processor software settings, configurations or installs for each function or agent in the service processor to implement its part of the service profile, service plan, service billing or transaction billing policies. In some embodiments, activation also includes the creation of entries in the various service account databases and/or billing databases to create a user account or device owner account for the purpose of managing the user choices for service plan and other account information storage and management aspects, such as maintaining status information, maintaining the central service profile configuration, conducting reconciliation and billing exchanges, service usage history, and/or account history.
- In some embodiments, the term credentials generally refers to the set of information parameters that the network and/or device uses (e.g., requires) to admit the device onto the network and associate it with the appropriate service profile and/or service plan. For example, the credentials can include one or more of the following: phone number, device ID, hardware security device ID, security signatures, IP or MAC address, signature algorithms, passwords, or other secure authorization processes, service provider, OEM, master agent (service distributor), device distributor, VSP, service processor settings or version, or other information used/required by the network to authorize network admission or activate service. In some embodiments, at least some of the credentials are unique to the device, and, in some embodiments, groups of devices share one or more aspects of the credentials. In some embodiments, the term permanent credentials generally refers to the set of credentials that include at least a subset that are intended to be assigned to a device or user on a permanent basis. In some embodiments, the term temporary credentials generally refers to the set of credentials that include at least a subset that are intended to be assigned to a device or user on a temporary basis. In some embodiments, temporary credentials are eventually replaced by permanent credentials. In some embodiments, at least some elements in the temporary credentials (e.g., phone number and/or access or authorization security credential) are used for more than one device. In some embodiments, the temporary credentials are recycled from one or more devices and used for one or more other devices, for example, when they remain unused for a period of time or when they are replaced with permanent credentials on one or more devices. It should not be inferred from the term permanent credentials that permanent credentials are never recycled, for example, when the user discontinues service or use of the credentials. Also, the term temporary credentials does not imply that temporary credentials are always temporary. In some embodiments, partial credentials or pre-activation credentials generally refer to a subset of credentials that are to gain access to limited network services for the purpose of provisioning of credentials and/or activation of a service plan or service profile. For example, prior to a phone number being assigned, a device can gain access to a limited set of network server destinations in which embedded information contained in the device (e.g., the partial credentials) is provided to the server, the server associates that information with the proper additional credentials (including the phone number) to assign to the device and/or associates the information with the proper service profile to activate service. In this example, partial credentials can include device type, OEM, service provider, VSP, device identification number, SIM, service processor configuration or some other information used by the server to determine what the credentials should be and the proper service profile.
- In some embodiments, a permanent service account generally refers to the service account that is permanently associated with the user and/or device. For example, this account includes an association with the device or user credentials, user information or billing information, service profile, billing profile, network authorization status and other aspects that define the device or user service policies and billing policies. In some embodiments, the term temporary service account generally refers to a service account that is temporarily set up and associated with the device before some or all of the required permanent account information is available or entered for a device or user. For example, this account can be set up with an association with an actual user, or can be set up with a mock user or unassigned user association so that the network and billing system can recognize the credentials, authenticate the device, admit the device, provide the proper level of service activity control according to the service profile associated with the temporary service account, or collect the service activity usage information for various network and billing system accounting needs before actual user information or billing information has been entered into the network systems. For example, a temporary service account can make it possible or easier to use existing billing systems or other network systems to provide simplified provisioning, simplified activation or ambient services. A temporary service account can also become a permanent service account by replacing mock user or unassigned user information with actual user information, or a temporary service account may need to be replaced by a permanent service account when actual user information needs to be entered into the network systems, possibly including the billing or service profile databases.
- In some embodiments, temporary or permanent device credentials and other information used/required for provisioning the device are generated with apparatus located at the manufacturer or in the distribution channel as discussed below. In some embodiments, the apparatus includes a local onsite server that typically shares some aspects of the provisioning information (e.g., phone number, phone number range, MEID or MEID range, SIM number or SIM number range, IP address or IP address range, MAC address or MAC address range, other secure device credential elements) with a network provisioning database. In some embodiments, the apparatus includes a server terminal, and the aforementioned portion of the credentials is generated by the network and shared with the local provisioning apparatus. In some embodiments, as will be discussed below, the provisioning credentials are in part generated in the network and shared with the device while it is connected online to an activation server (e.g., activation server 160) that is connected to the access network. Similarly, there can be activation servers connected to apparatus in the manufacturing or distribution channel that service device activation, or over the air or over the network apparatus connected to an activation server, which in turn connects to the device, can be used to accomplish activation programming of the network and device as further discussed below.
- In some embodiments, when a device is provisioned and entered into the network provisioning database, it is associated with the automatic provisioning and/or activation sequence the device is intended to go through once it connects to the network or to the apparatus that will complete the process. In some embodiments, one or more device parameters (e.g., service owner, device type, OEM, plan type, IP address, security credential and/or software version) are used to determine what the appropriate network provisioning steps and/or settings are for completing the provisioning and/or activation process, and this association information is stored in the network provisioning database for propagation of the provisioning profiles or activation profiles to the various network equipment elements. In some embodiments, the network provisioning database is provided (e.g., in the network) that associates the pre-activation provisioning information (e.g., generated, as described herein, at time of manufacture, sometime during distribution, by the user on a website by a sales associate or other activation assistant, or by the network when a new device enters the automatic activation process). For example, the pre-activation provisioning information informs the network whether or not to let the device onto an activation sequence when the device attempts access, and in some cases, also instructs the network to direct the device to a specific activation sequence including, for example, an activation server (or other activation sequencing apparatus) sequence as described herein. In some embodiments, a central database is queried by other network equipment or the central database is included in one or more of the network elements (e.g., the AAA server and/or billing system, mobile wireless center 132), or the database is copied in part or in whole in various network elements (e.g., the central database, AAA server, mobile wireless center, billing system and/or gateways).
- In some embodiments, propagating the network equipment provisioning information for a given device or group of devices is accomplished with a network provisioning system that has access to the network provisioning database and is capable of programming the appropriate network equipment. In some embodiments, this network equipment is referred to as “network management” equipment or “network provisioning” equipment. In some embodiments, there are several functions that take part individually or in concert, including, for example, the
AAA server 121, service controller 122 (either with device based/assisted services through the service processor related embodiments or with network only embodiments as described herein), the mobile wireless center 132 (e.g., including the home location register (HLR) or other similar function referred to by other industry terms), the activation server(s) 160, other network provisioning or management equipment attached to or associated with the billing database system, and/or some other equipment apparatus. In some embodiments, the local database on the device, database in the AAA server and/or database elsewhere in network is provisioned to inform the gateway of the process for handling the pre-provisioned device according to, for example, the credentials. For example, if the device is not recognized or not authenticated onto the access network as an activated device with associated active service profile and/or service plan, the device connection or communication can be directed (or routed) to a generic activation server that provides an activation sequence that is not necessarily determined by one or more of the specific device credential elements, partial credential elements, device profile or partial device profile that define something specific about the activation sequence for the device. In another example, in which the device is not recognized or authenticated as an activated device with associated service profile and/or service plan, the device can be directed (or routed) to an activation service (or other activation sequencing apparatus) that uses some part of the credentials or range of partial credentials or a portion of a partial or complete device profile to determine a desired pre-determined device specific or device group specific activation sequence that is implemented by a specific activation service sequence or other activation sequence apparatus. In another example, in which the device is not recognized or authenticated as an activated device with associated active service profile and/or service plan, a portion of the device credentials or partial credentials can be used as a look-up index into a database that determines what the specific device activation sequence should be, and the device can be directed (or routed) to a specific activation server sequence or other activation sequencing apparatus. - In some embodiments, a database in the AAA server or database elsewhere in network is provisioned to inform the gateway what to do with a pre-provisioned device according to the credentials. For example, devices can be authenticated (for activated devices), routed to activation servers (or other activation sequencing apparatus) or denied access. In some embodiments, the AAA server (and/or other network elements) provide the above discussed look-up function for the above gateway description in which a lookup database, locally stored or stored in a central database, is queried to provide secondary routing information to the specific or generic activation servers.
- In some embodiments, the pre-provisioned database is located in the billing system. In some embodiments, the billing system accesses the pre-provisioned database (e.g., stored on the billing system or another network element) for the purpose of setting up temporary accounts or permanent accounts and associating those accounts with pre-activation status, activated free ambient or activated paying customer.
- In some embodiments, for zero activation, all the required pre-provisioning or programming of the above network elements, or others, is coordinated by the network provisioning system at some point after the partial or full device credentials have been associated with the device or reserved for a particular device type or service type. In some embodiments, the network provisioning system also coordinates the information to or from the device provisioning apparatus that is described elsewhere.
- In view of the various embodiments described herein, it will be appreciated that many of the automated or background provisioning, activation and ambient embodiments described herein can be accomplished with network based approaches, device based approaches, or network/device combination/hybrid based approaches. For example, when the access control for the provisioning process is accomplished in the device (e.g., a device based approach), the activation server can be located anywhere on the Internet, and the device will ensure that the activation process is conducted with the activation server while blocking other traffic from occurring. As another example, some or all of the ambient provisioning programming steps become steps to program the access control, traffic control, application control, bill by account rules, and/or other aspects in the service processor or service controller as described herein.
- In some embodiments, the provisioning apparatus described herein can be a computer located in the user's home or business, and the user or an IT manager has access to a website that provides the provisioning information, in which the computer serves as the provisioning or software programming apparatus. In some embodiments, the network itself, possibly through an
activation server 160, website or other interface to the device, becomes the provisioning apparatus, in some cases, with the assistance of software on the device to affect the programming of provisioning information from the network or the communication of device credentials or other information to the network. For example, this software can be a background process that runs without user interaction, a portal/widget program, a web browser based program, a WAP browser based program, and/or any other program that provides a counterpart function to the network functions effecting the provisioning (e.g., activation server). In some embodiments, the activation server either initiates a specific provisioning sequence if device software is present to assist or routes to a website for manual entry if there is no software present. -
FIG. 64 illustrates another network architecture including a system located in the manufacturing or distribution chain for the device that provides the device provisioning or partial provisioning, and any pre-activation required for the device to later activate on the network in accordance with some embodiments. Device credential, software andsettings server 6420 provides a link to the network functions that generate or provide device credentials, and/or associate device credentials with activation profiles or pre-activation profiles in the network equipment (e.g., thebilling system 123, service controllerdevice control system 6225,gateways base station 125, credential generation andassociation server 6410,activation server 160, servicedownload control server 1660 and/or other network apparatus). For example, the link between the device credential, software andsettings server 6420 to the central provider core network equipment can be over the Internet 120 (e.g., a secure link over the Internet) as shown or over another connection such as a leased line. The device credential, software andsettings server 6420 obtains credentials or partial credentials from the network apparatus that generates them, illustrated by the credential generation &association server 6410. Credential generation &association server 6410 need not be directly connected to the centralprovider core network 110 as shown, but can be located elsewhere (e.g., in another location connected by a secure Internet link). Credential generation &association server 6410 assigns credentials, or partial credentials, for use by device credential, software andsettings server 6420. When these credentials are assigned to a device, they are programmed, loaded or otherwise associated with the device by devicecredential provisioning apparatus 6430, which is connected to the device wirelessly or via a wire line connection. - In some embodiments, a device software loading and
programming apparatus 6440 provides software loading or device settings functions that form a portion or all of the provisioning or pre-provisioning device configuration, or form a portion or all of the device activation profile configuration, or form the device service owner, master agent or VSP device assignment or signature, and in some embodiments, using an activation tracking service (ATS) system. As discussed herein, the ATS monitors network connections and aspects of traffic that provide insight into which networks thedevice 100 is gaining access to, in some embodiments, for the purpose of ensuring that an OEM, master agent, device service owner or VSP is being compensated for devices that activate on a service provider network. In some embodiments, the ATS agent connects to a server counterpart that records and, in some embodiments, also analyzes the service or network connection information to make a determination of the type of access service the device is receiving and, in some cases, determine which networks the device is activated on. In some embodiments, the ATS is installed on the device in a manner that makes it difficult to tamper with or remove so that the entity that is intended to get credit for device service activation does get credit (e.g., the ATS agent can be loaded into secure memory, it can be installed with software that makes it difficult to de-install, it can be installed on the modem possibly in secure memory, it can be installed in the BIOS, it can be installed deep in the OS kernel, it can be installed with one or more additional device agents that monitor the ATS agent and alert a network function or re-install it if tampered with). TheSIM inventory 6450 is provided to illustrate that, in some embodiments, hardware elements (e.g., a SIM security module as shown) or hardware configurations are also installed or manipulated indevice 100 and these operations and the recording of the resulting associations form a portion of the provisioning or pre-provisioning process. - In some embodiments, at the time the credentials or partial credentials are loaded, programmed, set, installed, read from the device or otherwise recorded, they are, in some cases, all associated together in a database that allows for later identification of the device and its appropriate provisioning and/or activation process through such associations. For example, this can involve reading device parameters such as MEID, MAC address, device type, or other information that is associated with the information being loaded or configured on the device. As discussed herein, this credential configuration and association information is stored in the network equipment responsible using it to configure the network to activate the device in one of the various embodiments disclosed herein.
- Some embodiments include tying some or all of the activation provisioning steps and information settings together into a database that defines a higher level activation profile for a group of users(/devices), and a server is used to perform device and equipment programming for the devices in the group, including, for example, associating the following device information into the group definition: credentials, service owner or master agent, provisioning information and/or activation profile. Some embodiments further provide for this device group information being distributed to the various network equipment components required to activate the devices as discussed elsewhere. In some embodiments, this programming and device group association is accomplished using the
VSP workstation server 4910. For example, a device can be manufactured and distributed in a manner that provides flexible assignment of the device to a group that is assigned to an activation profile or a service owner. - In some embodiments,
multiple activation servers 160 are provided (as shown), which illustrates that there can be multipledevice activation servers 160 each with a different device activation experience and potentially controlled by a different VSP, service owner, service provider, OEM or master agent. As discussed herein, there are several ways that adevice 100 can be routed to theproper activation server 160 so that the device provisioning and activation process can be completed. In some embodiments, all devices that are not activated are re-directed (or routed) to an activation server that reads one or more parameters in the device credentials. The device credential information can be determined either through the device identification information associated with the access network connection itself (e.g., MEID, IP address, phone number, security credentials, or other credentials identified for a device that gains access with the network), or with the aid of the device in a pre-arranged query-response sequence. The device can then be re-directed (or routed) to the appropriate activation server for that device, device group, device service owner or VSP. In some embodiments, the same process described above can be accomplished with a single re-direction from aservice gateway appropriate activation server 160 for that device. In some embodiments, theactivation server 160 can be incorporated directly into thegateway base station 125 or other network component. In some embodiments, theactivation server 160 can be incorporated into theservice controller 122 or the service controllerdevice control system 6225. - In some embodiments, apparatus other than the activation server are used to facilitate provisioning of credentials or partial credentials, or activation, during manufacturing or device distribution, and, for example, these apparatus can augment, supplement, compliment or replace the activation server function. Such apparatus include, for example, device programming equipment (e.g., device
credential provisioning apparatus 6430, device software loading andprogramming apparatus 6440 or SIM inventory 6450), equipment that is networked into a central provider, MVNO or VSP database (e.g., device credential, software and settings server 6420) to gain access to provisioning information or activation information that is programmed into a device or group of devices, or to place device credential or partial credential information in a network database for later recognition, or to receive or communicate security information such as certificates for devices or SIM modules that will later be used to complete provisioning or complete activation or gain access to a network. For example, these apparatus, or any other apparatus including the activation server, can be networked into a service provider network or device database, an MVNO network or device database or a VSP network or device database. In some embodiments, programming of the device credentials or other information associated with the service processor or device is provided, so that, for example, the device can be recognized by an activation server or similar network function at a later point in time so that provisioning or activation can be completed in an automated manner, potentially with reduced or no user involvement, that provides a provisioning or activation configuration that is in some way unique for the service provider or service provider partner, device type, user group, VSP, MVNO, master agent or other entity. In some embodiments, this programming is provided in a manner that is difficult to change without the proper authorization so that the device is properly associated with the proper “service owner” or master agent (e.g., for the purpose of activation incentive payments). For example, as discussed herein, various approaches can be applied to the device credential or other settings or software provisioning so that the settings or software are secure or protected, or so that if the software is removed, replaced or modified it is reported or replace or restored. In some embodiments, VSP control of the provisioning, partial provisioning or activation of devices is provided during manufacture or at different points in the distribution channel. As discussed herein, some of these embodiments allow the central provider to offer to service partners (e.g., VSPs, MVNOs, master agents, and/or OEMs) similar types of control for device activation experience design or device service assignment control (e.g., sometimes referred to as service provider device locking so that other service providers cannot provide primary access to the device) during the manufacturing or distribution process that are possible with devices manufactured and distributed for the central service provider. - In some embodiments, the device is provisioned before the user obtains the device with permanent credentials, temporary credentials or partial credentials. In this case, the necessary credential programming of the device occurs during manufacture, at some point in the device distribution, such as at a distribution depot or in a store, or at the point of sale or point of shipment. In some embodiments, provisioning of network information as discussed above is used, and the network information is provisioned at the same time, before or after the device information is provisioned. In some embodiments, the device provisioning information is programmed with dedicated apparatus that connects to the device either with wires or wirelessly. For example, the dedicated apparatus can be local to the location where the device is being provisioned, or it can be partially or entirely networked into a database or provisioning solution located elsewhere and operated by the central provider, a VSP, OEM or other entity. For example, the apparatus to program the network portions of the provisioning information can also be networked and the operators who set up the required network programming for a device or group of devices may be in the vicinity of the servers that host the provisioning and management tools or they may network into the servers. In some embodiments, provisioning system operators have full or partial control of any device provisioning equipment associated with the entity they work for (e.g., OEM, VSP or master agent) but only have remote access via secure terminal, secure website or other techniques to network into a central provider or VSP server farm in which they control or partially control the network portion of provisioning capabilities for that subset of devices that are assigned to the entity they work for with (e.g. OEM, VSP or master agent).
- In some embodiments, provisioning is accomplished over the air on the mobile access network for mobile devices, or over the wired access network or WLAN connection for wired access networks, either before the user receives the device or after the user receives the device. In some cases, the device can be connected to general purpose equipment, such as a computer to perform the programming required to complete provisioning. In the cases in which the device is provisioned at point of sale or after point of sale, the device provisioning can be triggered by a user initiated sequence, or can be initiated by an automated background sequence at any time after the device is powered on. In such cases, in some embodiments, partial credentials that include information such as device type, OEM or service provider are used to assist in determining how to complete the provisioning, and the information can also include secure information, certificate or signature programmed into the partial credentials that is required for the network to perform the provisioning of the remaining credential information in the device and possibly the network. In some embodiments, any network information used/required to provision the device or service is generated at the time the partial credentials are determined rather than beforehand.
- In some embodiments, the device is activated for service before the user obtains the device with permanent credentials, temporary credentials or partial credentials, or with a permanent service account or a temporary service account. For example, in this case, the necessary steps of provisioning and activating service for the device can occur during manufacture, at some point in the device distribution, such as at a distribution depot or in a store, or at the point of sale or point of shipment. In some embodiments, the steps for activating service include one or more of the following: provision the device (e.g., with permanent, temporary or partial credentials), provision the necessary network databases and equipment to prepare them to recognize the device and associate it with the service profile and/or service plan, create or select the service account (e.g., permanent or temporary service account), select or create the service profile and/or service plan, program any elements in the device required to activate service (e.g., account ID, device aspects of the service profile and/or service plan), and program the necessary network databases and equipment with the required associations of device credentials and service profile and/or service plan policy settings. In some embodiments, the device oriented programming portions of the service activation steps occur at the same time, before or after the network oriented programming portions of the service activation steps.
- In some embodiments, the device activation information is programmed with dedicated apparatus that connects to the device via a wireless or wire line connection. For example, the dedicated apparatus can be local to the location where the device is being provisioned, or the dedicated apparatus can be partially or entirely networked into a database or service activation solution located elsewhere and operated by the central provider, a VSP, OEM or other entity. For example, the apparatus to program the network portions of the activation information can also be networked and the operators who set up the required network programming for a device or group of devices can be in the vicinity of the servers that host the service activation and management tools or they can network into the servers. In some embodiments, activation server tools operators have full or partial control of any device activation apparatus associated with the entity they work for (e.g., OEM, VSP or master agent) but only have remote and partial access via secure terminal, secure website or other techniques to network into the network portion of the activation tools that are controlled by the central provider or VSP. The server tools operators can be restricted in some embodiments to providing network activation information or settings only for those devices or device groups that are assigned to the entity they work for with (e.g., OEM, VSP or master agent). For example, the device control group restriction can be accomplished with a secure database that has secure sub-partitions for one or more entities so that they cannot impact the control of one another's network activation settings but can control their own devices. In this way, a centralized set of activation tools resources controlled by a central provider, VSP or other entity can be partitioned so that different entities can have partial or full control of the activation service definition for devices or groups of devices without impact or risk to others who share the network and activation tools resources.
- In some embodiments, activation is accomplished with an over the air interface to a mobile device, or over the wired access network or WLAN connection for wired access networks, either before the user receives the device or after the user receives the device. In some cases, the device can be connected to general purpose equipment such as a computer to perform the programming required to complete activation. In the cases in which the device is activated at point of sale or after point of sale, the final device activation process can be triggered by a user initiated sequence, or can be initiated by an automated background sequence at any time after the device is powered on. In such cases, some embodiments call for a temporary service account that is used to bring the device onto the network before the user has input the information necessary to create a permanent service account. In some embodiments, a temporary or permanent service account can be applied to the device at the time the device reaches the network, and the type of account, service profile and/or service plan can be influenced (e.g., partially determined or informed) or determined by information embedded in the device credentials or partial credentials, such as device type, device ID, SIM, OEM or service provider. For example, the device credentials can also include secure information, certificate or signature that can be required by the network to perform the activation steps for temporary or permanent service account status. In some embodiments, in which the device is activated in this manner before the user information is available, or before the user has selected a pay for service plan, the service profile and service plan are set up for ambient services as described herein.
- In some embodiments, the device is activated during the manufacturing or distribution process, and then the activated device status is suspended. Once the temporary or permanent service account is set up, with appropriate service profile and/or service plan and temporary or permanent credentials, in some networks and billing systems the service can often be more easily resumed once suspended as compared to provisioning and activating the device from scratch. The device is then later resumed (or re-activated) when some event triggers the resume process, such as when it ships to the end user or when the end user attempts to use it. This process prevents the network from needing to manage credentials and accounts for devices that have been activated but are not yet on the network.
- In some embodiments, provisioning is accomplished at least in part with temporary credentials in a manner which is automated and convenient for the user or device owner. In some embodiments, at least some subset of the temporary credential elements replaced at a later point in time by permanent credential elements in a manner that is also automated and convenient for the user or device owner. In some embodiments, the temporary credential set is pre-programmed into the device along with a temporary or permanent service account including service profile during the manufacturing or distribution process so that the device is activated with temporary credentials when it ships. In some embodiments, the aforementioned pre-programming is performed for the network via a secure set of server access equipment that networks into the network databases used to define the service profile and/or the service plan. In some embodiments, a subset of the temporary credentials is recycled once it is replaced, if a temporary service account is not activated or used after some period of time, if a permanent account is not activated or used after some period of time, or if the credentials subset is revoked from the device for some other reason.
- In some embodiments, more than one device is assigned one or more elements of the temporary credentials, such as the phone number, which may be limited in supply. In some embodiments, a network will accept more than one set of temporary credentials, one or more redundant elements, for two or more different devices. In some embodiments, a device that has two or more temporary credential sets, in which at least a subset of the credential elements are different for the sets, so that if one set of credentials has elements that are already being used to access the network, then one or more reserve sets can be drawn upon to gain access to the network.
- In some embodiments, the temporary credentials are used to log onto the network to conduct an over the air or over the network activation process in which an activation server reads at least a portion the device credentials to determine some aspect of how the device service profile. In some embodiments, the aforementioned over the air activation process is accomplished in the background without user intervention. In some embodiments, the over the air activation process is initiated when the user first attempts to use the device or when the user first attempts to access the network or upon user request or approval. In some embodiments, the over the air activation process is initiated using a temporary service account for the device and/or network to gain access to the network. In some embodiments, the over the air activation process is initiated after the user has entered the information required to create a permanent user account into the device or into the network. In some embodiments, the user is required to enter the aforementioned user information before using the device or using some aspect of the device. In some embodiments, the temporary service account is replaced by a permanent service account some time after the user has entered the necessary information to create a permanent account into the device or network. In some embodiments, the over the air activation process is initiated using a permanent service account assignment for the device and/or network to gain access to the network.
- In some embodiments, the service profile is assigned to the device and/or network during the aforementioned over the air activation to be a pay for service profile with a free trial period. In some embodiments, the service profile assigned to the device and/or network during the aforementioned over the air activation includes pre-pay, post-pay, session based pay or pay as you go options for service. As will be apparent to one of ordinary skill in the art, various embodiments disclosed herein are particularly well suited for control or pre-pay services. In some embodiments, the service profile that is assigned to the device and/or network during the aforementioned over the air activation is an ambient service profile providing service access before all the user information is available to assign a permanent account. In some embodiments, the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing a service upgrade selection option interface to the user. In some embodiments, the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing transaction services to the user. In some embodiments, the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing bill by account functionality for the network. In some embodiments, the service profile that is assigned to the device and/or network during the aforementioned activation is an ambient service profile providing some amount of free networking or information service to entice the user to use the other ambient services. In some embodiments, the aforementioned ambient service is at least partially implemented with device based service activity control or control assistance. In some embodiments, the aforementioned ambient service is at least partially implemented by gateways, routers or switches in the network that are programmed according to the ambient access profile for the device to implement the ambient policies for network access control, routing control, traffic control or service monitoring and reporting for bill by account.
- In some embodiments, activation is accomplished at least in part with a temporary service account in a manner that is automated and convenient for the user or device owner. In some embodiments, at least some subset of the temporary service account is replaced at a later point in time by permanent service account subset in a manner that is also automated and convenient for the user or device owner. In some embodiments, the temporary service account settings (e.g., including the service profile settings and/or the service plan settings) are pre-programmed into the device along with a temporary or permanent credentials set during the manufacturing or distribution process so that the device is activated with temporary credentials when it ships. In some embodiments, the aforementioned pre-programming for the network is performed via a secure set of server access equipment that networks into the network databases used-to define the service profile and/or the service plan. In some embodiments, the device is suspended once it is activated but before the user is using it, and then resumed before or commensurate with the point in time that the user begins to use it. In some embodiments, some subset of the temporary service account is recycled once it is replaced, if the temporary service account is not used after some period of time, if the temporary service account is not upgraded to a permanent service account after some period of time, or if the activation is revoked from the device for some other reason. In some embodiments, more than one device is assigned to the same temporary service account. In some embodiments, a network accepts more than one device on the same temporary service account. In some embodiments, a device includes or is associated with two or more temporary service accounts, in which at least a subset of the temporary service account elements are different, so that if one account is already being used to access the network then one or more reserve accounts can be drawn upon to gain access to the network. In some embodiments, the temporary service account is associated with a temporary credentials set. In some embodiments, the temporary service account is associated with a permanent credentials set.
- In some embodiments, un-activated devices are detected by the network routing equipment (e.g., service gateways or routers in hierarchical networks or base stations with embedded gateways in flat networks) and the device routing is programmed to re-direct un-activated devices to an activation server network destination. For example, the activation server can first inspect the information associated with the device to determine if the device belongs to the list of devices, device types or device groups that the network is programmed to provide access to. For example, the information used to determine this can include device type, service provider, phone number, device ID, SIM ID or configuration, secure information used to qualify the device, IP address, MAC address, user, user group, VSP, OEM, device distributor, service distributor (master agent), service processor presence or configuration, presence or configuration of other software or hardware. There can also be some activation definition information embedded in the credentials, or associated with some portion of the credentials, or programmed additionally on the device that informs the activation server as to the service profile and/or service plan and/or service account that should be established for the device. If activation information (the service profile, service plan and/or service account information) is found through association with the device credentials (e.g., device ID, phone number, IP address, MAC address, SIM or other security credentials) rather than being read directly from information embedded in the device or device credentials, then the pertinent aspects of the credentials can be used as a cross reference to look up the service plan and/or service profile information stored in a database networked to or within the activation server. The activation information can include information to define a wide variety of service plans and service profiles that when properly implemented on the network functions, and perhaps device if necessary, can provide for a wide range of service activity policies, service billing policies, transaction billing policies and service account types that can be associated with the device over the air or over the network.
- In some embodiments, once the activation server has determined the activation information from the device or from a look up based on some aspect of the device credentials, then the activation server initiates the necessary network settings and billing database entries to be programmed by sending the service profile instructions to the network provisioning and activation apparatus and the service plan instructions to the billing system. In some embodiments, the activation server can then also send the any necessary service profile and/or service plan settings required for the device to a provisioning and activation support software function on the device, such as various embodiments of the service processor, so that the device provisioning and activation can be completed. The provisioning can be with permanent credentials or temporary credentials, and the service account that is set up may be permanent or temporary. In some embodiments, the activation process described above is completed perhaps before the user has entered some or all of the user information necessary to set up a permanent service account, and, in these cases, a temporary service account can be set up. In some cases, the activation process can be completed in the background before the user has completed an attempt to access the network and the service profile can be set up to provide ambient services to a temporary service account. In some embodiments, the user is required to enter the information required to establish a permanent service account prior to gaining full use of the device, either on the device, on a computer or in the store, so that by the time the user begins using the device the above activation embodiments can provide for ambient services activation with permanent account status so that the user can purchase a service upgrade or any transaction without entering any more account information.
- In some embodiments, a device status is changed from a temporary service account to a permanent service account. If the device is activated with a temporary service account, and the user information is available to set up a permanent account, then if the billing system rules and interfaces allow for such, the user information can be changed from the mock information to the actual user information while maintaining the same account identifiers in the billing system. If the billing system will not allow for such, then the user information can be used to establish a new account, the device credentials can be re-associated with the new account, in some cases, after modifying one or more of the device credential parameters, and the network functions can be re-programmed as required, and, in some cases, the device can be re-programmed as required to accommodate the new permanent account.
- In some embodiments, code on the device pulls a temporary or permanent set of credentials. When the credentials are pulled, the network associates the device with an ambient service profile according to one or more of the following: embedded device information identifying device type, service owner (e.g., VSP), user group, or user, or device ID is cross referenced to a database that is populated some time from manufacturing time to post sale where the database provides information identifying device type, service owner (e.g., VSP), user group, or user. The device is then re-directed accordingly (e.g., for device based this is a matter of setting the policies or loading the software for the service processor, for the network based approach this is a matter of populating the routing tables and service profile). For example, credentials can be re-cycled after a period of time, and/or some portion of the credentials can be redundant with other devices. For example, this is essentially a dynamic service for (temporarily) assigning device credentials, and the duration of the temporary credential validity for that device ID can be time limited to give the user time to activate a real account or a free trial, session limited, or a longer duration of time that is perhaps refreshed each time the device logs on. For example, the device could also already have permanent or temporary credentials but not have a service account. The above process can be used to assign a temporary or permanent service account as well. Once the service account is assigned and the appropriate service profile is propagated to the network elements, the device can then be directed to or use the appropriate activation profile service activities or the appropriate ambient service activities.
- In some embodiments, the device is activated in the background in a manner that is virtually transparent to the user. For example, at some point in the distribution channel, the device is programmed to seek the activation server system described above as soon as it is turned on, or as soon as some other event occurs like the user using the device or the user attempting to gain access. When the pre-programmed event is triggered, the device connects to the network and the gateways or routers re-direct the device to an activation server, as discussed above. As also described herein, the activation server either derives information from the device that informs the server what service the device should be activated with, or the server derives that information from a database look up with a portion of the device credentials as the cross reference parameter. Once the activation server has determined the activation information from the device or from a look up based on some aspect of the device credentials, then the activation server causes all the necessary network settings and billing database entries to be configured/programmed by sending the service profile instructions to the network provisioning and activation apparatus and the service plan instructions to the billing system. In some embodiments, the activation server can then also send the any necessary service profile and/or service plan settings required for the device to a provisioning and activation support software function on the device, such as various embodiments of the service processor, so that the device provisioning and activation can be completed. For example, the provisioning can be with permanent credentials or temporary credentials, and the service account that is set up can be permanent or temporary.
- In some embodiments, background activation is performed using the aforementioned activate/suspend process. At some point in the distribution channel, the device is programmed to seek to resume service as soon as it is turned on, or as soon as some other event occurs like the user using the device or the user attempting to gain access. When the pre-programmed event is triggered, the device attempts to connect to the network and the gateways or routers re-direct the device to an activation server as described herein. As also described herein, the activation server either derives information from the device that informs the server that the device is ready to resume service, or the server derives that information from a database look up with a portion of the device credentials as the cross reference parameter. Once the server is aware of this information, it sends a message to resume service to the billing system, or other network function that controls the suspend/resume function, and the service is resumed.
- In some embodiments, background activation is performed as described below. The service processor and the credentials are pre-programmed during the manufacturing or distribution process to provide the desired service profile support and/or billing profile support for the desired initial ambient service. As described herein, this programming can be accomplished with dedicated apparatus at the manufacturer or distribution depot. Furthermore, the party responsible for defining the service (e.g., typically the central provider, OEM, VSP, distributor or master agent) can network into the service processor programming apparatus to control service processor and/or credential programming for all or a subset or group of the devices or device types locally available. The service processor enabled device is programmed to seek the activation server system described above as soon as it is turned on, or as soon as some other event occurs like the user using the device or the user attempting to gain access. In some embodiments, the activation server is the access control server previously discussed or the access control server can act in concert with another server that performs the activation function. When the pre-programmed event is triggered, the device connects to the network and the gateways or routers re-direct the device to the activation server. As also described herein, the activation server can communicate with the service processor to verify the service processor security credentials, agents and configuration.
- In some embodiments, if the activation server determines that the pre-programmed settings stored in the service processor need to be modified to provide the latest version of the desired service, or if the service processor agent software needs to be updated, then this can be accomplished prior to completing the activation process. Once the service processor configuration and settings are confirmed, the activation server causes the necessary network settings and billing database entries to be programmed by sending the service profile instructions to the network provisioning and activation apparatus and the service plan instructions to the billing system. Given that the service processor can perform some or much of the service activity control or control assistance, the service control options are generally larger than without the service processor, and there can be less configuration to perform for other networking equipment to complete the provisioning and activation process. The provisioning can be with permanent credentials or temporary credentials, and the service account that is set up can be permanent or temporary.
- In some embodiments, pre-programming and pre-activation of devices with temporary credentials and a temporary service account are used to ship devices that are pre-activated. Given that the credentials are temporary and can be recycled when the permanent credentials are assigned, concerns about using up too many pre-assigned credentials are reduced. In embodiments in which a portion of credentials elements can be used for multiple devices, this concern is further reduced. If there is a concern about too many activated devices being assigned that are not actually active and generating service revenue, then the suspend/resume process discussed herein can be employed. In some embodiments, the temporary credentials and/or temporary account can be replaced with permanent credentials and/or account assignments at any time as follows. When a pre-programmed event in the device is triggered, then the device initiates a program that seeks the aforementioned activation server or another server that has the capability of fulfilling the device request to exchange the temporary credentials for permanent credentials and/or exchange the temporary account for a permanent account. The event that triggers the credential exchange can be the same or different than the event that triggers the service account exchange. The service account exchange can typically be triggered by the point in time that the user enters account information.
- In some embodiments, the aforementioned ambient service is partly implemented with a combination of the techniques for pre-provisioning during manufacturing or distribution and at least partially implementing the service activity control (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage) required for implementing ambient using the service policy provisioning capabilities in the data path gateways, routers or switches in the network. The gateways, router or switches are pre-programmed as discussed herein according to the ambient access profile for the device to implement the ambient policies for network access control, routing control, traffic control or service monitoring and reporting for bill by account. In some embodiments, the provisioning credential elements are not all pre-programmed before the device ships, but a subset of the credential elements are programmed using the activation server technique discussed herein. This over the air automated provisioning is combined with the activation server reading the device credentials to derive the service activity control settings for the gateways, routers or switches that will result in the desired ambient services activity controls.
- In some embodiments, the aforementioned ambient service is implemented with a combination of the techniques for pre-activation during manufacturing or distribution and at least partially implementing the service activity control (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage) required for implementing ambient using the service policy control capabilities in the data path gateways, routers or switches in the network. The gateways, router or switches are programmed to recognize the pre-activated device credentials as discussed herein according to the ambient access profile for the device to implement the ambient policies for network access control, routing control, traffic control or service monitoring and reporting for bill by account. In some embodiments, the device activation profile and/or service account are not pre-programmed in the network and/or the device before the device ships but the activation profile and/or service account are programmed using the activation server technique discussed herein. This over the air automated provisioning is combined with the activation server reading the device credentials to derive the service profile activity control settings for the gateways, routers or switches that results in the desired ambient services activity controls.
- In some embodiment, a VSP capability is enabled by providing a secure network connection to the service policy settings tools that define the device pre-provisioning settings, the device pre-activation service profile settings, the network equipment service activity control policy settings (e.g., access control, routing policy, traffic control, usage limits, and/or policy for usage limit overage), and the network billing system database. By providing server tools that enable all these settings to be controlled (or perhaps only observed in the case of the billing system) by a secure workstation or secure website interface that networks into the equipment that programs the settings, and providing for a secure partitioning of the devices that can be controlled by a given secure workstation or secure website interface, a central provider can provide VSP services to multiple entities who all have different device and service plan combinations that they desire different flavors of ambient services for. These techniques can also be extended beyond ambient to any device/service profile/service plan combo the VSP desires to create. In some embodiments, the networking equipment is implemented to secure device service group domains in which the service policies for a group of devices can be controlled. In some embodiments, the pre-provisioning and pre-activation techniques are substituted with the over the air activation server techniques discussed herein, and a secure device group partition capability is provided in the activation server as well so that the activation server device group partition control capabilities can be added to the secure device group partition control capabilities of the network gateways, routers and/or switches, the device programming tools and the billing system to form a VSP partition solution for over the air activation of various device/service plan combinations. In some embodiments, the device groups are relatively small so that beta trials of arbitrarily large or small size can be designed and implemented by defining a service control group as described above, and after fine tuning and perfecting the beta trial settings the device group can be expanded to publish the automated provisioning and activation service settings to a larger user or device group for production services.
- In some embodiments, device based service activity control assistance (e.g., based on the various service processor embodiments described herein) is combined with simplified provisioning techniques described herein so that service processor enabled devices can be shipped with pre-provisioned credentials (temporary or permanent) or can obtain credentials in an automated manner that is convenient and efficient for the user or device owner. In some embodiments, the service processor embodiments in combination with the manufacturing and supply chain credentials and provisioning apparatus described elsewhere provide various approaches for provisioning pre-provisioned service processor enabled devices. In some embodiments, the service processor embodiments in combination with the activation server variants discussed above provide various approaches for over the air or over the network simplified post-sale provisioning for service processor enabled devices. For example, these embodiments can also be used for ambient services given that as discussed herein the service processor has capability to implement service profile policies for deep control of ambient service activity control.
- In some embodiments, provisioning includes provisioning partial device credentials that include, for example, a secure certificate that is used to authorize full credential provisioning and/or activation by performing a process for a later look-up/validation of the full device credentials. For example, the look-up/validation of the full device credentials can be performed by a gateway, router or similar network device that re-directs to a provisioning server and/or activation server or other network components that either: (1) recognizes the partial credentials that serve as a reference to direct the device communication to a specific provisioning/activation server determined from the partial credentials; or (2) does not recognize the partial credentials, and directs the device communication to a less specific provisioning/activation server that is not necessarily associated with a reference to the partial credentials.
- In some embodiments, if the partial device credentials (e.g., temporary or permanent credentials) are being used for provisioning, then the partial credentials are read (e.g., and/or other credentials can be looked up based on the partial credentials as described above). The device is authorized if the proper credentials and/or secure certificate is present. The device credential provisioning is then completed (e.g., using activation server commands or settings to a device based software and/or hardware element), and the credentials are, in some cases, also communicated to the various network equipment elements.
- In some embodiments, if the partial device credentials are being used for activation, then partial or full device credential provisioning is performed, such as described above. A service account (e.g., temporary or permanent service account) is created or looked up based on the partial device credentials (e.g., a user account associated with the device through embedded partial or full credentials or a look up process, or based on a dynamically created/assigned temporary account associated with the device through embedded partial or full credentials). An initial service profile and, in some cases, an initial service plan (e.g., service control policy settings including a billing profile) are determined from embedded information and/or using a look up process (e.g., based on the device type and/or partial or full device credentials). The device is then programmed to enable access with the service profile and plan, and, in some cases, the various network components/elements are programmed to enable the service profile and plan, and, in some cases, proper entries in the billing system are made or confirmed, and the device credentials are, thus, activated for service.
- In some embodiments, the above described provisioning and/or activation processes are performed with the provisioning server(s) and/or activation server(s) in the background with reduced, minimal or no user input required, for example, after the device is sold to the user and the user turns on the device so that by the time the user attempts to access the service using the device, the provisioning and/or activation process is already completed.
- In some embodiments, device based service activity control assistance (e.g., based on the service processor embodiments) is combined with simplified activation techniques described herein so that service processor enabled devices can be shipped with pre-activated accounts (temporary or permanent), or can obtain activated account status in an automated manner that is convenient and efficient for the user or device owner. In some embodiments, the service processor embodiments in combination with the manufacturing and supply chain activation and provisioning apparatus described elsewhere provide various approaches for pre-activated service processor enabled devices. In some embodiments, the service processor embodiments in combination with the activation server variants discussed above provide various approaches for over the air or over the network simplified post-sale account activation for service processor enabled devices. These embodiments can also be used for ambient services given that as discussed herein the service processor has capability to implement service profile policies for deep control of ambient service activity control.
- In some embodiments, the service processor can be combined with the pre-provisioning and pre-activation techniques described above to create an ambient service solution that will work on roaming networks in which the central provider or VSP has no control or minimal control over the network elements. For example, the device includes a service processor pre-programmed for ambient service activity control as discussed herein, and the device credentials and other settings are pre-provisioned and pre-activated for the central provider network, all of which is described in numerous embodiments disclosed herein. Provided that the service provider has a roaming agreement with other service providers, or provided that the device may gain access to the roaming network, when the device is roaming it will be capable of ambient connectivity with bill by account functionality and all the other features of ambient. Furthermore, as also discussed herein, the ambient service activity control policies can be different for different roaming networks to accommodate the varying network costs and performance. Also, for example, it would be permissible to sign up for initial services or additional upgrade services with the central provider while roaming on the roaming partner network. One of ordinary skill in the art will appreciate that this also allows for creating a VSP or MVNO for the purpose of creating a clearing house for central provider service activations according to geography or user choice. By using a global multi-mode modem module, and maintaining service agreements with a multitude of carriers, the MVNO or VSP can provide consistent ambient services across multiple carriers and multiple geographies while still maintaining a good degree of cost control. Using bill by account capabilities, it is also possible to have an activation agreement where a roaming service provider agrees to refund the cost of ambient roaming. From the ambient service platform, the VSP or MVNO can then provide service purchase options to the user based on the carrier networks available to the device, or the VSP or MVNO can broker the user off to any of the carriers by activating the device onto the carriers main central provider service.
- Accordingly, these embodiments provide flexible capabilities for activating a device or group of devices with a broad range of service profiles and service plans by simply programming the device with the proper credentials at some time during manufacturing or distribution, or simply programming a database associated with the network so that a portion of the device credentials can be used to look up the desired service profile and service plan. For example, various activation embodiments described herein are highly convenient for the end user and need not, in many cases, involve any human intervention.
- The
service processor 115,service controller 122, policy implementation and/or profile implementation and various embodiments disclosed herein are applicable to conventional communication products as well as machine to machine applications. For example, if the machine to machine device includes aservice processor 115 with an activated account, then the service profile settings can be optimized for machine communications to provide only the limited access required to support the particular machine to machine application. This allows for cost optimized access services and prevents the machine to machine device or access modem from being misappropriated and used for some other service access than that intended. For example, by programming the machine to machine communications device at time of manufacture or during distribution with credentials or partial credentials that provide for automated provisioning and activation as described herein, the device can be automatically provisioned and activated on the service network with a service account when deployed, thus eliminating the need for costly or time consuming human intervention. The various embodiments that make it simpler to design, manufacture, test and deploy devices may also be equally applied to machine to machine devices. These embodiments include theservice processor 115 developers kit and the automated provisioning and activation management tools among others. Also, the service analysis and test tools and the virtual service provider embodiments can also be applied to machine to machine applications. - Verifiable Device Assisted Services for Intermediate Networking Devices
- It should be appreciated that the various service monitoring, notification, control and billing embodiments disclosed herein can also be applied to intermediate networking device applications.
- In some embodiments, an intermediate networking device is a communications device in which the
service processor 115 is configured at least in part to allow the intermediate networking device to act as a service intermediary or intermediate connection between the network and one or more end point devices (e.g., communications devices). In addition, aservice controller 122 or other suitable network functions can be employed to assist with the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments described herein. In some embodiments, an intermediate networking device does this by implementing the service policies required for assisting service usage control of the intermediate networking device and connecting the network to provide services to one or more end point devices that are connected to the intermediate networking device. In some embodiments, the intermediate networking device also monitors the service use activities of the intermediate networking device and/or the end point devices connected to the intermediate networking device. In some embodiments, the intermediate networking device and/or end point device service usage is verified to ensure that the service usage is within the expected ranges for the policies that are implemented. In some embodiments, the intermediate networking device connects with the network using one modem technology and connects with the end point devices using one or more additional technologies. In some embodiments, an intermediate networking device connects the end point devices to the network by passing, bridging, forwarding, routing, traffic shaping or otherwise allowing the end point devices to communicate with the network. Example intermediate networking device embodiments include a Wi-Fi to WWAN (e.g., 2G, 3G, 4G or other wireless wide area networking access technology) bridge or router device, a Wi-Fi to DSL, cable or fiber gateway device, a WWAN to DSL or Cable femto cell device, a WWAN and Wi-Fi to DSL, Cable or fiber back-hauled femto cell device, a WWAN to WWAN router device, a WWAN to WLAN, WPAN or LAN bridge, router or gateway device, or a WWAN back up connection device for an enterprise router. - An intermediate networking device can also be provided in some embodiments by including a bridging, forwarding or routing function between two modems in a communications enabled device that connects to the network. For example, an intermediate networking device configuration can be a cell phone, smart phone, mobile internet device or any other mobile device that includes a WWAN modem and a Wi-Fi, WLAN, WPAN or LAN connection that can be used to connect to other end point devices. For example, the mobile device WWAN modem can connect to the network, a
service processor 115 can be included on the device processor to assist monitoring, controlling and billing for services between the WWAN network and end point devices connected to a Wi-Fi modem. In addition, aservice controller 122 or other suitable network functions can be employed to assist with verifiable service usage monitoring, control and verification as disclosed in numerous embodiments disclosed throughout herein. In some embodiments, the Wi-Fi modem can be configured in access point mode or in ad hoc mode to communicate with other end point devices in the area covered by the mobile device WLAN modem. In this manner, aservice processor 115 and aservice controller 122 or other suitable network functions can be employed to enable the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments described herein. - Another example embodiment is a notebook or sub-notebook computer with a WWAN modem and a Wi-Fi, Ethernet, Firewire, Bluetooth, near field or Zigbee modem in which the notebook processor has a
service processor 115 running on the notebook processor and theservice processor 115 is used to assist monitoring, control and billing for services communicated between the WWAN network and end point devices connected to the notebook or sub-notebook WLAN, LAN or WPAN. Another example embodiment is a Wi-Fi hot spot with aservice processor 115 capability. Another example embodiment is a WWAN back up modem in an access network router where the back up modem connection to the WWAN network is used when the main wired network connection goes down, and a router processor or a WWAN back up modem processor runs aservice processor 115 to assist monitoring, controlling and billing for services between the WWAN network and the access router (e.g., the service provider may only wish to enable a connection when the main wired network is down to ensure that the WWAN modem is not used for everyday access). In this manner, aservice processor 115 and aservice controller 122 or other suitable network functions can be employed to enable the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments described herein. - Another example embodiment is a two-way home gateway configured to perform various functions such as reading power consumption of the home and/or components in the home, providing WLAN, WPAN or LAN connectivity for such components or to the power meters/controllers attached to such components, providing a WWAN or WAN connection to a network that reads, records, monitors and/or controls the home and/or component power consumption, and possibly to provide other wide area network services for other devices in the home such as computers or entertainment electronics in a similar manner to the WWAN, DSL, cable and fiber gateway embodiments. The WLAN, WPAN connections can be made with one or more of Wi-Fi, Zigbee, Bluetooth, NFC or any other suitable wireless modem technology, and any desired wired LAN connections may be made with one or more of Ethernet, USB, Firewire, data over cable, data over power line or any other suitable wired modem technology. The WWAN connections can be made with one or more of 2G (
e.g. CDMA 1×RT, GPRS), 3G (e.g. WCDMA UMTS/HSPA/non-MIMO HSPA+, CDMA EVDOrA/B, 802.16d/e WiMax), 4G (e.g. LTE, MIMO HSPA+, MIMO 802.16m WiMax) or any other suitable modem technologies and the wired WAN connections may be made with one or more of DSL, Cable, fiber or any other wired modem technology. Aservice processor 115 and aservice controller 122 or other suitable network functions can be employed to enable the verifiable service usage monitoring, control and verification as disclosed in numerous embodiments disclosed throughout herein. - In some embodiments, an intermediate networking device can be used to connect one end point device to a network and assist in implementing service policies, or an intermediate networking device can connect multiple end point devices to one or more networks and assist in implementing service policies. In some embodiments, an intermediate networking device can be associated with one service profile, one service plan or one service account, or an intermediate networking device can be associated with multiple service profiles, multiple service plans or multiple service accounts. In some embodiments, end point devices connected to an intermediate networking device can have service usage policies implemented in aggregate for all end point devices, or service policies can be implemented differentially for different end point devices.
- In some embodiments, an intermediate networking device can have a network connection associated with a single account and manage QOS between end point devices under one umbrella service profile or collection of profiles. In some embodiments, an intermediate networking device can treat all connected end point devices equally from a service sharing or QOS perspective so that, for example, service usage is based on end point device demand and/or contention. In some embodiments, an intermediate networking device differentiates service QOS between different end point devices based on end point device service demand or service usage patterns, EDP device type or device group, end point device user or user group, end point device service account status or service plan status, or end point device application type, and/or traffic type or service type.
- As discussed herein, the
service processor 115 function assisting intermediate networking device implementation can be included on the intermediate networking device, can be included in part on the intermediate networking device and one or more end point devices, or can be implemented mainly or entirely on one or more end point devices. - In some embodiments, an intermediate networking device can be constructed in which end point devices connect to the intermediate networking device and gain access services to a WWAN network through a WWAN/Wi-Fi enabled intermediate networking device that is supplied with services associated with a single account and service profile. The intermediate networking
device service processor 115 can assist in monitoring, control and billing for WWAN service usage for all end point devices in the area covered by the intermediate networking device Wi-Fi link. In some embodiments, end point devices receive service on first come first serve basis with no differentiation. In some embodiments, end point devices receive fair distribution of services so that if one end point device is using more significantly more service than the other end point devices, or is demanding more service than the intermediate networking device service profile settings provide for a single end point device (e.g., “bandwidth hogging”), then the high demand end point device is throttled and the other end point devices are not. In some embodiments, end point devices receive hierarchical distribution of services based on one or more of service type, device type, user type, and/or account status. In some embodiments, an intermediate networking device can provide for a large or unlimited number of end point devices to connect to the network and simply control aggregate service usage parameters for the intermediate networking device WWAN connection. In some embodiments, the intermediate networking device limits the number of end point devices that are allowed to connect to the WWAN network according the end point device count limits programmed in theservice processor 115 service profile settings in the intermediate networking device. In some embodiments, end point device traffic can be identified by various end point device credential aspects including, for example, by Wi-Fi ID, MAC ID, IP address, user ID, LAN tag, end point device agent credentials, and/or browser token or cookie. In some embodiments, the intermediate networking device service account can be billed for overall service usage and/or by number of end point device connections allowed or experienced. In some embodiments, as the intermediate networking device user or owner signs up for a higher end point device connection count, one ore more aspects of the service usage policy implementation and/or profile implementations in theservice processor 115 profile settings can be increased. - The various verification techniques described herein can also be applied to the intermediate networking device and extended to multiple end point devices. For example, network based service usage measures for verification can be applied to the intermediate networking device just as if the intermediate networking device were an end point device. For example, network based service usage measures (e.g., IPDR information) can be used to perform network verification checks to ensure that intermediate networking device service usage is within acceptable ranges based on intermediate networking device policy settings as similarly described with respect to various device embodiments. In some embodiments, in the event intermediate networking device service usage is outside the policy limits set for the intermediate networking
device service processor 115, a notification can be sent to the intermediate networking device main account owner. The main intermediate networking device account owner can also be required to acknowledge the notification. The notification can also be sent to one or more other users of the intermediate networking device connection, including possibly all users. Other actions that can be taken if the network based intermediate networking device service usage measure does not match the policy limits set on theservice processor 115 include notify the user, notify the user and require acknowledgement, bill the user for service overage, suspend the end point device, quarantine the end point device, SPAN the end point device, and/or alert network manager or alert an automated network troubleshooting function. In some embodiments, a device based usage measure can be verified against a network based service usage measure. It will now be apparent that thevarious service processor 115 verification embodiments,service controller 122 verification embodiments, network verification embodiments, authentication embodiments, and tamper prevention or detection embodiments, such as those shown in and described with respect toFIGS. 22 , 23, 26, 27 and 28, can be applied to intermediate networking device applications and embodiments. - In some embodiments, it is desirable to match up individual end point device or user intermediate networking device service usage with other service usage measures. For example, the individual end point device service usage measures logged or reported from the end point devices and/or the intermediate networking device can be aggregated to form a total intermediate networking device usage measure that is compared to an aggregate intermediate networking device usage measure logged or reported in the network. In some embodiments, if these measures do not match, then an error condition results and an action is taken. In some embodiments, the aggregate intermediate networking device service usage measure is compared to the aggregate network based service usage measure and as long as these two measures are within an acceptable tolerance, then the intermediate networking device service usage measures are trusted and can be used for deeper intermediate networking device and end point device usage measures for service control and/or billing than may be possible in the network. In such embodiments, the individual end point device service usage measures gained from the intermediate networking device or end point device can be used to verify end point device service usage versus service policy allowances. In some embodiments, end point device service usage measures are compared with intermediate networking device measures for the same end point devices.
- In some embodiments, the IPDR records for one or more networks can include individual end point device service usage information. This is the case for example when the IPDRs include information broken down by end point device credential, such as IP address or other end point device credential. In such cases, intermediate networking device embodiments can be employed in which the individual end point device service usage information measured in the network can be compared with the service usage policy allowances or limits for the end point device. Also, in some embodiments, the individual end point device service usage measures from an end point device service usage monitor and/or an intermediate networking device service usage monitor can be compared with the network based service usage information to verify an end point device and/or an intermediate networking device service usage monitor is operating properly.
- As similarly described with respect to end point device embodiments with no intermediate networking device between the end point device and the network, in some intermediate networking device embodiments, service usage and service usage monitor reports can be periodically verified by performing a SPAN function on the traffic for an intermediate networking device. The SPAN traffic can be analyzed in a real-time manner or in a non-real-time manner in the network and the results can be compared with the intermediate networking device or end point device service policies or service usage measures.
- The synchronized device notification and acknowledgement embodiments can also be employed in the case in which one service account is applied to the intermediate networking device. The service usage counters in the intermediate networking device can be synchronized or updated with the network based measures and the differences between the two may be minimized. The service usage notification can be sent to one or more of the end point devices connected to the intermediate networking device. For example, the notification can be sent to the intermediate networking device manager or service owner, all end point devices or the most active end point devices.
- Similarly, user preference feedback can be collected from one or more of the service users connected to the intermediate networking device. In some embodiments, user preferences or user service selections or service settings are collected from one user or a subset of end point devices used by the service subscriber. In some embodiments, more than one service user can provide preference information or service settings even if there is only one user account. In some embodiments, there are multiple service subscribers each providing preferences. In some embodiments, as similarly described with respect to various device embodiments, user preferences can be used set service control policies that provide the user with their selected balance of cost and service capability in a manner that meets network neutrality requirements. Similarly, in some embodiments, the service monitoring and customer resource management information collected on the intermediate networking device or end point devices can be filtered according to user privacy preferences to maintain the level of user privacy selected by the user.
- Adaptive intermediate networking device policy implementation can also be performed in the intermediate networking
device service processor 115 embodiments, as similarly described with respect to various device embodiments. In some embodiments, the service policy implementation for the intermediate networking device can be adapted by theservice processor 115 agents (e.g.,policy control agent 1692 working to control the settings inpolicy implementation agent 1690, and/or another service processor agent or function) to achieve a higher level service usage goal. In some embodiments, the usage goals or adaptation can be based on aggregate end point device usage for the intermediate networking device network services, and in some embodiments, the higher level usage goals or adaptation can apply to one or more individual end point devices. - In some embodiments, even though there is one intermediate networking device account, there can be multiple options for multi-end point device or multi-user operation in which the number of end point devices, number of users or service capabilities for some of the end point devices or users are selectable. These parameters are accommodated by an intermediate networking device service profile that includes the service capabilities that are to be delivered to a multitude of end point devices or users. In some cases, some end point devices or users have a different profile within the intermediate networking
device service processor 115 with differentiated capabilities as compared to the intermediate networkingdevice service processor 115 profile for other end point devices or users. This is the case for some of the examples provided herein. These multi-end point device or multi-user service profiles in the intermediate networkingdevice service processor 115 can share services equally or can allow more capable access services to some end point devices or users than others. In some embodiments, a service profile implemented by the intermediate networkingdevice service processor 115 for one end point device or user is different than that in the service profile implemented by theservice processor 115 for another end point device or user (e.g., providing differentiated service profile implementations by end point devices and/or users). End point devices can be uniquely identified for purposes involving implementation of different service profiles in the intermediate networkingdevice service processor 115 agents (e.g., depending on the embodiment,service monitor agent 1696,policy implementation agent 1690,policy control agent 1692,application interface agent 1693 and/or other service processor agents or functions) based on a number of parameters, such as IP address, local area network address (e.g., Wi-Fi address), MAC address end point device ID, user ID, and/or end point device application layer tag. This allows for independent service usage monitoring and control for different end point devices or users. - In some embodiments, an intermediate networking device also bridges services to end point devices or users that have individually managed service profiles, service plans or service accounts. As discussed herein, individual end point device service policy implementation and/or service profile implementation can be accomplished by classifying end point device service usage according to an end point device identifier so that service monitoring, control assistance and reporting may be differentiated between one or more end point devices. These end point device identifiers can then be associated with a different service plan or account in the
service processor 115 and/orbilling system 123. The end point device or user specific service usage monitoring, reporting, notification and control assistance can be accomplished by running one or more profiles for each end point device or each user. - It will now be apparent that billing can also be implemented with a single account encompassing service usage for all users or end point devices connected to an intermediate networking device, or for individual users, end point devices, user groups or end point device groups connected to an intermediate networking device. As similarly described with respect to the service profile, this is accomplished by associating service usage events and associated billing events with a end point device identifier, user identifier, end point device group identifier, and/or user group identifier.
- In some embodiments, end point devices or users connect to more than one intermediate networking device with the same service account, service plan or service profile. In some embodiments, the intermediate networking device requires an authentication sequence for the end point device or user before allowing connection to the network through the intermediate networking device. This authentication sequence can involve the end point device communicating an active account or admission credential with the intermediate networking device. The intermediate networking device can compare the credential with a local database or may query a database in the network to admit the end point device to the intermediate networking device network connection. In either case, provided the user credential or network authorization process is passed, the
service processor 115 service profile settings for the end point device are applied and service is then established as discussed herein. In these cases, the verification can be accomplished as described herein. In some embodiments, even if the end point device does not have aservice processor 115, provided that the intermediate networking device service policy implementations and/or service profile implementations are verified as described herein, then the intermediate networking device will accurately assist in control and reporting of service usage for the different end point devices or users, and the appropriate service policy controls and/or billing can be maintained. - In some embodiments, when the end point device attempts connection to the intermediate networking device, if the user or end point device does not already have an active account or logon credential that the intermediate networking device recognizes, then the intermediate networking device can offer the end point device or user a service sign up experience. This experience can be implemented in a number of ways, including a website, WAP site, portal, download of agent software, and other methods. For example, an automated recognition of new devices can redirect unauthorized end point devices to browse into a website, WAP site, or portal site located on the intermediate networking device or in the network. If the site is located on the intermediate networking device, it can be cached and refreshed at a time of day when the network is not overly busy. Once on the site, the user or end point device selects the plan choice they desire, inputs account information and, in some embodiments, downloads device agent software to aid in network service policy implementation and/or profile implementation with the intermediate networking device. Once the user signs up, the information is logged into the network data base, the service account is established and the intermediate networking device service profile for that user or end point device is activated and the user can begin using the service.
- In some embodiments, a website, WAP site, or portal site located in the intermediate networking device can be used to provide the end point device user with a service usage monitor interface and a service purchase interface for cases in which the end point device does not posses any special software to allow it to display a more specialized service usage monitor function for information received from the intermediate networking device or network service usage counters. The service usage monitor for the intermediate networking device can be synchronized, as similarly described with respect to various device embodiments. In some embodiments, the service usage notification system can also display cost data from a usage to cost look-up function. In some embodiments, the service usage notification system can display projected service usage or projected cost, as similarly described with respect to various device embodiments. The service usage monitor to drive these service notification embodiments can be located on one or more of the end point device, the intermediate networking device or the network.
- In some embodiments, if multiple accounts are serviced by one or more intermediate networking devices, verification can be performed on the service controls for the end point device or user service usage. As will now be apparent, just as with the intermediate networking device, the end point device or user service usage comparison with usage policy settings can be verified in the ways described herein. If the usage is found to be out of policy, then any of the out of policy actions described herein can be performed, including, for example, notify the end user, notify and require acknowledgement, bill for overage, suspend, quarantine, SPAN, and/or flag to network manager or network error handling function. For example, the verification methods shown in and described with respect to
FIGS. 22 , 23, 26, 27 and 28 can be applied for the embodiments where intermediate networking devices have multiple account, multiple service plan, multiple service profile, multiple end point device, and/or multiple user capabilities. - It will be apparent that the various embodiments described herein for automated provisioning and activation also can similarly be applied to the intermediate networking device embodiments. It will also be apparent that the various virtual service provider embodiments can similarly be applied to the intermediate networking device embodiments.
- Ambient services can be employed on the intermediate networking device and the ambient services can thus be provided to the end point devices. It will be apparent that the ambient service profile embodiments disclosed herein can similarly be applied to the intermediate networking device, and then the intermediate networking device can supply those ambient services to end point devices connected to the intermediate networking device. It will also be apparent that the intermediate networking device can provide an ambient service profile as described herein to end point devices or users that have not yet signed up for service, while providing other paid for service profiles to end point devices or users that have signed up for service.
- Bill by account embodiments can similarly be applied to the intermediate networking device embodiments. For example, bill by account can be used in embodiments in which all end point devices or users are connected to the intermediate networking device under one account, or to embodiments in which some end point devices or users are accounted for separately with different service accounts, service plans or service profiles. In either case, it will be apparent that using one or more of the end point device or user identification credential aspects discussed herein can be used in a bill by account profile to account for any end point device or service activity. In such embodiments, billing event reports for those activities that include the end point device or user identifiers can also be provided for billing mediation and reconciliation down to the individual end point device or user level. For example, this allows for very deep service monitoring and billing capabilities with intermediate networking devices.
- The intermediate networking device embodiments described above also have uses in machine to machine applications. It will be apparent that if the end point device includes the correct credentials to gain access to an existing account, or to allow an automated provisioning and activation account to be established, then the end point device can be connected to the network through the intermediate networking device without human intervention. Furthermore, the service profile that is established with the end point device for machine to machine communications can be set up to provide the access required to support the machine to machine application allowing for low cost access services and preventing the end point device from being misused for some service other than that intended. For example, the verification techniques and embodiments disclosed herein can similarly be applied to such machine to machine applications.
- It will be apparent that the identifiers discussed above for bill by account mediation with accounting down to the individual end point device or user level can be combined with a billing mediation server in the network that accepts intermediate networking device billing events with end point device identification or user identification indexed billing, performs the necessary bill by account mediation functions, formats the billing events into the format used by the billing system, and transmits the mediated billing information to the
billing system 123. - In some embodiments, the intermediate networking
device service processor 115 functionality can be split. The division ranges from some or all of theservice processor 115 on the device to some or all of theservice processor 115 on the intermediate networking device. - In some embodiments, all of the
service processor 115 is on the intermediate networking device. The end point device does not participate inservice processor 115 functions and has noservice processor 115 interface software. In some embodiments, the end point device has small subset ofservice processor 115 capabilities, including, for example, a service notification UI or a logon client with credentials. In some embodiments, service monitoring is implemented on the end point device or on both the end point device and in the intermediate networking device. In some embodiments, the end point device hasadditional service processor 115 capabilities including, for example, application layer tagging that associates application layer activity withservice processor 115 service monitoring or service policy implementation and/or service profile implementation information. This can be accomplished by a range of techniques, for example, transmitting the application tagging information disclosed elsewhere to the intermediate networkingdevice service processor 115 so that the policy implementation may be accomplished with knowledge of the application layer information. Another example involves assigning IP addresses in the intermediate networking device networking stack to the end point devices so that different types of end point device traffic can be routed intoservice processor 115 traffic shaping queues, each queue having a policy profile implementation engine, and application layer tagging information or similar traffic indentifying information is used to determine which policy implementation engine the traffic should be routed to in order to accomplish the desired traffic shaping for the traffic type, application type, service type, and/or content type. In some embodiments, the traffic control policy is implemented on the end point device either with an application layer traffic controller, or by implementing more of theservice processor 115 functionality, as similarly described with respect to various device embodiments. In the end point device service functionality example, most or all of theservice processor 115 functionality is implemented on the end point device and the intermediate networking device functionality can be reduced to a bridging, forwarding or routing function between the end point devices and the network that performs little or no service control, monitoring and/or billing functions. For example, the service usage monitoring agents can also be provided on the end point device to aid in verification. - In embodiments in which the end point device requires agent software, the software can be loaded at time of manufacture or during distribution, loaded later, and/or made available for download through the intermediate networking device. In the case in which the end point device agent SW is downloaded through the end point device, there can be locally cached copies of the SW for one or more OS variants stored in a cache on the intermediate networking device, with the cache being updated over the network at convenient or conducive times, or the software can be downloaded live over the network when it is needed by the end point device. Logging the service usage to download this software is another example in which bill by account functionality can be used to track network traffic that may not be desirable to bill to a end point device owner or user, and bill by account functionality can be used to log and mediate such usage out of the user or end point device owner's bill.
- Any end point device agent software required to connect to the intermediate networking device can also be implemented as a
service processor 115 developer's kit as described herein and distributed to aid manufacturers, service provider and virtual service providers in bringing new devices onto networks with intermediate networking device capability. - In the case of a femto cell intermediate networking device, in some embodiments, it is desirable to facilitate handover from the WWAN network to the femto cell. In some embodiments, this provided in the intermediate networking
device service processor 115 in a variety of ways. In some embodiments, the voice and data traffic is routed through a VPN tunnel controlled by theservice processor 115 and connected to a network element, such as the transport gateway or another specified traffic concentration destination for the femto cell. In some embodiments, the voice traffic, the data traffic or both can be routed in secure or open Internet channels to different destinations, or the data can be routed directly to the Internet destination specified by the packets. In some embodiments, the femto cell intermediate networking device controls the femto cell frequencies or local frequency channel strength surveys over the intermediate networking device control channel. In some embodiments, theservice processor 115 has a VPN connection to a network base station hand off controller to assist in handoff to and from the WWAN network and/or has the capability to instruct the end point device and the base station handoff controller. In some embodiment, whenever an end point device authenticated for femto cell access is within range of the femto cell, the service provider desires to set up aservice processor 115 profile to get the end point device to connect to the femto cell even if it has a strong signal with one or more WWAN base stations so that the WWAN traffic may be offloaded. In some embodiments, theservice processor 115 can form a secure control plane link with network AAA functions to manage authorization and admission of end point devices the femto cell has not yet admitted, or the network policies can require re-authorization every time a end point device attempts access. Once an end point device is connected to the femto cell intermediate networking device, the verifiable traffic monitoring, control and billing functions described herein can be applied to various application embodiments. For example, the intermediate networking device service policy verification techniques disclosed herein, as similarly described with respect to various device embodiments, can similarly be applied to the femto cell intermediate networking device embodiments. - In some embodiments, the service provider desires to keep the number of end point devices or users that access an intermediate networking device below a certain count specified in the
service processor 115 profile. In some embodiments, this is accomplished by controlling the number of IP addresses allowed onto the intermediate networking device local area side connection. In some embodiments, this is facilitated by observing the end point device identification parameters available in the end point device traffic. In some embodiments, this is facilitated by observing the traffic patterns to determine the likely number of devices connecting to the network. For example, traffic demand patterns can be examined to determine how many users are likely to be demanding access at one time. Although the foregoing embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There are many alternative ways of implementing the invention. The disclosed embodiments are illustrative and not restrictive.
Claims (18)
1. A system, comprising:
a processor of a network device configured to:
execute a service controller for a plurality of device groups, wherein the service controller includes a capability to securely partition one or more device group database partitions, wherein each device group partition includes service controller system settings, and wherein each device group includes a plurality of communication devices controlled by a virtual service provider; and
a memory of the server coupled to the processor and configured to provide the processor with instructions.
2. The system recited in claim 1 , wherein the processor of the network device is further configured to:
provide a device group control interface, wherein the device group control interface is displayed on a remote terminal, a portal, or a website.
3. The system recited in claim 1 , wherein the processor of the network device is further configured to:
manage at least one aspect of one or more of the following for one or more of the device groups: a device provisioning apparatus, a device provisioning database, provisioning of device service activation or service profile parameters, activation server programming, service plans, service plan billing rules in a billing system, bill by account mediation rules in a mediation server, device service usage monitoring, network management functions, device management functions, service alarm settings, actions taken on a service alarm, a device suspend function, a device resume function, a device quarantine status, device service usage analysis tools, device service profile test tools, customer care portal content, and customer care procedure content.
4. The system recited in claim 1 , wherein the processor of the network device is further configured to:
associate a first service processor with a first service controller and a first device group when a first communications device is activated on a first network.
5. The system recited in claim 1 , wherein the processor of the network device is further configured to:
associate a first service processor with a first activation server when a first device initiates an activation request.
6. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a first communications device with a first set of credentials to activate the first communications device.
7. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a first communications device with a first set of credentials required to gain access to the network using an automated activation process when the first communications device is turned on.
8. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a first communications device with account information used to associate with a first service controller and a first device group upon activation of the first communications device.
9. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a first communications device with account information used to create an account or temporary account for activation of the first communications device.
10. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a first communications device with activation tracking service settings to associate the first communications device with an activation master agent.
11. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program activation server settings to admit a first communications device using a first activation sequence for the first device group.
12. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a plurality of billing rules for a first device group in a billing system.
13. The system recited in claim 1 , wherein the processor of the network device is further configured to:
program a plurality of user service usage notification rules for a first device group in the service controller.
14. A method, comprising:
executing a service controller for a plurality of device groups on a processor of a network device, wherein the service controller includes a capability to securely partition one or more device group database partitions, wherein each device group partition includes service controller system settings, and wherein each device group includes a plurality of communication devices controlled by a virtual service provider.
15. A computer program product, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:
executing a service controller for a plurality of device groups, wherein the service controller includes a capability to securely partition one or more device group database partitions, wherein each device group partition includes service controller system settings, and wherein each device group includes a plurality of communication devices controlled by a virtual service provider.
16. A system, comprising:
a processor of a network device configured to:
execute a service controller for a plurality of device groups, wherein the service controller includes a capability to securely partition one or more device group database partitions for virtual control by a virtual service provider, wherein each device group partition includes service controller system settings, and wherein each device group includes a plurality of communication devices controlled by a virtual service provider; and
provide a device group control interface; and
a memory of the server coupled to the processor and configured to provide the processor with instructions.
17. The system recited in claim 16 , wherein the processor of the network device is further configured to:
manage at least one aspect of one or more of the following for one or more of the device groups: a device provisioning apparatus, a device provisioning database, provisioning of device service activation or service profile parameters, activation server programming, service plans, service plan billing rules in a billing system, bill by account mediation rules in a mediation server, device service usage monitoring, network management functions, device management functions, service alarm settings, actions taken on a service alarm, a device suspend function, a device resume function, a device quarantine status, device service usage analysis tools, device service profile test tools, customer care portal content, and customer care procedure content.
18. The system recited in claim 16 , wherein the device group control interface is a remote terminal, a portal, or a website.
Priority Applications (41)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/380,783 US20100192207A1 (en) | 2009-01-28 | 2009-03-02 | Virtual service provider systems |
KR1020117019890A KR20110116190A (en) | 2009-01-28 | 2010-01-19 | Virtual service provider systems |
PCT/US2010/021381 WO2010088094A1 (en) | 2009-01-28 | 2010-01-19 | Virtual service provider systems |
CN2010800147260A CN102365623B (en) | 2009-01-28 | 2010-01-19 | Communication system and method |
AU2010208565A AU2010208565A1 (en) | 2009-01-28 | 2010-01-19 | Virtual service provider systems |
NZ594766A NZ594766A (en) | 2009-01-28 | 2010-01-19 | Virtual service provider systems |
EP10736226.1A EP2391942B1 (en) | 2009-01-28 | 2010-01-19 | Virtual service provider systems |
CA2786746A CA2786746C (en) | 2009-01-28 | 2010-01-19 | Virtual service provider systems |
US13/134,028 US8589541B2 (en) | 2009-01-28 | 2011-05-25 | Device-assisted services for protecting network capacity |
US13/134,005 US8635335B2 (en) | 2009-01-28 | 2011-05-25 | System and method for wireless network offloading |
US13/229,580 US8626115B2 (en) | 2009-01-28 | 2011-09-09 | Wireless network service interfaces |
US13/237,827 US8832777B2 (en) | 2009-03-02 | 2011-09-20 | Adapting network policies based on device service processor configuration |
US13/239,321 US8898293B2 (en) | 2009-01-28 | 2011-09-21 | Service offer set publishing to device agent with on-device service selection |
US13/247,998 US8725123B2 (en) | 2008-06-05 | 2011-09-28 | Communications device with secure data path processing agents |
US13/248,028 US8924469B2 (en) | 2008-06-05 | 2011-09-28 | Enterprise access control and accounting allocation for access networks |
US13/253,013 US8745191B2 (en) | 2009-01-28 | 2011-10-04 | System and method for providing user notifications |
US13/309,556 US8893009B2 (en) | 2009-01-28 | 2011-12-01 | End user device that secures an association of application to service policy with an application certificate check |
US13/309,463 US8793758B2 (en) | 2009-01-28 | 2011-12-01 | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US13/374,959 US8606911B2 (en) | 2009-03-02 | 2012-01-24 | Flow tagging for service policy implementation |
US13/441,821 US9755842B2 (en) | 2009-01-28 | 2012-04-06 | Managing service user discovery and service launch object placement on a device |
US13/748,152 US9557889B2 (en) | 2009-01-28 | 2013-01-23 | Service plan design, user interfaces, application programming interfaces, and device management |
US13/802,483 US20130196647A1 (en) | 2009-01-28 | 2013-03-13 | Mobile Device Activation Via Dynamically Selected Access Network |
US13/842,172 US9858559B2 (en) | 2009-01-28 | 2013-03-15 | Network service plan design |
US13/941,310 US8745220B2 (en) | 2009-01-28 | 2013-07-12 | System and method for providing user notifications |
US13/947,099 US10057775B2 (en) | 2009-01-28 | 2013-07-21 | Virtualized policy and charging system |
US14/082,040 US9609544B2 (en) | 2009-01-28 | 2013-11-15 | Device-assisted services for protecting network capacity |
US14/083,324 US20140075567A1 (en) | 2009-01-28 | 2013-11-18 | Service Processor Configurations for Enhancing or Augmenting System Software of a Mobile Communications Device |
US14/098,527 US9270559B2 (en) | 2009-01-28 | 2013-12-05 | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
US14/098,523 US9351193B2 (en) | 2009-01-28 | 2013-12-05 | Intermediate networking devices |
US14/102,436 US9253663B2 (en) | 2009-01-28 | 2013-12-10 | Controlling mobile device communications on a roaming network based on device state |
US14/147,394 US9026079B2 (en) | 2009-01-28 | 2014-01-03 | Wireless network service interfaces |
US14/156,428 US9532261B2 (en) | 2009-01-28 | 2014-01-15 | System and method for wireless network offloading |
US14/181,910 US9571559B2 (en) | 2009-01-28 | 2014-02-17 | Enhanced curfew and protection associated with a device group |
US14/214,492 US20140198687A1 (en) | 2009-01-28 | 2014-03-14 | Wireless end-user device providing ambient or sponsored services |
US14/272,274 US20140289794A1 (en) | 2009-01-28 | 2014-05-07 | Communications device with secure data path processing agents |
US14/275,805 US9578182B2 (en) | 2009-01-28 | 2014-05-12 | Mobile device and service management |
US14/292,282 US9386165B2 (en) | 2009-01-28 | 2014-05-30 | System and method for providing user notifications |
US14/339,110 US9705771B2 (en) | 2009-01-28 | 2014-07-23 | Attribution of mobile device data traffic to end-user application based on socket flows |
US14/338,807 US9094311B2 (en) | 2009-01-28 | 2014-07-23 | Techniques for attribution of mobile device data traffic to initiating end-user application |
US14/340,270 US9491199B2 (en) | 2009-01-28 | 2014-07-24 | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US14/473,137 US9591474B2 (en) | 2009-01-28 | 2014-08-29 | Adapting network policies based on device service processor configuration |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US20635409P | 2009-01-28 | 2009-01-28 | |
US20694409P | 2009-02-04 | 2009-02-04 | |
US20739309P | 2009-02-10 | 2009-02-10 | |
US20773909P | 2009-02-13 | 2009-02-13 | |
US12/380,783 US20100192207A1 (en) | 2009-01-28 | 2009-03-02 | Virtual service provider systems |
Related Parent Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/380,781 Continuation-In-Part US8229812B2 (en) | 2008-06-05 | 2009-03-02 | Open transaction central billing system |
US12/380,757 Continuation-In-Part US8326958B1 (en) | 2008-06-05 | 2009-03-02 | Service activation tracking system |
US12/380,782 Continuation-In-Part US8270952B2 (en) | 2008-06-05 | 2009-03-02 | Open development system for access service providers |
Related Child Applications (10)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/380,767 Continuation-In-Part US8355337B2 (en) | 2008-06-05 | 2009-03-02 | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US12/380,757 Continuation-In-Part US8326958B1 (en) | 2008-06-05 | 2009-03-02 | Service activation tracking system |
US12/380,772 Continuation-In-Part US8839387B2 (en) | 2008-06-05 | 2009-03-02 | Roaming services network and overlay networks |
US12/380,759 Continuation-In-Part US8270310B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service policy implementation |
US12/380,756 Continuation-In-Part US8250207B2 (en) | 2008-06-05 | 2009-03-02 | Network based ambient services |
US12/380,782 Continuation-In-Part US8270952B2 (en) | 2008-06-05 | 2009-03-02 | Open development system for access service providers |
US13/134,005 Continuation-In-Part US8635335B2 (en) | 2008-06-05 | 2011-05-25 | System and method for wireless network offloading |
US13/134,028 Continuation-In-Part US8589541B2 (en) | 2008-06-05 | 2011-05-25 | Device-assisted services for protecting network capacity |
US13/229,580 Continuation-In-Part US8626115B2 (en) | 2008-06-05 | 2011-09-09 | Wireless network service interfaces |
US13/237,827 Continuation-In-Part US8832777B2 (en) | 2008-06-05 | 2011-09-20 | Adapting network policies based on device service processor configuration |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100192207A1 true US20100192207A1 (en) | 2010-07-29 |
Family
ID=42354072
Family Applications (81)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/380,782 Active 2030-10-25 US8270952B2 (en) | 2008-06-05 | 2009-03-02 | Open development system for access service providers |
US12/380,781 Expired - Fee Related US8229812B2 (en) | 2008-06-05 | 2009-03-02 | Open transaction central billing system |
US12/380,771 Active US8023425B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable service billing for intermediate networking devices |
US12/380,769 Expired - Fee Related US8675507B2 (en) | 2008-06-05 | 2009-03-02 | Service profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices |
US12/380,759 Active 2029-03-10 US8270310B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service policy implementation |
US12/380,767 Active US8355337B2 (en) | 2008-06-05 | 2009-03-02 | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US12/380,778 Active 2030-07-23 US8321526B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US12/380,772 Active 2030-04-21 US8839387B2 (en) | 2008-06-05 | 2009-03-02 | Roaming services network and overlay networks |
US12/380,758 Active US11134102B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service usage monitoring with reporting, synchronization, and notification |
US12/380,755 Active 2030-01-14 US8331901B2 (en) | 2008-06-05 | 2009-03-02 | Device assisted ambient services |
US12/380,757 Active 2030-12-06 US8326958B1 (en) | 2008-06-05 | 2009-03-02 | Service activation tracking system |
US12/380,779 Abandoned US20100192170A1 (en) | 2008-06-05 | 2009-03-02 | Device assisted service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US12/380,780 Active 2030-03-23 US8839388B2 (en) | 2008-06-05 | 2009-03-02 | Automated device provisioning and activation |
US12/380,774 Active US8630192B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US12/380,773 Active US8799451B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable service policy implementation for intermediate networking devices |
US12/380,756 Active 2030-08-03 US8250207B2 (en) | 2008-06-05 | 2009-03-02 | Network based ambient services |
US12/380,783 Abandoned US20100192207A1 (en) | 2008-06-05 | 2009-03-02 | Virtual service provider systems |
US12/380,777 Active 2030-01-27 US8583781B2 (en) | 2008-06-05 | 2009-03-02 | Simplified service network architecture |
US12/380,770 Abandoned US20100188993A1 (en) | 2008-06-05 | 2009-03-02 | Network tools for analysis, design, testing, and production of services |
US12/380,768 Active US9137739B2 (en) | 2008-06-05 | 2009-03-02 | Network based service policy implementation with network neutrality and user privacy |
US13/330,948 Active 2030-07-17 US8897743B2 (en) | 2009-01-28 | 2011-12-20 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US13/368,294 Active 2030-09-09 US9014026B2 (en) | 2009-01-28 | 2012-02-07 | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US13/439,788 Active US8516552B2 (en) | 2009-01-28 | 2012-04-04 | Verifiable service policy implementation for intermediate networking devices |
US13/442,214 Active US8437271B2 (en) | 2009-01-28 | 2012-04-09 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US13/443,842 Active US8531986B2 (en) | 2009-01-28 | 2012-04-10 | Network tools for analysis, design, testing, and production of services |
US13/445,180 Active US8547872B2 (en) | 2009-01-28 | 2012-04-12 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US13/445,110 Active US8713630B2 (en) | 2009-01-28 | 2012-04-12 | Verifiable service policy implementation for intermediate networking devices |
US13/445,134 Active US8467312B2 (en) | 2009-01-28 | 2012-04-12 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US13/451,349 Active US9179308B2 (en) | 2009-01-28 | 2012-04-19 | Network tools for analysis, design, testing, and production of services |
US13/451,337 Abandoned US20120201133A1 (en) | 2009-01-28 | 2012-04-19 | Network Tools for Analysis, Design, Testing, and Production of Services |
US13/456,139 Active US8478667B2 (en) | 2009-01-28 | 2012-04-25 | Automated device provisioning and activation |
US13/457,385 Active US8385916B2 (en) | 2009-01-28 | 2012-04-26 | Automated device provisioning and activation |
US13/457,389 Active US8396458B2 (en) | 2009-01-28 | 2012-04-26 | Automated device provisioning and activation |
US13/461,141 Active US8406733B2 (en) | 2009-01-28 | 2012-05-01 | Automated device provisioning and activation |
US13/554,616 Active US8441989B2 (en) | 2009-01-28 | 2012-07-20 | Open transaction central billing system |
US13/589,929 Active US8924549B2 (en) | 2009-01-28 | 2012-08-20 | Network based ambient services |
US13/615,094 Active US8688099B2 (en) | 2009-01-28 | 2012-09-13 | Open development system for access service providers |
US13/615,152 Active US8898079B2 (en) | 2009-01-28 | 2012-09-13 | Network based ambient services |
US13/615,249 Active US8666364B2 (en) | 2009-01-28 | 2012-09-13 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US13/615,217 Active US8588110B2 (en) | 2009-01-28 | 2012-09-13 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US13/633,817 Active US8903452B2 (en) | 2009-01-28 | 2012-10-02 | Device assisted ambient services |
US13/633,821 Active US8897744B2 (en) | 2009-01-28 | 2012-10-02 | Device assisted ambient services |
US13/678,410 Active US8630611B2 (en) | 2009-01-28 | 2012-11-15 | Automated device provisioning and activation |
US13/678,417 Active 2030-07-05 US8631102B2 (en) | 2009-01-28 | 2012-11-15 | Automated device provisioning and activation |
US13/705,055 Active US8667571B2 (en) | 2009-01-28 | 2012-12-04 | Automated device provisioning and activation |
US13/712,184 Active US8639935B2 (en) | 2009-01-28 | 2012-12-12 | Automated device provisioning and activation |
US13/742,312 Active US8639811B2 (en) | 2009-01-28 | 2013-01-15 | Automated device provisioning and activation |
US13/742,317 Active US8640198B2 (en) | 2009-01-28 | 2013-01-15 | Automated device provisioning and activation |
US13/847,417 Active US8724554B2 (en) | 2009-01-28 | 2013-03-19 | Open transaction central billing system |
US13/852,933 Active US8635678B2 (en) | 2009-01-28 | 2013-03-28 | Automated device provisioning and activation |
US13/866,955 Abandoned US20130229951A1 (en) | 2009-01-28 | 2013-04-19 | Automated device provisioning and activation |
US13/866,963 Active US8695073B2 (en) | 2009-01-28 | 2013-04-19 | Automated device provisioning and activation |
US13/867,347 Active US8737957B2 (en) | 2009-01-28 | 2013-04-22 | Automated device provisioning and activation |
US13/870,939 Active US8570908B2 (en) | 2009-01-28 | 2013-04-25 | Automated device provisioning and activation |
US13/896,065 Active US8797908B2 (en) | 2009-01-28 | 2013-05-16 | Automated device provisioning and activation |
US14/151,769 Active US8886162B2 (en) | 2009-01-28 | 2014-01-09 | Restricting end-user device communications over a wireless access network associated with a cost |
US14/263,604 Active US9037127B2 (en) | 2009-01-28 | 2014-04-28 | Device agent for remote user configuration of wireless network access |
US14/565,889 Active 2029-09-05 US9609459B2 (en) | 2009-01-28 | 2014-12-10 | Network tools for analysis, design, testing, and production of services |
US14/663,248 Active US9179315B2 (en) | 2009-01-28 | 2015-03-19 | Mobile device with data service monitoring, categorization, and display for different applications and networks |
US14/665,235 Active US9179316B2 (en) | 2009-01-28 | 2015-03-23 | Mobile device with user controls and policy agent to control application access to device location data |
US14/667,353 Active US9232403B2 (en) | 2009-01-28 | 2015-03-24 | Mobile device with common secure wireless message service serving multiple applications |
US14/667,516 Active US9198117B2 (en) | 2009-01-28 | 2015-03-24 | Network system with common secure wireless message service serving multiple applications on multiple wireless devices |
US14/668,829 Active US9173104B2 (en) | 2009-01-28 | 2015-03-25 | Mobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence |
US14/678,632 Active US9204374B2 (en) | 2009-01-28 | 2015-04-03 | Multicarrier over-the-air cellular network activation server |
US14/948,082 Active US10165447B2 (en) | 2009-01-28 | 2015-11-20 | Network service plan design |
US14/948,065 Active 2030-04-04 US10028144B2 (en) | 2009-01-28 | 2015-11-20 | Security techniques for device assisted services |
US14/979,233 Active US9532161B2 (en) | 2009-01-28 | 2015-12-22 | Wireless device with application data flow tagging and network stack-implemented network access policy |
US15/211,430 Active US9615192B2 (en) | 2009-01-28 | 2016-07-15 | Message link server with plural message delivery triggers |
US15/217,538 Active US9491564B1 (en) | 2009-01-28 | 2016-07-22 | Mobile device and method with secure network messaging for authorized components |
US15/239,398 Active US9641957B2 (en) | 2009-01-28 | 2016-08-17 | Automated device provisioning and activation |
US15/427,837 Active 2029-03-20 US10321318B2 (en) | 2009-01-28 | 2017-02-08 | Automated device provisioning and activation |
US15/582,350 Active 2029-12-07 US10321320B2 (en) | 2009-01-28 | 2017-04-28 | Wireless network buffered message system |
US16/034,362 Active US10694385B2 (en) | 2009-01-28 | 2018-07-13 | Security techniques for device assisted services |
US16/214,902 Active US10869199B2 (en) | 2009-01-28 | 2018-12-10 | Network service plan design |
US16/421,121 Active 2029-06-05 US11096055B2 (en) | 2009-01-28 | 2019-05-23 | Automated device provisioning and activation |
US16/436,628 Active 2029-06-18 US11228617B2 (en) | 2009-01-28 | 2019-06-10 | Automated device provisioning and activation |
US16/907,887 Active US11405429B2 (en) | 2009-01-28 | 2020-06-22 | Security techniques for device assisted services |
US17/121,717 Active US11477246B2 (en) | 2009-01-28 | 2020-12-14 | Network service plan design |
US17/342,136 Active 2029-11-04 US11757942B2 (en) | 2009-01-28 | 2021-06-08 | Automated device provisioning and activation |
US17/401,635 Active 2029-07-02 US11757943B2 (en) | 2009-01-28 | 2021-08-13 | Automated device provisioning and activation |
US17/577,237 Pending US20220279021A1 (en) | 2009-01-28 | 2022-01-17 | Automated Device Provisioning and Activation |
Family Applications Before (16)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/380,782 Active 2030-10-25 US8270952B2 (en) | 2008-06-05 | 2009-03-02 | Open development system for access service providers |
US12/380,781 Expired - Fee Related US8229812B2 (en) | 2008-06-05 | 2009-03-02 | Open transaction central billing system |
US12/380,771 Active US8023425B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable service billing for intermediate networking devices |
US12/380,769 Expired - Fee Related US8675507B2 (en) | 2008-06-05 | 2009-03-02 | Service profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices |
US12/380,759 Active 2029-03-10 US8270310B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service policy implementation |
US12/380,767 Active US8355337B2 (en) | 2008-06-05 | 2009-03-02 | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US12/380,778 Active 2030-07-23 US8321526B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US12/380,772 Active 2030-04-21 US8839387B2 (en) | 2008-06-05 | 2009-03-02 | Roaming services network and overlay networks |
US12/380,758 Active US11134102B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable device assisted service usage monitoring with reporting, synchronization, and notification |
US12/380,755 Active 2030-01-14 US8331901B2 (en) | 2008-06-05 | 2009-03-02 | Device assisted ambient services |
US12/380,757 Active 2030-12-06 US8326958B1 (en) | 2008-06-05 | 2009-03-02 | Service activation tracking system |
US12/380,779 Abandoned US20100192170A1 (en) | 2008-06-05 | 2009-03-02 | Device assisted service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US12/380,780 Active 2030-03-23 US8839388B2 (en) | 2008-06-05 | 2009-03-02 | Automated device provisioning and activation |
US12/380,774 Active US8630192B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US12/380,773 Active US8799451B2 (en) | 2008-06-05 | 2009-03-02 | Verifiable service policy implementation for intermediate networking devices |
US12/380,756 Active 2030-08-03 US8250207B2 (en) | 2008-06-05 | 2009-03-02 | Network based ambient services |
Family Applications After (64)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/380,777 Active 2030-01-27 US8583781B2 (en) | 2008-06-05 | 2009-03-02 | Simplified service network architecture |
US12/380,770 Abandoned US20100188993A1 (en) | 2008-06-05 | 2009-03-02 | Network tools for analysis, design, testing, and production of services |
US12/380,768 Active US9137739B2 (en) | 2008-06-05 | 2009-03-02 | Network based service policy implementation with network neutrality and user privacy |
US13/330,948 Active 2030-07-17 US8897743B2 (en) | 2009-01-28 | 2011-12-20 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US13/368,294 Active 2030-09-09 US9014026B2 (en) | 2009-01-28 | 2012-02-07 | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US13/439,788 Active US8516552B2 (en) | 2009-01-28 | 2012-04-04 | Verifiable service policy implementation for intermediate networking devices |
US13/442,214 Active US8437271B2 (en) | 2009-01-28 | 2012-04-09 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US13/443,842 Active US8531986B2 (en) | 2009-01-28 | 2012-04-10 | Network tools for analysis, design, testing, and production of services |
US13/445,180 Active US8547872B2 (en) | 2009-01-28 | 2012-04-12 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US13/445,110 Active US8713630B2 (en) | 2009-01-28 | 2012-04-12 | Verifiable service policy implementation for intermediate networking devices |
US13/445,134 Active US8467312B2 (en) | 2009-01-28 | 2012-04-12 | Verifiable and accurate service usage monitoring for intermediate networking devices |
US13/451,349 Active US9179308B2 (en) | 2009-01-28 | 2012-04-19 | Network tools for analysis, design, testing, and production of services |
US13/451,337 Abandoned US20120201133A1 (en) | 2009-01-28 | 2012-04-19 | Network Tools for Analysis, Design, Testing, and Production of Services |
US13/456,139 Active US8478667B2 (en) | 2009-01-28 | 2012-04-25 | Automated device provisioning and activation |
US13/457,385 Active US8385916B2 (en) | 2009-01-28 | 2012-04-26 | Automated device provisioning and activation |
US13/457,389 Active US8396458B2 (en) | 2009-01-28 | 2012-04-26 | Automated device provisioning and activation |
US13/461,141 Active US8406733B2 (en) | 2009-01-28 | 2012-05-01 | Automated device provisioning and activation |
US13/554,616 Active US8441989B2 (en) | 2009-01-28 | 2012-07-20 | Open transaction central billing system |
US13/589,929 Active US8924549B2 (en) | 2009-01-28 | 2012-08-20 | Network based ambient services |
US13/615,094 Active US8688099B2 (en) | 2009-01-28 | 2012-09-13 | Open development system for access service providers |
US13/615,152 Active US8898079B2 (en) | 2009-01-28 | 2012-09-13 | Network based ambient services |
US13/615,249 Active US8666364B2 (en) | 2009-01-28 | 2012-09-13 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US13/615,217 Active US8588110B2 (en) | 2009-01-28 | 2012-09-13 | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US13/633,817 Active US8903452B2 (en) | 2009-01-28 | 2012-10-02 | Device assisted ambient services |
US13/633,821 Active US8897744B2 (en) | 2009-01-28 | 2012-10-02 | Device assisted ambient services |
US13/678,410 Active US8630611B2 (en) | 2009-01-28 | 2012-11-15 | Automated device provisioning and activation |
US13/678,417 Active 2030-07-05 US8631102B2 (en) | 2009-01-28 | 2012-11-15 | Automated device provisioning and activation |
US13/705,055 Active US8667571B2 (en) | 2009-01-28 | 2012-12-04 | Automated device provisioning and activation |
US13/712,184 Active US8639935B2 (en) | 2009-01-28 | 2012-12-12 | Automated device provisioning and activation |
US13/742,312 Active US8639811B2 (en) | 2009-01-28 | 2013-01-15 | Automated device provisioning and activation |
US13/742,317 Active US8640198B2 (en) | 2009-01-28 | 2013-01-15 | Automated device provisioning and activation |
US13/847,417 Active US8724554B2 (en) | 2009-01-28 | 2013-03-19 | Open transaction central billing system |
US13/852,933 Active US8635678B2 (en) | 2009-01-28 | 2013-03-28 | Automated device provisioning and activation |
US13/866,955 Abandoned US20130229951A1 (en) | 2009-01-28 | 2013-04-19 | Automated device provisioning and activation |
US13/866,963 Active US8695073B2 (en) | 2009-01-28 | 2013-04-19 | Automated device provisioning and activation |
US13/867,347 Active US8737957B2 (en) | 2009-01-28 | 2013-04-22 | Automated device provisioning and activation |
US13/870,939 Active US8570908B2 (en) | 2009-01-28 | 2013-04-25 | Automated device provisioning and activation |
US13/896,065 Active US8797908B2 (en) | 2009-01-28 | 2013-05-16 | Automated device provisioning and activation |
US14/151,769 Active US8886162B2 (en) | 2009-01-28 | 2014-01-09 | Restricting end-user device communications over a wireless access network associated with a cost |
US14/263,604 Active US9037127B2 (en) | 2009-01-28 | 2014-04-28 | Device agent for remote user configuration of wireless network access |
US14/565,889 Active 2029-09-05 US9609459B2 (en) | 2009-01-28 | 2014-12-10 | Network tools for analysis, design, testing, and production of services |
US14/663,248 Active US9179315B2 (en) | 2009-01-28 | 2015-03-19 | Mobile device with data service monitoring, categorization, and display for different applications and networks |
US14/665,235 Active US9179316B2 (en) | 2009-01-28 | 2015-03-23 | Mobile device with user controls and policy agent to control application access to device location data |
US14/667,353 Active US9232403B2 (en) | 2009-01-28 | 2015-03-24 | Mobile device with common secure wireless message service serving multiple applications |
US14/667,516 Active US9198117B2 (en) | 2009-01-28 | 2015-03-24 | Network system with common secure wireless message service serving multiple applications on multiple wireless devices |
US14/668,829 Active US9173104B2 (en) | 2009-01-28 | 2015-03-25 | Mobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence |
US14/678,632 Active US9204374B2 (en) | 2009-01-28 | 2015-04-03 | Multicarrier over-the-air cellular network activation server |
US14/948,082 Active US10165447B2 (en) | 2009-01-28 | 2015-11-20 | Network service plan design |
US14/948,065 Active 2030-04-04 US10028144B2 (en) | 2009-01-28 | 2015-11-20 | Security techniques for device assisted services |
US14/979,233 Active US9532161B2 (en) | 2009-01-28 | 2015-12-22 | Wireless device with application data flow tagging and network stack-implemented network access policy |
US15/211,430 Active US9615192B2 (en) | 2009-01-28 | 2016-07-15 | Message link server with plural message delivery triggers |
US15/217,538 Active US9491564B1 (en) | 2009-01-28 | 2016-07-22 | Mobile device and method with secure network messaging for authorized components |
US15/239,398 Active US9641957B2 (en) | 2009-01-28 | 2016-08-17 | Automated device provisioning and activation |
US15/427,837 Active 2029-03-20 US10321318B2 (en) | 2009-01-28 | 2017-02-08 | Automated device provisioning and activation |
US15/582,350 Active 2029-12-07 US10321320B2 (en) | 2009-01-28 | 2017-04-28 | Wireless network buffered message system |
US16/034,362 Active US10694385B2 (en) | 2009-01-28 | 2018-07-13 | Security techniques for device assisted services |
US16/214,902 Active US10869199B2 (en) | 2009-01-28 | 2018-12-10 | Network service plan design |
US16/421,121 Active 2029-06-05 US11096055B2 (en) | 2009-01-28 | 2019-05-23 | Automated device provisioning and activation |
US16/436,628 Active 2029-06-18 US11228617B2 (en) | 2009-01-28 | 2019-06-10 | Automated device provisioning and activation |
US16/907,887 Active US11405429B2 (en) | 2009-01-28 | 2020-06-22 | Security techniques for device assisted services |
US17/121,717 Active US11477246B2 (en) | 2009-01-28 | 2020-12-14 | Network service plan design |
US17/342,136 Active 2029-11-04 US11757942B2 (en) | 2009-01-28 | 2021-06-08 | Automated device provisioning and activation |
US17/401,635 Active 2029-07-02 US11757943B2 (en) | 2009-01-28 | 2021-08-13 | Automated device provisioning and activation |
US17/577,237 Pending US20220279021A1 (en) | 2009-01-28 | 2022-01-17 | Automated Device Provisioning and Activation |
Country Status (9)
Country | Link |
---|---|
US (81) | US8270952B2 (en) |
EP (30) | EP2391965B1 (en) |
KR (19) | KR20110116189A (en) |
CN (20) | CN102365554B (en) |
AU (19) | AU2010208544B2 (en) |
CA (19) | CA2786832C (en) |
ES (1) | ES2657435T3 (en) |
NZ (19) | NZ594725A (en) |
WO (19) | WO2010088073A1 (en) |
Cited By (73)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090138577A1 (en) * | 2007-09-26 | 2009-05-28 | Nicira Networks | Network operating system for managing and securing networks |
US20090144182A1 (en) * | 2007-11-30 | 2009-06-04 | Seiko Epson Corporation | Task management system |
US20110066491A1 (en) * | 2009-09-16 | 2011-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | Method and Communication Device for Using a First Service Based on an Account Chargeable with the Use of a Second Service |
US20110085439A1 (en) * | 2009-10-07 | 2011-04-14 | Wichorus, Inc. | Method and apparatus for switching communications traffic in a communications network |
US20110087786A1 (en) * | 2009-10-07 | 2011-04-14 | Wichorus, Inc. | Method and apparatus for efficient resource allocation of quality of service profiles in mobile networks |
US20110085571A1 (en) * | 2009-10-07 | 2011-04-14 | Tellabs Operations, Inc. | Method and apparatus for assigning resources in a network node |
US20110208858A1 (en) * | 2010-02-24 | 2011-08-25 | Salesforce.Com, Inc. | System, method and computer program product for monitoring data activity utilizing a shared data store |
US20110225420A1 (en) * | 2010-03-10 | 2011-09-15 | Eigler Frank Ch | Module signing for unprivileged users to create and load trustworthy kernel modules |
US20110279286A1 (en) * | 2010-05-11 | 2011-11-17 | Lsis Co., Ltd. | Energy-related information display apparatus and method thereof |
US20110295728A1 (en) * | 2010-05-25 | 2011-12-01 | Salesforce.Com, Inc. | Systems and methods for automatically collection of performance data in a multi-tenant database system environment |
US20110307948A1 (en) * | 2010-06-15 | 2011-12-15 | Microsoft Corporation | Extending a customer relationship management eventing framework to a cloud computing environment in a secure manner |
US20120079559A1 (en) * | 2010-04-02 | 2012-03-29 | Interdigital Patent Holdings, Inc. | Methods for policy management |
US20120158578A1 (en) * | 2010-12-21 | 2012-06-21 | Sedayao Jeffrey C | Highly granular cloud computing marketplace |
US20120158829A1 (en) * | 2010-12-20 | 2012-06-21 | Kalle Ahmavaara | Methods and apparatus for providing or receiving data connectivity |
US20120158866A1 (en) * | 2010-12-20 | 2012-06-21 | Motorola-Mobility, Inc. | Method and System for Facilitating Interaction with Multiple Content Provider Websites |
US20120243463A1 (en) * | 2011-03-23 | 2012-09-27 | Verizon Patent And Licensing Inc. | Coaxial cable interface to outdoor broadband unit |
US8285749B2 (en) * | 2010-03-05 | 2012-10-09 | Hitachi, Ltd. | Computer system and recording medium |
US20120264400A1 (en) * | 2011-03-01 | 2012-10-18 | Tracfone Wireless, Inc. | System, method and apparatus for pairing sim or uicc cards with authorized wireless devices |
US20120317276A1 (en) * | 2011-05-24 | 2012-12-13 | Muraliraja Muniraju | Systems and methods for analyzing network metrics |
US20130219388A1 (en) * | 2012-02-22 | 2013-08-22 | Vmware, Inc. | Component framework for virtual machines |
US8533360B2 (en) | 2009-10-07 | 2013-09-10 | Wichorus, Inc. | Method and apparatus to report resource values in a mobile network |
US20130262293A1 (en) * | 2012-03-30 | 2013-10-03 | Robert L. Garner, JR. | Variable charging of audience member temporal viewing of a live video chat performance |
US8561142B1 (en) * | 2012-06-01 | 2013-10-15 | Symantec Corporation | Clustered device access control based on physical and temporal proximity to the user |
US8589516B2 (en) | 2009-09-10 | 2013-11-19 | Motorola Mobility Llc | Method and system for intermediating content provider website and mobile device |
WO2013170198A3 (en) * | 2012-05-10 | 2014-01-23 | Drawbridge, Inc. | System and method for determining related digital identities |
US8717895B2 (en) | 2010-07-06 | 2014-05-06 | Nicira, Inc. | Network virtualization apparatus and method with a table mapping engine |
US8780720B2 (en) | 2010-01-11 | 2014-07-15 | Venturi Ip Llc | Radio access network load and condition aware traffic shaping control |
US8805323B2 (en) | 2012-11-06 | 2014-08-12 | Tracfone Wireless, Inc. | Hybrid network based metering server and tracking client for wireless services |
US20140289829A1 (en) * | 2012-03-20 | 2014-09-25 | Guangdong Electronics Industry Institute Ltd | Computer account management system and realizing method thereof |
US20150038111A1 (en) * | 2011-11-15 | 2015-02-05 | Deutsche Telekom Ag | Method and telecommunications network utilizing more than one online charging system for a given user |
US8964528B2 (en) | 2010-07-06 | 2015-02-24 | Nicira, Inc. | Method and apparatus for robust packet distribution among hierarchical managed switching elements |
US8966035B2 (en) | 2009-04-01 | 2015-02-24 | Nicira, Inc. | Method and apparatus for implementing and managing distributed virtual switches in several hosts and physical forwarding elements |
US8990338B2 (en) | 2009-09-10 | 2015-03-24 | Google Technology Holdings LLC | Method of exchanging photos with interface content provider website |
US20150106495A1 (en) * | 2012-04-16 | 2015-04-16 | Clinct Holding B.V. | Computer Network for Services Retrieval, Method for Managing Such Network and a Computer System for Such Network |
US9043452B2 (en) | 2011-05-04 | 2015-05-26 | Nicira, Inc. | Network control apparatus and method for port isolation |
US9043455B1 (en) | 2011-04-06 | 2015-05-26 | Cellco Partnership | Universal data remote |
US20150154252A1 (en) * | 2013-12-04 | 2015-06-04 | Microsoft Corporation | Enhanced service environments with user-specific working sets |
US9106538B1 (en) * | 2014-09-05 | 2015-08-11 | Openpeak Inc. | Method and system for enabling data usage accounting through a relay |
US20150237667A1 (en) * | 2013-08-15 | 2015-08-20 | Benu Networks, Inc. | System and method of providing advanced services in a virtual cpe deployment |
US9124436B2 (en) | 2010-12-16 | 2015-09-01 | Cellco Partnership | Intelligent automated data usage upgrade recommendation |
US9165139B2 (en) | 2011-10-10 | 2015-10-20 | Openpeak Inc. | System and method for creating secure applications |
US20150326461A1 (en) * | 2014-05-08 | 2015-11-12 | Accenture Global Services Limited | Network usage monitoring and analytics for differentiated data services |
US9197706B2 (en) | 2008-12-16 | 2015-11-24 | Qualcomm Incorporated | Apparatus and method for bundling application services with inbuilt connectivity management |
US9215075B1 (en) | 2013-03-15 | 2015-12-15 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US9232013B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for enabling data usage accounting |
US9232012B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for data usage accounting in a computing device |
US9313604B1 (en) * | 2010-06-22 | 2016-04-12 | Amazon Technologies, Inc. | Network service request throttling system |
US9350818B2 (en) | 2014-09-05 | 2016-05-24 | Openpeak Inc. | Method and system for enabling data usage accounting for unreliable transport communication |
US9384028B1 (en) | 2013-12-19 | 2016-07-05 | Amdocs Software Systems Limited | System, method, and computer program for preserving service continuity in a network function virtualization (NFV) based communication network |
US9405902B1 (en) * | 2011-03-15 | 2016-08-02 | Trend Micro Incorporated | Anti-malware service in multi-tenant cloud computing environments |
US9460286B1 (en) | 2013-12-19 | 2016-10-04 | Amdocs Software Systems Limited | System, method, and computer program for managing security in a network function virtualization (NFV) based communication network |
US9525647B2 (en) | 2010-07-06 | 2016-12-20 | Nicira, Inc. | Network control apparatus and method for creating and modifying logical switching elements |
US9609510B2 (en) | 2009-01-28 | 2017-03-28 | Headwater Research Llc | Automated credential porting for mobile devices |
US9645899B1 (en) | 2013-12-19 | 2017-05-09 | Amdocs Software Systems Limited | System, method, and computer program for managing fault recovery in network function virtualization (NFV) based networks |
US9652727B1 (en) * | 2011-10-10 | 2017-05-16 | West Corporation | Mobile care with a virtual queue |
US9680750B2 (en) | 2010-07-06 | 2017-06-13 | Nicira, Inc. | Use of tunnels to hide network addresses |
US9686808B2 (en) | 2013-08-15 | 2017-06-20 | Benu Networks, Inc. | Centrally managed WI-FI |
US9723092B1 (en) | 2011-04-07 | 2017-08-01 | Cellco Partnership | Universal data remote application framework |
WO2017136166A1 (en) * | 2016-02-04 | 2017-08-10 | TEN DIGIT Communications LLC | Intermediary device for data message network routing and enhancement in a contact center environment |
US9760428B1 (en) | 2013-12-19 | 2017-09-12 | Amdocs Software Systems Limited | System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network |
US9794187B1 (en) | 2013-12-19 | 2017-10-17 | Amdocs Software Systems Limited | System, method, and computer program for resource conversion in a network function virtualization (NFV) based communication network |
US20170324808A1 (en) * | 2014-07-31 | 2017-11-09 | Honeywell International Inc. | Monitoring a building management system |
US20170372330A1 (en) * | 2009-09-11 | 2017-12-28 | Comscore, Inc. | Determining client system attributes |
US9954958B2 (en) * | 2016-01-29 | 2018-04-24 | Red Hat, Inc. | Shared resource management |
US9998428B2 (en) | 2015-06-29 | 2018-06-12 | Cisco Technology, Inc. | Virtual routing and forwarding (VRF) for asymmetrical virtual service provider (VSP) tunnels |
US10103939B2 (en) | 2010-07-06 | 2018-10-16 | Nicira, Inc. | Network control apparatus and method for populating logical datapath sets |
US10198142B1 (en) | 2007-08-06 | 2019-02-05 | Gogrid, LLC | Multi-server control panel |
US20190058670A1 (en) * | 2014-03-24 | 2019-02-21 | Huawei Technologies Co., Ltd. | Method for service implementation in network function virtualization (nfv) system and communications unit |
US10367766B2 (en) | 2017-01-20 | 2019-07-30 | TEN DIGIT Communications LLC | Intermediary device for data message network routing |
US10491748B1 (en) | 2006-04-03 | 2019-11-26 | Wai Wu | Intelligent communication routing system and method |
US10606718B1 (en) | 2013-12-19 | 2020-03-31 | Amdocs Development Limited | System, method, and computer program for managing fault recovery in network function virtualization (Nfv) based networks |
US11164398B2 (en) * | 2018-04-18 | 2021-11-02 | Hitachi, Ltd. | Software management system, gateway device, maintenance device, server device, and control method for software management system |
US11297688B2 (en) | 2018-03-22 | 2022-04-05 | goTenna Inc. | Mesh network deployment kit |
Families Citing this family (2032)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7958224B2 (en) | 1999-02-17 | 2011-06-07 | Catalina Marketing Corporation | Incentive network for distributing incentives on a network-wide basis and for permitting user access to individual incentives from a plurality of network servers |
WO2003058483A1 (en) | 2002-01-08 | 2003-07-17 | Seven Networks, Inc. | Connection architecture for a mobile network |
US6658091B1 (en) | 2002-02-01 | 2003-12-02 | @Security Broadband Corp. | LIfestyle multimedia security system |
US10031885B2 (en) * | 2010-02-01 | 2018-07-24 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US8918073B2 (en) | 2002-03-28 | 2014-12-23 | Telecommunication Systems, Inc. | Wireless telecommunications location based services scheme selection |
US8290505B2 (en) | 2006-08-29 | 2012-10-16 | Telecommunications Systems, Inc. | Consequential location derived information |
AU2003260071A1 (en) | 2002-08-27 | 2004-03-19 | Td Security, Inc., Dba Trust Digital, Llc | Enterprise-wide security system for computer devices |
US7296295B2 (en) * | 2002-12-11 | 2007-11-13 | Broadcom Corporation | Media processing system supporting different media formats via server-based transcoding |
US7013127B2 (en) * | 2003-01-07 | 2006-03-14 | Inphonic, Inc. | Systems and methods for employing “pay-as-you-go” telecommunication services |
US7853563B2 (en) | 2005-08-01 | 2010-12-14 | Seven Networks, Inc. | Universal data aggregation |
US7917468B2 (en) | 2005-08-01 | 2011-03-29 | Seven Networks, Inc. | Linking of personal information management data |
US8468126B2 (en) | 2005-08-01 | 2013-06-18 | Seven Networks, Inc. | Publishing data in an information community |
US9420072B2 (en) | 2003-04-25 | 2016-08-16 | Z124 | Smartphone databoost |
US20060266157A1 (en) * | 2003-09-05 | 2006-11-30 | Dai Nippon Toryo Co., Ltd. | Metal fine particles, composition containing the same, and production method for producing metal fine particles |
US7958029B1 (en) * | 2003-10-20 | 2011-06-07 | Thomas Bobich | Method for minimizing financial risk for wireless services |
US7424293B2 (en) | 2003-12-02 | 2008-09-09 | Telecommunication Systems, Inc. | User plane location based service using message tunneling to support roaming |
US7260186B2 (en) | 2004-03-23 | 2007-08-21 | Telecommunication Systems, Inc. | Solutions for voice over internet protocol (VoIP) 911 location services |
US20080126535A1 (en) | 2006-11-28 | 2008-05-29 | Yinjun Zhu | User plane location services over session initiation protocol (SIP) |
US8635661B2 (en) * | 2003-12-23 | 2014-01-21 | Mcafee, Inc. | System and method for enforcing a security policy on mobile devices using dynamically generated security profiles |
US10999298B2 (en) | 2004-03-02 | 2021-05-04 | The 41St Parameter, Inc. | Method and system for identifying users and detecting fraud by use of the internet |
US10339791B2 (en) | 2007-06-12 | 2019-07-02 | Icontrol Networks, Inc. | Security network integrated with premise security system |
US10127802B2 (en) | 2010-09-28 | 2018-11-13 | Icontrol Networks, Inc. | Integrated security system with parallel processing architecture |
US10721087B2 (en) | 2005-03-16 | 2020-07-21 | Icontrol Networks, Inc. | Method for networked touchscreen with integrated interfaces |
US11316958B2 (en) | 2008-08-11 | 2022-04-26 | Icontrol Networks, Inc. | Virtual device systems and methods |
US11368429B2 (en) | 2004-03-16 | 2022-06-21 | Icontrol Networks, Inc. | Premises management configuration and control |
US9729342B2 (en) | 2010-12-20 | 2017-08-08 | Icontrol Networks, Inc. | Defining and implementing sensor triggered response rules |
US20170118037A1 (en) | 2008-08-11 | 2017-04-27 | Icontrol Networks, Inc. | Integrated cloud system for premises automation |
US9141276B2 (en) | 2005-03-16 | 2015-09-22 | Icontrol Networks, Inc. | Integrated interface for mobile device |
US20090077623A1 (en) | 2005-03-16 | 2009-03-19 | Marc Baum | Security Network Integrating Security System and Network Devices |
AU2005223267B2 (en) | 2004-03-16 | 2010-12-09 | Icontrol Networks, Inc. | Premises management system |
US11201755B2 (en) | 2004-03-16 | 2021-12-14 | Icontrol Networks, Inc. | Premises system management using status signal |
US10237237B2 (en) | 2007-06-12 | 2019-03-19 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11113950B2 (en) | 2005-03-16 | 2021-09-07 | Icontrol Networks, Inc. | Gateway integrated with premises security system |
US10200504B2 (en) | 2007-06-12 | 2019-02-05 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US10142392B2 (en) | 2007-01-24 | 2018-11-27 | Icontrol Networks, Inc. | Methods and systems for improved system performance |
US10348575B2 (en) | 2013-06-27 | 2019-07-09 | Icontrol Networks, Inc. | Control system user interface |
US7711796B2 (en) | 2006-06-12 | 2010-05-04 | Icontrol Networks, Inc. | Gateway registry methods and systems |
US10156959B2 (en) | 2005-03-16 | 2018-12-18 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US11159484B2 (en) | 2004-03-16 | 2021-10-26 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US11677577B2 (en) | 2004-03-16 | 2023-06-13 | Icontrol Networks, Inc. | Premises system management using status signal |
US11811845B2 (en) | 2004-03-16 | 2023-11-07 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US8635350B2 (en) | 2006-06-12 | 2014-01-21 | Icontrol Networks, Inc. | IP device discovery systems and methods |
US9531593B2 (en) | 2007-06-12 | 2016-12-27 | Icontrol Networks, Inc. | Takeover processes in security network integrated with premise security system |
US11244545B2 (en) | 2004-03-16 | 2022-02-08 | Icontrol Networks, Inc. | Cross-client sensor user interface in an integrated security network |
US11343380B2 (en) | 2004-03-16 | 2022-05-24 | Icontrol Networks, Inc. | Premises system automation |
US10522026B2 (en) | 2008-08-11 | 2019-12-31 | Icontrol Networks, Inc. | Automation system user interface with three-dimensional display |
US11489812B2 (en) | 2004-03-16 | 2022-11-01 | Icontrol Networks, Inc. | Forming a security network including integrated security system components and network devices |
US11916870B2 (en) | 2004-03-16 | 2024-02-27 | Icontrol Networks, Inc. | Gateway registry methods and systems |
US11582065B2 (en) | 2007-06-12 | 2023-02-14 | Icontrol Networks, Inc. | Systems and methods for device communication |
US11277465B2 (en) | 2004-03-16 | 2022-03-15 | Icontrol Networks, Inc. | Generating risk profile using data of home monitoring and security system |
US7558289B1 (en) * | 2004-06-17 | 2009-07-07 | Marvell International Ltd. | Method and apparatus for providing quality of service (QOS) in a wireless local area network |
US7292198B2 (en) | 2004-08-18 | 2007-11-06 | Ruckus Wireless, Inc. | System and method for an omnidirectional planar antenna apparatus with selectable elements |
US7193562B2 (en) | 2004-11-22 | 2007-03-20 | Ruckus Wireless, Inc. | Circuit board having a peripheral antenna apparatus with selectable antenna elements |
US7358912B1 (en) | 2005-06-24 | 2008-04-15 | Ruckus Wireless, Inc. | Coverage antenna apparatus with selectable horizontal and vertical polarization elements |
US7893882B2 (en) | 2007-01-08 | 2011-02-22 | Ruckus Wireless, Inc. | Pattern shaping of RF emission patterns |
EP1866789B8 (en) * | 2005-02-28 | 2020-04-15 | McAfee, LLC | Mobile data security system and methods |
US7752633B1 (en) | 2005-03-14 | 2010-07-06 | Seven Networks, Inc. | Cross-platform event engine |
US9306809B2 (en) | 2007-06-12 | 2016-04-05 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US20110128378A1 (en) | 2005-03-16 | 2011-06-02 | Reza Raji | Modular Electronic Display Platform |
US20170180198A1 (en) | 2008-08-11 | 2017-06-22 | Marc Baum | Forming a security network including integrated security system components |
US11700142B2 (en) | 2005-03-16 | 2023-07-11 | Icontrol Networks, Inc. | Security network integrating security system and network devices |
US20120324566A1 (en) | 2005-03-16 | 2012-12-20 | Marc Baum | Takeover Processes In Security Network Integrated With Premise Security System |
US11615697B2 (en) | 2005-03-16 | 2023-03-28 | Icontrol Networks, Inc. | Premise management systems and methods |
US10999254B2 (en) | 2005-03-16 | 2021-05-04 | Icontrol Networks, Inc. | System for data routing in networks |
US11496568B2 (en) | 2005-03-16 | 2022-11-08 | Icontrol Networks, Inc. | Security system with networked touchscreen |
US8438633B1 (en) | 2005-04-21 | 2013-05-07 | Seven Networks, Inc. | Flexible real-time inbox access |
US9307397B2 (en) | 2005-04-29 | 2016-04-05 | Jasper Technologies, Inc. | Method for enabling a wireless device with customer-specific services |
US8391161B1 (en) | 2009-05-07 | 2013-03-05 | Jasper Wireless, Inc. | Virtual diagnostic system for wireless communications network systems |
US8867575B2 (en) | 2005-04-29 | 2014-10-21 | Jasper Technologies, Inc. | Method for enabling a wireless device for geographically preferential services |
US8818331B2 (en) | 2005-04-29 | 2014-08-26 | Jasper Technologies, Inc. | Method for enabling a wireless device for geographically preferential services |
US8917611B2 (en) | 2009-05-07 | 2014-12-23 | Jasper Technologies, Inc. | Core services platform for wireless voice, data and messaging network services |
US9226151B2 (en) | 2006-04-04 | 2015-12-29 | Jasper Wireless, Inc. | System and method for enabling a wireless device with customer-specific services |
US9167471B2 (en) | 2009-05-07 | 2015-10-20 | Jasper Technologies, Inc. | System and method for responding to aggressive behavior associated with wireless devices |
WO2006136660A1 (en) | 2005-06-21 | 2006-12-28 | Seven Networks International Oy | Maintaining an ip connection in a mobile network |
US7774402B2 (en) | 2005-06-29 | 2010-08-10 | Visa U.S.A. | Adaptive gateway for switching transactions and data on unreliable networks using context-based rules |
US8660573B2 (en) | 2005-07-19 | 2014-02-25 | Telecommunications Systems, Inc. | Location service requests throttling |
US9282451B2 (en) | 2005-09-26 | 2016-03-08 | Telecommunication Systems, Inc. | Automatic location identification (ALI) service requests steering, connection sharing and protocol translation |
EP1932272B1 (en) | 2005-10-05 | 2013-12-11 | Byres Security Inc. | Network security appliance |
EP1958369B1 (en) | 2005-12-01 | 2015-04-08 | Ruckus Wireless, Inc. | On-demand services by wireless base station virtualization |
US11301585B2 (en) | 2005-12-16 | 2022-04-12 | The 41St Parameter, Inc. | Methods and apparatus for securely displaying digital images |
US11125655B2 (en) | 2005-12-19 | 2021-09-21 | Sas Institute Inc. | Tool for optimal supersaturated designs |
US7769395B2 (en) | 2006-06-20 | 2010-08-03 | Seven Networks, Inc. | Location-based operations and messaging |
CA2867303C (en) | 2006-02-28 | 2015-07-14 | Helvetia Ip Ag | Methods and apparatus for overlapping mimo antenna physical sectors |
US8151327B2 (en) | 2006-03-31 | 2012-04-03 | The 41St Parameter, Inc. | Systems and methods for detection of session tampering and fraud prevention |
US9769655B2 (en) | 2006-04-24 | 2017-09-19 | Ruckus Wireless, Inc. | Sharing security keys with headless devices |
US9071583B2 (en) | 2006-04-24 | 2015-06-30 | Ruckus Wireless, Inc. | Provisioned configuration for automatic wireless connection |
CN103441984B (en) | 2006-04-24 | 2017-09-05 | 鲁库斯无线公司 | Dynamic authentication in safety wireless network |
US8924524B2 (en) * | 2009-07-27 | 2014-12-30 | Vmware, Inc. | Automated network configuration of virtual machines in a virtual lab data environment |
US8208605B2 (en) | 2006-05-04 | 2012-06-26 | Telecommunication Systems, Inc. | Extended efficient usage of emergency services keys |
US8532266B2 (en) | 2006-05-04 | 2013-09-10 | Telecommunication Systems, Inc. | Efficient usage of emergency services keys |
US10079839B1 (en) | 2007-06-12 | 2018-09-18 | Icontrol Networks, Inc. | Activation of gateway device |
US9137844B2 (en) * | 2007-10-04 | 2015-09-15 | Qualcomm Incorporated | Method and apparatus for handling user equipment capability information |
US8584199B1 (en) | 2006-10-17 | 2013-11-12 | A10 Networks, Inc. | System and method to apply a packet routing policy to an application session |
US8312507B2 (en) | 2006-10-17 | 2012-11-13 | A10 Networks, Inc. | System and method to apply network traffic policy to an application session |
US8259568B2 (en) | 2006-10-23 | 2012-09-04 | Mcafee, Inc. | System and method for controlling mobile device access to a network |
US7734379B2 (en) * | 2006-10-23 | 2010-06-08 | Service Pro Monitoring, Llc | System, method, and apparatus for managing wastewater treatment installation |
US10853780B1 (en) * | 2006-12-29 | 2020-12-01 | Amazon Technologies, Inc. | Providing configurable pricing for use of invocable services by applications |
US11706279B2 (en) | 2007-01-24 | 2023-07-18 | Icontrol Networks, Inc. | Methods and systems for data communication |
US8050386B2 (en) | 2007-02-12 | 2011-11-01 | Telecommunication Systems, Inc. | Mobile automatic location identification (ALI) for first responders |
US7633385B2 (en) | 2007-02-28 | 2009-12-15 | Ucontrol, Inc. | Method and system for communicating with and controlling an alarm system from a remote server |
US8533327B2 (en) * | 2007-04-04 | 2013-09-10 | Zte Corporation | System and method of providing services via a peer-to-peer-based next generation network |
US8451986B2 (en) | 2007-04-23 | 2013-05-28 | Icontrol Networks, Inc. | Method and system for automatically providing alternate network access for telecommunications |
US8693494B2 (en) | 2007-06-01 | 2014-04-08 | Seven Networks, Inc. | Polling |
US8805425B2 (en) | 2007-06-01 | 2014-08-12 | Seven Networks, Inc. | Integrated messaging |
US11089122B2 (en) | 2007-06-12 | 2021-08-10 | Icontrol Networks, Inc. | Controlling data routing among networks |
US10666523B2 (en) | 2007-06-12 | 2020-05-26 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US12003387B2 (en) | 2012-06-27 | 2024-06-04 | Comcast Cable Communications, Llc | Control system user interface |
US11218878B2 (en) | 2007-06-12 | 2022-01-04 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11212192B2 (en) | 2007-06-12 | 2021-12-28 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10523689B2 (en) | 2007-06-12 | 2019-12-31 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US11601810B2 (en) | 2007-06-12 | 2023-03-07 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11646907B2 (en) | 2007-06-12 | 2023-05-09 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11316753B2 (en) | 2007-06-12 | 2022-04-26 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US10616075B2 (en) | 2007-06-12 | 2020-04-07 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11237714B2 (en) | 2007-06-12 | 2022-02-01 | Control Networks, Inc. | Control system user interface |
US11423756B2 (en) | 2007-06-12 | 2022-08-23 | Icontrol Networks, Inc. | Communication protocols in integrated systems |
US11831462B2 (en) | 2007-08-24 | 2023-11-28 | Icontrol Networks, Inc. | Controlling data routing in premises management systems |
US8086398B2 (en) | 2007-10-25 | 2011-12-27 | Research In Motion Limited | Sending location information from within a communication application |
US9130963B2 (en) | 2011-04-06 | 2015-09-08 | Telecommunication Systems, Inc. | Ancillary data support in session initiation protocol (SIP) messaging |
US8364181B2 (en) | 2007-12-10 | 2013-01-29 | Seven Networks, Inc. | Electronic-mail filtering for mobile devices |
US9002828B2 (en) | 2007-12-13 | 2015-04-07 | Seven Networks, Inc. | Predictive content delivery |
KR101048449B1 (en) * | 2007-12-18 | 2011-07-11 | 삼성전자주식회사 | Admission control device and method considering multiple service providers in broadband wireless communication system |
US8107921B2 (en) | 2008-01-11 | 2012-01-31 | Seven Networks, Inc. | Mobile virtual network operator |
US8543667B2 (en) * | 2008-01-14 | 2013-09-24 | Akamai Technologies, Inc. | Policy-based content insertion |
US11916928B2 (en) | 2008-01-24 | 2024-02-27 | Icontrol Networks, Inc. | Communication protocols over internet protocol (IP) networks |
US8862657B2 (en) | 2008-01-25 | 2014-10-14 | Seven Networks, Inc. | Policy based content service |
US20090193338A1 (en) | 2008-01-28 | 2009-07-30 | Trevor Fiatal | Reducing network and battery consumption during content delivery and playback |
US8838554B2 (en) * | 2008-02-19 | 2014-09-16 | Bank Of America Corporation | Systems and methods for providing content aware document analysis and modification |
US7904942B2 (en) * | 2008-02-22 | 2011-03-08 | Inventec Corporation | Method of updating intrusion detection rules through link data packet |
US20090211543A1 (en) * | 2008-02-25 | 2009-08-27 | Stephen Gardner Rasmussen | Air cooler |
US20090237209A1 (en) * | 2008-03-20 | 2009-09-24 | Brian William Seal | Communicating keychain |
US8837465B2 (en) | 2008-04-02 | 2014-09-16 | Twilio, Inc. | System and method for processing telephony sessions |
EP3484135A1 (en) | 2008-04-02 | 2019-05-15 | Twilio Inc. | System and method for processing telephony sessions |
CN101577634B (en) * | 2008-05-07 | 2012-01-25 | 华为技术有限公司 | Network-quitting method, network side management device and network system of multi-host system |
US7979899B2 (en) | 2008-06-02 | 2011-07-12 | Microsoft Corporation | Trusted device-specific authentication |
EP2304902B1 (en) * | 2008-06-04 | 2015-04-08 | Nokia Solutions and Networks Oy | Network discovery and selection |
US8626115B2 (en) | 2009-01-28 | 2014-01-07 | Headwater Partners I Llc | Wireless network service interfaces |
US8275830B2 (en) | 2009-01-28 | 2012-09-25 | Headwater Partners I Llc | Device assisted CDR creation, aggregation, mediation and billing |
US8725123B2 (en) | 2008-06-05 | 2014-05-13 | Headwater Partners I Llc | Communications device with secure data path processing agents |
US8346225B2 (en) | 2009-01-28 | 2013-01-01 | Headwater Partners I, Llc | Quality of service for device assisted services |
US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8548428B2 (en) | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Device group partitions and settlement platform |
US8402111B2 (en) | 2009-01-28 | 2013-03-19 | Headwater Partners I, Llc | Device assisted services install |
US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US8898293B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Service offer set publishing to device agent with on-device service selection |
US8270952B2 (en) | 2009-01-28 | 2012-09-18 | Headwater Partners I Llc | Open development system for access service providers |
US8391834B2 (en) | 2009-01-28 | 2013-03-05 | Headwater Partners I Llc | Security techniques for device assisted services |
US8406748B2 (en) | 2009-01-28 | 2013-03-26 | Headwater Partners I Llc | Adaptive ambient services |
US8924543B2 (en) | 2009-01-28 | 2014-12-30 | Headwater Partners I Llc | Service design center for device assisted services |
US8340634B2 (en) | 2009-01-28 | 2012-12-25 | Headwater Partners I, Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8635335B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | System and method for wireless network offloading |
US8924469B2 (en) | 2008-06-05 | 2014-12-30 | Headwater Partners I Llc | Enterprise access control and accounting allocation for access networks |
US9170870B1 (en) | 2013-08-27 | 2015-10-27 | Sprint Communications Company L.P. | Development and testing of payload receipt by a portable electronic device |
US8787947B2 (en) | 2008-06-18 | 2014-07-22 | Seven Networks, Inc. | Application discovery on mobile devices |
GB2473173B (en) * | 2008-06-18 | 2012-11-07 | Ericsson Telefon Ab L M | Method and device for uniform resource identifier handling of user device |
US20170185278A1 (en) | 2008-08-11 | 2017-06-29 | Icontrol Networks, Inc. | Automation system user interface |
US20170070563A1 (en) * | 2008-08-11 | 2017-03-09 | Ken Sundermeyer | Data model for home automation |
US8078158B2 (en) | 2008-06-26 | 2011-12-13 | Seven Networks, Inc. | Provisioning applications for a mobile device |
US8825876B2 (en) * | 2008-07-17 | 2014-09-02 | Qualcomm Incorporated | Apparatus and method for mobile virtual network operator (MVNO) hosting and pricing |
US8171156B2 (en) * | 2008-07-25 | 2012-05-01 | JumpTime, Inc. | Method and system for determining overall content values for content elements in a web network and for optimizing internet traffic flow through the web network |
US9064275B1 (en) | 2008-07-25 | 2015-06-23 | At&T Intellectual Property I, L.P. | Systems and methods for charging and billing in converged communications networks |
WO2010012318A1 (en) * | 2008-07-31 | 2010-02-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, nodes, system, computer programs and computer program products for secure user subscription or registration |
US11792036B2 (en) | 2008-08-11 | 2023-10-17 | Icontrol Networks, Inc. | Mobile premises automation platform |
US11729255B2 (en) | 2008-08-11 | 2023-08-15 | Icontrol Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
US11258625B2 (en) | 2008-08-11 | 2022-02-22 | Icontrol Networks, Inc. | Mobile premises automation platform |
US10530839B2 (en) | 2008-08-11 | 2020-01-07 | Icontrol Networks, Inc. | Integrated cloud system with lightweight gateway for premises automation |
US11758026B2 (en) | 2008-08-11 | 2023-09-12 | Icontrol Networks, Inc. | Virtual device systems and methods |
US9076484B2 (en) | 2008-09-03 | 2015-07-07 | Sandisk Technologies Inc. | Methods for estimating playback time and handling a cumulative playback time permission |
US8468587B2 (en) * | 2008-09-26 | 2013-06-18 | Microsoft Corporation | Binding activation of network-enabled devices to web-based services |
US8964726B2 (en) | 2008-10-01 | 2015-02-24 | Twilio, Inc. | Telephony web event system and method |
US8271974B2 (en) * | 2008-10-08 | 2012-09-18 | Kaavo Inc. | Cloud computing lifecycle management for N-tier applications |
US8909759B2 (en) | 2008-10-10 | 2014-12-09 | Seven Networks, Inc. | Bandwidth measurement |
WO2010054258A1 (en) | 2008-11-06 | 2010-05-14 | Trust Digital | System and method for mediating connections between policy source servers, corporate repositories, and mobile devices |
US8484462B2 (en) * | 2008-11-07 | 2013-07-09 | Lockheed Martin Corporation | System and method for establishing a self-realizing expandable communications network |
US8479266B1 (en) | 2008-11-13 | 2013-07-02 | Sprint Communications Company L.P. | Network assignment appeal architecture and process |
US8363658B1 (en) | 2008-11-13 | 2013-01-29 | Sprint Communications Company L.P. | Dynamic firewall and dynamic host configuration protocol configuration |
US8341717B1 (en) * | 2008-11-13 | 2012-12-25 | Sprint Communications Company L.P. | Dynamic network policies based on device classification |
US8630683B2 (en) * | 2008-11-24 | 2014-01-14 | Centurylink Intellectual Property Llc | System and method for displaying information associated with a cellular device on a user specified display unit |
US10311446B2 (en) * | 2008-12-05 | 2019-06-04 | Nokia Technologies Oy | Method and apparatus for obfuscating context information |
US8464256B1 (en) | 2009-04-10 | 2013-06-11 | Open Invention Network, Llc | System and method for hierarchical interception with isolated environments |
US8539488B1 (en) | 2009-04-10 | 2013-09-17 | Open Invention Network, Llc | System and method for application isolation with live migration |
US8638804B2 (en) * | 2010-06-04 | 2014-01-28 | Broadcom Corporation | Method and system for recognizing energy efficient certified devices through a gateway |
IES20090031A2 (en) * | 2009-01-16 | 2009-10-14 | Openet Res Ltd | A method and system for policy control in telecommunications services |
US8977565B2 (en) * | 2009-01-23 | 2015-03-10 | Cfph, Llc | Interprogram communication using messages related to groups of orders |
US10715342B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US10841839B2 (en) | 2009-01-28 | 2020-11-17 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US9954975B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US9858559B2 (en) | 2009-01-28 | 2018-01-02 | Headwater Research Llc | Network service plan design |
US10200541B2 (en) | 2009-01-28 | 2019-02-05 | Headwater Research Llc | Wireless end-user device with divided user space/kernel space traffic policy system |
US10064055B2 (en) | 2009-01-28 | 2018-08-28 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10779177B2 (en) | 2009-01-28 | 2020-09-15 | Headwater Research Llc | Device group partitions and settlement platform |
US10484858B2 (en) | 2009-01-28 | 2019-11-19 | Headwater Research Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US10783581B2 (en) | 2009-01-28 | 2020-09-22 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
US9578182B2 (en) | 2009-01-28 | 2017-02-21 | Headwater Partners I Llc | Mobile device and service management |
US9755842B2 (en) | 2009-01-28 | 2017-09-05 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US8351898B2 (en) | 2009-01-28 | 2013-01-08 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US9647918B2 (en) | 2009-01-28 | 2017-05-09 | Headwater Research Llc | Mobile device and method attributing media services network usage to requesting application |
US11985155B2 (en) | 2009-01-28 | 2024-05-14 | Headwater Research Llc | Communications device with secure data path processing agents |
US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
US10237757B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | System and method for wireless network offloading |
US8745191B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
US8793758B2 (en) | 2009-01-28 | 2014-07-29 | Headwater Partners I Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US9571559B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners I Llc | Enhanced curfew and protection associated with a device group |
US9706061B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Service design center for device assisted services |
US8893009B2 (en) | 2009-01-28 | 2014-11-18 | Headwater Partners I Llc | End user device that secures an association of application to service policy with an application certificate check |
US9392462B2 (en) | 2009-01-28 | 2016-07-12 | Headwater Partners I Llc | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
US10057775B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Virtualized policy and charging system |
US11218854B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US9565707B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Wireless end-user device with wireless data attribution to multiple personas |
US9557889B2 (en) | 2009-01-28 | 2017-01-31 | Headwater Partners I Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US11973804B2 (en) | 2009-01-28 | 2024-04-30 | Headwater Research Llc | Network service plan design |
US9980146B2 (en) | 2009-01-28 | 2018-05-22 | Headwater Research Llc | Communications device with secure data path processing agents |
US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
US8606911B2 (en) | 2009-03-02 | 2013-12-10 | Headwater Partners I Llc | Flow tagging for service policy implementation |
US9270559B2 (en) | 2009-01-28 | 2016-02-23 | Headwater Partners I Llc | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
US10798252B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | System and method for providing user notifications |
US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
US9351193B2 (en) | 2009-01-28 | 2016-05-24 | Headwater Partners I Llc | Intermediate networking devices |
US9253663B2 (en) | 2009-01-28 | 2016-02-02 | Headwater Partners I Llc | Controlling mobile device communications on a roaming network based on device state |
US8977232B2 (en) * | 2009-01-29 | 2015-03-10 | Qualcomm Incorporated | Certified device-based accounting |
US8705523B2 (en) * | 2009-02-05 | 2014-04-22 | Google Inc. | Conjoined class-based networking |
JP2010178867A (en) * | 2009-02-05 | 2010-08-19 | Fujifilm Corp | Radiography network system and radiographic image capturing system control method |
US9036541B2 (en) | 2009-02-17 | 2015-05-19 | T-Mobile Usa, Inc. | Location-based IMS server selection |
US8977750B2 (en) * | 2009-02-24 | 2015-03-10 | Red Hat, Inc. | Extending security platforms to cloud-based networks |
US8315369B2 (en) | 2009-03-02 | 2012-11-20 | Twilio, Inc. | Method and system for a multitenancy telephone network |
US8280842B2 (en) * | 2009-03-03 | 2012-10-02 | Xerox Corporation | Collaborative linking of support knowledge bases with visualization of device |
US9614685B2 (en) * | 2009-03-09 | 2017-04-04 | Nokia Technologies Oy | Methods, apparatuses, and computer program products for facilitating synchronization of setting configurations |
US8266673B2 (en) | 2009-03-12 | 2012-09-11 | At&T Mobility Ii Llc | Policy-based privacy protection in converged communication networks |
US8217843B2 (en) | 2009-03-13 | 2012-07-10 | Ruckus Wireless, Inc. | Adjustment of radiation patterns utilizing a position sensor |
US9112850B1 (en) | 2009-03-25 | 2015-08-18 | The 41St Parameter, Inc. | Systems and methods of sharing information through a tag-based consortium |
US8391884B2 (en) * | 2009-03-26 | 2013-03-05 | Andrew Llc | System and method for managing created location contexts in a location server |
JP4811486B2 (en) * | 2009-03-26 | 2011-11-09 | ブラザー工業株式会社 | Program, information processing system, and information processing apparatus |
US8560675B2 (en) * | 2009-04-01 | 2013-10-15 | Comscore, Inc. | Determining projection weights based on a census data |
US8490176B2 (en) * | 2009-04-07 | 2013-07-16 | Juniper Networks, Inc. | System and method for controlling a mobile device |
US8340633B1 (en) * | 2009-04-09 | 2012-12-25 | Mobile Iron, Inc. | Mobile activity intelligence |
US8935773B2 (en) * | 2009-04-09 | 2015-01-13 | George Mason Research Foundation, Inc. | Malware detector |
US9577893B1 (en) | 2009-04-10 | 2017-02-21 | Open Invention Network Llc | System and method for cached streaming application isolation |
US11538078B1 (en) * | 2009-04-10 | 2022-12-27 | International Business Machines Corporation | System and method for usage billing of hosted applications |
US8401940B1 (en) * | 2009-04-10 | 2013-03-19 | Open Invention Network Llc | System and method for usage billing of hosted applications |
US8401941B1 (en) * | 2009-04-10 | 2013-03-19 | Open Invention Network Llc | System and method for usage billing of hosted applications |
US8555360B1 (en) | 2009-04-10 | 2013-10-08 | Open Invention Network Llc | System and method for on-line and off-line streaming application isolation |
US10419504B1 (en) | 2009-04-10 | 2019-09-17 | Open Invention Network Llc | System and method for streaming application isolation |
US8418236B1 (en) | 2009-04-10 | 2013-04-09 | Open Invention Network Llc | System and method for streaming application isolation |
US9058599B1 (en) * | 2009-04-10 | 2015-06-16 | Open Invention Network, Llc | System and method for usage billing of hosted applications |
US10326848B2 (en) * | 2009-04-17 | 2019-06-18 | Empirix Inc. | Method for modeling user behavior in IP networks |
US9715681B2 (en) | 2009-04-28 | 2017-07-25 | Visa International Service Association | Verification of portable consumer devices |
US8271634B2 (en) * | 2009-04-30 | 2012-09-18 | Alcatel Lucent | Buffer system for managing service measurement requests |
US8638211B2 (en) | 2009-04-30 | 2014-01-28 | Icontrol Networks, Inc. | Configurable controller and interface for home SMA, phone and multimedia |
US8867485B2 (en) | 2009-05-05 | 2014-10-21 | Telecommunication Systems, Inc. | Multiple location retrieval function (LRF) network having location continuity |
FR2945396A1 (en) * | 2009-05-07 | 2010-11-12 | St Microelectronics Grenoble 2 | METHOD AND DEVICE FOR ANALYZING THE PROPAGATION OF TRANSACTIONS IN A MULTI-PROTOCOL NETWORK OF A SYSTEM ON CHIP |
US8897146B2 (en) | 2009-05-07 | 2014-11-25 | Jasper Technologies, Inc. | Core services platform for wireless voice, data and messaging network services |
US9501329B2 (en) * | 2009-05-08 | 2016-11-22 | Rackspace Us, Inc. | Methods and systems for cloud computing management |
US8719414B2 (en) * | 2009-05-12 | 2014-05-06 | Centurylink Intellectual Property Llc | Multi-source broadband aggregation router |
US8893967B2 (en) | 2009-05-15 | 2014-11-25 | Visa International Service Association | Secure Communication of payment information to merchants using a verification token |
US8534564B2 (en) | 2009-05-15 | 2013-09-17 | Ayman Hammad | Integration of verification tokens with mobile communication devices |
US9038886B2 (en) * | 2009-05-15 | 2015-05-26 | Visa International Service Association | Verification of portable consumer devices |
US9105027B2 (en) | 2009-05-15 | 2015-08-11 | Visa International Service Association | Verification of portable consumer device for secure services |
US8665783B2 (en) * | 2009-05-20 | 2014-03-04 | Centurylink Intellectual Property Llc | Dynamic multi-point access network |
US9734496B2 (en) * | 2009-05-29 | 2017-08-15 | Paypal, Inc. | Trusted remote attestation agent (TRAA) |
US8341250B2 (en) * | 2009-05-30 | 2012-12-25 | Cisco Technology, Inc. | Networking device provisioning |
US7996526B2 (en) | 2009-06-08 | 2011-08-09 | Comcast Cable Communications, Llc | Management of shared access network |
EP2441283A4 (en) * | 2009-06-08 | 2014-10-22 | Ericsson Telefon Ab L M | Investigating a communication aspect of a data flow |
US8606232B2 (en) * | 2009-06-08 | 2013-12-10 | Qualcomm Incorporated | Method and system for performing multi-stage virtual SIM provisioning and setup on mobile devices |
US20130276054A1 (en) | 2012-04-13 | 2013-10-17 | Paul Michael Martini | Recording activity-triggered computer video output |
CN101576989A (en) * | 2009-06-09 | 2009-11-11 | 阿里巴巴集团控股有限公司 | Method for realizing payment in mobile terminal and mobile device |
US8214487B2 (en) | 2009-06-10 | 2012-07-03 | At&T Intellectual Property I, L.P. | System and method to determine network usage |
CN101931931B (en) * | 2009-06-25 | 2014-03-12 | 华为技术有限公司 | Information process method, system and mobility management network element |
SE535002C2 (en) * | 2009-07-06 | 2012-03-13 | Synapse Int Sa | A method and system for handling roaming of a mobile device |
US8942215B2 (en) | 2010-07-15 | 2015-01-27 | Dejero Labs Inc. | System and method for transmission of data from a wireless mobile device over a multipath wireless router |
US10117055B2 (en) | 2009-07-08 | 2018-10-30 | Dejero Labs Inc. | System and method for providing data services on vehicles |
US10033779B2 (en) | 2009-07-08 | 2018-07-24 | Dejero Labs Inc. | Multipath data streaming over multiple wireless networks |
US9756468B2 (en) | 2009-07-08 | 2017-09-05 | Dejero Labs Inc. | System and method for providing data services on vehicles |
US10165286B2 (en) | 2009-07-08 | 2018-12-25 | Dejero Labs Inc. | System and method for automatic encoder adjustment based on transport data |
US8873560B2 (en) * | 2009-07-08 | 2014-10-28 | Dejero Labs Inc. | Multipath video streaming over a wireless network |
WO2011003456A1 (en) * | 2009-07-10 | 2011-01-13 | Nokia Siemens Networks Oy | Methods, apparatuses, related computer program product and data structure for distributed storage of service provision-related information |
CN101945411B (en) * | 2009-07-10 | 2013-05-29 | 电信科学技术研究院 | Method and device for maintaining LTE base station |
US8296822B2 (en) * | 2009-07-14 | 2012-10-23 | Microsoft Corporation | State-updating authorization |
US8380836B2 (en) * | 2009-07-24 | 2013-02-19 | Broadcom Corporation | Method and system for leasing of network services and applications based on a usage pattern |
US20110019626A1 (en) * | 2009-07-24 | 2011-01-27 | Jeyhan Karaoguz | Method and system for network resource allocation based on a usage pattern |
US8121633B2 (en) * | 2009-07-24 | 2012-02-21 | Research In Motion Limited | Operator configurable preferred network and radio access technology selection for roaming multi-rat capable devices |
CN101964740A (en) * | 2009-07-24 | 2011-02-02 | 中兴通讯股份有限公司 | Method and device for distributing service traffic |
US9886696B2 (en) * | 2009-07-29 | 2018-02-06 | Shopkick, Inc. | Method and system for presence detection |
US8116757B2 (en) * | 2009-07-29 | 2012-02-14 | Intel Corporation | Virtual network service provider for mobile virtual network operator activation |
US8548417B2 (en) * | 2009-08-10 | 2013-10-01 | Freeport Technologies, Inc. | Secure control for desktop secure video teleconferencing |
JP5398410B2 (en) * | 2009-08-10 | 2014-01-29 | アラクサラネットワークス株式会社 | Network system, packet transfer apparatus, packet transfer method, and computer program |
CN101640787B (en) * | 2009-08-24 | 2011-10-26 | 中兴通讯股份有限公司 | Method and device for hierarchical control access of multicast group |
US8688095B2 (en) * | 2009-08-26 | 2014-04-01 | At&T Intellectual Property I, L.P. | Multiple user profiles and personas on a device |
US8234408B2 (en) | 2009-09-10 | 2012-07-31 | Cloudshield Technologies, Inc. | Differentiating unique systems sharing a common address |
US9734037B1 (en) * | 2009-09-15 | 2017-08-15 | Symantec Corporation | Mobile application sampling for performance and network behavior profiling |
US8471707B2 (en) | 2009-09-25 | 2013-06-25 | Intel Corporation | Methods and arrangements for smart sensors |
CN101674268A (en) * | 2009-09-25 | 2010-03-17 | 中兴通讯股份有限公司 | Internet access control device and method and gateway thereof |
US8141784B2 (en) | 2009-09-25 | 2012-03-27 | Hand Held Products, Inc. | Encoded information reading terminal with user-configurable multi-protocol wireless communication interface |
US8347362B2 (en) * | 2009-09-30 | 2013-01-01 | Alcatel Lucent | Usage control services performed in an end user device |
CN102782710B (en) | 2009-10-07 | 2016-08-24 | 鲁库斯无线公司 | The computer network services performing function including self-adjusting flow provides system |
US9210275B2 (en) | 2009-10-07 | 2015-12-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
US20110082719A1 (en) * | 2009-10-07 | 2011-04-07 | Tokoni Inc. | System and method for determining aggregated tracking metrics for user activities |
US8234138B2 (en) * | 2009-10-07 | 2012-07-31 | Xerox Corporation | Method and system to associate device models and accounts by utilization bands |
US8958770B2 (en) * | 2009-10-12 | 2015-02-17 | At&T Mobility Ii Llc | Dynamic usage inequity detection and/or remedy |
KR101679428B1 (en) * | 2009-10-16 | 2016-11-25 | 삼성전자주식회사 | Apparatus and method of establishing personal network for providing cpns service |
US8434121B2 (en) | 2009-10-16 | 2013-04-30 | At&T Intellectual Property I, L.P. | System and method for monitoring whole home digital video recorder usage for internet protocol television |
US8589264B2 (en) * | 2009-10-19 | 2013-11-19 | International Business Machines Corporation | Token licensing mapping costs to enabled software tool features |
US8543086B2 (en) * | 2009-10-20 | 2013-09-24 | Mgm Wireless Holdings Pty Ltd | System for schools managing SMS credits using mobile reverse charge technology |
EP2491740A1 (en) * | 2009-10-23 | 2012-08-29 | Telefonaktiebolaget L M Ericsson (PUBL) | Arrangements and methods in communication nodes |
US20110098030A1 (en) * | 2009-10-27 | 2011-04-28 | Nokia Corporation | Method and apparatus for activating services |
US8767544B1 (en) * | 2009-11-10 | 2014-07-01 | Sprint Communications Company L.P. | Data rate selection for wireless communication devices |
US20110119104A1 (en) * | 2009-11-17 | 2011-05-19 | Xerox Corporation | Individualized behavior-based service bundling and pricing |
US8645459B2 (en) * | 2009-11-18 | 2014-02-04 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for a service provisioning platform for activating services in a communication network |
KR20110055095A (en) * | 2009-11-19 | 2011-05-25 | 삼성전자주식회사 | Apparatus and method for preventing charge by utilizing application in portable terminal |
US8886805B2 (en) * | 2009-11-19 | 2014-11-11 | Flash Networks, Ltd | Method and system for dynamically allocating services for subscribers data traffic |
US8255702B1 (en) * | 2009-12-03 | 2012-08-28 | Altera Corporation | Programmable logic device with improved security |
US8271655B2 (en) * | 2009-12-03 | 2012-09-18 | International Business Machines Corporation | Cloud computing roaming services |
KR101316681B1 (en) * | 2009-12-08 | 2013-10-10 | 한국전자통신연구원 | Model-based customized eco system and method for design of the eco system |
US20110138009A1 (en) * | 2009-12-09 | 2011-06-09 | Nancy Grover | Methods, Systems and Computer Program Products for Tracking Creations on the Internet |
US8600850B2 (en) * | 2009-12-10 | 2013-12-03 | Redknee Inc. | Feedback loop for dynamic network resource allocation |
US8171529B2 (en) * | 2009-12-17 | 2012-05-01 | Intel Corporation | Secure subscriber identity module service |
US8387119B2 (en) * | 2009-12-21 | 2013-02-26 | Ebay Inc. | Secure application network |
US8112062B2 (en) * | 2009-12-22 | 2012-02-07 | Cellco Partnership | System and method for sending threshold notification in real time |
FI123336B (en) * | 2009-12-23 | 2013-02-28 | 7Signal Oy | A method for monitoring and intelligently adjusting radio network parameters |
US20110161452A1 (en) * | 2009-12-24 | 2011-06-30 | Rajesh Poornachandran | Collaborative malware detection and prevention on mobile devices |
US8611344B2 (en) * | 2009-12-28 | 2013-12-17 | At&T Intellectual Property I, L.P. | Method and apparatus for providing multi-homing to an aggregate endpoint device |
PL2520066T3 (en) * | 2009-12-30 | 2019-03-29 | Nokia Solutions And Networks Oy | Service access |
US8484366B2 (en) * | 2010-01-05 | 2013-07-09 | Accenture Global Services Limited | Hierarchical service management |
CN102859931A (en) * | 2010-01-12 | 2013-01-02 | 华为技术有限公司 | Charging method, device and system |
US9118934B2 (en) | 2010-01-18 | 2015-08-25 | Sprint Communications Company L.P. | Integration of remote electronic device with media local area network |
US9104659B2 (en) * | 2010-01-20 | 2015-08-11 | Bank Of America Corporation | Systems and methods for providing content aware document analysis and modification |
EP2365416A1 (en) * | 2010-02-02 | 2011-09-14 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling operations of devices based on information about power consumption of the devices |
US9794647B1 (en) | 2010-02-02 | 2017-10-17 | Sprint Communications Company L.P. | Centralized program guide |
US8340689B2 (en) | 2010-02-06 | 2012-12-25 | Microsoft Corporation | Commercially subsidized mobile communication devices and services |
US8850584B2 (en) * | 2010-02-08 | 2014-09-30 | Mcafee, Inc. | Systems and methods for malware detection |
US20110196690A1 (en) * | 2010-02-10 | 2011-08-11 | DSNR Media Group Ltd. | Method and system of selecting landing pages and optimizing routing efficiency |
US20110202646A1 (en) * | 2010-02-14 | 2011-08-18 | Bhatia Randeep S | Policy controlled traffic offload via content smart-loading |
US9020479B1 (en) | 2010-02-18 | 2015-04-28 | Amazon Technologies, Inc. | Single version of a user device modem for use with different wireless carriers |
US8626165B1 (en) | 2010-02-18 | 2014-01-07 | Amazon Technologies, Inc. | Dynamic carrier switching |
US8965366B1 (en) * | 2010-02-18 | 2015-02-24 | Amazon Technologies, Inc. | World SIM |
US8862178B2 (en) * | 2010-02-24 | 2014-10-14 | Qualcomm Incorporated | Methods and systems for managing participation in multiple wireless networks |
US9424413B2 (en) | 2010-02-24 | 2016-08-23 | Visa International Service Association | Integration of payment capability into secure elements of computers |
US8873482B2 (en) * | 2010-03-01 | 2014-10-28 | Nec Laboratories America, Inc. | Method and system for virtualizing a cellular basestation |
US9544143B2 (en) | 2010-03-03 | 2017-01-10 | Duo Security, Inc. | System and method of notifying mobile devices to complete transactions |
US9185510B2 (en) | 2010-03-03 | 2015-11-10 | Tekelec, Inc. | Methods, systems, and computer readable media for managing the roaming preferences of mobile subscribers |
US9532222B2 (en) | 2010-03-03 | 2016-12-27 | Duo Security, Inc. | System and method of notifying mobile devices to complete transactions after additional agent verification |
US20130040685A1 (en) * | 2010-03-09 | 2013-02-14 | Alcatel Lucent | Method and apparatus for controlling quality of service of user equipment |
US9917700B2 (en) | 2010-03-15 | 2018-03-13 | Tekelec, Inc. | Systems, methods, and computer readable media for policy enforcement correlation |
US8230061B2 (en) * | 2010-03-17 | 2012-07-24 | Microsoft Corporation | Network resource management with prediction |
US20110238498A1 (en) * | 2010-03-29 | 2011-09-29 | Microsoft Corporation | Service stage for subscription management |
WO2011120218A1 (en) * | 2010-03-30 | 2011-10-06 | Huawei Technologies Co., Ltd. | Method for re-selecting a communication network |
US8396946B1 (en) * | 2010-03-31 | 2013-03-12 | Amazon Technologies, Inc. | Managing integration of external nodes into provided computer networks |
JP5575325B2 (en) * | 2010-04-01 | 2014-08-20 | アルカテル−ルーセント | Quality of service throttling for mobile devices |
US20110251921A1 (en) * | 2010-04-09 | 2011-10-13 | Ebay Inc. | Method and system to facilitate billing of embedded applications in a serving platform |
CA2796992C (en) * | 2010-04-22 | 2017-01-10 | Allot Communications, Ltd. | Predictive internet traffic steering |
US9442178B2 (en) * | 2010-04-23 | 2016-09-13 | Qualcomm Incorporated | Hybrid tracking device |
US8472974B2 (en) * | 2010-04-28 | 2013-06-25 | T-Mobile Usa, Inc. | Location continuity service for locating mobile devices using multiple access networks including wireless telecommunication networks |
US9094927B2 (en) | 2010-04-28 | 2015-07-28 | T-Mobile Usa, Inc. | Location continuity service for locating mobile devices using multiple access networks including wireless telecommunication networks |
US8538405B2 (en) | 2010-04-29 | 2013-09-17 | T-Mobile Usa, Inc. | Communication protocol preferences |
US20120198046A1 (en) * | 2010-04-29 | 2012-08-02 | Mehul Jayant Shah | Mobile device bandwidth throttling |
US9204478B2 (en) | 2013-05-10 | 2015-12-01 | Elwha Llc | Dynamic point to point mobile network including intermediate user interface aspects system and method |
GB2480080B (en) * | 2010-05-05 | 2012-10-24 | Vodafone Ip Licensing Ltd | Telecommunications networks |
US8935384B2 (en) * | 2010-05-06 | 2015-01-13 | Mcafee Inc. | Distributed data revocation using data commands |
EP2569712B1 (en) | 2010-05-10 | 2021-10-13 | Icontrol Networks, Inc. | Control system user interface |
US8805922B2 (en) | 2010-05-14 | 2014-08-12 | Stephen Ball | System and method for negotiating a network connection |
GB201008368D0 (en) * | 2010-05-20 | 2010-07-07 | Moore Jesse K | Mobile meter |
US20120036263A1 (en) * | 2010-05-21 | 2012-02-09 | Open Subnet Inc. | System and Method for Monitoring and Controlling Access to Web Content |
WO2011153155A2 (en) | 2010-05-30 | 2011-12-08 | Sonian, Inc. | Method and system for arbitraging computing resources in a cloud computing environment |
CN102264087A (en) * | 2010-05-31 | 2011-11-30 | 中兴通讯股份有限公司 | Method and system for managing states or events of terminal in M2M business |
US8358640B1 (en) * | 2010-06-01 | 2013-01-22 | Sprint Communications Company L.P. | Femtocell bridging in media local area networks |
US8892068B2 (en) * | 2010-06-04 | 2014-11-18 | Verizon Patent And Licensing Inc. | Real-time usage monitoring for communication devices |
US8750857B2 (en) | 2010-06-04 | 2014-06-10 | Qualcomm Incorporated | Method and apparatus for wireless distributed computing |
GB201009649D0 (en) | 2010-06-09 | 2010-07-21 | Roke Manor Research | Mobile device and method |
US20110307541A1 (en) * | 2010-06-10 | 2011-12-15 | Microsoft Corporation | Server load balancing and draining in enhanced communication systems |
US8554835B1 (en) * | 2010-06-11 | 2013-10-08 | Robert Gordon Williams | System and method for secure social networking |
US20110307389A1 (en) * | 2010-06-15 | 2011-12-15 | Opensky Project, Inc. | Method and System for Distributed Point of Sale Transactions |
GB2481254B (en) * | 2010-06-18 | 2017-07-12 | Skype | Determining network quality |
US8838046B2 (en) | 2010-06-18 | 2014-09-16 | Mediatek Inc. | System and method of hybrid FDM/TDM coexistence interference avoidance |
JP5687335B2 (en) * | 2010-06-18 | 2015-03-18 | 聯發科技股▲ふん▼有限公司Mediatek Inc. | System and method for coordinating multiple radio transceivers in the same device platform |
EP2583189B1 (en) | 2010-06-18 | 2018-09-19 | Akamai Technologies, Inc. | Extending a content delivery network (cdn) into a mobile or wireline network |
US9338064B2 (en) | 2010-06-23 | 2016-05-10 | Twilio, Inc. | System and method for managing a computing cluster |
US20120208495A1 (en) | 2010-06-23 | 2012-08-16 | Twilio, Inc. | System and method for monitoring account usage on a platform |
US9459926B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US9590849B2 (en) | 2010-06-23 | 2017-03-07 | Twilio, Inc. | System and method for managing a computing cluster |
US9459925B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US20110320252A1 (en) * | 2010-06-24 | 2011-12-29 | Mobile Media Solutions, Inc. | Apparatus and Method for Redeeming an Incentive on a Wireless Device |
US8838707B2 (en) | 2010-06-25 | 2014-09-16 | Twilio, Inc. | System and method for enabling real-time eventing |
GB201010821D0 (en) * | 2010-06-28 | 2011-03-30 | Nokia Oyj | Mehtod and apparatus for communicating via a gateway |
US8559324B1 (en) * | 2010-06-29 | 2013-10-15 | Amazon Technologies, Inc. | Network routing metering |
SG186910A1 (en) | 2010-07-09 | 2013-02-28 | Visa Int Service Ass | Gateway abstraction layer |
US9460471B2 (en) | 2010-07-16 | 2016-10-04 | Hartford Fire Insurance Company | System and method for an automated validation system |
US9232046B2 (en) * | 2010-07-21 | 2016-01-05 | Tksn Holdings, Llc | System and method for controlling mobile services using sensor information |
US20120021770A1 (en) | 2010-07-21 | 2012-01-26 | Naqvi Shamim A | System and method for control and management of resources for consumers of information |
US9210528B2 (en) | 2010-07-21 | 2015-12-08 | Tksn Holdings, Llc | System and method for control and management of resources for consumers of information |
WO2013015835A1 (en) | 2011-07-22 | 2013-01-31 | Seven Networks, Inc. | Mobile application traffic optimization |
GB2495066B (en) | 2010-07-26 | 2013-12-18 | Seven Networks Inc | Mobile application traffic optimization |
CA2806527A1 (en) | 2010-07-26 | 2012-02-09 | Seven Networks, Inc. | Mobile network traffic coordination across multiple applications |
US8838783B2 (en) | 2010-07-26 | 2014-09-16 | Seven Networks, Inc. | Distributed caching for resource and mobile network traffic management |
EP2413279B1 (en) * | 2010-07-29 | 2016-03-30 | Accenture Global Services Limited | Account reconciliation server |
CN101909058B (en) * | 2010-07-30 | 2013-01-16 | 天维讯达无线电设备检测(北京)有限责任公司 | Platform authentication strategy management method and system suitable for credible connecting architecture |
US20120029974A1 (en) * | 2010-07-30 | 2012-02-02 | International Business Machines Corporation | Complex service modeling |
WO2012015902A1 (en) * | 2010-07-30 | 2012-02-02 | Interdigital Patent Holdings, Inc. | Method and apparatus for managing and processing policy profile restrictions |
US8732697B2 (en) | 2010-08-04 | 2014-05-20 | Premkumar Jonnala | System, method and apparatus for managing applications on a device |
US8737924B2 (en) | 2010-08-12 | 2014-05-27 | Mediatek Inc. | Method to trigger in-device coexistence interference mitigation in mobile cellular systems |
US8966590B2 (en) * | 2010-08-17 | 2015-02-24 | Facebook, Inc. | Managing social network accessibility based on age |
US9184983B2 (en) | 2010-08-26 | 2015-11-10 | Futurewei Technologies, Inc. | Cross-stratum optimization protocol |
US8838087B1 (en) | 2010-09-06 | 2014-09-16 | Sprint Communications Company L.P. | Provisioning system and methods for interfaceless phone |
US8583091B1 (en) | 2010-09-06 | 2013-11-12 | Sprint Communications Company L.P. | Dynamic loading, unloading, and caching of alternate complete interfaces |
RU2564251C2 (en) * | 2010-09-16 | 2015-09-27 | Нокиа Корпорейшн | Dynamic creation of account in protected network with wireless access point |
KR101867636B1 (en) | 2010-09-20 | 2018-06-14 | 헤드워터 리서치 엘엘씨 | Adapting network policies based on device service processor configuration |
CA2811577C (en) * | 2010-09-21 | 2017-10-10 | Headwater Partners I Llc | Service offer set publishing to device agent with on-device service selection |
US9021108B2 (en) * | 2010-09-27 | 2015-04-28 | Blackberry Limited | Method, system and apparatus for enabling access of a first mobile electronic device to at least one network accessible by a second mobile electronic device |
US8836467B1 (en) | 2010-09-28 | 2014-09-16 | Icontrol Networks, Inc. | Method, system and apparatus for automated reporting of account and sensor zone information to a central station |
AU2011312874B2 (en) * | 2010-09-28 | 2016-01-14 | Headwater Research Llc | Enterprise access control and accounting allocation for access networks |
US8615772B2 (en) * | 2010-09-28 | 2013-12-24 | Qualcomm Incorporated | Apparatus and methods of extending application services |
BR112013006890A2 (en) * | 2010-09-28 | 2020-06-02 | Headwater Partners I Llc | COMMUNICATIONS DEVICE AND NETWORK SYSTEM |
US8582458B2 (en) * | 2010-09-29 | 2013-11-12 | At&T Intellectual Property I, L.P. | Femtocell automatic speed test |
EP2437434A1 (en) * | 2010-09-30 | 2012-04-04 | British Telecommunications Public Limited Company | Monitoring of data traffic based on user profiles |
AU2014265092B2 (en) * | 2010-09-30 | 2016-06-23 | Amazon Technologies, Inc. | Virtual resource cost tracking with dedicated implementation resources |
AU2011314183B2 (en) * | 2010-09-30 | 2014-09-04 | Amazon Technologies, Inc. | Virtual resource cost tracking with dedicated implementation resources |
US10013662B2 (en) * | 2010-09-30 | 2018-07-03 | Amazon Technologies, Inc. | Virtual resource cost tracking with dedicated implementation resources |
US11106479B2 (en) | 2010-09-30 | 2021-08-31 | Amazon Technologies, Inc. | Virtual provisioning with implementation resource boundary awareness |
US8918467B2 (en) * | 2010-10-01 | 2014-12-23 | Clover Leaf Environmental Solutions, Inc. | Generation and retrieval of report information |
US8780880B2 (en) | 2010-10-01 | 2014-07-15 | Mediatek Singapore Pte, Ltd. | Method of TDM in-device coexistence interference avoidance |
US8516062B2 (en) | 2010-10-01 | 2013-08-20 | @Pay Ip Holdings Llc | Storage, communication, and display of task-related data |
US20120084187A1 (en) * | 2010-10-01 | 2012-04-05 | Smith Micro Software, Inc. | System and Method for Managing Billing for Hotspot Network Access |
KR101314201B1 (en) * | 2010-10-04 | 2013-10-02 | 엠파이어 테크놀로지 디벨롭먼트 엘엘씨 | Information processing device and program |
KR101768743B1 (en) | 2010-10-04 | 2017-08-16 | 헤드워터 리서치 엘엘씨 | System and method for providing user notifications |
US8943209B2 (en) * | 2010-10-07 | 2015-01-27 | Tekelec, Inc. | Methods, systems, and computer readable media for policy and charging rules function (PCRF) fault tolerance |
US8645509B2 (en) * | 2010-10-12 | 2014-02-04 | Guest Tek Interactive Entertainment Ltd. | System and server for assigning location-dependent hostname to client device over network and method thereof |
US9565318B2 (en) * | 2010-10-14 | 2017-02-07 | T-Mobile Usa, Inc. | Quality of service adjustments to improve network utilization |
US8787875B2 (en) * | 2010-10-22 | 2014-07-22 | Affirmed Networks, Inc. | Aggregating multiple functions into a single platform |
WO2012055013A1 (en) * | 2010-10-25 | 2012-05-03 | Research In Motion Limited | System and method for enabling applications to communicate using a peer-to-peer (p2p) system |
US9723463B2 (en) * | 2010-10-25 | 2017-08-01 | Nokia Technologies Oy | Method and apparatus for a device identifier based solution for user identification |
US9203969B2 (en) * | 2010-10-26 | 2015-12-01 | Vonage Network, Llc | Systems and methods for integrating information from voice over internet protocol systems and social networking systems |
US20120109817A1 (en) * | 2010-10-28 | 2012-05-03 | Robert Villalobos | Product and Method of Providing First Class Customer Service or Product Support |
US8484314B2 (en) | 2010-11-01 | 2013-07-09 | Seven Networks, Inc. | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
EP2635973A4 (en) | 2010-11-01 | 2014-01-15 | Seven Networks Inc | Caching adapted for mobile application behavior and network conditions |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
WO2012061194A2 (en) | 2010-11-01 | 2012-05-10 | Google Inc. | Mobile device-based bandwidth throttling |
WO2012060995A2 (en) | 2010-11-01 | 2012-05-10 | Michael Luna | Distributed caching in a wireless network of content delivered for a mobile application over a long-held request |
US10687250B2 (en) | 2010-11-05 | 2020-06-16 | Mark Cummings | Mobile base station network |
US10285094B2 (en) | 2010-11-05 | 2019-05-07 | Mark Cummings | Mobile base station network |
US9311108B2 (en) | 2010-11-05 | 2016-04-12 | Mark Cummings | Orchestrating wireless network operations |
US10694402B2 (en) | 2010-11-05 | 2020-06-23 | Mark Cummings | Security orchestration and network immune system deployment framework |
US10531516B2 (en) | 2010-11-05 | 2020-01-07 | Mark Cummings | Self organizing system to implement emerging topologies |
US8504889B2 (en) * | 2010-11-12 | 2013-08-06 | Qualcomm Incorporated | Sleep clock error recovery scheme |
US8457010B2 (en) | 2010-11-16 | 2013-06-04 | Edgecast Networks, Inc. | Request modification for transparent capacity management in a carrier network |
CA2798523C (en) | 2010-11-22 | 2015-02-24 | Seven Networks, Inc. | Aligning data transfer to optimize connections established for transmission over a wireless network |
WO2012071384A2 (en) | 2010-11-22 | 2012-05-31 | Michael Luna | Optimization of resource polling intervals to satisfy mobile device requests |
EP2643960A4 (en) * | 2010-11-25 | 2015-01-14 | Ericsson Telefon Ab L M | Method and arrangement for enabling service delivery in a telecommunications network |
KR101260648B1 (en) * | 2010-11-29 | 2013-05-03 | 주식회사 케이티 | Online activation method and system of user subscription for wireless internet service |
EP3267709B1 (en) * | 2010-12-01 | 2023-02-01 | Headwater Research LLC | Security, fraud detection, and fraud mitigation in device-assisted services systems |
EP2647190B1 (en) * | 2010-12-03 | 2019-10-16 | Unify Inc. | Method and apparatus for controlling sessions from one or more devices |
US9542203B2 (en) | 2010-12-06 | 2017-01-10 | Microsoft Technology Licensing, Llc | Universal dock for context sensitive computing device |
US8595374B2 (en) * | 2010-12-08 | 2013-11-26 | At&T Intellectual Property I, L.P. | Method and apparatus for capacity dimensioning in a communication network |
US9065936B2 (en) | 2010-12-09 | 2015-06-23 | Allot Communications Ltd. | Cellular traffic monitoring and charging using application detection rules |
US8923770B2 (en) | 2010-12-09 | 2014-12-30 | Microsoft Corporation | Cognitive use of multiple regulatory domains |
EP2649843B1 (en) * | 2010-12-09 | 2015-11-04 | Allot Communications Ltd. | Device, system and method of traffic detection |
USRE48656E1 (en) | 2010-12-09 | 2021-07-20 | Allot Ltd. | System, device, and method of traffic detection |
US8589991B2 (en) | 2010-12-14 | 2013-11-19 | Microsoft Corporation | Direct connection with side channel control |
US8792429B2 (en) | 2010-12-14 | 2014-07-29 | Microsoft Corporation | Direct connection with side channel control |
US9246764B2 (en) * | 2010-12-14 | 2016-01-26 | Verizon Patent And Licensing Inc. | Network service admission control using dynamic network topology and capacity updates |
US8699344B2 (en) * | 2010-12-15 | 2014-04-15 | At&T Intellectual Property I, L.P. | Method and apparatus for managing a degree of parallelism of streams |
US8391830B1 (en) * | 2010-12-15 | 2013-03-05 | Sprint Communications Company L.P. | Mobile phone emergency services |
US11750414B2 (en) | 2010-12-16 | 2023-09-05 | Icontrol Networks, Inc. | Bidirectional security sensor communication for a premises security system |
US8948382B2 (en) | 2010-12-16 | 2015-02-03 | Microsoft Corporation | Secure protocol for peer-to-peer network |
US9294545B2 (en) | 2010-12-16 | 2016-03-22 | Microsoft Technology Licensing, Llc | Fast join of peer to peer group with power saving mode |
US8971841B2 (en) | 2010-12-17 | 2015-03-03 | Microsoft Corporation | Operating system supporting cost aware applications |
US9147337B2 (en) | 2010-12-17 | 2015-09-29 | Icontrol Networks, Inc. | Method and system for logging security event data |
US20120158947A1 (en) * | 2010-12-17 | 2012-06-21 | Microsoft Corporation | Operating system supporting cost aware applications |
US8560839B2 (en) * | 2010-12-20 | 2013-10-15 | Microsoft Corporation | Tamper proof location services |
US9282085B2 (en) | 2010-12-20 | 2016-03-08 | Duo Security, Inc. | System and method for digital user authentication |
US8660026B2 (en) * | 2010-12-20 | 2014-02-25 | At&T Intellectual Property I, L.P. | Method and apparatus for providing mapping management |
WO2012087353A1 (en) * | 2010-12-22 | 2012-06-28 | Telecommunication Systems, Inc. | Area event handling when current network does not cover target area |
US8615737B2 (en) * | 2010-12-23 | 2013-12-24 | Red Hat, Inc. | Systems and methods for building software packages in secure development environments |
KR101337724B1 (en) | 2010-12-27 | 2013-12-06 | 주식회사 팬택 | Mobile terminal displaying the amount of using data for each application and control method there of |
US8909751B2 (en) * | 2010-12-28 | 2014-12-09 | Microsoft Corporation | Flexible policy based network decision making |
US8634348B2 (en) | 2010-12-29 | 2014-01-21 | Motorola Mobility Llc | Method and system for facilitating wireless communication via alternate wireless pathway |
US8630231B2 (en) | 2010-12-29 | 2014-01-14 | Motorola Mobility Llc | Method and system for facilitating wireless communication via alternate wireless pathway |
US8554645B1 (en) * | 2011-01-04 | 2013-10-08 | Intuit Inc. | Method and system for identifying business expenditures with vendors and automatically generating and submitting required forms |
WO2012094675A2 (en) | 2011-01-07 | 2012-07-12 | Seven Networks, Inc. | System and method for reduction of mobile network traffic used for domain name system (dns) queries |
US8707276B2 (en) * | 2011-01-07 | 2014-04-22 | Mastercard International Incorporated | Method and system for managing programmed applications in an open API environment |
US8671385B2 (en) | 2011-01-07 | 2014-03-11 | Mastercard International Incorporated | Methods and systems for throttling calls to a service application through an open API |
US9083534B2 (en) | 2011-01-07 | 2015-07-14 | Mastercard International Incorporated | Method and system for propagating a client identity |
US9032204B2 (en) | 2011-01-07 | 2015-05-12 | Mastercard International Incorporated | Methods and systems for providing a signed digital certificate in real time |
US8677308B2 (en) | 2011-01-07 | 2014-03-18 | Mastercard International Incorporated | Method and system for generating an API request message |
US8819757B2 (en) * | 2011-01-11 | 2014-08-26 | Manolo Fabio Rivera | Advanced wireless IPTV set top box |
US20120179396A1 (en) * | 2011-01-12 | 2012-07-12 | General Electric Company | Systems, methods, and apparatus for powering an ami communication board |
JPWO2012095918A1 (en) * | 2011-01-14 | 2014-06-09 | Necカシオモバイルコミュニケーションズ株式会社 | Remote operation system, relay device, communication device, and remote operation method |
US9378379B1 (en) * | 2011-01-19 | 2016-06-28 | Bank Of America Corporation | Method and apparatus for the protection of information in a device upon separation from a network |
US9363182B2 (en) * | 2011-01-20 | 2016-06-07 | Nec Corporation | Communication system, control device, policy management device, communication method, and program |
US9924044B2 (en) * | 2011-01-20 | 2018-03-20 | Verizon Patent And Licensing Inc. | Recommendations based on real-time usage information |
US8514717B2 (en) | 2011-01-21 | 2013-08-20 | T-Mobile Usa, Inc. | Smart connection manager |
CN103460729B (en) * | 2011-01-28 | 2017-02-22 | 三星电子株式会社 | Device and method for controlling charging in a mobile communication system |
US9161080B2 (en) | 2011-01-28 | 2015-10-13 | Level 3 Communications, Llc | Content delivery network with deep caching infrastructure |
WO2012103515A1 (en) * | 2011-01-28 | 2012-08-02 | Level 3 Communications, Llc | Content delivery network with deep caching infrastructure |
EP2671166A4 (en) * | 2011-02-03 | 2016-07-13 | Telcordia Tech Inc | System and method for group communications in 3gpp machine-to-machine networks |
US8649268B2 (en) | 2011-02-04 | 2014-02-11 | Twilio, Inc. | Method for processing telephony sessions of a network |
US9009697B2 (en) | 2011-02-08 | 2015-04-14 | International Business Machines Corporation | Hybrid cloud integrator |
US9063789B2 (en) | 2011-02-08 | 2015-06-23 | International Business Machines Corporation | Hybrid cloud integrator plug-in components |
US8559933B1 (en) | 2011-02-08 | 2013-10-15 | Sprint Communications Company L.P. | System and method for ID platform |
US20120209717A1 (en) * | 2011-02-16 | 2012-08-16 | Pascal Henry | Targeted delivery of payload to mobile users |
US9123062B1 (en) | 2011-02-18 | 2015-09-01 | Sprint Communications Company L.P. | Ad sponsored interface pack |
WO2012141762A1 (en) | 2011-02-25 | 2012-10-18 | Telecommunication Systems, Inc. | Mobile internet protocol (ip) location |
US8988998B2 (en) | 2011-02-25 | 2015-03-24 | International Business Machines Corporation | Data processing environment integration control |
US9128773B2 (en) | 2011-02-25 | 2015-09-08 | International Business Machines Corporation | Data processing environment event correlation |
US20120221693A1 (en) * | 2011-02-25 | 2012-08-30 | Alcatlel-Lucent Canada Inc. | Temporary restrictions and rollback |
US9104672B2 (en) | 2011-02-25 | 2015-08-11 | International Business Machines Corporation | Virtual security zones for data processing environments |
US8838791B2 (en) * | 2011-02-25 | 2014-09-16 | Alcatel Lucent | Transient subscription records |
US9053580B2 (en) | 2011-02-25 | 2015-06-09 | International Business Machines Corporation | Data processing environment integration control interface |
US9363842B2 (en) * | 2011-03-01 | 2016-06-07 | Lg Electronics Inc. | Method of transmitting and receiving data in a wireless communication system and apparatus therefor |
US20120227035A1 (en) * | 2011-03-03 | 2012-09-06 | Microsoft Corporation | Cross platform service notification |
US9021005B2 (en) | 2011-03-04 | 2015-04-28 | Mformation Software Technologies Llc | System and method to provide remote device management for mobile virtualized platforms |
US8355805B2 (en) | 2011-03-08 | 2013-01-15 | D. Light Design, Inc. | Systems and methods for activation and deactivation of appliances |
US20120231789A1 (en) * | 2011-03-09 | 2012-09-13 | Yakov Kharon | Method and System for SIM Card Reregistration Control in a Mobile Communications Network |
US8639595B1 (en) | 2011-03-10 | 2014-01-28 | Amazon Technologies, Inc. | Statistically cost-following accounting model for dedicated resources |
US9043446B1 (en) | 2011-03-10 | 2015-05-26 | Sprint Communications Company L.P. | Mirroring device interface components for content sharing |
US8661410B2 (en) | 2011-03-11 | 2014-02-25 | Oracle International Corporation | Managed enterprise software components as dynamic services |
US8856734B2 (en) | 2011-03-11 | 2014-10-07 | Oracle International Corporation | Type-safe dependency injection of services into enterprise components |
EP2687035A1 (en) | 2011-03-18 | 2014-01-22 | Smith Micro Software, Inc. | Managing tethered data traffic over a hotspot network |
WO2012128719A1 (en) * | 2011-03-21 | 2012-09-27 | Nanyang Technological University | Sensor device |
US8706881B2 (en) * | 2011-03-22 | 2014-04-22 | Oracle International Corporation | Automatic registration of enterprise resources in a dynamic module system services registry |
US9154555B2 (en) * | 2011-03-30 | 2015-10-06 | Paypal, Inc. | Device specific remote disabling of applications |
US9030935B2 (en) * | 2011-03-30 | 2015-05-12 | International Business Machines Corporation | Device and method for adjusting rate limits for transmission rates of data flows having a certain priority in a transmitter |
US9203722B2 (en) * | 2011-03-31 | 2015-12-01 | Verizon Patent And Licensing Inc. | Identifying and forecasting network conditions using real-time radio access network (RAN) modeling |
US20120250586A1 (en) * | 2011-04-01 | 2012-10-04 | Kalle Ilmari Ahmavaara | Methods and apparatus for managing data connectivity |
US9154826B2 (en) | 2011-04-06 | 2015-10-06 | Headwater Partners Ii Llc | Distributing content and service launch objects to mobile devices |
WO2012141628A1 (en) * | 2011-04-13 | 2012-10-18 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for sharing radio network infrastructure using carrier aggregation |
GB2517815A (en) | 2011-04-19 | 2015-03-04 | Seven Networks Inc | Shared resource and virtual resource management in a networked environment |
US9444692B2 (en) | 2011-04-26 | 2016-09-13 | Openet Telecom Ltd. | Systems, devices and methods of crowd-sourcing across multiple domains |
US9641403B2 (en) | 2011-04-26 | 2017-05-02 | Openet Telecom Ltd. | Systems, devices and methods of decomposing service requests into domain-specific service requests |
US9450766B2 (en) | 2011-04-26 | 2016-09-20 | Openet Telecom Ltd. | Systems, devices and methods of distributing telecommunications functionality across multiple heterogeneous domains |
US8929859B2 (en) | 2011-04-26 | 2015-01-06 | Openet Telecom Ltd. | Systems for enabling subscriber monitoring of telecommunications network usage and service plans |
US9565063B2 (en) | 2011-04-26 | 2017-02-07 | Openet Telecom Ltd. | Systems, devices and methods of synchronizing information across multiple heterogeneous networks |
US9130760B2 (en) | 2011-04-26 | 2015-09-08 | Openet Telecom Ltd | Systems, devices and methods of establishing a closed feedback control loop across multiple domains |
US9565074B2 (en) | 2011-04-26 | 2017-02-07 | Openet Telecom Ltd. | Systems, devices, and methods of orchestrating resources and services across multiple heterogeneous domains |
WO2012149221A2 (en) | 2011-04-27 | 2012-11-01 | Seven Networks, Inc. | System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief |
WO2012149434A2 (en) | 2011-04-27 | 2012-11-01 | Seven Networks, Inc. | Detecting and preserving state for satisfying application requests in a distributed proxy and cache system |
JP6066997B2 (en) | 2011-05-01 | 2017-01-25 | ラッカス ワイヤレス, インコーポレイテッド | Remote cable access point reset |
US20130006894A1 (en) * | 2011-05-02 | 2013-01-03 | Jerry Richard Jones | System for calculating the cost-per-unit of ink |
JP5759064B2 (en) | 2011-05-06 | 2015-08-05 | テケレック・インコーポレイテッドTekelec, Inc. | Method, system, and computer-readable medium for guiding subscribers between access networks |
US8620265B1 (en) * | 2011-05-06 | 2013-12-31 | Sprint Communications Company L.P. | Handset awareness and tracking of subscription plan |
US8655986B2 (en) * | 2011-05-06 | 2014-02-18 | Allot Communications Ltd. | Data path processing |
EP3576352A1 (en) * | 2011-05-09 | 2019-12-04 | Samsung Electronics Co., Ltd. | Method and system for managing telephony services in a universal plug and play home network environment |
US8971946B2 (en) * | 2011-05-11 | 2015-03-03 | Tikl, Inc. | Privacy control in push-to-talk |
GB2491096A (en) * | 2011-05-15 | 2012-11-28 | Whatever Software Contracts Ltd | Network access control based on a combined profile |
US8913587B2 (en) * | 2011-05-19 | 2014-12-16 | Qualcomm Incorporated | Infrastructure-unassisted inter-device wireless wide area network handoff |
WO2012162397A1 (en) | 2011-05-23 | 2012-11-29 | Twilio, Inc. | System and method for connecting a communication to a client |
US9648006B2 (en) | 2011-05-23 | 2017-05-09 | Twilio, Inc. | System and method for communicating with a client application |
US20140044123A1 (en) | 2011-05-23 | 2014-02-13 | Twilio, Inc. | System and method for real time communicating with a client application |
US8918641B2 (en) * | 2011-05-26 | 2014-12-23 | Intel Corporation | Dynamic platform reconfiguration by multi-tenant service providers |
US20130007849A1 (en) * | 2011-05-26 | 2013-01-03 | FonWallet Transaction Soulutions, Inc. | Secure consumer authorization and automated consumer services using an intermediary service |
US8972592B1 (en) | 2011-05-27 | 2015-03-03 | Sprint Communications Company L.P. | Extending an interface pack to a computer system |
WO2012164334A1 (en) | 2011-05-31 | 2012-12-06 | Indian Institute Of Technology Madras | Electrode and/or capacitor formation |
US8612967B1 (en) | 2011-05-31 | 2013-12-17 | Sprint Communications Company L.P. | Loading branded media outside system partition |
JP5691853B2 (en) * | 2011-06-02 | 2015-04-01 | 富士通株式会社 | Access monitoring program, information processing apparatus, and access monitoring method |
US9201895B2 (en) | 2011-06-03 | 2015-12-01 | Apple Inc. | Management of downloads from a network-based digital data repository based on network performance |
KR101548448B1 (en) * | 2011-06-03 | 2015-08-28 | 애플 인크. | Management of network-based digital data repository |
US8739244B1 (en) * | 2011-06-07 | 2014-05-27 | Riverbed Technology, Inc. | Configuring and authenticating WAN optimization devices for accessing content delivery networks |
US20120315893A1 (en) * | 2011-06-09 | 2012-12-13 | Alcatel-Lucent Canada Inc. | Intelligent network management of subscriber-related events |
US20120317270A1 (en) * | 2011-06-10 | 2012-12-13 | Alcatel-Lucent Usa Inc. | Intelligent presence cost management based upon congestion status and subscriber profile |
US8806003B2 (en) | 2011-06-14 | 2014-08-12 | International Business Machines Corporation | Forecasting capacity available for processing workloads in a networked computing environment |
US8634771B2 (en) * | 2011-06-15 | 2014-01-21 | Microsoft Corporation | Simple peer-to-peer network formation |
US9191275B1 (en) | 2011-06-22 | 2015-11-17 | Amazon Technologies, Inc. | Global computer provisioning |
US8730823B2 (en) * | 2011-06-24 | 2014-05-20 | Jasper Wireless, Inc. | Core services platform for wireless voice, data and messaging network services |
US10425336B2 (en) | 2011-06-24 | 2019-09-24 | Centurylink Intellectual Property Llc | System and method of adaptive congestion management |
US9148846B2 (en) * | 2011-06-30 | 2015-09-29 | Motorola Solutions, Inc. | Methods for intelligent network selection |
US8955078B2 (en) | 2011-06-30 | 2015-02-10 | Cable Television Laboratories, Inc. | Zero sign-on authentication |
US20130013459A1 (en) * | 2011-07-07 | 2013-01-10 | hi5 Networks, Inc. | Dynamic pricing of online content |
WO2012106889A1 (en) | 2011-07-14 | 2012-08-16 | 华为技术有限公司 | Receiver and receiving method thereof |
US9351236B2 (en) * | 2011-07-19 | 2016-05-24 | At&T Intellectual Property I, L.P. | UICC carrier switching via over-the-air technology |
US8964567B2 (en) * | 2011-07-21 | 2015-02-24 | Microsoft Technology Licensing, Llc | Wireless synchronization testing |
WO2013015995A1 (en) | 2011-07-27 | 2013-01-31 | Seven Networks, Inc. | Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network |
EP2737733A4 (en) * | 2011-07-27 | 2015-09-09 | Seven Networks Inc | Parental control of mobile content on a mobile device |
US9106769B2 (en) | 2011-08-10 | 2015-08-11 | Tekelec, Inc. | Methods, systems, and computer readable media for congestion management in a diameter signaling network |
US8566918B2 (en) | 2011-08-15 | 2013-10-22 | Bank Of America Corporation | Method and apparatus for token-based container chaining |
WO2013025581A1 (en) * | 2011-08-15 | 2013-02-21 | Bank Of America Corporation | Apparatus and method for token-based access control |
US8474056B2 (en) | 2011-08-15 | 2013-06-25 | Bank Of America Corporation | Method and apparatus for token-based virtual machine recycling |
US8752123B2 (en) * | 2011-08-15 | 2014-06-10 | Bank Of America Corporation | Apparatus and method for performing data tokenization |
US9069943B2 (en) | 2011-08-15 | 2015-06-30 | Bank Of America Corporation | Method and apparatus for token-based tamper detection |
US8972537B2 (en) * | 2011-08-16 | 2015-03-03 | Comcast Cable Communications, Llc | Prioritizing local and network traffic |
US8737222B2 (en) * | 2011-08-18 | 2014-05-27 | Alcatel Lucent | Method and apparatus for providing increased small cell resource utilization |
CA2752765A1 (en) * | 2011-09-02 | 2013-03-02 | Librestream Technologies Inc. | Transmitting a media stream over http |
US9467463B2 (en) | 2011-09-02 | 2016-10-11 | Duo Security, Inc. | System and method for assessing vulnerability of a mobile device |
WO2013036658A1 (en) * | 2011-09-06 | 2013-03-14 | Enfora, Inc. | Modeling billing impacts in data sensitive environments |
US8825001B2 (en) * | 2011-09-06 | 2014-09-02 | Tangoe Canada, Inc. | Confirmation based mobile messaging platform |
US8504906B1 (en) * | 2011-09-08 | 2013-08-06 | Amazon Technologies, Inc. | Sending selected text and corresponding media content |
JP4911737B1 (en) * | 2011-09-09 | 2012-04-04 | 株式会社アクティス | Communication speed control system |
US9300814B2 (en) * | 2011-09-12 | 2016-03-29 | Microsoft Technology Licensing Llc | Network adaptive content download |
KR20130030580A (en) * | 2011-09-19 | 2013-03-27 | 주식회사 팬택 | Data communication system and method between nfc terminals |
CN103891201B (en) | 2011-09-19 | 2018-03-30 | 塔塔咨询服务有限公司 | For the exploitation of the application and service based on sensing data and the calculating platform of deployment |
US8874703B1 (en) * | 2011-09-20 | 2014-10-28 | Amazon Technologies, Inc. | System and method of selectively implementing network configurations |
US9064117B1 (en) | 2011-09-20 | 2015-06-23 | Amazon Technologies, Inc. | Mobile provisioning device |
US10182147B2 (en) | 2011-09-21 | 2019-01-15 | Twilio Inc. | System and method for determining and communicating presence information |
EP2759123B1 (en) | 2011-09-21 | 2018-08-15 | Twilio, Inc. | System and method for authorizing and connecting application developers and users |
US9497563B2 (en) * | 2011-09-23 | 2016-11-15 | Google Inc. | Mobile device activation |
KR101258834B1 (en) * | 2011-09-23 | 2013-05-06 | 삼성에스디에스 주식회사 | Apparatus and method for management of mobile device by security policy, and management server for management of mobile device |
US8706100B1 (en) | 2011-09-23 | 2014-04-22 | Klone Mobile, LLC | End user controlled temporary phone service device swapping system and method |
US9722866B1 (en) | 2011-09-23 | 2017-08-01 | Amazon Technologies, Inc. | Resource allocation to reduce correlated failures |
US8244283B1 (en) | 2011-09-26 | 2012-08-14 | Klone Mobile, LLC | End user controlled temporary mobile phone service device swapping system and method |
US8983449B1 (en) | 2011-09-26 | 2015-03-17 | Klone Mobile, LLC | End user controlled temporary mobile phone service device swapping system and method |
US8583112B2 (en) | 2011-09-26 | 2013-11-12 | Klone Mobile, LLC | End user controlled temporary mobile phone service device swapping system and method |
US9495012B2 (en) * | 2011-09-27 | 2016-11-15 | Z124 | Secondary single screen mode activation through user interface activation |
US9774721B2 (en) | 2011-09-27 | 2017-09-26 | Z124 | LTE upgrade module |
US8693953B2 (en) * | 2011-09-28 | 2014-04-08 | Verizon Patent And Licensing Inc. | Optimizing use of network resources by small cells and/or user devices of a venue |
US8776043B1 (en) | 2011-09-29 | 2014-07-08 | Amazon Technologies, Inc. | Service image notifications |
WO2013044367A1 (en) * | 2011-09-29 | 2013-04-04 | Avvasi Inc. | Systems and methods for media service delivery |
WO2013048551A1 (en) | 2011-09-30 | 2013-04-04 | Telecommunication Systems, Inc. | Unique global identifier for minimizing prank 911 calls |
CN103037512B (en) | 2011-09-30 | 2016-06-01 | 上海贝尔股份有限公司 | A kind of method that message based on pattern is transmitted |
JP6047869B2 (en) | 2011-09-30 | 2016-12-21 | 株式会社リコー | Transmission system, participation fee management method, and program |
US20130086385A1 (en) * | 2011-09-30 | 2013-04-04 | Yuri Poeluev | System and Method for Providing Hardware-Based Security |
EP2764441A1 (en) * | 2011-10-03 | 2014-08-13 | Dantech Systems LLC | Network application based intranet |
US20130085864A1 (en) * | 2011-10-03 | 2013-04-04 | Hassan Ahmed | Mobile content delivery |
US9049537B2 (en) | 2011-10-06 | 2015-06-02 | Open Garden Inc. | Discovering and connecting wireless devices without discoverability |
US8763077B2 (en) | 2011-10-07 | 2014-06-24 | Duo Security, Inc. | System and method for enforcing a policy for an authenticator device |
US9280377B2 (en) | 2013-03-29 | 2016-03-08 | Citrix Systems, Inc. | Application with multiple operation modes |
US9215225B2 (en) | 2013-03-29 | 2015-12-15 | Citrix Systems, Inc. | Mobile device locking with context |
US20140032733A1 (en) | 2011-10-11 | 2014-01-30 | Citrix Systems, Inc. | Policy-Based Application Management |
US9183380B2 (en) | 2011-10-11 | 2015-11-10 | Citrix Systems, Inc. | Secure execution of enterprise applications on mobile devices |
US20140053234A1 (en) | 2011-10-11 | 2014-02-20 | Citrix Systems, Inc. | Policy-Based Application Management |
US20140040979A1 (en) | 2011-10-11 | 2014-02-06 | Citrix Systems, Inc. | Policy-Based Application Management |
US9619810B1 (en) | 2011-10-11 | 2017-04-11 | Sprint Communications Company L.P. | Zone architecture for dynamic targeted content creation |
CN102364892B (en) * | 2011-10-12 | 2013-04-24 | 华为技术有限公司 | Link aggregation control protocol (LACP) link switching and data transmission method and apparatus thereof |
US9154550B1 (en) * | 2011-10-17 | 2015-10-06 | Google Inc. | Methods and systems for determining, controlling, and reporting network data usage at the application and feature level |
US8744428B2 (en) * | 2011-10-18 | 2014-06-03 | Alcatel Lucent | Supported feature override |
US9385982B2 (en) * | 2011-10-19 | 2016-07-05 | International Business Machines Corporation | Identification to a recipient of an electronic communication of another user who has accessed the electronic communication |
US8910217B2 (en) * | 2011-10-25 | 2014-12-09 | Verizon Patent And Licensing Inc. | Broadcast video provisioning system |
US20130107783A1 (en) * | 2011-10-26 | 2013-05-02 | At&T Intellectual Property I, L.P | Intelligent Hot Spot and Tethering |
US8774035B1 (en) * | 2011-10-26 | 2014-07-08 | Sprint Spectrum L.P. | Managing a network connection of a wireless device |
US9544759B2 (en) * | 2011-11-01 | 2017-01-10 | Google Inc. | Systems, methods, and computer program products for managing states |
KR101826275B1 (en) | 2011-11-01 | 2018-02-06 | 구글 엘엘씨 | Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements |
US8787873B1 (en) * | 2011-11-04 | 2014-07-22 | Plusn Llc | System and method for communicating using bandwidth on demand |
US20130124631A1 (en) * | 2011-11-04 | 2013-05-16 | Fidelus Technologies, Llc. | Apparatus, system, and method for digital communications driven by behavior profiles of participants |
US9191985B2 (en) * | 2011-11-09 | 2015-11-17 | Verizon Patent And Licensing Inc. | Connecting to an evolved packet data gateway |
US10754913B2 (en) * | 2011-11-15 | 2020-08-25 | Tapad, Inc. | System and method for analyzing user device information |
AU2012345719A1 (en) * | 2011-11-30 | 2014-07-24 | Ulterius Technologies, Llc | Communications modules for a gateway device, system and method |
US8934414B2 (en) | 2011-12-06 | 2015-01-13 | Seven Networks, Inc. | Cellular or WiFi mobile traffic optimization based on public or private network destination |
EP2789137A4 (en) | 2011-12-06 | 2015-12-02 | Seven Networks Inc | A system of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation |
US9277443B2 (en) | 2011-12-07 | 2016-03-01 | Seven Networks, Llc | Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol |
WO2013086455A1 (en) | 2011-12-07 | 2013-06-13 | Seven Networks, Inc. | Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation |
US20130152196A1 (en) * | 2011-12-08 | 2013-06-13 | Microsoft Corporation | Throttling of rogue entities to push notification servers |
TWI467512B (en) * | 2011-12-09 | 2015-01-01 | Chunghwa Telecom Co Ltd | Design of Components for Communication Services of ICT Services |
US9300531B2 (en) | 2011-12-12 | 2016-03-29 | Openet Telecom Ltd. | Systems, devices, and methods of orchestration and application of business rules for real-time control of subscribers in a telecommunications operator's network |
US20130151386A1 (en) * | 2011-12-13 | 2013-06-13 | Cisco Technology, Inc. | Service Delivery in Networks |
EP2792188B1 (en) | 2011-12-14 | 2019-03-20 | Seven Networks, LLC | Mobile network reporting and usage analytics system and method using aggregation of data in a distributed traffic optimization system |
WO2013090834A1 (en) | 2011-12-14 | 2013-06-20 | Seven Networks, Inc. | Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic |
US8861354B2 (en) | 2011-12-14 | 2014-10-14 | Seven Networks, Inc. | Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization |
US8935804B1 (en) | 2011-12-15 | 2015-01-13 | United Services Automobile Association (Usaa) | Rules-based data access systems and methods |
US8699962B2 (en) * | 2011-12-15 | 2014-04-15 | Proximetry, Inc. | Systems and methods for preparing a telecommunication network for providing services |
KR101327935B1 (en) * | 2011-12-20 | 2013-11-13 | 전자부품연구원 | Apparatus for verifying World DMB digital radio receiver profiles |
US8666383B1 (en) | 2011-12-23 | 2014-03-04 | Sprint Communications Company L.P. | Automated branding of generic applications |
US10318950B2 (en) * | 2011-12-29 | 2019-06-11 | Blackberry Limited | Mobile communications device providing near field communication (NFC) security features and related methods |
WO2013103988A1 (en) | 2012-01-05 | 2013-07-11 | Seven Networks, Inc. | Detection and management of user interactions with foreground applications on a mobile device in distributed caching |
US20140059071A1 (en) * | 2012-01-11 | 2014-02-27 | Saguna Networks Ltd. | Methods, circuits, devices, systems and associated computer executable code for providing domain name resolution |
US9313099B2 (en) | 2012-01-13 | 2016-04-12 | Logic PD, Inc. | Systems, devices and methods for provisioning, pairing and activating a newly manufactured device for automatic joining of customer's network |
US8857705B2 (en) | 2012-01-13 | 2014-10-14 | Logic PD, Inc. | Methods for embedding device-specific data to enable remote identification and provisioning of specific devices |
US8857704B2 (en) | 2012-01-13 | 2014-10-14 | Logic PD, Inc. | Methods for embedding device-specific data to enable remote access to real time device data |
US9336061B2 (en) | 2012-01-14 | 2016-05-10 | International Business Machines Corporation | Integrated metering of service usage for hybrid clouds |
US8897782B2 (en) * | 2012-01-16 | 2014-11-25 | Microsoft Corporation | System and method for offloading traffic from cellular networks using plugins |
US9220065B2 (en) * | 2012-01-16 | 2015-12-22 | Smith Micro Software, Inc. | Enabling a mobile broadband hotspot by an auxiliary radio |
EP2807835B1 (en) | 2012-01-23 | 2018-06-27 | Headwater Research LLC | Service plan design, user interfaces, application programming interfaces, and device management |
US8914842B2 (en) * | 2012-01-23 | 2014-12-16 | Microsoft Corporation | Accessing enterprise resource planning data from a handheld mobile device |
US9444947B2 (en) * | 2012-01-25 | 2016-09-13 | Hewlett Packard Enterprise Development Lp | Method and system for differential charging |
US9264556B2 (en) | 2012-01-27 | 2016-02-16 | Microsoft Technology Licensing, Llc | On-device attribution of network data usage |
US9173081B2 (en) | 2012-01-27 | 2015-10-27 | Openet Telecom Ltd. | System and method for enabling interactions between a policy decision point and a charging system |
EP2810233A4 (en) * | 2012-01-30 | 2015-09-02 | Nokia Technologies Oy | A method, an apparatus and a computer program for promoting the apparatus |
EP2624083A1 (en) * | 2012-02-01 | 2013-08-07 | ABB Research Ltd. | Dynamic configuration of an industrial control system |
WO2013116856A1 (en) | 2012-02-02 | 2013-08-08 | Seven Networks, Inc. | Dynamic categorization of applications for network access in a mobile network |
US8918843B1 (en) * | 2012-02-03 | 2014-12-23 | Sprint Spectrum L.P. | Detecting unauthorized tethering |
WO2013116852A1 (en) | 2012-02-03 | 2013-08-08 | Seven Networks, Inc. | User as an end point for profiling and optimizing the delivery of content and data in a wireless network |
US8718699B2 (en) * | 2012-02-06 | 2014-05-06 | Harris Corporation | Wireless communication system having assigned access classes and related methods |
US8756668B2 (en) | 2012-02-09 | 2014-06-17 | Ruckus Wireless, Inc. | Dynamic PSK for hotspots |
US9495227B2 (en) | 2012-02-10 | 2016-11-15 | Twilio, Inc. | System and method for managing concurrent events |
US9252916B2 (en) | 2012-02-13 | 2016-02-02 | Affirmed Networks, Inc. | Mobile video delivery |
US9634403B2 (en) | 2012-02-14 | 2017-04-25 | Ruckus Wireless, Inc. | Radio frequency emission pattern shaping |
US10186750B2 (en) | 2012-02-14 | 2019-01-22 | Arris Enterprises Llc | Radio frequency antenna array with spacing element |
US9779008B2 (en) * | 2012-02-21 | 2017-10-03 | Disney Enterprises, Inc. | File monitoring |
EP2817934A1 (en) | 2012-02-22 | 2014-12-31 | Nokia Solutions and Networks Oy | Controlling access |
US20130227711A1 (en) * | 2012-02-29 | 2013-08-29 | Smith Micro Software, Inc. | Controlled Access by Applications to Mobile Device Resources |
US9633201B1 (en) | 2012-03-01 | 2017-04-25 | The 41St Parameter, Inc. | Methods and systems for fraud containment |
US8850301B1 (en) * | 2012-03-05 | 2014-09-30 | Google Inc. | Linking to relevant content from an ereader |
US8635128B2 (en) | 2012-03-06 | 2014-01-21 | Edgecast Networks, Inc. | Systems and methods for billing content providers for designated content delivered over a data network |
US10282724B2 (en) | 2012-03-06 | 2019-05-07 | Visa International Service Association | Security system incorporating mobile device |
US8862516B2 (en) * | 2012-03-06 | 2014-10-14 | Edgecast Networks, Inc. | Systems and methods for billing content providers for designated content delivered over a data network |
US9210591B2 (en) * | 2012-03-12 | 2015-12-08 | Starhome Gmbh | System and method for steering of roaming |
US9648133B2 (en) * | 2012-03-12 | 2017-05-09 | Telefonaktiebolaget L M Ericsson | Optimizing traffic load in a communications network |
TWI590631B (en) * | 2012-03-15 | 2017-07-01 | 微軟技術授權有限責任公司 | Multi-modal communication priority over wireless networks |
KR101980173B1 (en) * | 2012-03-16 | 2019-05-20 | 삼성전자주식회사 | A collaborative personal assistant system for delegating providing of services supported by third party task providers and method therefor |
US20130254121A1 (en) * | 2012-03-22 | 2013-09-26 | International Business Machines Corporation | Software Portfolio Management Based on Feature Usage |
US9521551B2 (en) | 2012-03-22 | 2016-12-13 | The 41St Parameter, Inc. | Methods and systems for persistent cross-application mobile device identification |
US9544260B2 (en) | 2012-03-26 | 2017-01-10 | Telecommunication Systems, Inc. | Rapid assignment dynamic ownership queue |
US9307372B2 (en) | 2012-03-26 | 2016-04-05 | Telecommunication Systems, Inc. | No responders online |
US9295020B2 (en) * | 2012-03-26 | 2016-03-22 | Harris Corporation | Systems and methods registration and maintenance of wireless clients via a proxy wireless network service |
CN103368930B (en) | 2012-03-27 | 2017-11-28 | 华为技术有限公司 | The method and user equipment of core net are accessed for controlling |
US9118618B2 (en) | 2012-03-29 | 2015-08-25 | A10 Networks, Inc. | Hardware-based packet editor |
US9479448B2 (en) * | 2012-04-02 | 2016-10-25 | Wipro Limited | Methods for improved provisioning of information technology resources and devices thereof |
US9092610B2 (en) * | 2012-04-04 | 2015-07-28 | Ruckus Wireless, Inc. | Key assignment for a brand |
US9338517B2 (en) * | 2012-04-07 | 2016-05-10 | Samsung Electronics Co., Ltd. | Method and system for reproducing contents, and computer-readable recording medium thereof |
US8812695B2 (en) | 2012-04-09 | 2014-08-19 | Seven Networks, Inc. | Method and system for management of a virtual network connection without heartbeat messages |
US10263899B2 (en) | 2012-04-10 | 2019-04-16 | Seven Networks, Llc | Enhanced customer service for mobile carriers using real-time and historical mobile application and traffic or optimization data associated with mobile devices in a mobile network |
US9198204B2 (en) | 2012-04-11 | 2015-11-24 | Google Inc. | Apparatus and method for seamless commissioning of wireless devices |
US9264395B1 (en) | 2012-04-11 | 2016-02-16 | Artemis Internet Inc. | Discovery engine |
US8799482B1 (en) | 2012-04-11 | 2014-08-05 | Artemis Internet Inc. | Domain policy specification and enforcement |
US9106661B1 (en) | 2012-04-11 | 2015-08-11 | Artemis Internet Inc. | Computing resource policy regime specification and verification |
US10075334B1 (en) | 2012-04-11 | 2018-09-11 | Google Llc | Systems and methods for commissioning a smart hub device |
US9083727B1 (en) | 2012-04-11 | 2015-07-14 | Artemis Internet Inc. | Securing client connections |
US8990392B1 (en) * | 2012-04-11 | 2015-03-24 | NCC Group Inc. | Assessing a computing resource for compliance with a computing resource policy regime specification |
US10397013B1 (en) | 2012-04-11 | 2019-08-27 | Google Llc | User interfaces, systems and methods for configuring smart devices for interoperability with a smart hub device |
US10142122B1 (en) | 2012-04-11 | 2018-11-27 | Google Llc | User interfaces, systems and methods for configuring smart devices for interoperability with a smart hub device |
US20130290547A1 (en) * | 2012-04-25 | 2013-10-31 | Alan C. Berkema | System for managing persistent connections |
EP2850850B1 (en) * | 2012-05-02 | 2020-04-01 | Nokia Solutions and Networks Oy | Methods and apparatus |
US20130294335A1 (en) * | 2012-05-02 | 2013-11-07 | Nokia Siemens Networks Oy | Methods and apparatus |
CN102647705B (en) * | 2012-05-08 | 2014-12-10 | 中兴通讯股份有限公司 | Method and system for mobile terminal parameter configuration |
CA2775782C (en) | 2012-05-08 | 2013-09-24 | Guest Tek Interactive Entertainment Ltd. | Automatic service activation for user device upon detecting its device identifier on network of hospitality establishment |
US20130304928A1 (en) | 2012-05-09 | 2013-11-14 | Twilio, Inc. | System and method for managing latency in a distributed telephony network |
US10455071B2 (en) | 2012-05-09 | 2019-10-22 | Sprint Communications Company L.P. | Self-identification of brand and branded firmware installation in a generic electronic device |
US9240941B2 (en) | 2012-05-09 | 2016-01-19 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US9602586B2 (en) | 2012-05-09 | 2017-03-21 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US20130304631A1 (en) * | 2012-05-10 | 2013-11-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Wi-fi hot-spot networking ecommerce |
CN103391579B (en) | 2012-05-11 | 2017-04-12 | 华为技术有限公司 | Service authority value processing method, user equipment and network device |
US20130305169A1 (en) * | 2012-05-11 | 2013-11-14 | Robert Evan Gold | Methods and Systems for Providing Feedback in Interactive, Interest Centric Communications Environment |
US9094873B2 (en) * | 2012-05-14 | 2015-07-28 | Wei Lu | Classified relation networking optimization platform in open wireless architecture (OWA) mobile cloud terminal device |
US9565615B2 (en) | 2012-05-16 | 2017-02-07 | Qualcomm Incorporated | Evolved hybrid internet protocol (IP) multimedia subsystem (IMS) architecture |
AU2013262973B2 (en) * | 2012-05-18 | 2017-12-07 | Aquto Corporation | Advertiser supported bandwidth platform |
US20130316703A1 (en) * | 2012-05-18 | 2013-11-28 | Aquto Corporation | Charging and billing for content, services, and access |
US10580090B2 (en) | 2012-05-25 | 2020-03-03 | Microsoft Technology Licensing, Llc | Batch-computed activity stream updates |
US9516176B2 (en) * | 2012-05-31 | 2016-12-06 | At&T Intellectual Property I, L.P. | Long term evolution network billing management |
US8893105B2 (en) * | 2012-06-08 | 2014-11-18 | Apple Inc. | Activation-based regulatory updates |
US9179392B2 (en) | 2012-06-13 | 2015-11-03 | All Purpose Networks LLC | Efficient delivery of real-time asynchronous services over a wireless network |
US9094803B2 (en) | 2012-06-13 | 2015-07-28 | All Purpose Networks LLC | Wireless network based sensor data collection, processing, storage, and distribution |
US8565689B1 (en) | 2012-06-13 | 2013-10-22 | All Purpose Networks LLC | Optimized broadband wireless network performance through base station application server |
US9125064B2 (en) | 2012-06-13 | 2015-09-01 | All Purpose Networks LLC | Efficient reduction of inter-cell interference using RF agile beam forming techniques |
US9131385B2 (en) | 2012-06-13 | 2015-09-08 | All Purpose Networks LLC | Wireless network based sensor data collection, processing, storage, and distribution |
US9179352B2 (en) | 2012-06-13 | 2015-11-03 | All Purpose Networks LLC | Efficient delivery of real-time synchronous services over a wireless network |
US9125123B2 (en) | 2012-06-13 | 2015-09-01 | All Purpose Networks LLC | Efficient delivery of real-time asynchronous services over a wireless network |
US9144082B2 (en) | 2012-06-13 | 2015-09-22 | All Purpose Networks LLC | Locating and tracking user equipment in the RF beam areas of an LTE wireless system employing agile beam forming techniques |
US9882950B2 (en) | 2012-06-13 | 2018-01-30 | All Purpose Networks LLC | Methods and systems of an all purpose broadband network |
US9137675B2 (en) | 2012-06-13 | 2015-09-15 | All Purpose Networks LLC | Operational constraints in LTE TDD systems using RF agile beam forming techniques |
US9219541B2 (en) | 2012-06-13 | 2015-12-22 | All Purpose Networks LLC | Baseband data transmission and reception in an LTE wireless base station employing periodically scanning RF beam forming techniques |
US9503927B2 (en) | 2012-06-13 | 2016-11-22 | All Purpose Networks LLC | Multiple-use wireless network |
US9084155B2 (en) | 2012-06-13 | 2015-07-14 | All Purpose Networks LLC | Optimized broadband wireless network performance through base station application server |
US9107094B2 (en) | 2012-06-13 | 2015-08-11 | All Purpose Networks LLC | Methods and systems of an all purpose broadband network |
US9179354B2 (en) | 2012-06-13 | 2015-11-03 | All Purpose Networks LLC | Efficient delivery of real-time synchronous services over a wireless network |
US9144075B2 (en) | 2012-06-13 | 2015-09-22 | All Purpose Networks LLC | Baseband data transmission and reception in an LTE wireless base station employing periodically scanning RF beam forming techniques |
US9031511B2 (en) | 2012-06-13 | 2015-05-12 | All Purpose Networks LLC | Operational constraints in LTE FDD systems using RF agile beam forming techniques |
US9084143B2 (en) | 2012-06-13 | 2015-07-14 | All Purpose Networks LLC | Network migration queuing service in a wireless network |
EP2677719A1 (en) * | 2012-06-19 | 2013-12-25 | Alcatel Lucent | A method for interfacing a communication terminal with networked objects |
US9247062B2 (en) | 2012-06-19 | 2016-01-26 | Twilio, Inc. | System and method for queuing a communication session |
US9185009B2 (en) * | 2012-06-20 | 2015-11-10 | Google Inc. | Status aware media play |
US20130346624A1 (en) * | 2012-06-20 | 2013-12-26 | Steven Chervets | Dynamic media throttling based on data quotas |
GB2503289B (en) * | 2012-06-22 | 2018-10-31 | 5Th Tier Ltd | Network provisioning |
EP2864908A2 (en) | 2012-06-22 | 2015-04-29 | 5th Tier Limited | Methods and apparatuses for modifying browser requests and responses and for provisioning a network based on browser traffic at an intermediary entity |
US9137281B2 (en) | 2012-06-22 | 2015-09-15 | Guest Tek Interactive Entertainment Ltd. | Dynamically enabling guest device supporting network-based media sharing protocol to share media content over local area computer network of lodging establishment with subset of in-room media devices connected thereto |
US9282898B2 (en) | 2012-06-25 | 2016-03-15 | Sprint Communications Company L.P. | End-to-end trusted communications infrastructure |
US10143018B2 (en) | 2012-06-27 | 2018-11-27 | Google Llc | Computing device with wireless network selection feature |
US9137656B2 (en) * | 2012-06-27 | 2015-09-15 | Rogers Communications Inc. | System and method for remote provisioning of embedded universal integrated circuit cards |
US8984598B2 (en) * | 2012-06-27 | 2015-03-17 | International Business Machines Corporation | Web-based security proxy for computing system environment scanning |
US8862882B2 (en) * | 2012-06-29 | 2014-10-14 | Intel Corporation | Systems and methods for authenticating devices by adding secure features to Wi-Fi tags |
US9037978B2 (en) * | 2012-06-29 | 2015-05-19 | Infinera Corporation | Digital link viewer |
US8843122B1 (en) | 2012-06-29 | 2014-09-23 | Sprint Communications Company L.P. | Mobile phone controls preprocessor |
TWI492155B (en) * | 2012-07-04 | 2015-07-11 | Hong Mo Yeh | Methods and systems for executing applications on mobile devices using cloud services |
GB2513795B (en) * | 2012-07-12 | 2016-03-30 | Pismo Labs Technology Ltd | Managing actions of a network device |
US10204073B2 (en) | 2012-07-12 | 2019-02-12 | Pismo Labs Technology Limited | Managing actions of a network device based on policy settings corresponding to a removable wireless communication device |
WO2014011216A1 (en) | 2012-07-13 | 2014-01-16 | Seven Networks, Inc. | Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications |
JP6514639B2 (en) | 2012-07-14 | 2019-05-15 | テケレック・インコーポレイテッドTekelec, Inc. | Method, system and computer readable medium for dynamically controlling congestion in a radio access network |
CN104429103B (en) | 2012-07-14 | 2019-03-08 | 泰科来股份有限公司 | For local method, system and the computer-readable medium for shunting (LBO) based on strategy |
US10169571B1 (en) * | 2012-07-18 | 2019-01-01 | Sequitur Labs, Inc. | System and method for secure, policy-based access control for mobile computing devices |
FR2993737B1 (en) * | 2012-07-18 | 2015-01-02 | Commissariat Energie Atomique | METHOD FOR MANAGING THE CONFIGURATION OF A TELECOMMUNICATION NETWORK |
US10477385B2 (en) * | 2012-07-20 | 2019-11-12 | Tekelec, Inc. | Methods, systems and computer readable media for distributing policy rules to the mobile edge |
US8843398B2 (en) * | 2012-07-23 | 2014-09-23 | Wal-Mart Stores, Inc. | Transferring digital receipt data to mobile devices |
US8738454B2 (en) * | 2012-07-23 | 2014-05-27 | Wal-Mart Stores, Inc. | Transferring digital receipt data to mobile devices |
US9608901B2 (en) | 2012-07-24 | 2017-03-28 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for enabling services chaining in a provider network |
US8737962B2 (en) | 2012-07-24 | 2014-05-27 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US9432268B2 (en) * | 2013-01-28 | 2016-08-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for placing services in a network |
US9584371B2 (en) | 2012-07-24 | 2017-02-28 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for assigning multi-instance services in a provider network |
US10219205B2 (en) | 2012-07-27 | 2019-02-26 | Calamp Corp. | Multiple network mode selection devices |
US9430778B2 (en) | 2012-07-30 | 2016-08-30 | Kount Inc. | Authenticating users for accurate online audience measurement |
US8676709B2 (en) | 2012-07-31 | 2014-03-18 | Google Inc. | Merchant category codes in a proxy card transaction |
US9413839B2 (en) | 2012-07-31 | 2016-08-09 | Sprint Communications Company L.P. | Traffic management of third party applications |
EP2880619A1 (en) | 2012-08-02 | 2015-06-10 | The 41st Parameter, Inc. | Systems and methods for accessing records via derivative locators |
US8699993B2 (en) * | 2012-08-03 | 2014-04-15 | Tracfone Wireless, Inc. | Device initiated replenishment procedures for wireless devices |
JP5980037B2 (en) * | 2012-08-06 | 2016-08-31 | キヤノン株式会社 | Management system, server, client, and method thereof |
US20140047079A1 (en) * | 2012-08-07 | 2014-02-13 | Advanced Micro Devices, Inc. | System and method for emulating a desired network configuration in a cloud computing system |
US9338115B2 (en) * | 2012-08-08 | 2016-05-10 | Microsoft Technology Licensing, Llc | Content based message delivery |
US8774824B1 (en) * | 2012-08-08 | 2014-07-08 | Sprint Communications Company L.P. | Alleviating and overriding throttled conditions in LTE |
US9183412B2 (en) | 2012-08-10 | 2015-11-10 | Sprint Communications Company L.P. | Systems and methods for provisioning and using multiple trusted security zones on an electronic device |
EP2883384B1 (en) | 2012-08-10 | 2019-10-16 | iBasis, Inc. | Signaling traffic reduction in mobile communication systems |
US11469914B2 (en) * | 2012-08-10 | 2022-10-11 | Viasat, Inc. | System, method and apparatus for subscriber user interfaces |
US8805779B2 (en) * | 2012-08-14 | 2014-08-12 | Longsand Limited | Applying an action on a data item according to a classification and a data management policy |
WO2014028712A1 (en) | 2012-08-15 | 2014-02-20 | Telecommunication Systems, Inc. | Device independent caller data access for emergency calls |
CN103596157A (en) * | 2012-08-15 | 2014-02-19 | 中兴通讯股份有限公司 | Method and device for billing local traffic on wireless side |
US8806526B2 (en) * | 2012-08-17 | 2014-08-12 | Broadcom Corporation | Security processing unit with secure connection to head end |
US10237763B1 (en) * | 2012-08-18 | 2019-03-19 | Global Eagle Entertainment Inc. | Real time data meter |
US8805921B2 (en) * | 2012-08-20 | 2014-08-12 | International Business Machines Corporation | System and method supporting application solution composition on cloud |
WO2014031689A1 (en) | 2012-08-24 | 2014-02-27 | Oceus Networks Inc. | Mobile cellular networks |
WO2014031597A1 (en) | 2012-08-24 | 2014-02-27 | Oceus Networks Inc. | Mobile cellular networks |
CN102890705A (en) * | 2012-08-24 | 2013-01-23 | 东莞宇龙通信科技有限公司 | Method and system for managing storage medium and mobile terminal |
TWI463886B (en) * | 2012-08-27 | 2014-12-01 | Hon Hai Prec Ind Co Ltd | System and method for managing processor utilization of a customer premise equipment |
US10203972B2 (en) * | 2012-08-27 | 2019-02-12 | Vmware, Inc. | Framework for networking and security services in virtual networks |
CN102868685B (en) * | 2012-08-29 | 2015-04-15 | 北京神州绿盟信息安全科技股份有限公司 | Method and device for judging automatic scanning behavior |
EP2863583A4 (en) * | 2012-08-31 | 2015-07-29 | Huawei Tech Co Ltd | Method and device for defending bearer attack |
US8745290B2 (en) * | 2012-09-10 | 2014-06-03 | Hobnob, Inc. | Multi-modem device |
US9313640B2 (en) * | 2012-09-12 | 2016-04-12 | Opennet Telecom Ltd. | System and method for performing multi-enforcement point charging |
WO2014047069A1 (en) | 2012-09-18 | 2014-03-27 | Jvl Ventures, Llc | Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements |
US9198027B2 (en) | 2012-09-18 | 2015-11-24 | Sprint Communications Company L.P. | Generic mobile devices customization framework |
US11521139B2 (en) | 2012-09-24 | 2022-12-06 | Amazon Technologies, Inc. | Providing system resources with secure containment units |
US9231774B2 (en) * | 2012-09-27 | 2016-01-05 | Alcatel Lucent | Congestion control for radio access networks (RAN) |
US20140095690A1 (en) * | 2012-09-28 | 2014-04-03 | Alcatel-Lucent Usa Inc. | Real time rules engine for policies orchestration in a mobile telecommunications network |
WO2014050143A1 (en) * | 2012-09-28 | 2014-04-03 | Nec Corporation | Communication system, control apparatus, control method, and program |
US10511497B2 (en) * | 2012-10-04 | 2019-12-17 | Fortinet, Inc. | System and method for dynamic management of network device data |
CN103716881B (en) * | 2012-10-08 | 2018-08-14 | 华为技术有限公司 | It eats dishes without rice or wine information processing system, method and apparatus |
US9769795B2 (en) * | 2012-10-09 | 2017-09-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods, a broadcast management unit and a user equipment for handling digital content in a cellular communications network |
US10225597B2 (en) | 2012-10-09 | 2019-03-05 | Comcast Cable Communications, Llc | Transmission and consumption of time-shifted content in a one-way communication environment |
US9787644B2 (en) | 2012-10-11 | 2017-10-10 | Mobile Search Security LLC | System and method for machine-to-machine privacy and security brokered transactions |
US9392077B2 (en) | 2012-10-12 | 2016-07-12 | Citrix Systems, Inc. | Coordinating a computing activity across applications and devices having multiple operation modes in an orchestration framework for connected devices |
US9774658B2 (en) | 2012-10-12 | 2017-09-26 | Citrix Systems, Inc. | Orchestration framework for connected devices |
WO2014056202A1 (en) * | 2012-10-12 | 2014-04-17 | 华为技术有限公司 | Method and advertisement server for providing network information for terminal |
US9516022B2 (en) | 2012-10-14 | 2016-12-06 | Getgo, Inc. | Automated meeting room |
US8938053B2 (en) | 2012-10-15 | 2015-01-20 | Twilio, Inc. | System and method for triggering on platform usage |
US20140109176A1 (en) | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Configuring and providing profiles that manage execution of mobile applications |
US8948356B2 (en) | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
US20140109171A1 (en) | 2012-10-15 | 2014-04-17 | Citrix Systems, Inc. | Providing Virtualized Private Network tunnels |
US8910239B2 (en) | 2012-10-15 | 2014-12-09 | Citrix Systems, Inc. | Providing virtualized private network tunnels |
US9606774B2 (en) | 2012-10-16 | 2017-03-28 | Citrix Systems, Inc. | Wrapping an application with field-programmable business logic |
US9971585B2 (en) | 2012-10-16 | 2018-05-15 | Citrix Systems, Inc. | Wrapping unmanaged applications on a mobile device |
EP2909715B1 (en) | 2012-10-16 | 2022-12-14 | Citrix Systems, Inc. | Application wrapping for application management framework |
US20140108793A1 (en) | 2012-10-16 | 2014-04-17 | Citrix Systems, Inc. | Controlling mobile device access to secure data |
US9253101B2 (en) * | 2012-10-17 | 2016-02-02 | Alcatel Lucent | Method and apparatus of group credit control for wireless networks |
US9247432B2 (en) * | 2012-10-19 | 2016-01-26 | Airwatch Llc | Systems and methods for controlling network access |
US20140113616A1 (en) * | 2012-10-19 | 2014-04-24 | Sony Mobile Communications Ab | Network initiated terminal background activity control |
CN103780926A (en) * | 2012-10-22 | 2014-05-07 | 中兴通讯股份有限公司 | IPTV value-added service management system and method |
US9258353B2 (en) | 2012-10-23 | 2016-02-09 | Microsoft Technology Licensing, Llc | Multiple buffering orders for digital content item |
US9300742B2 (en) * | 2012-10-23 | 2016-03-29 | Microsoft Technology Licensing, Inc. | Buffer ordering based on content access tracking |
US9442709B1 (en) | 2012-10-24 | 2016-09-13 | Sprint Communications Company L.P. | Transition experience during loading and updating an interface and applications pack |
US9161258B2 (en) | 2012-10-24 | 2015-10-13 | Seven Networks, Llc | Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion |
US9325575B2 (en) | 2012-10-31 | 2016-04-26 | Aruba Networks, Inc. | Zero touch provisioning |
EP2728813B1 (en) * | 2012-11-02 | 2017-01-04 | Telefonaktiebolaget LM Ericsson (publ) | Application function dependent policy control |
US20140137190A1 (en) * | 2012-11-09 | 2014-05-15 | Rapid7, Inc. | Methods and systems for passively detecting security levels in client devices |
US9426209B2 (en) * | 2012-11-12 | 2016-08-23 | Sap Se | Upload/download of mobile applications using a MIME repository |
US9042252B2 (en) * | 2012-11-13 | 2015-05-26 | Netronome Systems, Incorporated | Inter-packet interval prediction learning algorithm |
US8893222B2 (en) * | 2012-11-13 | 2014-11-18 | Auckland Uniservices Ltd. | Security system and method for the android operating system |
WO2014078569A1 (en) | 2012-11-14 | 2014-05-22 | The 41St Parameter, Inc. | Systems and methods of global identification |
US9171151B2 (en) * | 2012-11-16 | 2015-10-27 | Microsoft Technology Licensing, Llc | Reputation-based in-network filtering of client event information |
US8898769B2 (en) * | 2012-11-16 | 2014-11-25 | At&T Intellectual Property I, Lp | Methods for provisioning universal integrated circuit cards |
WO2014080993A1 (en) * | 2012-11-22 | 2014-05-30 | 日本電気株式会社 | Communication system, virtual-network management device, communication node, and communication method and program |
US10136355B2 (en) | 2012-11-26 | 2018-11-20 | Vasona Networks, Inc. | Reducing signaling load on a mobile network |
WO2014085605A2 (en) * | 2012-11-28 | 2014-06-05 | Intrepid Networks, Llc | Integrated systems and methods providing situational awareness of operations in an organization |
KR101980834B1 (en) * | 2012-11-28 | 2019-05-21 | 한국전자통신연구원 | Method and apparatus for managing applications based on contexts |
EP2738672B1 (en) * | 2012-11-30 | 2016-09-14 | Accenture Global Services Limited | Communications network, computer architecture, computer-implemented method and computer program product for development and management of femtocell-based applications |
US9338225B2 (en) | 2012-12-06 | 2016-05-10 | A10 Networks, Inc. | Forwarding policies on a virtual service network |
US9215591B2 (en) | 2012-12-06 | 2015-12-15 | At&T Intellectual Property I, L.P. | Security for network load broadcasts over cellular networks |
US9456301B2 (en) | 2012-12-11 | 2016-09-27 | Telecommunication Systems, Inc. | Efficient prisoner tracking |
US20140172569A1 (en) * | 2012-12-14 | 2014-06-19 | International Advertising Solutions | Method for Implementing a Customizable Interactive Menu System with User Interaction Data Analysis Capability by Executing Computer-Executable Instructions Stored On a Non-Transitory Computer-Readable Medium |
US9788188B2 (en) | 2012-12-14 | 2017-10-10 | Ibasis, Inc. | Method and system for hub breakout roaming |
US8832435B2 (en) * | 2012-12-17 | 2014-09-09 | International Business Machines Corporation | Providing a real-time indication of platform trust |
US9485159B1 (en) * | 2012-12-17 | 2016-11-01 | Juniper Networks, Inc. | Rules-based network service management with on-demand dependency insertion |
US9271188B2 (en) * | 2012-12-18 | 2016-02-23 | At&T Intellectual Property I, L.P. | Dynamic in-band service control mechanism in mobile network |
RU2519503C1 (en) * | 2012-12-19 | 2014-06-10 | Закрытое акционерное общество "Аладдин Р.Д." | Method and system for improving security of electronic internet transactions |
CN103139870A (en) * | 2012-12-19 | 2013-06-05 | 中兴通讯股份有限公司 | Data access method and data access device |
WO2014094836A1 (en) * | 2012-12-19 | 2014-06-26 | Telefonaktiebolaget L M Ericsson (Publ) | Extending global operator device id to aggregated devices |
US20140177497A1 (en) | 2012-12-20 | 2014-06-26 | Seven Networks, Inc. | Management of mobile device radio state promotion and demotion |
US8910262B2 (en) * | 2012-12-21 | 2014-12-09 | Cellco Partnership | Supporting multiple messaging services on mobile devices in a single user experience |
US20140189648A1 (en) * | 2012-12-27 | 2014-07-03 | Nvidia Corporation | Facilitated quality testing |
US9219732B2 (en) | 2012-12-28 | 2015-12-22 | Nok Nok Labs, Inc. | System and method for processing random challenges within an authentication framework |
US9083689B2 (en) | 2012-12-28 | 2015-07-14 | Nok Nok Labs, Inc. | System and method for implementing privacy classes within an authentication framework |
US9172687B2 (en) * | 2012-12-28 | 2015-10-27 | Nok Nok Labs, Inc. | Query system and method to determine authentication capabilities |
US9306754B2 (en) | 2012-12-28 | 2016-04-05 | Nok Nok Labs, Inc. | System and method for implementing transaction signing within an authentication framework |
US9015482B2 (en) | 2012-12-28 | 2015-04-21 | Nok Nok Labs, Inc. | System and method for efficiently enrolling, registering, and authenticating with multiple authentication devices |
US9609575B2 (en) | 2012-12-31 | 2017-03-28 | T-Mobile Usa, Inc. | Intelligent routing of network packets on telecommunication devices |
US10375629B2 (en) * | 2012-12-31 | 2019-08-06 | T-Mobile Usa, Inc. | Service preferences for multiple-carrier-enabled devices |
US9253254B2 (en) | 2013-01-14 | 2016-02-02 | Twilio, Inc. | System and method for offering a multi-partner delegated platform |
US9274935B1 (en) * | 2013-01-15 | 2016-03-01 | Google Inc. | Application testing system with application programming interface |
US9451446B2 (en) | 2013-01-18 | 2016-09-20 | Sprint Communications Company L.P. | SIM profile brokering system |
US8909291B1 (en) | 2013-01-18 | 2014-12-09 | Sprint Communications Company L.P. | Dynamic remotely managed SIM profile |
US9749321B2 (en) * | 2013-01-22 | 2017-08-29 | Prolifiq Software Inc. | System for multi-point publication syndication |
US9271238B2 (en) | 2013-01-23 | 2016-02-23 | Seven Networks, Llc | Application or context aware fast dormancy |
US9275206B2 (en) * | 2013-01-23 | 2016-03-01 | International Business Machines Corporation | Managing sensitive information |
US8874761B2 (en) | 2013-01-25 | 2014-10-28 | Seven Networks, Inc. | Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols |
US9135145B2 (en) | 2013-01-28 | 2015-09-15 | Rackspace Us, Inc. | Methods and systems of distributed tracing |
US9397902B2 (en) | 2013-01-28 | 2016-07-19 | Rackspace Us, Inc. | Methods and systems of tracking and verifying records of system change events in a distributed network system |
US9521004B2 (en) * | 2013-01-28 | 2016-12-13 | Rackspace Us, Inc. | Methods and systems of generating a billing feed of a distributed network |
US9882713B1 (en) | 2013-01-30 | 2018-01-30 | vIPtela Inc. | Method and system for key generation, distribution and management |
US8863276B2 (en) | 2013-01-31 | 2014-10-14 | International Business Machines Corporation | Automated role adjustment in a computer system |
US20150172946A1 (en) * | 2013-02-07 | 2015-06-18 | Multiple Access Technologies, Inc. | Remote and live rf network measurement and optimization |
US9100769B2 (en) * | 2013-02-08 | 2015-08-04 | Sprint Communications Company L.P. | System and method of storing service brand packages on a mobile device |
US9549009B1 (en) | 2013-02-08 | 2017-01-17 | Sprint Communications Company L.P. | Electronic fixed brand labeling |
US9100819B2 (en) | 2013-02-08 | 2015-08-04 | Sprint-Communications Company L.P. | System and method of provisioning and reprovisioning a mobile device based on self-locating |
US20140237081A1 (en) * | 2013-02-15 | 2014-08-21 | Zhongwen Zhu | Method and multimedia content manager for managing multimedia content download |
WO2014127322A1 (en) | 2013-02-18 | 2014-08-21 | Headwater Partners I Llc | Enhanced curfew and protection associated with a device group |
US9363388B2 (en) | 2013-02-18 | 2016-06-07 | Tekelec, Inc. | Methods, systems, and computer readable media for providing targeted services to telecommunications network subscribers based on information extracted from network signaling and data traffic |
US9215133B2 (en) | 2013-02-20 | 2015-12-15 | Tekelec, Inc. | Methods, systems, and computer readable media for detecting orphan Sy or Rx sessions using audit messages with fake parameter values |
US9137091B2 (en) * | 2013-02-20 | 2015-09-15 | Novatel Wireless, Inc. | Dynamic quality of service for control of media streams using feedback from the local environment |
US8817652B1 (en) * | 2013-02-20 | 2014-08-26 | 46 Labs Ops | Call routing and real-time monitoring |
US9071959B2 (en) | 2013-02-21 | 2015-06-30 | International Business Machines Corporation | Service awareness and seamless switchover between client based WiFi access and mobile data network access |
EP3627428A1 (en) * | 2013-02-21 | 2020-03-25 | CFM Global LLC | Data farm metering |
US9480101B2 (en) * | 2013-02-21 | 2016-10-25 | Altiostar Networks, Inc. | Systems and methods for scheduling of data packets based on application detection in a base station |
US9607156B2 (en) | 2013-02-22 | 2017-03-28 | Duo Security, Inc. | System and method for patching a device through exploitation |
US8893230B2 (en) | 2013-02-22 | 2014-11-18 | Duo Security, Inc. | System and method for proxying federated authentication protocols |
US10339542B2 (en) | 2013-02-22 | 2019-07-02 | Avatier Corporation | Store intelligence—in-store analytics |
US9443073B2 (en) | 2013-08-08 | 2016-09-13 | Duo Security, Inc. | System and method for verifying status of an authentication device |
US9338156B2 (en) | 2013-02-22 | 2016-05-10 | Duo Security, Inc. | System and method for integrating two-factor authentication in a device |
US9887911B2 (en) * | 2013-02-28 | 2018-02-06 | Xaptum, Inc. | Systems, methods, and devices for adaptive communication in a data communication network |
US9705957B2 (en) * | 2013-03-04 | 2017-07-11 | Open Garden Inc. | Virtual channel joining |
US20140258509A1 (en) * | 2013-03-05 | 2014-09-11 | Aerohive Networks, Inc. | Systems and methods for context-based network data analysis and monitoring |
US8694055B1 (en) | 2013-03-05 | 2014-04-08 | Metropcs Wireless, Inc. | System and method for selection of wireless service provider via a mobile terminal |
US9270765B2 (en) | 2013-03-06 | 2016-02-23 | Netskope, Inc. | Security for network delivered services |
US9372785B2 (en) | 2013-03-07 | 2016-06-21 | Microsoft Technology Licensing, Llc | Identifying implicit assumptions associated with a software product |
US8750123B1 (en) | 2013-03-11 | 2014-06-10 | Seven Networks, Inc. | Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network |
JP6123366B2 (en) * | 2013-03-11 | 2017-05-10 | 株式会社リコー | Cost management system, cost management device, cost management method, cost management program, and recording medium |
US20140258231A1 (en) * | 2013-03-11 | 2014-09-11 | Eran Birk | Device synchronization policy management |
US10007938B2 (en) | 2013-03-13 | 2018-06-26 | Aeris Communication, Inc. | Real-time priced (RTP) cellular service marketplace |
US9772919B2 (en) | 2013-03-14 | 2017-09-26 | Accenture Global Services Limited | Automation of D-bus communication testing for bluetooth profiles |
US9349365B2 (en) | 2013-03-14 | 2016-05-24 | Accenture Global Services Limited | Voice based automation testing for hands free module |
US9374700B2 (en) * | 2013-03-14 | 2016-06-21 | Tyntec Limited | Global local SIM |
US9282124B2 (en) | 2013-03-14 | 2016-03-08 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US9432520B2 (en) | 2013-03-14 | 2016-08-30 | Tracfone Wireless, Inc. | Proxy-based usage tracking for a wireless device |
US9026105B2 (en) | 2013-03-14 | 2015-05-05 | Sprint Communications Company L.P. | System for activating and customizing a mobile device via near field communication |
US9426154B2 (en) * | 2013-03-14 | 2016-08-23 | Amazon Technologies, Inc. | Providing devices as a service |
US10332142B2 (en) * | 2013-03-14 | 2019-06-25 | Datascape, Inc. | System and method for incentivizing wireless device users to interact with sponsor offers and advertising |
KR102170178B1 (en) * | 2013-03-14 | 2020-10-26 | 삼성전자주식회사 | Method and device for controlling use of external data network via mobile access point |
US9408056B2 (en) | 2013-03-15 | 2016-08-02 | T-Mobile Usa, Inc. | Systems and methods for improving telecommunications device experiences |
EP3493564B1 (en) | 2013-03-15 | 2020-09-09 | Intel Corporation | Budgeting and quota management system for data consumption |
EP3661164B1 (en) * | 2013-03-15 | 2022-06-22 | Headwater Research LLC | Network service plan design |
US20140280758A1 (en) * | 2013-03-15 | 2014-09-18 | Verizon Patent And Licensing Inc. | Methods and Systems for Providing Location-Based Subsidized Access to Network Content |
WO2014144837A1 (en) | 2013-03-15 | 2014-09-18 | A10 Networks, Inc. | Processing data packets using a policy based network path |
US9354983B1 (en) * | 2013-03-15 | 2016-05-31 | Entreda, Inc. | Integrated it service provisioning and management |
US9001666B2 (en) | 2013-03-15 | 2015-04-07 | Twilio, Inc. | System and method for improving routing in a distributed communication platform |
US9204286B1 (en) | 2013-03-15 | 2015-12-01 | Sprint Communications Company L.P. | System and method of branding and labeling a mobile device |
US8983047B2 (en) | 2013-03-20 | 2015-03-17 | Telecommunication Systems, Inc. | Index of suspicion determination for communications request |
US9887983B2 (en) | 2013-10-29 | 2018-02-06 | Nok Nok Labs, Inc. | Apparatus and method for implementing composite authenticators |
US9305298B2 (en) | 2013-03-22 | 2016-04-05 | Nok Nok Labs, Inc. | System and method for location-based authentication |
EP2782041B1 (en) * | 2013-03-22 | 2018-11-14 | F. Hoffmann-La Roche AG | Analysis system ensuring that sensitive data are not accessible |
US10270748B2 (en) | 2013-03-22 | 2019-04-23 | Nok Nok Labs, Inc. | Advanced authentication techniques and applications |
US10284627B2 (en) | 2013-03-29 | 2019-05-07 | Citrix Systems, Inc. | Data management for an application with multiple operation modes |
US9355223B2 (en) | 2013-03-29 | 2016-05-31 | Citrix Systems, Inc. | Providing a managed browser |
US9985850B2 (en) | 2013-03-29 | 2018-05-29 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US8996889B2 (en) * | 2013-03-29 | 2015-03-31 | Dropbox, Inc. | Portable computing device with methodologies for client-side analytic data collection |
US9413736B2 (en) | 2013-03-29 | 2016-08-09 | Citrix Systems, Inc. | Providing an enterprise application store |
US8813179B1 (en) | 2013-03-29 | 2014-08-19 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US20140297840A1 (en) * | 2013-03-29 | 2014-10-02 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US8849979B1 (en) | 2013-03-29 | 2014-09-30 | Citrix Systems, Inc. | Providing mobile device management functionalities |
US9510199B2 (en) | 2013-04-03 | 2016-11-29 | Nokia Technologies Oy | Soft activation of cellular modems in tablets |
US9882919B2 (en) | 2013-04-10 | 2018-01-30 | Illumio, Inc. | Distributed network security using a logical multi-dimensional label-based policy model |
KR101579715B1 (en) * | 2013-04-10 | 2015-12-22 | 일루미오, 아이엔씨. | Distributed Network Management Using a Logical Multi-Dimensional Label-Based Policy Model |
WO2014172386A2 (en) | 2013-04-15 | 2014-10-23 | Seven Networks, Inc. | Temporary or partial offloading of mobile applicaton functions to a cloud-based environment |
EP2797279B1 (en) * | 2013-04-23 | 2016-09-14 | Gurulogic Microsystems OY | Communications using at least two different media types |
US9794379B2 (en) | 2013-04-26 | 2017-10-17 | Cisco Technology, Inc. | High-efficiency service chaining with agentless service nodes |
WO2014179235A1 (en) | 2013-04-29 | 2014-11-06 | Oceus Networks Inc. | Mobile cellular network backhaul |
US9553787B1 (en) | 2013-04-29 | 2017-01-24 | Amazon Technologies, Inc. | Monitoring hosted service usage |
US9922580B2 (en) | 2013-04-30 | 2018-03-20 | Google Llc | Apparatus and method for the virtual demonstration of a smart phone controlled smart home using a website |
US9386010B2 (en) * | 2013-05-02 | 2016-07-05 | Globalfoundries Inc. | Abstracted authenticated client connectivity application programming interface (API) |
US10038693B2 (en) | 2013-05-03 | 2018-07-31 | A10 Networks, Inc. | Facilitating secure network traffic by an application delivery controller |
US9609144B2 (en) * | 2013-05-03 | 2017-03-28 | Qualcomm Incorporated | Method for policy control and charging for D2D services |
GB2516412A (en) * | 2013-05-03 | 2015-01-28 | Vodafone Ip Licensing Ltd | Access control |
US9412116B2 (en) | 2013-05-07 | 2016-08-09 | Yp, Llc | Systems, methods and machine-readable media for facilitating provisioning of platforms |
US8842578B1 (en) * | 2013-05-09 | 2014-09-23 | Yehuda Zisapel | End-to-end (E2E) application packet flow visibility |
US9591692B2 (en) | 2013-05-10 | 2017-03-07 | Elwha Llc | Dynamic point to point mobile network including destination device aspects system and method |
US9686417B2 (en) | 2013-05-10 | 2017-06-20 | Giesecke & Devrient Mobile Security America, Inc. | Device, computer-readable medium, and method for modifying services using advanced data collection capabilities |
US9356681B2 (en) | 2013-05-10 | 2016-05-31 | Elwha Llc | Dynamic point to point mobile network including destination device aspects system and method |
US9559766B2 (en) | 2013-05-10 | 2017-01-31 | Elwha Llc | Dynamic point to point mobile network including intermediate device aspects system and method |
US9380467B2 (en) | 2013-05-10 | 2016-06-28 | Elwha Llc | Dynamic point to point mobile network including intermediate device aspects system and method |
US9930190B2 (en) | 2013-05-10 | 2018-03-27 | Giesecke+Devrient Mobile Security America, Inc. | Device, computer-readable medium, and method for modifying services using advanced data collection capabilities |
US9414181B2 (en) | 2013-05-10 | 2016-08-09 | Giesecke & Devrient America, Inc. | Device, computer-readable medium, and method for retaining services |
US9787545B2 (en) | 2013-05-10 | 2017-10-10 | Elwha Llc | Dynamic point to point mobile network including origination device aspects system and method |
US9763166B2 (en) * | 2013-05-10 | 2017-09-12 | Elwha Llc | Dynamic point to point mobile network including communication path monitoring and analysis aspects system and method |
US9246918B2 (en) * | 2013-05-10 | 2016-01-26 | Airwatch Llc | Secure application leveraging of web filter proxy services |
US9832728B2 (en) | 2013-05-10 | 2017-11-28 | Elwha Llc | Dynamic point to point mobile network including origination user interface aspects system and method |
US9686420B2 (en) | 2013-05-10 | 2017-06-20 | Giesecke & Devrient Mobile Security America, Inc. | Device, computer-readable medium, and method for retaining services using advanced data collection capabilities |
US9042877B1 (en) | 2013-05-21 | 2015-05-26 | Sprint Communications Company L.P. | System and method for retrofitting a branding framework into a mobile communication device |
US10743177B2 (en) | 2013-05-21 | 2020-08-11 | Syniverse Technologies, Llc | Method and apparatus to provide mobile intelligence |
US9294912B1 (en) | 2013-05-22 | 2016-03-22 | Quantcast Corporation | Selective regulation of information transmission from mobile applications to third-party privacy complaint target systems |
US9280483B1 (en) | 2013-05-22 | 2016-03-08 | Sprint Communications Company L.P. | Rebranding a portable electronic device while maintaining user data |
CN103309705B (en) * | 2013-05-23 | 2016-11-16 | 北京微云即趣科技有限公司 | End application Activiation method and system |
US20140351420A1 (en) * | 2013-05-24 | 2014-11-27 | Connectloud, Inc. | Method for deterministic service offering for enterprise computing environment |
CN103281371A (en) * | 2013-05-29 | 2013-09-04 | 滁州友林科技发展有限公司 | System and method for controlling pumping unit in long distance based on 4G mobile network |
US9961077B2 (en) | 2013-05-30 | 2018-05-01 | Nok Nok Labs, Inc. | System and method for biometric authentication with device attestation |
CN103347257B (en) * | 2013-06-05 | 2016-08-24 | 华为技术有限公司 | Virtual user identification data distribution method, acquisition methods and equipment |
US20140365634A1 (en) * | 2013-06-05 | 2014-12-11 | Cisco Technology, Inc. | Programmable Network Analytics Processing via an Inspect/Apply-Action Applied to Physical and Virtual Entities |
KR101651957B1 (en) * | 2013-06-05 | 2016-08-29 | 가부시키가이샤 히타치 시스테무즈 | Portal site cost distribution/recovery system |
US20140372361A1 (en) * | 2013-06-14 | 2014-12-18 | Electronics And Telecommunications Research Institute | Apparatus and method for providing subscriber big data information in cloud computing environment |
US10546040B2 (en) * | 2013-06-14 | 2020-01-28 | Microsoft Technology Licensing Llc | System and method for automatic provisioning of companion resources in a web hosting environment |
US9071705B2 (en) * | 2013-06-19 | 2015-06-30 | Telefonaktiebolaget L M Ericsson (Publ) | Synchronizing charging for telecommunication service with notification of applicable tariff |
US9160696B2 (en) | 2013-06-19 | 2015-10-13 | Twilio, Inc. | System for transforming media resource into destination device compatible messaging format |
US9225840B2 (en) | 2013-06-19 | 2015-12-29 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9338280B2 (en) * | 2013-06-19 | 2016-05-10 | Twilio, Inc. | System and method for managing telephony endpoint inventory |
TWI506574B (en) * | 2013-06-20 | 2015-11-01 | Chunghwa Telecom Co Ltd | A flexible system of deployment for cloud network service |
KR102153585B1 (en) * | 2013-06-24 | 2020-09-09 | 한국전자통신연구원 | Method and apparatus for network functions virtualization |
US20140379539A1 (en) * | 2013-06-24 | 2014-12-25 | Infosys Limited | Systems and methods for generating billing data of a composite cloud service |
US9112790B2 (en) | 2013-06-25 | 2015-08-18 | Google Inc. | Fabric network |
US9319535B2 (en) * | 2013-06-25 | 2016-04-19 | Syniverse Technologies, Llc | Method and apparatus to collect, analyze, and utilize network data |
EP3014428A4 (en) * | 2013-06-28 | 2017-03-22 | Samsung Electronics Co., Ltd. | Method and apparatus for updating application |
US9819552B2 (en) * | 2013-07-02 | 2017-11-14 | Seven Networks, Llc | Modeling network signaling in a mobile network |
WO2015002545A1 (en) * | 2013-07-05 | 2015-01-08 | Sgx As | Method and system related to authentication of users for accessing data networks |
US9307450B2 (en) | 2013-07-11 | 2016-04-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for content caching in a wireless communication network |
US9483328B2 (en) | 2013-07-19 | 2016-11-01 | Twilio, Inc. | System and method for delivering application content |
KR20150010872A (en) * | 2013-07-19 | 2015-01-29 | 삼성전자주식회사 | Display apparatus and Method for providing user interface thereof |
US9065765B2 (en) | 2013-07-22 | 2015-06-23 | Seven Networks, Inc. | Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network |
US20150024720A1 (en) * | 2013-07-22 | 2015-01-22 | Vonage Network Llc | Remote Testing Through Third Party Devices |
US9167104B2 (en) * | 2013-07-25 | 2015-10-20 | Airwatch Llc | Telecommunications data usage management |
US9674193B1 (en) | 2013-07-30 | 2017-06-06 | Juniper Networks, Inc. | Aggregation and disbursement of licenses in distributed networks |
US20150039485A1 (en) * | 2013-07-31 | 2015-02-05 | Metratech Corp. | Billing transaction currency normalization |
WO2015015251A1 (en) * | 2013-08-01 | 2015-02-05 | Yogesh Chunilal Rathod | Presenting plurality types of interfaces and functions for conducting various activities |
US11397520B2 (en) | 2013-08-01 | 2022-07-26 | Yogesh Chunilal Rathod | Application program interface or page processing method and device |
US9053310B2 (en) | 2013-08-08 | 2015-06-09 | Duo Security, Inc. | System and method for verifying status of an authentication device through a biometric profile |
US9532211B1 (en) | 2013-08-15 | 2016-12-27 | Sprint Communications Company L.P. | Directing server connection based on location identifier |
US9247440B2 (en) | 2013-08-15 | 2016-01-26 | Qualcomm Incorporated | Automatic configuration of a network device |
US9161209B1 (en) | 2013-08-21 | 2015-10-13 | Sprint Communications Company L.P. | Multi-step mobile device initiation with intermediate partial reset |
US20150058481A1 (en) * | 2013-08-22 | 2015-02-26 | Bruce D. Miller | Method & apparatus for measuring power, bandwidth and monitoring the operation of a network infrastructure from another network infrastructure |
CN104254997B (en) * | 2013-08-27 | 2017-06-06 | 华为终端有限公司 | The transmission method and base station, user equipment of a kind of machine type communication downlink data |
US9125037B2 (en) | 2013-08-27 | 2015-09-01 | Sprint Communications Company L.P. | System and methods for deferred and remote device branding |
US9204239B1 (en) | 2013-08-27 | 2015-12-01 | Sprint Communications Company L.P. | Segmented customization package within distributed server architecture |
US9143924B1 (en) | 2013-08-27 | 2015-09-22 | Sprint Communications Company L.P. | Segmented customization payload delivery |
US9413463B2 (en) | 2013-08-30 | 2016-08-09 | Google Inc. | Apparatus and method for efficient two-way optical communication where transmitter may interfere with receiver |
US10902327B1 (en) | 2013-08-30 | 2021-01-26 | The 41St Parameter, Inc. | System and method for device identification and uniqueness |
US9408034B2 (en) | 2013-09-09 | 2016-08-02 | Telecommunication Systems, Inc. | Extended area event for network based proximity discovery |
US9092302B2 (en) | 2013-09-10 | 2015-07-28 | Duo Security, Inc. | System and method for determining component version compatibility across a device ecosystem |
US9608814B2 (en) | 2013-09-10 | 2017-03-28 | Duo Security, Inc. | System and method for centralized key distribution |
US9516104B2 (en) | 2013-09-11 | 2016-12-06 | Telecommunication Systems, Inc. | Intelligent load balancer enhanced routing |
US9036820B2 (en) | 2013-09-11 | 2015-05-19 | At&T Intellectual Property I, Lp | System and methods for UICC-based secure communication |
US10129242B2 (en) * | 2013-09-16 | 2018-11-13 | Airwatch Llc | Multi-persona devices and management |
US9274858B2 (en) | 2013-09-17 | 2016-03-01 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US9137127B2 (en) | 2013-09-17 | 2015-09-15 | Twilio, Inc. | System and method for providing communication platform metadata |
US9338018B2 (en) | 2013-09-17 | 2016-05-10 | Twilio, Inc. | System and method for pricing communication of a telecommunication platform |
US10097694B1 (en) | 2013-09-27 | 2018-10-09 | Google Llc | Method and system for moving phone call participation between carrier and data networks |
US9479897B2 (en) | 2013-10-03 | 2016-10-25 | Telecommunication Systems, Inc. | SUPL-WiFi access point controller location based services for WiFi enabled mobile devices |
US9124573B2 (en) | 2013-10-04 | 2015-09-01 | At&T Intellectual Property I, Lp | Apparatus and method for managing use of secure tokens |
CN104579721B (en) * | 2013-10-10 | 2018-07-24 | 施耐德电器工业公司 | Communication device and protective relaying device |
US9549318B2 (en) | 2013-10-10 | 2017-01-17 | Shaw Cablesystems G.P. | System and method for delayed device registration on a network |
US20150106513A1 (en) * | 2013-10-14 | 2015-04-16 | Ideaware Inc. | System and method for operating network traffic reduction policy in overloaded area |
US9155034B1 (en) | 2013-10-16 | 2015-10-06 | Sprint Communications Company L.P. | Wireless Communication Device and method for hand-up from less-capable to more-capable communication protocol |
US20150112767A1 (en) * | 2013-10-17 | 2015-04-23 | Cisco Technology, Inc. | System and method for using network mobility events to build advertising demographics |
US10069811B2 (en) * | 2013-10-17 | 2018-09-04 | Arm Ip Limited | Registry apparatus, agent device, application providing apparatus and corresponding methods |
US9743271B2 (en) | 2013-10-23 | 2017-08-22 | Sprint Communications Company L.P. | Delivery of branding content and customizations to a mobile communication device |
US10506398B2 (en) | 2013-10-23 | 2019-12-10 | Sprint Communications Company Lp. | Implementation of remotely hosted branding content and customizations |
US9208300B2 (en) | 2013-10-23 | 2015-12-08 | At&T Intellectual Property I, Lp | Apparatus and method for secure authentication of a communication device |
KR20150047831A (en) * | 2013-10-25 | 2015-05-06 | 한국전자통신연구원 | Apparatus and method for transmitting data of collected from smart device |
US9240994B2 (en) | 2013-10-28 | 2016-01-19 | At&T Intellectual Property I, Lp | Apparatus and method for securely managing the accessibility to content and applications |
US9231915B2 (en) * | 2013-10-29 | 2016-01-05 | A 10 Networks, Incorporated | Method and apparatus for optimizing hypertext transfer protocol (HTTP) uniform resource locator (URL) filtering |
US9544331B2 (en) * | 2013-10-31 | 2017-01-10 | Aruba Networks, Inc. | Method and system for controlling access to shared devices |
US9313660B2 (en) | 2013-11-01 | 2016-04-12 | At&T Intellectual Property I, Lp | Apparatus and method for secure provisioning of a communication device |
US9240989B2 (en) | 2013-11-01 | 2016-01-19 | At&T Intellectual Property I, Lp | Apparatus and method for secure over the air programming of a communication device |
US9301081B1 (en) | 2013-11-06 | 2016-03-29 | Sprint Communications Company L.P. | Delivery of oversized branding elements for customization |
US9363622B1 (en) | 2013-11-08 | 2016-06-07 | Sprint Communications Company L.P. | Separation of client identification composition from customization payload to original equipment manufacturer layer |
US10039028B2 (en) | 2013-11-12 | 2018-07-31 | Vasona Networks Inc. | Congestion in a wireless network |
US9553799B2 (en) | 2013-11-12 | 2017-01-24 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
WO2015071891A1 (en) | 2013-11-12 | 2015-05-21 | Vasona Networks Inc. | Supervision of data in a wireless network |
US10341881B2 (en) | 2013-11-12 | 2019-07-02 | Vasona Networks, Inc. | Supervision of data in a wireless network |
US9325624B2 (en) | 2013-11-12 | 2016-04-26 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US10382305B2 (en) | 2013-11-15 | 2019-08-13 | Microsoft Technology Licensing, Llc | Applying sequenced instructions to connect through captive portals |
US9087156B2 (en) * | 2013-11-15 | 2015-07-21 | Google Inc. | Application version release management |
JP6437541B2 (en) * | 2013-11-15 | 2018-12-12 | TenTen株式会社 | Method, system and mobile device for providing reward to a user |
US9369342B2 (en) | 2013-11-15 | 2016-06-14 | Microsoft Technology Licensing, Llc | Configuring captive portals with a cloud service |
US9554323B2 (en) | 2013-11-15 | 2017-01-24 | Microsoft Technology Licensing, Llc | Generating sequenced instructions for connecting through captive portals |
WO2015073979A1 (en) * | 2013-11-15 | 2015-05-21 | Good Technology Corporation | Authentication system |
JP6204800B2 (en) * | 2013-11-18 | 2017-09-27 | キヤノン株式会社 | COMMUNICATION DEVICE, COMMUNICATION DEVICE CONTROL METHOD, AND PROGRAM |
US9916462B1 (en) * | 2013-11-18 | 2018-03-13 | Securus Technologies, Inc. | Interception of unauthorized communications in an controlled-environment facility |
US9781046B1 (en) * | 2013-11-19 | 2017-10-03 | Tripwire, Inc. | Bandwidth throttling in vulnerability scanning applications |
US9161325B1 (en) | 2013-11-20 | 2015-10-13 | Sprint Communications Company L.P. | Subscriber identity module virtualization |
EP3072332B1 (en) * | 2013-11-21 | 2020-09-23 | Vodafone IP Licensing Limited | Telecommunication networks |
US9167453B2 (en) | 2013-11-25 | 2015-10-20 | At&T Intellectual Property I, L.P. | Cell and evolved node B station outage restoration tool |
US10333724B2 (en) | 2013-11-25 | 2019-06-25 | Oracle International Corporation | Method and system for low-overhead latency profiling |
WO2015075962A1 (en) * | 2013-11-25 | 2015-05-28 | 日本電気株式会社 | Information collection system, server, edge device, control method, and program |
WO2015079114A1 (en) * | 2013-11-27 | 2015-06-04 | Nokia Technologies Oy | Methods and apparatus for testing of interworking |
KR101470976B1 (en) * | 2013-12-03 | 2014-12-09 | 주식회사 안동통신 | The anticrime system in a school zone |
US20150156264A1 (en) * | 2013-12-04 | 2015-06-04 | International Business Machines Corporation | File access optimization using strategically partitioned and positioned data in conjunction with a collaborative peer transfer system |
US9319324B2 (en) | 2013-12-06 | 2016-04-19 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system of service placement for service chaining |
US9591560B2 (en) * | 2013-12-10 | 2017-03-07 | Verizon Patent And Licensing Inc. | Temporary credential assignment when connecting to roaming wireless networks |
WO2015095509A1 (en) * | 2013-12-18 | 2015-06-25 | Joseph Schuman | Systems, methods and associated program products to minimize, retrieve, secure and selectively distribute personal data |
US20150172469A1 (en) * | 2013-12-18 | 2015-06-18 | Telefonaktiebolaget L M Ericsson (Publ) | Method and Apparatus for Pre-Fetched Content Charging |
US9467478B1 (en) | 2013-12-18 | 2016-10-11 | vIPtela Inc. | Overlay management protocol for secure routing based on an overlay network |
DE102013021966A1 (en) * | 2013-12-20 | 2015-06-25 | Giesecke & Devrient Gmbh | A method and apparatus for providing a subscription for communication over a cellular network |
US9407664B1 (en) * | 2013-12-23 | 2016-08-02 | Symantec Corporation | Systems and methods for enforcing enterprise data access control policies in cloud computing environments |
US10088818B1 (en) | 2013-12-23 | 2018-10-02 | Google Llc | Systems and methods for programming and controlling devices with sensor data and learning |
EP3076703A4 (en) * | 2013-12-26 | 2016-11-23 | Huawei Tech Co Ltd | Network video issuing method, device and system |
JP6260272B2 (en) * | 2013-12-27 | 2018-01-17 | ブラザー工業株式会社 | Information processing program, information processing apparatus, and information processing apparatus control method |
WO2015101804A1 (en) * | 2013-12-31 | 2015-07-09 | Turkcell Teknoloji Arastirma Ve Gelistirme A.S. | Modifying mobile data speed of an outbound roamer |
US20150188761A1 (en) * | 2013-12-31 | 2015-07-02 | Top Victory Investments Ltd. | Method for Opening Network Connection of Display Device |
US9877188B1 (en) | 2014-01-03 | 2018-01-23 | Google Llc | Wireless network access credential sharing using a network based credential storage service |
US9860136B2 (en) * | 2014-01-07 | 2018-01-02 | Verizon Patent And Licensing Inc. | Providing network congestion information to mobile devices for sponsored data |
WO2015104525A1 (en) | 2014-01-08 | 2015-07-16 | Vodafone Ip Licensing Limited | Telecommunications network with optimisation of content delivery |
US9699160B2 (en) | 2014-01-10 | 2017-07-04 | Verato, Inc. | System and methods for exchanging identity information among independent enterprises which may include person enabled correlation |
US9705870B2 (en) | 2014-01-10 | 2017-07-11 | Verato, Inc. | System and methods for exchanging identity information among independent enterprises |
US9762702B2 (en) | 2014-01-14 | 2017-09-12 | Apple Inc. | Multipath TCP signaling with application specific tags |
US10341929B2 (en) | 2014-01-14 | 2019-07-02 | Google Llc | PSTN / VoIP communication system and method |
US9392395B1 (en) | 2014-01-16 | 2016-07-12 | Sprint Communications Company L.P. | Background delivery of device configuration and branding |
US10432658B2 (en) * | 2014-01-17 | 2019-10-01 | Watchguard Technologies, Inc. | Systems and methods for identifying and performing an action in response to identified malicious network traffic |
US9742624B2 (en) * | 2014-01-21 | 2017-08-22 | Oracle International Corporation | Logging incident manager |
US9603009B1 (en) * | 2014-01-24 | 2017-03-21 | Sprint Communications Company L.P. | System and method of branding a device independent of device activation |
US9420496B1 (en) | 2014-01-24 | 2016-08-16 | Sprint Communications Company L.P. | Activation sequence using permission based connection to network |
US10565623B2 (en) * | 2014-01-28 | 2020-02-18 | Oath Inc. | Systems and methods for ad-supported mobile data plans or in-app purchases |
US9197994B2 (en) * | 2014-01-29 | 2015-11-24 | Kaseya Limited | Identifying mobile device location and corresponding support center locations to provide support services over a network |
US9807639B2 (en) * | 2014-01-30 | 2017-10-31 | Shine Security Ltd. | Network traffic event management at the client terminal level |
US9513888B1 (en) | 2014-01-30 | 2016-12-06 | Sprint Communications Company L.P. | Virtual preloads |
US10263903B2 (en) | 2014-02-05 | 2019-04-16 | Ibasis, Inc. | Method and apparatus for managing communication flow in an inter-network system |
US9629018B2 (en) | 2014-02-05 | 2017-04-18 | Ibasis, Inc. | Method and apparatus for triggering management of communication flow in an inter-network system |
US9503975B2 (en) | 2014-02-07 | 2016-11-22 | Open Garden Inc. | Exchanging energy credits wirelessly |
US9832043B2 (en) * | 2014-02-07 | 2017-11-28 | Verizon Patent And Licensing Inc. | Bandwidth boosting in shared local networks |
KR20150094260A (en) * | 2014-02-11 | 2015-08-19 | 한국전자통신연구원 | Apparatus and method for supporting verification of network service chaining in software defined netwoking, and formal verification apparatus having the appratus |
US9656161B1 (en) | 2014-02-20 | 2017-05-23 | Aftershock Services, Inc. | System and method for facilitating assumption of player identity in an online game |
CA2942681C (en) | 2014-02-23 | 2023-09-26 | Brian Peebles | System and methods for enabling sponsored data access across multiple carriers |
EP3101928B1 (en) * | 2014-02-27 | 2018-05-23 | Huawei Technologies Co., Ltd. | Method and system for providing service according to policy |
US10878323B2 (en) | 2014-02-28 | 2020-12-29 | Tyco Fire & Security Gmbh | Rules engine combined with message routing |
US9851982B2 (en) | 2014-02-28 | 2017-12-26 | Tyco Fire & Security Gmbh | Emergency video camera system |
US10152864B2 (en) | 2014-02-28 | 2018-12-11 | Tyco Fire & Security Gmbh | Distributed rules engines for robust sensor networks |
US11405463B2 (en) | 2014-03-03 | 2022-08-02 | Icontrol Networks, Inc. | Media content management |
US11146637B2 (en) | 2014-03-03 | 2021-10-12 | Icontrol Networks, Inc. | Media content management |
EP3107351B1 (en) * | 2014-03-05 | 2018-05-23 | Huawei Technologies Co., Ltd. | Data forwarding control method, controller and access point |
US9697545B1 (en) * | 2014-03-11 | 2017-07-04 | Vmware, Inc. | Service monitor for monitoring and tracking the performance of an application running on different mobile devices |
JP2015173406A (en) * | 2014-03-12 | 2015-10-01 | 株式会社東芝 | Analysis system, analysis device, and analysis program |
JP6273927B2 (en) * | 2014-03-12 | 2018-02-07 | 富士通株式会社 | Information processing system, monitoring device, monitoring program, and monitoring method |
US9265067B2 (en) * | 2014-03-12 | 2016-02-16 | Verizon Patent And Licensing Inc. | Controlling connection to an access network by machine-to-machine devices |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US9413900B2 (en) | 2014-03-24 | 2016-08-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for online charging of pre-fetched content |
US9942152B2 (en) | 2014-03-25 | 2018-04-10 | A10 Networks, Inc. | Forwarding data packets using a service-based forwarding policy |
US9306985B1 (en) * | 2014-03-25 | 2016-04-05 | 8X8, Inc. | User configurable data storage |
US20150280946A1 (en) * | 2014-03-27 | 2015-10-01 | Qualcomm Incorporated | Feedback receive path with low-if mode |
US9681251B1 (en) | 2014-03-31 | 2017-06-13 | Sprint Communications Company L.P. | Customization for preloaded applications |
CN104954220B (en) * | 2014-03-31 | 2018-01-16 | 华为技术有限公司 | A kind of virtual network service deployment method and apparatus |
US9485801B1 (en) | 2014-04-04 | 2016-11-01 | Sprint Communications Company L.P. | Mobile communication device connected to home digital network |
EP3941016A1 (en) * | 2014-04-08 | 2022-01-19 | Family Zone Cyber Safety Ltd. | A device management system |
JP6102820B2 (en) * | 2014-04-10 | 2017-03-29 | 横河電機株式会社 | Engineering method |
US9647888B2 (en) * | 2014-05-30 | 2017-05-09 | Belkin International Inc. | Network addressable appliance interface device |
US10560975B2 (en) | 2014-04-16 | 2020-02-11 | Belkin International, Inc. | Discovery of connected devices to determine control capabilities and meta-information |
US9226217B2 (en) | 2014-04-17 | 2015-12-29 | Twilio, Inc. | System and method for enabling multi-modal communication |
US9762590B2 (en) | 2014-04-17 | 2017-09-12 | Duo Security, Inc. | System and method for an integrity focused authentication service |
US10122753B2 (en) | 2014-04-28 | 2018-11-06 | Sophos Limited | Using reputation to avoid false malware detections |
US9917851B2 (en) | 2014-04-28 | 2018-03-13 | Sophos Limited | Intrusion detection using a heartbeat |
US9521576B2 (en) * | 2014-04-28 | 2016-12-13 | Intel IP Corporation | System and method of performance measurements for wireless local area network access points |
ES2760875T3 (en) | 2014-04-30 | 2020-05-18 | Affirmed Networks Inc | Optimization of capacity extension in a mobile network |
US9713006B2 (en) | 2014-05-01 | 2017-07-18 | At&T Intellectual Property I, Lp | Apparatus and method for managing security domains for a universal integrated circuit card |
US9680942B2 (en) * | 2014-05-01 | 2017-06-13 | Visa International Service Association | Data verification using access device |
US9654469B1 (en) | 2014-05-02 | 2017-05-16 | Nok Nok Labs, Inc. | Web-based user authentication techniques and applications |
US9577999B1 (en) | 2014-05-02 | 2017-02-21 | Nok Nok Labs, Inc. | Enhanced security for registration of authentication devices |
US20150326497A1 (en) * | 2014-05-08 | 2015-11-12 | Oracle International Corporation | Group based policy management |
US10425536B2 (en) * | 2014-05-08 | 2019-09-24 | Ubiquiti Networks, Inc. | Phone systems and methods of communication |
WO2015174989A1 (en) | 2014-05-15 | 2015-11-19 | Hewlett-Packard Development Company, L.P. | Network traffic tuning |
WO2015174988A1 (en) * | 2014-05-15 | 2015-11-19 | Hewlett-Packard Development Company, L.P. | Network scheduling |
US10305748B2 (en) | 2014-05-19 | 2019-05-28 | The Michael Harrison Tretter Auerbach Trust | Dynamic computer systems and uses thereof |
US9742853B2 (en) | 2014-05-19 | 2017-08-22 | The Michael Harrison Tretter Auerbach Trust | Dynamic computer systems and uses thereof |
US10666735B2 (en) | 2014-05-19 | 2020-05-26 | Auerbach Michael Harrison Tretter | Dynamic computer systems and uses thereof |
US9344914B2 (en) * | 2014-05-21 | 2016-05-17 | Qualcomm Incorporated | Modem assisted contention handling of multiple active connections in wireless communications |
US9451444B2 (en) * | 2014-05-22 | 2016-09-20 | Cellco Partnership | Systems and methods for providing modem behavior-based setup for user devices |
US10313264B2 (en) * | 2014-05-28 | 2019-06-04 | Apple Inc. | Sharing account data between different interfaces to a service |
CN105228126B (en) * | 2014-05-30 | 2019-10-22 | 华为技术有限公司 | A kind of method and system of network access point trustship |
US10789642B2 (en) | 2014-05-30 | 2020-09-29 | Apple Inc. | Family accounts for an online content storage sharing service |
US20150358482A1 (en) * | 2014-06-04 | 2015-12-10 | Karma Mobility Inc. | Source selection for shared network connectivity |
US9560211B2 (en) * | 2014-06-04 | 2017-01-31 | Alcatel-Lucent Usa Inc. | Error handling for CDR transport within an offline charging system |
US9426641B1 (en) | 2014-06-05 | 2016-08-23 | Sprint Communications Company L.P. | Multiple carrier partition dynamic access on a mobile device |
US9553998B2 (en) | 2014-06-09 | 2017-01-24 | Oracle International Corporation | Sharing group notification |
MX369700B (en) * | 2014-06-11 | 2019-11-19 | Giesecke Devrient Mobile Security America Inc | Device, computer-readable medium, and method for retaining services using advnced data collection capabilities. |
US20150365379A1 (en) * | 2014-06-12 | 2015-12-17 | Gryphon Online Safety, Inc. | System and method for managing, controlling and configuring an intelligent parental control filter |
CN103997791B (en) * | 2014-06-13 | 2017-10-27 | 重庆大学 | The wireless network resource distribution method and system of preference are used based on user terminals resources |
WO2016004558A1 (en) | 2014-06-18 | 2016-01-14 | 华为技术有限公司 | Heartbeat adjustment method, device and terminal |
US9565578B2 (en) | 2014-06-18 | 2017-02-07 | Google Inc. | Method for collecting and aggregating network quality data |
US9380615B2 (en) * | 2014-06-19 | 2016-06-28 | Verizon Telematics Inc. | Managing a group of wireless devices in close proximity |
KR102218715B1 (en) * | 2014-06-19 | 2021-02-23 | 삼성전자주식회사 | Semiconductor device for protecting data per channel |
US10180890B2 (en) * | 2014-06-19 | 2019-01-15 | Telefonaktiebolaget L M Ericsson (Publ) | Systems and methods for monitoring hardware observation points within a system on a Chip (SoC) |
CN105323270B (en) * | 2014-06-20 | 2019-05-03 | 博雅网络游戏开发(深圳)有限公司 | Network information push method and system |
US20150382244A1 (en) * | 2014-06-27 | 2015-12-31 | T-Mobile Usa, Inc. | Upsell Framework for Network Services |
US9531714B2 (en) * | 2014-06-27 | 2016-12-27 | Citrix Systems, Inc. | Enterprise authentication via third party authentication support |
US9286001B2 (en) * | 2014-06-30 | 2016-03-15 | Microsoft Licensing Technology Llc | Effective range partition splitting in scalable storage |
US9386141B2 (en) | 2014-07-06 | 2016-07-05 | Robert Osann, Jr. | Automatic notification of potential emergency condition during travel |
US9516101B2 (en) | 2014-07-07 | 2016-12-06 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US10140827B2 (en) | 2014-07-07 | 2018-11-27 | Google Llc | Method and system for processing motion event notifications |
US9251371B2 (en) | 2014-07-07 | 2016-02-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9246694B1 (en) | 2014-07-07 | 2016-01-26 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US10127783B2 (en) | 2014-07-07 | 2018-11-13 | Google Llc | Method and device for processing motion events |
US9449229B1 (en) | 2014-07-07 | 2016-09-20 | Google Inc. | Systems and methods for categorizing motion event candidates |
US9420331B2 (en) | 2014-07-07 | 2016-08-16 | Google Inc. | Method and system for categorizing detected motion events |
US9774687B2 (en) | 2014-07-07 | 2017-09-26 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US9501915B1 (en) | 2014-07-07 | 2016-11-22 | Google Inc. | Systems and methods for analyzing a video stream |
US9354794B2 (en) | 2014-07-07 | 2016-05-31 | Google Inc. | Method and system for performing client-side zooming of a remote video feed |
US10390289B2 (en) | 2014-07-11 | 2019-08-20 | Sensoriant, Inc. | Systems and methods for mediating representations allowing control of devices located in an environment having broadcasting devices |
US20160012453A1 (en) | 2014-07-11 | 2016-01-14 | Shamim A. Naqvi | System and Method for Inferring the Intent of a User While Receiving Signals On a Mobile Communication Device From a Broadcasting Device |
US10412230B2 (en) | 2014-07-14 | 2019-09-10 | Google Llc | System and method for retail SIM marketplace |
KR102191017B1 (en) * | 2014-07-19 | 2020-12-15 | 삼성전자주식회사 | Method and server device for provisioning an embedded SIM |
US9749131B2 (en) | 2014-07-31 | 2017-08-29 | Nok Nok Labs, Inc. | System and method for implementing a one-time-password using asymmetric cryptography |
US10148630B2 (en) | 2014-07-31 | 2018-12-04 | Nok Nok Labs, Inc. | System and method for implementing a hosted authentication service |
US9875347B2 (en) | 2014-07-31 | 2018-01-23 | Nok Nok Labs, Inc. | System and method for performing authentication using data analytics |
US9814009B2 (en) | 2014-08-01 | 2017-11-07 | Google Llc | Multiple carrier attachment establishment and maintenance |
US11507663B2 (en) | 2014-08-11 | 2022-11-22 | Sentinel Labs Israel Ltd. | Method of remediating operations performed by a program and system thereof |
US10102374B1 (en) | 2014-08-11 | 2018-10-16 | Sentinel Labs Israel Ltd. | Method of remediating a program and system thereof by undoing operations |
US9710648B2 (en) | 2014-08-11 | 2017-07-18 | Sentinel Labs Israel Ltd. | Method of malware detection and system thereof |
US9830167B2 (en) * | 2014-08-12 | 2017-11-28 | Linkedin Corporation | Enhancing a multitasking user interface of an operating system |
EP3183839B1 (en) * | 2014-08-18 | 2020-10-21 | Nokia Solutions and Networks Oy | Group communication service enabler security |
EP2988467A1 (en) * | 2014-08-20 | 2016-02-24 | Agco Corporation | Wireless out-of-band authentication for a controller area network |
CA2959022C (en) * | 2014-08-22 | 2020-12-08 | Level 3 Communications, Llc | Software defined networking portal |
US9479937B2 (en) * | 2014-08-22 | 2016-10-25 | Ebay, Inc. | Using a wireless beacon to provide access credentials to a secure network |
US10200292B2 (en) * | 2014-08-25 | 2019-02-05 | Intel Corporation | Technologies for aligning network flows to processing resources |
KR102182512B1 (en) * | 2014-08-27 | 2020-11-25 | 아씨아 에스피이, 엘엘씨 | Systems, methods, and apparatuses for implementing the virtualization of access node functions |
CN105446872B (en) * | 2014-08-29 | 2018-04-10 | 国际商业机器公司 | Test manager, test agent device and the method for Mobile solution |
US9307400B1 (en) | 2014-09-02 | 2016-04-05 | Sprint Communications Company L.P. | System and method of efficient mobile device network brand customization |
US8984612B1 (en) * | 2014-09-04 | 2015-03-17 | Google Inc. | Method of identifying an electronic device by browser versions and cookie scheduling |
US9762450B2 (en) | 2014-09-04 | 2017-09-12 | Accenture Global Services Limited | System architecture for cloud-platform infrastructure layouts |
US9794266B2 (en) | 2014-09-05 | 2017-10-17 | Qualcomm Incorporated | Using multiple credentials for access and traffic differentiation |
US10354082B2 (en) * | 2014-09-06 | 2019-07-16 | Airwatch Llc | Document state interface |
US20160070431A1 (en) | 2014-09-06 | 2016-03-10 | Airwatch Llc | Sync based on navigation history |
US9819573B2 (en) | 2014-09-11 | 2017-11-14 | Microsoft Technology Licensing, Llc | Method for scalable computer network partitioning |
KR102284050B1 (en) * | 2014-09-11 | 2021-07-30 | 삼성전자주식회사 | Method and apparatus for controlling traffic of electronic device in wireless communication system |
US20160078581A1 (en) * | 2014-09-16 | 2016-03-17 | The Government of the United States of America, as Represented by the Secretary, Department of Homel | Mobile customs declaration system and method |
US9736154B2 (en) | 2014-09-16 | 2017-08-15 | Nok Nok Labs, Inc. | System and method for integrating an authentication service within a network architecture |
US9544225B2 (en) * | 2014-09-16 | 2017-01-10 | Microsoft Technology Licensing, Llc | Method for end point identification in computer networks |
US9392438B2 (en) | 2014-09-24 | 2016-07-12 | Motorola Solutions, Inc. | Method and apparatus to manage user/device profiles for public safety applications |
US10091174B2 (en) * | 2014-09-29 | 2018-10-02 | Dropbox, Inc. | Identifying related user accounts based on authentication data |
US9853929B2 (en) * | 2014-09-30 | 2017-12-26 | Apple Inc. | Service compatibility check for messages |
US10095500B2 (en) | 2014-09-30 | 2018-10-09 | Apple Inc. | Revision locking |
USD782495S1 (en) | 2014-10-07 | 2017-03-28 | Google Inc. | Display screen or portion thereof with graphical user interface |
US9544395B2 (en) | 2014-10-10 | 2017-01-10 | At&T Intellectual Property I, L.P. | Facilitating quality of service and security via functional classification of devices in networks |
US10091312B1 (en) | 2014-10-14 | 2018-10-02 | The 41St Parameter, Inc. | Data structures for intelligently resolving deterministic and probabilistic device identifiers to device profiles and/or groups |
US9781004B2 (en) | 2014-10-16 | 2017-10-03 | Cisco Technology, Inc. | Discovering and grouping application endpoints in a network environment |
US9247413B1 (en) | 2014-10-17 | 2016-01-26 | Motorola Solutions, Inc. | Method and apparatus for flexible fast network switching |
US9749428B2 (en) | 2014-10-21 | 2017-08-29 | Twilio, Inc. | System and method for providing a network discovery service platform |
US9521151B2 (en) | 2014-10-22 | 2016-12-13 | CloudHealth Technologies, Inc. | Automated and policy driven optimization of cloud infrastructure through delegated actions |
WO2016064550A1 (en) * | 2014-10-24 | 2016-04-28 | Verato, Inc. | System and methods for exchanging identity information among independent enterprises |
US11966907B2 (en) * | 2014-10-25 | 2024-04-23 | Yoongnet Inc. | System and method for mobile cross-authentication |
US9652465B2 (en) * | 2014-10-30 | 2017-05-16 | Lenovo (Singapore) Pte. Ltd. | Aggregate service with enhanced cloud device management |
US9971611B2 (en) * | 2014-10-31 | 2018-05-15 | Cisco Technology, Inc. | Monitoring a mobile device application |
US11687947B2 (en) * | 2014-10-31 | 2023-06-27 | Aeris Communications, Inc. | Automatic connected vehicle enrollment |
US9992326B1 (en) | 2014-10-31 | 2018-06-05 | Sprint Communications Company L.P. | Out of the box experience (OOBE) country choice using Wi-Fi layer transmission |
US9760501B2 (en) | 2014-11-05 | 2017-09-12 | Google Inc. | In-field smart device updates |
US20160128104A1 (en) * | 2014-11-05 | 2016-05-05 | Google Inc. | In-field smart device updates |
US10891690B1 (en) | 2014-11-07 | 2021-01-12 | Intuit Inc. | Method and system for providing an interactive spending analysis display |
US10268467B2 (en) * | 2014-11-11 | 2019-04-23 | A10 Networks, Inc. | Policy-driven management of application traffic for providing services to cloud-based applications |
US10601604B2 (en) | 2014-11-12 | 2020-03-24 | Google Llc | Data processing systems and methods for smart hub devices |
KR102211004B1 (en) * | 2014-11-18 | 2021-02-02 | 삼성전자 주식회사 | Method and apparatus for providing a service at a terminal in a mobile communication system |
WO2016078006A1 (en) * | 2014-11-19 | 2016-05-26 | 华为技术有限公司 | Directional traffic statistics method, device and system |
CN105682070A (en) * | 2014-11-20 | 2016-06-15 | 中兴通讯股份有限公司 | Sponsor business decision method and device |
US9529994B2 (en) | 2014-11-24 | 2016-12-27 | Shape Security, Inc. | Call stack integrity check on client/server systems |
JP6394325B2 (en) * | 2014-11-26 | 2018-09-26 | 富士通株式会社 | Network control method, communication apparatus, and communication system |
US9510209B2 (en) * | 2014-12-01 | 2016-11-29 | Viavi Solutions Uk Limited | Techniques for providing a small cell deployment plan |
US9349285B1 (en) | 2014-12-01 | 2016-05-24 | Here Global B.V. | Traffic classification based on spatial neighbor model |
US9660909B2 (en) | 2014-12-11 | 2017-05-23 | Cisco Technology, Inc. | Network service header metadata for load balancing |
USRE48131E1 (en) | 2014-12-11 | 2020-07-28 | Cisco Technology, Inc. | Metadata augmentation in a service function chain |
US10200866B1 (en) | 2014-12-12 | 2019-02-05 | Aeris Communications, Inc. | Method and system for detecting and minimizing harmful network device and application behavior on cellular networks |
US10193837B2 (en) * | 2014-12-12 | 2019-01-29 | At&T Intellectual Property I, L.P. | Presence-based communications |
US9774613B2 (en) | 2014-12-15 | 2017-09-26 | Sophos Limited | Server drift monitoring |
US9419989B2 (en) | 2014-12-15 | 2016-08-16 | Sophos Limited | Threat detection using URL cache hits |
US9571512B2 (en) * | 2014-12-15 | 2017-02-14 | Sophos Limited | Threat detection using endpoint variance |
GB201915196D0 (en) | 2014-12-18 | 2019-12-04 | Sophos Ltd | A method and system for network access control based on traffic monitoring and vulnerability detection using process related information |
RU2598337C2 (en) * | 2014-12-19 | 2016-09-20 | Закрытое акционерное общество "Лаборатория Касперского" | System and method of selecting means of interception of data transmitted over network |
US9785606B2 (en) * | 2014-12-22 | 2017-10-10 | Intel Corporation | Systems, methods, and devices for media agnostic USB packet scheduling |
US9906420B2 (en) | 2014-12-22 | 2018-02-27 | International Business Machines Corporation | Dynamic boundary based monitoring and metering |
US20160180328A1 (en) * | 2014-12-22 | 2016-06-23 | Capital One Services, Llc | Systems and Methods for Services Enrollment Using a Mobile Device |
US9852301B2 (en) * | 2014-12-24 | 2017-12-26 | Intel Corporation | Creating secure channels between a protected execution environment and fixed-function endpoints |
CN107113659A (en) * | 2014-12-25 | 2017-08-29 | 华为技术有限公司 | A kind of method and apparatus of business game deployment |
US10909069B2 (en) * | 2015-01-05 | 2021-02-02 | Iguazio Systems Ltd. | Service oriented data management and architecture |
US9979719B2 (en) | 2015-01-06 | 2018-05-22 | Duo Security, Inc. | System and method for converting one-time passcodes to app-based authentication |
US9787594B2 (en) | 2015-01-08 | 2017-10-10 | Coriant Operations, Inc. | Procedures, apparatuses, systems, and computer program products for adaptive tunnel bandwidth by using software defined networking |
US10855645B2 (en) | 2015-01-09 | 2020-12-01 | Microsoft Technology Licensing, Llc | EPC node selection using custom service types |
US10038591B1 (en) | 2015-01-09 | 2018-07-31 | Juniper Networks, Inc. | Apparatus, system, and method for secure remote configuration of network devices |
US10302329B2 (en) * | 2015-01-19 | 2019-05-28 | Lennox Industries, Inc. | Device for operating a heating, ventilation, and air conditioning network |
US10270774B1 (en) * | 2015-01-26 | 2019-04-23 | Microstrategy Incorporated | Electronic credential and analytics integration |
US10635724B2 (en) | 2015-01-30 | 2020-04-28 | International Business Machines Corporation | Analysis of data utilization |
US9967351B2 (en) * | 2015-01-31 | 2018-05-08 | Splunk Inc. | Automated service discovery in I.T. environments |
WO2016126491A1 (en) | 2015-02-02 | 2016-08-11 | Eero, Inc. | Systems and methods for intuitive home networking |
US10918924B2 (en) | 2015-02-02 | 2021-02-16 | RLT IP Ltd. | Frameworks, devices and methodologies configured to enable delivery of interactive skills training content, including content with multiple selectable expert knowledge variations |
US10536917B2 (en) * | 2015-02-03 | 2020-01-14 | Nokia Solutions And Networks Oy | Dual connectivity for different access networks |
US9654978B2 (en) * | 2015-02-03 | 2017-05-16 | Qualcomm Incorporated | Asset accessibility with continuous authentication for mobile devices |
US9477975B2 (en) | 2015-02-03 | 2016-10-25 | Twilio, Inc. | System and method for a media intelligence platform |
US9875346B2 (en) | 2015-02-06 | 2018-01-23 | Apple Inc. | Setting and terminating restricted mode operation on electronic devices |
US9736229B2 (en) * | 2015-02-17 | 2017-08-15 | Microsoft Technology Licensing, Llc | Device with embedded network subscription and methods |
US10298647B2 (en) * | 2015-02-26 | 2019-05-21 | Qualcomm Incorporated | Delay compensation for broadcast adaptive bitrate streaming |
US10200486B2 (en) | 2015-02-26 | 2019-02-05 | Urban Airship, Inc. | Mobile event notifications for network enabled objects |
US9794290B2 (en) * | 2015-02-26 | 2017-10-17 | Symantec Corporation | Quantitative security improvement system based on crowdsourcing |
US9787719B2 (en) | 2015-02-26 | 2017-10-10 | Symantec Corporation | Trusted third party broker for collection and private sharing of successful computer security practices |
US9357378B1 (en) | 2015-03-04 | 2016-05-31 | Sprint Communications Company L.P. | Subscriber identity module (SIM) card initiation of custom application launcher installation on a mobile communication device |
US9398462B1 (en) | 2015-03-04 | 2016-07-19 | Sprint Communications Company L.P. | Network access tiered based on application launcher installation |
US10887203B2 (en) * | 2015-03-09 | 2021-01-05 | Schlumberger Technology Corporation | Dynamic scada |
US10601766B2 (en) * | 2015-03-13 | 2020-03-24 | Hewlett Packard Enterprise Development Lp | Determine anomalous behavior based on dynamic device configuration address range |
US9936422B2 (en) * | 2015-03-16 | 2018-04-03 | Aruba Networks, Inc. | Client association management for improving MU-MIMO transmissions |
JP6551513B2 (en) | 2015-03-19 | 2019-07-31 | 日本電気株式会社 | Billing apparatus, method, system, and program |
US9998510B2 (en) * | 2015-03-20 | 2018-06-12 | Walter Partos | Video-based social interaction system |
AU2016236821A1 (en) * | 2015-03-23 | 2017-09-28 | Gloriam Technologies Pty Ltd | A method and system for providing a social network for creating, sharing and accessing content based upon location and mobility-related profiles of users |
US9716701B1 (en) * | 2015-03-24 | 2017-07-25 | Trend Micro Incorporated | Software as a service scanning system and method for scanning web traffic |
US9781024B2 (en) * | 2015-03-25 | 2017-10-03 | International Business Machines Corporation | Supporting low latency applications at the edge of wireless communication networks |
US9531556B2 (en) * | 2015-03-25 | 2016-12-27 | International Business Machines Corporation | Supporting low latency applications at the edge of wireless communication networks |
CN104811438B (en) * | 2015-03-26 | 2018-01-23 | 网宿科技股份有限公司 | Asynchronous anti-stealing link method and system based on scheduling system |
WO2016154785A1 (en) * | 2015-03-27 | 2016-10-06 | 华为技术有限公司 | Cloud platform, application operation method and access network unit |
US9641341B2 (en) | 2015-03-31 | 2017-05-02 | Duo Security, Inc. | Method for distributed trust authentication |
WO2016159998A1 (en) | 2015-03-31 | 2016-10-06 | Hewlett-Packard Development Company, L.P. | Application access based on network |
US9980304B2 (en) | 2015-04-03 | 2018-05-22 | Google Llc | Adaptive on-demand tethering |
US10225795B2 (en) | 2015-04-07 | 2019-03-05 | At&T Intellectual Property I, L.P. | Resource-sensitive token-based access point selection |
US9648537B2 (en) | 2015-04-17 | 2017-05-09 | Google Inc. | Profile switching powered by location |
CN107787592B (en) * | 2015-04-22 | 2021-08-31 | 捷德移动安全有限责任公司 | Apparatus, computer readable medium, and method for changing service using advanced data collection capability |
US10200909B2 (en) * | 2015-04-27 | 2019-02-05 | Michael Lu | Open wireless architecture (OWA) mobile cloud infrastructure and method |
JP2016207111A (en) * | 2015-04-28 | 2016-12-08 | 富士通株式会社 | Control program, information processing terminal, and control method |
US10298563B2 (en) | 2015-04-29 | 2019-05-21 | Hewlett Packard Enterprise Development Lp | Multi-factor authorization for IEEE 802.1x-enabled networks |
US9723470B1 (en) * | 2015-04-30 | 2017-08-01 | Tensera Networks Ltd. | Selective enabling of data services to roaming wireless terminals |
US10021618B2 (en) | 2015-04-30 | 2018-07-10 | Google Technology Holdings LLC | Apparatus and method for cloud assisted wireless mobility |
US9483253B1 (en) | 2015-04-30 | 2016-11-01 | Sprint Communications Company L.P. | Methods for customization of default applications on a mobile communication device |
WO2016175835A1 (en) * | 2015-04-30 | 2016-11-03 | Nokia Solutions And Networks Oy | Multi-security levels/traffic management across multiple network function instantiations |
CN107851113A (en) | 2015-05-08 | 2018-03-27 | Gn 股份有限公司 | Be configured as based on derived from performance sensor unit user perform attribute and realize the framework of automatic classification and/or search to media data, apparatus and method |
US10334479B2 (en) | 2015-05-11 | 2019-06-25 | Industrial Technology Research Institute | Traffic steering method and heterogeneous radio access network system applying the same |
US10084728B2 (en) * | 2015-05-11 | 2018-09-25 | Futurewei Technologies, Inc. | Localized traffic flow management in a wireless network |
US9948703B2 (en) | 2015-05-14 | 2018-04-17 | Twilio, Inc. | System and method for signaling through data storage |
US10419891B2 (en) | 2015-05-14 | 2019-09-17 | Twilio, Inc. | System and method for communicating through multiple endpoints |
US9736019B2 (en) | 2015-05-14 | 2017-08-15 | Eero Inc. | Methods for dynamic router configuration in a mesh network |
CN107847789A (en) * | 2015-05-27 | 2018-03-27 | Gn 股份有限公司 | It is configured as realizing the framework of the gameization including the gameization specific to position, apparatus and method via the monitoring of sensor-based technical ability to physical performance |
CN107615707A (en) * | 2015-05-29 | 2018-01-19 | 诺基亚技术有限公司 | The support of flexible radio protocol in 5G radio access networks |
US9729348B2 (en) | 2015-06-04 | 2017-08-08 | Cisco Technology, Inc. | Tunnel-in-tunnel source address correction |
CN104836707A (en) * | 2015-06-04 | 2015-08-12 | 郑州悉知信息技术有限公司 | User on-line status detection method and system, server and client |
US10536357B2 (en) | 2015-06-05 | 2020-01-14 | Cisco Technology, Inc. | Late data detection in data center |
US11373168B2 (en) * | 2015-06-05 | 2022-06-28 | Apple Inc. | Value added services polling |
US10142353B2 (en) | 2015-06-05 | 2018-11-27 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US9361011B1 (en) | 2015-06-14 | 2016-06-07 | Google Inc. | Methods and systems for presenting multiple live video feeds in a user interface |
CN104936225B (en) * | 2015-06-18 | 2019-02-26 | 哈尔滨工程大学 | A kind of message distribution optimal control method towards hybrid mobile community network |
US9628442B2 (en) * | 2015-06-22 | 2017-04-18 | Cisco Technology, Inc. | DNS snooping to create IP address-based trust database used to select deep packet inspection and storage of IP packets |
US9763089B2 (en) * | 2015-06-23 | 2017-09-12 | International Business Machines Corporation | Protecting sensitive data in a security area |
JP2018528641A (en) * | 2015-06-29 | 2018-09-27 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | Communication policy control in machine-to-machine communication system |
US9832797B2 (en) | 2015-06-29 | 2017-11-28 | At&T Intellectual Property I, L.P. | Mobility network function consolidation |
US10333784B2 (en) * | 2015-06-30 | 2019-06-25 | International Business Machines Corporation | Cloud system order and configuration using customized templates |
CN104994350B (en) * | 2015-07-07 | 2019-01-04 | 小米科技有限责任公司 | Information query method and device |
US9801059B2 (en) | 2015-07-09 | 2017-10-24 | Google Inc. | Security for wireless broadcasts |
GB201512043D0 (en) * | 2015-07-09 | 2015-08-19 | Microsoft Technology Licensing Llc | Client confirmation method and system |
US10419388B2 (en) * | 2015-07-14 | 2019-09-17 | Unisys Corporation | Method and system for dark matter scanning |
US20170019416A1 (en) * | 2015-07-14 | 2017-01-19 | Unisys Corporation | Method and system for dark matter scanning |
CN105120073A (en) * | 2015-07-20 | 2015-12-02 | 合肥讯飞淘云科技有限公司 | Method and system for setting communication information of intelligent terminal |
US9980115B2 (en) * | 2015-07-21 | 2018-05-22 | Tracfone Wireless, Inc. | System, process, and device for multiple network usage tracking |
US9774579B2 (en) | 2015-07-27 | 2017-09-26 | Duo Security, Inc. | Method for key rotation |
US10257782B2 (en) | 2015-07-30 | 2019-04-09 | Google Llc | Power management by powering off unnecessary radios automatically |
US9407585B1 (en) * | 2015-08-07 | 2016-08-02 | Machine Zone, Inc. | Scalable, real-time messaging system |
US9900377B2 (en) * | 2015-08-07 | 2018-02-20 | International Business Machines Corporation | Dynamic healthchecking load balancing gateway |
CN106455119B (en) | 2015-08-10 | 2022-02-25 | 北京三星通信技术研究有限公司 | WLAN aggregation control method and equipment |
CN108432176B (en) * | 2015-08-11 | 2022-02-11 | J·斯托曼 | System and method for ensuring asset and supply chain integrity |
US9832716B2 (en) | 2015-08-12 | 2017-11-28 | Google Llc | Switching between networks based on quality of available networks |
US10361936B2 (en) * | 2015-08-19 | 2019-07-23 | Google Llc | Filtering content based on user mobile network and data-plan |
US10447757B2 (en) | 2015-08-20 | 2019-10-15 | International Business Machines Corporation | Self-service server change management |
US9807198B2 (en) | 2015-08-20 | 2017-10-31 | Google Inc. | Methods and systems of identifying a device using strong component conflict detection |
TWI707286B (en) * | 2015-08-21 | 2020-10-11 | 新加坡商萬事達卡亞洲/太平洋私人有限公司 | Method and system for modifying transaction credentials, server and non-transitory computer readable medium |
KR20170025085A (en) * | 2015-08-27 | 2017-03-08 | 삼성전자주식회사 | Mobile Device for Communication with External Device and Server and Method for Updating Software thereof |
CN105263100B (en) * | 2015-08-31 | 2018-12-14 | 北京邮电大学 | content information transmission method and device |
WO2017045123A1 (en) | 2015-09-15 | 2017-03-23 | Telefonaktiebolaget Lm Ericsson (Publ) | A method for secure wifi calling connectivity over managed public wlan access |
WO2017049317A1 (en) | 2015-09-18 | 2017-03-23 | Able Device, Inc. | Secure data link for subscriber identification module (sim)-based processor |
WO2017053707A1 (en) | 2015-09-23 | 2017-03-30 | Sensoriant, Inc. | Method and system for using device states and user preferences to create user-friendly environments |
US9641553B2 (en) | 2015-09-25 | 2017-05-02 | Intel Corporation | Methods and apparatus to facilitate end-user defined policy management |
US9609613B1 (en) * | 2015-09-25 | 2017-03-28 | At&T Intellectual Property I, L.P. | Method and apparatus for managing communication services using multiple subscription agreements |
US9866592B2 (en) * | 2015-09-28 | 2018-01-09 | BlueTalon, Inc. | Policy enforcement system |
US9866530B2 (en) * | 2015-10-05 | 2018-01-09 | Zyxel Communications, Inc. | Method and apparatus for provision of secure connection |
US10129604B2 (en) * | 2015-10-26 | 2018-11-13 | Gvbb Holdings S.A.R.L. | Analytic system for automatically combining advertising and content in media broadcasts |
US9686415B2 (en) * | 2015-11-06 | 2017-06-20 | At&T Intellectual Property I, L.P. | Systems and methods of split billing |
US10542315B2 (en) | 2015-11-11 | 2020-01-21 | At&T Intellectual Property I, L.P. | Method and apparatus for content adaptation based on audience monitoring |
US10282719B1 (en) * | 2015-11-12 | 2019-05-07 | Sprint Communications Company L.P. | Secure and trusted device-based billing and charging process using privilege for network proxy authentication and audit |
US9826333B2 (en) * | 2015-11-13 | 2017-11-21 | Simapay Inc. | Dealer cellular phone activation portal with real-time commission management |
CN106714233B (en) * | 2015-11-13 | 2020-08-25 | 华为技术有限公司 | Communication system, networking method and controller of application-driven network |
US10592992B1 (en) * | 2015-11-16 | 2020-03-17 | Amdocs Development Limited | System, method, and computer program for calculating network value information |
US9817992B1 (en) | 2015-11-20 | 2017-11-14 | Sprint Communications Company Lp. | System and method for secure USIM wireless network access |
US11102103B2 (en) * | 2015-11-23 | 2021-08-24 | Bank Of America Corporation | Network stabilizing tool |
DE102015223078A1 (en) * | 2015-11-23 | 2017-05-24 | Siemens Aktiengesellschaft | Apparatus and method for adjusting authorization information of a terminal |
CN106803821B (en) * | 2015-11-26 | 2019-12-06 | 中国电信股份有限公司 | Method and system for identifying terminal user identity in WIFI scene |
CN105898796A (en) * | 2015-11-27 | 2016-08-24 | 乐视致新电子科技(天津)有限公司 | 4G device transmission rate improving method and system |
JP2017102777A (en) * | 2015-12-03 | 2017-06-08 | 富士通株式会社 | Load distribution processing server, load distribution processing method, and system |
US9929970B1 (en) | 2015-12-03 | 2018-03-27 | Innovium, Inc. | Efficient resource tracking |
US9876810B2 (en) * | 2015-12-04 | 2018-01-23 | Raytheon Company | Systems and methods for malware lab isolation |
US10470113B2 (en) | 2015-12-09 | 2019-11-05 | Lenovo (Singapore) Pte. Ltd. | Usage of network based on quality of network at a particular location |
US20170171736A1 (en) * | 2015-12-09 | 2017-06-15 | Lenovo (Singapore) Pte. Ltd. | Dynamic pricing for use of network |
US9871825B2 (en) | 2015-12-10 | 2018-01-16 | BlueTalon, Inc. | Policy enforcement for compute nodes |
KR20190038748A (en) | 2015-12-10 | 2019-04-09 | 지엔 아이피 피티와이 엘티디 | Structure and method for enabling real-time adaptive provision of functional training data based on user performance monitoring through performance monitoring hardware |
US10482437B2 (en) * | 2015-12-16 | 2019-11-19 | Mastercard International Incorporated | Systems and methods for identifying suspect illicit merchants |
US9942201B1 (en) * | 2015-12-16 | 2018-04-10 | vIPtela Inc. | Context specific keys |
US10218589B1 (en) | 2015-12-17 | 2019-02-26 | Innovium, Inc. | Efficient resource status reporting apparatuses |
US9980303B2 (en) | 2015-12-18 | 2018-05-22 | Cisco Technology, Inc. | Establishing a private network using multi-uplink capable network devices |
US9910713B2 (en) * | 2015-12-21 | 2018-03-06 | Amazon Technologies, Inc. | Code execution request routing |
JP6606421B2 (en) | 2015-12-22 | 2019-11-13 | 東芝テック株式会社 | Checkout system and registration device |
US10198595B2 (en) | 2015-12-22 | 2019-02-05 | Walmart Apollo, Llc | Data breach detection system |
US10178611B2 (en) * | 2015-12-23 | 2019-01-08 | Samsung Electronics Co., Ltd. | Scheme for performing a data session via a Wi-Fi access in a wireless communication system |
US9843474B2 (en) * | 2015-12-23 | 2017-12-12 | Intel Corporation | Telemetry adaptation |
US10817593B1 (en) * | 2015-12-29 | 2020-10-27 | Wells Fargo Bank, N.A. | User information gathering and distribution system |
JP6718966B2 (en) * | 2015-12-30 | 2020-07-08 | ドイッチェ テレコム アーゲー | Methods for establishing a roaming connection |
US20190089595A1 (en) * | 2017-09-18 | 2019-03-21 | Cyber 2.0 (2015) LTD | Automatic security configuration |
US10089124B2 (en) * | 2015-12-31 | 2018-10-02 | International Business Machines Corporation | Security application for a guest operating system in a virtual computing environment |
EP3190746B1 (en) | 2016-01-08 | 2021-09-15 | Alcatel Lucent | Dynamic provision of application related sponsored data connectivity |
CN105704066B (en) * | 2016-01-12 | 2019-06-25 | 北京奇虎科技有限公司 | Networking control method and device, system, security gateway, mobile terminal |
US10362000B2 (en) * | 2016-01-15 | 2019-07-23 | Electric Power Research Institute, Inc. | Virtual Wi-Fi network and secure tunnel provisioning for reliable, persistent connection of energy devices at the customer's premises |
CN106982443B (en) * | 2016-01-18 | 2020-10-30 | 中国移动通信集团河北有限公司 | Service distribution method and device |
US9942757B2 (en) * | 2016-01-19 | 2018-04-10 | Google Inc. | Identifying a mobile computing device |
US10856135B2 (en) * | 2016-01-25 | 2020-12-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for network access |
US10341923B2 (en) * | 2016-01-29 | 2019-07-02 | Google Llc | Techniques for minimizing user disruption during network connection switching |
US11290425B2 (en) * | 2016-02-01 | 2022-03-29 | Airwatch Llc | Configuring network security based on device management characteristics |
US10659349B2 (en) | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US10432429B1 (en) | 2016-02-16 | 2019-10-01 | Innovium, Inc. | Efficient traffic management |
EP3398091B1 (en) * | 2016-02-19 | 2022-05-11 | Huawei Technologies Co., Ltd. | System and method for unified access control on federated database |
KR102483836B1 (en) * | 2016-02-19 | 2023-01-03 | 삼성전자주식회사 | Electronic apparatus and operating method thereof |
CN105764095B (en) * | 2016-02-22 | 2020-08-21 | 世纪蜗牛通信科技有限公司 | Application identification and control system and method based on virtual private network |
MX2018009355A (en) | 2016-02-23 | 2018-12-19 | Nchain Holdings Ltd | Secure multiparty loss resistant storage and transfer of cryptographic keys for blockchain based systems in conjunction with a wallet management system. |
KR101999188B1 (en) | 2016-02-23 | 2019-07-11 | 엔체인 홀딩스 리미티드 | Secure personal devices using elliptic curve cryptography for secret sharing |
KR20180115768A (en) | 2016-02-23 | 2018-10-23 | 엔체인 홀딩스 리미티드 | Encryption method and system for secure extraction of data from a block chain |
CN108885745B (en) | 2016-02-23 | 2023-06-30 | 区块链控股有限公司 | Blockchain-based exchange with tokenization |
EP3420517B1 (en) | 2016-02-23 | 2022-07-06 | nChain Holdings Limited | A method and system for the secure transfer of entities on a blockchain |
PL3257191T3 (en) | 2016-02-23 | 2019-01-31 | Nchain Holdings Ltd | Registry and automated management method for blockchain-enforced smart contracts |
KR20180114939A (en) | 2016-02-23 | 2018-10-19 | 엔체인 홀딩스 리미티드 | Systems and methods for controlling asset-related activities through block chaining |
PL3268914T3 (en) | 2016-02-23 | 2018-12-31 | nChain Holdings Limited | Determining a common secret for the secure exchange of information and hierarchical, deterministic cryptographic keys |
EP3420674B1 (en) | 2016-02-23 | 2021-03-24 | Nchain Holdings Limited | Blockchain-implemented method for control and distribution of digital content |
EP3764589A1 (en) * | 2016-02-23 | 2021-01-13 | Nchain Holdings Limited | Agent-based turing complete transactions integrating feedback within a blockchain system |
CN109074579B (en) | 2016-02-23 | 2022-10-11 | 区块链控股有限公司 | Method and system for protecting computer software using distributed hash table and blockchain |
CA3014726A1 (en) | 2016-02-23 | 2017-08-31 | nChain Holdings Limited | Tokenisation method and system for implementing exchanges on a blockchain |
WO2017145004A1 (en) | 2016-02-23 | 2017-08-31 | nChain Holdings Limited | Universal tokenisation system for blockchain-based cryptocurrencies |
US10091243B2 (en) * | 2016-02-24 | 2018-10-02 | Qualcomm Incorporated | Apparatus and method for securely connecting to a remote server |
MX2018010156A (en) * | 2016-02-25 | 2019-01-31 | Acs Us Inc | Platform for computing at the mobile edge. |
US10180834B2 (en) * | 2016-02-29 | 2019-01-15 | Airwatch Llc | Provisioning of applications deployed on client devices |
US11310131B2 (en) * | 2016-02-29 | 2022-04-19 | Level 3 Communications, Llc | Data network analysis system and method for a communication network |
US11140167B1 (en) | 2016-03-01 | 2021-10-05 | Exabeam, Inc. | System, method, and computer program for automatically classifying user accounts in a computer network using keys from an identity management system |
US9935840B2 (en) * | 2016-03-04 | 2018-04-03 | Digi International Inc. | Systems and methods for self-configuring wireless device initializations |
CN107154863A (en) * | 2016-03-04 | 2017-09-12 | 中移(苏州)软件技术有限公司 | A kind of cloud host address monitoring method, cloud platform and proxy server |
US20170264484A1 (en) * | 2016-03-09 | 2017-09-14 | Industrial Technology Research Institute | Server and base station of a radio network, method of accessing a radio network, and non-transitory computer-readable storage medium thereof |
US11425169B2 (en) | 2016-03-11 | 2022-08-23 | Netskope, Inc. | Small-footprint endpoint data loss prevention (DLP) |
US10506048B2 (en) | 2016-03-11 | 2019-12-10 | Microsoft Technology Licensing, Llc | Automatic report rate optimization for sensor applications |
US9641880B1 (en) * | 2016-03-15 | 2017-05-02 | Adobe Systems Incorporated | Automatically identifying reduced availability of multi-channel media distributors for authentication or authorization |
US9848223B2 (en) | 2016-03-15 | 2017-12-19 | Adobe Systems Incorporated | Automatically determining restored availability of multi-channel media distributors for authentication or authorization |
US9980142B2 (en) | 2016-03-22 | 2018-05-22 | Google Llc | Methods and apparatus for SIM-based authentication of non-SIM devices |
US9980095B2 (en) | 2016-03-22 | 2018-05-22 | Google Llc | Method and apparatus for providing country detection on cellular devices using cell tower information |
US10187306B2 (en) | 2016-03-24 | 2019-01-22 | Cisco Technology, Inc. | System and method for improved service chaining |
US10594731B2 (en) * | 2016-03-24 | 2020-03-17 | Snowflake Inc. | Systems, methods, and devices for securely managing network connections |
US9998912B2 (en) | 2016-03-25 | 2018-06-12 | International Business Machines Corporation | Policy-driven aggregated network data use in mobile devices |
US20170279681A1 (en) * | 2016-03-28 | 2017-09-28 | Facebook, Inc. | Methods and Systems for Distributed Testing of Network Configurations for Zero-Rating |
US10575160B2 (en) | 2016-03-30 | 2020-02-25 | Vitrotv Hk Ltd | Systems and methods for operating display devices with dual pathway connections |
US11533382B2 (en) | 2016-03-31 | 2022-12-20 | Juniper Networks, Inc. | Providing user subscription nomadicity in wireline broadband networks |
US10225783B2 (en) | 2016-04-01 | 2019-03-05 | Google Llc | Method and apparatus for providing peer based network switching |
US20170289120A1 (en) * | 2016-04-04 | 2017-10-05 | Mastercard International Incorporated | Systems and methods for authenticating user for secure data access using multi-party authentication system |
US10256985B2 (en) | 2016-04-22 | 2019-04-09 | Tata Communication (America) Inc. | System and method for managing and selecting from multiple mobile data top-up product options |
US10931793B2 (en) | 2016-04-26 | 2021-02-23 | Cisco Technology, Inc. | System and method for automated rendering of service chaining |
CN108886723B (en) * | 2016-04-27 | 2021-06-25 | 英特尔公司 | Universal multiple access protocol for next generation multiple access networks |
CN107329927A (en) * | 2016-04-28 | 2017-11-07 | 富泰华工业(深圳)有限公司 | A kind of data-sharing systems and method |
EP3449596B1 (en) | 2016-04-28 | 2019-07-31 | Telefonaktiebolaget LM Ericsson (publ) | Technique for handling service level related performance data for roaming user terminals |
US9794795B1 (en) * | 2016-04-29 | 2017-10-17 | Corning Optical Communications Wireless Ltd | Implementing a live distributed antenna system (DAS) configuration from a virtual DAS design using an original equipment manufacturer (OEM) specific software system in a DAS |
US20170325134A1 (en) * | 2016-05-04 | 2017-11-09 | Huawei Technologies Co., Ltd. | Method and apparatus for connecting a mobile device to a pay-for-usage communication network |
US20170331690A1 (en) | 2016-05-12 | 2017-11-16 | Iboss, Inc. | Applying network policies to devices based on their current access network |
US10135837B2 (en) | 2016-05-17 | 2018-11-20 | Amazon Technologies, Inc. | Versatile autoscaling for containers |
US10470031B2 (en) | 2016-05-20 | 2019-11-05 | Ibasis, Inc. | Voice over IMS roaming gateway |
US10063713B2 (en) | 2016-05-23 | 2018-08-28 | Twilio Inc. | System and method for programmatic device connectivity |
US10686902B2 (en) | 2016-05-23 | 2020-06-16 | Twilio Inc. | System and method for a multi-channel notification service |
US10313316B2 (en) * | 2016-05-26 | 2019-06-04 | Pepsico, Inc. | Secure gateways for connected dispensing machines |
US10506237B1 (en) | 2016-05-27 | 2019-12-10 | Google Llc | Methods and devices for dynamic adaptation of encoding bitrate for video streaming |
WO2017207017A1 (en) * | 2016-05-30 | 2017-12-07 | Telecom Italia S.P.A. | Protection of privacy in wireless telecommunication networks |
US10700894B2 (en) | 2016-06-01 | 2020-06-30 | At&T Intellectual Property I, L.P. | Network caching of outbound content from endpoint device to prevent unauthorized extraction |
US20220284523A1 (en) * | 2016-06-03 | 2022-09-08 | State Farm Mutual Automobile Insurance Company | Control system for collecting sensor and device pairing data |
CN106101228A (en) * | 2016-06-13 | 2016-11-09 | 镇江市新创计算机系统集成有限公司 | A kind of control method of debt management |
CN116751293A (en) | 2016-06-14 | 2023-09-15 | 瑞泽恩制药公司 | anti-C5 antibodies and uses thereof |
EP3474597B1 (en) * | 2016-06-20 | 2021-05-05 | Nec Corporation | Communication network apparatus, communication network system, and method of communication network apparatus |
GB2551543A (en) * | 2016-06-21 | 2017-12-27 | Eckoh Uk Ltd | Methods of authenticating a user for data exchange |
US10366582B2 (en) | 2016-06-21 | 2019-07-30 | Bank Of America Corporation | Devices and systems for detecting unauthorized communication of data from a magnetic stripe device or embedded smart chip device |
US10659278B2 (en) | 2016-06-24 | 2020-05-19 | T-Mobile Usa, Inc. | Video interconnect system |
US11206223B2 (en) * | 2016-06-30 | 2021-12-21 | Microsoft Technology Licensing, Llc | Signal upload optimization |
US10873891B2 (en) | 2016-07-06 | 2020-12-22 | Oceus Networks, Llc | Secure network rollover |
US10419550B2 (en) | 2016-07-06 | 2019-09-17 | Cisco Technology, Inc. | Automatic service function validation in a virtual network environment |
US9924427B2 (en) | 2016-07-07 | 2018-03-20 | Oceus Networks Inc. | Network backhaul access |
US9686238B1 (en) | 2016-07-07 | 2017-06-20 | Oceus Networks Inc. | Secure network enrollment |
US10277701B2 (en) * | 2016-07-08 | 2019-04-30 | Facebook, Inc. | Methods and Systems for Rewriting Scripts to Direct Requests |
US10380429B2 (en) | 2016-07-11 | 2019-08-13 | Google Llc | Methods and systems for person detection in a video feed |
US10320664B2 (en) | 2016-07-21 | 2019-06-11 | Cisco Technology, Inc. | Cloud overlay for operations administration and management |
US10218616B2 (en) | 2016-07-21 | 2019-02-26 | Cisco Technology, Inc. | Link selection for communication with a service function cluster |
US9769668B1 (en) * | 2016-08-01 | 2017-09-19 | At&T Intellectual Property I, L.P. | System and method for common authentication across subscribed services |
US10416958B2 (en) * | 2016-08-01 | 2019-09-17 | Bank Of America Corporation | Hierarchical clustering |
US10250706B2 (en) * | 2016-08-01 | 2019-04-02 | Bank Of America Corporation | Hierarchical Clustering |
WO2018024205A1 (en) * | 2016-08-02 | 2018-02-08 | Chou Chie Ming | Method for signaling ran profile index and radio communication equipment using the same |
US10225270B2 (en) | 2016-08-02 | 2019-03-05 | Cisco Technology, Inc. | Steering of cloned traffic in a service function chain |
US10637853B2 (en) | 2016-08-05 | 2020-04-28 | Nok Nok Labs, Inc. | Authentication techniques including speech and/or lip movement analysis |
US10250624B2 (en) * | 2016-08-05 | 2019-04-02 | Oak Tree Logic, Llc | Method and device for robust detection, analytics, and filtering of data/information exchange with connected user devices in a gateway-connected user-space |
US10769635B2 (en) | 2016-08-05 | 2020-09-08 | Nok Nok Labs, Inc. | Authentication techniques including speech and/or lip movement analysis |
CN106301808B (en) * | 2016-08-15 | 2019-06-21 | 中国联合网络通信集团有限公司 | Policy control method and its system |
US10892963B2 (en) | 2016-08-15 | 2021-01-12 | Incognito Software Systems, Inc. | System and method for determining bandwith usage from a plurality of subscribers in a cable network |
WO2018035251A1 (en) | 2016-08-17 | 2018-02-22 | Performance And Privacy Ireland Ltd. | Deriving mobile application usage from network traffic |
EP3501192B1 (en) * | 2016-08-18 | 2021-03-31 | Telefonaktiebolaget LM Ericsson (publ) | Method and device for enhancing voip security by selectively scrutinizing caller's geographical location |
KR101697274B1 (en) * | 2016-08-19 | 2017-02-01 | 코나아이 (주) | Hardware secure module, hardware secure system, and method for operating hardware secure module |
US10218593B2 (en) | 2016-08-23 | 2019-02-26 | Cisco Technology, Inc. | Identifying sources of packet drops in a service function chain environment |
CN106295450A (en) * | 2016-08-26 | 2017-01-04 | 易联(北京)物联网科技有限公司 | A kind of based on the method that NFC label is locked |
USD794659S1 (en) * | 2016-08-26 | 2017-08-15 | Nasdaq, Inc. | Display screen or portion thereof with animated graphical user interface |
US10075373B2 (en) | 2016-08-26 | 2018-09-11 | Viasat, Inc. | Methods and apparatus for providing traffic forwarder via dynamic overlay network |
EP3291500B1 (en) * | 2016-08-30 | 2020-05-13 | Siemens Aktiengesellschaft | Data processing system |
US10310467B2 (en) * | 2016-08-30 | 2019-06-04 | Honeywell International Inc. | Cloud-based control platform with connectivity to remote embedded devices in distributed control system |
US9681471B1 (en) | 2016-08-31 | 2017-06-13 | Bank Of America Corporation | Pairing of devices for activation/deactivation of a paired device |
US10958547B2 (en) * | 2016-09-09 | 2021-03-23 | Hewlett Packard Enterprise Development Lp | Verify a network function by inquiring a model using a query language |
US10979890B2 (en) * | 2016-09-09 | 2021-04-13 | Ibasis, Inc. | Policy control framework |
US10523524B2 (en) | 2016-09-13 | 2019-12-31 | Gogo Llc | Usage-based bandwidth optimization |
US10491531B2 (en) | 2016-09-13 | 2019-11-26 | Gogo Llc | User directed bandwidth optimization |
US10511680B2 (en) | 2016-09-13 | 2019-12-17 | Gogo Llc | Network profile configuration assistance tool |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
US9913132B1 (en) | 2016-09-14 | 2018-03-06 | Sprint Communications Company L.P. | System and method of mobile phone customization based on universal manifest |
US10021240B1 (en) | 2016-09-16 | 2018-07-10 | Sprint Communications Company L.P. | System and method of mobile phone customization based on universal manifest with feature override |
US11625769B2 (en) * | 2016-09-21 | 2023-04-11 | Coinbase, Inc. | Multi-factor integrated compliance determination and enforcement platform |
US20180084460A1 (en) * | 2016-09-22 | 2018-03-22 | Qualcomm Incorporated | Sharing system resources between mobile devices |
CN109923883B (en) | 2016-09-27 | 2022-05-17 | A9.Com公司 | Method for sharing network configuration |
US10250587B2 (en) * | 2016-09-30 | 2019-04-02 | Microsoft Technology Licensing, Llc | Detecting malicious usage of certificates |
CN107888475B (en) * | 2016-09-30 | 2020-09-08 | 中国石油天然气股份有限公司 | Mail decryption method and server |
US20180098272A1 (en) * | 2016-10-05 | 2018-04-05 | Microsoft Technology Licensing, Llc | Cross-Transport Network Connection State Detection and Management Engine |
US10708730B2 (en) * | 2016-10-09 | 2020-07-07 | Nokia Solutions And Networks Oy | SDCI pull and push mode optimization |
DE102016219848A1 (en) * | 2016-10-12 | 2018-04-12 | Siemens Aktiengesellschaft | Method and apparatus for providing secure communication within a real-time communication network |
FR3057728B1 (en) | 2016-10-16 | 2018-11-02 | Taig Khris | METHOD FOR VERIFYING THE VALIDITY OF A TELEPHONE LINE OF A USER OF A SERVICE OR SOFTWARE APPLICATION |
GB201617620D0 (en) * | 2016-10-18 | 2016-11-30 | Cybernetica As | Composite digital signatures |
US10412022B1 (en) | 2016-10-19 | 2019-09-10 | Amazon Technologies, Inc. | On-premises scaling using a versatile scaling service and an application programming interface management service |
US10614427B2 (en) * | 2016-10-21 | 2020-04-07 | Johnson Controls Technology Company | Systems and methods for monetizing building management system software deployment |
KR102449475B1 (en) * | 2016-10-21 | 2022-09-30 | 삼성전자 주식회사 | Mehotd and apparatus for connecting network to terminal based on applicable network information in mobile communication system |
WO2018077376A1 (en) | 2016-10-24 | 2018-05-03 | NEC Laboratories Europe GmbH | Method for managing data traffic within a network |
US20210306348A1 (en) * | 2016-10-25 | 2021-09-30 | Michael Ratiner | System and method for securing electronic devices |
US10462734B2 (en) | 2016-10-31 | 2019-10-29 | Google Llc | Method, apparatus and system with carrier network switching control |
US10313359B2 (en) * | 2016-11-01 | 2019-06-04 | Microsoft Technology Licensing, Llc | Protocols for accessing hosts |
US10218562B2 (en) | 2016-11-09 | 2019-02-26 | Bank Of America Corporation | Parsing and optimizing runtime infrastructure alerts |
US10574559B2 (en) | 2016-11-10 | 2020-02-25 | Bank Of America Corporation | System for defining and implementing performance monitoring requirements for applications and hosted computing environment infrastructure |
EP3322209A1 (en) * | 2016-11-11 | 2018-05-16 | Telia Company AB | A method and a mobile user terminal for service quality prediction |
US10565177B2 (en) | 2016-11-14 | 2020-02-18 | At&T Intellectual Property I, L.P. | Software defined entities for digital service transactions |
US10409642B1 (en) | 2016-11-22 | 2019-09-10 | Amazon Technologies, Inc. | Customer resource monitoring for versatile scaling service scaling policy recommendations |
US10218694B2 (en) | 2016-11-22 | 2019-02-26 | Bank Of America Corporation | Securely orchestrating events initiated at remote servers using a certificate server |
CN106603526B (en) * | 2016-12-07 | 2020-03-24 | Oppo广东移动通信有限公司 | WiFi/hotspot starting method and device |
CN108616485B (en) * | 2016-12-09 | 2020-11-10 | 中兴通讯股份有限公司 | Communication method and device based on fusion device |
US10225741B2 (en) | 2016-12-12 | 2019-03-05 | International Business Machines Corporation | Security enabled predictive mobile data caching |
US20180165695A1 (en) * | 2016-12-12 | 2018-06-14 | Wal-Mart Stores, Inc. | Determining density of customers based on wi-fi load |
CN110063064B (en) * | 2016-12-13 | 2022-01-04 | 德国电信股份有限公司 | Method for providing enhanced communication capabilities to user equipment |
US10402273B2 (en) | 2016-12-14 | 2019-09-03 | Microsoft Technology Licensing, Llc | IoT device update failure recovery |
US10715526B2 (en) | 2016-12-14 | 2020-07-14 | Microsoft Technology Licensing, Llc | Multiple cores with hierarchy of trust |
US10416991B2 (en) * | 2016-12-14 | 2019-09-17 | Microsoft Technology Licensing, Llc | Secure IoT device update |
US10637957B2 (en) * | 2016-12-15 | 2020-04-28 | Vmware, Inc. | Dynamic runtime interface for device management |
US11616812B2 (en) | 2016-12-19 | 2023-03-28 | Attivo Networks Inc. | Deceiving attackers accessing active directory data |
US11695800B2 (en) | 2016-12-19 | 2023-07-04 | SentinelOne, Inc. | Deceiving attackers accessing network data |
US10638369B2 (en) * | 2016-12-20 | 2020-04-28 | Qualcomm Incorporated | Quality of service configuration based on channel quality |
JP6957878B2 (en) * | 2016-12-28 | 2021-11-02 | 日本電気株式会社 | Notification device, notification method, and program |
US10657225B2 (en) | 2016-12-29 | 2020-05-19 | Red Hat, Inc. | Providing blockchain-based subscription-as-a-service management |
EP3563598B1 (en) | 2016-12-30 | 2021-11-03 | British Telecommunications Public Limited Company | Automatic pairing of devices to wireless networks |
CN107087266B (en) * | 2016-12-30 | 2020-01-17 | 中国移动通信集团北京有限公司 | Method and device for making industry customer short message office data |
US10952263B2 (en) * | 2016-12-30 | 2021-03-16 | British Telecommunications Public Limited Company | Automatic device pairing |
US11190942B2 (en) | 2016-12-30 | 2021-11-30 | British Telecommunications Public Limited Company | Automatic pairing of devices to wireless networks |
CN106713648B (en) * | 2016-12-30 | 2019-07-26 | Oppo广东移动通信有限公司 | A kind of communication means and mobile terminal |
US10091195B2 (en) | 2016-12-31 | 2018-10-02 | Nok Nok Labs, Inc. | System and method for bootstrapping a user binding |
US10237070B2 (en) | 2016-12-31 | 2019-03-19 | Nok Nok Labs, Inc. | System and method for sharing keys across authenticators |
WO2018128605A1 (en) * | 2017-01-04 | 2018-07-12 | Sprague Don E | Enhanced online computer access cyber security system |
US11500762B2 (en) * | 2017-01-11 | 2022-11-15 | Smartlytics Llc | System and method for automated intelligent mobile application testing |
US11275834B1 (en) * | 2017-01-12 | 2022-03-15 | Richard Offer | System for analyzing backups for threats and irregularities |
US10552601B2 (en) * | 2017-01-18 | 2020-02-04 | Red Hat, Inc. | Deferred subscription activation using blockchain |
USD844658S1 (en) | 2017-01-20 | 2019-04-02 | Verisign, Inc. | Display screen or portion thereof with a sequential graphical user interface |
US10904211B2 (en) | 2017-01-21 | 2021-01-26 | Verisign, Inc. | Systems, devices, and methods for generating a domain name using a user interface |
US20180213048A1 (en) * | 2017-01-23 | 2018-07-26 | Microsoft Technology Licensing, Llc | Secured targeting of cross-application push notifications |
EP3567934B1 (en) * | 2017-02-07 | 2022-11-02 | Huawei Technologies Co., Ltd. | Data transmission method, terminal, and access network element |
CN108401259A (en) * | 2017-02-07 | 2018-08-14 | 蔡伟英 | A kind of mobile terminal multi-mode formula internet access method and system |
US10887325B1 (en) * | 2017-02-13 | 2021-01-05 | Exabeam, Inc. | Behavior analytics system for determining the cybersecurity risk associated with first-time, user-to-entity access alerts |
US20180247548A1 (en) * | 2017-02-27 | 2018-08-30 | Honeywell International Inc. | System and method to decipher and display advisory information |
CN108574591B (en) * | 2017-03-10 | 2020-04-17 | 中国移动通信有限公司研究院 | Configuration method, network management equipment, terminal equipment and network equipment |
US10594664B2 (en) | 2017-03-13 | 2020-03-17 | At&T Intellectual Property I, L.P. | Extracting data from encrypted packet flows |
US20180278607A1 (en) * | 2017-03-22 | 2018-09-27 | Amazon Technologies, Inc. | Device Credentials Management |
US10225187B2 (en) | 2017-03-22 | 2019-03-05 | Cisco Technology, Inc. | System and method for providing a bit indexed service chain |
US10225762B2 (en) | 2017-03-28 | 2019-03-05 | Oracle International Corporation | Methods, systems, and computer readable media for message flood suppression during access node-gateway (AN-GW) unavailability and after AN-GW restoration |
US10820190B2 (en) | 2017-03-30 | 2020-10-27 | Ibasis, Inc. | eSIM profile switching without SMS |
US20180287920A1 (en) * | 2017-03-30 | 2018-10-04 | Ca, Inc. | Intercepting application traffic monitor and analyzer |
US10172078B2 (en) | 2017-03-31 | 2019-01-01 | Oceus Networks Inc. | Targeted user equipment-base station communication link |
US10225355B2 (en) * | 2017-04-04 | 2019-03-05 | Facebook, Inc. | Methods and systems for abuse detection of zero-rated data |
US10884807B2 (en) | 2017-04-12 | 2021-01-05 | Cisco Technology, Inc. | Serverless computing and task scheduling |
US10257033B2 (en) | 2017-04-12 | 2019-04-09 | Cisco Technology, Inc. | Virtualized network functions and service chaining in serverless computing infrastructure |
EP3610384A4 (en) * | 2017-04-13 | 2020-11-25 | Nokia Technologies Oy | Apparatus, method and computer program product for trust management |
US10992729B2 (en) | 2017-04-18 | 2021-04-27 | Microsoft Technology Licensing, Llc | Endpoint configuration for a communication session |
US10333855B2 (en) | 2017-04-19 | 2019-06-25 | Cisco Technology, Inc. | Latency reduction in service function paths |
US10623264B2 (en) | 2017-04-20 | 2020-04-14 | Cisco Technology, Inc. | Policy assurance for service chaining |
US10560328B2 (en) | 2017-04-20 | 2020-02-11 | Cisco Technology, Inc. | Static network policy analysis for networks |
US10826788B2 (en) | 2017-04-20 | 2020-11-03 | Cisco Technology, Inc. | Assurance of quality-of-service configurations in a network |
US10171967B2 (en) * | 2017-04-26 | 2019-01-01 | Veniam, Inc. | Fast discovery, service-driven, and context-based connectivity for networks of autonomous vehicles |
US10554689B2 (en) | 2017-04-28 | 2020-02-04 | Cisco Technology, Inc. | Secure communication session resumption in a service function chain |
US10306433B1 (en) * | 2017-05-01 | 2019-05-28 | Sprint Communications Company L.P. | Mobile phone differentiated user set-up |
JP7178365B2 (en) | 2017-05-05 | 2022-11-25 | マイクロソフト テクノロジー ライセンシング,エルエルシー | Method and system for Service Capability Exposure Function (SCEF)-based Internet of Things (IOT) communication |
WO2018206999A1 (en) * | 2017-05-09 | 2018-11-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Handling of data limits in machine-to-machine communications network |
US10574680B2 (en) * | 2017-05-12 | 2020-02-25 | Teachers Insurance And Annuity Association Of America | Malware detection in distributed computer systems |
CN107148011B (en) * | 2017-05-12 | 2021-02-26 | 腾讯科技(深圳)有限公司 | Method, device and system for executing target service |
US10333822B1 (en) | 2017-05-23 | 2019-06-25 | Cisco Technology, Inc. | Techniques for implementing loose hop service function chains price information |
EP3410377A1 (en) * | 2017-05-29 | 2018-12-05 | Mastercard International Incorporated | Method for setting up a recurring payment |
US11783010B2 (en) | 2017-05-30 | 2023-10-10 | Google Llc | Systems and methods of person recognition in video streams |
US10812318B2 (en) | 2017-05-31 | 2020-10-20 | Cisco Technology, Inc. | Associating network policy objects with specific faults corresponding to fault localizations in large-scale network deployment |
US10439875B2 (en) | 2017-05-31 | 2019-10-08 | Cisco Technology, Inc. | Identification of conflict rules in a network intent formal equivalence failure |
US10623271B2 (en) | 2017-05-31 | 2020-04-14 | Cisco Technology, Inc. | Intra-priority class ordering of rules corresponding to a model of network intents |
US10581694B2 (en) | 2017-05-31 | 2020-03-03 | Cisco Technology, Inc. | Generation of counter examples for network intent formal equivalence failures |
US20180351788A1 (en) | 2017-05-31 | 2018-12-06 | Cisco Technology, Inc. | Fault localization in large-scale network policy deployment |
US10554483B2 (en) | 2017-05-31 | 2020-02-04 | Cisco Technology, Inc. | Network policy analysis for networks |
EP3632090A1 (en) | 2017-05-31 | 2020-04-08 | Affirmed Networks, Inc. | Decoupled control and data plane synchronization for ipsec geographic redundancy |
US10693738B2 (en) | 2017-05-31 | 2020-06-23 | Cisco Technology, Inc. | Generating device-level logical models for a network |
US10505816B2 (en) | 2017-05-31 | 2019-12-10 | Cisco Technology, Inc. | Semantic analysis to detect shadowing of rules in a model of network intents |
US10372939B2 (en) * | 2017-06-01 | 2019-08-06 | Dell Products L.P. | System and method to remotely provision out-of-band system |
US10616939B2 (en) | 2017-06-06 | 2020-04-07 | International Business Machines Corporation | Ad-hoc peer-to-peer communications to access various services via a cellular network |
US20180359639A1 (en) * | 2017-06-12 | 2018-12-13 | Francesco Trama | Methods and Systems for Protecting Computer Networks by Masking Ports |
CN107241742B (en) * | 2017-06-15 | 2024-02-02 | 深圳市潮流网络技术有限公司 | Network switching dynamic modification application configuration method |
US10686669B2 (en) | 2017-06-16 | 2020-06-16 | Cisco Technology, Inc. | Collecting network models and node information from a network |
US11150973B2 (en) | 2017-06-16 | 2021-10-19 | Cisco Technology, Inc. | Self diagnosing distributed appliance |
US10904101B2 (en) | 2017-06-16 | 2021-01-26 | Cisco Technology, Inc. | Shim layer for extracting and prioritizing underlying rules for modeling network intents |
CN109150751B (en) * | 2017-06-16 | 2022-05-27 | 阿里巴巴集团控股有限公司 | Network control method and device |
US10587621B2 (en) | 2017-06-16 | 2020-03-10 | Cisco Technology, Inc. | System and method for migrating to and maintaining a white-list network security model |
US10498608B2 (en) | 2017-06-16 | 2019-12-03 | Cisco Technology, Inc. | Topology explorer |
US11645131B2 (en) | 2017-06-16 | 2023-05-09 | Cisco Technology, Inc. | Distributed fault code aggregation across application centric dimensions |
US11469986B2 (en) | 2017-06-16 | 2022-10-11 | Cisco Technology, Inc. | Controlled micro fault injection on a distributed appliance |
US10574513B2 (en) | 2017-06-16 | 2020-02-25 | Cisco Technology, Inc. | Handling controller and node failure scenarios during data collection |
US10547715B2 (en) | 2017-06-16 | 2020-01-28 | Cisco Technology, Inc. | Event generation in response to network intent formal equivalence failures |
US10735275B2 (en) | 2017-06-16 | 2020-08-04 | Cisco Technology, Inc. | Releasing and retaining resources for use in a NFV environment |
US10505817B2 (en) | 2017-06-19 | 2019-12-10 | Cisco Technology, Inc. | Automatically determining an optimal amount of time for analyzing a distributed network environment |
US10812336B2 (en) | 2017-06-19 | 2020-10-20 | Cisco Technology, Inc. | Validation of bridge domain-L3out association for communication outside a network |
US10432467B2 (en) | 2017-06-19 | 2019-10-01 | Cisco Technology, Inc. | Network validation between the logical level and the hardware level of a network |
US11343150B2 (en) | 2017-06-19 | 2022-05-24 | Cisco Technology, Inc. | Validation of learned routes in a network |
US10341184B2 (en) | 2017-06-19 | 2019-07-02 | Cisco Technology, Inc. | Validation of layer 3 bridge domain subnets in in a network |
US10333787B2 (en) | 2017-06-19 | 2019-06-25 | Cisco Technology, Inc. | Validation of L3OUT configuration for communications outside a network |
US10437641B2 (en) | 2017-06-19 | 2019-10-08 | Cisco Technology, Inc. | On-demand processing pipeline interleaved with temporal processing pipeline |
US10528444B2 (en) | 2017-06-19 | 2020-01-07 | Cisco Technology, Inc. | Event generation in response to validation between logical level and hardware level |
US10567229B2 (en) | 2017-06-19 | 2020-02-18 | Cisco Technology, Inc. | Validating endpoint configurations between nodes |
US10547509B2 (en) | 2017-06-19 | 2020-01-28 | Cisco Technology, Inc. | Validation of a virtual port channel (VPC) endpoint in the network fabric |
US10348564B2 (en) | 2017-06-19 | 2019-07-09 | Cisco Technology, Inc. | Validation of routing information base-forwarding information base equivalence in a network |
US10554493B2 (en) | 2017-06-19 | 2020-02-04 | Cisco Technology, Inc. | Identifying mismatches between a logical model and node implementation |
US10411996B2 (en) | 2017-06-19 | 2019-09-10 | Cisco Technology, Inc. | Validation of routing information in a network fabric |
US10644946B2 (en) | 2017-06-19 | 2020-05-05 | Cisco Technology, Inc. | Detection of overlapping subnets in a network |
US10673702B2 (en) | 2017-06-19 | 2020-06-02 | Cisco Technology, Inc. | Validation of layer 3 using virtual routing forwarding containers in a network |
US10805160B2 (en) | 2017-06-19 | 2020-10-13 | Cisco Technology, Inc. | Endpoint bridge domain subnet validation |
US10567228B2 (en) | 2017-06-19 | 2020-02-18 | Cisco Technology, Inc. | Validation of cross logical groups in a network |
US10560355B2 (en) | 2017-06-19 | 2020-02-11 | Cisco Technology, Inc. | Static endpoint validation |
US10218572B2 (en) | 2017-06-19 | 2019-02-26 | Cisco Technology, Inc. | Multiprotocol border gateway protocol routing validation |
US10798187B2 (en) | 2017-06-19 | 2020-10-06 | Cisco Technology, Inc. | Secure service chaining |
US10536337B2 (en) | 2017-06-19 | 2020-01-14 | Cisco Technology, Inc. | Validation of layer 2 interface and VLAN in a networked environment |
US10652102B2 (en) | 2017-06-19 | 2020-05-12 | Cisco Technology, Inc. | Network node memory utilization analysis |
US11283680B2 (en) | 2017-06-19 | 2022-03-22 | Cisco Technology, Inc. | Identifying components for removal in a network configuration |
US10700933B2 (en) | 2017-06-19 | 2020-06-30 | Cisco Technology, Inc. | Validating tunnel endpoint addresses in a network fabric |
US10623259B2 (en) | 2017-06-19 | 2020-04-14 | Cisco Technology, Inc. | Validation of layer 1 interface in a network |
US10938855B1 (en) * | 2017-06-23 | 2021-03-02 | Digi International Inc. | Systems and methods for automatically and securely provisioning remote computer network infrastructure |
US10524116B2 (en) | 2017-06-27 | 2019-12-31 | Ibasis, Inc. | Internet of things services architecture |
US10785527B2 (en) | 2017-06-30 | 2020-09-22 | Qualcomm Incorporated | Dynamic allocation of wireless personal area network radios among a plurality of radio access technologies supported by a user equipment |
US10142794B1 (en) | 2017-07-10 | 2018-11-27 | International Business Machines Corporation | Real-time, location-aware mobile device data breach prevention |
US10397271B2 (en) | 2017-07-11 | 2019-08-27 | Cisco Technology, Inc. | Distributed denial of service mitigation for web conferencing |
US10499249B1 (en) | 2017-07-11 | 2019-12-03 | Sprint Communications Company L.P. | Data link layer trust signaling in communication network |
US10673698B2 (en) | 2017-07-21 | 2020-06-02 | Cisco Technology, Inc. | Service function chain optimization using live testing |
US20190026796A1 (en) * | 2017-07-21 | 2019-01-24 | Veniam, Inc. | Systems and methods for trading data in a network of moving things, for example including a network of autonomous vehicles |
US10834113B2 (en) | 2017-07-25 | 2020-11-10 | Netskope, Inc. | Compact logging of network traffic events |
US10713633B2 (en) * | 2017-07-26 | 2020-07-14 | The Toronto-Dominion Bank | Computing device and method to perform a data transfer using a document |
US10650367B2 (en) * | 2017-07-28 | 2020-05-12 | Ncr Corporation | Peer-to-peer (P2P) peripheral communication control |
USD882602S1 (en) | 2017-07-28 | 2020-04-28 | Verisign, Inc. | Display screen or portion thereof with a sequential graphical user interface of a mobile device |
USD844649S1 (en) | 2017-07-28 | 2019-04-02 | Verisign, Inc. | Display screen or portion thereof with a sequential graphical user interface |
JP6640798B2 (en) * | 2017-07-31 | 2020-02-05 | グリー株式会社 | Application usage management program, application usage management method, server, management program, and management user terminal |
US10209978B1 (en) * | 2017-08-04 | 2019-02-19 | Sprint Communications Company L.P. | Mobile application installation service on a mobile phone |
US10764295B2 (en) * | 2017-08-08 | 2020-09-01 | International Business Machines Corporation | Monitoring service policy management |
US10462171B2 (en) * | 2017-08-08 | 2019-10-29 | Sentinel Labs Israel Ltd. | Methods, systems, and devices for dynamically modeling and grouping endpoints for edge networking |
US11063856B2 (en) | 2017-08-24 | 2021-07-13 | Cisco Technology, Inc. | Virtual network function monitoring in a network function virtualization deployment |
DE102017119589A1 (en) * | 2017-08-25 | 2019-02-28 | Vorwerk & Co. Interholding Gmbh | A method of connecting a home appliance to a home wireless network |
US10462187B2 (en) * | 2017-08-28 | 2019-10-29 | General Electric Company | Network security policy configuration based on predetermined command groups |
US11256799B2 (en) | 2017-08-29 | 2022-02-22 | Seagate Technology Llc | Device lifecycle distributed ledger |
US10621578B2 (en) | 2017-08-29 | 2020-04-14 | Bank Of America Corporation | Transferring data using a smart reconciliation system |
US10459958B2 (en) | 2017-08-29 | 2019-10-29 | Bank Of America Corporation | Automated response system using smart data |
US10594502B1 (en) * | 2017-09-08 | 2020-03-17 | 8X8, Inc. | Communication bridging among disparate platforms |
EP3679709B1 (en) | 2017-09-08 | 2021-11-03 | Convida Wireless, LLC | Automated service enrollment in a machine-to-machine communications network |
US10587484B2 (en) | 2017-09-12 | 2020-03-10 | Cisco Technology, Inc. | Anomaly detection and reporting in a network assurance appliance |
US10587456B2 (en) | 2017-09-12 | 2020-03-10 | Cisco Technology, Inc. | Event clustering for a network assurance platform |
US10554477B2 (en) | 2017-09-13 | 2020-02-04 | Cisco Technology, Inc. | Network assurance event aggregator |
US11005892B2 (en) | 2017-09-17 | 2021-05-11 | Allot Ltd. | System, method, and apparatus of securing and managing internet-connected devices and networks |
US10791065B2 (en) | 2017-09-19 | 2020-09-29 | Cisco Technology, Inc. | Systems and methods for providing container attributes as part of OAM techniques |
US10856134B2 (en) | 2017-09-19 | 2020-12-01 | Microsoft Technolgy Licensing, LLC | SMS messaging using a service capability exposure function |
US10664688B2 (en) | 2017-09-20 | 2020-05-26 | Google Llc | Systems and methods of detecting and responding to a visitor to a smart home environment |
US10333833B2 (en) | 2017-09-25 | 2019-06-25 | Cisco Technology, Inc. | Endpoint path assurance |
CN109561048B (en) * | 2017-09-26 | 2021-05-25 | 北京京东尚科信息技术有限公司 | Communication management method and device |
CN109587672B (en) * | 2017-09-28 | 2022-04-26 | 展讯通信(上海)有限公司 | Method, device and terminal for selecting roaming operator network |
US10271236B1 (en) | 2017-09-29 | 2019-04-23 | At&T Intellectual Property I, L.P. | Collection of crowd-sourced access point data for 5G or other next generation network |
US10382995B2 (en) | 2017-09-29 | 2019-08-13 | At&T Intellectual Property I, L.P. | Utilization of crowd-sourced access point data for 5G or other next generation network |
US10231134B1 (en) | 2017-09-29 | 2019-03-12 | At&T Intellectual Property I, L.P. | Network planning based on crowd-sourced access point data for 5G or other next generation network |
WO2019061514A1 (en) * | 2017-09-30 | 2019-04-04 | 深圳大学 | Secure wireless communication physical layer slope authentication method and apparatus |
US11109232B2 (en) * | 2017-10-03 | 2021-08-31 | Single Digits Connection, Llc | Alerting systems and methods |
US10938921B2 (en) * | 2017-10-10 | 2021-03-02 | Samsung Electronics Co., Ltd | Method and apparatus for associating services in an electronic device |
US11018981B2 (en) | 2017-10-13 | 2021-05-25 | Cisco Technology, Inc. | System and method for replication container performance and policy validation using real time network traffic |
CN107948944B (en) * | 2017-10-16 | 2020-10-13 | 南京网元通信技术有限公司 | Method for verifying charging accuracy of mobile network content based on software simulation |
CN107835498B (en) * | 2017-10-18 | 2021-01-08 | 上海掌门科技有限公司 | Method and equipment for managing user |
US10541893B2 (en) | 2017-10-25 | 2020-01-21 | Cisco Technology, Inc. | System and method for obtaining micro-service telemetry data |
CN107682858A (en) * | 2017-10-27 | 2018-02-09 | 成都九洲电子信息系统股份有限公司 | A kind of the whole network leads to cryptographic communication system |
AU2018360878B2 (en) | 2017-10-31 | 2023-04-13 | Qoria Holdings Pty Ltd | A device management system |
US10628591B2 (en) * | 2017-11-20 | 2020-04-21 | Forcepoint Llc | Method for fast and efficient discovery of data assets |
US10477022B2 (en) | 2017-11-22 | 2019-11-12 | Repnow Inc. | Automated telephone host system interaction |
US11080670B2 (en) * | 2017-11-22 | 2021-08-03 | Ncr Corporation | Integrated retail platform |
WO2019101724A1 (en) * | 2017-11-24 | 2019-05-31 | British Telecommunications Public Limited Company | Access control for digital assets |
US11868995B2 (en) | 2017-11-27 | 2024-01-09 | Nok Nok Labs, Inc. | Extending a secure key storage for transaction confirmation and cryptocurrency |
CN109871309B (en) * | 2017-12-04 | 2020-12-04 | 中国移动通信集团公司 | Method and system for generating test case of charging system |
US11102053B2 (en) | 2017-12-05 | 2021-08-24 | Cisco Technology, Inc. | Cross-domain assurance |
US10855647B2 (en) * | 2017-12-05 | 2020-12-01 | At&T Intellectual Property I, L.P. | Systems and methods for providing ENUM service activations |
US10412113B2 (en) | 2017-12-08 | 2019-09-10 | Duo Security, Inc. | Systems and methods for intelligently configuring computer security |
US10671621B2 (en) | 2017-12-08 | 2020-06-02 | Microsoft Technology Licensing, Llc | Predictive scaling for cloud applications |
JP6996959B2 (en) * | 2017-12-11 | 2022-01-17 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | Communication normality confirmation device, communication normality confirmation method, and program |
US10868821B2 (en) * | 2017-12-20 | 2020-12-15 | Sophos Limited | Electronic mail security using a heartbeat |
US10972483B2 (en) | 2017-12-20 | 2021-04-06 | Sophos Limited | Electronic mail security using root cause analysis |
US11423143B1 (en) | 2017-12-21 | 2022-08-23 | Exabeam, Inc. | Anomaly detection based on processes executed within a network |
TWI650990B (en) * | 2017-12-22 | 2019-02-11 | 中華電信股份有限公司 | Certificate transparency monitoring ststem and method thereof |
US11026090B2 (en) | 2018-01-08 | 2021-06-01 | All Purpose Networks, Inc. | Internet of things system with efficient and secure communications network |
US10827019B2 (en) | 2018-01-08 | 2020-11-03 | All Purpose Networks, Inc. | Publish-subscribe broker network overlay system |
US11165866B2 (en) * | 2018-01-09 | 2021-11-02 | Stel Life, Inc. | Secure wireless communication platform |
US11831409B2 (en) | 2018-01-12 | 2023-11-28 | Nok Nok Labs, Inc. | System and method for binding verifiable claims |
US10873509B2 (en) | 2018-01-17 | 2020-12-22 | Cisco Technology, Inc. | Check-pointing ACI network state and re-execution from a check-pointed state |
EP3744076A4 (en) * | 2018-01-24 | 2021-08-25 | Telefonaktiebolaget LM Ericsson (publ) | Method and apparatus for improving service discovery |
CN110071952B (en) * | 2018-01-24 | 2023-08-08 | 北京京东尚科信息技术有限公司 | Service call quantity control method and device |
US10754502B2 (en) * | 2018-01-25 | 2020-08-25 | Microsoft Technology Licensing, Llc | Framework for contextual notifications |
US10539424B2 (en) | 2018-01-26 | 2020-01-21 | Honeywell International Inc. | Navigating an indoor transit system using a mobile device |
EP3518158A1 (en) * | 2018-01-29 | 2019-07-31 | Siemens Aktiengesellschaft | System and method for generating a plant bill of process |
CN108306703B (en) * | 2018-01-30 | 2019-10-18 | 郑州云海信息技术有限公司 | A kind of method, apparatus and equipment of redundancy monitoring network time synchronization |
CN110099393B (en) * | 2018-01-30 | 2022-06-21 | 阿里巴巴集团控股有限公司 | Method, device and system for monitoring network access state of distribution network equipment |
US11381495B2 (en) * | 2018-01-31 | 2022-07-05 | Assia Spe, Llc | Systems and methods for net neutrality testing |
WO2019152804A1 (en) | 2018-02-02 | 2019-08-08 | Affirmed Networks, Inc. | Estimating bandwidth savings for adaptive bit rate streaming |
US10572495B2 (en) | 2018-02-06 | 2020-02-25 | Cisco Technology Inc. | Network assurance database version compatibility |
JP7025638B2 (en) * | 2018-02-09 | 2022-02-25 | 富士通株式会社 | Management program and management method |
US11080075B2 (en) * | 2018-02-09 | 2021-08-03 | Lenovo (Singapore) Pte. Ltd. | Data threshold notification |
US11470115B2 (en) | 2018-02-09 | 2022-10-11 | Attivo Networks, Inc. | Implementing decoys in a network environment |
CZ308225B6 (en) * | 2018-02-19 | 2020-03-11 | Aducid S.R.O. | Authentication system and authentication method using personal authentication items |
EP3756384A1 (en) | 2018-02-20 | 2020-12-30 | Microsoft Technology Licensing, LLC | Dynamic selection of network elements |
US11665059B2 (en) | 2018-02-21 | 2023-05-30 | Aeris Communications, Inc. | Intelligent carrier and service selection for the internet of things |
US10848478B2 (en) * | 2018-02-21 | 2020-11-24 | JumpCloud, Inc. | Secure endpoint authentication credential control |
JP6777663B2 (en) * | 2018-02-22 | 2020-10-28 | 日本電信電話株式会社 | Policy conflict detection system and policy conflict detection method |
US11057352B2 (en) | 2018-02-28 | 2021-07-06 | Xaptum, Inc. | Communication system and method for machine data routing |
US20190273718A1 (en) * | 2018-03-01 | 2019-09-05 | ShieldX Networks, Inc. | Intercepting network traffic routed by virtual switches for selective security processing |
EP3762321A2 (en) * | 2018-03-09 | 2021-01-13 | Rite-Hite Holding Corporation | Methods and apparatus to monitor and manage loading docks and facility operations |
US11288662B2 (en) | 2018-03-19 | 2022-03-29 | Chng Weng WAH | Security systems and methods for electronic devices |
US10700868B2 (en) | 2018-03-19 | 2020-06-30 | Chng Weng WAH | Security systems and methods for electronic devices |
JP7087503B2 (en) * | 2018-03-19 | 2022-06-21 | 株式会社リコー | Information processing equipment, information processing system and information processing method |
KR20200132947A (en) | 2018-03-20 | 2020-11-25 | 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 | System and method for network slicing |
CA3095039A1 (en) * | 2018-03-23 | 2019-09-26 | Neustar, Inc. | Methods and apparatus to enable device based geo-location messages |
CN108566385B (en) * | 2018-03-24 | 2021-02-09 | 西安电子科技大学 | Bidirectional authentication method based on cloud efficient privacy protection |
US10798061B2 (en) * | 2018-03-26 | 2020-10-06 | Fortinet, Inc. | Automated learning of externally defined network assets by a network security device |
WO2019190468A1 (en) * | 2018-03-27 | 2019-10-03 | Visa International Service Association | System and method for authorizing and provisioning a token to an appliance |
JP7095354B2 (en) * | 2018-03-28 | 2022-07-05 | 株式会社リコー | Information processing system, information processing device, information processing method and program |
US10965653B2 (en) | 2018-03-28 | 2021-03-30 | Xaptum, Inc. | Scalable and secure message brokering approach in a communication system |
US10944650B2 (en) * | 2018-03-29 | 2021-03-09 | Fortinet, Inc. | Programmable, policy-based efficient wireless sniffing networks in WIPS (wireless intrusion prevention systems) |
KR102372494B1 (en) * | 2018-03-30 | 2022-03-10 | 삼성전자 주식회사 | Method and apparatus for cellular network connection release of terminal connected with nonauthentication |
US10733179B2 (en) * | 2018-04-04 | 2020-08-04 | Schlage Lock Company Llc | Access control with multiple security ecosystems |
CN108566425A (en) * | 2018-04-12 | 2018-09-21 | 苏州工业园区服务外包职业学院 | Block chain node business configuration system and method |
US10582356B2 (en) | 2018-04-20 | 2020-03-03 | At&T Intellectual Property I, L.P. | Dynamic management of default subcarrier spacing for 5G or other next generation network |
US10367687B1 (en) * | 2018-04-20 | 2019-07-30 | Spotify Ab | Methods and systems for provisioning settings of a media playback device |
US11216603B2 (en) | 2018-04-22 | 2022-01-04 | Sas Institute Inc. | Transformation and evaluation of disallowed combinations in designed experiments |
US11561690B2 (en) | 2018-04-22 | 2023-01-24 | Jmp Statistical Discovery Llc | Interactive graphical user interface for customizable combinatorial test construction |
WO2019205106A1 (en) * | 2018-04-27 | 2019-10-31 | Hewlett Packard Enterprise Development Lp | Convert devices according to seed images |
US10805439B2 (en) | 2018-04-30 | 2020-10-13 | Xaptum, Inc. | Communicating data messages utilizing a proprietary network |
US10817505B2 (en) * | 2018-05-08 | 2020-10-27 | Sap Se | Maintaining consistency within a federated cloud environment |
CN110460544B (en) | 2018-05-08 | 2021-09-07 | 华为技术有限公司 | Identification distribution method of switches in stack, optical cable and related equipment |
CN116546134A (en) * | 2018-05-08 | 2023-08-04 | 苹果公司 | User interface for controlling or presenting device usage on an electronic device |
CN109729063B (en) * | 2018-05-14 | 2022-02-25 | 网联清算有限公司 | Information processing method and information processing system applied to encryption machine |
US11431741B1 (en) | 2018-05-16 | 2022-08-30 | Exabeam, Inc. | Detecting unmanaged and unauthorized assets in an information technology network with a recurrent neural network that identifies anomalously-named assets |
JP7251055B2 (en) * | 2018-05-31 | 2023-04-04 | 富士フイルムビジネスイノベーション株式会社 | Information processing device and program |
US10666612B2 (en) | 2018-06-06 | 2020-05-26 | Cisco Technology, Inc. | Service chains for inter-cloud traffic |
US10868677B2 (en) * | 2018-06-06 | 2020-12-15 | Blackberry Limited | Method and system for reduced V2X receiver processing load using certificates |
US10812315B2 (en) * | 2018-06-07 | 2020-10-20 | Cisco Technology, Inc. | Cross-domain network assurance |
US20190378155A1 (en) * | 2018-06-12 | 2019-12-12 | Live Inc. | Time critical inventory control systems and methods |
CN110602023A (en) * | 2018-06-12 | 2019-12-20 | 中国移动通信有限公司研究院 | Personal information safety control method, device and computer readable storage medium |
US11477667B2 (en) | 2018-06-14 | 2022-10-18 | Mark Cummings | Using orchestrators for false positive detection and root cause analysis |
JP2019219794A (en) * | 2018-06-18 | 2019-12-26 | 富士ゼロックス株式会社 | Server device and license management system |
US10462023B1 (en) * | 2018-06-20 | 2019-10-29 | Mitel Networks Corporation | Communication method and system including built-in self test |
US10942991B1 (en) * | 2018-06-22 | 2021-03-09 | Kiddofy, LLC | Access controls using trust relationships and simplified content curation |
US10853115B2 (en) | 2018-06-25 | 2020-12-01 | Amazon Technologies, Inc. | Execution of auxiliary functions in an on-demand network code execution system |
US11019027B2 (en) | 2018-06-27 | 2021-05-25 | Cisco Technology, Inc. | Address translation for external network appliance |
US11044273B2 (en) | 2018-06-27 | 2021-06-22 | Cisco Technology, Inc. | Assurance of security rules in a network |
US10911495B2 (en) | 2018-06-27 | 2021-02-02 | Cisco Technology, Inc. | Assurance of security rules in a network |
US11218508B2 (en) | 2018-06-27 | 2022-01-04 | Cisco Technology, Inc. | Assurance of security rules in a network |
US10659298B1 (en) | 2018-06-27 | 2020-05-19 | Cisco Technology, Inc. | Epoch comparison for network events |
US10904070B2 (en) | 2018-07-11 | 2021-01-26 | Cisco Technology, Inc. | Techniques and interfaces for troubleshooting datacenter networks |
CN109194496A (en) * | 2018-07-15 | 2019-01-11 | 张帆 | A kind of Distributed Services mandatory system |
USD917520S1 (en) * | 2018-07-19 | 2021-04-27 | Magnifact, Llc | Display screen with a transitional graphical user interface |
US11025638B2 (en) | 2018-07-19 | 2021-06-01 | Forcepoint, LLC | System and method providing security friction for atypical resource access requests |
EP3827577B1 (en) | 2018-07-23 | 2023-09-13 | Microsoft Technology Licensing, LLC | System and method for intelligently managing sessions in a mobile network |
US10834266B2 (en) * | 2018-07-23 | 2020-11-10 | Cisco Technology, Inc. | Process-efficient generation of data records for data communications involving groups or aggregates of IoT devices |
US11228614B1 (en) * | 2018-07-24 | 2022-01-18 | Amazon Technologies, Inc. | Automated management of security operations centers |
US11099870B1 (en) | 2018-07-25 | 2021-08-24 | Amazon Technologies, Inc. | Reducing execution times in an on-demand network code execution system using saved machine states |
US10826770B2 (en) | 2018-07-26 | 2020-11-03 | Cisco Technology, Inc. | Synthesis of models for networks using automated boolean learning |
CN110769455B (en) | 2018-07-26 | 2022-05-31 | 华为技术有限公司 | Data collection method, equipment and system |
US10616072B1 (en) | 2018-07-27 | 2020-04-07 | Cisco Technology, Inc. | Epoch data interface |
US11246031B2 (en) | 2018-08-15 | 2022-02-08 | Oceus Networks, Llc | Disguising UE communications in a cellular network |
TW202404318A (en) | 2018-08-23 | 2024-01-16 | 美商阿爾克斯股份有限公司 | System for first hop gateway redundancy in a network computing environment using arp |
EP3614285A1 (en) | 2018-08-24 | 2020-02-26 | Hewlett-Packard Development Company, L.P. | Active testing of access control policy |
WO2020040675A1 (en) * | 2018-08-24 | 2020-02-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and communication device for controlling reception of data |
WO2020044082A1 (en) * | 2018-08-30 | 2020-03-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for restricting access to a management interface using standard management protocols and software |
US11134087B2 (en) | 2018-08-31 | 2021-09-28 | Forcepoint, LLC | System identifying ingress of protected data to mitigate security breaches |
US10924593B2 (en) | 2018-08-31 | 2021-02-16 | Xaptum, Inc. | Virtualization with distributed adaptive message brokering |
US10628865B2 (en) | 2018-09-04 | 2020-04-21 | Capital One Services, Llc | Subscription management platforms for automated group-based subscriptions |
US11368821B2 (en) * | 2018-09-07 | 2022-06-21 | Effortel Technologies | System and method for online charging telecommunication services in real time |
US10542157B1 (en) * | 2018-09-13 | 2020-01-21 | Nokia Solutions And Networks Oy | Communications recommendation assistant |
US11594312B2 (en) * | 2018-09-18 | 2023-02-28 | Myndshft Technologies, Inc | Data aggregation and process automation systems and methods |
CN109672580B (en) * | 2018-09-21 | 2022-01-18 | 平安科技(深圳)有限公司 | Full link monitoring method, device, terminal equipment and storage medium |
US11620345B2 (en) * | 2018-09-24 | 2023-04-04 | Salesforce, Inc. | Method and apparatus for a mechanism for event replay when a reroute of recordation of the event occurred in a multiplexed event recordation system |
US11184162B1 (en) * | 2018-09-28 | 2021-11-23 | NortonLifeLock Inc. | Privacy preserving secure task automation |
US11762869B1 (en) | 2018-09-28 | 2023-09-19 | Splunk Inc. | Generating journey flow visualization with node placement based on shortest distance to journey start |
US11039364B2 (en) | 2018-09-28 | 2021-06-15 | Google Llc | Methods and apparatus for proactively switching between available networks |
US11144185B1 (en) | 2018-09-28 | 2021-10-12 | Splunk Inc. | Generating and providing concurrent journey visualizations associated with different journey definitions |
US11075954B2 (en) * | 2018-09-28 | 2021-07-27 | International Business Machines Corporation | Identifying systems where a policy as a code is applicable |
CN109615357A (en) * | 2018-09-30 | 2019-04-12 | 三亚中科遥感研究所 | The fine-grained user of remote sensing big data cloud authorizes resource charge system and method |
US11128536B2 (en) * | 2018-10-04 | 2021-09-21 | Sandvine Corporation | System and method for intent based traffic management |
US11038774B2 (en) | 2018-10-22 | 2021-06-15 | International Business Machines Corporation | Facilitating reconciliation for early-access programs |
US11210654B2 (en) * | 2018-10-23 | 2021-12-28 | Capital One Services, Llc | Systems and methods for multicomputer data transferring to activate contactless communication |
US11308194B2 (en) * | 2018-10-31 | 2022-04-19 | Seagate Technology Llc | Monitoring device components using distributed ledger |
US10904796B2 (en) * | 2018-10-31 | 2021-01-26 | Motorola Solutions, Inc. | Device, system and method for throttling network usage of a mobile communication device |
CN109495460B (en) * | 2018-11-01 | 2021-04-06 | 南京邮电大学 | Privacy policy dynamic updating method in combined service |
US11171980B2 (en) | 2018-11-02 | 2021-11-09 | Forcepoint Llc | Contagion risk detection, analysis and protection |
US10951616B2 (en) | 2018-11-02 | 2021-03-16 | Spruce Labs, Inc. | Proximity-based device authentication |
US11245723B2 (en) | 2018-11-02 | 2022-02-08 | Forcepoint, LLC | Detection of potentially deceptive URI (uniform resource identifier) of a homograph attack |
CN109152095B (en) * | 2018-11-07 | 2021-10-22 | 上海尚往网络科技有限公司 | Wireless network connection method for terminal |
WO2020102727A1 (en) * | 2018-11-15 | 2020-05-22 | Trade Examination Technologies, Inc. | Secure and accountable data access |
KR102624323B1 (en) | 2018-11-16 | 2024-01-12 | 삼성전자 주식회사 | An electronic device supporting a virtual mobile infrastructure that allows a user to select computing resources and runs applications with selected computing resources |
US11121923B2 (en) | 2018-11-19 | 2021-09-14 | Cisco Technology, Inc. | Automatic provisioning of network components |
US11943093B1 (en) | 2018-11-20 | 2024-03-26 | Amazon Technologies, Inc. | Network connection recovery after virtual machine transition in an on-demand network code execution system |
US11295026B2 (en) | 2018-11-20 | 2022-04-05 | Forcepoint, LLC | Scan, detect, and alert when a user takes a photo of a computer monitor with a mobile phone |
US10824528B2 (en) | 2018-11-27 | 2020-11-03 | Capital One Services, Llc | Techniques and system for optimization driven by dynamic resilience |
US10282248B1 (en) | 2018-11-27 | 2019-05-07 | Capital One Services, Llc | Technology system auto-recovery and optimality engine and techniques |
MX2021006000A (en) | 2018-11-28 | 2021-07-06 | Viasat Inc | Hybrid adaptive networks. |
WO2020111090A1 (en) * | 2018-11-28 | 2020-06-04 | 株式会社オートネットワーク技術研究所 | Monitoring device, monitoring program, and monitoring method |
US11297099B2 (en) | 2018-11-29 | 2022-04-05 | Forcepoint, LLC | Redisplay computing with integrated data filtering |
US10938877B2 (en) | 2018-11-30 | 2021-03-02 | Xaptum, Inc. | Optimizing data transmission parameters of a proprietary network |
CN111277995B (en) * | 2018-12-05 | 2023-04-07 | 中国移动通信集团甘肃有限公司 | Method and equipment for identifying terminal user |
CN111294311B (en) * | 2018-12-06 | 2022-05-13 | 中国移动通信集团河南有限公司 | Traffic charging method and system for preventing traffic fraud |
US11658962B2 (en) | 2018-12-07 | 2023-05-23 | Cisco Technology, Inc. | Systems and methods of push-based verification of a transaction |
US10470015B1 (en) * | 2018-12-12 | 2019-11-05 | Citrix Systems, Inc. | System with automatic creation of application-orchestration widgets for multi-application interaction |
US11050767B2 (en) | 2018-12-17 | 2021-06-29 | Forcepoint, LLC | System for identifying and handling electronic communications from a potentially untrustworthy sending entity |
US11159368B2 (en) * | 2018-12-17 | 2021-10-26 | Sap Se | Component integration |
US11140149B2 (en) | 2018-12-20 | 2021-10-05 | Cisco Technology, Inc. | Zero-touch bootstrap of an endpoint without admin pre-provisioning |
US10848974B2 (en) * | 2018-12-28 | 2020-11-24 | Intel Corporation | Multi-domain trust establishment in edge cloud architectures |
US11017117B2 (en) | 2019-01-02 | 2021-05-25 | Bank Of America Corporation | Pre-firewall data classification |
EP3912035A1 (en) | 2019-01-15 | 2021-11-24 | Microsoft Technology Licensing, LLC | Dynamic auto-configuration of multi-tenant paas components |
US11818606B2 (en) * | 2019-01-24 | 2023-11-14 | Kymeta Corporation | Multiple aspects of communication in a diverse communication network |
US11416641B2 (en) | 2019-01-24 | 2022-08-16 | Netskope, Inc. | Incident-driven introspection for data loss prevention |
US10841399B2 (en) * | 2019-01-24 | 2020-11-17 | Tambora Systems Singapore Pte. Ltd. | System and method for guaranteeing quality of experience of a user in an online environment by implementing a required change in the mobile network based on quality of experience requirements and received quality of experience parameters |
US10667125B1 (en) | 2019-01-24 | 2020-05-26 | At&T Intellectual Property, L.P. | On-device activation of mobile computing devices |
CN109768984B (en) * | 2019-01-25 | 2021-11-09 | 成都西加云杉科技有限公司 | Authorization method and system for WiFi data analysis |
US10912053B2 (en) | 2019-01-31 | 2021-02-02 | Xaptum, Inc. | Enforcing geographic restrictions for multitenant overlay networks |
US11379426B2 (en) | 2019-02-05 | 2022-07-05 | Forcepoint, LLC | Media transfer protocol file copy detection |
US11263642B2 (en) * | 2019-02-08 | 2022-03-01 | International Business Machines Corporation | Ensuring compliance in on-premise compute models |
CN111614476A (en) * | 2019-02-22 | 2020-09-01 | 华为技术有限公司 | Equipment configuration method, system and device |
US11695777B2 (en) * | 2019-02-26 | 2023-07-04 | Vmware, Inc. | Hybrid access control model in computer systems |
US11042849B2 (en) * | 2019-02-26 | 2021-06-22 | Apifiny Group Inc. | Adjusting transaction distribution based on predicted open transaction execution rates |
US12041039B2 (en) | 2019-02-28 | 2024-07-16 | Nok Nok Labs, Inc. | System and method for endorsing a new authenticator |
US10986150B2 (en) | 2019-03-01 | 2021-04-20 | Netskope, Inc. | Load balancing in a dynamic scalable services mesh |
US11562093B2 (en) | 2019-03-06 | 2023-01-24 | Forcepoint Llc | System for generating an electronic security policy for a file format type |
US11490256B2 (en) | 2019-03-11 | 2022-11-01 | Hewlett Packard Enterprise Development Lp | Secure zero-touch provisioning of network devices in an offline deployment |
CN109979109B (en) * | 2019-03-13 | 2021-04-27 | 上海网之易璀璨网络科技有限公司 | Rental server processing method, processor, terminal and storage medium |
US10721168B1 (en) * | 2019-03-15 | 2020-07-21 | Juniper Networks, Inc. | Utilizing constraint optimization for egress peer engineering to determine optimized traffic plans and to implement an optimized traffic plan |
JP7259432B2 (en) * | 2019-03-18 | 2023-04-18 | 富士フイルムビジネスイノベーション株式会社 | Information processing device and program |
EP3713261A1 (en) | 2019-03-20 | 2020-09-23 | Giesecke+Devrient Mobile Security GmbH | Aggression management for a mobile device |
CN109921902B (en) | 2019-03-22 | 2020-10-23 | 创新先进技术有限公司 | Key management method, security chip, service server and information system |
US11861386B1 (en) | 2019-03-22 | 2024-01-02 | Amazon Technologies, Inc. | Application gateways in an on-demand network code execution system |
CN113647151A (en) * | 2019-03-28 | 2021-11-12 | 诺基亚技术有限公司 | Apparatus, method and computer program for performing radio access notification area update |
US11792024B2 (en) | 2019-03-29 | 2023-10-17 | Nok Nok Labs, Inc. | System and method for efficient challenge-response authentication |
US11570213B2 (en) * | 2019-04-03 | 2023-01-31 | Cisco Technology, Inc. | Collaborative security for application layer encryption |
CN110049505B (en) * | 2019-04-08 | 2021-08-24 | Oppo广东移动通信有限公司 | Data transmission method and related device |
US11030298B2 (en) * | 2019-04-08 | 2021-06-08 | Microsoft Technology Licensing, Llc | Candidate user profiles for fast, isolated operating system use |
US11095512B2 (en) * | 2019-04-17 | 2021-08-17 | Bank Of America Corporation | Internet of things (“IoT”) versatile nodes |
WO2020223414A1 (en) | 2019-04-30 | 2020-11-05 | Phantom Auto Inc. | Low latency wireless communication system for teleoperated vehicle environments |
US11115345B2 (en) | 2019-05-06 | 2021-09-07 | Bank Of America Corporation | Systems and methods for providing self-referencing utilization calculation and dynamic resource allocation based thereon for digital transmissions |
US11394789B2 (en) | 2019-05-08 | 2022-07-19 | Hewlett Packard Enterprise Development Lp | Seamless migration of a network management system deployment to cloud-based deployment |
US11527150B2 (en) * | 2019-05-08 | 2022-12-13 | Ford Global Technologies, Llc | Vehicle remote control |
EP3973427A4 (en) | 2019-05-20 | 2023-06-21 | Sentinel Labs Israel Ltd. | Systems and methods for executable code detection, automatic feature extraction and position independent code detection |
CN113315566B (en) * | 2019-05-23 | 2023-03-24 | 上海微小卫星工程中心 | Satellite ground comprehensive test system |
WO2020236296A1 (en) * | 2019-05-23 | 2020-11-26 | Cray Inc. | System and method for facilitating efficient packet injection into an output buffer in a network interface controller (nic) |
US10924353B2 (en) | 2019-05-29 | 2021-02-16 | Cisco Technology, Inc. | Progressive refinement of device classifications using colored device and policy trees |
US10904029B2 (en) | 2019-05-31 | 2021-01-26 | Apple Inc. | User interfaces for managing controllable external devices |
US11363071B2 (en) | 2019-05-31 | 2022-06-14 | Apple Inc. | User interfaces for managing a local network |
US11263324B2 (en) | 2019-06-04 | 2022-03-01 | Bank Of America Corporation | Monitoring source code repository data in real-time to protect sensitive information and provide entity-specific alerts |
US20220224553A1 (en) * | 2019-06-04 | 2022-07-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Managing a charging operation in a communication network |
US11223556B2 (en) | 2019-06-04 | 2022-01-11 | Phantom Auto Inc. | Platform for redundant wireless communications optimization |
US11625366B1 (en) | 2019-06-04 | 2023-04-11 | Exabeam, Inc. | System, method, and computer program for automatic parser creation |
US11102169B2 (en) | 2019-06-06 | 2021-08-24 | Cisco Technology, Inc. | In-data-plane network policy enforcement using IP addresses |
US11119809B1 (en) | 2019-06-20 | 2021-09-14 | Amazon Technologies, Inc. | Virtualization-based transaction handling in an on-demand network code execution system |
US11810105B2 (en) | 2019-06-20 | 2023-11-07 | Visa International Service Association | System and method for authorizing and provisioning a token to an appliance |
CN110225511B (en) * | 2019-06-20 | 2022-04-15 | 天翼数字生活科技有限公司 | Method, device and system for acquiring IMEI number of terminal and computer equipment |
US11082232B2 (en) * | 2019-06-24 | 2021-08-03 | International Business Machines Corporation | Auditably proving a usage history of an asset |
US11044168B2 (en) | 2019-07-02 | 2021-06-22 | Cisco Technology, Inc. | Fingerprinting application traffic in a network |
US11425174B2 (en) * | 2019-07-03 | 2022-08-23 | Buckeye Cablevision, Inc. | System for content triggered high-speed data service delivery independent of media delivery mechanisms |
US11139852B2 (en) * | 2019-07-04 | 2021-10-05 | Nortac Defence Limited | Situational awareness over a low bandwidth short burst data satellite system |
CN112218392A (en) | 2019-07-10 | 2021-01-12 | 鸿富锦精密电子(天津)有限公司 | Data center system |
TWI734139B (en) * | 2019-07-10 | 2021-07-21 | 鴻齡科技股份有限公司 | Data center system |
CN110750806A (en) * | 2019-07-16 | 2020-02-04 | 黑龙江省科学院自动化研究所 | TP-MFSA (TP-Multi-function document analysis) inhibition release-based high-dimensional position track data privacy protection release system and method |
US10873504B1 (en) | 2019-07-17 | 2020-12-22 | Hewlett Packard Enterprise Development Lp | Managing concurrently received configuration requests in a computing network |
US11100229B2 (en) * | 2019-07-18 | 2021-08-24 | Infineon Technologies Ag | Secure hybrid boot systems and secure boot procedures for hybrid systems |
US11196734B2 (en) | 2019-07-23 | 2021-12-07 | Allstate Insurance Company | Safe logon |
CN112312405B (en) * | 2019-07-25 | 2022-05-13 | 神顶科技(南京)有限公司 | Method and system for reinforcing wireless signal and sharing and following wireless network load |
US11698891B2 (en) * | 2019-07-30 | 2023-07-11 | Salesforce.Com, Inc. | Database systems and related multichannel communication methods |
US11178015B2 (en) * | 2019-08-01 | 2021-11-16 | Zebra Technologies Corporation | System, method and apparatus for updating network configuration parameters |
CN110443598B (en) * | 2019-08-08 | 2023-03-28 | 上海中通吉网络技术有限公司 | Account settlement method and device |
US11051172B2 (en) | 2019-08-13 | 2021-06-29 | Cisco Technology, Inc. | Private wireless network guest access |
US11469942B2 (en) | 2019-08-15 | 2022-10-11 | At&T Intellectual Property I, L.P. | System and method for SDN orchestration validation |
JPWO2021044895A1 (en) * | 2019-09-05 | 2021-03-11 | ||
TWI713325B (en) * | 2019-09-17 | 2020-12-11 | 宜鼎國際股份有限公司 | System and method capable of remotely controlling electronic apparatus |
US11483696B2 (en) * | 2019-09-24 | 2022-10-25 | T-Mobile Usa, Inc. | Rich user experience for service upgrades |
US11245577B2 (en) * | 2019-09-26 | 2022-02-08 | Amazon Technologies, Inc. | Template-based onboarding of internet-connectible devices |
CN111669424B (en) * | 2019-09-29 | 2023-05-02 | 深圳乐播科技有限公司 | Screen projection connection method, device and system and electronic equipment |
US11317285B2 (en) * | 2019-09-30 | 2022-04-26 | Dish Network L.L.C. | Wireless network provisioning using a pre-shared key |
US11201932B2 (en) * | 2019-10-07 | 2021-12-14 | Oracle International Corporation | Systems and methods for securely using cloud services on on-premises data |
US10686645B1 (en) * | 2019-10-09 | 2020-06-16 | Capital One Services, Llc | Scalable subscriptions for virtual collaborative workspaces |
US11134416B2 (en) * | 2019-10-16 | 2021-09-28 | Verizon Patent And Licensing Inc. | Control plane traffic load balancing, protection, and network selection |
FR3102332B1 (en) * | 2019-10-18 | 2024-03-08 | Sagemcom Broadband Sas | Method of connecting a communication node and communication node. |
CN110704754B (en) * | 2019-10-18 | 2023-03-28 | 支付宝(杭州)信息技术有限公司 | Push model optimization method and device executed by user terminal |
US10999755B1 (en) * | 2019-10-19 | 2021-05-04 | Skylo Technologies, Inc. | Data package selection for data reporting of one or more data sources |
CN110784240B (en) * | 2019-11-04 | 2022-02-25 | 华立科技股份有限公司 | Wireless data communication module and method |
TWI721631B (en) * | 2019-11-05 | 2021-03-11 | 中華電信股份有限公司 | System for determining obstacle source through notification information and method thereof |
JP7318730B2 (en) * | 2019-11-11 | 2023-08-01 | 日本電信電話株式会社 | Test equipment, test method and test program |
CN110995529B (en) * | 2019-11-14 | 2021-09-21 | 广州方硅信息技术有限公司 | Configuration data testing method and device of recommendation system and electronic equipment |
US11349777B2 (en) * | 2019-11-15 | 2022-05-31 | Charter Communications Operating, Llc | Network quality of service controller |
US10866872B1 (en) | 2019-11-18 | 2020-12-15 | Capital One Services, Llc | Auto-recovery for software systems |
CN110990824A (en) * | 2019-11-19 | 2020-04-10 | 江苏理工学院 | Method for remotely controlling service life of non-networked machine |
US11290390B2 (en) | 2019-11-20 | 2022-03-29 | Oracle International Corporation | Methods, systems, and computer readable media for lockless communications network resource quota sharing |
US11071484B2 (en) * | 2019-11-20 | 2021-07-27 | International Business Machines Corporation | Reduce electromagnetic frequency emissions from a mobile device |
KR20210076652A (en) * | 2019-12-16 | 2021-06-24 | 현대자동차주식회사 | In vehicle multimedia system and method of managing storage for the same |
WO2021130409A1 (en) * | 2019-12-23 | 2021-07-01 | Nokia Technologies Oy | Method, apparatus, and computer program product for alternative quality of service profile notification handling |
PH12019050295A1 (en) * | 2019-12-26 | 2021-06-28 | Samsung Electronics Ltd | System and method of collecting anonymous user data for analytics using recursive internetwork architecture (rina) |
US10979365B1 (en) * | 2019-12-31 | 2021-04-13 | Hughes Network Systems, Llc | Accelerated startup of satellite high-bandwidth communication sessions |
EP3846413B1 (en) * | 2020-01-03 | 2022-09-21 | Withings | Method and apparatus for installing a network-connectable device |
US11374980B1 (en) * | 2020-01-17 | 2022-06-28 | Cisco Technology, Inc. | Resolution of policy enforcement point by cross correlating other policies |
FR3106462A1 (en) * | 2020-01-20 | 2021-07-23 | Orange | Remote administration technique of a device by an administration server |
US11418542B2 (en) | 2020-01-23 | 2022-08-16 | Forcepoint Llc | Identification of unknown traffic based on transport layer security extensions |
US11856022B2 (en) | 2020-01-27 | 2023-12-26 | Netskope, Inc. | Metadata-based detection and prevention of phishing attacks |
US10944631B1 (en) * | 2020-01-29 | 2021-03-09 | Salesforce.Com, Inc. | Network request and file transfer prioritization based on traffic elasticity |
US11523282B2 (en) * | 2020-02-05 | 2022-12-06 | Lookout Inc. | Use of geolocation to improve security while protecting privacy |
US11638312B2 (en) | 2020-02-13 | 2023-04-25 | Qualcomm Incorporated | Slice allocation |
US11663087B2 (en) * | 2020-02-19 | 2023-05-30 | Nutanix, Inc. | Validating metering of a disaster recovery service used in clouds |
JPWO2021171210A1 (en) * | 2020-02-26 | 2021-09-02 | ||
WO2021171071A1 (en) * | 2020-02-26 | 2021-09-02 | ラクテン・シンフォニー・シンガポール・プライベート・リミテッド | Network service construction system and network service construction method |
CN111371872B (en) * | 2020-02-27 | 2022-04-15 | 青岛海尔空调器有限总公司 | Anti-theft control method, shared household appliance, server and shared system |
US11714682B1 (en) | 2020-03-03 | 2023-08-01 | Amazon Technologies, Inc. | Reclaiming computing resources in an on-demand code execution system |
CN111988141B (en) * | 2020-03-18 | 2022-08-02 | 支付宝(杭州)信息技术有限公司 | Method and device for sharing cluster key |
US11277734B2 (en) * | 2020-03-23 | 2022-03-15 | T-Mobile Usa, Inc. | Systems and methods for secure automatic system-network dual-activation |
USD973678S1 (en) * | 2020-03-25 | 2022-12-27 | Platstack, LLC | Display screen with graphical user interface |
USD974369S1 (en) * | 2020-03-25 | 2023-01-03 | Platstack, LLC | Display screen with graphical user interface |
USD974368S1 (en) * | 2020-03-25 | 2023-01-03 | Platstack, LLC | Display screen with graphical user interface |
US11451643B2 (en) * | 2020-03-30 | 2022-09-20 | Amazon Technologies, Inc. | Managed traffic processing for applications with multiple constituent services |
CN111586696B (en) * | 2020-04-29 | 2022-04-01 | 重庆邮电大学 | Resource allocation and unloading decision method based on multi-agent architecture reinforcement learning |
US10959167B1 (en) | 2020-05-06 | 2021-03-23 | Verizon Patent And Licensing Inc. | System and method for 5G service icon display and quality of service enforcement |
US11513667B2 (en) | 2020-05-11 | 2022-11-29 | Apple Inc. | User interface for audio message |
CN111600875B (en) * | 2020-05-14 | 2022-03-22 | 江苏大学 | Anonymous data sharing method and system based on data source and data master hiding |
US11018943B1 (en) * | 2020-05-20 | 2021-05-25 | Cisco Technology, Inc. | Learning packet capture policies to enrich context for device classification systems |
US11568357B2 (en) | 2020-05-26 | 2023-01-31 | Greenline, Llc | Systems and methods of validating data entry and generating error flags using artificial intelligence |
US11297802B2 (en) * | 2020-05-26 | 2022-04-12 | Greenline, Llc | Systems and methods of digital tracking of wellness programs with dynamic feedback from pets at different clinics using different manufacturer products |
US11901061B2 (en) * | 2020-05-29 | 2024-02-13 | PT Genie, LLC | Adaptation of telehealth in physical therapy |
CN111666303B (en) * | 2020-05-29 | 2022-09-09 | 傲网信息科技(厦门)有限公司 | Online and offline document processing system and method |
US11553030B2 (en) * | 2020-06-01 | 2023-01-10 | Microsoft Technology Licensing, Llc | Service worker configured to serve multiple single page applications |
US20210377240A1 (en) * | 2020-06-02 | 2021-12-02 | FLEX Integration LLC | System and methods for tokenized hierarchical secured asset distribution |
EP3920487A1 (en) | 2020-06-04 | 2021-12-08 | Sandvine Corporation | System and method for quality of experience management |
US11368554B2 (en) * | 2020-06-09 | 2022-06-21 | Paypal, Inc. | Systems and methods for regulating service behavior |
CN112291070A (en) * | 2020-06-10 | 2021-01-29 | 李彩云 | Communication information processing method and system based on cloud edge terminal cooperation |
US11956253B1 (en) | 2020-06-15 | 2024-04-09 | Exabeam, Inc. | Ranking cybersecurity alerts from multiple sources using machine learning |
US11405361B1 (en) | 2020-06-17 | 2022-08-02 | Amazon Technologies, Inc. | Securing connections with edge devices that are incapable of encrypted transport layer connections |
US11770377B1 (en) * | 2020-06-29 | 2023-09-26 | Cyral Inc. | Non-in line data monitoring and security services |
US11349932B2 (en) | 2020-06-30 | 2022-05-31 | Cisco Technology, Inc. | Policy-based connection provisioning using domain name system (DNS) requests |
CN111857476B (en) * | 2020-07-17 | 2022-07-08 | 维沃移动通信有限公司 | Display method and device and electronic equipment |
CN114070662A (en) * | 2020-07-31 | 2022-02-18 | 上海国际货币经纪有限责任公司 | Message bus system |
US20220046019A1 (en) * | 2020-08-04 | 2022-02-10 | Juniper Networks, Inc. | Adding third party hardware to network devices |
US11502993B2 (en) * | 2020-08-10 | 2022-11-15 | Perimeter 81 Ltd | Scalable and on-demand multi-tenant and multi region secure network |
US11765039B2 (en) * | 2020-08-13 | 2023-09-19 | Grass Valley Canada | System and method for optimizing deployment of a processing function in a media production workflow |
US11340916B2 (en) * | 2020-08-20 | 2022-05-24 | Vmware, Inc. | Dynamic plugin management for system health |
CN114205764B (en) * | 2020-09-02 | 2023-11-03 | 中国移动通信集团安徽有限公司 | Traffic resource sharing method, device, equipment and computer readable storage medium |
US12002125B2 (en) * | 2020-09-18 | 2024-06-04 | Salesforce, Inc. | Provisioning an escrow user account for tracking learning progress of an end user of a cloud computing platform while interacting with virtual learning entities of the cloud computing platform that represent content of an external learning application |
CN112437404B (en) * | 2020-09-29 | 2022-05-17 | 海能达通信股份有限公司 | Method, unit and gateway for realizing end-to-end data transmission |
WO2022069954A1 (en) * | 2020-10-01 | 2022-04-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Cell multi-agent coordination in shared control elements |
US11475668B2 (en) | 2020-10-09 | 2022-10-18 | Bank Of America Corporation | System and method for automatic video categorization |
US11443267B2 (en) * | 2020-10-20 | 2022-09-13 | Microsoft Technology Licensing, Llc | Intelligent edge state optimization within enterprise with zero data exhaust |
US11943616B2 (en) | 2020-11-13 | 2024-03-26 | Oracle International Corporation | Methods, systems, and computer readable media for utilizing network function identifiers to implement ingress message rate limiting |
US11663362B2 (en) * | 2020-11-10 | 2023-05-30 | Cobalt Iron, Inc. | Data inspection system and method |
CN114830615B (en) * | 2020-11-18 | 2024-05-10 | 京东方科技集团股份有限公司 | Data distribution system and data distribution method |
US11550713B1 (en) | 2020-11-25 | 2023-01-10 | Amazon Technologies, Inc. | Garbage collection in distributed systems using life cycled storage roots |
US11593270B1 (en) | 2020-11-25 | 2023-02-28 | Amazon Technologies, Inc. | Fast distributed caching using erasure coded object parts |
CN112528272A (en) * | 2020-12-04 | 2021-03-19 | 浪潮云信息技术股份公司 | Public open data-based security and privacy integrated protection system and method |
US11895501B2 (en) | 2020-12-08 | 2024-02-06 | Oracle International Corporation | Methods, systems, and computer readable media for automatic key management of network function (NF) repository function (NRF) access token public keys for 5G core (5GC) authorization to mitigate security attacks |
US11579857B2 (en) | 2020-12-16 | 2023-02-14 | Sentinel Labs Israel Ltd. | Systems, methods and devices for device fingerprinting and automatic deployment of software in a computing network using a peer-to-peer approach |
US11483724B2 (en) * | 2021-01-05 | 2022-10-25 | At&T Intellectual Property I, L.P. | Methods, systems, and devices for provisioning a subscriber identity module (SIM) to conduct testing of a communication device |
US11601399B2 (en) | 2021-01-20 | 2023-03-07 | Bank Of America Corporation | System and method for detecting forbidden network accesses based on zone connectivity mapping |
US11487639B2 (en) | 2021-01-21 | 2022-11-01 | Vmware, Inc. | User experience scoring and user interface |
US11586526B2 (en) | 2021-01-22 | 2023-02-21 | Vmware, Inc. | Incident workflow interface for application analytics |
US20220237097A1 (en) * | 2021-01-22 | 2022-07-28 | Vmware, Inc. | Providing user experience data to tenants |
CN112907928A (en) * | 2021-01-26 | 2021-06-04 | 徐州徐工矿业机械有限公司 | Wireless synchronous acquisition and classification system for multiple signals of excavator |
US20220247827A1 (en) * | 2021-01-29 | 2022-08-04 | Nokia Technologies Oy | Apparatus, methods, and computer programs |
CN112911716B (en) * | 2021-02-05 | 2023-02-17 | 贵州久华信电子技术有限公司 | Data transmission method, device, equipment and storage medium |
US11520910B2 (en) | 2021-02-09 | 2022-12-06 | Bank Of America Corporation | System and method for routing data to authorized users based on security classification of data |
US11563859B2 (en) * | 2021-03-03 | 2023-01-24 | T-Mobile Usa, Inc. | Internet subscription management in a cellular-based network |
US11553524B2 (en) * | 2021-03-04 | 2023-01-10 | Oracle International Corporation | Methods, systems, and computer readable media for resource object level authorization at a network function (NF) |
US11696185B2 (en) * | 2021-03-15 | 2023-07-04 | T-Mobile Usa, Inc. | Dynamic provisioning reconciliation of network elements in wireless communication networks |
US20220303313A1 (en) * | 2021-03-16 | 2022-09-22 | International Business Machines Corporation | Revision of access control system triggered by policies based on risks and/or countermeasures thereof |
US20220303278A1 (en) * | 2021-03-18 | 2022-09-22 | Hughes Systique Corporation | Captive portal for tiered access using conditional dns forwarding |
US11570674B1 (en) | 2021-04-01 | 2023-01-31 | T-Mobile Usa, Inc. | Dynamic management of telecommunication services at user equipment |
US20220321564A1 (en) * | 2021-04-02 | 2022-10-06 | Hewlett-Packard Development Company, L.P. | Resource payload communications |
US11659008B2 (en) * | 2021-04-13 | 2023-05-23 | Sevco Security, Inc. | Method for characterize security technology deployment telemetry across a computer network |
US11523281B1 (en) * | 2021-04-23 | 2022-12-06 | T-Mobile Usa, Inc. | Validating customized user equipment (UE) |
CN113259156B (en) * | 2021-04-27 | 2021-12-07 | 江南信安(北京)科技有限公司 | Remote upgrading method and system for network equipment with Internet of things module |
US11704484B2 (en) | 2021-04-30 | 2023-07-18 | Bank Of America Corporation | Cross channel digital data parsing and generation system |
US20220368624A1 (en) * | 2021-05-17 | 2022-11-17 | At&T Intellectual Property I, L.P. | Managing changes to interdependent network elements |
EP4096191A1 (en) * | 2021-05-25 | 2022-11-30 | Nokia Solutions and Networks Oy | Service model management request |
US11233801B1 (en) * | 2021-05-26 | 2022-01-25 | Netskope, Inc. | Session protocol update or upgrade web traffic |
US11671430B2 (en) * | 2021-05-26 | 2023-06-06 | Netskope, Inc. | Secure communication session using encryption protocols and digitally segregated secure tunnels |
CN113271360B (en) * | 2021-05-26 | 2023-09-29 | 维沃移动通信(杭州)有限公司 | Application program recommendation method and device, electronic equipment and medium |
US11528601B1 (en) | 2021-06-09 | 2022-12-13 | T-Mobile Usa, Inc. | Determining and ameliorating wireless telecommunication network functionalities that are impaired when using end-to-end encryption |
US11921842B2 (en) | 2021-06-14 | 2024-03-05 | Kyndryl, Inc. | Multifactor authorization on accessing hardware resources |
CN113312059B (en) * | 2021-06-15 | 2023-08-04 | 北京百度网讯科技有限公司 | Service processing system, method and cloud native system |
US11831688B2 (en) * | 2021-06-18 | 2023-11-28 | Capital One Services, Llc | Systems and methods for network security |
US11711421B2 (en) | 2021-06-23 | 2023-07-25 | Bank Of America Corporation | System and method using peer-to-peer connections for a distribution interaction session |
US11977629B2 (en) * | 2021-06-30 | 2024-05-07 | Microsoft Technology Licensing, Llc | Retrospective memory analysis |
US11916966B2 (en) * | 2021-07-02 | 2024-02-27 | Adaptiv Networks Inc. | Access policy management |
US11593428B2 (en) | 2021-07-08 | 2023-02-28 | Bank Of America Corporation | System and method for detecting errors in a task workflow from a video stream |
US11558264B1 (en) * | 2021-07-09 | 2023-01-17 | ReadyLinks Inc. | Facilitating and provisioning customer broadband transport service |
EP4367855A1 (en) | 2021-07-09 | 2024-05-15 | Readylinks Inc. | Facilitating and provisioning customer broadband transport service |
US11750407B2 (en) * | 2021-07-09 | 2023-09-05 | ReadyLinks Inc. | Bidirectional power feed digital communication device |
US11899782B1 (en) | 2021-07-13 | 2024-02-13 | SentinelOne, Inc. | Preserving DLL hooks |
US12034728B2 (en) * | 2021-07-23 | 2024-07-09 | EMC IP Holding Company LLC | Dynamic access control in service mesh with service broker |
US11785488B2 (en) * | 2021-07-28 | 2023-10-10 | Verizon Patent And Licensing Inc. | Enhanced real-time network consumption tracking for wireless networks |
US11785018B2 (en) | 2021-07-29 | 2023-10-10 | Bank Of America Corporation | Mobile device management system for securely managing device communication |
CN113612661B (en) * | 2021-08-03 | 2022-10-28 | 北京安天网络安全技术有限公司 | Method, device, computing equipment and storage medium for checking program stability |
CN113726634B (en) * | 2021-08-19 | 2023-03-21 | 宏图智能物流股份有限公司 | Voice transmission system and method |
CN113449135B (en) | 2021-08-31 | 2021-11-19 | 阿里巴巴达摩院(杭州)科技有限公司 | Image generation system and method |
US20230067756A1 (en) * | 2021-09-02 | 2023-03-02 | At&T Intellectual Property I, L.P. | Using machine learning for security anomaly detection and user experience inference |
US11403426B1 (en) * | 2021-09-14 | 2022-08-02 | Intercom, Inc. | Single path prioritization for a communication system |
TWI796789B (en) * | 2021-09-15 | 2023-03-21 | 綠夾克運動事業股份有限公司 | Monitoring system and monitoring method for vehicle |
US12041671B2 (en) * | 2021-09-21 | 2024-07-16 | Verizon Patent And Licensing Inc. | Systems and methods for indicating the presence of a multi-access edge computing application |
US11902664B2 (en) | 2021-09-22 | 2024-02-13 | Adam A. Locke | Cellular telephone with protracting monitor screen and camera |
US11985573B1 (en) * | 2021-09-29 | 2024-05-14 | T-Mobile Usa, Inc. | Methods and systems for reporting zero usage for immediate trigger types |
US11856030B2 (en) * | 2021-10-04 | 2023-12-26 | Motorola Solutions, Inc. | Security ecosystem |
US11917654B2 (en) * | 2021-10-26 | 2024-02-27 | Dell Products, Lp | System and method for intelligent wireless carrier link management system at user equipment devices |
WO2023070151A1 (en) * | 2021-10-26 | 2023-05-04 | Yoochooz Apps Pty Ltd | An electronic message content intercepting system |
US20230145797A1 (en) * | 2021-11-08 | 2023-05-11 | At&T Intellectual Property I, L.P. | Facilitating multiple step network configuration activation automation based on parallel processing |
US11871318B2 (en) * | 2021-11-08 | 2024-01-09 | Verizon Patent And Licensing Inc. | Systems and methods for tiered network slice design and management in a wireless network |
CN114139510B (en) * | 2021-11-08 | 2022-11-25 | 盟拓软件(苏州)有限公司 | Excel table-based process operation method and device, electronic equipment and storage medium |
US11936658B2 (en) | 2021-11-15 | 2024-03-19 | Bank Of America Corporation | Intelligent assignment of a network resource |
US11968280B1 (en) | 2021-11-24 | 2024-04-23 | Amazon Technologies, Inc. | Controlling ingestion of streaming data to serverless function executions |
CN114205847B (en) * | 2021-11-29 | 2024-01-19 | 上海庆科信息技术有限公司 | Method, device, storage medium, equipment and system for testing terminal equipment |
US11797285B2 (en) * | 2021-11-29 | 2023-10-24 | Software Ag | Systems and/or methods for facilitating software-based deployments into potentially complex heterogeneous computing environments |
US11991525B2 (en) | 2021-12-02 | 2024-05-21 | T-Mobile Usa, Inc. | Wireless device access and subsidy control |
TWI786981B (en) * | 2021-12-07 | 2022-12-11 | 中華電信股份有限公司 | System and mehtod of precertificate management and computer readable medium thererof |
US20230188370A1 (en) * | 2021-12-09 | 2023-06-15 | Rakuten Mobile, Inc. | System, method, and computer program to dynamically adapt over-the-top (ott) call routing |
US12015603B2 (en) | 2021-12-10 | 2024-06-18 | Amazon Technologies, Inc. | Multi-tenant mode for serverless code execution |
CN114267115B (en) * | 2021-12-27 | 2024-03-08 | 江苏银承网络科技股份有限公司 | Bill identification method and system |
CN114356240B (en) * | 2021-12-30 | 2023-09-26 | 重庆市紫建电子股份有限公司 | Method for rapidly and efficiently checking capacity flow |
US11553327B1 (en) * | 2022-01-19 | 2023-01-10 | Steve Disney | System and method for storing personal information |
US11716278B1 (en) | 2022-01-25 | 2023-08-01 | Bank Of America Corporation | System and method for determining the shortest data transfer path in data communication |
US12040967B2 (en) | 2022-01-25 | 2024-07-16 | Bank Of America Corporation | System and method for splitting data elements for data communication based on transformation types implemented on the data elements at different devices |
US11656926B1 (en) | 2022-01-26 | 2023-05-23 | Bank Of America Corporation | Systems and methods for automatically applying configuration changes to computing clusters |
US11799971B2 (en) | 2022-02-17 | 2023-10-24 | Bank Of America Corporation | Systems and methods for session migration between devices |
CN114640663A (en) * | 2022-03-03 | 2022-06-17 | 上海联虹技术有限公司 | Method for remotely controlling CPE (customer premises equipment) and remote control system |
US20230306432A1 (en) * | 2022-03-23 | 2023-09-28 | Capital One Services, Llc | Transmitting notifications based on machine learning model outputs |
FR3133990A1 (en) * | 2022-04-04 | 2023-10-06 | SiVIEW | System for controlling at least one eye examination device |
US11924047B2 (en) * | 2022-04-20 | 2024-03-05 | Jpmorgan Chase Bank, N.A. | System and method for declarative automation for deployment of a software-defined network (SDN) |
KR102429325B1 (en) * | 2022-05-02 | 2022-08-04 | 에스엠테크놀러지(주) | Parallel type certificate verification system and operation method |
US20230376879A1 (en) * | 2022-05-18 | 2023-11-23 | Cisco Technology, Inc. | Observability profile mapping for teleworker observability |
CN114900370B (en) * | 2022-06-02 | 2024-04-26 | 合肥卓讯云网科技有限公司 | Method and device for filtering flow aiming at application protocol |
CN115102852B (en) * | 2022-06-17 | 2023-07-21 | 中国联合网络通信集团有限公司 | Internet of things service opening method and device, electronic equipment and computer medium |
US11803848B1 (en) * | 2022-06-21 | 2023-10-31 | Pointsbet Pty Ltd. | Event-driven distributed networked jackpot architecture |
US11947682B2 (en) | 2022-07-07 | 2024-04-02 | Netskope, Inc. | ML-based encrypted file classification for identifying encrypted data movement |
TWI812491B (en) * | 2022-09-27 | 2023-08-11 | 財團法人資訊工業策進會 | System and method for cybersecurity threat detection and early warning |
US20240113967A1 (en) * | 2022-09-29 | 2024-04-04 | Cisco Technology, Inc. | Application Path Selection for Cloud-Based Applications from a Client Device |
US11765075B1 (en) | 2022-10-07 | 2023-09-19 | International Business Machines Corporation | Automatic tolling in traversal of a network |
CN115373965B (en) * | 2022-10-25 | 2023-01-10 | 中汽信息科技(天津)有限公司 | User tag identification method and device based on stack technology |
US11985044B1 (en) | 2022-11-01 | 2024-05-14 | Bank Of America Corporation | System and methods for proactive network infrastructure component monitoring and replacement |
CN115941612B (en) * | 2022-11-14 | 2024-05-17 | 中国联合网络通信集团有限公司 | Data processing method, device and storage medium |
US20240223461A1 (en) * | 2022-11-18 | 2024-07-04 | Altiostar Networks India Private Limited | Simulator for endc testing in communication network |
US11706207B1 (en) * | 2022-11-22 | 2023-07-18 | Integrity Security Services Llc | Application programming interface for certificate management systems |
US20240187411A1 (en) * | 2022-12-04 | 2024-06-06 | Asad Hasan | Human system operator identity associated audit trail of containerized network application with prevention of privilege escalation, online black-box testing, and related systems and methods |
US20240187438A1 (en) * | 2022-12-05 | 2024-06-06 | Netskope, Inc. | Policy-based ip address allocation |
US12034726B1 (en) * | 2023-05-31 | 2024-07-09 | Cloudflare, Inc. | Logging access types based on inserting tenant control headers into requests |
CN117851244B (en) * | 2023-12-29 | 2024-06-18 | 云和恩墨(北京)信息技术有限公司 | Database fault detection method and device, electronic equipment and storage medium |
Citations (102)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5283904A (en) * | 1990-12-21 | 1994-02-01 | Intel Corporation | Multi-processor programmable interrupt controller system |
US5594777A (en) * | 1992-08-26 | 1997-01-14 | Telecom Finland Oy | Wireless private branch exchange system for use with mobile communication devices |
US5889477A (en) * | 1996-03-25 | 1999-03-30 | Mannesmann Aktiengesellschaft | Process and system for ascertaining traffic conditions using stationary data collection devices |
US6038452A (en) * | 1997-08-29 | 2000-03-14 | Nortel Networks Corporation | Telecommunication network utilizing a quality of service protocol |
US6198915B1 (en) * | 1995-01-30 | 2001-03-06 | Telemac Corporation | Mobile phone with internal accounting |
US20010053694A1 (en) * | 2000-01-31 | 2001-12-20 | Fujitsu Limited | Network system with dynamic service profile updating functions |
US20020022472A1 (en) * | 2000-07-21 | 2002-02-21 | Telemac Corporation | Multiple virtual wallets in wireless device |
US20020120540A1 (en) * | 2000-12-01 | 2002-08-29 | Michael Kende | System and method for automatic analysis of rate information |
US20020131404A1 (en) * | 2000-11-28 | 2002-09-19 | 4Thpass Inc. | Method and system for maintaining and distributing wireless applications |
US20030004937A1 (en) * | 2001-05-15 | 2003-01-02 | Jukka-Pekka Salmenkaita | Method and business process to maintain privacy in distributed recommendation systems |
US20030005112A1 (en) * | 2001-06-28 | 2003-01-02 | Krautkremer Todd Joseph | Methods, apparatuses and systems enabling a network services provider to deliver application performance management services |
US6505114B2 (en) * | 2001-02-06 | 2003-01-07 | Sergio Luciani | Traffic monitoring system and method |
US6532579B2 (en) * | 2000-04-18 | 2003-03-11 | Hitachi, Ltd. | Semiconductor integrated circuit and design method and manufacturing method of the same |
US6532235B1 (en) * | 1998-12-29 | 2003-03-11 | Qwest Communication Int'l., Inc. | Method and tool for calculating impact of voice traffic on fast packet networks |
US20030050837A1 (en) * | 2000-03-09 | 2003-03-13 | Kim Do Sik | Method and system providing advertisement using tone of ringing sounds of mobile phone and commerical transaction service in association with the same |
US20030050070A1 (en) * | 2001-03-14 | 2003-03-13 | Alex Mashinsky | Method and system for dynamic spectrum allocation and management |
US6539082B1 (en) * | 1998-05-13 | 2003-03-25 | British Telecommunications Public Limited Company | Billing system |
US6678516B2 (en) * | 2001-05-21 | 2004-01-13 | Nokia Corporation | Method, system, and apparatus for providing services in a privacy enabled mobile and Ubicom environment |
US6683853B1 (en) * | 1999-12-01 | 2004-01-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Dynamic upgrade of quality of service in a packet switched network |
US6684244B1 (en) * | 2000-01-07 | 2004-01-27 | Hewlett-Packard Development Company, Lp. | Aggregated policy deployment and status propagation in network management systems |
US20040019539A1 (en) * | 2002-07-25 | 2004-01-29 | 3Com Corporation | Prepaid billing system for wireless data networks |
US20040030705A1 (en) * | 2001-11-27 | 2004-02-12 | Accenture Global Services, Gmbh | Service control architecture |
US20040044623A1 (en) * | 2002-08-28 | 2004-03-04 | Wake Susan L. | Billing system for wireless device activity |
US20040047358A1 (en) * | 2000-01-31 | 2004-03-11 | Aeptech Microsystems, Inc. | Broadband communications access device |
US6839340B1 (en) * | 1997-09-16 | 2005-01-04 | Bell Atlantic Network Services | Network session management |
US20050009499A1 (en) * | 2003-07-08 | 2005-01-13 | Karl Koster | Systems and methods for billing a mobile wireless subscriber for fixed location service |
US20050021995A1 (en) * | 2003-07-21 | 2005-01-27 | July Systems Inc. | Application rights management in a mobile environment |
US20050055309A1 (en) * | 2003-09-04 | 2005-03-10 | Dwango North America | Method and apparatus for a one click upgrade for mobile applications |
US20050055291A1 (en) * | 2003-09-04 | 2005-03-10 | Sbc Knowledge Ventures, L.P. | Shared usage telecommunications billing system and method |
US20050060266A1 (en) * | 2000-06-27 | 2005-03-17 | Microsoft Corporation | Method and system for limiting the use of user-specific software features |
US20060014519A1 (en) * | 2000-09-07 | 2006-01-19 | William Marsh | Pooling groups of wireless communication users |
US20060019632A1 (en) * | 2004-07-12 | 2006-01-26 | At&T Wireless Services, Inc. | Dedicated wireless device business method |
US20060026679A1 (en) * | 2004-07-29 | 2006-02-02 | Zakas Phillip H | System and method of characterizing and managing electronic traffic |
US6996076B1 (en) * | 2001-03-29 | 2006-02-07 | Sonus Networks, Inc. | System and method to internetwork wireless telecommunication networks |
US6998985B2 (en) * | 2003-03-05 | 2006-02-14 | Dmatek, Ltd. | Monitoring and tracking network |
US20060034256A1 (en) * | 2004-08-13 | 2006-02-16 | Nokia Corporation | System and method for service discovery during connection setup in a wireless environment |
US20060040642A1 (en) * | 2004-08-20 | 2006-02-23 | Adam Boris | Service detail record application and system |
US20060048223A1 (en) * | 2004-08-31 | 2006-03-02 | Lee Michael C | Method and system for providing tamper-resistant software |
US20060045245A1 (en) * | 2004-08-27 | 2006-03-02 | Aaron Jeffrey A | Methods, systems and computer program products for monitoring service usage |
US7158792B1 (en) * | 2001-09-20 | 2007-01-02 | Sprint Communications Company L.P. | Selecting a wireless link in a public wireless communication network |
US7167078B2 (en) * | 2004-02-19 | 2007-01-23 | Pourchot Shawn C | Electric, telephone or network access control system and method |
US20070022289A1 (en) * | 2005-07-20 | 2007-01-25 | Mci, Inc. | Method and system for providing secure credential storage to support interdomain traversal |
US20070019670A1 (en) * | 2005-07-22 | 2007-01-25 | Eric Falardeau | Mobile connectivity solution |
US20070033194A1 (en) * | 2004-05-21 | 2007-02-08 | Srinivas Davanum M | System and method for actively managing service-oriented architecture |
US20070036312A1 (en) * | 2005-06-24 | 2007-02-15 | Lucent Technologies Inc. | Converged offline charging and online charging |
US7180855B1 (en) * | 2001-04-19 | 2007-02-20 | At&T Corp. | Service interface for QoS-driven HPNA networks |
US20070055694A1 (en) * | 2005-08-19 | 2007-03-08 | Customer Feedback Solutions, Inc. | System and method for providing a unified customer feedback solution |
US7197321B2 (en) * | 2003-02-25 | 2007-03-27 | Boston Communications Group, Inc. | Method and system for providing supervisory control over wireless phone usage |
US20070093243A1 (en) * | 2005-10-25 | 2007-04-26 | Vivek Kapadekar | Device management system |
US20080005561A1 (en) * | 2006-05-18 | 2008-01-03 | Research In Motion Limited | Automatic security action invocation for mobile communications device |
US20080005285A1 (en) * | 2006-07-03 | 2008-01-03 | Impulse Point, Llc | Method and System for Self-Scaling Generic Policy Tracking |
US7317699B2 (en) * | 2001-10-26 | 2008-01-08 | Research In Motion Limited | System and method for controlling configuration settings for mobile communication devices and services |
US7322044B2 (en) * | 2002-06-03 | 2008-01-22 | Airdefense, Inc. | Systems and methods for automated network policy exception detection and correction |
US7324447B1 (en) * | 2002-09-30 | 2008-01-29 | Packeteer, Inc. | Methods, apparatuses and systems facilitating concurrent classification and control of tunneled and non-tunneled network traffic |
US7325037B2 (en) * | 2002-02-27 | 2008-01-29 | Eastman Kodak Company | Method and system for client-based adaptive networking system |
US20080039102A1 (en) * | 2004-09-08 | 2008-02-14 | Pat Sewall | Hotspot Communication Limiter |
US20080052387A1 (en) * | 2006-08-22 | 2008-02-28 | Heinz John M | System and method for tracking application resource usage |
US20080049630A1 (en) * | 2006-08-22 | 2008-02-28 | Kozisek Steven E | System and method for monitoring and optimizing network performance to a wireless device |
US20080059743A1 (en) * | 2006-07-06 | 2008-03-06 | Sandisk Il Ltd. | Portable Storage Device With Updatable Access Permission |
US20080059474A1 (en) * | 2005-12-29 | 2008-03-06 | Blue Jungle | Detecting Behavioral Patterns and Anomalies Using Activity Profiles |
US20080064367A1 (en) * | 2006-09-13 | 2008-03-13 | Mformation Technologies Inc. | System and method to enable subscriber self-activation of wireless data terminals |
US7346410B2 (en) * | 2004-12-16 | 2008-03-18 | Seiko Epson Corporation | Method and system for manufacturing electronic device, electronic device, and electro-optical apparatus |
US20080070550A1 (en) * | 2006-09-20 | 2008-03-20 | Hose David A | Providing Subscriber Specific Information Across Wireless Networks |
US7349695B2 (en) * | 2004-06-02 | 2008-03-25 | Nokia Corporation | Multimode roaming mobile devices |
US20080167027A1 (en) * | 2007-01-07 | 2008-07-10 | Patrice Gautier | Graphical user interface and method for mobile device activation |
US7486185B2 (en) * | 2004-07-14 | 2009-02-03 | Spectrum Tracking Systems, Inc. | Method and system for providing tracking services to locate an asset |
US20090046723A1 (en) * | 2007-08-16 | 2009-02-19 | Rahman Reshad A | Distinguishing between connectivity verification availability and forwarding protocol functionality in a computer network |
US20090054030A1 (en) * | 2007-08-24 | 2009-02-26 | Microsoft Corporation | Mobile billboard and usage advisor |
US20090067372A1 (en) * | 2007-09-07 | 2009-03-12 | Qualcomm Incorporated | Host-based quality of service for wireless communications |
US20090197585A1 (en) * | 2008-02-01 | 2009-08-06 | Aaron Jeffrey A | Quality of Service for Grouped Cellular Devices |
US7644267B2 (en) * | 2004-03-31 | 2010-01-05 | Nokia Corporation | Controlling access to services in a communications system |
US7644151B2 (en) * | 2002-01-31 | 2010-01-05 | Lancope, Inc. | Network service zone locking |
US7647047B2 (en) * | 2005-09-07 | 2010-01-12 | Ventraq Corporation | Consumer configurable mobile communication solution |
US20100027469A1 (en) * | 2008-06-12 | 2010-02-04 | At&T Mobility Ii Llc | Point of sales and customer support for femtocell service and equipment |
US20100043068A1 (en) * | 2008-08-14 | 2010-02-18 | Juniper Networks, Inc. | Routing device having integrated mpls-aware firewall |
US7668903B2 (en) * | 2003-07-07 | 2010-02-23 | Xerox Corporation | Method and apparatus for dynamically delivering service profiles to clients |
US7668176B2 (en) * | 2001-01-18 | 2010-02-23 | Alcatel-Lucent Usa Inc. | Universal mobile telecommunications system (UMTS) quality of service (QoS) supporting variable QoS negotiation |
US20100071053A1 (en) * | 2006-12-29 | 2010-03-18 | Prodea Systems, Inc. | Presence Status Notification From Digital Endpoint Devices Through A Multi-Services Gateway Device At The User Premises |
US7685131B2 (en) * | 2006-02-28 | 2010-03-23 | International Business Machines Corporation | Web services database cluster architecture |
US7865182B2 (en) * | 2003-10-08 | 2011-01-04 | Single Touch Interactive, Inc. | Over the air provisioning of mobile device settings |
US7868778B2 (en) * | 2005-09-20 | 2011-01-11 | David Norris Kenwright | Apparatus and method for proximity-responsive display materials |
US7873344B2 (en) * | 2005-10-03 | 2011-01-18 | Cisco Technology, Inc. | System and method to distribute emergency information |
US7873705B2 (en) * | 2004-03-12 | 2011-01-18 | Flash Networks Ltd. | System and method for identifying content service within content server |
US7877090B2 (en) * | 2003-06-27 | 2011-01-25 | Oracle International Corporation | Roaming across different access mechanisms and network technologies |
US7882029B2 (en) * | 2001-10-16 | 2011-02-01 | Hewlett-Packard Development Company, L.P. | Centralized billing credit system utilizing a predetermined unit of usage |
US7881199B2 (en) * | 2006-01-04 | 2011-02-01 | Alcatel Lucent | System and method for prioritization of traffic through internet access network |
US7886047B1 (en) * | 2008-07-08 | 2011-02-08 | Sprint Communications Company L.P. | Audience measurement of wireless web subscribers |
US7890111B2 (en) * | 2006-12-22 | 2011-02-15 | Embarq Holdings Company, Llc | System and method for virtual wireless roaming |
US7890084B1 (en) * | 2006-10-30 | 2011-02-15 | Cellco Partnership | Enterprise instant message aggregator |
US7903553B2 (en) * | 2004-08-05 | 2011-03-08 | Huawei Technologies Co., Ltd. | Method, apparatus, edge router and system for providing QoS guarantee |
US7907970B2 (en) * | 2006-04-14 | 2011-03-15 | Qualcomm Incorporated | Providing quality of service for various traffic flows in a communications environment |
US7986935B1 (en) * | 2007-10-26 | 2011-07-26 | Sprint Communications Company L.P. | Service plan optimizer |
US8094551B2 (en) * | 2008-05-13 | 2012-01-10 | At&T Mobility Ii Llc | Exchange of access control lists to manage femto cell coverage |
US8102814B2 (en) * | 2006-11-14 | 2012-01-24 | Cisco Technology, Inc. | Access point profile for a mesh access point in a wireless mesh network |
US8108520B2 (en) * | 2003-06-19 | 2012-01-31 | Nokia Corporation | Apparatus and method for providing quality of service for a network data connection |
US8126722B2 (en) * | 2001-12-20 | 2012-02-28 | Verizon Business Global Llc | Application infrastructure platform (AIP) |
US8126123B2 (en) * | 2007-02-27 | 2012-02-28 | Alcatel Lucent | Pre-biller in internet protocol multimedia subsystem (IMS) charging gateway function (CGF) |
US8350700B2 (en) * | 2004-02-04 | 2013-01-08 | Contigo Solutions, Inc. | System for, and method of, monitoring the movement of mobile items |
US8352980B2 (en) * | 2007-02-15 | 2013-01-08 | At&T Intellectual Property I, Lp | System and method for single sign on targeted advertising |
US8364806B2 (en) * | 1998-12-08 | 2013-01-29 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8386386B1 (en) * | 2009-01-05 | 2013-02-26 | Sprint Communications Company L.P. | Phone usage pattern as credit card fraud detection trigger |
US8385896B2 (en) * | 2008-09-08 | 2013-02-26 | Proxicom Wireless, Llc | Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided |
Family Cites Families (1521)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US720505A (en) * | 1902-09-10 | 1903-02-10 | Benjamin Tucker | Nut-lock. |
JPS5930942B2 (en) * | 1978-08-30 | 1984-07-30 | 日産自動車株式会社 | automatic transmission downshift valve |
JPS5949452B2 (en) * | 1978-10-03 | 1984-12-03 | 日産自動車株式会社 | Automatic transmission line pressure control device |
US6581092B1 (en) | 1999-09-29 | 2003-06-17 | Ricoh Co., Ltd. | Method and system for remote diagnostic, control and information collection based on various communication modes for sending messages to users |
US5014031A (en) * | 1989-07-21 | 1991-05-07 | Heinz Nusser | Ultra precision pressure regulator |
US5131020A (en) | 1989-12-29 | 1992-07-14 | Smartroutes Systems Limited Partnership | Method of and system for providing continually updated traffic or other information to telephonically and other communications-linked customers |
US7113780B2 (en) | 1992-03-06 | 2006-09-26 | Aircell, Inc. | System for integrating an airborne wireless cellular network with terrestrial wireless cellular networks and the public switched telephone network |
US5325532A (en) | 1992-09-25 | 1994-06-28 | Compaq Computer Corporation | Automatic development of operating system boot image |
US6970434B1 (en) | 1995-06-07 | 2005-11-29 | Broadcom Corporation | Hierarchical communication system providing intelligent data, program and processing migration |
US5689641A (en) | 1993-10-01 | 1997-11-18 | Vicor, Inc. | Multimedia collaboration system arrangement for routing compressed AV signal through a participant site without decompressing the AV signal |
US6292828B1 (en) | 1994-02-23 | 2001-09-18 | David L. Williams | Trans-modal animated information processing with selective engagement |
WO1995025295A1 (en) | 1994-03-17 | 1995-09-21 | Dow Benelux N.V. | System for real time optimization and profit depiction |
US5633868A (en) | 1994-10-17 | 1997-05-27 | Lucent Technologies Inc. | Virtual circuit management in cellular telecommunications |
US5633484A (en) | 1994-12-26 | 1997-05-27 | Motorola, Inc. | Method and apparatus for personal attribute selection and management using a preference memory |
US5630159A (en) | 1994-12-29 | 1997-05-13 | Motorola, Inc. | Method and apparatus for personal attribute selection having delay management method and apparatus for preference establishment when preferences in a donor device are unavailable |
US7095854B1 (en) | 1995-02-13 | 2006-08-22 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5892900A (en) | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
FI99071C (en) | 1995-02-15 | 1997-09-25 | Nokia Mobile Phones Ltd | Procedure for use of applications in a mobile telephone as well as a mobile telephone |
US5572528A (en) | 1995-03-20 | 1996-11-05 | Novell, Inc. | Mobile networking method and apparatus |
US5774532A (en) | 1995-04-21 | 1998-06-30 | Mci Corporation | Single network record construction |
US5915008A (en) | 1995-10-04 | 1999-06-22 | Bell Atlantic Network Services, Inc. | System and method for changing advanced intelligent network services from customer premises equipment |
US5751719A (en) * | 1995-11-30 | 1998-05-12 | Lucent Technologies Inc. | Method and system for data transfer in the presence of disconnects |
US6272341B1 (en) | 1995-11-30 | 2001-08-07 | Motient Services Inc. | Network engineering/systems engineering system for mobile satellite communication system |
US5794142A (en) | 1996-01-29 | 1998-08-11 | Nokia Mobile Phones Limited | Mobile terminal having network services activation through the use of point-to-point short message service |
US5915226A (en) | 1996-04-19 | 1999-06-22 | Gemplus Card International | Prepaid smart card in a GSM based wireless telephone network and method for operating prepaid cards |
US5933778A (en) | 1996-06-04 | 1999-08-03 | At&T Wireless Services Inc. | Method and apparatus for providing telecommunication services based on a subscriber profile updated by a personal information manager |
US5903845A (en) | 1996-06-04 | 1999-05-11 | At&T Wireless Services Inc. | Personal information manager for updating a telecommunication subscriber profile |
US6961341B1 (en) | 1996-07-02 | 2005-11-01 | Microsoft Corporation | Adaptive bandwidth throttling for network services |
WO1998012616A2 (en) | 1996-09-23 | 1998-03-26 | Lowrie Mcintosh | Defining a uniform subject classification system incorporating document management/records retention functions |
US5960074A (en) | 1996-09-23 | 1999-09-28 | Curtis Clark | Mobile tele-computer network for motion picture, television and tv advertising production |
US5754953A (en) | 1996-09-24 | 1998-05-19 | Motorola, Inc. | Method and apparatus for assisting a user to activate service for a subscriber unit in a messaging system |
US6064878A (en) | 1996-10-23 | 2000-05-16 | At&T Corp. | Method for separately permissioned communication |
US9418381B2 (en) | 2000-04-14 | 2016-08-16 | Citigroup Credit Services, Inc. (USA) | Method and system for notifying customers of transaction opportunities |
US6335927B1 (en) | 1996-11-18 | 2002-01-01 | Mci Communications Corporation | System and method for providing requested quality of service in a hybrid network |
US5940472A (en) | 1996-12-16 | 1999-08-17 | Mci Communications Corporation | Intelligent services network test system |
JP3098442B2 (en) | 1997-01-28 | 2000-10-16 | 日本電気移動通信株式会社 | Telephone system |
US6157636A (en) | 1997-03-06 | 2000-12-05 | Bell Atlantic Network Services, Inc. | Network session management with gateway-directory services and authorization control |
US6137869A (en) | 1997-09-16 | 2000-10-24 | Bell Atlantic Network Services, Inc. | Network session management |
US5983270A (en) | 1997-03-11 | 1999-11-09 | Sequel Technology Corporation | Method and apparatus for managing internetwork and intranetwork activity |
NZ337772A (en) | 1997-03-12 | 2001-09-28 | Nomadix Inc | Nomadic translator or router |
US6934249B1 (en) | 1997-04-01 | 2005-08-23 | Cisco Technology, Inc. | Method and system for minimizing the connection set up time in high speed packet switching networks |
US20010048738A1 (en) | 1997-04-03 | 2001-12-06 | Sbc Technology Resourses, Inc. | Profile management system including user interface for accessing and maintaining profile data of user subscribed telephony services |
US6081591A (en) | 1997-04-16 | 2000-06-27 | Skoog; Frederick H. | Signaling network gateway device and method for use in a signaling network |
US6608637B1 (en) | 1997-04-23 | 2003-08-19 | Nortel Networks Limited | Multitasking graphical user interface |
CN1510936B (en) | 1997-04-24 | 2010-05-26 | 株式会社Ntt都科摩 | Mobile communication method of mobile communication system |
US6574321B1 (en) | 1997-05-08 | 2003-06-03 | Sentry Telecom Systems Inc. | Apparatus and method for management of policies on the usage of telecommunications services |
US6578077B1 (en) | 1997-05-27 | 2003-06-10 | Novell, Inc. | Traffic monitoring tool for bandwidth management |
US6393014B1 (en) | 1997-06-03 | 2002-05-21 | At&T Wireless Services, Inc. | Method and system for providing data communication with a mobile station |
US6035281A (en) | 1997-06-16 | 2000-03-07 | International Business Machines Corporation | System and method of multiparty billing for Web access |
US6115823A (en) | 1997-06-17 | 2000-09-05 | Amphus, Inc. | System and method for task performance based dynamic distributed power management in a computer system and design method therefor |
FI112900B (en) | 1997-06-17 | 2004-01-30 | Sonera Oyj | Pricing method in mobile system |
US6119933A (en) | 1997-07-17 | 2000-09-19 | Wong; Earl Chang | Method and apparatus for customer loyalty and marketing analysis |
US6104700A (en) | 1997-08-29 | 2000-08-15 | Extreme Networks | Policy based quality of service |
US6385644B1 (en) | 1997-09-26 | 2002-05-07 | Mci Worldcom, Inc. | Multi-threaded web based user inbox for report management |
US6226277B1 (en) | 1997-10-14 | 2001-05-01 | Lucent Technologies Inc. | Method for admitting new connections based on usage priorities in a multiple access system for communications networks |
US6370139B2 (en) | 1997-10-24 | 2002-04-09 | Tranz-Send Broadcasting Network, Inc. | System and method for providing information dispersal in a networked computing environment |
US6047268A (en) | 1997-11-04 | 2000-04-04 | A.T.&T. Corporation | Method and apparatus for billing for transactions conducted over the internet |
US6141565A (en) * | 1997-11-13 | 2000-10-31 | Metawave Communications Corporation | Dynamic mobile parameter optimization |
US5974439A (en) | 1997-11-21 | 1999-10-26 | International Business Machines Corporation | Resource sharing between real-time and general purpose programs |
WO1999027723A1 (en) | 1997-11-24 | 1999-06-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Multiple subscriber service profiles per mobile station in a cellular communications system |
FI105986B (en) * | 1997-11-26 | 2000-10-31 | Nokia Networks Oy | Subscriber Service Profiles in a Telecommunication System |
US6058434A (en) | 1997-11-26 | 2000-05-02 | Acuity Imaging, Llc | Apparent network interface for and between embedded and host processors |
US6535855B1 (en) | 1997-12-09 | 2003-03-18 | The Chase Manhattan Bank | Push banking system and method |
US6563806B1 (en) * | 1997-12-12 | 2003-05-13 | Hitachi, Ltd. | Base station for multi-carrier TDMA mobile communication system and method for assigning communication channels |
US7283561B1 (en) | 1997-12-12 | 2007-10-16 | Level 3 Communications, Llc | Secure network architecture with quality of service |
US6078953A (en) | 1997-12-29 | 2000-06-20 | Ukiah Software, Inc. | System and method for monitoring quality of service over network |
US6510152B1 (en) | 1997-12-31 | 2003-01-21 | At&T Corp. | Coaxial cable/twisted pair fed, integrated residence gateway controlled, set-top box |
US6359881B1 (en) | 1997-12-31 | 2002-03-19 | At&T Corp. | Hybrid fiber twisted pair local loop network service architecture |
US6229810B1 (en) | 1997-12-31 | 2001-05-08 | At&T Corp | Network server platform for a hybrid fiber twisted pair local loop network service architecture |
US6418147B1 (en) | 1998-01-21 | 2002-07-09 | Globalstar Lp | Multiple vocoder mobile satellite telephone system |
US6141686A (en) | 1998-03-13 | 2000-10-31 | Deterministic Networks, Inc. | Client-side application-classifier gathering network-traffic statistics and application and user names using extensible-service provider plugin for policy-based network control |
US6148336A (en) | 1998-03-13 | 2000-11-14 | Deterministic Networks, Inc. | Ordering of multiple plugin applications using extensible layered service provider with network traffic filtering |
JP3148713B2 (en) | 1998-03-23 | 2001-03-26 | 株式会社エイ・ティ・アール環境適応通信研究所 | Communication service quality control method and apparatus |
US6154738A (en) | 1998-03-27 | 2000-11-28 | Call; Charles Gainor | Methods and apparatus for disseminating product information via the internet using universal product codes |
US6654786B1 (en) | 1998-04-30 | 2003-11-25 | Openwave Systems Inc. | Method and apparatus for informing wireless clients about updated information |
US6246870B1 (en) | 1998-04-30 | 2001-06-12 | Ericsson Inc. | Tariff management apparatus and methods for multiple-mode communications terminals |
US6098878A (en) | 1998-04-30 | 2000-08-08 | Ericsson Inc. | Tariff management apparatus and method for communications terminals using smart cards |
US6219694B1 (en) | 1998-05-29 | 2001-04-17 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device having a shared electronic address |
US6397259B1 (en) | 1998-05-29 | 2002-05-28 | Palm, Inc. | Method, system and apparatus for packet minimized communications |
CA2333362C (en) * | 1998-06-05 | 2007-11-13 | British Telecommunications Public Limited Company | Communications network |
US6876653B2 (en) | 1998-07-08 | 2005-04-05 | Broadcom Corporation | Fast flexible filter processor based architecture for a network device |
US6278701B1 (en) | 1998-07-10 | 2001-08-21 | Verizon Laboratories Inc. | Capacity enhancement for multi-code CDMA with integrated services through quality of services and admission control |
US6452915B1 (en) | 1998-07-10 | 2002-09-17 | Malibu Networks, Inc. | IP-flow classification in a wireless point to multi-point (PTMP) transmission system |
US6763000B1 (en) | 1998-07-12 | 2004-07-13 | Agilent Technologies, Inc. | Monitoring ATM traffic load by quality of service type |
US6526066B1 (en) | 1998-07-16 | 2003-02-25 | Nortel Networks Limited | Apparatus for classifying a packet within a data stream in a computer network |
US6615183B1 (en) | 1998-07-20 | 2003-09-02 | Usa Technologies, Inc. | Method of warehousing user data entered at an electronic commerce terminal |
US6219786B1 (en) | 1998-09-09 | 2001-04-17 | Surfcontrol, Inc. | Method and system for monitoring and controlling network access |
US6263055B1 (en) | 1998-09-09 | 2001-07-17 | Lucent Technologies Inc. | System for suppressed ringing access of subscriber lines to identify usage anomalies of customer premise equipment connected thereto |
PL347068A1 (en) * | 1998-09-15 | 2002-03-11 | In Touch Technologies Ltd | Communication services |
US6922562B2 (en) | 1998-09-24 | 2005-07-26 | Stephen L. Ward | System and method for providing information services to cellular roamers |
US7092696B1 (en) | 1998-10-13 | 2006-08-15 | Nortel Networks Limited | Accounting method and apparatus for communications network |
US6125391A (en) | 1998-10-16 | 2000-09-26 | Commerce One, Inc. | Market makers using documents for commerce in trading partner networks |
FI982748A (en) | 1998-10-19 | 2000-04-20 | Nokia Networks Oy | Billing in telecommunications networks |
US6286052B1 (en) | 1998-12-04 | 2001-09-04 | Cisco Technology, Inc. | Method and apparatus for identifying network data traffic flows and for applying quality of service treatments to the flows |
US7194554B1 (en) | 1998-12-08 | 2007-03-20 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization authentication and accounting |
US8713641B1 (en) | 1998-12-08 | 2014-04-29 | Nomadix, Inc. | Systems and methods for authorizing, authenticating and accounting users having transparent computer access to a network using a gateway device |
ES2299941T3 (en) | 1998-12-10 | 2008-06-01 | Nokia Corporation | METHOD FOR PERFORMING A SAFE DISCONNECTION PROCESS IN A RADIOTELECOMMUNICATIONS NETWORK. |
US6317584B1 (en) | 1998-12-21 | 2001-11-13 | Nortel Networks Limited | Controlling communication in wireless and satellite networks |
US7007295B1 (en) | 1998-12-24 | 2006-02-28 | B3D, Inc. | System and method for Internet streaming of 3D animated content |
US6658254B1 (en) | 1998-12-31 | 2003-12-02 | At&T Corp. | Method and apparatus for personalization of a public multimedia communications terminal |
US6570974B1 (en) | 1998-12-31 | 2003-05-27 | At&T Corp. | Cable connected network server platform for telephone white-yellow page services and emergency 911 location identification |
US7149229B1 (en) | 1999-01-08 | 2006-12-12 | Cisco Technology, Inc. | Mobile IP accounting |
US6184829B1 (en) | 1999-01-08 | 2001-02-06 | Trueposition, Inc. | Calibration for wireless location system |
US6654814B1 (en) | 1999-01-26 | 2003-11-25 | International Business Machines Corporation | Systems, methods and computer program products for dynamic placement of web content tailoring |
US6542992B1 (en) | 1999-01-26 | 2003-04-01 | 3Com Corporation | Control and coordination of encryption and compression between network entities |
US20010012346A1 (en) | 1999-01-29 | 2001-08-09 | Alex Terry | Interactive billing system utilizing a thin web client interface |
US6542490B1 (en) | 1999-01-29 | 2003-04-01 | Nortel Networks Limited | Data link control proctocol for 3G wireless system |
US8701015B2 (en) | 2008-03-26 | 2014-04-15 | Pierre Bonnat | Method and system for providing a user interface that enables control of a device via respiratory and/or tactual input |
US20020013852A1 (en) | 2000-03-03 | 2002-01-31 | Craig Janik | System for providing content, management, and interactivity for thin client devices |
US7082422B1 (en) | 1999-03-23 | 2006-07-25 | Microstrategy, Incorporated | System and method for automatic transmission of audible on-line analytical processing system report output |
JP2000295276A (en) | 1999-04-02 | 2000-10-20 | Hitachi Ltd | Communication control system |
US6535949B1 (en) | 1999-04-19 | 2003-03-18 | Research In Motion Limited | Portable electronic device having a log-structured file system in flash memory |
US6563809B1 (en) * | 1999-04-28 | 2003-05-13 | Tantivy Communications, Inc. | Subscriber-controlled registration technique in a CDMA system |
US6449479B1 (en) | 1999-04-30 | 2002-09-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatus and method for mobile subscriber service modification |
US6920455B1 (en) | 1999-05-19 | 2005-07-19 | Sun Microsystems, Inc. | Mechanism and method for managing service-specified data in a profile service |
US7356494B2 (en) | 1999-05-19 | 2008-04-08 | I.D. Systems, Inc. | Robust wireless communications system architecture and asset management applications performed thereon |
US7656271B2 (en) | 2002-01-09 | 2010-02-02 | I.D. Systems, Inc. | System and method for managing a remotely located asset |
AU5156800A (en) | 1999-05-24 | 2000-12-12 | Aprisma Management Technologies, Inc. | Service level management |
US6542465B1 (en) | 1999-05-28 | 2003-04-01 | 3Com Corporation | Method for flow control in asymmetric digital subscriber line devices |
AU5158800A (en) * | 1999-05-28 | 2000-12-18 | Basic Resources, Inc. | Wireless transceiver network employing node-to-node data messaging |
US8423648B2 (en) | 1999-06-01 | 2013-04-16 | Yodlee.Com, Inc. | Method and system for verifying state of a transaction between a client and a service over a data-packet-network |
US8046270B2 (en) | 2000-05-19 | 2011-10-25 | Eastman Kodak Company | System and method for providing image products and/or services |
US7523191B1 (en) | 2000-06-02 | 2009-04-21 | Yahoo! Inc. | System and method for monitoring user interaction with web pages |
US7882247B2 (en) | 1999-06-11 | 2011-02-01 | Netmotion Wireless, Inc. | Method and apparatus for providing secure connectivity in mobile and other intermittent computing environments |
US6631122B1 (en) | 1999-06-11 | 2003-10-07 | Nortel Networks Limited | Method and system for wireless QOS agent for all-IP network |
US7760137B2 (en) | 1999-06-18 | 2010-07-20 | Pfizer, Inc. | Portable position determining device |
US6804536B1 (en) | 1999-06-24 | 2004-10-12 | Parkervision, Inc. | Wireless communications interface |
US6765864B1 (en) | 1999-06-29 | 2004-07-20 | Cisco Technology, Inc. | Technique for providing dynamic modification of application specific policies in a feedback-based, adaptive data network |
US6466984B1 (en) | 1999-07-02 | 2002-10-15 | Cisco Technology, Inc. | Method and apparatus for policy-based management of quality of service treatments of network data traffic flows by integrating policies with application programs |
US6901440B1 (en) | 1999-07-02 | 2005-05-31 | Agilent Technologies, Inc. | System and method for universal service activation |
US6782412B2 (en) | 1999-08-24 | 2004-08-24 | Verizon Laboratories Inc. | Systems and methods for providing unified multimedia communication services |
US7171199B1 (en) * | 1999-09-10 | 2007-01-30 | Lucent Technologies Inc. | Method and system for directing a data message in a wireless communications network including multiple wireless systems |
US6757717B1 (en) | 1999-09-16 | 2004-06-29 | Proxyconn, Inc. | System and method for data access |
US6598034B1 (en) | 1999-09-21 | 2003-07-22 | Infineon Technologies North America Corp. | Rule based IP data processing |
US6982733B1 (en) | 1999-09-21 | 2006-01-03 | Ameranth Wireless, Inc. | Information management and synchronous communications system with menu generation, and handwriting and voice modification of orders |
US6640334B1 (en) | 1999-09-27 | 2003-10-28 | Nortel Networks Limited | Method and apparatus of remotely updating firmware of a communication device |
US7219123B1 (en) | 1999-10-08 | 2007-05-15 | At Road, Inc. | Portable browser device with adaptive personalization capability |
US7203721B1 (en) | 1999-10-08 | 2007-04-10 | At Road, Inc. | Portable browser device with voice recognition and feedback capability |
US6578076B1 (en) | 1999-10-18 | 2003-06-10 | Intel Corporation | Policy-based network management system using dynamic policy generation |
DE60033615T2 (en) | 1999-10-21 | 2007-10-31 | International Business Machines Corp. | Method and system to force the distribution of IP datagrams to multiple servers according to a defined strategy |
JP2003513538A (en) | 1999-10-22 | 2003-04-08 | アクティブスカイ,インコーポレイテッド | Object-oriented video system |
US6571221B1 (en) | 1999-11-03 | 2003-05-27 | Wayport, Inc. | Network communication service with an improved subscriber model using digital certificates |
IL149356A0 (en) | 1999-11-03 | 2002-11-10 | Wayport Inc | Distributed network communication system which enables multiple network providers to use a common distributed network infrastructure |
US6970927B1 (en) | 2000-04-18 | 2005-11-29 | Wayport, Inc. | Distributed network communication system which provides different network access features |
US6714987B1 (en) | 1999-11-05 | 2004-03-30 | Nortel Networks Limited | Architecture for an IP centric distributed network |
US7039713B1 (en) | 1999-11-09 | 2006-05-02 | Microsoft Corporation | System and method of user authentication for network communication through a policy agent |
US20020055351A1 (en) | 1999-11-12 | 2002-05-09 | Elsey Nicholas J. | Technique for providing personalized information and communications services |
US8032409B1 (en) | 1999-11-22 | 2011-10-04 | Accenture Global Services Limited | Enhanced visibility during installation management in a network-based supply chain environment |
US7130807B1 (en) | 1999-11-22 | 2006-10-31 | Accenture Llp | Technology sharing during demand and supply planning in a network-based supply chain environment |
US6606744B1 (en) | 1999-11-22 | 2003-08-12 | Accenture, Llp | Providing collaborative installation management in a network-based supply chain environment |
AU2021001A (en) | 1999-12-13 | 2001-06-18 | Markport Limited | A service management access node |
US6829696B1 (en) | 1999-12-30 | 2004-12-07 | Texas Instruments Incorporated | Data processing system with register store/load utilizing data packing/unpacking |
US6775267B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
US6694362B1 (en) | 2000-01-03 | 2004-02-17 | Micromuse Inc. | Method and system for network event impact analysis and correlation with network administrators, management policies and procedures |
US6748437B1 (en) | 2000-01-10 | 2004-06-08 | Sun Microsystems, Inc. | Method for creating forwarding lists for cluster networking |
US6735206B1 (en) | 2000-01-10 | 2004-05-11 | Sun Microsystems, Inc. | Method and apparatus for performing a fast service lookup in cluster networking |
EP1117265A1 (en) * | 2000-01-15 | 2001-07-18 | Telefonaktiebolaget Lm Ericsson | Method and apparatus for global roaming |
US6662014B1 (en) | 2000-02-04 | 2003-12-09 | Sbc Properties, L.P. | Location privacy manager for a wireless communication device and method therefor |
US6885997B1 (en) | 2000-02-16 | 2005-04-26 | Teligistics.Com | Apparatus and method for comparing rate plans on a net-net basis |
US7444669B1 (en) | 2000-05-05 | 2008-10-28 | Microsoft Corporation | Methods and systems for providing variable rates of service for accessing networks, methods and systems for accessing the internet |
CN1208731C (en) | 2000-02-22 | 2005-06-29 | 王迪兴 | Multipurpose platform for parallel operation, exchange and control |
US7266371B1 (en) | 2000-02-22 | 2007-09-04 | Cingular Wireless Ii, Llc | Activation and remote modification of wireless services in a packet network context |
JP4068780B2 (en) | 2000-02-24 | 2008-03-26 | 富士通株式会社 | COMMUNICATION STATUS NOTIFICATION DEVICE, COMMUNICATION STATUS DISPLAY DEVICE, COMMUNICATION STATUS NOTIFICATION METHOD, AND MEDIUM CONTAINING COMMUNICATION STATUS NOTIFICATION PROGRAM IN VoIP COMMUNICATION SYSTEM |
US7043225B1 (en) | 2000-02-25 | 2006-05-09 | Cisco Technology, Inc. | Method and system for brokering bandwidth in a wireless communications network |
US7200551B1 (en) | 2000-02-28 | 2007-04-03 | Telpay, Inc. | Automated bill payment system |
EP1260077B1 (en) | 2000-02-29 | 2005-04-13 | Swisscom Mobile AG | Transaction confirmation method, authentication server and wap server |
US20030236745A1 (en) | 2000-03-03 | 2003-12-25 | Hartsell Neal D | Systems and methods for billing in information management environments |
US20030046396A1 (en) | 2000-03-03 | 2003-03-06 | Richter Roger K. | Systems and methods for managing resource utilization in information management environments |
US20010044786A1 (en) | 2000-03-14 | 2001-11-22 | Yoshihito Ishibashi | Content usage management system and method, and program providing medium therefor |
US6697821B2 (en) | 2000-03-15 | 2004-02-24 | Süccesses.com, Inc. | Content development management system and method |
US6928280B1 (en) | 2000-03-20 | 2005-08-09 | Telephia, Inc. | Method and system for measuring data quality of service in a wireless network using multiple remote units and a back end processor |
CA2403736A1 (en) | 2000-03-20 | 2001-09-27 | At&T Corp. | Service selection in a shared access network using dynamic host configuration protocol |
US7260635B2 (en) | 2000-03-21 | 2007-08-21 | Centrisoft Corporation | Software, systems and methods for managing a distributed network |
US20020022483A1 (en) | 2000-04-18 | 2002-02-21 | Wayport, Inc. | Distributed network communication system which allows multiple wireless service providers to share a common network infrastructure |
US7502672B1 (en) | 2000-04-24 | 2009-03-10 | Usa Technologies, Inc. | Wireless vehicle diagnostics with service and part determination capabilities |
US7020781B1 (en) | 2000-05-03 | 2006-03-28 | Hewlett-Packard Development Company, L.P. | Digital content distribution systems |
US6829596B1 (en) | 2000-05-23 | 2004-12-07 | Steve Frazee | Account/asset activation device and method |
US6725036B1 (en) | 2000-05-30 | 2004-04-20 | Nokia Telecommunications Ojy | System and method of controlling application level access of a subscriber to a network |
US7423971B1 (en) | 2000-05-31 | 2008-09-09 | Cisco Technology, Inc. | Method and apparatus providing automatic RESV message generation for non-RESV-capable network devices |
US7551921B2 (en) | 2000-05-31 | 2009-06-23 | Wahoo Communications Corporation | Wireless communications system with parallel computing artificial intelligence-based distributive call routing |
US7395056B2 (en) | 2000-05-31 | 2008-07-01 | Wahoo Communications Corporation | Time-shared full duplex protocol for use with a wireless communications system with artificial intelligence-based distributive call routing |
US6438575B1 (en) | 2000-06-07 | 2002-08-20 | Clickmarks, Inc. | System, method, and article of manufacture for wireless enablement of the world wide web using a wireless gateway |
US8489669B2 (en) | 2000-06-07 | 2013-07-16 | Apple Inc. | Mobile data processing system moving interest radius |
EP1164266B1 (en) | 2000-06-13 | 2009-10-07 | Ford Global Technologies, Inc. | Method of optimizing reductant addition to an SCR catalyst coupled to an internal combustion engine |
US6785889B1 (en) | 2000-06-15 | 2004-08-31 | Aurema, Inc. | System and method for scheduling bandwidth resources using a Kalman estimator with active feedback |
US7017189B1 (en) | 2000-06-27 | 2006-03-21 | Microsoft Corporation | System and method for activating a rendering device in a multi-level rights-management architecture |
FI20001630A (en) | 2000-06-30 | 2001-12-31 | Nokia Mobile Phones Ltd | Determining quality of service for data streams |
US8380630B2 (en) | 2000-07-06 | 2013-02-19 | David Paul Felsher | Information record infrastructure, system and method |
US6751296B1 (en) | 2000-07-11 | 2004-06-15 | Motorola, Inc. | System and method for creating a transaction usage record |
US6725256B1 (en) | 2000-07-11 | 2004-04-20 | Motorola, Inc. | System and method for creating an e-mail usage record |
US7496652B2 (en) | 2000-07-17 | 2009-02-24 | Teleservices Solutions, Inc. | Intelligent network providing network access services (INP-NAS) |
DE10035348A1 (en) | 2000-07-20 | 2002-01-31 | Alcatel Sa | Method for providing a game for a subscriber's mobile radio terminal and program modules and means therefor |
EP1312201A4 (en) | 2000-07-21 | 2008-04-23 | Telemac Corp | A method and system for data rating for wireless devices |
US6725031B2 (en) | 2000-07-21 | 2004-04-20 | Telemac Corporation | Method and system for data rating for wireless devices |
US20020199001A1 (en) | 2001-02-25 | 2002-12-26 | Storymail, Inc. | System and method for conducting a secure response communication session |
US7849170B1 (en) | 2000-07-31 | 2010-12-07 | Sprint Communications Company L.P. | Dynamically providing communication accounts using a communication account system |
US6965872B1 (en) | 2000-08-02 | 2005-11-15 | Zipandshop Llc | Systems, methods and computer program products for facilitating the sale of commodity-like goods/services |
CN100372715C (en) | 2000-08-04 | 2008-03-05 | 都恩罗普空间技术有限公司 | Brake condition monitoring |
US7024200B2 (en) | 2000-08-14 | 2006-04-04 | Vesuvius, Inc. | Communique system with active feedback for cellular communication networks |
US6754470B2 (en) | 2000-09-01 | 2004-06-22 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
DE10043203A1 (en) | 2000-09-01 | 2002-03-21 | Siemens Ag | Generic WLAN architecture |
US6574465B2 (en) | 2000-09-07 | 2003-06-03 | Traq Wireless, Inc. | System and method for determining optimal wireless communication service plans |
US20020065083A1 (en) | 2000-09-07 | 2002-05-30 | Rajendra Patel | Method and system for high speed wireless data transmission and reception |
US20070192863A1 (en) | 2005-07-01 | 2007-08-16 | Harsh Kapoor | Systems and methods for processing data flows |
US8010469B2 (en) | 2000-09-25 | 2011-08-30 | Crossbeam Systems, Inc. | Systems and methods for processing data flows |
US6765925B1 (en) | 2000-09-28 | 2004-07-20 | Nortel Networks Limited | Apparatus and method of maintaining state in a data transmission system |
US6748195B1 (en) | 2000-09-29 | 2004-06-08 | Motorola, Inc. | Wireless device having context-based operational behavior |
US6522629B1 (en) | 2000-10-10 | 2003-02-18 | Tellicent Inc. | Traffic manager, gateway signaling and provisioning service for all packetized networks with total system-wide standards for broad-band applications including all legacy services |
US8078163B2 (en) | 2000-10-11 | 2011-12-13 | Gogo Llc | System for customizing electronic content for delivery to a passenger in an airborne wireless cellular network |
US8068829B2 (en) | 2000-10-11 | 2011-11-29 | Gogo Llc | System for customizing electronic services for delivery to a passenger in an airborne wireless cellular network |
US20020154751A1 (en) | 2000-10-18 | 2002-10-24 | Thompson Richard H. | Method for managing wireless communication device use including optimizing rate and service plan selection |
US6990472B2 (en) | 2000-10-23 | 2006-01-24 | Starpound Corporation | Telecommunications initiated data fulfillment system |
US6879825B1 (en) | 2000-11-01 | 2005-04-12 | At&T Wireless Services, Inc. | Method for programming a mobile station using a permanent mobile station identifier |
EP1338125A2 (en) | 2000-11-03 | 2003-08-27 | AT & T Corp. | Tiered contention multiple access (tcma): a method for priority-based shared channel access |
US7120133B1 (en) | 2000-11-03 | 2006-10-10 | Cisco Technology, Inc. | System and method of linking a wireless signaling protocol with a media gateway control protocol in a packet-based network |
US6591098B1 (en) | 2000-11-07 | 2003-07-08 | At&T Wireless Services, Inc. | System and method for using a temporary electronic serial number for over-the-air activation of a mobile device |
US7313825B2 (en) | 2000-11-13 | 2007-12-25 | Digital Doors, Inc. | Data security system and method for portable device |
US7657628B1 (en) | 2000-11-28 | 2010-02-02 | Verizon Business Global Llc | External processor for a distributed network access system |
US7177919B1 (en) | 2000-11-28 | 2007-02-13 | Cisco Technology, Inc. | Method and system for controlling tasks on network cards |
US7383191B1 (en) | 2000-11-28 | 2008-06-03 | International Business Machines Corporation | Method and system for predicting causes of network service outages using time domain correlation |
JP2002169806A (en) | 2000-12-01 | 2002-06-14 | Nec Corp | Service retrieval system |
KR100717941B1 (en) | 2000-12-05 | 2007-05-11 | 주식회사 케이티 | Method and Apparatus for Providing Measured rate system in IP Network |
US6961567B1 (en) | 2000-12-07 | 2005-11-01 | Palm, Inc. | Generic activation and registration framework for wireless devices |
US6944679B2 (en) | 2000-12-22 | 2005-09-13 | Microsoft Corp. | Context-aware systems and methods, location-aware systems and methods, context-aware vehicles and methods of operating the same, and location-aware vehicles and methods of operating the same |
EP1344353B1 (en) | 2000-12-22 | 2014-11-19 | BlackBerry Limited | Wireless router system and method |
WO2002052875A2 (en) | 2000-12-27 | 2002-07-04 | Ensemble Communications, Inc. | Adaptive call admission control for use in a wireless communication system |
US7039027B2 (en) | 2000-12-28 | 2006-05-02 | Symbol Technologies, Inc. | Automatic and seamless vertical roaming between wireless local area network (WLAN) and wireless wide area network (WWAN) while maintaining an active voice or streaming data connection: systems, methods and program products |
DE10065457B4 (en) * | 2000-12-28 | 2007-04-26 | Karl Marbach Gmbh & Co. Kg | Method and device for separating the use and waste of a stamped or cut sheet of material and plant for producing benefits from a sheet of material |
US6690918B2 (en) | 2001-01-05 | 2004-02-10 | Soundstarts, Inc. | Networking by matching profile information over a data packet-network and a local area network |
WO2002056152A2 (en) | 2001-01-10 | 2002-07-18 | Psionic Software Inc | Computer security and management system |
US6952428B1 (en) | 2001-01-26 | 2005-10-04 | 3Com Corporation | System and method for a specialized dynamic host configuration protocol proxy in a data-over-cable network |
EP1227449A1 (en) | 2001-01-30 | 2002-07-31 | Siemens Aktiengesellschaft | Method of billing for multi-media networks |
US7290283B2 (en) | 2001-01-31 | 2007-10-30 | Lancope, Inc. | Network port profiling |
US7184764B2 (en) | 2001-02-08 | 2007-02-27 | Starhome Gmbh | Method and apparatus for supporting cellular data communication to roaming mobile telephony devices |
FI111680B (en) | 2001-02-16 | 2003-08-29 | Sonera Oyj | Service-specific billing |
US7203752B2 (en) | 2001-02-16 | 2007-04-10 | Openwave Systems Inc. | Method and system for managing location information for wireless communications devices |
US8527410B2 (en) * | 2001-02-19 | 2013-09-03 | Nokia Corporation | Control of billing in a communications system |
US20020116338A1 (en) | 2001-02-22 | 2002-08-22 | Jean-Charles Gonthier | Prepaid access to internet protocol (IP) networks |
JP4139228B2 (en) | 2001-02-26 | 2008-08-27 | フォースパス インコーポレイテッド | Billing method and system based on application communication |
US6996062B1 (en) | 2001-02-28 | 2006-02-07 | 3Com Corporation | Policy-based weighted random early detection method for avoiding congestion in internet traffic |
US7027408B2 (en) * | 2001-03-05 | 2006-04-11 | Qwest Communications International, Inc | Method and system for dynamic service profile integration by a service controller |
US7016843B2 (en) | 2001-03-09 | 2006-03-21 | Bevocal, Inc. | System method and computer program product for transferring unregistered callers to a registration process |
US7539747B2 (en) * | 2001-03-14 | 2009-05-26 | Microsoft Corporation | Schema-based context service |
JP2002278839A (en) | 2001-03-15 | 2002-09-27 | Sony Corp | Data access managing system, memory packaged device, data access managing method and program storage medium |
US7406306B2 (en) | 2001-03-20 | 2008-07-29 | Verizon Business Global Llc | Method for billing in a telecommunications network |
US7058022B1 (en) | 2001-03-20 | 2006-06-06 | At&T Corp. | Method for managing access to networks by employing client software and a configuration protocol timeout |
US8402129B2 (en) | 2001-03-21 | 2013-03-19 | Alcatel Lucent | Method and apparatus for efficient reactive monitoring |
DE60116405T2 (en) | 2001-03-22 | 2006-09-07 | Nortel Networks Ltd., St. Laurent | Flexible customization of network services |
US7181017B1 (en) | 2001-03-23 | 2007-02-20 | David Felsher | System and method for secure three-party communications |
FI112426B (en) | 2001-03-23 | 2003-11-28 | Nixu Oy | Content server mediation server |
US7987510B2 (en) | 2001-03-28 | 2011-07-26 | Rovi Solutions Corporation | Self-protecting digital content |
JP2002300181A (en) | 2001-03-30 | 2002-10-11 | Nec Corp | INTEGRATED NETWORK QoS CONTROL SYSTEM |
US7269157B2 (en) | 2001-04-10 | 2007-09-11 | Internap Network Services Corporation | System and method to assure network service levels with intelligent routing |
US6970692B2 (en) | 2001-04-12 | 2005-11-29 | International Business Machines Corporation | Cell phone minute usage calculation and display |
US7363374B2 (en) | 2001-04-27 | 2008-04-22 | International Business Machines Corporation | Method and system for fault-tolerant remote boot in the presence of boot server overload/failure with self-throttling boot servers |
AUPR464601A0 (en) | 2001-04-30 | 2001-05-24 | Commonwealth Of Australia, The | Shapes vector |
CN100377027C (en) | 2001-05-14 | 2008-03-26 | 株式会社Ntt都科摩 | System for managing program |
US6714778B2 (en) | 2001-05-15 | 2004-03-30 | Nokia Corporation | Context sensitive web services |
US7024460B2 (en) | 2001-07-31 | 2006-04-04 | Bytemobile, Inc. | Service-based compression of content within a network communication system |
US20030182420A1 (en) | 2001-05-21 | 2003-09-25 | Kent Jones | Method, system and apparatus for monitoring and controlling internet site content access |
US20020176377A1 (en) | 2001-05-22 | 2002-11-28 | Hamilton Thomas E. | Service platform on wireless network |
US20020176378A1 (en) | 2001-05-22 | 2002-11-28 | Hamilton Thomas E. | Platform and method for providing wireless data services |
US7747699B2 (en) | 2001-05-30 | 2010-06-29 | Prueitt James K | Method and system for generating a permanent record of a service provided to a mobile device |
US20020188732A1 (en) | 2001-06-06 | 2002-12-12 | Buckman Charles R. | System and method for allocating bandwidth across a network |
US7653815B2 (en) | 2001-06-12 | 2010-01-26 | Research In Motion Limited | System and method for processing encoded messages for exchange with a mobile data communication device |
US7457265B2 (en) | 2001-06-13 | 2008-11-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Mobility management entity for high data rate wireless communication networks |
US20050198379A1 (en) | 2001-06-13 | 2005-09-08 | Citrix Systems, Inc. | Automatically reconnecting a client across reliable and persistent communication sessions |
US7010002B2 (en) | 2001-06-14 | 2006-03-07 | At&T Corp. | Broadband network with enterprise wireless communication method for residential and business environment |
US7756041B2 (en) | 2001-06-14 | 2010-07-13 | Meshnetworks, Inc. | Embedded routing algorithms under the internet protocol routing layer of a software architecture protocol stack in a mobile Ad-Hoc network |
US7002995B2 (en) | 2001-06-14 | 2006-02-21 | At&T Corp. | Broadband network with enterprise wireless communication system for residential and business environment |
US7191115B2 (en) | 2001-06-20 | 2007-03-13 | Microsoft Corporation | Statistical method and apparatus for learning translation relationships among words |
US7467160B2 (en) | 2001-06-26 | 2008-12-16 | Eastman Kodak Company | Method and system for managing images over a communication network using user provided instructions |
WO2003003235A1 (en) | 2001-06-27 | 2003-01-09 | 4 Media, Inc. | Improved media delivery platform |
US7315892B2 (en) | 2001-06-27 | 2008-01-01 | International Business Machines Corporation | In-kernel content-aware service differentiation |
US7136361B2 (en) | 2001-07-05 | 2006-11-14 | At&T Corp. | Hybrid coordination function (HCF) access through tiered contention and overlapped wireless cell mitigation |
US20040107360A1 (en) | 2002-12-02 | 2004-06-03 | Zone Labs, Inc. | System and Methodology for Policy Enforcement |
US8200818B2 (en) | 2001-07-06 | 2012-06-12 | Check Point Software Technologies, Inc. | System providing internet access management with router-based policy enforcement |
US6873988B2 (en) | 2001-07-06 | 2005-03-29 | Check Point Software Technologies, Inc. | System and methods providing anti-virus cooperative enforcement |
US7546629B2 (en) | 2002-03-06 | 2009-06-09 | Check Point Software Technologies, Inc. | System and methodology for security policy arbitration |
US7117504B2 (en) | 2001-07-10 | 2006-10-03 | Microsoft Corporation | Application program interface that enables communication for a network software platform |
US7017162B2 (en) | 2001-07-10 | 2006-03-21 | Microsoft Corporation | Application program interface for network software platform |
US6628934B2 (en) | 2001-07-12 | 2003-09-30 | Earthlink, Inc. | Systems and methods for automatically provisioning wireless services on a wireless device |
US20030018524A1 (en) | 2001-07-17 | 2003-01-23 | Dan Fishman | Method for marketing and selling products to a user of a wireless device |
WO2003015352A1 (en) | 2001-08-01 | 2003-02-20 | Nokia Corporation | Apparatus and method for flow scheduling based on priorities in a mobile network |
US7715819B2 (en) | 2001-08-03 | 2010-05-11 | The Boeing Company | Airborne security manager |
WO2003015341A2 (en) | 2001-08-04 | 2003-02-20 | Kontiki, Inc. | Method and apparatus for facilitating secure distributed content delivery across a computer network |
US7962622B2 (en) | 2001-08-07 | 2011-06-14 | Motorola Mobility, Inc. | System and method for providing provisioning and upgrade services for a wireless device |
US7170857B2 (en) * | 2001-08-10 | 2007-01-30 | Strix Systems, Inc. | Virtual linking using a wireless device |
US7389412B2 (en) | 2001-08-10 | 2008-06-17 | Interactive Technology Limited Of Hk | System and method for secure network roaming |
US7039037B2 (en) | 2001-08-20 | 2006-05-02 | Wang Jiwei R | Method and apparatus for providing service selection, redirection and managing of subscriber access to multiple WAP (Wireless Application Protocol) gateways simultaneously |
AU2002332604A1 (en) | 2001-08-21 | 2003-03-03 | Apogee Networks | Content ownership resolution |
AU2002332599A1 (en) | 2001-08-21 | 2003-03-03 | Apogee Networks | Settlement of transactions subject to multiple pricing plans |
US7310424B2 (en) | 2001-08-22 | 2007-12-18 | General Atomics | Encryption key distribution and network registration system, apparatus and method |
EP1289326A1 (en) | 2001-08-30 | 2003-03-05 | Motorola, Inc. | Method of verifying downloaded software and corresponding device |
US6996393B2 (en) * | 2001-08-31 | 2006-02-07 | Nokia Corporation | Mobile content delivery system |
US6842628B1 (en) | 2001-08-31 | 2005-01-11 | Palmone, Inc. | Method and system for event notification for wireless PDA devices |
TW535066B (en) | 2001-09-14 | 2003-06-01 | Inventec Tomorrow Studio Corp | Method for sharing data between cable platform and wireless platform and system thereof |
CA2357382A1 (en) | 2001-09-17 | 2003-03-17 | Soma Networks, Inc. | Software update method, apparatus and system |
US7248570B2 (en) | 2001-09-17 | 2007-07-24 | Microsoft Corporation | System and method for coordinating bandwidth usage of a communication channel by wireless network nodes |
US7133695B2 (en) | 2001-09-26 | 2006-11-07 | Siemens Communications, Inc. | System and method for automatic mobile device activation |
AU2002343424A1 (en) | 2001-09-28 | 2003-04-14 | Bluesocket, Inc. | Method and system for managing data traffic in wireless networks |
US8977284B2 (en) | 2001-10-04 | 2015-03-10 | Traxcell Technologies, LLC | Machine for providing a dynamic data base of geographic location information for a plurality of wireless devices and process for making same |
US8020201B2 (en) | 2001-10-23 | 2011-09-13 | Intel Corporation | Selecting a security format conversion for wired and wireless devices |
ATE375671T1 (en) | 2001-10-24 | 2007-10-15 | Siemens Ag | METHOD AND DEVICE FOR AUTHENTICATED ACCESS OF A STATION TO LOCAL DATA NETWORKS, IN PARTICULAR RADIO DATA NETWORKS |
US7039403B2 (en) | 2001-10-26 | 2006-05-02 | Wong Gregory A | Method and apparatus to manage a resource |
US20030084321A1 (en) | 2001-10-31 | 2003-05-01 | Tarquini Richard Paul | Node and mobile device for a mobile telecommunications network providing intrusion detection |
US7151764B1 (en) | 2001-11-01 | 2006-12-19 | Nokia Corporation | Service notification on a low bluetooth layer |
US7222190B2 (en) | 2001-11-02 | 2007-05-22 | Internap Network Services Corporation | System and method to provide routing control of information over data networks |
US7668966B2 (en) | 2001-11-02 | 2010-02-23 | Internap Network Services Corporation | Data network controller |
CN1345154A (en) | 2001-11-08 | 2002-04-17 | 大唐微电子技术有限公司 | Air download method of increment business of user identifying module |
US8819253B2 (en) | 2001-11-13 | 2014-08-26 | Oracle America, Inc. | Network message generation for automated authentication |
US7224968B2 (en) | 2001-11-23 | 2007-05-29 | Actix Limited | Network testing and monitoring systems |
US6983370B2 (en) | 2001-11-27 | 2006-01-03 | Motorola, Inc. | System for providing continuity between messaging clients and method therefor |
US7272113B2 (en) | 2001-12-05 | 2007-09-18 | Nokia Corporation | Apparatus, and associated method, for communicating frame-formatted data at a selected QoS level in a radio communication system |
US6947985B2 (en) | 2001-12-05 | 2005-09-20 | Websense, Inc. | Filtering techniques for managing access to internet sites or other software applications |
US7797204B2 (en) | 2001-12-08 | 2010-09-14 | Balent Bruce F | Distributed personal automation and shopping method, apparatus, and process |
US7580972B2 (en) | 2001-12-12 | 2009-08-25 | Valve Corporation | Method and system for controlling bandwidth on client and server |
US7373179B2 (en) | 2001-12-13 | 2008-05-13 | At&T Mobility Ii Llc | Call queue in a wireless device |
US20030217096A1 (en) | 2001-12-14 | 2003-11-20 | Mckelvie Samuel J. | Agent based application using data synchronization |
KR20040071200A (en) | 2001-12-15 | 2004-08-11 | 톰슨 라이센싱 소시에떼 아노님 | Videoconference bandwidth selection mechanism |
US7328266B2 (en) | 2001-12-18 | 2008-02-05 | Perftech, Inc. | Internet provider subscriber communications system |
US7203169B1 (en) | 2001-12-20 | 2007-04-10 | Packeteer, Inc. | Interface facilitating configuration of network resource utilization |
US8347104B2 (en) | 2001-12-26 | 2013-01-01 | Research In Motion Limited | Security interface for a mobile device |
US7032072B1 (en) | 2001-12-31 | 2006-04-18 | Packeteer, Inc. | Method and apparatus for fast lookup of related classification entities in a tree-ordered classification hierarchy |
US7149521B2 (en) | 2002-01-02 | 2006-12-12 | Winphoria Networks, Inc. | Method, system and apparatus for providing mobility management of a mobile station in WLAN and WWAN environments |
US20030134650A1 (en) | 2002-01-17 | 2003-07-17 | Rangamani Sundar | Method, system and apparatus for internetworking a mobile station to operate in a WWAN environment and in a WLAN environment with PBX services |
US7200112B2 (en) | 2002-01-02 | 2007-04-03 | Winphoria Networks, Inc. | Method, system, and apparatus for a mobile station to sense and select a wireless local area network (WLAN) or a wide area mobile wireless network (WWAN) |
US7873985B2 (en) | 2002-01-08 | 2011-01-18 | Verizon Services Corp. | IP based security applications using location, port and/or device identifier information |
WO2003058483A1 (en) | 2002-01-08 | 2003-07-17 | Seven Networks, Inc. | Connection architecture for a mobile network |
SE519072C2 (en) | 2002-01-10 | 2003-01-07 | Telia Ab | Method of access control in mobile communications |
US7206401B2 (en) | 2002-01-11 | 2007-04-17 | Freeny Jr Charles C | Remote PBX system and advanced communication terminals |
US7043237B2 (en) * | 2002-01-14 | 2006-05-09 | Agilent Technologies, Inc. | Method and system for improved monitoring, measurement and analysis of communication networks utilizing dynamically and remotely configurable probes |
US6947723B1 (en) | 2002-01-14 | 2005-09-20 | Cellco Partnership | Postpay spending limit using a cellular network usage governor |
US7450927B1 (en) | 2002-01-23 | 2008-11-11 | At&T Corp. | Interactive communication service account management system |
US7610328B2 (en) | 2002-01-23 | 2009-10-27 | Alcatel-Lucent Usa Inc. | Methods and apparatus for a multi-technology subscriber base for global roaming |
CN1204722C (en) | 2002-01-26 | 2005-06-01 | 深圳市朗科科技有限公司 | Wireless data communication method and device for data processing system |
US7689225B2 (en) | 2002-01-28 | 2010-03-30 | Ntt Docomo, Inc. | Method and apparatus for dormant mode support with paging |
US7508799B2 (en) | 2002-01-29 | 2009-03-24 | Arch Wireless Operating Company, Inc. | Managing wireless network data |
US10031885B2 (en) * | 2010-02-01 | 2018-07-24 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US20030159030A1 (en) | 2002-02-15 | 2003-08-21 | Imetrikus, Inc. | Method and system for the secure transmission of a portion of a web page over a computer network |
US20030161265A1 (en) | 2002-02-25 | 2003-08-28 | Jingjun Cao | System for end user monitoring of network service conditions across heterogeneous networks |
US8310943B2 (en) | 2002-02-26 | 2012-11-13 | Motorola Mobility Llc | Method and system for transmission-based billing applications |
US7493659B1 (en) * | 2002-03-05 | 2009-02-17 | Mcafee, Inc. | Network intrusion detection and analysis system and method |
US7916322B2 (en) | 2002-03-14 | 2011-03-29 | Senshin Capital, Llc | Method and apparatus for uploading content from a device to a remote network location |
US7283468B1 (en) | 2002-03-15 | 2007-10-16 | Packeteer, Inc. | Method and system for controlling network traffic within the same connection with different packet tags by varying the policies applied to a connection |
US7596373B2 (en) | 2002-03-21 | 2009-09-29 | Mcgregor Christopher M | Method and system for quality of service (QoS) monitoring for wireless devices |
US7028097B2 (en) | 2002-03-28 | 2006-04-11 | Intel Corporation | Wireless LAN with dynamic channel access management |
US7068600B2 (en) | 2002-04-29 | 2006-06-27 | Harris Corporation | Traffic policing in a mobile ad hoc network |
US6990996B2 (en) * | 2002-04-29 | 2006-01-31 | Sonnax Industries, Inc. | Torque converter clutch regulator valve assembly and method of installation |
US6959393B2 (en) | 2002-04-30 | 2005-10-25 | Threat Guard, Inc. | System and method for secure message-oriented network communications |
US7221945B2 (en) | 2002-05-03 | 2007-05-22 | Leapstone Systems, Inc. | System and method for establishing and controlling access to network resources |
US7899915B2 (en) | 2002-05-10 | 2011-03-01 | Richard Reisman | Method and apparatus for browsing using multiple coordinated device sets |
US7788700B1 (en) | 2002-05-15 | 2010-08-31 | Gerard A. Gagliano | Enterprise security system |
US8611919B2 (en) * | 2002-05-23 | 2013-12-17 | Wounder Gmbh., Llc | System, method, and computer program product for providing location based services and mobile e-commerce |
AU2003247428A1 (en) | 2002-05-28 | 2003-12-12 | Zte San Diego, Inc. | Interworking mechanism between cdma2000 and wlan |
US7965693B2 (en) | 2002-05-28 | 2011-06-21 | Zte (Usa) Inc. | Interworking mechanism between wireless wide area network and wireless local area network |
US20030233580A1 (en) | 2002-05-29 | 2003-12-18 | Keeler James D. | Authorization and authentication of user access to a distributed network communication system with roaming features |
US6965667B2 (en) | 2002-05-30 | 2005-11-15 | Slingshot Communications, Inc. | Method of accounting prepaid online internet service credit values |
US7512128B2 (en) | 2002-06-12 | 2009-03-31 | Sun Microsystems, Inc. | System and method for a multi-packet data link layer data transmission |
US7747730B1 (en) | 2002-06-28 | 2010-06-29 | Netfuel, Inc. | Managing computer network resources |
US7228354B2 (en) | 2002-06-28 | 2007-06-05 | International Business Machines Corporation | Method for improving performance in a computer storage system by regulating resource requests from clients |
US7636320B1 (en) | 2002-06-28 | 2009-12-22 | At&T Intellectual Property I, L.P. | System and method for creating an asynchronous transfer mode port mirror |
US20040203681A1 (en) | 2002-07-01 | 2004-10-14 | Ross David J. | Application catalog on an application server for wireless devices |
JP4221698B2 (en) | 2002-07-03 | 2009-02-12 | 日本電気株式会社 | Data transfer system and its base station |
US7693720B2 (en) | 2002-07-15 | 2010-04-06 | Voicebox Technologies, Inc. | Mobile systems and methods for responding to natural language speech utterance |
US7627872B2 (en) | 2002-07-26 | 2009-12-01 | Arbitron Inc. | Media data usage measurement and reporting systems and methods |
US7162237B1 (en) | 2002-07-26 | 2007-01-09 | Bellsouth Intellectual Property Corporation | System for automatic selection of profile based on location |
US8528068B1 (en) | 2002-07-26 | 2013-09-03 | Purple Communications, Inc. | Method of authenticating a user on a network |
US20040019564A1 (en) | 2002-07-26 | 2004-01-29 | Scott Goldthwaite | System and method for payment transaction authentication |
US20040127256A1 (en) | 2002-07-30 | 2004-07-01 | Scott Goldthwaite | Mobile device equipped with a contactless smart card reader/writer |
US7805606B2 (en) | 2002-07-29 | 2010-09-28 | Bea Systems, Inc. | Computer system for authenticating a computing device |
US6763226B1 (en) | 2002-07-31 | 2004-07-13 | Computer Science Central, Inc. | Multifunctional world wide walkie talkie, a tri-frequency cellular-satellite wireless instant messenger computer and network for establishing global wireless volp quality of service (qos) communications, unified messaging, and video conferencing via the internet |
US7133669B2 (en) | 2002-08-02 | 2006-11-07 | Pctel, Inc. | Systems and methods for seamless roaming between wireless networks |
US20040024756A1 (en) | 2002-08-05 | 2004-02-05 | John Terrell Rickard | Search engine for non-textual data |
US7606560B2 (en) | 2002-08-08 | 2009-10-20 | Fujitsu Limited | Authentication services using mobile device |
US6961595B2 (en) | 2002-08-08 | 2005-11-01 | Flarion Technologies, Inc. | Methods and apparatus for operating mobile nodes in multiple states |
SE0202450D0 (en) | 2002-08-15 | 2002-08-15 | Ericsson Telefon Ab L M | Non-repudiation of digital content |
DE10239061A1 (en) | 2002-08-26 | 2004-03-11 | Siemens Ag | Method for transferring user data objects |
US20040098715A1 (en) | 2002-08-30 | 2004-05-20 | Parixit Aghera | Over the air mobile device software management |
US6882718B1 (en) | 2002-09-06 | 2005-04-19 | Bellsouth Intellectual Property Corp. | Real time customer service data manipulation to allow multiple services per trigger type |
US7272660B1 (en) | 2002-09-06 | 2007-09-18 | Oracle International Corporation | Architecture for general purpose near real-time business intelligence system and methods therefor |
US7680086B2 (en) | 2002-09-09 | 2010-03-16 | Siemens Canada Limited | Wireless local area network with clients having extended freedom of movement |
US7512810B1 (en) | 2002-09-11 | 2009-03-31 | Guardian Data Storage Llc | Method and system for protecting encrypted files transmitted over a network |
US20040133668A1 (en) | 2002-09-12 | 2004-07-08 | Broadcom Corporation | Seamlessly networked end user device |
JP4309629B2 (en) | 2002-09-13 | 2009-08-05 | 株式会社日立製作所 | Network system |
US7665125B2 (en) | 2002-09-23 | 2010-02-16 | Heard Robert W | System and method for distribution of security policies for mobile devices |
EP1547303A4 (en) | 2002-09-23 | 2009-09-02 | Credant Technologies Inc | Server, computer memory, and method to support security policy maintenance and distribution |
US6957067B1 (en) | 2002-09-24 | 2005-10-18 | Aruba Networks | System and method for monitoring and enforcing policy within a wireless network |
US7110753B2 (en) | 2002-09-26 | 2006-09-19 | Siemens Communications, Inc. | Remotely controllable wireless device |
US7401338B1 (en) | 2002-09-27 | 2008-07-15 | Symantec Operating Corporation | System and method for an access layer application programming interface for managing heterogeneous components of a storage area network |
EP1550331A1 (en) | 2002-09-27 | 2005-07-06 | Axesstel, Inc. | Multimode phone including two wireless modems and a modem processor |
US6920320B2 (en) | 2002-09-30 | 2005-07-19 | Lucent Technologies Inc. | Method and apparatus for stable call preservation |
US7440573B2 (en) | 2002-10-08 | 2008-10-21 | Broadcom Corporation | Enterprise wireless local area network switching system |
US7574731B2 (en) * | 2002-10-08 | 2009-08-11 | Koolspan, Inc. | Self-managed network access using localized access management |
US7391724B2 (en) | 2002-10-09 | 2008-06-24 | Spyder Navigations, L.L.C. | System and method with policy control function for multimedia broadcast/multicast system services |
US7221929B2 (en) | 2002-10-12 | 2007-05-22 | Lg Electronics Inc. | Handling charging information in interworking structure of mobile communication and wireless local area networks |
US20040073361A1 (en) | 2002-10-15 | 2004-04-15 | Assimakis Tzamaloukas | Enhanced mobile communication device, and transportation application thereof |
WO2004036825A1 (en) | 2002-10-15 | 2004-04-29 | Telefonaktiebolaget Lm Ericsson (Publ) | System for providing flexible charging in a network |
US7640008B2 (en) | 2002-10-18 | 2009-12-29 | Kineto Wireless, Inc. | Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system |
US7885644B2 (en) * | 2002-10-18 | 2011-02-08 | Kineto Wireless, Inc. | Method and system of providing landline equivalent location information over an integrated communication system |
US7349698B2 (en) | 2002-10-18 | 2008-03-25 | Kineto Wireless, Inc. | Registration messaging in an unlicensed mobile access telecommunications system |
US7031733B2 (en) | 2002-10-25 | 2006-04-18 | Siemens Communications, Inc. | Online short message service (SMS) monitoring tool |
SE0203188D0 (en) | 2002-10-29 | 2002-10-29 | Ericsson Telefon Ab L M | Automatic provisioning including MMS greeting |
US7548746B2 (en) | 2002-11-01 | 2009-06-16 | At&T Mobility Ii Llc | General purpose automated activation and provisioning technologies |
US7242668B2 (en) | 2002-11-07 | 2007-07-10 | Alcatel Lucent | Network monitoring system responsive to changes in packet arrival variance and mean |
US20040103193A1 (en) | 2002-11-08 | 2004-05-27 | Pandya Suketu J. | Response time and resource consumption management in a distributed network environment |
AU2003280873A1 (en) | 2002-11-13 | 2004-06-03 | Ktfreetel Co., Ltd. | Apparatus for analyzing the packet data on mobile communication network and method thereof |
US7133386B2 (en) | 2002-11-18 | 2006-11-07 | Cisco Technology, Inc. | Method and system for service portability across disjoint wireless networks |
US7574509B2 (en) | 2002-11-25 | 2009-08-11 | Fisher-Rosemount Systems, Inc. | Interactive two-way collaboration in process control plants |
US6934751B2 (en) | 2002-11-29 | 2005-08-23 | Motorola, Inc. | Method and device for providing more accurate subscriber device billing |
US8005726B1 (en) | 2002-12-03 | 2011-08-23 | Verizon Data Services Llc | Method and system for interactive rate plan recommender |
AU2003300900A1 (en) | 2002-12-13 | 2004-07-09 | Internap Network Services Corporation | Topology aware route control |
CN1508734A (en) | 2002-12-13 | 2004-06-30 | 华人创意股份有限公司 | Method and system for providing information for supporting operation development of small-medium enterprises |
KR100483021B1 (en) | 2002-12-16 | 2005-04-15 | 한국전자통신연구원 | system for linking of wireless and cellular network and method thereof, its program storing recording medium |
US7353533B2 (en) | 2002-12-18 | 2008-04-01 | Novell, Inc. | Administration of protection of data accessible by a mobile device |
US7526800B2 (en) | 2003-02-28 | 2009-04-28 | Novell, Inc. | Administration of protection of data accessible by a mobile device |
US7356011B1 (en) | 2002-12-18 | 2008-04-08 | Mayfield Xi | Simplified configuration and security for networked wireless devices |
US7280818B2 (en) | 2004-05-28 | 2007-10-09 | At&T Mobility Ii Llc | Mobile device notification with opinions |
US7430602B2 (en) | 2002-12-20 | 2008-09-30 | Qualcomm Incorporated | Dynamically provisioned mobile station and method therefor |
US7802724B1 (en) | 2002-12-20 | 2010-09-28 | Steven Paul Nohr | Identifications and communications methods |
US7102620B2 (en) | 2002-12-24 | 2006-09-05 | Sierra Wireless, Inc. | Mobile electronic device |
US20040127200A1 (en) | 2002-12-31 | 2004-07-01 | Shaw Venson M. | Delivery of network services |
US20040181692A1 (en) | 2003-01-13 | 2004-09-16 | Johanna Wild | Method and apparatus for providing network service information to a mobile station by a wireless local area network |
WO2004066091A2 (en) | 2003-01-21 | 2004-08-05 | Bitfone Corporation | Update system capable of updating software across multiple flash chips |
US7295119B2 (en) | 2003-01-22 | 2007-11-13 | Wireless Valley Communications, Inc. | System and method for indicating the presence or physical location of persons or devices in a site specific representation of a physical environment |
US8149823B2 (en) | 2003-01-27 | 2012-04-03 | At&T Intellectual Property I, L.P. | Computer telephony integration (CTI) systems and methods for enhancing school safety |
US20040225898A1 (en) | 2003-01-28 | 2004-11-11 | Frost D. Gabriel | System and method for ubiquitous network access |
US6839343B2 (en) * | 2003-01-30 | 2005-01-04 | Pedestal Networks, Inc. | Physical layer router system and method |
US7363009B2 (en) | 2003-02-03 | 2008-04-22 | Qualcomm Incorporated | Method and apparatus for determining propagation delays for use in wide area networks |
US7573862B2 (en) | 2003-02-06 | 2009-08-11 | Mahdi Chambers | System and method for optimizing network capacity in a cellular wireless network |
CA2515819C (en) | 2003-02-13 | 2011-04-12 | Research In Motion Limited | Methods and apparatus for providing manual selection of a communication network for a mobile station |
US7505769B2 (en) | 2003-08-13 | 2009-03-17 | Roamware Inc. | Signaling gateway with multiple IMSI with multiple MSISDN (MIMM) service in a single SIM for multiple roaming partners |
US7577431B2 (en) | 2003-02-18 | 2009-08-18 | Roamware, Inc. | Providing multiple MSISDN numbers in a mobile device with a single IMSI |
WO2004075579A2 (en) | 2003-02-14 | 2004-09-02 | Roamware, Inc. | Signaling and packet relay method and system including general packet radio service (“gprs”) |
US7088237B2 (en) | 2003-02-14 | 2006-08-08 | Qualcomm Incorporated | Enhanced user privacy for mobile station location services |
US20040168052A1 (en) | 2003-02-25 | 2004-08-26 | Clisham Allister B. | Electronic content communication system and method |
US8949382B2 (en) | 2003-02-26 | 2015-02-03 | Siemens Industry, Inc. | Systems, devices, and methods for network wizards |
US6944144B2 (en) | 2003-02-28 | 2005-09-13 | Microsoft Corporation | Vertical roaming in wireless networks through improved quality of service measures |
US20080109679A1 (en) | 2003-02-28 | 2008-05-08 | Michael Wright | Administration of protection of data accessible by a mobile device |
US7142876B2 (en) | 2003-03-03 | 2006-11-28 | Nokia Corporation | Location dependent services |
US7720960B2 (en) | 2003-03-04 | 2010-05-18 | Cisco Technology, Inc. | Method and apparatus providing prepaid billing for network services using explicit service authorization in an access server |
US7444425B2 (en) | 2003-03-10 | 2008-10-28 | Meetrix, Inc. | Applying multicast protocols and VPN tunneling techniques to achieve high quality of service for real time media transport across IP networks |
GB2399712A (en) | 2003-03-17 | 2004-09-22 | Orange Personal Comm Serv Ltd | Telecommunications apparatus and method for multiple data type packets |
JP4145805B2 (en) | 2003-03-17 | 2008-09-03 | セイコーエプソン株式会社 | Template generation system, layout system, template generation program, layout program, template generation method, and layout method |
US7428750B1 (en) | 2003-03-24 | 2008-09-23 | Microsoft Corporation | Managing multiple user identities in authentication environments |
US7536695B2 (en) | 2003-03-28 | 2009-05-19 | Microsoft Corporation | Architecture and system for location awareness |
FR2853109B1 (en) | 2003-03-28 | 2005-06-24 | Cit Alcatel | LOCAL INSURANCE MANAGEMENT DEVICE FOR COMMUNICATIONS NETWORK EQUIPMENT |
US8019321B2 (en) | 2003-03-31 | 2011-09-13 | Varia Holdings Llc | Wireless mobile phone with authenticated mode of operation including heart beat profile based authentication |
US7477892B2 (en) | 2003-04-02 | 2009-01-13 | Sun Microsystems, Inc. | System and method for advanced service interaction |
SE0301053D0 (en) | 2003-04-07 | 2003-04-07 | Ericsson Telefon Ab L M | Method and system in a communications network |
US7930553B2 (en) | 2003-04-11 | 2011-04-19 | Intel Corporation | System and method for extending secure authentication using unique session keys derived from entropy generated by authentication method |
US20040203755A1 (en) | 2003-04-11 | 2004-10-14 | Jeffrey Brunet | Mobile care framework |
CN100417168C (en) | 2003-04-15 | 2008-09-03 | 中兴通讯股份有限公司 | Broadband public telephone system and its realizing method |
US20040209610A1 (en) | 2003-04-17 | 2004-10-21 | Adwankar Sandeep M. | Method and apparatus for managing wireless terminals |
US20040255008A1 (en) | 2003-04-21 | 2004-12-16 | International Business Machines Corporation | System for low power operation of wireless LAN |
US7724716B2 (en) | 2006-06-20 | 2010-05-25 | Apple Inc. | Wireless communication system |
US20040255145A1 (en) | 2003-05-06 | 2004-12-16 | Jerry Chow | Memory protection systems and methods for writable memory |
US7127232B2 (en) | 2003-05-08 | 2006-10-24 | Bell South Intellectual Property Corporation | Multiple access internet portal revenue sharing |
US20040225561A1 (en) * | 2003-05-09 | 2004-11-11 | Todd Hertzberg | Method for handling a subscription of a communication device |
US8174970B2 (en) | 2003-05-15 | 2012-05-08 | At&T Intellectual Property I, L.P. | Methods of implementing dynamic QoS and/or bandwidth provisioning and related data networks, data service providers, routing gateways, and computer program products |
US7617516B2 (en) | 2003-05-15 | 2009-11-10 | At&T Intellectual Property I, L.P. | Methods and systems for providing video on demand over a communication network using managed quality of service, bandwidth allocation and/or user profiles |
US7480254B2 (en) | 2003-05-28 | 2009-01-20 | Nokia Corporation | System, apparatus, and method for providing multi-application support using a single protocol stack |
US20040249918A1 (en) | 2003-06-05 | 2004-12-09 | Newisys, Inc. | Facilitating replication of a service processor configuration |
US8457082B2 (en) | 2003-06-06 | 2013-06-04 | At&T Intellectual Property I, L.P. | System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed/unregulated spectrum |
US7685254B2 (en) * | 2003-06-10 | 2010-03-23 | Pandya Ashish A | Runtime adaptable search processor |
US7209664B1 (en) | 2003-06-10 | 2007-04-24 | Nortel Networks Limited | Frequency agile transmitter and receiver architecture for DWDM systems |
AU2004247256B2 (en) | 2003-06-12 | 2010-08-12 | Camiant, Inc. | Dynamic service delivery with topology discovery for communication networks |
US7437458B1 (en) | 2003-06-13 | 2008-10-14 | Juniper Networks, Inc. | Systems and methods for providing quality assurance |
US7721296B2 (en) | 2003-06-13 | 2010-05-18 | Ericsson Ab | Event based charging in a communications system |
WO2004112344A2 (en) | 2003-06-13 | 2004-12-23 | Sap Aktiengesellschaft | Data processing system |
US20040260766A1 (en) | 2003-06-18 | 2004-12-23 | Barros Mark A. | System for location based internet access and method therefore |
US7103351B2 (en) | 2003-06-23 | 2006-09-05 | July Systems Inc. | Policy service system and methodology |
CN101159566B (en) | 2003-06-25 | 2011-05-04 | 华为技术有限公司 | Content charging method and system of data traffic |
US7899174B1 (en) | 2003-06-26 | 2011-03-01 | Nortel Networks Limited | Emergency services for packet networks |
US8352360B2 (en) | 2003-06-30 | 2013-01-08 | Toshiba Global Commerce Solutions Holdings Corporation | Method and system for secured transactions over a wireless network |
US20040267872A1 (en) | 2003-06-30 | 2004-12-30 | Serdy Frank Stephen | Provisioning interface |
EP1494387B1 (en) * | 2003-06-30 | 2008-05-07 | Research In Motion Limited | Processing radio modem commands during network data sessions |
JP2007535718A (en) | 2003-07-07 | 2007-12-06 | クリプターグラフィー リサーチ インコーポレイテッド | Reprogrammable security to regulate piracy and enable interactive content |
US8325906B2 (en) | 2003-07-14 | 2012-12-04 | Cisco Technology, Inc. | Class-based call request routing |
SG120939A1 (en) | 2003-07-21 | 2006-04-26 | Starhub Ltd | Roaming control panel |
US7236780B2 (en) | 2003-07-21 | 2007-06-26 | Lucent Technologies Inc. | Method for changing mobile subscriber service plan |
KR100546349B1 (en) * | 2003-07-23 | 2006-01-26 | 삼성전자주식회사 | Apparatus and method for compensating disc eccentricity in optical disc servo system |
US7526541B2 (en) | 2003-07-29 | 2009-04-28 | Enterasys Networks, Inc. | System and method for dynamic network policy management |
US20090048723A1 (en) * | 2003-07-31 | 2009-02-19 | The Boeing Company | Proactive optical wind shear protection and ride quality improvement system |
US8200775B2 (en) | 2005-02-01 | 2012-06-12 | Newsilike Media Group, Inc | Enhanced syndication |
EP1503548A1 (en) | 2003-08-01 | 2005-02-02 | fg microtec GmbH | Distributed Quality of Service Management System |
US7466652B2 (en) | 2003-08-14 | 2008-12-16 | Telcordia Technologies, Inc. | Auto-IP traffic optimization in mobile telecommunications systems |
GB0319359D0 (en) | 2003-08-18 | 2003-09-17 | Nokia Corp | Activation of communication sessions in a communication system |
US7191248B2 (en) | 2003-08-29 | 2007-03-13 | Microsoft Corporation | Communication stack for network communication and routing |
US7707320B2 (en) * | 2003-09-05 | 2010-04-27 | Qualcomm Incorporated | Communication buffer manager and method therefor |
US7200745B2 (en) | 2003-09-12 | 2007-04-03 | Microsoft Corporation | System and method for specifying and utilizing hardware functionality by executing a common hardware register pseudo-language |
US8214536B2 (en) | 2003-09-16 | 2012-07-03 | Research In Motion Limited | Methods and apparatus for selecting a wireless network based on quality of service (QoS) criteria associated with an application |
ATE491318T1 (en) | 2003-09-16 | 2010-12-15 | Research In Motion Ltd | METHOD AND APPARATUS FOR SELECTING A WIRELESS NETWORK BASED ON QUALITY OF SERVICE CRITERIA ASSOCIATED WITH AN APPLICATION |
US7562213B1 (en) | 2003-09-16 | 2009-07-14 | Cisco Technology, Inc. | Approaches for applying service policies to encrypted packets |
US7668612B1 (en) | 2003-09-18 | 2010-02-23 | Hewlett-Packard Development Company, L.P. | System and method for efficient manufacture and update of electronic devices |
US7239877B2 (en) | 2003-10-07 | 2007-07-03 | Accenture Global Services Gmbh | Mobile provisioning tool system |
US7505756B2 (en) | 2003-10-15 | 2009-03-17 | Microsoft Corporation | Dynamic online subscription for wireless wide-area networks |
US7539156B2 (en) | 2003-10-17 | 2009-05-26 | Qualcomm Incorporated | Method and apparatus for provisioning and activation of an embedded module in an access terminal of a wireless communication system |
US7958029B1 (en) | 2003-10-20 | 2011-06-07 | Thomas Bobich | Method for minimizing financial risk for wireless services |
US7181197B2 (en) | 2003-10-20 | 2007-02-20 | Cingular Wireless Ii, Llc | Preventing unauthorized switching of mobile telecommunications service providers |
US7813746B2 (en) | 2003-10-24 | 2010-10-12 | Samsung Electronics Co., Ltd. | Wireless network using shared traffic channel mode of operation for broadcast services |
CN100377523C (en) | 2003-10-28 | 2008-03-26 | 华为技术有限公司 | Data service information collecting device and charging method using same |
US7577427B2 (en) | 2003-11-05 | 2009-08-18 | At&T Intellectual Property I, L.P. | System and method of transitioning between cellular and voice over internet protocol communication |
US20050097516A1 (en) | 2003-11-05 | 2005-05-05 | Microsoft Corporation | Extensible and dynamically-configurable problem-reporting client |
US8050275B1 (en) | 2003-11-18 | 2011-11-01 | Cisco Technology, Inc. | System and method for offering quality of service in a network environment |
US20050108075A1 (en) | 2003-11-18 | 2005-05-19 | International Business Machines Corporation | Method, apparatus, and program for adaptive control of application power consumption in a mobile computer |
US8122128B2 (en) * | 2003-11-18 | 2012-02-21 | Burke Ii Robert M | System for regulating access to and distributing content in a network |
US7773502B2 (en) | 2003-11-19 | 2010-08-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Dynamic voice over data prioritization for wireless communication networks |
EP1702432A1 (en) | 2003-11-19 | 2006-09-20 | Telefonaktiebolaget LM Ericsson (publ) | Arrangement and method for determining charging in a telecommunications system |
US7409447B1 (en) | 2003-11-20 | 2008-08-05 | Juniper Networks, Inc. | Policy analyzer |
JP4131229B2 (en) | 2003-11-25 | 2008-08-13 | 日本電気株式会社 | Folding mobile phone and method for unlocking folding mobile phone |
CN1902965B (en) | 2003-11-26 | 2011-01-12 | 诺基亚公司 | Flexible messaging system |
US8495227B2 (en) | 2003-12-11 | 2013-07-23 | International Business Machines Corporation | Method and system to distribute policies |
US8095640B2 (en) | 2003-12-12 | 2012-01-10 | Alcatel Lucent | Distributed architecture for real-time flow measurement at the network domain level |
US7614051B2 (en) | 2003-12-16 | 2009-11-03 | Microsoft Corporation | Creating file systems within a file in a storage technology-abstracted manner |
GB2409368B (en) | 2003-12-16 | 2006-03-22 | Agilent Technologies Inc | Identifying services provided via IP and similar packet networks, and service usage records for such services |
US7043226B2 (en) | 2003-12-17 | 2006-05-09 | Motorola, Inc. | Variable expiration parameter of a wireless communication device based upon signal strength |
US7411930B2 (en) | 2003-12-17 | 2008-08-12 | Qualcomm, Incorporated | Apparatus and method for prioritized apportionment of transmission power in a multi-carrier terminal |
US7440433B2 (en) | 2003-12-19 | 2008-10-21 | Nortel Networks Limited | Mobile IP notification |
CN100492974C (en) | 2003-12-19 | 2009-05-27 | 上海贝尔阿尔卡特股份有限公司 | A method and apparatus for communication charges apportioning among different service providers |
US7792086B2 (en) * | 2003-12-23 | 2010-09-07 | Redknee Inc. | Method for implementing an intelligent content rating middleware platform and gateway system |
US20050254435A1 (en) | 2003-12-23 | 2005-11-17 | Moakley George P | Method and system for selecting network connections in a multi-network environment |
US8635661B2 (en) | 2003-12-23 | 2014-01-21 | Mcafee, Inc. | System and method for enforcing a security policy on mobile devices using dynamically generated security profiles |
US7610396B2 (en) | 2003-12-31 | 2009-10-27 | United States Cellular Corporation | System and method for measuring and recording latency in internet protocol networks |
US7461248B2 (en) | 2004-01-23 | 2008-12-02 | Nokia Corporation | Authentication and authorization in heterogeneous networks |
US8554876B2 (en) | 2004-01-23 | 2013-10-08 | Hewlett-Packard Development Company, L.P. | User profile service |
US7627314B2 (en) | 2004-01-27 | 2009-12-01 | At&T Mobility Ii Llc | Call handling scheme to reduce roaming charges |
US7925778B1 (en) | 2004-02-13 | 2011-04-12 | Cisco Technology, Inc. | Method and apparatus for providing multicast messages across a data communication network |
US20050183143A1 (en) | 2004-02-13 | 2005-08-18 | Anderholm Eric J. | Methods and systems for monitoring user, application or device activity |
US9589117B2 (en) | 2004-02-17 | 2017-03-07 | Hewlett-Packard Development Company, L.P. | Computer security system and method |
US7545782B2 (en) | 2004-02-19 | 2009-06-09 | Belair Networks, Inc. | Mobile station traffic routing |
US7512131B2 (en) | 2004-02-25 | 2009-03-31 | Schwegman, Lundberg & Woessner, P.A. | Systems and methods for centralized control and management of a broadband wireless network with data processing, and enforcement distributed to the network edge |
US8166554B2 (en) | 2004-02-26 | 2012-04-24 | Vmware, Inc. | Secure enterprise network |
DE602005007589D1 (en) | 2004-02-27 | 2008-07-31 | Research In Motion Ltd | SYSTEM AND PROCESS FOR ASYNCHRONOUS COMMUNICATION WITH SYNCHRONOUS WEB SERVICES USING A MEDIUM SERVICE |
US7774456B1 (en) | 2004-02-27 | 2010-08-10 | Packeteer, Inc. | Methods, apparatuses and systems facilitating classification of web services network traffic |
US7457870B1 (en) | 2004-02-27 | 2008-11-25 | Packeteer, Inc. | Methods, apparatuses and systems facilitating classification of web services network traffic |
US8468337B2 (en) | 2004-03-02 | 2013-06-18 | International Business Machines Corporation | Secure data transfer over a network |
US7665130B2 (en) | 2004-03-10 | 2010-02-16 | Eric White | System and method for double-capture/double-redirect to a different location |
US8473619B2 (en) | 2005-03-16 | 2013-06-25 | Icontrol Networks, Inc. | Security network integrated with premise security system |
US9172553B2 (en) | 2005-03-16 | 2015-10-27 | Icontrol Networks, Inc. | Security system with networked touchscreen and gateway |
US7088600B2 (en) * | 2004-03-16 | 2006-08-08 | Intersil Americas, Inc. | Startup via FB pin regulation |
EP1578059A1 (en) | 2004-03-19 | 2005-09-21 | Swisscom Mobile AG | WLAN handover |
US7356337B2 (en) | 2004-03-23 | 2008-04-08 | Starhome Gmbh | Dialing services on a mobile handset and remote provisioning therefor |
JP4346483B2 (en) * | 2004-03-25 | 2009-10-21 | 本田技研工業株式会社 | Twin clutch transmission |
US7460837B2 (en) | 2004-03-25 | 2008-12-02 | Cisco Technology, Inc. | User interface and time-shifted presentation of data in a system that monitors activity in a shared radio frequency band |
US7426181B1 (en) | 2004-03-26 | 2008-09-16 | Packeteer, Inc. | Slow-start adaptive mechanisms to improve efficiency of bandwidth allocation |
US7843843B1 (en) | 2004-03-29 | 2010-11-30 | Packeteer, Inc. | Adaptive, application-aware selection of differntiated network services |
US8489720B1 (en) | 2004-03-31 | 2013-07-16 | Blue Coat Systems, Inc. | Cost-aware, bandwidth management systems adaptive to network conditions |
US7590101B2 (en) | 2004-03-31 | 2009-09-15 | Intel Corporation | Remote operations using wireless personal area network |
GB2412797A (en) * | 2004-04-02 | 2005-10-05 | Motorola Inc | RF power amplifier with feedback-controlled dc supply voltage |
US8693323B1 (en) | 2004-04-05 | 2014-04-08 | Verizon Business Global Llc | System and method for managing communications in an access network |
US7539862B2 (en) | 2004-04-08 | 2009-05-26 | Ipass Inc. | Method and system for verifying and updating the configuration of an access device during authentication |
US7620041B2 (en) | 2004-04-15 | 2009-11-17 | Alcatel-Lucent Usa Inc. | Authentication mechanisms for call control message integrity and origin verification |
US7522549B2 (en) | 2004-04-16 | 2009-04-21 | Broadcom Corporation | Registering access device multimedia content via a broadband access gateway |
US7580857B2 (en) | 2004-04-16 | 2009-08-25 | First Data Corporation | Methods and systems for online transaction processing |
US7853255B2 (en) | 2004-04-16 | 2010-12-14 | Broadcom Corporation | Digital personal assistance via a broadband access gateway |
JP2006526229A (en) | 2004-04-20 | 2006-11-16 | イントロモバイル カンパニー リミテッド | Wait screen resource control and operation apparatus and method for mobile communication terminal apparatus |
US7610057B2 (en) | 2004-04-23 | 2009-10-27 | Microsoft Corporation | Selecting a wireless networking technology on a device capable of carrying out wireless network communications via multiple wireless technologies |
US7564799B2 (en) | 2004-04-23 | 2009-07-21 | Intermec Ip Corp. | System and method for providing seamless roaming |
US7761607B2 (en) | 2004-04-23 | 2010-07-20 | Microsoft Corporation | User based communication mode selection on a device capable of carrying out network communications |
US7606918B2 (en) | 2004-04-27 | 2009-10-20 | Microsoft Corporation | Account creation via a mobile device |
US7873708B2 (en) | 2004-04-28 | 2011-01-18 | At&T Mobility Ii Llc | Systems and methods for providing mobile advertising and directory assistance services |
US7174156B1 (en) | 2004-05-10 | 2007-02-06 | Sprint Spectrum L.P. | Method and system for tracking and billing vocoder bypass calls in a wireless wide area network |
JP2005339247A (en) | 2004-05-27 | 2005-12-08 | Secured Communications:Kk | Bidirectional one time id authenticating system and authenticating method |
US20050266880A1 (en) | 2004-05-27 | 2005-12-01 | Gupta Vivek G | Open and extensible framework for ubiquitous radio management and services in heterogeneous wireless networks |
US7889384B2 (en) | 2004-06-03 | 2011-02-15 | International Business Machines Corporation | Method for more efficiently managing complex payloads in a point of sale system |
US20050289558A1 (en) | 2004-06-08 | 2005-12-29 | Daniel Illowsky | Device interoperability runtime establishing event serialization and synchronization amongst a plurality of separate processing units and method for coordinating control data and operations |
US8522039B2 (en) | 2004-06-09 | 2013-08-27 | Apple Inc. | Method and apparatus for establishing a federated identity using a personal wireless device |
FI117587B (en) | 2004-06-18 | 2006-11-30 | Nethawk Oyj | Method, device, and computer program product for monitoring data communications |
US7395244B1 (en) | 2004-06-23 | 2008-07-01 | Symantec Corporation | Criticality classification system and method |
US9712443B1 (en) | 2004-06-25 | 2017-07-18 | InMon Corp. | Distributed traffic quota measurement and enforcement |
US8005009B2 (en) | 2004-06-25 | 2011-08-23 | InMon Corp. | Methods and computer programs for generating data traffic matrices |
US7760882B2 (en) | 2004-06-28 | 2010-07-20 | Japan Communications, Inc. | Systems and methods for mutual authentication of network nodes |
FI20040888A0 (en) | 2004-06-28 | 2004-06-28 | Nokia Corp | Management of services in a packet switching data network |
US7966405B2 (en) | 2004-06-29 | 2011-06-21 | Microsoft Corporation | Session multiplex protocol |
US7286848B2 (en) | 2004-06-30 | 2007-10-23 | Richard P Vireday | Method and apparatus to provide tiered wireless network access |
US7627767B2 (en) | 2004-06-30 | 2009-12-01 | At&T Intellectual Property I, L.P. | Methods and systems for remotely securing data in a wireless device in a communications network |
US7849161B2 (en) | 2004-06-30 | 2010-12-07 | At&T Intellectual Property I, L.P. | System and methods for remotely recovering and purging data from a wireless device in a communications network |
US8073427B2 (en) | 2004-06-30 | 2011-12-06 | At&T Intellectual Property I, L.P. | Remotely requesting an alert from a lost or stolen wireless device |
JP4445547B2 (en) | 2004-07-05 | 2010-04-07 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Binding mechanism for quality of service management in telecommunication networks |
US7505795B1 (en) | 2004-07-07 | 2009-03-17 | Advanced Micro Devices, Inc. | Power save management with customized range for user configuration and tuning value based upon recent usage |
US7551922B2 (en) | 2004-07-08 | 2009-06-23 | Carrier Iq, Inc. | Rule based data collection and management in a wireless communications network |
US7609650B2 (en) | 2004-07-08 | 2009-10-27 | Carrier Iq, Inc. | Collection of data at target wireless devices using data collection profiles |
US8605691B2 (en) | 2004-07-09 | 2013-12-10 | Koninklijke Philips N.V. | Enhanced site report by low latency roaming by passive scanning in IEEE 802.11 networks |
US7084775B1 (en) | 2004-07-12 | 2006-08-01 | User-Centric Ip, L.P. | Method and system for generating and sending user-centric weather alerts |
US7286834B2 (en) | 2004-07-13 | 2007-10-23 | Sbc Knowledge Ventures, Lp | System and method for location based policy management |
US7418253B2 (en) | 2004-07-19 | 2008-08-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, security system control module and policy server for providing security in a packet-switched telecommunications system |
US7908313B2 (en) * | 2004-07-21 | 2011-03-15 | The Mathworks, Inc. | Instrument-based distributed computing systems |
AU2005266945A1 (en) | 2004-07-23 | 2006-02-02 | Citrix Systems, Inc. | A method and systems for securing remote access to private networks |
AU2005266943C1 (en) | 2004-07-23 | 2011-01-06 | Citrix Systems, Inc. | Systems and methods for optimizing communications between network nodes |
US7676838B2 (en) | 2004-07-26 | 2010-03-09 | Alcatel Lucent | Secure communication methods and systems |
JP2006041989A (en) | 2004-07-28 | 2006-02-09 | Fujitsu Ltd | Charging plan notification system |
CN100372348C (en) * | 2004-07-28 | 2008-02-27 | 沈逸林 | Application and communication method of terminal of network media phone |
US7076237B2 (en) | 2004-08-05 | 2006-07-11 | International Business Machines Corporation | Traffic shaping of cellular service consumption through delaying of service completion according to geographical-based pricing advantages |
US7945945B2 (en) | 2004-08-06 | 2011-05-17 | Enterasys Networks, Inc. | System and method for address block enhanced dynamic network policy management |
US20060035631A1 (en) | 2004-08-13 | 2006-02-16 | Christopher White | Wireless device service activation from the wireless device |
US7660419B1 (en) | 2004-08-13 | 2010-02-09 | Texas Instruments Incorporated | System and method for security association between communication devices within a wireless personal and local area network |
US7418257B2 (en) | 2004-08-31 | 2008-08-26 | Pantech & Curitel Communications, Inc. | Mobile communication terminal, wireless data service authentication server, system for automatically blocking voice call connection, and method of processing various messages in mobile communication terminal |
US8146142B2 (en) | 2004-09-03 | 2012-03-27 | Intel Corporation | Device introduction and access control framework |
US8732808B2 (en) | 2004-09-08 | 2014-05-20 | Cradlepoint, Inc. | Data plan activation and modification |
US7697540B2 (en) | 2004-09-08 | 2010-04-13 | Telefonaktiebolaget L M Ericsson (Publ) | Quality of service (QoS) class reordering with token retention |
US7962569B2 (en) | 2004-09-08 | 2011-06-14 | Cradlepoint, Inc. | Embedded DNS |
US7366934B1 (en) | 2004-09-08 | 2008-04-29 | Stryker Corporation | Method of remotely controlling devices for endoscopy |
US7260382B1 (en) | 2004-09-21 | 2007-08-21 | Sprint Spectrum L.P. | Method and system for customizing a wireless device's user-interface based on which vendor distributed the wireless device |
US7561515B2 (en) * | 2004-09-27 | 2009-07-14 | Intel Corporation | Role-based network traffic-flow rate control |
US20060068796A1 (en) | 2004-09-30 | 2006-03-30 | Millen Stephanie L | Retrieving jurisdiction information from home location register |
KR100877475B1 (en) | 2004-09-30 | 2009-01-07 | 주식회사 케이티 | Apparatus and Method for Integrated Billing Management by Real-time Session Management in wire/wireless Integrated Service Network |
US7599288B2 (en) | 2004-09-30 | 2009-10-06 | Hewlett-Packard Development Company, L.P. | Processing of usage data for first and second types of usage-based functions |
EP1643358A1 (en) | 2004-10-01 | 2006-04-05 | Nokia Corporation | Pre-loading data |
US7421004B2 (en) | 2004-10-05 | 2008-09-02 | Kamilo Feher | Broadband, ultra wideband and ultra narrowband reconfigurable interoperable systems |
US7661124B2 (en) | 2004-10-05 | 2010-02-09 | Microsoft Corporation | Rule-driven specification of web service policy |
US7764768B2 (en) | 2004-10-06 | 2010-07-27 | Alcatel-Lucent Usa Inc. | Providing CALEA/legal intercept information to law enforcement agencies for internet protocol multimedia subsystems (IMS) |
US8238287B1 (en) | 2004-10-06 | 2012-08-07 | Marvell International Ltd. | Method and apparatus for providing quality of service (QoS) in a wireless local area network |
US8015234B2 (en) | 2004-10-08 | 2011-09-06 | Sharp Laboratories Of America, Inc. | Methods and systems for administering imaging device notification access control |
US20060095517A1 (en) | 2004-10-12 | 2006-05-04 | O'connor Clint H | Wide area wireless messaging system |
US8196199B2 (en) * | 2004-10-19 | 2012-06-05 | Airdefense, Inc. | Personal wireless monitoring agent |
US8010082B2 (en) | 2004-10-20 | 2011-08-30 | Seven Networks, Inc. | Flexible billing architecture |
US7336960B2 (en) | 2004-10-26 | 2008-02-26 | Cisco Technology, Inc. | Method and apparatus for balancing wireless access based on centralized information |
CA2585196C (en) | 2004-10-26 | 2015-01-06 | Chugai Seiyaku Kabushiki Kaisha | Anti-glypican 3 antibody having modified sugar chain |
US8504574B2 (en) | 2004-10-28 | 2013-08-06 | Motorola Mobility Llc | Method and system for freshness indication of location data |
EP1810528A4 (en) | 2004-10-29 | 2009-11-04 | Nokia Corp | Mobile telephone location application |
US7433362B2 (en) | 2004-11-05 | 2008-10-07 | Sbc Knowledge Ventures, L.P. | System and method for SONET NSAP addressing |
US8006288B2 (en) | 2004-11-05 | 2011-08-23 | International Business Machines Corporation | Method and apparatus for accessing a computer application program |
US7990949B2 (en) | 2004-11-09 | 2011-08-02 | Broadcom Corporation | Enhanced wide area network support via a broadband access gateway |
EP1810474B1 (en) | 2004-11-10 | 2014-03-12 | Telefonaktiebolaget LM Ericsson (publ) | An arrangement, nodes and a method relating to services access over a communication system |
US20060099970A1 (en) | 2004-11-10 | 2006-05-11 | Morgan Scott D | Method and system for providing a log of mobile station location requests |
US20130326356A9 (en) | 2004-11-12 | 2013-12-05 | Jianyu Roy Zheng | System and method for managing wireless connections in computer |
US7636333B2 (en) | 2004-11-16 | 2009-12-22 | Qualcomm Incorporated | Method and apparatus for carrier customization in communication systems |
US7369856B2 (en) | 2004-11-24 | 2008-05-06 | Intel Corporation | Method and system to support fast hand-over of mobile subscriber stations in broadband wireless networks |
CN100477613C (en) | 2004-11-25 | 2009-04-08 | 都科摩(北京)通信技术研究中心有限公司 | Distributed wireless access method and apparatus based on network distribution vector table |
KR101010654B1 (en) | 2004-11-29 | 2011-01-24 | 리서치 인 모션 리미티드 | System and method for providing operator-differentiated messaging to a wireless user equipment (ue) device |
DE602005024296D1 (en) | 2004-11-29 | 2010-12-02 | Research In Motion Ltd | SYSTEM AND METHOD FOR SERVICE ACTIVATION IN THE MOBILE NETWORK CHARGE CALCULATION |
JP4492318B2 (en) | 2004-11-30 | 2010-06-30 | 日本電気株式会社 | One-time ID authentication system, authentication server, conversion server, one-time ID authentication method and program |
US7529184B2 (en) | 2004-12-01 | 2009-05-05 | Research In Motion Limited | Flow control buffering |
US7848768B2 (en) | 2004-12-08 | 2010-12-07 | Sony Corporation | Network system and communication device |
US7936762B2 (en) | 2004-12-09 | 2011-05-03 | The Boeing Company | QOS provisioning in a network having dynamic link states |
US7376112B2 (en) | 2004-12-14 | 2008-05-20 | Sbc Knowledge Ventures, L.P. | Method and system for seamless service availability for multi-mode terminals in different access networks |
US20060136882A1 (en) | 2004-12-17 | 2006-06-22 | Nokia Corporation | System and method for background JAVA application resource control |
US7742406B1 (en) | 2004-12-20 | 2010-06-22 | Packeteer, Inc. | Coordinated environment for classification and control of network traffic |
US7554983B1 (en) | 2004-12-20 | 2009-06-30 | Packeteer, Inc. | Probing hosts against network application profiles to facilitate classification of network traffic |
US7280816B2 (en) | 2004-12-23 | 2007-10-09 | Agere Systems Inc. | Techniques for monitoring mobile telecommunications for shared accounts |
US20060143066A1 (en) | 2004-12-23 | 2006-06-29 | Hermann Calabria | Vendor-driven, social-network enabled review syndication system |
CN100433899C (en) | 2004-12-28 | 2008-11-12 | 华为技术有限公司 | Method and system for ensuring safe data service in mobile communication system |
KR100584409B1 (en) | 2004-12-29 | 2006-05-26 | 삼성전자주식회사 | Relay commonication method for ofdma-based cellular communication system |
EP1834449B1 (en) | 2004-12-29 | 2012-04-18 | Telefonaktiebolaget LM Ericsson (publ) | Priority bearers in a mobile telecommunication network |
GB2421872B (en) | 2004-12-29 | 2007-06-13 | Motorola Inc | Mobile station, infrastructure processor, system and method for use in cellular communications |
US7620383B2 (en) | 2004-12-29 | 2009-11-17 | United States Cellular Corporation | Client-based context-based billing for wireless networks |
US7822837B1 (en) | 2004-12-30 | 2010-10-26 | Packeteer, Inc. | Adaptive correlation of service level agreement and network application performance |
CN1801829A (en) | 2004-12-30 | 2006-07-12 | 昆达电脑科技(昆山)有限公司 | Mobile phone time automatic correction method |
US7593366B2 (en) | 2004-12-30 | 2009-09-22 | Intel Corporation | Wireless network facilitator and monitor |
US7571474B2 (en) | 2004-12-30 | 2009-08-04 | Intel Corporation | System security event notification aggregation and non-repudiation |
US7515608B2 (en) | 2005-01-04 | 2009-04-07 | Intel Corporation | Methods and media access controller for mesh networks with adaptive quality-of-service management |
US20060150238A1 (en) | 2005-01-04 | 2006-07-06 | Symbol Technologies, Inc. | Method and apparatus of adaptive network policy management for wireless mobile computers |
US7979889B2 (en) | 2005-01-07 | 2011-07-12 | Cisco Technology, Inc. | Methods and apparatus providing security to computer systems and networks |
US20060178943A1 (en) | 2005-01-07 | 2006-08-10 | Rollinson Joseph R | Food order fulfillment system deploying a universal in-store point-of-sale (POS) for preparation and pickup scheduling |
JP4567472B2 (en) | 2005-01-12 | 2010-10-20 | 株式会社エヌ・ティ・ティ・ドコモ | Data communication restriction method and data communication restriction control device for flat-rate users |
US8543814B2 (en) | 2005-01-12 | 2013-09-24 | Rpx Corporation | Method and apparatus for using generic authentication architecture procedures in personal computers |
US7499438B2 (en) | 2005-01-13 | 2009-03-03 | 2Wire, Inc. | Controlling wireless access to a network |
US7535880B1 (en) | 2005-01-13 | 2009-05-19 | 2Wire, Inc. | Method and apparatus for controlling wireless access to a network |
US7693513B2 (en) | 2005-01-18 | 2010-04-06 | Intel Corporation | Methods and apparatus for transferring service flow context of mobile broadband wireless access networks |
WO2006077481A1 (en) | 2005-01-19 | 2006-07-27 | Truecontext Corporation | Policy-driven mobile forms applications |
US8005913B1 (en) | 2005-01-20 | 2011-08-23 | Network Protection Sciences, LLC | Controlling, filtering, and monitoring of mobile device access to the internet, data, voice, and applications |
US7826605B1 (en) | 2005-01-20 | 2010-11-02 | Andre Denis Vanier | Method and system for integrating information from wireless and landline telephone systems |
US7539132B2 (en) | 2005-01-21 | 2009-05-26 | At&T Intellectual Property Ii, L.P. | Methods, systems, and devices for determining COS level |
US8700729B2 (en) | 2005-01-21 | 2014-04-15 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US7593417B2 (en) | 2005-01-21 | 2009-09-22 | Research In Motion Limited | Handling broadcast and multicast traffic as unicast traffic in a wireless network |
US7962606B2 (en) | 2005-01-24 | 2011-06-14 | Daintree Networks, Pty. Ltd. | Network analysis system and method |
US7681226B2 (en) | 2005-01-28 | 2010-03-16 | Cisco Technology, Inc. | Methods and apparatus providing security for multiple operational states of a computerized device |
US20060174035A1 (en) | 2005-01-28 | 2006-08-03 | At&T Corp. | System, device, & method for applying COS policies |
JP4376233B2 (en) | 2005-02-04 | 2009-12-02 | 株式会社エヌ・ティ・ティ・ドコモ | Client apparatus, device verification apparatus, and verification method |
US8676633B2 (en) | 2005-02-08 | 2014-03-18 | Xerox Corporation | Office document assessment method and system |
US20060183462A1 (en) | 2005-02-11 | 2006-08-17 | Nokia Corporation | Managing an access account using personal area networks and credentials on a mobile device |
US7549151B2 (en) | 2005-02-14 | 2009-06-16 | Qnx Software Systems | Fast and memory protected asynchronous message scheme in a multi-process and multi-thread environment |
US7373661B2 (en) | 2005-02-14 | 2008-05-13 | Ethome, Inc. | Systems and methods for automatically configuring and managing network devices and virtual private networks |
US7689681B1 (en) | 2005-02-14 | 2010-03-30 | David Scott L | System and method for facilitating controlled compensable use of a remotely accessible network device |
US7805140B2 (en) | 2005-02-18 | 2010-09-28 | Cisco Technology, Inc. | Pre-emptive roaming mechanism allowing for enhanced QoS in wireless network environments |
US7743002B2 (en) | 2005-02-24 | 2010-06-22 | Rearden Commerce, Inc. | Method and system for testing of policies to determine cost savings |
EP1866789B8 (en) * | 2005-02-28 | 2020-04-15 | McAfee, LLC | Mobile data security system and methods |
US20060199608A1 (en) | 2005-03-01 | 2006-09-07 | Kyocera Wireless Corp. | Systems and methods for motion sensitive roaming in a mobile communication device |
CN101283572A (en) | 2005-03-01 | 2008-10-08 | 方瑞公司 | Application program update deployment to a mobile device |
DE102005009504B3 (en) | 2005-03-02 | 2006-03-09 | Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. | Mobile unit for company DECT networks uses communications protocol with different messages for normal and ad hoc registration processes |
US7716638B2 (en) | 2005-03-04 | 2010-05-11 | Microsoft Corporation | Methods for describing processor features |
FR2883116B1 (en) | 2005-03-08 | 2007-04-13 | Commissariat Energie Atomique | GLOBALLY ASYNCHRONOUS COMMUNICATION ARCHITECTURE FOR CHIP SYSTEM. |
US8523547B2 (en) | 2005-03-09 | 2013-09-03 | Merton W. Pekrul | Rotary engine expansion chamber apparatus and method of operation therefor |
US7581229B2 (en) | 2005-03-11 | 2009-08-25 | Microsoft Corporation | Systems and methods for supporting device access from multiple operating systems |
US7609700B1 (en) | 2005-03-11 | 2009-10-27 | At&T Mobility Ii Llc | QoS channels for multimedia services on a general purpose operating system platform using data cards |
US7817983B2 (en) | 2005-03-14 | 2010-10-19 | Qualcomm Incorporated | Method and apparatus for monitoring usage patterns of a wireless device |
US7957020B2 (en) | 2005-03-15 | 2011-06-07 | Canon Kabushiki Kaisha | Image forming apparatus, image forming system, and control program thereof to manage printing sheet communications |
US8174378B2 (en) | 2005-03-18 | 2012-05-08 | Richman Technology Corporation | Human guard enhancing multiple site security system |
US20060248194A1 (en) | 2005-03-18 | 2006-11-02 | Riverbed Technology, Inc. | Connection forwarding |
ES2379074T3 (en) | 2005-03-22 | 2012-04-20 | Swisscom Ag | Method and system for establishing a "peer-to-peer" communication channel. |
US7426381B2 (en) | 2005-03-23 | 2008-09-16 | Oracle International Corporation | Device billing agent |
US7403763B2 (en) | 2005-03-23 | 2008-07-22 | Oracle International Corporation | Device agent |
US8116781B2 (en) | 2005-03-28 | 2012-02-14 | Rockstar Bidco Lp | Method and system of managing wireless resources |
US7636626B2 (en) | 2005-03-28 | 2009-12-22 | General Motors Company | Method and system for monitoring and retrieving device usage |
CN100505684C (en) | 2005-03-29 | 2009-06-24 | 国际商业机器公司 | Network system, flow equalization method, network monitoring device and host machine |
US7515926B2 (en) | 2005-03-30 | 2009-04-07 | Alcatel-Lucent Usa Inc. | Detection of power-drain denial-of-service attacks in wireless networks |
US7546460B2 (en) | 2005-03-30 | 2009-06-09 | Oracle International Corporation | Secure communications across multiple protocols |
US8060463B1 (en) | 2005-03-30 | 2011-11-15 | Amazon Technologies, Inc. | Mining of user event data to identify users with common interests |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US20070100981A1 (en) | 2005-04-08 | 2007-05-03 | Maria Adamczyk | Application services infrastructure for next generation networks including one or more IP multimedia subsystem elements and methods of providing the same |
EP1713206A1 (en) | 2005-04-11 | 2006-10-18 | Last Mile Communications/Tivis Limited | A distributed communications network comprising wirelessly linked base stations |
US7719966B2 (en) | 2005-04-13 | 2010-05-18 | Zeugma Systems Inc. | Network element architecture for deep packet inspection |
US20060235973A1 (en) * | 2005-04-14 | 2006-10-19 | Alcatel | Network services infrastructure systems and methods |
US7463637B2 (en) * | 2005-04-14 | 2008-12-09 | Alcatel Lucent | Public and private network service management systems and methods |
US7688792B2 (en) | 2005-04-21 | 2010-03-30 | Qualcomm Incorporated | Method and apparatus for supporting wireless data services on a TE2 device using an IP-based interface |
EP3021553A1 (en) | 2005-04-22 | 2016-05-18 | Thomson Licensing | Method and apparatuses for secure, anonymous wireless lan (wlan) access |
KR20100132556A (en) | 2005-04-28 | 2010-12-17 | 콸콤 인코포레이티드 | Wireless handoffs between multiple wireless networks |
US7937069B2 (en) | 2005-04-29 | 2011-05-03 | Rassam Frederic | System and process for switching between cell phone and landline services |
US7774412B1 (en) | 2005-05-06 | 2010-08-10 | Adobe Systems Inc. | Methods and apparatus facilitating distribution of content |
EP1880538B1 (en) | 2005-05-09 | 2017-12-06 | Nokia Technologies Oy | Services in a communication system |
GB0509440D0 (en) | 2005-05-09 | 2005-06-15 | Nokia Corp | Services in a communication system |
US8085808B2 (en) | 2005-05-12 | 2011-12-27 | Verizon Services Corp. | Automatic configuration of network devices for network services |
US20060258341A1 (en) | 2005-05-13 | 2006-11-16 | Microsoft Corporation | Mobile internet services discovery and/or provisioning |
US7945240B1 (en) | 2005-05-13 | 2011-05-17 | At&T Mobility Ii Llc | Mobile communications billing architecture |
CN1867024B (en) | 2005-05-19 | 2010-10-06 | 华为技术有限公司 | Charging information transmitting method |
US7920529B1 (en) | 2005-05-24 | 2011-04-05 | At&T Mobility Ii Llc | Intermediary query manager for 2G and 3G services |
CN100417070C (en) | 2005-05-30 | 2008-09-03 | 华为技术有限公司 | Method and system for realization of content charging |
US7729326B2 (en) | 2005-05-31 | 2010-06-01 | Symbol Technologies, Inc. | Wireless network system with wireless access ports |
US7242920B2 (en) | 2005-05-31 | 2007-07-10 | Scenera Technologies, Llc | Methods, systems, and computer program products for controlling data transmission based on power cost |
US8751648B2 (en) | 2005-06-03 | 2014-06-10 | Wefi, Inc. | Providing and receiving network access |
US20130058274A1 (en) | 2005-06-03 | 2013-03-07 | Wefi Inc. | Method and system for accessing wireless networks |
US7516478B2 (en) | 2005-06-03 | 2009-04-07 | Microsoft Corporation | Remote management of mobile devices |
CN101258713A (en) * | 2005-06-06 | 2008-09-03 | 茂比迪股份有限公司 | System and method of scheduling delivery of packets |
JP2006344007A (en) | 2005-06-09 | 2006-12-21 | Hitachi Ltd | Portable terminal identification system |
US7685530B2 (en) | 2005-06-10 | 2010-03-23 | T-Mobile Usa, Inc. | Preferred contact group centric interface |
US7770785B2 (en) | 2005-06-13 | 2010-08-10 | Qualcomm Incorporated | Apparatus and methods for detection and management of unauthorized executable instructions on a wireless device |
US7593730B2 (en) | 2005-06-17 | 2009-09-22 | Qualcomm Incorporated | System selection and acquisition for WWAN and WLAN systems |
US7574212B2 (en) | 2005-06-22 | 2009-08-11 | Sprint Spectrum L.P. | Method and system for managing communication sessions during multi-mode mobile station handoff |
US7580356B1 (en) | 2005-06-24 | 2009-08-25 | Packeteer, Inc. | Method and system for dynamically capturing flow traffic data |
US7724753B2 (en) | 2005-06-24 | 2010-05-25 | Aylus Networks, Inc. | Digital home networks having a control point located on a wide area network |
US8228818B2 (en) | 2005-06-24 | 2012-07-24 | At&T Intellectual Property Ii, Lp | Systems, methods, and devices for monitoring networks |
US20060291477A1 (en) | 2005-06-28 | 2006-12-28 | Marian Croak | Method and apparatus for dynamically calculating the capacity of a packet network |
US7650522B2 (en) | 2005-06-28 | 2010-01-19 | Symbol Technologies, Inc. | Mobility policy manager for mobile computing devices |
DE602005002741T2 (en) | 2005-06-29 | 2008-07-03 | Research In Motion Ltd., Waterloo | System and method for the management and revocation of rights |
US7844034B1 (en) | 2005-07-06 | 2010-11-30 | Sprint Spectrum L.P. | Method and system for bridging third parties into calls |
US20070168499A1 (en) | 2005-07-07 | 2007-07-19 | Acenet Technology Inc. | Configurable Modular Networking System and Method Thereof |
US7472189B2 (en) | 2005-07-21 | 2008-12-30 | Sbc Knowledge Ventures, L.P. | Method of collecting data from network elements |
EP2463820A3 (en) | 2005-07-22 | 2012-09-12 | Kangaroo Media, Inc. | System and methods for enhancing the experience of spectators attending a live sporting event |
GB2428933B (en) | 2005-07-25 | 2010-08-25 | Agilent Technologies Inc | An apparatus and method for enriching data records in a telecommunications network |
US8010080B1 (en) * | 2005-07-25 | 2011-08-30 | Sprint Spectrum L.P. | Predictive payment suggestion in a telecommunication system |
JP5000652B2 (en) | 2005-07-28 | 2012-08-15 | エムフォメーション・テクノロジーズ・インコーポレイテッド | System and method for quality of service management of wireless devices |
EP1910987A2 (en) | 2005-07-29 | 2008-04-16 | British Telecommunications Public Limited Company | Communications system |
US7486658B2 (en) | 2005-07-29 | 2009-02-03 | Cisco Technology, Inc. | Method and system for media synchronization in QoS-enabled wireless networks |
US8880047B2 (en) | 2005-08-03 | 2014-11-04 | Jeffrey C. Konicek | Realtime, location-based cell phone enhancements, uses, and applications |
EP1750469B1 (en) | 2005-08-03 | 2010-07-07 | Telefonaktiebolaget LM Ericsson (publ) | Automatic mobile device capability management |
GB2428938B (en) | 2005-08-05 | 2007-12-05 | Motorola Inc | Unauthorized call activity detection in a cellular communication system |
KR100753640B1 (en) | 2005-08-05 | 2007-08-29 | 주식회사 유프레스토 | System for testifying mobile communication network and method thereof |
US7304570B2 (en) | 2005-08-10 | 2007-12-04 | Scenera Technologies, Llc | Methods, systems, and computer program products for providing context-based, hierarchical security for a mobile device |
US8461958B2 (en) | 2005-08-17 | 2013-06-11 | Wireless Data Solutions, Llc | System for monitoring and control of transport containers |
GB0517304D0 (en) | 2005-08-23 | 2005-10-05 | Netronome Systems Inc | A system and method for processing and forwarding transmitted information |
US8195153B1 (en) | 2005-08-23 | 2012-06-05 | Emc Corporation | Mobile access to backup and recovery services |
CN100415051C (en) | 2005-08-25 | 2008-08-27 | 华为技术有限公司 | Method for sending paging information |
US7949529B2 (en) | 2005-08-29 | 2011-05-24 | Voicebox Technologies, Inc. | Mobile systems and methods of supporting natural language human-machine interactions |
US8191116B1 (en) | 2005-08-29 | 2012-05-29 | At&T Mobility Ii Llc | User equipment validation in an IP network |
WO2007026745A1 (en) | 2005-08-30 | 2007-03-08 | Matsushita Electric Industrial Co., Ltd. | Wireless device monitoring system |
US7853656B2 (en) | 2005-09-01 | 2010-12-14 | Research In Motion Limited | Method and device for predicting message recipients |
US7886158B2 (en) * | 2005-09-08 | 2011-02-08 | Hitachi, Ltd. | System and method for remote copy of encrypted data |
CN1928818A (en) | 2005-09-09 | 2007-03-14 | 鸿富锦精密工业(深圳)有限公司 | Network device and software updating method thereof |
US8220042B2 (en) | 2005-09-12 | 2012-07-10 | Microsoft Corporation | Creating secure interactive connections with remote resources |
US7660581B2 (en) | 2005-09-14 | 2010-02-09 | Jumptap, Inc. | Managing sponsored content based on usage history |
US8156128B2 (en) * | 2005-09-14 | 2012-04-10 | Jumptap, Inc. | Contextual mobile content placement on a mobile communication facility |
US8229914B2 (en) * | 2005-09-14 | 2012-07-24 | Jumptap, Inc. | Mobile content spidering and compatibility determination |
US7702318B2 (en) | 2005-09-14 | 2010-04-20 | Jumptap, Inc. | Presentation of sponsored content based on mobile transaction event |
US20070073899A1 (en) | 2005-09-15 | 2007-03-29 | Judge Francis P | Techniques to synchronize heterogeneous data sources |
US20110047162A1 (en) | 2005-09-16 | 2011-02-24 | Brindisi Richard G | Handheld device and kiosk system for automated compiling and generating item list information |
CN100486167C (en) | 2005-09-23 | 2009-05-06 | 中兴通讯股份有限公司 | Charged information acquisition system and method, and charge realizing system and method |
US8804695B2 (en) | 2005-09-30 | 2014-08-12 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for providing alerts and notifications |
US8059530B1 (en) | 2005-09-30 | 2011-11-15 | GlobalFoundries, Inc. | System and method for controlling network access |
US7921463B2 (en) | 2005-09-30 | 2011-04-05 | Intel Corporation | Methods and apparatus for providing an insertion and integrity protection system associated with a wireless communication platform |
US7599714B2 (en) | 2005-09-30 | 2009-10-06 | Alcatel-Lucent Usa Inc. | Increasing the range of access point cells for a given throughput in a downlink of a wireless local area network |
US8411579B2 (en) * | 2005-10-04 | 2013-04-02 | Alcatel Lucent | Communication system hierarchical testing systems and methods—entity dependent automatic selection of tests |
US7733224B2 (en) * | 2006-06-30 | 2010-06-08 | Bao Tran | Mesh network personal emergency response appliance |
JP2007115293A (en) | 2005-10-17 | 2007-05-10 | Toshiba Corp | Information storage medium, program, information reproducing method, information reproducing apparatus, data transfer method, and data processing method |
US8280354B2 (en) | 2005-10-27 | 2012-10-02 | Research In Motion Limited | Method and system for provisioning wireless services |
KR100719118B1 (en) | 2005-10-27 | 2007-05-17 | 삼성전자주식회사 | Method and system for limitting a function of device in specific perimeters |
US7760861B1 (en) | 2005-10-31 | 2010-07-20 | At&T Intellectual Property Ii, L.P. | Method and apparatus for monitoring service usage in a communications network |
WO2007053848A1 (en) | 2005-11-01 | 2007-05-10 | Mobile Armor, Llc | Centralized dynamic security control for a mobile device network |
US8719397B2 (en) | 2005-11-03 | 2014-05-06 | Emoze Ltd. | Method and system for email and PIM synchronization and updating |
US8634425B2 (en) | 2005-11-04 | 2014-01-21 | At&T Intellectual Property I, L.P. | Profile sharing across persona |
CN101346634B (en) | 2005-11-04 | 2012-10-24 | 甲骨文国际公司 | System and method for a gatekeeper in a communications network |
US7602746B2 (en) | 2005-11-04 | 2009-10-13 | Cisco Technology, Inc. | Method for optimized layer 2 roaming and policy enforcement in a wireless environment |
US8054778B2 (en) | 2005-11-10 | 2011-11-08 | Junxion, Inc. | LAN/WWAN gateway carrier customization |
US20070109983A1 (en) | 2005-11-11 | 2007-05-17 | Computer Associates Think, Inc. | Method and System for Managing Access to a Wireless Network |
US20070110035A1 (en) | 2005-11-14 | 2007-05-17 | Broadcom Corporation, A California Corporation | Network nodes cooperatively routing traffic flow amongst wired and wireless networks |
US7940685B1 (en) | 2005-11-16 | 2011-05-10 | At&T Intellectual Property Ii, Lp | Method and apparatus for monitoring a network |
US7689216B2 (en) | 2005-11-16 | 2010-03-30 | Research In Motion Limited | Scanning and decoding methods and apparatus for mobile communication devices |
KR20080068752A (en) | 2005-11-17 | 2008-07-23 | 코닌클리케 필립스 일렉트로닉스 엔.브이. | System for managing access control |
US20090172077A1 (en) | 2005-11-23 | 2009-07-02 | David Roxburgh | Apparatus for and a Method of Delivering a Message to a User |
US7508794B2 (en) | 2005-11-29 | 2009-03-24 | Cisco Technology, Inc. | Authorizing an endpoint node for a communication service |
US20070147324A1 (en) | 2005-11-29 | 2007-06-28 | Mcgary Faith | System and method for improved WiFi/WiMax retail installation management |
US20070124077A1 (en) * | 2005-11-30 | 2007-05-31 | Robert Hedlund | An Inventory Stocking and Locating System Utilizing Tags and GPS providing Summarization by Hierarchical Code |
US7860088B2 (en) | 2005-12-01 | 2010-12-28 | Qualcomm Incorporated | Concurrent internet protocol connectivity to an access terminal and a tethered device |
EP1958391A1 (en) | 2005-12-02 | 2008-08-20 | TELEFONAKTIEBOLAGET LM ERICSSON (publ) | Selective rab assignment |
US9002342B2 (en) | 2005-12-02 | 2015-04-07 | Nokia Corporation | System, apparatus, and method for dynamically customizing and configuring applications |
US7469269B2 (en) | 2005-12-05 | 2008-12-23 | At&T Intellectual Property I, L.P. | Method for exchanging content between communication devices |
US8381297B2 (en) | 2005-12-13 | 2013-02-19 | Yoggie Security Systems Ltd. | System and method for providing network security to mobile devices |
US7710932B2 (en) | 2005-12-14 | 2010-05-04 | Motorola, Inc. | Method and apparatus for encouraging routing in a network |
US8077609B2 (en) * | 2005-12-15 | 2011-12-13 | At&T Intellectual Property I, L.P. | Method for providing quality-of-service based services in a packet network |
US7882560B2 (en) | 2005-12-16 | 2011-02-01 | Cisco Technology, Inc. | Methods and apparatus providing computer and network security utilizing probabilistic policy reposturing |
US8413245B2 (en) | 2005-12-16 | 2013-04-02 | Cisco Technology, Inc. | Methods and apparatus providing computer and network security for polymorphic attacks |
US9286469B2 (en) | 2005-12-16 | 2016-03-15 | Cisco Technology, Inc. | Methods and apparatus providing computer and network security utilizing probabilistic signature generation |
US7607041B2 (en) | 2005-12-16 | 2009-10-20 | Cisco Technology, Inc. | Methods and apparatus providing recovery from computer and network security attacks |
CN101341764B (en) | 2005-12-16 | 2012-09-05 | 艾利森电话股份有限公司 | Service of intelligent network |
US8495743B2 (en) | 2005-12-16 | 2013-07-23 | Cisco Technology, Inc. | Methods and apparatus providing automatic signature generation and enforcement |
US8005459B2 (en) * | 2005-12-16 | 2011-08-23 | Research In Motion Limited | System and method of authenticating login credentials in a wireless communication system |
US7948953B2 (en) | 2005-12-19 | 2011-05-24 | Aruba Networks, Inc. | System and method for advertising the same service set identifier for different basic service sets |
US8024397B1 (en) | 2005-12-20 | 2011-09-20 | At&T Intellectual Property Ii, L.P. | System for generating a services repository using a target services roadmap |
US7730123B1 (en) | 2005-12-20 | 2010-06-01 | At&T Intellectual Property Ii, Lp | Software application implemented using services from a services repository generated using a target services roadmap |
US20070140275A1 (en) | 2005-12-21 | 2007-06-21 | Chris Bowman | Method of preventing denial of service attacks in a cellular network |
US20070143851A1 (en) | 2005-12-21 | 2007-06-21 | Fiberlink | Method and systems for controlling access to computing resources based on known security vulnerabilities |
US20070140145A1 (en) | 2005-12-21 | 2007-06-21 | Surender Kumar | System, method and apparatus for authentication of nodes in an Ad Hoc network |
US20070147317A1 (en) | 2005-12-23 | 2007-06-28 | Motorola, Inc. | Method and system for providing differentiated network service in WLAN |
US7650137B2 (en) | 2005-12-23 | 2010-01-19 | Apple Inc. | Account information display for portable communication device |
US8644702B1 (en) | 2005-12-28 | 2014-02-04 | Xi Processing L.L.C. | Computer-implemented system and method for notifying users upon the occurrence of an event |
KR100738545B1 (en) | 2005-12-29 | 2007-07-11 | 삼성전자주식회사 | Quality of service security system and method for service type of wireless local area network |
US7606357B2 (en) | 2005-12-29 | 2009-10-20 | At&T Intellectual Property I, L.P. | Caller identification of recipient that answered a simultaneous or routed communication |
US8494559B1 (en) | 2005-12-30 | 2013-07-23 | At&T Intellectual Property I, L.P. | Method and system for selecting a wireless access technology using location based information |
US7912056B1 (en) | 2005-12-30 | 2011-03-22 | Juniper Networks, Inc. | Dynamic traffic shaping adjustments for distributed multicast replication |
US8190087B2 (en) | 2005-12-31 | 2012-05-29 | Blaze Mobile, Inc. | Scheduling and paying for a banking transaction using an NFC enabled mobile communication device |
US7978686B2 (en) | 2006-01-03 | 2011-07-12 | Hewlett-Packard Company | System and method for feature-based services control using SIP |
IES20060005A2 (en) * | 2006-01-04 | 2007-02-21 | Minroc Techn Promotions Ltd | A drill bit assembly for fluid-operated percussion drill tools |
SE530653C2 (en) * | 2006-01-12 | 2008-07-29 | Vaelinge Innovation Ab | Moisture-proof floor board and floor with an elastic surface layer including a decorative groove |
US7911943B2 (en) | 2006-01-13 | 2011-03-22 | Nokia Corporation | Optimization of PDP context usage |
US8255515B1 (en) | 2006-01-17 | 2012-08-28 | Marvell Israel (M.I.S.L.) Ltd. | Rate limiting per-flow of traffic to CPU on network switching and routing devices |
US7720206B2 (en) | 2006-01-18 | 2010-05-18 | Teoco Corporation | System and method for intelligent data extraction for telecommunications invoices |
EP1974560B1 (en) | 2006-01-20 | 2011-11-30 | Telefonaktiebolaget LM Ericsson (publ) | Policy enforcement within an ip network |
US20070174429A1 (en) | 2006-01-24 | 2007-07-26 | Citrix Systems, Inc. | Methods and servers for establishing a connection between a client system and a virtual machine hosting a requested computing environment |
JP2007199880A (en) | 2006-01-25 | 2007-08-09 | Nec Corp | Communication system, network for qualification examination and setting, communication device, and networking method for use therewith |
EP1977334A4 (en) | 2006-01-25 | 2011-01-12 | Greystripe Inc | System and methods for managing content in pre-existing mobile applications |
US8584226B2 (en) | 2006-01-26 | 2013-11-12 | Iorhythm, Inc. | Method and apparatus for geographically regulating inbound and outbound network communications |
KR20070078862A (en) | 2006-01-31 | 2007-08-03 | 삼성전자주식회사 | Method of providing interoperatibility of heterogeneous network devices capable of error handling and network device using the same |
US8149771B2 (en) | 2006-01-31 | 2012-04-03 | Roundbox, Inc. | Reliable event broadcaster with multiplexing and bandwidth control functions |
US8238913B1 (en) | 2006-02-03 | 2012-08-07 | Sprint Communications Company L.P. | Wireless network augmentation using other wireless networks |
US8042148B2 (en) | 2006-02-07 | 2011-10-18 | Cisco Technology, Inc. | System and method for enforcing policy in a communication network |
US8732098B2 (en) | 2006-02-10 | 2014-05-20 | Numenta, Inc. | Hierarchical temporal memory (HTM) system deployed as web service |
US8027677B2 (en) | 2006-02-13 | 2011-09-27 | Research In Motion Limited | Automatic network selection methods and apparatus using a steered PLMN |
WO2007096884A2 (en) | 2006-02-22 | 2007-08-30 | Elad Barkan | Wireless internet system and method |
EP1827019A1 (en) | 2006-02-23 | 2007-08-29 | Nagravision S.A. | Conditional access method to conditional access data |
US8676925B1 (en) | 2006-02-27 | 2014-03-18 | Jiawei Liu | Method and apparatus for peer-to-peer capturing and sharing of visual information based on incentives |
US20070202850A1 (en) | 2006-02-27 | 2007-08-30 | Sony Ericsson Mobile Communications Ab | Cost estimation in messaging application for a mobile communication device |
KR100744384B1 (en) | 2006-02-28 | 2007-07-30 | 삼성전자주식회사 | Method and apparatus for providing charging information of wireless data communication service |
US20070201502A1 (en) | 2006-02-28 | 2007-08-30 | Maven Networks, Inc. | Systems and methods for controlling the delivery behavior of downloaded content |
US7873001B2 (en) | 2006-03-02 | 2011-01-18 | Tango Networks, Inc. | System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network |
EP1989827B3 (en) | 2006-03-02 | 2015-11-11 | Nokia Corporation | Supporting an access to a destination network via a wireless access network |
US7843901B2 (en) | 2006-03-02 | 2010-11-30 | Tango Networks, Inc. | Call flow system and method for use in a legacy telecommunication system |
CN101496387B (en) | 2006-03-06 | 2012-09-05 | 思科技术公司 | System and method for access authentication in a mobile wireless network |
US7720505B2 (en) | 2006-03-07 | 2010-05-18 | Marvell World Trade Ltd. | Personal lifestyle device |
CN101035308A (en) | 2006-03-09 | 2007-09-12 | 华为技术有限公司 | Radio communication system and mobility management method |
US8826411B2 (en) | 2006-03-15 | 2014-09-02 | Blue Coat Systems, Inc. | Client-side extensions for use in connection with HTTP proxy policy enforcement |
KR101539774B1 (en) | 2006-03-16 | 2015-07-29 | 엠.브루베이커 커티스 | System and method for earning revenue by displaying hyper-related advertisements on moving objects |
US8073444B2 (en) | 2006-03-17 | 2011-12-06 | Camiant, Inc. | Distributed policy services for mobile and nomadic networking |
WO2007107701A2 (en) | 2006-03-22 | 2007-09-27 | British Telecommunications Public Limited Company | Communications device monitoring |
US20070226225A1 (en) | 2006-03-22 | 2007-09-27 | Yiu Timothy C | Mobile collaboration and communication system |
US7774323B2 (en) | 2006-03-27 | 2010-08-10 | Sap Portals Israel Ltd. | Method and apparatus for delivering managed applications to remote locations |
US7720464B2 (en) | 2006-03-28 | 2010-05-18 | Symbol Technologies, Inc. | System and method for providing differentiated service levels to wireless devices in a wireless network |
US7694874B2 (en) | 2006-03-29 | 2010-04-13 | Amazon Technologies, Inc. | Over-the-air device provisioning and activation |
US7797019B2 (en) | 2006-03-29 | 2010-09-14 | Research In Motion Limited | Shared image database with geographic navigation |
CN101047515B (en) | 2006-03-31 | 2010-10-27 | 华为技术有限公司 | Charging associated method and system of applied service |
US7756509B2 (en) | 2006-03-31 | 2010-07-13 | Intel Corporation | Methods and apparatus for providing an access profile system associated with a broadband wireless access network |
US7703126B2 (en) | 2006-03-31 | 2010-04-20 | Intel Corporation | Hierarchical trust based posture reporting and policy enforcement |
WO2007117456A2 (en) | 2006-03-31 | 2007-10-18 | Duane Viazanko | Hybrid system and method for offering in-center and online learning sessions |
US7908358B1 (en) | 2006-03-31 | 2011-03-15 | Amazon Technologies, Inc. | Method and apparatus for network services metering |
US7975184B2 (en) | 2006-04-03 | 2011-07-05 | Donald Goff | Diagnostic access system |
US7826607B1 (en) | 2006-04-04 | 2010-11-02 | At & T Intellectual Property Ii, L.P. | Devices, systems, and methods for migration scheduling |
US8045973B2 (en) | 2006-04-05 | 2011-10-25 | Alcatel Lucent | Mobile device subject to a communication restriction responding to a priority call |
US8639215B2 (en) | 2006-04-07 | 2014-01-28 | Gregory M. McGregor | SIM-centric mobile commerce system for deployment in a legacy network infrastructure |
US20090315735A1 (en) | 2006-04-10 | 2009-12-24 | Bhavani Neeraj S | Patient flow management and analysis using location tracking |
US8548452B2 (en) | 2006-04-13 | 2013-10-01 | Blackberry Limited | System and method for controlling device usage |
US8755335B2 (en) * | 2006-04-13 | 2014-06-17 | At&T Intellectual Property I, L.P. | System and methods for control of a set top box |
US7929960B2 (en) | 2006-04-13 | 2011-04-19 | Research In Motion Limited | System and method for controlling device usage |
US20070255769A1 (en) | 2006-04-14 | 2007-11-01 | International Business Machines Corporation | System of hierarchical policy definition, dissemination, and evaluation |
US7822406B2 (en) | 2006-04-21 | 2010-10-26 | Cisco Technology, Inc. | Simplified dual mode wireless device authentication apparatus and method |
US7693157B2 (en) | 2006-04-25 | 2010-04-06 | Microsoft Corporation | Quality of service support for A/V streams |
US7612712B2 (en) | 2006-04-25 | 2009-11-03 | Rx Networks Inc. | Distributed orbit modeling and propagation method for a predicted and real-time assisted GPS system |
EP2061225A3 (en) | 2006-04-27 | 2009-05-27 | Research In Motion Limited | Method and apparatus for monitoring and controlling wireless resource usage |
US7676673B2 (en) | 2006-04-28 | 2010-03-09 | Bae Systems Information And Electronic Systems Integration Inc. | Multi-level secure (MLS) information network |
US20070254675A1 (en) | 2006-04-28 | 2007-11-01 | Motorola, Inc. | Method and apparatus for distributed call admission control in a wireless network |
US20070255797A1 (en) | 2006-04-28 | 2007-11-01 | Dunn Douglas L | Method for selecting an air interface using an access list on a multi-mode wireless device |
US8219080B2 (en) | 2006-04-28 | 2012-07-10 | Research In Motion Limited | Methods and apparatus for producing a user-controlled PLMN list for a SIM/USIM card with use of a user agent application |
US7809351B1 (en) | 2006-04-28 | 2010-10-05 | Cisco Technology, Inc. | Methods and systems for differential billing of services used during a mobile data service session |
US8175574B1 (en) * | 2006-04-28 | 2012-05-08 | Cisco Technology, Inc. | Methods and systems for selecting one or more charging profiles for a mobile data service session |
KR101196078B1 (en) | 2006-04-28 | 2012-11-01 | 리서치 인 모션 리미티드 | Wlan and wwan connection migration methods and apparatus |
US8407763B2 (en) | 2006-04-28 | 2013-03-26 | Bae Systems Information And Electronic Systems Integration Inc. | Secure network interface device |
WO2007126352A1 (en) | 2006-05-02 | 2007-11-08 | Telefonaktiebolaget Lm Ericsson (Publ) | A method for generating a congestion flag based on measured system load |
KR101085485B1 (en) | 2006-05-03 | 2011-11-21 | 엘지전자 주식회사 | Mobile communication terminal having a plural memorys and method of controlling the same |
US7680478B2 (en) | 2006-05-04 | 2010-03-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Inactivity monitoring for different traffic or service classifications |
US7966263B2 (en) | 2006-05-04 | 2011-06-21 | First Data Corporation | Wireless phone RF presentation instrument with sensor control |
US7864724B2 (en) | 2006-05-05 | 2011-01-04 | Nokia Corporation | Enhanced UE out-of-sync behavior with gated uplink DPCCH or gated downlink F-DPCH or DPCCH transmission |
US7911997B2 (en) | 2006-05-10 | 2011-03-22 | Intel Corporation | Quality of service resource negotiation |
US8489110B2 (en) | 2006-05-12 | 2013-07-16 | At&T Intellectual Property I, L.P. | Privacy control of location information |
WO2008005102A2 (en) | 2006-05-13 | 2008-01-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7792526B2 (en) | 2006-05-15 | 2010-09-07 | Research In Motion Limited | Adjustment of background scanning interval based on network usage |
US7957511B2 (en) | 2006-05-18 | 2011-06-07 | Hewlett-Packard Development Company, L.P. | Providing network services to a network agent |
US7636574B2 (en) | 2006-05-19 | 2009-12-22 | Alcatel-Lucent | Auctioning of message delivery opportunities in a location-based services system |
US7756534B2 (en) | 2006-05-19 | 2010-07-13 | Alcatel-Lucent Usa Inc. | Provision of location-based services utilizing user movement statistics |
US8966018B2 (en) | 2006-05-19 | 2015-02-24 | Trapeze Networks, Inc. | Automated network device configuration and network deployment |
US8194681B2 (en) | 2006-05-23 | 2012-06-05 | Core Wireless Licensing S. á.r. l. | Bridging between AD HOC local networks and internet-based peer-to-peer networks |
JP2007318354A (en) | 2006-05-24 | 2007-12-06 | Fujitsu Ten Ltd | Communication device for mobile and communication method for mobile |
US8565766B2 (en) | 2007-02-05 | 2013-10-22 | Wefi Inc. | Dynamic network connection system and method |
US9148843B2 (en) | 2006-05-25 | 2015-09-29 | Wefi Inc. | Method and system for selecting a wireless network for offloading |
US8644828B2 (en) | 2007-02-05 | 2014-02-04 | Wefi Inc. | Method and system for selecting a wireless network |
WO2007145804A2 (en) | 2006-05-26 | 2007-12-21 | Telcordia Technologies, Inc. | Pre-paid security mechanism in a post-pay telecommunications system |
US8090361B2 (en) | 2006-05-26 | 2012-01-03 | At&T Intellectual Property I, Lp | Methods and systems for monitoring computer systems using wireless devices |
US8392594B2 (en) | 2007-01-30 | 2013-03-05 | Sony Corporation | System and method for effectively providing content to client devices in an electronic network |
US7457814B2 (en) | 2006-05-30 | 2008-11-25 | Microsoft Corporation | Multi-dimensional data classification for user interface customizations |
US20070280453A1 (en) | 2006-05-30 | 2007-12-06 | Motorola, Inc. | Method and system to provide access network information to a service |
US7577453B2 (en) | 2006-06-01 | 2009-08-18 | Trapeze Networks, Inc. | Wireless load balancing across bands |
US20070281680A1 (en) | 2006-06-05 | 2007-12-06 | Vish Raju | Method and system for extending services to cellular devices |
US7616962B2 (en) | 2006-06-07 | 2009-11-10 | Cisco Technology, Inc. | QoS support for VoIP and streaming services |
US8255281B2 (en) | 2006-06-07 | 2012-08-28 | T-Mobile Usa, Inc. | Service management system that enables subscriber-driven changes to service plans |
US8300529B2 (en) | 2006-06-14 | 2012-10-30 | Alcatel Lucent | Service-centric communication network monitoring |
US7711848B2 (en) | 2006-06-15 | 2010-05-04 | Oracle International Corporation | System using session initiation protocol for seamless network switching in a media streaming session |
US7627600B2 (en) | 2006-06-20 | 2009-12-01 | Microsoft Corporation | Automatic layout of unpredictable content from multiple sources |
GB0612288D0 (en) | 2006-06-21 | 2006-08-02 | Nokia Corp | Selection of access interface |
US7676823B2 (en) | 2006-06-21 | 2010-03-09 | Alcatel-Lucent Usa Inc. | User interface methods and apparatus for roaming access to subscription services |
US20070299965A1 (en) | 2006-06-22 | 2007-12-27 | Jason Nieh | Management of client perceived page view response time |
US7540408B2 (en) | 2006-06-22 | 2009-06-02 | Hip Consult Inc. | Apparatus and method for facilitating money or value transfer |
US8375430B2 (en) * | 2006-06-27 | 2013-02-12 | Intel Corporation | Roaming secure authenticated network access method and apparatus |
US9491599B2 (en) * | 2006-06-29 | 2016-11-08 | At&T Mobility Ii Llc | Systems and methods for providing wireless account feature notifications to mobile communication devices |
US8320244B2 (en) | 2006-06-30 | 2012-11-27 | Qualcomm Incorporated | Reservation based MAC protocol |
US7765294B2 (en) | 2006-06-30 | 2010-07-27 | Embarq Holdings Company, Llc | System and method for managing subscriber usage of a communications network |
US8000318B2 (en) | 2006-06-30 | 2011-08-16 | Embarq Holdings Company, Llc | System and method for call routing based on transmission performance of a packet network |
JP2009541871A (en) * | 2006-07-03 | 2009-11-26 | ベイジン ファチ インフォメーション デジタル テクノロジー カンパニー リミテッド | Method, device and system for acquiring information from network by device as service voucher |
US20080010452A1 (en) | 2006-07-07 | 2008-01-10 | Michael Holtzman | Content Control System Using Certificate Revocation Lists |
US20090254857A1 (en) | 2006-07-11 | 2009-10-08 | Christopher Romine | Wireless communication device pre-purchase personalization |
BRPI0621842A2 (en) | 2006-07-11 | 2012-06-12 | Ultra Proizv Elektronskih Naprav D O O | mobile terminal device and its operating methods, merchant network store, authorization and processing center, multiple partner and system, clients and servers in client-server and multiple partner system, computer program product containing program code , computer readable medium, modulated data signal or computer data signal, transaction data exchange system and participant |
US8849297B2 (en) | 2006-07-14 | 2014-09-30 | Qualcomm Incorporated | Call establishment and maintenance in a wireless network |
US8010081B1 (en) | 2006-07-14 | 2011-08-30 | Carrier Iq, Inc. | Auditing system for wireless networks |
US7984130B2 (en) | 2006-07-14 | 2011-07-19 | Cellco Partnership | Multimedia next generation network architecture for IP services delivery based on network and user policy |
KR20090031778A (en) | 2006-07-14 | 2009-03-27 | 콸콤 인코포레이티드 | Methods and apparatus for policy enforcement in a wireless communication system |
US20080039086A1 (en) | 2006-07-14 | 2008-02-14 | Gallagher Michael D | Generic Access to the Iu Interface |
CN100518169C (en) | 2006-07-19 | 2009-07-22 | 华为技术有限公司 | Program exchanging system |
CN1889777A (en) | 2006-07-19 | 2007-01-03 | 华为技术有限公司 | Business exchaging method for switching from 2G to 3G mobile communication system |
US20080018494A1 (en) | 2006-07-24 | 2008-01-24 | Waite Robert K | Traffic Sign Beacon System |
CN101115248B (en) | 2006-07-25 | 2010-05-12 | 联想(北京)有限公司 | Multi-mode terminal and data forwarding method |
US7797406B2 (en) * | 2006-07-27 | 2010-09-14 | Cisco Technology, Inc. | Applying quality of service to application messages in network elements based on roles and status |
US8639837B2 (en) | 2006-07-29 | 2014-01-28 | Blue Coat Systems, Inc. | System and method of traffic inspection and classification for purposes of implementing session ND content control |
US8869262B2 (en) * | 2006-08-03 | 2014-10-21 | Citrix Systems, Inc. | Systems and methods for application based interception of SSL/VPN traffic |
US8495181B2 (en) | 2006-08-03 | 2013-07-23 | Citrix Systems, Inc | Systems and methods for application based interception SSI/VPN traffic |
US20080034063A1 (en) | 2006-08-04 | 2008-02-07 | Research In Motion Limited | Method and system for retrieving a document associated with a message received on a mobile device |
US8086791B2 (en) | 2006-08-08 | 2011-12-27 | Dataram, Inc. | Solid state memory device with PCI controller |
GB0615844D0 (en) | 2006-08-09 | 2006-09-20 | Intuwave Ltd | Mobile telephone programmed with phone call logging capability |
US8161339B2 (en) * | 2006-08-11 | 2012-04-17 | Sharp Kabushiki Kaisha | Content playback apparatus, content playback method, and storage medium |
US20080042387A1 (en) * | 2006-08-14 | 2008-02-21 | Joseph John Lesko | Single-handed lifting skateboard |
US9111088B2 (en) | 2006-08-14 | 2015-08-18 | Quantum Security, Inc. | Policy-based physical security system for restricting access to computer resources and data flow through network equipment |
US7770002B2 (en) * | 2006-08-17 | 2010-08-03 | Fiserv, Inc. | Multi-factor authentication |
DE102006038591B4 (en) | 2006-08-17 | 2008-07-03 | Siemens Ag | Method and device for providing a wireless mesh network |
DE102006038592B4 (en) | 2006-08-17 | 2008-07-03 | Siemens Ag | Method and device for providing a wireless mesh network |
US8223655B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for provisioning resources of a packet network based on collected network performance information |
US8655357B1 (en) | 2006-08-22 | 2014-02-18 | At&T Mobility Ii Llc | Systems and methods for identifying applications on a communications device |
US8531954B2 (en) | 2006-08-22 | 2013-09-10 | Centurylink Intellectual Property Llc | System and method for handling reservation requests with a connection admission control engine |
US8130793B2 (en) * | 2006-08-22 | 2012-03-06 | Embarq Holdings Company, Llc | System and method for enabling reciprocal billing for different types of communications over a packet network |
US8144587B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for load balancing network resources using a connection admission control engine |
US8125897B2 (en) | 2006-08-22 | 2012-02-28 | Embarq Holdings Company Lp | System and method for monitoring and optimizing network performance with user datagram protocol network performance information packets |
US8098579B2 (en) | 2006-08-22 | 2012-01-17 | Embarq Holdings Company, LP | System and method for adjusting the window size of a TCP packet through remote network elements |
US7843831B2 (en) | 2006-08-22 | 2010-11-30 | Embarq Holdings Company Llc | System and method for routing data on a packet network |
US7833101B2 (en) | 2006-08-24 | 2010-11-16 | Cfph, Llc | Secondary game |
US8216056B2 (en) | 2007-02-13 | 2012-07-10 | Cfph, Llc | Card picks for progressive prize |
US7585217B2 (en) | 2006-09-05 | 2009-09-08 | Cfph, Llc | Secondary game |
US20080051076A1 (en) * | 2006-08-25 | 2008-02-28 | O'shaughnessy John | System And Method For Mobile Device Application Management |
EP1892882A1 (en) | 2006-08-25 | 2008-02-27 | Alcatel Lucent | Method of providing QoS for a flow |
US8266681B2 (en) | 2006-08-29 | 2012-09-11 | Ca, Inc. | System and method for automatic network logon over a wireless network |
US8948206B2 (en) | 2006-08-31 | 2015-02-03 | Telefonaktiebolaget Lm Ericsson (Publ) | Inclusion of quality of service indication in header compression channel |
US8191124B2 (en) * | 2006-09-06 | 2012-05-29 | Devicescape Software, Inc. | Systems and methods for acquiring network credentials |
US20080066181A1 (en) | 2006-09-07 | 2008-03-13 | Microsoft Corporation | DRM aspects of peer-to-peer digital content distribution |
US20080065746A1 (en) * | 2006-09-07 | 2008-03-13 | Ace*Comm Corporation | Consumer configurable mobile communication web filtering solution |
US8160056B2 (en) | 2006-09-08 | 2012-04-17 | At&T Intellectual Property Ii, Lp | Systems, devices, and methods for network routing |
US8184530B1 (en) | 2006-09-08 | 2012-05-22 | Sprint Communications Company L.P. | Providing quality of service (QOS) using multiple service set identifiers (SSID) simultaneously |
US7835275B1 (en) * | 2006-09-08 | 2010-11-16 | Sprint Communications Company L.P. | Dynamic assignment of quality of service (QoS) to an active session in an ipsec tunnel |
WO2008033962A2 (en) | 2006-09-12 | 2008-03-20 | Hewlett-Packard Development Company, L.P. | Device and network capable of mobile device management |
US8131840B1 (en) | 2006-09-12 | 2012-03-06 | Packet Plus, Inc. | Systems and methods for data stream analysis using embedded design logic |
US8290820B2 (en) | 2006-09-13 | 2012-10-16 | Microsoft Corporation | Methods of maintaining a journal of media encounters between co-existing portable devices |
US8271045B2 (en) | 2006-09-13 | 2012-09-18 | AT&T Intellectual Property, I, L.P | Methods and apparatus to display service quality to a user of a multiple mode communication device |
CN101155343B (en) | 2006-09-29 | 2012-09-05 | 华为技术有限公司 | Method and system for adding multicast broadcasting service to terminal in wireless network |
US7873540B2 (en) | 2006-09-20 | 2011-01-18 | First Data Corporation | Virtual terminal payer authorization systems and methods |
US8291439B2 (en) | 2006-09-21 | 2012-10-16 | Convergys Information Management Group, Inc. | Data platform web services application programming interface |
WO2008036938A2 (en) | 2006-09-21 | 2008-03-27 | T-Mobile Usa, Inc. | Wireless device registration, such as automatic registration of a wi-fi enabled device |
US7734784B1 (en) | 2006-09-22 | 2010-06-08 | Juniper Networks, Inc. | Dynamic service activation using COPS-PR to support outsourcing and configuration models for policy control |
US8484326B2 (en) | 2006-09-28 | 2013-07-09 | Rockstar Bidco Lp | Application server billing |
US8068824B2 (en) | 2006-09-29 | 2011-11-29 | Avaya, Inc. | Automated reconnection of interrupted voice call session |
US20080081606A1 (en) | 2006-09-29 | 2008-04-03 | Cole Terry L | Connection manager with branded connection notification |
US20080080457A1 (en) | 2006-09-29 | 2008-04-03 | Cole Terry L | Connection manager responsive to power state |
US8260252B2 (en) | 2006-10-02 | 2012-09-04 | The Nielsen Company (Us), Llc | Method and apparatus for collecting information about portable device usage |
US7860532B2 (en) * | 2006-10-02 | 2010-12-28 | Nokia Corporation | Method and system for initiating a communication from an arbitrary document |
US8793304B2 (en) | 2006-10-05 | 2014-07-29 | Microsoft Corporation | Differentiated management of wireless connectivity |
US7885654B2 (en) | 2006-10-10 | 2011-02-08 | Apple Inc. | Dynamic carrier selection |
US8015249B2 (en) | 2006-10-10 | 2011-09-06 | Microsoft Corporation | Mitigating data usage in messaging applications |
US8739035B2 (en) | 2006-10-11 | 2014-05-27 | Intel Corporation | Controls and indicators with on-screen cognitive aids |
US8050705B2 (en) | 2006-10-12 | 2011-11-01 | Dell Products L.P. | Subscriber identity module unlocking service portal |
US20080089303A1 (en) | 2006-10-13 | 2008-04-17 | Jeff Wirtanen | System and method for deactivating IP sessions of lower priority |
US20080091807A1 (en) * | 2006-10-13 | 2008-04-17 | Lyle Strub | Network service usage management systems and methods |
EP2078430B1 (en) | 2006-10-19 | 2015-03-18 | BlackBerry Limited | Client device method and apparatus for routing a call |
US8095124B2 (en) | 2006-10-20 | 2012-01-10 | Verizon Patent And Licensing Inc. | Systems and methods for managing and monitoring mobile data, content, access, and usage |
US8244241B2 (en) | 2006-10-24 | 2012-08-14 | Research In Motion Limited | WLAN network information caching |
US8032899B2 (en) | 2006-10-26 | 2011-10-04 | International Business Machines Corporation | Providing policy-based operating system services in a hypervisor on a computing system |
US8010990B2 (en) | 2006-10-26 | 2011-08-30 | Intel Corporation | Acceleration of packet flow classification in a virtualized system |
US7634388B2 (en) | 2006-10-26 | 2009-12-15 | International Business Machines Corporation | Providing policy-based operating system services in an operating system on a computing system |
US8095175B2 (en) | 2006-10-26 | 2012-01-10 | Mcmaster University | WLAN-to-WWAN handover methods and apparatus using a WLAN support node having a WWAN interface |
US8531995B2 (en) | 2006-11-01 | 2013-09-10 | At&T Intellectual Property I, L.P. | Systems and methods for location management and emergency support for a voice over internet protocol device |
US9288276B2 (en) | 2006-11-03 | 2016-03-15 | At&T Intellectual Property I, L.P. | Application services infrastructure for next generation networks including a notification capability and related methods and computer program products |
US20080126287A1 (en) | 2006-11-03 | 2008-05-29 | Motorola, Inc. | Method for management of policy conflict in a policy continuum |
US20080125079A1 (en) * | 2006-11-07 | 2008-05-29 | O'neil Douglas | Methods, systems and computer products for remote monitoring and control of application usage on mobile devices |
US8116223B2 (en) | 2006-11-09 | 2012-02-14 | Ivt Technology Inc. | System and method for supporting automatic establishing and disconnecting several wireless connections |
US8126396B2 (en) | 2006-11-09 | 2012-02-28 | Broadcom Corporation | Wireless network that utilizes concurrent interfering transmission and MIMO techniques |
US8279864B2 (en) | 2006-11-10 | 2012-10-02 | Verizon Patent And Licensing Inc. | Policy based quality of service and encryption over MPLS networks |
US7941184B2 (en) * | 2006-11-10 | 2011-05-10 | Dell Products L.P. | Methods and systems for managing and/or tracking use of subscriber identity module components |
US8265004B2 (en) | 2006-11-11 | 2012-09-11 | Microsoft Corporation | Transferring data using ad hoc networks |
US8149748B2 (en) | 2006-11-14 | 2012-04-03 | Raytheon Company | Wireless data networking |
US7822849B2 (en) | 2006-11-16 | 2010-10-26 | Path Solutions, Inc. | Apparatus and method for measuring and using response to SNMP requests to provide real-time network parameter estimates in a network management zone |
US20080120174A1 (en) | 2006-11-16 | 2008-05-22 | Verizon Services Organization Inc. | Method and system for flexible product and service bundling |
US20080120668A1 (en) | 2006-11-18 | 2008-05-22 | Frank Chuen-Foo Yau | Integrated IPTV display set and methods |
US9047465B2 (en) | 2006-11-22 | 2015-06-02 | At&T Intellectual Property I, L.P. | Methods and apparatus for automatic security checking in systems that monitor for improper network usage |
US8583821B1 (en) | 2006-11-27 | 2013-11-12 | Marvell International Ltd. | Streaming traffic classification method and apparatus |
US8121049B2 (en) | 2006-11-29 | 2012-02-21 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangement for controlling service level agreements in a mobile network |
JP4374015B2 (en) | 2006-11-30 | 2009-12-02 | 株式会社東芝 | Data transmitting apparatus, data receiving apparatus, and data communication system |
US8229394B2 (en) | 2006-11-30 | 2012-07-24 | Sony Ericsson Mobile Communications Ab | Methods, devices and computer program products for tracking usage of a network by a plurality of users of a mobile phone |
KR100822707B1 (en) * | 2006-12-01 | 2008-04-18 | 한국전자통신연구원 | Apparatus and method for managing quality of service in integrated network of heterogeneous mobile networks |
US20080132268A1 (en) * | 2006-12-01 | 2008-06-05 | Cingular Wireless Ii, Llc | Dynamic quality of service adaptation in packet data communications |
US7965983B1 (en) | 2006-12-04 | 2011-06-21 | Sprint Spectrum L.P. | Method and system for conveying medical information to a medical service person |
JP4885693B2 (en) * | 2006-12-05 | 2012-02-29 | 株式会社オートネットワーク技術研究所 | Electrical junction box |
US8284740B2 (en) | 2006-12-11 | 2012-10-09 | Intel Corporation | Techniques to share multimedia and enable cellular phone conference calling using ad-hoc wireless networks |
US8347378B2 (en) | 2006-12-12 | 2013-01-01 | International Business Machines Corporation | Authentication for computer system management |
EP1940077B1 (en) | 2006-12-13 | 2010-03-10 | Alcatel Lucent | Remote activation of home devices |
WO2008072093A2 (en) | 2006-12-13 | 2008-06-19 | Quickplay Media Inc. | Mobile media platform |
US8612320B2 (en) | 2006-12-14 | 2013-12-17 | Corelogic Solutions, Llc | Method and apparatus for detecting fraudulent loans |
US8571598B2 (en) | 2006-12-18 | 2013-10-29 | Intel Corporation | Method and apparatus for location-based wireless connection and pairing |
CN101080055B (en) | 2006-12-21 | 2010-06-16 | 腾讯科技(深圳)有限公司 | A method, system and device for quickly browsing webpage via mobile phone browser |
CA2571891C (en) | 2006-12-21 | 2015-11-24 | Bce Inc. | Device authentication and secure channel management for peer-to-peer initiated communications |
WO2008080139A1 (en) | 2006-12-22 | 2008-07-03 | Integrated Mobile, Inc. | System and method for managing mobile devices and services |
US8326267B2 (en) | 2006-12-28 | 2012-12-04 | United States Cellular Corporation | Application access control in a mobile environment |
WO2008080430A1 (en) | 2006-12-29 | 2008-07-10 | Telecom Italia S.P.A. | METHOD AND SYSTEM FOR ENFORCING SECURITY POLICIES IN MANETs |
US7725594B2 (en) | 2006-12-29 | 2010-05-25 | Verizon Patent And Licensing Inc. | Assigning priority to network traffic at customer premises |
US7975053B2 (en) | 2006-12-29 | 2011-07-05 | United States Cellular Corporation | Establishing network policy for session-unaware mobile-device applications |
US20080167033A1 (en) | 2007-01-04 | 2008-07-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Apparatus for Cost-Based Network Selection |
EP1942698A1 (en) | 2007-01-07 | 2008-07-09 | Apple Inc. | Method and system for mobile device activation |
US8666366B2 (en) | 2007-06-22 | 2014-03-04 | Apple Inc. | Device activation and access |
US8239688B2 (en) | 2007-01-07 | 2012-08-07 | Apple Inc. | Securely recovering a computing device |
US7840685B2 (en) | 2007-01-07 | 2010-11-23 | Apple Inc. | Handheld computer having dynamic network transport selection according to a media type of a request |
US20090017809A1 (en) | 2007-01-08 | 2009-01-15 | Jethi Rashesh J | Support service architecture for a mobile virtual network operator |
US20080180391A1 (en) * | 2007-01-11 | 2008-07-31 | Joseph Auciello | Configurable electronic interface |
CN100499463C (en) * | 2007-01-12 | 2009-06-10 | 北京时代亮点科技发展有限公司 | Peer-to-peer network transmission method facing moving terminal |
US7865212B2 (en) | 2007-01-17 | 2011-01-04 | Research In Motion Limited | Methods and apparatus for use in transferring user data between two different mobile communication devices using a removable memory card |
GB0700968D0 (en) | 2007-01-18 | 2007-02-28 | Glue4 Technologles Ltd | Communication system |
EP2122531B1 (en) | 2007-01-19 | 2014-10-01 | BlackBerry Limited | Selectively wiping a remote device |
US20080263363A1 (en) | 2007-01-22 | 2008-10-23 | Spyrus, Inc. | Portable Data Encryption Device with Configurable Security Functionality and Method for File Encryption |
US7940751B2 (en) | 2007-01-23 | 2011-05-10 | Broadcom Corporation | Personal area network data encapsulation in WLAN communications |
US8621540B2 (en) | 2007-01-24 | 2013-12-31 | Time Warner Cable Enterprises Llc | Apparatus and methods for provisioning in a download-enabled system |
US20080183811A1 (en) * | 2007-01-25 | 2008-07-31 | Kotras Timothy W | Collaborative Multi-User Method and System |
US8104080B2 (en) | 2007-01-26 | 2012-01-24 | Microsoft Corporation | Universal schema for representing management policy |
US7860872B2 (en) | 2007-01-29 | 2010-12-28 | Nikip Technology Ltd. | Automated media analysis and document management system |
US7783703B2 (en) | 2007-01-29 | 2010-08-24 | Sony Corporation | Shared home media platform to support multi-user control |
WO2008094579A1 (en) | 2007-01-29 | 2008-08-07 | Genband Inc. | Methods, systems, and computer program products for synchronizing subscriber feature data across multiple domains |
US7633438B2 (en) | 2007-01-29 | 2009-12-15 | Research In Motion Limited | Method of downloading ephemeris data based on user activity |
WO2008094960A2 (en) | 2007-01-30 | 2008-08-07 | Invidi Technologies Corporation | Asset targeting system for limited resource environments |
US8086216B2 (en) | 2007-01-31 | 2011-12-27 | Alcatel Lucent | Mobility aware policy and charging control in a wireless communication network |
KR101301775B1 (en) | 2007-01-31 | 2013-09-02 | 삼성전자주식회사 | Method for executing distributed verification for measured data in sensor network and system for executing the method |
US8000276B2 (en) | 2007-02-05 | 2011-08-16 | Wefi, Inc. | Providing easy access to radio networks |
CN201146509Y (en) * | 2007-02-06 | 2008-11-05 | 南宁亚奥数码有限公司 | System for transmitting and receiving data of wireless emergency mobile platform rapidly and credibly |
US7873710B2 (en) | 2007-02-06 | 2011-01-18 | 5O9, Inc. | Contextual data communication platform |
US7971228B2 (en) | 2007-02-07 | 2011-06-28 | Cisco Technology, Inc. | System and method for providing application-specific on-line charging in a communications environment |
EP2124401A4 (en) | 2007-02-13 | 2012-09-26 | Nec Corp | Mobile terminal management system, network device, and mobile terminal operation control method used for them |
CA2578690A1 (en) | 2007-02-15 | 2008-08-15 | Ascalade Communications Inc. | Telephone background screensaver with live internet content |
CN101247384B (en) * | 2007-02-15 | 2012-01-11 | 株式会社日立制作所 | Content management system and method |
US8620257B2 (en) | 2007-02-20 | 2013-12-31 | At&T Intellectual Property I, L.P. | Systems and methods for location management and emergency support for a voice over internet protocol device |
US8015133B1 (en) | 2007-02-20 | 2011-09-06 | Sas Institute Inc. | Computer-implemented modeling systems and methods for analyzing and predicting computer network intrusions |
US8472371B1 (en) | 2007-02-21 | 2013-06-25 | At&T Mobility Ii Llc | Roaming support for wireless access subscriber over fixed IP access networks |
US9014973B2 (en) | 2007-02-23 | 2015-04-21 | At&T Intellectual Property I, L.P. | Methods for obtaining a navigation track between a first and a second location at a client device using location information obtained from a server device and related devices and computer program products |
US7797060B2 (en) | 2007-02-27 | 2010-09-14 | Rockwell Automation Technologies, Inc. | Prioritization associated with controller engine instances |
US8064881B2 (en) | 2007-02-28 | 2011-11-22 | Embarq Holdings Company, Llc | System and method for remotely managing wireless devices |
US8243597B2 (en) | 2007-03-01 | 2012-08-14 | International Business Machines Corporation | Application layer synchronous traffic shaping |
US8595357B2 (en) | 2007-03-01 | 2013-11-26 | Cisco Technology, Inc. | System and method for hosted network management |
US8442030B2 (en) | 2007-03-01 | 2013-05-14 | Extreme Networks, Inc. | Software control plane for switches and routers |
JP5208138B2 (en) | 2007-03-06 | 2013-06-12 | スペクトラム ブリッジ, インコーポレイテッド | Spectrum management system and method |
US20100142478A1 (en) | 2007-03-07 | 2010-06-10 | Nokia Corporation | Neighbor network advertisement |
WO2008107510A1 (en) | 2007-03-07 | 2008-09-12 | Cvon Innovations Ltd | An access control method and system |
US9191822B2 (en) | 2007-03-09 | 2015-11-17 | Sony Corporation | Device-initiated security policy |
US8340678B1 (en) | 2007-03-09 | 2012-12-25 | At&T Mobility Ii Llc | Indicating radio bearer information to network applications |
US7865589B2 (en) | 2007-03-12 | 2011-01-04 | Citrix Systems, Inc. | Systems and methods for providing structured policy expressions to represent unstructured data in a network appliance |
US7801985B1 (en) | 2007-03-22 | 2010-09-21 | Anchor Intelligence, Inc. | Data transfer for network interaction fraudulence detection |
US8214503B2 (en) | 2007-03-23 | 2012-07-03 | Oracle International Corporation | Factoring out dialog control and call control |
CN101272256B (en) | 2007-03-23 | 2011-07-06 | 华为技术有限公司 | Business handling method and system, policy control and charging regulation functional entity |
US9258346B2 (en) | 2007-03-26 | 2016-02-09 | International Business Machines Corporation | System, method and program for controlling MP3 player |
US9419867B2 (en) | 2007-03-30 | 2016-08-16 | Blue Coat Systems, Inc. | Data and control plane architecture for network application traffic management device |
EP1978772A1 (en) | 2007-04-02 | 2008-10-08 | British Telecommunications Public Limited Company | Authentication policy |
GB2448190A (en) | 2007-04-05 | 2008-10-08 | Cvon Innovations Ltd | Data delivery evaluation system |
US8239520B2 (en) | 2007-04-05 | 2012-08-07 | Alcatel Lucent | Network service operational status monitoring |
US8270965B2 (en) | 2007-04-05 | 2012-09-18 | Microsoft Corporation | Signaling over cellular networks to reduce the Wi-Fi energy consumption of mobile devices |
US9042263B1 (en) * | 2007-04-06 | 2015-05-26 | Netapp, Inc. | Systems and methods for comparative load analysis in storage networks |
US8229458B2 (en) | 2007-04-08 | 2012-07-24 | Enhanced Geographic Llc | Systems and methods to determine the name of a location visited by a user of a wireless device |
US9501803B2 (en) | 2007-04-12 | 2016-11-22 | Siemens Industry, Inc. | Devices, systems, and methods for monitoring energy systems |
US8307404B2 (en) | 2007-04-16 | 2012-11-06 | Microsoft Corporation | Policy-management infrastructure |
US7856226B2 (en) | 2007-04-17 | 2010-12-21 | Aylus Networks, Inc. | Systems and methods for IMS user sessions with dynamic service selection |
US8254915B2 (en) | 2007-04-17 | 2012-08-28 | Embarq Holdings Company, Llc | System and method for enabling subscribers of a communications carrier to access a network of other subscribers |
US7792538B2 (en) | 2007-04-17 | 2010-09-07 | Embarq Holdings Company, Llc | System and method for enabling subscribers of a communications carrier to access a network of wireless access points of subscribers of other communications carriers |
US20080263348A1 (en) | 2007-04-17 | 2008-10-23 | Texas Instruments Incorporated | Dynamic asymmetric partitioning of program code memory in network connected devices |
US8242959B2 (en) | 2007-04-18 | 2012-08-14 | Trueposition, Inc. | Sparsed U-TDOA wireless location networks |
US7903655B2 (en) | 2007-04-19 | 2011-03-08 | Hewlett-Packard Development Company, L.P. | Marked packet forwarding |
US8103285B2 (en) | 2007-04-19 | 2012-01-24 | Kyocera Corporation | Apparatus, system and method for determining a geographical location of a portable communication device |
US8656472B2 (en) | 2007-04-20 | 2014-02-18 | Microsoft Corporation | Request-specific authentication for accessing web service resources |
US7979896B2 (en) | 2007-04-20 | 2011-07-12 | Microsoft Corporation | Authorization for access to web service resources |
US8091087B2 (en) | 2007-04-20 | 2012-01-03 | Microsoft Corporation | Scheduling of new job within a start time range based on calculated current load and predicted load value of the new job on media resources |
US20080270212A1 (en) | 2007-04-25 | 2008-10-30 | Jeffrey Blight | Method, apparatus or software for managing a data processing process |
US8112435B2 (en) | 2007-04-27 | 2012-02-07 | Wififee, Llc | System and method for modifying internet traffic and controlling search responses |
CN101299660B (en) | 2007-04-30 | 2010-12-08 | 华为技术有限公司 | Method, system and equipment for executing security control |
US8065365B2 (en) | 2007-05-02 | 2011-11-22 | Oracle International Corporation | Grouping event notifications in a database system |
US7684370B2 (en) | 2007-05-03 | 2010-03-23 | Research In Motion Limited | Adaptive beamforming configuration methods and apparatus for wireless access points serving as handoff indication mechanisms in wireless local area networks |
US7801523B1 (en) | 2007-05-08 | 2010-09-21 | Amdocs Software Systems Limited | System, method, and computer program product for charging a roaming network for a chargeable event |
US20080293395A1 (en) | 2007-05-21 | 2008-11-27 | Motorola, Inc. | Using downloadable specifications to render a user interface on a mobile device |
US7930327B2 (en) | 2007-05-21 | 2011-04-19 | International Business Machines Corporation | Method and apparatus for obtaining the absolute path name of an open file system object from its file descriptor |
US8358638B2 (en) | 2007-05-24 | 2013-01-22 | Wefi, Inc. | Dynamically created and expanded wireless network |
US20080298230A1 (en) | 2007-05-30 | 2008-12-04 | Luft Siegfried J | Scheduling of workloads in a distributed compute environment |
US8365272B2 (en) | 2007-05-30 | 2013-01-29 | Yoggie Security Systems Ltd. | System and method for providing network and computer firewall protection with dynamic address isolation to a device |
JP5000381B2 (en) | 2007-05-30 | 2012-08-15 | 京セラ株式会社 | COMMUNICATION SYSTEM, THRESHOLD MANAGEMENT SERVER, RADIO COMMUNICATION DEVICE, AND COMMUNICATION METHOD |
US8595186B1 (en) | 2007-06-06 | 2013-11-26 | Plusmo LLC | System and method for building and delivering mobile widgets |
US8340625B1 (en) | 2007-06-06 | 2012-12-25 | Sprint Communications Company L.P. | Alternative techniques for processing wireless communication backhaul |
US8191106B2 (en) | 2007-06-07 | 2012-05-29 | Alcatel Lucent | System and method of network access security policy management for multimodal device |
US8355696B1 (en) | 2007-06-07 | 2013-01-15 | Sprint Communications Company L.P. | Automated device activation |
US9198030B2 (en) | 2007-06-12 | 2015-11-24 | Broadcom Corporation | Method and system for a networked self-configuring communication device utilizing user preference information |
US8442015B2 (en) | 2007-07-20 | 2013-05-14 | Broadcom Corporation | Method and system for an atomizing function of a mobile device |
GB2450193A (en) | 2007-06-12 | 2008-12-17 | Cvon Innovations Ltd | Method and system for managing credits via a mobile device |
US8155620B2 (en) | 2007-06-13 | 2012-04-10 | Qualcomm Incorporated | Method and apparatus for accounting in a mobile data packet network |
GB2450144A (en) | 2007-06-14 | 2008-12-17 | Cvon Innovations Ltd | System for managing the delivery of messages |
WO2008156745A1 (en) | 2007-06-15 | 2008-12-24 | Vonage Network Inc. | Method and apparatus for information conveyance for end users of a packet based communication network |
US20080313730A1 (en) | 2007-06-15 | 2008-12-18 | Microsoft Corporation | Extensible authentication management |
US20080319879A1 (en) | 2007-06-15 | 2008-12-25 | Jim Carroll | Optimized Communication Billing Management System |
US8243596B2 (en) | 2007-06-21 | 2012-08-14 | Intel Corporation | Distributing intelligence across networks |
US20080320596A1 (en) | 2007-06-22 | 2008-12-25 | Feng Chi Wang | Distributed digital rights management system and methods for use therewith |
US8046429B2 (en) | 2007-06-25 | 2011-10-25 | Nokia Corporation | Service mobility for composed components |
US8522249B2 (en) | 2007-06-27 | 2013-08-27 | Bluestreak Technology, Inc. | Management of software implemented services in processor-based devices |
US8019820B2 (en) | 2007-06-27 | 2011-09-13 | Research In Motion Limited | Service gateway decomposition in a network environment including IMS |
US7945238B2 (en) | 2007-06-28 | 2011-05-17 | Kajeet, Inc. | System and methods for managing the utilization of a communications device |
US20090006229A1 (en) | 2007-06-28 | 2009-01-01 | Embarq Holdings Company, Llc | System and method for telephony billing codes |
US8463238B2 (en) | 2007-06-28 | 2013-06-11 | Apple Inc. | Mobile device base station |
US9325737B2 (en) | 2007-06-28 | 2016-04-26 | Motorola Solutions, Inc. | Security based network access selection |
US8929857B2 (en) | 2007-06-28 | 2015-01-06 | Kajeet, Inc. | Policy management of electronic devices |
CN101335666B (en) | 2007-06-29 | 2013-03-20 | 杭州华三通信技术有限公司 | Configuration transmitting method, access control equipment and access point |
WO2009006630A1 (en) | 2007-07-05 | 2009-01-08 | Starent Networks, Corp | System and method for reducing latency in call setup and teardown |
CA2695010A1 (en) | 2007-07-06 | 2009-01-15 | Telefonaktiebolaget L M Ericsson (Publ) | Congestion control in a transmission node |
US8031687B2 (en) | 2007-07-13 | 2011-10-04 | Kyocera Corporation | Optimized usage of access technology in a multi-mode architecture |
US8572256B2 (en) | 2007-07-16 | 2013-10-29 | Qualcomm Incorporated | Method for supporting multiple diversified data applications with efficient use of network resources |
US8108680B2 (en) | 2007-07-23 | 2012-01-31 | Murray Mark R | Preventing unauthorized poaching of set top box assets |
US8060074B2 (en) | 2007-07-30 | 2011-11-15 | Mobile Iron, Inc. | Virtual instance architecture for mobile device management systems |
US7844728B2 (en) | 2007-07-31 | 2010-11-30 | Alcatel-Lucent Usa Inc. | Packet filtering/classification and/or policy control support from both visited and home networks |
US8184590B2 (en) | 2007-08-02 | 2012-05-22 | Counterpath Technologies Inc. | Method and system for handoff between wireless networks |
EP2188696A4 (en) * | 2007-08-08 | 2014-09-17 | Innopath Software Inc | Workflow-based user interface system for mobile devices management |
US8375136B2 (en) | 2007-08-08 | 2013-02-12 | Innopath Software, Inc. | Defining and implementing policies on managed object-enabled mobile devices |
US20090042536A1 (en) | 2007-08-08 | 2009-02-12 | Tellebs Vienna, Inc. | Method and apparatus to manage femtocell traffic |
US20090049518A1 (en) | 2007-08-08 | 2009-02-19 | Innopath Software, Inc. | Managing and Enforcing Policies on Mobile Devices |
US20090048913A1 (en) | 2007-08-13 | 2009-02-19 | Research In Motion Limited | System and method for facilitating targeted mobile advertisement using metadata embedded in the application content |
CN101127988A (en) | 2007-08-13 | 2008-02-20 | 中兴通讯股份有限公司 | An interactive device management method |
EP2026514A1 (en) | 2007-08-14 | 2009-02-18 | Nokia Siemens Networks S.p.A. | Resource management method for multi acces networks |
US8050690B2 (en) | 2007-08-14 | 2011-11-01 | Mpanion, Inc. | Location based presence and privacy management |
US8099455B2 (en) | 2007-08-16 | 2012-01-17 | Sony Ericsson Mobile Communications Ab | Notifying remote devices of available content |
US20090047989A1 (en) | 2007-08-16 | 2009-02-19 | Questox Corporation | Cellular notebook |
US7826427B2 (en) | 2007-08-22 | 2010-11-02 | Intel Corporation | Method for secure transfer of data to a wireless device for enabling multi-network roaming |
US8594665B2 (en) | 2007-08-27 | 2013-11-26 | At&T Intellectual Property I, L.P. | Communication devices that utilize various communication networks to satisfy communication needs of device applications |
US8332375B2 (en) | 2007-08-29 | 2012-12-11 | Nirvanix, Inc. | Method and system for moving requested files from one storage location to another |
US8500533B2 (en) | 2007-08-29 | 2013-08-06 | Cfph, Llc | Game with chance element and strategy component that can be copied |
US8107953B2 (en) | 2007-08-31 | 2012-01-31 | Tracfone Wireless, Inc. | System and method for activating services on a wireless device |
US7929959B2 (en) | 2007-09-01 | 2011-04-19 | Apple Inc. | Service provider activation |
US9451450B2 (en) | 2007-09-01 | 2016-09-20 | Apple Inc. | Postponed carrier configuration |
JP2009060012A (en) | 2007-09-03 | 2009-03-19 | Canon Inc | Organic field-effect element and manufacturing method therefor, and display device |
US20090068984A1 (en) | 2007-09-06 | 2009-03-12 | Burnett R Alan | Method, apparatus, and system for controlling mobile device use |
AU2008299011B2 (en) | 2007-09-10 | 2013-09-12 | Theodore S. Rappaport | Clearinghouse system for determining available network equipment |
CN101123553A (en) | 2007-09-11 | 2008-02-13 | 东南大学 | Mobile wireless local network access device and method based on code division multi-address technology |
US8341083B1 (en) | 2007-09-12 | 2012-12-25 | Devicefidelity, Inc. | Wirelessly executing financial transactions |
US8131281B1 (en) | 2007-09-12 | 2012-03-06 | Oceans' Edge, Inc. | Mobile device monitoring and control system |
US20090079699A1 (en) * | 2007-09-24 | 2009-03-26 | Motorola, Inc. | Method and device for associating objects |
US8374102B2 (en) | 2007-10-02 | 2013-02-12 | Tellabs Communications Canada, Ltd. | Intelligent collection and management of flow statistics |
US8780857B2 (en) | 2007-10-09 | 2014-07-15 | Qualcomm Incorporated | Methods and apparatus for mobility support between network domains |
US8270972B2 (en) | 2007-10-23 | 2012-09-18 | Motorola Mobility Llc | Method and apparatus for detecting an alternate wireless communication network |
US8086398B2 (en) | 2007-10-25 | 2011-12-27 | Research In Motion Limited | Sending location information from within a communication application |
US7831701B2 (en) | 2007-10-27 | 2010-11-09 | At&T Mobility Ii Llc | Cascading policy management deployment architecture |
JP4444327B2 (en) | 2007-10-31 | 2010-03-31 | 京セラコミュニケーションシステム株式会社 | Data communication fee billing system, program, recording medium, and data communication fee billing method |
US7970350B2 (en) | 2007-10-31 | 2011-06-28 | Motorola Mobility, Inc. | Devices and methods for content sharing |
KR20090044740A (en) | 2007-11-01 | 2009-05-07 | 삼성전자주식회사 | System and method for changing an access point in a wireless network system |
CN101965563A (en) | 2007-11-05 | 2011-02-02 | 维斯托公司 | Service management system & associated methodology of providing service related message prioritization in a mobile client |
US8484327B2 (en) | 2007-11-07 | 2013-07-09 | Mcafee, Inc. | Method and system for generic real time management of devices on computers connected to a network |
US8108522B2 (en) * | 2007-11-14 | 2012-01-31 | International Business Machines Corporation | Autonomic definition and management of distributed application information |
US8180886B2 (en) | 2007-11-15 | 2012-05-15 | Trustwave Holdings, Inc. | Method and apparatus for detection of information transmission abnormalities |
US8514927B2 (en) | 2007-11-20 | 2013-08-20 | Texas Instruments Incorporated | Compression code for transferring rate matched data between devices |
US20090132860A1 (en) | 2007-11-21 | 2009-05-21 | Inventec Corporation | System and method for rapidly diagnosing bugs of system software |
US20100248719A1 (en) | 2007-11-23 | 2010-09-30 | Aastra Telecom Schwiez Ag | Self-configuring man-machine interface for a communication terminal |
DE602007008111D1 (en) | 2007-11-27 | 2010-09-09 | Fraunhofer Ges Forschung | Wireless telecommunication system with base station, relay node and global scheduling method |
US8195661B2 (en) | 2007-11-27 | 2012-06-05 | Umber Systems | Method and apparatus for storing data on application-level activity and other user information to enable real-time multi-dimensional reporting about user of a mobile data network |
US8730842B2 (en) | 2007-11-29 | 2014-05-20 | Jasper Wireless, Inc. | Connectivity management and diagnostics for cellular data devices |
US20090149154A1 (en) | 2007-12-10 | 2009-06-11 | International Business Machines Corporation | Method for intelligent data handling for mobile call billing using ims |
US8401906B2 (en) * | 2007-12-12 | 2013-03-19 | At&T Intellectual Property I, L.P. | Financial transaction authentication servers, methods, and computer program products for facilitating financial transactions between buyers and sellers |
US8793305B2 (en) | 2007-12-13 | 2014-07-29 | Seven Networks, Inc. | Content delivery to a mobile device from a content service |
CN101183958A (en) | 2007-12-14 | 2008-05-21 | 华为技术有限公司 | Charging control method, charging center and related equipment |
EP2073460A1 (en) | 2007-12-17 | 2009-06-24 | Alcatel Lucent | Method for forwarding packets, a related packet forwarding system, a related classification device and a related popularity monitoring device |
CN101925939A (en) | 2007-12-20 | 2010-12-22 | 意大利电信股份公司 | Method and system for estimating road traffic |
US8544105B2 (en) | 2007-12-24 | 2013-09-24 | Qualcomm Incorporated | Method and apparatus for managing policies for time-based licenses on mobile devices |
EP2235968B1 (en) | 2007-12-28 | 2013-07-24 | Telecom Italia S.p.A. | Management of a hybrid communication network comprising a cellular network and a local network |
US7930446B2 (en) | 2007-12-28 | 2011-04-19 | Intel Corporation | Methods and apparatuses for wireless network communication wherein a universal serial bus request block (URB) is generated that will vary parameters that controls wireless transmission commands between devices |
US8463232B2 (en) | 2007-12-31 | 2013-06-11 | Motorola Mobility Llc | Accurate billing for services used across multiple serving nodes |
US8081612B2 (en) | 2007-12-31 | 2011-12-20 | Intel Corporation | Device, system, and method of selectively activating a wireless network connection |
US8505073B2 (en) | 2007-12-31 | 2013-08-06 | United States Cellular Corporation | Service utilization control manager |
US7929446B2 (en) * | 2008-01-04 | 2011-04-19 | Radiient Technologies, Inc. | Mesh networking for wireless communications |
CN101483847B (en) | 2008-01-07 | 2012-10-03 | 华为技术有限公司 | Method, apparatus and system for implementing policy control |
US8326828B2 (en) | 2008-01-15 | 2012-12-04 | International Business Machines Corporation | Method and system for employing a multiple layer cache mechanism to enhance performance of a multi-user information retrieval system |
US20100290448A1 (en) | 2008-01-15 | 2010-11-18 | Telefonaktiebolaget L M Ericsson (Publ) | Pre-fetching of input data for access network selection |
US20090180391A1 (en) | 2008-01-16 | 2009-07-16 | Broadcom Corporation | Network activity anomaly detection |
US8044792B2 (en) | 2008-01-30 | 2011-10-25 | Hewlett-Packard Development Company, L.P. | System and method for controlling remote sensors |
US8200200B1 (en) | 2008-02-04 | 2012-06-12 | Sprint Communications Company L.P. | Localized mobile digital TV |
US8208919B2 (en) | 2008-02-06 | 2012-06-26 | Cellco Partnership | Route optimization using network enforced, mobile implemented policy |
US8787249B2 (en) | 2008-02-06 | 2014-07-22 | Qualcomm Incorporated | Mobile IP multiple registrations and PCC interactions |
US8411587B2 (en) | 2008-02-11 | 2013-04-02 | Dell Products L.P. | System and method for configuring a network |
US8185127B1 (en) | 2008-02-12 | 2012-05-22 | Sprint Communications Company L. P. | Method and system for allocating network resources for a single user operating multiple devices |
US8589955B2 (en) | 2008-02-12 | 2013-11-19 | Nuance Communications, Inc. | System and method for building applications, such as customized applications for mobile devices |
US20090203352A1 (en) | 2008-02-13 | 2009-08-13 | Xelex Technologies Inc. | Mobile phone/device usage tracking system and method |
US9112909B2 (en) | 2008-02-13 | 2015-08-18 | Futurewei Technologies, Inc. | User and device authentication in broadband networks |
US8825109B2 (en) | 2008-02-15 | 2014-09-02 | Blackberry Limited | Policy-based data routing for a multi-mode device |
US8942112B2 (en) | 2008-02-15 | 2015-01-27 | Cisco Technology, Inc. | System and method for providing selective mobility invocation in a network environment |
US20090219170A1 (en) | 2008-02-18 | 2009-09-03 | Clark Ryan C | Wireless network inventory system |
US8930238B2 (en) | 2008-02-21 | 2015-01-06 | International Business Machines Corporation | Pervasive symbiotic advertising system and methods therefor |
US8553883B2 (en) | 2008-02-22 | 2013-10-08 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for managing subscription credentials in a wireless communication device |
US9105031B2 (en) | 2008-02-22 | 2015-08-11 | Microsoft Technology Licensing, Llc | Authentication mechanisms for wireless networks |
US8082459B2 (en) | 2008-02-26 | 2011-12-20 | Microsoft Corporation | Power management based on policy |
US8233433B2 (en) | 2008-02-26 | 2012-07-31 | Kyocera Corporation | Apparatus, system and method for initiating WLAN service using beacon signals |
US8875042B2 (en) | 2008-02-29 | 2014-10-28 | Blackberry Limited | System and method of navigating through notifications |
JP2009212707A (en) | 2008-03-03 | 2009-09-17 | Fujitsu Ltd | Controller, control method and computer program |
US7953808B2 (en) | 2008-03-04 | 2011-05-31 | Apple Inc. | Automatic notification system and process |
US8086497B1 (en) | 2008-03-05 | 2011-12-27 | United Services Automobile Association | Systems and methods for price searching and customer self-checkout using a mobile device |
US7756757B1 (en) | 2008-03-05 | 2010-07-13 | United Services Automobile Association (Usaa) | Systems and methods for price searching and intelligent shopping lists on a mobile device |
US20110019574A1 (en) | 2008-03-10 | 2011-01-27 | Szabolcs Malomsoky | Technique for classifying network traffic and for validating a mechanism for classifying network traffic |
JP4942115B2 (en) | 2008-03-10 | 2012-05-30 | 株式会社国際電気通信基礎技術研究所 | WIRELESS DEVICE, WIRELESS COMMUNICATION METHOD IN THE SAME, AND WIRELESS NETWORK HAVING THE WIRELESS DEVICE |
EP2253102A4 (en) | 2008-03-13 | 2013-05-22 | Ericsson Telefon Ab L M | Integration platform for collecting security audit trail |
US7933274B2 (en) | 2008-03-17 | 2011-04-26 | Samsung Electronics Co., Ltd. | Quality of service in a home network |
US8264965B2 (en) | 2008-03-21 | 2012-09-11 | Alcatel Lucent | In-band DPI application awareness propagation enhancements |
JP5262214B2 (en) | 2008-03-21 | 2013-08-14 | 富士通株式会社 | Call information recording program, call information recording apparatus, and call information recording method |
US9110685B2 (en) | 2008-03-25 | 2015-08-18 | Qualcomm, Incorporated | Apparatus and methods for managing widgets in a wireless communication environment |
US8401968B1 (en) | 2008-03-27 | 2013-03-19 | Amazon Technologies, Inc. | Mobile group payments |
US8131858B2 (en) | 2008-04-04 | 2012-03-06 | Motorola Solutions, Inc. | Method and devices for enabling a multi-mode device to establish a session through multiple networks |
MX2010010913A (en) | 2008-04-04 | 2010-12-21 | Powerwave Cognition Inc | Methods and systems for a mobile, broadband, routable internet. |
US7987496B2 (en) | 2008-04-11 | 2011-07-26 | Microsoft Corporation | Automatic application of information protection policies |
US8265017B2 (en) | 2008-04-11 | 2012-09-11 | Apple Inc. | Methods and apparatus for network capacity enhancement for wireless device coexistence |
CN101562553A (en) | 2008-04-18 | 2009-10-21 | 鸿富锦精密工业(深圳)有限公司 | Bridge set and network bridging method thereof |
US8571501B2 (en) | 2008-04-21 | 2013-10-29 | Qualcomm Incorporated | Cellular handheld device with FM Radio Data System receiver |
US8724486B2 (en) | 2008-05-02 | 2014-05-13 | Pine Valley Investments, Inc. | System and method for heartbeat signal generation |
US8571474B2 (en) | 2008-05-06 | 2013-10-29 | International Business Machines Corporation | Performing routing of a phone call through a third party device |
CA2723674C (en) | 2008-05-07 | 2014-09-09 | Chalk Media Service Corp. | Method for enabling bandwidth management for mobile content delivery |
CN102090110B (en) | 2008-05-09 | 2013-12-04 | 黑莓有限公司 | Methods and apparatus for prioritizing assignment of a packet data session for a plurality of applications of a mobile communication device |
US8194549B2 (en) | 2008-05-09 | 2012-06-05 | At&T Mobility Ii Llc | Femto cell access point passthrough model |
FI20080345A0 (en) | 2008-05-09 | 2008-05-09 | Joikusoft Oy Ltd | Symbian S60 phone as 3G bandwidth combiner |
WO2009140669A2 (en) | 2008-05-16 | 2009-11-19 | Terahop Networks, Inc. | Securing, monitoring and tracking shipping containers |
US8209744B2 (en) | 2008-05-16 | 2012-06-26 | Microsoft Corporation | Mobile device assisted secure computer network communication |
US8520589B2 (en) | 2008-05-19 | 2013-08-27 | Motorola Mobility Llc | Mobile device and method for intelligently communicating data generated thereby over short-range, unlicensed wireless networks and wide area wireless networks |
US8121584B2 (en) | 2008-05-21 | 2012-02-21 | Mediatek Inc. | Methods for handling conference communication and the communication apparatuses utilizing the same |
US7957718B2 (en) | 2008-05-22 | 2011-06-07 | Wmode Inc. | Method and apparatus for telecommunication expense management |
US8526350B2 (en) | 2008-05-23 | 2013-09-03 | Qualcomm Incorporated | Systems and methods for carrying broadcast services over a mobile broadcast network |
CN102138301B (en) | 2008-05-28 | 2016-02-17 | 凯敏公司 | Reasonable employment management method and system |
US8418168B2 (en) | 2008-05-29 | 2013-04-09 | Research In Motion Limited | Method and system for performing a software upgrade on an electronic device connected to a computer |
US8539544B2 (en) | 2008-05-30 | 2013-09-17 | Motorola Mobility Llc | Method of optimizing policy conformance check for a device with a large set of posture attribute combinations |
US8170553B2 (en) | 2008-06-04 | 2012-05-01 | Broadcom Corporation | Cash card system interface module |
US8670334B2 (en) | 2008-06-04 | 2014-03-11 | Cisco Technology, Inc | Click quality classification and delivery |
US8346225B2 (en) | 2009-01-28 | 2013-01-01 | Headwater Partners I, Llc | Quality of service for device assisted services |
US8270952B2 (en) * | 2009-01-28 | 2012-09-18 | Headwater Partners I Llc | Open development system for access service providers |
US8391834B2 (en) | 2009-01-28 | 2013-03-05 | Headwater Partners I Llc | Security techniques for device assisted services |
US8548428B2 (en) * | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Device group partitions and settlement platform |
US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8275830B2 (en) | 2009-01-28 | 2012-09-25 | Headwater Partners I Llc | Device assisted CDR creation, aggregation, mediation and billing |
US8406748B2 (en) * | 2009-01-28 | 2013-03-26 | Headwater Partners I Llc | Adaptive ambient services |
US8626115B2 (en) | 2009-01-28 | 2014-01-07 | Headwater Partners I Llc | Wireless network service interfaces |
US8402111B2 (en) | 2009-01-28 | 2013-03-19 | Headwater Partners I, Llc | Device assisted services install |
US8340634B2 (en) | 2009-01-28 | 2012-12-25 | Headwater Partners I, Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8589541B2 (en) * | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
JP5199735B2 (en) * | 2008-06-06 | 2013-05-15 | 富士フイルム株式会社 | Radiation image data correction method and apparatus, and radiation image photographing apparatus |
US8135392B2 (en) | 2008-06-06 | 2012-03-13 | Apple Inc. | Managing notification service connections and displaying icon badges |
US9027027B2 (en) | 2008-06-09 | 2015-05-05 | Microsoft Technology Licensing, Llc | Thread management based on device power state |
EP2304578A4 (en) | 2008-06-13 | 2012-08-29 | Hewlett Packard Development Co | Hierarchical policy management |
US20090312036A1 (en) | 2008-06-16 | 2009-12-17 | Skyhook Wireless, Inc. | Methods and systems for improving the accuracy of expected error estimation in location determinations using a hybrid cellular and wlan positioning system |
US8204505B2 (en) | 2008-06-17 | 2012-06-19 | Qualcomm Incorporated | Managing network-initiated quality of service setup in mobile device and network |
US8448015B2 (en) | 2008-06-17 | 2013-05-21 | My Computer Works, Inc. | Remote computer diagnostic system and method |
US8060603B2 (en) | 2008-06-18 | 2011-11-15 | Qualcomm Incorporated | Persistent personal messaging in a distributed system |
JP5178341B2 (en) | 2008-06-23 | 2013-04-10 | パナソニック株式会社 | Secure boot with optional components |
US8713535B2 (en) | 2008-06-30 | 2014-04-29 | Microsoft Corporation | Reliable and accurate usage detection of a software application |
US9673996B1 (en) | 2008-07-02 | 2017-06-06 | Sprint Spectrum L.P. | Redirection of a streaming media session in an anticipated failover scenario |
US8396929B2 (en) | 2008-07-02 | 2013-03-12 | Sap Portals Israel Ltd. | Method and apparatus for distributed application context aware transaction processing |
US7817615B1 (en) | 2008-07-03 | 2010-10-19 | Sprint Communications Company L.P. | Cross-network quality-of-service verification |
US20100010873A1 (en) | 2008-07-09 | 2010-01-14 | Matt Moreau | System and method for information acquisition and sharing |
US8185152B1 (en) | 2008-07-09 | 2012-05-22 | Marvell International Ltd. | Access network discovery and selection and internet protocol multimedia system service architecture |
US8818394B2 (en) | 2008-07-11 | 2014-08-26 | Intel Mobile Communications GmbH | Mobile radio communication devices having a trusted processing environment and method for processing a computer program therein |
US8259692B2 (en) | 2008-07-11 | 2012-09-04 | Nokia Corporation | Method providing positioning and navigation inside large buildings |
US8159520B1 (en) | 2008-07-11 | 2012-04-17 | Sprint Communications Company L.P. | Ensuring quality of a video stream through a telecommunications network |
US7792708B2 (en) | 2008-07-17 | 2010-09-07 | T-Mobile Usa, Inc. | Digital frame having wireless communication capability |
US8706863B2 (en) | 2008-07-18 | 2014-04-22 | Apple Inc. | Systems and methods for monitoring data and bandwidth usage |
US8107497B2 (en) | 2008-07-23 | 2012-01-31 | Embarq Holdings Company Llc | Auto bandwidth negotiation, reroute and advertisement |
US9064275B1 (en) * | 2008-07-25 | 2015-06-23 | At&T Intellectual Property I, L.P. | Systems and methods for charging and billing in converged communications networks |
US8121068B2 (en) | 2008-07-30 | 2012-02-21 | Intel Corporation | Techniques to improve co-existence among multiple radios |
CN102113271B (en) | 2008-07-30 | 2014-02-19 | 阿尔卡特朗讯美国公司 | Online charging for sessions that are transferred between network domains |
TW201005541A (en) | 2008-07-31 | 2010-02-01 | Aspeed Technology Inc | Transmission device and data extended transmission method |
US7840669B2 (en) * | 2008-08-04 | 2010-11-23 | Hewlett-Packard Development Company, L.P. | Provisioning artifacts for policy enforcement of service-oriented architecture (SOA) deployments |
TWI426762B (en) | 2008-08-04 | 2014-02-11 | Ind Tech Res Inst | Method and system for managing network identity |
US8422988B1 (en) | 2008-08-07 | 2013-04-16 | Bee Networx Inc. | Controlling activity levels and reducing infrastructure data transmission costs for wireless mobile devices |
JP4722973B2 (en) | 2008-08-12 | 2011-07-13 | 株式会社日立製作所 | Request processing method and computer system |
US20100041391A1 (en) | 2008-08-12 | 2010-02-18 | Anthony Wayne Spivey | Embedded mobile analytics in a mobile device |
US8429403B2 (en) | 2008-08-12 | 2013-04-23 | Juniper Networks, Inc. | Systems and methods for provisioning network devices |
US8943551B2 (en) | 2008-08-14 | 2015-01-27 | Microsoft Corporation | Cloud-based device information storage |
US8521775B1 (en) | 2008-08-20 | 2013-08-27 | At&T Mobility Ii Llc | Systems and methods for implementing a master policy repository in a policy realization framework |
US8095112B2 (en) | 2008-08-21 | 2012-01-10 | Palo Alto Research Center Incorporated | Adjusting security level of mobile device based on presence or absence of other mobile devices nearby |
US8266249B2 (en) | 2008-08-22 | 2012-09-11 | At&T Mobility Ii Llc | Providing remote access to multimedia content |
US8811338B2 (en) | 2008-08-22 | 2014-08-19 | Qualcomm Incorporated | Proxy mobile internet protocol (PMIP) in a multi-interface communication environment |
US7911975B2 (en) | 2008-08-26 | 2011-03-22 | International Business Machines Corporation | System and method for network flow traffic rate encoding |
US7826352B2 (en) | 2008-08-26 | 2010-11-02 | Broadcom Corporation | Meter-based hierarchical bandwidth sharing |
US7868814B1 (en) | 2008-08-27 | 2011-01-11 | Lockheed Martin Corporation | Method for transmission of target information over a network |
US8214890B2 (en) | 2008-08-27 | 2012-07-03 | Microsoft Corporation | Login authentication using a trusted device |
US8737989B2 (en) | 2008-08-29 | 2014-05-27 | Apple Inc. | Methods and apparatus for machine-to-machine based communication service classes |
US8863038B2 (en) | 2008-09-08 | 2014-10-14 | Qualcomm Incorporated | Multi-panel electronic device |
US8731519B2 (en) | 2008-09-08 | 2014-05-20 | At&T Mobility Ii Llc | Mobile handset extension to a device |
US7970426B2 (en) | 2008-09-10 | 2011-06-28 | Motorola Solutions, Inc. | Method of assigning provisional identification to a subscriber unit and group |
US8200509B2 (en) | 2008-09-10 | 2012-06-12 | Expanse Networks, Inc. | Masked data record access |
US20100069074A1 (en) | 2008-09-12 | 2010-03-18 | Lucent Technologies Inc. | Wireless-resource broker |
WO2010033944A2 (en) | 2008-09-22 | 2010-03-25 | Visa International Service Association | Over the air management of payment application installed in mobile device |
US20100077035A1 (en) | 2008-09-23 | 2010-03-25 | Nokia Corporation | Optimized Polling in Low Resource Devices |
US8311498B2 (en) | 2008-09-29 | 2012-11-13 | Broadcom Corporation | Multiband communication device for use with a mesh network and methods for use therewith |
US8151205B2 (en) | 2008-09-30 | 2012-04-03 | Nokia Corporation | Methods, apparatuses, and computer program products for providing activity coordination information |
US20100088387A1 (en) | 2008-10-03 | 2010-04-08 | Apple Inc. | Email Notification Proxy |
US8363799B2 (en) | 2008-10-03 | 2013-01-29 | At&T Intellectual Property I, L.P. | Party information for data-capable communication device |
US8588240B2 (en) | 2008-10-07 | 2013-11-19 | Cisco Technology, Inc. | Methods and systems for accounting in an access gateway |
US8538421B2 (en) | 2008-10-20 | 2013-09-17 | At&T Mobility Ii Llc | Management of network technology selection and display in multi-technology wireless environments |
US8543265B2 (en) | 2008-10-20 | 2013-09-24 | Honeywell International Inc. | Systems and methods for unmanned aerial vehicle navigation |
US8271025B2 (en) | 2008-10-20 | 2012-09-18 | At&T Mobility Ii Llc | Device network technology selection and display in multi-technology wireless environments |
US8280343B2 (en) | 2008-10-21 | 2012-10-02 | Centurylink Intellectual Property Llc | System and method for providing contact information of a mobile device to a reverse 911 database |
US9367680B2 (en) | 2008-10-21 | 2016-06-14 | Lookout, Inc. | System and method for mobile communication device application advisement |
US8984628B2 (en) | 2008-10-21 | 2015-03-17 | Lookout, Inc. | System and method for adverse mobile application identification |
US8190122B1 (en) | 2008-10-23 | 2012-05-29 | Cellco Partnership | Method and system for managing mobile telephone numbers and mobile telephone subscribers' data without geography-based restriction |
US8619733B2 (en) | 2008-11-03 | 2013-12-31 | Qualcomm Incorporated | Selection of wireless network in conjunction with selection of a wireless cell set |
US8194581B1 (en) | 2008-11-04 | 2012-06-05 | Cellco Partnership | Account holder notification for an infracting mobile station or mobile directory number (MDN) |
US8155670B2 (en) | 2008-11-04 | 2012-04-10 | 2Wire, Inc. | Cell notification |
US20100121744A1 (en) | 2008-11-07 | 2010-05-13 | At&T Intellectual Property I, L.P. | Usage data monitoring and communication between multiple devices |
US8346923B2 (en) | 2008-11-12 | 2013-01-01 | Sophos Plc | Methods for identifying an application and controlling its network utilization |
US8363658B1 (en) | 2008-11-13 | 2013-01-29 | Sprint Communications Company L.P. | Dynamic firewall and dynamic host configuration protocol configuration |
US8504687B2 (en) | 2008-11-26 | 2013-08-06 | Telecom Italia S.P.A. | Application data flow management in an IP network |
US8374576B2 (en) | 2008-12-04 | 2013-02-12 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for generating resource utilization alerts through communication terminals |
US8443390B2 (en) | 2008-12-05 | 2013-05-14 | Qualcomm Incorporated | Enhanced method and apparatus for enhancing support for service delivery |
US8325638B2 (en) | 2008-12-09 | 2012-12-04 | Qualcomm Incorporated | Performing packet flow optimization with policy and charging control |
US8160598B2 (en) | 2008-12-10 | 2012-04-17 | At&T Intellectual Property Ii, L.P. | Lightweight application level policy management for portable wireless devices under varying network |
US7996713B2 (en) | 2008-12-15 | 2011-08-09 | Juniper Networks, Inc. | Server-to-server integrity checking |
US20100151866A1 (en) | 2008-12-16 | 2010-06-17 | Verizon Corporate Services Group Inc. | Method and system for routing inter-carrier messaging application traffic via a carrier-assigned identifier |
US8615507B2 (en) | 2008-12-23 | 2013-12-24 | International Business Machines Corporation | Database management |
EP2368343A4 (en) | 2008-12-23 | 2012-06-13 | Ericsson Telefon Ab L M | A method and an arrangement for enabling user traffic classification configuration |
US8375128B2 (en) | 2008-12-23 | 2013-02-12 | At&T Mobility Ii Llc | Methods and apparatuses for providing communications services in connection with a communications network |
US8971912B2 (en) | 2008-12-24 | 2015-03-03 | Industrial Technology Research Institute | Paging process in a home cellular network |
EP2203006A1 (en) | 2008-12-29 | 2010-06-30 | Research in Motion Limited | Device-based Network Service Provisioning |
US8406736B2 (en) | 2008-12-30 | 2013-03-26 | Symbol Technologies, Inc. | System and method for identifying and locating wireless devices that are being operated by unauthorized users |
US8200163B2 (en) | 2008-12-30 | 2012-06-12 | Carrier Iq, Inc. | Distributed architecture for monitoring mobile communication in a wireless communication network |
US8565746B2 (en) | 2008-12-30 | 2013-10-22 | Carrier Iq, Inc. | Programmable agent for monitoring mobile communication in a wireless communication network |
US8561138B2 (en) | 2008-12-31 | 2013-10-15 | Intel Corporation | System and method to provide added security to a platform using locality-based data |
US8667542B1 (en) | 2009-01-05 | 2014-03-04 | Sprint Communications Company L.P. | System and method of filtered presentation of broadcast messages by mobile devices |
US8135388B1 (en) | 2009-01-07 | 2012-03-13 | Sprint Communications Company L.P. | Managing communication network capacity |
US8411691B2 (en) | 2009-01-12 | 2013-04-02 | Juniper Networks, Inc. | Transfer of mobile subscriber context in cellular networks using extended routing protocol |
US8116729B2 (en) | 2009-01-13 | 2012-02-14 | T-Mobile Usa, Inc. | System and method for peer-to-peer transfer of multimedia content and reconciliation thereof |
JP5648286B2 (en) * | 2009-01-14 | 2015-01-07 | ソニー株式会社 | COMMUNICATION SYSTEM, COMMUNICATION DEVICE, PROGRAM, AND COMMUNICATION CONTROL METHOD |
US8132256B2 (en) | 2009-01-21 | 2012-03-06 | At&T Mobility Ii Llc | Home networking using LTE radio |
EP2211569A1 (en) | 2009-01-23 | 2010-07-28 | Research In Motion Limited | System and Method for Self-Serve Provisioning of Services on a Mobile Communication Device |
US8326319B2 (en) | 2009-01-23 | 2012-12-04 | At&T Mobility Ii Llc | Compensation of propagation delays of wireless signals |
US8385199B1 (en) | 2009-01-26 | 2013-02-26 | Radisys Corporation | Adaptive traffic shaping for wireless communication systems |
US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
US8351898B2 (en) | 2009-01-28 | 2013-01-08 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
US10057775B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Virtualized policy and charging system |
US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
AU2010208183A1 (en) | 2009-01-28 | 2011-09-08 | Headwater Partners I Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8745191B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
US9253663B2 (en) * | 2009-01-28 | 2016-02-02 | Headwater Partners I Llc | Controlling mobile device communications on a roaming network based on device state |
US8977232B2 (en) | 2009-01-29 | 2015-03-10 | Qualcomm Incorporated | Certified device-based accounting |
US8275415B2 (en) | 2009-02-13 | 2012-09-25 | At&T Intellectual Property I, Lp | Systems and methods for multi-device wireless SIM management |
CN101577978B (en) | 2009-02-27 | 2011-02-16 | 西安西电捷通无线网络通信股份有限公司 | Method for realizing convergence WAPI network architecture in local MAC mode |
US8346210B2 (en) | 2009-02-27 | 2013-01-01 | Nokia Corporation | Method and apparatus for managing services using bearer tags |
US8064896B2 (en) | 2009-03-09 | 2011-11-22 | Apple Inc. | Push notification service |
US20100235473A1 (en) | 2009-03-10 | 2010-09-16 | Sandisk Il Ltd. | System and method of embedding second content in first content |
US8782755B2 (en) | 2009-03-20 | 2014-07-15 | Citrix Systems, Inc. | Systems and methods for selecting an authentication virtual server from a plurality of virtual servers |
US8385975B2 (en) * | 2009-04-23 | 2013-02-26 | Qualcomm Incorporated | Context-based messaging for wireless communication |
US8073440B2 (en) | 2009-04-27 | 2011-12-06 | Airbiquity, Inc. | Automatic gain control in a personal navigation device |
WO2010128391A2 (en) | 2009-05-04 | 2010-11-11 | Bridgewater Systems Corp. | System and methods for mobile device-based data communications cost monitoring and control |
US9177455B2 (en) | 2009-05-07 | 2015-11-03 | Perpcast, Inc. | Personal safety system, method, and apparatus |
JP2012526497A (en) | 2009-05-08 | 2012-10-25 | オービーディーエッジ, エルエルシー | System, method and apparatus for controlling and monitoring the use of mobile devices by vehicle operators based on policies |
US8213296B2 (en) | 2009-05-14 | 2012-07-03 | Verizon Patent And Licensing Inc. | Link aggregation protection |
US8452858B2 (en) * | 2009-05-15 | 2013-05-28 | Novatel Wireless, Inc. | Method and apparatus for loading landing page |
US20100290390A1 (en) | 2009-05-15 | 2010-11-18 | Novatel Wireless Inc. | Systems and methods for controlling device network access through a wireless router |
US10002332B2 (en) | 2009-05-21 | 2018-06-19 | Shared Performance, Llc | Methods and systems for resource and organization achievement |
US8898748B2 (en) | 2009-05-21 | 2014-11-25 | Mobile Iron, Inc. | Remote verification for configuration updates |
WO2010136070A1 (en) | 2009-05-29 | 2010-12-02 | Telefonaktiebolaget Lm Ericsson (Publ) | Policy and charging control method, network entities, communication system and computer program therefor |
US8180333B1 (en) | 2009-05-29 | 2012-05-15 | Sprint Spectrum L.P. | Differential routing of communication-usage records |
JP5379299B2 (en) | 2009-06-01 | 2013-12-25 | アルカテル−ルーセント | Notification of charge charge adjustment in the area of the mobile network to control bandwidth usage in the area |
US20100311402A1 (en) | 2009-06-08 | 2010-12-09 | Prasanna Srinivasan | Method and apparatus for performing soft switch of virtual sim service contracts |
US8306741B2 (en) | 2009-06-09 | 2012-11-06 | Alpine Electronics, Inc. | Method and apparatus for navigation system using routing data created by remote navigation server |
US8868725B2 (en) | 2009-06-12 | 2014-10-21 | Kent State University | Apparatus and methods for real-time multimedia network traffic management and control in wireless networks |
US8194572B2 (en) * | 2009-06-15 | 2012-06-05 | Motorola Mobility, Inc. | Method and apparatus for increasing performance of a wireless communication system |
US8234583B2 (en) | 2009-06-16 | 2012-07-31 | Microsoft Corporation | Media asset pivot navigation |
US8705361B2 (en) | 2009-06-16 | 2014-04-22 | Tellabs Operations, Inc. | Method and apparatus for traffic management in a wireless network |
CN101931928B (en) | 2009-06-19 | 2014-08-13 | 中兴通讯股份有限公司 | Method and system for policy and charging control on single-APN multi-PDN connection under ramble scene |
US8601556B2 (en) | 2009-06-22 | 2013-12-03 | Citrix Systems, Inc. | Systems and methods for handling SSL session not reusable across multiple cores |
US8336080B2 (en) | 2009-06-26 | 2012-12-18 | Symbol Technologies, Inc. | Methods and apparatus for rating device security and automatically assessing security compliance |
US8863111B2 (en) | 2009-06-26 | 2014-10-14 | Oracle International Corporation | System and method for providing a production upgrade of components within a multiprotocol gateway |
WO2011002450A1 (en) | 2009-06-30 | 2011-01-06 | Alcatel-Lucent Usa Inc | Front-end charging system that generates charging data per entity having a revenue share |
US8223741B1 (en) * | 2009-07-01 | 2012-07-17 | Sprint Communications Company L.P. | Acting on data packets in a mobile telecommunications network based on inner headers |
US8619735B2 (en) | 2009-07-16 | 2013-12-31 | Blackberry Limited | Methods and apparatus to register with external networks in wireless network environments |
US8750265B2 (en) | 2009-07-20 | 2014-06-10 | Wefi, Inc. | System and method of automatically connecting a mobile communication device to a network using a communications resource database |
US8504690B2 (en) | 2009-08-07 | 2013-08-06 | Broadcom Corporation | Method and system for managing network power policy and configuration of data center bridging |
US8355570B2 (en) | 2009-08-12 | 2013-01-15 | Conexant Systems, Inc. | Systems and methods for raster-to-block converter |
EP2468067A4 (en) * | 2009-08-19 | 2015-09-09 | Opanga Networks Inc | Optimizing media content delivery based on user equipment determined resource metrics |
US8891483B2 (en) | 2009-08-19 | 2014-11-18 | Comcast Cable Communications, Llc | Wireless gateway supporting a plurality of networks |
US8340628B2 (en) | 2009-09-10 | 2012-12-25 | Qualcomm Incorporated | Systems and methods for localized wireless notification |
US20110071854A1 (en) | 2009-09-21 | 2011-03-24 | Aetna Inc. | Health care payment estimator |
KR101373877B1 (en) * | 2009-09-28 | 2014-03-12 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Scalable wlan gateway |
US8549173B1 (en) | 2009-09-29 | 2013-10-01 | Google Inc. | User-space resource management |
US8347362B2 (en) * | 2009-09-30 | 2013-01-01 | Alcatel Lucent | Usage control services performed in an end user device |
US8315718B2 (en) * | 2009-10-02 | 2012-11-20 | General Electric Company | Control systems and methods of providing the same |
US8412798B1 (en) | 2009-10-03 | 2013-04-02 | Frank C. Wang | Content delivery system and method |
US8185088B2 (en) * | 2009-10-09 | 2012-05-22 | At&T Mobility Ii Llc | Mobile device leasing with customized operational features |
US8406427B2 (en) | 2009-10-13 | 2013-03-26 | Bae Systems Information And Electronic Systems Integration Inc. | Communication network with secure access for portable users |
US8315594B1 (en) | 2009-10-14 | 2012-11-20 | Cellco Partnership | Selecting a service plan based on projected usage requirements |
US8160015B2 (en) | 2009-10-27 | 2012-04-17 | Qualcomm Incorporated | Systems and methods for measuring and reducing latency of radio link flows |
US9313196B2 (en) | 2009-11-06 | 2016-04-12 | Certified Cyber Solutions, Inc. | System and method for secure access of a remote system |
US8843849B2 (en) | 2009-11-09 | 2014-09-23 | Blackberry Limited | Directional navigation of page content |
US8761809B2 (en) * | 2009-11-25 | 2014-06-24 | Visa International Services Association | Transaction using a mobile device with an accelerometer |
US8499087B2 (en) | 2009-11-30 | 2013-07-30 | At&T Mobility Ii Llc | Service-based routing for mobile core network |
US8631428B2 (en) | 2009-11-30 | 2014-01-14 | Charles Scott | System and method for displaying media usage |
US8644813B1 (en) | 2009-12-02 | 2014-02-04 | Sprint Communications Company L.P. | Customer initiated mobile diagnostics service |
US8600850B2 (en) | 2009-12-10 | 2013-12-03 | Redknee Inc. | Feedback loop for dynamic network resource allocation |
US8306518B1 (en) * | 2009-12-21 | 2012-11-06 | Sprint Communications Company L.P. | Handset service migration automation and subscriber identity module tracking |
US8949597B1 (en) | 2009-12-22 | 2015-02-03 | Sprint Communications Company L.P. | Managing certificates on a mobile device |
US8447324B2 (en) * | 2010-01-05 | 2013-05-21 | Qualcomm Incorporated | System for multimedia tagging by a mobile user |
US8630314B2 (en) | 2010-01-11 | 2014-01-14 | Faro Technologies, Inc. | Method and apparatus for synchronizing measurements taken by multiple metrology devices |
US8805365B2 (en) | 2010-01-15 | 2014-08-12 | Apple Inc. | Registration with a mobile telecommunications service provider |
US8228832B2 (en) | 2010-01-25 | 2012-07-24 | Motorola Mobility, Inc. | USSD transport method and device |
US8904206B2 (en) | 2010-01-26 | 2014-12-02 | Motorola Mobility Llc | Mobile computing device and method for maintaining application continuity |
US8335161B2 (en) | 2010-02-03 | 2012-12-18 | Bridgewater Systems Corp. | Systems and methods for network congestion management using radio access network congestion indicators |
US8280351B1 (en) | 2010-02-04 | 2012-10-02 | Cellco Partnership | Automatic device authentication and account identification without user input when application is started on mobile station |
US8346255B2 (en) | 2010-02-11 | 2013-01-01 | Apple Inc. | Method and apparatus for using a wireless communication device with multiple service providers |
US8190675B2 (en) | 2010-02-11 | 2012-05-29 | Inditto, Llc | Method and system for providing access to remotely hosted services through a normalized application programming interface |
US8930551B2 (en) | 2010-02-18 | 2015-01-06 | Alcatel Lucent | Diverse source message association |
US8423046B2 (en) | 2010-02-22 | 2013-04-16 | Google Inc. | Network performance server |
US8230061B2 (en) | 2010-03-17 | 2012-07-24 | Microsoft Corporation | Network resource management with prediction |
US20110238545A1 (en) | 2010-03-26 | 2011-09-29 | Nokia Corporation | Method and apparatus for providing bundled services |
US8798610B2 (en) | 2010-03-26 | 2014-08-05 | Intel Corporation | Method and apparatus for bearer and server independent parental control on smartphone, managed by the smartphone |
PT2554013T (en) | 2010-03-30 | 2019-10-30 | Nokia Technologies Oy | Method and apparatus for device discovery through beaconing |
US8332517B2 (en) * | 2010-03-31 | 2012-12-11 | Incnetworks, Inc. | Method, computer program, and algorithm for computing network service value pricing based on communication service experiences delivered to consumers and merchants over a smart multi-services (SMS) communication network |
JP5397699B2 (en) | 2010-03-31 | 2014-01-22 | 日本電気株式会社 | Mobile communication terminal and function restriction control method thereof |
US8193775B2 (en) | 2010-03-31 | 2012-06-05 | Kookmin University Industry Academy Cooperation Foundation | Hysteresis switch and electricity charging module using the same |
US20110252430A1 (en) | 2010-04-07 | 2011-10-13 | Apple Inc. | Opportunistic Multitasking |
CN101815275A (en) | 2010-04-09 | 2010-08-25 | 刘泱 | Mobile phone charge calculating device |
US8520595B2 (en) | 2010-05-04 | 2013-08-27 | Cisco Technology, Inc. | Routing to the access layer to support mobility of internet protocol devices |
US8364142B1 (en) * | 2010-05-05 | 2013-01-29 | Cellco Partnership | Synchronizing mobile station most recently used MRU list with carrier system preference list |
US20120029718A1 (en) | 2010-05-21 | 2012-02-02 | Davis Edward L | Systems and methods for generating and utilizing electrical signatures for electrical and electronic equipment |
US8301513B1 (en) | 2010-05-25 | 2012-10-30 | Amazon Technologies, Inc. | System, method, and computer readable medium for dynamically pricing an item based on service plan selection |
US8204794B1 (en) | 2010-05-25 | 2012-06-19 | Amazon Technologies, Inc. | Processing orders for wireless service |
KR101911215B1 (en) | 2010-05-25 | 2018-12-19 | 헤드워터 리서치 엘엘씨 | Device-assisted services for protecting network capacity |
US8804517B2 (en) | 2010-05-31 | 2014-08-12 | Blackberry Limited | Management of mobile hotspot connections |
US8307095B2 (en) | 2010-06-21 | 2012-11-06 | Research In Motion Limited | Firmware upgrade system and method in a device management architecture |
US8295170B2 (en) | 2010-06-28 | 2012-10-23 | Alcatel Lucent | PCRF-PCEF-OCS interaction in wireless-wireline convergence |
US8379847B2 (en) * | 2010-06-30 | 2013-02-19 | International Business Machines Corporation | Data and control encryption |
EP2596451B1 (en) | 2010-07-20 | 2018-11-28 | Verimatrix, Inc. | Digital rights domain management for secure content distribution in a local network |
US8326359B2 (en) | 2010-08-03 | 2012-12-04 | Honeywell International Inc. | Reconfigurable wireless modem adapter |
US8406756B1 (en) | 2010-08-13 | 2013-03-26 | Sprint Communications Company L.P. | Wireless network load balancing and roaming management system |
US8539561B2 (en) | 2010-08-24 | 2013-09-17 | International Business Machines Corporation | Systems and methods to control device endpoint behavior using personae and policies |
US8484568B2 (en) | 2010-08-25 | 2013-07-09 | Verizon Patent And Licensing Inc. | Data usage monitoring per application |
US8352630B2 (en) | 2010-09-01 | 2013-01-08 | Sonus Networks, Inc. | Dynamic classification and grouping of network traffic for service application across multiple nodes |
US8407472B2 (en) | 2010-09-13 | 2013-03-26 | Verizon Patent And Licensing Inc. | Mobile content delivery optimization |
US8868727B2 (en) | 2010-09-22 | 2014-10-21 | Blue Stripe Software, Inc. | Methods and computer program products for storing generated network application performance data |
US8670752B2 (en) | 2010-09-24 | 2014-03-11 | At&T Intellectual Property I, L.P. | Providing integrated service-entity premium communication services |
AU2011312874B2 (en) | 2010-09-28 | 2016-01-14 | Headwater Research Llc | Enterprise access control and accounting allocation for access networks |
US8675654B2 (en) | 2010-10-05 | 2014-03-18 | Cisco Technology, Inc. | System and method for providing smart grid communications and management |
US8381316B2 (en) * | 2010-10-21 | 2013-02-26 | Allan Milton Edwards | Head apparel |
US9032427B2 (en) | 2010-10-28 | 2015-05-12 | Avvasi Inc. | System for monitoring a video network and methods for use therewith |
US8843153B2 (en) | 2010-11-01 | 2014-09-23 | Seven Networks, Inc. | Mobile traffic categorization and policy for network use optimization while preserving user experience |
US8838686B2 (en) | 2010-11-03 | 2014-09-16 | Verizon Patent And Licensing Inc. | Method and apparatus for delivery of content to a mobile device |
US8320902B2 (en) | 2010-11-09 | 2012-11-27 | Kapsch Trafficcom Ag | System and method for selecting services in a wireless communication network |
US8621056B2 (en) | 2010-12-02 | 2013-12-31 | Microsoft Corporation | Enabling plural computing devices to communicate using a master account |
US8943221B2 (en) | 2010-12-16 | 2015-01-27 | Openet Telecom Ltd. | Methods, systems and devices for pipeline processing |
US9124436B2 (en) | 2010-12-16 | 2015-09-01 | Cellco Partnership | Intelligent automated data usage upgrade recommendation |
US8971841B2 (en) | 2010-12-17 | 2015-03-03 | Microsoft Corporation | Operating system supporting cost aware applications |
US8495207B2 (en) | 2010-12-21 | 2013-07-23 | Verizon Patent And Licensing Inc. | Network system for policing resource intensive behaviors |
US8909751B2 (en) | 2010-12-28 | 2014-12-09 | Microsoft Corporation | Flexible policy based network decision making |
US8812525B1 (en) | 2010-12-30 | 2014-08-19 | Eventbrite, Inc. | Local SQL files for mobile clients |
US9135037B1 (en) | 2011-01-13 | 2015-09-15 | Google Inc. | Virtual network protocol |
US8441955B2 (en) | 2011-01-24 | 2013-05-14 | Tektronix, Inc. | Determining mobile video quality of experience and impact of video transcoding |
EP2509254A1 (en) | 2011-04-06 | 2012-10-10 | Telefonaktiebolaget L M Ericsson (publ) | Method and apparatus for controlling service traffic in a communication network |
US8837322B2 (en) | 2011-06-20 | 2014-09-16 | Freescale Semiconductor, Inc. | Method and apparatus for snoop-and-learn intelligence in data plane |
US20130095787A1 (en) | 2011-06-22 | 2013-04-18 | Cellco Partnership D/B/A Verizon Wireless | Data transport bundle |
US20120330792A1 (en) | 2011-06-22 | 2012-12-27 | Cellco Partnership D/B/A Verizon Wireless | Open data transport bundle marketplace exchange |
US20130117140A1 (en) | 2011-06-22 | 2013-05-09 | Cellco Partnership D/B/A Verizon Wireless | Data transport content association |
US20130030960A1 (en) | 2011-06-22 | 2013-01-31 | Cellco Partnership D/B/A Verizon Wireless | Alternative data plans |
US8972537B2 (en) | 2011-08-16 | 2015-03-03 | Comcast Cable Communications, Llc | Prioritizing local and network traffic |
US9459767B2 (en) | 2011-08-29 | 2016-10-04 | Ebay Inc. | Tablet web visual browsing |
US9176913B2 (en) | 2011-09-07 | 2015-11-03 | Apple Inc. | Coherence switch for I/O traffic |
US9173090B2 (en) | 2011-09-15 | 2015-10-27 | Teletech Holdings, Inc. | Method for activating services associated with a product via a service center supporting a variety of products |
US9002322B2 (en) | 2011-09-29 | 2015-04-07 | Apple Inc. | Authentication with secondary approver |
US8763077B2 (en) | 2011-10-07 | 2014-06-24 | Duo Security, Inc. | System and method for enforcing a policy for an authenticator device |
US9015021B2 (en) | 2011-10-25 | 2015-04-21 | Cellco Partnership | Multiple client simulator for push engine |
US8732810B2 (en) | 2011-10-27 | 2014-05-20 | Cellco Partnership | IP push platform and connection protocol in a push notification framework |
US9369959B2 (en) | 2011-10-31 | 2016-06-14 | Nokia Technologies Oy | Wirelessly transferring data to a packaged electronic device |
US8914449B2 (en) | 2011-11-07 | 2014-12-16 | Cellco Partnership | Push messaging platform with high scalability and high availability |
US9137389B2 (en) | 2011-11-08 | 2015-09-15 | Kajeet, Inc. | Master limits and filters for electronic devices |
US8799227B2 (en) | 2011-11-11 | 2014-08-05 | Blackberry Limited | Presenting metadata from multiple perimeters |
US8503978B2 (en) | 2011-12-09 | 2013-08-06 | Cellco Partnership | Real time data usage metering on a mobile station and reconciliation with billable usage measured by a mobile network |
US20130225151A1 (en) | 2011-12-23 | 2013-08-29 | Microsoft Corporation | Mobile device parental control |
US8918080B2 (en) | 2012-01-17 | 2014-12-23 | Kajeet, Inc. | Mobile device management |
US8983860B1 (en) | 2012-01-30 | 2015-03-17 | Google Inc. | Advertising auction system |
US9042923B1 (en) | 2012-02-08 | 2015-05-26 | Fsp Llc | Text message definition and control of multimedia |
US9191394B2 (en) | 2012-02-08 | 2015-11-17 | Microsoft Technology Licensing, Llc | Protecting user credentials from a computing device |
US8712631B2 (en) | 2012-02-09 | 2014-04-29 | Nordic Capital Partners, LLC | System and method for access of user accounts on remote servers |
US8538402B2 (en) | 2012-02-12 | 2013-09-17 | Joel Vidal | Phone that prevents texting while driving |
US8429409B1 (en) | 2012-04-06 | 2013-04-23 | Google Inc. | Secure reset of personal and service provider information on mobile devices |
WO2013155535A1 (en) | 2012-04-13 | 2013-10-17 | Tekelec, Inc. | Methods, systems, and computer readable media for performing diameter overload control |
US9021069B2 (en) | 2012-06-27 | 2015-04-28 | Amazon Technologies, Inc. | Preventing deregistration from fleet accounts |
US9847948B2 (en) | 2012-07-09 | 2017-12-19 | Eturi Corp. | Schedule and location responsive agreement compliance controlled device throttle |
US9451403B2 (en) | 2012-08-30 | 2016-09-20 | Ebay Inc. | Systems and method for configuring mobile device applications based on location |
US8977856B2 (en) | 2012-08-31 | 2015-03-10 | Blackberry Limited | Methods and apparatus for use in sharing credentials amongst a plurality of mobile communication devices |
US9047651B2 (en) | 2012-09-14 | 2015-06-02 | Location Labs, Inc. | Contact management system |
US9298723B1 (en) | 2012-09-19 | 2016-03-29 | Amazon Technologies, Inc. | Deduplication architecture |
US9386045B2 (en) | 2012-12-19 | 2016-07-05 | Visa International Service Association | Device communication based on device trustworthiness |
KR102110786B1 (en) | 2013-03-13 | 2020-05-14 | 삼성전자 주식회사 | Method and apparatus for managing conversation message in portable terminal |
US9681003B1 (en) | 2013-03-14 | 2017-06-13 | Aeris Communications, Inc. | Method and system for managing device status and activity history using big data storage |
US9479917B1 (en) | 2013-05-24 | 2016-10-25 | Juniper Networks, Inc. | Rating group-specific actions for mobile networks |
-
2009
- 2009-03-02 US US12/380,782 patent/US8270952B2/en active Active
- 2009-03-02 US US12/380,781 patent/US8229812B2/en not_active Expired - Fee Related
- 2009-03-02 US US12/380,771 patent/US8023425B2/en active Active
- 2009-03-02 US US12/380,769 patent/US8675507B2/en not_active Expired - Fee Related
- 2009-03-02 US US12/380,759 patent/US8270310B2/en active Active
- 2009-03-02 US US12/380,767 patent/US8355337B2/en active Active
- 2009-03-02 US US12/380,778 patent/US8321526B2/en active Active
- 2009-03-02 US US12/380,772 patent/US8839387B2/en active Active
- 2009-03-02 US US12/380,758 patent/US11134102B2/en active Active
- 2009-03-02 US US12/380,755 patent/US8331901B2/en active Active
- 2009-03-02 US US12/380,757 patent/US8326958B1/en active Active
- 2009-03-02 US US12/380,779 patent/US20100192170A1/en not_active Abandoned
- 2009-03-02 US US12/380,780 patent/US8839388B2/en active Active
- 2009-03-02 US US12/380,774 patent/US8630192B2/en active Active
- 2009-03-02 US US12/380,773 patent/US8799451B2/en active Active
- 2009-03-02 US US12/380,756 patent/US8250207B2/en active Active
- 2009-03-02 US US12/380,783 patent/US20100192207A1/en not_active Abandoned
- 2009-03-02 US US12/380,777 patent/US8583781B2/en active Active
- 2009-03-02 US US12/380,770 patent/US20100188993A1/en not_active Abandoned
- 2009-03-02 US US12/380,768 patent/US9137739B2/en active Active
-
2010
- 2010-01-15 AU AU2010208544A patent/AU2010208544B2/en active Active
- 2010-01-15 KR KR1020117019879A patent/KR20110116189A/en not_active Application Discontinuation
- 2010-01-15 CN CN201080013736.2A patent/CN102365554B/en active Active
- 2010-01-15 WO PCT/US2010/021227 patent/WO2010088073A1/en active Application Filing
- 2010-01-15 KR KR1020117019882A patent/KR101646300B1/en active IP Right Grant
- 2010-01-15 CA CA2786832A patent/CA2786832C/en active Active
- 2010-01-15 NZ NZ594725A patent/NZ594725A/en unknown
- 2010-01-15 KR KR1020117019878A patent/KR20110110829A/en not_active Application Discontinuation
- 2010-01-15 KR KR1020117019881A patent/KR101602990B1/en active IP Right Grant
- 2010-01-15 NZ NZ594731A patent/NZ594731A/en unknown
- 2010-01-15 CN CN201080013735.8A patent/CN102365631B/en active Active
- 2010-01-15 CA CA2786830A patent/CA2786830A1/en not_active Abandoned
- 2010-01-15 WO PCT/US2010/021232 patent/WO2010088076A1/en active Application Filing
- 2010-01-15 CA CA2786825A patent/CA2786825A1/en not_active Abandoned
- 2010-01-15 AU AU2010208547A patent/AU2010208547A1/en not_active Abandoned
- 2010-01-15 AU AU2010208543A patent/AU2010208543A1/en not_active Abandoned
- 2010-01-15 WO PCT/US2010/021229 patent/WO2010088074A1/en active Application Filing
- 2010-01-15 CA CA2786864A patent/CA2786864C/en active Active
- 2010-01-15 CN CN201080013733.9A patent/CN102483730B/en active Active
- 2010-01-15 EP EP10736208.9A patent/EP2391965B1/en active Active
- 2010-01-15 NZ NZ594715A patent/NZ594715A/en unknown
- 2010-01-15 WO PCT/US2010/021231 patent/WO2010088075A1/en active Application Filing
- 2010-01-15 KR KR1020117019880A patent/KR20110124258A/en not_active Application Discontinuation
- 2010-01-15 EP EP10736205.5A patent/EP2391947B1/en active Active
- 2010-01-15 EP EP10736209.7A patent/EP2394181B1/en active Active
- 2010-01-15 WO PCT/US2010/021224 patent/WO2010088072A1/en active Application Filing
- 2010-01-15 EP EP10736206.3A patent/EP2391948B1/en active Active
- 2010-01-15 AU AU2010208546A patent/AU2010208546B2/en active Active
- 2010-01-15 CN CN201080013705.7A patent/CN102365630B/en active Active
- 2010-01-15 CN CN2010800137343A patent/CN102365642A/en active Pending
- 2010-01-15 EP EP10736207.1A patent/EP2391949B1/en active Active
- 2010-01-15 NZ NZ594724A patent/NZ594724A/en unknown
- 2010-01-15 CA CA2786828A patent/CA2786828A1/en not_active Abandoned
- 2010-01-15 NZ NZ594732A patent/NZ594732A/en unknown
- 2010-01-15 AU AU2010208545A patent/AU2010208545B2/en active Active
- 2010-01-18 EP EP16153095.1A patent/EP3043579A1/en not_active Withdrawn
- 2010-01-18 AU AU2010208557A patent/AU2010208557B2/en active Active
- 2010-01-18 CN CN201080013768.2A patent/CN102365855B/en active Active
- 2010-01-18 KR KR1020117019884A patent/KR101653852B1/en active IP Right Grant
- 2010-01-18 NZ NZ594753A patent/NZ594753A/en unknown
- 2010-01-18 NZ NZ594734A patent/NZ594734A/en unknown
- 2010-01-18 CN CN201080013732.4A patent/CN102365853B/en active Active
- 2010-01-18 EP EP10736215.4A patent/EP2391950B1/en active Active
- 2010-01-18 CN CN2010800137610A patent/CN102365620A/en active Pending
- 2010-01-18 WO PCT/US2010/021302 patent/WO2010088081A1/en active Application Filing
- 2010-01-18 KR KR1020117019886A patent/KR101646301B1/en active IP Right Grant
- 2010-01-18 CA CA2786868A patent/CA2786868C/en active Active
- 2010-01-18 CN CN201080013740.9A patent/CN102365876B/en active Active
- 2010-01-18 CN CN201080013744.7A patent/CN102365632B/en active Active
- 2010-01-18 EP EP16152669.4A patent/EP3043578B1/en active Active
- 2010-01-18 ES ES16181175.7T patent/ES2657435T3/en active Active
- 2010-01-18 CN CN2010800148121A patent/CN102365877A/en active Pending
- 2010-01-18 AU AU2010208558A patent/AU2010208558A1/en not_active Abandoned
- 2010-01-18 EP EP16153786.5A patent/EP3046344B1/en active Active
- 2010-01-18 CA CA2786865A patent/CA2786865C/en active Active
- 2010-01-18 CN CN201080015313.4A patent/CN102365858B/en active Active
- 2010-01-18 EP EP16180982.7A patent/EP3116245B1/en active Active
- 2010-01-18 WO PCT/US2010/021301 patent/WO2010088080A1/en active Application Filing
- 2010-01-18 EP EP16181175.7A patent/EP3116250B1/en active Active
- 2010-01-18 EP EP24169037.9A patent/EP4391609A2/en active Pending
- 2010-01-18 AU AU2010208554A patent/AU2010208554A1/en not_active Abandoned
- 2010-01-18 NZ NZ594758A patent/NZ594758A/en unknown
- 2010-01-18 NZ NZ594764A patent/NZ594764A/en unknown
- 2010-01-18 CN CN201710138754.7A patent/CN107425988B/en active Active
- 2010-01-18 WO PCT/US2010/021309 patent/WO2010088086A1/en active Application Filing
- 2010-01-18 WO PCT/US2010/021304 patent/WO2010088082A1/en active Application Filing
- 2010-01-18 EP EP10736219.6A patent/EP2392154B1/en active Active
- 2010-01-18 CA CA2786875A patent/CA2786875A1/en not_active Abandoned
- 2010-01-18 NZ NZ594762A patent/NZ594762A/en unknown
- 2010-01-18 EP EP16181187.2A patent/EP3116246B1/en active Active
- 2010-01-18 EP EP10736218.8A patent/EP2391940A4/en not_active Withdrawn
- 2010-01-18 EP EP16153115.7A patent/EP3043580B1/en active Active
- 2010-01-18 EP EP10736220.4A patent/EP2392129B1/en active Active
- 2010-01-18 AU AU2010208552A patent/AU2010208552B2/en active Active
- 2010-01-18 KR KR1020117019887A patent/KR101646810B1/en active IP Right Grant
- 2010-01-18 AU AU2010208551A patent/AU2010208551B2/en active Active
- 2010-01-18 WO PCT/US2010/021310 patent/WO2010088087A1/en active Application Filing
- 2010-01-18 CA CA2786876A patent/CA2786876A1/en not_active Abandoned
- 2010-01-18 EP EP19219822.4A patent/EP3661242B1/en active Active
- 2010-01-18 NZ NZ594756A patent/NZ594756A/en unknown
- 2010-01-18 CA CA2786870A patent/CA2786870C/en active Active
- 2010-01-18 EP EP10736216.2A patent/EP2392126B1/en active Active
- 2010-01-18 EP EP10736213.9A patent/EP2392153B1/en active Active
- 2010-01-18 NZ NZ594761A patent/NZ594761A/en unknown
- 2010-01-18 WO PCT/US2010/021306 patent/WO2010088083A1/en active Application Filing
- 2010-01-18 AU AU2010208556A patent/AU2010208556A1/en not_active Abandoned
- 2010-01-18 CA CA2786749A patent/CA2786749A1/en not_active Abandoned
- 2010-01-18 KR KR1020117019883A patent/KR20110110831A/en not_active Application Discontinuation
- 2010-01-18 WO PCT/US2010/021308 patent/WO2010088085A1/en active Application Filing
- 2010-01-18 EP EP10736214.7A patent/EP2392124B1/en active Active
- 2010-01-18 KR KR1020117019888A patent/KR20110126638A/en not_active Application Discontinuation
- 2010-01-18 CA CA2786873A patent/CA2786873C/en active Active
- 2010-01-18 AU AU2010208553A patent/AU2010208553B2/en active Active
- 2010-01-18 KR KR1020117019885A patent/KR101632093B1/en active IP Right Grant
- 2010-01-18 KR KR1020117019889A patent/KR20110113192A/en not_active Application Discontinuation
- 2010-01-19 WO PCT/US2010/021387 patent/WO2010088096A1/en active Application Filing
- 2010-01-19 AU AU2010208484A patent/AU2010208484B2/en active Active
- 2010-01-19 KR KR1020117019892A patent/KR101740068B1/en active IP Right Grant
- 2010-01-19 CA CA2786881A patent/CA2786881C/en active Active
- 2010-01-19 CN CN201080014654.XA patent/CN102365840B/en active Active
- 2010-01-19 AU AU2010208483A patent/AU2010208483B2/en active Active
- 2010-01-19 AU AU2010208485A patent/AU2010208485B2/en active Active
- 2010-01-19 EP EP10736230.3A patent/EP2392109B1/en active Active
- 2010-01-19 KR KR1020117019893A patent/KR20110124261A/en not_active Application Discontinuation
- 2010-01-19 WO PCT/US2010/021388 patent/WO2010088097A1/en active Application Filing
- 2010-01-19 CA CA2786752A patent/CA2786752A1/en not_active Abandoned
- 2010-01-19 NZ NZ594788A patent/NZ594788A/en unknown
- 2010-01-19 WO PCT/US2010/021381 patent/WO2010088094A1/en active Application Filing
- 2010-01-19 EP EP10736233.7A patent/EP2392102B1/en active Active
- 2010-01-19 KR KR1020117019896A patent/KR20110110835A/en not_active Application Discontinuation
- 2010-01-19 CA CA2786884A patent/CA2786884A1/en not_active Abandoned
- 2010-01-19 AU AU2010208486A patent/AU2010208486B2/en active Active
- 2010-01-19 EP EP10736232.9A patent/EP2391951B1/en active Active
- 2010-01-19 EP EP10736227.9A patent/EP2391977B1/en active Active
- 2010-01-19 EP EP10736228.7A patent/EP2391966B1/en active Active
- 2010-01-19 NZ NZ594795A patent/NZ594795A/en unknown
- 2010-01-19 CN CN2010800147966A patent/CN102365633A/en active Pending
- 2010-01-19 WO PCT/US2010/021384 patent/WO2010088095A1/en active Application Filing
- 2010-01-19 KR KR1020117019895A patent/KR20110113640A/en not_active Application Discontinuation
- 2010-01-19 CN CN201080014710.XA patent/CN102365842B/en active Active
- 2010-01-19 NZ NZ594787A patent/NZ594787A/en unknown
- 2010-01-19 AU AU2010208489A patent/AU2010208489B2/en active Active
- 2010-01-19 CA CA2786887A patent/CA2786887A1/en not_active Abandoned
- 2010-01-19 KR KR1020117019890A patent/KR20110116190A/en not_active Application Discontinuation
- 2010-01-19 CN CN2010800147330A patent/CN102365643A/en active Pending
- 2010-01-19 WO PCT/US2010/021398 patent/WO2010088100A1/en active Application Filing
- 2010-01-19 NZ NZ594766A patent/NZ594766A/en unknown
- 2010-01-19 AU AU2010208565A patent/AU2010208565A1/en not_active Abandoned
- 2010-01-19 CA CA2786878A patent/CA2786878A1/en not_active Abandoned
- 2010-01-19 EP EP10736229.5A patent/EP2392170B1/en active Active
- 2010-01-19 WO PCT/US2010/021400 patent/WO2010088101A1/en active Application Filing
- 2010-01-19 KR KR1020117019891A patent/KR20110117200A/en not_active Application Discontinuation
- 2010-01-19 CN CN201080014879.5A patent/CN102365847B/en active Active
- 2010-01-19 CN CN2010800147260A patent/CN102365623B/en active Active
- 2010-01-19 CN CN201080014827.8A patent/CN102365890B/en active Active
- 2010-01-19 EP EP10736226.1A patent/EP2391942B1/en active Active
- 2010-01-19 WO PCT/US2010/021393 patent/WO2010088098A1/en active Application Filing
- 2010-01-19 NZ NZ594793A patent/NZ594793A/en unknown
- 2010-01-19 CA CA2786815A patent/CA2786815A1/en not_active Abandoned
- 2010-01-19 NZ NZ594791A patent/NZ594791A/en unknown
- 2010-01-19 KR KR1020117019894A patent/KR20110110834A/en not_active Application Discontinuation
- 2010-01-19 NZ NZ594789A patent/NZ594789A/en unknown
- 2010-01-19 CA CA2786746A patent/CA2786746C/en active Active
- 2010-01-19 AU AU2010208488A patent/AU2010208488B2/en active Active
- 2010-01-27 EP EP16150276.0A patent/EP3062540B1/en active Active
- 2010-01-27 EP EP20159987.5A patent/EP3691309B1/en active Active
-
2011
- 2011-12-20 US US13/330,948 patent/US8897743B2/en active Active
-
2012
- 2012-02-07 US US13/368,294 patent/US9014026B2/en active Active
- 2012-04-04 US US13/439,788 patent/US8516552B2/en active Active
- 2012-04-09 US US13/442,214 patent/US8437271B2/en active Active
- 2012-04-10 US US13/443,842 patent/US8531986B2/en active Active
- 2012-04-12 US US13/445,180 patent/US8547872B2/en active Active
- 2012-04-12 US US13/445,110 patent/US8713630B2/en active Active
- 2012-04-12 US US13/445,134 patent/US8467312B2/en active Active
- 2012-04-19 US US13/451,349 patent/US9179308B2/en active Active
- 2012-04-19 US US13/451,337 patent/US20120201133A1/en not_active Abandoned
- 2012-04-25 US US13/456,139 patent/US8478667B2/en active Active
- 2012-04-26 US US13/457,385 patent/US8385916B2/en active Active
- 2012-04-26 US US13/457,389 patent/US8396458B2/en active Active
- 2012-05-01 US US13/461,141 patent/US8406733B2/en active Active
- 2012-07-20 US US13/554,616 patent/US8441989B2/en active Active
- 2012-08-20 US US13/589,929 patent/US8924549B2/en active Active
- 2012-09-13 US US13/615,094 patent/US8688099B2/en active Active
- 2012-09-13 US US13/615,152 patent/US8898079B2/en active Active
- 2012-09-13 US US13/615,249 patent/US8666364B2/en active Active
- 2012-09-13 US US13/615,217 patent/US8588110B2/en active Active
- 2012-10-02 US US13/633,817 patent/US8903452B2/en active Active
- 2012-10-02 US US13/633,821 patent/US8897744B2/en active Active
- 2012-11-15 US US13/678,410 patent/US8630611B2/en active Active
- 2012-11-15 US US13/678,417 patent/US8631102B2/en active Active
- 2012-12-04 US US13/705,055 patent/US8667571B2/en active Active
- 2012-12-12 US US13/712,184 patent/US8639935B2/en active Active
-
2013
- 2013-01-15 US US13/742,312 patent/US8639811B2/en active Active
- 2013-01-15 US US13/742,317 patent/US8640198B2/en active Active
- 2013-03-19 US US13/847,417 patent/US8724554B2/en active Active
- 2013-03-28 US US13/852,933 patent/US8635678B2/en active Active
- 2013-04-19 US US13/866,955 patent/US20130229951A1/en not_active Abandoned
- 2013-04-19 US US13/866,963 patent/US8695073B2/en active Active
- 2013-04-22 US US13/867,347 patent/US8737957B2/en active Active
- 2013-04-25 US US13/870,939 patent/US8570908B2/en active Active
- 2013-05-16 US US13/896,065 patent/US8797908B2/en active Active
-
2014
- 2014-01-09 US US14/151,769 patent/US8886162B2/en active Active
- 2014-04-28 US US14/263,604 patent/US9037127B2/en active Active
- 2014-12-10 US US14/565,889 patent/US9609459B2/en active Active
-
2015
- 2015-03-19 US US14/663,248 patent/US9179315B2/en active Active
- 2015-03-23 US US14/665,235 patent/US9179316B2/en active Active
- 2015-03-24 US US14/667,353 patent/US9232403B2/en active Active
- 2015-03-24 US US14/667,516 patent/US9198117B2/en active Active
- 2015-03-25 US US14/668,829 patent/US9173104B2/en active Active
- 2015-04-03 US US14/678,632 patent/US9204374B2/en active Active
- 2015-11-20 US US14/948,082 patent/US10165447B2/en active Active
- 2015-11-20 US US14/948,065 patent/US10028144B2/en active Active
- 2015-12-22 US US14/979,233 patent/US9532161B2/en active Active
-
2016
- 2016-07-15 US US15/211,430 patent/US9615192B2/en active Active
- 2016-07-22 US US15/217,538 patent/US9491564B1/en active Active
- 2016-08-17 US US15/239,398 patent/US9641957B2/en active Active
-
2017
- 2017-02-08 US US15/427,837 patent/US10321318B2/en active Active
- 2017-04-28 US US15/582,350 patent/US10321320B2/en active Active
-
2018
- 2018-07-13 US US16/034,362 patent/US10694385B2/en active Active
- 2018-12-10 US US16/214,902 patent/US10869199B2/en active Active
-
2019
- 2019-05-23 US US16/421,121 patent/US11096055B2/en active Active
- 2019-06-10 US US16/436,628 patent/US11228617B2/en active Active
-
2020
- 2020-06-22 US US16/907,887 patent/US11405429B2/en active Active
- 2020-12-14 US US17/121,717 patent/US11477246B2/en active Active
-
2021
- 2021-06-08 US US17/342,136 patent/US11757942B2/en active Active
- 2021-08-13 US US17/401,635 patent/US11757943B2/en active Active
-
2022
- 2022-01-17 US US17/577,237 patent/US20220279021A1/en active Pending
Patent Citations (106)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5283904A (en) * | 1990-12-21 | 1994-02-01 | Intel Corporation | Multi-processor programmable interrupt controller system |
US5594777A (en) * | 1992-08-26 | 1997-01-14 | Telecom Finland Oy | Wireless private branch exchange system for use with mobile communication devices |
US6198915B1 (en) * | 1995-01-30 | 2001-03-06 | Telemac Corporation | Mobile phone with internal accounting |
US5889477A (en) * | 1996-03-25 | 1999-03-30 | Mannesmann Aktiengesellschaft | Process and system for ascertaining traffic conditions using stationary data collection devices |
US6038452A (en) * | 1997-08-29 | 2000-03-14 | Nortel Networks Corporation | Telecommunication network utilizing a quality of service protocol |
US6839340B1 (en) * | 1997-09-16 | 2005-01-04 | Bell Atlantic Network Services | Network session management |
US6539082B1 (en) * | 1998-05-13 | 2003-03-25 | British Telecommunications Public Limited Company | Billing system |
US8370477B2 (en) * | 1998-12-08 | 2013-02-05 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8364806B2 (en) * | 1998-12-08 | 2013-01-29 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US6532235B1 (en) * | 1998-12-29 | 2003-03-11 | Qwest Communication Int'l., Inc. | Method and tool for calculating impact of voice traffic on fast packet networks |
US6683853B1 (en) * | 1999-12-01 | 2004-01-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Dynamic upgrade of quality of service in a packet switched network |
US6684244B1 (en) * | 2000-01-07 | 2004-01-27 | Hewlett-Packard Development Company, Lp. | Aggregated policy deployment and status propagation in network management systems |
US20010053694A1 (en) * | 2000-01-31 | 2001-12-20 | Fujitsu Limited | Network system with dynamic service profile updating functions |
US20040047358A1 (en) * | 2000-01-31 | 2004-03-11 | Aeptech Microsystems, Inc. | Broadband communications access device |
US20030050837A1 (en) * | 2000-03-09 | 2003-03-13 | Kim Do Sik | Method and system providing advertisement using tone of ringing sounds of mobile phone and commerical transaction service in association with the same |
US6532579B2 (en) * | 2000-04-18 | 2003-03-11 | Hitachi, Ltd. | Semiconductor integrated circuit and design method and manufacturing method of the same |
US20050060266A1 (en) * | 2000-06-27 | 2005-03-17 | Microsoft Corporation | Method and system for limiting the use of user-specific software features |
US20020022472A1 (en) * | 2000-07-21 | 2002-02-21 | Telemac Corporation | Multiple virtual wallets in wireless device |
US20060014519A1 (en) * | 2000-09-07 | 2006-01-19 | William Marsh | Pooling groups of wireless communication users |
US20020131404A1 (en) * | 2000-11-28 | 2002-09-19 | 4Thpass Inc. | Method and system for maintaining and distributing wireless applications |
US20020120540A1 (en) * | 2000-12-01 | 2002-08-29 | Michael Kende | System and method for automatic analysis of rate information |
US7668176B2 (en) * | 2001-01-18 | 2010-02-23 | Alcatel-Lucent Usa Inc. | Universal mobile telecommunications system (UMTS) quality of service (QoS) supporting variable QoS negotiation |
US6505114B2 (en) * | 2001-02-06 | 2003-01-07 | Sergio Luciani | Traffic monitoring system and method |
US20030050070A1 (en) * | 2001-03-14 | 2003-03-13 | Alex Mashinsky | Method and system for dynamic spectrum allocation and management |
US6996076B1 (en) * | 2001-03-29 | 2006-02-07 | Sonus Networks, Inc. | System and method to internetwork wireless telecommunication networks |
US7180855B1 (en) * | 2001-04-19 | 2007-02-20 | At&T Corp. | Service interface for QoS-driven HPNA networks |
US20030004937A1 (en) * | 2001-05-15 | 2003-01-02 | Jukka-Pekka Salmenkaita | Method and business process to maintain privacy in distributed recommendation systems |
US6678516B2 (en) * | 2001-05-21 | 2004-01-13 | Nokia Corporation | Method, system, and apparatus for providing services in a privacy enabled mobile and Ubicom environment |
US20030005112A1 (en) * | 2001-06-28 | 2003-01-02 | Krautkremer Todd Joseph | Methods, apparatuses and systems enabling a network services provider to deliver application performance management services |
US7158792B1 (en) * | 2001-09-20 | 2007-01-02 | Sprint Communications Company L.P. | Selecting a wireless link in a public wireless communication network |
US7882029B2 (en) * | 2001-10-16 | 2011-02-01 | Hewlett-Packard Development Company, L.P. | Centralized billing credit system utilizing a predetermined unit of usage |
US7317699B2 (en) * | 2001-10-26 | 2008-01-08 | Research In Motion Limited | System and method for controlling configuration settings for mobile communication devices and services |
US20040030705A1 (en) * | 2001-11-27 | 2004-02-12 | Accenture Global Services, Gmbh | Service control architecture |
US8126722B2 (en) * | 2001-12-20 | 2012-02-28 | Verizon Business Global Llc | Application infrastructure platform (AIP) |
US7644151B2 (en) * | 2002-01-31 | 2010-01-05 | Lancope, Inc. | Network service zone locking |
US7325037B2 (en) * | 2002-02-27 | 2008-01-29 | Eastman Kodak Company | Method and system for client-based adaptive networking system |
US7322044B2 (en) * | 2002-06-03 | 2008-01-22 | Airdefense, Inc. | Systems and methods for automated network policy exception detection and correction |
US20040019539A1 (en) * | 2002-07-25 | 2004-01-29 | 3Com Corporation | Prepaid billing system for wireless data networks |
US20040044623A1 (en) * | 2002-08-28 | 2004-03-04 | Wake Susan L. | Billing system for wireless device activity |
US7324447B1 (en) * | 2002-09-30 | 2008-01-29 | Packeteer, Inc. | Methods, apparatuses and systems facilitating concurrent classification and control of tunneled and non-tunneled network traffic |
US7197321B2 (en) * | 2003-02-25 | 2007-03-27 | Boston Communications Group, Inc. | Method and system for providing supervisory control over wireless phone usage |
US6998985B2 (en) * | 2003-03-05 | 2006-02-14 | Dmatek, Ltd. | Monitoring and tracking network |
US8108520B2 (en) * | 2003-06-19 | 2012-01-31 | Nokia Corporation | Apparatus and method for providing quality of service for a network data connection |
US7877090B2 (en) * | 2003-06-27 | 2011-01-25 | Oracle International Corporation | Roaming across different access mechanisms and network technologies |
US7668903B2 (en) * | 2003-07-07 | 2010-02-23 | Xerox Corporation | Method and apparatus for dynamically delivering service profiles to clients |
US20050009499A1 (en) * | 2003-07-08 | 2005-01-13 | Karl Koster | Systems and methods for billing a mobile wireless subscriber for fixed location service |
US20050021995A1 (en) * | 2003-07-21 | 2005-01-27 | July Systems Inc. | Application rights management in a mobile environment |
US20050055291A1 (en) * | 2003-09-04 | 2005-03-10 | Sbc Knowledge Ventures, L.P. | Shared usage telecommunications billing system and method |
US20050055309A1 (en) * | 2003-09-04 | 2005-03-10 | Dwango North America | Method and apparatus for a one click upgrade for mobile applications |
US7865182B2 (en) * | 2003-10-08 | 2011-01-04 | Single Touch Interactive, Inc. | Over the air provisioning of mobile device settings |
US8350700B2 (en) * | 2004-02-04 | 2013-01-08 | Contigo Solutions, Inc. | System for, and method of, monitoring the movement of mobile items |
US7167078B2 (en) * | 2004-02-19 | 2007-01-23 | Pourchot Shawn C | Electric, telephone or network access control system and method |
US7873705B2 (en) * | 2004-03-12 | 2011-01-18 | Flash Networks Ltd. | System and method for identifying content service within content server |
US7644267B2 (en) * | 2004-03-31 | 2010-01-05 | Nokia Corporation | Controlling access to services in a communications system |
US20070033194A1 (en) * | 2004-05-21 | 2007-02-08 | Srinivas Davanum M | System and method for actively managing service-oriented architecture |
US7349695B2 (en) * | 2004-06-02 | 2008-03-25 | Nokia Corporation | Multimode roaming mobile devices |
US20060019632A1 (en) * | 2004-07-12 | 2006-01-26 | At&T Wireless Services, Inc. | Dedicated wireless device business method |
US7486185B2 (en) * | 2004-07-14 | 2009-02-03 | Spectrum Tracking Systems, Inc. | Method and system for providing tracking services to locate an asset |
US20060026679A1 (en) * | 2004-07-29 | 2006-02-02 | Zakas Phillip H | System and method of characterizing and managing electronic traffic |
US7903553B2 (en) * | 2004-08-05 | 2011-03-08 | Huawei Technologies Co., Ltd. | Method, apparatus, edge router and system for providing QoS guarantee |
US20060034256A1 (en) * | 2004-08-13 | 2006-02-16 | Nokia Corporation | System and method for service discovery during connection setup in a wireless environment |
US20060040642A1 (en) * | 2004-08-20 | 2006-02-23 | Adam Boris | Service detail record application and system |
US20060045245A1 (en) * | 2004-08-27 | 2006-03-02 | Aaron Jeffrey A | Methods, systems and computer program products for monitoring service usage |
US20060048223A1 (en) * | 2004-08-31 | 2006-03-02 | Lee Michael C | Method and system for providing tamper-resistant software |
US20080039102A1 (en) * | 2004-09-08 | 2008-02-14 | Pat Sewall | Hotspot Communication Limiter |
US7346410B2 (en) * | 2004-12-16 | 2008-03-18 | Seiko Epson Corporation | Method and system for manufacturing electronic device, electronic device, and electro-optical apparatus |
US20070036312A1 (en) * | 2005-06-24 | 2007-02-15 | Lucent Technologies Inc. | Converged offline charging and online charging |
US20070022289A1 (en) * | 2005-07-20 | 2007-01-25 | Mci, Inc. | Method and system for providing secure credential storage to support interdomain traversal |
US20070019670A1 (en) * | 2005-07-22 | 2007-01-25 | Eric Falardeau | Mobile connectivity solution |
US20070055694A1 (en) * | 2005-08-19 | 2007-03-08 | Customer Feedback Solutions, Inc. | System and method for providing a unified customer feedback solution |
US7647047B2 (en) * | 2005-09-07 | 2010-01-12 | Ventraq Corporation | Consumer configurable mobile communication solution |
US7868778B2 (en) * | 2005-09-20 | 2011-01-11 | David Norris Kenwright | Apparatus and method for proximity-responsive display materials |
US7873344B2 (en) * | 2005-10-03 | 2011-01-18 | Cisco Technology, Inc. | System and method to distribute emergency information |
US20070093243A1 (en) * | 2005-10-25 | 2007-04-26 | Vivek Kapadekar | Device management system |
US20080059474A1 (en) * | 2005-12-29 | 2008-03-06 | Blue Jungle | Detecting Behavioral Patterns and Anomalies Using Activity Profiles |
US20080066150A1 (en) * | 2005-12-29 | 2008-03-13 | Blue Jungle | Techniques of Transforming Policies to Enforce Control in an Information Management System |
US20080066149A1 (en) * | 2005-12-29 | 2008-03-13 | Blue Jungle | Analyzing Activity Data of an Information Management System |
US7881199B2 (en) * | 2006-01-04 | 2011-02-01 | Alcatel Lucent | System and method for prioritization of traffic through internet access network |
US7685131B2 (en) * | 2006-02-28 | 2010-03-23 | International Business Machines Corporation | Web services database cluster architecture |
US7907970B2 (en) * | 2006-04-14 | 2011-03-15 | Qualcomm Incorporated | Providing quality of service for various traffic flows in a communications environment |
US20080005561A1 (en) * | 2006-05-18 | 2008-01-03 | Research In Motion Limited | Automatic security action invocation for mobile communications device |
US20080005285A1 (en) * | 2006-07-03 | 2008-01-03 | Impulse Point, Llc | Method and System for Self-Scaling Generic Policy Tracking |
US20080059743A1 (en) * | 2006-07-06 | 2008-03-06 | Sandisk Il Ltd. | Portable Storage Device With Updatable Access Permission |
US20080052387A1 (en) * | 2006-08-22 | 2008-02-28 | Heinz John M | System and method for tracking application resource usage |
US20080049630A1 (en) * | 2006-08-22 | 2008-02-28 | Kozisek Steven E | System and method for monitoring and optimizing network performance to a wireless device |
US20080064367A1 (en) * | 2006-09-13 | 2008-03-13 | Mformation Technologies Inc. | System and method to enable subscriber self-activation of wireless data terminals |
US20080070550A1 (en) * | 2006-09-20 | 2008-03-20 | Hose David A | Providing Subscriber Specific Information Across Wireless Networks |
US7890084B1 (en) * | 2006-10-30 | 2011-02-15 | Cellco Partnership | Enterprise instant message aggregator |
US8102814B2 (en) * | 2006-11-14 | 2012-01-24 | Cisco Technology, Inc. | Access point profile for a mesh access point in a wireless mesh network |
US7890111B2 (en) * | 2006-12-22 | 2011-02-15 | Embarq Holdings Company, Llc | System and method for virtual wireless roaming |
US20100071053A1 (en) * | 2006-12-29 | 2010-03-18 | Prodea Systems, Inc. | Presence Status Notification From Digital Endpoint Devices Through A Multi-Services Gateway Device At The User Premises |
US20080167027A1 (en) * | 2007-01-07 | 2008-07-10 | Patrice Gautier | Graphical user interface and method for mobile device activation |
US8352980B2 (en) * | 2007-02-15 | 2013-01-08 | At&T Intellectual Property I, Lp | System and method for single sign on targeted advertising |
US8126123B2 (en) * | 2007-02-27 | 2012-02-28 | Alcatel Lucent | Pre-biller in internet protocol multimedia subsystem (IMS) charging gateway function (CGF) |
US20090046723A1 (en) * | 2007-08-16 | 2009-02-19 | Rahman Reshad A | Distinguishing between connectivity verification availability and forwarding protocol functionality in a computer network |
US20090054030A1 (en) * | 2007-08-24 | 2009-02-26 | Microsoft Corporation | Mobile billboard and usage advisor |
US20090067372A1 (en) * | 2007-09-07 | 2009-03-12 | Qualcomm Incorporated | Host-based quality of service for wireless communications |
US7986935B1 (en) * | 2007-10-26 | 2011-07-26 | Sprint Communications Company L.P. | Service plan optimizer |
US20090197585A1 (en) * | 2008-02-01 | 2009-08-06 | Aaron Jeffrey A | Quality of Service for Grouped Cellular Devices |
US8094551B2 (en) * | 2008-05-13 | 2012-01-10 | At&T Mobility Ii Llc | Exchange of access control lists to manage femto cell coverage |
US20100027469A1 (en) * | 2008-06-12 | 2010-02-04 | At&T Mobility Ii Llc | Point of sales and customer support for femtocell service and equipment |
US20100041364A1 (en) * | 2008-06-12 | 2010-02-18 | At&T Mobility Ii Llc | Femtocell service registration, activation, and provisioning |
US7886047B1 (en) * | 2008-07-08 | 2011-02-08 | Sprint Communications Company L.P. | Audience measurement of wireless web subscribers |
US20100043068A1 (en) * | 2008-08-14 | 2010-02-18 | Juniper Networks, Inc. | Routing device having integrated mpls-aware firewall |
US8385896B2 (en) * | 2008-09-08 | 2013-02-26 | Proxicom Wireless, Llc | Exchanging identifiers between wireless communication to determine further information to be exchanged or further services to be provided |
US8386386B1 (en) * | 2009-01-05 | 2013-02-26 | Sprint Communications Company L.P. | Phone usage pattern as credit card fraud detection trigger |
Cited By (178)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10491748B1 (en) | 2006-04-03 | 2019-11-26 | Wai Wu | Intelligent communication routing system and method |
US10198142B1 (en) | 2007-08-06 | 2019-02-05 | Gogrid, LLC | Multi-server control panel |
US9083609B2 (en) | 2007-09-26 | 2015-07-14 | Nicira, Inc. | Network operating system for managing and securing networks |
US10749736B2 (en) | 2007-09-26 | 2020-08-18 | Nicira, Inc. | Network operating system for managing and securing networks |
US20090138577A1 (en) * | 2007-09-26 | 2009-05-28 | Nicira Networks | Network operating system for managing and securing networks |
US11683214B2 (en) | 2007-09-26 | 2023-06-20 | Nicira, Inc. | Network operating system for managing and securing networks |
US9876672B2 (en) | 2007-09-26 | 2018-01-23 | Nicira, Inc. | Network operating system for managing and securing networks |
US20090144182A1 (en) * | 2007-11-30 | 2009-06-04 | Seiko Epson Corporation | Task management system |
US8296202B2 (en) * | 2007-11-30 | 2012-10-23 | Seiko Epson Corporation | Task management system |
US9197706B2 (en) | 2008-12-16 | 2015-11-24 | Qualcomm Incorporated | Apparatus and method for bundling application services with inbuilt connectivity management |
US9609510B2 (en) | 2009-01-28 | 2017-03-28 | Headwater Research Llc | Automated credential porting for mobile devices |
US10931600B2 (en) | 2009-04-01 | 2021-02-23 | Nicira, Inc. | Method and apparatus for implementing and managing virtual switches |
US11425055B2 (en) | 2009-04-01 | 2022-08-23 | Nicira, Inc. | Method and apparatus for implementing and managing virtual switches |
US8966035B2 (en) | 2009-04-01 | 2015-02-24 | Nicira, Inc. | Method and apparatus for implementing and managing distributed virtual switches in several hosts and physical forwarding elements |
US9590919B2 (en) | 2009-04-01 | 2017-03-07 | Nicira, Inc. | Method and apparatus for implementing and managing virtual switches |
US8990338B2 (en) | 2009-09-10 | 2015-03-24 | Google Technology Holdings LLC | Method of exchanging photos with interface content provider website |
US9026581B2 (en) | 2009-09-10 | 2015-05-05 | Google Technology Holdings LLC | Mobile device and method of operating same to interface content provider website |
US8589516B2 (en) | 2009-09-10 | 2013-11-19 | Motorola Mobility Llc | Method and system for intermediating content provider website and mobile device |
US9450994B2 (en) | 2009-09-10 | 2016-09-20 | Google Technology Holdings LLC | Mobile device and method of operating same to interface content provider website |
US20170372330A1 (en) * | 2009-09-11 | 2017-12-28 | Comscore, Inc. | Determining client system attributes |
US11341510B2 (en) * | 2009-09-11 | 2022-05-24 | Comscore, Inc. | Determining client system attributes |
US20110066491A1 (en) * | 2009-09-16 | 2011-03-17 | Telefonaktiebolaget L M Ericsson (Publ) | Method and Communication Device for Using a First Service Based on an Account Chargeable with the Use of a Second Service |
US9106563B2 (en) | 2009-10-07 | 2015-08-11 | Wichorus, Inc. | Method and apparatus for switching communications traffic in a communications network |
US8533360B2 (en) | 2009-10-07 | 2013-09-10 | Wichorus, Inc. | Method and apparatus to report resource values in a mobile network |
US20110087786A1 (en) * | 2009-10-07 | 2011-04-14 | Wichorus, Inc. | Method and apparatus for efficient resource allocation of quality of service profiles in mobile networks |
US20110085439A1 (en) * | 2009-10-07 | 2011-04-14 | Wichorus, Inc. | Method and apparatus for switching communications traffic in a communications network |
US9385970B2 (en) | 2009-10-07 | 2016-07-05 | Wichorus, Inc. | Method and apparatus for assigning resources in a network node |
US20110085571A1 (en) * | 2009-10-07 | 2011-04-14 | Tellabs Operations, Inc. | Method and apparatus for assigning resources in a network node |
US8780720B2 (en) | 2010-01-11 | 2014-07-15 | Venturi Ip Llc | Radio access network load and condition aware traffic shaping control |
US20130238671A1 (en) * | 2010-02-24 | 2013-09-12 | Salesforce.Com, Inc | System, method and computer program product for monitoring data activity utilizing a shared data store |
US9237080B2 (en) * | 2010-02-24 | 2016-01-12 | Salesforce.Com, Inc. | System, method and computer program product for monitoring data activity utilizing a shared data store |
US20110208858A1 (en) * | 2010-02-24 | 2011-08-25 | Salesforce.Com, Inc. | System, method and computer program product for monitoring data activity utilizing a shared data store |
US20130254387A1 (en) * | 2010-02-24 | 2013-09-26 | Salesforce.Com, Inc | System, method and computer program product for monitoring data activity utilizing a shared data store |
US9178788B2 (en) * | 2010-02-24 | 2015-11-03 | Salesforce.Com, Inc. | System, method and computer program product for monitoring data activity utilizing a shared data store |
US8898287B2 (en) * | 2010-02-24 | 2014-11-25 | Salesforce.Com, Inc. | System, method and computer program product for monitoring data activity utilizing a shared data store |
US8285749B2 (en) * | 2010-03-05 | 2012-10-09 | Hitachi, Ltd. | Computer system and recording medium |
US8667298B2 (en) * | 2010-03-10 | 2014-03-04 | Red Hat, Inc. | Module signing for unprivileged users to create and load trustworthy kernel modules |
US20110225420A1 (en) * | 2010-03-10 | 2011-09-15 | Eigler Frank Ch | Module signing for unprivileged users to create and load trustworthy kernel modules |
US20120079559A1 (en) * | 2010-04-02 | 2012-03-29 | Interdigital Patent Holdings, Inc. | Methods for policy management |
US20110279286A1 (en) * | 2010-05-11 | 2011-11-17 | Lsis Co., Ltd. | Energy-related information display apparatus and method thereof |
US9311664B2 (en) * | 2010-05-25 | 2016-04-12 | Salesforce.Com, Inc. | Systems and methods for automatically collection of performance data in a multi-tenant database system environment |
US20110295728A1 (en) * | 2010-05-25 | 2011-12-01 | Salesforce.Com, Inc. | Systems and methods for automatically collection of performance data in a multi-tenant database system environment |
US20110307948A1 (en) * | 2010-06-15 | 2011-12-15 | Microsoft Corporation | Extending a customer relationship management eventing framework to a cloud computing environment in a secure manner |
US8544075B2 (en) * | 2010-06-15 | 2013-09-24 | Microsoft Corporation | Extending a customer relationship management eventing framework to a cloud computing environment in a secure manner |
US9313604B1 (en) * | 2010-06-22 | 2016-04-12 | Amazon Technologies, Inc. | Network service request throttling system |
US8717895B2 (en) | 2010-07-06 | 2014-05-06 | Nicira, Inc. | Network virtualization apparatus and method with a table mapping engine |
US9391928B2 (en) | 2010-07-06 | 2016-07-12 | Nicira, Inc. | Method and apparatus for interacting with a network information base in a distributed network control system with multiple controller instances |
US8842679B2 (en) | 2010-07-06 | 2014-09-23 | Nicira, Inc. | Control system that elects a master controller instance for switching elements |
US11677588B2 (en) | 2010-07-06 | 2023-06-13 | Nicira, Inc. | Network control apparatus and method for creating and modifying logical switching elements |
US8880468B2 (en) | 2010-07-06 | 2014-11-04 | Nicira, Inc. | Secondary storage architecture for a network control system that utilizes a primary network information base |
US8830823B2 (en) | 2010-07-06 | 2014-09-09 | Nicira, Inc. | Distributed control platform for large-scale production networks |
US8913483B2 (en) | 2010-07-06 | 2014-12-16 | Nicira, Inc. | Fault tolerant managed switching element architecture |
US9692655B2 (en) | 2010-07-06 | 2017-06-27 | Nicira, Inc. | Packet processing in a network with hierarchical managed switching elements |
US8959215B2 (en) | 2010-07-06 | 2015-02-17 | Nicira, Inc. | Network virtualization |
US8958292B2 (en) | 2010-07-06 | 2015-02-17 | Nicira, Inc. | Network control apparatus and method with port security controls |
US8964598B2 (en) | 2010-07-06 | 2015-02-24 | Nicira, Inc. | Mesh architectures for managed switching elements |
US8964528B2 (en) | 2010-07-06 | 2015-02-24 | Nicira, Inc. | Method and apparatus for robust packet distribution among hierarchical managed switching elements |
US8966040B2 (en) | 2010-07-06 | 2015-02-24 | Nicira, Inc. | Use of network information base structure to establish communication between applications |
US8817621B2 (en) | 2010-07-06 | 2014-08-26 | Nicira, Inc. | Network virtualization apparatus |
US8817620B2 (en) | 2010-07-06 | 2014-08-26 | Nicira, Inc. | Network virtualization apparatus and method |
US9007903B2 (en) | 2010-07-06 | 2015-04-14 | Nicira, Inc. | Managing a network by controlling edge and non-edge switching elements |
US9008087B2 (en) | 2010-07-06 | 2015-04-14 | Nicira, Inc. | Processing requests in a network control system with multiple controller instances |
US11641321B2 (en) | 2010-07-06 | 2023-05-02 | Nicira, Inc. | Packet processing for logical datapath sets |
US9680750B2 (en) | 2010-07-06 | 2017-06-13 | Nicira, Inc. | Use of tunnels to hide network addresses |
US8775594B2 (en) | 2010-07-06 | 2014-07-08 | Nicira, Inc. | Distributed network control system with a distributed hash table |
US10021019B2 (en) | 2010-07-06 | 2018-07-10 | Nicira, Inc. | Packet processing for logical datapath sets |
US10038597B2 (en) | 2010-07-06 | 2018-07-31 | Nicira, Inc. | Mesh architectures for managed switching elements |
US10103939B2 (en) | 2010-07-06 | 2018-10-16 | Nicira, Inc. | Network control apparatus and method for populating logical datapath sets |
US9049153B2 (en) | 2010-07-06 | 2015-06-02 | Nicira, Inc. | Logical packet processing pipeline that retains state information to effectuate efficient processing of packets |
US11539591B2 (en) | 2010-07-06 | 2022-12-27 | Nicira, Inc. | Distributed network control system with one master controller per logical datapath set |
US11509564B2 (en) | 2010-07-06 | 2022-11-22 | Nicira, Inc. | Method and apparatus for replicating network information base in a distributed network control system with multiple controller instances |
US9077664B2 (en) | 2010-07-06 | 2015-07-07 | Nicira, Inc. | One-hop packet processing in a network with managed switching elements |
US9525647B2 (en) | 2010-07-06 | 2016-12-20 | Nicira, Inc. | Network control apparatus and method for creating and modifying logical switching elements |
US8761036B2 (en) | 2010-07-06 | 2014-06-24 | Nicira, Inc. | Network control apparatus and method with quality of service controls |
US8750119B2 (en) | 2010-07-06 | 2014-06-10 | Nicira, Inc. | Network control apparatus and method with table mapping engine |
US9106587B2 (en) | 2010-07-06 | 2015-08-11 | Nicira, Inc. | Distributed network control system with one master controller per managed switching element |
US9112811B2 (en) | 2010-07-06 | 2015-08-18 | Nicira, Inc. | Managed switching elements used as extenders |
US8750164B2 (en) | 2010-07-06 | 2014-06-10 | Nicira, Inc. | Hierarchical managed switch architecture |
US8837493B2 (en) | 2010-07-06 | 2014-09-16 | Nicira, Inc. | Distributed network control apparatus and method |
US12028215B2 (en) | 2010-07-06 | 2024-07-02 | Nicira, Inc. | Distributed network control system with one master controller per logical datapath set |
US10320585B2 (en) | 2010-07-06 | 2019-06-11 | Nicira, Inc. | Network control apparatus and method for creating and modifying logical switching elements |
US9172663B2 (en) | 2010-07-06 | 2015-10-27 | Nicira, Inc. | Method and apparatus for replicating network information base in a distributed network control system with multiple controller instances |
US8743889B2 (en) | 2010-07-06 | 2014-06-03 | Nicira, Inc. | Method and apparatus for using a network information base to control a plurality of shared network infrastructure switching elements |
US11223531B2 (en) | 2010-07-06 | 2022-01-11 | Nicira, Inc. | Method and apparatus for interacting with a network information base in a distributed network control system with multiple controller instances |
US8743888B2 (en) | 2010-07-06 | 2014-06-03 | Nicira, Inc. | Network control apparatus and method |
US8718070B2 (en) | 2010-07-06 | 2014-05-06 | Nicira, Inc. | Distributed network virtualization apparatus and method |
US9363210B2 (en) | 2010-07-06 | 2016-06-07 | Nicira, Inc. | Distributed network control system with one master controller per logical datapath set |
US9231891B2 (en) | 2010-07-06 | 2016-01-05 | Nicira, Inc. | Deployment of hierarchical managed switching elements |
US10686663B2 (en) | 2010-07-06 | 2020-06-16 | Nicira, Inc. | Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches |
US10326660B2 (en) | 2010-07-06 | 2019-06-18 | Nicira, Inc. | Network virtualization apparatus and method |
US11743123B2 (en) | 2010-07-06 | 2023-08-29 | Nicira, Inc. | Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches |
US11979280B2 (en) | 2010-07-06 | 2024-05-07 | Nicira, Inc. | Network control apparatus and method for populating logical datapath sets |
US9300603B2 (en) | 2010-07-06 | 2016-03-29 | Nicira, Inc. | Use of rich context tags in logical data processing |
US9306875B2 (en) | 2010-07-06 | 2016-04-05 | Nicira, Inc. | Managed switch architectures for implementing logical datapath sets |
US11876679B2 (en) | 2010-07-06 | 2024-01-16 | Nicira, Inc. | Method and apparatus for interacting with a network information base in a distributed network control system with multiple controller instances |
US9124436B2 (en) | 2010-12-16 | 2015-09-01 | Cellco Partnership | Intelligent automated data usage upgrade recommendation |
US20120158829A1 (en) * | 2010-12-20 | 2012-06-21 | Kalle Ahmavaara | Methods and apparatus for providing or receiving data connectivity |
US9288230B2 (en) * | 2010-12-20 | 2016-03-15 | Qualcomm Incorporated | Methods and apparatus for providing or receiving data connectivity |
US9037656B2 (en) * | 2010-12-20 | 2015-05-19 | Google Technology Holdings LLC | Method and system for facilitating interaction with multiple content provider websites |
US20120158866A1 (en) * | 2010-12-20 | 2012-06-21 | Motorola-Mobility, Inc. | Method and System for Facilitating Interaction with Multiple Content Provider Websites |
US20120158578A1 (en) * | 2010-12-21 | 2012-06-21 | Sedayao Jeffrey C | Highly granular cloud computing marketplace |
US9471907B2 (en) * | 2010-12-21 | 2016-10-18 | Intel Corporation | Highly granular cloud computing marketplace |
US20140179277A1 (en) * | 2011-03-01 | 2014-06-26 | Tracfone Wireless, Inc. | System, Method and Apparatus for Pairing SIM or UICC Cards with Authorized Wireless Devices |
US8660533B2 (en) * | 2011-03-01 | 2014-02-25 | Tracfone Wireless, Inc. | System, method and apparatus for pairing SIM or UICC cards with authorized wireless devices |
US9154957B2 (en) * | 2011-03-01 | 2015-10-06 | Tracfone Wireless, Inc. | System, method and apparatus for pairing SIM or UICC cards with authorized wireless devices |
US20120264400A1 (en) * | 2011-03-01 | 2012-10-18 | Tracfone Wireless, Inc. | System, method and apparatus for pairing sim or uicc cards with authorized wireless devices |
US9503884B2 (en) * | 2011-03-01 | 2016-11-22 | Tracfone Wireless, Inc. | System, method and apparatus for pairing SIM or UICC cards with authorized wireless devices |
US9405902B1 (en) * | 2011-03-15 | 2016-08-02 | Trend Micro Incorporated | Anti-malware service in multi-tenant cloud computing environments |
US9661687B2 (en) | 2011-03-23 | 2017-05-23 | Verizon Patent And Licensing Inc. | Coaxial cable interface to outdoor broadband unit |
US20120243463A1 (en) * | 2011-03-23 | 2012-09-27 | Verizon Patent And Licensing Inc. | Coaxial cable interface to outdoor broadband unit |
US8718085B2 (en) * | 2011-03-23 | 2014-05-06 | Verizon Patent And Licensing Inc. | Coaxial cable interface to outdoor broadband unit |
US9043455B1 (en) | 2011-04-06 | 2015-05-26 | Cellco Partnership | Universal data remote |
US9723092B1 (en) | 2011-04-07 | 2017-08-01 | Cellco Partnership | Universal data remote application framework |
US9043452B2 (en) | 2011-05-04 | 2015-05-26 | Nicira, Inc. | Network control apparatus and method for port isolation |
US9015311B2 (en) * | 2011-05-24 | 2015-04-21 | Citrix Systems, Inc. | Systems and methods for analyzing network metrics |
US20120317276A1 (en) * | 2011-05-24 | 2012-12-13 | Muraliraja Muniraju | Systems and methods for analyzing network metrics |
US9722934B2 (en) | 2011-05-24 | 2017-08-01 | Citrix Systems, Inc. | Systems and methods for analyzing network metrics |
US9652727B1 (en) * | 2011-10-10 | 2017-05-16 | West Corporation | Mobile care with a virtual queue |
US9165139B2 (en) | 2011-10-10 | 2015-10-20 | Openpeak Inc. | System and method for creating secure applications |
US20150038111A1 (en) * | 2011-11-15 | 2015-02-05 | Deutsche Telekom Ag | Method and telecommunications network utilizing more than one online charging system for a given user |
US9485105B2 (en) * | 2011-11-15 | 2016-11-01 | Deutsche Telekom Ag | Method and telecommunications network utilizing more than one online charging system for a given user |
US10013269B2 (en) * | 2012-02-22 | 2018-07-03 | Vmware, Inc. | Component framework for deploying virtual machines using service provisioning information |
US20130219388A1 (en) * | 2012-02-22 | 2013-08-22 | Vmware, Inc. | Component framework for virtual machines |
US9047462B2 (en) * | 2012-03-20 | 2015-06-02 | Guangdong Electronics Industry Institute Ltd. | Computer account management system and realizing method thereof |
US20140289829A1 (en) * | 2012-03-20 | 2014-09-25 | Guangdong Electronics Industry Institute Ltd | Computer account management system and realizing method thereof |
US20130262293A1 (en) * | 2012-03-30 | 2013-10-03 | Robert L. Garner, JR. | Variable charging of audience member temporal viewing of a live video chat performance |
US9712399B2 (en) * | 2012-04-16 | 2017-07-18 | Clinct Holding B.V. | Computer network for services retrieval, method for managing such network and a computer system for such network |
US20150106495A1 (en) * | 2012-04-16 | 2015-04-16 | Clinct Holding B.V. | Computer Network for Services Retrieval, Method for Managing Such Network and a Computer System for Such Network |
WO2013170198A3 (en) * | 2012-05-10 | 2014-01-23 | Drawbridge, Inc. | System and method for determining related digital identities |
US10510094B2 (en) | 2012-05-10 | 2019-12-17 | Microsoft Technology Licensing, Llc | Method for transmitting information to device on a network based upon information associated with a different device on the network |
US10248968B2 (en) | 2012-05-10 | 2019-04-02 | Drawbridge, Inc. | System to deliver content to internet-connected devices that have shared a server internet protocol address |
US8561142B1 (en) * | 2012-06-01 | 2013-10-15 | Symantec Corporation | Clustered device access control based on physical and temporal proximity to the user |
US10368215B2 (en) | 2012-11-06 | 2019-07-30 | Tracfone Wireless, Inc. | Hybrid network based metering server and tracking client for wireless services |
US8805323B2 (en) | 2012-11-06 | 2014-08-12 | Tracfone Wireless, Inc. | Hybrid network based metering server and tracking client for wireless services |
US9204281B2 (en) | 2012-11-06 | 2015-12-01 | Tracfone Wireless, Inc. | Hybrid network based metering server and tracking client for wireless services |
US11588650B2 (en) | 2013-03-15 | 2023-02-21 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US10305695B1 (en) | 2013-03-15 | 2019-05-28 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US10841104B2 (en) | 2013-03-15 | 2020-11-17 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US9215075B1 (en) | 2013-03-15 | 2015-12-15 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US9942051B1 (en) | 2013-03-15 | 2018-04-10 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US11930126B2 (en) | 2013-03-15 | 2024-03-12 | Piltorak Technologies LLC | System and method for secure relayed communications from an implantable medical device |
US9585186B2 (en) * | 2013-08-15 | 2017-02-28 | Benu Networks, Inc. | System and method of providing advanced services in a virtual CPE deployment |
US20150237667A1 (en) * | 2013-08-15 | 2015-08-20 | Benu Networks, Inc. | System and method of providing advanced services in a virtual cpe deployment |
US9686808B2 (en) | 2013-08-15 | 2017-06-20 | Benu Networks, Inc. | Centrally managed WI-FI |
US20150154252A1 (en) * | 2013-12-04 | 2015-06-04 | Microsoft Corporation | Enhanced service environments with user-specific working sets |
US10417612B2 (en) * | 2013-12-04 | 2019-09-17 | Microsoft Technology Licensing, Llc | Enhanced service environments with user-specific working sets |
US10606718B1 (en) | 2013-12-19 | 2020-03-31 | Amdocs Development Limited | System, method, and computer program for managing fault recovery in network function virtualization (Nfv) based networks |
US9794187B1 (en) | 2013-12-19 | 2017-10-17 | Amdocs Software Systems Limited | System, method, and computer program for resource conversion in a network function virtualization (NFV) based communication network |
US9806979B1 (en) | 2013-12-19 | 2017-10-31 | Amdocs Software Systems Limited | System, method, and computer program for optimizing a chain of virtual network functions in a network based on network function virtualization (NFV) |
US9760428B1 (en) | 2013-12-19 | 2017-09-12 | Amdocs Software Systems Limited | System, method, and computer program for performing preventative maintenance in a network function virtualization (NFV) based communication network |
US9838265B2 (en) | 2013-12-19 | 2017-12-05 | Amdocs Software Systems Limited | System, method, and computer program for inter-module communication in a network based on network function virtualization (NFV) |
US9645899B1 (en) | 2013-12-19 | 2017-05-09 | Amdocs Software Systems Limited | System, method, and computer program for managing fault recovery in network function virtualization (NFV) based networks |
US10063633B1 (en) | 2013-12-19 | 2018-08-28 | Amdocs Development Limited | System, method, and computer program for managing hierarchy and optimization in a network function virtualization (NFV) based communication network |
US9460286B1 (en) | 2013-12-19 | 2016-10-04 | Amdocs Software Systems Limited | System, method, and computer program for managing security in a network function virtualization (NFV) based communication network |
US9384028B1 (en) | 2013-12-19 | 2016-07-05 | Amdocs Software Systems Limited | System, method, and computer program for preserving service continuity in a network function virtualization (NFV) based communication network |
US11218423B2 (en) * | 2014-03-24 | 2022-01-04 | Huawei Technologies Co., Ltd. | Method for service implementation in network function virtualization (NFV) system and communications unit |
US10862823B2 (en) | 2014-03-24 | 2020-12-08 | Huawei Technologies Co., Ltd. | Method for service implementation in network function virtualization (NFV) system and communications unit |
US20190058670A1 (en) * | 2014-03-24 | 2019-02-21 | Huawei Technologies Co., Ltd. | Method for service implementation in network function virtualization (nfv) system and communications unit |
US20150326461A1 (en) * | 2014-05-08 | 2015-11-12 | Accenture Global Services Limited | Network usage monitoring and analytics for differentiated data services |
US9628363B2 (en) * | 2014-05-08 | 2017-04-18 | Accenture Global Services Limited | Network usage monitoring and analytics for differentiated data services |
US11245747B2 (en) | 2014-07-31 | 2022-02-08 | Honeywell International Inc. | Monitoring a building management system |
US20170324808A1 (en) * | 2014-07-31 | 2017-11-09 | Honeywell International Inc. | Monitoring a building management system |
US10666717B2 (en) * | 2014-07-31 | 2020-05-26 | Honeywell International Inc. | Monitoring a building management system |
US9232012B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for data usage accounting in a computing device |
US10410154B2 (en) | 2014-09-05 | 2019-09-10 | Vmware, Inc. | Method and system for enabling data usage accounting through a relay |
US10943198B2 (en) | 2014-09-05 | 2021-03-09 | Vmware, Inc. | Method and system for enabling data usage accounting through a relay |
US9106538B1 (en) * | 2014-09-05 | 2015-08-11 | Openpeak Inc. | Method and system for enabling data usage accounting through a relay |
US9350818B2 (en) | 2014-09-05 | 2016-05-24 | Openpeak Inc. | Method and system for enabling data usage accounting for unreliable transport communication |
US9232013B1 (en) | 2014-09-05 | 2016-01-05 | Openpeak Inc. | Method and system for enabling data usage accounting |
US9998428B2 (en) | 2015-06-29 | 2018-06-12 | Cisco Technology, Inc. | Virtual routing and forwarding (VRF) for asymmetrical virtual service provider (VSP) tunnels |
US9954958B2 (en) * | 2016-01-29 | 2018-04-24 | Red Hat, Inc. | Shared resource management |
WO2017136166A1 (en) * | 2016-02-04 | 2017-08-10 | TEN DIGIT Communications LLC | Intermediary device for data message network routing and enhancement in a contact center environment |
US11431847B2 (en) | 2016-02-04 | 2022-08-30 | Virtual Hold Technology Solutions, Llc | Intermediary device for data message network routing and enhancement in a contact center environment |
US10455090B2 (en) | 2016-02-04 | 2019-10-22 | TEN DIGIT Communications LLC | Intermediary device for data message network routing and enhancement in a contact center environment |
US10367766B2 (en) | 2017-01-20 | 2019-07-30 | TEN DIGIT Communications LLC | Intermediary device for data message network routing |
US11146517B2 (en) | 2017-01-20 | 2021-10-12 | Virtual Hold Technology Solutions, Llc | Intermediary device for data message network routing |
US11297688B2 (en) | 2018-03-22 | 2022-04-05 | goTenna Inc. | Mesh network deployment kit |
US11164398B2 (en) * | 2018-04-18 | 2021-11-02 | Hitachi, Ltd. | Software management system, gateway device, maintenance device, server device, and control method for software management system |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11757943B2 (en) | Automated device provisioning and activation | |
US8351898B2 (en) | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HEADWATER PARTNERS I, LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RALEIGH, GREGORY G.;REEL/FRAME:022799/0427 Effective date: 20090324 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: HEADWATER RESEARCH LLC, TEXAS Free format text: MERGER AND CHANGE OF NAME;ASSIGNORS:HEADWATER PARTNERS I LLC;HEADWATER MANAGEMENT LLC;REEL/FRAME:041268/0108 Effective date: 20161229 |