ES2655499T3 - Automated device provisioning and activation - Google Patents

Abstract

A mobile device (100) comprising: a cellular network modem (942) that can perform data communication through different operator access networks; and a memory that can store pre-activation credentials and permanent credentials; in which the mobile device is configured to use stored pre-activation credentials and a pre-activation service policy in an environment access mode, in which in the environment access mode the mobile device is configured to provide network access control in accordance with the pre-activation service policy to allow and block access to a first operator access network via the cellular network modem, and in which a permitted network service activity is a sequence of activation comprising: connecting the device to an activation server connected to the Internet through the first operator access network, providing cellular network service options from the activation server to a user of the device, which includes service options Cellular network corresponding to different service providers, accept user input to select a first of the options to be Cellular network service for one selected from the different service providers, forwarding, based on the input, an activation request for the first service option to the activation server, and receiving from the activation server a set of corresponding permanent credentials to the selected service option and selected service provider and store permanent credentials in memory so that permanent credentials replace pre-activation credentials.

Description

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

DESCRIPTION

Automated device provisioning and activation Cross reference to other requests

This application claims priority to U.S. Provisional Patent Application No. 61 / 206,354 (Mandatory Record No. RALEP001 +) titled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed on January 28, 2009, Provisional Patent Application for United States No. 61 / 206,944 (Mandatory Record No. RALEP002 +) titled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed on February 4, 2009, U.S. Provisional Application No. 61 / 207,393 (File No. by RALEP003 +) entitled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD filed on February 10, 2009, and to the Provisional US Patent Application No. 61 / 207,739 (RALEP004 + Mandatory File No.) titled SERVICES POLICY COMMUNICATION SYSTEM AND METHOD presented on February 13, 2009.

Background of the invention

With the advent of digital communications from the mass market and content distribution, many access networks such as wireless networks, cable networks and DSL (Digital Subscriber Line) networks are pressured by the user's ability, with, for For example, wireless networks of EVDO (Optimized Evolution Data), HSPA (High Speed Package Access), LTE (Long Term Evolution), WiMax (Global Interoperability for Microwave Access) and Wi-Fi (Wireless Loyalty) each Once more limited user capacity. Although the capacity of the wireless network will increase with new wireless radio access technologies of higher capacity, such as MIMO (Multiple Input Multiple Output), and the spectrum developing more frequently in the future, these capacity gains are likely to be less than what is required to meet the growing demand for interconnection in the digital network.

Similarly, although wired line access networks, such as cable and DSL, may have higher average capacity per user, wired line user service consumption habits tend to very high bandwidth applications that can consume Quickly available capacity and degrade the global network service experience. Since some components of the service provider costs increase with increasing bandwidth, this trend will also negatively impact the benefits of the service provider.

Any mobile device has to be activated to be usable in a network that normally includes a registration with a specific network operator. Several activation procedures are known in the prior art.

US 2004/0137890 A1 suggests automated activation and provisioning technologies can be applied in a variety of scenarios. For example, an automated activation and provisioning server can translate desired user characteristics into associated provisioning policies. The directives can then be sent to elements of a wireless communications network support system. Activation and provisioning for an abundant set of features can therefore be achieved without manual intervention or reaction to user choices. The reception of user choices can be achieved in real time through a user interface of a mobile wireless device or a web-based user interface.

From US 2008/0167027 are known methods, systems and graphical user interfaces that facilitate the activation of mobile devices, such as communication devices or multi-function devices, by computers. According to one embodiment, the activation of a mobile device with respect to a wireless service provider can be performed by users through the use of a computer (eg personal computer) that communicates with an activation server located remotely . According to another embodiment, the graphical user interfaces can be presented to users to enable end users to easily activate mobile devices.

Document US 2008/0096559 A1 refers to methods and apparatus for providing manual selection of a communication network for a mobile station. A plurality of communication networks are identified by exploring a coverage area within which the mobile station is operating. A plurality of network identifiers corresponding to the plurality of communication networks are then retrieved from the memory of a Subscriber Identity Module (SIM) in accordance with an Enhanced Operator Name Chain (EONS) protocol. Preferably, each network identifier is retrieved based on a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a Location Area Code (LAC). The plurality of network identifiers are presented visually for user selection, and at least two of the network identifiers can be substantially the same. The communication network selected by the user is registered and the network identifier associated with this network is presented visually.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

US 6,879,825 B1 suggests the method of activating a mobile station to communicate with a telecommunications network, the method comprising a two-stage registration procedure whereby in the first registration procedure, a station ID is obtained permanent mobile by the mobile station and in the second registration procedure, the permanent mobile station ID is used to identify the mobile station when programming data is downloaded from the telecommunications network.

Brief description of the drawings

Various embodiments of the invention are disclosed in the following detailed description and in the accompanying drawings.

Figure 1 illustrates a simplified network architecture (eg, "flat") according to some embodiments.

Figure 2 illustrates another simplified network architecture (eg, "flat") that includes an MVNO (Mobile Virtual Network Operator) relationship according to some embodiments.

Figure 3 illustrates another simplified network architecture (eg, "flat") that includes two core providers according to some embodiments.

Figure 4 illustrates a network architecture that includes an overlay configuration of Universal Mobile Telecommunications System (UMTS) in accordance with some embodiments.

Figure 5 illustrates a network architecture that includes an Optimized Evolution Data (EVDO) overlay configuration according to some embodiments.

Figure 6 illustrates a network architecture that includes a 4G LTE overlay configuration and Wi-Fi according to some embodiments.

Figure 7 illustrates a network architecture that includes a WiMax and Wi-Fi overlay configuration according to some embodiments.

Figure 8 illustrates another simplified network architecture (eg, "flat") that includes multiple wireless access networks (for example, 3G and 4G Wireless Wide Area Networks (WWAN)) and multiple wired line networks (for example , Cable Data Service Interface Specification (DOCSIS) and Subscriber Digital Line Access Multiplexer (DSLAM) wired line networks in accordance with some embodiments.

Figure 9 illustrates a hardware diagram of a device that includes a service processor according to some embodiments.

Figure 10 illustrates another hardware diagram of a device that includes a service processor according to some embodiments.

Figure 11 illustrates another hardware diagram of a device that includes a service processor according to some embodiments.

Figure 12 illustrates another hardware diagram of a device that includes a service processor according to some embodiments.

Figure 13 illustrates another hardware diagram of a device that includes a service processor implemented in external memory of a Chip System (SOC) according to some embodiments.

Figure 14 illustrates another hardware diagram of a device that includes a service processor implemented in external memory of a Chip System (SOC) according to some embodiments.

Figures 15A to 15C illustrate hardware diagrams of a device that includes a service processor and a bus structure extension using intermediate modem or network interconnect device combinations according to various embodiments.

Figure 16 is a functional diagram illustrating a device-based service processor and a service controller in accordance with some embodiments.

Figure 17 is another functional diagram illustrating the device-based service processor and the service controller according to some embodiments.

Figure 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 modems and access network technologies in accordance with some embodiments.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Figure 20 is another functional diagram illustrating the service processor and the service controller according to some embodiments.

Figure 21 is another functional diagram illustrating the service processor and the service controller according to some embodiments.

Figures 22A to 22B provide tables summarizing various service processor agents (and / or components / functions implemented in software and / or hardware) according to some embodiments.

Figure 23 provides a table that summarizes various service controller server elements (and / or components / functions implemented in software and / or hardware) according to some embodiments.

Figure 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.

Figure 25 is a functional diagram illustrating the frame alignment structure of a service processor communication frame and a service controller communication frame according to some embodiments.

Figures 26A to 26H provide tables summarizing various functions of service processor operation indication and parameters according to some embodiments.

Figures 27A to 27P provide tables that summarize various device-based service policy implementation verification techniques in accordance with some embodiments.

Figures 28A to 28E provide tables that summarize various techniques to protect the device-based service policy from compromising in accordance with some embodiments.

Figure 29 is a functional diagram illustrating a device communications stack that allows to implement verifiable traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 30 is another functional diagram illustrating the device communications stack that allows to implement traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 31 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 32 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 33 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 34 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 35 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 36 is another functional diagram illustrating the device communications stack that allows to implement traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments.

Figure 37 is another functional diagram illustrating the device communications stack that allows to implement traffic shaping policy, access control policy and / or monitoring policy of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service according to some realizations.

Figure 39 is another functional diagram illustrating the processing flow of device service processor packets according to some embodiments.

Figure 40 is another functional diagram illustrating the processing flow of device service processor packets according to some embodiments.

Figure 41 provides a table that summarizes various levels of privacy for generating service history information according to some embodiments.

Figures 42A to 42J provide tables that summarize various service policy control commands according to some embodiments.

Figures 43A to 43B are flow charts illustrating a flow chart for a service processor authorization sequence as shown in Figure 43A and a flow chart for a service controller authorization sequence as shown in the Figure 43B according to some embodiments.

Figures 44A to 44B are flow charts illustrating a flow chart for a service processor activation sequence as shown in Figure 44A and a flow chart for a service controller activation sequence as shown in the Figure 44B according to some embodiments.

Figures 45A to 45B are flow charts illustrating a flow chart for a service processor access control sequence as shown in Figure 45A and a flow chart for a service controller access control sequence such as It is shown in Figure 45B according to some embodiments.

Figure 46 is a functional diagram illustrating mobile commerce transactions based on open decentralized devices according to some embodiments.

Figures 47A to 47B are transaction diagrams illustrating mobile commerce transactions based on open decentralized devices according to some embodiments.

Figure 48 illustrates a network architecture that includes a service controller device control system and a service controller analysis and management system according to some embodiments.

Figure 49 illustrates a network architecture for an open developer platform for virtual service provider (VSP) partitioning according to some embodiments.

Figure 50 illustrates a network architecture that includes a service controller billing interface to adapt minimal changes to central billing, AAA and / or other existing network components in accordance with some embodiments.

Figure 51 illustrates a network architecture for locating service controller device control functions with AAA and network service usage functions according to some embodiments.

Figure 52 illustrates a network architecture for locating service controller device control functions in the access transport network according to some embodiments.

Figure 53 illustrates a network architecture for locating service controller device control functions in the radio access network according to some embodiments.

Figure 54 illustrates a network architecture for locating service controller device control functions with AAA and using network service that includes deep packet inspection functions in accordance with some embodiments.

Figure 55 illustrates another network architecture for locating service controller device control functions with AAA and using network service that includes deep packet inspection functions in accordance with some embodiments.

Figure 56 illustrates an activated gateway for 4G / 3G / 2G DPI / DPC according to some embodiments.

Figure 57 illustrates a network architecture that includes the VSP workstation server in communication

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Figure 58 illustrates another gateway activated for 4G / 3G / 2G DPI / DPC according to some embodiments.

Figure 59 illustrates another network architecture that includes the VSP workstation server in communication with the 4G / 3G / 2G DPI / dPc gateways in accordance with some embodiments.

Figure 60 illustrates an activated gateway for 4G / 3G / 2G DPI / DPC and service controller device control system according to some embodiments.

Figure 61 illustrates another network architecture that includes the VSP workstation server in communication with the 4G / 3G / 2G DPI / dPc gateways in accordance with some embodiments.

Figure 62 illustrates another gateway activated for 4G / 3G / 2G DPI / DPC and service controller device control system according to some embodiments.

Figure 63 illustrates another network architecture that includes the VSP workstation server in communication with the 4G / 3G / 2G DPI / DPC gateways in accordance with some embodiments.

Figure 64 illustrates another network architecture that includes a system located in the manufacturing or distribution chain for the device that provides device provisioning or partial provisioning, and any pre-activation required for the device to be activated later in the network according to some embodiments.

Detailed description

The invention can be implemented in various ways, including as a process; an apparatus; a system; a composition of matter; a computer program product made in a computer readable storage medium; and / or a processor, such as a processor configured to execute instructions stored in 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 disclosed process steps can be modified within the scope of the invention. Unless stated otherwise, a component, such as a processor or memory, described as being configured to perform a task can be implemented as a general component that is temporarily configured to perform the task at a given time or a component. specific 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 together with the attached figures illustrating the principles of the invention. The invention is described in relation to such embodiments, although 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 to provide a thorough understanding of the invention. These details are provided for the purpose of example and the invention can be practiced according to the claims without some or all of these specific details. For the purpose of clarity, the 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 digital communications in the mass market and content distribution, the gains in communication network capacity are exceeded by the demand for growing digital network interconnection. For example, some industry experts project the use of average wireless devices of four devices per subscriber, with a mix of general purpose devices such as smartphones and computers along with special purpose devices such as music players, electronic readers, connected cameras (for example, network interconnected) and connected gaming devices. In addition, consumer habits of line user service are tending towards very high bandwidth applications that can quickly consume available capacity and degrade the experience of the global network service if not managed effectively. Because some service provider cost components increase with increasing bandwidth, this trend will also negatively impact the benefits of the service provider.

There is a need for a communication system and method that provide flexible service plans and user network service management to provide consumer choice of more refined service plan offers and effective network capacity management.

Also, it is becoming increasingly important to manage in greater depth the level of services delivered to networked devices to provide cost-effective services that adapt to growing patterns.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

of use of interconnection in digital network. For example, access providers can move away from just billing for basic access and move towards billing for higher-level service delivery with sample services that include Internet access and abundant email, application-based billing, content distribution, activities of entertainment, subscription of information or content or games. In addition, a growing number of new devices in special purpose and general purpose networks are fueling the demand for new service plans, for example, adapted to new device usage models (for example, a special service plan for electronic book reader device).

As network capabilities grow and new network device offerings grow, access network service providers will gain more and more value by opening their networks to enable innovation and expanded offers for network service consumers. However, opening networks to provide effective 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 bidirectional power control systems are new example applications that would require new offers to make them available to network service customers. The need to customize service offers for these new applications requires more efficient methods to define, test and launch new services with more perfected control of service functions and service costs. In some embodiments, this means billing of different types of service items, such as total traffic, content downloads, application usage, information or content subscription services, people or goods tracking services, machine-to-machine information on Real time or electronic commerce transactions.

In some embodiments, network user capacity is increased and user service costs are reduced by managing and billing service consumption in a more refined manner (for example, to meet network neutrality requirements). By managing the service consumption in a user-friendly manner, the overall service capacity required to meet the needs of the user device can be more closely adapted to the needs of a given user thereby reducing user service costs and increasing The benefits of the service provider. For example, managing service usage while maintaining user satisfaction includes implementing service usage policy and policy management to identify, manage and bill for service usage categories, such as total traffic consumption, content downloads, application use, information or content subscription services, e-commerce transactions, people or goods tracking services or machine-to-machine network interconnection services. As described herein, service activity is used to refer to any service use or traffic use that may be associated with, for example, an application; a network communication endpoint, such as an address, uniform resource locator (URL) or other identifier with which the device is communicating; a type of traffic content; a transaction where the content or other material, information or goods are processed, purchased, reserved, requested or exchanged; a download, upload or transfer of file; email, text, SMS, IMS or other messaging or use activity; VOIP services; video services; a device use event that generates a billing event; service use associated with an invoice per account activity (also called billing per account) as described in this document; device location; device service usage patterns, device user interface (UI) discovery patterns, content usage patterns or other device usage characterizations; 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 skilled in the art in view of the embodiments described herein, some embodiments identify various service activities for the purpose of breaking down the use of global service into more precise sub-categories of activities that can be monitored, categorized. , be cataloged, informed, controlled, monetized and used in a verifiable way for end-user notification in a way that results in superior optimization of service capabilities for various levels of service cost or for various types of devices or groups. In some embodiments, it will be apparent to a person skilled in the art that the expressions service activity or service use are associated with categorizing and possibly monitoring or controlling data traffic, application usage, communication with certain network endpoints or transactions, and it will also be evident that in some embodiments the expression service activity is intended to include one or more of the broader aspects listed above. The term abbreviated use of service can be used interchangeably with service activity, but no term is generally intended to exclude some aspect of the other. In some cases, when the terms use of service or service activity are used, more specific descriptors such as traffic usage, application usage, website usage and other examples of service usage are also used to provide more specific examples or focus on a particular element of the terms of greatest coverage.

In some embodiments, employing this level of categorization and service control is achieved in such a way that it satisfies user preferences. In some embodiments, using this level of categorization and service control is achieved in such a way that it also satisfies government rules or regulations regarding open access, for example, network neutrality requirements. In some embodiments, service management solutions are disclosed that also collect and / or inform the behavior of service activity or use of user or device service to determine how to best meet the user's simultaneous wishes of service quality and service costs. inferior service. For example, such monitoring and information generation is achieved

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

in such a way that it includes the approval by the user and in such a way that it also protects the privacy of the user information and service usage behavior or service activity history.

In some embodiments, a system and method for increasing network user capacity for wireless networks is disclosed in view of the increasing demand for service per user by providing a greater number of base stations, also sometimes referred to as access points, terminals base, terminal nodes or other well-known acronyms to be deployed more easily and / or more profitably. For example, to simplify the process of deploying base stations, the complexity of installation and the network infrastructure required for the base station to obtain backlink service to the various networks with which users wish to connect is reduced.

In some embodiments, dense base station deployments are simplified by reducing the requirement to add or concentrate base station traffic through a specific specialized core network infrastructure, so that the base stations connect to the desired user networks to through a more diverse set of local loop, and backbone network and main routing options. This approach also reduces network infrastructure equipment, installation and maintenance costs. In some embodiments, this is achieved by distributing the implementation and control of network traffic policy away from the main network by providing more control for the implementation of service and management policy in the end user device and, in some embodiments, in the device. end-user with respect to certain service policies and the network (for example, control plane servers) with respect to other service policies. For example, this approach makes it easy to connect base stations directly to the local loop Internet with a minimum of specific specialized network interconnection infrastructure.

In some embodiments, the service and transaction billing event capture is distributed to the device. For example, providing capture and recording of service billing and transaction event on the device provides a greater ability to monitor, classify and control deeper aspects of service use or service activity on the device compared to the relatively lower capacity for the same in the network infrastructure (for example, for certain traffic flows, such as encrypted traffic flows). Additionally, billing on the device provides highly specialized service and billing plans for different uses of devices and services or combinations of service activity scenarios without the problem of trying to propagate and manage many different deep packet inspection (DPI) profiles and traffic shaping in the network interconnection equipment infrastructure. For example, service billing on the device can provide more sophisticated, more specialized and more scalable billing and service plans.

Another form of billing that needs improvement is the e-commerce transaction billing with device-assisted central billing. Today, most central billing and content distribution models require or centralized content distribution maintained by the central service provider or central billing authority, or a centralized e-commerce website or traffic aggregation system. portal 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 electronic offer and general trading systems, such as experience websites. Purchase, to accommodate the diverse proprietary custom infrastructure and content storage solutions for e-commerce markets, such as BREW® (Qualcomm® Inc. Binary Wireless Runtime Environment), Symbian OS (from Symbian Software Ltd) and the Apple iPhone 3G App Store app store (from Apple Inc.). This approach requires a great deal of unnecessary development of a custom interface and represses open market creativity for HTTP, WAP or portal-based destinations and shopping experiences. As disclosed below, a superior approach includes device-based transaction billing for an open ecosystem in which a central billing provider provides e-commerce transaction users and providers with a central billing solution and experience that does not require extensive custom development or interconnection of e-commerce infrastructure.

In some embodiments, products are disclosed that incorporate device-assisted service policy implementation, network services and service profiles (for example, a service profile includes a set of one or more service policy settings for the device for a network service), as described below. For example, aspects of the service policy (for example, a set of policies / policy settings for the device for network services, which typically refer to lower-level settings, such as access control settings, security settings traffic control, billing system settings, user notification settings, user privacy settings, user preference settings, authentication settings and admission control settings) that move outside the main network and on the device End-user information includes, for example, certain lower-level service policy implementations, service use or monitoring and generation of service activity information that includes, for example, privacy filtering, monitoring and generation of resource management information. of client that includes, for example, privacy filtering, adaptive service policy control, service network access control, service network authentication services,

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service network admission control services, service billing, transaction billing, simplified service activation and subscription, user service use 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 elements or service policy implementation in the device provide several advantageous solutions for the needs described above. For example, the benefits of certain embodiments include the ability to manage or bill a more abundant and varied set of network services, better global network capacity management, better end user access cost management, simplify user activation or new device service, simplify development and deployment of new devices with new service plans (for example, service profile and billing / cost 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 main network interconnection equipment required to deploy certain access networks.

As discussed below, there are two types of network that are analyzed: 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 network interconnection functions that can be implemented to perform authentication, authorization and access control, and to route traffic to a network that connect 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 device service policies is achieved 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 highly effective means to enable control of third-party services and billing, such as for open operator central 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, various aspects of user privacy and desired network neutrality are provided to enable a user to control certain aspects of service use or generation of device-based service activity information, traffic information generation, policy control of service and generation of customer resource management information (CRM).

In many access networks, such as wireless access networks, bandwidth capacity is a valuable resource in view of the increasing popularity of devices, applications and content types that consume more bandwidth. To maintain reasonable service profit margins, a typical practice of the current service provider is to charge enough per user per access to make service plans beneficial to users of higher bandwidth. However, this is not an optimal situation for users who want to pay less for bandwidth service usage scenarios or lower service activity.

Accordingly, in some embodiments, a range of service plan prices can be made possible that also maintains the service benefit capability for the service provider, for example, by providing a more sophisticated set of service profile management and control capabilities. . For example, this approach generally leads to service management or traffic shaping where certain aspects of a service are controlled based on service policies at lower levels of service quality. In general, there are three problems that arise when these techniques are implemented. The first problem is to maintain user privacy preferences in the generation of service usage information or service activity required to establish, manage or verify the implementation of service policy. This problem is solved in a variety of ways by the embodiments described below with a combination of user notification, preference feedback and approval of the level of traffic information that the user feels comfortable or approves and the ability to filter the use of service or service activity, in some embodiments, specifically use of traffic or CRM reports so that only the level of information that the user prefers to share is communicated. The second problem is to satisfy network neutrality requirements in the way traffic is formed 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 choices about how service use, service activity, traffic use or CRM data is managed up to the costs of control, which includes realizations about user notification and feedback of service policy preference. By allowing the user to decide how much they want to spend and manage their service or resource allocation, a more neutral or completely neutral approach to network use can be maintained by the service provider. The third problem is to help the user to have an acceptable and enjoyable service experience of lower cost plans that will result in a much wider scale adoption of devices.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

connected and applications but that are more restricted in the use of service activity or options or bandwidth or traffic usage. As lower cost service plans are offered, which include plans where the basic connection service can be free, these service plans will require service provider cost controls to maintain the benefit capacity or preserve the network capacity that results in lower limits on the use of service or service activity. These service use limit plans or lower service activity will result in more users likely to exceed service use limits and experience service downtime or additional service cost use unless provided with more suitable means for assistance. on how to use and control the use of lower cost services. This problem is solved in a variety of ways with an abundant collection of user notification, service usage and cost projection, user notification policy feedback, user service policy preference feedback, and adaptive traffic shaping. service policy implementation. As described herein, some embodiments allow a wide range of flexible and verifiable service plans and service profile implementations that vary from examples such as free environment services that may be sponsored by transaction revenue and / or invoice for revenue of service partner sponsored by account, to intermediate price 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 usage limits of service or service activity or no limit at all. Several billing embodiments per account also provide the cataloging of service usage that is not a direct benefit for end users but is necessary for basic maintenance of the device control channels and access network connection, so that the service cost Maintenance traffic can be removed from user billing or billed to non-user accounts used to track or account for such service costs. These and other embodiments result in a service use or service activity control capability that provides more attractive device and service alternatives for end users while maintaining the benefit capacity for service providers and their partners.

In some embodiments, the various embodiments described above for device-based service policy and / or service profile communications control are implemented using network-based service control, for example, to meet various network neutrality requirements and / or privacy, based on indication or indications received from the device (for example, user input provided using the device UI using the service processor) and network-based service control (for example, 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 the device-based network service policy implementation. In some embodiments, the virtual network overlay network interconnection solution is applied to an existing hierarchical network (for example, for wireless services), and in some embodiments, it is applied to simplify or flatten the network architecture as will be described. additionally below. In some embodiments, the vast majority of complex data route network processing required to implement the most abundant service management objectives of existing hierarchical networks (e.g., for wireless services) are moved to the device, leaving less route processing of data required in the edge network and, in some cases, even less in the main network. Since control plane traffic between service control servers and device agents that implement service policies can be of several orders of magnitude slower than data plane traffic, control server network placement service and backlink infrastructure is much less performance sensitive than the data plane network. In some embodiments, as described further below, this architecture may be superimposed on all existing existing access network architectures used today. In some embodiments, this architecture can be used to greatly simplify the routing of main access network and forwarding and management of data plane traffic. For example, in the case of wireless networks, the incorporation of device-assisted service policy implementation architectures may result in the base stations connecting directly to the local Internet loop and data traffic not needing to concentrate on a network Main specialized. This results in, for example, a large reduction in the cost of backlink, main network cost and maintenance cost. These cost savings can be redeployed to buy and install more base stations with smaller cells, which results in superior data capacity for the access network that leads to better user experience, more useful applications and lower service costs. This flat network interconnection architecture also results in latency reduction since fewer routers are needed to move traffic over the Internet. In some embodiments, the present invention provides the necessary teaching to enable this powerful transformation from centralized network service architectures to more distributed device-based service architectures.

Device-based billing can be compromised, hacked and / or falsified in many different ways. Simply determining that the billing reports are being received from the device, that the device agent software is present and configured properly (for example, the billing agent is present and configured properly) is insufficient and easily falsifiable (for example, falsifying the same agent, providing counterfeit billing reports using a counterfeit billing agent or providing counterfeit agent configurations). Therefore, in some embodiments,

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

provides device-assisted and / or network-based service policy implementation verifiable. For example, billing for service use and / or verifiable service use may be provided as described herein with respect to various embodiments.

Although most of the analysis below and the embodiments described below focus on paid service networks, those skilled in the art will appreciate that many of the embodiments also apply to other networks, such as business networks. For example, the same device-assisted network services that create access control services, environment activation services and other service profiles can be used by corporate IT managers to create a cost-controlled service policy network for mobile devices corporate As another example, the embodiments described below to provide end-user service control may also allow a service provider to offer parental controls by providing parents access to a website with a web page that controls policy settings for the interconnection service in access control network for a child's device.

Network architecture for assisted / device-based service control

Figure 1 illustrates a simplified network architecture (eg, "flat") according to some embodiments. As shown, this provides a simplified service infrastructure that exemplifies a simplified and "flat" 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 the network infrastructure. For example, in contrast to a complex edge and core network infrastructure that connects base stations to the central service provider network, as shown the base stations 125 are connected directly to the Internet 120 by means of firewalls 124 (in some embodiments, base stations 125 include firewall functionality 124). Therefore, in some embodiments, a central provider network is no longer required to route, forward, inspect or manipulate data plane traffic, since the implementation of data plane traffic policy is performed on the device 100 by the service processor 115. However, it is still an option, in some embodiments, to provide data plane traffic from the base stations 125 to a central provider network using either open or secure Internet routing if desired. Communication of the base station control plane for the AAA (Authentication, Authorization and Accounting) access network 121 server, DNS / DHCP server (Domain Name System / Dynamic Host Configuration Protocol) 126, wireless center mobile 132 (sometimes referred to in part as a home location register (HLR) or other acronym) or other necessary functions are achieved, for example, with a secure IP tunnel or TCP connection between the central provider network and the stations base. The base station 125 is used to refer to embodiments of multiple base stations where the base station itself is directly connected to the RAN, or where the base station is connected to a base station controller or base station aggregator function that a in turn, it is connected to the RAN, and all such configurations are collectively referred to herein as the base station 125 in Figure 1 and most of the figures that follow that reference base station 125 as described below.

As shown, the central provider access network is suitable for both 3G and 4G, the devices 100 can be any of 3G, 4G or 3G and 4G in multiple ways. Those skilled in the art will also appreciate that in the most general case, the network could be suitable for 2G, 3G and 4G, or the device could be suitable for 2G, 3G and 4G with all or a subset of the Global Mobile System (GSM) ), General Radio Packet Service (GPRS), 1X Multiple Code Division Access (cDmA), High Speed Packet Access (HSPA), Optimized Evolution Data (EVDO), Long Term Evolution (LTE) and capacity WiMax modem. If the devices are in simple mode, then the 3G 100 devices will be activated with a service profile applied to the service processor 115 that is consistent with the 3G network capacity and speed, and the 4G devices will be activated with profiles of service applied to service processor 115 that are consistent with the network capacity and 4G speed. In both cases, the same service controller 122 manages services for both sets of devices according to some embodiments. If the devices are multiple modes, then the service processor 115 can be activated with a dual mode service profile capability in which the service profile for 3G offers a similar abundant set of services than the service profile for 4G but , for example, with reduced bandwidth. For example, this approach allows central providers to offer a more abundant set of service offers with 3G and then migrate the same set of service offers to 4G but with higher performance. In particular, this approach allows the abundant service migration from 3G to 4G to take place, for example, 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 settings Lower bandwidth service profile.

In some embodiments, if the devices are multiple mode, a network selection policy implementation performed on service controller 122 is provided based on service availability reports received from service processor 115. The network selection policy allows for network selection that corresponds to the most desirable service profile to meet user service preferences. For example, if the user specifies, in the embodiments of the service notification structure and user preference feedback described below, that the maximum performance is the most important factor when

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

select which access network to connect to, then the best profile is likely to be the 4G network since 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 charged than the 3G network. On the other hand, if the user's preference setting specifies cost as the most important factor, then depending on the service costs of the central provider the 3G network may become the most desirable service profile. This is a simple example and many other selection criteria are possible in performing network selection as discussed further below.

Network-based service usage monitoring for verification and other purposes

In some embodiments, if the data base traffic of the base station is transmitted over the Internet 120 as discussed above, then the IPDRs (Internet Protocol Detail Records, also occasionally and interchangeably referred to herein) as Collection Data Records or CDRs, which as used herein refer to any measure of service use network or service activity for voice and / or data traffic (for example, IPDRs may include an indication of time, a device ID and various levels of service usage network measures for the device associated with that device ID, such as perhaps the use of total traffic, 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, IPDRs may be generated by one or more of the following: base station 125, RAN or transport gateways and AAA 121. In some embodiments of Access network, IPDRs are transmitted to computer functions that add IPDRs for the purpose of service billing and other functions. Aggregation can take place at AAA, transport gateways or other functions that include billing system 123. As discussed below, it is often the case that IPDRs are supposed to be obtained from the AAA server 121 and / or a service usage data store 118 (for example, a real-time service usage collection stored in a database or a delayed data source service usage collection stored in a database ), or some other network function. However, this does not imply that IPDRs cannot be obtained from a variety of other network functions, and in some embodiments, IPDRs are obtained from other network functions as disclosed herein. In some embodiments, existing IPDR sources are used to obtain network-based service usage measures for multiple purposes that include, but are not limited to, service verification of policy or profile implementation, trigger verification error response actions. service and service notification synchronization. Certain types of IPDR can be based on, or based in part on, what is often referred to as CDR (Collection Data Records, which can track voice and data usage charges) or CDR modifications. Although the ability to monitor, categorize, catalog, inform and control the use of service or service activity is generally higher in the device than it is in the network, and, as described herein, service monitoring o Device-based control assistance is desirable in some way compared to network-based implementations, as described herein many embodiments take advantage of network-based service monitoring or control to increase service or control monitoring. assisted by device and vice versa. For example, even though many embodiments work well with minimal IPDR service usage information or service activity that is already available on a network, deeper levels of IPDR packet inspection information in general allow for deeper levels of monitoring. of service or service control verification, which may be desirable in some embodiments. As another example, deeper levels of network capacity to control service usage or service activity can provide more sophisticated error handling in some embodiments, for example, by providing more options for the Switching Port Analyzer (SPAN) and network quarantine as described in this document. As another example, in some embodiments it is advantageous to take advantage of network based service monitoring or control for these service aspects that the network can support, while using device-assisted service monitoring or control for the service aspects implemented. advantageously in the device.

In some embodiments, when the data base traffic of the base station has a backlink and is concentrated in a core provider network 110, then the IPDRs may originate at the base stations or at a router or gateway in the network. central provider 110, and IPDRs are collected on AAA server 121 and stored in service usage data store 118. In some embodiments, central billing system 123 collects IPDRs from AAA server 121 for purposes Billing service accounting. In some embodiments, a central billing system 123 collects IPDRs directly from the initial IPDR source or some other aggregator. In some embodiments, external partners such as MVNOs gain access to IPDRs from central billing system 123. As discussed below, IPDRs are assumed to be obtained from AAA server 121, and it is understood that the source of IPDRs are interchangeable in embodiments.

In some embodiments, IPDR information is used by service processor 115, service controller 122 and / or another network device or device device is provided to implement service control verification as described below. In some embodiments, an IPDR data source (for example, also referred to as collection data collection (CDR) flows between network elements. For example, an IPDR data source can flow from the gateway of RAN 410 (for example, SGSN 410, control of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

packages of BSC 510 or RNC 512) and the transport gateway 420 (for example, GGSN or PDSN). In other embodiments, IPDRs originate and flow from base station 125 or some other component / element in the network. In some embodiments, one or more of these IPDR data sources is transmitted to an IPDR aggregation function (for example, also referred to as a collection gateway). For example, this aggregation function can be located in AAA 121, in mobile wireless center 132 (and / or in the home location register (HLR) or other similar function called by other common industrial names), in the transport gateway 420, or some other network element. This aggregation function collects IPDR data sources in a database with an entry for each device 100. In some embodiments, an intermediate aggregation function is provided that feeds a higher level aggregation function, for example, the gateway Transport 420 may receive IPDR data sources from the RAN 410 gateway or base station 125 before sending them to another aggregation function. At some point in time (for example, 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 IPDR information 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 purposes of the IPDR information described herein, the IPDR feed for the service controller 122 is it derives from the added power, the billing system 123 having to transmit it to the service controller 122, or copying it from the IPDR aggregation function.

In some embodiments, the IPDR data source is obtained from the network function that is generating or adding the IPDR data source as described herein. In some embodiments, the IPDR data source is copied from the aggregation function so that it does not interrupt the operation of the network. For example, a switch-based port analysis function can be used to copy traffic to a traffic or server analysis element that filters IPDR traffic and records it to a database that is then sent to the service controller. 122 (or any other network element that uses IPDR information as described herein), or is consulted by service controller 122 (or any other function that uses IPDR information as described herein) . In some embodiments, if aggregate IPDR information transmitted to the billing system is delayed from real-time traffic use events in an amount of time, that is, for example, too long for the desired operation, or for any other reason which makes it less desirable to obtain IPDR information from the same aggregate data source used for billing system 123, IPDR information may be collected from one or more of the sources discussed below that include, for example, from another aggregation point (for example, the data source to the collection 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 base station 125 and / or other network element. In some embodiments, the IPDR data sources from these or other network functions are copied to a database as described above, which are sent or consulted to obtain the information to the service controller 122 or other network elements that request IPDR information.

In some embodiments, service processor 115 includes various components, such as device agents, that perform service policy implementation or management functions. In some embodiments, these functions include verification of service or implementation policy, prevention of service policy manipulation, concession or denial of service, application access control, traffic control, network access control services, various services network authentication, service control plane communication, device operation indication services, service billing, transaction billing, simplified activation services and / or other service implementations or service policy implementations. It will be apparent to those skilled in the art that the division in functionality between one device agent and another is a design choice, that functional lines can be rewritten in any technically feasible way that product designers see fit, and that the Placement divisions in functional nomenclature and analysis for device agents helps understanding, although in more complex embodiments, for example, it may make sense for the product designer to reveal the device agent's functionality specifications in some other way to manage the development specification and test complexity and workflow.

In some embodiments, network control of the service policy settings and services as discussed above are achieved with service controller 122 which in various embodiments includes one or more server functions. As with the agent nomenclature and functional analysis of the service processor 115, it is understood that the server nomenclature and functional analysis of the service controller 122 is also a design choice and is primarily provided to aid in the analysis. It will be apparent to those skilled in the art that server names and functional branches do not imply that each name is an individual server, and, for example, a single function named in the various embodiments may be implemented in multiple servers, or multiple functions named in The various embodiments can be implemented on a single server.

As shown, there are multiple open content transaction partner sites 134 (for example, open content transaction servers), which represent the websites or experience portals offered by content partners or e-commerce transaction partners of the provider of service. For example, the servers of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

transaction 134 can provide an electronic commerce transaction and offer platform to the device. In some embodiments, 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 using the service controller 122 for managing the device services by means of service processor 115 is not always the same as the central provider that provides the services of the access network.

In some embodiments, additional distribution of central provider access network interconnection functions such as AAA access network server 121, DNS / DHCP server 126 is provided, and other functions are provided at base stations 125. In In some embodiments, network-based device service suspension / resume control is also provided at base stations 125 (or in some embodiments, for hierarchical or overlay networks, this function is provided by one or more of the following: gateways of RAN, transport gateways, AAA 121 or some other network function). As shown, the following are connected (for example, in network communication with) the central provider network 110: central provider billing system 123, specialized leased lines 128 (for example, for other services / providers), controller of central provider service 122, a content management system 130 (e.g., content switching, content billing and content capture), central provider DNS / DHCP server 126, access network AAA server 121, store of service usage data 118 and mobile wireless center provider center 132. These embodiments may be particularly advantageous for flat networks such as those shown in Figure 1 that are provided by the present invention.

In some embodiments, base stations 125 implement a firewall function by means of firewall 124 and are placed directly on the local loop Internet for the backlink. Voice traffic transport is provided with a secure protocol with Voice over IP (VOIP) frame alignment that runs 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 application level security layer in the VOIP trunk traffic added before it is placed in 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 that run over the Transmission Control Protocol (TCP), Internet Protocol (IP) or Datagram Protocol. User (UDP), although TCP provides a more reliable delivery channel for control traffic that is not sensitive to delay or interference. An exemplary embodiment for the control channel is a buffer storage of control link, frame alignment, 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 function indication function is provided to base stations 125 similar to that implemented between service controller 122 and service processor 115 as described below. If the need to maintain an effective bandwidth 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 the device access network connection, then there are many other approaches to implementing a secure control channel over the Internet that include, for example, one or more of several packet encryption protocols that run at or just below the application layer, which execute Layer Security. Transport (TLS) of TCP, and running IP level security or secure tunnels.

In some embodiments, the device-based service control plane traffic channel between service processor 115 and service controller 122 is implemented on 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-based service control plane channel for communications from service processor 115 to service controller 122 is established over the Internet 120 or through the access network using service protocols IP since this is the most general case and applies to overlay network applications for various embodiments as well as applications where various embodiments are used to enable flat access networks.

In some embodiments, enabling the device to verifiably implement an abundant set of service features as described herein, and enabling the base station 125 to connect directly to the Internet 120 with a local firewall for device data traffic, Tunnel the voice to a voice network with VOIP and secure Internet protocols, and control the base station 125 through a secure control plane channel using base station control servers located in a central provider network, the stations base 125 can be provisioned and installed more efficiently, since, for example, base station 125 can adapt a greater variety of local loop backlink options. In such embodiments, it is advantageous to perform certain basic network functions at the base station 125 instead of the central provider network.

In some embodiments, a basic device suspension / resume function is provided to allow or deny Internet access of the device by base stations 125 (or in some embodiments, for hierarchical or overlay networks this function is provided in some embodiments by one or more of the following: RAN gateways, transport gateways, AAA 121 or some other network function). This functionality, as discussed below, is important for certain embodiments that involve taking actions to

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Resolve, for example, service policy verification errors. In some embodiments, this function is performed at the base station (for example, base stations 125) thereby eliminating the need for a more complex network interconnection equipment hierarchy and traffic concentration required to perform the suspension / deepest resumption in the network. Access network base stations control access to the medium and therefore are designed with knowledge of what device identification number originates from and ends in a given traffic packet, packet group, packet flow, connection Voice or other traffic flow. In some embodiments, the suspend / resume function is implemented in the base station 125 by placing an access control function in the traffic route of each device traffic flow. The suspend / resume function can be used by various network elements, and in the context of the present embodiment it can be used by the service controller 122 (for example, in some embodiments, the access control integrity server 1654 (Figure 16 ) of service controller 122 or other service controller elements) for suspending and resuming device service based on the determination of the verification status of service policy implementation as described below.

In some embodiments, at least one traffic monitoring or basic service monitoring function is performed at the base station (e.g., base stations 125) similar to service history records or IPDRs collected more deeply in the network at more conventional hierarchical access network infrastructure architectures. For example, 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 device-based services. superiors as discussed below. In some embodiments, a traffic monitoring function is provided at the base station 125 in which the traffic for each device is counted for at least total traffic use and recorded. In some embodiments, traffic inspection is provided beyond simply counting the total traffic usage. For example, the base station traffic monitor can register 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 registers. 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 use is outside the policy or profile limits or concessions are routed to a quarantined network instead of or as an initial alternative to a service. suspended 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 instead of simply suspending device traffic completely from the network as described above, the base station 125 includes a firewall function (for example, the firewall 124) that can pass device access traffic with quarantine network destinations and block device access to all other destinations. In some embodiments, when it is described that the conditions of service verification indicate that the use of service is outside the policy or profile limits or concessions, then one or more of the following actions are taken: the user is notified of the additional use condition, the user is required to acknowledge the additional use condition, the user's account is billed for the additional use condition, and the device is labeled for additional analysis by a device analysis function network or a network manager.

In some embodiments, network complexity is reduced by using the device without completely moving to a flat base station network as described above. The device participation in the implementation of main network services provides numerous measures to simplify or improve the network architecture, functionality or performance. For example, two approaches are discussed below that vary from a simple overlay of the service processor 115 on devices and the service controller 122 in a conventional hierarchical access network as illustrated in Figures 4 to 7, to a completely flat network as illustrated in Figures 1 to 3 and 8. Those skilled in the art will appreciate that the disclosed embodiments provided herein may be combined with the above embodiments and other embodiments involving flat network base stations to provide several advantages that include, for example, more abundant service capacity, less access network complexity, lower access network costs, more flexible base station deployments, or provisioning and less complex or less expensive base station backlink service costs.

In most of the analysis that follows, the network-based service history records and the network-based suspension-resume functionality used in certain embodiments that involve service implementation verification are assumed to be obtained from the central provider network element. of device service history 1618 (as shown in Figure 16) and the central server provider network element of AAA 121, and in some embodiments, operated in conjunction with other core provider network elements. It is understood that these functions provided by the network can be reorganized to be provided by other network interconnection equipment, which includes the base station as discussed above. It is also understood that the monitoring, recording and generation of network based device traffic information to the device service history element 1618 can be achieved at the base stations. Additionally, it is understood that while the AAA 121 server is supposed to provide the functionality of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

suspend / resume, quarantine network routing or limited network access requested in some embodiments, AAA server 121 may be a management device in which the actual implementation of traffic suspension / resume mechanisms, firewalls can be implemented , routing, redirection forwarding or traffic limitation analyzed in certain embodiments at the base stations as discussed above or in another network element.

In some embodiments, an activation server 160 (or other activation sequence generation apparatus) provides provisioning, as described below, of the devices 100 and / or network elements in the central provider network so that, by For example, device credentials can be recognized for activation and / or service over the network. In some embodiments, 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 partner with a service plan. As shown in Figure 1, the activation server 160 is connected to the main central provider network 110. In this configuration, the activation server 160 acts, over the network or wirelessly, as the activation function. In some embodiments, the activation server 160, or variations of the activation server 160 as described below, is connected to the apparatus in the manufacturing or distribution channel, or via the Internet 120, or as part of the service controller 122 for service provisioning or activation functions. In some embodiments, the activation server 160 is connected to the main central provider network 110. In some embodiments, the activation server 160 is connected to other network extensions such as an MVNO network or Internet 120 if, for example, routers on service gateways or base stations have the ability to direct traffic from devices that are not fully activated or provisioned to an Internet destination, or if service processor 115 is used for that address. In some embodiments, activation server 160 is included in service controller 122.

Figure 2 illustrates another simplified network architecture (eg, "flat") that includes an MVNO (Mobile Virtual Network Operator) relationship according to some embodiments. As shown, an open MVNO configuration is provided in a simplified network as described similarly above with respect to Figure 1. In some embodiments, the service provider (eg, service owner) is defined by the entity that maintains and / or manages the service controller 122 associated with and controls the service processors 115 that are within the devices 100 that use the service. In some embodiments, the service controller 122 requires only a secure control plane communication link of relatively low data rate not in real time to the service processors 115. Accordingly, in some embodiments, the servers of the service controller 122 may reside on any network that can connect (for example, be in network communication with) Internet 120. For example, this approach provides more efficient provisioning of the equipment used to establish an MVNO partnership between the central provider and the network provider. service, and as shown in Figure 2, an MVNO network 210 is in network communication with Internet 120 just as the central provider network 110 is in network communication with Internet 120. As shown, the following are connected to (for example, in network communication with) the main MVNO 210 network: MVNO 123 billing system, MVNO service controller 122, MVNO 130 content management system, MVNO 126 DNS / DHCP server, MVNO 121 AAA server and MVNO 132 mobile wireless center.

Showing two service controllers 122, one connected to (for example, in network communication with) the MVNO network 210 and one connected to the central provider network 110, Figure 2 also illustrates that some embodiments allow two entities in the same access network that each uses service controller 122 and service processor 115 to control different devices and offer different or similar services. As described below, the only secure communication link pairing that exists between the two ends of the service control link, 1691 and 1638 (as shown in Figure 16), ensures that the two service controllers 122 can only control the devices associated with the correct service provider service profiles.

Figure 3 illustrates another simplified network architecture (eg, "flat") that includes two core providers according to some embodiments. For example, it provides roaming agreements while maintaining abundant services across different networks with completely different access layers. As shown, mobile devices 100 are supposed 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. An example roaming condition would be that both Central Provider No. 1 and Central Provider No. 2 provide 3G and 4G network resources. In this example, mobile devices 100 can connect to both 3G and 4G 125 base stations owned and operated by the central provider with which they have registered for service, or when none is available from the central provider the user who Registered with the device can perform roaming on the other central provider access network and still potentially offer the same abundant service set using the same service profiles provided, for example, roaming service costs are reasonable. In some embodiments, if roaming service costs are significantly more expensive than home network service costs, then service processor 115 is configured with a roaming service profile that reduces or adapts the use of service or activity of service through a

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

combination of one or more user notification, user preference feedback regarding traffic shaping or service policy management preference collected and approved by service processor 115, adaptive policy control in service processor 115 which it tracks increasing roaming service costs and re-scales the service, or recognition of the change in the network that causes service controller 122 to configure service processor 115 of device 100 with a roaming service profile. In some embodiments, in roaming situations, the network selection may be based on an automatic network selection by determining the network selection, for example, by a combination of user service profile preferences, service provider roaming offers and / o network capabilities and roaming cost available, as discussed further below.

In some embodiments, the devices 100 are again assumed to be multi-mode 3G and 4G devices (for example, mobile devices 100 are supposed to have a dual mode wireless modem that will operate on both a 4G network, for example LTE, such as a 3G network, for example HSPA or EVDO), with devices 100 that are billed for service by Central Provider No. 1 which is, for example, suitable for EVDO and LTE, and devices 100 that are Billed for service by Central Provider No. 2 which are, for example, suitable for HSPA and LTE. For example, the devices 100 may perform roaming using the LTE 4G network of the central roaming provider when neither the 3G nor the 4G network with the home central provider is available. As similarly discussed above with respect to the roaming embodiments described above, service processors 115 and service controllers 122 can provide similar services in the 4G roaming network and the 3G home network than in the home network. of 4G, however, variable costs and available network capacity and speed differences of domestic 3G, roaming 4G and domestic 4G can also encourage the use of different service profiles, such as three different ones, to allow more selection efficient and cost-effective and control services based on the current network.

Figure 4 illustrates a network architecture that includes an overlay configuration of Universal Mobile Telecommunications System (UMTS) in accordance with some embodiments. As shown, Figure 4 includes a 4G / 3G / 2G HSPA / Transport access network operated by a central provider and two MVNO 210 networks operated by two MVNO partners. In some embodiments, the central provider may offer enhanced service capabilities using a conventional UMTS network. As shown, the base stations 125 do not connect directly to the Internet 120, and instead the base stations 125 connect to the conventional UMTS network. However, as in various previous embodiments, the service processor 115 still connects through the secure control plane link to the service controller 122. In some embodiments, the data plane traffic has a backlink link through the various UMTS network routers and gateways since it is the control plane traffic, and IPDRs are obtained from the access network AAA server 121. Referring now to the 4G / 3G / HSPA / Transport access network / 2G as shown in Figure 4, the base stations / nodes of HSPA / GPRS and LTE / HSPA 125 are in communication with group 410 of GPRS Support Nodes (SGSN) of Service / Servers of 4G / 3G / 2G via a radio access network 405, which is in communication with the group 420 of GPRS Support Nodes (SGSN) of 4G / 3G / 2G Gateway via a 415 wireless access network (eg, a GPRS-IP network ), which are then in communication with the main network of pr central shepherd 110.

As shown in Figure 4, as discussed elsewhere, the service usage data store 118 is a functional descriptor for a network level service usage information collection and generation function located at one or more of the network interconnection equipment boxes fixed to one or more of the sub-networks in the Figure (for example, RAN, transport and / or main networks). As shown in Figure 4, the use of service 118 is shown as an isolated function connected to the main central provider network 110 and the intention of this representation is to facilitate all possible embodiments to locate the service use function 118. In some UMTS network embodiments, the service usage function 118 is located or partially located on the gateway (or group of gateways) of GGSN 420. In some embodiments, the service usage functionality 118 is located or partially located at the SGSN gateway (or group of gateways) 410. In some embodiments, the service usage functionality 118 is located or partially located in the group of equipment that includes the AAA 121 and / or the mobile wireless center 132. In some embodiments , service use functionality 118 is located or partially located at the base station, base station controller and / or base station aggregator , collectively referred to as the base station 125 in Figure 4 and in many other figures described herein. In some embodiments, the service usage functionality 118 is located or partially located in a read component in the transport network 415, a read component in the main network 110, the billing system 123 and / or in another component or network function This analysis of the possible locations for the function of recording and generating information of network-based service usage history can easily be generalized to all other figures described herein by a person skilled in the art (e.g., gateway of RAN 410 and / or transport gateway 420), and this background will be assumed even if it has not been established throughout the previous analysis and then.

In some embodiments, a central provider provides open development services to MVNO partners, Master Value Added Reseller (MVAR) and / or Original Equipment Manufacturer (OEM). In some embodiments, the three service providers, the central provider service provider, MVNO service provider No.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

1 and MVNO service provider No. 2 have service control and billing control of their own respective devices 100 through the unique pairing of service processor 115 and service controllers 122. For example, MVNO # 1 and MVNO No. 2 may each have open development billing agreements with the central provider and each may have ownership of their respective billing systems 123. As shown in Figure 4, the main network of mVnO N .1 210 is in communication with the main network of central provider 110 via Internet 12o, and the main network of MVNO # 2 210 is in communication with the main network of central provider 110 via an alternative landline connection (LL ) / VPN 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 offers. In addition, the central billing system 123 allows the three service provider user populations to access e-commerce experiences from transaction provider partners operating transaction servers 134, to choose central provider billing options that combine their invoices of third party transaction on your service provider invoice, and each subscriber population may experience a specified look and feel of service provider that are unique to the respective service provider even if different user populations are interconnecting with the same servers Transaction partners and transaction partners do not need to require significant custom development to provide the only central billing and unique appearance and consistent user experience.

In some embodiments, a central provider offers open network device and service developer services using a service controller server 122 (e.g., a service controller server farm) and allows open development partners to lease time. Server and server tools to create your own service profiles. The central provider also provides service billing on behalf of the services for open development partners. For example, this reduces costs associated with establishing an MVNO network for open development partners and does not require partners to provide significant control or flexibility in device and / or service control.

Figure 5 illustrates a network architecture that includes an Optimized Evolution Data (EVDO) overlay configuration according to some embodiments. This figure is similar to Figure 4 except for the various particular variations of the EVDO network architecture compared to the HSPA / GPRS wireless access network architecture as will be apparent to one skilled in the art. As shown, Figure 5 includes an EVDO access network operated by a central provider and two MVNO 210 networks operated by two MVNO partners. The EVDO access network includes the LTE / EVDO and EVDO / lxRTT 125 base stations in communication with the Base Station Controller (BSC) 508 packet control and the radio network controller 512 via a radio access network (RAN) 505, which is in communication with the data packet service node 520 via a wireless access network 515, which is in communication with the main central provider network 110. As shown, a RAN AAA server 521 is also in communication with the access transport network 515.

In some embodiments, the central provider may offer enhanced service capabilities using a wireless access network. As shown, the base stations 125 do not connect directly to the Internet 120, and instead the base stations 125 connect to the wireless access network. However, as in various previous embodiments, the service processor 115 still connects via the secure control plane link to the service controller 122. In some embodiments, the data plane traffic has a backlink as shown through of the various routers and network gateways as control plane traffic does, and IPDRs are obtained from the access network AAA server 121.

Figure 6 illustrates a network architecture that includes a Wi-Fi 4G LTE overlay configuration according to some embodiments. This figure is also similar to Figure 4 except for the various particular variations of the 4G LTE / Wi-Fi network architecture compared to the HSPA / GPRS wireless access network architecture as will be apparent to one skilled in the art. As shown, Figure 6 includes a 4G LTE and Wi-Fi access network operated by a central provider and two MVNO 210 networks operated by two MVNO partners. The 4G LTE / Wi-Fi access network as shown includes the LTE and HSPA / EVDO 125 eNodeB base stations in communication with the Base Station Controller (BSC) packet control (EVDO and lxRTT) 608 and SGSN ( HSPA and GPRS) 612 via a radio access network (RAN) 605, which is in communication with the Gateway (GW) 620 of System Architecture Evolution (SAE) via a wireless access network 615, which is then in communication with the central provider network (main). As shown, a Mobile Management Entity (MME) 619 server is also in communication with the access transport network 615. Also as shown, a Wi-Fi Access Point (AP) 602 is also in communication with the 615 access transport network using the Wi-Fi Access Client Installations Team (CPE) 604. As will be apparent to those skilled in the art, the network architectures shown, for example, in Figures 1-8 they are exemplary network architecture embodiments in which one or more of the network elements shown may not be required or included, alternative network elements included and / or additional network elements based on the network design choices, network standards and / or other functional / design considerations and choices.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, the central provider may offer enhanced service capabilities using the wireless access network as depicted in Figure 6. As shown, base stations 125 do not connect directly to Internet 120, and instead base stations 125 connect to the wireless access network. However, as in various previous embodiments, the service processor 115 still connects via the secure control plane link to the service controller 122. In some embodiments, the data plane traffic has a backlink as shown through of the various routers and network gateways as control plane traffic has, and IPDRs are obtained from the access network AAA server 121. Accordingly, as shown in Figures 4 to 6, various can be implemented Embodiments regardless of wireless access network technology, and for example, can be implemented in 3G, 4G and any other wireless access network technology.

Figure 7 illustrates a network architecture that includes a WiMax and Wi-Fi overlay configuration according to some embodiments. This figure is also similar to Figure 4 except for the various particular variations of a combined WiMax / Wi-Fi network compared to the HSPA / GPRS wireless access network architecture as will be apparent to one skilled in the art. As shown, Figure 7 includes both a WiMax and Wi-Fi network (for example, a combined WiMax / Wi-Fi network) operated by a central provider and two MVNO 210 networks operated by two MVNO partners. Although Wi-Fi and WiMax access technologies are different wireless access network interconnection technologies, providing WiMax a wide area network interconnection technology and providing Wi-Fi a local area network interconnection technology, which operates effectively using the two wireless access network interconnection capabilities. As similarly discussed above with respect to switching between 3G and 4G networks, some embodiments employ 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 the free Wi-Fi services have adequate coverage, in most cases, the decision criteria programmed in the automatic network selection algorithm will select Wi-Fi whenever the Wi-Fi access points are associated With a known and reliable supplier. In some embodiments, the transaction billing from the central vendor billing system 123 or the billing systems of the MVNO # 1 or MVNO # 2 123 will work with the transaction servers when connected via Wi-Fi Just like when they connect through any other access technology (including wireless connections). The WiMax / Wi-Fi access network as shown includes the WiMax 125 base stations, Wi-Fi 702 hot spots / access points and / or 702 Wi-Fi mesh access networks (in some embodiments, they can be used femto cells in addition to and / or as an alternative to Wi-Fi), and the Wi-Fi access client facilities (CPE) 704 team in communication with the WiMax 708 service controller and the Wi-Fi service controller Fi 712 via a radio access network 705, which is in communication with the main gateway of WiMax 720 via a wireless access network 715, which is then in communication with the central provider network (core) 110.

In some embodiments, the central provider may offer enhanced service capabilities using the wireless access network as depicted in Figure 7. As shown, base stations 125 do not connect directly to Internet 120, and instead base stations 125 connect to the wireless access network. However, as in various previous embodiments, the service processor 115 still connects via the secure control plane link to the service controller 122. In some embodiments, the data plane traffic has a backlink as shown through of the various routers and network gateways such as control plane traffic, and IPDRs are obtained from the access network AAA server 121.

Referring to Figure 7, the Wi-Fi connection can be replaced by a cell femto (and the Wi-Fi modem shown in Figures 15B (3) and 15B (4) can be replaced by a cell femto modem (functionality from the base station side)). In some embodiments, service processor 115 is provided in the femto cell to control subscriber access in a verifiable manner as similarly described herein with respect to various embodiments (eg, Wi-related embodiments). Fi). For example, the service provider of the cell femto (for example, the entity that owns the spectrum that the cell femto is using) can operate the cell femto as a local access mechanism for the domestic subscriber (or other who bought or installed the femto cell), and then also use it to provide additional pay-per-service or free services, with controlled access and / or traffic control and / or service control and / or billing control performed locally or in combination with equipment network as described in this document. In some embodiments, WWAN devices that are used at home or work with the cell femto include a portion of the service processor functionality. For example, this allows the service provider for the femto cells to provide service and monetize service in a controlled manner even if the femto cell is not connected to the service provider network in the conventional manner that the base stations are connected to the service provider network, but be connected via Internet 120. For example, the safe operation indication function can be extended to include data traffic so that it is encrypted and secured along with the control plane traffic. The decision whether or not to admit a device in the femto cell can be made through the connection of the service processor 115 to the service controller 122 and the subsequent search of the credentials for the device and the associated service plan and service profile which is then programmed into the service processor in the femto cell and / or the same device. The femto cell can also offer a landing page to devices through the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service processor so that non-network devices can gain access to the network by registering through the femto cell. For example, embodiments of the Wi-Fi intermediate device at one end and WWAN at the other can be achieved by using the Wi-Fi connection on the cell phone in AP mode so that the intermediate device is made. The service processor 115 in the cell phone can then act in the same manner as described for the intermediate device as described herein.

Figure 8 illustrates another simplified network architecture (eg, "flat") that includes multiple wireless access networks (for example, 3G and 4G Wireless Wide Area Networks (WWAN)) and multiple wired networks (for example, networks Wired Data Over Cable Service Interface Specification (DOCSIS) and Subscriber Digital Line Access Multiplexer (DSLAM) according to some embodiments. It is a common network architecture for central multi-access providers to have one or more wired access networks and one or more wireless access networks. As shown, Figure 8 includes both 3G and 4G wireless access networks, which include a 4G 125 base station and a 3G 125 base station, and both DOCSIS and DSLAM wired networks (for example, a WWAN network / combined wired line), which includes the header end of DOCSIS 125 and DSLAM 125, operated by a central provider via a central (main) provider network 110 and an MVNO partner via the MVNO network 210 via Internet 120.

As shown, the service processor 115 may reside in a number of different types of devices 100 operating in 3G or 4G wireless, DSL or DOCSIS, and the service controller 122 can control each of these types of devices with experience coherent service, 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 the service controller 122 is managing service profile policies for a service processor 115 that resides in a DOCSIS 100 device (for example, a computer or laptop connected to a cable modem), but not when the same service controller 122 is managing service profile policies for a service processor 115 that resides in a 3G 100 device (for example, a smartphone connected to a network 3G mobile).

As will be apparent to one skilled in the art in view of the above description of Figures 1 to 8, the present invention can be provided through any access network and a set of service profiles can be defined in a variety of ways that include , for example, using preferred feedback, realization of access network, cost of access network, status of central provider network of access network with the central provider of service provider and roaming offers and costs. For example, as discussed below, various embodiments allow users to have superior service experiences based on the ability to control certain of their service settings, and service providers can also more effectively deploy a greater diversity of services / plans. of service to users.

In some embodiments, service processor 115 and service controller 122 provide an overlay for existing networks without significantly changing billing system 123, gateways / routers or other network components / elements, and can also provide verifiable service monitoring for control services and / or use of service / costs without involving, for example, a service provider or MVNO (for example, for smart phone and / or portable or portable devices (or any other accessible network device) with a plan for unlimited data or any other service plan). For example, applications that are deployed by device owners or service subscribers (for example, an IT manager) and do not imply that a service provider includes roaming services provided as an after-sales product without involvement of the operator / service provider. service. In this example, the device activity is recorded by service processor 115 and transmitted to service controller 122 (for example, the IT manager controls service controller 122). In another example, a third-party after-sales product is provided in which the service controller 122 is hosted by the third party and the device management entity (for example, the IT manager or the parents of the user of the device for parental control) uses a secure Virtual Service Provider (VSP) website to control the devices belonging to that device partition of the management entity (for example, partitions and VSP techniques are described below with respect to Figure 49). The VSP secure website techniques described in this document can also be applied to servers owned by the service provider with device partitions for the purpose of controlling, for example, controllers (for example, DPC 5402 policy implementation as shown in Figure 54) of Deep Packet Inspection (DPI) to provide similar or substantially equivalent service use / control capabilities using network-based service control techniques, as similarly described in detail below with respect to Figures 49 and 54 (for example, VSP control of the IT manager of a group partition and / or VSP control of MVNO of a group partition).

Service processor configurations for devices

Figure 9 illustrates a hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments. As shown in Figure 9, the service processor 115 is stored in a non-volatile memory 910 and a memory 920 of the device 100. As will be appreciated by those skilled in the art.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

subject matter, the present invention can operate with virtually any device architecture, and the device architectures discussed herein (for example, with respect to Figures 9 to 15) are examples of various implementations in certain devices (eg, of different representations of the device 100).

As shown in Figure 9, the device 100 also includes a processor 930, sometimes referred to as a CPU or central processor unit, an APU or application processor unit, a main processor, a computing device or many other terms either known. In some embodiments, the device 100 includes one or more processors and / or a multi-core processor. As shown, processor 930 includes a subprocessor 935. In some embodiments, processor 930 and / or subprocessor 935 are based on an architecture sometimes referred to as a set of complex computer instructions or CISC, a set of reduced computer instructions 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 of one or more of the standardized design library or published architecture, or includes specialized logic and circuitry designed for a given device 100 or collection of such devices. In some embodiments, one device includes more than one processor and / or sub-processor, and in such a device, a processor and / or sub-processor may have an architecture while the other may have a somewhat different architecture or completely different. In some embodiments, one or more of the processor and / or subprocessors may have an architecture or instruction set of general purpose, may have an architecture or instruction set that is partially general, partially specialized, or may have an instruction set or architecture that is completely specialized. In some embodiments, a device includes more than one processor and / or sub-processor, and in such a device, there may be a division of functionality for one or more processors and / or sub-processors. For example, one or more processors and / or subprocessors may perform general operating system or application program execution functions, while another or more may perform communication modem functions, input / output functions, interface functions. user, graphics or multimedia functions, communication stack functions, security functions, memory management functions or direct memory access, computer functions and / or may share these or other specialized or partially specialized functions. In some embodiments, any 930 processor and / or any 935 subprocessor may run a low level operating system, a high level operating system, a combination of low level and high level operating systems, or may 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 Figure 9, the device 100 also includes non-volatile memory 910, memory 920, graphics memory 950 and / or other memory used for general and / or specialized purposes. As shown, the device 100 also includes a graphics processor 938 (for example, for graphics processing functions). In some embodiments, the graphics processing functions are performed by the processor 930 and / or subprocessor 935, and a separate graphics process 938 is not included in the device 100. As shown in Figure 9, the device 100 includes the following modems: 940 wired line modem, WWAN 942 modem, 944 USB modem, 946 Wi-Fi modem, 948 Bluetooth modem, and 949 Ethernet modem. In some embodiments, device 100 includes one or more of these modems and / or other modems (for example, for other network interconnection / access technologies). In some embodiments, some or all of the functions performed by one or more of these modems are performed by processor 930 and / or subprocessor 935. For example, processor 930 may implement some or all of certain functional aspects of WWAN, such as 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, the 930 processor as functionally analyzed above is provided in a separate specialized processor as shown similarly with respect to the 938 graphics and / or multimedia processor.

As also shown in Figure 9, the 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 each other (for example, allows the intercommunication). In some embodiments, the internal communication bus structure 960 is based on one or more general purpose buses, such as AMBA, AHP, USB, PCIe, GPIO, UART, SPI, I2C, Firewire, 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 interconnection logic or protocol schemes. As will be apparent to one skilled in the art, any of these or other bus schemes can be used in isolation and / or in combination for various interconnections between the components of the device 100.

In some embodiments, all or a portion of the functions of the service processor 115 disclosed herein are implemented in software. In some embodiments, all or a portion of the functions of service processor 115 are implemented in hardware. In some embodiments, all or substantially all of the functionality (as discussed herein) of service processor 115 is implemented and stored in software that can be performed on (for example, run by) various components in device 100. Figure 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. In

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, it is advantageous to store or implement certain or all portions of service processor 115 in protected or secure memory so that other unwanted programs (and / or unauthorized users) have difficult access to functions or software in the service processor 115. In some embodiments, service processor 115, at least in part, is implemented in and / or stored in secure nonvolatile memory (for example, nonvolatile memory 930 may be secure nonvolatile memory) that is not accessible without pass codes and / or other security mechanisms. In some embodiments, the ability to load at least a portion of the service processor software 115 into protected nonvolatile memory also requires a secure key and / or signature and / or requires that the service processor software components 115 that are loaded in non-volatile memory they are also securely encrypted and properly signed by an authority that is reliable by a secure software download function, such as a 1663 service downloader as discussed below (and as shown in Figure 16). In some embodiments, a secure software download embodiment also uses secure nonvolatile memory. Those skilled in the art will also appreciate that all memory can be on chip, off chip, on board and / or off board. In some embodiments, the service processor 115 which, as shown in Figure 9, is stored or implemented in non-volatile memory 910 and memory 920, may be partially implemented in other components in the device 100.

As shown, the device 100 also includes a user interface device component 980 for communicating with user interface devices (e.g., keyboards, displays and / or other interface devices) and another I / O device component. 985 to communicate 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 to allow one or more users to use the device 100.

Figure 10 illustrates another hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments. As shown in Figure 10, the service processor 115 is implemented in the processor 930 of the device 100. In some embodiments, this implementation can be achieved in part or in its entirety in software, implemented and / or executed in the processor 930. In some embodiments, the implementation and / or execution may be achieved in part or in full in hardware found in the processor 930. While the service processor 115 is shown in Figure 10 stored, implemented and / or executed in the processor 930, in other embodiments, the service processor 115 is partly implemented in other components in the device 100, for example, as discussed below.

Service processor implemented in a communications modem

Figure 11 illustrates another hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments. As shown in Figure 11, the service processor 115 is implemented in the WWAN modem 942 of the device 100. In some embodiments, this implementation may be achieved in part or in full in software, implemented and / or executed in the modem. of WWAN 942. In some embodiments, the implementation and / or execution may be achieved in part or in full in hardware found in the WWAN 942 modem. In some embodiments, service process 115 is implemented in another modem component of device 100 and / or one or more of the modem components of device 100.

In some embodiments, the service processor 115 is implemented in a modem processor (for example, the WWAN 942 modem or the WWAN / Wi-Fi modem), and the service processor 115 may be installed and / or run in memory protected and / or secure or in processor hardware in the modem. The modem memory can be made robust to hacking or manipulation 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 the service processor 115 is implemented in a modem processor (eg, WWAN modem hardware or software 942), and a portion of the service processor 115 is implemented in another device 100 of the processor 930. For example, the device service monitoring agent 1696 and one or more service use measurement points (see the analysis associated with Figure 21) may be implemented in a modem processor, and other service processor elements 115 may be implemented in the operating system processor of the main device 930. As another example, a second (or first) service monitoring agent 1696 and one or more service use measurement points can be implemented in a modem processor, and a first (or second) 1696 service monitor with one or more service measurement points can be implemented in the main operating system processor 930 for di device 100. For example, such embodiments can be configured to provide a service usage measurement and generation system that offers a diversified countermeasure to protect against piracy, tampering or other errors for device-based service usage measurements that can be made. more difficult to hack or manipulate than with certain software embodiments in the 930 processor. For example, such embodiments may be employed when one or more of the following capabilities are not available: network-based service usage measures, or verification measures of implementation of network-based service profile or policy, and error response action capabilities of network-based service usage verification.

In some embodiments, certain portions of service processor 115 that deal with service monitoring

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

The application layer or traffic flow identification (for example, labeling or shaping traffic flow as disclosed elsewhere) is implemented in a main processor 930, and other portions of the service processor 115 are implemented in a processor modem (for example, WWAN 942 modem).

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 then, the WWAN 942 modem connection can be an internal connection to the device 100, for example a USB, GPIO, AMBA or other bus, or it can be a connection that extends external to the device such as by 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 that runs over USB or PCIe, a GPIO connection that runs from a 930 processor chipset to a chipset modem inside a mobile device, or a Wi-Fi connection that runs from a Wi-Fi modem inside device 100 to an intermediate modem or combination network interconnect device that forwards access network traffic between the access network connection and the device via the Wi-Fi connection. In some embodiments, in addition to the service processor 115 that is implemented in the WWAN modem 942 either internal or external to the device 100, similarly the service processor 115 can be implemented in a wired line modem 940, such as DSL, Cable or fiber, another wireless LAN or PAN modem, such as Wi-Fi, Zigbee, Bluetooth 948 modem, White Space or some other modem, connected internal to device 100 or external to device 100 via a LAN or PAN extension of the 960 internal or external communications bus structure.

In some embodiments, a complete integral reference design product for the device modem (one or more of 942, 946, 948, 949, 944, 940) combined with an integrated service processor 115, possibly with an application interface Well-defined and documented and a well-defined and documented service processor developer kit (SPDK) provides a powerful product realization for the purpose of achieving mass market distribution and use for modem features with service processor 115 and controller associated service 122. For example, embodiments that include the WWAN 942 modem, possibly in combination with one or more additional modems that include the 946 Wi-Fi modem, 948 bluetooth modem, 944 USB modem, and 949 Ethernet modem, can be combined with a pre-certified or pre-certified integrated embodiment of service processor 115, possibly in combination with a well-defined API for writing software applications that interconnect with, reside in or communicate with this integral modem embodiment. As disclosed herein, the advantageous capabilities of the service processor 115, possibly in conjunction with the service controller 122, to aid in the monitoring, control, billing and verification of services are made more available to the manufacturers of the device 100 such that, because manufacturers do not need to spend so much time and resources to develop a custom modem only for a subset of devices that the integral modem can be used to support. In some embodiments, service processor 115, as discussed herein, can be configured to provide device-assisted monitoring, billing and / or service verification through not only when connected to the WWAN network through the WWAN modem, but also when connected to other networks that correspond to the other access modems included in the integral combined module design plus service processor 115 (or SPDK or chipset plus service processor 115). The pre-integrated service processor 115 and API possibly in combination with testing and certification can be packaged in a small form factor that can have standardized interfaces such as USB, PCIe, firewire, Display Port, GPIO or other interface. The form factor can be miniaturized in standardized configurations such as mini-card, half-card or even smaller form factors, or it can be designed in an unconventional or proprietary form factor. The module form factor can be well documented to simplify integration into various device designs 100. SPDK embodiments can be designed to contain one or more of the following: hardware integration and usage documentation, software integration documentation, Software programming documentation, application interface documentation, service controller documentation, global test guidelines and global usage guidelines. In some embodiments, the modem module may be integrated with the service processor functionality 115 as a combined chipset, firmware product and / or software, with other SPDK features very similar to those listed above. The service controller programming guide for these integral embodiments can also be documented for the SPDK 115 service processor software, integral 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 sending 100 device products (or integrated network interconnect device products) with any of the monitoring, control, billing service verification capabilities assisted by device disclosed in This document.

Figure 12 illustrates another hardware diagram of a device 100 that includes a service processor 115 in accordance with some embodiments. As shown in Figure 12, service processor 115 is implemented in the other I / O device component 980 of device 100. In some embodiments, this implementation can be achieved in part or in full in software, implemented and / or executed on the other component of the 980 I / O devices (for example, a SIM / USIM card or other secure hardware I / O device). In some embodiments, the implementation and / or execution can be achieved in part or in full in hardware found in the other 980 I / O device component.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

As discussed above, various embodiments include product designs in which the service processor 115 resides in the volatile device or non-volatile memory (see Figure 9), the device application processor or CPU (see Figure 10) , the wireless access modem (see Figure 11) (or any other modem), or other I / O device (see Figure 12). Although these are only a few of the placement embodiments of the example service processor 115, these embodiments show that the placement of where the software or hardware to implement the service processor 115 can reside in the device 100 is very flexible and can be implemented. in a multitude of places and ways depending on the device and / or other technical design choices.

Figure 13 illustrates another hardware diagram of a device 100 that includes a service processor 115 implemented in external memory of a Chip System (SOC) 1310 in accordance with some embodiments. As shown in Figure 13, service processor 115 is implemented in external memory 1320 of device 100. In some embodiments, this implementation may be achieved in part or in full in software, implemented and / or executed in external memory. 1320. In some embodiments, the implementation and / or execution may be achieved in part or in full in hardware found in external memory 1320. In some embodiments, SOC chipset 1310 and external memory 1320 provide a portion or All device 100 hardware.

Figure 14 illustrates another hardware diagram of a device 100 that includes a service processor 115 implemented in external memory of a Chip System (SOC) 1310 in accordance with some embodiments. As shown, 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 Figure 9. In some embodiments, the assembly SOC chips 1310 and external memory 1320 provide a portion or all of the hardware of the device 100.

As similarly discussed above with respect to Figures 9 to 12, various embodiments include product designs that include the SOC chipset 1310 in which the service processor 115 resides in an internal volatile or nonvolatile memory 910 of the SOC 1310 chipset (see Figure 14), the device application processor or CPU 930 and / or sub processor 935, modems 940, 942, 944, 946, 948, and / or 949 (or any other modem), another I / O device 985, and / or external memory 1320 (see Figure 13) (and / or any combinations thereof). Although these are only a few of the examples of the service processor placement embodiments 115, these embodiments show that the placement of where the software or hardware may reside to implement the service processor 115 in the SOC 1310 chipset and / or the external memory 1320 of the device 100 is very flexible and can be implemented in a multitude of places and ways depending on the device and / or other technical design choices.

The above analysis with respect to Figures 9 to 14 illustrating various embodiments of internal hardware for device 100 applies equally to this partitioning of device functionality or any other partitioning of how components are configured in device 100, whether all Separate components, some of the components are combined into a single chipset but there are still multiple chipsets, or all components are combined into a chipset. For example, Figures 9 to 14 illustrating various embodiments of internal hardware for device 100 show various access modem components that include wired line modem 940, wireless wide area network modem (WWAN) 942, modem USB 944, Wi-Fi modem 946, Bluetooth 948 modem and 949 Ethernet modem. In some embodiments, the 940 wired line modem is a DSL or cable modem such as DOCSIS, or some other modem with a permanent connection such as fiber. In some embodiments, as discussed above and then, the connection to the wired line access network is achieved through an extension of the internal or external communications bus structure 960. For example, such an extension is achieved using one or the other modems, such as the 946 Wi-Fi modem or 949 Ethernet modem, which connects to a local area network that in turn connects the access network through a device that establishes a bridge the local area network to the access network. One skilled in the art will appreciate that when the device connection to any access network is analyzed the connection can be via a direct connection to the network, such as a WWAN modem connection of 3G or 4G 942 to a WWAN network of 3G or 4G, or it can be a connection to the access network through an intermediate connection, such as a 946 Wi-Fi modem connection to a modem or combination network interconnect device that has a LAN connection. Wi-Fi and a 3G or 4G access network connection. Another example of an embodiment of an extended modem connection includes a 946 Wi-Fi modem device connection to a modem or combination network interconnect device that includes a Wi-Fi LAN connection and a network access connection. DOCSIS or DSL. Other examples of such combinations will be readily apparent to one skilled in the art.

Service processor configurations for intermediate network interconnection devices

Figures 15A to 15C illustrate hardware diagrams of a device 100 that includes a service processor 115 and a bus structure extension 1510 using intermediate modem or network interconnect device combinations according to various embodiments. For example, Figures 15A and 15B illustrate various extended modem alternatives for access network connection through an intermediate or combination modem

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

of network interconnect device having a connection (for example, LAN connection) to one or more devices 100.

In some embodiments, device 100 includes a 3G and / or 4G network access connection in combination with the Wi-Fi LAN connection to device 100. For example, the intermediate device or combination of network interconnect device may be a device that simply translates Wi-Fi data to the WWAN access network without implementing any portion of service processor 115 as shown in Figure 15B (1). In some embodiments, an intermediate device or combination network interconnection device includes a more sophisticated implementation that includes a network interconnection stack and in some embodiments a processor, as is the case, for example, if the network interconnection device Intermediate or combination network interconnect device includes a router function, in which case the service processor 115 may be partially or completely implemented in the intermediate modem or combination network interconnect device. The intermediate modem or combination network interconnect device can also be a multi-user device in which more than one user gains access to the 3G or 4G access network via the Wi-Fi LAN connection. In the case of a network of multiple users of this type, the access network connection may include several managed service links using multiple instances of service processor 115, each instance, for example, being implemented in whole or in part in the device 100 with the intermediate modem or combination network interconnection device providing only the translation services from the Wi-Fi LAN to the WWAN access network.

Referring now to Figures 15A and 15B (2) - (4), in some embodiments, service processors 115 are partially or fully implemented in the intermediate modem or combination network interconnect device. In the case where the service processor 115 is implemented in part or in its entirety in the intermediate modem or combination of network interconnection device, the service processor 115 can be implemented for each device or each user in the network so that there is Multiple managed service provider accounts that all gain access through the same intermediate modem or combination network interconnect device. In some embodiments, the service processor functions 115 are implemented in an aggregate account that includes WWAN access network traffic for all users or devices connected to the Wi-Fi LAN served by the intermediate modem or device combination Network interconnection. In some embodiments, the central provider may also provide an aggregate account service plan, such as a family plan, a corporate user group plan and / or an instant hot spot plan. In the case where there is an account for the intermediate modem or combination of network interconnection device, the intermediate modem or combination of network interconnection device may implement a local division of services to one or more devices 100 or users in which control or manage the services by the intermediate modem or combination of network interconnection device or device 100, but the management is not subject to the control service provider and is auxiliary to the service management or service policy implementation performed by the service processor 115. In some embodiments, another service model may also be supported in which there is an aggregate service provider plan associated with an intermediate modem or network interconnection device combination, or a group of intermediate modems or combinations network interconnection device but where each user or device still has its own The service plan that is a sub-plan under the aggregate plan so that each user or device has independent service policy implementation with a single instance of the service processor 115 instead of the service policy implementation added through multiple users in the group with a single instance of service processor 115.

As shown in Figure 15A and 15B (2), in some embodiments, the device 100 includes a 946 Wi-Fi modem, a 946 Wi-Fi modem combined with a 3G and / or 4G 1530 WWAN modem in the intermediate modem or combination of network interconnect device 1510, and the intermediate modem or combination of network interconnect device forwards WWAN access network traffic to and from the device 100 via the Wi-Fi link. For example, the service processor 115 can be fully implemented in the device 100 and the service provider account can be associated exclusively with a device. This is an embodiment associated with one or more of Figures 29, 31, 32 or 34 discussed below, in which the modem bus represents the Wi-Fi LAN connection via the 946 Wi-Fi modem. similar, as shown in Figures 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 configuration, DSL wired line, DOCSIS cable or wired fiber cable line instead of the 3G and / or 4G access network connection to the intermediate modem or combination of 1510 network interconnect device. In addition, various other embodiments similarly use DSL as shown in Figures 15A and 15B (4), USB, Ethernet, Bluetooth or other LAN or point-to-point connection from device 100 to the intermediate modem or combination of network interconnect device 1510.

In some embodiments, a portion of service processor 115 is implemented in device 100, such as application interface agent 1693 and other support agents (see Figure 16), and another portion of service provider 115 is implemented in the intermediate modem or network interconnection device combination, such as policy implementation agent 1690 or possibly the modem firewall 1655 as well as other agents (see Figure 16). This is an embodiment associated with one or more of Figures 30 or 36

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

discussed below, in which the modem bus in the figure represents the Wi-Fi LAN connection via Wi-Fi modem 946. In this example, service provider 115 may still offer individual service plans associated exclusively with a device, or it may offer an aggregate plan in which the portion of the service processor 115 located in the intermediate modem or combination of network interconnect device 1510 adds service plans in a WWAN connection but each individual device 100 has a Single service interface through the application interface agents and associated agents located on the device 100. Similarly, such an implementation can be provided using a different access modem and access network, for example a 2G WWAN configuration and / or 3G, DSL wired line, DOCSIS cable wired line or fiber wired line instead of the ac network connection 3G and / or 4G cessation to the intermediate modem or combination of 1510 network interconnect device. In addition, various other embodiments similarly use USB, Ethernet, Bluetooth or other LAN or point-to-point connection from the device 100 to the modem intermediate or combination network interconnection device 1510.

In some embodiments, the entire service processor 115 is implemented in the intermediate modem or combination of network interconnect device 1510 and the demand for the aggregate device or user traffic from the LAN port is served through a network plan account. service provider service. This is an embodiment associated with Figure 35 in which, as discussed below, the modem bus in the figure represents the Wi-Fi LAN connection via the 946 Wi-Fi modem. Similarly, it can be provided such an implementation using a different access modem and access network, for example a 2G and / or 3G WWAN configuration, DSL wired line, DOCSIS cable wired line or fiber wired line instead of the connection of 3G and / or 4G access network to the intermediate modem or combination of 1510 network interconnect device. In addition, various other embodiments similarly use USB, Ethernet, Bluetooth or other LAN or point-to-point connection from device 100 to Intermediate modem or combination of network interconnect device 1510.

In some embodiments, the device 100 uses the integrated WWAN modem 942 when it is outside the Wi-Fi LAN coverage area for one or more reliable access networks for the device, and when the device falls within the range of a network of Wi-Fi associated with an intermediate modem or combination of network interconnect device connected to a reliable wired line access network, the device may switch to the Wi-Fi link service to connect service processor 115 to the service network reliable wired line access. In some embodiments, the decision to switch to the Wi-Fi LAN associated with a reliable wired line access network can be made automatically by the device based on the policy implementation rule settings for modem selection and control 1811 and / or policy control agent 1692, can be done by the user, or can be done by service controller 122 (see Figure 18). In addition, various other embodiments similarly use USB, Ethernet, Bluetooth or other LAN or point-to-point connection from the device 100 to the intermediate modem or combination network interconnect device 1510.

Figure 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 network interconnect device combinations according to various embodiments. In some embodiments, more than one access network connection is implemented in the intermediate modem or combination of network interconnect device 1510. This allows the device 100 to potentially connect through the intermediate modem or combination of network interconnect device. with a choice of access network services. An example of such an embodiment is illustrated in Figure 15C in which an access network router (for example, a business router) connected to a LAN with a wired primary line backlink connection and a network connection. WWAN backup, for example 3G or 4G, to provide access services when the primary wired line connection fails. As discussed above, the service profile service provider for service processor 115 and the service plan account can be configured as an aggregate account with multiple users connected to the LAN. The service provider may choose to use an embodiment that includes a portion of the service processor 115 on each device 100 so that the account may be managed by each user or each device, or the service provider may choose to implement all necessary features in the device. Service processor 115 in the intermediate modem or combination network interconnect device so that there is no visibility for individual devices 100 or users.

As described herein, various embodiments provide many service policy implementation options that can enhance the service provider's control of the service and cost experience, or enhance the user control of the service and cost experience by providing verifiable or commitment-resistant solutions to manage service policy implementation in the intermediate modem or combination of network interconnection device, for one or both of the WWAN or wired 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 verification of service policy implementation or commitment resistance made possible by these embodiments improve the backup services offered and the primary wired line services. One skilled in the art will now appreciate that any number of wired 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 network interconnect device combinations that

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

establish a bridge from 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 and / or multiple access networks in which the service account can be consistent across multiple networks, and service policies They can be changed from network to network as deemed appropriate by the service provider with service notification, service cost control and privacy preference entries from the user.

In various embodiments, the verification embodiments discussed in this document may be applied for verification of service policy implementation or commitment protection of service policy implementation. In some embodiments, instead of attaching a service provider service plan account to a single device, it is attached to (for example, associated with) a user. For example, when the user logs into an access network with a service controller controlled by a service provider, regardless of which device the user logs in, the user's service plan profile can be searched automatically in the billing system Central 123 and dynamically loaded (for example, downloaded) to the device 100 from the service controller 122 (for example, a service profile provided on demand based on the identity of the user). In some embodiments, in addition to dynamically loading the implementation of service policy and user control settings, one or more of the user's preferences including notification, service control, traffic monitoring information generation privacy, and privacy of Customer Relationship Management (CRM) information generation is also dynamically loaded. For example, this allows the user to have the same service, performance and experience settings regardless of the device on which the user is logged in and using on the network. In addition, as discussed in this document, in the various embodiments that request roaming from one type of access network to another, the user service plan profile, which includes all of the above in addition to the plan profile changes of service that have an effect between different types of access network, can be used on any device and on any network, providing the user with a consistent, commitment-resistant or verifiable service experience regardless of the network or device.

Many of the embodiments described herein refer to a user using the 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, devices or devices for automation, telemetry, sensors, security or surveillance, device control, remote machine-to-machine data connections, certain remote access settings, bi-directional power measurement or control, asset tracking , tracking people or other applications where a human user interface is not required for device 100.

Various embodiments of the device 100 described above include other 985 I / O devices. In some embodiments, these other devices include other modems, other special purpose hardware components and / or other I / O devices or controllers or modems for connecting to others. 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 the functions of the service processor 115 in an embodiment of the device 100 that includes a SIM and / or a USIM. In some embodiments, the other 985 I / O devices include a hardware device designed to implement a portion or all of the functions of the service processor 115. For example, this is advantageous in the case where the original device 100 was not manufactured. with service processor 115; in cases where specialized hardware is desired to improve one or more aspects of the service processor performance 115; which allows users, for example, to have the same service, performance and experience settings regardless of the device the user is using on the network using such a SIM and / or USIM (for example, or a type of key); and / or in cases where a separate component is desired to assist in compromise protection for one or more aspects of the service processor 115.

As discussed above, some embodiments described herein provide billing for certain access services. In some embodiments, various applications do not require or involve billing of certain services. For example, applications such as management of groups of implementation of access policy of IT business personnel (Information Technology) or access cost control or access security policy, privacy control, parental control, network quality control or improvement of the service, private network services, free access services, publicly funded access services, fixed rate service without options and other services or other examples that will be apparent to a person skilled in the art do not require functionality but benefit from Many other aspects of various embodiments.

Service processor and service controller for monitoring, notification and verifiable service control

Figure 16 is a functional diagram illustrating a service processor based on device 115 and a service controller 122 in accordance with some embodiments. For example, this provides device-based service processor implementation with relatively full functionality and service controller implementation. As shown, this corresponds to a network interconnection configuration in which the service controller 122 is connected to the Internet 120 and not directly to the access network 1610. As

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

shows, a data plane communication path (for example, service traffic plane) is shown on continuous line connections and a control plane communication path (for example, service control plane) is shown on connections dashed line As discussed above, it is understood that the division in functionality between one device agent and another is based on, for example, design choices, network environments, devices and / or services / applications, and various different combinations can be used in Various different implementations. For example, functional lines can be redrawn in any way that product designers deem appropriate. As shown, this includes certain functional divisions and bifurcations for device agents as an illustrative implementation, although other potentially more complex embodiments may include different functional divisions and bifurcations for device agent functionality specifications, for example, to manage the specification of development and test complexity and workflow. In addition, the placement of agents that operate, interact with or monitor the data path can be moved or re-sorted in various embodiments. For example, as discussed in some embodiments below, one or more of the policy implementation or service monitoring functions may be placed in one of the access modems located below the modem driver and modem bus in the stack of communication as illustrated in certain figures and described in this document. As discussed below, some figures of the simplified embodiment illustrate that not all functions illustrated in all figures are necessary for many designs, so a product / service designer may choose to implement those functions that are believed to be the most advantageous or sufficient for the desired purposes and / or environment. The functional elements shown in Figure 16 are described below.

As shown, service processor 115 includes a service control device link 1691. For example, as device-based service control techniques that involve monitoring over a network become more sophisticated, each It becomes increasingly important to have an effective and flexible control plane communication link between the device agents and the network elements with which it communicates, controls, monitors or verifies the service policy. In some embodiments, the service control device link 1691 provides the device side of a system for transmitting and receiving service agent to / from network element functions. In some embodiments, the traffic efficiency of this link is enhanced by storing intermediate memory and aligning multiple agent messages in the transmissions. In some embodiments, traffic efficiency is further improved by controlling the transmission frequency or by linking the transmission frequency to the rate of service use or traffic use. In some embodiments, one or more levels of security or encryption are used to make the robust link to discovery, clandestine listening or compromise. In some embodiments, the service control device link 1691 also provides the communication and operation indication timing link for the agent operation indication function. As discussed below, various embodiments disclosed herein for the 1691 service control device link provide an effective and secure solution for transmitting and receiving service policy implementation, control, monitoring and verification information with other elements of net.

In some embodiments, the agent messages of the service control device link 1691 are transmitted asynchronously as they are generated by one or more of the service agents. In some embodiments, the service control device link 1691 performs collection or buffering of agent messages between transmissions. In some embodiments, the service control device link 1691 determines when to transmit based potentially on several parameters that include, for example, one or more of the following parameters: periodic timer trigger, waits until a certain amount of time has taken place. service use or traffic use, respond to a service controller message, respond to a request from a service controller, initiated by one or more agents, initiated by a verification error condition, initiated by some other error or condition of State. In some embodiments, once a transmission trigger has taken place, the service control device link 1691 assembles all agent communications stored in buffer memory and frames communications.

In some embodiments, the transmission trigger is controlled by waiting for an amount of service use, such as waiting until a certain amount of data traffic has passed, which reduces the use of control plane communication channel traffic to a fraction. of data plane traffic. For example, this approach retains network capacity and reduces the cost of service even in traffic scenarios where data traffic is light.

In some embodiments, the transmission trigger is based on waiting for an amount of service use, and also including a minimum transmission rate that activates a transmission according to one or more of the following parameters: a maximum time between clock transmissions for keeping service processor 115 in communication with service controller 122 when little or no use of service is taking place, an interrogation request of some kind from service controller 122, a response to a service controller operation, a transmission generated by a service verification error event, or a transmission generated by some other asynchronous event with critical time service processor 115 (or service controller 122) messaging needs, such as a transaction or billing event of service or a user request. For example, descending service control plane traffic is reduced to a drip

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

relatively inexpensive and conservative capacity when the data traffic of the device 100 is not significant. At the same time, this approach also provides a real-time or near real-time service control plane traffic flow that is both cost and capacity efficient, since service control plane traffic is a relatively high percentage. small data plane traffic when the use of data plane traffic is high. For example, when the use of data plane traffic is high, it is generally the time when close monitoring of the verification of the implementation of the service policy or the prevention of compromise can be particularly important and maintaining the overhead of the data plane. control near a fraction of the data plane traffic, the monitoring and control of services are kept at a reasonable cost in terms of percentage of both the bandwidth used and the capacity of the network. In some embodiments, the service use or service activity trigger takes place based on some measure other than traffic use, such as a number of messages processed, one or more billing events, number of files downloaded, number of executed applications or time that an application has been running, use of one or more specified applications, changes in GPS coordinates, 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 assurance, signature, encryption or otherwise protection of communications prior to shipment. For example, the service control device link 1691 can be sent to the transport layer or directly to the transmission link layer. In some embodiments, communications are further secured with transport layer encryption, such as TCP (Transport Layer Transport Control Protocol Security) TLS or other secure transport layer protocol. In some embodiments, communications are encrypted at the link layer, such as IPSEC (Internet Protocol Security), various VPN services (Virtual Private Network), other forms of IP layer encryption and / or other encryption technique Link layer

In some embodiments, service control link 1691 includes the agent operation indication function discussed above in which agents provide certain required reports to service controller 122 for the purpose of service policy implementation verification (for example , reports related to verification of certain aspects of service processor 115) or for other purposes. For example, such agent operation indication messages may be open / transparent (decrypted) or encrypted, signed and / or otherwise secured. In some embodiments, these messages include one or more of the types of messages described below: an agent information message, an agent check message and / or agent cross check message.

In some embodiments, an agent information message is included in the agent operation indication service policy verification message, which includes, for example, any information that the agent needs to communicate to 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, may be included in the agent operation indication service policy implementation verification message.

In some embodiments, an agent verification message is included in an agent operation indication service policy implementation verification message, which includes, for example, a transmission of a unique agent identifier, secure unique identifier and / or an encrypted and signed message with a chopping function that begins with a shared secret or status variable for the chopping function. For example, an agent self-test can be included in the agent operation indication service policy implementation verification message, which includes generating information about the agent configuration, agent operation, agent code status, communication log of agent, agent error flags and / or other associated agent information potentially chopped, encrypted, signed or otherwise secured in the message (for example, using a unique shared secret for that agent).

In some embodiments, an agent cross-check message is included in the agent operation indication service policy implementation verification message, which includes, for example, reports on status, configuration, operation observations, registration of communication or other aspects of another agent. For example, agent environment reports may be included in the agent operation indication service policy verification message, which includes, for example, reports on certain aspects of the service processor 115 operating environment, such as presence of software (for example, installation status of certain operating system and / or application software and / or components thereof), communication or communication attempts observed with agents, access or memory access attempts, access or access attempts network, attempted downloads or downloads of software, removal of software or download blocking, verification of service policy implementation or error conditions of engagement event with respect to the operating environment of service processor 115, and / or other messages regarding the verification or possibility of commitment associated with the operating environment or agents of the processing r service 115.

In some embodiments, the agent operation indication function also provides normal updates of important information for user service notification services. For example, the elements

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Network-based can provide normal synchronization updates for device-based service use or service activity counters in which the measures of service use or service activity available from one or more network service history items are transmitted to device 100. This allows service usage counter errors between the device service counter and the counters used for central billing to be minimized. A measure of service use or common service activity is the use of total traffic measured to date within a time frame over which a service limit is applicable. Other measures of service use or service activity can also be tracked and reconciled in a similar manner.

In some embodiments for the operation indication function, the service controller 122 verifies that the planned agent reports are being received and that the reports are within expected parameters. In some embodiments, the access control integrity server 1654 issues signed challenge / response sequences to the policy implementation agent 1690. For example, the challenges may be synchronous, issued when an event or error condition occurs, issued in 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 reinforces the verification of service use measurement or service activity. For example, a challenge / response may be sent through the operation indication link in order to verify the integrity of the device agent. Various verification embodiments related to challenge / response are described below.

In some embodiments, the challenge / response operation indication message may include sending any kind of command or query, secure or transmitted in open, receiving a response from the agent and then evaluating the response to determine if the response is within a expected range of parameters for a correctly configured agent, an agent that is operating properly, an agent that is not partially compromised, or an agent that is not fully committed. In some embodiments, the agent is only required to respond with a simple acknowledgment of receipt of the challenge. In some embodiments, the agent is required to respond with a message or piece of information that is known to the agent. In some embodiments, the agent is required to respond with a message or piece of information that is difficult to answer by the agent correctly if partially or completely compromised. In some embodiments, the agent is required to respond back with information regarding the operation or configuration of the agent that it is difficult for the agent to respond appropriately if the agent was not configured properly, did not operate properly, was partially compromised, or was completely compromised. . In some embodiments, the first agent is required to respond back information regarding the operation, configuration, status or behavior of a second agent that is difficult for the first or second agents to respond appropriately if the first or second agent was not configured. properly, did not operate properly, was partially engaged or completely engaged. 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, operation characteristics or other information with respect to other programs in the agent's operating environment. In some embodiments, the agent is required to respond with chopped information to be portions of code or a code sample (for example, the code portion or code sample may be specified by service controller 122).

In some embodiments, the information that the agent responds 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 to respond correctly or it would be difficult for the agent to respond appropriately. if the agent was not properly configured, was not operating within appropriate limits, was partially compromised or completely compromised. In some embodiments, the agent signs or encrypts information so that it is difficult to respond correctly when the message is decoded by service controller 122 unless the agent is properly configured, is operating within appropriate limits, is not partially compromised and Don't be completely engaged. In some embodiments, the agent is required to respond with a signed or encrypted piece of information that is difficult for the agent to generate unless the agent is properly configured, is operating within appropriate limits, is not partially committed and is not fully committed. . For example, the information chopped may be local device configuration information, code portions or all code, and / or the code portion to be used in the response may be specified by the service controller. In another example, the chopped information to which the agent responds may include a shared secret, and / or the chopped information may be information regarding the presence, configuration, operation characteristics or other information regarding other programs in the environment of agent operation.

Therefore, as described above, the agent operation indication function provides an important and effective system in some embodiments to verify the implementation of service policy or protect against engagement events. For example, there are many other functions that the agent operation indication service can perform and some are described herein while others will be apparent to a person skilled in the art given the principles, design background and various embodiments provided in the present document

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

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 refreshments of software elements. of service processor. There are many embodiments for such operations. In some embodiments, the software is received as a single file on the service control device link 1691. For example, the file may have encryption or encryption signed beyond any provided by the same communication link protocol. In some embodiments, the software files are segmented into smaller packets that communicate in multiple messages sent through the service control device link 1691. In some embodiments, once the file or files are received, or received The segmented portions of the file or files are communicated to a 1663 service downloader for file aggregation and installation, which, in some embodiments, is performed after additional measures to verify that the service processor software is complete. In some embodiments, the files are sent using other means of delivery, such as a direct TCP connector connection to the service downloader 1663 or some other software installer, which may also involve secure transport and additional levels of encryption.

As shown in Figure 16, an agent communication bus 1630 represents a functional description for providing communication for the various agents and functions of the service processor 115. In some embodiments, as depicted in the functional diagram illustrated in Figure 16 , the bus architecture is generally from multipoint to multipoint so that any agent can communicate with another agent, the service controller or in some cases other device components, such as the 1697 user interface 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 structure so that all agent communication can be concentrated, or secured, or controlled. , or restrict, or register or inform. In some embodiments, the agent communication bus is secured, signed, encrypted, hidden, partitioned and / or otherwise protected from unauthorized monitoring or use.

In some embodiments, as described below, there are multiple security layers applied to the 1630 agent communication bus communication protocols, such as including one or more of the following: point-to-point message exchange encryption using a or more keys that are partially shared or shared within the agent group of service processor 115 and / or service controller 122, point-to-point message exchange using one or more keys that are private to the two endpoints of communication, a bus-level message exchange encryption that may 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 agent group 115 and / or service controller 122, a set of secure messages that can be decoded or observed only by the agents for whom they are It is intended, a set of secure messages that allow communication between certain agents or service processor functions and external entities of the operating environment of the service processor. In some embodiments, and as described herein, 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 is also extended to the service control communications link 1653. In some embodiments, the system has the ability to replace keys or signatures occasionally or on a regular basis to ensure additionally against monitoring, clandestine listening or commitment of the communication system agent.

For example, various forms of message encryption and security structure 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 the keys and updates as appropriate; Agent-level encryption using agent-to-agent shared keys in which the secure server informs the 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 the agent of the required point-to-point keys and updates the keys as appropriate; agent-level access authorization, which only allows access to 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; Only UI messages are analyzed and passed, in which the UI cannot access configuration information and cannot issue challenges; agent level operation indication encryption, which can be point-to-point or shared key for that agent; control link level indication operation encryption; TLS (Transport Layer Security) communication protocols; server level operation indication encryption, which can be point-to-point or shared key for that secure server; and / or the 1694 access control integrity agent or function indication function that can become secure point-to-multipoint 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 agents are broadly or completely implemented in software, then the communication bus of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Agent can be implemented as an inter-process software communication bus. In some embodiments, an interprocess software communication bus of this type is a variant of the D bus (for example, a message bus system for interprocess software communication that, for example, helps applications / agents to talk to each other), or another interprocess communication protocol or system, that executes a session bus in which all communications through the session bus can be secured, signed, encrypted or otherwise protected. For example, the session bus can be further protected by storing all software (for example, software components, applications and / or agents) in secure memory, storing all software in encrypted form in secure memory, and / or running 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 mainly with hardware, then the implementation of the bus design will vary, and the principles and embodiments described herein will enable an expert in the matter to design the specific details of the agent communication bus 1630 to meet a particular set of desired product and functional requirements.

As shown in Figure 16, a 1694 access control integrity agent collects device information about service policy, service use 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 gaps in the service policy and control system implementation. In some embodiments, the access control integrity agent 1694 also initiates actions when a service policy violation or a system integrity breach is suspected. In some embodiments, access control integrity agent 1694 also performs asynchronous or periodic agent checks to verify the 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.

In some embodiments, the access control integrity agent 1694 obtains service use or service activity measurements from a service monitoring agent 1696 and compares one or more first service use measurement points against one or more second points. of service use measurement to verify the implementation of service policy. For example, as shown in Figure 21, if service use at measurement point IV is inconsistent with measurement point III, which, for example, may indicate, for example, that unauthorized use is taking place or unmonitored access modem (for example, modems 2122, 2123, 2124, 2125 or 2141). As another example, as also shown in Figure 21, if one or more aspects of the upstream traffic use measurement point II, which represents the upstream demand side of policy implementation agent 1690, is inconsistent with the Measurement point III of upstream traffic, which represents the traffic delivered from the policy implementation agent 1690, then the policy implementation agent 1690 may not operate properly. As another example, as also shown in Figure 21, if the service measurement point III and IV indicate that the firewall agent 1655 is passing traffic to the URLs or IP addresses that are in the locked 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 the 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 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 monitoring agent and it is found that the two are outside acceptable tolerance limits for comparison, then there may be a verification error in the use of service service monitoring or service activity accounting. There are numerous additional embodiments for such comparisons as described herein and others as will be readily apparent to one skilled in the art given the principles, design backgrounds and specific examples and various embodiments described herein.

In some embodiments, device service policy implementations are verified by comparing various service usage measures used in the device against expected service usage behavior or service activity given the policies (for example, one or more service policy settings , service profile settings or service profile 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 on the device 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 on the device compared to the service policy for data passed in a period of time of this type. For example, verification is performed based on a communication monitoring from the device based on IP addresses compared to the policy for permissible IP addresses. For example, verification is performed based on a measure of total data passed from the device by IP address compared to the policy for total data use by IP address. Other examples include comparisons of such policy against the real one based on other measures in / from / to the device, such as location, downloads, accessed email, URL and / or any other data, location, application, time or other criteria or any other criteria combination of criteria that can be measured to compare with various policy adjustments and / or restrictions.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, access control integrity agent 1694 monitors agent self-test reports that are properly configured. In some embodiments, the access control integrity agent 1694 reports that the agent self-checks reports to the service controller 122. In some embodiments, the access control integrity agent 1694 plays a role in transmission, reception and / or service use monitoring, adapting the use test to test aspects of monitoring or control for any subset of service activities. In some embodiments, the access control integrity agent 1694 plays a role in the generation and / or monitoring of billing test event. In some embodiments, 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.

In some embodiments, the 1694 access control integrity agent receives agent access attempt reports to determine if unauthorized agent access attempts are taking place. In some embodiments, access control integrity agent 1694 acts as a central secure communications hub for agent-to-agent or service controller 122-agent communication. For example, the access control integrity agent 1694 can be used so that no other software or function can access other agents or so that the agents cannot access other agents except through the point-to-multipoint communications hub sure. In some embodiments, this approach further enhances the compromise resistance for agents. In some embodiments, some or all of the agent communications, which include agent-to-agent or service controller 122-to-agent communications, and possibly including unauthorized attempts to communicate with agents, are monitored and recorded so that it can be maintained. a trace record of some or all agent communications. For example, the agent communication trace record can be summarized and / or compressed for transmission efficiency or reported on a regular basis, such as through the operation indication function, or the agent communication trace record can be reported. only when service controller 122 requests the agent communication trace record or when there is a verification error event. As described similarly above, partitioning of agent functions and server functions is provided herein primarily to help disclose various embodiments, although those skilled in the art will appreciate that other agent partitioning functions may be used based on in different design choices. For example, 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. For example, when the central agent communication hub function is located at the service control device link 1691, then the device link in terms of architecture can be a single point to multipoint secure communications hub for all communications from agent to agent and from service controller 122 to agent. In some embodiments, this approach has certain advantages from a verification perspective of service policy implementation or commitment protection robustness, or has certain advantages from a communications protocol effectiveness perspective, or it may simply be more effective to implement. It should be noted that in other embodiments described herein, agent-to-agent and agent-to-service controller communications 122 may be multipoint to multipoint, each agent having the ability to communicate with other agents or the service controller, this communication it can be secure, signed or encrypted or otherwise protected in some embodiments and be open / transparent in others. Also, as discussed in some embodiments, agents can maintain their own communications or attempted communications log, which can then be reported to service controller 122. In some embodiments, agents implement restrictions on which device components or agents they will make communications so that only agents who need to communicate with each other can do so.

In some embodiments, the 1691 service control device link reviews the local billing event history and compares such history to billing event reports to verify that a 1695 billing agent is functioning properly (for example, has not been tampered with. or has been compromised). In some embodiments, the service control device link 1691 performs cross-checking of the use of service or service activity against billing event reports from the billing agent 1695 to verify that events are being billed appropriately for service use or service activity In some embodiments, the service control device link 1691 performs cross-checking of the transaction billing process or records against transaction billing reports to ensure that the transaction billing events are 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 potentially compromised agent of this type.

In some embodiments, 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 service usage reports obtained from the service monitoring 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 the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

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 use or roaming service use conditions.

In some embodiments, the access control integrity agent 1694 checks to verify that the device is not beginning service use until it has been authenticated, authorized or has been granted access to the network. In some embodiments, access control integrity agent 1694 checks with service controller 122 or billing system 1619 to verify that the user or device has valid service validity and should be admitted for access on the network.

In some embodiments, an Activation Tracking Service (ATS) is provided in which the service monitoring function (for example, performed by the service monitoring agent 1696 and / or some other agent / component or combinations thereof) on the device) is used in part to determine which access networks they are connecting to and to record and / or report this information. In some embodiments, the ATS is activated only if the user of the device approves the generation of information from access networks connected by the user device. In some embodiments, the ATS is protected from tampering. For example, the ATS can harden, that is, be more resistant to manipulation, using a variety of techniques, including any of the following: the ATS can be located (for example, stored) in secure memory and / or secure hardware ; the ATS can be implemented in the system BIOS, the access modem and / or another difficult-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 reinstallation of the ATS if it is absent or 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 it is removed it must be replaced for proper device operation to resume. A variety of other manipulation resistance techniques can also be used to protect the ATS from manipulation as described similarly herein with respect to other software-based functions / components / device agents.

In some embodiments, the access control integrity agent 1694 verifies that the ATS software or hardware is present, properly configured or operating properly. In some embodiments, the access control integrity agent 1694 checks the network connection or activity history and compares these with ATS reports to verify that the activation tracking service reports are taking place properly. In some embodiments, the 1694 access control integrity agent replaces the ATS software if it had been removed. In some embodiments, the access control integrity agent 1694 monitors access or compromise of the ATS software to determine if it may have been compromised. In some embodiments, the access control integrity agent 1694 reports the status of the ATS functions.

In some embodiments, the access control integrity agent 1694 scans the local agent runtime environment to determine if there are unauthorized access to the functions, settings or code of the service processor. In some embodiments, access control integrity agent 1694 monitors software loading activity, protected memory access or communication with service processor agents 115 to detect unauthorized changes to the software or service processor configuration. For example, the access control integrity agent 1694 can have a local database of potentially malicious items and compare entries in the database against locally detected items. As another example, the access control integrity agent 1694 may communicate a list of some or all of the items detected locally to the service controller 122 to increase or take the place of the database comparison function that can be performed locally. In some embodiments, the access control integrity agent 1694 detects new software downloads, installations 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 load and invocation activity along with a record of other software runtime events and regularly reports this trace so that when an error occurs or commitment event The trace that precedes the event can be analyzed to determine the trace of the software or attacking activity that took place to cause the commitment or error. Once the software or activity that caused the compromise is known, it can be introduced 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 include software invocations, software downloads, attempts to install certain software / agent components and / or application or OS components, a sequence of memory I / O events, a sequence of access events. software, a sequence of communications or downloads of network address or URL or a sequence of access modem I / O activity. In various other embodiments of the 1694 access control integrity agent, the agent performs or communicates (securely) with other software / hardware device / network components that perform other signature, behavior blocking and / or detection techniques. intrusion, identification / detection and / or blocking based on the presence of potentially unwanted and / or potentially known malicious software and / or attempted intrusion by unauthorized software and / or unauthorized users, using, for example, real-time scanning, on access, periodic and / or on demand.

In some embodiments, the access control integrity agent 1694 detects or blocks behavior

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

potentially compromising other software programs / users that attempt unauthorized behavior in the operating environment of service processor 115. In some embodiments, access control integrity agent 1694 detects software that is being loaded that has the same name, identification, memory location or similar function as one or more of the service processor agents 115. In some embodiments, the access control integrity agent 1694 blocks the loading operation of such software. In some embodiments, the access control integrity agent 1694 detects or blocks unauthorized access of protected memory of the service processor 115. In some embodiments, the access control integrity agent 1694 verifies the configuration and operation of the service downloader secure 1663. In some embodiments, access control integrity agent 1694 monitors network I / O activity to detect potentially compromising events, such as a program that downloads from known or potentially suspicious IP addresses or URLs or a program that accesses certain IP addresses or URLs. In some embodiments, the access control integrity agent 1694 scans of the operating environment of the service processor are recorded and maintained for a period of time, and if a service policy verification error occurs, then they are analyzed or the scans immediately prior to the error are reported to service controller 122 for analysis. In some embodiments, such scans are regularly reported to service 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 for certain critical service processor functions, which in some cases include the access control integrity agent 1694 on a periodic basis, or on a regular basis. periodic basis when network access activity is not required or is minimal.

In some embodiments, the access control integrity agent 1694 determines whether a threshold has been exceeded for a maximum use trigger for environment services and / or others that should not use significant amounts of data (for example, based on the type of device and / or service profile settings).

In some embodiments, the access control integrity agent 1694 determines if there are verification errors in one or more of the verification process embodiments and, in some embodiments, reports errors immediately or in the following indication of agent operation to the controller of service 122. In some embodiments, any number of results from previous checks, monitoring activities, reports or tests are reported to service controller 122.

In some embodiments, a policy control agent 1692 receives policy instructions from the service controller 122 and / or the user through the billing agent 1695 and adapts the device service policy settings (e.g., service policy settings instant device) on one or more of the following agents / components: a 1690 policy implementation agent, the 1655 modem firewall, and / or a 1693 application interface agent. As shown in Figure 16, the firewall for modem 1655 is in communication with a modem controller 1640, which is in communication with the agent communication bus 1630 and the access network 1610. As shown with respect to the access network 1610, a billing server is also provided central 1619, an access network aAa server 1621 and the device server history 1618. As shown, Internet 120 is accessible via the access network 16 10 and the firewall 124, from which the device 100 can then access various Internet services 1615.

In some embodiments, policy control agent 1692 adapts the low level service policy rules / adjustments to accomplish one or more of the following objectives: to obtain use of higher level service or cost objectives, reduce capacity loss of network control channel, reduce the bandwidth of control plane server processing and / or provide a higher level of network privacy or neutrality while satisfying the objectives of service use or service activity. In some embodiments, the policy control agent 1692 performs a policy control function to adapt instant service policies to achieve a service use objective. In some embodiments, policy control agent 1692 receives service usage information from service monitoring agent 1696 to evaluate service usage history as compared to service usage objectives. In some embodiments, policy control agent 1692 uses the service use or service activity history of service monitor 1696 and various possible algorithm embodiments to create an estimate of projected future service usage. In some embodiments, policy control agent 1692 uses a future projection of service use to determine which service use controls or service activity need to be changed to maintain service use objectives. In some embodiments, policy control agent 1692 uses the service usage history to perform a service usage or service activity analysis to determine the distribution of service usage through service usage elements within categories, such as use by application, use by URL, use by address, use by type of content, use by time of day, use by access network, use by location and / or any other category to classify service use. In some embodiments, policy control agent 1692 uses service usage distribution analysis to determine which service usage elements or service activities are creating the most service usage (for example, if email, social networks or multimedia / online video application are creating the greatest use of service).

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, policy control agent 1692 is ordered, for example, by the user, through billing agent 1695 to perform a service control algorithm, such as a traffic shaping or download management, to manage use of service or service activities to help the user control the cost of services. As a basic example of such a traffic shaping algorithm, the traffic shaping algorithm can simply reduce the traffic speed for all applications and traffic types successively until service usage projections are within the limits of service usage during the current service billing period. To illustrate an algorithm that is more sophisticated and provides the advantage of leaving many elements of service use or service activities unaffected while only controlling the downward use of service use elements or more aggressive service activities, the shaping algorithm traffic can identify the highest traffic use applications and / or websites and successively reduce the fair traffic speed for the highest use applications and / or websites until service usage projections are within the limits of service usage during the current service billing period. These examples thereby reduce network traffic for the user in accordance with the user's service usage objectives while maintaining the overall satisfactory service usage experience for the user such that they satisfy various network neutrality requirements (by For example, traffic regulation of certain applications / websites based on user input in which categories are selected based on user service usage history, for example, a certain application may be using 90% of traffic usage aggregate). For example, adaptive regulation algorithms can be used to regulate the application traffic that the user requests to regulate, such as recursively regulating the specified application traffic (for example, to denigrate the use of traffic associated with that application and thus reduce the use of global service data).

In some embodiments, policy control agent 1692 adjusts the service policy based on the time of day. In some embodiments, policy control agent 1692 obtains a measure of network availability and adjusts the traffic shaping policy settings based on the available network capacity. In some embodiments, policy control agent 1692 automatically and dynamically adjusts the service policy based on one or more other policy settings, the service profile and / or the service plan associated with the device and / or the device. of user.

In some embodiments, various lower level service policy implementation embodiments are combined with a set of higher level service policy monitoring functions to provide verifiable network access control, authentication and device-assisted 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 related user experience referred to herein as environment activation. In some embodiments, the environment access generally refers to an initial service access in which such service access is somewhat limited, such as when the service options are significantly limited (eg, low network scan bandwidth and / or access to a specific transactional service), limited bandwidth, limited duration access before a service plan must be purchased to maintain the service or have the service suspended / deactivated or regulated or limited / reduced / otherwise degraded, and / or any other time-limited initial service scope based on quality, for the network-capable device. In some embodiments, environment activation is provided by establishing access control to a fixed destination (for example, providing access to a portal, such as a web page (for example, for a hot spot) or WAP (Protocol Protocol) page. Wireless Application), which provides the user with service plan options to obtain a service plan for the user's desired access, such as service plan options for data use, service types, time period for access ( for example, a day pass, a week pass or some other duration), and plan costs or service plans In some embodiments, the use of service data of the activated environment device is verified using IPDRs (for example , using the device ID / device number for the device 101 to determine if the device has been used in such a way that it is outside the plan for the service plan associated with the device 101, such such as based on the amount of data usage that exceeds the service data usage limits of the service plan, outside the plan / unauthorized access to certain websites, and / or outside the plan / unauthorized transactions). In some embodiments, the use of service data from the activated environment device is verified by establishing a maximum data rate in policy control agent 1692 and if / when it is determined that the device is exceeding a data rate / data usage. specified, then the use of service data is regulated accordingly. In some embodiments, various other verification approaches are used for environment activation purposes.

In some embodiments, policy control agent 1692 (and / or another agent / component of service processor 115 and / or service controller 122) performs a service control algorithm to help manage global network capacity or QoS (Quality of Service) application. In some embodiments, policy control agent 1692 (and / or another agent / service processor component 115) performs an access network selection algorithm to determine which access network to connect based on determined connection options and intensities of available wireless networks, network preference and security settings, network preferences based on cost of service use and / or any other criteria.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Therefore, as described herein with respect to various embodiments, service or service use activities can be measured by various agents at various different measurement points, which provides more robust verification and communication integrity of device-based services. . For example, it is much less likely and more difficult to compromise and / or falsify multiple agents. As described herein, various verification and integrity checks are performed, including, for example, network-based service usage measurements (for example, using IPDRs); activity monitoring; agent-based activity (for example, challenge / response queries); agent operating environment protection; monitor agent communications; agent cross checks; compare device-based and network-based measures (for example, service usage measures); dynamic software / agent download; and / or any combination of these and various other verification / integrity checking techniques described herein and / or evident from the various embodiments described herein.

In some embodiments, the device 100 may connect to more than one network and the device service policies are potentially changed based on which network the device is currently connected to. 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 (for example, policy control agent 1692), detects network connection changes and implements the service policies established for the second net.

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 may be pre-established by the service provider and / or the user and / or modified / adjusted later by any of the service provider and / or the user. For example, the cost function may be based on determining a minimum service cost, maximum network performance, whether or not the user or device has access to the network, maximize the service provider's connection benefit, reduce connections to service providers. alternative payment service, and / or any other criteria related to cost 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 the highest in A preference list. For example, the preference list can be established 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 (for example, by indicating in a pop-up window / dialog or other UI-based screen a notification, such as “You are not connected to the network Click here to learn more, get a free trial, use a session, sign up for service ”). In some embodiments, the notification content may be determined based on usage service patterns, stored locally and / or programmable logic on the device and / or a server (for example, device reports that the user is not connected and WWAN is available). Decisions about what dialogue to present and when they may be in pre-stored logic on the device.

In some embodiments, the service policies are automatically adapted based on the network to which the device 100 is connected. For example, the device may be a cell-based device connected to a macrocell, a microcell, a picocell or a femtocell (For example, 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 / or billing agent 1695 modify the count and / or billing of service usage based on whether the device is connected to a macrocell, microcell, picocell or femtocell. In some embodiments, the device recognizes what type of network it is currently connecting to (for example, by searching in a network or local table for the current connected base station, and / or the information is disseminated to the device after connection with the station base), that is, if it is a macrocell, microcell, picocell or femtocell. In other embodiments, the device does not recognize what type of network it is currently connected to, but reports its current base station, and the network uses a network search function to determine what type of network it is connected to. In some embodiments, the device adjusts billing based on the type of network to which it is connected, or in other embodiments, the device calculates compensation for such billing based on the type of network to which it is connected and / or other embodiments, the device records such service usage associated with the type of network to which it is connected and network billing can adjust billing accordingly. For example, billing may be lower for use of service data through a femtocell versus a macrocell. In some embodiments, the service policies are adjusted based on the type of network to which the device is connected, such as billing, user notification, data usage / bandwidth, regulation, time of day, who owns the cellular network connection (for example, the femtocell of the user's home, or the femtocell of the user's work, or a commercial business femtocell such as a cafeteria or any other common area such as an airport) and / or any other service policy that it may 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, service notification

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

user, use / bandwidth of data and / or any other service policy that may be different for a femtocell connection (or for any other type of connection, such as a macrocell, microcell or picocell). In some embodiments, service policies and / or billing policies are adjusted based on network congestion.

In some embodiments, if adaptive service policy control is not required, then policy control agent 1692 may simply pass instant service policy settings directly to the agents responsible for implementing instant service policies.

In some embodiments, a policy implementation agent 1690 implements traffic shaping rules and QoS policy for device 100. In some embodiments, policy implementation agent 1690 provides a firewall function. In some embodiments, policy implementation agent 1690 performs traffic inspection and characterization. In some embodiments, packet inspection is aided by literal or virtual application layer labeling while in other embodiments packet inspection is performed completely in / by policy implementation agent 1690. In some embodiments, the deployment agent Policy 1690 accepts service policy implementation settings from policy control agent 1692 or directly from service controller 122. More details on specific embodiments for policy implementation agent 1690 are provided below with respect to the figures associated with the communication stack and the communication protocol flow.

In some embodiments, the burst size, intermediate memory delay, acknowledgment delay and descent rate used in shaping upstream and downstream traffic are optimized in order to reduce network access traffic overhead, and use of excess capacity that can result in mismatches in traffic transmission parameters with MAC and PHY access network or over-network protocol packet delivery re-transmissions. In some embodiments, the application interface agent 1693 is used to literally label or virtually label application layer traffic so that the policy implementation agent or agents 1690 has the information necessary to implement selected traffic shaping solutions. As shown in Figure 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.

In some embodiments, the literal or virtual downstream application labeling is delayed until a traffic flow passes through the service policy implementation functions and the application interface function where the service flow is then identified and it is 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, before being associated with a literal or virtual tag, the traffic flow is allowed to pass without traffic conformation, and once the traffic flow is identified and labeled, the appropriate traffic conformation is applied. In some embodiments, a set of traffic shaping policy parameters is 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 may be blocked in 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 a policy. Once packet processing, frame alignment and encryption are eliminated.

In some embodiments, a service monitoring agent 1696 records and reports device service usage or service activities of the device 100. In some embodiments, the service usage history is verified by a number of techniques including verification against the history. of network-based service usage (for example, device service history 1618) and the various service policy implementation techniques as described herein.

In some embodiments, the service monitoring agent 1696 includes the ability to filter the generation of service usage history information with the decision on which aspects of the service history to report are being determined by policies that possibly include privacy policies defined by the user of the control plane device or servers in the network. In some embodiments, the service monitoring agent 1696 monitors and possibly records or generates Customer Resource Management (CRM) information such as websites visited, time elapsed by website, indications of interest based on website viewing. , ads served to the device, ads opened by the user, location of the user, searches performed by the user, application usage profile, usage history of device user interface, e-commerce transactions, music or video files played , applications on the 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 is recorded and used to determine the filtering policy for how many of CRM data inform (for example, CRM filter level options selected by the user through the device UI and / or through various service plan options or service profile or service policy) and how much to delete or not even monitor / register / store in the first

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

place. In some embodiments, to protect the privacy of this information related to GPS tracking / user location, the user is provided with options on how much of the information shared and the user's response to the options is recorded and used to determine the policy. of filtering for how many of the data related to GPS tracking / location to report (for example, GPS tracking filter level / location options) and how much to suppress or even not monitor / record / store in the first place. In some embodiments, service processor 115 allows the user to provide feedback on user preferences, such as for privacy / CRM data to be reported. In some embodiments, the user may also specify his preference or preferences for notification (for example, related to the use of service / cost, generation of traffic information and other service / monitored usage information) and / or service control. In some embodiments, the service monitoring agent 1696 observes and possibly registers or reports use of network categorized service including possibly roaming networks, paid service networks or free service networks. In some embodiments, service monitoring 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 service controller 122. The service is monitored through various embodiments that may involve service use registration or traffic inspection and usage registration at the application level, various levels. in the network interconnection communication stack or 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: data rate downstream and / or upstream traffic; 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 download or upload content types; traffic transmitted and / or received by mobile commerce transaction; traffic transmitted and / or received for one or more periods of time; traffic transmitted and / or received by different levels of network activity and availability of network capacity; traffic transmitted and / or received by one or more levels of quality of service delivered; 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 use or service activity that the user values or desires; traffic transmitted and / or received to support one or more third-party service partner offers from the service provider; software usage history; application usage history; device discovery history for UI components, applications, settings, tutorials; ad history served; history of visited ads; and / or device location history.

In some embodiments, some or all service usage monitoring takes place at the application layer. In some embodiments, the service monitoring agent 1696 implements traffic inspection points between the applications and the network interconnect stack application interface, such as the connector API. In other embodiments, the application interface agent 1693 performs traffic inspection and reports the results to the service monitoring agent 1696. Traffic inspection can be accomplished in several ways, including, for example, implementing a buffer T in each connection. connector and feed the secondary traffic into a traffic flow analyzer, which in combination with an application to connector mapping provides most of the information listed above. In cases where it is necessary to obtain traffic information from the application itself, some embodiments request that the application be adapted or provided to any of the application interface agent 1693 or the service monitoring agent 1696. As a For example, the application interface agent 1693 or the service monitoring agent 1696 can monitor and decode advertisements downloaded via HTTP, but if the browser and the HTTP server employ security above the connector protocol stack layer then the Application interface agent can communicate with the browser through a java applet or some other interprocess communication method. In some embodiments, the service monitoring agent 1696, the billing agent 1695 and / or the policy control agent 1692 (or some other software or hardware function in the device) can monitor and / or control (e.g., allow, block and / or replace) the flow of ad traffic on the device. In some embodiments, the monitoring and control of ad traffic flow on the device is also used to bill for account purposes (e.g., charges, such as service charges, billed to the advertiser, sponsor and / or service provider of service or transaction).

In some embodiments, some or all service use monitoring takes place below the application interface for the network interconnect stack. In this case, some of the information listed above may not always be available due to the encryption applied in the upper layers and / or the computational costs associated with performing deep packet inspection on mobile devices.

In some embodiments, the service monitoring agent 1696 also monitors the installation or loading systems of operating software, and / or otherwise monitors software installations or loads and / or software installations / uninstalls.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Some of the above information may be considered by some users, advocacy groups or agencies as sensitive personal information of the client. Simply sending the above information to the network for unspecified purposes, therefore, may not be acceptable to some service providers. However, if the user provides specific approval (for example, 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 use and the purpose for which the information is used. Accordingly, various embodiments described herein provide the user with control of what information is used and the purposes for which it is used thereby allowing the user to adapt the control of any sensitive information of this type. In some embodiments, information that is thought to be sensitive and is reported to the network must first receive user approval for the generation of information. Some basic information is generally not considered sensitive and is necessary for certain basic needs of the service provider. For example, total data transmitted and / or received, downstream and / or upstream traffic speed, overall traffic use per hour of the day in general are not considered private from the service provider's perspective and are required in many implementations of Basic service policy. As additional examples, perhaps another service usage history, such as downloads and uploads of total traffic emails but not the type of files or any specific details about email traffic, total web browsing traffic without any details 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 so that The service provider manages services. Conversely, information such as websites visited, content viewed, mobile commerce transaction completed, ads visited, GPS location history and other service usage history that the service monitor can record may be sensitive or private for some users and in this way would benefit from the various embodiments that provide enhanced user control of the generation of information from such potentially sensitive or private data. It should also be appreciated that there is an inherent advantage in implementing the monitoring of traffic, traffic, service monitoring or service control in a device, since it is not necessary to generate information of network sensitive information to achieve many of these implementation objectives of service policy

In some embodiments, the service monitoring agent 1696 assists in the labeling of virtual application of traffic flows through the implementation of network interconnect stack policy by tracking virtually labeled packets through stack processing and communication of the flow tags to the 1690 service policy agent or agents implementation. In some embodiments, the 1696 service monitoring agent 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 been connected. In some embodiments, this network activity summary includes a summary of the accessed networks, activity versus time per connection and / or traffic versus time per connection. In some embodiments, traffic reports that go to the network, possibly to service controller 122, billing system 1619 and / or device service history 1618, are filtered first according to rules defined by preference selection of user at the time of service activation (for example, service plan / service plan option selection), time of first use of the device, at a time when the user selected the option in the service UI or in a time when the user chooses to change the option in the service UI or some other time / mechanism that allows user preference selection.

In some embodiments, service monitoring agent 1696 monitors application usage (for example, which application the user runs on device 101, such as email applications, web browsing applications and / or streaming content applications). media). In some embodiments, the service monitoring agent 1696 monitors the use of multimedia files (for example, based on type of multimedia file and / or based on specific multimedia files, such as specific movies and / or songs). In some embodiments, the service monitoring agent 1696 monitors the device user interface, application and content discovery history (for example, monitor what 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 in the user interface on the device to access such applications / content and maintain such patterns and history, such as what icons the user accesses on a home page, secondary or other portion / mechanism in the device to access various applications / content). In some embodiments, the service monitoring agent 1696 monitors advertisements provided to the user on the device 101. In some embodiments, the service monitoring agent 1696 monitors advertisements viewed (eg, accessed, such as by clicking on a web ad ) by the user in the device 101. In some embodiments, the service monitoring agent 1696 monitors location / GPS information for the device 101. As will be appreciated by those skilled in the art, the service monitoring 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 location / GPS information. As described herein, in some embodiments, the user of the device 101 may also specify what activities the user authorizes for such monitoring (for example, the user may prefer not to allow such GPS / location monitoring).

In some embodiments, the application interface agent 1693 provides an interface for software programs.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

device application. In some embodiments, application interface agent 1693 identifies application level traffic, generates virtual service identification tag information, or appends literal service identification tags to assist in the implementation of service policy, such as access control. , QoS traffic conformation control, service-dependent billing or other service control or implementation functions. In some embodiments, the application interface agent 1693 helps with the monitoring of application layer service usage, for example, passively inspecting and recording the traffic or service features at a point in the software stack between applications. and the conventional network interconnect stack application interface, such as the connector API. In some embodiments, the application interface agent 1693 intercepts traffic between the applications and the conventional network stack interface API to more deeply inspect the traffic, modify the traffic, or shape the traffic (for example, thus not requiring any modification of the network interconnection stack / communication of the device OS device). In some embodiments, application interface agent 1693 implements certain aspects of service policies, such as application level access control, billing associated with application, monitoring or generation of application layer information, layer-based traffic shaping. application, billing dependent on type of service or other service control or implementation functions.

In some embodiments, monitoring and shaping of traffic based on the application layer can be performed as described below. Traffic from each application can be divided into one or more traffic flows that each flows through a traffic queue, each queue being associated with one or more additional classifications for that application (for example, the application can be a browser that is associated with multiple queues representing different destinations or groups of destinations to which it is connected, potentially having each destination or group of destinations different policies access control or traffic control, or the application can be associated with different types of content or groups of types of content having each type of content different queues, the application can be an email program with email text traffic that goes to a queue and downloads that go to another with different policies for each). In some embodiments, queues are formed for all applications or application groups that are associated with one or more traffic parameters such as destination, content type, time of day or application groups can be similarly assigned to different queues. The functions performed by the application layer queues may be similar to the functions described for the policy implementation agent, such as passage, blocking, buffering, delay, burst to control traffic or network access associated with the tail. The descent 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 retransmission of reliable lost information this may result in lost data or unreliable communication that It may be acceptable in some cases. The way in which queues are controlled can be constructed to result in a similar approach to controlling services or implementing service activity control similar to the other embodiments described herein, which include, for example, the control agent. policy 1692 that implements a higher layer of service control to achieve a higher level objective as discussed in this document.

In some embodiments, the application interface agent 1693 interacts with application programs to arrange application settings to help implement the implementation of service policy or application level billing, such as email file transfer options, options of interconnection network transfer files between peers, resolution settings or compression of media content and / or insert or modify browser headers. In some embodiments, application 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, application interface agent 1693 transmits or receives a proof of service usage to help verify the implementation of service policy, service monitoring or service billing. In some embodiments, the application interface agent 1693 performs a transaction billing interception function to assist the billing agent 1695 in transaction billing. In some embodiments, application interface agent 1693 transmits or receives a billing item to help verify transaction billing or service billing.

In some embodiments, a 1655 modem firewall blocks or passes traffic based on service policies and traffic attributes. In some embodiments, the 1655 modem firewall helps in virtual or literal upstream traffic flow labeling. Although not shown in Figure 16, in some embodiments, the 1655 modem firewall is located on either side of the modem bus and in some embodiments it is advantageous to locate it in the same modem.

In some embodiments, billing agent 1695 detects and generates service billing event information. In some embodiments, 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: it provides the user with service plan options, accepts service plan selections, provides options on service usage notification policies, accepts service specifications user preference over service usage notification policies, provides notification about service usage levels, provides alerts when service usage threatens to exceed plane limits to generate cost in

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

excess, provides service use control policy options, accepts service use control policy choices, informs the user preference policy control agent 1692 about service use control policy, provides transaction options billing and / or accept billing transaction choices. In some embodiments, billing agent 1695 interacts with transaction servers (for example, open content transaction partner sites 134) to perform e-commerce transactions with central billing 1619.

In some embodiments, service processor 115 includes one or more service usage counters or service activity. For example, the service monitoring agent 1696, billing agent 1695 or a combination of these agents and / or other service processor components / components 115 may include such a local service use counter or counters for the device 101. In some embodiments, a service usage counter monitors service usage that includes data usage to / from device 101 with access network 1610. In some embodiments, the service usage counter periodically, in response to a user request, in response to a request from service processor agent 115 (for example, billing agent 1695, policy control agent 1692 or another service processor agent 115), in response to service controller 122 and / or in response to central billing 1619 (for example, for billing purposes and / or for storing in device service history 1618), provides a us report or service, which includes monitored service usage for device 101. In some embodiments, the service usage counter periodically, or in response to a request, synchronizes the service usage counter on device 101 with a usage counter network service (and / or billing), such as that potentially maintained in central billing 1619. In some embodiments, service processor 115 uses the service usage counter to provide a service usage projection. In some embodiments, service processor 115 uses the service usage counter to provide an estimate of service usage cost. In some embodiments, service usage projections from policy control agent 1692 are used to estimate projected future service usage if the user's service usage behavior remains consistent. In some embodiments, the service processor 115 uses the service usage counter to provide a service cost usage, and the service processor 115 then periodically, or in response to a request, synchronizes the service usage cost with , for example, central billing 1619. In some embodiments, service processor 115 uses the service usage counter to determine if the user is exceeding and / or is projected to exceed his current service plan for data use, since Various actions can then be performed as described similarly in this document to allow the user to modify their service plan and / or modify (for example, regulate) their use of network data. In some embodiments, the service use counter may support providing the user with the following data / reports related to service use: service use, known use and estimated use, projected use, current costs, projected costs, roaming costs, cost for roaming options, and / or projected roaming costs. For example, including a local service data usage counter in the device 101 allows the service processor 115 to more accurately monitor service data usage, since, for example, the network service usage counters (and / or billing) may also not accurately include, for example, control plane data traffic sent to / from the device 101 in its 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 may include a wide range of verification techniques to ensure that the device is generating information properly from service billing events (for example, to verify / ensure that service billing is not functioning incorrectly and / or has not been handled / compromised so that it is not providing service billing information in a timely manner). As described herein, service billing generally refers to billing for one or more services for a device, such as device 101 (e.g., email service billing for data use associated with data related to email sent / received through the access network 1610, web browsing service billing for data use associated with data related to web browsing received / sent through the access network 1610 and / or any other network-based service, and / or any transaction-based service, such as for multimedia content purchases or other transactions).

In some embodiments, service invoicing based on a verifiable device is provided by sending dummy / test billing events, such as having an access control integrity server 1654 of service controller 122 that orders the access control integrity agent 1694 send a dummy billing event (/ test) to billing agent 1695. If the billing agent does not send the expected report, which should reflect the dummy (/ test) (or fails to timely send any report) , then the system can verify if the billing process is working properly. In addition, a fictitious (/ test) transaction can be used to verify transaction-based billing through a variety of approaches (for example, access control integrity agent 1694 can similarly send a transaction billing event dummy (/ test) to billing agent 1695 as a test to determine if billing agent 1695 below provides the expected report that reflects this dummy transaction (/ test) For example, test billing events can be trapped by a device-assisted billing mediation server and removed from the user's account billing.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, service invoicing based on verifiable device is provided by sending one or more bursts of data to the device to confirm that the data was received and to confirm that the service monitoring agent 1696 properly recorded the burst or bursts of data in the use of local service or service activity counter. In some embodiments, bursts of data may be used to verify data regulation (for example, if the device has exceeded service data usage limits and / or is approaching such limits so that the use of service data should be regulated , then it can be used to send bursts of data to verify if the expected regulation is being performed properly on the device). In some embodiments, service invoicing based on verifiable device is provided by issuing requests to connect to an unauthorized service / website to verify if that use of unauthorized service is properly blocked. In some embodiments, service invoicing based on verifiable device is provided by issuing requests to perform an unauthorized transaction to verify if that unauthorized transaction is properly locked.

In some embodiments, service invoicing based on verifiable device is provided by verifying device service activities related to IPDRs for the device. In some embodiments, IPDRs for the device (possibly in a modified format) are sent periodically and / or upon request to the device, as described herein. For example, the IPDRs for the device can be compared to the device's local service data usage counter and / or the service plan so that the device determines whether the global service data usage limit has been exceeded, if they have been performed by the device websites / other services outside the plan / unauthorized / unregistered, if the bandwidth limits of the plan / service profile have been exceeded, if transactions outside the plan / unauthorized / unregistered ( for example, verify IPDR transaction records, assuming that such are included in the IPDRs, with the device's local transaction records to determine, for example, if the local device records indicate that they were purchased less than the registered network number of content downloads, such as downloaded songs), and / or if any other verifiable activities based on an IPDR comparison indicate that the device has been used d e in any way that is outside or exceeds the service plan / profile for the device.

In some embodiments, the device-based service billing includes the record billing option response history. For example, this approach may be particularly important for conditions of additional service plan use (for example, when the use of the device is exceeding the service plan associated with the device in some way, such as use of service data, width band, service or transaction access and / or some other way). In some embodiments, in a condition of additional use of the service plan, the user is requested to confirm that the user has notification with acknowledgment of receipt of the additional use of the service plan, such as through the user interface 1697. In some embodiments , such acknowledgments for additional use of the service plan require the user to enter a unique identification to validate the authorization for the identity of the user associated with the device (for example, another type of verification mechanism, in the event that steal a device or is being used by someone other than the authorized user of the device, then that unauthorized user could not confirm the acknowledgment of additional use of the service plan, and then appropriate actions can be taken, such as regulation, quarantine or suspension (temporarily) of the network service / access). In some embodiments, if the device is compromised / hacked (for example, by the user of the device), and the device is used in a manner that results in an additional use of service use (for example, determined based on monitoring of device-assisted service use, and / or network-based service usage monitoring using IPDR / CDR), then the billing system determines to bill for such additional service usage costs. This additional use billing can be initiated by the device 100 (for example, service processor 115), service controller 122, billing system 123, AAA 121, or some other network function. In some embodiments, if the device is compromised / hacked (for example, by a user of the device), and the device is used in a manner that results in additional use of service use, one or more of the following actions: the user is notified, the user is requested to acknowledge the notification, the device traffic is sent to the SPAN (or similar traffic sampling and analysis function) and / or the device is labeled for further analysis .

In some embodiments, device-based service billing includes an option to bill per account, such as billing different service activities and / or transactions to a specified account (for example, other than the user account associated with the service plan general for the device). For example, billing by account can provide billing according to the application, content type, website, transaction, network communication (for example, operation indication 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 sponsored transaction partner activities and then report such invoice information on account for billing mediation / reconciliation. For example, an invoice report per account can be sent by the billing agent 1695 from the device to the central billing 1619 (for example, as a billing event); or alternatively, sent from an intermediate server / aggregator, which can then reformat and send the reformatted report to central billing 1619 (for example, by providing the billing report in a format required by central billing 1619); or alternatively, send to a mediation server, which can recalculate billing based on the invoice report per account (for example, offset the invoice based on network communications, transaction-based billing, activities

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

sponsored by transaction partner, content providers, website providers and / or ad providers) and then send the recalculated (and potentially reformatted) report to central billing 1619.

In some embodiments, one or more of the mediation / reconciliation functions for device-assisted billing, device-generated billing events, device-generated billing for account events, and device-generated open billing events may be implemented in the controller. of service 122 (for example, billing event server 1662) or at another function located in billing system 123 or elsewhere. This mediation server function accepts device-based billing events analyzed immediately above, reformats billing events in a format accepted and recognized by the billing system, mediates billing event information to eliminate service usage billing. the user's account and place it in other categories of invoice per account as appropriate in accordance with the rules of invoice mediation per account, add other billing events for service use or transactions to the user's account as appropriate in accordance with the device-based billing rules, and then apply the information to the billing information of the user account to correct or update the account.

For example, one bill per account may allow a website provider, such as Google or Yahoo, to pay for or compensate for certain account usage by web browsing, web-based search, web-based email, or any other activities of service use or web-based, which may also be based (in whole or in part) on the activities performed by the user in such transactional services (for example, based on display / access of advertisements or activities through click by the user, by means of which an advertising business model used by such website providers directly or indirectly supports such service account subsidies). As another example, an invoice per account may allow an advertiser to pay for or compensate for certain account usage by viewing and / or accessing (for example, clicking through) an ad placed on the web or another advertisement sent via the network at device. As another example, various network communications (for example, use of network data related to operation indication and other services related to network communications) can be assigned to a fictitious account and this can be used to offset the invoice and / or be used to track the use of data for such activities for the device. In another example, the use of service data for access to a transactional service, such as a multimedia content download service (e.g., music, e-book, streaming music / video, and / or movie or other service multimedia content download), or an online shopping site (for example, Amazon, eBay or other online shopping site), can be billed to a transaction service account assigned to a transactional service partner that sponsors access to that transaction service of the sponsor, thus allowing the transaction service partner to pay for or compensate (for example, subsidize) the use of an account for such activities, which may also be based (in whole or in part) on the transactions actually made by the user in such transactional services (for example, based on the volume / cost of purchases of multimedia service download 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 (eg, central billing 1619). In some embodiments, device-based service billing includes reporting service usage events and / or applying registration service billing updates / generating cost search information. For example, this allows not only the service use to be reported but also the cost of such service use to the user through the user interface of the device 101. Also, for example, the cost of such service use can also be reported to the service server. billing. In some embodiments, device-based service billing includes reporting the use of service to the network, and the network determines the cost for such service use.

In some embodiments, billing information is provided for roaming partners. For example, a roaming server may include a roaming service cost data table for roaming service partners. In this example, when the device (for example, device 101) is connected to a roaming network provided by a roaming service partner, then the device can also receive the roaming service data rate based on the table of Roaming service cost data provided by the roaming server. Alternatively, the roaming server can send the roaming service cost data table (or a modified format thereof) to the device to thereby allow the device to determine the costs for such use of network service or activity Roaming service. As described herein, the device may also automatically use a roaming service profile when connected to the roaming network service and / or the user may be notified of the roaming service profile options based on the costs of Roaming service data and then select the desired roaming service profile accordingly.

In some embodiments, the user is provided with a service cost list based on the locally stored roaming table and a search for available roaming partners that the device 100 detects and to which it can connect. 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

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

set of options for service use notification, control or regulation of service use and / or cost while roaming (for example, using service notification and cost control techniques, as similarly analyzed herein document, but apply to the roaming network). In some embodiments, these controls are set by a VSP (or, for example, an IT manager using the VSP functions). In some embodiments, roaming tables in the background are periodically updated while on a home network (or other low-cost network) and cached. In some embodiments, cache updates take place based on a set period of time (for example, late at night when updates are less expensive due to network inactivity). In some embodiments, roaming partner cost table cache updates are made each time they are connected to a desirable network that is not expensive or of restricted bandwidth (for example, at home, work or outside the network). WWAN). In some embodiments, the updates take place at the time of day that the network is not busy. In some embodiments, the updates take place based on the network insertion capability when the roaming table is changed (for example, one or more of the roaming partners change the rate). In some embodiments, the service cost to update the roaming service cost table is charged to invoice per account and possibly not charged to the end user. In some embodiments, the roaming service center is provided as a service for which it is paid (for example, potentially the bill per account tracks all related costs). For example, this type of roaming cost control can be provided as a service through the central provider, MVNO, roaming partner provider, VSP or as a third-party application not associated with any service provider (for example, service manager YOU). For example, controls for how to update the cache, set service control policies and other controls can be defined by any number of VSP entities that include 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 service cost list based on a locally stored roaming table (or accessed remotely). 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 to control / regulate the use and / or cost while roaming. In some embodiments, these controls are set by a VSP (for example, an IT manager that uses VSP functions). For example, roaming tables can be periodically updated in the background while on a home network and cached. In some embodiments, caching updates takes place based on a set period of time. In some embodiments, roaming partner cost table cache updates are made each time the device connects to a desirable network that is not as expensive or restricted bandwidth (for example, at home, work and / or outside the WWAN). In some embodiments, the updates take place at the time of day when the network is not busy. In some embodiments, the updates take place based on a network insertion capability when a roaming table is changed (for example, one or more of the roaming partners changes the rate). In some embodiments, the service cost for updating the roaming service cost table is charged to invoice per account and possibly not charged to the user. In some embodiments, the roaming service center is provided as a service that is paid by the user and / or part of a service plan. In some embodiments, an invoice per account function tracks all related costs. For example, the roaming service center can be provided as a service through the central provider, MVNO, roaming partner provider, VSP or as a third-party application not associated with any service provider (for example, the IT manager ).

In some embodiments, a synchronized local service usage counter is provided based on central billing information with time indication. For example, the local service usage counter, as described similarly above, can also be synchronized to past service usage records (e.g., central billing records with indication of service usage time for the device ) and use local estimates for current / present service usage estimates for the device. In this example, the central billing system (for example, central billing 1619) can insert the central billing information with time indication to the device (e.g., device 101), the device can extract the central billing information with indication of time, and / or an intermediate server can provide a mediated insertion or extraction process. In some embodiments, synchronization is performed periodically based on service usage levels with estimates between free-running 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, the projected service usage can be calculated on the device or calculated on a server (for example, a billing server or an intermediate billing server), which provides the projected service usage information calculated to the device, such as using various adaptive algorithms for service usage projections. For example, an adaptive algorithm may use historical / past synchronized network service usage information (for example, synchronized with local service usage data based on time indications associated with IPDRs) to aid in service usage projections. , based on, for example, the total service usage count, service usage count by certain service related criteria (eg, application, content, type of service, website and / or time of day). In another example, an adaptive algorithm synchronizes data from

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

past service usage (for example, the local estimate of past service usage data is updated so that it is synchronized to the point in time associated with the last IPDR time indication received) and estimates are then added current service usage premises collected since the last time indication to the IPDR service usage counter with time indication to minimize service usage counter compensation so that it is not greater than the difference between the usage measure of network service and the measure of local service usage since the last IPDR time indication. In some embodiments, these adaptive algorithm techniques are performed on the device and / or performed on the network (for example, on a network server) for processing. In some embodiments, if there is compensation 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 used to estimate any sources Systematic compensation and correct local service usage count to minimize compensation. As an example, if the IPDR service usage count is typically disabled at a fixed, high or low percentage, then an algorithm can be used to estimate a multiplier that is applied to the local service usage count to minimize compensation between events. IPDR service usage synchronization. In another example, there may be a consistent constant compensation and a multiplier compensation, both of which can be estimated and corrected. Those skilled 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 use activities or network communication 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 statistical service usage patterns to provide more accurate service usage projections. Those skilled in the art will also appreciate that a variety of additional adaptive algorithm techniques can be used including those that provide various statistical analysis techniques and / or other techniques.

In some embodiments, the use of service is projected for the end of a billing / service period for a service plan versus the use of service allowed under the service plan for that billing / service period. A presentation of excess charges is also provided for the projected service usage rate based on the service usage behavior monitored through the end of the billing / service period (for example, this may be zero if the service usage is projected to be less than allowed under the service plan and a positive cost number if projected to be greater than the service plan). For example, this can be implemented in various ways, such as on a server on the network, on a gateway / router / switch on the network, and / or on the device, as discussed below and described in general herein. document with respect to other monitoring and service usage / cost notifications. If it is implemented on the network server or gateway / router / switch, then service / cost usage projections and related information can be inserted into the device, or the device can be notified that such information is available for extraction and / or inserted / removed periodically. Information / service usage estimates may be collected from the device, the network or both (for example, reconciled and / or synchronized) as described similarly in this document. The service usage information / estimates are analyzed below to determine projections of service usage / costs as described similarly in this document and compared to the service plan for the device to determine the additional use of service usage. / projected cost (if any). In some embodiments, one or more of the following is determined by, reported and / or displayed on the device: service use value, projected service use value, service use plan limit, additional use use of projected service, additional use of projected service cost, duration of service plan period time, remaining service plan time before end of period and / or other relevant information.

In some embodiments, the device also determines the cost of services based on the synchronized service usage count that allows the device to also report the service cost information to the user. For example, the device can store a service cost search table or tables locally, store different service cost search tables locally for different networks and / or for roaming networks, and / or request such information from a data server. Billing or intermediate billing (and / or a roaming server) on the network. As another example, the device can obtain the service cost calculated based on the synchronized local service usage count and / or the network service usage count from an intermediate server (for example, a billing or intermediate billing server ) downloading in this way the computational costs associated with these calculated projections and data storage for the service cost search tables on the intermediate server in the network using the network service usage counter with or, alternatively, without the synchronized local service usage counter.

In some embodiments, categorization of service usage count is provided by the network (for example, a home network (such as a Wi-Fi, WAN, femtocell, or other home network) versus a roaming network). Similarly, the synchronized local service usage counter can be synchronized over the network. Also, a synchronized local service usage count can be similarly provided for networks controlled by a central provider, for networks controlled by other providers (eg, MVNO) and / or free networks.

In some embodiments, a service and billing notification interface is provided. For example, the use

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

of service and the use of projected service, as described herein, may be presented to the user of the device (for example, via the user interface 1697). Similarly, the exceeding / additional use of service or expected / projected cost, as described herein, may also be presented to the user. As another example, a more cost-effective cost plan can be determined / projected based on the use of historical and / or projected service, and this determined / projected more cost-effective cost plan can be presented to the user. In another example, a list of available networks accessible by the device may be presented to the user. In this example, one or more unwanted available networks can also be blocked from the presentation thus presenting only the desired and / or preferred available networks to the user. In this example, service usage plans and / or the service usage plan option comparison for one or more alternative networks or roaming networks may also be presented to the user. Similarly, service cost plans and / or the service plan / cost option comparison for one or more alternative networks or roaming networks may also be presented to the user. In addition, the use of roaming service, use of projected roaming service, estimated roaming service cost and / or projected estimated roaming service cost may also be presented to the user. This use of roaming service / costs can also be presented to the user so that the user can use this information to select various roaming service billing options. In another example, alternative and / or minimum cost networks are determined and presented to the user. In another example, alternative warnings are presented to the user for any specified roaming network.

In some embodiments, the service and billing notification interface notifies the user of the expected network coverage (for example, based on the current geography / location of the device and the networks accessible to the device from that current geography / location) and presents options to the user based on the expected network coverage information. In some embodiments, the service and billing notification interface notifies the user of their current service usage at specified service usage points and presents various options to the user (for example, service usage options and / or billing options) . For example, user responses to the presented options are recorded (for example, they are stored locally on the device at least temporarily for information generation purposes or permanently in a local configuration data store until such configuration settings are modified or reset in another way) and be informed, such as the billing server (for example, central billing 1619). For example, user input, such as selected options and / or corresponding policy settings, can be stored locally on the device through a cache system. As another example, the service and billing notification interface presents options to the user for how the user wishes to be notified and how the user wishes to control the costs of service use, the user's input on how such notification options are recorded , and cost control options (for example, billing agent 1695 and policy control agent 1692) are configured accordingly. Similarly, user input on service plan options / changes can be registered, and service plan options / changes (for example, billing agent 1695 and policy control agent 1692) are configured / updated in consecuense. In another example, the service notification and billing interface provide various traffic control profiles, such as when the user requests assistance in controlling the costs of service use (for example, use of service data and / or activities / costs related to transaction use). Similarly, the service notification and billing interface can provide various notification options, such as when the user wants to warn in advance about service coverage. In another example, the service notification and billing interface provides options for automatic pre-purchase at a set point in service usage. In another example, the service and billing notification 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 to allow the user to select and / or update policy settings. For example, user input provided through the online portal / web server can be registered and reported to the billing server (for example, central billing 1619). In another example, the online portal / web server may submit transaction billing information and / or accept the entry for a transaction billing request, which can then be reported to the billing server accordingly.

As shown in Figure 16, service processor 115 includes a service interface or user interface 1697. In some embodiments, user interface 1697 provides the user with information and accepts user choices or preferences in 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, warnings of possibility of additional use of service use, service cost status, projection of service costs, service use control policy options, privacy-related options / CRM / GPS and / or other service-related information, settings and / or options. For example, the user interface 1697 may collect service usage information from the service monitoring 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 the user interface service usage information or service cost to present to the user. As another example, the service billing records obtained from the central billing system 1619 can be used to synchronize the information of local service usage counters and the service agent.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

1696 service monitoring for real-time updating of the local service usage counters between the synchronizations of the 1619 billing system. As another example, the user interface 1697 can present options and accept user preference feedback, as is It has similarly analyzed previously with respect to user privacy / CRM / GPS filtration, traffic monitoring and service controls. For example, the user interface 1697 may allow the user of the device to modify their privacy settings, provide user feedback about service preferences and / or service experiences, modify their service profiles (e.g., preferences, settings, settings and / or network settings and options), to review service usage data (for example, based on local service usage counters and / or other data monitored by service processor 115), to receive various events or triggers ( for example, based on service use / projected costs), and / or the user interface 1697 may provide / support various other user input / output for service control and service use.

In some embodiments, providing the service policy implementation and the service policy implementation control to the user's preferences, and / or providing the user with the option to specify or influence how the various service notification policies are implemented and control or control algorithms, the user is provided with options for how to control the service experience, the cost of service, the capabilities of the service, the way in which the user is notified regarding the use of service or cost of service, the level of sensitive user information that is shared with the network or service provider entity, and the way in which certain service use activities may or may not be driven, regulated, blocked, activated and / or otherwise controlled . Therefore, some embodiments provide service control to beneficially optimize user cost versus service capabilities or capabilities in a way that facilitates an optimized user experience and does not violate network neutrality objectives, regulations and / or requirements. . For example, offering the user with a set of choices, which vary from simple choices between two or more options for pre-packaged service control settings to advanced user screens where the level of user specification and more detailed 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 about which service use activities are controlled, such as how they are controlled or regulated and what service use activities may not be regulated or controlled in any way. These various embodiments allow the service provider, device manufacturer, device distributor, MVNO, VSP, service provider partner or other "entity" to help the user manage services in a network-neutral manner with respect to their implementation and service control policies, since the user is making or influencing decisions, for example, in cost versus service capabilities or quality. By additionally providing user control or influence over the filtering settings for the generation of service usage information or CRM information generation, 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 Figure 16, service processor 115 includes service downloader 1663. In some embodiments, service downloader 1663 provides a download function for installing or updating service software elements in the device. In some embodiments, the 1663 service downloader requires a signed version of software before a download is accepted. For example, the download may require a unique key for a downloader of a particular service 1663. As another example, the service downloader 1663 may be stored or run in secure memory or run a secure memory partition in the CPU memory space. Those skilled in the art will appreciate that there is a variety of other security techniques that can be used to ensure the integrity of the 1663 service downloader.

As shown in Figure 16, service processor 115 includes a modem controller 1640. In some embodiments, modem controller 1640 converts data traffic into modem bus traffic (not shown) for one or more modems by means of the 1655 modem firewall. As shown in Figure 18, in some embodiments, modem selection and control 1811 selects the access network connection and is in communication with the 1655 modem firewall, and modem controllers 1831, 1815 , 1814, 1813, 1812 convert data traffic into modem bus traffic for one or more modems and are in communication with modem selection and control 1811. As shown in Figure 21, in some embodiments, modems 2141 , 2125, 2124, 2123, 2122, which are in communication with the modem bus 2120, connect the device to one or more networks. In some embodiments, different profiles are selected based on the selected network connection (for example, different service / policy profiles for WWAN, WLAN, WPAN, Ethernet and / or DSL network connections), which are also referred to herein as document as multimode profile setting. For example, the service profile settings may be based on the actual access network (for example, DSL / home 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 seen as different from accessing a Wi-Fi network in the cafeteria. For example, in a Wi-Fi hot spot situation where there is a significant number of users on a DSL or T-1 backlink, the service controller can act in a service provider cloud or a cloud of MVNO, service controls can be provided by a VSP capability offered by the service provider.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service (for example, as described herein with respect to Figure 49) or it may be owned by the service controller by the hot spot service provider using the service controller itself without any association with a provider of network access service. For example, service processors can be controlled by the service controller to divide the available bandwidth at the hot spot according to the QoS or user sharing rules (for example, with some users having a higher differential priority (potentially for payments) of superior service), than other users). As another example, environment services (as similarly described herein) can be provided for the hot spot for verified service processors.

In some embodiments, service processor 115 and service controller 122 may assign multiple service profiles associated with multiple service plans that the user chooses individually or in combination as a package. For example, a device 100 starts with environment services that include free transaction services in which the user stops for transactions or events instead of the basic service (for example, a news server, an electronic reader, PND service, Internet pay per use session) in which each service is supported with an invoice capacity per account to correctly account for any subsidized partner billing to provide transaction services (for example, Barnes and Noble can pay for the electronic reader service and offer a revenue share to the service provider for any book or magazine transaction purchased from device 100). In some embodiments, the billing service per account may also track transactions and, in some embodiments, announcements for the purpose of revenue sharing are disclosed in this document, using all service monitoring capabilities. After starting the services with the free environment service discussed above, the user can later choose monthly post-paid Internet, email and SMS service. In this case, the service controller 122 would be obtained from the billing system 123 in the case of network-based billing (or in some embodiments the billing event server 1622 of the service controller 122 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 (for example, policy management server 1652) to find the appropriate service profile for the new service in combination with the initial environment service. The new superset service profile is then applied so that the user maintains free access to the environment services, and the billing partners continue to subsidize these services, the user also obtains access to Internet services and can choose the profile of service control (for example, from one of the embodiments disclosed in this document). The profile superset is the profile that provides the combined capabilities of two or more service profiles when the profiles are applied to the same service processor of the device 100. In some embodiments, the device 100 (service processor 115) can determine the profile supersetting instead of service controller 122 when more than one "stackable" service is selected by the user or is otherwise applied to the device. The flexibility of the embodiments of the service processor 115 and the service controller 122 described herein allows a wide variety of service profiles to be defined and applied individually or as a superset to achieve the desired service characteristics of the device 100 .

As shown in Figure 16, service controller 122 includes a service control server link 1638. In some embodiments, device-based service control techniques that involve monitoring across a network (eg, in the control plane) are more sophisticated, and for this it is increasingly important to have an efficient and flexible control plane communication link between the device agents (for example, of the service processor 115) and the network elements ( for example, of service controller 122) that communicate with, control, monitor or verify service policy. For example, the communication link between the service control server link 1638 of the service controller 122 and the service control device link 1691 of the service processor 115 can provide an effective and flexible control plane communication link , a service control link 1653 as shown in Figure 16, and, in some embodiments, this control plane communication link provides a secure communication link (eg, encrypted) to provide secure, bi-directional communications between the service processor 115 and service controller 122. In some embodiments, service control server link 1638 provides the network side of a system for transmitting and receiving service agent to / from network element functions. In some embodiments, the traffic efficiency of this link is enhanced by storing intermediate memory and aligning multiple agent messages in the transmissions (for example, thereby reducing network communication). In some embodiments, traffic efficiency is further improved by controlling the transmission frequency and / or by linking the transmission frequency to the rate of service use or traffic use. In some embodiments, one or more levels of security and / or encryption are used to secure the link against potential discovery, clandestine listening or compromise of communications on the link. In some embodiments, the service control server link 1638 also provides the communication and operation indication timing link for the agent operation indication function. As discussed below, various embodiments described herein for the service control server link 1638 provide an effective and secure mechanism for transmitting and receiving service policy implementation, control, monitoring and verification information among the agents of device (for example, service processor components / agents) and other network elements (for example, service controller components / agents).

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, the service control server link 1638 may emulate the opposite part of the secure service control plane transmission methods discussed above with respect to the service control device link 1691. For example, one can use a or more security layers to secure the communications link, which includes, for example, basic IP layer security, TCP layer security, service control link layer security, and / or specific security from controller servers of service to service processor agents.

In some embodiments, the service control server link 1638 reduces network communication by effectively transmitting the communications related to the service control through the link. For example, the service control server link 1638 can transmit server messages asynchronously as they arrive. As another example, the service control server link 1638 can perform collection or storage of server messages between transmissions. As another example, 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, wait until a certain amount of service use or use has taken place. traffic, respond to a service agent message, respond 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 taken place, the service control server link 1638 can take all agent communications stored in buffer and frame communications. In addition, the service control server link 1638 can provide an effective communication link based on various embodiments related to the timing of transmissions through the service control link, as similarly discussed above with respect to the description. of service control device link 1691. For example, timing functions, such as asynchronous messages or interrogation of messages, constant frequency transmission, transmission based on how much service use or use of service can be determined, controlled and / or initiated. data traffic has taken place, transmission in response a control link message from the device side, service verification error events, other error events and / or other message transmission trigger criteria, by either side of the device or network side depending on the realization.

In some embodiments, the service control server link 1638 provides secure, signed, encrypted and / or otherwise protected communications before sending such communications through the service control link 1653. For example, the service link 1638 service control server can send to the transport layer or directly to the link layer for transmission. In another example, the service control server link 1638 additionally ensures communications with transport layer encryption, such as TCP TLS or other transport layer protocol. As another example, the service control server link 1638 can be encrypted at the link layer, such as using IPSEC, various possible VPN services, other forms of IP layer encryption and / or other layer encryption technique. link.

In some embodiments, the service control server link 1638 includes the agent operation indication function in which the agents provide certain required reports to the service processor for the purpose of implementing service policy verification or for other purposes. . For example, the operation indication function can also be used to issue queries or challenges, messages, service settings, service control objectives, requests or interrogation of information, error checks and / or other communications to agents. As another example, agent operation indication messages may be open or encrypted, signed and / or otherwise secured. The additional function indication function and the content of operation indication messages may be provided as described similarly herein, as described above with respect to the service control device link 1691 and the service agent. 1694 access control integrity and other sections. In some embodiments, the service controller 122 and / or the agents of the service controller 122 are programmed to periodically provide reports, such as after an operation indication response (for example, an agent may repeatedly send necessary reports in each indication of operation), and appropriate actions can be taken based on such reports received. Accordingly, the function of indication of operation provides an important and effective system in various embodiments described herein to verify the implementation of service policy and / or protect against engagement events. There are many other functions that the agent operation indication service can perform many of which are discussed in this document, while others will be apparent to a person skilled in the art given the principles, design background and various embodiments provided in the present document

In some embodiments, the service control server link 1638 also provides a service control software download function for various embodiments, which, for example, may include a download of new service software items, service item reviews. service software, and / or dynamic refreshments of service software elements of service processor 115 in the device. In some embodiments, this function is performed by the service control server link 1638 which transmits the service control software as a single file through the service control link. For example, the file may have encryption or encryption signed beyond any provided by the same communication link protocol for service control link 1653. In another example, the software files of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Service control can be segmented / divided into smaller packets that are transmitted in multiple messages sent through the service control link 1653. In another example, the service control software files can be transmitted using another delivery mechanism, such as a direct TCP connector connection from a 1660 service download control server, which may also involve secure transport and additional levels of encryption. In some embodiments, the service control server link 1638 and / or the service download control server 1660 uses or uses an agent serial number and / or a security key search when the agents are updated and / or when a dynamic agent download takes place.

As shown in Figure 16, service controller 122 includes an access control integrity server 1654. In some embodiments, access control integrity server 1654 collects device information about service policy, service usage, agent configuration and / or agent behavior. For example, access control integrity server 1654 may cross-check this information to identify integrity gaps in the service policy implementation and control system. In another example, the access control integrity server 1654 may initiate actions when a service policy violation or a system integrity breach is suspected.

In some embodiments, access control integrity server 1654 (and / or some other service controller agent 122) acts on access control integrity agent reports and error conditions. Many of the 1654 access control integrity agent checks can be achieved by the server. For example, the checks for the access control integrity agent 1654 include one or more of the following: service usage measure against policy-consistent use interval (for example, usage measure from the network and / or from the device ); agent configuration; agent operation; and / or dynamic agent download.

In some embodiments, access control integrity server 1654 (and / or some other service controller agent 122) verifies device service policy implementations by comparing various service usage measures (e.g., network-based monitored information , such as 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 may include measuring total past data, data passed over a period of time, IP addresses, data per IP address and / or other measures such as location, downloads, email access, URL and compare such expected service usage behavior from the measures given to the policies that are intended to be in place.

In some embodiments, access control integrity server 1654 (and / or some other service controller agent 122) verifies the device service policy, and verification error conditions that may indicate a mismatch in service measure and the service policy includes one or more of the following: unauthorized network access (for example, access beyond the environment service policy limits); unauthorized network speed (for example, average speed beyond the service policy limit); amount of network data does not match policy limit (for example, device does not stop at limit without re-arranging / reviewing service policy); unauthorized network address: use of unauthorized service (for example, VOIP, email, and / or web browsing); use of unauthorized application (for example, email, VOIP, email, and / or web); service usage rate too high for the plan, and policy controller does not control / regulate it downwards; and / or any other mismatch in terms of service and service policy.

In some embodiments, the access control integrity server 1654 (and / or some other service controller agent 122) verifies the device service policy based at least in part on, for example, various error conditions indicating a mismatch in service measure and service policy. For example, various verification error conditions that may indicate a mismatch in service measure and service policy include one or more of the following: mismatch in a service measure and another service measure; agent failure to generate information; agent failure to respond to queries (for example, challenge-response sequence and / or expected periodic agent information generation); agent failure to respond correctly to challenge / response sequence; inappropriately configured agent; agent failure in self checks; agent failure in cross checks; unauthorized agent communication or attempted unauthorized communication; failure to test service policy implementation; failure to generate service usage information test; failure to invoice proof of service usage; failure in proof of transaction billing; download sequence failure; environment engagement event, such as loading or execution (or attempt) of unauthorized software, access (or attempt) of unauthorized memory, access (or attempt) of unauthorized agent, known harmful software and / or signing of harmful communications known; and / or failure to respond to various messages, such as sending message and suspension and / or sending message and entering quarantine. In some embodiments, the access control integrity server 1654 (and / or some other service controller agent 122) verifies the device service policy by performing automated queries and analysis, which are reported below (for example, results of Abnormal / suspicious reports may be reported for further analysis by a responsible person to determine whether such activities indicate activities outside of policy or to provide information to the user to inform the user of such anomalous / suspicious report results that may indicate activities outside of policy). For example, the user can review the report to authorize if such

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

activities were performed by the user (for example, website access requests, specific transactions and / or phone calls) and / or indicate that such activities were not authorized by the user (for example, indicate a potential commitment of the device, such such as by malicious software or other unauthorized use of software / user of the device). In another example, the user can also connect to communicate with the service support of the service provider regarding such informed activities (for example, by text / chat, voice / telephone, and / or video conference to a service support ). Accordingly, in some embodiments, access control integrity server 1654 (and / or some other service controller agent 122) provides a policy / service control integrity service to continuously verify (for example, periodically and / or based on trigger events) that the service control of the device has not been compromised and / or is not behaving outside the policy.

In some embodiments, after the detection of one or more service verification errors, such as the various service verification errors discussed above, the device is directed to a quarantined network state 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 and routing restrictions can be achieved with the AAA access network and the routing system (for example, the 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 achieved with device-based access control or traffic control policy implementation. The quarantine network equipment or servers can be located, for example, within the access network or within another network with access to the access network. Communication with the quarantine network infrastructure can be achieved, for example, with a secure link with one or more levels of encryption or a specialized private link. In some embodiments, quarantining a device includes, for example, a two-stage process for routing quarantine network device traffic, first, to a quarantine traffic management router or server and, secondly , from there to the real quarantine network infrastructure, the route being determined by device parameters, user parameters, access service provider parameters or other parameters associated with the quarantine network routing. In some embodiments, the device is completely suspended from the network in which, for example, the device may first issue a user interface message to the user or issue another form of a message to the user or service subscriber, such as by email, message printed on paper and / or voice message. In some embodiments, 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 on the device and / or on the network. For example, implementing a device quarantine (for example, using a RADIUS server to quarantine the device) may involve assigning the device to a different billing profile.

In some embodiments, after the detection of one or more service verification errors, such as the various service verification errors discussed above, the switch-based port analysis is performed to further monitor the device (for example, referred to as Analyzer Switching Ports (SPAN) on Cisco switches, and various other providers have different names for it, such as Itinerant Analysis Port (RAP) on 3Com switches). In some embodiments, the behavior of the device service policy implementation is monitored at a deeper level in the network by copying the device traffic to the switch so that it goes to both an intended data path destination and a port. specified for switch-based port analysis (for example, traffic content can be analyzed and recorded using deep packet inspection (DPI) techniques, which can provide a more precise level of detail than typical IPDR). For example, an advantage of performing a switch-based port analysis function is that traffic does not need to be analyzed in real time, and a sample subset of the devices in the network can be selected for such analysis based on, for example, any of identifying devices that have suspicious service policy implementation behavior and / or a regular sampling algorithm that eventually samples all devices, or some other selection approach. As another example, a planned switch-based port analysis can be applied that eventually rotates across all devices and designates a higher priority in the sampling queue for the devices that are suspected.

In some embodiments, switch-based port analysis allows for offline or non-real-time DPI sampling, as described above, as a verification measure for device-based service control measures that are implemented. In some embodiments, sophisticated IPR techniques are used to enhance the content of IPDRs so that they provide detailed information that can be made available on the network. For example, some of the IPR packet analysis may be redundant between the device and the network, although this approach provides a much higher resolution validation for the device-based service and less device-dependent 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, aggregator base station, aAa server group or any other hardware or hardware / software system) located on the network where network level traffic inspection is achieved, or on one or more integrated servers to operate from one

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

coordinated way with the IPR 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, aggregator base station, AAA server group or any other hardware or hardware / software system located on the network that provides deep service control capability (for example, using DPI techniques) for devices that have some or all of the functions of the service processor installed and, in some embodiments, also provide more coarse network control of the basic details for devices that do not have a service processor installed in the device (for example, such more coarse network control functions include rate of maximum data and / or maximum total data).

In some embodiments, the SPAN function is used in a periodic rotating manner as well as to increase CDR data with deeper packet information for the purpose of service usage measures based on point checking device. Examples of when this may be beneficial include point check network address access policies, point check environment access policies, point check billing event reports, intermediate network interconnect device / device count endpoint point check (by checking the source or destination addresses, token, cookies or other credentials, etc.). For example, the periodic SPAN may plan for all devices equally, for certain devices or users with higher SPAN priority, frequency or depth than others, higher priority, higher frequency, or immediate priority for devices with higher usage patterns or usage patterns Unusual, immediate or very high priority for devices with a policy violation status.

In some embodiments, a combination traffic inspection and service control approach implements network service control traffic functions that are conducive to a network-based implementation and implements traffic and service control functions on the device that they are more conducive to performing on the device or can only be performed on the device (for example, activities that involve the inspection of traffic that is encrypted once it is transmitted to the network). For example, using this approach, the activities that can be done in the network are generally performed in the network and / or are performed more effectively in the network than in the device, and the activities that are performed more effectively in the device or can performed only on the device are performed on the device (for example, 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, may be preferred or may only be performed on the device: network-based packet processing capacity limitations (eg, encrypted traffic, traffic information application layer not available once traffic goes to the network interconnect stack, other application / usage context information available on the device but not on the network); information that is generally maintained / processed locally / preferably on the device for reasons of network neutrality (for example, network neutrality problems can be effectively implemented in general by maintaining all, substantially all or at least some aspect of decisions on how implement algorithms to control local traffic to the device and under user decision control, and / or providing the user with a set of pre-packaged choices on how to manage service use or service activity use or manage service usage versus cost of service or price); information that is generally maintained / processed locally / preferably on the device for reasons of user privacy (for example, deeper levels of traffic monitoring and service usage data monitoring where they are available to help the user achieve the Better experience of lower cost and implement a CRM filter function for the user so that the user can control the level of the CRM network that is allowed to receive, such as with the higher levels of information that are being exchanged for something of value to the user, and / or user location information); information that is generally maintained / processed locally / preferably in the device for the purpose of informing the user of service control settings or use of service activity or for adjusting service activity control settings or receiving user feedback to choices regarding service usage policies or billing options (for example, 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 use of projected service, provide the user with a UI for the purpose of monitoring an estimate of service cost and / or notify the user of at least some aspect of estimated service cost or projected service cost, provide 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 acknowledgment of receipt. Bo user and / or a user decision and obtain or generate information of the user's acknowledgments and / or decisions, provide the user with a UI in order to provide the user with service options and / or payment options of service, provide the user with a UI for the purpose of obtaining user choice for such options when the use of service or cost estimates are about to exceed the limits or have exceeded the limits or are projected to exceed the limits, provide to the user with a UI for the purpose of monitoring or performing open central billing transactions or other transactions, providing the user with a UI for the purpose of selecting service control techniques and / or policies and / or algorithms and / or configurations pre-packaged that can be used to partially define or define the service activity usage control policies implemented in the device service processor or the network service control team / billing system or a combination of both); service control for roaming on different networks that typically do not have IP type compatible techniques for the network

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

domestic; certain service notification and traffic control algorithms (for example, statistical analysis of activity classified by stack and control of only high usage activities); and / or a function to assign a device a service experience or experience of environment activation 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, or economically feasible, IPR approach is not possible, or for any number of reasons it is not an option or is 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 superset of additional services and / or services is provided for devices that include a processor. service. As described herein, a service controller function may be located in various places in the network according to various embodiments. It should also be noted that various other embodiments described herein also employ a hybrid service control function that performs certain service control functions in the network (for example, collecting network service usage information, such as IPDRs, and / or perform IP-related functions in the network to collect network service usage information and / or regulate / shape traffic) and service control functions in the device (for example, service processor 115, which, by For example, it monitors the use of service in the device and / or performs traffic regulation or conformation in the device and / or performs certain functions of recording and generating billing event information that are properly performed in the device).

In some embodiments, lower level service policy implementation embodiments are combined with a higher level set of service policy monitoring functions to provide device-assisted 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 related user experience referred to herein as environment activation. As discussed in a similar way previously, the activation of the environment can be provided by establishing access control to a fixed destination, verifying access with IPDR, verifying access by establishing a maximum data rate and deactivating the network if it exceeds the data rate. maximum and / or by various other techniques.

As shown in Figure 16, service controller 122 includes a 1650 service history server. In some embodiments, the 1650 service history server collects and records service usage or service activity reports from the AAA server. of access network 1621 and the service monitoring agent 1696. For example, although the service usage history from the network elements may, in certain embodiments, be less detailed than the service history from the device, the service history service from the network can provide a valuable source for verification of device service policy implementation, since, for example, it is extremely difficult for a device error or compromise event on the device to compromise network-based equipment and software . For example, device service history reports may include various service tracking information, as described similarly above. In some embodiments, the 1650 service history server provides the service history in the request to other servers and / or one or more agents. In some embodiments, the 1650 service history server provides the service usage history to the 1618 device service history. In some embodiments, for purposes of facilitating the activation tracking service functions (described below), the server 1650 service history keeps a history of which networks the device has connected to. For example, this network activity summary may include a summary of the accessed networks, activity versus time per connection and / or traffic versus time per connection. As another example, this activity summary can be further analyzed or reported to estimate the type of service plan associated with the traffic activity for the purpose of reconciling invoice sharing.

As shown in Figure 16, the service controller 122 includes a policy management server 1652. In some embodiments, the policy management server 1652 transmits policies to the service processor 115 via the service control link 1653. In In some embodiments, the policy management server 1652 manages policy settings in the device (for example, various policy settings as described herein with respect to various embodiments) according to a device service profile. In some embodiments, the policy management server 1652 sets instant policies on the policy implementation agents (for example, the policy implementation agent 1690). For example, policy management server 1652 can issue policy settings, monitor service usage and, if necessary, modify policy settings. For example, in the event that a user prefers the network to manage their service usage costs, or in the case of any need for adaptive policy management, the policy management server 1652 can maintain a relatively high communication frequency. with the device to collect traffic and / or services measure and issue new policy settings. In this example, the measure of device monitored services and any changes in user service policy preference are reported periodically and / or based on various triggers / events / requests, to policy management server 1652. In this example, the User privacy settings generally require secure communication with the network (for

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

for example, a secure service control link 1653), such as with policy management server 1652, to ensure that various aspects of user privacy are properly maintained during such transmission policy requests / adjustments transmitted over the network . For example, the information may be divided into compartments for service policy management and not communicated to other databases used for CRM to maintain user privacy.

In some embodiments, policy management server 1652 provides adaptive policy management on the device. For example, policy management server 1652 may issue policy and objective settings and rely on device-based policy management (for example, service processor 115) for some or all of the policy adaptation. This approach may require less interaction with the device thereby reducing network communication on the service control link 1653 for device policy management purposes (for example, network communication is reduced in relation to various management approaches server / network based policies described below). This approach can also provide robust user privacy embodiments by allowing the user to configure the device policy for user privacy preferences / settings such that, for example, sensitive information (e.g., geo-location data, history of website) does not communicate to the network without user approval. In some embodiments, policy management server 1652 adjusts the service policy based on the time of day. In some embodiments, the policy management server 1652 receives, requests or otherwise obtains a measured network availability and adjusts the traffic shaping policy and / or other policy settings based on the available network capacity.

In some embodiments, policy management server 1652 performs a service control algorithm to help manage global network capacity or application QoS. In some embodiments, policy management server 1652 performs an algorithm to determine which access network is best to connect, such as based on network capacity or application QoS, service usage costs and / or any other criteria. In some embodiments, the device may connect to more than one network, and therefore, the device service policies may 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 (for example, policy control agent 1692 described herein) detects network connection changes from the first network to the second network and implements the policies of service 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 provider and / or the user. For example, the network cost function may be based on a minimum service cost, maximum network performance, determine whether or not the user or device has access to the network, maximize the service provider's connection benefit, reduce connections to alternative payment 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 the highest in a preference list. For example, the preference list can be established by the service provider, the user and / or the service subscriber.

As shown in Figure 16, the service controller 122 includes a 1656 network traffic analysis server. In some embodiments, the 1656 network traffic analysis server collects / receives service usage history for devices and / or device groups and analyzes the use of service. In some embodiments, network traffic 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 network traffic analysis server 1656 estimates the quality of service and / or service use for the network under variable adjustments in the potential service policy. In other embodiments, the network traffic analysis server 1656 identifies actual or potential service behaviors by one or more devices that are causing problems for the overall network service quality or service cost.

As shown in Figure 16, service controller 122 includes a beta test server 1658. In some embodiments, beta test server 1658 publishes service plan policy settings candidates for one or more devices. In some embodiments, the beta 1658 test server provides summary reports of network service usage or user feedback information for one or more candidate service plan policy settings. In some embodiments, the 1658 beta test server provides a mechanism to compare the results of beta tests for different candidate service plan policy settings or select the optimal candidates for optimization of additional policy settings.

As shown in Figure 16, the service controller 122 includes a service download control server 1660. In some embodiments, the service download control server 1660 provides a download function for installing and / or updating service elements. service software (for example, the service processor

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

115 and / or agents / service processor components 115) in the device, as described herein.

As shown in Figure 16, service controller 122 includes a billing event server 1662. In some embodiments, billing event server 1662 collects billing events, provides service plan information to service processor 115, provides service usage updates to service processor 115, serves as an interface between the device and central billing server 1619 and / or provides reliable third party function for certain e-commerce billing transactions.

As shown in Figure 16, the access network AAA server 1621 is in network communication with the access network 1610. In some embodiments, the access network AAA server 1621 provides the access network services AAA necessary (for example, access control and authorization functions for the device access layer) to allow the devices in the central provider's access network and the service provider network. In some embodiments, another access control layer 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 access control layer can be implemented, for example, by service processor 115 in the device. In some embodiments, 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 service controller 122. In some embodiments, the AAA server Access network 1621 also provides the ability to route routing for device traffic to a quarantined 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 the use of device network service (for example, the use of device network service may be reported to the device service history 1618).

As shown in Figure 16, the device service history 1618 is in network communication with the access network 1610. In some embodiments, the device service history 1618 provides records of service usage data used for various purposes. in various embodiments. In some embodiments, the device service history 1618 is used to help verify the service policy implementation. In some embodiments, device service history 1618 is used to verify service monitoring. In some embodiments, device service history 1618 is used to verify billing records and / or billing policy implementation. In some embodiments, device service history 1618 is used to synchronize and / or verify the local service usage counter.

As shown in Figure 16, the central billing provider server 1619 is in network communication with the access network 1610. In some embodiments, the central billing provider server 1619 provides a mediation function for central provider billing events. . For example, the 1619 central billing provider server can accept service plan changes. In some embodiments, the central billing provider server 1619 provides updates on the use of device service, service plan limits and / or service policies. In some embodiments, the central billing provider server 1619 collects billing events, formulates invoices, invoices to service users, provides certain billing event data and service plan information to service controller 122 and / or device 100.

Establish coordinated service and verification policies for the service processor, service controller and network functions

In some embodiments, the network device and device coordinate one or more of the following: network service policy implementation settings, device service policy implementation settings, network service profile implementation settings, network settings device service profile implementation, 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 use policy violation and device actions taken after service use policy violation detection. In some embodiments, the local device settings for 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 devices of network that are also based on service policy and profile settings to monitor, control and / or bill for services or to respond to conditions of service use outside of politics. For example, such a network device includes service controller 122 or similar functions, billing system 123 or similar functions, AAA network 121, gateways 410, 420, 508, 512, 520, 608, 612, 620, 708 , 712, 720, or other network interconnection equipment. In some embodiments, the service profile or policy settings are associated between the device and the network in a manner that allows efficient and coordinated operation between the device service processor 115 and the network apparatus, but does not require an explicit function. which simultaneously controls / coordinates the service policy or profile implementation and / or verification actions taken by the device 100 (for example, the service processor 115) and the network apparatus. As an example, such embodiments can be applied in overlay applications as discussed below.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, a network function (for example, service controller 122, and / or more specifically the function of policy management server 1652, or other similar function) obtains, derives or otherwise determines the association of the profile of service or policy settings to program a device service processor 115 and the various network device functions (for example, possibly including, but not limited to, service controller 122 or similar functions, billing system 123 or functions similar, the AAA 121 network, the gateways 410, 420, 508, 512, 520, 608, 612, 620, 708, 712, 720, or other network interconnection equipment) reading, receiving, consulting, extracting or obtaining from another way the settings from one or more of the network device functions or from a database that stores the service policy or profile settings for one or more of the network device functions. After obtaining one or more of the network device settings, a mapping (for example, an association) of the network device settings to the settings of the appropriate device 100 (service processor 115) that advantageously supports the objectives can be determined of service usage monitoring, service usage control, service usage billing or service usage verification that are discussed. The policy or profile settings for the device can be a direct translation of the policy or profile settings used for the network device, or the policy or device profile settings can be derived less directly from the policy or device profile settings Network For example, the service usage limits contained in the billing system service plan 123 can be mapped directly to usage limit settings in the device service processor 115 (for example, service usage stops when it is reached the limit or the user is notified or the user is billed), or the usage limits can be mapped to a number of service profiles that the user can select (for example, as discussed in this document, the user can select based on options that imply different real use against use limit notification policies and / or service use control policies, limitations or regulation.

For example, the service usage policy or profile limits or concessions maintained by the network device functions (for example, the service profile or service plan usage limits stored in billing system 123 or AAA 121) they can be read or consulted by a network function (for example, service controller 122 or service controller 122 through an intermediate server connected to billing system 123 and / or AAA system 121), and the limits of Service usage stored in these network interconnecting devices may be directly translated into the settings for service processor 115 or may need to be interpreted, expanded or otherwise modified to obtain the required service processor policy 115 and / or profile settings .

In some embodiments, the service usage limits set in the billing system service plan record 123, and / or the service profile record stored in the AAA 121 system can be obtained (for example, from the device or from a database that stores the settings for the device) by the service controller (or other network function) and translated directly and used to program the settings on the service processor 123. In some embodiments, the usage limits of service are determined or obtained by the embodiments of the activation server apparatus, other apparatus embodiments associated with service activation, or the virtual service provider embodiments, as described herein. Thus, once the association profile of the service use or policy settings used by a device service processor 115 and the profile or policy settings used by the various network device functions are established, then the service policy or profile for service monitoring, control, billing, verification and / or actions taken in the verification error can be coordinated between the device and the network even if some of the network functions act independently of some of the functions of the device .

For example, by associating service usage policies and / or profiles between device service processor 115 and the various network device functions, and then allowing independent operation or action by the various functions in such a way that it results in a coordinated result, it facilitates an overlap of device-assisted services technology in existing network equipment in such a way that it results in reliable and verifiable service improvements while minimizing the need for significant updates of existing network equipment.

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 device functions may be provided by a centralized network function that Determine the appropriate settings for the network device and service processor 115 and establish one or more settings for each function. In some embodiments, this network interconnection function is provided by a centralized network management function or service account activation function (for example, the activation server apparatus embodiments, one of the other associated disclosed apparatus embodiments. with service activation or the realizations of the virtual service provider apparatus, 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 device functions may be provided by a network function that reads , receive, query, extract or otherwise obtain the setting used by service controller 122 or service processor 115. The network function can then determine the association of the service profile or policy settings used by a processor device service 115 and the service profile or policy settings required by the various network device functions

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

before writing, transmitting, inserting or otherwise registering the appropriate settings required by each of the other network device functions. In some embodiments, this functionality may be implemented in the service controller (for example, the policy management server, possibly acting in coordination with another network or server function), which is then linked to the databases used to store the policy or profile settings for the other network device.

In some embodiments, once the association between the service policy or profile settings in the network apparatus and the service policy or profile settings in the service processor 115 is established, then the service usage measures based networked (for example, IPDRs communicated to billing system 123, AAA 121, service controller 122 or other network functions used to verify service usage and / or take actions) used to verify service usage of device 100 against the service policy or profile they can be monitored by the network device (for example, billing system 123 and AAA 121) regardless of coordination with service processor 115 and / or independently of service controller 122. In some realizations, in addition to independent monitoring and verification of service usage versus policy, regardless of service profile or verification error. In addition, response actions may be taken by the network device (for example, suspension, quarantine, SPAN or tag device 100, notify the user and possibly require acknowledgment of receipt, or invoice the user's account for additional use of service use ) without direct involvement by service processor 115 and / or service controller 122.

Accordingly, the association between the service profile and / or the service policy that is implemented in the device 100 (for example, the service processor 115) and the service profile and / or policy usage limits recorded in the Network device can be associated with each other by one or more of the following: (A) implement a function to read from the network database (for example, billing database 123, AAA database 121, database of service controller data 122, etc.) and mapping the profiles and / or network policies to the profiles and / or policies of the device 100 (for example, the service processor 115); (B) implement a function that simultaneously establishes the device profile and / or policy and the network equipment profile and / or policy registered in the appropriate database records; and (C) implement a function that reads the profile and / or policy on the device 100 (for example, the service processor 115) or the service controller 122 and then sets the network equipment profile and / or policy registered in the appropriate database records. This allows a simplified but coordinated response to monitor, control and bill for service use, to verify service usage versus service usage profile or policy, and / or initiate or carry out network actions in response to service usage. against profile or policy verification errors and / or device actions in response to service usage against profile or policy verification errors.

Figure 17 is another functional diagram illustrating device based service processor 115 and service controller 122 in accordance with some embodiments. Figure 17 provides various embodiments as described similarly above with respect to the various embodiments described above with respect to Figure 16, one of the differences being that the service controller 122 as shown in Figure 17 is connected to the access network and not (directly) connected to the Internet. Accordingly, as shown in Figure 17, in some embodiments, the service control link 1653 is a communication link between the service controller 122 and the service processor 115 through the access network 1610.

Figure 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 modems and access network technologies in accordance with some embodiments. As shown, Figure 18 provides various embodiments as described in a similar manner above with respect to the various embodiments described above with respect to Figure 16, one of the differences being that the service processor controls policy implementation for multiple modems and access network technologies. Therefore, as shown in Figure 18, in some embodiments, a connection manager 1804, which as shown is in control plane communication with a modem selection and control 1811, provides a control and monitoring function for one or more of the modem controllers or modems that connect to an access network. In some embodiments, modem selection and control 1811 selects the access network connection and is in communication with the 1655 modem firewall, and modem drivers, which as shown include the 1831 dial-up modem controller, 1815 Ethernet modem controller, WPAN 1814 modem controller, W13 1813 modem controller and WWAN 1812 modem controller, convert data traffic into modem bus traffic for one or more modems and are in communication with the modem selection and control 1811.

Figure 19 is another functional diagram illustrating service processor 115 and service controller 122 according to some embodiments. As shown in Figure 19, an embodiment is provided in its basic version (e.g., reduced set of agents / components / functionality) of service processor 115 and service controller 122 in which the service policy is not adaptive instead it is set by service controller 122. In this example, the agent in service processor 115 that implements service policy is policy implementation agent 1690. Also, in this example, the service controller service 122 is similarly in its basic version to a simplified configuration (for example, reduced set of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

agents / components / functionality).

Referring to Figure 19, in some embodiments, many of the service protection and commitment policy implementation protection techniques are similarly provided using these simplified configurations of service processor 115 and service controller 122, as described above with respect to, for example, Figure 16. For example, the service control device link 1691 and the service control server link 1638 can be used to download service policies to policy implementation agent 1690 (but, in some embodiments, they cannot perform the function of operation or authentication function).

For example, a basic service or technical service profile verification service profile for this reduced configuration requests that access control integrity server 1654 obtain IPDRs from access network AAA server 1621 (or 121) (for example, or other network functions as described herein) and compare the service usage shown by the device 100 with an expected service usage interval that would be expected if the intended service policies were in place in the device. In some embodiments, access control integrity server 1654 initiates or performs one or more of the profile verification or service usage error response actions disclosed herein, including, for example, one or more of the following: notify the user of the condition outside of policy or additional use, require the user to acknowledge the condition and / or acknowledge receipt of a subsequent billing event to continue, bill the user for additional service use, suspend the device from the network, quarantine the device, use the SPAN function on the device, or notify a network manager or device management or error handling function.

In some embodiments, a service profile verification or service policy implementation technique for this reduced configuration requests that billing system 123 obtain IPDRs from access network AAA server 1621 (or 121) (or other functions). network as discussed in this document) and compare the service usage shown by device 100 with an expected service usage interval that would be expected if the intended service policies were in place in the device. In some embodiments, billing system 123 initiates or performs one or more of the profile verification error or service use policy response actions disclosed herein, including, for example, one or more of the following: notify the user of the condition of out of policy or additional use, require the user to acknowledge the condition and / or acknowledge receipt of a subsequent billing event to continue, invoice the user for additional use of service, suspend the device from the network, quarantine the device, use the SPAN function on the device, or notify a network manager or device management or error handling function.

In some embodiments, a service profile verification or service policy implementation technique for this reduced configuration requests that the AAA server 1621 (or 121) itself compare the service usage shown by the 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 1621 (or 121) server initiates or performs one or more of the profile verification error or service use policy response actions disclosed herein, including, for example, one or more of the following: notify the user of the out-of-policy or additional use condition, require the user to acknowledge the condition and / or acknowledge receipt of a subsequent billing event to continue, Billing the user for additional service use, suspending the network device, quarantining the device, using the SPAN function on the device, or notifying a network manager or device management or error handling function.

Therefore, this approach provides a basic first layer of service policy implementation verification that does not depend on the behavior of the device-based agent for verification. If the service policy is in error in a manner 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 of the service policy integrity verification tests fail, appropriate response actions may include routing the device to quarantine status, sending an error message to the device or device user interface already then suspend the access of the device, and / or limit the access in some way without completely suspending the access, as described similarly above. In some embodiments, if one or more service policy integrity verification tests fail, appropriate response actions may include registering excess service usage above the intended service policy limits and billing the user for any or all overuse, send the user a notification and / or request for a response to the acknowledgment of receipt (possibly including a simple acknowledgment of the keystroke, or a password, a biometric signature or other secure response), and / or limit access in some way without completely suspending access, as described similarly above.

In some embodiments, a billing system technique provides another verification overlay. For example, service processor 115 may have a set of service policy implementations (or service profile) that request to maintain service usage within a certain limit, or assist the user or network to

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Keep service usage at that limit. The billing system 123 may be implemented in a manner to provide a "return stop" to the controls or service usage limits provided by the service processor 115, so that even if the service processor 115 is compromised, hacked , falsified or otherwise in error, billing system 123 protects the service provider, "service owner", operator, VSP or network operator from unpaid access beyond the service limits. This can be achieved, for example, by assigning a service use limit within the billing system 123 so that if the service processor 115 is compromised and the service usage is skipped the desired limit, the billing system 123 automatically charges the user's account for additional use. The billing system 123 can receive service usage information from the IPDRs that are added in the network as in the case of a conventional billing system, and because these network-based measures are independent of the device agent operation , something cannot simply be falsified in the processor of the device or service 115. In this way, overcoming the service agent control mechanisms of the service processor 115 described herein simply results in a billing charge and not free service. . In some embodiments, if the service usage exceeds the service usage limit specified in the service profile, the user may be notified as discussed herein, and the user may be required to acknowledge receipt of the additional use and approve a billing charge for the additional use as also analyzed in this document, communicating back the acknowledgment of receipt to the network in some embodiments. This positive acknowledgment also provides a protection and verification layer of the service control and usage limit control for the device service processor 115. In some embodiment also discussed herein, the user is requested to enter a password. , biometric or other secure response for notification of additional use use, providing another layer of protection to verify that the user intends to pay for the additional use of service use. In these embodiments taken individually or in combination, the assistance of the service processor 115 for service usage control can be verified and / or protected from compromise.

In some embodiments, the service control device link 1691 and the service control server link 1638 are used to implement the operation indication and communication authentication functions of the service processor 115 to reinforce the verification of an implementation. of the appropriate service policy of the embodiments of Figure 19. For example, the operation indication function can be used as authentication for service monitoring against network reports. In addition, the function indication function can be used as authentication for agent challenge / response queries. Also, the function indication function can be used as authentication for access control. In some embodiments, to reinforce the verification of the basic system illustrated in Figure 19, communication access to policy implementation agent 1690 is restricted so that the software or hardware in the device 100 and / or in a network cannot have authorized access to policy implementation agent 1690. For example, authorized access to policy implementation agent 1690 can be restricted to include only service controller 122 through service control device link 1691 and service server link service control 1638. For example, 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. As another example, agent level message encryption can be used as described herein. document.

In some embodiments, the service policy implementation agent 1690 of the embodiments of Figure 19 may be further reinforced against errors, intrusion, manipulation, hacking and / or other inadvertent or intentional integrity degradation using various other techniques. For example, the dynamic agent download feature of the service controller 122 may download a new version of the policy implementation agent 1690. In this example, the new agent code may be identical in functionality and also be chopped, obfuscated or ordered from differently before signing and encryption so that any hacking attempt must be restarted, and this process can be repeated periodically or repeated after an activation event. Additionally, once the new dynamically loaded agent is in place, it may be required to perform an environment scan to determine if the system configuration or operation is as expected, and / or may seek to detect elements in the runtime environment. that may be harmful or threaten the integrity of the policy implementation. The agent may also be required to report the scan back within a relatively short period of time so that any attempt to compromise the agent does not have enough time to be effective.

In some embodiments, the service policy implementation agent 1690 of the embodiments of Figure 19 may be reinforced to protect the policy implementation from compromise attempts by locating the software and / or hardware used in an access modem associated with the service. For example, the modem may make it difficult to access policy implementation agent 1690 using one or more security elements on one or more access ports on the modem, such as the device bus, an I / O port, a Network connection or debug port. The modem can also store and / or execute the policy implementation agent in secure memory. The modem may 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 of Figure

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

19 can be further reinforced against compromise attempts by performing scans of the code execution environment of the device 100 and / or the code storage environment to identify potentially malicious and / or unwanted / unreliable software or hardware. For example, this function can be performed by policy implementation agent 1690. The agent can have a local database of potentially malicious elements and compare entries in the database against locally detected elements using various malicious code techniques, behavior blocking, intrusion detection and / or other well known for security analysis. Alternatively or in addition, the agent may communicate a list of some or all of the locally detected elements to the service controller 122 to increase or take the place of the database comparison function that can be performed locally, thus performing such security or additional analysis on the network (for example, by service controller 122), and, in some embodiments, if not detected automatically, such locally detected elements (for example, and / or samples of such code or records potentially malicious behavior detected / potentially malicious / suspicious intrusions) forwarded to security analysts for the service provider for additional security analysis (for example, service provider security analysts and / or an external security distributor responsible for protecting the network from the service provider and supported devices). In some embodiments, the agent detects new downloads, installations and / or software invocations and immediately sends an error flag report when potentially malicious software is downloaded, installed or invoked (for example, based on access security detection techniques of file and network). In some embodiments, the agent scans the local software load and invocation activity along with a record of other software runtime events and regularly reports this trace so that when an error or compromise event occurs the trace that precedes the event can be analyzed to determine the attacking 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 introduced 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 may include software invocations, software downloads, a sequence of memory I / O events, a sequence of software access events, a sequence of network addresses or communications or URL downloads or a sequence of access modem I / O activity.

Figure 20 is another functional diagram illustrating service processor 115 and service controller 122 in accordance with some embodiments. As shown in Figure 20, the 1655 modem firewall has been removed, and the firewall and access control and traffic shaping functions are performed in these embodiments by the policy implementation agent 1690 and the application interface agent 1693.

Figure 21 is another functional diagram illustrating service processor 115 and service controller 122 according to some embodiments. Figure 21 illustrates the various modem controllers and modems 2122 through 2125 and 2141. In some embodiments, the modems, which include the WWAN 2122 modem, WLAN modem 2123, WPAN modem 2124, Ethernet modem 2125, and modem Dialing / DSL 2141, which are in communication with the modem bus 2120, connect the device to one or more networks. As shown, the service measurement points labeled I to VI represent various service measurement points for the service monitoring agent 1696 and / or other agents for performing 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 used in a given design can be used by a monitoring agent to track application layer traffic through the communication stack to help policy implementation functions, such as policy implementation agent 1690, or, in some embodiments, modem firewall agent 1655 or application interface agent 1693, when making a determination regarding traffic or type parameters once traffic It is further down 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 some or all of the measurement points illustrated in Figure 21 to have an effective implementation as shown in a similar manner with respect to Figure 19, various embodiments benefit from these and / or the like. Measuring 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 may have the agents that affect the policy implementation moved to different points in the Traffic processing stack while still maintaining effective operation.

As shown in Figure 21, the measurement point I takes place in the application interface agent 1693 which interfaces the applications. At this measurement point, the traffic application can be monitored, packaged or encrypted before it is framed by the lower layers of the network interconnect stack. For example, this allows inspection, characterization, labeling (literal or virtual) and, in some embodiments, conformation or control of services or traffic. At this measurement point, traffic can be more easily 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 endpoints, media file transfers, application traffic demand, URL traffic demand and other such service monitoring parameters are observed more easily (for example, accessible transparently without the need for deep packet inspection and / or decryption), they are recorded and possibly

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

They conform or control. As described in this document, it is also possible to monitor upstream traffic demand at this point and compare it to the other measurement points to determine whether traffic policies are instead meeting global traffic control policy objectives or to determine If the traffic policy implementation is operating properly. For example, traffic delivered downstream can be optimally observed at this measurement point.

As shown in Figure 21, traffic measurement points II and III are located at 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 policy implementation agent 1690. These two locations also provide potential cross-checking of how policy implementation agent 1690 is impacting traffic demand and delivery. Similarly, measuring point III in connection with measuring point IV provides an opportunity for packet tracing through the stack components associated with the 1655 modem firewall and provides the opportunity to observe demand and sides of the 1655 modem firewall delivery. The traffic measurement point V provides the potential to observe the traffic in the modem bus controllers for each of the modems.

As shown in Figure 21, the traffic measurement point VI provides, in some embodiments, the final measure of access traffic, for example, the traffic that actually operates through the access network through the modem. As shown, the measurement point VI is on the modem side of the internal or external communication bus 1630, and it will be appreciated that, in some embodiments, this measurement point can be found further down the modem stack closer to the MAC or physical layer (for example, at the discretion of the designer). An advantage of having a deep measuring point in the modem is, for example, that if the software or hardware that implements the measurement and generation of information is well secured against compromise, then this measure can be almost as strong from a verification perspective. than the measure that comes from the network (for example, from the network elements). Therefore, this makes it possible to compare this measure against the other measures to determine if there is a traffic route that is filtering past the other measurement point or one or more policy implementation points.

Figures 22A to 22B provide tables summarizing various service processor agents 115 (and / or components / functions implemented in software and / or hardware) according to some embodiments. Many of these agents have been similarly described above, and the table shown in Figures 22A to 22B is not intended to be a comprehensive summary of these agents, nor an exhaustive description of all the functions performed by the agents or described. in this document, but instead Figures 22A to 22B are provided as a summary to help understand the basic functions of each agent according to some embodiments and how the agents interact with each other, with the controller server elements of service, and / or with other network functions in certain embodiments to form a solution and / or service delivery platform based on a reliable device.

Figure 23 provides a table summarizing various service controller server elements 122 (and / or components / functions implemented in software and / or hardware) according to some embodiments. Many of these agents have been similarly described above, and the table shown in Figure 23 is not intended to be an exhaustive summary of these server elements, nor an exhaustive description of all the functions performed by the elements or described. in this document, but instead Figure 23 is provided as a summary to help understand the basic functions of each element according to some embodiments and how the elements interact with each other, certain network elements, and / or Service processor agents in certain embodiments to form a solution and / or service delivery platform based on reliable device.

In some embodiments, it is desirable to provide a control plane between the service processor and the service controller using a flexible communication connection or route that, for example, will operate between virtually any two network connection endpoints, one being the controller. of service and the device being one, in a scalable but secure way. In view of the embodiments described herein, one skilled in the art will recognize that it is possible to achieve such characteristics with a variety of different embodiments that share main characteristics similar to the embodiments described herein.

Service control device link and continuous operation indication authentication

As described herein, there are numerous ways to implement the control plane communication channel between service processor 115 and service controller 122, various embodiments described herein disclose an effective control plane in width of band and secure that it is compatible with any IP-based network (including the ability to locate service controller 122 over the Internet); provides service monitoring, control, verification and / or billing assisted by coherent device while roaming across multiple networks with different access technologies; and allows verification and / or authentication of continuous device-assisted service control with a variety of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

mechanisms to adjust the frequency of transmission operation indication. 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 alignment mechanisms of IP frames or data packets (for example , IPV6), which execute a more conventional VPN or IPSEC channel, and / or use a separate access network connection.

Figure 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. In particular, 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 Figure 24 provide secure control plane communication through the link of service control 1653 between service processor 115 and service controller 122 according to some embodiments. Various embodiments include two or three layers of encryption in the service control link, with one embodiment or layer that is implemented in the encryption functions (2408, 2428) and decoding functions (2412, 2422), and another embodiment or layer implemented in the transport services stack (2410, 2420). A third optional embodiment or encryption layer is implemented below the transport services stack, for example, with IPSEC or other IP, VPN or tunnel layer encryption scheme. For example, various known security encryption techniques can be implemented in the encryption functions (2408, 2428), with public / private or completely private keys and / or signatures so that very strong levels of security can be achieved for plane traffic of service processor control even through basic transport services (2410, 2420) implemented with conventional secure or open Internet network interconnection protocols, such as TLS or TCP. For example, local service processor agent communications to the device can be made to and from the service controller elements by connecting service control device link 1691 to agent communication bus 1630. The combination of the device link of service control 1691 and agent communication bus 1630, which in some embodiments is also encrypted or signed securely, provides an asynchronous control plane connection, highly secure, without interruptions between the service processor and server elements of service controller and service controller and service controller agents operating across a wide range of access networks, such as any access network that has the ability to connect Ip or TCP traffic to another endpoint of TCP or IP in the access network, another private network or over the Internet 120. As described in this document nto, in some embodiments, the agent communication bus 1630 also provides a fourth level of encrypted or signed communication to form a secure closed system in the device for agent-to-agent communication, for example, making it very difficult or virtually impossible for the software or applications gain access to one or more of the service processor agents in the device in some manner other than the service control device link 1691. Thus, in some embodiments, the agent communication bus 1630 and the Service processor agents can only access each other as necessary or allowed by agent communication policies, or by the service controller or other authorized network function with appropriate security credentials communicating through the control device link of service 1691. Additionally, in some embodiments, communications between a subco a set 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 such that a fourth level of security is provided that provides secure point communication lines to point, point to multipoint or multipoint to multipoint.

In some embodiments, all communications of the service control device link 1691 are transformed into a continuous control plane connection, with a frequency based on the service usage rate, a minimum established period between connections and / or other methods. to establish communication frequency. In some embodiments, this operation indication function provides a continuous verification link whereby the service controller verifies that the service processor and / or the device are operating properly by implementing the correct service policies. In view of the following operation indication function of the embodiments described herein, it will be apparent to one skilled in the art that different approaches are possible to implement the various performance indication embodiments, and it will be apparent that there are many ways to achieve the essential characteristics that enable a reliable control link on occasion continuous and the verification function in order to help control service use in a verifiable way. As shown, within the service processor 115, the service control device link 1691 includes an operation indication send counter 2402 in communication with the agent communication bus 1630. For example, the indication send counter of operation 2402 can provide a count for activation when a communication from a service processor 115 (eg, periodic communication based on an operation indication mechanism) should be sent to service controller 122, and an operation indication buffer 2404 , also in communication with the agent communication bus 1630, stores any such information for the following service processor communication 115 in buffer memory, in accordance with various embodiments based on indication of operation, as similarly described in This document. The operation indication buffer 2404 is in communication with a frame alignment element 2406 and an encryption element 2408 for frame alignment and encryption of any service processor communication 115 transmitted to the service controller 122 by a stack of service services 2410 transport through the 1653 service control link.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

similarly, as shown within the service controller 122, the service control server link 1638 includes an operation indication send counter 2434 in communication with a service controller network 2440, an operation indication buffer 2432 , also in communication with the service controller network 2440, stores in memory any such information for the following service controller communication 122, in accordance with various embodiments based on indication of operation, as similarly described in This document. The operation indication buffer 2432 is in communication with a frame alignment element 2430 and an encryption element 2428 to align frames and encrypt any communication of this type of service controller 122 transmitted to the service processor 115 by a stack of 2420 transport services through the 1653 service control link.

As also shown within the service processor 115 of Figure 24, the service control device link 1691 includes a decoding element 2412 to decode any received service controller communication 122 (for example, decrypt encrypted communications), a unpacking element 2414 for unpacking received service controller communications 122 (e.g., assembling packaged communications), and an agent route 2416 for routing received service controller communications 122 (e.g., commands, instructions, information or status reports related to operation indication, configuration information or settings and / or policy related updates, challenge / response queries, agent refreshments and / or new software for installation) to the appropriate service processor agent 115. In a manner similar, as shown within the controlled Service r 122, the service control server link 1638 also includes a decoding element 2422 to decode any received service processor communication 115 (e.g. decrypt encrypted communications), an unpacking element 2424 to unpack the communications from service processor 115 received (eg, assembled packaged communications), and an agent route 2426 to route received service processor communications 115 (eg, responses to instructions and / or commands, information or status reports related to indication of operation, information or configuration settings and / or updates related to policy, challenge / response queries, agent status information, service usage / network cost and / or any other information related to information generation) to the agent appropriate service controller 122. Therefore and, as described herein with respect to various embodiments, the various secure communications between service controller 122 and service processor 115 may be performed using the embodiment as shown in Figure 24, and those skilled in the art. they will also appreciate that a variety of other embodiments can be used to similarly provide the various secure communications between service controller 122 and service processor 115 (for example, using different software and / or hardware architectures to provide secure communications, such such as using fewer elements / functions or additional or other design choices to provide such secure communications).

In some embodiments, an efficient and effective communication frame alignment structure is provided between the service processor and the service controller, and the following embodiments (eg, as shown and described with respect to Figure 25) teach a Such a structure that packages the various service processor agent control plane communications and the various service controller element control plane connections in a format that does not consume excessive bandwidth to enable a plane connection of continuous control between the device and the service controller. In some embodiments, an efficient and effective communication frame alignment structure is provided between the service processor and the service controller for buffering such communication messages for some period of time before aligning and transmitting frames, such as in an operating indication frequency that is based on the service usage rate. In some embodiments, an efficient and effective communication frame alignment structure is provided between the service processor and service controller to allow the frame to be easily packaged, encrypted, decoded, unpacked and messages distributed. In view of the various embodiments described herein, it will be apparent to one skilled in the art that many frame alignment structures will work for the intended purpose of organizing or aligning agent communications frames and the uniqueness and importance of combining an element. of this type of system with the device service controller functions, the service processor functions, the service control verification functions and / or the other purposes.

Figure 25 is a functional diagram illustrating a frame alignment structure of a service processor communication frame 2502 and a service controller communication frame 2522 in accordance with some embodiments. In particular, the service control device link 1691 of the service processor 115 and the service control service link 1638 of the service controller 122 (for example, as shown in Figure 24) provide a plane communication of secure control via service control link 1653 between service processor 115 and 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 Figure 25 according to some embodiments. As shown, the service processor communication frame 2502 includes a service processor frame alignment sequence number 2504, a time indication 2506, a first agent function ID 2508, a first function message length of agent 2510, a first message from

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

agent function 2512, and assuming that more than one message is being transmitted in this frame, one nth agent function ID 2514, one nth length of agent function message 2516, and one nth agent function message 2518. By consequently, the service processor communication frame 2502 may include one or more messages as shown in Figure 25, which may depend on the network interconnect frame length requirements and / or other design choices. Similarly, as shown, the service controller communication frame 2522 includes a service controller frame alignment sequence number 2524, a time indication 2526, a first agent function ID 2528, a length of first agent function message 2530, a first agent function message 2532, and assuming that more than one message is being transmitted in this frame, one nth agent function ID 2534, a length of nth agent function message 2536 , and one nth agent function message 2538. Accordingly, the service controller communication frame 2522 may include one or more messages as shown in Figure 25, which may depend on the interconnect frame length requirements in network and / or other design choices.

Figures 26A to 26H provide tables summarizing various functions and parameters of service processor operation indication (for example, implemented by various agents, components and / or functions implemented in software and / or hardware) according to some embodiments. Many of these function indication functions and parameters have been described similarly above, and the tables shown in Figures 26A through 26H are not intended to be an exhaustive summary of these function indication and function indication parameters, but rather in their Instead they are provided as an aid to understand these functions and parameters in accordance with some embodiments based on indication of operation described herein.

Figures 27A to 27P provide tables that summarize various device-based service policy implementation verification techniques in accordance with some embodiments. Many of these device-based service policy implementation verification techniques have been described similarly above, and the tables shown in Figures 27A through 27P are not intended to be a comprehensive summary of these policy implementation verification techniques. device-based service, but instead are provided as an aid to understand these techniques in accordance with some device-based service policy embodiments described herein.

Figures 28A to 28E provide tables that summarize various techniques to protect the device-based service policy from compromising in accordance with some embodiments. Many of these techniques to protect the device-based service policy from compromising have been described similarly above, and the tables shown in Figures 28A through 28E are not intended to be a comprehensive summary of these techniques to protect the Device-based service policy enters into compromise, but instead is provided as an aid to understand these techniques in accordance with some embodiments of device-based service policy described in this document.

Device-assisted service control and traffic control

As described below, various techniques for implementing device-assisted traffic shaping and service control at the lower levels of service use policy implementation are disclosed.

Figure 29 is a functional diagram illustrating a device communications stack that allows implementing traffic shaping policy, access control policy and / or verifiable 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 policy settings for the data path service, implement billing for the data route service, manage one or more modem selections and settings for access network connection, interact with the user and / or provide verification of service policy implementation. Additionally, in some embodiments, several agents perform functions to help verify that the service control or monitoring policies that are intended to take place are properly implemented, the service control or monitoring policies are adhering properly, that the processor of service or one or more service agents are operating properly, to avoid unintended errors in implementation or control of policy, and / or to avoid manipulation with service or control policies. As shown, the service measurement points labeled I to VI represent various service measurement points for the service monitoring agent 1696 and / or other agents for performing 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 used in a given design can be used by a monitoring agent to track application layer traffic through the communication stack to help 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, when making a determination regarding the parameters or type of traffic once the traffic is over down in the communication stack where sometimes it is difficult or impossible to make a complete determination of traffic parameters. For example, a detailed set of embodiments is described.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

which describe how the various measurement points can be used to help reinforce the verification of the service control implementation in this document, which includes, for example, the embodiments described with respect to Figure 16 and Figure 21. The locations Particular for the measurement points provided in these figures are intended as instructive examples, and other measurement points may be used for different embodiments, as will be apparent to one skilled in the art in view of the embodiments described herein. In general, in some embodiments, one or more measurement points may be used within the device to assist in the verification of service control and / or troubleshooting of the device or service.

In some embodiments, the service monitoring agent and / or other agents implement virtual traffic labeling by tracking or tracing packet flows through the different format of communication stack, processing and encryption steps, and providing virtual tag information to the various agents that monitor, control, shape, regulate or otherwise observe, manipulate or modify traffic. This labeling approach is referred to herein as virtual labeling, since there is no literal data flow, traffic flow or package label that is attached to flows or packages, and the accounting for labeling the package is done by tracking or tracing the flow or package through the stack instead. In some embodiments, the application interface and / or other agents identify a traffic flow, associate it with a service use activity and cause a literal label to be attached to the traffic or packets associated with the activity. This labeling approach is referred to herein as literal labeling. There are several advantages with both virtual labeling and literal labeling approaches. For example, it may be preferred in some embodiments to reduce the inter-agent communication required to track or trace a packet through stack processing by assigning a literal tag so that each flow or packet has its own association of activity embedded in the data. As another example, it may be preferred in some embodiments to reuse portions of the software or components of the conventional communication stack, which improve the verifiable traffic control or service control capabilities of the conventional stack by inserting additional processing steps associated with the various agents. of service and monitoring points instead of rewriting the entire stack to correctly process literal tagging information, and in such cases, a virtual tagging scheme may be desired. As another example, some conventional communication stacks provide unused, unspecified or otherwise available bit fields available in a frame or packet stream, and these unused, unspecified or otherwise available bit fields can be used. to literally label traffic without the need to rewrite all the software of the conventional communication stack, with only the portions of the stack added to improve traffic control or service control capabilities of the conventional stack that you need to decode and use the literal tagging information encapsulated in the available bit fields. In the case of literal labeling, in some embodiments, the tags are removed before passing the packets or flows to the network or to the applications that use the stack. In some embodiments, the manner in which virtual or literal labeling is implemented can be developed in a conventional communication specification so that various device or service product developers can independently develop the hardware and / or software of the communication stack and / or service processor in a way that is compatible with the specifications of the service controller 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 Figure 29 is not required to have an effective implementation, as shown in a similar manner with respect to various embodiments described herein, such as With respect to Figures 19 and 21, various embodiments may 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 may have the policy-affecting agents moved to different points in the traffic stack. Traffic processing while still maintaining effective operation. In some embodiments, one or more deeper measurement points are provided in the modem stack (for example, such as for embodiments similarly described herein with respect to Figures 35 and 36) in which, for example , it is more difficult to avoid and it may be more difficult to access for handling purposes if the modem is designed with the appropriate software and / or hardware security to protect the integrity of the modem battery and the measuring point or points.

Referring to Figure 29, which describes 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 device modems in the device. bottom of the device communications stack. Example measurement point VI resides at or just above the modem controller layer. For example, the modem controller performs modem bus communications, data protocol translations, modem control and configuration to interconnect the network interconnect stack to the modem. As shown, measurement point VI is common to all modem and modem controllers, and it is advantageous for certain embodiments to differentiate the traffic or service activity that takes place through a modem from that of one or more of the other modems. . In some embodiments, measurement point VI, or another measurement point, is located above, at or below one or more of the individual modem controllers. The respective modem buses for each modem reside between the measuring points V and VI of the example. In the next upper layer, a modem selection and control layer is provided for multimode device based communication. In

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, this layer is controlled by a network decision policy that selects the most desirable network modem for some or all data traffic, and when the most desirable network is not available the policy returns to the next most desirable network until that a connection is established on the condition 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 a diversity of enhanced security, enhanced reliability or enhanced management capacity devices, services or applications. On the next top layer, a modem firewall is provided. For example, the modem firewall provides traditional firewall functions, but unlike traditional firewalls, to rely on the firewall for verifiable service usage control, such as access control and traffic safety protection or interconnection applications in Unwanted network, the various service verification techniques and agents described in this document are added to the firewall function to verify compliance with the service policy and avoid tampering with the service controls. In some embodiments, the modem firewall is implemented higher in the stack, possibly in combination with other layers as indicated in other Figures. In some embodiments, a specialized 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 further down the stack, such as in modem drivers, below modem drivers, or in the same modem. The 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 separated 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 conventional network stack function can be used for queues and IP routing, and the modifications necessary to implement the policy implementation agent functions. they can be provided in a new layer inserted in the conventional stack. In some embodiments, the queuing and IP routing layer is combined with the traffic or service usage control layer. Examples of this combined functionality are shown and described with respect to Figures 31, 32 and 33. For example, a routing and policy implementation layer embodiment may also be used in combination with the other embodiments, as shown in Figure 29. Various detailed embodiments are described that describe how the policy implementation layer can control traffic or other service use activities with respect to Figure 38. Measurement point III resides between the queue-up and IP routing layer. and a policy implementation agent layer. Measurement point II resides between the policy implementation agent layer and the transport layer, which includes TCP, UDP and another IP as shown. The session layer resides above the transport layer, which is shown as a mapping and connector session management layer (for example, basic TCP configuration, TLS / SSL). The network services API (for example, 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 the application service interface agent in the device communications stack of Figure 29.

As shown, the application service interface layer is above the conventional network interconnect stack API and, in some embodiments, its function is to monitor and, in some cases, intercept and process traffic between applications. and the conventional network interconnect stack API. In some embodiments, the application service interface layer identifies application traffic flows before application traffic flows are more difficult or virtually impossible to identify further down the stack. In some embodiments, the application service interface layer thus helps application layer labeling in both cases of virtual labeling and literal labeling. In the case of upstream traffic, the application layer labeling is direct, since the traffic originates in the application layer. In some downstream embodiments, when the traffic classification or service activity is based on easily obtainable traffic attributes, such as source address or URL, application connector address, IP destination address, time of day or any other easily obtained parameter, the type of traffic can be identified and labeled for processing by the firewall agent or other agent as it initially arrives. In other embodiments, as described herein, in the case downstream, the solution is generally more sophisticated when a traffic parameter is necessary to classify the way in which traffic flow is to be controlled or regulated. It is not readily available at the lower levels of the stack, such as association with an application aspect, content type, something contained in TLS, IPSEC or other secure format, or other information associated with traffic. Accordingly, in some embodiments the network interconnect stack identifies the traffic flow before it is fully characterized, categorized or associated with a service activity, and then the traffic passes through the application interface layer where it is completed. The final classification. In such embodiments, the application interface layer then communicates the traffic flow ID with the appropriate classification so that after a burst or initial brief traffic time period, the policy implementation agents can appropriately control the traffic. . In some embodiments, there is also a policy for labeling and adjusting service control policies for traffic that cannot be fully identified with all labeling sources that include application layer labeling.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

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 the 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) by 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 selection and control commands and / or modem and access network information through this communications stack, as shown (illustrating such communications with a reference (C) through the modem selection and control layer ). Various other communications (for example, communications related to the service processor and / or service controller, such as service usage measurement information and / or application information) are provided at various levels of this communication stack, such as sample (illustrating such communications with references (D) in the application layer, (E) in the policy implementation agent layer, and (F) in the modem firewall layer).

As shown in Figure 29, a service monitoring agent, which is also in communication with the agent communication bus 1630, communicates with various layers of the device communication stack. For example, the service monitoring agent performs monitoring at each of measurement points I to VI, receiving information that includes application information, service use and other service related information, and assignment information. An access control integrity agent is in communication with the service monitoring agent via the agent communications bus 1630, as also shown.

In some embodiments, one or more of the network interconnection stack modifications described herein are provided in combination with one or more of the service verification and tamper prevention techniques described herein. As described similarly with respect to Figure 29, the various example embodiments to assist in the verification of service control described herein and as summarized in the example tables provided in Figures 26, 27 and 28 they can be used individually or in combination to create increasingly secure cross-functional service control verification embodiments. In Figure 29, the presence of the access control integrity agent, policy control agent, service monitoring agent and the other agents that perform verification and / or tamper prevention functions illustrates verifiable service control aspects according to some embodiments. Additionally, the presence of the billing agent combined with the agents and service verification and / or handling prevention techniques described in this document provide a set of verifiable billing accomplishments for service billing, service billing compensation 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 network interconnect stack provides embodiments that involve a combination of service control with user preferences, which as described In this document, it provides the user with the ability to optimize service against service cost in a neutral network manner. In some embodiments, the user control of the service policy control is provided together with the verification of service control and / or tamper prevention. The presence of the policy control agent that in some embodiments implements a higher policy decision level than the most basic and the control with the policy implementation agents in the modified network interconnection stack allows, for example, that the device has the ability to implement a higher level of service control in order to obtain a higher level of service use or service activity objective. In some embodiments, application layer labeling in combination with other embodiments described herein provides control of deep service activity that is verifiable.

In some embodiments, verifiable traffic shaping as described herein may be performed using the device communications stack in a variety of embodiments for the combination of service control in a network interconnection stack and service control verification. and / or tamper prevention, with various embodiments depicted in Figures 29 to 37. Additional levels of detail are provided regarding how such embodiments can be used to implement verifiable traffic shaping and are described with respect to Figures 38 to 40 which they represent exemplary 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. Together with several other interesting features performed in Figures 38 to 40, application traffic layer labeling in accordance with some embodiments is depicted in additional details. For example, the application interface agent can determine use of service data in the application layer using measurement point I and a local service usage counter, and can, for example, pass this information to the monitoring agent of service. If the service usage exceeds a threshold, or if using a service usage prediction algorithm results in expected service usage that will exceed a threshold, then the user can be notified of what applications are causing service usage exceeding or exceeding of potential service usage, through the user service interface agent. The user can identify which application service (for example, traffic

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

associated with a use of specified high service or non-critical application, such as a website or social network service of high bandwidth consumption, website or multimedia streaming service, or any other website or service high bandwidth that transmits and / or receives data with the service network) that the user prefers to regulate. As another example, the user could select a service policy that allows video chat services until these services threaten to cause cost overruns in the user's service plan, and at that time the service policy could switch the service from Voice chat only and not transmit or receive the video. Traffic associated with the user's specified application can then be regulated according to user preference input. For example, for downstream traffic, packets (for example, packets that are labeled virtual or literally and / or associated with application traffic in this way can be regulated) from the access network can be stored in buffer, delayed and / or download to regulate the identified application traffic. For upstream traffic, packets (for example, packets that are virtual or literally labeled and / or otherwise associated with the traffic application to be regulated) can be stored in buffer, delayed and / or deleted before they are transmitted to the access network to regulate the identified application traffic. As described similarly above, the traffic conformation can be verified as described herein, such as by the service monitoring agent by the various measuring points and / or using other agents.

The embodiments depicted in Figure 30 and other figures generally require improvements to the processing of a network interconnection communication device of a conventional device. For example, these improvements can be implemented in whole or in part in the kernel space for the OS of the device, in whole or in part in the application space for the device, or partially in the core space and partially in space of application. As described herein, network interconnect stack improvements and other elements of the service processor can be packaged in a set of software that is previously tested or documented to enable the device manufacturer to quickly implement and bring to market. the functionality of the service processor in such a way that it is compatible with the service controller and the applicable network or access networks. For example, service processor software can also be specified in an interoperability standard so that various manufacturers and software developers can develop service processor implementations or improvements, or service controller implementations or improvements that are compatible with each other.

Figure 30 is another functional diagram illustrating the device communications stack that allows to implement 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 in the modem (for example, in modem module hardware or modem chipset) and a portion of the service processor is implemented in the device application processor subsystem . It will be apparent to one skilled in the art that variations of the embodiment depicted in Figure 30 are possible where more or less of the functionality of the service processor moves in the modem subsystem or in the device application processor subsystem. For example, such embodiments similar to those depicted in Figure 30 may be motivated by the advantages of containing some or all of the service processor network communication stack processing and / or some or all other service agent functions in the modem subsystem (for example, and such an approach can be applied to one or more modems). For example, the service processor may be distributed as a conventional feature set contained in a software package modem chipset hardware or modem module or software package hardware, and such a configuration may provide adoption or easier development by device OEMs, a higher level of differentiation for the chipset or modem module manufacturer, higher levels of performance or integrity or security of service use control implementation, specification standardization or interoperability and / or other benefits.

Referring to Figure 30, which describes 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 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 top layer, the policy implementation agent is provided, in which the policy implementation agent is implemented in the modem (for example, in modem hardware). Measurement point II resides between the policy implementation agent and the modem controller layer, which is shown below a modem bus layer. The next top layer is shown as the queuing and IP routing layer, followed by the transport layer, which includes TCP, UDP and other IP as shown. The session layer resides above the transport layer, which is shown as a connector assignment and session management layer (for example, basic TCP configuration, TLS / SSL). The network services API (for example, 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 the application service interface agent in the device communications stack of Figure 30.

Various applications and / or a user service interface agent communicate through this stack of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

communications, 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 inquiry and / or user input to the user service interface agent, as shown. Policy control agent B communicates service settings and / or configuration information through this communications stack, as shown (illustrating such communications with a reference (B)) through the application layer. Policy control agent A communicates service settings and / or configuration information through this communications stack, as shown (illustrating such communications with a reference (D)) through the policy implementation agent layer and / or the modem firewall layer. The connection manager agent communicates control and selection commands and / or modem and access network information through this communications stack, as shown (illustrating such communications with a reference (C)) through the modem controller layer . Various other communications (for example, communications related to the service processor and / or service controller, such as service usage measurement information, and / or application information) are provided at various levels of this communication stack, such as is shown (illustrating such communications with references (E)) in the application layer through the modem controller layer with the service monitoring agent B as shown (and an access control integrity agent B is also shows), and communications with references (F) in the policy implementation agent layer and (G) in the modem firewall layer with service monitoring agent A as shown (and an integrity agent Access control A is shown as well). In some embodiments, the embodiments of service policy use or tamper prevention described herein may be applied, in isolation or in combination, in the context of Figure 31 to provide embodiments with increasing levels of certainty of verification. of service policy usage control, as provided with Figures 26, 27 and 28.

Figure 31 is another functional diagram illustrating the device communications stack that allows 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 suitable device application processors, fast time to market needs, less service usage control needs, and / or other reasons that lead to a need for complexity implementation. lower.

Referring to Figure 31, which describes 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 upper layer, 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 top layer is shown as the transport layer, which includes TCP, UDP and other IP as shown. The session layer resides above the transport layer, which is shown as a connector assignment and session management layer (for example, basic TCP configuration, TLS / SSL). The network services API (for example, 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 using the network services API as shown. The network policy settings (for example, service settings) communicate with the policy implementation agent as shown. The connection manager communicates selection and control as well as modem and access network information through the modem controller as shown. Although Figure 31 does not represent all service use control verification functions provided by certain embodiments that request verification of additional service or control agents, a high level of certainty of service policy implementation verification can be achieved within the context. of the embodiments represented in Figure 31 applying a subset of the verification of use of service policy or manipulation prevention embodiments described herein. For example, the embodiments depicted in Figure 31 can be combined with the service controller embodiments used by IPDRs to verify that the service usage is in accordance with the desired service policy. There are also many other service use control embodiments described herein that can be applied in isolation or in combination to the embodiments depicted in Figure 31 to provide increasing levels of service usage control verification certainty, as will be evident to a person skilled in the art in view of Figures 26, 27 and 28 and the various embodiments described herein.

Figure 32 is another functional diagram illustrating the device communications stack that allows 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, Figure 32 provides somewhat greater complexity (for example, relative to the embodiments depicted in Figure 30) in exchange for the improved monitoring, control or verification of service that is possible by implementing additional agent embodiments, such as Roles of service monitoring agent and access control integrity agent.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Referring to Figure 32, which describes 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 in the bottom of the device communications stack. Measurement point II resides above the modem selection and control layer, which resides above the modem buses for each modem. Measurement point I resides between the policy implementation agent layer (policy-based router / firewall) and the transport layer, which includes TCP, UDP and other IP as shown. The session layer resides above the transport layer, which is shown as a connector assignment and session management layer (for example, basic TCP configuration, TLS / SSL). The network services API (for example, 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 using the network services API as shown. The network policy settings (for example, service settings) communicate with the policy implementation agent as shown. The connection manager communicates the selection and control as well as modem and access network information through the modem selection and control layer as shown. The service monitoring agent, which is also in communication with the agent communication bus 1630, communicates with various layers of the device communication stack. For example, the service monitoring agent performs monitoring at each of measurement points I and II, receiving information that includes application information, service use and other service-related information, and assignment information. An access control integrity agent is in communication with the service monitoring agent via the agent communications bus 1630, as also shown. As described similarly with respect to Figures 30 and 31, many of the service use control verification embodiments described herein can be applied in isolation or in combination in the context of Figure 32.

Figure 33 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments. Referring to Figure 33, which describes 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 device modems in the bottom of the device communications stack. Measurement point III resides above the modem selection and control layer, which resides above the respective modem buses for each modem. Measurement point II resides between the policy implementation agent layer (policy-based router / firewall) and the transport layer, which includes TCP, UDP and other IP as shown. The session layer resides above the transport layer, which is shown as a connector assignment and session management layer (for example, basic TCP configuration, TLS / SSL). The network services API (for example, 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 the application service interface agent in the device communications stack of Figure 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 communicates user information and decision inquiry and / or user input to the user service interface agent, as shown. The policy control agent communicates service settings and / or configuration information through this communications stack, as shown (illustrating such communications with a reference (B)) through the policy implementation agent layer. The connection manager agent communicates control and selection commands and / or modem and access network information through this communications stack, as shown (illustrating such communications with a reference (C)) through the selection and control layer of modem. Various other communications (for example, communications related to the service processor and / or service controller, such as service usage measurement information, application information) are provided at various levels of this communication stack, as shown ( illustrating such communications with references (D)) in the application layer and (E) in the policy implementation agent layer.

As shown in Figure 33, a service monitoring agent, which is also in communication with the agent communication bus 1630, communicates with various layers of the device communication stack. For example, the service monitoring agent performs monitoring at each of measurement points I to III, receiving information that includes application information, service use and other service-related information, and assignment information. An access control integrity agent is in communication with the service monitoring agent via the agent communications bus 1630, as also shown. As described similarly with respect to Figures 30, 31 and 32, many of the service use control verification embodiments disclosed herein may be applied in isolation or in combination in the context of Figure 33.

Figure 34 is another functional diagram illustrating the device communications stack that allows to implement traffic shaping policy, access control policy and / or monitoring policy of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service according to some realizations. In some embodiments, data path processing for the service processor is provided in conjunction with a single modem controller as shown. As shown, the processing of the service processor communication stack is provided below the conventional network communication stack and in combination with a modem controller (for example, and this approach can be extended to more than one modem) .

Referring to Figure 34, which describes 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 in the bottom of the device communications stack. Measurement point II resides above the modem controller layer 1. Measurement point I resides between the policy implementation agent layer (policy-based router / firewall) and the modem selection and control layer, for the modem controller stack 1 in this embodiment of a single modem controller. The transport layer, which includes TCP, UDP, and other IP, resides above the queue and IP routing layer, which resides above the modem selection and control layer, as shown. The session layer, shown as a connector assignment and session management layer (for example, basic TCP configuration, TLS / SSL), resides above the transport layer. The network services API (for example, HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer.

As shown in Figure 34, applications communicate with the device communications stack through the network services API as shown (illustrating such communications with a reference (A)). Policy settings from the network (for example, service settings) communicate with the policy implementation agent as shown (illustrating such communications with a reference (B)). The service monitoring agent, which is also in communication with the agent communication bus 1630, communicates with the policy implementation agent layer of the device communications stack. Also, the service monitoring agent performs monitoring at each of measurement points I and II, receiving information that includes application information, service use and other service related information, and assignment information. An access control integrity agent is in communication with the service monitoring agent via the agent communications bus 1630, as also shown. Various other communications (for example, communications related to the service processor and / or service controller, such as service usage measurement information, application information) are provided at various levels of this communication stack, as shown ( illustrating such communications with references (C)) in the policy implementation agent layer. Also, the billing agent, which is in communication with the agent communication bus 1630 communicates user information and decision inquiry and / or user input to the user service interface agent, as shown. As described similarly with respect to Figures 30, 31, 32 and 33, many of the service use control verification embodiments disclosed herein may be applied in isolation or in combination in the context of the Figure. 3. 4.

Figure 35 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments. In particular, Figure 35 illustrates an embodiment of single modem hardware as shown. As shown, the service processor network communication stack processing is provided in the hardware modem (for example, and this approach can be extended to more than one modem). This approach allows the service processor to be distributed as a conventional feature set contained in a software package modem chipset hardware or modem module or software package hardware, which, for example, can provide adoption easier or development by device OEMs, a higher level of differentiation for the chipset or modem module manufacturer, higher levels of performance or integrity of service use control implementation, or other benefits.

Referring to Figure 35, which describes 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 in the bottom of the device communications stack. As shown, measurement points I and II and the policy implementation agent reside in modem 1 (for example, implemented as hardware and / or software in modem 1). Measurement point I resides above the policy implementation agent layer (policy-based router / firewall), and measurement point II resides below the policy implementation agent later. The modem selection and control layer resides above the modem driver layer, as shown. The transport layer, which includes TCP, UDP, and other IP, resides above the queue and IP routing layer, which resides above the modem selection and control layer, as shown. The session layer, shown as a connector assignment and session management layer (for example, basic TCP configuration, TLS / SSL), resides above the transport layer. The network services API (for example, HTTP, HTTPS, FTP (File Transfer Protocol), SMTP (Simple Mail Transfer Protocol), POP3, DNS) resides above the session layer.

As shown in Figure 35, applications communicate with the device communications stack through

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

the network services API as shown. Policy settings from the network (for example, service settings) communicate with the policy implementation agent as shown (illustrating such communications with a reference (A)). The service monitoring agent, which is also in communication with the agent communication bus 1630, communicates with the modem policy implementation agent layer 1. Also, the service monitoring agent performs monitoring at each of the points of measurement I and II, receiving information that includes application information, service use and other service-related information, and assignment information. An access control integrity agent is in communication with the service monitoring agent via the agent communications bus 1630, as also shown. Various other communications (for example, communications related to the service processor and / or service controller, such as service usage measurement information and / or application information) are provided at various levels of this communication stack, such as sample (illustrating such communications with references (B)) in the policy implementation agent layer. As described similarly with respect to Figures 30, 31, 32, 33 and 34, many of the service use control verification embodiments disclosed herein may be applied in isolation or in combination in the context of Figure 35.

Figure 36 is another functional diagram illustrating the device communications stack that allows to implement traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments. In particular, Figure 36 illustrates a single modem hardware embodiment, in which modem 1 includes a portion of the service processor network interconnection communication stack processing and measurement points II and III and the agent policy implementation, as similarly shown in Figure 35, and the higher levels of the device communications stack above modem layer 1, such as the application service interface layer, are implemented in the device application processor or in the memory of the device application processor as described similarly above, for example, with respect to Figure 33, in which a measurement point I is shown between the interface agent of application layer service and the network services API layer. For example, this approach allows the application service interface agent to be provided in the device or memory application processor so that monitoring or control of application layer service usage can be implemented. For example, the differences between the embodiments depicted in Figure 36 and those in Figure 30 include a simplified implementation and a policy control agent that is fully implemented in 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 communicates user information and decision inquiry and / or user input to the user service interface agent, as shown. The policy control agent communicates service settings and / or configuration information through this communications stack, as shown (illustrating such communications with a reference (B)) through the policy implementation agent layer. Various other communications (for example, communications related to the service processor and / or service controller, such as service usage measurement information and / or application information) are provided at various levels of this communication stack, such as sample (illustrating such communications with reference (C) in the application layer and communications with reference (D) in the policy implementation agent layer). As shown, the service monitoring agent B communicates with the application service interface agent and the measurement point I, and the service monitoring agent A communicates with the policy implementation agent layer and the points of Measurement II and III of the modem 1. As described similarly with respect to Figures 30, 31, 32, 33, 34 and 35, many of the service use control verification embodiments disclosed herein may be applied. in isolation or in combination in the context of Figure 36.

Figure 37 is another functional diagram illustrating the device communications stack that allows implementing traffic shaping policy, access control policy and / or service monitoring policy in accordance with some embodiments. In particular, Figure 37 illustrates a device communications stack as similarly shown in Figure 36, the difference being that the service processor network interconnection communication stack processing is implemented in a function of hardware that is separate from the application processor and modem. For example, this approach provides security advantages with a specialized hardware system to protect some or all of the handling service use control system. For example, some or all of the service processor can be implemented in a SIM card module. As another example, some or all of the service processor can be encapsulated in a stand-alone hardware module that can be added to a device without the need to modify the network interconnect communication stack software or hardware.

Figure 38 is a functional diagram illustrating a processing flow of device service processor packets according to some embodiments. In particular, both an example upstream service processor packet processing flow (from the device to the network) and an example downstream service packet processing flow (from the network to the device) are shown. in the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Figure 38. For example, the service processor packet processing flow can be performed by the device communications stack, as described above with respect to Figure 29. The various embodiments for packet processing flow represented in Figures 38 to 40 are self explanatory to one skilled in the art and not all processing steps and flow sequences are described herein.

In some embodiments, the burst size, intermediate memory delay, acknowledgment delay and elimination rate used in shaping upstream and downstream traffic are optimized in order to reduce network access traffic overhead, and use of excess capacity that can result in mismatches in traffic transmission parameters with MAC and PHY access network or over-network protocol packet delivery re-transmissions. In some embodiments, an application interface agent 1693 is used to literally label or virtually label application layer traffic so that the policy implementation agent or agents 1690 have the information necessary to implement selected traffic shaping solutions. As shown in Figure 16, the application interface agent 1693 is in communication with various applications, which includes a TCP application 1604, an IP application 1605, and a voice application 1602.

Referring to Figures 38 to 40, in some embodiments, the upstream traffic service policy implementation stage corresponds to the traffic shaping stage described herein. Referring to Figure 38, this stage is depicted as an exploded view that includes four sub-stages upstream of QoS queue priority application, traffic shaping rules application, optimized buffer / delay network and remove application ID tag. An additional approach shown in Figure 38 involves two exploded view sub-stages associated with the firewall service policy implementation stage and these sub-stages are step / packet blocking and step / packet redirection. For example, the functions performed by these six sub-stages can be represented in any number of sub-stages, the order of the stages can be performed appropriately in several different orders to provide conformation of upstream traffic within the network communication stack. For example, Figures 39 and 40 show the two stages of policy and firewall implementation as one stage and the six exploded view sub-stages are included under the same policy implementation stage and are performed in a different order from that of Figure 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 Figure 38, there are two stages again called traffic service policy implementation and firewall service policy implementation in this example of traffic shaping, access control and firewall. These two stages of packet flow processing are represented as shown in the exploded view as the five sub-stages of labeling with flow ID, pass / block packet, apply QoS, apply traffic shaping rules and optimized network buffer , delay and elimination. As with the upstream packet processing flow, the number of sub-stages, the order of sub-stages and the location of the sub-stages in the downstream network interconnection stack processing can be represented in any number of sub-stages, order and / or location , and various other embodiments will be apparent to one skilled in the art, including embodiments that locate some or all of the stages in the application service interface layer or other layers as depicted in Figures 39 and 40. The details of the design of downstream packet flow processing can be somewhat more complex in certain embodiments compared to two-way upstream processing. First, as described herein, in some embodiments, packet labeling that requires application level information may require that the initial portion of the packet flow burst pass through the interconnect communication stack. upstream network 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 processor agent functions of service so that they can properly monitor or control the traffic associated with the flow.

Independently, another complication arises when reliable top-layer communication protocols, such as TCP, are used in the network interconnection stack in which the downstream transmission end repeats packet transmission if the TCP protocol stack Receipt does not send an acknowledgment of receipt (ACK) of package receipt within a certain period of time. If the packets are arbitrarily delayed or eliminated, then TCP re-transmission traffic can reduce, completely eliminate or even reverse the advantage of the network capacity obtained by reducing the average traffic speed or other transmission quality measure for one or more More service activities. To solve this problem, in some embodiments, the packet traffic control parameters (for example, downstream delay, eliminations, burst length, burst frequency and / or burst fluctuation) are optimized for TCP retransmission efficiency. so that changes in bandwidth or traffic control access speed for one or more service activities are implemented such that the TCP retransmission delay at the network transmission end is adapted to be the long enough to reduce wasted packet re-transmission bandwidth. In addition, and in combination or in isolation, in some embodiments, the packet traffic control parameters (e.g., downstream delay, eliminations, burst length, burst frequency and / or fluctuation

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

of bursts) can be adjusted so that MAC and / or PHY efficiencies are optimized downstream of access network.

Numerous other embodiments for the detailed implementation of packet flow processing both downstream and upstream will be apparent to one skilled in the art in view of the various embodiments described herein. In some embodiments, as described herein, the following is provided: (A) traffic shaping is performed in a verifiable manner, (B) traffic shaping is performed in such a way that results in network capacity improved by taking into account to some extent the way in which the PHY layer and / or the access network MAC layer respond to packet parameters (eg burst delay, burst eliminations, burst length, burst frequency and / or burst fluctuation), (C) traffic shaping is performed in such a way that it results in improved network capacity taking into account how the packet parameters (e.g., burst delay, burst eliminations, burst length , burst frequency and / or burst fluctuation) impact layer 3 and higher ACK protocol or other network protocol network capacity efficiencies, (D) packet shaping is performed The way that knowledge is known and optimized for the particular type of protocol or communication packets that are being sent (for example, TCP packets can be removed to slow down the transfer application rate while UDP packets are never eliminate, because there is no retransmission), (E) a virtual or literal packet labeling system is used in a verifiable traffic shaping service control system to provide a deeper level of service monitoring and control or to simplify packet processing, and / or (F) starting with this low level packet processing, traffic control or access control, building blocks can be added to one or more additional layers of higher level policy control in the device or network to create service profiles for the service provider network that define complete services, such as environment 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 processing stages or functions of low level traffic control, access control or firewall is also described herein. document.

Figure 39 is another functional diagram illustrating the processing flow of device service processor packets according to some embodiments. In particular, both an example upstream service processor packet processing flow (from the device to the network) and an example downstream service packet processing flow (from the network to the device) are shown. in Figure 39 (for example, one embodiment of a less abundant feature device service processor, such as one similar to that shown in Figure 32).

Figure 40 is another functional diagram illustrating the processing flow of device service processor packets according to some embodiments. In particular, both an example upstream service processor packet processing flow (from the device to the network) and an example downstream service packet processing flow (from the network to the device) are shown. in Figure 40 (for example, of a mid-category embodiment device service processor, such as one similar to that shown in Figure 33).

Figure 41 provides a table that summarizes various levels of privacy for generating service history information according to some embodiments. Many of these privacy levels have been described similarly above, and the table shown in Figure 41 is not intended to be a comprehensive summary of these privacy levels, but instead is provided as an aid to understanding these levels. of privacy in accordance with the embodiments described in this document related to user privacy. For example, there are many other parameters that can be associated with privacy filtering, and as will be apparent to a person skilled in the art in view of the various embodiments described herein, the unique feature of user-defined or influenced privacy filtering by the user for service use, service activity or CRM reports can be implemented with a variety of embodiments that are variations of those described herein.

Figures 42A to 42J provide tables that summarize various service policy control commands according to some embodiments. Many of these service policy control commands have been described similarly above, and the tables shown in Figures 42A through 42J are not intended to be a comprehensive summary of these service policy control commands and do not include summaries of All embodiments described herein, but instead are provided as a summary aid to understand these service policy control commands in accordance with various embodiments described herein.

In some embodiments, QoS is used for devices with a service processor 115. For example, QoS can be used in a busy hot spot where the profile of service processor 115 has been changed from WWAN to WLAN, but the WLAN is supported as Too many users are trying to use it. The service processor 115 may have a hierarchical access to the hot spot at that point; or service processor 115 that

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Pay less can be regulated while those who pay more can be opened; or service processor 115 may initiate a policy that slows down transmissions to improve trunk efficiency.

Figures 43A to 43B are flow charts illustrating a flow chart for a service processor authorization sequence as shown in Figure 43A and a flow chart for a service controller authorization sequence as shown in the Figure 43B according to some embodiments.

Referring to Figure 43A, at 4302, the device is in an offline state. In 4304, the service processor (for example, service processor 115) of the device collects device service processor credentials and access control integrity information. In 4306, the device service processor selects a better network. In 4308, the device connects to an access network. In 4310, the device service processor sends an authorization request to the service controller (for example, service controller 122) and also sends the credentials and access control integrity information. In 4312, the service processor determines if an integrity error has occurred. If so, then the service processor performs integrity error handling in 4314. Otherwise, the service processor determines if the device is activated and / or authorized for network access in 4316. If not, then the Service processor performs a device activation sequence in 4318. In 4320, the service processor performs the following: update critical software, initialize service policy and control settings, synchronize service counters, update service cost data, apply policy settings, apply CRM rules settings, obtain transaction identity certificate and send CRM and stored billing information. In 4322, the device is in an online state.

Referring to Figure 43B, in 4332, the device control is in an offline state. In 4334, the service controller (for example, service controller 122) receives a device authorization request, verifies the validity of the device service plan, verifies the validity of device access control integrity, verifies the information of device access control integrity, verifies the service processor operation indication, and performs various additional service processor integrity checks (for example, as similarly described herein). In 4336, the service controller determines whether all device integrity checks have passed. If not, then the service controller sends an integrity error to the service processor (for example, service processor 115) at 4338. In 4340, the service controller performs integrity error handling. Otherwise (all device integrity checks have passed), the service controller determines if the device is activated at 4342. If not, then the service controller sends an activation message to the service processor at 4344. In 4346, the service controller performs a service activation sequence. Otherwise (the device is activated), the service controller sends an authorization in 4348. In 4350, the service controller performs the following: update critical software in the service processor, initialize service policy and control settings, synchronize service counters, update service cost data, apply policy settings, apply CRM rule settings, obtain transaction identity certificate, send CRM and stored billing information. In 4352, the service controller is in a device online state.

Figures 44A to 44B are flow charts illustrating a flow chart for a service processor activation sequence as shown in Figure 44A and a flow chart for a service controller activation sequence as shown in the Figure 44B according to some embodiments.

Referring to Figure 44A, in 4402, a service processor activation sequence is initiated. In 4404, the service processor (for example, service processor 115) of the device displays an activation site (for example, HTTP site, WAP site or portal) to the user for the choice of user service activation. In 4406, the user selects the service plan, billing information and CRM information. In 4408, the service processor sends an activation request and user and CRM billing information to, for example, the service controller. In 4410, the service processor determines if there is an integrity error. If yes, then the service processor performs integrity error handling in 4412. Otherwise, the service processor determines if there has been a selection input error in 4414. If so, the service processor presents the User input selection error in 4416 and return to activation site / portal in 4404. Otherwise, the service processor identifies the service plan activated in 4418. In 4420, the service processor performs the following: update software Critical, initialize service policy and control settings, synchronize service counters, update service cost data, apply policy settings, apply CRM rule settings, obtain transaction identity certificate, and send cRm and billing information stored In 4422, the device is in an online and activated state.

Referring to Figure 44B, in 4432, a service controller activation sequence is initiated. In 4434, the service controller (for example, service controller 122) receives an activation request, which includes user and CRM billing information, and sends these to central billing. In 4436, the service controller receives a response from the central billing. In 4438, the service controller verifies the integrity of the service processor. If an integrity error is detected, then an integrity error is sent in 4440. In 4442, the service controller performs integrity error handling. In 4444, the controller of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service determines if 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 (the device has been activated), the service controller sends the service plan activation information to the device in 4448. In 4450, the service controller performs the following: update critical software, initialize service policy and control settings, synchronize service counters, update service cost data, apply policy settings, apply policy rule settings CRM, obtains transaction identity certificate, and sends CRM and stored billing information. In 4452, the service controller is in an online device and status activated.

Figures 45A to 45B are flow charts illustrating a flow chart for a service processor access control sequence as shown in Figure 45A and a flow chart for a service controller access control sequence such as It is shown in Figure 45B according to some embodiments.

Referring to Figure 45A, at 4502, the device is in an online state. At 4504, the service processor (for example, service processor 115) of the device processes any new operation indication message received from the service controller (for example, service controller 122). In 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. In 4508, the service processor performs access control integrity checks. In 4510, the service processor determines if there is any access control integrity error. If so, the service processor then performs integrity error handling in 4512. Otherwise, the service processor updates user service UI meters, provides notification if necessary, and accepts input if available in 4514 In 4516, the service processor sends new service processor operation indication messages to the operation indication message queue. In 4518, the service processor processes any pending billing transaction. At 4520, the service processor determines whether an operation indication transmission is due, and if not, returns to 4504 to process any received operation indication message. If so, in 4522, the service processor sends the new service processor operation indication message to the service controller.

Referring to Figure 45B, at 4532, the device is in an online state. In 4534, the service controller (for example, service controller 122) processes any new operation indication message received from the service processor. In 4536, the service controller performs access control integrity checks. In 4538, the service controller determines if there is any access control integrity error. If so, then the service controller performs integrity error handling in 4540. In 4542, the service controller updates the billing database, updates the CRM information, synchronizes service counters, updates the database cost if necessary, and synchronize CRM rules if necessary. In 4544, the service controller processes any pending billing transaction. In 4546, the service controller sends new service processor operation indication messages to the operation indication message queue. In 4548, the service controller determines whether an operation indication transmission is due, and if not, returns to 4534 to process any received operation indication message. If so, in 4550, the service controller sends the new service processor service message to the service processor.

Open content distribution and transaction system

Referring now to Figures 46 and 47A-B, in another set of embodiments a system based on open decentralized device is provided to enable central billing for third party electronic commerce transactions for mobile commerce as shown. For example, in these embodiments, device information may be embedded in HTTP, WAP or other browser / portal network header request information indicating that a central billing option is available for a compatible third-party transaction server, such as It is further described below with respect to Figures 46 and 47A-B.

Figure 46 is a functional diagram illustrating mobile commerce transactions based on open decentralized devices according to some embodiments. As shown, a service processor 4615 of the device 100 (for example, any mobile device that can store and run the service processor 4615) includes the access control integrity agent 1694, billing agent 1695, communication bus 1630 agent, 1697 user interface, 1692 policy control agent, 1696 service monitoring agent, 1693 application interface agent, 1690 policy implementation agent, and 1655 modem router and firewall, as similarly described in this document with respect to various other embodiments of service processor. In some embodiments, an application 4604 (for example, an HTML / WAP web browser) and a mobile payment agent 4699 are also included in the device, such as part of the service processor 4615 as shown. In some embodiments, application 4604 is not integrated as part of service processor 4615, but is executed and / or stored in the device. In some embodiments, mobile payment agent 4699 includes billing agent 1695, interface

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

1697 and / or 1693 application interface agent, and / or various other functional components / agents. As shown, service processor 4615 is in communication with an operator access network 4610, which is in network communication with Internet 120.

In some embodiments, the device information may be embedded in HTTP, WAP or other portal browser / network header request information indicating that a central billing option is available to a compatible third-party transaction server, such as the site. or open content transaction partner sites 134. For example, the compatible transaction server can then send a signed confirmation request through a control connector channel previously assigned to billing agent 1695 confirming billing agent 1695 the signed confirmation request by performing the signature verification locally based on a stored and synchronized list of approved transaction servers by passing the signed request on a 4630 billing server for confirmation. Optionally, in another example, a triangle confirmation can be established in which the billing server 4630 can confirm the transaction establishment with the transaction server 134, or the transaction server 134 can confirm the transaction established with the billing server 4630 Once the device confirms the compatible and approved status of transaction server 134, the device / transaction server pair can then optionally exchange additional keys for the rest of the transaction for enhanced security. In another example, transaction server 134 may also redirect the user browsing experience to one adapted to one or more of the type of device, service provider, device manufacturer or user. When the user selects a transaction, the transaction server sends a transaction invoice to the 1695 billing agent that describes the transaction and the amount. The billing agent 1695 may optionally confirm that the user's account has sufficient credit limit to make the purchase by confirming the credit limit stored on the device or by consulting the billing server 4630. The billing agent 1695 then invokes the UI of the 1697 device to display the transaction description and quantity and request user approval for billing through the central billing option. User approval can be obtained, for example, by a simple click operation or require a secure password, password and / or user biometric response. Upon user approval, billing agent 1695 generates a billing approval and sends it to transaction server 134, transaction server 134 completes the transaction and then sends an invoice to billing agent 1695. Billing agent 1695 sends optionally a confirmation to transaction server 134 and sends the invoice to billing server 4630. Again, a triangle confirmation can optionally be formed by the billing server that sends a confirmation to transaction server 134, or transaction server 134 can sending the invoice to billing server 4630. In some embodiments, billing server 4630 can also communicate such billed transactions to a central provider billing system 4623 via the operator access network 4610. Also, in some embodiments, a server alternative location billing 4632 it is in communication via Internet 120, and a central billing system of alternative location central provider 4625 is also in communication via Internet 120.

Figures 47A to 47B are transaction diagrams illustrating the mobile commerce transaction based on open decentralized device according to some embodiments. Referring to Figure 47A, device application 4604 scans (for example, based on the user issuing a scan request using a browser application) transaction server 134 (for example, a transaction web server, such as the open content transaction partner site 134). Transaction server 134 provides an offer to device application 4604. Device application 4604 selects a purchase (for example, based on the user selection entry). In response, transaction server 134 searches for an API connection with mobile device payment agent 4699, which then confirms the API connection. Transaction server 134 requests confirmation of user purchase (mediated by mobile device agent 4699 as shown), and the purchase is confirmed by device application 4604 (for example, based on the user's acknowledgment as similarly described above with respect to Figure 46). Transaction server 134 then transmits a purchase receipt, and device application 4604 confirms the receipt. Transaction server 134 then transmits the purchase invoice to the mobile payment agent of device 4699, which then sends the purchase invoice to the device billing server (for example, billing server 4630). The transaction server also optionally sends a purchase invoice confirmation to the device billing server for a triangle confirmation, as similarly described above with respect to Figure 46. The device billing server sends a copy from the purchase invoice to the central vendor billing system (for example, the central vendor billing system 4623).

Referring now to Figure 47B, device application 4604 scans (for example, on the basis that the user issues a scan request using a browser application) transaction server 134 (for example, a transaction web server, such such as open content transaction partner site 134), in which the scan request includes device ID information, as described similarly above with respect to Figure 46. Transaction server 134 establishes contact API with mobile device agent 4699, which then confirms the contact and validity for transaction purchases from the device. Transaction server 134 provides an offer to device application 4604. Device application 4604 selects a purchase (for example, based on the selection entry of the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Username). Transaction server 134 notifies the mobile payment agent of device 4699 of the description and amount of the purchase, and the mobile payment agent of device 4699 then requests confirmation of user purchase. The purchase is confirmed by the device application 4604 (for example, based on the user's acknowledgment as described similarly above with respect to Figure 46), and the device mobile payment agent 4699 then transmits a purchase confirmation to transaction server 134. Transaction server 134 then transmits a purchase receipt, and device application 4604 confirms the receipt. Transaction server 134 then transmits the purchase invoice to the mobile payment agent of device 4699, which then sends the purchase invoice to the device billing server (for example, billing server 4630). The transaction server also optionally sends a purchase invoice confirmation to the device billing server for a triangle confirmation, as similarly described above with respect to Figure 46. The device billing server sends the invoice Purchase to the central vendor billing system (for example, the central vendor billing system 4623). In some embodiments, the communications described above with respect to Figures 47A-B with the billing server and the central provider billing system are with the alternative location billing server 4632 and / or the central provider billing system of alternative location 4625 via Internet 120. Similarly, in some embodiments, transaction servers 134 are connected to Internet 120.

Therefore, these transaction billing embodiments do not require centralized storage or content or transaction exchange infrastructure. For example, transactions can be made over the Internet, and user experience and content can be adapted to normal experience and content versions of the transaction server / content provider. This approach provides a much broader range of content and transaction partners with no or minimal need to accommodate proprietary specialized systems. In addition, 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 contact message message transactions secure and signed 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 put the transaction partner on the compatible and approved list and exchange keys and / or security certificates . If a common user experience is desired by the service provider across multiple transaction partners, then the experience specifications for browser redirects can also be specified in the compatibility specification and tested before the transaction partner obtains approval. .

Design and test for service control

Figure 48 illustrates a network architecture that includes a service controller device control system and a service controller analysis and management system according to some embodiments. As described herein, the RAN gateway 410 generally represents the functionality of the various specific RAN gateway functional elements shown and / or analyzed herein. For example, these functional elements of the gateway of RAN 410 represent the gateways used to add the radio access network traffic functions, control, collection and roaming and / or other functions and are shown and / or analyzed herein. using other specific terminology for certain industrial standards, including the SGSN 410 gateway and the 508, 512, 608, 612, 708 and 712 gateways. Although the same reference numbers are used for the SGSN 410 gateway and the RAN gateway 410, it will be appreciated that the gateway of RAN 410 represents any or all of the functional elements of the gateway of rAn 410, 508, 512, 608, 612, 708, 712 or any other similar equipment or industry functions depending on the embodiment. Similarly, the transport gateway 420 represents the next higher level of gateway aggregation for the transport layer that is used in many networks, and this expression transport gateway 420 can be exchanged with any or all of the gateways 420, 520, 620 , 720 or any other similar equipment or industry functions depending on the realization. Those skilled in the art will appreciate that the gateway description applies to a respective embodiment in which the expressions RAN gateway 410, gateway 410, transport gateway 420 or gateway 420 are referred to herein.

Although the embodiments described below with respect to Figures 48 to 63 are represented in the context of a conventional multi-level access network, one skilled in the art will appreciate that such embodiments can also be generalized to other network topologies including the various topologies. flat network described in this document. As shown, the service controller is divided into two main functions (for example, in comparison to the service controller embodiments 122 depicted in Figure 16): (1) a service controller device control system 4825 and (2) a service controller design, policy analysis, definition, test, publication system 4835. The service controller device control system 4825 performs the functions of the device service control channel as described above. in this document with respect to various embodiments.

The service controller design, policy analysis, definition, test, publication system 4835 separates the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

service analysis, control policy design and publication of device service control channel functions. The service controller design, policy analysis, definition, test, publication system 4835 performs a variety of functions as described below. In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 provides use of statistical service analysis, notification policy or procedure response analysis and / or billing policy or response analysis. procedure for single devices, device groups, device types, user groups, user classes, or a complete set of devices and users subscribing to a given service. In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 detects, highlights and generates device service usage information, notification responses or billing behavior that is outside expected limits but That may or may not violate the policy. In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 provides service cost and profitability analysis for single devices, device groups, device types, user groups, user classes , or a complete set of devices and users that subscribe to a given service. In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 provides control of user service policy, statistical satisfaction analysis of notification policy or billing policy for single devices, groups of devices, device types, user groups, user classes, or a complete set of devices and users that subscribe to a given service. In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 provides statistical take rate analysis for transaction offers and billing offers for single devices, device groups, device types, user groups, user classes, or a complete set of devices and users that subscribe to a given service.

In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 provides service policy control definition work screens and "dry lab" (pre-beta) test versus Use database for single devices, device groups, device types, user groups, user classes, or a complete set of devices and users subscribing to a given service. In some embodiments, the service controller design, policy analysis, definition, test, publication system 4835 provides service policy control, notification policy test and / or beta billing policy (for example, using the server). 1658 beta tests) 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 known, then the beta test apparatus includes the offer system that provides user options to accept the beta test and provide feedback in exchange for an offer (for example, it shows them an offer page that is presented with existing subscription service or room service - offers a free trial, a discount for something and / or reward zone points (or other incentives / rewards) if they accept the test). In some embodiments, a beta test workstation (for example, in communication with the 1658 beta test server, such as the VSP 4920 remote workstation as shown in Figure 49) allows the beta test manager to define one or more beta test service control profiles, notification policy and / or billing policy. In some embodiments, the beta test workstation publishes each profile to specific (single) individual devices, device groups, device types, user groups, user classes, or a complete set of the devices and users that are paid 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, device groups or groups of users and compare real-time use in real time against beta test use objectives. In some embodiments, the beta test workstation allows the beta test manager to refine the service, notification and / or billing / transaction policies and republish 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 user feedback for a set of pre-designed user satisfaction questions or others regarding service usage. For example, questions can be presented through a pre-designed beta test portal or through a series of short pop-ups that arise when the user initiates a particular action or at a particular time. In some embodiments, the beta test workstation also collects service and device usage details (eg, CRM data) that beta test users have approved for collection. In some embodiments, the beta test workstation may decompose this data to determine if users are using the service in the manner intended by the beta test objectives. In some embodiments, the beta test workstation also allows multiple service variants and / or notification policy control settings to be published and to compare the service usage for each group with convenient displays with information presentations (e.g., statistical use versus time of day, use of particular activities, billing activity, device discovery activity, user response to message and notification 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 fully tested and approved for publication of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In production, the 1660 service download control server has a workstation screen that allows the service manager to specify which device group should receive the new service policy settings. In some embodiments, the service download control server 1660 allows the service manager to define specific individual (unique) devices, device groups, device types, user groups, user classes, or a complete set of devices and users who subscribe to a given service.

In some embodiments, a service (for example, a newly created or new version of an existing service) is tested and / or enhanced using a new service test model. For example, a new service (or a new version of an existing service) is loaded on a server to test, the new service is tested (optionally) against existing device usage statistics, a new service control definition (for for example, implemented as the service processor 115 for publishing 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 SDK) for the new service, it is developed and possibly adjusted based on the test against existing device usage statistics, the new service control definition is then published to beta devices ( for example, the various devices 100 used for beta testing of the new service), which then use the new service, are collected below. Service usage statistics and / or user feedback statistics (for example, to ensure that the service is functioning properly and so that the definition of service control can be adjusted to ensure adequate service, user experience and for the purpose of price / service profitability), the definition of service / service control is further refined based on the statistics of service usage / user feedback. Upon completion of the previous test and refinement of the service definition / service control, the service control definition can be published to groups of specified devices to use the new service. In some embodiments, this service control test model for device groups and service partners is provided by a virtual MVNO or VSP. For example, this allows new services to be developed, tested and proliferated more effectively and more efficiently.

In some embodiments, the service history IPDRs come from a network interconnection component connected to the core provider network 110 as represented by (for example, in real time) the use of service 118 (which as discussed in another part is a general purpose descriptor for a function located in one or more of the network interconnection equipment boxes). In some embodiments, service history IPDRs are collected / aggregated (in part) from central billing system 123. In some embodiments, service history IPDRs are collected / aggregated (in part) from transport gateways 420 In some embodiments, service history IPDRs are collected / aggregated (in part) from the RAN 410 gateways. In some embodiments, service history IPDRs are collected / aggregated (in part) from the base station or stations base 125 or a reading component co-located with the base station or base stations 125, a reading component in the transport network 415, a reading component in the main 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) definition and execution provisioning, (3) ATS activation owner, (4) service profile definitions, (5) activation and environment service definition, (6) billing rules definition, (7) billing process and controls brand, (8) invoice adjustments per account, (9) service usage analysis capabilities by device, subgroup or group, (10) beta test publication capabilities by device, subgroup or group, and (11) publication of production, perfected fit and re-publication.

Figure 49 illustrates a network architecture for an open developer platform for virtual service provider (VSP) partitioning according to some embodiments. As shown, the service controller design, policy analysis, definition, test, publication system 4835 is configured so that multiple “service group owners” (for example, the service provider for certain smartphones) or “Device group owners” (for example, electronic reader devices for the electronic reader service provider or providers) or “user group owners” (for example, IT for Company X for its employees' corporate mobile devices ), collectively referred to as the "Virtual Service Provider" (VSP), are served with the same service controller infrastructure and the same (or substantially similar) service processor design from the service provider workstation server virtual 4910 and / or remote station or workstations of virtual service provider 4920. As shown, l The 4920 virtual service provider remote station or stations communicate with the 4910 virtual service provider workstation server via VPN, leased line or secure Internet connections. The dashed lines shown in Figure 49 are shown 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, publication system 4835. Based on

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In the analysis herein, it will be apparent to one skilled in the art that the VSP 4910 workstation server may 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 functions related to network provisioning and activation discussed herein for the group of devices assigned to one or more VSPs, or for other reasons as will be apparent for an embodiment of VSP given.

In some embodiments, the service controller functionality is partitioned for a VSP by establishing up to one or more secure workstations, secure portals, secure websites, secure remote software terminals and / or other similar techniques to allow the manager of services that work for the VSP analyze, fine-tune, control or define the services that you decide to publish to one or more groups of devices or user groups that the VSP "owns" in some embodiments, the VSP "owns" such groups through 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 4910 and 4920 workstations only have access to the service analysis, design, beta testing, and publishing functions for the “proprietary” devices or users of the VSP. In some embodiments, the user or base device served by the central provider network is partitioned securely into those owned by the central provider, those owned by the VSP, and those owned by any other VSP.

In some embodiments, the VSP manages its devices from the VSP 4910 and 4920 workstations using device-based service control techniques as described herein. In some embodiments, the VSP manages its devices from the VSP 4910 and 4920 workstations using device-assisted and network-based service control techniques as described herein. In some embodiments, the VSP manages its devices from the VSP 4910 and 4920 workstations using network-based service control techniques (for example, DPI techniques) as described herein.

For example, this approach is particularly well suited for “open developer programs” offered by the central providers in which the central provider provides in the VSPs that offer special value in the devices or service plans, and using this approach, neither The central provider or VSP need to do all the work that would be required to establish a conventional MVNO or MVNE system, which often requires some degree of customization in the network solution, billing solution or device solution for each new application. device and / or service application that is developed and deployed. In some embodiments, service customization is simplified by implementing custom policy settings in the service processor and service controller, and the custom device is quickly carried on the network using the SDK and test / certification process. In some embodiments, VSP functionality is also offered by an entity other than the central provider. For example, an MVNE entity can develop a wholesaler relationship with one or more operators, use the service controller to create VSP capabilities, and then offer VSP services for a network or for a group of networks. In some embodiments, service customization is simplified by implementing custom policy settings through VSP realizations on the network equipment, which includes, in some embodiments, IP-based network equipment or service level that already has a level relatively deep capacity of service activity control. For example, using the embodiments described herein, and possibly also including some of the activation and provisioning embodiments, it is possible to effectively design and implement customized environment service plans that are different for different types of devices, different OEMs. , different VSP, different distributors or different user groups using all the same general infrastructure, if the service policy control implementation is achieved mainly (or exclusively) with service control based on network interconnection equipment (network), mainly (or exclusively) with device-based service control or with a combination of both (for example, device-based service control and hybrid network).

As discussed in this document, various VSP implementations to perform one or more of analyzing traffic use and defining, managing profiles or service plans, dry laboratory testing of profiles or service plans, beta testing of profiles or plans of service, refined adjustment of profiles or service plans, publication of profiles or service plans, or other policy related adjustments may involve programming settings on the network equipment and / or programming or software settings on the device. For example, as discussed herein, service processor settings are controlled by the service controller, which can be partitioned to allow device groups to be controlled. As another example, the equipment in the network involved with network-based service control, such as IP-based gateways, routers or switches, can be similarly programmed to use various VSP embodiments to implement that portion of the service profile (or service activity use control) which 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 achieved with the network functions instead of the device. Continuing this example, just as the service control settings functions of the service processor device service can have a group of devices that are partitioned and placed under the control of a VSP, various vSp control embodiments can partition a group of devices that have usage activity

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

of service controlled by the network interconnection equipment, which includes, in some embodiments, service control equipment based on IPR at the service level, to achieve similar objectives. It will be appreciated that the analysis of this document with respect to the service controller design, policy analysis, test, publication 4835, and the analysis with respect to device group, user group and other embodiments related to VSP, should be understood as applicable to various embodiments described in view of service control, assistance and / or device-based control monitoring, or service control, network-based control and / or monitoring assistance, or a combination of service control, control assistance and / or device-based monitoring and service control, network-based control and / or monitoring assistance. The various embodiments described herein related to service activation and provisioning can also make it clear how service control programming, service control assistance and / or network equipment monitoring can be implemented before and following device activation. . 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 that these techniques can be applied to central provider service realizations. , MVNO realizations and other realizations.

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 VSP, to develop various service processors (eg, different versions of service processor 115) to various devices (for example, different types of devices 100) and corresponding service controllers (for example, different versions of 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 (for example, mobile phone, PDA, e-book reader, portable music device, computer, laptop, portable computer or any other network accessible device). The device manufacturer can also preload / pre-install its new service processor on its own devices. In this example, users of the new device may then be able to use the new device for access network-based services using the new service processor, which communicates with the new service controller deployed, as similarly discussed herein. document in various embodiments. For example, the device can be pre-installed with the new service processor to provide environment services, as discussed in a similar manner herein in various embodiments. For example, the SDK can substantially allow 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 environment services for a group of devices, or devices associated with a certain service provider, a set of numbers (eg, dummy numbers) may be assigned for use in attempting to access through the access network using a new device that is not yet subscribed for the service. In some embodiments, the set of (dummy) numbers used for ambient access by the device may also be used for association of the device with a service provider or a type of device (e.g., electronic reader or some other type of accessible device of network), and after activation, the service provider assigns a real number for the activated device (for example, 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 after device activation). For example, the device environment access may use the device ID, SIM ID, assigned phone number (real or fictitious) and / or other information associated with the device to assign appropriate service control and service policy / profile for the device

In some embodiments, the service processor 115 is distributed as an SDK for any device with which the central provider or the VSP wishes to offer services so that the service processor 115 can be effectively designed or adapted by the OEM, ODM or manufacturer device for operation in the service network. In some embodiments, the SDK includes a complete set of service processor agent software 115 designed for and / or tested for the OS (Operating System) and processor set being used in the device, or a mature reference design for the OS and processor set that is being used in 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 used in the device ) that the OEM (Original Equipment Manufacturer) carries the desired So or processor set, or a basic set of sample 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 laboratory test procedures and / or test criteria to ensure that the implementation of the SDK service 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 SDK service is compatible with the service and will operate in an appropriate manner. In some embodiments, the certification procedures are approved for testing by the OEM, the central vendor, the VSP and / or a third party. For example, the central provider is typically responsible for the control of the SDK and the test procedures, although gold may be responsible for the control. In some embodiments, test procedures are at least partly common across multiple central provider networks. In some embodiments, the concept of

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

SDK is extended to include one or more modem modules where one or more of the SDK embodiments described above are combined with a conventional reference design or a conventional hardware sales package for one or more modems so that the complete package forms a comprehensive product that allows a device manufacturer, central provider, vSp or other entity to provide new devices or device applications in the central provider network possibly in combination with other networks in a way that requires less time and engineering resources and less network certification time and resources that would be required in some designs that do not use this conventional SDK approach plus module. For example, product implementations of conventional SDK plus module can be pre-certified and tested with one or more central suppliers to reduce development time and expenses. Conventional SDK embodiments plus module can also use multimode modem (for example, modems based on a set of CDMA, EVDO, UMTS, HSPA multimode chips such as the Gobi global multimode chipset product or modems based on other sets of LTE chips plus HSPA, WiMax chipsets plus Wi-Fi or LTE chipsets plus EVDo recently announced) and a multimode connection manager agent so that the same embodiment of SDK plus modem can satisfy a wide range of Applications for many service providers worldwide.

In some embodiments, at the time of manufacture, the device is associated with an MVNO. For example, the MVNO can provide an environment service that provides a service provider coordination center, in which the device can access a network in environment access mode (for example, a wholesale MVNO connection through of the access network) for the purpose of selecting a service provider (for example, a VSP, MVNO or operator). Based on the selection of the service provider, 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 in this document to provision the device and the account in that network service provider (for example, the ATS can track such activation, for example, for revenue sharing purposes, such as an activation incentive fee).

In some embodiments, the ATS is fully implemented in the network as described below. At the time of manufacture or at some time during device distribution, the device master agent programs a unique credential on the device that cannot be reprogrammed or deleted (or is difficult to reprogram or delete) and which can be recognized and registered by the network at the time of activation or at another time. In this way, even if other device credentials, possibly primary, are reprogrammed or deleted, there will still be a credential still associated with the device master agent. The ATS process can then be implemented 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. Examples of credentials that may be sufficient are the MEID, hardware MAC address and / or serial number, which are taken and recorded by the service provider or other service entity at the time of activation or before or after activation.

Interface server overlay for billing / IPDR data source mediation

Figure 50 illustrates a network architecture that includes a service controller billing interface to adapt minimal changes to central billing, AA and / or other existing network components in accordance with some embodiments. As shown, central billing system 123 includes mediation, customer service and billing databases, historical usage, billing system component 5010 and a billing interface component to service controller 5020. For example, the Service controller billing interface component 5020 allows the central billing system 123 to communicate effectively with the service controller (for example, the service controller device control system 4825).

In some embodiments, an interface server (for example, billing databases, historical use, billing system component 5010 and / or billing interface component to service controller 5020) is provided that reads IPDRs, service profile and / or service plan information stored in the database or billing databases and / or service record. In some embodiments, the interface server performs these functions in a manner that is compatible with communication formats of the database or billing databases and / or service record so that little or no change in configuration, formats is required. communication or central billing software, AAA and / or other existing network components. In some embodiments, the interface server (for example, which includes the billing databases, historical use, billing system component 5010 and the billing interface component to service controller 5020) is co-located with the components of the central billing system As shown, or in other embodiments, the interface server is located elsewhere. For example, the interface server can be located near or in the components comprising the service controller or anywhere else in the network.

In some embodiments, the interface server performs some translation of communication protocol or translation of data format required to interconnect the information stored in the billing database and / or service record to the service controller functions of so that the central billing system 123 and other existing components in the network do not need to change much (if any) to enable the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Service controller and service processor implement device-based service control. In some embodiments, the central billing system 123 or other network components is not required to have knowledge of the service control functions that are being implemented by the service controller or service processor, since the interface server obtains the Network-based information required by the service controller and / or service processor while requiring little or no specialized knowledge, communication, data formatting, user interface, service profile processing or service plan processing in the part of the billing components, database or existing network interconnection. In this type of overlay approach, various embodiments described herein can be used to rapidly improve 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 environment service plan may be implemented in the central billing system 123 that is associated with a zero or low cost billing plan and a usage limit (for example, environment service) that can be difficult or impossible to support in a way that would result in high user satisfaction and a high level of control for service cost and service policy definition. Even if the central billing system 123 is not highly involved in the process, the zero or low cost plan can be implemented in such a way that results in high user satisfaction and a cost controlled service using the service controller and / or service processor and the interface server to implement the functionality of environment services access control, service usage control, user interface, service notification use, transaction billing or invoice per account. For example, this approach can be implemented by reading the service plan and / or service policy settings for a device database in the central billing used by the interface server, looking for the corresponding service policy, user notification policy , transaction billing policy and invoice policy per account 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 levels 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 central billing system 123 and others. network components, all with minimal or no modification to the pre-existing network and billing system.

Another embodiment requests to receive a conventional IPDR data source 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 IPDR records for service policy usage verification and service usage notification synchronization with little or no need to modify existing billing or network device.

In some embodiments, duplicate IPDRs are sent from the network equipment to the billing system and / or network management system that are currently used to generate 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 the same level of information generation, lower level of information generation and / or higher level of information generation compared to the generation of information required by the central billing system.

In some embodiments, invoice billing compensation per account is provided using the interface server. For example, invoice billing compensation information by account is reported to the billing system through an existing data source by updating the billing database using the interface server. In some embodiments, transaction invoicing is provided using the interface server. For example, transaction billing registration information is provided to the billing system through an existing data source by updating the billing database using the interface server.

In some embodiments, user / existing service plan selection screens are presented to the user, a user choice or decision / entry is formed for a selected service plan, and then the service is implemented after confirmation of the system update billing for the new service plan. In some embodiments, the service is implemented upon user selection of a new service plan and then withdrawn if it is 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 source or by updating the database using the interface server.

Integrated service control

Figure 51 illustrates a network architecture for locating service controller device control functions with AAA and network service usage functions according to some embodiments. As shown, an integrated device service control, AAA, 5110 device usage monitoring system that integrates service controller functions (e.g., controller device control system) is provided

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

4825 of Figure 48) with access network AAA server functions 121 and network service use functions 118 (for example, in real time).

Figure 52 illustrates a network architecture for locating service controller device control functions in the access transport network according to some embodiments. As shown, the service controller device control system 4825 is located in the access transport network 415, or in some embodiments, on the 4G / 3G / 2G 410 RAN gateways (as indicated by the line discontinuous with the arrow), or alternatively, on the 4G / 3G / 2G 420 transport gateways (as indicated by the dashed line with the arrow).

Figure 53 illustrates a network architecture for locating service controller device control functions in the radio access network according to some embodiments. As shown, the service controller device control system 4825 is located in the radio access network 405, or in some embodiments, in the base station or base stations of 4G / 3G 125 (as indicated by the line discontinuous with the arrow), or alternatively, at the base stations of 3G / 2G 125 (as indicated by the dashed line with the arrow).

Environment services

In some embodiments, improved and simplified processes are provided to provision a device or user for service in a central provider network, an MVNO network or a virtual service provider (VSP) in the central provider network. In some embodiments, provisioning includes one or more of the following: a process or result of assigning, programming, storing or embedding a set of credentials in the device and / or in the network, or otherwise providing the credentials to the user; taking credentials at least in part on the device or with the user; and / or at least a portion of or a part opposed to the credentials being stored or recognized by the network so that the various network elements responsible for admitting device access to appropriate service activities do so once the device or User service is active.

As an example, as discussed herein, credentials may include one or more of the following: telephone number, device identification number, MEID or similar mobile device identifier, hardware security device ID, signature security or other security credentials, device serial number, device identification and / or credential information through security hardware such as a SIM, one or more IP addresses, one or more MAC addresses, any other identifier of network address, descriptive block of embedded device information (static or programmable), security key, security signature algorithms, passwords or other secure authorization information, service processor identifier (or similar device client or agent software ) or settings or version, device identifier type, browser (for example, http, https, WAP, other client d and browser) header or similar identifier information, browser token or similar identifier information, browser cookie or similar identifier information, embedded browser instructions, header or similar portal-client identifier information (for example, interface or agent of communication that connects to a network portal used at least in part for provisioning or activation for the device or by the user), portal-client witness information or similar identifier, portal-client cookie information or similar identifier, instructions of embedded customer portal, service provider, OEM, master agent (service distributor), VSP, device service owner identifier, distributor or master agent, and / or any information that the network can use to authorize network admission , provision the device, provision the network, activate service, authorize, associate or po enable the device with a provisioning sequence, associate or enable the device with one or more service profiles, associate or assist the device with an activation sequence, associate or enable the device with an environment profile or service experience, associate or enable the device with one or more service plans or service capabilities, associate the device with a service provider or service owner, associate the device with an OEM or master agent, associate the device with a distributor or master agent, or associate the device with a device group, user group or user.

In some embodiments, provisioning includes assigning, programming or embedding in 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 setting device settings and / or network settings to define an environment activation experience in which the device user receives a set of services after (for example, within a short period of time). later) buy or obtain or otherwise install the device if the device has been registered and activated or not with the device user or device owner.

In some embodiments, the environment experience is the user experience that is available at the time the device is sold at the time when the user has not yet registered for a service plan. For example, the environment experience is defined by an environment service profile, an environment service plan and / or the other service use activity control policies in effect on the network, on the device, or a combination from both. For example, if the device service processor is used in large

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

part to define the environment service profile, then the initial provisioning and activation settings in the service processor, and possibly the service controller, can define the user service improvement offer choices, access control possibilities network destination, traffic control policies, mobile commerce transaction capabilities (for example, to which transaction websites, WAP sites or portals the user can access purchase information, content, music, games and / or e-books), possible services of notifications or free weather or other modest Internet bandwidth that are provided free of charge to attract the user to use / improve the service or using transactions or viewing ads, ads that are presented to the user or what ad-based websites are exposed to the user, certain applications can be accessed while others are blocked (by For example, Internet-based text services have access but not email downloads), or other sample service capabilities. It will be apparent to one skilled in the art that allowing all of these services, and blocking other attempts of environment user service (eg, unpaid large file downloads or Internet uploads or viewing movies or other access that would consume wide bandwidth and would 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. Invoices per account, as discussed in this document, in which each service activity can be tracked, for example, separately with the monitor service and other agents and server functions to produce a billing compensation that allows The categorization and mediation of different billing entities (accounts) provides the ability for the service provider to individually account for the costs of each environment service item. This allows business models in which free access to the end user is paid or partially paid by one or more service provider partners that are billed for service access using the billing capabilities per account (for example, partners of transaction pay for user access to their transaction experience and maybe they pay a revenue share for transaction billing, advertising sponsored website partners pay for their access service sharing).

Although the service control capabilities of the service processor and invoice sharing on account of service cost and transaction revenue sharing in some cases can create a profitable environment business model, in other cases, environment services can be a potential source of losses for the service provider. Accordingly, in some embodiments, the ambient service capabilities may 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 may have a traffic control level for a period of time, and if the user has not registered for service at the end of the period, the environment service access is reduced by changing the policy control policy settings. service in the service processor, and the level of service may be further reduced over time if the user continues without registering for service or the user does not create too much transaction revenue. As another example, the recursive regulation algorithms analyzed herein can be used for one or more of the service activities offered in the ambient service mode so that the user experiences what the full speed service is like, and if the user continues to consume appreciable bandwidth with the service activity, then the activity is regulated back to reduce costs. In these examples, the service processor or service controller can issue a notification to the user explaining that their service is currently free, so their use is being regulated, and if they wish to receive better service, improvement plans can be delivered. UI service. It will now be apparent to one skilled in the art that the various environment service parameters, which include the provisioning and activation processes used to create the environment service activation, can also be managed by the VSP apparatus and the processes described in the present document For example, this allows the same service controller and service processor solutions to be used to define a wide range of environmental experiences for various device groups or user groups that are controlled by different VSPs.

Similarly, instead of controlling the environment service profile settings using the VSP functions to control the service controller, service processor, provisioning and activation settings, other embodiments request that the environment service profile settings are controlled by the network-based service activity control team as discussed in a similar manner in this document. Depending on the level of service control and sophistication of service monitoring (for example, highly advanced or service-level DPI techniques), some, many or most of all the environment service functionality described above can be implemented using service controls network-based and the VSP management and control embodiments described in this document.

In some embodiments, a device is suspended based on inactivity, or the device is placed in a suspended service state or suspended account statement, so that the network does not get stuck with a significant number of devices and credentials that are inactive. For example, this may also result in a portion of the device credentials being assigned back to an available pool instead of being reserved for that particular device (for example, phone numbers if phone numbers are scarce) . The device account and / or activation status can be reactivated when the device returns online. For example, the suspended status can be a simple suspension of services without changing the account statement, in which case the reactivation process can be automatically completed with a

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

subset or complete set of the activation sequence that occurs when the device is initially used as described herein. The suspended status may also involve changing the account status to inactive, in which case the reactivation process can automatically reconfigure the account status back to an active state when the device re-accesses the network. For example, the suspended state may involve unassigning or possibly claiming a portion of the device credentials. If a portion of the credentials is deallocated, then when the device re-accesses the network credentials they can be reassigned automatically 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 monitoring of deep service use, service control or control assistance, or service notification or notification assistance associated with a service profile in network device instead of the device, or implement some of the deep service monitoring, control, control assistance, notification or notification assistance on the device and others on the network. This is the case, for example, in a mixed network in which some devices have some, or at least one, or all the service processor capabilities discussed in this document, but other devices do not have any or as many of the capabilities of the service processor. Another example is for networks or devices that do not have any of the capabilities of the service processor or when it is desirable to do all service monitoring, control and notification on the network instead of on the device. As described below, Figures 54 to 63 represent various embodiments for combinations of service monitoring, control or control assistance, use notification or device notification assistance based on and / or service monitoring, control or assistance. of control, notification of use or assistance of notification of use based on network.

Figure 54 illustrates a network architecture for locating service controller device control functions with AAA and using network service that includes deep packet inspection functions in accordance with some embodiments. As shown, an integrated device service control is provided, a 5410 device usage monitoring system that integrates service controller functions that includes a deep packet control (DPC) 5402 policy implementation function with server functions AAA access network 121 and service usage functions 118 in real-time network. In the following analysis, it is understood that the AAA 121 server function may be relocated to another point in the network or network equipment partition without loss of generality. It is also understood that many of the functional partitions described for the various embodiments in the integrated device service control, 5410 device usage monitoring system can be redesigned without loss of applicability, function or generality. Finally, it is understood that one or more of the functional elements described in the integrated device service control, 5410 device usage monitoring system can be eliminated for simplified embodiments and that not all of the functionality described herein is necessary in some realizations

In some embodiments, the integrated device service control, 5410 device usage monitoring system provides network based monitoring or service control that satisfies various network neutrality and / or privacy requirements based on indication or indications received from the device or user (for example, user input provided using the device UI using service processor 115; user input provided through another WAP website, site or portal; or user input provided through the user agreement service where the user agrees to the levels of monitoring and / or service control) and network-based service control using a DPI 5412 service monitor and / or DPC 5402 policy implementation.

In some embodiments, the integrated device service control, 5410 device usage monitoring system provides network-based service monitoring or service control that satisfies various privacy requirements using the indication or indications received from the device or user (by for example, user input provided using the device UI using service processor 115; user input provided through another WAP website, site or portal; or user input provided through the service contract where the user agrees service monitoring and / or control levels) and network-based DPI service usage monitoring or DPC policy implementation using the DPI 5412 service monitor or DPC 5402 policy implementation as described below. In some embodiments, the DPI 5412 service monitor and / or DPC 5402 policy implementation includes a secure database for storing service monitoring and CRM information for each device / device user. In some embodiments, the DPI 5412 service monitor and / or DPC 5402 policy implementation may be integrated with the integrated device service control, 5410 device usage monitoring system (as shown) or provided on a separate router. , server, and / or function implemented in software / hardware that is in secure communication with the integrated device service control, 5410 device use monitoring system 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 the DPI 5412 service monitor or DPC 5402 policy implementation but is in secure communication with the DPI 5412 service monitor or DPC 5402 policy implementation, control

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

of integrated device service, 5410 device usage monitoring system and / or other network elements depending on the architecture (for example, a billing server or any other network element). In some embodiments, the user selects limits and / or restrictions on who can access the service history of remotely stored service and / or other data related to CRM / privacy (e.g., CRM / privacy guardian settings), and, by For example, other network elements and / or network administrators accessing such data may be limited and / or restricted accordingly. For example, access to such stored service monitoring and CRM information may require certain security credentials and / or use various other well-known secure data storage techniques, such as the various secure storage techniques described herein.

In some embodiments, the secure database that has user service usage information that is considered sensitive and has not been approved for distribution by the user may be made unavailable for credentials owned by network managers or network functions. except, for example, for emergency service situations or monitoring needs ordered by the government where special credentials are provided outside secure storage that are not normally available. In some embodiments, instead of selecting the user the limits, a certain set of restrictions is assumed unless the user selects information filtering settings that allow more information to be shared with the network functions, network administrators or network partners. service provider In some embodiments, the information is filtered to remove information that is thought to be sensitive but service usage information necessary to monitor network services or other important parameters is still transmitted. For example, the website destinations that a user is visiting can be classified with generic identifiers that are not decodable or the individual website information can be completely deleted. Many other examples will be apparent to an expert in the field.

For example, service monitoring and stored CRM information can also be organized into groups to define group CRM profiles to store service monitoring information for each user indexed by user credentials (for example, such groups can also be used for various functions related to VSP, as described in this document). The DPI 5412 service monitor or DPC 5402 policy implementation also uses secure storage to store service monitoring information for each user indexed by user credentials or another aspect of the device identifier or address assignment (for example , IP address or MAC address). In some embodiments, a CRM information manager (for example, a supervisory program running in the integrated device service control, 5410 device usage monitoring system) communicates with the other network functions and provides service usage. and CRM information filtered according to CRM filtering rules for each user or for user groups. In some embodiments, the filtered CRM data may be made available using secure communications with other network interconnection equipment by the integrated device service control, use monitoring system 5410. In some embodiments, the filter settings for some users allow that more information on the use of secure service information be shared than others due to differences in user preference settings and / or service plan agreements.

In some embodiments, user privacy preference information is used to determine privacy filter settings, which are safely implemented by the integrated device service control, 5410 device usage monitoring system. For example, the CRM filter settings can be received at the time of service contract registration (for example, service plan selection) and / or allow the user to log in to the service preferences web page to change settings (for example, without involving any interaction with local software on the device). As another example, the software on the device (for example, which includes service processor 115) can be used to select CRM preferences / user privacy, which are communicated securely to the integrated device service control, monitoring system 5410 device usage (for example, the device may include credentials that can be verified to allow selection / modification of CRM / privacy preferences or other user-based preferences maintained securely on a network server, such as service control of integrated device, 5410 device use monitoring system or other network element, as shown in various other embodiments described herein). In these examples, the filtered CRM data is available from the integrated device service control, 5410 device use monitoring system for other network components through a secure or open communication link. In another example, CRM / user privacy preferences are entered using a web server hosted by the integrated device service control, 5410 device usage monitoring system or central billing system 123. In another example, the software in the device (for example, which includes service processor 115) it can be used to securely communicate user preference decisions to an intermediate server that acts as a device manager and intermediate server for devices or groups of devices and control of integrated device service, 5410 device usage monitoring system.

In some embodiments, the integrated device service control, 5410 device usage monitoring system provides network based service control as described below. In some embodiments and similar to the network-based CRM filtering embodiments described above, the dPi 5412 service monitor or DPC 5402 policy implementation includes secure storage (for example, a

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

secure database) to store service monitoring information (for example, based on user selections / preferences), and DPC 5402 policy implementation performs traffic algorithm / regulation shaping for each user based on the monitoring information of service stored from the DPI 5412 service monitor. For example, the inspection of network-based DPI traffic by the DPI 5412 service monitor can use secure storage to save service monitoring information for each user indexed by the users. User credentials or other parameters, such as IP address or other network tag. As another example, the DPC 5402 policy implementation, for example, which can be monitored by policy management server 1652 as described herein with respect to various other embodiments, can implement statistical analysis of service usage history. within secure storage and maintain a history of service usage history for each device / user and / or perform various traffic shaping and / or regulation algorithms based on various settings related to the device, selected by the user and / or with service plan (for example, for network neutrality purposes) that allow various higher level service use objectives for one or more users, as similarly described herein with respect to various use monitoring embodiments device-based service (for example, except for certain encrypted or stream network traffic flows jos related to the application for which traffic control generally needs information from the application level and / or content specific traffic control).

In some embodiments, the entry on how to implement service control (for example, from the user of the device) is collected. For example, such an entry can be determined based on one or more of the following: a choice of service plan for the device; input provided by a user through a website (for example, web-based portal) to indicate changes to service control policies, as described similarly above; input provided by a user through the device (for example, which includes service processor 115), which securely communicates the input to the DPC 5402 policy implementation, for example, which can be monitored by the policy management server 1652; and input provided by a user through the device (for example, which includes service processor 115), which securely communicates the entry to an intermediate server for DPC 5402 policy implementation, as described similarly above. . In some embodiments, such service control is based on various algorithms as described herein that identify the most intensive service activities and recursively control the speed for those activities while leaving others unaffected, and in such a way that Specify or select by the user to ensure network neutrality. In some embodiments, the user is offered a choice to control service use and / or select an algorithm that controls all activities equally / neutrally (eg, based on selected user preferences). For example, implementing service control algorithms that are network neutral (for example, regulating all activities equally or regulating higher use algorithms without singling out certain activities to regulate unless they meet certain neutral network usage history or criteria usage statistics), or that are approved, selected or otherwise specified by the user, traffic control or neutral network service usage control may be maintained.

In some embodiments, the DPI 5412 service monitor, possibly in conjunction with the service usage notification 5420 and / or the service history server 1650, provides notifications related to service usage / service cost (e.g., a real-time service usage counter) to the device based on user preferences, as similarly described above with respect to various notification embodiments related to device-based service / service use. For example, the DPI 5412 service monitor, for example, in conjunction with the service usage notification 5420 and / or service history server 1650, can perform notification algorithms related to service / service usage based on one or more than the following: service plans, device settings and / or user preferences selected (for example, such notification messages can be safely communicated to the device and / or the device through an intermediate server). For example, the policies governing how the user is notified of service use or service cost can be determined by policy management server 1652 and / or service use notification 5420. As another example, acknowledgments of receipt of Important notification messages and / or user choices related to important service usage decisions may be requested, as discussed in a similar manner previously regarding device-based use / control realizations, which may then be communicated to the system. Central billing 123 as confirmation for any important notification message of this type (for example, related to charges for additional use of service use and / or confirmation of service improvements). In some embodiments, various other service use algorithms related to projections of service use and / or direct service cost described herein are made with respect to projections of direct service use based on a network device, such as by the integrated device service control, 5410 device usage monitoring system, and such direct projections can then be communicated to each respective device as service usage notification messages (for example, using an insert-based approach (started on the network) and / or extraction-based approach (initiated by a request from the device)). For example, these embodiments for projected service use methods, as described herein, may be useful in determining when the user is using services in such a way that will cause the user to exceed a service limit so that it can be notified. to the user, or the service can be controlled or regulated if the user has selected a control or regulation option.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, one or more intermediate servers are provided for balancing and / or unloading workload of the integrated device service control, 5410 device usage monitoring system and performing one or more of the functions described above with respect to various embodiments of the integrated device service control, 5410 device usage monitoring system. In some embodiments, service plans, device settings, and / or selected user preferences are used to associate each device / user with a pre-profile -programmed to more effectively associate such devices / users with their selected service plans, device settings and / or user preferences. For example, the process that establishes a service profile for a given device can be determined by assigning the device to a service flow that has the predefined service profile and is shared with other devices in the integrated device service control, monitoring system 5410 device usage instead of individually processing service flow manipulations for each device. In some embodiments, the act of provisioning and activating a service profile for a given device implies establishing the definition and service flow identifier in the integrated device service control, 5410 device usage monitoring system (if it is not already set) and then assign the routing of the device credentials to that service flow identifier. User preferences can be taken into account, for example, to assign the device service flow to one of several predefined profiles based on user preferences that are all supported under the same service plan. For example, a service flow profile may request service use notification but not control under the same service plan as another service flow profile that requests less notification but active service use control to maintain user costs at a service level. monthly post-payment limit.

In some embodiments, the billing by account function is implemented in the context of the integrated device service control, 5410 device usage monitoring system or other network-based system embodiments described herein. For example, the DPI 5412 service monitor, in some cases in conjunction with the 1650 service history server, can operate in conjunction with the billing policy settings per account stored on the billing event server 1662 so that the Service activities are divided into the account classifications defined by the service profile settings. Invoice data sources per account can then be sent to the billing system or to an intermediate billing event aggregation server that collects this type of deep packet inspection information generated from one or more integrated device service control units , 5410 device usage monitoring system to aggregate and format the information in such a way that it can be used by the central billing system 123. In some embodiments, the billing information per account collected in a network box as the service control For integrated device, 5410 device usage monitoring system is augmented by the invoice account information collected on the device as described herein, and any intermediate server can be used to aggregate and format these sources of invoice data by account so that the central billing system deals with both types of data, from the network and from the devices.

As shown in Figure 54, in some embodiments, the 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 (for example, with respect to Figure 16 and other embodiments described herein) to communicate with the device service processors 115. In some embodiments, the billing server 1662 in the integrated device service control, system 5410 device usage monitoring detects service usage events reported by the DPI 5412 service monitor, in some cases in conjunction with the 1650 service history server, generates a billing event that can be registered or transmitted to the system central billing 123. In some embodiments, billing server 1662 receives information from the billing agent of device 1695 and / or the device service monitoring agent 1696 and transmits the device service usage billing events to the central billing system 123. In some embodiments, certain billing events that are advantageously collected on the network (for example, the DPI 5412 service monitor and / or the billing event server 1662) are combined with certain billing events that are advantageously collected on the device (for example, the service monitoring agent 1696 and / or billing agent 1695), and both sources of billing information are transmitted to billing system 123. Similarly, in some embodiments, certain service usage information is collected with the service usage monitor agent 1696, and that information is combined with service usage information collected from the DPI 5412 service monitor and / or 1650 service history server and / or us or service 118. In some embodiments, certain aspects of service are controlled using the 5402 network-based DPC policy implementation, in some cases in conjunction with or supervised by the 1652 network-based policy management server, and other aspects of service are controlled using the device-based policy implementation agent 1690, in some cases in conjunction with or supervised by the policy control agent 1692. As will now be apparent to a person skilled in the art in view of the numerous embodiments described In this document, many hybrid approaches for service use monitoring, service control, service notification or service billing can be achieved with some aspects of the policy, notification, control, monitoring or billing that are implemented / performed on the device of device described in this document and others implemented / performed on the network device described in this document. The presence of the access control integrity server 1662 and many other service control verification embodiments described in

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

This document makes it clear that the embodiments of the integrated device service control, 5410 device usage monitoring system also provide affirmative verification of any functions that are implemented in the device. It will also be clear that all previous combinations of the device and network functions, and many others, can be achieved in ways that are network neutral and / or protect user privacy preferences by implementing service control algorithms in a neutral network manner. and / or receive user preference input on how to implement service control, and maintaining CRM security service and information use and filtration on both the device 100 and the network-based integrated device service control, monitoring system 5410 device use.

In some embodiments, the integrated device service control, 5410 device usage monitoring system facilitates or plays a part in the provisioning and automated activation of the devices as described in a similar manner above with respect to various provisioning embodiments and Automated activation based on device. In some embodiments, the activation server 160 is integrated into, or partially integrated into, the device service control, device usage monitoring system 5410.

In some embodiments, the integrated device service control, 5410 device usage monitoring system facilitates environment services as described similarly above with respect to various embodiments of device-based environment services.

In some embodiments, the integrated device service control, 5410 device usage monitoring system 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 that include deep packet inspection functions can be used in a similar manner as will be apparent to one skilled in the art in view of the various embodiments described herein.

Figure 55 illustrates another network architecture for locating service controller device control functions with AAA and using network service that includes deep packet inspection functions in accordance with some embodiments. As shown, service processor 115 is not present in devices 100, and integrated device service control, device usage monitoring system 5510 performs all functions of service monitoring, service control, billing and notification. .

Figure 56 illustrates an activated gateway for 4G / 3G / 2G DPI / DPC according to some embodiments. As shown, a gateway activated for DPI / DPC of 4G / 3G / 2G 5610 (for example, implemented in either gateway 420 or gateway 410 or a combination of both) where the functions of conventional service gateway 5616 (for example, routing, switching, translation / tunneling of protocol, collection data function (CDF), collection gateway function (GCF), mobility management and / or suspension / resume) are combined with one or more of the following embodiments and integrated into one or a combination of the service gateways (for example, RAN and / or transport gateways): DPI 5412 service monitor, 1650 service history server, device use 118, policy implementation DPC 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 (for example, used to represent the I / O port or ports for the gateway), and / or DPI / DPC 5622 gateway control plane link (for example, used to represent the control plane network channel which connects the previous elements to another network equipment and in communication with the gateway control communication 5620). The packet processing architecture shown in this figure requests a multipoint to multipoint backplane bus scheme, but it will be apparent that other data path configurations including serial are possible. As will also be apparent, the configuration described above can also be applied to any of the transport gateway 420 and / or the RAN gateway 410. As mentioned above, it is possible to maintain secure storage in the 4G DPI / DPC gateway / 3G / 2G 420 or 410 that requires secure credentials to enter so that user privacy is protected and service usage information or CRM information is filtered according to user preferences before sending to another network function or network manager, and the same concessions can also be applied for emergency or government monitoring purposes. Network neutrality can also be maintained in this configuration by maintaining network neutrality in the service control algorithm and / or requesting user input on how to control service usage as discussed above for other network service control implementations or as It is analyzed in the device-based service control descriptions.

In some embodiments, the billing by account function is implemented in the context realization of the 4G / 3G / 2G 5610 DPI / DPC gateway or other network-based system embodiments described herein. For example, billing information per account can be derived completely from the network box (for example, 4G / 3G / 2G 5610 DPI / DPC gateway) without assistance of device-based service or billing monitoring capabilities, or There may be none on the device. In this example, the DPI 5412 service monitor, in some cases in conjunction with the 1650 service history server, can operate in

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

together with the invoice policy settings per account stored on the billing event server 1662 so that the service activities are divided into the account classifications defined by the service profile settings. The invoice data sources per account can then be sent to the billing system or to an intermediate billing event aggregation server that collects this type of information generated from deep packet inspection from a 4G / DPI / DPC gateway units. 3G / 2G 5610 to add and format the information in such a way that it can be used by the central billing system 123. In some embodiments, the billing information per account collected in a network box, such as the DPI / DPC gateway of 4G / 3G / 2G 5610, is augmented, redefined or otherwise added to the billing account information collected on the device as described in this document and any intermediate server can be used to aggregate and format these data sources. bill by account so that the central billing system deals with both types of data, from the network and from the devices.

Figure 57 illustrates a network architecture that includes the VSP 4910 workstation server in communication with the 4G / 3G / 2G 410 and 420 DPI / DPC gateways in accordance with some embodiments. As shown, the VSP 4910 workstation server is in communication with the 4G / 3G / 2G 410 and / or 420 DPI / DPC gateways, the service controller design, policy analysis, test, system publication 4835, and / or other network interconnection elements that possibly include central billing system 123, mobile wireless center 132 (HLR) and / or aAa 121 server for the purpose of provisioning and / or control adjustments in the 4G / 3G / 2G 410 and / or 420 DPI / DPC gateways, mobile wireless center 132 and possibly other equipment for the purpose of implementing a portion of the VSP open partner functionality discussed herein. In Figure 57, the functionality of the 4G / 3G / 2G 5610 DPI / DPC gateway as shown in Figure 56 is implemented in the 4G / 3G / 2G 410 DPI / DPC RAN gateway and / or the gateway 4G / 3G / 2G 420 DPI / DPC transport as described similarly above. For example, VSP functionality can also be used to establish higher-level policies associated with the 4G / 3G / 2G 420 or 410 DPI / DPC gateway, such as provisioning or activation profiles or policies, service profiles or policies. environment and / or invoice service profiles per account or the other service profile or higher level service plan analyzes discussed in this document. In some embodiments, the provisioning and / or activation stages described herein involve adjusting service policies on the 4G / 3G / 2G 420 or 410 DPI / DPC gateway. In some embodiments, the environment or activation services of environment involve establishing service profiles on the 4G / 3G / 2G 420 or 410 DPI / DPC gateway that allow for desired activities and block unwanted activities. For example, these settings may be included as part of the open service provider partner programming capabilities of the VSP 4910 workstation server embodiments.

Figure 58 illustrates another gateway activated for 4G / 3G / 2G DPI / DPC according to some embodiments. As shown, a 4G / 3G / 2G 5810 DPI / DPC gateway is provided (for example, implemented in any of the gateway 420 and / or gateway 410) in which the service processor connection (for example, via the service control server link 1638 as shown in Figure 56) is not present so that all service monitoring, control, collection and transmission of billing and notification events are performed by the DPI / DPC gateway of 4G / 3G / 2G 5610 (for example, gateways 410 and / or 420).

Figure 59 illustrates another network architecture that includes the VSP 4910 workstation server in communication with the 4G / 3G / 2G 410 and 420 DPI / DPC gateways, the AAA 121 and the mobile wireless center 132 in accordance with Some realizations. As shown, Figure 59 provides a network diagram corresponding to Figure 58, with functionality similar to the embodiment shown in Figure 57, in which service processors 115 are not present in devices 100. In Figure 59, the functionality of the 4G / 3G / 2G 5810 DPI / DPC gateway as shown in Figure 58 is implemented in the 4G / 3G / 2G 410 DPI / DPC RAN gateway and / or the transport gateway of 4G / 3G / 2G 420 DPI / DPC as described similarly above.

Figure 60 illustrates an activated gateway for 4G / 3G / 2G DPI / DPC and service controller device control system according to some embodiments. In some embodiments, enhanced network-based service monitoring, control, billing and notification as discussed above are implemented using a gateway activated for 4G / 3G / 2G 6010 DPI / DPC and the device controller device control system. 6025 service as shown. In some embodiments, the functions shown in the figure to be within the service controller device control system 6025 have been moved from the 4G / 3G / 2G 5610 DPI / DPC gateway of Figure 56 (for example, or from gateways 410 and / or 420) so that they reside in a separate server embodiment or other network equipment function separate from the DPI / DPC gateway of 4G / 3G / 2G 6010. For example, this architecture can be used when the network equipment manufacturer wishes to separate these functions or has an existing product that is desirable to improve by adding a separate box. As another example, this architecture can be used when the 4G / 3G / 2G 6010 DPI / DPC gateway cannot be maintained with large numbers of individual user profiles so that it is desirable to move to a scalable server configuration where it can be applied. Load balancing with a potentially more flexible programming environment to implement service policy management functions, statistical service history analysis algorithms, service usage projection and / or service control (or regulation) algorithms. In some embodiments, secure storage is provided on the 4G / 3G / 2G 6010 DPI / DPC gateway and / or the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

6025 service controller device control system that requires secure credentials to obtain information so that, for example, user privacy can be protected and service usage information or CRM information can be filtered according to user preferences before of sending to another network function or network manager, and the same concessions 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 construction of the service control algorithm and / or requesting user input on how to control service usage as discussed above for other implementations of network service control or as discussed in the device-based service control descriptions.

Figure 61 illustrates another network architecture that includes the VSP 4910 workstation server in communication with the 4G / 3G / 2G 410 and 420 DPI / DPC gateways, AAA 121 and the mobile wireless center 132 according to some realizations In Figure 61, the functionality of the 4G / 3G / 2G 6010 DPI / DPC gateway as shown in Figure 60 is implemented in the 4G / 3G / 2G 410 DPI / DPC rAn gateway and / or the gateway 4G / 3G / 2G 420 DPI / DPC transport, as described similarly above, and that are in communication with the 6025 service controller device control system as shown.

Figure 62 illustrates another gateway activated for 4G / 3G / 2G DPI / DPC and service controller device control system according to some embodiments. As shown, the ability to communicate with service processor 115 has been removed so that all service monitoring, control, collection and transmission of billing event, and notification are performed by the 4G / DPI / DPC gateways. 3G / 2G 6210 (for example, implemented on gateways 410 and / or 420) in conjunction with the service controller device control system 6225 without assistance from service processors 115.

Figure 63 illustrates another network architecture that includes the VSP 4910 workstation server in communication with the 4G / 3G / 2G 410 and 420 DPI / DPC gateways, AAA 121 and the mobile wireless center 132 according to some realizations In Figure 61, the functionality of the 4G / 3G / 2G 6210 DPI / DPC gateway as shown in Figure 62 is implemented in the 4G / 3G / 2G 410 DPI / DPC rAn gateway and / or the gateway 4G / 3G / 2G 420 DPI / DPC transport, as described similarly above, and that are in communication with the 6225 service controller device control system as shown.

As will be apparent to one skilled in the art, the above-described embodiments may be extended to include some or all of the functions depicted in the 4G / 3G / 2G DPI / DPC service gateways of Figure 56 on the base station or controller of base station 125.

Provisioning and activation

In some embodiments, provisioning and automatic activation include automation of one or more of the following functions: (1) program device credentials or partial credentials and register them in a database (or provide them when programmed into the device), (2) associate these credentials with the appropriate provisioning and / or activation actions to be taken on the device and on the network, (3) direct the device to the appropriate activation sequence function (e.g., activation server) when you try to connect to the network, (4) complete the provisioning of the device, (5) program the AAA, billing system, gateways, mobile wireless center and other network equipment to the appropriate initial service control device settings, and (6) establish a service account for the device.

In some embodiments, improved processes are provided to activate service for a device or user with a network service provided by a central provider network, an MVNO network or a VSP in the central provider network. In some embodiments, the activation includes one or more of the following: a process or result of association of a service account with device or user credentials; the service account being additionally associated with a service profile that defines the service activities that the device is authorized to access; create or update a service usage or billing record and associate it with the service account to create a service plan; and / or start the service to the device or user in which the network equipment allows access to the appropriate level of service activities. In some embodiments, the VSP embodiments include the provisioning and activation apparatus embodiments in 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 applications, low cost or user-friendly device or service, since the process can often be complicated, 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 adapts a wide variety of device types and service profile types, with the ability to perform provisioning and activation at a number of points in the manufacturing progression. , distribution, sales and use for the device, and the ability to

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

pre-activate before the first use of the device or activate very quickly during the first use of the device (or during some subsequent 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 activate the device later, as well as, in some embodiments, create database entries and other credential associations in the network so that the network and / or the 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 used in each network function (for example , required) and / or each device function (for example, required) so that the system can properly associate the device credentials with the appropriate service activity policies, and then support the device on the network. The term activation may also refer, in some embodiments, to the creation of a user or device service account, in some cases, with user information or device owner or billing information. In some embodiments, the provisioning process is equivalent to assigning credentials to the device and programming a portion or all of the credentials in the device, entering a portion or all of the credentials in the various necessary network equipment databases so that the components of network can identify the device and associate 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.

Additional examples of the network-based service profile policies include network access level, traffic routing, service monitoring, service limits and actions taken after reaching service limits. Once the service profile is created and activated during the activation process, the device credentials and the associated service profile communicate through all the necessary network elements so that each element can implement its part of the network portion of service profile policies. This process of propagating the service profile settings to all 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 appropriate 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, the activation also includes the service processor software settings, configurations or facilities for each function or agent in the service processor to implement its part of the service profile, service plan, service billing or billing policies of transaction. In some embodiments, the 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 user choices. user for the service plan and other aspects of storage and management of account information, such as maintaining status information, maintaining the configuration of the central service profile, making reconciliation and billing exchanges, service usage history and / or history of account.

In some embodiments, the term credentials generally refers to the set of information parameters that the network and / or the device use (for example, require) to support the device on the network and associate it with the service profile and / or plan of appropriate service. For example, credentials may include one or more of the following: telephone number, device identification number, MEID or similar mobile device identifier, hardware security device ID, security signature or other security credentials, number serial device, device identification and / or credential information through security hardware such as a SIM, one or more IP addresses, one or more MAC addresses, any other network address identifier, information block of information embedded device (static or programmable), security key, security signature algorithms, passwords or other secure authorization information, service processor (or device client or similar agent software) identifier or settings or version, identifier type of device, browser header information (for example, http, https, WAP, other browser client) or similar identifier, browser token or similar identifier information, browser cookie information or similar identifier, embedded browser instructions, portal-client header information (for example, interface or communication agent connecting to a used network portal at least in part for provisioning or activation for the device or by the user) or similar identifier, portal-client witness information or similar identifier, portal-client cookie information or similar identifier, embedded portal-client instructions, provider service, OEM, master agent (service distributor), VSP, device service owner identifier, distributor or master agent, and / or any information that the network can use to authorize network admission, provision the device, provision the network, activate service, authorize, associate or enable the device with a sequence of provisioning, associating or enabling the device with one or more service profiles, associating or assisting the device with an activation sequence, associating or enabling the device with an environment profile or service experience, associating or enabling the device with one or more service plans or service capabilities, associate the device with a service provider or service owner, associate the device with an OEM or master agent, associate the device with a distributor or master agent, or associate the device with a group of devices , user group or user. In some

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

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 includes at least one subset that is 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 includes at least one subset that is 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 (for example, telephone number and / or access or authorization security credential) are used for more than one device. In some embodiments, 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 by permanent credentials on one or more devices. It should not be inferred from the expression permanent credentials that permanent credentials are never recycled, for example, when the user discontinues the 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 for accessing limited network services for the purpose of credential provisioning and / or activation of a service plan or profile of service. For example, before a phone number is assigned, a device can access a limited set of network server destinations where embedded information contained in the device (for example, partial credentials) is provided to the server, The server associates that information with the appropriate additional credentials (including the phone number) to assign to the device and / or associate the information with the appropriate service profile to activate the service. In this example, partial credentials can include the type of device, 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 appropriate 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 device or user credentials, user information or billing information, service profile, billing profile, network authorization status, and other aspects that define 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 established and associated with the device before any or all of the required permanent account information is available or entered for a device or Username. For example, this account can be established with a partnership with a real user, or it can be established with a simulated user or unassigned user association so that the network and billing system can recognize credentials, authenticate the device, support the device, provide the appropriate level of service activity control according to the service profile associated with the temporary service account, or collect service activity usage information for various network system accounting and billing needs before it is You have entered the user information or actual billing information in the network systems. For example, a temporary service account may make it possible or easier to use existing billing systems or other network systems to provide simplified provisioning, activation or simplified environment services. A temporary service account can also be made a permanent service account by replacing the simulated user or unassigned user information with real user information, or a temporary service account may need to be replaced by a permanent service account when the actual user information You need to enter network systems, possibly including billing or service profile databases.

In some embodiments, temporary and permanent device credentials and other information used / required to provision the device are generated with the device located at the manufacturer or in the distribution channel as discussed below. In some embodiments, the apparatus includes a server at the local site that typically shares some aspects of the provisioning information (eg, telephone number, telephone number range, MEID or MEID range, SIM number or number range SIM, IP address or IP address range, MAC address or MAC address range, other secure device credential items) with a network provisioning database. In some embodiments, the apparatus includes a server terminal, and the aforementioned portion of the credentials is generated over the network and shared with the local provisioning apparatus. In some embodiments, as will be discussed below, provisioning credentials are generated in part on the network and shared with the device while connected online to an activation server (for example, activation server 160) that is connected to the access network. Similarly, there may be activation servers connected to the device in the manufacturing or distribution channel that serve for device activation, or in the course of communication or through the network device connected to an activation server, which in turn, it is connected to the device, it can be used to achieve network and device activation programming as discussed further below.

In some embodiments, when a device is provisioned and entered into the network provisioning database, it is associated with the sequence of provisioning and / or automatic activation that is

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

It aims for the device to go through once it connects to the network or the device that will complete the process. In some embodiments, one or more device parameters (for example, service owner, device type, OEM, plan type, IP address, security credential and / or software version) are used to determine what the stages are and / or appropriate network provisioning settings to complete the provisioning and / or activation process, and this association information is stored in the network provisioning database for propagation of provisioning profiles or activation profiles to the various network equipment elements. In some embodiments, the network provisioning database (for example, on the network) is provided that associates the pre-activation provisioning information (eg, generated, as described herein, at the time of manufacturing, sometimes during distribution, by the user on a website by a vendor or other activation assistant, or by the network when a new device enters the automatic activation process). For example, pre-activation provisioning information informs the network whether or not to allow the device in an activation sequence when the device attempts to access, and in some cases, also orders the network to redirect the device to an activation sequence. specific that includes, for example, an activation server sequence (or other activation sequence generation apparatus) as described herein. In some embodiments, a central database is queried by another network equipment or the central database is included in one or more of the network elements (for example, the aAa server and / or billing system, wireless center mobile 132), or the database is copied in part or in full into various network elements (for example, the central database, the AAA server, mobile wireless center, billing system and / or gateways) .

In some embodiments, propagating network equipment provisioning information for a given device or group of devices is achieved with a network provisioning system that has access to the network provisioning database and can program the appropriate network equipment. . In some embodiments, this network equipment is referred to as "network management" or "network provisioning" equipment. In some embodiments, there are several functions that take part individually or jointly, including, for example, AAA server 121, service controller 122 (with device-based / assisted services through embodiments related to the processor). service or with network-only embodiments as described herein), the mobile wireless center 132 (for example, which includes the home location register (HLR) or other similar function referred to by other industry terms), the server or activation servers 160, other network provisioning or management equipment connected or associated with the billing database system, and / or some other equipment device. In some embodiments, the local database on the device, the database on the AAA server and / or the database elsewhere on the network are provisioned to inform the process gateway to handle the pre-device. provisioned according to, for example, credentials. For example, if the device is not recognized or authenticated in the access network as an activated device with service profile and / or associated active service plan, the device connection or communication can be directed (or routed) to an activation server generic 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 a service profile and / or associated service plan, the device can be directed (or routed) to an activation service (or other generation device). activation sequences) that use some part of the credentials or range of partial credentials or a portion of a partial or complete device profile to determine a specific desired predetermined device or specific activation sequence of device group that is implemented by a sequence of specific activation service or other activation sequence apparatus. In another example, in which the device is not recognized or authenticated as an activated device with service profile and / or associated active service plan, a portion of the device credentials or partial credentials can be used as a correspondence index in a database that determines that the specific device activation sequence and the device should and can be directed (or routed) to a specific activation server sequence or other activation sequence generation apparatus.

In some embodiments, a database on the AAA server or database elsewhere on the network is provisioned to inform the gateway what to do with a device previously provisioned according to credentials. For example, the devices can be authenticated (for activated devices) to be routed to activation servers (or other activation sequence generation apparatus) or denied access. In some embodiments, the AAA server (and / or other network elements) provide the correspondence function discussed above for the description of the previous gateway in which a correspondence database is consulted, stored locally or stored in a database. central data, to provide secondary routing information to specific or generic activation servers.

In some embodiments, the previously provisioned database is located in the billing system. In some embodiments, the billing system accesses the previously provisioned database (for example, stored in the billing system or other network element) for the purpose of establishing temporary accounts or permanent accounts and associating these accounts with pre-status -activation, free environment activated or paying customer activated.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, for zero activation, all required pre-provisioning or programming of the previous network elements, or others, are coordinated by the network provisioning system at some point after the partial device credentials have been associated or complete with the device or have been 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 described elsewhere.

In view of the various embodiments described herein, it will be appreciated that many of the automated or background provisioning, activation and environment embodiments described herein can be achieved with network based approaches, device based approaches or based approaches in combination / hybrid network / device. For example, when access control is achieved for the provisioning process on the device (for example, a device-based approach), the activation server can be located anywhere on the Internet, and the device will ensure that the activation process it is done with the activation server while blocking other traffic from taking place. As another example, some or all of the stages of environment provisioning programming are made stages to program access control, traffic control, application control, billing rules per account and / or other aspects in the service processor or controller of service as described in this document.

In some embodiments, the provisioning apparatus described herein may 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 device for provisioning or programming software. In some embodiments, the same network, possibly through an activation server 160, website or other interface to the device, the provisioning apparatus is made, in some cases, with software assistance on the device to affect programming of provisioning information from the network or 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 / tool program, a web browser based program, a WAP browser based program, and / or any other program you provide a function opposite to the network functions that perform provisioning (for example, activation server). In some embodiments, the activation server initiates a specific provisioning sequence if device software is present to assist or route to a website for manual entry if no software is present.

Figure 64 illustrates another network architecture that includes a system located in the manufacturing or distribution chain for the device that provides device provisioning or partial provisioning, and any pre-activation required for the device to be activated later in the network according to some embodiments. The 6420 device credential software and settings server 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 on the network equipment ( for example, billing system 123, service controller device control system 6225, gateways 410, 420, base station 125, credential generation and association server 6410, activation server 160, download control server 1660 service and / or other network device). For example, the link between the software server and 6420 device credential settings to the core provider network equipment may be over the Internet 120 (for example, a secure link over the Internet) as shown or over another connection such as a leased line. The 6420 device credential software and settings server obtains partial credentials or credentials from the network device that generates them, illustrated by the 6410 credential generation and association server. The 6410 credential generation and association server does not need to be connected directly to the main central provider network 110 as shown, but it can be located elsewhere (for example, in another location connected by a secure Internet link). The 6410 credential generation and association server assigns credentials, or partial credentials, for use by the software server and 6420 device credential settings. When these credentials are assigned to a device, they are programmed, loaded, or otherwise associated with the device by the 6430 device credential provisioning apparatus, which is connected to the device wirelessly or via a wired line connection.

In some embodiments, a 6440 device software loading and programming device provides functions of loading or software device settings that form a portion or all of the provisioning or configuration of pre-provisioning device, or form a portion or all of the configuration of device activation profile, or form the device service owner, master agent or VSP device assignment or signature, and in some embodiments, using an activation tracking service system (ATS). As discussed herein, the ATS monitors connections and traffic network aspects that provide information on which networks the device 100 is accessing, in some embodiments, in order to ensure that an OEM, master agent, service owner Device or VSP is being compensated for devices that are activated in a service provider network. In some embodiments, the ATS agent connects to an opposite server party that registers 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, it determines in which networks the device is activated. In some embodiments, the ATS is installed in the device in such a way that it makes it difficult to manipulate or eliminate it, so that the entity that intends

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Obtain credit for the activation of the device service. Obtain credit (for example, the ATS agent can be loaded in secure memory, it can be installed with software that makes it difficult to uninstall it, it can be installed in the modem possibly in secure memory, it can be installed in BIOS, it can be installed deep in the OS core, it can be installed with one or more additional device agents that monitor the ATS agent and alert a network function or reinstall it if it has been tampered with.) The SIM 6450 inventory is provided to illustrate that, in some embodiments, hardware elements (for example, a SIM security module as shown) or hardware configurations are also installed or handled in the device 100 and these operations and the Registration of the resulting associations form a portion of the provisioning or pre-provisioning process.

In some embodiments, at the time when the credentials or partial credentials are loaded, programmed, set, installed, read from the device or recorded in another way, in some cases, they are all associated together in a database that allows the subsequent identification of the device and its appropriate provisioning and / or activation process through such associations. For example, this may involve reading device parameters such as MEID, MAC address, device type or other information that is associated with the information that is being loaded or configured on the device. As discussed in this document, this credential configuration and association information is stored on the responsible network equipment that uses it to configure the network to activate the device in one of the various embodiments disclosed herein.

Some embodiments include linking some or all stages of activation provisioning and information adjustments together in a database that defines a higher level activation profile for a group of users (/ devices), and a server is used to perform programming. of device and equipment for the devices in the group, which includes, for example, associating the following device information in the group definition: credentials, service owner or master agent, provisioning information and / or activation profile. Some embodiments further provide that this device group information be distributed to the various network equipment components required to activate the devices as discussed elsewhere. In some embodiments, this programming association and device group is achieved using the VSP 4910 workstation server. For example, a device can be manufactured and distributed in such a way that it provides flexible device allocation 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 may be multiple device activation servers 160 each with a different device activation experience and potentially controlled by a different service owner VSP. , service provider, OEM or master agent. As discussed herein, there are several ways for a device 100 to be routed to the appropriate activation server 160 so that the device provisioning and activation process can be completed. In some embodiments, all devices that are not activated are redirected (or routed) to an activation server that reads one or more parameters in the device credentials. The device credential information can be determined through the device identification information associated with the same access network connection (e.g., MEID, IP address, telephone number, security credentials or other credentials identified for a device which gets access to the network), or with the help of the device in a pre-arranged query-response sequence. The device can then be redirected (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 achieved with a single redirection from a service gateway 420 or 410, or another network element activated for the router. In some embodiments, the same gateway or network element decodes the device credential information as described herein and performs the correct redirection (or routing) to the appropriate activation server 160 for that device. In some embodiments, the activation server 160 may be incorporated directly into the gateway 420 or 410, the base station 125 or another network component. In some embodiments, activation server 160 may be incorporated into service controller 122 or service controller device control system 6225.

In some embodiments, devices other than the activation server are used to facilitate the provisioning of credentials or partial credentials, or activation, during device manufacturing or distribution, and, for example, these devices may augment, supplement, complement or replace the function. of the activation server. Such devices include, for example, device programming equipment (for example, device credential provisioning device 6430, device loading device and programming software for device 6440 or SIM 6450 inventory), which is networked at a central vendor, MVNO or VSP database (for example, software server and 6420 device credential settings) to gain access to provisioning information or activation information that is programmed into a device or group of devices, or to put credential information or partial device credential in a network database for later recognition, or to receive or communicate security information such as certificates for SIM devices or modules that will be used later to complete provisioning or complete the activation or access to a network. For example, these devices, or any other device that includes the activation server, may be networked in a service provider network or device database, an MVNO network or database

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

device 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 may be recognized by an activation server or similar network function at a later point. over 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 to the service provider or service provider partner service, device type, user group, VSP, MVNO, master agent or other entity. In some embodiments, this programming is provided in such a way that it is difficult to change without having the appropriate authorization so that the device is properly associated with the "service owner" or appropriate master agent (eg, for the purpose of incentive payments of activation). For example, as discussed herein, various approaches can be applied to the device credential or other settings or provisioning of software so that the settings or software are secure or protected, or so that if the software is removed, replaced or Modify information is generated or replaced or restored. In some embodiments, vSp control of provisioning, partial provisioning or activation of the devices is provided during manufacturing or at different points in the distribution channel. As discussed in this document, some of these embodiments allow the central provider to offer service partners (by

example, VSP, MVNO, master agents and / or OEM) similar types of control for experience design

service activation or device service assignment control (for example, sometimes referred to as a service provider device lock so that other service providers cannot provide primary access to the device) during the manufacturing or distribution process that is possible with devices manufactured and distributed by the central service provider.

In some embodiments, the device is provided before the user obtains the device with permanent credentials, temporary credentials or partial credentials. In this case, the necessary credential programming of the device takes place during manufacturing, at some point in the distribution of the

device, such as in a distribution warehouse or warehouse, or at the point of sale or shipping point. In

In some embodiments, the provisioning of network information is used as discussed above, 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 specialized apparatus that is connected to the device wired or wirelessly. For example, the specialized apparatus may be local to the location where the device is being provisioned or it may be partially or completely networked in a database or provisioning solution located elsewhere and operated by the central provider, a VSP, OEM or other entity. For example, the apparatus for programming the network portions of the provisioning information may also be networked and the operators that establish the network programming required for a device or group of devices may be in the vicinity of the servers hosting the tools provisioning and management or may be networked on servers. In some embodiments, the provisioning system operators have complete or partial control of any device provisioning equipment associated with the entity for which they work (for example, OEM, VSP or master agent) but only have remote access through terminal techniques secure, secure website or others to network with a central provider or VSP server farm where they partially control or control the network portion of provisioning capabilities for that subset of the devices that are assigned to the entity for that work (for example OEM, VSP or master agent).

In some embodiments, provisioning is achieved during the communication in the mobile access network for mobile devices, or through the wired access network or WLAN connection for wired access networks, 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 the provisioning. In cases where the device is provisioned at the point of sale or after the point of sale, the device provisioning can be activated by a user-initiated sequence, or it can be initiated by an automated background sequence at any time after of the device being turned on. In such cases, in some embodiments, partial credentials are used that include information such as device type, OEM or service provider to help determine how to complete the provisioning, and the information may also include secure information, certificate or signature programmed in the partial credentials required for the network to provision the remaining credential information on the device and possibly on the network. In some embodiments, any network information used / required to provision the device or service is generated at the time when partial credentials are determined rather than previously.

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 stages of provisioning and activation of service for the device can take place during manufacturing, at some point in the distribution of the device, such as in a distribution warehouse or in a warehouse, or in the point of sale or shipping point. In some embodiments, the steps to activate service include one or more of the following: provision the device (for example, with permanent, temporary or partial credentials), provision the databases and network equipment necessary to prepare them to recognize the device and

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

associate it with the service profile and / or service plan, create or select the service account (for example, permanent or temporary service account), select or create the service profile and / or service plan, schedule any item in the device required to activate the service (for example, account ID, device aspects of the service profile and / or service plan), and program the necessary databases and network equipment with the required device credential associations and Policy settings for service profile and / or service plan. In some embodiments, the device-oriented programming portions of the service activation stages take place at the same time, before or after the network-oriented programming portions of the service activation stages.

In some embodiments, the device activation information is programmed with specialized apparatus that is connected to the device via a wireless or wired line connection. For example, the specialized apparatus may be local to the location where the device is being provisioned, or the specialized apparatus may be partially or completely networked in a database or service activation solution located elsewhere and operated by the Central provider, a VSP, OEM or other entity. For example, the apparatus for programming the network portions of the activation information may also be networked and the operators that establish the network programming required for a device or group of devices may be in the vicinity of the servers housing the tools activation and service management or may be networked on servers. In some embodiments, the activation server tool operators have complete or partial control of any device activation device associated with the entity for which they work (for example, OEM, VSP or master agent) but only have partial and remote access through the secure terminal, secure website or other techniques to network with the network portion of the activation tools that are controlled by the central provider or VSP. Server tool operators may be restricted in some embodiments to provide network activation information or settings only for those devices or groups of devices that are assigned to the entity they work for (for example, OEM, VSP or master agent). For example, the device control group restriction can be achieved with a secure database that has secure sub-partitions for one or more entities so that they cannot impact the control of the network activation settings with one another. , but can control their own devices. In this way, a centralized set of activation tool resources controlled by a central provider, VSP or other entity can be divided into partitions so that different entities can have partial or total control of the activation service definition for devices or groups of devices without impacting or putting others at risk who share the resources of network and activation tools.

In some embodiments, activation is achieved with an aerial interface to a mobile device, or through the wired access network or WLAN connection for wired access networks, before the user receives the device or after the user receives the device. In some cases, the device may be connected to general purpose equipment such as a computer to perform the programming required to complete the activation. In cases where the device is activated at the point of sale or after the point of sale, the final device activation process can be activated by a user-initiated sequence, or it can be initiated by an automated background sequence in any time after the device is turned on. In such cases, some embodiments request that a temporary service account be used to provide the device on the network before the user has entered the information necessary to create a permanent service account. In some embodiments, a temporary or permanent service account may be applied to the device at the time the device reaches the network, and the type of account, service profile and / or service plan may be influenced (e.g., determined or partially 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, device credentials may also include secure information, certificate or signature that may be required by the network to perform the activation stages for temporary or permanent service statement. In some embodiments, in which the device is activated in this manner before the user information is available, or after the user has selected a payment for service plan, the service profile and service plan are set to environment services as described in this document.

In some embodiments, the device is activated during the manufacturing or distribution process, and then the status of the activated device is suspended. Once the temporary or permanent service account is established, with an appropriate service profile and / or service plan and temporary or permanent credentials, in some billing networks and systems the service can sometimes be resumed more easily once suspended in comparison with the provisioning and activation of the device from scratch. The device resumes (or reactivates) then later when some event activates the process to resume, such as when it is sent to the end user or when the end user tries to use it. This process avoids the need for the network to manage credentials and accounts for devices that have been activated but are not yet on the network.

In some embodiments, provisioning is achieved at least in part with temporary credentials in a manner that is automated and convenient for the user or device owner. In some embodiments, at least some subsets of the temporary credential elements are replaced at a later point in time by permanent credential elements such that it is also automated and convenient for the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

user or device owner. In some embodiments, the temporary credential set is preprogrammed on the device along with a temporary or permanent service account that includes the service profile during the manufacturing or distribution process so that the device is activated with temporary credentials when it is sent. In some embodiments, the aforementioned pre-programming is performed for the network by a secure set of server access equipment that is networked in the network databases used to define the service profile and / or the service plan . In some embodiments, a subset of 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 is used after some time. period of time, or if the subset of credentials 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 telephone number, which may be limited in shipping. 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 items is different for the sets, so that if a set of credentials has items that are already being used for access the network, then one or more backup sets can be used after accessing the network.

In some embodiments, temporary credentials are used for network registration to perform an activation process in the course of communication or over the network in which an activation server reads at least a portion of the device credentials to determine Some aspect of how the device service profile is. In some embodiments, the activation process in the course of the aforementioned communication is achieved in the background without user intervention. In some embodiments, the activation process in the course of the communication is initiated when the user first tries to use the device or when the user first tries to access the network or upon user request or approval. In some embodiments, the activation process in the course of communication is initiated using a temporary service account so that the device and / or network gain access to the network. In some embodiments, the activation process in the course of communication begins after the user has entered the information required to create a permanent user account on the device or on the network. In some embodiments, the user is required to enter the aforementioned user information before using the device or using any 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 information necessary to create a permanent account on the device or network. In some embodiments, the activation process in the course of the communication 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 activation during the aforementioned communication to be a pay-per-service profile with a free trial period. In some embodiments, the service profile assigned to the device and / or network during activation in the course of the aforementioned communication includes options for pre-payment, post-payment, session-based payment or payment for use for service. As will be apparent to one skilled in the art, various embodiments are disclosed herein that are particularly well suited for control or prepaid services. In some embodiments, the service profile that is assigned to the device and / or network during activation during the aforementioned communication is an environment service profile that provides service access before all 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 environment service profile that provides a user service improvement selection option interface. In some embodiments, the service profile that is assigned to the device and / or network during the aforementioned activation is an environment service profile that provides 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 environment service profile that provides invoice functionality per account for the network. In some embodiments, the service profile assigned to the device and / or network during the aforementioned activation is an environment service profile that provides some amount of network interconnection service or free information to attract the user to use the others. environment services. In some embodiments, the aforementioned environment service is implemented at least partially with device-based service activity control or control assistance. In some embodiments, the aforementioned environment service is implemented at least partially by the gateways, routers or switches in the network that are programmed according to the environment access profile for the device to implement the environment policies for access control network, routing control, traffic control or service monitoring and generation of information for invoice per account.

In some embodiments, activation is achieved 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 by the permanent service account subset so that it is also automated and convenient for the user or device owner. In some embodiments, the temporary service account settings (for

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

for example, which include service profile settings and / or service plan settings) are pre-programmed into the device along with a set of temporary or permanent credentials during the manufacturing or distribution process so that the device is activated with Temporary credentials when sent. In some embodiments, the aforementioned pre-programming for the network is performed by a secure set of server access equipment that is networked in 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 resumes before or according to the point in time the user starts using it. In some embodiments, some subset of the temporary service account is received once it is replaced, if the temporary service account is not used after some period of time, if the temporary service account is not improved to a service account. permanent 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 in 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 an account is already being used to access The network then one or more reserve accounts can be used to gain access to the network. In some embodiments, the temporary service account is associated with a set of temporary credentials. In some embodiments, the temporary service account is associated with a set of permanent credentials.

In some embodiments, devices not activated by the network routing equipment are detected (eg, gateways or service routers in hierarchical networks or base stations with gateways embedded in flat networks) and the device routing is programmed to redirect non-activated devices to an activation server network destination. For example, the activation server may first inspect the information associated with the device to determine if the device belongs to the list of devices, device types or groups of devices to which the network is programmed to provide access. For example, the information used to determine this may include device type, service provider, telephone number, device ID, ID or SIM configuration, secure information used to qualify the device, IP address, MAC address, user , user group, VSP, OEM, device distributor, service distributor (master agent), presence or configuration of service processor, presence or configuration of other software or hardware. There may also be some activation definition information embedded in the credentials, or associated with some portion of the credentials, or additionally programmed into the device that informs the activation server as the service profile and / or service plan and / or account of service that should be set for the device. If the activation information (service profile, service plan and / or service account information) is found through association with device credentials (for example, device ID, phone number, IP address , MAC address, SIM or other security credentials) instead of reading directly from information embedded in the device or device credentials, then the relevant aspects of the credentials can be used as a cross-reference to search for service plan information and / or service profile stored in a network interconnected network or on the activation server. The activation information may include information to define a wide variety of service plans and service profiles that when properly implemented in the network functions, and perhaps the device if necessary, can provide a wide variety of activity activity policies. service, service billing policies, transaction billing policies and types of service account that can be associated with the device in the course of communication or over the network.

In some embodiments, once the activation server has determined the activation information from the device or from a search based on some aspect of the device credentials, then the activation server initiates the necessary network settings and base entries of billing data to be programmed by sending the service instructions to the network provisioning and activation device and the service plan instructions to the billing system. In some embodiments, the activation server may then send any of the necessary service profile and / or service plan settings required for the device to a provisioning and activation support software function in the device, such as various embodiments. of the service processor, so that provisioning and device activation can be completed. The establishment can 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 establish a permanent service account, and, in these cases, a temporary service account may be established. . In some cases, the activation process may be completed in the background before the user has completed an attempt to access the network and the service profile may be established to provide environment services to a temporary service account. In some embodiments, the user is required to enter the information required to establish a permanent service account before obtaining full use of the device, on the device, on a computer or in the warehouse, so that at the time when the user starts using the device the above activation embodiments can provide activation environment services 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 user information

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

is available to establish a permanent account, so if the billing system rules and interfaces allow this, the user information can be changed from the simulated information to the actual user information while maintaining the same account identifiers in the billing system . If the billing system now does not allow this, then user information can be used to establish a new account, device credentials can be re-associated with the new account, in some cases, after modifying one or more of the parameters of Device credential, and network functions can be reprogrammed as required, and, in some cases, the device can be reprogrammed as required to adapt the new permanent account.

In some embodiments, the code in the device extracts a temporary or permanent set of credentials. When credentials are extracted, the network associates the device with an environment service profile according to one or more of the following: embedded device information that identifies the type of device, service owner (for example, VSP), group of users, or user, or device ID have cross-reference to a database that is filled in some time from manufacturing time to subsequent sale where the database provides information that identifies the type of device, service owner ( for example, VSP), user group or user. The device is then redirected accordingly (for example, for device-based this is a matter of policy adjustment or loading the software for the service processor, for the network-based approach this is a matter of filling the tables of routing and service profile). For example, credentials may be recycled after a period of time, and / or some portion of the credentials may be redundant with other devices. For example, this is essentially a dynamic service for assigning (temporarily) device credentials, and the duration of the temporary credential validity for that device ID can be limited in time to provide the user time to activate a real account or a free trial , limited session or a longer duration of time that may be refreshed each time the device logs on. For example, the device may 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 environment 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 search for the activation server system described above as soon as it is turned on, or as soon as some other event occurs as the user is using the device or that the user tries to gain access When the pre-scheduled event is triggered, the device connects to the network and the gateways or routers redirect the device to an activation server, as discussed above. As also described herein, the activation server derives information from the device that informs the server with which service the device should be activated, or the server derives that information from a database map with a portion of the credentials of device as the cross-reference parameter. Once the activation server has determined the activation information from the device or from a correspondence based on some aspect of the device credentials, then the activation server causes all necessary network settings and database entries. billing to be configured / programmed by sending the service profile instructions to the network provisioning and activation device and the service plan instructions to the billing system. In some embodiments, the activation server may then also send any necessary service profile and / or service plan settings required for the device to a provisioning and activation support software function in the device, such as various embodiments of the device. service processor, so that 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 established can be permanent or temporary.

In some embodiments, background activation is performed using the above-mentioned activation / 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 or some other event that occurs as the user uses the device or the user tries to gain access. When the preprogrammed event is triggered, the device attempts to connect to the network and the gateways or routers redirect the device to an activation server as described in this document. Also as described herein, the activation server derives information from the device that informs the server that the device is ready to resume service, or the server derives that the information from a database search with a portion of Device credentials as the cross-reference parameter. Once the server is aware of this information, it sends a message to resume the service to the billing system, or another network function that controls the suspend / resume function, and the service resumes.

In some embodiments, background activation is performed as described below. The service processor and 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 environment service. As described herein, this programming can be achieved with apparatus

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

specialized in the manufacturer or distribution warehouse. Additionally, the party responsible for defining the service (for example, typically the central provider, OEM, VSP, distributor or master agent) may be networked with the service processor programming apparatus to control the service processor and / or programming of credential for all or a subset or group of locally available devices or device types. The device activated for the service processor is programmed to search for the activation server system described above as soon as it is turned on, or as soon as some other event occurs as the user uses the device or the user attempts to gain access. In some embodiments, the activation server is the previously analyzed access control server or the access control server may act in conjunction with another server that performs the activation function. When the pre-scheduled event is triggered, the device connects to the network and the gateways or routers redirect the device to the activation server. As also described herein, the activation server can communicate with the service processor to verify the security credentials of the service processor, 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 achieved. before completing the activation process. Once the configuration and settings of the service processor are confirmed, the activation server causes the necessary network settings and billing database entries to be programmed by sending the instructions from the service profile to the provisioning and activation device. network and billing system service plan instructions. Since the service processor can perform some or much of the service activity control or control assistance, the service control options in general are greater than without the service processor, and there may be less configuration to perform for other computer equipment. network interconnection to complete the provisioning and activation process. The provisioning can be with permanent credentials or temporary credentials, and the service account that is established can be permanent or temporary.

In some embodiments, pre-programming and pre-activation of devices with temporary credentials and a temporary service account is used to send devices that are pre-activated. Since credentials are temporary and can be recycled when permanent credentials are assigned, concerns about using too many pre-assigned credentials are reduced. In embodiments in which a portion of credential elements can be used for multiple devices, this concern is further reduced. If there is a concern about too many activated devices that are assigned that are not really active and generate service revenue, then the suspend / resume process discussed in this document can be used. In some embodiments, temporary credentials and / or temporary account may be replaced by permanent credentials and / or account assignments at any time as follows. When a pre-scheduled event is triggered on the device, then the device starts a program that searches for the above-mentioned activation server or another server that has the ability to satisfy the device's request to exchange 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 the account information.

In some embodiments, the aforementioned environment service is partially implemented with a combination of techniques for pre-provisioning during manufacturing or distribution and at least partially implementing the service activity control (eg, access control, routing policy, traffic control, usage limits and / or policy for additional use of usage limit) required to implement environment using the service policy provisioning capabilities on data path gateways, routers or switches in the network. The gateways, router or switches are pre-programmed as discussed in this document in accordance with the environment access profile for the device to implement the environment policies for network access control, routing control, traffic control or service monitoring and generate information for invoice per account. In some embodiments, the provisioning credential elements are not all pre-programmed before the device is sent, but a subset of the credential elements is programmed using the activation server technique discussed herein. This automated provisioning in the course of communication is combined with the activation server that reads the device credentials to derive the service activity control settings for the gateways, routers or switches that will result in the service activity controls of desired environment.

In some embodiments, the aforementioned environment service is implemented with a combination of techniques for pre-activation during manufacturing or distribution and at least partially implementing the service activity control (eg, access control, routing policy, traffic control, usage limits and / or policy for additional use of usage limit) required to implement environment using the service policy control capabilities on 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 in this document in accordance with the environment access profile for the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

device to implement the environment policies for network access control, routing control, traffic control or service monitoring and generate information by invoice per account. In some embodiments, the device activation profile and / or service account is not pre-programmed on the network and / or the device before the device is sent but the activation profile and / or service account are programmed. using the activation server technique discussed in this document. This automated provisioning in the course of communication is combined with the activation server that reads the device credentials to derive the control service profile activity settings for the gateways, routers or switches that results in the activity controls of desired environment services.

In some embodiment, a VSP capability is activated by providing a secure network connection to the service policy setting tools that define the device pre-provisioning settings, the device pre-activation service profile settings, the network equipment service activity control policy settings (for example, access control, routing policy, traffic control, usage limits and / or policy for additional use of usage limit), and the database of network billing system. By providing server tools that enable all of 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 is networked with the equipment that schedules the settings, and by providing a secure partitioning of devices that can be controlled by a given secure workstation or secure website interface, a central provider can provide VSP services to multiple entities that all have different combinations of device and service plan for those who want different tastes of environment services. These techniques can also be extended beyond environment to any combination of device / service profile / service plan that the VSP wishes to create. In some embodiments, the network interconnection equipment is implemented to ensure device service group domains in which service policies for a group of devices can be controlled. In some embodiments, the pre-provisioning and pre-activation techniques are replaced with the activation server techniques in the course of the communication discussed herein, and a secure device group partition capability is provided on the activation server. also so that the group partition control capabilities of activation server devices can be added to the group partition control capabilities of secure gateways, routers and / or network switches, programming tools device and billing system to form a VSP partition solution for activation during the communication of various device / service plan combinations. In some embodiments, the device groups are relatively small so that beta tests of arbitrarily large or small size can be designed and implemented by defining a service control group as described above, and then fine-tuning and perfecting the test settings. beta that the device group can expand to publish the provisioning and automated activation service settings to a larger group of users or devices for production services.

In some embodiments, device-based service activity control assistance (for example, based on the various service processor embodiments described herein) is combined with the simplified provisioning techniques described herein so that Service processor activated devices can be sent with pre-provisioned (temporary or permanent) credentials or can obtain credentials in an automated manner that is convenient and effective for the user or device owner. In some embodiments, the service processor embodiments in combination with the credentialing and provisioning apparatus of the manufacturing and supply chain described elsewhere provide various approaches for provisioning pre-provisioned service processor activated devices. In some embodiments, the service processor embodiments in combination with the activation server variants discussed above provide various approaches to simplified network after-sales provisioning for service processor activated devices. For example, these embodiments can also be used for environment services since, as discussed herein, the service processor has the capacity 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 provisioning and / or activation of full credential by performing a process for a subsequent search / validation of complete device credentials. . For example, the search / validation of complete device credentials can be performed by a gateway, router or similar network device that redirects to a provisioning server and / or activation server or other network components that: (1) recognize 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) do not recognize partial credentials, and direct the device's communication to a less specific provisioning / activation server that is not necessarily associated with a reference to partial credentials.

In some embodiments, if partial device credentials (for example, temporary or permanent credentials) are being used to provision, then partial credentials are read (for example, and / or other credentials can be searched based on partial credentials as has been previously described). He

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

device is authorized if appropriate credentials and / or secure certificate are present. The device credential provisioning is then completed (for example, using commands or activation server settings to a device-based software and / or hardware item), and the credentials are also communicated, in some cases, to the various network equipment elements.

In some embodiments, if partial device credentials are being used for activation, then partial or full device credential provisioning is performed, as described above. A service account (for example, a temporary or permanent service account) is created or searched based on partial device credentials (for example, a user account associated with the device through partial or full embedded credentials or a process search, or based on a temporary account created / assigned dynamically associated with the device through partial or full embedded credentials). An initial service profile and, in some cases, an initial service plan (for example, service control policy settings that include a billing profile) is determined from embedded information and / or using a search process ( for example, based on the type of device and / or partial or complete device credentials). The device is then programmed to enable access with the profile and service plan, and, in some cases, the various network components / elements are programmed to enable the profile and service plan, and, in some cases, are performed or confirm appropriate entries in the billing system, and device credentials, therefore, are activated for service.

In some embodiments, the provisioning and / or activation processes described above are performed with the provisioning server or servers and / or the background activation server or servers with reduced, minimal or no required user input, for example, after that the device is sold to the user and the user turns on the device so that at the time the user tries 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 (for example, based on service processor embodiments) is combined with simplified activation techniques described herein so that devices activated for service processor can be sent. with pre-activated accounts (temporarily or permanently), or they can obtain an activated account statement in an automated manner that is convenient and effective 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 to pre-activated service processor activated devices. In some embodiments, the service processor embodiments in combination with the activation server variants discussed above provide various approaches for simplified network after-sales account activation for service processor activated devices. These embodiments can also be used for environment services since, as discussed herein, the service processor has the capacity to implement service profile policies for deep control of ambient service activity control.

As discussed herein, in some embodiments for activation, the AAA network (or other network function) recognizes one or more aspects of pre-activated device credentials and routes the communication of the pre-activated device to a server of activation that is appropriate for that device (the routing information is derived through a search of the credential aspect or obtaining the required information directly from the same credential), or the AAA (or other network function) does not recognize the credentials and routes device communication to an activation server for unrecognized device credentials. In any case, in some embodiments, one or more of the credential aspects may then be used to make a secondary determination of what provisioning and / or activation sequence to perform in association with the device, or to which activation server sequence should be addressed. the device. For example, one or more aspects of device credential can be read and used as a cross-reference to determine a routing for device communication (or the information required to route may be in the same device credential information) so that the device can be routed to the appropriate activation server sequence.

In some embodiments, an activation server sequence can be determined at least in part using a browser server or a portal (eg, http server, https server, WAP server or other conventional or custom protocol server for a browser , embedded or automatic browser or a portal client on the device). In some embodiments, the browser server is an http or https server. The pre-activated device communication can be routed to the https server in a manner similar to that described above, and the server can read the information embedded in the https communication to determine the device credential information required to initiate the completion sequences. of correct provisioning and / or activation. For example, the header information of https, witnesses, cookies or other secure information communicated through https from a secure embedded client on the device (or user) can provide the activation server with the information required to cross-reference to an appropriate provisioning and / or activation sequence, or the embedded https information or the embedded client (or user) information may order the activation server on which the device services and / or any information and services should be provisioned and / or activated. of device or user required (for

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

In some embodiments, the service processor may be combined with the pre-provisioning and pre-activation techniques described above to create an environment service solution that will work in roaming networks in which the central provider or VSP has no control or minimum control over network elements. For example, the device includes a preprogrammed service processor for monitoring ambient service activity as discussed herein, and 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. On the condition that the service provider has a roaming agreement with other service providers, or on the condition that the device can gain access to the roaming network, when the device is roaming it can perform environment connectivity with functionality of invoice per account and all other environment features. Additionally, as also discussed herein, environmental service activity control policies may be different for different roaming networks to adapt variable network costs and performance. Also, for example, it would be permissible to register for initial services or additional improvement services with the central provider while roaming on the roaming partner's network. One skilled in the art will appreciate that this also allows the creation of a VSP or MVNO in order to create a coordination center for central provider service activations according to geography or user choice. Using a global multi-modem modem module, and maintaining service agreements with a multitude of operators, the MVNO or VSP can provide consistent environment services across multiple operators and multiple geographies while still maintaining a good degree of cost control. Using billing capabilities per account, it is also possible to have an activation agreement where a roaming service provider agrees to reimburse the cost of roaming environment. From the environment service platform, the VSP or MVNO can then provide service purchase options to the user based on the operator networks available for the device, or the VSP or MVNO can intermediate with the user any of the operators activating the device in the main central provider service of the operators.

Accordingly, these embodiments provide flexible capabilities to activate a device or group of devices with a wide range of service profiles and service plans simply by programming the device with the appropriate credentials at some time during manufacturing or distribution, or simply programming a base. of data associated with the network so that a portion of the device credentials can be used to search for the desired service profile and service plan. For example, various activation embodiments described herein are highly convenient for the end user and do not need to involve, in many cases, any human intervention.

The service processor 115, service controller 122, policy implementation and / or profile implementation and various embodiments disclosed herein are applications 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 account activated, 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 cost-optimized access services and prevents the machine-to-machine device or access modem from being misappropriated and used for any other service access than the intended one. For example, by programming the machine-to-machine communications device at the time of manufacture or during distribution with credentials or partial credentials that provide automated provisioning and activation as described herein, the device can be provisioned and automatically activated on the network. of service with a service account when deployed, thus eliminating the need for costly or time-consuming human intervention. The various embodiments that make it easier to design, manufacture, test and deploy devices can also be applied to machine-to-machine devices. These embodiments include the service processor 115 developer kit and automated provisioning and activation management tools among others. Also, service analysis and test tools and virtual service provider embodiments can also be applied to machine-to-machine applications.

Verifiable device-assisted services for intermediate network interconnection devices

It should be appreciated that the various embodiments of service monitoring, notification, control and billing disclosed herein can also be applied to intermediate network interconnect device applications.

In some embodiments, an intermediate network interconnection device is a communications device in which the service processor 115 is configured at least in part to allow the intermediate network interconnection device to act as an intermediary service or intermediate connection between the network and one or more endpoint devices (for example, communications devices). In addition, a service controller 122 or other suitable network function may be used to assist with the monitoring of verifiable service usage,

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

control and verification as disclosed in numerous embodiments described herein. In some embodiments, an intermediate network interconnection device does this by implementing the service policies required to assist in service usage control of the intermediate network interconnection device and connecting the network to provide services to one or more endpoint devices that they are connected to the intermediate network interconnection device. In some embodiments, the intermediate network interconnection device also monitors the service usage activities of the intermediate network interconnection device and / or the endpoint devices connected to the intermediate network interconnection device. In some embodiments, the service use of the intermediate network interconnect device and / or endpoint device is verified to ensure that the service use is within the expected ranges for the policies being implemented. In some embodiments, the intermediate network interconnect device connects to the network using a modem technology and connects to the endpoint devices using one or more additional technologies. In some embodiments, an intermediate network interconnection device connects the endpoint devices to the network by passing, bridging, forwarding, routing, shaping traffic or otherwise allowing the endpoint devices to communicate with the network. Exemplary intermediate network interconnection device embodiments include a WWAN Wi-Fi router or router device (eg, 2G, 3G, 4G or other wireless wide area network interconnect access technology), a gateway device Wi-Fi to DSL cable or fiber, a femto cell device from WWAN to DSL or Cable, a femto cell device with WWAN backlink and Wi-Fi to DSL, Cable or fiber, a WWAN router device to WWAN, a WWAN bridge, router or gateway device to WLAN, WPAN or LAN, or a WWAN backup connection device for a business router.

An intermediate network interconnection device may also be provided in some embodiments that includes a bridge, forwarding, or routing function between two modems in an activated communications device that connects to the network. For example, an intermediate network interconnect device configuration may be a cell phone, smartphone, 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 endpoint devices. For example, the mobile device WWAN modem can connect to the network, a service processor 115 can be included in the device processor to help monitor, control and bill services between the WWAN network and endpoint devices connected to a Wi-Fi modem. In addition, a service controller 122 or other suitable network functions may be employed to assist with the monitoring of verifiable service use, control and verification as disclosed in numerous embodiments disclosed throughout this document. In some embodiments, the Wi-Fi modem can be configured in access point mode or ad hoc mode to communicate with other endpoint devices in the area covered by the mobile device WLAN modem. Thus, a service processor 115 and a service controller 122 or other suitable network functions can be used to enable the monitoring of verifiable service use, control and verification as disclosed in numerous embodiments described herein.

Another exemplary embodiment is a portable or sub-portable computer with a WWAN modem and a Wi-Fi, Ethernet, Firewire, Bluetooth, near-field or Zigbee modem in which the laptop's processor has a service processor 115 that is runs on the laptop processor and service processor 115 is used to help monitor, control and bill services communicated between the WWAN network and endpoint devices connected to the WLAN, LAN or WPAN of the laptop or sub-laptop. Another example embodiment is a Wi-Fi hotspot with a service processor capacity 115. Another example embodiment is a WWAN backup modem in an access network router where the backup modem connection to the network WWAN is used when the main wired network connection is dropped, and a router processor or a WWAN backup modem processor runs a service processor 115 to help monitor, control and bill services between the WWAN network and the router of access (for example, 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 daily access). Thus, a service processor 115 and a service controller 122 or other suitable network functions can be used to enable the monitoring of verifiable service use, control and verification as disclosed in numerous embodiments described herein.

Another example embodiment is a bi-directional domestic gateway configured to perform various functions such as reading of household power consumption and / or components in the home, providing WLAN, WPAN or LAN connectivity for such components or to the fixed power meters / controllers. to such components, providing a WWAN or WAN connection as a network that reads, registers, monitors and / or controls the power consumption of the home and / or component, and possibly to provide other wide area network services for other devices in the home such as computers or electronic entertainment devices in a manner similar to WWAN, DSL, cable and fiber gateway realizations. 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 can be made with one or more of Ethernet, USB, Firewire , cable data, power line data or any other suitable wired modem technology. WWAN connections can be made with one or more of 2G (for example CDMA lxRT, GPRS), 3G (for example WCDMA UMTS / HSPA / non-MIMO HSPA +, CDMA EVDOrA / B, 802.16d / e WiMax), 4G (for

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

example LTE, MIMO HSPA +, MIMO 802.16m WiMax) or any other suitable modem technology and wired WAN connections can be made with one or more of DSL, Cable, fiber or any other wired modem technology. A service processor 115 and a service controller 122 or other suitable network functions can be used to enable the monitoring of verifiable service use, control and verification as disclosed in numerous embodiments disclosed throughout this document.

In some embodiments, an intermediate network interconnect device can be used to connect an endpoint device to a network and help implement service policies, or an intermediate network interconnect device can connect multiple endpoint devices to one or more networks and help implement service policies. In some embodiments, an intermediate network interconnection device may be associated with a service profile, a service plan or a service account, or an intermediate network interconnection device may be associated with multiple service profiles, multiple service plans or Multiple service accounts. In some embodiments, the endpoint devices connected to an intermediate network interconnect device may have service usage policies jointly implemented for all endpoint devices, or the service policies may be implemented differently for different devices. final point.

In some embodiments, an intermediate network interconnection device may have a network connection associated with a single account and manage the QOS between endpoint devices under umbrella service profile or profile collection. In some embodiments, an intermediate network interconnect device can treat all endpoint devices connected equally from a service sharing or QOS perspective so that, for example, service use is based on demand and / or contention. of endpoint device. In some embodiments, an intermediate network interconnection device differentiates service QOS between different endpoint devices based on service demand for endpoint device or service usage patterns, EDP device type or group of devices, user or endpoint device user group, service account status or endpoint device service plan status, or type of endpoint device application and / or type of traffic or type of service.

As discussed herein, the function of the service processor 115 that assists in the implementation of intermediate network interconnection device may be included in the intermediate network interconnection device, may be included in part in the intermediate network interconnection device and one or more endpoint devices, or it may be implemented primarily or completely on one or more endpoint devices.

In some embodiments, an intermediate network interconnection device may be constructed in which the endpoint devices connect to the intermediate network interconnection device and obtain access services to a WWAN network through an activated intermediate network interconnection device for WWAN / Wi-Fi that is supplied with services associated with a single account and service profile. The intermediate network interconnect device service processor 115 can help monitor, control and bill for WWAN service use for all endpoint devices in the area covered by the Wi-Fi link of the network interconnect device intermediate. In some embodiments, endpoint devices are serviced on a first-come-first-serve basis without differentiation. In some embodiments, the endpoint devices receive equitable distribution of services so that if one endpoint device is using significantly more service than the other endpoint devices, or is demanding more service than the intermediate network interconnect device, Service profile settings provide a single endpoint device (for example, "bandwidth hoarding"), then the high demand endpoint device is regulated and the other endpoint devices are not. In some embodiments, endpoint devices receive hierarchical distribution of services based on one or more of service type, device type, user type and / or account statement. In some embodiments, an intermediate network interconnect device can provide a large or unlimited number of endpoint devices to connect to the network and easily control aggregate service usage parameters for the WWAN connection of the network interconnect device. intermediate. In some embodiments, the intermediate network interconnect device limits the number of endpoint devices that are allowed to connect to the WWAN network in accordance with the endpoint device count limits programmed in the service profile settings. of service processor 115 in the intermediate network interconnection device. In some embodiments, endpoint device traffic can be identified by various aspects of endpoint device credential including, for example, by Wi-Fi ID, MAC ID, IP address, user ID, LAN tag , endpoint device agent and / or witness or browser cookie credentials. In some embodiments, the service account of the intermediate network interconnect device may be billed for use of the global service and / or for the number of endpoint device connections allowed or experienced. In some embodiments, as the user or owner of intermediate network interconnect device registers for a higher endpoint device connection count, one or more aspects of the service use and / or implementation policy implementation of profiles in the profile settings of the service processor 115 can be increased.

The various verification techniques described herein can also be applied to the intermediate network interconnection device and extend to multiple endpoint devices. For example, they can be applied

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

network-based service usage measures to the intermediate network interconnection device as if the intermediate network interconnection device was an endpoint device.

For example, network-based service usage measures (for example, IPDR information) can be used to perform network verification checks to ensure that service use of the intermediate network interconnect device is within acceptable ranges based on network settings. Intermediate network interconnect device policy as described similarly with respect to various device embodiments. In some embodiments, in the event that the use of the intermediate network interconnect device service is outside the policy limits set for the service processor 115 of the intermediate network interconnect device, a notification may be sent to the account owner main interconnection device in intermediate network. The account owner of the main intermediate network interconnection device may also be required to acknowledge the notification. The notification can also be sent to one or more other users of the connection of the intermediate network interconnection device, possibly including all users. Other actions that may be taken if the service use measure of the network-based intermediate network interconnection device does not match the policy limits established in the service processor 115 includes notifying the user, notifying the user and requiring acknowledgment of receipt, Billing the user for additional service use, suspending the endpoint device, quarantining the endpoint device, sending the endpoint device to SPAN, and / or alerting the network manager or alerting a troubleshooting function Automated network In some embodiments, a device-based usage measure can be verified against a network-based service usage measure. It will now be apparent that the various service processor verification embodiments 115, service controller verification embodiments 122, network verification embodiments, authentication embodiments, and manipulation or detection prevention embodiments, such as those shown and described with with respect to Figures 22, 23, 26, 27 and 28, they can be applied to applications and embodiments of intermediate network interconnection device.

In some embodiments, it is desirable to match the use of an interconnecting device service in the intermediate network of an individual endpoint device or user with other service usage measures. For example, the individual endpoint device service usage measures recorded or reported from the endpoint devices and / or the intermediate network interconnect device may be added to form a total intermediate network interconnect device usage measurement. which is compared to a measure of use of interconnecting device in an aggregate intermediate network registered 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 network interconnect device service usage measure is compared to the aggregate network based service usage measure and provided that these two measures are within an acceptable tolerance, then the usage measures of Intermediate network interconnect device service are reliable and can be used for measures of use of intermediate network interconnect device and deeper endpoint device for service control and / or billing than may be possible on the network. In such embodiments, the individual endpoint device service usage measures obtained from the intermediate network interconnect device or endpoint device can be used to verify service usage of endpoint device against service policy concessions. In some embodiments, the endpoint device service usage measures are compared with intermediate network interconnect device measurements for the same endpoint devices.

In some embodiments, the IPDR records for one or more networks may include individual endpoint device service usage information. This is the case, for example, when IPDRs include information broken down by endpoint device credential, such as IP address or other endpoint device credential. In such cases, embodiments of intermediate network interconnection device may be employed in which the service usage information of the individual endpoint device measured in the network can be compared with service policy usage concessions or limits for the point device final. Also, in some embodiments, the individual endpoint device service usage measurements from an endpoint device service usage monitor and / or an intermediate network interconnect device service usage monitor can be compared with the network-based service usage information to verify that a service usage monitor of an endpoint device and / or an intermediate network interconnect device is operating properly.

As similarly described with respect to embodiments of endpoint device with no intermediate network interconnection device between the endpoint device and the network, in some embodiments of intermediate network interconnect device, usage monitor reports of service and service use can be periodically verified by performing a SPAN function in traffic for an intermediate network interconnection device. SPAN traffic can be analyzed in a real-time manner or in a non-real-time manner on the network and the results can be compared with the service policies or service usage measures of the intermediate network interconnect device or point device final.

The synchronized device notification and acknowledgment embodiments can also be used in the case where a service account is applied to the intermediate network interconnection device. The service usage counters in the intermediate network interconnect device can be synchronized or updated with the

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Network-based measures and the differences between the two can be minimized. The service usage notification can be sent to one or more of the endpoint devices connected to the intermediate network interconnection device. For example, the notification can be sent to the intermediate network interconnect device manager or service owner, all endpoint devices or the most active endpoint devices.

Similarly, user preference feedback can be collected from one or more of the service users connected to the intermediate network interconnection device. In some embodiments, user preferences or user service selections or service settings are collected from a user or a subset of endpoint devices used by the service subscriber. In some embodiments, more than one service user may 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 described in a similar manner with respect to various device embodiments, user preferences of established service control policies that provide the user with their selected cost balance and service capacity in a manner that meets the requirements of the device can be used net neutrality Similarly, in some embodiments, the service monitoring and client resource management information collected on the intermediate network interconnect device or endpoint devices may be filtered according to user privacy preferences to maintain the level of privacy. of user selected by the user.

Implementation of the adaptive intermediate network interconnection device policy can also be implemented in the embodiments of the service processor 115 of the intermediate network interconnection device, as similarly described with respect to various device embodiments. In some embodiments, the service policy implementation for the intermediate network interconnect device may be adapted by the agents of the service processor 115 (for example, the policy control agent 1692 that functions to control the settings in the deployment agent of policy 1690, and / or another agent or service processor function) to achieve a higher level service use objective. In some embodiments, the use or adaptation objectives may be based on use of aggregate endpoint device for the network services of the intermediate network interconnect device, and in some embodiments, the higher level use or adaptation objectives may be applied. to one or more individual endpoint devices.

In some embodiments, even if there is an intermediate network interconnect device account, there may be multiple options for multiple or multiple user endpoint device operation in which the number of endpoint devices, number of users or service capabilities For some of the endpoint devices or users are selectable. These parameters are adapted by an intermediate network interconnect device service profile that includes the service capabilities to be delivered to a multitude of endpoint devices or users. In some cases, some endpoint devices or users have a different profile in the intermediate network interconnect device service processor 115 with differentiated capabilities compared to the profile of the service processor 115 of the intermediate network interconnect device for others. endpoint devices or users. This is the case for some of the examples provided in this document. These multiple or multiple user endpoint device service profiles in the intermediate network interconnect device service processor 115 may share services equally or may allow access services more suitable for some endpoint devices or users than others. In some embodiments, a service profile implemented by the service processor 115 of the intermediate network interconnect device for an endpoint device or user is different than that of the service profile implemented by the service processor 115 for another device or user. endpoint (for example, providing service profile implementations differentiated by endpoint devices and / or users). The endpoint devices can be unequivocally identified for purposes that involve implementation of different service profiles on the agents of the service processor 115 in the intermediate network interconnection device (for example, depending on the embodiment, the monitoring agent for service 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, address local area network (for example, Wi-Fi address), MAC address endpoint device ID, user ID and / or endpoint device application layer label. This allows independent service use monitoring and control for different endpoint devices or users.

In some embodiments, an intermediate network interconnection device also bridges services to endpoint devices or users who have individually managed service profiles, service plans or service accounts. As discussed herein, the implementation of individual endpoint device service policy and / or service profile implementation can be achieved by classifying endpoint device service usage according to an endpoint device identifier of so that service monitoring, control assistance and information generation can be differentiated between one or more endpoint devices. These endpoint device identifiers can then be associated with a different service plan or account in service processor 115 and / or billing system 123. Monitoring, generation of information, notification and control of specific service usage control The endpoint device or user can be achieved by running one or more profiles for each endpoint device or each user.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

It will now be clear that billing can also be implemented with a single account that encompasses service usage for all users or endpoint devices connected to an intermediate network interconnect device, or for individual users, endpoint devices, user groups or groups of endpoint devices connected to an intermediate network interconnection device. As described similarly with respect to the service profile, this is achieved by associating service usage events and billing events associated with an endpoint device identifier, user identifier, endpoint device group identifier, and / or user group identifier.

In some embodiments, endpoint devices or users connect more than one intermediate network interconnect device with the same service account, service plan or service profile. In some embodiments, the intermediate network interconnection device requires an authentication sequence for the endpoint device or user before allowing connection to the network through the intermediate network interconnection device. This authentication sequence may imply that the endpoint device communicates an active account or admission credential with the intermediate network interconnection device. The intermediate network interconnection device may compare the credential with a local database or may consult a database on the network to support the endpoint device to the network connection of the intermediate network interconnection device. In any case, with the condition that the user or network credential authorization process is passed, the service profile settings of the service processor 115 for the endpoint device are applied and then service is established as discussed in This document. In these cases, verification can be achieved as described in this document. In some embodiments, even if the endpoint device does not have a service processor 115, with the proviso that the intermediate network interconnect device service policy implementations and / or service profile implementations are verified as described in this document, then the intermediate network interconnection device will precisely help control and generate service usage information for the different endpoint devices or users, and the appropriate service and / or billing policy control can be maintained. .

In some embodiments, when the endpoint device attempts to connect to the intermediate network interconnect device, if the user or endpoint device no longer has an active account or login credential that the intermediate network interconnect device recognizes, The intermediate network interconnection device can then offer the endpoint device or user a service registration experience. This experience can be implemented in a number of ways, including a website, WAP site, portal, agent software download and other methods. For example, an automated recognition of new devices may redirect unauthorized endpoint devices to explore a website, WAP site, or portal site located on the intermediate network interconnect device or on the network. If the site is located on the intermediate network interconnect device, it can be cached and refreshed at a time of day when the network is not too busy. Once on the site, the user or endpoint device selects the plan choice they want, enter account information and, in some embodiments, download device agent software to assist in the implementation of network service policy and / or profile implementation with the intermediate network interconnection device. Once the user registers, the information is registered in the network database, the service account is established and the intermediate network interconnect device service profile for that user or endpoint device is activated and the User can start using the service.

In some embodiments, a website, WAP site, or portal site located in the intermediate network interconnect device may be used to provide the endpoint device user with a service usage monitor interface and a purchase interface. of service for cases in which the endpoint device does not have any special software to allow viewing of a more specialized service use monitor function for information received from the intermediate network interconnection device or network service usage counters. The service usage monitor for the intermediate network interconnect device can be synchronized, as described similarly with respect to various device embodiments. In some embodiments, the service usage notification system may also display cost data from a cost-use correspondence function. In some embodiments, the service usage notification system may have projected service usage or projected cost, as described similarly with respect to various device embodiments. The service usage monitor for controlling these service notification embodiments may be located in one or more of the endpoint device, the intermediate network interconnect device or the network.

In some embodiments, if multiple accounts are served by one or more intermediate network interconnection devices, verification can be performed at the service controls for the use of endpoint device or user service. As will now be apparent, as with the intermediate network interconnection device, the comparison of endpoint device or user service usage with usage policy settings can be verified in the ways described herein. If the use is found to be out of politics, then any of the out of policy actions described in this document may be performed, including, for example, notifying the end user, notifying and requiring acknowledgment of receipt, invoice for additional use, suspending , quarantine, SPAN and / or label for network manager or network error handling function. For example, the verification methods shown and described with respect to Figures 22, 23, 26, 27 and 28 may be applied for embodiments when the interconnecting devices in the intermediate network have multiple, multiple accounts

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

It will be apparent that the various embodiments described herein for automated provisioning and activation can be applied in a similar manner to the embodiments of intermediate network interconnection device. It will also be apparent that the various embodiments of the virtual service provider can be applied in a similar manner to the embodiments of the intermediate network interconnection device.

Ambient services can be employed in the intermediate network interconnection device and the environment services can therefore be provided to the endpoint devices. It will be apparent that the environmental service profile embodiments disclosed herein may be applied in a similar manner to the intermediate network interconnection device, and then the intermediate network interconnection device may provide these ambient services to connected endpoint devices. to the intermediate network interconnection device. It will also be apparent that the intermediate network interconnection device can provide an environment service profile as described herein to endpoint devices or users that have not yet registered for service, while providing other pay-per-service profiles. to endpoint devices or users that have registered for service.

Invoice per account embodiments can be applied similarly to the interconnection device embodiments in the intermediate network. For example, the invoice per account can be used in embodiments in which all endpoint devices or users are connected to the intermediate network interconnection device under an account, or to embodiments in which some endpoint devices or users are accounted for. separately with different service accounts, service plans or service profiles. In any case, it will be apparent that using one or more of the device identification or endpoint user identification aspects discussed in this document can be used in a profile and invoice per account to account for any endpoint device or service activity. . In such embodiments, billing event reports may also be provided for those activities that include the device identifiers or endpoint user for billing mediation and reconciliation to the individual endpoint device or user level. For example, this allows very deep service monitoring and billing capabilities with intermediate network interconnection devices.

The intermediate network interconnection device embodiments described above also have uses in machine-to-machine applications. It will be apparent that if the endpoint device includes the correct credentials to gain access to an existing account, or to allow an automatic provisioning and activation account to be established, then the endpoint device can connect to the network through the device of interconnection in intermediate network without human intervention. Additionally, the service profile established with the endpoint device for machine-to-machine communications can be established to provide the access required to support the machine-to-machine application to allow low-cost access services and prevent the device from endpoint is used incorrectly for any service other than the one intended. For example, the verification techniques and embodiments disclosed herein may similarly apply machine-to-machine applications of this type.

It will be apparent that the identifiers discussed above for account mediation with accounting up to the individual endpoint device or user level can be combined with a billing mediation server in the network that accepts interconnection device billing events in intermediate network with identification of endpoint device or indexed user identification billing, performs the necessary invoice mediation functions on account, formats billing events in the format used by the billing system, and transmits the mediated billing information to the billing system 123

In some embodiments, the functionality of the service processor 115 of the intermediate network interconnection device may be divided. The division varies from some or all of the service processor 115 in the device to some or all of the service processor 115 in the intermediate network interconnect device.

In some embodiments, the entire service processor 115 is located in the intermediate network interconnection device. The endpoint device does not participate in the functions of the service processor 115 and does not have service processor interface software 115. In some embodiments, the endpoint device has a small subset of service processor capabilities 115, which include , for example, a service notification UI or a login client with credentials. In some embodiments, service monitoring is implemented in the endpoint device or in both the endpoint device and the intermediate network interconnection device. In some embodiments, the endpoint device has additional service processor 115 capabilities that include, for example, application layer tagging that associates application layer activity with service monitoring of service processor 115 or service policy implementation. and / or service profile implementation information. This can be achieved by a range of techniques, for example, by transmitting the application tag information disclosed elsewhere to the service processor 115 of the intermediate network interconnection device so that policy implementation can be achieved with knowledge of the information of The application layer.

5

10

fifteen

twenty

25

30

35

40

Four. Five

fifty

55

60

65

Another example involves assigning IP addresses in the network interconnection stack of the intermediate network interconnection device to the endpoint devices so that different types of endpoint device traffic can be routed into traffic shaping queues of the processor. service 115, each queue having a policy profile implementation engine, and application layer labeling information or similar traffic identification information that is used to determine which policy implementation engine traffic should be routed to achieve the conformation of desired traffic for the type of traffic, type of application, type of service and / or type of content. In some embodiments, the traffic control policy is implemented in the endpoint device with a traffic control application layer or by implementing more functionality of the service processor 115, as described similarly with respect to various device embodiments. In the example of endpoint device service functionality, most or all of the functionality of service processor 115 is implemented in the endpoint device and the functionality of the intermediate network interconnect device can be reduced to a bridging function, forwarding or routing between endpoint devices and the network that performs little or no service control, monitoring and / or billing function. For example, service usage monitoring agents can also be provided on the endpoint device to aid verification.

In embodiments in which the endpoint device requires agent software, the software can be loaded at the time of manufacture or during distribution, loaded later and / or made available for download through the intermediate network interconnection device. In the case where the endpoint device agent SW is downloaded through the endpoint device, copies of the SW may be cached locally for one or more OS variants stored in a cache in the interconnect device. in an intermediate network, updating the cache through the network at convenient or appropriate times, the software can be downloaded live over the network when needed by the endpoint device. Registering the use of service to download this software is another example in which invoice functionality per account can be used to track network traffic that may not be desirable to bill an owner or user of endpoint device, and invoice functionality by Account can be used to record such use outside the invoice of the user's owner or endpoint device.

Any endpoint device agent software required to connect to the intermediate network interconnect device can also be implemented as a service processor developer kit 115 as described herein and distributed to assist manufacturers, service providers. and virtual service providers by providing new devices in networks with intermediate network interconnection device capability.

In the case of an interconnection device in intermediate network of femto cell, in some embodiments, it is desirable to facilitate the transfer of the WWAN network to the femto cell. In some embodiments, this is provided in the intermediate network interconnect device service processor 115 in a variety of ways. In some embodiments, voice and data traffic is routed through a VPN tunnel controlled by service processor 115 and connected to a network element, such as the transport gateway or other traffic concentration destination specified for the cell femto. In some embodiments, voice traffic, data traffic or both can be routed on secure Internet channels or open 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 network interconnection device controls the femto cell frequencies or local frequency channel intensity analysis through the intermediate network interconnect device control channel. In some embodiments, service processor 115 has a VPN connection to a network base station handover controller to assist in handover to and from the WWAN network and / or has the ability to order the endpoint device and the base station handover controller. In some embodiment, whenever an endpoint device is authenticated for femto cell access is in range of the femto cell, the service provider wishes to establish a profile of a service processor 115 to get the endpoint device to connect to the femto cell even if it has an intense signal with one or more WWAN base stations so that WWAN traffic can be downloaded. In some embodiments, service processor 115 may form a secure control plane link with network AAA functions to manage authorization and admission of endpoint devices that the cell has not yet supported, or network policies require reauthorization. every time an endpoint device attempts access. Once an endpoint device is connected to the intermediate network interconnection device of the femto cell, the traffic monitoring, control and verifiable billing functions described herein can be applied to various application embodiments. For example, the intermediate network interconnect device service policy verification techniques disclosed herein, as described similarly with respect to various device embodiments, can be applied similarly to the interconnect device embodiments. in intermediate network of femto cell.

In some embodiments, the service provider wishes to maintain the number of endpoint devices or users accessing an intermediate network interconnect device below a certain count specified in the service processor profile 115. In some embodiments, this it is achieved by controlling the number of IP addresses allowed in the local area side connection of the intermediate network interconnection device. In some embodiments, this is facilitated by observing the identification parameters of the device

endpoint available in endpoint device traffic. In some embodiments, this is facilitated by observing traffic patterns to determine the probable number of devices that connect to the network. For example, traffic demand patterns can be examined to determine how many users are likely to demand access at a time. Although the above embodiments have been described in some detail for purposes of clarity of understanding, the invention is not limited to the details provided. There can be many alternative ways of how to implement the invention. The disclosed embodiments are illustrative and not restrictive.

Claims (15)

5 10 fifteen twenty 25 30 35 40 Four. Five fifty 55 60 65 1. A mobile device (100) comprising: a cellular network modem (942) that can perform data communication through different operator access networks; Y a memory that can store pre-activation credentials and permanent credentials; in which the mobile device is configured to use stored pre-activation credentials and a policy pre-activation service in an environment access mode, wherein in the environment access mode the mobile device is configured to provide network access control in accordance with the pre-activation service policy to allow and block access to a first operator access network via the modem of cellular network, and in which a permitted network service activity is an activation sequence comprising: connect the device to an activation server connected to the Internet through the first operator access network, provide cellular network service options from the activation server to a user of the device, which includes cellular network service options that correspond to different service providers, accept user input to select a first of the cellular network service options for one selected from the different service providers, forwarding, based on the entry, an activation request for the first service option to the activation server, and receive from the activation server a set of permanent credentials that correspond to the selected service option and selected service provider and store permanent credentials in memory so that permanent credentials replace pre-activation credentials. 2. The mobile device of claim 1, wherein the pre-activation service policy is applied by a network element based on the pre-activation credentials, limiting the pre-activation service policy data access Internet through the first operator access network to access the activation server. 3. The mobile device of claim 1, wherein at least a portion of the preactivation service policy is stored in the device and applied by one or more device agents. 4. The mobile device of claim 3, wherein the at least a portion of the preactivation service policy stored in the device and applied by the device agents limits Internet data access through the first network of operator access to access the activation server and / or in which the at least a portion of the pre-activation service policy stored in the device and applied by the device agents limits a non-zero amount of data access Internet through the first operator access network while using pre-activation credentials and / or in which the at least a portion of the pre-activation service policy stored on the device and applied by agents Device allows an environment access to retrieve service improvement selection options. 5. The mobile device of claim 1, wherein the permanent credentials are associated with a data service policy that allows Internet data access not allowed by the pre-activation service policy, at least some aspects of the policy of data service received by the device as a result of the activation request, stored in the device, and applied by one or more device agents. 6. The mobile device of claim 1, wherein the pre-activation credentials and at least some aspects of the pre-activation service policy are preinstalled on the mobile device. 7. The mobile device of claim 1, wherein the credential memory is at least partially resident in a subscriber identity module (SIM) installed in the device, in particular in which the pre-activation credentials associate the device with a service provider that operates the activation server. 8. The mobile device of claim 7, wherein the pre-activation credentials allow a selection of multiple operator access networks as the first operator access network, in particular wherein the one or more device agents select the first operator access network from among the multiple operator access networks based on at least one of a list of stored preference, relative signal strength and current availability. 9. The mobile device of claim 1, wherein the credential memory comprises at least one master credential that cannot be reprogrammed during the activation sequence. 10. The mobile device of claim 1, wherein the pre-activation credentials are not associated with a user, and the permanent credentials are associated with a user and / or in which the permanent credentials include at least some of the pre-activation credentials. 5 10 fifteen twenty 25 30 35 11. The mobile device of claim 1, wherein the device that stores the permanent credentials in the credential memory to replace the pre-activation credentials comprises the device storing, in a subscriber identity module installed in the device , an indication of the selected service provider and a certificate or secure signature. 12. The mobile device of claim 1, wherein the device is configured to detect and respond to a first attempt by the user to access the Internet through the first operator access network by initiating the activation sequence. 13. The mobile device of claim 1, wherein a specific affiliation of the different service providers provided in the cellular network service options is geographically specific to the location of the mobile device at the time of initiation of the activation sequence . 14. The mobile device of claim 1, wherein the cellular network service options include multiple service plan options for at least one of the different service providers, in particular in which at least one of the different service providers is a mobile virtual network operator. 15. An operation method in a mobile device having a cellular network modem, the method comprising: in an environment access mode using stored pre-activation credentials, providing network access control in accordance with a service policy pre-activation to allow and block access to a first operator access network through the cellular network modem, in which a permitted network service activity is an activation sequence comprising: connect the device to an activation server connected to the Internet through the first operator access network, provide cellular network service options of the activation server to a user of the device, which includes cellular network service options that correspond to different service providers, Accept user input to select a first of the cellular network service options for one selected from the different service providers, forwarding, based on the entry, an activation request for the first service option to the activation server, receive from the activation server a set of permanent credentials that correspond to the selected service option and selected service provider, and store permanent credentials so that permanent credentials replace pre-activation credentials.